nick n.
nick n.
newer os versions have not fixed this. while a fabric interconnect 6332 is a nexus 9332pq in disguise hardware-wise, that's not the case for the os. after checking the ucs...
if at all possible the data dumps detailed here: https://github.com/netdisco/snmp-info/wiki/Simulating-Agents#get-snmp-datadump would help us out a lot.
this could be an interesting one. airespace support is provided via snmp::info::airespace, but according to it's manual page "This class emulates bridge functionality for the wireless switch. This enables end...
in regards to the snmp data, if you consider it sensitive you can also provide it to the snmp::info devs in private where we won't share it without your permission....
just an update to let you know this issue is not forgotten but given the complexity it's not on the top of my personal todo list. i'll try and have...
referencing #307 & #218 , both seem to be similar if not identical
those names come from h3c mibs, so we need to know which snmp::info class is used for your device, but if it's layer3::h3c then there are no provisions yet for...
> SNMP::Info will need a separate device class for Aruba switches running AOS-CX, such as the 8400, 8320 and several new smaller switches. Hope to start on this task soon....
side note: mentioning netdisco/netdisco-mibs#138 , i'll try & get those merged asap & do a new mibs release so you're working with up to date files.
has the topology ever worked? if so; with what version of snmp::info? with "connected devices", do you mean endnodes or other switches?