NT10G05 USER MANUAL
76-02-105 Rev.B
Page 58 of 80
Rx Frames
This is a count of the frames classified as good test
frames.
Rx Bandwidth (fps)
This is a calculated number of good frames per second
being received by the tester
Rx Bytes
This is a count of the received bytes
Rx Bandwidth (bps)
This is a calculation of the actual bandwidth being
received and is dependent upon the SLA bandwidth
setting. If the CIR is expressed as utilisation then the bit
rate includes the preamble and IPG overheads, whilst if
expressed as Information Rate then only the packet is
counted.
Rx Bandwidth (%CIR)
This expresses the receive bandwidth in terms of the SLA
CIR setting.
Lost / In Flight Frames
The meaning of this count differs when a test is running
and when it is completed. When the test has completed it
is a count of the lost frames, and should be the difference
between transmit and receive frame counts.
During the test, it is the Lost + In Flight count. Lost
frames are as it says, lost frames in the network. In Flight
frames are frames that have been transmitted, but not yet
received back.
In a normal test the Lost/In Flight count will settle at a
value related to the network latency and then stay at that
value throughout the test. If however, the count is
incrementing then that would suggest packets are being
lost.
Frame Loss Ratio (%)
The frame loss ratio is expressed as a percentage
according to the calculation
FLR = (100 * Lost/In Flight Frames) / Tx Frames
Frame Transit Delay (%) The measured latency is categorised into 8 discrete time
intervals and counts of frames within each interval are
maintained. The value indicated here is the upper limit
for the configured percentile of frames, in this case it says
that 95% of all frames had a latency less than 10mS
Frame Transit Delay (ms) The average frame transfer delay measured through the
test is displayed in milliseconds
IFDV (%)
Delay variation is measured and the average and
maximum values are displayed in milliseconds.
DV is measured according to MEF 10.1 standard
