On Sun, Nov 02, 2014 at 04:58:13PM +0100, Peter Nørlund wrote: > Hi, > > I have been working on adding SNMP support to BIRD through AgentX for a > while, but unfortunately I haven't had the necessary spare time the > last many month, so it is far from done. > > Lately we've experiencing scalability issues with out SNMP collector > at work, and I stumbled upon sFlow, which seemed a lot smarter and > simpler in may ways. > > This leads me to the question - if I were to add notifications and > statistical counters to protocols in BIRD, which way would then be the > preferred way for the community? And which counters/notifications do you > want?
Hi If i understand this correctly, there are several interwoven issues: 1) SNMP-like interface (pull-based) or just stream of counters (push-based) 1.1) Which variant of SNMP-based interface (AgentX, SMUX, raw SNMP, ...) 1.2) Which variant of stream-based interface (sFlow, IPFIX, ...) 2) What data/counters to export and how to represent it (standard MIB, BIRD specific) My comments to these questions: 1) I think that it could be useful to have both kinds of interfaces. SNMP-based interfaces could support traps and be compatible with SNMP tools while stream-based interfaces are simple enough to be easily integrated with other data-gathering tools. 1.1) I have no clue of advantages and prevalence of these. Having raw SNMP would be nice to be self-contained, but that is probably not so important. 1.2) Generally i would prefer self-explanatory streams (IPFIX with RFC 5102), but i have no experience with sFlow or IPFIX. 2) This is an interesting question. We already have several statistical counters in BIRD, but we could extend or modify it to cover some standard or well-established MIBs. Could you point me to some statistical data specifications (like SNMP MIBs or their relevant parts) that are relevant for BIRD? What is supported by other routing sofware/hardware? In short, i would prefer both your solution 1-3 and 6. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: [email protected]) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
signature.asc
Description: Digital signature
