NAT Realm Schema Statistics

The NAT Realm schema provides operational statistics that can be used for monitoring and troubleshooting the following products: NAT in-line service, 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.


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

vpnname

Name of the VPN context.

This is a key variable.

Type: Information

String

realmname

Name of the realm. Collected per context per realm.

This is a key variable.

Type: Information

String

nat-bind-updates

Description: Total binding updates sent to AAA. Collected per context per realm.

Triggers: Increments when the port chunk allocates or deallocates, and an update is sent to AAA.

Availability: Per Active Charging Service.

Int32

nat-rlm-bytes-tx

Description: Total number of bytes transferred by realm. Collected per context per realm.

Triggers: Increments when the packets are transmitted using this NAT realm.

Availability: Per Active Charging Service.

Int32

nat-rlm-flows

Description: Total number of flows used by realm. Collected per context per realm.

Triggers: Increments when the new flows use this NAT realm.

Availability: Per Active Charging Service.

Int32

nat-rlm-ip-denied

Description: Total number of flows denied IP. Collected per context per realm.

Triggers: Increments when the new NAT IP is not available for translation to new flows.

Availability: Per Active Charging Service.

Int32

nat-rlm-port-denied

Description: Total number of flows denied ports. Collected per context per realm.

Triggers: Increments when the new NAT port is not available for translation to new flows.

Availability: Per Active Charging Service.

Int32

nat-rlm-ttl-ips

Description: Total number of NAT public IP addresses. Collected per context per realm.

Availability: Per Active Charging Service.

Type: Gauge

Int32

nat-rlm-ips-in-use

Description: Total number of NAT public IP addresses currently in use. Collected per context.

Triggers: Increments when a new NAT IP address is used by any subscriber.

Availability: Per Active Charging Service.

Type: Gauge

Int32

nat-rlm-current-users

Description: Total number of current users using a NAT realm. Collected per context per realm.

Triggers: Increments when a new subscriber uses the NAT IP from this realm and decrements on releasing the NAT IP address.

Availability: Per Active Charging Service.

Type: Gauge

Int32

nat-rlm-ttl-port-chunks

Description: Total number of port chunks. Collected per context per realm.

Availability: Per Active Charging Service.

Type: Gauge

Int32

nat-rlm-chunks-in-use

Description: Total number of port chunks currently in use. Collected per context per realm.

Triggers: Increments when a new flow takes new port chunk and decrements on releasing the chunk.

Availability: Per Active Charging Service.

Type: Gauge

Int32

nat-rlm-port-chunk-size

Description: The size of the port chunk in the NAT realm. This is a snapshot statistic.

Availability: Per Active Charging Service.

Type: Gauge

Int32

nat-rlm-port-chunk-average-usage-tcp

Description: The average TCP port usage in the allocated TCP ports, i.e out of allocated TCP ports how many got used. This is not a percentage value. This is a snapshot statistic.

Triggers: Increments during TCP flows creation and existing network conditions.

Availability: Per Active Charging Service.

Type: Gauge

Int32

nat-rlm-port-chunk-average-usage-udp

Description: The average UDP port usage in the allocated UDP ports, i.e out of allocated UDP ports how many got used. This is not a percentage value. This is a snapshot statistic.

Triggers: Increments during UDP flows creation and existing network conditions.

Availability: Per Active Charging Service.

Type: Gauge

Int32

nat-rlm-port-chunk-average-usage-others

Description: The average Others (ICMP or GRE) port usage in the allocated others ports, i.e out of allocated ‘Others’ ports how many got used. This is not a percentage value. This is a snapshot statistic.

Triggers: Increments during ICMP or GRE flows creation and existing network conditions.

Availability: Per Active Charging Service.

Type: Gauge

Int32

nat-rlm-max-port-chunk-subs

Description: Total number of subscribers who have used maximum number of port chunks. This is a cumulative statistic.

Triggers: Increments when any subscriber uses maximum number of port chunks.

Availability: Per Active Charging Service.

Int64

nat-rlm-max-port-chunk-used

Description: The maximum number of port chunks used by any subscriber. This is a cumulative statistic.

Triggers: Increments when any subscriber uses new maximum number of port chunks.

Availability: Per Active Charging Service.

Int32

nat-rlm-max-cur-port-chunk-subs

Description: Total number of current subscribers using maximum number of port chunks. This is a snapshot statistic.

Triggers: Increments when the active subscriber uses maximum number of port chunks.

Availability: Per Active Charging Service.

Type: Gauge

Int64

nat-rlm-max-cur-port-chunk-used

Description: The maximum number of port chunks currently used by any subscriber. This is a snapshot statistic.

Triggers: Increments when the active subscriber uses new maximum number of port chunks.

Availability: Per Active Charging Service.

Type: Gauge

Int32

IMPORTANT:

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