Automatic link discovery
MPR-e and MSS-1c User Manual 3DB19901EFAA Edition 01 185
If the neighbor is unknown, that is, no entry exists in the remote systems MIB for that
neighbor, the MPR-e creates it.
If the neighbor is known, the MPR-e uses the new information contained in the LLDPDU
to replace the existing entry in the MIB. If there are information elements in the existing
MIB entry for which there are corresponding elements in the received LLDPDU, then those
elements are updated using the received information. Any other information elements in the
existing MIB entry are deleted.
3.11.4.3 — Notifying the SNMP manager
When detecting a new neighbor or a neighbor modification, the MPR-e:
1. Sends optics IM (object deletion and object creation) traps to the SNMP manager to
notify of the destruction or creation of the LLDP MIB entries and stores these events
in its event log.
2. Sends an lldpV2RemTablesChange notification to the manager indicating that
something has changed in the LLDP remote systems MIB associated with that
neighbor.
3.11.4.4 — Number of supported neighbors at a time
The maximum number of neighbors supported at a time is one.
When a neighbor already exists and a new neighbor is discovered, the information related
to the old neighbor is removed from the MPR-e database and the new neighbor takes its
place. The management of the Too Many Neighbors condition described in 9.2.7.7.5 of
802.1AB-2009 applies.
3.11.5 — Transparent relay of nearest non-TPMR bridge and
Nearest customer bridge PDUs
Whether its LLDP configuration is enabled or disabled, the MPR-e processes incoming
Nearest non-TPMR bridge and Nearest Customer bridge LLDPDUs as data traffic and
relays them transparently.
3.11.5.1 — Automatic link discovery scenarios
To Next Page
Loading...
