TCP/IP Configuration and Management Manual

SCF Reference
TCP/IP Configuration and Management Manual—427132-004
4-62
START Command
Examples
The following command causes the $ZTC0 primary process to become the backup
process (the attribute processor 6 identifies the processor where the former backup
process resided):
1-> PRIMARY PROCESS $ZTC0, CPU 6
Considerations
Run the NonStop TCP/IP process as a NonStop process pair. The NonStop TCP/IP
process can only access the LAN hardware when running in the processors that
access the ServerNet addressable controller (SAC)
START Command
The START command initiates the operation of SUBNETs and routes for the NonStop
TCP/IP subsystem. When the subsystem has successfully completed processing this
command, the specified object is placed in the STARTED summary state. You can start
a SUBNET or a route, but not a process. If a process is not started, it is undefined.
This is a sensitive command.
START ROUTE Command
The START ROUTE command creates implicit connections to and from a route. The
successful completion of the START command leaves the route in the STARTED
summary state.
Command Syntax
OUT file-spec
causes any SCF output generated for this command to be directed to the specified
file.
ROUTE route-spec
specifies the path on which data is sent in order to reach a destination. The fully-
qualified route-spec has the form:
If you specify the SCF object type (ROUTE) or any portion of the object name
(route-spec) in a prior ASSUME command, you can omit it in this command. For
information about the ASSUME command, see the SCF Reference Manual for G-
Series RVUs or the SCF Reference Manual for H-Series RVUs.
START [ / OUT file-spec / ] [ ROUTE route-spec ]
$process-name . #route-name