Overview… service disruptions
The receive logic can look for disruptions in an expected steady stream of incoming packets. This assumes that you have separately established a transmitting stream that sends a regular train of packets through the network under test to the receiving port.
Different kinds of service disruptions are defined, for different situations and time scales:
- No-sync, which simply monitors whether the port has established RX sync. Such a disruption would typically be because of an unplugged cable or a reset of the equipment directly attached to the Xena test port.
- Zero-rate, which monitors the port-level packet rate of incoming packets that is shown on the receive statistics, which is updated with a one-second period. Such a disruption would typically be because of an unplugged cable or a reset of the equipment deeper inside the network under test.
- Gap monitor, which monitors the incoming packet stream for gaps in the milli/micro-second range, according to the parameters defined under port properties.
The number of service disruption events is displayed along with the accumulated duration of those events.
Note that the no-sync and zero-rate events are detected by the XenaManager and therefore require an active connection to the tester. In contrast the gap monitor events are detected by the tester hardware and are therefore accumulated regardless of any XenaManager connections and shared across them all.
Service disruption events can be time-stamped and logged by an active XenaManager.