Business CommunityControllersTCP connection to the Controller on port 29817
Controllers

TCP connection to the Controller on port 29817

TCP connection to the Controller on port 29817

TCP connection to the Controller on port 29817
TCP connection to the Controller on port 29817
Tuesday - last edited Saturday
Tags: #Controller #Firmware Update #Adoption
Model: Omada Cloud Essentials  
Hardware Version: V6
Firmware Version: 6.2.0.100

 

Can anyone help me? I'm having this problem at one of my sites. I'm using Omada Essential Cloud. I have six EAP603 Outdoor devices with firmware version 1.5.51.

 

"monitor link down due to failure of TCP connection to the Controller on port 29817"

 

0
0
#1
1 Accepted Solution
Re:TCP connection to the Controller on port 29817-Solution
Friday - last edited Saturday

Hi,  @ludbarri 

Thank you for posting on our business forum.

A new device data collection and reporting mechanism has been introduced in Controller V6. To ensure proper communication between your devices and the controller, you will need to open TCP port 29817. If you have multiple devices that need to communicate with the controller, you will need to configure multiple corresponding access rules accordingly.

For detailed configuration instructions, you can refer to the port forwarding configuration guide for Archer routers: TP-Link Port Forwarding Setup Guide | Open Ports on Your Router

If you still experience the same log issue after opening the required port, we suggest you check whether the port forwarding rule is correctly set up, or verify if your firewall settings are blocking communication over this port.

 

Recommended Solution
0
0
#7
6 Reply
Re:TCP connection to the Controller on port 29817
Tuesday - last edited Tuesday

  @ludbarri  I have 5 Omada Essential controllers, with a total of 90 sites, I only have this problem on one "SITE". My ISP is Starlink, I'm using a Starlink V4 and a Tplink Archer AX12 Gigabit Router.

 

0
0
#2
Re:TCP connection to the Controller on port 29817
Tuesday

Hi @ludbarri 

Thanks for reaching out to TP-Link Business Forums.

 

This is a new mechanism introduced to V6 Controller. Which ports do Omada SDN Controller and Omada Discovery Utility use? (above Controller 5.0.15) | Omada Network Support

Since you are using a third party gateway, you need to open the port on that router.

0
0
#3
Re:TCP connection to the Controller on port 29817
Tuesday

  @Gabriel-TP 

Can you tell me if this is the correct configuration?

0
0
#4
Re:TCP connection to the Controller on port 29817
Tuesday

Hi @ludbarri 

 

What's the device owing IP 192.168.0.100?

As you said you have been using Starlink & Archer router, can you specify the network topology and their own IP ranges?

0
0
#5
Re:TCP connection to the Controller on port 29817
Thursday

  @Gabriel-TP 

I also get this every now and then although the ports are open, some days it works, some days I get these entries in the site's log.

0
0
#6
Re:TCP connection to the Controller on port 29817-Solution
Friday - last edited Saturday

Hi,  @ludbarri 

Thank you for posting on our business forum.

A new device data collection and reporting mechanism has been introduced in Controller V6. To ensure proper communication between your devices and the controller, you will need to open TCP port 29817. If you have multiple devices that need to communicate with the controller, you will need to configure multiple corresponding access rules accordingly.

For detailed configuration instructions, you can refer to the port forwarding configuration guide for Archer routers: TP-Link Port Forwarding Setup Guide | Open Ports on Your Router

If you still experience the same log issue after opening the required port, we suggest you check whether the port forwarding rule is correctly set up, or verify if your firewall settings are blocking communication over this port.

 

Recommended Solution
0
0
#7

Information

Helpful: 0

Views: 175

Replies: 6

Tags

Controller Firmware Update Adoption
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.