[WARNING]: Could not match supplied host pattern, ignoring: unprovisioned PLAY [Deploy initial device configuration] ************************************* TASK [Set variables that cannot be set with VARS] ****************************** ok: [dut_a] ok: [dut_b] ok: [x1] TASK [Find device readiness script] ******************************************** ok: [dut_a] ok: [dut_b] ok: [x1] TASK [Wait for device to become ready] ***************************************** skipping: [dut_a] skipping: [dut_b] skipping: [x1] TASK [Deploy initial configuration] ******************************************** included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-module.yml for dut_a, dut_b, x1 TASK [Figure out whether to deploy the module initial on current device] ******* ok: [dut_a] ok: [dut_b] ok: [x1] TASK [Find configuration template for initial] ********************************* ok: [dut_a] ok: [dut_b] ok: [x1] TASK [fail] ******************************************************************** skipping: [dut_a] skipping: [dut_b] skipping: [x1] TASK [Print deployed configuration when running in verbose mode] *************** ok: [dut_a] => msg: |- initial configuration for dut_a ========================================= hostname dut-a ! lldp ! ! vlan 76 name blue ! vlan 42 name red ! ! ! interface loopback 0 ip address 10.0.0.1/32 ! interface mgmt no lldp transmit no lldp receive ! interface 1/1/1 shutdown mtu 9198 description dut_a -> x1 no shutdown ! interface 1/1/2 shutdown mtu 9198 description dut_a -> dut_b no shutdown ! interface vlan76 description VLAN blue (76) -> [x1,dut_b] ! interface vlan42 description VLAN red (42) -> [x1,dut_b] ! ! ok: [dut_b] => msg: |- initial configuration for dut_b ========================================= hostname dut-b ! lldp ! ! vlan 76 name blue ! vlan 42 name red ! ! ! interface loopback 0 ip address 10.0.0.2/32 ! interface mgmt no lldp transmit no lldp receive ! interface 1/1/1 shutdown mtu 9198 description dut_b -> x1 no shutdown ! interface 1/1/2 shutdown mtu 9198 description dut_b -> dut_a no shutdown ! interface vlan76 description VLAN blue (76) -> [x1,dut_a] ! interface vlan42 description VLAN red (42) -> [x1,dut_a] ! ! ok: [x1] => msg: |- initial configuration for x1 ========================================= hostname x1 ! logging monitor debugging aaa authorization exec default local ! lldp run ip routing ! ! ip host duta 10.0.0.1 ip host dutb 10.0.0.2 ! interface Management1 no lldp transmit no lldp receive ! interface Loopback0 no shutdown ip address 10.0.0.3/32 ! interface Ethernet1 no shutdown no switchport description x1 -> dut_a ! mac-address 52dc.cafe.0301 ! interface Ethernet2 no shutdown no switchport description x1 -> dut_b ! mac-address 52dc.cafe.0302 ! interface Vlan76 no shutdown description VLAN blue (76) -> [dut_a,dut_b] ! interface Vlan42 no shutdown description VLAN red (42) -> [dut_a,dut_b] ! TASK [Find configuration deployment deploy_script for initial] ***************** ok: [dut_a] ok: [dut_b] ok: [x1] TASK [Deploy initial configuration] ******************************************** included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/arubacx.yml for dut_a, dut_b included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/eos.yml for x1 TASK [tempfile] **************************************************************** changed: [dut_b -> localhost] changed: [dut_a -> localhost] TASK [template] **************************************************************** changed: [dut_a -> localhost] changed: [dut_b -> localhost] TASK [aoscx_config: set session auto-confirm for initial] ********************** changed: [dut_a] changed: [dut_b] TASK [aoscx_config: deploying initial from /home/pipi/net101/tools/netsim/ansible/templates/initial/arubacx.j2] *** changed: [dut_b] changed: [dut_a] TASK [file] ******************************************************************** changed: [dut_a -> localhost] changed: [dut_b -> localhost] TASK [eos_config: deploying initial from /home/pipi/net101/tools/netsim/ansible/templates/initial/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: [x1] PLAY [Deploy module-specific configurations] *********************************** TASK [Set variables that cannot be set with VARS] ****************************** ok: [dut_a] ok: [dut_b] ok: [x1] TASK [Deploy individual configuration modules] ********************************* included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-module.yml for dut_a, dut_b, x1 => (item=vlan) included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-module.yml for dut_a, dut_b, x1 => (item=stp) TASK [Figure out whether to deploy the module vlan on current device] ********** ok: [dut_a] ok: [dut_b] ok: [x1] TASK [Find configuration template for vlan] ************************************ ok: [dut_a] ok: [dut_b] ok: [x1] TASK [fail] ******************************************************************** skipping: [dut_a] skipping: [dut_b] skipping: [x1] TASK [Print deployed configuration when running in verbose mode] *************** ok: [dut_a] => msg: |- vlan configuration for dut_a ========================================= ! ! interface 1/1/1 no routing vlan trunk allow 42,76 ! interface 1/1/2 no routing vlan trunk allow 42,76 ! interface vlan76 ! interface vlan42 ok: [dut_b] => msg: |- vlan configuration for dut_b ========================================= ! ! interface 1/1/1 no routing vlan trunk allow 42,76 ! interface 1/1/2 no routing vlan trunk allow 42,76 ! interface vlan76 ! interface vlan42 ok: [x1] => msg: |- vlan configuration for x1 ========================================= vlan 76 name blue ! vlan 42 name red ! ! interface Ethernet1 switchport switchport mode trunk switchport trunk allowed vlan 42,76 ! interface Ethernet2 switchport switchport mode trunk switchport trunk allowed vlan 42,76 ! interface Vlan76 ! interface Vlan42 TASK [Find configuration deployment deploy_script for vlan] ******************** ok: [dut_a] ok: [dut_b] ok: [x1] TASK [Deploy vlan configuration] *********************************************** included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/arubacx.yml for dut_a, dut_b included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/eos.yml for x1 TASK [tempfile] **************************************************************** changed: [dut_a -> localhost] changed: [dut_b -> localhost] TASK [template] **************************************************************** changed: [dut_a -> localhost] changed: [dut_b -> localhost] TASK [aoscx_config: set session auto-confirm for vlan] ************************* changed: [dut_a] changed: [dut_b] TASK [aoscx_config: deploying vlan from /home/pipi/net101/tools/netsim/ansible/templates/vlan/arubacx.j2] *** changed: [dut_b] changed: [dut_a] TASK [file] ******************************************************************** changed: [dut_a -> localhost] changed: [dut_b -> localhost] TASK [eos_config: deploying vlan from /home/pipi/net101/tools/netsim/ansible/templates/vlan/eos.j2] *** changed: [x1] TASK [Figure out whether to deploy the module stp on current device] *********** ok: [dut_a] ok: [dut_b] ok: [x1] TASK [Find configuration template for stp] ************************************* ok: [dut_a] ok: [dut_b] ok: [x1] TASK [fail] ******************************************************************** skipping: [dut_a] skipping: [dut_b] skipping: [x1] TASK [Print deployed configuration when running in verbose mode] *************** ok: [dut_b] => msg: |- stp configuration for dut_b ========================================= ! ! stp config module ! spanning-tree spanning-tree mode rpvst spanning-tree priority 3 ! spanning-tree vlan 76 spanning-tree vlan 76 priority 3 spanning-tree vlan 42 spanning-tree vlan 42 priority 3 ok: [dut_a] => msg: |- stp configuration for dut_a ========================================= ! ! stp config module ! spanning-tree spanning-tree mode rpvst ! spanning-tree vlan 76 spanning-tree vlan 76 priority 8 spanning-tree vlan 42 spanning-tree vlan 42 priority 1 ok: [x1] => msg: |- stp configuration for x1 ========================================= spanning-tree mode rapid-pvst spanning-tree priority 16384 spanning-tree vlan-id 76 priority 16384 spanning-tree vlan-id 42 priority 16384 TASK [Find configuration deployment deploy_script for stp] ********************* ok: [dut_a] ok: [dut_b] ok: [x1] TASK [Deploy stp configuration] ************************************************ included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/arubacx.yml for dut_a, dut_b included: /home/pipi/net101/tools/netsim/ansible/tasks/deploy-config/eos.yml for x1 TASK [tempfile] **************************************************************** changed: [dut_a -> localhost] changed: [dut_b -> localhost] TASK [template] **************************************************************** changed: [dut_a -> localhost] changed: [dut_b -> localhost] TASK [aoscx_config: set session auto-confirm for stp] ************************** changed: [dut_b] changed: [dut_a] TASK [aoscx_config: deploying stp from /home/pipi/net101/tools/netsim/ansible/templates/stp/arubacx.j2] *** changed: [dut_a] changed: [dut_b] TASK [file] ******************************************************************** changed: [dut_a -> localhost] changed: [dut_b -> localhost] TASK [eos_config: deploying stp from /home/pipi/net101/tools/netsim/ansible/templates/stp/eos.j2] *** changed: [x1] PLAY [Deploy custom deployment templates] ************************************** skipping: no hosts matched PLAY RECAP ********************************************************************* dut_a : ok=36 changed=15 unreachable=0 failed=0 skipped=4 rescued=0 ignored=0 dut_b : ok=36 changed=15 unreachable=0 failed=0 skipped=4 rescued=0 ignored=0 x1 : ok=24 changed=3 unreachable=0 failed=0 skipped=4 rescued=0 ignored=0 The devices under test form a layer-2 triangle of VLAN trunks. The devices are running PVRST and have different per-VLAN root priorities. If DUT_A and DUT_B run PVRST and has correct per-VLAN root priorities, DUT_A becomes the root bridge for red VLAN and DUT_B becomes the root bridge for the blue VLAN.