03-17-2026 09:58 AM
I need design advise to understand better and make decision:
- Elaborate/correct and answer please: when using 3-Tier LAN topology design basically we aggregate all L3 SVIs in Distribution switch offloading the load from core. this is in large scale. but if its mid-size network we go with collapsed core. now in 3-tier design does distribution always L3? or it can be L2 and SVIs terminate on core? i think it does not make sense to have L2 dist in 3-Tier design
- if I have a LAN with lets say 30X 9200 access switch, and C9500-24Y4C/C9300X-24HX option for core. also have 1-2 ESXI hosting 5-10 VM servers. what would be the recommended design? collapsed core or 3-tier ? how? Basically if we have local servers then how it fits into any of these design solutions
Solved! Go to Solution.
03-23-2026 11:09 AM
i think the reason i chose to have a separate core is to have dedicated redundant hardware as L3 core to serve access swithces as well as have link to Internet firewall and another link to SD-WAN Vello connecting the site to other sites.
If your thinking you're best served by the logical and physical topologies adopted, that's fine! Whether that's actually true, I cannot judge; I have insufficient information. However, again, good designs probably deserve more consideration beyond greatgrandpop, grandpop, and pop all did it a particular way, automatically make it the best way now, doesn't make it true. The converse is true too, i.e. a new approach isn't necessarily better either. Just consider what's actually best for you.
Whats the deal with not spanning same vlan across L2 HW?!
It continues to create potential L2 issues that are avoided by using L3.
Consider L2 hubs vs. L2 switches. Both provide L2 domains. Both move frames between hosts. So, why did practically everyone migrate from hubs to switches?
Just as switches are superior to hubs, L3 switches are superior to L2 switches. I believe some reasons why L3 switches haven't totally replaced L2 switches include reasons like: cost; the advantages don't seem as impressive; it seems to take more work to set them up, especially compared to the way we're accustomed to using L2 switches.
management vlan and voice vlan both of them needed everywhere ......
But do they all need to be in the same physical or logical subnet/VLAN?
In my last job, I had a couple of L3 6513s using 96 FE PoE port line cards, each port supporting a voice and data VLAN. Across a single chassis, 11 time 96 equals 1,056 edge ports. Do you think I had just one voice and data VLAN on that chassis, and spanned those two VLANs to another 6513 equipped the same way?
I vaguely recall, those two 6513s connected to a 6504, which hosted two off site links. Why use a 6504, couldn't the two 6513s connect to each other and each have one of the off-site links?
Yes, one aspect was the (questionable) hope if one edge 6513 went nuts, the 6504 protected the off-site ring from injected instability.
However, as OSPF was the routing protocol being used, to ECMP the off-site links, they had to be on just one device.
For either both reasons, a 6504 with dual sups is an expensive solution, but the 2,100 edge ports was supporting a call center, so avoiding a major outage was high priority. So, a good design takes into account many factors.
At the time, the 6513s, would have been replaced with newer technology, perhaps using the (then) new VSS technology (which we were starting to use). (Also, at that time, we also had one facility migrate to using new Catalyst 6xxx IA approach, which eventually allowed about 4,000 edge ports per one L3 switch chassis.)
If done today, possibly a spine/leaf might be considered.
03-23-2026 11:22 AM
As a footnote, decades ago, at a different company, when the 3750s were still pretty new, our remote site was a pair of ISRs, each having one WAN link, and one or more 3750 stacks. There was only one 3750 stack running L3, and if that stack had more than two members, only two members had full L3 licences (a feature not supported on today's Cisco stacks, but you could run full L3 if but one working stack member had the full L3 license, but it that single stack member failed, the whole stack would lose advanced L3 unless another working stack member had the advanced L3 - a lot of redundancy and features at minimal cost).
03-23-2026 01:02 PM
In my last job, I had a couple of L3 6513s using 96 FE PoE port line cards, each port supporting a voice and data VLAN. Across a single chassis, 11 time 96 equals 1,056 edge ports. Do you think I had just one voice and data VLAN on that chassis, and spanned those two VLANs to another 6513 equipped the same way?
can you please elaborate on this ? so basically you are saying if you have to have same VOICE/DATA ports being active on both chasis then you used a different VLAN? like valan 5 VOICE on chasis 1 and vlan 10 on chasis 2? if yes then possibly its easy with two chasis yes but what about a scenario with 10X IDFs each of course physically apart with one or two C9200 each uplinked to core? then how many subnets/vlan ?! cumbersome and not easy to manage ...
03-23-2026 01:44 PM
@Najib Akbari wrote:
In my last job, I had a couple of L3 6513s using 96 FE PoE port line cards, each port supporting a voice and data VLAN. Across a single chassis, 11 time 96 equals 1,056 edge ports. Do you think I had just one voice and data VLAN on that chassis, and spanned those two VLANs to another 6513 equipped the same way?
can you please elaborate on this ? so basically you are saying if you have to have same VOICE/DATA ports being active on both chasis then you used a different VLAN? like valan 5 VOICE on chasis 1 and vlan 10 on chasis 2?
I had multiple voice and data VLANs/Subnets on a single chassis, none spanning the two chassis.
@Najib Akbari wrote:
if yes then possibly its easy with two chasis yes but what about a scenario with 10X IDFs each of course physically apart with one or two C9200 each uplinked to core? then how many subnets/vlan ?! cumbersome and not easy to manage ...
Not much easier on a single chassis vs. 10x IDFs. although only two L3 uplinks to manage, rather than ten of them.
Yes, if you have a 10x IDFs, and you could have more VLANs/Subnets vs. spanning a VLAN/Subnet across multiple IDFs, but you gain a L3 design rather than a L2 design, and in some ways, the L3 design can be less complex. For example, needed worry about using PVST feature to direct specific VLANs to be active on just one link. With L3, can use multiple links, and each destination can be best path.
You have 3 choices. Edge might be full L3. Edge might be L2, but its distro either spans the same edge VLAN/subnet across multiple edge devices or it doesn't.
03-23-2026 04:36 PM
Thanks for all the helpful comments!!!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide