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.

RAP termination in 8.1

This thread has been viewed 0 times
  • 1.  RAP termination in 8.1

    Posted Oct 02, 2017 02:33 AM

    [accidental duplicate, mod please delete this post]


    Longtime reader, first time poster. We're starting to evaluate 8.1 for deployment and have an extensive RAP setup that needs to be migrated. I'm still working to understand the differences in 8.1 and one aspect that is confusing is RAP termination. We plan on using one virtual MM and rely on VMware clustering to ensure the VM stays up. According to some documentation the RAP will need to terminate on a NAT'd IP of the MM. Will the MM then "pass on" the RAP to terminate on an MD in a clustered environment? Does the MD also then need a public IP? Also, the RAPs must authenticate on the MM via certificates and not PSK, is that right? Broadly speaking, I'd like to be clear on how the RAP works in a cluster, since clustering MDs seems to be best practice for resiliency. The 8.1 guide has an extensive section on RAP setup but it is lacking in detail in how RAPs work in clusters, except for a brief blurb on the lc-rap-pool command. Any advice would be much appreciated. Thanks!