2 Problem Detection and Reporting

This chapter provides information about problem detection and reporting by the platform operating system and the EPAP application.

2.1 Detecting and Reporting Problems

Problems are detected and reported by the platform operating system and the EPAP application.

The EAGLE Application B Card (E5-APP-B) platform constantly monitors its operational status using the System Health Check utility syscheck. This utility can be initiated also by the user. For more details about syscheck, see System Health Check Overview.

2.2 E5-APP-B Card LEDs

This section describes the LEDs found on the front face of the E5-APP-B card.

Server Panel LEDs

Figure 2-1 shows the E5-APP-B card LEDs on the front panel

Figure 2-1 E5-APP-B Card LEDs

img/card_overview-2.jpg

The following light-emitting diode (LED) status indicators can be found on the E5-APP-B card:

  • One Server Status indicator (A)
  • Four E-Net link and Active LED status indicators (B)
  • Two drive module status indicators (C)
  • One Card Eject status indicator (D)

Table 2-1 E5-APP-B LED Table

LED Name HW/SW Controlled Description
Server Status SW

Solid Red - Server is halted

Flashing Red - Server is booting

Solid Amber - TKLC configuration beginning

Solid Green - TPD loaded/operational state

Flashing Green - Server is shutting down

Drive 1 Status SW/HW

HW: Flashing Green - Drive activity

SW: Flashing Red - Impending drive removal

SW: Steady red - Drive ready for removal

Drive 2 Status SW/HW

HW: Flashing Green - Drive activity

SW: Flashing Red - Impending drive removal

SW: Steady red - Drive ready for removal

Eject Status SW

Red - Card ready for extraction

Flashing Red - Card preparing for extraction

Off - Card is not ready for extraction

Act LED A1 HW Flashing Green - Link Activity
Act LED A2 HW Flashing Green - Link Activity
Act LED B1 HW Flashing Green - Link Activity
Act LED B2 HW Flashing Green - Link Activity
Link LED A1 HW

Green - 10/100 Link Speed

Amber - 1000 Link Speed

Link LED A2 HW

Green - 10/100 Link Speed

Amber - 1000 Link Speed

Link LED B1 HW

Green - 10/100 Link Speed

Amber - 1000 Link Speed

Link LED B2 HW

Green - 10/100 Link Speed

Amber - 1000 Link Speed

2.3 Displaying Errors on EPAP GUI

If the EPAP application detects an application error or receives an alarm message from the platform layer, the EPAP application displays the error on the graphical user interface (GUI). See "EPAP GUI Main Screen" in Administration Guide for details on the EPAP GUI Banner.

Figure 2-2 shows the GUI banner components:

Figure 2-2 EPAP Banner Components


EPAP Banner Components

Tool tips are displayed for all EPAP banner components. Tool tips are activated when the mouse cursor (mouse-over event) is placed over the component. Each tip is unique to the banner component. The components of the EPAP Banner are displayed in Figure 2-2:

Viewing Alarm Details

The first three indicators (from left) are the alarm indicators on the EPAP GUI. These indicators displays the number of respective alarms on the EPAP. The left indicator indicates the Critical alarms; it turns red when a Critical alarm occurs. The middle indicator indicates the major alarms, and turns orange when a Major alarm is raised. The right indicator indicates the Minor alarm, and turns yellow when Minor alarm is raised. A maximum of 99 alarm counts can be displayed, considering the sum of all 3 alarm types. The indicator will remain brown if no alarm of that type is raised on the EPAP, as seen in Figure 2-3.

Figure 2-3 EPAP GUI With No Raised Alarms


EPAP GUI With No Raised Alarms

Clicking on any of the alarm indicators displays the details of each prevailing alarm on the EPAP, depending on which alarm indicator is clicked, in a new window. The new window with alarm details will remain persistent until either the GUI is terminated or the user logs out of the GUI. The user will have to close all opened alarm windows manually. The details of alarm include:

  1. Alarm severity and type (heading)
  2. Alarm name

The individual alarm text is found in Alarm Categories. To correct the alarm condition, perform the associated procedure described in EPAP Alarm Recovery Procedures.

IPv4 and IPv6 Addresses in the EPAP GUI Banner

When the EPAP is configured as an IPv6-only node, the configured IPv6 address is reflected in both the PDB area and the MPS area. See "EPAP GUI Banner Section" in Administration Guide for different banner examples.

2.4 Unsolicited Alarm and Information Messages

The EAGLE displays only one alarm per EPAP at a time based on the highest priority. If a single error is detected, the EPAP application sends an error message to the EAGLE terminal to report the active alarm category. If multiple errors are detected, the EPAP application sends an error message to the EAGLE terminal to report the most severe active alarm category.

If multiple alarms of the same severity exist and their severity is the highest alarm severity currently active, a combination alarm code is sent to the EAGLE. The EAGLE issues the appropriate UAM to the operator.

Errors detected in the hardware and software are reported by the following UAMs, which are described in greater detail in the EAGLE Unsolicited Alarm and Information Messages Guide.

  • Critical Platform Alarms are reported by the EAGLE in UAM 0370.
  • Critical Application Alarms are reported to the EAGLE in UAM 0371.

  • Major Platform Alarms are reported to the EAGLE in UAM 0372.

  • Major Application Alarms are reported to the EAGLE in UAM 0373.

  • Minor Platform Alarms are reported to the EAGLE in UAM 0374.

  • Minor Application Alarms are reported to the EAGLE in UAM 0375.

When all error conditions are corrected for all platform and application errors, the operator receives this UAM:


UAM 0250 MPS available.

For information about the alarm data contained in UAMs, see Alarms.