# IPSG Schema Statistics

The IPSG schema provides operational statistics that can be used for monitoring and troubleshooting the following products: eWAG, 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.
Table 1. 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. Type: Information. | 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. Type: Information. | 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. Type: Information. | 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. Type: Information. | Int32
total-start-req-rcv | Description: The 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. Type: Counter. | Int32
total-start-req-retrans-rcv | Description: The total number of accounting start request retransmissions received by the IPSG service. Triggers: Increments when a retransmitted Accounting-Start message is received. If Accounting-Start message comes again matching an established session with same IP address, Username+MSISDN, APN, NAS-IP-Address, Accounting-Session-ID, and Source-IP address of the IP packet, it is treated as retransmission. Availability: Per IPSG service. Type: Counter. | Int32
total-start-rsp-sent | Description: The total number of start responses sent by the IPSG service. Triggers: Increments when an accounting response is sent for Accounting-Start received by IPSG. Availability: Per IPSG service. Type: Counter. | Int32
total-interim-update-req-rcv | Description: The 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. Type: Counter. | Int32
total-stop-req-rcv | Description: The total number of stop requests received by the IPSG service. Triggers: Increments when an Accounting-Stop request is received. Availability: Per IPSG service. Type: Counter. | Int32
total-unknown-req-rcv | Description: The total number of unknown requests received by the IPSG service. Triggers: Increments when an accounting message has unknown request. Valid RADIUS requests are Accounting-Start, Accounting-Interim, Accounting-Stop, Accounting-On, Accounting-Off, Access Request. For all other RADIUS messages unknown req will be updated. For eWAG, everything that is not expected to be processed is considered as unknown request. For example, disconnect, status, coa, any other accounting status type, accounting response. Availability: Per IPSG service. Type: Counter. | Int32
total-rsp-sent | Description: The 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. Type: Counter. | Int32
total-discard-msgs-unknown-clnt | Description: The 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 RADIUS client subscriber. RADIUS client subscribers are configured in IPSG service. Availability: Per IPSG service. Type: Counter. | Int32
total-discard-msgs-ignore-interim | Description: The 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. If session creation based on Accounting-Interim is supported then this counter will never increment. Availability: Per IPSG service. Type: Counter. | Int32
total-discard-msgs-ignore-stop | Description: The 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. Type: Counter. | Int32
total-discard-msgs-incorrect-secret | Description: The 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. Type: Counter. | Int32
total-discard-msgs-attr-missing | Description: The 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. Type: Counter. | 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. Type: Information. | 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. Type: Information. | Int32
total-sessions-attempt | Description: The number of IPSG calls attempted on IPSG service. Triggers: Increments when an IPSG call arrives. Availability: Per IPSG service. Type: Counter. | Int32
total-current-sessions | Description: The total number of IPSG calls currently active on IPSG service. Triggers: Increments when an IPSG call comes up. Decrements when an IPSG call ends. Availability: Per IPSG service. Type: Gauge. | Int32
total-sessions-setup | Description: The total number of calls setup on IPSG service. Triggers: Increments when an IPSG call is connected. Availability: Per IPSG service. Type: Counter. | Int32
total-sessions-replaced | Description: The total number of calls replaced by IPSG service. Triggers: Increments when an IPSG call is replaced. Availability: Per IPSG service. Type: Counter. | Int32
total-sessions-released | Description: The total number of IPSG calls released by IPSG service. Triggers: Increments when an IPSG call is released. Availability: Per IPSG service. Type: Counter. | Int32
total-interim-update-rsp-sent | Description: The total number of interim update response sent by the IPSG service. Triggers: Increments when an accounting response is sent for interim request received. Availability: Per IPSG service. Type: Counter. | Int32
total-stop-rsp-sent | Description: The total number of stop response sent by the IPSG service. Triggers: Increments when an Accounting-Response is sent for Accounting-Stop received. Availability: Per IPSG service. Type: Counter. | Int32
total-access-req-rcv | Description: The total number of Access-Requests received by the IPSG service. For eWAG service this will always be 0. If Access-Request is received it is discarded as service not supported. Triggers: Increments on receiving an Access-Request. Availability: Per IPSG service. Type: Counter. | Int32
total-access-req-retrans-rcv | Description: The total number of Access-Request retransmissions received by the IPSG service. For eWAG this will always be 0. Triggers: Increments when a retransmitted Access-Request message is received. Availability: Per IPSG service. Type: Counter. | Int32
total-access-accept-sent | Description: The total number of Access-Accept sent by the IPSG service. For eWAG this will always be 0. Triggers: Increments when an Access-Accept is sent. Availability: Per IPSG service. Type: Counter. | Int32
total-access-reject-sent | Description: The total number of access reject sent by the IPSG service. For eWAG this will always be 0. Triggers: Increments when an Access-Reject is sent. Availability: Per IPSG service. Type: Counter. | Int32
total-disconnect-msg-sent | Description: The total number of disconnect message sent by IPSG service. Triggers: Increments when a disconnect message is sent. Availability: Per IPSG service. Type: Counter. | Int32
total-discarded | Description: The total number of IPSG calls rejected by IPSG service. It is the sum of all IPSG RADIUS message disconnect reasons. Triggers: Increments when an IPSG call is rejected. Availability: Per IPSG service. Type: Counter. | Int32
total-discard-msgs-no-resource | Description: The total number of messages discarded by IPSG service due to no resource. Triggers: Increments when RADIUS message is discarded due to reasons including no resource, CPC failure, and invalid NAT scenarios. Availability: Per IPSG service. Type: Counter. | Int32
total-discard-msgs-ignore-start | Description: The total number of RADIUS-Accounting-start messages ignored by IPSG since they were received for non-existing sessions. Applicable in IPSG RADIUS Proxy Mode where Access-Request will trigger session creation and then Accounting-Start is expected. Not applicable to eWAG service. For eWAG, it will always be 0. Triggers: Increments on receiving RADIUS Accounting-Start messages for non-existing session. Availability: Per IPSG service. Type: Counter. | Int32
total-discard-msgs-stale-packets | Description: The total number of messages discarded by IPSG as they are stale. Triggers: Increments when a stale packet is received (event timestamp mismatch). Availability: Per IPSG service. Type: Counter. | Int32
total-discard-msgs-svc-not-supported | Description: The total number of messages discarded by IPSG if service is not supported. Triggers: Increments when Access-Request is received for non RADIUS Proxy Mode. For example, if Access-Request is received eWAG mode will increment svc-not-supported. Availability: Per IPSG service. Type: Counter. | Int32
total-discard-msgs-internal-error | Description: The total number of messages discarded by IPSG due to internal errors. For example, when Demux fails to send notification to SessMgr. Unexpected internal scenarios. Triggers: Increments when RADIUS message is discarded due to an internal error. Availability: Per IPSG service. Type: Counter. | Int32
total-discard-msgs-svc-limit-exceeded | Description: The total number of messages discarded by IPSG due to service limit for maximum sessions being exceeded. Triggers: Increments on receiving RADIUS message that triggers new session creation and service limit for maximum sessions is exceeded. Availability: Per IPSG service. Type: Counter. | Int32
total-discard-msgs-license-limit-exceeded | Description: The total number of messages discarded by IPSG due to license limit being exceeded. Triggers: Increments on receiving RADIUS message that triggers new session creation and license limit is exceeded. Availability: Per IPSG service. Type: Counter. | Int32
total-discard-msgs-congestion-policy-applied | Description: The total number of messages discarded by IPSG due to congestion policy. Triggers: Increments on receiving RADIUS message that triggers new session creation and congestion policy is applied. Availability: Per IPSG service. Type: Counter. | Int32
IMPORTANT: For information on statistics that are common to all schemas see the Statistics and Counters Overview chapter.