Deployment Guide
137
E
XAMPLE
5: A
SSIGNING
THE
C
ONFIGURATION
TO
H
IVE
AP
S
Uploading HiveAP Configurations
At this point, you have finished assigning configurations to the managed HiveAP objects on HiveManager, and it is
time to push these configurations from HiveManager to the physical HiveAP devices. Because this is the first time to
use HiveManager to update the configuration on these HiveAPs, you must perform a full upload, which requires
rebooting the HiveAPs to activate their new configurations.
Because HiveAP3 is a mesh point and the update involves changing its hive—from hive0 to hive1-test—you must make
sure to update its configuration before updating the configurations on HiveAP1 and HiveAP2. If you upload the
configuration on all of them at the same time and schedule them to reboot too quickly (say, 1 second after the
upload process completes), there is a chance that the portal through which the configuration for the mesh point is
passing will reboot before the mesh point finishes receiving its configuration. If that happens, only the configuration
on the portals will be updated. As a result, the portals will become members of a different hive (hive1-test) from
the mesh point (hive0). The mesh point will no longer be able to connect to the network through a portal using
hive0 and will become disconnected from the network and from HiveManager.
To avoid the preceding scenario, you must first change the hive on mesh points while they can still connect to the
network. After you change the hive to which the mesh points belong, they will will lose network and HiveManager
connectivity temporarily until you update the configuration on the portals. After they also join the new hive, the
mesh points will once again be able to connect through their portals to the network and to HiveManager. For more
information on this topic, see
" Updating HiveAPs in a Mesh Environment" on page 121
.
1. On the Monitor > Access Points > HiveAPs page, select the check box for HiveAP3, and then click Update >
Upload and Activate Configuration.
The Upload and Activate Configuration dialog box appears.
2. When initially sending the configuration to HiveAPs, HiveManager must perform a complete upload, which it
does automatically. After that, it automatically performs a delta upload by comparing the current configuration
for the HiveAP stored on HiveManager with that running on the HiveAP and then uploading only the parts that
are different. The three options (found in the Settings section) for uploading configurations are as follows:
Complete Upload: This option uploads the complete configuration to the selected HiveAPs and reboots
them to activate their new configuration.
Delta Upload (Compare with last HiveManager config): This option uploads only the parts of the
configuration that were not previously pushed to the HiveAPs from HiveManager.
Delta Upload (Compare with running HiveAP config): This option uploads only the changes to the
configuration based on a comparison of the current configuration for the selected HiveAPs on HiveManager
with the current configuration running on the HiveAPs.
Uploading a delta configuration does not require activation by rebooting the HiveAP and is, therefore, less
disruptive. However, before HiveManager can upload a delta configuration to a managed HiveAP, it must first
upload the full configuration and activate it by rebooting the HiveAP. After that, you can use the delta options.
3. Click Settings, select Activate after, leave the default interval of 5 seconds, and then click Save. The three
options for controlling the activation of an uploaded configuration are as follows:
Activate at: Select this option and set the time when you want the updated HiveAPs to activate their new
configuration. This is a good choice if you want to stagger the activation, or if you want to load a
configuration now but activate it when the network is less busy. To use this option accurately, both
HiveManager and the managed HiveAPs need to have NTP enabled.
Activate after: Select this option to load a configuration on the selected HiveAPs and activate it after a
specified interval. The range is 0 – 3600 seconds; that is, immediately to one hour. The default is 5 seconds.
Activate at next reboot: Select this option to load the configuration and not activate it. The loaded
configuration is activated the next time the HiveAP reboots.
Note:
If there is any failure when performing a delta upload, use a complete upload the next time.
Содержание access point
Страница 1: ...Aerohive Deployment Guide ...
Страница 7: ...HiveAP Compliance Information 6 Aerohive ...
Страница 13: ...Contents 12 Aerohive ...
Страница 37: ...Chapter 2 The HiveAP 20 ag Platform 36 Aerohive ...
Страница 71: ...Chapter 4 The HiveAP 340 Platform 70 Aerohive ...
Страница 81: ...Chapter 5 The HiveAP 320 Platform 80 Aerohive ...
Страница 105: ...Chapter 8 The High Capacity HiveManager Platform 104 Aerohive ...
Страница 123: ...Chapter 10 Using HiveManager 122 Aerohive ...
Страница 209: ...Chapter 14 Deployment Examples CLI 208 Aerohive ...
Страница 217: ...Appenidix A Country Codes 216 Aerohive ...