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
On Wed, 9 Jul 2014 10:33:25 -0300 Bruno Galindro da Costa bruno.galindro@gmail.com wrote:
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
You are referring to three different addresses here, not two, which is a bit confusing. I'm going to assume that whenever you wrote 250.121, what you really meant was 252.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
So 251.245 has identified itself to 252.121 by its MAC address 00-1E-C1-ED-78-80.
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
While 252.121 has identified itself to 251.245 by its MAC address 2810-7B68-9D90.
It appears to me that NAV is failing to see that 00-1E-C1-ED-78-80 is in fact the device 251.245, which is why you are seeing this record in the "unrecognized neighbors" list for 252.121:1/48.
NAV doesn't use the lldpRemManAddrTable to get management information for remote devices. When a remote device identifies itself with a MAC address like this, NAV will try to look up known MAC addresses from its own database.
It will look at ARP data. If 251.245 has never communicated over IP using the 00-1E-C1-ED-78-80 address, there will be no ARP data to find.
Secondly, NAV will look at the known physical addresses of any known interface. If has collected no interfaces from 251.245 with the physical address 00-1E-C1-ED-78-80, there will be no data found.
At this point, NAV has failed to identify the neighbor and puts it in the unrecognized neigbors list. The only identified neighbor candidates end up coming from CAM data, which can be an unreliable source.
-
So, my question is: If you search for 00-1E-C1-ED-78-80 in the Machine Tracker, do you have any hits for 251.245? If you look at the complete interface report for 251.245, do you see any interfaces with this adress in the physical address column?
Conversely, can you find machine tracker records linking 28-10-7B-68-9D-90 to the 252.121 IP address, or any interfaces on 252.121 with this physical address?
If not, NAV may need to employ further strategies to identify MAC addresses on devices.
You are referring to three different addresses here, not two, which is a bit confusing. I'm going to assume that whenever you wrote 250.121, what you really meant was 252.121.
Yes! The correct IP adress is 252.121. Sorry :)
So, my question is: If you search for 00-1E-C1-ED-78-80 in the Machine
Tracker, do you have any hits for 251.245? If you look at the complete
interface report for 251.245, do you see any interfaces with this adress
in the physical address column?
No for booth, and now I know why: 00-1E-C1-ED-78-80 is the chassis MAC Address os 251.245 switch. The mac address of 251.245 is 00:1e:c1:ed:78:8*1*. This is because 251.245 is the IP address of a VLAN interface... The device was registered with category SW not GSW. After change the device category from SW to GSW, waiting a few minutes to ipdevpool run, the machine tracker could find the relation beetween 251.245 and 00:1e:c1:ed:78:8*1.*
Conversely, can you find machine tracker records linking 28-10-7B-68-9D-90 to the 252.121 IP address, or any interfaces on 252.121 with this physical address?
Yes. 28-10-7B-68-9D-90 is the mac address of 252.121.
2014-07-11 11:02 GMT-03:00 Morten Brekkevold morten.brekkevold@uninett.no:
On Wed, 9 Jul 2014 10:33:25 -0300 Bruno Galindro da Costa < bruno.galindro@gmail.com> wrote:
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
You are referring to three different addresses here, not two, which is a bit confusing. I'm going to assume that whenever you wrote 250.121, what you really meant was 252.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
So 251.245 has identified itself to 252.121 by its MAC address 00-1E-C1-ED-78-80.
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
While 252.121 has identified itself to 251.245 by its MAC address 2810-7B68-9D90.
It appears to me that NAV is failing to see that 00-1E-C1-ED-78-80 is in fact the device 251.245, which is why you are seeing this record in the "unrecognized neighbors" list for 252.121:1/48.
NAV doesn't use the lldpRemManAddrTable to get management information for remote devices. When a remote device identifies itself with a MAC address like this, NAV will try to look up known MAC addresses from its own database.
It will look at ARP data. If 251.245 has never communicated over IP using the 00-1E-C1-ED-78-80 address, there will be no ARP data to find.
Secondly, NAV will look at the known physical addresses of any known interface. If has collected no interfaces from 251.245 with the physical address 00-1E-C1-ED-78-80, there will be no data found.
At this point, NAV has failed to identify the neighbor and puts it in the unrecognized neigbors list. The only identified neighbor candidates end up coming from CAM data, which can be an unreliable source.
So, my question is: If you search for 00-1E-C1-ED-78-80 in the Machine Tracker, do you have any hits for 251.245? If you look at the complete interface report for 251.245, do you see any interfaces with this adress in the physical address column?
Conversely, can you find machine tracker records linking 28-10-7B-68-9D-90 to the 252.121 IP address, or any interfaces on 252.121 with this physical address?
If not, NAV may need to employ further strategies to identify MAC addresses on devices.
-- Morten Brekkevold UNINETT
On Fri, 11 Jul 2014 14:42:07 -0300 Bruno Galindro da Costa bruno.galindro@gmail.com wrote:
You are referring to three different addresses here, not two, which is a bit confusing. I'm going to assume that whenever you wrote 250.121, what you really meant was 252.121.
Yes! The correct IP adress is 252.121. Sorry :)
So, my question is: If you search for 00-1E-C1-ED-78-80 in the Machine Tracker, do you have any hits for 251.245? If you look at the complete
interface report for 251.245, do you see any interfaces with this adress in the physical address column?
No for booth, and now I know why: 00-1E-C1-ED-78-80 is the chassis MAC Address os 251.245 switch. The mac address of 251.245 is 00:1e:c1:ed:78:8*1*. This is because 251.245 is the IP address of a VLAN interface... The device was registered with category SW not GSW. After change the device category from SW to GSW, waiting a few minutes to ipdevpool run, the machine tracker could find the relation beetween 251.245 and 00:1e:c1:ed:78:8*1.*
I'm not immediately sure why that helped, but I'm currently at EuroPython in Berlin inbetween my vacation weeks, so my memory on this issue may be foggy ;)
A bridge MAC address is retrievable via the BRIDGE-MIB, but NAV doesn't currently use this for anything. If this address doesn't correspond to any of the physical interfaces that are collected, and is never used for IP communication, NAV will not see it. This may be what was the case here.
It may be that we should collect and store the bridge address somewhere to aid in identication. It may also be that one of the auxilliary tables of the LLDP-MIB will provide more information. From the snmpwalk dumps you sent, it appears that there was more information to be found about the remote hosts discovered by LLDP.
If you would file a bug report we won't forget about it :)
Hi Morten!
It may be that we should collect and store the bridge address somewhere to
aid in identication. It may also be that one of the auxilliary tables of the LLDP-MIB will provide more information. From the snmpwalk dumps you sent, it appears that there was more information to be found about the remote hosts discovered by LLDP.
What title could I use to name the bug report for easy remeber?
2014-07-23 9:02 GMT-03:00 Morten Brekkevold morten.brekkevold@uninett.no:
On Fri, 11 Jul 2014 14:42:07 -0300 Bruno Galindro da Costa < bruno.galindro@gmail.com> wrote:
You are referring to three different addresses here, not two, which is a bit confusing. I'm going to assume that whenever you wrote 250.121, what you really meant was 252.121.
Yes! The correct IP adress is 252.121. Sorry :)
So, my question is: If you search for 00-1E-C1-ED-78-80 in the Machine Tracker, do you have any hits for 251.245? If you look at the complete
interface report for 251.245, do you see any interfaces with this adress in the physical address column?
No for booth, and now I know why: 00-1E-C1-ED-78-80 is the chassis MAC Address os 251.245 switch. The mac address of 251.245 is
00:1e:c1:ed:78:8*1*.
This is because 251.245 is the IP address of a VLAN interface... The
device
was registered with category SW not GSW. After change the device category from SW to GSW, waiting a few minutes to ipdevpool run, the machine tracker could find the relation beetween 251.245 and 00:1e:c1:ed:78:8*1.*
I'm not immediately sure why that helped, but I'm currently at EuroPython in Berlin inbetween my vacation weeks, so my memory on this issue may be foggy ;)
A bridge MAC address is retrievable via the BRIDGE-MIB, but NAV doesn't currently use this for anything. If this address doesn't correspond to any of the physical interfaces that are collected, and is never used for IP communication, NAV will not see it. This may be what was the case here.
It may be that we should collect and store the bridge address somewhere to aid in identication. It may also be that one of the auxilliary tables of the LLDP-MIB will provide more information. From the snmpwalk dumps you sent, it appears that there was more information to be found about the remote hosts discovered by LLDP.
If you would file a bug report we won't forget about it :)
-- Morten Brekkevold UNINETT
On Sat, 26 Jul 2014 14:30:05 -0300 Bruno Galindro da Costa bruno.galindro@gmail.com wrote:
It may be that we should collect and store the bridge address somewhere to aid in identication. It may also be that one of the auxilliary tables of the LLDP-MIB will provide more information. From the snmpwalk dumps you sent, it appears that there was more information to be found about the remote hosts discovered by LLDP.
What title could I use to name the bug report for easy remeber?
How about just "Collect bridge addresses for neighbor identification"? If we don't like the title, we can change it later.
Done: https://bugs.launchpad.net/nav/+bug/1356388
2014-08-12 10:21 GMT-03:00 Morten Brekkevold morten.brekkevold@uninett.no:
On Sat, 26 Jul 2014 14:30:05 -0300 Bruno Galindro da Costa < bruno.galindro@gmail.com> wrote:
It may be that we should collect and store the bridge address somewhere to aid in identication. It may also be that one of the auxilliary tables of the LLDP-MIB will provide more information. From the snmpwalk dumps you sent, it appears that there was more information to be found about the remote hosts discovered by LLDP.
What title could I use to name the bug report for easy remeber?
How about just "Collect bridge addresses for neighbor identification"? If we don't like the title, we can change it later.
-- Morten Brekkevold UNINETT
-
Bruno Galindro da Costa -
Morten Brekkevold