<div dir="ltr">I've done a few of these and here's the way I've done it in the past.<br><br>*) If using DNS make sure reverse DNS is working correctly (sub upgrade uses this regarding the pub)<br>*) upgrade Pub, reboot to new partition<br>
*) when this comes backup it doesn't become properly active (depending on config of cluster) so normally the phones will stay with the existing cluster (again depending on config of cluster).<br>*) upgrade subscriber and reboot.<br>
<br>Phones will reboot, in my scenario this never took more than 20 minutes, with 7940's and 60's. From 200 - 400 handsets.<br><br>To do each server takes approximately 2 hours each. I was under the impression you had to do it in this order to get the publisher database in a good condition for the subscriber database to use, but I could be wrong (anybody able to clarify this).<br>
<br>D<br><br><br><br><br><div class="gmail_quote">On Wed, Jul 30, 2008 at 11:01 PM, <span dir="ltr"><<a href="mailto:keli@carocomp.ro">keli@carocomp.ro</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
There are close to 1000 phones, a mix of 7940, 7960 and CIPC soft-phones, load-balanced across the two servers (so some have the sub as primary, while others have the pub as primary in their CCM group)<br>
<br>
Also, since the servers are in a datacenter, and the phones in several locations in a metropolitan area, I'm not exactly sure of the "distances" of each location ...<br>
<br>
Anyway, the good news for me seems to be that the 7940/60 phones have a much smaller firmware :)<br>
<br>
thanks,<br>
Zoltan<div><div></div><div class="Wj3C7c"><br>
<br>
Quoting Kris Seraphine <<a href="mailto:baryonyx5@gmail.com" target="_blank">baryonyx5@gmail.com</a>>:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Are all the phones registered with the same box? If so, your downtime<br>
should be limited to the time it takes to upgrade the phone firmware.<br>
The SRND has a section on how to calculate this. I just upgraded 25<br>
7941s to 8.3.5 last night over a T1 line and it took 24 minutes (from<br>
start until all phone were registered again). This was with peer<br>
firmware sharing enabled.<br>
<br>
I'd imagine you'd want to install the license after rebooting the<br>
publisher but before rebooting the sub. The CM service won't start<br>
until the license is installed.<br>
<br>
On Wed, Jul 30, 2008 at 8:49 AM, Kelemen Zoltan <<a href="mailto:keli@carocomp.ro" target="_blank">keli@carocomp.ro</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>
<br>
I'm going to upgrade a cluster of two CUCM 5.1.2 servers (both MCS7845) from<br>
5.1.2 to 6.1 release.<br>
<br>
However, the customer is keen on knowing expected service outage times, and<br>
the duration of the whole operation in itself. Even if they do not expect<br>
exact timeframes, telling them "it will take a lot" just won't do :-)<br>
<br>
So can anyone give me an idea, of how much time would it take to upgrade<br>
this cluster and of this, approximately how much would they be without<br>
service?<br>
<br>
Especially, since, as far as I understand, upgrading in itself does not mean<br>
interruption is service, since I'm working on an inactive partition.<br>
<br>
Also, is this planned order correct (basically based off SRND):<br>
- upgrade first node, don't reboot<br>
- upgrade second node (there's only one), don't reboot<br>
- reboot first node with switching versions<br>
- reboot second node with switching the version<br>
<br>
the Feature licenses for the v6 should be uploaded before the upgrade<br>
process, or after the first node reboot?<br>
<br>
thanks,<br>
Zoltan<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br>
</blockquote>
<br>
<br>
<br>
--<br>
kris seraphine<br>
<br>
</blockquote>
<br>
<br>
<br></div></div>
----------------------------------------------------------------<br>
This message was sent using IMP, the Internet Messaging Program.<div><div></div><div class="Wj3C7c"><br>
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</div></div></blockquote></div><br></div>