> Diameter Authentication Schema Statistics
> The Diameter Authentication schema provides operational statistics that can be used for monitoring and troubleshooting Diameter authentication functionality for STa, S6b, EAP, and so on used 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 Authentication Schema

> Variables | Description | Data Type
> vpnid | Description: The identification number of the context currently facilitating Diameter Authentication 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 Authentication 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: The 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
> der-req-id-sent | Description: The total number of Diameter-EAP-Request (DER) messages sent. Triggers: Increments when a DER message is sent Availability: Per AAAMgr instance | Int32
> der-req-aka-chal-sent | Description: The total number of DER-request-AKA-CHALLENGE messages sent. Triggers: Increments when a DER message is sent with AKA-Challenge Availability: Per AAAMgr instance | Int32
> der-req-retried | Description: The total number of retries for DER messages. Triggers: Increments when a DER message is retried Availability: Per AAAMgr instance | Int32
> dea-chal-rcvd | Description: The total number of DEA Challenge messages received. Triggers: Increments when a DEA message is received with EAP-Challenge Availability: Per AAAMgr instance | Int32
> dea-acpt-rcvd | Description: The total number of DEA Accept messages received. Triggers: Increments when a DEA is received with Result-Code value as 2001 Availability: Per AAAMgr instance | Int32
> dea-timeout | Description: The total number of DEA timeout messages. Triggers: Increments when a DEA is timed out Availability: Per AAAMgr instance | Int32
> dea-badauth | Description: The total number of DEA Bad-Authentication messages. Triggers: Increments when a DEA is received with malformed or wrong AVPs Availability: Per AAAMgr instance | Int32
> dea-malformed | Description: The total number of DEA Malformed messages. Triggers: Increments when a DEA is received with malformed version, length, or command-code, etc. Availability: Per AAAMgr instance | Int32
> dea-malformed-avp | Description: The total number of DEA Malformed AVP messages. Triggers: Increments when a DEA is received with malformed AVP Availability: Per AAAMgr instance | Int32
> dea-dropped | Description: The total number of dropped DEA messages. Triggers: Increments when a DEA is dropped Availability: Per AAAMgr instance | Int32
> rar-req-rcvd | Description: The total number of Re-Auth-Request (RAR) messages received. Triggers: Increments when a RAR is received Availability: Per AAAMgr instance | Int32
> raa-ans-accpt-sent | Description: The total number of Re-Auth-Answer (RAA) messages sent. Triggers: Increments when a RAA is sent Availability: Per AAAMgr instance | Int32
> aar-req-sent | Description: The total number of AAR messages sent. Triggers: Increments when a AAR is sent Availability: Per AAAMgr instance | Int32
> str-req-sent | Description: The total number of STR requests sent. Triggers: Increments when a STR is sent Availability: Per AAAMgr instance | Int32
> str-req-retried | Description: The total number of retries for STR messages. Triggers: Increments when a STR is retried Availability: Per AAAMgr instance | Int32
> sta-ans-accpt-rcvd | Description: The total number of received STA messages. Triggers: Increments when a STA is received Availability: Per AAAMgr instance | Int32
> asr-req-rcvd | Description: The total number of ASR requests received. Triggers: Increments when a ASR is received Availability: Per AAAMgr instance | Int32
> asa-rsp-accpt-sent | Description: The total number of ASA Messages sent. Triggers: Increments when a ASA is sent Availability: Per AAAMgr instance | Int32
> asa-rsp-rej-sent | Description: Total number of Abort-Session-Response sent with error Result-Code. Triggers: Increments when ASA is sent with failure result-code Availability: Per AAAMgr instance | Int32
> req-sock-write-err | Description: Total number of socket write failed for Diameter requests. Triggers: Increments when write failure is returned from socket for a Diameter request. Availability: Per Diameter TCP/SCTP connection | Int32
> rsp-sock-write-err | Description: Total number of socket write failed for Diameter responses. Triggers: Increments when write failure is returned from socket for a Diameter response. Availability: Per Diameter TCP/SCTP connection | Int32
> any-sock-read-err | Description: Total number of socket read failed for Diameter messages. Triggers: Increments when read failure is returned from socket for a Diameter message. Availability: Per Diameter TCP/SCTP connection | Int32
> rem-disconnect | Description: Total number of TCP/SCTP connections disconnected from remote peer. Triggers: Increments when a connection is disconnected from a remote peer. Availability: Per Diameter TCP/SCTP connection | Int32
> loc-disconnect | Description: Total number of TCP/SCTP connections disconnected locally. Triggers: Increments when a connection is disconnected locally. Availability: Per Diameter TCP/SCTP connection | 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