[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: [h2] ok: [s1] TASK [Find device readiness script] ******************************************** ok: [h1] ok: [h2] ok: [s1] TASK [Wait for device to become ready] ***************************************** skipping: [h1] skipping: [h2] included: /home/pipi/net101/tools/netsim/ansible/tasks/readiness-check/routeros7.yml for s1 TASK [Execute local ssh command to check router readiness] ********************* skipping: [s1] TASK [Deploy initial configuration] ******************************************** included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-module.yml for h1, h2, s1 TASK [Figure out whether to deploy the module initial on current device] ******* ok: [h1] ok: [h2] ok: [s1] TASK [Find configuration template for initial] ********************************* ok: [h1] ok: [h2] ok: [s1] TASK [Print deployed configuration when running in verbose mode] *************** ok: [s1] => msg: |- initial configuration for s1 ========================================= /system identity set name="s1" /interface bridge add name=loopback protocol-mode=none /ip address add interface=loopback address=10.0.0.3/32 /interface/bridge/add name=switch vlan-filtering=yes comment="Global Switch Bridge" /interface/vlan/add name=vlan1000 vlan-id=1000 interface=switch /interface ethernet set comment="VLAN red (1000) -> [h1,h2] [stub]" vlan1000 /ip address add interface=vlan1000 address=172.16.0.3/24 /ip address set [find where interface=vlan1000] comment="VLAN red (1000) -> [h1,h2] [stub]" /ip neighbor discovery-settings set discover-interface-list=all 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.3 # 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.3 # 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.3 # 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.3 # # 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.3 # 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.3 # 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.3 # 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.3 # # Print the final routing table ip route TASK [Find configuration deployment deploy_script for initial] ***************** ok: [h1] ok: [h2] ok: [s1] TASK [Deploy initial configuration] ******************************************** included: /home/pipi/net101/tools/netsim/ansible/tasks/linux/initial-clab.yml for h1, h2 included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/routeros7.yml for s1 TASK [set_fact] **************************************************************** ok: [h1] ok: [h2] TASK [Create initial container setup from /home/pipi/net101/tools/netsim/ansible/templates/initial/linux-clab.j2] *** changed: [h2 -> localhost] changed: [h1 -> localhost] TASK [Initial container configuration via /tmp/config-bLsLDtjf-h1.sh] ********** changed: [h1 -> localhost] changed: [h2 -> localhost] TASK [file] ******************************************************************** changed: [h1 -> localhost] changed: [h2 -> localhost] TASK [load initial from /home/pipi/net101/tools/netsim/ansible/templates/initial/routeros7.j2] *** ok: [s1] TASK [Run commands on CHR] ***************************************************** changed: [s1] PLAY [Deploy module-specific configurations] *********************************** TASK [Set variables that cannot be set with VARS] ****************************** ok: [s1] TASK [Deploy individual configuration modules] ********************************* included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-module.yml for s1 => (item=vlan) TASK [Figure out whether to deploy the module vlan on current device] ********** ok: [s1] TASK [Find configuration template for vlan] ************************************ ok: [s1] TASK [Print deployed configuration when running in verbose mode] *************** ok: [s1] => msg: |- vlan configuration for s1 ========================================= /interface/bridge/vlan add bridge=switch vlan-ids=1000 tagged=switch /interface/bridge/port add bridge=switch interface=ether2 pvid=1000 /interface/bridge/vlan set untagged=([get value-name=untagged [find vlan-ids=1000]],"ether2") [find vlan-ids=1000] /interface/bridge/port add bridge=switch interface=ether3 pvid=1000 /interface/bridge/vlan set untagged=([get value-name=untagged [find vlan-ids=1000]],"ether3") [find vlan-ids=1000] TASK [Find configuration deployment deploy_script for vlan] ******************** ok: [s1] TASK [Deploy vlan configuration] *********************************************** included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/routeros7.yml for s1 TASK [load vlan from /home/pipi/net101/tools/netsim/ansible/templates/vlan/routeros7.j2] *** ok: [s1] TASK [Run commands on CHR] ***************************************************** 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 s1 : ok=20 changed=2 unreachable=0 failed=0 skipped=1 rescued=0 ignored=0 The device under test is a layer-3 switch bridging VLAN between ports and having an IP address in the red VLAN h1 and h2 should be able to ping s1 and each other