Aller au contenu principal

Testing Replicas - Unsupported network adapter type '6'.

Thread needs solution

We have replication tasks for all of our VMs, and it seems that on several of them, whenever we test we get a warning in Acronis stating "Unsupported network adapter type '6'.".

We're testing without connecting to the network (because our production VMs are on the network while we're testing).  I'm not sure, but this may be happening only on Windows Server 2012 VMs.

Is this cause for concern?  If we were to boot up the replica with the network connected (in an actual recovery scenario), would it work?

Thanks

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 22
Commentaires: 3800

Hi Brian,

It's hard to advise without checking the full warning text and its context (e.g. full log from operation), but I can guess that you're replicating VMs between different ESXi hosts versions where original VM had some virtual network adapter type (vmxnet3/E1000e/etc.) unsupported by target ESXi host. The first thing to check would be the virtual adapters types on original and replica VMs to see if there are any specifics there + check which virtual network (vSwitch port group) both original and replica VMs are connected to.

Thank you.

Thanks for the reply.  Here's the log.

 

2018-06-14T13:27:51:569-07:00 140161888511744 I0135003A: User is running command. Command=Testing replica; User=root; clientProfileID=E0B8F7D5-09F6-28EE-0535-02FD386A1AB3; clientSessionID=4352E8C5-5B0F-441C-9020-D26C4037D5DB; tenantID=00000000-0000-0000-0000-000000000000

2018-06-14T13:27:58:673-07:00 140161888511744 W01D7003F: Error 0x1d7003f: Unsupported network adapter type '6'.
| trace level: warning
| channel: tol-activity#DF67F410-F846-4170-B7AE-9E9E11353052
| line: 0x7f255dd73eb1cf6a
| file: e:/93/enterprise/migration/replication/machine_networking.cpp:111
| function: ConvertVirtualWareRawNetworkAdapterType
| $module: disk_bundle_lxa64_9010

2018-06-14T13:28:08:624-07:00 140161888511744 I0135003B: Command has completed successfully. Command=Testing replica; tenantID=00000000-0000-0000-0000-000000000000

 

We are replicating across different hosts, but they all have the same ESXi version - ESXi 5.5.0 (7504623).
The source and replica VMs have the same virtual network adapter - E1000E.
They source and replica hosts have identical VM network configs.  Each host only has a single VM network that connects through to the same top-of-rack switch. They exist within the same VLAN and /24 subnet.
The source and replica VMs are the same virtual machine version 10 (vmx-10).

The only difference I can find is that the source host has a (physical) Broadcom BCM5720 adapter with driver "tg3" while the destination host has a (physical) Broadcom BCM5716 adapter with driver "bnx2".  Neither of the hosts have any connectivity issues.  The networks and physical adapters on all of them work fine.

 

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 22
Commentaires: 3800

Hi Brian,

Thank you for the details. I found a known issue record in our DB (internal bug ID: ABR-166490). The problem is related to E1000E virtual network adapter type which triggers the warning. This bug is already fixed in the recently released Update 3 for Acronis Backup 12.5 (build 10130), so updating to it should fix the issue (according to the quoted log you have an older 9010 build which corresponds Update 2).

Thank you.

Thanks.

Is the warning something I should be concerned about?  If we were to replicate and connect to the network (in an actual recovery scenario) would the replica have any issues?

Either way, we'll plan on updating soon.
 

As additional info for anyone who may search for this in the future:

We've finished testing and can now say that this is happening on every one of our Windows Server 2012 and Windows Server 2012R2 VMs.

Our older VMs running Windows Server 2008R2 do not show this warning.

(Our newer, Server 2016 VMs are not in the same ESXi stack and are not being replicated by Acronis.)

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Contributions: 22
Commentaires: 3800

Hi Brian,

The warning does not affect most operations with replica VM, except for connecting replica to virtual network during "Test replica" and "Failover" operations (where actions with virtual networks are performed). As a workaround the network connectivity can always be adjusted by editing replica VM settings.

As mentioned before the guest OS type of the VM does not matter - what matters is the type of virtual NIC: only E1000E is affected, while for example E1000 and vmxnet3 are not affected.

Thank you.