FIX: Set MTU before configuring l2patch

This should reduce number of "link down" failures dramatically.
The exact mechanism is not clear, but l2xc suites do not fail that much.

Change-Id: Ie102d90a58561121695c9938679ce0d3ee6a874f
Signed-off-by: Vratko Polak <vrpolak@cisco.com>

diff --git a/resources/libraries/robot/performance/performance_configuration.robot b/resources/libraries/robot/performance/performance_configuration.robot
index 9ea6e0d..4c01a1a 100644 (file)
--- a/resources/libraries/robot/performance/performance_configuration.robot
+++ b/resources/libraries/robot/performance/performance_configuration.robot
@@ -44,7 +44,7 @@
 | | ... | maximal MTU.*
 | | ...
 # TODO: Rework KW to set all interfaces in path UP and set MTU (including
-# software interfaces. Run KW at the end phase of VPP setup to split
+# software interfaces. Run KW at the start phase of VPP setup to split
 # from other "functial" configuration. This will allow modularity of this
 # library
 | | ${duts}= | Get Matches | ${nodes} | DUT*
@@ -805,10 +805,10 @@
 | | ... | Setup L2 patch topology by cross connecting two interfaces on
 | | ... | each DUT. Interfaces are brought up.
 | | ...
+| | Set interfaces in path up
 | | ${duts}= | Get Matches | ${nodes} | DUT*
 | | :FOR | ${dut} | IN | @{duts}
 | | | Configure L2patch | ${nodes['${dut}']} | ${${dut}_if1} | ${${dut}_if2}
-| | Set interfaces in path up
 
 | Initialize L2 xconnect in 2-node circular topology
 | | [Documentation]