- Objectives
- Prerequisites
- Introduction
- Management Server Functions
- Section 2.1: Installing and Configuring the Management Server
- Section 2.2: Configuring the Terminal Concentrator
- Section 2.3: Configuring the Solaris JumpStart Server
- Section 2.4: Installing SUNWccon Package on the Administrative Workstation
- Section 2.5: Configuring the Management Server to Administer Cluster Nodes
- Section 2.6: Configuring the Cluster Control Panel
- Appendix A: System Configuration Files
- Appendix B: References
Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
Section 2.2: Configuring the Terminal Concentrator
In this section, we configure the TC for use in the cluster.
NOTE
Some steps for configuring the terminal concentrator (TC) require you to gain physical access to the terminal concentrator and equipment (for example, forcing the TC into Monitor mode). Follow the steps in this section only when performing these steps locally, as during a manual installation.
Step 2.2.1—Preparing to Connect the Serial Cable
For local (manual) installations, prior to connecting the serial cable: Should this be an ordered list?
Ensure the TC power is off.
Connect the cable, noting the serial port (ttyb, is the default) you will be using on the administrative workstation.
As described in Figure 1-1 and Tables 1-1 through 1-5 of the "Guide to Installation - Hardware Setup," a serial cable must be connected from a serial (ttya or b) port on the administrative workstation to port 1 on the TC. Port 1 (configuration port) of the TC is required for performing all local (manual) steps.
NOTE
The next step is not implemented for these hands-on labs. As Figure 1-1 and Tables 1-1 through 1-5 of the "Guide to Installation - Hardware Setup," indicate, serial port "A" of the administrative workstation is connected to the TC (port 1) instead of (default) ttyb.
Step 2.2.2—Linking to the TC
For local (manual) installations, use the UNIX® tip command to communicate with the TC during configuration.
NOTE
Before the tip command will work, you must ensure that the /etc/remote file includes the following lines appended to the end of the file.
annexterm:\
:dv=/dev/term/n:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D
{{In the above line, substitute the serial port letter
you are using for "n" - for example, if using ttyb,
replace "n" with "b", as: "...../dev/term/b....."}}
An easy way create this entry is to simply copy the lines from the hardwire command, then change the entry from hardwire to annexterm—ensure the port letter is correct.
You can use the tip(1) command to connect the cluster administration console I/O with the TC I/O using the parameters specified in this file.
Step 2.2.3—Connecting to the TC
For local (manual) installations, on the administrative workstation, connect to the TC by entering the following command.
clustadm# tip annexterm connected
NOTE
For local (manual) installations, you will not receive a prompt from the TC until you physically power off the TC, power it back on, and within 30 seconds, press and hold the TEST button until the power LED starts flashing, as described in the next step.
Step 2.2.4—Configuring the TC and Verifying Settings
For local (manual) installations, configure the TC device in the following prescribed sequence:
Power on the TC while viewing the front panel and status LED indicators.
After powering on the unit, and within 30 seconds, press and hold the TEST button until the power LED starts flashing.
When the power LED starts to flash, release the TEST button for at least six seconds, then briefly push the TEST button again to initiate diagnostics.
Before proceeding to the next step, ensure that the TC successfully completes (the diagnostic tests take approximately 60 seconds to complete).
Key Practice: Verify that the TC settings are correct. TC firmware options and settings can vary between different TC revision levels; actual options will likely differ from those specified in this hands-on lab. When configuring the TC, refer to the manufacturers documentation to ensure settings are established correctly. Specifically, ensure settings for the TC Internet address, subnet mask, and broadcast address are as indicated in the following steps.
Step 2.2.5—Verifying the TC Settings
For local (manual) installations, when the diagnostic tests are completed, ensure that the Tip window of the administrative workstation appears as follows.
System Reset - Entering Monitor Mode monitor:
NOTE
For the next few steps to configure the TC, the settings should be configurable "as-listed;" however, the TC firmware settings vary from unit-revision to unit-revision. Your actual options may differ. When configuring the TC, refer to the manufacturer's documentation to ensure the settings are established correctly. Specifically, ensure the settings for the TC Internet address, subnet mask, and broadcast address, as indicated in the following steps.
Step 2.2.6—Setting TC Values
For local (manual) installations, use the addr command to set the Internet address, subnet mask, and broadcast address for the TC. To do this, enter the following commands.
System Reset - Entering Monitor Mode
monitor:addr
Enter Internet address [192.40.85.60]:: 192.9.200.4
Enter Subnet mask [255.255.255.0]:: <CR>
Enter Preferred load host Internet address [<any host>]:: <CR>
Enter Broadcast address [129.153.49.255]:: 192.9.200.255
Enter Preferred dump address [0.0.0.0]:: <CR>
Select type of IP packet encapsulation(ieee802/ethernet)
[<ethernet>]:: <CR>
Type of IP packet encapsulation: <Ethernet>
Load Broadcast Y/N:: [N] <CR>
monitor:: sequence
At this point you need to enter a list of 1 to 4 interfaces to
attempt to use for downloading 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:: ~. {{this command ends the tip session}}
The addr command displays and sets several annex TC operating parameters, IP address, subnet mask, preferred load host IP address, load/dump gateway IP addresses, broadcast address, and IP encapsulation type.
The sequence command edits the load/dump interface list. This list determines the order of the network interfaces and determines whether the local area network (LAN) or the SLIP interface will be used by the Annex TC for loading and dumping. The default Ethernet selection is "net," which uses the LAN interface.
The "self" selection specifies that the TC is self-boot configured.
Step 2.2.7—Initializing Changes to the Configuration
For local (manual) installations, the TC must be power cycled for the previous (manual) configuration changes to take effect. To put the changes into effect:
Power off the TC.
Power on the TC and wait approximately 90 seconds for it to configure.
Key Practice: Because port 1 of the TC is the configuration port, minimize security vulnerability by disconnecting the administrative workstation from port 1 of the TC after the configuration. This will prevent unauthorized access to the TC's configuration port.
Default Router Configuration
Though this is not required for these hands-on exercises, if the TC requires access from an adjacent network, the defaultrouter configuration must be performed on each cluster node. This would be performed later, after the Solaris OE installation has completed on each cluster node. At that time, configure the default router information on the cluster nodes by creating the file /etc/defaultrouter and inserting the IP address of your gateway.
The following example shows how to configure the gateway address when the TC requires access from an adjacent network.
192.9.200.254 {{sample gateway address}}
NOTE
In this example, we use the gateway IP address instead of the hostname (see following best practice).
Key Practice: For each node being managed, maintain all IP addresses in one location. Edit the file /etc/defaultrouter and add the hostname of the gateway system. Next, edit the /etc/inet/hosts file and reference the gateway (hostname, IP address, plus an appropriate comment to identify the entry—for example, default gateway). In this manner, you can easily record (and maintain) a complete list of all nodes on the SunPlex platform.
If you want to enable a default route without rebooting and want to verify your new router setting, enter the following commands.
clustadm# route add default 192.9.200.254 {{sample gateway address}}
clustadm# netstat -rn {{look for 192.9.200.254 entry with "ug" flag}}
Step 2.2.8—Completing the Configuration
For local (manual) installations, complete the configuration of the TC by entering the following commands. Enter the data as shown in the following example, where prompted.
clustadm# telnet tc
Trying 192.2.200.4...
Connected to tc.
Escape character is '^]'.
cli
Annex Command Line Interpreter * Copyright 1991 Xylogics, Inc.
annex: su
Password: 192.9.200.4 {{the password defaults to the assigned IP address, but does not echo
to the screen}}
annex# edit config.annex
Ctrl-W: save and exit Ctrl-X: exit Ctrl-F: page down Ctrl-B: page
up
# The following are definitions of the gateway entries
#
%gateway
#
# The following are definitions of the macro entries
#
%macros
%include macros
#
# The following are definitions of the rotary entries
#
%rotary
%include rotaries
<Cntrl>+W #to exit and save
annex# admin
admin: port all
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
reset default port set [y] ? y
admin: quit
annex# hangup {{ends the login session}}
clustadm#
If the TC requires access from an adjacent network, the default router should be included in the config.annex file of the TC.
Key Practice: To avoid security vulnerability, change the default password for the TC. After changing the password, maintain your telnet session with the TC and use another window to telnet to the TC to verify your new password works. A typographical error when entering a password change will render the TC inaccessible. See SunSolve SRDB ID 24989 for resetting a lost root password.
Step 2.2.9—Changing the TC Password
For local (manual) installations, and to avoid security vulnerability, change the TC password, which is similar to changing a UNIX password, as follows:
Telnet to the TC, enter the cli command at the port prompt (to enable the command interpreter).
Enter su, then the default password (the TC IP address).
Enter the passwd command at the prompt and change the default password. Record any changes, and the new password setting.
NOTE
While changing the password is important in the field, for the purpose of these manual procedures, we use the default password. In case the default password is lost, you must enter the erase command to clear the EEPROM contents and then re-enter all data. See the SunSolve article SRDB ID 24989.
Summary of Key Practices
|
Verify the TC settings are correct. TC firmware options/settings can vary between different TC units. Disconnect the administrative workstation (serial port) from the TC (port 1) to avoid security vulnerability. Maintain all IP addresses in a central location for each node being managed. Change the default password of the TC to avoid security vulnerability. |
End of Section 2.2
This completes this section. The TC configuration has been verified.