TCP/IPv6 Migration Guide

Transport-Service Provider Differences for NonStop
TCP/IPv6
HP NonStop TCP/IPv6 Migration Guide—524524-004
2-8
SCF
SCF
TCP6SAM cannot be used for configuring NonStop TCP/IPv6. TCP6MAN must be
used for configuration commands. See the TCP/IPv6 Configuration and Management
Manual for more information about SCF for NonStop TCP/IPv6.
TCP6SAM supports some SCF commands, which are shown in Table 2-2. TCP6SAM
supports the PROCESS, SUBNET, and ROUTE objects but does not support the
ENTRY, ADDRMAP, and SERVER objects.
The TCP6SAM SCF nonsensitive commands, when applied to the PROCESS,
ROUTE, and SUBNET objects, yield information about those objects in the processor
where the TCP6SAM process resides. (For information about these objects on all
configured processors, use the SCF commands for the TCP6MAN process. See the
TCP/IPv6 Configuration and Management Manual for more information about SCF for
NonStop TCP/IPv6.)
The SCF commands that are supported by TCP6SAM are discussed in detail in the
TCP/IPv6 Configuration and Management Manual.
Trace
Tracing in TCP6SAM primary and backup processes is enabled or disabled using the
SCF TRACE START or STOP command. The Trace records are compatible with those
generated by NonStop TCP/IP. The Trace records can be viewed and printed by the
same PTrace module used by NonStop TCP/IP (ZTCIPTR).
Note. The TCP6SAM process displays TCPIP instead of TCPIPV6 in SCF return displays and
does not display IPv6 addresses.
Table 2-2. Commands and Object Types for TCP6SAM
Object Types
SCF
Command PROCESS ROUTE SUBNET
ABORT Command X
INFO Command X X X
LISTOPENS Command X
NAMES Command X X
PRIMARY Command X
STATS Command X X X
STATUS Command X X X
STOP Command X
TRACE Command X
VERSION Command X