Figure -Broadcast Frame Latency Summary Results
-
Congestion Control
The objective of this test is to determine how a DUT handles congestion. Does the device implement congestion control and does congestion on one port affect an uncongested port? This procedure determines if “Head of Line Blocking” and/or “Backpressure” are present.
Table shows the results of applying the tests on our sample device. The table shows that our sample device does not have “Head of Line Blocking” and does not perform “Backpressure” for congestion control.
Table - Congestion Control Test Details
Frame
Size (Byte)
|
Burst
Size
|
Intended
Load (%)
|
Port
Type
|
Offered
Load (%)
|
Frame
Loss (%)
|
HOLB
Exists
|
BP
Exists
|
64
|
1
|
100
|
Transmit
|
100
|
0
|
0
|
0
|
64
|
1
|
100
|
Transmit
|
100
|
0
|
0
|
0
|
64
|
0
|
0
|
Uncongested
|
0
|
0
|
0
|
0
|
64
|
0
|
0
|
Congested
|
0
|
33.33
|
0
|
0
|
128
|
1
|
100
|
Transmit
|
100
|
0
|
0
|
0
|
128
|
1
|
100
|
Transmit
|
100
|
0
|
0
|
0
|
128
|
0
|
0
|
Uncongested
|
0
|
0
|
0
|
0
|
128
|
0
|
0
|
Congested
|
0
|
33.33
|
0
|
0
|
256
|
1
|
100
|
Transmit
|
100
|
0
|
0
|
0
|
256
|
1
|
100
|
Transmit
|
100
|
0
|
0
|
0
|
256
|
0
|
0
|
Uncongested
|
0
|
0
|
0
|
0
|
256
|
0
|
0
|
Congested
|
0
|
33.33
|
0
|
0
|
512
|
1
|
100
|
Transmit
|
100
|
0
|
0
|
0
|
512
|
1
|
100
|
Transmit
|
100
|
0
|
0
|
0
|
512
|
0
|
0
|
Uncongested
|
0
|
0
|
0
|
0
|
512
|
0
|
0
|
Congested
|
0
|
33.32
|
0
|
0
|
1024
|
1
|
100
|
Transmit
|
100
|
0
|
0
|
0
|
1024
|
1
|
100
|
Transmit
|
100
|
0
|
0
|
0
|
1024
|
0
|
0
|
Uncongested
|
0
|
0
|
0
|
0
|
1024
|
0
|
0
|
Congested
|
0
|
33.32
|
0
|
0
|
1280
|
1
|
100
|
Transmit
|
100
|
0
|
0
|
0
|
1280
|
1
|
100
|
Transmit
|
100
|
0
|
0
|
0
|
1280
|
0
|
0
|
Uncongested
|
0
|
0
|
0
|
0
|
1280
|
0
|
0
|
Congested
|
0
|
33.32
|
0
|
0
|
1518
|
1
|
100
|
Transmit
|
100
|
0
|
0
|
0
|
1518
|
1
|
100
|
Transmit
|
100
|
0
|
0
|
0
|
1518
|
0
|
0
|
Uncongested
|
0
|
0
|
0
|
0
|
1518
|
0
|
0
|
Congested
|
0
|
33.32
|
0
|
0
| -
Faulty (with error) Frame Filtering
The objective of the faulty frames filtering test is to determine the behavior of the DUT under faulty or abnormal frame conditions. The results of the test indicate if the DUT/SUT filters the errors, or simply propagates the faulty frames along to the destination
Table shows the results of applying the test on our sample device. The table shows that none of the faulty frames are sent to the destination and all are dropped.
Table - Faulty Frame Filtering Test Results
Error
Type
|
Test
Status
|
Intended
Load (%)
|
Tx Sig Frame Count
|
Rx Sig Frame Count
|
Tx Non Sig Frame Count
|
Rx Non Sig Frame Count
|
Oversize
Frames
|
Undersize
Frames
|
CRC Error Frames
|
CRC
|
Passed
|
100
|
178571430
|
0
|
0
|
92
|
0
|
0
|
0
|
Oversize
|
Passed
|
100
|
9721324
|
0
|
0
|
88
|
0
|
0
|
0
|
Undersize
|
Passed
|
100
|
180722892
|
0
|
0
|
91
|
0
|
0
|
0
| -
Forward Pressure Rate
The Forward Pressure test overloads a DUT/SUT port and measures the output for forward pressure. If the DUT/SUT transmits frames with an inter-frame gap will be less than 96 bits, then forward pressure is detected.
Table shows the results of applying the test on our sample device. The results show that even if the inter-frame gap is less than 96 bits frames, the device forwards them in the standard form.
Table - Forward Pressure Rate Test Results
Frame
Size (Byte)
|
Forward
Pressure
|
Intended
Load (%)
|
Offered
Load (%)
|
Offered
Load (fps)
|
Forwarding
Rate (fps)
|
Frame
Loss (%)
|
Other Frames
|
Flood Count
|
64
|
FALSE
|
101.20
|
101.21
|
36144578.4
|
35714722
|
1.188
|
0
|
0
|
128
|
FALSE
|
100.68
|
100.68
|
20408163.6
|
20270571
|
0.673
|
0
|
0
|
256
|
FALSE
|
100.36
|
100.36
|
10909091.2
|
10869729
|
0.36
|
0
|
0
|
512
|
FALSE
|
100.19
|
100.19
|
5649717.6
|
5639181
|
0.185
|
0
|
0
|
1024
|
FALSE
|
100.10
|
100.10
|
2876318.4
|
2873606
|
0.093
|
0
|
0
|
1280
|
FALSE
|
100.08
|
100.08
|
2309469.2
|
2307720
|
0.074
|
0
|
0
|
1518
|
FALSE
|
100.07
|
100.07
|
1951854.4
|
1950615
|
0.062
|
0
|
0
|
Share with your friends: |