TCP/IP Configuration and Management Manual

Configuring the NonStop TCP/IP Subsystem
TCP/IP Configuration and Management Manual—427132-004
3-28
Networking Services Provided in the Guardian
Environment
Networking Services Provided in the Guardian
Environment
Section 1, Configuration Quick Start and Example 3-1 through Example 3-16 provided
configuration files for starting NonStop TCP/IP in the Guardian environment. This
subsection focuses on the LISTNER process, the services that LISTNER provides, and
the Domain Name Server (DNS). For information on the other protocols and services,
see Appendix B, NonStop TCP/IP Processes and Protocols.
Configuring Subsystem Processes
This section describes the steps required to configure and start the various processes
that operate the NonStop TCP/IP subsystem.
QIO
For NonStop systems, you do not need to configure or start the QIO subsystem; it is
loaded and started during system cold load.
Configuring the NonStop TCP/IP Process
Once the NonStop system and the SLSA subsystem are running, start your NonStop
TCP/IP processes.
To start a NonStop TCP/IP process, enter the following:
TCPIP /NAME process-name, &
NOWAIT, &
CPU cpu/backupcpu
SYSnn is the name of the system subvolume on which your NonStop TCP/IP software
resides.
For process-name, enter a Guardian process name; the recommended form is
$ZTCx, where x is one or more letters or numeric digits. The recommended name is
$ZTC0; all NonStop applications look for this name.
Select the primary and backup cpus from the Potential Access CPUs of the LIF. For
information about why you must match the CPUs, see the Hint on page 1-7.
Finally, configure the NonStop TCP/IP SUBNETs and routes either through interactive
commands issued through SCF or through programmatic commands issued by a
management application.
A route is added automatically when you add a SUBNET, but you can add as many
additional routes as your resources will allow. The route that is added automatically
when you add the SUBNET has a name of the form #RT*. Additional routes are
required when the remote network address portion of the IP address is not the same
Note. The TCP/IP process priority is set internally to 200 in this RVU.