Details

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

    Description

      Is it possible to include the stats from the Aruba APs for currently connected clients? I've attached the snmpwalk exports and latest Aruba MIBs.

       

      Happy to provide any other info on this!

      Attachments

        1. 8-10-0-8myagent.snmpwalk
          78 kB
        2. 8-11-2-0myagent.snmpwalk
          119 kB
        3. 8-6-0-21myagent.snmpwalk
          69 kB
        4. 8-7-1-6myagent.snmpwalk
          43 kB
        5. myagent.snmpwalk
          193 kB

        Activity

          [OBS-4448] Aruba AP Client Count

          We've done some more poking around on our side and found some potentially useful information. The info below seems to be outputting the attached clients of an Aruba AP and their IP (less interesting).

          snmpwalk -v2c -c COMMUNITY AP-IPADDR 1.3.6.1.4.1.14823.2.3.3.1.2.4.1.3

          iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.40.107.53.145.139.121 = IpAddress: 10.33.x.x
          iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.40.107.53.146.232.22 = IpAddress: 10.33.x.x
          iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.68.229.23.76.148.121 = IpAddress: 10.33.x.x
          iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.94.252.68.9.156.210 = IpAddress: 192.168.144.x
          iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.126.176.3.156.197.134 = IpAddress: 192.168.144.x
          iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.134.145.158.64.222.142 = IpAddress: 192.168.144.x
          iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.136.102.90.53.80.209 = IpAddress: 10.33.x.x
          iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.140.133.144.61.51.187 = IpAddress: 10.33.x.x

          iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.154.238.15.239.179.63 = IpAddress: 10.33.x.x
          iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.174.21.167.213.35.5 = IpAddress: 192.168.144.x
          iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.202.91.252.149.172.238 = IpAddress: 192.168.144.x
          iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.238.88.194.127.96.74 = IpAddress: 192.168.144.x
          iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.246.127.69.228.222.161 = IpAddress: 192.168.144.x

           

          js-sol James Shields added a comment - We've done some more poking around on our side and found some potentially useful information. The info below seems to be outputting the attached clients of an Aruba AP and their IP (less interesting). snmpwalk -v2c -c COMMUNITY AP-IPADDR 1.3.6.1.4.1.14823.2.3.3.1.2.4.1.3 iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.40.107.53.145.139.121 = IpAddress: 10.33.x.x iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.40.107.53.146.232.22 = IpAddress: 10.33.x.x iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.68.229.23.76.148.121 = IpAddress: 10.33.x.x iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.94.252.68.9.156.210 = IpAddress: 192.168.144.x iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.126.176.3.156.197.134 = IpAddress: 192.168.144.x iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.134.145.158.64.222.142 = IpAddress: 192.168.144.x iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.136.102.90.53.80.209 = IpAddress: 10.33.x.x iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.140.133.144.61.51.187 = IpAddress: 10.33.x.x iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.154.238.15.239.179.63 = IpAddress: 10.33.x.x iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.174.21.167.213.35.5 = IpAddress: 192.168.144.x iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.202.91.252.149.172.238 = IpAddress: 192.168.144.x iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.238.88.194.127.96.74 = IpAddress: 192.168.144.x iso.3.6.1.4.1.14823.2.3.3.1.2.4.1.3.246.127.69.228.222.161 = IpAddress: 192.168.144.x  

          Uploaded the newer MIB files for the new software verisons. Let me know if you need some new snmpwalk outputs to match!

          js-sol James Shields added a comment - Uploaded the newer MIB files for the new software verisons. Let me know if you need some new snmpwalk outputs to match!

          Let me know if you need any more info on this to move it forward. We've also moved to Enterprise licensing if that helps

          js-sol James Shields added a comment - Let me know if you need any more info on this to move it forward. We've also moved to Enterprise licensing if that helps

          Let me know if you need any additional info on this. We have a decent amount of APs across 8.6.x and 8.7.x so we can provide more walks if needed.

          js-sol James Shields added a comment - Let me know if you need any additional info on this. We have a decent amount of APs across 8.6.x and 8.7.x so we can provide more walks if needed.

          Docs attached

          js-sol James Shields added a comment - Docs attached

          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
            js-sol James Shields
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: