Expand Configuration and Management Manual (H06.21+, J06.10+)

Configuring the Network Control Process
Expand Configuration and Management Manual — 529522-013
6 - 4
Step 3: Start $NCP
Step 3: Start $NCP
To start $NCP, use the WAN subsystem SCF START DEVICE command. The
command syntax is:
To make sure $NCP has started successfully, enter this command at the TACL prompt:
> STATUS $NCP
If $NCP was started successfully, you will see a display similar to Example 6-1:
If $NCP was not started successfully, this message will be displayed:
(Process does not exist)
$NCP Modifiers
These modifiers are included in the PEXPNCP profile. These modifiers are provided to
enable you to customize $NCP routing algorithm, select a network map propagation
algorithm, and modify network connection handling.
ABORTTIMER n
Default: 15,000 (2.5 minutes)
Units: 0.01 seconds
Range: 0 to 30,000 (0 to 5 minutes)
This modifier specifies the length of time, in one-hundredth of a second increments,
that $NCP will wait before aborting requests destined for a remote system to which an
alternate path has not yet been identified. The ABORTTIMER modifier must be set to
the same value on all systems in the network.
By setting the ABORTTIMER modifier, you can prevent $NCP from completing
request
s with an error 250 (all paths to the system are down) before it has sufficient
time to receive alternate-path information. The ABORTTIMER modifier should be used
with the modified split horizon (MSH) routing algorithm. The ABORTTIMER modifier is
explained in more detail in
Modified Split Horizon (MSH) on page 17-28.
START DEVICE $ZZWAN.#NCP
Example 6-1. SCF STATUS $NCP Command
System \NODEA
Process Pri PFR %WT Userid Program file Hometerm
$NCP 2,26 199 P 011 255,255 $SYSTEM.SYS01.NCPOBJ $YMIOP.#CLCI
Swap File Name: $SYSTEM.#0
$NCP B 3,24 199 P 011 255,255 $SYSTEM.SYS01.NCPOBJ $YMIOP.#CLCI
Swap File Name: $SYSTEM.#0