Firmware Upgrade - Western Digital Ultrastar Data60 User Manual

User Guide
• Power off the enclosure (not self-healing).
The enclosure operates visual indicators. These indicators can be set or cleared via host request, or
autonomously by the enclosure if it detects fault conditions. The enclosure provides non-volatile memory
that records enclosure serialization and branding information. The SEP records event log entries to
non-volatile memory. The SEP implements T10 defined SMP controlled "zoning on the fly", and has the
capability to save the host defined zoning parameters in non-volatile memory. The SEP also implements
several predefined zoning configurations. These predefined configurations are selectable via SES control
operations.
4.3 Firmware Upgrade
This section provides information on actions that should be taken before starting a firmware upgrade on the
Ultrastar Data60 .
The storage administrator should determine if the applications on the enclosure should be quiesced before
the online upgrade is completed. Before upgrading enclosure firmware, review the following section to
determine whether or not the enclosure should be taken offline before upgrading. As an alternative to the
automatic firmware upgrade activation process, the storage administrator may opt to use a more controlled
process by using the non-automatic firmware activation process detailed in
(page 165) and Windows Upgrade to New Firmware (page
Attention: It is strongly recommended that the non-automatic firmware activation process
be used for either Linux or Windows. And if using a RAID adapter, only the non-automatic
firmware activation process should be used. The non-automatic update allows for control of
the process during an online upgrade. With larger enclosures, the automatic firmware upgrade
could potentially be too fast for Operating Systems to recover paths to drives before the
redundant paths go down, resulting in a loss of access to drive paths. The non-automatic
process allows the end-user to control when an IOM is activated. This allows for all paths to be
optimal at the time firmware is activated on an IOM.
SAS Configuration: If the enclosure contains SAS drives and redundant IOMs, the enclosure firmware may
be upgraded while online. This is due to the SAS configuration and host being able to manage the firmware
upgrade using host multi-pathing software. The storage administrator should ensure that there are always
redundant paths to each drive before starting an upgrade on either IOM. This will ensure that at least one
path to each drive is available during the reset of the IOM that is being upgraded.
SATA Configuration: If the enclosure contains SATA drives, the enclosure firmware should not be upgraded
while online. This is due to the SATA configuration having no redundancy with only a single IOM (the second
slot contains an IOM blank). When the IOM is rebooted, the single path to the drives to service I/O will be
taken down.
Devices (<dev>)
In order to initiate a firmware upgrade on the enclosure, a target must be identified. Linux targets are
referred to as sg (SCSI Generic) devices and appear as <dev> in the Linux Firmware Upgrade procedure.
Windows targets are referred to as SCSI devices and appear as <dev> in the Windows Firmware Upgrade.
Users should install all of the required downloads before beginning the firmware upgrade process.
Required Downloads:
• SG3 Utils: download version 1.42 from the SG3 Utils website at:
Note: Firmware upgrades do not affect any zoning configurations that have been enabled on
the enclosure.

4.3 Firmware Upgrade

Linux Upgrade to New Firmware
170).
http:/ /sg.danny.cz/sg/sg3_utils.html
4. Management
161