MTP3:Statistics

From TBwiki
Jump to: navigation, search

The MTP3 layer can gather statistics information at any time to measure the performance of the MTP3 software. This information can be used to determine the distribution of traffic loads and quality of service (QoS) parameters, and to assist in MTP3 software debugging. The collection of statistics information may or may not result in the counters being reset.


General statistics

The following statistics are available for query/display:

  • The Unavailable received message counter indicates the number of userpart unavailable messages received for a user of this layer
  • The Unavailable transmit message counter indicates the number of userpart unavailable messages transmitted because of an unavailable user at this layer
  • The Traffic restart transmit message counter indicates the number of traffic restart allowed messages transmitted
  • The Traffic restart received message counter indicates the number of traffic restart allowed messages received
  • The Traffic restart waiting transmit message counter indicates the number of traffic restart waiting messages transmitted for the ANSI version
  • The Traffic restart waiting received message counter indicates the number of traffic restart waiting messages received for the ANSI version
  • The MSU dropped due to routing error counter indicates the number of drops that may have occurred for the following reasons:
    • Self or adjacent restart is in progress
    • SLS value is wrong
    • Circular routing
    • MSU is received at an SP for some other node (SP cannot route)
    • The destination is unreachable or unavailable
    • The layer encounters an illegal routing configuration or a bad packet


Other statistics

Personal tools