An update on this issue, name resolution and host files are correct per the reporting tool. See <a href="http://imgur.com/x78BT">http://imgur.com/x78BT</a> Utils diagnose didn't show anything that could be causing a problem either.<div>
<br></div><div>I'll open a TAC case on this tomorrow. </div><div><br></div><div>I also found an NTP issue while running utils diagnose, the test showed that the cluster didn't like the NTP servers I was using, being at stratum 5 or higher fails the test. I've changed my NTP servers, but that didn't resolve this issue.<div>
<br></div><div>I'm open to other thoughts on it.</div><div><br></div><div>Charles<br><br><div class="gmail_quote">On Wed, Aug 25, 2010 at 12:30 PM, Wes Sisk <span dir="ltr"><<a href="mailto:wsisk@cisco.com">wsisk@cisco.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#ffffff" text="#000000">
Even with "IP" there is internal configuration on CM that depends on
names. At install time servers attempt DNS to resolve name<->ip
to populate hosts files. Net, there is still dependence on name
resolution even internal to the server.<br><font color="#888888">
<br>
/Wes</font><div><div></div><div class="h5"><br>
<br>
Charles Goldsmith wrote:
<blockquote style="border:medium none ! important;padding-left:0px ! important;padding-right:0px ! important;margin-left:0px ! important;margin-right:0px ! important" type="cite">I'm not using DNS in my cluster and everything is set to
IP. My network is back online now, but I'll schedule and outage and do
some more testing.
<div><br>
</div>
<div>Thanks for the input</div>
<div>Charles<br>
<br>
<div class="gmail_quote">On Wed, Aug 25, 2010 at 7:10 AM, Wes Sisk <span dir="ltr"><<a href="mailto:wsisk@cisco.com" target="_blank">wsisk@cisco.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex">
<div bgcolor="#ffffff" text="#000000">Doesn't sound normal. Sounds
like something may be wrong with hosts
files so CM is resolving the name to wrong IP. There are checks in
Cisco Unified Reporting Tool to help identify problems with host
resolution and DNS. There is also 'utils diagnose' from the CLI.<br>
<br>
/Wes<br>
<br>
Charles Goldsmith wrote:
<blockquote style="border:medium none ! important;padding-left:0px ! important;padding-right:0px ! important;margin-left:0px ! important;margin-right:0px ! important" type="cite">
<div>
<div>During a loss of network connectivity between my
publisher
and subscriber, I cannot login to my publisher, it just sits at the
login screen "waiting for dfw-cm1" in the status bar forever. Running
version 8.0.2(40000).<br>
<br>
And I know its obvious, but yes, I can ping and have full network
access to my publisher, I'm on the same network as it, it's the side
with my subscriber that is down.<br>
<br>
Is this normal behavior?<br>
<br>
Thanks<br>
Charles<br>
</div>
</div>
<pre><hr size="4" width="90%"><div>
_______________________________________________
cisco-voip mailing list
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a>
</div></pre>
</blockquote>
</div>
</blockquote>
</div>
<br>
</div>
</blockquote>
</div></div></div>
</blockquote></div><br></div></div>