[cisco-voip] upgrade path question

[Erick Wellnitz]

 That's very interesting.  Learn something new from this group almost every
day.

I'm sure it would be fine provided you don't need too much redesign.


On Mon, Apr 23, 2012 at 10:12 AM, Nate VanMaren <VanMarenNP at ldschurch.org>wrote:

>  I don’t see anything wrong with the stated plan.****
>
> ** **
>
> Here is the doc****
>
>
> http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/install/8_6_1/cluster/clstr861.html
> ****
>
> ** **
>
> ** **
>
> *From:* cisco-voip-bounces at puck.nether.net [mailto:
> cisco-voip-bounces at puck.nether.net] *On Behalf Of *Erick Wellnitz
> *Sent:* Monday, April 23, 2012 9:08 AM
> *To:* cisco-voip
> *Subject:* [cisco-voip] upgrade path question****
>
> ** **
>
> Okay,****
>
>  ****
>
> I was under the impression that the following wasn't supported but a
> Cisco partner put this in their upgrade plan for moving from 6.1.3 to
> 8.6(2a).****
>
>  ****
>
> “Install an exact VM copy of the current Call Manager including the
> ES/SRs on the new UCS Hardware.****
>
> Export a copy of the current Call Manager Publisher database and restore
> it on the new VM. Change the****
>
> IP Address of the new virtualized Publisher to match the new IP scheme and
> clean up any IP Addresses &****
>
> Service URLs that pointed towards the old environment. Proceed to upgrade
> the Publisher to version****
>
> 8.0(3) then to 8.6(2a).”****
>
>  ****
>
> I've never seen this in any of the supported upgrade methods in any Cisco
> document.  It would also seem you'd run into licensing issues.  I also
> thought someone here wanted to do something similar and the finding was the
> database would still be marked as unsuppoted.  Maybe I'm remembering
> incorrectly.****
>
>
> Thanks!****
>
>
>
> NOTICE: This email message is for the sole use of the intended
> recipient(s) and may contain confidential and privileged information. Any
> unauthorized review, use, disclosure or distribution is prohibited. If you
> are not the intended recipient, please contact the sender by reply email
> and destroy all copies of the original message.****
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120423/6c92eb0d/attachment.html>