Management Information Base module for LLDP configuration, statistics, local system data and remote systems data components.
Copyright (C) IEEE (2005). This version of this MIB module is published as subclause 12.1 of IEEE Std 802.1AB-2005; see the standard itself for full legal notices.
The interval at which LLDP frames are transmitted on behalf of this LLDP agent.
The default value for lldpMessageTxInterval object is 30 seconds.
The value of this object must be restored from non-volatile storage after a re-initialization of the management system. Reference: IEEE 802.1AB-2005 10.5.3.3
lldpMessageTxHoldMultiplier
1.0.8802.1.1.2.1.1.2
Integer32 (2..10) · default 4
The time-to-live value expressed as a multiple of the lldpMessageTxInterval object. The actual time-to-live value used in LLDP frames, transmitted on behalf of this LLDP agent, can be expressed by the following formula: TTL = min(65535, (lldpMessageTxInterval * lldpMessageTxHoldMultiplier)) For example, if the value of lldpMessageTxInterval is '30', and the value of lldpMessageTxHoldMultiplier is '4', then the value '120' is encoded in the TTL field in the LLDP header.
The default value for lldpMessageTxHoldMultiplier object is 4.
The value of this object must be restored from non-volatile storage after a re-initialization of the management system. Reference: IEEE 802.1AB-2005 10.5.3.3
lldpReinitDelay
1.0.8802.1.1.2.1.1.3
Integer32 (1..10) · seconds · default 2
The lldpReinitDelay indicates the delay (in units of seconds) from when lldpPortConfigAdminStatus object of a particular port becomes 'disabled' until re-initialization will be attempted.
The default value for lldpReintDelay object is two seconds.
The value of this object must be restored from non-volatile storage after a re-initialization of the management system. Reference: IEEE 802.1AB-2005 10.5.3.3
lldpTxDelay
1.0.8802.1.1.2.1.1.4
Integer32 (1..8192) · seconds · default 2
The lldpTxDelay indicates the delay (in units of seconds) between successive LLDP frame transmissions initiated by value/status changes in the LLDP local systems MIB. The recommended value for the lldpTxDelay is set by the
following formula:
1 <= lldpTxDelay <= (0.25 * lldpMessageTxInterval)
The default value for lldpTxDelay object is two seconds.
The value of this object must be restored from non-volatile storage after a re-initialization of the management system. Reference: IEEE 802.1AB-2005 10.5.3.3
lldpNotificationInterval
1.0.8802.1.1.2.1.1.5
Integer32 (5..3600) · seconds · default 5
This object controls the transmission of LLDP notifications.
the agent must not generate more than one lldpRemTablesChange notification-event in the indicated period, where a 'notification-event' is the transmission of a single notification PDU type to a list of notification destinations. If additional changes in lldpRemoteSystemsData object groups occur within the indicated throttling period, then these trap- events must be suppressed by the agent. An NMS should periodically check the value of lldpStatsRemTableLastChangeTime to detect any missed lldpRemTablesChange notification-events, e.g. due to throttling or transmission loss.
If notification transmission is enabled for particular ports, the suggested default throttling period is 5 seconds.
The value of this object must be restored from non-volatile storage after a re-initialization of the management system.
lldpStatsRemTablesLastChangeTime
1.0.8802.1.1.2.1.2.1
TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be
defined in the description of any object defined using this type.
If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks
The value of sysUpTime object (defined in IETF RFC 3418) at the time an entry is created, modified, or deleted in the in tables associated with the lldpRemoteSystemsData objects and all LLDP extension objects associated with remote systems.
An NMS can use this object to reduce polling of the lldpRemoteSystemsData objects.
lldpStatsRemTablesInserts
1.0.8802.1.1.2.1.2.2
ZeroBasedCounter32This TC describes an object that counts events with the following semantics: objects of this type will be set to zero(0) on creation and will thereafter count appropriate events, wrapping back to zero(0) when the value 2^32 is reached.
Provided that an application discovers the new object within the minimum time to wrap, it can use the initial value as a delta since it last polled the table of which this object is part. It is important for a management station to be aware of this minimum time and the actual time between polls, and to discard data if the actual time is too long or there is no defined minimum time.
Typically, this TC is used in tables where the INDEX space is constantly changing and/or the TimeFilter mechanism is in use. · Gauge32 · table entries
The number of times the complete set of information advertised by a particular MSAP has been inserted into tables contained in lldpRemoteSystemsData and lldpExtensions objects.
The complete set of information received from a particular MSAP should be inserted into related tables. If partial information cannot be inserted for a reason such as lack of resources, all of the complete set of information should be removed.
This counter should be incremented only once after the complete set of information is successfully recorded in all related tables. Any failures during inserting information set which result in deletion of previously inserted information should not trigger any changes in lldpStatsRemTablesInserts since the insert is not completed yet or or in lldpStatsRemTablesDeletes, since the deletion would only be a partial deletion. If the failure was the result of lack of resources, the lldpStatsRemTablesDrops counter should be incremented once.
lldpStatsRemTablesDeletes
1.0.8802.1.1.2.1.2.3
ZeroBasedCounter32This TC describes an object that counts events with the following semantics: objects of this type will be set to zero(0) on creation and will thereafter count appropriate events, wrapping back to zero(0) when the value 2^32 is reached.
Provided that an application discovers the new object within the minimum time to wrap, it can use the initial value as a delta since it last polled the table of which this object is part. It is important for a management station to be aware of this minimum time and the actual time between polls, and to discard data if the actual time is too long or there is no defined minimum time.
Typically, this TC is used in tables where the INDEX space is constantly changing and/or the TimeFilter mechanism is in use. · Gauge32 · table entries
The number of times the complete set of information advertised by a particular MSAP has been deleted from tables contained in lldpRemoteSystemsData and lldpExtensions objects.
This counter should be incremented only once when the complete set of information is completely deleted from all related tables. Partial deletions, such as deletion of rows associated with a particular MSAP from some tables, but not from all tables are not allowed, thus should not change the value of this counter.
lldpStatsRemTablesDrops
1.0.8802.1.1.2.1.2.4
ZeroBasedCounter32This TC describes an object that counts events with the following semantics: objects of this type will be set to zero(0) on creation and will thereafter count appropriate events, wrapping back to zero(0) when the value 2^32 is reached.
Provided that an application discovers the new object within the minimum time to wrap, it can use the initial value as a delta since it last polled the table of which this object is part. It is important for a management station to be aware of this minimum time and the actual time between polls, and to discard data if the actual time is too long or there is no defined minimum time.
Typically, this TC is used in tables where the INDEX space is constantly changing and/or the TimeFilter mechanism is in use. · Gauge32 · table entries
The number of times the complete set of information advertised by a particular MSAP could not be entered into tables contained in lldpRemoteSystemsData and lldpExtensions objects because of insufficient resources.
lldpStatsRemTablesAgeouts
1.0.8802.1.1.2.1.2.5
ZeroBasedCounter32This TC describes an object that counts events with the following semantics: objects of this type will be set to zero(0) on creation and will thereafter count appropriate events, wrapping back to zero(0) when the value 2^32 is reached.
Provided that an application discovers the new object within the minimum time to wrap, it can use the initial value as a delta since it last polled the table of which this object is part. It is important for a management station to be aware of this minimum time and the actual time between polls, and to discard data if the actual time is too long or there is no defined minimum time.
Typically, this TC is used in tables where the INDEX space is constantly changing and/or the TimeFilter mechanism is in use. · Gauge32
The number of times the complete set of information advertised by a particular MSAP has been deleted from tables contained in lldpRemoteSystemsData and lldpExtensions objects because the information timeliness interval has expired.
This counter should be incremented only once when the complete set of information is completely invalidated (aged out) from all related tables. Partial aging, similar to deletion case, is not allowed, and thus, should not change the value of this counter.
lldpLocChassisIdSubtype
1.0.8802.1.1.2.1.3.1
LldpChassisIdSubtype1 = chassisComponent2 = interfaceAlias3 = portComponent4 = macAddress5 = networkAddress6 = interfaceName7 = localThis TC describes the source of a chassis identifier.
The enumeration 'chassisComponent(1)' represents a chassis identifier based on the value of entPhysicalAlias object (defined in IETF RFC 2737) for a chassis component (i.e., an entPhysicalClass value of 'chassis(3)').
The enumeration 'interfaceAlias(2)' represents a chassis identifier based on the value of ifAlias object (defined in IETF RFC 2863) for an interface on the containing chassis.
The enumeration 'portComponent(3)' represents a chassis identifier based on the value of entPhysicalAlias object (defined in IETF RFC 2737) for a port or backplane component (i.e., entPhysicalClass value of 'port(10)' or 'backplane(4)'), within the containing chassis.
The enumeration 'macAddress(4)' represents a chassis identifier based on the value of a unicast source address (encoded in network byte order and IEEE 802.3 canonical bit order), of a port on the containing chassis as defined in IEEE Std 802-2001.
The enumeration 'networkAddress(5)' represents a chassis identifier based on a network address, associated with a particular chassis. The encoded address is actually composed of two fields. The first field is a single octet, representing the IANA AddressFamilyNumbers value for the specific address type, and the second field is the network address value.
The enumeration 'interfaceName(6)' represents a chassis identifier based on the value of ifName object (defined in IETF RFC 2863) for an interface on the containing chassis.
The enumeration 'local(7)' represents a chassis identifier based on a locally defined value. · Integer32
The type of encoding used to identify the chassis associated with the local system. Reference: IEEE 802.1AB-2005 9.5.2.2
lldpLocChassisId
1.0.8802.1.1.2.1.3.2
LldpChassisIdThis TC describes the format of a chassis identifier string. Objects of this type are always used with an associated LldpChassisIdSubtype object, which identifies the format of the particular LldpChassisId object instance.
If the associated LldpChassisIdSubtype object has a value of 'chassisComponent(1)', then the octet string identifies a particular instance of the entPhysicalAlias object (defined in IETF RFC 2737) for a chassis component (i.e., an entPhysicalClass value of 'chassis(3)').
If the associated LldpChassisIdSubtype object has a value of 'interfaceAlias(2)', then the octet string identifies a particular instance of the ifAlias object (defined in IETF RFC 2863) for an interface on the containing chassis. If the particular ifAlias object does not contain any values, another chassis identifier type should be used.
If the associated LldpChassisIdSubtype object has a value of 'portComponent(3)', then the octet string identifies a particular instance of the entPhysicalAlias object (defined in IETF RFC 2737) for a port or backplane component within the containing chassis.
If the associated LldpChassisIdSubtype object has a value of 'macAddress(4)', then this string identifies a particular unicast source address (encoded in network byte order and IEEE 802.3 canonical bit order), of a port on the containing chassis as defined in IEEE Std 802-2001.
If the associated LldpChassisIdSubtype object has a value of 'networkAddress(5)', then this string identifies a particular network address, encoded in network byte order, associated with one or more ports on the containing chassis. The first octet contains the IANA Address Family Numbers enumeration value for the specific address type, and octets 2 through N contain the network address value in network byte order.
If the associated LldpChassisIdSubtype object has a value of 'interfaceName(6)', then the octet string identifies a particular instance of the ifName object (defined in IETF RFC 2863) for an interface on the containing chassis. If the particular ifName object does not contain any values, another chassis identifier type should be used.
If the associated LldpChassisIdSubtype object has a value of 'local(7)', then this string identifies a locally assigned Chassis ID. SIZE (1..255) · OCTET STRING
The string value used to identify the chassis component associated with the local system. Reference: IEEE 802.1AB-2005 9.5.2.3
lldpLocSysName
1.0.8802.1.1.2.1.3.3
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t
The string value used to identify the system name of the local system. If the local agent supports IETF RFC 3418, lldpLocSysName object should have the same value of sysName object. Reference: IEEE 802.1AB-2005 9.5.6.2
lldpLocSysDesc
1.0.8802.1.1.2.1.3.4
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t
The string value used to identify the system description of the local system. If the local agent supports IETF RFC 3418, lldpLocSysDesc object should have the same value of sysDesc object. Reference: IEEE 802.1AB-2005 9.5.7.2
lldpLocSysCapSupported
1.0.8802.1.1.2.1.3.5
LldpSystemCapabilitiesMapThis TC describes the system capabilities.
The bit 'other(0)' indicates that the system has capabilities other than those listed below.
The bit 'repeater(1)' indicates that the system has repeater capability.
The bit 'bridge(2)' indicates that the system has bridge capability.
The bit 'wlanAccessPoint(3)' indicates that the system has WLAN access point capability.
The bit 'router(4)' indicates that the system has router capability.
The bit 'telephone(5)' indicates that the system has telephone capability.
The bit 'docsisCableDevice(6)' indicates that the system has DOCSIS Cable Device capability (IETF RFC 2669 & 2670).
The bit 'stationOnly(7)' indicates that the system has only station capability and nothing else. · BITS
The bitmap value used to identify which system capabilities are supported on the local system. Reference: IEEE 802.1AB-2005 9.5.8.1
lldpLocSysCapEnabled
1.0.8802.1.1.2.1.3.6
LldpSystemCapabilitiesMapThis TC describes the system capabilities.
The bit 'other(0)' indicates that the system has capabilities other than those listed below.
The bit 'repeater(1)' indicates that the system has repeater capability.
The bit 'bridge(2)' indicates that the system has bridge capability.
The bit 'wlanAccessPoint(3)' indicates that the system has WLAN access point capability.
The bit 'router(4)' indicates that the system has router capability.
The bit 'telephone(5)' indicates that the system has telephone capability.
The bit 'docsisCableDevice(6)' indicates that the system has DOCSIS Cable Device capability (IETF RFC 2669 & 2670).
The bit 'stationOnly(7)' indicates that the system has only station capability and nothing else. · BITS
The bitmap value used to identify which system capabilities are enabled on the local system. Reference: IEEE 802.1AB-2005 9.5.8.2
Table details
lldpPortConfigTable
1.0.8802.1.1.2.1.1.6
Index: lldpPortConfigPortNum
The table that controls LLDP frame transmission on individual ports.
lldpPortConfigPortNum
1.0.8802.1.1.2.1.1.6.1.1
LldpPortNumberEach 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. (1..4096) · Integer32
The index value used to identify the port component (contained in the local chassis with the LLDP agent) associated with this entry.
The value of this object is used as a port index to the lldpPortConfigTable.
The administratively desired status of the local LLDP agent.
If the associated lldpPortConfigAdminStatus object has a value of 'txOnly(1)', then LLDP agent will transmit LLDP frames on this port and it will not store any information about the remote systems connected.
If the associated lldpPortConfigAdminStatus object has a value of 'rxOnly(2)', then the LLDP agent will receive, but it will not transmit LLDP frames on this port.
If the associated lldpPortConfigAdminStatus object has a value of 'txAndRx(3)', then the LLDP agent will transmit and receive LLDP frames on this port.
If the associated lldpPortConfigAdminStatus object has a value of 'disabled(4)', then LLDP agent will not transmit or receive LLDP frames on this port. If there is remote systems information which is received on this port and stored in other tables, before the port's lldpPortConfigAdminStatus becomes disabled, then the information will naturally age out. Reference: IEEE 802.1AB-2005 10.5.1
The lldpPortConfigNotificationEnable controls, on a per
port basis, whether or not notifications from the agent
are enabled. The value true(1) means that notifications are enabled; the value false(2) means that they are not.
lldpPortConfigTLVsTxEnable
1.0.8802.1.1.2.1.1.6.1.4
BITS · default { }
The lldpPortConfigTLVsTxEnable, defined as a bitmap, includes the basic set of LLDP TLVs whose transmission is allowed on the local LLDP agent by the network management. Each bit in the bitmap corresponds to a TLV type associated with a specific optional TLV.
It should be noted that the organizationally-specific TLVs are excluded from the lldpTLVsTxEnable bitmap.
LLDP Organization Specific Information Extension MIBs should have similar configuration object to control transmission of their organizationally defined TLVs.
The bit 'portDesc(0)' indicates that LLDP agent should transmit 'Port Description TLV'.
The bit 'sysName(1)' indicates that LLDP agent should transmit 'System Name TLV'.
The bit 'sysDesc(2)' indicates that LLDP agent should transmit 'System Description TLV'.
The bit 'sysCap(3)' indicates that LLDP agent should transmit 'System Capabilities TLV'.
There is no bit reserved for the management address TLV type since transmission of management address TLVs are controlled by another object, lldpConfigManAddrTable.
The default value for lldpPortConfigTLVsTxEnable object is empty set, which means no enumerated values are set.
The value of this object must be restored from non-volatile storage after a re-initialization of the management system. Reference: IEEE 802.1AB-2005 10.2.1.1
The table that controls selection of LLDP management address TLV instances to be transmitted on individual ports.
lldpConfigManAddrPortsTxEnable
1.0.8802.1.1.2.1.1.7.1.1
LldpPortListEach octet within this value specifies a set of eight ports, with the first octet specifying ports 1 through 8, the second octet specifying ports 9 through 16, etc. Within each octet, the most significant bit represents the lowest numbered port, and the least significant bit represents the highest numbered port. Thus, each port of the system is represented by a single bit within the value of this object. If that bit has a value of '1' then that port is included in the set of ports; the port is not included if its bit has a value of '0'.Reference: IETF RFC 2674 section 5 SIZE (0..512) · OCTET STRING · default '00000000'H
A set of ports that are identified by a PortList, in which each port is represented as a bit. The corresponding local system management address instance will be transmitted on the member ports of the lldpManAddrPortsTxEnable.
The default value for lldpConfigManAddrPortsTxEnable object is empty binary string, which means no ports are specified for advertising indicated management address instance. Reference: IEEE 802.1AB-2005 10.2.1.1
lldpStatsTxPortTable
1.0.8802.1.1.2.1.2.6
Index: lldpStatsTxPortNum
A table containing LLDP transmission statistics for individual ports. Entries are not required to exist in this table while the lldpPortConfigEntry object is equal to 'disabled(4)'.
lldpStatsTxPortNum
1.0.8802.1.1.2.1.2.6.1.1
LldpPortNumberEach 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. (1..4096) · Integer32
The index value used to identify the port component (contained in the local chassis with the LLDP agent) associated with this entry.
The value of this object is used as a port index to the lldpStatsTable.
lldpStatsTxPortFramesTotal
1.0.8802.1.1.2.1.2.6.1.2
Counter32
The number of LLDP frames transmitted by this LLDP agent on the indicated port. Reference: IEEE 802.1AB-2005 10.5.2.1
lldpStatsRxPortTable
1.0.8802.1.1.2.1.2.7
Index: lldpStatsRxPortNum
A table containing LLDP reception statistics for individual ports. Entries are not required to exist in this table while the lldpPortConfigEntry object is equal to 'disabled(4)'.
lldpStatsRxPortNum
1.0.8802.1.1.2.1.2.7.1.1
LldpPortNumberEach 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. (1..4096) · Integer32
The index value used to identify the port component (contained in the local chassis with the LLDP agent) associated with this entry.
The value of this object is used as a port index to the lldpStatsTable.
lldpStatsRxPortFramesDiscardedTotal
1.0.8802.1.1.2.1.2.7.1.2
Counter32
The number of LLDP frames received by this LLDP agent on the indicated port, and then discarded for any reason. This counter can provide an indication that LLDP header formating problems may exist with the local LLDP agent in the sending system or that LLDPDU validation problems may exist with the local LLDP agent in the receiving system. Reference: IEEE 802.1AB-2005 10.5.2.2
lldpStatsRxPortFramesErrors
1.0.8802.1.1.2.1.2.7.1.3
Counter32
The number of invalid LLDP frames received by this LLDP agent on the indicated port, while this LLDP agent is enabled. Reference: IEEE 802.1AB-2005 10.5.2.2
lldpStatsRxPortFramesTotal
1.0.8802.1.1.2.1.2.7.1.4
Counter32
The number of valid LLDP frames received by this LLDP agent on the indicated port, while this LLDP agent is enabled. Reference: IEEE 802.1AB-2005 10.5.2.2
lldpStatsRxPortTLVsDiscardedTotal
1.0.8802.1.1.2.1.2.7.1.5
Counter32
The number of LLDP TLVs discarded for any reason by this LLDP agent on the indicated port. Reference: IEEE 802.1AB-2005 10.5.2.2
lldpStatsRxPortTLVsUnrecognizedTotal
1.0.8802.1.1.2.1.2.7.1.6
Counter32
The number of LLDP TLVs received on the given port that are not recognized by this LLDP agent on the indicated port.
An unrecognized TLV is referred to as the TLV whose type value is in the range of reserved TLV types (000 1001 - 111 1110) in Table 9.1 of IEEE Std 802.1AB-2005. An unrecognized TLV may be a basic management TLV from a later LLDP version. Reference: IEEE 802.1AB-2005 10.5.2.2
lldpStatsRxPortAgeoutsTotal
1.0.8802.1.1.2.1.2.7.1.7
ZeroBasedCounter32This TC describes an object that counts events with the following semantics: objects of this type will be set to zero(0) on creation and will thereafter count appropriate events, wrapping back to zero(0) when the value 2^32 is reached.
Provided that an application discovers the new object within the minimum time to wrap, it can use the initial value as a delta since it last polled the table of which this object is part. It is important for a management station to be aware of this minimum time and the actual time between polls, and to discard data if the actual time is too long or there is no defined minimum time.
Typically, this TC is used in tables where the INDEX space is constantly changing and/or the TimeFilter mechanism is in use. · Gauge32
The counter that represents the number of age-outs that occurred on a given port. An age-out is the number of times the complete set of information advertised by a particular MSAP has been deleted from tables contained in lldpRemoteSystemsData and lldpExtensions objects because the information timeliness interval has expired.
This counter is similar to lldpStatsRemTablesAgeouts, except that the counter is on a per port basis. This enables NMS to poll tables associated with the lldpRemoteSystemsData objects and all LLDP extension objects associated with remote systems on the indicated port only.
This counter should be set to zero during agent initialization and its value should not be saved in non-volatile storage. When a port's admin status changes from 'disabled' to 'rxOnly', 'txOnly' or 'txAndRx', the counter associated with the same port should reset to 0. The agent should also flush all remote system information associated with the same port.
This counter should be incremented only once when the complete set of information is invalidated (aged out) from all related tables on a particular port. Partial aging is not allowed, and thus, should not change the value of this counter. Reference: IEEE 802.1AB-2005 10.5.2.2
lldpLocPortTable
1.0.8802.1.1.2.1.3.7
Index: lldpLocPortNum
This table contains one or more rows per port information associated with the local system known to this agent.
lldpLocPortNum
1.0.8802.1.1.2.1.3.7.1.1
LldpPortNumberEach 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. (1..4096) · Integer32
The index value used to identify the port component (contained in the local chassis with the LLDP agent) associated with this entry.
The value of this object is used as a port index to the lldpLocPortTable.
lldpLocPortIdSubtype
1.0.8802.1.1.2.1.3.7.1.2
LldpPortIdSubtype1 = interfaceAlias2 = portComponent3 = macAddress4 = networkAddress5 = interfaceName6 = agentCircuitId7 = localThis TC describes the source of a particular type of port identifier used in the LLDP MIB.
The enumeration 'interfaceAlias(1)' represents a port identifier based on the ifAlias MIB object, defined in IETF RFC 2863.
The enumeration 'portComponent(2)' represents a port identifier based on the value of entPhysicalAlias (defined in IETF RFC 2737) for a port component (i.e., entPhysicalClass value of 'port(10)'), within the containing chassis.
The enumeration 'macAddress(3)' represents a port identifier based on a unicast source address (encoded in network byte order and IEEE 802.3 canonical bit order), which has been detected by the agent and associated with a particular port (IEEE Std 802-2001).
The enumeration 'networkAddress(4)' represents a port identifier based on a network address, detected by the agent and associated with a particular port.
The enumeration 'interfaceName(5)' represents a port identifier based on the ifName MIB object, defined in IETF RFC 2863.
The enumeration 'agentCircuitId(6)' represents a port identifier based on the agent-local identifier of the circuit (defined in RFC 3046), detected by the agent and associated with a particular port.
The enumeration 'local(7)' represents a port identifier based on a value locally assigned. · Integer32
The type of port identifier encoding used in the associated 'lldpLocPortId' object. Reference: IEEE 802.1AB-2005 9.5.3.2
lldpLocPortId
1.0.8802.1.1.2.1.3.7.1.3
LldpPortIdThis TC describes the format of a port identifier string. Objects of this type are always used with an associated LldpPortIdSubtype object, which identifies the format of the particular LldpPortId object instance.
If the associated LldpPortIdSubtype object has a value of 'interfaceAlias(1)', then the octet string identifies a particular instance of the ifAlias object (defined in IETF RFC 2863). If the particular ifAlias object does not contain any values, another port identifier type should be used.
If the associated LldpPortIdSubtype object has a value of 'portComponent(2)', then the octet string identifies a particular instance of the entPhysicalAlias object (defined in IETF RFC 2737) for a port or backplane component.
If the associated LldpPortIdSubtype object has a value of 'macAddress(3)', then this string identifies a particular unicast source address (encoded in network byte order and IEEE 802.3 canonical bit order) associated with the port (IEEE Std 802-2001).
If the associated LldpPortIdSubtype object has a value of 'networkAddress(4)', then this string identifies a network address associated with the port. The first octet contains the IANA AddressFamilyNumbers enumeration value for the specific address type, and octets 2 through N contain the networkAddress address value in network byte order.
If the associated LldpPortIdSubtype object has a value of 'interfaceName(5)', then the octet string identifies a particular instance of the ifName object (defined in IETF RFC 2863). If the particular ifName object does not contain any values, another port identifier type should be used.
If the associated LldpPortIdSubtype object has a value of 'agentCircuitId(6)', then this string identifies a agent-local identifier of the circuit (defined in RFC 3046).
If the associated LldpPortIdSubtype object has a value of 'local(7)', then this string identifies a locally assigned port ID. SIZE (1..255) · OCTET STRING
The string value used to identify the port component associated with a given port in the local system. Reference: IEEE 802.1AB-2005 9.5.3.3
lldpLocPortDesc
1.0.8802.1.1.2.1.3.7.1.4
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t
The string value used to identify the 802 LAN station's port description associated with the local system. If the local agent supports IETF RFC 2863, lldpLocPortDesc object should have the same value of ifDescr object. Reference: IEEE 802.1AB-2005 9.5.5.2
lldpLocManAddrTable
1.0.8802.1.1.2.1.3.8
Index: lldpLocManAddrSubtype · lldpLocManAddr
This table contains management address information on the local system known to this agent.
lldpLocManAddrSubtype
1.0.8802.1.1.2.1.3.8.1.1
AddressFamilyNumbers0 = other1 = ipV42 = ipV63 = nsap4 = hdlc5 = bbn18226 = all8027 = e1638 = e1649 = f6910 = x12111 = ipx12 = appleTalk13 = decnetIV14 = banyanVines15 = e164withNsap16 = dns17 = distinguishedName18 = asNumber19 = xtpOverIpv420 = xtpOverIpv621 = xtpNativeModeXTP22 = fibreChannelWWPN23 = fibreChannelWWNN24 = gwid25 = afi26 = mplsTpSectionEndpointIdentifier27 = mplsTpLspEndpointIdentifier28 = mplsTpPseudowireEndpointIdentifier16384 = eigrpCommonServiceFamily16385 = eigrpIpv4ServiceFamily16386 = eigrpIpv6ServiceFamily16387 = lispCanonicalAddressFormat16388 = bgpLs16389 = fortyeightBitMac16390 = sixtyfourBitMac16391 = oui16392 = mac2416393 = mac4016394 = ipv66416395 = rBridgePortID16396 = trillNickname16397 = universallyUniqueIdentifier65535 = reservedThe definition of this textual convention with the addition of newly assigned values is published periodically by the IANA, in either the Assigned Numbers RFC, or some derivative of it specific to Internet Network Management number assignments. (The latest arrangements can be obtained by contacting the IANA.)
The enumerations are described as:
other(0), -- none of the following
ipV4(1), -- IP Version 4
ipV6(2), -- IP Version 6
nsap(3), -- NSAP
hdlc(4), -- (8-bit multidrop)
bbn1822(5),
all802(6), -- (includes all 802 media
-- plus Ethernet 'canonical format')
e163(7),
e164(8), -- (SMDS, Frame Relay, ATM)
f69(9), -- (Telex)
x121(10), -- (X.25, Frame Relay)
ipx(11), -- IPX (Internet Protocol Exchange)
appleTalk(12), -- Apple Talk
decnetIV(13), -- DEC Net Phase IV
banyanVines(14), -- Banyan Vines
e164withNsap(15), -- (E.164 with NSAP format subaddress)
dns(16), -- (Domain Name System)
distinguishedName(17), -- (Distinguished Name, per X.500) asNumber(18), -- (16-bit quantity, per the AS number space)
xtpOverIpv4(19), -- XTP over IP version 4
xtpOverIpv6(20), -- XTP over IP version 6
xtpNativeModeXTP(21), -- XTP native mode XTP
fibreChannelWWPN(22), -- Fibre Channel World-Wide Port Name
fibreChannelWWNN(23), -- Fibre Channel World-Wide Node Name
gwid(24), -- Gateway Identifier
afi(25), -- AFI for L2VPN information
mplsTpSectionEndpointIdentifier(26), -- MPLS-TP Section Endpoint Identifier
mplsTpLspEndpointIdentifier(27), -- MPLS-TP LSP Endpoint Identifier
mplsTpPseudowireEndpointIdentifier(28), -- MPLS-TP Pseudowire Endpoint Identifier
eigrpCommonServiceFamily(16384), -- EIGRP Common Service Family
eigrpIpv4ServiceFamily(16385), -- EIGRP IPv4 Service Family
eigrpIpv6ServiceFamily(16386), -- EIGRP IPv6 Service Family
lispCanonicalAddressFormat(16387), -- LISP Canonical Address Format (LCAF)
bgpLs(16388), -- BGP-LS
fortyeightBitMacBitMac(16389), -- 48-bit MAC
sixtyfourBitMac(16390), -- 64-bit MAC
oui(16391), -- OUI
mac24(16392), -- MAC/24
mac40(16393), -- MAC/40
ipv664(16394), -- IPv6/64
rBridgePortID(16395), -- RBridge Port ID
trillNickname(16396), -- TRILL Nickname
universallyUniqueIdentifier(16397), -- Universally Unique Identifier (UUID)
reserved(65535)
Requests for new values should be made to IANA via email (iana&iana.org). · Integer32
The type of management address identifier encoding used in the associated 'lldpLocManagmentAddr' object. Reference: IEEE 802.1AB-2005 9.5.9.3
lldpLocManAddr
1.0.8802.1.1.2.1.3.8.1.2
LldpManAddressThe value of a management address associated with the LLDP agent that may be used to reach higher layer entities to assist discovery by network management.
It should be noted that appropriate security credentials, such as SNMP engineId, may be required to access the LLDP agent using a management address. These necessary credentials should be known by the network management and the objects associated with the credentials are not included in the LLDP agent. SIZE (1..31) · OCTET STRING
The string value used to identify the management address component associated with the local system. The purpose of this address is to contact the management entity. Reference: IEEE 802.1AB-2005 9.5.9.4
lldpLocManAddrLen
1.0.8802.1.1.2.1.3.8.1.3
Integer32
The total length of the management address subtype and the management address fields in LLDPDUs transmitted by the local LLDP agent.
The management address length field is needed so that the receiving systems that do not implement SNMP will not be required to implement an iana family numbers/address length equivalency table in order to decode the management adress. Reference: IEEE 802.1AB-2005 9.5.9.2
lldpLocManAddrIfSubtype
1.0.8802.1.1.2.1.3.8.1.4
LldpManAddrIfSubtype1 = unknown2 = ifIndex3 = systemPortNumberThis TC describes the basis of a particular type of interface associated with the management address.
The enumeration 'unknown(1)' represents the case where the interface is not known.
The enumeration 'ifIndex(2)' represents interface identifier based on the ifIndex MIB object.
The enumeration 'systemPortNumber(3)' represents interface identifier based on the system port numbering convention.Reference: IEEE 802.1AB-2005 9.5.9.5 · Integer32
The enumeration value that identifies the interface numbering method used for defining the interface number, associated with the local system. Reference: IEEE 802.1AB-2005 9.5.9.5
lldpLocManAddrIfId
1.0.8802.1.1.2.1.3.8.1.5
Integer32
The integer value used to identify the interface number regarding the management address component associated with the local system. Reference: IEEE 802.1AB-2005 9.5.9.6
lldpLocManAddrOID
1.0.8802.1.1.2.1.3.8.1.6
OBJECT IDENTIFIER
The OID value used to identify the type of hardware component or protocol entity associated with the management address advertised by the local system agent. Reference: IEEE 802.1AB-2005 9.5.9.8
This table contains one or more rows per physical network connection known to this agent. The agent may wish to ensure that only one lldpRemEntry is present for each local port, or it may choose to maintain multiple lldpRemEntries for the same local port.
The following procedure may be used to retrieve remote systems information updates from an LLDP agent:
1. NMS polls all tables associated with remote systems and keeps a local copy of the information retrieved. NMS polls periodically the values of the following objects: a. lldpStatsRemTablesInserts b. lldpStatsRemTablesDeletes c. lldpStatsRemTablesDrops d. lldpStatsRemTablesAgeouts e. lldpStatsRxPortAgeoutsTotal for all ports.
2. LLDP agent updates remote systems MIB objects, and sends out notifications to a list of notification destinations.
3. NMS receives the notifications and compares the new values of objects listed in step 1.
Periodically, NMS should poll the object lldpStatsRemTablesLastChangeTime to find out if anything has changed since the last poll. if something has changed, NMS will poll the objects listed in step 1 to figure out what kind of changes occurred in the tables.
if value of lldpStatsRemTablesInserts has changed, then NMS will walk all tables by employing TimeFilter with the last-polled time value. This request will return new objects or objects whose values are updated since the last poll.
if value of lldpStatsRemTablesAgeouts has changed, then NMS will walk the lldpStatsRxPortAgeoutsTotal and compare the new values with previously recorded ones. For ports whose lldpStatsRxPortAgeoutsTotal value is greater than the recorded value, NMS will have to retrieve objects associated with those ports from table(s) without employing a TimeFilter (which is performed by specifying 0 for the TimeFilter.)
lldpStatsRemTablesDeletes and lldpStatsRemTablesDrops objects are provided for informational purposes.
lldpRemTimeMark
1.0.8802.1.1.2.1.4.1.1.1
TimeFilterTo be used for the index to a table. Allows an application to download only those rows changed since a particular time.
Note that this is not a history mechanism. Only current values of underlying objects are returned; saved instance values associated with particular values of sysUpTime are not.
An entry is considered changed if the value of any object in the entry changes, if the row is created, or if any object in the entry is created or deleted. Note that deleted entries cannot be detected or downloaded.
A time-filtered conceptual table is created by inserting a single object of SYNTAX TimeFilter as the first INDEX component in a copy of an existing basic conceptual table (i.e., any SEQUENCE without a TimeFilter INDEX component). Thus, for each conceptual entry 'I' in the basic table, there exists N conceptual entries in the time-filtered version, indexed N.I, where 'N' is equal to the value of sysUpTime.
When an application retrieves conceptual instances from a time-filtered table, and an INDEX value is provided for the TimeFilter INDEX component 'N', the agent will only consider returning basic conceptual entries (e.g., 'fooColumn.N.I') if any column within the basic conceptual entry has changed since sysUpTime 'N'. If not, the basic conceptual entry will be ignored for the particular retrieval operation.
When sysUpTime is equal to zero, this table shall be empty.
One conceptual entry exists for each past value of sysUpTime, except that the whole table is purged should sysUpTime wrap.
As an entry in a time-filtered table is updated (i.e., one of the columns in the basic conceptual table is changed), new conceptual entries are also created in the time-filtered version (which still shares the now updated object values with all other instances). The number of unique time-filtered instances that are created is determined by the value of sysUpTime at which the basic entry was last updated. One unique instance will exist for each value of sysUpTime at the last update time for the row. However, a new TimeFilter index instance is created for each new sysUpTime value. The TimeFilter index values not associated with entry updates are called duplicate time-filtered instances.
After some deployment experience, it has been determined that a time-filtered table is more efficient if the agent stops a MIB walk operation by skipping over rows with a TimeFilter index value higher than the value in the received GetNext/GetBulk request. That is, instead of incrementing a TimeFilter index value, the agent will continue to the next object or table. As a consequence, GetNext or GetBulk operations will provide only one pass through a time-filtered table.
It is suggested that an agent implement a time-filtered table in this manner to improve performance and avoid a MIB walk getting stuck in time-filtered tables. It is, however, still acceptable for an agent to implement a time-filtered table in the traditional manner (i.e., every conceptual time-filtered instance is returned in GetNext and GetBulk PDU responses), and management applications must be able to deal with such traditional implementations.
See the appendix for further discussion of this textual convention.
The following example is provided to demonstrate TimeFilter behavior:
Consider the following basic conceptual table, basicFooTable. (Note that the basic version of a time-filtered table may not actually be defined.)
basicFooTable:
basicFooTable ... INDEX { fooIndex }
BasicFooEntry {
fooIndex Integer32,
fooCounts Counter32
}
For this example, the basicFooTable contains two static conceptual entries (fooIndex equals '1' and '2'), created at time zero. It also contains one dynamic conceptual entry (fooIndex equals '3'), which is created at time '3' and deleted at time '7'.
The time-filtered version of the basicFooTable could be defined as follows:
FooTable:
fooTable ... INDEX { fooTimeMark, fooIndex }
FooEntry {
fooTimeMark TimeFilter,
fooIndex Integer32,
fooCounts Counter32
}
Note that entries exist in the time-filtered conceptual table only if they actually exist in the underlying (basic) table.
For this example, the fooTable will have three underlying basic entries (fooIndex == 1, 2, and 3), with the following activity (for sysUpTime equal 0 to 9):
- fooEntry.N.1 is created at time '0' and most recently updated at time '6' to the value '5'. - fooEntry.N.2 is created at time '0' and most recently updated at time '8' to the value '9'. - fooEntry.N.3 is created at time '3', updated at time '5' to the value '17', and deleted at time '7'.
The following tables show the values that would be returned for MIB walk operations with various TimeFilter values, done at different times. An application issues a retrieval request at time 'T', with a TimeFilter value, 'N' (typically set to a lower value, such as the value of sysUpTime at the last polling cycle).
The following values would be returned in a MIB walk of fooCounts.N if T equals '0' and N equals '0':
fooCounts.N.I Value
==========================
fooCounts.0.1 0
fooCounts.0.2 0
Note that nothing is returned for fooCounts.0.3, since that entry does not exist at sysUpTime equals '0'.
The following values would be returned in a full (traditional) MIB walk of fooCounts.N if T equals '3' and N equals '0':
fooCounts.N.I Value
=======================
fooCounts.0.1 0
fooCounts.0.2 0
fooCounts.0.3 0
fooCounts.1.3 0
fooCounts.2.3 0
fooCounts.3.3 0
Note that there are no instances for T equals 1 or 2 for the first two values of N, as these entries did not change since they were created at time '0'.
Note that the current value for 'fooCounts.N.3' is returned here, even for values of N less than '3' (when the entry was created). The agent only considers the current existence of an entry in the TimeFilter algorithm, not the time when the entry was created.
Note that the instances 'fooCounts.0.3', 'fooCounts.1.3', and 'fooCounts.2.3' are duplicates and can be suppressed by the agent in a MIB walk.
The following values would be returned in a full (traditional) MIB walk of fooCounts.N if T equals '6' and N equals '3':
fooCounts.N.I Value
=======================
fooCounts.3.1 5
fooCounts.3.3 17
fooCounts.4.1 5
fooCounts.4.3 17
fooCounts.5.1 5
fooCounts.5.3 17
fooCounts.6.1 5
Note that no instances for entry 'fooCounts.N.2' are returned, since it has not changed since time '3'.
Note that all instances except 'fooCounts.5.3' and 'fooCounts.6.1' are duplicates and can be suppressed by the agent in a MIB walk.
The following values would be returned in a full (traditional) MIB walk of fooCounts.N if T equals '9' and N equals '6':
fooCounts.N.I Value
=======================
fooCounts.6.1 5
fooCounts.6.2 9
fooCounts.7.2 9
fooCounts.8.2 9
Note that no instances for entry 'fooCounts.N.3' are returned, since it was deleted at time '7'.
Note that instances 'fooCounts.6.2' and 'fooCounts.7.2' are duplicates and can be suppressed by the agent in a MIB walk. · TimeTicks
A TimeFilter for this entry. See the TimeFilter textual convention in IETF RFC 2021 and http://www.ietf.org/IESG/Implementations/RFC2021-Implementation.txt to see how TimeFilter works. Reference: IETF RFC 2021 section 6
lldpRemLocalPortNum
1.0.8802.1.1.2.1.4.1.1.2
LldpPortNumberEach 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. (1..4096) · Integer32
The index value used to identify the port component (contained in the local chassis with the LLDP agent) associated with this entry. The lldpRemLocalPortNum identifies the port on which the remote system information is received.
The value of this object is used as a port index to the lldpRemTable.
lldpRemIndex
1.0.8802.1.1.2.1.4.1.1.3
Integer32 (1..2147483647)
This object represents an arbitrary local integer value used by this agent to identify a particular connection instance, unique only for the indicated remote system.
An agent is encouraged to assign monotonically increasing index values to new entries, starting with one, after each reboot. It is considered unlikely that the lldpRemIndex will wrap between reboots.
lldpRemChassisIdSubtype
1.0.8802.1.1.2.1.4.1.1.4
LldpChassisIdSubtype1 = chassisComponent2 = interfaceAlias3 = portComponent4 = macAddress5 = networkAddress6 = interfaceName7 = localThis TC describes the source of a chassis identifier.
The enumeration 'chassisComponent(1)' represents a chassis identifier based on the value of entPhysicalAlias object (defined in IETF RFC 2737) for a chassis component (i.e., an entPhysicalClass value of 'chassis(3)').
The enumeration 'interfaceAlias(2)' represents a chassis identifier based on the value of ifAlias object (defined in IETF RFC 2863) for an interface on the containing chassis.
The enumeration 'portComponent(3)' represents a chassis identifier based on the value of entPhysicalAlias object (defined in IETF RFC 2737) for a port or backplane component (i.e., entPhysicalClass value of 'port(10)' or 'backplane(4)'), within the containing chassis.
The enumeration 'macAddress(4)' represents a chassis identifier based on the value of a unicast source address (encoded in network byte order and IEEE 802.3 canonical bit order), of a port on the containing chassis as defined in IEEE Std 802-2001.
The enumeration 'networkAddress(5)' represents a chassis identifier based on a network address, associated with a particular chassis. The encoded address is actually composed of two fields. The first field is a single octet, representing the IANA AddressFamilyNumbers value for the specific address type, and the second field is the network address value.
The enumeration 'interfaceName(6)' represents a chassis identifier based on the value of ifName object (defined in IETF RFC 2863) for an interface on the containing chassis.
The enumeration 'local(7)' represents a chassis identifier based on a locally defined value. · Integer32
The type of encoding used to identify the chassis associated with the remote system. Reference: IEEE 802.1AB-2005 9.5.2.2
lldpRemChassisId
1.0.8802.1.1.2.1.4.1.1.5
LldpChassisIdThis TC describes the format of a chassis identifier string. Objects of this type are always used with an associated LldpChassisIdSubtype object, which identifies the format of the particular LldpChassisId object instance.
If the associated LldpChassisIdSubtype object has a value of 'chassisComponent(1)', then the octet string identifies a particular instance of the entPhysicalAlias object (defined in IETF RFC 2737) for a chassis component (i.e., an entPhysicalClass value of 'chassis(3)').
If the associated LldpChassisIdSubtype object has a value of 'interfaceAlias(2)', then the octet string identifies a particular instance of the ifAlias object (defined in IETF RFC 2863) for an interface on the containing chassis. If the particular ifAlias object does not contain any values, another chassis identifier type should be used.
If the associated LldpChassisIdSubtype object has a value of 'portComponent(3)', then the octet string identifies a particular instance of the entPhysicalAlias object (defined in IETF RFC 2737) for a port or backplane component within the containing chassis.
If the associated LldpChassisIdSubtype object has a value of 'macAddress(4)', then this string identifies a particular unicast source address (encoded in network byte order and IEEE 802.3 canonical bit order), of a port on the containing chassis as defined in IEEE Std 802-2001.
If the associated LldpChassisIdSubtype object has a value of 'networkAddress(5)', then this string identifies a particular network address, encoded in network byte order, associated with one or more ports on the containing chassis. The first octet contains the IANA Address Family Numbers enumeration value for the specific address type, and octets 2 through N contain the network address value in network byte order.
If the associated LldpChassisIdSubtype object has a value of 'interfaceName(6)', then the octet string identifies a particular instance of the ifName object (defined in IETF RFC 2863) for an interface on the containing chassis. If the particular ifName object does not contain any values, another chassis identifier type should be used.
If the associated LldpChassisIdSubtype object has a value of 'local(7)', then this string identifies a locally assigned Chassis ID. SIZE (1..255) · OCTET STRING
The string value used to identify the chassis component associated with the remote system. Reference: IEEE 802.1AB-2005 9.5.2.3
lldpRemPortIdSubtype
1.0.8802.1.1.2.1.4.1.1.6
LldpPortIdSubtype1 = interfaceAlias2 = portComponent3 = macAddress4 = networkAddress5 = interfaceName6 = agentCircuitId7 = localThis TC describes the source of a particular type of port identifier used in the LLDP MIB.
The enumeration 'interfaceAlias(1)' represents a port identifier based on the ifAlias MIB object, defined in IETF RFC 2863.
The enumeration 'portComponent(2)' represents a port identifier based on the value of entPhysicalAlias (defined in IETF RFC 2737) for a port component (i.e., entPhysicalClass value of 'port(10)'), within the containing chassis.
The enumeration 'macAddress(3)' represents a port identifier based on a unicast source address (encoded in network byte order and IEEE 802.3 canonical bit order), which has been detected by the agent and associated with a particular port (IEEE Std 802-2001).
The enumeration 'networkAddress(4)' represents a port identifier based on a network address, detected by the agent and associated with a particular port.
The enumeration 'interfaceName(5)' represents a port identifier based on the ifName MIB object, defined in IETF RFC 2863.
The enumeration 'agentCircuitId(6)' represents a port identifier based on the agent-local identifier of the circuit (defined in RFC 3046), detected by the agent and associated with a particular port.
The enumeration 'local(7)' represents a port identifier based on a value locally assigned. · Integer32
The type of port identifier encoding used in the associated 'lldpRemPortId' object. Reference: IEEE 802.1AB-2005 9.5.3.2
lldpRemPortId
1.0.8802.1.1.2.1.4.1.1.7
LldpPortIdThis TC describes the format of a port identifier string. Objects of this type are always used with an associated LldpPortIdSubtype object, which identifies the format of the particular LldpPortId object instance.
If the associated LldpPortIdSubtype object has a value of 'interfaceAlias(1)', then the octet string identifies a particular instance of the ifAlias object (defined in IETF RFC 2863). If the particular ifAlias object does not contain any values, another port identifier type should be used.
If the associated LldpPortIdSubtype object has a value of 'portComponent(2)', then the octet string identifies a particular instance of the entPhysicalAlias object (defined in IETF RFC 2737) for a port or backplane component.
If the associated LldpPortIdSubtype object has a value of 'macAddress(3)', then this string identifies a particular unicast source address (encoded in network byte order and IEEE 802.3 canonical bit order) associated with the port (IEEE Std 802-2001).
If the associated LldpPortIdSubtype object has a value of 'networkAddress(4)', then this string identifies a network address associated with the port. The first octet contains the IANA AddressFamilyNumbers enumeration value for the specific address type, and octets 2 through N contain the networkAddress address value in network byte order.
If the associated LldpPortIdSubtype object has a value of 'interfaceName(5)', then the octet string identifies a particular instance of the ifName object (defined in IETF RFC 2863). If the particular ifName object does not contain any values, another port identifier type should be used.
If the associated LldpPortIdSubtype object has a value of 'agentCircuitId(6)', then this string identifies a agent-local identifier of the circuit (defined in RFC 3046).
If the associated LldpPortIdSubtype object has a value of 'local(7)', then this string identifies a locally assigned port ID. SIZE (1..255) · OCTET STRING
The string value used to identify the port component associated with the remote system. Reference: IEEE 802.1AB-2005 9.5.3.3
lldpRemPortDesc
1.0.8802.1.1.2.1.4.1.1.8
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t
The string value used to identify the description of the given port associated with the remote system. Reference: IEEE 802.1AB-2005 9.5.5.2
lldpRemSysName
1.0.8802.1.1.2.1.4.1.1.9
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t
The string value used to identify the system name of the remote system. Reference: IEEE 802.1AB-2005 9.5.6.2
lldpRemSysDesc
1.0.8802.1.1.2.1.4.1.1.10
SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form.
To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279].
Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited.
The use of control codes should be avoided.
When it is necessary to represent a newline, the control code sequence CR LF should be used.
The use of leading or trailing white space should be avoided.
For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided.
For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding.
UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding.
Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416].
Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t
The string value used to identify the system description of the remote system. Reference: IEEE 802.1AB-2005 9.5.7.2
lldpRemSysCapSupported
1.0.8802.1.1.2.1.4.1.1.11
LldpSystemCapabilitiesMapThis TC describes the system capabilities.
The bit 'other(0)' indicates that the system has capabilities other than those listed below.
The bit 'repeater(1)' indicates that the system has repeater capability.
The bit 'bridge(2)' indicates that the system has bridge capability.
The bit 'wlanAccessPoint(3)' indicates that the system has WLAN access point capability.
The bit 'router(4)' indicates that the system has router capability.
The bit 'telephone(5)' indicates that the system has telephone capability.
The bit 'docsisCableDevice(6)' indicates that the system has DOCSIS Cable Device capability (IETF RFC 2669 & 2670).
The bit 'stationOnly(7)' indicates that the system has only station capability and nothing else. · BITS
The bitmap value used to identify which system capabilities are supported on the remote system. Reference: IEEE 802.1AB-2005 9.5.8.1
lldpRemSysCapEnabled
1.0.8802.1.1.2.1.4.1.1.12
LldpSystemCapabilitiesMapThis TC describes the system capabilities.
The bit 'other(0)' indicates that the system has capabilities other than those listed below.
The bit 'repeater(1)' indicates that the system has repeater capability.
The bit 'bridge(2)' indicates that the system has bridge capability.
The bit 'wlanAccessPoint(3)' indicates that the system has WLAN access point capability.
The bit 'router(4)' indicates that the system has router capability.
The bit 'telephone(5)' indicates that the system has telephone capability.
The bit 'docsisCableDevice(6)' indicates that the system has DOCSIS Cable Device capability (IETF RFC 2669 & 2670).
The bit 'stationOnly(7)' indicates that the system has only station capability and nothing else. · BITS
The bitmap value used to identify which system capabilities are enabled on the remote system. Reference: IEEE 802.1AB-2005 9.5.8.2
This table contains one or more rows per management address information on the remote system learned on a particular port contained in the local chassis known to this agent.
lldpRemManAddrSubtype
1.0.8802.1.1.2.1.4.2.1.1
AddressFamilyNumbers0 = other1 = ipV42 = ipV63 = nsap4 = hdlc5 = bbn18226 = all8027 = e1638 = e1649 = f6910 = x12111 = ipx12 = appleTalk13 = decnetIV14 = banyanVines15 = e164withNsap16 = dns17 = distinguishedName18 = asNumber19 = xtpOverIpv420 = xtpOverIpv621 = xtpNativeModeXTP22 = fibreChannelWWPN23 = fibreChannelWWNN24 = gwid25 = afi26 = mplsTpSectionEndpointIdentifier27 = mplsTpLspEndpointIdentifier28 = mplsTpPseudowireEndpointIdentifier16384 = eigrpCommonServiceFamily16385 = eigrpIpv4ServiceFamily16386 = eigrpIpv6ServiceFamily16387 = lispCanonicalAddressFormat16388 = bgpLs16389 = fortyeightBitMac16390 = sixtyfourBitMac16391 = oui16392 = mac2416393 = mac4016394 = ipv66416395 = rBridgePortID16396 = trillNickname16397 = universallyUniqueIdentifier65535 = reservedThe definition of this textual convention with the addition of newly assigned values is published periodically by the IANA, in either the Assigned Numbers RFC, or some derivative of it specific to Internet Network Management number assignments. (The latest arrangements can be obtained by contacting the IANA.)
The enumerations are described as:
other(0), -- none of the following
ipV4(1), -- IP Version 4
ipV6(2), -- IP Version 6
nsap(3), -- NSAP
hdlc(4), -- (8-bit multidrop)
bbn1822(5),
all802(6), -- (includes all 802 media
-- plus Ethernet 'canonical format')
e163(7),
e164(8), -- (SMDS, Frame Relay, ATM)
f69(9), -- (Telex)
x121(10), -- (X.25, Frame Relay)
ipx(11), -- IPX (Internet Protocol Exchange)
appleTalk(12), -- Apple Talk
decnetIV(13), -- DEC Net Phase IV
banyanVines(14), -- Banyan Vines
e164withNsap(15), -- (E.164 with NSAP format subaddress)
dns(16), -- (Domain Name System)
distinguishedName(17), -- (Distinguished Name, per X.500) asNumber(18), -- (16-bit quantity, per the AS number space)
xtpOverIpv4(19), -- XTP over IP version 4
xtpOverIpv6(20), -- XTP over IP version 6
xtpNativeModeXTP(21), -- XTP native mode XTP
fibreChannelWWPN(22), -- Fibre Channel World-Wide Port Name
fibreChannelWWNN(23), -- Fibre Channel World-Wide Node Name
gwid(24), -- Gateway Identifier
afi(25), -- AFI for L2VPN information
mplsTpSectionEndpointIdentifier(26), -- MPLS-TP Section Endpoint Identifier
mplsTpLspEndpointIdentifier(27), -- MPLS-TP LSP Endpoint Identifier
mplsTpPseudowireEndpointIdentifier(28), -- MPLS-TP Pseudowire Endpoint Identifier
eigrpCommonServiceFamily(16384), -- EIGRP Common Service Family
eigrpIpv4ServiceFamily(16385), -- EIGRP IPv4 Service Family
eigrpIpv6ServiceFamily(16386), -- EIGRP IPv6 Service Family
lispCanonicalAddressFormat(16387), -- LISP Canonical Address Format (LCAF)
bgpLs(16388), -- BGP-LS
fortyeightBitMacBitMac(16389), -- 48-bit MAC
sixtyfourBitMac(16390), -- 64-bit MAC
oui(16391), -- OUI
mac24(16392), -- MAC/24
mac40(16393), -- MAC/40
ipv664(16394), -- IPv6/64
rBridgePortID(16395), -- RBridge Port ID
trillNickname(16396), -- TRILL Nickname
universallyUniqueIdentifier(16397), -- Universally Unique Identifier (UUID)
reserved(65535)
Requests for new values should be made to IANA via email (iana&iana.org). · Integer32
The type of management address identifier encoding used in the associated 'lldpRemManagmentAddr' object. Reference: IEEE 802.1AB-2005 9.5.9.3
lldpRemManAddr
1.0.8802.1.1.2.1.4.2.1.2
LldpManAddressThe value of a management address associated with the LLDP agent that may be used to reach higher layer entities to assist discovery by network management.
It should be noted that appropriate security credentials, such as SNMP engineId, may be required to access the LLDP agent using a management address. These necessary credentials should be known by the network management and the objects associated with the credentials are not included in the LLDP agent. SIZE (1..31) · OCTET STRING
The string value used to identify the management address component associated with the remote system. The purpose of this address is to contact the management entity. Reference: IEEE 802.1AB-2005 9.5.9.4
lldpRemManAddrIfSubtype
1.0.8802.1.1.2.1.4.2.1.3
LldpManAddrIfSubtype1 = unknown2 = ifIndex3 = systemPortNumberThis TC describes the basis of a particular type of interface associated with the management address.
The enumeration 'unknown(1)' represents the case where the interface is not known.
The enumeration 'ifIndex(2)' represents interface identifier based on the ifIndex MIB object.
The enumeration 'systemPortNumber(3)' represents interface identifier based on the system port numbering convention.Reference: IEEE 802.1AB-2005 9.5.9.5 · Integer32
The enumeration value that identifies the interface numbering method used for defining the interface number, associated with the remote system. Reference: IEEE 802.1AB-2005 9.5.9.5
lldpRemManAddrIfId
1.0.8802.1.1.2.1.4.2.1.4
Integer32
The integer value used to identify the interface number regarding the management address component associated with the remote system. Reference: IEEE 802.1AB-2005 9.5.9.6
lldpRemManAddrOID
1.0.8802.1.1.2.1.4.2.1.5
OBJECT IDENTIFIER
The OID value used to identify the type of hardware component or protocol entity associated with the management address advertised by the remote system agent. Reference: IEEE 802.1AB-2005 9.5.9.8
This table contains information about an incoming TLV which is not recognized by the receiving LLDP agent. The TLV may be from a later version of the basic management set.
This table should only contain TLVs that are found in a single LLDP frame. Entries in this table, associated with an MAC service access point (MSAP, the access point for MAC services provided to the LCC sublayer, defined in IEEE 100, which is also identified with a particular lldpRemLocalPortNum, lldpRemIndex pair) are overwritten with most recently received unrecognized TLV from the same MSAP, or they will naturally age out when the rxInfoTTL timer (associated with the MSAP) expires. Reference: IEEE 802.1AB-2005 10.3.2
lldpRemUnknownTLVType
1.0.8802.1.1.2.1.4.3.1.1
Integer32 (9..126)
This object represents the value extracted from the type field of the TLV. Reference: IEEE 802.1AB-2005 10.3.5
lldpRemUnknownTLVInfo
1.0.8802.1.1.2.1.4.3.1.2
OCTET STRING SIZE (0..511)
This object represents the value extracted from the value field of the TLV. Reference: IEEE 802.1AB-2005 10.3.5
This table contains one or more rows per physical network connection which advertises the organizationally defined information.
Note that this table contains one or more rows of organizationally defined information that is not recognized by the local agent.
If the local system is capable of recognizing any organizationally defined information, appropriate extension MIBs from the organization should be used for information retrieval.
lldpRemOrgDefInfoOUI
1.0.8802.1.1.2.1.4.4.1.1
OCTET STRING SIZE (3)
The Organizationally Unique Identifier (OUI), as defined in IEEE std 802-2001, is a 24 bit (three octets) globally unique assigned number referenced by various standards, of the information received from the remote system. Reference: IEEE 802.1AB-2005 9.5.1.3
lldpRemOrgDefInfoSubtype
1.0.8802.1.1.2.1.4.4.1.2
Integer32 (1..255)
The integer value used to identify the subtype of the organizationally defined information received from the remote system.
The subtype value is required to identify different instances of organizationally defined information that could not be retrieved without a unique identifier that indicates the particular type of information contained in the information string. Reference: IEEE 802.1AB-2005 9.5.1.4
lldpRemOrgDefInfoIndex
1.0.8802.1.1.2.1.4.4.1.3
Integer32 (1..2147483647)
This object represents an arbitrary local integer value used by this agent to identify a particular unrecognized organizationally defined information instance, unique only for the lldpRemOrgDefInfoOUI and lldpRemOrgDefInfoSubtype from the same remote system.
An agent is encouraged to assign monotonically increasing index values to new entries, starting with one, after each reboot. It is considered unlikely that the lldpRemOrgDefInfoIndex will wrap between reboots.
lldpRemOrgDefInfo
1.0.8802.1.1.2.1.4.4.1.4
OCTET STRING SIZE (0..507)
The string value used to identify the organizationally defined information of the remote system. The encoding for this object should be as defined for SnmpAdminString TC. Reference: IEEE 802.1AB-2005 9.5.1.5
Trap details
lldpRemTablesChange
1.0.8802.1.1.2.0.0.1
A lldpRemTablesChange notification is sent when the value of lldpStatsRemTableLastChangeTime changes. It can be utilized by an NMS to trigger LLDP remote systems table maintenance polls.
Note that transmission of lldpRemTablesChange notifications are throttled by the agent, as specified by the 'lldpNotificationInterval' object.
lldpStatsRemTablesInserts
1.0.8802.1.1.2.1.2.2
ZeroBasedCounter32This TC describes an object that counts events with the following semantics: objects of this type will be set to zero(0) on creation and will thereafter count appropriate events, wrapping back to zero(0) when the value 2^32 is reached.
Provided that an application discovers the new object within the minimum time to wrap, it can use the initial value as a delta since it last polled the table of which this object is part. It is important for a management station to be aware of this minimum time and the actual time between polls, and to discard data if the actual time is too long or there is no defined minimum time.
Typically, this TC is used in tables where the INDEX space is constantly changing and/or the TimeFilter mechanism is in use. · Gauge32 · table entries
The number of times the complete set of information advertised by a particular MSAP has been inserted into tables contained in lldpRemoteSystemsData and lldpExtensions objects.
The complete set of information received from a particular MSAP should be inserted into related tables. If partial information cannot be inserted for a reason such as lack of resources, all of the complete set of information should be removed.
This counter should be incremented only once after the complete set of information is successfully recorded in all related tables. Any failures during inserting information set which result in deletion of previously inserted information should not trigger any changes in lldpStatsRemTablesInserts since the insert is not completed yet or or in lldpStatsRemTablesDeletes, since the deletion would only be a partial deletion. If the failure was the result of lack of resources, the lldpStatsRemTablesDrops counter should be incremented once.
lldpStatsRemTablesDeletes
1.0.8802.1.1.2.1.2.3
ZeroBasedCounter32This TC describes an object that counts events with the following semantics: objects of this type will be set to zero(0) on creation and will thereafter count appropriate events, wrapping back to zero(0) when the value 2^32 is reached.
Provided that an application discovers the new object within the minimum time to wrap, it can use the initial value as a delta since it last polled the table of which this object is part. It is important for a management station to be aware of this minimum time and the actual time between polls, and to discard data if the actual time is too long or there is no defined minimum time.
Typically, this TC is used in tables where the INDEX space is constantly changing and/or the TimeFilter mechanism is in use. · Gauge32 · table entries
The number of times the complete set of information advertised by a particular MSAP has been deleted from tables contained in lldpRemoteSystemsData and lldpExtensions objects.
This counter should be incremented only once when the complete set of information is completely deleted from all related tables. Partial deletions, such as deletion of rows associated with a particular MSAP from some tables, but not from all tables are not allowed, thus should not change the value of this counter.
lldpStatsRemTablesDrops
1.0.8802.1.1.2.1.2.4
ZeroBasedCounter32This TC describes an object that counts events with the following semantics: objects of this type will be set to zero(0) on creation and will thereafter count appropriate events, wrapping back to zero(0) when the value 2^32 is reached.
Provided that an application discovers the new object within the minimum time to wrap, it can use the initial value as a delta since it last polled the table of which this object is part. It is important for a management station to be aware of this minimum time and the actual time between polls, and to discard data if the actual time is too long or there is no defined minimum time.
Typically, this TC is used in tables where the INDEX space is constantly changing and/or the TimeFilter mechanism is in use. · Gauge32 · table entries
The number of times the complete set of information advertised by a particular MSAP could not be entered into tables contained in lldpRemoteSystemsData and lldpExtensions objects because of insufficient resources.
lldpStatsRemTablesAgeouts
1.0.8802.1.1.2.1.2.5
ZeroBasedCounter32This TC describes an object that counts events with the following semantics: objects of this type will be set to zero(0) on creation and will thereafter count appropriate events, wrapping back to zero(0) when the value 2^32 is reached.
Provided that an application discovers the new object within the minimum time to wrap, it can use the initial value as a delta since it last polled the table of which this object is part. It is important for a management station to be aware of this minimum time and the actual time between polls, and to discard data if the actual time is too long or there is no defined minimum time.
Typically, this TC is used in tables where the INDEX space is constantly changing and/or the TimeFilter mechanism is in use. · Gauge32
The number of times the complete set of information advertised by a particular MSAP has been deleted from tables contained in lldpRemoteSystemsData and lldpExtensions objects because the information timeliness interval has expired.
This counter should be incremented only once when the complete set of information is completely invalidated (aged out) from all related tables. Partial aging, similar to deletion case, is not allowed, and thus, should not change the value of this counter.