netdisco
Cannot get remote neighbour on esxi
We are running the latest netdisco version 2.44 snmp::info is also at the latest version 3.70 We are trying to get lldp working on various Huawei switches (6810, 6855, 5855) I have enabled the iso fix from the lldp help page and snmp is working fine on the huawei switches. However, lldp is very capricious and seems to work very sparingly toward ESXi servers. Running ~/bin/netdisco-do show -d Huawei-switch -e lldpRemSysName gives the proper lldp remote servers but running the same command against and ESXi gives the following [16271] 2020-01-03 09:10:11 info App::Netdisco version 2.044004 loaded. [16271] 2020-01-03 09:10:11 info show: [x.x.x.x]/lldpRemSysName started at Fri Jan 3 09:10:11 2020 undef [16271] 2020-01-03 09:10:12 info show: finished at Fri Jan 3 09:10:12 2020 [16271] 2020-01-03 09:10:12 info show: status done: Showed lldpRemSysName response from x.x.x.x Same goes with lldp_SysName However sysName give the name of the ESXi host.
"Undef" is the hint here I guess but i'm not sure what to do with it Also for some reason under ports in netdisco on the switch I cannot see the mac address of the attached nic of the ESXi but other mac addresses despite the switch showing the proper mac when running display lldp neigbhour if this is relevant.
I have tried to apply patch from https://github.com/netdisco/netdisco/issues/436 with no luck (actualy it broke the file so future request wouldn't work so i reverted back)
Added note, our ESX are configured with lldp (not cdp as huawei is working with lldp) On the vcenter, each host shows the proper lldp information and report the proper port so basically, info reported by the switch and the esx are correct but not on netdisco.
Some more info : it looks like the issue is with mac address learning on the switch as it sees the info with lldp but not with mac address learning. Seems to be an issue with the snmp info on the switch.
Just realized that the mac of the esx is showing on the trunk and not on the port itself obviously and this is probably what is causing the issue with netdisco.
esxi support could be better, it's somewhere on my todo list but ⌛️ has not been on my side lately ☹️
https://kb.vmware.com/s/article/2118059 has some pointers, and https://github.com/netdisco/netdisco-mibs/pull/113 will most likely also be needed. vlan, cdp/lldp, arpnic/macsuck all could use some love.
Thanks, well I think i'll wait. In the meantime I went to the manual link route
fyi, i haven't forgotten about this, but real life got in the way and i currently have more pressing issues to fix.
as long as this issue is open it remains on our radar.
netdisco/netdisco-mibs#113 has been merged for a while, and we just released netdisco-mibs 2.019
this does not mean the issue is fixed, but if with more recent mibs it might be easier for someone else to troubleshoot. esxi stuff is on my todolist, but so are a lot of other items...
feel free to give it a try if you feel up to it, we'll support you any way we can.