TCP/IPv6 Migration Guide

Migration Considerations
HP NonStop TCP/IPv6 Migration Guide—524524-004
3-7
Modes
Naming Conventions
The PROCESS object has the reserved name of $ZZTCP.
The MON object has the reserved name of $ZPTMn, where n is the number (in
hexadecimal) of the processor in which the MON resides.
The ROUTE object has reserved names. The reserved names for ROUTE start with:
EA, DDcpu-number, DAcpu-number, DRcpu-number, NDcpu-number, and RT.
The names for ARP entries must start with EA.
Master TCP6MON
The monitor object (TCP6MON) provides the NonStop TCP/IPv6 environment in each
processor; there is one monitor object in each configured processor. The monitor
objects are controlled by the TCP6MAN process. The monitor object is 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.
Modes
NonStop TCP/IPv6 has three operating modes: INET, INET6, and DUAL. In INET
mode, NonStop TCP/IPv6 functions in the same manner as Parallel Library TCP/IP
and supports TCP/IP version 4 (IPv4) communications. In INET6 mode, NonStop
TCP/IPv6 supports TCP/IP version 6 (IPv6) communications. IPv6 is an Internet
Engineering Task Force (IETF) standard that extends the 32-bit address of IPv4 to 128
bits. In DUAL mode, NonStop TCP/IPv6 supports both IPv4 and IPv6 communications.
NonStop Operations
NonStop TCP/IPv6 supports Ethernet failover which provides fault-tolerance at the
adapter level. Unlike other failover implementations, NonStop TCP/IPv6 Ethernet
failover does not require one of the LIFs to act as a “hot standby” in anticipation of a
failure. Both LIFs are active, allowing inbound and outbound network traffic to be
distributed between them. Therefore, you gain scalability when all your adapters are
functioning correctly. See the TCP/IPv6 Configuration and Management Manual for
more information about Ethernet failover.
Persistence Manager
NonStop TCP/IPv6, unlike NonStop TCP/IP, participates in the system configuration
database; that is, changes to the SCF objects for NonStop TCP/IPv6 are stored in the
system configuration database so that the subsystem can be restored by the