|
Home > Archive > Voice over IP Cisco > December 2007 > Upgrading from CCM4.0 to CCM6.0
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Upgrading from CCM4.0 to CCM6.0
|
|
| Tim Reimers 2007-12-10, 7:11 pm |
| 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.
| |
| Jonathan Charles 2007-12-10, 7:11 pm |
| 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@asheville.k12.nc.us> wrot=
e:
>
>
>
>
> Hi =96
>
>
>
> 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 =96 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 num=
ber
> 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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
| |
| Scott Voll 2007-12-11, 1:11 pm |
| 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@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@asheville.k12.nc.us>
> wrote:
> of
> number
> a
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
| |
| Jonathan Charles 2007-12-11, 1:11 pm |
| 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@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@gmail.com> wrote:
>
> wrote:
tem[vbcol=seagreen]
hones[vbcol=seagreen]
ils[vbcol=seagreen]
ow[vbcol=seagreen]
> of
> number
if[vbcol=seagreen]
> a
>
>
| |
| Ali, Aziz 2007-12-11, 1:11 pm |
| 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@puck.nether.net
[mailto:cisco-voip-bounces@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@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@gmail.com> wrote:
>
and[vbcol=seagreen]
<tim.reimers@asheville.k12.nc.us>[vbcol=seagreen]
> wrote:
system[vbcol=seagreen]
phones[vbcol=seagreen]
details[vbcol=seagreen]
know[vbcol=seagreen]
> of
serial[vbcol=seagreen]
> number
know if[vbcol=seagreen]
> a
>
>
________________________________________
_______
cisco-voip mailing list
cisco-voip@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 rec
ipient, 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.
| |
| Jonathan Charles 2007-12-11, 7:11 pm |
| 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@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@puck.nether.net
> [mailto:cisco-voip-bounces@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@gmail.com> wrote:
> into
> July
> so you
> version
> and
> <tim.reimers@asheville.k12.nc.us>
> system
> phones
> details
> know
> serial
> know if
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@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 r
ecipient, 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.
>
| |
| Tim Reimers 2007-12-11, 7:11 pm |
| We put "current stable version at install time"
I've also told vendors that THEY are responsible for checking all
configurations in our existing system to ensure what the upgrade path
is, etc.
Main thing I'm needing is to ensure that when I'm reading the bids, I
know who is doing the best job of checking IOS versions and quoting the
right upgrades, etc as needed.
________________________________
From: Scott Voll [mailto:svoll.voip@gmail.com]
Sent: Tuesday, December 11, 2007 11:33 AM
To: Jonathan Charles
Cc: Tim Reimers; cisco Voip Mailing list
Subject: Re: [cisco-voip] Upgrading from CCM4.0 to CCM6.0
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@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@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@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
| |
| Jonathan Charles 2007-12-11, 7:11 pm |
| Well, I have to recommend one thing, and it seems like a little one,
but I was shocked to find out that there are vendors who do not do
this....
Make sure that the partner that is doing the upgrade quotes you a
flat-rate and guarantees their work (we do), which means you may be
paying a little more, but if things go wrong, they will stay there as
long as it takes to get you up and running.
There is a vendor we compete with that quotes a flat-rate PLUS a max
hours, and if it goes over, they go into T&M mode.
Which means you can end up paying a LOT for their (or your) screw-ups...
An example, the upgrade I did this past weekend was quoted at 40 hours
(including staging), the staging took 50 hours by itself (nightmare
licensing issue with cisco that killed three days (the license caused
CER to crash))... and then the actual, on-site part took another 30
hours... so, the customer made out like a bandit, even though our
initial bid for those hours was probably more than our competitors
(who do not do straight flat-rate)... some of the problems were Cisco,
some were the customer (DNS and Exchange things) and some ours (we
misordered some software).
In the end, the customer had a working system.
Something to consider.
Jonathan
On Dec 11, 2007 2:43 PM, Tim Reimers <tim.reimers@asheville.k12.nc.us> wrot=
e:
>
>
>
>
> We put "current stable version at install time"
>
>
>
> I've also told vendors that THEY are responsible for checking all
> configurations in our existing system to ensure what the upgrade path is,
> etc.
>
>
>
> Main thing I'm needing is to ensure that when I'm reading the bids, I know
> who is doing the best job of checking IOS versions and quoting the right
> upgrades, etc as needed.
>
>
>
> ________________________________
>
>
> From: Scott Voll [mailto:svoll.voip@gmail.com]
> Sent: Tuesday, December 11, 2007 11:33 AM
> To: Jonathan Charles
> Cc: Tim Reimers; cisco Voip Mailing list
>
> Subject: Re: [cisco-voip] Upgrading from CCM4.0 to CCM6.0
>
>
>
>
>
>
> 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@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@asheville.k12.nc.us>
> wrote:
em[vbcol=seagreen]
ones[vbcol=seagreen]
ls[vbcol=seagreen]
> of
> number
if[vbcol=seagreen]
> a
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
|
|
|
|
|