logo
Manual Pages
Table of Contents

NAME

na_disk_fw_update - update disk firmware

SYNOPSIS

disk_fw_update < disk_list >

DESCRIPTION

Use the disk_fw_update command to manually update firmware on all disks or a specified list of disks on a filer. Each filer is shipped with a /etc/disk_fw directory that contains the latest firmware versions. Because this command makes disks inaccessible for up to five minutes after the start of its execution, network sessions that use the filer must be closed down before running the disk_fw_update command. This is particularly true for CIFS sessions that might be terminated while this command is executed. For Data ONTAP 6.0 and later, the firmware is downloaded automatically to disks with previous versions of firmware. For information on automatic firmware update downloads, see AUTOMATIC vs. MANUAL FIRMWARE DOWNLOAD. On configurations using software-based disk ownership both automatic and manual downloads update firmware only for those disks owned by the local filer. Disks owned by the partner filer are updated when the automatic download or the manual disk_fw_update command is executed on that particular node. Disks that are owned by neither filer are not updated. To update all disks, you must assign ownership to the unowned disks before running the disk_fw_update command. Ignore any warning messages issued while the disk firmware is being updated. To download the firmware to every disk, use the disk_fw_update command without arguments. To download the firmware to a particular list of disks, specify the disk names in the command. The disk names are in the form of cahnnel_name.disk_ID. For example, if you want to update firmware on disk ID 0, 1 and 3 on adapter 8, enter the following command: disk_fw_update 8.0 8.1 8.3 The command applies to both SCSI disks and Fibre Channel disks. If you need to view the current firmware versions, enter the sysconfig -v command. The following example displays a partial output from the sysconfig -v command, where the firmware version for the disk is NA01: 
    slot 8: Fibre Channel Host Adapter 8 (QLogic 2200 rev. 5, 64-bit, L-port, )
                  Firmware rev:   2.1.20
                  Host Loop Id:   7       FC Node Name:   2:000:00e08b:00c702
                  Cacheline size: 8       FC Packet size: 2048
                  SRAM parity:    Yes     External GBIC:  Yes
                    0: NETAPP   X225_ST336704FC  NA01  34.5GB ( 71687368 512B/sect)
The firmware files are stored in the /etc/disk_fw directory. The firmware file name is in the form of prod_uct_ID.revision.LOD. For example, if the firmware file is for Seagate disks with product ID X225_ST336704FC and the firmware version is NA02, the file name is X225_ST336704FC.NA02.LOD. The revision part of the file name is the number against which the filer compares each disk's current firmware version. If the filer in this example contains disks with firmware version NA01, the /etc/disk_fw/X225_ST336704FC.NA02.LOD file is downloaded to every disk when you execute this command.

AUTOMATIC vs MANUAL FIRMWARE DOWNLOAD

For Data ONTAP 6.0 or later, firmware is automatically downloaded to those disks with previous versions of firmware following a system boot or disk insertion. The firmware: 
  -    Is not automatically downloaded to the filer's partner filer in
       a cluster.

  -    Is not automatically downloaded to unowned disks on filers
       configured to use software-based disk ownership.

  -    For Data ONTAP 7.0.1 or later a new registry entry controls how the
       automatic firmware download feature works:

       If raid.background_disk_fw_update.enable is set to off,
       disk_fw_update will run as in previous releases of Data ONTAP.

       If raid.background_disk_fw_update.enable is set to on,
       disk_fw_update will only automatically update to filesystem disks
       contained in RAID4 volumes. Firmware updates for spares and filesystem
       disks contained within RAID-DP, mirrored RAID-DP and mirrored RAID4
       volumes will be done in a non-disruptive manner in the background after
       boot. Firmware download for these disks will be done sequentially by
       temporarily offlining them one at a time for the duration of the download.
       Once firmware is updated, the disk will be onlined and restored back to
       normal operation mode.
During an automatic download to a clustered environment, the firmware is not downloaded to a cluster partner's disk. Automatic downloads to a cluster are unsuccessful with certain disk drives. In such cases, you may need to manually execute the disk_fw_update command to update the disks in a cluster. When you manually key in the disk_fw_update command, the firmware is: 
  -    Updated on every disk regardless of whether it is on the A-loop,
       the B-loop, or in a clustered environment.

  -    If the filer is configured in a software-based disk ownership
       system only disks owned by this filer are updated.
Follow the instructions in HOW TO UPDATE FIRMWARE FOR A CLUSTER to ensure that the updating process is successful. Data ONTAP 6.1 and later supports redundant path configurations for disks in a non-clustered configuration. Firmware is automatically downloaded to disks on the Aloop or B-loop of redundant configurations that are not configured in a cluster and are not configured to use software-based disk ownership.

AUTOMATIC BACKGROUND FIRMWARE UPDATE

In Data ONTAP 7.0.1 or later, firmware can be updated in the background so clients are not impacted by the firmware update process. This functionality is controlled by the registry entry raid.background_disk_fw_update.enable. The default value for this option is on. When disabled or set to "off", disk_fw_update will update firmware in automated mode just like on previous releases of Data ONTAP. Namely all disks which are downrev will be updated regardless of if they are SPARE or filesystem disks. When enabled or set to "on", background disk_fw_update will update firmware in automated mode only to disks which can be offlined successfully from active filesystem raid groups and from the spare pool. For filesystem disks, this capability currently exists within volumes of type RAIDDP, mirrored RAID-DP, and mirrored RAID4. To ensure a faster boot process, no firmware will be downloaded to spares and filesystem disks contained in the above volume types. However, firmware updates for disks within RAID4 volumes will be done at boot. RAID4 volumes can be temporarily (or permanently) upgraded to RAID-DP to automatically enable background firmware update capability. This provides the highest degree of safety available, without the cost of copying data from each disk in the system twice. Disks are offlined one at a time and then firmware is updated on them. The disk is onlined after the firmware update and a mini/optimized reconstruct happens for any writes which occurred while the disk was offline. Background disk firmware update will not occur for a disk if its containing raid group or volume is not in a normal state (e.g if the volume/plex is offline or the raid group is degraded). However, due to the continuous polling nature of background disk firmware update, firmware updates will resume once the raid group/plex/volume is restored to a normal mode. Similarly, background disk firmware updates are suspended for the duration of any reconstruction within the system.

CLUSTER CONSIDERATIONS

When you are running a clustered configuration, do not attempt takeovers or givebacks during the execution of the disk_fw_update command. If you use the manual disk_fw_update command on a filer that belongs to a cluster, the filer downloads the firmware to its disks and its partner's disks, unless the filers are configured for software-based disk ownership. In that configuration firmware is only downloaded to disks the filer owns. The automatic firmware download only takes place on a filer's local disks. For cluster failover configurations, clustering must be enabled and the CFO interconnect must be linked.

HOW TO UPDATE FIRMWARE FOR A CLUSTER

The automatic download of firmware updates can lead to problems when filers are configured in a clustered environment. Known disk manufacturer limitations on certain disks further contribute to problems with firmware updates. For this reason, Data ONTAP does not allow firmware updates by automatic download to disk models with known limitations when a filer is configured in a clustered environment. Disks with known limitations can only accept firmware updates if the disk_fw_update command is executed manually. You may need to enter and run the command yourself. However, no matter which disks your clustered filers use, it's safest to update firmware this way. Use the following procedure to successfully update your disk firmware in a clustered environment: 
   1. Make sure that the filers are not in takeover or giveback mode.

   2. Install the new disk firmware on Filer A's disks by issuing the
      disk_fw_update command on Filer A.

   3. Wait until the disk_fw_update command completes on Filer A, and
      then install the new disk firmware on Filer B's disks by issuing
      the disk_fw_update command on Filer B.

  Alternatively, if the registry entry raid.background_disk_fw_update is
  enabled then one simply needs to allow the cluster partners to update
  firmware one disk at a time in automated background mode.

SEE ALSO

na_partner(1)
Table of Contents