Home Network Community > Deco > Frequent Disconnections in Network Using Deco X95 in AP Mode
< Deco

Frequent Disconnections in Network Using Deco X95 in AP Mode

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

Frequent Disconnections in Network Using Deco X95 in AP Mode

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Frequent Disconnections in Network Using Deco X95 in AP Mode
Frequent Disconnections in Network Using Deco X95 in AP Mode
2024-05-09 07:26:34
Tags: #Access Point Mode #Network Connectivity
Model: Deco X95  
Hardware Version:
Firmware Version: 1.2.4 Build 20231227 Rel. 63632

Operating the main Deco X95 in AP mode, connected via wired LAN under the router, in a network with 9 other Deco units, the main Deco disconnects from the network about once or twice every few days. When this happens, a red light is displayed. After a few minutes, the light turns green, and the network connection is restored.

 

Logs：

Thu May  9 13:59:53 2024 daemon.err mcsd: ENTER mcManagerMCReadBufCB
Thu May  9 13:59:53 2024 daemon.err mcsd: Get netlink MSG 100 size 52 from br-lan

Thu May  9 13:59:53 2024 daemon.err mcsd: mcManagerMCReadBufCB: Receive mdb updated event from br-lan 

Thu May  9 13:59:53 2024 daemon.err mcsd: ENTER mcManagerMCReadBufCB
Thu May  9 13:59:53 2024 daemon.err mcsd: ENTER mcManagerMCReadBufCB
Thu May  9 13:59:53 2024 daemon.err mcsd: Get netlink MSG 17 size 6708 from br-lan

Thu May  9 13:59:53 2024 daemon.err mcsd: mcManagerMCProcess: Legacy node 0 - F4:39:09:1B:A9:FB, add it to flood table
Thu May  9 13:59:53 2024 daemon.err mcsd: mcManagerMCProcess: Legacy node 0, update forwarding table
Thu May  9 13:59:53 2024 daemon.err mcsd: mcManagerMCProcess: Legacy node 1 - E4:54:E8:DA:90:FF, add it to flood table
Thu May  9 13:59:53 2024 daemon.err mcsd: mcManagerMCProcess: Legacy node 1, update forwarding table
Thu May  9 13:59:53 2024 daemon.err mcsd: mcManagerMCProcess: Legacy node 2 - B0:22:7A:23:93:EC, add it to flood table
Thu May  9 13:59:53 2024 daemon.err mcsd: mcManagerMCProcess: Legacy node 2, update forwarding table
Thu May  9 13:59:53 2024 daemon.err mcsd: mcManagerMCProcess: Legacy node 3 - 20:C1:9B:03:F2:D2, add it to flood table
Thu May  9 13:59:53 2024 daemon.err mcsd: mcManagerMCProcess: Legacy node 3, update forwarding table
Thu May  9 13:59:53 2024 daemon.err mcsd: mcManagerMCProcess: Legacy node 4 - B0:7D:64:5E:91:33, add it to flood table
Thu May  9 13:59:53 2024 daemon.err mcsd: mcManagerMCProcess: Legacy node 4, update forwarding table
Thu May  9 13:59:53 2024 daemon.err mcsd: mcManagerMCProcess: Interface eth2's forwarding table is changed
Thu May  9 13:59:53 2024 daemon.err mcsd: mcManagerMCProcess: Updated interface eth2 forwarding table successfully
Thu May  9 13:59:53 2024 daemon.err mcsd: ENTER mcManagerMCReadBufCB
Thu May  9 13:59:54 2024 daemon.err nrd[19095]: bcm_get_fdb_dst failed
Thu May  9 13:59:54 2024 daemon.err nrd[19095]: bcm_get_fdb_dst failed
Thu May  9 13:59:58 2024 daemon.err nrd[19095]: triggerMonSteering: Failed to get uplink rssi for 52:67:D3:0E:2F:0E
Thu May  9 13:59:58 2024 daemon.err nrd[19095]: triggerMonSteering: Failed to get uplink rssi for 9E:5D:82:9D:48:66
Thu May  9 14:00:06 2024 daemon.err client_mgmt: can not parse json_obj
Thu May  9 14:00:06 2024 daemon.err client_mgmt: update_history_wire_type:exit failed.
Thu May  9 14:00:06 2024 daemon.err client_mgmt: update /tmp/client_mgmt/history_wire_type failed, offline client type recognization of link priority will be influenced.
Thu May  9 14:00:10 2024 daemon.err nrd[19095]: _bcm_wlanifBSteerEventsHandleRRMReportInd: 11k handle regclass=128 channel=36, channelId=(36)24
Thu May  9 14:00:10 2024 daemon.err nrd[19095]: _bcm_wlanifBSteerEventsHandleRRMReportInd: 11k handle regclass=129 channel=36, channelId=(36)24
Thu May  9 14:00:10 2024 daemon.err nrd[19095]: _bcm_wlanifBSteerEventsHandleRRMReportInd: 11k handle regclass=129 channel=36, channelId=(36)24
Thu May  9 14:00:10 2024 daemon.err nrd[19095]: _bcm_wlanifBSteerEventsHandleRRMReportInd: 11k handle regclass=129 channel=36, channelId=(36)24
Thu May  9 14:00:10 2024 daemon.err nrd[19095]: _bcm_wlanifBSteerEventsHandleRRMReportInd: Beacon report too much
Thu May  9 14:00:10 2024 daemon.err nrd[19095]: steeralgFindBestAPCallback: iterate BSS APId 9   ChanId 2   ESSId 0   targetBand(0) != measuredBss->band(1)
Thu May  9 14:00:11 2024 user.err smartip: [lan] !!ip addr del!! ip addr del 192.168.0.81 dev br-lan
Thu May  9 14:00:11 2024 daemon.err udhcpc[9160]: Received SIGTERM
Thu May  9 14:00:12 2024 daemon.err udhcpc[23820]: udhcpc (v1.22.1) started
Thu May  9 14:00:12 2024 daemon.err udhcpc[23820]: Sending discover...
Thu May  9 14:00:12 2024 daemon.err udhcpc[23820]: Sending select for 192.168.0.81...
Thu May  9 14:00:13 2024 user.emerg logx: tp217,505[23909]:
Thu May  9 14:00:14 2024 daemon.err nrd[19095]: bcm_get_fdb_dst failed
Thu May  9 14:00:14 2024 daemon.err nrd[19095]: bcm_get_fdb_dst failed
Thu May  9 14:00:16 2024 daemon.err nrd[19095]: triggerMonSteering: Failed to get uplink rssi for 52:67:D3:0E:2F:0E
Thu May  9 14:00:24 2024 daemon.err client_mgmt: can not parse json_obj
Thu May  9 14:00:24 2024 daemon.err client_mgmt: update_history_wire_type:exit failed.
Thu May  9 14:00:24 2024 daemon.err client_mgmt: update /tmp/client_mgmt/history_wire_type failed, offline client type recognization of link priority will be influenced.
Thu May  9 14:00:39 2024 daemon.err nrd[19095]: _bcm_wlanifBSteerEventsHandleRRMReportInd: error mode: 4
Thu May  9 14:00:39 2024 daemon.err nrd[19095]: estimatorCmnHandleBeaconReportEvent: Invalid beacon report for 52:67:D3:0E:2F:0E
Thu May  9 14:00:42 2024 daemon.err client_mgmt: can not parse json_obj
Thu May  9 14:00:42 2024 daemon.err client_mgmt: update_history_wire_type:exit failed.
Thu May  9 14:00:42 2024 daemon.err client_mgmt: update /tmp/client_mgmt/history_wire_type failed, offline client type recognization of link priority will be influenced.
Thu May  9 14:00:45 2024 daemon.err nrd[19095]: triggerMonSteering: Failed to get uplink rssi for 52:67:D3:0E:2F:0E
Thu May  9 14:00:45 2024 daemon.err mcsd: ENTER mcManagerMCReadBufCB
Thu May  9 14:00:45 2024 daemon.err mcsd: Get netlink MSG 100 size 52 from br-lan

 

I suspect there might be an issue with the log at 14:00:11.

  0      
 
  0      
 
#1
Options
4 Reply
Re:Frequent Disconnections in Network Using Deco X95 in AP Mode
2024-05-10 06:14:37

  @ten2 

Hi, welcome to the community.

Can I have a picture or diagram of how the 9 Deco units are connected to the Mesh system?

Would there be a network switch in the network?

 

When the main Deco X95 turned red, did you still get an internet connection from the ISP router？

If possible, since all Decos work quite the same in AP mode, it is also suggested to refer to this link to switch to another Deco as the main Deco:

How to replace the main Deco with another Deco

 

Thank you very much and best regards.

 

▶Check What's Currently Going on With Deco ▶Deco Starts Supporting Changing Wireless Channels! ▶KidShield Now Open for Trial! Try to leave a Message if urgent help is required.
  0  
  0  
#2
Options
Re:Frequent Disconnections in Network Using Deco X95 in AP Mode
2024-05-10 07:11:55

  @David-TP 

Hi!!

 

Hello,

I will attach a schematic diagram. When the main Deco X95 light turns red, all of "Zone B" loses network connectivity. However, "Zone A", which branches from the main Deco to the upper L2SW, remains connected to the network normally.

 

I would like to try switching the main Deco as well. Since all Decos are connected via Ethernet backhaul, is it acceptable to switch the main Deco with another Deco?

File:
deco_nw.pngDownload
  1  
  1  
#3
Options
Re:Frequent Disconnections in Network Using Deco X95 in AP Mode
2024-05-10 08:18:37

  @ten2 

Hi, Thanks for the update.

It is ok to switch the main Deco with another Deco X95. 

(After switching the main Deco, you might need to manually bring the original "satellite Deco X95" to where the main Deco X95 used to be.)

The initial reason to switch the Deco is to rule out the possibility of a broken hardware.

 

However, after viewing the topology, I think the disconnection is more likely caused by the internal network loop.

May I know the model number of your L2 switches? Are all the L2SW here the same models?

Have you noticed any loop detection alerts on the switch when the main Deco X95 turned red?

 

Previously you mentioned there are 9 Decos in the Mesh system, are the rest 5* Decos using Wireless Backhaul?

 

Thank you very much and Wait for your reply

▶Check What's Currently Going on With Deco ▶Deco Starts Supporting Changing Wireless Channels! ▶KidShield Now Open for Trial! Try to leave a Message if urgent help is required.
  0  
  0  
#4
Options
Re:Frequent Disconnections in Network Using Deco X95 in AP Mode
2024-05-11 12:19:00

  @David-TP 

Hi,

 

I will look for an opportunity to switch the main Deco and test it.

 

However, after viewing the topology, I think the disconnection is more likely caused by the internal network loop.

Wow, that’s a very interesting perspective. I had some suspicions about a network loop, but it didn't seem likely from the topology. Could you please explain how you derived the possibility of a network loop from the topology?

 

Regarding the L2 switches, we are using multiple models, including "YAMAHA SWX2200" and "TP-Link TLSG105". However, I didn’t notice any loop detection alerts on the switches when the main Deco X95 turned red.

 

Also, the remaining 5 Decos are using wired LAN for backhaul.

 

Please let me know if you notice anything else.

  0  
  0  
#5
Options

Information

Helpful: 0

Views: 448

Replies: 4

Tags

Access Point Mode Network Connectivity
Related Articles
 Deco X95 Frequent drop-offs
261 0
Having issues setting up my Deco x95
645 0
 Add printer to Deco X95
583 0
 X95 Deco connectivity
315 0
 Difference between Deco X95 V1.60 and Deco X95 V1.0
440 0
 Deco X90 and X95 Ethernet Backhaul
1877 1
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.