[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: [h5]
ok: [h6]
ok: [s1]
ok: [s2]
ok: [s3]

TASK [Find device readiness script] ********************************************
ok: [h1]
ok: [s1]
ok: [h2]
ok: [h4]
ok: [h3]
ok: [h6]
ok: [h5]
ok: [s2]
ok: [s3]

TASK [Wait for device to become ready] *****************************************
skipping: [s1]
skipping: [s2]
skipping: [s3]
skipping: [h1]
skipping: [h2]
skipping: [h3]
skipping: [h4]
skipping: [h5]
skipping: [h6]

TASK [Deploy initial configuration] ********************************************
included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-module.yml for s1, s2, s3, h1, h2, h3, h4, h5, h6

TASK [Figure out whether to deploy the module initial on current device] *******
ok: [h1]
ok: [h2]
ok: [s1]
ok: [h3]
ok: [h4]
ok: [h6]
ok: [h5]
ok: [s3]
ok: [s2]

TASK [Find configuration template for initial] *********************************
ok: [h1]
ok: [s1]
ok: [h2]
ok: [h3]
ok: [h5]
ok: [h4]
ok: [h6]
ok: [s2]
ok: [s3]

TASK [Print deployed configuration when running in verbose mode] ***************
ok: [h5] => 
  msg: |-
    initial configuration for h5
    =========================================
    #!/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.5/24 dev eth1 2>/dev/null
    set -e
    ip addr add 172.16.1.5/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: [s1] => 
  msg: |-
    initial configuration for s1
    =========================================
    hostname s1
    !
    no ip domain lookup
    !
    lldp run
    !
    ip host h1 172.16.0.1
    ip host h2 172.16.0.2
    ip host h3 172.16.0.3
    ip host h4 172.16.1.4
    ip host h5 172.16.1.5
    ip host h6 172.16.1.6
    ip host s2 10.0.0.8 10.1.0.2 10.1.0.5
    ip host s3 10.0.0.9 10.1.0.6 10.1.0.10
    !
  
    !
    !
    interface Loopback0
     ip address 10.0.0.7 255.255.255.255
    !
    interface GigabitEthernet1
     no lldp transmit
     no lldp receive
    !
    interface GigabitEthernet2
     no shutdown
     description s1 -> s2
     mtu 1600
     ip address 10.1.0.1 255.255.255.252
    !
    interface GigabitEthernet3
     no shutdown
     description s1 -> s3
     mtu 1600
     ip address 10.1.0.9 255.255.255.252
    !
    interface GigabitEthernet4
     no shutdown
    !
    interface GigabitEthernet5
     no shutdown
    !
    interface BDI1000
     no shutdown
     description VLAN red (1000) -> [h1,h2,s2,h3,s3]
    !
    interface BDI1001
     no shutdown
     description VLAN blue (1001) -> [h4,h5,s2,h6,s3]
    !
    no banner exec
    no banner login
    no banner incoming
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)
    #
    #
    # Print the final routing table
    ip route
ok: [s2] => 
  msg: |-
    initial configuration for s2
    =========================================
    hostname s2
    !
    no ip domain lookup
    !
    lldp run
    !
    ip host h1 172.16.0.1
    ip host h2 172.16.0.2
    ip host h3 172.16.0.3
    ip host h4 172.16.1.4
    ip host h5 172.16.1.5
    ip host h6 172.16.1.6
    ip host s1 10.0.0.7 10.1.0.1 10.1.0.9
    ip host s3 10.0.0.9 10.1.0.6 10.1.0.10
    !
  
    !
    !
    interface Loopback0
     ip address 10.0.0.8 255.255.255.255
    !
    interface GigabitEthernet1
     no lldp transmit
     no lldp receive
    !
    interface GigabitEthernet2
     no shutdown
     description s2 -> s1
     mtu 1600
     ip address 10.1.0.2 255.255.255.252
    !
    interface GigabitEthernet3
     no shutdown
     description s2 -> s3
     mtu 1600
     ip address 10.1.0.5 255.255.255.252
    !
    interface GigabitEthernet4
     no shutdown
    !
    interface GigabitEthernet5
     no shutdown
    !
    interface BDI1000
     no shutdown
     description VLAN red (1000) -> [h1,s1,h2,h3,s3]
    !
    interface BDI1001
     no shutdown
     description VLAN blue (1001) -> [h4,s1,h5,h6,s3]
    !
    no banner exec
    no banner login
    no banner incoming
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)
    #
    #
    # 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.0.3/24 dev eth1 2>/dev/null
    set -e
    ip addr add 172.16.0.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.16.1.4/24 dev eth1 2>/dev/null
    set -e
    ip addr add 172.16.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: [h6] => 
  msg: |-
    initial configuration for h6
    =========================================
    #!/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.6/24 dev eth1 2>/dev/null
    set -e
    ip addr add 172.16.1.6/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: [s3] => 
  msg: |-
    initial configuration for s3
    =========================================
    hostname s3
    !
    no ip domain lookup
    !
    lldp run
    !
    ip host h1 172.16.0.1
    ip host h2 172.16.0.2
    ip host h3 172.16.0.3
    ip host h4 172.16.1.4
    ip host h5 172.16.1.5
    ip host h6 172.16.1.6
    ip host s1 10.0.0.7 10.1.0.1 10.1.0.9
    ip host s2 10.0.0.8 10.1.0.2 10.1.0.5
    !
  
    !
    !
    interface Loopback0
     ip address 10.0.0.9 255.255.255.255
    !
    interface GigabitEthernet1
     no lldp transmit
     no lldp receive
    !
    interface GigabitEthernet2
     no shutdown
     description s3 -> s2
     mtu 1600
     ip address 10.1.0.6 255.255.255.252
    !
    interface GigabitEthernet3
     no shutdown
     description s3 -> s1
     mtu 1600
     ip address 10.1.0.10 255.255.255.252
    !
    interface GigabitEthernet4
     no shutdown
    !
    interface GigabitEthernet5
     no shutdown
    !
    interface BDI1000
     no shutdown
     description VLAN red (1000) -> [h1,s1,h2,s2,h3]
    !
    interface BDI1001
     no shutdown
     description VLAN blue (1001) -> [h4,s1,h5,s2,h6]
    !
    no banner exec
    no banner login
    no banner incoming

TASK [Find configuration deployment deploy_script for initial] *****************
ok: [h2]
ok: [h1]
ok: [s1]
ok: [h3]
ok: [h5]
ok: [h4]
ok: [h6]
ok: [s2]
ok: [s3]

TASK [Deploy initial configuration] ********************************************
included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/ios.yml for s1, s2, s3
included: /home/pipi/net101/tools/netsim/ansible/tasks/linux/initial-clab.yml for h1, h2, h3, h4, h5, h6

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: [s1]
changed: [s2]
changed: [s3]

TASK [set_fact] ****************************************************************
ok: [h1]
ok: [h2]
ok: [h4]
ok: [h3]
ok: [h5]
ok: [h6]

TASK [Create initial container setup from /home/pipi/net101/tools/netsim/ansible/templates/initial/linux-clab.j2] ***
changed: [h5 -> localhost]
changed: [h3 -> localhost]
changed: [h2 -> localhost]
changed: [h1 -> localhost]
changed: [h6 -> localhost]
changed: [h4 -> localhost]

TASK [Initial container configuration via /tmp/config-YwBDpzvz-h1.sh] **********
changed: [h1 -> localhost]
changed: [h4 -> localhost]
changed: [h2 -> localhost]
changed: [h3 -> localhost]
changed: [h5 -> localhost]
changed: [h6 -> localhost]

TASK [file] ********************************************************************
changed: [h1 -> localhost]
changed: [h6 -> localhost]
changed: [h4 -> localhost]
changed: [h2 -> localhost]
changed: [h5 -> localhost]
changed: [h3 -> localhost]

PLAY [Deploy module-specific configurations] ***********************************

TASK [Set variables that cannot be set with VARS] ******************************
ok: [s1]
ok: [s3]
ok: [s2]

TASK [Deploy individual configuration modules] *********************************
included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-module.yml for s1, s2, s3 => (item=vlan)
included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-module.yml for s1, s2, s3 => (item=ospf)
included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-module.yml for s1, s2, s3 => (item=vxlan)

TASK [Figure out whether to deploy the module vlan on current device] **********
ok: [s1]
ok: [s2]
ok: [s3]

TASK [Find configuration template for vlan] ************************************
ok: [s1]
ok: [s3]
ok: [s2]

TASK [Print deployed configuration when running in verbose mode] ***************
ok: [s3] => 
  msg: |-
    vlan configuration for s3
    =========================================
    !
    bridge-domain 1001
     member GigabitEthernet5 service-instance 1001
    !
    bridge-domain 1000
     member GigabitEthernet4 service-instance 1000
    !
    interface GigabitEthernet4
     service instance 1000 ethernet
      encapsulation untagged
    !
    interface GigabitEthernet5
     service instance 1001 ethernet
      encapsulation untagged
ok: [s2] => 
  msg: |-
    vlan configuration for s2
    =========================================
    !
    bridge-domain 1001
     member GigabitEthernet5 service-instance 1001
    !
    bridge-domain 1000
     member GigabitEthernet4 service-instance 1000
    !
    interface GigabitEthernet4
     service instance 1000 ethernet
      encapsulation untagged
    !
    interface GigabitEthernet5
     service instance 1001 ethernet
      encapsulation untagged
ok: [s1] => 
  msg: |-
    vlan configuration for s1
    =========================================
    !
    bridge-domain 1001
     member GigabitEthernet5 service-instance 1001
    !
    bridge-domain 1000
     member GigabitEthernet4 service-instance 1000
    !
    interface GigabitEthernet4
     service instance 1000 ethernet
      encapsulation untagged
    !
    interface GigabitEthernet5
     service instance 1001 ethernet
      encapsulation untagged

TASK [Find configuration deployment deploy_script for vlan] ********************
ok: [s1]
ok: [s2]
ok: [s3]

TASK [Deploy vlan configuration] ***********************************************
included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/ios.yml for s1, s2, s3

TASK [ios_config: deploying vlan from /home/pipi/net101/tools/netsim/ansible/templates/vlan/csr.j2] ***
changed: [s1]
changed: [s2]
changed: [s3]

TASK [Figure out whether to deploy the module ospf on current device] **********
ok: [s2]
ok: [s1]
ok: [s3]

TASK [Find configuration template for ospf] ************************************
ok: [s1]
ok: [s2]
ok: [s3]

TASK [Print deployed configuration when running in verbose mode] ***************
ok: [s1] => 
  msg: |-
    ospf configuration for s1
    =========================================
    router ospf 1
     router-id 10.0.0.7
  
    !
    interface Loopback0
    !
     ip ospf 1 area 0.0.0.0
    !
    interface GigabitEthernet2
    ! s1 -> s2
     ip ospf 1 area 0.0.0.0
     ip ospf network point-to-point
    !
    interface GigabitEthernet3
    ! s1 -> s3
     ip ospf 1 area 0.0.0.0
     ip ospf network point-to-point
    !
ok: [s3] => 
  msg: |-
    ospf configuration for s3
    =========================================
    router ospf 1
     router-id 10.0.0.9
  
    !
    interface Loopback0
    !
     ip ospf 1 area 0.0.0.0
    !
    interface GigabitEthernet2
    ! s3 -> s2
     ip ospf 1 area 0.0.0.0
     ip ospf network point-to-point
    !
    interface GigabitEthernet3
    ! s3 -> s1
     ip ospf 1 area 0.0.0.0
     ip ospf network point-to-point
    !
ok: [s2] => 
  msg: |-
    ospf configuration for s2
    =========================================
    router ospf 1
     router-id 10.0.0.8
  
    !
    interface Loopback0
    !
     ip ospf 1 area 0.0.0.0
    !
    interface GigabitEthernet2
    ! s2 -> s1
     ip ospf 1 area 0.0.0.0
     ip ospf network point-to-point
    !
    interface GigabitEthernet3
    ! s2 -> s3
     ip ospf 1 area 0.0.0.0
     ip ospf network point-to-point
    !

TASK [Find configuration deployment deploy_script for ospf] ********************
ok: [s1]
ok: [s3]
ok: [s2]

TASK [Deploy ospf configuration] ***********************************************
included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/ios.yml for s1, s2, s3

TASK [ios_config: deploying ospf from /home/pipi/net101/tools/netsim/ansible/templates/ospf/ios.j2] ***
changed: [s1]
changed: [s3]
changed: [s2]

TASK [Figure out whether to deploy the module vxlan on current device] *********
ok: [s1]
ok: [s2]
ok: [s3]

TASK [Find configuration template for vxlan] ***********************************
ok: [s1]
ok: [s2]
ok: [s3]

TASK [Print deployed configuration when running in verbose mode] ***************
ok: [s1] => 
  msg: |-
    vxlan configuration for s1
    =========================================
    interface nve1
     no shutdown
     source-interface Loopback0
     member vni 101000
      ingress-replication 10.0.0.8
      ingress-replication 10.0.0.9
     member vni 101001
      ingress-replication 10.0.0.8
      ingress-replication 10.0.0.9
    !
    bridge-domain 1000
     member vni 101000
    !
    bridge-domain 1001
     member vni 101001
ok: [s3] => 
  msg: |-
    vxlan configuration for s3
    =========================================
    interface nve1
     no shutdown
     source-interface Loopback0
     member vni 101000
      ingress-replication 10.0.0.7
      ingress-replication 10.0.0.8
     member vni 101001
      ingress-replication 10.0.0.7
      ingress-replication 10.0.0.8
    !
    bridge-domain 1000
     member vni 101000
    !
    bridge-domain 1001
     member vni 101001
ok: [s2] => 
  msg: |-
    vxlan configuration for s2
    =========================================
    interface nve1
     no shutdown
     source-interface Loopback0
     member vni 101000
      ingress-replication 10.0.0.7
      ingress-replication 10.0.0.9
     member vni 101001
      ingress-replication 10.0.0.7
      ingress-replication 10.0.0.9
    !
    bridge-domain 1000
     member vni 101000
    !
    bridge-domain 1001
     member vni 101001

TASK [Find configuration deployment deploy_script for vxlan] *******************
ok: [s3]
ok: [s2]
ok: [s1]

TASK [Deploy vxlan configuration] **********************************************
included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/ios.yml for s1, s2, s3

TASK [ios_config: deploying vxlan from /home/pipi/net101/tools/netsim/ansible/templates/vxlan/csr.j2] ***
changed: [s1]
changed: [s3]
changed: [s2]

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   
h5                         : ok=12   changed=3    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0   
h6                         : ok=12   changed=3    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0   
s1                         : ok=31   changed=4    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0   
s2                         : ok=31   changed=4    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0   
s3                         : ok=31   changed=4    unreachable=0    failed=0    skipped=1    rescued=0    ignored=0   



This is the multi-node version of the vxlan-bridging lab.
Use it to check that you don't have spanning tree problems
in VXLAN overlay

* h1, h2 and h3 should be able to ping each other
* h4, h5 and h6 should be able to ping each other

Please note it might take a while for the lab to work due to
OSPF adjacency establishment and STP learning phase