Белая книга для Cisco Cisco Prime Virtual Network Analysis Module (vNAM) 6.1

From a resilience perspective, a vPC-based design is sufficient at this scale, although there are other 
benefits of using FabricPath, including:

FabricPath is simple to configure and manage. There is no need to identify a pair of peers or 
configure port channels. Nevertheless, port channels can still be leveraged in FabricPath topologies 
if needed.

FabricPath is flexible. It does not require a particular topology, and functions even if the network is 
cabled for the classic triangle vPC topology. FabricPath can accommodate any future design.

FabricPath does not use or extend STP. Even a partial introduction of FabricPath benefits the 
network because it segments the span of STP.

FabricPath can be extended easily without degrading operations. Adding a switch or a link in a 
FabricPath-based fabric does not result in lost frames. Therefore, it is possible to start with a small 
network and extend it gradually, as needed.

FabricPath increases the pool of servers that are candidates for VM mobility and thereby enables 
more efficient server utilization.

Certain application environments, especially those that generate high levels of broadcast, may not 
tolerate extremely large Layer 2 environments.

VMDC 3.0-3.0.1 addressed several methods of resiliently attaching redundant appliance or 
module-based service nodes in order to optimize service availability and efficient link path utilization, 
including Ether-channel (for example, as shown previously), vPCs with Multi-Chassis EtherChannel on 
paired Virtual Switching Systems (VSSs), and vPCs on clustered (Cisco ASA) firewall appliances. 
However, service node implementation in VMDC VSA 1.0 differs significantly from previous VMDC 
releases in the following ways: