Configuration settings for Sonic fiber for Ubiquiti Dream Machine?

[js9erfan]

I ran the ethtool on my setup too after SSH into my UDM SE. Here's what mine looks like.

The setup:
Sonic Adtrans ONT (10Gbe) → Eero POE Gateway (10Gbe) → Ubiquiti UDM SE (SFP+ in port 10 with a very new SFP+ to RJ45 module from Ubiquiti) and all new cabling. Eero is in bridge mode.

I've also tried this setup but noticed zero improvements to the Sonic connection instability:
Sonic Adtrans ONT (10Gbe) → Ubiquiti UDM SE (SFP+ in port 10 with a very new SFP+ to RJ45 module from Ubiquiti)) and all new cabling. Eero is in bridge mode.

As a test I would remove the eero from the equation and connect the ont to the udm via the 2.5g ethernet port. See if you experience the same disconnects. Also disable smart queues on the unifi network controller if enabled. You may try setting the speed/duplex manually to 10g when connected via the sfp+ module to see if that helps. Also try the early access firmware version mentioned above or found here. Lastly, to see if its isolated to the udm, remove the udm so its ont > eero and see if you have same disconnects. Basically process of elimination.

[shio_ramen]

I ran the ethtool on my setup too after SSH into my UDM SE. Here's what mine looks like.

The setup:
Sonic Adtrans ONT (10Gbe) → Eero POE Gateway (10Gbe) → Ubiquiti UDM SE (SFP+ in port 10 with a very new SFP+ to RJ45 module from Ubiquiti) and all new cabling. Eero is in bridge mode.

I've also tried this setup but noticed zero improvements to the Sonic connection instability:
Sonic Adtrans ONT (10Gbe) → Ubiquiti UDM SE (SFP+ in port 10 with a very new SFP+ to RJ45 module from Ubiquiti)) and all new cabling. Eero is in bridge mode.

As a test I would remove the eero from the equation and connect the ont to the udm via the 2.5g ethernet port. See if you experience the same disconnects. Also disable smart queues on the unifi network controller if enabled. You may try setting the speed/duplex manually to 10g when connected via the sfp+ module to see if that helps. Also try the early access firmware version mentioned above or found here. Lastly, to see if its isolated to the udm, remove the udm so its ont > eero and see if you have same disconnects. Basically process of elimination.

I’m the one who connected to Ubiquiti support to provide that screenshot, so i’ve already tried the 4.1.11 version. They told me they’re done their own troubleshooting (with my support log export download) to rule out the UDM as the cause.

Smart queue was never enabled in Auto and in Manual settings. Zero effect.

Changing to UDM SE’s port 9 2.5Gbe doesn’t change the level of disconnections.

The UDM SE uses vanilla configuration settings with only the use of new Ubiquiti SFP+ for the 10G connection) in Port 10 for WAN.

Already done this process of hardware elimination before as stated in the thread.

When the UDM SE is plugged directly into the AdTrans ONT (without an Eero gateway like POE or a Max 7), I get similar disconnections.

UDM SE is needed for the entire home’s Ubiquiti cameras including the door bell, so there simply cannot be complete removal beyond testing.

When Ubiquiti is complete cut out and only Eero Max 7 is plugged into the AdTrans ONT, I still get disconnections easily and the disconnections are very noticeable during Zoom (throughout the day) unfortunately.

Even tried using the AdTrans’s 1G port instead of the 10G port, but got the same outcomes.

[jakemauer]

@shio_ramen Are you running the alpha version of UniFi OS 4.1.11? If not which version are you on currently?

Also if you're getting disconnections regardless of what router is plugged into the ONT, then that would indicate the ONT is the problem right? I had similar issues with my ONT where it rebooted under full load during a technician's directly connected bandwidth test and he got approval to swap out the ONT from his manager and did it on the spot.

[shio_ramen]

@shio_ramen Are you running the alpha version of UniFi OS 4.1.11? If not which version are you on currently?

Also if you're getting disconnections regardless of what router is plugged into the ONT, then that would indicate the ONT is the problem right? I had similar issues with my ONT where it rebooted under full load during a technician's directly connected bandwidth test and he got approval to swap out the ONT from his manager and did it on the spot.

Yes, I updated to UniFi 4.1.11 already as advised by Ubiquiti as soon as I received the response.

Screenshot 2024-12-27 at 12.09.49 PM.png (115.01 KiB) Viewed 3104 times

We just had the ONT swapped out on 12/24 for a new one. Unfortunately we still saw the disconnection a few minutes later after the replacement AdTrans ONT was installed (even after the latest firmware was pushed by Sonic) and a few times within the same hour. This was despite the fact that the new AdTrans ONT was wired directly to the Eero POE gateway (which is just a Eero Max 7 without WiFi capabilities), which the Eero first setup that Sonic prefers.

That was how the onsite Sonic technician and I were able to narrow the issue cause down to somewhere from AdTrans to the street poles, rather than the Ubiquiti hardware or the Eero hardware, both of which are already all running the latest software and firmware versions.

[shio_ramen]

Here are the traceroute when I cut Eero out completely (so that it's just AdTrans to Ubiquiti UDM SE, and no Eero in between)

Screenshot 2024-12-27 at 12.33.29 PM.png (166.67 KiB) Viewed 3092 times

Screenshot 2024-12-27 at 12.36.45 PM.png (190.89 KiB) Viewed 3092 times

[shio_ramen]

And traceroute 8.8.8.8 from the MacBook Pro directly to the Eero Max 7 that's connected directly to AdTrans ONT. UDM SE downstream to all the Eero's.

Screenshot 2024-12-27 at 3.21.19 PM.png (208.72 KiB) Viewed 3029 times

Screenshot 2024-12-27 at 3.21.05 PM.png (226.54 KiB) Viewed 3029 times

Screenshot 2024-12-27 at 3.26.04 PM.png (159.68 KiB) Viewed 3028 times

[shio_ramen]

Traceroute 8.8.8.8 from the MacBook Pro directly to the AdTrans ONT via a 2.5G ethernet adapter, so no Eero and no Ubiquiti Dream Machine.

Screenshot 2024-12-27 at 3.34.27 PM.png (183.05 KiB) Viewed 3021 times

Screenshot 2024-12-27 at 3.34.15 PM.png (192.77 KiB) Viewed 3021 times

Screenshot 2024-12-27 at 3.43.01 PM.png (191.48 KiB) Viewed 3019 times

[js9erfan]

If the Sonic tech who replaced the ont suspects there's an issue between the ont and the street I would call Sonic and request they send a tech out to troubleshoot further. Assuming you have tested more than one wired device (and ethernet cable) while directly connected to the ont and are still seeing disconnects then there's not much more you can do here.

[shio_ramen]

Traceroute 8.8.8.8 from the MacBook Pro directly to the AdTrans ONT via a 2.5G ethernet adapter, so no Eero and no Ubiquiti Dream Machine.

Screenshot 2024-12-27 at 3.34.27 PM.png
Screenshot 2024-12-27 at 3.34.15 PM.png
Screenshot 2024-12-27 at 3.43.01 PM.png

Paying more attention to these output from traceroute 8.8.8.8, it seems like there are some hops that have abnormally high latency, with some spiking to over 4 seconds (e.g. ae1.cr6.rcmdca11.sonic.net).

ae5.cr3.colaca01.sonic.net and ae0.cr4.colaca01.sonic.net are other ones that also seem to have abnormally high latency according to the outputs from the other traceroute 8.8.8.8 screenshots (like download/file.php?id=895) too.

And then quite a number of hops with just * * * - either caused by packet loss or timeouts.

The issues consistently occur within Sonic’s network, particularly at the following nodes, when aggregating across all of the traceroutes:

• ae5.cr3.colaca01.sonic.net (latency spikes: 400–1100 ms)

• ae0.cr4.colaca01.sonic.net (latency spikes: 500–900 ms)

• ae1.cr6.rcmdca11.sonic.net (latency: ~4300 ms)

I now wonder if the traceroute output from all the various setup is suggesting Sonic's infrastructure has:

• potential potential congestion, and/or

• routing inefficiency issues, and/or

• hardware issues in its network, and/or

• wiring issues upstream to the AdTrans ONT

... because the local hardware seems fine (e.g. whether connected via Ubiquity, or Eero, or directly from MacBook Pro to ONT), and the latency generally normalizes in the last hop when things reach Equinix infrastructure right before hitting Google.

[js9erfan]

I'll defer to Sonic but that could just be their routers giving low prioritization to your traceroutes. They return to normal later in the route and all reach the destination. Lots of good info here btw (specifically page 37).

I looked at a remote box on Sonic fiber and see similar results via mtr to 8.8.8.8. However, the wan connection is pretty clean as you can see from my screenshots below.

Good luck!

mtr.png (52.87 KiB) Viewed 2833 times

net.png (15.98 KiB) Viewed 2833 times

wan.png (61.73 KiB) Viewed 2833 times