Cisco Nexus 1000V Deployment Manual page 23

In some scenarios, customers may want to share the physical NICs (pNICs) on the host between management
and workload virtual machines (storage, live migration, and cluster heartbeat traffic is also usually shared in these
cases) when limited pNICs are available per Microsoft Hyper-V host. In such scenarios, management can be
moved behind the Cisco Nexus 1000V (VEM), as shown in Figure 21.
Figure 21. Management and Control0 Interface on the VSM and the Virtual Management NIC Behind the Cisco Nexus 1000V
Microsoft Hyper-V has a special requirement for management vNICs. A management vNIC can be created only
during virtual switch (native switch or Cisco Nexus 1000V switch) creation on a Microsoft Hyper-V host. In other
words, a management vNIC cannot be created and deployed to an already existing virtual switch (vSwitch). This
management vNIC creation activity must be performed during vSwitch creation.
To create the topology shown here on a Microsoft Hyper-V host, the Microsoft SCVMM administrator creates a
Cisco Nexus 1000V Logical Switch on the Microsoft Hyper-V host with the pNIC currently used for management
connectivity. As part of this process, the administrator must also create a management vNIC and apply a system
port profile to the vNIC. When the management vNIC is moved behind the Cisco Nexus 1000V (VEM), the network
segment (VLAN) and the port profile used by the management vNIC must be marked as "system network
segment" and "system port profile," respectively. On the physical NIC, the uplink profile with the system VLAN
configuration must be applied. The Microsoft Hyper-V host automatically copies the IP address and Domain Name
System (DNS) setting from the pNIC to the vNIC that is created.
Note: Typically, a pNIC does not use VLAN tags for communication; therefore, while moving the management
vNIC behind the Cisco Nexus 1000V, set the management VLAN on the uplink profile to native. Failure to do so
may lead to loss of connectivity to the host.
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information. Page 23 of 48