[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: [pe2] ok: [p1] ok: [p2] ok: [dut] ok: [h1] ok: [h3] ok: [h2] ok: [h4] TASK [Find device readiness script] ******************************************** ok: [pe2] ok: [p1] ok: [p2] ok: [dut] ok: [h1] ok: [h3] ok: [h2] ok: [h4] TASK [Wait for device to become ready] ***************************************** skipping: [pe2] skipping: [p1] skipping: [p2] skipping: [h1] skipping: [h2] skipping: [h3] skipping: [h4] included: /home/pipi/net101/tools/netsim/ansible/tasks/readiness-check/vjunos-switch-clab.yml for dut TASK [Wait for SSH server] ***************************************************** included: /home/pipi/net101/tools/netsim/ansible/tasks/readiness-check/vm-clab-ssh-check.yml for dut TASK [Execute local ssh command to check vjunos-switch readiness] ************** FAILED - RETRYING: [dut -> localhost]: Execute local ssh command to check vjunos-switch readiness (40 retries left). FAILED - RETRYING: [dut -> localhost]: Execute local ssh command to check vjunos-switch readiness (39 retries left). changed: [dut -> localhost] TASK [Confirm dut SSH server works] ******************************************** ok: [dut] => msg: Node dut is ready. TASK [Wait for ge-0/0/0 interface] ********************************************* included: /home/pipi/net101/tools/netsim/ansible/tasks/readiness-check/vjunos-switch.yml for dut TASK [Wait for ge-0/0/0 to appear] ********************************************* ok: [dut] TASK [Deploy initial configuration] ******************************************** included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-module.yml for dut, pe2, p1, p2, h1, h2, h3, h4 TASK [Figure out whether to deploy the module initial on current device] ******* ok: [pe2] ok: [p1] ok: [dut] ok: [p2] ok: [h1] ok: [h2] ok: [h3] ok: [h4] TASK [Find configuration template for initial] ********************************* ok: [pe2] ok: [p1] ok: [dut] ok: [p2] ok: [h2] ok: [h1] ok: [h4] ok: [h3] TASK [Print deployed configuration when running in verbose mode] *************** 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.1.2/24 dev eth1 2>/dev/null set -e ip addr add 172.16.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) # # 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.6 # 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.6 # 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.6 # 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.6 # # Print the final routing table ip route ok: [dut] => msg: |- initial configuration for dut ========================================= system { host-name dut static-host-mapping { pe2 inet 10.0.0.6; p1 inet 10.0.0.7; p2 inet 10.0.0.8; h1 inet 172.16.0.1; h2 inet 172.16.1.2; h3 inet 172.16.2.3; h4 inet 172.16.3.4; } } policy-options { community tg_65000_1 members target:65000:1; community tg_65000_2 members target:65000:2; } policy-options { policy-statement vrf-t1-export { term 1 { then { community add tg_65000_1; accept; } } } policy-statement vrf-t1-import { term 1 { from community [ tg_65000_1 ]; then accept; } term default { then reject; } } policy-statement vrf-t2-export { term 1 { then { community add tg_65000_2; accept; } } } policy-statement vrf-t2-import { term 1 { from community [ tg_65000_2 ]; then accept; } term default { then reject; } } } routing-instances { t1 { instance-type vrf; route-distinguisher 65000:1; vrf-import vrf-t1-import; vrf-export vrf-t1-export; routing-options { auto-export; } interface ge-0/0/1.0; } t2 { instance-type vrf; route-distinguisher 65000:2; vrf-import vrf-t2-import; vrf-export vrf-t2-export; routing-options { auto-export; } interface ge-0/0/2.0; } } 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 { description "dut -> p1"; family inet { address 10.1.0.1/30; } } ge-0/0/1.0 { description "dut -> h1 [stub]"; family inet { address 172.16.0.5/24; } } ge-0/0/2.0 { description "dut -> h3 [stub]"; family inet { address 172.16.2.5/24; } } } protocols { lldp { interface fxp0 { disable; } interface all; } } ok: [pe2] => msg: |- initial configuration for pe2 ========================================= #!/bin/bash # set -e set -x # # Create bash profile script # cat <