Professional Documents
Culture Documents
http://www.datadisk.co.uk/html_docs/veritas/veritas_cluster.htm
Veritas Cluster
Cluster Information
Veritas cluster 4.0 can have upto 32 nodes.
LLT (Low-Latency Transport)
veritas uses a high-performance, low-latency protocol for cluster communications. LLT runs directly
on top of the data link provider interface (DLPI) layer ver ethernet and has several major junctions:
sending and receiving heartbeats
monitoring and transporting network traffic over multiple network links to every active system
within the cluster
load-balancing traffic over multiple links
maintaining the state of communication
providing a nonroutable transport mechanism for cluster communications.
Group membership services/Atomic Broadcast (GAB)
GAB provides the following:
Group Membership Services - GAB manitains the overall cluster membership by the way of
its Group Membership Sevices function. Heartbeats are used to determine if a system is active
member, joining or leaving a cluster. GAB determines what the position of a system is in within
a cluster.
Atomic Broadcast - Cluster configuration and status information is distributed dynamically to
all system within the cluster using GAB's Atomic Broadcast feature. Atomic Broadcast ensures
all active system receive all messages, for every resource and service group in the cluster.
Atomic means that all system receive the update, if one fails then the change is rolled back on
all systems.
High Availability Daemon (HAD)
The HAD tracks all changes within the cluster configuration and resource status by communicating
with GAB. Think of HAD as the manager of the resource agents. A companion daemon called
hashadow moniotrs HAD and if HAD fails hashadow attempts to restart it. Like wise if hashadow
daemon dies HAD will restart it. HAD maintains the cluster state information. HAD uses the main.cf
file to build the cluster information in memory and is also responsible for updating the configuration
in memory.
VCS architecture
So putting the above altogether we get:
Agents monitor resources on each system and provide status to HAD on the local system
1 of 4
3/1/14 11:26 AM
http://www.datadisk.co.uk/html_docs/veritas/veritas_cluster.htm
2 of 4
3/1/14 11:26 AM
http://www.datadisk.co.uk/html_docs/veritas/veritas_cluster.htm
below:
1. At the OBP set the scsi-initiator-id to 6
OK> setenv scsi-initiator-id 6
OK> printenv scsi-initiator-id
2. When the server has booted create and enter the following in /kernel/drv/glm.conf
name="glm" parent=/pci@1f,4000
unit-address="5"
scsi-initiator-id=6;
3. To check that the scsi-initiator-id has been set use the following command
# prtconf -v
Installation
Before you install VCS make sure you have the following perpared:
Cluster Name
Unique ID Number
Hostnames of the servers
Devices names of the network interfaces for the private networks
Root access
Able to perform remote shell from all systems (.rhosts file requires updating)
VCS software
To install VCS follow below, remember that both hosts must be able to root rsh into each otherwithout
requesting for a password: 1. Start the VCS installation by entering
# ./installVCS
cluster1
1
4. The software will now check each servers remote access and then install the software on each
server.
5. A list will appear detailing all the NIC's available. Select the FIRST then the SECOND private
networks links
3 of 4
3/1/14 11:26 AM
First Link:
Second Link:
http://www.datadisk.co.uk/html_docs/veritas/veritas_cluster.htm
hme0
qfe0
4 of 4
3/1/14 11:26 AM