Oliver Gorwits

It did occur to me that perhaps Netdisco is insistent on `uptime()` because without it, macsuck would be messed up (calculating time last seen, wrapping clock, etc).

Hi @SaymonDzen the device class (Layer3 :: DLink) is not related to the SNMP version. However, the device class *does* control which information is gathered and how that information is...

Hi, please can you give the Netdisco and SNMP::Info version of your old installation where it's working correctly? Thanks

Thanks @inphobia, looks like CiscoSB is a Layer2 implementation but is used even if the device has Layer3 capabilities. So we need a Layer3 version of CiscoSB (or use another...

good question, I've no idea :-D. but it can't hurt, I guess. On Sun, 27 Jan 2019 at 01:13, nick n. wrote: > i'll tag @postilion too, i think he...

Hi, if you go to the Device Ports page for device ip252.31 and select port 22, and enable the Neighbor Device column, what is shown there? Also in the return,...

@def-bs thanks! OK so this is a consequence of the recent fix where Netdisco was overlaying two links. Here you asymmetric connection definitions. Netdisco has to pick one to use...

OK looks like a problem with the HP class in SNMP::Info, you can see the duplicate port "22.1" and "0.22.1" (latter is the correct data).

Sorry for jumping on this... I've also been asked by some downstream users for upstart and BSD rc.d support. I would guess that systemd support is yet another kind of...

I have a hand in the App::Netdisco stuff, and that's also where the other init requests come from (& let's not ignore BSD - lots of users there!). I can...