Dear TP-Link Support,

I am experiencing a recurring issue with the ER8411 router in two separate networks managed by the OC200 hardware controller.

In both cases, the ER8411 router worked perfectly for several months in a production environment using a static IP configuration. However, at some point, the router becomes unreachable — it stops responding to pings and disappears from the network. When disconnected from the OC200 and used in standalone mode, the router operates normally and remains stable.

The issue reoccurs each time I perform a factory reset and re-adopt the ER8411 through the OC200 controller. As soon as the router is adopted, it becomes unresponsive and disappears from the network again. This happens even when I pre-configure the correct static IP, gateway, and DNS settings, and even when DHCP is enabled temporarily during the adoption process.

I strongly suspect that the OC200 is pushing a configuration to the ER8411 (possibly changing its IP address, VLAN assignment, or interface status) which causes the router to disconnect itself from the network. Unfortunately, there is no option to prevent the controller from pushing its configuration immediately after adoption, nor is there any way to selectively disable specific settings being applied to the router.

Both my OC200 controllers are updated to the latest firmware (v5.15.20.39) and the routers are running firmware v1.2.2. This issue affects production environments and significantly disrupts network availability.

Could you please investigate this behavior and let me know if:

1. There is a way to adopt the ER8411 without forcing a full configuration push from OC200?

2. This issue is known and being addressed in a future firmware update?

3. There are any workarounds to prevent the router from becoming unreachable after adoption?

I am happy to provide logs or configuration files if needed.

Thank you in advance for your support.