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

| Previous Contents Index Next
2. 1. Chapter 3 # Configuring Standalone CGTP Without the Reliable Boot Service This chapter describes how to configure standalone CGTP without the Reliable Boot Service. The examples in this chapter use IPv4. For more information, see these sections: Introducing CGTP Configuration Preparing to Configure Standalone CGTP Configuring the `cgtp0` Virtual Physical Interface Configuring Additional CGTP Virtual Logical Interfaces Creating Routes for CGTP Disabling CGTP ## Introducing CGTP Configuration This chapter describes the steps that you perform on nodes that are to run standalone CGTP. All examples in this chapter describe the configuration of two nodes, `machine A` and `machine B`, as shown in Figure 3-1. When configured, these nodes communicate through dual network links that form a CGTP network. You must decide the number of nodes that you want to configure to be part of this CGTP network. Figure 3-1 CGTP Configuration for `machine A` and `machine B` ## Preparing to Configure Standalone CGTP To have a CGTP network, each node on the network must be configured to have three interfaces: Two interfaces, NIC0 and NIC1, that can be either physical or logical. These interfaces can be `hme`, `eri`, or `le` depending on the hardware you use. For more information and the interface type for specific supported hardware, see the Netra High Availability Suite Foundation Services 2.1 6/03 Hardware Guide. One virtual physical interface, `cgtp0`. Configure CGTP on the node's `local` file system. Do not configure CGTP on a remote shared file system because a remote file system might become unreachable if the network fails. Before configuring CGTP interfaces and routes, configure the interface names, addresses, netmasks, and the database search on each node. Perform the following procedures on each node that you are configuring for standalone CGTP. To Configure Interface Names To Configure an Ethernet Address Per Network Interface To Configure Node Addresses To Configure Netmasks To Configure the NIS Database Search ### To Configure Interface Names Configure the interface names manually to enable creation of interfaces, and redundant routes, at first boot. Note - You cannot enable the autoconfiguration of routes on subsequent reboots. Log in to the node that you want to configure for CGTP. Register the host names for each local IP interface. To ensure that the devices that you configure for CGTP are located in subsequent reboots, create five files: `/etc/hostname.`NIC0`` `/etc/hostname.`NIC1`` `/etc/hostname.cgtp0` `/etc/dhcp.`NIC0`` `/etc/dhcp.`NIC1`` These files must be empty. Note - Network interfaces, such as NIC0, might have been created during the installation process. ### To Configure an Ethernet Address Per Network Interface Configure the network interfaces of the node to use the Ethernet address on the card and not the Ethernet address stored in its NVRAM. Log in to the node as superuser. Enable the `ok` prompt. To get the `telnet` prompt, press Control-]:
          # Control-]
   2. To get the `ok` prompt, type `send brk` at the `telnet` prompt:
          telnet> send brk
          Type 'go' to resume
          ok>
3. Configure the processors to use local Ethernet (MAC) addresses:
       ok> setenv local-mac-address? true
6. ### To Configure Node Addresses Manually configure the node addresses so that the interfaces and the redundant routes are created at first boot. Log in to the node that you want to configure for CGTP. Open `/etc/inet/hosts` in a text editor. Define the set of IP addresses for NIC0, NIC1, and `cgtp0` in the `/etc/inet/hosts` file as described in To Configure Interface Names. Save the `/etc/inet/hosts` file and exit the text editor. Reboot the node. Check that the node addresses are automatically assigned to the interface:
       % ifconfig -a
For more information on the `ifconfig` command, see the `ifconfig`(1M) man page.
Previous Contents Index Next

Copyright 1994-2004 Sun Microsystems