In this section:

Signaling Gateway Statistics

The DSC Platform provides Signaling Gateway (SG) data measurements as described in the following table.

The following figure shows an example for these measurements.

The instance represents the application object that generates the data measurements. The Signaling Gateway (SG) instance value has the following format:

  • slot_<CPU>


SG Stats

Name in Stats File Statistic Description
Msgs TX to IP Applications Msgs TX to IP Applications The total number of data messages sent by the SG to IP applications.
Msgs RX from IP Applications Msgs RX from IP Applications The total number of data messages received by SG from IP applications.
Bad Msgs RX from IP Application Bad Msgs RX from IP Application The total number of incorrectly formatted data messages received from an ASP.
Msgs TX to SS7 Msgs TX to SS7 The total number of data messages sent by the SG to SS7.
Msgs RX from SS7 Msgs RX from SS7 The total number of data messages received by the SG from SS7.
Bad Msgs from SS7 Bad Msgs from SS7 The total number of incorrectly formatted data messages received from SS7.
Discarded Msgs from SS7 Discarded Msgs from SS7 The total number of discarded data messages received from SS7.
Discarded Msgs from IP Applications Discarded Msgs from IP Applications The total number of discarded data messages received from IP applications.
SS7 Msgs TX to Peer SS7 Msgs RX to Peer The total number of SS7 data messages sent to the peer SG.
SS7 Msgs RX from Peer SS7 Msgs TX from Peer The total number of SS7 data messages received from the peer SG.
IP Msgs RX from Peer IP Msgs RX from Peer The total number of IP (UA) data messages received from the peer SG.
IP Msgs TX to Peer IP Msgs TX to Peer The total number of IP (UA) data messages sent to the peer SG.
M3UA Msgs TX M3UA Msgs TX The total number of M3UA data messages sent to ASPs.
M3UA Msgs RX M3UA Msgs RX The total Number of M3UA data messages received from ASPs.
Bad Msgs RX from M3UA Bad Msgs RX from M3UA The total number of incorrectly formatted data messages received from an M3UA ASP.
Discarded Msgs from M3UA Discarded Msgs from M3UA The total number of discarded data messages received from ASP.
SUA Msgs TX SUA Msgs TX The total number of SUA data messages sent to ASPs.
SUA Msgs RX SUA Msgs RX The total number of SUA data messages received from ASPs.
Bad Msgs RX from SUA Bad Msgs RX from SUA The total number of incorrectly formatted data messages received from an SUA ASP.
Discarded Msgs from SUA Discarded Msgs from SUA The total number of discarded data messages received from SUA.
SCCP Msgs TX SCCP Msgs TX The total number of data messages sent to SCCP.
SCCP Msgs RX SCCP Msgs RX The total number of data messages received from SCCP.
Bad Msgs RX from SCCP Bad Msgs RX from SCCP The total number of incorrectly formatted data messages received from SCCP.
Discarded Msgs from SCCP Discarded Msgs from SCCP The total number of discarded data messages received from SCCP.
MTP3 Msgs TX MTP3 Msgs TX The total number of data messages sent to MTP3.
MTP3 Msgs RX MTP3 Msgs RX The total number of data messages received from MTP3.
Bad Msgs RX from MTP3 Bad Msgs RX from MTP3 The total number of incorrectly formatted data messages received from MTP3.
Discarded Msgs from MTP3 Discarded Msgs from MTP3 The total number of discarded data messages received from MTP3.

M3UA-ASP Statistics

The DSC Platform provides M3UA-ASP data measurements as described in the following table.

Note
M3UA ASP Congestion statistics are only provided for configured ASPs. Congestion statistics will not be provided for M3UA ASPs connecting dynamically.


Note
The instance identifies the name of the ASP in the M3UA ASP configuration.


SG M3UA-ASP Stats

Name in Stats File Statistic Description

Msgs TX to M3UA ASP

Msgs TX to M3UA ASP

The total number of M3UA data messages sent to ASP.

Msgs RX from M3UA ASPMsgs RX from M3UA ASP

The total Number of M3UA data messages received from ASP.

Bytes TX to M3UA ASPBytes TX to M3UA ASP

The total number of M3UA bytes sent to ASP.

Bytes RX to M3UA ASPBytes RX to M3UA ASP

The total Number of M3UA bytes received from ASP.

Msgs Discarded TX to M3UA ASPMsgs Discarded TX to M3UA ASP

The total number of discarded data messages sent to the ASP.

Msgs Discarded RX from M3UA ASPMsgs Discarded RX from M3UA ASP

The total number of discarded data messages received from the ASP.

M3UA ASP Outage TimeM3UA ASP Outage Time

The total time the association is unavailable.

M3UA ASP Sctp Retransmission Data ChunksM3UA ASP Sctp Retransmission Data Chunks

Number of SCTP data chunks retransmitted on this association.

Duration of Level 1 ASP CongestionDuration of Level 1 ASP Congestion

The total time the M3UA ASP was in congestion Level 1 during the measurement interval. This total time is derived by summing the time duration of each individual Level  congestion event. A Level 1 congestion event begins when the Level 1 congestion onset threshold is first reached or exceeded, or at the start of the measurement interval if the M3UA ASP is already at congestion Level 1. The Level 1 congestion event ends when one of the following occurs:

  • the occupancy first falls below the Level 1 congestion abatement threshold
  • the occupancy reaches or exceeds the congestion onset threshold for Levels 2 or 3
  • the measurement interval ends

Note: The congestion L1 duration is started when the M3UA ASP congestion level changes to Level 1.

Duration of Level 2 ASP CongestionDuration of Level 2 ASP Congestion

The total time the M3UA ASP was in congestion Level 2 during the measurement interval. This total time is derived by summing the time duration of each individual Level  congestion event. A Level 2 congestion event begins when the Level 2 congestion onset threshold is first reached or exceeded, or at the start of the measurement interval if the M3UA ASP is already at congestion Level 2. The Level 2 congestion event ends when one of the following occurs:

  • the occupancy first falls below the Level 2 congestion abatement threshold
  • the occupancy reaches or exceeds the congestion onset threshold for Level 3
  • the measurement interval ends
  • the occupancy first falls below the Level 2 congestion abatement threshold
  • the occupancy reaches or exceeds the congestion onset threshold for Level 3
  • the measurement interval ends

Note: The congestion L2 duration is started when the M3UA ASP congestion level changes to Level 2.

Duration of Level 3 ASP CongestionDuration of Level 3 ASP Congestion

Total time the M3UA ASP is in congestion Level 3 during the measurement interval. This total time is derived by summing the time duration of each individual Level 3 congestion events. A Level 3 congestion event begins when the Level 3 congestion onset threshold is first reached or exceeded, or at the start of the measurement interval if the M3UA ASP is already at congestion Level 3. The Level 3 congestion event ends when one of the following occurs:

  • the occupancy first falls below the level 3 congestion abatement threshold or
  • the measurement interval ends

Note: The congestion Level 3 duration is started when congestion level changes to Level 3.

Event Count for Entering Level 1 ASP CongestionEvent Count for Entering Level 1 ASP CongestionThe number of times congestion Level 1 is entered. Congestion Level 1 is entered when the M3UA ASP was previously not congested, and the transmission buffer occupancy at a given scan first reaches or exceeds the Level 1 congestion onset threshold, but does not reach or exceed the congestion onset threshold for Level 2 or 3.
Event Count for Entering Level 2 ASP CongestionEvent Count for Entering Level 2 ASP CongestionThe number of times congestion Level 2 is entered. Congestion Level 2 is entered when the M3UA ASP is previously not congested or at Level 1, and the link transmission buffer occupancy at a given scan first reaches or exceeds the Level 2 congestion onset threshold, but does not reach or exceed the congestion onset threshold for Level 3.
Event Count for Entering Level 3 ASP CongestionEvent Count for Entering Level 3 ASP CongestionThe number of times congestion Level 3 is entered. Congestion Level 3 is entered when the M3UA ASP is previously not congested or at Levels 1 or 2, and the link transmission buffer occupancy at a given scan first reaches or exceeds the Level 3 congestion onset threshold.
Priority 0 MSU's Discarded Due to Congestion

MSU's Discarded Due to Congestion

Priority 0

The number of priority 0 messages discarded due to congestion.
Priority 1 MSU's Discarded Due to Congestion

MSU's Discarded Due to Congestion

Priority 1

The number of priority 1 messages discarded due to congestion.
Priority 2 MSU's Discarded Due to Congestion

MSU's Discarded Due to Congestion

Priority 2

The number of priority 2 messages discarded due to congestion.
Priority 3 MSU's Discarded Due to Congestion

MSU's Discarded Due to Congestion

Priority 3

The number of priority 3 messages discarded due to congestion.

M3UA-ASSOC Statistics

The DSC Platform provides M3UA-ASSOC data measurements as described in the following table.

SG M3UA-ASSOC Stats

Name in Stats File Statistic Description
Duration of Level 1 ASSOC Congestion

Duration of Level 1 ASSOC

Level 1

The total time the M3UA Multi-ASP Assoc was in congestion Level 1 during the measurement interval. This total time is derived by summing the time duration of each individual Level congestion event. A Level 1 congestion event begins when the Level 1 congestion onset threshold is first reached or exceeded, or at the start of the measurement interval if the M3UA Multi-ASP Assoc is already at congestion Level 1. The Level 1 congestion event ends when one of the following occurs:

  • the occupancy first falls below the Level 1 congestion abatement threshold
  • the occupancy reaches or exceeds the congestion onset threshold for Levels 2 or 3
  • the measurement interval ends

Note: The congestion L1 duration is started when the M3UA Multi-ASP Assoc congestion level changes to Level 1.

Duration of Level 2 ASSOC Congestion

Duration of ASSOC Congestion

Level 2

The total time the M3UA Multi-ASP Assoc was in congestion Level 2 during the measurement interval. This total time is derived by summing the time duration of each individual Level  congestion event. A Level 2 congestion event begins when the Level 2 congestion onset threshold is first reached or exceeded, or at the start of the measurement interval if the M3UA Multi-ASP Assoc is already at congestion Level 2. The Level 2 congestion event ends when one of the following occurs:

  • the occupancy first falls below the Level 2 congestion abatement threshold
  • the occupancy reaches or exceeds the congestion onset threshold for Level 3
  • the measurement interval ends
  • the occupancy first falls below the Level 2 congestion abatement threshold
  • the occupancy reaches or exceeds the congestion onset threshold for Level 3
  • the measurement interval ends

Note: The congestion L2 duration is started when the M3UA Multi-ASP Assoc congestion level changes to Level 2.

Duration of Level 3 ASSOC Congestion

Duration of ASSOC Conjection

Level 3

Total time the M3UA Multi-ASP Assoc is in congestion Level 3 during the measurement interval. This total time is derived by summing the time duration of each individual Level 3 congestion events. A Level 3 congestion event begins when the Level 3 congestion onset threshold is first reached or exceeded, or at the start of the measurement interval if the M3UA Multi-ASP Assoc is already at congestion Level 3. The Level 3 congestion event ends when one of the following occurs:

  • the occupancy first falls below the level 3 congestion abatement threshold or
  • the measurement interval ends

Note: The congestion Level 3 duration is started when congestion level changes to Level 3.

Event Count for Entering Level 1 ASSOC Congestion

Event Count for Entering ASSOC Congestion

Level 1

The number of times congestion Level 1 is entered. Congestion Level 1 is entered when the M3UA Multi-ASP Assoc was previously not congested, and the transmission buffer occupancy at a given scan first reaches or exceeds the Level 1 congestion onset threshold, but does not reach or exceed the congestion onset threshold for Level 2 or 3.
Event Count for Entering Level 2 ASSOC Congestion

Event Count for Entering ASSOC Congestion

Level 2

The number of times congestion Level 2 is entered. Congestion Level 2 is entered when the M3UA Multi-ASP Assoc is previously not congested or at Level 1, and the link transmission buffer occupancy at a given scan first reaches or exceeds the Level 2 congestion onset threshold, but does not reach or exceed the congestion onset threshold for Level 3.
Event Count for Entering Level 3 ASSOC Congestion

Event Count for Entering ASSOC Congestion

Level 3

The number of times congestion Level 3 is entered. Congestion Level 3 is entered when the M3UA Multi-ASP Assoc is previously not congested or at Levels 1 or 2, and the link transmission buffer occupancy at a given scan first reaches or exceeds the Level 3 congestion onset threshold.
Priority 0 MSU's Discarded Due to Congestion

MSU's Discarded Due to Congestion

Priority 0

The number of priority 0 messages discarded due to congestion.
Priority 1 MSU's Discarded Due to Congestion

MSU's Discarded Due to Congestion

Priority 1

The number of priority 1 messages discarded due to congestion.
Priority 2 MSU's Discarded Due to Congestion

MSU's Discarded Due to Congestion

Priority 2

The number of priority 2 messages discarded due to congestion.
Priority 3 MSU's Discarded Due to Congestion

MSU's Discarded Due to Congestion

Priority 3

The number of priority 3 messages discarded due to congestion.