Hi @Armin_,

Are you are looking at the Devices in the Global View?

  @D-C 

Looking at both global and local view (I called it Home). No sucess. I really may mis something essential here . . .

  @Armin_ 

You need to setup a VLAN 10 on all switches, untagged on all ports, assign them an iswitch nterface with admin enabled,and set that as the management vlan - all in standalone mode

  @Vincent-TP 

Hello,

unfortunately no success. So, my next test was: resetting all devices and connect a single switch, the SG2008P, with a separate network cable to a free port on the netgate 6100. I assigned the 192.168.0.0/24 network. And I connected the OC200 to a free port of the SG2008P. It worked. I could adopt the switch. 

Next, I reset the main switch SG2218 and connected the SG2008P to any port of the SG2218. I could adopt SG2218 and see both switches.

Then I set up VLANs and a LAG connection between SG2218 and SG2008P. I assigned VLANS and then all connections were gone. 

So, It basically works  but my setup is obviously wrong. 

I want to achieve something rather simple which all works fine in standalone mode.

All devices like switches and APs shall be in VLAN 10. All uplinks and downlinks between switches are a 2 port LAGs.

If I setup in standalone mode, then all switches are in VLAN 10 and receive an IP via DHCP. Also the OC200. I can communicate with all devices. All devices can ping each other. But OC200, does not detect them.

I am at a loss here. Next steps will be to rest switches again and start all over. I am also running out of ideas now and I am meanwhile disappointed.

Armin

@Armin_, at this step ..

Then I set up VLANs and a LAG connection between SG2218 and SG2008P. I assigned VLANS and then all connections were gone.

Were the devices adopted by the controller and in a  connected status before this step?

Can you describe (paste screenshots) what changed in this step?

I know you want lags, but I think it's easier to troubleshoot without them and just focus on the vlans first and then create the lags later.

  @D-C 

Agreed - get the basic adoption and trunking working first then expand after.  

The other thing i just realised

You are not using an omada gateway, therefore, in the controller you need to modify the default vlan with the correct vlan ID as well (it has to have an IP but this can be anything, its important the the management ID matches what you are actually using) and this will be initially assigned to adopted devices.

What might be hapenning is

Device gets adoptioed - first stage is give it the management vlan ID - which might be set incorrectly in controller - device then imemdiately loses connection and adoption dies