| Asset ID: |
1-71-2088888.1 |
| Update Date: | 2016-04-19 |
| Keywords: | |
Solution Type
Technical Instruction Sure
Solution
2088888.1
:
How to Update Disk Drive Firmware on Exadata and Recovery Appliance Compute Nodes
| Related Items |
- Exadata X4-2 Hardware
- Exadata X3-2 Hardware
- Zero Data Loss Recovery Appliance X6 Hardware
- Exadata X5-8 Hardware
- Exadata X6-2 Hardware
- Exadata X6-8 Hardware
- Exadata X5-2 Hardware
- Exadata Database Machine X2-8
- Exadata X4-8 Hardware
- Exadata X3-8 Hardware
- Zero Data Loss Recovery Appliance X5 Hardware
- Zero Data Loss Recovery Appliance X4 Hardware
- Exadata Database Machine X2-2 Hardware
- Exadata Database Machine V2
|
| Related Categories |
- PLA-Support>Sun Systems>x86>Engineered Systems HW>SN-x64: EXADATA
|
Procedure for how to update disk drive firmware on Exadata and Recovery Appliance Compute Nodes.
In this Document
Applies to:
Exadata X4-2 Hardware - Version All Versions and later Exadata X3-2 Hardware - Version All Versions and later Exadata X3-8 Hardware - Version All Versions and later Zero Data Loss Recovery Appliance X5 Hardware - Version All Versions and later Zero Data Loss Recovery Appliance X4 Hardware - Version All Versions and later Information in this document applies to any platform.
Goal
Procedure for how to update disk drive firmware on Exadata and Recovery Appliance Compute Nodes.
Solution
Exadata and Recovery Appliance Compute Nodes contain disks with firmware which is not normally part of the hardware configuration checks. Oracle supplies separate firmware patches for disk drives which can be used to update DB Node disk firmware on an as desired basis, using the following procedure.
Note: Exadata Storage Servers in Exadata Database Machines and Recovery Appliances contain disks with firmware that is part of the hardware configuration checks. Those disks will have firmware automatically updated when imaged and patched, if necessary. See Note 888828.1 for specifics on Exadata Storage Server images and patches.
- Identify which disk models are installed and the firmware version of each:
Linux/OVM:
# /opt/MegaRAID/MegaCli/MegaCli64 -pdlist -a0 | grep -iE "encl|slot|inq|level"
Enclosure Device ID: 252
Slot Number: 0
Enclosure position: N/A
Device Firmware Level: A31A
Inquiry Data: HITACHI H109060SESUN600GA31A1329BSD9ZL
Enclosure Device ID: 252
Slot Number: 1
Enclosure position: N/A
Device Firmware Level: A31A
Inquiry Data: HITACHI H109060SESUN600GA31A1329BS88PL
Enclosure Device ID: 252
Slot Number: 2
Enclosure position: N/A
Device Firmware Level: A31A
Inquiry Data: HITACHI H109060SESUN600GA31A1329BSASLL
Enclosure Device ID: 252
Slot Number: 3
Enclosure position: N/A
Device Firmware Level: A31A
Inquiry Data: HITACHI H109060SESUN600GA31A1329BRBNGL
Solaris:
# /opt/MegaRAID/MegaCli -pdlist -a0 | egrep -i "encl|slot|inq|level"
Enclosure Device ID: 252
Slot Number: 0
Enclosure position: 0
Device Firmware Level: A2B0
Inquiry Data: HITACHI H106030SDSUN300GA2B01219NTSULB
Enclosure Device ID: 252
Slot Number: 1
Enclosure position: 0
Device Firmware Level: A2B0
Inquiry Data: HITACHI H106030SDSUN300GA2B01219NXGS5B
Enclosure Device ID: 252
Slot Number: 2
Enclosure position: 0
Device Firmware Level: A2B0
Inquiry Data: HITACHI H106030SDSUN300GA2B01219NVDZTB
Enclosure Device ID: 252
Slot Number: 3
Enclosure position: 0
Device Firmware Level: A2B0
Inquiry Data: HITACHI H106030SDSUN300GA2B01219NUH2UB
NOTE: Some HBA firmware versions may not report the "Device Firmware Level: " information separately. In that case, the firmware level is the 4 characters immediately following the disk model name in the "Inquiry Data" field. In the examples above: "H109060SESUN600GA31A1329BRBNGL" model is H109060SESUN600G, firmware level is A31A. "H106030SDSUN300GA2B01219NTSULB" model is H106030SDSUN300G, firmware level is A2B0.
While all Exadata and Recovery Appliance systems are shipped with the same disk model in each DB server slot at the time of shipping, be careful that any disk replacements may have been replaced with a different model and firmware level. Multiple patches may be required if multiple model types are installed. Only the specific model firmware should be applied to that drive.
- Using the below table, identify and download the disk firmware patch for the disk models needed from the My Oracle Support patch page. Use the exact patch number as given below, including "-XX" when searching in the "Patch Number" box.
Upon results being returned for different architectures, you can select either Solaris x86 or Linux x86, as these provide the same patch zip file which provides the utilities and firmware for both OS'.
OS specific instructions are provided in this document covering both Solaris and Linux.
For more information on finding disk firmware patches in MOS, refer to Note 1294589.1.
|
Exadata Model(s)
|
Disk Type
|
Installed Part Number
|
Oracle Model #
(Inquiry Disk Drive Name)
|
Vendor Model #
(Label)
|
Latest Firmware
Version
|
Firmware Patch
|
|
V2
|
146GB 10K RPM Disk
|
540-7868
|
ST914602SSUN146G
|
ST9146802SS
|
0703 |
124780-03 *
|
|
H101414SCSUN146G
|
HUC101414CSS300
|
SA25 |
145141-01 *
|
|
ST914603SSUN146G
|
ST9146803SS
|
0E71 |
140493-08 *
|
|
H103014SCSUN146G
|
HUC103014CSS600
|
A2A8 |
138335-03 *
|
|
X2-2, X3-2
|
300GB 10K RPM Disk
|
540-7869
|
ST930003SSUN300G
|
ST9300603SS
|
0E71 |
140493-08 *
|
|
H103030SCSUN300G
|
HUC103030CSS600
|
A2A8 |
138335-03 *
|
|
542-0388
|
H106030SDSUN300G
|
HUC106030CSS600
|
A4C0 |
149675-06
|
|
H109030SESUN300G
|
HUC109030CSS600
|
A720 |
150940-04
|
|
ST930005SSUN300G
|
ST9300605SS
|
0606 |
No Update Available
|
|
X2-8, X3-8
|
300GB 10K RPM Disk
|
542-0300
|
ST930003SSUN300G
|
ST9300603SS
|
0E71 |
140493-08 *
|
|
H103030SCSUN300G
|
HUC103030CSS600
|
A2A8 |
138335-03 *
|
|
542-0387
|
H106030SDSUN300G
|
HUC106030CSS600
|
A4C0 |
149675-06
|
|
H109030SESUN300G
|
HUC109030CSS600
|
A720 |
150940-04
|
|
ST930005SSUN300G
|
ST9300605SS
|
0606 |
No Update Available
|
|
X4-2, X4-8, X5-2
|
600GB 10K RPM Disk
|
542-0287
|
H106060SDSUN600G
|
HUC106060CSS600
|
A4C0 |
149675-06
|
|
H109060SESUN600G
|
HUC109060CSS600
|
A720 |
150940-04
|
|
ST960005SSUN600G
|
ST9600205SS
|
0606 |
No Update Available
|
|
X5-8, X6-2, X6-8
|
600GB 10K RPM Disk
|
7093015
|
H101860SFSUN600G
|
HUC101860CSS200
|
A770 |
152013-02
|
* For patches 124780-03, 138335-03, 140493-08 and 145141-01, additional files are required to make them compatible with the HBA used in Exadata DB nodes. Also download the file "DB_diskfw_patch_addition.tar" attached to this Note which provides these files that are not included in the patch zip file. This file is used in step 4.
|
Recovery Appliance Model(s)
|
Disk Type
|
Installed Part Number
|
Oracle Model #
(Inquiry Disk Drive Name)
|
Vendor Model #
(Label)
|
Latest Firmware
Version
|
Firmware Patch
|
|
X4, X5
|
600GB 10K RPM Disk
|
542-0287
|
H106060SDSUN600G
|
HUC106060CSS600
|
A4C0 |
149675-06
|
|
H109060SESUN600G
|
HUC109060CSS600
|
A720 |
150940-04
|
|
ST960005SSUN600G
|
ST9600205SS
|
0606 |
No Update Available
|
|
X6
|
600GB 10K RPM Disk
|
7093015
|
H101860SFSUN600G
|
HUC101860CSS200
|
A770 |
152013-02
|
- Copy the patch file to the DB node, and unzip the patch. You will need ~30-35MB free disk space for each patch zip file and unzipped patch.
For example:
# cd /root
# unzip –q 150940-04.zip
- Change into the patch directory and run the ‘bitops.sh’ script to convert the firmware binary to a version compatible with MegaCli used to download the firmware.
For example:
# cd 150940-04/megaraid/
# ls
bitops.sh linux_bitops sparc_bitops x86_bitops
# ./bitops.sh
#
NOTE 1: If the patch does not include the "megaraid" directory with "bitops.sh" script as noted in step 2, then download the file " DB_diskfw_patch_addition.tar" attached to this Note which provides these files. Untar this in the patch directory which will create the "megaraid" directory with the required files. For example: # cd 124780-03 # tar xvf /root/DB_diskfw_patch_addition.tar megaraid/ megaraid/linux_bitops megaraid/sparc_bitops megaraid/bitops.sh megaraid/x86_bitops Download verification information for "DB_diskfw_patch_addition.tar": # ls -l DB_diskfw_patch_addition.tar -rw-r--r-- 1 root root 40960 Jan 28 13:30 DB_diskfw_patch_addition.tar # md5sum DB_diskfw_patch_addition.tar 0e252209c145fc8c5362949606f34876 DB_diskfw_patch_addition.tar
NOTE 2: Some newer Exadata/Recovery Appliance images based on newer OEL versions may not have "/usr/bin/ksh" available by default, which the "bitops.sh" requires. To workaround this, create links as follows, then run "bitops.sh":
# ./bitops.sh
-bash: ./bitops.sh: /usr/bin/ksh: bad interpreter: No such file or directory
# ln -s /bin/ksh93 /etc/alternatives/ksh-usrbin
# ln -s /etc/alternatives/ksh-usrbin /usr/bin/ksh
After running "bitops.sh", the disk firmware binary should now be in the “<patch>/megaraid” directory:
# pwd
/root/150940-04/megaraid
# ls –l
total 3704
-rwxr-xr-x 1 root root 460 Oct 13 17:29 bitops.sh
-rw-r--r-- 1 root root 884736 Dec 10 14:31 H101212SE.A720.fw
-rw-r--r-- 1 root root 950272 Dec 10 14:31 H109030SE.A720.fw
-rw-r--r-- 1 root root 950272 Dec 10 14:31 H109060SE.A720.fw
-rw-r--r-- 1 root root 950272 Dec 10 14:31 H109090SE.A720.fw
-rwxr-xr-x 1 root root 11861 Nov 30 2012 linux_bitops
-rwxr-xr-x 1 root root 10728 Oct 7 14:56 sparc_bitops
-rwxr-xr-x 1 root root 12072 Nov 30 2012 x86_bitops
- Repeat steps 2 to 4, for each different disk model installed in the DB node. While all Exadata and Recovery Appliance systems are shipped with the same disk model in each DB server slot at the time of shipping, be careful that any disk replacements may have been replaced with a different model and firmware level. Multiple patches may be required if multiple model types are installed. Only the specific model firmware should be applied to that drive.
- Shutdown the CRS services following the steps in Note 1982342.1 for Linux or OVM. If running Solaris, follow the Linux/non-OVM steps. Do not run the shutdown step.
- From the system console, login as 'root' and place the system into single-user mode to make the system as idle as possible during disk firmware upgrade. The console may be either on graphics or serial stream and is accessible through the ILOM. Refer to Note 1070658.1 for how to access the console through ILOM. To access single-user mode, login as 'root' and run the following command:
For Linux or OVM, run "init s".
For Solaris, follow the steps in the Solaris documentation: https://docs.oracle.com/cd/E26502_01/html/E28983/gktkr.html#fvzqr
- Apply the firmware to the disk drives. Be careful that any disk replacements may have been replaced with a different model. Only the specific model firmware should be applied to that drive.
The general disk firmware update command is of the form:
MegaCli –PdFwDownload -PhysDrv[<Enclosure Device ID>:<Slot Number>] –f <firmware file> -a0
The parameter for Physical Drive is of the form:
“-PhysDrv[<Enclosure Device ID>:<Slot Number>]
where Enclosure device ID and slot numbers may vary from system to system. Use the enclosure device ID and slot numbers present for each model on this specific system as obtained in Step 1 output.
The parameter for the firmware file is the file created in step 4.
If the firmware file used is from the patch directory and is not created with 'bitops.sh', then an error will result - "The requested operation could not be completed as device is busy or unexpected error occurred" with "Exit Code 0x2d". Re-run the firmware update command using the correct firmware file.
For a single drive update, use the following command for each slot, adjusting the PhysDrv numbers for the specific values obtained in Step 1 output.
For example:
# /opt/MegaRAID/MegaCli/MegaCli64 -PdFwDownload -PhysDrv[252:0] -f /root/150940-04/megaraid/H109060SE.A720.fw –a0
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
Exit Code: 0x00
For multiple drives of the same model, updates can be done with a single command, providing a comma separated list of disks to the "PhysDrv" parameter, for the specific values obtained in Step 1 output:
For example:
# /opt/MegaRAID/MegaCli/MegaCli64 -PdFwDownload -PhysDrv[252:0,252:1,252:2,252:3] -f /root/150940-04/megaraid/H109060SE.A720.fw –a0
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
...
MicroCode Update is already in progress. Please wait...
MicroCode Update is already in progress. Please wait...
Flashing firmware image size 0x8000 (0x0 0x80 0x0). Please wait...
...
Exit Code: 0x00
NOTE: If the RAID HBA firmware is an early version, the multiple drive update may fail with the error "Firmware Download on Device at Enclosure - #, Slot - # in Adapter 0 is not Allowed" with "Exit Code: 0x01". If this occurs, the 1st disk specified will update but the 2nd and subsequent disks will not. To workaround this, use the single drive update syntax to update each slot individually.
If there are any other errors in the download output, engage Oracle support via a SR.
- Repeat step 8 as necessary to update each disk drive.
- Verify the new firmware was applied by repeating the command in step 1.
For example:
# /opt/MegaRAID/MegaCli/MegaCli64 -pdlist -a0 | grep -iE "encl|slot|inq|level"
Enclosure Device ID: 252
Slot Number: 0
Enclosure position: N/A
Device Firmware Level: A720
Inquiry Data: HITACHI H109060SESUN600GA7201329BSD9ZL
Enclosure Device ID: 252
Slot Number: 1
Enclosure position: N/A
Device Firmware Level: A720
Inquiry Data: HITACHI H109060SESUN600GA7201329BS88PL
Enclosure Device ID: 252
Slot Number: 2
Enclosure position: N/A
Device Firmware Level: A720
Inquiry Data: HITACHI H109060SESUN600GA7201329BSASLL
Enclosure Device ID: 252
Slot Number: 3
Enclosure position: N/A
Device Firmware Level: A720
Inquiry Data: HITACHI H109060SESUN600GA7201329BRBNGL
NOTE: Some HBA firmware versions may not report the "Device Firmware Level: " information separately. In that case, the firmware level is the 4 characters immediately following the disk model name in the "Inquiry Data" field. In the examples above: "H109060SESUN600GA7201329BSD9ZL" model is H109060SESUN600G, firmware level is A720.
-
Re-enable multi-user mode from single-user mode using "exit" command or typing Ctrl-D.
-
Re-start CRS services following the steps in Note 1982342.1.
Attachments
This solution has no attachment
|
