VMM Tricks: VMM 2012 error when adding new Host

We are working on new private cloud implementation with high restrictive security boundaries, while adding new Hyper-v cluster “ Windows 2008 R2 Sp1 Core edition” we got error

 

We make sure that we are using administrator account, No firewall problems.

We have Parent Domain (xxx.local) where all Management servers are running "VMM, SCOM and DPM" and we have child domain "YYY.xxx.local"  where all Hyper-v servers are running "10 Servers in One Hyper-v cluster using Windows 2008 R2 SP1 Server Core"
the Hyper-v hosts are from HV01 to HV10 and using IPs from XX.XXX.XX.51 to XX.XXX.XX.60 and Hyper-v cluster IP is XX.XXX.XX.61

 

When I am trying to ping any node of the Hyper-v hosts it is working fine, Able to resolve the Hosts names using NSLOOKUP

When I am trying to add any host to Hyper-v cluster I got this error
[2124] 084C.06D4::06/03-09:25:30.427#18:ServerConnection.cs(1229): Microsoft.VirtualManager.Utils.CarmineException: HV01 cannot resolve with DNS.

I tried to add the host name "netbios and FQDN" to hosts file and got the same error. the funny thing that when I am trying for example HV04 I got the same error that the servers HV01 cannot resolve with DNS.  !!!!!!!!!!

VMM is trying to resolve HV01 not Hv04, I tried IPs and got the same error.

After some troubleshooting it turn to be something wrong in the VMM Server

Using Network Monitor and Wirshark here what i found

When adding the cluster IP or FQDN , VMM Service check with Parent DC to resolve and it manage to get the IP "it does not matter wherever I provide IP or FQDN"

Then the VMM checks with the Child DC for the cluster "Since The cluster and Hyper-v hosts exist in the child domain" and it resolve the cluster name.

VMM start to query the cluster nodes and resolve all nodes and suddenly it start searching for any random host NetBIOS name and consider Host.Parent.domain not hots.child.parent.domain without any reasons and return error that it can not resolve the name

So for the seek of troubleshooting we added all the hosts NetBIOS and FQDN to hosts file and got the same error. Analyzing the capture I found that all Cluster name and all hosts were resolved but suddenly the VMM did the same again with Cluster name "Since it is not added to hosts file"

Adding all Hosts and Cluster names to Hosts file solved the problem.

About these ads