[WARNING]: Could not match supplied host pattern, ignoring: unprovisioned PLAY [Deploy initial device configuration] ************************************* TASK [Set variables that cannot be set with VARS] ****************************** ok: [x1] ok: [x2] ok: [dut] TASK [Find device readiness script] ******************************************** ok: [x1] ok: [x2] ok: [dut] TASK [Wait for device to become ready] ***************************************** skipping: [x1] skipping: [x2] included: /home/pipi/net101/tools/netsim/ansible/tasks/readiness-check/ioll2-clab.yml for dut TASK [Check if 'sshpass' is installed] ***************************************** ok: [dut -> localhost] TASK [Execute local ssh command to check ioll2 readiness] ********************** FAILED - RETRYING: [dut -> localhost]: Execute local ssh command to check ioll2 readiness (20 retries left). ok: [dut -> localhost] TASK [Confirm dut SSH server works] ******************************************** ok: [dut] => msg: Node dut is ready. TASK [Deploy initial configuration] ******************************************** included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-module.yml for dut, x1, x2 TASK [Figure out whether to deploy the module initial on current device] ******* ok: [x1] ok: [x2] ok: [dut] TASK [Find configuration template for initial] ********************************* ok: [x1] ok: [x2] ok: [dut] TASK [Print deployed configuration when running in verbose mode] *************** ok: [x1] => msg: |- initial configuration for x1 ========================================= #!/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 sysctl -w net.ipv6.conf.eth1.disable_ipv6=0 set +e ip -6 addr del 2001:db8:2::2/64 dev eth1 2>/dev/null set -e ip -6 addr add 2001:db8:2::2/64 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.1 # 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.1 # 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.1 # 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.1 # # Print the final routing table ip route ok: [x2] => msg: |- initial configuration for x2 ========================================= #!/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 sysctl -w net.ipv6.conf.eth1.disable_ipv6=0 set +e ip -6 addr del 2001:db8:2:1::3/64 dev eth1 2>/dev/null set -e ip -6 addr add 2001:db8:2:1::3/64 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.1 # 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.1 # 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.1 # 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.1 # # Print the final routing table ip route ok: [dut] => msg: |- initial configuration for dut ========================================= hostname dut ! no ip domain lookup ! lldp run ! ip host dut-blue 172.16.1.1 ip host dut-red 172.16.0.1 ip host x1 172.16.0.2 ip host x2 172.16.1.3 ! ip routing ! ipv6 unicast-routing ! vrf definition blue rd 65000:2 route-target import 65000:2 route-target export 65000:2 ! address-family ipv4 exit-address-family ! address-family ipv6 exit-address-family ! vrf definition red rd 65000:1 route-target import 65000:1 route-target export 65000:1 ! address-family ipv4 exit-address-family ! address-family ipv6 exit-address-family ! ! ! interface Loopback0 ip address 10.0.0.1 255.255.255.255 ipv6 address 2001:DB8:1:1::1/64 ! interface Ethernet0/0 no lldp transmit no lldp receive ! interface Ethernet0/1 no shutdown no switchport vrf forwarding red description dut -> x1 [stub] mtu 1500 ip address 172.16.0.1 255.255.255.0 ipv6 address 2001:DB8:2::1/64 ! interface Ethernet0/2 no shutdown no switchport vrf forwarding blue description dut -> x2 [stub] mtu 1500 ip address 172.16.1.1 255.255.255.0 ipv6 address 2001:DB8:2:1::1/64 ! ! line vty 0 4 exec-timeout 0 0 ! no banner exec no banner login no banner incoming TASK [Find configuration deployment deploy_script for initial] ***************** ok: [x1] ok: [x2] ok: [dut] TASK [Deploy initial configuration] ******************************************** included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/ios.yml for dut included: /home/pipi/net101/tools/netsim/ansible/tasks/linux/initial-clab.yml for x1, x2 TASK [ios_config: deploying initial from /home/pipi/net101/tools/netsim/ansible/templates/initial/ios.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: [dut] TASK [set_fact] **************************************************************** ok: [x1] ok: [x2] TASK [Create initial container setup from /home/pipi/net101/tools/netsim/ansible/templates/initial/linux-clab.j2] *** changed: [x2 -> localhost] changed: [x1 -> localhost] TASK [Initial container configuration via /tmp/config-zdmETTKI-x1.sh] ********** changed: [x2 -> localhost] changed: [x1 -> localhost] TASK [file] ******************************************************************** changed: [x2 -> localhost] changed: [x1 -> localhost] PLAY [Deploy module-specific configurations] *********************************** TASK [Set variables that cannot be set with VARS] ****************************** ok: [dut] TASK [Deploy individual configuration modules] ********************************* included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-module.yml for dut => (item=routing) included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-module.yml for dut => (item=vrf) TASK [Figure out whether to deploy the module routing on current device] ******* ok: [dut] TASK [Find configuration template for routing] ********************************* ok: [dut] TASK [Print deployed configuration when running in verbose mode] *************** ok: [dut] => msg: |- routing configuration for dut ========================================= ! ! ! AS-path access lists ! ! ! Static routes ! ip route vrf blue 172.16.0.0 255.255.255.0 Ethernet0/1 172.16.0.2 ipv6 route vrf blue 2001:db8:2::/64 Ethernet0/1 2001:db8:2::2 ip route vrf red 172.16.1.0 255.255.255.0 Ethernet0/2 172.16.1.3 ipv6 route vrf red 2001:db8:2:1::/64 Ethernet0/2 2001:db8:2:1::3 TASK [Find configuration deployment deploy_script for routing] ***************** ok: [dut] TASK [Deploy routing configuration] ******************************************** included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/ios.yml for dut TASK [ios_config: deploying routing from /home/pipi/net101/tools/netsim/ansible/templates/routing/ios.j2] *** changed: [dut] TASK [Figure out whether to deploy the module vrf on current device] *********** ok: [dut] TASK [Find configuration template for vrf] ************************************* ok: [dut] TASK [Print deployed configuration when running in verbose mode] *************** ok: [dut] => msg: |- vrf configuration for dut ========================================= TASK [Find configuration deployment deploy_script for vrf] ********************* ok: [dut] TASK [Deploy vrf configuration] ************************************************ included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/ios.yml for dut TASK [ios_config: deploying vrf from /home/pipi/net101/tools/netsim/ansible/templates/vrf/ios.j2] *** ok: [dut] PLAY [Deploy custom deployment templates] ************************************** skipping: no hosts matched PLAY RECAP ********************************************************************* dut : ok=28 changed=2 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 x1 : ok=12 changed=3 unreachable=0 failed=0 skipped=1 rescued=0 ignored=0 x2 : ok=12 changed=3 unreachable=0 failed=0 skipped=1 rescued=0 ignored=0 Use this topology to test inter- VRF IPv4 and IPv6 static routes. DUT has to have static routes for loopback addresses of X1 and X2.