VMware Cloud Community
thomps01
Enthusiast
Enthusiast
Jump to solution

Changing the vCPU qty in vCD removes the network connection from the VM in vCenter


This is a crazy issue we've discovered and I wanted to know if anyone else had seen it.

Firstly, we're running the following versions of software:

vCD: 5.1.1.867405

vCenter: 5.0.0 Build 913577

ESXi: 5.0.0 Build 1024429

If you go into vCloud Director and edit the hardware properties of an existing VM (Powered off) any change the vCPU quantity (to anything new), inside vCenter the network status will change to none(inactive) Standard port group.


Even though, before you make the change, the VM is connected to a distributed port group and working ok.

We are posting an SR to VMware now but sometimes it's worth running this by the community to see if other people have seen it already or indeed wish to test it on their deployments.


Thanks in advance

Reply
0 Kudos
1 Solution

Accepted Solutions
thomps01
Enthusiast
Enthusiast
Jump to solution

We've resolved the issue now.

The reason we were experiencing this problem is because we'd used the wrong command in the API.


You need to make sure you use the undeploy command when working with the vCD API otherwise you end up with a disconnected NIC.

View solution in original post

Reply
0 Kudos
1 Reply
thomps01
Enthusiast
Enthusiast
Jump to solution

We've resolved the issue now.

The reason we were experiencing this problem is because we'd used the wrong command in the API.


You need to make sure you use the undeploy command when working with the vCD API otherwise you end up with a disconnected NIC.

Reply
0 Kudos