<div>So for those of us that will be upgrading to 6.x............ which is the better method? With or Without DNS. </div>
<div> </div>
<div>Thanks</div>
<div> </div>
<div>Scott<br><br></div>
<div class="gmail_quote">On Mon, Apr 7, 2008 at 6:31 AM, Ryan Ratliff <<a href="mailto:rratliff@cisco.com">rratliff@cisco.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">DNS is not required for CUCM. That said if you have configured a DNS<br>server it is required that the server be able to do a dns reverse<br>
lookup on itself and every other server in the cluster. So if<br>configure a DNS server during installation, DNS has to be operating<br>properly. If you don't configure a DNS server, then don't worry<br>about it as the hosts file on each server should get populated with<br>
IP address and hostname info during install.<br><br>Did you add the subscriber to System->Server on the pub before the<br>install? This is what allows the sub to talk to the pub's database,<br>etc. That error sure sounds like a connectivity issue.<br>
<font color="#888888"><br>-Ryan<br></font>
<div>
<div></div>
<div class="Wj3C7c"><br>On Apr 6, 2008, at 3:58 PM, Dave wrote:<br>I have run v6 before without DNS, and had no issues. I cannot locate<br>the documentation where DNS is a requirement. AFAIK, you just need<br>to change all IP addresses in the Enterprise Parameters to their IP<br>
addresses (Cisco's recommendation).<br><br>- original message -<br>Subject: Re: [cisco-voip] Subscriber refusing to join cluster<br>From: "Louis Koekemoer (ZA)" <<a href="mailto:Louis.Koekemoer@za.didata.com">Louis.Koekemoer@za.didata.com</a>><br>
Date: 04/06/2008 5:08 PM<br><br>Yip, the are on the same subnet, same 6500 switch. Publisher is x.x.x.<br>10 and subscriber x.x.x.11. I see Chris mentioned that DNS is<br>required in 6.x. I don't know if this is applicable to 5.x as well. I<br>
cannot remember that I had to do this the previous time I've done<br>this, but will give it a go as soon as I can.<br><br><br>Kind Regards<br><br>Louis Koekemoer<br>Cisco IPT Systems Engineer<br>Dimension Data South Africa<br>
+27 11 575 6560<br>+ +27 76 608 7221<br> <a href="mailto:louis.koekemoer@za.didata.com">louis.koekemoer@za.didata.com</a><br><br><br>-----Original Message-----<br>From: Jonathan Charles [mailto:<a href="mailto:jonvoip@gmail.com">jonvoip@gmail.com</a>]<br>
Sent: 06 April 2008 04:08 PM<br>To: Louis Koekemoer (ZA)<br>Cc: Frazee, Timothy; <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>Subject: Re: [cisco-voip] Subscriber refusing to join cluster<br>
<br>See, that part helps.<br><br>OK, are these two on the same subnet? Are they separated by a firewall?<br><br><br><br>Jonathan<br><br>On Sun, Apr 6, 2008 at 8:29 AM, Louis Koekemoer (ZA)<br><<a href="mailto:Louis.Koekemoer@za.didata.com">Louis.Koekemoer@za.didata.com</a>> wrote:<br>
> Sorry, I forgot to mention it is CCM5.1(3)<br>><br>><br>><br>> Kind Regards<br>><br>> Louis Koekemoer<br>> Cisco IPT Systems Engineer<br>> Dimension Data South Africa<br>> +27 11 575 6560<br>
> + +27 76 608 7221<br>> <a href="mailto:louis.koekemoer@za.didata.com">louis.koekemoer@za.didata.com</a><br>><br>><br>> -----Original Message-----<br>><br>> From: Frazee, Timothy [mailto:<a href="mailto:Timothy_Frazee@adp.com">Timothy_Frazee@adp.com</a>]<br>
> Sent: 06 April 2008 02:44 PM<br>> To: Louis Koekemoer (ZA); Jonathan Charles<br>> Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>><br>><br>> Subject: RE: [cisco-voip] Subscriber refusing to join cluster<br>
><br>> I think Jonathan meant to add and entry to either<br>> winnt/system32/drivers/etc/hosts or windows/system32/drivers/etc/<br>> hosts<br>><br>> Assuming you have a 3.x or 4.x server.<br>><br>> You didn't tell anyone what flavor of callmanager your working with.<br>
><br>><br>> -----Original Message-----<br>> From: <a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a><br>> [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>] On Behalf Of Louis<br>
> Koekemoer<br>> (ZA)<br>> Sent: Sunday, April 06, 2008 10:33 PM<br>> To: Jonathan Charles<br>> Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> Subject: Re: [cisco-voip] Subscriber refusing to join cluster<br>
><br>> Hi Jonathan,<br>><br>> But if the Subscriber is not fully installed, how can I add a<br>> hostname<br>> for Publisher on it? What I have done is on the Publisher I after the<br>> 2nd attempt, I removed subscriber totally, reloaded Publisher, and<br>
> added<br>> the subscriber on the hostname, and I also added another entry on<br>> the IP<br>> address. This obviously was also not successful. The thing is just<br>> that<br>> I have done this before, and it was so easy. I really suspect some<br>
> network or hardware issue here. I'm trying to locate another<br>> server to<br>> try and eliminate the server hardware as a possibility.<br>><br>><br>> Kind Regards<br>><br>> Louis Koekemoer<br>
> Cisco IPT Systems Engineer<br>> Dimension Data South Africa<br>> +27 11 575 6560<br>> + +27 76 608 7221<br>> <a href="mailto:louis.koekemoer@za.didata.com">louis.koekemoer@za.didata.com</a><br>><br>
> -----Original Message-----<br>> From: Jonathan Charles [mailto:<a href="mailto:jonvoip@gmail.com">jonvoip@gmail.com</a>]<br>> Sent: 06 April 2008 02:25 PM<br>> To: Louis Koekemoer (ZA)<br>> Cc: <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
> Subject: Re: [cisco-voip] Subsciber refusing to join cluster<br>><br>> Add a hosts entry on both to each other.<br>><br>><br>> Jonathan<br>><br>> On Sun, Apr 6, 2008 at 5:06 AM, Louis Koekemoer (ZA)<br>
> <<a href="mailto:Louis.Koekemoer@za.didata.com">Louis.Koekemoer@za.didata.com</a>> wrote:<br>>><br>>><br>>><br>>><br>>> I need help on adding a subscriber server to a cluster. I did create<br>
> the<br>>> subscriber on the Publisher, and after some time installing<br>> subscriber, at<br>>> the point of joining to Publisher I get the following message "The<br>>> configuration validation with ZAMDH06056 (xxx.xxx.xxx.xxx.) failed.<br>
> The<br>>> server could not send /receive UDP packets to the Publisher on port<br>> 8500. Is<br>>> network connection to ZADMH06056 up? Is the MTU size correct for this<br>>> network? Does the network allow packet fragments?" We can ping this<br>
> server<br>>> from the voice VLAN, and I can ping Subscriber IP from Publisher, so<br>> we<br>>> don't think we have network connectivity issues here.<br>>><br>>><br>>><br>>> Kind Regards<br>
>><br>>><br>>><br>>> Louis<br>>><br>>><br>>><br>>> This email and all contents are subject to the following disclaimer:<br>>><br>>> "<a href="http://www.dimensiondata.com/emaildisclaimer.htm" target="_blank">http://www.dimensiondata.com/emaildisclaimer.htm</a>"<br>
>> _______________________________________________<br>>> cisco-voip mailing list<br>>> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
>><br>>><br>> This email and all contents are subject to the following disclaimer:<br>><br>> "<a href="http://www.dimensiondata.com/emaildisclaimer.htm" target="_blank">http://www.dimensiondata.com/emaildisclaimer.htm</a>"<br>
> _______________________________________________<br>> cisco-voip mailing list<br>> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>> <a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
><br>><br>> This message and any attachments are intended only for the use of<br>> the addressee and may contain information that is privileged and<br>> confidential. If the reader of the message is not the intended<br>
> recipient or an authorized representative of the intended<br>> recipient, you are hereby notified that any dissemination of this<br>> communication is strictly prohibited. If you have received this<br>> communication in error, please notify us immediately by e-mail and<br>
> delete the message and any attachments from your system.<br>> This email and all contents are subject to the following disclaimer:<br>><br>> "<a href="http://www.dimensiondata.com/emaildisclaimer.htm" target="_blank">http://www.dimensiondata.com/emaildisclaimer.htm</a>"<br>
><br>This email and all contents are subject to the following disclaimer:<br><br>"<a href="http://www.dimensiondata.com/emaildisclaimer.htm" target="_blank">http://www.dimensiondata.com/emaildisclaimer.htm</a>"<br>
_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
<br>_______________________________________________<br>cisco-voip mailing list<br><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br><a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</div></div></blockquote></div><br>