Introduction to Networking for NonStop NS-Series Servers (H06.03+, J06.03+)

Networking on Integrity NonStop Servers
Introduction to Networking for HP Integrity NonStop NS-Series Servers—529874-003
1-13
Integrity NonStop Server Networking Compared to
Other Platforms
will get because the interface is no longer associated with the TCP/IP process used by
the applications.
To have application isolation on specific interfaces in the NonStop TCP/IPv6
environment, you must configure the NonStop TCP/IPv6 subsystem to use LNP.
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
TCP/IP 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 NonStop TCP/IPv6 TCP/IP process (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 restrict itself to specific interfaces, has direct
access (with no interprocess, message-system hop) to the network adapter.
For more information about LNP, see the TCP/IPv6 Configuration and Management
Manual.
Persistence
The NonStop TCP/IPv6 product on the Integrity NonStop server participates in the
system configuration database as a generic process and can be managed by the
persistence manager so that the NonStop TCP/IPv6 manager process (TCP6MAN) is
restarted whenever it abends, is stopped through TACL, or the system is reloaded.
If you add the TCP6MAN process as a generic process configured in this way,
TCP6MAN starts automatically upon system reload and restores its stored and
subordinate objects.
For more information about configuring NonStop TCP/IPv6 as a persistent process,
see the TCP/IPv6 Configuration and Management Manual. For more information about
managing generic processes, see the SCF Reference Manual for the Kernel
Subsystem.