The P2P schema provides
operational statistics that can be used for monitoring and troubleshooting
the following products: ADC in-line service
IMPORTANT:
In StarOS 14.0 and later releases,
the P2P Schema is new. If detection of a specific P2P protocol is
enabled, bulk statistics for that protocol will be automatically
generated using the Dynamic Software Upgrade plugin installed on
the chassis. In the case of protocols that support sub-classification
(audio/video/unclassified), the bulk statistics
will be generated for each of the supported sub-classifications
per protocol and also the corresponding cumulative count.
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:
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 P2P Schema
| Variables | Description | Data Type |
|---|---|---|
|
p2p-protocol
|
Description: The
name of the specific P2P protocol.
Availability: Per
Active Charging Service
Type: Information
|
String
|
|
p2p-duration-name
|
Description: The
name of the specific protocol for which the total duration is generated.
Availability: Per
Active Charging Service
|
String
|
|
p2p-duration-value
|
Description: The
total duration of a specific protocol at a given instance in time.
Triggers: Increments
whenever a detected flow for a specific protocol ends the conversation.
Availability: Per
Active Charging Service
|
Int64
|
|
p2p-uplnk-bytes-name
|
Description: The
name of the specific protocol for which the total number of bytes
detected in uplink direction (received from MS) is generated.
Availability: Per
Active Charging Service
|
String
|
|
p2p-uplnk-bytes-value
|
Description: The
number of bytes of traffic detected in uplink direction for a specific
protocol.
Triggers: Increments
when a packet of traffic for a specific protocol is detected by
the P2P analyzer.
Availability: Per
Active Charging Service
|
Int64
|
|
p2p-dwlnk-bytes-name
|
Description: The
name of the specific protocol for which the total number of bytes
detected in downlink direction (sent to MS) is generated.
Availability: Per
Active Charging Service
|
String
|
|
p2p-dwlnk-bytes-value
|
Description: The
number of bytes of traffic detected in downlink direction for a
specific protocol.
Triggers: Increments
when a packet of traffic for a specific protocol is detected by
the P2P analyzer.
Availability: Per
Active Charging Service
|
Int64
|
|
p2p-uplnk-pkts-name
|
Description: The
name of the specific protocol for which the total number of packets
detected in uplink direction is generated.
Availability: Per
Active Charging Service
|
String
|
|
p2p-uplnk-pkts-value
|
Description: The
number of bytes of traffic detected in uplink direction for a specific
protocol.
Triggers: Increments
when a packet of traffic for a specific protocol is detected by
the P2P analyzer.
Availability: Per
Active Charging Service
|
Int64
|
|
p2p-dwlnk-pkts-name
|
Description: The
name of the specific protocol for which the total number of packets
detected in downlink direction is generated.
Availability: Per
Active Charging Service
|
String
|
|
p2p-dwlnk-pkts-value
|
Description: The
number of bytes of traffic detected in downlink direction for a
specific protocol.
Triggers: Increments
when a packet of traffic for a specific protocol is detected by
the P2P analyzer.
Availability: Per
Active Charging Service
|
Int64
|
|
|
||