I have an RB600 with OS 3.13. For unknown reasons, all traffic to port 2 stops intermittently. I can not even ping the IP of that port when conected to it, however I can ping it's IP from both port 1 and 3.

Sometimes the problems corrects itself and traffic starts to flow on it's own, other times, a reboot is required. Disabling and Enabling Port 2 has no effect and there are no log entries to help.

I can't say for sure, but often the problem happens when I am running Torch on Port 1 which is our WAN and Port 2 is our primary LAN with about 90% of our traffic. WAN is a 10mb Fiber link.

We have an RB450 that is used as a backup and it does not suffer from this problem, however it has been known to reboot completely on occasion hence the reason we bought an RB600.

I did try OS 3.16 before it was said to be the stable version had actually found the problem to be worse.

Any suggestions welcome.

Greg

Same problem here. I have an RB600 with a GigE device connected to it. Out of the blue this morning, the port locked up. It showed a few Kbps of TX traffic, but 0Kbps RX. A reboot caused the locked port to work OK, but then one of the other ports locked up in the same manner. After a couple more reboots, all ports were working fine.
This has to be a software issue....

We had this happen when we installed our first RB600 a couple months back. I though it was the device that was plugged into it, so I replaced that device and didn't have any problems until today.

I'm running ROS 3.15 with hardware firmware 2.18. I will be upgrading to ROS 3.16 tonight to see if that helps.

I've heard of interfaces flat out disappearing on the RB600s, and some people recommend downgrading the firmware to 2.16 to fix that. I'm not sure I want to try that, as it seems to be a different problem altogether.

Allready have 2.16. On previous RB600 I tried 3.16 and seemed to have more problems than 3.13?

routerboard: yes
model: "600A"
current-firmware: "2.16"
upgrade-firmware: "2.16"

Let me know if 3.16 helps you!

I recommend 2.18 bootloader, it has many important fixes for Rb600

Do I have to upgrade to ROS 3.16 to use 2.18 or is there a seperate update available?

upload this file to your router with FTP:

http://www.routerboard.com/files/rb-2.1 ... 3-2.18.fwf

then run command "/system routerboard upgrade"

Are you by chance using VRRP on the interface that stops responding?

I have had a few occurrences on one of our 433AH devices that had the same symptoms. This last time that we had the problem reboots didn't help. I eventually disabled the VRRP instances and traffic started to flow again. VRRP showed that it was the master on this router and also the router on the remote side thought it was master.

No, I do not use VRRP.

I'm not using VRRP either.

I was using 5 Simple PCQ queues and after reading another thread decided to remove all simple queues. So far, no lock up, but it is still early to point the finger at PCQs. Will report back later.

UPDATE. Despite having removed queues, a port has locked up once again. This time it was port 3 rather than port 2.

I had uploaded 2.18 file and now since the RB600 locked again, I was forced to restart and am now running 2.18 firmware.

Will see if 2.18 is any better.

So far so good... knock on wood!

Up 1d 18h since reboot with no lockup using 2.18 Firm and 3.13 ROS.

See we now have 3.17 as stable download... tempted to give it a try and add back queues etc?

I upgraded to 3.16 with 2.18 firmware and had to reboot a few times just to get all ports working normally. Maybe I'll try rolling back to 3.13.

Let us know if it remains stable for you. If so, I'll probably do the downgrade ASAP.

2d 2h and still going without issue. Think I will stick with 3.13 until another lockup happens.

Bad News. Port 2 dropped all incoming traffic once again and required reboot to resolve it.

Going to prepare a P4 PC with 3.13 and see if the same problem persists with my config. Should help me decide if it is the RB600 or the ROS that has issues.

If it is RB600 fault, please contact support with as much details as you can

Those with any RB600 related issues, try to lower the CPU frequency and then see if it reboots or loses a port. Also run a Memory test in the Bootloader setup. It will run for 15 minutes and tell you if the memory is good or bad.

Same as before - you have to use RouterOS v3.17 and Bootloader v2.18 while doing this.

PC Has been running flawlessly. I have to assume it is RB600 related. Don't have time to experiment with it any further. Going to leave it on the shelf or trade it for an RB433AH. (Can't afford the 1000U)

Still having problems here on 3.13. Mikrotik Support suggested lowering the CPU freq. and/or putting a fan on the CPU, so I wonder if they are thinking that it's an overheating issue.
However, my board is on a tower where the temps are 10-30 degrees Fahrenheit. The latest outage we had was when the temperature was around 20 degrees.

Maybe it's faulty hardware???

I can't believe that no one else is having these problems.

If it's possible to take it down for inspection, closely observe all parts on the device, maybe there is something loose, or there is bad connection for some part.

Also maybe you have another RB600 that you could try to put in place of this one?

I've also been experiencing this problem. ether3 kept failing after several hours. I upgraded to firmware 2.18 and did not have the problem for almost a month, but it just happened again. I'm running RouterOS 3.19. The switch that ether3 is plugged into reports many rx errors for that port. The router is in a datacenter, so I don't think there are any environmental factors such as heat or power that would be affecting this.

Exactly the same problem here with RB450G.

Randomly in time, one port stops to work under load (30Mbps FD link). Maybe it will be related to Gigabit implementation of Mikrotik.

PD: in the affected port there are a lot of Rx Errors, more then 14000 in three minutes.

PD: I use 3.27 software version and 2.20 preinstalled firmware

I too am having this same iss with a new RB450G.

Port 1, the wan port as I have it configured, seems to just lock up.

Is there anyone else experiencing issues with this?

I had the problem with both the factory 3.22 that was loaded and still after upgrading to 3.27

I did notice that there was some junk in the header for winbox ex.
WinBox v3.27 on RB e8Aa... etc.

If there is any one with an idea of what could be happening any help would be welcomed!!

ps.. I just reloaded a fresh copy of the 3.27 os and the garbage in the header is gone... I will don't know if that was the issue but will update later, unless anyone has any suggestions.

I upgraded my RB600s to RB450Gs about 6 months ago. I haven't had any issues. I'm running 3.21 on both.

Well even after a fresh reload of the OS, port 1 just locked up again. Port 2 is working fine but port 1 continues to lock up randomly. I am switching our connection from the carrier to another port to see if that makes any difference.

Any ideas why this port keeps locking up?

Hi,

Got a similar problem on on of our RB600's. The eth2 was connected to a media convertor to connect to our core switching via singlemode fibre. The RB unit suddenly stopped working about a month ago and we upgraded both the Fw to latest version and to ROS 3.30. After this, unit seemed to work fine. This last weekend same unit stopped again - same problem. At this point we connected it to a 10/100mb copper port and it works fine. Problem seems to be the ethernet port autonegotiation - when connected to a Gigabit port it starts flipping from 10mb to 1Gb quite a few times per second (observed this via Winbox) and no traffic can pass through. When connected to a 10/100mb port - works a charm and connects at 100mb immediately.

Any ideas what could be wrong here?

Rgds,
Mark