Go to primary content
Oracle® Communications Measurements Reference
Release 46.6
E93320 Revision 1
Go To Table Of Contents
Contents

Previous
Previous
Next
Next

STP NM Report

STP-NM measurements are a system total of the STP, GTT, and MTP network management traffic. STP collection is the aggregated register totals of OAM and LIM/SCCP cards. If any one of these cards are isolated/re-booted during the collection period, measurements data is not provided to the OAM or MCPM and the interval is marked as I because at least one of the cards did not provide data. Measurement intervals for which the OAM and all LIM/SCCP cards are IS-NR throughout the measurement interval generate K reports.

enttype=stp

Example Commands:
  • UI: rept-meas:type=nm:enttype=stp
  • FTP: rept-ftp-meas:type=nm:enttype=stp

Table 3-35 Network Management STP Measurements

Event Name Description Unit

GTTPERFD

GTTs Performed - Usually, the total number of MSUs that successfully completed global title translation (GTT). Also includes G-Port and INPMSUs that got a match in either the G-Port, INP, or GTT DB.

Sometimes, GTTPERFD indicates the total number of global title translations (GTTs) performed on MSUs that successfully completed GTT, because several GTTs may happen for the same MSU. One scenario where multiple GTTs occur for an MSU occurs is when the ANSI/ITU SCCP Conversion Feature is activated. In this case, the count for GTTPERFD can be double what it would be without the feature, although the number of MSUs received by the EAGLE did not change.

peg count

GTTUN0NS

GTTs Unable to Perform - Diagnostic 0: No Translation for Address of Such Nature – Total number of times that the specified translation type in an MSU was not supported by the STP or the form of the GTT was incorrect for the given translation type.

peg count

GTTUN1NT

GTTs Unable to Perform - Diagnostic 1: No Translation for This Address – Number of times that a match for the global title could not be found in the translation table.

peg count

MSIDPMATCH

MSUs Returned – Total number of IDP messages returned to originating MSC. These messages bypass the prepaid engine since it has been determined that they meet the criteria for subscribers with unlimited prepaid calling plan.

peg count

MSIDPNOMCH

MSUs Relayed - Total number of IDP messages relayed to their destination.

peg count

MSINVDPC

MSUs Rcvd – Invalid DPC - The number of MSUs received and discarded because the DPC could not be found in the STP routing table.

peg count

MSINVSIF

MSUs Discarded – InvalidSIF - Number of MSUs that have been received and discarded because of an invalid SIF.

peg count

MSINVDPC

MSUs Rcvd – InvalidDPC - Number of MSUs received and discarded because the DPC could not be found in the STP routing table.

peg count

MSINVLNK

MSUs Discarded – InvalidLink - Number of MSUs discarded because of an incorrect SLC. (The SLC refers to a nonexistent link or the same link.)

peg count

MSINVSIO

MSUs Rcvd – Invalid Service Indicator Octet (SIO) -

Number of MSUs received and discarded because the service requested in the service indicator octet (SIO) was not supported by the STP.

peg count

MSINVSLC

MSUs Discarded – InvalidSLC - Number of MSUs discarded because of an invalid SLC code in the ECO/COO.

peg count

MSNACDPC

MSUs Discarded – InaccessibleDPC - The total number of MSUs discarded because of an inaccessible DPC.

peg count

MSSCCPFL

MSUs Discarded – Routing Failure - Number of MSUs discarded due to a routing failure.

peg count

MSUDSCRD

MSUs Discarded –Gateway Screening -

The total number of MSUs that failed gateway screening and have been discarded.

peg count

MSULOST1

MSUs Discarded – Level 2/Level 3 Queue Full -

Number of MSUs discarded because the level 2 to level 3 queue was full.

peg count

MSULOST2

MSUs Discarded –Route On Hold Buffer Overflow -

Number of MSUs discarded because the routing buffer was in overflow.

peg count

MSULOST3

MSUs Discarded –

  1. LS On Hold Buffer Overflow - The number of MSUs discarded because the linkset-on-hold buffer was in overflow. The On Hold Buffer is used during changeover/changeback situations to ensure that traffic is sequenced correctly. During changeover and changeback, MSUs that were originally sent over links which are now failed (not IS-NR) are buffered while the changeover/changeback procedures are carried out. Once those procedures are completed, the traffic in the on-hold buffer is routed based on the current configuration.
  2. LSL LIM does not have SCCP assignment for received SCCP traffic.
  3. HSL
    • All Class 1 (sequenced) GTT traffic addressed to EAGLE
    • A Class 0 GTT message for EAGLE arrives when the SCCP TVG queue is full
    • A GTT message in the SCCP TVG queue is more than 2 seconds old.

peg count

MSULOST4

MSUs Discarded – Rcv Queue Full -

Number of MSUs discarded because the receive queue was full.

peg count

NMTSKDSC0

Network Management Task Discard from Processor Overload - The total number of network management tasks (messages) discarded because of a processor overload (task priority = 0).

peg count

NMTSKDSC1

Network Management Task Discard from Processor Overload - The total number of network management tasks (messages) discarded because of a processor overload (task priority = 1).

peg count

NMTSKDSC2

Network Management Task Discard from Processor Overload - The total number of network management tasks (messages) discarded because of a processor overload (task priority = 2).

peg count

NMTSKDSC3

Network Management Task Discard from Processor Overload - The total number of network management tasks (messages) discarded because of a processor overload (task priority = 3).

peg count

OMSINVDPC

MSUs Originated – InvalidDPC -

Number of MSUs originated with an invalid DPC.

peg count

ORIGMSUS

OriginatedMSUs - The total number of outgoing MSUs successfully passed to MTP level 2 for transmission, while carrying the STP point code in the OPC field.

peg count

ORMSUOCT

OriginateMSU Octets -

The total number of outgoing octets associated with MSUs carrying the STP point code in the OPC field. This includes octets added in MTP level 2 processing.

octets

OVSZMSG

OversizedMTP 3 Messages - Oversized MTP 3 messages exceeding 272 octets (level 3) that are received by an HSL and are discarded.

peg count

STATUS

Indication of Data Validity:
  • K indicates good data
  • I indicates incomplete interval
  • N indicates data not current

status

THRSWMSU

Through-SwitchedMSUs -

The total number of MSUs that did not carry the STP point code in the OPC or the DPC, and were successfully passed to MTP level 2 for transmission.

peg count

TRMDMSUS

TerminatedMSUs - The total number of incoming MSUs carrying the STP point code in the DPC.

peg count

TRMSUOCT

TerminatedMSU Octets -

The total number of octets associated with incoming MSUs carrying the STP point code in the DPC. Includes octets removed in MTP level 2 processing.

octets

TSMSUOCT

Through-SwitchedMSU Octets -

The total number of octets associated with MSUs that did not carry the STP point code in the OPC or the DPC, and were successfully passed to MTP level 2 for transmission

octets

UI Example Output:

    eagle10506 03-04-15 17:13:02 EST EAGLE 34.0.0
    TYPE OF REPORT: NETWORK MANAGEMENT MEASUREMENTS ON STP
    REPORT PERIOD: LAST
    REPORT INTERVAL:  03-04-15,  17:05:00 THROUGH 17:09:59
    STP-NM MEASUREMENTS
    These measurements are from 03-04-15, 17:05:00 through 17:09:59.
    ORIGMSUS   =        80, TRMDMSUS   =        80, THRSWMSU   =         0,
    ORMSUOCT   =      1540, TRMSUOCT   =      1540, TSMSUOCT   =         0,
    MSINVDPC   =         0, MSINVSIO   =         0, OMSINVDPC  =         0,
    MSINVLNK   =         0, GTTPERFD   =         0, GTTUN0NS   =         0,
    GTTUN1NT   =         0, MSSCCPFL   =         0, MSINVSIF   =         0,
    MSNACDPC   =         0, MSINVSLC   =         0, MSUDSCRD   =         0,
    MSULOST1   =         0, MSULOST2   =         0, MSULOST3   =         0,
    MSULOST4   =         0, NMTSKDSC0  =         0, NMTSKDSC1  =         0,
    NMTSKDSC2  =         0, NMTSKDSC3  =         0, OVSZMSG    =         0
;
    eagle10506 03-04-15 17:13:03 EST EAGLE 34.0.0
    END OF ON-DEMAND STP-NM MEASUREMENT REPORT
;

FTP Example output file name: nm-stp_19990117_1550.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",
"NETWORK MANAGEMENT MEASUREMENTS ON STP","LAST","1999-01-17","15:45:00","15:50:00",1<cr><lf>
<cr><lf>
"STATUS","ORIGMSUS","TRMDMSUS","THRSWMSU","ORMSUOCT","TRMSUOCT","TSMSUOCT",
"MSINVDPC","MSINVSIO","OMSINVDPC","MSINVLNK","GTTPERFD","GTTUN0NS","GTTUN1NT",
"MSSCCPFL","MSINVSIF","MSNACDPC","MSINVSLC","MSUDSCRD","MSULOST1","MSULOST2",
"MSULOST3","MSULOST4","NMTSKDSC0","NMTSKDSC1","NMTSKDSC2","NMTSKDSC3","OVSZMSG"<cr><lf>
"K",80,80,0,1540,1540,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0<cr><lf>

Typical file size is:

Table 3-36 Typical File Size: nm-stp.csv

System header + Report header + Report data = File Size

250

+

315

+

477

=

1042 bytes