test

Sun Cluster Software Installation Guide for Solaris OS

How to Install Solaris and Sun Cluster Software (JumpStart)

This procedure describes how to set up and use the scinstall(1M) custom JumpStart installation method. This method installs both Solaris and Sun Cluster software on all cluster nodes in a single operation and establishes the cluster. You can also use this procedure to add new nodes to an existing cluster.

  1. Ensure that the hardware setup is complete and that connections are verified before you install Solaris software.

    See the Sun Cluster Hardware Administration Collection and your server and storage device documentation for details on how to set up the hardware.

  2. Ensure that your cluster configuration planning is complete.

    See How to Prepare for Cluster Software Installation for requirements and guidelines.

  3. Have available the following information:

    • The Ethernet address of each cluster node

    • The following completed installation worksheet

    Table 2–7 JumpStart Installation and Configuration Worksheet

    Component 

    Description/Example 

    Enter Answers Here 

    JumpStart Directory 

    What is the name of the JumpStart directory to use? 

    		 

    Cluster Name 

    What is the name of the cluster that you want to establish? 

    		 

    Cluster Nodes 

    What are the names of the cluster nodes that are planned for the initial cluster configuration? 

    		 

    DES Authentication 

    Do you need to use DES authentication? 

    No  |  Yes  

    Network Address for the Cluster Transport 

    Do you want to accept the default network address (172.16.0.0)?

    Yes   |  No  

    If no, supply your own network address: 

    _____ . _____.0.0

    Do you want to accept the default netmask (255.255.0.0)?

    Yes   |  No  

    If no, supply your own netmask: 

    255.255.___ . ___

    Point-to-Point Cables 

    Does this cluster use transport junctions (two-node clusters only)?

    Yes  |  No 

    Cluster-Transport Junctions 

    If used, what are the names of the two transport junctions? 

      Defaults: switch1 and switch2


    First

    Second

    Cluster-Transport Adapters and Cables 

    First node name: 

    		 

    Transport adapters: 

    First

      

    Second

      

    Where does each transport adapter connect to (a transport junction or another adapter)?

      Junction defaults: switch1 and switch2


    		  

    For transport junctions, do you want to use the default port name? 

    Yes | No 

    Yes | No 

    If no, what is the name of the port that you want to use? 

    		  

    Do you want to use autodiscovery to list the available adapters for the other nodes? 

    If no, supply the following information for each additional node: 

    Yes  |  No 
     

    Node name: 

    		 

    Transport adapters: 

    First

      

    Second

      

    Where does each transport adapter connect to (a transport junction or another adapter)?

      Junction defaults: switch1 and switch2


    		  

    For transport junctions, do you want to use the default port name? 

    Yes | No 

    Yes | No 

    If no, what is the name of the port that you want to use? 

     

     

    Global-Devices File System 

    Do you want to use the default name of the global-devices file system (/globaldevices)?

    Yes  |   No 

    If no, do you want to use an already-existing file system? 

    Yes  |   No 

    What is the name of the file system? 

    		 

    Software Patch Installation 

    Do you want scinstall to install patches for you?

    Yes  |   No 

    If yes, what is the name of the patch directory? 

    		 

    Do you want to use a patch list? 

    Yes  |  No 

    See Planning the Solaris Operating Environment and Planning the Sun Cluster Environment for planning guidelines.

    Note –

    You cannot change the private-network address and netmask after scinstall processing has finished. If you need to use a different private-network address or netmask and the node is still in installation mode, follow the procedures in How to Uninstall Sun Cluster Software to Correct Installation Problems. Then repeat this procedure to reinstall and configure the node with the correct information.

  4. Do you use a naming service?

    • If no, proceed to Step 5. You set up the necessary hostname information in Step 15.

    • If yes, add the following information to any naming services that clients use to access cluster services:

      • Address-to-name mappings for all public hostnames and logical addresses

      • The IP address and hostname of the JumpStart server

    See IP Addresses for planning guidelines. See your Solaris system-administrator documentation for information about using Solaris naming services.

  5. Are you installing a new node to an existing cluster?

  6. Set up your JumpStart installation server for Solaris operating-environment installation.

    • SPARC: As superuser, set up your JumpStart installation server.

    • x86: Set up and configure your JumpStart Dynamic Host Configuration Protocol (DHCP) server and your Solaris network for Preboot Execution Environment (PXE) installations.

      The Sun Fire V60x and Sun Fire V65x Server Solaris Operating Environment Installation Guide contains instructions about how to set up a DHCP server and Solaris network for PXE installations.

      x86 only –

      You must use a DHCP server and PXE to install Sun Cluster software with JumpStart over a network.

    See “Preparing Custom JumpStart Installations (Tasks)” in Solaris 9 Installation Guide for instructions on how to set up a JumpStart installation server. See also the setup_install_server(1M) and add_install_client(1M) man pages.

    When you set up the installation server, ensure that the following requirements are met:

    • The installation server is on the same subnet as the cluster nodes but the server is not itself a cluster node.

    • The installation server installs a release of the Solaris operating environment that is supported by the Sun Cluster software.

    • A custom JumpStart directory exists for JumpStart installation of Sun Cluster software. This jumpstart-dir directory must contain a copy of the check(1M) utility. The directory must also be NFS exported for reading by the JumpStart installation server.

    • Each new cluster node is configured as a custom JumpStart install client that uses the custom JumpStart directory that you set up for Sun Cluster installation.

  7. Create a directory on the JumpStart installation server to hold your copy of the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM.

    Skip this step if a directory already exists.

    In the following example, the /export/suncluster directory is created for this purpose.


    # mkdir -m 755 /export/suncluster

  8. Copy the Sun Cluster CD-ROM to the JumpStart installation server.

    1. Insert the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM into the CD-ROM drive on the JumpStart installation server.

      If the volume management daemon vold(1M) is running and configured to manage CD-ROM devices, the daemon automatically mounts the CD-ROM on the /cdrom/cdrom0 directory.

    2. From the /cdrom/cdrom0 directory, change to the Solaris_arch/Product/sun_cluster/Solaris_ver/Tools directory, where arch is sparc or x86 and where ver is 8 (for Solaris 8) or 9 (for Solaris 9) .

      The following example uses the path to the SPARC Solaris 8 version of Sun Cluster software.


      # cd /cdrom/cdrom0/Solaris_sparc/Product/sun_cluster/Solaris_8/Tools

    3. Copy the CD-ROM to a new directory on the JumpStart installation server.

      The scinstall command creates the new installation directory when the command copies the CD-ROM files. The following example uses the installation directory name /export/suncluster/sc31.


      # ./scinstall -a /export/suncluster/sc31

    4. Unload the CD-ROM from the CD-ROM drive.

      1. To ensure that the CD-ROM is not being used, change to a directory that does not reside on the CD-ROM.

      2. Eject the CD-ROM.


        # eject cdrom

    5. Ensure that the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM image on the JumpStart installation server is NFS exported for reading by the JumpStart installation server.

      See “Solaris NFS Environment” in System Administration Guide, Volume 3 or “Managing Network File Systems (Overview)” in System Administration Guide: Resource Management and Network Services for more information about automatic file sharing. See also the share(1M) and dfstab(4) man pages.

  9. From the JumpStart installation server, start the scinstall(1M) utility.

    The path /export/suncluster/sc31 is used here as an example of the installation directory that you created. In the CD-ROM path, replace arch with sparc or x86 and replace ver with 8 (for Solaris 8) or 9 (for Solaris 9).


    # cd /export/suncluster/sc31/Solaris_arch/Product/sun_cluster/Solaris_ver/Tools
# ./scinstall

  10. Follow these guidelines to use the interactive scinstall utility:

    • Interactive scinstall enables you to type ahead. Therefore, do not press the Return key more than once if the next menu screen does not appear immediately.

    • Unless otherwise noted, you can press Control-D to return to either the start of a series of related questions or to the Main Menu.

    • Default answers or answers to previous sessions are displayed in brackets ([ ]) at the end of a question. Press Return to enter the response that is in brackets without typing it.

  11. From the Main Menu, choose Configure a cluster to be JumpStarted from this installation server.

    This option is used to configure custom JumpStart finish scripts. JumpStart uses these finish scripts to install the Sun Cluster software.


     *** Main Menu ***
 
    Please select from one of the following (*) options:
 
      * 1) Install a cluster or cluster node
      * 2) Configure a cluster to be JumpStarted from this install server
        3) Add support for new data services to this cluster node
      * 4) Print release information for this cluster node
 
      * ?) Help with menu options
      * q) Quit
 
    Option:  2

    Note –

    If the JumpStart option does not have an asterisk in front, the option is disabled. This condition indicates that JumpStart setup is not complete or that the setup has an error. To correct this condition, do the following:

    1. Exit the scinstall utility.

    2. Repeat Step 6 through Step 8 to correct JumpStart setup.

    3. Restart the scinstall utility.

  12. Follow the menu prompts to supply your answers to Table 2–7, which you completed in Step 3.

  13. If necessary, make adjustments to the default class file, or profile, that scinstall creates.

    The scinstall command creates the following autoscinstall.class default class file in the jumpstart-dir/autoscinstall.d/3.1 directory.


    install_type    initial_install
system_type     standalone
partitioning    explicit
filesys         rootdisk.s0 free /
filesys         rootdisk.s1 750  swap
filesys         rootdisk.s3 512  /globaldevices
filesys         rootdisk.s7 20
cluster         SUNWCuser        add
package         SUNWman          add

    The default class file installs the End User Solaris Software Group (SUNWCuser). If your configuration has additional Solaris software requirements, change the class file accordingly. See Solaris Software Group Considerations for more information.

    If you installed the End User Solaris Software Group, add to the default class file any additional Solaris software packages that you might need. The following table lists Solaris packages that are required to support some Sun Cluster functionality.

    Table 2–8 Solaris Software Package Dependencies

    Feature 

    Required Solaris Software Packages (shown in installation order) 

    RSMAPI,SCI-PCI adapters (SPARC based clusters only) 

    SUNWrsm SUNWrsmx SUNWrsmo SUNWrsmox

    SunPlex Manager 

    SUNWapchr SUNWapchu

    You can change the default class file in one of the following ways:

    • Edit the autoscinstall.class file directly. These changes are applied to all nodes in all clusters that use this custom JumpStart directory.

    • Update the rules file to point to other profiles, then run the check utility to validate the rules file.

    As long as the Solaris operating-environment installation profile meets minimum Sun Cluster file-system allocation requirements, Sun Cluster software places no restrictions on other changes to the installation profile. See System Disk Partitions for partitioning guidelines and requirements to support Sun Cluster software.

    For more information about JumpStart profiles, see “Preparing Custom JumpStart Installations (Tasks)” in Solaris 9 Installation Guide or “Preparing Custom JumpStart Installations (Tasks)” in Solaris 9 Installation Guide.

  14. Set up Solaris patch directories.

    Note –

    If you specified a patch directory to the scinstall utility, patches that are located in Solaris patch directories are not installed.

    1. Create jumpstart-dir/autoscinstall.d/nodes/node/patches directories on the JumpStart installation server.

      Create one directory for each node in the cluster, where node is the name of a cluster node. Alternately, use this naming convention to create symbolic links to a shared patch directory.


      # mkdir jumpstart-dir/autoscinstall.d/nodes/node/patches

    2. Place copies of any Solaris patches into each of these directories.

    3. Place copies of any hardware-related patches that you must install after Solaris software is installed into each of these directories.

  15. Set up files to contain the necessary hostname information locally on each node.

    1. On the JumpStart installation server, create files that are named jumpstart-dir/autoscinstall.d/nodes/node/archive/etc/inet/hosts.

      Create one file for each node, where node is the name of a cluster node. Alternately, use this naming convention to create symbolic links to a shared hosts file.

    2. Add the following entries into each file.

      • IP address and hostname of the NFS server that holds a copy of the Sun Cluster CD-ROM image. The NFS server could be the JumpStart installation server or another machine.

      • IP address and hostname of each node in the cluster.

  16. Do you intend to use the Remote Shared Memory Application Programming Interface (RSMAPI) or use SCI-PCI adapters for the interconnect transport?

    • If no, proceed to Step 17 if you intend to add your own postinstallation finish script. Otherwise, skip to Step 18.

    • If yes, follow instructions in Step 17 to set up a postinstallation finish script to install the following additional packages. Install the appropriate packages from the Solaris_arch/Product/sun_cluster/Solaris_ver/Packages directory of the Sun Java Enterprise System 2004Q2 2 of 2 CD-ROM in the order that is given in the following table.

      Note –

      In the CD-ROM path, replace arch with sparc or x86 and replace ver with 8 (for Solaris 8) or 9 (for Solaris 9).

      Feature 

      Additional Sun Cluster 3.1 4/04 Packages to Install  

      RSMAPI 

      SUNWscrif

      SCI-PCI adapters 

      SUNWsci SUNWscid SUNWscidx

  17. (Optional) Add your own postinstallation finish script.

    Note –

    If you intend to use the Remote Shared Memory Application Programming Interface (RSMAPI) or use SCI-PCI adapters for the interconnect transport, you must modify the finish script to install the Sun Cluster SUNWscrif software package. This package is not automatically installed by scinstall.

    You can add your own finish script, which is run after the standard finish script installed by the scinstall command. See “Preparing Custom JumpStart Installations” in Solaris 8 Advanced Installation Guide or “Preparing Custom JumpStart Installations (Tasks)” in Solaris 9 Installation Guide for information about creating a JumpStart finish script.

    1. Name your finish script finish.

    2. Copy your finish script to the jumpstart-dir/autoscinstall.d/nodes/node directory.

      Create one directory for each node in the cluster. Alternately, use this naming convention to create symbolic links to a shared finish script.

  18. If you are using a cluster administrative console, display a console screen for each node in the cluster.

    • If Cluster Control Panel (CCP) software is installed and configured on your administrative console, you can use the cconsole(1M) utility to display the individual console screens. The cconsole utility also opens a master window from which you can send your input to all individual console windows at the same time. Use the following command to start cconsole:


      # /opt/SUNWcluster/bin/cconsole clustername &

    • If you do not use the cconsole utility, connect to the consoles of each node individually.

  19. Shut down each node.


    # shutdown -g0 -y -i0

  20. Boot each node to start the JumpStart installation.

    • On SPARC based systems, do the following:


      ok boot net - install

      Note –

      Surround the dash (-) in the second command with a space on each side.

    • On x86 based systems, do the following:

      1. When the BIOS information screen appears, press the Esc key.

        The Select Boot Device screen appears.

      2. On the Select Boot Device screen, choose the listed IBA that is connected to the same network as the JumpStart DHCP installation server.

        The lowest number to the right of the IBA boot choices corresponds to the lower Ethernet port number. The higher number to the right of the IBA boot choices corresponds to the higher Ethernet port number.

        The node reboots and the Device Configuration Assistant appears.

      3. On the Boot Solaris screen, choose Net.

      4. At the following prompt, choose Custom JumpStart and press Enter:


        Select the type of installation you want to perform:

         1 Solaris Interactive
         2 Custom JumpStart

Enter the number of your choice followed by the <ENTER> key.

If you enter anything else, or if you wait for 30 seconds,
an interactive installation will be started.

      5. When prompted, answer the questions and follow the instructions on the screen.

    JumpStart installs the Solaris software and Sun Cluster software on each node.

    Note –

    Unless you have installed your own /etc/inet/ntp.conf file, the scinstall command installs a default ntp.conf file for you. The default file is shipped with references to the maximum number of nodes. Therefore, the xntpd(1M) daemon might issue error messages regarding some of these references at boot time. You can safely ignore these messages. See How to Configure Network Time Protocol (NTP) for information on how to suppress these messages under otherwise normal cluster conditions.

    When the installation is successfully completed, each node is fully installed as a new cluster node. Sun Cluster installation output is logged in a /var/cluster/logs/install/scinstall.log.N file.

    You cannot change the private-network address and netmask after scinstall processing has finished. If you need to use a different private-network address or netmask and the node is still in installation mode, follow the procedures in How to Uninstall Sun Cluster Software to Correct Installation Problems. Then repeat this procedure to reinstall and configure the node with the correct information.

  21. Are you installing a new node to an existing cluster?

    • If no, proceed to Step 22.

    • If yes, create mount points on the new node for all existing cluster file systems.

    1. From another cluster node that is active, display the names of all cluster file systems.


      % mount | grep global | egrep -v node@ | awk '{print $1}'

    2. On the node that you added to the cluster, create a mount point for each cluster file system in the cluster.


      % mkdir -p mountpoint

      For example, if a file-system name that is returned by the mount command is /global/dg-schost-1, run mkdir -p /global/dg-schost-1 on the node that is being added to the cluster.

      Note –

      The mount points become active after you reboot the cluster in Step 24.

    3. Is VERITAS Volume Manager (VxVM) installed on any nodes that are already in the cluster?

      • If no, proceed to Step 22.

      • If yes, ensure that the same vxio number is used on each of the VxVM-installed nodes. Also ensure that the vxio number is available for use on each of the nodes that do not have VxVM installed. 


        # grep vxio /etc/name_to_major
vxio NNN

        If the vxio number is already in use on a node that does not have VxVM installed, free the number on that node. Change the /etc/name_to_major entry to use a different number.

  22. (Optional) To use dynamic reconfiguration on Sun Enterprise 10000 servers, add the following entry to the /etc/system file. Add this entry on each node in the cluster.


    set kernel_cage_enable=1

    This entry becomes effective after the next system reboot. See the Sun Cluster System Administration Guide for Solaris OS for procedures to perform dynamic reconfiguration tasks in a Sun Cluster configuration. See your server documentation for more information about dynamic reconfiguration.

  23. x86: Set the default boot file to kadb.


    # eeprom boot-file=kadb

    The setting of this value enables you to reboot the node if you are unable to access a login prompt.

  24. Did you add a new node to an existing cluster or install Sun Cluster software patches that require you to reboot the entire cluster, or both?

    • If no, reboot the individual node if any patches that you installed require a node reboot. Also reboot if any other changes that you made require a reboot to become active, then proceed to Step 25.

    • If yes, perform a reconfiguration reboot of the cluster as instructed in the following steps.

    1. From one node, shut down the cluster.


      # scshutdown

      Note –

      Do not reboot the first-installed node of the cluster until after the cluster is shut down.

    2. Reboot each node in the cluster.

      • On SPARC based systems, do the following:


        ok boot

      • On x86 based systems, do the following:


                             <<< Current Boot Parameters >>>
Boot path: /pci@0,0/pci-ide@7,1/ata@1/cmdk@0,0:b
Boot args:

Type   b [file-name] [boot-flags] <ENTER>  to boot with options
or     i <ENTER>                           to enter boot interpreter
or     <ENTER>                             to boot with defaults

                 <<< timeout in 5 seconds >>>
Select (b)oot or (i)nterpreter: b

    Note –

    Until cluster installation mode is disabled, only the first-installed node, which established the cluster, has a quorum vote. In an established cluster that is still in installation mode, if the cluster is not shut down before the first-installed node is rebooted, the remaining cluster nodes cannot obtain quorum. The entire cluster then shuts down. Cluster nodes remain in installation mode until the first time you run the scsetup(1M) command, during the procedure How to Perform Postinstallation Setup and Configure Quorum Devices.

    The scinstall utility installs and configures all cluster nodes and reboots the cluster. The cluster is established when all nodes have successfully booted into the cluster. Sun Cluster installation output is logged in a /var/cluster/logs/install/scinstall.log.N file.

  25. SPARC: Do you intend to install VERITAS File System?