Re: [Idr] BGP MIB v2 input

Bill Fenner <fenner@research.att.com> Mon, 26 March 2007 20:16 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 1HVvc8-00014F-OF; Mon, 26 Mar 2007 16:16:24 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HVvc7-00014A-OF for idr@ietf.org; Mon, 26 Mar 2007 16:16:23 -0400
Received: from mail-red.research.att.com ([192.20.225.110]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1HVvc4-0004pC-El for idr@ietf.org; Mon, 26 Mar 2007 16:16:23 -0400
Received: from bright.research.att.com (bright.research.att.com [135.207.20.189]) by mail-green.research.att.com (Postfix) with ESMTP id 1F3AA8580; Mon, 26 Mar 2007 16:16:14 -0400 (EDT)
Received: (from fenner@localhost) by bright.research.att.com (8.13.1/8.12.10/Submit) id l2QKGEVi013401; Mon, 26 Mar 2007 22:16:14 +0200
From: Bill Fenner <fenner@research.att.com>
Message-Id: <200703262016.l2QKGEVi013401@bright.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
To: Pekka Savola <pekkas@netcore.fi>
Subject: Re: [Idr] BGP MIB v2 input
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>
Date: Mon, 26 Mar 2007 22:16:13 +0100
Versions: dmail (linux) 2.7/makemail 2.14
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
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

>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.

>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.

  Bill

_______________________________________________
Idr mailing list
Idr@ietf.org
https://www1.ietf.org/mailman/listinfo/idr