TCP/IP (Parallel Library) Configuration and Management Manual

HP NonStop TCP/IP (Parallel Library) Configuration and Management Manual522271-006
4-1
4
Managing the Parallel Library TCP/IP
Subsystem
This section describes the following aspects of managing the Parallel Library TCP/IP
subsystem:
Running Applications in Both Environments on page 4-1
Managing the System Configuration Database on page 4-1
Managing Performance on page 4-7
Strategy for Coexistence with Conventional TCP/IP on page 4-7
Falling Back to Conventional TCP/IP on page 4-7
Dynamically Loading SPRs on page 4-8
There are some new system management tasks for Parallel Library TCP/IP as well as
some considerations for running applications in the Parallel Library TCP/IP and
conventional TCP/IP environments.
Running Applications in Both Environments
You will probably run applications in both the conventional TCP/IP and the Parallel
Library TCP/IP environments. If you are using ATM or token-ring adapters your
applications must use conventional TCP/IP. If you are using Ethernet adapters, you
can run your application in either environment.
The two environments cannot share the same LIF but they can share an E4SA or
G4SA because those adapters have four LIFs. However, a FESA and a GESA have
only one LIF, so they can only support one environment.
You may choose to dedicate some combination of these adapters to either the
conventional TCP/IP or Parallel Library TCP/IP environments, but you don’t have to do
anything differently to configure the FESA, E4SA, GESA, and G4SA adapters for use
with Parallel Library TCP/IP.
Managing the System Configuration Database
The system configuration database (CONFIG) is part of the NonStop Kernel subsystem
on NonStop S-series servers. The conventional TCP/IP subsystem (NonStop TCP/IP)
does not participate in the system configuration database but Parallel Library TCP/IP
does. As soon as you configure Parallel Library TCP/IP for the first time, the MON,
ROUTE, ENTRY, and SUBNET objects are added to the system configuration
database and any alterations to those objects also update the configuration of those
objects in the system configuration database. The system configuration database