xCAT Terminal Server HOWTO

The purpose of this document is to describe the options available for the remote text console of  IBM and non-IBM servers.  This document assumes familiarity with xCAT 1.1.8 and the Building a Linux HPC Cluster with xCAT Redbook.

Console Management

xCAT provides a framework for the following remote text console functions:

• Remote OS Console.  Serial OS console requires that the OS support serial redirection.  (e.g. RH or SuSE Linux)
• Remote BIOS/POST Console.  BIOS/POST serial console is only available if the BIOS supports serial redirection and if it is enabled.  (e.g. x330, x335, x345, x360, x342)
• Remote anything with a serial port.  Many infrastructure devices have  a serial port for configuration and management.  (e.g. FastT fiber channel controllers, most high end Ethernet/Gigabit switches, remote power control switches, etc...)

xCAT provide three methods to connect to remote serial ports:

• rtel.  Deprecated.  Reverse Telnet, or just Telnet.  Your basic telnet protocol to a specific port on a terminal server.
• rtty.  Deprecated.  A front end to cu, for direct attached serial port.  Most commonly use with a null modem cable or multi port serial solution.
• conserver.  From http://conserver.com: 

  "Conserver is an application that allows multiple users to watch a serial console at the same time. It can log the data, allows users to take write-access of a console (one at a time), and has a variety of bells and whistles to accentuate that basic functionality. The idea is that conserver will log all your serial traffic so you can go back and review why something crashed, look at changes (if done on the console), or tie the console logs into a monitoring system (just watch the logfiles it creates). With multi-user capabilities you can work on equipment with others, mentor, train, etc. It also does all that client-server stuff so that, assuming you have a network connection, you can interact with any of the equipment from home or wherever."

  Bottom line conserver can access direct attached or terminal servers or a command to access any remote console anyway you like.
  
  I recommend only using conserver.  Conserver is Open Source.  Only Conserver will be mentioned in this document.

The method that you use must be defined in $XCATROOT/etc/nodehm.tab in the cons field.  Do not define it in the mpcons field, mpcons is the text console available through a management processor not a serial port.

Conserver

Conserver is a client-server-based console management solution.  The conserver daemon manages the connections to each console.  The console command is used to connect to a conserver daemon to obtain access to a remote console.

xCAT support for conserver is defined by two files:

• $XCATROOT/etc/conserver.tab.  This table defines the relationship between conserver daemon and the console command.  Usually localhost is the correct entry for the conserver daemon.  If you require that a conserver daemon run elsewhere, then change localhost to the hostname or IP address of the host running conserver.
  
  This table is formatted:
  
  nodename<tab>conserver hostname,nodename as defined by conserver.cf, e.g.:
  
  node1    localhost,node1
  node2    foobar.foo.bar,uta45
  node3    mgmt2,node3
   
• $XCATROOT/etc/conserver.cf.  This table defines each of the consoles to be managed by Conserver and their method of access.  This table is fully documented in the conserver.cf man page (type: man conserver.cf) and is required only for the server running the conserver daemon.

Terminal Servers

The following table describes the key features available for each terminal server described in this document.

• DHCP and BOOTP are important when setting up new or replacement terminal servers.  Terminal servers lacking this capability require extra effort when defining the IP address.

• Telnet is the most popular method of accessing remote consoles.  Most terminal servers provide a different TCP port per physical port.

• SSH functions similar to telnet, but is encrypted.

• Direct attached is used only by multi port solutions with device drivers.  This is the most troublesome way to access a remote console, however there are advantages to having complete control over all the serial signals, but none I can think of with respect to remote console.

• Setup indicates that xCAT has an automated procedure for the setup of the terminal server.

• Ports/U indicates the number of ports per U (1.75") of space.

HOWTO For All Terminal Servers

1. Assign a hostname for each terminal server in /etc/hosts.
2. Create an entry in $XCATROOT/etc/nodelist.tab (remember EVERYTHING in xCAT is a node).
3. Type:
   
   makedns

iTouch/InReach IR Series

1. Reset each unit to factory settings.  (RTFM).

2. For each terminal server assign an IP.  You have two options:
   
   BOOTP (recommended)
   
   

   1. For each terminal server, note the MAC address printed on the outside of the unit and enter manually in $XCATROOT/etc/mac.tab, e.g.:
      
      ts1    12:34:56:78:90:ab
       
   2. If you do not have a PC flash card, then each IR Series requires an $XCATROOT/etc/nodehm.tab entry to define the location of the IR Series firmware:
      
      ts1    NA,NA,NA,NA,NA,NA,NA,NA,NA,file:NEMC_IR.SYS,NA,NA,N,NA
      
      The file NEMC_IR.SYS can be obtained from http://mrv.com and must be placed in /tftpboot.
       
   3. Type:
      
      makedhcp (noderange of terminal servers, e.g. ts1-ts4).
       
   4. Reboot each IR.

   Manual
   
   

   1. Each IR Series must contain a PC flash card.
   2. Attach a serial cable to the local management port on the unit (this will be the highest numbered port). Connect this to a serial terminal, terminal emulator, or a serial port on your server node.  Connect at 9600 baud, and set up the IP address following this example:
      
      login> access
      Enter username> system
      > set priv
      password> system
      > define server ip address 10.1.1.1
      > define server ip subnet mask 255.255.0.0
      > define server IP primary gateway address 10.0.2.254
      > init
       

3. For each IR type:
   
   setupir (terminal server hostname)
    

4. $XCATROOT/etc/conserver.cf entries should look like this:
   
   node01:!ts1:2100:&:
   
   If you encounter problems with function and arrow key interaction with serial BIOS try changing the line to:
   
   node01:|telnet ts1 2100::&:
   
   The IR Series port numbers start with 2100 and increment 100 for every port (e.g. port 2 is 2200).

iTouch/InReach LX Series

1. Reset each unit to factory settings.  (RTFM).

2. For each terminal server assign an IP.  You have two options:
   
   DHCP (recommended)
   
   

   1. For each terminal server, note the MAC address printed on the outside of the unit and enter manually in $XCATROOT/etc/mac.tab, e.g.:
      
      ts1    12:34:56:78:90:ab
       
   2. Type:
      
      makedhcp (noderange of terminal servers, e.g. ts1-ts4).
       
   3. Reboot each LX.

   Manual
   
   

   1. Attach a serial cable to the local management port on the unit (this will be the highest numbered port). Connect this to a serial terminal, terminal emulator, or a serial port on your server node.  Connect at 9600 baud, and set up the IP address following this example:
      
      RTFM
       

3. Update Firmware to 2.2.1.  Use show version from a LX prompt to determine if you need to update.  e.g.:
   
   telnet (hostname terminal server)
   Login: InReach or iTouch
   Password: access
   InReach:0 >enable
   Password: system
   InReach:0 >>show version
   
   Software Version must be 2.2.1.
    

   1. Obtain the files ppciboot.img and linuxito.img from http://www.mrv.com and place in /tftpboot.
   2. For each LX type:
      
      telnet (hostname terminal server)
      Login: InReach or iTouch
      Password: access
      InReach:0 >enable
      Password: system
      InReach:0 >>update software (IP address of management/tftp server)
      InReach:0 >>update ppciboot (IP address of management/tftp server)
      InReach:0 >>reload
       
   3. Remove files ppciboot.img and linuxito.img from /tftpboot.
       
4. For each LX type:
   
   setuplx (terminal server hostname)
   
   

5. $XCATROOT/etc/conserver.cf entries should look like this:
   
   node01:!ts1:2100:&:
   
   If you encounter problems with function and arrow key interaction with serial BIOS try changing the line to:
   
   node01:|telnet ts1 2100::&:
   
   The LX Series telnet port numbers start with 2100 and increment 100 for every port (e.g. port 2 is 2200).
   
   For using SSH entries should look like this:
   
   node01:|ssh -p 2122 ts1::&:
   
   The LX Series SSH port numbers start with 2122 and increment 100 for every port (e.g. port 2 is 2222).

Equinox ELS

1. Reset each unit to factory settings.  (RTFM).

2. For each terminal server assign an IP.  You have two options:
   
   Automated (recommended)
   
   

   1. Attach a serial cable to port 1.  Connect this to serial port A or 1 on your management server node.
   2. Type:
      
      setupelsip (terminal server hostname)
      
      If you must connect to serial port B or 2 on your management server node, then type:
      
      setupelsip (terminal server hostname) ttyS1

   Manual
   
   

   1. Attach a serial cable to port 1.  Connect this to a serial terminal, terminal emulator, or a serial port on your server node.  Connect at 9600 baud, and set up the IP address following this example:
      
      Enter username>root
      Local>set priv
      Password>system
      Local>>change server ip 10.1.1.1
      Local>>change server subnet mask 255.255.0.0
       

3. For each ELS type:
   
   setupels (terminal server hostname)
    

4. $XCATROOT/etc/conserver.cf entries should look like this:
   
   node01:!ts1:3001:&:
   
   If you encounter problems with function and arrow key interaction with serial BIOS try changing the line to:
   
   node01:|telnet ts1 3001::&:
   
   The ELS port numbers start with 3001 and increment 1 for every port (e.g. port 2 is 3002).

Equinox ESP (Red Hat Support Only)

1. Reset each unit to factory settings.  (RTFM).
2. Install ESP device driver.  Obtain from http://equinox.com.  NOTE:  Your kernel tree must be prepared correctly.
3. The ESP install RPM will have put entries in rc.local--not good, since we need this up an running before the conserver daemon starts, and rc.local is run last on boot.  The command setupxcat will clean this up, or you can manually remove the added lines, and then copy the $XCATROOT/rc.d/espx startup script to /etc/rc.d/init.d.
4. Type:
   
   chkconfig --level 345 espx on
   service espx stop
   rmmod espx
   service espx start
    

5. For each ESP assign an IP.  You have two options:
   
   DHCP
   
   

   1. For each terminal server, note the MAC address printed on the outside of the unit and enter manually in $XCATROOT/etc/mac.tab, e.g.:
      
      esp1    12:34:56:78:90:ab
       
   2. Type:
      
      makedhcp (noderange of ESPs, e.g. esp1-esp4).
       
   3. Reset each ESP.  Validate that DHCP worked with a simple ping test.  If DHCP fails, try the manual method.

   Manual (recommended)
   
   

   1. RTFM.

    

6. RTFM for the setup of each ESP.
7. Type:
   
   service espx stop
   rmmod espx
   service espx start
    
8. $XCATROOT/etc/conserver.cf entries should look like this:
   
   node01:/dev/ttyQ01e0:9600p:&:
   
   Each ESP tty device is prefixed with ttyQ, the next 2 numbers are the ESP unit number starting with 01, then the letter 'e', then the port number 0-f.  The next field is the line speed, read the conserver.cf man page for details.

Equinox CPS

1. Reset each unit to factory settings.  (RTFM).

2. For each terminal server assign an IP.  You have two options:
   
   DHCP (recommended)
   
   

   1. For each terminal server, note the MAC address printed on the outside of the unit and enter manually in $XCATROOT/etc/mac.tab, e.g.:
      
      cps1    12:34:56:78:90:ab
       
   2. Type:
      
      makedhcp (noderange of terminal servers, e.g. ts1-ts4).
       
   3. Reboot each CPS.

   Manual
   
   

   1. RTFM
       
3. For each CPS type:
   
   setupcps (CPS hostname)
   
   

4. $XCATROOT/etc/conserver.cf entries should look like this:
   
   node01:!cps1:3001:&:
   
   If you encounter problems with function and arrow key interaction with serial BIOS try changing the line to:
   
   node01:|telnet cps1 3001::&:
   
   The CPS port numbers start with 3001 and increment 1 for every port (e.g. port 2 is 3002).

Cyclades

TBD.

Support

http://xcat.org

Egan Ford
egan@us.ibm.com
January  2003