1. EAGLE LNP Application Processor Administration and LNP Feature Activation Guide
  2. EAGLE Status Reporting and Alarms for ELAP and LNP

10 EAGLE Status Reporting and Alarms for ELAP and LNP

This chapter describes the ELAP alarm reporting process, EAGLE commands for maintenance functions and status reporting, and EAGLE Unsolicited Alarms and Information Messages.

10.1 EAGLE Status and Alarm Reporting

The MPS systems and ELAPs have no direct means of displaying output messages on EAGLE terminals. Maintenance, measurements, status, and alarm information must be routed from the Active ELAP to an arbitrarily selected Service Module card, known as the primary Service Module card.

All the alarms are reported in a common message format. The Active ELAP generates and sends Maintenance Blocks to the primary Service Module card. One Maintenance Block is sent when the IP link is established between the Active ELAP and the primary Service Module card. Additional Maintenance Blocks are sent whenever the ELAP needs to report any change in status or error conditions. The information returned in Maintenance Blocks is included in the status reports produced by the EAGLE rept-stat-mps command (see EAGLE Maintenance Commands).

The ELAP sends Maintenance Blocks that contain (at a minimum) the following information:

  • MPS major, minor, and dot software versions

  • MPS Status (down/up)

  • MPS Status (Active/Standby)

If the ELAP needs to report one or more alarm conditions, it inserts the appropriate alarm data string for the indicated alarm category into the Maintenance Block.

Table 10-1 defines the application and platform alarms that are forwarded to the EAGLE. The EAGLE receives the alarm number, alarm text, and alarm data string recovered from the MPS/ELAP.

Table 10-1 EAGLE MPS Application and Platforms UAM Alarms

Alarm Number Level Device Error Description

370

Critical

MPS A or B

Critical Platform Failure

371

Critical

MPS A or B

Critical Application Failure

372

Major

MPS A or B

Major Platform Failure

373

Major

MPS A or B

Major Application Failure

374

Minor

MPS A or B

Minor Platform Failure

375

Minor

MPS A or B

Minor Application Failure

250

Clearing

MPS A or B

MPS Available

10.1.1 Maintenance Blocks

MPS and ELAP have no direct means of accepting user input from or displaying output messages on EAGLE terminals. Maintenance, measurements, error, and status information are routed to the EAGLE through the primary Service Module card.

The Active ELAP generates and sends Maintenance Blocks to an arbitrarily selected Service Module card known as the primary Service Module card. One Maintenance Block is sent as soon as the IP link is established between the Active ELAP and the primary Service Module card. Additional Maintenance Blocks are sent whenever the ELAP needs to report any change in status or error conditions. The information returned in Maintenance Blocks is also included in the output of the EAGLE rept-stat-mps command.

It is possible for the ELAP to be at a provisioning congestion threshold, and to be entering and exiting congested mode at a very high rate of speed. To minimize this thrashing effect, the ELAP is restricted to sending no more than one ELAP Maintenance Block per second.

ELAP Maintenance Block Contents

The ELAP sends Maintenance Blocks that contain (at a minimum) the following information. The actual states are defined in the description of the rept-stat-mps command in Commands User's Guide.

  • MPS major, minor, and dot software versions
  • MPS Status (down/up)
  • MPS Status (Active/Standby)

If the ELAP needs to report one or more alarm conditions, it inserts the appropriate alarm data string for the indicated alarm category into the Maintenance Block.

EAGLE Alarm Reporting of ELAP Alarms

A 16-character hexadecimal alarm data string reports any errors found during the last System Health Check and the level of severity for each error. The first character (four bits) uniquely identifies the alarm severity for the alarm data. The remaining 15 characters (60 bits) uniquely identify up to 60 individual failure cases for the alarm category.

The System Health Check (syscheck) is responsible for forwarding platform errors to the application. The application combines the platform alarms with the application alarms and forwards all of this information to EAGLE. The information that is transferred is described in Alarms and Maintenance Guide for ELAP. MPS Platform and ELAP Application Alarms describes the application and platform alarms that are forwarded to the EAGLE. The EAGLE eceives the alarm number, alarm text, and alarm data string recovered from the MPS/ELAP.

10.1.2 Alarm Priorities

The ELAP sends the maintenance information, including the alarm data strings, to the EAGLE for interpretation. Alarm priorities determine which alarm category is displayed at the EAGLE terminal when multiple alarm levels exist simultaneously. EAGLE prioritizes the data and displays only the alarm category with the highest severity level and priority for each MPS.

If an alarm category of lower priority is sent from the MPS, the lower priority alarm category is not displayed on the EAGLE terminal until any higher priority alarms are cleared.

10.1.3 Multiple Alarm Conditions

Critical, major and minor alarms appear repeatedly in each alarm delivery to the EAGLE until the alarm condition clears.

If multiple alarms exist, the highest priority alarm category is the Active Alarm. The Active Alarm is shown in the output from the rept-stat-trbl command and the rept-stat-mps command, and the alarm count associated with this alarm is included in the rept-stat-alm command output.

Though only the highest priority alarm is displayed at the EAGLE terminal when multiple alarms are reported, you can use the EAGLE rept-stat-mps command to list the alarm data strings for all of the alarm categories with existing alarms. Then you can use the ELAP user interface Maintenance menu item Decode EAGLE Output of MPS Alarms to convert the hexadecimal alarm data string to text. The output text shows the alarm category represented by the string and the alarm text for each alarm encoded in the string.

10.1.4 Service Module Card Status Requests and Status Messages

When the ELAP needs to know the status of a Service Module card, it can send a Service Module Card Status Request to all Service Module cards. Because status messages are sent over UDP, the ELAP broadcasts the Service Module Card Status Request and each Service Module cards returns its status to the ELAP.

Service Module cards send a Service Module Card Status Message to the ELAP when any of the following events occur in the Service Module card:

  • The Service Module card is booted.

  • The Service Module card receives a Service Module Card Status Request message from the ELAP

  • The Service Module card determines that it needs to download the entire RTDB; for example, the Service Module card determines that the RTDB needs to be downloaded because it is totally corrupted, or a craftsperson requests that the RTDB be reloaded.

  • The Service Module card starts receiving RTDB downloads or updates. When a Service Module card starts downloading the RTDB, or if the Service Module card starts accepting database updates, it sends a Service Module Card Status Message informing the ELAP of the first record received. This helps the ELAP keep track of downloads in progress.

The Service Module Card Status Message provides the following information to the ELAP:

  • Service Module card Memory Size - When the Service Module card is initialized, it determines the amount of applique memory present. The ELAP uses this value to determine if the Service Module card has enough memory to hold the RTDB.

  • Database Level Number - The ELAP maintains a level number for the RTDB. Each time the database is updated, the level number will be incremented. When the database is sent to the Service Module card, the Service Module card keeps track of the database level number. The database level number is included in all Status messages sent from the Service Module card. A level number of 0 signifies that no database has been loaded into the Service Module card (this can be done any time the Service Module card wants to request a full database download).

  • Database Download Starting Record Number - When the Service Module card starts downloading either the entire RTDB or updates to the database, it will identify the starting record number. This allows the ELAP to know when to wrap around the end of the file, and when the Service Module card has finished receiving the file or updates.

10.2 EAGLE Maintenance Commands

The EAGLE commands described in this section can be used for maintenance functions for LNP, including reporting status and alarm information.

Refer to Commands User's Guide for complete command descriptions, parameters and valid values, rules for using the commands correctly, and output examples.

rept-stat-lnp

The rept-stat-lnp command reports LNP status information.

When the rept-stat-lnp command is entered with no parameters, a summary of the LNP status of all equipped Service Module cards is provided. The summary includes Global Title Translation (GTT) and LNP function status for every Service Module card, as well as LNP Query Service system information.

When the loc parameter is specified, a detailed status of LNP information for the specified Service Module card is provided. The detailed reports include information for each of the following functions: Global Title Translation (GTT), LNP Message Relay (LNPMR), LNP Query Service (LNPQS), Personal Communication Service LNP Query Service (PLNPQS) (if the PLNP feature is turned on), Wireless LNP Query Service (WNPQS) (if the WNP feature is turned on), Triggerless LNP (TLNP) (if the TLNP feature is turned on), LRNQT (if the ITU TCAP LRN Query feature is turned on), and Automatic Call Gap (ACG).

When the card=sccp all parameter is specified, a detailed status of LNP information for all Service Module cards is provided.

rept-stat-db

The rept-stat-db command report includes the RTDB birthdate, level, and status. This information is used to help determine the need for and method to use for an RTDB resynchronization, audit and reconcile, reload from another RTDB, or bulk load from LSMS.

rept-stat-mps

The rept-stat-mps command reports the status of the provisioning system, including MPS platform status and ELAP status.

The rept-stat-mps command produces a summary report showing the overall status of the provisioning system and a moderate level of information for each Service Module card.

The rept-stat-mps:loc=xxxx command produces a more detailed report showing the status of a specific Service Module card.

When the ELAP sends database updates to the Service Module cards, the update messages include a field that contains the new database memory requirements. This version of the rept-stat-mps command displays the amount of memory used by the RTDB as a percent of available Service Module card memory.

Each Service Module card monitors the database size requirements and issues a minor alarm if the size of the database exceeds the configured percentage allowed. See Modify System Defaults for more information on configured percentages. If a database increases to the point that it occupies 100% of the Service Module card memory, it issues a major alarm.

rept-stat-trbl

The rept-stat-trbl command output includes the Service Module card and ELAP IP link alarms.

rept-stat-alm

The rept-stat-alm command output includes the alarm totals for the Service Module card and ELAP IP links.

10.3 Unsolicited Alarm Messages and Unsolicited Information Messages

The following sections describe MPS and ELAP Unsolicited Alarm Messages (UAMs) and Unsolicited Information Messages (UIMs).

The EAGLE outputs two types of unsolicited messages:

  • Unsolicited Alarm Messages (UAMs) - Denotes persistent problems with a device or object that needs the attention of a craftsperson.

  • Unsolicited Informational Messages (UIMs) - Indicates transient events that have occurred.

Unsolicited Alarm Messages are generated by the maintenance system as trouble notification for the OS. The maintenance system is able to determine the status of the system through polling and periodic audits. Troubles are detected through analysis of system status and notifications from various subsystems in the EAGLE. The EAGLE controls and generates the alarm number, associated text, and formatting for alarms sent to EAGLE through the Maintenance Block mechanism for the ELAP.

Unsolicited Alarm and Information Messages describes all EAGLE UAMs and the appropriate recovery actions.

MPS Platform and ELAP Application Alarms

MPS platform and ELAP application alarms are reported in the following six categories of alarms:

  • Critical Platform Alarm—This is a 16-character hexadecimal string in which each bit represents a unique critical platform failure and alarm. An alarm in this category results in the associated MPS state being set to OOS-MT// Fault.

  • Major Platform Alarm—This is a 16-character hexadecimal string in which each bit represents a unique major platform failure and alarm. An alarm in this category results in the associated MPS state being set to OOS-MT// Fault.

  • Minor Platform Alarm—This is a 16-character hexadecimal string in which each bit represents a unique minor platform failure and alarm. An alarm in this category results in the associated MPS state being set to IS-ANR// Restricted.

  • Critical Application Alarm—This is a 16-character hexadecimal string in which each bit represents a unique critical application failure/alarm. An alarm in this category results in the associated MPS state being set to OOS-MT//Fault.

  • Major Application Alarm—This is a 16-character hexadecimal string in which each bit represents a unique major application failure/alarm. An alarm in this category results in the associated MPS state being set to OOS-MT// Fault.

  • Minor Application Alarm—This is a 16-character hexadecimal string in which each bit represents a unique minor application failure and alarm. An alarm in this category results in the associated MPS state being set to IS-ANR/Restricted.

The alarm categories, shown in Table 10-2, are forwarded to the EAGLE when MPS and ELAP failures or errors are detected. Each alarm category is sent with a hexadecimal alarm data string that encodes all alarms detected in that category (see EAGLE Status and Alarm Reporting). The clearing alarm for all of the MPS Platform and Application alarms is UAM 0250, MPS Available.

Note:

The recovery actions for the platform and application alarms are defined in Alarms and Maintenance for ELAP.

Table 10-2 MPS Platform and ELAP Alarm Category UAMs

UAM # Severity Message Text

370

Critical

Critical Platform Failure(s)

371

Critical

Critical Application Failure(s)

372

Major

Major Platform Failure(s)

373

Major

Major Application Failure(s)

374

Minor

Minor Platform Failure(s)

375

Minor

Minor Application Failure(s)

Table 10-3 MPS Available UAM

UAM # Severity Message Text
250 None MPS available

Figure 10-1 Alarm Output Example


Alarm Output Example

Figure 10-2 MPS Available Alarm


MPS Available Alarm

The clearing alarm is generated after existing alarms have been cleared. The clearing alarm sets the MPS primary status to IS-NR.

10.3.1 ELAP-to-Service Module Card Connection Status

The ELAP and the Service Module card are connected over one 100BASE-T Ethernet network that runs at 100 Mbps and one 10BASE-T Ethernet network that runs at 10 Mbps, and use TCP/IP. In the event connection is inoperative, the Service Module card is responsible for generating an appropriate UAM. Loss of connectivity or inability of the ELAP to communicate (from hardware or software failure, for example) is detected and reported within 30 seconds.

ELAP-Service Module Card UAMs

Maintenance Blocks sent from the ELAP have a field to identify error message requests. (See “Maintenance Blocks”). The Service Module card processes incoming Maintenance Blocks and generates the requested UAM. The Service Module card acts only as a delivery agent. The recovery actions for the ELAP-Service Module card UAMs are defined in "UAM/UIM Troubleshooting" chapter in Unsolicited Alarm and Information Messages Reference.

Service Module Card-ELAP Link Status Alarms

Two alarms indicate the Service Module card-to-MPS link status:

  • 0084 “IP Connection Unavailable” (Major)

  • 0085 “IP Connection Available” (Normal/Clearing)

    Example: 

    
         1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    station1234 00-09-30 16:28:08 EST EAGLE 35.0.0-35.10.0
**  3582.0084 ** DSM B   1217          IP Connection Unavailable

RTDB Audit Alarms

During an audit of the Service Module cards and the ELAPs, the status of each Real-Time Database (RTDB) is examined and the following alarms can be raised. The recovery actions for the RTDB Audit Alarms are defined in the "UAM/UIM Troubleshooting" chapter in Unsolicited Alarm and Information Messages Reference.

Table 10-4 RTDB Audit Alarms

UAM # Alarm Level Trigger Message Text
443 Major An RTDB has become corrupted. RTDB database corrupted
444 Minor A card's RTDB is inconsistent (its contents are not identical to the current RTDB on the Active ELAP fixed disks RTDB database is inconsistent
445 N/A An inconsistent, incoherent, or corrupted RTDB has been fixed and the card or ELAP is an IS-NR condition. RTDB database has been corrected
448 Minor The RTDB is being downloaded or an update has failed. Therefore, the RTDB is in an incoherent state. RTDB database incoherent
449 Major A Service Module card detects that its RTDB needs to be resynchronized and has started the resyn operation. RTDB resynchronization in progress
450 Informational A Service Module card completes its RTDB resync operation. RTDB resynchroniation complete
451 Major A Service Module card detects that its RTDB needs to be reloaded because the resync log does not contain all of the required updates. RTDB reload required

10.3.2 Feature Quantity Capacity UAMs

The following alarms are issued when the Service Module card detects the capacity has been exceeded. The recovery actions for the Feature Quantity Capacity Alarms are defined in the "UAM/UIM Troubleshooting" chapter in Unsolicited Alarm and Information Messages Reference.

Table 10-5 Feature Quantity Capacity Alarms

UAM # Alarm Level Trigger Message Text
283 Major The NPANXXX totals on the Service Module cards have reached 90% of the total NPANXX capacity that is currently configured for the EAGLE. LNP Ported LRNs approaching Feat. Capacity
284 N/A A previous fault with the number of LNP ported NPAs is greater than the capacity this feature supports has been corrected. LNP Ported NPAs exceeds feat. Capacity
285 Major The LRN totals on the Service Module cards has reached 90% of the total LRN capacity that is currently configured for the EAGLE. LNP Ported NPAs approaching Feat. Capacity
286 N/A A previous fault with the number of LNP ported LRNs is greater than the capacity this feature supports has been corrected. LNP Ported NPAs Capacity Normal
287 Critical The total TNs in the LNP database has reached the configurable percentage (default value is 95%) of the allowed capacity currently configured for the EAGLE. RTDB Table Level 2 FAK Cap Exceeded
288 Major The total TNs in the LNP database has reached the configurable percentage (default value is 80%) of the allowed capacity currently configured for the EAGLE. The configured threshold value for UAM 0288 must be less than the configured threshold value for UAM 0287. RTDB Table Level 2 FAK Cap Exceeded
289 N/A A previous LNP FAK alarm condition no longer exists. RTDB Table FAK Capacity Normal

10.3.3 Physical Memory Usage UAMs

The following alarms are issued when the Service Module card detects the RTDB memory capacity is not adequate for the ELAP feature. The recovery actions for the Physical Memory Usage Alarms are defined in "UAM/UIM Troubleshooting" chapter in the Unsolicited Alarm and Information Messages Reference .

Table 10-6 Physical Memory Usage Alarms

UAM # Alarm Level Trigger Message Text
442 Critical The RTDB physical memory usage threshold exceeds 95% for the specified number of TNs, LRNs, or NPAs. RTDB database capacity is 90% full
446 Minor The RTDB physical memory usage threshold exceeds 80% for the specified number of TNs, LRNs, or NPAs. RTDB database capacity is 80% full
447 N/A A previous RTDB physical memory usage alarm condition no longer exists. RTDB database capacity alarm cleared

10.3.4 EAGLE Service Module Card Audit UIMs

The Service Module card performs data validation checks prior to applying updates and changes to the RTDB. This consist of comparing the checksum in the data about to be overwritten with the old checksum (new data element) in the update about to be applied.

A UIM is created when validation failure occurs because the target-cell checksums do not match the source-cell checksums. The updates are not applied and the database is marked incoherent.

10.3.5 Measurement Capacity UIMs

When the Measurements Platform is not installed, the OAM-based Measurements Subsystem will collect up to 100,000 LRNs and 150,000 NPANXXs from the SCCP cards. If the number of provisioned LRNs exceeds 100,000 or the number of provisioned NPANXXs exceeds 150,000, the Measurements Subsystem will generate a UIM at each hourly collection interval. The UIM is a warning that measurements data have been discarded. The UIM output may be suppressed by setting the UIM threshold limit to zero. More information on the Measurement Capacity UIMs are defined in "UAM/UIM Troubleshooting" chapter in Unsolicited Alarm and Information Messages Reference .

Table 10-7 Measurement Capacity UIMs

UIM # Alarm Level Trigger Message Text
1310 N/A The Measurements Platform is not enabled and the number of provisioned LRNs exceeds 100,000. This UIM is notification that the LNPLRN measurements report will be truncated, and additional LRN measurements will not be collected or reported. System Meas. Limit exceeded for LRN
1311 N/A The Measurements Platform is not enabled and the number of provisioned NPANXXs exceeds 150,000. This UIM is notification that the LNPNPANXXs measurements report will be truncated, and additional NPANXX measurements will not be collected or reported. System Meas. Limit exceeded for NPANXX