Chapter 7
Upgrade Symmetry Systems Not Running ptx/SVM

This chapter describes how to upgrade DYNIX/ptx and/or layered products on systems that are not running ptx/SVM. Choose the appropriate installation scenario:

When you use these procedures, have ptx/INSTALL build the default kernel, but do not reboot.


INIT ALT DISK DELTA Installation

The INIT ALT DISK DELTA procedure updates the base operating system and layered products on an alternate disk. It installs a VTOC on the alternate disk (if necessary), copies an image of the current root filesystem (and /usr if it is a separate filesystem) to the alternate disk, and then updates the specified products on that disk.


ATTENTION

The INIT ALT DISK DELTA procedure will place an image of root and /usr on the same partition on the alternate disk. Although root and /usr may currently be on different partitions, the INIT ALT DISK DELTA copy procedure will create a single root filesystem containing your current root and /usr filesystems. When the installation is complete, there will no longer be a separate /usr filesystem.


This procedure is supported only for the root and /usr filesystems; it cannot create an image of other filesystems. Products that install software in other filesystems cannot use the INIT ALT DISK DELTA procedure. See the section "INIT ALT DISK DELTA Installation Type" in Chapter 3 for a list of affected products.


Install Software With the INIT ALT DISK DELTA Procedure


ATTENTION

The following products cannot be installed with the ALT DISK DELTA procedure: ptx/SNA, ptx/SYNC, ptx/X.25, SequentLINK. Use the ROOT procedure to install these products after updating the base operating system.



ATTENTION

Be sure to delete any unsupported products before starting the installation. See Table 2-3, "Software to Deinstall."


To install software packages, use the following procedure. You must be root to perform the software installation.

  1. Select an alternate disk. (Review "Alternate Disk Requirements" in Chapter 3.)

  2. Insert the distribution CD-ROM into the CD-ROM drive.

  3. Issue the menu command to start ptx/ADMIN; then go to the Software Management Menu.

    Use System Administration -> Software Management


    ATTENTION

    If the menu system does not display properly, suspend or leave the menu system and type the following command: stty -tabs


    If you want to check the contents of the CD-ROM, select the "List Software Packages Available on Installation Distribution" option.

  4. If you are updating from DYNIX/ptx V4.4.x, select the Install Software Package option and then go to step 4.

    If you are updating from a version earlier than V4.4.0, you must load ptx/INSTALL on your system:

    1. Run the preview phase for ptx/INSTALL.

      For the installation procedure, the name of the ptx/INSTALL software is install. The software Bill of Materials (BOM) and other installation files are loaded into the /usr/options/install directory. The preview log is named /usr/options/install/preview.log.

    2. Run the install phase. This phase can be run in multiuser mode.

    3. After ptx/INSTALL is loaded on your system, go back to the System Administration menu; then reenter the Software Management menu. This menu will now contain a new option, Upgrade Base OS to v4.4/v4.5. Select this option to continue the installation.

      If the installation is halted for any reason, you will need to select the Upgrade Base OS to v4.4/v4.5 option again to restart the installation.

      Use System Administration ->Software Management -> Upgrade Base OS to v4.4/v4.5

  5. Specify the installation source, which can be either CD-ROM, nfs, or directory.

                   Installation Source Type
      
     Enter installation source type          ___________     
                             
    

  6. Specify the location of the installation source on the screen that appears next:

  7. On the Installation Type window, select INIT ALT DISK DELTA.

                          Installation Type 
    Installation Type    Description
    ________________________________________________________________________
    ROOT                 Install on current root, /usr partitions          #
    ALT DISK DELTA       Install on mounted alternate root partition
    INIT ALT DISK DELTA  Make copies of current partitions and install on it
    SCRATCH              Initial install on alternate disk                 #  
               
    

  8. Specify information about the alternate disk on the Disk Locations form. The alternate disk must be a local disk attached directly to the CSM. At the prompt "Enter alternate root disk and partition," specify a device in the form /dev/dsk/sd0s0. Similarly, for the prompt "Enter alternate primary swap disk and partition," specify a device such as /dev/dsk/sd0s1.

                    Disk Locations
     
    Enter alternate root disk and partition        ____
     
    Enter filesystem type                          ____
    Warning: efs requires ptx/EFS,
    a licensed product, be installed or
    selected for installation on new root
     
    Should the filesystems support ACLs?           _
    (Y/N)   
    Install standard vtoc on disk? (Y/N)           _
    (Answer N only if vtoc already exists
     on device)
     
    Enter alternate primary swap disk and          ______
    partition             
    

    If you chose to have a VTOC installed on the alternate disk, ptx/INSTALL will attempt to determine the disk type for that disk. If it is unable to locate this information, you will be asked to specify the disk type on the following form. Use SELECT to see a list of valid disk types.

                        Disk Type
     
    Enter type of disk                     _________ 
    

  9. At the next screen, answer N.

            C2-Certifiable Product Installation
    
    Install only those products which        N
    are C2-Certifiable? (Y/N)
    Enter 'Y' to install only products
    which are C2-Certifiable
    

    Do not answer Y; DYNIX/ptx V4.4.10 has not been certified for C2-level security.

  10. Select the software packages to be installed from the Select Software Packages window. You can select multiple packages. The packages can be both new installations and updates to existing products. Following is an example of this window.

                               
                       Select Software Packages 
           Part Number   Name       Description                  Version     
    ________________________________________________________________
      1003-xxxxx-xx base       DYNIX/ptx(R) Base            v4.4.10 #
      1003-xxxxx-xx encryption DYNIX/ptx(R) Encryption      V4.4.10 
    N 1003-xxxxx-xx nfs        ptx/NFS                      v4.6.5
    


    ATTENTION

    If you are not already running the latest versions of the CSM and QCIC software, be sure to install them on the system. If you do not do this, you will need to boot the CSM and QCIC software from the distribution CD-ROM when you need to boot the operating system.



    ATTENTION

    Do not install the Fibre Channel Switch, Bridge, or Host Adapter software. This software is used only on IBM xSeries 430 and NUMA-Q 2000 systems.


    Certain software packages require that you enter a license password into the system nodelock file before the package can be installed. If the license password has already been entered, the letter L will precede the entry for that package in the Select Software Packages window. If the license password has not been entered, the letter N will appear. License passwords are not required for packages that do not specify one of these letters.


    ATTENTION

    If you selected several products that require licenses, it might take a few minutes for the next installation screen to appear.


  11. If you have selected a software package that requires a license password but you have not yet entered the password into the system nodelock file, a window listing the name of the product will be displayed. Highlight the line containing the product name and press F1 to enter the license for that product. To deselect the product, enter d.

    If you choose to enter the license password, the following form will be displayed. You must enter the license password, the expiration date, and the license checksum. The other values will be filled in for you. (The license information for the products you have purchased is located in the license folder shipped with your software.)

                  Add Installation License
     
    Enter the product name               ________
     
    Enter the product version            ________
     
    Enter the node ID                    ________
     
    Enter the vendor ID                  ________
     
    Enter the license password           ________
     
    Enter the expiration date            ________
     
    Enter the license checksum           ________      
    

    The license entries you specify are added to the system nodelock file, /var/netls/nodelock.

  12. ptx/INSTALL now determines whether the products currently on the system are compatible with the products being installed. When a product requires that another product be installed, ptx/INSTALL also verifies that the required product has been selected for installation. If certain products are not compatible or if required products have not been selected, the following form will appear. You can either reselect products or abort the installation.

     
                     Compatibility Error
     
    View compatibility errors? (Y/N)               _
     
    Enter 'Y' to display the product
    incompatibilities identified.  You can
    then  reselect products to install
    and continue the installation.
     
    Answer 'N' to abort installation
    

    ptx/INSTALL will now create the temporary directories needed for the installation.

  13. ptx/INSTALL requires additional information to install certain layered products. At this point, you will be asked for that information. For example, a product might include optional components; you will need to specify whether you want to install those components. Most of these screens are self-explanatory.

    If you are installing ptx/LICENSE, refer to the ptx/LICENSE Release Notes for a description of the installation and configuration screens that appear. In particular, do not configure ptx/LICENSE if ptx/TCP/IP is not already configured for networking on your system.

  14. ptx/INSTALL now verifies that there is adequate filesystem space to install the selected products. If there is not enough space, ptx/INSTALL interrupts the installation and displays the following form. Enter Y at the prompt to review the problems found.

                        Disk Space Error
     
    View info on disk space insufficiencies?         ___
    Enter 'Y' to display products whose disk
    space requirements will not be met.
    Enter 'N' to abort the installation.
     
    You may restart the installation once
    the disk space requirements for all
    selected products have been resolved.
    

    When adequate disk space is available, you can resume the installation by selecting the Install Software Package option (or the Upgrade Base OS to v4.4/v4.5 option) from the Software Management menu.


    ATTENTION

    If the alternate disk partition is the same size as the current root partition, ptx/INSTALL may incorrectly report that there is not enough room to do the install. If this message occurs, you will need to do an ALT DISK DELTA install and copy the image to the alternate disk partition manually.


  15. ptx/INSTALL now creates a preview log for each product to be installed. The preview log specifies whether file conflicts exist for the product. File conflicts can occur when the version of a file currently on the system differs from the original file, from the version of the file on the CD-ROM, or from both. You will need to resolve certain file conflicts manually. You can either halt the installation and resolve those file conflicts now, or continue with the installation and resolve the conflicts after the software is installed.

                      Conflict File Resolution
     
    Resolve files in conflict now? (Y/N)        __
    Enter 'Y' to preload conflict files and 
    temporarily exit to view preview logs
    and resolve files in conflict.  
    Enter 'N' to continue with installation,
    and resolve files in conflict after the
    installation is completed.
    

    Appendix B lists file conflicts that may occur for DYNIX/ptx, ptx/TCP/IP, and ptx/RAID. Be sure to review this information to help you determine whether you want to resolve file conflicts now or after the installation is complete.

    To resolve any conflicts after the installation is complete, answer N on the form. The installation will continue as specified in the preview logs for the selected products and the old files will be moved to the <product_name>/oldfiles directories.

    To resolve the conflicts now, answer Y on the form. The files in conflict will then be preloaded and the installation will exit. To locate file conflicts, use the View/Edit Preview Logs menu option from the Software Management menu to examine the preview logs. For details about the preview logs and resolving conflicts, refer to Appendix B.


    ATTENTION

    After resolving the conflicts, you can resume the installation by selecting the Install Software Package option (or the Upgrade Base OS to v4.4/v4.5 option) from the Software Management menu.


  16. If conflicts were found, the following form will specify where the files in conflict will be preloaded. You can change the locations for preloading new conflict files and saving the currently installed version (the old version) of conflict files.

    The default locations for new and old versions of conflict files are /usr/options/<product>/newfiles.<installation_date-time> and /usr/options/<product>/oldfiles.<installation_date-time>.

    The following form will specify the parent directory as /tmp/<temporary /usr/options directory>. Because the alternate disk has not yet been initialized, this temporary directory contains the/usr/options directory for the alternate disk. Later in the installation, the files will be moved to the appropriate /usr/options/<product> directory on the alternate disk.

                  Conflict File Parent Directories
     
    Enter the parent directory for           ____________
    preloading new versions of files in
    conflict
    (For each product selected, a
    subdirectory of the form 'PRODUCT_NAME/
    newfiles.<installation_date_time>' will
    be created)
     
    Enter parent directory for saving        ____________
    old versions of files in conflict
    (For each product selected, a
    subdirectory of the form 'PRODUCT_NAME/
    oldfiles.<installation_date_time>' will
    be created)                                              
       
    

  17. ptx/INSTALL now determines whether the kernel needs to be recompiled after the installation is complete. Typically, this is needed only when the products to be installed contain kernel components. You can override the value specified on the form.

    We recommend that you answer Y on the form. ptx/INSTALL will then build a default kernel that includes the layered products you have installed. This kernel is needed to boot the operating system properly.

    The default kernel will not include any local kernel modifications that you have made. After booting the system, you can build your custom kernel and then reboot with that kernel.

     Configure and compile a kernel with default parameters
      
     Configure and compile a default kernel      ____
     following installation? (Y/N)
    

    If you chose to have ptx/INSTALL compile the default kernel, the following form appears. The name you specify at the first prompt cannot be std, mfg, or mod.

           Configure a kernel with default parameters
     
    Enter a unique name to associate with       default
    this kernel and all its associated
    configuration files
     
    Choose a kernel environment type            ___
           T for TIMESHARE
           P for PARALLEL
           C for COMMERCIAL
     
    Configure for audit? (Y/N)                  ___
     
    Enter a short description of this kernel    _______
                                             
    The starting machine type                   _______
     
    The starting architecture type              _______
     
    The starting configuration type             _______
    

  18. If the following situation applies to your installation, the Crosstools Source Type form shown next will appear: you have installed the base operating system on an alternate disk; you are now installing a layered product from another CD-ROM on the alternate disk; the layered product includes kernel components but the CD-ROM it is on does not include the V4.4.10 kernel compilation tools; you specified that the default kernel should be compiled.

                      Crosstools Source Type
     
    Enter crosstools source type                      ______
    Supported types: CD-ROM, nfs, directory, or NONE
    (crosstools source only)       
    

    Because the tools needed to compile the V4.4.10 kernel are not available, the form allows you to specify an alternate source for the tools. If you have another CD-ROM drive, insert the CD-ROM containing DYNIX/ptx V4.4.10 into that drive and enter CD-ROM as the crosstools source type on the form. You will then be asked to specify the name of the CD-ROM device, such as cd1.

    If you do not have another CD-ROM drive, use Cancel to exit the installation; then start the installation again. The "Configure and compile a kernel with default parameters" form will be displayed. Enter N at the prompt and compile the default kernel manually when the installation is complete.

  19. Specify whether you want to rebuild the man pages database and reboot the operating system on the installation disk after the software installation is complete.

    Rebuilding the man pages takes several minutes. You can also build the man pages at a later time using one of the methods described in theptx/INSTALL Software Installation Guide.


    ATTENTION

    Do not have ptx/INSTALL reboot the kernel.


                    Installation Options
      
     Rebuild manpages following installation?(Y/N)    __
      
     Reboot on installation disk after                __
     installation? (Y/N)
      
     This is the last screen for installation
     Entering "Run" from this screen will
     start the installation of files for all
     selected products.
    

ptx/INSTALL will now perform the software installation.


ATTENTION

The installation procedure sets both the permanent and the temporary bootpaths to point to the new root disk. If you installed software on an alternate disk, the ptx/ADMIN Set Boot Strings and Flags menu option will not report the updated permanent bootpath until after the system is rebooted. To check the updated bootflags, use the /etc/bootflags command.



CSM Installation Problem

When the CSM software is installed, you may see a message stating that /usr/ssw is not mounted. The message can incorrectly appear even though /usr/ssw is mounted. Also, the complete message is not displayed.

The message is as follows:

ERROR: 

A filesystem on a CSM SCSI channel 0 qd or sd disk in the address
range [0..7] must be mounted on /usr/ssw before this software
can be installed. Consult the CSM SW Installation Guide.

It is recommended that the installation be aborted
at this point. However you can continue if you
have a special reason to.

To abort the installation, press Return. If you are sure that /usr/ssw is mounted, enter N. The remainder of the message will then be displayed and the installation will continue:

Abort installation of CSM firmware? [yes] Checking /usr/ssw

The incomplete message will be repeated later in the installation. Answer N again to finish the installation.


Removing the Distribution CD (Optional)

If you want to remove the distribution CD from the drive before booting the system, you can. However, the system will boot properly if the distribution CD is left in the drive during the boot operation.

Previously, the documentation instructed you to devdestroy the cd device after the software was installed. This is no longer necessary as ptx/INSTALL now executes any devdestory action that may be required as part of the installation.


ALT DISK DELTA Installation

The ALT DISK DELTA installation procedure can be used in three different ways. Choose the method that is appropriate for your site.


Boot From the Distribution CD-ROM

If ptx/EFS is not currently installed on your system and you want to make the root filesystem an EFS filesystem, you must boot from the CD-ROM and create the filesystem image on the alternate disk. Complete the following steps:

  1. Run the following command to provide your current dumpconf output for installation process:

    $ /etc/dumpconf -ds > /var/dumpconf.out
  2. Take the system to run-level 0:

    # shutdown -gseconds -y -i0
  3. Insert the distribution CD-ROM into the system CD-ROM drive.

  4. Set the loader path to point to the boot program on the CD-ROM device. In the following example, the CD-ROM device is at SCSI ID 5.

    ---> bh loaderPath=qc(0x500,0)boot
  5. Set the QCICPatch to point to the QCIC software on the CD.

    ---> bo QCICPath=qc(0x500,0)usr/ssw/fw/qcic/opfw
  6. Set the lvlBPath to point to the Level-B software on the CD-ROM.

    ---> bs lvlBPath=qc(0x500,0)usr/ssw/fw/csm/lvlB
  7. Boot the operating system from the CD-ROM. In the following example, the CD-ROM device is at SCSI ID 5 and the primary swap space is onsd0s1.

    ---> bh slic(2)scsi(5)disk(0)sb8000_unix -s slic(2)scsi(0)disk(1) -I -L

    In the command, the location of the root disk and the primary swap partition (the -s option) must be indicated with physical path specifiers because the naming database is not available on the CD-ROM. The -I option creates a naming database. The -L option labels the primary swap partition and is needed only if this partition has not been previously used for swap. (For more information about the syntax, see Appendix A.)


    ATTENTION

    During the boot, you may see messages that the system cannot read or write to certain files. These messages can be ignored.


    When the operating system is booted, only the root device (the CD-ROM device in this case) and the swap device will have permanent names in the naming database. All other devices will have temporary names. During the software installation, the devctl -N command will be run automatically to give the devices default permanent names and add them to the naming database. (For details about the naming database, refer to the DYNIX/ptx System Configuration and Performance Guide.)

  8. The temporary name that was assigned to the original root disk might not match its original name. To restore the original name, run one of the following commands.

  9. If you will be installing on an alternate disk, use the procedure "Create an Image with a Different Filesystem Type," later in this chapter, to create EFS filesystems on the alternate disk partition and then copy the current filesystems to that partition.

  10. If you will be installing on the current root filesystem, build a VTOC on that disk and mount the root filesystem. (In the following example, the root filesystem is sd0s0):

    # devbuild vtoc /dev/rdsk/sd0
    # mount /dev/dsk/sd0s0 /mnt
  11. If you will be installing ptx/SYNC, set the HOME variable to /tmp and export it:

    # HOME=/tmp
    # export HOME

  12. Go to the section "Install Software With the ALT DISK DELTA Procedure."


Create Filesystem Images on the Alternate Disk

Before starting the installation on an alternate disk , you must create an image of the root filesystem (and any other filesystems in which software will be installed) on the alternate disk. Although the following examples copy the current root filesystem, the image you create does not need to match the current root filesystem.

Also, the image can have the same filesystem type (for example, UFS or EFS) as the original filesystem, or you can change the filesystem type.

Also, you can create an image with the same filesystem type (for example, UFS or EFS) as the original filesystem, or you can create an image with a different filesystem type.


Create an Image With the Same Filesystem Type

This procedure describes how to create an image that will have the same filesystem type as the original root filesystem. In the following example, the original root disk is sd0 and the alternate disk is sd1.

The examples in the procedure create a UFS filesystem; however, you can use the same procedure to create an EFS filesystem (check the newfs(1M) man page for the appropriate flags.)


ATTENTION

Be sure to use dump/restore to copy the filesystem image. Other utilities such as rdcp and dd are not aware of filesystem formats and cannot be guaranteed to copy a mounted read/write filesystem correctly.



ATTENTION

Do not boot from the copied image on the alternate disk partition. The system must be booted from the original root partition and the software must be installed on the alternate disk partition.


To create the image, complete the following steps:

  1. Ensure that the VTOC on the alternate disk has the same (or larger) partition sizes as the original root disk. If necessary, install an appropriate VTOC on the disk. (You can use the prtvtoc command to display the VTOCs). The commands have this syntax.

    # /etc/mkvtoc -g -s vtoc_name disk_name disk_type
    # /etc/devbuild vtoc /dev/rdsk/disk_name

    The following example installs a custom root VTOC on disk sd1:

    # /etc/mkvtoc -g -s /etc/vtoc/root.vtoc sd1 hp97560
    # /etc/devbuild vtoc /dev/rdsk/sd1
  2. Create a filesystem for root on the alternate disk (sd1s0 in the following example):

    # /etc/newfs /dev/rdsk/sd1s0 

    If /usr is a separate filesystem, create a filesystem for it on the alternate disk:

    # /etc/newfs /dev/rdsk/sd1s2 

    ATTENTION

    The root filesystem (and /usr if it is a separate filesystem) on the alternate disk cannot be under ptx/SVM control. They must be a regular filesystems.


  3. Copy the current root filesystem to the alternate disk. (The dump command is shown on two lines for readability). Be sure to specify the dump flags shown here. The commands have this syntax:

    # /etc/mount /dev/dsk/alt_root_partition mountpoint
    # sync
    # /etc/dump 0bdsf 32 54000 10000 - /dev/rdsk/current_root_partition
    | (cd alt_root_mountpoint; /etc/restore xbf 32 -)

    The following example mounts the alternate root partition sd1s0 as /mnt and copies the current root filesystem to that partition.

    # /etc/mount /dev/dsk/sd1s0 /mnt
    # sync
    # /etc/dump 0bdsf 32 54000 10000 - /dev/rdsk/sd0s0 | (cd /mnt;
    /etc/restore xbf 32 -)

    If the current root partition is under ptx/SVM control, use /dev/vx/rdsk/ROOTVOL instead of/dev/rdsk to specify the current root partition.

    When the dump is complete, the following prompt appears:

    set owner/mode for '.'? [yn]
    

    Enter y at the prompt.

  4. If /usr is a separate filesystem, copy it to the alternate disk:

    # /etc/mount /dev/dsk/sd1s2 /mnt/usr
    # sync
    # /etc/dump 0bdsf 32 54000 10000 - /dev/rdsk/sd0s2 | (cd /mnt/usr;
    /etc/restore xbf 32 -)

    If the current /usr partition is under ptx/SVM control, use the ptx/SVM syntax instead of /dev/rdsk to specify the current /usr partition.

    When the dump is complete, the following prompt appears:

    set owner/mode for '.'? [yn]
    

    Enter y at the prompt.

  5. Unmount the alternate root and /usr partitions (/mnt and /mnt/usr in this example):

    # /etc/umount /mnt/usr
    # /etc/umount /mnt
  6. Run labelit on the root filesystem (and /usr if it is a separate filesystem) on the alternate disk:

    # /etc/labelit -F filesystem_type /dev/rdsk/alt_root_partition label 
    alt_root_partition

    The filesystem_type can be either ufs or efs.

    The following example assigns the label root to the alternate root partition and the label usr to the alternate usr partition.

    # /etc/labelit -F ufs /dev/rdsk/sd1s0 root sd1s0
    # /etc/labelit -F ufs /dev/rdsk/sd1s2 usr sd1s2
  7. Run fsck on the root filesystem (and on /usr if it is a separate filesystem on the alternate disk). Be sure to specify the appropriate filesystem type (ufs or efs). In the following example the filesystems on the alternate disk (sd1) are ufs.

    # /etc/fsck -F ufs /dev/rdsk/sd1s0  
    # /etc/fsck -F ufs /dev/rdsk/sd1s2

    If fsck should fail, use the -o full option offsck to recover.

  8. Mount the root filesystem (and /usr if it is a separate filesystem) on the alternate disk:

    # /etc/mount /dev/dsk/sd1s0 /mnt
    # /etc/mount /dev/dsk/sd1s2 /mnt/usr
  9. Issue a df command to confirm that the root filesystem is mounted. If /usr is a separate filesystem, also verify that it is mounted.

    # df
    / (/dev/dsk/sd0s0 ): 38760 blocks 25107 i-nodes
    /mnt (/dev/dsk/sd1s0 ): 38812 blocks 25110 i-nodes

    You now have an image of the current root filesystem (and /usr if it is a separate filesystem) on the alternate disk.


Create an Image With a Different Filesystem Type

This procedure describes how to create an image that will have a different filesystem type from the original root filesystem (and /usr if it is a separate filesystem). In the example, the original root disk is sd0 and the alternate disk is sd1.

The examples in the procedure are to create an EFS filesystem; however, you can use the same procedure to create a UFS filesystem.


ATTENTION

Be sure to use dump/restore to copy the filesystem image. Other utilities such as rdcp and dd are not aware of filesystem formats and cannot be guaranteed to copy a mounted read/write filesystem correctly.



ATTENTION

Do not boot from the copied image on the alternate disk partition. This partition should be used only to install the new software.



ATTENTION

To create an EFS filesystem, ptx/EFS must be currently installed on your system or you must have booted the operating system from the distribution CD-ROM.


To create the image, complete the following steps:

  1. Ensure that the VTOC on the alternate disk has the same partition sizes as the original root disk. If necessary, install the VTOC on the disk. (You can use the prtvtoc command to display the VTOCs.)

    The following example installs a custom root VTOC on disk qd1:

    # /etc/mkvtoc -g -s /etc/vtoc/root.vtoc sd1 hp97560
    # /etc/devbuild vtoc /dev/rdsk/sd1
  2. Create a filesystem for root on the alternate disk. Use the appropriate newfs flag to create either an EFS or UFS filesystem. The following example creates an EFS filesystem.


    ATTENTION

    The root filesystem (and usr if it is a separate filesystem) on the alternate disk cannot be under SVM control. They must be regular filesystems.


    # /etc/newfs -F efs /dev/rdsk/sd1s0 

    If /usr is a separate filesystem, create a filesystem for it on the alternate disk:

    # /etc/newfs -F efs /dev/rdsk/sd1s2 
  3. Copy the current root filesystem to the alternate disk, creating an EFS filesystem. Be sure to specify the dump command flags shown here. (The command is shown on two lines for readability.) The commands have this syntax:

    # /etc/mount -F efs /dev/dsk/alt_root_partition mountpoint
    # sync
    # /etc/dump 0bdsf 32 54000 10000 - /dev/rdsk/current_root_partition
    | (cd alt_root_mountpoint; /etc/restore xbf 32 -)

    The following example mounts the alternate root partition sd1s0 as /mnt and copies the current root filesystem to that partition.

    # /etc/mount -F efs /dev/dsk/sd1s0 /mnt
    # sync
    # /etc/dump 0bdsf 32 54000 10000 - /dev/rdsk/sd0s0 | (cd /mnt;
    /etc/restore xbf 32 -)

    If the current root partition is under ptx/SVM control, use /dev/vx/rdsk/ROOTVOL instead of /dev/rdsk to specify the partition.

    When the dump is complete, the following prompt appears:

    set owner/mode for '.'? [yn]
    

    Enter y at the prompt.

  4. If /usr is a separate filesystem, copy it to the alternate disk. In the following example, the filesystem on the alternate disk will be an EFS filesystem.

    # /etc/mount -F efs /dev/dsk/sd1s2 /mnt/usr
    # sync
    # /etc/dump 0bdsf 32 54000 10000 - /dev/rdsk/sd0s2 | (cd /mnt/usr;
    /etc/restore xbf 32 -)

    If the current /usr partition is under ptx/SVM control, use the ptx/SVM syntax instead of /dev/rdsk to specify the current /usr partition.

    When the dump is complete, the following prompt appears:

    set owner/mode for '.'? [yn]
    

    Enter y at the prompt.

  5. Unmount /mnt (and /mnt/usr if it exists):

    # /etc/umount /mnt/usr
    # /etc/umount /mnt
  6. Run labelit on the root filesystem (and /usr if it is a separate filesystem) on the alternate disk:

    # /etc/labelit -F filesystem_type /dev/rdsk/sd1s0 root sd1s0
    # /etc/labelit -F filesystem_type /dev/rdsk/sd1s2 usr sd1s2
  7. Run fsck on the root filesystem (and /usr if it is a separate filesystem) on the alternate disk:

    # /etc/fsck -F filesystem_type /dev/rdsk/sd1s0  
    # /etc/fsck -F filesystem_type /dev/rdsk/sd1s2

    If fsck should fail, use the -o full option to fsck to recover.

  8. Mount the root filesystem (and /usr if it is a separate filesystem) on the alternate disk:

    # /etc/mount -f filesystem_typeq /dev/dsk/sd1s0 /mnt
    # /etc/mount -f filesystem_typeq /dev/dsk/sd1s2 /mnt/usr
  9. Issue a df command to confirm that the root filesystem is mounted. (If /usr is a separate filesystem, also verify that it is mounted.)

    # df
    / (/dev/dsk/sd0s0 ): 38760 blocks 25107 i-nodes
    /mnt (/dev/dsk/sd1s0 ): 38812 blocks 25110 i-nodes

    You now have an image of the current root filesystem (and /usr if it is a separate filesystem) on the alternate disk.

  10. Change the filesystem type specified for the root filesystem in the /etc/vfstab file.


Install Software With the ALT DISK DELTA Procedure


ATTENTION

The following products cannot be installed with the ALT DISK DELTA procedure: ptx/SNA, ptx/SYNC, ptx/X.25, SequentLINK. Use the ROOT procedure to install these products after updating the base operating system.



ATTENTION

Be sure to delete any unsupported products before starting the installation. See Table 2-3, "Software to Deinstall."


To install software packages, use the following procedure. You must be root to perform the installation.

  1. If you have not done so already, insert the distribution CD-ROM into the CD-ROM drive.

  2. Issue the menu command to start ptx/ADMIN; then go to the Software Management Menu.

    Use System Administration -> Software Management


    ATTENTION

    If the menu system does not display properly, suspend or leave the menu system and type the following command: stty -tabs


    If you want to check the contents of the CD-ROM, select the "List Software Packages Available on Installation Distribution" option.

  3. Select the Install Software Package option.

  4. Specify the installation source, which can be either CD-ROM, nfs, or directory.

                    Installation Source Type
      
     Enter installation source type          ___________     
                             
    

  5. Specify the location of the installation source on the screen that appears next:

  6. On the Installation Type window, select the ALT DISK DELTA installation type. (The ROOT and INIT ALT DISK DELTA options will not appear if you booted from CD-ROM.)

     
                            Installation Type 
     Installation Type    Description
    ________________________________________________________________________
    ROOT                 Install on current root, /usr partitions          #
    ALT DISK DELTA       Install on mounted alternate root partition
    INIT ALT DISK DELTA  Make copies of current partitions and install on it
    SCRATCH              Initial install on alternate disk                 #  
    

  7. The Change Installation Disk form will ask you to specify the root partition on the alternate disk. The alternate disk must be a local disk attached directly to the CSM. The disk you specify is considered to be the installation disk for the Software Management menu options listed on the form.

                Change Installation Disk
     
    Enter root partition on alternate disk          _______
    (use the form /dev/dsk/sd0s0). If the 
    corresponding /usr directory is on a
    separate partition, that partition must 
    be mounted before using this form. The 
    alternate-disk mountpoint must be in the
    root directory (/mnt is valid;
    /a/mnt is not).
     
    The current installation root disk is          disk_name 
    The installation disk value affects
    these menu selections: Install SW Pkg,
    Remove SW Pkg, List SW Pkg, Check SW 
    Pkg, and View/Edit Preview Log.  The 
    installation disk value stays in effect 
    until changed.
    

  8. At the next screen, answer N.

            C2-Certifiable Product Installation
    
    Install only those products which        N
    are C2-Certifiable? (Y/N)
    Enter 'Y' to install only products
    which are C2-Certifiable
    

    Do not answer Y; DYNIX/ptx V4.4.10 has not been certified for C2-level security.

  9. Select the software packages to be installed from the Select Software Packages window. You can select multiple packages. The packages can be both new installations and updates to existing products. Following is an example of this window.

                          Select Software Packages 
           Part Number   Name       Description                  Version
    ________________________________________________________________
      1003-xxxxx-xx base       DYNIX/ptx(R) Base            v4.4.10 #
      1003-xxxxx-xx encryption DYNIX/ptx(R) Encryption      V4.4.10 
    N 1003-xxxxx-xx nfs        ptx/NFS                      v4.6.5
    


    ATTENTION

    ptx/SPDRIVERS should be installed before you build the kernel. You will see warnings if this product is not installed.

    If you are not already running the latest versions of the CSM and QCIC software, be sure to install them. These versions are required to boot the system without the distribution CD-ROM.



    ATTENTION

    Do not install the Fibre Channel Switch, Bridge, or Host Adapter software. This software is used only on IBM xSeries 430 and NUMA-Q 2000 systems.


    Certain software packages require that you enter a license password into the system nodelock file before the package can be installed. If the license password has already been entered, the letter L will precede the entry for that package in the Select Software Packages window. If the license password has not been entered, the letter N will appear. License passwords are not required for packages that do not specify one of these letters.


    ATTENTION

    If you selected several products that require licenses, it might take a few minutes for the next installation screen to appear.


  10. If you have selected a software package that requires a license password but you have not yet entered the password into the system nodelock file, a window listing the name of the product will be displayed. Highlight the line containing the product name and press F1 to enter the license for that product. To deselect the product, enter d.

    If you choose to enter the license password, the following form will be displayed. You must enter the license password, the expiration date, and the license checksum. The other values will be filled in for you. (The license information for the products you have purchased is located in the license folder shipped with your software.)

                Add Installation License
     
    Enter the product name               ________
     
    Enter the product version            ________
     
    Enter the node ID                    ________
     
    Enter the vendor ID                  ________
     
    Enter the license password           ________
     
    Enter the expiration date            ________
     
    Enter the license checksum           ________      
    

    The license entries you specify are added to the system nodelock file, /var/netls/nodelock.

  11. ptx/INSTALL now determines whether the products currently on the system are compatible with the products being installed. When a product requires that another product be installed, ptx/INSTALL also verifies that the required product has been selected for installation. If certain products are not compatible or if required products have not been selected, the following form will appear. You can either reselect products or abort the installation.

                   Compatibility Error
     
    View compatibility errors? (Y/N)               _
     
    Enter 'Y' to display the product
    incompatibilities identified.  You can
    then  reselect products to install
    and continue the installation.
     
    Answer 'N' to abort installation
    

  12. ptx/INSTALL requires additional information to install certain layered products. At this point, you will be asked for that information. For example, a product might include optional components; you will need to specify whether you want to install those components. Most of these screens are self-explanatory.

    If you are installing ptx/LICENSE, refer to the ptx/LICENSE Release Notes for a description of the installation and configuration screens that appear. In particular, do not configure ptx/LICENSE if ptx/TCP/IP is not already configured for networking on your system.

  13. ptx/INSTALL now verifies that there is adequate filesystem space to install the selected products. If there is not enough space, ptx/INSTALL halts the installation and displays the following form. Enter Y at the prompt to review any problems.

                       Disk Space Error
     
    View info on disk space insufficiencies?         ___
    Enter 'Y' to display products whose disk
    space requirements will not be met.
    Enter 'N' to abort the installation.
     
    You may restart the installation once
    the disk space requirements for all
    selected products have been resolved.
    

    When adequate disk space is available, you can resume the installation by selecting the Install Software Package option (or the Upgrade Base OS to v4.4/v4.5 option) from the Software Management menu.

  14. ptx/INSTALL now creates a preview log for each product to be installed. The preview log specifies whether file conflicts exist for the product. File conflicts can occur when the version of a file currently on the system differs from the original file, from the version of the file on the CD-ROM, or from both. You will need to resolve certain file conflicts manually. You can either halt the installation and resolve those file conflicts now, or continue with the installation and resolve the conflicts after the software is installed.

    Appendix B lists file conflicts that may occur for DYNIX/ptx, ptx/TCP/IP, and ptx/RAID. Be sure to review this information to help you determine whether you want to resolve file conflicts now or after the installation is complete.

                  Conflict File Resolution
     
    Resolve files in conflict now? (Y/N)        __
    Enter 'Y' to preload conflict files and 
    temporarily exit to view preview logs
    and resolve files in conflict.  
    Enter 'N' to continue with installation,
    and resolve files in conflict after the
    installation is completed.
    

    To resolve any conflicts after the installation is complete, answer N on the form. The installation will continue as specified in the preview logs for the selected products and the old files will be moved to the <product_name>/oldfiles directories.

    To resolve the conflicts now, answer Y on the form. The files in conflict will then be preloaded and the installation will exit. To locate file conflicts, use the View/Edit Preview Logs menu option from the Software Management menu to examine the preview logs. For details about the preview logs and resolving conflicts, refer to Appendix B.


    ATTENTION

    After resolving the conflicts, you can resume the installation by selecting the Install Software Package option (or the Upgrade Base OS to v4.4/v4.5 option) from the Software Management menu.


  15. If conflicts were found, the following form will specify where the files in conflict will be preloaded. You can change the locations for preloading new conflict files and saving the currently installed version (the old version) of conflict files.

    The default locations for new and old versions of conflict files are /usr/options/<product>/newfiles.<installation_date-time> and /usr/options/<product>/oldfiles.<installation_date-time>.

                 Conflict File Parent Directories
     
    Enter the parent directory for           ____________
    preloading new versions of files in
    conflict
    (For each product selected, a
    subdirectory of the form 'PRODUCT_NAME/
    newfiles.<installation_date_time>' will
    be created)
     
    Enter parent directory for saving        ____________
    old versions of files in conflict
    (For each product selected, a
    subdirectory of the form 'PRODUCT_NAME/
    oldfiles.<installation_date_time>' will
    be created)                                              
       
    

  16. ptx/INSTALL now determines whether the kernel needs to be recompiled after the installation is complete. Typically, this is needed only when the products to be installed contain kernel components. You can override the value specified on the form.

    We recommend that you answer Y on the form. ptx/INSTALL will then build a default kernel that includes the layered products you have installed. This kernel is needed to boot the operating system properly.

    The default kernel will not include any local kernel modifications that you have made. After booting the system, you can build your custom kernel and then reboot with that kernel.

     Configure and compile a kernel with default parameters
      
     Configure and compile a default kernel      ____
     following installation? (Y/N)
    

    If you chose to have ptx/INSTALL compile the default kernel, the following form appears. The name you specify at the first prompt cannot be std, mfg, or mod.

          Configure a kernel with default parameters
     
    Enter a unique name to associate with       default
    this kernel and all its associated
    configuration files
     
    Choose a kernel environment type            ___
           T for TIMESHARE
           P for PARALLEL
           C for COMMERCIAL
     
    Configure for audit? (Y/N)                  ___
     
    Enter a short description of this kernel    _______
                                             
    The starting machine type                   _______
     
    The starting architecture type              _______
     
    The starting configuration type             _______
    

  17. If the following situation applies to your installation, the Crosstools Source Type form shown next will appear: you have installed the base operating system on an alternate disk; you are now installing a layered product from another CD-ROM on the alternate disk; the layered product includes kernel components but the CD-ROM it is on does not include the V4.4.10 kernel compilation tools; you specified that the default kernel should be compiled.

                     Crosstools Source Type
     
    Enter crosstools source type                      ______
    Supported types: CD-ROM, nfs, directory, or NONE
    (crosstools source only)       
    

    Because the tools needed to compile the V4.4.10 kernel are not available, the form allows you to specify an alternate source for the tools. If you have another CD-ROM drive, insert the CD-ROM containing DYNIX/ptx V4.4.10 into that drive and enter CD-ROM as the crosstools source type on the form. You will then be asked to specify the name of the CD-ROM device, such as cd1.

    If you do not have another CD-ROM drive, use Cancel to exit the installation; then start the installation again. The "Configure and compile a kernel with default parameters" form will be displayed. Enter N at the prompt and compile the default kernel manually when the installation is complete.

  18. Specify whether you want to rebuild the man pages database and reboot the operating system on the installation disk after the software installation is complete.

    Rebuilding the man pages takes several minutes. You can also build the man pages at a later time using one of the methods described in the ptx/INSTALL Software Installation Guide.


    ATTENTION

    Do not have ptx/INSTALL reboot the kernel.


                  Installation Options
      
     Rebuild manpages following installation?(Y/N)    __
      
     Reboot on installation disk after                __
     installation? (Y/N)
      
     This is the last screen for installation
     Entering "Run" from this screen will
     start the installation of files for all
     selected products.
    

ptx/INSTALL will now perform the software installation.


ATTENTION

The installation procedure sets both the permanent and the temporary bootpaths to point to the new root disk. If you installed software on an alternate disk, the ptx/ADMIN Set Boot Strings and Flags menu option will not report the updated permanent bootpath until after the system is rebooted. To check the updated bootflags, use the /etc/bootflags command.


If you booted from the distribution CD-ROM, be sure to reset the loaderPath, QCICPath, and lvlBPath.


CSM Installation Problem

When the CSM software is installed, you may see a message stating that /usr/ssw is not mounted. The message can incorrectly appear even though /usr/ssw is mounted. Also, the complete message is not displayed. The message is as follows:

ERROR: 

A filesystem on a CSM SCSI channel 0 qd or sd disk in the address
range [0..7] must be mounted on /usr/ssw before this software
can be installed. Consult the CSM SW Installation Guide.

It is recommended that the installation be aborted
at this point. However you can continue if you
have a special reason to.

To abort the installation, press Return. If you are sure that /usr/ssw is mounted, enter N. The remainder of the message will then be displayed and the installation will continue:

Abort installation of CSM firmware? [yes] Checking /usr/ssw

The incomplete message will be repeated later in the installation. Answer N again to finish the installation.


Removing the Distribution CD (Optional)

If you want to remove the distribution CD from the drive before booting the system, you can. However, the system will boot properly if the distribution CD is left in the drive during the boot operation.

Previously, the documentation instructed you to devdestroy the cd device after the software was installed. This is no longer necessary as ptx/INSTALL now executes any devdestory action that may be required as part of the installation.