Part XII Managing Terminals and Modems

This part provides instructions for managing terminals and modems. This part contains these chapters.

Chapter 47 Managing Terminals and Modems (Overview)

This chapter provides the overview information for managing terminals and modems. This is a list of the overview information in this chapter.

• "Terminals, Modems, Ports, and Services"

• "Tools for Managing Terminals and Modems"

• "Admintool"

• "Service Access Facility"

For step-by-step instructions about how to set up terminals and modems with Admintool, see Chapter 48, Setting Up Terminals and Modems (Tasks).

For step-by-step instructions about how to set up terminals and modems with the SAF, see Chapter 49, Setting Up Terminals and Modems With the Service Access Facility (Tasks).

Terminals, Modems, Ports, and Services

Terminals and modems provide both local and remote access to system and network resources. Setting up terminals and modem access is an important responsibility of a system administrator. This section explains some of the concepts behind modem and terminal management in the Solaris 2.x environment.

Terminals

Your system's bit-mapped graphics display is not the same as an alphanumeric terminal, which connects to a serial port and displays only text. You don't have to perform any special steps to administer the graphics display.

Modems

Modems can be set up in three basic configurations:

• Dial-out

• Dial-in

• Bidirectional

A modem connected to your home computer might be set up to provide dial - -out service, meaning you can access other computers from your own home, but nobody outside can gain access to your machine.

Dial-in service is just the opposite. It allows people to access a system from remote sites, but it does not permit calls to the outside world.

Bidirectional access, as the name implies, provides both dial-in and dial-out capabilities.

Ports

A port is a channel through which a device communicates with the operating system. From a hardware perspective, a port is a "receptacle" into which a terminal or modem cable may be plugged.

However, a port is not strictly a physical receptacle, but an entity with hardware (pins and connectors) and software (a device driver) components. A single physical receptacle often provides multiple ports, allowing connection of two or more devices.

Common types of ports include serial, parallel, small computer systems interface (SCSI), and Ethernet.

A serial port, using a standard communications protocol, transmits a byte of information bit-by-bit over a single line.

Devices that have been designed according to RS-232-C or RS-423 standards (this includes most modems, alphanumeric terminals, plotters, and some printers) can be plugged interchangeably (using standard cables) into serial ports of computers that have been similarly designed.

When many serial port devices must be connected to a single computer, it may be necessary to add an adapter board to the system. The adapter board, with its driver software, provides additional serial ports for connecting more devices than could otherwise be accommodated.

Services

Modems and terminals gain access to computing resources via the serial port software. The serial port software must be set up to provide a particular "service" for the device attached to the port. For example, you can set up a serial port to provide bidirectional service for a modem.

Port Monitors

The main mechanism for gaining access to a service is through a port monitor. A port monitor is a program that continuously monitors for requests to log in or access printers or files.

When a port monitor detects a request, it sets whatever parameters are required to establish communication between the operating system and the device requesting service. Then the port monitor transfers control to other processes that provide the services needed.

Table 47-1 describes the two types of port monitors included in the Solaris 2.x environment.

You may be familiar with an older port monitor called getty(1M). The new ttymon is more powerful; a single ttymon can replace multiple occurrences of getty. Otherwise, these two programs serve the same function.

Tools for Managing Terminals and Modems

Table 47-2 lists the recommended tools for managing terminals and modems. Table 47-3 lists specific differences in functionality between the Service Access Facility (SAF) and the Solstice^TM Serial Port Manager.

Admintool

Admintool sets up the serial port software to work with terminals and modems by calling the pmadm command with the appropriate information. It also provides:

• Templates for common terminal and modem configurations

• Multiple port setup, modification, or deletion

• Quick visual status of each port

Service Access Facility

The SAF is the tool used for administering terminals, modems, and other network devices. In particular, SAF enables you to set up:

• ttymon and listen port monitors (using the sacadm command)

• ttymon port monitor services (using the pmadm and ttyadm commands)

• listen port monitor services (using the pmadm and nlsadmin commands)

• And troubleshoot tty devices

• And troubleshoot incoming network requests for printing service

• And troubleshoot the Service Access Controller (using the sacadm command)

The SAF is an open-systems solution that controls access to system and network resources through tty devices and local-area networks (LANs). SAF is not a program. It is a hierarchy of background processes and administrative commands.

Chapter 48 Setting Up Terminals and Modems (Tasks)

This chapter provides step-by-step instructions for setting up terminals and modems using Admintool. This is a list of the step-by-step instructions in this chapter.

• "How to Start Admintool"

• "How to Set Up a Terminal"

• "How to Set Up a Modem"

• "How to Set Up a Modem for Use With UUCP"

• "How to Initialize a Port"

• "How to Disable a Port"

• " How to Remove a Port Service"

For overview information about terminals and modems, see Chapter 47, Managing Terminals and Modems (Overview).

Setting Up Terminals and Modems

When setting up serial port information, start Admintool, and select Serial Ports from the Browse menu. Select a serial port from the Serial Ports window and then choose Modify from the Edit menu to bring up the Modify Serial Port window. This window provides access to the port templates and provides information on the port in three levels of detail--Basic, More, and Expert.

The Modify Serial Port window appears in the Basic detail mode. To view More or Expert details, select the More or Expert option from the Detail menu.

The descriptions of each item in the Modify Serial window are listed in Table 48-1.

Setting Up Terminals

Table 48-2 describes the menu items (and their default values) when setting up a terminal using Serial Ports.

Setting Up Modems

Table 48-3 describes the three modem templates available when setting up a modem using Serial Ports.

Table 48-4 describes the default values of each template.

Table 48-5 describes the default values for the Initialize Only template.

How to Start Admintool

1. Verify that the following prerequisites are met. To use Admintool, you must:

   • Have a bit-mapped display monitor. The Admintool software can be used only on a system with a console that is a bit-mapped screen such as a standard display monitor that comes with a Sun workstation.

   • Be running an X Window System, such as the OpenWindows^TM environment.

   • Be a member of the sysadmin group (group 14).

   If you want to perform administration tasks on a system with an ASCII terminal as the console, use Solaris commands instead.

   ---

   Note -

   The system being configured must be your local system. Use Solstice AdminSuite Serial Port Manager to configure serial ports on a remote system.

   ---

2. Start Admintool.

   $ admintool &

   The Users main window is displayed.

How to Set Up a Terminal

1. Start Admintool, if it's not already running.

   See "How to Start Admintool" for more information on starting Admintool.

2. Select Serial Ports from the Browse menu.

   The Serial Ports menu is displayed.

3. Select the port or ports that will be used with a terminal.

4. Choose Modify from the Edit menu.

   The Modify Serial Port window appears in the Basic Detail mode. To enter additional details, select either the More or Expert Detail modes.

5. Choose Terminal-Hardwired from the Use Template menu.

   See Table 48-2 for a description of the Terminal-Hardware menu items.

6. Change values of template entries if desired.

7. Click on OK to configure the port.

8. Use the pmadm command to verify the terminal service has been added.

   $ pmadm -l -s ttya

Example--Completed Modify Window to Set Up a Terminal

How to Set Up a Modem

1. Start Admintool, if it's not already running.

   See "How to Start Admintool" for more information on starting Admintool.

2. Select Serial Ports from the Browse menu.

   The Serial Ports menu is displayed.

3. Select the port or ports that will be used with a modem.

4. Choose Modify from the Edit menu.

   The Modify Serial Port window appears in the Basic Detail mode. To enter additional details, select either the More or Expert Detail modes.

5. Choose the modem configuration template from the Use Template menu that meets or most closely matches your modem service.

   See Table 48-3 for a description of each template.

   See Table 48-4 for the default values of each template. If a UUCP service will be used to dial in to your modem on a Solaris 2.x system, see "How to Set Up a Modem for Use With UUCP" for the rest of the procedure.

6. Change values of template entries if desired.

7. Click on OK to configure the port.

8. Use the pmadm command to verify the modem service has been configured for use with UUCP.

   $ pmadm -l -s ttyb

Example--Completed Modify Window to Set Up a Modem

How to Set Up a Modem for Use With UUCP

UUCP sends information to a service using seven bits and even parity. Solaris 2.x modem configurations use eight bits and no parity for internationalization purposes. To set up your modem service to work with UUCP, follow these instructions.

1. Start Admintool, if it's not already running.

   See "How to Start Admintool" for more information on starting Admintool.

2. Select Serial Ports from the Browse menu.

   The Serial Ports menu is displayed.

3. Select the port or ports that will be used with a modem.

4. Choose Modify from the Edit menu.

   The Modify Serial Port window appears in the Basic Detail mode. For additional details, select either the More or Expert Detail modes.

5. Select Other from the Baud Rate menu.

   A window listing baud rates from the /etc/ttydefs file is displayed.

6. Enter a baud rate that provides seven bit, even parity service. Click on OK.

7. Change values of other template entries if desired.

8. Click on OK to configure the port.

9. Use the pmadm command to verify the modem service has been configured for use with UUCP.

   $ pmadm -l -s ttya

Example--Completed Modify Window to Set Up a Modem for Use With UUCP

In this example, the 9600E baud rate was selected. This provides a service with a 9600 baud rate, seven bits, and even parity.

How to Initialize a Port

1. Start Admintool, if it's not already running.

   See "How to Start Admintool" for more information on starting Admintool.

2. Select Serial Ports from the Browse menu.

   The Serial Ports menu is displayed.

3. Select the port or ports that you want to initialize.

4. Choose Modify from the Edit menu.

   The Modify Serial Port window appears in the Basic Detail mode. To enter additional details, select either the More or Expert Detail modes.

5. Choose Initialize Only - No Connection from the Use Template menu.

   See Table 48-5 for a description of the Initialize Only - No Connection template.

6. Click on OK to initialize the port.

7. Use the pmadm command to verify the port has been disabled.

   $ pmadm -l -s ttyb

Example--Completed Modify Window to Initialize a Port

How to Disable a Port

1. Start Admintool, if it's not already running.

   See "How to Start Admintool" for more information on starting Admintool.

2. Select Serial Ports from the Browse menu.

   The Serial Ports menu is displayed.

3. Select the port or ports that you want to disable.

4. Choose Modify from the Edit menu.

5. Click on the Service Enable button to disable the port service in the Modify window.

   This button acts as a toggle switch to enable or disable a port service.

6. Click on OK to disable the port.

7. Use the pmadm command to verify the port service has been disabled.

   $ pmadm -l -s ttya

Example--Completed Modify Window to Disable a Port

How to Remove a Port Service

1. Start Admintool, if it's not already running.

   See "How to Start Admintool" for more information on starting Admintool.

2. Select the port or ports that has a service you want to delete.

3. Choose Delete from the Edit menu.

   You are asked if you really want to delete the service for the specified port or ports. You may cancel the delete operation or continue with it.

4. Use the pmadm command to verify the port service has been deleted.

   $ pmadm -l -s ttya

TroubleshootingTerminal and Modem Problems

If users are unable to log in over serial port lines after you have added a terminal or modem and set up the proper services, consider the following possible causes of failure.

1. Begin by checking with the user.

   Malfunctions in terminals and modem use are typically reported by a user who has failed to log in or dial in. For this reason, it is best to begin troubleshooting by checking for a problem on the desktop.

   Some common reasons for login failure include:

   • Login ID or password is incorrect.

   • Terminal is waiting for X-ON flow control key (Control-q).

   • Serial cable is loose or unplugged.

   • Terminal configuration is incorrect.

   • Terminal is shut off or otherwise has no power.

2. Check the terminal.

   Continue to troubleshoot by checking the configuration of the terminal or modem. Determine the proper ttylabel for communicating with the terminal or modem. Verify that the terminal or modem settings match those of the ttylabel.

3. Check the terminal server.

   If the terminal checks out, continue to search for the source of the problem on the terminal or modem server. Use the pmadm command to verify that a port monitor has been configured to service the terminal or modem and that it has the correct ttylabel associated with it.

   $ pmadm -l -t ttymon

   Examine /etc/ttydefs and double check the label definition against the terminal configuration. Use sacadm to check the port monitor's status. Use pmadm to check the service associated with the port the terminal uses.

4. Check the serial connection.

   If the Service Access Controller is starting the TTY port monitor and pmadm reports that the service for the terminal's port is enabled, and if the terminal's configuration matches the port monitor's, then continue to search for the problem by checking the serial connection. A serial connection comprises serial ports, cables, and terminals. Test each of these parts by using it with two other parts that are known to be reliable.

   Test all of the following:

   • Serial ports

   • Modems

   • Cables

   • Connectors

5. Do not use Admintool or Solstice AdminSuite Serial Port Manager to modify serial port settings if the serial port is being used as a console. The correct procedure for changing console settings is by modifying the following line in the /etc/inittab file:

   co:234:respawn:/usr/lib/saf/ttymon -g -h -p "`uname -n` console login: " -T terminal_type -d /dev/console -l console -m ldterm,ttcompat

Chapter 49 Setting Up Terminals and Modems With the Service Access Facility (Tasks)

This chapter explains in detail what a system or network administrator needs to know about the Service Access Facility (SAF) in the Solaris 2.x environment.

If you want to see examples of specific SAF commands, skip the first section, "Using the Service Access Facility", and use the following list to find the instructions you need.

• "Using the Service Access Facility"

• "Overall Administration: sacadm Command"

• "Port Monitor Service Administrator: pmadm Command"

• "Port Monitors: TTY Monitor and Network Listener"

• "Administering ttymon Port Monitors"

• "Administering ttymon Services"

• "Administering listen Port Monitors"

• "Administering listen Port Monitor Services"

• "Troubleshooting the Network Listener: listen Port Monitor"

• "Reference Material for Service Access Facility Administration"

For overview information about terminals and modems, see Chapter 47, Managing Terminals and Modems (Overview).

Using the Service Access Facility

The SAF is the tool used for administering terminals, modems, and other network devices. The top-level SAF program is the Service Access Controller (SAC). The SAC controls port monitors which you administer through the sacadm command. Each port monitor can manage one or more ports.

You administer the services associated with ports through the pmadm command. While services provided through SAC may differ from network to network, SAC and the administrative programs sacadm and pmadm are network independent.

Table 49-1 illustrates the SAF control hierarchy. The sacadm command is used to administer the SAC which controls the ttymon and listen port monitors.

The services of ttymon and listen are in turn controlled by pmadm. One instance of ttymon can service multiple ports and one instance of listen can provide multiple services on a network interface.

Overall Administration: sacadm Command

The sacadm command is the top level of the SAF. The sacadm command primarily is used to add and remove port monitors such as ttymon and listen. Other sacadm functions include listing the current status of port monitors and administering port monitor configuration scripts.

Service Access Controller: SAC Program

The Service Access Controller program (SAC) oversees all port monitors. A system automatically starts SAC upon entering multiuser mode.

When SAC is invoked, it first looks for, and interprets, each system's configuration script, by which SAC customizes its environment. The modifications made to the SAC environment are inherited by all the "children" of the SAC. This inherited environment may be modified by the children.

After it has interpreted the per-system configuration script, the SAC program reads its administrative file and starts the specified port monitors. For each port monitor, SAC runs a copy of itself (SAC forks a child process). Each child then interprets its per-port monitor configuration script, if such a script exists.

Any modifications to the environment specified in the per-port monitor configuration script affect the port monitor and will be inherited by all its children. Finally, the child process runs the port monitor program using the command found in the SAC administrative file.

SAC Initialization Process

The following steps summarize what happens when SAC is first started:

1. The SAC program is spawned by init at run level two.

2. The SAC program reads /etc/saf/_safconfig, the per-system configuration script.

3. The SAC program reads /etc/saf/_sactab, the SAC administrative file.

4. The SAC program forks a child process for each port monitor it starts.

5. Each port monitor reads /etc/saf/pmtag/_config, the per-port monitor configuration script.

Port Monitor Service Administrator: pmadm Command

The pmadm command enables you to administer port monitors' services. In particular, you use the pmadm command to add or remove a service and to enable or disable a service. You can also install or replace per-service configuration scripts, or print information about a service.

Each instance of a service must be uniquely identified by a port monitor and a port. When you use the pmadm command to administer a service, you specify a particular port monitor via the pmtag argument, and a particular port via the svctag argument.

For each port monitor type, the SAF requires a specialized command to format port monitor-specific configuration data. This data is used by the pmadm command. For ttymon and listen type port monitors, these specialized commands are ttyadm and nlsadmin, respectively.

A Port Monitor at Work: ttymon

Whenever you attempt to log in via a directly connected modem or alphanumeric terminal, ttymon goes to work, as follows.

As shown in Figure 49-1, the init program is the first process to be started at boot time. Consulting its administrative file (/etc/inittab), init starts other processes as they are needed. Listed among those processes is the SAC.

SAC, in turn, automatically starts up the port monitors designated in its administrative file (/etc/saf/_sactab). Figure 49-1 shows only a single ttymon port monitor.

After ttymon has been started, it monitors the serial port lines for service requests.

Figure 49-1 How ttymon Helps Process a Login Request

When someone attempts to log in via an alphanumeric terminal or a modem, the serial port driver passes the activity to the operating system. The ttymon port monitor notes the serial port activity, and attempts to establish a communications link. ttymon determines what data transfer rate, line discipline, and handshaking protocol are required to communicate with the device.

Having established the proper parameters for communication with the modem or terminal, ttymon passes these parameters to the login program and transfers control to it.

Port Initialization Process

When an instance of ttymon is invoked by SAC, ttymon starts to monitor its ports. For each port, ttymon first initializes the line disciplines, if they are specified, and the speed and terminal settings. The values used for initialization are taken from the appropriate entry in /etc/ttydefs.

The ttymon port monitor then writes the prompt and waits for user input. If the user indicates that the speed is inappropriate by pressing the Break key, ttymon tries the next speed and writes the prompt again.

If autobaud is enabled for a port, ttymon will try to determine the baud rate on the port automatically. Users must press Return before ttymon can recognize the baud rate and print the prompt.

When valid input is received, ttymon interprets the per-service configuration file for the port, creates a /etc/utmp entry if required, establishes the service environment, and invokes the service associated with the port.

After the service terminates, ttymon cleans up the /etc/utmp entry, if one exists, and returns the port to its initial state.

Bidirectional Service

If a port is configured for bidirectional service, ttymon will:

• Allow users to connect to a service

• Allow uucico, cu, or ct to use the port for dialing out (if the port's free)

• Wait to read a character before printing a prompt

• Invoke the port's associated service--without sending the prompt message--when a connection is requested (if the connect-on-carrier flag is set)

Port Monitors: TTY Monitor and Network Listener

Though SAF provides a generic means for administering any future or third-party port monitors, only two are implemented in the Solaris 2.x environment--ttymon and listen.

TTY Port Monitor: ttymon

The ttymon port monitor is STREAMS-based. It monitors ports; sets terminal modes, baud rates, and line disciplines; and invokes the login process. (It provides Solaris 2.x users the same services that getty did under previous versions of Solaris software.)

The ttymon port monitor runs under the SAC program. It is configured using the sacadm command. Each instance of ttymon can monitor multiple ports. These ports are specified in the port monitor's administrative file. The administrative file is configured using the pmadm and ttyadm commands.

ttymon and the Console Port

Console services are not managed by the Service Access Controller nor any explicit ttymon administration file. An entry in the /etc/inittab file is used to manage the console port using ttymon in express mode, which is a special ttymon mode that is invoked directly by a command that requires login service.

The default console entry in the /etc/inittab file looks like this:

co:234:respawn:/usr/lib/saf/ttymon -g -h -p "`uname -n` console login: "
 -T terminal_type -d /dev/console -l console -m ldterm,ttcompat

Special ttymon-Specific Administrative Command: ttyadm

The ttymon administrative file is updated by sacadm and pmadm, as well as by the ttyadm command. The ttyadm command formats ttymon-specific information and writes it to the standard output, providing a means for presenting formatted ttymon-specific data to the sacadm and pmadm commands.

Thus, ttyadm does not administer ttymon directly; rather, it complements the generic administrative commands, sacadm and pmadm. See ttyadm(1M) for more details.

Network Listener Service: listen

The listen port monitor runs under SAC. It monitors the network for service requests, accepts requests when they arrive, and invokes servers in response to those service requests.

The listen port monitor is configured using the sacadm command. Each instance of listen can provide multiple services. These services are specified in the port monitor's administrative file. This administrative file is configured using the pmadm and nlsadmin commands.

The network listener process may be used with any connection-oriented transport provider that conforms to the Transport Layer Interface (TLI) specification. In the Solaris 2.x environment, listen port monitors provide additional network services not provided by inetd, such as print service.

Special listen-Specific Administrative Command: nlsadmin

The listen port monitor's administrative file is updated by sacadm and pmadm, as well as by the nlsadmin command. The nlsadmin command formats listen-specific information and writes it to the standard output, providing a means of presenting formatted listen-specific data to the sacadm and pmadm commands.

Thus, nlsadmin does not administer listen directly; rather, it complements the generic administrative commands, sacadm and pmadm. See nlsadmin(1M) for more details.

Each network has at least one instance of the network listener process associated with it. Each network is configured separately. The nlsadmin command controls the operational states of listen port monitors.

The nlsadmin command can establish a listen port monitor for a given network, configure the specific attributes of that port monitor, and start and kill the monitor. The nlsadmin command can also report on the listen port monitors on a machine. See nlsadmin(1M) for a detailed description.

Administering ttymon Port Monitors

Use the sacadm command to add, list, remove, kill, start, enable, disable, enable, and remove a ttymon port monitor.

You must be superuser to perform the following procedures.

How to Add a ttymon Port Monitor

To add a ttymon port monitor, type:

# sacadm -a -p mbmon -t ttymon -c /usr/lib/saf/ttymon -v `ttyadm
-V` -y "TTY Ports a & b"

How to View ttymon Port Monitor Status

To see the status of a ttymon port monitor, type:

# sacadm -l -p mbmon

Example--Viewing ttymon Port Monitor Status

# sacadm -l -p mbmon
PMTAG  PMTYPE  FLGS RCNT STATUS    COMMAND
mbmon  ttymon  -    0    STARTING  /usr/lib/saf/ttymon #TTY Ports a & b

How to Stop a ttymon Port Monitor

To kill a ttymon port monitor, type:

# sacadm -k -p mbmon

How to Start a ttymon Port Monitor

To start a killed ttymon port monitor, type:

# sacadm -s -p mbmon

How to Disable a ttymon Port Monitor

Disabling a port monitor prevents new services from starting, without affecting existing services.

To disable a ttymon port monitor, type:

# sacadm -d -p mbmon

How to Enable a ttymon Port Monitor

Enabling a ttymon port monitor allows it to service new requests.

To enable a ttymon port monitor, type:

# sacadm -e -p mbmon

How to Remove a ttymon Port Monitor

To remove a ttymon port monitor, type:

# sacadm -r -p mbmon

Removing a port monitor deletes all the configuration files associated with it. Port monitor configuration files cannot be updated or changed using sacadm. To reconfigure a port monitor, remove it and add a new one.

Administering ttymon Services

Use pmadm to add services, list the services of one or more ports associated with a port monitor, and enable or disable a service.

You must be superuser to perform the following procedures.

How to Add a Service

To add a standard terminal service to the mbmon port monitor, type:

# pmadm -a -p mbmon -s a -i root -v `ttyadm -V` -m "`ttyadm -i 'Terminal disabled'
-l contty  -m ldterm,ttcompat -S y -d /dev/term/a -s /usr/bin/login`"

In this example, the input wraps to the next line. Do not put a Return or line feed after contty.

The above pmadm command contains an embedded ttyadm command. The options in this embedded command are as follows:

How to View the Status of a TTY Port Service

Use the pmadm command as shown to list the status of a TTY port, or all the ports associated with a port monitor.

Listing One Service

To list one service of a port monitor, type:

# pmadm -l -p mbmon -s a

Listing All Services of All Port Monitors

To list all services of all port monitors, type:

# pmadm -l

Listing All Services of a Port Monitor

To list all services of a port monitor, type:

# pmadm -l -p mbmon

Example--Viewing the Status of a TTY Port Monitor Service

# pmadm -l -p mbmon
PMTAG  PMTYPE  SVCTAG FLAGS ID    <PMSPECIFIC> 
mbmon  ttymon  a      -     root  /dev/term/a - - /usr/bin/login - contty
ldterm,ttcompat login:  Terminal disabled - y  #

How to Enable a Port Monitor Service

To enable a disabled port monitor service, type:

# pmadm -e -p mbmon -s a

How to Disable a Port Monitor Service

To disable a port monitor service, type:

# pmadm -d -p mbmon -s a

Administering listen Port Monitors

Use the sacadm command to add, list, kill, start, enable, disable, or remove a listen port monitor.

You must be superuser to perform the following procedures.

How to Add a listen Port Monitor

To add a listen port monitor, type:

# sacadm -a -p tcp -t listen -c /usr/lib/saf/listen -v `nlsadmin
-V` -y "le0 ethernet"

How to View listen Port Monitor Status

To list the status of a listen port monitor, type:

# sacadm -l -p tcp

How to Stop a listen Port Monitor

To kill a listen port monitor, type:

# sacadm -k -p tcp

How to Start a listen Port Monitor

To start a listen port monitor, type:

# sacadm -s -p tcp

How to Enable a listen Port Monitor

To enable a listen port monitor, type:

# sacadm -e -p tcp

How to Disable a listen Port Monitor

To disable a listen port monitor, type:

# sacadm -d -p tcp

How to Remove a listen Port Monitor

To remove a listen port monitor, type:

# sacadm -r -p tcp

Administering listen Port Monitor Services

Use the pmadm command to add, enable, disable, and list the services associated with a listen port monitor.

You must be superuser to perform the following procedures.

How to Add a listen Port Monitor Service

To add a listen port monitor service, type:

# pmadm -a -p tcp -s lp -i root -v `nlsadmin -V` -m "`nlsadmin
-o /var/spool/lp/fifos/listenS5`"

In this example, a listen service is added for print requests from remote SunOS 5.x machines. This service does not listen for requests from SunOS 4.x machines.

In this example, the input wraps to the next line. Do not put a Return or line feed after the -o.

The above pmadm command contains an embedded nlsadmin command. In that embedded command -o specifies the full path name of a first-in first-out (FIFO) or named STREAM through which a standing server will receive the connection.

How to List listen Port Monitor Services

To list the services associated with a listen port monitor, type:

# pmadm -l -p tcp

How to Enable a listen Port Monitor Service

To enable a listen port monitor service, type:

# pmadm -e -p tcp -s lp

How to Disable a listen Port Monitor Service

To disable a listen port monitor service, type:

# pmadm -d -p tcp -s lp

Troubleshooting the Network Listener: listen Port Monitor

Use the following tips to remedy listen port monitor difficulties.

1. Begin with the network.

   The network listener is suspect when users report that they cannot print to a network printer. Begin by issuing the /usr/sbin/ping command from the print server to the client and back to determine if the network is up.

2. Check the listen port monitor.

   Use sacadm to check that the listener is starting. Use pmadm to check that the print service is configured correctly and that the service is enabled.

3. Check the print server's configuration.

   See Chapter 72, Troubleshooting Printing Problems, for more information.

Reference Material for Service Access Facility Administration

Files Associated With SAF

SAF uses configuration files which can be modified by using the sacadm and pmadm commands. You should not need to edit them manually.

The /etc/saf/_sactab File

The /etc/saf/_sactab looks like this:

# VERSION=1
zsmon:ttymon::0:/usr/lib/saf/ttymon     #
tcp:listen::999:/usr/lib/saf/listen tcp #

The /etc/saf/pmtab/_pmtab File

The /etc/saf/pmtab/_pmtab file, such as /etc/saf/zsmon/_pmtab, looks like this:

# VERSION=1
ttya:u:root:reserved:reserved:reserved:/dev/term/a:I::/usr/bin/login::9600:ldterm,
ttcompat:ttya login\: ::tvi925:y:# 

Service States

The sacadm command controls the states of services. The possible states are shown below.

To determine the state of any particular service, use the following:

# pmadm -l -p portmon_name -s svctag

Port Monitor States

The sacadm command controls the states of ttymon and listen port monitors. The possible states are shown below.

To determine the state of any particular port monitor, use the following:

# sacadm -l -p portmon_name

Port States

Ports may be enabled or disabled depending on the state of the port monitor that controls them.