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-12
TCP6MAN
Note that in NonStop TCP/IPv6, the TCP6MON, TCP/IP library and application
components are in the data path. Figure 2-8 on page 2-11 also shows that the TCP/IP
library is pulled into the application context. Data transfer in the NonStop TCP/IPv6
occurs within the library.
The conventional TCP/IP environment shown in Figure 2-8 on page 2-11 requires two
message-system, inter-process communication hops.
TCP6MAN
The manager process (TCP6MAN) runs as a process pair and is the management
point for the NonStop TCP/IPv6 subsystem. Only one manager process pair exists for
each system. TCP6MAN is always named $ZZTCP. After the monitors (TCP6MON)
have been configured at least once in the system, TCP6MAN starts the monitors along
with any other subordinate objects from the system configuration database whenever
TCP6MAN is started.
TCP6MAN automatically configures one TCP6MON for each system as the MASTER
TCP6MON. The MASTER TCP6MON is usually the first TCP6MON started. If the
MASTER TCP6MON processor fails, TCP6MAN picks the TCP6MON in the next
configured processor as the MASTER. TCP6MAN ensures that one MASTER
TCP6MON always exists in the system. For more information about the role of the
master TCP6MON, see TCP6MON.
TCP6MON
The monitor object (TCP6MON) provides the NonStop TCP/IPv6 environment in each
processor; one TCP6MON exists in each configured processor. TCP6MONs are
controlled by the TCP6MAN process.
TCP6MONs are named automatically. The naming convention for TCP6MON is
$ZZTCP.#ZPTMn where n is the processor number in which the TCP6MON resides.
The format for this processor number is hexadecimal (0-F). The TCP6MON object has
a MASTER attribute. The MASTER TCP6MON receives and processes inbound frames
that do not match any filter. The MASTER TCP6MON also replies to all ICMP echo
requests.
TCP6SAM
The socket access method (TCP6SAM) is a process pair provided for
backward-compatibility with socket applications. TCP6SAM provides applications with
a name for a socket transport-service provider. By specifying the TCP6SAM process
as the name of the socket transport-service provider, the application programmer can
access NonStop TCP/IPv6. If the application is using IPv4, no application changes are
needed. For information about porting applications to IPv6, see TCP/IP Programming
Manual.
TCP6SAM provides transport service for applications, but no data passes through
TCP6SAM. For an illustration of the data path for NonStop TCP/IPv6, see Figure 2-8