1. EAGLE G-Flex C7 Relay User's Guide
  2. Maintenance

7 Maintenance

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

7.1 G-Flex-Related Alarms

Refer to the Unsolicited Alarm and Information Messages Reference for a complete description, formats, output examples, and the associated corrective procedure for each G-Flex-related UAM.

The alarms shown in Table 7-1 can be generated for the G-Flex service (including G-Flex traffic).

Table 7-1 G-Flex-Related Alarms

UAM # Severity Message Text Output Group (UI Output Direction)

0328

None

SCCP is available

GTT

0329

None

SCCP capacity normal, card(s) abnormal

GTT

0330

Major

SCCP TPS Threshold exceeded

GTT

0331

Critical

SCCP is not available

GTT

0335

None

SCCP is removed

GTT

0336

Major

LIM(s) have been denied SCCP service

GTT

0526

None

Service is available

APSS

0527

Minor

Service abnormal

APSS

0528

Critical

Service is not available

APSS

0529

Critical

Service is disabled

APSS

0530

None

Service is removed

APSS

7.2 G-Flex-Related UIMs

The Unsolicited Alarm and Information Messages Reference contains a complete description of all UIM text and formats. Table 7-2 describes the G-Flex and G-Flex MLR UIMs. All of the the G-Flex-related UIMs are generated to the Application Subsystem Output Group.

Table 7-2 G-Flex UIMs

UIM # Text Description Recovery

1242

Conv to intl num - Dflt CC not found

Default CC is not defined

Define the default CC by chg-stpopts:defcc=xxxx

1243

Conv to intl num - Dflt NC not found

Conversion to international number failed because default NDC was not found

Define the default NDC by chg-stpopts:defndc=xxxx

1244

Conv to intl num – Dflt MCC not found

Default MCC is not defined

Define the default MCC by chg-gsmopts:defmcc=xxxx

1245

Conv to intl num – Dflt MNC not found

Default MNC is not defined

Define the default MNC by chg-gsmopts:defmnc=xxxx

1246

Invalid length of conditioned digits

Length of the conditioned international number is <5 or >15

Use an international number with length within this range.

1247

Conversion of MGT to IMSI not possible

The E.212 part for the E.214 MGT digit not found in the database

Enter the E.212 part (MCC + MNC) for the E.214 MGT part (CC + NDC) in the database using chg-gsmopts:ccndc=xxxxxx:mccmnc=yyyyyy

1384

 G-Flex MLR: Op without IMSI erroneous

The G-Flex MLR Function encountered an updateLocation, updateGprsLocation, or sendAuthenticationInfo operation that did not contain an IMSI parameter

The G-Flex MLR Function encountered an updateLocation, updateGprsLocation, sendAuthenticationInfo, registerSS, activateSS, deactivateSS, interrogateSS, restoreData, readyForSM, or purgeMS operation that did not contain an IMSI parameter

No action necessary

1385

G-Flex MLR: Op without IMSI skipped

The G-Flex MLR Function encountered a sendParameters operation that did not contain an IMSI parameter

No action necessary

1386

G-Flex MLR: Op with bad TCAP skipped

The G-Flex MLR Function encountered problems decoding the TCAP and MAP layers of a message prior to attempting to identify IMSI or MSISDN parameters (for example, generic structure decoding problems such as Length part errors). This UIM is not generated when a valid TCAP component other than Invoke is detected.

The G-Flex MLR Function encountered problems decoding the TCAP and MAP layers of a message prior to attempting to identify an IMSI parameter

No action necessary

1387

G-Flex MLR: Op with bad IMSI skipped

The G-Flex MLR Function encountered an IMSI parameter that contains fewer than 5 digits or more than 15 digits

No action necessary

1440

G-Flex MLR: Op with bad MSISDN skipped

The G-Flex MLR Function encountered an AnyTimeInterrogation, processUnstructuredSS-Request, or sendRoutingInfoForLCS operation that contains an invalid MSISDN parameter

No action necessary

1448

 G-Flex MLR: Op w/o IMSI/MSISDN skipped

The G-Flex MLR Function encountered a processUnstructuredSS-Request operation that does not contain an IMSI or MSISDN parameter.

 No action necessary

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

7.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 values, and output examples for the command.

The rept-stat-sccp command displays the following statistics for the G-Flex service when the G-Flex feature is turned on:

  • State information

  • Alarm information

  • Number of G-Flex messages that have been re-routed for the prior 30 seconds.

    The Re-route count is incremented when the G-Flex service is OFFLINE and messages are re-routed to alternate PCs or fall through to GTT.

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

A G-Flex MSU trigger can be created on the Service Module card, on any one or more of the following criteria defined in the ent-trace command. When multiple trigger criteria are entered, the MSU is trapped when any of the criteria are satisfied.

  • E.164 MSISDN number (MSISDN) – Use this criterion to trap messages immediately before performing a G-Flex search based on the MSISDN numbers defined in the Real Time Database (RTDB). This parameter allows a variable number of digits (from 5 to 15). The number specified must be an International E.164 number (MSISDN or Entity Number).

  • E.212 IMSI number (IMSI) – Use this criterion to trap messages immediately before performing a G-Flex search based on the IMSI numbers defined in the RTDB. This parameter allows a variable number of digits (from 5 to 15). The number specified must be an international E.212 IMSI. This parameter cannot be used to trap on E.214 MGT.

  • Global Title digits (GT) – Use this criterion to trap messages based on the CdPA Global Title Address (that is, either E.164, E.214 MGT, or E.212 number) present in the SCCP part of the message.

  • SSP point code (MSC or VLR PC, for example) – After the SSN has been determined to belong to a G-Flex entity object, use this criterion to trap messages based on CgPA (Calling Party Address) SPC present in the SCCP part of the message. If no point code is present in CgPA SPC, the criteria is matched with the OPC present in the MTP part of the message.

Caution:

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

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

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

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

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

7.5.2 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"
;