clutil command

Purpose

Allows the administrator to run different cluster utilities in the Virtual I/O Server (VIOS).

Syntax

clutil -o pingcheck [-v] [-f <filename>]

Description

The clutil command uses the -o pingcheck option to verify whether the network communications among the Shared Storage Pool (SSP) cluster nodes are in the working state. It conducts a reverse lookup on all the nodes, and communicates from the local primary Internet Protocol (IP) address to the primary IP addresses of all other nodes, and local non-primary IP address to non primary IP addresses of other nodes.

The clutil-o pingcheck command uses the -v option to provide additional details about the nodes. If the -f <filename> option is not present, the command checks for network communications of all the nodes available in the cluster nodes.

Flags

Flag name Description

-v Specifies the details of the cluster nodes.

Flag name	Description
-v	Specifies the details of the cluster nodes.
-f <filename>	Specifies the file that consists of the list of nodes and IP addresses. The format of the file is as follows: `<hostname> <primary IP> <secondary IP1> ... <secondary IPn>`

-f <filename>

Specifies the file that consists of the list of nodes and IP addresses.

The format of the file is as follows: <hostname> <primary IP> <secondary IP1> ... <secondary IPn>

Examples

To perform the pingcheck operation among all the nodes in the SSP cluster, type the following command:

$ clutil -o pingcheck
Checking that reverse lookup of primary IP matches hostname...
Host: vss10-v1.aus.stglabs.ibm.com Reverse: vss10-v1.aus.stglabs.ibm.com... OK
Host: vss10-v3.aus.stglabs.ibm.com Reverse: vss10-v3.aus.stglabs.ibm.com... OK
Host: vss10-v5.aus.stglabs.ibm.com Reverse: vss10-v5.aus.stglabs.ibm.com... OK
Host: vss10-v4.aus.stglabs.ibm.com Reverse: vss10-v4.aus.stglabs.ibm.com... OK
Host: vss10-v6.aus.stglabs.ibm.com Reverse: vss10-v6.aus.stglabs.ibm.com... OK
Host: vss10-v2.aus.stglabs.ibm.com Reverse: vss10-v2.aus.stglabs.ibm.com... OK

Checking connectivity...
MY HOSTNAME: vss10-v1.aus.stglabs.ibm.com
LOCAL IP: 9.3.149.225 (PRIMARY)
...trying vss10-v3.aus.stglabs.ibm.com (9.3.148.78)... OK
...trying vss10-v5.aus.stglabs.ibm.com (9.3.148.81)... OK
...trying vss10-v4.aus.stglabs.ibm.com (9.3.148.80)... OK
...trying vss10-v6.aus.stglabs.ibm.com (9.3.148.97)... OK
...trying vss10-v2.aus.stglabs.ibm.com (9.3.149.226)... OK

To get the details of the nodes present in the cluster when the pingcheck operation is in progress, type the following command:

$ clutil -o pingcheck -v
Checking the following cluster nodes:
vss10-v1.aus.stglabs.ibm.com : 
    Primary IP: 9.3.149.225
vss10-v3.aus.stglabs.ibm.com : 
    Primary IP: 9.3.148.78
vss10-v5.aus.stglabs.ibm.com : 
    Primary IP: 9.3.148.81
vss10-v4.aus.stglabs.ibm.com : 
    Primary IP: 9.3.148.80
vss10-v6.aus.stglabs.ibm.com : 
    Primary IP: 9.3.148.97
vss10-v2.aus.stglabs.ibm.com : 
    Primary IP: 9.3.149.226

Checking that reverse lookup of primary IP matches hostname...
Host: vss10-v1.aus.stglabs.ibm.com Reverse: vss10-v1.aus.stglabs.ibm.com... OK
Host: vss10-v3.aus.stglabs.ibm.com Reverse: vss10-v3.aus.stglabs.ibm.com... OK
Host: vss10-v5.aus.stglabs.ibm.com Reverse: vss10-v5.aus.stglabs.ibm.com... OK
Host: vss10-v4.aus.stglabs.ibm.com Reverse: vss10-v4.aus.stglabs.ibm.com... OK
Host: vss10-v6.aus.stglabs.ibm.com Reverse: vss10-v6.aus.stglabs.ibm.com... OK
Host: vss10-v2.aus.stglabs.ibm.com Reverse: vss10-v2.aus.stglabs.ibm.com... OK

Checking connectivity...
MY HOSTNAME: vss10-v1.aus.stglabs.ibm.com
LOCAL IP: 9.3.149.225 (PRIMARY)
...trying vss10-v3.aus.stglabs.ibm.com (9.3.148.78)... OK
...trying vss10-v5.aus.stglabs.ibm.com (9.3.148.81)... OK
...trying vss10-v4.aus.stglabs.ibm.com (9.3.148.80)... OK
...trying vss10-v6.aus.stglabs.ibm.com (9.3.148.97)... OK
...trying vss10-v2.aus.stglabs.ibm.com (9.3.149.226)... OK

To get details of the nodes in a file and perform the pingcheck operation among those nodes, type the following command:

(0) padmin @ vss10-v1: /home/padmin
$ cat ip_file
vss10-v1.aus.stglabs.ibm.com 9.3.149.225 10.10.100.1
vss10-v2.aus.stglabs.ibm.com 9.3.149.226 10.10.100.3

(0) padmin @ vss10-v1: /home/padmin
$ clutil -o pingcheck -v -f ip_file
Checking the following cluster nodes:
vss10-v1.aus.stglabs.ibm.com : 
        Primary IP: 9.3.149.225
        Gateway IPs: ['10.10.100.1']
vss10-v2.aus.stglabs.ibm.com : 
        Primary IP: 9.3.149.226
        Gateway IPs: ['10.10.100.3']

Checking that reverse lookup of primary IP matches hostname...
Host: vss10-v1.aus.stglabs.ibm.com Reverse: vss10-v1.aus.stglabs.ibm.com... OK
Host: vss10-v2.aus.stglabs.ibm.com Reverse: vss10-v2.aus.stglabs.ibm.com... OK

Checking connectivity...
MY HOSTNAME: vss10-v1.aus.stglabs.ibm.com
LOCAL IP: 9.3.149.225 (PRIMARY)
...trying vss10-v2.aus.stglabs.ibm.com (9.3.149.226)... OK
LOCAL IP: 10.10.100.1
...trying vss10-v2.aus.stglabs.ibm.com (10.10.100.3)... OK

(0) padmin @ vss10-v1: /home/padmin
$