Previous  |  Next  >  
Product: Cluster Server Guides   
Manual: Cluster Server 4.1 Installation Guide   

Verifying LLT, GAB, and Cluster Operation

Before attempting to verify the operation of LLT, GAB, or the cluster, you must:

    Checkmark  Log in to any system in the cluster as root.

    Checkmark  Place the VCS command directory in your PATH variable:


    export PATH=$PATH:/usr/sbin:/sbin:/opt/VRTS/bin:/opt/VRTSvcs/bin

Verifying LLT

Use the lltstat command to verify that links are active for LLT. This command returns information about the links for LLT for the system on which it is typed. Refer to the lltstat(1M) manual page for more information.

Using lltstat -n

In the following example, lltstat -n is typed on each system in the cluster:


System 1


lltstat -n

Output resembles:


 LLT  node  information:
       Node      State     Links
      *0 north   OPEN      2
       1 south   OPEN      2

System 2


lltstat -n

Output resembles:


 LLT  node  information:
       Node      State     Links
       0 north   OPEN      2
      *1 south   OPEN      2

Note that each system has two links and that each system is in the OPEN state. The asterisk (*) denotes the system on which the command is typed.

Using lltstat -nvv

With LLT configured correctly, the output of lltstat -n shows all the systems in the cluster and two links for each system. If the output shows otherwise, you can use the verbose option of lltstat.

For example, type lltstat -nvv | more on a system to view additional information about LLT. In the following example, lltstat -nvv | more is typed on a system in a two-system cluster:


lltstat -nvv | more

Output resembles:


Node        State    Link         Status   Address
*0 north    OPEN
                      lan1         UP       08:00:20:93:0E:34
                      lan2         UP       08:00:20:93:0E:35
1 south     OPEN
                      lan1         UP       08:00:20:8F:D1:F2
                      lan2         DOWN
2           CONNWAIT
                      lan1         DOWN
                      lan2         DOWN
             CONNWAIT
                      lan1         DOWN
                      lan2         DOWN
.
.
.
1           CONNWAIT
                      lan1         DOWN
                      lan2         DOWN

Note that the output lists 32 nodes. It reports on the two cluster systems, north and south, plus non-existent nodes. For each correctly configured system, the information should show a state of OPEN, a status for each link of UP, and an address for each link. However, the output in the example shows that for the system south the private network connection is possibly broken or the information in the /etc/llttab file may be incorrect.

To obtain information about the ports open for LLT, type lltstat -p on any system. In the following example, lltstat -p is typed on one system in a two-system cluster:


System 1


lltstat -p

Output resembles:


LLT port information: 
    Port   Usage     Cookie
      0    gab       0x0
        opens:       0 2 3 4 5 6 7 8 9 10 11 … 28 29 30 31
        connects:    0 1  
      7    gab       0x7
           opens:       0 2 3 4 5 6 7 8 9 10 11 … 28 29 30 31
           connects:    0 1 
         31   gab       0x1F
           opens:       0 2 3 4 5 6 7 8 9 10 11 … 28 29 30 31
           connects:    0 1 

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 random generation number, and membership 01 indicates that systems 0 and 1 are connected.

Port h indicates that VCS is started, gen fd570002 is a random generation number, and membership 01 indicates that systems 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, refer to the VERITAS Cluster Server User's Guide.

Verifying the Cluster

To verify that the cluster is operating, type the following command:


hastatus -summary

The output resembles:


-- SYSTEM STATE
-- System               State                Frozen

A  north                RUNNING              0
A  south                RUNNING              0

-- GROUP STATE
-- Group            System       Probed  AutoDisabled  State

B  ClusterService   north        Y       N             ONLINE
B  ClusterService   south        Y       N             OFFLINE

Note the system state. If the value is RUNNING, VCS is successfully installed and running. The group state lists the ClusterService group, which is ONLINE on north and OFFLINE on south. Refer to the hastatus(1M) manual page. In the VERITAS Cluster Server User's Guide, look for a description of system states and the transitions between them.

hasys -display

On one of the systems, use the hasys(1M) command:


 # /opt/VRTSvcs/bin/hasys -display

On each system, the output should be similar. For more information on the hasys -display command, refer to the hasys(1M) manual page. Also refer to the VERITAS Cluster Server User's Guide for information about administering VCS from the command line.

The example shows the output when the hasys -display command is run on the system north; the list continues with similar information for south (not shown) and any other systems in the cluster:


#System

Attribute

Value

north

AgentsStopped

0

north

AvailableCapacity

100

north

CPUBinding

BindTo None CPUNumber 0

north

CPUUsage

0

north

CPUUsageMonitoring

Enabled 0 ActionThreshold 0 ActionTimeLimit 0 Action NONE NotifyThreshold 0 NotifyTimeLimit 0

north

Capacity

100

north

ConfigBlockCount

100

north

ConfigCheckSum

29776

north

ConfigDiskState

CURRENT

north

ConfigFile

/etc/VRTSvcs/conf/config

north

ConfigInfoCnt

0

north

ConfigModDate

Thu Sep 16 23:00:00 2004

north

CurrentLimits


north

DiskHbStatus


north

DynamicLoad

0

north

EngineRestarted

0

north

Frozen

0

north

GUIIPAddr


north

LLTNodeId

0

north

LicenseType

DEMO

north

Limits


north

LinkHbStatus

lan1 UP lan2 UP

north

LoadTimeCounter

1890

north

LoadTimeThreshold

600

north 

LoadWarningLevel

80

north

MajorVersion

4

north

MinorVersion

0

north

NoAutoDisable

0

north

NodeId

0

north

OnGrpCnt

1

north

ShutdownTimeout

120

north

SourceFile

./main.cf

north

SysInfo

HP-UX:north,U,B.11.23,9000/800

north

SysName

north

north

SysState

RUNNING

north

SystemLocation


north

SystemOwner


north

TFrozen2

0

north

TRSE

0

north

UpDownState

Up

north

UserInt

0

north

UserStr


north

VCSFeatures

DR

north

VCSMode

VCS

 ^ Return to Top Previous  |  Next  >  
Product: Cluster Server Guides  
Manual: Cluster Server 4.1 Installation Guide  
VERITAS Software Corporation
www.veritas.com