Explains SNMP wireless trap functionality and outlines configuration procedures for enabling traps via GUI and CLI, including access points, wireless client, mesh, RF, rogue, mobility, RRM, and general traps, with instructions for verification.

An SNMP trap is an alert message sent from SNMP-enabled devices to an SNMP manager. It does not require acknowledgment from the receiver and does not confirm receipt at the sender.

SNMP trap configuration details

To configure the controller to send SNMP notifications, you must enter at least one snmp-server host command. If you do not enter an snmp-server host command, the system does not send any notifications.

To enable multiple hosts, specify a separate snmp-server host command for each host.
You can specify multiple notification types in the command for each host.
If you issue multiple snmp-server host commands for the same host and notification type (trap or inform), each new command overwrites the previous one. The system considers only the most recent snmp-server host command.
For example, entering an snmp-server host inform command for a host and then entering another for the same host causes the second command to replace the first.

To specify which SNMP notifications are sent globally, use the snmp-server enable traps wireless <TrapName> command. For a host to receive wireless notifications, at least one snmp-server enable traps wireless <TrapName> command and the snmp-server host command for that host must be enabled.

Some notification types cannot be controlled with the snmp-server enable command.
Some notification types are enabled by default. For example, a few Access Point (AP)-related traps such as crash, register, and noradiocards are enabled by default.

Note

On physical Cisco Catalyst 9800 Series Wireless Controller appliances, such as Cisco Catalyst 9800-L, 9800-40, and 9800-80, the SNMP trap rate is limited to 4 traps per second. On virtual Catalyst 9800 appliances, the SNMP trap rate supports up to 300 traps per second.

Configure SNMP Traps (GUI)

Enable and customize Simple Network Management Protocol (SNMP) trap notifications for wireless events by using the GUI.

Procedure

	1.	Choose Administration > Management > SNMP. The SNMP page appears. By default, SNMP mode is disabled. Click the SNMP Mode toggle button to enable or disable SNMP.
	2.	Choose the Wireless Traps tab. By default, only the Access Point trap is enabled; all other SNMP wireless traps are disabled. To enable all wireless traps, click Enable All.
	3.	Select wireless SNMP traps. Select the wireless SNMP trap to enable. Click the Select All check box to enable all trap flags in the trap. To enable all trap flags in the Mesh trap section, check the Select All check box in the section. Clear the Select All check box to deselect all trap flags. Note In the Access Point trap, the Crash, No Radio Cards, and Register trap flags are enabled by default. Select the Broken Antenna trap flag to detect a broken antenna. Select the AP Stats trap flag to enable traps for access point statistics.
	4.	Click Apply.

By configuring SNMP trap notifications, network management systems receive wireless event alerts based on your selections.

Enable AP Traps (CLI)

Configure Simple Network Management Protocol (SNMP) traps on your device to monitor wireless access point (AP) events.

This configuration helps you monitor AP status and troubleshoot issues.

Procedure

	1.	Enter the global configuration mode. Example: `Device# configure terminal`
	2.	Enable wireless SNMP traps for APs. Example: `Device# snmp-server enable traps wireless AP`
	3.	Enable or disable AP-related trap flags. Example: `Device# trapflags ap authorization` Example: `Device# trapflags ap authorization broken-antenna crash interfaceup ipaddrfallback mfp mode noradiocards register` The crash, noradiocards, and register trap flags are enabled by default.

Your device sends SNMP traps for wireless AP events.

This configuration helps you monitor AP status and identify issues.

Enable wireless client traps (CLI)

Configure Simple Network Management Protocol (SNMP) traps on your device to monitor wireless client events. This setup helps you manage and troubleshoot your network.

Procedure

	1.	Enter the global configuration mode. Example: `Device# configure terminal`
	2.	Enable wireless client traps. Example: `Device# snmp-server enable traps wireless bsnMobileStation`
	3.	Enable or disable 802.11ax-related trap flags for wireless clients. Example: `Device# trapflags client dot11 assocfail` Example: `trapflags client dot11 assocfail associate authenticate authfail deauthenticate disassociate`
	4.	Enable trap flags that are excluded for clients. Example: `Device# trapflags client excluded`

Your device generates SNMP traps for wireless client events. Your network monitoring tools receive and process these notifications.

Enable Mesh Traps (CLI)

You can configure a device to send wireless-mesh Simple Network Management Protocol (SNMP) traps and control mesh trap notifications.

Before you begin

To enable mesh traps with CLI commands, complete each step in order.

Procedure

Enter the global configuration mode.

Example:

Device# configure terminal

Enable wireless-mesh traps.

Example:

Device# snmp-server enable traps wireless MESH

Enable or disable mesh trap flags.

Example:

Device# trapflags mesh abate-snr

Example:

trapflags mesh abate-snr authentication-failure child-moved excessive-children excessive-hopcount onset-snr parent-change

The device sends wireless-mesh SNMP traps according to the mesh trap flags you selected.

Enable RF Traps (CLI)

You can configure your device to send radio frequency (RF) traps for wireless networking events using CLI commands.

Before you begin

To enable radio frequency (RF) traps using CLI commands, complete the steps below.

Procedure

	1.	Enter global configuration mode. Example: `Device# configure terminal`
	2.	Enable wireless RF-related traps. Example: `Device# snmp-server enable traps wireless bsnAutoRF`
	3.	Enable or disable sending traps related to radio resource management (RRM) parameter updates. Example: `Device# trapflags rrm-params channels tx-power`
	4.	Enable or disable traps related to the radio resource management (RRM) profile. Example: `Device# trapflags rrm-profile coverage` Example: `trapflags rrm-profile coverage interference load noise`

The device sends RF-related SNMP traps to support network monitoring of wireless events.

Enable rogue, mobility, RRM, and general traps (CLI)

Configure SNMP traps for wireless rogue devices, mobility events, Radio Resource Management (RRM), and general controller events on your device using the CLI.

Before you begin

Use these steps to enable rogue, mobility, RRM, and general traps.

Procedure

	1.	Enter global configuration mode. Example: `Device# configure terminal`
	2.	Enable traps for wireless rogue. Example: `Device# snmp-server enable traps wireless rogue`
	3.	Enable rogue AP detection trapflag. Example: `Device# trapflags rogue-ap`
	4.	Enable rogue client detection trapflag. Example: `Device# trapflags rogue-client`
	5.	Enable traps for wireless mobility. Example: `Device# snmp-server enable traps wireless wireless_mobility`
	6.	Enable anchor trapflags. Example: `Device# trapflags anchor`
	7.	Enable traps for wireless RRM. Example: `Device# snmp-server enable traps wireless RRM`
	8.	Enable or disable the RRM parameter related traps, when the RF manager group changes. Example: `Device# trapflags rrm-params group`
	9.	Enable general controller traps. Example: `Device# snmp-server enable traps wireless bsnGeneral`

SNMP trap notifications for rogue, mobility, RRM, and general controller events are enabled on the device and will be sent to your configured SNMP management system.

Verify SNMP wireless traps

To verify the various SNMP traps enabled, use this command:

Device# show run | sec trapflag 
trapflags ap crash
trapflags ap noradiocards
trapflags ap register
trapflags rogue-client

Need help?

Open a support case

(Requires a Cisco Service Contract)

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.