VLAN forwarding/learning broken in 1.5.5 (and a workaround)
Posted: Wed Jun 17, 2020 7:32 pm
Chris and team - please read carefully, no skimming please -- this is a big deal!
Here are the steps I took.Makes it easy to reproduce the problem (only on out-of-the-box new switches preinstalled with 1.5.5) and how I "fixed" it.
1. Upgraded 40+ routers to 1.5.5, using Netonix-manager -- uneventful, success.
2. Received a batch of new switches - model WS-12-250-DCPreloaded with 1.5.5 (Board Rev F, PS-Firmware 70, PS-rev B) - identical to the 40+ which we had before.
3. Connected a router (Mikrotik) to a port, configured the port as Trunk, management untagged, moved the 192.168.1.X IP on the router to VLAN1 on that port, success -- access to the router restored - config saved (no roll-ack).
4. Added a VLAN. Untagged a port on that VLAN -- kept the trunk tagged.
No forwarding between the Mikrotik router and the device on the untagged port!
5. Uploaded firmware (downgrade) 1.5.3 -- no configuration changes ---
everything is working fine!Switching between the router and the device on the untagged port, using IPs assigned to the VLAN in the router is working fine.
6. Upgraded firmware back to 1.5.5 -- no configuration changes --- everything is STILL working fine!
7. Reset to factory defaults, then repeated steps 3 & 4 (step 4 failed before), now everything is STILL working fine.
8. Tried the same with another BRAND-NEW switch -- from the new batch -- same thing!No VLAN forwarding on 1.5.5 !!!
Same problem!!Downgrade to 1.5.3 fixes the problem.
Upgrade back to 1.5.5 -- problem stays fixed!
Hypothesis -- something is missing in 1.5.5 that enables VLAN forwarding.
This something exists in 1.5.3, and it persists after upgrades and configuration changes.
The persistent fix remains fixed after:warm-startcold-startreset-to-factory-defaults
(In other words, once a switch is downgraded to 1.5.3 it gets fixed -- I cannot find a way to break it in that way again --- persistent bit in the switch-chip?).
WIthout first downgrading to 1.5.3 nothing else solved the problem -- there was simply no packet forwarding (on the VLAN).
I tried warm and cold reset (didn't try reset to defaults).
==============================Additional bugs =====================
(tested in 1.5.5 -- might exist in older versions as well).
* Rollback does not work for VLAN changes when UI loss and rever-timer elapses.
* Reordering of VLANs (drag) makes the watchdog IPs disappear...There's never a watchdog-IP on the top VLAN, regardless of it's number.
Feature? Bug?
* In discovery tab, hitting the reload (two round arrows on top right), results in page reload -- and it exists the discovery tab to the default "status" tab.
I have never seen this before today -- this is on Firefox (which I rarely use -- could that be it?).
Thanks,
Yahel.
Here are the steps I took.Makes it easy to reproduce the problem (only on out-of-the-box new switches preinstalled with 1.5.5) and how I "fixed" it.
1. Upgraded 40+ routers to 1.5.5, using Netonix-manager -- uneventful, success.
2. Received a batch of new switches - model WS-12-250-DCPreloaded with 1.5.5 (Board Rev F, PS-Firmware 70, PS-rev B) - identical to the 40+ which we had before.
3. Connected a router (Mikrotik) to a port, configured the port as Trunk, management untagged, moved the 192.168.1.X IP on the router to VLAN1 on that port, success -- access to the router restored - config saved (no roll-ack).
4. Added a VLAN. Untagged a port on that VLAN -- kept the trunk tagged.
No forwarding between the Mikrotik router and the device on the untagged port!
5. Uploaded firmware (downgrade) 1.5.3 -- no configuration changes ---
everything is working fine!Switching between the router and the device on the untagged port, using IPs assigned to the VLAN in the router is working fine.
6. Upgraded firmware back to 1.5.5 -- no configuration changes --- everything is STILL working fine!
7. Reset to factory defaults, then repeated steps 3 & 4 (step 4 failed before), now everything is STILL working fine.
8. Tried the same with another BRAND-NEW switch -- from the new batch -- same thing!No VLAN forwarding on 1.5.5 !!!
Same problem!!Downgrade to 1.5.3 fixes the problem.
Upgrade back to 1.5.5 -- problem stays fixed!
Hypothesis -- something is missing in 1.5.5 that enables VLAN forwarding.
This something exists in 1.5.3, and it persists after upgrades and configuration changes.
The persistent fix remains fixed after:warm-startcold-startreset-to-factory-defaults
(In other words, once a switch is downgraded to 1.5.3 it gets fixed -- I cannot find a way to break it in that way again --- persistent bit in the switch-chip?).
WIthout first downgrading to 1.5.3 nothing else solved the problem -- there was simply no packet forwarding (on the VLAN).
I tried warm and cold reset (didn't try reset to defaults).
==============================Additional bugs =====================
(tested in 1.5.5 -- might exist in older versions as well).
* Rollback does not work for VLAN changes when UI loss and rever-timer elapses.
* Reordering of VLANs (drag) makes the watchdog IPs disappear...There's never a watchdog-IP on the top VLAN, regardless of it's number.
Feature? Bug?
* In discovery tab, hitting the reload (two round arrows on top right), results in page reload -- and it exists the discovery tab to the default "status" tab.
I have never seen this before today -- this is on Firefox (which I rarely use -- could that be it?).
Thanks,
Yahel.