Hyper-V-VmSwitch Event ID 95 created on each replication

[martin.scott]

Hello

I have a set up where I have two server 2012 hyper-v servers. One is used as primary host, the other as failover.
Veeam is set up to replicate the servers on the first one onto the second. Various jobs with various frequencies depending on requirements.

Failover and failback tests indicate all of this works ok.

However on the failover server I get a Hyper-V-VmSwitch error - event id 95 (The VLAN configuration being set on port 4762DBF3-67D0-44B7-8251-483D54471086 (Friendly Name: Virtual Machines_External) on switch CA089C91-F23D-4924-B7FD-A31FECD77829 (Friendly Name: Virtual Machines) is invalid. Reason: VLAN settings other than Access VLAN Id must be zero)
every single time replication begins.

I cant find any hints anywhere about this error(eventid.net, google, TechNet, here) but as we run a continual replication for one particular server, the event log is just filling up with it.

Ive tried removing the relevant switch from hyper v and recreating it precisely as it is on the primary host server. And checked all settings to see if they look the same both on the switch and the network section on the hyper v console for the servers in question. All without any success.

Any help or suggestions would be gratefully received!

[Vitaliy S.]

Hi Martin,

Do you have the same issue if you replicate any VM back to the production host? I will consult with our dev team on the event you see, meanwhile can you please open a support case, so we could check where this mapping comes from? Additionally, do you see any other related events on the DR host?

Thanks!

[martin.scott]

I dont get the same thing on failbacks but I havent replicated any VMs from the failover host to the live one. Ill set something up to check that in a little while.
There are no particularly related events in the logs. Just page after page of the this one

There is a another Hyper-V-VmSwitch Event ID 75 (The operation 'Get Stats' failed on port 16543142-08D9-4603-AF2D-081FF2F4F5E4 (Friendly Name: ) on switch CA089C91-F23D-4924-B7FD-A31FECD77829 (Friendly Name: Virtual Machines). Status = A non close operation has been requested of a file object with a delete pending..) but I havent started looking into that, but I dont think its related. I think thats a separate issue.

[Vitaliy S.]

Yes, could be. Can you please update this topic with your case ID after you run a replication job back to the prod host?

[martin.scott]

The support number is 00692307

I am unable to run a replication job from the failover to the production host. I keep getting the error, not enough licences.

[Vitaliy S.]

Ah... yes you need more sockets to protect another host. Thanks for the case ID.

[Justin_Beswick]

Hi was there ever a resolution to this, I'm getting a similar issue. All Failovers, failbacks and migrations work, however I get the below issue with Veeam

The operation 'Get Stats' failed on port <ID> (Friendly Name: ) on switch <ID>Friendly Name: LAN Switch). Status = A non close operation has been requested of a file object with a delete pending..

[Vitaliy S.]

Our support team has provided a hotfix for this problem, so please contact them directly to obtain it and give a reference to this case ID 00692307 in your email. Thanks!

[martin.scott]

awesome, thanks

[micheldb]

Hi, I have the same issue with EventID 75
The operation 'Get Stats' failed on port <ID> (Friendly Name: ) on switch <ID>Friendly Name: LAN Switch). Status = A non close operation has been requested of a file object with a delete pending..
This seems to happen if the Hyper-V server is very busy.....

[foggy]

Michel, please contact technical support for a hotfix mentioned above.

[valentin.ciobanu]

Hi There ,

We encounter this kind of error but strangely we only have backups and no replication jobs.
Does anyone know if this issue is truly related to Veeam ?

Thanks 1

[veremin]

It's been over three years since the last reply in this thread, so, we cannot say reliably whether the issue experienced is similar to the one discussed here.

Kindly, open a ticket with our support team for further investigation.

Thanks.