WAN Subsystem Configuration and Management Manual

Configuration Quick Start

WAN Subsystem Configuration and Management Manual—522463-011

1-22

Starting the WAN Manager Process

If the WAN manager process is not in the STARTED state, try to start it by using this

SCF command:

The priority of the WAN manager process should stay fairly constant over a period of

time. The priority can vary depending on how busy the Integrity NonStop NS-series or

NonStop S-series server is, but if it goes down by a substantial amount, a problem

such as a looping situation maybe causing the WAN manager process to time out.

The creation time of the WAN manager process should be shortly after the

Integrity NonStop NS-series or NonStop S-series server was last started. (You can use

the SCF STATUS PROCESS command with the DETAIL option to determine the

process creation time.) If the creation time is more recent, a switch could have

occurred between the primary and backup WAN manager processes.

Starting a WAN Subsystem Process

If an SNMP trap multiplexer process, ConMgr process, WANBoot process, or TFTP

server process is not in the STARTED state, try to start it by using the SCF START

PROCESS command. The command syntax is:

process_name

is the name of the WAN subsystem process you want to start.

Starting a Subnet

If a TCP/IP SUBNET is not in the STARTED state, use the SCF START SUBNET

command to start it.

The command syntax for G06.26 and earlier RVUs is:

nnn

is the last three characters of the TCP/IP process name for which the SUBNET is

configured.

subnet

is the name of the SUBNET you want to start.

START PROCESS $ZZKRN.#ZZWAN

START PROCESS $ZZWAN.#process_name

START SUBNET $ZBnnn.#subnet