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

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


The devices under test are an EVPN PE-device and an EVPN route reflector. The
PE-device should originate EVPN routes with correct next-hop and the RR should
propagate EVPN AF routes between PE-devices, resulting in VXLAN-based VLAN
extension. However, the core routing protocol is not OSPF but EBGP faked with
BGP local-as settings. The overall design is thus EVPN IBGP between loopbacks
running over IPv4 EBGP.

* 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