Management Microsoft Hyper-V Clusters And Hosts; Vsm High Availability - Cisco Nexus 1000V Deployment Manual

Switch for microsoft hyper-v

Hide thumbs Also See for Nexus 1000V:

Table of Contents

separated from workload virtual machines (running line-of-business [LoB] applications) by running them on

separate Microsoft Hyper-V hosts or clusters.

Management Microsoft Hyper-V Clusters and Hosts

In this Microsoft Hyper-V deployment topology, infrastructure virtual machines are deployed on a separate set of

hosts or on an infrastructure Microsoft Windows failover cluster. Examples of infrastructure virtual machines are

Microsoft Active Directory servers, DNS servers, SQL servers, and Microsoft SCVMM and other Microsoft System

Center roles. The Cisco Nexus 1000V VSM virtual machine should also be deployed on an infrastructure host or

cluster. The Cisco Nexus 1000V Logical Switch (VEM) is not created on the infrastructure hosts; instead, the

native Microsoft Hyper-V switch is used.

Figure 29.

Deployment Topology 1 (Recommended)

Cisco Nexus 1000V VSM deployment in high-availability mode is recommended. When the Cisco Nexus 1000V is

deployed in high-availability mode, one of the virtual machine functions as the active VSM, and the other is in hot-

standby mode. VSM virtual machines can be deployed on standalone Microsoft Hyper-V hosts, in Microsoft

Windows failover cluster, or on Cisco Nexus 1010 and 1110 devices. For information about how to deploying the

Cisco Nexus 1000V VSM on the Cisco Nexus 1010 and 1110, please refer to the Cisco Nexus 1010/1110

documentation.

Page 34 of 48

Table of Contents