And now, hours later, we're back to the same functionality problem - the switch won't stay on an IP, and is inaccessible from that 10.50.1.x IP range. I'm inclined to say the switch is defective, but...

I performed a system reset to wipe the switch back to factory, and now so far after setting the configuration up again the switch is working as expected - it seems that when the on site installer...

@Clive_A The VLANs aren't defined in the FortiGate however, but DHCP scopes assigned to the ports (port 1 for 10.50.1.x, port 2 for 192.168.80.x) - it feels like the VLAN 1 on the switch is where the...

I made a change (to be honest, I'm not sure what specifically) and the switch is no longer grabbing multiple IP addresses. The issue of the switch getting/releasing the IP address and not listening...

I'm trying (and failing badly) at setting up a TL-SG3452XP remotely in the EMEA region, from the US - we used a TL-SG3428MP as a local testing environment with minimal issue (after help with this...

@KJK Spot on - doing research before your reply, in Fortigate's cookbook: A VLAN interface is attached to a physical interface. When the FortiGate sends out traffic to the physical interface level,...