I want to discover Aruba WAP

[Dhruv Gupta1]

HI team,

I have a requirement to discover Aruba WAP. I assume to achieve this we would need to discover controller handling SNMP. Can anybody provide me with guidance on this. Any help is much appreciated. 

[AJ-TechTrek]

Hi @Kuljeet1 ,

1. Why You Need to Discover the Controller
* Aruba WAPs (Access Points) are typically lightweight — they don’t store their full configuration or SNMP data locally.
* They are managed by an Aruba Mobility Controller (or Aruba Central cloud).
* The WAP inventory, configuration, and status are stored in the controller, and that’s where ServiceNow can pull their details.
* Therefore, you discover the controller via SNMP, and from that SNMP walk, you can extract WAP details.

2. ServiceNow Discovery Approach
A. Discover the Aruba Controller
1. SNMP Credentials
* Create an SNMP v2c or v3 credential in ServiceNow → Discovery → Credentials.
* SNMP v3 is recommended (more secure), but v2c is often used for simplicity.
* Test the credential against the controller’s management IP.
2. IP Range
* Add the controller’s management IP to an IP range in Discovery Schedules.
3. Classification
* Ensure that the controller is identified as a Network Gear device.
* OOB patterns may classify it as a generic network device; you may want to customize for Aruba vendor.

B. Extend the Pattern to Pull WAP Info
Once the controller is discovered, you can extend or create a SNMP-based pattern to:
* Query the Aruba-specific MIB OIDs for connected APs:
* Example OIDs:
* 1.3.6.1.4.1.14823 (Aruba enterprise MIB base)
* 1.3.6.1.4.1.14823.2.3.3.1.1.1 (AP name)
* 1.3.6.1.4.1.14823.2.3.3.1.1.2 (AP MAC address)
* 1.3.6.1.4.1.14823.2.3.3.1.1.3 (AP status)
* Map these values into the CMDB (cmdb_ci_access_point class).
* Link each WAP CI to the discovered controller via Depends on::Used by relationship.

C. Optional – Direct AP Discovery
If WAPs have IP addresses and respond to SNMP:
* You can add their IPs to Discovery.
* They may return minimal data (model, serial), but most config info will still come from the controller.

3. Best Practices
* MIB Files: Import Aruba MIB files into your SNMP MIB repository in ServiceNow so OIDs translate into meaningful names.
* Relationships: Use ServiceNow Identification & Reconciliation (IRE) to ensure each AP is linked to its controller without duplication.
* Scheduling: Run controller discovery more frequently than OS discovery, since AP connections can change often.
* Security: Use SNMPv3 with encryption/authentication to meet compliance.

Please appreciate the efforts of community contributors by marking appropriate response as Mark my Answer Helpful or Accept Solution this may help other community users to follow correct solution in future.
 

Thank You
AJ - TechTrek with AJ - ITOM Trainer
LinkedIn:- https://www.linkedin.com/in/ajay-kumar-66a91385/
YouTube:- https://www.youtube.com/@learnitomwithaj
Topmate:- https://topmate.io/aj_techtrekwithaj (Connect for 1-1 Session)
ServiceNow Community MVP 2025