Once cluster hardware and networking is configured as required, CSM software must be installed and configured to enable remote console functions. The installms command installs the required csm.server package, including the /opt/csm/bin/rconsole remote console command, on the management server. For detailed CSM installation instructions, see the IBM CSM for Linux: Software Planning and Installation Guide. For detailed command usage information, see the installms, rconsole, and definenode man pages or the IBM CSM for Linux: Administration Guide.
The CSM management server communicates with the specific console server types described in this book through the provided console server commands. The management server can communicate with other console server types through customized programs and scripts. Each program or script must communicate to the console server, make the request for the console functions, and return the action request results to the user.
IBM supports CSM remote console software environments for the following third-party console server types:
The rconsole ConsoleMethod attribute specifies the
software environment used for remote console: cps,
computone, conserver, els, or
esp. Each ConsoleMethod type also has a
corresponding ConsoleMethod_console command that the
rconsole command communicates with to control remote console
functions. The following table describes the console server types that
can be used with CSM, and their associated console method attribute and
command.
Table 3. Console server attributes
Console server type | ConsoleMethod value | ConsoleServerNum value | ConsolePortNum value |
---|---|---|---|
Equinox ELS-16 II | els | not applicable | 1-16 |
Equinox ESP-8; ESP-16 | esp | 1 or more (returned by espcfg) | 0-7; 0-f |
other | conserver | not applicable | not applicable |
Computone IntelliServer RCM8, RCM24, and RCM48 | computone | not applicable | 1-8; 1-24; 1-48 |
Avocent CPS1600 | cps | not applicable | 1-16 |
For more information about these console servers, see the product Web site URLs in Related information.
Remote console depends on file changes being made on each node to direct the console to the node's serial port. These changes, shown in the two examples below, are made automatically when the csm.client package is installed on a node. Remote console is activated when the following lines of code in bold text have been added to the lilo.conf, grub.conf, and inittab files during csm.client installation:
boot=/dev/sda map=/boot/map install=/boot/boot.b prompt timeout=50 message=/boot/message linear default=linux serial = 1,9600n8 append = "console=tty1 console=ttyS1,9600" image=/boot/vmlinuz-2.4.2-2smp label=linux initrd=/boot/initrd-2.4.2-2smp.img read-only root=/dev/sda8 image=/boot/vmlinuz-2.4.2-2 label=linux-up initrd=/boot/initrd-2.4.2-2.img read-only root=/dev/sda8
# grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/sda5 # initrd /initrd-version.img #boot=/dev/sda default=0 serial = 1,9600n8 append = "console=tty1 console=ttyS1,9600" timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz title Red Hat Linux (2.4.7-10smp) root (hd0,0) kernel /vmlinuz-2.4.7-10smp ro root=/dev/sda5 initrd /initrd-2.4.7-10smp.img title Red Hat Linux-up (2.4.7-10) root (hd0,0) kernel /vmlinuz-2.4.7-10 ro root=/dev/sda5 initrd /initrd-2.4.7-10.img
s1:345:respawn:/sbin/agetty 9600 ttyS1 xterm
See the IBM CSM for Linux: Software Planning and Installation Guide for software installation details.
Attention! |
---|
The hardware configuration tips in this section are provided as a convenience only. These tips are not a replacement for reading and using the installation and configuration documentation provided with the specified remote console hardware. |
ELS configuration
change server ip <desired IP address of ELS> change server subnet mask <desired mask> change node gw ip <default gateway IP address> gateway en
For example:
change server ip 123.45.67.89 change server subnet 255.255.255.0 change node gw ip 123.45.67.1 gateway en
define port 1-16 access remote define port 1-16 flow control xon define port 1-16 speed 9600 lo port 1-16
ESP configuration
The ESP console device requires the installation of software and drivers that are shipped with the device. Once these are installed the device can be configured using the espcfg command. Refer to the ESP device installation instructions for details.
CPS configuration
The CPS 1610 console device requires a firmware level of 1.5 or higher to work properly with CSM remote console.
SERVER SET IP=<CPS IP Address> MASK=<subnet mask> GATEWAY=<Default gateway IP address>
SERVER SECURITY AUTHENTICATION=NONE
A CPS device does not require explicit configuration to set the ports to Reverse Telnet mode. However, by default the CPS serial Command Line Interface (CLI) is enabled on CPS port 1. Any CPS ports that have the CLI enabled cannot be used for Reverse Telnet, and therefore will not work with CSM remote console. If the default CLI setting is not changed, CPS port 1 will not be available for remote console access. See the CPS documentation for information on the CLI settings.
Computone configuration
The Computone console device requires a firmware level of 1.6.002 or higher to work with CSM remote console.
set ether address <Computone IP Address>/<# of bits in mask>
The device's IP address and subnet mask are entered in a single string. The subnet mask is entered as the number of bits that are set in the mask, and is appended to the IP address by a forward slash (/). Each of the four parts of the subnet mask is composed of eight bits, for a possible maximum of 32 bits set. For example, if the subnet mask is 255.255.255.0, the number of bits set is 8 + 8 + 8 + 0 = 24 bits. If the mask is 255.255.255.192, the number of bits set is 8 + 8 + 8 + 2 = 26 bits. If the device IP address is 123.45.67.89, and the subnet mask is 255.255.255.192, then you would enter the following command:
set ether address 123.45.67.89/26
set gateway 0 destination 0.0.0.0 gateway <Default Gateway IP address>/<# of bits in mask>
The gateway address requires the subnet mask also, and is entered as it was for the device IP address in step 4. If the gateway address is 123.45.67.1, and the subnet mask is 255.255.25.192, enter the command:
set gateway 0 destination 0.0.0.0 gateway 123.45.67.1/26
set port 1 type "reverse tcp"
Repeat this step for ports 2 - 8. Note that Computone refers to Reverse Telnet as "Reverse TCP".
set apps telnetd enabled
Conserver configuration
Conserver is an open source package that adds features to console management. Details are available at the Conserver Web site (see Related information). To use Conserver with CSM remote console, the Conserver source code must be downloaded and compiled. The resulting Conserver daemon must be run on the management server, and the Conserver configuration file conserver.cf must be modified to include entries for each of the consoles that will be managed by Conserver. The node names for these entries must match the Hostname attribute in the CSM database, and the ConsoleMethod attribute for each node must be set to "conserver".
CSM remote console uses a ConsoleMethod_console command which specifies the type of console servers used in the cluster. When new nodes are defined in the cluster using the definenode command, a ConsoleMethod attribute is set for each new node in the CSM database. The ConsoleMethod attribute dictates which ConsoleMethod_console command rconsole will use for each node.
The ConsoleServerName attribute value specifies the short host name, long host name, or IP address of the console server used for the node.
The ConsoleServerNumber attribute (applicable to Equinox ESPs only) is the number assigned by the Equinox configuration tool when the ESP console is defined. The attribute value is passed from the rconsole command to the esp_console command corresponding to the target node. The attribute value must be the sequence number assigned to the Equinox ESP providing remote console for the target node. The espcfg command displays the current sequence number value.
The console port number ConsolePortNum attribute is passed from the rconsole command to the ConsoleMethod_console command to contact the target node. The console port number is the physical port that the node's serial port is connected to in the console server hardware. See Table 3 for the console server types that can be used with CSM and the ConsoleMethod attribute and ConsoleMethod_console command required for each type.
If console server types other than those listed in Table 3 are used, then additional software and configuration is required to enable remote console functions. The ConsoleMethod, ConsoleServerName, ConsoleServerNumber, and ConsolePortNum attributes for each node must be set to the values expected by the corresponding ConsoleMethod_console command. For example, if the ConsoleMethod attribute for a console server is set to termservX, then rconsole would attempt to run /opt/csm/bin/termservX_console to carry out remote console requests.
To use other console servers with CSM the following steps are required. In this example, termservX is used as the ConsoleMethod node attribute value. The termservX_console command is used by the rconsole command to connect to the target node. The console method must print the ConsoleMethod_console command required to connect to the target node through the console server.
To ensure that the cluster is configured correctly, all remote console hardware control functions should be tested before using them in a production environment. Run the rconsole command to verify that all nodes are configured correctly and are responding accordingly. See the rconsole man page or the IBM CSM for Linux: Administration Guide for detailed examples.
lsnode -l
Output for each node in the cluster is similar to:
ManagementServer = csmlinux.pok.ibm.com Mode = PreManaged Name = clsn02.pok.ibm.com NodeNameList = {csmlinux.pok.ibm.com} PowerMethod = netfinity PowerStatus = on Status = on UniversalId = 0 UpdatenodeFailed = 0 ------------------- Hostname = clsn03.pok.ibm.com AllowManageRequest = 0 (no) CSMVersion = ConfigChanged = 0 (no) ConsoleMethod = esp ConsolePortNum =a ConsoleServerName = clsn03.pok.ibm.com ConsoleServerNumber =1 HWControlNodeId = ppsclnt3_NODEID HWControlPoint = clsn03.pok.ibm.com HWModel = HWSerialNum = HWType = InstallAdapterDuplex = InstallAdapterMacaddr = 00:00:00:00:00:00 InstallAdapterSpeed = InstallAdapterType = InstallCSMVersion = 1.2.0 InstallDisk = InstallDiskType = InstallDistributionName = RedHat InstallDistributionVersion = 7.2 InstallKernelVersion = InstallMethod = kickstart InstallOSName = Linux InstallPkgArchitecture = i386 LParID = LastCFMUpdateTime = ManagementServer = csmlinux.pok.ibm.com Mode = PreManaged Name = ppsclnt3.pok.ibm.com NodeNameList = {csmlinux.pok.ibm.com} PowerMethod = netfinity PowerStatus = 128 on Status = 127 on UniversalId = 0 UpdatenodeFailed = 0
lsnode -l clsn03
Output should include:
ConsoleServerName = clsn03.pok.ibm.com ConsoleMethod = esp ConsoleServerNumber = 1 ConsolePortNum = a
rconsole -n clsn03,clsn09,clsn15,clsn19
rconsole -a
rconsole -N nodegrp1, nodegrp2
rconsole -t -n clsn03
The following examples show problems and solutions for specific instances of using remote console:
export RCONSOLE_FONT=fixed