> IPSG Schema Statistics
> The IPSG schema provides operational statistics that can be used for monitoring and troubleshooting the following products: IPSG
> 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 IPSG Schema

> Variables | Description | Data Type
> vpnname | Description: Name of the VPN context in which the IPSG service is configured. This is a key variable. Triggers: Is updated when an IPSG service is configured. Availability: Per IPSG service. | String
> vpnid | Description: Identification number of the VPN context in which the IPSG service is configured. This is a key variable. Triggers: Is updated when an IPSG service is configured. Availability: Per IPSG service. | Int32
> servname | Description: Name of the IPSG service. This is a key variable. Triggers: Is updated when an IPSG service is configured. Availability: Per IPSG service. | String
> servid | Description: Identification number of the service configured on the system that is currently facilitating the IPSG service. This is an internal reference number. This is a key variable. Triggers: Is updated when an IPSG service is configured. Availability: Per IPSG service. | Int32
> total-start-req-rcv | Description: Total number of accounting start requests received by the IPSG service. Triggers: Increments when an accounting start message is sent from RADIUS client to IPSG. Availability: Per IPSG service. | Int32
> total-start-req-retrans-rcv | Description: Total number of accounting start request retransmissions received by the IPSG service. Triggers: Increments when a retransmitted accounting start message is received. Availability: Per IPSG service. | Int32
> total-start-rsp-sent | Description: Total number of start responses sent by the IPSG service. Triggers: Increments when an accounting response is received by IPSG. Availability: Per IPSG service. | Int32
> total-interim-update-req-rcv | Description: Total number of interim update requests received by the IPSG service. Triggers: Increments when an interim message is received after call is up. Availability: Per IPSG service. | Int32
> total-stop-req-rcv | Description: Total number of stop requests received by the IPSG service. Triggers: Increments when an accounting stop request is received. Availability: Per IPSG service. | Int32
> total-unknown-req-rcv | Description: Total number of unknown requests received by the IPSG service. Triggers: Increments when an accounting message has unknown request. Availability: Per IPSG service. | Int32
> total-rsp-sent | Description: Total number of responses sent by the IPSG service. Triggers: Increments with every response sent (auth response + accounting response + other messages). Availability: Per IPSG service. | Int32
> total-discard-msgs-unknown-clnt | Description: Total number of messages discarded by IPSG since they were received from an unknown client. Triggers: Increments if, in accounting messages the IP address does not match the current subscriber. Availability: Per IPSG service. | Int32
> total-discard-msgs-ignore-interim | Description: Total number of RADIUS-Accounting-Interim messages ignored by IPSG since they were received for non-existing sessions. Triggers: Increments on receiving RADIUS-Accounting-Interim messages for non-existing session. Availability: Per IPSG service. | Int32
> total-discard-msgs-ignore-stop | Description: Total number of RADIUS-Accounting-Stop messages ignored by IPSG since they were received for non-existing sessions. Triggers: Increments on receiving RADIUS Accounting Stop messages for non-existing session. Availability: Per IPSG service. | Int32
> total-discard-msgs-incorrect-secret | Description: Total number of messages discarded by IPSG due to an incorrect secret. Triggers: Increments on mismatch of shared secrets between RADIUS client / IPSG and IPSG / RADIUS server. Availability: Per IPSG service. | Int32
> total-discard-msgs-attr-missing | Description: Total number of messages discarded by IPSG due to a missing attribute. Triggers: Increments if a RADIUS packet does not have the needed attributes. Availability: Per IPSG service. | Int32
> rad-servaddr | Description: IP address of the RADIUS server supporting the service. Triggers: Is updated when a RADIUS server is configured. Availability: Per IPSG service. | String
> rad-servport | Description: Port number of the RADIUS server supporting the service. Triggers: Is updated when a RADIUS server is configured. Availability: Per IPSG service. | Int32
> Important: For information on statistics that are common to all schemas see the Statistics and Counters Overview chapter.

> ‌

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