[cisco-voip] Two Versions of CUCM

[Jason Roysdon]

However, once the old CUCM 6.x cluster goes offline (and none of the
CUCM servers in the XML file are available), and provided SRST is
disabled, the phones will give up and reset themselves.  At that time
they will not be able to reach TFTP1 and TFTP2 will be reached.  At the
time the phones will get the new cluster's CUCM XML file and switchover.

If you can prep your CUCM6.1 cluster with the same DevPack/phoneload as
7.x, the phones will swap over relatively fast as they won't have to
download anything newer than a small config file.  Of course, they'll
have to download a new phoneload from the old cluster, but this could be
scheduled on a previous maintenance window, and reduce the switchover
window.

For a more complicated, but more controlled cutover, and depending on
other items in your configuration, you could have new voice VLAN(s) for
the phones in the new cluster.  Then just move phones over from the old
voice VLAN to the new.  I don't think you'd really want to do this - my
original thought was you could have an intercluster-trunk between both
and the phones/gateways could still be configured to talk back and
forth, but this would only work if you configured complicated CFwdUR or
some other method, with the idea that no matter the cluster you could
talk back and forth.  Probably more mess and problems than it is worth
trying to solve.

You could also test out a few phones with the new cluster before downing
the old cluster by giving them a static DHCP lease with different a
different TFTP1 value, or just manually assign it via the phone Settings
interface.

Jorge L. Rodriguez Aguila wrote:
> No, They are two separate clusters and so this will not work, The Phones
> when coming up go to their first TFTP and only if they Fail to find it
> go to TFTP server 2. Once they hit TFTP 1 that phone receives an XML
> file which tells him the CCM server list which will obviously not
> include servers from the other cluster.
> 
>  
> 
>  
> 
> Jorge Rodríguez Aguila
> 
> CCNA,CCVP,CRMCS,CIPCES
> 
> Senior Voice/Data Network Consultant
> 
> Netxar Technologies
> 
> jorge.rodriguez at netxar.com
> 
> Office 787-765-0058
> 
> PCS 787-688-8530
> 
> netxar
> 
>  
> 
>  
> 
>  
> 
> *From:* cisco-voip-bounces at puck.nether.net
> [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf Of *Mike Louis
> *Sent:* Monday, November 10, 2008 9:04 AM
> *To:* cisco-voip at puck.nether.net
> *Subject:* [cisco-voip] Two Versions of CUCM
> 
>  
> 
> Hello All,
> 
>  
> 
> If I have a call manager cluster running 6.x and a cluster running 7.x
> and I configure the TFTP server addresses in the DHCP scopes to be
> servers in each cluster, making 6.x primary and 7.x secondary, will the
> phones register with both servers? I would like to use this as a
> migration process to 7.x but I am not sure if it would work. Any thoughts?
> 
>  
> 
>  
> 
>  
> 
> ------------------------------------------------------------------------
> 
> Note: This message and any attachments is intended solely for the use of
> the individual or entity to which it is addressed and may contain
> information that is non-public, proprietary, legally privileged,
> confidential, and/or exempt from disclosure. If you are not the intended
> recipient, you are hereby notified that any use, dissemination,
> distribution, or copying of this communication is strictly prohibited.
> If you have received this communication in error, please notify the
> original sender immediately by telephone or return email and destroy or
> delete this message along with any attachments immediately.
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip