
© 2010 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Inf ormation. Page 15 of 62
Figure 9. VSL Composed of Interfaces on the Cisco 8-Port 10 Gigabit Ethernet Sw itching Module
This deployment scenario allows for a redundant VSL connection as well, but uses the two Cisco 8-port 10 Gigabit
Ethernet modules if the uplinks on the supervisor engine are already in use. As a result, the scenario depicted in
Figure 8 involves more hardware, but it is highly redundant: the VSL can survive both a physical link failure as well as
a complete VSL module failure. This solution also provides for future VSL bandwidth scalability.
Two-Port VSL Using Supervisor Engine and Line Card
Figure 10 shows the two members of the VSS connected through a 2-port VSL bundle; this scenario uses both
supervisor-engine uplinks and a single 8-port 10 Gigabit Ethernet line card for bandwidth and redundancy.
Figure 10. VSL Members Across Supervisor Engine Ports and 8-Port 10 Gigabit Ethernet Sw itching Module
This deployment scenario, which allows for a redundant VSL connection, may require more hardware than using a
single supervisor engine, but offers both link and line-card redundancy as well as the added benefit of future scaling
requirements if you need extra VSL bandwidth in the future.
Multiple Cisco Virtual Switching System Domains
Multiple deployments of Cisco Virtual Switching System can exist in a given network design, adding to the availability
and scalability of the network. As a result, Cisco requires you use unique virtual switch domain identifiers for each
pair of VSS switches.
Figure 11 shows an example of multiple Cisco Virtual Switching System domains in a network design. The figure
shows three unique VSS domains, each with a unique domain ID. You can also deploy multichassis Cisco
EtherChannel links across other Cisco Virtual Switching Systems, removing the reliance on protocols such as
Spanning Tree Protocol.
Comentarios a estos manuales