Western Digital Ultrastar Data60 User Manual page 176

User Guide
Step 1 : Connect the Ultrastar Data60 to a standard SAS HBA or a RAID SAS HBA hosted on the Linux
Server that presents the Enclosure Services Processor to the Linux operating system. The
Enclosure Services Processor in the Ultrastar Data60 will be referred to as an IOM.
Step 2 : Type the sg_scan -i command to verify that the enclosure has been found by the server.
# sg_scan -i | grep -i 4060 -B 1
<dev>: scsi8 channel=0 id=50 lun=0
HGST
<dev>: scsi8 channel=0 id=204 lun=0
HGST
Step 3 : The following upgrade preparation steps apply only to firmware versions 01XX-XXX or if the
user is upgrading via OOBM. If this does not apply, please proceed to the upgrade procedure.
Note: To perform an online firmware upgrade, the Ultrastar Data60 must be
configured with redundant data paths, meaning both IOMs must have a SAS Port
populated and connected to the host server.
SAS Configurations: The server host must be configured with multi-pathing
software that can handle the nature of the firmware upgrade. i.e. Once firmware
is downloaded to the IOMs, each IOM will reset and boot the new code in a
staggered fashion such that the host always has at least one path to the drives to
service I/O.
SATA Configurations: A SATA configuration should not be considered for an
online upgrade due to the single path nature of the topology.
Figure 193: Multipathing Configuration Minimum Requirement
H4060-J 2020 [rmb=0 cmdq=1 pqual=0 pdev=0xd]
H4060-J 2020 [rmb=0 cmdq=1 pqual=0 pdev=0xd]
Note: If the Ultrastar Data60 is connected to an HBA that does not present
the Enclosure Services Processor to the host for management purposes, HGST
recommends attaching the Ultrastar Data60 to a host that does expose the
Enclosure Services Processor so that the upgrade may be performed.
Attention: Beginning with firmware version 2000-073, the user may upgrade in-
band via sg_ses_microcode without the requirement of having Ethernet interfaces
actively configured with DHCP. Please proceed to the upgrade procedure.
4. Management
4.3 Firmware Upgrade
164