Chapter 8
ROOT Installation for NUMA-Q and Symmetry Systems

The ROOT installation procedure installs or updates layered products on the current root disk. This method cannot be used to install the base operating system.


Install Software With the ROOT Procedure

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

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

  2. If you are updating existing layered products on the current root disk, the installation must be run in single-user mode:

    1. Use the following command to go to single-user mode:

      # shutdown -gseconds -y -i1

      ATTENTION

      Filesystems cannot be mounted over ptx/NFS while the system is in single-user mode. If files will be installed on filesystems that are NFS-mounted, you must run the installation in multiuser mode. Before starting the installation, be sure no users are working with the package being installed.


    2. Mount all local filesystems listed in the /etc/vfstab file.

      # mountall -f filesystem_type
  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


    c1admapp       Software Management
    _______________________________________________________
     
    A Install Software Package   F View/Edit Preview Log
     
    B Remove Software Package    G Update Man Page Databases
           
    C List Software Packages     H Change Installation Disk
      
    D Check Package Consistency  I Alternate Disk Compare
                              
    E List Software Packages Available
      on Installation Distribution   
    
  4. Select the Install Software Package option.

  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 the ROOT installation type.

     
                                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                 #  
                    
    

    The installation process now retrieves the product information from the TOC file on the CD-ROM.

  8. Select the software packages to be installed from the window that appears next. 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 one or more software packages to install/update 
           Part Number   Name       Description                  Version 
    ________________________________________________________________
      1003-xxxxx-xx public     DYNIX/ptx(R) Public Software V4.4.7  
      1003-xxxxx-xx base_comms ptx/BaseComms                V4.4.7 
    N 1003-xxxxx-xx nfs        ptx/NFS                      v4.6.4
    


    ATTENTION

    The CSM, SSM, QCIC, and Online Diagnostic V1.4.1 software should be installed only on Symmetry systems.

    The Fibre Channel software should be installed only on NUMA-Q systems. The Switch software should be installed only on NUMA-Q systems with switched fabric.


    Certain software packages require that you enter a license key into the system nodelock file before the package can be installed. If the license key has already been entered, the letter L will precede the entry for that package in the Select Software Packages window. If the license key has not been entered, the letter N will appear. License keys 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.


  9. 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. Type i to enter the license for that product or d to deselect the product.

    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.

  10. 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
    

  11. 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.

  12. 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, resume the installation by selecting the Install Software Package option from the Software Management menu.

  13. ptx/INSTALL now creates a preview log for each product to be installed. The preview log specifies whether any 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 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. 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 specified in the next step.

    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 from the Software Management menu.


  14. 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)                              
        
    


    ATTENTION

    If you exited the installation to resolve conflicts, you can resume the installation by selecting the Install Software Package option from the Software Management menu.


  15. 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.

    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       ______
    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             _______
    

  16. 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 if you have updated the CSM or QCIC software, This software must be downloaded before the system is booted.


                     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 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.



CSM/SSM Installation Problem

When the CSM or SSM 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.

On a CSM-based system, 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.

On an SSM-based system, the message is as follows:

ERROR: /usr/ssw does not reside on a CSM/SSM SCSI channel 0 disk.

A filesystems on a SSM2 SCSI wd or sd boot disk must be mounted
on /usr/ssw before this software can be installed.
Consult the SSM2 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.

For CSM-based systems, the remainder of the message is as follows:

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

For SSM-based systems, the remainder of the message is as follows:

Abort installation of SSM 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-ROM

If you remove the CD-ROM from the drive before booting the system, you must run the devdestroy command on the CD-ROM device. This step enables the system to shut down cleanly when you reboot. The following example is for the cd0 device:

# /etc/devdestroy /dev/rdsk/cd0

If you do not run this command, the system will not shut down properly during the reboot and error messages such as the following will appear:

vtoc: unable to access diagnostic device /dev/diag/rdsk/cd0

The system will boot properly if the CD-ROM is left in the drive during the boot operation.