05-22-2014 02:56 AM - edited 03-17-2019 04:11 PM
Hi,
I am having a 50 user deployment non redundant setup using non split DNS.The version used for deployment is CWMS 2.0.1.107B-AE .I have configured the ports as per the planning guide for manual deplyment,public access and Non split DNS. Forward and Reverse DNS Entries for are also configured
After deploying the vmmachine at the end ,during the system check i get an error showing that the irp in the DMZ is not able to receive network packets and thus the deployment status is shown as Unsupported Configuration
Attaching the error received. How do I troubleshoot this?Has anyone come across this error?
Solved! Go to Solution.
05-22-2014 07:34 AM
Hi,
You are definitely experiencing a network connectivity issue between the Admin and IRP VMs. Please, ensure that PING (ICMP) is allowed between the Admin and IRP VMs as well as all other required ports (http://www.cisco.com/c/en/us/td/docs/collaboration/CWMS/2_0/Planning_Guide/Planning_Guide_chapter_011.html#reference_CB65D7FE4B3746DDAF1649884AD777CE). Also, ensure that DNS server is reachable from internal and DMZ networks.
Furthermore, I can see that you are using domain.internal for your VM domains. Per Certification Authority announcements, they will stop issuing SSL certificates for internal domains next year (http://www.digicert.com/internal-names.htm) so it might be good to assign a valid domain name for your VMs. This is not related to the current issue you are seeing, but can help you avoid issues with SSL certs in the future.
-Dejan
05-22-2014 07:34 AM
Hi,
You are definitely experiencing a network connectivity issue between the Admin and IRP VMs. Please, ensure that PING (ICMP) is allowed between the Admin and IRP VMs as well as all other required ports (http://www.cisco.com/c/en/us/td/docs/collaboration/CWMS/2_0/Planning_Guide/Planning_Guide_chapter_011.html#reference_CB65D7FE4B3746DDAF1649884AD777CE). Also, ensure that DNS server is reachable from internal and DMZ networks.
Furthermore, I can see that you are using domain.internal for your VM domains. Per Certification Authority announcements, they will stop issuing SSL certificates for internal domains next year (http://www.digicert.com/internal-names.htm) so it might be good to assign a valid domain name for your VMs. This is not related to the current issue you are seeing, but can help you avoid issues with SSL certs in the future.
-Dejan
05-22-2014 08:26 AM
Thank you Dejan.I will check on the points mentioned
05-25-2014 01:44 AM
The system check has passed.I had not added the rule for ICMP from IRP to Admin Machine.ICMP from Admin to IRP was only there
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide