The PCC-Sp-Endpoint
schema provides operational statistics that can be used for monitoring
and troubleshooting the following products from StarOS Release 12.1
onward: IPCF.
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 PCC-Sp-Endpoint Schema
| Variables | Description | Data Type |
|---|---|---|
|
vpnname
|
The name of the context
in which PCC-Sp-Endpoint is configured.
This is a key variable.
|
String
|
|
vpnid
|
The identity number of
the context in which PCC-Sp-Endpoint is configured.
This is a key variable.
|
String
|
|
endpt-name
|
The name of the PCC-Sp-Endpoint
instance for which statistics are collected or displayed.
This is a key variable.
|
String
|
|
req-open
|
Indicates total number
of SPRMgr Sh session Create requests received from PCCMgr.
Trigger: When SPRMgr
receives a first GET profile request for a session.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
req-close
|
Indicates total number
of SPRMgr Sh session Close requests received from PCCMgr.
Trigger: When SPRMgr
receives the last notification de-registration request or session
close request.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
req-update-profile
|
Indicates total number
of requests received from PCCMgr to send PUR to SSC.
Trigger: When SPRMgr
gets a request from PCCMgr to send PUR to SSC.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
req-update-profile-answer
|
Indicates total number
of PUA received from SSC.
Trigger: When SPRMgr
receives a PUA message from SSC.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
req-user-data-req
|
Indicates total number
of requests received from PCCMgr to send UDR to SSC.
Trigger: When SPRMgr
gets a request from PCCMgr to send UDR to SSC.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
req-user-data-answer
|
Indicates total number
of UDA received from SSC.
Trigger: When SPRMgr
receives a UDA message from SSC.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
req-push-notif-req
|
Indicates total number
of PNRs received.
Trigger: When IPCF receives
a PNR message from SSC.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
req-push-notif-answer
|
Indicates total number
of PNA received from PCCMgr.
Trigger: After successful
parsing of PNR message and before sending the PNA message out.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
req-subscr-notif-req
|
Indicates total number
of requests received from PCCMgr to send PNR to SSC.
Trigger: When IPCF receives
a SNR message from SSC.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
req-subscr-notif-answer
|
Indicates total number
of SNAs sent.
Trigger: When SPRMgr
receives a SNA message from SSC.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
success-open
|
Indicates total number
of SPRMgr Sh sessions successfully created.
Trigger: When SPRMgr
has successfully created a Sh session.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
success-close
|
Indicates total number
of SPRMgr Sh sessions successfully closed.
Trigger: When SPRMgr
has successfully closed a Sh session.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
success-update-profile
|
Indicates total number
of PUR successfully sent to SSC.
Trigger: When a PUR message
is successfully sent from IPCF to SSC.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
success-update-profile-answer
|
Indicates total number
of PUA successfully parsed and their data sent to PCCMgr.
Trigger: When the PUA
message received from SSC is successfully parsed.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
success-user-data-req
|
Indicates total number
of UDR successfully sent to SSC.
Trigger: When a UDR message
is successfully sent from IPCF to SSC.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
success-user-data-answer
|
Indicates total number
of UDA successfully parsed and their data sent to PCCMgr.
Trigger: When the UDA
message received from SSC is successfully parsed.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
success-push-notif-req
|
Indicates total number
of PNR successfully sent to SSC.
Trigger: When the PNR
message received from SSC is successfully parsed.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
success-push-notif-answer
|
Indicates total number
of PNA successfully parsed and their data sent to PCCMgr.
Trigger: When a PNA message
is successfully sent from IPCF to SSC.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
success-subscr-notif-req
|
Indicates total number
of SNR successfully sent to SSC.
Trigger: When a SNR message
is successfully sent from IPCF to SSC.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
success-subscr-notif-answer
|
Indicates total number
of SNA successfully parsed and their data sent to PCCMgr.
Trigger: When the SNA
message received from SSC is successfully parsed.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
error-open
|
Indicates total number
of SPRMgr Sh session create failures.
Trigger: When SPRMgr
session creation fails.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
error-close
|
Indicates total number
of SPRMgr Sh session close failures.
Trigger: When SPRMgr
session close fails.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
error-update-profile
|
Indicates total number
of errors occurred while sending PUR.
Trigger: When an error
occurs while sending PUR message to SSC.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
error-update-profile-answer
|
Indicates total number
of errors occurred while processing PUA.
Trigger: When an error
occurs while processing PUA message received from SSC.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
error-user-data-req
|
Indicates total number
of errors occurred while sending UDR.
Trigger: When an error
occurs while sending UDR message to SSC.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
error-user-data-answer
|
Indicates total number
of errors occurred while processing UDA.
Trigger: When an error
occurs while processing UDA message received from SSC.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
error-push-notif-req
|
Indicates total number
of errors occurred while processing PNR.
Trigger: When an error
occurs while processing PNR message received from SSC.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
error-push-notif-answer
|
Indicates total number
of errors occurred while sending PNA.
Trigger: When an error
occurs while sending PNA message to SSC.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
error-subscr-notif-req
|
Indicates total number
of errors occurred while sending SNR.
Trigger: When an error
occurs while sending SNR message to SSC.
Availability: Across
all PCC SP Endpoints.
|
Unsigned Int32
|
|
error-subscr-notif-answer
|
Indicates total number
of errors occurred while processing SNA.
Trigger: When an error
occurs while processing SNA message received from SSC.
Availability: Across
all PCC SP Endpoints
|
Unsigned Int32
|
|
|
||