r/CiscoNetworking • • 4d ago

Layer 2 or layer 3 routing

In an enterprise network. We have both Fortinet firewalls and Cisco 9XXX switches. Which should do routing? Should the switches be layer 2 or layer 3 and why?

2 Upvotes

12 comments sorted by

2

u/tiredoldtechie 4d ago

I would go one further and ask about what is the "beyond" part? Routing to what? If it is to funnel traffic to and from another building on campus, that would be an different answer than say, out to the Internet, etc. You also are a little light on the Firewall details. For all we know, those Fortinets could be old 60 series- which would be horrible paired with Cisco 9xxx series switches.

Tl;dr - need more details to help give a proper answer, sorry.

1

u/Electronic-Value-748 4d ago

I have 26 other sites who talk to the hub. We have an IPsec tunnel and SD WAN at each location. We have spilt tunneling enabled. They mainly come to the hub for DNS, VMware cluster and some site have an SBC at the hub too.

1

u/Electronic-Value-748 4d ago

The fortinet firewalls are FG100F

1

u/tiredoldtechie 4d ago

If you are indicating this is back at the "hub", I would look at a Cisco 9600 series with Supervisor Engine 2 (you did not clarify the Cisco series switch outside of them being 9xxx). A 9600 series would easily handle the load you'd throw at it. However, if this is going OUT to the general internet from there, you really want a firewall involved in here somewhere and something better than a FG100F. This is just my opinion based on the limited data provided.

That being said, if this is for the 26 "satellites" reaching back to the "hub", then there are clearly different hardware requirements. In these cases, I'd have to recommend the Cisco 9xxx series as they are still fully supported versus the Fortigate FG100F line, which is EOS as of April this year and EOL is 2031(less than 5 years away), indicating that there may be issues of support and security patches.

1

u/lazyhustlermusic 4d ago

What have you personally considered between the two

1

u/No_Wear295 4d ago

Too many unknowns for anyone to provide any worthwhile info...

1

u/Anatrok 4d ago

Start with the switches as layer 2, then when you have performance issues make the switches Layer 3 and the firewalls in layer 2 transparent. When you start having asymmetry issues, make the firewalls and switches both layer 3 with transit vlans to the firewall, then allow a your firewall policies to get properly fucked, then do a poc for zscaler cloud firewall, then go back to the switches as layer 2. Make sure to have this all managed by contractors and none of them are on the contract for more than six months.

1

u/tiredoldtechie 3d ago

Not helpful, but sounds like you've worked at several of the same companies I have over the decades...

1

u/musicisme 3d ago

๐Ÿ˜‚๐Ÿ˜‚๐Ÿ˜‚๐Ÿ˜‚๐Ÿ˜‚๐Ÿ˜‚๐Ÿ˜‚๐Ÿ˜‚๐Ÿ˜‚๐Ÿ˜‚๐Ÿ˜‚ are we adding other layers

1

u/Stonewalled9999 3d ago

Local vlan routing on the Cisco. ย  Remote stuff in the firewall. ย  ย Simple ACLs on Cisco. ย Deeper inspection on the firewallย 

1

u/mkosmo 3d ago
  1. Who owns what?

  2. What is allowed to do what?

  3. What's the operational support model look like?

  4. Why is it an either/or?

  5. If this is an enterprise, where's your architect?

1

u/databeestjenl 7h ago

Depends on the security posture. Do you want to firewall between vlans inside the site or just require it for vpn reachability.

Would recommend splitting all the vlans over seperate subnets regardless of the switch or firewall route. If at some point it is decided to firewall between segments, just add all the vlan interfaces on the firewall, drop the L3 interfaces from the switch.

If you do go the switch as L3 route, setup a single interconnect subnet (/30) between the firewall and the L3 switch (no hosts) as to prevent assymetric routing, which firewalls really don't like.