[79571] in North American Network Operators' Group
Re: Maybe OT: MPLS QOS SLA Monitoring
daemon@ATHENA.MIT.EDU (Bill Nash)
Mon Apr 11 13:53:40 2005
Date: Mon, 11 Apr 2005 10:58:29 -0700 (PDT)
From: Bill Nash <billn@billn.net>
To: christian.macnevin@uk.bnpparibas.com
Cc: nanog@merit.edu
In-Reply-To: <OF72EB3F4E.7A3A80F4-ON80256FE0.004AB9E7@bnpparibas.com>
Errors-To: owner-nanog@merit.edu
On Mon, 11 Apr 2005 christian.macnevin@uk.bnpparibas.com wrote:
> I'm currently looking at what the possibilities are for monitoring network
> activity and SLAs against Cisco QOS mechanisms within VRFs. The most
> desirable method seems to be using NetFlow collectors, though it seems as
> though the benchmark for this is NetFlow 9, and I'm not sure if it's
> terribly well deployed on NetFlow collectors out there. Anyone know if it
> *is* well implemented for a given product? Or even if there's just a better
> way?
>
My knee jerk response was to suggest that flow-tools[1] can handle v9
output, but now that I look closer, it doesn't appear to. What you're
talking about wouldn't be *too* difficult to implement externally, you
just need some way to connect your SLA metrics to your aggregate flows for
violation checks.
If you're perl-ish, the flow-tools kit + dplonka's toys should give you
what you're after with some implementation fu.
- billn
[1] www.splintered.net/sw/flow-tools/
