Network Management
Nodes with LLDP don't show connections
If trying to configure links between LLDP nodes, need the LLDP poller assigned and OID's required in both devices snmpwalks.
First published date
1/21/2020 9:26 AM
Last published date
1/21/2020 9:26 AM
Overview
You are not able to setup LLDP connections between Cisco and non-Cisco nodes.
LLDP OID's required are outlined in:
https://support.solarwinds.com/SuccessCenter/s/article/What-object-IDs-OIDs-does-the-Orion-Platform-poll-for-network-topology-information
For LLDP connections between nodes, the LLDP poller needs to be assigned to the nodes:
Poller: N.Topology_LLDP.SNMP
This is assigned automatically once LLDP is enabled and next Topology discovery job kicks in (default every 30 mins)
LLDP OID's required are outlined in:
https://support.solarwinds.com/SuccessCenter/s/article/What-object-IDs-OIDs-does-the-Orion-Platform-poll-for-network-topology-information
For LLDP connections between nodes, the LLDP poller needs to be assigned to the nodes:
Poller: N.Topology_LLDP.SNMP
This is assigned automatically once LLDP is enabled and next Topology discovery job kicks in (default every 30 mins)
Product section
Network Performance Monitor
Cause
We poll LLDP remote port id on OID lldpRemPortId = "1.0.8802.1.1.2.1.4.1.1.7." and the devices seem to use different format than ifName.
For example node 334 OP-H3-CAJ2-IZQ reports remotePortID "Eth3/41" but node 6 NX7009_1-SE has interface with ifName "Ethernet3/41"
Because these two do not match the connection is not established.
For example node 334 OP-H3-CAJ2-IZQ reports remotePortID "Eth3/41" but node 6 NX7009_1-SE has interface with ifName "Ethernet3/41"
Because these two do not match the connection is not established.
Resolution
To fix this, you should setup the LLDP on the devices to return full names port/interfaces names e.g. "Ethernet3/41" instead of "Eth3/41"