Creating Device configuration snippets [CREATED] dut: initial,vlan [CREATED] h1: initial,routing [CREATED] h2: initial,routing [CREATED] h3: initial,routing [CREATED] h4: initial,routing [CREATED] h5: initial,routing Checking Are lab devices ready to be configured? [INFO] Checking SSH server(s) on dut [SSH] SSH server on node dut (device iol) is ready after 27.3 seconds Config Deploying device configurations [INFO] Executing initial configuration for node h1 (namespace clab- ml-17-h1) [INFO] Executing initial configuration for node h2 (namespace clab- ml-17-h2) [INFO] Executing initial configuration for node h4 (namespace clab- ml-17-h4) [INFO] Executing initial configuration for node h3 (namespace clab- ml-17-h3) [INFO] Executing initial configuration for node h5 (namespace clab- ml-17-h5) [INFO] Executing routing configuration for node h4 (namespace clab- ml-17-h4) [INFO] Executing routing configuration for node h2 (namespace clab- ml-17-h2) [INFO] Executing routing configuration for node h1 (namespace clab- ml-17-h1) [INFO] Executing routing configuration for node h3 (namespace clab- ml-17-h3) [INFO] Executing routing configuration for node h5 (namespace clab- ml-17-h5) Results of configuration script deployments ================================================================================ dut Startup: initial,vlan h1 Script: initial,routing h2 Script: initial,routing h3 Script: initial,routing h4 Script: initial,routing h5 Script: initial,routing This scenario tests the basic "bridge" functionality. As a "bridge" is nothing more than a VLAN-capable node having all interfaces in VLAN 1, this test effectively: * Tests whether the device can take the role 'bridge' * Whether the interfaces are all configured in the same VLAN * Whether the device configuration template handles VLAN 1, or the device quirks take extra efforts to work around that