[ebgp] Check EBGP adjacencies with DUT [ node(s): r2,r4 ] [WAITING] Waiting for EBGP sessions to start (retrying for 10 seconds) [PASS] r2: Neighbor 172.16.1.1 (dut) is in state Established [PASS] r4: Neighbor 172.16.3.1 (dut) is in state Established [PASS] Succeeded in 6.2 seconds [PASS] Test succeeded [red_c_rip] Check connected subnet as RIPv2 prefix on R1 [ node(s): r1 ] [PASS] r1: Found prefix 172.16.1.0/24 in the ipv4 routing table [PASS] Test succeeded [red_bgp_rip] Check for BGP prefix in RIPv2 [ node(s): r1 ] [WAITING] Waiting for BGP and RIPv2 convergence (retrying for 10 seconds) [PASS] r1: Found prefix 10.0.0.3/32 in the ipv4 routing table [PASS] Succeeded in 3.4 seconds [PASS] Test succeeded [red_rip_bgp] Check for RIPv2 prefix in BGP [ node(s): r2 ] [PASS] r2: The prefix 10.0.0.2/32 is in the BGP table [PASS] Test succeeded [red_lb_ping] Loopback-to-loopback reachability test in VRF red [ node(s): r1 ] [PASS] r1: Ping to r2 from 10.0.0.2/32 succeeded [PASS] Test succeeded [red_p_rip] Check for reachability of connected routes in RIPv2 [ node(s): r2 ] [PASS] r2: Ping to r1 succeeded [PASS] Test succeeded [blue_lb_ping] Loopback-to-loopback reachability test in VRF blue [ node(s): r3 ] [PASS] r3: Ping to r4 from 10.0.0.4/32 succeeded [PASS] Test succeeded [inter_vrf] Ping-based isolation test between blue and red VRF [ node(s): r1 ] [PASS] r1: Ping to r4 failed as expected [PASS] Test succeeded [SUCCESS] Tests passed: 9