tnLldpRemPortIndexTable
TN-LLDP-MIB ·
.1.3.6.1.4.1.7483.6.1.2.59.4.3
Object
table
Note that this table is same as tnLldpRemTable except that the order of two
indices tnLldpRemTimeMark and tnPortPortID are reversed.
This table contains one or more rows per physical network
connection known to this agent. The agent may wish to ensure
that only one tnLldpRemEntry is present for each local port
and destination MAC address,
or it may choose to maintain multiple tnLldpRemEntry rows for
the same local port and destination MAC address.
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. tnLldpStatsRemTablesInserts
b. tnLldpStatsRemTablesDeletes
c. tnLldpStatsRemTablesDrops
d. tnLldpStatsRemTablesAgeouts
e. tnLldpStatsRxPortAgeouts 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
tnLldpStatsRemTablesLastChangeTime 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 tnLldpStatsRemTablesInserts 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 tnLldpStatsRemTablesAgeouts has changed,
then NMS will walk the tnLldpStatsRxPortAgeouts and
compare the new values with previously recorded ones.
For ports whose tnLldpStatsRxPortAgeouts 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.)
tnLldpStatsRemTablesDeletes and tnLldpStatsRemTablesDrops
objects are provided for informational purposes.
Context
- MIB
- TN-LLDP-MIB
- OID
.1.3.6.1.4.1.7483.6.1.2.59.4.3- Type
- table
- Status
- current
- Parent
- tnLldpRemoteSystemsData
- Siblings
- 3
- Children
- 1
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.
Related Objects
Sibling Objects
| Object | Type | Syntax | OID |
|---|---|---|---|
| tnLldpRemTable This table contains one or more rows per physical network
connection known to this agent. The agent may wish to ensure
that only one tnLldpRemEntry is present for each local port
… | table | - | .1.3.6.1.4.1.7483.6.1.2.59.4.1 |
| tnLldpRemManAddrTable 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. | table | - | .1.3.6.1.4.1.7483.6.1.2.59.4.2 |
| tnLldpRemManAddrPortIndexTable Note that this table is same as tnLldpRemManAddrTable except that the order of two
indices tnLldpRemTimeMark and tnPortPortID are reversed.
This table contains one or m… | table | - | .1.3.6.1.4.1.7483.6.1.2.59.4.4 |
Child Objects
| Object | Type | Syntax | OID |
|---|---|---|---|
| tnLldpRemPortIndexEntry Information 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.
… | row | - | .1.3.6.1.4.1.7483.6.1.2.59.4.3.1 |