So what is guest cluster? A guest cluster is when you create cluster inside of virtual machines. In the past we’ve done that trough ISCSI or FC and lately with Shared VHDX in Windows Server 2012 R2. And like any other cluster you will want to monitor these clusters with SCOM but as they are just like any other cluster where is the catch? Continue reading “Notes from System Center Battlefield: Monitoring Guest Clusters with SCOM”
The last issue I’ve stumbled upon with System Center is with VMM component.
- You have SCVMM 2012 SP1 UR2 installed
- You have Windows Server 2012 Hyper-V for hosts
- You use SMB 3.0 share for storing virtual machines
- Some or all of your virtual machines does not use FQDN path to their vhd/x files
- You’ve added your File Server in VMM by FQDN or NetBIOS Name
- You receive the following error: Error (13924) The highly available virtual machine (VMNAME) is not supported by VMM because the virtual machine uses non-clustered storage.
- Some or all of your virtual machines show as Unsupported Cluster Configuration
I’ve managed to resolve this issue by executing the following steps:
1. Make sure you’ve added your file server in VMM by FQDN. If it is not added by FQDN you have to add it.
2. Create new share. You can create it on the same server. Give the share appropriate permissions.
3. Locate the new share in VMM. Add it as storage location to your hosts/clusters.
4. After is added make sure it show green in the properties of the hosts/clusters.
5. Storage migrate all your virtual machines from the old share to new share. For the machines with status Unsupported Cluster Configuration you can change the status to Running by live migrating them trough the Failover Cluster console.
6. After storage migration of each virtual machine refresh it and make sure in the properties of the machine in Status tab all is green.
7. After successful migration of all virtual machines you can remove the old share from the hosts/clusters and delete it from the File Server.
I’ve also may had problems with the permissions on the old share but it is easier to create new share than fixing permissions on existing share with running virtual machines.
The information is provided ‘AS IS’ with no warranties and confers no rights. Keep in mind that your case may be similar and this solution may not work for you.
Software I’ve used:
- Windows Server 2012 with latest updates
- SCVMM 2012 SP1 UR2
- File Server with SMB share
I am sure everybody has faced the challenge with patching clusters. In Windows Server 2012 we have the feature Cluster-Aware Updating to help us with applying software updates. Unfortunately if you use SCCM for patching you will probably continue using it even for 2012 clusters because you’ve already have some process in place and this new feature is no use, at least at first look. When you want to consolidate the work of two or more tools SC 2012 Orchestrator comes to the rescue. That is what Neil Peterson from MSFT have done and provided Cluster patching runbooks that leverage Windows Server 2012 Cluster and System Center 2012 Components. I haven’t tested them but feel free to test them and drop some comment here or in this page where you can download them..
John Marlin [MSFT] wrote a very useful article on how to troubleshoot when a node is removed from active Failover Cluster memberships. As Hyper-V uses Failover Cluster for clustering technologies these tips also apply to Hyper-v Clusters. Read the full article on the link below.