SCCP:General Statistics

From TBwiki
(Difference between revisions)
Jump to: navigation, search
(initial content)
 
(initial content)
Line 14: Line 14:
 
*The 'Prohibited received' counter indicates the number of 'subsystem prohibited' messages received
 
*The 'Prohibited received' counter indicates the number of 'subsystem prohibited' messages received
 
*The 'Unit data transmitted' counter indicates the amount of unit data sent
 
*The 'Unit data transmitted' counter indicates the amount of unit data sent
*The unit data service transmitted counter indicates the amount of unit data service sent
+
*The 'Unit data service transmitted' counter indicates the amount of unit data service sent
*The unit data received counter indicates the amount of unit data received
+
*The 'Unit data received' counter indicates the amount of unit data received
*The unit data service received counter indicates the amount of unit data service received
+
*The 'Unit data service received' counter indicates the amount of unit data service received
*The extended unit data transmitted counter indicates the amount of extended unit data sent
+
*The 'Extended unit data transmitted' counter indicates the amount of extended unit data sent
*The extended unit data service transmitted counter indicates the amount of extended unit data service sent
+
*The 'Extended unit data service transmitted' counter indicates the amount of extended unit data service sent
*The extended unit data received counter indicates the amount of extended unit data received
+
*The 'Extended unit data received' counter indicates the amount of extended unit data received
*The extended unit data service received counter indicates the amount of extended unit data service received
+
*The 'Extended unit data service received' counter indicates the amount of extended unit data service received
*The message handle counter indicates the total number of messages handled
+
*The 'Message handle' counter indicates the total number of messages handled
*The message local counter indicates the total number of messages intended for local subsystems
+
*The 'Message local' counter indicates the total number of messages intended for local subsystems
*The GTT request counter indicates the number of messages requiring global address translation
+
*The 'GTT request' counter indicates the number of messages requiring global address translation
*The message transmitted class 0 counter indicates the number of class 0 messages sent
+
*The 'Message transmitted class 0' counter indicates the number of class 0 messages sent
*The message transmitted class 1 counter indicates the number of class 1 messages sent
+
*The 'Message transmitted class 1' counter indicates the number of class 1 messages sent
*The message received class 0 counter indicates the number of class 0 messages received
+
*The 'Message received class 0' counter indicates the number of class 0 messages received
*The message received class 1 counter indicates the number of class 1 messages received
+
*The 'Message received class 1' counter indicates the number of class 1 messages received
*The long unit data transmitted counter indicates the amount of long unit data sent
+
*The 'Long unit data transmitted' counter indicates the amount of long unit data sent
*The long unit data service transmitted counter indicates the amount of long unit data service sent
+
*The 'Long unit data service transmitted' counter indicates the amount of long unit data service sent
*The long unit data received counter indicates the amount of long unit data received
+
*The 'Long unit data received' counter indicates the amount of long unit data received
 
+
*The 'Long unit data service received' counter indicates the number of long unit data service messages received
 
+
*The 'Segmentation error' counter indicates the number of segmentation errors (message too large for segmentation)
-          The long unit data service received counter (un32LUnitDataSrvRx) indicates the number of long unit data service received.
+
*The 'Segmentation error fail' counter indicates the number of segmentation failed errors (case of LUDT segmentation at interworking node)
 
+
*The 'Reassembly error' counter indicates the number of reassembly out of sequence errors (including duplicate segment and non-first segment)
-          The segmentation error counter (un32SegErr) indicates the number of segmentation errors (message too large for segmentation).
+
*The 'Reassembly error timer expiry' counter indicates the number of reassembly errors timer expiry events
 
+
*The 'Reassembly error no space' counter indicates the number of reassembly errors (no space for reassembly) events
-          The segmentation error fail counter (un32SegErrFail) indicates the number of segmentation failed errors (case of LUDT segmentation at interworking node).
+
*The 'Inactivity timer expire' counter indicates the number of inactivity timer expire events
 
+
*The 'Routing failure invalid INS routing request' counter indicates the number of routing failure invalid INS routing requests
-          The reassembly error counter (un32ReassemErr) indicates the number of reassembly out of sequence errors (including duplicate segment and non-first segment).
+
*The 'Routing failure invalid ISNI routing request' counter indicates the number of routing failure invalid ISNI routing requests
 
+
*The 'Failure ISNI constrained routing' counter indicates the number of failure ISNI constrained routing events
-          The reassembly error timer expiry counter indicates the number of reassembly errors timer expiry.
+
*The 'Failure redundant ISNI routing request' counter indicates the number of failure due to redundant ISNI routing request
 
+
*The 'Failure ISNI network identifier' counter indicates the number of failures in ISNI identification of network
-          The reassembly error no space (un32ReassemErrNoSpc) indicates the number of reassembly errors (no space for reassembly).
+
 
+
-          The inactivity timer expire counter (un32InaTimerExpiry) indicates the number of inactivity timer expire.
+
 
+
-          The routing failure invalid INS routing request counter (un32RtFailInvInsRtReq) indicates the number of routing failure invalid INS routing request.
+
 
+
-          The routing failure invalid ISNI routing request counter (un32RtFailInvIsniRtReq) indicates the number of routing failure invalid ISNI routing request.
+
 
+
-          The failure ISNI constrained routing counter (un32FailIsniConRt) indicates the number of failure ISNI constrained routing.
+
 
+
-          The failure redundant ISNI routing request counter (un32FailRedIsniRtReq) indicates the number of failure due to redundant ISNI routing request.
+
 
+
-          The failure ISNI network identifier counter (un32FailIsniNetId) indicates the number of failure in ISNI identification of network.
+

Revision as of 08:19, 25 August 2009

General explanation of the general layer SCCP statistics parameters:

  • The 'No translation address such nature' counter indicates the number of routing failures because of a no translation for address of such nature
  • The 'No translation specific address' counter indicates the number of routing failures because of a no translation for this specific address
  • The 'Network failure' counter indicates the number of routing failures because of a network failure (point code unavailable)
  • The 'Network congestion counter indicates the number of routing failures because of network congestion
  • The 'Subsystem failure' counter indicates the number of routing failures because of subsystem failure
  • The 'Subsystem congestion counter indicates the number of routing failures because of subsystem congestion
  • The 'Unequipped' counter indicates the number of routing failures because of unequipped user
  • The 'Hop violate' counter indicates the number of routing failures because of hop counter violation
  • The 'Syntax error' counter indicates the number of syntax error
  • The 'Unknown' counter indicates the number of routing failures because of reason unknown
  • The 'Subsystem congestion received' counter indicates the number of SCCP / subsystem congested messages received
  • The 'Prohibited received' counter indicates the number of 'subsystem prohibited' messages received
  • The 'Unit data transmitted' counter indicates the amount of unit data sent
  • The 'Unit data service transmitted' counter indicates the amount of unit data service sent
  • The 'Unit data received' counter indicates the amount of unit data received
  • The 'Unit data service received' counter indicates the amount of unit data service received
  • The 'Extended unit data transmitted' counter indicates the amount of extended unit data sent
  • The 'Extended unit data service transmitted' counter indicates the amount of extended unit data service sent
  • The 'Extended unit data received' counter indicates the amount of extended unit data received
  • The 'Extended unit data service received' counter indicates the amount of extended unit data service received
  • The 'Message handle' counter indicates the total number of messages handled
  • The 'Message local' counter indicates the total number of messages intended for local subsystems
  • The 'GTT request' counter indicates the number of messages requiring global address translation
  • The 'Message transmitted class 0' counter indicates the number of class 0 messages sent
  • The 'Message transmitted class 1' counter indicates the number of class 1 messages sent
  • The 'Message received class 0' counter indicates the number of class 0 messages received
  • The 'Message received class 1' counter indicates the number of class 1 messages received
  • The 'Long unit data transmitted' counter indicates the amount of long unit data sent
  • The 'Long unit data service transmitted' counter indicates the amount of long unit data service sent
  • The 'Long unit data received' counter indicates the amount of long unit data received
  • The 'Long unit data service received' counter indicates the number of long unit data service messages received
  • The 'Segmentation error' counter indicates the number of segmentation errors (message too large for segmentation)
  • The 'Segmentation error fail' counter indicates the number of segmentation failed errors (case of LUDT segmentation at interworking node)
  • The 'Reassembly error' counter indicates the number of reassembly out of sequence errors (including duplicate segment and non-first segment)
  • The 'Reassembly error timer expiry' counter indicates the number of reassembly errors timer expiry events
  • The 'Reassembly error no space' counter indicates the number of reassembly errors (no space for reassembly) events
  • The 'Inactivity timer expire' counter indicates the number of inactivity timer expire events
  • The 'Routing failure invalid INS routing request' counter indicates the number of routing failure invalid INS routing requests
  • The 'Routing failure invalid ISNI routing request' counter indicates the number of routing failure invalid ISNI routing requests
  • The 'Failure ISNI constrained routing' counter indicates the number of failure ISNI constrained routing events
  • The 'Failure redundant ISNI routing request' counter indicates the number of failure due to redundant ISNI routing request
  • The 'Failure ISNI network identifier' counter indicates the number of failures in ISNI identification of network
Personal tools