LLDP-MIB
Management Information Base module for LLDP configuration, statistics, local system data and remote systems data components.
Copyright (C) IEEE (2004). This version of this MIB module is published as subclause 12.1 of IEEE Std 802.1AB-2004; see the standard itself for full legal notices.
Main OID:
lldpMIB.1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2
96
Objects
Active
Status
6
Dependencies
Imported Objects
Objects
96 total| Object Name |
|---|
lldpMIBManagement Information Base module for LLDP configuration,
statistics, local system data and remote systems data
components.
Copyright (C) IEEE (2004). This version of this MIB module
is published as subclause 12.1 of IEEE Std 802.1AB-2004;
see the standard itself for full legal notices. MODULE-IDENTITY .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2 |
lldpNotifications OBJECT IDENTIFIER .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.0 |
lldpNotificationPrefix OBJECT IDENTIFIER .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.0.0 |
lldpRemTablesChangeA 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. NOTIFICATION-TYPE .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.0.0.1 |
lldpObjects OBJECT IDENTIFIER .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1 |
lldpConfiguration OBJECT IDENTIFIER .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.1 |
lldpMessageTxIntervalThe 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.ro Integer32 .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.1.1 |
lldpMessageTxHoldMultiplierThe 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.ro Integer32 .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.1.2 |
lldpReinitDelayThe 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.ro Integer32 .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.1.3 |
lldpTxDelayThe 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.ro Integer32 .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.1.4 |
lldpNotificationIntervalThis 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.ro Integer32 .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.1.5 |
lldpPortConfigTableThe table that controls LLDP frame transmission on individual
ports. SEQUENCE OF LldpPortConfigEntry .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.1.6 |
lldpPortConfigEntryLLDP configuration information for a particular port.
This configuration parameter controls the transmission and
the reception of LLDP frames on those ports whose rows are
created in this table. LldpPortConfigEntry .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.1.6.1 |
lldpPortConfigPortNumThe 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. LldpPortNumber .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.1.6.1.1 |
lldpPortConfigAdminStatusThe 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.ro Enumeration .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.1.6.1.2 |
lldpPortConfigNotificationEnableThe 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.ro TruthValue (SNMPv2-TC) .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.1.6.1.3 |
lldpPortConfigTLVsTxEnableThe 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.ro Bits .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.1.6.1.4 |
lldpConfigManAddrTableThe table that controls selection of LLDP management address
TLV instances to be transmitted on individual ports. SEQUENCE OF LldpConfigManAddrEntry .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.1.7 |
lldpConfigManAddrEntryLLDP configuration information that specifies the set
of ports (represented as a PortList) on which the local
system management address instance will be transmitted.
This configuration object augments the lldpLocManAddrEntry,
therefore it is only present along with the management
address instance contained in the associated
lldpLocManAddrEntry entry.
Each active lldpConfigManAddrEntry must be restored from
non-volatile and re-created (along with the corresponding
lldpLocManAddrEntry) after a re-initialization of the
management system. LldpConfigManAddrEntry .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.1.7.1 |
lldpConfigManAddrPortsTxEnableA 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.ro LldpPortList .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.1.7.1.1 |
lldpStatistics OBJECT IDENTIFIER .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.2 |
lldpStatsRemTablesLastChangeTimeThe 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.ro TimeStamp (SNMPv2-TC) .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.2.1 |
lldpStatsRemTablesInsertsThe 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 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.ro ZeroBasedCounter32 UNITS "table entries" .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.2.2 |
lldpStatsRemTablesDeletesThe 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.ro ZeroBasedCounter32 UNITS "table entries" .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.2.3 |
lldpStatsRemTablesDropsThe 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.ro ZeroBasedCounter32 UNITS "table entries" .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.2.4 |
lldpStatsRemTablesAgeoutsThe 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.ro ZeroBasedCounter32 (RMON2-MIB) .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.2.5 |
lldpStatsTxPortTableA 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)'. SEQUENCE OF LldpStatsTxPortEntry .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.2.6 |
lldpStatsTxPortEntryLLDP frame transmission statistics for a particular port.
The port must be contained in the same chassis as the
LLDP agent.
All counter values in a particular entry shall be
maintained on a continuing basis and shall not be deleted
upon expiration of rxInfoTTL timing counters in the LLDP
remote systems MIB of the receipt of a shutdown frame from
a remote LLDP agent.
All statistical counters associated with a particular
port on the local LLDP agent become frozen whenever the
adminStatus is disabled for the same port. LldpStatsTxPortEntry .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.2.6.1 |
lldpStatsTxPortNumThe 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. LldpPortNumber .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.2.6.1.1 |
lldpStatsTxPortFramesTotalThe number of LLDP frames transmitted by this LLDP agent
on the indicated port.ro Counter32 .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.2.6.1.2 |
lldpStatsRxPortTableA 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)'. SEQUENCE OF LldpRxStatsPortEntry .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.2.7 |
lldpStatsRxPortEntryLLDP frame reception statistics for a particular port.
The port must be contained in the same chassis as the
LLDP agent.
All counter values in a particular entry shall be
maintained on a continuing basis and shall not be deleted
upon expiration of rxInfoTTL timing counters in the LLDP
remote systems MIB of the receipt of a shutdown frame from
a remote LLDP agent.
All statistical counters associated with a particular
port on the local LLDP agent become frozen whenever the
adminStatus is disabled for the same port. LldpRxStatsPortEntry .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.2.7.1 |
lldpStatsRxPortNumThe 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. LldpPortNumber .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.2.7.1.1 |
lldpStatsRxPortFramesDiscardedTotalThe 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.ro Counter32 .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.2.7.1.2 |
lldpStatsRxPortFramesErrorsThe number of invalid LLDP frames received by this LLDP
agent on the indicated port, while this LLDP agent is enabled.ro Counter32 .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.2.7.1.3 |
lldpStatsRxPortFramesTotalThe number of valid LLDP frames received by this LLDP agent
on the indicated port, while this LLDP agent is enabled.ro Counter32 .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.2.7.1.4 |
lldpStatsRxPortTLVsDiscardedTotalThe number of LLDP TLVs discarded for any reason by this LLDP
agent on the indicated port.ro Counter32 .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.2.7.1.5 |
lldpStatsRxPortTLVsUnrecognizedTotalThe 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.ro Counter32 .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.2.7.1.6 |
lldpStatsRxPortAgeoutsTotalThe 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.ro ZeroBasedCounter32 (RMON2-MIB) .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.2.7.1.7 |
lldpLocalSystemData OBJECT IDENTIFIER .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.3 |
lldpLocChassisIdSubtypeThe type of encoding used to identify the chassis
associated with the local system.ro LldpChassisIdSubtype .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.3.1 |
lldpLocChassisIdThe string value used to identify the chassis component
associated with the local system.ro LldpChassisId .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.3.2 |
lldpLocSysNameThe 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.ro SnmpAdminString .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.3.3 |
lldpLocSysDescThe 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.ro SnmpAdminString .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.3.4 |
lldpLocSysCapSupportedThe bitmap value used to identify which system capabilities
are supported on the local system.ro LldpSystemCapabilitiesMap .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.3.5 |
lldpLocSysCapEnabledThe bitmap value used to identify which system capabilities
are enabled on the local system.ro LldpSystemCapabilitiesMap .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.3.6 |
lldpLocPortTableThis table contains one or more rows per port information
associated with the local system known to this agent. SEQUENCE OF LldpLocPortEntry .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.3.7 |
lldpLocPortEntryInformation about a particular port component.
Entries may be created and deleted in this table by the
agent. LldpLocPortEntry .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.3.7.1 |
lldpLocPortNumThe 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. LldpPortNumber .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.3.7.1.1 |
lldpLocPortIdSubtypeThe type of port identifier encoding used in the associated
'lldpLocPortId' object.ro LldpPortIdSubtype .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.3.7.1.2 |
lldpLocPortIdThe string value used to identify the port component
associated with a given port in the local system.ro LldpPortId .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.3.7.1.3 |
lldpLocPortDescThe string value used to identify the IEEE 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.ro SnmpAdminString .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.3.7.1.4 |
lldpLocManAddrTableThis table contains management address information on the
local system known to this agent. SEQUENCE OF LldpLocManAddrEntry .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.3.8 |
lldpLocManAddrEntryManagement address information about a particular chassis
component. There may be multiple management addresses
configured on the system identified by a particular
lldpLocChassisId. Each management address should have
distinct 'management address type' (lldpLocManAddrSubtype) and
'management address' (lldpLocManAddr.)
Entries may be created and deleted in this table by the
agent. LldpLocManAddrEntry .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.3.8.1 |
lldpLocManAddrSubtypeThe type of management address identifier encoding used in
the associated 'lldpLocManagmentAddr' object. AddressFamilyNumbers (IANA-ADDRESS-FAMILY-NUMBERS-MIB) .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.3.8.1.1 |
lldpLocManAddrThe 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. LldpManAddress .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.3.8.1.2 |
lldpLocManAddrLenThe 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 address.ro Integer32 .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.3.8.1.3 |
lldpLocManAddrIfSubtypeThe enumeration value that identifies the interface numbering
method used for defining the interface number, associated
with the local system.ro LldpManAddrIfSubtype .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.3.8.1.4 |
lldpLocManAddrIfIdThe integer value used to identify the interface number
regarding the management address component associated with
the local system.ro Integer32 .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.3.8.1.5 |
lldpLocManAddrOIDThe OID value used to identify the type of hardware component
or protocol entity associated with the management address
advertised by the local system agent.ro OBJECT IDENTIFIER .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.3.8.1.6 |
lldpRemoteSystemsData OBJECT IDENTIFIER .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4 |
lldpRemTableThis 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. SEQUENCE OF LldpRemEntry .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.1 |
lldpRemEntryInformation about a particular physical network connection.
Entries may be created and deleted in this table by the agent,
if a physical topology discovery process is active. LldpRemEntry .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.1.1 |
lldpRemTimeMarkA 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. TimeFilter (RMON2-MIB) .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.1.1.1 |
lldpRemLocalPortNumThe 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. LldpPortNumber .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.1.1.2 |
lldpRemIndexThis 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. Integer32 .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.1.1.3 |
lldpRemChassisIdSubtypeThe type of encoding used to identify the chassis associated
with the remote system.ro LldpChassisIdSubtype .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.1.1.4 |
lldpRemChassisIdThe string value used to identify the chassis component
associated with the remote system.ro LldpChassisId .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.1.1.5 |
lldpRemPortIdSubtypeThe type of port identifier encoding used in the associated
'lldpRemPortId' object.ro LldpPortIdSubtype .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.1.1.6 |
lldpRemPortIdThe string value used to identify the port component
associated with the remote system.ro LldpPortId .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.1.1.7 |
lldpRemPortDescThe string value used to identify the description of
the given port associated with the remote system.ro SnmpAdminString .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.1.1.8 |
lldpRemSysNameThe string value used to identify the system name of the
remote system.ro SnmpAdminString .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.1.1.9 |
lldpRemSysDescThe string value used to identify the system description
of the remote system.ro SnmpAdminString .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.1.1.10 |
lldpRemSysCapSupportedThe bitmap value used to identify which system capabilities
are supported on the remote system.ro LldpSystemCapabilitiesMap .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.1.1.11 |
lldpRemSysCapEnabledThe bitmap value used to identify which system capabilities
are enabled on the remote system.ro LldpSystemCapabilitiesMap .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.1.1.12 |
lldpRemManAddrTableThis 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. SEQUENCE OF LldpRemManAddrEntry .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.2 |
lldpRemManAddrEntryManagement address information about a particular chassis
component. There may be multiple management addresses
configured on the remote system identified by a particular
lldpRemIndex whose information is received on
lldpRemLocalPortNum of the local system. Each management
address should have distinct 'management address
type' (lldpRemManAddrSubtype) and 'management address'
(lldpRemManAddr.)
Entries may be created and deleted in this table by the
agent. LldpRemManAddrEntry .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.2.1 |
lldpRemManAddrSubtypeThe type of management address identifier encoding used in
the associated 'lldpRemManagmentAddr' object. AddressFamilyNumbers (IANA-ADDRESS-FAMILY-NUMBERS-MIB) .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.2.1.1 |
lldpRemManAddrThe 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. LldpManAddress .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.2.1.2 |
lldpRemManAddrIfSubtypeThe enumeration value that identifies the interface numbering
method used for defining the interface number, associated
with the remote system.ro LldpManAddrIfSubtype .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.2.1.3 |
lldpRemManAddrIfIdThe integer value used to identify the interface number
regarding the management address component associated with
the remote system.ro Integer32 .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.2.1.4 |
lldpRemManAddrOIDThe OID value used to identify the type of hardware component
or protocol entity associated with the management address
advertised by the remote system agent.ro OBJECT IDENTIFIER .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.2.1.5 |
lldpRemUnknownTLVTableThis 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. SEQUENCE OF LldpRemUnknownTLVEntry .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.3 |
lldpRemUnknownTLVEntryInformation about an unrecognized TLV received from a
physical network connection. Entries may be created and
deleted in this table by the agent, if a physical topology
discovery process is active. LldpRemUnknownTLVEntry .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.3.1 |
lldpRemUnknownTLVTypeThis object represents the value extracted from the type
field of the TLV. Integer32 .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.3.1.1 |
lldpRemUnknownTLVInfoThis object represents the value extracted from the value
field of the TLV.ro OCTET STRING .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.3.1.2 |
lldpRemOrgDefInfoTableThis 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. SEQUENCE OF LldpRemOrgDefInfoEntry .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.4 |
lldpRemOrgDefInfoEntryInformation about the unrecognized organizationally
defined information advertised by the remote system.
The lldpRemTimeMark, lldpRemLocalPortNum, lldpRemIndex,
lldpRemOrgDefInfoOUI, lldpRemOrgDefInfoSubtype, and
lldpRemOrgDefInfoIndex are indexes to this table. If there is
an lldpRemOrgDefInfoEntry associated with a particular remote
system identified by the lldpRemLocalPortNum and lldpRemIndex,
there must be an lldpRemEntry associated with the same
instance (i.e, using same indexes.) When the lldpRemEntry
for the same index is removed from the lldpRemTable, the
associated lldpRemOrgDefInfoEntry should be removed from
the lldpRemOrgDefInfoTable.
Entries may be created and deleted in this table by the
agent. LldpRemOrgDefInfoEntry .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.4.1 |
lldpRemOrgDefInfoOUIThe 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. OCTET STRING .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.4.1.1 |
lldpRemOrgDefInfoSubtypeThe 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. Integer32 .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.4.1.2 |
lldpRemOrgDefInfoIndexThis 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. Integer32 .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.4.1.3 |
lldpRemOrgDefInfoThe 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.ro OCTET STRING .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.4.4.1.4 |
lldpExtensions OBJECT IDENTIFIER .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.1.5 |
lldpConformance OBJECT IDENTIFIER .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.2 |
lldpCompliances OBJECT IDENTIFIER .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.2.1 |
lldpGroups OBJECT IDENTIFIER .1.1.3.6.1.4.1.30631.1.8.1.27.2.0.8802.1.1.3.111.2.802.1.1.1.2.2.2 |
More MIBs from Default
Browse all DefaultMIBs →RC-TLS-MIB
SNMP MIB module
2614 objects→
AVAYA-WLAN-MIB
The AVAYA-WLAN-MIB provides SNMP-based management and monitoring capabilities for Avaya wireless LAN infrastructure, enabling the collection of performance metrics such as access point status, client association counts, signal strength, and radio interface statistics. This module facilitates the tracking of WLAN-specific events and configuration parameters to support network availability and troubleshooting within Avaya wireless deployments.
2022 objects→
VMWARE-NSX-MIB
The VMWARE-NSX-MIB enables SNMP-based monitoring and management of VMware NSX-T Data Center virtual network infrastructure, exposing metrics for logical switches, routers, distributed firewalls, and overlay tunnel states. It facilitates the tracking of Layer 2 through Layer 7 service instances, including access control lists, Quality of Service policies, and virtual network topology changes within the software-defined networking environment.
1035 objects→
923switch.m
Standard SNMP MIB module defining data structures for 923switch.m.
999 objects→
CTATX-MIB
Standard SNMP MIB module defining data structures for CTATX-MIB.
747 objects→
DC-BGP-MIB
SNMP MIB module
652 objects→