idnits 2.17.1 draft-ietf-idr-bgp4-mibv2-10.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Sep 2009 rather than the newer Notice from 28 Dec 2009. (See https://trustee.ietf.org/license-info/) 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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors 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 (February 1, 2010) is 5170 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'I-D.draft-ietf-idr-bgp4-mibv2-tc' is mentioned on line 209, but not defined -- 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: 1 error (**), 0 flaws (~~), 3 warnings (==), 4 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 Arbor Networks 4 Intended status: Standards Track February 1, 2010 5 Expires: August 5, 2010 7 Definitions of Managed Objects for the Fourth Version of Border Gateway 8 Protocol (BGP-4), Second Version 9 draft-ietf-idr-bgp4-mibv2-10 11 Abstract 13 This memo defines a portion of the Management Information Base (MIB) 14 for use with network management protocols. In particular it defines 15 objects for managing the Border Gateway Protocol, Version 4. 17 Status of This Memo 19 This Internet-Draft is submitted to IETF in full conformance with the 20 provisions of BCP 78 and BCP 79. 22 Internet-Drafts are working documents of the Internet Engineering 23 Task Force (IETF), its areas, and its working groups. Note that 24 other groups may also distribute working documents as Internet- 25 Drafts. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet-Drafts as reference 30 material or to cite them other than as "work in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt. 35 The list of Internet-Draft Shadow Directories can be accessed at 36 http://www.ietf.org/shadow.html. 38 This Internet-Draft will expire on August 5, 2010. 40 Copyright Notice 42 Copyright (c) 2010 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 2. The Internet-Standard Management Framework . . . . . . . . . . 3 59 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 60 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 62 5.1. Notifications . . . . . . . . . . . . . . . . . . . . . . 4 63 5.2. Tables . . . . . . . . . . . . . . . . . . . . . . . . . . 4 64 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 5 65 6.1. Relationship to the TCP-MIB . . . . . . . . . . . . . . . 5 66 6.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 5 67 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 68 8. Security Considerations . . . . . . . . . . . . . . . . . . . 42 69 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 43 70 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 43 71 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 44 72 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 44 73 12.1. Normative References . . . . . . . . . . . . . . . . . . . 44 74 12.2. Informative References . . . . . . . . . . . . . . . . . . 45 76 1. Introduction 78 This memo defines a portion of the Management Information Base (MIB) 79 for use with network management protocols. In particular it defines 80 objects for managing the Border Gateway Protocol, Version 4 81 [RFC4271]. 83 2. The Internet-Standard Management Framework 85 For a detailed overview of the documents that describe the current 86 Internet-Standard Management Framework, please refer to section 7 of 87 RFC 3410 [RFC3410]. 89 Managed objects are accessed via a virtual information store, termed 90 the Management Information Base or MIB. MIB objects are generally 91 accessed through the Simple Network Management Protocol (SNMP). 92 Objects in the MIB are defined using the mechanisms defined in the 93 Structure of Management Information (SMI). This memo specifies a MIB 94 module that is compliant to the SMIv2, which is described in STD 58, 95 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 96 [RFC2580]. 98 3. Conventions 100 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 101 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 102 document are to be interpreted as described in RFC 2119 [RFC2119]. 104 4. Overview 106 As part of the IETF standardization effort for the BGP-4 protocol, 107 [RFC4273] was written to address open issues in the previous version 108 of the BGP-4 MIB, [RFC1657]. However, that RFC was primarily 109 intended to address the base BGP-4 protocol as documented in 110 [RFC4271]. 112 The BGP-4 protocol has greatly increased in scope over the years from 113 its original definition. Scaling mechanisms such as Route Reflection 114 [RFC4456] and Confederations [RFC5065] have been introduced. Multi- 115 protocol extensions [RFC4760] were introduced which allowed 116 advertisement of reachability such as IPv6 [RFC2545], MPLS Labeled 117 routes [RFC3107], etc. 119 This MIB addresses several of the deficiencies of the previous BGP-4 120 MIB. In particular: 122 o Add the ability to monitor IPv6 BGP-4 peering sessions and carry 123 IPv6 reachability. Other forms of reachability can be added at a 124 later date courtesy of the address-family independent manner in 125 which this was done. 127 o Add several counters of operational interest. For example, the 128 number of routes received from a given BGP peer. 130 o Replaces objects that were incapable of carrying the full range of 131 their values with ones that can. 133 o Provides human-readable output for some complex data structures, 134 such as the AS_PATH while also preserving a version of the data 135 that is canonically machine readable. 137 5. Structure of the MIB Module 139 5.1. Notifications 141 o bgp4V2EstablishedNotification - Sent when a BGP peer transitions 142 into the Established state. Replaces the previous 143 bgpEstablishedNotification from RFC 4273 which was not address 144 family independent. 146 o bgp4V2BackwardTransitionNotification - Sent when a BGP peer 147 transitions out of the Established state. Replaces the previous 148 bgpBackwardTransNotification, which was not address family 149 independent. 151 5.2. Tables 153 o bgp4V2DiscontinuityTable - This MIB allows management of more than 154 one instance of the BGP-4 protocol. This table provides the 155 ability to show when a given instance of BGP-4 has suffered an 156 event that may lead to a discontinuity in its objects. 158 o bgp4V2PeerTable - The BGP peer table. This table is capable of 159 representing IPv6 and other address-family independent peering 160 sessions. This table replaces the bgpPeerTable from RFC 4273. 162 o bgp4V2PeerErrorsTable - A table of peering session errors. This 163 table covers information previously present in bgpPeerTable from 164 RFC 4273. 166 o bgp4V2PeerEventTimesTable - A table of peer-specific event timers. 167 This table covers information previously present in bgpPeerTable 168 in RFC 4273 . 170 o bgp4V2PeerConfiguredTimersTable - A table of the configured values 171 of peer-specific event timers. This table covers information 172 previously present in bgpPeerTable from RFC 4273. 174 o bgp4V2PeerNegotiatedTimersTable - A table of per-peer negotiated 175 timers. This information covers information previously derived 176 from the bgpPeerTable from RFC 4273. 178 o bgp4V2PeerCountersTable - A table of per-peer counters for 179 messages and the BGP FSM. 181 o bgp4V2PrefixGaugesTable - A table of per-peer per Address Family 182 Identifer-Subsequent Address Family Identifier (AFI-SAFI) 183 [RFC4760] gauges for prefixes. 185 o bgp4V2NlriTable - A table of per-peer per AFI-SAFI prefix data. 186 This table covers information previously present in 187 bgp4PathAttrTable from RFC 4273. 189 o bgp4V2AdjRibsOutTable - A per-peer per AFI-SAFI table indicating 190 what reachability has been advertised to a given peer. 192 6. Relationship to Other MIB Modules 194 6.1. Relationship to the TCP-MIB 196 The bgp4V2PeerLocalAddrType/bgp4V2PeerLocalAddr/bgp4V2PeerLocalPort 197 and bgp4V2PeerRemoteAddrType/bgp4V2PeerRemoteAddr/ 198 bgp4V2PeerRemotePort objects may provide a suitable index for 199 monitoring the BGP peering session's TCP session via the TCP-MIB 200 [RFC4022]. 202 Note that conducting BGP peering sessions over transport protocols 203 other than TCP over IP are out of scope of the current BGP 204 specifications. 206 6.2. MIB modules required for IMPORTS 208 The following MIB module IMPORTS objects from BGP4V2-TC-MIB 209 [I-D.draft-ietf-idr-bgp4-mibv2-tc], SNMPv2-SMI [RFC2578], SNMPv2-TC 210 [RFC2579], SNMPv2-CONF [RFC2580], INET-ADDRESS-MIB [RFC4001] and 211 SNMP-FRAMEWORK-MIB [RFC3411]. 213 7. Definitions 215 BGP4V2-MIB DEFINITIONS ::= BEGIN 217 IMPORTS 218 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 219 mib-2, Counter32, Gauge32, Unsigned32 220 FROM SNMPv2-SMI 221 InetAddressType, InetAddress, InetPortNumber, 222 InetAutonomousSystemNumber, InetAddressPrefixLength 223 FROM INET-ADDRESS-MIB 224 TruthValue, RowPointer, TimeStamp 225 FROM SNMPv2-TC 226 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 227 FROM SNMPv2-CONF 228 SnmpAdminString 229 FROM SNMP-FRAMEWORK-MIB 230 Bgp4V2IdentifierTC, Bgp4V2AddressFamilyIdentifierTC, 231 Bgp4V2SubsequentAddressFamilyIdentifierTC 232 FROM BGP4V2-TC-MIB; 234 bgp4V2 MODULE-IDENTITY 235 LAST-UPDATED "201002010000Z" 236 ORGANIZATION "IETF IDR Working Group" 237 CONTACT-INFO "E-mail: idr@ietf.org" 239 DESCRIPTION 240 "The MIB module for the BGP-4 protocol. 242 Copyright (C) The IETF Trust (2010). This 243 version of this MIB module is part of RFC XXX; 244 see the RFC itself for full legal notices." 245 -- RFC Editor - replace XXX with RFC number 247 REVISION "201002010000Z" 248 DESCRIPTION 249 "This MIB updates and replaces the BGP MIB defined in 250 RFC 4273." 251 ::= { mib-2 XXX } 253 -- Top level components of this MIB module 255 -- Notifications 256 bgp4V2Notifications OBJECT IDENTIFIER ::= { bgp4V2 0 } 258 -- Objects 259 bgp4V2Objects OBJECT IDENTIFIER ::= { bgp4V2 1 } 261 -- Conformance 262 bgp4V2Conformance OBJECT IDENTIFIER ::= { bgp4V2 2 } 264 -- 265 -- Per-instance BGP discontinuities 266 -- 268 bgp4V2DiscontinuityTable OBJECT-TYPE 269 SYNTAX SEQUENCE OF Bgp4V2DiscontinuityEntry 270 MAX-ACCESS not-accessible 271 STATUS current 272 DESCRIPTION 273 "Table of BGP-4 discontinuities. Discontinuities that have 274 external visibility occur on a per-BGP instance basis. 275 Transitions by a given BGP peer will result in a consistent 276 BGP view within that instance and thus do not represent a 277 discontinuity from a protocol standpoint." 278 ::= { bgp4V2Objects 1 } 280 bgp4V2DiscontinuityEntry OBJECT-TYPE 281 SYNTAX Bgp4V2DiscontinuityEntry 282 MAX-ACCESS not-accessible 283 STATUS current 284 DESCRIPTION 285 "Entry repsenting information about a discontinuity event 286 for a given BGP instance." 287 INDEX { 288 bgp4V2PeerInstance 289 } 290 ::= { bgp4V2DiscontinuityTable 1 } 292 Bgp4V2DiscontinuityEntry ::= SEQUENCE { 293 bgp4V2DiscontinuityTime 294 TimeStamp 295 } 297 bgp4V2DiscontinuityTime OBJECT-TYPE 298 SYNTAX TimeStamp 299 MAX-ACCESS read-only 300 STATUS current 301 DESCRIPTION 302 "The value of sysUpTime at the most recent occasion at which 303 this BGP management instance has suffered a discontinuity." 304 ::= { bgp4V2DiscontinuityEntry 1 } 306 -- 307 -- Per-peer session management information. 308 -- 310 bgp4V2PeerTable OBJECT-TYPE 311 SYNTAX SEQUENCE OF Bgp4V2PeerEntry 312 MAX-ACCESS not-accessible 313 STATUS current 314 DESCRIPTION 315 "BGP peer table. This table contains, one entry per BGP 316 peer, information about the connections with BGP peers." 317 ::= { bgp4V2Objects 2 } 319 bgp4V2PeerEntry OBJECT-TYPE 320 SYNTAX Bgp4V2PeerEntry 321 MAX-ACCESS not-accessible 322 STATUS current 323 DESCRIPTION 324 "Entry containing information about the connection with 325 a remote BGP peer." 326 INDEX { 327 bgp4V2PeerInstance, 328 bgp4V2PeerRemoteAddrType, 329 bgp4V2PeerRemoteAddr 330 } 331 ::= { bgp4V2PeerTable 1 } 333 Bgp4V2PeerEntry ::= SEQUENCE { 334 -- INDEX information 335 bgp4V2PeerInstance 336 Unsigned32, 337 bgp4V2PeerLocalAddrType 338 InetAddressType, 339 bgp4V2PeerLocalAddr 340 InetAddress, 341 bgp4V2PeerRemoteAddrType 342 InetAddressType, 343 bgp4V2PeerRemoteAddr 344 InetAddress, 346 -- Local 347 bgp4V2PeerLocalPort 348 InetPortNumber, 349 bgp4V2PeerLocalAs 350 InetAutonomousSystemNumber, 351 bgp4V2PeerLocalIdentifier 352 Bgp4V2IdentifierTC, 354 -- Remote 355 bgp4V2PeerRemotePort 356 InetPortNumber, 357 bgp4V2PeerRemoteAs 358 InetAutonomousSystemNumber, 359 bgp4V2PeerRemoteIdentifier 360 Bgp4V2IdentifierTC, 362 -- Session status 363 bgp4V2PeerAdminStatus 364 INTEGER, 365 bgp4V2PeerState 366 INTEGER, 367 bgp4V2PeerDescription 368 SnmpAdminString 369 } 371 bgp4V2PeerInstance OBJECT-TYPE 372 SYNTAX Unsigned32 (1..4294967295) 373 MAX-ACCESS not-accessible 374 STATUS current 375 DESCRIPTION 376 "The routing instance index. 378 Some BGP implementations permit the creation of 379 multiple instances of a BGP routing process. An 380 example includes routers running BGP/MPLS IP Virtual 381 Private Networks. 383 Implementations that do not support multiple 384 routing instances should return 1 for this object." 385 ::= { bgp4V2PeerEntry 1 } 387 bgp4V2PeerLocalAddrType OBJECT-TYPE 388 SYNTAX InetAddressType 389 MAX-ACCESS not-accessible 390 STATUS current 391 DESCRIPTION 392 "The address family of the local end of the peering 393 session." 394 ::= { bgp4V2PeerEntry 2 } 396 bgp4V2PeerLocalAddr OBJECT-TYPE 397 SYNTAX InetAddress 398 MAX-ACCESS not-accessible 399 STATUS current 400 DESCRIPTION 401 "The local IP address of this entry's BGP connection." 402 ::= { bgp4V2PeerEntry 3 } 404 bgp4V2PeerRemoteAddrType OBJECT-TYPE 405 SYNTAX InetAddressType 406 MAX-ACCESS not-accessible 407 STATUS current 408 DESCRIPTION 409 "The address family of the remote end of the peering 410 session." 411 ::= { bgp4V2PeerEntry 4 } 413 bgp4V2PeerRemoteAddr OBJECT-TYPE 414 SYNTAX InetAddress 415 MAX-ACCESS not-accessible 416 STATUS current 417 DESCRIPTION 418 "The remote IP address of this entry's BGP peer." 419 ::= { bgp4V2PeerEntry 5 } 421 bgp4V2PeerLocalPort OBJECT-TYPE 422 SYNTAX InetPortNumber 423 MAX-ACCESS read-only 424 STATUS current 425 DESCRIPTION 426 "The local port for the TCP connection between the BGP 427 peers." 428 ::= { bgp4V2PeerEntry 6 } 430 bgp4V2PeerLocalAs OBJECT-TYPE 431 SYNTAX InetAutonomousSystemNumber 432 MAX-ACCESS read-only 433 STATUS current 434 DESCRIPTION 435 "Some implementations of BGP can represent themselves 436 as multiple ASes. This is the AS that this peering 437 session is representing itself as to the remote peer." 438 ::= { bgp4V2PeerEntry 7 } 440 bgp4V2PeerLocalIdentifier OBJECT-TYPE 441 SYNTAX Bgp4V2IdentifierTC 442 MAX-ACCESS read-only 443 STATUS current 444 DESCRIPTION 445 "The BGP Identifier of the local system for this peering 446 session. It is REQUIRED that all bgp4V2PeerLocalIdentifier 447 values for the same bgp4V2PeerInstance be identical." 448 REFERENCE 449 "RFC 4271, Section 4.2, 'BGP Identifier'." 450 ::= { bgp4V2PeerEntry 8 } 452 bgp4V2PeerRemotePort OBJECT-TYPE 453 SYNTAX InetPortNumber 454 MAX-ACCESS read-only 455 STATUS current 456 DESCRIPTION 457 "The remote port for the TCP connection between the BGP 458 peers. 460 Note that the objects bgp4V2PeerLocalAddr, 461 bgp4V2PeerLocalPort, bgp4V2PeerRemoteAddr and 462 bgp4V2PeerRemotePort provide the appropriate reference to 463 the standard MIB TCP connection table, or even the ipv6 464 TCP MIB as in RFC 4022." 465 REFERENCE 466 "RFC 2012 - SNMPv2 Management Information Base for the 467 Transmission Control Protocol using SMIv2. 468 RFC 4022 - IP Version 6 Management Information Base 469 for the Transmission Control Protocol." 470 ::= { bgp4V2PeerEntry 9 } 472 bgp4V2PeerRemoteAs OBJECT-TYPE 473 SYNTAX InetAutonomousSystemNumber 474 MAX-ACCESS read-only 475 STATUS current 476 DESCRIPTION 477 "The remote autonomous system number received in the BGP 478 OPEN message." 479 REFERENCE 480 "RFC 4271, Section 4.2." 481 ::= { bgp4V2PeerEntry 10 } 483 bgp4V2PeerRemoteIdentifier OBJECT-TYPE 484 SYNTAX Bgp4V2IdentifierTC 485 MAX-ACCESS read-only 486 STATUS current 487 DESCRIPTION 488 "The BGP Identifier of this entry's remote BGP peer. 490 This entry should be 0.0.0.0 unless the 491 bgp4V2PeerState is in the openconfirm or the 492 established state." 493 REFERENCE 494 "RFC 4271, Section 4.2, 'BGP Identifier'." 495 ::= { bgp4V2PeerEntry 11 } 497 bgp4V2PeerAdminStatus OBJECT-TYPE 498 SYNTAX INTEGER { 499 halted(1), 500 running(2) 501 } 502 MAX-ACCESS read-only 503 STATUS current 504 DESCRIPTION 505 "Whether or not the BGP FSM for this remote peer is 506 halted or running. The BGP FSM for a remote peer is 507 halted after processing a Stop event. Likewise, it is 508 in the running state after a Start event. 510 The bgp4V2PeerState will generally be in the idle state 511 when the FSM is halted, although some extensions such 512 as Graceful Restart will leave the peer in the Idle 513 state but with the FSM running." 514 REFERENCE 515 "RFC 4271, Section 8.1.2." 516 ::= { bgp4V2PeerEntry 12 } 518 bgp4V2PeerState OBJECT-TYPE 519 SYNTAX INTEGER { 520 idle(1), 521 connect(2), 522 active(3), 523 opensent(4), 524 openconfirm(5), 525 established(6) 526 } 527 MAX-ACCESS read-only 528 STATUS current 529 DESCRIPTION 530 "The BGP peer connection state." 531 REFERENCE 532 "RFC 4271, Section 8.2.2." 533 ::= { bgp4V2PeerEntry 13 } 535 bgp4V2PeerDescription OBJECT-TYPE 536 SYNTAX SnmpAdminString 537 MAX-ACCESS read-only 538 STATUS current 539 DESCRIPTION 540 "A user configured description identifying this peer. When 541 this object is not the empty string, this object SHOULD 542 contain a description that is unique within a given BGP 543 instance for this peer." 544 ::= { bgp4V2PeerEntry 14 } 546 -- 547 -- Per-peer error management information. 548 -- 550 bgp4V2PeerErrorsTable OBJECT-TYPE 551 SYNTAX SEQUENCE OF Bgp4V2PeerErrorsEntry 552 MAX-ACCESS not-accessible 553 STATUS current 554 DESCRIPTION 555 "On a per-peer basis, this table reflects the last 556 protocol-defined error encountered and reported on 557 the peer session." 558 ::= { bgp4V2Objects 3 } 560 bgp4V2PeerErrorsEntry OBJECT-TYPE 561 SYNTAX Bgp4V2PeerErrorsEntry 562 MAX-ACCESS not-accessible 563 STATUS current 564 DESCRIPTION 565 "Each entry contains information about errors sent 566 and received for a particular BGP peer." 567 AUGMENTS { 568 bgp4V2PeerEntry 569 } 570 ::= { bgp4V2PeerErrorsTable 1 } 572 Bgp4V2PeerErrorsEntry ::= SEQUENCE { 573 bgp4V2PeerLastErrorCodeReceived 574 Unsigned32, 575 bgp4V2PeerLastErrorSubCodeReceived 576 Unsigned32, 577 bgp4V2PeerLastErrorReceivedTime 578 TimeStamp, 579 bgp4V2PeerLastErrorReceivedText 580 SnmpAdminString, 581 bgp4V2PeerLastErrorReceivedData 582 OCTET STRING, 583 bgp4V2PeerLastErrorCodeSent 584 Unsigned32, 585 bgp4V2PeerLastErrorSubCodeSent 586 Unsigned32, 587 bgp4V2PeerLastErrorSentTime 588 TimeStamp, 589 bgp4V2PeerLastErrorSentText 590 SnmpAdminString, 591 bgp4V2PeerLastErrorSentData 592 OCTET STRING 593 } 595 bgp4V2PeerLastErrorCodeReceived OBJECT-TYPE 596 SYNTAX Unsigned32 (0..255) 597 MAX-ACCESS read-only 598 STATUS current 599 DESCRIPTION 600 "The last error code received from this peer via 601 NOTIFICATION message on this connection. If no error has 602 occurred, this field is zero." 603 REFERENCE 604 "RFC 4271, Section 4.5. 605 RFC 4486 optionally supported. 606 RFC 3362, Section 5 optionally supported." 607 ::= { bgp4V2PeerErrorsEntry 1 } 609 bgp4V2PeerLastErrorSubCodeReceived OBJECT-TYPE 610 SYNTAX Unsigned32 (0..255) 611 MAX-ACCESS read-only 612 STATUS current 613 DESCRIPTION 614 "The last subcode received from this peer via NOTIFICATION 615 message on this connection. If no error has occurred, this 616 field is zero." 617 REFERENCE 618 "RFC 4271, Section 4.5. 619 RFC 4486 optionally supported. 620 RFC 3362, Section 5 optionally supported." 621 ::= { bgp4V2PeerErrorsEntry 2 } 623 bgp4V2PeerLastErrorReceivedTime OBJECT-TYPE 624 SYNTAX TimeStamp 625 MAX-ACCESS read-only 626 STATUS current 627 DESCRIPTION 628 "The timestamp that the last NOTIFICATION was received from 629 this peer." 630 REFERENCE 631 "RFC 4271, Section 4.5." 632 ::= { bgp4V2PeerErrorsEntry 3 } 634 bgp4V2PeerLastErrorReceivedText OBJECT-TYPE 635 SYNTAX SnmpAdminString 636 MAX-ACCESS read-only 637 STATUS current 638 DESCRIPTION 639 "This object contains an implementation specific 640 explanation of the error that was reported." 641 ::= { bgp4V2PeerErrorsEntry 4 } 643 bgp4V2PeerLastErrorReceivedData OBJECT-TYPE 644 SYNTAX OCTET STRING (SIZE(0..4075)) 645 MAX-ACCESS read-only 646 STATUS current 647 DESCRIPTION 648 "The last error code's data seen by this peer. 650 Per RFC 2578, some implementations may have limitations 651 dealing with OCTET STRINGS larger than 255. Thus, this 652 data may be truncated." 653 REFERENCE 654 "RFC 4271, Section 4.5, 655 RFC 2578, Section 7.1.2, 656 RFC 4486 optionally supported. 657 RFC 3362, Section 5 optionally supported." 658 ::= { bgp4V2PeerErrorsEntry 5 } 660 bgp4V2PeerLastErrorCodeSent OBJECT-TYPE 661 SYNTAX Unsigned32 (0..255) 662 MAX-ACCESS read-only 663 STATUS current 664 DESCRIPTION 665 "The last error code sent to this peer via NOTIFICATION 666 message on this connection. If no error has occurred, this 667 field is zero." 668 REFERENCE 669 "RFC 4271, Section 4.5. 670 RFC 4486 optionally supported. 671 RFC 3362, Section 5 optionally supported." 672 ::= { bgp4V2PeerErrorsEntry 6 } 674 bgp4V2PeerLastErrorSubCodeSent OBJECT-TYPE 675 SYNTAX Unsigned32 (0..255) 676 MAX-ACCESS read-only 677 STATUS current 678 DESCRIPTION 679 "The last subcode sent to this peer via NOTIFICATION 680 message on this connection. If no error has occurred, this 681 field is zero." 682 REFERENCE 683 "RFC 4271, Section 4.5. 684 RFC 4486 optionally supported. 685 RFC 3362, Section 5 optionally supported." 686 ::= { bgp4V2PeerErrorsEntry 7 } 688 bgp4V2PeerLastErrorSentTime OBJECT-TYPE 689 SYNTAX TimeStamp 690 MAX-ACCESS read-only 691 STATUS current 692 DESCRIPTION 693 "The timestamp that the last NOTIFICATION was sent to 694 this peer." 695 REFERENCE 696 "RFC 4271, Section 4.5." 697 ::= { bgp4V2PeerErrorsEntry 8 } 699 bgp4V2PeerLastErrorSentText OBJECT-TYPE 700 SYNTAX SnmpAdminString 701 MAX-ACCESS read-only 702 STATUS current 703 DESCRIPTION 704 "This object contains an implementation specific 705 explanation of the error that is being reported." 706 ::= { bgp4V2PeerErrorsEntry 9 } 708 bgp4V2PeerLastErrorSentData OBJECT-TYPE 709 SYNTAX OCTET STRING (SIZE(0..4075)) 710 MAX-ACCESS read-only 711 STATUS current 712 DESCRIPTION 713 "The last error code's data sent to this peer. 715 Per RFC 2578, some implementations may have limitations 716 dealing with OCTET STRINGS larger than 255. Thus, this 717 data may be truncated." 718 REFERENCE 719 "RFC 4271, Section 4.5, 720 RFC 2578, Section 7.1.2 721 RFC 4486 optionally supported. 722 RFC 3362, Section 5 optionally supported." 723 ::= { bgp4V2PeerErrorsEntry 10 } 725 -- 726 -- Per-peer Event Times 727 -- 729 bgp4V2PeerEventTimesTable OBJECT-TYPE 730 SYNTAX SEQUENCE OF Bgp4V2PeerEventTimesEntry 731 MAX-ACCESS not-accessible 732 STATUS current 733 DESCRIPTION 734 "A table reporting the per-peering session amount 735 of time elapsed and update events since the peering 736 session advanced into the established state." 737 ::= { bgp4V2Objects 4 } 739 bgp4V2PeerEventTimesEntry OBJECT-TYPE 740 SYNTAX Bgp4V2PeerEventTimesEntry 741 MAX-ACCESS not-accessible 742 STATUS current 743 DESCRIPTION 744 "Each row contains a set of statistics about time 745 spent and events encountered in the peer session 746 established state." 747 AUGMENTS { 748 bgp4V2PeerEntry 749 } 750 ::= { bgp4V2PeerEventTimesTable 1 } 752 Bgp4V2PeerEventTimesEntry ::= SEQUENCE { 753 bgp4V2PeerFsmEstablishedTime 754 Gauge32, 755 bgp4V2PeerInUpdatesElapsedTime 756 Gauge32 757 } 759 bgp4V2PeerFsmEstablishedTime OBJECT-TYPE 760 SYNTAX Gauge32 761 UNITS "seconds" 762 MAX-ACCESS read-only 763 STATUS current 764 DESCRIPTION 765 "This timer indicates how long (in seconds) this peer 766 has been in the established state or how long since this 767 peer was last in the established state. It is set to 768 zero when a new peer is configured or when the router is 769 booted. If the peer has never reached the established 770 state, the value remains zero." 771 REFERENCE 772 "RFC 4271, Section 8." 773 ::= { bgp4V2PeerEventTimesEntry 1 } 775 bgp4V2PeerInUpdatesElapsedTime OBJECT-TYPE 776 SYNTAX Gauge32 777 UNITS "seconds" 778 MAX-ACCESS read-only 779 STATUS current 780 DESCRIPTION 781 "Elapsed time (in seconds) since the last BGP UPDATE 782 message was received from the peer. Each time 783 bgpPeerInUpdates is incremented, the value of this 784 object is set to zero (0)." 785 REFERENCE 786 "RFC 4271, Section 4.3. 787 RFC 4271, Section 8.2.2, Established state." 789 ::= { bgp4V2PeerEventTimesEntry 2 } 791 -- 792 -- Per-Peer Configured Timers 793 -- 795 bgp4V2PeerConfiguredTimersTable OBJECT-TYPE 796 SYNTAX SEQUENCE OF Bgp4V2PeerConfiguredTimersEntry 797 MAX-ACCESS not-accessible 798 STATUS current 799 DESCRIPTION 800 "Per peer management data on BGP session timers." 801 ::= { bgp4V2Objects 5 } 803 bgp4V2PeerConfiguredTimersEntry OBJECT-TYPE 804 SYNTAX Bgp4V2PeerConfiguredTimersEntry 805 MAX-ACCESS not-accessible 806 STATUS current 807 DESCRIPTION 808 "Each entry corresponds to the current state of 809 BGP timers on a given peering session." 810 AUGMENTS { 811 bgp4V2PeerEntry 812 } 813 ::= { bgp4V2PeerConfiguredTimersTable 1 } 815 Bgp4V2PeerConfiguredTimersEntry ::= SEQUENCE { 816 bgp4V2PeerConnectRetryInterval 817 Unsigned32, 818 bgp4V2PeerHoldTimeConfigured 819 Unsigned32, 820 bgp4V2PeerKeepAliveConfigured 821 Unsigned32, 822 bgp4V2PeerMinASOrigInterval 823 Unsigned32, 824 bgp4V2PeerMinRouteAdverInterval 825 Unsigned32 826 } 828 bgp4V2PeerConnectRetryInterval OBJECT-TYPE 829 SYNTAX Unsigned32 (1..65535) 830 UNITS "seconds" 831 MAX-ACCESS read-only 832 STATUS current 833 DESCRIPTION 834 "Time interval (in seconds) for the ConnectRetry timer. 835 The suggested value for this timer is 120 seconds." 836 REFERENCE 837 "RFC 4271, Section 8.2.2. This is the value used 838 to initialize the 'ConnectRetryTimer'." 840 ::= { bgp4V2PeerConfiguredTimersEntry 1 } 842 bgp4V2PeerHoldTimeConfigured OBJECT-TYPE 843 SYNTAX Unsigned32 ( 0 | 3..65535 ) 844 UNITS "seconds" 845 MAX-ACCESS read-only 846 STATUS current 847 DESCRIPTION 848 "Time interval (in seconds) for the Hold Timer 849 established with the peer. The value of this object is 850 calculated by this BGP speaker, using the smaller of the 851 values in bgpPeerHoldTimeConfigured and the Hold Time 852 received in the OPEN message. 854 This value must be at least three seconds if it is not 855 zero (0). 857 If the Hold Timer has not been established with the 858 peer this object MUST have a value of zero (0). 860 If the bgpPeerHoldTimeConfigured object has a value of 861 (0), then this object MUST have a value of (0)." 862 REFERENCE 863 "RFC 4271, Section 4.2." 864 ::= { bgp4V2PeerConfiguredTimersEntry 2 } 866 bgp4V2PeerKeepAliveConfigured OBJECT-TYPE 867 SYNTAX Unsigned32 ( 0 | 1..21845 ) 868 UNITS "seconds" 869 MAX-ACCESS read-only 870 STATUS current 871 DESCRIPTION 872 "Time interval (in seconds) for the KeepAlive timer 873 configured for this BGP speaker with this peer. The 874 value of this object will only determine the KEEPALIVE 875 messages' frequency relative to the value specified in 876 bgpPeerHoldTimeConfigured; the actual time interval for 877 the KEEPALIVE messages is indicated by bgpPeerKeepAlive. 879 A reasonable maximum value for this timer would be one 880 third of that of bgpPeerHoldTimeConfigured. 882 If the value of this object is zero (0), no periodic 883 KEEPALIVE messages are sent to the peer after the BGP 884 connection has been established. The suggested value 885 for this timer is 30 seconds." 886 REFERENCE 887 "RFC 4271, Section 4.4. 889 RFC 4271, Section 10." 890 ::= { bgp4V2PeerConfiguredTimersEntry 3 } 892 bgp4V2PeerMinASOrigInterval OBJECT-TYPE 893 SYNTAX Unsigned32 (0..65535) 894 UNITS "seconds" 895 MAX-ACCESS read-only 896 STATUS current 897 DESCRIPTION 898 "Time interval (in seconds) for the 899 MinASOriginationInterval timer. 901 The suggested value for this timer is 15 seconds." 902 REFERENCE 903 "RFC 4271, Section 9.2.1.2. 904 RFC 4271, Section 10." 905 ::= { bgp4V2PeerConfiguredTimersEntry 4 } 907 bgp4V2PeerMinRouteAdverInterval OBJECT-TYPE 908 SYNTAX Unsigned32 (0..65535) 909 UNITS "seconds" 910 MAX-ACCESS read-only 911 STATUS current 912 DESCRIPTION 913 "Time interval (in seconds) for the 914 MinRouteAdvertisementInterval timer. 916 The suggested value for this timer is 30 seconds for 917 EBGP connections and 5 seconds for IBGP connections." 918 REFERENCE 919 "RFC 4271, Section 9.2.1.1. 920 RFC 4271, Section 10." 921 ::= { bgp4V2PeerConfiguredTimersEntry 5 } 923 -- 924 -- Per-Peer Negotiated Timers 925 -- 927 bgp4V2PeerNegotiatedTimersTable OBJECT-TYPE 928 SYNTAX SEQUENCE OF Bgp4V2PeerNegotiatedTimersEntry 929 MAX-ACCESS not-accessible 930 STATUS current 931 DESCRIPTION 932 "Configured values of per-peer timers are seen 933 in the bgp4V2PeerConfiguredTimersTable. 935 Values in this table reflect the current 936 operational values, after negotiation from values 937 derived from initial configuration." 938 ::= { bgp4V2Objects 6 } 940 bgp4V2PeerNegotiatedTimersEntry OBJECT-TYPE 941 SYNTAX Bgp4V2PeerNegotiatedTimersEntry 942 MAX-ACCESS not-accessible 943 STATUS current 944 DESCRIPTION 945 "Each entry reflects a value of the currently 946 operational, negotiated timer as reflected in the 947 Bgp4V2PeerNegotiatedTimersEntry." 948 AUGMENTS { 949 bgp4V2PeerEntry 950 } 951 ::= { bgp4V2PeerNegotiatedTimersTable 1 } 953 Bgp4V2PeerNegotiatedTimersEntry ::= SEQUENCE { 954 bgp4V2PeerHoldTime 955 Unsigned32, 956 bgp4V2PeerKeepAlive 957 Unsigned32 958 } 960 bgp4V2PeerHoldTime OBJECT-TYPE 961 SYNTAX Unsigned32 ( 0 | 3..65535 ) 962 UNITS "seconds" 963 MAX-ACCESS read-only 964 STATUS current 965 DESCRIPTION 966 "The value of this object is calculated by this BGP 967 Speaker as being; 969 zero (0) - if this was the value sent by the peer and 970 this value is permitted by this BGP Speaker. In this 971 case, no keepalive messages are sent and the Hold Timer 972 is not set. 974 At least three (3). This value is the smaller of 975 the value sent by this peer in the OPEN message and 976 bgp4V2PeerHoldTimeConfigured for this peer. 978 If the peer is not in the established state, the value 979 of this object is zero (0)." 980 REFERENCE 981 "RFC 4271, Section 4.2." 982 ::= { bgp4V2PeerNegotiatedTimersEntry 1 } 984 bgp4V2PeerKeepAlive OBJECT-TYPE 985 SYNTAX Unsigned32 ( 0 | 1..21845 ) 986 UNITS "seconds" 987 MAX-ACCESS read-only 988 STATUS current 989 DESCRIPTION 990 "Time interval in seconds for the KeepAlive timer 991 established with the peer. The value of this object 992 is calculated by this BGP speaker such that, when 993 compared with bgp4V2PeerHoldTime, it has the same 994 proportion as what bgp4V2PeerKeepAliveConfigured has 995 when compared with bgp4V2PeerHoldTimeConfigured. If 996 the value of this object is zero (0), it indicates 997 that the KeepAlive timer has not been established 998 with the peer, or, the value of 999 bgp4V2PeerKeepAliveConfigured is zero (0). 1001 If the peer is not in the established state, the value 1002 of this object is zero (0)." 1003 REFERENCE 1004 "RFC 4271, Section 4.4." 1005 ::= { bgp4V2PeerNegotiatedTimersEntry 2 } 1007 -- 1008 -- Per-peer counters 1009 -- 1011 bgp4V2PeerCountersTable OBJECT-TYPE 1012 SYNTAX SEQUENCE OF Bgp4V2PeerCountersEntry 1013 MAX-ACCESS not-accessible 1014 STATUS current 1015 DESCRIPTION 1016 "The counters associated with a BGP Peer." 1017 ::= { bgp4V2Objects 7 } 1019 bgp4V2PeerCountersEntry OBJECT-TYPE 1020 SYNTAX Bgp4V2PeerCountersEntry 1021 MAX-ACCESS not-accessible 1022 STATUS current 1023 DESCRIPTION 1024 "Each entry contains counters of message transmissions 1025 and FSM transitions for a given BGP Peering session." 1026 AUGMENTS { 1027 bgp4V2PeerEntry 1028 } 1029 ::= { bgp4V2PeerCountersTable 1 } 1031 Bgp4V2PeerCountersEntry ::= SEQUENCE { 1032 bgp4V2PeerInUpdates 1033 Counter32, 1034 bgp4V2PeerOutUpdates 1035 Counter32, 1036 bgp4V2PeerInTotalMessages 1037 Counter32, 1038 bgp4V2PeerOutTotalMessages 1039 Counter32, 1040 bgp4V2PeerFsmEstablishedTransitions 1041 Counter32 1042 } 1044 bgp4V2PeerInUpdates OBJECT-TYPE 1045 SYNTAX Counter32 1046 MAX-ACCESS read-only 1047 STATUS current 1048 DESCRIPTION 1049 "The number of BGP UPDATE messages received on this 1050 connection." 1051 ::= { bgp4V2PeerCountersEntry 1 } 1053 bgp4V2PeerOutUpdates OBJECT-TYPE 1054 SYNTAX Counter32 1055 MAX-ACCESS read-only 1056 STATUS current 1057 DESCRIPTION 1058 "The number of BGP UPDATE messages transmitted on this 1059 connection." 1060 ::= { bgp4V2PeerCountersEntry 2 } 1062 bgp4V2PeerInTotalMessages OBJECT-TYPE 1063 SYNTAX Counter32 1064 MAX-ACCESS read-only 1065 STATUS current 1066 DESCRIPTION 1067 "The total number of messages received from the remote 1068 peer on this connection." 1069 ::= { bgp4V2PeerCountersEntry 3 } 1071 bgp4V2PeerOutTotalMessages OBJECT-TYPE 1072 SYNTAX Counter32 1073 MAX-ACCESS read-only 1074 STATUS current 1075 DESCRIPTION 1076 "The total number of messages transmitted to the remote 1077 peer on this connection." 1078 ::= { bgp4V2PeerCountersEntry 4 } 1080 bgp4V2PeerFsmEstablishedTransitions OBJECT-TYPE 1081 SYNTAX Counter32 1082 MAX-ACCESS read-only 1083 STATUS current 1084 DESCRIPTION 1085 "The total number of times the BGP FSM transitioned into 1086 the established state for this peer." 1087 ::= { bgp4V2PeerCountersEntry 5 } 1089 -- 1090 -- Per-Peer Prefix Gauges 1091 -- 1093 bgp4V2PrefixGaugesTable OBJECT-TYPE 1094 SYNTAX SEQUENCE OF Bgp4V2PrefixCountersEntry 1095 MAX-ACCESS not-accessible 1096 STATUS current 1097 DESCRIPTION 1098 "Additional per-peer, per AFI-SAFI counters for 1099 prefixes" 1100 ::= { bgp4V2Objects 8 } 1102 bgp4V2PrefixGaugesEntry OBJECT-TYPE 1103 SYNTAX Bgp4V2PrefixCountersEntry 1104 MAX-ACCESS not-accessible 1105 STATUS current 1106 DESCRIPTION 1107 "Entry containing information about a bgp-peers prefix 1108 counters." 1109 INDEX { 1110 bgp4V2PeerInstance, 1111 bgp4V2PeerRemoteAddrType, 1112 bgp4V2PeerRemoteAddr, 1113 bgp4V2PrefixGaugesAfi, 1114 bgp4V2PrefixGaugesSafi 1115 } 1116 ::= { bgp4V2PrefixGaugesTable 1 } 1118 Bgp4V2PrefixCountersEntry ::= SEQUENCE { 1119 bgp4V2PrefixGaugesAfi 1120 Bgp4V2AddressFamilyIdentifierTC, 1121 bgp4V2PrefixGaugesSafi 1122 Bgp4V2SubsequentAddressFamilyIdentifierTC, 1123 bgp4V2PrefixInPrefixes 1124 Gauge32, 1125 bgp4V2PrefixInPrefixesAccepted 1126 Gauge32, 1127 bgp4V2PrefixOutPrefixes 1128 Gauge32 1130 } 1132 bgp4V2PrefixGaugesAfi OBJECT-TYPE 1133 SYNTAX Bgp4V2AddressFamilyIdentifierTC 1134 MAX-ACCESS not-accessible 1135 STATUS current 1136 DESCRIPTION 1137 "The AFI index of the per-peer, per prefix counters" 1138 ::= { bgp4V2PrefixGaugesEntry 1 } 1140 bgp4V2PrefixGaugesSafi OBJECT-TYPE 1141 SYNTAX Bgp4V2SubsequentAddressFamilyIdentifierTC 1142 MAX-ACCESS not-accessible 1143 STATUS current 1144 DESCRIPTION 1145 "The SAFI index of the per-peer, per prefix counters" 1146 ::= { bgp4V2PrefixGaugesEntry 2 } 1148 bgp4V2PrefixInPrefixes OBJECT-TYPE 1149 SYNTAX Gauge32 1150 MAX-ACCESS read-only 1151 STATUS current 1152 DESCRIPTION 1153 "The number of prefixes received from a peer and are 1154 stored in the Adj-Ribs-In for that peer. 1156 Note that this number does not reflect prefixes that 1157 have been discarded due to policy." 1158 REFERENCE 1159 "RFC 4271, Sections 3.2 and 9." 1160 ::= { bgp4V2PrefixGaugesEntry 3 } 1162 bgp4V2PrefixInPrefixesAccepted OBJECT-TYPE 1163 SYNTAX Gauge32 1164 MAX-ACCESS read-only 1165 STATUS current 1166 DESCRIPTION 1167 "The number of prefixes for a peer that are installed 1168 in the Adj-Ribs-In and are eligible to become active 1169 in the Loc-Rib." 1170 REFERENCE 1171 "RFC 4271, Sections 3.2 and 9." 1172 ::= { bgp4V2PrefixGaugesEntry 4 } 1174 bgp4V2PrefixOutPrefixes OBJECT-TYPE 1175 SYNTAX Gauge32 1176 MAX-ACCESS read-only 1177 STATUS current 1178 DESCRIPTION 1179 "The number of prefixes for a peer that are installed 1180 in that peer's Adj-Ribs-Out." 1181 REFERENCE 1182 "RFC 4271, Sections 3.2 and 9." 1183 ::= { bgp4V2PrefixGaugesEntry 5 } 1185 -- 1186 -- BGP NLRI 1187 -- 1189 bgp4V2NlriTable OBJECT-TYPE 1190 SYNTAX SEQUENCE OF Bgp4V2NlriEntry 1191 MAX-ACCESS not-accessible 1192 STATUS current 1193 DESCRIPTION 1194 "The BGP-4 Received Path Attribute Table contains 1195 information about paths to destination networks 1196 received from all BGP4 peers. Collectively, this 1197 represents the Adj-Ribs-In. The route where 1198 bgp4V2NlriBest is true represents, for this NLRI, 1199 the route that is installed in the LocRib from the 1200 Adj-Ribs-In." 1201 REFERENCE 1202 "RFC 4271, Sections 3.2 and 9." 1203 ::= { bgp4V2Objects 9 } 1205 bgp4V2NlriEntry OBJECT-TYPE 1206 SYNTAX Bgp4V2NlriEntry 1207 MAX-ACCESS not-accessible 1208 STATUS current 1209 DESCRIPTION 1210 "Information about a path to a network." 1211 INDEX { 1212 bgp4V2PeerInstance, 1213 bgp4V2NlriAfi, 1214 bgp4V2NlriSafi, 1215 bgp4V2NlriPrefixType, 1216 bgp4V2NlriPrefix, 1217 bgp4V2NlriPrefixLen, 1218 bgp4V2PeerRemoteAddrType, 1219 bgp4V2PeerRemoteAddr, 1220 bgp4V2NlriIndex 1221 } 1222 ::= { bgp4V2NlriTable 1 } 1224 Bgp4V2NlriEntry ::= SEQUENCE { 1225 bgp4V2NlriIndex 1226 Unsigned32, 1227 bgp4V2NlriAfi 1228 Bgp4V2AddressFamilyIdentifierTC, 1229 bgp4V2NlriSafi 1230 Bgp4V2SubsequentAddressFamilyIdentifierTC, 1231 bgp4V2NlriPrefixType 1232 InetAddressType, 1233 bgp4V2NlriPrefix 1234 InetAddress, 1235 bgp4V2NlriPrefixLen 1236 InetAddressPrefixLength, 1237 bgp4V2NlriBest 1238 TruthValue, 1239 bgp4V2NlriCalcLocalPref 1240 Unsigned32, 1241 bgp4V2NlriOrigin 1242 INTEGER, 1243 bgp4V2NlriNextHopAddrType 1244 InetAddressType, 1245 bgp4V2NlriNextHopAddr 1246 InetAddress, 1247 bgp4V2NlriLinkLocalNextHopAddrType 1248 InetAddressType, 1249 bgp4V2NlriLinkLocalNextHopAddr 1250 InetAddress, 1251 bgp4V2NlriLocalPrefPresent 1252 TruthValue, 1253 bgp4V2NlriLocalPref 1254 Unsigned32, 1255 bgp4V2NlriMedPresent 1256 TruthValue, 1257 bgp4V2NlriMed 1258 Unsigned32, 1259 bgp4V2NlriAtomicAggregate 1260 INTEGER, 1261 bgp4V2NlriAggregatorPresent 1262 TruthValue, 1263 bgp4V2NlriAggregatorAS 1264 InetAutonomousSystemNumber, 1265 bgp4V2NlriAggregatorAddr 1266 Bgp4V2IdentifierTC, 1267 bgp4V2NlriAsPathCalcLength 1268 Unsigned32, 1269 bgp4V2NlriAsPathString 1270 SnmpAdminString, 1271 bgp4V2NlriAsPath 1272 OCTET STRING, 1273 bgp4V2NlriPathAttrUnknown 1274 OCTET STRING 1275 } 1277 bgp4V2NlriIndex OBJECT-TYPE 1278 SYNTAX Unsigned32 1279 MAX-ACCESS not-accessible 1280 STATUS current 1281 DESCRIPTION 1282 "This index allows for multiple instances of a base 1283 prefix for a certain AFI-SAFI from a given peer. 1284 This is currently useful for two things: 1285 1. Allowing for a peer in future implementations to 1286 send more than a single route instance. 1287 2. Allow for extensions which extend the NLRI field 1288 to send the same prefix while utilizing other 1289 extension specific information. An example of 1290 this is RFC 3107 - Carrying MPLS labels in BGP." 1291 REFERENCE 1292 "RFC 3107 - Carrying Label Information in BGP-4." 1293 ::= { bgp4V2NlriEntry 1 } 1295 bgp4V2NlriAfi OBJECT-TYPE 1296 SYNTAX Bgp4V2AddressFamilyIdentifierTC 1297 MAX-ACCESS not-accessible 1298 STATUS current 1299 DESCRIPTION 1300 "The address family of the prefix for this NLRI. 1302 Note that the AFI is not necessarily equivalent to 1303 the an InetAddressType." 1304 REFERENCE 1305 "RFC 4760 - Multiprotocol Extensions for BGP-4" 1306 ::= { bgp4V2NlriEntry 2 } 1308 bgp4V2NlriSafi OBJECT-TYPE 1309 SYNTAX Bgp4V2SubsequentAddressFamilyIdentifierTC 1310 MAX-ACCESS not-accessible 1311 STATUS current 1312 DESCRIPTION 1313 "The subsequent address family of the prefix for 1314 this NLRI" 1315 REFERENCE 1316 "RFC 4760 - Multiprotocol Extensions for BGP-4" 1317 ::= { bgp4V2NlriEntry 3 } 1319 bgp4V2NlriPrefixType OBJECT-TYPE 1320 SYNTAX InetAddressType 1321 MAX-ACCESS not-accessible 1322 STATUS current 1323 DESCRIPTION 1324 "The type of the IP address prefix in the 1325 Network Layer Reachability Information field. 1326 The value of this object is derived from the 1327 appropriate value from the bgp4V2NlriAfi field. 1328 Where an appropriate InetAddressType is not 1329 available, the value of the object must be 1330 unknown(0)." 1331 ::= { bgp4V2NlriEntry 4 } 1333 bgp4V2NlriPrefix OBJECT-TYPE 1334 SYNTAX InetAddress 1335 MAX-ACCESS not-accessible 1336 STATUS current 1337 DESCRIPTION 1338 "An IP address prefix in the Network Layer 1339 Reachability Information field. This object 1340 is an IP address containing the prefix with 1341 length specified by bgp4V2NlriPrefixLen. 1342 Any bits beyond the length specified by 1343 bgp4V2NlriPrefixLen are zeroed." 1344 REFERENCE 1345 "RFC 4271, Section 4.3." 1346 ::= { bgp4V2NlriEntry 5 } 1348 bgp4V2NlriPrefixLen OBJECT-TYPE 1349 SYNTAX InetAddressPrefixLength 1350 MAX-ACCESS not-accessible 1351 STATUS current 1352 DESCRIPTION 1353 "Length in bits of the address prefix in 1354 the Network Layer Reachability Information field." 1355 ::= { bgp4V2NlriEntry 6 } 1357 bgp4V2NlriBest OBJECT-TYPE 1358 SYNTAX TruthValue 1359 MAX-ACCESS read-only 1360 STATUS current 1361 DESCRIPTION 1362 "An indication of whether or not this route 1363 was chosen as the best BGP4 route for this 1364 destination." 1365 REFERENCE 1366 "RFC 4271, Section 9.1.2." 1367 ::= { bgp4V2NlriEntry 7 } 1369 bgp4V2NlriCalcLocalPref OBJECT-TYPE 1370 SYNTAX Unsigned32 1371 MAX-ACCESS read-only 1372 STATUS current 1373 DESCRIPTION 1374 "The degree of preference calculated by the 1375 receiving BGP4 speaker for an advertised 1376 route. 1378 In the case where this prefix is ineligible, the 1379 value of this object will be zero (0)." 1380 REFERENCE 1381 "RFC 4271, Section 9.1.1" 1382 ::= { bgp4V2NlriEntry 8 } 1384 bgp4V2NlriOrigin OBJECT-TYPE 1385 SYNTAX INTEGER { 1386 igp(1),-- networks are interior 1387 egp(2),-- networks learned via the EGP protocol 1388 incomplete(3) -- networks that 1389 -- are learned by some other 1390 -- means 1391 } 1392 MAX-ACCESS read-only 1393 STATUS current 1394 DESCRIPTION 1395 "The ultimate origin of the path information." 1396 REFERENCE 1397 "RFC 4271, Section 4.3. 1398 RFC 4271, Section 5.1.1." 1399 ::= { bgp4V2NlriEntry 9 } 1401 bgp4V2NlriNextHopAddrType OBJECT-TYPE 1402 SYNTAX InetAddressType 1403 MAX-ACCESS read-only 1404 STATUS current 1405 DESCRIPTION 1406 "The address family of the address for 1407 the border router that should be used 1408 to access the destination network." 1409 ::= { bgp4V2NlriEntry 10 } 1411 bgp4V2NlriNextHopAddr OBJECT-TYPE 1412 SYNTAX InetAddress (SIZE(4..20)) 1413 MAX-ACCESS read-only 1414 STATUS current 1415 DESCRIPTION 1416 "The address of the border router that 1417 should be used to access the destination 1418 network. This address is the nexthop 1419 address received in the UPDATE packet associated with 1420 this prefix. 1422 Note that for RFC2545 style double nexthops, 1423 this object will always contain the global scope 1424 nexthop. bgpPathAttrLinkLocalNextHop will contain 1425 the linklocal scope nexthop, if it is present. 1427 In the case a mechanism is developed to use only a link 1428 local nexthop, bgp4V2NlriNextHopAddr will contain the 1429 link local nexthop." 1430 REFERENCE 1431 "RFC 4271, Section 4.3, 1432 RFC 4271, Section 5.1.3, 1433 RFC 2545, Section 3." 1434 ::= { bgp4V2NlriEntry 11 } 1436 bgp4V2NlriLinkLocalNextHopAddrType OBJECT-TYPE 1437 SYNTAX InetAddressType 1438 MAX-ACCESS read-only 1439 STATUS current 1440 DESCRIPTION 1441 "The address type for IPv6 link local addresses. 1442 This is present only when receiving RFC 2545 1443 style double nexthops. 1445 This object is optionally present in BGP 1446 implementations that do not support IPv6. 1448 When no IPv6 link local nexthop is present, the value of 1449 this object should be unknown(0)." 1450 REFERENCE 1451 "RFC 2545, Section 3." 1452 ::= { bgp4V2NlriEntry 12 } 1454 bgp4V2NlriLinkLocalNextHopAddr OBJECT-TYPE 1455 SYNTAX InetAddress 1456 MAX-ACCESS read-only 1457 STATUS current 1458 DESCRIPTION 1459 "This value contains an IPv6 link local address 1460 and is present only when receiving RFC 2545 style 1461 double nexthops. 1463 This object is optionally present in BGP 1464 implementations that do not support IPv6. 1466 When no IPv6 link local nexthop is present, the length of 1467 this object should be zero." 1468 REFERENCE 1469 "RFC 2545, Section 3." 1470 ::= { bgp4V2NlriEntry 13 } 1472 bgp4V2NlriLocalPrefPresent OBJECT-TYPE 1473 SYNTAX TruthValue 1474 MAX-ACCESS read-only 1475 STATUS current 1476 DESCRIPTION 1477 "This value is true when the LOCAL_PREF value was sent in 1478 the UPDATE message." 1479 ::= { bgp4V2NlriEntry 14 } 1481 bgp4V2NlriLocalPref OBJECT-TYPE 1482 SYNTAX Unsigned32 1483 MAX-ACCESS read-only 1484 STATUS current 1485 DESCRIPTION 1486 "The originating BGP4 speakers degree of preference for an 1487 advertised route." 1488 REFERENCE 1489 "RFC 4271, Section 4.3. 1490 RFC 4271, Section 5.1.5." 1491 ::= { bgp4V2NlriEntry 15 } 1493 bgp4V2NlriMedPresent OBJECT-TYPE 1494 SYNTAX TruthValue 1495 MAX-ACCESS read-only 1496 STATUS current 1497 DESCRIPTION 1498 "This value is true when the MED value was sent in 1499 the UPDATE message." 1500 ::= { bgp4V2NlriEntry 16 } 1502 bgp4V2NlriMed OBJECT-TYPE 1503 SYNTAX Unsigned32 1504 MAX-ACCESS read-only 1505 STATUS current 1506 DESCRIPTION 1507 "This metric is used to discriminate between multiple 1508 exit points to an adjacent autonomous system. When the MED 1509 value is absent but has a calculated default value, this 1510 object will contain the calculated value." 1511 REFERENCE 1512 "RFC 4271, Section 4.3. 1513 RFC 4271, Section 5.1.4." 1515 ::= { bgp4V2NlriEntry 17 } 1517 bgp4V2NlriAtomicAggregate OBJECT-TYPE 1518 SYNTAX TruthValue 1519 MAX-ACCESS read-only 1520 STATUS current 1521 DESCRIPTION 1522 "This value is true when the ATOMIC_AGGREGATE Path Attribute 1523 is present and indicates that the NLRI MUST NOT be made 1524 more specific." 1525 REFERENCE 1526 "RFC 4271, Sections 5.1.6 and 9.1.4." 1527 ::= { bgp4V2NlriEntry 18 } 1529 bgp4V2NlriAggregatorPresent OBJECT-TYPE 1530 SYNTAX TruthValue 1531 MAX-ACCESS read-only 1532 STATUS current 1533 DESCRIPTION 1534 "This value is true when the AGGREGATOR path attribute 1535 was sent in the UPDATE message." 1536 ::= { bgp4V2NlriEntry 19 } 1538 bgp4V2NlriAggregatorAS OBJECT-TYPE 1539 SYNTAX InetAutonomousSystemNumber 1540 MAX-ACCESS read-only 1541 STATUS current 1542 DESCRIPTION 1543 "The AS number of the last BGP4 speaker that performed route 1544 aggregation. When bgp4V2NlriAggregatorPresent is 1545 false, the value of this object should be zero (0)." 1546 REFERENCE 1547 "RFC 4271, Section 5.1.7. 1548 RFC 4271, Section 9.2.2.2." 1549 ::= { bgp4V2NlriEntry 20 } 1551 bgp4V2NlriAggregatorAddr OBJECT-TYPE 1552 SYNTAX Bgp4V2IdentifierTC 1553 MAX-ACCESS read-only 1554 STATUS current 1555 DESCRIPTION 1556 "The IP address of the last BGP4 speaker that performed 1557 route aggregation. When bgp4V2NlriAggregatorPresent is 1558 false, the value of this object should be 0.0.0.0" 1559 REFERENCE 1560 "RFC 4271, Section 5.1.7. 1561 RFC 4271, Section 9.2.2.2." 1562 ::= { bgp4V2NlriEntry 21 } 1564 bgp4V2NlriAsPathCalcLength OBJECT-TYPE 1565 SYNTAX Unsigned32 1566 MAX-ACCESS read-only 1567 STATUS current 1568 DESCRIPTION 1569 "This value represents the calculated length of the 1570 AS Path according to the rules of the BGP 1571 specification. This value is used in route selection." 1572 REFERENCE 1573 "RFC 4271, Section 9.1.2.2.a" 1574 ::= { bgp4V2NlriEntry 22 } 1576 bgp4V2NlriAsPathString OBJECT-TYPE 1577 SYNTAX SnmpAdminString 1578 MAX-ACCESS read-only 1579 STATUS current 1580 DESCRIPTION 1581 "This is a string depicting the autonomous system 1582 path to this network which was received from the 1583 peer which advertised it. The format of the string 1584 is implementation-dependent, and should be designed 1585 for operator readability. 1587 Note that SnmpAdminString is only capable of representing a 1588 maximum of 255 characters. This may lead to the string 1589 being truncated in the presence of a large AS Path. It is 1590 RECOMMENDED that when this object's contents will be 1591 truncated that the final 3 octets be reserved for the 1592 ellipses string, '...'. bgp4V2NlriAsPath may give access 1593 to the full AS Path." 1594 ::= { bgp4V2NlriEntry 23 } 1596 -- Maximum size of the following is derived as 1597 -- 4096 max message size 1598 -- - 16 BGP message marker bytes 1599 -- - 2 BGP message size 1600 -- - 1 BGP message type (UPDATE with unknown attr) 1601 -- - 2 UPDATE routes length (even assuming no routes) 1602 -- - 2 UPDATE path attributes length 1603 -- - 1 path attribute flag octet 1604 -- --------- 1605 -- 4072 bytes maximum per-message attribute value data 1607 bgp4V2NlriAsPath OBJECT-TYPE 1608 SYNTAX OCTET STRING (SIZE(2..4072)) 1609 MAX-ACCESS read-only 1610 STATUS current 1611 DESCRIPTION 1612 "In order to provide a canonicalized form of the BGP-4 1613 AS_PATH along with the human-readable 1614 bgp4V2NlriAsPathString, which may be truncated, this object 1615 contains the contents of the BGP-4 AS_PATH Path Attribute. 1616 This object may be parsed using the rules defined for 1617 Four-octet ASes as defined in RFC 4893. RFC 4271, Section 1618 4.3, 'Path Attributes: b) AS_PATH' as amended by RFC 5065, 1619 Section 3 defines the general format of the AS_PATH path 1620 attribute and its code points. 1622 In brief, the AS_PATH is composed of a sequence of AS 1623 Segments. Each AS Segment is represented by a triple: 1624 . 1627 The path segment type and path segment length fields are 1628 one octet in length each. 1630 The path segment type field may be one of: 1631 1 - AS_SET (RFC 4721, Section 4.3) 1632 2 - AS_SEQUENCE (RFC 4721, Section 4.3) 1633 3 - AS_CONFED_SEQUENCE (RFC 3065, Section 5) 1634 4 - AS_CONFED_SET (RFC 3065, Section 5) 1636 The path segment length field contains the number of ASes 1637 (not the number of octets) in the path segment value field. 1639 The path segment value field contains one or more AS 1640 numbers, each encoded as a 4-octet length field in network 1641 byte order. 1643 Note that since an SNMP agent may truncate this object to 1644 less than its maximum theoretical length of 4072 octets 1645 users of this object should be prepared to deal with a 1646 truncated and thus malformed AS_PATH. It is RECOMMENDED 1647 that when such truncation would occur on the boundary of an 1648 encoded AS that the partial AS be discarded from this 1649 object and the object's size be adjusted accordingly. 1650 Further, it is also RECOMMENDED that when such truncation, 1651 either alone or in conjuction with the truncation of a 1652 partially encoded AS described previously, would yield an 1653 empty path segment value field that the path segment type 1654 and path segment length components of the truncated AS_PATH 1655 also be discarded and the object's size be adjusted 1656 accordingly." 1657 REFERENCE 1658 "RFC 4271, Section 4.3. 1659 RFC 5065, Section 5. 1661 RFC 4893." 1662 ::= { bgp4V2NlriEntry 24 } 1664 bgp4V2NlriPathAttrUnknown OBJECT-TYPE 1665 SYNTAX OCTET STRING (SIZE(0..4072)) 1666 MAX-ACCESS read-only 1667 STATUS current 1668 DESCRIPTION 1669 "Path Attributes not understood by this implementation 1670 SHOULD be be presented in this object. Those Path 1671 Attributes use the type, length, value encoding documented 1672 in RFC 4271, Section 4.3, 'Path Attributes'. 1674 Note that since an SNMP agent may truncate this object to 1675 less than its maximum theoretical length of 4072 octets 1676 users of this object should be prepared to deal with a 1677 truncated and thus malformed Path Attribute." 1678 REFERENCE 1679 "RFC 4271, Section 4.3." 1680 ::= { bgp4V2NlriEntry 25 } 1682 -- 1683 -- Adj-Ribs-Out Table 1684 -- 1686 bgp4V2AdjRibsOutTable OBJECT-TYPE 1687 SYNTAX SEQUENCE OF Bgp4V2AdjRibsOutEntry 1688 MAX-ACCESS not-accessible 1689 STATUS current 1690 DESCRIPTION 1691 "This table contains on a per-peer basis one or more 1692 routes from the bgp4V2NlriTable that have been 1693 placed in this peer's Adj-Ribs-Out." 1694 REFERENCE 1695 "RFC 4271, Section 3.2." 1696 ::= { bgp4V2Objects 10 } 1698 bgp4V2AdjRibsOutEntry OBJECT-TYPE 1699 SYNTAX Bgp4V2AdjRibsOutEntry 1700 MAX-ACCESS not-accessible 1701 STATUS current 1702 DESCRIPTION 1703 "List of BGP routes that have been placed into a 1704 peer's Adj-Ribs-Out." 1705 INDEX { 1706 bgp4V2PeerInstance, 1707 bgp4V2NlriAfi, 1708 bgp4V2NlriSafi, 1709 bgp4V2NlriPrefixType, 1710 bgp4V2NlriPrefix, 1711 bgp4V2NlriPrefixLen, 1712 bgp4V2PeerRemoteAddrType, 1713 bgp4V2PeerRemoteAddr, 1714 bgp4V2AdjRibsOutIndex 1715 } 1716 ::= { bgp4V2AdjRibsOutTable 1 } 1718 Bgp4V2AdjRibsOutEntry ::= SEQUENCE { 1719 bgp4V2AdjRibsOutIndex 1720 Unsigned32, 1721 bgp4V2AdjRibsOutRoute 1722 RowPointer 1723 } 1725 bgp4V2AdjRibsOutIndex OBJECT-TYPE 1726 SYNTAX Unsigned32 1727 MAX-ACCESS not-accessible 1728 STATUS current 1729 DESCRIPTION 1730 "Certain extensions to BGP permit multiple instance of 1731 a per afi, per safi prefix to be advertised to a peer. 1732 This object allows the enumeration of them." 1733 ::= { bgp4V2AdjRibsOutEntry 1 } 1735 bgp4V2AdjRibsOutRoute OBJECT-TYPE 1736 SYNTAX RowPointer 1737 MAX-ACCESS read-only 1738 STATUS current 1739 DESCRIPTION 1740 "This object points to the route in the bgp4V2NlriTable 1741 that corresponds to the entry in the peer's 1742 Adj-Rib-Out. Outgoing route maps are not 1743 reflected at this point as those are part of the 1744 Update-Send process." 1745 REFERENCE 1746 "RFC 4271, Section 9.2." 1747 ::= { bgp4V2AdjRibsOutEntry 2 } 1749 -- 1750 -- Notifications 1751 -- 1753 bgp4V2EstablishedNotification NOTIFICATION-TYPE 1754 OBJECTS { 1755 bgp4V2PeerState, 1756 bgp4V2PeerLocalPort, 1757 bgp4V2PeerRemotePort 1758 } 1759 STATUS current 1760 DESCRIPTION 1761 "The BGP Established event is generated when 1762 the BGP FSM enters the established state." 1763 ::= { bgp4V2Notifications 1 } 1765 bgp4V2BackwardTransitionNotification NOTIFICATION-TYPE 1766 OBJECTS { 1767 bgp4V2PeerState, 1768 bgp4V2PeerLocalPort, 1769 bgp4V2PeerRemotePort, 1770 bgp4V2PeerLastErrorCodeReceived, 1771 bgp4V2PeerLastErrorSubCodeReceived, 1772 bgp4V2PeerLastErrorReceivedText 1773 } 1774 STATUS current 1775 DESCRIPTION 1776 "The BGPBackwardTransition Event is generated 1777 when the BGP FSM moves from a higher numbered 1778 state to a lower numbered state. 1780 Due to the nature of the BGP state machine, an 1781 implementation MAY rate limit the generation of this event. 1782 An implementation MAY also generate this notification ONLY 1783 when the state machine moves out of the established state. 1784 An implementation should document its specific behavior." 1785 ::= { bgp4V2Notifications 2 } 1787 -- 1788 -- Conformance Information 1789 -- 1791 bgp4V2Compliances OBJECT IDENTIFIER ::= 1792 { bgp4V2Conformance 1 } 1794 bgp4V2Groups OBJECT IDENTIFIER ::= 1795 { bgp4V2Conformance 2 } 1797 bgp4V2Compliance MODULE-COMPLIANCE 1798 STATUS current 1799 DESCRIPTION 1800 "The compliance statement for entities which 1801 implement the BGP4 mib." 1802 MODULE -- this module 1803 MANDATORY-GROUPS { 1804 bgp4V2StdMIBTimersGroup, 1805 bgp4V2StdMIBCountersGroup, 1806 bgp4V2StdMIBErrorsGroup, 1807 bgp4V2StdMIBPeerGroup, 1808 bgp4V2StdMIBNlriGroup, 1809 bgp4V2GlobalsGroup 1810 } 1811 GROUP bgp4V2StdMIBNotificationGroup 1812 DESCRIPTION 1813 "Implementation of BGP Notifications are completely 1814 optional in this MIB." 1816 OBJECT bgp4V2PeerLocalAddr 1817 SYNTAX InetAddress (SIZE(4|16|20)) 1818 DESCRIPTION 1819 "An implementation is required to support IPv4 peering 1820 sessions. An implementation MAY support IPv6 peering 1821 sessions. IPv6 link-local peering sessions MAY be 1822 supported by this MIB." 1824 OBJECT bgp4V2PeerRemoteAddr 1825 SYNTAX InetAddress (SIZE(4|16|20)) 1826 DESCRIPTION 1827 "An implementation is required to support IPv4 peering 1828 sessions. An implementation MAY support IPv6 peering 1829 sessions. IPv6 link-local peering sessions MAY be 1830 supported by this MIB." 1832 OBJECT bgp4V2NlriPrefix 1833 SYNTAX InetAddress (SIZE(0..16)) 1834 DESCRIPTION 1835 "An implementation is required to support IPv4 prefixes. 1836 An implementation MAY support IPv6 prefixes." 1838 OBJECT bgp4V2NlriLinkLocalNextHopAddrType 1839 SYNTAX InetAddressType 1840 DESCRIPTION 1841 "This object is only present when RFC 2545 extensions for 1842 IPv6 are supported by the implementation. When present, 1843 this object shall only have a value of ipv6z or none." 1845 OBJECT bgp4V2NlriLinkLocalNextHopAddr 1846 SYNTAX InetAddress (SIZE(0|20)) 1847 DESCRIPTION 1848 "This object is only present when RFC 2545 extensions for 1849 IPv6 are supported by the implementation. When present, 1850 this object shall only have a size of 20 or 0 when no 1851 RFC 2545 double-nexthop is present." 1853 OBJECT bgp4V2PeerInstance 1854 SYNTAX Unsigned32 (1..4294967295) 1855 DESCRIPTION 1856 "This object represents an abstract index which can utilize 1857 the full range of acceptable SNMP index values." 1859 ::= { bgp4V2Compliances 4 } 1861 bgp4V2GlobalsGroup OBJECT-GROUP 1862 OBJECTS { bgp4V2DiscontinuityTime } 1863 STATUS current 1864 DESCRIPTION 1865 "A collection of objects providing information on global 1866 BGP state." 1867 ::= { bgp4V2Groups 1 } 1869 bgp4V2StdMIBTimersGroup OBJECT-GROUP 1870 OBJECTS { 1871 bgp4V2PeerFsmEstablishedTime, 1872 bgp4V2PeerInUpdatesElapsedTime, 1873 bgp4V2PeerConnectRetryInterval, 1874 bgp4V2PeerHoldTimeConfigured, 1875 bgp4V2PeerKeepAliveConfigured, 1876 bgp4V2PeerMinASOrigInterval, 1877 bgp4V2PeerMinRouteAdverInterval, 1878 bgp4V2PeerHoldTime, 1879 bgp4V2PeerKeepAlive 1880 } 1881 STATUS current 1882 DESCRIPTION 1883 "Objects associated with BGP peering timers." 1884 ::= { bgp4V2Groups 2 } 1886 bgp4V2StdMIBCountersGroup OBJECT-GROUP 1887 OBJECTS { 1888 bgp4V2PeerInUpdates, 1889 bgp4V2PeerOutUpdates, 1890 bgp4V2PeerInTotalMessages, 1891 bgp4V2PeerOutTotalMessages, 1892 bgp4V2PeerFsmEstablishedTransitions, 1893 bgp4V2PrefixInPrefixes, 1894 bgp4V2PrefixInPrefixesAccepted, 1895 bgp4V2PrefixOutPrefixes 1896 } 1897 STATUS current 1898 DESCRIPTION 1899 "Objects to count discrete events and exchanges on BGP 1900 sessions." 1901 ::= { bgp4V2Groups 3 } 1903 bgp4V2StdMIBErrorsGroup OBJECT-GROUP 1904 OBJECTS { 1905 bgp4V2PeerLastErrorCodeReceived, 1906 bgp4V2PeerLastErrorSubCodeReceived, 1907 bgp4V2PeerLastErrorReceivedData, 1908 bgp4V2PeerLastErrorReceivedTime, 1909 bgp4V2PeerLastErrorReceivedText, 1910 bgp4V2PeerLastErrorCodeSent, 1911 bgp4V2PeerLastErrorSubCodeSent, 1912 bgp4V2PeerLastErrorSentData, 1913 bgp4V2PeerLastErrorSentTime, 1914 bgp4V2PeerLastErrorSentText 1915 } 1916 STATUS current 1917 DESCRIPTION 1918 "Errors received on BGP peering sessions." 1919 ::= { bgp4V2Groups 5 } 1921 bgp4V2StdMIBPeerGroup OBJECT-GROUP 1922 OBJECTS { 1923 bgp4V2PeerState, 1924 bgp4V2PeerAdminStatus, 1925 bgp4V2PeerLocalPort, 1926 bgp4V2PeerLocalAs, 1927 bgp4V2PeerRemotePort, 1928 bgp4V2PeerRemoteAs, 1929 bgp4V2PeerLocalIdentifier, 1930 bgp4V2PeerRemoteIdentifier, 1931 bgp4V2PeerDescription 1932 } 1933 STATUS current 1934 DESCRIPTION 1935 "Core object types on BGP peering sessions." 1936 ::= { bgp4V2Groups 6 } 1938 bgp4V2StdMIBNlriGroup OBJECT-GROUP 1939 OBJECTS { 1940 bgp4V2NlriAsPathCalcLength, 1941 bgp4V2NlriAsPathString, 1942 bgp4V2NlriBest, 1943 bgp4V2NlriCalcLocalPref, 1944 bgp4V2NlriPrefixType, 1945 bgp4V2AdjRibsOutRoute, 1946 bgp4V2NlriAggregatorPresent, 1947 bgp4V2NlriAggregatorAS, 1948 bgp4V2NlriAggregatorAddr, 1949 bgp4V2NlriAtomicAggregate, 1950 bgp4V2NlriLocalPref, 1951 bgp4V2NlriLocalPrefPresent, 1952 bgp4V2NlriMed, 1953 bgp4V2NlriMedPresent, 1954 bgp4V2NlriNextHopAddr, 1955 bgp4V2NlriNextHopAddrType, 1956 bgp4V2NlriLinkLocalNextHopAddrType, 1957 bgp4V2NlriLinkLocalNextHopAddr, 1958 bgp4V2NlriOrigin, 1959 bgp4V2NlriAsPath, 1960 bgp4V2NlriPathAttrUnknown 1961 } 1962 STATUS current 1963 DESCRIPTION 1964 "Attributes received on BGP peering sessions." 1965 ::= { bgp4V2Groups 7 } 1967 bgp4V2StdMIBNotificationGroup NOTIFICATION-GROUP 1968 NOTIFICATIONS { 1969 bgp4V2EstablishedNotification, 1970 bgp4V2BackwardTransitionNotification 1971 } 1972 STATUS current 1973 DESCRIPTION 1974 "Notifications in this modules are completely optional." 1975 ::= { bgp4V2Groups 8 } 1977 END 1979 8. Security Considerations 1981 There are no management objects defined in this MIB module that have 1982 a MAX-ACCESS clause of read-write and/or read-create. So, if this 1983 MIB module is implemented correctly, then there is no risk that an 1984 intruder can alter or create any management objects of this MIB 1985 module via direct SNMP SET operations. 1987 Some of the readable objects in this MIB module (i.e., objects with a 1988 MAX-ACCESS other than not-accessible) may be considered sensitive or 1989 vulnerable in some network environments. It is thus important to 1990 control even GET and/or NOTIFY access to these objects and possibly 1991 to even encrypt the values of these objects when sending them over 1992 the network via SNMP. These are the tables and objects and their 1993 sensitivity/vulnerability: 1995 o bgp4V2PeerLocalAddrType, bgp4V2PeerLocalAddr, bgp4V2PeerLocalPort 1996 bgp4V2PeerRemoteAddrType, bgp4V2PeerRemoteAddr, 1997 bgp4V2PeerRemotePort, bgp4V2PeerLocalAddr, bgp4V2PeerLocalPort, 1998 bgp4V2PeerRemoteAddr, bgp4V2PeerRemotePort - A BGP peer's local 1999 and remote addresses might be sensitive for ISPs who want to keep 2000 interface addresses on routers confidential in order to prevent 2001 router addresses used for a denial of service attack or spoofing. 2002 Note that other tables which share elements of these objects as 2003 indexes may similarly expose sensitive information. 2005 o bgp4V2NlriTable, bgp4V2AdjRibsOutTable - A BGP peer's routing 2006 information may be sensitive for ISPs as the contents of their 2007 routing tables may expose details related to business 2008 relationships as implemented in Internet routing. 2010 SNMP versions prior to SNMPv3 did not include adequate security. 2011 Even if the network itself is secure (for example by using IPSec), 2012 even then, there is no control as to who on the secure network is 2013 allowed to access and GET/SET (read/change/create/delete) the objects 2014 in this MIB module. 2016 It is RECOMMENDED that implementers consider the security features as 2017 provided by the SNMPv3 framework (see [RFC3410], section 8), 2018 including full support for the SNMPv3 cryptographic mechanisms (for 2019 authentication and privacy). 2021 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2022 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2023 enable cryptographic security. It is then a customer/operator 2024 responsibility to ensure that the SNMP entity giving access to an 2025 instance of this MIB module is properly configured to give access to 2026 the objects only to those principals (users) that have legitimate 2027 rights to indeed GET or SET (change/create/delete) them. 2029 9. IANA Considerations 2031 IANA is requested to assign this MIB module an OID under mib-2. 2033 10. Contributors 2035 This document owes significant thanks over the years to Wayne 2036 Tackabury, Susan Hares and the members of the IDR and OPS-NM mailing 2037 lists. This document represents several years of negotiating 2038 operational needs, Internet operational security considerations and 2039 the sheer messiness of representing the BGP protocol in SMIv2. 2041 I owe particular thanks to Susan Hares as a mentor who let me dive 2042 head-first into the world of Internet standards work by saying, "We 2043 have this MIB that just needs a little cleanup to advance in the 2044 standards process." 2046 11. Acknowledgements 2048 We would like to acknowledge the assistance of all the members of the 2049 Inter-Domain Routing Working Group and individuals who contributed to 2050 RFCs 1269, 1657 and 4273. 2052 The origin of this document is from RFC 1269 "Definitions of Managed 2053 Objects for the Border Gateway Protocol (Version 3)" written by Steve 2054 Willis and John Burruss, which was updated by John Chu to support 2055 BGP-4 in RFC 1657. The author wishes to acknowledge the fine work of 2056 these original authors. 2058 12. References 2060 12.1. Normative References 2062 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2063 Requirement Levels", BCP 14, RFC 2119, March 1997. 2065 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2066 Schoenwaelder, Ed., "Structure of Management Information 2067 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2069 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2070 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 2071 STD 58, RFC 2579, April 1999. 2073 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2074 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2075 April 1999. 2077 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 2078 Architecture for Describing Simple Network Management 2079 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 2080 December 2002. 2082 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 2083 Protocol 4 (BGP-4)", RFC 4271, January 2006. 2085 [RFC4273] Haas, J. and S. Hares, "Definitions of Managed Objects for 2086 BGP-4", RFC 4273, January 2006. 2088 [RFC2545] Marques, P. and F. Dupont, "Use of BGP-4 Multiprotocol 2089 Extensions for IPv6 Inter-Domain Routing", RFC 2545, 2090 March 1999. 2092 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2093 Schoenwaelder, "Textual Conventions for Internet Network 2094 Addresses", RFC 4001, February 2005. 2096 [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, 2097 "Multiprotocol Extensions for BGP-4", RFC 4760, 2098 January 2007. 2100 [RFC5065] Traina, P., McPherson, D., and J. Scudder, "Autonomous 2101 System Confederations for BGP", RFC 5065, August 2007. 2103 12.2. Informative References 2105 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2106 "Introduction and Applicability Statements for Internet- 2107 Standard Management Framework", RFC 3410, December 2002. 2109 [RFC1657] Willis, S., Burruss, J., and J. Chu, "Definitions of 2110 Managed Objects for the Fourth Version of the Border 2111 Gateway Protocol (BGP-4) using SMIv2", RFC 1657, 2112 July 1994. 2114 [RFC3107] Rekhter, Y. and E. Rosen, "Carrying Label Information in 2115 BGP-4", RFC 3107, May 2001. 2117 [RFC4022] Raghunarayan, R., "Management Information Base for the 2118 Transmission Control Protocol (TCP)", RFC 4022, 2119 March 2005. 2121 [RFC4456] Bates, T., Chen, E., and R. Chandra, "BGP Route 2122 Reflection: An Alternative to Full Mesh Internal BGP 2123 (IBGP)", RFC 4456, April 2006. 2125 Author's Address 2127 Jeffrey Haas 2128 Arbor Networks 2130 EMail: jhaas@arbor.net