I PCD 18.104.22.16800-4 and I'm migrating a CUCM version 8.5 to 11.5, and the installation is complete, but the tool indicates that PCD is waiting to answer the CUCM PAWS service, and this can not be manipulated by WEB or CLI
The same problem:
I PCD 22.214.171.12400-4 and I'm migrating a CUCM version 8.6.2 to 11.5, and the installation is completed but the tool indicates that PCD is waiting to answer the CUCM PAWS Service.
The installation of 10.C.C.X took too long to complete. PAWS service on
the node did not respond to PCD with the active version response. Please check the plataform-api logs on the UC application node for further failure details.
Also tried to get the active version using CLI from the UC application node.
Which was also failed to give the response to PCD. Hence the task is failed
In one similar case it was resolved by disabling LRO on ESXI.
Disable LRO, reboot ESXi and PCD. Also ensure that DNS is set up correctly if it is being used.
In my case, we have a bug in the version. The certificates did not migrate to new CUCM11.5 installation.
So, after collected a lot of logs of the server via CLI (with boot cd and recovery disk) we got access to CUCM 11.5 partitions and collected the logs to tac Cisco.This case has been scaleted to Cisco Developers team that created a special release to fix this problem.
With that realease I got to use the PCD and create a migration task and end the installation without errors.
Following the information about the problem found:
After performing a PCD Migration to CUCM 10.5.2SU3 or 11.x, all the phones are unregistered, ILS links down and secure SIP trunks. The OS Administration webpage will show that the certificates are valid from the date of the migration.
PCD Migration from CUCM 8 or 9 to 10.5.2SU3 or 11.x.
The PCD Migration is performed with default settings. No network settings are changed.
a) Set the service parameter "rollback to pre 8.0" to true and then perform the migration.
b) Migrate to 10.5.2 and then perform a normal upgrade to 11.x
Further Problem Description:
When the migration is made, the destination node detects at install phase that the hostname has changed and there's no need to migrate the certificates, thus it's regenerating them because it cannot find any on the trust store.
Root Cause Analysis
Due to the defect, if the source cluster's hostname is in upper case(or one or more letter is in upper case) then while migrating, PCD will return the hostname in lower case. This leads to hostname change parameter to be TRUE.
As hostname has changed as per logic, PCD will not migrate the certificates and hence the migration fails.
The defect will be fixed in CUCM 12.X but I have been asked to send a request for an ES for 11.5 CUCM version. I am raising the same now.
You will need downloaded the image: UCSInstall_UCOS_126.96.36.19925-1.sgn.iso, and create a task to migration via PCD but create only CUCM Pub Migration process from 9.x to 5.1.12025-1.
After that install the subscriber, apply the patchs and locales.
Yes, you do need to install the same ISO image for subscriber CUCM, and one image version 11.5.x of the CUPS or IM&P.