I've two switches: xxx.xxx.251.245 and xxx.xxx.252.121.
250.121 is connected to GigabitEthernet 1/0/5 of 251.245 251.245 is connected to GigabitEthernet 1/48 of 250.121
251.245 is a 5500G-EI 24-Port (3Com Switch 5500G-EI 24-Port Software Version 3Com OS V3.03.02s168p22 from 3com) 250.121 is a DGS-3120-48TC (DGS-3120-48TC Gigabit Ethernet Switch from dlink)
All of them has LLDP enabled.
This is the neighbor information on switch port 1/48 of 250.121:
Port ID : 1:48 ------------------------------------------------------------------------------- Remote Entities Count : 1 Entity 1 Chassis ID Subtype : MAC Address Chassis ID : 00-1E-C1-ED-78-80 Port ID Subtype : Interface Name Port ID : GigabitEthernet1/0/5
Port Description : GigabitEthernet1/0/5 System Name : xxxxxx System Description : Switch 5500G-EI 24-Port System Capabilities : Bridge, Router Management Address Count : 1 Port PVID : 1 PPVID Entries Count : 0 VLAN Name Entries Count : 1 Protocol ID Entries Count : 0 MAC/PHY Configuration/Status : (See Detail) Power Via MDI : (See Detail) Link Aggregation : (See Detail) Maximum Frame Size : 1522 Unknown TLVs Count : 0
This is the neighbor information on switch port 1/0/5 of 251.245:
LLDP neighbor-information of port 5[GigabitEthernet1/0/5]: Neighbor index : 1 Update time : 80 days,21 hours,14 minutes,30 seconds Chassis type : MAC address Chassis ID : 2810-7B68-9D90 Port ID type : MAC address Port ID : 2810-7B68-9DC0 Port description : D-Link DGS-3120-48TC R2.00.010 Port 48 on Unit 1 System name : xxxxxx System description : Gigabit Ethernet Switch System capabilities supported : Repeater,Bridge System capabilities enabled : Repeater,Bridge
Management address type : ipV4 Management address : xxx.xxx.252.121 Management address interface type : IfIndex Management address interface ID : 5121 Management address OID :
In NAV, the DIRECT NEIGHBORSHIP CANDIDATES reports that *another.host* is a candidate neighbor to 1/0/5 of 251.245. BUT *another.host* is physically connected in switch port 1/2 of 252.121, as reported bellow:
[image: Imagem inline 3]
AFAIK, Nav will use LLDP over CAM to build the network topology. But, in this case, maybe is occurring something wrong, because seems that Nav isn't collecting LLDP informations from switches to build the network topology.
Another strange thing is the UNRECOGNIZED NEIGHBORS report. It is reporting that 251.245 is an unrecognized neighbor of 252.121 with lldp as source. Why??
[image: Imagem inline 4]
Morten, I'll send to you by e-mail the result of these commands:
root@nav:~# ipdevpolld -J topo -n xxx.xxx.252.121 root@nav:~# snmpwalk -v2c -c 1brass12 xxx.xxx.252.121 .1.0.8802.1.1.2.1.4 root@nav:~# snmpwalk -v2c -c 1brass12 xxx.xxx.252.121 .1.0.8802.1.1.2.1.3
root@nav:~# ipdevpolld -J topo -n xxx.xxx.251.245 root@nav:~# snmpwalk -v2c -c 1brass12 xxx.xxx.251.245 .1.0.8802.1.1.2.1.4 root@nav:~# snmpwalk -v2c -c 1brass12 xxx.xxx.251.245 .1.0.8802.1.1.2.1.3
-- Att. Bruno Galindro da Costa