SCCP:Error Performance Report
From TBwiki
(Difference between revisions)
(→Description of parameters: clean up) |
(clean up) |
||
Line 1: | Line 1: | ||
The performance report error (event) notification message is received by the host application when a SCCP is reporting a performance error. | The performance report error (event) notification message is received by the host application when a SCCP is reporting a performance error. | ||
− | General explanation of the | + | General explanation of the error event notification fields in the performance report: |
*The '''SCCP handle field''' specifies the handle of the SCCP instance. | *The '''SCCP handle field''' specifies the handle of the SCCP instance. | ||
Line 12: | Line 12: | ||
{| class="wikitable" border="1" | {| class="wikitable" border="1" | ||
− | |+ SCCP event and cause LSAP alarm under CATEGORY_PROTOCOL | + | |+ '''SCCP event and cause LSAP alarm under CATEGORY_PROTOCOL''' |
! width="150" style="background:#efefef;" |Cause | ! width="150" style="background:#efefef;" |Cause | ||
! width="200" style="background:#efefef;" |Report parameters used | ! width="200" style="background:#efefef;" |Report parameters used | ||
! width="200" style="background:#efefef;" |Description | ! width="200" style="background:#efefef;" |Description | ||
|- | |- | ||
− | | | + | | Unknown || None|| Unknown |
|- | |- | ||
− | | | + | | No Translation - bad address (RTF_NTBADADDR)|| |
+ | *un32NetworkId | ||
+ | *ProtocolVariant | ||
+ | *Called Address | ||
+ | *Calling Address | ||
+ | ||Routing failure - No translation for address of such nature | ||
|- | |- | ||
− | | | + | | No translation - specific address (RTF_NTSPECADDR)|| |
+ | *un32NetworkId | ||
+ | *Protocol Variant | ||
+ | *Called Address | ||
+ | *Calling Address | ||
+ | ||Routing failure - No translation for this specific address | ||
|- | |- | ||
− | | | + | | Network failure (RTF_NETWORK_FAIL)|| |
+ | *un32NetworkId | ||
+ | *ProtocolVariant | ||
+ | *Calling Address | ||
+ | ||Routing failure - Network failure (point code not available) | ||
|- | |- | ||
− | | | + | | Network congestion (RTF_NETWORK_CONGESTION)|| |
+ | *un32NetworkId | ||
+ | *ProtocolVariant | ||
+ | *DPC | ||
+ | *Calling Address | ||
+ | || Routing failure - Network congestion | ||
+ | |- | ||
+ | |Subsystem failure (RTF_SUBSYSTEM_FAILURE)|| | ||
+ | *un32NetworkId | ||
+ | *ProtocolVariant | ||
+ | ||Routing failure - Subsystem failure (unavailable) | ||
+ | |- | ||
+ | |System congestion (RTF_SUBSYSTEM_CONGESTION)|| | ||
+ | *un32NetworkId | ||
+ | *ProtocolVariant | ||
+ | *Calling Address | ||
+ | ||Routing failure - Subsystem congestion | ||
+ | |- | ||
+ | |Routing failure - unequipped user (RTF_UNEQUIPPED)|| | ||
+ | *un32NetworkId | ||
+ | *ProtocolVariant | ||
+ | ||Routing failure - Unequipped user (subsystem). | ||
+ | |- | ||
+ | |Reassembly outside of sequence (REASSEMBLY_OUTSEQ)|| | ||
+ | *un32NetworkId | ||
+ | *ProtocolVariant | ||
+ | *Calling Address | ||
+ | *un32CongestionLvl | ||
+ | ||Reassembly error - Segment received out of sequence | ||
+ | |- | ||
+ | | Hop violation (HOP_VIOLATION)|| | ||
+ | *un32NetworkId | ||
+ | *ProtocolVariant | ||
+ | *Called Address | ||
+ | *Calling Address | ||
+ | ||Hop counter violation (XUDT(S) / LUDT(S)) | ||
+ | |- | ||
+ | |Segment failure - too large (SEGFAIL_TOO_LARGE)|| | ||
+ | *un32NetworkId | ||
+ | *ProtocolVariant | ||
+ | ||Message too large for segmentation | ||
+ | |- | ||
+ | |Subsystem congested received (SSC_RECV)|| | ||
+ | *un32NetworkId | ||
+ | *ProtocolVariant | ||
+ | *DPC | ||
+ | *un32CongestionLvl | ||
+ | ||SCCP / Subsystem congested message received. | ||
+ | |- | ||
+ | |Subsystem prohibited received (SSP_RECV)|| | ||
+ | *un32NetworkId | ||
+ | *ProtocolVariant | ||
+ | *DPC | ||
+ | *un32SSN | ||
+ | ||Subsystem prohibited message received | ||
|} | |} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Revision as of 10:40, 8 September 2009
The performance report error (event) notification message is received by the host application when a SCCP is reporting a performance error.
General explanation of the error event notification fields in the performance report:
- The SCCP handle field specifies the handle of the SCCP instance.
- The Cause field specifies the cause of the error performance report.
Cause | Report parameters used | Description |
---|---|---|
Unknown | None | Unknown |
No Translation - bad address (RTF_NTBADADDR) |
|
Routing failure - No translation for address of such nature |
No translation - specific address (RTF_NTSPECADDR) |
|
Routing failure - No translation for this specific address |
Network failure (RTF_NETWORK_FAIL) |
|
Routing failure - Network failure (point code not available) |
Network congestion (RTF_NETWORK_CONGESTION) |
|
Routing failure - Network congestion |
Subsystem failure (RTF_SUBSYSTEM_FAILURE) |
|
Routing failure - Subsystem failure (unavailable) |
System congestion (RTF_SUBSYSTEM_CONGESTION) |
|
Routing failure - Subsystem congestion |
Routing failure - unequipped user (RTF_UNEQUIPPED) |
|
Routing failure - Unequipped user (subsystem). |
Reassembly outside of sequence (REASSEMBLY_OUTSEQ) |
|
Reassembly error - Segment received out of sequence |
Hop violation (HOP_VIOLATION) |
|
Hop counter violation (XUDT(S) / LUDT(S)) |
Segment failure - too large (SEGFAIL_TOO_LARGE) |
|
Message too large for segmentation |
Subsystem congested received (SSC_RECV) |
|
SCCP / Subsystem congested message received. |
Subsystem prohibited received (SSP_RECV) |
|
Subsystem prohibited message received |
Description of parameters
General explanation of the Report-specific information parameters:
- The Network identifier parameter specifies the ID of the network
- The Called address parameter specifies the called party address. See the Entity explanation in GTT Address Map Configuration
- The Calling address parameter specifies the calling party address. See the Entity explanation in GTT Address Map Configuration
- The Destination point code parameter (DPC) specifies the point code of the node where the route is terminating
- The Protocol variant parameter specifies the SCCP protocol variant. See the SCCP protocol variant table in Toolpack:Create a SSCP network
- The Subsystem number parameter specifies a subsystem number. See the SCCP SSN value to identify SCCP user table in Toolpack:Create a SCCP route.
- The Segmentation reference parameter specifies the SCCP segmentation local reference number
- The Congestion level parameter specifies the remote SCCP congestion level (reception of SSC). Value is in range 0 to 7.