Weird MAC/Vlan related issues with multiple uplinks
Posted: Tue May 08, 2018 9:41 pm
Hi All,
We have a WS-26-500-DC running 1.5.0rc4 and have many vlans passing through 2 separate uplinks.
The uplinks are connected to the same switch on the other side passing the same vlans (yes together you will cause a loop, we are aware) so what we do when we want to switch over from one link to the other we just enable the Ethernet port on the netonix of the first link and disable it on the second by checking/unchecking the appropriate checkboxes.
Upon switching manually no traffic passes through the link as if it appears that the MAC table is not updated at all. Waiting for 10 minutes makes no difference and only a reboot of the netonix fixes this issue. After rebooting the netonix correctly starts passing traffic as it should through the link that was brought up and had issues. The ethernet is correctly brought up and shows that its running so this is not a cable/interface issue.
This method of switching used to work fine on a Mikrotik CRS and a Cisco 2960G with the same type of simple configuration.
Can anyone help as to why the netonix has this issue? We are aware that this is not an efficient way to switch uplinks but we have it for special purposes and need it like this.
Thank you.
We have a WS-26-500-DC running 1.5.0rc4 and have many vlans passing through 2 separate uplinks.
The uplinks are connected to the same switch on the other side passing the same vlans (yes together you will cause a loop, we are aware) so what we do when we want to switch over from one link to the other we just enable the Ethernet port on the netonix of the first link and disable it on the second by checking/unchecking the appropriate checkboxes.
Upon switching manually no traffic passes through the link as if it appears that the MAC table is not updated at all. Waiting for 10 minutes makes no difference and only a reboot of the netonix fixes this issue. After rebooting the netonix correctly starts passing traffic as it should through the link that was brought up and had issues. The ethernet is correctly brought up and shows that its running so this is not a cable/interface issue.
This method of switching used to work fine on a Mikrotik CRS and a Cisco 2960G with the same type of simple configuration.
Can anyone help as to why the netonix has this issue? We are aware that this is not an efficient way to switch uplinks but we have it for special purposes and need it like this.
Thank you.