Details

    • Improvement
    • Resolution: Unresolved
    • Minor
    • None
    • None
    • Discovery
    • None

    Description

      Software 8.10 was release, with fixes in the OS to match the MIB files, and also has fixes in the MIB files. Here are the new MIB files. This is specifically for the Alpha FXM HP controllers, which are separate from the Alpha FXM controllers. Here's a link to the changelog. 

      https://tools.alpha.ca/downloads/readme/0350091-001_AM_APP_CORDEXHP_README_FOR_UPGRADE_V8.10.pdf

      Attachments

        Issue Links

          Activity

            [OBS-4714] Alpha FXM HP MIB Update

            New MIB File uploaded, thanks!

            HamSolo Elijah Zeida added a comment - New MIB File uploaded, thanks!

            Uploaded! Thanks!

            HamSolo Elijah Zeida added a comment - Uploaded! Thanks!
            landy Mike Stupalov added a comment - - edited

            You can make snmpdump by this Oid (.1.3.6), I sure it's enough for this device:

            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6 > myagent.snmpwalk
            

            landy Mike Stupalov added a comment - - edited You can make snmpdump by this Oid (.1.3.6), I sure it's enough for this device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6 > myagent.snmpwalk

            Here is the response from Alpha 
            "

            "After looking a recent snmp fixed issue, we did find a problem in v8.10 that caused timeouts if an OID had a length of 1. This only happened if a walk starts on OID 1, or 1.3 . If you start a walk too high in the tree you will get a timeout. 

            They also tried snmpwalk -v2c -c public -Cc --hexOutputlength=0 -Ih -ObentxU 10.10.10.201 .1.3.6 and got a response, but snmpwalk -v2c -c public -Cc --hexOutputlength=0 -Ih -ObentxU 10.10.10.201 .1.3 did not."

            Thank you for escalating this issue. It will be solved in the upcoming release of software version 8.20.

            Our product management team will advise once the v8.20 is officially released." 

            If you guys want to close this ticket, I'll open a new one when 8.20 is released. Thanks!

            HamSolo Elijah Zeida added a comment - Here is the response from Alpha  " "After looking a recent snmp fixed issue, we did find a problem in v8.10 that caused timeouts if an OID had a length of 1. This only happened if a walk starts on OID 1, or 1.3 . If you start a walk too high in the tree you will get a timeout.  They also tried snmpwalk -v2c -c public -Cc --hexOutputlength=0 -Ih -ObentxU 10.10.10.201 .1.3.6 and got a response, but snmpwalk -v2c -c public -Cc --hexOutputlength=0 -Ih -ObentxU 10.10.10.201 .1.3 did not." Thank you for escalating this issue. It will be solved in the upcoming release of software version 8.20. Our product management team will advise once the v8.20 is officially released."  If you guys want to close this ticket, I'll open a new one when 8.20 is released. Thanks!

            I'm working with Alpha to get the issue resolved and will let you guys know. 

            HamSolo Elijah Zeida added a comment - I'm working with Alpha to get the issue resolved and will let you guys know. 

            We can't add support for any os by just MIB files.
            Need ro snmp access to test device or snmpdump (as requested).
            No other options.

            landy Mike Stupalov added a comment - We can't add support for any os by just MIB files. Need ro snmp access to test device or snmpdump (as requested). No other options.

            Yep, pretty much.... 

            HamSolo Elijah Zeida added a comment - Yep, pretty much.... 

            Hrm, I not understand.
            You can add device to observium (definitely by snmp), but can't do any snmpwalk directly from cli?

            landy Mike Stupalov added a comment - Hrm, I not understand. You can add device to observium (definitely by snmp), but can't do any snmpwalk directly from cli?

            I have talked to Alpha and they're looking into it. What's odd is we're still getting SNMP responses, and triggers from the device, it's just the snmp walk isn't working. 

            HamSolo Elijah Zeida added a comment - I have talked to Alpha and they're looking into it. What's odd is we're still getting SNMP responses, and triggers from the device, it's just the snmp walk isn't working. 

            without snmp walks it makes no sense to support the device in observium

            landy Mike Stupalov added a comment - without snmp walks it makes no sense to support the device in observium

            There appears to be a software bug that is preventing me from doing an SNMP walk... I'll see if I can get that resolved. 

            HamSolo Elijah Zeida added a comment - There appears to be a software bug that is preventing me from doing an SNMP walk... I'll see if I can get that resolved. 

            People

              landy Mike Stupalov
              HamSolo Elijah Zeida
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated: