Details

    • Add New Device / OS
    • Resolution: Fixed
    • Minor
    • None
    • Professional Edition
    • Discovery

    Description

      Hello Observium TEAM

       

      We have some new Extreme Routers (former Brocade)

      On these Devices it is SLX-OS Running.

      The following device are perfect working and we see all the stuff, CPU RAM Fans VLAN and all the normaly stuff: Extreme SLX9140 / Extreme SLX OS 17s.1.02c 

      But withe the new Device, Extreme SLX9640 Switch/Router, SLX Operating System Version 18r.2.00. We only can monitor the Interfaces.

      May i ask is these Device still not integrated or is there something wrong ?

       

      Thanks for your Help and regards from Switzerland

      Chris

      Attachments

        1. discovery_php.txt
          9 kB
        2. slxos18r.2.00_all_mibs.tar.gz
          558 kB
        3. snmpwalk_1.txt
          1.21 MB
        4. snmpwalk_2.txt
          757 kB
        5. VLANS_missing.JPG
          VLANS_missing.JPG
          34 kB

        Issue Links

          Activity

            [OBS-3004] Extreme SLX9640 Switch/Router

            Hello Mike

            Thbaks for your help. Now it looks much better. But we still miss the VLAN section as you see in an oter Device on the attaced File (VLANS_missing.jpeg). Is it possible to make these also visible ? Thanks for your help and regards.

            Leucom Tobler Christoph added a comment - Hello Mike Thbaks for your help. Now it looks much better. But we still miss the VLAN section as you see in an oter Device on the attaced File (VLANS_missing.jpeg). Is it possible to make these also visible ? Thanks for your help and regards.

            Support added in r9864.

            landy Mike Stupalov added a comment - Support added in r9864.

            Just for your info (and report to Extreme support), device report incorrect (empty) ip address prefixes in IP-MIB::ipAddressPrefix:

            snmpbulkwalk -v2c -c <community> -Pud -OQUs -m IP-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp slx9640.test ipAddressPrefix
             
            ipAddressPrefix.ipv4."172.16.0.20" = zeroDotZero
            ipAddressPrefix.ipv4."172.16.1.130" = zeroDotZero
            ipAddressPrefix.ipv4."172.16.63.220" = zeroDotZero
            ipAddressPrefix.ipv4."212.203.63.1" = zeroDotZero
            ipAddressPrefix.ipv4."212.203.63.2" = zeroDotZero
            ipAddressPrefix.ipv4."212.203.63.220" = zeroDotZero
            ipAddressPrefix.ipv6."2a:00:aa:c0:00:00:00:00:00:00:00:00:00:00:00:01" = zeroDotZero
            ipAddressPrefix.ipv6."2a:00:aa:c0:00:00:00:00:00:00:00:00:00:00:00:02" = zeroDotZero
            ipAddressPrefix.ipv6."2a:00:aa:c0:00:00:00:00:00:00:00:00:00:00:02:20" = zeroDotZero
            ipAddressPrefix.ipv6."fe:80:00:00:00:00:00:00:fe:0a:81:ff:fe:f9:8d:31" = zeroDotZero
            ipAddressPrefix.ipv6."fe:80:00:00:00:00:00:00:fe:0a:81:ff:fe:f9:8d:32" = zeroDotZero
            

            There should be numeric value, ie 24 for 172.16.0.20/24

            landy Mike Stupalov added a comment - Just for your info (and report to Extreme support), device report incorrect (empty) ip address prefixes in IP-MIB::ipAddressPrefix : snmpbulkwalk -v2c -c <community> -Pud -OQUs -m IP-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp slx9640.test ipAddressPrefix   ipAddressPrefix.ipv4."172.16.0.20" = zeroDotZero ipAddressPrefix.ipv4."172.16.1.130" = zeroDotZero ipAddressPrefix.ipv4."172.16.63.220" = zeroDotZero ipAddressPrefix.ipv4."212.203.63.1" = zeroDotZero ipAddressPrefix.ipv4."212.203.63.2" = zeroDotZero ipAddressPrefix.ipv4."212.203.63.220" = zeroDotZero ipAddressPrefix.ipv6."2a:00:aa:c0:00:00:00:00:00:00:00:00:00:00:00:01" = zeroDotZero ipAddressPrefix.ipv6."2a:00:aa:c0:00:00:00:00:00:00:00:00:00:00:00:02" = zeroDotZero ipAddressPrefix.ipv6."2a:00:aa:c0:00:00:00:00:00:00:00:00:00:00:02:20" = zeroDotZero ipAddressPrefix.ipv6."fe:80:00:00:00:00:00:00:fe:0a:81:ff:fe:f9:8d:31" = zeroDotZero ipAddressPrefix.ipv6."fe:80:00:00:00:00:00:00:fe:0a:81:ff:fe:f9:8d:32" = zeroDotZero There should be numeric value, ie 24 for 172.16.0.20/ 24

            Tnx, this is new line of Extreme OS (SLX OS), partially already supported, but here changed base system id.
            Will fixed soon.

            Can you attach vendor specific MIB files from support zone?

            landy Mike Stupalov added a comment - Tnx, this is new line of Extreme OS (SLX OS), partially already supported, but here changed base system id. Will fixed soon. Can you attach vendor specific MIB files from support zone?

            Hello Mike

            Thanks for your fast Answer.

            In the Atachement you will fionde the 3 outputs.

            Please tell me if i can do somethiong more.

             

            Thanks for your help and Regards from Switzerland, Chris

            Leucom Tobler Christoph added a comment - Hello Mike Thanks for your fast Answer. In the Atachement you will fionde the 3 outputs. Please tell me if i can do somethiong more.   Thanks for your help and Regards from Switzerland, Chris

            Please attach debug discovery:

            ./discovery.php -d -m os -h <device>
            

            and will help a lot full snmpwalk:

             snmpwalk -v2c -c <community> -ObentU <device> .1 > myagent.snmpwalk
             snmpwalk -v2c -c <community> -ObentU <device> .1.3.6.1.4.1 >> myagent.snmpwalk
            

            landy Mike Stupalov added a comment - Please attach debug discovery: ./discovery.php -d -m os -h <device> and will help a lot full snmpwalk: snmpwalk -v2c -c <community> -ObentU <device> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -ObentU <device> .1.3.6.1.4.1 >> myagent.snmpwalk

            People

              landy Mike Stupalov
              Leucom Tobler Christoph
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: