--- 1/draft-ietf-idr-bgp4-mib-05.txt 2006-02-04 23:30:43.000000000 +0100 +++ 2/draft-ietf-idr-bgp4-mib-06.txt 2006-02-04 23:30:43.000000000 +0100 @@ -2,27 +2,25 @@ Network Working Group S. Hares INTERNET DRAFT NextHop J. Haas NextHop S. Willis Argon Networks J. Burruss WinData J. Chu Cosine - December 2000 + February 2000 Definitions of Managed Objects - for the Fourth Version of Border Gateway Protocol (BGP-4) - - + Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC 2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. @@ -61,51 +59,45 @@ This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects used for managing the Border Gateway Protocol Version 4 or lower [1, 2]. 2. The SNMP Network Management Framework The SNMP Management Framework presently consists of five major components: - 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 An overall architecture, described in RFC 2271 [3]. - o Message protocols for transferring management information. - The first version of the SNMP message protocol is called - SNMPv1 and described in RFC 1157 [10]. A second version of - the SNMP message protocol, which is not an Internet standards - track protocol, is 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 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 Protocol operations for accessing management information. The - first set of protocol operations and associated PDU formats - is described in RFC 1157 [10]. A second set of protocol - operations and associated PDU formats is described in RFC - 1905 [15]. + +o Message protocols for transferring management information. The + first version of the SNMP message protocol is called SNMPv1 and + described in RFC 1157 [10]. A second version of the SNMP message + protocol, which is not an Internet standards track protocol, is + 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] - and the view-based access control mechanism described in RFC - 2275 [17]. + +o Protocol operations for accessing management information. The + first set of protocol operations and associated PDU formats is + 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 - the Management Information Base or MIB. Objects in the MIB are - defined using the mechanisms defined in the SMI. + +o A set of fundamental applications described in RFC 2273 [16] and + the view-based access control mechanism described in RFC 2275 + [17]. This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB. @@ -149,46 +141,52 @@ FROM SNMPv2-CONF; bgp MODULE-IDENTITY LAST-UPDATED "0012100000Z" ORGANIZATION "IETF IDR Working Group" CONTACT-INFO "E-mail: idr@merit.net Susan Hares (Editor) 517 W. William Street Ann Arbor, MI 48103-4943 - Tel: +1 734 936 2095 + Tel: +1 734 973-2200 Fax: +1 734 615-3241 E-mail: skh@nexthop.com" 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." REVISION "0012100000Z" DESCRIPTION "Corrected duplicate OBJECT IDENTIFIER assignment in the conformance information." 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. 3) Updated for latest BGP information draft-ietf-idr-bgp4-10.txt for value of bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref, bgp4PathAttrCalcLocalPref,bgp4PathAttrMultiExitDisc, bgp4PathAttrASPathSegement." ::= { mib-2 15 } bgpVersion OBJECT-TYPE - SYNTAX OCTET STRING (SIZE (1..32)) --- change to match draft + SYNTAX OCTET STRING (SIZE (1..32)) MAX-ACCESS read-only STATUS current DESCRIPTION "Vector of supported BGP protocol version numbers. Each peer negotiates the version from this vector. Versions are identified via the string of bits contained within this object. The first octet contains bits 0 to 7, the second octet contains bits 8 to 15, and so on, with the most significant bit @@ -317,21 +315,21 @@ the BGP Start Event to be generated. A transition from 'start' to 'stop' will cause the BGP Stop Event to be generated. This parameter can be used to restart BGP peer connections. Care should be used in providing write access to this object without adequate authentication." ::= { bgpPeerEntry 3 } bgpPeerNegotiatedVersion OBJECT-TYPE - SYNTAX Integer[1..255] --- change to match draft + SYNTAX INTEGER (1..255) MAX-ACCESS read-only STATUS current DESCRIPTION "The negotiated version of BGP running between the two peers." ::= { bgpPeerEntry 4 } bgpPeerLocalAddr OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only @@ -631,21 +630,21 @@ bgpPathAttrDestNetwork OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS obsolete DESCRIPTION "The address of the destination network." ::= { bgpPathAttrEntry 2 } bgpPathAttrOrigin OBJECT-TYPE - SYNTAX INTEGER { + SYNTAX Integer32 { igp(1),-- networks are interior egp(2),-- networks learned via EGP incomplete(3) -- undetermined } MAX-ACCESS read-only STATUS obsolete DESCRIPTION "The ultimate origin of the path information." ::= { bgpPathAttrEntry 3 } @@ -706,43 +705,43 @@ "Information about a path to a network." INDEX { bgp4PathAttrIpAddrPrefix, bgp4PathAttrIpAddrPrefixLen, bgp4PathAttrPeer } ::= { bgp4PathAttrTable 1 } Bgp4PathAttrEntry ::= SEQUENCE { bgp4PathAttrPeer IpAddress, bgp4PathAttrIpAddrPrefixLen - INTEGER, + Integer32, bgp4PathAttrIpAddrPrefix IpAddress, bgp4PathAttrOrigin - INTEGER, + Integer32, bgp4PathAttrASPathSegment OCTET STRING, bgp4PathAttrNextHop IpAddress, bgp4PathAttrMultiExitDisc - INTEGER, + Integer32, bgp4PathAttrLocalPref - INTEGER, + Integer32, bgp4PathAttrAtomicAggregate - INTEGER, + Integer32, bgp4PathAttrAggregatorAS - INTEGER, + Integer32, bgp4PathAttrAggregatorAddr IpAddress, bgp4PathAttrCalcLocalPref - INTEGER, + Integer32, bgp4PathAttrBest - INTEGER, + Integer32, bgp4PathAttrUnknown OCTET STRING } bgp4PathAttrPeer OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The IP address of the peer where the path @@ -776,21 +776,21 @@ egp(2),-- networks learned via EGP incomplete(3) -- undetermined } MAX-ACCESS read-only STATUS current DESCRIPTION "The ultimate origin of the path information." ::= { bgp4PathAttrEntry 4 } 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 STATUS current DESCRIPTION "The sequence of AS path segments. Each AS path segment is represented by a triple . The type is a 1-octet field which has two possible values: 1 AS_SET: unordered set of ASs a @@ -817,43 +818,56 @@ MAX-ACCESS read-only STATUS current DESCRIPTION "The address of the border router that should be used for the destination network. This address is the nexthop address received in the UPDATE packet." ::= { bgp4PathAttrEntry 6 } bgp4PathAttrMultiExitDisc OBJECT-TYPE - SYNTAX INTEGER (0..4294967295) + SYNTAX Integer32 (0..4294967295) MAX-ACCESS read-only STATUS current DESCRIPTION "This metric is used to discriminate between multiple exit points to an adjacent autonomous - system. A value of -1 (4294967295) indicates the absence of - this attribute." + system. A value of -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 7 } bgp4PathAttrLocalPref OBJECT-TYPE - SYNTAX INTEGER (0..4294967295) + SYNTAX Integer32 (0..4294967295) MAX-ACCESS read-only STATUS current DESCRIPTION "The originating BGP4 speaker's degree 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 } bgp4PathAttrAtomicAggregate OBJECT-TYPE SYNTAX INTEGER { - lessSpecificRrouteNotSelected(1), + lessSpecificRouteNotSelected(1), lessSpecificRouteSelected(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "Whether or not a system has selected a less specific route without selecting a more specific route." ::= { bgp4PathAttrEntry 9 } @@ -861,67 +875,73 @@ SYNTAX INTEGER (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The AS number of the last BGP4 speaker that performed route aggregation. A value of zero (0) indicates the absence of this attribute." ::= { bgp4PathAttrEntry 10 } bgp4PathAttrAggregatorAddr OBJECT-TYPE - SYNTAX IpAddress propagation of AS path zero] + SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The IP address of the last BGP4 speaker that performed route aggregation. A value of 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 } bgp4PathAttrCalcLocalPref OBJECT-TYPE - SYNTAX INTEGER (0 ..4294967295) + SYNTAX Integer32 (0..4294967295) MAX-ACCESS read-only STATUS current DESCRIPTION "The degree of preference calculated by the receiving BGP4 speaker for an advertised route. 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 } bgp4PathAttrBest OBJECT-TYPE - SYNTAX INTEGER { + SYNTAX Integer32 { false(1),-- not chosen as best route true(2) -- chosen as best route } MAX-ACCESS read-only STATUS current DESCRIPTION "An indication of whether or not this route was chosen as the best BGP4 route." ::= { bgp4PathAttrEntry 13 } - bgp4PathAttrUnknown OBJECT-TYPE [format not specific enough - [switch to path format - type length value] - SYNTAX OCTET STRING (SIZE(0..255)) + bgp4PathAttrUnknown OBJECT-TYPE + SYNTAX OCTET STRING (SIZE(0..4096)) MAX-ACCESS read-only STATUS current DESCRIPTION "One or more path attributes not understood - by this BGP4 speaker. Path attributes are - recorded in the Update Path attribute format - of type, length, value. Size zero (0) indicates - the absence of such attribute(s). Octets - beyond the maximum size, if any, are not - recorded by this object. " + by the base BGP-4 document. + + Path attributes are recorded in the Update + Path attribute format of type, length, value. + Size zero (0) indicates the absence of such + attribute(s). Octets beyond the maximum size, + if any, are not recorded by this object. " ::= { bgp4PathAttrEntry 14 } -- Traps. -- 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.