Remote Host did not respond, while deploying CWMS 1.1

[marahman78]

When i tried to install CMWS 1.1, during IRP deployment its giving me Remote Host did not respond and when i try to check VM Console it's showing "

Network Error 3-302: Redeploy, Bad DNS Server, server not responding ". Can anyone face this issue. Find the attached snapshots.

[dpetrovi]

Hi,

As the error states, there is an issue communicating with the DNS server or similar network connectivity. I suggest verifying the networking on the VM (vNICs enabled and connected, correct VM network), but if the system is in the same network as the IRP there should be no issue unless the firewall is blocking something. Please, go through the Network Requirements checklist:

http://www.cisco.com/en/US/docs/collaboration/CWMS/1_5/Planning_Guide_chapter_011.html#concept_DDD6AF3E341B4C6A9C5C65229143F305

Ensure that in case your Internet Reverse Proxy is in the DMZ network, firewall allows Internet Control Message Protocol (ICMP) echo requests and replies. Otherwise, the Internet Reverse Proxy detect and the DNS server accessibility validation may fail if the ICMP echo reply is not received.

I hope this will help.

-Dejan

[Chris Deren]

Dejan,

I am running into the same issue with version 2.5, and customer opened all IP traffic (testing purposes) from the DMZ network to internal network, and nslookup resolves the proper IRP server DNS. What else could it be?  Would it be a DNS resolution or firewall issue? I asked customer to observe firewall traffic, but I am not sure he is able to do that.

[dpetrovi]

Hi Chris,

Just to ensure you are hitting the same issue, can you provide me with some more details about your customer's deployment:

1. What is the size of this deployment?

2. Are internal VMs successfully deployed?

3. Is this issue affecting only IRP VM?

4. Are you deploying IRP automatically or manually?

5. In DNS that IRP is pointing to, do you have IRP hostname and IP address properly configured?

6. Is DNS server pingable from the IRP VLAN?

7. As for the firewall, is it doing any ARP proxying? We've seen issues where firewall hijacks the IP address of the IRP and bounds it to the MAC address of the firewall port. Hence, during the install, this error shows due to duplicate IP issue. Unfortunately, this can only be seen if we access the IRP CLI.

If all of the above seems to be good, and you still have issues with deploying IRP, I would have to suggest opening a TAC ticket as it would be impossible to troubleshoot via forum.

I hope this will help.

-Dejan

[Chris Deren]

Thank you, answers below:

1. What is the size of this deployment?

50-port

2. Are internal VMs successfully deployed?

Yes

3. Is this issue affecting only IRP VM?

Yes

4. Are you deploying IRP automatically or manually?

Manually

5. In DNS that IRP is pointing to, do you have IRP hostname and IP address properly configured?

Yes, ping of the FQDN from another windows host on that network resolves proper IP address, and returns host unreachable

6. Is DNS server pingable from the IRP VLAN?

Yes

7. As for the firewall, is it doing any ARP proxying? We've seen issues where firewall hijacks the IP address of the IRP and bounds it to the MAC address of the firewall port. Hence, during the install, this error shows due to duplicate IP issue. Unfortunately, this can only be seen if we access the IRP CLI.

Not sure, how can we access the IRP via CLI if it's not deployed? The firewall is ASA, is there a way to check if ARP proxy is enabled?

[dpetrovi · Accepted solution]

Hi Chris,

There is a way to access CLI but you will need TAC to boot the VM into SingleUser mode and check the log file to see if it reports duplicate IP address during boot process.

As for ASA, I don't know how to check that. Normally, we involve ASA team to help us look into that. 

I would first reach out to Conferencing TAC to check what they see during boot process, and then go ahead further checking on the ASA.

-Dejan

[Chris Deren]

Thanks, I found some documents that state current ASA code uses ARP proxy by default, so I am checking with customer on this.  If that gets me nowhere I'll open a case. Thank you as usually.

[Oussama.bachiri]

Hi Chris,

we are right now encountering this issue, did you get any workaround or something that you solved the issue with

Thanks a lot

[Chris Deren]

I've encountered it on 2 separate deployments, the solution on first was to add proper DNS entries in DNS as customer entered them incorrectly. Second time the issue was with UCS networking on my ESXi host where VLAN tagging was set.