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.
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.
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.
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.
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.
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?