CRS226-24G-2S-RM ether drops intermittent

RouterOS General
1

Ive got a CCR1016-12G feeding a CRS226 and CRS125.

The 226 is always every few hours (may go up to 20 hours) sooner or later drops. The CCR shows a link down against ether 4 (running to ether 1 on CRS226). What’s interesting the CRS shows a cycle on the logs of all the used ether ports.
The CRS 125 never its on ether 5 on CCR.

So I set up a bonded balance-tlb layer 2/3 on the CRS226. I used ether1 and 9 since 9 belongs to the next internal switch.

I then have ether4 and 5 on the CCR feeding this, the CRS125 is now on ether 6

So its still happening, but Im seeing ether4 and 5 drop almost the same time.

Ive had the CCR and CRS226 replaced still doing this cycling of the ethers used on the CRS226

I’m now trying 6.30rc22 as support say this has a kernel crash fix that has been around the last few versions..

CCR226 2S+ v6.27 all ports flap
CCR1009: ether1 through ether4 sporadically drop then instantly come back up - switch chip problem?
2

We have had the same problems with the CRS226: http://forum.mikrotik.com/t/ccr226-2s-v6-27-all-ports-flap/88303/6

We even tried a different CRS226, but after 5 days and 16 hours, the same problems: all ports go down for a second, then come back up. Another 20 minutes later, they all go down for a few seconds, then back up, then back down for a second, then back up.

We have been advised by MikroTik to try 6.30rc22 as well. I will post here in about 6 days when we know more!

3

Glad I’m not alone it was driving me crazy, especially I dumped a old 16 port POS 4k buffer non managed.

Anyway it’s been up hours both the CRS and CCR and I’ve not seen any random kernel failures on the CCR and the CRS it’s so far not cycled the ethers!

I’ll keep you posted it will NEVER go 24h stay tuned!

4

[quote=“105547111”]I’ll keep you posted it will NEVER go 24h stay tuned!
[/quote]

Thanks - and good luck! :slight_smile:

5

Uptime over 8h and no drops on the CCR and no ether cycle on the CRS226 :slight_smile:

This IS looking good :wink:

6

Not fixed :frowning:

Right at 9hrs 50 up time all the ethers reset on the CRS226 ;(

But Ive tried few restarts the CCR random kernel reboot issue looks good.

7

Did you send support request on Mikrotik?

8

Yes :slight_smile:

Ticket [Ticket#2015062366000063] RE: CRS226-24G-2S-RM

It included the supout that shows a clean reboot then 9 hours later all the ethers in use cycled :slight_smile:

9

[quote=“105547111”]It included the supout that shows a clean reboot then 9 hours later all the ethers in use cycled :slight_smile:
[/quote]

Oh dear. I guess I will be saying the same thing in a few days’ time, then. I hope our supout files help, at least!

Our ticket is #2015052766000629 (opened almost a month ago now).

10

Whats interesting the logs in the CRS show the ethers all cycle that are in use, down first then immediately up.

But in interfaces the link downs remain at 0???

But on reverse end (eth4 and 5 on the CCR) I see ether 4 and 5 immediately cycled in sequence very fast down and up.

This is clearly a interesting CRS226 bug the CRS126 is perfect…

11

Any response that in 6.30 would be fixed?

12

All I know is what Janis from MT Support sent in my exchange on the ticket:

Please upgrade to RouterOS release candidate version 6.30rc22.
If the changes in the latest version do not solve this problem completely, supout
files from that version will allow us to continue debugging.

13

I’ve provided Janis with supout and remote access to our CRS226.

I can confirm on RC22 I saw the ethers all cycle still for us about the 8 to 12 hour range normally but definitely within 24 hours like clockwork. It’s had two sets of resets since running.

I had RC24 running but I’ve updated to RC26 now and it only had 6 hours uptime so I’m far away from saying it’s fixed…,

Hopefully RC26 stay around - I’ll update this thread should I see the CRS226 have a cycle again. What’s interesting it’s not just Ethernet. I set up a SFP link between the CRS226 and CRS125 yes it’s doing that as well.

It’s looking like a low level reset on all the switch chips, but not a full kernel failure. What’s interesting always the CRS226 claims no ether drops on some ports, but the CRS125 and the CCR1016 on the other ends show link downs…

I also know it’s happening as all IPv6 traffic through the switch dies for about 3 minutes as it has to wait for RADVD advertisement from the CCR, plus I’m monitoring winbox over IPv6.

Tick tick RC26 running about a hour so far…

14

Just lost it all again 19:25

Sending to support

15

Random reboot after about 18-24 hours running v6.30rc22:

14:04:16 system,error,critical router was rebooted without proper shutdown

No flaps yet, but random reboots isn’t better.

16

[quote=“maznu”]No flaps yet, but random reboots isn’t better.
[/quote]

Well, we just had the flaps:

14:18:34 interface,info ether02-mmr link down
14:18:34 interface,info ether23-wap1 link down
14:18:34 interface,info ether01-mmr link down
14:18:34 interface,info ether06-mmr-metronet link down
14:18:34 interface,info ether21-mmr-exa link down

14:18:35 interface,info ether02-mmr link up (speed 1G, full duplex)
14:18:35 interface,info ether23-wap1 link up (speed 100M, full duplex)
14:18:35 interface,info ether01-mmr link up (speed 1G, full duplex)
14:18:35 interface,info ether21-mmr-exa link up (speed 100M, full duplex)

…repeating…

14:20:24 interface,info ether02-mmr link up (speed 1G, full duplex)
14:20:24 interface,info ether23-wap1 link up (speed 100M, full duplex)
14:20:24 interface,info ether01-mmr link up (speed 1G, full duplex)
14:20:24 interface,info ether21-mmr-exa link up (speed 100M, full duplex)

17

Tried 6.30rc28 for ten minutes. Ports were flapping so much (every couple of minutes) that the switch was unusable.

Trying 6.30rc29 now… hasn’t flapped in a whole 1 hour so far!

18

[quote=“maznu”]Trying 6.30rc29 now… hasn’t flapped in a whole 1 hour so far!
[/quote]

6.30rc29: kernel crash and switch reboot after under 10 hours. I can’t keep on testing firmware that is this unreliable, so am downgrading to v6.29.1 which at least will run for five days before all the ports flap.

6.30 released
19

You’ll love this… As I’ve still got a several days left to return the 226 for a full refund, I ordered a 125-RM. I’ve thrown it in place of the 226 and RC28 17 hours strong (never ever).

So I played devils advocate wanting to still help eradicate this bug, changed IPs on the 226, plugged eth1 and 3 into a spare MT951G on eth4 and 5 let it run. NO LOAD NOTHING. Simply ether 1 and 3 as inputs and I had a winbox open to monitor.

After the magic about 9H bang winbox gone. Shows eth4 and 5 dropped on the 951G

Even no use it goes in 9H.

Don’t forget this is my second 226 the SAME issue exactly.

Cheers!

20

Funnily enough, our 125 arrives tomorrow morning. We’ll swap out the 226 for the 125 (there are two other 125s on our network, been running fine for 60 days). And then make the 226 available for MikroTik support.

Interesting to hear your problems continue with no traffic. That suggests it is not CPU load, but maybe some other resource exhaustion.

Good luck, MikroTik!

Thank you, 105547111 :slight_smile: