ZyXEL Communications NWA-3163 & NWA-3166 User Manual

Page of 372
Chapter 3 Tutorials
NWA-3160 Series User’s Guide
70
2
You want to have a backup of the NWA controller AP configuration. 
3.6.3  Setup
In this example, each of your NWA standalone AP mirror each other. They all have 
the same SSID profiles stored. First you need to download the configuration file 
from one of your NWAs for backup purposes. Refer to 
for information on how to download the configuration file from your NWA. 
In case there are various SSID profiles stored in each NWA standalone AP, the 
administrator will have to copy each SSID profile to just one NWA (which will 
serve as the NWA controller AP.)
Note: This tutorial covers only the MGNT MODE and Controller screens. 
You will need to do the following steps to configure the management modes of 
your NWAs.
1
Assign one NWA AP (A) as the controller AP for your wireless NWA AP network. 
This will be your primary controller AP. Acquire another NWA with the same model 
and firmware version as A, to serve as the secondary controller AP (E). Both 
controller APs (A and E) are in the 1st floor of the building (recommended). The 
NWA APs (Band D) from the 2nd, 3rd and 4th floors are going to be your 
managed APs. 
Note: The controllers need to have static IP addresses in the same network. Make 
sure you set the IP addresses in the IP screen.
• Configure the newly added NWA (
E
) in Secondary Controller AP mode. 
• Configure the 1st floor NWA in Primary Controller AP (A) mode and enter the 
IP address of your Secondary Controller AP (E) for synchronization.
2
Change the management mode of your 2nd, 3rd and 4th floor NWAs (BC and D
originally in default standalone mode) to Managed AP mode. You can also 
manually enter the IP addresses of your primary and secondary NWA controller 
APs.
3
Add the newly converted managed APs (BC and D, from step 4) to the Managed 
Access Points List
 of the NWA primary controller AP.
4
Check your settings and test the configuration. This example uses screens from G-
302 v3, a wireless client that will try to access one of the mananged APs, for this 
section.