Cisco Cisco Packet Data Gateway (PDG)

Página de 4778
 
Statistics and Counters Reference, StarOS Release 18   ▄  
 
   
2781 
Chapter 115    
TAI Schema Statistics 
 
The TAI (Tracking Area Identifier) schema provides operational statistics that can be used for monitoring and 
troubleshooting the following products: MME  
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 the 
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 includes decimal points; 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. 
Important:
  The statistics provided in the TAI schema are collected per TAI. Refer to the MME Service 
command: 
statistics collection-mode { enodeb | tai }
 in the Command Line Interface Reference for 
more information or to configure these statistics to be collected per TAI. 
Important:
  The MME will collect these statistics only for TAIs that are configured in a LTE TAI Management 
Database that has been associated with the MME Service.