Cisco Cisco Prime Virtual Network Analysis Module (vNAM) 6.1 Livre blanc
3-29
Cisco Virtualized Multiservice Data Center (VMDC) Virtual Services Architecture (VSA) 1.0
Design Guide
Chapter 3 VMDC VSA 1.0 Design Details
System Level Design Considerations
Figure 3-16
Nexus 1000v 5 Uplink PortChannel Model
Traffic engineering can be performed selectively by configuring the Nexus 1000V to select the target uplink
using a manual configuration (static pinning) instead of the default. For example, front-end traffic that
contains many diversified flows can use both members (fabrics) of the port-channel. On the other hand,
backend traffic, which has more diversity in terms of bandwidth/response time (VM-to-VM inter-fabric
traffic flows, vMotion, backup, and so on) can benefit by selecting a path that enables VM-to-VM traffic
to remain in the same fabric so that Fabric Interconnect switches the traffic locally.
using a manual configuration (static pinning) instead of the default. For example, front-end traffic that
contains many diversified flows can use both members (fabrics) of the port-channel. On the other hand,
backend traffic, which has more diversity in terms of bandwidth/response time (VM-to-VM inter-fabric
traffic flows, vMotion, backup, and so on) can benefit by selecting a path that enables VM-to-VM traffic
to remain in the same fabric so that Fabric Interconnect switches the traffic locally.
architectural features of VMDC VSA 1.0.
Table 3-1
Traffic Classification Example for MAC Pinning
Traffic Type
Classification
UCS Fabric
Mac-Pining
Option
Option
Rational
Front End Traffic Tenant Data
Fabric A & B Automatic
Load Share on all available
uplinks, most traffic should be
exiting the pod through the
Aggregation-Edge Nexus 7000
uplinks, most traffic should be
exiting the pod through the
Aggregation-Edge Nexus 7000