Wireless Access

last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

Clients Disconnecting

This thread has been viewed 24 times

  • 1.  Clients Disconnecting

    Posted Feb 11, 2020 01:55 PM

    We are having some issues where clients are being disconnected from the wireless network. The only error that shows up in the log is the following:

    wms[3600]: <126118> <3600> <WARN> |wms| |ids| AP(9c:8c:d8:e5:cf:40@3YL4CH01P3): Phony BSSID Detection: An AP detected a phony BSSID 6c:f3:7f:de:22:c0 on CHANNEL 11 belonging to AP (NAME 3YL4CH02P5 and MAC 6c:f3:7f:c5:e2:2c). Additional Info: SSID:Employee.

    This error shows up in all the SSID the AP is transmitting and where the clients connect. Its actually detecting, not protecting.

     

    Could this be the reason the clients are being disconnected? We didn't have this issue before and the controller configuration remains the same.

     



  • 2.  RE: Clients Disconnecting

    MVP GURU
    Posted Feb 11, 2020 02:06 PM

    Have you tried re-naming the SSID and testing, or walking the area using a WLAN monitoring tool? It looks like another WLAN in the area is also using "Employee" as its SSID. It is possible that they are trying to associate with the other Employee SSID, and they fail leading to disconnects.



  • 3.  RE: Clients Disconnecting

    Posted Feb 11, 2020 02:26 PM

    Forgot to mention that the Controllers are in the process of having their AOS upgraded. The controller with the 5 APs that are disconnecting clients is already using AOS 8.6. AP's nearby, in higher floors, are still in the older Controller using AOS 6.5. Could this be causing the SSID conflict? This is also happening with another SSID named IntraMobile.



  • 4.  RE: Clients Disconnecting

    MVP GURU
    Posted Feb 12, 2020 09:00 AM

    It is not recommended to have two environments running in the same RF space just due to the fact that it will treat them like two separate managed domains. If the clients are able to authenticate and join the v6 environment as well you should see the clients performing a hard roam to v6 from v8 to v8 from v6. The client will lose connectivity for a brief moment while it associates to the other environment, but should come back up. How often that happens will mostly be decided by the client, and how the roaming aggressiveness is configured. If you were to cut the rest of the APs in the area over to v8, I would bet that this issue would go away.