Wireless Access

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

Client match doesnt work if the APs are configured as AP specific --But they are in same ARM profile

This thread has been viewed 0 times

  • 1.  Client match doesnt work if the APs are configured as AP specific --But they are in same ARM profile

    Posted Jun 03, 2016 03:18 AM

    Hi

    I have configured APs in the AP specific group.

    eg: ap-name "B3-RR3-R2-W078"
    regulatory-domain-profile "NO_DFS"

    ap-name "B3-RR3-R3-W338"
    regulatory-domain-profile "NO_DFS"

     

    There is no difference in the arm profile for the 2 APs.

    Both the above mentioned Aps belong to the AP-group mentioned below:

    ap-group "Ward_Tower(RH)_L2"
    virtual-ap "civetcat_dot1x"
    virtual-ap "woodpecker_wpa2-psk"
    virtual-ap "parrot_wpa2-psk"
    virtual-ap "penguin_wpa2-psk"
    virtual-ap "TMEP_wpa2-psk"
    virtual-ap "wireless@sg_cp"
    virtual-ap "wireless@sgx_dot1x"
    virtual-ap "vocera_vap"

     

    They both belong to the same arm profile. Client match is enabled.

    But the user doesnt roam to another AP.

     



  • 2.  RE: Client match doesnt work if the APs are configured as AP specific --But they are in same ARM profile

    EMPLOYEE
    Posted Jun 03, 2016 07:30 AM

    The client decides when it will roam to another AP.   Client Match is not a roaming mechanism; it will help if it believes a client is "sticky".  What is your ARM Maximum Transmit Power for those APs?  You could have the power too high.