Cannot used wired backhaul on XE5300

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Cannot used wired backhaul on XE5300

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Cannot used wired backhaul on XE5300
Cannot used wired backhaul on XE5300
2022-12-08 19:19:49 - last edited 2022-12-08 19:29:30
Model: Deco XE5300  
Hardware Version: V1
Firmware Version: 1.0.0 Build 20220929 Rel 65468

I have setup a 3 node XE5300 in Access Point mode, with the main used being plugged into a Netgear JGS524E gigabit switch, which is then plugged into my external router (a Firewalla Gold).   Everything seems to work fine with the additional two deco nodes backhauled wirelessly, but I can only get a "Fair" signal for the Wifi6 backhaul with the units placed appropriately in my house.  I DO have gigabit wired ethernet in several locations and would like to use wired backhaul if at all possible.

 

Whenever I plug one of the additional two units into an ethernet connection that goes back to the same switch that the main unit is plugged into, mayhem ensues.    The deco nodes go offline (I'm assuming trying to "remesh" and when one may briefly come up, it doesn't have internet access).   I've let this sit in this state for 10 minutes, and it doesn't seem to sort itself out.   During this timeframe, a PC hardwired into another switch cannot even ping the gateway, except intermittently (perhaps once every 10-15 ping attempts).    The entire network appears to be in a loop state or similar.

 

To isolate the switch out of the issue, I connected the cable going to one of the two "remote" deco units directly into the main deco, so the "remote" deco was literally connected to the main deco via nothing but ethernet cable and a patch panel plug - no switch or anything between the remote deco and the main deco.    The same issue resulted.

 

I have updated the Netgear switch to latest firmware, and confimed loop detection is disabled on the switch.

 

I do have other switches elsewhere within the network, but they are not connected to either deco in my tests.   I have tried different ports on the remote deco units.   The ethernet cable is plugged into the "bottom" port on the main deco.   i have tried different cables.    I have confirmed that a PC plugged into the same port as the remote deco functions normally over that eithernet connection (when that remote port is plugged into the switch).

 

Any suggestions on other items to try?  It appears that in my scenario, even when directly hardwired from one deco to another, the wired backhaul does not function.

  2      
  2      
#1
Options
6 Reply
Re:Cannot used wired backhaul on XE5300
2022-12-09 03:46:44

  @dbonds 

Hi, welcome to the community.

When the remote satellite XE5300 is directly into man XE5300, is your network layout like this:

92e8bc739fff4057bdd4978ef70f60be

As for the "same issue resulted", do you mean all three XE5300s turned red and offline on the APP?

How about the laptop at this moment? still unable to ping the gateway?

If unplugging the remote wired XE5300 this time, will the rest 2*XE5300s be back to green and online?

By the way, were you able to reproduce this issue most of the time?

Is there any chance that you could temporarily bypass the Netgear switch, and connect the main XE5300 to Firewalla router directly, then check whether the same issue is repeated again?

Thank you very much.

Wait for your reply.

Best regards.

 

 

  0  
  0  
#2
Options
Re:Cannot used wired backhaul on XE5300
2022-12-09 21:34:25

  @David-TP 

 

Yes - that network diagram is accurate WHEN I was trying to do the wired backhaul option. The only clarification is that the hardwired PC (shown as laptop in your test) is is behind a second switch (opposite end of house from the main switch the deco is plugged into) - I'll refer to the switch with the hardwired PC as "switch2" - its another Netgear JGS524E (the v2 model). 

 

...to answer your questions:

 

As for the "same issue resulted", do you mean all three XE5300s turned red and offline on the APP?   yes, they would cycle from red to yellow to green then back to red (VERY slowly, but I could never get it stabilized when there was a wired backhaul connection between two of the decos.

 

How about the laptop at this moment? still unable to ping the gateway? yes, pings to gateway were only very intermittently able to get a response (ie, 1 out of every 10-15 attempts)

 

If unplugging the remote wired XE5300 this time, will the rest 2*XE5300s be back to green and online?   Once the wired backhaul connection was removed, all three decos (and the remaining wired network) would return back to normal state within 5-10 seconds. 

 

By the way, were you able to reproduce this issue most of the time?   I could repro this 100% of the time

 

...and for the next troubleshooting step:

 

As a reference (for any speedtests below) - my main internet connection is gigabit fiber, with a secondary cable modem connection (setup as failover in firewalla).

  • A wired speedtest normally gets 600-900mbit/sec downstream.
  • A wireless speedtest from a phone standing feet from main deco results in similar speeds.
  • A wireless speedtest from deco3 normally gets ~90-100mbit (it's going from the deco3 to deco2 with a "fair connection" over wifi6E backhaul, then again from deco2 to main deco over wifi6E backhaul)

 

 

I WAS able to move the main deco over to a second lan port directly on the firewalla gold - took about 10 seconds for wifi (via decos) to regain connectivity, but then everything appeared to be operating normally.  I did a few pings across the network and a speedtest from a phone on the "most distant" deco (2 deco units away from the main deco), with "ok" results with about 90mbit downstream.

 

With the environment in this state (main deco wired directly into firewalla gold, +2 decos wireless backhaul) I started a constant ping from a wired PC (on switch2) to both the firewalla gold and to the main deco.    Ping times to both of these were a constant 1ms in this state.

 

I tried adding a wired backhaul connection to that "most distant" deco (deco3) - going only thru an ethernet patch panel to a cable directly connected to the main deco.    As soon as I added the wired connection, there was a brief (3-5 second) interruption in networking - pings to both the firewalla and main deco failed during that time.   However, they did resume after 5 seconds -- oddly pings to the gateway were in the 4-8ms range and pings to the main deco were in the 4-25ms range.   The deco app on my phone still showed the deco3 with a wireless connection to deco2 with a "Fair" signal - which seemed odd as I thought it might show a different status once it was using wired backhaul (which I assumed it was at this point).   Does the deco app on phone show some type of indicator for a deco using wired backhaul?   

 

The increase in latency/ping times seemed odd, but the network seemed stable and working (which was better than my prior attempt at wired backhaul).

 

At this point, I tried a quick test - running a speedtest from a phone connected to deco3 resulted in similar speeds as before (~90mbit) - which makes me think deco3 was NOT using wired backhaul at that point.   Of greater concern --- while the speedtest was running, pings (again, from wired PC) to both the main deco and to the firewalla increased to  >100ms, with some pings to deco main being dropped entirely.      I did this twice and there was a definite correlation between the speedtest running and high ping times and packet loss on what should be the wired network (PC to firewalla).

 

These results baffled me as (based on what I saw with the latency of the pings) they lead me to believe that somehow traffic that should remain on wired network (the pings from the wired PC) are somehow being forced over the wireless (deco) network, but only while the wired backhaul connection is in place.    I think there is still some type of a network loop in place.

 

When I removed the "wired backhaul" connection from deco3, the same pings went nonresponsive for about 10-12 seconds, but then the network came back with <1ms pings to both devices.      Running the same speedtest (from phone connected to deco3) had no impact on ping times (still 1ms throughout speedtest).

 

I have two other troubleshooting steps I'll try next time I have ability to test (ie, when the rest of my family isn't home) :

 

1. Replacing the "main switch" being used (the Netgear JGS524E) with a Cisco SG-200-18 switch I have elsewhere in my network.       

2. Moving the 3 node deco infrastructure over to a different cable modem/router - this will eliminate ALL switches and the firewalla gold from the environment with the deco.

 

 

  0  
  0  
#3
Options
Re:Cannot used wired backhaul on XE5300
2022-12-12 21:05:54

  @dbonds 

 

I also purchased the XE5300 3 pack and I have a similar network config with a Goole Fiber Jack > Ubiquiti EdgeMax Router > Netgear JGS516PE > XE5300 Main (AP Mode).  

 

I could not get the nodes to detect the ethernet backhaul if there was a switch between any of the nodes. 

 

They would only use the ethernet backhaul if they were directly connected to each other.

  0  
  0  
#4
Options
Re:Cannot used wired backhaul on XE5300
2022-12-12 22:35:22

  @emo65170 Thanks for the input - my first attempt was via the netgear switch.  My attempt last Friday was with one of the remote decos connected back to the main deco via a direct cable with no switch, and still failed.   I'm going to try and isolate the main deco OFF the existing netgear switch on to a TP-Link TL-SG108 unmanaged switch and see if that helps before trying the other two steps I put in my last post.

 

 

  0  
  0  
#5
Options
Re:Cannot used wired backhaul on XE5300
2022-12-13 00:26:36
Update: I tried again connecting all of the Deco nodes directly to the Netgear switch and the ethernet backhaul is now working as expected. I can even see in the Netgear Port Status screeen that the ports that the Decos are attached to are in Up status and link speed correctly listed as 1000M. SpeedTest is testing 380/484 with 4-8ms ping. So it appears to be working as expected. Since we have similar equipment, Netgear, TPLink, etc. If you want to compare settings to help troubleshoot, I'd be happy to do that. Regarding your question about whether the phone app shows an icon for ethernet back haul, yes, it does. It looks like a blue cable in the shape of a "2" with terminated ends. Good luck!
  0  
  0  
#6
Options
Re:Cannot used wired backhaul on XE5300
2022-12-13 00:42:14
One more thing to try on your side. On the Port Statistics page on the Netgear Management page, System > Monitoring > Port Statistics, check if there are any CRC error packets reported; may indicate a bad connection or port starting to go bad.
  0  
  0  
#7
Options