TCP/IPv6 Configuration and Management Manual (G06.24+)

Overview of NonStop TCP/IPv6
HP NonStop TCP/IPv6 Configuration and Management Manual—524523-008
2-8
Logical-Network Partitioning (LNP)
You can limit the shared ports by adding one or both of the DEFINEs:
ADD DEFINE =PTCPIP^FILTER^TCP^PORTS, FILE Pstartport.Pendport
ADD DEFINE =PTCPIP^FILTER^UDP^PORTS, FILE Pstartport.Pendport
The startport and endport variables are integers specifying the allowable port
range. The =PTCPIP^FILTER^TCP^PORTS key limits the shared TCP ports to the
range defined in startport and endport. The =PTCPIP^FILTER^UDP^PORTS key
limits the shared UDP ports to the range defined in startport and endport. Ports
outside those ranges are not shared.
You must always specify the =PTCPIP^FILTER^KEY DEFINE to enable round-robin
filtering. If you want to limit TCP and UDP ports, add the appropriate DEFINE after the
=PTCPIP^FILTER^KEY DEFINE.
Logical-Network Partitioning (LNP)
One of the most important differences between conventional TCP/IP and NonStop
TCP/IPv6 that influences how you configure the subsystem is that NonStop TCP/IPv6
has one manager process ($ZZTCP) and all interfaces (LIFs) are associated with that
single process. In conventional TCP/IP, you can have multiple TCP/IP processes, each
having one or more interfaces uniquely associated with it, as shown in Figure 2-5.
In NonStop TCP/IPv6, if you do not configure the environment to use logical-network
partitioning, applications using NonStop TCP/IPv6 do not know which LIF or IP address
they will get because the LIF and IP address are no longer associated with the TCP/IP
process used by the applications, as shown in Figure 2-6 on page 2-9.
Figure 2-5. Conventional TCP/IP: Data From the Interface is Restricted to
Applications Using the Associated Process
VST127.vsd
Application 2
Application 1
1.2.3.4
1.2.3.5
1.2.3.6
TCP/IP
Process 1
1.2.3.7
1.2.3.8
1.2.3.9
LAN Adapter
TCP/IP
Process 2
LAN Adapter