Template-Based Network Policy - Cisco Nexus 1000V Deployment Manual

Switch for microsoft hyper-v

Hide thumbs Also See for Nexus 1000V:

Table of Contents

Cisco Nexus 1000V sees the VSMs and VEMs as modules. In the current release, a single VSM can manage up

to 64 VEMs. The VSMs are always associated with slot numbers 1 and 2 in the virtual chassis. The VEMs are

sequentially assigned to slots 3 through 66 based on the order in which their respective hosts were added to the

Cisco Nexus 1000V Switch.

The Cisco Nexus 1000V Switch provides Layer 2 switching, advanced networking functions (security and

monitoring), and a common network management model for Microsoft Hyper-V servers by implementing a

forwarding extension for the Microsoft Hyper-V Extensible Switch. For more information about Microsoft's

Extensible Switch architecture, refer to the Microsoft documentation at

http://technet.microsoft.com/en-

us/library/hh831452.aspx.

Microsoft strongly recommends the use of Microsoft SCVMM as a centralized platform for managing Compute,

Network and Storage resources in the data center. Cisco Nexus 1000V integrates with Microsoft SCVMM 2012

SP1 to allow the virtualization administrator to deploy virtual machines to the virtual access layer. The server and

virtualization teams must deploy Microsoft SCVMM to use Cisco Nexus 1000V to manage virtual networking.

Note:

Cisco Nexus 1000V integrates with Microsoft SCVMM SP1 UR2 Version 3.1.6020.0 and later. Verify that

you are running the minimum required Microsoft SCVMM version before installing Cisco Nexus 1000V.

Figure 1.

Cisco Nexus 1000V Switch Components

Template-Based Network Policy

A unique aspect of the Cisco Nexus 1000V is the way that network policy is defined and deployed. Today, when

an application is deployed on a physical server, the upstream network switches are configured. VLANs and

network policies are applied to the physical switches to help ensure that the application and host run securely and

are highly available. For Cisco switches, this management model requires administrators to enter configuration

mode and apply a series of switch commands that define the interface configuration.

Often, identical configurations are needed on multiple interfaces of the same switch or on different switches. This

management model requires server administrators to depend on network administrators to reconfigure the

network each time a server is brought online. This process can create unnecessary delays in deployment of new

Page 5 of 48

Table of Contents