Cisco Nexus 1000V Deployment Manual page 38

Switch for microsoft hyper-v
Hide thumbs Also See for Nexus 1000V:
Table of Contents

Advertisement

Also, because the Cisco VIC supports a minimum of 128 PCIe interfaces, you should create at least 6 vNICs per
blade running Microsoft Windows Server 2012 as shown in Figure 31.
Figure 31.
Cisco Nexus 1000V Switch for Microsoft Hyper-V on a Cisco UCS Blade Server
In this topology, the storage, cluster, live migration, and management traffic is sent directly to the Cisco UCS
vNIC. Workload virtual machines running LoB applications are deployed on the Cisco Nexus 1000V Logical
Switch. The Cisco Nexus 1000V also uses two or more vNICs as uplinks.
To support this topology, a separate service profile is created for the Cisco Nexus 1000V switch uplink vNICs. In
this profile, fabric failover is disabled, as shown in Figure 32. To ensure high availability for workload virtual
machines, vPC host mode is configured on the Cisco Nexus 1000V Switch uplinks. This configuration helps
ensure that the uplinks are bound to a team. When a member link in the team fails, the Cisco Nexus 1000V VEM
helps ensure that traffic from workload virtual machines fails over to one of the remaining links.
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 38 of 48

Advertisement

Table of Contents
loading

Table of Contents