Asset ID:	1-71-1516163.1
Update Date:	2018-04-24
Keywords:

Solution Type Technical Instruction Sure

Solution 1516163.1 : Pillar Axiom: How to upgrade the brick raid controller firmware manually (burn)

Applies to:

Pillar Axiom 600 Storage System - Version Not Applicable and later
Pillar Axiom 500 Storage System - Version Not Applicable and later
Pillar Axiom 300 Storage System - Version Not Applicable and later
Information in this document applies to any platform.

Goal

How to upgrade the brick raid controller firmware manually (burn)

This procedure applies to SATA and Fibre Channel RAID Controllers.

The Fibre Channel Expansion Controller obtains its firmware from the FC RAID Controller if both are powered on in the correct sequence. In some instances, it is necessary to upgrade the Boot Block of the FC Expansion Controller in order to allow it to obtain the rest of the Expansion Firmware. If any other component of the Expansion Controller must be updated, replace the Expansion Controller.

The Enclosure Services (SES) Modules cannot be upgraded in the field. The SATA Brick supports SES Firmware 197 or 205. The FC RAID and Expansion Brick require SES Firmware 205 or higher.

Please read this entire procedure in advance so you are familiar with the process and concepts.

Solution

Notes

“Buddy Burn” If a FC or SATA RAID controller with no firmware, but a valid bootblack, is installed in a Brick where the buddy controller has valid firmware, that running RAID controller will perform a “buddy burn” and load its firmware onto the new RAID CU. There is no Buddy Burn for FC Expansion Controllers. RAID Logistics Spares are stocked with only the boot block. If they are placed in a Brick where there is an existing controller, “buddy burn” will install the correct firmware much quicker than a “manual burn”. Buddy Burn can only be done if there is another RAID CU in that Brick with valid firmware. You can force a Buddy Burn (if there is a good controller in the same brick) by deleting the firmware on a RAID Controller.

“Manual Burn”. Firmware can be installed by attaching a serial console cable to the RAID CU and the ymodem file transfer utility and the “bd” (binary download) RAID console command. The firmware is provided as a “dlf” or down load file. If there is another RAID CU in the Brick and that other CU has a valid firmware image, you will need to remove it, since it will repeatedly attempt to reset the RAID CU you are attempting to burn.

SES Modules. The firmware on the SES module for FC Bricks is a higher revision than that for the SES Module on the SATA Brick. There is no method to upgrade this firmware in the field. If an FC Brick below 2.4.2 must be upgraded manually, the SES modules on the FC RAID and FC EXP brick should be replaced. Be sure to set the thumb wheel to “0” for FC and SATA RAID and “1” for FC Expansion Bricks.

SATA and FC RAID Firmware. The firmware images for manual burn are Fnnn_nnnnRel.dlf (down load format) files approximately 1.5 to 2 Mbytes in size, for example: F200_5719Rel.dlf (FC RAID 00.57.19), FW06_9045Rel.dlf (SATA 06.90.45).

FC Expansion Firmware. The only FC Expansion Boot package is J200_NNNNBoot.dlf [Boot Block]. Under normal circumstances, the firmware on the FC Expansion Controller is managed by the FC RAID Controller. As the FC Expansion controller boots, it sends its FPGA, SES, and Boot Block firmware versions to the FC RAID controller. If any of those require update, the FC RAID Controller performs the upgrade. If the PNET protocol version has changed, the FC Expansion Brick will not be able to contact the RAID Brick—the firmware on the Expansion Brick must be updated manually by the installation of the Boot Block or the Expansion Controller must be replaced. The upgrade of the FC Expansion Controller by the RAID Controller can only be done if the Expansion Controller is powered on before the RAID Controller and the PNET connection is able to establish Sync.

Console Connection

The Brick Console port is a 1/8 Inch Mini Stereo Jack. This is connected to a Microsoft workstation Serial Port with a Console Cable (The cable may be supplied as two pieces, a Stereo to RJ-45 Telco Cable and a DB-9 to RJ-45 Telco Adapter. For systems without serial ports, a USB-Serial Convertor may be supplied):

Serial Communications Settings

Use the Microsoft HyperTerminal™ utility. It is known to work for downloads. All other utilities are to be used at your own risk, including all responsibility for trouble shooting or recovery.

All Brick Console Ports are:

115,200 Bits per Second

8N1 or 8 Bits, No Parity, 1 Stop Bit

No Flow Control All hardware and software flow control must be disabled.

ymodem For file transfers. This is selected after entering the download command.

Passwords and Console Commands

Do not enter any commands on the Brick Console without explicit instructions from an advanced support engineer or a written procedure. Many of the available commands may render the entire Brick inoperable.

The password for SATA and FC RAID Controllers is “tardis” lower case.
The password for FC Expansion Controllers is “gemini” lower case.

Manually Burning RAID Firmware

Note: In order to burn a RAID or Expansion controller, the buddy controller in the same Brick must not be running, as the buddy will repeatedly attempt to reset and recover your RAID controller as you are

attempting to burn firmware. The connection to the Slammer or the Upstream Brick must also be disconnected. If you are burning the Boot Block in an Expansion Controller, the PNET and Fibre Channel connections to the RAID Brick must be removed.

Note: Replacement of Expansion Controllers with new units is recommended.

OPTIONAL: Remove all firmware from a RAID Controller

If there is a RAID Controller with good firmware in the same Brick, and there are no firmware defects involving GM of RAID controllers, you can force Buddy Burn by removing all firmware from the RAID Controller that you are attempting to upgrade.

If the Brick is connected to the Slammer on a running system, it will only do Buddy Burn if there is no firmware on the RAID Controller. If there is any firmware at all, whether or not it is a firmware level that can be upgraded by the system, Buddy Burn will not occur if the Slammer is connected to the Brick and running.

CAUTION: Be sure not to remove all firmware from the survivor. If you do, you must manually flash both RAID Controllers to the correct level, with the Slammer disconnected.

Make sure there is no connection to the FC2 or FC1 port of the Brick. This prevents the Slammer from sending commands.

Power off the Brick.

Back the RAID CU that you do NOT want to remove firmware from out of the Brick Chassis.

Power on the Brick with only the RAID CU that you want to remove firmware from fully seated in the Chassis.

As the RAID CU boots, enter “tardis” during the countdown to enter the Boot Menu.

If you do not enter the password in time, enter “rst 1234” to boot the controller again. Be sure to type the password as the countdown numbers are displayed.

If the RAID CU stops at the Preboot prompt, enter “b” to go to the BootBlock prompt.

Enter “dir” to see all of the firmware images and Flash Data Records (FDR files)

Enter “del” to remove all of the firmware images and Flash Data Records.

Enter “dir” to verify that there are no files remaining.

Power the Brick off and insert the other RAID Controller

Power the Brick on to Buddy Burn the RAID CU where you have just deleted all firmware.

After the Buddy Burn completes, make sure the RAID version is the same on both controllers with “ver”

Connect the upstream and downstream fibre cables.

Downloading Firmware to a RAID or Expansion Controller

Make sure you can quickly locate the correct firmware file as you enter the “bd” command. The command will time out and abort if the download does not begin quickly. If the command times out, you will have to start all over.

Power the brick off and back the buddy controller out of the chassis slightly so it is powered off.

Disconnect the FC2 port Fibre Cables to the Slammer or Upstream Brick if this Brick is installed in a cabinet. The Slammer may attempt recovery action that will interfere with the firmware update.

Start HyperTerminal™ and make sure the communications settings are 115,200 bps, 8N1, No Flow Control.

Place HyperTerminal™ in Capture mode and save the output of all commands to a unique file. You may be asked to send this file to Pillar Support for verification.

Insert the serial cable in the console port of the Controller you will be burning.

Press Carriage Return. You should get a Password prompt.

Enter “tardis” for all RAID controllers. Enter “gemini” for FC Exp (JBOD) Controllers. The SES modules do not have a password.

Type “bd” to begin the download. You should see heartbeats from the controller, waiting for the download to begin. Perform the next steps quickly or else the RAID controller will time out and abort the transfer.

On the HyperTerminal™ menu, Select “Transfer” and then “Send File”.
Select “Ymodem” and then select “Browse” and locate the firmware image file.
Select “Send” to begin the transfer.

It will take about 15 minutes to transfer the file. You should see the transfer complete, then you will see console entries that the flash is being compacted and flash sections burned as required. You will then see a message that the last packet has been processed. There is no such message on Expansion Controllers.

Note: This only downloads the new firmware. You must reboot the RAID controller to install the new firmware.

Wait at least one minute after you see the message that the last packet has been processed.

Type “rst 1234” (rst, then a space, then 1234) to reset the RAID controller to install the new firmware. You may also power cycle the brick if desired, but do not insert the buddy controller.

For Expansion Controllers, use rstu (reset us)

Do not connect the Expansion Controller to the RAID Brick until both controllers have the same Boot Block version.

You will see the RAID Controller reboot, which includes a numeric countdown. Do not enter the password at this time.

After the boot completes, press “Enter” to get the password prompt. Enter “tardis” on RAID or “gemini” on Expansion.

On a RAID controller, you should see the FCRoot> prompt. On an FC Expansion Controller, you should see the Elwood> prompt.

Type “ver” to display the version information.

Typical RAID output. Your version will vary.

FCRoot>ver

2050-00038-005719-005719

Product: FC to FC Raid controller

FPGA internal ver F7

Typical Expansion output. Your version will vary.

Elwood>version

Product: FC to FC JBOD

Xfer Fr RAID Ver 004500

FPGA internal ver D8

You can now use “Buddy Burn” to install this same firmware on additional RAID controllers. Expansion Controllers must be upgraded manually, this step does not apply. Be sure to check the version on both controllers with the “ver” command after every burn.

Power the brick off. Leave this controller in the brick.
Insert the RAID controller to be burned in the other slot in this brick.
Power the brick on. You should see the two controllers boot, then a very rapid amber flashing pattern on the FC0-FC3 LEDs on the controller that is being burned.
When the LEDs on both controllers begin a steady pattern, reset both controllers. Power cycle the brick, or enter “brst 1234” (both reset) on either controller.
Log in and check the version on both controllers. They must be identical.
If more controllers are to be upgraded, repeat this one controller at a time.

If any SES module on a FC RAID or EXP Bricks is below revision 205, replace the SES Module. [FC Bricks require SES 205 or higher, SATA Bricks require 197 or higher.] Make sure the thumbwheel switch on all RAID Controllers (both SATA and FC RAID) is always set to “0” and the thumbwheel on all FC Exp Controllers is always set to “1”.

After burning both RAID Controllers in a Brick, power cycle the entire Brick. Watch the boot to make sure that both controllers boot at the same rate.

Burning FC Expansion Firmware

The most reliable method of upgrading FC Expansion Bricks is to replace the FC Expansion controllers and SES Modules with newer units with the upgraded firmware.

The FC Expansion Brick firmware is part of the FC RAID firmware. If the PNET communication path works, the Expansion Brick will get new firmware installed by the FC RAID Brick.

The only package documented here for field installation is the Boot Block. If this does not allow the RAID Brick to upgrade the rest of the Expansion firmware, the controller must be replaced.

The FC RAID Brick that the Expansion Brick is connected to must be upgraded first, so when the Expansion unit is power cycled, it can retrieve any additional updates required from the FC RAID Brick.

Disconnect the PNET and FC cables between the Expansion and RAID Brick when burning firmware.

Back the other Expansion Controller out of the chassis during each burn.

The FC Expansion brick password is “gemini” This should return the Elwood> prompt. Use the “bd” command to download the firmware, just as on RAID controllers.

Burn the Boot Block with the J200_NNNN.Boot.dlf file, for example, J200_4100Boot.dlf.

Burn the Boot Block on the other Expansion Controller in this Brick.

Replace the SES module if required. Be sure the thumbwheel is set to “1” for all Expansion Controllers.

Make sure the FC RAID Controller has been upgraded. The SES Module thumbwheel switch on the RAID Controller must be “0”.

Power off the FC RAID and Expansion Bricks.

Power on the Expansion Brick, then the RAID Brick and watch the boot process.

The PNET port LEDs on the RAID and Expansion controllers must go green. If this does not happen, the Expansion Brick cannot check and update any required remaining firmware. Attempt to burn the Exp firmware again, and if this does not work, the Exp module must be replaced. The scsi> chk command on the RAID brick will indicate the Boot Block version of the Expansion Brick if the PNET is able to establish communications.

Attachments

This solution has no attachment