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