Installing VCS 4.1 Manually

Install VCS manually by using the swinstall utility.

Adding a License Key

After all packages have been installed on the cluster node, use the vxlicinst command to add the VCS license key on each system:

If you have VCS already installed and configured and you are using a demo license, you can replace the demo license using the procedure Replacing a VCS Demo License with a Permanent License.

Checking Licensing Information on the System

You can use the utility vxlicrep to display information about all VERITAS licenses on a system. For example, enter:

From the output, you can determine the license key, the type of license, the product for which it applies, and its expiration date, if any. Demo keys have expiration dates, permanent keys and site keys do not.

Configuring LLT and GAB

1. Create the file /etc/llthosts on the new system. You must also update it on each of the current systems in the cluster. For example, suppose you are adding east to a cluster consisting of north and south:
   1. If the file on one of the existing systems resembles:
   
       0 north
       1 south
   2. The updated file for all systems, including the new one, would resemble:
   
       0 north
       1 south
       2 east
2. Create the file /etc/llttab on the new system, making sure that line beginning "set-node" specifies the new system. Refer to /etc/llttab; the file /etc/llttab on an existing system can serve as a guide. The following example describes a system where system east is the new system on cluster number 2:
     set-node east
     set-cluster 2
     link lan1 /dev/lan:1 - ether - -
     link lan2 /dev/lan:2 - ether - -
3. On the new system, run the command:
     # /sbin/lltconfig -c
4. Create the file /etc/gabtab on the new system.
   1. If the /etc/gabtab file on the existing systems resembles:
   
       /sbin/gabconfig -c

   Then the file on the new node should be the same, although it is recommended to use the -c -nN option, where N is the number of cluster systems.

   2. If the /etc/gabtab file on the existing systems resembles:
   
       /sbin/gabconfig -c -n2

   Then, the file on all systems, including the new system, should change to reflect the change in the number of cluster systems. For example, the new on each system should resemble:

   
       /sbin/gabconfig -c -n3

   Refer to /etc/gabtab. The -n flag indicates to VCS the number of systems required to be ready to form a cluster before VCS starts.

   3. If you are adding a system to a cluster that has a heartbeat disk configured, then the new system should have access to the heartbeat disk. It requires an /etc/gabtab file that configures heartbeating, just as do the existing nodes. For example, the new /etc/gabtab file for each system may resemble:
   
       /sbin/gabdiskhb -a /dev/vg01/lvol1 -s 0 -p a
       /sbin/gabdiskhb -a /dev/vg01/lvol1 -s 128 -p h
       /sbin/gabconfig -c -n3

   SeeConfiguring Membership Heartbeat Regions on Disk (optional).

5. On the new system, run the command, to configure GAB:
     # /sbin/gabconfig -c
6. On the new system, run the command:
     # /sbin/gabconfig -a

   The output should indicate that Port a membership shows all nodes including the new node. The output should resemble:

   
     GAB Port Memberships
     ====================================
     Port a gen a3640003 membership 012

   Refer to Verifying GAB.

7. Run the same command on the other nodes (north and south) to verify that the
   Port a membership includes the new node:
     # /sbin/gabconfig -a
     GAB Port Memberships
     ====================================
     Port a gen a3640003 membership 012
     Port h gen fd570002 membership 01
     Port h gen fd570002    visible ; 2
8. On one of the existing systems in the cluster,
   1. Enter the command:
   
       # haconf -makerw
   2. Add the new system, for example, east, to the cluster:
   
       # hasys -add east
   3. If necessary, modify any new system attributes.
   4. Enter the command:
   
       # haconf -dump -makero
9. From the new system start VCS with the new system added to the cluster:
     # hastart
10. Run the GAB configuration command on each node to verify that port a and port h include the new node in the membership:
      # /sbin/gabconfig -a
      GAB Port Memberships
      ===================================
      Port a gen a3640003 membership 012
      Port h gen fd570002 membership 012