[cisco-voip] Upgrading from CCM4.0 to CCM6.0

[Jonathan Charles]

I have done about 45 upgrades of CCM clusters, some during maintenance
windows measured in minutes (one was only 2 hrs)...

Yes, they can be bloody... most of the time they are bloody due to
licensing issues with Cisco.



Jonathan

On Dec 11, 2007 12:54 PM, Ali, Aziz <Aziz_Ali at adp.com> wrote:
> That's explains everything. You lucky to have that time to play around
> in lab. BUT
>
> I  hope you haven't got the taste of real upgrade during limited
> maintenance window. This is real BLOODY.
>
> Z
>
> -----Original Message-----
> From: cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jonathan
> Charles
> Sent: Tuesday, December 11, 2007 12:25 PM
> To: Scott Voll
> Cc: Cisco Voip Mailing list
> Subject: Re: [cisco-voip] Upgrading from CCM4.0 to CCM6.0
>
>
> It wasn't that big a deal, it was new servers, so I had plenty of time
> to stage and restore the DMA in a lab, then I just dropped the servers
> in...
>
> The only catch was unity, and that took a few more hours than
> intended, but no big thing...
>
>
> J
>
> On Dec 11, 2007 10:32 AM, Scott Voll <svoll.voip at gmail.com> wrote:
> > only Jonathan can say I did a Huge upgrade and it's "NO Biggie"
> >
> > Tim--  I would make sure the upgrade is to 6.1 if your writing this
> into
> > your erate.  since your doing Erate I'm guessing this will be a after
> July
> > Upgrade.  I'm not an erate expert but be a little vag on the versions
> so you
> > can get the latest.  I had a School district that put the specific
> version
> > and that's what they got.
> >
> > Scott
> >
> >
> >
> > On Dec 10, 2007 1:11 PM, Jonathan Charles <jonvoip at gmail.com> wrote:
> >
> > > Not sure what you are looking for, but I did this upgrade this past
> > > weekend (from CCM 3.3 to 6.0; Unity 4.0.4 to 5.0.1; CER 1.2 to 2.0
> and
> > > CCC 1.2 to MPX 2.0)...
> > >
> > > No biggie.
> > >
> > >
> > >
> > > Jonathan
> > >
> > >
> > >
> > >
> > > On Dec 10, 2007 1:22 PM, Tim Reimers
> <tim.reimers at asheville.k12.nc.us>
> > wrote:
> > > >
> > > >
> > > >
> > > >
> > > > Hi -
> > > >
> > > >
> > > >
> > > > I'm proposing in Erate funding requests that we upgrade our phone
> system
> > > > from:
> > > >
> > > >
> > > >
> > > > Two Call Managers running 4.13
> > > >
> > > > One Unity server running 4.0
> > > >
> > > > One Emergency Responder server running 1.2
> > > >
> > > >
> > > >
> > > > We have a mix of 7960 phones, 7905 phones, and 7912 phones
> > > >
> > > > All switches are 3560 series - a few 3524 switches for additional
> phones
> > > > here and there.
> > > >
> > > > All gateways are H.323 running 12.3 for the most part, and are
> > > >
> > > >
> > > >
> > > > What I'm wondering is if people out there have any documentation
> details
> > > > they wrote up as part of their upgrade planning.
> > > >
> > > >
> > > >
> > > > I'm going to be getting bids from vendors on this, and I'd love to
> know
> > of
> > > > various and sundry gotchas, such as "7905 phones with an early
> serial
> > number
> > > > aren't supported on CCM 6.0" and things like that, so that I can
> know if
> > a
> > > > bidder has spotted and addressed potential problem areas.
> > > > _______________________________________________
> > > > 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
> > >
> >
> >
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
>