BelAir100SN User Guide
Performing a Software Upgrade
May 31, 2010
Confidential
Document Number BDTM11001-A01 Released
The
commit
command copies the system software and the configuration
database to the adjacent bank at the time of execution. However, changes to
the active load’s configuration after the
commit
command is executed are not
automatically stored in the standby bank. To keep both banks synchronized, you
must use the
commit
command after every configuration change of the active
load.
Backing Out from
a Software
Upgrade
It is possible to back out from a software upgrade in case its effects are
undesired, but only if the new software load has not been committed. See
Figure 12: Backing Out from an Uncommitted Software Upgrade
When you back out of a software upgrade, the old load overwrites the new
software load.
To back out from an upgrade, do the following steps:
1 Determine which bank has the old software load with the following
command:
/system/show loads
2 Set the old software load to be the next active load with the following
command:
/system/set next-load {A|B}
BelAir Unit
A
B
Old
Software Load
New
Software Load
Active
Software Load
Pointer to software
load for next restart
Activate old
software load
Backout: Overwrite new software
load with old software load