I am testing DRS restore for production CUCM 612 Cluster with multiple subsequent nodes. Is it possible to restore First Node and subsequent nodes to servers with different IP addresses other than the ones used in production cluster? In Cisco DRS doco, no place mention that you have to use the same server name and IP address.
I installed a First node with the same server name, but different IP address. When did DRS restore, it failed at CCMDB restore. Anyone knows what caused this error?
I was trying to retore the entire cluster. This CCMDB error occurred when restoring the First Node. I did not see the error 425 in the log. The CCMDB log in DRS restore:
CDRREP: Could not start Cisco CAR Scheduler
CDRREP: Exiting car service activation script with error code 99
CAR services failed to start; Restore failed. TERMINATING
I have not started the subsequent node yet. My feeling is that DRS only works when all nodes in the cluster use the same IP addresses as the original cluster where the backup files were generated. After restoring the first node (90% complete with CCMDB Error), I could not login to CCM Admin page. But I could login to OS Admin and DRS page. I guess the restore process changed the First node IP address in CCM Admin under System > Server.
I will try again to install the new Cluster with the same IP addresses and then do DRS restore.
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...