We see some failures while running lag_2 test in T1-Lag Topology
T1-Lag topology:
Lag-2:
The physical ports used on S6100 in our tetsbed are non-contiguous
The script for Lag_2 [single_lag_test.yml] takes the interface number from topo_t1-lag.yml vlan info.
The topo_t1-lag.yml file has the vlan listed in contiguous order from 0 to31
Snip from single_lag_test.yml
We modified topo_t1-lag.yml vlan number to match the physical interface numbering on sonic dut.
After modifying this we do not see the failure in lag2 tests.
Can you help out in making us understand the reason to take the port numbers from vlan info?
We see some failures while running lag_2 test in T1-Lag Topology
T1-Lag topology:
Lag-2:
The physical ports used on S6100 in our tetsbed are non-contiguous
The script for Lag_2 [single_lag_test.yml] takes the interface number from topo_t1-lag.yml vlan info.
The topo_t1-lag.yml file has the vlan listed in contiguous order from 0 to31
Snip from single_lag_test.yml
set_fact:
iface_behind_lag_member_0: "{{ topology['VMs'][peer_device]['vlans'][0] }}"
set_fact:
iface_behind_lag_member_1: "{{ topology['VMs'][peer_device]['vlans'][1] }}"
We modified topo_t1-lag.yml vlan number to match the physical interface numbering on sonic dut.
After modifying this we do not see the failure in lag2 tests.
Can you help out in making us understand the reason to take the port numbers from vlan info?