Re: [Idr] BGP MIB v2 input

Pekka Savola <pekkas@netcore.fi> Mon, 26 March 2007 19:50 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 1HVvCy-00075j-Lx; Mon, 26 Mar 2007 15:50:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HVvCx-00075e-QW for idr@ietf.org; Mon, 26 Mar 2007 15:50:23 -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 1HVvCx-0005fY-Ai for idr@ietf.org; Mon, 26 Mar 2007 15:50:23 -0400
Received: from localhost (pekkas@localhost) by netcore.fi (8.12.11.20060614/8.12.11) with ESMTP id l2QJoIlx006000; Mon, 26 Mar 2007 22:50:18 +0300
Date: Mon, 26 Mar 2007 22:50:18 +0300
From: Pekka Savola <pekkas@netcore.fi>
To: Jeffrey Haas <jhaas@pfrc.org>
Subject: Re: [Idr] BGP MIB v2 input
In-Reply-To: <20070326184044.GA11264@scc.mi.org>
Message-ID: <Pine.LNX.4.64.0703262242070.5773@netcore.fi>
References: <20070326171746.GA5090@scc.mi.org> <200703261821.l2QILAae076038@workhorse.brookfield.occnc.com> <20070326184044.GA11264@scc.mi.org>
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=-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: bb8f917bb6b8da28fc948aeffb74aa17
Cc: Bill Fenner <fenner@research.att.com>, 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

On Mon, 26 Mar 2007, Jeffrey Haas wrote:
>> If it could be made useful for ISPs it would make the job of writing
>> NOC software tools and ISP NMS tools all the easier.
>
> <zathras>This is wrong tool</zathras>
>
> To re-ask the question - drop the routing database from the MIB?

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?

Similar information for the whole FIB exists under IP-FORWARD-MIB.

Both are widely implemented AFAIK, which seems like a proof that an 
implementation is feasible.

FWIW, I agree that using SNMP to dump 200K+ prefixes from routing 
tables across all routers is likely not very useful in most cases, 
especially if you want to compare the tables, as the tables are going 
change over time. (Though in restricted contexts like without DFZ this 
may or may not be useful.)

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

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