<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Inline again, ws.<br>
<br>
On Monday, August 09, 2010 3:32:40 PM, Lelio Fulgenzi
<a class="moz-txt-link-rfc2396E" href="mailto:lelio@uoguelph.ca"><lelio@uoguelph.ca></a> wrote:<br>
<blockquote
cite="mid:1317199537.158467.1281382360660.JavaMail.root@simcoe.cs.uoguelph.ca"
type="cite">
<style type="text/css">p { margin: 0; }</style>
<div
style="font-family: Verdana; font-size: 10pt; color: rgb(0, 0, 0);">Thanks
Wes.<br>
<br>
I installed the publisher without an NTP source (it sync'ed to the
hardware clock) and then when I tried to install a subscriber it
choked, said it couldn't contact the NTP server on the publisher. I
tried reconfiguring NTP on the publisher to the local switch, but I
don't think it liked it.</div>
</blockquote>
ws: not likely, CM needs a stratum 3(?) or better source. See SRND.
Configuring stratum on router/switch is undesirable as NTP process will
monitor clock drift.<br>
<blockquote
cite="mid:1317199537.158467.1281382360660.JavaMail.root@simcoe.cs.uoguelph.ca"
type="cite">
<div
style="font-family: Verdana; font-size: 10pt; color: rgb(0, 0, 0);">
Anyways, the subscriber installed terminated abruptly after I said
retry.<br>
<br>
I'm not sure how to make the publisher believe the switch is a valid
NTP source. Any clues? I don't have to reinstall the publisher do I?<br>
</div>
</blockquote>
ws: you can definitely add one from CLI. you may be able to do it from
platform web pages. Just give it a valid NTP reference. You can
restart NTP to expedite the sync. Use 'utils ntp status' and make sure
you're not seeing '*127.127.1.0' as this indicates you're still using
the internal clock.<br>
<blockquote
cite="mid:1317199537.158467.1281382360660.JavaMail.root@simcoe.cs.uoguelph.ca"
type="cite">
<div
style="font-family: Verdana; font-size: 10pt; color: rgb(0, 0, 0);"><br>
Regarding, the cluster itself...everything is new hardware - pub and
subs. The steps you point to refer to changing the IP address on the
subscribers, but they don't exist yet. This leads me to believe that
changing the IP addresses on the publisher is sufficient, then I begin
re-installing the subscribers with the new IP addresses.<br>
</div>
</blockquote>
ws: Yep! Just re-ip your publisher. change it under system->server
and then from CLI/platform. Then reboot. After that install subs.<br>
<blockquote
cite="mid:1317199537.158467.1281382360660.JavaMail.root@simcoe.cs.uoguelph.ca"
type="cite">
<div
style="font-family: Verdana; font-size: 10pt; color: rgb(0, 0, 0);"><br>
Perhaps it will just be easier once the publisher is built and the IP
addresses are changed, to move it back to the production network,
configure a valid NTP source and start building the subscribers after
that?<br>
</div>
</blockquote>
ws: just need valid NTP source so clocks get in sync before database
tries to replicate.<br>
<blockquote
cite="mid:1317199537.158467.1281382360660.JavaMail.root@simcoe.cs.uoguelph.ca"
type="cite">
<div
style="font-family: Verdana; font-size: 10pt; color: rgb(0, 0, 0);"><br>
<br>
<br>
<span><br>
<span name="x"></span>---<br>
Lelio Fulgenzi, B.A.<br>
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
Cooking with unix is easy. You just sed it and forget it. <br>
- LFJ (with apologies to Mr. Popeil)<br>
<span name="x"></span><br>
</span><br>
<hr id="zwchr"><b>From: </b>"Wes Sisk" <a class="moz-txt-link-rfc2396E" href="mailto:wsisk@cisco.com"><wsisk@cisco.com></a><br>
<b>To: </b>"Lelio Fulgenzi" <a class="moz-txt-link-rfc2396E" href="mailto:lelio@uoguelph.ca"><lelio@uoguelph.ca></a><br>
<b>Cc: </b>"voyp list" <a class="moz-txt-link-rfc2396E" href="mailto:cisco-voip@puck.nether.net"><cisco-voip@puck.nether.net></a><br>
<b>Sent: </b>Monday, August 9, 2010 2:48:29 PM<br>
<b>Subject: </b>Re: [cisco-voip] building a new cluster from DMA
(getting from point A to point B)<br>
<br>
<title></title>
Inline, ws.<br>
<br>
On Monday, August 09, 2010 9:53:54 AM, Lelio Fulgenzi
<a moz-do-not-send="true" class="moz-txt-link-rfc2396E"
href="mailto:lelio@uoguelph.ca" target="_blank"><lelio@uoguelph.ca></a>
wrote:<br>
<blockquote
cite="mid:448537915.144564.1281362034422.JavaMail.root@simcoe.cs.uoguelph.ca">
<style>p { margin: 0; }</style>
<div
style="font-family: Verdana; font-size: 10pt; color: rgb(0, 0, 0);"><br>
I'm <span>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. <br>
</span></div>
</blockquote>
ws: make sure you provide it a valid NTP reference, espcially if this
standalone will become a cluster.<br>
<blockquote
cite="mid:448537915.144564.1281362034422.JavaMail.root@simcoe.cs.uoguelph.ca">
<div
style="font-family: Verdana; font-size: 10pt; color: rgb(0, 0, 0);"><span><br>
</span><span id="7cfbb40c-a4b1-4204-bd00-d872375142d4">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?<br>
</span><br>
<span id="7cfbb40c-a4b1-4204-bd00-d872375142d4">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.<br>
<br>
</span><span id="7cfbb40c-a4b1-4204-bd00-d872375142d4">This is what
I
have now:<br>
<br>
publisher hostname: iptccm105<br>
publisher ip addr: 10.104.91.105<br>
<br>
(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)<br>
<br>
The old/new information is below. <br>
<br>
</span>
<div style="margin-left: 40px;"><span
id="7cfbb40c-a4b1-4204-bd00-d872375142d4"></span>
<hr style="width: 100%; height: 2px;"><span
style="text-decoration: underline;"
id="7cfbb40c-a4b1-4204-bd00-d872375142d4">Servers:</span><br>
<br>
<span id="7cfbb40c-a4b1-4204-bd00-d872375142d4"></span><span
id="7cfbb40c-a4b1-4204-bd00-d872375142d4">10.104.20.101 (OLD) ->
10.104.91.104 (NEW)</span><br>
<span id="7cfbb40c-a4b1-4204-bd00-d872375142d4">10.104.20.103 (OLD)
-> 10.104.91.103</span> (NEW)<br>
10.104.91.105 (no change)<br>
10.104.96.104 (OLD) -> 10.104.91.204 (NEW)<br>
10.104.96.106 (OLD) -> 10.104.91.205 (NEW)<br>
10.104.96.108 (OLD) -> 10.104.91.203 (NEW)<br>
<br>
<u>CallManagers:</u><br>
uogccm101 (pointing to 10.104.20.101) -> iptccm104 (pointing to
10.104.91.104)<br>
uogccm103 (pointing to 10.104.20.103) -> iptccm103 (pointing to
10.104.91.103)<br>
uogccm104 (pointing to 10.104.96.104) -> iptccm204 (pointing to
10.104.91.204)<br>
uogccm105 (pointing to 10.104.91.105) -> iptccm105 (pointing to
10.104.91.105)<br>
uogccm106 (pointing to 10.104.96.106) -> iptccm205 (pointing to
10.104.91.205)<br>
uogccm108 (pointing to 10.104.96.108) -> iptccm203 (pointing to
10.104.91.203)</div>
<div style="margin-left: 40px;">
<hr style="width: 100%; height: 2px;"><br>
</div>
<br>
<span id="7cfbb40c-a4b1-4204-bd00-d872375142d4">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:<br>
</span></div>
</blockquote>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/install/7_1_2/ipchange/ipchg712.html"
target="_blank">http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/install/7_1_2/ipchange/ipchg712.html</a><br>
<br>
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.<br>
<br>
/Wes<br>
<blockquote
cite="mid:448537915.144564.1281362034422.JavaMail.root@simcoe.cs.uoguelph.ca">
<div
style="font-family: Verdana; font-size: 10pt; color: rgb(0, 0, 0);"><span
id="7cfbb40c-a4b1-4204-bd00-d872375142d4"><br>
<span></span>---<br>
Lelio Fulgenzi, B.A.<br>
Senior Analyst (CCS) * University of Guelph * Guelph, Ontario N1G 2W1<br>
(519) 824-4120 x56354 (519) 767-1060 FAX (JNHN)<br>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<br>
Cooking with unix is easy. You just sed it and forget it. <br>
- LFJ (with apologies to Mr. Popeil)<br>
<span></span><br>
</span><br>
</div>
<pre><hr size="4" width="90%">
_______________________________________________
cisco-voip mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated"
href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext"
href="https://puck.nether.net/mailman/listinfo/cisco-voip"
target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
<br>
</div>
</blockquote>
<br>
</body>
</html>