< Previous  | TOC | Index | Next  >

Getting your VCS installation and configuration
information ready

The VCS installation and configuration program prompts you for information about certain VCS components. When you perform the installation, prepare the following information.

• To install VCS depots you need:

   

  The system names where you plan to install VCS	Example: north, south
  The required license keys	Keys include:  A valid site license key A valid demo license key A valid license key for VCS global clusters See Obtaining VCS license keys
  To decide whether to install:  the required VCS depots all the VCS depots	Install only the required depots if you do not want to configure any optional components or features.  The default option is to install all depots.  See Optional VCS depots

• To configure the Veritas Cluster Server you need:

   

  The name of the cluster	The cluster name must begin with a letter of the alphabet. The cluster name can contain only the characters "a" through "z", "A" through "Z", the numbers "0" through "9", the hyphen "-", and the underscore "_".  Example: vcs_cluster27
  A unique ID number for the cluster	A number in the range of 0-65535. Within the site that contains the cluster, each cluster must have a unique ID.   Example: 7
  The device names of the NICs used by the private networks among systems	Do not use the network interface card that is used for the public network, which is typically lan0.  Example: lan1, lan2

• To configure VCS clusters in secure mode (optional), you need:

   

  For automatic mode (default)	The name of the Root Broker system Example: east See Symantec Product Authentication Service Access to the Root Broker system without use of a password.
  For semiautomatic mode using encrypted files	The path for the encrypted files that you get from the Root Broker administrator.  See Creating encrypted files for Symantec Product Authentication Service.
  For semiautomatic mode without using encrypted files	The fully-qualified hostname (FQDN) of the Root Broker . (e.g. east.symantecexample.com) The above example given posits a system in the (DNS) domain symantecexample.com with the unqualified hostname east, which is designated as the Root Broker. The root broker's security domain (e.g. root@east.symantecexample.com) The root broker's port (e.g. 2821) The path to the local root hash (e.g. /var/tmp/privatedir/root_hash) The authentication broker's principal name on the each cluster node (e.g. north.symantecexample.com and south.symantecexample.com)

• To add VCS users, which is not required if you configure your cluster in secure mode, you need:

   

  User names	Example: smith
  User passwords	Enter the password at the prompt.
  To decide user privileges	Users have three levels of privileges: A=Administrator, O=Operator, or G=Guest.  Example: A

• To configure the Cluster Management Console to locally manage this cluster (optional), you need:

   

  The name of the public NIC for each node in the cluster	The device name for the NIC that provides public network access.   Example: lan0
  A virtual IP address of the NIC for the Cluster Management Console	This virtual IP address becomes a resource for use by the ClusterService group that includes the Cluster Management Console. The "Cluster Virtual IP address" can fail over to another cluster system, making the Web Console highly available.  Example: 10.10.12.1
  The netmask for the virtual IP address	The subnet used with the virtual address.  Example: 255.255.240.0
  NetworkHosts IP addresses	IP addresses that are used to check the adapter connections.  Example: 10.10.12.2

• To configure the Cluster Management Console cluster connector (optional), you need:

   

  The management server network address for Cluster Management Console	The Cluster Management Console cluster connector requires the management server network address.  See Veritas Cluster Management Console  Example: mgmtserver1.symantecexample.com
  A Cluster Management Console service account password	You must have set this account password while installing the management server.
  The root hash of the management server	You can use vssat showbrokerhash command and copy the root hash of the management server.

• To configure SMTP email notification (optional), you need:

   

  The domain-based address of the SMTP server	The SMTP server sends notification emails about the events within the cluster.  Example: smtp.symantecexample.com
  The email address of each SMTP recipient to be notified	Example: john@symantecexample.com
  To decide the minimum severity of events for SMTP email notification	Events have four levels of severity: I=Information, W=Warning, E=Error, and S=SevereError.  Example: E

• To configure SNMP trap notification (optional), you need:

   

  The port number for the SNMP trap daemon	The default port number is 162.
  The system name for each SNMP console	Example: saturn
  To decide the minimum severity of events for SNMP trap notification	Events have four levels of severity: I=Information, W=Warning, E=Error, and S=SevereError.  Example: E

• To configure global clusters (optional), you need:

   

  The name of the public NIC	You can use the same NIC that you configured for the ClusterService group. Otherwise, specify appropriate values for the NIC.  Example: lan0
  The virtual IP address of the NIC	You can use the same virtual IP address that you configured for the ClusterService group. Otherwise, specify appropriate values for the virtual IP address.  Example: 10.10.12.1
  The netmask for the virtual IP address	You can use the same netmask as configured for the ClusterService group. Otherwise, specify appropriate values for the netmask.  Example: 255.255.240.0
  The NetworkHosts IP addresses	You can use the same NetworkHosts IP address as configured for the ClusterService group. Otherwise, specify appropriate values for the netmask when you are prompted.  Example: 10.10.12.2

• To configure I/O fencing:

   

  The names of the three disks that form the coordinator disk group	Example: c1t1d0, c2t1d0, c3t1d0
  The DMP nodes names for each disk in the coordinator disk group (if using DMP)	Example: /dev/vx/dmp