Cluster I/O Protocols (CIP) Configuration and Management Manual (H06.16+, J06.05+)
6 IP CIP Migration, Compatibility and Operational
Differences
The same methods of specifying a NonStop TCP/IPv6 transport-service provider are available for
CIP. Once CIP is installed, applications can use CIP by specifying a CIPSAM process name as
their transport-service provider. An application can change transport-service providers while running
and can also have sockets using conventional NonStop TCP/IP, NonStop TCP/IPv6 and CIP at
the same time. (Parallel Library TCP/IP cannot co-exist with NonStop TCP/IPv6.)
This chapter covers:
• “Summary of High-Level Differences Between Previous TCP/IP Subsystems and CIP”
• “Operational Differences Between Previous TCP/IP Subsystems and CIP” (page 175)
• “Application Programming Differences Between NonStop TCP/IPv6 and CIP” (page 188)
• “TCP/IP Attributes in CIP” (page 193)
• “How to Migrate From NonStop TCP/IP or NonStop TCP/IPv6 to CIP” (page 203)
For high-level comparisons of all NonStop networking products, see the NonStop Networking
Overview.
Summary of High-Level Differences Between Previous TCP/IP Subsystems
and CIP
Table 16 summarizes the differences between conventional TCP/IP, Parallel Library TCP/IP,
NonStopTCP/IPv6, and CIP.
NOTE: To find out which servers support these subsystems, see the planning guide for your system
or the NonStop Networking Overview.
Table 16 High-Level Differences Between Conventional TCP/IP, Parallel Library TCP/IP, NonStop
TCP/IPv6, and CIP
CIPNonStop TCP/IPv6Parallel Library TCP/IPConventional TCP/IP
Supported interface types:
Ethernet (Gigabit) with Jumbo
frames
Supported interface types:
Ethernet (Ethernet, Fast
Ethernet, Gigabit Ethernet
with Jumbo frames)
Supported interface types:
Ethernet (Ethernet, Fast
Ethernet, Gigabit Ethernet
with Jumbo frames)
Supported interface types:
• ATM
• Ethernet (Ethernet, Fast
Ethernet, Gigabit Ethernet
without Jumbo frames)
• SNAP (token-ring or
Ethernet)
• X.25
System configuration
database: Supports
System configuration
database: Supports
System configuration
database: Supports
System configuration
database: Does not support
Subsystem name: CIPSubsystem name: TCPIPV6Subsystem name: PTCPIPSubsystem name: TCPIP
transport-service provider
name: Any CIPSAM process
transport-service provider
name: Any TCP6SAM
transport-service provider
name: Any TCPSAM
Transport-service provider
name: ($ZTC0 default) or
name. ($ZTC0 default)
Program name is CIPSAM.
process name. ($ZTC0
default) Program name is
TCP6SAM
process name. ($ZTC0
default). Program name is
TCPSAM.
any TCP/IP process name.
Program name is TCPIP
SPI subsystem ID: ZCIPSPI subsystem ID: ZTC6SPI subsystem ID: ZTCPSPI subsystem ID: ZTCI
SPI subsystem number: 259SPI subsystem number: 246SPI subsystem number: 220SPI subsystem number: 80
174 IP CIP Migration, Compatibility and Operational Differences










