Solved: PCD 14 SU2 - Migrate CUCM 11 to 14 - PCD not pulling PlatformConfig - Page 2

steeda · ‎02-16-2023

Got a fun one here. Migration failed and I restarted the source VMs running 11. It failed because the nodes could not contact the publisher so they just stalled out forever. Why couldn't they contact the Pub? Come to find out hey had no domain name so couldn't resolve it.

My cluster is DNS based, and DNS is fine. I discovered PCD is *not* getting the Domain Name during the Cluster Discovery task. I verified this by looking in the /export directory by SFTPing into the PCD. The Platformconfig XMLs have every setting except for the local domain section. The PCD Migrate task uses this file and some other others to create a Floppy Image used during install of the new VMs. It's the answer file.

I went ahead an logged into another PCD I used for a previous migration, a 12.5 one. The /export Platformconfig XMLs *have* the local domain section. That PCD had no problem.

I have a TAC case open on this - they're clueless and provided no resolution to the issue or even a suggestion. SO - I am having to figure out a way to fix this myself instead. Fun.

I am wondering if there would be any issue if, prior to the Migration task, I manually edited these PCD-derived Platformconfig XMLs - adding the localdomain section back in - and then starting the task. I am hoping the correct Floppy Images will then be created for the migration.

Anyone hit this yet?

Here is the end of the PCD 14 files it pulls. IPs changed.

Here is the end of the files pulled by PCD 12.5 on a different migration:

<LocalHostDomain>
<ParamNameText>Domain name for this machine</ParamNameText>
<ParamDefaultValue>cisco.com</ParamDefaultValue>
<ParamValue>fake.com</ParamValue>
</LocalHostDomain>

I assure you DNS and domains are populated properly and working in the Source Cluster - PCD is not gathering the info.

Think I can just manually add that section?

steeda · ‎02-18-2023

TAC hasn't responded in 46 hours. Calling it a day until Tuesday.

steeda · ‎02-21-2023

Back at it.

SO:

Have tried fresh installs of both PCD 12.5 and 14.0 - same problem. PCD doesn't get Domain of CUCM servers ( 5 of them ) but does get it from the IM&P pair.

Revved CUCM cluster from 11.0SU2 to 11.5 SU11. Same problem, no change.

Since everyone else's PCD 12.5 and 14 work, there must be *something* going on with this cluster, but what?

This cluster started life in 2012 on CUCM 9 and was IP based. No DNS. In 2015, it was revved to 11.0 and switched to DNS based as that is when the IM&P servers were added and running IM&P without DNS is not ideal. Could there be something where if an ancient cluster like this one - starting life IP based - PCD cannot detect the DNS Domain? What is it even reading with its SOAP requests? Does it look at the ORIGINAL install information where - in 2012 - IPs were specified and DNS was rejected? Or is it looking at the CURRENT config? The former I doubt - as PCD is pulling the DNS Server IPs and placing them in platformConfig.xml - just not the Domain.

I have a new TAC person - stay tuned. They collected the logs and witnessed my findings.

steeda · ‎02-24-2023

7 TAC engineers later and I finally got it escalated. A CCIE Collab team lead helped me and found the problem instantly. The problem isn't PCD at all, there's something to these older clusters that have been upgraded multiple times. In my case, the cluster:

1. Began life as CUCM 9.1, IP based

2. Revved later to 11.0, switched to DNS based.

The servers have a platformConfig.xml file on them, probably from the initial installation when you manually type everything in. In our case, the Domain is blank on all 5 CUCM servers in that file as it would have been on the original 9.1 install. Only TAC can view this file, root is required. Despite the cluster being DNS based, domains specified, FQDNs used in CUCM/Servers, TFTP - fully functioning DNS cluster, that old file sits there doing nothing... until.... PCD pulls it out for a Migration. My IM&P servers started life at version 11 and DNS based, so naturally they were fine - their platformConfig.xml had the Domain from initial installation.

The solution is TAC has to root into each server and manually add the Domain Name to the platformConfig.xml files. PCD will then work. The End User - me - has no way to see this or fix it.