This chapter explains what to do to configure the 4DLT application after you install it. It explains the default LAT configuration that results from 4DLT software installation and explains how to modify and add to the default configuration. This chapter also contains instructions for preparing the user environment for 4DLT, and instructions for starting and stopping 4DLT.
The chapter includes these sections:
Before you perform 4DLT setup procedures, 4DLT software must be installed on your IRIS system. If you have not already installed 4DLT software, see your 4DLT Release Notes for specific product installation information. Your 4DLT Release Notes also recommend additional documentation on product installation.
After 4DLT software is installed, you might want to modify the IRIX initialization file for the root user to include the pathnames of 4DLT software. During initialization, IRIX sets a path to directories that are listed in the initialization file; this enables you (as the root user) to execute 4DLT commands without specifying the entire pathname of each command in your entries.
4DLT commands are stored in two directories:
/usr/bin/lat
/usr/etc/lat
If you use the C shell (the IRIX system default), search paths are set in the .cshrc file in root's home directory. Add the 4DLT directories as arguments to the set path command in the .cshrc file.
If you use the Bourne or Korn shell, search paths are set in the .profile file in root's home directory. Include 4DLT directories as arguments to the setenv PATH command in the .profile file.
The 4DLT installation process creates a default LAT configuration on the IRIS system.To define a default configuration, 4DLT installation performs these setup tasks:
Assigning the LAT node name to the IRIS system
Assigning the LAN interface to the LAT network
Creating a default version of the 4DLT configuration file, /usr/etc/lat/latconfig
Creating a preliminary version of the LAT services file, /usr/etc/lat/latservice
In many LAT networks, the default configuration that the 4DLT installation process creates is sufficient to begin running the IRIS system as a dual purpose LAT node. In other networks, however, the default configuration will require some modification.
To determine whether the default 4DLT configuration is suitable for your particular IRIS system and LAT network, review the information in the remainder of this section. If you determine that changes are needed, use the procedures in this chapter and in Chapter 4 and Chapter 5 to make the required modifications.
The 4DLT installation process assigns the IRIS system a LAT node name by reading the system's /etc/sys_id file and writing its contents to the /usr/etc/lat/latconfig file. To determine the LAT node name assigned to your IRIS system, display the contents of /etc/sys_id using the hostname (1) command:
# hostname <Enter> |
If you prefer to use a LAT node name that is different from the name returned by hostname, you can change the LAT name with either the slcp utility (see “Changing the LAT Node Name or Description”) or the lati utility (see “Setting LAT Node Identification Parameters”). You must start 4DLT software before you use slcp (see “Standard 4DLT Startup Procedures” for instructions).
 | Note: If your IRIS system is also a member of a TCP/IP or DECnet network, the name contained in /etc/sys_id is usually the recognized name for your system on those networks as well. Although it is permissible to choose a different LAT node name, assigning the same node name for all networks makes system administration easier. |
The 4DLT installation process assigns the primary LAN interface on the IRIS system as the LAT network interface. By default, the primary LAN interface on your IRIS system is its built-in Ethernet interface, which is usually configured as either ec0 or et0 when the IRIS system is initialized. If you plan to use the primary LAN interface as the LAT network interface, you do not need to change the default network interface in order to run 4DLT.
If you are currently using your primary LAN interface for a network other than an Ethernet network (your primary interface is currently used for an FDDI or token ring network, for example), you must specify an alternate network interface during 4DLT startup. See “Starting 4DLT with an Alternate LAN Interface” for details.
The LAT configuration file, /usr/etc/lat/latconfig contains parameters that regulate LAT performance on the IRIS system. This file is read at 4DLT startup, and its contents remain in effect until 4DLT is stopped (or until you change latconfig). In most cases, the as-shipped version of latconfig contains the appropriate settings for an IRIS host to operate satisfactorily on a LAT network, but occasionally these parameters must be changed.
To verify that the default settings are satisfactory for your node and network, review the information in Table 5-1. If you determine that latconfig requires changing, start the 4DLT application (instructions are given in “Standard 4DLT Startup Procedures”) and follow the instructions in Chapter 5 to make your changes.
| Note: If you are not the LAT network administrator, discuss any changes you plan with the administrator before you complete them. |
The 4DLT installation process creates a default version of the /usr/etc/lat/latservice file that contains one record. The record sets up a login service on the IRIS node. The name of the new login service is the IRIS host name as specified in the /etc/sys_id file. The record also assigns a service rating and a description for the login service; it does not assign a password to the service.
For example, assume that you just installed 4DLT on an IRIS system that contains the host name moonbeam in its /etc/sys_id file. After 4DLT installation, the default /usr/etc/lat/latservice file would contain this record:
LOGN:moonbeam:-1:“Login service for host `moonbeam'”:*: |
The /usr/etc/lat/latservice file is an ASCII file that you can modify using your favorite editor. The list below explains each field shown in the sample default entry above and describes what you can do to change your default version of latservice.
| LOGN | Is a keyword that specifies the type of service defined in this entry. Do not change LOGN; it must appear as the first word in this entry. | |
| moonbeam | Is the name of the login service to be advertised by this node. The service name was derived from the entry moonbeam in moonbeam's /etc/sys_id file. You can replace this service name with a different name if you wish. | |
| -1 | Is a service rating designation. This particular rating, negative 1, specifies that the service rating is to be dynamically derived by the latd daemon. See “Setting a LAT Service Rating” for information about setting service ratings. | |
| ``LAT login service for host `moonbeam'” |
| |
| * (asterisk) |
|
| Note: The asterisk must appear in any empty field of a latservice file record. |
In addition to changing the default entry in /usr/etc/lat/latservice, you can add more login services, password protect login services, and include LAT printer records in this file. Additional information about modifying /usr/etc/lat/latservice is given in “Maintaining the LAT Services File”.
The 4DLT installation process assumes that you wish to operate the IRIS host as a dual purpose LAT node; therefore, it enables both service node and terminal server functions on the IRIS system. If you prefer, you can disable the terminal server functions on your system, which prevents the local IRIS system user from connecting to LAT services. To disable terminal server functions, you must modify /usr/etc/lat/latconfig using the lati utility (see “Setting Ethernet Parameters” for instructions).
When an IRIX user creates a new shell, the shell initialization procedure sets a path to the directories that will be searched to execute the user's commands. 4DLT commands must be included in this path to allow users to execute 4DLT commands without specifying the entire pathname for each command entered.
The procedure below explains how to modify the .cshrc file to include the 4DLT directory in the search path. You must do this procedure as either the root user or as the owner of this account.
| Note: If you are preparing the environment for a Bourne or Korn shell user, modify the user's .profile file instead of the .cshrc file; add 4DLT directories as arguments to the setenv PATH command in the .profile file. |
Change to the user's home directory:
# cd login_name <Enter>
Edit the .cshrc file in the home directory.
4DLT user commands are located in the /usr/bin/lat directory. To add this directory to the user's path, open the .cshrc file with an IRIX editor and add this line to the end of the path:
set path = ($path /usr/bin/lat) <Enter>
Note: If this .cshrc file already has a set path command in it, you can just add the /usr/bin/lat directory as an argument. Close and save the .cshrc file.
Execute the .cshrc script:
# source .cshrc <Enter>
Once you complete this procedure, the user whose .cshrc file you edited will be able to execute 4DLT commands without specifying the 4DLT directory in each command entry. Repeat this procedure for other 4DLT users on this IRIS system.
Starting the LAT daemon starts 4DLT software on an IRIS system. You can start latd with a command line entry, or you can enable automatic startup by setting an initialization flag. The procedures below explain how to start 4DLT using each method.
| Note: If your IRIS system is also running 4DDN, always start 4DDN before starting 4DLT software. |
The example below shows the command you use to start 4DLT from the command line. It assumes that you have included the /usr/bin/lat directory in your search path. It also assumes that you plan to use the primary network interface for the LAT network (see “Using the Alternative Startup Command” for details).
Notice that you must be logged in as root to execute this command:
# latd <Enter> |
Once latd is started, 4DLT commands are ready to use and the IRIX system is ready to accept requests for outgoing and incoming LAT connections. Before turning the system over to LAT users, however, your should review the procedures in the remainder of this guide to determine whether additional setup procedures are necessary.
If you would like 4DLT to start automatically as part of the initialization process on the IRIS system, you can set a flag that will start latd each time the IRIS system is restarted. Enter this command to enable automatic startup:
# /etc/chkconfig 4DLT on <Enter> |
If you decide to turn automatic startup off, enter this command:
# /etc/chkconfig 4DLT off <Enter> |
During the IRIX initialization process, the system's network interfaces are assigned numbers, based on the order in which they are enabled, that identify them to other software. The initialization process assigns the primary network interface a unit number of 0.
By default, 4DLT software uses unit 0 as its network interface. If you want 4DLT to use a network interface other than the primary interface, you can specify an alternate interface at 4DLT startup. During the 4DLT startup process, the /dev/snif device is assigned to the designated network interface.
To display your IRIS system's network interfaces and their assigned unit numbers, use the latmac command:
# latmac <Enter> |
Name Unit ec0 0 fv0 1 |
The example above shows that ec0 is the primary network interface on this IRIS system, since it has a unit number of 0. Because unit 0 is assigned to the ec0 LAN interface, 4DLT software will use ec0 as its LAT network interface.
If you do not plan to use the primary network interface on your IRIS system for the LAT network, you must specify a different unit number to 4DLT software in the startup command.
To specify a new unit number for 4DLT software, use the latd -u command:
# latd -u new_unit_number <Enter> |
The argument to latd -u is the unit number of the network interface that you plan to use for the LAT network. For example, assume that a latmac command returns this information:
Name Unit ec0 0 ec1 1 enp0 2 |
To assign enp0 as the LAT network interface, you would issue this startup command:
# latd -u 2 <Enter> |
You can set up 4DLT to start automatically and specify an alternative LAN interface in the automatic startup process. To enable automatic startup, modify the /etc/rc2.d/S31lat initialization file:
Open the S31lat file:
# vi /etc/rc2.d/S31lat
Modify the OPTIONS setting in S31lat, as shown below:
OPTIONS=”-u unit_number”
Stop and restart 4DLT for your changes to take effect (see “Stopping and Restarting 4DLT”).
Many 4DLT maintenance procedures require you to stop and restart the LAT daemon so that your changes will take effect. Use the commands below to stop and restart latd. Notice that you must complete this procedure as the root user of the IRIS system:
Stop latd:
# /etc/killall 15 latd <Enter>
Restart latd:
# latd <Enter>
| Note: If you are using a non-primary network interface to the LAT network, specify the alternate network interface number when you restart 4DLT (see “Using the Alternative Startup Command” for details). |