Why would an ?Interfering AP detected? syslog message not contain the SSID information?

Aruba Employee

Product and Software: This article applies to all ArubaOS.

If an Aruba AP detects an interfering AP by listening to frames that do not contain the SSID, the syslog message it sends will not contain the SSID info. However, later when the AP learns the SSID of the interfering AP, it updates its monitored AP list, but does not send a new syslog message to reflect the SSID information.

Therefore, you may see "Interfering AP detected" syslog messages without the SSID.

Here is an example (marked in blue):

Jul 16 03:24:01 idcwl1-vlan28 [199.249.28.3] sapd[144]: <404003> <WARN> |AP PHNXAZKOAP41@166.33.107.34 sapd| AM 00:0b:86:27:57:10: Interfering AP detected with SSID Sam's Cafe and BSSID 00:23:69:3c:dc:fe
Jul 16 03:24:17 idcwl1-vlan28 [199.249.28.3] sapd[144]: <404003> <WARN> |AP PHNXAZKOAP41@166.33.107.34 sapd| AM 00:0b:86:27:57:10: Interfering AP detected with SSID Sam's Cafe and BSSID 00:23:69:3c:dc:fe

Jul 16 03:24:33 idcwl1-vlan28 [199.249.28.3] sapd[144]: <404003> <WARN> |AP PHNXAZKOAP41@166.33.107.34 sapd| AM 00:0b:86:27:57:10: Interfering AP detected with SSID

and BSSID 00:23:69:3c:dc:fe


Jul 16 03:24:52 idcwl1-vlan28 [199.249.28.3] sapd[144]: <404003> <WARN> |AP PHNXAZKOAP41@166.33.107.34 sapd| AM 00:0b:86:27:57:10: Interfering AP detected with SSID Sam's Cafe and BSSID 00:23:69:3c:dc:fe
Jul 16 03:25:24 idcwl1-vlan28 [199.249.28.3] sapd[144]: <404003> <WARN> |AP PHNXAZKOAP41@166.33.107.34 sapd| AM 00:0b:86:27:57:10: Interfering AP detected with SSID Sam's Cafe and BSSID 00:23:69:3c:dc:fe

Version history
Revision #:
1 of 1
Last update:
‎07-05-2014 04:35 AM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
Showing results for 
Search instead for 
Did you mean: