TCP/IPv6 Migration Guide

Transport-Service Provider Differences for NonStop
TCP/IPv6
HP NonStop TCP/IPv6 Migration Guide—524524-004
2-6
Compatibility
Compatibility
Consider these compatibility issues when using TCP6SAM:
•
Event Management Service (EMS)
•
Fault-Tolerant Behavior
•
SCF on page 2-8
•
Trace on page 2-8
Event Management Service (EMS)
TCP6SAM uses the same subsystem ID, ZTCI, as NonStop TCP/IP. The EMS
messages issued by TCP6SAM are a subset of the ones issued by NonStop TCP/IP.
Fault-Tolerant Behavior
The difference in implementation between NonStop TCP/IP and TCP6SAM in terms of
where the actual socket is created and what a socket backup open does results in a
slightly different fault-tolerant behavior in TCP6SAM than in the TCP/IP process of
NonStop TCP/IP.
TCP6SAM can be started as a continuously available process pair similar to NonStop
TCP/IP.
Similarities
•
When the TCP6SAM primary processor fails, the backup takes over as the
primary. When the processor is reloaded, the primary creates a backup on that
processor.
•
When the TCP6SAM backup processor fails, the TCP6SAM primary process
restarts the backup when the processor is reloaded.
Differences
Applications can be fault-tolerant, but sockets are not fault-tolerant in the NonStop
TCP/IPv6 environment.
Table 2-1 on page 2-7 lists other differences in fault-tolerant behavior.