Information About Configuring SNMP Traps
Simple Network Management Protocol (SNMP) Traps are alert messages sent from a remote SNMP-enabled device such as the controller, to an SNMP manager. Traps are unreliable because the receiver does not send acknowledgments when the device receives traps. Hence, the sender cannot determine if the traps were received.
In order 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, no notifications are sent.
In order to enable multiple hosts, you must specify separate snmp-server host command for each host. You can specify multiple notification types in the command for each host. When multiple snmp-server host commands are given for the same host and notification of either trap or inform, each command overwrites the previous command. Only the last snmp-server host command is taken into account. For example, if you enter an snmp-server host inform command for a host and then enter another snmp-server host inform command for the same host, the second command replaces the first.
Specify the snmp-server enable traps wireless <TrapName> command in order to specify which SNMP notifications are sent globally. In order 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. However, some notification types cannot be controlled with the snmp-server enable command. And some notification types are enabled by default . For example, few AP related traps crash, register, and noradiocards are enabled by default.