Chapter 4
Upgrading and Rebooting CSM Software in S5000 Systems

Use the following procedures on all S5000 systems to perform any of the following tasks:

The distribution CD-ROM jewel case contains a listing of the software contained on the disk. Verify that the disk contains the system software CSM V1.6.1.


4.1 Upgrading CSM System Software

Two types of procedures are provided in this section:


ATTENTION

Bootstring examples are shown in this section for a default setup, with the root partition being in partition 0 of disk 0, the /usr partition being in partition 2 of disk 0, and /usr/ssw residing in the /usr partition. A bootstring for this system would be similar to the following example:

qd(0,2)/ssw/fw/csm/lvlB

However, some systems will have different setups and require different bootstrings. With DYNIX/ptx V4.4, the default is to have /usr reside in the same partition as root, and the VTOCs for some disks have been revised to support this. A bootstring for this system would be similar to the following example:

qd(0,0)/usr/ssw/fw/csm/lvlB

Some administrators prefer to keep the firmware in a separate disk partition. For example, they might keep the firmware in partition 3 of disk 0, and mount this filesystem on /usr/ssw. A bootstring for this system would be similar to the following example:

qd(0,3)/fw/csm/lvlB

In all cases, the leading '/' character is optional. The actual bootstrings for your particular system may vary from the examples here.



4.1.1 Summary Procedure for Experienced Installers

Each step in the Summary Procedure correlates to the same step number in the Detailed Procedure, so that users of the Summary Procedure can easily refresh their memories on any step.


ATTENTION

When upgrading from CSM V1.4.1 or earlier to CSM V1.5 or later, the CSM software automatically scrubs the NVRAM and installs the factory default settings. This scrubbing process erases all NVRAM data including any custom data you may have stored there. Before installing the new CSM software, write down any customized NVRAM data so that you can re-enter the data manually after the scrub. Also, the bs save and bs restore commands can be helpful in preserving bootstrings. If the system is running Windows NT and NVRAM is scrubbed, you must stop the boot at Level-A and change the DYNIX/ptx bootstrings to Windows NT bootstrings.


  1. Make sure that there is a correct /usr/ssw directory structure on a qd disk connected to CSM Channel 0, where the system software will be loaded.

  2. Record any custom NVRAM data before proceeding.

  3. Install the new version of the CSM software from the distribution CD-ROM or the tape containing the software for CSM V1.6.1. DO NOT BOOT TO THE OPERATING SYSTEM LEVEL AT THIS TIME.


    ATTENTION

    Some pathnames and device names might vary depending on whether you are installing from tape or from CD-ROM.



    ATTENTION

    To install CSM software on DYNIX/ptx systems, refer to the DYNIX/ptx and Layered Product Software Installation Release Notes. Afterwards, return to Step 4 to update the CSM board Flash PROMs.


  4. Take the system down to Level-B of the Power-Up Monitor. Use init 0. Do not use Ctrl-P.

  5. Update the CSM board Flash PROMs with fprog. Quit fprog and boot a new Level-B, using the zap command to simulate a system power cycle. Stop the boot at Level-B.

  6. Set production operating mode using the opmode p command at the Level-B prompt. This step is done automatically after an NVRAM scrub.

  7. Run the print command to verify that the bootstrings and flags settings are correct. Make changes as required. When the Level-B software runs after the zap, it overwrites the NVRAM with factory defaults (if you're installing a new version of CSM SW). Restore any custom settings at this time.

  8. From Level-B, use the config command to verify matching Aver and Bver levels.

  9. Boot the operating system with the bh command.

  10. Configure the diagnostics for clustered or HIAV (High Availability) systems. Update script files to enable Diagnostic Executive use with clustered or HIAV systems.


4.1.2 Detailed Procedure

The system software must be installed in a filesystem on a qd disk drive connected to CSM Channel 0. The installation script will look for a /usr/ssw filesystem in a partition of a qd disk drive on the bus controlled by that SCSI channel.


ATTENTION

When upgrading from CSM V1.4.1 or earlier to CSM V1.5 or later, the CSM software automatically scrubs the NVRAM and installs the factory default settings. This scrubbing process erases all NVRAM data including any custom data you may have stored there. Before installing the new CSM software, write down any customized NVRAM data so that you can re-enter the data manually after the scrub. Also, the bs save and bs restore commands can be helpful in preserving bootstrings.

If the system is running Windows NT and NVRAM is scrubbed, you must stop the boot at Level-A and change the DYNIX/ptx bootstrings to Windows NT bootstrings.


  1. If a /usr filesystem is already mounted on a qd disk connected to CSM Channel 0, skip this step and start the installation with Step 2.

    Set up a new directory structure if all of /usr currently resides on a qd disk not connected to CSM Channel 0.

    Create a /usr/ssw directory structure in partition /dev/dsk/qd0s2 of the qd disk and mount it as a filesystem.

    After creating the /usr/ssw directory, create a /usr/ssw/diag directory and a /usr/ssw/fw directory.

  2. Before proceeding, write down any customized NVRAM data (boot string settings, etc.) The installation process overwrites NVRAM with factory default data so any customized information is lost. After installation of CSM software, re-enter the customized data manually.

  3. Install the new software.


    ATTENTION

    To install CSM software on DYNIX/ptx V 4.4 systems, refer to the DYNIX/ptx and Layered Product Software Installation Release Notes. Afterwards, return to Step 5 to update the CSM board Flash PROMs.


    To install the CSM software on systems running DYNIX/ptx 4.2, complete the following steps:


    ATTENTION

    Use the distribution CD-ROM or the tape containing the software for CSM V1.6.1.


    1. Insert the distribution medium into the appropriate drive.

    2. The installation device must match your distribution medium. If necessary, use the Change Installation Device option in the Software Management menu to change to CD-ROM or tape as appropriate.

    3. Select the Preview Software Package option. For the installation procedure, the name of this product is csm.

      The output of the preview and installation phases of the installation script is specific for the system type. The output examples in this procedure may differ in terms of drive unit numbers, file space requirements, and bootstring information during the actual installation.

    4. Run the preview phase.

      The Bill of Materials (BOM) and other installation files are loaded into the /usr/options/csm directory. The preview log is named /usr/options/csm/preview.log. To read this file, use the Edit/View Preview Log option from the Software Management menu.

      If the preview phase reports that files are in conflict or will be deleted, be sure to examine the preview log to determine whether you need to take any actions to resolve the conflicts or to save files.

      The preview phase of the installation script produces a dialog similar to the following example:

      Previewing csm from CD-ROM Rewinding
      the tape ... Installation script, preview step, for CSM SW 1.6.1 Install CSM
      Diagnostic Executive?  [y] : y Filesystem /user 41611 K free      70 K space
      needed to do install      0 K required to preload conflicts      11075 K required
      to preload all files      0 K required to save old files
      
    5. Run the preload phase. This phase is optional if your system is low on disk space.


      ATTENTION

      The /usr/options/csm/newfiles directory is the default location for preloaded files. If the newfiles directory contains preloaded files from an earlier version of this software, be sure to move or delete the directory before you start the preload phase. When the preload phase is complete, you can examine the preloaded files. To resolve file conflicts, merge the local information from the files on the system into the preloaded files.


    6. Run the install phase.


      ATTENTION

      The /usr/options/csm/oldfiles directory is the default location for saving locally modified files. If the oldfiles directory currently contains files saved from an earlier version of this package, be sure to move or delete the directory before you start the install phase.


      Select the Install Software Package option of the Software Management menu to run the install phase. During the installation phase, note the online caution about updating CSM PROMs before rebooting.


      ATTENTION

      In the following example, all of /usr is installed in the same qd partition. If you install only the /usr/ssw filesystem in the partition, then the output script will not show the " qd(0x0,2)ssw/" portion of the path. Some pathnames and device names will vary depending on whether you are installing the system software from tape or from CD-ROM.


      Installation script, install step, for CSM SW 1.6.1 Your
      options for continuing are:    1)Install files without preserving locally
      modified files that      are overwritten or deleted.    2)Install files preserving
      locally modified files that are      overwritten or deleted. How would you
      like to proceed?  1 Installing CSM fw... ****************************************************************
      *                    CAUTION                                   * *       
                                                            * *   The CSM Flash
      PROMs MUST be updated before rebooting the   * *   system.  The Flash PROM
      update procedure is described in   * *   the CSM Software Release Notes. 
                                * *                                            
                       * ****************************************************************
       CSM Firmware Monitor boot strings: bs lvlBPath:              "qd(0x0,2)ssw/fw/csm/lvlB"
      bs diagPath:              "qd(0x0,2)ssw/diag/csm/exec" bs lvlBTests:     
             "qd(0x0,2)ssw/fw/csm/" bh loaderPath:            "qd(0x0,2)ssw/boot"
       CSM Flash Prom data file: "qd(0x0,2)ssw/fw/csm/lvlA.rom  "The bootstring
      info is captured in /usr/options/csm/BOOTSTRING-INFO  Installing CSM Diagnostic
      Executive... Installing CSM Firmware in reserved disk partition... 52+1 records
      in 53+0 records out Press RETURN to redisplay menu
      

      When the install phase is complete, you can resolve file conflicts by merging local information from the saved files into the files now on the system.


      ATTENTION

      Do not reboot the system at this time because the current Level-A may not match the new Level-B if this installation is an upgrade.


  4. Go to Level-B of the Power-Up Monitor.


    ATTENTION

    Do not use Ctrl-P to go from the operating system to Level-B in this procedure. This command leaves the operating system running in the background. The fprog utility will display a warning message and will not run until the operating system is shut down.


    Use the ptx/ADMIN menu system to take the system to the firmware level (Level-B).

    (An alternative to the menu system is to use init 0.)

  5. CSM versions prior to V1.5 had revision format number 0, and versions later than V1.5 have format revision number 1. Beginning with CSM SW V1.5, the firmware checks the format revision number in NVRAM. If that number does not match the number for the firmware level being installed, the firmware overwrites the NVRAM with factory default data. And of course that would erase any custom boot strings or other NVRAM data.

    Update the CSM board PROMs.

    The firmware in the CSM board flash PROMs (Level-A) must be the same version as the system software on the boot disk (Level-B).

    If you are upgrading the system software to a new version, update (flash) the PROMs with the fprog command.


    ATTENTION

    When replacing the CSM board, you must verify that Level-A and Level-B are at the same revision level. (Use the config command.) If they are not at the same revision level, you must update the PROMs.


    Before beginning this procedure, find the path for the new Level-A software in the file /usr/options/csm/BOOTSTRING-INFO.

    To update the flash PROMs on the CSM board, follow these steps:

    1. Ensure that the system is at Level-B.


      ATTENTION

      Do not use Ctrl-P to go from the operating system to Level-B for this procedure. Ctrl-P leaves the operating system running in the background, and fprog will not run if the operating system is running.



      ATTENTION

      If you put incorrect data into the flash PROMs, the system will not boot after the next power cycle.


    2. At the Level-B prompt, enter fprog.

    3. Select option 2 from the menu. The CSM board SLIC ID will automatically be selected as the default value.

    4. Select option 1 from the fprog menu to update the flash PROMs and select a filename.

      Typically, the filename to program into the flash PROMs will be:

      qd(0,2)ssw/fw/csm/lvlA.rom (for a CSM board)

      After you select the filename, the system displays the following:

      Verifying input data checksum
      Programming FPROM at slic address xx, 0x80000 bytes Using FPROM data file
      qd(0,2)ssw/fw/csm/lvlA.rom Continue? (y/n)
      

      (The filename might be different on your system.)

      If you are satisfied with the selections, enter y to continue. If you want to make a change, enter n. The system will return you to the fprog menu, where you have the option to select a different file or change the SLIC ID.

      The programming operation can take up to one minute. While the PROMs are being programmed, the system will display the following:

      Programming zeros Erasing FPROM Programming ..................................
      Verifying FPROM checksum FPROM programming complete.
      
    5. Exit fprog by choosing option q from the fprog menu.

  6. Set the system to production operating mode. If the software automatically scrubbed NVRAM, you can skip this step because the system is already in production operating mode. If the NVRAM was not scrubbed, enter the following command at the Level-B prompt:

    ---> opmode p

  7. Set up the boot strings and verify matching Level-A and Level-B versions.

    Make sure that the power-up monitor bootstrings are set to the same paths as listed in the output from the installation script, as shown in Step 3.

    During installation, the system displayed the name of each product as it was installed and listed the path for the bootstrings. That bootstring information was also captured and saved in the file /usr/options/csm/BOOTSTRING-INFO.

    You can look at the current values of the bs, bo, and bh bootstrings by using the print command from the Level-B prompt. For example:

    ---> print bs

    ---> print bo

    ---> print bh

    If any of the bootstrings are different, you must change them to match the output from the installation script. For example:

    ---> bh loaderPath=qd(0,2)ssw/boot


    ATTENTION

    If the CSM software is moved to a different disk or partition after initial installation, you must revise the BOOTSTRING-INFO file so that it will provide accurate bootstring path information for later reference.


    Boot a new Level-B using the zap command to simulate a system power cycle and activate the new software. Stop the boot at Level-B.

  8. At the Level-B prompt, enter config and verify that the CSM board has matching Aver and Bver values.

  9. Boot the operating system.

    At the Level-B prompt, enter bh to boot the operating system.

  10. Configure the diagnostics for clustered or HIAV systems, if appropriate.

    After installing the Diagnostic Executive software on a system that is part of a cluster or a HIAV system, you must edit the files /usr/ssw/diag/csm/script and /usr/ssw/diag/csm/script.auto from the operating system to include the following line:

    cc y

    This line must appear in these two script files before any other commands in the script files. Refer to your Diagnostic Executive User's Guide for details about the cc y command.


4.2 Booting System Software from CD-ROM or Tape


4.2.1 Replacing Corrupted Level-B Software


ATTENTION

Refer to Section 4.2.2 for information on how to boot a new Diagnostic Executive from disk, CD-ROM, or tape.


If the current Level-B is corrupted, boot the system software directly from the distribution CD-ROM or tape containing CSM SW V1.6.1.

  1. Power-cycle the system and halt the booting process at the Level-A prompt (->) by typing any character within 5 seconds after the prompt appears.

  2. Load the distribution CD-ROM or tape into the appropriate drive. (The drive must be connected to CSM channel 0. Drives connected to other SCSI ports are not bootable.)

  3. Boot the CSM software.

    If booting from CD-ROM, enter:

    -> bs qc(0x500,0)/usr/ssw/fw/csm/lvlB

    If booting from tape, enter:

    -> bs tq(0x400,1)

  4. When the Level-B prompt (--->) appears, you can boot either the operating system:

    ---> bh

    or the Diagnostic Executive:

    ---> bs doDiags


4.2.2 Booting the Diagnostic Executive from Level-B


ATTENTION

In the following examples of system output, the file sizes in bytes will vary from release to release.



4.2.2.1 Booting from Disk

To boot the diagnostics from disk while at a current Level-B prompt, enter:

---> bs qd(0,2)ssw/diag/csm/exec

The system will display the following messages:

booting CSM from 'qd(0,2)ssw/diag/csm/exec' loading 1191936
bytes

4.2.2.2 Booting from CD-ROM

To boot the diagnostics from CD-ROM while at a current Level-B prompt, enter:

---> bs qc(0x500,0)/usrssw/diag/csm/exec

The system will display the following messages:

booting CSM from 'qc(0x500,0)ssw/diag/csm/exec' oading
1191936 bytes

4.2.2.3 Booting from Tape

To boot the diagnostics from tape while at a current Level-B prompt, enter:

---> bs tq(0x400,3)

The system will display the following messages:

spinning up disks  0 1 2 3 4 5 booting CSM from 'tq(0x400,3)'
loading 1191936 bytes

4.3 Booting from CD-ROM When the Boot Disk Is Blank or Defective

When the boot disk (qd0) has been replaced (and is still blank), or when the boot disk is defective and must be rebuilt, use the following procedure to boot system software from the distribution CD-ROM. This CD-ROM contains the operating system (DYNIX/ptx 4.4.x) and the CSM, VBAD, and QCIC software.


ATTENTION

The CSM board includes two separate functions: the CSM function and the HPSE (high-performance SCSI/Ethernet) function. Therefore, it requires two separate system software products to boot, CSM software and QCIC software. The HPSE section of the CSM board requires the QCIC software.


  1. Power-cycle the system and halt the booting process at the Level-A prompt (->) by typing any character within 5 seconds after the prompt appears.

  2. Load the distribution disk into the CD-ROM drive. (The drive must be connected to CSM channel 0. Drives connected to other SCSI ports are not bootable.)

  3. Set the following boot paths to point to the CD-ROM:

    -> bo QCICPath=qc(0x500,0)/usr/ssw/fw/qcic/opfw

    If a VBAD board is present in the system:

    -> bo VBADPath=qc(0x500,0)/usr/ssw/fw/ssm/lvlB

  4. Boot the CSM software.

    -> bs qc(0x500,0)/usr/ssw/fw/csm/lvlB

  5. When the Level-B prompt (--->) appears, refer to the DYNIX/ptx System Administration Guide. Use the procedures there to load and boot a new miniroot and operating system from the CD-ROM. This manual also describes how to rebuild the operating system and filesystem from backup tapes.


4.4 Booting from Tape When the Boot Disk Is Blank or Defective

When the boot disk (qd0) has been replaced (and is still blank), or when the boot disk is defective and must be rebuilt, use the following procedures to boot system software from a CSM system software tape and from QCIC-firmware PROMs.


ATTENTION

The CSM board includes two separate functions: the CSM function and the HPSE (high-performance SCSI/Ethernet) function. Therefore, it requires two separate system software products to boot, CSM software and QCIC software. The HPSE section of the CSM board requires the QCIC software.



4.4.1 Booting QCIC Software from the HPSE PROMs

With the CSM software distribution tape loaded into the tape drive, the CSM board cannot access the QCIC software that it needs to boot. Therefore, the system must read the QCIC software from another source, namely the HPSE PROMs on the CSM board. This operation will work only if the correct version of QCIC Level-B software (opfw256k.bin) has been flashed into the HPSE PROMs. (This situation does not apply to systems with a CD-ROM drive because both the CSM software and the QCIC software are supplied on the same CD-ROM.)

  1. Power-cycle the system and halt the booting process at the Level-A prompt (->) by typing any character within 5 seconds after the prompt appears.

  2. Verify or set the QCICFB flag to access the QCIC software from the HPSE PROMs on the CSM board with the following command:

    -> bo QCICFB=yes

  3. Insert the CSM SW tape into the tape drive.

  4. Boot the CSM software from tape:

    -> bs tq(0x400,1)

    If a VBAD board is installed in the system, console messages will appear stating that the VBAD software will not load. Ignore these messages because the VBAD software is not yet loaded onto the boot disk.


    ATTENTION

    If the system cannot access the QCIC software in the HPSE PROMs, ignore the error messages and allow the system to boot to Level-B. Then, terminate this procedure and follow the procedure in Section 4.4.2.


    If the QCIC software was accessible in the HPSE PROMs, the Level-B prompt (--->) will appear.

  5. When the Level-B prompt (--->) appears, verify that the QCIC boot path points to the normal location:

    ---> bo QCICPath=qd(0,2)ssw/fw/qcic/opfw

  6. With Level-B established, refer to the DYNIX/ptx System Administration Guide for procedures to load and boot a new miniroot and operating system from the CD-ROM. That manual also describes how to rebuild the operating system and filesystem from backup tapes.

  7. When the operating system is running, use the ptx/ADMIN menu system to load the VBAD software from its distribution medium onto the new boot disk. If you are not familiar with that procedure, follow the instructions in the SSM/VBAD System Software and Diagnostic Executive V4.9.2 Release Notes.


4.4.2 Loading QCIC Software into the HPSE PROMs

If the system could not read the QCIC software from the HPSE PROMs during the boot procedure in Section 4.4.1, follow this procedure to load (or reload) QCIC software into the HPSE PROMs:

  1. Remove the CSM software tape and insert the QCIC software tape into the tape drive.

  2. At the Level-B prompt, enter fprog.

  3. Select option 2 from the menu. When the prompt asks for a SLIC ID, enter 2. This identifies the HPSE PROMs on the CSM board that will receive the new QCIC software from tape.

  4. Select option 1 from the fprog menu to update the flash PROMs. When the prompt asks which PROM to program, enter 1 (Level-B). When the prompt asks for the source file, enter tq(0x400,3).

    After you select the file, the system displays the following:

    Verifying input data checksum
    Programming FPROM at slic address xx, 0x80000 bytes Using FPROM data file
    tq(0x400,3) Continue? (y/n)
    

    (The filename might be different on your system.)

    If you are satisfied with the selections, enter y to continue. If you want to make a change, enter n. The system will return you to the fprog menu, where you have the option to select a different file or change the SLIC ID.

    The programming operation can take up to one minute. While the PROMs are being programmed, the system will display the following:

    Programming zeros Erasing
    FPROM Programming .................................. Verifying FPROM checksum
    FPROM programming complete.
    
  5. Exit fprog by choosing option q from the fprog menu.

  6. Verify or set the QCICFB flag so that the system will boot the QCIC software from the HPSE PROMs:

    ---> bo QCICFB=yes

  7. At the Level-B prompt, enter the following command:

    ---> pup skip=y

  8. Then enter the following command to boot the QCIC software from the PROMs:

    ---> ctlr probe

  9. When the Level-B prompt (--->) appears, verify that the QCIC boot path points to the normal location:

    ---> bo QCICPath=qd(0,2)ssw/fw/qcic/opfw

  10. With Level-B established, refer to the DYNIX/ptx System Administration Guide, Vol. 2, Chapter 20. Use the procedures there to load and boot a new miniroot and operating system from the CD-ROM. That manual also describes how to rebuild the operating system and filesystem from backup tapes.

  11. When the operating system is running, use the ptx/ADMIN menu system to load the VBAD software from its distribution medium onto the new boot disk. If you are not familiar with that procedure, follow the instructions in the SSM/VBAD System Software and Diagnostic Executive V4.9.2 Release Notes.