Why does an AC fail to report unauthorized APs after calibration is enabled

5

The possible causes are:
- Unauthorized AP detection is not enabled when calibration is enabled on the AC.
- After the calibration command is executed, the AC does not send neighbor detection messages to APs.
- APs do not receive neighbor detection messages from the AC.
- APs are not enabled to detect neighbors.
- APs do not report detected information to the AC.
- The AC does not receive neighbor information sent from APs.
- Errors occur when the AC is saving received neighbor information.

Other related questions:
Why does an AC fail to detect unauthorized APs after calibration is enabled
Perform the following operations to locate the fault: 1. Check whether unauthorized AP detection is enabled when calibration is enabled on the AC. 2. Check whether neighbor detection is enabled for the AP. Perform the following operations on the AC: 1. After the calibration command is executed, check whether the AC sends a neighbor detection message to the AP. 2. Check whether the AP receives the neighbor detection message from the AC. 3. Check whether the AP reports detected neighbor information to the AC. 4. Check whether the AC receives neighbor information sent from the AP. 5. Check whether errors occur when the AC is saving received neighbor information.

Why does an AC fail to report authorized APs after calibration is enabled
The possible causes are: - The AC is not configured with an AC ID or carrier ID. In versions earlier than V200R006, configure an AC ID and carrier ID for the AC and commit the configuration. In V200R006 and later versions, the configuration model is optimized and does not include any AC ID and carrier ID. - The AC does not send neighbor detection messages to APs, APs do not report detected neighbor information to the AC, or errors occur when the AC is saving received neighbor information.

Why does an AC fail to detect authorized APs after calibration is enabled
Perform the following operations to locate the fault: 1. For versions earlier than V200R006, check whether the AC is configured with an AC ID and a carrier ID. If not, configure an AC ID and a carrier ID for the AC and commit the configuration. For V200R006 and later versions, the AC ID and carrier ID do not exist due to the optimization of the configuration model. 2. Check whether the AC sends a neighbor detection message to an AP, whether the AP reports detected neighbor information to the AC, and whether errors occur when the AC is saving received neighbor information.

Why did STAs fail to search 802.11n signals after the AP is enabled with 802.11n
This is because the IEEE 802.11n draft protocol does not support a high throughput rate of the WEP or TKIP unicast ciphers. If a STA uses the WEP or WPA-TKIP encryption mode, the data transmission rate will decrease to 54 Mbit/s. In WEP or TKIP mode, if the STA uses the 802.11b/g/n NIC to associate with APs, it can only be associated with 802.11g APs. As a result, the displayed signal transmission rate is 54 Mbit/s but not the 802.11n rate. This is restricted by the IEEE 802.11 standard.

Failed to report eService alarms
Why does an eService alarm fail to be reported and how do I resolve the problem? 1. The network connection between eService and the device that is responsible for reporting alarms is abnormal. Handling method: Check whether the network configuration between the eService program and the reporting device is correct. If the network configuration is incorrect, configure the network again. 2. The SNMP Agent process is not started. Handling method: Log in to the device and start the SNMP Agent process. 3. SNMP communication parameters are incorrectly configured. Handling method: Correctly configure the SNMP communication parameters. For details about how to set SNMP parameters, see section 2.1.5 "Preparing Information for Configuration" in the eService User Guide.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top