How to upgrade firmware on the Sun Blade 6000 Virtualized Multi-Fabric 10GbE NEM and troubleshoot issues with this NEM:ATR:1381794.1:0

Asset ID:	1-71-1381794.1
Update Date:	2012-01-04
Keywords:

Solution Type Technical Instruction Sure

Solution 1381794.1 : How to upgrade firmware on the Sun Blade 6000 Virtualized Multi-Fabric 10GbE NEM and troubleshoot issues with this NEM:ATR:1381794.1:0

Applies to:

Sun Blade 6000 System - Version: Not Applicable and later [Release: N/A and later ]
Information in this document applies to any platform.

Goal

Give advice on firmware upgrade procedures for virtualised 10GBE 540-7695
and data gathering procedures for such configuration

Solution

DISPATCH INSTRUCTIONS
- WHAT SKILLS DOES THE FIELD ENGINEER/ADMINISTRATOR NEED: B6000 and SAS knowledge
- TIME ESTIMATE: 60 minutes
- TASK COMPLEXITY:0

FIELD ENGINEER/ADMINISTRATOR INSTRUCTIONS:
- PROBLEM OVERVIEW: Instructions for upgrading various firmware components of the Sun Blade 6000 10GBE VMF NEM
- WHAT STATE SHOULD THE SYSTEM BE IN TO BE READY TO PERFORM THE
RESOLUTION ACTIVITY?: All Blades within the chassis should be brought down before
performing work on this NEM
- WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE:

To update NEM ILOM Firmware.

1. Download latest patch for Sun Blade 6000 10GBE VMF NEM Firmware
from My Oracle Support Patches and Updates.

2) Unzip patch and required file will be in the Firmware directory
with a name similar to ILOM-2_0_3_12-Sun_Fire_X4238.pkg

3) Note the NEM ILOM must have its own valid IP address and
parameters defined to upgrade firmware.

4) Update the ILOM firmware by using browser method or ILOM
CLI method see

Sun Integrated Lights Out Manager 2.0 User's Guide
http://docs.oracle.com/cd/E19720-01/index.html

To update SAS expander firmware

Note – The Sun Blade 6000 disk modules and Sun Blade 6000 Virtualized
Multi-Fabric 10GbE NEMs must always be upgraded to the same firmware revision
level.

1) Note there are two different methods used to upgrade the firmware Common Array Manager (CAM) or Oracle Hardware Management Pack using the fwupdate tool.

2) If Common Array Manager (CAM) is required see page 119- 125 of Sun Blade 6000 10 GbE Virtualized Multi-Fabric Network Express Module User’s Guide
http://docs.oracle.com/cd/E19677-01/index.html

3) If the Oracle Hardware Management Pack is required then see Oracle® Server CLITools
http://docs.oracle.com/cd/E20451_01/index.html
and reference the section entitled "Using the fwupdate Tool"

LSIUTIL

If the Raid Expansion module installed is LSI based then many of the tasks concerning this NEM and related hardware will require the use of lsiutil and the saving and restoring of persistent mapping.
For details about this utility and when its use is required then refer to Appendix B of the Sun Blade 6000 Disk Module Administration Guide
http://docs.oracle.com/cd/E19045-01/blade.6000disk/index.html

To Update the Main Power Firmware
See page 7 of Sun Blade 6000 Virtualized Multi-Fabric 10 GbE Network Express Module Product Notes
http://docs.oracle.com/cd/E19677-01/index.html

1. Download the following patch from My Oracle Support 11884182

2. Unzip the p11884182_221_Generic.zip file
then unzip Power_Sequencer/NEMHydraPwrUpd10.zip
The following files that are needed to upgrade the
power sequencer will now be available.

■ update_nem0_mainpwr.sh- Script to upgrade NEM in slot 0
■ update_nem1_mainpwr.sh- Script to upgrade NEM in slot 1
■ nem_pwr_ver.sh- Displays the version of NEM power firmware
■ adm1066_update- Binary to update power sequencer firmware (runs on the
CMM)
■ main_pwrseq_rev110304.hex- Modified power sequencer firmware to
prevent unexpected shutdowns
Note – Make sure that you have execute permissions on these files. If you do not
have execute permissions, use the chmod +x command on the files before copying
them to the CMM.
3. Enter escalation mode on the CMM see following MOS document
CMM access to escalation mode (Doc ID 1353684.1)
https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?_afPfm=e
4. From within the ILOM bash shell (escalation mode) use scp to copy
required files to to the /coredump directory
cd /coredump
scp [email protected]:/home/user_name/TEMP/Power_Sequencer/*

5. Check current status of power sequencer firmware
./nem_pwr_ver.sh
If power sequencer firmware has been updated the following is displayed
otherwise the values displayed are 0.

Nem (slot 0) main power version:
04
03
11
Nem (slot 1) main power version:
04
03
11

6. Update the NEM in slot 0, with the following command:
./update_nem0_mainpwr.sh
7. If necessary, update the NEM in slot 1:
./update_nem1_mainpwr.sh
Note – Each command may take more than two minutes to complete.
8. Power cycle the Virtualized NEMs
Note that there is no power cycle facility within the NEM ILOM
so the easiest way to do this is the following commands from within
the CMM ILOM cli (normal root log in)
stop /CH
check state of NEMs to ensure they have been powered off
show /CH/NEM0/STATE value
show /CH/NEM1/STATE value
then restart chassis
start /CH
9. From escalation mode (ILOM bash shell) check the upgrade is complete
/coredump/nem_pwr_ver.sh
(see step 5 for required output)

OBTAIN CUSTOMER ACCEPTANCE
- WHAT ACTION DOES THE FIELD ENGINEER/ADMINISTRATOR NEED TO TAKE TO RETURN THE SYSTEM TO AN OPERATIONAL STATE:

PARTS NOTE:

REFERENCE INFORMATION:
Sun Blade 6000 Virtualized Multi-Fabric 10 GbE Network Express Module Product Notes
http://docs.oracle.com/cd/E19677-01/index.html
Sun Blade 6000 Virtualized Multi-Fabric 10GbE Network Express Module User’s Guide
http://docs.oracle.com/cd/E19677-01/index.html
CMM access to escalation mode (Doc ID 1353684.1)
https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1353684.1
NEM Hydras's Main Power Shuts Down Unexpectedly (Doc ID 12222158.1)
https://support.us.oracle.com/oip/faces/secure/km/DocumentDisplay.jspx?id=1222158.1
Sun Integrated Lights Out Manager 2.0 User's Guide
http://docs.oracle.com/cd/E19720-01/index.html
Oracle Integrated Lights Out Manager 3.0 documentation.
http://docs.oracle.com/cd/E19860-01/index.html

Attachments

This solution has no attachment