cfan73
asked on
Cisco Catalyst 6500 Virtual Switching System (VSS) design - Layer 2/3
Cisco's Virtual Switching System (VSS) in the Catalyst 6500-series is a Layer 2 technology. The customer (currently w/ a non-VSS dual-core design), is routing at the edge - meaning, they have Cisco 3750 stacks in the closets configured for Layer 3 links (point-to-point /30 subnets between the closets and the core). They're dual-homed to each parent switch (again, non-VSS), so there's EIGRP load-balancing between the two equal-cost uplinks. My questions:
Is it possible/feasible to deploy a unified VSS core design w/ L3 distribution links, or should VSS only be rolled out in environments w/ L2-only access closets?
Given that the customer already has L3 switching at the edge (w/ load-balancing across the dual-homed uplinks), does a VSS core really offer any benefit, performance/scalability-wi se?
Thank you - reference links/docs are always appreciated.
Is it possible/feasible to deploy a unified VSS core design w/ L3 distribution links, or should VSS only be rolled out in environments w/ L2-only access closets?
Given that the customer already has L3 switching at the edge (w/ load-balancing across the dual-homed uplinks), does a VSS core really offer any benefit, performance/scalability-wi
Thank you - reference links/docs are always appreciated.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
>which would be tough (for me) to justify wasting multiple 10-GE ports on each chassis just for this.
If you've already got the sup's in place and you're not using them, I don't see a downside to VSS.
>Do you know if the same reasoning would apply to vPC
Yes.
If you've already got the sup's in place and you're not using them, I don't see a downside to VSS.
>Do you know if the same reasoning would apply to vPC
Yes.
ASKER
Do you know if the same reasoning would apply to vPC (Virtual Port Channels) on the Nexus side, where there would be no reason to implement this in a routed L3 environment?