{"id":10000,"date":"2009-11-24T09:56:00","date_gmt":"1999-11-29T20:00:00","guid":{"rendered":"https:\/\/aidanfinn.com\/?p=10000"},"modified":"2009-11-24T09:56:00","modified_gmt":"1999-11-29T20:00:00","slug":"update-vmm-warning-13926-host-cluster-was-not-fully-refreshed","status":"publish","type":"post","link":"https:\/\/aidanfinn.com\/?p=10000","title":{"rendered":"Update: VMM Warning 13926 Host Cluster Was Not Fully Refreshed"},"content":{"rendered":"

Here\u2019s an update on a previous blog post<\/a> that I wrote last week.<\/p>\n

The issue was that I had built a new one node Hyper-V cluster and VMM could not manage it.\u00a0 The error was:<\/p>\n

\u201cWarning (13926)
\nHost cluster <cluster FQDN> was not fully refreshed because not all of the nodes could be contacted. Highly available storage and virtual network information reported for this cluster might be inaccurate. <\/em><\/p>\n

Recommended Action
\nEnsure that all the nodes are online and do not have Not Responding status in Virtual Machine Manager. Then refresh the host cluster again\u201d.<\/em><\/p>\n

I logged a call with Microsoft through IT Pro Momentum<\/a> and here was the response:<\/p>\n

\u201cAfter confirmed this design with our product team, they told me that this feedback has already been reported to them, it\u2019s really a problem, and they are considering to improve it in the future release of VMM, They are aware of this issue and are actively looking into it further. I\u2019m sorry for the inconvenience brought to you now.<\/em><\/p>\n

In the current release of VMM, There are also some workarounds you can take to \u201csolve\u201d this issue. One possible workaround that has been identified is to temporarily add a second node to the cluster at which point you are then able to bring it under management by VMM.\u00a0 While this is neither an ideal or long term solution, it has allowed other customers who have ran into this issue to move forward with their projects. Another workaround that I\u2019ve found that will allow the \u2018single node cluster\u2019 scenario to complete is \u2026 once the Add Host process completes w\/info and has the 13926 warning, change the cluster reserve value from 1 to 0, and then re-cycle the vmmservice.\u00a0 This should allow the host cluster to be added successfully in the console\u201d.<\/em><\/p>\n

There you go.\u00a0 It\u2019s a bit late for me to test but the real world work around appears to be to change the cluster reserve value (cluster properties in VMM) from 1 to 0, and then recycle the VMM Service on the Hyper-V node.\u00a0 I\u2019d tried the value change without the service restart which didn\u2019t work.\u00a0 Hopefully this will help someone in the future.<\/p>\n","protected":false},"excerpt":{"rendered":"

Here\u2019s an update on a previous blog post that I wrote last week. The issue was that I had built a new one node Hyper-V cluster and VMM could not manage it.\u00a0 The error was: \u201cWarning (13926) Host cluster <cluster FQDN> was not fully refreshed because not all of the nodes could be contacted. Highly … Continue reading “Update: VMM Warning 13926 Host Cluster Was Not Fully Refreshed”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"_wpcom_ai_launchpad_first_post":false,"footnotes":""},"categories":[20],"tags":[],"class_list":["post-10000","post","type-post","status-publish","format-standard","hentry","category-hyper-v"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t