Configuring Alarm Rules for Wireless Monitoring

Configuring Alarm Rules for Wireless Monitoring

Wireless Monitoring

Configuring Alarm Rules for Wireless Monitoring

Set up threshold-based alarms for wireless LAN controllers, access points, SSIDs, and clients so Cloudmon alerts your team the moment a wireless metric or availability condition breaches its defined limit.

Overview

Wireless devices in Cloudmon are monitored via SNMP when a WLC or access point is added as an SNMP device. Cloudmon automatically classifies them under Wireless Devices and applies specialised monitoring views. Alarm rules can be configured at the group level for consistent coverage across all wireless infrastructure, or individually per device for site-specific thresholds.

There are two ways to configure alarm rules for wireless devices:

  • Group level: Navigate to Settings → Configurations → Alarm Rules → Add, select the entity type, add triggers, and associate the rule to a group.
  • Individual device: Navigate to Network → Wireless Devices → [Select Device] → Settings → Alarm Rule → Add Trigger.

How to Configure an Alarm

Each alarm is built around a simple IF/THEN model, where you select a metric, set a threshold, and define what happens when it is breached. Learn more.

Common Use Cases

Below are recommended alarm configurations for the most common wireless monitoring scenarios:

Use CaseDevice TypeMetricSuggested ThresholdWhy
WLC CPU under heavy loadWLCCPU UtilisationAbove 80% for 3 intervalsA heavily loaded WLC begins dropping client associations and slowing roaming handoffs, impacting all users across every AP it manages.
Access point goes offlineAccess PointAvailabilityBelow 100% for 1 intervalAn offline AP creates a coverage gap that prevents devices in that area from connecting, causing connectivity complaints before IT is aware.
AP client count nearing capacityAccess PointClient CountAbove 50 for 2 intervalsOverloaded APs reduce per-client throughput significantly. Early warning allows redistribution of clients or addition of a new AP before degradation becomes noticeable.
WLC bandwidth utilisation highWLCBandwidth UtilisationAbove 80% for 2 intervalsHigh controller bandwidth usage degrades throughput for all clients before the uplink saturates completely.
Rogue SSID detectedWLCRogue SSID CountAbove 0 for 1 intervalRogue SSIDs indicate an unauthorised access point broadcasting in your environment, which is a potential security risk and policy violation.

Viewing and Managing Triggers

Once saved, all triggers for a wireless device are listed in the Triggers table under the Alarm Rule section. Each row shows the trigger title, alarm severity, notification configuration, and script settings. Triggers can be edited or deleted using the action icons on the right.

To apply consistent alarm rules across all WLCs or all access points without configuring each device individually, save the rule as a reusable template under Settings → Configurations → Alarm Rules and associate it to a group.