[167118] in North American Network Operators' Group
Re: Is there a method or tool(s) to prove network outages?
daemon@ATHENA.MIT.EDU (George William Herbert)
Sun Dec 1 15:11:23 2013
In-Reply-To: <20131201195031.GG14268@hezmatt.org>
From: George William Herbert <george.herbert@gmail.com>
Date: Sun, 1 Dec 2013 12:10:33 -0800
To: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Dec 1, 2013, at 11:50 AM, Matt Palmer <mpalmer@hezmatt.org> wrote:
> I'm surprised nobody's mentioned the root question to answer before you go=
> off spending time setting up anything in particular: what *will* the ISP
> accept (or be forced to accept) as outage/instability proof? Contracts ar=
e
> your first line of defence, but it's nigh-on universal that they don't cov=
er
> these sorts of situations well enough. So you probably need to have a
> discussion, as a follow-on from being told that your UTM's e-mails *aren't=
*
> sufficient, to determine what *is* sufficient.
This.
They may not cooperate, in which case, you have to force proof down their t=
hroats.
I would go with the Zenoss (or Zabbix, or...) option - a free to use, profes=
sionally supported, professional grade commonly used monitoring package that=
would meet anyone's basic "credible tool" definition plus neat GUI to send a=
snapshot of the results.
Use it to perform various tests of the net - pings, http gets of some small t=
arget, starting pings with the next hop outside your premise and working out=
wards to the outside world. Don't overwhelm your net with tests, but test a=
s often as needed to demonstrate an issue.
-george william herbert
george.herbert@gmail.com
Sent from Kangphone=
