Use this page to review or delete current pending alarms detected by the controller.
|
Alarm |
Severity |
Explanation |
| Alarm Link up | info | Physical link on controller is up. |
| Alarm Link down | critical | Physical link on the controller is down; check the connection. |
| Alarm auth fail | info | An administrator failed GUI login due to an authentication failure. |
| AP down | critical | An AP is down. Possible reasons for this are an AP reboot, an AP crash, or an Ethernet cable from the controller may be down. Also the AP may have connected to another controller. |
| Rogue AP Detected | critical | A rogue AP has been detected on the network. The message looks something like this: Rogue AP Detected Critical 06/04/2010 10:04:51 CONTROLLER (1:24194) ROGUE AP DETECTED. Station mac=0c:60:76:2d:fe:d9 bss=00:02:6f:3a:fd:89 by AP Ben-Cubei (18) |
| AP Software Version Mismatch | critical | The software version on the AP does not match the version on the controller. Automatic AP upgrade must have been turned off. Update the AP from the controller with either the CLI command ugrade ap same <ap id> force or upgrade ap same all force. You can also turn automatic upgrade back on with the CLI command auto-ap-upgrade enable. |
| AP init failure | major | AP initialization failed. |
| Software License expired | major | Controller software license has expired. To obtain additional licenses, see www.merunetworks.com/license. |
| 802.1X auth failure | info major minor |
Radius server authentication failed. To find out why, look at the Radius server log for the error message and also check the station log. If this happens only occasionally, you can ignore it. However, if this message appears repeatedly, the authentication failures could prevent a station from entering the network. In this case, check the Radius server to make sure the client and server have the same credentials. |
| MIC failure | The Michael MIC Authenticator Tx/Rx Keys provided in the Group Key Handshake are only used if the network is using TKIP to encrypt the data. A failure of the Michael MIC in a packet usually indicates that the WPA WPSK password is wrong. | |
| MIC Countermeasure activation | major | Two consecutive MIC failures have occurred (see above). |
| Radius Server switchover | major | A switchover from the Primary Authentication Radius Server to the
Secondary Authentication Radius Server occured. When this message
occurs, the Primary Radius server is configured but not reachable and
the Secondary Radius server is both configured and reachable. This
message is generated only for 802.1x switchover, not for Captive Portal
switchover.
An example looks like this: Radius Server Switchover Major 06/07/2010 14:09:57 Radius Server switches over from Primary <172.18.1.7> to Secondary <172.18.1.3> for Profile <wpa> |
| Radius Server switchover failed | major | A switchover from the Primary Authentication Radius Server to the Secondary Authentication Radius Server failed because the secondary server is not configured. When this message occurs, the Primary Radius server is configured but not reachable and the Secondary Radius server is not configured. This message is generated only for 802.1x switchover failure, not for Captive Portal switchover failure. An example looks like this: Radius Server Switchover Failed Major 06/07/2010 14:02:47 Primary Radius Server <172.18.1.7> failed. No valid Secondary Radius Server present. Switchover FAILED for Profile <wpa> Alarms Table(1 entry). |
| Restore Primary Radius Server | major | A switchover from the Secondary Authentication Radius Server to the Primary Authentication Radius Server occured. This alarm was generated while doing Radius fall back to the primary server after 15 minutes. This message is generated only for 802.1x primary Radius restore, not for Captive Portal restore. An example looks like this: Restore Primary Radius Server Major 06/07/2010 15:54:10 Security Profile <wpa> restored back to the Primary Radius server <172.18.1.7>. |
| Acct Radius server switchover | major | A switchover from either Accounting Radius Server (primary or secondary) to the other one occured. This message is generated only for 802.1x switchover, not for Captive Portal switchover. An example when the primary to secondary switch occurred looks like this: Accounting Radius Server Switch Major 06/07/2010 14:39:00 Accounting Radius Server switches over from Primary <172.18.1.7> to Secondary <172.18.1.3> for Profile <wpa>. |
| Acct Radius server switchover failed | major | An attempted switchover from one Accounting Radius Server to the other server failed. When this message occurs, the Primary Accounting Radius server is configured but not reachable and the Secondary Accounting Radius server is not configured. This message is generated only for 802.1x switchover failure, not for Captive Portal switchover failure. An example looks like this: Accounting Radius Server Switch Major 06/07/2010 14:22:26 Primary Accounting Radius Server <172.18.1.7> failed. No valid Secondary Accounting Radius Server present. Switchover FAILED for Profile <wpa>. |
| Master down | critical | N+1 Master controller is down and no longer in control; the slave controller will now take over. |
| Master up | critical | N+1 Master controller is up and running; this controller will now take control away from the slave controller. |
| CAC limit reached | major | Admission control in ATM networks is known as Connection Admission Control (CAC) - this process determines which traffic is admitted into a network. If this message occurs, the maximum amount of traffic is now occurring on the network and no more can be added. |
| N-upgrade license checkout failed | major | An 11N license is not available to support 11n mode for the specified AP300. You can either obtain an N license or reconfigure the AP to ABG mode. See the System Director 4.0 Release Notes for directions. |