Sad to say, but this made no difference.Try 6.43.7 and make sure routerboot is also updated.
I agree with you assumtion that this is an edge case between the SFP units and the switch. But strangely it only occurs on one of our two CRS317 in the installation.I have the SAME EXACT problem. Mikrotik needs to fix this. No problem with 1Gbps SFP but with OWM SFP+ it's hell. I think this could be combination of software and hardware problem with SFP+ modules.
I am using the paired SFP+ from Mikrotik S+2332LC10D. So yes.From the MikroTik site it looks to me like the S+32LC10D is specifically meant to have the S+23LC10D module on the other end. Are you using the same module on both ends?
I can only speak for myself - and i am only using the SFP+ ports.Are any of you using port ether1 or just sfp-plus ports? If you are, remember that "The new Cloud Router Switch 317-1G-16S+RM is a rack-mountable manageable switch with Layer3 features, it has 16 SFP+ ports for high performance 10GbE connectivity and a 1GbE copper port for management. "
In production context ?Sometimes on CCRs ports go totally down, disabling and enabling them solves the problem.
since, not all ports flapping, just one or two, I assume that there is a hardware failure. But we have to wait, until MikroTik have something so say.Me too..
317 - Ccr 10Gb mk Dac ok
317 - 326 10Gb mk S+85DLC03D ok
317 - 328 10Gb mk Dac flapping
The strange thing is that for over one month all worked fine, after that, without any change, the flapping began.
Forcing the Dac to 1Gbps stop the flapping immediatly, now we are monitoring it, but we need 10Gb connections.
This is good news and indicative of software issues. Raising the probability of a fix. I have however met nothing but radio silence from MT lately, have any of you guys gotten any info from them?hello folks,
update:
After we switched on the CRS317-1G-16S+ to SwitchOS 2.9
5 days without port flapping.
regards
Hi roggles, still stable with SwitchOs?After we switched on the CRS317-1G-16S+ to SwitchOS 2.9
5 days without port flapping.
Could you please send us email, about your setup and problem, to support@mikrotik.com?Have the same problem with UF-SM-10G & CRS317-1G-16S+ with 6.42.12.
Any RoOS version with fix?
Hi! How Is the fix coming along?Could you please send us email, about your setup and problem, to support@mikrotik.com?Have the same problem with UF-SM-10G & CRS317-1G-16S+ with 6.42.12.
Any RoOS version with fix?
Ticket#2019040322003846Could you please send us email, about your setup and problem, to support@mikrotik.com?
Where do i get additional information about tickets? I see no links in the emails i have gotten.Ticket#2019040322003846Could you please send us email, about your setup and problem, to support@mikrotik.com?
You are absolutely right about SwOS, but what can do with many introduced MiktoTik devices with only SwOS ?Hello,
SwitchOS is one big pile of shit with no real featues, as it was intended for the general audience.
When i add SFP media converters or non-mikrotik or unmanaged switches on the other end it does not pick the link up.
But ROS does, hence we cannot use SWOS at all (As a last resort even if it a very crap OS .).
We can confirm the same, but not on all interfaces, those that were stable on RoOS have only 2 Errors.The problem is partially solved by the change of the CRS317 system to SwOS. But still Rx FCS Errors occur on the 10G interfaces.
That seems unlikely as I have the same link flapping on my DAC links btween the CRS328 and CRS317 on 10G links. Something seems to be wrong (software or hardware??), but Mikrotik does not seem to be interested...Can anybody try to add attenuators on problematic links? Would it change anything?
YesDoes the DAC link have Rx FCS Errors also?
Hi gentrice, we are angry too, but the problem we are talking here is on crs317.. what kind of problem do you have on crs328?Very bad service, client try to use Ubq to replace all CRS328.
We received an answer that MikroTik is aware of this issue and is working on a solution.There has not been any reaction since*.
we hope it...We are working on this problem, it could take up to a couple of weeks, to find a proper solution and test it.
We were able to reproduce this issue on CRS328-24P-4S+ connected via SFP+ DAC to a CRS317-1G-16S+. We tested the following scenarios:Hi gentrice, we are angry too, but the problem we are talking here is on crs317.. what kind of problem do you have on crs328?
this issue also happens with mikrotik SFP+ and fibersdo not use DAC.
According to all posters here, the problem presents itself only in connection with CRS317 and 10G SFP+. So it will not happen to your setup.Hello. I need to buy two 24 port switches and I have to choose between CRS326 and second hand Cisco 2960G, the price is the same. If I take CRS326 it will be used with RouterOS for access switch. From what I read in forum, SwOS is not ready for "in production" setups and this is the reason to choose CRS326 instead of CSS326.
My question is - if I use only 100Mbps and 1000Mbps (random mix of ports, PCs, VoIP phones etc.) connections and not 10G connections, the problem with port flapping will be present or not?
I think the same GuJack20. Do you have CRS326 in production? If you have, what is your opinion for the switch? Somebody else do you have CRS326 in production running RouterOS?According to all posters here, the problem presents itself only in connection with CRS317 and 10G SFP+. So it will not happen to your setup.
Hi,I think the same GuJack20. Do you have CRS326 in production? If you have, what is your opinion for the switch? Somebody else do you have CRS326 in production running RouterOS?
I'm sorry if this is mistake. I posted here because CRS328 is the same as CRS326 but with PoE. If moderators want they can delete my posts.Hi,
please open or write in a thread/section where your question is addressed. This thread is about a severe port flapping issue on CRS328 and CRS317 as the title reflects.
Thanks,
nh
EDIT: corrected a typo of product names.
Is there something hardware specific related to that - in a way that some devices might not be affected at all? I have one 317 with problem while other has been without problems...Our investigation has revealed that there might be a SFP+ compatibility issue with specific CRS317-1G-16S+ units when connected to other CRS3xx devices resulting in random link downs. Please, contact MikroTik support if you experience similar issue, we will verify it and arrange a repair if necessary.
The worst problems with port flapping (more that 70 per day) after the upgrade to 6.45.1 have been resolved after another reboot of the CRS317, but I still see port flaps (1 per day??). I guess that the issues I noticed where my UNMS monitoring the network often reports nodes not responding and returning after 1 -3 minutes and frequent drops of the internet radio streams are related too (no proof of that though).Our investigation has revealed that there might be a SFP+ compatibility issue with specific CRS317-1G-16S+ units when connected to other CRS3xx devices resulting in random link downs. Please, contact MikroTik support if you experience similar issue, we will verify it and arrange a repair if necessary.
So it could really be a hardware problemYesterday connected the new one CRS317-1G-16S+
On it, not one flap happened.
time is not right for me either. strange bug...And also noticed a strange thing.
Interface status, last link up / down shows a strange time.
@BECS: is there a way to identify if a CRS is affected? Does the serial numer tell if the device is affected?Our investigation has revealed that there might be a SFP+ compatibility issue with specific CRS317-1G-16S+ units when connected to other CRS3xx devices resulting in random link downs. Please, contact MikroTik support if you experience similar issue, we will verify it and arrange a repair if necessary.
If this is the case - it is simply not good enough. I have 30 of these devices in an installation, and -all- of them are experiencing this issue. It has almost been a year since i reported this to mikrotik support, and all i have got - despite several attempts at getting updated answers - is "we have recreated the issue".as MK support said: "if possible, please, consider using CRS309-1G-8S+ as replacement in similar applications to decrease probability of encountering this issue."
I can live with GE a while longer, and i'm sure there will be a replacement program at some point. I just wish MT would communicate a little more. What switches did you go for? Changing the poe switches would be a nightmare for us, but changing the crs328 would be less painful. You say you chose cisco, did you consider other options? If so, what were they?To all posters here,
i'm afraid that this is a combination of HW and SW problem when there's a SFP+ connection between CRS 317 and CRS 328 and simply put, don't expect that anything's gonna change anytime soon.
We've replaced CRS 328 with much more expensive Cisco devices and it works like a charm.
So my advice would be:
If you can replace one of the devices, DO IT!
If your network won't fully utilize 10G just go 1G and figure replacement later.
If you can't or don't want to replace a lot devices for an non-Mikrotik equivalent sell CRS 317 and buy CRS 309 instead.
We have our Mikrotik CRS 317 connected to couple of Cisco SF350-48P (48 port POE switch) via 10G SFP+. And another couple of NETGEAR GS752TXP connected via SPF+ too. In both cases no port flapping.I can live with GE a while longer, and i'm sure there will be a replacement program at some point. I just wish MT would communicate a little more. What switches did you go for? Changing the poe switches would be a nightmare for us, but changing the crs328 would be less painful. You say you chose cisco, did you consider other options? If so, what were they?To all posters here,
i'm afraid that this is a combination of HW and SW problem when there's a SFP+ connection between CRS 317 and CRS 328 and simply put, don't expect that anything's gonna change anytime soon.
We've replaced CRS 328 with much more expensive Cisco devices and it works like a charm.
So my advice would be:
If you can replace one of the devices, DO IT!
If your network won't fully utilize 10G just go 1G and figure replacement later.
If you can't or don't want to replace a lot devices for an non-Mikrotik equivalent sell CRS 317 and buy CRS 309 instead.
Well I reported my issues to support and now will have to return the CRS317 for RMA. I can only hope that that will solve my issues. It remains a mystery that this apparently happens only between the CRS317 and CRS328. It still sounds as if the issue is partly caused by the CRS328 as well, otherwise it should occur between the CRS317 and other switches and/or 10G network cards....I have to say that it seems that there are either
a) just a few CRS317 affected
or/and
b) most buyers not aware of this issue
or/and
c) the amount of CRS317 <- 10G SFP+ -> CRS328 combinations are low
It seems that MikroTik accepts the risk to repair/replace a few CRS317 and continues selling a device which does not provide 10G connections to CRS328. I would go with a) or b) when comparing the stock levels over time of online shops to the amount of posts and active people in this thread.
Telling customers not to buy a product in order to reduce the probability of failure is another way to tell them to look for alternatives as Elliot did.
My experience tells otherwise - links between 317 and 326 are flapping, but when link from one 317 is connected to other 326, then flapping travels along with "sick" 317.Its 100% the CRS328's not the CRS317's
I raised a case with support and they told me to RMA the CRS317. We will see what will happen when I get the CRS317 (or a replacement) back....My experience tells otherwise - links between 317 and 326 are flapping, but when link from one 317 is connected to other 326, then flapping travels along with "sick" 317.Its 100% the CRS328's not the CRS317's
I don't know about 328-24P-4S+, but 326 seems to have similar hardware (counting out PoE and amount of sfp+ ports) hence problems might be of similar nature.
I RMAd the device and the problem got acknowledged. The switch now has to be sent to Mikrotik for repair, which will take 6-8 weeks. That is a loooong time.I raised a case with support and they told me to RMA the CRS317. We will see what will happen when I get the CRS317 (or a replacement) back....My experience tells otherwise - links between 317 and 326 are flapping, but when link from one 317 is connected to other 326, then flapping travels along with "sick" 317.Its 100% the CRS328's not the CRS317's
I don't know about 328-24P-4S+, but 326 seems to have similar hardware (counting out PoE and amount of sfp+ ports) hence problems might be of similar nature.
According to the findings within this thread and the information I received from our distributor: Yes.Does this mean that Mikrotik knowingly continues to sell a faulty product?
So almost one year after, we're at the same place....According to the findings within this thread and the information I received from our distributor: Yes.Does this mean that Mikrotik knowingly continues to sell a faulty product?
In my case - yes, they were on a UPS.Hi!
I just found this topic.
Did you use the Mikrotik switch through an UPS(uninterruptible power supply - sinus wave type) hardware ?
If not, then this maybe a main problem - the power supply might have receiving some OVP/OCP/SCP effects - causing the port flapping.
Hi!In my case - yes, they were on a UPS.Hi!
I just found this topic.
Did you use the Mikrotik switch through an UPS(uninterruptible power supply - sinus wave type) hardware ?
If not, then this maybe a main problem - the power supply might have receiving some OVP/OCP/SCP effects - causing the port flapping.
Can you elaberate on what quality parameters are not up to scratch? Also, the CRS317 has internal PSUs. Furthermore - as per my last post, they have admitted hardware faults in some CRS317.Hi!In my case - yes, they were on a UPS.Hi!
I just found this topic.
Did you use the Mikrotik switch through an UPS(uninterruptible power supply - sinus wave type) hardware ?
If not, then this maybe a main problem - the power supply might have receiving some OVP/OCP/SCP effects - causing the port flapping.
I read in other topics/people, the power supply comes with the mikrotik switch - has not the best "quality".
I dont have any other idea what causing the port flapping.
I heard a story, RouterBoard copper RJ45 ports had the same strange port flapping issue - they could not solve/trace the problem: software upgrade/config changes.If the problem is on power supply there will be port flapping always, no matter what OS is running.
I have always port flapping when winning RouterOS (every single version on it) and never when running SwOS 2.7. We have a lot of 317 some connected to 326, 328 - different versions, all with SFP+ 10G running without single flap - all 317 running SwOS 2.7, other switches RouterOS or SwOS 2.9.
This is SOFTWARE problem, but I'm sure that MikroTik don't know how to resolve it - just see how many they need to produce new version on SwOS, because 2.9 is hell of the bugs.
I'm not an expert about that.Can you elaberate on what quality parameters are not up to scratch? Also, the CRS317 has internal PSUs. Furthermore - as per my last post, they have admitted hardware faults in some CRS317.Hi!In my case - yes, they were on a UPS.Hi!
I just found this topic.
Did you use the Mikrotik switch through an UPS(uninterruptible power supply - sinus wave type) hardware ?
If not, then this maybe a main problem - the power supply might have receiving some OVP/OCP/SCP effects - causing the port flapping.
I read in other topics/people, the power supply comes with the mikrotik switch - has not the best "quality".
I dont have any other idea what causing the port flapping.
I have one RMA'd with my supplier. On week 2 of the 4-6 week turn around...I am wondering if anyone has had success getting their unit repaired or replaced and if so was the problem resolved with the new/repaired unit.
My RMA (6 - 8 weeks) is only in the third week. I was told that a replacement would not make sense as new switches willhave the same problem.... So I am waiting for the repair while Mikrotik continues to selll defective equipment.I have one RMA'd with my supplier. On week 2 of the 4-6 week turn around...I am wondering if anyone has had success getting their unit repaired or replaced and if so was the problem resolved with the new/repaired unit.
All the sources indicate that is only that specific combination that this topic is affected, and maybe even then only some part of CRS317 affected.Has anyone tried the new CRS326-24S+2Q+RM Cloud Router Switch? I am wondering if it has the same port issues when connection at 10GB to other CRS3xx switches as the CRS317.
Has anyone given the new MikroTik CRS326-24S+2Q+RM a try?
Hi,
we can confirm that CRS328-24P-4S+ in combination with CRS312-4C+8XG show the exact same problematic port flapping behavior (RouterOS & FW v6.45.6) as the CRS317-1G-16S+. The exact testing scenario is:
- 2x CRS312-4C+8XG (both new)
- 2x CRS328-24P-4S+ (1 new, 1 used but "working as expected" from our supplier)
- The CRS328s are connected with SFP+ DACs to the CRS312 SFP+ combi ports
- The test scenario ran 9 days in an air-conditioned environment
The outcome is attached to this post. Some observations:
- Both CRS328 show just a few link downs (<20 Link Downs), there is no behavioral difference between the new and the used CRS328
- The CRS312s show different results 50 vs. 1129 Link Downs to the same CRS328
- The screenshot was taken on the Oct. 10th, the Last Link Down Time information do contain wrong information.
We also had two new CRS326 connected (via SFP+) to the CRS328 and CRS312 in question which did not show any port flappings during the testing period. This test is a consequence of the recommendations done by MikroTik to use the CRS312 and CRS326 as replacement for the flapping CRS317. In our tests we see that at least the CRS312 have the exact same issue as the CRS317s. There is still no evidence that the CRS328 is not part of the problem.
Conclusion:
- CRS312-4C+8XG combined with CRS328-24P-4S+ do have flapping SFP+ connections
- We did not receive any feedback from Mikrotik regarding this issue. Therefore, we will stop our tests of Mikrotiks problematic network devices.
br,
nicoh
The new CRS317 I received to test has port flapping too: 5 - 10 times a day in addition to the FCS and RX errors.I am still waiting for the RMA of my CRS317: after 8 weeks I asked the shop and they checked with MT: it is waiting for parts and no idea when they will arrive. I am quite disappointed by this whole story. What a mess!!
The shop sent me a new CRS317 that I installed today. No flaps yet but in only 2 hours I see 15 FCS errrors and 2 RX error events, so I am not hopefull.
maybe some of us are not interested in SwOS ?I posted several times above:
This problem persists only on CRS317 running RouterOS (any version).
If you don’t want port flapping at all, use SwOS 2.7 or 2.10 (don’t even try 2.8, 2.9).
We have many 317 in different configurations with heavy traffic, hundreds of vlans, many of them connected with 10G links to CSS326, CRS326, CRS328 (and many more 4011, 1009, other vendor switches and routers), WITH NO ANY PORT FLAPPING!
As SwitchOS has very limited management capabilities (web only) and not even HTTPS it is a too limited platform to be taken serious. I do not want any plaintext management traffic in my network. Once they support HTTPS I could consider SwitchOS. I only need very basic functionality anyway but this silly HTTP(S) limitation stops me from even considering SwitchOS.I posted several times above:
This problem persists only on CRS317 running RouterOS (any version).
If you don’t want port flapping at all, use SwOS 2.7 or 2.10 (don’t even try 2.8, 2.9).
We have many 317 in different configurations with heavy traffic, hundreds of vlans, many of them connected with 10G links to CSS326, CRS326, CRS328 (and many more 4011, 1009, other vendor switches and routers), WITH NO ANY PORT FLAPPING!
I noticed this comment too. I therefore upgraded my temporary CRS317 half an hour ago. Should know more tomorrow, but I am not optimistic.RouterOS 6.46 released. In the changelog:
*) crs3xx - improved switch-chip resource allocation on CRS317-1G-16S+, CRS309-1G-8S+, CRS312-4C+8XG, CRS326-24S+2Q+ devices;
Would this solve the port flapping issue? Has anybody tested it?
Don't bother testing: it took 1.5 hours after the upgrade (on both CRS328 and CRS317) for the first flap to occur on my lightly loaded networkI have CRS328-24P-4S+ and CRS317-1G-16S+ on the shelf. In the next 1-3 days, I will test RouterOS 6.46 on them in 10G.
Less than a full day ater: 29 flaps... routerOS 6.46 does not solve the issues with port flappingDon't bother testing: it took 1.5 hours after the upgrade (on both CRS328 and CRS317) for the first flap to occur on my lightly loaded networkI have CRS328-24P-4S+ and CRS317-1G-16S+ on the shelf. In the next 1-3 days, I will test RouterOS 6.46 on them in 10G.
Last Friday I received my CRS317 back from repair (took "only" 4 months) and now I have not seen any port flaps (0 link downs) nor any receive error counters increase (FCS errors not RX error events) that I used to see. So the repair was successful.The only way to fix this problem is to send your devices back to your distributor! This is not a software bug!!!
We have serveral CRS317, CRS328 and the new CRS326 and they worked now without port flappings or other problems.
Now they running with RouterOS 6.46 since last friday.
regards
I had the flapping problem on the Crs317/CRS328 combo too. I had my CRS317 repaired (took them 4 months, unbelievable) but the link between the 2 is now absolutely stable: I just checked and the link is has now been up since Dec 18 (when I rebooted both switches for a SW u[date). So it shows that the CRS317 was at least part of the problem. It might quite well be that the CRS326-24S+2Q has the same problems as the CRS317... But you can not rule out the CRS328 either.An update from my side:
We bought CRS326-24S+2Q to replace the CRS317 devices. Mikrotik support told us the flapping problem between CRS317 and CRS328-20S-4C-4S+ is caused by the CRS317. That was over 1 year ago. They also told us to buy other devices but no CRS317. That means over one year later they still sell the faulty devices!! Back then I told MT support that I don't think the problem is the CRS317 but the CRS328....
Now I testet the CRS328 <-> CRS326-24S+2Q and of course I have flapping again. 696 link downs in 3 days. Well done Mikrotik!!
We decided to switch to another vendor. That was too much. Not only the problem itself but also the handling.
If you only need 10G go for the CRS317: it works well connected to anything but the CRS328 (and possibly the CRS326).Hello
One of my partner gave me the link to that thread when I was looking for a 10G Mikrotik switch.
I'm still interested in CRS317 switch. What I need is just the following things:
* no crash
* RouterOS as I need kind of integration with other things (at least via CLI)
* no port flapping
* VLAN mapping/translation on each port. Hardware based
* dual power source
* most links will be fiber connections at 10G, but I predict mixture of 1G/10G fiber connections with none or few copper 1G connections
I have no other Mikrotik devices. But, If everything works well, I may add more CRS317 or CRS326.
If problem really related to combination of CRS317 and CRS326 I might avoid it. But, there were people saying it is same issue even with recommended CRS309.
Could you please give me (other readers) what is the status with this issue?
Thank you in advance for your information!
PS CSR312 doesn't fit as it has only 4SFP+ cages. CSR309 doesn't fit as it has only one power source (maybe, there is a possibility to use POE-IN + power supply to achieve redundant power configuration?)
Sounds good....
If you only need 10G go for the CRS317: it works well connected to anything but the CRS328 (and possibly the CRS326).
Since the repair my CRS317 - CRS328 link has been rock solid too. That connection was the only one with flapping. It is now up since Dec 18 without any issues whatsoever. I am happy.
...
Right now I only have some 10Gb DACs (FS.com) and an S+RJ10 in the switch, but I used to have some 1Gb Fiber modules to an older (now removed) 1Gb switch. Worked perfectly fine. I never tried 10Gb fiber as I had no use for it.Sounds good....
If you only need 10G go for the CRS317: it works well connected to anything but the CRS328 (and possibly the CRS326).
Since the repair my CRS317 - CRS328 link has been rock solid too. That connection was the only one with flapping. It is now up since Dec 18 without any issues whatsoever. I am happy.
...
Do you have mixture of 1G/10G connections or 10G connections only? Via SFP+ modules or DAC?
ok, you can also buy another vendor switch, but I don't think that it was the question...Switch to SwOS
Use it with no flapping
This is user forum. Support replies in some topics occasionally, but there's not guarantee they reply to your particular message. If you are looking for an official reply you should contact support@ and/or you supplier/distributor directly.Hey Mikrotik guys, where are you?
I think that after one year and an half, many support request, some device repair, some device went in the bin, and a lot of devices with the same problem, mikrotik guys could pubblicaly response and give us an idea if they want to continue seriusly making routerOs switches or not.This is user forum. Support replies in some topics occasionally, but there's not guarantee they reply to your particular message. If you are looking for an official reply you should contact support@ and/or you supplier/distributor directly.
Very funny - for you MikroTik = RouterOS ??!?ok, you can also buy another vendor switch, but I don't think that it was the question...Switch to SwOS
Use it with no flapping
Hey Mikrotik guys, where are you?
onestly, yes.for you MikroTik = RouterOS ??!?
Mail support at Mikrotik with the support files for both switches. They will probably tell you that the CRS317 needs a repair. In that case prepare for a long wait: it took them 4 months in my case if I remember correctly..... My switches now link perfectly fine: the link has been up since Dec 18: more than 5 monthsI'm also having some severe port flapping issues with a bonded 20G (2 DAC SFP Plus cables) between a CRS328 and a CRS317 switch.
Need to use RouterOS on both because I would really like to have OSPF running on both switches. (i am aware of the routing performance of these switches, no need to comment on this).
So, switching to SWOS is not an option for me.
Need a reliable fix for this as well.
You can check the logs on the CRS328 side.Quick Question : If I try to switch to SWOs to reduce port flapping, How will I know if it's solved? Is there a log event for port down as in RouterOS?
try upgrading the routerboot inside routeros, install the latest bugfix, upgrade routerboot, then reboot with switchos.
RouterBOOT is responsible for starting RouterOS in RouterBOARD devices.
Yes, because in another changelog, I dont remember where, told to start routerOS, upgrade routerboot, then restart in sw os.
I have a 326 that had tx drop, and the suggestion was to upgrade routerboot to the latest, then restart sw0s. now it is working perfectly with 0 tx drops.
According to all posters here, the problem presents itself only in connection with CRS317 and 10G SFP+. So it will not happen to your setup.Hello. I need to buy two 24 port switches and I have to choose between CRS326 and second hand Cisco 2960G, the price is the same. If I take CRS326 it will be used with RouterOS for access switch. From what I read in forum, SwOS is not ready for "in production" setups and this is the reason to choose CRS326 instead of CSS326.
My question is - if I use only 100Mbps and 1000Mbps (random mix of ports, PCs, VoIP phones etc.) connections and not 10G connections, the problem with port flapping will be present or not?
latest long-term version RouterOS
[brg3466@CRS312] > log print where message~"combo"
dec/28 02:56:00 bridge,info hardware offloading activated on bridge "bridge1" po
rts: combo1,combo2
dec/28 02:56:01 interface,info combo1 link up
dec/28 02:56:01 interface,info combo3 link up (speed 10G, full duplex)
dec/28 02:56:01 interface,info combo1 link down
dec/28 02:56:01 interface,info combo4 link up (speed 10G, full duplex)
dec/28 02:56:01 interface,info combo1 link up (speed 10G, full duplex)
dec/28 02:56:02 interface,info combo3 link down
dec/28 02:56:02 interface,info combo3 link up (speed 10G, full duplex)
dec/28 02:56:02 interface,info combo1 link down
dec/28 02:56:03 interface,info combo1 link up (speed 10G, full duplex)
dec/27 20:10:42 interface,info combo3 link down
dec/27 20:10:42 interface,info combo4 link down
dec/27 20:11:38 interface,info combo4 link up (speed 10G, full duplex)
dec/27 20:11:39 interface,info combo3 link up (speed 10G, full duplex)
dec/27 21:11:22 interface,info combo4 link down
dec/27 21:11:22 interface,info combo4 link up (speed 10G, full duplex)
dec/28 08:12:09 interface,info combo3 link down
dec/28 08:12:09 interface,info combo3 link up (speed 10G, full duplex)
dec/28 08:46:29 interface,info combo3 link down
dec/28 08:46:29 interface,info combo3 link up (speed 10G, full duplex)
dec/28 10:59:42 interface,info combo3 link down
dec/28 10:59:42 interface,info combo3 link up (speed 10G, full duplex)
dec/29 00:32:18 interface,info combo4 link down
dec/29 00:32:18 interface,info combo4 link up (speed 10G, full duplex)
dec/29 00:57:25 interface,info combo3 link down
dec/29 00:57:26 interface,info combo3 link up (speed 10G, full duplex)
dec/29 05:35:05 interface,info combo3 link down
dec/29 05:35:05 interface,info combo3 link up (speed 10G, full duplex)
dec/29 06:11:54 interface,info combo3 link down
dec/29 06:11:54 interface,info combo3 link up (speed 10G, full duplex)
dec/29 07:29:38 interface,info combo3 link down
dec/29 07:29:38 interface,info combo3 link up (speed 10G, full duplex)
dec/29 12:03:06 interface,info combo4 link down
dec/29 12:03:07 interface,info combo4 link up (speed 10G, full duplex)
dec/29 12:03:07 interface,info combo3 link down
dec/29 12:03:07 interface,info combo3 link up (speed 10G, full duplex)
dec/29 12:05:52 interface,info combo3 link down
dec/29 12:05:52 interface,info combo3 link up (speed 10G, full duplex)
dec/29 12:06:13 interface,info combo3 link down
dec/29 12:06:13 interface,info combo3 link up (speed 10G, full duplex)
dec/29 12:06:19 interface,info combo3 link down
dec/29 12:06:19 interface,info combo3 link up (speed 10G, full duplex)
dec/29 12:17:12 interface,info combo3 link down
dec/29 12:17:12 interface,info combo3 link up (speed 10G, full duplex)
dec/29 16:19:47 interface,info combo4 link down
dec/29 16:19:47 interface,info combo4 link up (speed 10G, full duplex)
dec/29 16:19:48 interface,info combo3 link down
dec/29 16:19:48 interface,info combo3 link up (speed 10G, full duplex)
dec/29 16:30:16 interface,info combo3 link down
dec/29 16:30:16 interface,info combo3 link up (speed 10G, full duplex)
dec/29 16:30:54 interface,info combo3 link down
dec/29 16:30:55 interface,info combo3 link up (speed 10G, full duplex)
dec/29 16:40:35 interface,info combo4 link down
dec/29 16:40:36 interface,info combo4 link up (speed 10G, full duplex)
dec/29 16:43:24 interface,info combo3 link down
dec/29 16:43:24 interface,info combo3 link up (speed 10G, full duplex)
dec/29 16:44:10 interface,info combo3 link down
dec/29 16:44:10 interface,info combo3 link up (speed 10G, full duplex)
dec/29 17:04:24 interface,info combo3 link down
dec/29 17:04:25 interface,info combo3 link up (speed 10G, full duplex)
CRS328-24P <-> CRS312 with 1m Mikrotik DAC, port flapping every 2 hours. both switch running Stable 7.6
…the same port flapping…
Only the PC computers connected to it do flap.
192.168.40.62 Apr 23 19:55:06 interface,info sfp-sfpplus4-tiny link down
192.168.40.62 Apr 23 19:55:08 interface,info sfp-sfpplus4-tiny link up (speed 10G, full duplex)
192.168.40.62 Apr 23 19:55:08 interface,info sfp-sfpplus4-tiny detect LAN
192.168.40.62 Apr 23 19:55:51 interface,info sfp-sfpplus4-tiny link down
192.168.40.62 Apr 23 19:55:53 interface,info sfp-sfpplus4-tiny link up (speed 10G, full duplex)
192.168.40.62 Apr 23 19:55:53 interface,info sfp-sfpplus4-tiny detect LAN
192.168.40.62 Apr 23 19:55:54 interface,info sfp-sfpplus4-tiny link down
192.168.40.62 Apr 23 19:55:55 interface,info sfp-sfpplus4-tiny link up (speed 10G, full duplex)
192.168.40.62 Apr 23 19:55:55 interface,info sfp-sfpplus4-tiny detect LAN
192.168.40.62 Apr 23 19:55:57 interface,info sfp-sfpplus4-tiny link down
192.168.40.62 Apr 23 19:56:02 interface,info sfp-sfpplus4-tiny link up (speed 10G, full duplex)
192.168.40.62 Apr 23 19:56:02 interface,info sfp-sfpplus4-tiny detect LAN
192.168.40.62 Apr 23 20:21:25 interface,info sfp-sfpplus4-tiny link down
192.168.40.62 Apr 23 20:21:28 interface,info sfp-sfpplus4-tiny link up (speed 10G, full duplex)
192.168.40.62 Apr 23 20:21:28 interface,info sfp-sfpplus4-tiny detect LAN
192.168.40.62 Apr 23 20:22:11 interface,info sfp-sfpplus4-tiny link down
192.168.40.62 Apr 23 20:22:16 interface,info sfp-sfpplus4-tiny link up (speed 10G, full duplex)
192.168.40.62 Apr 23 20:22:16 interface,info sfp-sfpplus4-tiny detect LAN
192.168.40.62 Apr 23 20:22:18 interface,info sfp-sfpplus4-tiny link down
192.168.40.62 Apr 23 20:22:21 interface,info sfp-sfpplus4-tiny link up (speed 10G, full duplex)
192.168.40.62 Apr 23 20:22:21 interface,info sfp-sfpplus4-tiny detect LAN
192.168.40.62 Apr 23 20:33:59 interface,info sfp-sfpplus4-tiny link down
192.168.40.62 Apr 23 20:34:01 interface,info sfp-sfpplus4-tiny link up (speed 10G, full duplex)
192.168.40.62 Apr 23 20:34:01 interface,info sfp-sfpplus4-tiny detect LAN
192.168.40.62 Apr 23 20:38:38 interface,info sfp-sfpplus4-tiny link down
192.168.40.62 Apr 23 20:38:51 interface,info sfp-sfpplus4-tiny link up (speed 10G, full duplex)
192.168.40.62 Apr 23 20:38:51 interface,info sfp-sfpplus4-tiny detect LAN
192.168.40.62 Apr 23 20:38:55 interface,info sfp-sfpplus4-tiny link down
192.168.40.62 Apr 23 20:38:57 interface,info sfp-sfpplus4-tiny link up (speed 10G, full duplex)
192.168.40.62 Apr 23 20:38:57 interface,info sfp-sfpplus4-tiny detect LAN
192.168.40.62 Apr 23 20:38:58 interface,info sfp-sfpplus4-tiny link down
192.168.40.62 Apr 23 20:38:59 interface,info sfp-sfpplus4-tiny link up (speed 10G, full duplex)
192.168.40.62 Apr 23 20:38:59 interface,info sfp-sfpplus4-tiny detect LAN
7.4 changelog says:It was fixed in 7.4, which is “stable,” not LTS.
What about the CRS317? Was the same lobotomy performed on it as well?switch - disabled second CPU core for CRS328-24P-4S+ device in order to improve SFP+ link stability;
CRS317 always have had 2 CPU cores no change on that AFAIK
What about the CRS317? Was the same lobotomy performed on it as well?
Could someone compare the PSU before and after an RMA? Maybe the issue could be resolved simply by replacing the capacitors with ones of higher capacitance? It makes sense, since in SwOS there were no SFP+ port flapping issues, possibly because the CPU's power consumption was lower compared to RouterOS.
P.S. What is the maximum number of active SFP+ links that the CRS317 can handle with the factory PSU?