nick n.

updating netdisco-mibs is the first step, but snmp::info might also need updating. i'll add updating the mibs to my todo list.

> Grepping for enterprises in these MIBs shows me lancom-systems instead of lancom. this is corrent, we prefer the dirname to be the same as the oid id. for lancom...

added in netdisco/netdisco-mibs#137 it seems at one time onesome submitted complete code for a lancom class ( netdisco/snmp-info#250 ) if you can provide me with an snmprec as detail here...

is this correct that you are using version 2.039031? that's almost 3 years old. any chance to test with a recent version? a clean install under a different user is...

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...

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...

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...

it seems you missed the `-e` parameter just before at_paddr & at_netaddr, so netdisco-do defaulted to showing interfaces instead of of addresses. i guess we should at least warn if...

ahha, this gets us further. first of: layer2 devices can return a the macip mappings they know, but for the full list you'll need to poll the gateway (10.84.0.2 in...

hm, why are all your addresses in the 127.0.0.0/8 range? those are designed to be device local, so netdisco tries it's best not to store them...