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: galaxy, nebula
  The required license keys	Depending on the type of installation, keys include: A valid site license key A valid demo license key A valid license key for VCS global clusters
  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.

• To configure Veritas Cluster Server you need:

  A name for 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 that the private networks use among systems	A network interface card that is not part of any aggregated interface, or an aggregated interface. 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 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.
  For semiautomatic mode without using encrypted files	The fully-qualified hostname (FQDN) of the Root Broker . (e.g. east.symantecexample.com) The given example puts 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 each cluster node (e.g. galaxy.symantecexample.com and nebula.symantecexample.com)

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

  User names	VCS usernames are restricted to 1024 characters. Example: smith
  User passwords	VCS passwords are restricted to 255 characters. 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 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 must specify appropriate values for the NIC. Example: lan0
  The virtual IP address of the NIC	You must specify appropriate values for the virtual IP address. Example: 192.168.1.16
  The netmask for the virtual IP address	You must specify appropriate values for the netmask. Example: 255.255.240.0
  The NetworkHosts IP addresses	You must specify appropriate values for the NetworkHosts IP address. Example: 192.168.1.15