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.
Solved! Go to Solution.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
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.
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
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.
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.
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
It's a new VLAN I created on the new VDOM.
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/assignin...
Regards,
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.
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1732 | |
1105 | |
752 | |
447 | |
240 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.