# SCCP Schema Statistics

The SCCP schema provides operational statistics that can be used for monitoring and troubleshooting the following products: SGSN
This schema provides the following types of statistics:

- Counter: A counter records incremental data cumulatively and rolls over when the counter limit is reached. All counter statistics are cumulative and reset only by one of the following methods: roll-over when limit is reached, after a system restart, or after a clear command is performed. The limit depends upon the data type.
- Gauge: A gauge statistic indicates a single value; a snapshot representation of a single point in time within a defined time frame. The gauge changes to a new value with each snapshot though a value may repeat from one period to the next. The limit depends upon the data type.
- Information: This type of statistic provides information, often intended to differentiate sets of statistics; for example, a VPN name or IP address. The type of information provided depends upon the data type.

The data type defines the format of the data for the value provided by the statistic. The following data types are used in statistics for this schema:

- Int32/Int64: An integer, either 32-bit or 64-bit: For statistics with the Int32 data type, the roll-over to zero limit is 4,294,967,295. For statistics with the Int64 data type, the roll-over to zero limit is 18,446,744,073,709,551,615.
- Float: A numeric value that can be represented fractionally; for example, 1.345.
- String: A series of ASCII alphanumeric characters in a single grouping, usually pre-configured.

IMPORTANT:

Unless otherwise indicated, all statistics are counters and all statistics are standards-based.

Key Variables: Every schema has some variables which are typically referred to as 'key variables'. These key variables provide index markers to identify which object the statistics apply to. For example, in the card schema, the card number (variable %card%) uniquely identifies a card. For an HA service, the keys would be "%vpnname%" plus "%servname%", as the combination uniquely identifies an HA service. So, in a given measurement interval, one row of statistics will be generated per unique key. The schema keys are identified in the Description section of the table.
Table 1. Bulk Statistic Variables in the SCCP Service Schema

Variables | Description | Data Type
--- | --- | ---
ssa-txed | Description: Total number of Subsystem Allowed (SSA) messages sent by Signalling Connection Control Part (SCCP) function to the peer destination Triggers: Increments when the SCCP subsystem becomes available (SCCP function is not prohibited or unavailable) and SCCP function sends an SSA message to inform the peer destination. Availability: per VPN context Type: Counter | Int32
ss-oos-grant-txed | Description: Total number of Subsystem-Out-of-Service-Grant (SOG) messages sent by the SCCP function. SOG is sent as a reply by the SCCP when it receives and accepts a Subsystem-Out-of-Service-Request (SOR) message from the peer SCCP. Triggers: Increments when a SOG message is sent, in reply to a SOR message, to the requesting SCCP. Availability: per VPN context Type: Counter | Int32
ss-oos-req-txed | Description: Total number of Subsystem-Out-of-Service-Request ( SOR) messages sent by the SCCP function, to the peer SCCP, to inform the peer that the requesting SCCP wishes to go out-of-service. Triggers: Increments when the SCCP wishes to go out-of-service and sends a SOR. Availability: per VPN context Type: Counter | Int32
ssp-txed | Description: Total number of Subsystem-Prohibited (SSP) messages sent by the SCCP function, to the peer SCCP subsytem, to inform the peer SCCP that the originateing SCCP is not not available. Triggers: Increments when the local SCCP is unavailable and sends an SSP message. Availability: per VPN context Type: Counter | Int32
ss-status-test-txed | Description: Total number of Subsystem-Status-Test messages (SST) sent by the local SCCP, to the peer SCCP subsystem, to verify the status of the marked peer. Triggers: Increments when the local SCCP sends SST to verify the peer's availability Availability: per VPN context Type: Counter | Int32
ssa-rcvd | Description: Total number of Subsystem-Allowed (SSA) messages received, by the local Signalling Connection Control Part (SCCP) function, from the peer SCCP. Triggers: Increments when the local SCCP sends SSA to verify the peer's availability Availability: per VPN context Type: Counter | Int32
ss-oos-grant-rcvd | Description: Total number of Subsystem-Out-of-Service-Grant (SOG) messages received by the SCCP. Triggers: Increments when the local SCCP accepts a Subsystem-Out-of-Service-Request (SOR). Availability: per VPN context Type: Counter | Int32
ss-oos-req-rcvd | Description:Total number of Subsystem-Out-of-Service-Request (SOR) messages received by the local SCCP. Triggers: Increments when the local SCCP receives a Subsystem-Out-of-Service-Request (SOR) message. Availability: per VPN context Type: Counter | Int32
ss-prohibit-rcvd | Description: Total number of Subsystem-Prohibited (SSP) messages received by the local SCCP. Triggers: Increments when the local SCCP receives an SSP message. Availability: per VPN context Type: Counter | Int32
ss-status-test-rcvd | Description: Total number of Subsystem Status Test (SST) messages received by the local SCCP Triggers: Increments when the local SCCP receives an SST message. Availability: per VPN context Type: Counter | Int32
ss-congested-txed | Description: Total number of Subsystem Congested (SSC) messages sent by the local SCCP. Triggers: Increments when the local SCCP sends an SSC message. Availability: per VPN context Type: Counter | Int32
ss-congested-rcvd | Description: Total number of Subsystem Congested (SSC) messages received by the local SCCP. Triggers: Increments when the local SCCP receives an SSC message. Availability: per VPN context Type: Counter | Int32
sccp-rtf-notrans-addr-nature | Description: Total number of SCCP routing failures due to unavailable translation for a bad address. Triggers: Increments when the local SCCP routing failures is due to unavailable translation for a bad address. Availability: per VPN context Type: Counter | Int32
sccp-rtf-notrans-addr-specific | Description: Total number of SCCP routing failures due to unavailable translation for a specific address. Triggers: Increments when the local SCCP routing failures is due to unavailable translation for a specific address. Availability: per VPN context Type: Counter | Int32
sccp-rtf-netwfail-pc-unavail | Description: Total number of SCCP routing failures due to a network failure or the point code is unavailable. Triggers: Increments when the SCCP routing failure is due to a network failure or the point code being unavailable. Availability: per VPN context Type: Counter | Int32
sccp-rtf-netw-conges | Description: Total number of SCCP routing failures due to a network failure result from congestion. Triggers: Increments when the SCCP routing failure is due to a network failure resulting from congestion. Availability: per VPN context Type: Counter | Int32
sccp-rtf-ssn-fail | Description: Total number of SCCP routing failures due to a subsystem failure of a specific subsystem number (SSN). Triggers: Increments when the SCCP routing failure is due to a subsystem failure of a specific subsystem number (SSN). Availability: per VPN context Type: Counter | Int32
sccp-rtf-ssn-conges | Description: Total number of SCCP routing failures due to subsystem congestion of a specific subsystem number (SSN). Triggers: Increments when the SCCP routing failure is due to subsystem congestion of a specific subsystem number (SSN). Availability: per VPN context Type: Counter | Int32
sccp-syntax-error | Description: Total number of SCCP functions that have failed due to a syntax error in a message. Triggers: Increments when the SCCP function fails due to a syntax error in a message. Availability: per VPN context Type: Counter | Int32
sccp-reassem-err-timer | Description: Total number of SCCP functions that failed due to the expiration of the reassembly timer for a message. Triggers: Increments when the SCCP function fails due to the expiration of the reassembly timer for a message. Availability: per VPN context Type: Counter | Int32
sccp-reassem-err-sequence | Description: Total number of SCCP functions that failed because segments arrived out of sequence during reassembly. Triggers: Increments when the SCCP function fails because segments arrived out of sequence during reassembly. Availability: per VPN context Type: Counter | Int32
sccp-reassem-err-space | Description: Total number of SCCP functions that failed due to out of memory or space errors occurred during reassembly. Triggers: Increments when the SCCP function fails because out of memory or space errors occurred during reassembly. Availability: per VPN context Type: Counter | Int32
sccp-hop-counter-violation | Description: Total number of SCCP functions that have failed due to hop counter violations in messages. Triggers: Increments when the SCCP function fails due to hop counter violations in a message. Availability: per VPN context Type: Counter | Int32
sccp-provider-ini-reset | Description: Total number of SCCP functions that have failed because the service provider initiated a reset. Triggers: Increments when the SCCP function fails due to a reset initiated by the service provider. Availability: per VPN context Type: Counter | Int32
sccp-provider-ini-rel | Description: Total number of SCCP functions that have failed because the service provider initiated a release. Triggers: Increments when the SCCP function fails due to a release initiated by the service provider. Availability: per VPN context Type: Counter | Int32
sccp-msg-toolarge-segment | Description: Total number of SCCP functions that have failed because the message was to large for segmentation. Triggers: Increments when the SCCP function fails because the messages was too large for segmentation. Availability: per VPN context Type: Counter | Int32
sccp-segmentation-fail | Description: Total number of SCCP functions that have failed due to failure of the segmentation procedure. Triggers: Increments when the SCCP function fails due to failure of the segmentation procedure. Availability: per VPN context Type: Counter | Int32
sccp-total-msgs-handled | Description: Total number of SCCP messages that have been handled by the subsystem. Triggers: Increments when a new SCCP message is received by the system and the message is intended for the local SCCP. Availability: per VPN context Type: Counter | Int32
sccp-total-msgs-handl-local-ss | Description: Total number of SCCP messages that have been handled by the subsystem but were intended for local subsystems. Triggers: Increments when a new SCCP message is received by the system. Availability: per VPN context Type: Counter | Int32
sccp-total-msgs-req-gtt | Description: Total number of SCCP messages that require global title translation (GTT). Triggers: Increments when an SCCP message is received, by the system, which requires GTT. Availability: per VPN context Type: Counter | Int32
sccp-udt-sent | Description: Total number of Unit Data (UDT) messages sent by the SCCP layer. Triggers: Increments when the SCCP layer sends a new UDT message. Availability: per VPN context Type: Counter | Int32
sccp-udt-rcvd | Description: Total number of Unit Data (UDT) messages received by the SCCP layer. Triggers: Increments when the SCCP layer receives a new UDT message. Availability: per VPN context Type: Counter | Int32
sccp-udts-sent | Description: Total number of Unit Data Service (UDTS) messages sent by the SCCP layer. Triggers: Increments when the SCCP layer sends a new UDTS message. Availability: per VPN context Type: Counter | Int32
sccp-udts-rcvd | Description: Total number of Unit Data Service (UDTS) messages received by the SCCP layer. Triggers: Increments when the SCCP layer receives a new UDTS message. Availability: per VPN context Type: Counter | Int32
sccp-xudt-sent | Description: Total number of Extended Unit Data (XUDT) messages sent by the SCCP layer. Triggers: Increments when the SCCP layer sends a new XUDT message. Availability: per VPN context Type: Counter | Int32
sccp-xudt-rcvd | Description: Total number of Extended Unit Data (XUDT) messages received by the SCCP layer. Triggers: Increments when the SCCP layer receives a new XUDT message. Availability: per VPN context Type: Counter | Int32
sccp-xudts-sent | Description: Total number of Extended Unit Data Service (XUDTS) messages sent by the SCCP layer. Triggers: Increments when the SCCP layer sends a new XUDTS message. Availability: per VPN context Type: Counter | Int32
sccp-xudts-rcvd | Description: Total number of Extended Unit Data Service (XUDTS) messages received by the SCCP layer. Triggers: Increments when the SCCP layer receives a new XUDTS message. Availability: per VPN context Type: Counter | Int32
sccp-ludt-sent | Description: Total number of Long Unit Data (LUDT) messages sent by the SCCP layer. Triggers: Increments when the SCCP layer sends a new LUDT message. Availability: per VPN context Type: Counter | Int32
sccp-ludt-rcvd | Description: Total number of Long Unit Data (LUDT) messages received by the SCCP layer. Triggers: Increments when the SCCP layer receives a new LUDT message. Availability: per VPN context Type: Counter | Int32
sccp-ludts-sent | Description: Total number of Long Unit Data Service (LUDTS) messages sent by the SCCP layer. Triggers: Increments when the SCCP layer sends a new LUDTS message. Availability: per VPN context Type: Counter | Int32
sccp-ludts-rcvd | Description: Total number of Long Unit Data Service (LUDTS) messages received by the SCCP layer. Triggers: Increments when the SCCP layer receives a new LUDTS message. Availability: per VPN context Type: Counter | Int32
sccp-cr-sent | Description: Total number of Connection Request (CR) messages sent by the SCCP layer. Triggers: Increments when the SCCP layer sends a new CR message. Availability: per VPN context Type: Counter | Int32
sccp-cr-rcvd | Description: Total number of Connection Request (CR) messages received by the SCCP layer. Triggers: Increments when the SCCP layer receives a new CR message. Availability: per VPN context Type: Counter | Int32
sccp-cc-sent | Description: Total number of Connection Confirm (CC) messages sent by the SCCP layer. Triggers: Increments when the SCCP layer sends a new CC message. Availability: per VPN context Type: Counter | Int32
sccp-cc-rcvd | Description: Total number of Connection Confirm (CC) messages received by the SCCP layer. Triggers: Increments when the SCCP layer receives a new CC message. Availability: per VPN context Type: Counter | Int32
sccp-cref-sent | Description: Total number of Connection Refuse (CREF) messages sent by the SCCP layer. Triggers: Increments when the SCCP layer sends a new CREF message. Availability: per VPN context Type: Counter | Int32
sccp-cref-rcvd | Description: Total number of Connection Refuse (CREF) messages received by the SCCP layer. Triggers: Increments when the SCCP layer receives a new CREF message. Availability: per VPN context Type: Counter | Int32
sccp-rsr-msg-sent | Description: Total number of Reset Request (RSR) messages sent by the SCCP layer. Triggers: Increments when the SCCP layer sends a new RSR message. Availability: per VPN context Type: Counter | Int32
sccp-rsr-msg-rcvd | Description: Total number of Reset Request (RSR) messages received by the SCCP layer. Triggers: Increments when the SCCP layer receives a new RSR message. Availability: per VPN context Type: Counter | Int32
sccp-err-msg-sent | Description: Total number of Protocol Data Unit Error (ERR) messages sent by the SCCP layer. Triggers: Increments when the SCCP layer sends a new ERR message. Availability: per VPN context Type: Counter | Int32
sccp-err-msg-rcvd | Description: Total number of Protocol Data Unit Error (ERR) messages received by the SCCP layer. Triggers: Increments when the SCCP layer receives a new ERR message. Availability: per VPN context Type: Counter | Int32
sccp-unequipped-user | Description: Total number of routing failures that occur when the upper SAP of the SCCP layer is unequipped. Triggers: Increments when routing failures occur because the upper SAP of the SCCP layer is unequipped. Availability: per VPN context Type: Counter | Int32
sccp-reason-unknown | Description: Total number of failures at the SCCP layer that are due to unknown reasons or reasons not specified in this table. Triggers: Increments when SCCP failure occurs due to unknown reason(s). Availability: per VPN context Type: Counter | Int32
sccp-congested-msg-rcvd | Description: Total number of SCCP/Subsystem Congested (SSC) messages received by the local SCCP. Triggers: Increments when a new SSC message is received by the SCCP. Availability: per VPN context Type: Counter | Int32
sccp-prohibit-msg-rcvd | Description: Total number of SCCP/Subsystem Prohibited (SSP) messages received by the local SCCP. Triggers: Increments when a new SSP message is received by the SCCP. Availability: per VPN context Type: Counter | Int32
sccp-class-0-sent | Description: Total number of SCCP class -0 (basic connectionless) messages are sent by SCCP function. Triggers: Increments when the SCCP layer sends a new class-0 message. Availability: per VPN context Type: Counter | Int32
sccp-class-0-rcvd | Description: Total number of SCCP class -0 (basic connectionless) messages are received by SCCP function. Triggers: Increments when the SCCP layer receives a new class-0 message. Availability: per VPN context Type: Counter | Int32
sccp-class-1-sent | Description: Total number of SCCP class -1 (basic connectionless) messages are sent by SCCP function. Triggers: Increments when the SCCP layer sends a new class-1 message. Availability: per VPN context Type: Counter | Int32
sccp-class-1-rcvd | Description: Total number of SCCP class -1 (basic connectionless) messages are received by SCCP function. Triggers: Increments when the SCCP layer receives a new class-1 message. Availability: per VPN context Type: Counter | Int32
sccp-DT1-sent | Description: Total number of Data Form 1 (DT1) messages that have been sent by the SCCP function. Triggers: Increments when the SCCP layer sends a new DT1 message. Availability: per VPN context Type: Counter | Int32
sccp-DT1-rcvd | Description: Total number of Data Form 1 (DT1) messages that have been received by the SCCP function. Triggers: Increments when the SCCP layer receives a new DT1 message. Availability: per VPN context Type: Counter | Int32
sccp-rel-compl-supv-fail | Description: Total number of SCCP functions released due to supervision failure in the SCCP release complete procedure. Triggers: Increments when the SCCP function is released due to supervision failure of the SCCP release complete procedure. Availability: per VPN context Type: Counter | Int32
sccp-rel-disconn-req-rx | Description: Total number of SCCP functions released due to received Disconnect Request messages. Triggers: Increments when the SCCP function is released because a DR is received. Availability: per VPN context Type: Counter | Int32
sccp-routing-fail-invalid-ins-routing-req | Description: Total number of routing failures due to invalid INS in the routing requested by the SCCP function. Triggers: Increments when the routing fails due to invalid INS in the routing requested by the SCCP function. Availability: per VPN context Type: Counter | Int32
sccp-routing-fail-invalid-isni-routing-req | Description: Total number of routing failures due to invalid intermediate signaling network identification (ISNI) information in the routing requested by the SCCP function. Triggers: Increments when the routing fails due to invalid ISNI information in the routing requested by the SCCP function. Availability: per VPN context Type: Counter | Int32
sccp-routing-fail-isni-constrained-routing | Description: Total number of routing failures due to constraints by the intermediate signaling network identification (ISNI) information in the routing requested by the SCCP function. Triggers: Increments when the routing fails due to constraints in the ISNI information in the routing requested by the SCCP function. Availability: per VPN context Type: Counter | Int32
sccp-routing-fail-redundant-isni-routing-req | Description: Total number of routing failures due to redundant intermediate signaling network identification (ISNI) information in the routing requested by the SCCP function. Triggers: Increments when the routing fails due to redundant ISNI information in the routing requested by the SCCP function. Availability: per VPN context Type: Counter | Int32
sccp-routing-fail-isni-identify-network | Description: Total number of routing failures due to missing intermediate signaling network identification (ISNI) information in the routing requested by the SCCP function. Triggers: Increments when the routing fails due to missing ISNI information in the routing requested by the SCCP function. Availability: per VPN context Type: Counter | Int32
sccp-inactivity-rcv-tmr-expired | Description: Total number of times the SCCP inactivity receive timer expired. Triggers: Increments when the SCCP inactivity receive timer expires. Availability: per VPN context Type: Counter | Int32
sccp-inactivity-test-sent | Description: Total number of SCCP Inactivity Test messages that were sent. Triggers: Increments when an SCCP Inactivity Test message is sent. Availability: per VPN context Type: Counter | Int32
sccp-inactivity-test-received | Description: Total number of SCCP Inactivity Test messages that were received. Triggers: Increments when an SCCP Inactivity Test message is received. Availability: per VPN context Type: Counter | Int32
IMPORTANT: For information on statistics that are common to all schema see the Statistics and Counters Overview chapter.