Wireless Access

last person joined: 19 hours ago 

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

clientmatch best practices

This thread has been viewed 19 times

  • 1.  clientmatch best practices

    Posted Feb 03, 2014 10:45 AM

    We're looking to do our 6.3.1.2 upgrade soon to take advantage of the arm improvements, and specifically clientmatch.

     

    Anyone using it now care to weigh in on how well it works? Also looking for any suggestions regarding the best way to implement it for best effect.

     

    From what I've seen, it's just a check box. Is there anything else that should or should not be done to have the best clientmatch experience for my users?

     

    Thanks!



  • 2.  RE: clientmatch best practices



  • 3.  RE: clientmatch best practices

    EMPLOYEE
    Posted Sep 21, 2016 07:01 AM

    I happen to sit in class right now (at a time where version 6.5.0.1 just got released) and got some advice from the instructor in tuning the power levels. Current best practice is to set the min to 12 and the max to 18. As I am lacking the experience in the field on this topic, I am just heralding the words from the classromm for your convenience.



  • 4.  RE: clientmatch best practices

    EMPLOYEE
    Posted Sep 21, 2016 07:10 AM

    12 and 18 is a good starting point.  There are other factors that go into power planning like the clients that will be connecting as well as AP density.  Starting at 12 and 18 is a good beginning.  Lower than 12 when your clients are not in the same room as the AP all the time is not good.  Higher than 18 could cause roaming issues when clients hold on too long.