[cisco-voip] building a new cluster from DMA (getting from point A to point B)

Wes Sisk wsisk at cisco.com
Mon Aug 9 14:48:29 EDT 2010


Inline, ws.

On Monday, August 09, 2010 9:53:54 AM, Lelio Fulgenzi 
<lelio at uoguelph.ca> wrote:
>
> I'm going through building a new cluster that I'd like to run 
> concurrently on my network with new IP addresses and CallManager 
> names. I have always used IP addresses and would like to continue 
> using IP addresses for now. I've installed 7.1(3a) along with a DMA 
> import. Then I applied 7.1(5) upgrade. No problems. I did this all in 
> an isolated switch with only the publisher and FTP server.
ws: make sure you provide it a valid NTP reference, espcially if this 
standalone will become a cluster.
>
> Can I just go into the servers, change the IP address, then go into 
> the CallManagers and change the names? Is it that simple? That way I 
> wouldn't have to bother messing around with CallPark numbers and 
> CallManager groups. If simply changing them is the answer should I 
> change one first?
>
> Once I confirm there is no communications happening from the new 
> publisher to the old cluster (via wireshark) I can then plug in the 
> publisher into the network and start installing new subscribers.
>
> This is what I have now:
>
> publisher hostname: iptccm105
> publisher ip addr: 10.104.91.105
>
> (during the install, the process asked me about changing the ip 
> address, but i can't recall if it asked me about changing the name, 
> but i think it did)
>
> The old/new information is below.
>
> ------------------------------------------------------------------------
> Servers:
>
> 10.104.20.101 (OLD) -> 10.104.91.104 (NEW)
> 10.104.20.103 (OLD) -> 10.104.91.103 (NEW)
> 10.104.91.105 (no change)
> 10.104.96.104 (OLD) -> 10.104.91.204 (NEW)
> 10.104.96.106 (OLD) -> 10.104.91.205 (NEW)
> 10.104.96.108 (OLD) -> 10.104.91.203 (NEW)
>
> _CallManagers:_
> uogccm101 (pointing to 10.104.20.101) -> iptccm104 (pointing to 
> 10.104.91.104)
> uogccm103 (pointing to 10.104.20.103) -> iptccm103 (pointing to 
> 10.104.91.103)
> uogccm104 (pointing to 10.104.96.104) -> iptccm204 (pointing to 
> 10.104.91.204)
> uogccm105 (pointing to 10.104.91.105) -> iptccm105 (pointing to 
> 10.104.91.105)
> uogccm106 (pointing to 10.104.96.106) -> iptccm205 (pointing to 
> 10.104.91.205)
> uogccm108 (pointing to 10.104.96.108) -> iptccm203 (pointing to 
> 10.104.91.203)
> ------------------------------------------------------------------------
>
>
> ws: Are you replacing the whole cluster or trying to replace just 
> individual nodes?  If you are replacing the whole cluster then you 
> just need follow the proper process to change server hostname and ip:
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/install/7_1_2/ipchange/ipchg712.html

If you are looking to replace certain nodes within the cluster then  you 
will need to reinstall and restore those nodes from backup. This is 
especially true if you are attempting to replace the publisher node in 
an existing cluster.

/Wes
>
> ---
> Lelio Fulgenzi, B.A.
> Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1
> (519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Cooking with unix is easy. You just sed it and forget it.
>                               - LFJ (with apologies to Mr. Popeil)
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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/20100809/742b985d/attachment.html>


More information about the cisco-voip mailing list