> Diameter Accounting Schema Statistics
> The Diameter Accounting schema provides operational statistics that can be used for monitoring and troubleshooting Rf interface functionality used by the following products:

> • | GGSN

> • | HSGW

> • | P-GW

> • | SCM

> 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 Diameter Accounting Schema

> Variables | Description | Data Type
> vpnid | Description: The identification number of the context currently facilitating Diameter Accounting configuration. This is a key variable. Triggers: This statistics is updated whenever a new VPN is configured. Availability: Per system Type: Information | Int32
> vpnname | Description: The name of the context currently facilitating Diameter Accounting configuration. This is a key variable. Triggers: This statistics is updated whenever a new VPN is configured. Availability: Per system Type: Information | String
> 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. Triggers: This statistics is updated whenever a new Authentication Server is configured. Availability: Per system Type: Information | String
> port | Description: The server port being used for exchange of data. This is a key variable. Triggers: This statistics is updated whenever a new Authentication Server is configured. Availability: Per system Type: Information | Int32
> servertype | Description: The type of server for which statistics are being collected. Triggers: This statistics is updated whenever a new Authentication Server is configured. Availability: Per system Type: Information | String
> group | Description: The name of the AAA Server Group. Triggers: This statistics is updated whenever a new AAA Server group is configured. Availability: Per system Type: Information | String
> req-sent | Description: The total number of Accounting Request messages sent. Triggers: Increments when a ACR is sent Availability: Per AAAMgr instance | Int32
> req-retried | Description: The total number of Accounting Requests retried. Triggers: Increments when a ACR is retried Availability: Per AAAMgr instance | Int32
> rsp-rcvd | Description: The total number of Accounting Responses received. Triggers: Increments when a ACA is received Availability: Per AAAMgr instance | Int32
> req-timeout | Description: The total number of Accounting Requests timed out. Triggers: Increments when a ACR is timed out Availability: Per AAAMgr instance | Int32
> rsp-bad-resp | Description: The total number of bad response messages received. Triggers: Increments when a ACA is received with wrong AVPs Availability: Per AAAMgr instance | Int32
> rsp-malformed | Description: The total number of malformed messages received. Triggers: Increments when a ACA is received with malformed AVPs Availability: Per AAAMgr instance | Int32
> rsp-dropped | Description: The total number of dropped messages received. Triggers: Increments when a ACA is dropped Availability: Per AAAMgr instance | Int32
> start-sent | Description: The total number of Accounting Start messages sent. Triggers: Increments when a ACR-START is sent Availability: Per AAAMgr instance | Int32
> stop-sent | Description: The total number of Accounting Stop messages sent. Triggers: Increments when a ACR-STOP is sent Availability: Per AAAMgr instance | Int32
> interim-sent | Description: The total number of Accounting Interim messages sent. Triggers: Increments when a ACR-INTERIM is sent Availability: Per AAAMgr instance | Int32
> start-retries | Description: The total number of retries for Accounting Start messages. Triggers: Increments when a ACR-START is retried Availability: Per AAAMgr instance | Int32
> stop-retries | Description: The total number of retries for Accounting Stop messages. Triggers: Increments when a ACR-STOP is retried Availability: Per AAAMgr instance | Int32
> interim-retries | Description: The total number of retries for Accounting Interim messages. Triggers: Increments when a ACR-INTERIM is retried Availability: Per AAAMgr instance | 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