The CS-Network-SCCP
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:
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 CS-Network-SCCP Schema
| Variables | Description | Data Type |
|---|---|---|
|
nwname
|
Indicates the name of
the Circuit Switch (CS) Network connected with specific HNB-GW of
which statistics are collected or displayed.
This is a key variable.
|
String
|
|
dest-pt-code
|
Indicates the destination
point code in SS7 notation of MSC in core network connected with
specific HNB-GW of which statistics are collected or displayed.
This is a key variable.
|
String
|
|
sccp-conn-req-rx
|
Indicates the total
number of SCCP connection Request received by HNB-GW from the Core
Node.
Trigger: When Core Node
initiates SCCP connection during Relocation.
Availability: Per CS
Networks.
|
Unsigned Int32
|
|
sccp-conn-req-tx
|
Indicates the total
number of SCCP connection Request sent by HNB-GW towards the CN
after getting RUA Connect Request for a Registered UE.
Trigger: When RUA Connect
Request sent for a Registered UE.
Availability: Per CS
Networks.
|
Unsigned Int32
|
|
sccp-conn-cfm-rx
|
Indicates the total
number of SCCP Connection Confirmation messages received by HNB-GW
from the Core Node.
Trigger: When CN sends
the SCCP connection confirmation for a requested SCCP Connection
Request.
Availability: Per CS
Networks.
|
Unsigned Int32
|
|
sccp-conn-cfm-tx
|
Indicates the total
number of SCCP Connection Confirmation response messages sent by
HNB-GW to the Core Node.
Trigger: When HNB-GW
sends the SCCP connection confirmation response for a requested
SCCP Connection Request to CN.
Availability: Per CS
Networks.
|
Unsigned Int32
|
|
sccp-conn-rej-rx
|
Indicates the total
number of SCCP Connection Reject messages received by HNB-GW from
the Core Node.
Trigger: When Core node
Rejects the SCCP Conn Request due to some parameter mismatch, etc.
Availability: Per CS
Networks.
|
Unsigned Int32
|
|
sccp-conn-rej-tx
|
Indicates the total
number of SCCP Connection Rejection response messages sent by HNB-GW
to the Core Node.
Trigger: When HNBGW
initiates the tear Down on receiving RUA disconnect from HNB which
doesn't contain RANAP Iu-release complete message and other failure
scenarios.
Availability: Per CS
Networks.
|
Unsigned Int32
|
|
sccp-con-data-rx
|
Indicates the total
data received by HNB-GW over SCCP connection between HNB-GW and
Core Node.
Trigger: When CN sends
the data towards HNB-GW over SCCP connection.
Availability: Per CS
Networks.
|
Unsigned Int32
|
|
sccp-con-data-tx
|
Indicates the total
data sent by HNB-GW over SCCP connection between HNB-GW and Core
Node.
Trigger: When HNB-GW
sends the data towards CN over SCCP connection.
Availability: Per CS
Networks.
|
Unsigned Int32
|
|
sccp-disconnect-rx
|
Indicates the total
number of SCCP Disconnect messages received by HNB-GW from Core
Node.
Trigger: When CN initiate
tear-down procedure for SCCP connection.
Availability: Per CS
Networks.
|
Unsigned Int32
|
|
sccp-disconnect-tx
|
Indicates the total
number of SCCP Disconnect response messages sent by HNB-GW to Core
Node.
Trigger: When HNBGW
initiates the tear-down procedure on receiving RUA disconnect from
HNB which doesn't contain RANAP Iu-release complete message and
other failure scenarios.
Availability: Per CS
Networks.
|
Unsigned Int32
|
|
sccp-uni-data-rx
|
Indicates the total
Connection-less data, like paging, received by HNB-GW over SCCP
connection between HNB-GW and Core Node.
Trigger: When CN sends
any connection-less data, like paging, towards HNB-GW over SCCP
connection.
Availability: Per CS
Networks.
|
Unsigned Int32
|
|
sccp-uni-data-tx
|
Indicates the total
Connection-less data, RANAP Reset, RANAP reset Resource, sent by
HNB-GW over SCCP connection between HNB-GW and Core Node.
Trigger: When HNB-GW
sends or forward any Connection-less data, like RANAP reset, RANAP
Reset Resource, towards CN over SCCP connection.
Availability: Per CS
Networks.
|
Unsigned Int32
|
|
|
||