[cisco-voip] Upgrade from CM 3.2 > 3.3 > 4.1

[Andrew Dignan]

Yeah.  Thats the plan, to run the new environment and complete a very
detailed test plan on it.  I was just concerned about getting CM 3.2 to
the new MCS hardware.  It looks like I can do a new install of 3.2 on OS
2.7.  I could swear there was an issue with installing 3.2 on an OS that
had Windows SP4 way back when.

digger

> In my opinion, upgrades typically go well. Nothing out of the ordinary.
> The
> one thing you have to be careful of is the behaviour of your system after
> the upgrades. New (and deprecated) system and enterprise parameters as
> well
> as configuration options make upgrading a bit of a task - especially since
> the documentation has been lacking in the past. If you have made use of
> any
> special configuration options, ensure that they are still available. For
> example, I believe in 3.2 there was a 'voicemail box' option in the
> directory number configuration screen - this was removed in 3.3. Your
> upgrade path will more than likely include upgrading the phone images as
> well - that's something you will also have to test.
>
> Consider running a beta (or alpha as some people call it) cluster with
> your
> new hardware and get some real live testing going on. An intercluster
> trunk
> will allow for communications between the clusters although you will lose
> some functionality, e.g. CallBack, PickGroup, etc.
>
> ----- Original Message -----
> From: "Andrew Dignan" <andy at dignans.com>
> To: <cisco-voip at puck.nether.net>
> Sent: Sunday, September 25, 2005 11:46 PM
> Subject: [cisco-voip] Upgrade from CM 3.2 > 3.3 > 4.1
>
>
>> Anyone sure if the following is supported:
>>
>> 1. Existing CM cluster running 3.2.3
>> 2. Migrating to new hardware
>> 3. Install BARS 4.0(x) on existing publisher and run backup
>> 4. Install CM 3.3 on new MCS server
>> 5. Import using BARS the backup from step 3
>>
>> I tried this at home and it does work, I am just not sure if its
>> supported.  The reason I have to do this is because upgrading the
>> production cluster isn't an option at this point.  I have new MCS
>> servers
>> and I cannot install OS 2.4 on these servers for obvious reasons so I
>> think going this route is my only option besides upgrading the
>> production
>> servers to CM 3.3.
>>
>> I have all new hardware and the goal was to build everything off on its
>> own island without effecting the production environment.  There has to
>> be
>> a way..supported or not..to get this done.
>>
>> TIA
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>