< Previous  | TOC | Index | Next  >

Checking cluster operation

You need to check cluster operaton only if you installed and configured an HA version of the Storage Foundation software.

 To verify that the cluster is operating

• Type the following command on any node:

  # hastatus -summary

-- SYSTEM STATE

-- System State Frozen

A  host1 RUNNING 0

A  host2 RUNNING 0

-- GROUP STATE

-- Group System Probed AutoDisabled State

B  ClusterService host1 Y N ONLINE

B  ClusterService host2 Y N OFFLINE

Identify the system state of each node in the output of this command. If the value is running for all the nodes, VCS is successfully installed and running.

Refer to the hastatus(1M) manual page and the Veritas Cluster Server User's Guide for more information on system states and state transitions.

About Low Latency Transport

The file llthosts(4) is a database containing one entry per node that links the Low Latency Transport (LLT) system ID (in the first column) with the LLT host name. This file is identical on each cluster node.

Based on the sample installation, the file /etc/llthosts contains the entries:

0 host1

1 host2

The file llttab(1M) contains information derived from the installation and used by the utility lltconfig(1M). After installation, this file lists the network links that correspond to the specific node.

The first line identifies the node. The second line identifies the cluster, based on the cluster ID entered during installation. The next two lines, beginning with the link command, identify the two network cards used by the LLT protocol.

See the llttab(4) manual page for details on how to modify the LLT configuration. The manual page describes ordering the directives in the llttab file.

Verifying LLT

Use the lltstat command to verify that LLT links are active for each system in the cluster.

 To verify that links are active for LLT

• Use the lltstat -n as follows:

  # lltstat -n

With LLT configured correctly, the output of lltstat -n shows all of the nodes in the cluster and two links for each node. If the output shows otherwise, type
lltstat -nvv | more on any node to view additional information about LLT.

 To obtain LLT port information

• Use the lltstat -p command as follows:

  # lltstat -p

About Group Membership and Atomic Broadcast

After installation, the file /etc/gabtab contains a gabconfig(1M) command that configures the Group Membership and Atomic Broadcast (GAB) driver.

The file /etc/gabtab contains a line that resembles:

/sbin/gabconfig -c -nN

where the -c option configures the driver and -nN specifies the cluster will not be formed until at least N nodes are ready. The variable N represents the number of cluster nodes.

Verifying GAB

 To verify that GAB is operating

• Type the following command on each system:

  # /sbin/gabconfig -a

If GAB is operating, the following GAB port membership information is returned:

GAB Port Memberships

===================================

Port a gen a36e0003 membership 01

Port h gen fd570002 membership 01

Port a indicates that GAB is communicating, gen a36e0003 is a randomly generated number, and membership 01 indicates that nodes 0 and 1 are connected.

Port h indicates that VCS is started, gen fd570002 is a randomly generated number, and membership 01 indicates that nodes 0 and 1 are both running VCS.

If GAB is not operating, no GAB port membership information is returned:

GAB Port Memberships

===================================

If only one network is connected, the following GAB port membership information is returned:

GAB Port Memberships

===================================

Port a gen a36e0003 membership 01

Port a gen a36e0003 jeopardy    1

Port h gen fd570002 membership 01

Port h gen fd570002 jeopardy    1

For more information on GAB, including descriptions of ports, refer to the Veritas Cluster Server User's Guide.