Maintenance

ATINPQ Subsystem Alarms

This section contains a list of EAGLE Unsolicited Alarm Messages (UAMs) that support the ATINPQ local subsystem. All ATINPQ-related UAMs are generated to the APSS Output Group.

Refer to Unsolicited Alarm and Information Messages Reference for descriptions and corrective procedures for EAGLE-related alarms.

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

Table 6-1 ATINPQ UAMs

UAM	Severity	Message Text	Alarm Condition
0565	Critical	ATINPQ Subsystem is not available	No SCCP cards have an ATINPQ status of Active (all are OOS or loading)
0566	Critical	ATINPQ Subsystem is disabled	All IS-NR SCCP cards have ATINPQ status of offline (with at least 1 card IS-NR). An inh-map-ss command has been executed.
0567	Minor	ATINPQ Subsystm normal, cards(s) abnorml	1 SCCP card has ATINPQ status of Active and there are 1 or more cards with ATINPQ status other the Active (offline or loading)
0568	None	ATINPQ Subsystem is available	All SCCP cards are IS-NR and have an ATINPQ status of Active
0569	None	ATINPQ Subsystem is removed	Last SCCP card deleted

ATINPQ Subsystem UIMs

This section contains a list of EAGLE Unsolicited Information Messages (UIMs) that support the ATINPQ local subsystem.

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

Note:

If both a decode and an encode error occur during ATINP processing, precedence is given to the decode error and only one UIM will be generated.

Table 6-2 ATINPQ UIMs

UIM	Text	Description	Action
1395	Inh ATINPQ SS request alrdy outstanding	A second attempt to inhibit the ATINPQ subsystem has been made while the first is still being processed.	None - the second attempt will be ignored
1396	Failure Inhibiting ATINPQ SS	The attempted inhibit of the ATINPQ subsystem failed. A response SOG was not received from the mate.	No action necessary.
1397	LSS: Missing Mandatory Parameter	A required parameter was missing in the ATI NP query.	Verify that the incoming ATI NP query has Subscriber Identity and Requested Info parameters.
1398	ATINPQ: Badly formatted Subs Id	The Subscriber Identity parameter in the ATI NP query was found to be mistyped.	Verify that the Subscriber Identity parameter length is at least 2 bytes (1 byte length field of MSISDN). If greater than 2 bytes, the Subscriber Identity length must be equal to 2 + the length of the MSISDN.
1399	ATINPQ: Subscriber Identity not MSISDN	The Choice for Subscriber Identity in the ATI NP query is not the MSISDN.
1400	LSS: Invalid MSISDN digits length	The MSISDN length in Subscriber Information was 0, or the MSISDN had only one 0xF (filler) digit.
1402	ATINPQ: Invalid Requested Info	The Requested Info parameter in the incoming ATI NP query was invalid. Either the length of the Requested Info parameter does not contain MNP Requested Info or Location Information, or the parameter is badly formatted.
1403	LSS: Dgts truncated in encd parms	One or more encoded digits parameter in the ATI ACK response had to be truncated to fit maximum allowed encoded digits.	Verify the expected number of digits in routeingNumber and MSISDN fields. These depend on the combination of requested formatting for routeingNumber, MSISDN, and vlr-number fields (ATINPQOPTS: ATIACKRN, ATIACKMSISDN, ATIACKVLRNUM options), digits in incoming ATI NP query, and the result of RTDB lookup.
1426	S-Port: Missing GRN for srvc prtd subs	Service Portability required use of RTDB GRN for encoding response; however GRN was not provisioned.	Verify EPAP provisioning for the subscriber.

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

This command reports local subsystem operating status, CPU usage related to the subsystem, and Service Module card status. When the loc parameter is specified, the command displays detailed card traffic statistics.

EAGLE Debug Commands

Commands User's Guide contains descriptions of debug commands 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 are the DN and ENTITYID parameters when the ATINP feature is enabled.

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

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.