NonStop S-Series Operations Guide (G06.24+)

Overview of Monitoring and Recovery
HP NonStop S-Series Operations Guide—522459-007
3-20
Using OSM or TSM to Locate the Problem
•
Four “port error” messages from group 03: three from the PMF CRU in slot 55, and
one from the SEB in slot 52
•
Two “domain deletion” error messages from processor group 01, both from the
SEB in slot 52
•
A “Path change on device $ZZLAN.E3153.0.A” error message from the Web
application in group 01, indicating that the application had to switch paths to
access the services of the adapter in group 31
•
Fourteen error messages—including path-switch errors—from disk volume
$D3101, whose primary and mirror disks are located in slots 1 and 2 of group 31
You consider the messages and group them conceptually:
•
Processors and applications in groups 01 and 03 are having trouble
communicating with each other—there is a connection problem. As yet, it is
unclear which group is originating the problem.
•
All the port errors and domain deletion errors are from PMF CRUs in slot 55 and a
SEB in slot 52—system components that communicate over the ServerNet Y
fabric.
•
The Web application in group 01 and the disk volume $D3101 attached to group
03 both appear to have failed when attempting to use a primary communication
path. Each was forced to use a secondary path. The path-switch errors from
$3101 are puzzling because the disk process would normally have performed this
switch transparently.
Using OSM or TSM to Locate the Problem
You log onto the OSM Service Connection or the TSM Service Application to look at
system \2DIE4. You see an alarm displayed next to the Y fabric icon in the overview
pane or the tree pane. You select that icon and then select the Alarms tab in the
details pane.
Only one alarm is listed for the Y fabric. You double-click that alarm to display the
Alarm Detail dialog box. Under “Probable Cause,” you find:
•
The PMF CRU in 01.1.55 might be down.
•
The SEB in 01.1.52 might be down.
•
The PMF CRU in 03.1.55 might be down.
•
The SEB in 03.1.52 might be down.
•
The cable connecting port 2 of the SEB in 01.1.52 to port 2 of the SEB in 03.1.52
might be loose or faulty.
Note. Beginning with the G06.11 RVU, TSM provides an additional field called Specific
Problem that provides some additional information and a Repair Actions button that provides
expanded information on the problem and repair actions.