NonStop Operations Guide for H-Series and J-Series RVUs

TCPIP Status ROUTE \SYSA.$ZTCO.*
Name Status RefCnt
#ROU11 STARTED 0
#ROU9 STARTED 0
#ROU12 STARTED 0
#ROU8 STARTED 1
#ROU3 STOPPED 0
Monitoring NonStop TCP/IP Subnets
To obtain the status of all NonStop TCP/IP subnets:
> SCF STATUS SUBNET $ZTC0.*
The system displays a listing similar to:
1-> STATUS SUBNET $ZTC0.*
TCPIP Status SUBNET \SYSA.$ZTC0.*
Name Status
#LOOP0 STARTED
#EN1 STARTED
Monitoring the CIP Subsystem
CIP processes run on both the NonStop BladeSystem or NonStop NS-series system and the CLIM,
but they are completely managed from the NonStop host. Monitor CIP processes on the NonStop
BladeSystem or NonStop NS-series system with SCF commands and CLIMCMD commands.
Use the following SCF commands to monitor CIP processes on the NonStop BladeSystem or NonStop
NS-series system and to monitor the connection to the CLIM:
• STATS CLIM, to display protocol statistics for individual processes on the CLIM
• STATS MON, to display statistics pertaining to the interaction of CIP processes on the NonStop
BladeSystem or NonStop NS-series system with applications using the socket interface
• STATUS MON, to display statistics pertaining to the interaction of CIP processes on the NonStop
BladeSystem or NonStop NS-series system with individual CLIMs
• STATUS CLIM, to discover whether a given CLIM is present. If the CLIM is present, this command
also discovers whether the CLIM is started or stopped and whether it is currently being traced.
The detail option also displays information about the physical condition of the CLIM.
This is an example using STATS CLIM to get statistics about CLIM2:
94 Communications Subsystems: Monitoring and Recovery