TCP/IPv6 Configuration and Management Manual (G06.29+, H06.03+, J06.03+)

Overview of NonStop TCP/IPv6
HP NonStop TCP/IPv6 Configuration and Management Manual—524523-012
2-13
ZTCP6REL/ZTCP6SRL (for G-Series RVUs Only)
on page 2-11. As of G06.22, the TCP6SAM process provides a feature from the
conventional NonStop TCP/IP product: the ability to associate a TCP/IP process with
specific IP addresses and, in turn, to associate applications with that process and set
of IP addresses. This feature is called LNP (see Logical-Network Partitioning (LNP) on
page 2-7). You can associate one or two TCP6SAM processes with specific SUBNETs,
then only applications that select those TCP6SAM processes as their transport-service
providers can access the interfaces on those SUBNETs.
In the default LNP, you can have as many TCP6SAM processes in a system as you
wish but you only need one. For TCP6SAM processes in the default LNP, the
recommended naming convention is $ZSAMn where n is a number used to distinguish
among the different TCP6SAM processes. Any TCP6SAM processes that are added to
the system but not specified as LNP transport providers for any SUBNET (that is, not
associated with a SUBNET in the ADD SUBNET command by the LNPTPLIST
attribute) become transport providers for the default LNP.
In the configured LNPs, you can have at most two TCP6SAM processes. You can
name TCP6SAM processes any five alpha-numeric characters preceded by a dollar
sign ($).
ZTCP6REL/ZTCP6SRL (for G-Series RVUs Only)
NonStop TCP/IPv6 on NonStop S-series servers places most of the protocol stack in a
private shared runtime library (SRL) rather than in a process. Users of ZTCP6SRL
transparently use QIO functions without having to explicitly issue calls to initialize the
QIO segment. This architecture allows TCP/IP to retain its context during processing
and shortens the path-length. This library is dynamically loaded into the application’s
process space as soon as the application issues a TCP/IP socket request. Figure 2-8
on page 2-11 shows the application laid over the TCP/IP library. As the application
invokes the TCP/IP library, TCP/IP retains the context of the application while
processing the request. The ZTCP6REL generates the SRL automatically upon
loading.
Note. Multiple TCP6SAM processes in the default LNP do not provide any functional
differences, but configuring two or more in multiple processors provides fault-tolerance.
Note. The Expand application expects a TCP/IP process name to start with Z so you may
want to ensure that at least one TCP6SAM process starts with a Z.
Caution. NonStop TCP/IPv6 uses a private shared runtime library (SRL). If you run programs
that use private SRLs and you are running NonStop TCP/IPv6, do not create private SRLs that
overlap the memory segments: 0x75800000 through 0X759FFFFF and 0x7FE00000 through
0x7FE1FFFF. In addition, QIO reserves 0x20000000 through 0x41FFFFFF
. A failure during a
QIO_ATTACH_SEGMENT call might indicate that your program conflicted with the QIO reserved
segment.