Migrating between 2 CUCM clusters both running 8.5

[bigcappa1]

Guys,

Got an issue, we are moving our cluster location, rather than pick the kit up we bought more chassis to deal with this. So are migration from one cluster to the other

So the CUCM is built on the new chassis, DRS imported no problem, configuration all looks good.

Because of the cert (CTL file) on the current system we need to invoke the roll back in the enterprise paramaters.

This is where my confusion lies. We use EM heavily so the help text for the Prepare Cluster for Rollback to pre-8. state the following:-

Enable this option ONLY if you are preparing to rollback your cluster to a pre 8.0 Cisco Unified Communications Manager release. Phone services (for example, extension mobility) will NOT work when this parameter is set to True, however, users will be able to continue making and receiving basic phone calls. IMPORTANT: You must restart the following services on all nodes, in the order described, immediately after setting this parameter to True: First, restart the Trust Verification Service (TVS) on all nodes; next, restart the TFTP service on all nodes that have TFTP activated; last, return to the Enterprise Parameters Configuration window and click the Reset button to reset all phones. When those three steps are completed and have been performed in the specified order, the cluster will be ready for rollback.

The bit that concerns me the most is Phone services (for example, extension mobility) will NOT work when this parameter is set to True, however, users will be able to continue making and receiving basic phone calls.

So does this mean whilst it is set to true you cannot login or logout, we have around a dozen sites and plan to move them over a three week period, so does this mean they cant login or out for that time?

Secondly we have left the parameter true on the new cluster so does this mean Extension mobility won’t work on the new cluster until we set it back to false?

Any advise would be appreciated

thanks

Paul

[Jonathan Schulenberg]

First off, this parameter only impacts the ITL, not the CTL as you mentioend above. This will *not* erase the CTL from the phone. All it does is create an empty ITL file and sign it with the existing TVS certificate the phones already trust. This effectively tells the phones to accept the next ITL file they get, no matter what it is. Until they get a legit ITL file again all HTTPS operations will fail. This is why non of the services will work: in 8.0+ the phones all use an HTTPS URL, not HTTP.

Secondly, if you have performed a DRS backup/restore this should be entirely unecessary since the DRS restore operations would have retained all of the certificates. You can verify this by comparing the thumbprints under OS Administration > Certificate Management on both clusters. Just watch out for CSCtn50405.

Please remember to rate helpful responses and identify helpful or correct answers.