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-9
Logical-Network Partitioning (LNP)
For examples of configuring the subsystem and applications for LNP, see Configure
the Subsystem for INET-Mode on page 1-5, Configure the Subsystem for INET Mode,
Ethernet Failover, and Shared IP, With LNP on page 1-10, and VB. Start the
Applications (With LNP) on page 1-21.
LNP makes NonStop TCP/IPv6 similar to conventional TCP/IP in the sense that you
can restrict an application’s view of the network by associating the application with a
TCP6SAM process. LNP allows flexible security configurations in the subsystem
because you can prevent unwanted applications in the system from using interfaces in
a configured LNP.
Each LNP has its own set of IP addresses and SLSA logical interfaces (LIFs). An IP
address used on one LNP cannot be used on a different LNP and a LIF cannot be
shared between LNPs. Applications on one LNP are isolated from applications on
different LNPs on the same system in the same way they would be isolated if using
different conventional TCP/IP processes. Communication between such applications is
only possible through the attached local area networks. NonStop TCP/IPv6 does not
forward packets between partitions internally.
The difference between conventional TCP/IP and NonStop TCP/IPv6 with LNP is that
the TCP6SAM process, unlike the NonStop TCP/IP process, spans all the processors
in the whole system; the TCP6SAM process is not limited to the processor in which it
resides. The result is that an application in any processor, even when using LNP to
Figure 2-7. Logical-Network Partitioning: Applications are Restricted to the
Interfaces Within an LNP
VST159.vsd
Global
Internet
Finance
Network
BEA WebLogic
CPU 0
NonStop
TCP/IPv6
LNP 1 LNP 2
BEA WebLogic
Servernet
L018
Customer Billing
Logical Network Partitioning Enabled
LNP 1 LNP 2
LAN02
L019