Updating the System BIOS
3-4
Express5800/
ftServer
: System Administrator’s Guide for the Linux Operating System
6. Perform the BIOS burn by issuing the following commands to one of the CPU-I/O
enclosures.
#
/opt/ft/bin/ftsmaint bringDown 0
Completed bringDown on the device at path 0.
#
/opt/ft/bin/ftsmaint burnProm
Path and filename for the BIOS
Updated firmware on the device at path 0.
#
/opt/ft/bin/ftsmaint jumpSwitch 0
Transferred processing to the device at path 0.
#
/opt/ft/bin/ftsmaint bringUp 1
Completed bringUp on the device at path 1.
The preceding commands burn the BIOS to both CPUs as follows:
•
bringDown
: Takes the CPU 0 element, in the upper enclosure, out of service.
•
burnProm
: Burns the new BIOS to CPU 0.
•
jumpSwitch
: Brings CPU 0 up, runs diagnostics on it, synchronizes it with
CPU 1, in lower enclosure, and then takes CPU 1 down.
•
bringUp
: Brings CPU 1 up, runs diagnostics on it, automatically burns the
new BIOS from CPU 0 onto it, reruns diagnostics, and resynchronizes CPU 1
with CPU 0.
N O T E S
At this point, reboot only if you need to change BIOS
configuration settings.
7. Repeat step
4
to verify that the CPU-I/O enclosures are again duplexed.
8. If the new BIOS did not perform as you expected, first verify that you do not also
need to perform an
Express Builder
upgrade to use the new BIOS. If so, proceed
to step
9
(returning here if the upgrade procedure does not initiate or follow the
documented and expected steps). If your operating system is fully up-to-date, it is
likely that the BIOS image file was not the correct firmware file for your system, or
the EEPROM that holds the BIOS did not properly capture the BIOS. This occurs
rarely, but it can happen. In that case, repeating the burn procedure usually works.
9. Double-check that you have a good BIOS image file before attempting the BIOS
upgrade again. It should not matter whether you retry the burn on the upper
CPU-I/O enclosure or the lower CPU-I/O enclosure, but you should note which
option you choose in case troubleshooting is required. Remember that image files
are easily corrupted during file transfer if copied from one format to another, as
when written out as a regular file rather than stored as an image, or by transfer as
