Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-4346

aruba mibs / devices - snmpwalk attached. would really like to see APs/clients/etc

Details

    • Improvement
    • Resolution: Unresolved
    • Major
    • None
    • None
    • Discovery, Poller
    • None

    Description

      Hi there! 

      Running Observium Professional 22.12.12420

       

      Attached are latest mibs for APs and switches...

      as well as an SNMPwalk from my virtual controller. 

      Currently no wireless information is picked up by observium... just interface stats.

       

      Attachments

        1. kwalitywalk.txt
          95 kB
        2. kwalitywalk_resolved.txt
          91 kB
        3. apwalk_resolved.txt
          7 kB

        Activity

          [OBS-4346] aruba mibs / devices - snmpwalk attached. would really like to see APs/clients/etc
          Wolfspyre Wolf Noble added a comment -

          looking at this a bit closer:

           

          snmpwalk -v3 -a 'SHA'  -l 'authPriv' -u 'USER' -A 'AUTH' -X 'PRIV' -x 'DES'  ap-65.wolfspyre.io .1.3.6.1.4.1.14823.2 -m all -O Xa 
          

          I see much of the output resolving to the AI-AP-MIB mib:

          AI-AP-MIB::aiVirtualControllerKey.0 = STRING: xxxxx
          AI-AP-MIB::aiVirtualControllerName.0 = STRING: kwality
          AI-AP-MIB::aiVirtualControllerOrganization.0 = STRING:
          AI-AP-MIB::aiVirtualControllerVersion.0 = STRING: 8.10.0.7-8.10.0.7_87023 LSR
          AI-AP-MIB::aiVirtualControllerIPAddress.0 = IpAddress: 198.18.44.42
          AI-AP-MIB::aiSSIDIndex[0] = INTEGER: 0
          AI-AP-MIB::aiSSIDIndex[1] = INTEGER: 1
          AI-AP-MIB::aiSSIDIndex[2] = INTEGER: 2
          AI-AP-MIB::aiSSID[0] = STRING: "NO_SKWIRREL"
          AI-AP-MIB::aiSSID[1] = STRING: "24SKWIRREL"
          AI-AP-MIB::aiSSID[2] = STRING: "InternutOfSkwirrel"
          AI-AP-MIB::aiSSIDStatus[0] = INTEGER: enable(0)
          AI-AP-MIB::aiSSIDStatus[1] = INTEGER: enable(0)
          AI-AP-MIB::aiSSIDStatus[2] = INTEGER: disable(1)
          AI-AP-MIB::aiSSIDClientNum[0] = INTEGER: 0
          AI-AP-MIB::aiSSIDClientNum[1] = INTEGER: 0
          AI-AP-MIB::aiSSIDClientNum[2] = INTEGER: 0
          AI-AP-MIB::aiSSIDHide[0] = INTEGER: disable(0)
          AI-AP-MIB::aiSSIDHide[1] = INTEGER: disable(0)
          AI-AP-MIB::aiSSIDHide[2] = INTEGER: disable(0)
          <snip>
          

          but looking at includes/definitions/mibs/aruba.inc.php, it looks like (to my ignorant mind) observium is referencing "WLSX-SWITCH-MIB"
          and it looks like aruba has decided to use different lately:

          snmpwalk -v3 -a 'SHA'  -l 'authPriv' -u 'USER' -A AUTH' -X 'PRIV' -x 'DES'  kwality.wolfspyre.io .1.3.6.1.4.1.14823.2 -m all -O Xn
          

          .1.3.6.1.4.1.14823.2.3.3.1.1.1.0 = STRING: xxxxxxx
          .1.3.6.1.4.1.14823.2.3.3.1.1.2.0 = STRING: kwality
          .1.3.6.1.4.1.14823.2.3.3.1.1.3.0 = STRING:
          .1.3.6.1.4.1.14823.2.3.3.1.1.4.0 = STRING: 8.10.0.7-8.10.0.7_87023 LSR
          .1.3.6.1.4.1.14823.2.3.3.1.1.5.0 = IpAddress: 198.18.44.42
          .1.3.6.1.4.1.14823.2.3.3.1.1.7.1.1.0 = INTEGER: 0
          .1.3.6.1.4.1.14823.2.3.3.1.1.7.1.1.1 = INTEGER: 1
          .1.3.6.1.4.1.14823.2.3.3.1.1.7.1.1.2 = INTEGER: 2
          .1.3.6.1.4.1.14823.2.3.3.1.1.7.1.2.0 = STRING: "NO_SKWIRREL"
          .1.3.6.1.4.1.14823.2.3.3.1.1.7.1.2.1 = STRING: "24SKWIRREL"
          .1.3.6.1.4.1.14823.2.3.3.1.1.7.1.2.2 = STRING: "InternutOfSkwirrel"
          .1.3.6.1.4.1.14823.2.3.3.1.1.7.1.3.0 = INTEGER: enable(0)
          .1.3.6.1.4.1.14823.2.3.3.1.1.7.1.3.1 = INTEGER: enable(0)
          .1.3.6.1.4.1.14823.2.3.3.1.1.7.1.3.2 = INTEGER: disable(1)
          <snip>
          

          it looks like in includes/discovery/wifi there's nothing related to the aruba wifi mibs... I just see airespace, ruckus, and trapeze... but I'm not sure that I'm understanding this correctly.

          kwalitywalk_resolved.txt apwalk_resolved.txt kwalitywalk.txt

          Wolfspyre Wolf Noble added a comment - looking at this a bit closer:   snmpwalk -v3 -a 'SHA'  -l 'authPriv' -u 'USER' -A 'AUTH' -X 'PRIV' -x 'DES'  ap-65.wolfspyre.io .1.3.6.1.4.1.14823.2 -m all -O Xa I see much of the output resolving to the AI-AP-MIB mib: AI-AP-MIB::aiVirtualControllerKey.0 = STRING: xxxxx AI-AP-MIB::aiVirtualControllerName.0 = STRING: kwality AI-AP-MIB::aiVirtualControllerOrganization.0 = STRING: AI-AP-MIB::aiVirtualControllerVersion.0 = STRING: 8.10.0.7-8.10.0.7_87023 LSR AI-AP-MIB::aiVirtualControllerIPAddress.0 = IpAddress: 198.18.44.42 AI-AP-MIB::aiSSIDIndex[0] = INTEGER: 0 AI-AP-MIB::aiSSIDIndex[1] = INTEGER: 1 AI-AP-MIB::aiSSIDIndex[2] = INTEGER: 2 AI-AP-MIB::aiSSID[0] = STRING: "NO_SKWIRREL" AI-AP-MIB::aiSSID[1] = STRING: "24SKWIRREL" AI-AP-MIB::aiSSID[2] = STRING: "InternutOfSkwirrel" AI-AP-MIB::aiSSIDStatus[0] = INTEGER: enable(0) AI-AP-MIB::aiSSIDStatus[1] = INTEGER: enable(0) AI-AP-MIB::aiSSIDStatus[2] = INTEGER: disable(1) AI-AP-MIB::aiSSIDClientNum[0] = INTEGER: 0 AI-AP-MIB::aiSSIDClientNum[1] = INTEGER: 0 AI-AP-MIB::aiSSIDClientNum[2] = INTEGER: 0 AI-AP-MIB::aiSSIDHide[0] = INTEGER: disable(0) AI-AP-MIB::aiSSIDHide[1] = INTEGER: disable(0) AI-AP-MIB::aiSSIDHide[2] = INTEGER: disable(0) <snip> but looking at includes/definitions/mibs/aruba.inc.php, it looks like (to my ignorant mind) observium is referencing "WLSX-SWITCH-MIB" and it looks like aruba has decided to use different lately: snmpwalk -v3 -a 'SHA' -l 'authPriv' -u 'USER' -A AUTH' -X 'PRIV' -x 'DES' kwality.wolfspyre.io .1.3.6.1.4.1.14823.2 -m all -O Xn .1.3.6.1.4.1.14823.2.3.3.1.1.1.0 = STRING: xxxxxxx .1.3.6.1.4.1.14823.2.3.3.1.1.2.0 = STRING: kwality .1.3.6.1.4.1.14823.2.3.3.1.1.3.0 = STRING: .1.3.6.1.4.1.14823.2.3.3.1.1.4.0 = STRING: 8.10.0.7-8.10.0.7_87023 LSR .1.3.6.1.4.1.14823.2.3.3.1.1.5.0 = IpAddress: 198.18.44.42 .1.3.6.1.4.1.14823.2.3.3.1.1.7.1.1.0 = INTEGER: 0 .1.3.6.1.4.1.14823.2.3.3.1.1.7.1.1.1 = INTEGER: 1 .1.3.6.1.4.1.14823.2.3.3.1.1.7.1.1.2 = INTEGER: 2 .1.3.6.1.4.1.14823.2.3.3.1.1.7.1.2.0 = STRING: "NO_SKWIRREL" .1.3.6.1.4.1.14823.2.3.3.1.1.7.1.2.1 = STRING: "24SKWIRREL" .1.3.6.1.4.1.14823.2.3.3.1.1.7.1.2.2 = STRING: "InternutOfSkwirrel" .1.3.6.1.4.1.14823.2.3.3.1.1.7.1.3.0 = INTEGER: enable(0) .1.3.6.1.4.1.14823.2.3.3.1.1.7.1.3.1 = INTEGER: enable(0) .1.3.6.1.4.1.14823.2.3.3.1.1.7.1.3.2 = INTEGER: disable(1) <snip> it looks like in includes/discovery/wifi there's nothing related to the aruba wifi mibs... I just see airespace, ruckus, and trapeze... but I'm not sure that I'm understanding this correctly. kwalitywalk_resolved.txt apwalk_resolved.txt kwalitywalk.txt
          Wolfspyre Wolf Noble added a comment -

          When should I check back in on this?  Not trying to be a nag, just trying to set my expectations.

           

          Wolfspyre Wolf Noble added a comment - When should I check back in on this?  Not trying to be a nag, just trying to set my expectations.  

          Thanks, nothing right now.
          Just need time for review.

          landy Mike Stupalov added a comment - Thanks, nothing right now. Just need time for review.
          Wolfspyre Wolf Noble added a comment -

          snmpwalk output already added via attachment... need anything else?

           

           

          Wolfspyre Wolf Noble added a comment - snmpwalk output already added via attachment... need anything else?    

          General questions and device support can be discussed in our Discord channel, click here to join.


          Please make and attach additional information about the device:

          • full snmp dump from device:

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

            If device not support SNMP version 2c, replace -v2c with -v1.

          • If you have problems with discovery or poller processes, please do and attach these debugs:

            ./discovery.php -d -h <device>
            ./poller.php -d -h <device>

          • additionally attach device and/or vendor specific MIB files

          This comment is added automatically.

          bot Observium Bot added a comment - General questions and device support can be discussed in our Discord channel, click here to join . Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files This comment is added automatically.

          People

            landy Mike Stupalov
            Wolfspyre Wolf Noble
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: