Sun Microsystems
Products & Services
 
Support & Training
 
 

Previous Previous     Contents     Next Next
Chapter 4

Running Administration Tasks on the Cluster

After you have installed the software on the cluster, run some administration tasks to check that the cluster is functioning correctly and to further evaluate the product.

To check your cluster, perform the following administration tasks:

Checking the Cluster Nodes

The Foundation Services product is delivered with tools to check different aspects of a cluster, including the status of cluster nodes, the network connection between nodes, and the IP addresses of nodes.

ProcedureTo Check the Status of the Cluster Nodes

To check the nodes of your cluster, use the nhcmmstat command.

  1. Log in to a master-eligible node as superuser.

  2. Check the nodes by using the nhcmmstat command.

    # /opt/SUNWcgha/sbin/nhcmmstat -c all
    Executed Command: all
    ------------------------------
    node_id     = 10   [This is the current node]
    domain_id   = 250
    name        = MEN-C250-N10
    role        = MASTER
    qualified   = YES
    synchro.    = READY
    frozen      = NO
    excluded    = NO
    eligible    = YES
    incarn.     = 1038420771 (27/11/2002 - 19:12:51)
    swload_id   = 1
    CGTP @      = 10.240.3.10
    ------------------------------
    ------------------------------
    node_id     = 30 
    domain_id   = 250
    name        = node30
    role        = IN
    qualified   = YES
    synchro.    = READY
    frozen      = NO
    excluded    = NO
    eligible    = NO
    incarn.     = 1038422116 (27/11/2002 - 19:35:16)
    swload_id   = 1
    CGTP @      = 10.240.3.30
    ------------------------------
    ------------------------------
    node_id     = 20 
    domain_id   = 2540
    name        = MEN-C250-N20
    role        = VICE-MASTER
    qualified   = YES
    synchro.    = READY
    frozen      = NO
    excluded    = NO
    eligible    = YES
    incarn.     = 1038420945 (27/11/2002 - 19:15:45)
    swload_id   = 1
    CGTP @      = 10.240.3.20
    ------------------------------

    In the preceding example, the output from the nhcmmstat command displays information about all the peer nodes in the console window. This information includes the role of each node. The peer nodes must include the master and vice-master nodes.

    For more information on nhcmmstat, see the nhcmmstat(1M) man page.

ProcedureTo Check the Network Connection Between Nodes

To check that the cluster network is functioning correctly, use the nhadm command.

  1. Log in to a peer node as superuser.

  2. Verify that the nodes in the cluster are communicating through a network.

    # /opt/SUNWcgha/sbin/nhadm check

    If any peer node is not accessible from any other peer node, the nhadm command displays an error message in the console window.

    For more information, see the Netra High Availability Suite Foundation Services 2.1 6/03 Cluster Administration Guide.

ProcedureTo Check Node Addresses

Each node has an IP address assigned to the NIC0, NIC1, and cgtp0 network interfaces. To identify and ping each network interface of a node, follow this procedure.

  1. Log in to the node that you want to examine.

  2. Run the ifconfig command.

    # ifconfig -a

    The ifconfig command displays configuration information about the network interfaces to the console window. Sample output for the ifconfig command on a peer node is as follows:

    hme0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 \
    index 1
            inet 10.250.1.30 netmask ffffff00 broadcast 10.250.1.255
            ether 8:0:20:f9:b4:b0 
    lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 2
            inet 127.0.0.1 netmask ff000000 
    hme1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3
            inet 10.250.2.30 netmask ffffff00 broadcast 10.250.2.255
            ether 8:0:20:f9:b4:b1 
    cgtp0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
            inet 10.250.3.30 netmask ffffff00 broadcast 10.250.3.255
            ether 0:0:0:0:0:0 

    Each peer node has at least three network interfaces configured. If a node has external access configured or if the node is the master, more network interfaces are displayed by the ifconfig command.

  3. Retrieve the cluster ID, that is, the domainid, by using the output from the ifconfig command.

    The domainid in this example is 250.

  4. Retrieve the node ID, that is, the nodeid, by using the output from the ifconfig command.

    The nodeid in this example is 30.

  5. Retrieve the network interface names and corresponding IP addresses by using the output from the ifconfig command.

    The network interfaces NIC0 and NIC1 in this example are the physical interfaces hme0 and hme1, respectively. The third interface is the virtual physical interface, cgtp0.

    The IP addresses for the three network interfaces in this example are as follows:

    hme0

    10.250.1.30

    hme1

    10.250.2.30

    cgtp0

    10.250.3.30

    The Ethernet addresses for NIC0 and NIC1 in this example are as follows:

    hme0

    8:0:20:f9:b4:b0

    hme1

    8:0:20:f9:b4:b1

  6. Log in to another peer node as superuser.

  7. Ping each network interface address of the node 30.

    # ping 10.250.1.30
    # ping 10.250.2.30
    # ping 10.250.3.30

Previous Previous     Contents     Next Next