TCP/IP (Parallel Library) Migration Guide

Migration Considerations
HP NonStop TCP/IP (Parallel Library) Migration Guide—522272-003
3-2
Applications: Restricting to Listen on Only Some
Subnets
•
SWAN on page 3-12
•
Telserv on page 3-129
•
Trace on page 3-13
Applications: Restricting to Listen on Only Some Subnets
Subnets are managed by TCPMON, not by TCPSAM. Because TCPMON runs in all
Parallel Library TCP/IP-configured processors (TCPSAM, like the conventional TCP/IP
process, runs only in a processor pair) all subnets and IP addresses are available to all
applications regardless of the TCPSAM process name specified as the
transport-service provider. Because all subnets are available to all applications, an
application cannot be restricted to listening on only some subnets. In conventional
TCP/IP, you could restrict applications to some subnets because the TCP/IP process
serving as the transport-service provider provided exclusive access to its subnets.
Attribute Defaults and SCF Object Differences
There are differences between the SCF commands and attributes in conventional and
Parallel Library TCP/IP.
Unsupported SCF Objects
The following SCF objects that are supported in conventional TCP/IP are not
supported in Parallel Library TCP/IP:
•
ADDRMAP
•
SERVER
For some SCF attributes and their defaults, differences also exist between
conventional TCP/IP and Parallel Library TCP/IP. These differences are shown in the
following tables.
ADD ENTRY Command
Attribute Conventional TCP/IP Parallel Library TCP/IP
TYPE ATMARP No default No such attribute
ATMADDR No default No such attribute
PVCNAME No default No such attribute
SUBNET No default No such attribute