Wireless deep discovery and troubleshooting
What it is
Deep discovery is an on-demand SNMP scan, executed by the Local Agent, that pulls the vendor-specific tables of your APs: radios, SSIDs, connected clients, hardware details. Basic status (online/offline, ping) works without it; the rich tables need it.
The stored SNMP credentials are resolved securely on the server side — the Agent fetches them by device id, your browser never sees them.
How to run it
- Whole fleet: in the sidebar, click Deep Data. A “Deep Discovery” progress overlay appears in the top-right corner showing the device count and status (“Dispatching to Agent…” → “Scanning X APs via Local Agent…”). When done, click Accept.
- Single AP: open the AP’s detail view and click Deep Discover in the header.
The tables refresh when the scan completes. Run it again whenever you change SSIDs, radios or firmware and want the inventory updated.
Troubleshooting
- “Local Agent not available” — the Agent is not running or not reachable. Start
CreaRackAgent.exeon its PC and check it shows as online in the Observatory’s Fleet Manager. See [[crearack—terminal—local-agent]]. - The progress bar turns orange / times out — some APs did not answer in time. Usual causes: wrong SNMP credentials (fix them via Config on the AP), the AP filtering SNMP to certain source IPs (allow the Agent’s PC), or the device being briefly unreachable. Re-run Deep Data afterwards.
- “Radios” / “SSIDs” / “Connected Clients” are empty — deep discovery has never completed for that AP, or the vendor’s OID profile does not expose those tables. Run Deep Discover first; if still empty, the model may need a custom OID profile.
- Client counts look stale — counts refresh with regular polling, but the per-client table comes from the last deep discovery. Re-run it for a current snapshot.
- An uploaded MIB shows “Source” instead of “Compiled” — this is a supported mode, not an error. Some vendor MIB files do not compile with the strict compiler; CreaRack then extracts the OIDs directly from the MIB source and deep discovery works normally with them. Only a red Failed (0 OIDs) means the file was unusable.
- An AP went offline after a credential change on the device — update the credentials in CreaRack too: detail view → Config → save the new community/v3 credentials.
Related
- [[crearack—wireless—add-access-points]] — discovery and destinations
- [[crearack—terminal—local-agent]] — installing and checking the Local Agent
- [[crearack—monitoring—configurar-snmp]] — SNMP credentials in depth
Véase también
- [[crearack—monitoring—que-es-wireless]]
- [[crearack—wireless—add-access-points]]
- [[crearack—terminal—local-agent]]