Current multidut snappi topology doesn't support add-topo/remove-topo/deploy-mg for T2 testbed. As it requires the testbed definition to have the LCs only.
For multidut, the testbed definition is the following:
For T2 testbed, it has RP included the testbed definition which is required for add-topo/remove-topo/deploy-mg.
- conf-name: vms-chassis-packet-dut
......
dut:
- lab-msft-lc0-1
- lab-msft-lc1-1
- lab-msft-lc2-1
- lab-msft-sup-1 <<< RP dut is needed for T2 add-topo/remove-topo/deploy-mg
The multidut test cases needs to support the T2 testbed definition, so that we can use the same testbed definition for both add-topo/remove-topo/deploy-mg and multidut snappi testing.
Current multidut snappi topology doesn't support add-topo/remove-topo/deploy-mg for T2 testbed. As it requires the testbed definition to have the LCs only.
For multidut, the testbed definition is the following:
For T2 testbed, it has RP included the testbed definition which is required for add-topo/remove-topo/deploy-mg.
The multidut test cases needs to support the T2 testbed definition, so that we can use the same testbed definition for both add-topo/remove-topo/deploy-mg and multidut snappi testing.