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