10-16-2012 02:41 PM - edited 03-16-2019 01:43 PM
We are running CallManager 7.0.1 and currently when we login to CUCM as the administrator, everyting works fine. Our current DNS/DHCP server address is 172.16.1.10. We have just created two new DNS/DHCP servers with the address 172.16.1.20 and 172.16.1.30 and want to turn the old server off. We made the change by telnet into CUCM:
set network dns primary 172.16.1.20
set network dns secondary 172.16.1.30
After we do this and turn off the old DNS server, we get the following error when we try to login to CUCM:
Failed to connect to LDAP Server
Where else do we need to make changes, cant seem to find it.
Solved! Go to Solution.
10-16-2012 04:28 PM
If you reset the DNS service you need to restart the tomcat service and cluster manager. For these kinds of changes it might make more sense to restart the cluster Publisher first (might not).
1. utils service restart Cisco Tomcat
2. utils service restart Cluster Manager
Here is the documentation for 7.0.1
Command Line Reference
http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cucm/cli_ref/7_0_1/cli_ref.html#wp39980 DNS
http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cucm/cli_ref/7_0_1/cli_ref.html#wp42424 Service restart
You can verify if it has restarted with
utils service list
If that doesn't work restart the Pub and verify from the command line that you can ping our DNS server.
Here is the information regarding that command line option:
Design guide in case you need it:
http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cucm/srnd/7x/uc7_0.html
Server admin guide also in case you need it.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucmbe/admin/7_0_1/ccmcfg/b02servr.html
10-16-2012 04:28 PM
If you reset the DNS service you need to restart the tomcat service and cluster manager. For these kinds of changes it might make more sense to restart the cluster Publisher first (might not).
1. utils service restart Cisco Tomcat
2. utils service restart Cluster Manager
Here is the documentation for 7.0.1
Command Line Reference
http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cucm/cli_ref/7_0_1/cli_ref.html#wp39980 DNS
http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cucm/cli_ref/7_0_1/cli_ref.html#wp42424 Service restart
You can verify if it has restarted with
utils service list
If that doesn't work restart the Pub and verify from the command line that you can ping our DNS server.
Here is the information regarding that command line option:
Design guide in case you need it:
http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cucm/srnd/7x/uc7_0.html
Server admin guide also in case you need it.
http://www.cisco.com/en/US/docs/voice_ip_comm/cucmbe/admin/7_0_1/ccmcfg/b02servr.html
10-18-2012 07:43 AM
That was it. Thanks for the information.
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