uses two components LLT and GAB to share data over private networks among systems. These components provide the performance and reliability required by VCS.
LLT(Low Latency Transport) provides fast, kernel-to-kernel communications,and monitors network connections. The system administrator configures LLT by creating the configuration files /etc/llthosts, which lists all the system in the cluster, and /etc/llttab, which descrbes the local system’s private network links to the other system in the cluster.
GAB(group membership and atomic broadcast) provides the global message order required to maintain a synchronized state among the systems and monitors disk communications such as that required by the VCS heartbeat utility.The system administrator configures GAB driver by creating a configuration file(/etc/gabtab)
Verifying LLT and GAB configuration files
The following files are required by the VCS communication services LLT and GAB.
/etc/llthosts
The file llthosts is a database containing one entry per system that links the LLT system ID (in the first column) with the LLT host name This file is identical on each system in the cluster.
For example the file /etc/llthosts contains entries that resemble:
0 north
1 south
/etc/llttab
The file llttab contains information that is derived during installation and used by the utility lltconfig . After installation ,this file lists the private network links that correspond to the specific system.
For example the file /etc/llttab contains entries that resemble:
Set-node north
Set-cluster 2
Link qfe:0 /dev/qfe:0 – ether - -
Link qfe:1 /dev/qfe:1 – ether - -
The first line identifies the system. The second line identifies the cluster---the cluster ID you entered during installation. The next two lines beginning with the link command, identify the two network cards used by the LLT protocol.
Use hacf to verify(check syntax of) the main.cf and the type definition file,types,cf.
Hacf –verify config_directory
To install a new license
Cd /opt/VRTS/bin
#./vxlicinst –k xxxxxxxxxxxxxxxxx
To update licensing information in a running cluster
1、 updae system-level licensing information on all nodes in the cluster:
#hasy – updatelic -all
2、 update cluster-level licensing information:
#aclus – updatelic
To start VCS
# hastart [-stale|-force]
The option –stale instructs the engine to treat the local configuration as stale even if it is valid. The option – force instructs the engine to treat a stale but otherwise valid local configuration as valid.
To start VCS when all systems are in ADMIN_WAIT
Run the following command from any system in the cluster to force VCS to use the configuration file from the system specified by the variable system:
#hasys – force system
To start VCS on a single node
#hastart –onenode
To start VCS as a time-sharing process
#hastart –ts
Stopping VCS
The hastop command stops HAD and related processes. This command includes the following options:
Hastop –all [-force]
Hastop [-help]
Hastop –local [-force |-evacuate|-noautodisable]
The option –all stops HAD on all systems in the cluster and take all service groups offline.
The option –local stops HAD on the system on which you typed the command.
The option –force allows HAD to be stopped without taking service groups offline on the system
The option –evacuate when combined with –local or –sys migrates the system’s active service groups to another system in the cluster, before the system is stopped.
The option –noautodisable ensures that service groups that can run on the node where the hastop command was issued are not autodisabled.This option can be used with –evacuate but not with –force.
The option –sys stops HAD on the system you specified.
Log on to VCS
#halogin vcsusername password
To end a session for a host
#halogin –endsession hostname
To end all sessions
#halogin –endallsessions
setting the configuration to read/write
The commands to add modify and delete a user must be executed only as root, and only if the VCS configuration is in read/write mode.
To set the mode to read/write, type the following command from any system in the cluster
#haconf – makerw
When you have completed adding modifying and deleting users, reset the configuration to read only
#haconf –dump –makero
Adding a user
1、 the configuration to read/write mode:
#haconf –makerw
2 add the user
#hauser –add user [-priv
[ -group service_groups]]
Reset the configuration to read-only:
#haconf –dump –makero
Assigning and removing user privileges
To assign privileges to an administrator or operator
#hauser –addpriv user Administrator|Operator [-group service_groups]
To remove privileges from an administrator or operator
#hauser –delpriv user Administrator|Operator [-group service_groups]
Modifyling a user
#haconf –makerw
#hauser –update user
#haconf –dump –makero
Deleting a user
#haconf –makerw
#hauser –delpriv user Administrator|Operator [-group service_groups]
#hauser –delete user
#haconf –dump –makero
Displaying a user
#hauser –list
To display the privileges of all users
#hauser –display
To display the privileges of a specific user
#hauser –display user
Querying VCS
VCS enables you to query various cluster objects, includeing resources,service groups,
System, resource types,agents and cluster. You may enter query commands form. any system in the cluster. Command to display information on the VCS configuration or system states can be executed by all users: you do not need root privileges.
Querying services groups
To display the state of a service group on a system
#hagrp –state [service_group] [-sys system]
For a list of a service group is resources
#hagrp –resources service_group
For a list of a service group is dependencies
#hagrp –dep [service_group]
To display attributes of a system
#hagrp –display [service_group] [-attribute attribute] [-sys system]
