Hi,
I use a CRS317 as core switch for my 10g LAN. We had two power failures in the last 2 weeks, because of thunderstorms. When the power comes back, the CRS317 isn’t switching. I have to cut the power cables (1 and 2) and wait a minute. After that period, the switch works again. Is this a known problem, or should I connect the switch to a UPS?
Thanks.
What kind of SFP modules are you using there? Specifically models
I use the SFP-S-85DLC03D from Mikrotik. And I forgot to mention, I run SwOs.
Is the device accessible and operational from the management ethernet port, during the problem?
I haven’t tried that, because it was time critical. Only the blue power LEDs were active, the SFP+ LEDs were all inactive/dark.
If the issue repeats itself, try the management port. This would help us to repeat the issue quicker.
Thank you, I will do that the next time.
In my opinion, regardless of this problem, you should have protected power for your network core.
Sent from a $&@#% iPhone using Tapatalk
We found a software issue that prevented SFP ports linking up properly after a power cycle in some cases. The fix will be included in the next SwOS version.
Hi,
I have updated to SwOS 2.8 and now my CRS317 hangs up after a few minutes. Any known issues? Where can I download 2.7?
what steps you took? today we had same problem after upgrade to SwOS 2.8, STP was not working and it was taking so much time to boot up but downgrade to 2.6 resolved the problem.
I downloaded 2.7 and then everything was fine agin. I have bought a 2nd CRS317 and some CRS125 to test 2.8 in an isolated test environment. Updating on our live system was a bad idea.
I was having the same issue on my 317 with 2.7. Now I’m on 2.8 and while the link issue appears to be resolved, a much worse issue has appeared.
The switch intermittently stops passing traffic. This includes accessing the GUI. I might have to revert back to 2.7 myself and just bounce the ports like I used to to restore layer 1.
I backed down to 2.6 and now the switch is passing traffic like it’s supposed to.
I see SwOS 2.9 was released today. Who’s gonna be brave and give it a test run?
Where are you seeing that 2.9 was released? Not on the software download page and no announcements here on the forum.
Ah, one of my switches shows that:
Current Installed Version 2.8 (built at Fri Jul 13 2018 04:37:06 GMT-0700 (Pacific Daylight Time))
Latest Available Version 2.8 (built at Thu Sep 13 2018 19:40:15 GMT-0700 (Pacific Daylight Time))
And under Changelog:
What’s new in v2.9:
*) CRS326 & CRS328 & CRS317: make sure that RSTP BPDU packets are always untagged;
*) CRS328-4C-20S-4S+: make 1G fiber SFP modules work;
2.9 does nothing for me, so I likely won’t bother with this one…
There are a lot of issues with auto-upgrade in SwOS. For example right now I see 2.7 as newest despite 2.8 being released for quite a while now. Attempting to manually fetch 2.9 via crafted links fail so most likely it was not planned to be released today or they found critical bug in last moment and decided to pull it.
Thought of running RouterOS instead? Its far more powerful than SWOS and more mature in my opinion?
"And under Changelog:
What’s new in v2.9:
*) CRS326 & CRS328 & CRS317: make sure that RSTP BPDU packets are always untagged;
*) CRS328-4C-20S-4S+: make 1G fiber SFP modules work;"
I’m seeing the same thing on my switch currently running v2.8 . That post was from Sept of this year, I would very much like the “make 1G fiber SFP modules work;” part.
So what is the scoop on the mysterious v2.9 ?