[WARNING]: Could not match supplied host pattern, ignoring: unprovisioned PLAY [Deploy initial device configuration] ************************************* TASK [Set variables that cannot be set with VARS] ****************************** ok: [h1] ok: [h3] ok: [h2] ok: [h4] ok: [s1] ok: [s2] TASK [Find device readiness script] ******************************************** ok: [h2] ok: [h1] ok: [h3] ok: [h4] ok: [s1] ok: [s2] TASK [Wait for device to become ready] ***************************************** skipping: [h1] skipping: [h2] skipping: [h3] skipping: [h4] included: /home/pipi/net101/tools/netsim/ansible/tasks/readiness-check/eos-clab.yml for s1, s2 TASK [Wait for cEOS SSH daemon to start] *************************************** ok: [s2] ok: [s1] TASK [Deploy initial configuration] ******************************************** included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-module.yml for s1, s2, h1, h2, h3, h4 TASK [Figure out whether to deploy the module initial on current device] ******* ok: [h1] ok: [h2] ok: [h4] ok: [h3] ok: [s1] ok: [s2] TASK [Find configuration template for initial] ********************************* ok: [h1] ok: [h2] ok: [h4] ok: [h3] ok: [s1] ok: [s2] TASK [Print deployed configuration when running in verbose mode] *************** ok: [h1] => msg: |- initial configuration for h1 ========================================= #!/bin/bash # # This script contains the 'ip' commands needed to set up container # interfaces and route table. It's executed within the container # network namespace on the container host. # # /etc/hosts file is generated as a clab bind. # set -e ### One-Shot configuration (non-Ubuntu VM or container) # # Disable IPv4 and IPv6 forwarding # sysctl -w net.ipv4.ip_forward=0 sysctl -w net.ipv6.conf.all.forwarding=0 # # Interface addressing # ip link set dev eth1 up set +e ip addr del 172.16.0.1/24 dev eth1 2>/dev/null set -e ip addr add 172.16.0.1/24 dev eth1 ip link set eth1 mtu 1500 # # Add routes to IPv4 address pools pointing to the first neighbor on the first link # # If you need anything better, use FRR instead of Linux and start routing (or use IPv6) # # lan prefix: 172.16.0.0/16 local subnet: 172.16.0.0/24 set +e ip route del 172.16.0.0/16 2>/dev/null set -e ip route add 172.16.0.0/16 via 172.16.0.5 # loopback prefix: 10.0.0.0/24 local subnet: 172.16.0.0/24 set +e ip route del 10.0.0.0/24 2>/dev/null set -e ip route add 10.0.0.0/24 via 172.16.0.5 # mgmt prefix: 192.168.17.0/24 local subnet: 172.16.0.0/24 # p2p prefix: 10.1.0.0/16 local subnet: 172.16.0.0/24 set +e ip route del 10.1.0.0/16 2>/dev/null set -e ip route add 10.1.0.0/16 via 172.16.0.5 # router_id prefix: 10.0.0.0/24 local subnet: 172.16.0.0/24 # vrf_loopback prefix: 10.2.0.0/24 local subnet: 172.16.0.0/24 set +e ip route del 10.2.0.0/24 2>/dev/null set -e ip route add 10.2.0.0/24 via 172.16.0.5 # # Print the final routing table ip route ok: [h4] => msg: |- initial configuration for h4 ========================================= #!/bin/bash # # This script contains the 'ip' commands needed to set up container # interfaces and route table. It's executed within the container # network namespace on the container host. # # /etc/hosts file is generated as a clab bind. # set -e ### One-Shot configuration (non-Ubuntu VM or container) # # Disable IPv4 and IPv6 forwarding # sysctl -w net.ipv4.ip_forward=0 sysctl -w net.ipv6.conf.all.forwarding=0 # # Interface addressing # ip link set dev eth1 up set +e ip addr del 172.16.2.4/24 dev eth1 2>/dev/null set -e ip addr add 172.16.2.4/24 dev eth1 ip link set eth1 mtu 1500 # # Add routes to IPv4 address pools pointing to the first neighbor on the first link # # If you need anything better, use FRR instead of Linux and start routing (or use IPv6) # # lan prefix: 172.16.0.0/16 local subnet: 172.16.2.0/24 set +e ip route del 172.16.0.0/16 2>/dev/null set -e ip route add 172.16.0.0/16 via 172.16.2.6 # loopback prefix: 10.0.0.0/24 local subnet: 172.16.2.0/24 set +e ip route del 10.0.0.0/24 2>/dev/null set -e ip route add 10.0.0.0/24 via 172.16.2.6 # mgmt prefix: 192.168.17.0/24 local subnet: 172.16.2.0/24 # p2p prefix: 10.1.0.0/16 local subnet: 172.16.2.0/24 set +e ip route del 10.1.0.0/16 2>/dev/null set -e ip route add 10.1.0.0/16 via 172.16.2.6 # router_id prefix: 10.0.0.0/24 local subnet: 172.16.2.0/24 # vrf_loopback prefix: 10.2.0.0/24 local subnet: 172.16.2.0/24 set +e ip route del 10.2.0.0/24 2>/dev/null set -e ip route add 10.2.0.0/24 via 172.16.2.6 # # Print the final routing table ip route ok: [s1] => msg: |- initial configuration for s1 ========================================= hostname s1 ! logging monitor debugging ! lldp run ip routing ! vrf instance tenant rd 65000:1 ! ip routing vrf tenant ! ! ip host h1 172.16.0.1 ip host h2 172.16.0.2 ip host h3 172.16.1.3 ip host h4 172.16.2.4 ip host s1-tenant 172.16.0.5 172.16.1.5 ip host s2 10.0.0.6 10.1.0.2 ip host s2-tenant 172.16.2.6 172.16.0.6 ! interface Management0 no lldp transmit no lldp receive ! interface Loopback0 no shutdown ip address 10.0.0.5/32 ! interface Ethernet1 no shutdown no switchport mtu 1600 description s1 -> s2 ip address 10.1.0.1/30 ! mac-address 52dc.cafe.0501 ! interface Ethernet2 no shutdown no switchport ! mac-address 52dc.cafe.0502 ! interface Ethernet3 no shutdown no switchport ! mac-address 52dc.cafe.0503 ! interface Vlan1000 no shutdown vrf tenant description VLAN red (1000) -> [h1,h2,s2] ip address 172.16.0.5/24 ! interface Vlan1001 no shutdown vrf tenant description VLAN blue (1001) -> [h3] [stub] ip address 172.16.1.5/24 ! ok: [h3] => msg: |- initial configuration for h3 ========================================= #!/bin/bash # # This script contains the 'ip' commands needed to set up container # interfaces and route table. It's executed within the container # network namespace on the container host. # # /etc/hosts file is generated as a clab bind. # set -e ### One-Shot configuration (non-Ubuntu VM or container) # # Disable IPv4 and IPv6 forwarding # sysctl -w net.ipv4.ip_forward=0 sysctl -w net.ipv6.conf.all.forwarding=0 # # Interface addressing # ip link set dev eth1 up set +e ip addr del 172.16.1.3/24 dev eth1 2>/dev/null set -e ip addr add 172.16.1.3/24 dev eth1 ip link set eth1 mtu 1500 # # Add routes to IPv4 address pools pointing to the first neighbor on the first link # # If you need anything better, use FRR instead of Linux and start routing (or use IPv6) # # lan prefix: 172.16.0.0/16 local subnet: 172.16.1.0/24 set +e ip route del 172.16.0.0/16 2>/dev/null set -e ip route add 172.16.0.0/16 via 172.16.1.5 # loopback prefix: 10.0.0.0/24 local subnet: 172.16.1.0/24 set +e ip route del 10.0.0.0/24 2>/dev/null set -e ip route add 10.0.0.0/24 via 172.16.1.5 # mgmt prefix: 192.168.17.0/24 local subnet: 172.16.1.0/24 # p2p prefix: 10.1.0.0/16 local subnet: 172.16.1.0/24 set +e ip route del 10.1.0.0/16 2>/dev/null set -e ip route add 10.1.0.0/16 via 172.16.1.5 # router_id prefix: 10.0.0.0/24 local subnet: 172.16.1.0/24 # vrf_loopback prefix: 10.2.0.0/24 local subnet: 172.16.1.0/24 set +e ip route del 10.2.0.0/24 2>/dev/null set -e ip route add 10.2.0.0/24 via 172.16.1.5 # # Print the final routing table ip route ok: [h2] => msg: |- initial configuration for h2 ========================================= #!/bin/bash # # This script contains the 'ip' commands needed to set up container # interfaces and route table. It's executed within the container # network namespace on the container host. # # /etc/hosts file is generated as a clab bind. # set -e ### One-Shot configuration (non-Ubuntu VM or container) # # Disable IPv4 and IPv6 forwarding # sysctl -w net.ipv4.ip_forward=0 sysctl -w net.ipv6.conf.all.forwarding=0 # # Interface addressing # ip link set dev eth1 up set +e ip addr del 172.16.0.2/24 dev eth1 2>/dev/null set -e ip addr add 172.16.0.2/24 dev eth1 ip link set eth1 mtu 1500 # # Add routes to IPv4 address pools pointing to the first neighbor on the first link # # If you need anything better, use FRR instead of Linux and start routing (or use IPv6) # # lan prefix: 172.16.0.0/16 local subnet: 172.16.0.0/24 set +e ip route del 172.16.0.0/16 2>/dev/null set -e ip route add 172.16.0.0/16 via 172.16.0.6 # loopback prefix: 10.0.0.0/24 local subnet: 172.16.0.0/24 set +e ip route del 10.0.0.0/24 2>/dev/null set -e ip route add 10.0.0.0/24 via 172.16.0.6 # mgmt prefix: 192.168.17.0/24 local subnet: 172.16.0.0/24 # p2p prefix: 10.1.0.0/16 local subnet: 172.16.0.0/24 set +e ip route del 10.1.0.0/16 2>/dev/null set -e ip route add 10.1.0.0/16 via 172.16.0.6 # router_id prefix: 10.0.0.0/24 local subnet: 172.16.0.0/24 # vrf_loopback prefix: 10.2.0.0/24 local subnet: 172.16.0.0/24 set +e ip route del 10.2.0.0/24 2>/dev/null set -e ip route add 10.2.0.0/24 via 172.16.0.6 # # Print the final routing table ip route ok: [s2] => msg: |- initial configuration for s2 ========================================= hostname s2 ! logging monitor debugging ! lldp run ip routing ! vrf instance tenant rd 65000:1 ! ip routing vrf tenant ! ! ip host h1 172.16.0.1 ip host h2 172.16.0.2 ip host h3 172.16.1.3 ip host h4 172.16.2.4 ip host s1 10.0.0.5 10.1.0.1 ip host s1-tenant 172.16.0.5 172.16.1.5 ip host s2-tenant 172.16.2.6 172.16.0.6 ! interface Management0 no lldp transmit no lldp receive ! interface Loopback0 no shutdown ip address 10.0.0.6/32 ! interface Ethernet1 no shutdown no switchport mtu 1600 description s2 -> s1 ip address 10.1.0.2/30 ! mac-address 52dc.cafe.0601 ! interface Ethernet2 no shutdown no switchport ! mac-address 52dc.cafe.0602 ! interface Ethernet3 no shutdown no switchport vrf tenant description s2 -> h4 [stub] ip address 172.16.2.6/24 ! mac-address 52dc.cafe.0603 ! interface Vlan1000 no shutdown vrf tenant description VLAN red (1000) -> [h1,s1,h2] ip address 172.16.0.6/24 ! TASK [Find configuration deployment deploy_script for initial] ***************** ok: [h1] ok: [h3] ok: [h2] ok: [s1] ok: [s2] ok: [h4] TASK [Deploy initial configuration] ******************************************** included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/eos.yml for s1, s2 included: /home/pipi/net101/tools/netsim/ansible/tasks/linux/initial-clab.yml for h1, h2, h3, h4 TASK [eos_config: deploying initial from /home/pipi/net101/tools/netsim/ansible/templates/initial/eos.j2] *** [WARNING]: To ensure idempotency and correct diff the input configuration lines should be similar to how they appear if present in the running configuration on device including the indentation changed: [s2] changed: [s1] TASK [set_fact] **************************************************************** ok: [h1] ok: [h2] ok: [h3] ok: [h4] TASK [Create initial container setup from /home/pipi/net101/tools/netsim/ansible/templates/initial/linux-clab.j2] *** changed: [h4 -> localhost] changed: [h2 -> localhost] changed: [h1 -> localhost] changed: [h3 -> localhost] TASK [Initial container configuration via /tmp/config-KiCDpVIb-h1.sh] ********** changed: [h4 -> localhost] changed: [h1 -> localhost] changed: [h3 -> localhost] changed: [h2 -> localhost] TASK [file] ******************************************************************** changed: [h2 -> localhost] changed: [h1 -> localhost] changed: [h3 -> localhost] changed: [h4 -> localhost] PLAY [Deploy module-specific configurations] *********************************** TASK [Set variables that cannot be set with VARS] ****************************** ok: [s1] ok: [s2] TASK [Deploy individual configuration modules] ********************************* included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-module.yml for s1, s2 => (item=vlan) included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-module.yml for s1, s2 => (item=ospf) included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-module.yml for s1, s2 => (item=vrf) included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-module.yml for s1, s2 => (item=vxlan) TASK [Figure out whether to deploy the module vlan on current device] ********** ok: [s1] ok: [s2] TASK [Find configuration template for vlan] ************************************ ok: [s1] ok: [s2] TASK [Print deployed configuration when running in verbose mode] *************** ok: [s1] => msg: |- vlan configuration for s1 ========================================= vlan 1001 name blue ! vlan 1000 name red ! ! interface Ethernet2 switchport switchport access vlan 1000 ! interface Ethernet3 switchport switchport access vlan 1001 ! interface Vlan1000 ! interface Vlan1001 ok: [s2] => msg: |- vlan configuration for s2 ========================================= vlan 1000 name red ! ! interface Ethernet2 switchport switchport access vlan 1000 ! interface Vlan1000 TASK [Find configuration deployment deploy_script for vlan] ******************** ok: [s1] ok: [s2] TASK [Deploy vlan configuration] *********************************************** included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/eos.yml for s1, s2 TASK [eos_config: deploying vlan from /home/pipi/net101/tools/netsim/ansible/templates/vlan/eos.j2] *** changed: [s2] changed: [s1] TASK [Figure out whether to deploy the module ospf on current device] ********** ok: [s1] ok: [s2] TASK [Find configuration template for ospf] ************************************ ok: [s1] ok: [s2] TASK [Print deployed configuration when running in verbose mode] *************** ok: [s1] => msg: |- ospf configuration for s1 ========================================= ! ! OSPFv2 configuration ! router ospf 1 router-id 10.0.0.5 interface unnumbered hello mask tx 0.0.0.0 timers spf delay initial 100 200 500 timers lsa rx min interval 100 timers lsa tx delay initial 100 200 500 ! interface Loopback0 ! ip ospf area 0.0.0.0 ! interface Ethernet1 ! s1 -> s2 ip ospf area 0.0.0.0 ip ospf network point-to-point ! ok: [s2] => msg: |- ospf configuration for s2 ========================================= ! ! OSPFv2 configuration ! router ospf 1 router-id 10.0.0.6 interface unnumbered hello mask tx 0.0.0.0 timers spf delay initial 100 200 500 timers lsa rx min interval 100 timers lsa tx delay initial 100 200 500 ! interface Loopback0 ! ip ospf area 0.0.0.0 ! interface Ethernet1 ! s2 -> s1 ip ospf area 0.0.0.0 ip ospf network point-to-point ! TASK [Find configuration deployment deploy_script for ospf] ******************** ok: [s1] ok: [s2] TASK [Deploy ospf configuration] *********************************************** included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/eos.yml for s1, s2 TASK [eos_config: deploying ospf from /home/pipi/net101/tools/netsim/ansible/templates/ospf/eos.j2] *** changed: [s2] changed: [s1] TASK [Figure out whether to deploy the module vrf on current device] *********** ok: [s1] ok: [s2] TASK [Find configuration template for vrf] ************************************* ok: [s1] ok: [s2] TASK [Print deployed configuration when running in verbose mode] *************** ok: [s1] => msg: |- vrf configuration for s1 ========================================= ! ! OSPFv2 configuration ! router ospf 100 vrf tenant router-id 10.0.0.5 interface unnumbered hello mask tx 0.0.0.0 timers spf delay initial 100 200 500 timers lsa rx min interval 100 timers lsa tx delay initial 100 200 500 redistribute connected passive-interface Vlan1001 ! interface Vlan1000 ! VLAN red (1000) -> [h1,h2,s2] ip ospf area 0.0.0.0 ip ospf cost 5 ! interface Vlan1001 ! VLAN blue (1001) -> [h3] ip ospf area 0.0.0.0 ip ospf network point-to-point ip ospf cost 10 ! ok: [s2] => msg: |- vrf configuration for s2 ========================================= ! ! OSPFv2 configuration ! router ospf 100 vrf tenant router-id 10.0.0.6 interface unnumbered hello mask tx 0.0.0.0 timers spf delay initial 100 200 500 timers lsa rx min interval 100 timers lsa tx delay initial 100 200 500 redistribute connected passive-interface Ethernet3 ! interface Ethernet3 ! s2 -> h4 ip ospf area 0.0.0.0 ip ospf network point-to-point ! interface Vlan1000 ! VLAN red (1000) -> [h1,s1,h2] ip ospf area 0.0.0.0 ip ospf cost 5 ! TASK [Find configuration deployment deploy_script for vrf] ********************* ok: [s1] ok: [s2] TASK [Deploy vrf configuration] ************************************************ included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/eos.yml for s1, s2 TASK [eos_config: deploying vrf from /home/pipi/net101/tools/netsim/ansible/templates/vrf/eos.j2] *** changed: [s2] changed: [s1] TASK [Figure out whether to deploy the module vxlan on current device] ********* ok: [s1] ok: [s2] TASK [Find configuration template for vxlan] *********************************** ok: [s1] ok: [s2] TASK [Print deployed configuration when running in verbose mode] *************** ok: [s1] => msg: |- vxlan configuration for s1 ========================================= interface vxlan 1 vxlan source-interface Loopback0 vxlan vlan 1000 vni 101000 vxlan vlan 1000 flood vtep 10.0.0.6 vxlan vlan 1001 vni 101001 ok: [s2] => msg: |- vxlan configuration for s2 ========================================= interface vxlan 1 vxlan source-interface Loopback0 vxlan vlan 1000 vni 101000 vxlan vlan 1000 flood vtep 10.0.0.5 TASK [Find configuration deployment deploy_script for vxlan] ******************* ok: [s1] ok: [s2] TASK [Deploy vxlan configuration] ********************************************** included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/eos.yml for s1, s2 TASK [eos_config: deploying vxlan from /home/pipi/net101/tools/netsim/ansible/templates/vxlan/eos.j2] *** changed: [s2] changed: [s1] PLAY [Deploy custom deployment templates] ************************************** skipping: no hosts matched PLAY RECAP ********************************************************************* h1 : ok=12 changed=3 unreachable=0 failed=0 skipped=1 rescued=0 ignored=0 h2 : ok=12 changed=3 unreachable=0 failed=0 skipped=1 rescued=0 ignored=0 h3 : ok=12 changed=3 unreachable=0 failed=0 skipped=1 rescued=0 ignored=0 h4 : ok=12 changed=3 unreachable=0 failed=0 skipped=1 rescued=0 ignored=0 s1 : ok=40 changed=5 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 s2 : ok=40 changed=5 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 The devices under test are VLAN-to-VXLAN layer-3 switches connecting a VLAN stretched across VXLAN transport and two edge subnets. The test case verifies that you can use VXLAN-enabled VLANs in VRFs and that your device runs OSPF across VXLAN-enabled VLANs. * All hosts should be able to ping each other. * Switches should have OSPF adjacencies in the tenant VRF Notes: * It might take a while for the lab to work due to STP learning phase. * The validation tests don't check OSPF adjacencies