[WARNING]: Invalid characters were found in group names but not replaced, use -vvvv to see details [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: [h3] ok: [h4] ok: [s2] ok: [s1] TASK [Find device readiness script] ******************************************** ok: [h1] ok: [h2] 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/vjunos-switch-clab.yml for s1, s2 TASK [Wait for SSH server] ***************************************************** included: /home/pipi/net101/tools/netsim/ansible/tasks/readiness-check/vm-clab-ssh-check.yml for s1, s2 TASK [Execute local ssh command to check vjunos-switch readiness] ************** FAILED - RETRYING: [s1 -> localhost]: Execute local ssh command to check vjunos-switch readiness (40 retries left). FAILED - RETRYING: [s2 -> localhost]: Execute local ssh command to check vjunos-switch readiness (40 retries left). FAILED - RETRYING: [s2 -> localhost]: Execute local ssh command to check vjunos-switch readiness (39 retries left). FAILED - RETRYING: [s1 -> localhost]: Execute local ssh command to check vjunos-switch readiness (39 retries left). changed: [s2 -> localhost] changed: [s1 -> localhost] TASK [Confirm s1 SSH server works] ********************************************* ok: [s1] => msg: Node s1 is ready. ok: [s2] => msg: Node s2 is ready. TASK [Wait for ge-0/0/0 interface] ********************************************* included: /home/pipi/net101/tools/netsim/ansible/tasks/readiness-check/vjunos-switch.yml for s1, s2 TASK [Wait for ge-0/0/0 to appear] ********************************************* ok: [s2] ok: [s1] TASK [Deploy initial configuration] ******************************************** included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-module.yml for h1, h2, h3, h4, s1, s2 TASK [Figure out whether to deploy the module initial on current device] ******* ok: [h1] ok: [h2] ok: [h3] ok: [h4] ok: [s1] ok: [s2] TASK [Find configuration template for initial] ********************************* ok: [h1] ok: [h2] ok: [h3] ok: [h4] 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.31.1.1/24 dev eth1 2>/dev/null set -e ip addr add 172.31.1.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) # # # 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.31.1.2/24 dev eth1 2>/dev/null set -e ip addr add 172.31.1.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) # # # Print the final routing table ip route 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.31.1.3/24 dev eth1 2>/dev/null set -e ip addr add 172.31.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) # # # 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.31.1.4/24 dev eth1 2>/dev/null set -e ip addr add 172.31.1.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) # # # Print the final routing table ip route ok: [s2] => msg: |- initial configuration for s2 ========================================= system { host-name s2 static-host-mapping { h1 inet 172.31.1.1; h2 inet 172.31.1.2; h3 inet 172.31.1.3; h4 inet 172.31.1.4; s1 inet 10.0.0.5; } } interfaces { ge-0/0/0 { flexible-vlan-tagging; native-vlan-id 1000; } ge-0/0/0.0 { vlan-id 1000; } ge-0/0/1 { flexible-vlan-tagging; native-vlan-id 1000; } ge-0/0/1.0 { vlan-id 1000; } ge-0/0/2 { flexible-vlan-tagging; native-vlan-id 1001; } ge-0/0/2.0 { vlan-id 1001; } } interfaces { ge-0/0/0 { mtu 1514; } ge-0/0/1 { mtu 1514; } ge-0/0/2 { mtu 1514; } lo0.0 { family inet { address 10.0.0.6/32; } } ge-0/0/0.0 { } ge-0/0/1.0 { } ge-0/0/2.0 { } irb.1000 { description "VLAN red (1000) -> [s1,h1,h2]"; } irb.1001 { description "VLAN blue (1001) -> [h3,s1,h4]"; } } protocols { lldp { interface fxp0 { disable; } interface all; } } ok: [s1] => msg: |- initial configuration for s1 ========================================= system { host-name s1 static-host-mapping { h1 inet 172.31.1.1; h2 inet 172.31.1.2; h3 inet 172.31.1.3; h4 inet 172.31.1.4; s2 inet 10.0.0.6; } } interfaces { ge-0/0/0 { flexible-vlan-tagging; native-vlan-id 1000; } ge-0/0/0.0 { vlan-id 1000; } ge-0/0/1 { flexible-vlan-tagging; native-vlan-id 1000; } ge-0/0/1.0 { vlan-id 1000; } ge-0/0/2 { flexible-vlan-tagging; native-vlan-id 1001; } ge-0/0/2.0 { vlan-id 1001; } } interfaces { ge-0/0/0 { mtu 1514; } ge-0/0/1 { mtu 1514; } ge-0/0/2 { mtu 1514; } lo0.0 { family inet { address 10.0.0.5/32; } } ge-0/0/0.0 { } ge-0/0/1.0 { } ge-0/0/2.0 { } irb.1000 { description "VLAN red (1000) -> [s2,h1,h2]"; } irb.1001 { description "VLAN blue (1001) -> [h3,s2,h4]"; } } protocols { lldp { interface fxp0 { disable; } interface all; } } TASK [Find configuration deployment deploy_script for initial] ***************** ok: [h1] ok: [h2] ok: [h3] ok: [h4] ok: [s1] ok: [s2] TASK [Deploy initial configuration] ******************************************** included: /home/pipi/net101/tools/netsim/ansible/tasks/linux/initial-clab.yml for h1, h2, h3, h4 included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/junos.yml for s1, s2 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: [h1 -> localhost] changed: [h3 -> localhost] changed: [h2 -> localhost] changed: [h4 -> localhost] TASK [Initial container configuration via /tmp/config-wVGHClBi-h1.sh] ********** changed: [h3 -> localhost] changed: [h2 -> localhost] changed: [h1 -> localhost] changed: [h4 -> localhost] TASK [file] ******************************************************************** changed: [h4 -> localhost] changed: [h1 -> localhost] changed: [h2 -> localhost] changed: [h3 -> localhost] TASK [junos_config: deploying initial from /home/pipi/net101/tools/netsim/ansible/templates/initial/junos.j2] *** changed: [s2] changed: [s1] PLAY [Deploy module-specific configurations] *********************************** TASK [Set variables that cannot be set with VARS] ****************************** ok: [s2] ok: [s1] TASK [Deploy individual configuration modules] ********************************* included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-module.yml for s1, s2 => (item=vlan) 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 ========================================= vlans { blue { vlan-id 1001; } red { vlan-id 1000; } } interfaces { ge-0/0/0.0 { family ethernet-switching { interface-mode trunk; vlan { members [ blue red ]; } } } ge-0/0/0 { native-vlan-id 1000; } ge-0/0/1.0 { family ethernet-switching { vlan { members red; } } } ge-0/0/2.0 { family ethernet-switching { vlan { members blue; } } } } ok: [s2] => msg: |- vlan configuration for s2 ========================================= vlans { blue { vlan-id 1001; } red { vlan-id 1000; } } interfaces { ge-0/0/0.0 { family ethernet-switching { interface-mode trunk; vlan { members [ blue red ]; } } } ge-0/0/0 { native-vlan-id 1000; } ge-0/0/1.0 { family ethernet-switching { vlan { members red; } } } ge-0/0/2.0 { family ethernet-switching { vlan { members blue; } } } } 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/junos.yml for s1, s2 TASK [junos_config: deploying vlan from /home/pipi/net101/tools/netsim/ansible/templates/vlan/vjunos-switch.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=23 changed=3 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 s2 : ok=23 changed=3 unreachable=0 failed=0 skipped=0 rescued=0 ignored=0 The devices under test are simple bridges with a VLAN trunk between them. One of the trunk members is a native VLAN. Both VLANs are using the same IP prefix to identify potential inter-VLAN leaking. * h1 and h2 should be able to ping each other * h3 and h4 should be able to ping each other * h1 should not be able to reach h3 Please note it might take a while for the lab to work due to STP learning phase