draft-ietf-idr-bgp4-mib-04.txt   draft-ietf-idr-bgp4-mib-05.txt 
Network Working Group S. Hares Network Working Group S. Hares
INTERNET DRAFT Merit INTERNET DRAFT NextHop
J. Johnson J. Haas
RedBack Networks NextHop
S. Willis S. Willis
Argon Networks Argon Networks
J. Burruss J. Burruss
WinData WinData
J. Chu J. Chu
IBM Corporation Cosine
February 1999 December 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-04.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.
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.txt 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 Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
Abstract Abstract
skipping to change at page 2, line 33 skipping to change at page 2, line 33
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 Mechanisms for describing and naming objects and events for o bgp Mechanisms for describing and naming objects and events for
the purpose of management. The first version of this the purpose of management. The first version of this
Structure of Management Information (SMI) is called SMIv1 and Structure of Management Information (SMI) is called SMIv1 and
described in RFC 1155 [4], RFC 1212 [5] and RFC 1215 [6]. The described in RFC 1155 [4], RFC 1212 [5] and RFC 1215 [6]. The
second version, called SMIv2, is described in RFC 1902 [7], second version, called SMIv2, is described in RFC 1902 [7],
RFC 1903 [8] and RFC 1904 [9]. RFC 1903 [8] and RFC 1904 [9].
o Message protocols for transferring management information. o Message protocols for transferring management information.
The first version of the SNMP message protocol is called The first version of the SNMP message protocol is called
SNMPv1 and described in RFC 1157 [10]. A second version of SNMPv1 and described in RFC 1157 [10]. A second version of
the SNMP message protocol, which is not an Internet standards the SNMP message protocol, which is not an Internet standards
skipping to change at page 5, line 17 skipping to change at page 5, line 17
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 "9902100000Z" 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)
Merit Network 517 W. William Street
4251 Plymouth Road Ann Arbor, MI 48103-4943
Suite C
Ann Arbor, MI 48105-2785
Tel: +1 734 936 2095 Tel: +1 734 936 2095
Fax: +1 734 647 3185 Fax: +1 734 615-3241
E-mail: skh@merit.edu E-mail: skh@nexthop.com"
Jeff Johnson (Editor)
RedBack Networks, Inc.
1389 Moffett Park Drive
Sunnyvale, CA 94089-1134
Tel: +1 408 548 3516
Fax: +1 408 548 3599
E-mail: jeff@redback.com"
DESCRIPTION DESCRIPTION
"The MIB module for BGP-4." "The MIB module for BGP-4."
REVISION "9902100000Z" 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
draft-ietf-idr-bgp4-10.txt for value of
bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref,
bgp4PathAttrCalcLocalPref,bgp4PathAttrMultiExitDisc,
bgp4PathAttrASPathSegement."
::= { mib-2 15 } ::= { mib-2 15 }
bgpVersion OBJECT-TYPE bgpVersion OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (1..255)) SYNTAX OCTET STRING (SIZE (1..32)) --- change to match draft
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 9, line 4
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 Integer32 SYNTAX Integer[1..255] --- change to match draft
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 18, line 39 skipping to change at page 18, line 39
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..255)) SYNTAX OCTET STRING (SIZE (2..500)) --- [change 3 possible to have 500*4 bytes of aSpath]
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 26 skipping to change at page 19, line 26
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
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." be used for the destination network. This
address is the nexthop address received in
the UPDATE packet."
::= { bgp4PathAttrEntry 6 } ::= { bgp4PathAttrEntry 6 }
bgp4PathAttrMultiExitDisc OBJECT-TYPE bgp4PathAttrMultiExitDisc OBJECT-TYPE
SYNTAX INTEGER (-1..2147483647) SYNTAX INTEGER (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 indicates the absence of system. A value of -1 (4294967295) indicates the absence of
this attribute." this attribute."
::= { bgp4PathAttrEntry 7 } ::= { bgp4PathAttrEntry 7 }
bgp4PathAttrLocalPref OBJECT-TYPE bgp4PathAttrLocalPref OBJECT-TYPE
SYNTAX INTEGER (-1..2147483647) SYNTAX INTEGER (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 indicates the absence of this attribute." -1 (4294967295) indicates the absence of this attribute."
::= { bgp4PathAttrEntry 8 } ::= { bgp4PathAttrEntry 8 }
bgp4PathAttrAtomicAggregate OBJECT-TYPE bgp4PathAttrAtomicAggregate OBJECT-TYPE
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
skipping to change at page 20, line 26 skipping to change at page 20, line 26
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 SYNTAX IpAddress propagation of AS path zero]
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."
::= { bgp4PathAttrEntry 11 } ::= { bgp4PathAttrEntry 11 }
bgp4PathAttrCalcLocalPref OBJECT-TYPE bgp4PathAttrCalcLocalPref OBJECT-TYPE
SYNTAX INTEGER (-1..2147483647) SYNTAX INTEGER (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 indicates the absence of this A value of -1 (4294967295) indicates the absence of this
attribute." attribute."
::= { bgp4PathAttrEntry 12 } ::= { bgp4PathAttrEntry 12 }
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."
::= { bgp4PathAttrEntry 13 } ::= { bgp4PathAttrEntry 13 }
bgp4PathAttrUnknown OBJECT-TYPE bgp4PathAttrUnknown OBJECT-TYPE [format not specific enough
[switch to path format
type length value]
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 this BGP4 speaker. Size zero (0) indicates 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 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.
-- 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
skipping to change at page 25, line 28 skipping to change at page 25, line 28
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.
7. Acknowledgements 7. 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, cisco Systems Yakov Rekhter, cisco Systems
Rob Coltun, Fore Rob Coltun, Redback
Guy Almes, ANS Guy Almes, Internet2
Jeff Honig, Cornell Theory Center Jeff Honig, Cornell Theory Center
Marshall T. Rose, Dover Beach Consulting, Inc. Marshall T. Rose, Dover Beach Consulting, Inc.
Dennis Ferguson, Juniper Networks Dennis Ferguson, Juniper Networks
Mike Mathis, PSC Mike Mathis, PSC
John Krawczyk, Bay Networks John Krawczyk, Bay Networks
Curtis Villamizar, ANS Curtis Villamizar, Avici
Dave LeRoy, Pencom Systems Dave LeRoy, Pencom Systems
Paul Traina, Juniper Networks Paul Traina, Juniper Networks
Andrew Partan, UUNET Andrew Partan, MFS
Robert Snyder, cisco Systems Robert Snyder, cisco Systems
Dimitry Haskin, Bay Networks Dimitry Haskin, Nortel
Peder Chr Norgaard, Telebit Communications A/S Peder Chr Norgaard, Telebit Communications A/S
Joel Halpern, NewBridge Joel Halpern, CTO Longitude Systems, Inc.
Nick Thille, RedBack Networks Nick Thille, RedBack Networks
Bert Wijnen, IBM Bert Wijnen, IBM
Shane Wright, NextHop
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 wishes to acknowledge the fine work BGP-4 in RFC 1657. The editors wishes to acknowledge the fine work
of these original authors. of these original authors.
8. References 8. References
[1] Rekhter, Y., Li, T., "A Border Gateway Protocol 4 (BGP-4)", RFC [1] Rekhter, Y., Li, T., "A Border Gateway Protocol 4 (BGP-4)", RFC
skipping to change at page 28, line 41 skipping to change at page 28, line 41
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.
10. Authors' Address 10. Authors' Address
Susan Hares Susan Hares
Merit Network, Inc. NextHop Technologies
4251 Plymouth Road 517 Williams
Suite C Ann Arbor, MI 48103-4943
Ann Arbor, MI 48105-2785
Phone: +1 734 936 2095 Phone: +1 734 936 2095
Fax: +1 734 647 3185 Fax: +1 734 615-3241
Email: skh@merit.edu Email: skh@nexthop.com
Jeff Johnson Jeff Johnson
RedBack Networks, Inc. RedBack Networks, Inc.
1389 Moffett Park Drive 1389 Moffett Park Drive
Sunnyvale, CA 94089 Sunnyvale, CA 94089
Phone: +1 408 548 3516 Phone: +1 408 548 3516
Email: jeff@redback.com Email: jeff@redback.com
Steve Willis Steve Willis
Argon Networks Argon Networks
skipping to change at page 29, line 26 skipping to change at page 29, line 26
Email: swills@argon.com Email: swills@argon.com
John Burruss John Burruss
Windata Inc. Windata Inc.
543 Great Road 543 Great Road
Littleton MA 01460 Littleton MA 01460
Phone: +1 508 952 0170 Phone: +1 508 952 0170
Email: jburruss@windata.com Email: jburruss@windata.com
John Chu John Chu
IBM Corporation Cosine Communications
P.O.Box 704 1200 Bridge Parkway
Yorktown Heights, NY 10598 Redwood City, CA 94065
Phone: +1 914 784 7839 Phone: 650-637-4780
Email: jychu@watson.ibm.com Email: jchu@cosinecom.com
11. Full Copyright Statement 11. 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
 End of changes. 

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