[VMC] vMotion Compatibility Check Fails for VM with a Disconnected NIC
Article ID: 329677
Updated On:
Products
VMware Cloud on AWS
Issue/Introduction
Details the cause of this issue as well as the workaround plan VMware is implementing.
Symptoms:
The Customer is attempting to vMotion a specific VM and receives a vCenter Compatibility Check failure relating to VM Networks/vmnics.
The specific VM has one/multiple NICs that are in a disconnected state, showing no networks selected for the specific vmnic when checking the VM Settings.
VMC Hosts are unable to enter Maintenance Mode.
A given Virtual Machine shows connected to a "quarantine" network that the customer did not configure themselves.
Symptoms:
The Customer is attempting to vMotion a specific VM and receives a vCenter Compatibility Check failure relating to VM Networks/vmnics.
The specific VM has one/multiple NICs that are in a disconnected state, showing no networks selected for the specific vmnic when checking the VM Settings.
VMC Hosts are unable to enter Maintenance Mode.
A given Virtual Machine shows connected to a "quarantine" network that the customer did not configure themselves.
Cause
The specific VM has one/multiple NICs that are in a disconnected state, showing no networks selected for the specific vmnic when checking the VM Settings. This specific configuration blocks the VMC Host's ability to enter Maintenance Mode.
Resolution
There will be a patch included in a future SDDC release covering the underlying root cause.
Workaround:
VMC Service Owners are going to remediate this issue for the customers who are known to have this configuration present.
Customers will see one/multiple NICs for a given VM show as connected to a "quarantine" network. This quarantine network is being created for the specific purpose of remediation of this problem.
This quarantine network will have no CIDR assigned (No L3 networking in place) and no North/South Connectivity. The segment type will be ISOLATED instead of the traditional ROUTED or DISCONNECTED types. Customers may notice L2 Broadcast traffic originating from this quarantine network, which is expected.
There will be zero changes to any Firewall/security configurations present within the SDDC.
Workaround:
VMC Service Owners are going to remediate this issue for the customers who are known to have this configuration present.
Customers will see one/multiple NICs for a given VM show as connected to a "quarantine" network. This quarantine network is being created for the specific purpose of remediation of this problem.
This quarantine network will have no CIDR assigned (No L3 networking in place) and no North/South Connectivity. The segment type will be ISOLATED instead of the traditional ROUTED or DISCONNECTED types. Customers may notice L2 Broadcast traffic originating from this quarantine network, which is expected.
There will be zero changes to any Firewall/security configurations present within the SDDC.
Additional Information
Impact/Risks:
The customer is unable to vMotion the VM between hosts.
The customer is unable to vMotion the VM between hosts.
Feedback
Yes
No
Powered by
