ATINP Measurements

5 ATINP Measurements

This chapter describes the measurements that can be collected and generated for the ATINP feature.

5.1 ATINP Measurements

The EAGLE Measurements Platform supports the collection and retrieval of measurements related to the ATINP feature and the ATINPQ local subsystem. The ATINP measurements are collected only with the Measurements Platform feature enabled and the Measurements Platform collection option on.

The EAGLE Measurements subsystem supports the collection and retrieval of measurements related to the ATINP feature and the ATINPQ local subsystem. The ATINP measurements can be collected with either of the following collection methods:

The Measurements Platform feature enabled and the Measurements Platform collection option on
The E5-OAM Integrated Measurements feature enabled and on and the E5-OAM Integrated Measurements collection option on

OAM-based (UI) measurements are not available for ATINP.

Refer to Measurements Reference for descriptions of collection methods, measurements, and measurements reports.

Refer to Commands User's Guide for descriptions of the commands used to enable and turn on features, turn on measurements collection options, and schedule and generate measurements reports.

Refer to the procedures in Database Administration - System Management User's Guide for configuring the Measurements Platform feature or the EAGLE Integrated Measurements feature and the EAGLE OA&M IP Security feature in the EAGLE.

The Per System totals and Per SSP totals shown in Table 5-1 are collected for ATINP. The totals are reported in the Hourly Maintenance Measurements (MTCHATINP) report and Daily Maintenance Measurements (MTCDATINP) report.

Note:

If an MSU is received with CdPA Rt-on-GT, EAGLE replaces the OPC with its PC as a part of the GTT process. If the CgPA is Rt-on-GT and no CgPA PC is present, it is not possible to determine the originating SSP until GTT has been performed on the CgPA during the encode function. If a decode problem with the query is encountered, then processing will be aborted and Per-SSP measurements will not be updated. GTT of the CgPA will not be attempted on a suspect message. Normal UIM generation will occur (see ATINPQ Subsystem UIMs).

Table 5-1 Pegs for Per System and Per SSP

Peg	Description
ATINPQRCV	Total number of queries received for the ATINPQ service, when the incoming message opcode is ATI. Note: MSUs resulting in U-Abort and P-Abort messages typically are not successfully decoded to identify them as ATI messages. ATINPQRCV will not be incremented for these MSUs.
ATIPNQACK	Total number of ATI ACK messages sent by the ATINPQ service
ATIPNQERR	Total number of incoming ATI messages that did not result in either ATI ACK or ATI NACK with Error Code of either Unknown Subscriber or ATI Not Allowed. (The ATI NACK is considered to be a TC_END TCAP message with a Return Error component.) Note: MSUs resulting in U-Abort and P-Abort messages typically are not successfully decoded to identify them as ATI messages. ATINPQERR will not be incremented for these MSUs.

Peg

Description

ATINPQRCV

Total number of queries received for the ATINPQ service, when the incoming message opcode is ATI.

Note: MSUs resulting in U-Abort and P-Abort messages typically are not successfully decoded to identify them as ATI messages. ATINPQRCV will not be incremented for these MSUs.

ATIPNQACK

Total number of ATI ACK messages sent by the ATINPQ service

ATIPNQERR

Total number of incoming ATI messages that did not result in either ATI ACK or ATI NACK with Error Code of either Unknown Subscriber or ATI Not Allowed. (The ATI NACK is considered to be a TC_END TCAP message with a Return Error component.)

Note: MSUs resulting in U-Abort and P-Abort messages typically are not successfully decoded to identify them as ATI messages. ATINPQERR will not be incremented for these MSUs.