[cisco-voip] Upgrading CallManager 3.3(3)

[Mike Armstrong]

We've got a single cluster - pub/sub - with about 250 phones.  Takes us 
about 3 hours to do a CM release upgrade, but if we knew we were going to do 
two of them in sequence, we could do both in about 4, I think.  I wouldn't 
deviate from TAC's advice.  One shortcut we've used in the past is to 
upgrade the Publisher all the way, then simply shut down the old Subscriber 
and build a new one from scratch at the final release level, avoiding 
intermediate Subscriber upgrades.  You may need the media kit to do this, 
however.

Mike Armstrong
UF/IFAS CREC
Lake Alfred, FL

> Date: Tue, 15 Aug 2006 15:08:45 -0400
> From: Wes Sisk <wsisk at cisco.com>
> Subject: Re: [cisco-voip] Upgrading CallManager 3.3(3)
> To: Adam <cisco at adman.net>
> Cc: "cisco-voip at puck.nether.net" <cisco-voip at puck.nether.net>
> Message-ID: <44E21BBD.7060009 at cisco.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> it's a YMMV.  Cisco only tested and development only supports 3.3(5) to
> 4.2(1) so TAC will provide only nominal support on attempts to do
> directly from 3.3(3) to 4.2(1).
>
> /Wes
>
> Adam wrote:
>> I need to upgrade a CallManager cluster from 3.3(3) to 4.2(1). The
>> documentation says that I can only upgrade to 4.2(1) from 3.3(5). Is
>> this non negotiable, or is it possible from 3.3(3) as well. If so
>> approximately how long does it take for an upgrade of cluster with a
>> publisher and a single subscriber with less then 100 phones? I'm
>> trying to work out how many/long maintenance windows need to be
>> scheduled.
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip