No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


FusionAccessR5C20 failed to deploy VM due to DNS name resolving issue

Publication Date:  2015-06-03 Views:  454 Downloads:  0
Issue Description


Product Version: FusionAccess V1R5C20

Issue Description:When deploying full-copy VM through FusionAccess Portal,it failed and got the error "Failed to obtain the domain information "


Alarm Information

Task failed and got the error "Failed to obtain the domain information"

Handling Process

We login both ITA servers, find the two ITA servers were out of domain, it can ping the AD IP, but can’t ping the domain name.


The AD/DNS server has one NIC, and it is in the management VLAN A;

The ITA server has two NICs, NIC1 for management VLAN A and NIC2 for service VLAN B, but only NIC2 configed with DNS entry,NIC1 didn’t have DNS entry.


Root Cause
When ITA communicate with AD/DNS, because the NIC1 is in the same VLAN with AD, so it always try to resolve the AD name through NIC1,but there is no DNS entry, so it always fail.

To fix this issue, we just need to disable NIC1 for ITA to let it communicate with AD/DNS through NIC2 which configed with DNS entry.

When install the FusionAccess system,if ITA can reach AD and fusioncompute in the same VLAN,then no need to create two NICs.