Created
March 9, 2017 11:06
-
-
Save BlackDex/49bdc45eb3a57c6dbb72f8193193af0d to your computer and use it in GitHub Desktop.
irc conversation about librenms/oxidized issue
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
< BlackDex> laf: Oke, here i am :) | |
<@laf> BlackDex: so the DNOS device, is it DNOS or powerconnect? | |
< BlackDex> According to the switch it self it is DNOS v6 | |
< BlackDex> But that is totally different from DNOS v9 | |
< BlackDex> which is a true DNOS | |
< BlackDex> I don't know the exact differences | |
< BlackDex> The problem i had is that some switches were not able to be backuped by oxidized | |
< BlackDex> After some searching, i found that DNOS v6 is the continuation of the older powerconnect OS | |
< BlackDex> and that DNOS v9 is more like iOS | |
<@laf> BlackDex: so we need to update our detection then, Do you have sysObjectId's for a v6 and v9? | |
< BlackDex> after trying the powerconnect model with oxidized, the switches are backuped, but they fail with the dnos model | |
< BlackDex> let me check | |
< BlackDex> hmm. i don't have a v9 available atm. | |
<@laf> Anyone else run DNOS? | |
< BlackDex> i only have v6 an v8 atm here | |
< BlackDex> and it seems all those work better with the powerconnect profile. The commands which are in the dnos profile of oxidized arn't available | |
< BlackDex> like `show inventory` | |
<@laf> We shouldn't detect them as powerconnect though as they aren't, we will need to make a dnosv6 and dnosv9 profile I expect but need data from v9 to do that | |
<@laf> Is v8 like v6 or v9? | |
< BlackDex> let me see if i can find that | |
< BlackDex> v8 is FTOS 8.x | |
< BlackDex> ah, they don't make it easy :p | |
<@laf> No vendor does :( | |
<@laf> BlackDex: actually we've got v9 data | |
< BlackDex> the v6 i have i get "Dell-Vendor-MIB::dellLan.3058" and "Dell-Vendor-MIB::dellLan.3055", for the v8 (FTOS) i get "SNMPv2-SMI::enterprises.6027.1.3.8" | |
< BlackDex> Also: Dell-Vendor-MIB::dellLan.3042 | |
<@laf> What's the last one from? | |
< BlackDex> v6 also | |
< BlackDex> all v6's give me dellLan.30xx | |
<@laf> BlackDex: does v8 work ok as dnos in oxidized? | |
< BlackDex> yes, that seems to work fine | |
<@laf> BlackDex: then this is easy enough to fix from what I can see | |
<@laf> It will take us a good few days though as we have to notify users of the change to os type | |
<@laf> But .1.3.6.1.4.1.6027 = v8/v9 | |
<@laf> .1.3.6.1.4.1.674.10895 = v6 | |
< BlackDex> ah cool :). | |
< BlackDex> Yea. the v8 has the show inventory also | |
< BlackDex> the v6 doesn't | |
<@laf> BlackDex: Ok, now you can create an issue :) Just copy / paste this convo into the issue for reference | |
<@lnms-bot> You can create an issue on github: https://github.com/librenms/librenms/issues | |
< BlackDex> v8 works with powerconnect profile, but probably not the best thing i think to use | |
< BlackDex> oke :) | |
<@laf> BlackDex: but just to confirm, v8 on dnos profile works as expected? | |
< BlackDex> yes, that worked as it should | |
<@laf> Fine, fixable then | |
< BlackDex> no problems found using a debug session of oxidized |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment