On Mon, 20 Apr 2020 11:46:06 -0400 scorpion7 scorpion7@iqonline.net wrote:
NAV v5.0.5 appears to have a problem in the topology/LLDP portion. The switch referenced below is a Cisco WS-3750X stack, running 15.2(4)E10. Referenced devices are [Ubiquiti] APs. FWIW – the switch does have such things as ARP inspection, DHCP snooping, etc. – enabled.
File "/opt/venvs/nav/lib/python3.7/site-packages/nav/ipdevpoll/plugins/lldp.py", line 222, in _identify_interfaces result = lookup(str(portid)) File "/opt/venvs/nav/lib/python3.7/site-packages/nav/ipdevpoll/plugins/lldp.py", line 248, in _interfaces_from_mac return self._interface_query(Q(ifphysaddress=mac))
[snip]
django.db.utils.DataError: invalid input syntax for type macaddr: "None"
LINE 1: ..."netboxid" = 26 AND "interface"."ifphysaddress" = 'None') OR...
It looks to me like the LLDP record in question was incomplete, something the code doesn't seem prepared to handle.
You could either do a manual snmpwalk against the device, querying `LLDP-MIB::lldpRemTable`, or you could enable debug logging for the LLDP subsystems of ipdevpoll in NAV and dump the relevant log parts here.
For the latter, add `nav.ipdevpoll.plugins.lldp = DEBUG` to the `[levels]` section of `/etc/nav/logging.conf`, then invoke a manual topo job against the affected device:
ipdevpolld -J topo -n AFFECTED-DEVICE
Related: Was running an older version of NAV which appeared (at least via GUI) to have no issue this equipment combination of Cisco and Ubiquiti. Due to an odd issue, did end up dropping the VM and simply created a new one with latest Debian and latest NAV version, re-populating the equipment and configuration. Which may have been why certain things came to light?
You may simply have been hit by a known bug with caching of LLDP identification. Reinstalling things meant starting without cached data. We should really get on that soon :-) See [1] for details.
The Netmap doesn’t appear to be fully populated – suspect that it’s a cascading result of the above error?
That is likely, yes.
[1] https://github.com/Uninett/nav/issues/2106
-- sincerely, Morten Brekkevold Uninett