HCX - OSAM failure: "Invalid Configuration for device"

Products

• VMware HCX

Issue/Introduction

Identify a known issue with invalid Windows GuestOS settings that will cause OSAM failure.

Symptoms:
HCX Operating System Assisted Migration (OSAM) will fail to instantiate the VM on the target vCenter.
The error in the HCX Cloud Manager's app.log will show:

2022-00-00 00:00:06.221 UTC [OsAssistedMigrationService_SvcThread-XXX, Ent: HybridityAdmin, , TxId: TxId: <id>] ERROR c.v.v.h.s.m.h.OsAssistedMigrationUtil- Task Failed. {"fault":{"@xsi:type":"InvalidDeviceSpec","property":"macAddress","deviceIndex":4},"localizedMessage":"Invalid configuration for device '4'."}

2022-00-00 00:00:06.436 UTC [OsAssistedMigrationService_SvcThread-XXX, Ent: HybridityAdmin, , TxId: TxId: <id>] ERROR c.v.v.h.s.migration.jobs.CreateVMJob- Failed in executing subworkflow Instantiate VM workflow - Invalid configuration for device '4'. migrationId: <id>

Cause

Under certain conditions, a Windows VM will not record a valid MAC address for an interface (NIC), which is required for OSAM. Some Network Backup solutions may create such interfaces.

Resolution

Remove the invalid NIC from the GuestOS prior to migrating the VM with OSAM.

Workaround:
None.

Additional Information

Impact/Risks:
OSAM will fail for the VM.