Chapter 2. Configuring IRISconsole

This chapter describes various tasks that you must perform to install and perform the initial configuration of IRISconsole software. The major sections in this chapter are as follows:

Installing IRISconsole Software

To install IRISconsole software, install these subsystems:

oe.sw.uucp

UUCP software required by IRISconsole software

 

sgitcl_eoe.sw.base

Tcl toolkit software required by IRISconsole software

 

sgitcl_eoe.sw.tm

Tcl toolkit software required by IRISconsole software



Note: You must choose the sts.xx.xx subsystems or the el_serial.xx.xx subsystems, or both, depending upon which multiplexer(s) your site is using.


sts.sw.base

Multiplexer software

sts.man.man

Reference pages for multiplexer software

sts.man.relnotes

Release notes for multiplexer software

IRISconsole.sw.base

IRISconsole base software

IRISconsole.sw.remoteaccess

IRISconsole software for remote access

IRISconsole.sw.tcllink

IRISconsole Tcl software

IRISconsole.man.man

Reference pages for IRISconsole software

IRISconsole.man.relnotes

IRISconsole release notes

IRISconsole.books.IRISconsole_AG

This guide

IRISconsole.books.MUX_IG

The IRISconsole Multiplexer Installation Guide


Making Device Nodes

If you install IRISconsole software and then attempt to configure your system and use IRISconsole and do not run the cdmknods command, you may receive an error message similar to the following:

/dev/ttyd055 no such device

If you encounter this problem, run the following commands:

rm -f /dev/tty[mfd]???

then

cdmknods

The rm command removes any existing device nodes. The cdmknods command is run to make the device nodes associated with your system. The cdmknods simplifies and automates the process of making device nodes for Digi International scsiTerminalServer and EtherLite Terminal Server products. It may be used to make single nodes with specific features, to generate all the necessary nodes for a particular product, or to make nodes for all scsiTerminal Server products found on a particular system. See the cdmknods(1) man page for more information.

Adding an IRISconsole Administrator

To add an IRISconsole administrator, type as root

icpass -add icadmin 

The window shown in Figure 2-1 appears.

Figure 2-1. Adding an IRISconsole Administrator

Figure 2-1 Adding an IRISconsole Administrator

Enter the new user's login and password. Note that they are independent of that user's system login and password. Click the Apply button.

Adding an IRISconsole User

To add an IRISconsole user, you must be an IRISconsole administrator. Type

icpass -add icuser 

The window shown in Figure 2-2 appears.

Figure 2-2. Using the IRISconsole Security Window

Figure 2-2 Using the IRISconsole Security Window

After you enter your IRISconsole login and password and click the Apply button, the window shown in Figure 2-3 appears.

Figure 2-3. Adding an IRISconsole User

Figure 2-3 Adding an IRISconsole User

Enter the new user's login and password. Note that they are independent of that user's system login and password. Click the Apply button.

Determining Whether IRISconsole Security Is On or Off

As described in the section “IRISconsole Security” in Chapter 1, IRISconsole can be used to limit access to the capabilities of IRISconsole. To determine whether IRISconsole security is on, type

icpass -security get 

The software returns off or on.

Setting IRISconsole Security On or Off

To set IRISconsole security on or off, you must be an IRISconsole administrator. To set IRISconsole security on, type

icpass -security set on 

To set IRISconsole security off, type

icpass -security set off 

In either case, the security window shown in Figure 2-2 appears. After you enter correct information, a confirmation window appears with the message

Access Control status changed to `ON'

or

Access Control status changed to `OFF'

Setting Up Additional Access Control

IRISconsole uses files to either allow or deny access to particular systems within a site. These files are Achill and icdeny. They are located in the /usr/IRISconsole/adm directory. Each entry in these file has the following format:

user_id : site_name : system_name [, system_name ]

The icallow and icdeny files work like the allow and deny functionality of the cron command. If the entry is in the icallow file, user user_id is allowed access to the system site_name : system_name. If the entry is in the icdeny file, that user is denied access to that system. If both the icallow and icdeny files contain entries, then only the entry in the icallow file is used.

Obtaining the Multiplexer SCSI ID Number and Serial Port Connections

In preparation for installing systems for IRISconsole, you need to obtain a SCSI ID and port connections numbers by looking at the multiplexer and its cable connections. Follow these steps:

  1. Get the number of the SCSI ID used by the multiplexer. This number was set when the IRISconsole system was installed and is displayed on the back of the multiplexer, as shown in Figure 2-4.


    Note: If you are installing an EtherLite multiplexer, you do not need to determine the SCSI ID.

    Figure 2-4. Checking the Multiplexer SCSI ID Number

    Figure 2-4 Checking the Multiplexer SCSI ID Number

  2. Check the cabling for each system connected to the multiplexer to determine the multiplexer port to which each system's Console Connection and Remote System Control Connection ports are connected.

    If you want, create a table such as the example in Table 2-1 as an aid in determining which serial ports are used for which servers.

    Table 2-1. Example Table for Server Multiplexer Port Numbers


    Server Hostname

    Multiplexer Port Number for Console Connection

    Multiplexer Port Number for Remote System Control Connection

    jupiter

    01

    02

    zeus

    03

    04


Determining the Multiplexer Device Name

Beginning with the IRISconsole 1.3 release, the way special tty devices such as the SCSI multiplexers (ST-1600, ST-1616, and so on) or EtherLite multiplexers (EL-8 and EL-16) are created and used has changed. This section describes how to determine the device name for your multiplexer(s).

SCSI Multiplexers

To determine the name of a SCSI multiplexer, use:

/dev/ttyd{bus}{scsi_id}{port}

where:

  • bus is 0, 1, or 2 corresponding to the first, second, or third SCSI multiplexer found.

  • scsi_id is the ID of the ST-xxxx number on the SCSI multiplexer.

  • port is 0 - 9 or a - v, which corresponds to the port on the SCSI multiplexer numbered 1 through 32 (for example, port 1 = 0, port 11 = a).


Note: On the ST-1616 multiplexer, the ports are numbered 1 through 16, which correspond to ports 0 - 9 and a - f on the tty device. On the ST-1032 multiplexer, the ports are numbered 1 through 32, which correspond to ports 0 - 9 and a - v on the tty device.


EtherLite Multiplexers

To calculate the name of an EtherLite multiplexer, use:

/dev/ttydn{elps}{port}

where:

  • elps is the EtherLite number from the /etc/els.conf file associated with an IP address.

  • port is also 0 - 9 or a - f, which corresponds to port numbers 1 - 16 (for example, port 1 = 0, port 16 = f).

Setting Up IRISconsole for Remote Access

You can use the command ictelnet, which is a version of telnet adapted for IRISconsole, to access the IRISconsole text-based menu from another system. Follow these steps to prepare the IRISconsole system for remote access using ictelnet:

  1. To configure a port on the IRISconsole system so that ictelnet communicates directly to the IRISconsole application, edit the file /etc/services on that system to include the following line, which specifies the port on which the service is available:

    ictelnet 5000/tcp # IRISconsole Remote Access service
    

    For the port number, use any number between 5000 and 5063; the number 5000 is recommended for the status port.

  2. Edit the file /etc/inetd.conf on the IRISconsole system to include this line:

    ictelnet stream tcp     nowait   root  /usr/IRISconsole/bin/ictelnetd  ictelnetd