-
-
Notifications
You must be signed in to change notification settings - Fork 89
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
Vendor Extrem Network : model not parsed correctly for AP3xx / AP7532 #212
Comments
what os version are these running? i'm guessing "wing"? ap's running "iq engine" aka aerohive's hiveos should be supported. |
yes we are using "wing". We have several thousands of those devices and os versions may vary, 5.X (5.9.1 on the screenshot), 7.7 etc etc but it's difficult to say while Netdisco doesn't parse them accurately :) |
at least with the latest mib release this object translates: 👀 Building MIBs index now, if i read the code correctly, somewhere along the line snmp::info will have to have read the mib to find a translation, and since we don't have explicit support for wing devices their mibs are most likely never loaded. since i'm curious, could you modify Layer3.pm? in add:
this should return the translated value for that oid then, which should result in returning the vendor might also be possible, if by vendor you're ok with whatever name is mapped to the enterprise registration, in this case this will return for that you'll need to modify the haven't tested the code example, and have no idea what impact this will have. i think it will at least populate the vendor & model and the values of whatever Layer3.pm supports if they are exactly implemented as the mibs describe. |
perhaps Layer3.pm could try & bit harder also return something from entity-mib if supported, but that could just make it a huge mess depending if those values make little sense or tend to change a lot (new os, diffent hw, etc)... |
if all you want is pretty formatted vendor , model and perhaps os release, that can probably be done in under an hour. but providing a module creates expectations, such as mapping clients to ssid etc... |
everybody here like netdisco because it's easy to handle without having big network knowledge, so our main goal is to have all of our big network mapped in netdisco with the following informations : FQDN, IP, serial number, vendor, model, os, os version. So i can promise you that if the vendor/model/os/os version can work for extreme network devices we won't open a new ticket for ssid & co anytime soon ;) |
haven't tested this but should be fairly close.
if you still use that hack from previously in this thread, but back the original file the in the main Info.pm file look for
below this add
create a file under Layer3/ named Wing.pm (you might need to change the VERSION to match what you're running:
this mostly a copy/paste from Redlion.pm , and as you can see i list interest halfway through to renaming it to wing unless it was needed. manual part isn't even changed. Important none of this is tested, haven't even tested it for syntax errors it should however give you a base that should not need many changes to do what you want. oids i use to get the relevant info are also a complete guess, but they seem likely candidates. |
Hello,
We have trouble with some Extrem Network devices details :
Here are the mibs of the equipments:
AP3xx-mibs-7.7.1.8-009R.tar.gz
AP7532-mibs-7.7.1.8-009R.tar.gz
The text was updated successfully, but these errors were encountered: