Creating Device configuration snippets
[CREATED] spine: initial,bgp,evpn
[CREATED] dut: initial,vlan,bgp,vxlan,evpn,bgp.session
[CREATED] l2: initial,vlan,bgp,vxlan,evpn,bgp.session
[CREATED] h1: initial,routing
[CREATED] h2: initial,routing
Checking Are lab devices ready to be configured?
 [INFO] Checking SSH server(s) on dut
[SSH]     SSH server on node dut (device iol) is ready after 25.4 seconds
Config Deploying device configurations
 [INFO] Executing initial configuration for node spine
 [INFO] Executing initial configuration for node l2
 [INFO] Executing initial configuration for node h1 (namespace clab-
          ml-17-h1)
 [INFO] Executing initial configuration for node h2 (namespace clab-
          ml-17-h2)
 [INFO] Executing routing configuration for node h1 (namespace clab-
          ml-17-h1)
 [INFO] Executing routing configuration for node h2 (namespace clab-
          ml-17-h2)
 [INFO] Executing bgp configuration for node spine
 [INFO] Executing vlan configuration for node l2
 [INFO] Executing bgp configuration for node l2
 [INFO] Executing evpn configuration for node spine
 [INFO] Executing vxlan configuration for node l2
 [INFO] Executing evpn configuration for node l2
 [INFO] Executing bgp.session configuration for node l2

Results of configuration script deployments
================================================================================
spine            Script:  initial,bgp,evpn
dut              Startup: initial,vlan,bgp,vxlan,evpn,bgp.session
l2               Script:  initial,vlan,bgp,vxlan,evpn,bgp.session
h1               Script:  initial,routing
h2               Script:  initial,routing


The device under test is an EVPN leaf device using EVPN-over-EBGP. It should
generate EVPN AF routes and accepts EBGP EVPN AF routes with the same AS.

* h1 and h2 should be able to ping each other

Please note it might take a while for the lab to work due to
STP learning phase