idnits 2.17.1 draft-ietf-idr-bgp4-mib-15.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 33 instances of too long lines in the document, the longest one being 5 characters in excess of 72. ** There are 1134 instances of lines with control characters in the document. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 308: '... This entry MUST be 0.0.0.0 unles...' RFC 2119 keyword, line 366: '... This entry MUST be zero (0) unle...' RFC 2119 keyword, line 557: '...the peer this object MUST have a value...' RFC 2119 keyword, line 561: '...e of (0), then this object MUST have a...' RFC 2119 keyword, line 583: '...the peer this object MUST have a value...' (3 more instances...) -- The abstract seems to indicate that this document obsoletes RFC1657, but the header doesn't have an 'Obsoletes:' line to match this. -- The abstract seems to indicate that this document obsoletes RFC1269, but the header doesn't have an 'Obsoletes:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 1437 has weird spacing: '... There are ...' == Line 1440 has weird spacing: '...terface addre...' -- 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 (August 2004) is 7156 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) == Missing Reference: 'BGP' is mentioned on line 83, but not defined == Missing Reference: 'RFC3410' is mentioned on line 91, but not defined == Missing Reference: 'REF' is mentioned on line 1456, but not defined == Unused Reference: 'BGP4' is defined on line 1509, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'BGP4' Summary: 6 errors (**), 0 flaws (~~), 8 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET DRAFT BGP4-MIB August 2004 3 Network Working Group Editors of this version: 4 INTERNET DRAFT J. Haas 5 S. Hares 6 NextHop Technologies 7 August 2004 9 Definitions of Managed Objects 10 for the Fourth Version of Border Gateway Protocol (BGP-4) 11 13 Status of this Memo 15 This document is an Internet-Draft and is in full conformance with 16 all provisions of Section 10 of RFC 2026. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet- Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 Copyright Notice 36 Copyright (C) The Internet Society (2004). All Rights Reserved. 38 Abstract 40 This memo defines a portion of the Management Information Base (MIB) 41 for use with network management protocols in the Internet community 42 In particular, it describes managed objects used for managing the 43 Border Gateway Protocol Version 4 or lower. 45 The origin of this memo is from RFC 1269 "Definitions of Managed 46 Objects for the Border Gateway Protocol (Version 3)", which was 47 updated to support BGP-4 in RFC 1657. This memo fixes errors 48 introduced when the MIB module was converted to use the SMIv2 49 language. This memo also updates references to the current SNMP 50 framework documents. 52 This memo is intended to document deployed implementations of this 53 MIB module in a historical context, provide clarifications of some 54 items and also note errors where the MIB module fails to fully 55 represent the BGP protocol. Work is currently in progress to replace 56 this MIB module with a new one representing the current state of the 57 BGP protocol and its extensions. 59 This document obsoletes RFC 1269 and RFC 1657. 61 Distribution of this memo is unlimited. Please forward comments to 62 idr@ietf.org. 64 Table of Contents 66 1. Introduction ................................................. 3 67 2. The Internet-Standard Management Framework ................... 3 68 3. Overview ..................................................... 3 69 4. Definitions .................................................. 4 70 5. Intellectual Property ....................................... 32 71 6. Security Considerations ..................................... 33 72 7. Acknowledgements ............................................ 35 73 8. IANA Considerations ......................................... 36 74 9. Normative References ........................................ 36 75 10. Editors' Address ............................................ 36 76 11. Full Copyright Statement .................................... 37 78 1. Introduction 80 This memo defines a portion of the Management Information Base (MIB) 81 for use with network management protocols in the Internet community. 82 In particular, it describes managed objects used for managing the 83 Border Gateway Protocol Version 4 or lower [BGP, BGP4APP]. 85 This memo obsoletes RFC 1657 and RFC 1269. 87 2. The Internet-Standard Management Framework 89 For a detailed overview of the documents that describe the current 90 Internet-Standard Management Framework, please refer to section 7 of 91 RFC 3410 [RFC3410]. 93 Managed objects are accessed via a virtual information store, termed 94 the Management Information Base or MIB. MIB objects are generally 95 accessed through the Simple Network Management Protocol (SNMP). 96 Objects in the MIB are defined using the mechanisms defined in the 97 Structure of Management Information (SMI). This memo specifies a MIB 98 module that is compliant to the SMIv2, which is described in STD 58, 99 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 100 [RFC2580]. 102 3. Overview 104 These objects are used to control and manage a BGP-4 implementation. 106 Apart from a few system-wide scalar objects, this MIB is broken into 107 three tables: the BGP Peer Table, the BGP Received Path Attribute 108 Table, and the BGP-4 Received Path Attribute Table. The BGP Peer 109 Table contains information about state and current activity of 110 connections with the BGP peers. The BGP Received Path Attribute 111 Table contains path attributes received from all peers running BGP 112 version 3 or less. The BGP-4 Received Path Attribute Table contains 113 path attributes received from all BGP-4 peers. The actual attributes 114 used in determining a route are a subset of the received attribute 115 tables after local routing policy has been applied. 117 4. Definitions 119 BGP4-MIB DEFINITIONS ::= BEGIN 121 IMPORTS 122 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 123 IpAddress, Integer32, Counter32, Gauge32, mib-2 124 FROM SNMPv2-SMI 125 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 126 FROM SNMPv2-CONF; 128 bgp MODULE-IDENTITY 129 LAST-UPDATED "200408310000Z" 130 ORGANIZATION "IETF IDR Working Group" 131 CONTACT-INFO "E-mail: idr@ietf.org 133 Jeffrey Haas, Susan Hares (Editors) 134 NextHop Technologies 135 825 Victors Way 136 Suite 100 137 Ann Arbor, MI 48108-2738 138 Tel: +1 734 222-1600 139 Fax: +1 734 222-1602 140 E-mail: jhaas@nexthop.com 141 skh@nexthop.com" 143 DESCRIPTION 144 "The MIB module for the BGP-4 protocol. 146 Copyright (C) The Internet Society (2004). This version 147 of this MIB module is part of RFC yyyy; see the RFC 148 itself for full legal notices." 150 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 152 REVISION "200408310000Z" 153 DESCRIPTION 154 "Changes from RFC 1657: 156 1) Fixed the definitions of the notifications 157 to make them equivalent to their initial 158 definition in RFC 1269. 159 2) Added compliance and conformance info. 160 3) Updated information for the values of 161 bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref, 162 bgp4PathAttrCalcLocalPref, bgp4PathAttrMultiExitDisc, 163 bgp4PathAttrASPathSegement. 164 4) Added additional clarification comments where 165 needed. 166 5) Noted where objects do not fully reflect 167 the protocol as Known Issues. 168 6) Updated the DESCRIPTION for the 169 bgp4PathAttrAtomicAggregate object. 170 7) The following objects have had their DESCRIPTION 171 clause modified to remove the text that suggested 172 (using 'should' verb) to initialize the counter 173 to zero on a transition to the established state: 174 bgpPeerInUpdates, bgpPeerOutUpdates, 175 bgpPeerInTotalMessages, bgpPeerOutTotalMessages 176 Those implementations that still do this are 177 still compliant with this new wording. 178 Appliciations should not assume counters to have 179 started at zero. 181 Published as RFC yyyy." 182 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 184 REVISION "199405050000Z" 185 DESCRIPTION 186 "Translated to SMIv2 and published as RFC 1657." 188 REVISION "199110261839Z" 189 DESCRIPTION 190 "Initial version, published as RFC 1269." 192 ::= { mib-2 15 } 194 bgpVersion OBJECT-TYPE 195 SYNTAX OCTET STRING (SIZE (1..255)) 196 MAX-ACCESS read-only 197 STATUS current 198 DESCRIPTION 199 "Vector of supported BGP protocol version 200 numbers. Each peer negotiates the version 201 from this vector. Versions are identified 202 via the string of bits contained within this 203 object. The first octet contains bits 0 to 204 7, the second octet contains bits 8 to 15, 205 and so on, with the most significant bit 206 referring to the lowest bit number in the 207 octet (e.g., the MSB of the first octet 208 refers to bit 0). If a bit, i, is present 209 and set, then the version (i+1) of the BGP 210 is supported." 211 REFERENCE 212 "RFC yyyy, Section 4.2." 213 ::= { bgp 1 } 215 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 217 bgpLocalAs OBJECT-TYPE 218 SYNTAX Integer32 (0..65535) 219 MAX-ACCESS read-only 220 STATUS current 221 DESCRIPTION 222 "The local autonomous system number." 223 REFERENCE 224 "RFC yyyy, Section 4.2, 'My Autonomous System'." 225 ::= { bgp 2 } 226 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 228 -- BGP Peer table. This table contains, one entry per 229 -- BGP peer, information about the BGP peer. 231 bgpPeerTable OBJECT-TYPE 232 SYNTAX SEQUENCE OF BgpPeerEntry 233 MAX-ACCESS not-accessible 234 STATUS current 235 DESCRIPTION 236 "BGP peer table. This table contains, 237 one entry per BGP peer, information about the 238 connections with BGP peers." 239 ::= { bgp 3 } 241 bgpPeerEntry OBJECT-TYPE 242 SYNTAX BgpPeerEntry 243 MAX-ACCESS not-accessible 244 STATUS current 245 DESCRIPTION 246 "Entry containing information about the 247 connection with a BGP peer." 248 INDEX { bgpPeerRemoteAddr } 249 ::= { bgpPeerTable 1 } 251 BgpPeerEntry ::= SEQUENCE { 252 bgpPeerIdentifier 253 IpAddress, 254 bgpPeerState 255 INTEGER, 256 bgpPeerAdminStatus 257 INTEGER, 258 bgpPeerNegotiatedVersion 259 Integer32, 260 bgpPeerLocalAddr 261 IpAddress, 262 bgpPeerLocalPort 263 Integer32, 264 bgpPeerRemoteAddr 265 IpAddress, 266 bgpPeerRemotePort 267 Integer32, 268 bgpPeerRemoteAs 269 Integer32, 270 bgpPeerInUpdates 271 Counter32, 272 bgpPeerOutUpdates 273 Counter32, 274 bgpPeerInTotalMessages 275 Counter32, 276 bgpPeerOutTotalMessages 277 Counter32, 278 bgpPeerLastError 279 OCTET STRING, 280 bgpPeerFsmEstablishedTransitions 281 Counter32, 282 bgpPeerFsmEstablishedTime 283 Gauge32, 284 bgpPeerConnectRetryInterval 285 Integer32, 286 bgpPeerHoldTime 287 Integer32, 288 bgpPeerKeepAlive 289 Integer32, 290 bgpPeerHoldTimeConfigured 291 Integer32, 292 bgpPeerKeepAliveConfigured 293 Integer32, 294 bgpPeerMinASOriginationInterval 295 Integer32, 296 bgpPeerMinRouteAdvertisementInterval 297 Integer32, 298 bgpPeerInUpdateElapsedTime 299 Gauge32 300 } 302 bgpPeerIdentifier OBJECT-TYPE 303 SYNTAX IpAddress 304 MAX-ACCESS read-only 305 STATUS current 306 DESCRIPTION 307 "The BGP Identifier of this entry's BGP peer. 308 This entry MUST be 0.0.0.0 unless the 309 bgpPeerState is in the openconfirm or the 310 established state." 311 REFERENCE 312 "RFC yyyy, Section 4.2, 'BGP Identifier'." 313 ::= { bgpPeerEntry 1 } 314 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 316 bgpPeerState OBJECT-TYPE 317 SYNTAX INTEGER { 318 idle(1), 319 connect(2), 320 active(3), 321 opensent(4), 322 openconfirm(5), 323 established(6) 324 } 325 MAX-ACCESS read-only 326 STATUS current 327 DESCRIPTION 328 "The BGP peer connection state." 329 REFERENCE 330 "RFC yyyy, Section 8.2.2." 331 ::= { bgpPeerEntry 2 } 333 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 335 bgpPeerAdminStatus OBJECT-TYPE 336 SYNTAX INTEGER { 337 stop(1), 338 start(2) 339 } 340 MAX-ACCESS read-write 341 STATUS current 342 DESCRIPTION 343 "The desired state of the BGP connection. 344 A transition from 'stop' to 'start' will cause 345 the BGP Manual Start Event to be generated. 347 A transition from 'start' to 'stop' will cause 348 the BGP Manual Stop Event to be generated. 349 This parameter can be used to restart BGP peer 350 connections. Care should be used in providing 351 write access to this object without adequate 352 authentication." 353 REFERENCE 354 "RFC yyyy, Section 8.1.2." 355 ::= { bgpPeerEntry 3 } 356 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 358 bgpPeerNegotiatedVersion OBJECT-TYPE 359 SYNTAX Integer32 360 MAX-ACCESS read-only 361 STATUS current 362 DESCRIPTION 363 "The negotiated version of BGP running between 364 the two peers. 366 This entry MUST be zero (0) unless the 367 bgpPeerState is in the openconfirm or the 368 established state. 370 Note that legal values for this object are 371 between 0 and 255." 372 REFERENCE 373 "RFC yyyy, Section 4.2. 374 RFC yyyy, Section 7." 375 ::= { bgpPeerEntry 4 } 377 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 379 bgpPeerLocalAddr OBJECT-TYPE 380 SYNTAX IpAddress 381 MAX-ACCESS read-only 382 STATUS current 383 DESCRIPTION 384 "The local IP address of this entry's BGP 385 connection." 386 ::= { bgpPeerEntry 5 } 388 bgpPeerLocalPort OBJECT-TYPE 389 SYNTAX Integer32 (0..65535) 390 MAX-ACCESS read-only 391 STATUS current 392 DESCRIPTION 393 "The local port for the TCP connection between 394 the BGP peers." 395 ::= { bgpPeerEntry 6 } 397 bgpPeerRemoteAddr OBJECT-TYPE 398 SYNTAX IpAddress 399 MAX-ACCESS read-only 400 STATUS current 401 DESCRIPTION 402 "The remote IP address of this entry's BGP 403 peer." 404 ::= { bgpPeerEntry 7 } 406 bgpPeerRemotePort OBJECT-TYPE 407 SYNTAX Integer32 (0..65535) 408 MAX-ACCESS read-only 409 STATUS current 410 DESCRIPTION 411 "The remote port for the TCP connection 412 between the BGP peers. Note that the 413 objects bgpPeerLocalAddr, 414 bgpPeerLocalPort, bgpPeerRemoteAddr and 415 bgpPeerRemotePort provide the appropriate 416 reference to the standard MIB TCP 417 connection table." 418 ::= { bgpPeerEntry 8 } 420 bgpPeerRemoteAs OBJECT-TYPE 421 SYNTAX Integer32 (0..65535) 422 MAX-ACCESS read-only 423 STATUS current 424 DESCRIPTION 425 "The remote autonomous system number." 426 REFERENCE 427 "RFC yyyy, Section 4.2." 428 ::= { bgpPeerEntry 9 } 429 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 431 bgpPeerInUpdates OBJECT-TYPE 432 SYNTAX Counter32 433 MAX-ACCESS read-only 434 STATUS current 435 DESCRIPTION 436 "The number of BGP UPDATE messages 437 received on this connection." 438 REFERENCE 439 "RFC yyyy, Section 4.3." 440 ::= { bgpPeerEntry 10 } 441 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 443 bgpPeerOutUpdates OBJECT-TYPE 444 SYNTAX Counter32 445 MAX-ACCESS read-only 446 STATUS current 447 DESCRIPTION 448 "The number of BGP UPDATE messages 449 transmitted on this connection." 450 REFERENCE 451 "RFC yyyy, Section 4.3." 452 ::= { bgpPeerEntry 11 } 453 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 455 bgpPeerInTotalMessages OBJECT-TYPE 456 SYNTAX Counter32 457 MAX-ACCESS read-only 458 STATUS current 459 DESCRIPTION 460 "The total number of messages received 461 from the remote peer on this connection." 462 REFERENCE 463 "RFC yyyy, Section 4." 464 ::= { bgpPeerEntry 12 } 465 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 467 bgpPeerOutTotalMessages OBJECT-TYPE 468 SYNTAX Counter32 469 MAX-ACCESS read-only 470 STATUS current 471 DESCRIPTION 472 "The total number of messages transmitted to 473 the remote peer on this connection." 474 REFERENCE 475 "RFC yyyy, Section 4." 476 ::= { bgpPeerEntry 13 } 477 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 479 bgpPeerLastError OBJECT-TYPE 480 SYNTAX OCTET STRING (SIZE (2)) 481 MAX-ACCESS read-only 482 STATUS current 483 DESCRIPTION 484 "The last error code and subcode seen by this 485 peer on this connection. If no error has 486 occurred, this field is zero. Otherwise, the 487 first byte of this two byte OCTET STRING 488 contains the error code, and the second byte 489 contains the subcode." 490 REFERENCE 491 "RFC yyyy, Section 4.5." 492 ::= { bgpPeerEntry 14 } 493 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 495 bgpPeerFsmEstablishedTransitions OBJECT-TYPE 496 SYNTAX Counter32 497 MAX-ACCESS read-only 498 STATUS current 499 DESCRIPTION 500 "The total number of times the BGP FSM 501 transitioned into the established state 502 for this peer." 503 REFERENCE 504 "RFC yyyy, Section 8." 505 ::= { bgpPeerEntry 15 } 506 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 508 bgpPeerFsmEstablishedTime OBJECT-TYPE 509 SYNTAX Gauge32 510 UNITS "seconds" 511 MAX-ACCESS read-only 512 STATUS current 513 DESCRIPTION 514 "This timer indicates how long (in 515 seconds) this peer has been in the 516 established state or how long 517 since this peer was last in the 518 established state. It is set to zero when 519 a new peer is configured or the router is 520 booted." 521 REFERENCE 522 "RFC yyyy, Section 8." 523 ::= { bgpPeerEntry 16 } 524 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 525 bgpPeerConnectRetryInterval OBJECT-TYPE 526 SYNTAX Integer32 (1..65535) 527 UNITS "seconds" 528 MAX-ACCESS read-write 529 STATUS current 530 DESCRIPTION 531 "Time interval in seconds for the 532 ConnectRetry timer. The suggested value 533 for this timer is 120 seconds." 534 REFERENCE 535 "RFC yyyy, Section 8.2.2. This is the value used 536 to initialize the 'ConnectRetryTimer'." 537 ::= { bgpPeerEntry 17 } 538 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 540 bgpPeerHoldTime OBJECT-TYPE 541 SYNTAX Integer32 ( 0 | 3..65535 ) 542 UNITS "seconds" 543 MAX-ACCESS read-only 544 STATUS current 545 DESCRIPTION 546 "Time interval in seconds for the Hold 547 Timer established with the peer. The 548 value of this object is calculated by this 549 BGP speaker by using the smaller of the 550 value in bgpPeerHoldTimeConfigured and the 551 Hold Time received in the OPEN message. 553 This value must be at least three seconds 554 if it is not zero (0). 556 If the Hold Timer has not been established 557 with the peer this object MUST have a value 558 of zero (0). 560 If the bgpPeerHoldTimeConfigured object has 561 a value of (0), then this object MUST have a 562 value of (0)." 563 REFERENCE 564 "RFC yyyy, Section 4.2." 565 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 566 ::= { bgpPeerEntry 18 } 568 bgpPeerKeepAlive OBJECT-TYPE 569 SYNTAX Integer32 ( 0 | 1..21845 ) 570 UNITS "seconds" 571 MAX-ACCESS read-only 572 STATUS current 573 DESCRIPTION 574 "Time interval in seconds for the KeepAlive 575 timer established with the peer. The value 576 of this object is calculated by this BGP 577 speaker such that, when compared with 578 bgpPeerHoldTime, it has the same proportion 579 as what bgpPeerKeepAliveConfigured has when 580 compared with bgpPeerHoldTimeConfigured. 582 If the KeepAlive timer has not been established 583 with the peer this object MUST have a value 584 of zero (0). 586 If the of bgpPeerKeepAliveConfigured object 587 has a value of (0), then this object MUST have 588 a value of (0)." 589 REFERENCE 590 "RFC yyyy, Section 4.4." 591 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 592 ::= { bgpPeerEntry 19 } 594 bgpPeerHoldTimeConfigured OBJECT-TYPE 595 SYNTAX Integer32 ( 0 | 3..65535 ) 596 UNITS "seconds" 597 MAX-ACCESS read-write 598 STATUS current 599 DESCRIPTION 600 "Time interval in seconds for the Hold Time 601 configured for this BGP speaker with this 602 peer. This value is placed in an OPEN 603 message sent to this peer by this BGP 604 speaker, and is compared with the Hold 605 Time field in an OPEN message received 606 from the peer when determining the Hold 607 Time (bgpPeerHoldTime) with the peer. 608 This value must not be less than three 609 seconds if it is not zero (0) in which 610 case the Hold Time is NOT to be 611 established with the peer. The suggested 612 value for this timer is 90 seconds." 613 REFERENCE 614 "RFC yyyy, Section 4.2." 615 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 616 ::= { bgpPeerEntry 20 } 617 bgpPeerKeepAliveConfigured OBJECT-TYPE 618 SYNTAX Integer32 ( 0 | 1..21845 ) 619 UNITS "seconds" 620 MAX-ACCESS read-write 621 STATUS current 622 DESCRIPTION 623 "Time interval in seconds for the 624 KeepAlive timer configured for this BGP 625 speaker with this peer. The value of this 626 object will only determine the 627 KEEPALIVE messages' frequency relative to 628 the value specified in 629 bgpPeerHoldTimeConfigured; the actual 630 time interval for the KEEPALIVE messages is 631 indicated by bgpPeerKeepAlive. A 632 reasonable maximum value for this timer 633 would be configured to be one 634 third of that of 635 bgpPeerHoldTimeConfigured. 636 If the value of this object is zero (0), 637 no periodical KEEPALIVE messages are sent 638 to the peer after the BGP connection has 639 been established. The suggested value for 640 this timer is 30 seconds." 641 REFERENCE 642 "RFC yyyy, Section 4.4." 643 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 644 ::= { bgpPeerEntry 21 } 646 bgpPeerMinASOriginationInterval OBJECT-TYPE 647 SYNTAX Integer32 (1..65535) 648 UNITS "seconds" 649 MAX-ACCESS read-write 650 STATUS current 651 DESCRIPTION 652 "Time interval in seconds for the 653 MinASOriginationInterval timer. 654 The suggested value for this timer is 15 655 seconds." 656 REFERENCE 657 "RFC yyyy, Section 9.2.1.2." 658 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 659 ::= { bgpPeerEntry 22 } 661 bgpPeerMinRouteAdvertisementInterval OBJECT-TYPE 662 SYNTAX Integer32 (1..65535) 663 UNITS "seconds" 664 MAX-ACCESS read-write 665 STATUS current 666 DESCRIPTION 667 "Time interval in seconds for the 668 MinRouteAdvertisementInterval timer. 669 The suggested value for this timer is 30 670 seconds." 671 REFERENCE 672 "RFC yyyy, Section 9.2.1.1." 673 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 674 ::= { bgpPeerEntry 23 } 676 bgpPeerInUpdateElapsedTime OBJECT-TYPE 677 SYNTAX Gauge32 678 UNITS "seconds" 679 MAX-ACCESS read-only 680 STATUS current 681 DESCRIPTION 682 "Elapsed time in seconds since the last BGP 683 UPDATE message was received from the peer. 684 Each time bgpPeerInUpdates is incremented, 685 the value of this object is set to zero (0)." 686 REFERENCE 687 "RFC yyyy, Section 4.3. 688 RFC yyyy, Section 8.2.2, Established state." 689 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 690 ::= { bgpPeerEntry 24 } 692 bgpIdentifier OBJECT-TYPE 693 SYNTAX IpAddress 694 MAX-ACCESS read-only 695 STATUS current 696 DESCRIPTION 697 "The BGP Identifier of the local system." 698 REFERENCE 699 "RFC yyyy, Section 4.2." 700 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 701 ::= { bgp 4 } 703 -- BGP Received Path Attribute Table. This table contains, 704 -- one entry per path to a network, path attributes 705 -- received from all peers running BGP version 3 or less. 706 -- This table is obsolete, having been replaced in 707 -- functionality with the bgp4PathAttrTable. 709 bgpRcvdPathAttrTable OBJECT-TYPE 710 SYNTAX SEQUENCE OF BgpPathAttrEntry 711 MAX-ACCESS not-accessible 712 STATUS obsolete 713 DESCRIPTION 714 "The BGP Received Path Attribute Table 715 contains information about paths to 716 destination networks received from all 717 peers running BGP version 3 or less." 718 ::= { bgp 5 } 720 bgpPathAttrEntry OBJECT-TYPE 721 SYNTAX BgpPathAttrEntry 722 MAX-ACCESS not-accessible 723 STATUS obsolete 724 DESCRIPTION 725 "Information about a path to a network." 726 INDEX { bgpPathAttrDestNetwork, 727 bgpPathAttrPeer } 728 ::= { bgpRcvdPathAttrTable 1 } 730 BgpPathAttrEntry ::= SEQUENCE { 731 bgpPathAttrPeer 732 IpAddress, 733 bgpPathAttrDestNetwork 734 IpAddress, 735 bgpPathAttrOrigin 736 INTEGER, 737 bgpPathAttrASPath 738 OCTET STRING, 739 bgpPathAttrNextHop 740 IpAddress, 741 bgpPathAttrInterASMetric 742 Integer32 743 } 745 bgpPathAttrPeer OBJECT-TYPE 746 SYNTAX IpAddress 747 MAX-ACCESS read-only 748 STATUS obsolete 749 DESCRIPTION 750 "The IP address of the peer where the path 751 information was learned." 752 ::= { bgpPathAttrEntry 1 } 753 bgpPathAttrDestNetwork OBJECT-TYPE 754 SYNTAX IpAddress 755 MAX-ACCESS read-only 756 STATUS obsolete 757 DESCRIPTION 758 "The address of the destination network." 759 REFERENCE 760 "RFC 1267, Section 4.3." 761 ::= { bgpPathAttrEntry 2 } 763 bgpPathAttrOrigin OBJECT-TYPE 764 SYNTAX INTEGER { 765 igp(1),-- networks are interior 766 egp(2),-- networks learned via the 767 -- EGP protocol 768 incomplete(3) -- networks that 769 -- are learned by some other 770 -- means 771 } 772 MAX-ACCESS read-only 773 STATUS obsolete 774 DESCRIPTION 775 "The ultimate origin of the path information." 776 REFERENCE 777 "RFC 1267, Section 4.3. 778 RFC 1267, Section 5." 779 ::= { bgpPathAttrEntry 3 } 781 bgpPathAttrASPath OBJECT-TYPE 782 SYNTAX OCTET STRING (SIZE (2..255)) 783 MAX-ACCESS read-only 784 STATUS obsolete 785 DESCRIPTION 786 "The set of ASs that must be traversed to reach 787 the network. This object is probably best 788 represented as SEQUENCE OF INTEGER. For SMI 789 compatibility, though, it is represented as 790 OCTET STRING. Each AS is represented as a pair 791 of octets according to the following algorithm: 793 first-byte-of-pair = ASNumber / 256; 794 second-byte-of-pair = ASNumber & 255;" 795 REFERENCE 796 "RFC 1267, Section 4.3. 797 RFC 1267, Section 5." 798 ::= { bgpPathAttrEntry 4 } 799 bgpPathAttrNextHop OBJECT-TYPE 800 SYNTAX IpAddress 801 MAX-ACCESS read-only 802 STATUS obsolete 803 DESCRIPTION 804 "The address of the border router that should 805 be used for the destination network." 806 REFERENCE 807 "RFC 1267, Section 4.3. 808 RFC 1267, Section 5." 809 ::= { bgpPathAttrEntry 5 } 811 bgpPathAttrInterASMetric OBJECT-TYPE 812 SYNTAX Integer32 813 MAX-ACCESS read-only 814 STATUS obsolete 815 DESCRIPTION 816 "The optional inter-AS metric. If this 817 attribute has not been provided for this route, 818 the value for this object is 0." 819 REFERENCE 820 "RFC 1267, Section 4.3. 821 RFC 1267, Section 5." 822 ::= { bgpPathAttrEntry 6 } 824 -- BGP-4 Received Path Attribute Table. This table 825 -- contains, one entry per path to a network, path 826 -- attributes received from all peers running BGP-4. 828 bgp4PathAttrTable OBJECT-TYPE 829 SYNTAX SEQUENCE OF Bgp4PathAttrEntry 830 MAX-ACCESS not-accessible 831 STATUS current 832 DESCRIPTION 833 "The BGP-4 Received Path Attribute Table 834 contains information about paths to 835 destination networks received from all 836 BGP4 peers." 837 ::= { bgp 6 } 839 bgp4PathAttrEntry OBJECT-TYPE 840 SYNTAX Bgp4PathAttrEntry 841 MAX-ACCESS not-accessible 842 STATUS current 843 DESCRIPTION 844 "Information about a path to a network." 845 INDEX { bgp4PathAttrIpAddrPrefix, 846 bgp4PathAttrIpAddrPrefixLen, 847 bgp4PathAttrPeer } 848 ::= { bgp4PathAttrTable 1 } 850 Bgp4PathAttrEntry ::= SEQUENCE { 851 bgp4PathAttrPeer 852 IpAddress, 853 bgp4PathAttrIpAddrPrefixLen 854 Integer32, 855 bgp4PathAttrIpAddrPrefix 856 IpAddress, 857 bgp4PathAttrOrigin 858 INTEGER, 859 bgp4PathAttrASPathSegment 860 OCTET STRING, 861 bgp4PathAttrNextHop 862 IpAddress, 863 bgp4PathAttrMultiExitDisc 864 Integer32, 865 bgp4PathAttrLocalPref 866 Integer32, 867 bgp4PathAttrAtomicAggregate 868 INTEGER, 869 bgp4PathAttrAggregatorAS 870 Integer32, 871 bgp4PathAttrAggregatorAddr 872 IpAddress, 873 bgp4PathAttrCalcLocalPref 874 Integer32, 875 bgp4PathAttrBest 876 INTEGER, 877 bgp4PathAttrUnknown 878 OCTET STRING 879 } 881 bgp4PathAttrPeer OBJECT-TYPE 882 SYNTAX IpAddress 883 MAX-ACCESS read-only 884 STATUS current 885 DESCRIPTION 886 "The IP address of the peer where the path 887 information was learned." 888 ::= { bgp4PathAttrEntry 1 } 890 bgp4PathAttrIpAddrPrefixLen OBJECT-TYPE 891 SYNTAX Integer32 (0..32) 892 MAX-ACCESS read-only 893 STATUS current 894 DESCRIPTION 895 "Length in bits of the IP address prefix in 896 the Network Layer Reachability 897 Information field." 898 ::= { bgp4PathAttrEntry 2 } 900 bgp4PathAttrIpAddrPrefix OBJECT-TYPE 901 SYNTAX IpAddress 902 MAX-ACCESS read-only 903 STATUS current 904 DESCRIPTION 905 "An IP address prefix in the Network Layer 906 Reachability Information field. This object 907 is an IP address containing the prefix with 908 length specified by 909 bgp4PathAttrIpAddrPrefixLen. 910 Any bits beyond the length specified by 911 bgp4PathAttrIpAddrPrefixLen are zeroed." 912 REFERENCE 913 "RFC yyyy, Section 4.3." 914 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 915 ::= { bgp4PathAttrEntry 3 } 917 bgp4PathAttrOrigin OBJECT-TYPE 918 SYNTAX INTEGER { 919 igp(1),-- networks are interior 920 egp(2),-- networks learned via the 921 -- EGP protocol 922 incomplete(3) -- networks that 923 -- are learned by some other 924 -- means 925 } 926 MAX-ACCESS read-only 927 STATUS current 928 DESCRIPTION 929 "The ultimate origin of the path 930 information." 931 REFERENCE 932 "RFC yyyy, Section 4.3. 934 RFC yyyy, Section 5.1.1." 935 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 936 ::= { bgp4PathAttrEntry 4 } 938 bgp4PathAttrASPathSegment OBJECT-TYPE 939 SYNTAX OCTET STRING (SIZE (2..255)) 940 MAX-ACCESS read-only 941 STATUS current 942 DESCRIPTION 943 "The sequence of AS path segments. Each AS 944 path segment is represented by a triple 945 . 947 The type is a 1-octet field which has two 948 possible values: 949 1 AS_SET: unordered set of ASs a 950 route in the UPDATE message 951 has traversed 953 2 AS_SEQUENCE: ordered set of ASs 954 a route in the UPDATE message 955 has traversed. 957 The length is a 1-octet field containing the 958 number of ASs in the value field. 960 The value field contains one or more AS 961 numbers, each AS is represented in the octet 962 string as a pair of octets according to the 963 following algorithm: 965 first-byte-of-pair = ASNumber / 256; 966 second-byte-of-pair = ASNumber & 255; 968 Known Issues: 969 o BGP Confederations will result in 970 a value of either 3 or 4. 971 o An AS Path may be longer than 255 octets. 972 This may result in this object containing 973 a truncated AS Path." 974 REFERENCE 975 "RFC yyyy, Section 4.3. 976 RFC yyyy, Section 5.1.2." 977 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 978 ::= { bgp4PathAttrEntry 5 } 979 bgp4PathAttrNextHop OBJECT-TYPE 980 SYNTAX IpAddress 981 MAX-ACCESS read-only 982 STATUS current 983 DESCRIPTION 984 "The address of the border router that 985 should be used for the destination 986 network. This address is the nexthop 987 address received in the UPDATE packet." 988 REFERENCE 989 "RFC yyyy, Section 4.3. 990 RFC yyyy, Section 5.1.3." 991 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 992 ::= { bgp4PathAttrEntry 6 } 994 bgp4PathAttrMultiExitDisc OBJECT-TYPE 995 SYNTAX Integer32 (-1..2147483647) 996 MAX-ACCESS read-only 997 STATUS current 998 DESCRIPTION 999 "This metric is used to discriminate 1000 between multiple exit points to an 1001 adjacent autonomous system. A value of -1 1002 indicates the absence of this attribute. 1004 Known Issues: 1005 o The BGP-4 specification uses an 1006 unsigned 32 bit number and thus this 1007 object cannot represent the full 1008 range of the protocol." 1009 REFERENCE 1010 "RFC yyyy, Section 4.3. 1011 RFC yyyy, Section 5.1.4." 1012 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 1013 ::= { bgp4PathAttrEntry 7 } 1015 bgp4PathAttrLocalPref OBJECT-TYPE 1016 SYNTAX Integer32 (-1..2147483647) 1017 MAX-ACCESS read-only 1018 STATUS current 1019 DESCRIPTION 1020 "The originating BGP4 speaker's degree of 1021 preference for an advertised route. A 1022 value of -1 indicates the absence of this 1023 attribute. 1025 Known Issues: 1026 o The BGP-4 specification uses an 1027 unsigned 32 bit number and thus this 1028 object cannot represent the full 1029 range of the protocol." 1030 REFERENCE 1031 "RFC yyyy, Section 4.3. 1032 RFC yyyy, Section 5.1.5." 1033 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 1034 ::= { bgp4PathAttrEntry 8 } 1036 bgp4PathAttrAtomicAggregate OBJECT-TYPE 1037 SYNTAX INTEGER { 1038 lessSpecificRouteNotSelected(1), 1039 -- Typo corrected from RFC 1657 1040 lessSpecificRouteSelected(2) 1041 } 1042 MAX-ACCESS read-only 1043 STATUS current 1044 DESCRIPTION 1045 "If the ATOMIC_AGGREGATE attribute is present 1046 in the Path Attributes then this object MUST 1047 have a value of 'lessSpecificRouteNotSelected'. 1049 If the ATOMIC_AGGREGATE attribute is missing 1050 in the Path Attributes then this object MUST 1051 have a value of 'lessSpecificRouteSelected'. 1053 Note that ATOMIC_AGGREGATE is now a primarily 1054 informational attribute." 1055 REFERENCE 1056 "RFC yyyy, Sections 5.1.6 and 9.1.4." 1057 -- RFC Ed.: Replace yyyy with latest BGP RFC 1058 ::= { bgp4PathAttrEntry 9 } 1060 bgp4PathAttrAggregatorAS OBJECT-TYPE 1061 SYNTAX Integer32 (0..65535) 1062 MAX-ACCESS read-only 1063 STATUS current 1064 DESCRIPTION 1065 "The AS number of the last BGP4 speaker that 1066 performed route aggregation. A value of 1067 zero (0) indicates the absence of this 1068 attribute. 1070 Note that propagation of AS of zero is illegal 1071 in the Internet." 1072 REFERENCE 1073 "RFC yyyy, Section 5.1.7. 1074 RFC yyyy, Section 9.2.2.2." 1075 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 1076 ::= { bgp4PathAttrEntry 10 } 1078 bgp4PathAttrAggregatorAddr OBJECT-TYPE 1079 SYNTAX IpAddress 1080 MAX-ACCESS read-only 1081 STATUS current 1082 DESCRIPTION 1083 "The IP address of the last BGP4 speaker 1084 that performed route aggregation. A 1085 value of 0.0.0.0 indicates the absence 1086 of this attribute." 1087 REFERENCE 1088 "RFC yyyy, Section 5.1.7. 1089 RFC yyyy, Section 9.2.2.2." 1090 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 1091 ::= { bgp4PathAttrEntry 11 } 1093 bgp4PathAttrCalcLocalPref OBJECT-TYPE 1094 SYNTAX Integer32 (-1..2147483647) 1095 MAX-ACCESS read-only 1096 STATUS current 1097 DESCRIPTION 1098 "The degree of preference calculated by the 1099 receiving BGP4 speaker for an advertised 1100 route. A value of -1 indicates the 1101 absence of this attribute. 1103 Known Issues: 1104 o The BGP-4 specification uses an 1105 unsigned 32 bit number and thus this 1106 object cannot represent the full 1107 range of the protocol." 1108 REFERENCE 1109 "RFC yyyy, Section 9.1.1." 1110 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 1111 ::= { bgp4PathAttrEntry 12 } 1113 bgp4PathAttrBest OBJECT-TYPE 1114 SYNTAX INTEGER { 1115 false(1),-- not chosen as best route 1116 true(2) -- chosen as best route 1117 } 1118 MAX-ACCESS read-only 1119 STATUS current 1120 DESCRIPTION 1121 "An indication of whether or not this route 1122 was chosen as the best BGP4 route for this 1123 destination." 1124 REFERENCE 1125 "RFC yyyy, Section 9.1.2." 1126 -- RFC Ed.: replace yyyy with actual RFC number for the new BGP specification 1127 ::= { bgp4PathAttrEntry 13 } 1129 bgp4PathAttrUnknown OBJECT-TYPE 1130 SYNTAX OCTET STRING (SIZE(0..255)) 1131 MAX-ACCESS read-only 1132 STATUS current 1133 DESCRIPTION 1134 "One or more path attributes not understood by 1135 this BGP4 speaker. 1137 Path attributes are recorded in the Update Path 1138 attribute format of type, length, value. 1140 Size zero (0) indicates the absence of such 1141 attributes. 1143 Octets beyond the maximum size, if any, are not 1144 recorded by this object. 1146 Known Issues: 1147 o Attributes understood by this speaker, but not 1148 represented in this MIB, are unavailable to 1149 the agent." 1150 ::= { bgp4PathAttrEntry 14 } 1152 -- Traps. 1154 -- Note that in RFC 1657, bgpTraps was incorrectly 1155 -- assigned a value of { bgp 7 } and each of the 1156 -- traps had the bgpPeerRemoteAddr object inappropriately 1157 -- removed from their OBJECTS clause. The following 1158 -- definitions restore the semantics of the traps as 1159 -- they were initially defined in RFC 1269. 1161 bgpNotification OBJECT IDENTIFIER ::= { bgp 0 } 1163 bgpEstablishedNotification NOTIFICATION-TYPE 1164 OBJECTS { bgpPeerRemoteAddr, 1165 bgpPeerLastError, 1166 bgpPeerState } 1167 STATUS current 1168 DESCRIPTION 1169 "The BGP Established event is generated when 1170 the BGP FSM enters the ESTABLISHED state. 1172 This Notification replaces the bgpEstablished 1173 Notification." 1174 ::= { bgpNotification 1 } 1176 bgpBackwardTransNotification NOTIFICATION-TYPE 1177 OBJECTS { bgpPeerRemoteAddr, 1178 bgpPeerLastError, 1179 bgpPeerState } 1180 STATUS current 1181 DESCRIPTION 1182 "The BGPBackwardTransNotification Event is 1183 generated when the BGP FSM moves from a higher 1184 numbered state to a lower numbered state. 1186 This Notification replaces the 1187 bgpBackwardsTransition Notification." 1188 ::= { bgpNotification 2 } 1190 -- { bgp 7 } is deprecated. Do not allocate new objects or 1191 -- notifications underneath this branch. 1193 bgpTraps OBJECT IDENTIFIER ::= { bgp 7 } -- deprecated 1195 bgpEstablished NOTIFICATION-TYPE 1196 OBJECTS { bgpPeerLastError, 1197 bgpPeerState } 1198 STATUS deprecated 1199 DESCRIPTION 1200 "The BGP Established event is generated when 1201 the BGP FSM enters the ESTABLISHED state. 1203 This Notification has been replaced by the 1204 bgpEstablishedNotification Notification." 1205 ::= { bgpTraps 1 } 1207 bgpBackwardTransition NOTIFICATION-TYPE 1208 OBJECTS { bgpPeerLastError, 1209 bgpPeerState } 1210 STATUS deprecated 1211 DESCRIPTION 1212 "The BGPBackwardTransition Event is generated 1213 when the BGP FSM moves from a higher numbered 1214 state to a lower numbered state. 1216 This Notification has been replaced by the 1217 bgpBackwardTransNotification Notification." 1218 ::= { bgpTraps 2 } 1220 -- Conformance information 1222 bgp4MIBConformance OBJECT IDENTIFIER 1223 ::= { bgp 8 } 1224 bgp4MIBCompliances OBJECT IDENTIFIER 1225 ::= { bgp4MIBConformance 1 } 1226 bgp4MIBGroups OBJECT IDENTIFIER 1227 ::= { bgp4MIBConformance 2 } 1229 -- Compliance statements 1231 bgp4MIBCompliance MODULE-COMPLIANCE 1232 STATUS current 1233 DESCRIPTION 1234 "The compliance statement for entities which 1235 implement the BGP4 mib." 1236 MODULE -- this module 1237 MANDATORY-GROUPS { bgp4MIBGlobalsGroup, 1238 bgp4MIBPeerGroup, 1239 bgp4MIBPathAttrGroup } 1240 GROUP bgp4MIBNotificationGroup 1241 DESCRIPTION 1242 "Implementation of BGP Notifications are 1243 completely optional in this MIB." 1244 ::= { bgp4MIBCompliances 1 } 1245 bgp4MIBDeprecatedCompliances MODULE-COMPLIANCE 1246 STATUS deprecated 1247 DESCRIPTION 1248 "The compliance statement documenting deprecated 1249 objects in the BGP4 mib." 1250 MODULE -- this module 1251 GROUP bgp4MIBTrapGroup 1252 DESCRIPTION 1253 "Group containing TRAP objects that were 1254 improperly converted from SMIv1 in RFC 1657. 1255 The proper semantics have been restored 1256 with the objects in bgp4MIBNotificationGroup." 1257 ::= { bgp4MIBCompliances 2 } 1259 bgp4MIBObsoleteCompliances MODULE-COMPLIANCE 1260 STATUS obsolete 1261 DESCRIPTION 1262 "The compliance statement documenting obsolete 1263 objects in the BGP4 mib." 1264 MODULE -- this module 1265 GROUP bgpRcvdPathAttrGroup 1266 DESCRIPTION 1267 "Group containing objects relevant to BGP-3 1268 and earlier objects." 1269 ::= { bgp4MIBCompliances 3 } 1271 -- Units of conformance 1273 bgp4MIBGlobalsGroup OBJECT-GROUP 1274 OBJECTS { bgpVersion, 1275 bgpLocalAs, 1276 bgpIdentifier } 1277 STATUS current 1278 DESCRIPTION 1279 "A collection of objects providing 1280 information on global BGP state." 1281 ::= { bgp4MIBGroups 1 } 1283 bgp4MIBPeerGroup OBJECT-GROUP 1284 OBJECTS { bgpPeerIdentifier, 1285 bgpPeerState, 1286 bgpPeerAdminStatus, 1287 bgpPeerNegotiatedVersion, 1288 bgpPeerLocalAddr, 1289 bgpPeerLocalPort, 1290 bgpPeerRemoteAddr, 1291 bgpPeerRemotePort, 1292 bgpPeerRemoteAs, 1293 bgpPeerInUpdates, 1294 bgpPeerOutUpdates, 1295 bgpPeerInTotalMessages, 1296 bgpPeerOutTotalMessages, 1297 bgpPeerLastError, 1298 bgpPeerFsmEstablishedTransitions, 1299 bgpPeerFsmEstablishedTime, 1300 bgpPeerConnectRetryInterval, 1301 bgpPeerHoldTime, 1302 bgpPeerKeepAlive, 1303 bgpPeerHoldTimeConfigured, 1304 bgpPeerKeepAliveConfigured, 1305 bgpPeerMinASOriginationInterval, 1306 bgpPeerMinRouteAdvertisementInterval, 1307 bgpPeerInUpdateElapsedTime } 1308 STATUS current 1309 DESCRIPTION 1310 "A collection of objects for managing 1311 BGP peers." 1312 ::= { bgp4MIBGroups 2 } 1314 bgpRcvdPathAttrGroup OBJECT-GROUP 1315 OBJECTS { bgpPathAttrPeer, 1316 bgpPathAttrDestNetwork, 1317 bgpPathAttrOrigin, 1318 bgpPathAttrASPath, 1319 bgpPathAttrNextHop, 1320 bgpPathAttrInterASMetric } 1321 STATUS obsolete 1322 DESCRIPTION 1323 "A collection of objects for managing BGP-3 and 1324 earlier path entries. 1326 This conformance group, like BGP-3, is obsolete." 1327 ::= { bgp4MIBGroups 3 } 1329 bgp4MIBPathAttrGroup OBJECT-GROUP 1330 OBJECTS { bgp4PathAttrPeer, 1331 bgp4PathAttrIpAddrPrefixLen, 1332 bgp4PathAttrIpAddrPrefix, 1333 bgp4PathAttrOrigin, 1334 bgp4PathAttrASPathSegment, 1335 bgp4PathAttrNextHop, 1336 bgp4PathAttrMultiExitDisc, 1337 bgp4PathAttrLocalPref, 1338 bgp4PathAttrAtomicAggregate, 1339 bgp4PathAttrAggregatorAS, 1340 bgp4PathAttrAggregatorAddr, 1341 bgp4PathAttrCalcLocalPref, 1342 bgp4PathAttrBest, 1343 bgp4PathAttrUnknown } 1344 STATUS current 1345 DESCRIPTION 1346 "A collection of objects for managing 1347 BGP path entries." 1348 ::= { bgp4MIBGroups 4 } 1350 bgp4MIBTrapGroup NOTIFICATION-GROUP 1351 NOTIFICATIONS { bgpEstablished, 1352 bgpBackwardTransition } 1353 STATUS deprecated 1354 DESCRIPTION 1355 "A collection of notifications for signaling 1356 changes in BGP peer relationships. 1358 Obsoleted by bgp4MIBNotificationGroup" 1359 ::= { bgp4MIBGroups 5 } 1361 bgp4MIBNotificationGroup NOTIFICATION-GROUP 1362 NOTIFICATIONS { bgpEstablishedNotification, 1363 bgpBackwardTransNotification } 1364 STATUS current 1365 DESCRIPTION 1366 "A collection of notifications for signaling 1367 changes in BGP peer relationships. 1369 Obsoletes bgp4MIBTrapGroup." 1370 ::= { bgp4MIBGroups 6 } 1372 END 1374 5. Intellectual Property 1376 The IETF takes no position regarding the validity or scope of any 1377 intellectual property or other rights that might be claimed to 1378 pertain to the implementation or use of the technology described in 1379 this document or the extent to which any license under such rights 1380 might or might not be available; neither does it represent that it 1381 has made any effort to identify any such rights. Information on the 1382 IETF's procedures with respect to rights in standards-track and 1383 standards-related documentation can be found in BCP-11. Copies of 1384 claims of rights made available for publication and any assurances of 1385 licenses to be made available, or the result of an attempt made to 1386 obtain a general license or permission for the use of such 1387 proprietary rights by implementors or users of this specification can 1388 be obtained from the IETF Secretariat. 1390 The IETF invites any interested party to bring to its attention any 1391 copyrights, patents or patent applications, or other proprietary 1392 rights which may cover technology that may be required to practice 1393 this standard. Please address the information to the IETF Executive 1394 Director. 1396 6. Security Considerations 1398 This MIB relates to a system providing inter-domain routing. As 1399 such, improper manipulation of the objects represented by this MIB 1400 may result in denial of service to a large number of end-users. 1402 There are several management objects defined in this MIB that have a 1403 MAX-ACCESS clause of read-write and/or read-create. Such objects 1404 should be considered sensitive or vulnerable in most network 1405 environments. The support for SET operations in a non-secure 1406 environment without proper protection can have a negative effect on 1407 network operations. These objects include: 1409 o bgpPeerAdminStatus 1411 Improper change of bgpPeerAdminStatus from start to stop can 1412 cause significant disruption of the connectivity to those 1413 portions of the Internet reached via the applicable remote BGP 1414 peer. 1416 o bgpPeerConnectRetryInterval 1418 Improper change of this object can cause connections to be 1419 disrupted for extremely long time periods when otherwise they 1420 would be restored in a relatively short period of time. 1422 o bgpPeerHoldTimeConfigured, bgpPeerKeepAliveConfigured 1424 Misconfiguration of these objects can make BGP sessions more 1425 fragile and less resilient to denial of service attacks on the 1426 inter-domain routing system. 1428 o bgpPeerMinASOriginationInterval, 1429 bgpPeerMinRouteAdvertisementInterval 1431 Misconfiguration of these objects may adversely affect global 1432 Internet convergence of the routes advertised by this BGP 1433 speaker. This may result in long-lived routing loops and 1434 blackholes for the portions of the Internet that utilize these 1435 routes." 1437 There are a number of managed objects in this MIB that 1438 contain sensitive information regarding the operation of a network. 1439 For example, a BGP peer's local and remote addresses might be 1440 sensitive for ISPs who want to keep interface addresses on routers 1441 confidential to prevent router addresses used for a denial of service 1442 attack or spoofing. 1444 Therefore, it is important in most environments to control read 1445 access to these objects and possibly to even encrypt the values of 1446 these object when sending them over the network via SNMP. 1448 SNMPv1 by itself is not a secure environment. Even if the network 1449 itself is secure (for example by using IPSec), there is still no 1450 control as to who on the secure network is allowed to access and 1451 GET/SET (read/change/create/delete) the objects in this MIB. 1453 It is recommended that the implementers consider the security 1454 features as provided by the SNMPv3 framework.[REF] Specifically, the 1455 implementation and use of the User-based Security Model [REF] and the 1456 View-based Access Control Model [REF] is recommended to provide 1457 appropriate security controls. 1459 It is then an operator/user responsibility to ensure that the SNMP 1460 entity giving access to an instance of this MIB, is properly 1461 configured to give access to the objects only to those principals 1462 (users) that have legitimate rights to indeed GET or SET 1463 (change/create/delete) them. 1465 7. Acknowledgements 1467 We would like to acknowledge the assistance of all the members of the 1468 Inter-Domain Routing Working Group, and particularly the following 1469 individuals: 1471 Yakov Rekhter, Juniper Networks 1472 Rob Coltun, Redback 1473 Guy Almes, Internet2 1474 Jeff Honig, BSDi 1475 Marshall T. Rose, Dover Beach Consulting, Inc. 1476 Dennis Ferguson, Juniper Networks 1477 Matt Mathis, PSC 1478 John Krawczyk, Bay Networks 1479 Curtis Villamizar, Avici 1480 Dave LeRoy, Pencom Systems 1481 Paul Traina, Juniper Networks 1482 Andrew Partan, MFN 1483 Robert Snyder, Cisco Systems 1484 Dimitry Haskin, Nortel 1485 Peder Chr Norgaard, Telebit Communications A/S 1486 Joel Halpern, CTO Longitude Systems, Inc. 1487 Nick Thille, RedBack Networks 1488 Bert Wijnen, Lucent 1489 Shane Wright, NextHop Technologies 1490 Mike McFadden, Riverstone Networks, Inc. 1491 Jon Saperia, JDS Consulting, Inc. 1492 Wayne Tackabury, Gold Wire Technology, Inc. 1493 Bill Fenner, AT&T Research 1494 RJ Atkinson, Extreme Networks 1495 Dan Romascanu, Avaya 1497 The origin of this document is from RFC 1269 "Definitions of Managed 1498 Objects for the Border Gateway Protocol (Version 3)" written by Steve 1499 Willis and John Burruss, which was updated by John Chu to support 1500 BGP-4 in RFC 1657. The editors wish to acknowledge the fine work of 1501 these original authors. 1503 8. IANA Considerations 1505 This document presents no new IANA considerations. 1507 9. Normative References 1509 [BGP4] Rekhter, Y., Li, T., Hares, S., "A Border Gateway 1510 Protocol 4 (BGP-4)", RFC yyyy, zzzz 2004. 1512 -- RFC Ed.: Replace yyyy with latest BGP RFC and zzzz with its 1513 -- month of publication 1515 [BGP4APP] Rekhter, Y., Gross, P., "Application of the Border 1516 Gateway Protocol in the Internet", RFC 1772, March 1995. 1518 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1519 Rose, M., and S. Waldbusser, "Structure of Management 1520 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1521 1999. 1523 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1524 Rose, M., and S. Waldbusser, "Textual Conventions for 1525 SMIv2", STD 58, RFC 2579, April 1999. 1527 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1528 Rose, M., and S. Waldbusser, "Conformance Statements for 1529 SMIv2", STD 58, RFC 2580, April 1999. 1531 10. Editors' Address 1533 Jeffrey Haas, Susan Hares 1534 NextHop Technologies 1535 825 Victor's Way, Suite 100 1536 Ann Arbor, MI 48103 1537 Phone: +1 734 222-1600 1538 Fax: +1 734 222-1602 1539 Email: jhaas@nexthop.com 1540 skh@nexthop.com 1541 11. Full Copyright Statement 1543 Copyright (C) The Internet Society (2004). All Rights Reserved. 1545 This document and translations of it may be copied and furnished to 1546 others, and derivative works that comment on or otherwise explain it 1547 or assist in its implementation may be prepared, copied, published 1548 and distributed, in whole or in part, without restriction of any 1549 kind, provided that the above copyright notice and this paragraph are 1550 included on all such copies and derivative works. However, this 1551 document itself may not be modified in any way, such as by removing 1552 the copyright notice or references to the Internet Society or other 1553 Internet organizations, except as needed for the purpose of 1554 developing Internet standards in which case the procedures for 1555 copyrights defined in the Internet Standards process must be 1556 followed, or as required to translate it into languages other than 1557 English. 1559 The limited permissions granted above are perpetual and will not be 1560 revoked by the Internet Society or its successors or assigns. 1562 This document and the information contained herein is provided on an 1563 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1564 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1565 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1566 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1567 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.