Normal
The AP is operating normally and had its software and configuration settings successfully updated by the controller. |
Warning (rotating)
The AP is performing one of the following actions: | |||
Action |
Description |
||
Enabling WLAN services |
The AP is enabling wireless services for all WLANs. |
||
Establishing tunnel |
A secure management tunnel is being established to the AP. |
||
Installing firmware |
New software has been successfully uploaded to the AP. The AP will restart to activate the new software. |
||
Waiting for manager |
When teaming is active, a newly discovered AP will temporarily be in this state while it waits for the team manager to add it. Teaming can only by configured using the Advanced UI. |
||
Restarting |
The AP is restarting. |
||
Resetting configuration |
The AP configuration is being reset to factory defaults. This is normal and will occur when the software version on the controller is changed, or if the AP is not synchronized. |
||
Restoring configuration |
The AP is currently restoring its previous configuration settings. |
||
Suspicious device |
The AP unexpectedly requested new authentication certificates from the controller. Possible causes are as follows:
This is a possible security breach that should be investigated before authorizing the AP again. |
||
Uploading configuration |
Configuration settings are currently being sent to the AP. |
||
Uploading firmware |
The controller is uploading new software to the AP. Wait until the operation completes. |
||
Validating configuration |
The controller is waiting for the AP to send its configuration. |
||
Validating firmware |
The controller is waiting for the AP to send its software version number. |
||
Waiting for acceptance |
The AP has been authorized by the controller. However, the AP has not yet selected the controller to function as its controller. (If multiple controllers replied to the AP discovery request, the AP may choose to connect with another controller.) |
||
Validating capabilities |
The capabilities of the AP are being identified by the controller. |
Warning
The AP is operational, but is experiencing one of the following conditions: | |||
Condition | Description | ||
AP limit exceeded |
The maximum number of APs are already being managed by the controller as defined on the Network > Access Points > Controlled Mode page. |
||
Authentication tunnel failure |
The AP and/or controller authentication feature was enabled in the Advanced UI, but the shared secrets on the AP and controller do not match. |
||
Detected |
The AP was detected by the controller. |
||
Suspicious device |
The AP unexpectedly requested new authentication certificates from the controller. Possible causes are as follows:
This is a possible security breach that should be investigated before authorizing the AP again. |
||
Synchronized/License violation |
Although the AP is synchronized, it is non-functional (quarantined) due to a license violation. You must change the configuration to omit the affected licensed feature or acquire and install a valid license. |
||
Unsynchronized/License violation |
The AP is not synchronized but can continue operation. However, if synchronized, it will become non-functional as described above for Synchronized/License violation. Before synchronizing, either change the configuration to omit the affected licensed feature or acquire and install a valid license. |
Problem
The AP is not operating normally due to one of the following conditions: | |||
Condition | Description | ||
Firmware failure |
New software failed to upload to the AP. The controller will retry soon. |
||
Incompatible settings |
Local mesh has been provisioned on the AP (using the Advanced UI), but:
|
||
Not authorized |
The AP could not be authenticated by the controller. This may be due to invalid authentication credentials supplied by the AP. (Authentication settings used by the controller are defined on the Controller >> Security > Controlled APs page in the Advanced UI.) You should accept the AP unless it is an actual rogue. |
||
Not responding |
The AP has stopped sending management information to the controller. Rediscovery may re-establish the connection. If not, the AP may have lost power or a network failure has occurred. |
||
Priority conflict |
More than one controller responded to the AP discovery request with the same priority. The AP is therefore unable to select a controller to function as its controller. The AP will retry its discovery request shortly. You must fix the priority conflict by changing the priority setting for one of the controllers (Controller >> Management > Device discovery page in the Advanced UI). |
||
Unconfigurable |
This AP cannot be added because the maximum number of configured APs has been reached. To add this AP you must first remove one or more currently configured APs. |
||
Unsupported product |
No suitable software is available for this AP on the controller. You should upgrade the controller software so that the newly-introduced product can be recognized. |
||
Wrong product |
The AP was created with a product type that does not match the detected product type. This can occur when an AP is manually added to a group with the wrong product type in the Advanced UI. You should verify and fix the product type. |
Admin Down
Indicates that the Admin Down flag is set for this AP. |