Replicated VM NIC - invalid configuration for device 0

[Cragdoo]

Support Case: # 01723992

I have a weird issue, where I can replicate a VM, run a successful SureReplica job, but when I initiate a failover plan the NIC for a VM appears as disconnected. If I attempt to re-connect the NIC I get the error message ' invalid configuration for device 0'


Replication - success



SureReplica/SureBackup - success



VM after failover plan - success



VM NIC disconnected



Error when reconnecting NIC



Has anyone come across this issue before ?

[skrause]

I have had this issue crop up in VMware when the vswitch/network selected is not available on the host.

I would confirm the network remap settings in your Replication job plan are correct for the target host.

[Cragdoo]

have already done so. The weird thing is it isn't every time that nic fails to connect , some days it does, others it doesn't.

[skrause]

Are you using distributed vSwitches?

If you are using standard vSwitches and it is powering up on a different host that has an ever so slightly different vSwitch configuration that might do it.

[Cragdoo]

Distributed switches

[dellock6]

I remember there was a different error "Invalid backing" when using static binding in distributed switching. I know this one is different, but maybe it's worth a try to use ephemeral binding ?

[skrause]

What luca mentioned reminds me that I had an issue with starting up a new VM on one of my clusters with distributed switches that had reached the maximum number of ports configured even though they were set to ephemeral bindings. So you might check that as well.