This chapter provides the hardware and software procedures for installing and configuring a terminal concentrator in a Sun Cluster environment.
This chapter contains the following procedures:
"How to Establish a Default Route for the Terminal Concentrator"
"How to Connect to a Node's Console Through the Terminal Concentrator"
For conceptual information on terminal concentrators, see Sun Cluster 3.0 Concepts.
The following table lists the procedures for installing and configuring the terminal concentrator.
Table 2-1 Task Map: Installing and Configuring the Terminal Concentrator
Task |
For Instructions, Go To... |
---|---|
Install the terminal concentrator | |
Cable the terminal concentrator | |
Configure the terminal concentrator |
"How to Configure the Terminal Concentrator"
|
Set terminal concentrator port parameters |
"How to Set Terminal Concentrator Port Parameters"
|
Correct a port configuration access error | |
Establish a default route |
"How to Establish a Default Route for the Terminal Concentrator" |
This section covers the procedure for installing the terminal concentrator hardware and connecting cables from the terminal concentrator to the administrative console and the cluster nodes.
This procedure provides step-by-step instructions for rack-mounting the terminal concentrator. For convenience, you can rack-mount the terminal concentrator even if your cluster does not contain rack-mounted nodes.
If you do not want to rack-mount your terminal concentrator, place the terminal concentrator in its standalone location, and connect the unit into a utility outlet.
Install the terminal concentrator bracket hinge in the primary cabinet.
Locate the hinge portion of the terminal concentrator bracket assembly.
Loosely install two locator screws in the right-side rail in the rear of the cabinet.
Thread the screws into holes 8 and 29, as shown in Figure 2-1. The locator screws will accept the slotted holes in the hinge piece.
Place the slotted holes of the hinge over the locator screws, and let the hinge drop into place.
Install the screws in holes 7 and 28.
Tighten these screws, as well as those in holes 8 and 29, as shown in Figure 2-1.
Install the terminal concentrator in the bracket, and assemble the bracket.
Place the side pieces of the bracket against the terminal concentrator, as shown in Figure 2-2.
Lower the terminal concentrator (with side pieces) onto the bottom plate. Align the holes in the side pieces with those in the bottom plate.
Install and tighten three nuts on threaded studs penetrating through each side plate.
This step completes the bracket assembly.
Install the terminal concentrator bracket onto the hinge in the chassis.
Turn the terminal concentrator bracket on its side so the hinge holes and cable connectors face right.
Align the bracket holes with the boss pins in the hinge assembly, and drop the bracket onto the hinge, as shown in Figure 2-3.
Install the keeper screw in the shorter boss pin to ensure the assembly cannot be accidentally knocked off the hinge.
Connect the power cord to the terminal concentrator, as shown in Figure 2-4. Connect the other end to the power distribution unit.
To cable the terminal concentrator, go to "How to Cable the Terminal Concentrator".
Connect the serial cable (530-2152-01 or 530-2151-01) from serial port A on the administrative console to serial port 1 on the terminal concentrator, as shown in Figure 2-5.
The cable connection from the administrative console enables you to configure the terminal concentrator. The connection serves no other purpose. You can remove this connection after you set up the terminal concentrator.
Connect the nodes to the terminal concentrator. Use serial cables with an RJ-45 connector on one end and a DB-25 on the other.
The cable connections from the concentrator to the nodes enable you to access the ok prompt or OpenBootTM PROM (OBP) mode by using the Cluster Console (Console Mode) Windows from the Cluster Control Panel (CCP). For more information on using the CCP, see Sun Cluster 3.0 System Administration Guide.
Connect the public network Ethernet cable to the appropriate connector on the terminal concentrator.
The terminal concentrator requires a 10-Mbit/sec Ethernet connection.
Close the terminal concentrator bracket, and install screws in holes 8 and 29 on the left-side rail.
Go to "Configuring the Terminal Concentrator".
This section provides the procedure for configuring the terminal concentrator's network addresses and ports.
From the administrative console, add the following entry to the /etc/remote file.
tc:\ :dv=/dev/term/a:br#9600: |
Verify that the server and the terminal concentrator are powered on and that the cabinet keyswitch (if applicable) is in the ON position.
Establish a connection to the terminal concentrator's serial port.
# tip tc |
If your terminal concentrator is powered off, power on the terminal concentrator and, within five seconds of it being powered on, hold down the Test button for one second, then release the Test button.
If your terminal concentrator is powered on, hold down the Test button until the power LED flashes (about three seconds), then release the Test button. For one second, hold down the Test button again, then release.
Figure 2-6 shows the location of the Test button.
The terminal concentrator performs a self-test, which lasts about 30 seconds. Messages display on the administrative console. If the network connection is not found, press the Q key to stop the message.
If the front panel LEDs light up as shown in Table 2-2, and the administrative console displays a monitor:: prompt, proceed to Step 5. Otherwise, use Table 2-3 and the documentation that shipped with your terminal concentrator to troubleshoot.
Table 2-2 Front Panel LEDs: Indicating a Successful Boot or Monitor Mode Reset
Power (Green) |
Unit (Green) |
Net (Green) |
Attn (Amber) |
Load (Green) |
Active (Green) |
Test (Orange) |
---|---|---|---|---|---|---|
ON |
ON |
ON |
ON |
OFF |
Intermittent blinking |
ON |
Table 2-3 Front Panel LEDs: Indicating a Failed Boot
Mode |
Power (Green) |
Unit (Green) |
Net (Green) |
Attn (Amber) |
Load (Green) |
Active (Green) |
---|---|---|---|---|---|---|
Hardware failure |
ON |
Blinking |
OFF |
Blinking |
OFF |
OFF |
Network test failure |
ON |
ON |
Blinking |
OFF |
OFF |
Intermittent blinking |
Network test aborted, or net command failed |
ON |
ON |
OFF |
Blinking |
OFF |
Intermittent blinking |
Booted wrong image |
ON |
ON |
ON |
Blinking |
OFF |
OFF |
Other failure |
One or more Status LEDs (1-8) are ON |
Use the addr command to assign an IP address, subnet mask, and network address to the terminal concentrator.
In the following example (Class B network, Class C subnet), the broadcast address is the terminal concentrator's address with the host portion set to 255 (all binary 1's).
monitor:: addr Enter Internet address [<uninitialized>]:: 172.25.80.6 Internet address: 172.25.80.6 Enter Subnet mask [255.255.0.0]:: 255.255.255.0 Subnet mask: 255.255.255.0 Enter Preferred load host Internet address [<any host>]:: 172.25.80.6 *** Warning: Load host and Internet address are the same *** Preferred load host address: 172.25.80.6 Enter Broadcast address [0.0.0.0]:: 172.25.80.255 Broadcast address: 172.25.80.255 Enter Preferred dump address [0.0.0.0]:: 172.25.80.6 Preferred dump address: 172.25.80.6 Select type of IP packet encapsulation (ieee802/ethernet) [<ethernet>]:: Type of IP packet encapsulation: <ethernet> Load Broadcast Y/N [Y]:: n Load Broadcast: N |
After the addr session, power-cycle the terminal concentrator.
The Load and Active lights should briefly blink, and then the Load light turns off.
Use the ping(1M) command to confirm that the network connection works.
Exit the tip utility by entering <Return> and typing a tilde followed by a period.
<Return>~. ~ [EOT] # |
Go to "How to Set Terminal Concentrator Port Parameters".
This procedure explains how to determine if the port type variable must be set and how to set the variable.
The port type parameter must be set to dial_in. If the parameter is set to hardwired, the cluster console might be unable to detect when a port is already in use. The port type parameter must be set to Y.
Find the Sun label on the top panel of the terminal concentrator.
Figure 2-7 shows the Sun label.
Examine the serial number to see if it is in the lower serial number range. The serial number consists of 7 digits, followed by a dash and 10 more digits.
If the numbers after the dash start with 9520 or higher, the port type variable is set correctly. Skip to Step 4.
If the numbers after the dash start with 9519 or lower, you must change the port type variable. Proceed to Step 3.
Using an administrative console, change the port type variable by setting the port parameters, then reboot the terminal concentrator as shown in the following example.
The boot command causes the changes to take effect. The terminal concentrator will be unavailable for approximately one minute.
admin-ws# telnet tc_name Trying terminal concentrator IP address Connected to tc_name Escape character is '^]'. Rotaries Defined: cli - Enter Annex port name or number: cli Annex Command Line Interpreter * Copyright 1991 Xylogics, Inc. annex: su Password: password (default password is the terminal concentrator IP address) annex# admin Annex administration MICRO-XL-UX R7.0.1, 8 ports admin : set port=1-8 type dial_in imask_7bits Y You may need to reset the appropriate port, Annex subsystem or reboot the Annex for changes to take effect. admin : set port=1-8 mode slave admin : quit annex# boot bootfile: <return> warning: <return> |
Ensure that the terminal concentrator is powered on and has completed booting.
Verify that you can log in from the administrative console to the consoles of each node.
For information on how to connect to the nodes' consoles, see "How to Connect to a Node's Console Through the Terminal Concentrator".
A misconfigured port not accepting network connections may return a Connect: Connection refused message when you use telnet(1). Use the following procedure to correct the port configuration.
Connect to the terminal concentrator without specifying a port.
# telnet tc_name |
Specifies the hostname of the terminal concentrator
Press an extra Return after making the connection, and specify the port number.
Trying ip_address .. Connected to 192.9.200.1 Escape character is '^]'. ... [RETURN] Rotaries Defined: cli - Enter Annex port name or number: 2 |
If you see a Port(s) busy, do you wish to wait? (y/n) message, answer N and go to "How to Reset a Terminal Concentrator Port".
If you see a Error: Permission denied message, the port mode is configured incorrectly to the command-line interface and must be set to slave. Go to Step 3.
Select the terminal concentrator's command-line interface.
... Enter Annex port name or number: cli annex: |
Type the su command and password.
The default password is the terminal concentrator's IP address.
annex: su Password: |
Reset the port.
annex# admin Annex administration MICRO-XL-UX R7.0.1, 8 ports admin: port 2 admin: set port mode slave You may need to reset the appropriate port, Annex subsystem or reboot the Annex for changes to take effect. admin: reset 2 |
The following example shows how to correct an access error on the terminal concentrator port 2.
admin-ws# telnet tc1 Trying 192.9.200.1 ... Connected to 192.9.200.1. Escape character is '^]'. [Return] Enter Annex port name or number: cli ... annex: su Password: root_password annex# admin Annex administration MICRO-XL-UX R7.0.1, 8 ports admin: port 2 admin: set port mode slave You may need to reset the appropriate port, Annex subsystem or reboot the Annex for changes to take effect. admin: reset 2 |
A routing table overflow in the terminal concentrator can cause network connections to be intermittent or lost altogether. Symptoms include connection timeouts and routes that are reestablished then disappear, even though the terminal concentrator itself has not rebooted.
The following procedure fixes this problem by establishing a default route within the terminal concentrator. To preserve the default route within the terminal concentrator, you must also disable the routed feature.
The routing table overflow is not a problem for connections made from a host that resides on the same network as the terminal concentrator.
Connect to the terminal concentrator.
# telnet tc_name |
Specifies the name of the terminal concentrator
Press an extra Return after making the connection, and select the command-line interface to connect to the terminal concentrator.
... Enter Annex port name or number: cli annex: |
Type the su command and password.
The default password is the terminal concentrator's IP address.
annex: su Password: |
Start the editor to change the config.annex file.
annex# edit config.annex |
The keyboard commands for this editor are Control-W:save and exit, Control-X:exit, Control-F:page down, and Control-B:page up.
The config.annex file, which is created in the terminal concentrator's EEPROM file system, defines the default route. The config.annex file can also define rotaries that enable a symbolic name to be used instead of a port number.
Add the following lines to the file.
Substitute the appropriate IP address for your default router.
%gateway net default gateway 192.9.200.2 metric 1 active ^W |
Disable the local routed feature.
annex# admin set annex routed n |
Reboot the terminal concentrator.
annex# boot bootfile: <reboot> warning: <return> |
While the terminal concentrator is rebooting, the node consoles are not accessible.
The following example shows how to establish a default route for the terminal concentrator.
admin-ws# telnet tc1 Trying 192.9.200.1 ... Connected to 192.9.200.1. Escape character is '^]'. [Return] Enter Annex port name or number: cli ... annex: su Password: root_password annex: edit config.annex (Editor starts) Ctrl-W:save and exit Ctrl-X:exit Ctrl-F:page down Ctrl-B:page up %gateway net default gateway 192.9.200.2 metric 1 active ^W annex# admin set annex routed n You may need to reset the appropriate port, Annex subsystem or reboot the Annex for changes to take effect. annex# boot |
This section provides the procedures for using the terminal concentrator in a cluster.
Table 2-4 Task Map: Using the Terminal Concentrator
Task |
For Instructions, Go To... |
---|---|
Connect to a node's console through the terminal concentrator |
"How to Connect to a Node's Console Through the Terminal Concentrator" |
Reset a terminal concentrator port |
The following procedure enables remote connections from the administrative console to a cluster node's console by first connecting to the terminal concentrator.
Connect to a node by starting a session with the appropriate terminal concentrator port.
You need to know which terminal concentrator port the node is physically cabled to. See Step 2 in "How to Cable the Terminal Concentrator" for details on determining which terminal concentrator port the node is physically cabled to.
# telnet tc_name tc_port_number |
Specifies the name of the terminal concentrator.
Specifies the port number on the terminal concentrator. Port numbers are configuration dependent. Typically, ports 2 and 3 (5002 and 5003) are used for the first cluster installed at a site.
If you set up node security, you are prompted for the port password.
Log in to the node's console.
After establishing the connection, the system prompts for the login name and password.
Set the terminal type based on the type of window used in Step 1.
# TERM=xterm # export TERM |
The following example shows how to connect to a cluster node in a configuration that uses a terminal concentrator. A Shell tool has already been started by using an xterm type window.
admin-ws# telnet tc1 5002 Trying 192.9.200.1 ... Connected to 192.9.200.1. Escape character is '^]'. [Return] pys-palindrome-1 console login: root password: root_password (for sh or ksh) phys-palindrome-1# TERM=xterm; export TERM (for csh) phys-palindrome-1# set term=xterm |
When a port on the terminal concentrator is busy, that is, in use by a user, you can reset the port to disconnect that user. This procedure is useful if you need to perform an administrative task on the busy port.
A busy port returns the following message when you try to connect to the terminal concentrator.
telnet: Unable to connect to remote host: Connection refused |
If you use the port selector, you might see a port busy message. See "How to Correct a Port Configuration Access Error" for details on the port busy message.
Connect to the terminal concentrator port.
# telnet tc_name |
Specifies the name of the terminal concentrator
Press an extra Return after making the connection and select the command-line interface to connect to the terminal concentrator.
... Enter Annex port name or number: cli annex: |
Type the su command and password.
The default password is the terminal concentrator's IP address.
annex: su Password: |
Determine which port to reset.
The who command shows ports that are in use.
annex# who |
Reset the port that is in use.
annex# admin reset port_number |
Disconnect from the terminal concentrator.
annex# hangup |
You can now connect to the port.
The following example shows how to reset the terminal concentrator connection on port 2.
admin-ws# telnet tc1 Trying 192.9.200.1 ... Connected to 192.9.200.1. Escape character is '^]'. [Return] ... Enter Annex port name or number: cli ... annex: su Password: root_password annex: who Port What User Location When Idle Address 2 PSVR --- --- --- 1:27 192.9.75.12 v1 CLI --- --- --- 192.9.76.10 annex# admin reset 2 annex# hangup |