idnits 2.17.1 draft-ietf-idr-bgp4-mibv2-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 16. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 4055. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 4066. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 4073. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 4079. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 26 instances of too long lines in the document, the longest one being 6 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- 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 (June 22, 2008) is 5787 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 informational reference (is this intentional?): RFC 1657 (Obsoleted by RFC 4273) -- Obsolete informational reference (is this intentional?): RFC 3107 (Obsoleted by RFC 8277) Summary: 2 errors (**), 0 flaws (~~), 2 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Inter-Domain Routing Working Group J. Haas 3 Internet-Draft June 22, 2008 4 Intended status: Standards Track 5 Expires: December 24, 2008 7 Definitions of Managed Objects for the Fourth Version of Border Gateway 8 Protocol (BGP-4), Second Version 9 draft-ietf-idr-bgp4-mibv2-07 11 Status of This Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 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.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on December 24, 2008. 36 Copyright Notice 38 Copyright (C) The IETF Trust (2008). 40 Abstract 42 This memo defines a portion of the Management Information Base (MIB) 43 for use with network management protocols. In particular it defines 44 objects for managing the Border Gateway Protocol, Version 4. 46 Table of Contents 48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 49 2. The Internet-Standard Management Framework . . . . . . . . . . 3 50 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 53 5.1. Global Scalars . . . . . . . . . . . . . . . . . . . . . . 4 54 5.2. Tables . . . . . . . . . . . . . . . . . . . . . . . . . . 4 55 5.3. Obsoleted Tables . . . . . . . . . . . . . . . . . . . . . 5 56 5.4. Textual Conventions . . . . . . . . . . . . . . . . . . . 5 57 5.5. Notifications . . . . . . . . . . . . . . . . . . . . . . 6 58 5.6. Extensions . . . . . . . . . . . . . . . . . . . . . . . . 6 59 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 6 60 6.1. Relationship to the TCP-MIB . . . . . . . . . . . . . . . 6 61 6.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 7 62 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 7 63 8. Security Considerations . . . . . . . . . . . . . . . . . . . 80 64 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 82 65 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 82 66 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 82 67 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 84 68 12.1. Normative References . . . . . . . . . . . . . . . . . . . 84 69 12.2. Informative References . . . . . . . . . . . . . . . . . . 85 71 1. Introduction 73 This memo defines a portion of the Management Information Base (MIB) 74 for use with network management protocols. In particular it defines 75 objects for managing the Border Gateway Protocol, Version 4 76 [RFC4271]. 78 2. The Internet-Standard Management Framework 80 For a detailed overview of the documents that describe the current 81 Internet-Standard Management Framework, please refer to section 7 of 82 RFC 3410 [RFC3410]. 84 Managed objects are accessed via a virtual information store, termed 85 the Management Information Base or MIB. MIB objects are generally 86 accessed through the Simple Network Management Protocol (SNMP). 87 Objects in the MIB are defined using the mechanisms defined in the 88 Structure of Management Information (SMI). This memo specifies a MIB 89 module that is compliant to the SMIv2, which is described in STD 58, 90 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 91 [RFC2580]. 93 3. Conventions 95 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 96 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 97 document are to be interpreted as described in RFC 2119 [RFC2119]. 99 4. Overview 101 As part of the IETF standardization effort for the BGP-4 protocol, 102 [RFC4273] was written to address open issues in the previous version 103 of the BGP-4 MIB, [RFC1657]. However, that RFC was primarily 104 intended to address the base BGP-4 protocol as documented in 105 [RFC4271]. 107 The BGP-4 protocol has greatly increased in scope over the years from 108 its original definition. Scaling mechanisms such as Route Reflection 109 [RFC4456] and Confederations [RFC5065] have been introduced. Multi- 110 protocol extensions [RFC4760] were introduced which allowed 111 advertisement of reachability such as IPv6 [RFC2545], MPLS Labeled 112 routes [RFC3107], etc. 114 This MIB addresses several of the deficiencies of the previous BGP-4 115 MIB and provides an extension mechanism to permit additional MIB 116 modules to be authored without requiring the base BGP-4 MIB to be 117 updated. This is seen as a desirable goal since the BGP-4 protocol 118 continues to receive attention by those wishing to add to its 119 functionality. 121 In particular, this MIB addresses some specific weaknesses of the 122 previous version: 124 o Add the ability to monitor IPv6 BGP-4 peering sessions and carry 125 IPv6 reachability. Other forms of reachability can be added at a 126 later date courtesy of the address-family independent manner in 127 which this was done. 129 o Add several counters of operational interest. For example, the 130 number of routes received from a given BGP peer. 132 o Replaces objects that were incapable of carrying the full range of 133 their values with ones that can. 135 o Provides human-readable output for some complex data structures, 136 such as the AS_PATH while also preserving a version of the data 137 that is canonically machine readable. 139 5. Structure of the MIB Module 141 5.1. Global Scalars 143 o bgpVersion - A vector of supported BGP Versions. 145 o bgpIdentifier - The BGP identifier of the local system. 147 o bgpLocalAsNew - A 4-byte capable local AS number which replaces 148 the bgpLocalAs object. 150 o bgpAfPathAttrCounter - The number of entries in the 151 bgpAfPathAttrTable. 153 5.2. Tables 155 o bgpPeerAfTable - The BGP peer table. This table is capable of 156 representing IPv6 and other address-family (Af) independent 157 peering sessions. This table replaces the bgpPeerTable from 158 previous versions of this MIB. 160 o bgpPeerAfErrorsTable - A table of peering session errors. This 161 table covers information previously present in bgpPeerTable. 163 o bgpPeerAfEventTimesTable - A table of peer-specific event timers. 164 This table covers information previously present in bgpPeerTable. 166 o bgpPeerAfConfiguredTimersTable - A table of the configured values 167 of peer-specific event timers. This table covers information 168 previously present in bgpPeerTable. 170 o bgpPeerAfNegotiatedTimersTable - A table of per-peer negotiated 171 timers. This information covers information previously derived 172 from the bgpPeerTable. 174 o bgpPerAfCountersTable - A table of per-peer counters for messages 175 and the BGP FSM. 177 o bgpPrefixCountersTable - A table of per-peer per Address Family 178 Identifer-Subsequent Address Family Identifier (AFI-SAFI) 179 [RFC4760] counters for prefixes. 181 o bgpNlriTable - A table of per-peer per AFI-SAFI prefix data. This 182 table covers information previously present in bgp4PathAttrTable. 184 o bgpAdjRibsOutTable - A per-peer per AFI-SAFI table indicating what 185 reachability has been advertised to a given peer. 187 o bgpAfPathAttrTable - A table of BGP Path Attribute information. 189 o bgpAsPathTable - A table that decomposes the elements of a BGP AS 190 Path. 192 o bgpAfPathUnknownTable - A table that decomposes the unknown 193 elements received in a BGP Path Attribute tuple. 195 5.3. Obsoleted Tables 197 o bgpPeerTable - Replaced by the information in bgpPeerAfTable, 198 bgpPeerAfErrorsTable, bgpPeerConfiguredTimersTable, 199 bgpPeerAfNegotiatedTimersTable, bgpPeerAfCountersTable. 201 o bgpRcvPathAttrTable - Covered BGP-3 and earlier. 203 o bgp4PathAttrTable - Replaced by the information in bgpNlriTable, 204 bgpAfPathAttrTable and bgpAfPathUnknownTable. 206 5.4. Textual Conventions 208 o BgpIdentifierTC - Representation of a BGP Identifier 210 o BgpAddressFamilyIdentifierTC - Representation of a BGP Address 211 Family Identifier 213 o BgpSubsequentAddressFamilyIdentifierTC - Representation of a BGP 214 Subsequent Address Family Identifier 216 o BgpPathAttributeFlagsTC - Representation of BGP-4 Path Attribute 217 Flags. 219 5.5. Notifications 221 o bgpAfEstablishedNotification - Sent when a BGP peer transitions 222 into the Established state. Replaces the previous 223 bgpEstablishedNotification, which was not address family 224 independent. 226 o bgpAfBackwardTransitionNotification - Sent when a BGP peer 227 transitions out of the Established state. Replaces the previous 228 bgpBackwardTransNotification, which was not addrss family 229 independent. 231 o bgpEstablished - Erroneously added to an incorrect OID in a 232 previous version of this MIB. 234 o bgpBackwardsTransition - Erroneously added to an incorrect OID in 235 a previous version of this MIB. 237 5.6. Extensions 239 A feature of this MIB is the recognition that the BGP protocol 240 continues to grow in functionality. The bgpExtensions OID is defined 241 to provide a place for IDR-approved MIB modules for BGP extensions to 242 be added to the bgp MIB subtree. 244 It is intended that, where possible, that tables added via extensions 245 that add information via additional path attributes use 246 bgpAfPathAttrIndex as a common index, either via INDEX or AUGMENTS. 248 6. Relationship to Other MIB Modules 250 6.1. Relationship to the TCP-MIB 252 The bgpPeerAfLocalAddrType/bgpPeerAfLocalAddr/bgpPeerAfLocalPort and 253 bgpPeerAfRemoteAddrType/bgpPeerAfRemoteAddr/bgpPeerAfRemotePort 254 objects may provide a suitable index for monitoring the BGP peering 255 session's TCP session via the TCP-MIB [RFC4022]. 257 Note that conducting BGP peering sessions over transport protocols 258 other than TCP over IP are out of scope of the current BGP 259 specifications. 261 6.2. MIB modules required for IMPORTS 263 The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], 264 SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], INET-ADDRESS-MIB 265 [RFC4001] and SNMP-FRAMEWORK-MIB [RFC3411]. 267 7. Definitions 269 BGP4-MIB DEFINITIONS ::= BEGIN 271 IMPORTS 272 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 273 IpAddress, Counter32, Gauge32, mib-2, Unsigned32, Integer32 274 FROM SNMPv2-SMI 275 InetAddressType, InetAddress, InetPortNumber, 276 InetAutonomousSystemNumber, InetAddressPrefixLength 277 FROM INET-ADDRESS-MIB 278 TEXTUAL-CONVENTION, TruthValue, RowPointer, TimeStamp 279 FROM SNMPv2-TC 280 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 281 FROM SNMPv2-CONF 282 SnmpAdminString 283 FROM SNMP-FRAMEWORK-MIB; 285 bgp MODULE-IDENTITY 286 LAST-UPDATED "200806220000Z" 287 ORGANIZATION "IETF IDR Working Group" 288 CONTACT-INFO "E-mail: idr@ietf.org" 290 DESCRIPTION 291 "The MIB module for the BGP-4 protocol. 293 Copyright (C) The IETF Trust (2008). This 294 version of this MIB module is part of RFC XXX; 295 see the RFC itself for full legal notices." 296 -- RFC Editor - replace XXX with RFC number 298 REVISION "200806220000Z" 299 DESCRIPTION 300 "Changes from RFC 4273: 302 TODO" 304 REVISION "200601110000Z" 305 DESCRIPTION 306 "Changes from RFC 1657: 308 1) Fixed the definitions of the notifications 309 to make them equivalent to their initial 310 definition in RFC 1269. 311 2) Added compliance and conformance info. 312 3) Updated information for the values of 313 bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref, 314 bgp4PathAttrCalcLocalPref, 315 bgp4PathAttrMultiExitDisc, 316 bgp4PathAttrASPathSegement. 317 4) Added additional clarification comments where 318 needed. 319 5) Noted where objects do not fully reflect 320 the protocol as Known Issues. 321 6) Updated the DESCRIPTION for the 322 bgp4PathAttrAtomicAggregate object. 323 7) The following objects have had their DESCRIPTION 324 clause modified to remove the text that suggested 325 (using 'should' verb) initializing the counter 326 to zero on a transition to the established state: 327 bgpPeerInUpdates, bgpPeerOutUpdates, 328 bgpPeerInTotalMessages, bgpPeerOutTotalMessages 329 Those implementations that still do this are 330 still compliant with this new wording. 331 Applications should not assume counters have 332 started at zero. 334 Published as RFC 4273." 336 REVISION "199405050000Z" 337 DESCRIPTION 338 "Translated to SMIv2 and published as RFC 1657." 340 REVISION "199110261839Z" 341 DESCRIPTION 342 "Initial version, published as RFC 1269." 343 ::= { mib-2 15 } 345 -- 346 -- Textual Conventions 347 -- 349 -- TODO: Separate into BGP4-TC-MIB 350 BgpIdentifierTC ::= TEXTUAL-CONVENTION 351 DISPLAY-HINT "1d." 352 STATUS current 353 DESCRIPTION 354 "The representation of a BGP Identifier. BGP Identifiers 355 are presented in the received network byte order. 357 The BGP Identifier is displayed as if it is an IP address, 358 even if it would be an illegal one." 359 REFERENCE 360 "RFC 4273, Section 4.2" 361 SYNTAX OCTET STRING(SIZE (4)) 363 -- TODO: Separate into BGP4-TC-MIB 364 BgpAddressFamilyIdentifierTC ::= TEXTUAL-CONVENTION 365 DISPLAY-HINT "d" 366 STATUS current 367 DESCRIPTION 368 "The representation of a BGP AFI" 369 REFERENCE 370 "RFC 4760, Section 3" 371 SYNTAX Unsigned32(0..65535) 373 -- TODO: Separate into BGP4-TC-MIB 374 BgpSubsequentAddressFamilyIdentifierTC ::= TEXTUAL-CONVENTION 375 DISPLAY-HINT "d" 376 STATUS current 377 DESCRIPTION 378 "The representation of a BGP SAFI" 379 REFERENCE 380 "RFC 4760, Section 3" 381 SYNTAX Unsigned32(0..255) 383 BgpPathAttributeFlagsTC ::= TEXTUAL-CONVENTION 384 STATUS current 385 DESCRIPTION 386 "The representation of BGP Path Attribute Flags. Note that this 387 textual convention is meant to directly map to a BGP Path 388 Attribute's Flags and is thus constrained by protocol to have no 389 more than 8 total bits in use." 390 REFERENCE 391 "RFC 4271, Sec. 4.3" 392 SYNTAX BITS { 393 optional(0), -- When set, path attribute is optional instead of 394 -- well known. 395 transitive(1), -- Path attribute is transitive when set. 396 partial(2), -- Path attribute is partial when set. 397 extLength(3) -- Path attributes has extended length field. 398 -- 4-7 are reserved 399 -- values 8 or greater are illegal. 400 } 402 -- 403 -- Top level scalars for this MIB 404 -- 406 bgpVersion OBJECT-TYPE 407 SYNTAX OCTET STRING (SIZE (1..255)) 408 MAX-ACCESS read-only 409 STATUS current 410 DESCRIPTION 411 "Vector of supported BGP protocol version 412 numbers. Each peer negotiates the version 413 from this vector. Versions are identified 414 via the string of bits contained within this 415 object. The first octet contains bits 0 to 416 7, the second octet contains bits 8 to 15, 417 and so on, with the most significant bit 418 referring to the lowest bit number in the 419 octet (e.g., the MSB of the first octet 420 refers to bit 0). If a bit, i, is present 421 and set, then the version (i+1) of the BGP 422 is supported." 423 REFERENCE 424 "RFC 4271, Section 4.2." 425 ::= { bgp 1 } 427 -- { bgp 2 } and { bgp 3 } have been deprecated and are documented 428 -- elsewhere in this MIB 430 bgpIdentifier OBJECT-TYPE 431 SYNTAX IpAddress 432 MAX-ACCESS read-only 433 STATUS current 434 DESCRIPTION 435 "The BGP Identifier of the local system. 437 A SYNTAX of BgpIdentifierTC would be used here, 438 however it would cause this object to be 439 deprecated with no additional value. The 440 comments in the DESCRIPTION of BgpIdentifierTC 441 apply here." 442 REFERENCE 443 "RFC 4271, Section 4.2." 444 ::= { bgp 4 } 446 bgpLocalAsNew OBJECT-TYPE 447 SYNTAX InetAutonomousSystemNumber 448 MAX-ACCESS read-only 449 STATUS current 450 DESCRIPTION 451 "The local autonomous system number. 453 This object supports 4 byte ASes and replaces 454 bgpLocalAs." 455 REFERENCE 456 "RFC 4271, Section 4.2, 'My Autonomous System'. 458 RFC 4893, BGP Support for Four-octet AS Number 459 Space." 460 ::= { bgp 9 } 462 -- 463 -- Address Family (Af) independent per-peer management information. 464 -- 466 bgpPeerAf 467 OBJECT IDENTIFIER ::= { bgp 10 } 469 -- 470 -- Address Family (Af) independent per-peer session management 471 -- information. 472 -- 474 bgpPeerAfTable OBJECT-TYPE 475 SYNTAX SEQUENCE OF BgpPeerAfEntry 476 MAX-ACCESS not-accessible 477 STATUS current 478 DESCRIPTION 479 "BGP peer table. This table contains, one entry per BGP 480 peer, information about the connections with BGP peers. 482 This table replaces bgpPeerTable." 483 ::= { bgpPeerAf 1 } 485 bgpPeerAfEntry OBJECT-TYPE 486 SYNTAX BgpPeerAfEntry 487 MAX-ACCESS not-accessible 488 STATUS current 489 DESCRIPTION 490 "Entry containing information about the connection with 491 a remote BGP peer." 492 INDEX { 493 bgpPeerAfInstance, 494 bgpPeerAfLocalAddrType, 495 bgpPeerAfLocalAddr, 496 bgpPeerAfRemoteAddrType, 497 bgpPeerAfRemoteAddr 498 } 499 ::= { bgpPeerAfTable 1 } 501 BgpPeerAfEntry ::= SEQUENCE { 502 -- INDEX information 503 bgpPeerAfInstance 504 Unsigned32, 505 bgpPeerAfLocalAddrType 506 InetAddressType, 507 bgpPeerAfLocalAddr 508 InetAddress, 509 bgpPeerAfRemoteAddrType 510 InetAddressType, 511 bgpPeerAfRemoteAddr 512 InetAddress, 514 -- Local 515 bgpPeerAfLocalPort 516 InetPortNumber, 517 bgpPeerAfLocalAs 518 InetAutonomousSystemNumber, 520 -- Remote 521 bgpPeerAfRemotePort 522 InetPortNumber, 523 bgpPeerAfRemoteAs 524 InetAutonomousSystemNumber, 525 bgpPeerAfIdentifier 526 BgpIdentifierTC, 528 -- Session status 529 bgpPeerAfAdminStatus 530 INTEGER, 531 bgpPeerAfPeerState 532 INTEGER, 533 bgpPeerAfConfiguredVersion 534 Unsigned32, 535 bgpPeerAfNegotiatedVersion 536 Unsigned32 537 } 539 bgpPeerAfInstance OBJECT-TYPE 540 SYNTAX Unsigned32 (1..4294967295) 541 MAX-ACCESS not-accessible 542 STATUS current 543 DESCRIPTION 544 "The routing instance index. 546 Some BGP implementations permit the creation of 547 multiple instances of a BGP routing process. An 548 example includes routers running BGP/MPLS IP Virtual 549 Private Networks. 551 Implementations that do not support multiple 552 routing instances should return 1 for this object." 553 ::= { bgpPeerAfEntry 1 } 555 bgpPeerAfLocalAddrType OBJECT-TYPE 556 SYNTAX InetAddressType 557 MAX-ACCESS not-accessible 558 STATUS current 559 DESCRIPTION 560 "The address family of the local end of the peering 561 session." 562 ::= { bgpPeerAfEntry 2 } 564 bgpPeerAfLocalAddr OBJECT-TYPE 565 SYNTAX InetAddress 566 MAX-ACCESS not-accessible 567 STATUS current 568 DESCRIPTION 569 "The local IP address of this entry's BGP connection." 570 ::= { bgpPeerAfEntry 3 } 572 bgpPeerAfRemoteAddrType OBJECT-TYPE 573 SYNTAX InetAddressType 574 MAX-ACCESS not-accessible 575 STATUS current 576 DESCRIPTION 577 "The address family of the remote end of the peering 578 session." 579 ::= { bgpPeerAfEntry 4 } 581 bgpPeerAfRemoteAddr OBJECT-TYPE 582 SYNTAX InetAddress 583 MAX-ACCESS not-accessible 584 STATUS current 585 DESCRIPTION 586 "The remote IP address of this entry's BGP peer." 587 ::= { bgpPeerAfEntry 5 } 589 bgpPeerAfLocalPort OBJECT-TYPE 590 SYNTAX InetPortNumber 591 MAX-ACCESS read-only 592 STATUS current 593 DESCRIPTION 594 "The local port for the TCP connection between the BGP 595 peers." 596 ::= { bgpPeerAfEntry 6 } 598 bgpPeerAfLocalAs OBJECT-TYPE 599 SYNTAX InetAutonomousSystemNumber 600 MAX-ACCESS read-only 601 STATUS current 602 DESCRIPTION 603 "Some implementations of BGP can represent themselves 604 as multiple ASes. This is the AS that this peering 605 session is representing itself as to the remote peer." 606 ::= { bgpPeerAfEntry 7 } 608 bgpPeerAfRemotePort OBJECT-TYPE 609 SYNTAX InetPortNumber 610 MAX-ACCESS read-only 611 STATUS current 612 DESCRIPTION 613 "The remote port for the TCP connection between the BGP 614 peers. 616 Note that the objects bgpPeerAfLocalAddr, 617 bgpPeerAfLocalPort, bgpPeerAfRemoteAddr and 618 bgpPeerAfRemotePort provide the appropriate reference to 619 the standard MIB TCP connection table, or even the ipv6 620 TCP MIB as in RFC 4022." 621 REFERENCE 622 "RFC 2012 - SNMPv2 Management Information Base for the 623 Transmission Control Protocol using SMIv2. 624 RFC 4022 - IP Version 6 Management Information Base 625 for the Transmission Control Protocol." 626 ::= { bgpPeerAfEntry 8 } 628 bgpPeerAfRemoteAs OBJECT-TYPE 629 SYNTAX InetAutonomousSystemNumber 630 MAX-ACCESS read-only 631 STATUS current 632 DESCRIPTION 633 "The remote autonomous system number received in the BGP 634 OPEN message." 635 REFERENCE 636 "RFC 4271, Section 4.2." 637 ::= { bgpPeerAfEntry 9 } 639 bgpPeerAfIdentifier OBJECT-TYPE 640 SYNTAX BgpIdentifierTC 641 MAX-ACCESS read-only 642 STATUS current 643 DESCRIPTION 644 "The BGP Identifier of this entry's remote BGP peer. 646 This entry should be 0.0.0.0 unless the 647 bgpPeerAfPeerState is in the openconfirm or the 648 established state." 649 REFERENCE 650 "RFC 4271, Section 4.2, 'BGP Identifier'." 651 ::= { bgpPeerAfEntry 10 } 653 bgpPeerAfAdminStatus OBJECT-TYPE 654 SYNTAX INTEGER { 655 halted(1), 656 running(2) 657 } 658 MAX-ACCESS read-only 659 STATUS current 660 DESCRIPTION 661 "Whether or not the BGP FSM for this remote peer is 662 halted or running. The BGP FSM for a remote peer is 663 halted after processing a Stop event. Likewise, it is 664 in the running state after a Start event. 666 The bgpPeerAfState will generally be in the idle state 667 when the FSM is halted, although some extensions such 668 as Graceful Restart will leave the peer in the Idle 669 state but with the FSM running." 670 REFERENCE 671 "RFC 4271, Section 8.1.2." 672 ::= { bgpPeerAfEntry 11 } 674 -- TODO - update according to new FSM 675 bgpPeerAfPeerState OBJECT-TYPE 676 SYNTAX INTEGER { 677 idle(1), 678 connect(2), 679 active(3), 680 opensent(4), 681 openconfirm(5), 682 established(6) 683 } 684 MAX-ACCESS read-only 685 STATUS current 686 DESCRIPTION 687 "The BGP peer connection state." 688 REFERENCE 689 "RFC 4271, Section 8.2.2." 690 ::= { bgpPeerAfEntry 12 } 692 bgpPeerAfConfiguredVersion OBJECT-TYPE 693 SYNTAX Unsigned32 (1..255) 694 MAX-ACCESS read-only 695 STATUS current 696 DESCRIPTION 697 "The configured version to originally start with this 698 remote peer. The BGP speaker may permit negotiation to a 699 lower version number of the protocol." 700 REFERENCE 701 "RFC 4271, Section 4.2. 702 RFC 4271, Section 7." 703 ::= { bgpPeerAfEntry 13 } 705 bgpPeerAfNegotiatedVersion OBJECT-TYPE 706 SYNTAX Unsigned32 (1..255) 707 MAX-ACCESS read-only 708 STATUS current 709 DESCRIPTION 710 "The negotiated version of BGP running between 711 the two peers. 713 This entry MUST be zero (0) unless the 714 bgpPeerAfState is in the openconfirm or the 715 established state. 717 Note that legal values for this object are 718 between 0 and 255." 719 REFERENCE 720 "RFC 4271, Section 4.2. 721 RFC 4271, Section 7." 722 ::= { bgpPeerAfEntry 14 } 724 -- 725 -- Address Family (Af) independent per-peer error management 726 -- information. 727 -- 729 bgpPeerAfErrors 730 OBJECT IDENTIFIER ::= { bgpPeerAf 2 } 732 bgpPeerAfErrorsTable OBJECT-TYPE 733 SYNTAX SEQUENCE OF BgpPeerAfErrorsEntry 734 MAX-ACCESS not-accessible 735 STATUS current 736 DESCRIPTION 737 "On a per-peer basis, this table reflects the last 738 protocol-defined error encountered and reported on 739 the peer session. If no entry for a given peer 740 exists in this table, then no such errors have been 741 observed, reported, and recorded on the session." 742 ::= { bgpPeerAfErrors 1 } 744 bgpPeerAfErrorsEntry OBJECT-TYPE 745 SYNTAX BgpPeerAfErrorsEntry 746 MAX-ACCESS not-accessible 747 STATUS current 748 DESCRIPTION 749 "Each entry contains information about errors sent 750 and received for a particular BGP peer." 751 AUGMENTS { 752 bgpPeerAfEntry 753 } 754 ::= { bgpPeerAfErrorsTable 1 } 756 BgpPeerAfErrorsEntry ::= SEQUENCE { 757 bgpPeerAfLastErrorCodeReceived 758 OCTET STRING, 759 bgpPeerAfLastErrorSubCodeReceived 760 OCTET STRING, 761 bgpPeerAfLastErrorReceivedTime 762 TimeStamp, 763 bgpPeerAfLastErrorReceivedText 764 SnmpAdminString, 765 bgpPeerAfLastErrorReceivedData 766 OCTET STRING, 767 bgpPeerAfLastErrorCodeSent 768 OCTET STRING, 769 bgpPeerAfLastErrorSubCodeSent 770 OCTET STRING, 771 bgpPeerAfLastErrorSentTime 772 TimeStamp, 773 bgpPeerAfLastErrorSentText 774 SnmpAdminString, 775 bgpPeerAfLastErrorSentData 776 OCTET STRING 777 } 779 bgpPeerAfLastErrorCodeReceived OBJECT-TYPE 780 SYNTAX OCTET STRING (SIZE (1)) 781 MAX-ACCESS read-only 782 STATUS current 783 DESCRIPTION 784 "The last error code received from this peer via NOTIFICATION 785 message on this connection. If no error has occurred, this 786 field is zero." 788 REFERENCE 789 "RFC 4271, Section 4.5. 790 RFC 4486 optionally supported. 791 RFC 3362, Section 5 optionally supported." 792 ::= { bgpPeerAfErrorsEntry 1 } 794 bgpPeerAfLastErrorSubCodeReceived OBJECT-TYPE 795 SYNTAX OCTET STRING (SIZE (1)) 796 MAX-ACCESS read-only 797 STATUS current 798 DESCRIPTION 799 "The last subcode received from this peer via NOTIFICATION 800 message on this connection. If no error has occurred, this 801 field is zero." 802 REFERENCE 803 "RFC 4271, Section 4.5. 804 RFC 4486 optionally supported. 805 RFC 3362, Section 5 optionally supported." 806 ::= { bgpPeerAfErrorsEntry 2 } 808 bgpPeerAfLastErrorReceivedTime OBJECT-TYPE 809 SYNTAX TimeStamp 810 MAX-ACCESS read-only 811 STATUS current 812 DESCRIPTION 813 "The timestamp that the last NOTIFICATION was received from 814 this peer." 815 REFERENCE 816 "RFC 4271, Section 4.5." 817 ::= { bgpPeerAfErrorsEntry 3 } 819 bgpPeerAfLastErrorReceivedText OBJECT-TYPE 820 SYNTAX SnmpAdminString 821 MAX-ACCESS read-only 822 STATUS current 823 DESCRIPTION 824 "This object contains an implementation specific 825 explanation of the error that was reported." 826 ::= { bgpPeerAfErrorsEntry 4 } 828 bgpPeerAfLastErrorReceivedData OBJECT-TYPE 829 SYNTAX OCTET STRING (SIZE(0..4075)) 830 MAX-ACCESS read-only 831 STATUS current 832 DESCRIPTION 833 "The last error code's data seen by this peer. 835 Per RFC 2578, some implementations may have limitations 836 dealing with OCTET STRINGS larger than 255. Thus, this 837 data may be truncated." 838 REFERENCE 839 "RFC 4271, Section 4.5, 840 RFC 2578, Section 7.1.2, 841 RFC 4486 optionaly supported. 842 RFC 3362, Section 5 optionally supported." 843 ::= { bgpPeerAfErrorsEntry 5 } 845 bgpPeerAfLastErrorCodeSent OBJECT-TYPE 846 SYNTAX OCTET STRING (SIZE (1)) 847 MAX-ACCESS read-only 848 STATUS current 849 DESCRIPTION 850 "The last error code sent to this peer via NOTIFICATION 851 message on this connection. If no error has occurred, this 852 field is zero." 853 REFERENCE 854 "RFC 4271, Section 4.5. 855 RFC 4486 optionally supported. 856 RFC 3362, Section 5 optionally supported." 857 ::= { bgpPeerAfErrorsEntry 6 } 859 bgpPeerAfLastErrorSubCodeSent OBJECT-TYPE 860 SYNTAX OCTET STRING (SIZE (1)) 861 MAX-ACCESS read-only 862 STATUS current 863 DESCRIPTION 864 "The last subcode sent to this peer via NOTIFICATION 865 message on this connection. If no error has occurred, this 866 field is zero." 867 REFERENCE 868 "RFC 4271, Section 4.5. 869 RFC 4486 optionally supported. 870 RFC 3362, Section 5 optionally supported." 871 ::= { bgpPeerAfErrorsEntry 7 } 873 bgpPeerAfLastErrorSentTime OBJECT-TYPE 874 SYNTAX TimeStamp 875 MAX-ACCESS read-only 876 STATUS current 877 DESCRIPTION 878 "The timestamp that the last NOTIFICATION was sent to 879 this peer." 880 REFERENCE 881 "RFC 4271, Section 4.5." 882 ::= { bgpPeerAfErrorsEntry 8 } 884 bgpPeerAfLastErrorSentText OBJECT-TYPE 885 SYNTAX SnmpAdminString 886 MAX-ACCESS read-only 887 STATUS current 888 DESCRIPTION 889 "This object contains an implementation specific 890 explanation of the error that is being reported." 891 ::= { bgpPeerAfErrorsEntry 9 } 893 bgpPeerAfLastErrorSentData OBJECT-TYPE 894 SYNTAX OCTET STRING (SIZE(0..4075)) 895 MAX-ACCESS read-only 896 STATUS current 897 DESCRIPTION 898 "The last error code's data sent to this peer. 900 Per RFC 2578, some implementations may have limitations 901 dealing with OCTET STRINGS larger than 255. Thus, this 902 data may be truncated." 903 REFERENCE 904 "RFC 4271, Section 4.5, 905 RFC 2578, Section 7.1.2 906 RFC 4486 optionaly supported. 907 RFC 3362, Section 5 optionally supported." 908 ::= { bgpPeerAfErrorsEntry 10 } 910 -- 911 -- Address Family (Af) independent per-peer timer information 912 -- 914 bgpPeerAfTimers 915 OBJECT IDENTIFIER ::= { bgpPeerAf 3 } 917 -- 918 -- Per-peer Event Times 919 -- 921 bgpPeerAfEventTimesTable OBJECT-TYPE 922 SYNTAX SEQUENCE OF BgpPeerAfEventTimesEntry 923 MAX-ACCESS not-accessible 924 STATUS current 925 DESCRIPTION 926 "A table reporting the per-peering session amount 927 of time elapsed and update events since the peering 928 session advanced into the established state." 929 ::= { bgpPeerAfTimers 1 } 931 bgpPeerAfEventTimesEntry OBJECT-TYPE 932 SYNTAX BgpPeerAfEventTimesEntry 933 MAX-ACCESS not-accessible 934 STATUS current 935 DESCRIPTION 936 "Each row contains a set of statistics about time 937 spent and events encountered in the peer session 938 established state." 939 AUGMENTS { 940 bgpPeerAfEntry 941 } 942 ::= { bgpPeerAfEventTimesTable 1 } 944 BgpPeerAfEventTimesEntry ::= SEQUENCE { 945 bgpPeerAfFsmEstablishedTime 946 Gauge32, 947 bgpPeerAfInUpdatesElapsedTime 948 Gauge32 949 } 951 bgpPeerAfFsmEstablishedTime OBJECT-TYPE 952 SYNTAX Gauge32 953 UNITS "seconds" 954 MAX-ACCESS read-only 955 STATUS current 956 DESCRIPTION 957 "This timer indicates how long (in seconds) this peer 958 has been in the established state or how long since this 959 peer was last in the established state. It is set to 960 zero when a new peer is configured or when the router is 961 booted. If the peer has never reached the established 962 state, the value remains zero." 963 REFERENCE 964 "RFC 4271, Section 8." 965 ::= { bgpPeerAfEventTimesEntry 1 } 967 bgpPeerAfInUpdatesElapsedTime OBJECT-TYPE 968 SYNTAX Gauge32 969 UNITS "seconds" 970 MAX-ACCESS read-only 971 STATUS current 972 DESCRIPTION 973 "Elapsed time (in seconds) since the last BGP UPDATE 974 message was received from the peer. Each time 975 bgpPeerInUpdates is incremented, the value of this 976 object is set to zero (0)." 977 REFERENCE 978 "RFC 4271, Section 4.3. 979 RFC 4271, Section 8.2.2, Established state." 981 ::= { bgpPeerAfEventTimesEntry 2 } 983 -- 984 -- Per-Peer Configured Timers 985 -- 987 bgpPeerAfConfiguredTimersTable OBJECT-TYPE 988 SYNTAX SEQUENCE OF BgpPeerAfConfiguredTimersEntry 989 MAX-ACCESS not-accessible 990 STATUS current 991 DESCRIPTION 992 "Per peer management data on BGP session timers." 993 ::= { bgpPeerAfTimers 2 } 995 bgpPeerAfConfiguredTimersEntry OBJECT-TYPE 996 SYNTAX BgpPeerAfConfiguredTimersEntry 997 MAX-ACCESS not-accessible 998 STATUS current 999 DESCRIPTION 1000 "Each entry corresponds to the current state of 1001 BGP timers on a given peering session." 1002 AUGMENTS { 1003 bgpPeerAfEntry 1004 } 1005 ::= { bgpPeerAfConfiguredTimersTable 1 } 1007 BgpPeerAfConfiguredTimersEntry ::= SEQUENCE { 1008 bgpPeerAfConnectRetryInterval 1009 Unsigned32, 1010 bgpPeerAfHoldTimeConfigured 1011 Unsigned32, 1012 bgpPeerAfKeepAliveConfigured 1013 Unsigned32, 1014 bgpPeerAfMinASOrigInterval 1015 Unsigned32, 1016 bgpPeerAfMinRouteAdverInterval 1017 Unsigned32 1018 } 1020 bgpPeerAfConnectRetryInterval OBJECT-TYPE 1021 SYNTAX Unsigned32 (1..65535) 1022 UNITS "seconds" 1023 MAX-ACCESS read-only 1024 STATUS current 1025 DESCRIPTION 1026 "Time interval (in seconds) for the ConnectRetry timer. 1027 The suggested value for this timer is 120 seconds." 1028 REFERENCE 1029 "RFC 4271, Section 8.2.2. This is the value used 1030 to initialize the 'ConnectRetryTimer'." 1031 ::= { bgpPeerAfConfiguredTimersEntry 1 } 1033 bgpPeerAfHoldTimeConfigured OBJECT-TYPE 1034 SYNTAX Unsigned32 ( 0 | 3..65535 ) 1035 UNITS "seconds" 1036 MAX-ACCESS read-only 1037 STATUS current 1038 DESCRIPTION 1039 "Time interval (in seconds) for the Hold Timer 1040 established with the peer. The value of this object is 1041 calculated by this BGP speaker, using the smaller of the 1042 values in bgpPeerHoldTimeConfigured and the Hold Time 1043 received in the OPEN message. 1045 This value must be at least three seconds if it is not 1046 zero (0). 1048 If the Hold Timer has not been established with the 1049 peer this object MUST have a value of zero (0). 1051 If the bgpPeerHoldTimeConfigured object has a value of 1052 (0), then this object MUST have a value of (0)." 1053 REFERENCE 1054 "RFC 4271, Section 4.2." 1055 ::= { bgpPeerAfConfiguredTimersEntry 2 } 1057 bgpPeerAfKeepAliveConfigured OBJECT-TYPE 1058 SYNTAX Unsigned32 ( 0 | 1..21845 ) 1059 UNITS "seconds" 1060 MAX-ACCESS read-only 1061 STATUS current 1062 DESCRIPTION 1063 "Time interval (in seconds) for the KeepAlive timer 1064 configured for this BGP speaker with this peer. The 1065 value of this object will only determine the KEEPALIVE 1066 messages' frequency relative to the value specified in 1067 bgpPeerHoldTimeConfigured; the actual time interval for 1068 the KEEPALIVE messages is indicated by bgpPeerKeepAlive. 1070 A reasonable maximum value for this timer would be one 1071 third of that of bgpPeerHoldTimeConfigured. 1073 If the value of this object is zero (0), no periodic 1074 KEEPALIVE messages are sent to the peer after the BGP 1075 connection has been established. The suggested value 1076 for this timer is 30 seconds." 1078 REFERENCE 1079 "RFC 4271, Section 4.4. 1080 RFC 4271, Section 10." 1081 ::= { bgpPeerAfConfiguredTimersEntry 3 } 1083 bgpPeerAfMinASOrigInterval OBJECT-TYPE 1084 SYNTAX Unsigned32 (0..65535) 1085 UNITS "seconds" 1086 MAX-ACCESS read-only 1087 STATUS current 1088 DESCRIPTION 1089 "Time interval (in seconds) for the 1090 MinASOriginationInterval timer. 1092 The suggested value for this timer is 15 seconds." 1093 REFERENCE 1094 "RFC 4271, Section 9.2.1.2. 1095 RFC 4271, Section 10." 1096 ::= { bgpPeerAfConfiguredTimersEntry 4 } 1098 bgpPeerAfMinRouteAdverInterval OBJECT-TYPE 1099 SYNTAX Unsigned32 (0..65535) 1100 UNITS "seconds" 1101 MAX-ACCESS read-only 1102 STATUS current 1103 DESCRIPTION 1104 "Time interval (in seconds) for the 1105 MinRouteAdvertisementInterval timer. 1107 The suggested value for this timer is 30 seconds for 1108 EBGP connections and 5 seconds for IBGP connections." 1109 REFERENCE 1110 "RFC 4271, Section 9.2.1.1. 1111 RFC 4271, Section 10." 1112 ::= { bgpPeerAfConfiguredTimersEntry 5 } 1114 -- 1115 -- Per-Peer Negotiated Timers 1116 -- 1118 bgpPeerAfNegotiatedTimersTable OBJECT-TYPE 1119 SYNTAX SEQUENCE OF BgpPeerAfNegotiatedTimersEntry 1120 MAX-ACCESS not-accessible 1121 STATUS current 1122 DESCRIPTION 1123 "Configured values of per-peer timers are seen 1124 in the bgpPeerAfConfiguredTimersTable. 1126 Values in this table reflect the current 1127 operational values, after negotiation from values 1128 derived from initial configuration." 1129 ::= { bgpPeerAfTimers 3 } 1131 bgpPeerAfNegotiatedTimersEntry OBJECT-TYPE 1132 SYNTAX BgpPeerAfNegotiatedTimersEntry 1133 MAX-ACCESS not-accessible 1134 STATUS current 1135 DESCRIPTION 1136 "Each entry reflects a value of the currently 1137 operational, negotiated timer as reflected in the 1138 BgpPeerAfNegotiatedTimersEntry." 1139 AUGMENTS { 1140 bgpPeerAfEntry 1141 } 1142 ::= { bgpPeerAfNegotiatedTimersTable 1 } 1144 BgpPeerAfNegotiatedTimersEntry ::= SEQUENCE { 1145 bgpPeerAfHoldTime 1146 Unsigned32, 1147 bgpPeerAfKeepAlive 1148 Unsigned32 1149 } 1151 bgpPeerAfHoldTime OBJECT-TYPE 1152 SYNTAX Unsigned32 ( 0 | 3..65535 ) 1153 UNITS "seconds" 1154 MAX-ACCESS read-only 1155 STATUS current 1156 DESCRIPTION 1157 "The value of this object is calculated by this BGP 1158 Speaker as being; 1160 zero (0) - if this was the value sent by the peer and 1161 this value is permitted by this BGP Speaker. In this 1162 case, no keepalive messages are sent and the Hold Timer 1163 is not set. 1165 At least three (3). This value is the smaller of 1166 the value sent by this peer in the OPEN message and 1167 bgpPeerAfHoldTimeConfigured for this peer. 1169 This value is only defined when the peering session is 1170 in the Established state." 1171 REFERENCE 1172 "RFC 4271, Section 4.2." 1173 ::= { bgpPeerAfNegotiatedTimersEntry 1 } 1175 bgpPeerAfKeepAlive OBJECT-TYPE 1176 SYNTAX Unsigned32 ( 0 | 1..21845 ) 1177 UNITS "seconds" 1178 MAX-ACCESS read-only 1179 STATUS current 1180 DESCRIPTION 1181 "Time interval in seconds for the KeepAlive timer 1182 established with the peer. The value of this object 1183 is calculated by this BGP speaker such that, when 1184 compared with bgpPeerAfHoldTime, it has the same 1185 proportion as what bgpPeerAfKeepAliveConfigured has 1186 when compared with bgpPeerAfHoldTimeConfigured. If 1187 the value of this object is zero (0), it indicates 1188 that the KeepAlive timer has not been established 1189 with the peer, or, the value of 1190 bgpPeerAfKeepAliveConfigured is zero (0). 1192 This value is only defined when the peering session is 1193 in the Established state." 1194 REFERENCE 1195 "RFC 4271, Section 4.4." 1196 ::= { bgpPeerAfNegotiatedTimersEntry 2 } 1198 -- 1199 -- Per-peer counters 1200 -- 1202 bgpPeerAfCounters 1203 OBJECT IDENTIFIER ::= { bgpPeerAf 4 } 1205 bgpPeerAfCountersTable OBJECT-TYPE 1206 SYNTAX SEQUENCE OF BgpPeerAfCountersEntry 1207 MAX-ACCESS not-accessible 1208 STATUS current 1209 DESCRIPTION 1210 "The counters associated with a BGP Peer." 1211 ::= { bgpPeerAfCounters 1 } 1213 bgpPeerAfCountersEntry OBJECT-TYPE 1214 SYNTAX BgpPeerAfCountersEntry 1215 MAX-ACCESS not-accessible 1216 STATUS current 1217 DESCRIPTION 1218 "Each entry contains counters of message transmissions 1219 and FSM transitions for a given BGP Peering session." 1220 AUGMENTS { 1221 bgpPeerAfEntry 1222 } 1223 ::= { bgpPeerAfCountersTable 1 } 1225 BgpPeerAfCountersEntry ::= SEQUENCE { 1226 bgpPeerAfInUpdates 1227 Counter32, 1228 bgpPeerAfOutUpdates 1229 Counter32, 1230 bgpPeerAfInTotalMessages 1231 Counter32, 1232 bgpPeerAfOutTotalMessages 1233 Counter32, 1234 bgpPeerAfFsmEstablishedTransitions 1235 Counter32 1236 } 1238 bgpPeerAfInUpdates OBJECT-TYPE 1239 SYNTAX Counter32 1240 MAX-ACCESS read-only 1241 STATUS current 1242 DESCRIPTION 1243 "The number of BGP UPDATE messages received on this 1244 connection." 1245 ::= { bgpPeerAfCountersEntry 1 } 1247 bgpPeerAfOutUpdates OBJECT-TYPE 1248 SYNTAX Counter32 1249 MAX-ACCESS read-only 1250 STATUS current 1251 DESCRIPTION 1252 "The number of BGP UPDATE messages transmitted on this 1253 connection." 1254 ::= { bgpPeerAfCountersEntry 2 } 1256 bgpPeerAfInTotalMessages OBJECT-TYPE 1257 SYNTAX Counter32 1258 MAX-ACCESS read-only 1259 STATUS current 1260 DESCRIPTION 1261 "The total number of messages received from the remote 1262 peer on this connection." 1263 ::= { bgpPeerAfCountersEntry 3 } 1265 bgpPeerAfOutTotalMessages OBJECT-TYPE 1266 SYNTAX Counter32 1267 MAX-ACCESS read-only 1268 STATUS current 1269 DESCRIPTION 1270 "The total number of messages transmitted to the remote 1271 peer on this connection." 1272 ::= { bgpPeerAfCountersEntry 4 } 1274 bgpPeerAfFsmEstablishedTransitions OBJECT-TYPE 1275 SYNTAX Counter32 1276 MAX-ACCESS read-only 1277 STATUS current 1278 DESCRIPTION 1279 "The total number of times the BGP FSM transitioned into 1280 the established state for this peer." 1281 ::= { bgpPeerAfCountersEntry 5 } 1283 -- 1284 -- Per-Peer Prefix Counters 1285 -- 1287 bgpPrefixCountersTable OBJECT-TYPE 1288 SYNTAX SEQUENCE OF BgpPrefixCountersEntry 1289 MAX-ACCESS not-accessible 1290 STATUS current 1291 DESCRIPTION 1292 "Additional per-peer, per AFI-SAFI counters for 1293 prefixes" 1294 ::= { bgpPeerAfCounters 2 } 1296 bgpPrefixCountersEntry OBJECT-TYPE 1297 SYNTAX BgpPrefixCountersEntry 1298 MAX-ACCESS not-accessible 1299 STATUS current 1300 DESCRIPTION 1301 "Entry containing information about a bgp-peers prefix 1302 counters." 1303 INDEX { 1304 bgpPeerAfInstance, 1305 bgpPeerAfLocalAddrType, 1306 bgpPeerAfLocalAddr, 1307 bgpPeerAfRemoteAddrType, 1308 bgpPeerAfRemoteAddr, 1309 bgpPrefixCountersAfi, 1310 bgpPrefixCountersSafi 1311 } 1312 ::= { bgpPrefixCountersTable 1 } 1314 BgpPrefixCountersEntry ::= SEQUENCE { 1315 bgpPrefixCountersAfi 1316 BgpAddressFamilyIdentifierTC, 1317 bgpPrefixCountersSafi 1318 BgpSubsequentAddressFamilyIdentifierTC, 1320 bgpPrefixInPrefixes 1321 Gauge32, 1322 bgpPrefixInPrefixesAccepted 1323 Gauge32, 1324 bgpPrefixOutPrefixes 1325 Gauge32 1326 } 1328 bgpPrefixCountersAfi OBJECT-TYPE 1329 SYNTAX BgpAddressFamilyIdentifierTC 1330 MAX-ACCESS not-accessible 1331 STATUS current 1332 DESCRIPTION 1333 "The AFI index of the per-peer, per prefix counters" 1334 ::= { bgpPrefixCountersEntry 1 } 1336 bgpPrefixCountersSafi OBJECT-TYPE 1337 SYNTAX BgpSubsequentAddressFamilyIdentifierTC 1338 MAX-ACCESS not-accessible 1339 STATUS current 1340 DESCRIPTION 1341 "The SAFI index of the per-peer, per prefix counters" 1342 ::= { bgpPrefixCountersEntry 2 } 1344 bgpPrefixInPrefixes OBJECT-TYPE 1345 SYNTAX Gauge32 1346 MAX-ACCESS read-only 1347 STATUS current 1348 DESCRIPTION 1349 "The number of prefixes received from a peer and are 1350 stored in the Adj-Ribs-In for that peer. 1352 Note that this number does not reflect prefixes that 1353 have been discarded due to policy." 1354 REFERENCE 1355 "RFC 4271, Sections 3.2 and 9." 1356 ::= { bgpPrefixCountersEntry 3 } 1358 bgpPrefixInPrefixesAccepted OBJECT-TYPE 1359 SYNTAX Gauge32 1360 MAX-ACCESS read-only 1361 STATUS current 1362 DESCRIPTION 1363 "The number of prefixes for a peer that are installed 1364 in the Adj-Ribs-In and are eligible to become active 1365 in the Loc-Rib." 1366 REFERENCE 1367 "RFC 4271, Sections 3.2 and 9." 1369 ::= { bgpPrefixCountersEntry 4 } 1371 bgpPrefixOutPrefixes OBJECT-TYPE 1372 SYNTAX Gauge32 1373 MAX-ACCESS read-only 1374 STATUS current 1375 DESCRIPTION 1376 "The number of prefixes for a peer that are installed 1377 in that peer's Adj-Ribs-Out." 1378 REFERENCE 1379 "RFC 4271, Sections 3.2 and 9." 1380 ::= { bgpPrefixCountersEntry 5 } 1382 -- 1383 -- BGP NLRI Data 1384 -- 1386 bgpRib 1387 OBJECT IDENTIFIER ::= { bgp 11 } 1389 -- 1390 -- NLRI Table 1391 -- 1393 bgpNlriTable OBJECT-TYPE 1394 SYNTAX SEQUENCE OF BgpNlriEntry 1395 MAX-ACCESS not-accessible 1396 STATUS current 1397 DESCRIPTION 1398 "The BGP-4 Received Path Attribute Table contains 1399 information about paths to destination networks 1400 received from all BGP4 peers. Collectively, this 1401 represents the Adj-Ribs-In. The route where 1402 bgpNlriBest is true represents, for this NLRI, 1403 the route that is installed in the LocRib from the 1404 Adj-Ribs-In." 1405 REFERENCE 1406 "RFC 4271, Sections 3.2 and 9." 1407 ::= { bgpRib 1 } 1409 bgpNlriEntry OBJECT-TYPE 1410 SYNTAX BgpNlriEntry 1411 MAX-ACCESS not-accessible 1412 STATUS current 1413 DESCRIPTION 1414 "Information about a path to a network." 1415 INDEX { 1416 bgpNlriAfi, 1417 bgpNlriSafi, 1418 bgpNlriPrefix, 1419 bgpNlriPrefixLen, 1420 bgpNlriIndex, 1421 bgpPeerAfInstance, 1422 bgpPeerAfLocalAddrType, 1423 bgpPeerAfLocalAddr, 1424 bgpPeerAfRemoteAddrType, 1425 bgpPeerAfRemoteAddr 1426 } 1427 ::= { bgpNlriTable 1 } 1429 BgpNlriEntry ::= SEQUENCE { 1430 bgpNlriIndex 1431 Unsigned32, 1432 bgpNlriAfi 1433 BgpAddressFamilyIdentifierTC, 1434 bgpNlriSafi 1435 BgpSubsequentAddressFamilyIdentifierTC, 1436 bgpNlriPrefixType 1437 InetAddressType, 1438 bgpNlriPrefix 1439 InetAddress, 1440 bgpNlriPrefixLen 1441 InetAddressPrefixLength, 1442 bgpNlriBest 1443 TruthValue, 1444 bgpNlriCalcLocalPref 1445 Unsigned32, 1446 bgpAfPathAttrIndex 1447 Unsigned32, 1448 bgpAfPathAttrUnknownIndex 1449 Unsigned32 1450 } 1452 bgpNlriIndex OBJECT-TYPE 1453 SYNTAX Unsigned32 1454 MAX-ACCESS not-accessible 1455 STATUS current 1456 DESCRIPTION 1457 "This index allows for multiple instances of a base 1458 prefix for a certain AFI-SAFI from a given peer. 1459 This is currently useful for two things: 1460 1. Allowing for a peer in future implementations to 1461 send more than a single route instance. 1462 2. Allow for extensions which extend the NLRI field 1463 to send the same prefix while utilizing other 1464 extension specific information. An example of 1465 this is RFC 3107 - Carrying MPLS labels in BGP." 1466 REFERENCE 1467 "RFC 3107 - Carrying Label Information in BGP-4." 1468 ::= { bgpNlriEntry 1 } 1470 bgpNlriAfi OBJECT-TYPE 1471 SYNTAX BgpAddressFamilyIdentifierTC 1472 MAX-ACCESS not-accessible 1473 STATUS current 1474 DESCRIPTION 1475 "The address family of the prefix for this NLRI. 1477 Note that the AFI is not necessarily equivalent to 1478 the an InetAddressType." 1479 REFERENCE 1480 "RFC 4760 - Multiprotocol Extensions for BGP-4" 1481 ::= { bgpNlriEntry 2 } 1483 bgpNlriSafi OBJECT-TYPE 1484 SYNTAX BgpSubsequentAddressFamilyIdentifierTC 1485 MAX-ACCESS not-accessible 1486 STATUS current 1487 DESCRIPTION 1488 "The subsequent address family of the prefix for 1489 this NLRI" 1490 REFERENCE 1491 "RFC 4760 - Multiprotocol Extensions for BGP-4" 1492 ::= { bgpNlriEntry 3 } 1494 bgpNlriPrefixType OBJECT-TYPE 1495 SYNTAX InetAddressType 1496 MAX-ACCESS read-only 1497 STATUS current 1498 DESCRIPTION 1499 "The type of the IP address prefix in the 1500 Network Layer Reachability Information field. 1501 The value of this object is derived from the 1502 appropriate value from the bgpNlriAfi field. 1503 Where an appropriate InetAddressType is not 1504 available, the value of the object must be 1505 unknown(0)." 1506 ::= { bgpNlriEntry 4 } 1508 bgpNlriPrefix OBJECT-TYPE 1509 SYNTAX InetAddress 1510 MAX-ACCESS not-accessible 1511 STATUS current 1512 DESCRIPTION 1513 "An IP address prefix in the Network Layer 1514 Reachability Information field. This object 1515 is an IP address containing the prefix with 1516 length specified by 1517 bgpAfPathAttrAddrPrefixLen. 1518 Any bits beyond the length specified by 1519 bgpAfPathAttrAddrPrefixLen are zeroed." 1520 REFERENCE 1521 "RFC 4271, Section 4.3." 1522 ::= { bgpNlriEntry 5 } 1524 bgpNlriPrefixLen OBJECT-TYPE 1525 SYNTAX InetAddressPrefixLength 1526 MAX-ACCESS not-accessible 1527 STATUS current 1528 DESCRIPTION 1529 "Length in bits of the address prefix in 1530 the Network Layer Reachability Information field." 1531 ::= { bgpNlriEntry 6 } 1533 bgpNlriBest OBJECT-TYPE 1534 SYNTAX TruthValue 1535 MAX-ACCESS read-only 1536 STATUS current 1537 DESCRIPTION 1538 "An indication of whether or not this route 1539 was chosen as the best BGP4 route for this 1540 destination." 1541 REFERENCE 1542 "RFC 4271, Section 9.1.2." 1543 ::= { bgpNlriEntry 7 } 1545 bgpNlriCalcLocalPref OBJECT-TYPE 1546 SYNTAX Unsigned32 1547 MAX-ACCESS read-only 1548 STATUS current 1549 DESCRIPTION 1550 "The degree of preference calculated by the 1551 receiving BGP4 speaker for an advertised 1552 route. 1554 In the case where this prefix is ineligible, this 1555 object will be absent." 1556 REFERENCE 1557 "RFC 4271, Section 9.1.1" 1558 ::= { bgpNlriEntry 8 } 1560 bgpAfPathAttrIndex OBJECT-TYPE 1561 SYNTAX Unsigned32 1562 MAX-ACCESS read-only 1563 STATUS current 1564 DESCRIPTION 1565 "This value is a unique index for entries in the 1566 bgpAfPathAttrTable. It is assigned by the agent at the 1567 point of creation of the bgpAfPathAttrTable row entry. 1568 While its value is guaranteed to be unique at any time, 1569 it is otherwise opaque to the management application 1570 with respect to its value or the contiguity of 1571 bgpAfPathAttrIndex row instance values across rows of the 1572 bgpAfPathAttrTable. 1574 Note well that this index is used to distinguish unique 1575 sets of Path Attributes sent as part of BGP NLRI. The 1576 implementor is thus encouraged to make this index unique 1577 per set of all received path attributes. This value may 1578 be used to index tables in extension MIBs that share the 1579 property of belonging to the same received Path Attribute 1580 tuple." 1581 ::= { bgpNlriEntry 9 } 1583 bgpAfPathAttrUnknownIndex OBJECT-TYPE 1584 SYNTAX Unsigned32 1585 MAX-ACCESS read-only 1586 STATUS current 1587 DESCRIPTION 1588 "This value is a unique index for entries in the 1589 bgpAfPathAttrUnknownTable. It is assigned by the agent at 1590 the point of creation of the bgpAfPathAttrUnknownTable row 1591 entry. While its value is guaranteed to be unique at 1592 any time, it is otherwise opaque to the management 1593 application with respect to its value or the contiguity 1594 of bgpAfPathAttrUnknownIndex row instance values across 1595 rows of the bgpAfPathAttrUnknownTable." 1596 ::= { bgpNlriEntry 10 } 1598 -- 1599 -- Adj-Ribs-Out Table 1600 -- 1602 bgpAdjRibsOutTable OBJECT-TYPE 1603 SYNTAX SEQUENCE OF BgpAdjRibsOutEntry 1604 MAX-ACCESS not-accessible 1605 STATUS current 1606 DESCRIPTION 1607 "This table contains on a per-peer basis one or more 1608 routes from the bgpNlriTable that have been 1609 placed in this peer's Adj-Ribs-Out." 1610 REFERENCE 1611 "RFC 4271, Section 3.2." 1612 ::= { bgpRib 2 } 1614 bgpAdjRibsOutEntry OBJECT-TYPE 1615 SYNTAX BgpAdjRibsOutEntry 1616 MAX-ACCESS not-accessible 1617 STATUS current 1618 DESCRIPTION 1619 "List of BGP routes that have been placed into a 1620 peer's Adj-Ribs-Out." 1621 INDEX { 1622 bgpNlriAfi, 1623 bgpNlriSafi, 1624 bgpNlriPrefix, 1625 bgpNlriPrefixLen, 1626 bgpAdjRibsOutIndex, 1627 bgpPeerAfInstance, 1628 bgpPeerAfLocalAddrType, 1629 bgpPeerAfLocalAddr, 1630 bgpPeerAfRemoteAddrType, 1631 bgpPeerAfRemoteAddr 1632 } 1633 ::= { bgpAdjRibsOutTable 1 } 1635 BgpAdjRibsOutEntry ::= SEQUENCE { 1636 bgpAdjRibsOutIndex 1637 Unsigned32, 1638 bgpAdjRibsOutRoute 1639 RowPointer 1640 } 1642 bgpAdjRibsOutIndex OBJECT-TYPE 1643 SYNTAX Unsigned32 1644 MAX-ACCESS not-accessible 1645 STATUS current 1646 DESCRIPTION 1647 "Certain extensions to BGP permit multiple instance of 1648 a per afi, per safi prefix to be advertised to a peer. 1649 This object allows the enumeration of them." 1650 ::= { bgpAdjRibsOutEntry 1 } 1652 bgpAdjRibsOutRoute OBJECT-TYPE 1653 SYNTAX RowPointer 1654 MAX-ACCESS read-only 1655 STATUS current 1656 DESCRIPTION 1657 "This object points to the route in the bgpNlriTable 1658 that corresponds to the entry in the peer's 1659 Adj-Rib-Out. Outgoing route maps are not 1660 reflected at this point as those are part of the 1661 Update-Send process." 1662 REFERENCE 1663 "RFC 4271, Section 9.2." 1664 ::= { bgpAdjRibsOutEntry 2 } 1666 -- 1667 -- Path Attribute Counter 1668 -- 1670 bgpAfPathAttrCounter OBJECT-TYPE 1671 SYNTAX Counter32 1672 MAX-ACCESS read-only 1673 STATUS current 1674 DESCRIPTION 1675 "The number of entries in the bgpAfPathAttrTable." 1676 ::= { bgpRib 3 } 1678 -- 1679 -- Path Attributes Table 1680 -- 1682 bgpAfPathAttrTable OBJECT-TYPE 1683 SYNTAX SEQUENCE OF BgpAfPathAttrEntry 1684 MAX-ACCESS not-accessible 1685 STATUS current 1686 DESCRIPTION 1687 "Provides per advertised network-prefix attribute data, 1688 as advertised over a peering session." 1689 ::= { bgpRib 4 } 1691 bgpAfPathAttrEntry OBJECT-TYPE 1692 SYNTAX BgpAfPathAttrEntry 1693 MAX-ACCESS not-accessible 1694 STATUS current 1695 DESCRIPTION 1696 "Each entry contains data about path attributes 1697 associated with a given prefix in the bgpNlriTable." 1698 REFERENCE 1699 "RFC 4271, Section 5." 1700 INDEX { 1701 bgpAfPathAttrIndex 1702 } 1703 ::= { bgpAfPathAttrTable 1 } 1705 BgpAfPathAttrEntry ::= SEQUENCE { 1706 bgpAfPathAttrOrigin 1707 INTEGER, 1708 bgpAfPathAttrNextHopAddrType 1709 InetAddressType, 1710 bgpAfPathAttrNextHopAddr 1711 InetAddress, 1712 bgpAfPathAttrLinkLocalNextHopAddrType 1713 InetAddressType, 1714 bgpAfPathAttrLinkLocalNextHopAddr 1715 InetAddress, 1716 bgpAfPathAttrMedPresent 1717 TruthValue, 1718 bgpAfPathAttrMed 1719 Unsigned32, 1720 bgpAfPathAttrLocalPref 1721 Unsigned32, 1722 bgpAfPathAttrAtomicAggregate 1723 INTEGER, 1724 bgpAfPathAttrAggregatorAS 1725 InetAutonomousSystemNumber, 1726 bgpAfPathAttrAggregatorAddr 1727 BgpIdentifierTC, 1728 bgpAsPathCalcLength 1729 Unsigned32, 1730 bgpAsPathIndex 1731 Unsigned32, 1732 bgpAsPathString 1733 SnmpAdminString 1734 } 1736 bgpAfPathAttrOrigin OBJECT-TYPE 1737 SYNTAX INTEGER { 1738 igp(1),-- networks are interior 1739 egp(2),-- networks learned via the EGP protocol 1740 incomplete(3) -- networks that 1741 -- are learned by some other 1742 -- means 1743 } 1744 MAX-ACCESS read-only 1745 STATUS current 1746 DESCRIPTION 1747 "The ultimate origin of the path information." 1748 REFERENCE 1749 "RFC 4271, Section 4.3. 1750 RFC 4271, Section 5.1.1." 1751 ::= { bgpAfPathAttrEntry 1 } 1753 bgpAfPathAttrNextHopAddrType OBJECT-TYPE 1754 SYNTAX InetAddressType 1755 MAX-ACCESS read-only 1756 STATUS current 1757 DESCRIPTION 1758 "The address family of the address for 1759 the border router that should be used 1760 to access the destination network." 1761 ::= { bgpAfPathAttrEntry 2 } 1763 bgpAfPathAttrNextHopAddr OBJECT-TYPE 1764 SYNTAX InetAddress (SIZE(4..20)) 1765 MAX-ACCESS read-only 1766 STATUS current 1767 DESCRIPTION 1768 "The address of the border router that 1769 should be used to access the destination 1770 network. This address is the nexthop 1771 address received in the UPDATE packet associated with 1772 this prefix. 1774 Note that for RFC2545 style double nexthops, 1775 this object will always contain the global scope 1776 nexthop. bgpPathAttrLinkLocalNextHop will contain 1777 the linklocal scope nexthop, if it is present. 1779 In the case a mechanism is developed to use only a link 1780 local nexthop, bgpAfPathAttrNextHopAddr will contain the 1781 link local nexthop." 1782 REFERENCE 1783 "RFC 4271, Section 4.3, 1784 RFC 4271, Section 5.1.3, 1785 RFC 2545, Section 3." 1786 ::= { bgpAfPathAttrEntry 3 } 1788 bgpAfPathAttrLinkLocalNextHopAddrType OBJECT-TYPE 1789 SYNTAX InetAddressType 1790 MAX-ACCESS read-only 1791 STATUS current 1792 DESCRIPTION 1793 "The address type for IPv6 link local addresses. 1794 This is present only when receiving RFC 2545 1795 style double nexthops. 1797 This object is optionally present in BGP 1798 implementations that do not support IPv6." 1799 REFERENCE 1800 "RFC 2545, Section 3." 1802 ::= { bgpAfPathAttrEntry 4 } 1804 bgpAfPathAttrLinkLocalNextHopAddr OBJECT-TYPE 1805 SYNTAX InetAddress 1806 MAX-ACCESS read-only 1807 STATUS current 1808 DESCRIPTION 1809 "This value contains an IPv6 link local address 1810 and is present only when receiving RFC 2545 style 1811 double nexthops. 1813 This object is optionally present in BGP 1814 implementations that do not support IPv6." 1815 REFERENCE 1816 "RFC 2545, Section 3." 1817 ::= { bgpAfPathAttrEntry 5 } 1819 bgpAfPathAttrMedPresent OBJECT-TYPE 1820 SYNTAX TruthValue 1821 MAX-ACCESS read-only 1822 STATUS current 1823 DESCRIPTION 1824 "This value is true when the MED value was sent in 1825 the UPDATE message." 1826 ::= { bgpAfPathAttrEntry 6 } 1828 bgpAfPathAttrMed OBJECT-TYPE 1829 SYNTAX Unsigned32 1830 MAX-ACCESS read-only 1831 STATUS current 1832 DESCRIPTION 1833 "This metric is used to discriminate between multiple 1834 exit points to an adjacent autonomous system. When the MED 1835 value is absent but has a calculated default value, this 1836 object will contain the calculated value." 1837 REFERENCE 1838 "RFC 4271, Section 4.3. 1839 RFC 4271, Section 5.1.4." 1840 ::= { bgpAfPathAttrEntry 7 } 1842 bgpAfPathAttrLocalPref OBJECT-TYPE 1843 SYNTAX Unsigned32 1844 MAX-ACCESS read-only 1845 STATUS current 1846 DESCRIPTION 1847 "The originating BGP4 speakers degree of preference for an 1848 advertised route. If the route was not sent with a LOCAL_PREF 1849 value, this object will be absent." 1851 REFERENCE 1852 "RFC 4271, Section 4.3. 1853 RFC 4271, Section 5.1.5." 1854 ::= { bgpAfPathAttrEntry 8 } 1856 bgpAfPathAttrAtomicAggregate OBJECT-TYPE 1857 SYNTAX INTEGER { 1858 atomicAggregatePresent(1), 1859 atomicAggregateMissing(2) 1860 } 1861 MAX-ACCESS read-only 1862 STATUS current 1863 DESCRIPTION 1864 "When this object is set to atomicAggregatePresent, 1865 the ATOMIC_AGGREGATE Path Attribute is present and 1866 indicates that the NLRI MUST NOT be made more 1867 specific." 1868 REFERENCE 1869 "RFC 4271, Sections 5.1.6 and 9.1.4." 1870 ::= { bgpAfPathAttrEntry 9 } 1872 bgpAfPathAttrAggregatorAS OBJECT-TYPE 1873 SYNTAX InetAutonomousSystemNumber 1874 MAX-ACCESS read-only 1875 STATUS current 1876 DESCRIPTION 1877 "The AS number of the last BGP4 speaker that performed route 1878 aggregation. If the AGGREGATOR path attribute is absent, this 1879 object will not be present in the conceptual row." 1880 REFERENCE 1881 "RFC 4271, Section 5.1.7. 1882 RFC 4271, Section 9.2.2.2." 1883 ::= { bgpAfPathAttrEntry 10 } 1885 bgpAfPathAttrAggregatorAddr OBJECT-TYPE 1886 SYNTAX BgpIdentifierTC 1887 MAX-ACCESS read-only 1888 STATUS current 1889 DESCRIPTION 1890 "The IP address of the last BGP4 speaker that performed route 1891 aggregation. If the AGGREGATOR path attribute is absent, this 1892 object will not be present in the conceptual row." 1893 REFERENCE 1894 "RFC 4271, Section 5.1.7. 1895 RFC 4271, Section 9.2.2.2." 1896 ::= { bgpAfPathAttrEntry 11 } 1898 bgpAsPathCalcLength OBJECT-TYPE 1899 SYNTAX Unsigned32 1900 MAX-ACCESS read-only 1901 STATUS current 1902 DESCRIPTION 1903 "This value represents the calculated length of the 1904 AS Path according to the rules of the BGP 1905 specification. This value is used in route selection." 1906 REFERENCE 1907 "RFC 4271, Section 9.1.2.2.a" 1908 ::= { bgpAfPathAttrEntry 12 } 1910 bgpAsPathIndex OBJECT-TYPE 1911 SYNTAX Unsigned32 1912 MAX-ACCESS read-only 1913 STATUS current 1914 DESCRIPTION 1915 "This value is a unique index for the decomposed AS Path 1916 in the bgpAsPathTable. It is assigned by the 1917 agent at the point of creation of the bgpAsPathTable 1918 row entry. While its value is guaranteed to be unique 1919 at any time, it is otherwise opaque to the management 1920 application with respect to its value or the contiguity 1921 of bgpAsPathIndex row instance values across rows 1922 of the bgpAsPathTable." 1923 ::= { bgpAfPathAttrEntry 13 } 1925 bgpAsPathString OBJECT-TYPE 1926 SYNTAX SnmpAdminString 1927 MAX-ACCESS read-only 1928 STATUS current 1929 DESCRIPTION 1930 "This is a string depicting the autonomous system 1931 path to this network which was received from the 1932 peer which advertised it. The format of the string 1933 is implementation-dependent, and should be designed 1934 for operator readability. 1936 Note that SnmpAdminString is only capable of 1937 representing a maximum of 255 characters. This may 1938 lead to the string being truncated in the presence of 1939 a large AS Path. The bgpAsPathTable will give access 1940 to the full AS Path." 1941 ::= { bgpAfPathAttrEntry 14 } 1943 -- 1944 -- BGP 4 AS_PATH. This table provides a platform netrual 1945 -- representation of the AS_PATH. 1947 -- 1949 bgpAsPathTable OBJECT-TYPE 1950 SYNTAX SEQUENCE OF BgpAsPathEntry 1951 MAX-ACCESS not-accessible 1952 STATUS current 1953 DESCRIPTION 1954 "The BGP-4 Path Attribute AS Path Table 1955 contains the per network path (NLRI) 1956 AS PATH data received from the 1957 advertising BGP peer. 1959 Note that the bgpAsPathElementValue is 4-byte AS capable. This 1960 table and related objects in this MIB are meant to reflect the 1961 active AS_PATH for a 2-byte or a 4-byte AS speaker. For a 1962 transitional 2-byte to 4-byte speaker, the received AS_PATH and 1963 AS4_PATH path attributes may be present in an extension MIB." 1964 REFERENCE 1965 "RFC 4271, Sections 4.3 and 5.1.2. 1966 RFC 4893, BGP Support for Four-octet AS Number Space" 1967 ::= { bgpRib 5 } 1969 bgpAsPathEntry OBJECT-TYPE 1970 SYNTAX BgpAsPathEntry 1971 MAX-ACCESS not-accessible 1972 STATUS current 1973 DESCRIPTION 1974 "Information about an AS path provided with a path to 1975 a network." 1976 INDEX { 1977 bgpAsPathIndex, 1978 bgpAsPathSegmentIndex, 1979 bgpAsPathElementIndex 1980 } 1981 ::= { bgpAsPathTable 1 } 1983 BgpAsPathEntry ::= SEQUENCE { 1984 bgpAsPathSegmentIndex 1985 Unsigned32, 1986 bgpAsPathElementIndex 1987 Unsigned32, 1988 bgpAsPathType 1989 INTEGER, 1990 bgpAsPathElementValue 1991 InetAutonomousSystemNumber 1992 } 1994 bgpAsPathSegmentIndex OBJECT-TYPE 1995 SYNTAX Unsigned32 1996 MAX-ACCESS not-accessible 1997 STATUS current 1998 DESCRIPTION 1999 "A per-AS path segment index. This will index a set of 2000 autonomous systems in an AS path which are part 2001 of the same sequence or set (as determined by 2002 the row value of bgpAsPathType, which 2003 should be the same value for each bgpAsPathTable 2004 entry indexed by the same bgpAsPathIndex." 2005 REFERENCE 2006 "RFC 4271, Sections 4.3 and 5.1.2." 2007 ::= { bgpAsPathEntry 1 } 2009 bgpAsPathElementIndex OBJECT-TYPE 2010 SYNTAX Unsigned32 2011 MAX-ACCESS not-accessible 2012 STATUS current 2013 DESCRIPTION 2014 "A per-AS element index. This will index a particular 2015 AS within a sequence or set of autonomous systems in 2016 an AS path." 2017 REFERENCE 2018 "RFC 4271, Sections 4.3 and 5.1.2." 2019 ::= { bgpAsPathEntry 2 } 2021 bgpAsPathType OBJECT-TYPE 2022 SYNTAX INTEGER { 2023 asSet(1), 2024 asSequence(2), 2025 confedSequence(3), 2026 confedSet(4) 2027 } 2028 MAX-ACCESS read-only 2029 STATUS current 2030 DESCRIPTION 2031 "The path segment type advertised for the per-AS element. 2032 Note that all asPath row instances for a given 2033 bgpAsPathIndex index will have their 2034 bgpAsPathType set to the same value. 2035 The values for bgpAsPathType are 2036 interpreted as defined in the base BGP document 2037 and the BGP AS Confederations document." 2038 REFERENCE 2039 "RFC 4271, Sections 4.3 and 5.1.2, 2040 RFC 5065 - BGP AS Confederations" 2041 ::= { bgpAsPathEntry 3 } 2043 bgpAsPathElementValue OBJECT-TYPE 2044 SYNTAX InetAutonomousSystemNumber 2045 MAX-ACCESS read-only 2046 STATUS current 2047 DESCRIPTION 2048 "An AS the NLRI traversed in the propagation of its 2049 advertisement. This value is to be interpreted in 2050 the context of the segment type of the bgpAsPathType 2051 in the same conceptual row." 2052 ::= { bgpAsPathEntry 4 } 2054 -- BGP 4 Path unknown attribute. There is one row in 2055 -- this table for each attribute not known by this BGP 2056 -- implementation (or agent instrumentation), but provided 2057 -- from a peer. 2059 bgpAfPathAttrUnknownTable OBJECT-TYPE 2060 SYNTAX SEQUENCE OF BgpAfPathAttrUnknownEntry 2061 MAX-ACCESS not-accessible 2062 STATUS current 2063 DESCRIPTION 2064 "The BGP-4 Path Attribute Unknown Table 2065 contains the per network path (NLRI) 2066 data on the path attributes advertised 2067 with a route but not known to the local BGP 2068 implementation or not otherwise capable of being 2069 returned from this agent. 2071 The absence of row data for a given index value for 2072 bgpAfPathAttrIndex indicates a lack of such unknown 2073 attribute information for the indicated network path 2074 (as indexed by that bgpAfPathAttrIndex value in the 2075 bgpAfPathAttrTable)." 2076 REFERENCE 2077 "RFC 4271, Sections 4.3 and 5." 2078 ::= { bgpRib 6 } 2080 bgpAfPathAttrUnknownEntry OBJECT-TYPE 2081 SYNTAX BgpAfPathAttrUnknownEntry 2082 MAX-ACCESS not-accessible 2083 STATUS current 2084 DESCRIPTION 2085 "Information about an unknown attribute 2086 provided with a path to a network." 2087 INDEX { 2088 bgpAfPathAttrUnknownIndex, 2089 bgpAfPathAttrUnknownCode 2090 } 2091 ::= { bgpAfPathAttrUnknownTable 1 } 2093 BgpAfPathAttrUnknownEntry ::= SEQUENCE { 2094 bgpAfPathAttrUnknownCode 2095 Unsigned32, 2096 bgpAfPathAttrUnknownFlags 2097 BgpPathAttributeFlagsTC, 2098 bgpAfPathAttrUnknownValue 2099 OCTET STRING 2100 } 2102 bgpAfPathAttrUnknownCode OBJECT-TYPE 2103 SYNTAX Unsigned32 2104 MAX-ACCESS not-accessible 2105 STATUS current 2106 DESCRIPTION 2107 "The path attribute code advertised with this unknown 2108 attribute by the peer." 2109 ::= { bgpAfPathAttrUnknownEntry 1 } 2111 -- Maximum size of the following is derived as 2112 -- 4096 max message size 2113 -- - 16 BGP message marker bytes 2114 -- - 2 BGP message size 2115 -- - 1 BGP message type (UPDATE with unknown attr) 2116 -- - 2 UPDATE routes length (even assuming no routes) 2117 -- - 2 UPDATE path attributes length 2118 -- - 1 path attribute flag octet 2119 -- - 1 unknown path attr type (in bgpAfPathAttrUnknownCode) 2120 -- --------- 2121 -- 4071 bytes maximum per-message attribute value data 2123 bgpAfPathAttrUnknownFlags OBJECT-TYPE 2124 SYNTAX BgpPathAttributeFlagsTC 2125 MAX-ACCESS read-only 2126 STATUS current 2127 DESCRIPTION 2128 "The flags of the unknown path attribute." 2129 ::= { bgpAfPathAttrUnknownEntry 2 } 2131 bgpAfPathAttrUnknownValue OBJECT-TYPE 2132 SYNTAX OCTET STRING (SIZE(0..4071)) 2133 MAX-ACCESS read-only 2134 STATUS current 2135 DESCRIPTION 2136 "Value of path attribute not understood 2137 by the base BGP-4 document. 2139 Per RFC 2578, Section 7.1.2, some implementations 2140 may have limitations dealing with OCTET STRINGS 2141 larger than 255. Thus, this data may be truncated. 2143 Octets beyond the maximum size, if any, 2144 are not recorded by this row object." 2145 ::= { bgpAfPathAttrUnknownEntry 3 } 2147 -- 2148 -- Mount point for extensions 2149 -- 2151 bgpExtensions OBJECT IDENTIFIER ::= { bgp 12 } 2153 -- 2154 -- Discontinuity 2155 -- 2156 bgpDiscontinuityTime OBJECT-TYPE 2157 SYNTAX TimeStamp 2158 MAX-ACCESS read-only 2159 STATUS current 2160 DESCRIPTION 2161 "The value of sysUpTime at the most recent occasion at which 2162 this BGP management instance has suffered a discontinuity. 2164 In particular, tables with abstract indexes such as 2165 bgpAfPathAttrIndex, bgpAsPathIndex and 2166 bgpAfPathAttrUnknownIndex are not guaranteed to contain the 2167 same data across discontinuities." 2168 ::= { bgp 13 } 2170 -- 2171 -- Notifications 2172 -- 2174 bgpNotification OBJECT IDENTIFIER ::= { bgp 0 } 2176 -- bgpNotification 1 and 2 have been deprecated and are 2177 -- documented elsewhere in this MIB 2179 bgpAfEstablishedNotification NOTIFICATION-TYPE 2180 OBJECTS { 2181 bgpPeerAfPeerState, 2182 bgpPeerAfLocalPort, 2183 bgpPeerAfRemotePort 2184 } 2185 STATUS current 2186 DESCRIPTION 2187 "The BGP Established event is generated when 2188 the BGP FSM enters the established state." 2189 ::= { bgpNotification 3 } 2191 bgpAfBackwardTransitionNotification NOTIFICATION-TYPE 2192 OBJECTS { 2193 bgpPeerAfPeerState, 2194 bgpPeerAfLocalPort, 2195 bgpPeerAfRemotePort, 2196 bgpPeerAfLastErrorCodeReceived, 2197 bgpPeerAfLastErrorSubCodeReceived, 2198 bgpPeerAfLastErrorReceivedText 2199 } 2200 STATUS current 2201 DESCRIPTION 2202 "The BGPBackwardTransition Event is generated 2203 when the BGP FSM moves from a higher numbered 2204 state to a lower numbered state. 2206 Due to the nature of the BGP state machine, an implementation MAY 2207 rate limit the generation of this event. An implementation MAY 2208 also generate this notification ONLY when the state machine moves 2209 out of the established state. An implementation should document 2210 its specific behavior." 2211 ::= { bgpNotification 4 } 2213 -- 2214 -- Conformance Information 2215 -- 2217 bgpConformance 2218 OBJECT IDENTIFIER ::= { bgp 8 } 2220 bgp4MIBCompliances OBJECT IDENTIFIER ::= 2221 { bgpConformance 1 } 2223 bgp4MIBGroups OBJECT IDENTIFIER ::= 2224 { bgpConformance 2 } 2226 -- bgp4MIBCompliances 1 through 3 have been deprecated and are 2227 -- documented elsewhere in this MIB. 2229 bgpAfMIBCompliance MODULE-COMPLIANCE 2230 STATUS current 2231 DESCRIPTION 2232 "The compliance statement for entities which 2233 implement the BGP4 mib." 2234 MODULE -- this module 2235 MANDATORY-GROUPS { 2236 bgpTimersGroup, 2237 bgpCountersGroup, 2238 bgpAsPathGroup, 2239 bgpBaseGroup, 2240 bgpErrorsGroup, 2241 bgpPeerAfGroup, 2242 bgpAfPathAttributesGroup, 2243 bgpAfMIBGlobalsGroup 2244 } 2245 GROUP bgpAsPathGroup 2246 DESCRIPTION 2247 "This group is optional for all agent implementations." 2248 GROUP bgpAfMIBNotificationGroup 2249 DESCRIPTION 2250 "Implementation of BGP Notifications are completely 2251 optional in this MIB." 2253 OBJECT bgpPeerAfLocalAddr 2254 SYNTAX InetAddress (SIZE(4|16|20)) 2255 DESCRIPTION 2256 "An implementation is required to support IPv4 peering 2257 sessions. An implementation MAY support IPv6 peering 2258 sessions. IPv6 link-local peering sessions MAY be 2259 supported by this MIB." 2261 OBJECT bgpPeerAfRemoteAddr 2262 SYNTAX InetAddress (SIZE(4|16|20)) 2263 DESCRIPTION 2264 "An implementation is required to support IPv4 peering 2265 sessions. An implementation MAY support IPv6 peering 2266 sessions. IPv6 link-local peering sessions MAY be 2267 supported by this MIB." 2269 OBJECT bgpNlriPrefix 2270 SYNTAX InetAddress (SIZE(0..16)) 2271 DESCRIPTION 2272 "An implementation is required to support IPv4 prefixes. 2273 An implementation MAY support IPv6 prefixes." 2275 OBJECT bgpAfPathAttrLinkLocalNextHopAddrType 2276 SYNTAX InetAddressType 2277 DESCRIPTION 2278 "This object is only present when RFC 2545 double nexthops 2279 are sent for IPv6 reachability. IPv6 is optionally 2280 supported. When present, this object shall only have a 2281 value of ipv6z" 2283 OBJECT bgpAfPathAttrLinkLocalNextHopAddr 2284 SYNTAX InetAddress (SIZE(20)) 2285 DESCRIPTION 2286 "This object is only present when RFC 2545 double nexthops 2287 are sent for IPv6 reachability. IPv6 is optionally 2288 supported. When present, this object shall only have a 2289 size of 20." 2291 OBJECT bgpPeerAfInstance 2292 SYNTAX Unsigned32 (1..4294967295) 2293 DESCRIPTION 2294 "This object represents an abstract index which can utilize the 2295 full range of acceptable SNMP index values." 2297 OBJECT bgpNlriIndex 2298 SYNTAX Unsigned32 (1..4294967295) 2299 DESCRIPTION 2300 "This object represents an abstract index which can utilize the 2301 full range of acceptable SNMP index values." 2303 OBJECT bgpAdjRibsOutIndex 2304 SYNTAX Unsigned32 (1..4294967295) 2305 DESCRIPTION 2306 "This object represents an abstract index which can utilize the 2307 full range of acceptable SNMP index values." 2309 OBJECT bgpAfPathAttrIndex 2310 SYNTAX Unsigned32 (1..4294967295) 2311 DESCRIPTION 2312 "This object represents an abstract index which can utilize the 2313 full range of acceptable SNMP index values." 2315 OBJECT bgpAsPathIndex 2316 SYNTAX Unsigned32 (1..4294967295) 2317 DESCRIPTION 2318 "This object represents an abstract index which can utilize the 2319 full range of acceptable SNMP index values." 2321 OBJECT bgpAsPathSegmentIndex 2322 SYNTAX Unsigned32 (1..4294967295) 2323 DESCRIPTION 2324 "This object represents an abstract index which can utilize the 2325 full range of acceptable SNMP index values." 2327 OBJECT bgpAsPathElementIndex 2328 SYNTAX Unsigned32 (1..4294967295) 2329 DESCRIPTION 2330 "This object represents an abstract index which can utilize the 2331 full range of acceptable SNMP index values." 2333 OBJECT bgpAfPathAttrUnknownIndex 2334 SYNTAX Unsigned32 (1..4294967295) 2335 DESCRIPTION 2336 "This object represents an abstract index which can utilize the 2337 full range of acceptable SNMP index values." 2339 OBJECT bgpAfPathAttrUnknownCode 2340 SYNTAX Unsigned32 (0..255) 2341 DESCRIPTION 2342 "Path attribute codes are one octet." 2344 ::= { bgp4MIBCompliances 4 } 2346 bgpAfMIBDeprecatedCompliances MODULE-COMPLIANCE 2347 STATUS deprecated 2348 DESCRIPTION 2349 "The compliance statement for entities which 2350 implement the BGP4 mib." 2351 MODULE -- this module 2352 GROUP bgpAfMIBOldGlobalsGroup 2353 DESCRIPTION 2354 "Implementation of the bgp4MIBGlobalsGroup is OPTIONAL. 2355 If it is implemented, then bgp4MIBGlobalsGroup, 2356 bgp4MIBPeerGroup, bgp4MIBPathAttrGroup and 2357 bgp4MIBNotificationGroup MUST all be implemented." 2358 GROUP bgp4MIBPeerGroup 2359 DESCRIPTION 2360 "Implementation of the bgp4MIBPeerGroup is OPTIONAL. 2361 If it is implemented, then bgp4MIBGlobalsGroup, 2362 bgp4MIBPeerGroup, bgp4MIBPathAttrGroup and 2363 bgp4MIBNotificationGroup MUST all be implemented." 2364 GROUP bgp4MIBPathAttrGroup 2365 DESCRIPTION 2366 "Implementation of the bgp4MIBPathAttrGroup is OPTIONAL. 2367 If it is implemented, then bgp4MIBGlobalsGroup, 2368 bgp4MIBPeerGroup, bgp4MIBPathAttrGroup and 2369 bgp4MIBNotificationGroup MUST all be implemented." 2370 GROUP bgp4MIBNotificationGroup 2371 DESCRIPTION 2372 "Implementation of the bgp4MIBNotificationGroup is OPTIONAL. 2373 If it is implemented, then bgp4MIBGlobalsGroup, 2374 bgp4MIBPeerGroup, bgp4MIBPathAttrGroup and 2375 bgp4MIBNotificationGroup MUST all be implemented." 2376 ::= { bgp4MIBCompliances 5 } 2378 -- bgp4MIBGroups 1 through 7 have been deprecated and are documented 2379 -- elsewhere in this MIB. 2381 bgpAfMIBGlobalsGroup OBJECT-GROUP 2382 OBJECTS { bgpVersion, 2383 bgpIdentifier, 2384 bgpDiscontinuityTime } 2385 STATUS current 2386 DESCRIPTION 2387 "A collection of objects providing information on global 2388 BGP state. This group covers objects that overlap the 2389 old bgp4MIBGlobalsGroup that are still current." 2390 ::= { bgp4MIBGroups 8 } 2392 bgpAfMIBOldGlobalsGroup OBJECT-GROUP 2393 OBJECTS { bgpLocalAs } 2394 STATUS deprecated 2395 DESCRIPTION 2396 "A collection of objects providing information on global 2397 BGP state. This group covers objects that overlap the 2398 old bgp4MIBGlobalsGroup that are deprecated." 2399 ::= { bgp4MIBGroups 9 } 2401 bgpTimersGroup OBJECT-GROUP 2402 OBJECTS { 2403 bgpPeerAfFsmEstablishedTime, 2404 bgpPeerAfInUpdatesElapsedTime, 2405 bgpPeerAfConnectRetryInterval, 2406 bgpPeerAfHoldTimeConfigured, 2407 bgpPeerAfKeepAliveConfigured, 2408 bgpPeerAfMinASOrigInterval, 2409 bgpPeerAfMinRouteAdverInterval, 2410 bgpPeerAfHoldTime, 2411 bgpPeerAfKeepAlive 2412 } 2413 STATUS current 2414 DESCRIPTION 2415 "Objects associated with BGP peering timers." 2416 ::= { bgp4MIBGroups 10 } 2418 bgpCountersGroup OBJECT-GROUP 2419 OBJECTS { 2420 bgpPeerAfInUpdates, 2421 bgpPeerAfOutUpdates, 2422 bgpPeerAfInTotalMessages, 2423 bgpPeerAfOutTotalMessages, 2424 bgpPeerAfFsmEstablishedTransitions, 2425 bgpPrefixInPrefixes, 2426 bgpPrefixInPrefixesAccepted, 2427 bgpPrefixOutPrefixes 2428 } 2429 STATUS current 2430 DESCRIPTION 2431 "Objects to count discrete events and exchanges on BGP 2432 sessions." 2433 ::= { bgp4MIBGroups 11 } 2435 bgpAsPathGroup OBJECT-GROUP 2436 OBJECTS { 2437 bgpAsPathType, 2438 bgpAsPathElementValue 2439 } 2440 STATUS current 2441 DESCRIPTION 2442 "Objects to report AS paths received on BGP NLRIs." 2443 ::= { bgp4MIBGroups 12 } 2445 bgpBaseGroup OBJECT-GROUP 2446 OBJECTS { 2447 bgpLocalAsNew 2448 } 2449 STATUS current 2450 DESCRIPTION 2451 "Basic objects in local BGP implementation." 2452 ::= { bgp4MIBGroups 13 } 2454 bgpErrorsGroup OBJECT-GROUP 2455 OBJECTS { 2456 bgpPeerAfLastErrorCodeReceived, 2457 bgpPeerAfLastErrorSubCodeReceived, 2458 bgpPeerAfLastErrorReceivedData, 2459 bgpPeerAfLastErrorReceivedTime, 2460 bgpPeerAfLastErrorReceivedText, 2461 bgpPeerAfLastErrorCodeSent, 2462 bgpPeerAfLastErrorSubCodeSent, 2463 bgpPeerAfLastErrorSentData, 2464 bgpPeerAfLastErrorSentTime, 2465 bgpPeerAfLastErrorSentText 2466 } 2467 STATUS current 2468 DESCRIPTION 2469 "Errors received on BGP peering sessions." 2470 ::= { bgp4MIBGroups 14 } 2472 bgpPeerAfGroup OBJECT-GROUP 2473 OBJECTS { 2474 bgpPeerAfIdentifier, 2475 bgpPeerAfPeerState, 2476 bgpPeerAfAdminStatus, 2477 bgpPeerAfConfiguredVersion, 2478 bgpPeerAfNegotiatedVersion, 2479 bgpPeerAfLocalPort, 2480 bgpPeerAfLocalAs, 2481 bgpPeerAfRemotePort, 2482 bgpPeerAfRemoteAs 2483 } 2484 STATUS current 2485 DESCRIPTION 2486 "Core object types on BGP peering sessions." 2487 ::= { bgp4MIBGroups 15 } 2489 bgpAfPathAttributesGroup OBJECT-GROUP 2490 OBJECTS { 2491 bgpAfPathAttrCounter, 2492 bgpAsPathCalcLength, 2493 bgpAsPathElementValue, 2494 bgpAsPathIndex, 2495 bgpAsPathString, 2496 bgpAsPathType, 2497 bgpNlriBest, 2498 bgpNlriCalcLocalPref, 2499 bgpNlriPrefixType, 2500 bgpAdjRibsOutRoute, 2501 bgpAfPathAttrAggregatorAS, 2502 bgpAfPathAttrAggregatorAddr, 2503 bgpAfPathAttrAtomicAggregate, 2504 bgpAfPathAttrIndex, 2505 bgpAfPathAttrLocalPref, 2506 bgpAfPathAttrMed, 2507 bgpAfPathAttrMedPresent, 2508 bgpAfPathAttrNextHopAddr, 2509 bgpAfPathAttrNextHopAddrType, 2510 bgpAfPathAttrLinkLocalNextHopAddrType, 2511 bgpAfPathAttrLinkLocalNextHopAddr, 2512 bgpAfPathAttrOrigin, 2513 bgpAfPathAttrUnknownIndex, 2514 bgpAfPathAttrUnknownFlags, 2515 bgpAfPathAttrUnknownValue 2516 } 2517 STATUS current 2518 DESCRIPTION 2519 "Attributes received on BGP peering sessions." 2520 ::= { bgp4MIBGroups 16 } 2522 -- ========================================================= 2523 -- 2524 -- Objects that are deprecated from RFC 4273 follow below. 2525 -- 2526 -- ========================================================= 2528 bgpLocalAs OBJECT-TYPE 2529 SYNTAX Integer32 (0..65535) 2530 MAX-ACCESS read-only 2531 STATUS deprecated 2532 DESCRIPTION 2533 "The local autonomous system number. 2535 This object has been replaced with bgpLocalAsNew 2536 which can accomodate 4-byte AS numbers. When 2537 the Local AS number cannot be represented by 2538 a 2-byte number, this object should return the 2539 AS_TRANS value, 23456." 2540 REFERENCE 2541 "RFC 4271, Section 4.2, 'My Autonomous System'. 2543 RFC 4893, BGP Support for Four-octet AS Number 2544 Space." 2545 ::= { bgp 2 } 2547 -- BGP Peer table. This table contains, one entry per 2548 -- BGP peer, information about the BGP peer. 2550 bgpPeerTable OBJECT-TYPE 2551 SYNTAX SEQUENCE OF BgpPeerEntry 2552 MAX-ACCESS not-accessible 2553 STATUS deprecated 2554 DESCRIPTION 2555 "BGP peer table. This table contains, 2556 one entry per BGP peer, information about the 2557 connections with BGP peers. 2559 This table has been replaced with bgpPeerAfTable." 2560 ::= { bgp 3 } 2562 bgpPeerEntry OBJECT-TYPE 2563 SYNTAX BgpPeerEntry 2564 MAX-ACCESS not-accessible 2565 STATUS deprecated 2566 DESCRIPTION 2567 "Entry containing information about the 2568 connection with a BGP peer." 2569 INDEX { bgpPeerRemoteAddr } 2570 ::= { bgpPeerTable 1 } 2572 BgpPeerEntry ::= SEQUENCE { 2573 bgpPeerIdentifier 2574 IpAddress, 2575 bgpPeerState 2576 INTEGER, 2577 bgpPeerAdminStatus 2578 INTEGER, 2579 bgpPeerNegotiatedVersion 2580 Integer32, 2581 bgpPeerLocalAddr 2582 IpAddress, 2583 bgpPeerLocalPort 2584 Integer32, 2585 bgpPeerRemoteAddr 2586 IpAddress, 2587 bgpPeerRemotePort 2588 Integer32, 2589 bgpPeerRemoteAs 2590 Integer32, 2591 bgpPeerInUpdates 2592 Counter32, 2593 bgpPeerOutUpdates 2594 Counter32, 2595 bgpPeerInTotalMessages 2596 Counter32, 2597 bgpPeerOutTotalMessages 2598 Counter32, 2599 bgpPeerLastError 2600 OCTET STRING, 2601 bgpPeerFsmEstablishedTransitions 2602 Counter32, 2603 bgpPeerFsmEstablishedTime 2604 Gauge32, 2605 bgpPeerConnectRetryInterval 2606 Integer32, 2607 bgpPeerHoldTime 2608 Integer32, 2609 bgpPeerKeepAlive 2610 Integer32, 2611 bgpPeerHoldTimeConfigured 2612 Integer32, 2613 bgpPeerKeepAliveConfigured 2614 Integer32, 2615 bgpPeerMinASOriginationInterval 2616 Integer32, 2617 bgpPeerMinRouteAdvertisementInterval 2618 Integer32, 2619 bgpPeerInUpdateElapsedTime 2620 Gauge32 2621 } 2623 bgpPeerIdentifier OBJECT-TYPE 2624 SYNTAX IpAddress 2625 MAX-ACCESS read-only 2626 STATUS deprecated 2627 DESCRIPTION 2628 "The BGP Identifier of this entry's BGP peer. 2629 This entry MUST be 0.0.0.0 unless the 2630 bgpPeerState is in the openconfirm or the 2631 established state. 2633 This object has been replaced with 2634 bgpPeerAfIdentifier." 2635 REFERENCE 2636 "RFC 4271, Section 4.2, 'BGP Identifier'." 2637 ::= { bgpPeerEntry 1 } 2639 bgpPeerState OBJECT-TYPE 2640 SYNTAX INTEGER { 2641 idle(1), 2642 connect(2), 2643 active(3), 2644 opensent(4), 2645 openconfirm(5), 2646 established(6) 2647 } 2648 MAX-ACCESS read-only 2649 STATUS deprecated 2650 DESCRIPTION 2651 "The BGP peer connection state. 2653 This object has been replaced with 2654 bgpPeerAfPeerState." 2655 REFERENCE 2656 "RFC 4271, Section 8.2.2." 2657 ::= { bgpPeerEntry 2 } 2659 bgpPeerAdminStatus OBJECT-TYPE 2660 SYNTAX INTEGER { 2661 stop(1), 2662 start(2) 2663 } 2664 MAX-ACCESS read-write 2665 STATUS deprecated 2666 DESCRIPTION 2667 "The desired state of the BGP connection. 2668 A transition from 'stop' to 'start' will cause 2669 the BGP Manual Start Event to be generated. 2670 A transition from 'start' to 'stop' will cause 2671 the BGP Manual Stop Event to be generated. 2672 This parameter can be used to restart BGP peer 2673 connections. Care should be used in providing 2674 write access to this object without adequate 2675 authentication. 2677 This object has been replaced with 2678 bgpPeerAfAdminStatus." 2679 REFERENCE 2680 "RFC 4271, Section 8.1.2." 2681 ::= { bgpPeerEntry 3 } 2683 bgpPeerNegotiatedVersion OBJECT-TYPE 2684 SYNTAX Integer32 2685 MAX-ACCESS read-only 2686 STATUS deprecated 2687 DESCRIPTION 2688 "The negotiated version of BGP running between 2689 the two peers. 2691 This entry MUST be zero (0) unless the 2692 bgpPeerState is in the openconfirm or the 2693 established state. 2695 Note that legal values for this object are 2696 between 0 and 255. 2698 This object has been replaced with 2699 bgpPeerAfNegotiatedVersion." 2700 REFERENCE 2701 "RFC 4271, Section 4.2. 2702 RFC 4271, Section 7." 2703 ::= { bgpPeerEntry 4 } 2705 bgpPeerLocalAddr OBJECT-TYPE 2706 SYNTAX IpAddress 2707 MAX-ACCESS read-only 2708 STATUS deprecated 2709 DESCRIPTION 2710 "The local IP address of this entry's BGP 2711 connection. 2713 This object has been replaced with 2714 bgpPeerAfLocalAddrType and bgpPeerAfLocalAddr." 2715 ::= { bgpPeerEntry 5 } 2717 bgpPeerLocalPort OBJECT-TYPE 2718 SYNTAX Integer32 (0..65535) 2719 MAX-ACCESS read-only 2720 STATUS deprecated 2721 DESCRIPTION 2722 "The local port for the TCP connection between 2723 the BGP peers. 2725 This object has been replaced with 2726 bgpPeerAfLocalPort." 2727 ::= { bgpPeerEntry 6 } 2729 bgpPeerRemoteAddr OBJECT-TYPE 2730 SYNTAX IpAddress 2731 MAX-ACCESS read-only 2732 STATUS deprecated 2733 DESCRIPTION 2734 "The remote IP address of this entry's BGP 2735 peer. 2737 This object has been replaced with 2738 bgpPeerAfRemoteAddrType and bgpPeerAfRemoteAddr." 2739 ::= { bgpPeerEntry 7 } 2741 bgpPeerRemotePort OBJECT-TYPE 2742 SYNTAX Integer32 (0..65535) 2743 MAX-ACCESS read-only 2744 STATUS deprecated 2745 DESCRIPTION 2746 "The remote port for the TCP connection 2747 between the BGP peers. Note that the 2748 objects bgpPeerLocalAddr, 2749 bgpPeerLocalPort, bgpPeerRemoteAddr, and 2750 bgpPeerRemotePort provide the appropriate 2751 reference to the standard MIB TCP 2752 connection table. 2754 This object has been replaced with 2755 bgpPeerAfRemotePort." 2756 ::= { bgpPeerEntry 8 } 2758 bgpPeerRemoteAs OBJECT-TYPE 2759 SYNTAX Integer32 (0..65535) 2760 MAX-ACCESS read-only 2761 STATUS deprecated 2762 DESCRIPTION 2763 "The remote autonomous system number received in 2764 the BGP OPEN message. 2766 This object has been replaced with 2767 bgpPeerAfRemoteAs." 2768 REFERENCE 2769 "RFC 4271, Section 4.2." 2770 ::= { bgpPeerEntry 9 } 2772 bgpPeerInUpdates OBJECT-TYPE 2773 SYNTAX Counter32 2774 MAX-ACCESS read-only 2775 STATUS deprecated 2776 DESCRIPTION 2777 "The number of BGP UPDATE messages 2778 received on this connection. 2780 This object has been replaced with 2781 bgpPeerAfInUpdates." 2782 REFERENCE 2783 "RFC 4271, Section 4.3." 2784 ::= { bgpPeerEntry 10 } 2786 bgpPeerOutUpdates OBJECT-TYPE 2787 SYNTAX Counter32 2788 MAX-ACCESS read-only 2789 STATUS deprecated 2790 DESCRIPTION 2791 "The number of BGP UPDATE messages 2792 transmitted on this connection. 2794 This object has been replaced with 2795 bgpPeerAfOutUpdates." 2796 REFERENCE 2797 "RFC 4271, Section 4.3." 2798 ::= { bgpPeerEntry 11 } 2800 bgpPeerInTotalMessages OBJECT-TYPE 2801 SYNTAX Counter32 2802 MAX-ACCESS read-only 2803 STATUS deprecated 2804 DESCRIPTION 2805 "The total number of messages received 2806 from the remote peer on this connection. 2808 This object has been replaced with 2809 bgpPeerAfInTotalMessages." 2811 REFERENCE 2812 "RFC 4271, Section 4." 2813 ::= { bgpPeerEntry 12 } 2815 bgpPeerOutTotalMessages OBJECT-TYPE 2816 SYNTAX Counter32 2817 MAX-ACCESS read-only 2818 STATUS deprecated 2819 DESCRIPTION 2820 "The total number of messages transmitted to 2821 the remote peer on this connection. 2823 This object has been replaced with 2824 bgpPeerAfOutTotalMessages." 2825 REFERENCE 2826 "RFC 4271, Section 4." 2827 ::= { bgpPeerEntry 13 } 2829 bgpPeerLastError OBJECT-TYPE 2830 SYNTAX OCTET STRING (SIZE (2)) 2831 MAX-ACCESS read-only 2832 STATUS deprecated 2833 DESCRIPTION 2834 "The last error code and subcode seen by this 2835 peer on this connection. If no error has 2836 occurred, this field is zero. Otherwise, the 2837 first byte of this two byte OCTET STRING 2838 contains the error code, and the second byte 2839 contains the subcode. 2841 This object has been replaced by 2842 bgpPeerAfLastErrorCodeRecieved and 2843 bgpPeerAfLastErrorSubCodeReceived. Further, this 2844 data has been supplemented by additional objects 2845 in the bgpPeerAfErrorsTable." 2846 REFERENCE 2847 "RFC 4271, Section 4.5." 2848 ::= { bgpPeerEntry 14 } 2850 bgpPeerFsmEstablishedTransitions OBJECT-TYPE 2851 SYNTAX Counter32 2852 MAX-ACCESS read-only 2853 STATUS deprecated 2854 DESCRIPTION 2855 "The total number of times the BGP FSM 2856 transitioned into the established state 2857 for this peer. 2859 This object has been replaced by 2860 bgpPeerAfFsmEstablishedTransitions." 2861 REFERENCE 2862 "RFC 4271, Section 8." 2863 ::= { bgpPeerEntry 15 } 2865 bgpPeerFsmEstablishedTime OBJECT-TYPE 2866 SYNTAX Gauge32 2867 UNITS "seconds" 2868 MAX-ACCESS read-only 2869 STATUS deprecated 2870 DESCRIPTION 2871 "This timer indicates how long (in 2872 seconds) this peer has been in the 2873 established state or how long 2874 since this peer was last in the 2875 established state. It is set to zero when 2876 a new peer is configured or when the router is 2877 booted. 2879 This object has been replaced by 2880 bgpPeerAfFsmEstablishedTime." 2881 REFERENCE 2882 "RFC 4271, Section 8." 2883 ::= { bgpPeerEntry 16 } 2885 bgpPeerConnectRetryInterval OBJECT-TYPE 2886 SYNTAX Integer32 (1..65535) 2887 UNITS "seconds" 2888 MAX-ACCESS read-write 2889 STATUS deprecated 2890 DESCRIPTION 2891 "Time interval (in seconds) for the 2892 ConnectRetry timer. The suggested value 2893 for this timer is 120 seconds. 2895 This object has been replaced by 2896 bgpPeerAfConnectRetryInterval." 2897 REFERENCE 2898 "RFC 4271, Section 8.2.2. This is the value used 2899 to initialize the 'ConnectRetryTimer'." 2900 ::= { bgpPeerEntry 17 } 2902 bgpPeerHoldTime OBJECT-TYPE 2903 SYNTAX Integer32 ( 0 | 3..65535 ) 2904 UNITS "seconds" 2905 MAX-ACCESS read-only 2906 STATUS deprecated 2907 DESCRIPTION 2908 "Time interval (in seconds) for the Hold 2909 Timer established with the peer. The 2910 value of this object is calculated by this 2911 BGP speaker, using the smaller of the 2912 values in bgpPeerHoldTimeConfigured and the 2913 Hold Time received in the OPEN message. 2915 This value must be at least three seconds 2916 if it is not zero (0). 2918 If the Hold Timer has not been established 2919 with the peer this object MUST have a value 2920 of zero (0). 2922 If the bgpPeerHoldTimeConfigured object has 2923 a value of (0), then this object MUST have a 2924 value of (0). 2926 This object has been replaced by 2927 bgpPeerAfHoldTime." 2928 REFERENCE 2929 "RFC 4271, Section 4.2." 2930 ::= { bgpPeerEntry 18 } 2932 bgpPeerKeepAlive OBJECT-TYPE 2933 SYNTAX Integer32 ( 0 | 1..21845 ) 2934 UNITS "seconds" 2935 MAX-ACCESS read-only 2936 STATUS deprecated 2937 DESCRIPTION 2938 "Time interval (in seconds) for the KeepAlive 2939 timer established with the peer. The value 2940 of this object is calculated by this BGP 2941 speaker such that, when compared with 2942 bgpPeerHoldTime, it has the same proportion 2943 that bgpPeerKeepAliveConfigured has, 2944 compared with bgpPeerHoldTimeConfigured. 2946 If the KeepAlive timer has not been established 2947 with the peer, this object MUST have a value 2948 of zero (0). 2950 If the of bgpPeerKeepAliveConfigured object 2951 has a value of (0), then this object MUST have 2952 a value of (0). 2954 This object has been replaced by 2955 bgpPeerAfKeepAlive." 2956 REFERENCE 2957 "RFC 4271, Section 4.4." 2958 ::= { bgpPeerEntry 19 } 2960 bgpPeerHoldTimeConfigured OBJECT-TYPE 2961 SYNTAX Integer32 ( 0 | 3..65535 ) 2962 UNITS "seconds" 2963 MAX-ACCESS read-write 2964 STATUS deprecated 2965 DESCRIPTION 2966 "Time interval (in seconds) for the Hold Time 2967 configured for this BGP speaker with this 2968 peer. This value is placed in an OPEN 2969 message sent to this peer by this BGP 2970 speaker, and is compared with the Hold 2971 Time field in an OPEN message received 2972 from the peer when determining the Hold 2973 Time (bgpPeerHoldTime) with the peer. 2974 This value must not be less than three 2975 seconds if it is not zero (0). If it is 2976 zero (0), the Hold Time is NOT to be 2977 established with the peer. The suggested 2978 value for this timer is 90 seconds. 2980 This object has been replaced by 2981 bgpPeerAfHoldTimeConfigured." 2982 REFERENCE 2983 "RFC 4271, Section 4.2. 2984 RFC 4271, Section 10." 2985 ::= { bgpPeerEntry 20 } 2987 bgpPeerKeepAliveConfigured OBJECT-TYPE 2988 SYNTAX Integer32 ( 0 | 1..21845 ) 2989 UNITS "seconds" 2990 MAX-ACCESS read-write 2991 STATUS deprecated 2992 DESCRIPTION 2993 "Time interval (in seconds) for the 2994 KeepAlive timer configured for this BGP 2995 speaker with this peer. The value of this 2996 object will only determine the 2997 KEEPALIVE messages' frequency relative to 2998 the value specified in 2999 bgpPeerHoldTimeConfigured; the actual 3000 time interval for the KEEPALIVE messages is 3001 indicated by bgpPeerKeepAlive. A 3002 reasonable maximum value for this timer 3003 would be one third of that of 3004 bgpPeerHoldTimeConfigured. 3005 If the value of this object is zero (0), 3006 no periodic KEEPALIVE messages are sent 3007 to the peer after the BGP connection has 3008 been established. The suggested value for 3009 this timer is 30 seconds. 3011 This object has been replaced by 3012 bgpPeerAfKeepAliveConfigured." 3013 REFERENCE 3014 "RFC 4271, Section 4.4. 3015 RFC 4271, Section 10." 3016 ::= { bgpPeerEntry 21 } 3018 bgpPeerMinASOriginationInterval OBJECT-TYPE 3019 SYNTAX Integer32 (1..65535) 3020 UNITS "seconds" 3021 MAX-ACCESS read-write 3022 STATUS deprecated 3023 DESCRIPTION 3024 "Time interval (in seconds) for the 3025 MinASOriginationInterval timer. 3026 The suggested value for this timer is 15 3027 seconds. 3029 This object has been replaced by 3030 bgpPeerAfMinASOrigInterval." 3031 REFERENCE 3032 "RFC 4271, Section 9.2.1.2. 3033 RFC 4271, Section 10." 3034 ::= { bgpPeerEntry 22 } 3036 bgpPeerMinRouteAdvertisementInterval OBJECT-TYPE 3037 SYNTAX Integer32 (1..65535) 3038 UNITS "seconds" 3039 MAX-ACCESS read-write 3040 STATUS deprecated 3041 DESCRIPTION 3042 "Time interval (in seconds) for the 3043 MinRouteAdvertisementInterval timer. 3044 The suggested value for this timer is 30 3045 seconds for EBGP connections and 5 3046 seconds for IBGP connections. 3048 This object has been replaced by 3049 bgpPeerAfMinRouteAdverInterval." 3050 REFERENCE 3051 "RFC 4271, Section 9.2.1.1. 3052 RFC 4271, Section 10." 3053 ::= { bgpPeerEntry 23 } 3055 bgpPeerInUpdateElapsedTime OBJECT-TYPE 3056 SYNTAX Gauge32 3057 UNITS "seconds" 3058 MAX-ACCESS read-only 3059 STATUS deprecated 3060 DESCRIPTION 3061 "Elapsed time (in seconds) since the last BGP 3062 UPDATE message was received from the peer. 3063 Each time bgpPeerInUpdates is incremented, 3064 the value of this object is set to zero (0). 3066 This object has been replaced by 3067 bgpPeerAfInUpdatesElapsedTime." 3068 REFERENCE 3069 "RFC 4271, Section 4.3. 3070 RFC 4271, Section 8.2.2, Established state." 3071 ::= { bgpPeerEntry 24 } 3073 -- BGP Received Path Attribute Table. This table contains 3074 -- one entry per path to a network, and path attributes 3075 -- received from all peers running BGP version 3 or less. 3076 -- This table is obsolete, having been replaced in 3077 -- functionality by the bgp4PathAttrTable. 3079 bgpRcvdPathAttrTable OBJECT-TYPE 3080 SYNTAX SEQUENCE OF BgpPathAttrEntry 3081 MAX-ACCESS not-accessible 3082 STATUS obsolete 3083 DESCRIPTION 3084 "The BGP Received Path Attribute Table 3085 contains information about paths to 3086 destination networks, received from all 3087 peers running BGP version 3 or less." 3088 ::= { bgp 5 } 3090 bgpPathAttrEntry OBJECT-TYPE 3091 SYNTAX BgpPathAttrEntry 3092 MAX-ACCESS not-accessible 3093 STATUS obsolete 3094 DESCRIPTION 3095 "Information about a path to a network." 3096 INDEX { bgpPathAttrDestNetwork, 3097 bgpPathAttrPeer } 3099 ::= { bgpRcvdPathAttrTable 1 } 3101 BgpPathAttrEntry ::= SEQUENCE { 3102 bgpPathAttrPeer 3103 IpAddress, 3104 bgpPathAttrDestNetwork 3105 IpAddress, 3106 bgpPathAttrOrigin 3107 INTEGER, 3108 bgpPathAttrASPath 3109 OCTET STRING, 3110 bgpPathAttrNextHop 3111 IpAddress, 3112 bgpPathAttrInterASMetric 3113 Integer32 3114 } 3116 bgpPathAttrPeer OBJECT-TYPE 3117 SYNTAX IpAddress 3118 MAX-ACCESS read-only 3119 STATUS obsolete 3120 DESCRIPTION 3121 "The IP address of the peer where the path 3122 information was learned." 3123 ::= { bgpPathAttrEntry 1 } 3125 bgpPathAttrDestNetwork OBJECT-TYPE 3126 SYNTAX IpAddress 3127 MAX-ACCESS read-only 3128 STATUS obsolete 3129 DESCRIPTION 3130 "The address of the destination network." 3131 REFERENCE 3132 "RFC 1267, Section 4.3." 3133 ::= { bgpPathAttrEntry 2 } 3135 bgpPathAttrOrigin OBJECT-TYPE 3136 SYNTAX INTEGER { 3137 igp(1),-- networks are interior 3138 egp(2),-- networks learned via the 3139 -- EGP protocol 3140 incomplete(3) -- networks that 3141 -- are learned by some other 3142 -- means 3143 } 3144 MAX-ACCESS read-only 3145 STATUS obsolete 3146 DESCRIPTION 3147 "The ultimate origin of the path information." 3148 REFERENCE 3149 "RFC 1267, Section 4.3. 3150 RFC 1267, Section 5." 3151 ::= { bgpPathAttrEntry 3 } 3153 bgpPathAttrASPath OBJECT-TYPE 3154 SYNTAX OCTET STRING (SIZE (2..255)) 3155 MAX-ACCESS read-only 3156 STATUS obsolete 3157 DESCRIPTION 3158 "The set of ASes that must be traversed to reach 3159 the network. This object is probably best 3160 represented as SEQUENCE OF INTEGER. For SMI 3161 compatibility, though, it is represented as 3162 OCTET STRING. Each AS is represented as a pair 3163 of octets according to the following algorithm: 3165 first-byte-of-pair = ASNumber / 256; 3166 second-byte-of-pair = ASNumber & 255;" 3167 REFERENCE 3168 "RFC 1267, Section 4.3. 3169 RFC 1267, Section 5." 3170 ::= { bgpPathAttrEntry 4 } 3172 bgpPathAttrNextHop OBJECT-TYPE 3173 SYNTAX IpAddress 3174 MAX-ACCESS read-only 3175 STATUS obsolete 3176 DESCRIPTION 3177 "The address of the border router that should 3178 be used for the destination network." 3179 REFERENCE 3180 "RFC 1267, Section 4.3. 3181 RFC 1267, Section 5." 3182 ::= { bgpPathAttrEntry 5 } 3184 bgpPathAttrInterASMetric OBJECT-TYPE 3185 SYNTAX Integer32 3186 MAX-ACCESS read-only 3187 STATUS obsolete 3188 DESCRIPTION 3189 "The optional inter-AS metric. If this 3190 attribute has not been provided for this route, 3191 the value for this object is 0." 3192 REFERENCE 3193 "RFC 1267, Section 4.3. 3194 RFC 1267, Section 5." 3196 ::= { bgpPathAttrEntry 6 } 3198 -- BGP-4 Received Path Attribute Table. This table 3199 -- contains one entry per path to a network, and path 3200 -- attributes received from all peers running BGP-4. 3202 bgp4PathAttrTable OBJECT-TYPE 3203 SYNTAX SEQUENCE OF Bgp4PathAttrEntry 3204 MAX-ACCESS not-accessible 3205 STATUS deprecated 3206 DESCRIPTION 3207 "The BGP-4 Received Path Attribute Table 3208 contains information about paths to 3209 destination networks, received from all 3210 BGP4 peers. 3212 This table has been replaced by the functionality 3213 provided under the bgpRib OID." 3214 ::= { bgp 6 } 3216 bgp4PathAttrEntry OBJECT-TYPE 3217 SYNTAX Bgp4PathAttrEntry 3218 MAX-ACCESS not-accessible 3219 STATUS deprecated 3220 DESCRIPTION 3221 "Information about a path to a network." 3222 INDEX { bgp4PathAttrIpAddrPrefix, 3223 bgp4PathAttrIpAddrPrefixLen, 3224 bgp4PathAttrPeer } 3225 ::= { bgp4PathAttrTable 1 } 3227 Bgp4PathAttrEntry ::= SEQUENCE { 3228 bgp4PathAttrPeer 3229 IpAddress, 3230 bgp4PathAttrIpAddrPrefixLen 3231 Integer32, 3232 bgp4PathAttrIpAddrPrefix 3233 IpAddress, 3234 bgp4PathAttrOrigin 3235 INTEGER, 3236 bgp4PathAttrASPathSegment 3237 OCTET STRING, 3238 bgp4PathAttrNextHop 3239 IpAddress, 3240 bgp4PathAttrMultiExitDisc 3241 Integer32, 3242 bgp4PathAttrLocalPref 3243 Integer32, 3245 bgp4PathAttrAtomicAggregate 3246 INTEGER, 3247 bgp4PathAttrAggregatorAS 3248 Integer32, 3249 bgp4PathAttrAggregatorAddr 3250 IpAddress, 3251 bgp4PathAttrCalcLocalPref 3252 Integer32, 3253 bgp4PathAttrBest 3254 INTEGER, 3255 bgp4PathAttrUnknown 3256 OCTET STRING 3257 } 3259 bgp4PathAttrPeer OBJECT-TYPE 3260 SYNTAX IpAddress 3261 MAX-ACCESS read-only 3262 STATUS deprecated 3263 DESCRIPTION 3264 "The IP address of the peer where the path 3265 information was learned. 3267 This object has been replaced by the following 3268 tuples of objects: bgpPeerAfInstance, 3269 bgpPeerAfLocalAddrType, bgpPeerAfLocalAddr, 3270 bgpPeerAfRemoteAddrType, bgpPeerAfRemoteAddr." 3271 ::= { bgp4PathAttrEntry 1 } 3273 bgp4PathAttrIpAddrPrefixLen OBJECT-TYPE 3274 SYNTAX Integer32 (0..32) 3275 MAX-ACCESS read-only 3276 STATUS deprecated 3277 DESCRIPTION 3278 "Length in bits of the IP address prefix in 3279 the Network Layer Reachability 3280 Information field. 3282 This object has been replaced by bgpNlriPrefixLen." 3283 ::= { bgp4PathAttrEntry 2 } 3285 bgp4PathAttrIpAddrPrefix OBJECT-TYPE 3286 SYNTAX IpAddress 3287 MAX-ACCESS read-only 3288 STATUS deprecated 3289 DESCRIPTION 3290 "An IP address prefix in the Network Layer 3291 Reachability Information field. This object 3292 is an IP address containing the prefix with 3293 length specified by 3294 bgp4PathAttrIpAddrPrefixLen. 3295 Any bits beyond the length specified by 3296 bgp4PathAttrIpAddrPrefixLen are zeroed. 3298 This object has been replaced by bgpNlriPrefixType 3299 and bgpNlriPrefix." 3300 REFERENCE 3301 "RFC 4271, Section 4.3." 3302 ::= { bgp4PathAttrEntry 3 } 3304 bgp4PathAttrOrigin OBJECT-TYPE 3305 SYNTAX INTEGER { 3306 igp(1),-- networks are interior 3307 egp(2),-- networks learned via the 3308 -- EGP protocol 3309 incomplete(3) -- networks that 3310 -- are learned by some other 3311 -- means 3312 } 3313 MAX-ACCESS read-only 3314 STATUS deprecated 3315 DESCRIPTION 3316 "The ultimate origin of the path 3317 information. 3319 This object has been replaced by bgpAfPathAttrOrigin." 3320 REFERENCE 3321 "RFC 4271, Section 4.3. 3322 RFC 4271, Section 5.1.1." 3323 ::= { bgp4PathAttrEntry 4 } 3325 bgp4PathAttrASPathSegment OBJECT-TYPE 3326 SYNTAX OCTET STRING (SIZE (2..255)) 3327 MAX-ACCESS read-only 3328 STATUS deprecated 3329 DESCRIPTION 3330 "The sequence of AS path segments. Each AS 3331 path segment is represented by a triple 3332 . 3334 The type is a 1-octet field that has two 3335 possible values: 3336 1 AS_SET: unordered set of ASes that a 3337 route in the UPDATE message 3338 has traversed 3340 2 AS_SEQUENCE: ordered set of ASes that 3341 a route in the UPDATE message 3342 has traversed. 3344 The length is a 1-octet field containing the 3345 number of ASes in the value field. 3347 The value field contains one or more AS 3348 numbers. Each AS is represented in the octet 3349 string as a pair of octets according to the 3350 following algorithm: 3352 first-byte-of-pair = ASNumber / 256; 3353 second-byte-of-pair = ASNumber & 255; 3355 Known Issues: 3356 o BGP Confederations will result in 3357 a type of either 3 or 4. 3358 o An AS Path may be longer than 255 octets. 3359 This may result in this object containing 3360 a truncated AS Path. 3362 This object has been replaced by the bgpAsPathTable 3363 and supplemented by a human readable object, 3364 bgpAsPathString." 3365 REFERENCE 3366 "RFC 4271, Section 4.3. 3367 RFC 4271, Section 5.1.2." 3368 ::= { bgp4PathAttrEntry 5 } 3370 bgp4PathAttrNextHop OBJECT-TYPE 3371 SYNTAX IpAddress 3372 MAX-ACCESS read-only 3373 STATUS deprecated 3374 DESCRIPTION 3375 "The address of the border router that 3376 should be used for the destination 3377 network. This address is the NEXT_HOP 3378 address received in the UPDATE packet. 3380 This object has been replaced by 3381 bgpAfPathAttrNextHop." 3382 REFERENCE 3383 "RFC 4271, Section 4.3. 3384 RFC 4271, Section 5.1.3." 3385 ::= { bgp4PathAttrEntry 6 } 3387 bgp4PathAttrMultiExitDisc OBJECT-TYPE 3388 SYNTAX Integer32 (-1..2147483647) 3389 MAX-ACCESS read-only 3390 STATUS deprecated 3391 DESCRIPTION 3392 "This metric is used to discriminate 3393 between multiple exit points to an 3394 adjacent autonomous system. A value of -1 3395 indicates the absence of this attribute. 3397 Known Issues: 3398 o The BGP-4 specification uses an 3399 unsigned 32 bit number. Thus, this 3400 object cannot represent the full 3401 range of the protocol. 3403 This object has been replaced by bgpAfPathAttrMed 3404 and bgpAfPathAttrMedPresent." 3405 REFERENCE 3406 "RFC 4271, Section 4.3. 3407 RFC 4271, Section 5.1.4." 3408 ::= { bgp4PathAttrEntry 7 } 3410 bgp4PathAttrLocalPref OBJECT-TYPE 3411 SYNTAX Integer32 (-1..2147483647) 3412 MAX-ACCESS read-only 3413 STATUS deprecated 3414 DESCRIPTION 3415 "The originating BGP4 speaker's degree of 3416 preference for an advertised route. A 3417 value of -1 indicates the absence of this 3418 attribute. 3420 Known Issues: 3421 o The BGP-4 specification uses an 3422 unsigned 32 bit number and thus this 3423 object cannot represent the full 3424 range of the protocol. 3426 This object has been replaced by bgpAfPathAttrLocalPref." 3427 REFERENCE 3428 "RFC 4271, Section 4.3. 3429 RFC 4271, Section 5.1.5." 3430 ::= { bgp4PathAttrEntry 8 } 3432 bgp4PathAttrAtomicAggregate OBJECT-TYPE 3433 SYNTAX INTEGER { 3434 lessSpecificRouteNotSelected(1), 3435 -- Typo corrected from RFC 1657 3436 lessSpecificRouteSelected(2) 3438 } 3439 MAX-ACCESS read-only 3440 STATUS deprecated 3441 DESCRIPTION 3442 "If the ATOMIC_AGGREGATE attribute is present 3443 in the Path Attributes then this object MUST 3444 have a value of 'lessSpecificRouteNotSelected'. 3446 If the ATOMIC_AGGREGATE attribute is missing 3447 in the Path Attributes then this object MUST 3448 have a value of 'lessSpecificRouteSelected'. 3450 Note that ATOMIC_AGGREGATE is now a primarily 3451 informational attribute. 3453 This object has been replaced by 3454 bgpAfPathAttrAtomicAggregate." 3455 REFERENCE 3456 "RFC 4271, Sections 5.1.6 and 9.1.4." 3457 ::= { bgp4PathAttrEntry 9 } 3459 bgp4PathAttrAggregatorAS OBJECT-TYPE 3460 SYNTAX Integer32 (0..65535) 3461 MAX-ACCESS read-only 3462 STATUS deprecated 3463 DESCRIPTION 3464 "The AS number of the last BGP4 speaker that 3465 performed route aggregation. A value of 3466 zero (0) indicates the absence of this 3467 attribute. 3469 Note that propagation of AS of zero is illegal 3470 in the Internet. 3472 This object has been replaced by 3473 bgpAfPathAttrAggregatorAS." 3474 REFERENCE 3475 "RFC 4271, Section 5.1.7. 3476 RFC 4271, Section 9.2.2.2." 3477 ::= { bgp4PathAttrEntry 10 } 3479 bgp4PathAttrAggregatorAddr OBJECT-TYPE 3480 SYNTAX IpAddress 3481 MAX-ACCESS read-only 3482 STATUS deprecated 3483 DESCRIPTION 3484 "The IP address of the last BGP4 speaker 3485 that performed route aggregation. A 3486 value of 0.0.0.0 indicates the absence 3487 of this attribute. 3489 This object has been replaced by 3490 bgpAfPathAttrAggregatorAddr." 3491 REFERENCE 3492 "RFC 4271, Section 5.1.7. 3493 RFC 4271, Section 9.2.2.2." 3494 ::= { bgp4PathAttrEntry 11 } 3496 bgp4PathAttrCalcLocalPref OBJECT-TYPE 3497 SYNTAX Integer32 (-1..2147483647) 3498 MAX-ACCESS read-only 3499 STATUS deprecated 3500 DESCRIPTION 3501 "The degree of preference calculated by the 3502 receiving BGP4 speaker for an advertised 3503 route. A value of -1 indicates the 3504 absence of this attribute. 3506 Known Issues: 3507 o The BGP-4 specification uses an 3508 unsigned 32 bit number and thus this 3509 object cannot represent the full 3510 range of the protocol. 3512 This object has been replaced by 3513 bgpNlriCalcLocalPref." 3514 REFERENCE 3515 "RFC 4271, Section 9.1.1." 3516 ::= { bgp4PathAttrEntry 12 } 3518 bgp4PathAttrBest OBJECT-TYPE 3519 SYNTAX INTEGER { 3520 false(1),-- not chosen as best route 3521 true(2) -- chosen as best route 3522 } 3523 MAX-ACCESS read-only 3524 STATUS deprecated 3525 DESCRIPTION 3526 "An indication of whether this route 3527 was chosen as the best BGP4 route for this 3528 destination. 3530 This object has been replaced by bgpNlriBest." 3531 REFERENCE 3532 "RFC 4271, Section 9.1.2." 3533 ::= { bgp4PathAttrEntry 13 } 3535 bgp4PathAttrUnknown OBJECT-TYPE 3536 SYNTAX OCTET STRING (SIZE(0..255)) 3537 MAX-ACCESS read-only 3538 STATUS deprecated 3539 DESCRIPTION 3540 "One or more path attributes not understood by 3541 this BGP4 speaker. 3543 Path attributes are recorded in the Update Path 3544 attribute format of type, length, value. 3546 Size zero (0) indicates the absence of such 3547 attributes. 3549 Octets beyond the maximum size, if any, are not 3550 recorded by this object. 3552 Known Issues: 3553 o Attributes understood by this speaker, but not 3554 represented in this MIB, are unavailable to 3555 the agent. 3557 This object has been replaced by the contents of 3558 bgpAfPathAttrUnknownTable." 3559 REFERENCE 3560 "RFC 4271, Section 5." 3561 ::= { bgp4PathAttrEntry 14 } 3563 -- Traps. 3564 -- Note that in RFC 1657, bgpTraps was incorrectly 3565 -- assigned a value of { bgp 7 } and each of the 3566 -- traps had the bgpPeerRemoteAddr object inappropriately 3567 -- removed from their OBJECTS clause. The following 3568 -- definitions restore the semantics of the traps as 3569 -- they were initially defined in RFC 1269. 3571 bgpEstablishedNotification NOTIFICATION-TYPE 3572 OBJECTS { bgpPeerRemoteAddr, 3573 bgpPeerLastError, 3574 bgpPeerState } 3575 STATUS deprecated 3576 DESCRIPTION 3577 "The bgpEstablishedNotification event is generated 3578 when the BGP FSM enters the established state. 3580 This Notification replaces the bgpEstablished 3581 Notification and has been replaced by 3582 bgpAfEstablishedNotification." 3583 ::= { bgpNotification 1 } 3585 bgpBackwardTransNotification NOTIFICATION-TYPE 3586 OBJECTS { bgpPeerRemoteAddr, 3587 bgpPeerLastError, 3588 bgpPeerState } 3589 STATUS deprecated 3590 DESCRIPTION 3591 "The bgpBackwardTransNotification event is 3592 generated when the BGP FSM moves from a higher 3593 numbered state to a lower numbered state. 3595 This Notification replaces the 3596 bgpBackwardsTransition Notification and has 3597 been replaced by bgpAfBackwardsNotification." 3598 ::= { bgpNotification 2 } 3600 -- { bgp 7 } is deprecated. Do not allocate new objects or 3601 -- notifications underneath this branch. 3603 bgpTraps OBJECT IDENTIFIER ::= { bgp 7 } -- deprecated 3605 bgpEstablished NOTIFICATION-TYPE 3606 OBJECTS { bgpPeerLastError, 3607 bgpPeerState } 3608 STATUS deprecated 3609 DESCRIPTION 3610 "The bgpEstablished event is generated when 3611 the BGP FSM enters the established state. 3613 This Notification has been replaced by the 3614 bgpEstablishedNotification Notification." 3615 ::= { bgpTraps 1 } 3617 bgpBackwardTransition NOTIFICATION-TYPE 3618 OBJECTS { bgpPeerLastError, 3619 bgpPeerState } 3620 STATUS deprecated 3621 DESCRIPTION 3622 "The bgpBackwardTransition event is generated 3623 when the BGP FSM moves from a higher numbered 3624 state to a lower numbered state. 3626 This Notification has been replaced by the 3627 bgpBackwardTransNotification Notification." 3628 ::= { bgpTraps 2 } 3630 -- Obsolete Compliance statements 3632 bgp4MIBCompliance MODULE-COMPLIANCE 3633 STATUS obsolete 3634 DESCRIPTION 3635 "The compliance statement for entities which 3636 implement the BGP4 mib. 3638 This compliance statement is obsoleted by 3639 bgpAfMIBCompliance." 3640 MODULE -- this module 3641 MANDATORY-GROUPS { bgp4MIBGlobalsGroup, 3642 bgp4MIBPeerGroup, 3643 bgp4MIBPathAttrGroup } 3644 GROUP bgp4MIBNotificationGroup 3645 DESCRIPTION 3646 "Implementation of BGP Notifications are 3647 completely optional in this MIB." 3648 ::= { bgp4MIBCompliances 1 } 3650 bgp4MIBDeprecatedCompliances MODULE-COMPLIANCE 3651 STATUS obsolete 3652 DESCRIPTION 3653 "The compliance statement documenting deprecated 3654 objects in the BGP4 mib. 3656 This compliance statement is obsoleted 3657 by bgpAfMIBCompliance." 3658 MODULE -- this module 3659 GROUP bgp4MIBTrapGroup 3660 DESCRIPTION 3661 "Group containing TRAP objects that were 3662 improperly converted from SMIv1 in RFC 1657. 3663 The proper semantics have been restored 3664 with the objects in bgp4MIBNotificationGroup." 3665 ::= { bgp4MIBCompliances 2 } 3667 bgp4MIBObsoleteCompliances MODULE-COMPLIANCE 3668 STATUS obsolete 3669 DESCRIPTION 3670 "The compliance statement documenting obsolete 3671 objects in the BGP4 mib." 3672 MODULE -- this module 3673 GROUP bgpRcvdPathAttrGroup 3674 DESCRIPTION 3675 "Group containing objects relevant to BGP-3 3676 and earlier objects." 3677 ::= { bgp4MIBCompliances 3 } 3679 -- Units of conformance 3681 bgp4MIBGlobalsGroup OBJECT-GROUP 3682 OBJECTS { bgpVersion, 3683 bgpLocalAs, 3684 bgpIdentifier } 3685 STATUS obsolete 3686 DESCRIPTION 3687 "A collection of objects providing 3688 information on global BGP state. 3690 This group has been replaced by 3691 bgpAfMIBGlobalsGroup and bgpAfMIBOldGlobalsGroup." 3692 ::= { bgp4MIBGroups 1 } 3694 bgp4MIBPeerGroup OBJECT-GROUP 3695 OBJECTS { bgpPeerIdentifier, 3696 bgpPeerState, 3697 bgpPeerAdminStatus, 3698 bgpPeerNegotiatedVersion, 3699 bgpPeerLocalAddr, 3700 bgpPeerLocalPort, 3701 bgpPeerRemoteAddr, 3702 bgpPeerRemotePort, 3703 bgpPeerRemoteAs, 3704 bgpPeerInUpdates, 3705 bgpPeerOutUpdates, 3706 bgpPeerInTotalMessages, 3707 bgpPeerOutTotalMessages, 3708 bgpPeerLastError, 3709 bgpPeerFsmEstablishedTransitions, 3710 bgpPeerFsmEstablishedTime, 3711 bgpPeerConnectRetryInterval, 3712 bgpPeerHoldTime, 3713 bgpPeerKeepAlive, 3714 bgpPeerHoldTimeConfigured, 3715 bgpPeerKeepAliveConfigured, 3716 bgpPeerMinASOriginationInterval, 3717 bgpPeerMinRouteAdvertisementInterval, 3718 bgpPeerInUpdateElapsedTime } 3719 STATUS deprecated 3720 DESCRIPTION 3721 "A collection of objects for managing BGP peers 3722 from the previous version of this MIB. The 3723 individual objects are deprecated and their support 3724 is OPTIONAL." 3725 ::= { bgp4MIBGroups 2 } 3727 bgpRcvdPathAttrGroup OBJECT-GROUP 3728 OBJECTS { bgpPathAttrPeer, 3729 bgpPathAttrDestNetwork, 3730 bgpPathAttrOrigin, 3731 bgpPathAttrASPath, 3732 bgpPathAttrNextHop, 3733 bgpPathAttrInterASMetric } 3734 STATUS obsolete 3735 DESCRIPTION 3736 "A collection of objects for managing BGP-3 and 3737 earlier path entries. 3739 This conformance group, like BGP-3, is obsolete." 3740 ::= { bgp4MIBGroups 3 } 3742 bgp4MIBPathAttrGroup OBJECT-GROUP 3743 OBJECTS { bgp4PathAttrPeer, 3744 bgp4PathAttrIpAddrPrefixLen, 3745 bgp4PathAttrIpAddrPrefix, 3746 bgp4PathAttrOrigin, 3747 bgp4PathAttrASPathSegment, 3748 bgp4PathAttrNextHop, 3749 bgp4PathAttrMultiExitDisc, 3750 bgp4PathAttrLocalPref, 3751 bgp4PathAttrAtomicAggregate, 3752 bgp4PathAttrAggregatorAS, 3753 bgp4PathAttrAggregatorAddr, 3754 bgp4PathAttrCalcLocalPref, 3755 bgp4PathAttrBest, 3756 bgp4PathAttrUnknown } 3757 STATUS deprecated 3758 DESCRIPTION 3759 "A collection of objects for managing BGP path 3760 entries from the previous version of this MIB. This 3761 individual objects are deprecated and their support 3762 is OPTIONAL." 3763 ::= { bgp4MIBGroups 4 } 3765 bgp4MIBTrapGroup NOTIFICATION-GROUP 3766 NOTIFICATIONS { bgpEstablished, 3767 bgpBackwardTransition } 3768 STATUS deprecated 3769 DESCRIPTION 3770 "A collection of notifications for signaling 3771 changes in BGP peer relationships. 3773 Obsoleted by bgp4MIBNotificationGroup. Support of 3774 the objects in this group is OPTIONAL." 3776 ::= { bgp4MIBGroups 5 } 3778 bgp4MIBNotificationGroup NOTIFICATION-GROUP 3779 NOTIFICATIONS { bgpEstablishedNotification, 3780 bgpBackwardTransNotification } 3781 STATUS deprecated 3782 DESCRIPTION 3783 "A collection of notifications for signaling 3784 changes in BGP peer relationships. 3786 Obsoletes bgp4MIBTrapGroup. Obsoleted by 3787 bgpAfMIBNotificationGroup. Support for objects in 3788 this group is OPTIONAL." 3789 ::= { bgp4MIBGroups 6 } 3791 bgpAfMIBNotificationGroup NOTIFICATION-GROUP 3792 NOTIFICATIONS { bgpAfEstablishedNotification, 3793 bgpAfBackwardTransitionNotification } 3794 STATUS current 3795 DESCRIPTION 3796 "A collection of notifications for signaling 3797 changes in BGP peer relationships. 3799 Obsoletes bgp4MIBNotificationGroup." 3800 ::= { bgp4MIBGroups 7 } 3802 END 3804 8. Security Considerations 3806 This MIB relates to a system providing inter-domain routing. As 3807 such, improper manipulation of the objects represented by this MIB 3808 may result in denial of service to a large number of end-users. 3810 There are a number of management objects defined in this MIB module 3811 with a MAX-ACCESS clause of read-write and/or read-create. Such 3812 objects may be considered sensitive or vulnerable in some network 3813 environments. The support for SET operations in a non-secure 3814 environment without proper protection can have a negative effect on 3815 network operations. These are the tables and objects and their 3816 sensitivity/vulnerability: 3818 bgpPeerAdminStatus - Improper change of bgpPeerAdminStatus, from 3819 start to stop, can cause significant disruption of the 3820 connectivity to those portions of the Internet reached via the 3821 applicable remote BGP peer. 3823 bgpPeerConnectRetryInterval - Improper change of this object can 3824 cause connections to be disrupted for extremely long time periods 3825 when otherwise they would be restored in a relatively short period 3826 of time. 3828 bgpPeerHoldTimeConfigured, bgpPeerKeepAliveConfigured - 3829 Misconfiguration of these objects can make BGP sessions more 3830 fragile and less resilient to denial of service attacks on the 3831 inter-domain routing system. 3833 bgpPeerMinASOriginationInterval, 3834 bgpPeerMinRouteAdvertisementInterval - Misconfiguration of these 3835 objects may adversely affect global Internet convergence of the 3836 routes advertised by this BGP speaker. This may result in long- 3837 lived routing loops and blackholes for the portions of the 3838 Internet that utilize these routes. 3840 Some of the readable objects in this MIB module (i.e., objects with a 3841 MAX-ACCESS other than not-accessible) may be considered sensitive or 3842 vulnerable in some network environments. It is thus important to 3843 control even GET and/or NOTIFY access to these objects and possibly 3844 to even encrypt the values of these objects when sending them over 3845 the network via SNMP. These are the tables and objects and their 3846 sensitivity/vulnerability: 3848 o bgpPeerAfLocalAddrType, bgpPeerAfLocalAddr,bgpPeerAfLocalPort 3849 bgpPeerAfRemoteAddrType, bgpPeerAfRemoteAddr, bgpPeerAfRemotePort, 3850 bgpPeerLocalAddr, bgpPeerLocalPort, bgpPeerRemoteAddr, 3851 bgpPeerRemotePort - A BGP peer's local and remote addresses might 3852 be sensitive for ISPs who want to keep interface addresses on 3853 routers confidential in order to prevent router addresses used for 3854 a denial of service attack or spoofing. Note that other tables 3855 which share elements of these objects as indexes may similarly 3856 expose sensitive information. 3858 o bgpNlriTable, bgpAdjRibsOutTable, bgpAfPathAttrTable, 3859 bgpAsPathTable, bgpRcvdPathAttrTable, bgp4PathAttrTable - A BGP 3860 peer's routing information may be sensitive for ISPs as the 3861 contents of their routing tables may expose details related to 3862 business relationships as implemented in Internet routing. 3864 SNMP versions prior to SNMPv3 did not include adequate security. 3865 Even if the network itself is secure (for example by using IPSec), 3866 even then, there is no control as to who on the secure network is 3867 allowed to access and GET/SET (read/change/create/delete) the objects 3868 in this MIB module. 3870 It is RECOMMENDED that implementers consider the security features as 3871 provided by the SNMPv3 framework (see [RFC3410], section 8), 3872 including full support for the SNMPv3 cryptographic mechanisms (for 3873 authentication and privacy). 3875 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3876 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3877 enable cryptographic security. It is then a customer/operator 3878 responsibility to ensure that the SNMP entity giving access to an 3879 instance of this MIB module is properly configured to give access to 3880 the objects only to those principals (users) that have legitimate 3881 rights to indeed GET or SET (change/create/delete) them. 3883 9. IANA Considerations 3885 This document includes an OID, bgpExtensions, which defines a name 3886 space for future BGP extensions. IANA is requested to create a new 3887 registry for new OIDs under bgpExtensions that will define the root 3888 OID of future MIB modules for bgp extensions. The assignment OIDs 3889 should be done based upon IDR working group consensus. 3891 10. Contributors 3893 This document owes significant thanks over the years to Wayne 3894 Tackabury, Susan Hares and the members of the idr and ops-nm mailing 3895 lists. This document represents several years of negotiating 3896 operational needs, Internet operational security considerations and 3897 the sheer messiness of representing the BGP protocol in SMIv2. 3899 I owe particular thanks to Susan Hares as a mentor who let me dive 3900 head-first into the world of Internet standards work by saying, "We 3901 have this MIB that just needs a little cleanup to advance in the 3902 standards process." 3904 11. Acknowledgements 3906 We would like to acknowledge the assistance of all the members of the 3907 Inter-Domain Routing Working Group, and particularly the following 3908 individuals: 3910 Yakov Rekhter, Juniper Networks 3912 Rob Coltun, Redback 3914 Guy Almes, Internet2 3916 Jeff Honig, BSDi 3917 Marshall T. Rose, Dover Beach Consulting, Inc. 3919 Dennis Ferguson, Juniper Networks 3921 Matt Mathis, PSC 3923 John Krawczyk, Bay Networks 3925 Curtis Villamizar, Avici 3927 Dave LeRoy, Pencom Systems 3929 Paul Traina, Juniper Networks 3931 Andrew Partan, MFN 3933 Robert Snyder, Cisco Systems 3935 Dimitry Haskin, Nortel 3937 Peder Chr Norgaard, Telebit Communications A/S 3939 Joel Halpern, CTO Longitude Systems, Inc. 3941 Nick Thille, RedBack Networks 3943 Bert Wijnen, Lucent 3945 Shane Wright, NextHop Technologies 3947 Mike McFadden, Riverstone Networks, Inc. 3949 Jon Saperia, JDS Consulting, Inc. 3951 Wayne Tackabury, Gold Wire Technology, Inc. 3953 Bill Fenner, AT&T Research 3955 RJ Atkinson, Extreme Networks 3957 Dan Romascanu, Avaya 3959 Mathew Richardson, NextHop Technologies 3961 The origin of this document is from RFC 1269 "Definitions of 3962 Managed Objects for the Border Gateway Protocol (Version 3)" 3963 written by Steve Willis and John Burruss, which was updated by 3964 John Chu to support BGP-4 in RFC 1657. The editors wish to 3965 acknowledge the fine work of these original authors. 3967 12. References 3969 12.1. Normative References 3971 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3972 Requirement Levels", BCP 14, RFC 2119, March 1997. 3974 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3975 Schoenwaelder, Ed., "Structure of Management Information 3976 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 3978 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3979 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 3980 STD 58, RFC 2579, April 1999. 3982 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3983 "Conformance Statements for SMIv2", STD 58, RFC 2580, 3984 April 1999. 3986 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 3987 Architecture for Describing Simple Network Management 3988 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 3989 December 2002. 3991 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 3992 Protocol 4 (BGP-4)", RFC 4271, January 2006. 3994 [RFC4273] Haas, J. and S. Hares, "Definitions of Managed Objects for 3995 BGP-4", RFC 4273, January 2006. 3997 [RFC2545] Marques, P. and F. Dupont, "Use of BGP-4 Multiprotocol 3998 Extensions for IPv6 Inter-Domain Routing", RFC 2545, 3999 March 1999. 4001 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 4002 Schoenwaelder, "Textual Conventions for Internet Network 4003 Addresses", RFC 4001, February 2005. 4005 [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, 4006 "Multiprotocol Extensions for BGP-4", RFC 4760, 4007 January 2007. 4009 [RFC5065] Traina, P., McPherson, D., and J. Scudder, "Autonomous 4010 System Confederations for BGP", RFC 5065, August 2007. 4012 12.2. Informative References 4014 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 4015 "Introduction and Applicability Statements for Internet- 4016 Standard Management Framework", RFC 3410, December 2002. 4018 [RFC1657] Willis, S., Burruss, J., and J. Chu, "Definitions of 4019 Managed Objects for the Fourth Version of the Border 4020 Gateway Protocol (BGP-4) using SMIv2", RFC 1657, 4021 July 1994. 4023 [RFC3107] Rekhter, Y. and E. Rosen, "Carrying Label Information in 4024 BGP-4", RFC 3107, May 2001. 4026 [RFC4022] Raghunarayan, R., "Management Information Base for the 4027 Transmission Control Protocol (TCP)", RFC 4022, 4028 March 2005. 4030 [RFC4456] Bates, T., Chen, E., and R. Chandra, "BGP Route 4031 Reflection: An Alternative to Full Mesh Internal BGP 4032 (IBGP)", RFC 4456, April 2006. 4034 Author's Address 4036 Jeffrey Haas 4038 Phone: 4039 EMail: jhaas@pfrc.org 4041 Full Copyright Statement 4043 Copyright (C) The IETF Trust (2008). 4045 This document is subject to the rights, licenses and restrictions 4046 contained in BCP 78, and except as set forth therein, the authors 4047 retain all their rights. 4049 This document and the information contained herein are provided on an 4050 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 4051 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 4052 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 4053 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 4054 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 4055 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 4057 Intellectual Property 4059 The IETF takes no position regarding the validity or scope of any 4060 Intellectual Property Rights or other rights that might be claimed to 4061 pertain to the implementation or use of the technology described in 4062 this document or the extent to which any license under such rights 4063 might or might not be available; nor does it represent that it has 4064 made any independent effort to identify any such rights. Information 4065 on the procedures with respect to rights in RFC documents can be 4066 found in BCP 78 and BCP 79. 4068 Copies of IPR disclosures made to the IETF Secretariat and any 4069 assurances of licenses to be made available, or the result of an 4070 attempt made to obtain a general license or permission for the use of 4071 such proprietary rights by implementers or users of this 4072 specification can be obtained from the IETF on-line IPR repository at 4073 http://www.ietf.org/ipr. 4075 The IETF invites any interested party to bring to its attention any 4076 copyrights, patents or patent applications, or other proprietary 4077 rights that may cover technology that may be required to implement 4078 this standard. Please address the information to the IETF at 4079 ietf-ipr@ietf.org. 4081 Acknowledgement 4083 Funding for the RFC Editor function is provided by the IETF 4084 Administrative Support Activity (IASA).