-
-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wing/Extreme/Zebra/Motorola devices #369
Comments
Adding the output of ~/bin/netdisco-do show for one of the devices... [netdisco@netlogdbgsrv ~]$ ~/bin/netdisco-do show -d 10.250.192.31 -e specify -DIQ |
We have some new Extreme devices and they are not yet recognized: Support would be nice indeed. TIA |
On an added note: Extreme hardware: Software version 7.6.2.303 on a Ethernet Routing Switch 4950GTS-PWR+ identifies as model "303". Before that version (possibly up to 7.6.2.217 (not sure), the switch is correctly identified. |
this is most likely due to outdated mibs. since i'm no extreme customer (yet, since i am an aerohive user which extreme recently bought) i'm having a hard time finding their most recent mibs. if you can provide those mibs to us we will update them & things will most likely work. |
first of it would be handy that we somehow get those mibs first, this will allow us to check if any snmp::info class has provisions for them. thx |
Hi inphobia, I hope that MIBS are in the public space. See attachment, hope this helps. versions seems to be 7.6.1 for the mibs, they came with 7.6.3 software I think. |
excellent, at first glance these seem to include the required mapping in S5-REG-MIB.mib and/or SYNOPTICS-ROOT-MIB.mib. they do however include mibs from all over the place (makes sense since extreme seems to be buying everything that's for sale in the network world atm), so it will take some time to work through this to see what's the best option to get this in. the also include a lot of iana & such mibs. this could be just so they can offer a complete package (which makes it easy to use for most customers). this could also be because they made changes to them, which would be crap. bottom line: this seems to be the stuff we need, getting it sorted and merged could take a bit of time. i've taken a liking to the mib stuff lately, regretfully my schedule hasn't. you can always have a go yourself, our docs are here: https://github.com/netdisco/netdisco-mibs/wiki/Updating-MIBs |
Hi @inphobia , I need to get Extreme support added (for their BOSS and EXOS OS switches), so I have forked the MIBS repo and will have a go at following the instructions to add new MIBs that I got from Extreme directly. Can you please let me know how to access the IRC? |
our channel is netdisco on freenode.net you can either use an irc client like mirc (windows) or xchat (unix), or use a web interface: |
according to your report and recent report these devices are classified under snmp::info::layer3 since no specific module has been written for them. if all you need is showing model & vendor than this might work for you: netdisco/netdisco-mibs#212 (comment) the netdiso-mibs are up to date so if sysObjectID points to an actual product it can be resolved, and for vendor you can get the use strip everything after .1.3.6.1.4.1.xxx from sysobjectid & translate that. everything more advanced requires knowing the layout of a specific mib and thus needs a device specific module. i see how at least trying to get the vendor & model can be usefull, but figuring out which mibs to load to translate them is not trivial, and loading all the mibs is expensive. |
Greetings :)
I have got an issue with Extreme devices on my network, getting discovered...
I am not even sure whether I am posting this in the right place...
I read a few threads about it and I missing the point...
While using netdisco, lots of devices (~1300 Access points) get discovered as vendor unknow with the oid of the vedor being:
388.11.1.2
388.11.1.4
388.15
388.50.1.1.3
388.50.1.1.40
Al of these belong nowadays to Extreme, though Identified also as their previous acquisitions (Symbol, Motorola, Zebra...)
each of these devices have a mib file, containing the same enterprise identifier 388..
I added the files to netdisco-mibs/motorola and followed the adding mibs procedure.
Still, few errors (because of the 388 being identified in more than one mib file I guess...
The question I have is there anything I can do for identifying those devices correctly or should it be a feature request...
10xs in advance for your response.
And for a Great project!!!
Jacob
The text was updated successfully, but these errors were encountered: