Event Logs of VMs Migration in Failover Cluster of Hyper-V Hosts

Hello All,
We're running Failover Cluster of Hyper-V hosts of Windows Server 2012 R2. Using SCVMM 2012 R2 with UR5 for management.
If any host gets down unexpectedly (due to any reason power/bugcheck/hardware failure or what so ever), then the VMs on that host, of course, get migrated (either quick or live) to some other host within the cluster.
I want to have logs/events of this VMs migration. I want to know that which of the VMs were residing on that host at that time of failure. Of course, we can't have this info in the Cluster events is Failover Cluster Manager. I am unable to find this info
anywhere. I have searched in Event Viewer --> Administrative Roles --> Hyper-V. I have searched a lot in the SCVMM, but no success.
Please help me in finding the exact location of these logs/events. I would also like to know that if the VM was quick migrated or live migrated, and to which host the VM got migrated.
I'd be highly grateful.
Thanks in anticipation.
Regards,
Hasan Bin Hasib

This post was cross-posted in the clustering forum. As noted in that forum, a failure of a host does not initiate a quick or live migration. Migration requires both the source and destination nodes be operational during the entire migration
process. Should a host fail, it is impossible for that host to participate in a migration. In the case of a host failure, the VM is restarted on another node of the cluster. You can still use the information provided by Elton for viewing
events in the event log. If you want to see the exact sequence of log entries, perform quick/live migrations in a lab and notices the changes in the event log. You can also fail a host and see the sequence of log entries.
. : | : . : | : . tim

Similar Messages

Event Logs of VMs Migration in Hyper-V Cluster

Hello All,
We're running Failover Cluster of Win Server 2012 R2 Hyper-V hosts. If any host gets down unexpectedly (due to any reason power/bugcheck/hardware failure or what so ever), then the VMs on that host, of course, get migrated (either quick or live) to some
other host within the cluster.
I want to have logs/events of this VMs migration. I want to know that which of the VMs were residing on that host at that time of failure. Of course, we can't have this info in the Cluster events is Failover Cluster Manager. I am unable to find this info
anywhere. I have searched in Event Viewer --> Administrative Roles --> Hyper-V. I have searched a lot in the SCVMM, but no success. We're using SCVMM 2012 R2 with UR5.
Please help me in finding the exact location of these logs/events. I would also like to know that if the VM was quick migrated or live migrated, and to which host the VM got migrated.
I'd be highly grateful.
Thanks in anticipation.
Regards,
Hasan

You have posted this same question in two different forums. The answer on where to look is posted in the other forum.
https://social.technet.microsoft.com/Forums/en-US/7f0da2a8-debc-4dd8-9214-72ed46e3c76b/event-logs-of-vms-migration-in-failover-cluster-of-hyperv-hosts?forum=winserverhyperv
In the future, forum etiquette requests that you do not cross-post.
Again, when a host fails, there is no migration, quick or live, to another node of the cluster. There is a restart. When a host fails, the VMs on that host also fail. The cluster detects the failure and the resources (VMs) that had
been running on the failed node are restarted on another node. You will see different events entered into the event log for a resource start than for a quick/live migration.
The easiest way to see this is to do it. Open up the event viewer on a host to which you plan to migrate a VM. Perform a quick/live migration. Refresh the event viewer and note the events that were logged.
. : | : . : | : . tim

No events logged while VMS offline

IDS and VMS are working fine, the issue is when my Windows box running VMS goes offline(crash, reboot....). I bring the VMS box back online and poll the IDS, but it reports no events.
I tested it by running Nessus while the VMS box is offline, from the CLI I see events, but when the VMS box comes online and polls the IDS....Nothing...
Do I need to setup the IDS to store the events until the VMS box can poll again?
Thanks,
Jamey

I did a "sh event alert past 23:00" and it does show the old alerts, however security monitor still does not show then. It only show alerts that happen while it is connected.
I cleared the alerts on the IDS. ran Nessus, then did "sh event alert past 23:00" and it did show the past events (from the nessus scan). I then turned on the VMS box. But security monitor does not show any events (it is set show earliest).
Any other thoughts?
Jamey

Guest VM failover cluster on Hyper-V 2012 Cluster does not work across hosts

Hi all,
We are evaluating Hyper-V on Windows Server 2012, and I have bumped in to this problem:
I have a Exchange 2010SP2 DAG installed on 2 vms in our Hyper-V cluster (a DAG forms a failover cluster, but does not use any shared storage). As long as my vms are on the same host, all is good. However, if I live migrate or shutdown-->move-->start one
of the guest nodes on another pysical host, it loses connectivity with the cluster. "regular" network is fine across hosts, and I can ping/browse one guest node from the other. I have tried looking for guidance for Exchange on Hyper-V clusters but have not
been able to find anything.
According to the Exchange documentation this configuration is supported, so I guess I'm asking for any tips and pointers on where to troubleshoot this.
regards,
Trond

Hi All,
so some updates...
We have a ticket logged with Microsoft, more of a check box exercise to reassure the business we're doing the needful. Anyway, they had us....
Apply hotfix http://support.microsoft.com/kb/2789968?wa=wsignin1.0 to both guest DAG nodes, which seems pretty random, but they wanted to update the TCP/IP stack...
There was no change in error, move guest to another Hyper-V node, and the failover cluster, well, fails with the following event ids I the node that fails...
1564 -File share witness resource 'xxxx)' failed to arbitrate for the file share 'xxx'. Please ensure that file share '\xxx' exists and is accessible by the cluster..
1069 - Cluster resource 'File Share Witness (xxxxx)' in clustered service or application 'Cluster Group' failed
1573 - Node xxxx failed to form a cluster. This was because the witness was not accessible. Please ensure that the witness resource is online and available
The other node stays up, and the Exchange DB's mounted on that node stay up, the ones mounted on the way that fails failover to the remaining node...
So we then
Removed 3 x Nic's in one of the 4 x NIC teams, so, leaving a single NIC in the team (no change)
Removed one NIC from the LACP group on each Hyper-V host
Created new Virtual Switch using this simple trunk port NIC on each Hyper-V host
Moved the DAG nodes to this vSwitch
Failover cluster works as expected, guest VM's running on separate Hyper-V hosts, when on this vswitch with single NIC
So Microsoft were keen to close the call, as there scope was, I kid you not, to "consider this issue
resolved once we are able to find the cause of the above mentioned issue", which we have now done, as in, teaming is the cause... argh.
But after talking, they are now escalating internally.
The other thing we are doing, is building Server 2010 Guests, and installing Exchange 2010 SP3, to get a Exchange 2010 DAG running on Server 2010 and see if this has the same issue, as people indicate that this is perhaps not got the same problem.
Cheers
Ben
Name                   : Virtual Machine Network 1
Members                : {Ethernet, Ethernet 9, Ethernet 7, Ethernet 12}
TeamNics               : Virtual Machine Network 1
TeamingMode            : Lacp
LoadBalancingAlgorithm : HyperVPort
Status                 : Up
Name                   : Parent Partition
Members                : {Ethernet 8, Ethernet 6}
TeamNics               : Parent Partition
TeamingMode            : SwitchIndependent
LoadBalancingAlgorithm : TransportPorts
Status                 : Up
Name                   : Heartbeat
Members                : {Ethernet 3, Ethernet 11}
TeamNics               : Heartbeat
TeamingMode            : SwitchIndependent
LoadBalancingAlgorithm : TransportPorts
Status                 : Up
Name                   : Virtual Machine Network 2
Members                : {Ethernet 5, Ethernet 10, Ethernet 4}
TeamNics               : Virtual Machine Network 2
TeamingMode            : Lacp
LoadBalancingAlgorithm : HyperVPort
Status                 : Up
A Cloud Mechanic.

Network Name Resource Availability - failover cluster error 1196 on Hyper-V 2012 R2 nodes

Hello,
We're getting this error in our even logs of our four node failover cluster, we tried deleting Host A record in DNS management, that did nothing.
Failover cluster event: 1196
"Cluster network name resource 'CAUCrgt8' failed registration of one or more associated DNS name(s) for the following reason: This operation returned because the timeout period expired.
Ensure that the network adapters associated with dependent IP address resources are configured with at least one accessible DNS server."
And this resource http://technet.microsoft.com/en-us/library/cc773529%28v=WS.10%29.aspx did not help in solving this.
Do you guys have any other suggestions we could try to resolve this error?

Hi Jonas,
Please offer us which platform server you are using, such as if you are using server 2012 please refer the following update first.
Recommended hotfixes and updates for Windows Server 2012-based Failover Clusters - http://support.microsoft.com/kb/2784261
If the update not work please ppply Full Control permissions for the Cluster Name Resources in the DNS console.
More detail information please refer the following article:
Windows Server 2008 Troubleshooting: Event ID 1196 — Microsoft-Windows-FailoverClustering - http://social.technet.microsoft.com/wiki/contents/articles/windows-server-2008-troubleshooting-event-id-1196-microsoft-windows-failoverclustering.aspx
DNS Registration with the Network Name Resource -
http://blogs.msdn.com/b/clustering/archive/2009/07/17/9836756.aspx
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Cannot migrate VM in VMM but can in Failover Cluster Manager network adapters network optimization warning

I have a 4 node Server 2012 R2 Hyper-V Cluster and manage it with VMM 2012 R2. I just upgraded the cluster from 2012 RTM to 2012 R2 last week which meant pulling 2 nodes out of the existing cluster, creating the new R2 cluster, running the copy
cluster roles wizard since the VHDs are stored on CSVs, and then added the other 2 nodes after installing R2 on them, back into the cluster. After upgrading the cluster I am unable to migrate some VMs from one node to another. When trying to do
a live migration, I get the following notifications under the Rating Explanation tab:
Warning: There currently are not network adapters with network optimization available on host Node7.
Error: Configuration issues related to the virtual machine VM1 prevent deployment and must be resolved before deployment can continue.
I get this error for 3 out of the 4 nodes in the cluster. I do not get this error for Node10 and I can live migrate to that node in VMM. It has a green check for Network optimization. The others do not. These errors only affect
VMM. In the Failover Cluster Manager, I can live migrate any VM to any node in the cluster without any issues. In the old 2012 RTM cluster I used to get the warning but I could still migrate the VMs anywhere I wanted to. I've checked the network
adapter settings in VMM on VM1 and they are the same as VM2 which can migrate to any host in VMM. I then checked the network adapter settings of the VMs from the Failover Cluster Manager and VM1 under Hardware Acceleration has "Enable virtual machine
queue" and Enable IPsec task offloading" checked. I unchecked those 2 boxes refreshed the VMs, refreshed the cluster, rebooted the VM and refreshed again but I still could not live migrate VM1. Why is this an issue now but it wasn't before
running on the new cluster? How do I resolve the issue? VMM is useless if I can't migrate all my VMs with it.

I checked the settings on the physical nics on each node and here is what I found:
Node7: Virtual machine queue is not listed (Cannot live migrate problem VM's to this node in VMM)
Node8: Virtual machine queue is not listed (Cannot live migrate problem VM's to this node in VMM)
Node9: Virtual machine queue is listed and enabled (Cannot live migrate problem VM's to this node in VMM)Node10: Virtual machine queue is listed and enabled (Live Migration works on all VMs in VMM)
From Hyper-V or the Failover Cluster manager I can see in the network adapter settings of the VMs under Hardware Acceleration that these two settings are checked "Enable virtual machine queue" and Enable IPsec task offloading". I unchecked those
2 boxes, refreshed the VMs, refreshed the cluster, rebooted the VM and refreshed again but I still cannot live migrate the problem VMs.
It seems to me that if I could adjust those VM settings from VMM that it might fix the problem. Why isn't that an option to do so in VMM?
Do I have to rebuild the VMM server with a new DB and then before adding the Hyper-V cluster uncheck those two settings on the VM's from Hyper-V manager? That would be a lot of unnecessary work but I don't know what else to do at this point.

Windows Server 2012 Failover Cluster (Hyper-V) Event Id 1196

Hi All,
I just installed Failover Cluster for Hyper-V on windows server 2012 with 2 nodes. I got following error event id 1196.
reCreated / deleted Cluster Host A record on DNS and nothing happened.
Any suggestion?
There is similar topic but it couldnt help
http://social.technet.microsoft.com/Forums/en-US/winserverClustering/thread/2ad0afaf-8d86-4f16-b748-49bf9ac447a3/
Regards

Hi,
You may refer to this article to troubleshoot this issue;
Event ID 1196 — Network Name Resource Availability
http://technet.microsoft.com/en-us/library/dd354022(v=WS.10).aspx
Check the following:
Check that on the DNS server, the record for the Network Name resource still exists. If the record was accidentally deleted, or was scavenged by the DNS server, create it again, or arrange to have a network administrator create it.
Ensure that a valid, accessible DNS server has been specified for the indicated network adapter or adapters in the cluster.
Check the system event log for Netlogon or DNS events that occurred near the time of the failover cluster event. Troubleshooting these events might solve the problem that prevented the clustered Network Name resource from registering the DNS name.
For more information please refer to following MS articles:
DNS Registration with the Network Name Resource
http://blogs.msdn.com/b/clustering/archive/2009/07/17/9836756.aspx
Lawrence
TechNet Community Support

Migration of VMs from WS2012 Hyper-V Hosts Cluster to WS2012 R2 Hyper-V Hosts Cluster

Hello All,
We’re currently running our production VMs on a Failover Cluster of Windows Server 2012 Hyper-V Hosts. We’re planning to migrate these VMs to the cluster of
Windows Server 2012 R2 Hyper-V Hosts.
I have created a failover cluster of Windows Server 2012 R2 Hyper-V Hosts, and successfully tested the HA of my new test VMs on this new cluster.
Anyone please tell me the procedure, steps and best practices to migrate these VMs from Windows Server 2012 Hyper-V Hosts to Windows Server 2012 R2 Hyper-V
Hosts.
Thank you.
Regards,
Hasan Bin Hasib

Hi Hasan Bin Hasib,
You can refer the following related cross-version live migration KB:
Hyper-V: Migration Options
https://technet.microsoft.com/en-us/library/dn486792.aspx?f=255&MSPPError=-2147217396
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Failover Cluster, Hyper-V, Virtualised PDC and Time Sync

Hi,
I wonder if anyone can clear something up for me.
We have two hosts running failover cluster and hyper-v. On these hosts we two Virtual DCs (one of which is our PDC) as well as a number of member servers. In Hyper-V integration services we have set the time synchronisation option for each server including
the DCs. Each host is joined to the domain so that Failover Cluster works. We also have two physical domain controllers.
When we run w32tm /query /source we can see that the VMs, including the Virtual DCs are getting their time from the Hosts (VM IC Time Synchronization Provider) and when we run w32tm /query /source on the hosts we find that they are getting the time from
each other (host1 has host2 and host2 has host1).
We are experiencing some time drift and I wonder whether this is due to the PDC getting its time from the host, instead of having its w32time type parameter setup to be NTP instead of NT5DS?
What's the best practice for a situation like this??
Thanks in advance!
Stephen

yes, I was actually just digging the article out to post back but looks like you found it already.
i'm not aware of snapshot issues that you mention, its not something I've experienced, but if I was snapshotting a DC I would make sure if was running on 2012 hyper-v and the dc was also 2012, with the pdc being 2012 too. otherwise snapshotting a DC could cause
issues.
Regards,
Denis Cooper
MCITP EA - MCT
Help keep the forums tidy, if this has helped please mark it as an answer
My Blog
LinkedIn:

How to assign SMB storage to CSV in HV failover cluster?

I have a Hyper-V Cluster that looks like this:
Clustered-Hyper-V-Diagram
2012 R2 Failover Cluster
2 Hyper-V nodes
iSCSI Disk Witness on isolated "Cluster Only" Network
"Cluster and Client" Network with nic-team connectivity to 2012 R2 File Server
Share configured using: server manager > file and storage services > shares > tasks > new share > SMB Share - Applications > my RAID 1 volume.
My question is this: how do I configure a Clustered Shared Volume? How do I present the Shared Folder to the cluster?
I can create/add VMs from Cluster Manager > Roles > Virtual Machines using \\SMB\Share for the location of the vhd... but how do I use a CSV with this config? Am I missing something?

right click one of the disks that you assigned to cluster as available storage
I don't yet have any disks assigned to the cluster as available storage.
Just for grins, I added an 8Gb iSCSI lun and added it to a CSV:
PS C:\> get-clusterresource
Name State OwnerGroup ResourceType
Cluster IP Address Online Cluster Group IP Address
Cluster Name Online Cluster Group Network Name
witness Online Cluster Group Physical Disk
PS C:\> Get-ClusterSharedVolume
Name State Node
test8Gb Online CLUSTERNODE01
All well and good, but from what I've read elsewhere...
SMB 3.0 via a 2012 File server can only be added to a Hyper-V CSV cluster using the VMM component of System Center 2012. That is the only way to import an SMB 3 share for CSV storage usage.
http://community.spiceworks.com/topic/439383-hyper-v-2012-and-smb-in-a-csv
http://technet.microsoft.com/en-us/library/jj614620.aspx

VMs on Hyper -V Host Cluster not appearing in Private Cloud in VMM

Hello All,
We are running our production VMs (around 70 VMs) on a failover cluster (let’s say ProductionCluster) of Hyper-V hosts. I created a host group of ProductionCluster in VMM 2012 R2 (with Update Rollup
4 installed), added all the Hyper-V hosts to this host group.
Then I configured a Private Cloud using ProductionCluster, the job successfully completed. I verified it that my cloud was appearing in the VMs and Services workspace
à Clouds, my cloud is appearing there. I also verified that the private cloud library was
created, from Library à Cloud Libraries.
However, any of our production VMs is not appearing in VMs pane. I want to assign user roles and services to the private cloud.
I can see all the VMs when I go to VMs ribbon of host group, but not in private cloud pane.
Please help and guide me.
Thank you.
Regards
Hasan Bin Hasib

>Is it mandatory to associate my VMs with the Cloud?
No, it's not. You can have VMs 'outside' of your 'Cloud'.
>Can I associate my running (production) VMs to the Cloud?
Yes, you can.
>Will it reboot or change the any properties of VM?
No. The only change is the value of the 'Cloud' property.
>Actually, my ultimate goal is to assign delegate control to the VMs' users, and not to give full rights on my Cloud to the VMs' users.
For every VM created before your cloud were created you must assign a VM to your cloud if you want your cloud users to see\manage it. For every VM deployed to a cloud (by a user via WAP portal or if you select 'Deploy to a Cloud' option when deploying a
VM from a VMM Console) the "cloud" property will be set automatically.
http://OpsMgr.ru/

Adding more RAM to all 3 nodes in a hyperV failover cluster, re-validate config?

No issues with 2012 R2 also. Just add the ram and you will be fine.

hey spiceheads,
I have a 3 server node hyper-v failover cluster running hyper-v server 2012 R2.
two of the servers have 96gb and the other 120gb. Going to even all three servers to 128gb.
Once this is done do I need to re-validate? If so, re-validation would take my cluster completely off-line, correct?
Thanks,
ceez
This topic first appeared in the Spiceworks Community

More Failover Cluster CSV problems

Windows 2008 R2 Failover Cluster for Hyper V using CSVSo I come into work today and one of our two nodes on our HyperV cluster is reporting a memory DIMM error. So I am anticipating that we have to bring that server down.I know from the past that if the server that goes down is the Owner of any of the LUNs then if the other server goes down for any reason, the entire cluster will crap out when the other server comes back up and the owner is still down.So in the past I've been able to use Failover Cluster MMC to right click on a LUN and transfer ownership to the other node.I did that today on my 1st of 4 LUNs and instead of transferring over, it now says "Failed" and when I right click on it, all it has is "Help" , no other action available.I'm doing my googling to figure out what to do but I'm sure this is one of the problems I have...
This topic first appeared in the Spiceworks Community

Windows 2008 R2 Failover Cluster for Hyper V using CSVSo I come into work today and one of our two nodes on our HyperV cluster is reporting a memory DIMM error. So I am anticipating that we have to bring that server down.I know from the past that if the server that goes down is the Owner of any of the LUNs then if the other server goes down for any reason, the entire cluster will crap out when the other server comes back up and the owner is still down.So in the past I've been able to use Failover Cluster MMC to right click on a LUN and transfer ownership to the other node.I did that today on my 1st of 4 LUNs and instead of transferring over, it now says "Failed" and when I right click on it, all it has is "Help" , no other action available.I'm doing my googling to figure out what to do but I'm sure this is one of the problems I have...
This topic first appeared in the Spiceworks Community

Failover Cluster - GHOST VMS / ROLES

I mean Ghost as in mysterious non-existent machine, not the old Norton program. I've periodically had random cluster crashes, mainly due to my own negligence. 99%
of the time everything comes back up normally. However periodically a machine will have very strange symptoms that i'm unable to resolve. The only resolution I've found is to create a new VM and link to the the old VHD. A description of the
machines with this issue:
Shown in Failover Cluster role as Running but cannot Connect, turn off, shutdown, etc.
Login to Host machine for the VM and open Hyper-V Manager the machine does not exist. The only place this machine seems to exist is in Failover cluster.
No details available on the Summary Tab, machine doesn't actually appear to be running despite what the console says.
Under the resources tab for that Machine is shows the VM as running, but the VM Configuration as failed.
Unable to bring the configuration back online. Error is "The group or resource is not the correct state to perform the requested operation"
I've seen other vague areas about null context pointers or something alone those lines. I've tried researching the users methods to no avail. How can I fix these? Or at least remove them when i've recreated the machine.

Hi,
Unfortunately, the available information is not enough to have a clear view of the occurred behavior.Could you provide more information about your environment. The server version of the problem on, when this problem occurs the system log record information,
screenshots is the best information.
If you are using Server 2012R2 failover cluster please install the following update:
Recommended hotfixes and updates for Windows Server 2012 R2-based failover clusters
http://support.microsoft.com/kb/2920151
More information:
Event Logs
http://technet.microsoft.com/en-us/library/cc722404.aspx
Thanks.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Failover Cluster 2008 R2 - VM lose connectivity after live migration

Hello,
I have a Failover Cluster with 3 server nodes running. I have 2 VMs running in one the the host without problems, but when I do a live migration of the VM to another host the VM lose network connectivity, for example if I leave a ping running, the ping command
has 2 response, and 3 packets lost, then 1 response again, then 4 packets lost again, and so on... If I live migrate the VM to the original host, everything goes OK again.
The same bihavior is for the 2 VMs, but I do a test with a new VM and with that new VM everything Works fine, I can live migrate it to every host.
Any advice?
Cristian L Ruiz

Hi Cristian Ruiz,
What your current host nic settings now, from you description it seems you are using the incorrect network nic design. If you are using iSCSI storage it need use the dedicate
network in cluster.
If your NIC teaming is iconfigured in switch independent + dynamic, please try to disable VMQ on VM Setting for narrow down the issue area.
More information:
VMQ Deep Dive, 1 of 3
http://blogs.technet.com/b/networking/archive/2013/09/10/vmq-deep-dive-1-of-3.aspx
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.
Hi!
thank you for your reply!
Yes, We are using iSCSI storage, but it has its own NICs for that (2 independant NIcs just to connect the server with the storage) and they are configured to not use those NICs to cluster communication. The team configuration is just for the LAN connectivity.
The NIC teaming is configured using BACS4 software from a DELL server and in Smart Load Balancing and Failover (as you can see here
http://www.micronova.com.ar/cap01.jpg). The link you passed is for Windows Server 2012 and we are running Windows Server 2008 R2, BUT as you can see in the following capture the NICs has that feature disabled
( http://www.micronova.com.ar/cap02.jpg ).
One test that I'm thinking to do is to remove teaming configuration and test just with one independant NIC for LAN connection. But, I do not know if you think another choice.
Thanks in advance.
Cristian L Ruiz
Sorry, another choice I'm thinking too is to update the driver versión. But the server is in production and I need to take a downtime window for test that.
Cristian L Ruiz

Event Logs of VMs Migration in Failover Cluster of Hyper-V Hosts

Similar Messages

Maybe you are looking for