VCS : Configuring Veritas Cluster and Configuration files

About the VCS configuration files

VCS configuration files include the following:

main.cf


The installer creates the VCS configuration file in the /etc/VRTSvcs/conf/config folder by default during the VCS configuration. The main.cf file contains the minimum information that defines the cluster and its nodes.

types.cf


The file types.cf, which is listed in the include statement in the main.cf file, defines the VCS bundled types for VCS resources. The file types.cf is also located in the folder /etc/VRTSvcs/conf/config.

Additional files similar to types.cf may be present if agents have been added, such as Oracletypes.cf.

/etc/default/vcsThis file stores the start and stop environment variables for VCS engine:
VCS_START—Defines the startup behavior for VCS engine after a system reboot. Valid values include:

  • 1—Indicates that VCS engine is enabled to start up.
  • 0—Indicates that VCS engine is disabled to start up.

VCS_STOP—Defines the shutdown behavior for VCS engine during a system shutdown. Valid values include:

  • 1—Indicates that VCS engine is enabled to shut down.
  • 0—Indicates that VCS engine is disabled to shut down.

The installer sets the value of these variables to 1 at the end of VCS configuration.  If you manually configured VCS, make sure you set the values of these environment variables to 1.

Note the following information about the VCS configuration file after installing and configuring VCS:

The cluster definition includes the cluster information that you provided during the configuration. This definition includes the cluster name, cluster address, and the names of users and administrators of the cluster.Notice that the cluster has an attribute UserNames. The installvcs program creates a user “admin” whose password is encrypted; the word “password” is the default password.

If you set up the optional I/O fencing feature for VCS, then the UseFence = SCSI3 attribute is present.

If you configured the cluster in secure mode, the main.cf includes the VxSS service group and “SecureClus = 1″ cluster attribute.

The installvcs program creates the ClusterService service group if you configured the virtual IP, SMTP, SNMP, or global cluster options.The service group also has the following characteristics:
The group includes the IP and NIC resources.
The service group also includes the notifier resource configuration, which is based on your input to installvcs program prompts about notification.
The installvcs program also creates a resource dependency tree.

If you set up global clusters, the ClusterService service group contains an Application resource, wac (wide-area connector). This resource’s attributes contain definitions for controlling the cluster in a global cluster environment.Refer to the Veritas Cluster Server Administrator’s Guide for information about managing VCS global clusters.

Configuring VCS

VCS configuration requires the types.cf and main.cf files on each system in the cluster. Both of the files are in the /etc/VRTSvcs/conf/config directory.

main.cf file The main.cf configuration file requires the following minimum essential elements:

  • An “include” statement that specifies the file, types.cf, which defines the VCS bundled agent resources.
  • The name of the cluster.
  • The name of the systems that make up the cluster.

types.cf file Note that the “include” statement in main.cf refers to the types.cf file. This text file describes the VCS bundled agent resources. During new installations, the types.cf file is automatically copied in to the /etc/VRTSvcs/conf/config directory.
When you manually install VCS, the file /etc/VRTSvcs/conf/config/main.cf contains only the line:

include “types.cf”

To configure VCS manually

Log on as superuser, and move to the directory that contains the configuration file:
# cd /etc/VRTSvcs/conf/config
Use vi or another text editor to edit the main.cf file, defining your cluster name and system names. Refer to the following example.An example main.cf for a two-node cluster:

include “types.cf”
cluster VCSCluster2 ( )
system galaxy ( )
system nebula ( )

An example main.cf for a single-node cluster:

include “types.cf”
cluster VCSCluster1 ( )
system sn1

Save and close the main.cf file.

Edit the following file on each node in the cluster to change the values of the VCS_START and the VCS_STOP environment variables to 1:

/etc/default/vcs

we respect your email privacy Check confirmation email for download link

You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

5 Comments on “VCS : Configuring Veritas Cluster and Configuration files”

  • Santosh
    5 October, 2011, 20:33

    Hi Ramdev,
    thanks for the Post,
    is it possible to post “How to configure a VCS (Step by step like config LLT, GAB etc..) and how to put a application in that system and how to add another node (2 node cluster)?
    I am bit confused in these things…
    Please help me, I am learning VCS from your site only…so help me to understand better.
    Thank you..

  • Yogesh Raheja
    6 October, 2011, 4:31

    Hi Santosh, While installing the cluster software, it will ask how much nodes do you want to configure in the cluster and related things. But you have to make sure that all the nodes which you are planning to put in the cluster configuration should ssh each other without password authentication. Try configuring a cluster your doubts will be cleared and put the issues which you got so that we can try our level best to guide you. (though these all configuration which you asked can also be done by changing the configuration files) but better to start with the easy way. As you wrote its your starting phase in the VCS.

  • 1 April, 2012, 7:13

    I have 2 node vcs5.0 running on solaris 8 .I want to reboot the server one by one . is this steps correct coorect ?

    I have 2 node vcs5.0 running on solaris 8 .I want to reboot the server one by one . is this steps correct coorect ?

    node1:/# hastatus -sum

    – SYSTEM STATE
    – System State Frozen

    A node1 RUNNING 0
    A node1 RUNNING 0

    – GROUP STATE
    – Group System Probed AutoDisabled State

    B ora9-rg node1 Y N ONLINE
    B ora9-rg node1 Y N OFFLINE

    – RESOURCES OFFLINING
    – Group Type Resource System IState

    F ora9-rg Application app9 node1 W_OFFLINE_PATH

    on node 2: hastop -local force ( once i get the status exited )
    #init 6 ( CAN i reboot the box )

    Similiarly on node 1

    Should i do the same or i need to move the hagrp switch ora9-rg to node2 ? the then stop the cluser local ,reboot the box ?pl advise

  • Ramdev
    1 April, 2012, 13:06

    @sekhar, please do service group switch over to the other node before you stop HA services and shutdown the machine. That way you will keep the services running without interruption.

  • Yogesh Raheja
    2 April, 2012, 11:23

    @Sekhar, and once you switch over the SG’s to other node dont forget to freeze that persistently to aviod automatic failback.

Leave a Comment

Join us at Linked-in Network -