NIC loses network label when unregistered and re-registered

[rodupr]

We have a dynamic enviornment where when VMs are not in use they are unregistered, then when needed again they are re-registered. Since we upgraded everything to vSphere 4 U1 and implemented disturbuted virtual switches we have run into a problem. When the VM is unregistered and later re-registered it looses it network label and comes up not connected to the DVS. I am not sure if this is because of the DVS or vSphere 4. This was not a problem when we were using vCenter 2.5 and ESX 3.5 U4.

I was wondering if any one else had noticed this and if they found a workaround other than manually going into the VM configruation and picking the correct network label?

Thanks,

Rodney

[jfelinski]

Restart vmware management service and it will bind right ports from dvSwitch

service mgmt-vmware restart

---

MCSA+S, VCP 3, VCP 4

[rodupr]

The VM has lost it's network label, so there is nothing to bind to.

[jfelinski]

I had the same problem when dvSwitches wasn't correctly assigned after manual registration. Management network restart will map the right dswitch ports to the host. Did you try to do it?

---

MCSA+S, VCP 3, VCP 4

[rodupr]

We are programmatically using the vCenter API to register and unregister vms and it is not known what host in the cluster they will come back on so it is not feasible to restart the management network services on all hosts in the cluster.

[calypsocraig625]

Hi rodupr,

Did you find a resolution to this issue? I fail to see how restarting the mgmt service on a host will resolve this, however I tested it anyway and it failed. It feels like an issue either with the .vmx file or vcenter does not recognise the parameter from the .vmx file or it's done by design for some reason?

Cheers