sun.com | docs.sun.com | How To Buy | My Sun | Worldwide Sites |  |

| Previous Contents Index Next
2. Chapter 4 # Examining the Cluster Networking Configuration For information about how to obtain information about peer nodes and the network interfaces on those nodes, see the following sections. For a description of addressing and networking, see the Netra High Availability Suite Foundation Services 2.1 6/03 Overview. Using Tools to Examine the Cluster Network Creating a Network Topology Map Mapping the Network Configuration of a Peer Node Mapping the External Network Configuration of a Node Mapping the Floating Address Triplet of the Master Node Mapping the Floating External Address of the Master Node Examining the Network Configuration Files Examining the Routes on a Node ## Using Tools to Examine the Cluster Network Use the following tools to examine the cluster network configuration: `nhadm` `ifconfig` `netstat` Use these tools to ensure that your cluster network is correctly configured after maintenance, or to obtain information about cluster membership problems. For information about solving cluster membership problems, see the Netra High Availability Suite Foundation Services 2.1 6/03 Troubleshooting Guide. ### Verifying the Network Configuration Before collecting data about the cluster network configuration, perform the following procedure to test whether the interfaces of a node are configured correctly. #### To Verify the Network Interfaces of a Node Log in as superuser to the node whose interfaces you want to examine. Check the network configuration:
       # nhadm check configuration
2. The tests this command performs include: Whether the files `/etc/hostname.`NIC0`` and `/etc/hostname.`NIC1`` exist on the current node. Whether the `/etc/hosts` file contains IP addresses that correspond to the NIC0, NIC1, and `cgtp0` interfaces for each peer node. The `nhadm` tool displays the success or failure of each test it performs. ## Creating a Network Topology Map A network topology map contains information about each node in a cluster, and each interface on a node. A network topology map can also include information about nonpeer nodes that are communicating with the cluster. When investigating your network topology, you can create a network topology map. The map is a helpful reference when using the cluster or changing the cluster configuration. The following figure illustrates an example of the information that you can include in a network topology map. Figure 4-1 Template for a Network Topology Map As you work through the procedures in this chapter, add information to the network topology map for the nodes in your cluster. You can link all the nodes in the network topology map using the routing information described in Examining the Routes on a Node. ## Mapping the Network Configuration of a Peer Node This section describes how to obtain network information about a peer node. ### To Identify the Name of a Node Log in to the node you want to examine. Run:
       # hostname
2. The name of the node is displayed in the console window. ### To Identify the Host Name of the Network Interfaces of a Node Log in to the node whose network interfaces you want to examine. Run:
       # netstat -i
2. The host name of the node's network interfaces is displayed. For more information, see the `netstat`(1M) man page. ### To Obtain Configuration Information About the Network Interfaces of a Node This procedure determines the IP addresses, netmask value, network IDs, node IDs, Ethernet address, and interface names of a peer node. Log in to the node whose network interfaces you want to examine. Run the `ifconfig` command:
       # ifconfig -a
   The `ifconfig` command displays configuration information about the network interfaces. Each peer node has at least three configured network interfaces. The physical interfaces, NIC0 and NIC1, and the CGTP interface. Additional network interfaces are displayed for the master node, the vice-master node, and for interfaces that are configured for external access. If the node is using the class B addressing scheme, output similar to this is displayed:
       hme0: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 \
       index 1
               inet 172.15.0.30 netmask ffff0000 broadcast 172.15.255.255
               ether 8:0:20:f9:b3:60
       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 172.16.0.30 netmask ffff0000 broadcast 172.16.255.255
               ether 8:0:20:f9:b3:61
       cgtp0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4
               inet 172.17.0.30 netmask ffff0000 broadcast 172.17.255.255
               ether 0:0:0:0:0:0
   In this example, the nodeid is `30`, the netmask is `ffff0000`, and the network IDs are `172.15.0.0`, `172.16.0.0`, and `172.17.0.0`. If the node is using the default class C addressing scheme, output similar to this is displayed:
       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
In this example, the nodeid is `30`, the netmask is `ffffff00`, and the network IDs are `10.250.1.0`, `10.250.2.0`, and `10.250.3.0`.
Previous Contents Index Next

Copyright 1994-2004 Sun Microsystems