HP OpenVMS Systems Documentation

Compaq Availability Manager User's Guide

The LAN Adapter Transmit Data page, shown in Figure 4-22, displays LAN adapter transmit data.

Figure 4-22 LAN Adapter Transmit Data Page

Table 4-22 describes the data displayed in Figure 4-22.

The LAN Adapter Receive Data page, shown in Figure 4-23, displays LAN adapter receive data.

Figure 4-23 LAN Adapter Receive Data Page

Table 4-23 describes the data displayed in Figure 4-23.

The LAN Adapter Events Data page, shown in Figure 4-24, displays LAN adapter events data.

Figure 4-24 LAN Adapter Events Data Page

Table 4-24 describes the data displayed in Figure 4-24.

The LAN Adapter Errors Data page, shown in Figure 4-25, displays LAN adapter errors data.

Figure 4-25 LAN Adapter Errors Data Page

Table 4-25 describes the data displayed in Figure 4-25.

The Availability Manager indicates resource availability problems in the Event pane Figure 5-1 of the main Application window (see Figure 1-1).

Figure 5-1 OpenVMS Event Pane

The Event pane helps you identify system problems. In many cases, you can apply fixes to correct these problems as well, as explained in Chapter 6.

The Availability Manager displays a warning message in the Event pane whenever it detects a resource availability problem. If logging is enabled (the default), the Availability Manager also logs each event in the Event Log file, which you can display or print. (See Section 5.2 for the location of this file and a cautionary note about it.)

Occurrence Counters

During data collection, any time data meets or exceeds the threshold for an event, an occurrence counter is incremented. When the incremented value matches the value in the Occurrence box on the Event Customization page (Figure 1-6), the event is posted in the Event pane of the Application window (see Figure 1-1).

Note that some events are triggered when data is lower than the threshold; other events are triggered when data is higher than the threshold.

If, at any time during data collection, the data does not meet or exceed the threshold, the occurrence counter is set to 0, and the event is removed from the Event pane. Figure 5-2 depicts this sequence.

Figure 5-2 Testing for Events

The Availability Manager can display events for all nodes that are currently in communication with the Data Analyzer. When an event of a certain severity occurs, the Availability Manager adds the event to a list in the Event pane.

The length of time an event is displayed depends on the severity of the event. Less severe events are displayed for a short period of time (30 seconds); more severe events are displayed until you explicitly remove the event from the Event pane (explained in Section 5.1.2).

5.1.1 Data in the Event Pane

Table 5-1 identifies the data items displayed in the Event pane.

Appendix B contains tables of events that are displayed in the Event pane. In addition, these tables contain an explanation of each event and the recommended remedial action.

5.1.2 Event Pane Menu Options

The Availability Manager uses the following criteria to determine whether to post an event and display it in the Event pane:

• Data collection posts an event if the event condition exists for the number of data collections specified in the Occurrence value on the Event Customization page (Figure 5-3).
  

  Figure 5-3 Sample Event Customization Page

  ---

  
  The sample Event Customization page indicates an Occurrence value of 2. This means that if the DSKERR event exceeds its threshold of 15 for two consecutive data collections, the DSKERR event is posted in the Event pane.
• When an event is posted, data is collected at the Event interval shown on the Data Collection Customization page (Figure 5-4).
  

  Figure 5-4 OpenVMS Data Collection Customization Page

  ---

  
  On the Data Collection Customization page, for example, the Event interval for Disk Status is every 15 seconds.
• The data value displayed in the Node pane that is associated with the event turns red when an event is posted (see Figure 5-5).
  

  Figure 5-5 OpenVMS Node Pane

  ---

  
• When an event is posted, it is added to the Events Log file by default:
  • On OpenVMS systems, the Events Log file is:

    AMDS$AM_LOG:ANALYZEREVENTS.LOG

    
    A new version of this file is created each time you access the Availability Manager.
  • On Windows systems, the Events Log file is:

    AnalyzerEvents.log

    
    This file, which is in the installation directory, is overwritten each time you access the Availability Manager.
  
  The following example shows a partial event log file:

  VAXJET 01-22-2001 11:24:50.67 0 CFGDON VAXJET configuration done DBGAVC 01-22-2001 11:25:12.41 0 CFGDON DBGAVC configuration done AFFS5 01-22-2001 11:25:13.23 0 CFGDON AFFS5 configuration done DBGAVC 01-22-2001 11:25:18.31 80 LCKCNT DBGAVC possible contention for resource REG$MASTER_LOCK VAXJET 01-22-2001 11:25:27.47 40 LOBIOQ VAXJET LES$ACP_V30 has used most of its BIOLM process quota PEROIT 01-22-2001 11:25:27.16 0 CFGDON PEROIT configuration done KOINE 01-22-2001 11:25:33.05 99 NOSWFL KOINE has no swap file MAWK 01-22-2001 11:26:20.15 99 FXTIMO MAWK Fix timeout for FID to Filename Fix MAWK 01-22-2001 11:26:24.48 60 HIDIOR MAWK direct I/O rate is high REDSQL 01-22-2001 11:26:30.61 10 PRPGFL REDSQL _FTA2: high page fault rate REDSQL 01-22-2001 11:26:31.18 60 PRPIOR REDSQL _FTA7: paging I/O rate is high MAWK 01-22-2001 11:26:24.48 60 HIDIOR MAWK direct I/O rate is high AFFS52 01-22-2001 11:25:33.64 60 DSKMNV AFFS52 $4$DUA320(OMTV4) disk mount verify in progress VAXJET 01-22-2001 11:38:46.23 90 DPGERR VAXJET error executing driver program, ... REDSQL 01-22-2001 11:39:18.73 60 PRCPWT REDSQL _FTA2: waiting in PWAIT REDSQL 01-22-2001 11:44:37.19 75 PRCCUR REDSQL _FTA7: has a high CPU rate

For more detailed information about a specific event, double-click any event data item in the Event pane. The Availability Manager first displays a data page that most closely corresponds to the cause of the event. You can choose other tabs for additional detailed information.

For a description of data pages and the information they contain, see Chapter 3.

You can perform fixes on OpenVMS nodes to resolve resource availability problems and improve system availability.

This chapter discusses the following topics:

• Understanding fixes
• Performing fixes

When you suspect or detect a resource availability problem, in many cases you can use the Availability Manager to analyze the problem and to perform a fix to improve the situation.

Availability Manager fixes fall into these categories:

• Node fixes
• Process fixes
• Cluster interconnect fixes

You can access fixes, by category, from the pages listed in Table 6-1.

Table 6-2 summarizes various problems, recommended fixes, and the expected results of fixes.

Most process fixes correspond to an OpenVMS system service call, as shown in the following table:

Be aware of the following facts before you perform a fix:

• You must have write access to perform a fix. To perform LAN fixes, you must have control access.
• You cannot undo many fixes. For example, after using the Crash Node fix, the node must be rebooted (either by the node if the node reboots automatically, or by a person performing a manual boot).
• Do not apply the Exit Image, Delete Process, or Suspend Process fix to system processes. Doing so might require you to reboot the node.
• Whenever you exit an image, you cannot return to that image.
• You cannot delete processes that have exceeded their job or process quota.
• The Availability Manager ignores fixes applied to the SWAPPER process.

How to Perform Fixes

Standard OpenVMS privileges restrict users' write access. When you run the Data Analyzer, you must have the CMKRNL privilege to send a write (fix) instruction to a node with a problem.

The following options are displayed at the bottom of all fix pages:

The following sections explain how to perform node fixes and process fixes.