Hello,
There is a project in our organization to deploy a Microsoft virtualization infrastructure.
Most of our networking gear is from Cisco, so presently we are evaluating the Nexus 1000v
for Hyper-V. We have a setup in a lab with SCVMM, AD and two Hyper-V hosts, all running
2012R2. On the N1K, we're running version 5.2(1)SM1(5.2a) .
This post is to figure out the ins and outs of the "system" parameter that can be applied
to a network segment, network uplink or port profile. The documentation states that this
parameter should be applied when there is a need for forwarding to work, even when the
VSM is unreacheable. In the deployment guide, one can read: "When the Microsoft
Hyper-V host restarts, all the switch ports are disabled for forwarding...the Cisco
Nexus 1000V VSM will reprogram all the switch ports on the Microsoft Hyper-V host...."
Why are the vSwitch ports in disabled mode by default ? What are the limitations of
using the "system" parameter ? The documentation implies it should be used only
with host management ports, storage ports (i.e. "system" ports). Why not use it
on vethernet VM ports ?
François
