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

ServerNet wide area network (SWAN) concentrator. Examples of IOPs include, but are not limited
to, line-handler processes for Expand and other communications subsystems.
CIP Processes
Cluster I/O Protocols (CIP) processes provide configuration and management interfaces for I/O
between CLIMs and NonStop server blades in NonStop BladeSystems. For information about CIP
processes, refer to the Cluster I/O Protocols (CIP) Configuration and Management Manual.
Generic Processes
Generic processes are configured by the SCF interface to the Kernel subsystem. They can be
configured in one or more processors. Although sometimes called system-managed processes,
generic processes can be either system processes or user-created processes. Any process that can
be started from a TACL prompt can be configured as a generic process. Generic processes can
be configured to have persistence; that is, to automatically restart if stopped abnormally.
Examples of generic processes:
• The $ZZKRN Kernel subsystem manager process
• Other generic processes controlled by $ZZKRN; for example:
The $ZZSTO storage subsystem manager process◦
◦ The $ZZWAN wide area network (WAN) subsystem manager process
◦ QIO processes
◦ OSM server processes
◦ The $ZZLAN ServerNet LAN Systems Access (SLSA) subsystem manager process
◦ The $FCSMON fibre channel storage monitor
For more information, refer to the SCF Reference Manual for the Kernel Subsystem.
Monitoring Processes
This section briefly provides examples of some of the HP tools available to monitor processes. For
some processes, such as IOPs, monitoring is more fully discussed in other manuals. In general, use
this method to monitor processes:
1. Develop a list of processes that are crucial to the operation of your system.
2. Determine how each of these processes is configured.
3. Use the appropriate tool to monitor the process.
80 Processes: Monitoring and Recovery