Oliver Gorwits
Oliver Gorwits
Moved to SNMP::Info repo because Netdisco would log if it could see the IPv4 entry. Not sure what's going on but `_lldp_addr_index` in LLDP.pm should work for this. Did not...
Hi @rkerr are you interested in commit access to do this directly? You seem to know well enough!
Hi @rkerr no worries! completely understand that situation, and having the great detail is a massive head start and much appreciated. I'll take a look at this asap.
Netdisco has some support coming from Cisco WLC that extra virtual ports are created on the WLC for each AP and then wireless clients are put onto those ports. None...
Hi @NMCPaul indeed you are right. Unfortunately, however, this seems to be by design in Netdisco. It seems to be difficult to check which type of interface is running, so...
Hi @sir-bogbrush this is very likely because you have a large number of devices in Netdisco (more than 1000) and the network map doesn't show the options in that case....
implemented in b02990f52181042797d67d30840884a1c17dd9af
Hi @elbuit Thanks for opening an issue. This is unlikely to be Netdisco itself (as far as I can tell from code), and likely either SNMP::Info or even an issue...
according to google AI (!) this is most likely an issue on the "server" side - that is, the Aruba device. unfortunately I guess this Aruba module in Netdisco works...
It looks to me like the backend is functioning correctly...? Note that if you manually run any single discover job, it is forced to run (ignores the deferrals) by design....