1. EAGLE EIR User's Guide
  2. Maintenance

5 Maintenance

This chapter describes commands and reports that can be used for EIR maintenance, including status reporting and problem identification.

5.1 EIR Alarms

Table 5-1 lists the UAMs that specifically support the EIR feature. All EIR-related UAMs are generated to the Maintenance Output Group.

Refer to Unsolicited Alarm and Information Messages Reference for complete descriptions and corrective procedures for all UAMs.

Refer to Alarms and Maintenance Guide for EPAP for the descriptions and corrective procedures for MPS-related alarms.

Table 5-1 EIR UAMs

UAM ID Severity Message Text

0455

Critical

EIR Subsystem is not available

0456

Critical

EIR Subsystem is disabled

0457

Minor

EIR Subsystem normal, card(s) abnormal

0458

None

EIR Subsystem is available

0459

None

EIR Subsystem is removed

0483

Critical

DEIR System is not available

0484

Major

DEIR System normal, card(s) abnormal

0485

Normal

DEIR System is available

0486

Minor

DEIR Threshold -Level1 exceeded

0487

Major

DEIR Threshold -Level2 exceeded

0488

Normal

DEIR Threshold Condition Cleared

0489

Critical

DEIR capacity exceeded

0490

Normal

DEIR normal

0491

Major

Connection TPS exceed

0492

Normal

Connection TPS normal

0493

Major

Diameter Connection Down

0494

Normal

Diameter Connection UP

0495

Normal

Diameter Connection Closed

0496

Normal

DEIR System is removed

5.2 EIR UIMs

Table 5-2 lists the UIMs that specifically support the EIR feature. Refer to Unsolicited Alarm and Information Messages Reference for complete descriptions of all UIM text, formats, and recovery procedures.

Table 5-2 EIR UIMs

UIM Text Description Recovery

1030

Inh EIR SS request already outstanding

An inh-map-ss command is already entered and queued.

None

1031

Failure Inhibiting EIR SS

The inh-map-ss command was unsuccessful in taking the EIR subsystem off-line.

Enter the inh-map-ss command with the force parameter.

1102

Invalid Length for Map IMEI Parameter

The EIR subsystem received a Check-IMEI message in which the Map IMEI parameter had an invalid length.

None

1103

LSS:No Map IMEI Parameter present

The EIR subsystem received a Check-IMEI message in which the Map IMEI parameter is not present

None

1306

GSMOPTS: EIR Global Response is ON

The EIR Global Response Type is on. The EIR Global Response Type is set by the chg-gsmopts command and the eirgrsp parameter.

For information about eirgrsp, refer to the chg-gsmopts command in Commands User's Guide

1307

GSMOPTS: EIR Global Response is OFF

The EIR Global Response Type is off. The EIR Global Response Type is set by the chg-gsmopts command and the eirgrsp parameter.

For information about eirgrsp, refer to the chg-gsmopts command in Commands User's Guide.

1133

Diameter msg decode failed

Diameter message parsing FAILS.

Examples:
  • ECR Message does not have IMEI AVP or value in IMEI AVP.
  • CER Message does not have mandatory AVP present.
  • DPR message received does not have disconnect cause AVP present.
Output Group: LINK
 

1134

Diameter msg encode failed

Diameter message Encoding FAILS. Output Group: LINK

  

1135

Invalid Diameter Msg received

Diameter message was received which is not supported in the EAGLE or an error exists in Diameter message header. Output Group: LINK

  

1136

Invalid Diameter Msg length

Total Diameter message length specified in diameter header does not match with the actual diameter message length. Output Group: LINK

  

1137

Diameter AVP Decode Fail

AVP decoding failed. Output Group: LINK

  

1138

Connection Refused
  • Origin host and Origin Realm AVPs in CER message does not match with the host and realm values provisioned in the IPAPSOCK table.
  • Source IP Address of the CER message does not match with the IP Address present in the Host-IP-Address AVP.
Error Cause:
  • Origin Host Mismatch
  • Origin Realm Mismatch
  • IP Address Mismatch
  • No common application
Output Group: LINK
 

1139

DEIR Global Response is ON

DEIR Global Response is set to Allowlist/Graylist/Blocklist/Unknown from OFF in DEIROPTS table. Output Group: APSS

  

1140

DEIR Global Response is OFF

DEIR Global Response is set to OFF from Allowlist/Graylist/Blocklist/Unknown in DEIROPTS table. Output Group: APSS

  

UIM Format for EIR S13/S13' Support Feature

The UIMs added for the EIR S13/S13' Interface Support feature are displayed in the format shown in Table 5-3. The maximum length of origin host/origin realm/AVP code and error to be displayed in the UIM is 32 bytes.

Table 5-3 UIM format for EIR S13/S13' Support Feature

UIM format for EIR S13/S13' Support Feature

Literal

RPT_DEIR_MSG (I-85)

Format

 
         1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    xxxx.xxxx    CARD cccc,ppp INFO     ’text’
                 DCNAME= xxxxxxxxxxxxxxx    
                 Command Code = xxxx
                 Error Cause=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

         1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    xxxx.xxxx    CARD cccc,ppp INFO     ’text’
                 DCNAME= xxxxxxxxxxxxxxx    
                 Command Code = xxxx
                 Origin Realm= xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
                 Error Cause=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx


         1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    xxxx.xxxx    CARD cccc,ppp INFO     ’text’
                 DCNAME= xxxxxxxxxxxxxxx    
                 Command Code = xxxx
                 Origin Host= xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
                 Error Cause=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Output Examples 

         1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    0014.1133    CARD 1103,B   INFO     Diameter msg decode failed 
                 DCNAME= Con1
                 Command Code = 324
                 Error Cause= Unsupported appl id

                 Report Date:10-10-12  Time:16:20:19

         1         2         3         4         5         6         7         8
12345678901234567890123456789012345678901234567890123456789012345678901234567890
    0014.1138    CARD 1103,B   INFO     Connection Refused 
                 DCNAME= Con3
                 Command Code = 324 (R) 
                 IP Address=10.248.4.5
                 Error Cause= IP Addr Mismatch

                 Report Date:03-22-13  Time:16:20:19

5.3 Maintenance Commands

The following commands can be used for maintenance when an EPAP-related feature is on.

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

Table 5-4 Maintenance Commands

Command Description
rept-stat-sys Reports the status of system entities, including cards. The output includes the number of Service Module cards that are in service (IS-NR) and how many are in another state (IS-ANR, OOS-MT, OOS-MT-DSBLD).
rept-stat-sccp Reports operating status of services and subsystems, CPU usage, and Service Module card status. When the loc parameter is specified, the command displays detailed card traffic statistics, including cards that are denied SCCP service. See the section in this manual that describes the use of the rept-stat-sccp command.
rept-stat-mps Displays the overall status of the EPAP application running on the MPS (multi-purpose server). Command output for the various reports of this command include overall MPS alarm status and card status, and status for a specific Service Module card when a feature is on.
rept-stat-trbl Includes a summary of any trouble notifications (UAMs) for local subsystems, cards, and linksets. The severity of each alarm is indicated in the output report.
rept-stat-alm Displays the alarm counts and totals for local subsystems and Service Module card/EPAP IP links.
rept-stat-db Displays the status information for the EAGLE databases. This includes the level information for each Service Module card, and for the active and standby EPAP RTDB. The command reports database exception status such as corrupted, incoherent, or inconsistent, as well as providing the birth dates and levels. It shows the status of each PDB and RTDB when an EPAP-related feature is enabled.
rtrv-tbl capacity Retrieves table use capacity summary information. For each table listed, the number of table entry elements in use and the total allowed number of table elements is presented, along with a percent (%) full value. Information is shown for some tables only if the feature that uses the table is enabled.
inh-card/alw-card

The inh-card command is used to change the operating state of the card from In-Service Normal (IS-NR) to Out-of-Service Maintenance-Disabled (OOS-MT-DSBLD). A craftsperson then can test the card or physically remove it from the shelf.

The alw-card command is used to change the card from OOS-MT-DSBLD (Out-of-Service Maintenance-Disabled) to IS-NR (In-Service Normal) if card loading is successful.

inh-alm/unhb-alm Used to allow and inhibit reporting of alarms for a given device, including the Service Module card ports. The commands allow both Port A and Port B to be specified. Inhibited alarms will not generate UAMs or cause alarm indicators to be turned on. All rept-stat-xxx commands continue to display the alarms with an indication that the device has its alarms inhibited.
rtrv-data-rtdb

Retrieves Entity data, DN data, IMEI data, IMSI data, TN data, NPANXX data, and LRN data from the RTDB on an active Service Module card.

If the loc parameter is specified and the target card is an active Service Module card, the RTDB data is retrieved from that card.

If the loc parameter is not specified, the RTDB data is retrieved on the active Service Module card that has the lowest IMT address.

The RTDB status on the active Service Module card can be coherent or incoherent.

5.3.1 rept-stat-sccp

The rept-stat-sccp command provides statistics for Service Module cards and for the services that execute on the cards. The statistics can be displayed for all Service Module cards, or for a specified card.

Refer to Commands User's Guide for a description of the rept-stat-sccp command, including parameter names, valid parameter values, examples, and dependencies for the command.

EIR Feature Statistics

The rept-stat-sccp command counts and displays the following statistics when the EIR feature is enabled and turned on (WARNINGS and FORWARD TO GTT are not reported for EIR):
  • TOTAL = the total number of messages that contain a CheckIMEI MAP Operation.
  • SUCCESS = the number of messages that passed CheckIMEI processing
  • ERRORS = the number of messages that were not counted in SUCCESS.

5.4 EAGLE Debug Commands

Commands User's Guide contains descriptions of debug commands that can be used in assessing and modifying system status and operation. Most of the debug commands are used only under the direction of Oracle support personnel.

Refer to Commands User's Guide for a complete description of the debug commands, including the ent-trace command.

The ent-trace command can be used for EIR to provide a trap-and-trace function for MSUs on the Service Module cards.
  • Trap Message will be performed on a Query message with:
    • A decode error, and Trace-On-Error set
    • IMEI match
    • IMSI match
    • SSP
    • GT
  • Because the Response message will not contain the IMEI or IMSI information, it will be trapped if the Query message was trapped.

Caution:

This command can cause OAM to reset if too many MSUs are trapped.

A trace must be set on all Service Module cards; specify the card=sccp-all parameter. Use a repetition parameter (rep) to control the number of MSUs that are trapped.

The 14-digit IMEI is a trapping field. MSUs are trapped only when the SDS count (REP) is positive. If a Query and Response are both trapped, that is 2 SDS counts.

MSUs that satisfy any trigger criteria are trapped on the Service Module card, forwarded to OAM, and displayed.

5.5 Status Reporting and Problem Identification

EAGLE commands can be used to obtain status and statistics for the EAGLE system, the EPAP systems, system devices including Service Module cards, EPAP-related features, local subsystems, and SCCP services.

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

Refer to Unsolicited Alarm and Information Messages Reference for descriptions and recovery procedures for UAMs and UIMs.

Refer to Administration Guide for EPAP for descriptions of EPAP functions and operation.

Refer to Alarms and Maintenance Guide for descriptions and recovery procedures for EPAP alarms.

Refer to the appropriate feature User's Guide for information about the functions and operation of EPAP-related features.

Table 5-5 Status Reporting for EPAP-Related Features

Reports, Status, and Statistics Command

EAGLE

Maintenance Status Report - indicates whether Maintenance, Routing, and SCCP Baselines have been established.

rept-stat-sys

Alarms and operating state for system devices, including Service Module ( "SCCP") cards.

rept-stat-sys
Unsolicited Alarm Messages (UAMs) and Unsolicited Information Messages (UIMs)

rept-stat-alm

rept-stat-trbl

EPAP/MPS (from the EAGLE)

EPAP code version and operating state for each EPAP.

rept-stat-mps

MPS hexadecimal alarm strings for the active and standby EPAPs.

rept-stat-mps

Operating state and alarm status of equipped Service Module cards and their DSM ports and IP connections.

rept-stat-mps

rept-stat-mps:loc=<Service Module card location>

Amount of memory used by the RTDB on the specified card, as a percent of available Service Module card memory.

rept-stat-mps:loc=<Service Module card location>
EPAP Provisioning Database (PDB), EPAP Real Time Database (RTDB), and Service Module card RTDB status information - Coherent, birthdate (date and time of creation), and exception (condition when a problem was detected).

rept-stat-db

rept-stat-db:db=mps

Service Module Cards, EPAP-Related Features, Services, Local Subsystems

Status of the Service Module cards, and the services executing on the cards for EPAP-related features that are turned on. Includes Service Report, Subsystem Report, and Alarm Status; Total Service Statistics.

rept-stat-sccp

Operating state and alarm status of equipped Service Module cards and their DSM ports and IP connections; EPAP-related feature status per card.

rept-stat-mps:loc=<Service Module card location>

Alarms and operating state for Service Module ( "SCCP") cards.

rept-stat-sys

rept-stat-mps

Any cards that are denied SCCP service.

rept-stat-sccp

Detailed view of the status of SCCP services provided by the specified Service Module card. Includes Card Alarm Status, Card Service Statistics

rept-stat-sccp:loc=<Service Module card location>

General SCCP traffic performance for Service Module cards. Message rates for TVG performance.

rept-stat-sccp:mode=perf

Statistics for EPAP-related feature local subsystems - Subsystem Report

rept-stat-sccp

Statistics for EPAP-related features

rept-stat-sccp

5.5.1 EPAP Status and Alarm Reporting

Because EPAP has no direct means of accepting user input or displaying output messages on EAGLE terminals, EPAP maintenance, measurements, and status information are routed through a Service Module card. EPAP sends two types of messages to the Service Module card: EPAP Maintenance Blocks and DSM Status Requests and DSM Status Messages. Each message type is discussed in the following sections.

EPAP Maintenance Blocks

The EPAP forwards all status and error messages to the Service Module cards in maintenance blocks. Maintenance blocks are asynchronously sent whenever the EPAP has something to report. The status information that is displayed when a rept-stat-mps command is issued includes information that came from the maintenance blocks.

The active EPAP generates and sends maintenance blocks to the primary Service Module card. One maintenance block is sent as soon as the IP link is established between the active EPAP and the primary Service Module card. Additional maintenance blocks are sent whenever the EPAP needs to report any change in status or error conditions. The information returned in maintenance blocks is included in the output of the rept-stat-mps and rept-stat-sccp commands.

The EPAP sends maintenance blocks that contain at least the following information:

  • Status of EPAP A - actual states are active, standby, and down (inoperative). Maintenance blocks include a field for this information so that it can be available for the output of the rept-stat-mps command.

  • Status of EPAP B - actual states are active, standby, and down (inoperative). Maintenance blocks include a field for this information so that it can be available for the output of the rept-stat-mps command.

  • Identification of Active EPAP - a field to identify the active EPAP.

  • Congestion Indicator - an indicator showing provisioning link congestion. The link between the EPAPs and the external source of provisioning data can become congested in high-provisioning traffic situations. When this occurs and subsequently as the congestion clears, the EPAP sends maintenance blocks to the Service Module card.

  • Alarm Conditions - an error code field. If the EPAP needs to report an alarm condition, it puts an appropriate UAM identifier in this field.

  • Current MPS Database Size - a field indicating the current RTDB size. The Service Module card uses this information to calculate the percentage of memory used by the RTDB.

DSM Status Requests and DSM Status Messages

When the EPAP needs to know the status of a Service Module card, the EPAP sends a DSM Status Request to all Service Module cards, and each Service Module card returns its status to the EPAP.

Service Module cards send a DSM Status Message to the EPAP when any the following events occur in the Service Module card:

  • The Service Module card is booted.

  • The Service Module card receives a DSM Status Request message from the EPAP.

  • 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 user requests that the RTDB be reloaded. The Service Module card sends a Full Download Request message to the EPAP

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

The DSM Status Message provides the following information to the EPAP:

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

  • Load Mode Status. This indicator indicates whether or not a sufficient number of the IS-NR (In-Service Normal) LIMs have access to SCCP services.