draft-ietf-idr-bgp4-mib-07.txt   draft-ietf-idr-bgp4-mib-08.txt 
Network Working Group J. Haas Network Working Group Editors of this version:
INTERNET DRAFT NextHop INTERNET DRAFT J. Haas
NextHop
S. Hares S. Hares
NextHop NextHop
Authors of previous version:
S. Willis S. Willis
Argon Networks Argon Networks
J. Burruss
WinData
Editor of previous version:
J. Chu J. Chu
Cosine Cosine
July 2001 November 2001
Definitions of Managed Objects Definitions of Managed Objects
for the Fourth Version of Border Gateway Protocol (BGP-4) for the Fourth Version of Border Gateway Protocol (BGP-4)
<draft-ietf-idr-bgp4-mib-07.txt> <draft-ietf-idr-bgp4-mib-08.txt>
Status of this Memo 1. Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. all provisions of Section 10 of RFC 2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts. http://www.ietf.org/ietf/1id-abstracts.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Copyright Notice 2. Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
Abstract 3. Abstract
This memo is an extension to the SNMP MIB. The origin of this memo This memo is an extension to the SNMP MIB. The origin of this memo
is from RFC 1269 "Definitions of Managed Objects for the Border is from RFC 1269 "Definitions of Managed Objects for the Border
Gateway Protocol (Version 3)", which was updated to support BGP-4 in Gateway Protocol (Version 3)", which was updated to support BGP-4 in
RFC 1657. This memo fixes errors introduced when the MIB was RFC 1657. This memo fixes errors introduced when the MIB was
converted to use the SNMPv2 SMI, as well as updates references to the converted to use the SNMPv2 SMI, as well as updates references to the
current SNMP framework documents. current SNMP framework documents.
This memo is intended to document deployed implementations of this This memo is intended to document deployed implementations of this
MIB in a historical context, provide clarifications of some items and MIB in a historical context, provide clarifications of some items and
also note errors where the MIB fails to fully represent the BGP also note errors where the MIB fails to fully represent the BGP
protocol. Work is currently in progress to replace this MIB with a protocol. Work is currently in progress to replace this MIB with a
new one representing the current state of the BGP protocol and its new one representing the current state of the BGP protocol and its
extensions. extensions.
Distribution of this memo is unlimited. Please forward comments to Distribution of this memo is unlimited. Please forward comments to
idr@merit.net. idr@merit.net.
1. Introduction 4. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects used for managing the In particular, it describes managed objects used for managing the
Border Gateway Protocol Version 4 or lower [BGP, BGPAPPL]. Border Gateway Protocol Version 4 or lower [BGP, BGPAPPL].
2. The SNMP Management Framework 5. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
-- An overall architecture, described in RFC 2571 [RFC2571]. -- An overall architecture, described in RFC 2571 [RFC2571].
-- Mechanisms for describing and naming objects and events for the -- Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in Management Information (SMI) is called SMIv1 and described in
STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC
skipping to change at page 3, line 34 skipping to change at page 3, line 41
This memo specifies a MIB module that is compliant to the SMIv2. A This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB.
3. Overview 6. Overview
These objects are used to control and manage a BGP-4 implementation. 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 Apart from a few system-wide scalar objects, this MIB is broken into
three tables: the BGP Peer Table, the BGP Received Path Attribute three tables: the BGP Peer Table, the BGP Received Path Attribute
Table, and the BGP-4 Received Path Attribute Table. The BGP Peer Table, and the BGP-4 Received Path Attribute Table. The BGP Peer
Table contains information about state and current activity of Table contains information about state and current activity of
connections with the BGP peers. The Received Path Attribute Table connections with the BGP peers. The Received Path Attribute Table
contains path attributes received from all peers running BGP version contains path attributes received from all peers running BGP version
3 or less. The BGP-4 Received Path Attribute Table contains path 3 or less. The BGP-4 Received Path Attribute Table contains path
attributes received from all BGP-4 peers. The actual attributes used attributes received from all BGP-4 peers. The actual attributes used
in determining a route are a subset of the received attribute tables in determining a route are a subset of the received attribute tables
after local routing policy has been applied. after local routing policy has been applied.
4. Definitions 7. Definitions
BGP4-MIB DEFINITIONS ::= BEGIN BGP4-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
IpAddress, Integer32, Counter32, Gauge32, mib-2 IpAddress, Integer32, Counter32, Gauge32, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF; FROM SNMPv2-CONF;
bgp MODULE-IDENTITY bgp MODULE-IDENTITY
LAST-UPDATED "200106010000Z" LAST-UPDATED "200111030000Z"
ORGANIZATION "IETF IDR Working Group" ORGANIZATION "IETF IDR Working Group"
CONTACT-INFO "E-mail: idr@merit.net CONTACT-INFO "E-mail: idr@merit.net
Jeff Haas (Editor) Jeff Haas, Sue Hares (Editor)
517 W. William Street 517 W. William Street
Ann Arbor, MI 48103-4943 Ann Arbor, MI 48103-4943
Tel: +1 734 973-2200 Tel: +1 734 973-2200
Fax: +1 734 615-3241 Fax: +1 734 615-3241
E-mail: skh@nexthop.com" E-mail: jhaas@nexthop.com
skh@nexthop.com"
DESCRIPTION DESCRIPTION
"1) Fixed the definitions of the traps to "The MIB module for the BGP-4 protocol.
Changes since RFC 1657:
1) Fixed the definitions of the traps to
make them equivalent to their initial make them equivalent to their initial
definition in RFC 1269. definition in RFC 1269.
2) Added compliance and conformance info. 2) Added compliance and conformance info.
3) Updated for latest BGP information 3) Updated for latest BGP information
draft-ietf-idr-bgp4-10.txt for value of draft-ietf-idr-bgp4-15.txt for value of
bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref, bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref,
bgp4PathAttrCalcLocalPref,bgp4PathAttrMultiExitDisc, bgp4PathAttrCalcLocalPref,bgp4PathAttrMultiExitDisc,
bgp4PathAttrASPathSegement. bgp4PathAttrASPathSegement.
4) Added additional clarification commments where 4) Added additional clarification commments where
needed. needed.
5) Noted where objects do not fully reflect 5) Noted where objects do not fully reflect
the protocol as Known Issues." the protocol as Known Issues."
::= { mib-2 15 } ::= { mib-2 15 }
bgpVersion OBJECT-TYPE bgpVersion OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1..255)) SYNTAX OCTET STRING (SIZE (1..255))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Vector of supported BGP protocol version "Vector of supported BGP protocol version
numbers. Each peer negotiates the version numbers. Each peer negotiates the version
from this vector. Versions are identified from this vector. Versions are identified
via the string of bits contained within this via the string of bits contained within this
object. The first octet contains bits 0 to object. The first octet contains bits 0 to
skipping to change at page 8, line 4 skipping to change at page 9, line 10
start(2) start(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The desired state of the BGP connection. "The desired state of the BGP connection.
A transition from 'stop' to 'start' will A transition from 'stop' to 'start' will
cause the BGP Start Event to be generated. cause the BGP Start Event to be generated.
A transition from 'start' to 'stop' will A transition from 'start' to 'stop' will
cause the BGP Stop Event to be generated. cause the BGP Stop Event to be generated.
This parameter can be used to restart BGP This parameter can be used to restart BGP
peer connections. Care should be used in peer connections. Care should be used in
providing write access to this object providing write access to this object
without adequate authentication." without adequate authentication."
::= { bgpPeerEntry 3 } ::= { bgpPeerEntry 3 }
bgpPeerNegotiatedVersion OBJECT-TYPE bgpPeerNegotiatedVersion OBJECT-TYPE
SYNTAX Integer32 (1..255) SYNTAX Integer32 (0..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The negotiated version of BGP running between "The negotiated version of BGP running between
the two peers." the two peers.
This entry should be zero (0) unless the
bgpPeerState is in the openconfirm or the
established state."
::= { bgpPeerEntry 4 } ::= { bgpPeerEntry 4 }
bgpPeerLocalAddr OBJECT-TYPE bgpPeerLocalAddr OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The local IP address of this entry's BGP "The local IP address of this entry's BGP
connection." connection."
::= { bgpPeerEntry 5 } ::= { bgpPeerEntry 5 }
skipping to change at page 9, line 10 skipping to change at page 10, line 19
peer." peer."
::= { bgpPeerEntry 7 } ::= { bgpPeerEntry 7 }
bgpPeerRemotePort OBJECT-TYPE bgpPeerRemotePort OBJECT-TYPE
SYNTAX Integer32 (0..65535) SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The remote port for the TCP connection "The remote port for the TCP connection
between the BGP peers. Note that the between the BGP peers. Note that the
OBJECts bgpPeerLocalAddr, objects bgpPeerLocalAddr,
bgpPeerLocalPort, bgpPeerRemoteAddr and bgpPeerLocalPort, bgpPeerRemoteAddr and
bgpPeerRemotePort provide the appropriate bgpPeerRemotePort provide the appropriate
reference to the standard MIB TCP reference to the standard MIB TCP
connection table." connection table."
::= { bgpPeerEntry 8 } ::= { bgpPeerEntry 8 }
bgpPeerRemoteAs OBJECT-TYPE bgpPeerRemoteAs OBJECT-TYPE
SYNTAX Integer32 (0..65535) SYNTAX Integer32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 9, line 33 skipping to change at page 10, line 42
::= { bgpPeerEntry 9 } ::= { bgpPeerEntry 9 }
bgpPeerInUpdates OBJECT-TYPE bgpPeerInUpdates OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of BGP UPDATE messages "The number of BGP UPDATE messages
received on this connection. This object received on this connection. This object
should be initialized to zero (0) when the should be initialized to zero (0) when the
connection is established." connection is established. The value of this
object, when not in the established state,
is undefined."
::= { bgpPeerEntry 10 } ::= { bgpPeerEntry 10 }
bgpPeerOutUpdates OBJECT-TYPE bgpPeerOutUpdates OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of BGP UPDATE messages "The number of BGP UPDATE messages
transmitted on this connection. This transmitted on this connection. This
object should be initialized to zero (0) object should be initialized to zero (0)
when the connection is established." when the connection is established. The
value of this object, when not in the
established state, is undefined."
::= { bgpPeerEntry 11 } ::= { bgpPeerEntry 11 }
bgpPeerInTotalMessages OBJECT-TYPE bgpPeerInTotalMessages OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of messages received "The total number of messages received
from the remote peer on this connection. from the remote peer on this connection.
This object should be initialized to zero This object should be initialized to zero
when the connection is established." when the connection is established. The
value of this object, when not in the
established state, is undefined."
::= { bgpPeerEntry 12 } ::= { bgpPeerEntry 12 }
bgpPeerOutTotalMessages OBJECT-TYPE bgpPeerOutTotalMessages OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of messages transmitted to "The total number of messages transmitted to
the remote peer on this connection. This the remote peer on this connection. This
object should be initialized to zero when object should be initialized to zero when
the connection is established." the connection is established. The
value of this object, when not in the
established state, is undefined."
::= { bgpPeerEntry 13 } ::= { bgpPeerEntry 13 }
bgpPeerLastError OBJECT-TYPE bgpPeerLastError OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (2)) SYNTAX OCTET STRING (SIZE (2))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The last error code and subcode seen by this "The last error code and subcode seen by this
peer on this connection. If no error has peer on this connection. If no error has
occurred, this field is zero. Otherwise, the occurred, this field is zero. Otherwise, the
skipping to change at page 11, line 4 skipping to change at page 12, line 20
bgpPeerFsmEstablishedTransitions OBJECT-TYPE bgpPeerFsmEstablishedTransitions OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The total number of times the BGP FSM "The total number of times the BGP FSM
transitioned into the established state transitioned into the established state
for this peer." for this peer."
::= { bgpPeerEntry 15 } ::= { bgpPeerEntry 15 }
bgpPeerFsmEstablishedTime OBJECT-TYPE bgpPeerFsmEstablishedTime OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This timer indicates how long (in "This timer indicates how long (in
seconds) this peer has been in the seconds) this peer has been in the
Established state or how long established state or how long
since this peer was last in the since this peer was last in the
Established state. It is set to zero when established state. It is set to zero when
a new peer is configured or the router is a new peer is configured or the router is
booted." booted."
::= { bgpPeerEntry 16 } ::= { bgpPeerEntry 16 }
bgpPeerConnectRetryInterval OBJECT-TYPE bgpPeerConnectRetryInterval OBJECT-TYPE
SYNTAX Integer32 (1..65535) SYNTAX Integer32 (1..65535)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time interval in seconds for the "Time interval in seconds for the
skipping to change at page 11, line 40 skipping to change at page 13, line 13
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time interval in seconds for the Hold "Time interval in seconds for the Hold
Timer established with the peer. The Timer established with the peer. The
value of this object is calculated by this value of this object is calculated by this
BGP speaker by using the smaller of the BGP speaker by using the smaller of the
value in bgpPeerHoldTimeConfigured and the value in bgpPeerHoldTimeConfigured and the
Hold Time received in the OPEN message. Hold Time received in the OPEN message.
This value must be at lease three seconds This value must be at lease three seconds
if it is not zero (0) in which case the if it is not zero (0). If the value is
Hold Timer has not been established with the zero (0), the Hold Timer has either not been
peer, or, the value of established with the peer, or, the value of
bgpPeerHoldTimeConfigured is zero (0)." bgpPeerHoldTimeConfigured is zero (0)."
::= { bgpPeerEntry 18 } ::= { bgpPeerEntry 18 }
bgpPeerKeepAlive OBJECT-TYPE bgpPeerKeepAlive OBJECT-TYPE
SYNTAX Integer32 ( 0 | 1..21845 ) SYNTAX Integer32 ( 0 | 1..21845 )
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time interval in seconds for the KeepAlive "Time interval in seconds for the KeepAlive
timer established with the peer. The value of timer established with the peer. The value
this object is calculated by this BGP of this object is calculated by this BGP
speaker such that, when compared with speaker such that, when compared with
bgpPeerHoldTime, it has the same bgpPeerHoldTime, it has the same proportion
proportion as what as what bgpPeerKeepAliveConfigured has when
bgpPeerKeepAliveConfigured has when compared with bgpPeerHoldTimeConfigured. If
compared with bgpPeerHoldTimeConfigured. the value of this object is zero (0), it
If the value of this object is zero (0), indicates that the KeepAlive timer has not
it indicates that the KeepAlive timer has been established with the peer, or, the value
not been established with the peer, or, of bgpPeerKeepAliveConfigured is zero (0)."
the value of bgpPeerKeepAliveConfigured is
zero (0)."
::= { bgpPeerEntry 19 } ::= { bgpPeerEntry 19 }
bgpPeerHoldTimeConfigured OBJECT-TYPE bgpPeerHoldTimeConfigured OBJECT-TYPE
SYNTAX Integer32 ( 0 | 3..65535 ) SYNTAX Integer32 ( 0 | 3..65535 )
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time interval in seconds for the Hold Time "Time interval in seconds for the Hold Time
configured for this BGP speaker with this configured for this BGP speaker with this
peer. This value is placed in an OPEN peer. This value is placed in an OPEN
skipping to change at page 14, line 4 skipping to change at page 15, line 20
seconds." seconds."
::= { bgpPeerEntry 23 } ::= { bgpPeerEntry 23 }
bgpPeerInUpdateElapsedTime OBJECT-TYPE bgpPeerInUpdateElapsedTime OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Elapsed time in seconds since the last BGP "Elapsed time in seconds since the last BGP
UPDATE message was received from the peer. UPDATE message was received from the peer.
Each time bgpPeerInUpdates is incremented, Each time bgpPeerInUpdates is incremented,
the value of this object is set to zero the value of this object is set to zero (0)."
(0)."
::= { bgpPeerEntry 24 } ::= { bgpPeerEntry 24 }
bgpIdentifier OBJECT-TYPE bgpIdentifier OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BGP Identifier of local system." "The BGP Identifier of local system."
::= { bgp 4 } ::= { bgp 4 }
skipping to change at page 15, line 7 skipping to change at page 16, line 20
INDEX { bgpPathAttrDestNetwork, INDEX { bgpPathAttrDestNetwork,
bgpPathAttrPeer } bgpPathAttrPeer }
::= { bgpRcvdPathAttrTable 1 } ::= { bgpRcvdPathAttrTable 1 }
BgpPathAttrEntry ::= SEQUENCE { BgpPathAttrEntry ::= SEQUENCE {
bgpPathAttrPeer bgpPathAttrPeer
IpAddress, IpAddress,
bgpPathAttrDestNetwork bgpPathAttrDestNetwork
IpAddress, IpAddress,
bgpPathAttrOrigin bgpPathAttrOrigin
Integer32, INTEGER,
bgpPathAttrASPath bgpPathAttrASPath
OCTET STRING, OCTET STRING,
bgpPathAttrNextHop bgpPathAttrNextHop
IpAddress, IpAddress,
bgpPathAttrInterASMetric bgpPathAttrInterASMetric
Integer32 Integer32
} }
bgpPathAttrPeer OBJECT-TYPE bgpPathAttrPeer OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
skipping to change at page 15, line 36 skipping to change at page 17, line 5
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The address of the destination network." "The address of the destination network."
::= { bgpPathAttrEntry 2 } ::= { bgpPathAttrEntry 2 }
bgpPathAttrOrigin OBJECT-TYPE bgpPathAttrOrigin OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
igp(1),-- networks are interior igp(1),-- networks are interior
egp(2),-- networks learned via EGP egp(2),-- networks learned via the
incomplete(3) -- undetermined -- EGP protocol
incomplete(3) -- networks that
-- are learned by some other
-- means
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The ultimate origin of the path information." "The ultimate origin of the path information."
::= { bgpPathAttrEntry 3 } ::= { bgpPathAttrEntry 3 }
bgpPathAttrASPath OBJECT-TYPE bgpPathAttrASPath OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (2..255)) SYNTAX OCTET STRING (SIZE (2..255))
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 18, line 40 skipping to change at page 20, line 12
is an IP address containing the prefix with is an IP address containing the prefix with
length specified by length specified by
bgp4PathAttrIpAddrPrefixLen. bgp4PathAttrIpAddrPrefixLen.
Any bits beyond the length specified by Any bits beyond the length specified by
bgp4PathAttrIpAddrPrefixLen are zeroed." bgp4PathAttrIpAddrPrefixLen are zeroed."
::= { bgp4PathAttrEntry 3 } ::= { bgp4PathAttrEntry 3 }
bgp4PathAttrOrigin OBJECT-TYPE bgp4PathAttrOrigin OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
igp(1),-- networks are interior igp(1),-- networks are interior
egp(2),-- networks learned egp(2),-- networks learned via the
-- via EGP -- EGP protocol
incomplete(3) -- undetermined incomplete(3) -- networks that
-- are learned by some other
-- means
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ultimate origin of the path "The ultimate origin of the path
information." information."
::= { bgp4PathAttrEntry 4 } ::= { bgp4PathAttrEntry 4 }
bgp4PathAttrASPathSegment OBJECT-TYPE bgp4PathAttrASPathSegment OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (2..255)) SYNTAX OCTET STRING (SIZE (2..255))
skipping to change at page 22, line 17 skipping to change at page 23, line 36
bgp4PathAttrBest OBJECT-TYPE bgp4PathAttrBest OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
false(1),-- not chosen as best route false(1),-- not chosen as best route
true(2) -- chosen as best route true(2) -- chosen as best route
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An indication of whether or not this route "An indication of whether or not this route
was chosen as the best BGP4 route." was chosen as the best BGP4 route for this
destination."
::= { bgp4PathAttrEntry 13 } ::= { bgp4PathAttrEntry 13 }
bgp4PathAttrUnknown OBJECT-TYPE bgp4PathAttrUnknown OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(0..255)) SYNTAX OCTET STRING (SIZE(0..255))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"One or more path attributes not understood "One or more path attributes not understood
by the base BGP-4 document. this BGP4 speaker.
Path attributes are recorded in the Update Path
attribute format of type, length, value.
Path attributes are recorded in the Update
Path attribute format of type, length, value.
Size zero (0) indicates the absence of such Size zero (0) indicates the absence of such
attribute(s). Octets beyond the maximum size, attributes.
if any, are not recorded by this object. "
Octets beyond the maximum size, if any, are not
recorded by this object.
Known Issues:
o Attributes understood by this speaker, but not
represented in this MIB, are unavailable to
the agent."
::= { bgp4PathAttrEntry 14 } ::= { bgp4PathAttrEntry 14 }
-- Traps. -- Traps.
-- note that in RFC 1657, bgpTraps was incorrectly -- note that in RFC 1657, bgpTraps was incorrectly
-- assigned a value of { bgp 7 }, and each of the -- assigned a value of { bgp 7 }, and each of the
-- traps had the bgpPeerRemoteAddr object inappropriately -- traps had the bgpPeerRemoteAddr object inappropriately
-- removed from their OBJECTS clause. The following -- removed from their OBJECTS clause. The following
-- definitions restore the semantics of the traps as -- definitions restore the semantics of the traps as
-- they were initially defined in RFC 1269. -- they were initially defined in RFC 1269.
skipping to change at page 23, line 22 skipping to change at page 25, line 5
This object obsoletes bgpEstablished." This object obsoletes bgpEstablished."
::= { bgpNotification 1 } ::= { bgpNotification 1 }
bgpBackwardTransNotification NOTIFICATION-TYPE bgpBackwardTransNotification NOTIFICATION-TYPE
OBJECTS { bgpPeerRemoteAddr, OBJECTS { bgpPeerRemoteAddr,
bgpPeerLastError, bgpPeerLastError,
bgpPeerState } bgpPeerState }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BGP Backward Transition Event is generated "The BGPBackwardTransNotification Event is
when the BGP FSM moves from a higher numbered generated when the BGP FSM moves from a higher
state to a lower numbered state. numbered state to a lower numbered state.
This object obsoletes bgpBackwardTransition." This object obsoletes bgpBackwardsTransition."
::= { bgpNotification 2 } ::= { bgpNotification 2 }
-- { bgp 7 } is obsoleted -- { bgp 7 } is obsoleted
bgpTraps OBJECT IDENTIFIER ::= { bgp 7 } bgpTraps OBJECT IDENTIFIER ::= { bgp 7 }
bgpEstablished NOTIFICATION-TYPE bgpEstablished NOTIFICATION-TYPE
OBJECTS { bgpPeerRemoteAddr, OBJECTS { bgpPeerRemoteAddr,
bgpPeerLastError, bgpPeerLastError,
bgpPeerState } bgpPeerState }
skipping to change at page 24, line 7 skipping to change at page 25, line 33
the BGP FSM enters the ESTABLISHED state. the BGP FSM enters the ESTABLISHED state.
This object has been obsoleted in favor of This object has been obsoleted in favor of
bgpEstablishedNotification." bgpEstablishedNotification."
::= { bgpTraps 1 } ::= { bgpTraps 1 }
bgpBackwardTransition NOTIFICATION-TYPE bgpBackwardTransition NOTIFICATION-TYPE
OBJECTS { bgpPeerRemoteAddr, OBJECTS { bgpPeerRemoteAddr,
bgpPeerLastError, bgpPeerLastError,
bgpPeerState } bgpPeerState }
STATUS obsolete STATUS current
DESCRIPTION DESCRIPTION
"The BGPBackwardTransition Event is generated "The BGPBackwardTransition Event is generated
when the BGP FSM moves from a higher numbered when the BGP FSM moves from a higher numbered
state to a lower numbered state. state to a lower numbered state.
This object has been obsoleted in favor of This object has been obsoleted in favor of
bgpBackwardTransitionNotification." bgpBackwardTransNotification."
::= { bgpTraps 2 } ::= { bgpTraps 2 }
-- conformance information -- conformance information
bgpMIBConformance OBJECT IDENTIFIER bgpMIBConformance OBJECT IDENTIFIER
::= { bgp 8 } ::= { bgp 8 }
bgpMIBCompliances OBJECT IDENTIFIER bgpMIBCompliances OBJECT IDENTIFIER
::= { bgpMIBConformance 1 } ::= { bgpMIBConformance 1 }
bgpMIBGroups OBJECT IDENTIFIER bgpMIBGroups OBJECT IDENTIFIER
::= { bgpMIBConformance 2 } ::= { bgpMIBConformance 2 }
skipping to change at page 26, line 41 skipping to change at page 28, line 24
::= { bgpMIBGroups 4 } ::= { bgpMIBGroups 4 }
bgp4MIBNotificationGroup NOTIFICATION-GROUP bgp4MIBNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { bgpEstablished, NOTIFICATIONS { bgpEstablished,
bgpBackwardTransition } bgpBackwardTransition }
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"A collection of notifications for signaling "A collection of notifications for signaling
changes in BGP peer relationships. changes in BGP peer relationships.
Obsoleted by bgp4MIBNewNotificationGroup." Obsoleted by bgp4MIBNewNotificationGroup"
::= { bgpMIBGroups 5 } ::= { bgpMIBGroups 5 }
bgp4MIBNewNotificationGroup NOTIFICATION-GROUP bgp4MIBNewNotificationGroup NOTIFICATION-GROUP
NOTIFICATIONS { bgpEstablishedNotification, NOTIFICATIONS { bgpEstablishedNotification,
bgpBackwardTransNotification } bgpBackwardTransNotification }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of notifications for signaling "A collection of notifications for signaling
changes in BGP peer relationships. changes in BGP peer relationships.
Obsoletes bgp4MIBNotificationGroup." Obsoletes bgp4MIBNotificationGroup."
::= { bgpMIBGroups 6 } ::= { bgpMIBGroups 6 }
END END
5. Intellectual Property 8. Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat. be obtained from the IETF Secretariat.
6. Acknowledgements 9. Acknowledgements
We would like to acknowledge the assistance of all the members of the We would like to acknowledge the assistance of all the members of the
Inter-Domain Routing Working Group, and particularly the following Inter-Domain Routing Working Group, and particularly the following
individuals: individuals:
Yakov Rekhter, Juniper Networks Yakov Rekhter, Juniper Networks
Rob Coltun, Redback Rob Coltun, Redback
Guy Almes, Internet2 Guy Almes, Internet2
Jeff Honig, BSDi Jeff Honig, BSDi
Marshall T. Rose, Dover Beach Consulting, Inc. Marshall T. Rose, Dover Beach Consulting, Inc.
skipping to change at page 28, line 4 skipping to change at page 29, line 35
Mike Mathis, PSC Mike Mathis, PSC
John Krawczyk, Bay Networks John Krawczyk, Bay Networks
Curtis Villamizar, Avici Curtis Villamizar, Avici
Dave LeRoy, Pencom Systems Dave LeRoy, Pencom Systems
Paul Traina, Juniper Networks Paul Traina, Juniper Networks
Andrew Partan, MFN Andrew Partan, MFN
Robert Snyder, cisco Systems Robert Snyder, cisco Systems
Dimitry Haskin, Nortel Dimitry Haskin, Nortel
Peder Chr Norgaard, Telebit Communications A/S Peder Chr Norgaard, Telebit Communications A/S
Joel Halpern, CTO Longitude Systems, Inc. Joel Halpern, CTO Longitude Systems, Inc.
Nick Thille, RedBack Networks Nick Thille, RedBack Networks
Bert Wijnen, Lucent Bert Wijnen, Lucent
Shane Wright, NextHop Shane Wright, NextHop
Mike McFadden, Riverstone Networks, Inc. Mike McFadden, Riverstone Networks, Inc.
Jon Saperia, JDS Consulting, Inc. Jon Saperia, JDS Consulting, Inc.
Wayne Tackabury, Gold Wire Technology, Inc Wayne Tackabury, Gold Wire Technology, Inc.
Bill Fenner, AT&T Research Bill Fenner, AT&T Research
The origin of this document is from RFC 1269 "Definitions of Managed The origin of this document is from RFC 1269 "Definitions of Managed
Objects for the Border Gateway Protocol (Version 3)" written by Steve Objects for the Border Gateway Protocol (Version 3)" written by Steve
Willis and John Burruss, which was updated by John Chu to support Willis and John Burruss, which was updated by John Chu to support
BGP-4 in RFC 1657. The editors wish to acknowledge the fine work of BGP-4 in RFC 1657. The editors wish to acknowledge the fine work of
these original authors. these original authors.
7. References 10. References
[BGP4] Rekhter, Y., Li, T., "A Border Gateway Protocol 4 (BGP-4)", RFC [BGP4] Rekhter, Y., Li, T., "A Border Gateway Protocol 4 (BGP-4)", RFC
1771, March 1995. 1771, March 1995.
[BGP4APP] Rekhter, Y., Gross, P., "Application of the Border Gateway [BGP4APP] Rekhter, Y., Gross, P., "Application of the Border Gateway
Protocol in the Internet", RFC 1772, March 1995. Protocol in the Internet", RFC 1772, March 1995.
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture
for Describing SNMP Management Frameworks", RFC 2571, April for Describing SNMP Management Frameworks", RFC 2571, April
1999. 1999.
skipping to change at page 31, line 5 skipping to change at page 32, line 5
RFC 2573, April 1999. RFC 2573, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2575, April 1999. Management Protocol (SNMP)", RFC 2575, April 1999.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction to Version 3 of the Internet-standard Network "Introduction to Version 3 of the Internet-standard Network
Management Framework", RFC 2570, April 1999. Management Framework", RFC 2570, April 1999.
8. Security Considerations 11. Security Considerations
There are a number of management objects defined in this MIB that There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write: have a MAX-ACCESS clause of read-write:
bgpPeerAdminStatus bgpPeerAdminStatus
bgpPeerConnectRetryInterval bgpPeerConnectRetryInterval
bgpPeerHoldTimeConfigured bgpPeerHoldTimeConfigured
bgpPeerKeepAliveConfigured bgpPeerKeepAliveConfigured
bgpPeerMinASOriginationInterval bgpPeerMinASOriginationInterval
bgpPeerMinRouteAdvertisementInterval bgpPeerMinRouteAdvertisementInterval
skipping to change at page 32, line 5 skipping to change at page 33, line 5
features as provided by the SNMPv3 framework. Specifically, the use features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model RFC 2274 [14] and the View-based of the User-based Security Model RFC 2274 [14] and the View-based
Access Control Model RFC 2275 [17] is recommended. Access Control Model RFC 2275 [17] is recommended.
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly entity giving access to an instance of this MIB, is properly
configured to give access to the objects only to those principals configured to give access to the objects only to those principals
(users) that have legitimate rights to indeed GET or SET (users) that have legitimate rights to indeed GET or SET
(change/create/delete) them. (change/create/delete) them.
9. Authors' Address 12. Editors Address
Jeff Haas Jeff Haas, Sue Hares
NextHop Technologies NextHop Technologies
517 Williams 825 Victor's Way, Suite 100
Ann Arbor, MI 48103-4943 Ann Arbor, MI 48103
Phone: +1 734 973-2200 Phone: +1 734 222-1600
Fax: +1 734 615-3241 Fax: +1 734 222-1602
Email: jhaas@nexthop.com Email: jhaas@nexthop.com
skh@nexthop.com
Jeff Johnson 13. Full Copyright Statement
RedBack Networks, Inc.
1389 Moffett Park Drive
Sunnyvale, CA 94089
Phone: +1 408 548 3516
Email: jeff@redback.com
Steve Willis
Argon Networks
25 Porter Road
Littleton, MA 01450
Phone: +1 508 486 0665
Fax: +1 508 486 9379
Email: swills@argon.com
John Burruss
Windata Inc.
543 Great Road
Littleton MA 01460
Phone: +1 508 952 0170
Email: jburruss@windata.com
John Chu
Cosine Communications
1200 Bridge Parkway
Redwood City, CA 94065
Phone: 650-637-4780
Email: jchu@cosinecom.com
10. Full Copyright Statement
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
skipping to change at line 1395 skipping to change at line 1399
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Table of Contents
1. Status of this Memo .............................................. 1
2. Copyright Notice ................................................. 2
3. Abstract ......................................................... 2
4. Introduction ..................................................... 2
5. The SNMP Management Framework .................................... 2
6. Overview ......................................................... 3
7. Definitions ...................................................... 5
8. Intellectual Property ........................................... 28
9. Acknowledgements ................................................ 29
10. References ...................................................... 30
11. Security Considerations ......................................... 32
12. Editors Address ................................................. 33
13. Full Copyright Statement ........................................ 33
i
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/