Virtual Machine NIC configuration changed seemingly on its own

Products

• VMware Cloud Director

Issue/Introduction

• When modifying VM configuration through Cloud Director (RAM, CPU, Storage Policy, Compute Resource)
  • VM NIC in Disconnected State
  • VM NIC configuration using a different Network

Environment

Cloud Director 10.x

Cause

During Placement/Reconfigure Task for VM, Cloud Director uses current configuration information stored within its DB, with the assumption that it has not changed.

If the Network changed outside Cloud Director, it is not known and will be over written. 

For example, if you added a NIC to the VM through vCenter and connect the NIC to a VC network for management.

Another example, if you change network for NIC for the VM in vCenter.

Resolution

Making changes to the VM outside of Cloud Director comes with the risk that it will be overwritten.

Only Make VM changes directly in Cloud Director.