[cisco-voip] PCD 10.5(3) and IM&P 9x to 10x

[Anthony Holloway]

That's a relief to hear you've done it. The documentation isn't very clear
if a Network Migration is possible, let alone a Simple Migration. Just take
a look at the PCD 10.5(3) doc under supported releases. Thanks for
replying.
On Mon, May 4, 2015 at 10:27 PM Justin Steinberg <jsteinberg at gmail.com>
wrote:

> i've done it and it is mostly straightforward.  In my case, I did a
> network migration to change the hostname of IM/P.   However, I used the
> same IP address as the old server (this was a MCS to UCS 8 to 10 migration).
>
> I only did a network migration because I wanted to change the hostname to
> align with naming conventions.    The first go around, I didn't update the
> DNS with the new hostname A/PTR for the new IMP name.   The PCD migration
> task for the IMP server failed.  It needed to have the DNS server updated
> with the new IM/P 10.x server's A/PTR in DNS and the old MCS v8 CUPS server
> removed from DNS (since it was using the same IP)..
>
> Make sure that all the VMs in the new v10 cluster have perfect DNS
> resolution, A & PTR before the PCD.   If there are any issues, this will
> mess up the migration.
>
> Also, open the console of the VM in VMware during the PCD tasks to monitor
> the status of the tasks.   PCD doesn't provide alot of progress update, but
> if you watch the console of the VM in VMware you can follow the familiar
> CLI install process.
>
> On Mon, May 4, 2015 at 10:57 PM, Anthony Holloway <
> avholloway+cisco-voip at gmail.com> wrote:
>
>> Has anyone experience with PCD and performing a *Network Migration* on
>> IM&P?  If not, how about performing a *Network Migration* on CUCM, and
>> then how did you handle IM&P?
>>
>> Thanks.
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150505/9fc36695/attachment.html>