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

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

19 Reply
Re:Selfhosted Omada SDN - Remote device adoption fails using FQDN as inform Url
17 hours ago

  @MR.S 

 

Ok I dont have a SG3428x and not use stand alone, I se if I can find a emulator ..

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

  @Fabiuzz 

Goto system and DNS

 

 

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

  @MR.S 

Emulator starts from version  V1.30 and there was an option to set dns, not for v.1.0

But i have the same behaviour with SG2210P v.5.20, inform ip ok, fqdn not. And i'm unable to set dns manually.

 

sg3428x

 

 

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

  @Fabiuzz 

 

ok, then I can't help you, I see the firmware is very old too, but it's the latest for that switch. but it's strange if you can't set dns on the switch, I refuse to believe that. but Vincent probably has the answer to that. but I found an emulator for SG2210p but I didn't find DNS settings there either.

try with SSH and take the command from the switch conole.

 

type when you are loged in

enable
ip dns-address primary 1.1.1.1 secondary 1.0.0.1

 

 

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

  @Fabiuzz 

 

If you haven't used SSH before, there is a good tool for that, search for putty. It is self-explanatory when you start the program.

 

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

@Fabiuzz, did you try option 138? You just need to set and maintain the controller's IP in one place and any Omada device using DHCP (factory default is enabled) should announce itself to the controller. You don't even need to log into the device to set anything out of the box to adopt it. Once adopted you can set static IP, DNS, etc.

 

This solution doesn't work by using fqdn, but I think it accomplishes what you want unless I missed a requirement.

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

Hi  @Fabiuzz 

 

You don’t need to look for how to configure the DNS server in the standalone interface—even if the configuration succeeds, the controller will overwrite and clear it once the device is adopted.

We recommend first managing the switch, then configuring the DNS server in the controller interface. Below is the page:

 

BTW, to configure the DNS server for switches under the standalone interface, you need to enable the DHCP server for the switch first.

 

 

 

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

  @Vincent-TP 

I don't really need to set dns except because the adoption fails with fqdn and the switch is set with static ip.

As you can read in my first post, my controller is hosted on cloud vps with docker, so if i can't adopt my switches with fqdn i can't really start to manage my sites (3 at now); my concern is that I have to reconfigure all the devices in the sites if I change the controller's ip address.

BUT, if i can adopt the switches using controller ip in inform url and then change it (inform url) with fqdn in the controller, then this could be a solution!

 

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

  @Fabiuzz 

 

you can do it in global settings, but I doubt if your switch supports device management with so old firmware, device management is similar to inform address.

 

 

 

 

Fabiuzz wrote

  @Vincent-TP 

I don't really need to set dns except because the adoption fails with fqdn and the switch set with static ip.

As you can read in my first post, my controller is hosted on cloud vps with docker, so if i can't adopt my switches with fqdn i can't really start to manage my sites (3 at now); my concern is that I have to reconfigure all the devices in the sites if I change the controller's ip address.

BUT, if i can adopt using ip in inform url and then change it (inform url) with fqdn in the controller, then this could be a solution!

 

 

  0  
  0  
#20
Options