Re: [Idr] [f-nsp] XMR SNMP BGP accepted prefixes

Simon Leinen <> Wed, 18 June 2008 08:56 UTC

Return-Path: <>
Received: from [] (localhost []) by (Postfix) with ESMTP id 0239D3A6901; Wed, 18 Jun 2008 01:56:15 -0700 (PDT)
Received: from localhost (localhost []) by (Postfix) with ESMTP id 876083A6901 for <>; Wed, 18 Jun 2008 01:56:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id jVtqsw6WNyTm for <>; Wed, 18 Jun 2008 01:56:13 -0700 (PDT)
Received: from ( [IPv6:2001:620:0:4:203:baff:fe4c:d751]) by (Postfix) with ESMTP id 2D7573A684F for <>; Wed, 18 Jun 2008 01:56:12 -0700 (PDT)
Received: from (localhost []) by (8.14.2+Sun/8.14.2) with ESMTP id m5I8ut0P018242; Wed, 18 Jun 2008 10:56:55 +0200 (CEST)
Received: (from leinen@localhost) by (8.14.2+Sun/8.14.2/Submit) id m5I8usUe018240; Wed, 18 Jun 2008 10:56:55 +0200 (CEST)
X-Authentication-Warning: leinen set sender to using -f
From: Simon Leinen <>
To: Erich Hohermuth <>
In-Reply-To: <> (Erich Hohermuth's message of "Mon, 16 Jun 2008 11:30:01 +0200")
References: <>
X-Face: 1Nk*r=:$IBBb8|TyRB'2WSY6u:BzMO7N)#id#-4_}MsU5?vTI?dez|JiutW4sKBLjp.l7, F 7QOld^hORRtpCUj)!cP]gtK_SyK5FW(+o"!or:v^C^]OxX^3+IPd\z, @ttmwYVO7l`6OXXYR`
Date: Wed, 18 Jun 2008 10:56:54 +0200
Message-ID: <>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.2 (usg-unix-v)
MIME-Version: 1.0
Subject: Re: [Idr] [f-nsp] XMR SNMP BGP accepted prefixes
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Inter-Domain Routing <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Erich Hohermuth writes:
> I'm searching for something similar on the xmr like I had on my
> cisco device for pooling the accepted bgp prefixes
> "cbgpPeerPrefixAccepted" [1]. I searched the foundry mib [2] but I
> couldn't find something. Unfortunately on the standard bgp mib [3]
> this information isn't supported.

That's true.  But in the IETF IDR (Inter-Domain Routing) WG there is
an effort to define a new and improved standard BGP MIB.

(The draft has currently "expired" because it hasn't been updated in
 six months.  But as long as people are interested in this, there is a
 chance that this will become standardized eventually.)

As of the latest proposal, this new BGP4-MIB will include

    bgpPrefixInPrefixesAccepted OBJECT-TYPE
        SYNTAX Gauge32
        MAX-ACCESS read-only
        STATUS current
            "The number of prefixes for a peer that are installed
             in the Adj-Ribs-In and are eligible to become active
             in the Loc-Rib."
        ::= { bgpPrefixCountersEntry 4 }

In addition, it will allow monitoring of BGP peerings and routes for
(sub-) address families other than IPv4 unicast, in particular IPv6.

It would be really great if vendors such as Foundry would go ahead and
implement this draft.  That way people could gather experience both
implementing the SNMP agent side and using the MIB to monitor their
peerings, and feed back those experiences into the IETF IDR WG.

It's a shame that we still don't have a standard BGP MIB that has
these things that many ISPs find essential for monitoring their
Idr mailing list