> - Ping/Trace Tools: ping or a trace to any interface with an ip address.
This could be very useful if we do it right. Keep in mind that trace could spend a lot of time if something is down in the middle of the path (waiting the timeout). Typically, when the monitoring system/LAN has issue, the entire wall will be painted red and every things are slowed. Of cause, if the ping/trace find out where is the problem, jffnms can stop polling/pinging the rest 2000 interfaces and wasting time simply to wait timeouts. Here is what I did before (simplified): 1) create a list of IPs and did a trace on them (daily or weekly, depends on the size of the list/need), which in turn build a list of <IP, previous IP>s 2) fping the IPs, -> IP success list and IP failed list. 3) skips IP that have its previous IP in the IP failed list. and alert the remaining IPs in the failed list. (I did another trace on this limited list to pin point where the ping stopped) 4) clear previous alarms if they are in the IP success list. Some people may argue that there could be more than one paths to an IP and above scheme may not accurately reflect the network. But it never failed me. Min ------------------------------------------------------- This SF.net email is sponsored by Demarc: A global provider of Threat Management Solutions. Download our HomeAdmin security software for free today! http://www.demarc.com/info/Sentarus/hamr30 _______________________________________________ jffnms-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jffnms-users
