[rescue] Storage Firmware Update
Tato Sampurno
tatosamp at bluebottle.com
Tue Jul 10 10:43:23 CDT 2007
Hi All,
I have a problem in updating a Sun StorEdge 3310 SCSI Disk Array.
Before Updating I issue a command to check the firmware version and safte
version and redundancy condition
# sccli -y c3t0d0 show inquiry
sccli: selected device /dev/rdsk/c3t0d0s2 [SUN StorEdge 3310 SN#08386C]
Vendor: SUN
Product: StorEdge 3310
Revision: 0325
Peripheral Device Type: 0x0
NVRAM Defaults: 325S 3310 v1.37
Bootrecord version: 1.31G
Page 80 Serial Number: 08386C36D5B25E02
Page 83 Logical Unit Device ID: 600C0FF00000000008386C36D5B25E02
Page D0 Target ID: 0
Ethernet Address: 00:C0:FF:88:38:6C
Device Type: Primary
# sccli -y c3t0d0 show safte
sccli: selected device /dev/rdsk/c3t0d0s2 [SUN StorEdge 3310 SN#08386C]
Ch Id Chassis Vendor Product ID Rev Package
---------------------------------------------------------
0 14 08386C SUN StorEdge 3310 A 1159 1159
# sccli -y c3t0d0 show redundancy
sccli: selected device /dev/rdsk/c3t0d0s2 [SUN StorEdge 3310 SN#08386C]
Primary controller serial number: 82890
Redundancy mode: Active-Active
Redundancy status: Enabled
Secondary controller serial number: 79603
I update the safte version to 1170 by issuing the following command, but
beforehand I booted into single user mode to stop the activity on the
storage and mounted the /opt manually
sccli> download safte-firmware saftefw_3310_1170.bin
sccli: Downloading SAFTE firmware package to SAFTE targets
Module EMU ENVIRONMENTALS already updated at CH 0 ID 14 Rev: 1006
Module EMU ISEMS already updated at CH 0 ID 14 Rev: A000
Module EMU LED CONTROLLER already updated at CH 0 ID 14 Rev: A000
Module POWER SUPPLY CTRL already updated at CH 0 ID 14 Rev: A000
sccli: downloading SAFTE module: SAFTE HC11
............................
........................................................................
CH 0 ID 14 succeeded
sccli: wait 10 seconds for SAF-TE device resetting
sccli: SAFTE firmware package download succeeded (rev 1170 CH 0 ID 14)
sccli: wait 10 seconds for SAF-TE device updating database
Download Status Report
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
SAF-TE Firmware download completed (CH 0 ID 14)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
sccli: download enclosure firmware: succeeded
sccli> download safte-firmware saftefw_3310_1170.bin
sccli: Downloading SAFTE firmware package to SAFTE targets
Module EMU ENVIRONMENTALS already updated at CH 0 ID 14 Rev: 1006
Module EMU ISEMS already updated at CH 0 ID 14 Rev: A000
Module EMU LED CONTROLLER already updated at CH 0 ID 14 Rev: A000
Module POWER SUPPLY CTRL already updated at CH 0 ID 14 Rev: A000
Module SAFTE HC11 already updated at CH 0 ID 14 Rev: 1170
sccli: wait 10 seconds for SAF-TE device resetting
sccli: SAFTE firmware package download succeeded (rev 1170 CH 0 ID 14)
sccli: wait 10 seconds for SAF-TE device updating database
Download Status Report
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
SAF-TE Firmware download completed (CH 0 ID 14)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
sccli: download enclosure firmware: succeeded
sccli> exit
# sccli -y c3t0d0 show safte
sccli: selected device /dev/rdsk/c3t0d0s2 [SUN StorEdge 3310 SN#08386C]
Ch Id Chassis Vendor Product ID Rev Package
---------------------------------------------------------
0 14 08386C SUN StorEdge 3310 A 1170 1170
This confirms that the safte update is succesfull, Then followed with the
firmware update by issuing the following command.
# ./s3kdlres /var/tmp/xml_conf.out --device=c3t0d0
"/opt/SUNWsscs/sbin/sccli" -y -w "" c3t0d0 about
"/opt/SUNWsscs/sbin/sccli" -y -w "" c3t0d0 show access
Access mode: inband
*********************************************************************
* NOTE: In-band devices may require significant manual *
* reconfiguration. Target IDs, LUN mappings, *
* World-Wide-Names, FC port configurations, may change *
* and render the array inaccessible. In addition, a host *
* reboot may be required to reestablish contact with the *
* controller. *
* *
* If the script cannot continue, it may be interrupted with *
* Control-C. After reestablishing connectivity, remaining *
* configuration settings can be restored with the *
* --restore=all option to this script. *
* *
* Ex: s3kdlres <XMLfile> --device=<device> --restore=all *
* *
* Manually reconfigured in-band devices must be consistent *
* with the original configuration. If not, the above command *
* will again reset the channel settings, and communication *
* may be lost. *
* *
* Also, passwords must be restored manually with sccli. *
* Ex: sccli <device> set password <password> *
*********************************************************************
Continue? <yes/no>: [no] yes
"/opt/SUNWsscs/sbin/sccli" -y -w "" c3t0d0 show inq
Getting Redundancy
"/opt/SUNWsscs/sbin/sccli" -y -w "" c3t0d0 show redundancy
Getting Current Configuration
"/opt/SUNWsscs/sbin/sccli" -y -w "" c3t0d0 show config -x
Saving Original Configuration
Load controller firmware? <yes/no>: [no] yes
Enter firmware file: /var/tmp/113722-11/SUN413B-3310.bin
Downloading firmware: /var/tmp/113722-11/SUN413B-3310.bin
"/opt/SUNWsscs/sbin/sccli" -y -w "" c3t0d0 download controller-firmware -r
--don
t-reset-nvram "/var/tmp/113722-11/SUN413B-3310.bin"
WARNING: /ssm at 0,0/pci at 18,600000/pci at 1/scsi at 4/sd at 0,0 (sd31):
disk not responding to selection
Checking Redundancy
"/opt/SUNWsscs/sbin/sccli" -y -w "" c3t0d0 show redundancy
Redundancy status after controller reset does not match original
Redundancy status.
Original Redundancy Status: Enabled
New Redundancy Status: Scanning
If the problem persists, rerun script from the beginning.
Retry? <yes/no>: yes
"/opt/SUNWsscs/sbin/sccli" -y -w "" c3t0d0 show redundancy
Redundancy status after controller reset does not match original
Redundancy status.
Original Redundancy Status: Enabled
New Redundancy Status: Scanning
If the problem persists, rerun script from the beginning.
Retry? <yes/no>: yes
"/opt/SUNWsscs/sbin/sccli" -y -w "" c3t0d0 show redundancy
Redundancy status after controller reset does not match original
Redundancy status.
Original Redundancy Status: Enabled
New Redundancy Status: Scanning
If the problem persists, rerun script from the beginning.
Retry? <yes/no>: no
After this update I lost redundancy on the controller, and can't recover the
redundancy, The state of Controller redundancy is scanning, and the
controller serial num state 0.
# sccli -y c3t0d0 show redundancy
sccli: selected device /dev/rdsk/c3t0d0s2 [SUN StorEdge 3310 SN#08386C]
Primary controller serial number: 82890
Primary controller location: N/A
Redundancy mode: Active-Active
Redundancy status: Scanning
Secondary controller serial number: 0
Any way or advice, on how to get the redundancy back, cause when I look at
the Led indicator Primary controller and Secondary controller is on a good
working order the only difference is that the Secondary Batt Led is dead. It
does not even glow.
Thank You for any advice or assistance.
Regards
Tato Sampurno
Indonesia
----------------------------------------------------------------------
Free pop3 email with a spam filter.
http://www.bluebottle.com/tag/5
More information about the rescue
mailing list