TCP/IPv6 Configuration and Management Manual (G06.24+)

Manage the NonStop TCP/IPv6 Subsystem
HP NonStop TCP/IPv6 Configuration and Management Manual—524523-008
6-24
Managing Applications
Managing Applications
Applications are not affected if LNP is not enabled, however after a SUBNET is
configured with the attributes enabling logical-network partitioning all applications
running on the TCP/IPv6 subsystem are affected. Coding changes are not needed in
an application to support LNP, but how an application is run and perhaps configured
can change. An application can view multiple LNPs configured on TCP/IPv6 as a
similar number of configured conventional NonStop TCP/IP processes. The actions
necessary to support the application in a multiple conventional TCP/IP process
environment are similar when using the application in a multiple LNP environment.
Without LNP, applications have connectivity through all IP addresses configured on a
system, and as a result it might only be necessary to run one copy of a server
application (or multiple copies using round-robin filtering) on a system. An example is
the LISTNER process. After LNP is enabled it is necessary to start a copy of an
application on each LNP through which connectivity is desired. For applications that
initiate connections, it is very important that they select the correct TCP6SAM process
as their socket provider so that the destination IP addresses are reachable through the
SUBNETs associated with the LNP the transport provider is associated with.
Determining the TCP6SAM Process Names for the Partitions
The INFO SUBNET, DETAIL command shows the TCP6SAM processes that are
associated with configured LNPs. If you want to find the TCP6SAM processes for the
default partition, you have to perform several steps because there is no direct way to
determine the TCP6SAM process names for the default partition. (The TCP6SAM
process is not displayed in the INFO SUBNET DETAIL command.) To find TCP6SAM
processes for the default partition, perform these steps:
1. Issue the SCF INFO SUBNET $ZZTCP.*, DETAIL command.
2. Identify all TCP6SAM processes that are listed in the LNP field of the SUBNET
display and make a note of these process names.
3. Issue the SCF LISTDEV TCPIP command.
4. Use your list of TCP6SAM names to eliminate the LNP-assigned TCP6SAM
processes. The remaining TCP6SAM process(es) is associated with the default
LNP. This process has access only to the SUBNETs in the default partition.
LNP Guidelines
•
Configure all the SUBNETs before adding the TCP6SAM processes.
•
Do not specify the LNPTPLIST attribute for the default LNP SUBNETs.
•
Do not specify the LNPTPLIST attribute for a configured-tunnel type SUBNET. The
IPTSRC attribute associates the configured-tunnel type SUBNET with the LNP.
•
Each SUBNET configured on the same LNP must be added with the same
TCP6SAM process name(s).