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

Client not showing up in client-match

This thread has been viewed 0 times

  • 1.  Client not showing up in client-match

    MVP
    Posted Aug 19, 2015 05:44 AM

    What would be a possible cause for an 802.11ac (intel 7260) client to not show up in client-match while it is connected in 2.4Ghz for several hours while all AP's are AP-205's?

     

    Both summary, history, unsteerable show no attemps or whatever for that client.

    After changing the preferred band in the clients own setting to 5GHz he is now connecting properly but still.. I would have hoped that client-match would have steered him or at least understand why it didn't.

     

     

     

     



  • 2.  RE: Client not showing up in client-match

    Posted Aug 19, 2015 07:20 AM

    What version of AOS are you running ?



  • 3.  RE: Client not showing up in client-match

    MVP
    Posted Aug 19, 2015 07:36 AM

    ArubaOS 6.4.3.3



  • 4.  RE: Client not showing up in client-match

    EMPLOYEE
    Posted Aug 19, 2015 08:04 AM

    Koenv,

     

    If you can replicate the circumstances, please try:

     

    show ap virtual-beacon-report client-mac <mac of client>

    ..to see what access points have seen that client, potentially.  If a client is connected to the G band, it must be weaker than Client Match Band Steer G Band Max Signal   (-45 by default) and the 802.11a access point we want to steer it to must also be stronger than Client Match Band Steer A Band Min Signal (-75 by default).  That is to prevent a user that has a good G signal from being steered to a bad 802.11a signal.

     

    Here are the rules:

     

    - If the client is connected at -45 or stronger to an 802.11g AP, we will not attempt to steer the client.  

    - If the 802.11a AP we want to steer it to sees it as weaker than -75, we will not attempt to steer the client.

    - We only attempt to steer to the 802.11a side of the access point it is currently connected to.

     

    If any of those conditions existed, there would not be a steer attempt, even if the client was connected for hours.  We have seen that if we steer a client to an 802.11a access point that is weaker than -75, it will just keep going back to the 802.11g side of the AP.