Extreme Wireless Controller Monitoring in ObserveOps
ObserveOps (formerly known as AIOps) supports monitoring of Extreme Wireless Controllers. You can discover and monitor Extreme Wireless Controllers using the Wireless Discovery Profile with SNMP credentials (V1, V2, and V3).
Prerequisites
- The Extreme Wireless Controller is reachable from the ObserveOps server or collector.
- SNMP is enabled on the Extreme Wireless Controller.
- You have the SNMP community string (V1/V2) or authentication credentials (V3).
- Ports
161/UDP(SNMP) are open between the ObserveOps server and the controller.
How It Works
ObserveOps discovers the Extreme Wireless Controller through the Wireless Discovery Profile using SNMP. After discovery, ObserveOps polls the controller at regular intervals to collect metrics across wireless-specific monitoring templates. The collected data appears in monitor dashboards, alerts, and topology views.
Discover an Extreme Wireless Controller
- Go to Menu and select Settings.
- Select Discovery, then select Wireless Discovery Profile.
- Click Create Wireless Discovery Profile.
- In the Wireless Type dropdown, select Extreme Wireless.
- Select or create an SNMP Credential Profile:
| SNMP Version | Required Fields |
|---|---|
| V1 / V2 | Community String, Port (default: 161) |
| V3 | Username, Authentication Protocol, Authentication Password, Privacy Protocol, Privacy Password |
- Enter the IP address or IP range of the Extreme Wireless Controller.
- Fill in the remaining discovery profile fields — Group, Tags, Collector, and Polling Interval.
- Click Save to create the discovery profile.
- Click Discover Now to run the discovery immediately, or let it run on the scheduled interval.
After discovery, the Extreme Wireless Controller appears in Device Inventory with the monitor type Extreme Wireless.
Available Monitoring Views
Once discovered, the Extreme Wireless Controller monitor provides the following tabs:
| Tab | What It Shows |
|---|---|
| Overview | Health status, uptime, CPU usage, memory usage, total associated clients, active SSIDs |
| Access Points | List of APs managed by this controller — AP name, IP, state, client count, channel, signal strength |
| Clients | Connected wireless clients — MAC address, IP, SSID, RSSI, data rate, association time |
| SSIDs | Active SSIDs — SSID name, VLAN, security type, client count |
| Interfaces | Controller network interfaces — interface name, state, speed, traffic in/out |
Example
A campus IT team manages 120 access points across three buildings using an Extreme Wireless Controller. They add a Wireless Discovery Profile for the controller IP with SNMP V3 credentials. ObserveOps discovers the controller and immediately starts collecting AP health, client counts, and SSID performance. When a building's AP cluster shows high client density, the operations team sees the alert in ObserveOps before users report connectivity issues.
Troubleshooting
Extreme Wireless Controller does not appear after discovery
Cause: SNMP is disabled or the community string/credentials are incorrect.
Fix: Test SNMP connectivity from the ObserveOps server using snmpwalk -v2c -c <community> <controller-ip>. Correct the credential profile and retry discovery.
Discovery completes but shows 0 access points
Cause: The SNMP polling user does not have read access to the wireless MIB tables. Fix: On the Extreme Wireless Controller, confirm the SNMP user or community has read access to wireless management OIDs. Consult the Extreme Networks documentation for the correct MIB access policy.
Monitor shows "Down" immediately after discovery
Cause: ICMP is blocked on the network path between the collector and the controller. Fix: Confirm ICMP ping is allowed. If ICMP is intentionally blocked in your environment, set Availability Check to SNMP only in the monitor settings.
Known Limitations
- Configuration push and firmware upgrade are not supported for Extreme Wireless Controllers in this release.
- Controllers managed via ExtremeCloud IQ (cloud-managed) may require additional SNMP configuration on the cloud portal.