The 1016 connected to a 2004 was the one complaining.On yours, which device is complaining about the FCS errors?
The packetloss? Then the 2004 wont be usable is the conclusion?It's ha hardware problem due to cache missing on the switch chip, it can not be solved
No I loose connectivity with L3HW for Loopback0 so waiting for Mikrotik to fix.Are you using hardware offload on the CCR2216?
You need this Normis - https://www.redbubble.com/i/t-shirt/BGP ... 1893.UGYPMJoke <<==
You ==>
:)
Just tested on 7.2 with same result so posted ticket SUP-79177.Please create a support ticket, and we will try to reproduce your issue.
You obviously dident get the problem which is that 2 interfaces only allows chaining.Buy two?
It's still a 10th of Cisco/Juniper 100G stuff.
1036, 1072 and 2004s. Its was not seamless - We had to rewrite some of the bgp filters and make some smaller adjustments.Which units did you upgrade using full BGP and was it seemless upgrade - (im still getting used to the new terminology before I upgrade)?
I have no PPP users and no reboots.Are you using this router as ppp server ?
I am 200+ ppp clients.
.
For test, I only one ppp client on this ccr, no reboot for 30 days, then i gave full load of 200+ users, and it's started to reboot again. 7 days to 15 days gap.
Thank you I hope to have more positive reports
No, still weekly reboots on ccr2004 with stable v7.1.1
Try looking under IPv6 settings - first option.Why is not in GUI in Windows (Winbox), or in WebFig?
Code: Select all/ipv6/settings/set disable-ipv6=no
We were instructed to use 500 and doing so on 7.x too.Code: Select all/queue type set ethernet-default pfifo-limit=300 /queue interface set [find where queue!=no-queue] queue=ethernet-default
viewtopic.php?p=895484#p895484
BFD is working for BGP in v6 not sure why you say its not working.
7.1 has been stable since yesterday for me on several boxes :)which version is actually stable, from all RouterOS versions?
Seems to still be the same in ROS7 too. Just did testing with a couple.I have exactly the same situation. Did you ever managed to make it work?
I see these too on multiple RC6 systems but not quite so often. Just a couple per day and not from all neighbours.I have received a lot of this warning message on my RB5009 over my neighbor which is using ROS v6.49. Is this a bug from the beta3 version?
Its still missing and needed for us to really test the correct things.Please update https://help.mikrotik.com/docs/display/ ... col+Status
Same here :) Hopefully soon!waiting for a beta with functional route filtering. I can then test it extensively.
No reboots yet on beta22.Hows the uptime look so far?
Most has been fixed in last RC but still some left. MT says they are improving it still but the fix itself is well tested.Anyone has good news? :-)
For me they have been stable - we have 7 running RC and it solved most of packetloss.Tested the latest RC Friday just past and the 2004 lasted all of 8 hours before rebooting...
Are you using 1Gs - optics or rj45?I tried 6.49beta11 and BGP was flapping like mad on it, certainly don't run that version in production.
For us the 1Gs report 10G. Same for you?…and now same here with the 6.49beta11 "SFP at 1G is not stable" bug.
This bug claims to be fixed in 6.47.8 and then some more in 6.48. Ive had reboots on 6.48 but not on 6.47.8 so running 6.47.9 now.What version of RouterOS are you running? I might swap to that.
We had 2 reboots on 6.47.8 14 days ago in same day for 2 routers. After that nothing. We don't run 6.48.Same here, 6..48 and a lot of reboots.
Yes this was for sure an operator bug :) For other users with the same issue - make sure the filter is applied to the bgp peer.Filtrs pareizs, tikai jāpievieno BGP peeram! ;)
Yeah and sent in some more too - one asking if 6.48 does in fact solve anything more but got a wierd response so I've asked for clarification.Sent another one in.
SUP-37419 (new)
SUP-35544 (yours)
SUP-30924 (my previous)
Please send ticket to Mikrotik too so they dont think its just me :)Mine was going strong until you said that, it died 2.5 hours ago lol, time to pull it I suppose. Has anyone had better success 6.46 long term versions?
What was the reason for rejecting?We tried to RMA our units as not fit for use and it was rejected so we now have 4 of them just sitting collecting dust.
BothDid you just upgrade the RouterOS or did you upgrade the firmware as well?