Status in source: current.
Names: lldpXdcbxPortNumber
Technical details
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"lldpXdcbxPortNumber",
"OBJECT-TYPE",
"SYNTAX",
"LldpPortNumber",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"Each port contained in the chassis (that is known to the LLDP agent) is uniquely identified by a port number. A port number has no mandatory relationship to an InterfaceIndex object (of the interfaces MIB, IETF RFC 2863). If the LLDP agent is a IEEE 802.1D, IEEE 802.1Q bridge, the LldpPortNumber will have the same value as the dot1dBasePort object (defined in IETF RFC 1493) associated corresponding bridge port. If the system hosting LLDP agent is not an IEEE 802.1D or an IEEE 802.1Q bridge, the LldpPortNumber will have the same value as the corresponding interface's InterfaceIndex object. Port numbers should be in the range of 1 and 4096 since a particular port is also represented by the corresponding port number bit in LldpPortList.\"",
"::=",
"{",
"lldpXdcbxPortEntry",
"1",
"}"
],
"syntax_tree": [
[
"row",
"LldpPortNumber"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Each port contained in the chassis (that is known to the LLDP agent) is uniquely identified by a port number. A port number has no mandatory relationship to an InterfaceIndex object (of the interfaces MIB, IETF RFC 2863). If the LLDP agent is a IEEE 802.1D, IEEE 802.1Q bridge, the LldpPortNumber will have the same value as the dot1dBasePort object (defined in IETF RFC 1493) associated corresponding bridge port. If the system hosting LLDP agent is not an IEEE 802.1D or an IEEE 802.1Q bridge, the LldpPortNumber will have the same value as the corresponding interface's InterfaceIndex object. Port numbers should be in the range of 1 and 4096 since a particular port is also represented by the corresponding port number bit in LldpPortList."
],
null,
null,
null,
null
]
}
- Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
· Publisher's source file: Source package: observium-community-latest.tar.gz
Vendor MIB copy from the Observium Community archive.
Module: LLDP-EXT-DCBX-MIB
See published definition above
Module imports
{'LLDP-MIB': ['lldpExtensions', 'LldpPortNumber'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
Related source files and packages:
- NETGEAR official product and EOL MIB downloads
· Publisher's source file: Source package: MS510TX_TXPP_MIBS_V6.7.0.43.zip
Module: LLDP-EXT-DCBX-MIB
See published definition above
Module imports
{'LLDP-MIB': ['lldpExtensions', 'LldpPortNumber'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
Related source files and packages:
Same file in MX510TX_MS510TXPP_MIBS_ODM_V6.7.0.42.zip.
Same file in MS510TX_TXPP_V6.7.0.37_MIB_V6.7.0.37.zip.
- Common and standard MIB copies (LibreNMS/Observium Community)
· Publisher's source file: LLDP-EXT-DCBX-MIB
Vendor MIB copy from the LibreNMS archive.
Module: LLDP-EXT-DCBX-MIB
Same published definition
Module imports
{'LLDP-MIB': ['lldpExtensions', 'LldpPortNumber'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'NOTIFICATION-TYPE'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
Related source files and packages: