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