TCP/IP Configuration and Management Manual

NonStop Systems Used as Internet Gateways
TCP/IP Configuration and Management Manual—427132-004
F-7
Startup Files for HOST1
starts the TCP/IP process named $ZTC0 in processors 1 (primary) and 0 (backup).
The RUN command:
TCPIP/NAME $ZTC1, NOWAIT, CPU 1/0
starts the TCP/IP process named $ZTC1 in processors 1 (primary) and 0 (backup).
Note that TCP/IP starts at a priority of 200, regardless of the priority specified in the
RUN command.
The line:
ADD DEFINE =TCPIP^PROCESS^NAME, FILE $ZTC0
sets the =TCPIP^PROCESS^NAME parameter to $ZTC0. This action must occur prior to
starting the LISTNER and TELSERV processes. That way when each process is
started, through interrogation of this parameter, they know which Non/Stop TCP/IP
process to use. $ZTC0 is the recommended first name to use for the NonStop TCP/IP
process. Successive NonStop TCP/IP process names should be $ZTC1, $ZTC2, and
so on.
The RUN command:
LISTNER/NAME $LSN1,CPU 4, NOWAIT, PRI 160/ &
$SYSTEM.TCPIP.PORTCONF
starts the LISTNER process responsible for starting the ECHO, FINGER, and FTP
servers when a client request is received by the LISTNER process. Consequently, you
should run this process at a higher priority. This command also specifies the location of
the PORTCONF file used to designate which ports this process is to listen to. This
process requires privileged access to some NonStop TCP/IP ports; therefore, always
start with a super group ID.
The line:
TELSERV/NAME $ZTN0,CPU 2,NOWAIT,PRI 170/-BACKUPCPU 3
starts the Telserv process. When an application (such as Outside View) connects to the
IP address of the NonStop TCP/IP process, Telserv presents a window with a
Welcome Banner and Service Menu. You can start a TACL using the Service Menu.
The SCFSBNT File
The SCFSBNT file adds and starts subnets and routes. As Example F-2 shows, this
file begins by assuming the NonStop TCP/IP process $ZTC0. Thus, the NonStop
TCP/IP process must be started in order to add subnets and routes.