Ethernet BackHaul Working Topology

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

Ethernet BackHaul Working Topology

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Ethernet BackHaul Working Topology
Ethernet BackHaul Working Topology
2024-02-24 17:25:18 - last edited 2024-02-24 17:27:53
Model: Deco XE75  
Hardware Version: V2
Firmware Version: 1.2.5 Build 20231225 Rel, 58766

Here is a topology diagram of my working envornment using Ethernet backhaul.

It has been in production for 2 days - so far so good.

The only thing I notice is that the satelite Deco's will intermittantly appear as offline in the app.

There are roughly 50 client devices connected with a mix of 2.4, 5 Ghz and wired.

 

52bfadaa5a8845048c77ab2cc7af1d84

File:
Screenshot 2024-02-24 at 12.07.17 PM.pngDownload
  0      
  0      
#1
Options
7 Reply
Re:Ethernet BackHaul Working Topology
2024-02-26 06:54:38

  @SDWAN-MAN

Hi, would any Deco turn flashing red when Deco APP reported "Offline"?

And could mobile devices still get internet connection when they are connected to the "Offline" Deco?

If the LED is solid green and the internet works fine, it is suggested to install the beta firmware here:

Optimize The Overall App Experience on Deco XE5300/XE75/XE75 Pro

Wait for your reply and best regards.

  0  
  0  
#2
Options
Re:Ethernet BackHaul Working Topology
2024-03-01 05:12:37

  @David-TP I have not noticed but a handful of times so I do not know what the LED color is when it happens.

If I see it again I will make sure I do some trouble-shooting.

Thank you for the beta code link.

I will use it if I need to.

  0  
  0  
#3
Options
Re:Ethernet BackHaul Working Topology
2024-03-03 06:00:55

  @David-TP I have a Thousand Eyes test running over the wireless NIC on a laptop that I have preferring one of the satellite Deco's.
Going to let it run for a couple of weeks to prove out if the issue is with the Deco mesh or if the app showing the satellites offline is just a cosmetic bug in the app

  1  
  1  
#4
Options
Re:Ethernet BackHaul Working Topology
2024-03-05 11:02:55

  @SDWAN-MAN did u disable wireless backhaul?  (there is an option for it) 

My setup is same as yours, am using 2.5Gb ethernet switch that all decos plugfed into, then that's uplinked to att fiber 5Gb wan port.... All one flat vlan/subnet 

I had problems when I had not turned off wireless backhaul 

 

  0  
  0  
#5
Options
Re:Ethernet BackHaul Working Topology
2024-04-12 16:14:03

  @imrj I cannot find where to turn wireless backhaul off.

  0  
  0  
#6
Options
Re:Ethernet BackHaul Working Topology
2024-04-12 16:28:09

  @SDWAN-MAN The plot thickens.  On the switch I notice STP events around the ports where the Deco's are connected.
I suspect that the deco's are causing bridging loops and STP is intermittantly blocking the ports.

In some intances the switch hears the mac of a hadrwaire client with no wireless access flapping between a Deo uplink port and a hardwired client port.

This is really odd behavior,

I have also noticed the MAC addresses of the Deco's are flapping between Deco ports on the switch.

I have put mac address ACL's on the switchport facing the Decos that explicitly deny that port from learning deco MACs not specifically connected and permitting all others.

This appears to have settled my network but it would be really cool if I could disable wireless backhaul manully since I am using a switch.

  0  
  0  
#7
Options
Re:Ethernet BackHaul Working Topology
2024-04-22 02:57:19

  @SDWAN-MAN 

 

I see my satellite Decos intermittently appearing offline in the app.
Connectivity to the world is lost during this time.

I see these messages in the Deco log:
 

Sun Apr 21 22:02:41 2024 user.emerg : tp229,505[26806]:

Sun Apr 21 22:02:43 2024 user.emerg : tp229,502[26806]:

Sun Apr 21 22:02:43 2024 user.emerg : tp229,504[26806]:

Sun Apr 21 22:32:59 2024 kern.emerg the module failed

Sun Apr 21 22:33:04 2024 user.emerg : tp229,503[11062]:

Sun Apr 21 22:33:04 2024 user.emerg : tp229,505[11062]:

Sun Apr 21 22:33:06 2024 user.emerg : tp259,505[10891]:

Sun Apr 21 22:33:06 2024 user.emerg : tp229,502[11062]:

Sun Apr 21 22:33:06 2024 user.emerg : tp229,504[11062]:

Sun Apr 21 22:33:06 2024 user.emerg : tp259,502[11577]:

Sun Apr 21 22:33:07 2024 user.emerg : tp230,505[11718]:

Sun Apr 21 22:33:07 2024 user.emerg : tp230,503[11718]:

Sun Apr 21 22:33:07 2024 user.emerg : tp230,504[11718]:

Sun Apr 21 22:33:07 2024 user.emerg : tp259,504[11577]:

Sun Apr 21 22:33:08 2024 kern.emerg the module failed

Sun Apr 21 22:33:10 2024 kern.emerg the module failed

Sun Apr 21 22:33:17 2024 user.emerg : tp259,505[12052]:

Sun Apr 21 22:33:18 2024 user.emerg : tp259,502[12597]:

Sun Apr 21 22:33:19 2024 user.emerg : tp259,504[12597]:

Sun Apr 21 22:33:20 2024 kern.emerg the module failed

Sun Apr 21 22:33:42 2024 kern.emerg the module failed

Sun Apr 21 22:33:49 2024 user.emerg : tp259,505[13919]:

Sun Apr 21 22:33:50 2024 user.emerg : tp259,502[14673]:

Sun Apr 21 22:33:52 2024 user.emerg : tp229,503[14423]:

Sun Apr 21 22:33:52 2024 user.emerg : tp229,505[14423]:

Sun Apr 21 22:33:53 2024 user.emerg : tp259,504[14673]:

Sun Apr 21 22:33:54 2024 kern.emerg the module failed

Sun Apr 21 22:33:56 2024 user.emerg : tp229,502[14423]:

Sun Apr 21 22:33:56 2024 user.emerg : tp229,504[14423]:

Sun Apr 21 22:33:59 2024 user.emerg : tp230,505[15678]:

Sun Apr 21 22:33:59 2024 user.emerg : tp230,503[15678]:

Sun Apr 21 22:33:59 2024 user.emerg : tp230,504[15678]:

Sun Apr 21 22:34:08 2024 kern.emerg the module failed

Sun Apr 21 22:34:14 2024 user.emerg : tp259,505[16361]:

Sun Apr 21 22:34:15 2024 user.emerg : tp259,502[17216]:

Sun Apr 21 22:34:15 2024 user.emerg : tp229,503[16875]:

Sun Apr 21 22:34:15 2024 user.emerg : tp229,505[16875]:

Sun Apr 21 22:34:16 2024 user.emerg : tp259,504[17216]:

Sun Apr 21 22:34:16 2024 kern.emerg the module failed

Sun Apr 21 22:34:18 2024 user.emerg : tp229,502[16875]:

Sun Apr 21 22:34:18 2024 user.emerg : tp229,504[16875]:

Sun Apr 21 22:34:19 2024 user.emerg : tp230,505[17778]:

Sun Apr 21 22:34:19 2024 user.emerg : tp230,503[17778]:

Sun Apr 21 22:34:19 2024 user.emerg : tp230,504[17778]:

Sun Apr 21 22:35:22 2024 kern.emerg the module failed

Sun Apr 21 22:35:31 2024 user.emerg : tp259,505[20756]:

Sun Apr 21 22:35:31 2024 user.emerg : tp229,503[21138]:

Sun Apr 21 22:35:31 2024 user.emerg : tp229,505[21138]:

Sun Apr 21 22:35:32 2024 user.emerg : tp259,502[21685]:

Sun Apr 21 22:35:34 2024 user.emerg : tp259,504[21685]:

Sun Apr 21 22:35:35 2024 user.emerg : tp229,502[21138]:

Sun Apr 21 22:35:35 2024 user.emerg : tp229,504[21138]:

Sun Apr 21 22:35:36 2024 kern.emerg the module failed

Sun Apr 21 22:35:39 2024 user.emerg : tp230,505[22498]:

Sun Apr 21 22:35:39 2024 user.emerg : tp230,503[22498]:

Sun Apr 21 22:35:39 2024 user.emerg : tp230,504[22498]:

Sun Apr 21 22:35:45 2024 kern.emerg the module failed

Sun Apr 21 22:35:52 2024 user.emerg : tp259,505[23176]:

Sun Apr 21 22:35:53 2024 user.emerg : tp259,502[23769]:

Sun Apr 21 22:35:54 2024 user.emerg : tp229,503[23525]:

Sun Apr 21 22:35:54 2024 user.emerg : tp229,505[23525]:

Sun Apr 21 22:35:56 2024 user.emerg : tp259,504[23769]:

Sun Apr 21 22:35:59 2024 kern.emerg the module failed

Sun Apr 21 22:36:01 2024 user.emerg : tp229,502[23525]:

Sun Apr 21 22:36:01 2024 user.emerg : tp229,504[23525]:

Sun Apr 21 22:36:05 2024 user.emerg : tp230,505[24882]:

Sun Apr 21 22:36:05 2024 user.emerg : tp230,503[24882]:

Sun Apr 21 22:36:05 2024 user.emerg : tp230,504[24882]:

Sun Apr 21 22:37:25 2024 kern.emerg the module failed

Sun Apr 21 22:37:31 2024 user.emerg : tp229,503[28557]:

Sun Apr 21 22:37:31 2024 user.emerg : tp229,505[28557]:

Sun Apr 21 22:37:34 2024 user.emerg : tp259,505[28518]:

Sun Apr 21 22:37:36 2024 user.emerg : tp259,502[29645]:

Sun Apr 21 22:37:40 2024 user.emerg : tp229,502[28557]:

Sun Apr 21 22:37:40 2024 user.emerg : tp229,504[28557]:

Sun Apr 21 22:37:41 2024 user.emerg : tp259,504[29645]:

Sun Apr 21 22:37:42 2024 kern.emerg the module failed

Sun Apr 21 22:37:42 2024 user.emerg : tp230,505[30334]:

Sun Apr 21 22:37:42 2024 user.emerg : tp230,503[30334]:

Sun Apr 21 22:37:42 2024 user.emerg : tp230,504[30334]:

Sun Apr 21 22:37:45 2024 kern.emerg the module failed

Sun Apr 21 22:37:52 2024 user.emerg : tp259,505[30511]:

Sun Apr 21 22:37:53 2024 user.emerg : tp259,502[31029]:

Sun Apr 21 22:37:55 2024 user.emerg : tp259,504[31029]:

Sun Apr 21 22:37:56 2024 kern.emerg the module failed

Sun Apr 21 22:38:08 2024 kern.emerg the module failed

Sun Apr 21 22:38:14 2024 user.emerg : tp229,503[32429]:

Sun Apr 21 22:38:14 2024 user.emerg : tp229,505[32429]:

Sun Apr 21 22:38:15 2024 user.emerg : tp259,505[32148]:

Sun Apr 21 22:38:16 2024 user.emerg : tp259,502[469]:

Sun Apr 21 22:38:17 2024 user.emerg : tp259,504[469]:

Sun Apr 21 22:38:18 2024 user.emerg : tp229,502[32429]:

Sun Apr 21 22:38:18 2024 user.emerg : tp229,504[32429]:

Sun Apr 21 22:38:18 2024 kern.emerg the module failed

Sun Apr 21 22:38:19 2024 user.emerg : tp230,505[980]:

Sun Apr 21 22:38:19 2024 user.emerg : tp230,503[980]:

Sun Apr 21 22:38:19 2024 user.emerg : tp230,504[980]:

Sun Apr 21 22:38:45 2024 kern.emerg the module failed

Sun Apr 21 22:38:52 2024 user.emerg : tp229,503[2850]:

Sun Apr 21 22:38:52 2024 user.emerg : tp229,505[2850]:

  0  
  0  
#8
Options

Information

Helpful: 0

Views: 896

Replies: 7

Related Articles