Smartpathos Configuration File Types - Black Box LWN602A User Manual

Chapter 10: SmartPath Operating System (OS)

10.3 SmartPathOS Configuration File Types

SmartPathOS supports several types of configuration files: running, current, backup, bootstrap, default, and failed.
The running configuration (config) is the configuration that is actively running in DRAM. During the bootup process, a SmartPath
AP loads the running config from one of up to four config files stored in flash memory:
• current: a flash file containing a combination of default and admin-defined settings. During the bootup process, this is the first
config that the SmartPath AP attempts to load as the running config. This is also the file to which you typically save commands
from the running config (you can also save them to the bootstrap config). See Figure 10-3.
• backup: a flash file that the SmartPath AP attempts to load during the reboot process if there is a newly uploaded current
config file or if it cannot load the current config file. See Figures 10-4 and 10-5.
• bootstrap: a flash file containing a second config composed of a combination of default and admin-defined settings. The
SmartPath AP fails over to this config when you enter the reset config command or if both the current and backup config files
fail to load. See Figure 10-6.
• default: a flash file containing only default settings. If there is no bootstrap config, the SmartPath AP reverts to this config when
you enter the reset config command or if both the current and backup config files fail to load. See Figure 10-6.
NOTE: There is also a failed config file, which holds any backup config that fails to load. See Figure 10-5.
When using the CLI, the two most frequently accessed config types are the running config and current config. When you enter a
command in the running config, the SmartPath AP performs it immediately. However, because the running config is stored in
volatile memory (DRAM), the commands are not yet permanent and will be lost when the SmartPath AP next reboots. For your
configuration settings to persist after rebooting, enter the save config command. This command saves the running config to the
current config, which is a file stored in nonvolatile (flash) memory. See Figure 10-3.
The running config comprises the current config
plus any commands that have not yet been
saved. The running config runs in DRAM.
The current config comprises saved
commands plus default settings. The
current config is stored in flash memory.
When you enter the save config command, the
When you enter the save config command,
SmartPath AP saves the running config from DRAM
the HiveAP saves the running config from
to flash memory, where it becomes the new current
DRAM to flash memory, where it becomes
config, replacing the one previously there.
the new current config, replacing the one
previously there.
When you upload a configuration file from SmartPath EMS or from a TFTP or SCP server, the SmartPath AP stores the uploaded
file in the backup config partition in flash memory, where it remains until the SmartPath AP reboots. If there is a backup config
file already stored in flash, the newly uploaded file overwrites it. See Figure 10-4.
Page 132
NOTE: The commands in bold have not yet been saved, which
(Note: The commands in bold have not yet been saved,
is why they do not appear in the current config. which is why they do not appear in the current config.)
NOTE: After entering the save config
(Note: After entering the save
command, the current and running
config command, the current and
running configs become identical.)
configs become identical.
Figure 10-3. Relationship between running and current config files.
724-746-5500 | blackbox.com
Running Config
(in DRAM)
Running Config
save config
Current Config
(in flash memory)
New Current Config
Previous Current Config
(overwritten)