Filter statistics - counting specification

Recording statistics events

The statistics events are worked out from the counting of protocol events depending on:

  • the protocols used on the SL, DL links of the interfaces.
  • the Time sampling period.
  • the types of counting details to be recorded or not for each protocol layer to allow the Counter display actions on the generated statistics event file:
    • Decoding: by protocol unit type - frames, messages, packets, ....
    • Decoding/Multiplex: counting by protocol unit type AND/OR particular field-value.
    • Measure: counting of data flow, of frames with a certain length.
    • Measure/Multiplex: counting of data flow AND/OR particular field-value.
    • Delays: counting of the number of Delay protocol system events of different types within a time range.

Counter display action

A selection of interface(s) (not related to Filter set) is attached to each of the 20 available Counters display actions which are related to:

  • counting of protocol event types.
  • Delays counting: counting of the number of Delay protocol system events (Start Delay, Stop Delay or Kill Delay events) within a time range (only for Stop Delay events). For example, that makes possible to glance over dispersion of the delay values.

Counting of protocol events

The specifications for counting BOP or Ethernet/802.3 protocol events are based on a group of selection conditions specific to the types of event depending on the protocol used on the SL, DL links.

Each Counter display action (20 available) can be defined by selection conditions of Measure, Decoding or Value type according to the selection of interface(s), the layer and the direction:

  • Measure: on a particular layer and a specific protocol, counting can be done on the data flow or the number of frames depending on their length.
  • Decoding: each protocol condition can be defined by any type of event of the SL, DL links according to the protocol stack specification by layers.
  • Value: selection conditions in a layer can be defined by a field-value in the control field or a data-value identified in the data field.

Use of protocol conditions to manage the actions is based on the following principles:

  • The group of protocol conditions which refer to different protocol layers, constitute an OR function.
  • The protocol conditions defined within a selection mode constitute an OR function.
  • Basically there is an OR function between the different selection modes, but an AND function can be defined according to the two following cases:
    • between used Decoding and Value selection modes.
    • between used Measure and Value selection modes.

 


home     Quick start     Specifications     Connections     Features     How to?     Notes     Search     Site Map

updated:  27-Feb-04