nick n.
nick n.
no clue either, but it seemes our version could use an update netdisco/netdisco-mibs#231 perhaps updating the entity parts isn't a bad idea either...
s::i::layer2::ciscosb has provisions for this using the ciscosb mibs. that's the good news. the bad news is that for whatever reason the ciscosb 220 series mibs seems to be different...
10.98.1.201 is a ciscosb sg300 10.40.254.105 is a ciscosb `CBS220-24T-4X` ``` netdisco:~> netdisco-do show -d 10.40.254.105 -e Q-BRIDGE-MIB::dot1qTpFdbAddress [32395] 2024-06-12 21:33:27 info App::Netdisco version 2.076005 loaded. [32395] 2024-06-12 21:33:27 info...
i'll try & have a look, but at first glance none of my devices return this & all return with: ``` Read Q-BRIDGE-MIB trace: netsnmp_ds_set_int(): default_store.c, 268: netsnmp_ds_set_int: Setting LIB:4...
what's not working? i have a CBS350-16T-2G on v3.4 firmware working fine.
> [!IMPORTANT] this is not an official release. do not bother the devs should you run into issues. only windows binaries, building on other operating systems is less of a...
while i'm at it might as well add see if we can close some more requests as well.
opengear changes still need to be checked if they don't break the snmp::info module
#221 has newer cisco updates, will need to redo opengear
if there are now objections i'll delete this branch, recreate it and actually merge it in the next 4 weeks