[cisco-voip] CUCM Bridge Upgrade Question 7.1 to 8.6

[Gregory Wenzel]

That's how we do it. During your import of your lab ucs build you should change the ip address so you can do a parallel install. This is our path usually if it can be done over a weekend and depending on how many remote locations on the cluster you could make the changes on each gw one at a time. This way you can have a back-out plan with little downtime.

Check the firmware upgrade path but you should be fine at your current level os.

Gregory Wenzel
Solution Engineer, CCNP Voice
Continental Resources Inc

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Hitch
Sent: Friday, May 04, 2012 4:54 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] CUCM Bridge Upgrade Question 7.1 to 8.6

I am planning an upgrade for a (3) node 7835-H1 cluster running 7.1(5)SU2 to a (3) node cluster running 8.6(2)a on VMs.
Since these servers only support a bridged upgrade I was wondering if I could do the following to reduce the risk and amount of downtime required for the extended "refresh" upgrade.

1. Install 7.1(5)SU2 on a 7845-H2 lab server
2. Perform a DRS restore on this lab server from the production 7.1(5) publisher
3. Upgrade the lab server to 8.6(2)
4. Perform a DRS backup of 8.6(2)
5. Restore the DRS backup on 8.6(2) Publisher VM (pre-built in an isolated environment using the same IP address).
6. Build Subscriber VMs in isolated lab environment using the same IP addresses.
7. Switch routing from the production environment to the pre-built lab environment.

I find this very appealing since our original cluster will still be running untouched in case we have to switch back.

Any concerns with this "modified bridge" approach?
The only concern that I see is that the subscribers will not be connected to the lab publisher server when I do the upgrade from 7.1 to 8.6.
Is that going to be an issue?  Any other concerns?

I see a few posts with similar questions, but I just want to be clear about the subscriber portion.
I do not think that the disconnected subscribers should matter, but would love to hear from someone who has used this method.

Thanks,
Ryan

This message w/attachments (message) is solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited. 
Unless specifically indicated, this message is not an offer to sell or a solicitation of any products.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20120504/f97f4aac/attachment.html>