Monitoring SSIDs and Rogue SSIDs

Monitoring SSIDs and Rogue SSIDs

Network

Monitoring SSIDs and Rogue SSIDs

Track the performance of every wireless network in your environment and monitor for unauthorised or unknown SSIDs detected by your access points.

Overview

SSIDs and Rogue SSIDs are discovered automatically from monitored wireless LAN controllers. Navigate to Network → Wireless Devices to access both views. The SSID view covers your own wireless networks and their performance, while the Rogue SSID view surfaces any SSIDs detected by your access points that do not belong to your environment.

SSIDs

The SSID list ranks all wireless networks across all monitored controllers by client count, access point coverage, transmitted bytes, and received bytes. This makes it straightforward to identify which networks are carrying the most load, which have the widest coverage, and whether any SSID is disproportionately overloaded relative to others in the environment.

Each SSID shows its name, connected client count, access point count, TX bytes, RX bytes, and last polled time. Tracking SSIDs at this level is useful for capacity planning, where if one SSID is consistently serving significantly more clients than others on the same hardware, it may indicate a need to rebalance client distribution or add additional access points to that coverage area.

Rogue SSIDs

Rogue SSIDs are wireless networks detected by your access points that are not part of your managed environment. These can include neighbouring office networks, personal hotspots, or potentially malicious networks attempting to impersonate legitimate SSIDs. Cloudmon surfaces all detected rogue SSIDs so teams can review and classify them.

A high rogue SSID count is common in dense environments such as office buildings where neighbouring organisations share airspace. Reviewing the rogue SSID list regularly and classifying known neighbouring networks reduces noise and makes it easier to spot genuinely suspicious SSIDs that warrant further investigation.

Troubleshooting

SymptomLikely CauseFix
SSIDs not appearing in the listThe parent controller has not completed its first full pollWait for the next poll cycle and confirm the controller is actively polling in the Wireless Devices overview
High rogue SSID countNeighbouring wireless networks are being detected by the access pointsReview the Rogue SSID list and classify known neighbouring networks to reduce noise and surface genuinely unknown SSIDs
SSID showing zero clients despite active usersClient data has not been refreshed since the last pollCheck the last polled time and wait for the next poll cycle; verify the controller is reachable from the probe