Explorer

Solved

Using FortiSwitch Interfaces in multiple VDOMs

Forum|Forum|2 years ago
May 4, 2024
8 replies
6762 views

Has anyone been able to move FortiSwitch interfaces to a different VDOM than where FSW is?

I added FortiSwitch to root VDOM and moved some interfaces to another VDOM following this guide: https://docs.fortinet.com/document/fortiswitch/7.4.2/fortilink-guide/801172/multitenancy-and-vdoms

I created a VLAN on the new VDOM and assigned to the switch ports. However, when connecting a device to one of these ports, I'm unable to get the device to have an IP assigned from the VLAN.

When checking "FortiSwitch Clients" list, I find the connected device under "root" instead of the new VDOM, and It's assigned the default VLAN 1 from root, rather than the VDOM assigned to the port.

I'm running FortiOS 7.4.3 on FGT and FortiSwitch 7.4.2.

Best answer by Theo4

The issue got fixed after upgrading FortiOS to 7.4.4 and FortiSwitch to 7.4.3, so I assume it's a bug, although can't find a matching issue in the release notes.

dbu

Staff

Hi @Theo4 ,

Is the DHCP server enabled for this VLAN interface ?
What happens if you assign a manual IP address to the device ?

You mentioned it is showing under vdom root, have you done the export of the interface to the tenant VDOM ?

Here is a good article on how to troubleshoot the DHCP flow :
https://community.fortinet.com/t5/FortiGate/Technical-Tip-Diagnosing-DHCP-on-a-FortiGate/ta-p/192960

https://community.fortinet.com/t5/FortiGate/Troubleshooting-Tip-DHCP-relay-issue/ta-p/215535

Theo4Author

Explorer

Hi,

- DHCP server is enabled.

- I assigned a manual IP to the device. It keeps sending ARP to FGT without reply, because it wasn't assigned to the intended VLAN.

- I did export the interface to the tenant VDOM. the switch port is showing under the tenant VDOM already.

- Eliminating DHCP still didn't fix the issue, so I don't think it's a DHCP problem. Adding to that the fact that the device is landing in root VDOM and being assigned the wrong VLAN.

pushparaj2

New Member

I don’t think (though can’t be certain) that it’s work, fortilink is a single interface (made up of many physicals) but the single fortilink has to reside in one vdom and tha vdom can only be active on one cluster node. I suspect that the interface you use on node b with the split mode wouldn’t come up.

Theo4Author

Explorer

Hi pushparaj2

There is no cluster. This is a single FortiGate node. There is also no split mode. FortiLink consists of two physical interfaces and they are both active.

The idea here is to split FortiSwitch ports into multiple VDOMs, not FortiLink interfaces, similar to what's described here: https://docs.fortinet.com/document/fortiswitch/7.4.2/fortilink-guide/801172/multitenancy-and-vdoms

hbac

Staff

Hi @Theo4,

What is the native VLAN of the switch port you are connected to?

Regards,

Theo4Author

Explorer

It's a new VLAN I created on the new VDOM.

hbac

Staff

Hi @Theo4,

Please make sure you assign that new VLAN as a native VLAN of the switch port. Please refer to https://docs.fortinet.com/document/fortigate/7.0.0/sd-wan-sd-branch-deployment-guide/352373/assigning-vlans-to-switch-ports

Regards,

Theo4AuthorAnswer

Explorer

The issue got fixed after upgrading FortiOS to 7.4.4 and FortiSwitch to 7.4.3, so I assume it's a bug, although can't find a matching issue in the release notes.

Sign up

Login with SSO

Login to the community

Login with SSO