11.1 Configuring the Terminal Concentrator

1. Edit the contents of the /etc/remote file on the administration workstation, and create the following line.

a:dv=/dev/term/a:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D:

2. From the administration workstation, type the following command to connect the workstation serial port, TTYA to terminal concentrator port 1:

# tip a

---

Note - Your administration workstation may have a combined serial port labeled SERIAL A/B. In this case, you cannot use the TTYB port without the appropriate splitter cable. See the documentation supplied with your workstation for more information.

---

3. Verify the server is powered on and the cabinet key switch is in the ON position.

4. Reset the terminal concentrator.

   Depress the Test button for three or more seconds until the Power LED blinks rapidly. Release the button. See Figure 11-1.

Figure 11-1

5. Within 30 seconds, press the Test button (again) on the unit front panel.

---

Note - Verify that the orange test LED lights to ensure the unit is in test mode.

---

The terminal concentrator performs a self-test, which lasts about 30 seconds. Messages are displayed on the terminal screen. If a message denotes the network connection is not found, press the q key to stop the message. This message appears because you have not yet connected a network cable. Check connection to the public Ethernet to verify that it is connected correctly.

When terminal concentrator boot completes successfully, the front panel LEDs light as shown:

Power (Green)	Unit (Green)	Net (Green)	Attn (Amber)	Load (Green)	Active (Green)
ON	ON	ON	OFF	OFF	Intermittent blinking

If boot fails, the LEDs on the front panel may light in one of these modes:

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 mor	e Status LEDs (1-8) ar		e ON

If the LEDs denote another mode of failure, refer to the SPARCcluster High Availability Service Manual.

6. Upon successful power-on, the monitor:: prompt appears. Use the addr command to assign an IP address, subnet mask, and network address to the terminal concentrator.

   In the prompt which follows, the broadcast address is the administration workstation address with the host portion set to 255 or all ones.

monitor:: addr Enter Internet address [192.5.101.10]::IP address of terminal concentrator Enter Subnet mask [255.255.255.255]:: subnet mask Enter preferred load host Internet address [<any host>]::<return> Enter Broadcast address [192.5.101.0]::your network broadcast address Enter preferred dump address [192.5.101.10]:: Select type of IP packet encapsulation (ieee802/ethernet) [<ethernet>]::<return> Type of IP packet encapsulation: <ethernet> Load Broadcast Y/N [Y]:: monitor::

7. Verify that the terminal concentrator boots from itself instead of the network.

   To do this, type the commands at the monitor:: prompt and press Return after verifying the correct settings, shown below:

monitor:: seq Enter a list of 1 to 4 interfaces to attempt to use for downloading code or upline dumping. Enter them in the order they should be tried, separated by commas or spaces. Possible interfaces are: Ethernet: net SELF: self Enter Interface sequence [net]:: self Interface sequence: self monitor:: image Enter Image name ["oper.52.enet"]:: <return> Enter TFTP Load directory ["[]" ]:: <return> Enter TFTP Dump path/filename ["dump.192.5.101.10]::<return> monitor::

8. If you are using tip, quit the program by pressing Return and typing:

monitor:: <return> monitor:: ~.

9. Use the power switch on the back of the terminal concentrator to turn the terminal concentrator off momentarily, and then on again.

   A power cycle will reboot the terminal concentrator. The terminal concentrator is ready when the Load light on the front panel goes off.

---

Note - For more information about commands available on the terminal ^(R) concentrator, see the Xylogics manuals that came with your server.

---

10. Disconnect the serial cable from the administration workstation.

    The cable is no longer needed. Store it under the terminal concentrator using the reusable tie wrap. Leave one end connected to Port 1 on the terminal concentrator.

    Caution - Do not connect outside devices, other than those described in this manual, to the terminal concentrator. Significant performance problems can occur if external devices are connected.

11.2 Checkpoint to Verify Terminal Concentrator Setup

Verify your installation up to this point. If any verification procedure fails, refer to the SPARCcluster High Availability Server Service Manual.

* Ping the terminal concentrator over the network by typing:

# ping name of terminal concentrator

11.3 Setting the Port Parameters

The type variable for each port must be set to dial_in. If it is set to hardwired, cluster console may be unable to detect when a port is already in use. The next section explains how to determine if the port type variable must be set.

11.3.1 Determining if the Port Type Variable Must Be set.

Perform this procedure to see if you must set the port variable.

1. Find the Sun label on top of the terminal concentrator.

   It is on the top panel of the unit. See Figure 11-2.

2. Examine the serial number to see if it is in the lower serial number range.

   The serial number consists of seven digits, followed by a dash and ten more digits.

   If the numbers after the dash start with 9520 or higher, the port type variable is set correctly -- no action required.

   If the numbers after the dash start with 9519 or lower, the port type variable must be changed.

3. If you must change the port type variable, do so using the procedure found in Section 11.3, "Setting the Port Parameters."

11.3.2 Port Parameters Procedure

Using an administration workstation, perform these steps to set the port parameters.

---

Note - Make sure that the terminal concentrator is powered on and has completed boot-up.

---

admin-ws# telnet planets-tc Trying 192.5.101.10 Connected to planets-tc. Escape character is '^]'. Rotaries Defined: cli - Enter Annex port name or number: cli Annex Command Line Interpreter * Copyright 1991 Xylogics, Inc. annex: su Password: type the password annex# admin Annex administration MICRO-XL-UX R7.0.1, 8 ports admin : set port=1-8 type dial_in You may need to reset the appropriate port, Annex subsystem or reboot the Annex for changes to take effect. admin : quit annex# boot bootfile: <return> warning: <return>

---

Note - This will cause the terminal concentrator to reboot. Thus, the terminal concentrator will be unavailable for about a minute.

---

11.4 SPARCcluster Acceptance Test

At this point, establish an important installation milestone. Completion and sign-off of this acceptance test by both the installer and the site client is a mutual declaration that operational acceptance of all nodes of the cluster hardware with associated components, cabling and installation is completed, checked, and approved.

Perform the acceptance test after

• All hardware is installed and cabling complete
• The Solaris operating system is installed, including

  · Installation of the system administration workstation

  · Configuration of the terminal concentrator

Perform the acceptance test using the procedures presented in the following sections.

11.4.1 SunVTS

SunVTS is one of the on-line diagnostics tool for SPARCcluster High Availability servers. Refer to Section 11.4.1.2, "Running SunVTS."

A utility within SunVTS, vtsprobe, is used to verify installation of system hardware, SPARCstorage Arrays, private net devices, network and interfaces. See Section 11.4.1.1, "Verifying Hardware Installation."

---

Caution - Run SunVTS only while no high availability software is running. Use SunVTS at this stage only to verify that the hardware configuration is correct. Do not attempt to use SunVTS to validate software configuration. If you run SunVTS while high availability software is running, unpredictable results will occur.

---

---

Note - SunVTS must be run separately on each node. There is no provision for running SunVTS on both nodes at the same time. When you are done running SunVTS on one node, you must then repeat the process on the other node.

---

11.4.1.1 Verifying Hardware Installation

To verify hardware configuration, the following three prerequisites must be satisfied. Both nodes must have:

1. Solaris 2.4 Hardware: 3/95 installed.

2. SPARCstorage Array package installed.

3. SUNWvts package installed.

Perform the following steps on a selected node, then return to this point and repeat this procedure on the other node:

1. Become superuser and then change directories as follows:

# cd /opt/SUNWvts/bin

2. Set the following environment variables:

   For a Bourne shell:

# BYPASS_FS_PROBE=1;export BYPASS_FS_PROBE

For a C shell:

% setenv BYPASS_FS_PROBE 1

3. Become superuser and then enter the following command:

# ./vtsk

Executing the ./vtsk command starts the SunVTS kernel. The SunVTS kernel then probes system devices and awaits commands from an interface.

---

Note - The following error message may be displayed if you are executing the ./vtsk command for the second time, such as when directed to in the final step of this procedure.

---

# vtsk: SunVTS kernel is already running

If this error message occurs, enter the following:

# ps -ef|grep vtsk (find process id of vtsk) # kill -INT <vtsk pid> # ./vtsk

4. Wait a few minutes to allow vtsk to finish probing the system and then initiate a probe_map file using the vtsprobe command. As shown in the following example, the output, which can be lengthy, is redirected to a file for later viewing. The vtsprobe command without modifiers will produce a console screen output.

# ./vtsprobe > /tmp/probe_map

5. Verify that the response to the vtsprobe command is similar to the following for the private net devices:

---

Note - The data listed in the following example is obtained before the private net is configured.

---

Network beo(nettest) Port Address: Unknown Host ID: 80500419 Domain Name : nn.nn.nn.com be1(nettest) Port Address: Unknown Host ID: 80500419 Domain Name : nn.nn.nn.com

If the data listed for the private net devices does not match the build configuration, check and correct any cabling errors and then repeat steps 1 through 5.

6. Verify that there is a response (under the Network heading) to the vtsprobe command for any network interface devices that you have installed.

   For example, if you have installed an SBus Quad Ethernet Controller there should be corresponding qe entries. Consult documentation supplied with your network interface card to determine the correct entry for your device.

7. Verify that the response to the vtsprobe command is similar to the following for the SPARCstorage Arrays:

pln0(plntest) Worldwide Name: 08002018375f Disks Attached: c1t0d0 c1t0d1 c1t1d0 c1t1d1 c1t2d0 : c1t2d1 c1t3d0 c1t3d1 c1t4d0 c1t4d1 : c1t5d0 c1t5d1 pln1(plntest) Worldwide Name: 0800201cad8e Disks Attached: c2t0d0 c2t0d1 c2t1d0 c2t1d1 c2t2d0 : c2t2d1 c2t3d0 c2t3d1 c2t4d0 c2t4d1 : c2t5d0 c2t5d1

If the data listed for the SPARCstorage Arrays does not match the build configuration, check and correct any cabling errors and then repeat steps 1 through 7.

8. Verify that the response to the vtsprobe command is similar to the following for each disk listed under a SPARCstorage Array:

SparcStorageArray(pln0) c1t0d0(rawtest)<--- logical name(test name) Logical Name: c1t0d0 Capacity: 1002.09MB Controller: pln0 c1t0d1(rawtest)<--- logical name(test name) Logical Name: c1t0d1 Capacity: 1002.09MB Controller: pln0 c1t1d0(rawtest)<--- logical name(test name) Logical Name: c1t1d0 Capacity: 1002.09MB Controller: pln0

If the data listed for the disks does not match that shown under the corresponding SPARCstorage array entry, check and correct the cabling and then repeat steps 1 through 8.

9. Compare the probe_maps generated by each node. Check and verify WWN of each SPARCstorage array. Check and compare disk logical name and capacity for all disks under corresponding SPARCstorage array. If there is not an identical match, replace the SPARCstorage array controller and/or disks if necessary.

10. To run a final system functional check, run SunVTS using the procedure in Section 11.4.1.2, "Running SunVTS."

11.4.1.2 Running SunVTS

To run a final functional test of the system using SunVTS:

1. Become superuser and then change directories as shown in the following example:

# cd /opt/SUNWvts/bin

2. Enter:

# ./sunvts

If the system does not have a frame buffer, a TTY base SunVTS control panel will be displayed. After the TTY interface comes up, direct the cursor to the "start" button and use RETURN to start SunVTS system testing. Allow for one system pass of the SunVTS run. For details of how to run SunVTS, refer to SunVTS User's Guide, Part Number 801-7271.

11.4.2 Acceptance Test Criteria

This acceptance test has completed successfully if the data listed for all hardware components match the corresponding build configurations.

If this statements are not true, the system has failed acceptance test.

11.5 What's Next

Hardware and basic software installation are complete. Return to the SPARCcluster High Availability Server Software Planning and Installation Guide, 802-3509, Chapter 6 and finish loading software packages.