draft-ietf-idr-bgp4-mib-05.txt   draft-ietf-idr-bgp4-mib-06.txt 
skipping to change at page 1, line 13 skipping to change at page 1, line 13
Network Working Group S. Hares Network Working Group S. Hares
INTERNET DRAFT NextHop INTERNET DRAFT NextHop
J. Haas J. Haas
NextHop NextHop
S. Willis S. Willis
Argon Networks Argon Networks
J. Burruss J. Burruss
WinData WinData
J. Chu J. Chu
Cosine Cosine
December 2000 February 2000
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-06.txt>
<draft-ietf-idr-bgp4-mib-05.txt>
Status of this Memo 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.
skipping to change at page 2, line 31 skipping to change at page 2, line 31
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 [1, 2]. Border Gateway Protocol Version 4 or lower [1, 2].
2. The SNMP Network Management Framework 2. The SNMP Network Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2271 [3]. +o An overall architecture, described in RFC 2271 [3].
o bgp Mechanisms for describing and naming objects and events for
the purpose of management. The first version of this
Structure of Management Information (SMI) is called SMIv1 and
described in RFC 1155 [4], RFC 1212 [5] and RFC 1215 [6]. The
second version, called SMIv2, is described in RFC 1902 [7],
RFC 1903 [8] and RFC 1904 [9].
o Message protocols for transferring management information. +o bgp Mechanisms for describing and naming objects and events for
The first version of the SNMP message protocol is called the purpose of management. The first version of this Structure
SNMPv1 and described in RFC 1157 [10]. A second version of of Management Information (SMI) is called SMIv1 and described in
the SNMP message protocol, which is not an Internet standards RFC 1155 [4], RFC 1212 [5] and RFC 1215 [6]. The second version,
track protocol, is called SNMPv2c and described in RFC 1901 called SMIv2, is described in RFC 1902 [7], RFC 1903 [8] and RFC
[11] and RFC 1906 [12]. The third version of the message 1904 [9].
protocol is called SNMPv3 and described in RFC 1906 [12], RFC
2272 [13] and RFC 2274 [14].
o Protocol operations for accessing management information. The +o Message protocols for transferring management information. The
first set of protocol operations and associated PDU formats first version of the SNMP message protocol is called SNMPv1 and
is described in RFC 1157 [10]. A second set of protocol described in RFC 1157 [10]. A second version of the SNMP message
operations and associated PDU formats is described in RFC protocol, which is not an Internet standards track protocol, is
1905 [15]. called SNMPv2c and described in RFC 1901 [11] and RFC 1906 [12].
The third version of the message protocol is called SNMPv3 and
described in RFC 1906 [12], RFC 2272 [13] and RFC 2274 [14].
o A set of fundamental applications described in RFC 2273 [16] +o Protocol operations for accessing management information. The
and the view-based access control mechanism described in RFC first set of protocol operations and associated PDU formats is
2275 [17]. described in RFC 1157 [10]. A second set of protocol operations
and associated PDU formats is described in RFC 1905 [15].
Managed objects are accessed via a virtual information store, termed +o A set of fundamental applications described in RFC 2273 [16] and
the Management Information Base or MIB. Objects in the MIB are the view-based access control mechanism described in RFC 2275
defined using the mechanisms defined in the SMI. [17].
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.
skipping to change at page 5, line 24 skipping to change at page 4, line 24
FROM SNMPv2-CONF; FROM SNMPv2-CONF;
bgp MODULE-IDENTITY bgp MODULE-IDENTITY
LAST-UPDATED "0012100000Z" LAST-UPDATED "0012100000Z"
ORGANIZATION "IETF IDR Working Group" ORGANIZATION "IETF IDR Working Group"
CONTACT-INFO "E-mail: idr@merit.net CONTACT-INFO "E-mail: idr@merit.net
Susan Hares (Editor) Susan Hares (Editor)
517 W. William Street 517 W. William Street
Ann Arbor, MI 48103-4943 Ann Arbor, MI 48103-4943
Tel: +1 734 936 2095 Tel: +1 734 973-2200
Fax: +1 734 615-3241 Fax: +1 734 615-3241
E-mail: skh@nexthop.com" E-mail: skh@nexthop.com"
DESCRIPTION DESCRIPTION
"Cleanup to conform with draft-12 of BGP.
Updated semantics of MED and localpref.
Adjusted sizes of objects to match draft.
Changed the semantics of bgp4PathAttrUnknown."
REVISION "200102240000Z"
DESCRIPTION
"The MIB module for BGP-4." "The MIB module for BGP-4."
REVISION "0012100000Z" REVISION "0012100000Z"
DESCRIPTION DESCRIPTION
"Corrected duplicate OBJECT IDENTIFIER "Corrected duplicate OBJECT IDENTIFIER
assignment in the conformance information." assignment in the conformance information."
REVISION "9601080000Z" REVISION "9601080000Z"
DESCRIPTION DESCRIPTION
"1) Fixed the definitions of the traps to "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-10.txt for value of
bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref, bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref,
bgp4PathAttrCalcLocalPref,bgp4PathAttrMultiExitDisc, bgp4PathAttrCalcLocalPref,bgp4PathAttrMultiExitDisc,
bgp4PathAttrASPathSegement." bgp4PathAttrASPathSegement."
::= { mib-2 15 } ::= { mib-2 15 }
bgpVersion OBJECT-TYPE bgpVersion OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1..32)) --- change to match draft SYNTAX OCTET STRING (SIZE (1..32))
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,
and so on, with the most significant bit and so on, with the most significant bit
skipping to change at page 9, line 4 skipping to change at page 8, line 19
the BGP Start Event to be generated. A the BGP Start Event to be generated. A
transition from 'start' to 'stop' will cause transition from 'start' to 'stop' will cause
the BGP Stop Event to be generated. This the BGP Stop Event to be generated. This
parameter can be used to restart BGP peer parameter can be used to restart BGP peer
connections. Care should be used in providing connections. Care should be used in providing
write access to this object without adequate write access to this object without adequate
authentication." authentication."
::= { bgpPeerEntry 3 } ::= { bgpPeerEntry 3 }
bgpPeerNegotiatedVersion OBJECT-TYPE bgpPeerNegotiatedVersion OBJECT-TYPE
SYNTAX Integer[1..255] --- change to match draft SYNTAX INTEGER (1..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."
::= { bgpPeerEntry 4 } ::= { bgpPeerEntry 4 }
bgpPeerLocalAddr OBJECT-TYPE bgpPeerLocalAddr OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 15, line 36 skipping to change at page 15, line 27
bgpPathAttrDestNetwork OBJECT-TYPE bgpPathAttrDestNetwork OBJECT-TYPE
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 Integer32 {
igp(1),-- networks are interior igp(1),-- networks are interior
egp(2),-- networks learned via EGP egp(2),-- networks learned via EGP
incomplete(3) -- undetermined incomplete(3) -- undetermined
} }
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 }
skipping to change at page 17, line 17 skipping to change at page 17, line 17
"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
IpAddress, IpAddress,
bgp4PathAttrIpAddrPrefixLen bgp4PathAttrIpAddrPrefixLen
INTEGER, Integer32,
bgp4PathAttrIpAddrPrefix bgp4PathAttrIpAddrPrefix
IpAddress, IpAddress,
bgp4PathAttrOrigin bgp4PathAttrOrigin
INTEGER, Integer32,
bgp4PathAttrASPathSegment bgp4PathAttrASPathSegment
OCTET STRING, OCTET STRING,
bgp4PathAttrNextHop bgp4PathAttrNextHop
IpAddress, IpAddress,
bgp4PathAttrMultiExitDisc bgp4PathAttrMultiExitDisc
INTEGER, Integer32,
bgp4PathAttrLocalPref bgp4PathAttrLocalPref
INTEGER, Integer32,
bgp4PathAttrAtomicAggregate bgp4PathAttrAtomicAggregate
INTEGER, Integer32,
bgp4PathAttrAggregatorAS bgp4PathAttrAggregatorAS
INTEGER, Integer32,
bgp4PathAttrAggregatorAddr bgp4PathAttrAggregatorAddr
IpAddress, IpAddress,
bgp4PathAttrCalcLocalPref bgp4PathAttrCalcLocalPref
INTEGER, Integer32,
bgp4PathAttrBest bgp4PathAttrBest
INTEGER, Integer32,
bgp4PathAttrUnknown bgp4PathAttrUnknown
OCTET STRING OCTET STRING
} }
bgp4PathAttrPeer OBJECT-TYPE bgp4PathAttrPeer OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the peer where the path "The IP address of the peer where the path
skipping to change at page 18, line 39 skipping to change at page 18, line 42
egp(2),-- networks learned via EGP egp(2),-- networks learned via EGP
incomplete(3) -- undetermined incomplete(3) -- undetermined
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ultimate origin of the path information." "The ultimate origin of the path information."
::= { bgp4PathAttrEntry 4 } ::= { bgp4PathAttrEntry 4 }
bgp4PathAttrASPathSegment OBJECT-TYPE bgp4PathAttrASPathSegment OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (2..500)) --- [change 3 possible to have 500*4 bytes of aSpath] SYNTAX OCTET STRING (SIZE (0..4096))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The sequence of AS path segments. Each AS "The sequence of AS path segments. Each AS
path segment is represented by a triple path segment is represented by a triple
<type, length, value>. <type, length, value>.
The type is a 1-octet field which has two The type is a 1-octet field which has two
possible values: possible values:
1 AS_SET: unordered set of ASs a 1 AS_SET: unordered set of ASs a
skipping to change at page 19, line 32 skipping to change at page 19, line 42
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address of the border router that should "The address of the border router that should
be used for the destination network. This be used for the destination network. This
address is the nexthop address received in address is the nexthop address received in
the UPDATE packet." the UPDATE packet."
::= { bgp4PathAttrEntry 6 } ::= { bgp4PathAttrEntry 6 }
bgp4PathAttrMultiExitDisc OBJECT-TYPE bgp4PathAttrMultiExitDisc OBJECT-TYPE
SYNTAX INTEGER (0..4294967295) SYNTAX Integer32 (0..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This metric is used to discriminate between "This metric is used to discriminate between
multiple exit points to an adjacent autonomous multiple exit points to an adjacent autonomous
system. A value of -1 (4294967295) indicates the absence of system. A value of -1 (4294967295) indicates
this attribute." the absence of this attribute.
Note that this precludes the representation of
the maximum value for this attribute. Previously
the variable held only 2^31 bits of information
which covered only half the allowed values
and reserved -1 for not present."
::= { bgp4PathAttrEntry 7 } ::= { bgp4PathAttrEntry 7 }
bgp4PathAttrLocalPref OBJECT-TYPE bgp4PathAttrLocalPref OBJECT-TYPE
SYNTAX INTEGER (0..4294967295) SYNTAX Integer32 (0..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The originating BGP4 speaker's degree of "The originating BGP4 speaker's degree of
preference for an advertised route. A value of preference for an advertised route. A value of
-1 (4294967295) indicates the absence of this attribute." -1 (4294967295) indicates the absence of this
attribute.
Note that this precludes the representation of
the maximum value for this attribute. Previously
the variable held only 2^31 bits of information
which covered only half the allowed values
and reserved -1 for not present."
::= { bgp4PathAttrEntry 8 } ::= { bgp4PathAttrEntry 8 }
bgp4PathAttrAtomicAggregate OBJECT-TYPE bgp4PathAttrAtomicAggregate OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
lessSpecificRrouteNotSelected(1), lessSpecificRouteNotSelected(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."
::= { bgp4PathAttrEntry 9 } ::= { bgp4PathAttrEntry 9 }
skipping to change at page 20, line 26 skipping to change at page 21, line 12
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."
::= { bgp4PathAttrEntry 10 } ::= { bgp4PathAttrEntry 10 }
bgp4PathAttrAggregatorAddr OBJECT-TYPE bgp4PathAttrAggregatorAddr OBJECT-TYPE
SYNTAX IpAddress propagation of AS path zero] SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP address of the last BGP4 speaker that "The IP address of the last BGP4 speaker that
performed route aggregation. A value of performed route aggregation. A value of
0.0.0.0 indicates the absence of this attribute. 0.0.0.0 indicates the absence of this attribute.
Note propagation of AS of zero is illegal in internet." Note propagation of AS of zero is illegal in
internet."
::= { bgp4PathAttrEntry 11 } ::= { bgp4PathAttrEntry 11 }
bgp4PathAttrCalcLocalPref OBJECT-TYPE bgp4PathAttrCalcLocalPref OBJECT-TYPE
SYNTAX INTEGER (0 ..4294967295) SYNTAX Integer32 (0..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The degree of preference calculated by the "The degree of preference calculated by the
receiving BGP4 speaker for an advertised route. receiving BGP4 speaker for an advertised route.
A value of -1 (4294967295) indicates the absence of this A value of -1 (4294967295) indicates the absence of this
attribute." attribute.
Note that this precludes the representation of
the maximum value for this attribute. Previously
the variable held only 2^31 bits of information
which covered only half the allowed values
and reserved -1 for not present."
::= { bgp4PathAttrEntry 12 } ::= { bgp4PathAttrEntry 12 }
bgp4PathAttrBest OBJECT-TYPE bgp4PathAttrBest OBJECT-TYPE
SYNTAX INTEGER { SYNTAX Integer32 {
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."
::= { bgp4PathAttrEntry 13 } ::= { bgp4PathAttrEntry 13 }
bgp4PathAttrUnknown OBJECT-TYPE [format not specific enough bgp4PathAttrUnknown OBJECT-TYPE
[switch to path format SYNTAX OCTET STRING (SIZE(0..4096))
type length value]
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 this BGP4 speaker. Path attributes are by the base BGP-4 document.
recorded in the Update Path attribute format
of type, length, value. Size zero (0) indicates Path attributes are recorded in the Update
the absence of such attribute(s). Octets Path attribute format of type, length, value.
beyond the maximum size, if any, are not Size zero (0) indicates the absence of such
recorded by this object. " attribute(s). Octets beyond the maximum size,
if any, are not recorded by this object. "
::= { 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.
 End of changes. 

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