TCP/IPv6 Migration Guide

Migration Considerations
HP NonStop TCP/IPv6 Migration Guide—524524-004
3-2
Application Behavior
•
SPI Interface on page 3-9
•
SWAN on page 3-9
•
System Configuration Database on page 3-9
•
Telserv on page 3-109
•
Trace on page 3-10
•
Tips for Migrating from NonStop TCP/IP to NonStop TCP/IPv6 on page 3-10
Application Behavior
For AF_INET sockets using conventional TCP/IP, a backlog parameter value of less
than or equal to 0 (zero) allows the socket to accept the number of connections
configured for the TCP-LISTEN-QUE-MIN parameter of the transport process. These
values can allow up to 5 connections (the default value for TCP-LISTEN-QUE-MIN).
For AF_INET or AF_INET6 sockets using NonStop TCP/IPv6, a backlog parameter
value of less than or equal to 0 (zero) is ignored. The maximum number of pending
connections is always 5.
Applications: Restricting Access to Network Interfaces
SUBNETs are managed by TCP6MON, not by TCP6SAM. Because TCP6MON runs in
all NonStop TCP/IPv6-configured processors, all SUBNETs and IP addresses are
available to all applications regardless of the TCP6SAM process name specified as the
transport-service provider. If you want to restrict application access to network
interfaces, you must configure the subsystem to use logical network partitioning (LNP).
When you use LNP, you configure SUBNETs with a list of TCP6SAM processes. This
configuration limits access to these SUBNETs to applications using the specified
TCP6SAM processes as their transport-service providers. For more information about
LNP, see Logical Network Partitioning (LNP) on page 2-2 and the TCP/IPv6
Configuration and Management Manual.
Attribute Defaults
There are differences between NonStop TCP/IP and NonStop TCP/IPv6 for some of
the SCF attributes and their defaults. These differences are shown in the following
tables.
ADD ROUTE
ADD ROUTE Attribute NonStop TCP/IP NonStop TCP/IPv6
SUBNET No such attribute No default value
FAMILY No such attribute INET
ALLROUTES No such attribute OFF