Controllerless Networks

 View Only
last person joined: yesterday 

Instant Mode - the controllerless Wi-Fi solution that's easy to set up, is loaded with security and smarts, and won't break your budget
Expand all | Collapse all

SNMP OID - WLAN client role

This thread has been viewed 24 times
  • 1.  SNMP OID - WLAN client role

    Posted Nov 09, 2022 02:27 AM
    Hi community!

    I am using Aruba Instant on the latest firmware.

    Does anybody know if there is an OID for getting the assigned wlan client role via SNMP.
    The role is assigned by Aruba Clearpass when the wlan client is authenticated.

    Unfortunately I couldn't find anything in the aruba instant mib reference guide.

    Thx in advance!


  • 2.  RE: SNMP OID - WLAN client role
    Best Answer

    EMPLOYEE
    Posted Nov 09, 2022 07:40 AM

    Admitting that I don't know the specific answer to your question, I want to say that SNMP is the "old" way of doing things.  Using the rest api is the way forward:
    https://developer.arubanetworks.com/aruba-aos/docs/rest-apis
    https://www.arubanetworks.com/techdocs/Aruba-Instant-8.x-Books/89/Aruba-Instant-8.9.0.0-REST-API-Guide.pdf

    There is even a developer section on here where you can receive answers to your questions:  https://community.arubanetworks.com/community-home/digestviewer?communitykey=ea467413-8db4-4c49-b5f8-1a12f193e959



    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.

    HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
    ------------------------------



  • 3.  RE: SNMP OID - WLAN client role

    Posted Nov 10, 2022 01:04 AM
    Thank you very much! I'll look into it.


  • 4.  RE: SNMP OID - WLAN client role

    EMPLOYEE
    Posted Nov 14, 2022 06:23 AM
    The old fashioned SNMP method, which works:

    10.10.10.10 is a standalone MD, these OIDs should work for AOS8 clustered nodes as well.

    export MIBS=all
    snmpwalk -OX -v 2c -c public  10.10.10.10  .1.3.6.1.4.1.14823.2.2.1.4.1 | more

    WLSX-USER-MIB::nUserName[STRING: 0:1d:63:9:45:93][10.10.82.156] = STRING: 001d63094593 <------  MAC authenticated user
    WLSX-USER-MIB::nUserName[STRING: 0:50:56:51:dc:1f][0.0.0.0] = STRING:
    WLSX-USER-MIB::nUserName[STRING: 24:24:e:9c:40:15][10.10.82.215] = STRING: frieda@mini  <-------- TLS authenticated user

    # focusing on one device of interest by MAC address:
    snmpwalk -OX -v 2c -c public 10.10.10.10 .1.3.6.1.4.1.14823.2.2.1.4.1 | grep 24:24:e:9c:40:15


    WLSX-USER-MIB::nUserName[STRING: 24:24:e:9c:40:15][10.10.82.215] = STRING: frieda@mini
    WLSX-USER-MIB::nUserRole[STRING: 24:24:e:9c:40:15][10.10.82.215] = STRING: cppm-auth   <----------------------------------------- user-role VSA assigned
    WLSX-USER-MIB::nUserUpTime[STRING: 24:24:e:9c:40:15][10.10.82.215] = Timeticks: (23190900) 2 days, 16:25:09.00
    WLSX-USER-MIB::nUserAuthenticationMethod[STRING: 24:24:e:9c:40:15][10.10.82.215] = INTEGER: dot1x(4)
    WLSX-USER-MIB::nUserSubAuthenticationMethod[STRING: 24:24:e:9c:40:15][10.10.82.215] = INTEGER: eapTLS(5)
    WLSX-USER-MIB::nUserAuthServerName[STRING: 24:24:e:9c:40:15][10.10.82.215] = STRING: radius_pi-3    <------------------- RADIUS server
    WLSX-USER-MIB::nUserExtVPNAddress[STRING: 24:24:e:9c:40:15][10.10.82.215] = IpAddress: 0.0.0.0
    WLSX-USER-MIB::nUserApLocation[STRING: 24:24:e:9c:40:15][10.10.82.215] = STRING: ap515-f666
    WLSX-USER-MIB::nUserApBSSID[STRING: 24:24:e:9c:40:15][10.10.82.215] = STRING: f4:2e:7f:ef:66:70
    WLSX-USER-MIB::nUserIsOnHomeAgent[STRING: 24:24:e:9c:40:15][10.10.82.215] = INTEGER: 0
    WLSX-USER-MIB::nUserHomeAgentIpAddress[STRING: 24:24:e:9c:40:15][10.10.82.215] = IpAddress: 0.0.0.0
    WLSX-USER-MIB::nUserMobilityStatus[STRING: 24:24:e:9c:40:15][10.10.82.215] = INTEGER: wireless(5)
    WLSX-USER-MIB::nUserHomeVlan[STRING: 24:24:e:9c:40:15][10.10.82.215] = INTEGER: 0
    WLSX-USER-MIB::nUserDefaultVlan[STRING: 24:24:e:9c:40:15][10.10.82.215] = INTEGER: 82
    WLSX-USER-MIB::nUserAssignedVlan[STRING: 24:24:e:9c:40:15][10.10.82.215] = INTEGER: 82

    I'd be interested to see how one does this with an API.





    ------------------------------
    Shawn Adams
    ------------------------------