[cisco-voip] RE: CCM Upgrade from 3.3(3) to 4.1 (Mourits, Leo)

Tue Dec 21 10:54:26 EST 2004

I think you will have to upgrade to 4.0 first if you want it to be TAC supported. Anyway, one important thing to remember is that any upgrade from 3.3.x to 4.x changes a lot of things, sometimes in a way that you would not expect. For example, I had a setup with voicemail profiles, different Unity servers in one cluster and different voice pilot numbers. This configuration was totally screwed up after upgrade and needed a lot of manual fixing.

I would not go and upgrade to 4.1 directly if it is not supported.

Regards,
Leo

-----Original Message-----
From: cisco-voip-request at puck.nether.net [mailto:cisco-voip-request at puck.nether.net] 
Sent: Tuesday, December 21, 2004 4:18 PM
To: cisco-voip at puck.nether.net
Subject: cisco-voip Digest, Vol 22, Issue 52

Send cisco-voip mailing list submissions to
	cisco-voip at puck.nether.net

To subscribe or unsubscribe via the World Wide Web, visit
	https://puck.nether.net/mailman/listinfo/cisco-voip
or, via email, send a message with subject or body 'help' to
	cisco-voip-request at puck.nether.net

You can reach the person managing the list at
	cisco-voip-owner at puck.nether.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of cisco-voip digest..."

Today's Topics:

   1. CCM Upgrade from 3.3(3) to 4.1 (Kasturi, Shrenik)
   2. RE: CCM Upgrade from 3.3(3) to 4.1 (King, Jesse)
   3. lab  guide (Marcin Nowacki)
   4. Re: CCM Upgrade from 3.3(3) to 4.1 (Lelio Fulgenzi)
   5. RE: CCM Upgrade from 3.3(3) to 4.1 (Watson, Craig)

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

Message: 1
Date: Tue, 21 Dec 2004 08:43:43 -0500
From: "Kasturi, Shrenik" <Shrenik.Kasturi at gs.com>
Subject: [cisco-voip] CCM Upgrade from 3.3(3) to 4.1
To: "'cisco-voip at puck.nether.net'" <cisco-voip at puck.nether.net>
Message-ID:
	<B0AD405A5CF4C9479FB52279C6EE68300380F40F at gsnmp36es.ny.fw.gs.com>
Content-Type: text/plain; charset="us-ascii"

Has any one successfully upgraded CCM from 3.3(3) to 4.1?  I read somewhere
that this upgrade path hasn't been tested and only upgrades from 3.3(4) and
later are supported, has anyone attempted this?

Thanks,

SK
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20041221/bce0ffbc/attachment-0001.html

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

Message: 2
Date: Tue, 21 Dec 2004 08:51:14 -0500
From: "King, Jesse" <JKing at thegranitegroup.com>
Subject: RE: [cisco-voip] CCM Upgrade from 3.3(3) to 4.1
To: "'Kasturi, Shrenik'" <Shrenik.Kasturi at gs.com>,
	"'cisco-voip at puck.nether.net'" <cisco-voip at puck.nether.net>
Message-ID:
	<6F18BEEC743DD411B2B900508B69063902233602 at thegranitegroup.com>
Content-Type: text/plain; charset="iso-8859-1"

I have, but I did 3.3.(3), to 4.0(2), to 4.1.... Painful but this way it is
supported....

-----Original Message-----
From: Kasturi, Shrenik [mailto:Shrenik.Kasturi at gs.com]
Sent: Tuesday, December 21, 2004 8:44 AM
To: 'cisco-voip at puck.nether.net'
Subject: [cisco-voip] CCM Upgrade from 3.3(3) to 4.1

Has any one successfully upgraded CCM from 3.3(3) to 4.1?  I read somewhere
that this upgrade path hasn't been tested and only upgrades from 3.3(4) and
later are supported, has anyone attempted this?

Thanks, 

SK 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20041221/79a8e28b/attachment-0001.html

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

Message: 3
Date: Tue, 21 Dec 2004 14:49:47 +0100
From: "Marcin Nowacki" <Marcin_Nowacki at sevenet.pl>
Subject: [cisco-voip] lab  guide
To: <cisco-voip at puck.nether.net>
Message-ID:
	<AF7AA9F0562A514FBB1FEF74A53971B41712FD at serwer11.sevenet.local>
Content-Type: text/plain; charset="iso-8859-2"

Hello 

Does anyone have an experience with workbooks  preparing to CCIE Voice Lab egzam ? Could you propose some ? IPExpert or Hello Computers books ?

I would be glad for any information .

Greetings

Marcin

***********************************************************************

Systemy Sieciowe SEVENET Sp. z o.o.

Marcin Nowacki

tel. +58 3400414, 600490308; fax. +58 3400401

e-mail: marcin_nowacki <BLOCKED::mailto:marcin_nowacki at sevenet.pl> @sevenet.pl

***********************************************************************

Zawarto¶æ tej wiadmo¶ci zawiera informacje zastrze¿one, stanowi±ce tajemnicê firmy Systemy Sieciowe SEVENET sp. z o.o. Nieuprawnione wykorzystanie tych informacji do w³asnych celów lub ich ujawnianie osobom trzecim jest zabronione. W przypadku omy³kowego otrzymania tej wiadomo¶ci prosimy o jej trwa³e skasowanie oraz powiadomienie o tym fakcie nadawcy informacji.

This e-mail content contains confidential information, and is the property of Systemy Sieciowe SEVENET sp. z o.o. Any illegal use of this information for personal purposes or any disclosure to other persons or entities is prohibited. If you are not the intended recipient of this message please delete this e-mail and inform the sender about it.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20041221/87329092/attachment-0001.html

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

Message: 4
Date: Tue, 21 Dec 2004 09:06:40 -0500
From: "Lelio Fulgenzi" <lelio at uoguelph.ca>
Subject: Re: [cisco-voip] CCM Upgrade from 3.3(3) to 4.1
To: <cisco-voip at puck.nether.net>
Message-ID: <00a901c4e766$4b53cc80$ef196883 at Dellicious>
Content-Type: text/plain; charset="iso-8859-1"

CCM Upgrade from 3.3(3) to 4.1We're in the same boat. I'm going to discuss with my SE and some others about TAC support with an upgrade from 3.3(3) to 4.1(2) directly. I don't understand how they expect people to upgrade from 3.3(4) and not 3.3(3) when they specifically told people 3.3(4) and 4.x were different trains and that upgrades may be difficult. Maybe not in all those words, but the content of the message was the same. Being the holidays, this is one of the first things I will look at in the new year.

  ----- Original Message ----- 
  From: Kasturi, Shrenik 
  To: 'cisco-voip at puck.nether.net' 
  Sent: Tuesday, December 21, 2004 8:43 AM
  Subject: [cisco-voip] CCM Upgrade from 3.3(3) to 4.1

  Has any one successfully upgraded CCM from 3.3(3) to 4.1?  I read somewhere that this upgrade path hasn't been tested and only upgrades from 3.3(4) and later are supported, has anyone attempted this?

  Thanks, 

  SK 

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

  _______________________________________________
  cisco-voip mailing list
  cisco-voip at puck.nether.net
  https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20041221/1d7d9c44/attachment-0001.html

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

Message: 5
Date: Tue, 21 Dec 2004 09:17:23 -0600
From: "Watson, Craig" <Craig.Watson at CommerceBank.com>
Subject: RE: [cisco-voip] CCM Upgrade from 3.3(3) to 4.1
To: "Lelio Fulgenzi" <lelio at uoguelph.ca>, <cisco-voip at puck.nether.net>
Message-ID:
	<A965E0D8AD05FF4487E19C242C9AFA0701669057 at kc-exc4.cbsh.com>
Content-Type: text/plain; charset="iso-8859-1"

Currently, in order to upgrade from 3.3 to 4.1, you have to first upgrade to 4.0 and then take the executeable and upgrade to 4.1.  Cisco should be coming out with a way to upgrade from 3.3 sometime next quarter, but for now, the only way to get to 4.1 is to upgrade to 4.0 first.

Craig

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net]On Behalf Of Lelio Fulgenzi
Sent: Tuesday, December 21, 2004 8:07 AM
To: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CCM Upgrade from 3.3(3) to 4.1

We're in the same boat. I'm going to discuss with my SE and some others about TAC support with an upgrade from 3.3(3) to 4.1(2) directly. I don't understand how they expect people to upgrade from 3.3(4) and not 3.3(3) when they specifically told people 3.3(4) and 4.x were different trains and that upgrades may be difficult. Maybe not in all those words, but the content of the message was the same. Being the holidays, this is one of the first things I will look at in the new year.

----- Original Message ----- 
From: Kasturi, Shrenik <mailto:Shrenik.Kasturi at gs.com>  
To: 'cisco-voip at puck.nether.net' 
Sent: Tuesday, December 21, 2004 8:43 AM
Subject: [cisco-voip] CCM Upgrade from 3.3(3) to 4.1

Has any one successfully upgraded CCM from 3.3(3) to 4.1?  I read somewhere that this upgrade path hasn't been tested and only upgrades from 3.3(4) and later are supported, has anyone attempted this?

Thanks, 

SK 

  _____  

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

***********************************************************************
NOTICE:  This electronic mail message and any attached files are 
confidential.  The information is exclusively for the use of the 
individual or entity intended as the recipient.  If you are not the 
intended recipient, any use, copying, printing, reviewing, retention, 
disclosure, distribution or forwarding of the message or any attached 
file is not authorized and is strictly prohibited.  If you have received 
this electronic mail message in error, please advise the sender by reply 
electronic mail immediately and permanently delete the original 
transmission, any attachments and any copies of this message from your 
computer system.
***********************************************************************
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20041221/0df68c0e/attachment.html

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

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

End of cisco-voip Digest, Vol 22, Issue 52
******************************************