<!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 text="#000000" bgcolor="#ffffff">
ccmadmin->system->server<br>
<br>
change the names to the correct IP's and reboot.<br>
<br>
These names also determine how the IDS database engine comes up. If
you update them it is critical to update them to the correct value.
There is no validation in the page. The administrator is the
validator.<br>
<br>
Regards,<br>
Wes<br>
<br>
On 4/1/2011 2:48 AM, Anthony Kouloglou wrote:
<blockquote cite="mid:4D957539.6070407@dataways.gr" type="cite">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
Hi, i have a cluster with 2 CUCMs 7.1.5 and they are defined by
name.<br>
What is the safer way/sequence to change their names into their
current IPs? (so no IP change is needed)<br>
I want to do that so remote sites will not have the need of a DNS
to resolve their names.<br>
If dns is not used and in the remote dhcp is configured to provide
the 2 IPs of Publisher and Subscriber, devices such as 69XX and
7931 will put only the publisher as the active CUCM and not the
subscriber even though their is IP connectivity!!<br>
So i guess, if i use the 2 nodes with their IPs, none of these
problems will exist.<span style="font-size: 10pt; color: silver;"
lang="EN-US"><br>
<br>
Cheers<br>
Anthony</span><span style="font-size: 12pt; font-family:
"Times New Roman","serif";" lang="EN-US"><o:p></o:p></span>
<div class="moz-signature">
<div class="Section1"> </div>
</div>
<pre wrap="">
<fieldset class="mimeAttachmentHeader"></fieldset>
_______________________________________________
cisco-voip mailing list
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</pre>
</blockquote>
</body>
</html>