Hi,

I have a POP with a RB1200 router. It has WAN (eth1) and LAN (bridged eth2 to eth10). It is routing only (no nat), DHCP server, PPPoE server, DNS server and nothing else
It had 5.25 installed
It has been working flawlessly for years without issues.
Now I have disconnected equipment in eth9 and eth10 (no longer in use) and as our technician was there, asked him to update firmware to the latest (bug fixes only) 6.32.3.
Then I'm getting alarms about customers in eth7 or eth8 are not reachable. For example when this happens on eth7, there is no RX traffic nor RX packets on such port. The port is UP and I can disable/enable/etc.. but no traffic passed.
It is only fixed by reboot of the RB1200 and it works again for several hours then it suddenly happens. It is only happening in eth7 or eth8.
I have downgraded to 6.30.4 as I have others RB1200 with this FW working correctly (but ports used up to eth7).

Any idea?

Can I downgrade again to 5.25? Will break something?

Regards
Antonio

Have you upgraded the firmware?

See System > Routerboard.

Have you done a reset to no defaults after upgrading ROS/Firmware?

Do so if haven't done it yet, make sure you save a configuration export prior to ressetting, and reload it afterwards.

Hi,

yes firmware has been upgraded to 3.10

So you recommend to reset to default and reload configuration? It happened to you too?

I have to be very sure as the device is located far from our premises and I have to send technician...

Regards
Antonio

Hi,

yes firmware has been upgraded to 3.10

So you recommend to reset to default and reload configuration? It happened to you too?

It's not my recomendation, is general good practice with any kind of hardware/software units... specially with "embedded" devices.

And yes, it's the first thing I routinely do with devices after major upgrades, or with devices showing "misbehaviour".

In it's fact a requirement prior to filing an RMA with mikrotik (and most manufacturers) due to this.

Symptoms however (only happening on two ports) may indicate defective hardware; I'm just pointing you to the general troubleshooting steps you should follow when facing hardware with unexpected behaviour.

The next step would be a netinstall, this process "formats" the nand memory, then reinstalls everything.

I have to be very sure as the device is located far from our premises and I have to send technician...

Regards
Antonio

If that's the case and you're going to do it remotely you'd better have someone skilled to do so, or at least have someone warned with physical access to the device, just in case...

The netinstall could be done by someone skilled remotely.