OID repository
OID Repository
Display OID:
Action itemiso(1) Action itemidentified-organization(3) Action itemdod(6) Action iteminternet(1) Action itemmgmt(2) Action itemmib-2(1)  

Navigating the OID tree

child OIDs: Child OID separator bgpNotification(0) Child OID separator bgpVersion(1) Child OID separator bgpLocalAs(2) Child OID separator bgpPeerTable(3) Child OID separator bgpIdentifier(4) Child OID separator bgpRcvdPathAttrTable(5) Child OID separator bgp4PathAttrTable(6) Child OID separator bgpTraps(7) Child OID separator bgp4MIBConformance(8) Child OID separator bgp4OptParametersMIB(9) Child OID separator bgpCommunities(10) Child OID separator bgpReflect(11) Child OID separator bgpConfed(12) Child OID separator bgpExtComm(13) Child OID separator
Separation line
OID description

OID: (ASN.1 notation)
(dot notation)
(OID-IRI notation)


LAST-UPDATED "200601110000Z"
CONTACT-INFO "E-mail: idr@ietf.org
Jeffrey Haas, Susan Hares (Editors)
NextHop Technologies
825 Victors Way
Suite 100
Ann Arbor, MI 48108-2738
Tel: +1 734 222-1600
Fax: +1 734 222-1602
E-mail: jhaas@nexthop.com
"The MIB module for the BGP-4 protocol.
Copyright (C) The Internet Society (2006). This version of this MIB module is part of RFC 4273; see the RFC itself for full legal notices."
REVISION "200601110000Z"
"Changes from RFC 1657:
1) Fixed the definitions of the notifications to make them equivalent to their initial definition in RFC 1269.
2) Added compliance and conformance info.
3) Updated information for the values of bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref, bgp4PathAttrCalcLocalPref, bgp4PathAttrMultiExitDisc, bgp4PathAttrASPathSegement.
4) Added additional clarification comments where needed.
5) Noted where objects do not fully reflect the protocol as Known Issues.
6) Updated the DESCRIPTION for the bgp4PathAttrAtomicAggregate object.
7) The following objects have had their DESCRIPTION clause modified to remove the text that suggested (using 'should' verb) initializing the counter to zero on a transition to the established state:
bgpPeerInUpdates, bgpPeerOutUpdates, bgpPeerInTotalMessages, bgpPeerOutTotalMessages
Those implementations that still do this are still compliant with this new wording.
Applications should not assume counters have started at zero.
Published as RFC 4273."
REVISION "199405050000Z"
"Translated to SMIv2 and published as RFC 1657."
REVISION "199110261839Z"
"Initial version, published as RFC 1269."


Automatically extracted from IETF RFC 4273.

Short URLs for this page:

Disclaimer: The owner of this site does not warrant or assume any liability or responsibility for the accuracy, completeness, or usefulness of any information available on this page (for more information, please read the complete disclaimer).
All rights reserved, Orange © 2024
Tree display Parent OID: mib-2(1) First child OID: bgpNotification(0) First sibling OID: reserved(0) Previous sibling OID: ospf(14) Next sibling OID: rmon(16) Last sibling OID: iptfsMIB(246)
Separation line
OID helper Webmaster Bullet 20 Sep 2023 Bullet Page top