I have a couple of posts i want to make about issues in SDN - possibly quick fixes, but this topic is about an issue i can't seem to figure out.
EAP245V3 (x2) - Connected all under the same WLAN
SG2428P (about 3 days old), configured and connected to Omada SDN - hence the topic being under this category
ISP - PfSense (VM) - ESXi - 2 x LAN ports out (non LAG/LACP) - SG2428P
Omada SDN controller running on Debian, clean install, no migrated data. All FW and OS versions are the latest.
I have posted my question here, though i believe the issue is around configuration of the switch, simply because the switch is managed by Omada, so all guides on the switch configuration itself are not relevant or have not been helpful in me finding a solution.
I have read both the Switch manual and the Omada controller manual, though i'll be honest, i may have missed or misunderstood something.
Do note that all of the above setup was the same previously with the exception of the switch, I've replaced an SG2434P with SG2428P, the configuration otherwise is all the same.
1. I can see the switch, all ports and all physically conencted devices, where a name is listed an IP is too and the 'uptime' is stable and counting as it should, however for any VMs on the ESXi host, connected by 2 LAN ports, not LAG/LACP configured, i get a list of mac addresses, but no IP and no host names (I've added some manually) and in the log>events, these connections connect and disconnect constantly, I thought this might be the two NICs, so i disconnected one, the problem persists. Do note, the devices do not physically drop off the network, they do not drop pings either, but they log a disconnection and connection.
The PfSense firewall has multiple VLANs and both physical NICS are trunks (in VMware) and all tagged except LAN on the switch. Using the ALL profile
Nothing disconnects physically and i can always ping VMs, the LAN ports, the host, firewall etc. It's just the disconnection in the events view, it shouldn't be doing this and since i don't drop any pings, i dont know if this is accurate or something i've missed in the switch/Omada configuration. This is affecting all VMs and all VMs will use ports 23 or 24.
2. My EAP 245v3, one of them has a pass-through device connected, I've set the LAN port as a different VLAN (but same as one of the SSIDs the AP hosts) - but it never gives the guest an IP on the VLAN it's marked for, it only ever gives an IP from the VLAN the AP is connected to, if this is VLAN1, the pass-through device gets an IP from VLAN1, if this is VLAN30 it gets an IP from VLAN30, even if it's marked to be on VLAN 50 for example.
3. Also related and similar to 2. If i put the AP on a different VLAN, such as VLAN30, but also want guests on the SSID to use 30, 40 and 50, again as examples, SSIDs 40 and 50 both work, but 30 fails to get an IP - yet the AP is happily sitting on this VLAN. If i move the AP to VLAN1, all 3 SSIDs work as expected. In the settings of the switch, it says the native VLAN is tagged by default, so VLAN30 should be passing through, but it doesn't seem to. This setup worked on the old switch, just doesn't seem to on the new one.
Sorry this is a long post, i hope it all makes sense and i've simply missed something in the configuration - the configuration between my old switch and the Omada managed one is a little different, so it's possible my translation of the configuration isn't 10% accurate.
I will post the issues with Omada SDN seperately another time.