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 OS and Sun Cluster software on all cluster nodes in the same 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. If you use a naming service, 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.

  4. If you are installing a new node to an existing cluster, add the node to the list of authorized cluster nodes.

    1. Run scsetup(1M) from another cluster node that is active.

    2. Use the scsetup utility to add the new node's name to the list of authorized cluster nodes.

    For more information, see “How to Add a Cluster Node to the Authorized Node List” in “Adding and Removing a Cluster Node” in Sun Cluster System Administration Guide for Solaris OS.

  5. Set up your JumpStart installation server.

  6. On a cluster node or another machine of the same server platform, prepare a flash archive of the Solaris OS and Sun Web Console software.

    1. Install the Solaris OS as described in How to Install Solaris Software.

    2. Insert the Sun Cluster 3.1 9/04 CD-ROM in the CD-ROM drive.

    3. Change to the /cdrom/cdrom0/Solaris_arch/Product/sun_web_console/2.1/ directory, where arch is sparc or x86.

    4. Run the setup command.


      # ./setup

      The setup command installs all packages to support Sun Web Console.

    5. Change to a directory that does not reside on the CD-ROM and eject the CD-ROM.


      # eject cdrom

    6. Create the flash archive of the installed system.


      # flar create -n name archive
      -n name

      Name to give the flash archive.

      archive

      File name to give the flash archive, with the full path. By convention, the file name ends in .flar.

      Follow procedures in “Creating Web Start Flash Archives” in Solaris 8 Advanced Installation Guide or “Creating Solaris Flash Archives (Tasks)” in Solaris 9 9/04 Installation Guide.

  7. Copy the flash archive to the JumpStart installation server.

  8. Ensure that the flash archive 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. Create a directory on the JumpStart installation server to hold your copy of the Sun Cluster 3.1 9/04 CD-ROM.

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


    # mkdir -m 755 /export/suncluster/

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

    1. Insert the Sun Cluster 3.1 9/04 CD-ROM into the CD-ROM drive on the JumpStart installation server.

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

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


      # cd /cdrom/cdrom0/Solaris_arch/Product/sun_cluster/Solaris_ver/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. Change to a directory that does not reside on the CD-ROM and eject the CD-ROM.


      # eject cdrom

  11. Ensure that the Sun Cluster 3.1 9/04 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.

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

    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 

    Specify for each additional node

    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 

    (specify for each node)

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

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

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

  15. From the Main Menu, choose the menu item, 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. Quit the scinstall utility.

    2. Repeat Step 5 through Step 10 to correct JumpStart setup.

    3. Restart the scinstall utility.

  16. Follow the menu prompts to supply your answers from the worksheet that you completed in Step 12.

    The scinstall command stores your configuration information and 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

  17. Make adjustments to the default autoscinstall.class file to configure JumpStart to install the flash archive.

    1. Change the following entries in the autoscinstall.class file. In the last new entry in the table, archive represents the location of the flash archive file.

      Existing Entry 

      New Entry 

      install_type

      initial_install

      install_type

      flash_install

      system_type

      standalone

      archive_location

      archive

    2. Remove all entries that would install a specific package.


      cluster         SUNWCuser        add
package         SUNWman          add

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

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

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

  21. Shut down each node.


    # shutdown -g0 -y -i0

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

  23. If you are installing a new node to an existing cluster, 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 26.

    3. If VERITAS Volume Manager (VxVM) is installed on any nodes that are already in the cluster, view the vxio number on each VxVM–installed node.


      # grep vxio /etc/name_to_major
vxio NNN

      • Ensure that the same vxio number is used on each of the VxVM-installed nodes.

      • Ensure that the vxio number is available for use on each of the nodes that do not have VxVM installed.

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

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

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

  26. If you performed a task that requires a cluster reboot, follow these steps to perform a reconfiguration reboot of the cluster.

    The following are some of the tasks that require a reboot:

    • Adding a new node to an existing cluster

    • Installing patches that require a node or cluster reboot

    • Making configuration changes that require a reboot to become active

    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. 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 that you run the scsetup(1M) command. You run this command during the procedure How to Perform Postinstallation Setup and Configure Quorum Devices.

    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

    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.

  27. Install Sun StorEdge QFS file system software.

    Follow the procedures for initial installation in the Sun StorEdge QFS and Sun StorEdge SAM-FS Software Installation and Configuration Guide.

  28. SPARC: To install VERITAS File System, go to SPARC: How to Install VERITAS File System Software.

  29. Set up the name-service look-up order.

    Go to How to Configure the Name-Service Switch.