TCP/IPv6 Configuration and Management Manual (G06.24+)

HP NonStop TCP/IPv6 Configuration and Management Manual—524523-008
8-1
8
SCF Reference for NonStop
TCP/IPv6
This section provides information about:
•
The Subsystem Control Facility (SCF)
•
SCF commands available for NonStop TCPIPv6 (To find a command quickly, see
Table 8-4 on page 8-10.)
•
The PTrace facility
SCF for NonStop TCP/IPv6
SCF provides an operator interface to an intermediate process, the Subsystem Control
Point (SCP), which in turn provides the interface to the I/O processes of the various
subsystems.
The NonStop TCP/IPv6 subsystem runs on the NonStop operating system and
supports SUBNETs using Ethernet LANs.
Ethernet SUBNETs use the ServerNet LAN systems access (SLSA) subsystem to
provide access to Ethernet local area networks (LANs). The NonStop TCP/IPv6
subsystem is a client of the SLSA subsystem.
SCF Commands for TCP6MAN Compared to
SCF Commands for TCP6SAM
This section describes SCF command syntax for both the TCP6MAN and the
TCP6SAM processes.
TCP6SAM SCF syntax differs from TCP6MAN syntax because TCP6SAM provides
backward compatibility for applications. Existing applications expect objects to have
the format $process-name.#subordinate-object-name which is the format that
TCP6SAM uses. By contrast, TCP6MAN objects use the format
$process-name.#TCP6MON-name.subordinate-object-name.
The TCP6SAM and TCP6MAN processes yield different command results. For
example, STATUS PROCESS $ZZTCP yields information about the primary and
backup processor and identification numbers, whereas, STATUS PROCESS
$TCP6SAM-name yields more extensive information (comparable to the STATUS
PROCESS command in conventional TCP/IP.) In addition, when TCP6SAM
nonsensitive SCF commands are applied to the PROCESS, ROUTE, and SUBNET
objects, the information returned reflects only those objects in the processor where the