Maintenance

6 Maintenance

This chapter describes the maintenance information available from the EAGLE for the MO SMS features. The information includes status, alarms (UAMs), and information messages (UIMs).

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

6.2 UIMs

This section lists the Unsolicited Information Messages (UIMs) used to support the MO SMS features. Refer to Unsolicited Alarm and Information Messages Reference for a complete description of all UIM text and formats.

Table 6-1 Unsolicited Information Messages

UIM	Text	Description	Action
1374	SMS B-party Address decode failed	An error was detected during decode of the SMS message destination address.	The message should be analyzed to determine the error, and the originating node should be contacted to send a corrected message.
1375	SMS Failed to modify TCAP MSU	The formatted outbound digit string length generated by MO SMS features for encoding the TCAP message exceeded system limits.	The message and outbound digits formatting should be analyzed to determine the error, and the originating node or the requested outbound digits formatting option should be modified to correct the encoding error.
1376	SMS Failed to modify B-party digits	During processing of the SMS message, the formatted outbound digit string length exceeded limit for number of digits.	The message and the digit format provisioning should be analyzed to determine the error, and the originating node or the requested outbound digit formatting option should modified to correct the encoding error.
1410	MOSMS: Migrated Subscriber with no entity	No entity is defined in the RTDB for the migrated subscriber. The subscriber is found to be migrated and the migration prefix must be the entity resulting from the RTDB Lookup.	Ensure that the subscriber has an entity in the RTDB or change the value for MOIGMPFX in Table IS41SMSOPTS.
1416	MAP Missing Mandatory Parameters	An MO SMS feature cannot decode the GSM MAP message because mandatory parameters (SM-RP-UI or SM-RP-OA) in the TCAP portion of the message are missing.	Ensure that the message contains all mandatory parameters.
1425	SMS A-party Address decode failed	Decoding of the SMS_OOA parameter fields of the IS41 SMDPP message failed. MSU encountered a decoding error.	Ensure that the SMDPP message contains a corrctly formatted SMS_OOA parameter.
1426	S-Port: Missing GRN for srvc prtd subs	Service Portability is to be applied and RTDB GRN is required to format outbound digits but is not provisioned for the DN.	Verify EPAP and EAGLE provisioning to configure the GRN for the DN.

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

6.3.1 rept-stat-sccp

The rept-stat-sccp command provides statistics for local subsystem operating status, CPU usage related to the subsystem, and Service Module cards and the services that execute on the cards. Statistics can be displayed for all Service Module cards, or detailed card traffic statistics can be displayed for a single card when the loc parameter is specified.

Statistics are displayed under SMSMR Service Statistics for MO SMS IS41-to-GSM Migration, MO-Based GSM SMS NP, MO-Based IS41 SMS NP, and PPSMS features.

Refer to Commands User's Guide for a complete description of the rept-stat-sccp command, including parameters and valid values, rules for using the command correctly, and output examples.

MO SMS-Related Feature Statistics

All rept-stat-sccp counters for MO SMS processing are displayed with the SMSMR Service. The rept-stat-sccp counters show the outcome of the cumulative processing of all Mo SMS-related features.

All of the rept-stat-sccp counters except the ERRORS counter are incremented. The ERRORS counter is pegged only by the features that respond to the incoming message. MO SMS-related features are message relay features.

MO SMS-related features are processed independently based on whether the feature is provisioned and turned on with an NPP service. Each feature keeps track of whether the message processing is SUCCESS, FAILURE or WARNINGS. At the end of all processing, rept-stat-sccp counters are derived by considering all feature outcome cumulatively. The counters are derived in the following order - first FAILURE, second WARNINGS, third SUCCESS. and last FALL THROUGH:

FAILURE: The message had all information required for processing and was processed, but encountered delivery problems due to cross network routing failure, lack of routing information, or encoding failure. Failure errors do not mean that the message being processed is discarded. Because all MO SMS-related features are intercepting the message being translated by GTT, the messages fall back to GTT routing without modification when a failure to process has occurred.
WARNINGS: This count will be incremented for the feature if a decoding failure, lack of information to process, parameter not provisioned, or processing failure is encountered.
SUCCESS: The feature successfully processed the message. Message contents have been modified.
FALL THROUGH: The message is good; none of the features changed the contents of the message.
TOTAL: SUCCESS + FAILURE + WARNINGS + FALL THROUGH = TOTAL number of messages processed by the SMSMR service.

SMDPP or Forward Short Message Decoding and Pre-NPP Processing

Table 6-3 Service Status Counters-Message Decoding and Pre-NPP Processing

Service Status Completion	Description
WARNINGS	Could not decode Calling Party or Called Party parameters from the message. See x
FALL THROUGH	Message is not valid. IS41: Not an SMDPP message. GSM: Message is not MO-FSM. PDU type is not SMS_SUBMIT or SMS-COMMAND.
	NPP Service Status is OFF.
	SCCP message is not UDT Or non-segmented XUDT.

Table 6-4 rept-stat-sccp Counters Incremented During Decoding

	Missing CgPN	Missing CdPN	Decode Error in CgPN	Decode Error in CdPN
GSM	Missing mandatory parameter- WARNINGS	Missing mandatory parameter- WARNINGS	WARNINGS	WARNINGS
IS41	--	--	WARNINGS (An error)	WARNINGS (An error)

The following tables describe the counters that are incremented specifically for message decoding and for MO SMS-related features.

Prepaid SMS Intercept Phase 1 Feature Service Status Counters

Table 6-5 Service Status Counters-Prepaid SMS Intercept Phase 1

Service Completion Status	Description
SUCCESS	Message is for a Prepaid subscriber, and the message was processed
WARNINGS	Length of the MSISDN digits is less than 0 or greater than 21
	Length of the outbound DN digits is greater than 20
	MSU number conditioning failed because DEFCC or DEFNDC is not provisioned
	NPP processing failed
	Length of the conditioned digits is greater than 15
FAILURE	Failed to route to the Prepaid server Invalid Point Code is defined for IN Plat form No SSN is present in entity data and no CdPA SSN is present SCCP layer encode to Prepaid server failed In all of these cases, the message falls through to GTT without modification.
FALL THROUGH (Did not process)	Message is not from or to a Prepaid subscriber
	Message is from a Prepaid server.
	MSISDN is not found in RTDB
	MOSMSGCGPN or MOSMSGCDPN NPP service state is OFF
	PPSMS feature is not turned on

Portability Check for MO SMS Feature Service Status Counters

Table 6-6 Service Status Counters-Portability Check for MO SMS

Service Completion Status	Description
SUCCESS	FRAUD detected
WARNINGS	Length of the MSISDN digits is less than 0 or greater than 21
	Length of the outbound DN digits is greater than 20
	MSU number conditioning failed because DEFCC or DEFNDC is not provisioned
	NPP processing failed
	Length of the conditioned digits is greater than 15
FAILURE	Encoding and sending of NACK message failed. (TCAP length is zero; translated PC after GTT is in a different domain.) Encoding and sending ABORT message to SMSC failed. (TCAP portion length is zero during encoding.)
FALL THROUGH (Did not process)	MSISDN is not found in RTDB
	Subscriber is not FRAUD
	Destination is not HOME SMSC
	MOSMSGCGPN NPP service state is OFF
	Portability Check for MO SMS feature is not turned on

MO SMS IS41-to-GSM Migration Feature Service Status

Table 6-7 Service Status Counters-MO SMS IS41-to-GSM Migration

Service Completion Status	Description
SUCCESS	User found to have migrated, and message is modified
WARNINGS	MIGRATE failed because the IS41SMSOPTS MOIGMPFX option is not provisioned
	MIGRATE failed because the GSMOPTS IS412GSM option is not provisioned and the IS41SMSOPTS MOIGMPFX option is set to IS412GSM
	Subscriber is migrated base on NO ENTITY with DN PORT TYPE = 5 and the IS41SMSOPTS MOIGMPFX option is set to NE
	Length of the outbound DN digits is greater than 20
	MSU number conditioning failed because DEFCC or DEFNDC is not provisioned
	NPP Conditioning Action execution or Formatting Action execution failed
	Length of the conditioned digits is greater than 15
FAILURE	Modified TCAP encoding failed The message falls through to GTT without being modified.
FALL THROUGH (Did not process)	DA/ODA not found in RTDB
	Called Party parameter is not found to have migrated
	Destination is not HOME SMSC
	The MOSMSICDPN NPP service state is OFF
	MO SMS IS41-to-GSM Migration feature is not turned on

Number Portability and Service Portability Service Status

Table 6-8 Service Status Counters-Number Portability and Service Portability

Service Completion Status	Description
SUCCESS	Number Portability or Service Portability was applied and the message was modified
WARNINGS	Length of the outbound DN digits is greater than 20 for GSM messages and 21 for IS41 messages
	MSU number conditioning failed because DEFCC or DEFNDC is not provisioned
	Decode of SM-RP-UI parameter failed. The length of the TP_DA parameter and valued do not conform with the GSM MAP protocol requirements.
	NPP Conditioning Action execution or Formatting Action execution failed
	Length of the conditioned digits is greater than 15
	Service Portability is applicable but GRN is not provisioned for the DN in the RTDB. Service Portability is applicable if the S-Port feature is turned on and any of the following conditions is true: Subscriber is own-network IS41 subscriber and the SPORTTYPE configuration option value is IS41 or ALL Subscriber is own-network GSM subscriber and the SPORTTYPE configuration option value is GSM or ALL
FAILURE	Modified TCAP encoding failed The message falls through to GTT without being modified.
FALL THROUGH (Did not process)	RTDB lookup was unsuccessful because DA/ODA were not found in the RTDB or an Entity was not found or validated
	Called Party parameter is not ported out and Service Portability does not apply
	Destination is HOME SMSC
	The MOSMSICDPN or MOSMSGCDPN NPP service state is OFF
	The required Number Portability feature is not turned on

MO SMS B-Party Routing Feature Service Status Counters

Table 6-9 Service Status Counters-MO SMS B-Party Routing

Service Completion Status	Description
SUCCESS	Successfully routed MSU on B-Party Number
WARNINGS	Length of the outbound DN digits is greater than 20
FAILURE	Modified TCAP encoding failed The message falls through to GTT without being modified.
	SCRC_ERR_USER_ACTION_UDTS. UDTS generated.
	SCRC_ERR_USER_ACTION_DISCARD. MSU discarded.
	SCRC_ERR_NO_SSN_IN. MSG_OR_XLATION. Lack of routing information. Message falls through to GTT without being modified..
	SCRC_ERR_MSG_XING_DOMAIN. Delivery problems were encountered due to cross network. Message falls through to GTT without being modified..
	SCRC_ERR_CLG_PC_CONVERSION. Delivery problems were encountered due to cross network. Message falls through to GTT without being modified..
FALL THROUGH (Did not process)	SCRC_ERR_NO_XLATION. No rules were configured for the B-Party GTA..
FALL THROUGH (Did not process)	MO SMS B-Party Routing feature is not turned on

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

6.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 6-10 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`

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