idnits 2.17.1 draft-ietf-idr-bgp4-mibv2-12.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 (July 11, 2011) is 4644 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 July 11, 2011 5 Expires: January 12, 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-12 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 January 12, 2012. 34 Copyright Notice 36 Copyright (c) 2011 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 . . . . . . . . . . . . . . . . . . . . . . . 44 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 "201101170000Z" 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 (2011). 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 "201101170000Z" 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 not-accessible 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 not-accessible 393 STATUS current 394 DESCRIPTION 395 "The local IP address of this entry's BGP connection." 396 ::= { bgp4V2PeerEntry 3 } 398 bgp4V2PeerRemoteAddrType OBJECT-TYPE 399 SYNTAX InetAddressType 400 MAX-ACCESS not-accessible 401 STATUS current 402 DESCRIPTION 403 "The address family of the remote end of the peering 404 session." 405 ::= { bgp4V2PeerEntry 4 } 407 bgp4V2PeerRemoteAddr OBJECT-TYPE 408 SYNTAX InetAddress 409 MAX-ACCESS not-accessible 410 STATUS current 411 DESCRIPTION 412 "The remote IP address of this entry's BGP peer." 413 ::= { bgp4V2PeerEntry 5 } 415 bgp4V2PeerLocalPort OBJECT-TYPE 416 SYNTAX InetPortNumber 417 MAX-ACCESS read-only 418 STATUS current 419 DESCRIPTION 420 "The local port for the TCP connection between the BGP 421 peers." 422 ::= { bgp4V2PeerEntry 6 } 424 bgp4V2PeerLocalAs OBJECT-TYPE 425 SYNTAX InetAutonomousSystemNumber 426 MAX-ACCESS read-only 427 STATUS current 428 DESCRIPTION 429 "Some implementations of BGP can represent themselves 430 as multiple ASes. This is the AS that this peering 431 session is representing itself as to the remote peer." 432 ::= { bgp4V2PeerEntry 7 } 434 bgp4V2PeerLocalIdentifier OBJECT-TYPE 435 SYNTAX Bgp4V2IdentifierTC 436 MAX-ACCESS read-only 437 STATUS current 438 DESCRIPTION 439 "The BGP Identifier of the local system for this peering 440 session. It is REQUIRED that all bgp4V2PeerLocalIdentifier 441 values for the same bgp4V2PeerInstance be identical." 442 REFERENCE 443 "RFC 4271, Section 4.2, 'BGP Identifier'." 444 ::= { bgp4V2PeerEntry 8 } 446 bgp4V2PeerRemotePort OBJECT-TYPE 447 SYNTAX InetPortNumber 448 MAX-ACCESS read-only 449 STATUS current 450 DESCRIPTION 451 "The remote port for the TCP connection between the BGP 452 peers. 454 Note that the objects bgp4V2PeerLocalAddr, 455 bgp4V2PeerLocalPort, bgp4V2PeerRemoteAddr and 456 bgp4V2PeerRemotePort provide the appropriate reference to 457 the standard MIB TCP connection table, or even the ipv6 458 TCP MIB as in RFC 4022." 459 REFERENCE 460 "RFC 2012 - SNMPv2 Management Information Base for the 461 Transmission Control Protocol using SMIv2. 462 RFC 4022 - IP Version 6 Management Information Base 463 for the Transmission Control Protocol." 464 ::= { bgp4V2PeerEntry 9 } 466 bgp4V2PeerRemoteAs OBJECT-TYPE 467 SYNTAX InetAutonomousSystemNumber 468 MAX-ACCESS read-only 469 STATUS current 470 DESCRIPTION 471 "The remote autonomous system number received in the BGP 472 OPEN message." 473 REFERENCE 474 "RFC 4271, Section 4.2." 475 ::= { bgp4V2PeerEntry 10 } 477 bgp4V2PeerRemoteIdentifier OBJECT-TYPE 478 SYNTAX Bgp4V2IdentifierTC 479 MAX-ACCESS read-only 480 STATUS current 481 DESCRIPTION 482 "The BGP Identifier of this entry's remote BGP peer. 484 This entry should be 0.0.0.0 unless the 485 bgp4V2PeerState is in the openconfirm or the 486 established state." 487 REFERENCE 488 "RFC 4271, Section 4.2, 'BGP Identifier'." 489 ::= { bgp4V2PeerEntry 11 } 491 bgp4V2PeerAdminStatus OBJECT-TYPE 492 SYNTAX INTEGER { 493 halted(1), 494 running(2) 495 } 496 MAX-ACCESS read-only 497 STATUS current 498 DESCRIPTION 499 "Whether or not the BGP FSM for this remote peer is 500 halted or running. The BGP FSM for a remote peer is 501 halted after processing a Stop event. Likewise, it is 502 in the running state after a Start event. 504 The bgp4V2PeerState will generally be in the idle state 505 when the FSM is halted, although some extensions such 506 as Graceful Restart will leave the peer in the Idle 507 state but with the FSM running." 508 REFERENCE 509 "RFC 4271, Section 8.1.2." 510 ::= { bgp4V2PeerEntry 12 } 512 bgp4V2PeerState OBJECT-TYPE 513 SYNTAX INTEGER { 514 idle(1), 515 connect(2), 516 active(3), 517 opensent(4), 518 openconfirm(5), 519 established(6) 520 } 521 MAX-ACCESS read-only 522 STATUS current 523 DESCRIPTION 524 "The BGP peer connection state." 525 REFERENCE 526 "RFC 4271, Section 8.2.2." 527 ::= { bgp4V2PeerEntry 13 } 529 bgp4V2PeerDescription OBJECT-TYPE 530 SYNTAX SnmpAdminString 531 MAX-ACCESS read-only 532 STATUS current 533 DESCRIPTION 534 "A user configured description identifying this peer. When 535 this object is not the empty string, this object SHOULD 536 contain a description that is unique within a given BGP 537 instance for this peer." 538 ::= { bgp4V2PeerEntry 14 } 540 -- 541 -- Per-peer error management information. 542 -- 544 bgp4V2PeerErrorsTable OBJECT-TYPE 545 SYNTAX SEQUENCE OF Bgp4V2PeerErrorsEntry 546 MAX-ACCESS not-accessible 547 STATUS current 548 DESCRIPTION 549 "On a per-peer basis, this table reflects the last 550 protocol-defined error encountered and reported on 551 the peer session." 552 ::= { bgp4V2Objects 3 } 554 bgp4V2PeerErrorsEntry OBJECT-TYPE 555 SYNTAX Bgp4V2PeerErrorsEntry 556 MAX-ACCESS not-accessible 557 STATUS current 558 DESCRIPTION 559 "Each entry contains information about errors sent 560 and received for a particular BGP peer." 561 AUGMENTS { 562 bgp4V2PeerEntry 563 } 564 ::= { bgp4V2PeerErrorsTable 1 } 566 Bgp4V2PeerErrorsEntry ::= SEQUENCE { 567 bgp4V2PeerLastErrorCodeReceived 568 Unsigned32, 569 bgp4V2PeerLastErrorSubCodeReceived 570 Unsigned32, 571 bgp4V2PeerLastErrorReceivedTime 572 TimeStamp, 573 bgp4V2PeerLastErrorReceivedText 574 SnmpAdminString, 575 bgp4V2PeerLastErrorReceivedData 576 OCTET STRING, 577 bgp4V2PeerLastErrorCodeSent 578 Unsigned32, 579 bgp4V2PeerLastErrorSubCodeSent 580 Unsigned32, 581 bgp4V2PeerLastErrorSentTime 582 TimeStamp, 583 bgp4V2PeerLastErrorSentText 584 SnmpAdminString, 585 bgp4V2PeerLastErrorSentData 586 OCTET STRING 587 } 589 bgp4V2PeerLastErrorCodeReceived OBJECT-TYPE 590 SYNTAX Unsigned32 (0..255) 591 MAX-ACCESS read-only 592 STATUS current 593 DESCRIPTION 594 "The last error code received from this peer via 595 NOTIFICATION message on this connection. If no error has 596 occurred, this field is zero." 597 REFERENCE 598 "RFC 4271, Section 4.5. 599 RFC 4486 optionally supported. 600 RFC 3362, Section 5 optionally supported." 601 ::= { bgp4V2PeerErrorsEntry 1 } 603 bgp4V2PeerLastErrorSubCodeReceived OBJECT-TYPE 604 SYNTAX Unsigned32 (0..255) 605 MAX-ACCESS read-only 606 STATUS current 607 DESCRIPTION 608 "The last subcode received from this peer via NOTIFICATION 609 message on this connection. If no error has occurred, this 610 field is zero." 611 REFERENCE 612 "RFC 4271, Section 4.5. 613 RFC 4486 optionally supported. 614 RFC 3362, Section 5 optionally supported." 615 ::= { bgp4V2PeerErrorsEntry 2 } 617 bgp4V2PeerLastErrorReceivedTime OBJECT-TYPE 618 SYNTAX TimeStamp 619 MAX-ACCESS read-only 620 STATUS current 621 DESCRIPTION 622 "The timestamp that the last NOTIFICATION was received from 623 this peer." 624 REFERENCE 625 "RFC 4271, Section 4.5." 626 ::= { bgp4V2PeerErrorsEntry 3 } 628 bgp4V2PeerLastErrorReceivedText OBJECT-TYPE 629 SYNTAX SnmpAdminString 630 MAX-ACCESS read-only 631 STATUS current 632 DESCRIPTION 633 "This object contains an implementation specific 634 explanation of the error that was reported." 635 ::= { bgp4V2PeerErrorsEntry 4 } 637 bgp4V2PeerLastErrorReceivedData OBJECT-TYPE 638 SYNTAX OCTET STRING (SIZE(0..4075)) 639 MAX-ACCESS read-only 640 STATUS current 641 DESCRIPTION 642 "The last error code's data seen by this peer. 644 Per RFC 2578, some implementations may have limitations 645 dealing with OCTET STRINGS larger than 255. Thus, this 646 data may be truncated." 647 REFERENCE 648 "RFC 4271, Section 4.5, 649 RFC 2578, Section 7.1.2, 650 RFC 4486 optionally supported. 651 RFC 3362, Section 5 optionally supported." 652 ::= { bgp4V2PeerErrorsEntry 5 } 654 bgp4V2PeerLastErrorCodeSent OBJECT-TYPE 655 SYNTAX Unsigned32 (0..255) 656 MAX-ACCESS read-only 657 STATUS current 658 DESCRIPTION 659 "The last error code sent to this peer via NOTIFICATION 660 message on this connection. If no error has occurred, this 661 field is zero." 662 REFERENCE 663 "RFC 4271, Section 4.5. 664 RFC 4486 optionally supported. 665 RFC 3362, Section 5 optionally supported." 666 ::= { bgp4V2PeerErrorsEntry 6 } 668 bgp4V2PeerLastErrorSubCodeSent OBJECT-TYPE 669 SYNTAX Unsigned32 (0..255) 670 MAX-ACCESS read-only 671 STATUS current 672 DESCRIPTION 673 "The last subcode sent to this peer via NOTIFICATION 674 message on this connection. If no error has occurred, this 675 field is zero." 676 REFERENCE 677 "RFC 4271, Section 4.5. 678 RFC 4486 optionally supported. 679 RFC 3362, Section 5 optionally supported." 680 ::= { bgp4V2PeerErrorsEntry 7 } 682 bgp4V2PeerLastErrorSentTime OBJECT-TYPE 683 SYNTAX TimeStamp 684 MAX-ACCESS read-only 685 STATUS current 686 DESCRIPTION 687 "The timestamp that the last NOTIFICATION was sent to 688 this peer." 689 REFERENCE 690 "RFC 4271, Section 4.5." 691 ::= { bgp4V2PeerErrorsEntry 8 } 693 bgp4V2PeerLastErrorSentText OBJECT-TYPE 694 SYNTAX SnmpAdminString 695 MAX-ACCESS read-only 696 STATUS current 697 DESCRIPTION 698 "This object contains an implementation specific 699 explanation of the error that is being reported." 700 ::= { bgp4V2PeerErrorsEntry 9 } 702 bgp4V2PeerLastErrorSentData OBJECT-TYPE 703 SYNTAX OCTET STRING (SIZE(0..4075)) 704 MAX-ACCESS read-only 705 STATUS current 706 DESCRIPTION 707 "The last error code's data sent to this peer. 709 Per RFC 2578, some implementations may have limitations 710 dealing with OCTET STRINGS larger than 255. Thus, this 711 data may be truncated." 712 REFERENCE 713 "RFC 4271, Section 4.5, 714 RFC 2578, Section 7.1.2 715 RFC 4486 optionally supported. 716 RFC 3362, Section 5 optionally supported." 717 ::= { bgp4V2PeerErrorsEntry 10 } 719 -- 720 -- Per-peer Event Times 721 -- 723 bgp4V2PeerEventTimesTable OBJECT-TYPE 724 SYNTAX SEQUENCE OF Bgp4V2PeerEventTimesEntry 725 MAX-ACCESS not-accessible 726 STATUS current 727 DESCRIPTION 728 "A table reporting the per-peering session amount 729 of time elapsed and update events since the peering 730 session advanced into the established state." 731 ::= { bgp4V2Objects 4 } 733 bgp4V2PeerEventTimesEntry OBJECT-TYPE 734 SYNTAX Bgp4V2PeerEventTimesEntry 735 MAX-ACCESS not-accessible 736 STATUS current 737 DESCRIPTION 738 "Each row contains a set of statistics about time 739 spent and events encountered in the peer session 740 established state." 741 AUGMENTS { 742 bgp4V2PeerEntry 743 } 744 ::= { bgp4V2PeerEventTimesTable 1 } 746 Bgp4V2PeerEventTimesEntry ::= SEQUENCE { 747 bgp4V2PeerFsmEstablishedTime 748 Gauge32, 749 bgp4V2PeerInUpdatesElapsedTime 750 Gauge32 751 } 753 bgp4V2PeerFsmEstablishedTime OBJECT-TYPE 754 SYNTAX Gauge32 755 UNITS "seconds" 756 MAX-ACCESS read-only 757 STATUS current 758 DESCRIPTION 759 "This timer indicates how long (in seconds) this peer 760 has been in the established state or how long since this 761 peer was last in the established state. It is set to 762 zero when a new peer is configured or when the router is 763 booted. If the peer has never reached the established 764 state, the value remains zero." 765 REFERENCE 766 "RFC 4271, Section 8." 767 ::= { bgp4V2PeerEventTimesEntry 1 } 769 bgp4V2PeerInUpdatesElapsedTime OBJECT-TYPE 770 SYNTAX Gauge32 771 UNITS "seconds" 772 MAX-ACCESS read-only 773 STATUS current 774 DESCRIPTION 775 "Elapsed time (in seconds) since the last BGP UPDATE 776 message was received from the peer. Each time 777 bgpPeerInUpdates is incremented, the value of this 778 object is set to zero (0)." 779 REFERENCE 780 "RFC 4271, Section 4.3. 781 RFC 4271, Section 8.2.2, Established state." 783 ::= { bgp4V2PeerEventTimesEntry 2 } 785 -- 786 -- Per-Peer Configured Timers 787 -- 789 bgp4V2PeerConfiguredTimersTable OBJECT-TYPE 790 SYNTAX SEQUENCE OF Bgp4V2PeerConfiguredTimersEntry 791 MAX-ACCESS not-accessible 792 STATUS current 793 DESCRIPTION 794 "Per peer management data on BGP session timers." 795 ::= { bgp4V2Objects 5 } 797 bgp4V2PeerConfiguredTimersEntry OBJECT-TYPE 798 SYNTAX Bgp4V2PeerConfiguredTimersEntry 799 MAX-ACCESS not-accessible 800 STATUS current 801 DESCRIPTION 802 "Each entry corresponds to the current state of 803 BGP timers on a given peering session." 804 AUGMENTS { 805 bgp4V2PeerEntry 806 } 807 ::= { bgp4V2PeerConfiguredTimersTable 1 } 809 Bgp4V2PeerConfiguredTimersEntry ::= SEQUENCE { 810 bgp4V2PeerConnectRetryInterval 811 Unsigned32, 812 bgp4V2PeerHoldTimeConfigured 813 Unsigned32, 814 bgp4V2PeerKeepAliveConfigured 815 Unsigned32, 816 bgp4V2PeerMinASOrigInterval 817 Unsigned32, 818 bgp4V2PeerMinRouteAdverInterval 819 Unsigned32 820 } 822 bgp4V2PeerConnectRetryInterval OBJECT-TYPE 823 SYNTAX Unsigned32 (1..65535) 824 UNITS "seconds" 825 MAX-ACCESS read-only 826 STATUS current 827 DESCRIPTION 828 "Time interval (in seconds) for the ConnectRetry timer. 829 The suggested value for this timer is 120 seconds." 830 REFERENCE 831 "RFC 4271, Section 8.2.2. This is the value used 832 to initialize the 'ConnectRetryTimer'." 834 ::= { bgp4V2PeerConfiguredTimersEntry 1 } 836 bgp4V2PeerHoldTimeConfigured OBJECT-TYPE 837 SYNTAX Unsigned32 ( 0 | 3..65535 ) 838 UNITS "seconds" 839 MAX-ACCESS read-only 840 STATUS current 841 DESCRIPTION 842 "Time interval (in seconds) for the Hold Timer 843 established with the peer. The value of this object is 844 calculated by this BGP speaker, using the smaller of the 845 values in bgpPeerHoldTimeConfigured and the Hold Time 846 received in the OPEN message. 848 This value must be at least three seconds if it is not 849 zero (0). 851 If the Hold Timer has not been established with the 852 peer this object MUST have a value of zero (0). 854 If the bgpPeerHoldTimeConfigured object has a value of 855 (0), then this object MUST have a value of (0)." 856 REFERENCE 857 "RFC 4271, Section 4.2." 858 ::= { bgp4V2PeerConfiguredTimersEntry 2 } 860 bgp4V2PeerKeepAliveConfigured OBJECT-TYPE 861 SYNTAX Unsigned32 ( 0 | 1..21845 ) 862 UNITS "seconds" 863 MAX-ACCESS read-only 864 STATUS current 865 DESCRIPTION 866 "Time interval (in seconds) for the KeepAlive timer 867 configured for this BGP speaker with this peer. The 868 value of this object will only determine the KEEPALIVE 869 messages' frequency relative to the value specified in 870 bgpPeerHoldTimeConfigured; the actual time interval for 871 the KEEPALIVE messages is indicated by bgpPeerKeepAlive. 873 A reasonable maximum value for this timer would be one 874 third of that of bgpPeerHoldTimeConfigured. 876 If the value of this object is zero (0), no periodic 877 KEEPALIVE messages are sent to the peer after the BGP 878 connection has been established. The suggested value 879 for this timer is 30 seconds." 880 REFERENCE 881 "RFC 4271, Section 4.4. 883 RFC 4271, Section 10." 884 ::= { bgp4V2PeerConfiguredTimersEntry 3 } 886 bgp4V2PeerMinASOrigInterval OBJECT-TYPE 887 SYNTAX Unsigned32 (0..65535) 888 UNITS "seconds" 889 MAX-ACCESS read-only 890 STATUS current 891 DESCRIPTION 892 "Time interval (in seconds) for the 893 MinASOriginationInterval timer. 895 The suggested value for this timer is 15 seconds." 896 REFERENCE 897 "RFC 4271, Section 9.2.1.2. 898 RFC 4271, Section 10." 899 ::= { bgp4V2PeerConfiguredTimersEntry 4 } 901 bgp4V2PeerMinRouteAdverInterval 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 MinRouteAdvertisementInterval timer. 910 The suggested value for this timer is 30 seconds for 911 EBGP connections and 5 seconds for IBGP connections." 912 REFERENCE 913 "RFC 4271, Section 9.2.1.1. 914 RFC 4271, Section 10." 915 ::= { bgp4V2PeerConfiguredTimersEntry 5 } 917 -- 918 -- Per-Peer Negotiated Timers 919 -- 921 bgp4V2PeerNegotiatedTimersTable OBJECT-TYPE 922 SYNTAX SEQUENCE OF Bgp4V2PeerNegotiatedTimersEntry 923 MAX-ACCESS not-accessible 924 STATUS current 925 DESCRIPTION 926 "Configured values of per-peer timers are seen 927 in the bgp4V2PeerConfiguredTimersTable. 929 Values in this table reflect the current 930 operational values, after negotiation from values 931 derived from initial configuration." 932 ::= { bgp4V2Objects 6 } 934 bgp4V2PeerNegotiatedTimersEntry OBJECT-TYPE 935 SYNTAX Bgp4V2PeerNegotiatedTimersEntry 936 MAX-ACCESS not-accessible 937 STATUS current 938 DESCRIPTION 939 "Each entry reflects a value of the currently 940 operational, negotiated timer as reflected in the 941 Bgp4V2PeerNegotiatedTimersEntry." 942 AUGMENTS { 943 bgp4V2PeerEntry 944 } 945 ::= { bgp4V2PeerNegotiatedTimersTable 1 } 947 Bgp4V2PeerNegotiatedTimersEntry ::= SEQUENCE { 948 bgp4V2PeerHoldTime 949 Unsigned32, 950 bgp4V2PeerKeepAlive 951 Unsigned32 952 } 954 bgp4V2PeerHoldTime OBJECT-TYPE 955 SYNTAX Unsigned32 ( 0 | 3..65535 ) 956 UNITS "seconds" 957 MAX-ACCESS read-only 958 STATUS current 959 DESCRIPTION 960 "The value of this object is calculated by this BGP 961 Speaker as being; 963 zero (0) - if this was the value sent by the peer and 964 this value is permitted by this BGP Speaker. In this 965 case, no keepalive messages are sent and the Hold Timer 966 is not set. 968 At least three (3). This value is the smaller of 969 the value sent by this peer in the OPEN message and 970 bgp4V2PeerHoldTimeConfigured for this peer. 972 If the peer is not in the established state, the value 973 of this object is zero (0)." 974 REFERENCE 975 "RFC 4271, Section 4.2." 976 ::= { bgp4V2PeerNegotiatedTimersEntry 1 } 978 bgp4V2PeerKeepAlive OBJECT-TYPE 979 SYNTAX Unsigned32 ( 0 | 1..21845 ) 980 UNITS "seconds" 981 MAX-ACCESS read-only 982 STATUS current 983 DESCRIPTION 984 "Time interval in seconds for the KeepAlive timer 985 established with the peer. The value of this object 986 is calculated by this BGP speaker such that, when 987 compared with bgp4V2PeerHoldTime, it has the same 988 proportion as what bgp4V2PeerKeepAliveConfigured has 989 when compared with bgp4V2PeerHoldTimeConfigured. If 990 the value of this object is zero (0), it indicates 991 that the KeepAlive timer has not been established 992 with the peer, or, the value of 993 bgp4V2PeerKeepAliveConfigured is zero (0). 995 If the peer is not in the established state, the value 996 of this object is zero (0)." 997 REFERENCE 998 "RFC 4271, Section 4.4." 999 ::= { bgp4V2PeerNegotiatedTimersEntry 2 } 1001 -- 1002 -- Per-peer counters 1003 -- 1005 bgp4V2PeerCountersTable OBJECT-TYPE 1006 SYNTAX SEQUENCE OF Bgp4V2PeerCountersEntry 1007 MAX-ACCESS not-accessible 1008 STATUS current 1009 DESCRIPTION 1010 "The counters associated with a BGP Peer." 1011 ::= { bgp4V2Objects 7 } 1013 bgp4V2PeerCountersEntry OBJECT-TYPE 1014 SYNTAX Bgp4V2PeerCountersEntry 1015 MAX-ACCESS not-accessible 1016 STATUS current 1017 DESCRIPTION 1018 "Each entry contains counters of message transmissions 1019 and FSM transitions for a given BGP Peering session." 1020 AUGMENTS { 1021 bgp4V2PeerEntry 1022 } 1023 ::= { bgp4V2PeerCountersTable 1 } 1025 Bgp4V2PeerCountersEntry ::= SEQUENCE { 1026 bgp4V2PeerInUpdates 1027 Counter32, 1028 bgp4V2PeerOutUpdates 1029 Counter32, 1030 bgp4V2PeerInTotalMessages 1031 Counter32, 1032 bgp4V2PeerOutTotalMessages 1033 Counter32, 1034 bgp4V2PeerFsmEstablishedTransitions 1035 Counter32 1036 } 1038 bgp4V2PeerInUpdates OBJECT-TYPE 1039 SYNTAX Counter32 1040 MAX-ACCESS read-only 1041 STATUS current 1042 DESCRIPTION 1043 "The number of BGP UPDATE messages received on this 1044 connection." 1045 ::= { bgp4V2PeerCountersEntry 1 } 1047 bgp4V2PeerOutUpdates OBJECT-TYPE 1048 SYNTAX Counter32 1049 MAX-ACCESS read-only 1050 STATUS current 1051 DESCRIPTION 1052 "The number of BGP UPDATE messages transmitted on this 1053 connection." 1054 ::= { bgp4V2PeerCountersEntry 2 } 1056 bgp4V2PeerInTotalMessages OBJECT-TYPE 1057 SYNTAX Counter32 1058 MAX-ACCESS read-only 1059 STATUS current 1060 DESCRIPTION 1061 "The total number of messages received from the remote 1062 peer on this connection." 1063 ::= { bgp4V2PeerCountersEntry 3 } 1065 bgp4V2PeerOutTotalMessages OBJECT-TYPE 1066 SYNTAX Counter32 1067 MAX-ACCESS read-only 1068 STATUS current 1069 DESCRIPTION 1070 "The total number of messages transmitted to the remote 1071 peer on this connection." 1072 ::= { bgp4V2PeerCountersEntry 4 } 1074 bgp4V2PeerFsmEstablishedTransitions OBJECT-TYPE 1075 SYNTAX Counter32 1076 MAX-ACCESS read-only 1077 STATUS current 1078 DESCRIPTION 1079 "The total number of times the BGP FSM transitioned into 1080 the established state for this peer." 1081 ::= { bgp4V2PeerCountersEntry 5 } 1083 -- 1084 -- Per-Peer Prefix Gauges 1085 -- 1087 bgp4V2PrefixGaugesTable OBJECT-TYPE 1088 SYNTAX SEQUENCE OF Bgp4V2PrefixCountersEntry 1089 MAX-ACCESS not-accessible 1090 STATUS current 1091 DESCRIPTION 1092 "Additional per-peer, per AFI-SAFI counters for 1093 prefixes" 1094 ::= { bgp4V2Objects 8 } 1096 bgp4V2PrefixGaugesEntry OBJECT-TYPE 1097 SYNTAX Bgp4V2PrefixCountersEntry 1098 MAX-ACCESS not-accessible 1099 STATUS current 1100 DESCRIPTION 1101 "Entry containing information about a bgp-peers prefix 1102 counters." 1103 INDEX { 1104 bgp4V2PeerInstance, 1105 bgp4V2PeerRemoteAddrType, 1106 bgp4V2PeerRemoteAddr, 1107 bgp4V2PrefixGaugesAfi, 1108 bgp4V2PrefixGaugesSafi 1109 } 1110 ::= { bgp4V2PrefixGaugesTable 1 } 1112 Bgp4V2PrefixCountersEntry ::= SEQUENCE { 1113 bgp4V2PrefixGaugesAfi 1114 Bgp4V2AddressFamilyIdentifierTC, 1115 bgp4V2PrefixGaugesSafi 1116 Bgp4V2SubsequentAddressFamilyIdentifierTC, 1117 bgp4V2PrefixInPrefixes 1118 Gauge32, 1119 bgp4V2PrefixInPrefixesAccepted 1120 Gauge32, 1121 bgp4V2PrefixOutPrefixes 1122 Gauge32 1124 } 1126 bgp4V2PrefixGaugesAfi OBJECT-TYPE 1127 SYNTAX Bgp4V2AddressFamilyIdentifierTC 1128 MAX-ACCESS not-accessible 1129 STATUS current 1130 DESCRIPTION 1131 "The AFI index of the per-peer, per prefix counters" 1132 ::= { bgp4V2PrefixGaugesEntry 1 } 1134 bgp4V2PrefixGaugesSafi OBJECT-TYPE 1135 SYNTAX Bgp4V2SubsequentAddressFamilyIdentifierTC 1136 MAX-ACCESS not-accessible 1137 STATUS current 1138 DESCRIPTION 1139 "The SAFI index of the per-peer, per prefix counters" 1140 ::= { bgp4V2PrefixGaugesEntry 2 } 1142 bgp4V2PrefixInPrefixes OBJECT-TYPE 1143 SYNTAX Gauge32 1144 MAX-ACCESS read-only 1145 STATUS current 1146 DESCRIPTION 1147 "The number of prefixes received from a peer and are 1148 stored in the Adj-Ribs-In for that peer. 1150 Note that this number does not reflect prefixes that 1151 have been discarded due to policy." 1152 REFERENCE 1153 "RFC 4271, Sections 3.2 and 9." 1154 ::= { bgp4V2PrefixGaugesEntry 3 } 1156 bgp4V2PrefixInPrefixesAccepted OBJECT-TYPE 1157 SYNTAX Gauge32 1158 MAX-ACCESS read-only 1159 STATUS current 1160 DESCRIPTION 1161 "The number of prefixes for a peer that are installed 1162 in the Adj-Ribs-In and are eligible to become active 1163 in the Loc-Rib." 1164 REFERENCE 1165 "RFC 4271, Sections 3.2 and 9." 1166 ::= { bgp4V2PrefixGaugesEntry 4 } 1168 bgp4V2PrefixOutPrefixes OBJECT-TYPE 1169 SYNTAX Gauge32 1170 MAX-ACCESS read-only 1171 STATUS current 1172 DESCRIPTION 1173 "The number of prefixes for a peer that are installed 1174 in that peer's Adj-Ribs-Out." 1175 REFERENCE 1176 "RFC 4271, Sections 3.2 and 9." 1177 ::= { bgp4V2PrefixGaugesEntry 5 } 1179 -- 1180 -- BGP NLRI 1181 -- 1183 bgp4V2NlriTable OBJECT-TYPE 1184 SYNTAX SEQUENCE OF Bgp4V2NlriEntry 1185 MAX-ACCESS not-accessible 1186 STATUS current 1187 DESCRIPTION 1188 "The BGP-4 Received Path Attribute Table contains 1189 information about paths to destination networks 1190 received from all BGP4 peers. Collectively, this 1191 represents the Adj-Ribs-In. The route where 1192 bgp4V2NlriBest is true represents, for this NLRI, 1193 the route that is installed in the LocRib from the 1194 Adj-Ribs-In." 1195 REFERENCE 1196 "RFC 4271, Sections 3.2 and 9." 1197 ::= { bgp4V2Objects 9 } 1199 bgp4V2NlriEntry OBJECT-TYPE 1200 SYNTAX Bgp4V2NlriEntry 1201 MAX-ACCESS not-accessible 1202 STATUS current 1203 DESCRIPTION 1204 "Information about a path to a network." 1205 INDEX { 1206 bgp4V2PeerInstance, 1207 bgp4V2NlriAfi, 1208 bgp4V2NlriSafi, 1209 bgp4V2NlriPrefixType, 1210 bgp4V2NlriPrefix, 1211 bgp4V2NlriPrefixLen, 1212 bgp4V2PeerRemoteAddrType, 1213 bgp4V2PeerRemoteAddr, 1214 bgp4V2NlriIndex 1215 } 1216 ::= { bgp4V2NlriTable 1 } 1218 Bgp4V2NlriEntry ::= SEQUENCE { 1219 bgp4V2NlriIndex 1220 Unsigned32, 1221 bgp4V2NlriAfi 1222 Bgp4V2AddressFamilyIdentifierTC, 1223 bgp4V2NlriSafi 1224 Bgp4V2SubsequentAddressFamilyIdentifierTC, 1225 bgp4V2NlriPrefixType 1226 InetAddressType, 1227 bgp4V2NlriPrefix 1228 InetAddress, 1229 bgp4V2NlriPrefixLen 1230 InetAddressPrefixLength, 1231 bgp4V2NlriBest 1232 TruthValue, 1233 bgp4V2NlriCalcLocalPref 1234 Unsigned32, 1235 bgp4V2NlriOrigin 1236 INTEGER, 1237 bgp4V2NlriNextHopAddrType 1238 InetAddressType, 1239 bgp4V2NlriNextHopAddr 1240 InetAddress, 1241 bgp4V2NlriLinkLocalNextHopAddrType 1242 InetAddressType, 1243 bgp4V2NlriLinkLocalNextHopAddr 1244 InetAddress, 1245 bgp4V2NlriLocalPrefPresent 1246 TruthValue, 1247 bgp4V2NlriLocalPref 1248 Unsigned32, 1249 bgp4V2NlriMedPresent 1250 TruthValue, 1251 bgp4V2NlriMed 1252 Unsigned32, 1253 bgp4V2NlriAtomicAggregate 1254 INTEGER, 1255 bgp4V2NlriAggregatorPresent 1256 TruthValue, 1257 bgp4V2NlriAggregatorAS 1258 InetAutonomousSystemNumber, 1259 bgp4V2NlriAggregatorAddr 1260 Bgp4V2IdentifierTC, 1261 bgp4V2NlriAsPathCalcLength 1262 Unsigned32, 1263 bgp4V2NlriAsPathString 1264 SnmpAdminString, 1265 bgp4V2NlriAsPath 1266 OCTET STRING, 1267 bgp4V2NlriPathAttrUnknown 1268 OCTET STRING 1269 } 1271 bgp4V2NlriIndex OBJECT-TYPE 1272 SYNTAX Unsigned32 1273 MAX-ACCESS not-accessible 1274 STATUS current 1275 DESCRIPTION 1276 "This index allows for multiple instances of a base 1277 prefix for a certain AFI-SAFI from a given peer. 1278 This is currently useful for two things: 1279 1. Allowing for a peer in future implementations to 1280 send more than a single route instance. 1281 2. Allow for extensions which extend the NLRI field 1282 to send the same prefix while utilizing other 1283 extension specific information. An example of 1284 this is RFC 3107 - Carrying MPLS labels in BGP." 1285 REFERENCE 1286 "RFC 3107 - Carrying Label Information in BGP-4." 1287 ::= { bgp4V2NlriEntry 1 } 1289 bgp4V2NlriAfi OBJECT-TYPE 1290 SYNTAX Bgp4V2AddressFamilyIdentifierTC 1291 MAX-ACCESS not-accessible 1292 STATUS current 1293 DESCRIPTION 1294 "The address family of the prefix for this NLRI. 1296 Note that the AFI is not necessarily equivalent to 1297 the an InetAddressType." 1298 REFERENCE 1299 "RFC 4760 - Multiprotocol Extensions for BGP-4" 1300 ::= { bgp4V2NlriEntry 2 } 1302 bgp4V2NlriSafi OBJECT-TYPE 1303 SYNTAX Bgp4V2SubsequentAddressFamilyIdentifierTC 1304 MAX-ACCESS not-accessible 1305 STATUS current 1306 DESCRIPTION 1307 "The subsequent address family of the prefix for 1308 this NLRI" 1309 REFERENCE 1310 "RFC 4760 - Multiprotocol Extensions for BGP-4" 1311 ::= { bgp4V2NlriEntry 3 } 1313 bgp4V2NlriPrefixType OBJECT-TYPE 1314 SYNTAX InetAddressType 1315 MAX-ACCESS not-accessible 1316 STATUS current 1317 DESCRIPTION 1318 "The type of the IP address prefix in the 1319 Network Layer Reachability Information field. 1320 The value of this object is derived from the 1321 appropriate value from the bgp4V2NlriAfi field. 1322 Where an appropriate InetAddressType is not 1323 available, the value of the object must be 1324 unknown(0)." 1325 ::= { bgp4V2NlriEntry 4 } 1327 bgp4V2NlriPrefix OBJECT-TYPE 1328 SYNTAX InetAddress 1329 MAX-ACCESS not-accessible 1330 STATUS current 1331 DESCRIPTION 1332 "An IP address prefix in the Network Layer 1333 Reachability Information field. This object 1334 is an IP address containing the prefix with 1335 length specified by bgp4V2NlriPrefixLen. 1336 Any bits beyond the length specified by 1337 bgp4V2NlriPrefixLen are zeroed." 1338 REFERENCE 1339 "RFC 4271, Section 4.3." 1340 ::= { bgp4V2NlriEntry 5 } 1342 bgp4V2NlriPrefixLen OBJECT-TYPE 1343 SYNTAX InetAddressPrefixLength 1344 MAX-ACCESS not-accessible 1345 STATUS current 1346 DESCRIPTION 1347 "Length in bits of the address prefix in 1348 the Network Layer Reachability Information field." 1349 ::= { bgp4V2NlriEntry 6 } 1351 bgp4V2NlriBest OBJECT-TYPE 1352 SYNTAX TruthValue 1353 MAX-ACCESS read-only 1354 STATUS current 1355 DESCRIPTION 1356 "An indication of whether or not this route 1357 was chosen as the best BGP4 route for this 1358 destination." 1359 REFERENCE 1360 "RFC 4271, Section 9.1.2." 1361 ::= { bgp4V2NlriEntry 7 } 1363 bgp4V2NlriCalcLocalPref OBJECT-TYPE 1364 SYNTAX Unsigned32 1365 MAX-ACCESS read-only 1366 STATUS current 1367 DESCRIPTION 1368 "The degree of preference calculated by the 1369 receiving BGP4 speaker for an advertised 1370 route. 1372 In the case where this prefix is ineligible, the 1373 value of this object will be zero (0)." 1374 REFERENCE 1375 "RFC 4271, Section 9.1.1" 1376 ::= { bgp4V2NlriEntry 8 } 1378 bgp4V2NlriOrigin OBJECT-TYPE 1379 SYNTAX INTEGER { 1380 igp(1),-- networks are interior 1381 egp(2),-- networks learned via the EGP protocol 1382 incomplete(3) -- networks that 1383 -- are learned by some other 1384 -- means 1385 } 1386 MAX-ACCESS read-only 1387 STATUS current 1388 DESCRIPTION 1389 "The ultimate origin of the path information." 1390 REFERENCE 1391 "RFC 4271, Section 4.3. 1392 RFC 4271, Section 5.1.1." 1393 ::= { bgp4V2NlriEntry 9 } 1395 bgp4V2NlriNextHopAddrType OBJECT-TYPE 1396 SYNTAX InetAddressType 1397 MAX-ACCESS read-only 1398 STATUS current 1399 DESCRIPTION 1400 "The address family of the address for 1401 the border router that should be used 1402 to access the destination network." 1403 ::= { bgp4V2NlriEntry 10 } 1405 bgp4V2NlriNextHopAddr OBJECT-TYPE 1406 SYNTAX InetAddress (SIZE(4..20)) 1407 MAX-ACCESS read-only 1408 STATUS current 1409 DESCRIPTION 1410 "The address of the border router that 1411 should be used to access the destination 1412 network. This address is the nexthop 1413 address received in the UPDATE packet associated with 1414 this prefix. 1416 Note that for RFC2545 style double nexthops, 1417 this object will always contain the global scope 1418 nexthop. bgpPathAttrLinkLocalNextHop will contain 1419 the linklocal scope nexthop, if it is present. 1421 In the case a mechanism is developed to use only a link 1422 local nexthop, bgp4V2NlriNextHopAddr will contain the 1423 link local nexthop." 1424 REFERENCE 1425 "RFC 4271, Section 4.3, 1426 RFC 4271, Section 5.1.3, 1427 RFC 2545, Section 3." 1428 ::= { bgp4V2NlriEntry 11 } 1430 bgp4V2NlriLinkLocalNextHopAddrType OBJECT-TYPE 1431 SYNTAX InetAddressType 1432 MAX-ACCESS read-only 1433 STATUS current 1434 DESCRIPTION 1435 "The address type for IPv6 link local addresses. 1436 This is present only when receiving RFC 2545 1437 style double nexthops. 1439 This object is optionally present in BGP 1440 implementations that do not support IPv6. 1442 When no IPv6 link local nexthop is present, the value of 1443 this object should be unknown(0)." 1444 REFERENCE 1445 "RFC 2545, Section 3." 1446 ::= { bgp4V2NlriEntry 12 } 1448 bgp4V2NlriLinkLocalNextHopAddr OBJECT-TYPE 1449 SYNTAX InetAddress 1450 MAX-ACCESS read-only 1451 STATUS current 1452 DESCRIPTION 1453 "This value contains an IPv6 link local address 1454 and is present only when receiving RFC 2545 style 1455 double nexthops. 1457 This object is optionally present in BGP 1458 implementations that do not support IPv6. 1460 When no IPv6 link local nexthop is present, the length of 1461 this object should be zero." 1462 REFERENCE 1463 "RFC 2545, Section 3." 1464 ::= { bgp4V2NlriEntry 13 } 1466 bgp4V2NlriLocalPrefPresent OBJECT-TYPE 1467 SYNTAX TruthValue 1468 MAX-ACCESS read-only 1469 STATUS current 1470 DESCRIPTION 1471 "This value is true when the LOCAL_PREF value was sent in 1472 the UPDATE message." 1473 ::= { bgp4V2NlriEntry 14 } 1475 bgp4V2NlriLocalPref OBJECT-TYPE 1476 SYNTAX Unsigned32 1477 MAX-ACCESS read-only 1478 STATUS current 1479 DESCRIPTION 1480 "The originating BGP4 speakers degree of preference for an 1481 advertised route." 1482 REFERENCE 1483 "RFC 4271, Section 4.3. 1484 RFC 4271, Section 5.1.5." 1485 ::= { bgp4V2NlriEntry 15 } 1487 bgp4V2NlriMedPresent OBJECT-TYPE 1488 SYNTAX TruthValue 1489 MAX-ACCESS read-only 1490 STATUS current 1491 DESCRIPTION 1492 "This value is true when the MED value was sent in 1493 the UPDATE message." 1494 ::= { bgp4V2NlriEntry 16 } 1496 bgp4V2NlriMed OBJECT-TYPE 1497 SYNTAX Unsigned32 1498 MAX-ACCESS read-only 1499 STATUS current 1500 DESCRIPTION 1501 "This metric is used to discriminate between multiple 1502 exit points to an adjacent autonomous system. When the MED 1503 value is absent but has a calculated default value, this 1504 object will contain the calculated value." 1505 REFERENCE 1506 "RFC 4271, Section 4.3. 1507 RFC 4271, Section 5.1.4." 1509 ::= { bgp4V2NlriEntry 17 } 1511 bgp4V2NlriAtomicAggregate OBJECT-TYPE 1512 SYNTAX TruthValue 1513 MAX-ACCESS read-only 1514 STATUS current 1515 DESCRIPTION 1516 "This value is true when the ATOMIC_AGGREGATE Path Attribute 1517 is present and indicates that the NLRI MUST NOT be made 1518 more specific." 1519 REFERENCE 1520 "RFC 4271, Sections 5.1.6 and 9.1.4." 1521 ::= { bgp4V2NlriEntry 18 } 1523 bgp4V2NlriAggregatorPresent OBJECT-TYPE 1524 SYNTAX TruthValue 1525 MAX-ACCESS read-only 1526 STATUS current 1527 DESCRIPTION 1528 "This value is true when the AGGREGATOR path attribute 1529 was sent in the UPDATE message." 1530 ::= { bgp4V2NlriEntry 19 } 1532 bgp4V2NlriAggregatorAS OBJECT-TYPE 1533 SYNTAX InetAutonomousSystemNumber 1534 MAX-ACCESS read-only 1535 STATUS current 1536 DESCRIPTION 1537 "The AS number of the last BGP4 speaker that performed route 1538 aggregation. When bgp4V2NlriAggregatorPresent is 1539 false, the value of this object should be zero (0)." 1540 REFERENCE 1541 "RFC 4271, Section 5.1.7. 1542 RFC 4271, Section 9.2.2.2." 1543 ::= { bgp4V2NlriEntry 20 } 1545 bgp4V2NlriAggregatorAddr OBJECT-TYPE 1546 SYNTAX Bgp4V2IdentifierTC 1547 MAX-ACCESS read-only 1548 STATUS current 1549 DESCRIPTION 1550 "The IP address of the last BGP4 speaker that performed 1551 route aggregation. When bgp4V2NlriAggregatorPresent is 1552 false, the value of this object should be 0.0.0.0" 1553 REFERENCE 1554 "RFC 4271, Section 5.1.7. 1555 RFC 4271, Section 9.2.2.2." 1556 ::= { bgp4V2NlriEntry 21 } 1558 bgp4V2NlriAsPathCalcLength OBJECT-TYPE 1559 SYNTAX Unsigned32 1560 MAX-ACCESS read-only 1561 STATUS current 1562 DESCRIPTION 1563 "This value represents the calculated length of the 1564 AS Path according to the rules of the BGP 1565 specification. This value is used in route selection." 1566 REFERENCE 1567 "RFC 4271, Section 9.1.2.2.a" 1568 ::= { bgp4V2NlriEntry 22 } 1570 bgp4V2NlriAsPathString OBJECT-TYPE 1571 SYNTAX SnmpAdminString 1572 MAX-ACCESS read-only 1573 STATUS current 1574 DESCRIPTION 1575 "This is a string depicting the autonomous system 1576 path to this network which was received from the 1577 peer which advertised it. The format of the string 1578 is implementation-dependent, and should be designed 1579 for operator readability. 1581 Note that SnmpAdminString is only capable of representing a 1582 maximum of 255 characters. This may lead to the string 1583 being truncated in the presence of a large AS Path. It is 1584 RECOMMENDED that when this object's contents will be 1585 truncated that the final 3 octets be reserved for the 1586 ellipses string, '...'. bgp4V2NlriAsPath may give access 1587 to the full AS Path." 1588 ::= { bgp4V2NlriEntry 23 } 1590 -- Maximum size of the following is derived as 1591 -- 4096 max message size 1592 -- - 16 BGP message marker bytes 1593 -- - 2 BGP message size 1594 -- - 1 BGP message type (UPDATE with unknown attr) 1595 -- - 2 UPDATE routes length (even assuming no routes) 1596 -- - 2 UPDATE path attributes length 1597 -- - 1 path attribute flag octet 1598 -- --------- 1599 -- 4072 bytes maximum per-message attribute value data 1601 bgp4V2NlriAsPath OBJECT-TYPE 1602 SYNTAX OCTET STRING (SIZE(2..4072)) 1603 MAX-ACCESS read-only 1604 STATUS current 1605 DESCRIPTION 1606 "In order to provide a canonicalized form of the BGP-4 1607 AS_PATH along with the human-readable 1608 bgp4V2NlriAsPathString, which may be truncated, this object 1609 contains the contents of the BGP-4 AS_PATH Path Attribute. 1610 This object may be parsed using the rules defined for 1611 Four-octet ASes as defined in RFC 4893. RFC 4271, Section 1612 4.3, 'Path Attributes: b) AS_PATH' as amended by RFC 5065, 1613 Section 3 defines the general format of the AS_PATH path 1614 attribute and its code points. 1616 In brief, the AS_PATH is composed of a sequence of AS 1617 Segments. Each AS Segment is represented by a triple: 1618 . 1621 The path segment type and path segment length fields are 1622 one octet in length each. 1624 The path segment type field may be one of: 1625 1 - AS_SET (RFC 4721, Section 4.3) 1626 2 - AS_SEQUENCE (RFC 4721, Section 4.3) 1627 3 - AS_CONFED_SEQUENCE (RFC 3065, Section 5) 1628 4 - AS_CONFED_SET (RFC 3065, Section 5) 1630 The path segment length field contains the number of ASes 1631 (not the number of octets) in the path segment value field. 1633 The path segment value field contains one or more AS 1634 numbers, each encoded as a 4-octet length field in network 1635 byte order. 1637 Note that since an SNMP agent may truncate this object to 1638 less than its maximum theoretical length of 4072 octets 1639 users of this object should be prepared to deal with a 1640 truncated and thus malformed AS_PATH. It is RECOMMENDED 1641 that when such truncation would occur on the boundary of an 1642 encoded AS that the partial AS be discarded from this 1643 object and the object's size be adjusted accordingly. 1644 Further, it is also RECOMMENDED that when such truncation, 1645 either alone or in conjuction with the truncation of a 1646 partially encoded AS described previously, would yield an 1647 empty path segment value field that the path segment type 1648 and path segment length components of the truncated AS_PATH 1649 also be discarded and the object's size be adjusted 1650 accordingly." 1651 REFERENCE 1652 "RFC 4271, Section 4.3. 1653 RFC 5065, Section 5. 1655 RFC 4893." 1656 ::= { bgp4V2NlriEntry 24 } 1658 bgp4V2NlriPathAttrUnknown OBJECT-TYPE 1659 SYNTAX OCTET STRING (SIZE(0..4072)) 1660 MAX-ACCESS read-only 1661 STATUS current 1662 DESCRIPTION 1663 "Path Attributes not understood by this implementation 1664 SHOULD be be presented in this object. Those Path 1665 Attributes use the type, length, value encoding documented 1666 in RFC 4271, Section 4.3, 'Path Attributes'. 1668 Note that since an SNMP agent may truncate this object to 1669 less than its maximum theoretical length of 4072 octets 1670 users of this object should be prepared to deal with a 1671 truncated and thus malformed Path Attribute." 1672 REFERENCE 1673 "RFC 4271, Section 4.3." 1674 ::= { bgp4V2NlriEntry 25 } 1676 -- 1677 -- Adj-Ribs-Out Table 1678 -- 1680 bgp4V2AdjRibsOutTable OBJECT-TYPE 1681 SYNTAX SEQUENCE OF Bgp4V2AdjRibsOutEntry 1682 MAX-ACCESS not-accessible 1683 STATUS current 1684 DESCRIPTION 1685 "This table contains on a per-peer basis one or more 1686 routes from the bgp4V2NlriTable that have been 1687 placed in this peer's Adj-Ribs-Out." 1688 REFERENCE 1689 "RFC 4271, Section 3.2." 1690 ::= { bgp4V2Objects 10 } 1692 bgp4V2AdjRibsOutEntry OBJECT-TYPE 1693 SYNTAX Bgp4V2AdjRibsOutEntry 1694 MAX-ACCESS not-accessible 1695 STATUS current 1696 DESCRIPTION 1697 "List of BGP routes that have been placed into a 1698 peer's Adj-Ribs-Out." 1699 INDEX { 1700 bgp4V2PeerInstance, 1701 bgp4V2NlriAfi, 1702 bgp4V2NlriSafi, 1703 bgp4V2NlriPrefixType, 1704 bgp4V2NlriPrefix, 1705 bgp4V2NlriPrefixLen, 1706 bgp4V2PeerRemoteAddrType, 1707 bgp4V2PeerRemoteAddr, 1708 bgp4V2AdjRibsOutIndex 1709 } 1710 ::= { bgp4V2AdjRibsOutTable 1 } 1712 Bgp4V2AdjRibsOutEntry ::= SEQUENCE { 1713 bgp4V2AdjRibsOutIndex 1714 Unsigned32, 1715 bgp4V2AdjRibsOutRoute 1716 RowPointer 1717 } 1719 bgp4V2AdjRibsOutIndex OBJECT-TYPE 1720 SYNTAX Unsigned32 1721 MAX-ACCESS not-accessible 1722 STATUS current 1723 DESCRIPTION 1724 "Certain extensions to BGP permit multiple instance of 1725 a per afi, per safi prefix to be advertised to a peer. 1726 This object allows the enumeration of them." 1727 ::= { bgp4V2AdjRibsOutEntry 1 } 1729 bgp4V2AdjRibsOutRoute OBJECT-TYPE 1730 SYNTAX RowPointer 1731 MAX-ACCESS read-only 1732 STATUS current 1733 DESCRIPTION 1734 "This object points to the route in the bgp4V2NlriTable 1735 that corresponds to the entry in the peer's 1736 Adj-Rib-Out. Outgoing route maps are not 1737 reflected at this point as those are part of the 1738 Update-Send process." 1739 REFERENCE 1740 "RFC 4271, Section 9.2." 1741 ::= { bgp4V2AdjRibsOutEntry 2 } 1743 -- 1744 -- Notifications 1745 -- 1747 bgp4V2EstablishedNotification NOTIFICATION-TYPE 1748 OBJECTS { 1749 bgp4V2PeerState, 1750 bgp4V2PeerLocalPort, 1751 bgp4V2PeerRemotePort 1752 } 1753 STATUS current 1754 DESCRIPTION 1755 "The BGP Established event is generated when 1756 the BGP FSM enters the established state." 1757 ::= { bgp4V2Notifications 1 } 1759 bgp4V2BackwardTransitionNotification NOTIFICATION-TYPE 1760 OBJECTS { 1761 bgp4V2PeerState, 1762 bgp4V2PeerLocalPort, 1763 bgp4V2PeerRemotePort, 1764 bgp4V2PeerLastErrorCodeReceived, 1765 bgp4V2PeerLastErrorSubCodeReceived, 1766 bgp4V2PeerLastErrorReceivedText 1767 } 1768 STATUS current 1769 DESCRIPTION 1770 "The BGPBackwardTransition Event is generated 1771 when the BGP FSM moves from a higher numbered 1772 state to a lower numbered state. 1774 Due to the nature of the BGP state machine, an 1775 implementation MAY rate limit the generation of this event. 1776 An implementation MAY also generate this notification ONLY 1777 when the state machine moves out of the established state. 1778 An implementation should document its specific behavior." 1779 ::= { bgp4V2Notifications 2 } 1781 -- 1782 -- Conformance Information 1783 -- 1785 bgp4V2Compliances OBJECT IDENTIFIER ::= 1786 { bgp4V2Conformance 1 } 1788 bgp4V2Groups OBJECT IDENTIFIER ::= 1789 { bgp4V2Conformance 2 } 1791 bgp4V2Compliance MODULE-COMPLIANCE 1792 STATUS current 1793 DESCRIPTION 1794 "The compliance statement for entities which 1795 implement the BGP4 mib." 1796 MODULE -- this module 1797 MANDATORY-GROUPS { 1798 bgp4V2StdMIBTimersGroup, 1799 bgp4V2StdMIBCountersGroup, 1800 bgp4V2StdMIBErrorsGroup, 1801 bgp4V2StdMIBPeerGroup, 1802 bgp4V2StdMIBNlriGroup, 1803 bgp4V2GlobalsGroup 1804 } 1805 GROUP bgp4V2StdMIBNotificationGroup 1806 DESCRIPTION 1807 "Implementation of BGP Notifications are completely 1808 optional in this MIB." 1810 OBJECT bgp4V2PeerLocalAddr 1811 SYNTAX InetAddress (SIZE(4|16|20)) 1812 DESCRIPTION 1813 "An implementation is required to support IPv4 peering 1814 sessions. An implementation MAY support IPv6 peering 1815 sessions. IPv6 link-local peering sessions MAY be 1816 supported by this MIB." 1818 OBJECT bgp4V2PeerRemoteAddr 1819 SYNTAX InetAddress (SIZE(4|16|20)) 1820 DESCRIPTION 1821 "An implementation is required to support IPv4 peering 1822 sessions. An implementation MAY support IPv6 peering 1823 sessions. IPv6 link-local peering sessions MAY be 1824 supported by this MIB." 1826 OBJECT bgp4V2NlriPrefix 1827 SYNTAX InetAddress (SIZE(0..16)) 1828 DESCRIPTION 1829 "An implementation is required to support IPv4 prefixes. 1830 An implementation MAY support IPv6 prefixes." 1832 OBJECT bgp4V2NlriLinkLocalNextHopAddrType 1833 SYNTAX InetAddressType 1834 DESCRIPTION 1835 "This object is only present when RFC 2545 extensions for 1836 IPv6 are supported by the implementation. When present, 1837 this object shall only have a value of ipv6z or none." 1839 OBJECT bgp4V2NlriLinkLocalNextHopAddr 1840 SYNTAX InetAddress (SIZE(0|20)) 1841 DESCRIPTION 1842 "This object is only present when RFC 2545 extensions for 1843 IPv6 are supported by the implementation. When present, 1844 this object shall only have a size of 20 or 0 when no 1845 RFC 2545 double-nexthop is present." 1847 OBJECT bgp4V2PeerInstance 1848 SYNTAX Unsigned32 (1..4294967295) 1849 DESCRIPTION 1850 "This object represents an abstract index which can utilize 1851 the full range of acceptable SNMP index values." 1853 ::= { bgp4V2Compliances 4 } 1855 bgp4V2GlobalsGroup OBJECT-GROUP 1856 OBJECTS { bgp4V2DiscontinuityTime } 1857 STATUS current 1858 DESCRIPTION 1859 "A collection of objects providing information on global 1860 BGP state." 1861 ::= { bgp4V2Groups 1 } 1863 bgp4V2StdMIBTimersGroup OBJECT-GROUP 1864 OBJECTS { 1865 bgp4V2PeerFsmEstablishedTime, 1866 bgp4V2PeerInUpdatesElapsedTime, 1867 bgp4V2PeerConnectRetryInterval, 1868 bgp4V2PeerHoldTimeConfigured, 1869 bgp4V2PeerKeepAliveConfigured, 1870 bgp4V2PeerMinASOrigInterval, 1871 bgp4V2PeerMinRouteAdverInterval, 1872 bgp4V2PeerHoldTime, 1873 bgp4V2PeerKeepAlive 1874 } 1875 STATUS current 1876 DESCRIPTION 1877 "Objects associated with BGP peering timers." 1878 ::= { bgp4V2Groups 2 } 1880 bgp4V2StdMIBCountersGroup OBJECT-GROUP 1881 OBJECTS { 1882 bgp4V2PeerInUpdates, 1883 bgp4V2PeerOutUpdates, 1884 bgp4V2PeerInTotalMessages, 1885 bgp4V2PeerOutTotalMessages, 1886 bgp4V2PeerFsmEstablishedTransitions, 1887 bgp4V2PrefixInPrefixes, 1888 bgp4V2PrefixInPrefixesAccepted, 1889 bgp4V2PrefixOutPrefixes 1890 } 1891 STATUS current 1892 DESCRIPTION 1893 "Objects to count discrete events and exchanges on BGP 1894 sessions." 1895 ::= { bgp4V2Groups 3 } 1897 bgp4V2StdMIBErrorsGroup OBJECT-GROUP 1898 OBJECTS { 1899 bgp4V2PeerLastErrorCodeReceived, 1900 bgp4V2PeerLastErrorSubCodeReceived, 1901 bgp4V2PeerLastErrorReceivedData, 1902 bgp4V2PeerLastErrorReceivedTime, 1903 bgp4V2PeerLastErrorReceivedText, 1904 bgp4V2PeerLastErrorCodeSent, 1905 bgp4V2PeerLastErrorSubCodeSent, 1906 bgp4V2PeerLastErrorSentData, 1907 bgp4V2PeerLastErrorSentTime, 1908 bgp4V2PeerLastErrorSentText 1909 } 1910 STATUS current 1911 DESCRIPTION 1912 "Errors received on BGP peering sessions." 1913 ::= { bgp4V2Groups 5 } 1915 bgp4V2StdMIBPeerGroup OBJECT-GROUP 1916 OBJECTS { 1917 bgp4V2PeerState, 1918 bgp4V2PeerAdminStatus, 1919 bgp4V2PeerLocalPort, 1920 bgp4V2PeerLocalAs, 1921 bgp4V2PeerRemotePort, 1922 bgp4V2PeerRemoteAs, 1923 bgp4V2PeerLocalIdentifier, 1924 bgp4V2PeerRemoteIdentifier, 1925 bgp4V2PeerDescription 1926 } 1927 STATUS current 1928 DESCRIPTION 1929 "Core object types on BGP peering sessions." 1930 ::= { bgp4V2Groups 6 } 1932 bgp4V2StdMIBNlriGroup OBJECT-GROUP 1933 OBJECTS { 1934 bgp4V2NlriAsPathCalcLength, 1935 bgp4V2NlriAsPathString, 1936 bgp4V2NlriBest, 1937 bgp4V2NlriCalcLocalPref, 1938 bgp4V2NlriPrefixType, 1939 bgp4V2AdjRibsOutRoute, 1940 bgp4V2NlriAggregatorPresent, 1941 bgp4V2NlriAggregatorAS, 1942 bgp4V2NlriAggregatorAddr, 1943 bgp4V2NlriAtomicAggregate, 1944 bgp4V2NlriLocalPref, 1945 bgp4V2NlriLocalPrefPresent, 1946 bgp4V2NlriMed, 1947 bgp4V2NlriMedPresent, 1948 bgp4V2NlriNextHopAddr, 1949 bgp4V2NlriNextHopAddrType, 1950 bgp4V2NlriLinkLocalNextHopAddrType, 1951 bgp4V2NlriLinkLocalNextHopAddr, 1952 bgp4V2NlriOrigin, 1953 bgp4V2NlriAsPath, 1954 bgp4V2NlriPathAttrUnknown 1955 } 1956 STATUS current 1957 DESCRIPTION 1958 "Attributes received on BGP peering sessions." 1959 ::= { bgp4V2Groups 7 } 1961 bgp4V2StdMIBNotificationGroup NOTIFICATION-GROUP 1962 NOTIFICATIONS { 1963 bgp4V2EstablishedNotification, 1964 bgp4V2BackwardTransitionNotification 1965 } 1966 STATUS current 1967 DESCRIPTION 1968 "Notifications in this modules are completely optional." 1969 ::= { bgp4V2Groups 8 } 1971 END 1973 8. Security Considerations 1975 There are no management objects defined in this MIB module that have 1976 a MAX-ACCESS clause of read-write and/or read-create. So, if this 1977 MIB module is implemented correctly, then there is no risk that an 1978 intruder can alter or create any management objects of this MIB 1979 module via direct SNMP SET operations. 1981 Some of the readable objects in this MIB module (i.e., objects with a 1982 MAX-ACCESS other than not-accessible) may be considered sensitive or 1983 vulnerable in some network environments. It is thus important to 1984 control even GET and/or NOTIFY access to these objects and possibly 1985 to even encrypt the values of these objects when sending them over 1986 the network via SNMP. These are the tables and objects and their 1987 sensitivity/vulnerability: 1989 o bgp4V2PeerLocalAddrType, bgp4V2PeerLocalAddr, bgp4V2PeerLocalPort 1990 bgp4V2PeerRemoteAddrType, bgp4V2PeerRemoteAddr, 1991 bgp4V2PeerRemotePort, bgp4V2PeerLocalAddr, bgp4V2PeerLocalPort, 1992 bgp4V2PeerRemoteAddr, bgp4V2PeerRemotePort - A BGP peer's local 1993 and remote addresses might be sensitive for ISPs who want to keep 1994 interface addresses on routers confidential in order to prevent 1995 router addresses used for a denial of service attack or spoofing. 1996 Note that other tables which share elements of these objects as 1997 indexes may similarly expose sensitive information. 1999 o bgp4V2NlriTable, bgp4V2AdjRibsOutTable - A BGP peer's routing 2000 information may be sensitive for ISPs as the contents of their 2001 routing tables may expose details related to business 2002 relationships as implemented in Internet routing. 2004 SNMP versions prior to SNMPv3 did not include adequate security. 2005 Even if the network itself is secure (for example by using IPSec), 2006 even then, there is no control as to who on the secure network is 2007 allowed to access and GET/SET (read/change/create/delete) the objects 2008 in this MIB module. 2010 It is RECOMMENDED that implementers consider the security features as 2011 provided by the SNMPv3 framework (see [RFC3410], section 8), 2012 including full support for the SNMPv3 cryptographic mechanisms (for 2013 authentication and privacy). 2015 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2016 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2017 enable cryptographic security. It is then a customer/operator 2018 responsibility to ensure that the SNMP entity giving access to an 2019 instance of this MIB module is properly configured to give access to 2020 the objects only to those principals (users) that have legitimate 2021 rights to indeed GET or SET (change/create/delete) them. 2023 9. IANA Considerations 2025 IANA is requested to assign this MIB module an OID under mib-2. 2027 10. Contributors 2029 This document owes significant thanks over the years to Wayne 2030 Tackabury, Susan Hares and the members of the IDR and OPS-NM mailing 2031 lists. This document represents several years of negotiating 2032 operational needs, Internet operational security considerations and 2033 the sheer messiness of representing the BGP protocol in SMIv2. 2035 I owe particular thanks to Susan Hares as a mentor who let me dive 2036 head-first into the world of Internet standards work by saying, "We 2037 have this MIB that just needs a little cleanup to advance in the 2038 standards process." 2040 11. Acknowledgements 2042 We would like to acknowledge the assistance of all the members of the 2043 Inter-Domain Routing Working Group and individuals who contributed to 2044 RFCs 1269, 1657 and 4273. 2046 The origin of this document is from RFC 1269 "Definitions of Managed 2047 Objects for the Border Gateway Protocol (Version 3)" written by Steve 2048 Willis and John Burruss, which was updated by John Chu to support 2049 BGP-4 in RFC 1657. The author wishes to acknowledge the fine work of 2050 these original authors. 2052 12. References 2054 12.1. Normative References 2056 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2057 Requirement Levels", BCP 14, RFC 2119, March 1997. 2059 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2060 Schoenwaelder, Ed., "Structure of Management Information 2061 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2063 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2064 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 2065 STD 58, RFC 2579, April 1999. 2067 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2068 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2069 April 1999. 2071 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 2072 Architecture for Describing Simple Network Management 2073 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 2074 December 2002. 2076 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 2077 Protocol 4 (BGP-4)", RFC 4271, January 2006. 2079 [RFC4273] Haas, J. and S. Hares, "Definitions of Managed Objects for 2080 BGP-4", RFC 4273, January 2006. 2082 [RFC2545] Marques, P. and F. Dupont, "Use of BGP-4 Multiprotocol 2083 Extensions for IPv6 Inter-Domain Routing", RFC 2545, 2084 March 1999. 2086 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2087 Schoenwaelder, "Textual Conventions for Internet Network 2088 Addresses", RFC 4001, February 2005. 2090 [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, 2091 "Multiprotocol Extensions for BGP-4", RFC 4760, 2092 January 2007. 2094 [RFC5065] Traina, P., McPherson, D., and J. Scudder, "Autonomous 2095 System Confederations for BGP", RFC 5065, August 2007. 2097 12.2. Informative References 2099 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2100 "Introduction and Applicability Statements for Internet- 2101 Standard Management Framework", RFC 3410, December 2002. 2103 [RFC1657] Willis, S., Burruss, J., and J. Chu, "Definitions of 2104 Managed Objects for the Fourth Version of the Border 2105 Gateway Protocol (BGP-4) using SMIv2", RFC 1657, 2106 July 1994. 2108 [RFC3107] Rekhter, Y. and E. Rosen, "Carrying Label Information in 2109 BGP-4", RFC 3107, May 2001. 2111 [RFC4022] Raghunarayan, R., "Management Information Base for the 2112 Transmission Control Protocol (TCP)", RFC 4022, 2113 March 2005. 2115 [RFC4456] Bates, T., Chen, E., and R. Chandra, "BGP Route 2116 Reflection: An Alternative to Full Mesh Internal BGP 2117 (IBGP)", RFC 4456, April 2006. 2119 Author's Address 2121 Jeffrey Haas 2122 Juniper Networks 2124 EMail: jhaas@juniper.net