1. EAGLE IDP-Related Features User's Guide
  2. Maintenance

8 Maintenance

This chapter describes commands, tools and reports that can be used for IDP Relay and IDP-Relay-related feature maintenance, including status reporting and problem identification.

Alarms

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

IDP Relay-Related UIMs

The Unsolicited Information Messages (UIMs) in Table 8-1 support the IDP Relay feature. Unsolicited Alarm and Information Messages Reference contains a complete description of UIMs, including text, output examples, and recovery procedures.

Note:

"IDPRCDPN(X)" refers to any of the IDPRCDPN, IDPRCDPN2, IDPRCDPN3, and IDPRCDPN4 services,

Table 8-1 IDP Relay-Related UIMs

UIM Text Description Action
1382 Too many digits for DRA parameter Too many digits (>31) in the DRA parameter to encode. Decrease the number of RN digits or modify the querying node to send fewer digits in DN.
1392 IDPRCDPNIDPRCDPN(X) NPP SERVICE is Disabled The status of the IDPRCDPNIDPRCDPN(X) service is OFF while processing an IDP message. Set the status of the IDPRCDPNIDPRCDPN(X) service to ON.
1393 IDPRCGPN NPP SERVICE is Disabled The status of the IDPRCGPN service is OFF while processing an IDP message. Set the status of the IDPRCGPN service to ON.
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.

Note:

The EPAP does not have any UIM requirements.

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

IDP Relay Feature Statistics

The following statistics are updated for the GTT service when the IDP Relay feature is turned on:
  • FORWARD TO GTT = total number of messages sent for GTT processing
  • SUCCESS = the IDPRSUCC measurements register count.
  • ERRORS = the total of the IDPRERR and IDPRFAIL measurements register counts
  • FAIL RATIO = ERRORS divided by the total of ERRORS plus SUCCESS
  • REROUTE/WARNINGS = number of UIMs generated
  • TOTAL = ERRORS plus SUCCESS plus REROUTE/WARNINGS

Statistics Affected by IDP-Related Features

The following IDP Relay statistics are updated for the TTR service when one or more of the IDP A-Party Blocklist, IDP A-Party Routing, and IDP Service Routing features are enabled and turned on. Table 8-4 and Table 8-3 summarize the updates.
  • Depending upon provisioning configuration, feature status, Service Action outcome, and feature results, the IDP and IDPSMS messages that are successfully processed by IDP A-Party Routing, IDP Service Key Routing, or IDP A-Party Blocklist Query or Relay will not result in updating the Forward to GTT counters.
  • If message processing results in success, the Success counters for the TTR service are updated, and the Forward to GTT counters are not updated.
  • If message processing results in an encoding or routing error, the Error counters for the TTR service are updated, and the Forward to GTT counters are not updated.
  • If message processing results in a fall-through to GTT due to insufficient feature data or success match criteria, the TTR Forward to GTT counters are updated
  • The TTR Total count is updated for every message serviced (resulting in success or failure) through the IDPR service.

The number of messages handled by any IDP Relay-related feature that did not go through to GTT can be derived from the difference between the TTR Total and Forward to GTT counters.

The TTR Error counter is updated in the case of routing failure for the IDP A-Party Routing and IDP Service Key Routing features, and in the case of Connect/Continue Encoding failure for the IDP A-Party Blocklist feature.

Table 8-3 IDP Relay Counters Updated for IDP A-Party Routing and IDP Service Key Routing

IDP A-Party Routing IDP Service Key Routing
Success No Match/incomplete data Success Fall-through to GTT
SK Routing success Fall-through to GTT

Update:

TTR:Success

TTR:Total

Update:

TTR:Success

TTR:Total

Update:

TTR:Success

TTR:Forward to GTT

TTR:Total

Update:

TTR:Success

TTR:Total

Update:

TTR:Success

TTR:Fall-through to GTT

TTR:Total

Table 8-4 IDP Relay Counters Updated for IDP A-Party Blocklist

IDP A-Party Blocklist Query IDP A-Party Blocklist Relay
Match (Connect response) No Match/incomplete data (Continue response) Match (Connect response) No Match/incomplete data (fall-through to GTT)

Update:

TTR:Success

TTR:Total

Update:

TTR:Success

TTR:Total

Update:

TTR:Success

TTR:Total

Update:

TTR:Success

TTR:Forward to GTT

TTR:Total

rtrv-data-rtdb

The rtrv-data-rtdb command retrieves 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 data is retrieved on the active Service Module card that has the lowest IMT address.

IDP A-Party Blocklist Feature Data

The rtrv-data-rtdb command displays the blocklist indicator for a number that is blocklisted. The DN parameter must be entered to specify the DN to be displayed:
  • A DN that is located in a non-ranged entry and is listed as an A-Party Blocklisted number
  • A DN that is located in a ranged entry and is listed as an A-Party Blocklisted number

The rtrv-data-rtdb command with the DN parameter also displays an indicator for a number that is public or private.