With 8x100-GbE QSFP28 slots per FortiGate unit, it provides enough capacity to directly connect with 2x100-GbE ports to each of the two core FortiSwitch units at a nonstop forwarding capacity of up to 800-Gbps firewall performance using NP7 and CP9 hardware accelerated security. With 8x100-GbE QSFP28 slots per FortiGate unit, it provides enough capacity to directly connect with 2x100-GbE ports to each of the two core FortiSwitch units at a nonstop forwarding capacity of up to 800-Gbps firewall performance using NP7 and CP9 hardware accelerated security. With the Fortinet solution for integrated networking using FortiLink, the core layer always comprises a set of two to four FortiGate devices and two very high-speed FortiSwitch units, which support a large number of 100-GbE and/or 40-GbE ports with enough capacity to grow the links between them and. The stack is connected to two Secure Firewalls 3105. The Core is doing L3 routing for four VFR's. Other VFR's are routed on the Firewall. How would you configure the connection between Core and Firewall? Currently we have a transit network (VLAN 100, 192. Routes on the Core for all. Firewalls typically have lower throughout than the Core, however it would give you security between VLANs There is no best solution, just depends on the customer requirements EDIT: also, it's not a stupid question, this comes up pretty regularly in the Enterprise and knowing why you would do one. For enterprise network architects and senior infrastructure engineers, determining where Layer 3 routing logic should reside—on the core switch or the Next-Generation Firewall (NGFW)—is a foundational design decision. A misstep here can either cripple network performance with unnecessary. In this scenario, IP addresses of the interfaces connecting the core switch to the BRASs and firewalls and OSPF need to be configured on the core switch, so as to implement connectivity between the user network to egress network through the core switch.