draft-ietf-idr-bgp4-mib-00.txt   draft-ietf-idr-bgp4-mib-01.txt 
Network Working Group S. Willis Network Working Group S. Willis
INTERNET DRAFT J. Burruss INTERNET DRAFT BayNetworks
J. Burruss
BayNetworks BayNetworks
J. Chu J. Chu
(Editor) IBM Corporation
IBM Corp. J. Johnson
November 1995 cisco Systems
January 1996
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-00.txt> <draft-ietf-idr-bgp4-mib-01.txt>
Status of this Memo Status of this Memo
This document is an Internet Draft. Internet Drafts are working This document is an Internet Draft. Internet Drafts are working
documents of the Internet Engineering Task Force (IETF), its Areas, and documents of the Internet Engineering Task Force (IETF), its Areas, and
its Working Groups. Note that other groups may also distribute working its Working Groups. Note that other groups may also distribute working
documents as Internet Drafts. documents as Internet 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.
Internet Drafts may be updated, replaced, or obsoleted by other Internet Drafts may be updated, replaced, or obsoleted by other
documents at any time. It is not appropriate to use Internet Drafts as documents at any time. It is not appropriate to use Internet Drafts as
reference material or to cite them other than as a "working draft" or reference material or to cite them other than as a "working draft" or
"work in progress." "work in progress."
Please check the I-D abstract listing contained in each Internet Draft Please check the I-D abstract listing contained in each Internet Draft
directory to learn the current status of this or any other Internet directory to learn the current status of this or any other Internet
Draft. Draft.
Abstract
This memo is an extension to the SNMP MIB. It specifies an IAB This memo is an extension to the SNMP MIB. It specifies an IAB
standards track protocol for the Internet community, and requests standards track protocol for the Internet community, and requests
discussion and suggestions for improvements. The origin of this memo is discussion and suggestions for improvements. The origin of this memo is
from RFC 1269 "Definitions of Managed Objects for the Board Gateway from RFC 1269 "Definitions of Managed Objects for the Board Gateway
Protocol (Version 3)" written by the first two authors of this memo. Protocol (Version 3)" written by the first two authors of this memo,
which was updated to support BGP-4 in RFC 1657. This memo fixes errors
introduced when the MIB was converted to use the SNMPv2 SMI.
Distribution of this memo is unlimited. Please forward comments to Distribution of this memo is unlimited. Please forward comments to
bgp@ans.net. bgp@ans.net.
1. Introduction 1. Introduction
This memo defines an experimental portion of the Management Information This memo defines an experimental portion of the Management Information
Base (MIB) for use with network management protocols in the Internet Base (MIB) for use with network management protocols in the Internet
Expiration Date May 1996 [Page 1]FORMFEED
community. In particular, it describes managed objects used for community. In particular, it describes managed objects used for
managing the Border Gateway Protocol Version 4 or lower [1, 2]. managing the Border Gateway Protocol Version 4 or lower [1, 2].
2. The SNMPv2 Network Management Framework 2. The SNMPv2 Network Management Framework
The SNMPv2 Network Management Framework consists of four major The SNMPv2 Network Management Framework consists of four major
components. They are: components. They are:
RFC 1442 which defines the SMI, the mechanisms used for describing RFC 1442 which defines the SMI, the mechanisms used for describing
and naming objects for the purpose of management. and naming objects for the purpose of management.
skipping to change at line 90 skipping to change at line 92
termed the descriptor, to refer to the object type. termed the descriptor, to refer to the object type.
4. Overview 4. 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 Table, 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 connections contains information about state and current activity of connections
Expiration Date May 1996 [Page 2]FORMFEED
with the BGP peers. The Received Path Attribute Table contains path with the BGP peers. The Received Path Attribute Table contains path
attributes received from all peers running BGP version 3 or less. The attributes received from all peers running BGP version 3 or less. The
BGP-4 Received Path Attribute Table contains path attributes received BGP-4 Received Path Attribute Table contains path attributes received
from all BGP-4 peers. The actual attributes used in determining a route 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 are a subset of the received attribute tables after local routing policy
has been applied. has been applied.
5. Definitions 5. 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 IpAddress, Integer32, Counter32, Gauge32
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF
mib-2 mib-2
FROM RFC1213-MIB; FROM RFC1213-MIB;
bgp MODULE-IDENTITY bgp MODULE-IDENTITY
LAST-UPDATED "9511090000Z" LAST-UPDATED "9512110000Z"
ORGANIZATION "IETF BGP Working Group" ORGANIZATION "IETF BGP Working Group"
CONTACT-INFO CONTACT-INFO
" John Chu (Editor) " John Chu (Editor)
Postal: IBM Corp. Postal: IBM Corp.
P.O.Box 704 P.O.Box 704
Yorktown Heights, NY 10598 Yorktown Heights, NY 10598
US US
Tel: +1 914 784 7839 Tel: +1 914 784 7839
Fax: +1 914 784 6205 Fax: +1 914 784 6205
E-mail: jychu@watson.ibm.com" E-mail: jychu@watson.ibm.com
Jeff Johnson (Editor)
Postal: cisco Systems
170 W. Tasman Drive
San Jose, CA 95134
Tel: +1 408 526 7789
Fax: +1 408 526 4860
E-mail: jjohnson@cisco.com"
DESCRIPTION DESCRIPTION
"The MIB module for BGP-4." "The MIB module for BGP-4."
REVISION "9601080000Z"
DESCRIPTION
"1) Fixed the definitions of the traps to
make them equivalent to their initial
definition in RFC 1269.
2) Added compliance and conformance info."
::= { 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
7, the second octet contains bits 8 to 15, 7, the second octet contains bits 8 to 15,
Expiration Date May 1996 [Page 3]FORMFEED
and so on, with the most significant bit and so on, with the most significant bit
referring to the lowest bit number in the referring to the lowest bit number in the
octet (e.g., the MSB of the first octet octet (e.g., the MSB of the first octet
refers to bit 0). If a bit, i, is present refers to bit 0). If a bit, i, is present
and set, then the version (i+1) of the BGP and set, then the version (i+1) of the BGP
is supported." is supported."
::= { bgp 1 } ::= { bgp 1 }
bgpLocalAs OBJECT-TYPE bgpLocalAs OBJECT-TYPE
SYNTAX INTEGER (0..65535) SYNTAX INTEGER (0..65535)
skipping to change at line 187 skipping to change at line 201
INDEX { bgpPeerRemoteAddr } INDEX { bgpPeerRemoteAddr }
::= { bgpPeerTable 1 } ::= { bgpPeerTable 1 }
BgpPeerEntry ::= SEQUENCE { BgpPeerEntry ::= SEQUENCE {
bgpPeerIdentifier bgpPeerIdentifier
IpAddress, IpAddress,
bgpPeerState bgpPeerState
INTEGER, INTEGER,
bgpPeerAdminStatus bgpPeerAdminStatus
INTEGER, INTEGER,
Expiration Date May 1996 [Page 4]FORMFEED
bgpPeerNegotiatedVersion bgpPeerNegotiatedVersion
Integer32, Integer32,
bgpPeerLocalAddr bgpPeerLocalAddr
IpAddress, IpAddress,
bgpPeerLocalPort bgpPeerLocalPort
INTEGER, INTEGER,
bgpPeerRemoteAddr bgpPeerRemoteAddr
IpAddress, IpAddress,
bgpPeerRemotePort bgpPeerRemotePort
INTEGER, INTEGER,
skipping to change at line 237 skipping to change at line 249
bgpPeerMinRouteAdvertisementInterval bgpPeerMinRouteAdvertisementInterval
INTEGER, INTEGER,
bgpPeerInUpdateElapsedTime bgpPeerInUpdateElapsedTime
Gauge32 Gauge32
} }
bgpPeerIdentifier OBJECT-TYPE bgpPeerIdentifier OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
Expiration Date May 1996 [Page 5]FORMFEED
DESCRIPTION DESCRIPTION
"The BGP Identifier of this entry's BGP peer." "The BGP Identifier of this entry's BGP peer."
::= { bgpPeerEntry 1 } ::= { bgpPeerEntry 1 }
bgpPeerState OBJECT-TYPE bgpPeerState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
idle(1), idle(1),
connect(2), connect(2),
active(3), active(3),
opensent(4), opensent(4),
skipping to change at line 287 skipping to change at line 297
bgpPeerNegotiatedVersion OBJECT-TYPE bgpPeerNegotiatedVersion OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
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."
::= { bgpPeerEntry 4 } ::= { bgpPeerEntry 4 }
bgpPeerLocalAddr OBJECT-TYPE bgpPeerLocalAddr OBJECT-TYPE
Expiration Date May 1996 [Page 6]FORMFEED
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 }
bgpPeerLocalPort OBJECT-TYPE bgpPeerLocalPort OBJECT-TYPE
SYNTAX INTEGER (0..65535) SYNTAX INTEGER (0..65535)
skipping to change at line 337 skipping to change at line 345
bgpPeerRemoteAs OBJECT-TYPE bgpPeerRemoteAs OBJECT-TYPE
SYNTAX INTEGER (0..65535) SYNTAX INTEGER (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The remote autonomous system number." "The remote autonomous system number."
::= { bgpPeerEntry 9 } ::= { bgpPeerEntry 9 }
bgpPeerInUpdates OBJECT-TYPE bgpPeerInUpdates OBJECT-TYPE
Expiration Date May 1996 [Page 7]FORMFEED
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of BGP UPDATE messages received on "The number of BGP UPDATE messages received on
this connection. This object should be this connection. This object should be
initialized to zero (0) when the connection is initialized to zero (0) when the connection is
established." established."
::= { bgpPeerEntry 10 } ::= { bgpPeerEntry 10 }
skipping to change at line 387 skipping to change at line 393
the remote peer on this connection. This object the remote peer on this connection. This object
should be initialized to zero when the should be initialized to zero when the
connection is established." connection is established."
::= { 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
Expiration Date May 1996 [Page 8]FORMFEED
"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
first byte of this two byte OCTET STRING first byte of this two byte OCTET STRING
contains the error code, and the second byte contains the error code, and the second byte
contains the subcode." contains the subcode."
::= { bgpPeerEntry 14 } ::= { bgpPeerEntry 14 }
bgpPeerFsmEstablishedTransitions OBJECT-TYPE bgpPeerFsmEstablishedTransitions OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
skipping to change at line 437 skipping to change at line 441
bgpPeerHoldTime OBJECT-TYPE bgpPeerHoldTime OBJECT-TYPE
SYNTAX INTEGER ( 0 | 3..65535 ) SYNTAX INTEGER ( 0 | 3..65535 )
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Time interval in seconds for the Hold Timer "Time interval in seconds for the Hold Timer
established with the peer. The value of this established with the peer. The value of this
object is calculated by this BGP speaker by object is calculated by this BGP speaker by
using the smaller of the value in using the smaller of the value in
Expiration Date May 1996 [Page 9]FORMFEED
bgpPeerHoldTimeConfigured and the Hold Time bgpPeerHoldTimeConfigured and the Hold Time
received in the OPEN message. This value received in the OPEN message. This value
must be at lease three seconds if it is not must be at lease three seconds if it is not
zero (0) in which case the Hold Timer has zero (0) in which case the Hold Timer has
not been established with the peer, or, the not been established with the peer, or, the
value of bgpPeerHoldTimeConfigured is zero (0)." value of bgpPeerHoldTimeConfigured is zero (0)."
::= { bgpPeerEntry 18 } ::= { bgpPeerEntry 18 }
bgpPeerKeepAlive OBJECT-TYPE bgpPeerKeepAlive OBJECT-TYPE
SYNTAX INTEGER ( 0 | 1..21845 ) SYNTAX INTEGER ( 0 | 1..21845 )
skipping to change at line 487 skipping to change at line 489
must not be less than three seconds if it is not must not be less than three seconds if it is not
zero (0) in which case the Hold Time is NOT to be zero (0) in which case the Hold Time is NOT to be
established with the peer. The suggested value for established with the peer. The suggested value for
this timer is 90 seconds." this timer is 90 seconds."
::= { bgpPeerEntry 20 } ::= { bgpPeerEntry 20 }
bgpPeerKeepAliveConfigured OBJECT-TYPE bgpPeerKeepAliveConfigured OBJECT-TYPE
SYNTAX INTEGER ( 0 | 1..21845 ) SYNTAX INTEGER ( 0 | 1..21845 )
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
Expiration Date May 1996 [Page 10]FORMFEED
DESCRIPTION DESCRIPTION
"Time interval in seconds for the KeepAlive timer "Time interval in seconds for the KeepAlive timer
configured for this BGP speaker with this peer. configured for this BGP speaker with this peer.
The value of this object will only determine the The value of this object will only determine the
KEEPALIVE messages' frequency relative to the value KEEPALIVE messages' frequency relative to the value
specified in bgpPeerHoldTimeConfigured; the actual specified in bgpPeerHoldTimeConfigured; the actual
time interval for the KEEPALIVE messages is time interval for the KEEPALIVE messages is
indicated by bgpPeerKeepAlive. A reasonable maximu indicated by bgpPeerKeepAlive. A reasonable
m maximum value for this timer would be configured to
value for this timer would be configured to be one be one third of that of bgpPeerHoldTimeConfigured.
third of that of bgpPeerHoldTimeConfigured.
If the value of this object is zero (0), no If the value of this object is zero (0), no
periodical KEEPALIVE messages are sent to the peer periodical KEEPALIVE messages are sent to the peer
after the BGP connection has been established. The after the BGP connection has been established. The
suggested value for this timer is 30 seconds." suggested value for this timer is 30 seconds."
::= { bgpPeerEntry 21 } ::= { bgpPeerEntry 21 }
bgpPeerMinASOriginationInterval OBJECT-TYPE bgpPeerMinASOriginationInterval OBJECT-TYPE
SYNTAX INTEGER (1..65535) SYNTAX INTEGER (1..65535)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
skipping to change at line 537 skipping to change at line 536
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 (0)." the value of this object is set to zero (0)."
::= { bgpPeerEntry 24 } ::= { bgpPeerEntry 24 }
Expiration Date May 1996 [Page 11]FORMFEED
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 }
-- Received Path Attribute Table. This table contains, -- Received Path Attribute Table. This table contains,
-- one entry per path to a network, path attributes -- one entry per path to a network, path attributes
-- received from all peers running BGP version 3 or less. -- received from all peers running BGP version 3 or less.
-- This table is deprecated. -- This table is obsolete, having been replaced in
-- functionality with the bgp4PathAttrTable.
bgpRcvdPathAttrTable OBJECT-TYPE bgpRcvdPathAttrTable OBJECT-TYPE
SYNTAX SEQUENCE OF BgpPathAttrEntry SYNTAX SEQUENCE OF BgpPathAttrEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The BGP Received Path Attribute Table contains "The BGP Received Path Attribute Table contains
information about paths to destination networks information about paths to destination networks
received from all peers running BGP version 3 or received from all peers running BGP version 3 or
less." less."
skipping to change at line 584 skipping to change at line 583
IpAddress, IpAddress,
bgpPathAttrDestNetwork bgpPathAttrDestNetwork
IpAddress, IpAddress,
bgpPathAttrOrigin bgpPathAttrOrigin
INTEGER, INTEGER,
bgpPathAttrASPath bgpPathAttrASPath
OCTET STRING, OCTET STRING,
bgpPathAttrNextHop bgpPathAttrNextHop
IpAddress, IpAddress,
bgpPathAttrInterASMetric bgpPathAttrInterASMetric
Expiration Date May 1996 [Page 12]FORMFEED
Integer32 Integer32
} }
bgpPathAttrPeer OBJECT-TYPE bgpPathAttrPeer OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The IP address of the peer where the path "The IP address of the peer where the path
information was learned." information was learned."
skipping to change at line 634 skipping to change at line 631
the network. This object is probably best the network. This object is probably best
represented as SEQUENCE OF INTEGER. For SMI represented as SEQUENCE OF INTEGER. For SMI
compatibility, though, it is represented as compatibility, though, it is represented as
OCTET STRING. Each AS is represented as a pair OCTET STRING. Each AS is represented as a pair
of octets according to the following algorithm: of octets according to the following algorithm:
first-byte-of-pair = ASNumber / 256; first-byte-of-pair = ASNumber / 256;
second-byte-of-pair = ASNumber & 255;" second-byte-of-pair = ASNumber & 255;"
::= { bgpPathAttrEntry 4 } ::= { bgpPathAttrEntry 4 }
Expiration Date May 1996 [Page 13]FORMFEED
bgpPathAttrNextHop OBJECT-TYPE bgpPathAttrNextHop OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS obsolete STATUS obsolete
DESCRIPTION DESCRIPTION
"The address of the border router that should "The address of the border router that should
be used for the destination network." be used for the destination network."
::= { bgpPathAttrEntry 5 } ::= { bgpPathAttrEntry 5 }
bgpPathAttrInterASMetric OBJECT-TYPE bgpPathAttrInterASMetric OBJECT-TYPE
skipping to change at line 681 skipping to change at line 677
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a path to a network." "Information about a path to a network."
INDEX { bgp4PathAttrIpAddrPrefix, INDEX { bgp4PathAttrIpAddrPrefix,
bgp4PathAttrIpAddrPrefixLen, bgp4PathAttrIpAddrPrefixLen,
bgp4PathAttrPeer } bgp4PathAttrPeer }
::= { bgp4PathAttrTable 1 } ::= { bgp4PathAttrTable 1 }
Bgp4PathAttrEntry ::= SEQUENCE { Bgp4PathAttrEntry ::= SEQUENCE {
bgp4PathAttrPeer bgp4PathAttrPeer
Expiration Date May 1996 [Page 14]FORMFEED
IpAddress, IpAddress,
bgp4PathAttrIpAddrPrefixLen bgp4PathAttrIpAddrPrefixLen
INTEGER, INTEGER,
bgp4PathAttrIpAddrPrefix bgp4PathAttrIpAddrPrefix
IpAddress, IpAddress,
bgp4PathAttrOrigin bgp4PathAttrOrigin
INTEGER, INTEGER,
bgp4PathAttrASPathSegment bgp4PathAttrASPathSegment
OCTET STRING, OCTET STRING,
bgp4PathAttrNextHop bgp4PathAttrNextHop
skipping to change at line 731 skipping to change at line 724
bgp4PathAttrIpAddrPrefixLen OBJECT-TYPE bgp4PathAttrIpAddrPrefixLen OBJECT-TYPE
SYNTAX INTEGER (0..32) SYNTAX INTEGER (0..32)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Length in bits of the IP address prefix in the "Length in bits of the IP address prefix in the
Network Layer Reachability Information field." Network Layer Reachability Information field."
::= { bgp4PathAttrEntry 2 } ::= { bgp4PathAttrEntry 2 }
Expiration Date May 1996 [Page 15]FORMFEED
bgp4PathAttrIpAddrPrefix OBJECT-TYPE bgp4PathAttrIpAddrPrefix OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An IP address prefix in the Network Layer "An IP address prefix in the Network Layer
Reachability Information field. This object Reachability Information field. This object
is an IP address containing the prefix with is an IP address containing the prefix with
length specified by bgp4PathAttrIpAddrPrefixLen. length specified by bgp4PathAttrIpAddrPrefixLen.
Any bits beyond the length specified by Any bits beyond the length specified by
skipping to change at line 780 skipping to change at line 772
has traversed has traversed
2 AS_SEQUENCE: ordered set of ASs 2 AS_SEQUENCE: ordered set of ASs
a route in the UPDATE message a route in the UPDATE message
has traversed. has traversed.
The length is a 1-octet field containing the The length is a 1-octet field containing the
number of ASs in the value field. number of ASs in the value field.
The value field contains one or more AS The value field contains one or more AS
numbers, each AS is represented in the octet numbers, each AS is represented in the octet
Expiration Date May 1996 [Page 16]FORMFEED
string as a pair of octets according to the string as a pair of octets according to the
following algorithm: following algorithm:
first-byte-of-pair = ASNumber / 256; first-byte-of-pair = ASNumber / 256;
second-byte-of-pair = ASNumber & 255;" second-byte-of-pair = ASNumber & 255;"
::= { bgp4PathAttrEntry 5 } ::= { bgp4PathAttrEntry 5 }
bgp4PathAttrNextHop OBJECT-TYPE bgp4PathAttrNextHop OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at line 830 skipping to change at line 820
SYNTAX INTEGER { SYNTAX INTEGER {
lessSpecificRrouteNotSelected(1), lessSpecificRrouteNotSelected(1),
lessSpecificRouteSelected(2) lessSpecificRouteSelected(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Whether or not a system has selected "Whether or not a system has selected
a less specific route without selecting a a less specific route without selecting a
more specific route." more specific route."
Expiration Date May 1996 [Page 17]FORMFEED
::= { bgp4PathAttrEntry 9 } ::= { bgp4PathAttrEntry 9 }
bgp4PathAttrAggregatorAS OBJECT-TYPE bgp4PathAttrAggregatorAS OBJECT-TYPE
SYNTAX INTEGER (0..65535) SYNTAX INTEGER (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The AS number of the last BGP4 speaker that "The AS number of the last BGP4 speaker that
performed route aggregation. A value of zero (0) performed route aggregation. A value of zero (0)
indicates the absence of this attribute." indicates the absence of this attribute."
skipping to change at line 880 skipping to change at line 868
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."
::= { 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
Expiration Date May 1996 [Page 18]FORMFEED
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"One or more path attributes not understood "One or more path attributes not understood
by this BGP4 speaker. Size zero (0) indicates by this BGP4 speaker. Size zero (0) indicates
the absence of such attribute(s). Octets the absence of such attribute(s). Octets
beyond the maximum size, if any, are not beyond the maximum size, if any, are not
recorded by this object." recorded by this object."
::= { bgp4PathAttrEntry 14 } ::= { bgp4PathAttrEntry 14 }
-- Traps. -- Traps.
bgpTraps OBJECT IDENTIFIER ::= { bgp 7 } -- note that in RFC 1657, bgpTraps was incorrectly
-- assigned a value of { bgp 7 }, and each of the
-- traps had the bgpPeerRemoteAddr object inappropriately
-- removed from their OBJECTS clause. The following
-- definitions restore the semantics of the traps as
-- they were initially defined in RFC 1269.
-- { bgp 7 } is unused
bgpTraps OBJECT IDENTIFIER ::= { bgp 0 }
bgpEstablished NOTIFICATION-TYPE bgpEstablished NOTIFICATION-TYPE
OBJECTS { bgpPeerLastError, OBJECTS { bgpPeerRemoteAddr,
bgpPeerLastError,
bgpPeerState } bgpPeerState }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The BGP Established event is generated when "The BGP Established event is generated when
the BGP FSM enters the ESTABLISHED state." the BGP FSM enters the ESTABLISHED state."
::= { bgpTraps 1 } ::= { bgpTraps 1 }
bgpBackwardTransition NOTIFICATION-TYPE bgpBackwardTransition NOTIFICATION-TYPE
OBJECTS { bgpPeerLastError, OBJECTS { bgpPeerRemoteAddr,
bgpPeerLastError,
bgpPeerState } bgpPeerState }
STATUS current 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."
::= { bgpTraps 2 } ::= { bgpTraps 2 }
-- conformance information
bgpMIBConformance OBJECT IDENTIFIER ::= { bgp 8 }
bgpMIBCompliances OBJECT IDENTIFIER ::= { bgpMIBConformance 1 }
bgpMIBGroups OBJECT IDENTIFIER ::= { bgpMIBConformance 2 }
-- compliance statements
bgpMIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for entities which
implement the BGP4 mib."
MODULE -- this module
MANDATORY-GROUPS { bgp4MIBGlobalsGroup,
bgp4MIBPeerGroup,
bgp4MIBPathAttrGroup,
bgp4MIBNotificationGroup }
::= { bgpMIBCompliances 1 }
-- units of conformance
bgp4MIBGlobalsGroup OBJECT-GROUP
OBJECTS { bgpVersion,
bgpLocalAs,
bgpIdentifier }
STATUS current
DESCRIPTION
"A collection of objects providing information
on global BGP state."
::= { bgpMIBGroups 1 }
bgp4MIBPeerGroup OBJECT-GROUP
OBJECTS { bgpPeerIdentifier,
bgpPeerState,
bgpPeerAdminStatus,
bgpPeerNegotiatedVersion,
bgpPeerLocalAddr,
bgpPeerLocalPort,
bgpPeerRemoteAddr,
bgpPeerRemotePort,
bgpPeerRemoteAs,
bgpPeerInUpdates,
bgpPeerOutUpdates,
bgpPeerInTotalMessages,
bgpPeerOutTotalMessages,
bgpPeerLastError,
bgpPeerFsmEstablishedTransitions,
bgpPeerFsmEstablishedTime,
bgpPeerConnectRetryInterval,
bgpPeerHoldTime,
bgpPeerKeepAlive,
bgpPeerHoldTimeConfigured,
bgpPeerKeepAliveConfigured,
bgpPeerMinASOriginationInterval,
bgpPeerMinRouteAdvertisementInterval,
bgpPeerInUpdateElapsedTime }
STATUS current
DESCRIPTION
"A collection of objects for managing
BGP peers."
::= { bgpMIBGroups 2 }
bgp4MIBRcvdPathAttrGroup OBJECT-GROUP
OBJECTS { bgpPathAttrPeer,
bgpPathAttrDestNetwork,
bgpPathAttrOrigin,
bgpPathAttrASPath,
bgpPathAttrNextHop,
bgpPathAttrInterASMetric }
STATUS obsolete
DESCRIPTION
"A collection of objects for managing BGP
path entries.
This conformance group is obsolete,
replaced by bgp4MIBPathAttrGroup."
::= { bgpMIBGroups 3 }
bgp4MIBPathAttrGroup OBJECT-GROUP
OBJECTS { bgp4PathAttrPeer,
bgp4PathAttrIpAddrPrefixLen,
bgp4PathAttrIpAddrPrefix,
bgp4PathAttrOrigin,
bgp4PathAttrASPathSegment,
bgp4PathAttrNextHop,
bgp4PathAttrMultiExitDisc,
bgp4PathAttrLocalPref,
bgp4PathAttrAtomicAggregate,
bgp4PathAttrAggregatorAS,
bgp4PathAttrAggregatorAddr,
bgp4PathAttrCalcLocalPref,
bgp4PathAttrBest,
bgp4PathAttrUnknown }
STATUS current
DESCRIPTION
"A collection of objects for managing
BGP path entries."
::= { bgpMIBGroups 4 }
bgp4MIBNotiicationGroup NOTIFICATION-GROUP
NOTIFICATIONS { bgpEstablished,
bgpBackwardTransition }
STATUS current
DESCRIPTION
"A collection of notifications for signaling
changes in BGP peer relationships."
::= { bgpMIBGroups 4 }
END END
6. Acknowledgements 6. 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
Interconnectivity Working Group, and particularly the following Interconnectivity Working Group, and particularly the following
individuals: individuals:
Yakov Rekhter, cisco Systems Yakov Rekhter, cisco Systems
Rob Coltun, Fore Rob Coltun, Fore
Guy Almes, ANS Guy Almes, ANS
Jeff Honig, Cornell Theory Center Jeff Honig, Cornell Theory Center
Marshall T. Rose, Dover Beach Consulting, Inc. Marshall T. Rose, Dover Beach Consulting, Inc.
Expiration Date May 1996 [Page 19]FORMFEED
Dennis Ferguson, Ipsilon Dennis Ferguson, Ipsilon
Mike Mathis, PSC Mike Mathis, PSC
John Krawczyk, BayNetworks John Krawczyk, BayNetworks
Curtis Villamizar, ANS Curtis Villamizar, ANS
Dave LeRoy, Pencom Systems Dave LeRoy, Pencom Systems
Paul Traina, cisco Systems Paul Traina, cisco Systems
Andrew Partan, UUNET Andrew Partan, UUNET
Robert Snyder, cisco Systems Robert Snyder, cisco Systems
Dimitry Haskin, BayNetworks Dimitry Haskin, BayNetworks
Peder Chr Norgaard, Telebit Communications A/S Peder Chr Norgaard, Telebit Communications A/S
Joel Halpern, NewBridge Joel Halpern, NewBridge
Nick Thille, cisco Systems
7. References 7. References
[1] Rekhter, Y., Li, T., "A Border Gateway Protocol 4 (BGP-4)", [1] Rekhter, Y., Li, T., "A Border Gateway Protocol 4 (BGP-4)",
RFC1771, March 1995 RFC1771, March 1995
[2] Rekhter, Y., Gross, P., "Application of the Border [2] Rekhter, Y., Gross, P., "Application of the Border
Gateway Protocol in the Internet", RFC1772, March 1995 Gateway Protocol in the Internet", RFC1772, March 1995
8. Security Considerations 8. Security Considerations
Security issues are not discussed in this memo. Security issues are not discussed in this memo.
Authors' Address Authors' Address
Steven Willis Steven Willis
BayNetworks BayNetworks
15 Crosby Drive 15 Crosby Drive
Bedford, MA 01730 Bedford, MA 01730
Phone: (617) 275-2400 Phone: +1 617 275 2400
Email: swillis@baynetworks.com Email: swillis@baynetworks.com
John Burruss John Burruss
BayNetworks BayNetworks
15 Crosby Drive 15 Crosby Drive
Bedford, MA 01730 Bedford, MA 01730
Phone: (617) 275-2400 Phone: +1 617 275 2400
Email: jburruss@baynetworks.com Email: jburruss@baynetworks.com
Expiration Date May 1996 [Page 20]FORMFEED
John Chu John Chu
IBM Corp. IBM Corporation
P.O.Box 704 P.O.Box 704
Yorktown Heights, NY 10598 Yorktown Heights, NY 10598
Phone: (914) 784-7839 Phone: +1 914 784 7839
Email: jychu@watson.ibm.com Email: jychu@watson.ibm.com
Expiration Date May 1996 [Page 21]FORMFEED Jeff Johnson
cisco Systems
170 W. Tasman Drive
San Jose, CA 95134
Phone: +1 408 526 7789
Email: jjohnson@cisco.com
 End of changes. 

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