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

Manage the NonStop TCP/IPv6 Subsystem
HP NonStop TCP/IPv6 Configuration and Management Manual—524523-012
6-25
LNP Guidelines

SUBNETs configured as failover pairs must be assigned to the same LNP.

A SUBNET can be configured with at most two TCP6SAM processes specified in
its LNPTPLIST attribute.

Route and ARP entries between LNPs cannot be shared, each is independent.

Adding of route and ARP entries requires the use of the SUBNET attribute to
assign the entry to a specific LNP. If this attribute is not specified, the entry is
assigned to the first interface that has matching criteria which can cause the entry
being assigned to a different LNP than the intended one. When using LNP, you
should add a route or ARP entry and specify which SUBNET to use, unless also
using the ALLROUTES or ALLENTRY attributes.

Adding routes and using the ALLROUTES attribute results in a route being added
to each SUBNET configured on the same IP subnetwork that is applicable based
on the route’s destination and gateway addresses. Therefore, the route can be
added to SUBNETs on different logical-network partitions.

Adding IPv4 entry objects and using the ALLENTRY attribute results in an entry
object being added to each SUBNET configured on the same IP subnetwork as the
IP address being used for the entry object. This action can cause the entry being
added to SUBNETs on different logical-network partitions.

A SUBNET can belong to only one logical network partition, which implies that a
LIF can only belong to one LNP.

SCF commands issued on a TCP6SAM process only return information about
objects configured under the LNP with which the TCP6SAM process is associated.
This condition also applies to SPI requests built by applications and issued directly
to a TCP6SAM process.

All the SCF-alterable attributes on a TCP6MON object apply equally to all the
LNPs that are configured.

If you use LNP in a DUAL-mode environment and want to use tunneling, use
configured tunneling rather than automatic tunneling because the automatic tunnel
associates itself with the first available DUAL-mode SUBNET and is only available
to applications associated with the LNP of that SUBNET. To use tunneling in an
LNP environment, add configured tunnels for each LNP for which you want
tunneling.

You cannot use SCF to alter the LNPTPLIST on a SUBNET.

When LNP is enabled, applications are limited to the IP addresses within the LNP
being used by a socket. This condition can change the expected behavior of an
application used prior to enabling LNP. An example would be an application such
as TELSERV. If, prior to enabling LNP, only one TELSERV process was started
that serviced connections from every configured SUBNET on a TCP/IPv6
subsystem, you must start a TELSERV process on each LNP to service the
connections. For an example of starting applications such as TELSERV in each
LNP, see V
B. Start the Applications (With LNP) on page 1-21.