Problem 1 - Port Auto-negotiation.
Ports 1-10 when set to full duplex 100, they do not connect (No Link) to switch I am using (Nortel 1800) (Cross or straight cable)
Ports 1-10 DO connect when I set them to auto, but they don't have duplex.
Ports 11-12 DO connect to the switch with 100 full duplex, auto or manual set.

Some questions for clarification. Have you tried turning auto off on ports 1-10 and forcing the connection to 100 half duplex? Does it work? Looks like something might be wrong making a full duplex link between that switch and the RB1100. Have any other equipment that is experiencing the same issues with the RB1100 ports 1-10?

Problem 2 - Speed
When Port 12 is plugged into our fiber demarc (Nortel 1800) and I plug a computer into ports 1-10 the speed is <5mbps if we are lucky
When Port 12 is plugged into our fiber demarc (Nortel 1800) and I plug a computer into port 11... Full speed
All settings remain the same between test ports, Auto, Manual, Duplex, etc...
It just feels like ports 1-10 are broken.

When I run speed tests between Mikrotik RB-450 and RB-1100 on ports 1-10 speed looks good, when I run speed tests THROUGH the RB-1100, using ports 1-10, the speed is terrible.

The port 12 tests involving the 1800 are routed, correct? Do you think the half-duplex negotiations are causing these issues? Maybe the Nortel and the RB just are not going to play nice with each other. It would be interesting to see if you have the problems with any other piece of networking equipment.

As for the second set of tests, I'm assuming you're routing, correct? What are the different speeds you're seeing? And when you run the tests through the router, are the two routers being tested plugged into the same 5 port grouping? 1-5 and 6-10 each have one backplane to the CPU. You'll want to have each router plugged into one group if you're testing the maximum throughput. So, plug in one into port 1 and the other into port 6 and look at the performance. You should see an improvement compared to plugging the two units into port 1 and port 2.

There definitely are big issues with the RB800/1100 ethernet. I've had an 1100 for almost a month now and cannot use it because of these problems.

My edge router is an old 1GHz Mini-ITX box with dual on-board NICs and a RB44. We're pushing peaks of 72x12Mbps on our 100Mb F/D fiber-ethernet circuit. And the CPU gets up around 95%. I think the PCI bus on these small PCs just don't have enough bandwidth to the CPU for packet routing.

Before I did anything, I first loaded v4.10 and upgraded the boot firmware to 2.27. Our uplink goes into a Cisco 3500 switch and AT&T has our port forced to 100Mb F/D (common auto-neg issues on Cisco gear). I have ether13 on the RB1100 forced to 100 F/D as well. The port randomly throws errors. I look at it and it's at 100 H/D even though it's configured for 100 full, auto is OFF. Plug back into the old router, works fine.

Ether11 and 12 randomly stop passing traffic for about 10 seconds and then the links go down and come back up, over and over. I had two Trango backhauls plugged into those ports. Works fine on the old router.

Ether1-10 didn't seem to have link or negotiation issues or errors, but I haven't tested for throughput problems on them either.

And today I upgraded to 5.0beta4, same problems all around. I sent MT support a supout from it after the testing. I hope they find the problem(s) and fix it.. soon.

Just a "me too" with RB1100 and Ports 11 through 13.

Does anyone have update on a fix? I need the bypass...

Thanks,

Andy

Ports 1-10 when set to full duplex 100, they do not connect (No Link) to switch I am using (Nortel 1800) (Cross or straight cable)

What is exact configuration for both end (auto-negotiation=yes/no, full-duplex=yes/no, speed)?

DO connect when I set them to auto, but they don't have duplex

If one end has auto-negotiation enabled while disabled on the other, half duplex mode will be used on auto-negotiation end.

When Port 12 is plugged into our fiber demarc (Nortel 1800) and I plug a computer into ports 1-10 the speed is <5mbps if we are lucky

What results are you getting if you pass traffic through ether1-ether5, ether1-ether2 and ether6-ether7?

Please generate and send supout.rif file to support@mikrotik.com from configuration having these problems.

kewlkeed, poor speed could be result of duplex mismatch. We will investigate why this link does not work at forced 100FD.

verdonker, please send supout.rif file to support@mikrotik.com

I, have the same problem. we are waiting for a urgent solution.

Thanks

Luis

I was asked by kirshteins through the ticket I have open with MT support to back the CPU speed down from 1333 to 800 and the memory speed down from 533 to 400 and see if this problem still exists and send a supout. Did all that. Even backed both the CPU and memory clock down to 333MHz, no difference.

We have an F/O link from AT&T and the demarc/termination is a Cisco 3500 (or 3550, don't remember) switch. They always hard set the copper ports to 100 FD. There are known auto-neg issues with Cisco gear and non-Cisco gear.

So this time, instead of driving all the way to the site and taking my whole network down, I tested on the bench.

Set ether13 forced to 100 FD. Set my laptop to the same. RX errors continuously. Tried two managed switches and a Cisco 1800 router, all forced to 100 FD, RX errors still.

Set ether13 to auto, laptop to auto, switches and router to auto. At first it didn't work on my laptop. Unplugged the cable to bring the link down, plugged it back in, everything works fine.

So this tells me that, even though in Winbox the port is forced to a speed and duplex, it still auto-negotiates. With the other devices forced, the RB1100 still auto-negotiates, even though the interface status says it's running full-duplex, it's really only half-duplex while the other end is full. Duplex mis-match = errors and terrible speed.

Still don't know why ether11 & 12 links suddenly and randomly drop out. I have every port set to auto-neg except ether13.

This is obviously some kind of ethernet hardware and/or software-to-hardware communication problem.

I needed this thing working like a month ago. Please fix it MT, please.

Did you test your Cisco Catalyst 3500 and RB1100 port 11-13 enable auto-negotiation and make gbit connection over twisted pair.

I experience the same issue. Connected an RB1100 Ether11 to a cisco ME3400 switch. Interface resets every 10 seconds or so. Ether12 and 13, same issue. All other interfaces works fine. Tried another RB1100 with the same issue. This is a really nasty error.

I experience the same issue. Connected an RB1100 Ether11 to a cisco ME3400 switch. Interface resets every 10 seconds or so. Ether12 and 13, same issue. All other interfaces works fine. Tried another RB1100 with the same issue. This is a really nasty error.

Is there are auto-negotiation enabled on both end or is it forced 100FD link? Please send supout.rif file to support@mikrotik.com

The interfaces are set to auto-negotiation. I probably won't have time to replicate the issue as I'm leaving for holiday later today, but I'll make sure to get back to you when I get back.

I see wrong interface statistics in Port 11-13.

Plugged in a device in one of those ports. Removed this device.
Now I see incoming Traffic >200MBit on this port.
Connecting s.th. to this port it looks ok. After reboot all is ok again.

Another "me, too". Couldn't get 100FD hard set on both sides to work between an RB110 and a Cisco 4507 on ports 11-13. Auto-negotiation had the port fail randomly.

Migrated configuration to ports 1-10 and all is well.

Another me too here. All 3 1100s have the exact same problems with these 3 ports. Errhhhmmmm... I REALLY HOPE I am wrong here but there maybe something more to this than just a simple software fix. It looks more like a hardware bug...

I have turned off auto negotiation everywhere and the problems seem to have stopped for the past 2-3 hrs anyway.

are you guys all restoring backups on these 1100's to get them configured? I had a friend run into the exact same problem and I told him no way is it a hardware problem, although it sure seemed like one. I took control and ran a /system reset-configuration and reconfigured it from scratch and all those problems went away. I know a backup should have nothing to do with full duplex / auto negotiation, but something was seriously wrong to the point it wouldn't work with a restored backup. After making it work I used diff to check the differences between the old config (before reset) and the new config - and there were no differences... so maybe it's something that gets corrupted outside of the visible config.

Just a shot in the dark... same thing happens on the wireless config reset, for some reason it just fixes things.

Mine were new configurations (copy/paste a text template into the CLI), and applied straight to how the router shipped with a few of the default packages removed. The interface configuration in that template only deals with interface names, all other interface changes were made manually.

New config here also but speed and duplex negotiation doesn't really have to do much with configuration in most cases when set to auto. This is really a hardware implementation problem and a pretty old one actually that used to happen quite a lot a few years back.

No, not a .backup file here. I exported the config from my old router, edited for the new hardware (removed ALL ethernet settings), and it imported IPs, routing, firewall, queues, etc. without issue.

5.0b4 or 4.10, doesn't make a difference.

Set my laptop to 100 full, Rx errors on every port of the RB1100 forced to 100 full. Laptop and RB493AH works fine forced to 100 full. Laptop and managed switches, laptop and Cisco switches, laptop and Cisco routers all work fine. RB493AH to RB1100 ethers 1-10 works fine, 11-13 does not.

Anyway, I couldn't wait any longer for the 1100 to be fixed. So I bought a Roc-Box from Tom @ Roc-Noc. It has seven Intel 82573L Gbit NICs and uses the PRO/1000 driver. Forced to 100 full works perfectly fine with everything. I have it running v4.10 right now on the edge of my network routing about 75Mbps and 12k PPS and the CPU only hits 10-15%. And it has an expansion slot for other NICs. I would've been perfectly happy with the RB1100 if it worked AND I wouldn't have needed to install a new rack to fit the Roc-Box. But when MT figures out the 1100 issues, I'll be happy to know that I have a backup router.

The workaround of this 1100 hardware glitch is to turn off auto negotiation. No more disconnects for me here after this.

THIS MUST BE DONE IN ALL DEVICES CONNECTED TO PORTS 11-13.

What I wonder though is if Mikrotik acknowledges the problem and is going to replace the boards having this hardware failure.

Try to test with recently released v5.0beta5 if possible.

I will setup a test router sometime next week and let you know but even if this works, I don't really feel comfortable using betas in production routers. Shouldn't the fix also apply to future v4 releases?

The v5.0beta5 seems to work as it should with the default settings (auto negotiation turned on at both sides). However, I still get errors and extremely slow connection problems when I turn auto negotiation off at both sides and I set duplex to half at 100Mbps. I have tested with a couple of different switches and every time I set duplex to half I get the same bad results.

But wouldn't you expect extremely bad throughput on half duplex?

Why do you need to use half duplex at all on wired Ethernet ports?

But wouldn't you expect extremely bad throughput on half duplex?

Why do you need to use half duplex at all on wired Ethernet ports?

Yes, I would expect slower speeds but not EXTREMELY BAD.

I don't need half duplex in case I have full. However, there are still cases of people having hubs which means half duplex or even faulty auto negotiation which also usually means half duplex. I was under the impression that 1100 is suppose to work in half duplex mode also, or is it not?

Fair. What kind of results are you getting?

Something like 100-200k!!!

After some more extensive tests, even the beta is not working right. All interfaces seem to open at 100/FDX with auto negotiation on however the transfer speed is really slow again no matter how many times I recycled the Cisco switches or the 1100s. THE ONLY way I got the 1100s to work correctly even with the v5 beta is the same as with the v4 and that is by turning auto negotiation off everywhere (Ether11-13) and thats all there is to it! I don't think this can be fixed by software upgrade as IMHO indicates a hardware problem. I wonder what Mikrotik has to say about all this though.

Please send supout.rif file to support@mikrotik.com. Generate it while you have auto-negotiation enabled on ether11-ether13. What exact devices are connected to those ports?

This sounds like standard Cisco auto-negotiation problems to me.

Just lock the ports each end at 100mbit FDX and you will have no problems. This is not limited to Cisco+Mikrotik, it also happens when you try and connect many other brands of equipment to Cisco switches.

Please list exact device names you are experiencing problems with when connected to RB1100 ether11-ether13. Also state their transmission parameters (speed, duplex mode) if auto negotiation is disabled.

All 3 (11-13) trouble making ports are connected with a couple of Cisco L3 2948G switches. The only way that worked without giving me trouble was with auto negotiation off at 100/FDX. I will be submitting the supout file soon.

This sounds like standard Cisco auto-negotiation problems to me.

Just lock the ports each end at 100mbit FDX and you will have no problems. This is not limited to Cisco+Mikrotik, it also happens when you try and connect many other brands of equipment to Cisco switches.

I am not so sure about this here. Some early Cisco products (and a few other brands to be fair) had these auto negotiation problems as you say but I am afraid this is not the case now. In our L3 2948G switches we have connected just about anything from 3Com, Compex, Intel, other Cisco, Broadcoms, variety of Realtek chipsets and the only ports that have manual duplex and speed are those connected to the 1100s. If I lock them everything works fine. However, just for testing purposes as I also mentioned before, I locked both sides at 100/HDX and they still had problems.

It seems to me that the pressure to send new products out is causing big corners to be cut.

As ROS on Mikrotik is kind of Mature, we expect it to work.
That is a compelling reason to Buy Mikrotik - we believe it will work out of the box.

IF i have doubts that the MT New Product might *Not* work, and therefore do not Buy It until the bugs are ironed out, only Mikrotik Sales are affected : we can buy other stuff.

I cannot afford, nor do i want, to spend my money and Wait for a Fix for equipment that doesn't work as expected - that affects my Money, my Service, my Customers and my Reputation.

That's the main reason i fell out with Ubiquiti as regards AP equipment - their CPE is great VFM when you can get it.

Feeling that MikroTik is starting to make a Big Mistake right now is disturbing, and not just as regards the RB1100.

I sincerely hope that MT can be honest with their Loyal Customers, and sort out the Plan.

My hope is that MT keep on making great kit at affordable prices - not cheap, just Good, Affordable and Working 99% (nobody's Perfect).

Paradyne ADSL2 modem, 100/full duplex. Works on Ports 1-10, but every 10-30 seconds, goes offline on 11-13. D-link DES-3028P.

Tried on 5.0b5,6,7 w/ latest boot loader.

EDIT: Both 100 and 1000 ports on Dlink. Also tried forcing 100 FD and 10 FD with same results.

We are having trouble with our RB1100 's , Ether 2 connected to a cisco 3500 switch drops every 10 seconds or so when speed is fixed to 100 and duplex to full, when both ends are set to auto it can work fine for 3 or 4 days then the port will keep dropping randomly ! This of course is proving to be a nightmare with ospf etc etc.

Is there no chance of Mikrotik continuing production of the RB1000 ? WE had no problem with them, i have tried to get old stock everywhere but no luck !

Regards
Darren

Have anyone tried to reinstall problematic RB1100 using Netinstall and reproduce this problem with default configuration?

I think there appear to be many people having the same problem that it is most likely hardware, our config was manually entered, it still had this problem with only a single ip and default route set.

Regards
Darren

I had the same problem I cant reintsall via netinstall because is operating.. only in weekends can test it.. please mikrotik lets us a solution

ok guys, rb1100 into cheap rubish switch and it has not dropped now for a week ! it just seems to be with cisco's !

Regards
Darren

Have anyone tried to reinstall problematic RB1100 using Netinstall and reproduce this problem with default configuration?

What relevance would that have. You have A LOT of people having the same problem. Default config or no, the device wont keep a link with many different types of hardware....

All 3 (11-13) trouble making ports are connected with a couple of Cisco L3 2948G switches. The only way that worked without giving me trouble was with auto negotiation off at 100/FDX. I will be submitting the supout file soon.

We tested multiple RB1100 with Cisco L3 2948G and did not experience any problems. Please describe what kind of traffic is being forwarded, configuration of both devices and other conditions to reproduce this problem.

did u test it with wimax CPE? Ive the same problem...

Is the original poster still having those issues ? The same symptoms are happening at a similar scenario.

Can anyone test whether link drops occur by entering RouterBOOT setup and testing from that point?

the same problem exist with HP Procurve 2610-48 switch: both ends (procurve and rb1100) configured auto. port 1 on rb1100 gets max 100mbps. Any attempt to force 1gb link speed simply disconnects rb1100 forever. I use firmware 4.15 with latest boot loader (2.27 i think). Configuration entered on clean system, no config imports done. Any solutions?

AndrewMT, I have RB1100's connected to HP ProCurve 2610's at gigabit at many client sites.

Check the firmware release on the 2610.

Thanks, I will check. Would you suggest using ports 1-10 on Mikrotik with Procurve, or 11-13 work too on gigabit speeds for you?

Additionally 4.16 is out, and I believe that takes the firmware on RB1100s to 2.29 (RB1000s go to 2.30).

Has anyone followed up on this issue yet? The thread seems to have ended unresolved...

We we still have not found a solution, well we did, install the software on pc boards with network cards in. We have given up on the rb1100's for now, i only wish we could source some rb1000's from somewhere....

Regards
Darren

I just shot another supout to Mikrotik on 5.0rc7. Still getting the flapping ether11-13

I either need this working now, or a replacement RB1000

This is getting really old. Had the thing for 8 months now, reported the problem, they cant seem to fix it.

I have no use for this brick

I have similar issues with my rb 1100 but on ports 1 and 2 going to a cisco 3640 i think it is. i have tried everything i can think of to keep my router up and nothing has worked. before the rb 1100 i was using a custom dual xeon server with 1 gig ram 1 20 gig hd for mt os and 1 80G hd for proxy. the dual xeon server was also doing the same thing where it would reboot or lock up with no consistency and only option was to manually reboot and wait for the next time. sent supout file from xeon server and was told to set ether1 to auto. Still no help yet to get that working. Switched to rb 1100 same issue and still no help after sending supout file. I think my only option left is to get a cisco so my network will stay up. i have been using MT for years and i am very disappointed.

Found that if i disable all mangle rules for ether1 and also disable queues that use the mangle rules then router will not reboot or lock up randomly. Router has been up and going for 2 days since disabled but now i cant filter or manage traffic with my queue tree/mangle rules. Any ideas?

Yeah, I found the same thing. But only mangle rules that affect ether 11-13. And it SEEMS only mangle rules that have a queue acting on them.

Yeah, I found the same thing. But only mangle rules that affect ether 11-13. And it SEEMS only mangle rules that have a queue acting on them.

This problem will be fixed in next release of RouterOS v4.x and v5.x. Thank you for the input.

Can anyone confirm the resolution of these issues? Which version of ROS resolves the issue or is it not out yet?

We have a RB1100 we have taken out of service and would like to use it again.

Rick

Can anyone confirm the resolution of these issues? Which version of ROS resolves the issue or is it not out yet?

We have a RB1100 we have taken out of service and would like to use it again.

Rick

Yes, i have a device in production now, after some testing with 4.17; Problems with Port 11-13 are gone.

Martin

I just shot another supout to Mikrotik on 5.0rc7. Still getting the flapping ether11-13

I either need this working now, or a replacement RB1000

This is getting really old. Had the thing for 8 months now, reported the problem, they cant seem to fix it.

I have no use for this brick

Having the same problem - what was the outcome in your case?

Sure wish I had read this forum before we bought all of our RB1100's and RB1200's. Ethernet flapping all over the place! How about you folks at MT testing this stuff before releasing to us for beta testing? My subscribers aren't impressed nor are my investors.

Just about done with MT!

Sure wish I had read this forum before we bought all of our RB1100's and RB1200's. Ethernet flapping all over the place! How about you folks at MT testing this stuff before releasing to us for beta testing? My subscribers aren't impressed nor are my investors.

Just about done with MT!

You are replying to a very old thread. All these issues have long been resolved. Are you using RouterOS v5.11 and newest bootloader? There is no "flapping" or anything else. If you have specific problems, email support and we will try to work them out.

Hello, I am going to use RB1100 on primary GW, what is the best ROS version for this? Is 5.11 stable with RB1100? no packet lost on eth? or rebooting? Thanks

///If I upgrade it to 5.11...bootloader will be upgradet too? Or I must manualy upgrade bootloader? Thanks. 2,30 is the newest?

I dont think that it is fixed. i am still not able to get a link between a RB1100AHx2 to a Cisco 3550 at gigabit-speed. The RB1100 which was in place worked with the 3550 without any problems.

I dont think that it is fixed. i am still not able to get a link between a RB1100AHx2 to a Cisco 3550 at gigabit-speed. The RB1100 which was in place worked with the 3550 without any problems.

Please try not to cross-post to multiple threads about the same issue. Have you tried using a different cable (CAT6, better brand)? Have you tried connecting other Gigabit devices to the same Cisco port? They link fine?

Let's continue discussion here: http://forum.mikrotik.com/viewtopic.php?f=2&t=61475