FIX: Initialize L2BD keyword

Currently in Performance the "Initialize L2 bridge domain" keyword is adding
interfaces to L2DB per node and at the same time waiting until interfaces
become UP. This may be an issue if physical interfaces interconnecting DUTs
required to be administratively UP on both DUTs to physical link state became
UP.

This fix is supposed to check the link state after all DUTs are
initialized.

Change-Id: I430b4285967f6168e6c74e0089a3e0d037b251d1
Signed-off-by: Peter Mikus <pmikus@cisco.com>

diff --git a/resources/libraries/robot/performance/performance_configuration.robot b/resources/libraries/robot/performance/performance_configuration.robot
index 2469799..adf233d 100644 (file)
--- a/resources/libraries/robot/performance/performance_configuration.robot
+++ b/resources/libraries/robot/performance/performance_configuration.robot
@@ -731,8 +731,19 @@
 | | ... | that is created automatically with index 1. Learning is enabled.
 | | ... | Interfaces are brought up.
 | | ...
 | | ... | that is created automatically with index 1. Learning is enabled.
 | | ... | Interfaces are brought up.
 | | ...

-| | Configure L2BD forwarding | ${dut1} | ${dut1_if1} | ${dut1_if2}
-| | Configure L2BD forwarding | ${dut2} | ${dut2_if1} | ${dut2_if2}
+| | ... | *Arguments:*
+| | ... | - bd_id - Bridge domain ID. Type: integer
+| | ...
+| | ... | *Example:*
+| | ...
+| | ... | \| Initialize L2 bridge domain in 3-node circular topology \| 1 \|
+| | ...
+| | [Arguments] | ${bd_id}=${1}
+| | ...
+| | Add interface to bridge domain | ${dut1} | ${dut1_if1} | ${bd_id}
+| | Add interface to bridge domain | ${dut1} | ${dut1_if2} | ${bd_id}
+| | Add interface to bridge domain | ${dut2} | ${dut2_if1} | ${bd_id}
+| | Add interface to bridge domain | ${dut2} | ${dut2_if2} | ${bd_id}

 | | All Vpp Interfaces Ready Wait | ${nodes}
 
 | Configure IPv4 ACLs
 | | All Vpp Interfaces Ready Wait | ${nodes}
 
 | Configure IPv4 ACLs