STP GTWY Report

STP GTYW reports are an aggregation of the counters from OAM, SCCP, and LIM cards. If any of the cards are ISOLATED/OOS during a measurement interval, the report is marked I. The report is marked K only when the OAM, SCCP, and LIM cards are IS-NR throughout the entire measurement interval.

Example Commands:

• UI

  • rept-meas:type=gtwy:enttype=stp
• FTP

  • rept-ftp-meas:type=gtwy:enttype=stp

Measurement Events

Table 3-196 Gateway STP Measurements

Event Name	Description	Unit
GTTPFDIC	Number of Global Title Translations (GTTs) performed on messages received from an interconnecting network.	peg count
MSUDSCRD	Number of MSUs discarded due to screening failure.	peg count
MSURJOPC	Number of MSUs rejected due to screening - disallowed OPC.	peg count
MSURJDPC	Number of MSUs rejected due to screening - disallowed DPC.	peg count
MSURJSIO	Number of MSUs rejected due to screening - invalid service information octet (SIO).	peg count
MSURJCPA	Number of MSUs rejected due to screening - invalid calling party address.	peg count
MSURJAPC	Number of subsystem prohibited (SSP) and subsystem allowed (SSA) MSUs rejected due to screening - invalid affected point code.	peg count
MSURJPCS	Number of subsystem status test (SST) MSUs rejected due to screening - invalid affected point code and SSN.	peg count
MSURJDST	Number of MTP-NM MSUs rejected due to screening - invalid affected destination field.	peg count
MSURJTT	Number of SCCP MSUs rejected due to screening - invalid translation type.	peg count
MSURJDSN	Number of SCCP MSUs rejected due to screening - disallowed DPC/SSN in called party address.	peg count
MSURJTFC	Number of transfer controlled (TFC) MSUs rejected due to screening - invalid affected destination field.	peg count
MSURJSRT	Number of signaling routeset test (SRST) MSUs rejected due to screening - invalid affected destination field.	peg count
STATUS	Indication of Data Validity: K indicates good data I indicates incomplete interval N indicates data not current	status
TTMAPPF	Number of translation type mapping translations performed. For example, a mapped SS7 message translation type was found for the existing SS7 message translation type.	peg count

UI Reports

UI Example Output:

    tekelecstp 03-12-19 12:51:24 EST EAGLE 34.0.0 
    TYPE OF REPORT: GATEWAY MEASUREMENTS ON STP
    REPORT PERIOD: LAST
    REPORT INTERVAL:  03-12-19,  12:00:00 THROUGH 12:29:59 
    
    STP-GTWY MEASUREMENTS
    
    These measurements are from 03-12-19, 12:00:00 through 12:29:59.
    TTMAPPF    =         0, GTTPFDIC   =         0, MSUDSCRD   =         0,
    MSURJOPC   =         0, MSURJDPC   =         0, MSURJSIO   =         0, 
    MSURJCPA   =         0, MSURJAPC   =         0, MSURJPCS   =         0, 
    MSURJDST   =         0, MSURJTT    =         0, MSURJDSN   =         0, 
    MSURJTFC   =         0, MSURJSRT   =         0
    
;
    tekelecstp 03-12-19 12:51:26 EST EAGLE 34.0.0 
    END OF ON-DEMAND STP-GTWY MEASUREMENT REPORT
;

FTP Reports

FTP Example Output File Name: gtwy-stp_19990117_1530.csv

FTP Example Output File Format:

"CLLI","SWREL","RPTDATE","RPTIME","TZ","RPTTYPE","RPTPD","IVALDATE",
"IVALSTART","IVALEND","NUMENTIDS"<cr><lf>
"tekelecstp","34.0.0-39.1.0","1999-01-17","15:51:37","EST",
"GATEWAY MEASUREMENTS ON STP","LAST","1999-01-17","15:00:00","15:30:00",1<cr><lf>
<cr><lf>
"STATUS","TTMAPPF","GTTPFDIC","MSUDSCRD","MSURJOPC","MSURJDPC","MSURJSIO", "MSURJCPA","MSURJAPC","MSURJPCS","MSURJDST","MSURJTT","MSURJDSN","MSURJTFC", "MSURJSRT"<cr><lf>
"K",0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>

Typical file size is:

Table 3-197 Typical File Size: gtwy-stp.csv

System header	+	Report header	+	Report data	=	File Size
250	+	164	+	90	=	504 bytes