Chapter 2
Drive Firmware Downloading Instructions for CLARiiON Disk Arrays


2.1 Installing Drive Firmware for DAE Units in DYNIX/ptx V4.4.x Systems

On systems running DYNIX/ptx V4.4.5 or higher in the 4.4.x version train, DAE drive firmware can be installed with the download utility fwdl. This utility is a part of ptx/SPDRIVERS V2.x.x, a layered product provided with DYNIX/ptx V4.4.x.


2.1.1 Installing DAE Drive Firmware on the NUMA-Q Host Under DYNIX/ptx V4.4.x

Insert the CD-ROM containing the compatible version of DYNIX/ptx and install the appropriate versions of DAE disk drive firmware and SPDrivers software as layered products, following the normal installation procedures described in the DYNIX/ptx and Layered Products Software Installation Release Notes.


ATTENTION

The ptx/INSTALL product uses a naming convention for software and firmware versions that differs from those used by our firmware vendors. The following table maps the vendors' firmware version names to those displayed by ptx/INSTALL.

Table 2-1. Translation Between Vendor Names and ptx/INSTALL Names for Firmware Versions

Disk Drive

Vendor's Firmware Designation

ptx/INSTALL's Firmware Designation

IBM FC JBOD 18GB/9GB Disk, 10k rpm

SQ00

V0.0.0

Seagate FC JBOD 18GB/9GB disk, 7200 rpm

SQ25

V2.5.0




2.1.2 Downloading Drive Firmware to the DAE Unit Under DYNIX/ptx V4.4.x

Your NUMA-Q system must be configured to support a Fibre Channel arbitrated loop; if you have already been operating the DAE unit on a NUMA-Q system, this should already be done. If it is not, become the root user and then run the command bp /unix ff_topology 2; you must then reboot the system to put the command into effect.


ATTENTION

The effect of the bp /unix ff_topology 2 will be negated if the kernel is recompiled, thereby restoring default settings. In order to keep the system configured for FC arbitrated loop, edit the file /usr/conf/uts/io/ff/ff_space.c. Change the parameter ff_topology = FC_TOPOLOGY_FABRIC

to ff_topology = FC_TOPOLOGY_AL.


If your system is already configured to support FC arbitrated loop, perform the following procedure to download the desired drive firmware.

  1. Become root user.

  2. Determine the device names of all the drives in the DAE, as follows. This example assumes that the DAE is on fabric0.

    #dumpconf -a | grep sd
    sd10  sd       10  0x00d9f800  S  fcp    fabric0      
    sd11        sd        11  0x00dbf800  S  fcp   fabric0      
    sd12        sd       12  0x00ddf800  S  fcp    fabric0      
    sd13        sd        13  0x00dff800  S   fcp  fabric0      
    sd14        sd        14 0x00e1f800  S   fcp   fabric0      
    sd15        sd         1  0x00e3f800  S  fcp   fabric0      
    sd16        sd        16  0x00e5f800  S   fcp  fabric0      
    sd17        sd        17  0x00e7f800  S  fcp   fabric0      
    sd0         sd         3  0x00000000  S   fcp  fabric0     
    sd3         sd        15  0x00000030  S   fcp  fabric0    
    
  3. List the current value of the fabric_timeout_max parameter with the following command:

    #bp -s /unix /dev/kmem fabric_timeout_max
  4. After making a note of the current value for the fabric_timeout_max parameter, change that value to 1000, as follows:

    #bp -s /unix /dev/kmem fabric_timeout_max 1000

    You do not need to reboot in order to put this command into effect. After the firmware downloading is finished, you are advised to reset fabric_timeout_max to the default value.

  5. Stop any I/O to the drives whose firmware is being downloaded, and remove the target drive from ptx®/SVM control. Ordinarily, ptx/SVM will have already excluded a faulty drive. Refer to the ptx/SVM Administration Guide.

    If the drive was not under ptx/SVM control, remove any existing VTOC applied to the drive. In the following example, the drive is sd10.

    devdestroy /dev/rdsk/sd10
  6. Stop ptx/SESMON if it is running. Rather than using the kill command, employ the following script, which prevents possible mistyping of the process ID and also frees up memory after the sesmon daemon is stopped:

    #sh /etc/init.d/sesmon stop
  7. Run the download utility. The following example assumes that you wish to download SQ25 firmware to sd10, a single 18-GB, 7200-rpm disk drive.

    #/usr/service/bin/fwdl -mx -f /usr/ssw/fw/disk/sq25_18gb.sqfw sd10

    If the download has succeeded, you will see information similar to the following displayed:

    fwdl: Started downloading FirmWare to sd10                                    
    Device: sd10    Located On: fabric0   Unit ID: 0xd9f800                       
    fwdl: Open FW File                                                            
    fwdl: reading firmware from /usr/ssw/fw/disk/sq25_18gb.sqfw...                 
    

    After this point in the process, the output from fwdl will vary somewhat, depending on what firmware version you are downloading and what version was formerly on your drives. Unless the DAE drive firmware version you are now downloading is the very next version of the same vendor's firmware as on your existing drives, you will see a warning that the old version does not match the expected value. You may disregard this message; downloading will continue normally.

    The fwdl utility will then display output similar to the following:

    fwdl: Write Firmware File to sd10                                             
    sd10: loaded                                                                  
    fwdl: Wait for 10 sec, performing final sanity checks                         
    fwdl: New FW has been installed on sd10  
    

    The name of the vendor, the product ID, and the firmware revision number will then be displayed.

  8. The download is now complete; however, in order for the results of the download to be known to the operating system's device-status utilities such as infodev and diskid, you will have to deconfigure and then reconfigure the device, as follows. The example still assumes that you have downloaded drive firmware to device sd10 on fabric0.


    ATTENTION

    If you have used devbuild to create a volume table of contents for this device, you will need to destroy the VTOC with devdestroy before running devctl -d.


    #devctl -d sd10 
    devctl: deconfiguring sd10 from fabric0
    #devctl -c fabric0
    devctl: Found sd10
  9. Now infodev will report the current drive firmware version:

    #infodev -a sd10
    Vendor ID                       : SEAGATE                 
    Product ID                      : ST39173F CLAR09         
    Revision Level                  : SQ25                    
    Device Class                    : disk                    
    Capacity (in blocks)            : 17783112                
    Block Size                      : 512                     
    Fibre Channel Address           : 0xcc                    
    FCP LUN                         : 00:00:00:00:00:00:00:00 
    Located on                      : fabric0                 
    
  10. Place the drive with its updated firmware under ptx/SVM control. Refer to the ptx/SVM Administration Guide. If the device was never under ptx/SVM control, reattach its VTOC with the devbuild command.

  11. Restore the fabric_timeout_max parameter to the value that it had before the firmware download. In the following example, that value is assumed to have been 45.

    #bp -s /unitx/dev/kmem fabric_timeout_max 45
  12. Restart ptx/SESMON.

    #sh /etc/init.d/sesmon start

    Installation of the disk-drive firmware is now complete.


2.2 Installing Drive Firmware for DAE Units in DYNIX/ptx V4.5.x Systems

On systems running DYNIX/ptx V4.5.1 or higher, DAE drive firmware can be installed with the Common Firmware Download utility, cfwdl. This utility is a part of ptx/SPDRIVERS V3.1.0, a layered product provided with DYNIX/ptx V4.5.1 and higher versions. See Chapter of the DYNIX/ptx V4.5.1 and Layered Products Software Installation Release Notes for detailed instructions on downloading disk drive firmware with cfwdl.


2.3 Installing Drive Firmware for DPE Units in NUMACenter


ATTENTION

DPE disk arrays are not supported in NUMACenterTM 2C (released Q1 2000).


Drive firmware for DPE units in the NUMACenter should be downloaded only by NUMA-Q Customer Support providers. Complete instructions for downloading drive firmware to DPE units under the Windows NT® operating system in the NUMACenter environment are available to NUMA-Q Customer Support providers in Technical Service Note hw/disk/98, "Steps for Updating CLARiiON DPE Drive Firmware Under Windows NT."