Creating Device configuration snippets
[CREATED] spine: initial,bgp,evpn,ebgp.multihop
[CREATED] l1: initial,vlan,bgp,vxlan,evpn,ebgp.multihop
[CREATED] l2: initial,vlan,bgp,vxlan,evpn,ebgp.multihop
[CREATED] h1: initial,routing
[CREATED] h2: initial,routing
Checking Are lab devices ready to be configured?
 [INFO] Checking SSH server(s) on spine,l1
[SSH]     SSH server on node l1 (device iol) is ready after 25.3 seconds
[SSH]     SSH server on node spine (device iol) is ready after 25.3 seconds
Config Deploying device configurations
 [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 h2 (namespace clab-
          ml-17-h2)
 [INFO] Executing routing configuration for node h1 (namespace clab-
          ml-17-h1)
 [INFO] Executing vlan configuration for node l2
 [INFO] Executing bgp configuration for node l2
 [INFO] Executing vxlan configuration for node l2
 [INFO] Executing evpn configuration for node l2
 [INFO] Executing ebgp.multihop configuration for node l2

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


The devices under test are EVPN switches (leaf and spine) using
EVPN-over-multihop-EBGP. The leaf switch should generate and accept EVPN AF
routes, and the spine switch should propagate them without changing the BGP
next hop.

* 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