1. EAGLE Analyzed Information Features User's Guide
  2. Maintenance

6 Maintenance

This chapter describes commands, tools and reports that can be used for Analyzed Information feature maintenance, including status reporting and problem identification.

Alarms

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

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

Table 6-1 can be generated by the IAR NP, IAR, ASD, and IAR GRN features and other features that use the RTDB. There are no UAMs that are specific to the IAR-related features.

Table 6-1 UAM 0451

UAM Message Text Description

0451

RTDB reload is required

 The RTDB is not already downloaded on the Service Module card and a feature that needs the RTDB is turned ON.

IAR-Related UIMs

The Unsolicited Information Messages (UIMs) in Table 6-2 support the IAR-related features, and the UIM in Table 6-3 supports the Service Portability feature. Unsolicited Alarm and Information Messages Reference contains a complete description of all UIM text and recovery procedures.

Table 6-2 IAR-Related UIMs

UIM Text Description Action
1020 IARCDPN NPP SERVICE is off The status of the IARCDPN service is OFF while processing a message. Set the status of the IARCDPN service to ON.
1021 IARCGPN NPP SERVICE is off The status of the IARCGPN service is OFF while processing a message. Set the status of the IARCGPN service to ON.
1427 IAR CdPN parameter invalid or not found

The IAR Base feature cannot find the CdPN parameter within a message, when it cannot decode the parameter after it finds it, or when the parameter does not contain the required information in a usable format.

If there is a DSTDGTS parameter, it is used as the CdPN. If there is no DSTDGTS parameter, the DGTSDIAL parameter is used as the CdPN. If neither parameter is in the AnalyzedInformation message, or one parameter is present but invalid, or both parameters are present but the chosen CdPN is invalid, UIM 1427 is generated.

The DSTDGTS and DGTSDIAL parameters are considered invalid if they are encoded in a format other than BCD.

 
1428 IAR CgPN parameter invalid or not found

The IAR Base feature cannot find the CgPN parameter within a message, when it cannot decode the parameter after it finds it, or when the parameter does not contain the required information in a usable format.

The CPNDGTS1 parameter is considered invalid if it is encoded in a format other than BCD.

  
1429 IAR TRIGTYPE invalid or not found The IAR Base feature cannot find the TRIGTYPE parameter within a message, when it cannot decode the parameter after it finds it, or when the parameter does not contain the required information in a usable format.  
1430 IAR CdPN parameter encoding failed The IAR Base feature cannot encode the message after modifying its CdPN parameter. One way that this can occur without invalid data is when a CdPN parameter length increases, and the containing message grows too large (more than 275 octets).  
1431 IAR CgPN parameter encoding failed The IAR Base feature cannot encode the message after modifying its CgPN parameter. One way that this can occur without invalid data is when a CgPN parameter length increases, and the containing message grows too large (more than 275 octets).  

The following UIM is generated when Service Portability is used with IAR NP, and the required GRN data has not been provisioned.

Table 6-3 UIM for Service Portability

UIM Text Description Action
1426 S-Port: Missing GRN for srvc prtd subs The GRN data is not present that is needed for Service Portability processing. Verify and correct the GRN data provisioning in the RTDB.

AIQ Local Subsystem Alarms

This section contains a list of EAGLE UAMs that support the AIQ local subsystem. All ANSI41 AIQ-related UAMs are generated to the LSS Output Group and use the SYS_MAINT format.

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

Table 6-4 describes the UAMs that are specific to the AIQ local subsystem.

Note:

"Active" Service Module cards have a status not equal to OOS (Out-of-Service), loading, or Offline.

Table 6-4 AIQ Local Subsystem UAMs

UAM Message Text Description

0592

AIQ : Subsystem is not available

 No Service Module cards have an AIQ status of Active (see Note; all are OOS or loading).
0593 AIQ : Subsystem is disabled All IS-NR (In-Service Normal) Service Module cards have Subsystem status of Offline (with at least 1 card IS-NR). An inh-map-ss command has been executed.
0594 AIQ : Subsystem normal, card(s) abnormal One Service Module card has Subsystem status of Active (see Note), and one or more cards have Subsystem status other than Active.
0595 AIQ : Subsystem is available All Service Module cars are IS-NR and have Subsystem status of Active.
0596 AIQ : Subsystem is removed The last Service Module card is deleted.

AIQ Local Subsystem UIMs

The Unsolicited Information Messages (UIMs) in Table 6-5 specifically support the AIQ Local Subsystem.

Refer to Unsolicited Alarm and Information Messages Reference for a complete description of all UIM text and formats, including UIMs that are used for local subsystems.

Table 6-5 AIQ Local Subsystem UIMs

UIM Text Output Group Description Action
1433 AIQ: Inhibit request already pending APSS A second attempt to inhibit the subsystem has been made while the first attempt is still being processed. The second attempt is ignored.
1434 AIQ: Failure Inhibiting SS APSS The attempted inhibit of the subsystem failed. A response SOG was not received from the mate.
1435 AIQ: Trigger Type not provisioned APSS An entry matching the incoming Trigger Type value is not found in the AIQOPTS table. Verify the TRIGTYPE option values in the AIQOPTS table, and provision the missing entry if needed.
1436 AIQ: Unsupported Digits (Dialed) length APSS The number of Digits (Dialed) in the received AnalyzedInformation Query is not within the provisioned range of the DIGMINLEN and DIGMAXLEN option values in the AIQOPTS table. Verify the DIGMINLEN and DIGMAXLEN option values in the AIQOPTS table, and modify the values if needed.

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

IAR Base Feature Statistics

The following statistics are updated for the GTT service rept-stat-sccp command counts and displays the following statistics when the IAR Base feature is enabled and turned on:
  • TOTAL = the total number of messages that were passed into the IAR Base feature by the TTR Service Selector processing. TOTAL = ERRORS plus SUCCESS plus REROUTE/WARNINGS.
  • TOTAL = the total number of messages for which the IAR Base feature is selected for processing. TOTAL = ERRORS plus SUCCESS plus REROUTE/WARNINGS.
  • SUCCESS = the number of messages that passed pre-NPP processing, NPP processing, and post-NPP processing without being dismissed, and were modified before being routed to the destination.
  • WARNINGS = the number of messages for which a UIM (1020, 1021, 1427-1431) was generated, indicating messages that were not counted in SUCCESS.
  • ERRORS = the number of messages that were not counted in SUCCESS and a UIM was not counted in WARNINGS. The problem could be that the message was dismissed, or that a routing failure occurred on a message that was not dismissed.
  • FORWARD TO GTT = the total number of GT-routed messages that were sent for GTT processing by the IAR Base feature processing.

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.

The ent-trace command can be used to trace MSUs sent to Service Module cards that are running the VSCCP application. The EAGLE traps MSUs that meet the specified tracing criteria, which include DN, some point codes, Entity ID, message verification errors, and message processing errors.

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