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.
what vlan is the fortigate connected to? If possible move it to its own vlan and verifiy that the other vlans can route to the new switch-fortigate vlan.
Make sure you set the default gateway or route 0 to that of the connected fortigate interface IP
Did you assign IPs to the vlan interfaces on the switch? if not, ip the vlan interfaces and set the clients default gateway to the IP of the vlan. see if you can ping the fortigate.
I don't know if you are using any kind of dynamic routing protocol - but it looks like probably not.
Easiest way is to create another VLAN dedicated for swtich/fortigate traffic with a small subnet (/28 or /29) and put only the switch and the Fortigate on that vlan.
Then you create a static route on the switch that points 0.0.0.0/0 to the IP of the Fortigate on that "transit" vlan.
On the fortigate side, you'd create static routes for each of your subnet and point those to the IP of the Cisco on that transit VLAN. Or you could just use 10.95.0.0/21 based on your diagram.
Does that help?
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 |
---|---|
1696 | |
1091 | |
752 | |
446 | |
228 |
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.