Creating Device configuration snippets [CREATED] dut: initial,routing,ospf,bgp [CREATED] x1: initial,bgp [CREATED] x2: initial,ospf,bgp [CREATED] x3: initial,routing,ospf,bgp [CREATED] x4: initial,ospf,bgp Checking Are lab devices ready to be configured? [INFO] Checking SSH server(s) on dut [SSH] SSH server on node dut (device iosxr) is ready after 26.0 seconds Config Deploying device configurations [INFO] Executing initial configuration for node dut [INFO] Executing initial configuration for node x1 [INFO] Executing initial configuration for node x2 [INFO] Executing initial configuration for node x3 [INFO] Executing initial configuration for node x4 [INFO] Executing ospf configuration for node x2 [INFO] Executing bgp configuration for node x1 [INFO] Executing routing configuration for node x3 [INFO] Executing ospf configuration for node x4 [INFO] Executing ospf configuration for node x3 [INFO] Executing bgp configuration for node x2 [INFO] Executing bgp configuration for node x4 [INFO] Executing bgp configuration for node x3 [INFO] Executing routing configuration for node dut [INFO] Executing ospf configuration for node dut [INFO] Executing bgp configuration for node dut Results of configuration script deployments ================================================================================ dut Script: initial,routing,ospf,bgp x1 Script: initial,bgp x2 Script: initial,ospf,bgp x3 Script: initial,routing,ospf,bgp x4 Script: initial,ospf,bgp Use this topology to test the 'local_as' functionality on IBGP sessions. The device under test uses local AS which is identical to remote AS, effectively turning an EBGP session into an IBGP session. It should establish the BGP sessions with X1 and X2, and propagate BGP prefixes between them. The test also checks (as a warning) whether DUT propagates "real" IBGP routes over local-as IBGP session. Failure to do that indicates that the next hop is not set correctly, or that DUT is not working as a route reflector toward local-as IBGP neighbor.