AAL2 Schema Statistics

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


Table 1. Bulk Statistic Variables in the AAL2 Schema
Variables Description Data Type

vpnname

The name of the context in which AAL2 service is configured.

This is a key variable.

String

vpnid

The identity number of the context in which AAL2 service is configured.

This is a key variable.

String

servname

The name of the AAL2 service for which statistics are collected or displayed.

This is a key variable.

String

uplink-pkts-tx

Indicates the total number of AAL2 Uplink Packets transmitted.

Trigger: When AAL2 Uplink Packets are transmitted by ALCAP Service.

Availability: Across all ALCAP Services.

Unsigned Int32

uplink-byts-tx

Indicates the total number of AAL2 Uplink Bytes transmitted.

Trigger: When AAL2 Uplink Bytes are transmitted by ALCAP Service.

Availability: Across all ALCAP Services.

Unsigned Int32

downlink-pkts-rx

Indicates the total number of AAL2 Downlink Packets received.

Trigger: When AAL2 Downlink Packets are received by ALCAP Service.

Availability: Across all ALCAP Services.

Unsigned Int32

downlink-byts-rx

Indicates the total number of AAL2 Downlink Bytes received.

Trigger: When AAL2 Downlink Bytes are received by ALCAP Service.

Availability: Across all ALCAP Services.

Unsigned Int32

downlink-pkts-dropped

Indicates the total number of AAL2 Downlink packets dropped.

Trigger: When AAL2 Downlink packets are dropped by ALCAP Service.

Availability: Across all ALCAP Services.

Unsigned Int32

downlink-pkts-drop-rab-not-in-conn-state

Indicates the total number of AAL2 Downlink Packets dropped with cause RAB not in CONNETED state.

Trigger: When AAL2 Downlink Packets are dropped by ALCAP Service with cause RAB not in CONNETED state.

Availability: Across all ALCAP Services.

Unsigned Int32

downlink-pkts-drop-cause-misc

Indicates the total number of AAL2 Downlink Packets dropped with cause Miscellaneous.

Trigger: When AAL2 Downlink Packets are dropped by ALCAP Service with cause Miscellaneous.

Availability: Across all ALCAP Services.

Unsigned Int32

downlink-byts-dropped

Indicates the total number of AAL2 Downlink bytes dropped.

Trigger: When AAL2 Downlink bytes are dropped by ALCAP Service.

Availability: Across all ALCAP Services.

Unsigned Int32

downlink-byts-drop-rab-not-in-conn-state

Indicates the total number of AAL2 Downlink bytes dropped with cause RAB not in CONNETED state.

Trigger: When AAL2 Downlink bytes are dropped by ALCAP Service with cause RAB not in CONNETED state.

Availability: Across all ALCAP Services.

Unsigned Int32

downlink-byts-drop-cause-misc

Indicates the total number of AAL2 Downlink bytes dropped with cause Miscellaneous.

Trigger: When AAL2 Downlink Bytes are dropped by ALCAP Service with cause Miscellaneous.

Availability: Across all ALCAP Services.

Unsigned Int32

IMPORTANT:

For information on statistics that are common to all schema see the Statistics and Counters Overview chapter.