[cisco-voip] upgrade path question
Mike
mikeeo at msn.com
Mon Apr 23 17:45:34 EDT 2012
If your current partner is using that upgrade plan then you need to switch
partners immediately. If you install any version prior to 8.x on VMWARE the
database will be marked as "UNSUPPORTED"
If you need to move from 6.x to 8.x on VMWARE without disrupting the
production environment then you should use the swing server technique.
1) Install current CM version w/ patches on swing server
2) Backup/restore to swing server
3) Upgrade swing server to current 8.x version
4) Backup/restore from swing server to VMWARE
5) Install licenses and test.
6) Swap cables to VMWARE
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 11: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!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120423/f54e4b3f/attachment.html>
More information about the cisco-voip
mailing list