User`s guide

Identifying Bricks

007-3938-003 29

Upgrading L2 Firmware

The L2 ﬁrmware consists of the following two parts:

• Boot image

• Kernel image

Typically, you will upgrade the ﬁrmware through the network connection from the

SGIconsole to the L2, as follows:

$> /usr/cpu/firmware/sysco/flashsc --12 10.1.1.1

/usr/cpu/firmware/sysco/l2.bin local

Once this command has executed, You must power-cycle the L2 to run the new image.

To do this, you can use the L2 command reboot_l2.

If the L2 update fails, there is no back-up second image as there is with the L1. The L2,

however, will not run the kernel image if it is not valid. At this point, the L2 is intelligent

enough for you to upgrade it through its console port, as follows:

$> /usr/cpu/firmware/sysco/flashsc --l2recover /usr/cpu/firmware/sysco

/l2.bin <device>

where <device> equals --dev or --serial with the appropriate argument for the option

entered.

Output will indicate that the ﬁrmware image is being erased and then rewritten. The

ﬂash image is quite large (almost 2 MB), so updating the ﬂash takes several minutes. You

must power-cycle the L2 to run the new image by using the L2 command reboot_l2.

Identifying Bricks

Bricks are referenced by their racks and slot or bay locations. These values are stored in

non-volatile memory on the L1. Virtually all system controller communication requires

that each brick have a valid and unique rack and slot. If a brick does not have these, the

output of an L2 config command will reﬂect that as shown in the following example:

L2> config

137.38.88.82.1.0 ---c-- (no rack/slot set)

L2>