Controllerless Networks

last person joined: yesterday 

Instant Mode - the controllerless Wi-Fi solution that's easy to set up, is loaded with security and smarts, and won't break your budget
Expand all | Collapse all

Instant ARM ClientMatch configuration

This thread has been viewed 3 times
  • 1.  Instant ARM ClientMatch configuration

    Posted Apr 22, 2016 07:38 AM

    Greetings to all!

     

    Can anybody explain to me more exact a meaning of the next three fields in the RF/ARM settings and its affect on the fork of CM:

    CM calculating interval
    CM neighbor matching %
    CM threshold

    Thanks in advance!



  • 2.  RE: Instant ARM ClientMatch configuration

    EMPLOYEE
    Posted Apr 22, 2016 07:45 AM

    @mulleree wrote:

    Greetings to all!

     

    Can anybody explain to me more exact a meaning of the next three fields in the RF/ARM settings and its affect on the fork of CM:

    CM calculating interval - How often the ClientMatch Algorithm is run and consequently makes decisions.  The defaults are usually adequate and should not be changed.
    CM neighbor matching % -
    Used for load balancing.  Roughly determines how close access points need to be to be considered in the same "Neighborhood".
    CM threshold -
    In general the number of users on an AP before Client Match considers load balancing.

    Thanks in advance!


    Link to the userguide explanations are here:  http://www.arubanetworks.com/techdocs/Instant_42_WebHelp/InstantWebHelp.htm?_ga=1.43038629.1615771646.1440445030#UG_files/ARM/Configuring_ARM-Features.htm#Spectrum



  • 3.  RE: Instant ARM ClientMatch configuration

    Posted Apr 22, 2016 07:59 AM

     



  • 4.  RE: Instant ARM ClientMatch configuration
    Best Answer

    EMPLOYEE
    Posted Apr 22, 2016 08:35 AM

    If you lower the percentage, more APs will be considered in the same neighborhood.  That means a client could be load balanced or moved to more access points, which is not necessarily a good thing.  The percentage is really just a factor that could be adjusted by TAC or engineering for testing, but it never is.