LAN Configuration and Management Manual

Configuration Quick Start

LAN Configuration and Management Manual—520469-012

1-5

Troubleshooting Tips

All the required processes and objects described in Initial SLSA Subsystem

Configuration should be started during the system-load sequence. If you discover that

a process or object is in the STOPPED state, determine the cause of the problem, then

start the process or other object.

The following are some general troubleshooting guidelines:



Examine the contents of the event-message log: a WAN subsystem or Kernel

subsystem event message might have been issued that provides information about

the process failure.



Try to start the process or object using the commands described in this subsection

or execute the STARTCOM file by entering the following command at the TACL

prompt:

TACL /IN $SYSTEM.ZSYSCONF.STARTCOM, NAME/

The STARTCOM file invokes the STARTSCF file. The contents of both files are

described in the WAN Subsystem Configuration and Management Manual. You

must be logged on as SUPER.SUPER to run the STARTCOM file.

Starting the LANMAN Process

If the LANMAN process is in the STOPPED state, try to start it by using the following

SCF command:

The priority of the LANMAN process should stay fairly constant over time; the priority

can vary depending on how busy the NonStop NS-series or NonStop S-series server

is, but if the priority goes down by a substantial amount, a problem may exist.

The creation time of the LANMAN process should occur shortly after the

NonStop server was last started. (You can use the STATUS PROCESS

$ZZKRN.#ZZLAN, DETAIL command from SCF or the STATUS $ZZLAN, DETAIL

command from TACL to determine the process-creation time.)

Starting a LANMON Process

If a LANMON process is in the STOPPED state, use the SCF START MON command

to start it:

processor-id

is the number of the processor in which you want the LANMON to start.

START PROCESS $ZZKRN.#ZZLAN

START MON $ZZLAN.#ZLM processor-id