Sun Microsystems
Products & Services
 
Support & Training
 
 

Previous Previous     Contents     Index     Next Next

Examining the Network Configuration Files

Each interface of each peer node must have the following configuration information:

  • An entry in the /etc/hosts file for the node

  • An /etc/hostname.interface-name file or an /etc/nodename file

Examine these files to understand the network configuration of a peer node. To find the name of the current node, see Mapping the Network Configuration of a Peer Node.

The network configuration files contain the following example information. In the following examples, the node name is MEN-C250-N20.

  • /etc/hostname.hme0 and /etc/hostname.hme1

    These files defines the host name for the hme0 and hme1 interface on a node.

    The /etc/hostname.hme0:100 file defines the host name for an additional external interface configured on a node.

  • /etc/nodename

    This file defines the host name of the cgtp0 interface on a node.

  • /etc/hosts

    This file contains a list of host names. For a cluster of three nodes, using the default class C addressing scheme, the /etc/hosts file is like this:

    Local host
    127.0.0.1 localhost

    Peer node 1 address triplet (Current node)
    10.250.1.20 MEN-C250-N20 MEN-C250-N20.localdomain loghost
    10.250.2.20 MEN-C250-N20-nic1 MEN-C250-N20-nic1.localdomain
    10.250.3.20 MEN-C250-N20-cgtp MEN-C250-N20-cgtp.localdomain

    Peer node 2 address triplet
    10.250.1.10 MEN-C250-N10
    10.250.2.10 MEN-C250-N10-nic1
    10.250.3.10 MEN-C250-N10-cgtp

    Peer node 3 address triplet
    10.250.1.30 NMEN-C250-N30
    10.250.2.30 NMEN-C250-N30-nic1
    10.250.3.30 NMEN-C250-N30-cgtp

    External address
    172.36.128.51 sol52

    Floating address triplet
    10.250.1.1 master-nic0
    10.250.2.1 master-nic1
    10.250.3.1 master-cgtp

Examining the Routes on a Node

At startup, the Cluster Membership Manager (CMM) creates a routing table for the interfaces on each peer node. The routing table is used by Carrier Grade Transport Protocol (CGTP) for data replication. To examine the routing table for a peer node, perform the following procedure. For simplicity, this procedure does not show external network access.

ProcedureTo Examine the Routing Table for a Node

  1. Log in to the peer node whose routes you want to examine.

  2. Display the routing table for the node:

    # netstat -r

    For a node using the class C addressing scheme, output similar to this is displayed:

    Routing Table: IPv4
      Destination           Gateway           Flags    Ref   Use  Interface
    -------------------- -------------------- -----  ----- ------ ---------
    10.250.3.255         10.250.1.255          UGHMS     1      0  
    10.250.3.255         10.250.2.255          UGHMS     1      0  
    NMEN-C250-N30-cgtp   NMEN-C250-N30         UGHMS     1   2557  
    NMEN-C250-N30-cgtp   NMEN-C250-N30-nic1    UGHMS     1   2554  
    master-cgtp0         master-nic0           UGHMS     1      1  
    master-cgtp0         master-nic1           UGHMS     1      1  
    MEN-C250-N10-cgtp    MEN-C250-N10          UGHMS     1   2644  
    MEN-C250-N10-cgtp    MEN-C250-N10-nic1     UGHMS     1   2640  
    10.250.1.0           MEN-C250-N20          U         1   3886  hme0
    10.250.1.0           MEN-C250-N20          U         1      0  hme0:1
    10.250.2.0           MEN-C250-N20-nic1     U         1   3866  hme1
    10.250.2.0           MEN-C250-N20-nic1     U         1      0  hme1:1
    10.250.3.0           MEN-C250-N20-cgtp     U         1      0  cgtp0
    10.250.3.0           MEN-C250-N20-cgtp     U         1      0  cgtp0:1
    default              10.250.1.253          UG        1      0  
    localhost            localhost             UH       17    747  lo0

For a description of the column headings, see Output of the netstat -r Command.

From the sample output, you can conclude the following facts:

  • This is a three node cluster. The cluster contains the nodes NMEN-C250-N30, MEN-C250-N10, and the current node.

  • The CGTP routes to broadcast 10.250.1.255 are as follows:

      Destination           Gateway           Flags    Ref   Use  Interface
    -------------------- -------------------- -----  ----- ------ ---------
    10.250.3.255         10.250.1.255          UGHMS     1      0  
    10.250.3.255         10.250.2.255          UGHMS     1      0  

  • The CGTP routes to node 30 are as follows:

      Destination           Gateway           Flags    Ref   Use  Interface
    -------------------- -------------------- -----  ----- ------ ---------
    NMEN-C250-N30-cgtp   NMEN-C250-N30         UGHMS     1   2557  
    NMEN-C250-N30-cgtp   NMEN-C250-N30-nic1    UGHMS     1   2554  

  • The CGTP routes to the CGTP floating address, cgtp0:1, are as follows:

      Destination           Gateway           Flags    Ref   Use  Interface
    -------------------- -------------------- -----  ----- ------ ---------
    master-cgtp          master-nic0           UGHMS     1      1  
    master-cgtp          master-nic1           UGHMS     1      1  

  • The CGTP routes to MEN-C250-N10 are as follows:

      Destination           Gateway           Flags    Ref   Use  Interface
    -------------------- -------------------- -----  ----- ------ ---------
    MEN-C250-N10-cgtp    MEN-C250-N10          UGHMS     1   2644  
    MEN-C250-N10-cgtp    MEN-C250-N10-nic1     UGHMS     1   2640  

The other entries in the table are standard Solaris routes.

To change the entries in the routing table, use the route command as described in the route(1M) man page.

Previous Previous     Contents     Index     Next Next