1. EAGLE INP/AINPQ User's Guide
  2. INP/AINPQ Maintenance

6 INP/AINPQ Maintenance

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

INP/AINPQ Subsystem-Related Alarms

Refer to Unsolicited Alarm and Information Messages Reference for a complete description and the associated corrective procedure for each INP/AINPQ-related UAM, and for information about other EAGLE alarms.

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

Table 6-1 INP/AINPQ Subsystem-Related UAMs

UAM Severity Message Text

0394

None

Local Subsystem is available

0395

Critical

Local Subsystem is not available

0396

Critical

Local Subsystem is disabled

0397

None

Local Subsystem is removed

0398

Minor

Local Subsystem normal, card(s) abnormal

INP/AINPQ Subsystem-Related UIMs

The Unsolicited Information Messages (UIMs) listed in Table 6-2 support the INP/AINPQ subsystem. The INP/AINPQ UIMs are generated to the Application Subsystem (APSS) Output Group.

Refer to Unsolicited Alarm and Information Messages Reference for a complete description of all UIM text and formats.

Table 6-2 INP/AINPQ Subsystem UIMs

UIM Text Description Action
1174 Inh INP SS request alrdy outstanding A second attempt to inhibit the INP subsystem has been made while the first attempt is still being processed. No action is necessary. The second attempt will be ignored.
1175 Failure Inhibiting INP SS The inh-map-ss command did not take the local subsystem off-line. Enter the inh-map-ss command with the force parameter.

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

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

1246

Invalid length of conditioned digits

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

Use an international number with length in the acceptable range

1295

Translation PC is EAGLE

PC translation is invalid because it is one of the point codes of the EAGLE

Change the point code

1296

Translation PC type is ANSI

PC translation is invalid because it is an ANSI point code

Change the point code

1297

Invalid length of prefix/suffix

digits

Attempted digit action of prefixing or suffixing the entity ID is invalid because the combined length of entity ID and GT digits is greater than 21 digits.

Change the attempted digit action or decrease the length of the entity ID and/or GT digits
1382 Too many digits for DRA parameter Outgoing formatted digits exceeds the maximum allowed limit (32 for ITU TCAP Connect response and 21 for routing digits in ANSI-41 Return result). Decrease the number of RN digits or modify the querying node to send fewer digits in DN.

Two UIMs for One MSU

An MSU that is invalid for INP Message Relay (INPMR), which consequently falls through to GTT, might result in two UIMs being issued. For example, the first UIM results from INP Message Relay due to a number conditioning error. The second results from the GTT, due to a routing failure or a translation not provisioned for the GTAI.

In these cases, one UIM may not be generated because of frequency limiting. For example, the frequencies for an INPMR UIM and a PC Unavailable UIM are one message every 200 milliseconds. In the case of two problems with one MSU, the UIMs occur within microseconds of each other, so that one of the UIMs is not generated. It is the timing of UIMs with regard to any UIMs for other MSUs that determines which, if either, is generated. In the example, assuming no UIMs occurred in the previous 200 ms for any other MSUs, the INPMR UIM is generated first.

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 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 the command descriptions in Commands User's Guide for a complete descriptions of the rept-stat-sccp command, including parameter names, valid parameter values, examples, and dependencies.

If multiple error conditions are found during MSU processing, rept-stat-sccp will display the counter for the most severe condition. The order will be ERRORS, WARNINGS, SUCCESS.

Table 6-4 describes the incrementing of the rept-stat-sccp statistics counters for the INP and AINPQ features and services.

Table 6-4 rept-stat-sccp Statistics for INP and AINPQ

Statistic Service or Function Reason to Increment Count
SUCCESS INPQS

INP CRP on: Calls has a circular route detected and results in successful encoding of an INAP RELEASECALL message.
Outgoing Message Encoding Errors

Service Portability: GRN data required for own-network subscriber and GRN not provisioned in entity data.
ERRORS INP Query Verification - SCCP Decoding

Not an ITU-N message type.

Not an SCCP UDT or non--segmented XUDT message

TCAP Type is not ANSI-41 or INAP.

TCAP Type is ANSI-41 and AINPQ feature is not enabled.

TCAP Type is INAP, and INPQ service is not provisioned.
INP Query Verification - INAP TCAP Decoding

Message type is not supported, invalid, or unknown.

TCAP components are missing or invalid.
INP Query Verification - ANSI-41 TCAP Decoding

Message type is not supported, invalid, or unknown.

TCAP components are missing or invalid.
INAP Query Processing

Op code is not INITALDP or NPREQ.

Service Key is missing.

Parameters out of sequence.

Called Party Number errors.

SNAI is Subscriber and Default NDC is not provisioned.

SNAI is not International and the Default Country Code is not provisioned.

Conditioned number is too short or too long.
INP-specific Decode Errors

Segmented XUDT.

MSU is not UDT, UDTS, XUDT, or XUDTS.

MSU is UDT or XUDT, is not MTP-routed, and SCCP message class is not 0 or 1.

MSU is UDTS or XUDTS and CdPA is Rt-on-GT.

MSU is UDTS or XUDTS and CdPA is Rt-on-SSN
Outgoing Message Encoding Errors

Cannot route to CgPA GTT information.

GTT of CgPA attempted network crossing.

DPC not a true point code.

GTT required on CgPA, but GTI is not 2 or 4.

GTT of CgPA failed for Bad GT Type (“No Translation).

GTT of CgPA failed for No Translation.

Could not encode CdPA or CgPA in response.

Outgoing formatted CdPN digits exceed the maximum allowed limit (32 digits in ITU TCAP Connect, 21 digits for routing digits in ANSI-41).
INPQ Service

INP CRP on: Call has a circular route detected and results in unsuccessful encoding of an INAP RELEASECALL message.
INPMR Service

Default CC or default NDC not provisioned, during number conditioning to International format.

Invalid length of conditioned digits
WARNINGS INPQ Service

GRN data required to encode digits in CONNECT response and GRN not provisioned in entity data.

INP CRP on: Detection of circular route by INPQS.
INPMR Service

GRN data required for own-network subscriber and GRN not provisioned in entity data.

INP CRP on: Detection of circular route by INPMR.
AINPQ-specific GRN data required to encode digits in RRWDGTS response and GRN not provisioned in entity data.
Outgoing Message Encoding Errors

Service Portability on: GRN data required for own-network subscriber and GRN not provisioned in entity data.
FORWARD TO GTT INPMR Service

Message falls through to GTT because GRN data was not provisioned for an own-network subscriber.

INP CRP on: Message falls through to GTT because of circular route detection.
TOTAL INPQ Service

INP CRP on: Equals ERRORS plus SUCCESS (does NOT include WARNINGS)
INPMR Service

INP CRP on: Equals ERRORS plus SUCCESS plus FORWARD TO GTT (does NOT include WARNINGS)

EAGLE Debug Commands

Commands User's Guide contains descriptions of debug commands that can be used in assessing and modifying system status and operation. Refer to Commands User's Guide for a complete description of the debug commands, including the ent-trace command. Most of the debug commands are used only under the direction of Oracle support personnel.

INP and AINPQ use the ent-trace command to provide a trap-and-trace function for MSUs on the Service Module cards.

Caution:

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

The ent-trace command can be used to create an MSU trigger on the Service Module card with one or more of the following criteria. When multiple trigger criteria are entered, the MSU is trapped when any one of the criteria is satisfied.

  • RN or SP address (Entity ID) - Trap messages immediately after performing the RTDB lookup. If the RN or SP obtained from the database lookup matches the Entity ID provisioned in the command, the message is trapped. This parameter supports a variable number of hexadecimal digits from 1 to 15 digits, and the Entity ID specified must be the one stored in the RTDB.

  • E.164 MSISDN number (DN) – Trap messages immediately before performing a search based on the MSISDN numbers defined in the RTDB. This parameter accepts a range of digits, from 5 to 15. The number specified must be an International E.164 number (MSISDN or Entity Number).

  • Global Title digits (GT) – Trap messages based on CdPA Global Title Address (that is, either MSISDN (+ST) number or RN + MSISDN (+ST)) present in the SCCP part of the message.

  • Origination point code (SSPI/SSPN) – Trap messages based on CgPA SPC present in the SCCP part of the message. If no point code is present in the CgPA SPC, the criteria is matched with the OPC present in the MTP part of the message.

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.

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

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

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.

Hourly Maintenance Report

The Hourly Maintenance Report, generated automatically, includes the alarm totals of the INP/AINPQ subsystem and Service Module card /EPAP IP links. A sample follows. 


    eagle10506 99-10-10 16:00:01 EST EAGLE 41.0.0
    5072.0000 REPT COND GSM SS
    "GSM SS :0440,MTCEINT-0,SA,99-10-10,16:00:01,,,,*C"
;
    eagle10506 99-10-10 16:00:01 EST EAGLE 41.0.0
    5073.0000 REPT COND INP SS
    "INP SS :0440,MTCEINT-0,SA,99-10-10,16:20:01,,,,*C"
;
    eagle10506 99-10-10 16:00:01 EST EAGLE 41.0.0
    5077.0000 REPT COND EPAPDSM
    "EPAPDSM :0084,MTCEINT-0,SA,99-10-10,16:00:01,,,,**"
;
    eagle10506 99-10-10 16:00:01 EST EAGLE 41.0.0
    5007.0000 REPT COND CARD
    "CARD 1102:0422,SCMMA,SA,99-10-10,16:00:01,,,,**"
;
    eagle10506 99-09-13 16:00:01 EST EAGLE 41.0.0
    3561.0000 REPT COND ALARM STATUS
    "ALARMS:PERM. INHIBITED,0,0,0"
    "ALARMS:TEMP. INHIBITED,0,0,0"
    "ALARMS:ACTIVE,10,14,3"
    "ALARMS:TOTAL,10,14,3"
;