Western Digital Ultrastar Data60 User Manual page 186

User Guide
Step 4 : Issue the following command to activate IOM A:
sg_ses <dev> -p4 -c -d 02,00,01,00
Step 5 : Ensure Windows MPIO can see all paths to the drives after activating IOM A.
a. Execute the following command:
Important: Due to the firmware image being a .tar.gz file, the enclosure has to
unpack and load the firmware onto the respective ICs which may take up to 15
minutes. Once the sg_ses_microcode command is issued wait 20 minutes to
ensure the enclosure has time to perform this process. To check the status of this
process, use the Redfish out-of-band management to make a GET request to the
following target:
curl -G -k -u admin:admin -H "Content-type: application/
json" https://<ip address>/redfish/v1/UpdateService/Actions/
UpdateService.SimpleUpdate/Status
Note: Execute the command until you see the following result:
{"ErrorCode":0,"StatusCode":2,"Description":"FW update completed.
Waiting for activation.","EstimatedRemainingMinutes":0}
Attention: If the OOBM is not being used, query Page Eh by executing the
following command
sg_ses <dev> -p 0xe
the output may be inaccurate, please ignore and issue the command again. The
string to observe for download microcode status is "Complete, no error, start
after hard reset or power cycle [0x11]" before proceeding to the activate step.
Example output:
sg_ses <dev> -p 0xe
HGST H4060-J <FW Version>
Download microcode status diagnostic page:
number of secondary subenclosures: 0
generation code: 0x0
subenclosure identifier: 0 [primary]
download microcode status: Complete, no error, start after
hard reset or power cycle [0x11]
download microcode additional status: 0x0
download microcode maximum size: 1703914 bytes
download microcode expected buffer id: 0x0
download microcode expected buffer id offset: 0
Note: Only activate one IOM at a time to ensure there is always at least one path
to the drives to service I/O while an IOM is being reset. The user will need to
issue a reset command to each IOM to activate the firmware using an sg_ses
command to ensure this occurs properly.
4.3 Firmware Upgrade
. The first time this command is issued,
4. Management
174