[cisco-voip] Planning to upgrade CM from 4.2 to 8.0.2
Go0se
me at go0se.com
Wed Oct 20 10:50:13 EDT 2010
A couple of "gotchas":
Depending on what phone firmware version you are currently running you may
need to upgrade your phones to 8.3(3) firmware on your old 4.2 cluster
before you begin. See notes here:
http://www.cisco.com/en/US/partner/docs/voice_ip_comm/cuipph/firmware/9_0_3/
english/release/notes/7900_903.html#wp57602
Also, keep in mind that if you use attendant console it is no longer
supported in CUCM 8.x.
Finally, if possible we typically like to purchase a new hard drive to
install the new UCM version onto. Keep the old drive as an emergency backup.
If something goes wrong simply swap the old drive back into the server and
you are back to your old 4.2 cluster. Trust me, if you spend several hours
on an upgrade only to have something go wrong the last thing you will want
to do is spend several more hours installing a clean copy of 4.2 and then
restoring a backup.
Thanks,
Go0se
My blog:
<http://atc.go0se.com> http://atc.go0se.com
--------------------------------------------
Help Hopegivers International
Feed the orphans of Haiti and India
<http://www.hopegivers.org> http://www.hopegivers.org
--------------------------------------------
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Amanda Lalli-Cafini
Sent: Wednesday, October 20, 2010 6:05 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Planning to upgrade CM from 4.2 to 8.0.2
Good Day All,
I have a CM 4.2 (publisher and subscriber) that I need to upgrade to CUCM
version 8.
I am trying to get my head around the best process to follow.
Prework- doublecheck the physical hardware will support 8.0.2c.
7835-H2 with 2Gig RAM and 72G hard disk (done)
1. Get everything ready to rebuild CM4.2 if necessary
check the backups
recovery/installation disks
2. Use the DMA tool
Correct any problems or errors before proceeding.
3. The devices on the network are registered t the subscriber.
Shutdown subscriber (small outage window) and make sure the devices
register with the CM 4.2 publisher.
4. Build a new publisher on test network to 7.1(2)
The new Publisher server gets the IP address of the current publisher
Choosing this particular version because I found a Cisco guide for
upgrading 4.2(3) to 7.1(2)
5. Migrate the data
6. Check that phones will regiter to new CM 7.2(2) publisher.
7. Upgrade to 8.0.2 and recheck test phones.
8. Plan an outage window to shutdown CM4.2 Publisher and introduce
CUCM8.0.2c publisher
9 If all goes well, build a new subscriber
This will be the first time I am responsible for an upgrade between Windows
based CM to Linux Based so it would be really great to hear from people who
have done this before.
I am most interested in knowing if my plan is basically solid and what are
the 'gotchas' that I need to look out for.
Thanks very much for any assistance.
Regards,
Amanda
Amanda Lalli-Cafini
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20101020/92d1aa36/attachment.html>
More information about the cisco-voip
mailing list