CSS610-8P-2S+IN Blocked Traffic?

Hardware MikroTik hardware general
1

I have a CSS610-8P-2S+IN as the first connection off my router.

This morning I noticed EVERYTHING went offline for 5 minutes.

Tracking backwards using Domotz I found that everything BEYOND the CSS610-8P-2S+IN went offline for about 5 minutes. The switch was still responding to pings from the router and the Domotz that is connected to the router.

By the time I got to a computer it was passing traffic like normal and made it hard to track down where the break was.

There is no log in this thing.

Is this an issue others have run into?
I am running SwitchOS Lite 2.18 on the switch.

Any insight?

Log from my router that was pinging several hosts.

 07:28:19 netwatch,info event down [ Waffel ]
 07:28:19 netwatch,info event down [ Kitchen ]
 07:28:19 netwatch,info event down [ Waffel ]
 07:28:19 netwatch,info event down [ Waffel ]
 07:28:19 script,info !!!Waffels WAP 60G is NOT there!!!
 07:28:19 netwatch,info event down [ type: icmp, host: 192.168.101.5 ]
 07:28:19 netwatch,info event down [ type: icmp, host: 192.168.101.3 ]
 07:28:19 script,info !!!DJ PtMP WAP 60G is NOT there!!!
 07:28:19 netwatch,info event down [ type: icmp, host: 192.168.101.6 ]
 07:28:19 script,info !!!HQ2DJ WAP 60G is NOT there!!!
 07:28:19 netwatch,info event down [ Kitchen ]
 07:28:19 script,info !!!DJ2HQ WAP 60G is NOT there!!!
 07:28:19 netwatch,info event down [ type: icmp, host: 192.168.101.4 ]
 07:28:19 script,info !!!Waffel Switch can't be pinged!!!
 07:28:19 script,info !!!DJ Booth Switch can't be pinged!!!
 07:28:19 script,info !!!HQSwitch can't be pinged!!!
 07:28:19 script,info !!!Kitchen WAP 60G is NOT there!!!
 07:28:19 script,info !!!Kitchen Switch can't be pinged!!!
 07:33:48 netwatch,info event up [ type: icmp, host: 192.168.101.3 ]
 07:33:48 netwatch,info event up [ Waffel ]
 07:33:48 script,info DJ Booth Switch can be pinged
 07:33:48 netwatch,info event up [ Kitchen ]
 07:33:48 script,info DJ2HQ WAP 60G is there.
 07:33:48 script,info DJ PtMP WAP 60G is there.
 07:33:48 netwatch,info event up [ Kitchen ]
 07:33:48 netwatch,info event up [ type: icmp, host: 192.168.101.5 ]
 07:33:48 script,info Kitchen WAP 60G is there.
 07:33:48 netwatch,info event up [ Waffel ]
 07:33:48 script,info Waffel Switch can be pinged
 07:33:48 netwatch,info event up [ type: icmp, host: 192.168.101.4 ]
 07:33:48 script,info Waffels WAP 60G is there.
 07:33:48 netwatch,info event up [ type: icmp, host: 192.168.101.6 ]
 07:33:48 script,info Kitchen Switch can be pinged
 07:33:48 netwatch,info event up [ Waffel ]
 07:33:48 script,info HQSwitch can be pinged
 07:33:48 script,info HQ2DJ WAP 60G is there.
2

Nobody?

Not even support?

3

I have no witnessed anything similar with the CSS610-8P that I have running. No unexplainable outages or interruptions and it is basically serving as the core switch for one of my networks.

4

I noticed my home network did this once. I was running the CSS as the core then.

And

At this install… The CSS is at the barn feeding the fiber link and wireless back hauls.

5

Just did it again.

5 minutes. Then it’s fine.

6

Maybe take a backup and reinstall the SWoS version? Or perhaps there’s a bad config somewhere? I’ve still had no issues and the switch has been up for 136 days.

7

This switch has been on for 7 months+

8

At the very least I’d save the config, reset the switch, update the SWoS version and then restore the config. You’ve got nothing to lose at this point. I’d probably even recreate the config. Other than that, have your filed a support ticket with MT support?

9

Yes I put in a support request.

All it has is the names on the ports… And the VLAN assignments.

The firmware is up to date.

I was the one who first reported the token issue on the hosts page.

10

Support verified the issue.

There is a firmware patch in the works.

The RC they sent me extended the amount of time between these lock ups. But they are still there.

Locked up on me yesterday and I reached out to support… heard nothing yet.

11

Just had another report of the 2.19rc6 firmware locking up for 5 minutes again.

Any chance this ever gets fixed?

12

Man when Mikrotik decides to ignore a faulty firmware… They really take it to the limit.

13

Unit is now running SwitchOS Lite 2.20.

The lock up was about 10 seconds.

Much improved… not gone…

I am running caps-man so that was long enough to force the caps to drop all clients.

14

After digging more… the switch actually rebooted.

15

Have you checked CPU / SFP tempts? It’s summer, unconditioned indoors… maybe some protection kicked in?

16

Not the case on this one.

The barn is still running one of the Betas support sent.

This reboot was observed at my home. Where the CSS is sitting in the air conditioned basement.

17

ulds,

Just shared with support ticket. THIS IS AT MY HOUSE IN A TEMPERATURE CONTROLLED ROOM.

This problem still exists on the 2.20 firmware. Switch was up for 59 days when I noticed this.

The switch does not reboot. It has all its light lit. It just doesn’t allow anything to pass through it for about 5 minutes.

Log entry from the RB5009 that works as the router in front of the CSS610-8P

2025-09-27 10:20:06 netwatch,info event down [ type: icmp, host: 172.16.14.2 ]
2025-09-27 10:20:06 script,info !!! WARNING CORE SWITCH !!!
2025-09-27 10:20:16 netwatch,info event up [ type: icmp, host: 172.16.14.2 ]
2025-09-27 10:20:16 script,info Core Switch is Good.
2025-09-27 10:20:16 dhcp,info Main_DHCP deassigned 172.16.14.2 for 48:A9:8A:97:7A:3E CSS610-8P
2025-09-27 10:20:16 dhcp,info Main_DHCP assigned 172.16.14.2 for 48:A9:8A:97:7A:3E CSS610-8P
2025-09-27 10:20:22 dhcp,info Main_DHCP deassigned 172.16.14.2 for 48:A9:8A:97:7A:3E CSS610-8P
2025-09-27 10:20:22 dhcp,info Main_DHCP assigned 172.16.14.2 for 48:A9:8A:97:7A:3E CSS610-8P
2025-09-27 10:20:30 caps,info disconnected MikroTik@04:F4:1C:54:D1:A8%*a, connection interrupted
2025-09-27 10:20:31 caps,info disconnected MikroTik@F4:1E:57:35:D5:EA%*a, connection interrupted
2025-09-27 10:21:47 netwatch,info event down [ type: icmp, host: 172.16.14.2 ]

2025-09-27 10:21:47 script,info !!! WARNING CORE SWITCH !!!
2025-09-27 10:23:34 dhcp,info Main_DHCP deassigned 172.16.14.2 for 48:A9:8A:97:7A:3E CSS610-8P
2025-09-27 10:23:34 dhcp,info Main_DHCP assigned 172.16.14.2 for 48:A9:8A:97:7A:3E CSS610-8P
2025-09-27 10:23:39 dhcp,info Main_DHCP deassigned 172.16.14.2 for 48:A9:8A:97:7A:3E CSS610-8P
2025-09-27 10:23:39 dhcp,info Main_DHCP assigned 172.16.14.2 for 48:A9:8A:97:7A:3E CSS610-8P
2025-09-27 10:25:34 dhcp,info Main_DHCP deassigned 172.16.14.2 for 48:A9:8A:97:7A:3E CSS610-8P
2025-09-27 10:25:34 dhcp,info Main_DHCP assigned 172.16.14.2 for 48:A9:8A:97:7A:3E CSS610-8P
2025-09-27 10:25:36 caps,info MikroTik@172.16.14.83 joined
2025-09-27 10:25:36 netwatch,info event up [ type: icmp, host: 172.16.14.2 ]
2025-09-27 10:25:36 script,info Core Switch is Good.

18

Bump… Anyone?

19

Just observed the problem at the Barn. No reboots. Just nothing passes for 5 minutes.