iTP Secure WebServer System Administrator's Guide (Version 7.0)
Installing the iTP Secure WebServer
iTP Secure WebServer System Administrator’s Guide—523346-012
2-16
Setup for IP CIP Support
There are other dialogs with the setup script if you choose conventional TCP/IP 
support, or support for both types of support.
LNP Support for TCP/IPv6
LNP can be viewed as an instance of the Conventional TCP/IP (T9551) process that 
spans all CPUs within a system. Each LNP can logically be viewed as a different 
Conventional TCP/IP process running on the system with its own set of IP addresses. 
An IP address used on one LNP cannot be used on a different LNP. Applications on 
one LNP are isolated from applications on different LNPs on the same system in the 
same way they would be if using different Conventional TCP/IP processes. 
Communication between such applications will only be through the attached local area 
networks. TCP/IPv6 does not forward internal packets between partitions. 
With LNP configured, iTP Secure WebServer is able to bind and listen on multiple 
TCPIPv6 transports and servers across multiple networks. Additionally, when LNP is 
configured over TCP/IPv6, iTP Secure WebServer is able to listen on all combinations 
of IP and port from the list of configured combinations provided by the user. For using 
LNP feature of iTP Secure WebServer it is necessary that LNP be properly configured 
on the system.
A typical configuration for enabling iTP WebServer to work with LNP requires a proper 
system-level TCP/IPv6 LNP configuration and proper changes in the iTP Secure 
WebServer's configuration file (multiple Accept directives). For example, if there are 
four TCP/IPv6 transport processes, namely $ZSAM0, $ZSAM1, $ZSAM2, $ZSAM3, 
running on a system configured on four different IP addresses, then iTP WebServer's 
configuration file must specify the following:
Accept -transport /G/ZSAM0 -port 80 -address 172.31.24.12
Accept -transport /G/ZSAM1 -port 80 -address 172.31.24.13
Accept -transport /G/ZSAM2 -port 80 -address 172.31.24.14
Accept -transport /G/ZSAM3 -port 80 -address 172.31.24.15
It is noteworthy that in this case, it becomes mandatory to mention address and port 
attribute for each of the Accept directives. However, the order of the Accept 
directives is not relevant in this case.
Setup for IP CIP Support
In addition to scanning for conventional TCP/IP processes, Parallel Library TCP/IP and 
TCP/IPv6, the setup script checks for the presence of CIPSAM processes on the target 
Note. For more information on system configuration of LNP, see the TCP/IPv6 Configuration 
and Management Manual.
Note. The LNP feature is supported on systems running J06.04 and later J-series RVUs and 
H06.15 and later H-series RVUs.










