Re: [Idr] BGP MIB v2 input
Pekka Savola <pekkas@netcore.fi> Mon, 26 March 2007 05:41 UTC
Return-path: <idr-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HVhx7-0002iN-Bs; Mon, 26 Mar 2007 01:41:09 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HVhx6-0002h6-Jp for idr@ietf.org; Mon, 26 Mar 2007 01:41:08 -0400
Received: from eunet-gw.ipv6.netcore.fi ([2001:670:86:3001::1] helo=netcore.fi) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HVhx5-0000Uy-0n for idr@ietf.org; Mon, 26 Mar 2007 01:41:08 -0400
Received: from localhost (pekkas@localhost) by netcore.fi (8.12.11.20060614/8.12.11) with ESMTP id l2Q5eeTG020674 for <idr@ietf.org>; Mon, 26 Mar 2007 08:40:41 +0300
Date: Mon, 26 Mar 2007 08:40:40 +0300
From: Pekka Savola <pekkas@netcore.fi>
To: idr@ietf.org
Subject: Re: [Idr] BGP MIB v2 input
In-Reply-To: <200703260450.l2Q4obpc001219@bright.research.att.com>
Message-ID: <Pine.LNX.4.64.0703260810390.20059@netcore.fi>
References: <6F44D7F6B24A8F4DA0AB46C9BE924F0209F07D6F@VS4.EXCHPROD.USA.NET> <17921.18878.834053.856771@limmat.switch.ch> <200703260450.l2Q4obpc001219@bright.research.att.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Virus-Scanned: ClamAV 0.90.1/2924/Sun Mar 25 15:56:14 2007 on otso.netcore.fi
X-Virus-Status: Clean
X-Spam-Status: No, score=0.1 required=5.0 tests=NO_RELAYS, TW_JN autolearn=failed version=3.1.8
X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on otso.netcore.fi
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
Errors-To: idr-bounces@ietf.org
On Mon, 26 Mar 2007, Bill Fenner wrote: > It may be worth breaking this down into areas of limitation of the > current MIB: > 1. v6 peer support > 2. v6 and other NLRI support > 3. 4-byte AS support > 4. extra counters desired > (Others?) .. As I mentioned at the mike, I believe the counters for prefixes rejected by policy (whether this also includes AS-path loops, invalid next-hops etc. doesn't matter to me) apart from those that are accepted by policy but not necessarily the preferred ones right now. This can be used for monitoring how well BGP prefix filters etc. are functioning. As a bonus, it'd be nice to be able to see which prefixes are stuck in the inbound policy filter, but that's not mandatory. Support for reporting information on IPv6 peers and non-IPv4 NLRIs would also be very welcome. ... Below is some information about what some implementations do: Juniper reports the following support on their web page (which we are already using) for JunOS: ==8<== Internet draft draft-ietf-idr-bgp4-mibv2-04.txt, Definitions of Managed Objects for the Fourth Version of Border Gateway Protocol (BGP-4), Second Version (only the objects jnxBgpM2PrefixInPrefixes, jnxBgpM2PrefixInPrefixesAccepted, and jnxBgpM2PrefixInPrefixesRejected) ==8<== [Note: they actually support slightly more than that, e.g., most or all of peer-status objects, but for example not dumping all the BGP routes using SNMP.] With the MIB at: http://www.juniper.net/techpubs/software/junos/junos82/swconfig82-net-mgmt/html/mib-jnx-bgpmib2.txt Note: Juniper's current implementation of BgpM2PrefixInPrefixesRejected is broken as it counts all non-active routes instead of those rejected by policy. Surfing around a bit, Cisco IOS XR 3.4 at least claims to support draft-ietf-idr-bgp4-mibv2-05.txt (though under 'BGP Next Hop Tracking enhancements' so I suspect they don't implement the full MIB either). In some other software trains, Cisco also seems to support some of the features of the new BGP mib, such as the number of 'received routes' but not the whole MIB as such: http://www.cisco.com/en/US/products/sw/iosswrel/ps5207/products_feature_guide09186a00802259e0.html#wp1059248 -- Pekka Savola "You each name yourselves king, yet the Netcore Oy kingdom bleeds." Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings _______________________________________________ Idr mailing list Idr@ietf.org https://www1.ietf.org/mailman/listinfo/idr
- [Idr] BGP MIB v2 input Susan Hares
- Re: [Idr] BGP MIB v2 input Simon Leinen
- Re: [Idr] BGP MIB v2 input Henk Uijterwaal
- Re: [Idr] BGP MIB v2 input Bill Fenner
- Re: [Idr] BGP MIB v2 input Pekka Savola
- Re: [Idr] BGP MIB v2 input Jeffrey Haas
- Re: [Idr] BGP MIB v2 input Curtis Villamizar
- Re: [Idr] BGP MIB v2 input Jeffrey Haas
- Re: [Idr] BGP MIB v2 input Curtis Villamizar
- Re: [Idr] BGP MIB v2 input Jeffrey Haas
- Re: [Idr] BGP MIB v2 input Pekka Savola
- Re: [Idr] BGP MIB v2 input Bill Fenner
- Re: [Idr] BGP MIB v2 input Jeffrey Haas
- Re: [Idr] BGP MIB v2 input Curtis Villamizar
- Re: [Idr] BGP MIB v2 input Curtis Villamizar
- Re: [Idr] BGP MIB v2 input Pekka Savola