Cluster I/O Protocols (CIP) Configuration and Management Manual (H06.16+, J06.05+)

Table 16 High-Level Differences Between Conventional TCP/IP, Parallel Library TCP/IP, NonStop
TCP/IPv6, and CIP (continued)
CIPNonStop TCP/IPv6Parallel Library TCP/IPConventional TCP/IP
Transport service provider
process: CIPSAM PROCESS
object
Transport service provider
process: TCP6SAM
PROCESS object
Transport service provider
process: TCPSAM
PROCESS object
Transport service provider
process: TCP/IP PROCESS
object
TCP/IP and SCTP (see
“Configuring Stream Control
TCP/IPTCP/IPSupported protocols
Transmission Protocol (SCTP)
(IP and Telco CIP)” (page 112))
Operational Differences Between Previous TCP/IP Subsystems and CIP
Several operational differences exist between CIP and previous NonStop host system TCP/IP
subsystems. The main differences are:
• CIP does not use the ServerNet LAN Systems Access (SLSA) subsystem.
• Routing configuration and behavior are different.
• IPSec is a new feature supported in CIP.
• The SUBNET object is only provided as a subordinate object for the CIPSAM (transport provider)
object for application backward-compatibility. You do not configure the SUBNET.
• There is no neighbor discovery and autoconfiguration (ND6HOSTD) process. In NonStop
TCP/IPv6, the ND6HOSTD process received and processed IPv6 router advertisement (RA)
packets and updated the global IPv6 address information in the DNS. You could use it for
updating the DNS with automatically generated IPv6 addresses.
• The SNMP TCP/IP subagent (TCPIPSA) is not supported and therefore you cannot collect
information on the CLIM from the NonStop SNMP agent.
• The CIP operational interface is significantly different. Table 17: Subsystem Task
Comparisonshows how conventional NonStop TCP/IP, Parallel Library TCP/IP, and NonStop
TCP/IPv6 tasks are performed in CIP.
Operational Differences Between Previous TCP/IP Subsystems and CIP 175