Sounds like they need to through in MRTG and go red when the traffic is high on the link.
And then throw in things like
bb-ospf.pl to check that ospf is not flapping over the link
bb-xsnmp.pl to check out the routers at each end and the interfaces
you can also use http to a reliable server on the remote side as part of the link test. Just make the http test for the link dependent on the router and the conn test to the web server.
From: Charles Jones [mailto:jonescr at cisco.com] Sent: Friday, January 13, 2006 1:01 PM To: hobbit at hswn.dk Cc: crimson at technologist.com Subject: [hobbit] conn alerts based on ping time
I'm helping someone set up Hobbit at their company, and they want to monitor the status of a remote office T1 link. Of course Hobbit can tell them if the link goes totally down, or you can ignore bad pings with "badconn", but they want to know when the link is slow, as they often have periods of time when the pings are not dropped, but instead taking 1-3 seconds (instead of <100ms like normal).
Is there any chance that Hobbit will soon support comparing the ping replies to specifiied values for green, yellow, and red?
Somethign like:
1.2.3.4 myhost.com # conn:200:500
This would make myhost.com's conn test go yellow if the ping was between 200 and 500ms, and red if it was over 500ms. Since hobbit already graphs the numeric values of the ping replies, this seems like it would be fairly easy to add?
-Charles