idnits 2.17.1 draft-ietf-idr-bgp4-mib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** The document is more than 15 pages and seems to lack a Table of Contents. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 1141 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 82 instances of too long lines in the document, the longest one being 7 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (January 1996) is 10328 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 1771 (ref. '1') (Obsoleted by RFC 4271) Summary: 11 errors (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group S. Willis 2 INTERNET DRAFT BayNetworks 3 J. Burruss 4 BayNetworks 5 J. Chu 6 IBM Corporation 7 J. Johnson 8 cisco Systems 9 January 1996 11 Definitions of Managed Objects 12 for the Fourth Version of Border Gateway Protocol (BGP-4) 14 16 Status of this Memo 18 This document is an Internet Draft. Internet Drafts are working 19 documents of the Internet Engineering Task Force (IETF), its Areas, and 20 its Working Groups. Note that other groups may also distribute working 21 documents as Internet Drafts. 23 Internet Drafts are draft documents valid for a maximum of six months. 24 Internet Drafts may be updated, replaced, or obsoleted by other 25 documents at any time. It is not appropriate to use Internet Drafts as 26 reference material or to cite them other than as a "working draft" or 27 "work in progress." 29 Please check the I-D abstract listing contained in each Internet Draft 30 directory to learn the current status of this or any other Internet 31 Draft. 33 Abstract 35 This memo is an extension to the SNMP MIB. It specifies an IAB 36 standards track protocol for the Internet community, and requests 37 discussion and suggestions for improvements. The origin of this memo is 38 from RFC 1269 "Definitions of Managed Objects for the Board Gateway 39 Protocol (Version 3)" written by the first two authors of this memo, 40 which was updated to support BGP-4 in RFC 1657. This memo fixes errors 41 introduced when the MIB was converted to use the SNMPv2 SMI. 43 Distribution of this memo is unlimited. Please forward comments to 44 bgp@ans.net. 46 1. Introduction 48 This memo defines an experimental portion of the Management Information 49 Base (MIB) for use with network management protocols in the Internet 50 community. In particular, it describes managed objects used for 51 managing the Border Gateway Protocol Version 4 or lower [1, 2]. 53 2. The SNMPv2 Network Management Framework 55 The SNMPv2 Network Management Framework consists of four major 56 components. They are: 58 RFC 1442 which defines the SMI, the mechanisms used for describing 59 and naming objects for the purpose of management. 61 RFC 1213 defines MIB-II, the core set of managed objects for the 62 Internet suite of protocols. 64 RFC 1445 which defines the administrative and other architectural 65 aspects of the framework. 67 RFC 1448 which defines the protocol used for network access to 68 managed objects. 70 The Framework permits new objects to be defined for the purpose of 71 experimentation and evaluation. 73 3. Object Definitions 75 Managed objects are accessed via a virtual information store, termed the 76 Management Information Base or MIB. Objects in the MIB are defined 77 using the subset of Abstract Syntax Notation One (ASN.1) defined in the 78 SMI. In particular, each object type is named by an OBJECT IDENTIFIER, 79 an administratively assigned name. The object type together with an 80 object instance serves to uniquely identify a specific instantiation of 81 the object. For human convenience, we often use a textual string, 82 termed the descriptor, to refer to the object type. 84 4. Overview 86 These objects are used to control and manage a BGP-4 implementation. 88 Apart from a few system-wide scalar objects, this MIB is broken into 89 three tables: the BGP Peer Table, the BGP Received Path Attribute Table, 90 and the BGP-4 Received Path Attribute Table. The BGP Peer Table 91 contains information about state and current activity of connections 92 with the BGP peers. The Received Path Attribute Table contains path 93 attributes received from all peers running BGP version 3 or less. The 94 BGP-4 Received Path Attribute Table contains path attributes received 95 from all BGP-4 peers. The actual attributes used in determining a route 96 are a subset of the received attribute tables after local routing policy 97 has been applied. 99 5. Definitions 101 BGP4-MIB DEFINITIONS ::= BEGIN 103 IMPORTS 104 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 105 IpAddress, Integer32, Counter32, Gauge32 106 FROM SNMPv2-SMI 107 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 108 FROM SNMPv2-CONF 109 mib-2 110 FROM RFC1213-MIB; 112 bgp MODULE-IDENTITY 113 LAST-UPDATED "9512110000Z" 114 ORGANIZATION "IETF BGP Working Group" 115 CONTACT-INFO 116 " John Chu (Editor) 117 Postal: IBM Corp. 118 P.O.Box 704 119 Yorktown Heights, NY 10598 120 US 122 Tel: +1 914 784 7839 123 Fax: +1 914 784 6205 124 E-mail: jychu@watson.ibm.com 126 Jeff Johnson (Editor) 127 Postal: cisco Systems 128 170 W. Tasman Drive 129 San Jose, CA 95134 131 Tel: +1 408 526 7789 132 Fax: +1 408 526 4860 133 E-mail: jjohnson@cisco.com" 134 DESCRIPTION 135 "The MIB module for BGP-4." 136 REVISION "9601080000Z" 137 DESCRIPTION 138 "1) Fixed the definitions of the traps to 139 make them equivalent to their initial 140 definition in RFC 1269. 141 2) Added compliance and conformance info." 142 ::= { mib-2 15 } 144 bgpVersion OBJECT-TYPE 145 SYNTAX OCTET STRING (SIZE (1..255)) 146 MAX-ACCESS read-only 147 STATUS current 148 DESCRIPTION 149 "Vector of supported BGP protocol version 150 numbers. Each peer negotiates the version 151 from this vector. Versions are identified 152 via the string of bits contained within this 153 object. The first octet contains bits 0 to 154 7, the second octet contains bits 8 to 15, 155 and so on, with the most significant bit 156 referring to the lowest bit number in the 157 octet (e.g., the MSB of the first octet 158 refers to bit 0). If a bit, i, is present 159 and set, then the version (i+1) of the BGP 160 is supported." 161 ::= { bgp 1 } 163 bgpLocalAs OBJECT-TYPE 164 SYNTAX INTEGER (0..65535) 165 MAX-ACCESS read-only 166 STATUS current 167 DESCRIPTION 168 "The local autonomous system number." 169 ::= { bgp 2 } 171 -- BGP Peer table. This table contains, one entry per BGP 172 -- peer, information about the BGP peer. 174 bgpPeerTable OBJECT-TYPE 175 SYNTAX SEQUENCE OF BgpPeerEntry 176 MAX-ACCESS not-accessible 177 STATUS current 178 DESCRIPTION 179 "BGP peer table. This table contains, 180 one entry per BGP peer, information about the 181 connections with BGP peers." 182 ::= { bgp 3 } 184 bgpPeerEntry OBJECT-TYPE 185 SYNTAX BgpPeerEntry 186 MAX-ACCESS not-accessible 187 STATUS current 188 DESCRIPTION 189 "Entry containing information about the 190 connection with a BGP peer." 191 INDEX { bgpPeerRemoteAddr } 192 ::= { bgpPeerTable 1 } 194 BgpPeerEntry ::= SEQUENCE { 195 bgpPeerIdentifier 196 IpAddress, 197 bgpPeerState 198 INTEGER, 199 bgpPeerAdminStatus 200 INTEGER, 201 bgpPeerNegotiatedVersion 202 Integer32, 203 bgpPeerLocalAddr 204 IpAddress, 205 bgpPeerLocalPort 206 INTEGER, 207 bgpPeerRemoteAddr 208 IpAddress, 209 bgpPeerRemotePort 210 INTEGER, 211 bgpPeerRemoteAs 212 INTEGER, 213 bgpPeerInUpdates 214 Counter32, 215 bgpPeerOutUpdates 216 Counter32, 217 bgpPeerInTotalMessages 218 Counter32, 219 bgpPeerOutTotalMessages 220 Counter32, 221 bgpPeerLastError 222 OCTET STRING, 223 bgpPeerFsmEstablishedTransitions 224 Counter32, 225 bgpPeerFsmEstablishedTime 226 Gauge32, 227 bgpPeerConnectRetryInterval 228 INTEGER, 229 bgpPeerHoldTime 230 INTEGER, 231 bgpPeerKeepAlive 232 INTEGER, 233 bgpPeerHoldTimeConfigured 234 INTEGER, 235 bgpPeerKeepAliveConfigured 236 INTEGER, 237 bgpPeerMinASOriginationInterval 238 INTEGER, 239 bgpPeerMinRouteAdvertisementInterval 240 INTEGER, 241 bgpPeerInUpdateElapsedTime 242 Gauge32 243 } 245 bgpPeerIdentifier OBJECT-TYPE 246 SYNTAX IpAddress 247 MAX-ACCESS read-only 248 STATUS current 249 DESCRIPTION 250 "The BGP Identifier of this entry's BGP peer." 251 ::= { bgpPeerEntry 1 } 253 bgpPeerState OBJECT-TYPE 254 SYNTAX INTEGER { 255 idle(1), 256 connect(2), 257 active(3), 258 opensent(4), 259 openconfirm(5), 260 established(6) 261 } 262 MAX-ACCESS read-only 263 STATUS current 264 DESCRIPTION 265 "The BGP peer connection state." 266 ::= { bgpPeerEntry 2 } 268 bgpPeerAdminStatus OBJECT-TYPE 269 SYNTAX INTEGER { 270 stop(1), 271 start(2) 272 } 273 MAX-ACCESS read-write 274 STATUS current 275 DESCRIPTION 276 "The desired state of the BGP connection. A 277 transition from 'stop' to 'start' will cause 278 the BGP Start Event to be generated. A 279 transition from 'start' to 'stop' will cause 280 the BGP Stop Event to be generated. This 281 parameter can be used to restart BGP peer 282 connections. Care should be used in providing 283 write access to this object without adequate 284 authentication." 285 ::= { bgpPeerEntry 3 } 287 bgpPeerNegotiatedVersion OBJECT-TYPE 288 SYNTAX Integer32 289 MAX-ACCESS read-only 290 STATUS current 291 DESCRIPTION 292 "The negotiated version of BGP running between 293 the two peers." 294 ::= { bgpPeerEntry 4 } 296 bgpPeerLocalAddr OBJECT-TYPE 297 SYNTAX IpAddress 298 MAX-ACCESS read-only 299 STATUS current 300 DESCRIPTION 301 "The local IP address of this entry's BGP 302 connection." 303 ::= { bgpPeerEntry 5 } 305 bgpPeerLocalPort OBJECT-TYPE 306 SYNTAX INTEGER (0..65535) 307 MAX-ACCESS read-only 308 STATUS current 309 DESCRIPTION 310 "The local port for the TCP connection between 311 the BGP peers." 312 ::= { bgpPeerEntry 6 } 314 bgpPeerRemoteAddr OBJECT-TYPE 315 SYNTAX IpAddress 316 MAX-ACCESS read-only 317 STATUS current 318 DESCRIPTION 319 "The remote IP address of this entry's BGP 320 peer." 321 ::= { bgpPeerEntry 7 } 323 bgpPeerRemotePort OBJECT-TYPE 324 SYNTAX INTEGER (0..65535) 325 MAX-ACCESS read-only 326 STATUS current 327 DESCRIPTION 328 "The remote port for the TCP connection between 329 the BGP peers. Note that the objects 330 bgpPeerLocalAddr, bgpPeerLocalPort, 331 bgpPeerRemoteAddr and bgpPeerRemotePort 332 provide the appropriate reference to the 333 standard MIB TCP connection table." 334 ::= { bgpPeerEntry 8 } 336 bgpPeerRemoteAs OBJECT-TYPE 337 SYNTAX INTEGER (0..65535) 338 MAX-ACCESS read-only 339 STATUS current 340 DESCRIPTION 341 "The remote autonomous system number." 342 ::= { bgpPeerEntry 9 } 344 bgpPeerInUpdates OBJECT-TYPE 345 SYNTAX Counter32 346 MAX-ACCESS read-only 347 STATUS current 348 DESCRIPTION 349 "The number of BGP UPDATE messages received on 350 this connection. This object should be 351 initialized to zero (0) when the connection is 352 established." 353 ::= { bgpPeerEntry 10 } 355 bgpPeerOutUpdates OBJECT-TYPE 356 SYNTAX Counter32 357 MAX-ACCESS read-only 358 STATUS current 359 DESCRIPTION 360 "The number of BGP UPDATE messages transmitted 361 on this connection. This object should be 362 initialized to zero (0) when the connection is 363 established." 364 ::= { bgpPeerEntry 11 } 366 bgpPeerInTotalMessages OBJECT-TYPE 367 SYNTAX Counter32 368 MAX-ACCESS read-only 369 STATUS current 370 DESCRIPTION 371 "The total number of messages received from the 372 remote peer on this connection. This object 373 should be initialized to zero when the 374 connection is established." 375 ::= { bgpPeerEntry 12 } 377 bgpPeerOutTotalMessages OBJECT-TYPE 378 SYNTAX Counter32 379 MAX-ACCESS read-only 380 STATUS current 381 DESCRIPTION 382 "The total number of messages transmitted to 383 the remote peer on this connection. This object 384 should be initialized to zero when the 385 connection is established." 386 ::= { bgpPeerEntry 13 } 388 bgpPeerLastError OBJECT-TYPE 389 SYNTAX OCTET STRING (SIZE (2)) 390 MAX-ACCESS read-only 391 STATUS current 392 DESCRIPTION 393 "The last error code and subcode seen by this 394 peer on this connection. If no error has 395 occurred, this field is zero. Otherwise, the 396 first byte of this two byte OCTET STRING 397 contains the error code, and the second byte 398 contains the subcode." 399 ::= { bgpPeerEntry 14 } 401 bgpPeerFsmEstablishedTransitions OBJECT-TYPE 402 SYNTAX Counter32 403 MAX-ACCESS read-only 404 STATUS current 405 DESCRIPTION 406 "The total number of times the BGP FSM 407 transitioned into the established state." 408 ::= { bgpPeerEntry 15 } 410 bgpPeerFsmEstablishedTime OBJECT-TYPE 411 SYNTAX Gauge32 412 MAX-ACCESS read-only 413 STATUS current 414 DESCRIPTION 415 "This timer indicates how long (in seconds) this 416 peer has been in the Established state or how long 417 since this peer was last in the Established state. 418 It is set to zero when a new peer is configured or 419 the router is booted." 420 ::= { bgpPeerEntry 16 } 422 bgpPeerConnectRetryInterval OBJECT-TYPE 423 SYNTAX INTEGER (1..65535) 424 MAX-ACCESS read-write 425 STATUS current 426 DESCRIPTION 427 "Time interval in seconds for the ConnectRetry 428 timer. The suggested value for this timer is 429 120 seconds." 430 ::= { bgpPeerEntry 17 } 432 bgpPeerHoldTime OBJECT-TYPE 433 SYNTAX INTEGER ( 0 | 3..65535 ) 434 MAX-ACCESS read-only 435 STATUS current 436 DESCRIPTION 437 "Time interval in seconds for the Hold Timer 438 established with the peer. The value of this 439 object is calculated by this BGP speaker by 440 using the smaller of the value in 441 bgpPeerHoldTimeConfigured and the Hold Time 442 received in the OPEN message. This value 443 must be at lease three seconds if it is not 444 zero (0) in which case the Hold Timer has 445 not been established with the peer, or, the 446 value of bgpPeerHoldTimeConfigured is zero (0)." 447 ::= { bgpPeerEntry 18 } 449 bgpPeerKeepAlive OBJECT-TYPE 450 SYNTAX INTEGER ( 0 | 1..21845 ) 451 MAX-ACCESS read-only 452 STATUS current 453 DESCRIPTION 454 "Time interval in seconds for the KeepAlive 455 timer established with the peer. The value of 456 this object is calculated by this BGP speaker 457 such that, when compared with bgpPeerHoldTime, 458 it has the same proportion as what 459 bgpPeerKeepAliveConfigured has when compared 460 with bgpPeerHoldTimeConfigured. If the value 461 of this object is zero (0), it indicates that 462 the KeepAlive timer has not been established 463 with the peer, or, the value of 464 bgpPeerKeepAliveConfigured is zero (0)." 465 ::= { bgpPeerEntry 19 } 467 bgpPeerHoldTimeConfigured OBJECT-TYPE 468 SYNTAX INTEGER ( 0 | 3..65535 ) 469 MAX-ACCESS read-write 470 STATUS current 471 DESCRIPTION 472 "Time interval in seconds for the Hold Time 473 configured for this BGP speaker with this peer. 474 This value is placed in an OPEN message sent to 475 this peer by this BGP speaker, and is compared 476 with the Hold Time field in an OPEN message 477 received from the peer when determining the Hold 478 Time (bgpPeerHoldTime) with the peer. This value 479 must not be less than three seconds if it is not 480 zero (0) in which case the Hold Time is NOT to be 481 established with the peer. The suggested value for 482 this timer is 90 seconds." 483 ::= { bgpPeerEntry 20 } 485 bgpPeerKeepAliveConfigured OBJECT-TYPE 486 SYNTAX INTEGER ( 0 | 1..21845 ) 487 MAX-ACCESS read-write 488 STATUS current 489 DESCRIPTION 490 "Time interval in seconds for the KeepAlive timer 491 configured for this BGP speaker with this peer. 492 The value of this object will only determine the 493 KEEPALIVE messages' frequency relative to the value 494 specified in bgpPeerHoldTimeConfigured; the actual 495 time interval for the KEEPALIVE messages is 496 indicated by bgpPeerKeepAlive. A reasonable 497 maximum value for this timer would be configured to 498 be one third of that of bgpPeerHoldTimeConfigured. 499 If the value of this object is zero (0), no 500 periodical KEEPALIVE messages are sent to the peer 501 after the BGP connection has been established. The 502 suggested value for this timer is 30 seconds." 503 ::= { bgpPeerEntry 21 } 505 bgpPeerMinASOriginationInterval OBJECT-TYPE 506 SYNTAX INTEGER (1..65535) 507 MAX-ACCESS read-write 508 STATUS current 509 DESCRIPTION 510 "Time interval in seconds for the 511 MinASOriginationInterval timer. 512 The suggested value for this timer is 15 seconds." 513 ::= { bgpPeerEntry 22 } 515 bgpPeerMinRouteAdvertisementInterval OBJECT-TYPE 516 SYNTAX INTEGER (1..65535) 517 MAX-ACCESS read-write 518 STATUS current 519 DESCRIPTION 520 "Time interval in seconds for the 521 MinRouteAdvertisementInterval timer. 522 The suggested value for this timer is 30 seconds." 523 ::= { bgpPeerEntry 23 } 525 bgpPeerInUpdateElapsedTime OBJECT-TYPE 526 SYNTAX Gauge32 527 MAX-ACCESS read-only 528 STATUS current 529 DESCRIPTION 530 "Elapsed time in seconds since the last BGP 531 UPDATE message was received from the peer. 532 Each time bgpPeerInUpdates is incremented, 533 the value of this object is set to zero (0)." 534 ::= { bgpPeerEntry 24 } 536 bgpIdentifier OBJECT-TYPE 537 SYNTAX IpAddress 538 MAX-ACCESS read-only 539 STATUS current 540 DESCRIPTION 541 "The BGP Identifier of local system." 542 ::= { bgp 4 } 544 -- Received Path Attribute Table. This table contains, 545 -- one entry per path to a network, path attributes 546 -- received from all peers running BGP version 3 or less. 547 -- This table is obsolete, having been replaced in 548 -- functionality with the bgp4PathAttrTable. 550 bgpRcvdPathAttrTable OBJECT-TYPE 551 SYNTAX SEQUENCE OF BgpPathAttrEntry 552 MAX-ACCESS not-accessible 553 STATUS obsolete 554 DESCRIPTION 555 "The BGP Received Path Attribute Table contains 556 information about paths to destination networks 557 received from all peers running BGP version 3 or 558 less." 559 ::= { bgp 5 } 561 bgpPathAttrEntry OBJECT-TYPE 562 SYNTAX BgpPathAttrEntry 563 MAX-ACCESS not-accessible 564 STATUS obsolete 565 DESCRIPTION 566 "Information about a path to a network." 567 INDEX { bgpPathAttrDestNetwork, 568 bgpPathAttrPeer } 569 ::= { bgpRcvdPathAttrTable 1 } 571 BgpPathAttrEntry ::= SEQUENCE { 572 bgpPathAttrPeer 573 IpAddress, 574 bgpPathAttrDestNetwork 575 IpAddress, 576 bgpPathAttrOrigin 577 INTEGER, 578 bgpPathAttrASPath 579 OCTET STRING, 580 bgpPathAttrNextHop 581 IpAddress, 582 bgpPathAttrInterASMetric 583 Integer32 584 } 586 bgpPathAttrPeer OBJECT-TYPE 587 SYNTAX IpAddress 588 MAX-ACCESS read-only 589 STATUS obsolete 590 DESCRIPTION 591 "The IP address of the peer where the path 592 information was learned." 593 ::= { bgpPathAttrEntry 1 } 595 bgpPathAttrDestNetwork OBJECT-TYPE 596 SYNTAX IpAddress 597 MAX-ACCESS read-only 598 STATUS obsolete 599 DESCRIPTION 600 "The address of the destination network." 601 ::= { bgpPathAttrEntry 2 } 603 bgpPathAttrOrigin OBJECT-TYPE 604 SYNTAX INTEGER { 605 igp(1),-- networks are interior 606 egp(2),-- networks learned via EGP 607 incomplete(3) -- undetermined 608 } 609 MAX-ACCESS read-only 610 STATUS obsolete 611 DESCRIPTION 612 "The ultimate origin of the path information." 613 ::= { bgpPathAttrEntry 3 } 615 bgpPathAttrASPath OBJECT-TYPE 616 SYNTAX OCTET STRING (SIZE (2..255)) 617 MAX-ACCESS read-only 618 STATUS obsolete 619 DESCRIPTION 620 "The set of ASs that must be traversed to reach 621 the network. This object is probably best 622 represented as SEQUENCE OF INTEGER. For SMI 623 compatibility, though, it is represented as 624 OCTET STRING. Each AS is represented as a pair 625 of octets according to the following algorithm: 627 first-byte-of-pair = ASNumber / 256; 628 second-byte-of-pair = ASNumber & 255;" 629 ::= { bgpPathAttrEntry 4 } 631 bgpPathAttrNextHop OBJECT-TYPE 632 SYNTAX IpAddress 633 MAX-ACCESS read-only 634 STATUS obsolete 635 DESCRIPTION 636 "The address of the border router that should 637 be used for the destination network." 638 ::= { bgpPathAttrEntry 5 } 640 bgpPathAttrInterASMetric OBJECT-TYPE 641 SYNTAX Integer32 642 MAX-ACCESS read-only 643 STATUS obsolete 644 DESCRIPTION 645 "The optional inter-AS metric. If this 646 attribute has not been provided for this route, 647 the value for this object is 0." 648 ::= { bgpPathAttrEntry 6 } 650 -- BGP-4 Received Path Attribute Table. This table contains, 651 -- one entry per path to a network, path attributes 652 -- received from all peers running BGP-4. 654 bgp4PathAttrTable OBJECT-TYPE 655 SYNTAX SEQUENCE OF Bgp4PathAttrEntry 656 MAX-ACCESS not-accessible 657 STATUS current 658 DESCRIPTION 659 "The BGP-4 Received Path Attribute Table contains 660 information about paths to destination networks 661 received from all BGP4 peers." 662 ::= { bgp 6 } 664 bgp4PathAttrEntry OBJECT-TYPE 665 SYNTAX Bgp4PathAttrEntry 666 MAX-ACCESS not-accessible 667 STATUS current 668 DESCRIPTION 669 "Information about a path to a network." 670 INDEX { bgp4PathAttrIpAddrPrefix, 671 bgp4PathAttrIpAddrPrefixLen, 672 bgp4PathAttrPeer } 673 ::= { bgp4PathAttrTable 1 } 675 Bgp4PathAttrEntry ::= SEQUENCE { 676 bgp4PathAttrPeer 677 IpAddress, 678 bgp4PathAttrIpAddrPrefixLen 679 INTEGER, 680 bgp4PathAttrIpAddrPrefix 681 IpAddress, 682 bgp4PathAttrOrigin 683 INTEGER, 684 bgp4PathAttrASPathSegment 685 OCTET STRING, 686 bgp4PathAttrNextHop 687 IpAddress, 688 bgp4PathAttrMultiExitDisc 689 INTEGER, 690 bgp4PathAttrLocalPref 691 INTEGER, 692 bgp4PathAttrAtomicAggregate 693 INTEGER, 694 bgp4PathAttrAggregatorAS 695 INTEGER, 696 bgp4PathAttrAggregatorAddr 697 IpAddress, 698 bgp4PathAttrCalcLocalPref 699 INTEGER, 700 bgp4PathAttrBest 701 INTEGER, 702 bgp4PathAttrUnknown 703 OCTET STRING 704 } 706 bgp4PathAttrPeer OBJECT-TYPE 707 SYNTAX IpAddress 708 MAX-ACCESS read-only 709 STATUS current 710 DESCRIPTION 711 "The IP address of the peer where the path 712 information was learned." 713 ::= { bgp4PathAttrEntry 1 } 715 bgp4PathAttrIpAddrPrefixLen OBJECT-TYPE 716 SYNTAX INTEGER (0..32) 717 MAX-ACCESS read-only 718 STATUS current 719 DESCRIPTION 720 "Length in bits of the IP address prefix in the 721 Network Layer Reachability Information field." 722 ::= { bgp4PathAttrEntry 2 } 724 bgp4PathAttrIpAddrPrefix OBJECT-TYPE 725 SYNTAX IpAddress 726 MAX-ACCESS read-only 727 STATUS current 728 DESCRIPTION 729 "An IP address prefix in the Network Layer 730 Reachability Information field. This object 731 is an IP address containing the prefix with 732 length specified by bgp4PathAttrIpAddrPrefixLen. 733 Any bits beyond the length specified by 734 bgp4PathAttrIpAddrPrefixLen are zeroed." 735 ::= { bgp4PathAttrEntry 3 } 737 bgp4PathAttrOrigin OBJECT-TYPE 738 SYNTAX INTEGER { 739 igp(1),-- networks are interior 740 egp(2),-- networks learned via EGP 741 incomplete(3) -- undetermined 742 } 743 MAX-ACCESS read-only 744 STATUS current 745 DESCRIPTION 746 "The ultimate origin of the path information." 747 ::= { bgp4PathAttrEntry 4 } 749 bgp4PathAttrASPathSegment OBJECT-TYPE 750 SYNTAX OCTET STRING (SIZE (2..255)) 751 MAX-ACCESS read-only 752 STATUS current 753 DESCRIPTION 754 "The sequence of AS path segments. Each AS 755 path segment is represented by a triple 756 . 758 The type is a 1-octet field which has two 759 possible values: 760 1 AS_SET: unordered set of ASs a 761 route in the UPDATE message 762 has traversed 763 2 AS_SEQUENCE: ordered set of ASs 764 a route in the UPDATE message 765 has traversed. 767 The length is a 1-octet field containing the 768 number of ASs in the value field. 770 The value field contains one or more AS 771 numbers, each AS is represented in the octet 772 string as a pair of octets according to the 773 following algorithm: 775 first-byte-of-pair = ASNumber / 256; 776 second-byte-of-pair = ASNumber & 255;" 777 ::= { bgp4PathAttrEntry 5 } 779 bgp4PathAttrNextHop OBJECT-TYPE 780 SYNTAX IpAddress 781 MAX-ACCESS read-only 782 STATUS current 783 DESCRIPTION 784 "The address of the border router that should 785 be used for the destination network." 786 ::= { bgp4PathAttrEntry 6 } 788 bgp4PathAttrMultiExitDisc OBJECT-TYPE 789 SYNTAX INTEGER (-1..2147483647) 790 MAX-ACCESS read-only 791 STATUS current 792 DESCRIPTION 793 "This metric is used to discriminate between 794 multiple exit points to an adjacent autonomous 795 system. A value of -1 indicates the absence of 796 this attribute." 797 ::= { bgp4PathAttrEntry 7 } 799 bgp4PathAttrLocalPref OBJECT-TYPE 800 SYNTAX INTEGER (-1..2147483647) 801 MAX-ACCESS read-only 802 STATUS current 803 DESCRIPTION 804 "The originating BGP4 speaker's degree of 805 preference for an advertised route. A value of 806 -1 indicates the absence of this attribute." 807 ::= { bgp4PathAttrEntry 8 } 809 bgp4PathAttrAtomicAggregate OBJECT-TYPE 810 SYNTAX INTEGER { 811 lessSpecificRrouteNotSelected(1), 812 lessSpecificRouteSelected(2) 813 } 814 MAX-ACCESS read-only 815 STATUS current 816 DESCRIPTION 817 "Whether or not a system has selected 818 a less specific route without selecting a 819 more specific route." 820 ::= { bgp4PathAttrEntry 9 } 822 bgp4PathAttrAggregatorAS OBJECT-TYPE 823 SYNTAX INTEGER (0..65535) 824 MAX-ACCESS read-only 825 STATUS current 826 DESCRIPTION 827 "The AS number of the last BGP4 speaker that 828 performed route aggregation. A value of zero (0) 829 indicates the absence of this attribute." 830 ::= { bgp4PathAttrEntry 10 } 832 bgp4PathAttrAggregatorAddr OBJECT-TYPE 833 SYNTAX IpAddress 834 MAX-ACCESS read-only 835 STATUS current 836 DESCRIPTION 837 "The IP address of the last BGP4 speaker that 838 performed route aggregation. A value of 839 0.0.0.0 indicates the absence of this attribute." 840 ::= { bgp4PathAttrEntry 11 } 842 bgp4PathAttrCalcLocalPref OBJECT-TYPE 843 SYNTAX INTEGER (-1..2147483647) 844 MAX-ACCESS read-only 845 STATUS current 846 DESCRIPTION 847 "The degree of preference calculated by the 848 receiving BGP4 speaker for an advertised route. 849 A value of -1 indicates the absence of this 850 attribute." 851 ::= { bgp4PathAttrEntry 12 } 853 bgp4PathAttrBest OBJECT-TYPE 854 SYNTAX INTEGER { 855 false(1),-- not chosen as best route 856 true(2) -- chosen as best route 857 } 858 MAX-ACCESS read-only 859 STATUS current 860 DESCRIPTION 861 "An indication of whether or not this route 862 was chosen as the best BGP4 route." 863 ::= { bgp4PathAttrEntry 13 } 865 bgp4PathAttrUnknown OBJECT-TYPE 866 SYNTAX OCTET STRING (SIZE(0..255)) 867 MAX-ACCESS read-only 868 STATUS current 869 DESCRIPTION 870 "One or more path attributes not understood 871 by this BGP4 speaker. Size zero (0) indicates 872 the absence of such attribute(s). Octets 873 beyond the maximum size, if any, are not 874 recorded by this object." 875 ::= { bgp4PathAttrEntry 14 } 877 -- Traps. 879 -- note that in RFC 1657, bgpTraps was incorrectly 880 -- assigned a value of { bgp 7 }, and each of the 881 -- traps had the bgpPeerRemoteAddr object inappropriately 882 -- removed from their OBJECTS clause. The following 883 -- definitions restore the semantics of the traps as 884 -- they were initially defined in RFC 1269. 886 -- { bgp 7 } is unused 888 bgpTraps OBJECT IDENTIFIER ::= { bgp 0 } 890 bgpEstablished NOTIFICATION-TYPE 891 OBJECTS { bgpPeerRemoteAddr, 892 bgpPeerLastError, 893 bgpPeerState } 894 STATUS current 895 DESCRIPTION 896 "The BGP Established event is generated when 897 the BGP FSM enters the ESTABLISHED state." 898 ::= { bgpTraps 1 } 900 bgpBackwardTransition NOTIFICATION-TYPE 901 OBJECTS { bgpPeerRemoteAddr, 902 bgpPeerLastError, 903 bgpPeerState } 904 STATUS current 905 DESCRIPTION 906 "The BGPBackwardTransition Event is generated 907 when the BGP FSM moves from a higher numbered 908 state to a lower numbered state." 909 ::= { bgpTraps 2 } 911 -- conformance information 913 bgpMIBConformance OBJECT IDENTIFIER ::= { bgp 8 } 914 bgpMIBCompliances OBJECT IDENTIFIER ::= { bgpMIBConformance 1 } 915 bgpMIBGroups OBJECT IDENTIFIER ::= { bgpMIBConformance 2 } 917 -- compliance statements 919 bgpMIBCompliance MODULE-COMPLIANCE 920 STATUS current 921 DESCRIPTION 922 "The compliance statement for entities which 923 implement the BGP4 mib." 924 MODULE -- this module 925 MANDATORY-GROUPS { bgp4MIBGlobalsGroup, 926 bgp4MIBPeerGroup, 927 bgp4MIBPathAttrGroup, 928 bgp4MIBNotificationGroup } 929 ::= { bgpMIBCompliances 1 } 931 -- units of conformance 933 bgp4MIBGlobalsGroup OBJECT-GROUP 934 OBJECTS { bgpVersion, 935 bgpLocalAs, 936 bgpIdentifier } 937 STATUS current 938 DESCRIPTION 939 "A collection of objects providing information 940 on global BGP state." 941 ::= { bgpMIBGroups 1 } 943 bgp4MIBPeerGroup OBJECT-GROUP 944 OBJECTS { bgpPeerIdentifier, 945 bgpPeerState, 946 bgpPeerAdminStatus, 947 bgpPeerNegotiatedVersion, 948 bgpPeerLocalAddr, 949 bgpPeerLocalPort, 950 bgpPeerRemoteAddr, 951 bgpPeerRemotePort, 952 bgpPeerRemoteAs, 953 bgpPeerInUpdates, 954 bgpPeerOutUpdates, 955 bgpPeerInTotalMessages, 956 bgpPeerOutTotalMessages, 957 bgpPeerLastError, 958 bgpPeerFsmEstablishedTransitions, 959 bgpPeerFsmEstablishedTime, 960 bgpPeerConnectRetryInterval, 961 bgpPeerHoldTime, 962 bgpPeerKeepAlive, 963 bgpPeerHoldTimeConfigured, 964 bgpPeerKeepAliveConfigured, 965 bgpPeerMinASOriginationInterval, 966 bgpPeerMinRouteAdvertisementInterval, 967 bgpPeerInUpdateElapsedTime } 968 STATUS current 969 DESCRIPTION 970 "A collection of objects for managing 971 BGP peers." 972 ::= { bgpMIBGroups 2 } 974 bgp4MIBRcvdPathAttrGroup OBJECT-GROUP 975 OBJECTS { bgpPathAttrPeer, 976 bgpPathAttrDestNetwork, 977 bgpPathAttrOrigin, 978 bgpPathAttrASPath, 979 bgpPathAttrNextHop, 980 bgpPathAttrInterASMetric } 981 STATUS obsolete 982 DESCRIPTION 983 "A collection of objects for managing BGP 984 path entries. 986 This conformance group is obsolete, 987 replaced by bgp4MIBPathAttrGroup." 988 ::= { bgpMIBGroups 3 } 990 bgp4MIBPathAttrGroup OBJECT-GROUP 991 OBJECTS { bgp4PathAttrPeer, 992 bgp4PathAttrIpAddrPrefixLen, 993 bgp4PathAttrIpAddrPrefix, 994 bgp4PathAttrOrigin, 995 bgp4PathAttrASPathSegment, 996 bgp4PathAttrNextHop, 997 bgp4PathAttrMultiExitDisc, 998 bgp4PathAttrLocalPref, 999 bgp4PathAttrAtomicAggregate, 1000 bgp4PathAttrAggregatorAS, 1001 bgp4PathAttrAggregatorAddr, 1002 bgp4PathAttrCalcLocalPref, 1003 bgp4PathAttrBest, 1004 bgp4PathAttrUnknown } 1005 STATUS current 1006 DESCRIPTION 1007 "A collection of objects for managing 1008 BGP path entries." 1009 ::= { bgpMIBGroups 4 } 1011 bgp4MIBNotiicationGroup NOTIFICATION-GROUP 1012 NOTIFICATIONS { bgpEstablished, 1013 bgpBackwardTransition } 1014 STATUS current 1015 DESCRIPTION 1016 "A collection of notifications for signaling 1017 changes in BGP peer relationships." 1018 ::= { bgpMIBGroups 4 } 1020 END 1022 6. Acknowledgements 1024 We would like to acknowledge the assistance of all the members of the 1025 Interconnectivity Working Group, and particularly the following 1026 individuals: 1028 Yakov Rekhter, cisco Systems 1029 Rob Coltun, Fore 1030 Guy Almes, ANS 1031 Jeff Honig, Cornell Theory Center 1032 Marshall T. Rose, Dover Beach Consulting, Inc. 1033 Dennis Ferguson, Ipsilon 1034 Mike Mathis, PSC 1035 John Krawczyk, BayNetworks 1036 Curtis Villamizar, ANS 1037 Dave LeRoy, Pencom Systems 1038 Paul Traina, cisco Systems 1039 Andrew Partan, UUNET 1040 Robert Snyder, cisco Systems 1041 Dimitry Haskin, BayNetworks 1042 Peder Chr Norgaard, Telebit Communications A/S 1043 Joel Halpern, NewBridge 1044 Nick Thille, cisco Systems 1046 7. References 1048 [1] Rekhter, Y., Li, T., "A Border Gateway Protocol 4 (BGP-4)", 1049 RFC1771, March 1995 1051 [2] Rekhter, Y., Gross, P., "Application of the Border 1052 Gateway Protocol in the Internet", RFC1772, March 1995 1054 8. Security Considerations 1056 Security issues are not discussed in this memo. 1058 Authors' Address 1060 Steven Willis 1061 BayNetworks 1062 15 Crosby Drive 1063 Bedford, MA 01730 1065 Phone: +1 617 275 2400 1066 Email: swillis@baynetworks.com 1068 John Burruss 1069 BayNetworks 1070 15 Crosby Drive 1071 Bedford, MA 01730 1073 Phone: +1 617 275 2400 1074 Email: jburruss@baynetworks.com 1076 John Chu 1077 IBM Corporation 1078 P.O.Box 704 1079 Yorktown Heights, NY 10598 1081 Phone: +1 914 784 7839 1082 Email: jychu@watson.ibm.com 1084 Jeff Johnson 1085 cisco Systems 1086 170 W. Tasman Drive 1087 San Jose, CA 95134 1089 Phone: +1 408 526 7789 1090 Email: jjohnson@cisco.com