[cisco-voip] Advice on CCM3 to CCM4 Migration please

[Hering, Marc]

Ditto, cept we go for 90 days...(Far too many of us remember NT4.0 Sp6
(and then 6a :) )
 
<M>

________________________________

From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
Sent: Monday, January 24, 2005 2:27 PM
To: Simon Hamilton-Wilkes; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] Advice on CCM3 to CCM4 Migration please


We have an unwritten rule that we won't run/install anything unless it's
been out for 30 days. Far too many last minute software pulls and
service releases.

	----- Original Message ----- 
	From: Simon Hamilton-Wilkes <mailto:simon at jettis.com>  
	To: cisco-voip at puck.nether.net 
	Sent: Monday, January 24, 2005 1:19 PM
	Subject: RE: [cisco-voip] Advice on CCM3 to CCM4 Migration
please

	While we're on this topic, I notice 3.3.5 has been posted.  Does
this affect CCM 4.1 migration in any way?

________________________________

	From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Lelio Fulgenzi
	Sent: Monday, January 24, 2005 10:08 AM
	To: chris donnelly; cisco-voip at puck.nether.net
	Subject: Re: [cisco-voip] Advice on CCM3 to CCM4 Migration
please
	
	
	It is my hope that I will be able to do something similar when
testing out new versions of Call Manager, basically mimicing all route
patterns etc on the new server and have a few phones testing things live
and interacting with the production service.
	 
	However, I think it's quite an ordeal to migrate things piece
meal. Test as much as you can, then upgrade the cluster. Be sure to have
plenty of outs, i.e. backup and mirrored disks. We have new hardware and
will be building the new publisher exactly as you mentioned. If you
don't have new hardware, you should be able to take your publisher
off-line during the upgrade and then plug it back in when you are done.
Obviously database changes can't happen during that time and will affect
things like call forwarding.
	 
	I think we have to begin letting our clients know that we have
to upgrade and there will be changes seen. Many we will be able to
document, but many may slip by our fingers because of lack of change
documentation (sorry Cisco).
	 
	For your notes, you will have to do a two stage upgrade, from
3.3(3) -> 3.3(4) or 4.0(x) -> 4.1(2). We are choosing to go to 3.3(4) as
our interim step.

		----- Original Message ----- 
		From: chris donnelly
<mailto:c.donnelly at skynetsystems.co.uk>  
		To: cisco-voip at puck.nether.net 
		Sent: Monday, January 24, 2005 4:57 AM
		Subject: [cisco-voip] Advice on CCM3 to CCM4 Migration
please


		Hi, 
		
		Hopefully one of you guys have been through this and can
recommend the most painless way forward.... 
		
		We have a customer who currently has an old 3.3.3 CCM
Cluster with about 2000 phones hanging of it. 
		
		They need to go to CCM 4.x and want to prove the
environment / product first by staging the new CCM 4 and then gradually
moving users from the old cluster to the new cluster. The downside of
this is that it is not a straightforward upgrade / replacement as the
two clusters will live side by side for a while. 
		
		I have no problem with this apart from the sheer numbers
involved. My initial thought was to use the BAT tool to import all data
from the production cluster to the CCM4 cluster - but that still leaves
me loads of stuff to cross-pollinate i.e. Route patterns, partitions
etc...etc... 
		
		My second thought is to build the CCM4 cluster from the
Upgrade 'Replace Server' option whilst building -but that forces me to
use the old CCM3's machine name etc so the two clusters cannot live side
by side....unless there is a way to build the CCM cluster by the
'Upgrade Replace Server' option and then rename the machine name and
change IP addresses etc... 
		
		BTW I know everyone says that you cannot change machine
names because of SQL (but has anyone actually tried this?) - there are
snippets of info available on the web detailing how to change SQL
machine names. 
		
		Any advice gratefully received. 
		
		Chris

		
________________________________


		

		_______________________________________________
		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
	

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