On Sun, 18 Mar 2007, Rubens Kuhl Jr. wrote:
What open-source or low-budget tools are operators using for SLA
monitoring when the reports (current state and historical) should be
available to customers ?
Please define SLA in terms of monitoring.
- 99.x% availability (defined by packet
On Sun, 18 Mar 2007, virendra rode // wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
william(at)elan.net wrote:
On Sun, 18 Mar 2007, Rubens Kuhl Jr. wrote:
What open-source or low-budget tools are operators using for SLA
monitoring when the reports (current state and historical)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
william(at)elan.net wrote:
On Sun, 18 Mar 2007, virendra rode // wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
william(at)elan.net wrote:
On Sun, 18 Mar 2007, Rubens Kuhl Jr. wrote:
What open-source or low-budget tools are
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
william(at)elan.net
Sent: Monday, March 19, 2007 3:20 AM
To: virendra rode //
Cc: Rubens Kuhl Jr.; NANOG list
Subject: Re: SLA monitoring and reporting to customers
How is that part of SLA? Or do you mean
What open-source or low-budget tools are operators using for SLA
monitoring when the reports (current state and historical) should be
available to customers ?
Looking at NANOG archives, NAGIOS is the most prevalent tool, but its
authorization mechanisms are somewhat below I would like so
On Sun, 18 Mar 2007, Rubens Kuhl Jr. wrote:
What open-source or low-budget tools are operators using for SLA
monitoring when the reports (current state and historical) should be
available to customers ?
Please define SLA in terms of monitoring.
Looking at NANOG archives, NAGIOS is the
What open-source or low-budget tools are operators using for
SLA monitoring when the reports (current state and
historical) should be available to customers ?
Here is one way to do it on the cheap.
I have worked with Cricket and genDevConfig extensively. genDevConfig will
scan a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ray Burkholder wrote:
What open-source or low-budget tools are operators using for
SLA monitoring when the reports (current state and
historical) should be available to customers ?
Here is one way to do it on the cheap.
I have worked with
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
william(at)elan.net wrote:
On Sun, 18 Mar 2007, Rubens Kuhl Jr. wrote:
What open-source or low-budget tools are operators using for SLA
monitoring when the reports (current state and historical) should be
available to customers ?
Please
