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

| Previous Contents Index Next
1. Chapter 3 # Installing and Configuring the Cluster Hardware After you have chosen your cluster configuration, install and configure the cluster hardware. For example cluster configurations and supported hardware, see Chapter 2, Choosing the Cluster Hardware. For instructions on installing and configuring the cluster hardware, see the following sections: Installing and Configuring Netra Servers Installing and Configuring the Terminal Server Installing and Configuring Ethernet Switches Installing and Configuring Supplemental Ethernet Cards for External Access Note - Wherever possible, URLs are provided to relevant online documentation. Where no URL is provided, see the documentation that is provided with the hardware. For a list of additional hardware packages and patches to install before installing the Foundation Services, see the Netra High Availability Suite Foundation Services 2.1 6/03 README. To connect the cluster to the installation server, see Chapter 4, Connecting the Installation Hardware and Cluster Hardware. ## Installing and Configuring Netra Servers To install the Netra servers, see the documentation provided with the hardware or go to the following web site: `http://www.sun.com/products-n-solutions/hardware/docs/Servers` ### Installing CompactPCI Boards For the Foundation Services, the Netra CT 810 and Netra CT 410 servers can be installed with the following types of boards: Netra CP2140 system boards for master-eligible nodes Netra CP2160 satellite boards for diskless nodes The Netra CT 820 servers can be installed with CP2300 boards as master-eligible, diskless, or dataless nodes nodes. To install one or more of the boards, see the documentation that is provided with the processor or go to this web site: `http://www.sun.com/products-n-solutions/hardware/docs/CPU_Boards/` ## Installing and Configuring the Terminal Server A terminal server is a console access device that connects the console ports of several nodes to a TCP/IP network. The terminal server connects to cluster nodes through an Ethernet connection. The terminal server enables you to connect to the console of a node. Note - Terminal servers are also called remote terminal servers (RTS), system console servers, or access servers. For the Foundation Services, each cluster must have one terminal server. You can use any terminal server with your cluster. You can share a terminal server across clusters, where the number of nodes you can have per terminal server depends on the server model. Install your terminal server using the documentation that is provided with your terminal server. The Foundation Services have been tested on clusters that use terminal servers such as the Cisco 2511 Access Server, the CompactPCI CPC4406, and the PERL CS9000. The examples in this section are for the Cisco 2511 Access Server. The documentation for this terminal server is located at: `http://cisco.com/univercd/cc/td/doc/product/access` Configure the Cisco 2511 Access Server as described in the following procedure. ### To Configure the Cisco 2511 Access Server Turn on the power for the Cisco 2511 access server, and connect to it by using a terminal console window. Startup information is displayed in the console window.
       14336K/2048K bytes of memory.
       Processor board ID 21448610, with hardware
       revision 00000000
       Bridging software.
       X.25 software, Version 2.0, NET2, BFE and
       GOSIP compliant.
       1 Ethernet/IEEE 802.3 interface(s)
       2 Serial network interface(s)
       16 terminal line(s)
       32K bytes of non-volatile configuration
       memory.
       8192K bytes of processor board System flash
       (Read ONLY)
       ...
       Default settings are in square brackets '[]'.
       Would you like to enter the initial
       configuration dialog? [yes]:
2. When asked if you want to enter the initial configuration dialog, type `No`.
       Would you like to enter the initial configuration dialog? [yes]: No
3. Enter the configuration mode to modify the configuration on the terminal server:
       router> enable
4. When you are in the configuration mode, the prompt changes to `router#`. Display the `running-config` configuration file for the terminal server:
       router# show running-config
6. The configuration file is displayed. Copy and paste the entire configuration file into a text editor. In the text editor, customize the configuration file for your network. Change the parameters that are marked in italics in the following example:
       !
       version 11.2
       no service password-encryption
       no service udp-small-servers
       no service tcp-small-servers
       !
       hostname machine-hostname
       !
       enable password access-password
       !
       no ip routing
       ip domain-name IP-domain-name
       ip name-server IP-name-server
       !
       interface Ethernet0
       ip address IP-address 255.255.255.0
       no shutdown
       !
       interface Serial0
       no ip address
       no ip route-cache
       shutdown
       !
       ip default-gateway IP-default-gateway
       ip classless
       ip route 0.0.0.0 0.0.0.0 IP-default-gateway
       snmp-server community public RO
       snmp-server trap-authentication
       snmp-server location snmp-server-location
       snmp-server contact contact-email-address
       !
       line con 0
        transport preferred none
       line 1 16
        no exec
        exec-timeout 0 0
        transport preferred none
        transport input all
        stopbits 1
       line aux 0
       line vty 0 4
        no login
       !
7. Enable the configuration file to be modified from the console window:
       router# config terminal
9. Copy and paste the modified configuration file into the console window. Exit the configuration mode:
       router(config)# end
10. Verify that the configuration file has been modified:
        router# show running-config
11. Verify that the output contains the configuration information that you specified in Step 6. Save the configuration as the startup configuration file:
        router# copy running-config startup-config
12. Press Return to confirm and to save the changes to the configuration. The terminal server, Cisco 2511 Access Server, is now configured to be used by your cluster. A console window to the terminal server on a port can be accessed by using `telnet` as follows:
        $ telnet terminal-concentrator-hostname 20port-number
Previous Contents Index Next

Copyright 1994-2004 Sun Microsystems