User`s guide

XSR User’s Guide 35
Chapter 2 Utilizing the Command Line Interface
Managing the XSR
XSR-1805#more boot-config
updateBootrom.fls
XSR-1805#more restore-boot-config
xsr1800.fls
8 This is a critical step and all previous steps must be completed
accurately before proceeding. Reload and wait a couple of minutes.
You will lose your Telnet session as the system reboots. The XSR will
run
updateBootrom.fls and update the Bootrom into the boot flash
sectors. Power must not be interrupted since a power failure or
interruption may render the XSR unusable. The file,
restore-boot-
config
, will be renamed to boot-config and updateBootrom.fls and
bootrom.fls will be removed before the router is rebooted again.
XSR-1805#reload
Proceed with reload (y/n) ? y
9 Verify that the system is up by remotely logging in via Telnet. Enter
show version and check the new Bootrom version.
Local Bootrom Upgrade
Due to the change in the format of the Bootrom file between version 1.x and
version 2.01, a transitional step is required when updating across these
versions only. This transitional step can be avoided by using the Bootrom
Update utility described above.
When you are running a 1.x version of the Bootrom and you try to upgrade to
version 2.01 of the Bootrom file, it will be rejected due to the change in format.
bootrom_uncmp.fls is a transitional, non-redundant Bootrom file that the
existing 1_x version bU command can recognize. By updating and rebooting
with this transitional version, you can subsequently use the new
bU command
(which recognizes the new 2.01 format) to update the Bootrom to version 2.01.
Be aware that if you boot with
bootrom_uncmp.fls, you will see the
following output on the screen:
"Danger! Cannot find a good copy of Bootrom"
Once you have upgraded to version 2.01 with bootrom2_01.fls, you can
reboot and all subsequent Bootrom updates (which do not involve a change
in the bootFirst module) are power-safe.