> IMSA Schema Statistics
> The IMSA schema provides operational statistics that can be used for monitoring and troubleshooting Gx, Gxx, and Ty interface functionality used by the following products: GGSN, HA, HSGW, IPSG, PDSN, P-GW, S-GW
> 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.
> Bulk Statistic Variables in the IMSA Schema

> Variables | Description | Data Type
> vpnname | Description: The name of the context configured on the system that is currently facilitating the IMS Authorization service. This is a key variable. Availability: Per system Type: Information | String
> vpnid | Description: The identification number of the context configured on the system that is currently facilitating the IMS Authorization service. This is an internal reference number. This is a key variable. Availability: Per system Type: Information | Int32
> servname | Description: The name of the IMS Authorization service for which the statistics are displayed. This is a key variable. Availability: Per system Type: Information | String
> servid | Description: The identification number of the service configured on the system that is currently facilitating the IMS Authorization service. This is an internal reference number. This is a key variable. Availability: Per system Type: Information | Int32
> dpca-cursess | Description: The total number of DPCA sessions currently active on this system. Triggers: Increments when DPCA session is created Decrements when DPCA session is terminated Availability: Per IMS authorization service Type: Gauge | Int32
> dpca-imsaadd | Description: The total number of DPCA sessions created. Triggers: Increments when DPCA receives a create request Availability: Per IMS authorization service | Int32
> dpca-start | Description: The total number of CCR Initial request messages sent. Triggers: Increments whenever CCR-I message is sent Availability: Per IMS authorization service | Int32
> dpca-seccreate | Description: The total number of UE Initiated Secondary contexts created in the system. Triggers: Increments when a UE initiated secondary bearer is created Availability: Per IMS authorization service | Int32
> dpca-secterm | Description: The total number of secondary contexts deleted for DPCA sessions on this system. Triggers: Increments when a UE initiated secondary bearer is terminated Availability: Per IMS authorization service | Int32
> dpca-sessupd | Description: The total number of updates to DPCA sessions on this system. Triggers: Increments whenever a CCR-U message is sent Availability: Per IMS authorization service | Int32
> dpca-term | Description: The total number of DPCA sessions terminated. Triggers: Increments when a IMSA session is terminated Availability: Per IMS authorization service | Int32
> dpca-msg-recv | Description: The total number of DPCA messages received by IMS authorization services configured on this system. Triggers: Increments whenever any DPCA message is received Availability: Per IMS authorization service | Int32
> dpca-msg-sent | Description: The total number of DPCA messages sent by IMS authorization services configured on this system. Triggers: Increments whenever any DPCA message is sent out of the chassis Availability: Per IMS authorization service | Int32
> dpca-msg-ccr | Description: The total number of DPCA credit control request messages sent by IMS authorization services configured on this system. Triggers: Increments when a CCR message is sent Availability: Per IMS authorization service | Int32
> dpca-msg-cca | Description: The total number of DPCA credit control answer messages received by IMS authorization services configured on this system. Triggers: Increments when a CCA message is received Availability: Per IMS authorization service | Int32
> dpca-msg-ccrinit | Description: The total number of initial DPCA credit control request messages sent by IMS authorization services configured on this system. Triggers: Increments when a CCR-I message is sent Availability: Per IMS authorization service | Int32
> dpca-msg-ccainit | Description: The total number of initial DPCA credit control accept messages received by IMS authorization services configured on this system. Triggers: Increments when a CCA-I message is received Availability: Per IMS authorization service | Int32
> dpca-msg-ccainitacc | Description: The total number of initial DPCA credit control accept messages accepted in response to initial credit control request messages sent by IMS authorization services configured on this system. Triggers: Increments when a CCA-I message is accepted Availability: Per IMS authorization service | Int32
> dpca-msg-ccainitrej | Description: The total number of initial DPCA credit control accept messages rejected in response to initial credit control request messages sent by IMS authorization services configured on this system. Triggers: Increments when a CCA-I message is rejected Availability: Per IMS authorization service | Int32
> dpca-msg-ccrupd | Description: The total number of CCR Update messages sent. Triggers: Increments when a CCR-U message is sent Availability: Per IMS authorization service | Int32
> dpca-msg-ccaupd | Description: The total number of CCA Update messages received. Triggers: Increments when a CCA-U message is received Availability: Per IMS authorization service | Int32
> dpca-msg-ccaupderror | Description: The total number of DPCA credit control accept messages received in response to credit control request update error messages sent by IMS authorization services configured on this system. Triggers: Increments when there is an error in CCA-U message Availability: Per IMS authorization service | Int32
> dpca-msg-ccrfin | Description: The total number of CCR Terminate messages sent. Triggers: Increments when CCR-T message is sent Availability: Per IMS authorization service | Int32
> dpca-msg-ccafin | Description: The total number of final DPCA credit control accept messages received in response to final credit control request messages sent by IMS authorization services configured on this system. Triggers: Increments when CCA-T message is received Availability: Per IMS authorization service | Int32
> dpca-msg-ccafinerror | Description: The total number of final DPCA credit control accept messages received in response to final credit control request error messages sent by IMS authorization services configured on this system. Triggers: Increments when there is an error in CCA-T message Availability: Per IMS authorization service | Int32
> dpca-msg-asr | Description: The total number of DPCA Abort-Session-Request messages received by IMS Authorization services configured on this system. Triggers: Increments when ASR message is sent (Not supported for 3GPP Rel. 7 standard and higher) Availability: Per IMS authorization service | Int32
> dpca-msg-asa | Description: The total number of DPCA Abort-Session-Accept messages sent in response to Abort-Session-Request messages received by IMS Authorization services configured on this system. Triggers: Increments when ASA message is received Availability: Per IMS authorization service | Int32
> dpca-msg-rar | Description: The total number of Re-Auth-Request messages received by IMS Authorization services configured on this system. Triggers: Increments when RAR message is received Availability: Per IMS authorization service | Int32
> dpca-msg-raa | Description: The total number of DPCA Re-Auth-Accept messages sent in response to Re-Auth-Request messages received by IMS Authorization services configured on this system. Triggers: Increments when RAA message is sent Availability: Per IMS authorization service | Int32
> dpca-msgerr-proto | Description: The total number of Diameter protocol error messages received by IMS Authorization services configured on this system. Triggers: Increments when result code of 3xxx is received Availability: Per IMS authorization service | Int32
> dpca-msgerr-badans | Description: The total number of bad response/answer error messages received by IMS Authorization services configured on this system. Triggers: Increments when a bad answer error message is received Availability: Per IMS authorization service | Int32
> dpca-msgerr-unksessreq | Description: The total number of error messages related to unknown session requests received by IMS Authorization services configured on this system. Triggers: Increments when RAR message is received for an unknown session Availability: Per IMS authorization service | Int32
> dpca-msgerr-unkcomm | Description: The total number of error messages related to unknown command codes received by IMS Authorization services configured on this system. Triggers: Increments when a message with unknown command code is received Availability: Per IMS authorization service | Int32
> dpca-msgerr-unsupcomm | Description: The total number of error messages related to unknown failure handling received by IMS Authorization services configured on this system. Triggers: Increments when an unsupported command is received Availability: Per IMS authorization service | Int32
> dpca-term-diamlogout | Description: The total number of DPCA session terminations due to Diameter logouts. Triggers: Increments when a CCR-T message is sent with this term cause Availability: Per IMS authorization service | Int32
> dpca-term-servnotprov | Description: The total number of DPCA session terminations due to unavailability of service. Triggers: Increments when a CCR-T message is sent with this term cause Availability: Per IMS authorization service | Int32
> dpca-term-badans | Description: The total number of DPCA session terminations due to bad responses/answers. Triggers: Increments when a CCR-T message is sent with this term cause Availability: Per IMS authorization service | Int32
> dpca-term-admin | Description: The total number of DPCA session terminations due to administrative reasons. Triggers: Increments when a CCR-T message is sent with this term cause Availability: Per IMS authorization service | Int32
> dpca-term-linkbroken | Description: The total number of DPCA session terminations due to a broken link. Triggers: Increments when a CCR-T message is sent with this term cause Availability: Per IMS authorization service | Int32
> dpca-term-authexp | Description: The total number of DPCA session terminations due to expired authorization. Triggers: Increments when a CCR-T message is sent with this term cause Availability: Per IMS authorization service | Int32
> dpca-term-usermoved | Description: The total number of DPCA session terminations due to the subscriber moving to an unknown or non-serviceable area. Triggers: Increments when a CCR-T message is sent with this term cause Availability: Per IMS authorization service | Int32
> dpca-term-sesstmo | Description: The total number of DPCA session terminations due to sessions timing out. Triggers: Increments when a CCR-T message is sent with this term cause Availability: Per IMS authorization service | Int32
> dpca-term-authrej | Description: The total number of DPCA session terminations due to the authorization being rejected. Triggers: Increments when a CCR-T message is sent with this term cause Availability: Per IMS authorization service | Int32
> dpca-term-other | Description: The total number of DPCA session terminations due to unknown reasons or reasons not listed above. Triggers: Increments when a CCR-T message is sent with this term cause Availability: Per IMS authorization service | Int32
> dpca-expres-errinitparam | Description: The number of times DIAMETER_ERROR_INITIAL_PARAMETERS (5140) Experimental-Result-Code value was received in the Diameter CCA. Triggers: Increments when a CCA message is received with this experimental result code Availability: Per IMS authorization service | Int32
> dpca-expres-errtrigevt | Description: The number of times DIAMETER_ERROR_TRIGGER_EVENT (5141) Experimental-Result-Code value was received in the Diameter CCA. Triggers: Increments when a CCA message is received with this experimental result code Availability: Per IMS authorization service | Int32
> dpca-expres-bearnotauth | Description: The number of times DIAMETER_ERROR_BEARER_NOT_AUTHORIZED (5143) Experimental-Result-Code value was received in the Diameter CCA. Triggers: Increments when a CCA message is received with this experimental result code Availability: Per IMS authorization service | Int32
> dpca-expres-trafmaprej | Description: The number of times DIAMETER_ERROR_TRAFFIC_MAPPING_INFO_REJECTED (5144) Experimental-Result-Code value was received in the Diameter CCA. Triggers: Increments when a CCA message is received with this experimental result code Availability: Per IMS authorization service | Int32
> dpca-expres-pccruleevt | Description: The number of times DIAMETER_PCC_RULE_EVENT (5142) Experimental-Result-Code value was sent in the Diameter Re-Auth-Request (RAR). Triggers: Increments when a RAA message is sent with this experimental result code Availability: Per IMS authorization service | Int32
> dpca-expres-conflictingreq | Description: The number of Gx Experimental Result code. DIAMETER_ERROR_CONFLICTING_REQUEST (5147) error is used when the PCRF cannot accept the UE-initiated resource request as a network-initiated resource allocation is already in progress that covers the packet filters in the received UE-initiated resource request. The PCEF rejects the attempt for UE-initiated resource request. Triggers: Increments when a CCA message is received with this experimental result code Availability: Per IMS authorization service | Int32
> dpca-expres-bearerevt | Description: Tracks the number of Gx Experimental Transient Failures. DIAMETER_PCC_BEARER_EVENT (4141) error is used when for some reason a PCC rule cannot be enforced or modified successfully in a network initiated procedure. Affected PCC-Rules will be provided in the Charging-Rule-Report AVP including the reason and status. This is a Transient Failure. Triggers: Increments when a CCA message is received with this experimental result code Availability: Per IMS authorization service | Int32
> dpca-expres-badrescode | Description: The number of times an unknown Experimental-Result-Code value (apart from the ones recognized in CCA that are listed above PCC Rule Event) was received in the Diameter CCA. Triggers: Increments when this experimental result code is received in a CCA message Availability: Per IMS authorization service | Int32
> dpca-peer-switch | Description: The total number of peer switches attempted. Triggers: Increments when performing a peer switch Availability: Per IMS authorization service | Int32
> dpca-peer-switch-done | Description: The total number of peer switches successful. Triggers: Increments when a peer switch is done Availability: Per IMS authorization service | Int32
> dpca-ccai-timeout | Description: The total number of CCA-I message timeouts. Triggers: Increments when Tx timer expires for CCA-I Availability: Per IMS authorization service | Int32
> dpca-ccri-send-error | Description: The total number of CCR-I message send errors (DIABASE ERRORS), since the TCP connection to the peer is no longer available. Triggers: Increments when there is an error in sending CCR-I message Availability: Per IMS authorization service | Int32
> dpca-ccai-unh-unk-rcode | Description: The total number of CCA-I messages received with unknown or unhandled result codes which have initiated the failure handling procedure configured for the any-error scenario. Triggers: Increments when there is an unknown result code in CCA-I message Availability: Per IMS authorization service | Int32
> dpca-ccai-err-rcode | Description: The total number of CCA-I messages received with error result codes which have initiated the failure handling procedure configured for a particular or range of result codes. Triggers: Increments when there is a known error code in CCA-I message Availability: Per IMS authorization service | Int32
> dpca-ccau-timeout | Description: The total number of CCA-U message timeouts. Triggers: Increments when Tx timer expires for CCA-U Availability: Per IMS authorization service | Int32
> dpca-ccru-send-error | Description: The total number of CCR-U message send errors (DIABASE ERRORS), since the TCP connection to the peer is no longer available. Triggers: Increments when there is a diabase error while sending CCR-U message Availability: Per IMS authorization service | Int32
> dpca-ccau-unh-unk-rcode | Description: The total number of CCA-U messages received with unknown or unhandled result codes which have initiated the failure handling procedure configured for the any-error scenario. Triggers: Increments when there is an unknown result code in CCA-U message Availability: Per IMS authorization service | Int32
> dpca-ccau-err-rcode | Description: The total number of CCA-U messages received with error result codes which have initiated the failure handling procedure configured for a particular or range of result codes. Triggers: Increments when there is a known error code in CCA-U message Availability: Per IMS authorization service | Int32
> dpca-ccat-timeout | Description: The total number of CCA-T message timeouts. Triggers: Increments when Tx timer expires for CCA-T Availability: Per IMS authorization service | Int32
> dpca-ccrt-send-error | Description: The total number of CCR-T message send errors (DIABASE ERRORS), since the TCP connection to the peer is no longer available. Triggers: Increments when there is a diabase error while sending CCR-T message Availability: Per IMS authorization service | Int32
> dpca-ccat-unh-unk-rcode | Description: The total number of CCA-T messages received with unknown or unhandled result codes which have initiated the failure handling procedure configured for the any-error scenario. Triggers: Increments when there is an unknown result code in CCA-T message Availability: Per IMS authorization service | Int32
> dpca-ccat-err-rcode | Description: The total number of CCA-T messages received with error result codes which have initiated the failure handling procedure configured for a particular or range of result codes. Triggers: Increments when there is a known error code in CCA-T message Availability: Per IMS authorization service | Int32
> dpca-ccfh-continue | Description: The total number of times the failure handling action continue has been undertaken. Triggers: Increments when CCFH continue action is undertaken Availability: Per IMS authorization service | Int32
> dpca-ccfh-retry-and-term | Description: The total number of times the failure handling action retry-and-terminate has been undertaken. Triggers: Increments when CCFH retry and terminate action is undertaken Availability: Per IMS authorization service | Int32
> dpca-ccfh-terminate | Description: The total number of times the failure handling action terminate has been undertaken. Triggers: Increments when CCFH terminate action is undertaken Availability: Per IMS authorization service | Int32
> dpca-unknown-reason | Description: The total number of sessions released due to unspecified reasons. Triggers: Increments when unspecified reason is received in Session Release Cause in RAR message Availability: Per IMS authorization service | Int32
> dpca-ue-subscription-chngd | Description: The total number of sessions released due to a change in the UE subscription. Triggers: Increments when UE subscription reason is received in Session Release Cause in RAR message Availability: Per IMS authorization service | Int32
> dpca-insuffcnt-srvr-resrce | Description: The total number of sessions released due to insufficient server resources. Triggers: Increments when insufficient resources are received in Session Release Cause in RAR message Availability: Per IMS authorization service | Int32
> dpca-fail-connfh-totmsgtmo | Description: The total number of message timeouts. Triggers: Increments whenever Tx timeouts for CCA-I, CCA-U, and CCA-T Availability: Per IMS authorization service | Int32
> dpca-fail-connfh-totmsgsenderr | Description: The total number of message send errors (DIABASE ERRORS), since the TCP connection to the peer is no longer available. Triggers: Increments when there is a diabase error while sending CCR-I, CCR-U, and CCR-T messages Availability: Per IMS authorization service | Int32
> dpca-fail-rescodefh-confrescode | Description: The total number of messages received with error result codes which have initiated the failure handling procedure configured for a particular or range of result codes. Triggers: Increments when there is a known error result code in CCA-I, CCA-U, and CCA-T messages Availability: Per IMS authorization service | Int32
> dpca-fail-rescodefh-unhunkrescode | Description: The total number of messages received with unknown or unhandled result codes which have initiated the failure handling procedure configured for the any-error scenario. Triggers: Increments when there is an unknown error result code in CCA-I, CCA-U, and CCA-T messages Availability: Per IMS authorization service | Int32
> Important: For information on statistics that are common to all schema see the Statistics and Counters Overview chapter.

> ‌

Cisco Systems Inc.
Tel: 408-526-4000
Fax: 408-527-0883