> DCCA Schema Statistics
> The Diameter Credit Control Application (DCCA) schema provides operational statistics that can be used for monitoring and troubleshooting Gy interface functionality used by the following products:

> • | GGSN

> • | HA

> • | IPSG

> • | PDSN

> • | P-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 DCCA Schema

> Variables | Description | Data Type
> vpnname | Description: Name of the context facilitating the DCCA configuration. This is a key variable. Availability: Per system Type: Information | String
> vpnid | Description: Identifier of the context currently facilitating the DCCA configuration. This is an internal reference number. This is a key variable. Availability: Per system Type: Information | Int32
> ipaddr | Description: IP address of the server for which statistics are being collected. The IP address can be specified in IPv4 or IPv6 notation. This is a key variable. Availability: Per system Type: Information | String
> port | Description: The port being used for exchange of data. This is a key variable. Availability: Per system Type: Information | Int32
> ccr-inisent | Description: Total number of Credit Control Request-Initial (CCR-Initial) messages sent. Triggers: Increments when the CCR-Initial message is successfully sent from the system Availability: Per Gy server | Int32
> cca-inirec | Description: Total number of Credit Control Answer-Initial (CCA-Initial) messages received. Triggers: Increments when the CCA-Initial message is successfully received Availability: Per Gy server | Int32
> cca-initimeout | Description: Total number of CCA-Initial message timeouts. Triggers: Increments when the CCA-Initial message response timeout occurs Availability: Per Gy server | Int32
> ccr-updsent | Description: Total number of CCR-Update messages sent. Triggers: Increments when the CCR-Update message is successfully sent from the system Availability: Per Gy server | Int32
> cca-updrec | Description: Total number of CCA-Update messages received. Triggers: Increments when the CCA-Update message is successfully received Availability: Per Gy server | Int32
> cca-updtimeout | Description: Total number of CCA-Update message timeouts. Triggers: Increments when the CCA-Update message response timeout occurs Availability: Per Gy server | Int32
> ccr-tersent | Description: Total number of CCR-Terminate messages sent. Triggers: Increments when the CCR-Terminate message is successfully sent from the system Availability: Per Gy server | Int32
> cca-terrec | Description: Total number of CCA-Terminate messages received. Triggers: Increments when the CCA-Terminate message is successfully received Availability: Per Gy server | Int32
> cca-tertimeout | Description: Total number of CCA-Terminate message timeouts. Triggers: Increments when the CCA-Terminate message response timeout occurs Availability: Per Gy server | Int32
> reauth-anssent | Description: Total number of Re-Authorization Answer messages sent. Triggers: Increments when the RAA message is successfully sent from the system Availability: Per Gy server | Int32
> reauth-reqrec | Description: Total number of Re-Authorization Request messages received. Triggers: Increments when the RAR message is received Availability: Per Gy server | 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