CUCM 5.1.3 removing server did not remove from show cluster in OS
Just wondering if anyone has seen this - I had someone call in, they had built a Pub, and then were adding 2nd node to the server, in preparation for installing the Sub. They noticed they had used the wrong name, so they deleted it, and added it again correctly. They built the 2nd node, all seemed to be well, and went on and did a bunch of config, and then noticed that it did not appear to be replicating. None of the utils commands to fix replication did anything. They then noticed that in the OS Admin interface, under show cluster, they still saw the incorrectly named Sub, along with the correctly named Sub - suspect that was causing problems, but could not find a way to delete it - it did not show up in the server config in CCMAdmin any more, just in the OS Admin list. They are currently rebuilding, just to get it out the door, but this seems like a real problem!
If you are in a production environment, make sure you move all the services off of the server you plan to remove from the cluster. Make sure nothing is registered to it and no dial-peers etc are pointed at it.
Then remove the server using the Callmanager administration. There are some scripts (Bat files) that must be ran to clean up SQL replication and DCD.
Make sure you follow the instructions EXACTLY. If you do not run the scripts correctly you could drop the wrong database/subscription and be SOL. Don't ask how I know this :-)
If you have another CCM version just do a search for "removing a subscriber server from Cisco Callmanager" on cisco.com.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...