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

In NonStop TCP/IPv6, interfaces configured for NONSHAREDIP failover have separate IP addresses
and outgoing data uses the usual routing table rules. (Only the first routing table match is used in
NonStop TCP/IPv6, however, so even if both interfaces have a route, only one is selected.)
SHAREDIP always alternates between the two interfaces of a failover pair and this option tells
TCP/IPv6 to do the same for NONSHAREDIP.
In CIP, CLIM-to-CLIM failover most closely resembles the NonStop TCP/IPv6 NONSHAREDIP
failover. CIP uses round-robin rotation among the routes to CLIMs, so load balancing occurs as
long as routes to both CLIMs exist. You can ensure any static routes are added to both CLIMs;
dynamic routes will match because the CLIMs must be on the same LAN segment. This option is
no longer needed in CIP. (See “Failover Differences (Fault Tolerance)” (page 183).)
PORT-SHARE-ENABLE-ALL
This NonStop TCP/IPv6 Monitor attribute allows applications running in different processors to
bind to the same TCP or UDP yet have different IP addresses. CIP algorithms makes this attribute
unnecessary, and it is therefore not supported in CIP. (This attribute enabled behavior unique to
the NonStop TCP/IPv6 architecture.)
TCP-INIT-REXMIT-TIMEOUT
This NonStop TCP/IPv6 Monitor attribute, which sets the initial retransmit timer-value in milliseconds
to use on a TCP connection, is not supported in CIP.
TCP-MAX-REXMIT-TIMEOUT
This NonStop TCP/IPv6 Monitor attribute, which sets the maximum time value in milliseconds
allowed for a TCP retransmission timeout, is not supported by CIP.
TCP-MIN-REXMIT-TIMEOUT
This NonStop TCP/IPv6 Monitor attribute, which set the minimum value allowed for the TCP
retransmission timeout, is not supported by CIP.
TCP-TOTAL-REXMIT-DURATION
This NonStop TCP/IPv6 Monitor attribute, which sets the total time a TCP connection can be in the
retransmission state without receiving an acknowledgement from the other endpoint before the TCP
connection is dropped, is not supported in CIP.
TCPCWNDMULTIPLIER
This NonStop TCP/IPv6 Monitor attribute, which was used to calculate the initial TCP congestion
window, is not supported by CIP. CIP uses its own algorithm to calculate the initial TCP congestion
window, ranging from 1 to 4. Higher values are considered potentially harmful to overall network
stability and so the CIP defaults are used in CIP.
TCPCOMPAT42
This NonStop TCP/IPv6 Monitor attribute, which set a flag to make the TCP6MON compatible
with Berkeley Standard Distribution TCP/IP (BSD) 4.2 versions, is not supported by CIP. In BSD
4.2, TCP sequence numbers were 32-bit signed values. Modern implementations of TCP use
unsigned values. This option caused the initial sequence number to start in the range 2^31 rather
than the full unsigned range of 2^32. Also, under BSD 4.2, keepalive packets must contain at
least one byte, or else the remote end does not respond. The default for this attribute was ON.
IRDP SUBNET
The IRDP SUBNET attribute enables or disables the ICMP Router Discovery Protocol on the SUBNET
interface. IRDP is a mechanism for locating default routers. CIP does not support this attribute.
202 IP CIP Migration, Compatibility and Operational Differences