Mailing List Archive

Hi Marc,

Your procedure looks good. I performed this upgrade several months ago with no problems. Just be sure to watch your callmanger backup as it runs and look for any errors.

Having a good backup is the key.

Once you have your publisher up and running, the subscriber is a snap.
----- Original Message -----
From: Hering, Marc
To: cisco-voip@puck.nether.net
Sent: Thursday, July 01, 2004 10:03 AM
Subject: [cisco-voip] CCM Upgrade 3.2 to 3.3 questions..


Hey everyone,
I am getting ready to upgrade my CCM installation from 3.2(3) to 3.3(4). As far as I can tell, the steps for the Publisher should be as follows:

1.. Install Backup utility 3.5.53,
2.. Backup complete config using backup utility
3.. Check backup by verifying that the following files exist
1.. Dbname.ini
2.. Backup.ini
3.. Mcs.sti
4.. Copy all files generated during backup to another server and burn to CD
5.. Install and run upgrade assistant utility to verify server health
6.. Resolve any and all issues prior to continuing
7.. Remove a drive and replace with blank mirror drive. Wait for mirror to rebuild.
8.. REInstall OS using same server recovery method
9.. Update to OS 2.6
10.. Install OS 2.6 Sr1 patch
11.. Install Call manager version 3.3.4 and restore data from backup
12.. Perform clean backup of database
13.. Proceed to Subscriber upgrade
Is there anything I have missed or anything I should watch out for, I have never done this before so I am understandibly being overcautious.

Thanks

Marc Hering

Network Engineer

The Gale Company

100 Campus Drive

Suite 200

Florham Park, NJ 07932

Direct: 973.301.8209

Fax: 973.245.3605

www.thegalecompany.com


The Gale Company is one of the largest real estate companies in the industry with a global portfolio exceeding 60 million square feet of office space. For more information contact 973-301-9500 or visit www.TheGaleCompany.com



------------------------------------------------------------------------------


_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

We did a similar upgrade, and we decided to split the OS upgrades and the Call Manager upgrades into two seperate maintenance windows. We have a total of 6 servers to upgrade, so splitting the upgrades was great for us. I'm not sure what you mean by step #11, restore from backup - the CCM upgrade did not wipe out any of our data, so we did not have to restore from backup - things were working after the upgrade.

Something you have to be aware of is the signed loads of the phones. 3.3.3 and after has signed images - once a phone has a signed load, it can not go back to an unsigned load. We made sure to upgrade a few phones in our test centre to signed loads and put them back on our production network to see that they operated properly. We tested a few applications on the phone as well as ICD/IPCC express. You should throughly test any applications you are using.

It's also important to know that Cisco does not guarentee or support call managers in a cluster running different versions - they actually strongly recommend against it. We witnessed that phones registered to call managers with different versions were not able to communicate to each other - not even ringing through. That's another reason we chose to seperate the OS and CCM upgrades - to minimize the actual time that phones were not able to talk to each other. You could further minimize the service interruption by changing the device pools so all phones use the same call manager subscriber temporarily.

Regarding signed loads, we were surprised to see that even though the backup call manager of a phone was not yet upgraded, when we took the primary call manager down for upgrading, the phone communicated to the publisher and actually upgraded itself with the signed load.

I think those were the major points - other than that - we were quite surprised how easy the upgrade went.

Oh yeah - if you have a CCO contract, you can open a TAC case in preparation and in advance of your upgrade. We did so under advisement from our SE and it was great - immediate attention with all your background already discussed with the engineer.

Lelio

----- Original Message -----
From: Hering, Marc
To: cisco-voip@puck.nether.net
Sent: Thursday, July 01, 2004 10:03 AM
Subject: [cisco-voip] CCM Upgrade 3.2 to 3.3 questions..


Hey everyone,
I am getting ready to upgrade my CCM installation from 3.2(3) to 3.3(4). As far as I can tell, the steps for the Publisher should be as follows:

1.. Install Backup utility 3.5.53,
2.. Backup complete config using backup utility
3.. Check backup by verifying that the following files exist
1.. Dbname.ini
2.. Backup.ini
3.. Mcs.sti
4.. Copy all files generated during backup to another server and burn to CD
5.. Install and run upgrade assistant utility to verify server health
6.. Resolve any and all issues prior to continuing
7.. Remove a drive and replace with blank mirror drive. Wait for mirror to rebuild.
8.. REInstall OS using same server recovery method
9.. Update to OS 2.6
10.. Install OS 2.6 Sr1 patch
11.. Install Call manager version 3.3.4 and restore data from backup
12.. Perform clean backup of database
13.. Proceed to Subscriber upgrade
Is there anything I have missed or anything I should watch out for, I have never done this before so I am understandibly being overcautious.

Thanks

Marc Hering

Network Engineer

The Gale Company

100 Campus Drive

Suite 200

Florham Park, NJ 07932

Direct: 973.301.8209

Fax: 973.245.3605

www.thegalecompany.com


The Gale Company is one of the largest real estate companies in the industry with a global portfolio exceeding 60 million square feet of office space. For more information contact 973-301-9500 or visit www.TheGaleCompany.com



----------------------------------------------------------------------------


_______________________________________________
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

Hmmmm....I suppose then that the below caution from cisco is no longer true?

Caution Reader, be careful. You may do something that could result in equipment damage or loss of data.
For Cisco CallManager 3.1/3.2 Upgrades to 3.3(4)

You must perform a same server recovery by using the operating system disks that ship with this version of Cisco CallManager to install operating system version 2000.2.4 before you upgrade to 2000.2.5sr2. You cannot upgrade to Cisco-provided operating system version 2000.2.5sr2 (or later) from a previous version of the operating system. For detailed instructions, refer to "Upgrading From

Cisco CallManager 3.1 or 3.2 (If You Are Not Replacing Hardware)" section.

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_2/install/install/cm323ins.htm


----- Original Message -----

From: Lelio Fulgenzi
To: cisco-voip@puck.nether.net
Sent: Thursday, July 01, 2004 11:13 AM
Subject: Re: [cisco-voip] CCM Upgrade 3.2 to 3.3 questions..


We did a similar upgrade, and we decided to split the OS upgrades and the Call Manager upgrades into two seperate maintenance windows. We have a total of 6 servers to upgrade, so splitting the upgrades was great for us. I'm not sure what you mean by step #11, restore from backup - the CCM upgrade did not wipe out any of our data, so we did not have to restore from backup - things were working after the upgrade.

Something you have to be aware of is the signed loads of the phones. 3.3.3 and after has signed images - once a phone has a signed load, it can not go back to an unsigned load. We made sure to upgrade a few phones in our test centre to signed loads and put them back on our production network to see that they operated properly. We tested a few applications on the phone as well as ICD/IPCC express. You should throughly test any applications you are using.

It's also important to know that Cisco does not guarentee or support call managers in a cluster running different versions - they actually strongly recommend against it. We witnessed that phones registered to call managers with different versions were not able to communicate to each other - not even ringing through. That's another reason we chose to seperate the OS and CCM upgrades - to minimize the actual time that phones were not able to talk to each other. You could further minimize the service interruption by changing the device pools so all phones use the same call manager subscriber temporarily.

Regarding signed loads, we were surprised to see that even though the backup call manager of a phone was not yet upgraded, when we took the primary call manager down for upgrading, the phone communicated to the publisher and actually upgraded itself with the signed load.

I think those were the major points - other than that - we were quite surprised how easy the upgrade went.

Oh yeah - if you have a CCO contract, you can open a TAC case in preparation and in advance of your upgrade. We did so under advisement from our SE and it was great - immediate attention with all your background already discussed with the engineer.

Lelio

----- Original Message -----
From: Hering, Marc
To: cisco-voip@puck.nether.net
Sent: Thursday, July 01, 2004 10:03 AM
Subject: [cisco-voip] CCM Upgrade 3.2 to 3.3 questions..


Hey everyone,
I am getting ready to upgrade my CCM installation from 3.2(3) to 3.3(4). As far as I can tell, the steps for the Publisher should be as follows:

1.. Install Backup utility 3.5.53,
2.. Backup complete config using backup utility
3.. Check backup by verifying that the following files exist
1.. Dbname.ini
2.. Backup.ini
3.. Mcs.sti
4.. Copy all files generated during backup to another server and burn to CD
5.. Install and run upgrade assistant utility to verify server health
6.. Resolve any and all issues prior to continuing
7.. Remove a drive and replace with blank mirror drive. Wait for mirror to rebuild.
8.. REInstall OS using same server recovery method
9.. Update to OS 2.6
10.. Install OS 2.6 Sr1 patch
11.. Install Call manager version 3.3.4 and restore data from backup
12.. Perform clean backup of database
13.. Proceed to Subscriber upgrade
Is there anything I have missed or anything I should watch out for, I have never done this before so I am understandibly being overcautious.

Thanks

Marc Hering

Network Engineer

The Gale Company

100 Campus Drive

Suite 200

Florham Park, NJ 07932

Direct: 973.301.8209

Fax: 973.245.3605

www.thegalecompany.com


The Gale Company is one of the largest real estate companies in the industry with a global portfolio exceeding 60 million square feet of office space. For more information contact 973-301-9500 or visit www.TheGaleCompany.com



--------------------------------------------------------------------------


_______________________________________________
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



------------------------------------------------------------------------------


_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Nope, it is not really a conversion. This is a fresh install. If you
follow instructions, it wipes your entire server clean and reinstalls
everything from scratch.
Thus the purpose of performing a backup and restore of data.

However, someone previously describes a way to upgrade, though i am not
familiar with it.


----- Original Message -----
From: "Anthony Mendoza" <amendoza@Niku.com>
To: <gea@ufl.edu>
Sent: Thursday, July 01, 2004 1:45 PM
Subject: Re: [cisco-voip] CCM Upgrade 3.2 to 3.3 questions..



Thanks. For some reason I was told that the sql7 to sql2k conversion itself
took multiple hours.
--
Anthony Mendoza
Senior Infrastructure Manager
t: 650-298-5955
c: 510-579-1909
f: 208-247-5501
e: amendoza@niku.com

-----Original Message-----
From: Greg Ayoub <gea@ufl.edu>
To: Anthony Mendoza <amendoza@Niku.com>
Sent: Thu Jul 01 10:38:07 2004
Subject: Re: [cisco-voip] CCM Upgrade 3.2 to 3.3 questions..

The publisher is the big one, takes a little under 2 hours. As long as your
pub/sub SQL links come back, each subscriber take a little less than 1 hour.

----- Original Message -----
From: "Anthony Mendoza" <amendoza@Niku.com>
To: "Greg Ayoub" <gea@ufl.edu>
Sent: Thursday, July 01, 2004 12:42 PM
Subject: Re: [cisco-voip] CCM Upgrade 3.2 to 3.3 questions..


>
> How long does this process take? I've heard anywhere from 4-6+ hours..
> --
> Anthony Mendoza
>
>
> On 7/1/2004 7:47 AM, Greg Ayoub wrote:
> > Hi Marc,
> >
> > Your procedure looks good. I performed this upgrade several months ago
with no problems. Just be sure to watch your callmanger backup as it runs
and look for any errors.
> >
> > Having a good backup is the key.
> >
> > Once you have your publisher up and running, the subscriber is a snap.
> >
> > ----- Original Message -----
> > From: Hering, Marc <mailto:MHering@TheGaleCompany.com>
> > To: cisco-voip@puck.nether.net
> > Sent: Thursday, July 01, 2004 10:03 AM
> > Subject: [cisco-voip] CCM Upgrade 3.2 to 3.3 questions..
> >
> > Hey everyone,
> > I am getting ready to upgrade my CCM installation from 3.2(3) to 3.3(4).
As far as I can tell, the steps for the Publisher should be as follows:
> >
> >
> >
> > 1. Install Backup utility 3.5.53,
> >
> > 2. Backup complete config using backup utility
> >
> > 3. Check backup by verifying that the following files exist
> >
> >
> > a. Dbname.ini
> >
> > b. Backup.ini
> >
> > c. Mcs.sti
> >
> > 4. Copy all files generated during backup to another server and burn to
CD
> >
> > 5. Install and run upgrade assistant utility to verify server health
> >
> > 6. Resolve any and all issues prior to continuing
> >
> > 7. Remove a drive and replace with blank mirror drive. Wait for mirror
to rebuild.
> >
> > 8. REInstall OS using same server recovery method
> >
> > 9. Update to OS 2.6
> >
> > 10. Install OS 2.6 Sr1 patch
> >
> > 11. Install Call manager version 3.3.4 and restore data from backup
> >
> > 12. Perform clean backup of database
> >
> > 13. Proceed to Subscriber upgrade
> >
> > Is there anything I have missed or anything I should watch out for, I
have never done this before so I am understandibly being overcautious.
> >
> > Thanks
> >
> >
> > Marc Hering
> >
> > Network Engineer
> >
> > The Gale Company
> >
> > 100 Campus Drive
> >
> > Suite 200
> >
> > Florham Park, NJ 07932
> >
> > Direct: 973.301.8209
> >
> > Fax: 973.245.3605
> >
> > www.thegalecompany.com <http://www.thegalecompany.com/>
> >
> >
> > The Gale Company is one of the largest real estate companies in the
industry with a global portfolio exceeding 60 million square feet of office
space. For more information contact 973-301-9500 or visit
www.TheGaleCompany.com <http://www.thegalecompany.com/>
> >
> >
> >
> >
> > _____
> >
> >
> >
> >
> > _______________________________________________
> > 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
>
> CONFIDENTIALITY NOTICE: The information contained in this message and
> or attachments is intended only for the person or entity to which it
> is addressed and may contain confidential and/or privileged material.
> Any review, retransmission, dissemination, copying, or other use of
> this information by persons or entities other than the intended
> recipient is prohibited. If you received this e-mail or its
> attachments in error, please contact the sender and delete the
> material from any system and destroy any copies.
>
>



CONFIDENTIALITY NOTICE: The information contained in this message and
or attachments is intended only for the person or entity to which it
is addressed and may contain confidential and/or privileged material.
Any review, retransmission, dissemination, copying, or other use of
this information by persons or entities other than the intended
recipient is prohibited. If you received this e-mail or its
attachments in error, please contact the sender and delete the
material from any system and destroy any copies.

Let me confirm with my colleague - I honestly don't remember that part! We were upgrading from 3.3(2) spB so I don't think we required that step.

----- Original Message -----
From: Greg Ayoub
To: cisco-voip@puck.nether.net
Sent: Thursday, July 01, 2004 1:36 PM
Subject: Re: [cisco-voip] CCM Upgrade 3.2 to 3.3 questions..


Hmmmm....I suppose then that the below caution from cisco is no longer true?

Caution Reader, be careful. You may do something that could result in equipment damage or loss of data.
For Cisco CallManager 3.1/3.2 Upgrades to 3.3(4)

You must perform a same server recovery by using the operating system disks that ship with this version of Cisco CallManager to install operating system version 2000.2.4 before you upgrade to 2000.2.5sr2. You cannot upgrade to Cisco-provided operating system version 2000.2.5sr2 (or later) from a previous version of the operating system. For detailed instructions, refer to "Upgrading >From

Cisco CallManager 3.1 or 3.2 (If You Are Not Replacing Hardware)" section.

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_2/install/install/cm323ins.htm


----- Original Message -----

From: Lelio Fulgenzi
To: cisco-voip@puck.nether.net
Sent: Thursday, July 01, 2004 11:13 AM
Subject: Re: [cisco-voip] CCM Upgrade 3.2 to 3.3 questions..


We did a similar upgrade, and we decided to split the OS upgrades and the Call Manager upgrades into two seperate maintenance windows. We have a total of 6 servers to upgrade, so splitting the upgrades was great for us. I'm not sure what you mean by step #11, restore from backup - the CCM upgrade did not wipe out any of our data, so we did not have to restore from backup - things were working after the upgrade.

Something you have to be aware of is the signed loads of the phones. 3.3.3 and after has signed images - once a phone has a signed load, it can not go back to an unsigned load. We made sure to upgrade a few phones in our test centre to signed loads and put them back on our production network to see that they operated properly. We tested a few applications on the phone as well as ICD/IPCC express. You should throughly test any applications you are using.

It's also important to know that Cisco does not guarentee or support call managers in a cluster running different versions - they actually strongly recommend against it. We witnessed that phones registered to call managers with different versions were not able to communicate to each other - not even ringing through. That's another reason we chose to seperate the OS and CCM upgrades - to minimize the actual time that phones were not able to talk to each other. You could further minimize the service interruption by changing the device pools so all phones use the same call manager subscriber temporarily.

Regarding signed loads, we were surprised to see that even though the backup call manager of a phone was not yet upgraded, when we took the primary call manager down for upgrading, the phone communicated to the publisher and actually upgraded itself with the signed load.

I think those were the major points - other than that - we were quite surprised how easy the upgrade went.

Oh yeah - if you have a CCO contract, you can open a TAC case in preparation and in advance of your upgrade. We did so under advisement from our SE and it was great - immediate attention with all your background already discussed with the engineer.

Lelio

----- Original Message -----
From: Hering, Marc
To: cisco-voip@puck.nether.net
Sent: Thursday, July 01, 2004 10:03 AM
Subject: [cisco-voip] CCM Upgrade 3.2 to 3.3 questions..


Hey everyone,
I am getting ready to upgrade my CCM installation from 3.2(3) to 3.3(4). As far as I can tell, the steps for the Publisher should be as follows:

1.. Install Backup utility 3.5.53,
2.. Backup complete config using backup utility
3.. Check backup by verifying that the following files exist
1.. Dbname.ini
2.. Backup.ini
3.. Mcs.sti
4.. Copy all files generated during backup to another server and burn to CD
5.. Install and run upgrade assistant utility to verify server health
6.. Resolve any and all issues prior to continuing
7.. Remove a drive and replace with blank mirror drive. Wait for mirror to rebuild.
8.. REInstall OS using same server recovery method
9.. Update to OS 2.6
10.. Install OS 2.6 Sr1 patch
11.. Install Call manager version 3.3.4 and restore data from backup
12.. Perform clean backup of database
13.. Proceed to Subscriber upgrade
Is there anything I have missed or anything I should watch out for, I have never done this before so I am understandibly being overcautious.

Thanks

Marc Hering

Network Engineer

The Gale Company

100 Campus Drive

Suite 200

Florham Park, NJ 07932

Direct: 973.301.8209

Fax: 973.245.3605

www.thegalecompany.com


The Gale Company is one of the largest real estate companies in the industry with a global portfolio exceeding 60 million square feet of office space. For more information contact 973-301-9500 or visit www.TheGaleCompany.com



------------------------------------------------------------------------


_______________________________________________
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



----------------------------------------------------------------------------


_______________________________________________
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

CallManager 3.2 used SQL 7, and CallManager 3.3 - 4.0 uses SQL 2000, so this is considered a rebuild and restore. You cannot (via Cisco's instructions) upgrade this, it is a rebuild. I have done this in a test environment as well as on an existing Production 4 server cluster and your steps are correct! Make sure for the Subscriber you follow it's install path as well, there are specific instructions and files the subscriber uses that make your job easier (pulls all the IP info etc automatially).

Good Luck!

JD
----- Original Message -----
From: Lelio Fulgenzi<mailto:lelio@uoguelph.ca>
To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Sent: Thursday, July 01, 2004 11:57 AM
Subject: Re: [cisco-voip] CCM Upgrade 3.2 to 3.3 questions..


Let me confirm with my colleague - I honestly don't remember that part! We were upgrading from 3.3(2) spB so I don't think we required that step.

----- Original Message -----
From: Greg Ayoub<mailto:gea@ufl.edu>
To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Sent: Thursday, July 01, 2004 1:36 PM
Subject: Re: [cisco-voip] CCM Upgrade 3.2 to 3.3 questions..


Hmmmm....I suppose then that the below caution from cisco is no longer true?

Caution Reader, be careful. You may do something that could result in equipment damage or loss of data.
For Cisco CallManager 3.1/3.2 Upgrades to 3.3(4)

You must perform a same server recovery by using the operating system disks that ship with this version of Cisco CallManager to install operating system version 2000.2.4 before you upgrade to 2000.2.5sr2. You cannot upgrade to Cisco-provided operating system version 2000.2.5sr2 (or later) from a previous version of the operating system. For detailed instructions, refer to "Upgrading >From <http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_3/install/upgrade/upgra334.htm#wp162154>

Cisco CallManager 3.1 or 3.2 (If You Are Not Replacing Hardware)" section.

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_2/install/install/cm323ins.htm<http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_2/install/install/cm323ins.htm>


----- Original Message -----

From: Lelio Fulgenzi<mailto:lelio@uoguelph.ca>
To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Sent: Thursday, July 01, 2004 11:13 AM
Subject: Re: [cisco-voip] CCM Upgrade 3.2 to 3.3 questions..


We did a similar upgrade, and we decided to split the OS upgrades and the Call Manager upgrades into two seperate maintenance windows. We have a total of 6 servers to upgrade, so splitting the upgrades was great for us. I'm not sure what you mean by step #11, restore from backup - the CCM upgrade did not wipe out any of our data, so we did not have to restore from backup - things were working after the upgrade.

Something you have to be aware of is the signed loads of the phones. 3.3.3 and after has signed images - once a phone has a signed load, it can not go back to an unsigned load. We made sure to upgrade a few phones in our test centre to signed loads and put them back on our production network to see that they operated properly. We tested a few applications on the phone as well as ICD/IPCC express. You should throughly test any applications you are using.

It's also important to know that Cisco does not guarentee or support call managers in a cluster running different versions - they actually strongly recommend against it. We witnessed that phones registered to call managers with different versions were not able to communicate to each other - not even ringing through. That's another reason we chose to seperate the OS and CCM upgrades - to minimize the actual time that phones were not able to talk to each other. You could further minimize the service interruption by changing the device pools so all phones use the same call manager subscriber temporarily.

Regarding signed loads, we were surprised to see that even though the backup call manager of a phone was not yet upgraded, when we took the primary call manager down for upgrading, the phone communicated to the publisher and actually upgraded itself with the signed load.

I think those were the major points - other than that - we were quite surprised how easy the upgrade went.

Oh yeah - if you have a CCO contract, you can open a TAC case in preparation and in advance of your upgrade. We did so under advisement from our SE and it was great - immediate attention with all your background already discussed with the engineer.

Lelio

----- Original Message -----
From: Hering, Marc<mailto:MHering@TheGaleCompany.com>
To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Sent: Thursday, July 01, 2004 10:03 AM
Subject: [cisco-voip] CCM Upgrade 3.2 to 3.3 questions..


Hey everyone,
I am getting ready to upgrade my CCM installation from 3.2(3) to 3.3(4). As far as I can tell, the steps for the Publisher should be as follows:

1.. Install Backup utility 3.5.53,
2.. Backup complete config using backup utility
3.. Check backup by verifying that the following files exist
1.. Dbname.ini
2.. Backup.ini
3.. Mcs.sti
4.. Copy all files generated during backup to another server and burn to CD
5.. Install and run upgrade assistant utility to verify server health
6.. Resolve any and all issues prior to continuing
7.. Remove a drive and replace with blank mirror drive. Wait for mirror to rebuild.
8.. REInstall OS using same server recovery method
9.. Update to OS 2.6
10.. Install OS 2.6 Sr1 patch
11.. Install Call manager version 3.3.4 and restore data from backup
12.. Perform clean backup of database
13.. Proceed to Subscriber upgrade
Is there anything I have missed or anything I should watch out for, I have never done this before so I am understandibly being overcautious.

Thanks

Marc Hering

Network Engineer

The Gale Company

100 Campus Drive

Suite 200

Florham Park, NJ 07932

Direct: 973.301.8209

Fax: 973.245.3605

www.thegalecompany.com<http://www.thegalecompany.com/>


The Gale Company is one of the largest real estate companies in the industry with a global portfolio exceeding 60 million square feet of office space. For more information contact 973-301-9500 or visit www.TheGaleCompany.com<http://www.thegalecompany.com/>



----------------------------------------------------------------------


_______________________________________________
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



--------------------------------------------------------------------------


_______________________________________________
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

_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Confirmed - no restore required for upgrade from 3.3(2) to 3.3(3). Sorry for adding any confusion.

----- Original Message -----
From: Lelio Fulgenzi
To: cisco-voip@puck.nether.net
Sent: Thursday, July 01, 2004 1:57 PM
Subject: Re: [cisco-voip] CCM Upgrade 3.2 to 3.3 questions..


Let me confirm with my colleague - I honestly don't remember that part! We were upgrading from 3.3(2) spB so I don't think we required that step.

----- Original Message -----
From: Greg Ayoub
To: cisco-voip@puck.nether.net
Sent: Thursday, July 01, 2004 1:36 PM
Subject: Re: [cisco-voip] CCM Upgrade 3.2 to 3.3 questions..


Hmmmm....I suppose then that the below caution from cisco is no longer true?

Caution Reader, be careful. You may do something that could result in equipment damage or loss of data.
For Cisco CallManager 3.1/3.2 Upgrades to 3.3(4)

You must perform a same server recovery by using the operating system disks that ship with this version of Cisco CallManager to install operating system version 2000.2.4 before you upgrade to 2000.2.5sr2. You cannot upgrade to Cisco-provided operating system version 2000.2.5sr2 (or later) from a previous version of the operating system. For detailed instructions, refer to "Upgrading >From

Cisco CallManager 3.1 or 3.2 (If You Are Not Replacing Hardware)" section.

http://www.cisco.com/univercd/cc/td/doc/product/voice/c_callmg/3_2/install/install/cm323ins.htm


----- Original Message -----

From: Lelio Fulgenzi
To: cisco-voip@puck.nether.net
Sent: Thursday, July 01, 2004 11:13 AM
Subject: Re: [cisco-voip] CCM Upgrade 3.2 to 3.3 questions..


We did a similar upgrade, and we decided to split the OS upgrades and the Call Manager upgrades into two seperate maintenance windows. We have a total of 6 servers to upgrade, so splitting the upgrades was great for us. I'm not sure what you mean by step #11, restore from backup - the CCM upgrade did not wipe out any of our data, so we did not have to restore from backup - things were working after the upgrade.

Something you have to be aware of is the signed loads of the phones. 3.3.3 and after has signed images - once a phone has a signed load, it can not go back to an unsigned load. We made sure to upgrade a few phones in our test centre to signed loads and put them back on our production network to see that they operated properly. We tested a few applications on the phone as well as ICD/IPCC express. You should throughly test any applications you are using.

It's also important to know that Cisco does not guarentee or support call managers in a cluster running different versions - they actually strongly recommend against it. We witnessed that phones registered to call managers with different versions were not able to communicate to each other - not even ringing through. That's another reason we chose to seperate the OS and CCM upgrades - to minimize the actual time that phones were not able to talk to each other. You could further minimize the service interruption by changing the device pools so all phones use the same call manager subscriber temporarily.

Regarding signed loads, we were surprised to see that even though the backup call manager of a phone was not yet upgraded, when we took the primary call manager down for upgrading, the phone communicated to the publisher and actually upgraded itself with the signed load.

I think those were the major points - other than that - we were quite surprised how easy the upgrade went.

Oh yeah - if you have a CCO contract, you can open a TAC case in preparation and in advance of your upgrade. We did so under advisement from our SE and it was great - immediate attention with all your background already discussed with the engineer.

Lelio

----- Original Message -----
From: Hering, Marc
To: cisco-voip@puck.nether.net
Sent: Thursday, July 01, 2004 10:03 AM
Subject: [cisco-voip] CCM Upgrade 3.2 to 3.3 questions..


Hey everyone,
I am getting ready to upgrade my CCM installation from 3.2(3) to 3.3(4). As far as I can tell, the steps for the Publisher should be as follows:

1.. Install Backup utility 3.5.53,
2.. Backup complete config using backup utility
3.. Check backup by verifying that the following files exist
1.. Dbname.ini
2.. Backup.ini
3.. Mcs.sti
4.. Copy all files generated during backup to another server and burn to CD
5.. Install and run upgrade assistant utility to verify server health
6.. Resolve any and all issues prior to continuing
7.. Remove a drive and replace with blank mirror drive. Wait for mirror to rebuild.
8.. REInstall OS using same server recovery method
9.. Update to OS 2.6
10.. Install OS 2.6 Sr1 patch
11.. Install Call manager version 3.3.4 and restore data from backup
12.. Perform clean backup of database
13.. Proceed to Subscriber upgrade
Is there anything I have missed or anything I should watch out for, I have never done this before so I am understandibly being overcautious.

Thanks

Marc Hering

Network Engineer

The Gale Company

100 Campus Drive

Suite 200

Florham Park, NJ 07932

Direct: 973.301.8209

Fax: 973.245.3605

www.thegalecompany.com


The Gale Company is one of the largest real estate companies in the industry with a global portfolio exceeding 60 million square feet of office space. For more information contact 973-301-9500 or visit www.TheGaleCompany.com



----------------------------------------------------------------------


_______________________________________________
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



--------------------------------------------------------------------------


_______________________________________________
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