IPX/SPX Configuration and Management Manual

Managing NonStop™ IPX/SPX With the Subsystem
Control Facility (SCF)
IPX/SPX Configuration and Management Manual—425731-001
3-40
STATUS Command
Trace
displays the status of the trace activity for the primary IPXPROTO process. Values
can be ON or OFF.
STATUS PROCESS Display Format With DETAIL
The format of the display for the STATUS PROCESS command with the DETAIL
option is:
Process Name
displays the name of the process about which you want status information.
MEMORY The process could not get memory during initialization. Possible causes
and recommended actions are
•
The QIO monitor (QIOMON) process may not be configured with
enough memory. Increase memory limits by reconfiguring QIO.
•
The QIOMON process may not be running. Use the QIO subsystem
SCF STATUS MON command to check the status of the QIOMON
process.
NETWORK A network problem prevents the PROCESS object from reaching the
STARTED summary state. Causes and recommended actions are
•
The NetWare server is not running. The process cannot start unless
a NetWare server is running and configured with the same frame
type as the IPXPROTO process.
•
If the NetWare server is fully operational and SLSA LIF
configuration is correct, check that the cables on the network are
fully connected.
NORMAL
•
If the summary state is STOPPED, the diagnostic state is
NORMAL if the process was stopped by a user who executed an
SCF STOP command or an SCF ABORT command against the
process.
•
If the summary state is something other than STOPPED, the
diagnostic state is NORMAL.
UNKNOWN
•
There is a NETWORK or MEMORY problem. The process cannot
distinguish the cause of the STOPPED state. Follow the
troubleshooting methods outlined above for both MEMORY and
NETWORK.
-> STATUS PROCESS $ZNV1, DETAIL
IPXSPX Detailed Status PROCESS \HIMA.$ZNV1
Process Name ........... $ZNV1 State ............... STARTED
Diagnostic State ....... NORMAL Trace ............... ON
Trace File Name ........ \HIMA.$DSV.IPX.TRACE1