(no subject)

[Rob Nelson]

>There is no VPN involved as our network is only private circuits. As for a 
>route, that would not explain why I could telnet to the device, but not 
>ping. The problem is very specific to ICMP. As well, having another 
>machine on the same switch being able to ping the device indicates it is 
>not related to the network, but more specifically to the Nagios server. 
>I'm only running a default gateway with no routing protocols and no static 
>routes. I've checked the routes on the device before and after the problem 
>and the do not change. It is a very wierd problem.

Yes, but on this other host, were you pinging the machine before it went 
down? It could be anything from an arp bridge table holding bad information 
across a link recycle to screwed up ICMP access-lists. If you can duplicate 
the before-and-after picture entirely, then I'd guess on the machine, but 
not until you have another machine pinging the same device before, during, 
and after the link goes up and down.

How is this device connected? Most of my hosts are something like:

remote node -> [wireless eq] -> PIX firewall <- VPN -> central PIX firewall 
-> monitoring server

If the node goes down and reconnects on a different wireless unit, we were 
having some problems because someone set the entire site's equipment to use 
a bridge learn timeout of 700 minutes. Possibly something similar?


|Rob Nelson
Network Administrator, Capitol Broadband
C: 919-369-1874
rob at capband.net 



-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null