idnits 2.17.1 draft-ietf-idr-bgp4-mibv2-06.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 3783. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 3794. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 3801. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 3807. 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 16 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 (November 11, 2007) is 6012 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 November 11, 2007 4 Intended status: Standards Track 5 Expires: May 14, 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-06 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 May 14, 2008. 36 Copyright Notice 38 Copyright (C) The IETF Trust (2007). 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 . . . . . . . . . . . . . 6 62 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 7 63 8. Security Considerations . . . . . . . . . . . . . . . . . . . 75 64 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 76 65 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 76 66 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 77 67 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 78 68 12.1. Normative References . . . . . . . . . . . . . . . . . . . 78 69 12.2. Informative References . . . . . . . . . . . . . . . . . . 79 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 along 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 bgpAfPathAttrCount - 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 independent peering 157 sessions. This table replaces the bgpPeerTable from previous 158 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 AFI-SAFI counters for 178 prefixes. 180 o bgpNlriTable - A table of per-peer per AFI-SAFI prefix data. This 181 table covers information previously present in bgp4PathAttrTable. 183 o bgpAdjRibsOutTable - A per-peer per AFI-SAFI table indicating what 184 reachability has been advertised to a given peer. 186 o bgpAfPathAttrTable - A table of BGP Path Attribute information. 188 o bgpAsPathTable - A table that decomposes the elements of a BGP AS 189 Path. 191 o bgpAfPathUnknownTable - A table that decomposes the unknown 192 elements received in a BGP Path Attribute tuple. 194 5.3. Obsoleted Tables 196 o bgpPeerTable - Replaced by the information in bgpPeerAfTable, 197 bgpPeerAfErrorsTable, bgpPeerConfiguredTimersTable, 198 bgpPeerAfNegotiatedTimersTable, bgpPeerAfCountersTable. 200 o bgpRcvPathAttrTable - Covered BGP-3 and earlier. 202 o bgp4PathAttrTable - Replaced by the information in bgpNlriTable, 203 bgpAfPathAttrTable and bgpAfPathUnknownTable. 205 5.4. Textual Conventions 207 o BgpIdentifierTC - Representation of a BGP Identifier 209 o BgpAfiTC - Representation of a BGP Address Family Identifier 211 o BgpSafiTC - Representation of a BGP Subsequent Address Family 212 Identifier 214 o BgoPathAttrFlagsTC - Representation of BGP-4 Path Attribute Flags. 216 5.5. Notifications 218 o bgpAfEstablishedNotification - Sent when a BGP peer transitions 219 into the Established state. Replaces the previous 220 bgpEstablishedNotification, which was not address family 221 independent. 223 o bgpAfBackwardTransNotification - Sent when a BGP peer transitions 224 out of the Established state. Replaces the previous 225 bgpBackwardTransNotification, which was not addrss family 226 independent. 228 o bgpEstablished - Erroneously added to an incorrect OID in a 229 previous version of this MIB. 231 o bgpBackwardsTransition - Erroneously added to an incorrect OID in 232 a previous version of this MIB. 234 5.6. Extensions 236 A feature of this MIB is the recognition that the BGP protocol 237 continues to grow in functionality. The bgpExtensions OID is defined 238 to provide a place for IDR-approved MIB modules for BGP extensions to 239 be added to the bgp MIB subtree. 241 It is intended that, where possible, that tables added via extensions 242 that add information via additional path attributes use 243 bgpAfPathAttrIndex as a common index, either via INDEX or AUGMENTS. 245 6. Relationship to Other MIB Modules 247 6.1. Relationship to the TCP-MIB 249 The bgpPeerAfLocalAddrType/bgpPeerAfLocalAddr/bgpPeerAfLocalPort and 250 bgpPeerAfRemoteAddrType/bgpPeerAfRemoteAddr/bgpPeerAfRemotePort 251 objects may provide a suitable index for monitoring the BGP peering 252 session's TCP session via the TCP-MIB [RFC4022]. 254 Note that conducting BGP peering sessions over transport protocols 255 other that TCP over IP are out of scope of the current BGP 256 specifications. 258 6.2. MIB modules required for IMPORTS 260 The following MIB module IMPORTS objects from SNMPv2-SMI [RFC2578], 261 SNMPv2-TC [RFC2579], SNMPv2-CONF [RFC2580], INET-ADDRESS-MIB 263 [RFC4001] and SNMP-FRAMEWORK-MIB [RFC3411]. 265 7. Definitions 267 BGP4-MIB DEFINITIONS ::= BEGIN 269 IMPORTS 270 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 271 IpAddress, Counter32, Gauge32, mib-2, Unsigned32, Integer32 272 FROM SNMPv2-SMI 273 InetAddressType, InetAddress, InetPortNumber, 274 InetAutonomousSystemNumber, InetAddressPrefixLength 275 FROM INET-ADDRESS-MIB 276 TEXTUAL-CONVENTION, TruthValue, RowPointer, TimeStamp 277 FROM SNMPv2-TC 278 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 279 FROM SNMPv2-CONF 280 SnmpAdminString 281 FROM SNMP-FRAMEWORK-MIB; 283 bgp MODULE-IDENTITY 284 LAST-UPDATED "200711070000Z" 285 ORGANIZATION "IETF IDR Working Group" 286 CONTACT-INFO "E-mail: idr@ietf.org" 288 DESCRIPTION 289 "The MIB module for the BGP-4 protocol. 291 Copyright (C) The Internet Society (2007). This 292 version of this MIB module is part of RFC XXX; 293 see the RFC itself for full legal notices." 294 -- RFC Editor - replace XXX with RFC number 296 REVISION "200711110000Z" 297 DESCRIPTION 298 "Changes from RFC 4273: 300 TODO" 302 REVISION "200601110000Z" 303 DESCRIPTION 304 "Changes from RFC 1657: 306 1) Fixed the definitions of the notifications 307 to make them equivalent to their initial 308 definition in RFC 1269. 309 2) Added compliance and conformance info. 310 3) Updated information for the values of 311 bgpPeerNegotiatedVersion, bgp4PathAttrLocalPref, 312 bgp4PathAttrCalcLocalPref, 313 bgp4PathAttrMultiExitDisc, 314 bgp4PathAttrASPathSegement. 315 4) Added additional clarification comments where 316 needed. 317 5) Noted where objects do not fully reflect 318 the protocol as Known Issues. 319 6) Updated the DESCRIPTION for the 320 bgp4PathAttrAtomicAggregate object. 321 7) The following objects have had their DESCRIPTION 322 clause modified to remove the text that suggested 323 (using 'should' verb) initializing the counter 324 to zero on a transition to the established state: 325 bgpPeerInUpdates, bgpPeerOutUpdates, 326 bgpPeerInTotalMessages, bgpPeerOutTotalMessages 327 Those implementations that still do this are 328 still compliant with this new wording. 329 Applications should not assume counters have 330 started at zero. 332 Published as RFC 4273." 334 REVISION "199405050000Z" 335 DESCRIPTION 336 "Translated to SMIv2 and published as RFC 1657." 338 REVISION "199110261839Z" 339 DESCRIPTION 340 "Initial version, published as RFC 1269." 341 ::= { mib-2 15 } 343 -- 344 -- Textual Conventions 345 -- 347 BgpIdentifierTC ::= TEXTUAL-CONVENTION 348 DISPLAY-HINT "1d." 349 STATUS current 350 DESCRIPTION 351 "The representation of a BGP Identifier. The BGP 352 Identifier should be represented in the OCTET STRING 353 as with the first OCTET of the string containing 354 the first OCTET of the BGP Identifier received or sent 355 in the OPEN packet and so on. 357 The BGP Identifier is displayed as if it is an IP address, 358 even if it would be an illegal one." 360 REFERENCE 361 "RFC 4273, Section 4.2" 362 SYNTAX OCTET STRING(SIZE (4)) 364 BgpAfiTC ::= 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 BgpSafiTC ::= TEXTUAL-CONVENTION 374 DISPLAY-HINT "d" 375 STATUS current 376 DESCRIPTION 377 "The representation of a BGP SAFI" 378 REFERENCE 379 "RFC 4760, Section 3" 380 SYNTAX Unsigned32(0..255) 382 BgpPathAttrFlagsTC ::= TEXTUAL-CONVENTION 383 STATUS current 384 DESCRIPTION 385 "The representation of BGP Path Attribute Flags. Note that this 386 textual convention is meant to directly map to a BGP Path 387 Attribute's Flags and is thus constrained by protocol to have no 388 more than 8 total bits in use." 389 REFERENCE 390 "RFC 4271, Sec. 4.3" 391 SYNTAX BITS { 392 optional(0), -- When set, path attribute is optional instead of 393 -- well known. 394 transitive(1), -- Path attribute is transitive when set. 395 partial(2), -- Path attribute is partial when set. 396 extLength(3) -- Path attributes has extended length field. 397 -- 4-7 are reserved 398 -- values 8 or greater are illegal. 399 } 401 -- 402 -- Top level scalars for this MIB 403 -- 405 bgpVersion OBJECT-TYPE 406 SYNTAX OCTET STRING (SIZE (1..255)) 407 MAX-ACCESS read-only 408 STATUS current 409 DESCRIPTION 410 "Vector of supported BGP protocol version 411 numbers. Each peer negotiates the version 412 from this vector. Versions are identified 413 via the string of bits contained within this 414 object. The first octet contains bits 0 to 415 7, the second octet contains bits 8 to 15, 416 and so on, with the most significant bit 417 referring to the lowest bit number in the 418 octet (e.g., the MSB of the first octet 419 refers to bit 0). If a bit, i, is present 420 and set, then the version (i+1) of the BGP 421 is supported." 422 REFERENCE 423 "RFC 4271, Section 4.2." 424 ::= { bgp 1 } 426 -- bgp 2 and 3 have been deprecated and are documented 427 -- elsewhere in this MIB 429 bgpIdentifier OBJECT-TYPE 430 SYNTAX IpAddress 431 MAX-ACCESS read-only 432 STATUS current 433 DESCRIPTION 434 "The BGP Identifier of the local system. 436 A SYNTAX of BgpIdentifierTC would be used here, 437 however it would cause this object to be 438 deprecated with no additional value. The 439 comments in the DESCRIPTION of BgpIdentifierTC 440 apply here." 441 REFERENCE 442 "RFC 4271, Section 4.2." 443 ::= { bgp 4 } 445 bgpLocalAsNew OBJECT-TYPE 446 SYNTAX InetAutonomousSystemNumber 447 MAX-ACCESS read-only 448 STATUS current 449 DESCRIPTION 450 "The local autonomous system number. 452 This object supports 4 byte ASes and replaces 453 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 bgpPeerAfInstance 503 Unsigned32, 504 bgpPeerAfIdentifier 505 BgpIdentifierTC, 506 bgpPeerAfPeerState 507 INTEGER, 508 bgpPeerAfAdminStatus 509 INTEGER, 510 bgpPeerAfConfiguredVersion 511 Unsigned32, 512 bgpPeerAfNegotiatedVersion 513 Unsigned32, 514 bgpPeerAfLocalAddrType 515 InetAddressType, 516 bgpPeerAfLocalAddr 517 InetAddress, 518 bgpPeerAfLocalPort 519 InetPortNumber, 520 bgpPeerAfLocalAs 521 InetAutonomousSystemNumber, 522 bgpPeerAfRemoteAddrType 523 InetAddressType, 524 bgpPeerAfRemoteAddr 525 InetAddress, 526 bgpPeerAfRemotePort 527 InetPortNumber, 528 bgpPeerAfRemoteAs 529 InetAutonomousSystemNumber 530 } 532 bgpPeerAfInstance OBJECT-TYPE 533 SYNTAX Unsigned32 534 MAX-ACCESS not-accessible 535 STATUS current 536 DESCRIPTION 537 "The routing instance index. 539 Some BGP implementations permit the creation of 540 multiple instances of a BGP routing process. An 541 example includes routers running BGP/MPLS IP Virtual 542 Private Networks. 544 Implementations that do not support multiple 545 routing instances should return 1 for this object." 546 ::= { bgpPeerAfEntry 1 } 548 bgpPeerAfIdentifier OBJECT-TYPE 549 SYNTAX BgpIdentifierTC 550 MAX-ACCESS read-only 551 STATUS current 552 DESCRIPTION 553 "The BGP Identifier of this entry's remote BGP peer. 555 This entry should be 0.0.0.0 unless the 556 bgpPeerAfPeerState is in the openconfirm or the 557 established state." 558 REFERENCE 559 "RFC 4271, Section 4.2, 'BGP Identifier'." 560 ::= { bgpPeerAfEntry 2 } 562 -- TODO - update according to new FSM 563 bgpPeerAfPeerState OBJECT-TYPE 564 SYNTAX INTEGER { 565 idle(1), 566 connect(2), 567 active(3), 568 opensent(4), 569 openconfirm(5), 570 established(6) 571 } 572 MAX-ACCESS read-only 573 STATUS current 574 DESCRIPTION 575 "The BGP peer connection state." 576 REFERENCE 577 "RFC 4271, Section 8.2.2." 578 ::= { bgpPeerAfEntry 3 } 580 bgpPeerAfAdminStatus OBJECT-TYPE 581 SYNTAX INTEGER { 582 halted(1), 583 running(2) 584 } 585 MAX-ACCESS read-only 586 STATUS current 587 DESCRIPTION 588 "Whether or not the BGP FSM for this remote peer is 589 halted or running. The BGP FSM for a remote peer is 590 halted after processing a Stop event. Likewise, it is 591 in the running state after a Start event. 593 The bgpPeerAfState will generally be in the idle state 594 when the FSM is halted, although some extensions such 595 as Graceful Restart will leave the peer in the Idle 596 state but with the FSM running." 597 REFERENCE 598 "RFC 4271, Section 8.1.2." 600 ::= { bgpPeerAfEntry 4 } 602 bgpPeerAfConfiguredVersion OBJECT-TYPE 603 SYNTAX Unsigned32 (1..255) 604 MAX-ACCESS read-only 605 STATUS current 606 DESCRIPTION 607 "The configured version to originally start with this 608 remote peer. The BGP speaker may permit negotiation to a 609 lower version number of the protocol." 610 REFERENCE 611 "RFC 4271, Section 4.2. 612 RFC 4271, Section 7." 613 ::= { bgpPeerAfEntry 5 } 615 bgpPeerAfNegotiatedVersion OBJECT-TYPE 616 SYNTAX Unsigned32 (1..255) 617 MAX-ACCESS read-only 618 STATUS current 619 DESCRIPTION 620 "The negotiated version of BGP running between 621 the two peers. 623 This entry MUST be zero (0) unless the 624 bgpPeerAfState is in the openconfirm or the 625 established state. 627 Note that legal values for this object are 628 between 0 and 255." 629 REFERENCE 630 "RFC 4271, Section 4.2. 631 RFC 4271, Section 7." 632 ::= { bgpPeerAfEntry 6 } 634 bgpPeerAfLocalAddrType OBJECT-TYPE 635 SYNTAX InetAddressType 636 MAX-ACCESS not-accessible 637 STATUS current 638 DESCRIPTION 639 "The address family of the local end of the peering 640 session." 641 ::= { bgpPeerAfEntry 7 } 643 bgpPeerAfLocalAddr OBJECT-TYPE 644 SYNTAX InetAddress (SIZE(4..20)) 645 MAX-ACCESS not-accessible 646 STATUS current 647 DESCRIPTION 648 "The local IP address of this entry's BGP connection." 649 ::= { bgpPeerAfEntry 8 } 651 bgpPeerAfLocalPort OBJECT-TYPE 652 SYNTAX InetPortNumber 653 MAX-ACCESS read-only 654 STATUS current 655 DESCRIPTION 656 "The local port for the TCP connection between the BGP 657 peers." 658 ::= { bgpPeerAfEntry 9 } 660 bgpPeerAfLocalAs OBJECT-TYPE 661 SYNTAX InetAutonomousSystemNumber 662 MAX-ACCESS read-only 663 STATUS current 664 DESCRIPTION 665 "Some implementations of BGP can represent themselves 666 as multiple ASes. This is the AS that this peering 667 session is representing itself as to the remote peer." 668 ::= { bgpPeerAfEntry 10 } 670 bgpPeerAfRemoteAddrType OBJECT-TYPE 671 SYNTAX InetAddressType 672 MAX-ACCESS not-accessible 673 STATUS current 674 DESCRIPTION 675 "The address family of the remote end of the peering 676 session." 677 ::= { bgpPeerAfEntry 11 } 679 bgpPeerAfRemoteAddr OBJECT-TYPE 680 SYNTAX InetAddress (SIZE(4..20)) 681 MAX-ACCESS not-accessible 682 STATUS current 683 DESCRIPTION 684 "The remote IP address of this entry's BGP peer." 685 ::= { bgpPeerAfEntry 12 } 687 bgpPeerAfRemotePort OBJECT-TYPE 688 SYNTAX InetPortNumber 689 MAX-ACCESS read-only 690 STATUS current 691 DESCRIPTION 692 "The remote port for the TCP connection between the BGP 693 peers. 695 Note that the objects bgpPeerAfLocalAddr, 696 bgpPeerAfLocalPort, bgpPeerAfRemoteAddr and 697 bgpPeerAfRemotePort provide the appropriate reference to 698 the standard MIB TCP connection table, or even the ipv6 699 TCP MIB as in RFC 4022." 700 REFERENCE 701 "RFC 2012 - SNMPv2 Management Information Base for the 702 Transmission Control Protocol using SMIv2. 703 RFC 4022 - IP Version 6 Management Information Base 704 for the Transmission Control Protocol." 705 ::= { bgpPeerAfEntry 13 } 707 bgpPeerAfRemoteAs OBJECT-TYPE 708 SYNTAX InetAutonomousSystemNumber 709 MAX-ACCESS read-only 710 STATUS current 711 DESCRIPTION 712 "The remote autonomous system number received in the BGP 713 OPEN message." 714 REFERENCE 715 "RFC 4271, Section 4.2." 716 ::= { bgpPeerAfEntry 14 } 718 -- 719 -- Address Family (Af) independent per-peer error management 720 -- information. 721 -- 723 bgpPeerAfErrors 724 OBJECT IDENTIFIER ::= { bgpPeerAf 2 } 726 bgpPeerAfErrorsTable OBJECT-TYPE 727 SYNTAX SEQUENCE OF BgpPeerAfErrorsEntry 728 MAX-ACCESS not-accessible 729 STATUS current 730 DESCRIPTION 731 "On a per-peer basis, this table reflects the last 732 protocol-defined error encountered and reported on 733 the peer session. If no entry for a given peer 734 exists in this table, then no such errors have been 735 observed, reported, and recorded on the session." 736 ::= { bgpPeerAfErrors 1 } 738 bgpPeerAfErrorsEntry OBJECT-TYPE 739 SYNTAX BgpPeerAfErrorsEntry 740 MAX-ACCESS not-accessible 741 STATUS current 742 DESCRIPTION 743 "Each entry contains information about errors sent 744 and received for a particular BGP peer." 745 AUGMENTS { 746 bgpPeerAfEntry 747 } 748 ::= { bgpPeerAfErrorsTable 1 } 750 BgpPeerAfErrorsEntry ::= SEQUENCE { 751 bgpPeerAfLastErrorReceived 752 OCTET STRING, 753 bgpPeerAfLastErrorSent 754 OCTET STRING, 755 bgpPeerAfLastErrorReceivedTime 756 TimeStamp, 757 bgpPeerAfLastErrorSentTime 758 TimeStamp, 759 bgpPeerAfLastErrorReceivedText 760 SnmpAdminString, 761 bgpPeerAfLastErrorSentText 762 SnmpAdminString, 763 bgpPeerAfLastErrorReceivedData 764 OCTET STRING, 765 bgpPeerAfLastErrorSentData 766 OCTET STRING 767 } 769 bgpPeerAfLastErrorReceived OBJECT-TYPE 770 SYNTAX OCTET STRING (SIZE (2)) 771 MAX-ACCESS read-only 772 STATUS current 773 DESCRIPTION 774 "The last error code and subcode received from this peer 775 via NOTIFICATION message on this connection. If no 776 error has occurred, this field is zero. Otherwise, the 777 first byte of this two byte OCTET STRING contains the 778 error code, and the second byte contains the subcode." 779 REFERENCE 780 "RFC 4271, Section 4.5. 781 RFC 4486 optionally supported. 782 RFC 3362, Section 5 optionally supported." 783 ::= { bgpPeerAfErrorsEntry 1 } 785 bgpPeerAfLastErrorSent OBJECT-TYPE 786 SYNTAX OCTET STRING (SIZE (2)) 787 MAX-ACCESS read-only 788 STATUS current 789 DESCRIPTION 790 "The last error code and subcode sent by this BGP 791 Speaker via NOTIFICATION message on this connection. 793 If no error has occurred, this field is zero. 794 Otherwise, the first byte of this two byte OCTET STRING 795 contains the error code, and the second byte contains 796 the subcode." 797 REFERENCE 798 "RFC 4271, Section 4.5. 799 RFC 4486 optionaly supported. 800 RFC 3362, Section 5 optionally supported." 801 ::= { bgpPeerAfErrorsEntry 2 } 803 bgpPeerAfLastErrorReceivedTime OBJECT-TYPE 804 SYNTAX TimeStamp 805 MAX-ACCESS read-only 806 STATUS current 807 DESCRIPTION 808 "The timestamp that the last NOTIFICATION was received from 809 this peer." 810 REFERENCE 811 "RFC 4271, Section 4.5." 812 ::= { bgpPeerAfErrorsEntry 3 } 814 bgpPeerAfLastErrorSentTime OBJECT-TYPE 815 SYNTAX TimeStamp 816 MAX-ACCESS read-only 817 STATUS current 818 DESCRIPTION 819 "The timestamp that the last NOTIFICATION was sent to 820 this peer." 821 REFERENCE 822 "RFC 4271, Section 4.5." 823 ::= { bgpPeerAfErrorsEntry 4 } 825 bgpPeerAfLastErrorReceivedText OBJECT-TYPE 826 SYNTAX SnmpAdminString 827 MAX-ACCESS read-only 828 STATUS current 829 DESCRIPTION 830 "This object contains an implementation specific 831 explanation of the error that was reported." 832 ::= { bgpPeerAfErrorsEntry 5 } 834 bgpPeerAfLastErrorSentText OBJECT-TYPE 835 SYNTAX SnmpAdminString 836 MAX-ACCESS read-only 837 STATUS current 838 DESCRIPTION 839 "This object contains an implementation specific 840 explanation of the error that is being reported." 842 ::= { bgpPeerAfErrorsEntry 6 } 844 bgpPeerAfLastErrorReceivedData OBJECT-TYPE 845 SYNTAX OCTET STRING (SIZE(0..4075)) 846 MAX-ACCESS read-only 847 STATUS current 848 DESCRIPTION 849 "The last error code's data seen by this peer. 851 Per RFC 2578, some implementations may have limitations 852 dealing with OCTET STRINGS larger than 255. Thus, this 853 data may be truncated." 854 REFERENCE 855 "RFC 4271, Section 4.5, 856 RFC 2578, Section 7.1.2, 857 RFC 4486 optionaly supported. 858 RFC 3362, Section 5 optionally supported." 859 ::= { bgpPeerAfErrorsEntry 7 } 861 bgpPeerAfLastErrorSentData OBJECT-TYPE 862 SYNTAX OCTET STRING (SIZE(0..4075)) 863 MAX-ACCESS read-only 864 STATUS current 865 DESCRIPTION 866 "The last error code's data sent to this peer. 868 Per RFC 2578, some implementations may have limitations 869 dealing with OCTET STRINGS larger than 255. Thus, this 870 data may be truncated." 871 REFERENCE 872 "RFC 4271, Section 4.5, 873 RFC 2578, Section 7.1.2 874 RFC 4486 optionaly supported. 875 RFC 3362, Section 5 optionally supported." 876 ::= { bgpPeerAfErrorsEntry 8 } 878 -- 879 -- Address Family (Af) independent per-peer timer information 880 -- 882 bgpPeerAfTimers 883 OBJECT IDENTIFIER ::= { bgpPeerAf 3 } 885 -- 886 -- Per-peer Event Times 887 -- 889 bgpPeerAfEventTimesTable OBJECT-TYPE 890 SYNTAX SEQUENCE OF BgpPeerAfEventTimesEntry 891 MAX-ACCESS not-accessible 892 STATUS current 893 DESCRIPTION 894 "A table reporting the per-peering session amount 895 of time elapsed and update events since the peering 896 session advanced into the established state." 897 ::= { bgpPeerAfTimers 1 } 899 bgpPeerAfEventTimesEntry OBJECT-TYPE 900 SYNTAX BgpPeerAfEventTimesEntry 901 MAX-ACCESS not-accessible 902 STATUS current 903 DESCRIPTION 904 "Each row contains a set of statistics about time 905 spent and events encountered in the peer session 906 established state." 907 AUGMENTS { 908 bgpPeerAfEntry 909 } 910 ::= { bgpPeerAfEventTimesTable 1 } 912 BgpPeerAfEventTimesEntry ::= SEQUENCE { 913 bgpPeerAfFsmEstablishedTime 914 Gauge32, 915 bgpPeerAfInUpdatesElapsedTime 916 Gauge32 917 } 919 bgpPeerAfFsmEstablishedTime OBJECT-TYPE 920 SYNTAX Gauge32 921 UNITS "seconds" 922 MAX-ACCESS read-only 923 STATUS current 924 DESCRIPTION 925 "This timer indicates how long (in seconds) this peer 926 has been in the established state or how long since this 927 peer was last in the established state. It is set to 928 zero when a new peer is configured or when the router is 929 booted." 930 REFERENCE 931 "RFC 4271, Section 8." 932 ::= { bgpPeerAfEventTimesEntry 1 } 934 bgpPeerAfInUpdatesElapsedTime OBJECT-TYPE 935 SYNTAX Gauge32 936 UNITS "seconds" 937 MAX-ACCESS read-only 938 STATUS current 939 DESCRIPTION 940 "Elapsed time (in seconds) since the last BGP UPDATE 941 message was received from the peer. Each time 942 bgpPeerInUpdates is incremented, the value of this 943 object is set to zero (0)." 944 REFERENCE 945 "RFC 4271, Section 4.3. 946 RFC 4271, Section 8.2.2, Established state." 948 ::= { bgpPeerAfEventTimesEntry 2 } 950 -- 951 -- Per-Peer Configured Timers 952 -- 954 bgpPeerAfConfiguredTimersTable OBJECT-TYPE 955 SYNTAX SEQUENCE OF BgpPeerAfConfiguredTimersEntry 956 MAX-ACCESS not-accessible 957 STATUS current 958 DESCRIPTION 959 "Per peer management data on BGP session timers." 960 ::= { bgpPeerAfTimers 2 } 962 bgpPeerAfConfiguredTimersEntry OBJECT-TYPE 963 SYNTAX BgpPeerAfConfiguredTimersEntry 964 MAX-ACCESS not-accessible 965 STATUS current 966 DESCRIPTION 967 "Each entry corresponds to the current state of 968 BGP timers on a given peering session." 969 AUGMENTS { 970 bgpPeerAfEntry 971 } 972 ::= { bgpPeerAfConfiguredTimersTable 1 } 974 BgpPeerAfConfiguredTimersEntry ::= SEQUENCE { 975 bgpPeerAfConnectRetryInterval 976 Unsigned32, 977 bgpPeerAfHoldTimeConfigured 978 Unsigned32, 979 bgpPeerAfKeepAliveConfigured 980 Unsigned32, 981 bgpPeerAfMinASOrigInterval 982 Unsigned32, 983 bgpPeerAfMinRouteAdverInterval 984 Unsigned32 985 } 986 bgpPeerAfConnectRetryInterval OBJECT-TYPE 987 SYNTAX Unsigned32 (1..65535) 988 UNITS "seconds" 989 MAX-ACCESS read-only 990 STATUS current 991 DESCRIPTION 992 "Time interval (in seconds) for the ConnectRetry timer. 993 The suggested value for this timer is 120 seconds." 994 REFERENCE 995 "RFC 4271, Section 8.2.2. This is the value used 996 to initialize the 'ConnectRetryTimer'." 997 ::= { bgpPeerAfConfiguredTimersEntry 1 } 999 bgpPeerAfHoldTimeConfigured OBJECT-TYPE 1000 SYNTAX Unsigned32 ( 0 | 3..65535 ) 1001 UNITS "seconds" 1002 MAX-ACCESS read-only 1003 STATUS current 1004 DESCRIPTION 1005 "Time interval (in seconds) for the Hold Timer 1006 established with the peer. The value of this object is 1007 calculated by this BGP speaker, using the smaller of the 1008 values in bgpPeerHoldTimeConfigured and the Hold Time 1009 received in the OPEN message. 1011 This value must be at least three seconds if it is not 1012 zero (0). 1014 If the Hold Timer has not been established with the 1015 peer this object MUST have a value of zero (0). 1017 If the bgpPeerHoldTimeConfigured object has a value of 1018 (0), then this object MUST have a value of (0)." 1019 REFERENCE 1020 "RFC 4271, Section 4.2." 1021 ::= { bgpPeerAfConfiguredTimersEntry 2 } 1023 bgpPeerAfKeepAliveConfigured OBJECT-TYPE 1024 SYNTAX Unsigned32 ( 0 | 1..21845 ) 1025 UNITS "seconds" 1026 MAX-ACCESS read-only 1027 STATUS current 1028 DESCRIPTION 1029 "Time interval (in seconds) for the KeepAlive timer 1030 configured for this BGP speaker with this peer. The 1031 value of this object will only determine the KEEPALIVE 1032 messages' frequency relative to the value specified in 1033 bgpPeerHoldTimeConfigured; the actual time interval for 1034 the KEEPALIVE messages is indicated by bgpPeerKeepAlive. 1036 A reasonable maximum value for this timer would be one 1037 third of that of bgpPeerHoldTimeConfigured. 1039 If the value of this object is zero (0), no periodic 1040 KEEPALIVE messages are sent to the peer after the BGP 1041 connection has been established. The suggested value 1042 for this timer is 30 seconds." 1043 REFERENCE 1044 "RFC 4271, Section 4.4. 1045 RFC 4271, Section 10." 1046 ::= { bgpPeerAfConfiguredTimersEntry 3 } 1048 bgpPeerAfMinASOrigInterval OBJECT-TYPE 1049 SYNTAX Unsigned32 (0..65535) 1050 UNITS "seconds" 1051 MAX-ACCESS read-only 1052 STATUS current 1053 DESCRIPTION 1054 "Time interval (in seconds) for the 1055 MinASOriginationInterval timer. 1057 The suggested value for this timer is 15 seconds." 1058 REFERENCE 1059 "RFC 4271, Section 9.2.1.2. 1060 RFC 4271, Section 10." 1061 ::= { bgpPeerAfConfiguredTimersEntry 4 } 1063 bgpPeerAfMinRouteAdverInterval OBJECT-TYPE 1064 SYNTAX Unsigned32 (0..65535) 1065 UNITS "seconds" 1066 MAX-ACCESS read-only 1067 STATUS current 1068 DESCRIPTION 1069 "Time interval (in seconds) for the 1070 MinRouteAdvertisementInterval timer. 1072 The suggested value for this timer is 30 seconds for 1073 EBGP connections and 5 seconds for IBGP connections." 1074 REFERENCE 1075 "RFC 4271, Section 9.2.1.1. 1076 RFC 4271, Section 10." 1077 ::= { bgpPeerAfConfiguredTimersEntry 5 } 1079 -- 1080 -- Per-Peer Negotiated Timers 1081 -- 1082 bgpPeerAfNegotiatedTimersTable OBJECT-TYPE 1083 SYNTAX SEQUENCE OF BgpPeerAfNegotiatedTimersEntry 1084 MAX-ACCESS not-accessible 1085 STATUS current 1086 DESCRIPTION 1087 "Configured values of per-peer timers are seen 1088 in the bgpPeerAfConfiguredTimersTable. 1090 Values in this table reflect the current 1091 operational values, after negotiation from values 1092 derived from initial configuration." 1093 ::= { bgpPeerAfTimers 3 } 1095 bgpPeerAfNegotiatedTimersEntry OBJECT-TYPE 1096 SYNTAX BgpPeerAfNegotiatedTimersEntry 1097 MAX-ACCESS not-accessible 1098 STATUS current 1099 DESCRIPTION 1100 "Each entry reflects a value of the currently 1101 operational, negotiated timer as reflected in the 1102 BgpPeerAfNegotiatedTimersEntry." 1103 AUGMENTS { 1104 bgpPeerAfEntry 1105 } 1106 ::= { bgpPeerAfNegotiatedTimersTable 1 } 1108 BgpPeerAfNegotiatedTimersEntry ::= SEQUENCE { 1109 bgpPeerAfHoldTime 1110 Unsigned32, 1111 bgpPeerAfKeepAlive 1112 Unsigned32 1113 } 1115 bgpPeerAfHoldTime OBJECT-TYPE 1116 SYNTAX Unsigned32 ( 0 | 3..65535 ) 1117 UNITS "seconds" 1118 MAX-ACCESS read-only 1119 STATUS current 1120 DESCRIPTION 1121 "The value of this object is calculated by this BGP 1122 Speaker as being; 1124 zero (0) - if this was the value sent by the peer and 1125 this value is permitted by this BGP Speaker. In this 1126 case, no keepalive messages are sent and the Hold Timer 1127 is not set. 1129 At least three (3). This value is the smaller of 1130 the value sent by this peer in the OPEN message and 1131 bgpPeerAfHoldTimeConfigured for this peer. 1133 This value is only defined when the peering session is 1134 in the Established state." 1135 REFERENCE 1136 "RFC 4271, Section 4.2." 1137 ::= { bgpPeerAfNegotiatedTimersEntry 1 } 1139 bgpPeerAfKeepAlive OBJECT-TYPE 1140 SYNTAX Unsigned32 ( 0 | 1..21845 ) 1141 UNITS "seconds" 1142 MAX-ACCESS read-only 1143 STATUS current 1144 DESCRIPTION 1145 "Time interval in seconds for the KeepAlive timer 1146 established with the peer. The value of this object 1147 is calculated by this BGP speaker such that, when 1148 compared with bgpPeerAfHoldTime, it has the same 1149 proportion as what bgpPeerAfKeepAliveConfigured has 1150 when compared with bgpPeerAfHoldTimeConfigured. If 1151 the value of this object is zero (0), it indicates 1152 that the KeepAlive timer has not been established 1153 with the peer, or, the value of 1154 bgpPeerAfKeepAliveConfigured is zero (0). 1156 This value is only defined when the peering session is 1157 in the Established state." 1158 REFERENCE 1159 "RFC 4271, Section 4.4." 1160 ::= { bgpPeerAfNegotiatedTimersEntry 2 } 1162 -- 1163 -- Per-peer counters 1164 -- 1166 bgpPeerAfCounters 1167 OBJECT IDENTIFIER ::= { bgpPeerAf 4 } 1169 bgpPeerAfCountersTable OBJECT-TYPE 1170 SYNTAX SEQUENCE OF BgpPeerAfCountersEntry 1171 MAX-ACCESS not-accessible 1172 STATUS current 1173 DESCRIPTION 1174 "The counters associated with a BGP Peer." 1175 ::= { bgpPeerAfCounters 1 } 1177 bgpPeerAfCountersEntry OBJECT-TYPE 1178 SYNTAX BgpPeerAfCountersEntry 1179 MAX-ACCESS not-accessible 1180 STATUS current 1181 DESCRIPTION 1182 "Each entry contains counters of message transmissions 1183 and FSM transitions for a given BGP Peering session." 1184 AUGMENTS { 1185 bgpPeerAfEntry 1186 } 1187 ::= { bgpPeerAfCountersTable 1 } 1189 BgpPeerAfCountersEntry ::= SEQUENCE { 1190 bgpPeerAfInUpdates 1191 Counter32, 1192 bgpPeerAfOutUpdates 1193 Counter32, 1194 bgpPeerAfInTotalMessages 1195 Counter32, 1196 bgpPeerAfOutTotalMessages 1197 Counter32, 1198 bgpPeerAfFsmEstablishedTrans 1199 Counter32 1200 } 1202 bgpPeerAfInUpdates OBJECT-TYPE 1203 SYNTAX Counter32 1204 MAX-ACCESS read-only 1205 STATUS current 1206 DESCRIPTION 1207 "The number of BGP UPDATE messages received on this 1208 connection. This object should be initialized to zero 1209 (0) when the connection is established." 1210 ::= { bgpPeerAfCountersEntry 1 } 1212 bgpPeerAfOutUpdates OBJECT-TYPE 1213 SYNTAX Counter32 1214 MAX-ACCESS read-only 1215 STATUS current 1216 DESCRIPTION 1217 "The number of BGP UPDATE messages transmitted on this 1218 connection. This object should be initialized to zero 1219 (0) when the connection is established." 1220 ::= { bgpPeerAfCountersEntry 2 } 1222 bgpPeerAfInTotalMessages OBJECT-TYPE 1223 SYNTAX Counter32 1224 MAX-ACCESS read-only 1225 STATUS current 1226 DESCRIPTION 1227 "The total number of messages received from the remote 1228 peer on this connection. This object should be 1229 initialized to zero when the connection is established." 1230 ::= { bgpPeerAfCountersEntry 3 } 1232 bgpPeerAfOutTotalMessages OBJECT-TYPE 1233 SYNTAX Counter32 1234 MAX-ACCESS read-only 1235 STATUS current 1236 DESCRIPTION 1237 "The total number of messages transmitted to the remote 1238 peer on this connection. This object should be 1239 initialized to zero when the connection is established." 1240 ::= { bgpPeerAfCountersEntry 4 } 1242 bgpPeerAfFsmEstablishedTrans OBJECT-TYPE 1243 SYNTAX Counter32 1244 MAX-ACCESS read-only 1245 STATUS current 1246 DESCRIPTION 1247 "The total number of times the BGP FSM transitioned into 1248 the established state for this peer." 1249 ::= { bgpPeerAfCountersEntry 5 } 1251 -- 1252 -- Per-Peer Prefix Counters 1253 -- 1255 bgpPrefixCountersTable OBJECT-TYPE 1256 SYNTAX SEQUENCE OF BgpPrefixCountersEntry 1257 MAX-ACCESS not-accessible 1258 STATUS current 1259 DESCRIPTION 1260 "Additional per-peer, per AFI-SAFI counters for 1261 prefixes" 1262 ::= { bgpPeerAfCounters 2 } 1264 bgpPrefixCountersEntry OBJECT-TYPE 1265 SYNTAX BgpPrefixCountersEntry 1266 MAX-ACCESS not-accessible 1267 STATUS current 1268 DESCRIPTION 1269 "Entry containing information about a bgp-peers prefix 1270 counters." 1271 INDEX { 1272 bgpPeerAfInstance, 1273 bgpPeerAfLocalAddrType, 1274 bgpPeerAfLocalAddr, 1275 bgpPeerAfRemoteAddrType, 1276 bgpPeerAfRemoteAddr, 1277 bgpPrefixCountersAfi, 1278 bgpPrefixCountersSafi 1279 } 1280 ::= { bgpPrefixCountersTable 1 } 1282 BgpPrefixCountersEntry ::= SEQUENCE { 1283 bgpPrefixCountersAfi 1284 BgpAfiTC, 1285 bgpPrefixCountersSafi 1286 BgpSafiTC, 1287 bgpPrefixInPrefixes 1288 Gauge32, 1289 bgpPrefixInPrefixesAccepted 1290 Gauge32, 1291 bgpPrefixOutPrefixes 1292 Gauge32 1293 } 1295 bgpPrefixCountersAfi OBJECT-TYPE 1296 SYNTAX BgpAfiTC 1297 MAX-ACCESS not-accessible 1298 STATUS current 1299 DESCRIPTION 1300 "The AFI index of the per-peer, per prefix counters" 1301 ::= { bgpPrefixCountersEntry 1 } 1303 bgpPrefixCountersSafi OBJECT-TYPE 1304 SYNTAX BgpSafiTC 1305 MAX-ACCESS not-accessible 1306 STATUS current 1307 DESCRIPTION 1308 "The SAFI index of the per-peer, per prefix counters" 1309 ::= { bgpPrefixCountersEntry 2 } 1311 bgpPrefixInPrefixes OBJECT-TYPE 1312 SYNTAX Gauge32 1313 MAX-ACCESS read-only 1314 STATUS current 1315 DESCRIPTION 1316 "The number of prefixes received from a peer and are 1317 stored in the Adj-Ribs-In for that peer. 1319 Note that this number does not reflect prefixes that 1320 have been discarded due to policy." 1321 ::= { bgpPrefixCountersEntry 3 } 1323 bgpPrefixInPrefixesAccepted OBJECT-TYPE 1324 SYNTAX Gauge32 1325 MAX-ACCESS read-only 1326 STATUS current 1327 DESCRIPTION 1328 "The number of prefixes for a peer that are installed 1329 in the Adj-Ribs-In and are eligible to become active 1330 in the Loc-Rib." 1331 ::= { bgpPrefixCountersEntry 4 } 1333 bgpPrefixOutPrefixes OBJECT-TYPE 1334 SYNTAX Gauge32 1335 MAX-ACCESS read-only 1336 STATUS current 1337 DESCRIPTION 1338 "The number of prefixes for a peer that are installed 1339 in that peer's Adj-Ribs-Out." 1340 ::= { bgpPrefixCountersEntry 5 } 1342 -- 1343 -- BGP NLRI Data 1344 -- 1346 bgpRib 1347 OBJECT IDENTIFIER ::= { bgp 11 } 1349 -- 1350 -- NLRI Table 1351 -- 1353 bgpNlriTable OBJECT-TYPE 1354 SYNTAX SEQUENCE OF BgpNlriEntry 1355 MAX-ACCESS not-accessible 1356 STATUS current 1357 DESCRIPTION 1358 "The BGP-4 Received Path Attribute Table contains 1359 information about paths to destination networks 1360 received from all BGP4 peers. Collectively, this 1361 represents the Adj-Ribs-In. The route where 1362 bgpNlriBest is true represents, for this NLRI, 1363 the route that is installed in the LocRib from the 1364 Adj-Ribs-In." 1365 ::= { bgpRib 1 } 1367 bgpNlriEntry OBJECT-TYPE 1368 SYNTAX BgpNlriEntry 1369 MAX-ACCESS not-accessible 1370 STATUS current 1371 DESCRIPTION 1372 "Information about a path to a network." 1373 INDEX { 1374 bgpNlriAfi, 1375 bgpNlriSafi, 1376 bgpNlriPrefix, 1377 bgpNlriPrefixLen, 1378 bgpNlriIndex, 1379 bgpPeerAfInstance, 1380 bgpPeerAfLocalAddrType, 1381 bgpPeerAfLocalAddr, 1382 bgpPeerAfRemoteAddrType, 1383 bgpPeerAfRemoteAddr 1384 } 1385 ::= { bgpNlriTable 1 } 1387 BgpNlriEntry ::= SEQUENCE { 1388 bgpNlriIndex 1389 Unsigned32, 1390 bgpNlriAfi 1391 BgpAfiTC, 1392 bgpNlriSafi 1393 BgpSafiTC, 1394 bgpNlriPrefixType 1395 InetAddressType, 1396 bgpNlriPrefix 1397 InetAddress, 1398 bgpNlriPrefixLen 1399 InetAddressPrefixLength, 1400 bgpNlriBest 1401 TruthValue, 1402 bgpNlriCalcLocalPref 1403 Unsigned32, 1404 bgpAfPathAttrIndex 1405 Unsigned32, 1406 bgpAfPathAttrUnknownIndex 1407 Unsigned32 1408 } 1410 bgpNlriIndex OBJECT-TYPE 1411 SYNTAX Unsigned32 1412 MAX-ACCESS not-accessible 1413 STATUS current 1414 DESCRIPTION 1415 "This index allows for multiple instances of a base 1416 prefix for a certain AFI-SAFI from a given peer. 1417 This is currently useful for two things: 1418 1. Allowing for a peer in future implementations to 1419 send more than a single route instance. 1420 2. Allow for extensions which extend the NLRI field 1421 to send the same prefix while utilizing other 1422 extension specific information. An example of 1423 this is RFC 3107 - Carrying MPLS labels in BGP." 1424 REFERENCE 1425 "RFC 3107 - Carrying Label Information in BGP-4." 1426 ::= { bgpNlriEntry 1 } 1428 bgpNlriAfi OBJECT-TYPE 1429 SYNTAX BgpAfiTC 1430 MAX-ACCESS not-accessible 1431 STATUS current 1432 DESCRIPTION 1433 "The address family of the prefix for this NLRI. 1435 Note that the AFI is not necessarily equivalent to 1436 the an InetAddressType." 1437 REFERENCE 1438 "RFC 4760 - Multiprotocol Extensions for BGP-4" 1439 ::= { bgpNlriEntry 2 } 1441 bgpNlriSafi OBJECT-TYPE 1442 SYNTAX BgpSafiTC 1443 MAX-ACCESS not-accessible 1444 STATUS current 1445 DESCRIPTION 1446 "The subsequent address family of the prefix for 1447 this NLRI" 1448 REFERENCE 1449 "RFC 4760 - Multiprotocol Extensions for BGP-4" 1450 ::= { bgpNlriEntry 3 } 1452 bgpNlriPrefixType OBJECT-TYPE 1453 SYNTAX InetAddressType 1454 MAX-ACCESS not-accessible 1455 STATUS current 1456 DESCRIPTION 1457 "The type of the IP address prefix in the 1458 Network Layer Reachability Information field. 1459 The value of this object is derived from the 1460 appropriate value from the bgpNlriAfi field. 1461 Where an appropriate InetAddressType is not 1462 available, the value of the object must be 1463 unknown(0)." 1464 ::= { bgpNlriEntry 4 } 1466 bgpNlriPrefix OBJECT-TYPE 1467 SYNTAX InetAddress (SIZE (4..20)) 1468 MAX-ACCESS not-accessible 1469 STATUS current 1470 DESCRIPTION 1471 "An IP address prefix in the Network Layer 1472 Reachability Information field. This object 1473 is an IP address containing the prefix with 1474 length specified by 1475 bgpAfPathAttrAddrPrefixLen. 1476 Any bits beyond the length specified by 1477 bgpAfPathAttrAddrPrefixLen are zeroed." 1478 REFERENCE 1479 "RFC 4271, Section 4.3." 1480 ::= { bgpNlriEntry 5 } 1482 bgpNlriPrefixLen OBJECT-TYPE 1483 SYNTAX InetAddressPrefixLength 1484 MAX-ACCESS not-accessible 1485 STATUS current 1486 DESCRIPTION 1487 "Length in bits of the address prefix in 1488 the Network Layer Reachability Information field." 1489 ::= { bgpNlriEntry 6 } 1491 bgpNlriBest OBJECT-TYPE 1492 SYNTAX TruthValue 1493 MAX-ACCESS read-only 1494 STATUS current 1495 DESCRIPTION 1496 "An indication of whether or not this route 1497 was chosen as the best BGP4 route for this 1498 destination." 1499 REFERENCE 1500 "RFC 4271, Section 9.1.2." 1501 ::= { bgpNlriEntry 7 } 1503 bgpNlriCalcLocalPref OBJECT-TYPE 1504 SYNTAX Unsigned32 1505 MAX-ACCESS read-only 1506 STATUS current 1507 DESCRIPTION 1508 "The degree of preference calculated by the 1509 receiving BGP4 speaker for an advertised 1510 route. 1512 In the case where this prefix is ineligible, this 1513 object will be absent." 1514 REFERENCE 1515 "RFC 4271, Section 9.1.1" 1516 ::= { bgpNlriEntry 8 } 1518 bgpAfPathAttrIndex OBJECT-TYPE 1519 SYNTAX Unsigned32 1520 MAX-ACCESS read-only 1521 STATUS current 1522 DESCRIPTION 1523 "This value is a unique index for entries in the 1524 bgpAfPathAttrTable. It is assigned by the agent at the 1525 point of creation of the bgpAfPathAttrTable row entry. 1526 While its value is guaranteed to be unique at any time, 1527 it is otherwise opaque to the management application 1528 with respect to its value or the contiguity of 1529 bgpAfPathAttrIndex row instance values across rows of the 1530 bgpAfPathAttrTable. 1532 Note well that this index is used to distinguish unique 1533 sets of Path Attributes sent as part of BGP NLRI. The 1534 implementor is thus encouraged to make this index unique 1535 per set of all received path attributes. This value may 1536 be used to index tables in extension MIBs that share the 1537 property of belonging to the same received Path Attribute 1538 tuple." 1539 ::= { bgpNlriEntry 9 } 1541 bgpAfPathAttrUnknownIndex OBJECT-TYPE 1542 SYNTAX Unsigned32 1543 MAX-ACCESS read-only 1544 STATUS current 1545 DESCRIPTION 1546 "This value is a unique index for entries in the 1547 bgpAfPathAttrUnknownTable. It is assigned by the agent at 1548 the point of creation of the bgpAfPathAttrUnknownTable row 1549 entry. While its value is guaranteed to be unique at 1550 any time, it is otherwise opaque to the management 1551 application with respect to its value or the contiguity 1552 of bgpAfPathAttrUnknownIndex row instance values across 1553 rows of the bgpAfPathAttrUnknownTable." 1554 ::= { bgpNlriEntry 10 } 1556 -- 1557 -- Adj-Ribs-Out Table 1558 -- 1560 bgpAdjRibsOutTable OBJECT-TYPE 1561 SYNTAX SEQUENCE OF BgpAdjRibsOutEntry 1562 MAX-ACCESS not-accessible 1563 STATUS current 1564 DESCRIPTION 1565 "This table contains on a per-peer basis one or more 1566 routes from the bgpNlriTable that have been 1567 placed in this peer's Adj-Ribs-Out." 1568 REFERENCE 1569 "RFC 4271, Section 3.2." 1570 ::= { bgpRib 2 } 1572 bgpAdjRibsOutEntry OBJECT-TYPE 1573 SYNTAX BgpAdjRibsOutEntry 1574 MAX-ACCESS not-accessible 1575 STATUS current 1576 DESCRIPTION 1577 "List of BGP routes that have been placed into a 1578 peer's Adj-Ribs-Out." 1579 INDEX { 1580 bgpPeerAfInstance, 1581 bgpPeerAfLocalAddrType, 1582 bgpPeerAfLocalAddr, 1583 bgpPeerAfRemoteAddrType, 1584 bgpPeerAfRemoteAddr, 1585 bgpNlriAfi, 1586 bgpNlriSafi, 1587 bgpNlriPrefix, 1588 bgpNlriPrefixLen, 1589 bgpAdjRibsOutIndex 1590 } 1591 ::= { bgpAdjRibsOutTable 1 } 1593 BgpAdjRibsOutEntry ::= SEQUENCE { 1594 bgpAdjRibsOutIndex 1595 Unsigned32, 1596 bgpAdjRibsOutRoute 1597 RowPointer 1598 } 1600 bgpAdjRibsOutIndex OBJECT-TYPE 1601 SYNTAX Unsigned32 1602 MAX-ACCESS not-accessible 1603 STATUS current 1604 DESCRIPTION 1605 "Certain extensions to BGP permit multiple instance of 1606 a per afi, per safi prefix to be advertised to a peer. 1607 This object allows the enumeration of them." 1608 ::= { bgpAdjRibsOutEntry 1 } 1610 bgpAdjRibsOutRoute OBJECT-TYPE 1611 SYNTAX RowPointer 1612 MAX-ACCESS read-only 1613 STATUS current 1614 DESCRIPTION 1615 "This object points to the route in the bgpNlriTable 1616 that corresponds to the entry in the peer's 1617 Adj-Rib-Out. Outgoing route maps are not 1618 reflected at this point as those are part of the 1619 Update-Send process." 1620 REFERENCE 1621 "RFC 4271, Section 9.2." 1622 ::= { bgpAdjRibsOutEntry 2 } 1624 -- 1625 -- Path Attribute Counter 1626 -- 1628 bgpAfPathAttrCount OBJECT-TYPE 1629 SYNTAX Counter32 1630 MAX-ACCESS read-only 1631 STATUS current 1632 DESCRIPTION 1633 "The number of entries in the bgpAfPathAttrTable." 1634 ::= { bgpRib 3 } 1636 -- 1637 -- Path Attributes Table 1638 -- 1640 bgpAfPathAttrTable OBJECT-TYPE 1641 SYNTAX SEQUENCE OF BgpAfPathAttrEntry 1642 MAX-ACCESS not-accessible 1643 STATUS current 1644 DESCRIPTION 1645 "Provides per advertised network-prefix attribute data, 1646 as advertised over a peering session." 1647 ::= { bgpRib 4 } 1649 bgpAfPathAttrEntry OBJECT-TYPE 1650 SYNTAX BgpAfPathAttrEntry 1651 MAX-ACCESS not-accessible 1652 STATUS current 1653 DESCRIPTION 1654 "Each entry contains data about path attributes 1655 associated with a given prefix in the bgpNlriTable." 1656 REFERENCE 1657 "RFC 4271, Section 5." 1658 INDEX { 1659 bgpAfPathAttrIndex 1660 } 1661 ::= { bgpAfPathAttrTable 1 } 1663 BgpAfPathAttrEntry ::= SEQUENCE { 1664 bgpAfPathAttrOrigin 1665 INTEGER, 1666 bgpAfPathAttrNextHopAddrType 1667 InetAddressType, 1668 bgpAfPathAttrNextHop 1669 InetAddress, 1670 bgpAfPathAttrLinkLocalNextHop 1671 InetAddress, 1672 bgpAfPathAttrMedPresent 1673 TruthValue, 1674 bgpAfPathAttrMed 1675 Unsigned32, 1676 bgpAfPathAttrLocalPref 1677 Unsigned32, 1678 bgpAfPathAttrAtomicAggregate 1679 INTEGER, 1680 bgpAfPathAttrAggregatorAS 1681 InetAutonomousSystemNumber, 1682 bgpAfPathAttrAggregatorAddr 1683 BgpIdentifierTC, 1684 bgpAsPathCalcLength 1685 Unsigned32, 1686 bgpAsPathIndex 1687 Unsigned32, 1688 bgpAsPathString 1689 SnmpAdminString 1690 } 1692 bgpAfPathAttrOrigin OBJECT-TYPE 1693 SYNTAX INTEGER { 1694 igp(1),-- networks are interior 1695 egp(2),-- networks learned via the EGP protocol 1696 incomplete(3) -- networks that 1697 -- are learned by some other 1698 -- means 1699 } 1700 MAX-ACCESS read-only 1701 STATUS current 1702 DESCRIPTION 1703 "The ultimate origin of the path information." 1704 REFERENCE 1705 "RFC 4271, Section 4.3. 1706 RFC 4271, Section 5.1.1." 1708 ::= { bgpAfPathAttrEntry 1 } 1710 bgpAfPathAttrNextHopAddrType OBJECT-TYPE 1711 SYNTAX InetAddressType 1712 MAX-ACCESS read-only 1713 STATUS current 1714 DESCRIPTION 1715 "The address family of the address for 1716 the border router that should be used 1717 to access the destination network." 1718 ::= { bgpAfPathAttrEntry 2 } 1720 bgpAfPathAttrNextHop OBJECT-TYPE 1721 SYNTAX InetAddress (SIZE(4..20)) 1722 MAX-ACCESS read-only 1723 STATUS current 1724 DESCRIPTION 1725 "The address of the border router that 1726 should be used to access the destination 1727 network. This address is the nexthop 1728 address received in the UPDATE packet associated with 1729 this prefix. 1731 Note that for RFC2545 style double nexthops, 1732 this object will always contain the global scope 1733 nexthop. bgpPathAttrLinkLocalNextHop will contain 1734 the linklocal scope nexthop, if it is present. 1736 In the case a mechanism is developed to use only a link 1737 local nexthop, bgpAfPathAttrNextHop will contain the 1738 link local nexthop." 1739 REFERENCE 1740 "RFC 4271, Section 4.3, 1741 RFC 4271, Section 5.1.3, 1742 RFC 2545, Section 3." 1743 ::= { bgpAfPathAttrEntry 3 } 1745 bgpAfPathAttrLinkLocalNextHop OBJECT-TYPE 1746 SYNTAX InetAddress (SIZE(20)) 1747 MAX-ACCESS read-only 1748 STATUS current 1749 DESCRIPTION 1750 "This value contains an IPv6 link local address of 1751 InetAddressType of type ipv6z and is present only when 1752 receiving RFC 2545 style double nexthops. 1754 This object is optionally present in BGP 1755 implementations that do not support IPv6." 1757 REFERENCE 1758 "RFC 2545, Section 3." 1759 ::= { bgpAfPathAttrEntry 4 } 1761 bgpAfPathAttrMedPresent OBJECT-TYPE 1762 SYNTAX TruthValue 1763 MAX-ACCESS read-only 1764 STATUS current 1765 DESCRIPTION 1766 "Whether or not the MED value was sent in the UPDATE 1767 message." 1768 ::= { bgpAfPathAttrEntry 5 } 1770 bgpAfPathAttrMed OBJECT-TYPE 1771 SYNTAX Unsigned32 1772 MAX-ACCESS read-only 1773 STATUS current 1774 DESCRIPTION 1775 "This metric is used to discriminate between multiple 1776 exit points to an adjacent autonomous system. When the MED 1777 value is absent but has a calculated default value, this 1778 object will contain the calculated value." 1779 REFERENCE 1780 "RFC 4271, Section 4.3. 1781 RFC 4271, Section 5.1.4." 1782 ::= { bgpAfPathAttrEntry 6 } 1784 bgpAfPathAttrLocalPref OBJECT-TYPE 1785 SYNTAX Unsigned32 1786 MAX-ACCESS read-only 1787 STATUS current 1788 DESCRIPTION 1789 "The originating BGP4 speakers degree of preference for an 1790 advertised route. If the route was not sent with a LOCAL_PREF 1791 value, this object will be absent." 1792 REFERENCE 1793 "RFC 4271, Section 4.3. 1794 RFC 4271, Section 5.1.5." 1795 ::= { bgpAfPathAttrEntry 7 } 1797 bgpAfPathAttrAtomicAggregate OBJECT-TYPE 1798 SYNTAX INTEGER { 1799 atomicAggregatePresent(1), 1800 atomicAggregateMissing(2) 1801 } 1802 MAX-ACCESS read-only 1803 STATUS current 1804 DESCRIPTION 1805 "When this object is set to atomicAggregatePresent, 1806 the ATOMIC_AGGREGATE Path Attribute is present and 1807 indicates that the NLRI MUST NOT be made more 1808 specific." 1809 REFERENCE 1810 "RFC 4271, Sections 5.1.6 and 9.1.4." 1811 ::= { bgpAfPathAttrEntry 8 } 1813 bgpAfPathAttrAggregatorAS OBJECT-TYPE 1814 SYNTAX InetAutonomousSystemNumber 1815 MAX-ACCESS read-only 1816 STATUS current 1817 DESCRIPTION 1818 "The AS number of the last BGP4 speaker that performed route 1819 aggregation. If the AGGREGATOR path attribute is absent, this 1820 object will not be present in the conceptual row." 1821 REFERENCE 1822 "RFC 4271, Section 5.1.7. 1823 RFC 4271, Section 9.2.2.2." 1824 ::= { bgpAfPathAttrEntry 9 } 1826 bgpAfPathAttrAggregatorAddr OBJECT-TYPE 1827 SYNTAX BgpIdentifierTC 1828 MAX-ACCESS read-only 1829 STATUS current 1830 DESCRIPTION 1831 "The IP address of the last BGP4 speaker that performed route 1832 aggregation. If the AGGREGATOR path attribute is absent, this 1833 object will not be present in the conceptual row." 1834 REFERENCE 1835 "RFC 4271, Section 5.1.7. 1836 RFC 4271, Section 9.2.2.2." 1837 ::= { bgpAfPathAttrEntry 10 } 1839 bgpAsPathCalcLength OBJECT-TYPE 1840 SYNTAX Unsigned32 1841 MAX-ACCESS read-only 1842 STATUS current 1843 DESCRIPTION 1844 "This value represents the calculated length of the 1845 AS Path according to the rules of the BGP 1846 specification. This value is used in route selection." 1847 REFERENCE 1848 "RFC 4271, Section 9.1.2.2.a" 1849 ::= { bgpAfPathAttrEntry 11 } 1851 bgpAsPathIndex OBJECT-TYPE 1852 SYNTAX Unsigned32 1853 MAX-ACCESS read-only 1854 STATUS current 1855 DESCRIPTION 1856 "This value is a unique index for the decomposed AS Path 1857 in the bgpAsPathTable. It is assigned by the 1858 agent at the point of creation of the bgpAsPathTable 1859 row entry. While its value is guaranteed to be unique 1860 at any time, it is otherwise opaque to the management 1861 application with respect to its value or the contiguity 1862 of bgpAsPathIndex row instance values across rows 1863 of the bgpAsPathTable." 1864 ::= { bgpAfPathAttrEntry 12 } 1866 bgpAsPathString OBJECT-TYPE 1867 SYNTAX SnmpAdminString 1868 MAX-ACCESS read-only 1869 STATUS current 1870 DESCRIPTION 1871 "This is a string depicting the autonomous system 1872 path to this network which was received from the 1873 peer which advertised it. The format of the string 1874 is implementation-dependent, and should be designed 1875 for operator readability. 1877 Note that SnmpAdminString is only capable of 1878 representing a maximum of 255 characters. This may 1879 lead to the string being truncated in the presence of 1880 a large AS Path. The bgpAsPathTable will give access 1881 to the full AS Path." 1882 ::= { bgpAfPathAttrEntry 13 } 1884 -- 1885 -- BGP 4 AS_PATH. This table provides a platform netrual 1886 -- representation of the AS_PATH. 1887 -- 1889 bgpAsPathTable OBJECT-TYPE 1890 SYNTAX SEQUENCE OF BgpAsPathEntry 1891 MAX-ACCESS not-accessible 1892 STATUS current 1893 DESCRIPTION 1894 "The BGP-4 Path Attribute AS Path Table 1895 contains the per network path (NLRI) 1896 AS PATH data received from the 1897 advertising BGP peer. 1899 Note that the bgpAsPathElementValue is 4-byte AS capable. This 1900 table and related objects in this MIB are meant to reflect the 1901 active AS_PATH for a 2-byte or a 4-byte AS speaker. For a 1902 transitional 2-byte to 4-byte speaker, the received AS_PATH and 1903 AS4_PATH path attributes may be present in an extension MIB." 1904 REFERENCE 1905 "RFC 4271, Sections 4.3 and 5.1.2. 1906 RFC 4893, BGP Support for Four-octet AS Number Space" 1907 ::= { bgpRib 6 } 1909 bgpAsPathTableEntry OBJECT-TYPE 1910 SYNTAX BgpAsPathEntry 1911 MAX-ACCESS not-accessible 1912 STATUS current 1913 DESCRIPTION 1914 "Information about an AS path provided with a path to 1915 a network." 1916 INDEX { 1917 bgpAsPathIndex, 1918 bgpAsPathSegmentIndex, 1919 bgpAsPathElementIndex 1920 } 1921 ::= { bgpAsPathTable 1 } 1923 BgpAsPathEntry ::= SEQUENCE { 1924 bgpAsPathSegmentIndex 1925 Unsigned32, 1926 bgpAsPathElementIndex 1927 Unsigned32, 1928 bgpAsPathType 1929 INTEGER, 1930 bgpAsPathElementValue 1931 InetAutonomousSystemNumber 1932 } 1934 bgpAsPathSegmentIndex OBJECT-TYPE 1935 SYNTAX Unsigned32 1936 MAX-ACCESS not-accessible 1937 STATUS current 1938 DESCRIPTION 1939 "A per-AS path segment index. This will index a set of 1940 autonomous systems in an AS path which are part 1941 of the same sequence or set (as determined by 1942 the row value of bgpAsPathType, which 1943 should be the same value for each bgpAsPathTable 1944 entry indexed by the same bgpAsPathIndex." 1945 REFERENCE 1946 "RFC 4271, Sections 4.3 and 5.1.2." 1947 ::= { bgpAsPathTableEntry 1 } 1949 bgpAsPathElementIndex OBJECT-TYPE 1950 SYNTAX Unsigned32 1951 MAX-ACCESS not-accessible 1952 STATUS current 1953 DESCRIPTION 1954 "A per-AS element index. This will index a particular 1955 AS within a sequence or set of autonomous systems in 1956 an AS path." 1957 REFERENCE 1958 "RFC 4271, Sections 4.3 and 5.1.2." 1959 ::= { bgpAsPathTableEntry 2 } 1961 bgpAsPathType OBJECT-TYPE 1962 SYNTAX INTEGER { 1963 asSet(1), 1964 asSequence(2), 1965 confedSequence(3), 1966 confedSet(4) 1967 } 1968 MAX-ACCESS read-only 1969 STATUS current 1970 DESCRIPTION 1971 "The path segment type advertised for the per-AS element. 1972 Note that all asPath row instances for a given 1973 bgpAsPathIndex index will have their 1974 bgpAsPathType set to the same value. 1975 The values for bgpAsPathType are 1976 interpreted as defined in the base BGP document 1977 and the BGP AS Confederations document." 1978 REFERENCE 1979 "RFC 4271, Sections 4.3 and 5.1.2, 1980 RFC 5065 - BGP AS Confederations" 1981 ::= { bgpAsPathTableEntry 3 } 1983 bgpAsPathElementValue OBJECT-TYPE 1984 SYNTAX InetAutonomousSystemNumber 1985 MAX-ACCESS read-only 1986 STATUS current 1987 DESCRIPTION 1988 "An AS the NLRI traversed in the propagation of its 1989 advertisement. This value is to be interpreted in 1990 the context of the segment type of the bgpAsPathType 1991 in the same conceptual row." 1992 ::= { bgpAsPathTableEntry 4 } 1994 -- BGP 4 Path unknown attribute. There is one row in 1995 -- this table for each attribute not known by this BGP 1996 -- implementation (or agent instrumentation), but provided 1997 -- from a peer. 1999 bgpAfPathAttrUnknownTable OBJECT-TYPE 2000 SYNTAX SEQUENCE OF BgpAfPathAttrUnknownEntry 2001 MAX-ACCESS not-accessible 2002 STATUS current 2003 DESCRIPTION 2004 "The BGP-4 Path Attribute Unknown Table 2005 contains the per network path (NLRI) 2006 data on the path attributes advertised 2007 with a route but not known to the local BGP 2008 implementation or not otherwise capable of being 2009 returned from this agent. 2011 The absence of row data for a given index value for 2012 bgpAfPathAttrIndex indicates a lack of such unknown 2013 attribute information for the indicated network path 2014 (as indexed by that bgpAfPathAttrIndex value in the 2015 bgpAfPathAttrTable)." 2016 REFERENCE 2017 "RFC 4271, Sections 4.3 and 5." 2018 ::= { bgpRib 7 } 2020 bgpAfPathAttrUnknownEntry OBJECT-TYPE 2021 SYNTAX BgpAfPathAttrUnknownEntry 2022 MAX-ACCESS not-accessible 2023 STATUS current 2024 DESCRIPTION 2025 "Information about an unknown attribute 2026 provided with a path to a network." 2027 INDEX { 2028 bgpAfPathAttrUnknownIndex, 2029 bgpAfPathAttrUnknownCode 2030 } 2031 ::= { bgpAfPathAttrUnknownTable 1 } 2033 BgpAfPathAttrUnknownEntry ::= SEQUENCE { 2034 bgpAfPathAttrUnknownCode 2035 Unsigned32, 2036 bgpAfPathAttrUnknownFlags 2037 OCTET STRING, 2038 bgpAfPathAttrUnknownValue 2039 OCTET STRING 2040 } 2042 bgpAfPathAttrUnknownCode OBJECT-TYPE 2043 SYNTAX Unsigned32 2044 MAX-ACCESS not-accessible 2045 STATUS current 2046 DESCRIPTION 2047 "The path attribute code advertised with this unknown 2048 attribute by the peer." 2049 ::= { bgpAfPathAttrUnknownEntry 1 } 2051 -- Maximum size of the following is derived as 2052 -- 4096 max message size 2053 -- - 16 BGP message marker bytes 2054 -- - 2 BGP message size 2055 -- - 1 BGP message type (UPDATE with unknown attr) 2056 -- - 2 UPDATE routes length (even assuming no routes) 2057 -- - 2 UPDATE path attributes length 2058 -- - 1 path attribute flag octet 2059 -- - 2 unknown path attr type (in bgpAfPathAttrUnknownCode) 2060 -- --------- 2061 -- 4070 bytes maximum per-message attribute value data 2063 bgpAfPathAttrUnknownFlags OBJECT-TYPE 2064 SYNTAX BgpPathAttrFlagsTC 2065 MAX-ACCESS read-only 2066 STATUS current 2067 DESCRIPTION 2068 "The flags of the unknown path attribute." 2069 ::= { bgpAfPathAttrUnknownEntry 2 } 2071 bgpAfPathAttrUnknownValue OBJECT-TYPE 2072 SYNTAX OCTET STRING (SIZE(0..4070)) 2073 MAX-ACCESS read-only 2074 STATUS current 2075 DESCRIPTION 2076 "Value of path attribute not understood 2077 by the base BGP-4 document. 2079 Per RFC 2578, Section 7.1.2, some implementations 2080 may have limitations dealing with OCTET STRINGS 2081 larger than 255. Thus, this data may be truncated. 2083 Octets beyond the maximum size, if any, 2084 are not recorded by this row object." 2085 ::= { bgpAfPathAttrUnknownEntry 3 } 2087 -- 2088 -- Mount point for extensions 2089 -- 2091 bgpExtensions OBJECT IDENTIFIER ::= { bgp 12 } 2092 -- 2093 -- Notifications 2094 -- 2096 bgpNotification OBJECT IDENTIFIER ::= { bgp 0 } 2098 -- bgpNotification 1 and 2 have been deprecated and are 2099 -- documented elsewhere in this MIB 2101 bgpAfEstablishedNotification NOTIFICATION-TYPE 2102 OBJECTS { 2103 bgpPeerAfPeerState, 2104 bgpPeerAfLocalPort, 2105 bgpPeerAfRemotePort 2106 } 2107 STATUS current 2108 DESCRIPTION 2109 "The BGP Established event is generated when 2110 the BGP FSM enters the established state." 2111 ::= { bgpNotification 3 } 2113 bgpAfBackwardTransNotification NOTIFICATION-TYPE 2114 OBJECTS { 2115 bgpPeerAfPeerState, 2116 bgpPeerAfLocalPort, 2117 bgpPeerAfRemotePort, 2118 bgpPeerAfLastErrorReceived, 2119 bgpPeerAfLastErrorReceivedText 2120 } 2121 STATUS current 2122 DESCRIPTION 2123 "The BGPBackwardTransition Event is generated 2124 when the BGP FSM moves from a higher numbered 2125 state to a lower numbered state. 2127 Due to the nature of the BGP state machine, an implementation MAY 2128 rate limit the generation of this event. An implementation MAY 2129 also generate this notification ONLY when the state machine moves 2130 out of the established state. An implementation should document 2131 its specific behavior." 2132 ::= { bgpNotification 4 } 2134 -- 2135 -- Conformance Information 2136 -- 2138 bgpConformance 2139 OBJECT IDENTIFIER ::= { bgp 8 } 2141 bgp4MIBCompliances OBJECT IDENTIFIER ::= 2142 { bgpConformance 1 } 2144 bgp4MIBGroups OBJECT IDENTIFIER ::= 2145 { bgpConformance 2 } 2147 -- bgp4MIBCompliances 1 through 3 have been deprecated and are 2148 -- documented elsewhere in this MIB. 2150 bgpAfMIBCompliance MODULE-COMPLIANCE 2151 STATUS current 2152 DESCRIPTION 2153 "The compliance statement for entities which 2154 implement the BGP4 mib." 2155 MODULE -- this module 2156 MANDATORY-GROUPS { 2157 bgpTimersGroup, 2158 bgpCountersGroup, 2159 bgpAsPathGroup, 2160 bgpBaseGroup, 2161 bgpErrorsGroup, 2162 bgpPeerAfGroup, 2163 bgpAfPathAttributesGroup 2164 } 2165 GROUP bgpAfMIBGlobalsGroup 2166 DESCRIPTION 2167 "This group is mandatory for all agent implementations." 2168 GROUP bgpTimersGroup 2169 DESCRIPTION 2170 "This group is mandatory for all agent implementations." 2171 GROUP bgpCountersGroup 2172 DESCRIPTION 2173 "This group is mandatory for all agent implementations." 2174 GROUP bgpAsPathGroup 2175 DESCRIPTION 2176 "This group is mandatory for all agent implementations." 2177 GROUP bgpBaseGroup 2178 DESCRIPTION 2179 "This group is mandatory for all agent implementations." 2180 GROUP bgpErrorsGroup 2181 DESCRIPTION 2182 "This group is mandatory for all agent implementations." 2183 GROUP bgpPeerAfGroup 2184 DESCRIPTION 2185 "This group is mandatory for all agent implementations." 2186 GROUP bgpAfPathAttributesGroup 2187 DESCRIPTION 2188 "This group is mandatory for all agent implementations." 2190 GROUP bgpAfMIBNotificationGroup 2191 DESCRIPTION 2192 "Implementation of BGP Notifications are completely 2193 optional in this MIB." 2194 ::= { bgp4MIBCompliances 4 } 2196 bgpAfMIBDeprecatedCompliances MODULE-COMPLIANCE 2197 STATUS deprecated 2198 DESCRIPTION 2199 "The compliance statement for entities which 2200 implement the BGP4 mib." 2201 MODULE -- this module 2202 GROUP bgpAfMIBOldGlobalsGroup 2203 DESCRIPTION 2204 "Implementation of the bgp4MIBGlobalsGroup is OPTIONAL. 2205 If it is implemented, then bgp4MIBGlobalsGroup, 2206 bgp4MIBPeerGroup, bgp4MIBPathAttrGroup and 2207 bgp4MIBNotificationGroup MUST all be implemented." 2208 GROUP bgp4MIBPeerGroup 2209 DESCRIPTION 2210 "Implementation of the bgp4MIBPeerGroup is OPTIONAL. 2211 If it is implemented, then bgp4MIBGlobalsGroup, 2212 bgp4MIBPeerGroup, bgp4MIBPathAttrGroup and 2213 bgp4MIBNotificationGroup MUST all be implemented." 2214 GROUP bgp4MIBPathAttrGroup 2215 DESCRIPTION 2216 "Implementation of the bgp4MIBPathAttrGroup is OPTIONAL. 2217 If it is implemented, then bgp4MIBGlobalsGroup, 2218 bgp4MIBPeerGroup, bgp4MIBPathAttrGroup and 2219 bgp4MIBNotificationGroup MUST all be implemented." 2220 GROUP bgp4MIBNotificationGroup 2221 DESCRIPTION 2222 "Implementation of the bgp4MIBNotificationGroup is OPTIONAL. 2223 If it is implemented, then bgp4MIBGlobalsGroup, 2224 bgp4MIBPeerGroup, bgp4MIBPathAttrGroup and 2225 bgp4MIBNotificationGroup MUST all be implemented." 2226 ::= { bgp4MIBCompliances 5 } 2228 -- bgp4MIBGroups 1 through 7 have been deprecated and are documented 2229 -- elsewhere in this MIB. 2231 bgpAfMIBGlobalsGroup OBJECT-GROUP 2232 OBJECTS { bgpVersion, 2233 bgpIdentifier } 2234 STATUS current 2235 DESCRIPTION 2236 "A collection of objects providing information on global 2237 BGP state. This group covers objects that overlap the 2238 old bgp4MIBGlobalsGroup that are still current." 2239 ::= { bgp4MIBGroups 8 } 2241 bgpAfMIBOldGlobalsGroup OBJECT-GROUP 2242 OBJECTS { bgpLocalAs } 2243 STATUS deprecated 2244 DESCRIPTION 2245 "A collection of objects providing information on global 2246 BGP state. This group covers objects that overlap the 2247 old bgp4MIBGlobalsGroup that are deprecated." 2248 ::= { bgp4MIBGroups 9 } 2250 bgpTimersGroup OBJECT-GROUP 2251 OBJECTS { 2252 bgpPeerAfFsmEstablishedTime, 2253 bgpPeerAfInUpdatesElapsedTime, 2254 bgpPeerAfConnectRetryInterval, 2255 bgpPeerAfHoldTimeConfigured, 2256 bgpPeerAfKeepAliveConfigured, 2257 bgpPeerAfMinASOrigInterval, 2258 bgpPeerAfMinRouteAdverInterval, 2259 bgpPeerAfHoldTime, 2260 bgpPeerAfKeepAlive 2261 } 2262 STATUS current 2263 DESCRIPTION 2264 "Objects associated with BGP peering timers." 2265 ::= { bgp4MIBGroups 10 } 2267 bgpCountersGroup OBJECT-GROUP 2268 OBJECTS { 2269 bgpPeerAfInUpdates, 2270 bgpPeerAfOutUpdates, 2271 bgpPeerAfInTotalMessages, 2272 bgpPeerAfOutTotalMessages, 2273 bgpPeerAfFsmEstablishedTrans, 2274 bgpPrefixInPrefixes, 2275 bgpPrefixInPrefixesAccepted, 2276 bgpPrefixOutPrefixes 2277 } 2278 STATUS current 2279 DESCRIPTION 2280 "Objects to count discrete events and exchanges on BGP 2281 sessions." 2282 ::= { bgp4MIBGroups 11 } 2284 bgpAsPathGroup OBJECT-GROUP 2285 OBJECTS { 2286 bgpAsPathType, 2287 bgpAsPathElementValue 2288 } 2289 STATUS current 2290 DESCRIPTION 2291 "Objects to report AS paths received on BGP NLRIs." 2292 ::= { bgp4MIBGroups 12 } 2294 bgpBaseGroup OBJECT-GROUP 2295 OBJECTS { 2296 bgpLocalAsNew 2297 } 2298 STATUS current 2299 DESCRIPTION 2300 "Basic objects in local BGP implementation." 2301 ::= { bgp4MIBGroups 13 } 2303 bgpErrorsGroup OBJECT-GROUP 2304 OBJECTS { 2305 bgpPeerAfLastErrorReceived, 2306 bgpPeerAfLastErrorReceivedData, 2307 bgpPeerAfLastErrorReceivedTime, 2308 bgpPeerAfLastErrorReceivedText, 2309 bgpPeerAfLastErrorSent, 2310 bgpPeerAfLastErrorSentData, 2311 bgpPeerAfLastErrorSentTime, 2312 bgpPeerAfLastErrorSentText 2313 } 2314 STATUS current 2315 DESCRIPTION 2316 "Errors received on BGP peering sessions." 2317 ::= { bgp4MIBGroups 14 } 2319 bgpPeerAfGroup OBJECT-GROUP 2320 OBJECTS { 2321 bgpPeerAfIdentifier, 2322 bgpPeerAfPeerState, 2323 bgpPeerAfAdminStatus, 2324 bgpPeerAfConfiguredVersion, 2325 bgpPeerAfNegotiatedVersion, 2326 bgpPeerAfLocalPort, 2327 bgpPeerAfLocalAs, 2328 bgpPeerAfRemotePort, 2329 bgpPeerAfRemoteAs 2330 } 2331 STATUS current 2332 DESCRIPTION 2333 "Core object types on BGP peering sessions." 2335 ::= { bgp4MIBGroups 15 } 2337 bgpAfPathAttributesGroup OBJECT-GROUP 2338 OBJECTS { 2339 bgpAfPathAttrCount, 2340 bgpAsPathCalcLength, 2341 bgpAsPathElementValue, 2342 bgpAsPathIndex, 2343 bgpAsPathString, 2344 bgpAsPathType, 2345 bgpNlriBest, 2346 bgpNlriCalcLocalPref, 2347 bgpAdjRibsOutRoute, 2348 bgpAfPathAttrAggregatorAS, 2349 bgpAfPathAttrAggregatorAddr, 2350 bgpAfPathAttrAtomicAggregate, 2351 bgpAfPathAttrIndex, 2352 bgpAfPathAttrLocalPref, 2353 bgpAfPathAttrMed, 2354 bgpAfPathAttrMedPresent, 2355 bgpAfPathAttrNextHop, 2356 bgpAfPathAttrNextHopAddrType, 2357 bgpAfPathAttrLinkLocalNextHop, 2358 bgpAfPathAttrOrigin, 2359 bgpAfPathAttrUnknownIndex, 2360 bgpAfPathAttrUnknownFlags, 2361 bgpAfPathAttrUnknownValue 2362 } 2363 STATUS current 2364 DESCRIPTION 2365 "Attributes received on BGP peering sessions." 2366 ::= { bgp4MIBGroups 16 } 2368 -- ========================================================= 2369 -- 2370 -- Objects that are deprecated from RFC 4273 follow below. 2371 -- 2372 -- ========================================================= 2374 bgpLocalAs OBJECT-TYPE 2375 SYNTAX Integer32 (0..65535) 2376 MAX-ACCESS read-only 2377 STATUS deprecated 2378 DESCRIPTION 2379 "The local autonomous system number. 2381 This object has been replaced with bgpLocalAsNew 2382 which can accomodate 4-byte AS numbers. When 2383 the Local AS number cannot be represented by 2384 a 2-byte number, this object should return the 2385 AS_TRANS value, 23456." 2386 REFERENCE 2387 "RFC 4271, Section 4.2, 'My Autonomous System'. 2389 RFC 4893, BGP Support for Four-octet AS Number 2390 Space." 2391 ::= { bgp 2 } 2393 -- BGP Peer table. This table contains, one entry per 2394 -- BGP peer, information about the BGP peer. 2396 bgpPeerTable OBJECT-TYPE 2397 SYNTAX SEQUENCE OF BgpPeerEntry 2398 MAX-ACCESS not-accessible 2399 STATUS deprecated 2400 DESCRIPTION 2401 "BGP peer table. This table contains, 2402 one entry per BGP peer, information about the 2403 connections with BGP peers. 2405 This table has been replaced with BgpPeerAfTable." 2406 ::= { bgp 3 } 2408 bgpPeerEntry OBJECT-TYPE 2409 SYNTAX BgpPeerEntry 2410 MAX-ACCESS not-accessible 2411 STATUS deprecated 2412 DESCRIPTION 2413 "Entry containing information about the 2414 connection with a BGP peer." 2415 INDEX { bgpPeerRemoteAddr } 2416 ::= { bgpPeerTable 1 } 2418 BgpPeerEntry ::= SEQUENCE { 2419 bgpPeerIdentifier 2420 IpAddress, 2421 bgpPeerState 2422 INTEGER, 2423 bgpPeerAdminStatus 2424 INTEGER, 2425 bgpPeerNegotiatedVersion 2426 Integer32, 2427 bgpPeerLocalAddr 2428 IpAddress, 2429 bgpPeerLocalPort 2430 Integer32, 2431 bgpPeerRemoteAddr 2432 IpAddress, 2433 bgpPeerRemotePort 2434 Integer32, 2435 bgpPeerRemoteAs 2436 Integer32, 2437 bgpPeerInUpdates 2438 Counter32, 2439 bgpPeerOutUpdates 2440 Counter32, 2441 bgpPeerInTotalMessages 2442 Counter32, 2443 bgpPeerOutTotalMessages 2444 Counter32, 2445 bgpPeerLastError 2446 OCTET STRING, 2447 bgpPeerFsmEstablishedTransitions 2448 Counter32, 2449 bgpPeerFsmEstablishedTime 2450 Gauge32, 2451 bgpPeerConnectRetryInterval 2452 Integer32, 2453 bgpPeerHoldTime 2454 Integer32, 2455 bgpPeerKeepAlive 2456 Integer32, 2457 bgpPeerHoldTimeConfigured 2458 Integer32, 2459 bgpPeerKeepAliveConfigured 2460 Integer32, 2461 bgpPeerMinASOriginationInterval 2462 Integer32, 2463 bgpPeerMinRouteAdvertisementInterval 2464 Integer32, 2465 bgpPeerInUpdateElapsedTime 2466 Gauge32 2467 } 2469 bgpPeerIdentifier OBJECT-TYPE 2470 SYNTAX IpAddress 2471 MAX-ACCESS read-only 2472 STATUS deprecated 2473 DESCRIPTION 2474 "The BGP Identifier of this entry's BGP peer. 2475 This entry MUST be 0.0.0.0 unless the 2476 bgpPeerState is in the openconfirm or the 2477 established state." 2479 REFERENCE 2480 "RFC 4271, Section 4.2, 'BGP Identifier'." 2481 ::= { bgpPeerEntry 1 } 2483 bgpPeerState OBJECT-TYPE 2484 SYNTAX INTEGER { 2485 idle(1), 2486 connect(2), 2487 active(3), 2488 opensent(4), 2489 openconfirm(5), 2490 established(6) 2491 } 2492 MAX-ACCESS read-only 2493 STATUS deprecated 2494 DESCRIPTION 2495 "The BGP peer connection state." 2496 REFERENCE 2497 "RFC 4271, Section 8.2.2." 2498 ::= { bgpPeerEntry 2 } 2500 bgpPeerAdminStatus OBJECT-TYPE 2501 SYNTAX INTEGER { 2502 stop(1), 2503 start(2) 2504 } 2505 MAX-ACCESS read-write 2506 STATUS deprecated 2507 DESCRIPTION 2508 "The desired state of the BGP connection. 2509 A transition from 'stop' to 'start' will cause 2510 the BGP Manual Start Event to be generated. 2511 A transition from 'start' to 'stop' will cause 2512 the BGP Manual Stop Event to be generated. 2513 This parameter can be used to restart BGP peer 2514 connections. Care should be used in providing 2515 write access to this object without adequate 2516 authentication." 2517 REFERENCE 2518 "RFC 4271, Section 8.1.2." 2519 ::= { bgpPeerEntry 3 } 2521 bgpPeerNegotiatedVersion OBJECT-TYPE 2522 SYNTAX Integer32 2523 MAX-ACCESS read-only 2524 STATUS deprecated 2525 DESCRIPTION 2526 "The negotiated version of BGP running between 2527 the two peers. 2529 This entry MUST be zero (0) unless the 2530 bgpPeerState is in the openconfirm or the 2531 established state. 2533 Note that legal values for this object are 2534 between 0 and 255." 2535 REFERENCE 2536 "RFC 4271, Section 4.2. 2537 RFC 4271, Section 7." 2538 ::= { bgpPeerEntry 4 } 2540 bgpPeerLocalAddr OBJECT-TYPE 2541 SYNTAX IpAddress 2542 MAX-ACCESS read-only 2543 STATUS deprecated 2544 DESCRIPTION 2545 "The local IP address of this entry's BGP 2546 connection." 2547 ::= { bgpPeerEntry 5 } 2549 bgpPeerLocalPort OBJECT-TYPE 2550 SYNTAX Integer32 (0..65535) 2551 MAX-ACCESS read-only 2552 STATUS deprecated 2553 DESCRIPTION 2554 "The local port for the TCP connection between 2555 the BGP peers." 2556 ::= { bgpPeerEntry 6 } 2558 bgpPeerRemoteAddr OBJECT-TYPE 2559 SYNTAX IpAddress 2560 MAX-ACCESS read-only 2561 STATUS deprecated 2562 DESCRIPTION 2563 "The remote IP address of this entry's BGP 2564 peer." 2565 ::= { bgpPeerEntry 7 } 2567 bgpPeerRemotePort OBJECT-TYPE 2568 SYNTAX Integer32 (0..65535) 2569 MAX-ACCESS read-only 2570 STATUS deprecated 2571 DESCRIPTION 2572 "The remote port for the TCP connection 2573 between the BGP peers. Note that the 2574 objects bgpPeerLocalAddr, 2575 bgpPeerLocalPort, bgpPeerRemoteAddr, and 2576 bgpPeerRemotePort provide the appropriate 2577 reference to the standard MIB TCP 2578 connection table." 2579 ::= { bgpPeerEntry 8 } 2581 bgpPeerRemoteAs OBJECT-TYPE 2582 SYNTAX Integer32 (0..65535) 2583 MAX-ACCESS read-only 2584 STATUS deprecated 2585 DESCRIPTION 2586 "The remote autonomous system number received in 2587 the BGP OPEN message." 2588 REFERENCE 2589 "RFC 4271, Section 4.2." 2590 ::= { bgpPeerEntry 9 } 2592 bgpPeerInUpdates OBJECT-TYPE 2593 SYNTAX Counter32 2594 MAX-ACCESS read-only 2595 STATUS deprecated 2596 DESCRIPTION 2597 "The number of BGP UPDATE messages 2598 received on this connection." 2599 REFERENCE 2600 "RFC 4271, Section 4.3." 2601 ::= { bgpPeerEntry 10 } 2603 bgpPeerOutUpdates OBJECT-TYPE 2604 SYNTAX Counter32 2605 MAX-ACCESS read-only 2606 STATUS deprecated 2607 DESCRIPTION 2608 "The number of BGP UPDATE messages 2609 transmitted on this connection." 2610 REFERENCE 2611 "RFC 4271, Section 4.3." 2612 ::= { bgpPeerEntry 11 } 2614 bgpPeerInTotalMessages OBJECT-TYPE 2615 SYNTAX Counter32 2616 MAX-ACCESS read-only 2617 STATUS deprecated 2618 DESCRIPTION 2619 "The total number of messages received 2620 from the remote peer on this connection." 2621 REFERENCE 2622 "RFC 4271, Section 4." 2623 ::= { bgpPeerEntry 12 } 2625 bgpPeerOutTotalMessages OBJECT-TYPE 2626 SYNTAX Counter32 2627 MAX-ACCESS read-only 2628 STATUS deprecated 2629 DESCRIPTION 2630 "The total number of messages transmitted to 2631 the remote peer on this connection." 2632 REFERENCE 2633 "RFC 4271, Section 4." 2634 ::= { bgpPeerEntry 13 } 2636 bgpPeerLastError OBJECT-TYPE 2637 SYNTAX OCTET STRING (SIZE (2)) 2638 MAX-ACCESS read-only 2639 STATUS deprecated 2640 DESCRIPTION 2641 "The last error code and subcode seen by this 2642 peer on this connection. If no error has 2643 occurred, this field is zero. Otherwise, the 2644 first byte of this two byte OCTET STRING 2645 contains the error code, and the second byte 2646 contains the subcode." 2647 REFERENCE 2648 "RFC 4271, Section 4.5." 2649 ::= { bgpPeerEntry 14 } 2651 bgpPeerFsmEstablishedTransitions OBJECT-TYPE 2652 SYNTAX Counter32 2653 MAX-ACCESS read-only 2654 STATUS deprecated 2655 DESCRIPTION 2656 "The total number of times the BGP FSM 2657 transitioned into the established state 2658 for this peer." 2659 REFERENCE 2660 "RFC 4271, Section 8." 2661 ::= { bgpPeerEntry 15 } 2663 bgpPeerFsmEstablishedTime OBJECT-TYPE 2664 SYNTAX Gauge32 2665 UNITS "seconds" 2666 MAX-ACCESS read-only 2667 STATUS deprecated 2668 DESCRIPTION 2669 "This timer indicates how long (in 2670 seconds) this peer has been in the 2671 established state or how long 2672 since this peer was last in the 2673 established state. It is set to zero when 2674 a new peer is configured or when the router is 2675 booted." 2676 REFERENCE 2677 "RFC 4271, Section 8." 2678 ::= { bgpPeerEntry 16 } 2680 bgpPeerConnectRetryInterval OBJECT-TYPE 2681 SYNTAX Integer32 (1..65535) 2682 UNITS "seconds" 2683 MAX-ACCESS read-write 2684 STATUS deprecated 2685 DESCRIPTION 2686 "Time interval (in seconds) for the 2687 ConnectRetry timer. The suggested value 2688 for this timer is 120 seconds." 2689 REFERENCE 2690 "RFC 4271, Section 8.2.2. This is the value used 2691 to initialize the 'ConnectRetryTimer'." 2692 ::= { bgpPeerEntry 17 } 2694 bgpPeerHoldTime OBJECT-TYPE 2695 SYNTAX Integer32 ( 0 | 3..65535 ) 2696 UNITS "seconds" 2697 MAX-ACCESS read-only 2698 STATUS deprecated 2699 DESCRIPTION 2700 "Time interval (in seconds) for the Hold 2701 Timer established with the peer. The 2702 value of this object is calculated by this 2703 BGP speaker, using the smaller of the 2704 values in bgpPeerHoldTimeConfigured and the 2705 Hold Time received in the OPEN message. 2707 This value must be at least three seconds 2708 if it is not zero (0). 2710 If the Hold Timer has not been established 2711 with the peer this object MUST have a value 2712 of zero (0). 2714 If the bgpPeerHoldTimeConfigured object has 2715 a value of (0), then this object MUST have a 2716 value of (0)." 2717 REFERENCE 2718 "RFC 4271, Section 4.2." 2719 ::= { bgpPeerEntry 18 } 2721 bgpPeerKeepAlive OBJECT-TYPE 2722 SYNTAX Integer32 ( 0 | 1..21845 ) 2723 UNITS "seconds" 2724 MAX-ACCESS read-only 2725 STATUS deprecated 2726 DESCRIPTION 2727 "Time interval (in seconds) for the KeepAlive 2728 timer established with the peer. The value 2729 of this object is calculated by this BGP 2730 speaker such that, when compared with 2731 bgpPeerHoldTime, it has the same proportion 2732 that bgpPeerKeepAliveConfigured has, 2733 compared with bgpPeerHoldTimeConfigured. 2735 If the KeepAlive timer has not been established 2736 with the peer, this object MUST have a value 2737 of zero (0). 2739 If the of bgpPeerKeepAliveConfigured object 2740 has a value of (0), then this object MUST have 2741 a value of (0)." 2742 REFERENCE 2743 "RFC 4271, Section 4.4." 2744 ::= { bgpPeerEntry 19 } 2746 bgpPeerHoldTimeConfigured OBJECT-TYPE 2747 SYNTAX Integer32 ( 0 | 3..65535 ) 2748 UNITS "seconds" 2749 MAX-ACCESS read-write 2750 STATUS deprecated 2751 DESCRIPTION 2752 "Time interval (in seconds) for the Hold Time 2753 configured for this BGP speaker with this 2754 peer. This value is placed in an OPEN 2755 message sent to this peer by this BGP 2756 speaker, and is compared with the Hold 2757 Time field in an OPEN message received 2758 from the peer when determining the Hold 2759 Time (bgpPeerHoldTime) with the peer. 2760 This value must not be less than three 2761 seconds if it is not zero (0). If it is 2762 zero (0), the Hold Time is NOT to be 2763 established with the peer. The suggested 2764 value for this timer is 90 seconds." 2765 REFERENCE 2766 "RFC 4271, Section 4.2. 2767 RFC 4271, Section 10." 2768 ::= { bgpPeerEntry 20 } 2770 bgpPeerKeepAliveConfigured OBJECT-TYPE 2771 SYNTAX Integer32 ( 0 | 1..21845 ) 2772 UNITS "seconds" 2773 MAX-ACCESS read-write 2774 STATUS deprecated 2775 DESCRIPTION 2776 "Time interval (in seconds) for the 2777 KeepAlive timer configured for this BGP 2778 speaker with this peer. The value of this 2779 object will only determine the 2780 KEEPALIVE messages' frequency relative to 2781 the value specified in 2782 bgpPeerHoldTimeConfigured; the actual 2783 time interval for the KEEPALIVE messages is 2784 indicated by bgpPeerKeepAlive. A 2785 reasonable maximum value for this timer 2786 would be one third of that of 2787 bgpPeerHoldTimeConfigured. 2788 If the value of this object is zero (0), 2789 no periodic KEEPALIVE messages are sent 2790 to the peer after the BGP connection has 2791 been established. The suggested value for 2792 this timer is 30 seconds." 2793 REFERENCE 2794 "RFC 4271, Section 4.4. 2795 RFC 4271, Section 10." 2796 ::= { bgpPeerEntry 21 } 2798 bgpPeerMinASOriginationInterval OBJECT-TYPE 2799 SYNTAX Integer32 (1..65535) 2800 UNITS "seconds" 2801 MAX-ACCESS read-write 2802 STATUS deprecated 2803 DESCRIPTION 2804 "Time interval (in seconds) for the 2805 MinASOriginationInterval timer. 2806 The suggested value for this timer is 15 2807 seconds." 2808 REFERENCE 2809 "RFC 4271, Section 9.2.1.2. 2810 RFC 4271, Section 10." 2811 ::= { bgpPeerEntry 22 } 2813 bgpPeerMinRouteAdvertisementInterval OBJECT-TYPE 2814 SYNTAX Integer32 (1..65535) 2815 UNITS "seconds" 2816 MAX-ACCESS read-write 2817 STATUS deprecated 2818 DESCRIPTION 2819 "Time interval (in seconds) for the 2820 MinRouteAdvertisementInterval timer. 2821 The suggested value for this timer is 30 2822 seconds for EBGP connections and 5 2823 seconds for IBGP connections." 2824 REFERENCE 2825 "RFC 4271, Section 9.2.1.1. 2826 RFC 4271, Section 10." 2827 ::= { bgpPeerEntry 23 } 2829 bgpPeerInUpdateElapsedTime OBJECT-TYPE 2830 SYNTAX Gauge32 2831 UNITS "seconds" 2832 MAX-ACCESS read-only 2833 STATUS deprecated 2834 DESCRIPTION 2835 "Elapsed time (in seconds) since the last BGP 2836 UPDATE message was received from the peer. 2837 Each time bgpPeerInUpdates is incremented, 2838 the value of this object is set to zero (0)." 2839 REFERENCE 2840 "RFC 4271, Section 4.3. 2841 RFC 4271, Section 8.2.2, Established state." 2842 ::= { bgpPeerEntry 24 } 2844 -- BGP Received Path Attribute Table. This table contains 2845 -- one entry per path to a network, and path attributes 2846 -- received from all peers running BGP version 3 or less. 2847 -- This table is obsolete, having been replaced in 2848 -- functionality by the bgp4PathAttrTable. 2850 bgpRcvdPathAttrTable OBJECT-TYPE 2851 SYNTAX SEQUENCE OF BgpPathAttrEntry 2852 MAX-ACCESS not-accessible 2853 STATUS obsolete 2854 DESCRIPTION 2855 "The BGP Received Path Attribute Table 2856 contains information about paths to 2857 destination networks, received from all 2858 peers running BGP version 3 or less." 2859 ::= { bgp 5 } 2861 bgpPathAttrEntry OBJECT-TYPE 2862 SYNTAX BgpPathAttrEntry 2863 MAX-ACCESS not-accessible 2864 STATUS obsolete 2865 DESCRIPTION 2866 "Information about a path to a network." 2867 INDEX { bgpPathAttrDestNetwork, 2868 bgpPathAttrPeer } 2869 ::= { bgpRcvdPathAttrTable 1 } 2871 BgpPathAttrEntry ::= SEQUENCE { 2872 bgpPathAttrPeer 2873 IpAddress, 2874 bgpPathAttrDestNetwork 2875 IpAddress, 2876 bgpPathAttrOrigin 2877 INTEGER, 2878 bgpPathAttrASPath 2879 OCTET STRING, 2880 bgpPathAttrNextHop 2881 IpAddress, 2882 bgpPathAttrInterASMetric 2883 Integer32 2884 } 2886 bgpPathAttrPeer OBJECT-TYPE 2887 SYNTAX IpAddress 2888 MAX-ACCESS read-only 2889 STATUS obsolete 2890 DESCRIPTION 2891 "The IP address of the peer where the path 2892 information was learned." 2893 ::= { bgpPathAttrEntry 1 } 2895 bgpPathAttrDestNetwork OBJECT-TYPE 2896 SYNTAX IpAddress 2897 MAX-ACCESS read-only 2898 STATUS obsolete 2899 DESCRIPTION 2900 "The address of the destination network." 2901 REFERENCE 2902 "RFC 1267, Section 4.3." 2903 ::= { bgpPathAttrEntry 2 } 2905 bgpPathAttrOrigin OBJECT-TYPE 2906 SYNTAX INTEGER { 2907 igp(1),-- networks are interior 2908 egp(2),-- networks learned via the 2909 -- EGP protocol 2910 incomplete(3) -- networks that 2911 -- are learned by some other 2912 -- means 2913 } 2914 MAX-ACCESS read-only 2915 STATUS obsolete 2916 DESCRIPTION 2917 "The ultimate origin of the path information." 2918 REFERENCE 2919 "RFC 1267, Section 4.3. 2920 RFC 1267, Section 5." 2921 ::= { bgpPathAttrEntry 3 } 2923 bgpPathAttrASPath OBJECT-TYPE 2924 SYNTAX OCTET STRING (SIZE (2..255)) 2925 MAX-ACCESS read-only 2926 STATUS obsolete 2927 DESCRIPTION 2928 "The set of ASes that must be traversed to reach 2929 the network. This object is probably best 2930 represented as SEQUENCE OF INTEGER. For SMI 2931 compatibility, though, it is represented as 2932 OCTET STRING. Each AS is represented as a pair 2933 of octets according to the following algorithm: 2935 first-byte-of-pair = ASNumber / 256; 2936 second-byte-of-pair = ASNumber & 255;" 2937 REFERENCE 2938 "RFC 1267, Section 4.3. 2939 RFC 1267, Section 5." 2940 ::= { bgpPathAttrEntry 4 } 2942 bgpPathAttrNextHop OBJECT-TYPE 2943 SYNTAX IpAddress 2944 MAX-ACCESS read-only 2945 STATUS obsolete 2946 DESCRIPTION 2947 "The address of the border router that should 2948 be used for the destination network." 2949 REFERENCE 2950 "RFC 1267, Section 4.3. 2951 RFC 1267, Section 5." 2952 ::= { bgpPathAttrEntry 5 } 2954 bgpPathAttrInterASMetric OBJECT-TYPE 2955 SYNTAX Integer32 2956 MAX-ACCESS read-only 2957 STATUS obsolete 2958 DESCRIPTION 2959 "The optional inter-AS metric. If this 2960 attribute has not been provided for this route, 2961 the value for this object is 0." 2962 REFERENCE 2963 "RFC 1267, Section 4.3. 2964 RFC 1267, Section 5." 2965 ::= { bgpPathAttrEntry 6 } 2967 -- BGP-4 Received Path Attribute Table. This table 2968 -- contains one entry per path to a network, and path 2969 -- attributes received from all peers running BGP-4. 2971 bgp4PathAttrTable OBJECT-TYPE 2972 SYNTAX SEQUENCE OF Bgp4PathAttrEntry 2973 MAX-ACCESS not-accessible 2974 STATUS deprecated 2975 DESCRIPTION 2976 "The BGP-4 Received Path Attribute Table 2977 contains information about paths to 2978 destination networks, received from all 2979 BGP4 peers. 2981 This table has been replaced by the functionality 2982 provided under the bgpRib OID." 2983 ::= { bgp 6 } 2985 bgp4PathAttrEntry OBJECT-TYPE 2986 SYNTAX Bgp4PathAttrEntry 2987 MAX-ACCESS not-accessible 2988 STATUS deprecated 2989 DESCRIPTION 2990 "Information about a path to a network." 2991 INDEX { bgp4PathAttrIpAddrPrefix, 2992 bgp4PathAttrIpAddrPrefixLen, 2993 bgp4PathAttrPeer } 2994 ::= { bgp4PathAttrTable 1 } 2996 Bgp4PathAttrEntry ::= SEQUENCE { 2997 bgp4PathAttrPeer 2998 IpAddress, 2999 bgp4PathAttrIpAddrPrefixLen 3000 Integer32, 3001 bgp4PathAttrIpAddrPrefix 3002 IpAddress, 3003 bgp4PathAttrOrigin 3004 INTEGER, 3006 bgp4PathAttrASPathSegment 3007 OCTET STRING, 3008 bgp4PathAttrNextHop 3009 IpAddress, 3010 bgp4PathAttrMultiExitDisc 3011 Integer32, 3012 bgp4PathAttrLocalPref 3013 Integer32, 3014 bgp4PathAttrAtomicAggregate 3015 INTEGER, 3016 bgp4PathAttrAggregatorAS 3017 Integer32, 3018 bgp4PathAttrAggregatorAddr 3019 IpAddress, 3020 bgp4PathAttrCalcLocalPref 3021 Integer32, 3022 bgp4PathAttrBest 3023 INTEGER, 3024 bgp4PathAttrUnknown 3025 OCTET STRING 3026 } 3028 bgp4PathAttrPeer OBJECT-TYPE 3029 SYNTAX IpAddress 3030 MAX-ACCESS read-only 3031 STATUS deprecated 3032 DESCRIPTION 3033 "The IP address of the peer where the path 3034 information was learned." 3035 ::= { bgp4PathAttrEntry 1 } 3037 bgp4PathAttrIpAddrPrefixLen OBJECT-TYPE 3038 SYNTAX Integer32 (0..32) 3039 MAX-ACCESS read-only 3040 STATUS deprecated 3041 DESCRIPTION 3042 "Length in bits of the IP address prefix in 3043 the Network Layer Reachability 3044 Information field." 3045 ::= { bgp4PathAttrEntry 2 } 3047 bgp4PathAttrIpAddrPrefix OBJECT-TYPE 3048 SYNTAX IpAddress 3049 MAX-ACCESS read-only 3050 STATUS deprecated 3051 DESCRIPTION 3052 "An IP address prefix in the Network Layer 3053 Reachability Information field. This object 3054 is an IP address containing the prefix with 3055 length specified by 3056 bgp4PathAttrIpAddrPrefixLen. 3057 Any bits beyond the length specified by 3058 bgp4PathAttrIpAddrPrefixLen are zeroed." 3059 REFERENCE 3060 "RFC 4271, Section 4.3." 3061 ::= { bgp4PathAttrEntry 3 } 3063 bgp4PathAttrOrigin OBJECT-TYPE 3064 SYNTAX INTEGER { 3065 igp(1),-- networks are interior 3066 egp(2),-- networks learned via the 3067 -- EGP protocol 3068 incomplete(3) -- networks that 3069 -- are learned by some other 3070 -- means 3071 } 3072 MAX-ACCESS read-only 3073 STATUS deprecated 3074 DESCRIPTION 3075 "The ultimate origin of the path 3076 information." 3077 REFERENCE 3078 "RFC 4271, Section 4.3. 3079 RFC 4271, Section 5.1.1." 3080 ::= { bgp4PathAttrEntry 4 } 3082 bgp4PathAttrASPathSegment OBJECT-TYPE 3083 SYNTAX OCTET STRING (SIZE (2..255)) 3084 MAX-ACCESS read-only 3085 STATUS deprecated 3086 DESCRIPTION 3087 "The sequence of AS path segments. Each AS 3088 path segment is represented by a triple 3089 . 3091 The type is a 1-octet field that has two 3092 possible values: 3093 1 AS_SET: unordered set of ASes that a 3094 route in the UPDATE message 3095 has traversed 3097 2 AS_SEQUENCE: ordered set of ASes that 3098 a route in the UPDATE message 3099 has traversed. 3101 The length is a 1-octet field containing the 3102 number of ASes in the value field. 3104 The value field contains one or more AS 3105 numbers. Each AS is represented in the octet 3106 string as a pair of octets according to the 3107 following algorithm: 3109 first-byte-of-pair = ASNumber / 256; 3110 second-byte-of-pair = ASNumber & 255; 3112 Known Issues: 3113 o BGP Confederations will result in 3114 a type of either 3 or 4. 3115 o An AS Path may be longer than 255 octets. 3116 This may result in this object containing 3117 a truncated AS Path." 3118 REFERENCE 3119 "RFC 4271, Section 4.3. 3120 RFC 4271, Section 5.1.2." 3121 ::= { bgp4PathAttrEntry 5 } 3123 bgp4PathAttrNextHop OBJECT-TYPE 3124 SYNTAX IpAddress 3125 MAX-ACCESS read-only 3126 STATUS deprecated 3127 DESCRIPTION 3128 "The address of the border router that 3129 should be used for the destination 3130 network. This address is the NEXT_HOP 3131 address received in the UPDATE packet." 3132 REFERENCE 3133 "RFC 4271, Section 4.3. 3134 RFC 4271, Section 5.1.3." 3135 ::= { bgp4PathAttrEntry 6 } 3137 bgp4PathAttrMultiExitDisc OBJECT-TYPE 3138 SYNTAX Integer32 (-1..2147483647) 3139 MAX-ACCESS read-only 3140 STATUS deprecated 3141 DESCRIPTION 3142 "This metric is used to discriminate 3143 between multiple exit points to an 3144 adjacent autonomous system. A value of -1 3145 indicates the absence of this attribute. 3147 Known Issues: 3148 o The BGP-4 specification uses an 3149 unsigned 32 bit number. Thus, this 3150 object cannot represent the full 3151 range of the protocol." 3152 REFERENCE 3153 "RFC 4271, Section 4.3. 3154 RFC 4271, Section 5.1.4." 3155 ::= { bgp4PathAttrEntry 7 } 3157 bgp4PathAttrLocalPref OBJECT-TYPE 3158 SYNTAX Integer32 (-1..2147483647) 3159 MAX-ACCESS read-only 3160 STATUS deprecated 3161 DESCRIPTION 3162 "The originating BGP4 speaker's degree of 3163 preference for an advertised route. A 3164 value of -1 indicates the absence of this 3165 attribute. 3167 Known Issues: 3168 o The BGP-4 specification uses an 3169 unsigned 32 bit number and thus this 3170 object cannot represent the full 3171 range of the protocol." 3172 REFERENCE 3173 "RFC 4271, Section 4.3. 3174 RFC 4271, Section 5.1.5." 3175 ::= { bgp4PathAttrEntry 8 } 3177 bgp4PathAttrAtomicAggregate OBJECT-TYPE 3178 SYNTAX INTEGER { 3179 lessSpecificRouteNotSelected(1), 3180 -- Typo corrected from RFC 1657 3181 lessSpecificRouteSelected(2) 3182 } 3183 MAX-ACCESS read-only 3184 STATUS deprecated 3185 DESCRIPTION 3186 "If the ATOMIC_AGGREGATE attribute is present 3187 in the Path Attributes then this object MUST 3188 have a value of 'lessSpecificRouteNotSelected'. 3190 If the ATOMIC_AGGREGATE attribute is missing 3191 in the Path Attributes then this object MUST 3192 have a value of 'lessSpecificRouteSelected'. 3194 Note that ATOMIC_AGGREGATE is now a primarily 3195 informational attribute." 3196 REFERENCE 3197 "RFC 4271, Sections 5.1.6 and 9.1.4." 3199 ::= { bgp4PathAttrEntry 9 } 3201 bgp4PathAttrAggregatorAS OBJECT-TYPE 3202 SYNTAX Integer32 (0..65535) 3203 MAX-ACCESS read-only 3204 STATUS deprecated 3205 DESCRIPTION 3206 "The AS number of the last BGP4 speaker that 3207 performed route aggregation. A value of 3208 zero (0) indicates the absence of this 3209 attribute. 3211 Note that propagation of AS of zero is illegal 3212 in the Internet." 3213 REFERENCE 3214 "RFC 4271, Section 5.1.7. 3215 RFC 4271, Section 9.2.2.2." 3216 ::= { bgp4PathAttrEntry 10 } 3218 bgp4PathAttrAggregatorAddr OBJECT-TYPE 3219 SYNTAX IpAddress 3220 MAX-ACCESS read-only 3221 STATUS deprecated 3222 DESCRIPTION 3223 "The IP address of the last BGP4 speaker 3224 that performed route aggregation. A 3225 value of 0.0.0.0 indicates the absence 3226 of this attribute." 3227 REFERENCE 3228 "RFC 4271, Section 5.1.7. 3229 RFC 4271, Section 9.2.2.2." 3230 ::= { bgp4PathAttrEntry 11 } 3232 bgp4PathAttrCalcLocalPref OBJECT-TYPE 3233 SYNTAX Integer32 (-1..2147483647) 3234 MAX-ACCESS read-only 3235 STATUS deprecated 3236 DESCRIPTION 3237 "The degree of preference calculated by the 3238 receiving BGP4 speaker for an advertised 3239 route. A value of -1 indicates the 3240 absence of this attribute. 3242 Known Issues: 3243 o The BGP-4 specification uses an 3244 unsigned 32 bit number and thus this 3245 object cannot represent the full 3246 range of the protocol." 3248 REFERENCE 3249 "RFC 4271, Section 9.1.1." 3250 ::= { bgp4PathAttrEntry 12 } 3252 bgp4PathAttrBest OBJECT-TYPE 3253 SYNTAX INTEGER { 3254 false(1),-- not chosen as best route 3255 true(2) -- chosen as best route 3256 } 3257 MAX-ACCESS read-only 3258 STATUS deprecated 3259 DESCRIPTION 3260 "An indication of whether this route 3261 was chosen as the best BGP4 route for this 3262 destination." 3263 REFERENCE 3264 "RFC 4271, Section 9.1.2." 3265 ::= { bgp4PathAttrEntry 13 } 3267 bgp4PathAttrUnknown OBJECT-TYPE 3268 SYNTAX OCTET STRING (SIZE(0..255)) 3269 MAX-ACCESS read-only 3270 STATUS deprecated 3271 DESCRIPTION 3272 "One or more path attributes not understood by 3273 this BGP4 speaker. 3275 Path attributes are recorded in the Update Path 3276 attribute format of type, length, value. 3278 Size zero (0) indicates the absence of such 3279 attributes. 3281 Octets beyond the maximum size, if any, are not 3282 recorded by this object. 3284 Known Issues: 3285 o Attributes understood by this speaker, but not 3286 represented in this MIB, are unavailable to 3287 the agent." 3288 REFERENCE 3289 "RFC 4271, Section 5." 3290 ::= { bgp4PathAttrEntry 14 } 3292 -- Traps. 3293 -- Note that in RFC 1657, bgpTraps was incorrectly 3294 -- assigned a value of { bgp 7 } and each of the 3295 -- traps had the bgpPeerRemoteAddr object inappropriately 3296 -- removed from their OBJECTS clause. The following 3297 -- definitions restore the semantics of the traps as 3298 -- they were initially defined in RFC 1269. 3300 bgpEstablishedNotification NOTIFICATION-TYPE 3301 OBJECTS { bgpPeerRemoteAddr, 3302 bgpPeerLastError, 3303 bgpPeerState } 3304 STATUS deprecated 3305 DESCRIPTION 3306 "The bgpEstablishedNotification event is generated 3307 when the BGP FSM enters the established state. 3309 This Notification replaces the bgpEstablished 3310 Notification and has been replaced by 3311 bgpAfEstablishedNotification." 3312 ::= { bgpNotification 1 } 3314 bgpBackwardTransNotification NOTIFICATION-TYPE 3315 OBJECTS { bgpPeerRemoteAddr, 3316 bgpPeerLastError, 3317 bgpPeerState } 3318 STATUS deprecated 3319 DESCRIPTION 3320 "The bgpBackwardTransNotification event is 3321 generated when the BGP FSM moves from a higher 3322 numbered state to a lower numbered state. 3324 This Notification replaces the 3325 bgpBackwardsTransition Notification and has 3326 been replaced by bgpAfBackwardsNotification." 3327 ::= { bgpNotification 2 } 3329 -- { bgp 7 } is deprecated. Do not allocate new objects or 3330 -- notifications underneath this branch. 3332 bgpTraps OBJECT IDENTIFIER ::= { bgp 7 } -- deprecated 3334 bgpEstablished NOTIFICATION-TYPE 3335 OBJECTS { bgpPeerLastError, 3336 bgpPeerState } 3337 STATUS deprecated 3338 DESCRIPTION 3339 "The bgpEstablished event is generated when 3340 the BGP FSM enters the established state. 3342 This Notification has been replaced by the 3343 bgpEstablishedNotification Notification." 3344 ::= { bgpTraps 1 } 3346 bgpBackwardTransition NOTIFICATION-TYPE 3347 OBJECTS { bgpPeerLastError, 3348 bgpPeerState } 3349 STATUS deprecated 3350 DESCRIPTION 3351 "The bgpBackwardTransition event is generated 3352 when the BGP FSM moves from a higher numbered 3353 state to a lower numbered state. 3355 This Notification has been replaced by the 3356 bgpBackwardTransNotification Notification." 3357 ::= { bgpTraps 2 } 3359 -- Obsolete Compliance statements 3361 bgp4MIBCompliance MODULE-COMPLIANCE 3362 STATUS obsolete 3363 DESCRIPTION 3364 "The compliance statement for entities which 3365 implement the BGP4 mib. 3367 This compliance statement is obsoleted by 3368 bgpAfMIBCompliance." 3369 MODULE -- this module 3370 MANDATORY-GROUPS { bgp4MIBGlobalsGroup, 3371 bgp4MIBPeerGroup, 3372 bgp4MIBPathAttrGroup } 3373 GROUP bgp4MIBNotificationGroup 3374 DESCRIPTION 3375 "Implementation of BGP Notifications are 3376 completely optional in this MIB." 3377 ::= { bgp4MIBCompliances 1 } 3379 bgp4MIBDeprecatedCompliances MODULE-COMPLIANCE 3380 STATUS obsolete 3381 DESCRIPTION 3382 "The compliance statement documenting deprecated 3383 objects in the BGP4 mib. 3385 This compliance statement is obsoleted 3386 by bgpAfMIBCompliance." 3387 MODULE -- this module 3388 GROUP bgp4MIBTrapGroup 3389 DESCRIPTION 3390 "Group containing TRAP objects that were 3391 improperly converted from SMIv1 in RFC 1657. 3392 The proper semantics have been restored 3393 with the objects in bgp4MIBNotificationGroup." 3394 ::= { bgp4MIBCompliances 2 } 3396 bgp4MIBObsoleteCompliances MODULE-COMPLIANCE 3397 STATUS obsolete 3398 DESCRIPTION 3399 "The compliance statement documenting obsolete 3400 objects in the BGP4 mib." 3401 MODULE -- this module 3402 GROUP bgpRcvdPathAttrGroup 3403 DESCRIPTION 3404 "Group containing objects relevant to BGP-3 3405 and earlier objects." 3406 ::= { bgp4MIBCompliances 3 } 3408 -- Units of conformance 3410 bgp4MIBGlobalsGroup OBJECT-GROUP 3411 OBJECTS { bgpVersion, 3412 bgpLocalAs, 3413 bgpIdentifier } 3414 STATUS obsolete 3415 DESCRIPTION 3416 "A collection of objects providing 3417 information on global BGP state. 3419 This group has been replaced by 3420 bgpAfMIBGlobalsGroup and bgpAfMIBOldGlobalsGroup." 3421 ::= { bgp4MIBGroups 1 } 3423 bgp4MIBPeerGroup OBJECT-GROUP 3424 OBJECTS { bgpPeerIdentifier, 3425 bgpPeerState, 3426 bgpPeerAdminStatus, 3427 bgpPeerNegotiatedVersion, 3428 bgpPeerLocalAddr, 3429 bgpPeerLocalPort, 3430 bgpPeerRemoteAddr, 3431 bgpPeerRemotePort, 3432 bgpPeerRemoteAs, 3433 bgpPeerInUpdates, 3434 bgpPeerOutUpdates, 3435 bgpPeerInTotalMessages, 3436 bgpPeerOutTotalMessages, 3437 bgpPeerLastError, 3438 bgpPeerFsmEstablishedTransitions, 3439 bgpPeerFsmEstablishedTime, 3440 bgpPeerConnectRetryInterval, 3441 bgpPeerHoldTime, 3442 bgpPeerKeepAlive, 3443 bgpPeerHoldTimeConfigured, 3444 bgpPeerKeepAliveConfigured, 3445 bgpPeerMinASOriginationInterval, 3446 bgpPeerMinRouteAdvertisementInterval, 3447 bgpPeerInUpdateElapsedTime } 3448 STATUS deprecated 3449 DESCRIPTION 3450 "A collection of objects for managing BGP peers 3451 from the previous version of this MIB. The 3452 individual objects are deprecated and their support 3453 is OPTIONAL." 3454 ::= { bgp4MIBGroups 2 } 3456 bgpRcvdPathAttrGroup OBJECT-GROUP 3457 OBJECTS { bgpPathAttrPeer, 3458 bgpPathAttrDestNetwork, 3459 bgpPathAttrOrigin, 3460 bgpPathAttrASPath, 3461 bgpPathAttrNextHop, 3462 bgpPathAttrInterASMetric } 3463 STATUS obsolete 3464 DESCRIPTION 3465 "A collection of objects for managing BGP-3 and 3466 earlier path entries. 3468 This conformance group, like BGP-3, is obsolete." 3469 ::= { bgp4MIBGroups 3 } 3471 bgp4MIBPathAttrGroup OBJECT-GROUP 3472 OBJECTS { bgp4PathAttrPeer, 3473 bgp4PathAttrIpAddrPrefixLen, 3474 bgp4PathAttrIpAddrPrefix, 3475 bgp4PathAttrOrigin, 3476 bgp4PathAttrASPathSegment, 3477 bgp4PathAttrNextHop, 3478 bgp4PathAttrMultiExitDisc, 3479 bgp4PathAttrLocalPref, 3480 bgp4PathAttrAtomicAggregate, 3481 bgp4PathAttrAggregatorAS, 3482 bgp4PathAttrAggregatorAddr, 3483 bgp4PathAttrCalcLocalPref, 3484 bgp4PathAttrBest, 3485 bgp4PathAttrUnknown } 3487 STATUS deprecated 3488 DESCRIPTION 3489 "A collection of objects for managing BGP path 3490 entries from the previous version of this MIB. This 3491 individual objects are deprecated and their support 3492 is OPTIONAL." 3493 ::= { bgp4MIBGroups 4 } 3495 bgp4MIBTrapGroup NOTIFICATION-GROUP 3496 NOTIFICATIONS { bgpEstablished, 3497 bgpBackwardTransition } 3498 STATUS deprecated 3499 DESCRIPTION 3500 "A collection of notifications for signaling 3501 changes in BGP peer relationships. 3503 Obsoleted by bgp4MIBNotificationGroup. Support of 3504 the objects in this group is OPTIONAL." 3505 ::= { bgp4MIBGroups 5 } 3507 bgp4MIBNotificationGroup NOTIFICATION-GROUP 3508 NOTIFICATIONS { bgpEstablishedNotification, 3509 bgpBackwardTransNotification } 3510 STATUS deprecated 3511 DESCRIPTION 3512 "A collection of notifications for signaling 3513 changes in BGP peer relationships. 3515 Obsoletes bgp4MIBTrapGroup. Obsoleted by 3516 bgpAfMIBNotificationGroup. Support for objects in 3517 this group is OPTIONAL." 3518 ::= { bgp4MIBGroups 6 } 3520 bgpAfMIBNotificationGroup NOTIFICATION-GROUP 3521 NOTIFICATIONS { bgpAfEstablishedNotification, 3522 bgpAfBackwardTransNotification } 3523 STATUS current 3524 DESCRIPTION 3525 "A collection of notifications for signaling 3526 changes in BGP peer relationships. 3528 Obsoletes bgp4MIBNotificationGroup." 3529 ::= { bgp4MIBGroups 7 } 3531 END 3532 8. Security Considerations 3534 This MIB relates to a system providing inter-domain routing. As 3535 such, improper manipulation of the objects represented by this MIB 3536 may result in denial of service to a large number of end-users. 3538 There are a number of management objects defined in this MIB module 3539 with a MAX-ACCESS clause of read-write and/or read-create. Such 3540 objects may be considered sensitive or vulnerable in some network 3541 environments. The support for SET operations in a non-secure 3542 environment without proper protection can have a negative effect on 3543 network operations. These are the tables and objects and their 3544 sensitivity/vulnerability: 3546 bgpPeerAdminStatus - Improper change of bgpPeerAdminStatus, from 3547 start to stop, can cause significant disruption of the 3548 connectivity to those portions of the Internet reached via the 3549 applicable remote BGP peer. 3551 bgpPeerConnectRetryInterval - Improper change of this object can 3552 cause connections to be disrupted for extremely long time periods 3553 when otherwise they would be restored in a relatively short period 3554 of time. 3556 bgpPeerHoldTimeConfigured, bgpPeerKeepAliveConfigured - 3557 Misconfiguration of these objects can make BGP sessions more 3558 fragile and less resilient to denial of service attacks on the 3559 inter-domain routing system. 3561 bgpPeerMinASOriginationInterval, 3562 bgpPeerMinRouteAdvertisementInterval - Misconfiguration of these 3563 objects may adversely affect global Internet convergence of the 3564 routes advertised by this BGP speaker. This may result in long- 3565 lived routing loops and blackholes for the portions of the 3566 Internet that utilize these routes. 3568 Some of the readable objects in this MIB module (i.e., objects with a 3569 MAX-ACCESS other than not-accessible) may be considered sensitive or 3570 vulnerable in some network environments. It is thus important to 3571 control even GET and/or NOTIFY access to these objects and possibly 3572 to even encrypt the values of these objects when sending them over 3573 the network via SNMP. These are the tables and objects and their 3574 sensitivity/vulnerability: 3576 o bgpPeerAfLocalAddrType, bgpPeerAfLocalAddr,bgpPeerAfLocalPort 3577 bgpPeerAfRemoteAddrType, bgpPeerAfRemoteAddr, bgpPeerAfRemotePort, 3578 bgpPeerLocalAddr, bgpPeerLocalPort, bgpPeerRemoteAddr, 3579 bgpPeerRemotePort - A BGP peer's local and remote addresses might 3580 be sensitive for ISPs who want to keep interface addresses on 3581 routers confidential in order to prevent router addresses used for 3582 a denial of service attack or spoofing. Note that other tables 3583 which share elements of these objects as indexes may similarly 3584 expose sensitive information. 3586 o bgpNlriTable, bgpAdjRibsOutTable, bgpAfPathAttrTable, 3587 bgpAsPathTable, bgpRcvdPathAttrTable, bgp4PathAttrTable - A BGP 3588 peer's routing information may be sensitive for ISPs as the 3589 contents of their routing tables may expose details related to 3590 business relationships as implemented in Internet routing. 3592 SNMP versions prior to SNMPv3 did not include adequate security. 3593 Even if the network itself is secure (for example by using IPSec), 3594 even then, there is no control as to who on the secure network is 3595 allowed to access and GET/SET (read/change/create/delete) the objects 3596 in this MIB module. 3598 It is RECOMMENDED that implementers consider the security features as 3599 provided by the SNMPv3 framework (see [RFC3410], section 8), 3600 including full support for the SNMPv3 cryptographic mechanisms (for 3601 authentication and privacy). 3603 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3604 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3605 enable cryptographic security. It is then a customer/operator 3606 responsibility to ensure that the SNMP entity giving access to an 3607 instance of this MIB module is properly configured to give access to 3608 the objects only to those principals (users) that have legitimate 3609 rights to indeed GET or SET (change/create/delete) them. 3611 9. IANA Considerations 3613 This document includes an OID, bgpExtensions, which defines a name 3614 space for future BGP extensions. IANA is requested to create a new 3615 registry for new OIDs under bgpExtensions that will define the root 3616 OID of future MIB modules for bgp extensions. The assignment OIDs 3617 should be done based upon IDR working group consensus. 3619 10. Contributors 3621 This document owes significant thanks over the years to Wayne 3622 Tackabury, Susan Hares and the members of the idr and ops-nm mailing 3623 lists. This document represents several years of negotiating 3624 operational needs, Internet operational security considerations and 3625 the sheer messiness of representing the BGP protocol in SMIv2. 3627 I owe particular thanks to Susan Hares as a mentor who let me dive 3628 head-first into the world of Internet standards work by saying, "We 3629 have this MIB that just needs a little cleanup to advance in the 3630 standards process." 3632 11. Acknowledgements 3634 We would like to acknowledge the assistance of all the members of the 3635 Inter-Domain Routing Working Group, and particularly the following 3636 individuals: 3638 Yakov Rekhter, Juniper Networks 3640 Rob Coltun, Redback 3642 Guy Almes, Internet2 3644 Jeff Honig, BSDi 3646 Marshall T. Rose, Dover Beach Consulting, Inc. 3648 Dennis Ferguson, Juniper Networks 3650 Matt Mathis, PSC 3652 John Krawczyk, Bay Networks 3654 Curtis Villamizar, Avici 3656 Dave LeRoy, Pencom Systems 3658 Paul Traina, Juniper Networks 3660 Andrew Partan, MFN 3662 Robert Snyder, Cisco Systems 3664 Dimitry Haskin, Nortel 3666 Peder Chr Norgaard, Telebit Communications A/S 3668 Joel Halpern, CTO Longitude Systems, Inc. 3670 Nick Thille, RedBack Networks 3672 Bert Wijnen, Lucent 3674 Shane Wright, NextHop Technologies 3675 Mike McFadden, Riverstone Networks, Inc. 3677 Jon Saperia, JDS Consulting, Inc. 3679 Wayne Tackabury, Gold Wire Technology, Inc. 3681 Bill Fenner, AT&T Research 3683 RJ Atkinson, Extreme Networks 3685 Dan Romascanu, Avaya 3687 Mathew Richardson, NextHop Technologies 3689 The origin of this document is from RFC 1269 "Definitions of 3690 Managed Objects for the Border Gateway Protocol (Version 3)" 3691 written by Steve Willis and John Burruss, which was updated by 3692 John Chu to support BGP-4 in RFC 1657. The editors wish to 3693 acknowledge the fine work of these original authors. 3695 12. References 3697 12.1. Normative References 3699 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3700 Requirement Levels", BCP 14, RFC 2119, March 1997. 3702 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3703 Schoenwaelder, Ed., "Structure of Management Information 3704 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 3706 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3707 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 3708 STD 58, RFC 2579, April 1999. 3710 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3711 "Conformance Statements for SMIv2", STD 58, RFC 2580, 3712 April 1999. 3714 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 3715 Architecture for Describing Simple Network Management 3716 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 3717 December 2002. 3719 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 3720 Protocol 4 (BGP-4)", RFC 4271, January 2006. 3722 [RFC4273] Haas, J. and S. Hares, "Definitions of Managed Objects for 3723 BGP-4", RFC 4273, January 2006. 3725 [RFC2545] Marques, P. and F. Dupont, "Use of BGP-4 Multiprotocol 3726 Extensions for IPv6 Inter-Domain Routing", RFC 2545, 3727 March 1999. 3729 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 3730 Schoenwaelder, "Textual Conventions for Internet Network 3731 Addresses", RFC 4001, February 2005. 3733 [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, 3734 "Multiprotocol Extensions for BGP-4", RFC 4760, 3735 January 2007. 3737 [RFC5065] Traina, P., McPherson, D., and J. Scudder, "Autonomous 3738 System Confederations for BGP", RFC 5065, August 2007. 3740 12.2. Informative References 3742 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 3743 "Introduction and Applicability Statements for Internet- 3744 Standard Management Framework", RFC 3410, December 2002. 3746 [RFC1657] Willis, S., Burruss, J., and J. Chu, "Definitions of 3747 Managed Objects for the Fourth Version of the Border 3748 Gateway Protocol (BGP-4) using SMIv2", RFC 1657, 3749 July 1994. 3751 [RFC3107] Rekhter, Y. and E. Rosen, "Carrying Label Information in 3752 BGP-4", RFC 3107, May 2001. 3754 [RFC4022] Raghunarayan, R., "Management Information Base for the 3755 Transmission Control Protocol (TCP)", RFC 4022, 3756 March 2005. 3758 [RFC4456] Bates, T., Chen, E., and R. Chandra, "BGP Route 3759 Reflection: An Alternative to Full Mesh Internal BGP 3760 (IBGP)", RFC 4456, April 2006. 3762 Author's Address 3764 Jeffrey Haas 3766 Phone: 3767 EMail: jhaas@pfrc.org 3769 Full Copyright Statement 3771 Copyright (C) The IETF Trust (2007). 3773 This document is subject to the rights, licenses and restrictions 3774 contained in BCP 78, and except as set forth therein, the authors 3775 retain all their rights. 3777 This document and the information contained herein are provided on an 3778 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 3779 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 3780 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 3781 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 3782 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 3783 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 3785 Intellectual Property 3787 The IETF takes no position regarding the validity or scope of any 3788 Intellectual Property Rights or other rights that might be claimed to 3789 pertain to the implementation or use of the technology described in 3790 this document or the extent to which any license under such rights 3791 might or might not be available; nor does it represent that it has 3792 made any independent effort to identify any such rights. Information 3793 on the procedures with respect to rights in RFC documents can be 3794 found in BCP 78 and BCP 79. 3796 Copies of IPR disclosures made to the IETF Secretariat and any 3797 assurances of licenses to be made available, or the result of an 3798 attempt made to obtain a general license or permission for the use of 3799 such proprietary rights by implementers or users of this 3800 specification can be obtained from the IETF on-line IPR repository at 3801 http://www.ietf.org/ipr. 3803 The IETF invites any interested party to bring to its attention any 3804 copyrights, patents or patent applications, or other proprietary 3805 rights that may cover technology that may be required to implement 3806 this standard. Please address the information to the IETF at 3807 ietf-ipr@ietf.org. 3809 Acknowledgement 3811 Funding for the RFC Editor function is provided by the IETF 3812 Administrative Support Activity (IASA).