Filter
Top Products
517 | Remote AccessPoints DellPowerConnectW-SeriesArubaOS6.2 | User Guide
Deployment Scenario Master IP Address Value
Deployment 1 Controller IP address
Deployment 2 Controller public IP address
Deployment 3 Public address of the NAT device to which the controller is connected
NOTE: The username and password you enter must match the username and password configured on the authentication server for
the remote AP
4. Under IP Settings, make sure that Obtain IP Address Using DHCP is selected.
5. Click Apply and Reboot.
Deploying a Branch Office/Home Office Solution
In a branch office, the AP is deployed in a separate IP network from the corporate network. Typically, there are one
or two NAT devices between the two networks. Branch office users need access to corporate resources like printers
and servers but traffic to and from these resources must not impact the corporate head office.
The Figure 167 is a graphic representation of a remote AP in a branch or home office with a single controller
providing access to both a corporate WLAN and a branch office WLAN.
Figure 167: Remote AP with Single Controller
Branch office users want continued operation of the branch office WLAN even if the link to the corporate network
goes down. The branch office AP solves these requirements by providing the following capabilities on the branch
office WLAN:
l Local termination of 802.11 management frames which provides survivability of the branch office WLAN.
l All 802.1x authenticator functionality is implemented in the AP. The controller is used as a RADIUS pass-
through when the authenticator has to communicate with a RADIUS server (which also supports survivability).
l 802.11 encryption/decryption is in the AP to provide access to local resources.
l Local bridging of client traffic connected to the WLAN or to an AP 70 enet1 port to provide access to local
resources.