6 Maintenance

This chapter describes the maintenance information available from the EAGLE for the IS41 GSM Migration (IGM) feature. The information includes status, alarms (UAMs), and information messages (UIMs).

IGM Related Alarms

All IGM related Unsolicited Alarm Messages (UAMs) are output to the Maintenance Output Group. Unsolicited Alarm and Information Messages Reference contains a complete description of all UAMs. Table 6-1 contains a listing of UAMs used to support the IGM feature.

Refer to Unsolicited Alarm and Information Messages Reference for descriptions and corrective procedures for EAGLE-related alarms. Refer to Alarms and Maintenance Guide for EPAP for the descriptions and corrective procedures associated with MPS-related alarms.

Table 6-1 IGM Related UAMs

UAM Severity Message Text MPS or EAGLE

0013

Major

Card is isolated from system

EAGLE

0084

Major

IP Connection Unavailable

EAGLE

0085

None

IP Connection Available

EAGLE

0099

Major

Incompatible HW for provisioned slot

EAGLE

0250

None

MPS available

MPS

0261

Critical

MPS unavailable

MPS

0328

None

SCCP is available

EAGLE

0329

None

SCCP capacity normal, card(s) abnormal

EAGLE

0330

Major

SCCP TPS Threshold exceeded

EAGLE

0331

Critical

SCCP is not available

EAGLE

0335

None

SCCP is removed

EAGLE

0336

Major

LIMs have been denied SCCP service

EAGLE

0370

Critical

Critical Platform Failures

MPS

0371

Critical

Critical Application Failures

MPS

0372

Major

Major Platform Failures

MPS

0373

Major

Major Application Failures

MPS

0374

Minor

Minor Platform Failures

MPS

0375

Minor

Minor Application Failures

MPS

0422

Major

Insufficient extended memory

EAGLE

0423

None

Card reload attempted

EAGLE

0441

Major

Incorrect MBD - CPU

EAGLE

0442

Critical

RTDB database capacity is 95% full

EAGLE

0443

Major

RTDB database is corrupted

EAGLE

0444

Minor

RTDB database is inconsistent

EAGLE

0445

None

RTDB database has been corrected

EAGLE

0446

Major

RTDB database capacity is 80% full

EAGLE

0447

None

RTDB database capacity alarm cleared

EAGLE

0448

Minor

RTDB database is incoherent

EAGLE

0449

Major

RTDB resynchronization in progress

EAGLE

0451

Major

RTDB reload is required

EAGLE

0526

None

Service is available

EAGLE

0527

Minor

Service abnormal

EAGLE

0528

Critical

Service is not available

EAGLE

0529

Critical

Service is disabled

EAGLE

0530

None

Service is removed

EAGLE

IGM UIMs

Unsolicited Alarm and Information Messages Reference contains a complete description of all Unsolicited Information Message (UIM) text and formats. Table 6-2 lists UIMs used to support the IGM feature.

Table 6-2 IGM Related UIMs

UIM Text Description Action Output Group (UI Output Direction)

1035

SCCP rsp did not route - invalid GTI

The SCCP response did not route due to an invalid GTI

Use a valid GTI in the CGPA part of the query

gtt

1036

SCCP rsp did not route - invalid TT

The SCCP response did not route due to an invalid TT

Provision the CGPA TT in the GTT TT table

gtt

1037

SCCP rsp did not route - bad Xlation

The SCCP response did not route due to a bad translation

Provision the CGPA GTA address in the GTT database

gtt

1038

SCCP rsp did not route - SSP not True PC

The SCCP response did not route due to SSP is not true point code

Use the true point code in the CGPA point code or OPC of the query

gtt

1039

SCCP rsp did not route - bad Selectors

The SCCP response did not route due to invalid selectors

Provision the CGPA GTI, TT, NP, and NAI in the EGTT selector table

gtt

1130

IS412GSM not provisioned

The IS-41 to GSM Migration prefix specified by the IS412GSM parameter is not provisioned on this system.

The IS412GSM prefix must be specified in the GSMOPTS table.

gtt

1131

Invalid digits in IS41 MAP Digits parms

The EAGLE encountered an error in decoding the digits parameter in the LocationRequest message.

Correct the digits parameter

gtt

1169

SCCP rcvd inv TCAP portion

This indicates that SCCP discarded a message because the TCAP provided in the called party address is invalid in the EAGLE.

No action is necessary.

application subsystem

1227

SCCP did not route - DPC not in MAP tbl

This message indicates that SCCP did not route a message because the destination point code was not in the mated application (MAP) table. The message was discarded.

If the DPC indicated in the message should not be routed to, no further action is necessary.

gtt

1230

SCCP did not route - SS not in MAP tbl

This message indicates that SCCP did not route a message because the destination subsystem was not in the Mated Application (MAP) table. The message was discarded.

No action is necessary.

gtt

1242

Conv to intl num

- Dflt CC not found

Conversion to international number failed because default CC was not found

Define the default CC with chg-stpopts :defcc=xxx

application subsystem

1243

Conv to intl num

- Dflt NC not found

Conversion to international number failed because default NC was not found

Define the default NDC with chg-stpopts :defndc=xxxxx

application subsystem

1246

Invalid length of conditioned digits

Invalid length of condition- ed digits (length of conditioned international number is less than 5 or greater than 15)

Use an international number with length in the acceptable range

application subsystem

1256

MNP Circular Route Detected

This message indicates the network has incorrect number portability data for a subscriber.

Verify and update number portability data.

application subsystem

1294

Invalid digits in MAP MSISDN

parameter

No digits found in MAP MSISDN

parameter

Specify valid digits in the MSISDN

application subsystem

1295

Translation PC is EAGLE’s

PC translation is invalid because it is one of EAGLE PCs

Change the point code

application subsystem

1297

Invalid length of prefix/suffix digits

Attempted digit action of prefixing entity ID is invalid because combined length of entity ID and GT digits was greater than 21 digits

Change the attempted digit action or decrease the length of the entity ID and/or GT digits

application subsystem

1341

SRI rcvd - GSM2IS41 not provisioned

MIGRPFX=SINGLE and GSM2IS41 prefix is NONE. The GSM to IS-41 Migration prefix is not provisioned on this system.

The GSM2IS41 prefix must be specified in the GSMOPTS table.

gtt

1432

IGM Relay Failed - Bad IS41 SMSC Xlation

GTT translation lookup on DEFIS41SMSC digits failed. Message falls through to SCCP CDPA GTT.

The DEFIS41SMSC digits must be provisioned.

gtt

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 6-3 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.

rept-stat-sccp

The rept-stat-sccp command displays the status of the Service Module cards and the statistics of the services running on the Service Module cards. The command also displays any cards that are denied SCCP service. An MSU is considered to be an A-Port MSU after service selection. Statistics are displayed under MNP Service Statistics for A-Port, G-Port, and IGM features. Statistics are displayed under SMSMR Service Statistics for MO SMS IS41-to-GSM Migration, MO-Based GSM SMS NP, MO-Based IS41SMS NP, and PPSMS features.

EAGLE Debug Commands

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

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 6-4 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

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.