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

The OSM Service Connection provides several options for obtaining diagnostic data about CLIMs.
The System action Collect Diagnostic Data generates Diagnostic Data files for the system, allowing
you to locate and reviewCLIM diagnostic data. The CLIM action Reboot performs a CLIM reboot;
you can select the “Yes” default value to generate a dump of CLIM diagnostic data before the
CLIM reboots. For detailed information about these options and others, see the OSM Service
Connection User’s Guide.
Monitoring Communications Subsystems and Their Objects
Monitoring and recovery operations for communications subsystems can be complex. An error in
any of the components—service providers, clients, objects, adapters, processes, and so on—can
generate multiple error messages from many interdependent subsystems and processes. Analyzing
and solving an error that originates in an object controlled by a LAN or a WAN often requires
that you methodically gather status information about the affected services and then eliminate
objects that are working normally.
Detailed monitoring and recovery techniques for devices and processes related to communications
subsystems are discussed in detail in the manuals for each subsystem. For more information, refer
to “Related Reading for Communications Subsystems” (page 99).
This guide provides some information about automated HP tools and basic commands you can
use to identify and resolve common problems. The automated HP tools identified in “Automated
HP Tools That Monitor Communications Subsystems” (page 88) play an essential role of
automatically alerting you to current or developing problems. SCF also provides a powerful tool
for monitoring and collecting information about subsystem objects is the SCF facility. You can use
SCF commands to get information and status for subsystem objects by name, device type, or device
subtype.
Subdevices are defined if a subsystem potentially operates on numerous, separately addressable
objects, such as stations on a multipoint line; the line is a device, and the stations are subdevices.
For a list of subsystems with their device type numbers and device subtypes, see “Using SCF to
Determine Your System Configuration” (page 39).
Automated HP Tools That Monitor Communications Subsystems
NonStop Availability Statistics and Performance (ASAP), NonStop I/O Essentials plug-in to HP
SIM, and NonStop Cluster Performance Essentials can monitor communication subsystem objects
and alert you to exception conditions or performance problems. See Table 16 (page 88).
Table 16 Automated HP Tools That Monitor Communications Subsystems
For more information, see..Monitored objectsHP tools
“NonStop Availability Statistics and Performance (ASAP)” (page 72)CommNonStop
Availability
HP NonStop ASAP Server Manual
Statistics
HP NonStop ASAP Client Manual
and
Performance
(ASAP)
HP NonStop ASAP QuickStart Guide
“Using HP SIM” (page 55)CLIM, FCSA,
G4SA, IOAM
HP SIM
using I/O
“NonStop I/O Essentials” (page 57)
Essentials
plug-in
HP SIM for NonStop Manageability
NonStop I/O Essentials Installation and Quick Start Guide and online help
Monitoring the SLSA Subsystem
This section describes how to obtain the status of adapters, SACs, LIFs, and PIFs. For more
information on the SLSA subsystem, refer to the LAN Configuration and Management Manual.
88 Communications Subsystems: Monitoring and Recovery