Business Community > Controllers > Selfhosted Omada SDN - Remote device adoption fails using FQDN as inform Url
< Controllers

Selfhosted Omada SDN - Remote device adoption fails using FQDN as inform Url

Selfhosted Omada SDN - Remote device adoption fails using FQDN as inform Url

Selfhosted Omada SDN - Remote device adoption fails using FQDN as inform Url
Selfhosted Omada SDN - Remote device adoption fails using FQDN as inform Url
22 hours ago
Tags: #Controller #Adoption
Model: Omada Software Controller (Linux)  
Hardware Version:
Firmware Version: 6.0.0

Hi to all, i would want to share my issue with you becasuse it's driving me crazy:

i've deployed omada sdn on cloud vps with docker, all seems to work well but when i try to adopt a device using fqdn as inform url (omada.example.com), the device is never showed in "device list".
If i use ip address (xxx.xxx.xxx.xxx), device appears immediatly and adoption stage works as expected!!

 

1-Access the web interface on the device you want to remotely adopt and go to "controller settings"
2-Set the controller inform url using the ip address of the remote machine (xxx.xxx.xxx.xxx)
3-The device is immediatly ready for adoption on the controller device list
4-Set again the controller inform url using the fqdn of the remote machine (omada.example.com)
5-The device disappear from the device list after a while.

 

Anyone knows the reason f this behaviour?

  0      
 
  0      
 
#1
Options
4 Reply
Re:Selfhosted Omada SDN - Remote device adoption fails using FQDN as inform Url
21 hours ago

  @Fabiuzz 

 

no, I have used fqdn since the start of omada sdn, I have dynamic ip so that's why I have to use fqdn, no problem. The problem could be the dns server that the devices use, it could be ports in the firewall. You have to open up UDP 29810 and TCP 29811-29817 and mangement port 8043, but since you can adopt on IP the ports should be fine,

 

  1  
  1  
#2
Options
Re:Selfhosted Omada SDN - Remote device adoption fails using FQDN as inform Url
16 hours ago

  @MR.S 

As you wrote, the ports are fine.

But DNS... make me on the right way. I always use static ip setup for my nework device but I found that if i set DHCP on IP address mode in "L3 Features->Interface", fqdn adoption works!

So i'm doing something wrong when i set static ip on switch interface, but i can't find what.

Any suggestion to debug this issue?

  0  
  0  
#3
Options
Re:Selfhosted Omada SDN - Remote device adoption fails using FQDN as inform Url
14 hours ago

@Fabiuzz, the UI may not have a way to add the DNS server.  You might check the cli for your specific device to see if it can be set that way.  For new device adoption, using DHCP and option 138 with the controller's ip is very convenient.

  0  
  0  
#4
Options
Re:Selfhosted Omada SDN - Remote device adoption fails using FQDN as inform Url
8 hours ago - last edited 8 hours ago

  @Fabiuzz 

 

I set ip like this on switches

 

 

  0  
  0  
#5
Options

Information

Helpful: 0

Views: 62

Replies: 4

Tags

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