Re: [Idr] BGP MIB v2 input
Pekka Savola <pekkas@netcore.fi> Tue, 27 March 2007 05:52 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 1HW4bR-0005RR-Sk; Tue, 27 Mar 2007 01:52:17 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HW4bQ-0005RJ-Tn for idr@ietf.org; Tue, 27 Mar 2007 01:52:16 -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 1HW4bQ-0007nU-Cx for idr@ietf.org; Tue, 27 Mar 2007 01:52:16 -0400
Received: from localhost (pekkas@localhost) by netcore.fi (8.12.11.20060614/8.12.11) with ESMTP id l2R5q2xu017612; Tue, 27 Mar 2007 08:52:02 +0300
Date: Tue, 27 Mar 2007 08:52:02 +0300
From: Pekka Savola <pekkas@netcore.fi>
To: Bill Fenner <fenner@research.att.com>
Subject: Re: [Idr] BGP MIB v2 input
In-Reply-To: <200703262016.l2QKGEVi013401@bright.research.att.com>
Message-ID: <Pine.LNX.4.64.0703270843310.16264@netcore.fi>
References: <20070326171746.GA5090@scc.mi.org> <200703261821.l2QILAae076038@workhorse.brookfield.occnc.com> <20070326184044.GA11264@scc.mi.org> <Pine.LNX.4.64.0703262242070.5773@netcore.fi> <200703262016.l2QKGEVi013401@bright.research.att.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Virus-Scanned: ClamAV 0.90.1/2931/Mon Mar 26 11:43:40 2007 on otso.netcore.fi
X-Virus-Status: Clean
X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL, BAYES_00, NO_RELAYS autolearn=ham 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: 50a516d93fd399dc60588708fd9a3002
Cc: idr@ietf.org
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
off-list, On Mon, 26 Mar 2007, Bill Fenner wrote: >> Just wondering: the current BGP4 MIB already supports the routing >> databse (BGP4-MIB::bgp4PathAttrBest at least). Are you proposing >> dropping the equivalent functionality from the new MIB or just some >> more exciting new variants? > > That was my proposal, since getting a pathattr table that > nicely handles IP and non-IP NLRI is ... confusing. It also > can result in less than ideal behavior when walking the whole > MIB on a device that has hundreds of thousands of prefixes. If non-IP NLRI's are considerably difficult, maybe those should not be presented in the MIB (at least in the basic version)? >> An example: I currently use both IP-FORWARD-MIB and >> BGP4-MIB::bgp4PathAttrBest in SNMP scripts by parsing the config files >> (interface-related routing protocol config to be exact) and checking >> them against operational policy (e.g., certain kinds of interface >> addresses must be in OSPF; others must not be in OSPF; some others >> must be in BGP; static routes must be in BGP; etc.). > > Interesting. I was looking it from the point of view of not knowing > exactly what prefix you were looking for (e.g., "show ip bgp 12.106.35.1" > without knowing that it's in a /22). The obvious thing to do is to grab > the whole table (probably inadvisable); there are more subtle ways but > none are very efficient. I'm not sure how the SNMP agent implementation actually does it (i.e. whether it needs to do memory copy of the whole table), but this what I do is without a subnet mask (because I have been too lazy to convert it between different prefix length representations :-): $ snmpwalk -v 2c -c $comm -m BGP4-MIB $rtr bgp4PathAttrBest.193.167.190.0 BGP4-MIB::bgp4PathAttrBest.193.167.190.0.25.172.31.5.199 = INTEGER: true(2) BGP4-MIB::bgp4PathAttrBest.193.167.190.0.30.172.31.5.199 = INTEGER: true(2) .. and if I wanted to get more than just one prefix, I could walk a whole /16 with, e.g.: $ snmpwalk -v 2c -c $comm -m BGP4-MIB $rtr bgp4PathAttrBest.193.166 ... -- 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