Storage Foundation and High Availability 7.4.2 Configuration and Upgrade Guide - Linux

Last Published:
Product(s): InfoScale & Storage Foundation (7.4.2)
Platform: Linux
  1. Section I. Introduction to SFHA
    1. Introducing Storage Foundation and High Availability
      1. About Storage Foundation High Availability
        1.  
          About Veritas Replicator Option
      2.  
        About Veritas InfoScale Operations Manager
      3. About Storage Foundation and High Availability features
        1.  
          About LLT and GAB
        2.  
          About I/O fencing
        3.  
          About global clusters
      4.  
        About Veritas Services and Operations Readiness Tools (SORT)
      5. About configuring SFHA clusters for data integrity
        1.  
          About I/O fencing for SFHA in virtual machines that do not support SCSI-3 PR
        2. About I/O fencing components
          1.  
            About data disks
          2.  
            About coordination points
          3.  
            About preferred fencing
  2. Section II. Configuration of SFHA
    1. Preparing to configure
      1. I/O fencing requirements
        1.  
          Coordinator disk requirements for I/O fencing
        2.  
          CP server requirements
        3.  
          Non-SCSI-3 I/O fencing requirements
    2. Preparing to configure SFHA clusters for data integrity
      1. About planning to configure I/O fencing
        1.  
          Typical SFHA cluster configuration with server-based I/O fencing
        2.  
          Recommended CP server configurations
      2. Setting up the CP server
        1.  
          Planning your CP server setup
        2.  
          Installing the CP server using the installer
        3.  
          Configuring the CP server cluster in secure mode
        4.  
          Setting up shared storage for the CP server database
        5.  
          Configuring the CP server using the installer program
        6. Configuring the CP server manually
          1.  
            Configuring the CP server manually for HTTPS-based communication
          2.  
            Generating the key and certificates manually for the CP server
          3.  
            Completing the CP server configuration
        7. Configuring CP server using response files
          1.  
            Response file variables to configure CP server
          2.  
            Sample response file for configuring the CP server on single node VCS cluster
          3.  
            Sample response file for configuring the CP server on SFHA cluster
        8.  
          Verifying the CP server configuration
    3. Configuring SFHA
      1. Configuring Storage Foundation High Availability using the installer
        1.  
          Overview of tasks to configure SFHA using the product installer
        2.  
          Required information for configuring Storage Foundation and High Availability Solutions
        3.  
          Starting the software configuration
        4.  
          Specifying systems for configuration
        5.  
          Configuring the cluster name
        6.  
          Configuring private heartbeat links
        7.  
          Configuring the virtual IP of the cluster
        8.  
          Configuring SFHA in secure mode
        9. Configuring a secure cluster node by node
          1.  
            Configuring the first node
          2.  
            Configuring the remaining nodes
          3.  
            Completing the secure cluster configuration
        10.  
          Adding VCS users
        11.  
          Configuring SMTP email notification
        12.  
          Configuring SNMP trap notification
        13.  
          Configuring global clusters
        14. Completing the SFHA configuration
          1.  
            Verifying the NIC configuration
        15.  
          About Veritas License Audit Tool
        16. Verifying and updating licenses on the system
          1.  
            Checking licensing information on the system
          2.  
            Replacing a SFHA keyless license with another keyless license
          3.  
            Replacing a SFHA keyless license with a permanent license
      2.  
        Configuring SFDB
    4. Configuring SFHA clusters for data integrity
      1. Setting up disk-based I/O fencing using installer
        1.  
          Initializing disks as VxVM disks
        2. Checking shared disks for I/O fencing
          1.  
            Verifying Array Support Library (ASL)
          2.  
            Verifying that the nodes have access to the same disk
          3.  
            Testing the disks using vxfentsthdw utility
        3.  
          Configuring disk-based I/O fencing using installer
        4.  
          Refreshing keys or registrations on the existing coordination points for disk-based fencing using the installer
      2. Setting up server-based I/O fencing using installer
        1.  
          Refreshing keys or registrations on the existing coordination points for server-based fencing using the installer
        2. Setting the order of existing coordination points for server-based fencing using the installer
          1.  
            About deciding the order of existing coordination points
          2.  
            Setting the order of existing coordination points using the installer
      3.  
        Setting up non-SCSI-3 I/O fencing in virtual environments using installer
      4.  
        Setting up majority-based I/O fencing using installer
      5.  
        Enabling or disabling the preferred fencing policy
    5. Manually configuring SFHA clusters for data integrity
      1. Setting up disk-based I/O fencing manually
        1.  
          Removing permissions for communication
        2.  
          Identifying disks to use as coordinator disks
        3.  
          Setting up coordinator disk groups
        4.  
          Creating I/O fencing configuration files
        5.  
          Modifying VCS configuration to use I/O fencing
        6.  
          Verifying I/O fencing configuration
      2. Setting up server-based I/O fencing manually
        1.  
          Preparing the CP servers manually for use by the SFHA cluster
        2.  
          Generating the client key and certificates manually on the client nodes
        3. Configuring server-based fencing on the SFHA cluster manually
          1.  
            Sample vxfenmode file output for server-based fencing
        4.  
          Configuring CoordPoint agent to monitor coordination points
        5.  
          Verifying server-based I/O fencing configuration
      3. Setting up non-SCSI-3 fencing in virtual environments manually
        1.  
          Sample /etc/vxfenmode file for non-SCSI-3 fencing
      4. Setting up majority-based I/O fencing manually
        1.  
          Creating I/O fencing configuration files
        2.  
          Modifying VCS configuration to use I/O fencing
        3.  
          Verifying I/O fencing configuration
    6. Performing an automated SFHA configuration using response files
      1.  
        Configuring SFHA using response files
      2.  
        Response file variables to configure SFHA
      3.  
        Sample response file for SFHA configuration
    7. Performing an automated I/O fencing configuration using response files
      1.  
        Configuring I/O fencing using response files
      2.  
        Response file variables to configure disk-based I/O fencing
      3.  
        Sample response file for configuring disk-based I/O fencing
      4. Response file variables to configure server-based I/O fencing
        1.  
          Sample response file for configuring server-based I/O fencing
      5.  
        Sample response file for configuring non-SCSI-3 I/O fencing
      6.  
        Response file variables to configure non-SCSI-3 I/O fencing
      7.  
        Response file variables to configure majority-based I/O fencing
      8.  
        Sample response file for configuring majority-based I/O fencing
  3. Section III. Upgrade of SFHA
    1. Planning to upgrade SFHA
      1.  
        About the upgrade
      2.  
        Supported upgrade paths
      3.  
        Considerations for upgrading SFHA to 7.4.2 on systems configured with an Oracle resource
      4. Preparing to upgrade SFHA
        1.  
          Getting ready for the upgrade
        2.  
          Creating backups
        3.  
          Determining if the root disk is encapsulated
        4. Pre-upgrade planning when VVR is configured
          1.  
            Considerations for upgrading SFHA to 7.4 or later on systems with an ongoing or a paused replication
          2. Planning an upgrade from the previous VVR version
            1.  
              Planning and upgrading VVR to use IPv6 as connection protocol
        5. Preparing to upgrade VVR when VCS agents are configured
          1. Freezing the service groups and stopping all the applications
            1.  
              Determining the nodes on which disk groups are online
          2.  
            Preparing for the upgrade when VCS agents are configured
        6.  
          Upgrading the array support
      5.  
        Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches
    2. Upgrading Storage Foundation and High Availability
      1. Upgrading Storage Foundation and High Availability from previous versions to 7.4.2
        1.  
          Upgrading Storage Foundation and High Availability using the product installer
      2. Upgrading Volume Replicator
        1. Upgrading VVR without disrupting replication
          1.  
            Upgrading VVR on the Secondary
          2.  
            Upgrading VVR on the Primary
      3.  
        Upgrading SFDB
    3. Performing a rolling upgrade of SFHA
      1.  
        About rolling upgrade
      2.  
        Performing a rolling upgrade using the product installer
    4. Performing a phased upgrade of SFHA
      1. About phased upgrade
        1.  
          Prerequisites for a phased upgrade
        2.  
          Planning for a phased upgrade
        3.  
          Phased upgrade limitations
        4.  
          Phased upgrade example
        5.  
          Phased upgrade example overview
      2. Performing a phased upgrade using the product installer
        1.  
          Moving the service groups to the second subcluster
        2.  
          Upgrading the operating system on the first subcluster
        3.  
          Upgrading the first subcluster
        4.  
          Preparing the second subcluster
        5.  
          Activating the first subcluster
        6.  
          Upgrading the operating system on the second subcluster
        7.  
          Upgrading the second subcluster
        8.  
          Finishing the phased upgrade
    5. Performing an automated SFHA upgrade using response files
      1.  
        Upgrading SFHA using response files
      2.  
        Response file variables to upgrade SFHA
      3.  
        Sample response file for full upgrade of SFHA
      4.  
        Sample response file for rolling upgrade of SFHA
    6. Performing post-upgrade tasks
      1.  
        Optional configuration steps
      2.  
        Re-joining the backup boot disk group into the current disk group
      3.  
        Reverting to the backup boot disk group after an unsuccessful upgrade
      4.  
        Recovering VVR if automatic upgrade fails
      5. Post-upgrade tasks when VCS agents for VVR are configured
        1.  
          Unfreezing the service groups
        2.  
          Restoring the original configuration when VCS agents are configured
        3.  
          CVM master node needs to assume the logowner role for VCS managed VVR resources
      6.  
        Resetting DAS disk names to include host name in FSS environments
      7.  
        Upgrading disk layout versions
      8.  
        Upgrading VxVM disk group versions
      9.  
        Updating variables
      10.  
        Setting the default disk group
      11. About enabling LDAP authentication for clusters that run in secure mode
        1.  
          Enabling LDAP authentication for clusters that run in secure mode
      12.  
        Verifying the Storage Foundation and High Availability upgrade
  4. Section IV. Post-installation tasks
    1. Performing post-installation tasks
      1.  
        Switching on Quotas
      2. About configuring authentication for SFDB tools
        1.  
          Configuring vxdbd for SFDB tools authentication
  5. Section V. Adding and removing nodes
    1. Adding a node to SFHA clusters
      1.  
        About adding a node to a cluster
      2.  
        Before adding a node to a cluster
      3.  
        Adding a node to a cluster using the Veritas InfoScale installer
      4. Adding the node to a cluster manually
        1.  
          Starting Veritas Volume Manager (VxVM) on the new node
        2.  
          Configuring cluster processes on the new node
        3. Setting up the node to run in secure mode
          1.  
            Setting up SFHA related security configuration
        4.  
          Starting fencing on the new node
        5.  
          Configuring the ClusterService group for the new node
      5. Adding a node using response files
        1.  
          Response file variables to add a node to a SFHA cluster
        2.  
          Sample response file for adding a node to a SFHA cluster
      6. Configuring server-based fencing on the new node
        1.  
          Adding the new node to the vxfen service group
      7.  
        After adding the new node
      8.  
        Adding nodes to a cluster that is using authentication for SFDB tools
      9.  
        Updating the Storage Foundation for Databases (SFDB) repository after adding a node
    2. Removing a node from SFHA clusters
      1. Removing a node from a SFHA cluster
        1.  
          Verifying the status of nodes and service groups
        2.  
          Deleting the departing node from SFHA configuration
        3.  
          Modifying configuration files on each remaining node
        4.  
          Removing the node configuration from the CP server
        5.  
          Removing security credentials from the leaving node
        6.  
          Unloading LLT and GAB and removing Veritas InfoScale Availability or Enterprise on the departing node
        7.  
          Updating the Storage Foundation for Databases (SFDB) repository after removing a node
  6. Section VI. Configuration and upgrade reference
    1. Appendix A. Installation scripts
      1.  
        Installation script options
      2.  
        About using the postcheck option
    2. Appendix B. SFHA services and ports
      1.  
        About InfoScale Enterprise services and ports
    3. Appendix C. Configuration files
      1.  
        About the LLT and GAB configuration files
      2.  
        About the AMF configuration files
      3. About the VCS configuration files
        1.  
          Sample main.cf file for VCS clusters
        2.  
          Sample main.cf file for global clusters
      4.  
        About I/O fencing configuration files
      5. Sample configuration files for CP server
        1.  
          Sample main.cf file for CP server hosted on a single node that runs VCS
        2.  
          Sample main.cf file for CP server hosted on a two-node SFHA cluster
        3.  
          Sample CP server configuration (/etc/vxcps.conf) file output
    4. Appendix D. Configuring the secure shell or the remote shell for communications
      1.  
        About configuring secure shell or remote shell communication modes before installing products
      2.  
        Manually configuring passwordless ssh
      3.  
        Setting up ssh and rsh connection using the installer -comsetup command
      4.  
        Setting up ssh and rsh connection using the pwdutil.pl utility
      5.  
        Restarting the ssh session
      6.  
        Enabling rsh for Linux
    5. Appendix E. Sample SFHA cluster setup diagrams for CP server-based I/O fencing
      1. Configuration diagrams for setting up server-based I/O fencing
        1.  
          Two unique client clusters served by 3 CP servers
        2.  
          Client cluster served by highly available CPS and 2 SCSI-3 disks
        3.  
          Two node campus cluster served by remote CP server and 2 SCSI-3 disks
        4.  
          Multiple client clusters served by highly available CP server and 2 SCSI-3 disks
    6. Appendix F. Configuring LLT over UDP
      1. Using the UDP layer for LLT
        1.  
          When to use LLT over UDP
      2. Manually configuring LLT over UDP using IPv4
        1.  
          Broadcast address in the /etc/llttab file
        2.  
          The link command in the /etc/llttab file
        3.  
          The set-addr command in the /etc/llttab file
        4.  
          Selecting UDP ports
        5.  
          Configuring the netmask for LLT
        6.  
          Configuring the broadcast address for LLT
        7.  
          Sample configuration: direct-attached links
        8.  
          Sample configuration: links crossing IP routers
      3. Using the UDP layer of IPv6 for LLT
        1.  
          When to use LLT over UDP
      4. Manually configuring LLT over UDP using IPv6
        1.  
          Sample configuration: direct-attached links
        2.  
          Sample configuration: links crossing IP routers
      5. About configuring LLT over UDP multiport
        1.  
          Manually configuring LLT over UDP multiport
        2.  
          Enabling LLT ports in firewall
        3.  
          Disabling the UDP multiport feature
    7. Appendix G. Using LLT over RDMA
      1.  
        Using LLT over RDMA
      2.  
        About RDMA over RoCE or InfiniBand networks in a clustering environment
      3.  
        How LLT supports RDMA capability for faster interconnects between applications
      4.  
        Using LLT over RDMA: supported use cases
      5. Configuring LLT over RDMA
        1.  
          Choosing supported hardware for LLT over RDMA
        2.  
          Installing RDMA, InfiniBand or Ethernet drivers and utilities
        3. Configuring RDMA over an Ethernet network
          1.  
            Enable RDMA over Converged Ethernet (RoCE)
          2.  
            Configuring RDMA and Ethernet drivers
          3.  
            Configuring IP addresses over Ethernet Interfaces
        4. Configuring RDMA over an InfiniBand network
          1.  
            Configuring RDMA and InfiniBand drivers
          2.  
            Configuring the OpenSM service
          3.  
            Configuring IP addresses over InfiniBand Interfaces
        5. Tuning system performance
          1.  
            Tuning the CPU frequency
          2.  
            Tuning the boot parameter settings
        6. Manually configuring LLT over RDMA
          1.  
            Broadcast address in the /etc/llttab file
          2.  
            The link command in the /etc/llttab file
          3.  
            Selecting UDP ports
          4.  
            Configuring the netmask for LLT
          5.  
            Sample configuration: direct-attached links
        7.  
          LLT over RDMA sample /etc/llttab
        8.  
          Verifying LLT configuration
      6. Troubleshooting LLT over RDMA
        1.  
          IP addresses associated to the RDMA NICs do not automatically plumb on node restart
        2.  
          Ping test fails for the IP addresses configured over InfiniBand interfaces
        3.  
          After a node restart, by default the Mellanox card with Virtual Protocol Interconnect (VPI) gets configured in InfiniBand mode
        4.  
          The LLT module fails to start

Configuring the CP server using the installer program

Use the configcps option available in the installer program to configure the CP server.

Perform one of the following procedures:

For CP servers on single-node VCS cluster:

See “To configure the CP server on a single-node VCS cluster”.

For CP servers on an SFHA cluster:

See “To configure the CP server on an SFHA cluster”.

To configure the CP server on a single-node VCS cluster

  1. Verify that the VRTScps RPM is installed on the node.
  2. Run the installer program with the configcps option.
    # /opt/VRTS/install/installer  -configcps
  3. Installer checks the cluster information and prompts if you want to configure CP Server on the cluster.

    Enter y to confirm.

  4. Select an option based on how you want to configure Coordination Point server.
    1) Configure Coordination Point Server on single node VCS system
    2) Configure Coordination Point Server on SFHA cluster
    3) Unconfigure Coordination Point Server
  5. Enter the option: [1-3,q] 1.

    The installer then runs the following preconfiguration checks:

    • Checks to see if a single-node VCS cluster is running with the supported platform.

      The CP server requires VCS to be installed and configured before its configuration.

    The installer automatically installs a license that is identified as a CP server-specific license. It is installed even if a VCS license exists on the node. CP server-specific key ensures that you do not need to use a VCS license on the single-node. It also ensures that Veritas Operations Manager (VOM) identifies the license on a single-node coordination point server as a CP server-specific license and not as a VCS license.

  6. Restart the VCS engine if the single-node only has a CP server-specific license.
    A single node coordination point server will be configured and 
    VCS will be started in one node mode, do you want to 
    continue?  [y,n,q]  (y)
  7. Communication between the CP server and application clusters is secured by using the HTTPS protocol from release 6.1.0 onwards.

    Enter the name of the CP Server.

    Enter the name of the CP Server: [b]   cps1
  8. Enter valid virtual IP addresses for the CP Server with HTTPS-based secure communication. A CP Server can be configured with more than one virtual IP address.
    Enter Virtual IP(s) for the CP server for HTTPS, 
    separated by a space:  [b]  10.200.58.231 10.200.58.232 
    10.200.58.233

    Note:

    Ensure that the virtual IP address of the CP server and the IP address of the NIC interface on the CP server belongs to the same subnet of the IP network. This is required for communication to happen between client nodes and CP server.

  9. Enter the corresponding CP server port number for each virtual IP address or press Enter to accept the default value (443).
    Enter the default port '443' to be used for all the 
    virtual IP addresses for HTTPS communication or assign the 
    corresponding port number in the range [49152, 65535] for 
    each virtual IP address. Ensure that each port number is 
    separated by a single 
    space: [b]  (443) 54442 54443 54447
  10. Enter the absolute path of the CP server database or press Enter to accept the default value (/etc/VRTScps/db).
    Enter absolute path of the database: [b] (/etc/VRTScps/db)
    
  11. Verify and confirm the CP server configuration information.
    CP Server configuration verification:
    -------------------------------------------------
    CP Server Name:  cps1
    CP Server Virtual IP(s) for HTTPS: 10.200.58.231, 10.200.58.232,
    10.200.58.233
    CP Server Port(s) for HTTPS: 54442, 54443, 54447
    CP Server Database Dir: /etc/VRTScps/db
    
    -------------------------------------------------
    
    Is this information correct? [y,n,q,?]  (y)
  12. The installer proceeds with the configuration process, and creates a vxcps.conf configuration file.
    Successfully generated the /etc/vxcps.conf configuration file
    Successfully created directory /etc/VRTScps/db on node
    
  13. Configure the CP Server Service Group (CPSSG) for this cluster.
    Enter how many NIC resources you want to configure (1 to 2): 2

    Answer the following questions for each NIC resource that you want to configure.

  14. Enter a valid network interface for the virtual IP address for the CP server process.
    Enter a valid network interface on sys1 for NIC resource - 1: eth0
    Enter a valid network interface on sys1 for NIC resource - 2:  eth1
  15. Enter the NIC resource you want to associate with the virtual IP addresses.
    Enter the NIC resource you want to associate with the virtual IP 10.200.58.231 (1 to 2): 1
    Enter the NIC resource you want to associate with the virtual IP 10.200.58.232 (1 to 2): 2
    
  16. Enter the networkhosts information for each NIC resource.
    Veritas recommends configuring NetworkHosts attribute to ensure NIC resource
    to be always online
    
    Do you want to add NetworkHosts attribute for the NIC device eth0
    on system sys1? [y,n,q] y
    Enter a valid IP address to configure NetworkHosts for NIC eth0
    on system sys1: 10.200.56.22
    Do you want to add another Network Host? [y,n,q] n
  17. Enter the netmask for virtual IP addresses. If you entered an IPv6 address, enter the prefix details at the prompt.
    Enter the netmask for virtual IP for 
    HTTPS 192.169.0.220: (255.255.252.0)
    
  18. Installer displays the status of the Coordination Point Server configuration. After the configuration process has completed, a success message appears.
    For example:
    Updating main.cf with CPSSG service group.. Done
    Successfully added the CPSSG service group to VCS configuration.
    Trying to bring CPSSG service group
    ONLINE and will wait for upto 120 seconds
    
    The Veritas coordination point server is ONLINE
    
    The Veritas coordination point server has 
    been configured on your system.
    
  19. Run the hagrp -state command to ensure that the CPSSG service group has been added.
    For example:
    # hagrp -state CPSSG
    #Group Attribute System Value
    CPSSG State.... |ONLINE|
    

    It also generates the configuration file for CP server (/etc/vxcps.conf). The vxcpserv process and other resources are added to the VCS configuration in the CP server service group (CPSSG).

For information about the CPSSG, refer to the Cluster Server Administrator's Guide.

To configure the CP server on an SFHA cluster

  1. Verify that the VRTScps RPM is installed on each node.
  2. Ensure that you have configured passwordless ssh or rsh on the CP server cluster nodes.
  3. Run the installer program with the configcps option.
    # ./installer -configcps
  4. Specify the systems on which you need to configure the CP server.
  5. Installer checks the cluster information and prompts if you want to configure CP Server on the cluster.

    Enter y to confirm.

  6. Select an option based on how you want to configure Coordination Point server.
     
    1)  Configure Coordination Point Server on single node VCS system
    2)  Configure Coordination Point Server on SFHA cluster
    3)  Unconfigure Coordination Point Server
    
  7. Enter 2 at the prompt to configure CP server on an SFHA cluster.

    The installer then runs the following preconfiguration checks:

    • Checks to see if an SFHA cluster is running with the supported platform.

      The CP server requires SFHA to be installed and configured before its configuration.

  8. Communication between the CP server and application clusters is secured by HTTPS from Release 6.1.0 onwards.

    Enter the name of the CP server.

    Enter the name of the CP Server: [b]  cps1
  9. Enter valid virtual IP addresses for the CP Server. A CP Server can be configured with more than one virtual IP address.
    Enter Virtual IP(s) for the CP server for HTTPS,
     separated by a space: [b] 10.200.58.231 10.200.58.232 10.200.58.233
    
  10. Enter the corresponding CP server port number for each virtual IP address or press Enter to accept the default value (443).
    Enter the default port '443' to be used for all the virtual IP addresses
    for HTTPS communication or assign the corresponding port number in the range [49152,
    65535] for each virtual IP address. Ensure that each port number is separated by
    a single space: [b] (443) 65535 65534 65537
  11. Enter absolute path of the database.
    CP Server uses an internal database to store the client information.
    As the CP Server is being configured on SFHA cluster, the database should reside 
    on shared storage with vxfs file system. Please refer to documentation for
    information on setting up of shared storage for CP server database.
    Enter absolute path of the database: [b] /cpsdb
  12. Verify and confirm the CP server configuration information.
    CP Server configuration verification:
    
    CP Server Name: cps1
    CP Server Virtual IP(s) for HTTPS: 10.200.58.231, 10.200.58.232,
    10.200.58.233
    CP Server Port(s) for HTTPS: 65535, 65534, 65537
    CP Server Database Dir: /cpsdb
    
    Is this information correct? [y,n,q,?] (y)
    
  13. The installer proceeds with the configuration process, and creates a vxcps.conf configuration file.
    Successfully generated the /etc/vxcps.conf configuration file
    Copying configuration file /etc/vxcps.conf to sys0....Done
    Creating mount point /cps_mount_data on sys0. ... Done
    Copying configuration file /etc/vxcps.conf to sys0. ... Done
    Press Enter to continue.
  14. Configure CP Server Service Group (CPSSG) for this cluster.
    Enter how many NIC resources you want to configure (1 to 2): 2
    
    Answer the following questions for each NIC resource that you want to configure.
  15. Enter a valid network interface for the virtual IP address for the CP server process.
    Enter a valid network interface on sys1 for NIC resource - 1: eth0
    Enter a valid network interface on sys1 for NIC resource - 2: eth1
  16. Enter the NIC resource you want to associate with the virtual IP addresses.
    Enter the NIC resource you want to associate with the virtual IP 10.200.58.231 (1 to 2): 1
    Enter the NIC resource you want to associate with the virtual IP 10.200.58.232 (1 to 2): 2
    
  17. Enter the networkhosts information for each NIC resource.
    Veritas recommends configuring NetworkHosts attribute to ensure NIC resource
    to be always online
    
    Do you want to add NetworkHosts attribute for the NIC device eth0
    on system sys1? [y,n,q] y
    Enter a valid IP address to configure NetworkHosts for NIC eth0
    on system sys1: 10.200.56.22
    Do you want to add another Network Host? [y,n,q] n
    Do you want to apply the same NetworkHosts for all systems? [y,n,q] (y)
  18. Enter the netmask for virtual IP addresses. If you entered an IPv6 address, enter the prefix details at the prompt.
    Enter the netmask for virtual IP for 
    HTTPS 192.168.0.111: (255.255.252.0)
    
    
  19. Configure a disk group for CP server database. You can choose an existing disk group or create a new disk group.
    Veritas recommends to use the disk group that has at least
    two disks on which mirrored volume can be created.
    Select one of the options below for CP Server database disk group:
    
    1)  Create a new disk group
    2)  Using an existing disk group
    
    Enter the choice for a disk group: [1-2,q]  2
    
  20. Select one disk group as the CP Server database disk group.
    Select one disk group as CP Server database disk group: [1-3,q] 3
    1)  mycpsdg
    2)  cpsdg1
    3)  newcpsdg
    
  21. Select the CP Server database volume.

    You can choose to use an existing volume or create new volume for CP Server database. If you chose newly created disk group, you can only choose to create new volume for CP Server database.

    Select one of the options below for CP Server database volume:
     1)  Create a new volume on disk group newcpsdg
     2)  Using an existing volume on disk group newcpsdg
  22. Enter the choice for a volume: [1-2,q] 2.
  23. Select one volume as CP Server database volume [1-1,q] 1
    1) newcpsvol
    
  24. After the VCS configuration files are updated, a success message appears.
    For example:
    Updating main.cf with CPSSG service group .... Done
    Successfully added the CPSSG service group to VCS configuration.
  25. If the cluster is secure, installer creates the softlink /var/VRTSvcs/vcsauth/data/CPSERVER to /cpsdb/CPSERVER and check if credentials are already present at /cpsdb/CPSERVER. If not, installer creates credentials in the directory, otherwise, installer asks if you want to reuse exsting credentials.
    Do you want to reuse these credentials? [y,n,q] (y)
    
  26. After the configuration process has completed, a success message appears.
    For example:
    Trying to bring CPSSG service group ONLINE and will wait for upto 120 seconds
    The Veritas Coordination Point Server is ONLINE
    The Veritas Coordination Point Server has been configured on your system.
    
  27. Run the hagrp -state command to ensure that the CPSSG service group has been added.
    For example:
    # hagrp -state CPSSG
    #Group Attribute System Value
    CPSSG State cps1 |ONLINE|
    CPSSG State cps2 |OFFLINE|
    
    

    It also generates the configuration file for CP server (/etc/vxcps.conf). The vxcpserv process and other resources are added to the VCS configuration in the CP server service group (CPSSG).

For information about the CPSSG, refer to the Cluster Server Administrator's Guide.