lldpMessageTxInterval |
The interval (in seconds) at which LLDP frames are transmitted on behalf of this LLDP agent. |
lldpMessageTx HoldMultiplier
|
The time-to-live value expressed as a multiple of the object. The actual time-to-live value used in LLDP frames, transmitted
on behalf of this LLDP agent, is 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, the value 120 is encoded in the TTL field in the LLDP header.
|
lldpReinitDelay |
The lldpReinitDelay indicates the delay (in seconds) from when the LLDP Port AdminStatus of a particular port is disabled
until reinitialization begins.
|
lldpTxDelay |
The lldpTxDelay indicates the delay (in seconds) between successive LLDP frame transmissions initiated by value or 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)
|
lldpNotificationInterval |
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, these trap-events must be suppressed by
the agent. An NMS must periodically check the value of lldpStatsRemTableLastChangeTime to detect any missed lldpRemTablesChange
notification-events, for example, due to throttling or transmission loss. If notification transmission is enabled for particular
ports, the suggested default throttling period is 5 seconds.
|
RemTablesLast ChangeTime
|
The value of the sysUpTime object (defined in IETF RFC 3418) at the time an entry is created, modified, or deleted 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.
|
RemTablesInserts |
The number of times the complete set of information advertised by a particular MSAP is inserted into tables contained in lldpRemoteSystemsData
and lldpExtensions objects. The complete set of information received from a particular MSAP is 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 is
removed. This counter is incremented only once after the complete set of information is successfully recorded in all related
tables. Any failures occurring during insertion of the information set, which result in deletion of previously inserted information,
do not trigger any changes in lldpStatsRemTablesInserts because the insert is not completed yet or in lldpStatsRemTablesDeletes,
because the deletion is only a partial deletion. If the failure is the result of a lack of resources, the lldpStatsRemTablesDrops
counter is incremented once.
|
RemTablesDeletes |
The number of times the complete set of information advertised by a particular MSAP is deleted from tables contained in lldpRemoteSystemsData
and lldpExtensions objects. This counter is incremented only once when the complete set of information is completely deleted
from all related tables. Partial deletions, such as a deletion of rows associated with a particular MSAP, from some tables,
but not from all tables, are not allowed, and thus, do not change the value of this counter.
|
RemTablesDrops |
The number of times the complete set of information advertised by a particular MSAP can not be entered into tables contained
in lldpRemoteSystemsData and lldpExtensions objects because of insufficient resources.
|
RemTablesAgeouts |
The number of times the complete set of information advertised by a particular MSAP is deleted from tables contained in lldpRemoteSystemsData
and lldpExtensions objects because the information timeliness interval has expired. This counter is 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, does not change the value of this counter.
|
FastStartRepeatCount |
The number of times the fast start LLDPDU is sent during the activation of the fast start mechanism defined by LLDP-MED. |