Cisco Nexus 1000V Deployment Manual page 20

Switch for microsoft hyper-v

Hide thumbs Also See for Nexus 1000V:

Table of Contents

Figure 18.

Some administrators prefer to keep management and control traffic on separate networks on the VSM. This

separation can be achieved by using the control0 interface on the VSM to communicate with the physical

management interface on the Microsoft Hyper-V hosts. It can be configured using the following svs command:

Nexus1000V(config-svs-domain)# svs mode L3 interface[Mgmt0|Control0]

Following is an example showing how to configure the Control0 interface for communication:

Nexus1000v(config)# int control 0

Nexus1000v(config-if)# ip address 192.168.150.10 255.255.255.0

Nexus1000v(config-if)# svs-domain

Nexus1000v(config-svs-domain)# svs mode L3 interface control0

After entering this code, try to ping the 192.168.150.10 interface from the Microsoft Hyper-V hosts. You should not

be able to because a default route has not yet been set for the default VRF instance. The following CLI shows how

to set the default router

Nexus1000v(config)# vrf context default

Nexus1000v(config)# ip route 0.0.0.0/0 192.168.150.1

Figure 19 shows the control0 interface used to communicate with the VEM.

Management Interface on the VSM and the Microsoft Hyper-V Host Management Physical NIC Used for

Connectivity

Page 20 of 48

Table of Contents