Firmware Download - Parallel Upgrade Tool (PUT)

Parallel Upgrade Tool (PUT) Reference

Product
Parallel Upgrade Tool (PUT)
Release Number
3.09
Published
February 2020
Language
English (United States)
Last Update
2020-02-24
dita:mapPath
ows1493317469465.ditamap
dita:ditavalPath
ows1493317469465.ditaval
dita:id
B035-5716
Product Category
Software
Teradata Tools and Utilities
The Firmware Download screen includes the following subsections:
  • Interconnect Firmware: Displays a final summary of the supported Interconnect switches for download.
  • Storage Firmware: Displays a final summary of the arrays that are compatible and optimal for download. It also provides a list of downloads performed by each array.

If you selected Query Array Health as the component type, PUT skips this step.

Interconnect Firmware Download

After you have confirmed the download instructions and clicked Next, PUT begins downloading the firmware selected to the Interconnect specified.

PUT downloads one Fabric at a time. A status report appears after download to each Fabric. When two Fabrics are selected for download, PUT presents the option of proceeding to the next fabric or not after the first Fabric download completes successfully.

When you click Next, the PUT Finished screen appears and the operations ends.
The following information describes how firmware is downloaded:
  • During the firmware download, switches reboot twice for a 5030 switch and once for all other types. See the following table for Time to Copy and Install and Time to Reboot based on switch type.
    Model Time to Copy and Install Time to Reboot
    IS5030 15 minutes 15 minutes
    SX6036 15 minutes 15 minutes
    SX6506 30 minutes 20 minutes
    SX6518 45 minutes 40 minutes
    SX6536 60 minutes 60 minutes
    SX7800 15 minutes 5 minutes
  • If downloading to the first Fabric fails, PUT does not proceed to the second Fabric download.

Storage Firmware Download


Begin Firmware Download

After you have confirmed the download instructions and clicked Next, PUT begins downloading the firmware selected to the Interconnect specified.

PUT downloads, in parallel, at the storage array level. For example, if there are two arrays attached to two nodes it processes those downloads at the same time. If multiple firmware download types were selected for an array, subsequent downloads occur after the previous download and health check are successful. When all the downloads are complete, a status report appears showing whether the downloads were successful.

Firmware download results

Click Next. The PUT Finished screen appears and the operations ends.

NetApp Arrays

The following information describes how firmware is downloaded on NetApp Storage Arrays:
  • ESM and ESM NVRAM firmware are downloaded one tray at a time.
  • Drive firmware downloads are performed on one drive from each optimal drive group in parallel.
  • If a failure occurs on one drive in a drive group during a drive firmware download on a Teradata Storage Array (or if there is already a non-optimal drive in the group), a download to the remaining drives in the group is not attempted.
    • Drive download to remaining drive groups that is not yet attempted will still be performed.
    • Download to unassigned drives are also grouped together.
  • Drive firmware download is also attempted on Global Hot spare drives that are not in use. PUT unassigns the drives as GHS drives, downloads the firmware, and reassigns the drives as GHS drives.
  • Due to the large number of drives present in arrays, the drive firmware download may take several hours.
Do not perform any other operations on the array for at least two minutes after the download is completed, so the new firmware can be saved and initialized.

DotHill Arrays

Note the following information about how firmware is downloaded on DotHill Storage Arrays:
  • Drive firmware is updated in parallel across vdisks, one drive at a time, per vdisk. One exception: Arrays with controller firmware version CF101XXXX download sequentially, to one drive at a time.
  • The drive download is only attempted if the following conditions are met:
    • The vdisk is either in an optimal state or a degraded state (Degraded state means 1 disk is down in the RAID 6 vdisk).
    • The total number of drives in a FAILED or LEFTOVER state within the array is less than or equal to 10% of the total number of drives in the array.