DYNIX/ptx V4.4.8 and Layered Products Software Installation Release Notes: Upgrade SSM-Based Systems to V4.4.8


Appendix C
Upgrade SSM-Based Systems to V4.4.8

This appendix contains the following installation procedures for SSM-based systems upgrading to V4.4.8:


Requirements for SSM-Based Systems

DYNIX/ptx V4.4.8 is supported on SSM-based systems only for testing and development purposes.


Hardware Requirements

SSM-based systems typically require hardware upgrades before being updated from DYNIX/ptx V4.2 to DYNIX/ptx V4.4.8. The following hardware is required:

The following hardware is supported:

The following hardware is not supported:


Software Restrictions

The following software restrictions apply to SSM-based systems:


Additional Restrictions for S2000/7x0 Systems

S2000/7x0 machines have a single 1.2-GB SSM SCSI disk connected directly to the SSM. This disk must be used as both the boot disk and the root disk. The following configuration rules apply to this disk:

The maximum size of physical memory is limited to the size of the primary swap partition.


Upgrade From DYNIX/ptx V4.4.x to V4.4.8

If your system is currently running DYNIX/ptx V4.4 and you have a second wd disk, you can perform a delta upgrade to V4.4.8 as described in this section. Refer to the "Upgrade Checklist" in Chapter 1 for pre- and post-installation steps.


ATTENTION

If your system does not have a second local wd disk, you must first install DYNIX/ptx V4.2 on a qd disk and then upgrade to V4.4.8. See "Upgrade from DYNIX/ptx V4.2 to V4.4.8" later in this appendix.



Systems Not Running ptx/SVM

If your system is not running ptx/SVM, use the INIT ALT DISK DELTA procedure described in Chapter 7 to perform the upgrade.


Systems Running ptx/SVM V2.x


Prepare for the Installation

Complete the following steps to prepare your system for the installation:

  1. If your root volume is not mirrored, create a mirror on another partition. The partition must be on a local bus and be the same size as the original root plex. This partition will be used as the alternate disk partition during the software installation.

    To mirror the root volume, complete the following steps. In the following example, the mirror is created on partition wd3s0:

    # vxdisk -f init wd3s0
    # vxdg adddisk wd3s0
    # vxassist mirror ROOTVOL wd3s0

    The following message may appear; it can be ignored.

    vxbootsetup: NOTE: Root file system is not defined on a volume.
    

  2. Determine the location of the current root partition and the partition that will be used for the alternate disk installation. The alternate disk partition must be a mirror of the root volume. It cannot be the partition from which the system is currently booted.

    To determine the current root partition, enter the following command. The command returns the name of the disk from which the system is booted.

    # bfget -r
    root_dev=wd0s0:0:0

    To determine the partition to be used for the alternate disk installation, enter the following command.

    # vxprint -ht -g rootdg ROOTVOL

    Select the plex that is not associated with the boot disk.

  3. Disassociate the selected mirrored plex from the root volume. Before performing this step, ensure that your system is as idle as possible to avoid filesystem corruption on the alternate disk. (Later in this procedure, you will run fsck to verify the integrity of that filesystem.)

    # vxplex dis ROOTVOL-wd3s0
  4. Remove the plex and subdisk from the rootdg's records:

    # vxedit -r rm ROOTVOL-wd3s0
  5. Remove the disk media record from the rootdg.

    # vxdg rmdisk wd3s0

    ATTENTION

    If you should need to reboot the system after this point, you must boot on your current boot device, not on the new alternate disk. This may require changing your current boot flags to match those recorded earlier. (You cannot boot from the alternate disk until you have completed step 3 in the later section "Prepare to Reboot the System.")


  6. Check the integrity of the filesystem on the newly detached device:

    # fsck -y /dev/rdsk/wd3s0

Install Software

Perform the installation as described in the section, "Install Software with the INIT ALT DISK DELTA Procedure" in Chapter 7. Build the default kernel, but do not have ptx/INSTALL reboot the system.


Prepare to Reboot the System

Before rebooting the system, the device where the installation was performed must be returned to the rootdg:

  1. Reinitialize the private area for the new boot partition:

    # vxdisk -f init wd3s0
  2. Add the boot partition as a media record in the rootdg:

    # vxdg adddisk wd3s0
  3. Determine the bootpath of the partition containing the newly installed software:

    # dumpconf -b wd3s0
  4. Check the bootflags. In the output from the bootflags command, the n0= value should point to the bootpath determined in the previous step.

    # /etc/bootflags

    If the bootpath is not correct, use the following command to change it:

    # /etc/bootflags n0='bootpath'
  5. Shut down the operating system.

    #shutdown -i0 -g grace_period
  6. If you have new versions of the system firmware, install it as described in the corresponding release notes.

  7. Reboot the operating system. You will see a message such as the following when ptx/SVM starts:

    SVM starting in boot mode...
    Jul  9 17:21:50 vxvm:vxconfigd: Group rootdg: Duplicate virtual device number(s)
    :
    Jul  9 17:21:50 vxvm:vxconfigd:         Volume ROOTVOLremapped from 121,5 to 121
    ,4194302
    

Mirror the Original Root Partition to the Upgraded Root Volume

When you have completed the installation on the Symmetry system, you can reestablish the root mirror and then reboot on the original boot plex. Complete the following steps:

  1. Remove the old root volume, which is now known as ROOTVOL%1. (If you have multiple boot partitions, this can be a number other than %1, for example ROOTVOL%2.)

    1. Stop the volume:

      # vxvol stop ROOTVOL%1
    2. Remove all ROOTVOL%1 objects:

      # vxedit -r rm ROOTVOL%1
  2. Create the new half of the root mirror. (Wait for vxassist to complete before rebooting in step 4). The following example assumes sd0s0 was the original root partition; be sure to specify the correct name. (This name was returned by the bfget -r command in the earlier section "Prepare for the Installation.")

    # vxassist mirror ROOTVOL sd0s0

    If the following message appears, it can be ignored.

    vxbootsetup: NOTE: Root file system is not defined on a volume.
    

  3. Use ptx/ADMIN to set the bootflags to point to the original root disk. Be sure to specify the correct partition name.

    Use System Administration -> System Setup -> Set Boot Flags and Strings

  4. Reboot the system.


Break the Mirror If Desired

It is strongly recommended that you mirror the root volume at all times. However, if the root volume was previously unmirrored and you want to continue with that method of operation, enter the following commands to break the mirror. In the commands, plex is the plex associated with the partition that is not being used to boot the system. In the third command, specify the media record associated with that partition.

# vxplex -o norestr dis plex
# vxedit -r rm plex
# vxdg rmdisk media_record

Upgrade from DYNIX/ptx V4.2 to V4.4.8


ATTENTION

You must use this procedure if your system is currently running a version of DYNIX/ptx earlier than V4.4, or you have only one wd disk.


To upgrade an SSM-based system from DYNIX/ptx V4.2 to V4.4.8, you will need the following release notes in addition to this document:


ATTENTION

Be sure to retain the DYNIX/ptx V4.4.8, SSM/VBAD, and QCIC distribution software. You may need to use this software for disaster recovery.


DYNIX/ptx V4.4.8 must be installed on a disk connected directly to the SSM. This disk must be 1.2 GB or larger (typically an HP®97560 disk). If you need to replace the wd disk that will be used for V4.4.6 with a larger disk, do not perform the disk replacement until you are able to boot the SSM and QCIC firmware from another location.

Use the following procedure to update to V4.4.8:

  1. Install DYNIX/ptx V4.2.x on a qd disk. The firmware partition (/usr/ssw) can remain on the wd disk. Refer to the DYNIX/ptx V4.2.x Release Notes.

  2. If you will be replacing the wd disk, move any other filesystems on that disk to another location.

  3. Boot DYNIX/ptx V4.2.x.

  4. Install SSM V4.9.2. See the SSM release notes.

  5. Install QCIC V3.4.1. See the QCIC release notes.

  6. Shut down the system to the lvl-B prompt.

  7. Update the lvl-A and lvl-B QCIC flash PROMs with the fprog command as described in the QCIC release notes.

  8. Set QCICPath to boot the lvl-B firmware from flash.

    ---> bo QCICPath='wd(0,0)boot from flash'
  9. Update the SSM Flash PROMs with the fprog command as described in the SSM release notes.

  10. Change lvlBPath to point to the SSM file on tape. (This will help prove that you can boot without wd0.)

    For S2000/2x0 systems:

    ---> bs lvlBPath=tm(56,1)

    For S2000/4x0 and S2000/7x0 systems:

    ---> bs lvlBPath=tm(56,3)
  11. Boot a new lvl-B with the zap command and stop the boot when a message appears stating that five seconds remain until the lvl-B boot.

  12. Insert the SSM tape into the 5-1/4" tape drive connected to the SSM.

  13. Boot the SSM from tape. (This step verifies that you can boot without wd0.)

    -> bs
  14. If you need to replace the wd drive with a larger drive, shut down the system and replace the drive.

  15. If you have not already done so, install the CD-ROM/tape dual carrier:

  16. If the tape drive was replaced, insert the SSM tape into the new tape drive.

  17. Power on the system and boot to lvl-B.

  18. Insert the DYNIX/ptx V4.2 distribution tape into the tape drive and set the loader path to point to the tape:

    ---> bh loaderPath=tm(56,1)
  19. Boot the operating system:

    ---> bh
  20. Create the devices /dev/rSA/cdrom0 and /dev/rSA/cdrom0n:

    # cd /dev
    # ./MAKEDEV sysadm
  21. Insert the DYNIX/ptx V4.4.8 distribution CD-ROM into the CD-ROM drive.

  22. Copy the default root VTOC for the HP97560 disk from the CD-ROM filesystem.

    # devbuild vtoc /dev/rSA/cdrom0
    # mount -r /dev/rSA/cdrom0 /mnt
    # cp /mnt/etc/vtoc/hp97560.scan /etc/vtoc
    # umount /dev/rSA/cdrom0
  23. On S2000/7x0 systems, modify the VTOC to provide a larger primary swap partition. See the next section, "Modify the hp97560.scan VTOC."

    On S2000/2x0 and S2000/4x0 systems, the default hp97560.scan VTOC can be used with no modifications.

  24. Install the VTOC on the disk that will be used for the V4.4.8 installation.

    # mkvtoc -f -g -s /etc/vtoc/<vtoc_name> wd0 hpc97560
  25. Perform the update to DYNIX/ptx V4.4.8. Use the INIT ALT DISK DELTA procedure described in Chapter 7. When asked whether you want to install a VTOC on the root disk, answer no. When asked for the swap partition, specify wd0s1.

    You must reinstall the SSM and QCIC software either during the INIT ALT DISK DELTA procedure or immediately afterward (using a ROOT installation).

    After the SSM software is reinstalled, change the lvlBPath to point to the firmware file on disk. Until you do this, you must have the SSM tape in the tape drive to boot the SSM to lvl-B. After the QCIC software is installed, you can also set the QCICPath to boot from disk; however, this step is not required.

    If you have additional wd disks and want to install the firmware in a separate partition, do not install the firmware during the INIT ALT DISK DELTA procedure. After that installation is complete, create and mount a /usr/ssw filesystem and then use the ROOT procedure to install the firmware.


Modify the hp97560.scan VTOC

On S2000/7x0 systems, you will need to modify the default hp97560.scan VTOC to provide a larger primary swap partition. The default partition layout is as follows:

* Partition Type  Start Sector  Size in Sectors  Block Sz Frag Sz
0 1 5472 2049264 8192 1024
1 1 2054736 360896 8192 1024
8 8 2415632 8192 8192 1024
9 9 2423824 200000 8192 1024
10 5 2623824 20520 8192 1024
12 4 32 5440 0 0
13 3 2644344 2736 0 0
14 2 0 16 0 0
15 3 16 16 0 0

Combine partitions 1, 8, and part of partition 9 to create a larger partition 1, which will be used for primary swap. The new partition should contain about 280 MB, which is enough to boot with 160 MB of memory. (If your system has 256 MB of memory, the primary swap partition must contain 186 MB; you will need to take the extra space from the root partition.)

Also create a new partition 8 containing 8192 blocks. This partition must be of type 8 and is used by ptx/SVM.

Following is the modified partition layout:

* Partition Type  Start Sector  Size in Sectors  Block Sz Frag Sz
0 1 5472 2049264 8192 1024
1 1 2054736 560896 8192 1024
8 8 2615632 8192 8192 1024
10 5 2623824 20520 8192 1024
12 4 32 5440 0 0
13 3 2644344 2736 0 0
14 2 0 16 0 0
15 3 16 16 0 0

For more information about modifying VTOCs, see the DYNIX/ptx System Administration Guide.


Systems With More Than 256 MB of Physical Memory

If your system has more than 256 MB of physical memory, you may need to reduce the size of the root partition and increase the size of the swap partition.

The minimum size of the root partition depends on the products you will install. For example, an install of the following products from the V4.4.8 CD-ROM consumes 560 MB of the 1-GB root filesystem:

DYNIX/ptx

ptx/LAN

SSM, QCIC

ptx/NFS

Encryption

ptx/SVM

Public Software

ptx/SYNC

ptx/BaseComms

ptx/TCP/IP

ptx/EFS

ptx/XWM

ptx/INSTALL


If your system requires more swap space and you need assistance with modifying the hp97560.scan VTOC, contact your customer service representative.


V4.4.8 Installation Problems


Automatic Bootflag Generation Fails

When you update to V4.4.8, the system may not be able to update the bootflags automatically. You will see error messages such as the following:

Error while generating bootflags.
Bootflags update NOT successful.

If you see these messages, you will need to update the bootflags manually. To do this, complete the following steps:

  1. Use Ctrl-P to go to Level B of the monitor.

  2. Run the following command to see the current bootflag settings:

    --> pr bh
  3. Enter the correct bootstrings for OsPath and auxPath. (The tmpPath bootstring contains the correct value for OsPath.)

    The following example is for a system where the bootflags have been set correctly.

    ---> pr bh
    osPath = 0 slic(28,0)scsi(0,0)disk(0,0,0)
    autoBoot = 0
    tmpPath = 0 slic(28,0)scsi(0,0)disk(0,0,0)
    auxPath = 88 slic(28)scsi()disk()dump -f /etc/dumplist
    autoDump = 0
    loaderPath = wd(0,0)/usr/ssw/boot
    errPath = 0 wd(0,10)

ptx/SLPT Is Not Completely Deinstalled

The ptx/SLPT layered product is deinstalled during the update to V4.4.8; however, ptx/ADMIN still lists ptx/SPLT as being installed. Also, /etc/versionlog does not specify that the product has been deinstalled.

Do not attempt to deinstall ptx/SLPT again; the product has already been deinstalled. The ptx/ADMIN listing can be ignored.