Cluster Server 7.3.1 Configuration and Upgrade Guide - Solaris

Last Published:
Product(s): InfoScale & Storage Foundation (7.3.1)
Platform: Solaris
  1. Section I. Configuring Cluster Server using the script-based installer
    1. I/O fencing requirements
      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 VCS clusters for data integrity
      1. About planning to configure I/O fencing
        1.  
          Typical VCS cluster configuration with disk-based I/O fencing
        2.  
        3.  
          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.  
          Setting up shared storage for the CP server database
        4.  
          Configuring the CP server using the installer program
        5. 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
        6. 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
        7.  
          Verifying the CP server configuration
    3. Configuring VCS
      1.  
        Overview of tasks to configure VCS using the product installer
      2.  
        Starting the software configuration
      3.  
        Specifying systems for configuration
      4.  
        Configuring the cluster name
      5.  
        Configuring private heartbeat links
      6.  
        Configuring the virtual IP of the cluster
      7.  
        Configuring VCS in secure mode
      8.  
        Setting up trust relationships for your VCS cluster
      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 VCS configuration
      15. Verifying and updating licenses on the system
        1.  
          Checking licensing information on the system
        2. Updating product licenses
          1.  
            Replacing a Veritas InfoScale Enterprise demo license with a permanent license
    4. Configuring VCS clusters for data integrity
      1. Setting up disk-based I/O fencing using installer
        1.  
          Initializing disks as VxVM disks
        2.  
          Configuring disk-based I/O fencing using installer
        3.  
          Refreshing keys or registrations on the existing coordination points for disk-based fencing using the installer
        4. 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
      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
  2. Section II. Automated configuration using response files
    1. Performing an automated VCS configuration
      1.  
        Configuring VCS using response files
      2.  
        Response file variables to configure VCS
      3.  
        Sample response file for configuring Cluster Server
    2. 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
      5.  
        Sample response file for configuring server-based I/O fencing
      6.  
        Response file variables to configure non-SCSI-3 I/O fencing
      7.  
        Sample response file for configuring non-SCSI-3 I/O fencing
      8.  
        Response file variables to configure majority-based I/O fencing
      9.  
        Sample response file for configuring majority-based I/O fencing
  3. Section III. Manual configuration
    1. Manually configuring VCS
      1.  
        About configuring VCS manually
      2. Configuring LLT manually
        1.  
          Setting up /etc/llthosts for a manual installation
        2.  
          Setting up /etc/llttab for a manual installation
        3.  
          About LLT directives in /etc/llttab file
        4.  
          Additional considerations for LLT for a manual installation
      3.  
        Configuring GAB manually
      4. Configuring VCS manually
        1.  
          Configuring the cluster UUID when creating a cluster manually
      5. Configuring VCS in single node mode
        1. Disabling LLT, GAB, and I/O fencing on a single node cluster
          1.  
            Disabling LLT, GAB, and I/O fencing on Oracle Solaris 11
        2. Enabling LLT, GAB, and I/O fencing on a single node cluster
          1.  
            Enabling LLT, GAB, and I/O fencing on Solaris 11
      6.  
        Starting LLT, GAB, and VCS after manual configuration
      7.  
        About configuring cluster using VCS Cluster Configuration wizard
      8.  
        Before configuring a VCS cluster using the VCS Cluster Configuration wizard
      9.  
        Launching the VCS Cluster Configuration wizard
      10.  
        Configuring a cluster by using the VCS cluster configuration wizard
      11.  
        Adding a system to a VCS cluster
      12. Modifying the VCS configuration
        1.  
          Configuring the ClusterService group
    2. Manually configuring the clusters for data integrity
      1. Setting up disk-based I/O fencing manually
        1.  
          Identifying disks to use as coordinator disks
        2.  
          Setting up coordinator disk groups
        3.  
          Creating I/O fencing configuration files
        4.  
          Modifying VCS configuration to use I/O fencing
        5.  
          Verifying I/O fencing configuration
      2. Setting up server-based I/O fencing manually
        1.  
          Preparing the CP servers manually for use by the VCS cluster
        2.  
          Generating the client key and certificates manually on the client nodes
        3. Configuring server-based fencing on the VCS 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
        4.  
          Sample /etc/vxfenmode file for majority-based fencing
  4. Section IV. Upgrading VCS
    1. Planning to upgrade VCS
      1.  
        About upgrading to VCS 7.3.1
      2.  
        Upgrading VCS in secure enterprise environments
      3.  
        Supported upgrade paths
      4.  
        Considerations for upgrading secure VCS 6.x clusters to VCS 7.3.1
      5.  
        Considerations for upgrading VCS to 7.3.1 on systems configured with an Oracle resource
      6.  
        Considerations for upgrading secure VCS clusters to VCS 7.3.1
      7.  
        Considerations for upgrading CP servers
      8.  
        Considerations for upgrading CP clients
      9.  
        Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches
    2. Performing a VCS upgrade using the installer
      1.  
        Before upgrading VCS using the script-based installer
      2.  
        Upgrading VCS using the product installer
      3.  
        Upgrading to 2048 bit key and SHA256 signature certificates
      4. Tasks to perform after upgrading to 2048 bit key and SHA256 signature certificates
        1.  
          Deleting certificates of non-root users after upgrading to 2048 bit key and SHA256 signature certificates
        2.  
          Re-establishing WAC communication in global clusters after upgrading to 2048 bit key and SHA256 signature certificates
        3.  
          Re-establishing CP server and CP client communication after upgrading to 2048 bit key and SHA256 signature certificates
        4.  
          Re-establishing trust with Steward after upgrading to 2048 bit key and SHA256 signature certificates
      5.  
        Upgrading Steward to 2048 bit key and SHA256 signature certificates
    3. Performing an online upgrade
      1.  
        Limitations of online upgrade
      2.  
        Upgrading VCS online using the installer
    4. Performing a rolling upgrade of VCS
      1.  
        About rolling upgrade
      2.  
        Performing a rolling upgrade using the product installer
      3.  
        About rolling upgrade with local zone on Solaris 11
    5. Performing a phased upgrade of VCS
      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
    6. Performing an automated VCS upgrade using response files
      1.  
        Upgrading VCS using response files
      2.  
        Response file variables to upgrade VCS
      3.  
        Sample response file for full upgrade of VCS
      4.  
        Sample response file for rolling upgrade of VCS
    7. Upgrading VCS using Live Upgrade and Boot Environment upgrade
      1.  
        About ZFS Boot Environment (BE) upgrade
      2.  
        Supported upgrade paths for Boot Environment upgrade
      3. Performing Boot Environment upgrade on Solaris 11 systems
        1.  
          Creating a new Solaris 11 BE on the primary boot disk
        2.  
          Upgrading VCS using the installer for upgrading BE on Solaris 11
        3.  
          Completing the VCS upgrade on BE on Solaris 11
        4.  
          Verifying Solaris 11 BE upgrade
        5. Administering BEs on Solaris 11 systems
          1.  
            Reverting to the primary BE on a Solaris 11 system
  5. Section V. Adding and removing cluster nodes
    1. Adding a node to a single-node cluster
      1. Adding a node to a single-node cluster
        1. Setting up a node to join the single-node cluster
          1.  
            Installing VxVM or VxFS if necessary
        2.  
          Installing and configuring Ethernet cards for private network
        3.  
          Configuring the shared storage
        4.  
          Bringing up the existing node
        5.  
          Creating configuration files
        6.  
          Starting LLT and GAB
        7.  
          Reconfiguring VCS on the existing node
        8.  
          Verifying configuration on both nodes
    2. Adding a node to a multi-node VCS cluster
      1.  
        Adding nodes using the VCS installer
      2. Manually adding a node to a cluster
        1.  
          Setting up the hardware
        2.  
          Installing the VCS software manually when adding a node
        3. Setting up the node to run in secure mode
          1.  
            Configuring the authentication broker on node sys5
        4.  
          Configuring LLT and GAB when adding a node to the cluster
        5. Configuring I/O fencing on the new node
          1.  
            Preparing to configure I/O fencing on the new node
          2. Configuring server-based fencing on the new node
            1.  
              Adding the new node to the vxfen service group
          3.  
            Starting I/O fencing on the new node
        6.  
          Adding the node to the existing cluster
        7.  
          Starting VCS and verifying the cluster
        8. Adding a node using response files
          1.  
            Response file variables to add a node to a VCS cluster
          2.  
            Sample response file for adding a node to a VCS cluster
    3. Removing a node from a VCS cluster
      1. Removing a node from a VCS cluster
        1.  
          Verifying the status of nodes and service groups
        2.  
          Deleting the departing node from VCS 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
  6. Section VI. Installation reference
    1. Appendix A. Services and ports
      1.  
        About InfoScale Enterprise services and ports
    2. Appendix B. 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
      6.  
        Packaging related SMF services on Solaris 11
      7. Tuning LLT variables for FSS environments
        1.  
          Tuning LLT variables for Ethernet links
    3. Appendix C. 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. Manually configuring LLT over UDP using IPv6
        1.  
          The link command in the /etc/llttab file
        2.  
          The set-addr command in the /etc/llttab file
        3.  
          Selecting UDP ports
        4.  
          Sample configuration: direct-attached links
        5.  
          Sample configuration: links crossing IP routers
      4.  
        LLT over UDP sample /etc/llttab
    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 and disabling rsh for Solaris
    5. Appendix E. Installation script options
      1.  
        Installation script options
    6. Appendix F. Troubleshooting VCS configuration
      1.  
        Restarting the installer after a failed network connection
      2.  
        Cannot launch the cluster view link
      3.  
        Starting and stopping processes for the Veritas InfoScale products
      4.  
        Installer cannot create UUID for the cluster
      5.  
        LLT startup script displays errors
      6.  
        The vxfentsthdw utility fails when SCSI TEST UNIT READY command fails
      7.  
        Issues during fencing startup on VCS cluster nodes set up for server-based fencing
    7. Appendix G. Sample VCS 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
    8. Appendix H. Reconciling major/minor numbers for NFS shared disks
      1. Reconciling major/minor numbers for NFS shared disks
        1.  
          Checking major and minor numbers for disk partitions
        2.  
          Checking the major and minor number for VxVM volumes
    9. Appendix I. Upgrading the Steward process
      1.  
        Upgrading the Steward process

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 package 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. For HTTPS-based communication, only IPv4 addresses are supported.
    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:  e1000g0
    Enter a valid network interface on sys1 for NIC resource - 2:  e1000g1
  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 e1000g0
    on system sys1? [y,n,q] y
    Enter a valid IP address to configure NetworkHosts for NIC e1000g0
    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.

    Note that if you are using HTTPS-based communication, only IPv4 addresses are supported.

    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 package 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. For HTTPS-based communication, only IPv4 addresses are supported.
    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: e1000g0
    Enter a valid network interface on sys1 for NIC resource - 2: e1000g1
  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 e1000g0
    on system sys1? [y,n,q] y
    Enter a valid IP address to configure NetworkHosts for NIC e1000g0
    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.

    Note that if you are using HTTPS-based communication, only IPv4 addresses are supported.

    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.