To install SFCFS using Kickstart

1. Create a directory for the Kickstart configuration files.

   # mkdir /kickstart_files/

2. Generate the Kickstart configuration files and the installproduct and uninstallproduct scripts. The configuration files have the extension .ks. Do one of the following:

   • To generate scripts and configuration files for all products, including Veritas Storage Foundation™ (SF), Storage Foundation Cluster File System (SFCFS), and Storage Foundation Cluster File System for Oracle® RAC, enter the following command:

     # ./installer -kickstart /kickstart_files/

     The system lists the scripts and files as they are generated.

   • To only generate scripts and configuration files for SFCFS, enter the following command:

     # ./installsfcfs -kickstart /kickstart_files/

     The command output includes the following:

     The kickstart script for SFCFS51 is generated at
     /kickstart_files/kickstart_sfcfs51.ks
     The installer script to configure SFCFS is generated at
     /kickstart_files/installsfcfs
     The installer script to uninstall SFCFS is generated at
     /kickstart_files/uninstallsfcfs

3. Setup an NFS exported location which the Kickstart client can access. For example, if /nfs_mount_kickstart is the directory which has been NFS exported, the NFS exported location may look similar to the following:

   # cat /etc/exports
   /nfs_mount_kickstart  * (rw,sync,no_root_squash)

4. Copy the entire directory of packages and scripts from the CD/DVD to the NFS location.

5. Copy the required SFCFS installproduct and uninstallproduct scripts you generated in step 2 to the following NFS directory:

   # cp /kickstart_files/installsfcfs /nfs_mount_kickstart

   # cp /kickstart_files/uninstallsfcfs /nfs_mount_kickstart

6. Verify the contents of the directory. They should look similar to the following:

   # ls /nfs_mount_kickstart/
   

   rpms     scripts          installsfcfs     uninstallsfcfs

7. In the SFCFS Kickstart configuration file, modify the BUILDSRC variable to point to the actual NFS location. The variable has the following format:

   BUILDSRC="hostname_or_ip:/nfs_mount_kickstart"

8. Append the entire modified contents of the Kickstart configuration file to the operating system ks.cfg file.

9. Launch the Kickstart installation for the RHEL5 operating system.

10. After the operating system installation is complete, check the file /var/tmp/kickstart.log for any errors related to the installation of Veritas packages and CPI scripts.

11. Verify that all the product rpms have been installed. Enter the following command:

    # rpm -qa | grep -i vrts

    If you do not find any installation issues or errors, configure the product stack. Enter the following command:

    # /opt/VRTS/install/installsfcfs -configure node1 node2

12. Verify that all the configured llt links and gab ports have started. Enter the following:

    # gabconfig -a
    GAB Port Memberships
    ===============================================================
    Port a gen   b66f01 membership 01
    Port b gen   b66f03 membership 01
    Port d gen   b66f07 membership 01
    Port f gen   b66f0d membership 01
    Port h gen   b66f05 membership 01
    Port v gen   b66f09 membership 01
    Port w gen   b66f0b membership 01

13. Verify that the product is configured properly. Enter the following:

    # hastatus -summ
    -- SYSTEM STATE
    -- System               State                Frozen
     
    A  swlx13               RUNNING              0
    A  swlx14               RUNNING              0
     
    -- GROUP STATE
    -- Group           System               Probed     AutoDisabled    State
     
    B  cvm             swlx13               Y          N               ONLINE
    B  cvm             swlx14               Y          N               ONLINE

    Note that the cvm service group comes online when the SFCFSHA stack is configured.

14. Verify that the ODM package is installed and determine which mode it is running in.

    For example, in the case of the SFCFSHA stack, the ODM cluster status is shown as enabled exclusive.

15. If you configured the node in a secured mode, verify the VxSS service group status. For example:

    # hastatus -summary
    -- Group         System             Probed     AutoDisabled    State
                                                                                                                                                                
    B  VxSS          swlx13             Y          N               ONLINE
    B  VxSS          swlx14             Y          N               ONLINE