Hi @OliversQuestion 

Thanks for posting in our business forum.

Is it in the same network? I think your management VLAN is the reason why.

Hi @OliversQuestion 

Thanks for posting in our business forum.

OliversQuestion wrote

  @Clive_A 

 

Hello Clive

 

Thank you very much for your answer and support. Here are some pictures of my configurations.

 

The first picture shows the IP setting of my switch, which I have set up as a management interface. I have set up a VLAN20 for this.

 

 

 

 

 

 

The computer with the Omada controller software is connected to port 10, which is configured as untagged. The AccessPoint on port 7 which is configured as tagged. This are in VLAN20.

 

 

 

 

I have entered the IP of the controller in the controller settings

 

 

 

In order for the switch to communicate with the Internet, I have set up a static route and a corresponding firewall rule on my firewall

 

 

 

 

 

I can ping the switch from the Omada controller PC and access it via web gui 

 

 

 

 

 

The settings for the wired network in the Omada Controller

 

 

 

Unfortunately, only the access point is displayed

 

 

 

Configuration IP and  Management-VLAN AccessPoint

 

 

 

 

 

I don't know what I'm doing wrong. thank you very much for your help.

Greetings

Oliver

 

You don't have to mosaic the private IP address. That poses no danger to your privacy or network security.

Here's the thing, if you are gonna adopt the switch, you will lose the settings you have now. This means even if I get this switch displayed up there, you will lose control again and will lose the AP as well.

(1. I don't think you should put the inform URL. That's unnecessary in LAN setup. 2. Discovery is sent by broadcast in this VLAN interface X.Y.32.1, I think something is blocking it. 3. If the switch is not in management while AP and controller are and they can find each other, of course, you don't find the switch because it is not included in the management VLAN.)

I would recommend you start over and get them to the default VLAN, no management VLAN yet, after they are adopted, get them to the management VLAN.

There's a guide, and search management VLAN on the official website. It would be the controller one.