User's Manual

Chapter 10 HiveOS
158 Aerohive
When you upload a configuration file from HiveManager or from a TFTP or SCP server, the HiveAP stores the
uploaded file in the backup config partition in flash memory, where it remains until the HiveAP reboots. If there is a
backup config file already stored in flash, the newly uploaded file overwrites it. See Figure 4.
Figure 4 Relationship between Current and Backup Config Files during a File Upload
When the HiveAP reboots, it attempts to load the the newly uploaded config file. If the file loads successfully, the
HiveAP makes that file the new current config and makes the previous current config the new backup config. If the
file does not load successfully, the HiveAP reboots again and loads the previous current config file. The HiveAP saves
the file it was unable to load as a failed config for diagnostics. See Figure 5.
Figure 5 Relationship between Current and Backup Config Files while Rebooting a HiveAP
Config File
Current Config
When you upload a config file from HiveManager or a TFTP or
SCP server, the HiveAP saves the uploaded file as a backup
config. This file replaces any previous backup config file that
might have been there.
TFTP
Server
SCP
Server
HiveManager or or HiveAP
Previous Backup Config
(overwritten)
New Backup Config
(in flash memory)
Current Config
(existing config)
Backup Config
(newly uploaded config file)
After uploading a new config
file, the following two config
files are stored in flash
memory on the HiveAP:
When you reboot the HiveAP, it tries to load the backup
config. Either of the following two results can occur:
If the newly loaded config
file loads successfully, . . .
. . . it becomes the new
current config, and . . .
. . . the previous current
config becomes the new
backup config.
. . . the backup config is
saved as a failed config
(for diagnostic analysis).
. . . the HiveAP reboots
again, loads the previous
current config, and . . .
If the newly loaded config
file fails to load, . . .
Reboot the HiveAP