SFP Module on WAN2,Flapping not getting DHCP from ISP

Routers
1

I have encountered a significant issue with the Route10 device: the WAN 2 SFP+ port fails to come online automatically after a restart.

To get the connection back up, I have to perform a tedious workaround: I disconnect the SFP module, plug it into an old fibre-to-LAN converter, and then reconnect it to the WAN 2 port. After waiting about 10 minutes, the port finally receives a public IP via DHCP from the ISP.

I have performed the following tests:

  • WAN 1 Comparison: If I use the fiber-to-LAN converter on WAN 1, the Route10 receives an IP almost immediately.

  • Other Hardware: If I connect the fiber-to-LAN converter to the WAN port of a different router, it also pulls an IP quickly.

Despite our fiber connection being 1G, I have tried setting the WAN 2 link to auto-negotiate, default, and forced 1G, but none of these settings resolve the issue. The SFP port seems unable to negotiate a link with the ISP’s downstream device on its own.

Could you please help me investigate why the SFP+ port is failing to initialize and negotiate this link correctly and get IP via DHCP?

I can collect the logs for investigation. I really appreciate the help to get the issue resolved, i want to connect the ISP fiber directly to the WAN2 port. Every time I restart Route10, the WAN2 port will not come up/get DHCP from the ISP.

2

Thanks for reaching out.

The easiest way to diagnose this is if you have a second WAN connection that can be used for debugging while the flakey one is down after a reboot.

If that’s not a possibility, we can still use logs from your device to understand the issue. If you enable persistent logging (from settings, set it to 3 MB), mark the timestamp when the connection was down, and the time when you brought it back up manually, and then you can DM me the logs.

3

Hi Alta-Jeff

i have sent you the logs, i do not have an option for setting up seconday WAN connection,