Wireless Access

 View Only
last person joined: 12 hours ago 

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

Clients disconnecting under high network load on ArubaOS 8.x

This thread has been viewed 28 times
  • 1.  Clients disconnecting under high network load on ArubaOS 8.x

    Posted Jan 19, 2021 10:28 AM
    Hello,

    We are experiencing issues at one Aruba deployment, which consists of 3 AP-305 devices, of which one is a virtual controller.
    They are on 8.7.1.1_78245 Ursa version.

    The issue we see is clients getting disconnected for some period of time, then reassociate to a different AP than the previous one.
    This issue manifests itself under moderately high network load (unthrottled upload from a device to the internet) and seems to be correlated with receiving or sending broadcast packets (DHCP, mDNS, ARP, broadcast ping).

    The issue manifested itself on 8.6.x ArubaOS versions as well, but it does not seem to be present in other deployments where we have 6.x ArubaOS.

    A packet dump of a client during one such disconnection is available, as well as debug syslog logs of the Aruba controller.

    The packet dump shows what has been summarized above: connection is going well, then a broadcast is sent/received, then the client is mostly sending packets and almost never receiving (to the exceptions of a few TCP keepalive packets that can get through), then we see old packets arriving from the remote server all at the same time, then after a few seconds we see WPA authentication, DHCP lease and so on taking place; the packet dump could be provided if needed.
    The debug syslog log seems to show the client reconnecting to a different AP than the previous one at around the same time the above is happening:
    Jan 18 18:44:02 2021 192.168.20.9 cli[5381]: <541004> <WARN> AP:AP-001 <192.168.20.9 24:F2:7F:C9:F0:7E> recv_sta_update: receive station msg, mac-b8:27:eb:cb:1a:6f bssid-c8:b5:ad:f0:7f:60 essid-HBF2-60732492 timestamp-1610991842-460151.
    Jan 18 18:44:03 2021 192.168.20.9 cli[5381]: <541004> <WARN> AP:AP-001 <192.168.20.9 24:F2:7F:C9:F0:7E> recv_sta_update: receive station msg, mac-b8:27:eb:cb:1a:6f bssid-c8:b5:ad:f0:7f:60 essid-HBF2-60732492 timestamp-1610991843-170049.
    Jan 18 18:44:14 2021 192.168.20.9 cli[5381]: <541004> <WARN> AP:AP-001 <192.168.20.9 24:F2:7F:C9:F0:7E> recv_sta_update: receive station msg, mac-b8:27:eb:cb:1a:6f bssid-c8:b5:ad:f0:7f:60 essid-HBF2-60732492 timestamp-1610991854-690348.
    Jan 18 18:44:15 2021 192.168.20.9 cli[5381]: <541004> <WARN> AP:AP-001 <192.168.20.9 24:F2:7F:C9:F0:7E> recv_sta_update: receive station msg, mac-b8:27:eb:cb:1a:6f bssid-c8:b5:ad:f0:7f:60 essid-HBF2-60732492 timestamp-1610991855-161352.
    Jan 18 18:45:14 2021 192.168.20.9 AP:AP-001 <192.168.20.9 24:F2:7F:C9:F0:7E> awc[5378]: [activate] awc_init_connection: 2973: cert verify: enable, domainame verify: enable
    Jan 18 18:45:27 2021 192.168.20.11 cli[5377]: <541004> <WARN> AP:AP-002 <192.168.20.11 C8:B5:AD:C7:07:F6> recv_sta_offline: receive station msg, mac-b8:27:eb:cb:1a:6f bssid-c8:b5:ad:f0:7f:60 essid-HBF2-60732492 timestamp-1610991927-172177.
    Jan 18 18:45:27 2021 192.168.20.11 cli[5377]: <541004> <WARN> AP:AP-002 <192.168.20.11 C8:B5:AD:C7:07:F6> recv_sta_offline: receive station msg, mac-b8:27:eb:cb:1a:6f bssid-c8:b5:ad:f0:7f:60 essid-HBF2-60732492 timestamp-1610991927-172974.
    Jan 18 18:45:28 2021 192.168.20.11 cli[5377]: <541004> <WARN> AP:AP-002 <192.168.20.11 C8:B5:AD:C7:07:F6> recv_sta_online: receive station msg, mac-b8:27:eb:cb:1a:6f bssid-c8:b5:ad:f0:7f:60 essid-HBF2-60732492 timestamp-1610991928-375447.
    Jan 18 18:45:28 2021 192.168.20.11 cli[5377]: <541004> <WARN> AP:AP-002 <192.168.20.11 C8:B5:AD:C7:07:F6> recv_stm_sta_update: receive station msg, mac-b8:27:eb:cb:1a:6f bssid-c8:b5:ad:f0:7f:60 essid-HBF2-60732492 timestamp-1610991928-378910.
    Jan 18 18:45:28 2021 192.168.20.9 cli[5381]: <541004> <WARN> AP:AP-001 <192.168.20.9 24:F2:7F:C9:F0:7E> recv_sta_update: receive station msg, mac-b8:27:eb:cb:1a:6f bssid-c8:b5:ad:f0:7f:60 essid-HBF2-60732492 timestamp-1610991928-399375.
    Jan 18 18:45:29 2021 192.168.20.11 AP:AP-002 <192.168.20.11 C8:B5:AD:C7:07:F6> stm[5411]: asap_update_client_name:16897 client b8:27:eb:cb:1a:6f name updated to SCN-011


    Thank you in advance,



    ------------------------------
    N. Douma
    ------------------------------


  • 2.  RE: Clients disconnecting under high network load on ArubaOS 8.x

    EMPLOYEE
    Posted Feb 02, 2021 08:09 PM
    Do you have broadcast filtering enabled on those SSIDs?

    ------------------------------
    Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
    ------------------------------



  • 3.  RE: Clients disconnecting under high network load on ArubaOS 8.x

    Posted Feb 18, 2021 03:41 AM
    Yes we had broadcast filtering enabled on those SSIDs. The problem appeared to be the roaming settings.

    Disabling 802.11k and 802.11v  solved the issue. 802.11r remained enabled


    ------------------------------
    Athanasios Karapatis
    ------------------------------