Network Working Group J. Haas, Ed.
Request for Comments: 4273 S. Hares, Ed.
Obsoletes: 1269, 1657 NextHop Technologies
Category: Standards Track January 2006
Definitions of Managed Objects for BGP-4
Status of This Memo
This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2006).
Abstract
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community
In particular, it describes managed objects used for managing the
Border Gateway Protocol Version 4 or lower.
The origin of this memo is from RFC 1269 "Definitions of Managed
Objects for the Border Gateway Protocol (Version 3)", which was
updated to support BGP-4 in RFC 1657. This memo fixes errors
introduced when the MIB module was converted to use the SMIv2
language. This memo also updates references to the current SNMP
framework documents.
This memo is intended to document deployed implementations of this
MIB module in a historical context, to provide clarifications of some
items, and to note errors where the MIB module fails to fully
represent the BGP protocol. Work is currently in progress to replace
this MIB module with a new one representing the current state of the
BGP protocol and its extensions.
This document obsoletes RFC 1269 and RFC 1657.
Haas & Hares Standards Track [Page 1]RFC 4273 BGP4-MIB January 2006Table of Contents
1. Introduction ....................................................2
2. The Internet-Standard Management Framework ......................2
3. Overview ........................................................2
4. Definitions .....................................................3
5. Security Considerations ........................................28
6. Acknowledgements ...............................................30
7. Normative References ...........................................31
1. Introduction
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes managed objects used for managing the
Border Gateway Protocol Version 4 or lower [BGP4, BGP4APP].
This memo obsoletes RFC 1657 and RFC 1269.
2. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580].
3. Overview
These objects are used to control and manage a BGP-4 implementation.
Apart from a few system-wide scalar objects, this MIB is broken into
three tables: the BGP Peer Table, the BGP Received Path Attribute
Table, and the BGP-4 Received Path Attribute Table. The BGP Peer
Table contains information about state and current activity of
connections with the BGP peers. The BGP Received Path Attribute
Table contains path attributes received from all peers running BGP
version 3 or less. The BGP-4 Received Path Attribute Table contains
path attributes received from all BGP-4 peers. The actual attributes
used in determining a route are a subset of the received attribute
tables after local routing policy has been applied.
Haas & Hares Standards Track [Page 2]RFC 4273 BGP4-MIB January 20064. Definitions
BGP4-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
IpAddress, Integer32, Counter32, Gauge32, mib-2