[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: [h4] ok: [h3] ok: [dut] TASK [Find device readiness script] ******************************************** ok: [h1] ok: [h2] ok: [h3] ok: [h4] ok: [dut] TASK [Wait for device to become ready] ***************************************** skipping: [h1] skipping: [h2] skipping: [h3] skipping: [h4] skipping: [dut] TASK [Deploy initial configuration] ******************************************** included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-module.yml for h1, h2, h3, h4, dut TASK [Figure out whether to deploy the module initial on current device] ******* ok: [h1] ok: [h2] ok: [h3] ok: [h4] ok: [dut] TASK [Find configuration template for initial] ********************************* ok: [h1] ok: [h2] ok: [h3] ok: [h4] ok: [dut] 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: [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.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: [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.2.3/24 dev eth1 2>/dev/null set -e ip addr add 172.16.2.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.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.5 # 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.5 # 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.5 # 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.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.3.4/24 dev eth1 2>/dev/null set -e ip addr add 172.16.3.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.3.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.3.5 # loopback prefix: 10.0.0.0/24 local subnet: 172.16.3.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.3.5 # mgmt prefix: 192.168.17.0/24 local subnet: 172.16.3.0/24 # p2p prefix: 10.1.0.0/16 local subnet: 172.16.3.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.3.5 # router_id prefix: 10.0.0.0/24 local subnet: 172.16.3.0/24 # vrf_loopback prefix: 10.2.0.0/24 local subnet: 172.16.3.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.3.5 # # Print the final routing table ip route ok: [dut] => msg: |- initial configuration for dut ========================================= updates: - path: /interface[name=system0]/subinterface[index=0] value: description: "No description" ipv4: admin-state: enable address: - ip-prefix: "10.0.0.5/32" - path: /interface[name=ethernet-1/1] value: subinterface: index: 0 description: "dut ~ h1" - path: /interface[name=ethernet-1/1]/subinterface[index=0] value: description: "dut ~ h1" ipv4: admin-state: enable address: - ip-prefix: "172.16.0.5/24" primary: [null] - path: /interface[name=ethernet-1/2] value: subinterface: index: 0 description: "dut ~ h2" - path: /interface[name=ethernet-1/2]/subinterface[index=0] value: description: "dut ~ h2" ipv4: admin-state: enable address: - ip-prefix: "172.16.1.5/24" primary: [null] - path: /interface[name=ethernet-1/3] value: subinterface: index: 0 description: "dut ~ h3" - path: /interface[name=ethernet-1/3]/subinterface[index=0] value: description: "dut ~ h3" ipv4: admin-state: enable address: - ip-prefix: "172.16.2.5/24" primary: [null] - path: /interface[name=ethernet-1/4] value: subinterface: index: 0 description: "dut ~ h4" - path: /interface[name=ethernet-1/4]/subinterface[index=0] value: description: "dut ~ h4" ipv4: admin-state: enable address: - ip-prefix: "172.16.3.5/24" primary: [null] - path: /interface[name=lo0] value: subinterface: index: 1 description: "VRF Loopback red" - path: /interface[name=lo0]/subinterface[index=1] value: description: "VRF Loopback red" ipv4: admin-state: enable address: - ip-prefix: "10.0.0.42/32" primary: [null] - path: /interface[name=lo0] value: subinterface: index: 2 description: "VRF Loopback blue" - path: /interface[name=lo0]/subinterface[index=2] value: description: "VRF Loopback blue" ipv4: admin-state: enable address: - ip-prefix: "10.0.0.43/32" primary: [null] - path: /network-instance[name=default] value: type: default interface: - name: system0.0 # TODO: vdata.rd, vdata.import/export, vdata.af - path: /network-instance[name=blue] value: type: ip-vrf interface: - name: ethernet-1/3.0 - path: /network-instance[name=blue] value: type: ip-vrf interface: - name: ethernet-1/4.0 - path: /network-instance[name=blue] value: type: ip-vrf interface: - name: lo0.2 # TODO: vdata.rd, vdata.import/export, vdata.af - path: /network-instance[name=red] value: type: ip-vrf interface: - name: ethernet-1/1.0 - path: /network-instance[name=red] value: type: ip-vrf interface: - name: ethernet-1/2.0 - path: /network-instance[name=red] value: type: ip-vrf interface: - name: lo0.1 TASK [Find configuration deployment deploy_script for initial] ***************** ok: [h1] ok: [h2] ok: [h3] ok: [dut] ok: [h4] 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/srlinux.yml for dut 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: [h2 -> localhost] changed: [h3 -> localhost] changed: [h1 -> localhost] changed: [h4 -> localhost] TASK [Initial container configuration via /tmp/config-bMhwjkaO-h1.sh] ********** changed: [h2 -> localhost] changed: [h1 -> localhost] changed: [h4 -> localhost] changed: [h3 -> localhost] TASK [file] ******************************************************************** changed: [h3 -> localhost] changed: [h2 -> localhost] changed: [h4 -> localhost] changed: [h1 -> localhost] TASK [Generate JSON-RPC YAML configuration] ************************************ ok: [dut] TASK [Update SRL initial node configuration (template=/home/pipi/net101/tools/netsim/ansible/templates/initial/srlinux.j2)] *** changed: [dut] TASK [debug] ******************************************************************* skipping: [dut] 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=vrf) 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 ========================================= updates: - path: /network-instance[name=blue] value: type: ip-vrf - path: /routing-policy/community-set[name=C65000_2] value: member: - "target:65000:2" # Single member, else matching is AND - path: /routing-policy/community-set[name=blue_export] value: member: - "target:65000:2" - path: /network-instance[name=blue]/protocols/bgp-vpn value: bgp-instance: - id: 1 route-distinguisher: rd: "65000:2" - path: /network-instance[name=blue]/inter-instance-policies value: apply-policy: export-policy: "blue_vpn_export" import-policy: "blue_vpn_import" - path: /routing-policy/policy[name=blue_vpn_export] value: default-action: policy-result: "accept" bgp: communities: add: "blue_export" - path: /routing-policy/policy[name=blue_vpn_import] value: default-action: policy-result: "reject" statement: - name: 11 match: bgp: community-set: "C65000_2" action: policy-result: "accept" - path: /network-instance[name=red] value: type: ip-vrf - path: /routing-policy/community-set[name=C65000_1] value: member: - "target:65000:1" # Single member, else matching is AND - path: /routing-policy/community-set[name=red_export] value: member: - "target:65000:1" - path: /network-instance[name=red]/protocols/bgp-vpn value: bgp-instance: - id: 1 route-distinguisher: rd: "65000:1" - path: /network-instance[name=red]/inter-instance-policies value: apply-policy: export-policy: "red_vpn_export" import-policy: "red_vpn_import" - path: /routing-policy/policy[name=red_vpn_export] value: default-action: policy-result: "accept" bgp: communities: add: "red_export" - path: /routing-policy/policy[name=red_vpn_import] value: default-action: policy-result: "reject" statement: - name: 11 match: bgp: community-set: "C65000_1" action: policy-result: "accept" TASK [Find configuration deployment deploy_script for vrf] ********************* ok: [dut] TASK [Deploy vrf configuration] ************************************************ included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/srlinux.yml for dut TASK [Generate JSON-RPC YAML configuration] ************************************ ok: [dut] TASK [Update SRL vrf node configuration (template=/home/pipi/net101/tools/netsim/ansible/templates/vrf/srlinux.j2)] *** changed: [dut] TASK [debug] ******************************************************************* skipping: [dut] PLAY [Deploy custom deployment templates] ************************************** skipping: no hosts matched PLAY RECAP ********************************************************************* dut : ok=19 changed=2 unreachable=0 failed=0 skipped=3 rescued=0 ignored=0 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 The device under test has two VRFs with two interfaces in each VRF. Each VRF has a loopback interface. * h1 and h2 should be able to ping each other and the VRF loopback interface * h3 and h4 should be able to ping each other and the VRF loopback interface * h1 should not be able to reach h3