Aerohive access point, Deployment Manual

Page: 136 / 221

Deployment Guide 135
E
XAMPLE
5: A
SSIGNING THE
C
ONFIGURATION TO
H
IVE
AP
S
E
XAMPLE
5: A
SSIGNING THE
C
ONFIGURATION TO
H
IVE
AP
S
After completing the steps in the previous examples, you now assign the WLAN policy to the HiveAPs. In addition,
you set one radio in access mode and one in backhaul mode, and you change their login settings (and country code
if necessary). Finally, you push the configuration to the HiveAPs. The transfer of HiveAP configuration assignments is
presented conceptually in
Figure 7 .
Figure 7 HiveAP configuration assignments
Assigning Configurations
1. Click Monitor > Access Points > HiveAPs (View mode: Config).
2. Because you can only set radio modes on individual HiveAPs, click one of their names, select Use one radio (2.4
GHz) for client access and one radio (5 GHz) for a mesh link, and then click Save. Repeat this step for all the
other HiveAPs as well.
3. To modify all the HiveAPs at the same time, select the check box in the header to the left of Host Name, which
selects the check boxes of all the HiveAPs, and then click Modify.
The HiveAPs > Modify (Multiple) dialog box appears.
4. From the WLAN Policy drop-down list, choose wlan-policy-test1. This is the WLAN policy that you created in
"Example 3: Creating a WLAN Policy" on page 128 . Do not modify any of the other basic settings.
5. In the Optional Settings section, expand Credentials, and then enter the following in the Root Admin
Configuration section:
New Admin Name: testadmin1
This is the root admin name that HiveManager uses to make SSH connections and upload a full
configuration to managed HiveAPs. The default root admin name and password is admin and
aerohive.
New Password: testpass1
Confirm New Password: testpass1
Although changing the login credentials is not necessary, it is good practice, which is why it is
included here. When you are ready to deploy the HiveAPs on your network, change the admin name
and password again.
Note: To see the text strings that you enter, clear the Obscure Password check box.
CAPWAP traffic secured with DTLS
Note: The CAPWAP path to HiveAP3 really passes through
one of the portals (HiveAP1 or HiveAP2) before reaching it.
HiveManager
Members of “hive1 test”
HiveAP3
(Mesh Point)
HiveAP2
(Portal)
HiveAP1
(Portal)
WLAN Policy:
wlan policy test1
SSID: test1 psk
Hive: hive1 test
DHCP client: enabled
Credentials:
Name: testadmin1
Password: testpass1
SSID: test1 psk
Hive: hive1 test DHCP client: enabled
Credentials:
Name: testadmin1
Password: testpass1