@D-C 

I made some small changes in the switch configuration like you mentioned. I have 3 AP's, located on the switch on ports 21, 22 and 23. These ports have the MGMT network (10.10.10.x as VLAN 1 untagged, with PVID set to 1) and the other 3 networks, LAN(20), IOT(60) and GUEST(99) are set as tagged. So far so good.

A little bit more detailed info: 

- The omada controller is located virtually (I know, to make it even more difficult to get setup correctly :/) and is connected to the MGMT (management) network (10.10.10.x) 

- The AP was first connected to the LAN network (10.10.20.x) 

At this stage, even though they aren't both in the same network, they could "see" each other in the omada controller(green - CONNECTED) and I can configure the AP.

When I then make the changes in the omada wireless settings and then connect one of the AP's to port 21, the omada controller first gives an error "heartbeat missed", followed bu "disconnected" a little while later. 

To make things even more strange, when I swapped the AP's cable to port 21, It actually worked for a few minutes, I got a IP address in the 10.10.99.x range, I even could browse the web, but after a few minutes, all wireless SSID's are gone. I assume at the same time that the omada controller changes the state of the AP to "disconnected".

I think I am still missing something?

If you need some screenshots, or any more info, please let me know.

  @Houseofdreams_, assuming that you're using DHCP, if you can plug a computer into port 21, do you get a 10.10.10.x address?

  @D-C 

When I use a static 10.10.10.x address I'm connected (lan/internet) when I use DHCP, I don't get a IP address. Strange... This is my "networks" setup in the omada controller. 

Edit: I'm now connected with a patch cable to one of the ports on the switch that are in the MGMT 10.10.10.x network (port 7 on the switch) and also there, with a direct connection, I don't seem to get a IP address from the MGMT network. I'm trying to find out why I don't get DCHP from that network. It's enabled in PFSense, all other networks do get DHCP, so it's not the DCHP service that's buggy.

Strange.

@Houseofdreams_ DHCP services on pfSense are unique to each interface so don't assume it's running on your 10.10.10.x network based on it working on other networks. Most likely it's an issue with the VLAN 1 configuration somewhere between pfSense and the AP.  On the Omada devices that support it, I use DHCP and set the fallback ip so a DHCP issue will not cause problems.

  @D-C 

Got some time to test some things....

Made a ubuntu VM on the esxi box, gave it a MGMT network card, installed it and without a problem, it gets an IP of 10.10.10.100 

So on the esxi box, the DHCP works, I can see it in the DHCP leases table in PFsense. But still, when I connect a laptop for example to one of the 2 assigned MGMT ports on one of the 2 switches (windows laptop, not that this would make any difference) I can do ipconfig / release - ipconfig / renew and it just sits there and after a while it just says that there is no ip address assigned.

From what I can see, the port settings on the switches are also correct. Port 18 on switch 2 is assigned as a untagged System-VLAN (1) with PVID set to 1. The same is done n switch 1 on port 7.

I assume this is correct?

Is there any way that I can "debug" the switch?

@Houseofdreams_, yes port settings seem correct.  "Debugging" a switch?  I guess you could try packet captures (not my specialty), but not sure that's necessary.

Try assigning a static IP to your laptop and plug it in to one of the MGMT ports.  Try pinging the pfSence interface (10.10.10.1??).  If that works, I'd focus on DHCP/pfSense.  If you can't ping it, try pinging the switches between the laptop and pfSense to see what works and what doesn't.

If you can share more details about your topology it would help to visualize things now that there's more than a switch, controller and AP in play,

  @D-C 

Topology is no problem :)

@Houseofdreams_, you might try changing switch 1 port 8 (pfSense trunk) to make VLAN 1 untagged and PVID=1.  Seems using default VLAN could have some odd behaviors.  I can't put the link in th post, but google "pfsense default vlan interface" and go to the Netgate Documentation to read about it.

I have pfSense and no problems, but I don't use VLAN 1 for anything.

  @D-C 

It's getting stranger by the day... Positive news is, it now seems to be working like I want it to?

Changes I made: (correct me if I'm wrong somewhere)

- made a new VLAN 70 (Servers) and put my linux servers in there, also the Omada controller with fixed IP 10.10.70.10. So far so good.

- Set the Omada MGMT lan network to the settings below, so I assumed the AP's would be getting a IP in the VLAN 70 range.

All Wireless SSID's are visibe, I can connect to them and I'm getting the expected IP ranges, according to the SSID I connect to (20, 60, 99). Wifi is also stable and doesn't lose connection after a while like before. AP is also not displayed as "heartbeat missed" or "disconnected" but... And here is where it get's really strange: the AP get's a IP in the 10.10.10.x range??? (All of a sudden the DHCP problem in the 10.10.10.x range is gone, without me having changed anything... )

I assumed, with changing the Omada MGMT lan to the 10.10.70.x range, all of the AP's would be getting an IP in this range?

Extra info: AP is now connected to port 21 on the switch, which has the following VLAN settings:

- VLAN 1: untagged

- VLAN 20, 60, 70 and 99 : tagged

Oh yeah, extra thing: with no exact reason, the Omada controller website, is sometimes unreacheable for a couple of minutes, coming back online without any input/changes from me. I'm really strating to think my server is haunted.

If you can make any sense of this, I'm all ears :)