[cisco-voip] publisher unavailable

[Wes Sisk]

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.

/Wes

Charles Goldsmith wrote:
> 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.
>
> Thanks for the input
> Charles
>
> On Wed, Aug 25, 2010 at 7:10 AM, Wes Sisk <wsisk at cisco.com 
> <mailto:wsisk at cisco.com>> wrote:
>
>     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.
>
>     /Wes
>
>     Charles Goldsmith wrote:
>>     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).
>>
>>     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.
>>
>>     Is this normal behavior?
>>
>>     Thanks
>>     Charles
>>     ------------------------------------------------------------------------
>>     _______________________________________________ cisco-voip
>>     mailing list cisco-voip at puck.nether.net
>>     <mailto: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/20100825/c98ce415/attachment.html>