10.1 Connecting to the Solstice HA Server Console

You can perform administrative tasks from a window connected to either Solstice HA server. The procedures for initial set up of a terminal concentrator and how to set up security can be found in the SPARCcluster High Availability Software Planning and Installation Guide and in the terminal concentrator documentation.

The following procedure tells you how to create connections from the administrative workstation in a Solstice HA configuration.

· How to Connect to the Solstice HA Server Console

1. Open a shelltool(1) window on the desktop of the administration workstation.

2. Note the size of the shelltool window.

   Run the tput(1) command and note the size of the shelltool window. This number will be used in Step 6.

# tput lines 35 #

3. Open a telnet(1) connection to one of the Solstice HA servers through the terminal concentrator.

   Run the following command to open the telnet connection to a server in a window.

# telnet terminal_concentrator_name 5002 Trying 192.9.200.1 ... Connected to 192.9.200.1. Escape character is '^]'.

4. Optionally, open another shelltool window and run the following command to open a telnet connection to the other server.

# telnet terminal_concentrator_name 5003 Trying 192.9.200.1 ... Connected to 192.9.200.1. Escape character is '^]'.

---

Note - If you set up security as described in the SPARCcluster High Availability Software Planning and Installation Guide, you will be prompted for the port password. After establishing the connection, you will be prompted for the login name and password.

---

5. Login to the server.

Console login: root Password: root_password

6. Reset the terminal rows attribute to the number found in Step 2. You will use the stty(1) command for this procedure.

   A problem exists with the default shelltool size and the size reported by the console terminal type. By entering the following, the information these two values will agree.

# stty rows 35

10.2 Resetting Terminal Concentrator Connections

This section contains instructions for resetting the terminal concentrator connection.

If another user has a connection to the Solstice HA server console port on the terminal concentrator, you can reset the port to disconnect that user. This procedure will be useful if you need to immediately perform an administrative procedure.

If you cannot connect to the terminal concentrator, the following message will be displayed:

# telnet xx-tc 5002 Trying 192.9.200.1 ... telnet: Unable to connect to remote host: Connection refused #

If you use the port selector, you may see a port busy message.

· How to Reset a Terminal Concentrator Connection

1. Connect to the terminal concentrator and select the command line interface (cli). Remember to press an extra return after making the connection.

# telnet xx-tc Enter Annex port name or number: cli

2. Enter the su command and passwd.

   By default, the password is the IP address of the terminal concentrator.

annex: su Password:

3. Discover which port you want to reset.

   The port in this example is port 2. Use the terminal concentrator's built-in who command to show connections.

annex# who

4. Reset the port.

   Use the terminal concentrator's built-in reset command to reset the port. This example breaks the connection on port 2.

annex# admin reset 2

5. Disconnect from the terminal concentrator.

annex# hangup

6. Reconnect to the desired port.

# telnet xx-tc 5002

10.3 Entering the OpenBoot PROM

This section contains information for entering the OpenBoot PROM from the terminal concentrator.

· How to Enter the OpenBoot PROM on a Solstice HA Server

1. Connect to the desired port.

# telnet xx-tc 5002 Trying 192.9.200.1 ... Connected to 129.9.200.1 . Escape character is '^]'.

2. Enter the telnet command mode by typing the telnet escape character.

^] telnet>

3. Send a break to the server.

telnet> send brk

4. You may now execute the OpenBoot commands.

10.4 Troubleshooting the Terminal Concentrator

Terminal concentrator connections made through a router can exhibit an intermittent problem.

Connections from a host that resides on the same network as the terminal continue to work normally. However, connections to the terminal concentrator via a router display a random interruption. These connections may come alive for random periods, then go dead again. When the connection is dead, new terminal concentrator connection attempts will timeout. The terminal concentrator shows no signs of rebooting.

The diagnosis of this problem is that with routed traffic for many routes on your network you may encounter terminal concentrator routing table overflow and loss of the route to one or more networks. This problem will not occur for connecting hosts on the same network as the terminal concentrator, but rather it will occur for hosts reaching the terminal concentrator through a router. Later routed traffic may re-establish a needed route only to disappear again later.

The solution to this problem is to establish a default route within the terminal concentrator and disable the routed feature. The routed feature must be disabled to prevent the default route from being lost.

The following procedure shows how this can be done. The file config.annex is created in the terminal concentrator's EEPROM file system and defines the default route to be used. The config.annex file can also be used to define rotaries which allow a symbolic name to be used instead of a port number. The routed feature is disabled using the terminal concentrator's set command.

1. Open an xterm(1) connection to the terminal concentrator.

# telnet xx-tc Trying 192.9.200.2 ... Connected to xx-tc. Escape character is '^]'. Rotaries Defined: cli - Enter Annex port name or number: cli Annex Command Line Interpreter * Copyright 1991 Xylogics, Inc.

2. Enter the su command and administrative password. By default, the password is the IP address of the terminal concentrator.

annex: su Password: administrative_password

3. Edit the config.annex file.

   When the terminal concentrator's editor starts, you will see the following message:

annex# edit config.annex

Enter the information that is highlighted in the following example, substituting the appropriate IP address for your default router.

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

4. Disable the local routed.

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#

5. Reboot the terminal concentrator.

annex# boot