TCP/IPv6 Configuration and Management Manual (G06.29+, H06.03+, J06.03+)

SCF Reference for NonStop TCP/IPv6
HP NonStop TCP/IPv6 Configuration and Management Manual—524523-012
8-2
Object Types
The SCF STATUS PROC command for TCP6SAM differs from the SCF STATUS MON
$ZZTCP.* command. The SCF STATUS PROC command does not provide complete
CPU information for the connections for which accept() was not posted. To obtain
complete information about CPUs, use the SCF STATUS MON $ZZTCP.* command.
Object Types
You can monitor and control the NonStop TCP/IPv6 subsystem by issuing commands
that act on one or more NonStop TCP/IPv6 subsystem objects. Each object has an
object type and an object name. The object type describes the type of object. The
object name uniquely identifies the object within the system.
The NonStop TCP/IPv6 subsystem has two PROCESS object types:

TCP6MAN

TCP6SAM
The TCP6MAN and TCP6SAM processes support different subordinate objects and
have different SCF command syntax, attribute definitions, and displays. This section
describes each command in alphabetic order. In this section, when the command
applies to both the TCP6MAN and TCP6SAM processes, the TCP6MAN command
syntax is described first with the TCP6SAM command syntax immediately following.
There are six object types supported by TCP6MAN:

PROCESS

MON

SUBNET

ROUTE

ENTRY

null
There are four object types supported by TCP6SAM:

PROCESS

SUBNET

ROUTE

null
Figure 8-1 on page 8-3 shows the object hierarchy for TCP6MAN and that the ROUTE,
SUBNET, and ENTRY object types are peers. The ROUTE, SUBNET, and ENTRY
object types are subordinate to the process and monitor (TCP6MON) objects. This
hierarchy is important when issuing commands to the NonStop TCP/IPv6 subsystem
for processing. For example, as the ROUTE, SUBNET, and ENTRY object types are
subordinate to the process and monitor (TCP6MON) object types, any commands