Wireless Access

last person joined: 17 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

Client Match Attempts/Successes - 6.3.0.0

This thread has been viewed 0 times
  • 1.  Client Match Attempts/Successes - 6.3.0.0

    Posted Jul 03, 2013 02:31 PM

    In Dashboard under Access Points it shows columns for Client Match Attempts and Successes. For example, I have one AP with 119 attempts and 107 successes. Can not find in the user guide or anywhere else a definition of successes and  failures. My best guess is that the system could not find a better AP for a poor performing client since the APs with higher numbers seem to be in more thinly covered areas.



  • 2.  RE: Client Match Attempts/Successes - 6.3.0.0

    EMPLOYEE
    Posted Jul 03, 2013 02:40 PM

    You are correct. On the controller you can run the command show ap arm client-match unsupported which can help you isolate which clients have been flagged as unsteerable.

     

    You can also change the threshold for the number of consecutive failed steer attempts before the client is marked as unsteerable.

    cm-max-steer-fails (rf arm-profile)

    Default is 5.

     



  • 3.  RE: Client Match Attempts/Successes - 6.3.0.0

    Posted Jul 04, 2013 10:05 AM

    Thanks that a great help.  Do you also happen to know how they define the "Client Health" stat under Performance?



  • 4.  RE: Client Match Attempts/Successes - 6.3.0.0

    Posted Jul 05, 2013 03:51 AM

    Clientmatch aims at helping the clients with poor health in a given wireless network. The "Clien Health" represents the connectivity and performance of given clients. So Green, orange and red colors on the chart means good, questionable and bad health of associated clients in the network.



  • 5.  RE: Client Match Attempts/Successes - 6.3.0.0

    EMPLOYEE
    Posted Jul 12, 2013 01:13 PM

    Client health = SNR