[WARNING]: Could not match supplied host pattern, ignoring: unprovisioned [WARNING]: Found variable using reserved name: hosts PLAY [Deploy initial device configuration] ************************************* TASK [Set variables that cannot be set with VARS] ****************************** ok: [x1] ok: [x2] ok: [dut] TASK [Find device readiness script] ******************************************** ok: [x1] ok: [dut] ok: [x2] TASK [Wait for device to become ready] ***************************************** skipping: [dut] skipping: [x1] skipping: [x2] TASK [Normalize config on bridge-like devices] ********************************* included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-module.yml for dut, x1, x2 TASK [Figure out whether to deploy the module normalize on current device] ***** ok: [dut] ok: [x1] ok: [x2] TASK [Find configuration template for normalize] ******************************* ok: [dut] ok: [x2] ok: [x1] TASK [fail] ******************************************************************** skipping: [dut] skipping: [x1] skipping: [x2] TASK [Find configuration deployment deploy_script for normalize] *************** ok: [dut] ok: [x1] ok: [x2] TASK [Print deployed configuration when running in verbose mode] *************** ok: [dut] => msg: |- normalize configuration for dut ========================================= ! interface Ethernet1 shutdown mac-address 52dc.cafe.0101 ! interface Ethernet2 shutdown mac-address 52dc.cafe.0102 ! interface Ethernet3 shutdown mac-address 52dc.cafe.0103 ! interface Ethernet4 shutdown mac-address 52dc.cafe.0104 ok: [x1] => msg: |- normalize configuration for x1 ========================================= ! interface Ethernet1 shutdown mac-address 52dc.cafe.0201 ! interface Ethernet2 shutdown mac-address 52dc.cafe.0202 ok: [x2] => msg: |- normalize configuration for x2 ========================================= ! interface Ethernet1 shutdown mac-address 52dc.cafe.0301 ! interface Ethernet2 shutdown mac-address 52dc.cafe.0302 TASK [Deploy normalize configuration] ****************************************** included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/eos.yml for dut, x1, x2 TASK [eos_config: deploying normalize from /home/pipi/net101/tools/netsim/ansible/templates/normalize/eos.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: [x2] changed: [x1] changed: [dut] TASK [Deploy initial configuration] ******************************************** included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-module.yml for dut, x1, x2 TASK [Figure out whether to deploy the module initial on current device] ******* ok: [x1] ok: [dut] ok: [x2] TASK [Find configuration template for initial] ********************************* ok: [x1] ok: [x2] ok: [dut] TASK [fail] ******************************************************************** skipping: [dut] skipping: [x1] skipping: [x2] TASK [Find configuration deployment deploy_script for initial] ***************** ok: [dut] ok: [x1] ok: [x2] TASK [Print deployed configuration when running in verbose mode] *************** ok: [dut] => msg: |- initial configuration for dut ========================================= hostname dut ! logging monitor debugging aaa authorization exec default local ! lldp run ip routing ! ! ip host x1 172.16.0.2 ip host x2 172.16.1.3 ! interface Management1 no lldp transmit no lldp receive ! interface Loopback0 ip address 10.0.0.1/32 ! interface port-channel1 no switchport mtu 1500 description dut -> x1 [stub] ip address 172.16.0.1/24 ! interface port-channel2 no switchport mtu 1400 description dut -> x2 [stub] ip address 172.16.1.1/24 ! interface Ethernet1 no switchport mtu 1500 description dut -> x1 [stub] ! mac-address 52dc.cafe.0101 no shutdown ! interface Ethernet2 no switchport mtu 1500 description dut -> x1 [stub] ! mac-address 52dc.cafe.0102 no shutdown ! interface Ethernet3 no switchport mtu 1400 description dut -> x2 [stub] ! mac-address 52dc.cafe.0103 no shutdown ! interface Ethernet4 no switchport mtu 1400 description dut -> x2 [stub] ! mac-address 52dc.cafe.0104 no shutdown ! ok: [x2] => msg: |- initial configuration for x2 ========================================= hostname x2 ! logging monitor debugging aaa authorization exec default local ! lldp run ip routing ! ! ip host dut 10.0.0.1 172.16.0.1 172.16.1.1 ip host x1 172.16.0.2 ! interface Management1 no lldp transmit no lldp receive ! interface port-channel1 no switchport mtu 1400 description x2 -> dut [stub] ip address 172.16.1.3/24 ! interface Ethernet1 no switchport mtu 1400 description x2 -> dut [stub] ! mac-address 52dc.cafe.0301 no shutdown ! interface Ethernet2 no switchport mtu 1400 description x2 -> dut [stub] ! mac-address 52dc.cafe.0302 no shutdown ! ok: [x1] => msg: |- initial configuration for x1 ========================================= hostname x1 ! logging monitor debugging aaa authorization exec default local ! lldp run ip routing ! ! ip host dut 10.0.0.1 172.16.0.1 172.16.1.1 ip host x2 172.16.1.3 ! interface Management1 no lldp transmit no lldp receive ! interface port-channel1 no switchport mtu 1500 description x1 -> dut [stub] ip address 172.16.0.2/24 ! interface Ethernet1 no switchport mtu 1500 description x1 -> dut [stub] ! mac-address 52dc.cafe.0201 no shutdown ! interface Ethernet2 no switchport mtu 1500 description x1 -> dut [stub] ! mac-address 52dc.cafe.0202 no shutdown ! TASK [Deploy initial configuration] ******************************************** included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/eos.yml for dut, x1, x2 TASK [eos_config: deploying initial from /home/pipi/net101/tools/netsim/ansible/templates/initial/eos.j2] *** changed: [x2] changed: [x1] changed: [dut] PLAY [Deploy module-specific configurations] *********************************** TASK [Set variables that cannot be set with VARS] ****************************** ok: [dut] ok: [x1] ok: [x2] TASK [Deploy individual configuration modules] ********************************* included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-module.yml for dut, x1, x2 => (item=lag) included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-module.yml for dut, x1, x2 => (item=routing) TASK [Figure out whether to deploy the module lag on current device] *********** ok: [dut] ok: [x1] ok: [x2] TASK [Find configuration template for lag] ************************************* ok: [dut] ok: [x1] ok: [x2] TASK [fail] ******************************************************************** skipping: [dut] skipping: [x1] skipping: [x2] TASK [Find configuration deployment deploy_script for lag] ********************* ok: [dut] ok: [x1] ok: [x2] TASK [Print deployed configuration when running in verbose mode] *************** ok: [x2] => msg: |- lag configuration for x2 ========================================= interface port-channel1 description x2 -> dut ! ! interface Ethernet1 description x2 -> dut in channel-group 1 channel-group 1 mode active lacp timer fast ! interface Ethernet2 description x2 -> dut in channel-group 1 channel-group 1 mode active lacp timer fast ok: [dut] => msg: |- lag configuration for dut ========================================= interface port-channel1 description dut -> x1 ! ! interface Ethernet1 description dut -> x1 in channel-group 1 channel-group 1 mode active lacp timer fast ! interface Ethernet2 description dut -> x1 in channel-group 1 channel-group 1 mode active lacp timer fast interface port-channel2 description dut -> x2 ! ! interface Ethernet3 description dut -> x2 in channel-group 2 channel-group 2 mode active lacp timer fast ! interface Ethernet4 description dut -> x2 in channel-group 2 channel-group 2 mode active lacp timer fast ok: [x1] => msg: |- lag configuration for x1 ========================================= interface port-channel1 description x1 -> dut ! ! interface Ethernet1 description x1 -> dut in channel-group 1 channel-group 1 mode active lacp timer fast ! interface Ethernet2 description x1 -> dut in channel-group 1 channel-group 1 mode active lacp timer fast TASK [Deploy lag configuration] ************************************************ included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/eos.yml for dut, x1, x2 TASK [eos_config: deploying lag from /home/pipi/net101/tools/netsim/ansible/templates/lag/eos.j2] *** changed: [x1] changed: [x2] changed: [dut] TASK [Figure out whether to deploy the module routing on current device] ******* ok: [dut] ok: [x1] ok: [x2] TASK [Find configuration template for routing] ********************************* skipping: [dut] ok: [x1] ok: [x2] TASK [fail] ******************************************************************** skipping: [dut] skipping: [x1] skipping: [x2] TASK [Find configuration deployment deploy_script for routing] ***************** skipping: [dut] ok: [x1] ok: [x2] TASK [Print deployed configuration when running in verbose mode] *************** skipping: [dut] ok: [x1] => msg: |- routing configuration for x1 ========================================= ! ! ! AS-path access lists ! ! ! Static routes ! ip route 0.0.0.0/0 port-channel1 172.16.0.1 ok: [x2] => msg: |- routing configuration for x2 ========================================= ! ! ! AS-path access lists ! ! ! Static routes ! ip route 0.0.0.0/0 port-channel1 172.16.1.1 TASK [Deploy routing configuration] ******************************************** skipping: [dut] included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/eos.yml for x1, x2 TASK [eos_config: deploying routing from /home/pipi/net101/tools/netsim/ansible/templates/routing/eos.j2] *** changed: [x2] changed: [x1] PLAY [Deploy custom deployment templates] ************************************** skipping: no hosts matched PLAY RECAP ********************************************************************* dut : ok=26 changed=3 unreachable=0 failed=0 skipped=9 rescued=0 ignored=0 x1 : ok=31 changed=4 unreachable=0 failed=0 skipped=5 rescued=0 ignored=0 x2 : ok=31 changed=4 unreachable=0 failed=0 skipped=5 rescued=0 ignored=0 The device under is a router with a L3 LAG link connected to a FRR device. The FRR device should be able to ping the loopback interface of DUT.