idnits 2.17.1 draft-ietf-idr-bgp4-mibv2-08.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 16. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 2142. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2153. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2160. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2166. 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 Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (November 2, 2008) is 5625 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 200, 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 (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Inter-Domain Routing Working Group J. Haas 3 Internet-Draft Arbor Networks 4 Intended status: Standards Track November 2, 2008 5 Expires: May 6, 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-08 11 Status of This Memo 13 By submitting this Internet-Draft, each author represents that any 14 applicable patent or other IPR claims of which he or she is aware 15 have been or will be disclosed, and any of which he or she becomes 16 aware will be disclosed, in accordance with Section 6 of BCP 79. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on May 6, 2009. 36 Copyright Notice 38 Copyright (C) The IETF Trust (2008). 40 Abstract 42 This memo defines a portion of the Management Information Base (MIB) 43 for use with network management protocols. In particular it defines 44 objects for managing the Border Gateway Protocol, Version 4. 46 Table of Contents 48 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 49 2. The Internet-Standard Management Framework . . . . . . . . . . 3 50 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 51 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 52 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 53 5.1. Notifications . . . . . . . . . . . . . . . . . . . . . . 4 54 5.2. Tables . . . . . . . . . . . . . . . . . . . . . . . . . . 4 55 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 5 56 6.1. Relationship to the TCP-MIB . . . . . . . . . . . . . . . 5 57 6.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 5 58 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 59 8. Security Considerations . . . . . . . . . . . . . . . . . . . 42 60 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 43 61 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 43 62 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 44 63 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 44 64 12.1. Normative References . . . . . . . . . . . . . . . . . . . 44 65 12.2. Informative References . . . . . . . . . . . . . . . . . . 45 67 1. Introduction 69 This memo defines a portion of the Management Information Base (MIB) 70 for use with network management protocols. In particular it defines 71 objects for managing the Border Gateway Protocol, Version 4 72 [RFC4271]. 74 2. The Internet-Standard Management Framework 76 For a detailed overview of the documents that describe the current 77 Internet-Standard Management Framework, please refer to section 7 of 78 RFC 3410 [RFC3410]. 80 Managed objects are accessed via a virtual information store, termed 81 the Management Information Base or MIB. MIB objects are generally 82 accessed through the Simple Network Management Protocol (SNMP). 83 Objects in the MIB are defined using the mechanisms defined in the 84 Structure of Management Information (SMI). This memo specifies a MIB 85 module that is compliant to the SMIv2, which is described in STD 58, 86 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 87 [RFC2580]. 89 3. Conventions 91 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 92 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 93 document are to be interpreted as described in RFC 2119 [RFC2119]. 95 4. Overview 97 As part of the IETF standardization effort for the BGP-4 protocol, 98 [RFC4273] was written to address open issues in the previous version 99 of the BGP-4 MIB, [RFC1657]. However, that RFC was primarily 100 intended to address the base BGP-4 protocol as documented in 101 [RFC4271]. 103 The BGP-4 protocol has greatly increased in scope over the years from 104 its original definition. Scaling mechanisms such as Route Reflection 105 [RFC4456] and Confederations [RFC5065] have been introduced. Multi- 106 protocol extensions [RFC4760] were introduced which allowed 107 advertisement of reachability such as IPv6 [RFC2545], MPLS Labeled 108 routes [RFC3107], etc. 110 This MIB addresses several of the deficiencies of the previous BGP-4 111 MIB. In particular: 113 o Add the ability to monitor IPv6 BGP-4 peering sessions and carry 114 IPv6 reachability. Other forms of reachability can be added at a 115 later date courtesy of the address-family independent manner in 116 which this was done. 118 o Add several counters of operational interest. For example, the 119 number of routes received from a given BGP peer. 121 o Replaces objects that were incapable of carrying the full range of 122 their values with ones that can. 124 o Provides human-readable output for some complex data structures, 125 such as the AS_PATH while also preserving a version of the data 126 that is canonically machine readable. 128 5. Structure of the MIB Module 130 5.1. Notifications 132 o bgp4V2EstablishedNotification - Sent when a BGP peer transitions 133 into the Established state. Replaces the previous 134 bgpEstablishedNotification from RFC 4273 which was not address 135 family independent. 137 o bgp4V2BackwardTransitionNotification - Sent when a BGP peer 138 transitions out of the Established state. Replaces the previous 139 bgpBackwardTransNotification, which was not address family 140 independent. 142 5.2. Tables 144 o bgp4V2DiscontinuityTable - This MIB allows management of more than 145 one instance of the BGP-4 protocol. This table provides the 146 ability to show when a given instance of BGP-4 has suffered an 147 event that may lead to a discontinuity in its objects. 149 o bgp4V2PeerTable - The BGP peer table. This table is capable of 150 representing IPv6 and other address-family independent peering 151 sessions. This table replaces the bgpPeerTable from RFC 4273. 153 o bgp4V2PeerErrorsTable - A table of peering session errors. This 154 table covers information previously present in bgpPeerTable from 155 RFC 4273. 157 o bgp4V2PeerEventTimesTable - A table of peer-specific event timers. 158 This table covers information previously present in bgpPeerTable 159 in RFC 4273 . 161 o bgp4V2PeerConfiguredTimersTable - A table of the configured values 162 of peer-specific event timers. This table covers information 163 previously present in bgpPeerTable from RFC 4273. 165 o bgp4V2PeerNegotiatedTimersTable - A table of per-peer negotiated 166 timers. This information covers information previously derived 167 from the bgpPeerTable from RFC 4273. 169 o bgp4V2PeerCountersTable - A table of per-peer counters for 170 messages and the BGP FSM. 172 o bgp4V2PrefixGaugesTable - A table of per-peer per Address Family 173 Identifer-Subsequent Address Family Identifier (AFI-SAFI) 174 [RFC4760] gauges for prefixes. 176 o bgp4V2NlriTable - A table of per-peer per AFI-SAFI prefix data. 177 This table covers information previously present in 178 bgp4PathAttrTable from RFC 4273. 180 o bgp4V2AdjRibsOutTable - A per-peer per AFI-SAFI table indicating 181 what reachability has been advertised to a given peer. 183 6. Relationship to Other MIB Modules 185 6.1. Relationship to the TCP-MIB 187 The bgp4V2PeerLocalAddrType/bgp4V2PeerLocalAddr/bgp4V2PeerLocalPort 188 and bgp4V2PeerRemoteAddrType/bgp4V2PeerRemoteAddr/ 189 bgp4V2PeerRemotePort objects may provide a suitable index for 190 monitoring the BGP peering session's TCP session via the TCP-MIB 191 [RFC4022]. 193 Note that conducting BGP peering sessions over transport protocols 194 other than TCP over IP are out of scope of the current BGP 195 specifications. 197 6.2. MIB modules required for IMPORTS 199 The following MIB module IMPORTS objects from BGP4V2-TC-MIB 200 [I-D.draft-ietf-idr-bgp4-mibv2-tc], SNMPv2-SMI [RFC2578], SNMPv2-TC 201 [RFC2579], SNMPv2-CONF [RFC2580], INET-ADDRESS-MIB [RFC4001] and 202 SNMP-FRAMEWORK-MIB [RFC3411]. 204 7. Definitions 206 BGP4V2-MIB DEFINITIONS ::= BEGIN 208 IMPORTS 209 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 210 mib-2, Counter32, Gauge32, Unsigned32 211 FROM SNMPv2-SMI 212 InetAddressType, InetAddress, InetPortNumber, 213 InetAutonomousSystemNumber, InetAddressPrefixLength 214 FROM INET-ADDRESS-MIB 215 TruthValue, RowPointer, TimeStamp 216 FROM SNMPv2-TC 217 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 218 FROM SNMPv2-CONF 219 SnmpAdminString 220 FROM SNMP-FRAMEWORK-MIB 221 Bgp4V2IdentifierTC, Bgp4V2AddressFamilyIdentifierTC, 222 Bgp4V2SubsequentAddressFamilyIdentifierTC 223 FROM BGP4V2-TC-MIB; 225 bgp4V2 MODULE-IDENTITY 226 LAST-UPDATED "200811020000Z" 227 ORGANIZATION "IETF IDR Working Group" 228 CONTACT-INFO "E-mail: idr@ietf.org" 230 DESCRIPTION 231 "The MIB module for the BGP-4 protocol. 233 Copyright (C) The IETF Trust (2008). This 234 version of this MIB module is part of RFC XXX; 235 see the RFC itself for full legal notices." 236 -- RFC Editor - replace XXX with RFC number 238 REVISION "200811020000Z" 239 DESCRIPTION 240 "This MIB updates and replaces the BGP MIB defined in 241 RFC 4273." 242 ::= { mib-2 XXX } 244 -- Top level components of this MIB module 246 -- Notifications 247 bgp4V2Notifications OBJECT IDENTIFIER ::= { bgp4V2 0 } 249 -- Objects 250 bgp4V2Objects OBJECT IDENTIFIER ::= { bgp4V2 1 } 252 -- Conformance 253 bgp4V2Conformance OBJECT IDENTIFIER ::= { bgp4V2 2 } 255 -- 256 -- Per-instance BGP discontinuities 257 -- 259 bgp4V2DiscontinuityTable OBJECT-TYPE 260 SYNTAX SEQUENCE OF Bgp4V2DiscontinuityEntry 261 MAX-ACCESS not-accessible 262 STATUS current 263 DESCRIPTION 264 "Table of BGP-4 discontinuities. Discontinuities that have 265 external visibility occur on a per-BGP instance basis. 266 Transitions by a given BGP peer will result in a consistent 267 BGP view within that instance and thus do not represent a 268 discontinuity from a protocol standpoint." 269 ::= { bgp4V2Objects 1 } 271 bgp4V2DiscontinuityEntry OBJECT-TYPE 272 SYNTAX Bgp4V2DiscontinuityEntry 273 MAX-ACCESS not-accessible 274 STATUS current 275 DESCRIPTION 276 "Entry repsenting information about a discontinuity event 277 for a given BGP instance." 278 INDEX { 279 bgp4V2PeerInstance 280 } 281 ::= { bgp4V2DiscontinuityTable 1 } 283 Bgp4V2DiscontinuityEntry ::= SEQUENCE { 284 bgp4V2DiscontinuityTime 285 TimeStamp 286 } 288 bgp4V2DiscontinuityTime OBJECT-TYPE 289 SYNTAX TimeStamp 290 MAX-ACCESS read-only 291 STATUS current 292 DESCRIPTION 293 "The value of sysUpTime at the most recent occasion at which 294 this BGP management instance has suffered a discontinuity." 295 ::= { bgp4V2DiscontinuityEntry 1 } 297 -- 298 -- Per-peer session management information. 299 -- 301 bgp4V2PeerTable OBJECT-TYPE 302 SYNTAX SEQUENCE OF Bgp4V2PeerEntry 303 MAX-ACCESS not-accessible 304 STATUS current 305 DESCRIPTION 306 "BGP peer table. This table contains, one entry per BGP 307 peer, information about the connections with BGP peers." 308 ::= { bgp4V2Objects 2 } 310 bgp4V2PeerEntry OBJECT-TYPE 311 SYNTAX Bgp4V2PeerEntry 312 MAX-ACCESS not-accessible 313 STATUS current 314 DESCRIPTION 315 "Entry containing information about the connection with 316 a remote BGP peer." 317 INDEX { 318 bgp4V2PeerInstance, 319 bgp4V2PeerLocalAddrType, 320 bgp4V2PeerLocalAddr, 321 bgp4V2PeerRemoteAddrType, 322 bgp4V2PeerRemoteAddr 323 } 324 ::= { bgp4V2PeerTable 1 } 326 Bgp4V2PeerEntry ::= SEQUENCE { 327 -- INDEX information 328 bgp4V2PeerInstance 329 Unsigned32, 330 bgp4V2PeerLocalAddrType 331 InetAddressType, 332 bgp4V2PeerLocalAddr 333 InetAddress, 334 bgp4V2PeerRemoteAddrType 335 InetAddressType, 336 bgp4V2PeerRemoteAddr 337 InetAddress, 339 -- Local 340 bgp4V2PeerLocalPort 341 InetPortNumber, 342 bgp4V2PeerLocalAs 343 InetAutonomousSystemNumber, 344 bgp4V2PeerLocalIdentifier 345 Bgp4V2IdentifierTC, 347 -- Remote 348 bgp4V2PeerRemotePort 349 InetPortNumber, 350 bgp4V2PeerRemoteAs 351 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 -- 543 bgp4V2PeerErrorsTable OBJECT-TYPE 544 SYNTAX SEQUENCE OF Bgp4V2PeerErrorsEntry 545 MAX-ACCESS not-accessible 546 STATUS current 547 DESCRIPTION 548 "On a per-peer basis, this table reflects the last 549 protocol-defined error encountered and reported on 550 the peer session." 551 ::= { bgp4V2Objects 3 } 553 bgp4V2PeerErrorsEntry OBJECT-TYPE 554 SYNTAX Bgp4V2PeerErrorsEntry 555 MAX-ACCESS not-accessible 556 STATUS current 557 DESCRIPTION 558 "Each entry contains information about errors sent 559 and received for a particular BGP peer." 560 AUGMENTS { 561 bgp4V2PeerEntry 562 } 563 ::= { bgp4V2PeerErrorsTable 1 } 565 Bgp4V2PeerErrorsEntry ::= SEQUENCE { 566 bgp4V2PeerLastErrorCodeReceived 567 OCTET STRING, 568 bgp4V2PeerLastErrorSubCodeReceived 569 OCTET STRING, 570 bgp4V2PeerLastErrorReceivedTime 571 TimeStamp, 572 bgp4V2PeerLastErrorReceivedText 573 SnmpAdminString, 574 bgp4V2PeerLastErrorReceivedData 575 OCTET STRING, 576 bgp4V2PeerLastErrorCodeSent 577 OCTET STRING, 578 bgp4V2PeerLastErrorSubCodeSent 579 OCTET STRING, 580 bgp4V2PeerLastErrorSentTime 581 TimeStamp, 582 bgp4V2PeerLastErrorSentText 583 SnmpAdminString, 584 bgp4V2PeerLastErrorSentData 585 OCTET STRING 586 } 588 bgp4V2PeerLastErrorCodeReceived OBJECT-TYPE 589 SYNTAX OCTET STRING (SIZE (1)) 590 MAX-ACCESS read-only 591 STATUS current 592 DESCRIPTION 593 "The last error code received from this peer via 594 NOTIFICATION message on this connection. If no error has 595 occurred, this field is zero." 596 REFERENCE 597 "RFC 4271, Section 4.5. 598 RFC 4486 optionally supported. 599 RFC 3362, Section 5 optionally supported." 600 ::= { bgp4V2PeerErrorsEntry 1 } 602 bgp4V2PeerLastErrorSubCodeReceived OBJECT-TYPE 603 SYNTAX OCTET STRING (SIZE (1)) 604 MAX-ACCESS read-only 605 STATUS current 606 DESCRIPTION 607 "The last subcode received from this peer via NOTIFICATION 608 message on this connection. If no error has occurred, this 609 field is zero." 610 REFERENCE 611 "RFC 4271, Section 4.5. 612 RFC 4486 optionally supported. 613 RFC 3362, Section 5 optionally supported." 614 ::= { bgp4V2PeerErrorsEntry 2 } 616 bgp4V2PeerLastErrorReceivedTime OBJECT-TYPE 617 SYNTAX TimeStamp 618 MAX-ACCESS read-only 619 STATUS current 620 DESCRIPTION 621 "The timestamp that the last NOTIFICATION was received from 622 this peer." 623 REFERENCE 624 "RFC 4271, Section 4.5." 625 ::= { bgp4V2PeerErrorsEntry 3 } 627 bgp4V2PeerLastErrorReceivedText OBJECT-TYPE 628 SYNTAX SnmpAdminString 629 MAX-ACCESS read-only 630 STATUS current 631 DESCRIPTION 632 "This object contains an implementation specific 633 explanation of the error that was reported." 634 ::= { bgp4V2PeerErrorsEntry 4 } 636 bgp4V2PeerLastErrorReceivedData OBJECT-TYPE 637 SYNTAX OCTET STRING (SIZE(0..4075)) 638 MAX-ACCESS read-only 639 STATUS current 640 DESCRIPTION 641 "The last error code's data seen by this peer. 643 Per RFC 2578, some implementations may have limitations 644 dealing with OCTET STRINGS larger than 255. Thus, this 645 data may be truncated." 646 REFERENCE 647 "RFC 4271, Section 4.5, 648 RFC 2578, Section 7.1.2, 649 RFC 4486 optionally supported. 650 RFC 3362, Section 5 optionally supported." 651 ::= { bgp4V2PeerErrorsEntry 5 } 653 bgp4V2PeerLastErrorCodeSent OBJECT-TYPE 654 SYNTAX OCTET STRING (SIZE (1)) 655 MAX-ACCESS read-only 656 STATUS current 657 DESCRIPTION 658 "The last error code sent to this peer via NOTIFICATION 659 message on this connection. If no error has occurred, this 660 field is zero." 661 REFERENCE 662 "RFC 4271, Section 4.5. 663 RFC 4486 optionally supported. 664 RFC 3362, Section 5 optionally supported." 665 ::= { bgp4V2PeerErrorsEntry 6 } 667 bgp4V2PeerLastErrorSubCodeSent OBJECT-TYPE 668 SYNTAX OCTET STRING (SIZE (1)) 669 MAX-ACCESS read-only 670 STATUS current 671 DESCRIPTION 672 "The last subcode sent to this peer via NOTIFICATION 673 message on this connection. If no error has occurred, this 674 field is zero." 675 REFERENCE 676 "RFC 4271, Section 4.5. 677 RFC 4486 optionally supported. 678 RFC 3362, Section 5 optionally supported." 679 ::= { bgp4V2PeerErrorsEntry 7 } 681 bgp4V2PeerLastErrorSentTime OBJECT-TYPE 682 SYNTAX TimeStamp 683 MAX-ACCESS read-only 684 STATUS current 685 DESCRIPTION 686 "The timestamp that the last NOTIFICATION was sent to 687 this peer." 688 REFERENCE 689 "RFC 4271, Section 4.5." 690 ::= { bgp4V2PeerErrorsEntry 8 } 692 bgp4V2PeerLastErrorSentText OBJECT-TYPE 693 SYNTAX SnmpAdminString 694 MAX-ACCESS read-only 695 STATUS current 696 DESCRIPTION 697 "This object contains an implementation specific 698 explanation of the error that is being reported." 699 ::= { bgp4V2PeerErrorsEntry 9 } 701 bgp4V2PeerLastErrorSentData OBJECT-TYPE 702 SYNTAX OCTET STRING (SIZE(0..4075)) 703 MAX-ACCESS read-only 704 STATUS current 705 DESCRIPTION 706 "The last error code's data sent to this peer. 708 Per RFC 2578, some implementations may have limitations 709 dealing with OCTET STRINGS larger than 255. Thus, this 710 data may be truncated." 711 REFERENCE 712 "RFC 4271, Section 4.5, 713 RFC 2578, Section 7.1.2 714 RFC 4486 optionally supported. 715 RFC 3362, Section 5 optionally supported." 716 ::= { bgp4V2PeerErrorsEntry 10 } 718 -- 719 -- Per-peer Event Times 720 -- 722 bgp4V2PeerEventTimesTable OBJECT-TYPE 723 SYNTAX SEQUENCE OF Bgp4V2PeerEventTimesEntry 724 MAX-ACCESS not-accessible 725 STATUS current 726 DESCRIPTION 727 "A table reporting the per-peering session amount 728 of time elapsed and update events since the peering 729 session advanced into the established state." 730 ::= { bgp4V2Objects 4 } 732 bgp4V2PeerEventTimesEntry OBJECT-TYPE 733 SYNTAX Bgp4V2PeerEventTimesEntry 734 MAX-ACCESS not-accessible 735 STATUS current 736 DESCRIPTION 737 "Each row contains a set of statistics about time 738 spent and events encountered in the peer session 739 established state." 740 AUGMENTS { 741 bgp4V2PeerEntry 742 } 743 ::= { bgp4V2PeerEventTimesTable 1 } 745 Bgp4V2PeerEventTimesEntry ::= SEQUENCE { 746 bgp4V2PeerFsmEstablishedTime 747 Gauge32, 748 bgp4V2PeerInUpdatesElapsedTime 749 Gauge32 750 } 752 bgp4V2PeerFsmEstablishedTime OBJECT-TYPE 753 SYNTAX Gauge32 754 UNITS "seconds" 755 MAX-ACCESS read-only 756 STATUS current 757 DESCRIPTION 758 "This timer indicates how long (in seconds) this peer 759 has been in the established state or how long since this 760 peer was last in the established state. It is set to 761 zero when a new peer is configured or when the router is 762 booted. If the peer has never reached the established 763 state, the value remains zero." 764 REFERENCE 765 "RFC 4271, Section 8." 766 ::= { bgp4V2PeerEventTimesEntry 1 } 768 bgp4V2PeerInUpdatesElapsedTime OBJECT-TYPE 769 SYNTAX Gauge32 770 UNITS "seconds" 771 MAX-ACCESS read-only 772 STATUS current 773 DESCRIPTION 774 "Elapsed time (in seconds) since the last BGP UPDATE 775 message was received from the peer. Each time 776 bgpPeerInUpdates is incremented, the value of this 777 object is set to zero (0)." 778 REFERENCE 779 "RFC 4271, Section 4.3. 780 RFC 4271, Section 8.2.2, Established state." 782 ::= { bgp4V2PeerEventTimesEntry 2 } 784 -- 785 -- Per-Peer Configured Timers 786 -- 788 bgp4V2PeerConfiguredTimersTable OBJECT-TYPE 789 SYNTAX SEQUENCE OF Bgp4V2PeerConfiguredTimersEntry 790 MAX-ACCESS not-accessible 791 STATUS current 792 DESCRIPTION 793 "Per peer management data on BGP session timers." 794 ::= { bgp4V2Objects 5 } 796 bgp4V2PeerConfiguredTimersEntry OBJECT-TYPE 797 SYNTAX Bgp4V2PeerConfiguredTimersEntry 798 MAX-ACCESS not-accessible 799 STATUS current 800 DESCRIPTION 801 "Each entry corresponds to the current state of 802 BGP timers on a given peering session." 803 AUGMENTS { 804 bgp4V2PeerEntry 805 } 806 ::= { bgp4V2PeerConfiguredTimersTable 1 } 808 Bgp4V2PeerConfiguredTimersEntry ::= SEQUENCE { 809 bgp4V2PeerConnectRetryInterval 810 Unsigned32, 811 bgp4V2PeerHoldTimeConfigured 812 Unsigned32, 813 bgp4V2PeerKeepAliveConfigured 814 Unsigned32, 815 bgp4V2PeerMinASOrigInterval 816 Unsigned32, 817 bgp4V2PeerMinRouteAdverInterval 818 Unsigned32 819 } 821 bgp4V2PeerConnectRetryInterval OBJECT-TYPE 822 SYNTAX Unsigned32 (1..65535) 823 UNITS "seconds" 824 MAX-ACCESS read-only 825 STATUS current 826 DESCRIPTION 827 "Time interval (in seconds) for the ConnectRetry timer. 828 The suggested value for this timer is 120 seconds." 829 REFERENCE 830 "RFC 4271, Section 8.2.2. This is the value used 831 to initialize the 'ConnectRetryTimer'." 832 ::= { bgp4V2PeerConfiguredTimersEntry 1 } 834 bgp4V2PeerHoldTimeConfigured OBJECT-TYPE 835 SYNTAX Unsigned32 ( 0 | 3..65535 ) 836 UNITS "seconds" 837 MAX-ACCESS read-only 838 STATUS current 839 DESCRIPTION 840 "Time interval (in seconds) for the Hold Timer 841 established with the peer. The value of this object is 842 calculated by this BGP speaker, using the smaller of the 843 values in bgpPeerHoldTimeConfigured and the Hold Time 844 received in the OPEN message. 846 This value must be at least three seconds if it is not 847 zero (0). 849 If the Hold Timer has not been established with the 850 peer this object MUST have a value of zero (0). 852 If the bgpPeerHoldTimeConfigured object has a value of 853 (0), then this object MUST have a value of (0)." 854 REFERENCE 855 "RFC 4271, Section 4.2." 856 ::= { bgp4V2PeerConfiguredTimersEntry 2 } 858 bgp4V2PeerKeepAliveConfigured OBJECT-TYPE 859 SYNTAX Unsigned32 ( 0 | 1..21845 ) 860 UNITS "seconds" 861 MAX-ACCESS read-only 862 STATUS current 863 DESCRIPTION 864 "Time interval (in seconds) for the KeepAlive timer 865 configured for this BGP speaker with this peer. The 866 value of this object will only determine the KEEPALIVE 867 messages' frequency relative to the value specified in 868 bgpPeerHoldTimeConfigured; the actual time interval for 869 the KEEPALIVE messages is indicated by bgpPeerKeepAlive. 871 A reasonable maximum value for this timer would be one 872 third of that of bgpPeerHoldTimeConfigured. 874 If the value of this object is zero (0), no periodic 875 KEEPALIVE messages are sent to the peer after the BGP 876 connection has been established. The suggested value 877 for this timer is 30 seconds." 879 REFERENCE 880 "RFC 4271, Section 4.4. 881 RFC 4271, Section 10." 882 ::= { bgp4V2PeerConfiguredTimersEntry 3 } 884 bgp4V2PeerMinASOrigInterval OBJECT-TYPE 885 SYNTAX Unsigned32 (0..65535) 886 UNITS "seconds" 887 MAX-ACCESS read-only 888 STATUS current 889 DESCRIPTION 890 "Time interval (in seconds) for the 891 MinASOriginationInterval timer. 893 The suggested value for this timer is 15 seconds." 894 REFERENCE 895 "RFC 4271, Section 9.2.1.2. 896 RFC 4271, Section 10." 897 ::= { bgp4V2PeerConfiguredTimersEntry 4 } 899 bgp4V2PeerMinRouteAdverInterval OBJECT-TYPE 900 SYNTAX Unsigned32 (0..65535) 901 UNITS "seconds" 902 MAX-ACCESS read-only 903 STATUS current 904 DESCRIPTION 905 "Time interval (in seconds) for the 906 MinRouteAdvertisementInterval timer. 908 The suggested value for this timer is 30 seconds for 909 EBGP connections and 5 seconds for IBGP connections." 910 REFERENCE 911 "RFC 4271, Section 9.2.1.1. 912 RFC 4271, Section 10." 913 ::= { bgp4V2PeerConfiguredTimersEntry 5 } 915 -- 916 -- Per-Peer Negotiated Timers 917 -- 919 bgp4V2PeerNegotiatedTimersTable OBJECT-TYPE 920 SYNTAX SEQUENCE OF Bgp4V2PeerNegotiatedTimersEntry 921 MAX-ACCESS not-accessible 922 STATUS current 923 DESCRIPTION 924 "Configured values of per-peer timers are seen 925 in the bgp4V2PeerConfiguredTimersTable. 927 Values in this table reflect the current 928 operational values, after negotiation from values 929 derived from initial configuration." 930 ::= { bgp4V2Objects 6 } 932 bgp4V2PeerNegotiatedTimersEntry OBJECT-TYPE 933 SYNTAX Bgp4V2PeerNegotiatedTimersEntry 934 MAX-ACCESS not-accessible 935 STATUS current 936 DESCRIPTION 937 "Each entry reflects a value of the currently 938 operational, negotiated timer as reflected in the 939 Bgp4V2PeerNegotiatedTimersEntry." 940 AUGMENTS { 941 bgp4V2PeerEntry 942 } 943 ::= { bgp4V2PeerNegotiatedTimersTable 1 } 945 Bgp4V2PeerNegotiatedTimersEntry ::= SEQUENCE { 946 bgp4V2PeerHoldTime 947 Unsigned32, 948 bgp4V2PeerKeepAlive 949 Unsigned32 950 } 952 bgp4V2PeerHoldTime OBJECT-TYPE 953 SYNTAX Unsigned32 ( 0 | 3..65535 ) 954 UNITS "seconds" 955 MAX-ACCESS read-only 956 STATUS current 957 DESCRIPTION 958 "The value of this object is calculated by this BGP 959 Speaker as being; 961 zero (0) - if this was the value sent by the peer and 962 this value is permitted by this BGP Speaker. In this 963 case, no keepalive messages are sent and the Hold Timer 964 is not set. 966 At least three (3). This value is the smaller of 967 the value sent by this peer in the OPEN message and 968 bgp4V2PeerHoldTimeConfigured for this peer. 970 This value is only defined when the peering session is 971 in the Established state." 972 REFERENCE 973 "RFC 4271, Section 4.2." 974 ::= { bgp4V2PeerNegotiatedTimersEntry 1 } 976 bgp4V2PeerKeepAlive OBJECT-TYPE 977 SYNTAX Unsigned32 ( 0 | 1..21845 ) 978 UNITS "seconds" 979 MAX-ACCESS read-only 980 STATUS current 981 DESCRIPTION 982 "Time interval in seconds for the KeepAlive timer 983 established with the peer. The value of this object 984 is calculated by this BGP speaker such that, when 985 compared with bgp4V2PeerHoldTime, it has the same 986 proportion as what bgp4V2PeerKeepAliveConfigured has 987 when compared with bgp4V2PeerHoldTimeConfigured. If 988 the value of this object is zero (0), it indicates 989 that the KeepAlive timer has not been established 990 with the peer, or, the value of 991 bgp4V2PeerKeepAliveConfigured is zero (0). 993 This value is only defined when the peering session is 994 in the Established state." 995 REFERENCE 996 "RFC 4271, Section 4.4." 997 ::= { bgp4V2PeerNegotiatedTimersEntry 2 } 999 -- 1000 -- Per-peer counters 1001 -- 1003 bgp4V2PeerCountersTable OBJECT-TYPE 1004 SYNTAX SEQUENCE OF Bgp4V2PeerCountersEntry 1005 MAX-ACCESS not-accessible 1006 STATUS current 1007 DESCRIPTION 1008 "The counters associated with a BGP Peer." 1009 ::= { bgp4V2Objects 7 } 1011 bgp4V2PeerCountersEntry OBJECT-TYPE 1012 SYNTAX Bgp4V2PeerCountersEntry 1013 MAX-ACCESS not-accessible 1014 STATUS current 1015 DESCRIPTION 1016 "Each entry contains counters of message transmissions 1017 and FSM transitions for a given BGP Peering session." 1018 AUGMENTS { 1019 bgp4V2PeerEntry 1020 } 1021 ::= { bgp4V2PeerCountersTable 1 } 1023 Bgp4V2PeerCountersEntry ::= SEQUENCE { 1024 bgp4V2PeerInUpdates 1025 Counter32, 1026 bgp4V2PeerOutUpdates 1027 Counter32, 1028 bgp4V2PeerInTotalMessages 1029 Counter32, 1030 bgp4V2PeerOutTotalMessages 1031 Counter32, 1032 bgp4V2PeerFsmEstablishedTransitions 1033 Counter32 1034 } 1036 bgp4V2PeerInUpdates OBJECT-TYPE 1037 SYNTAX Counter32 1038 MAX-ACCESS read-only 1039 STATUS current 1040 DESCRIPTION 1041 "The number of BGP UPDATE messages received on this 1042 connection." 1043 ::= { bgp4V2PeerCountersEntry 1 } 1045 bgp4V2PeerOutUpdates OBJECT-TYPE 1046 SYNTAX Counter32 1047 MAX-ACCESS read-only 1048 STATUS current 1049 DESCRIPTION 1050 "The number of BGP UPDATE messages transmitted on this 1051 connection." 1052 ::= { bgp4V2PeerCountersEntry 2 } 1054 bgp4V2PeerInTotalMessages OBJECT-TYPE 1055 SYNTAX Counter32 1056 MAX-ACCESS read-only 1057 STATUS current 1058 DESCRIPTION 1059 "The total number of messages received from the remote 1060 peer on this connection." 1061 ::= { bgp4V2PeerCountersEntry 3 } 1063 bgp4V2PeerOutTotalMessages OBJECT-TYPE 1064 SYNTAX Counter32 1065 MAX-ACCESS read-only 1066 STATUS current 1067 DESCRIPTION 1068 "The total number of messages transmitted to the remote 1069 peer on this connection." 1070 ::= { bgp4V2PeerCountersEntry 4 } 1072 bgp4V2PeerFsmEstablishedTransitions OBJECT-TYPE 1073 SYNTAX Counter32 1074 MAX-ACCESS read-only 1075 STATUS current 1076 DESCRIPTION 1077 "The total number of times the BGP FSM transitioned into 1078 the established state for this peer." 1079 ::= { bgp4V2PeerCountersEntry 5 } 1081 -- 1082 -- Per-Peer Prefix Gauges 1083 -- 1085 bgp4V2PrefixGaugesTable OBJECT-TYPE 1086 SYNTAX SEQUENCE OF Bgp4V2PrefixCountersEntry 1087 MAX-ACCESS not-accessible 1088 STATUS current 1089 DESCRIPTION 1090 "Additional per-peer, per AFI-SAFI counters for 1091 prefixes" 1092 ::= { bgp4V2Objects 8 } 1094 bgp4V2PrefixGaugesEntry OBJECT-TYPE 1095 SYNTAX Bgp4V2PrefixCountersEntry 1096 MAX-ACCESS not-accessible 1097 STATUS current 1098 DESCRIPTION 1099 "Entry containing information about a bgp-peers prefix 1100 counters." 1101 INDEX { 1102 bgp4V2PeerInstance, 1103 bgp4V2PeerLocalAddrType, 1104 bgp4V2PeerLocalAddr, 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 1123 } 1125 bgp4V2PrefixGaugesAfi OBJECT-TYPE 1126 SYNTAX Bgp4V2AddressFamilyIdentifierTC 1127 MAX-ACCESS not-accessible 1128 STATUS current 1129 DESCRIPTION 1130 "The AFI index of the per-peer, per prefix counters" 1131 ::= { bgp4V2PrefixGaugesEntry 1 } 1133 bgp4V2PrefixGaugesSafi OBJECT-TYPE 1134 SYNTAX Bgp4V2SubsequentAddressFamilyIdentifierTC 1135 MAX-ACCESS not-accessible 1136 STATUS current 1137 DESCRIPTION 1138 "The SAFI index of the per-peer, per prefix counters" 1139 ::= { bgp4V2PrefixGaugesEntry 2 } 1141 bgp4V2PrefixInPrefixes OBJECT-TYPE 1142 SYNTAX Gauge32 1143 MAX-ACCESS read-only 1144 STATUS current 1145 DESCRIPTION 1146 "The number of prefixes received from a peer and are 1147 stored in the Adj-Ribs-In for that peer. 1149 Note that this number does not reflect prefixes that 1150 have been discarded due to policy." 1151 REFERENCE 1152 "RFC 4271, Sections 3.2 and 9." 1153 ::= { bgp4V2PrefixGaugesEntry 3 } 1155 bgp4V2PrefixInPrefixesAccepted OBJECT-TYPE 1156 SYNTAX Gauge32 1157 MAX-ACCESS read-only 1158 STATUS current 1159 DESCRIPTION 1160 "The number of prefixes for a peer that are installed 1161 in the Adj-Ribs-In and are eligible to become active 1162 in the Loc-Rib." 1163 REFERENCE 1164 "RFC 4271, Sections 3.2 and 9." 1165 ::= { bgp4V2PrefixGaugesEntry 4 } 1167 bgp4V2PrefixOutPrefixes OBJECT-TYPE 1168 SYNTAX Gauge32 1169 MAX-ACCESS read-only 1170 STATUS current 1171 DESCRIPTION 1172 "The number of prefixes for a peer that are installed 1173 in that peer's Adj-Ribs-Out." 1174 REFERENCE 1175 "RFC 4271, Sections 3.2 and 9." 1176 ::= { bgp4V2PrefixGaugesEntry 5 } 1178 -- 1179 -- BGP NLRI 1180 -- 1182 bgp4V2NlriTable OBJECT-TYPE 1183 SYNTAX SEQUENCE OF Bgp4V2NlriEntry 1184 MAX-ACCESS not-accessible 1185 STATUS current 1186 DESCRIPTION 1187 "The BGP-4 Received Path Attribute Table contains 1188 information about paths to destination networks 1189 received from all BGP4 peers. Collectively, this 1190 represents the Adj-Ribs-In. The route where 1191 bgp4V2NlriBest is true represents, for this NLRI, 1192 the route that is installed in the LocRib from the 1193 Adj-Ribs-In." 1194 REFERENCE 1195 "RFC 4271, Sections 3.2 and 9." 1196 ::= { bgp4V2Objects 9 } 1198 bgp4V2NlriEntry OBJECT-TYPE 1199 SYNTAX Bgp4V2NlriEntry 1200 MAX-ACCESS not-accessible 1201 STATUS current 1202 DESCRIPTION 1203 "Information about a path to a network." 1204 INDEX { 1205 bgp4V2PeerInstance, 1206 bgp4V2NlriAfi, 1207 bgp4V2NlriSafi, 1208 bgp4V2NlriPrefix, 1209 bgp4V2NlriPrefixLen, 1210 bgp4V2PeerLocalAddrType, 1211 bgp4V2PeerLocalAddr, 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 read-only 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." 1362 ::= { bgp4V2NlriEntry 7 } 1364 bgp4V2NlriCalcLocalPref OBJECT-TYPE 1365 SYNTAX Unsigned32 1366 MAX-ACCESS read-only 1367 STATUS current 1368 DESCRIPTION 1369 "The degree of preference calculated by the 1370 receiving BGP4 speaker for an advertised 1371 route. 1373 In the case where this prefix is ineligible, the 1374 value of this object will be zero (0)." 1375 REFERENCE 1376 "RFC 4271, Section 9.1.1" 1377 ::= { bgp4V2NlriEntry 8 } 1379 bgp4V2NlriOrigin OBJECT-TYPE 1380 SYNTAX INTEGER { 1381 igp(1),-- networks are interior 1382 egp(2),-- networks learned via the EGP protocol 1383 incomplete(3) -- networks that 1384 -- are learned by some other 1385 -- means 1386 } 1387 MAX-ACCESS read-only 1388 STATUS current 1389 DESCRIPTION 1390 "The ultimate origin of the path information." 1391 REFERENCE 1392 "RFC 4271, Section 4.3. 1393 RFC 4271, Section 5.1.1." 1394 ::= { bgp4V2NlriEntry 9 } 1396 bgp4V2NlriNextHopAddrType OBJECT-TYPE 1397 SYNTAX InetAddressType 1398 MAX-ACCESS read-only 1399 STATUS current 1400 DESCRIPTION 1401 "The address family of the address for 1402 the border router that should be used 1403 to access the destination network." 1404 ::= { bgp4V2NlriEntry 10 } 1406 bgp4V2NlriNextHopAddr OBJECT-TYPE 1407 SYNTAX InetAddress (SIZE(4..20)) 1408 MAX-ACCESS read-only 1409 STATUS current 1410 DESCRIPTION 1411 "The address of the border router that 1412 should be used to access the destination 1413 network. This address is the nexthop 1414 address received in the UPDATE packet associated with 1415 this prefix. 1417 Note that for RFC2545 style double nexthops, 1418 this object will always contain the global scope 1419 nexthop. bgpPathAttrLinkLocalNextHop will contain 1420 the linklocal scope nexthop, if it is present. 1422 In the case a mechanism is developed to use only a link 1423 local nexthop, bgp4V2NlriNextHopAddr will contain the 1424 link local nexthop." 1425 REFERENCE 1426 "RFC 4271, Section 4.3, 1427 RFC 4271, Section 5.1.3, 1428 RFC 2545, Section 3." 1429 ::= { bgp4V2NlriEntry 11 } 1431 bgp4V2NlriLinkLocalNextHopAddrType OBJECT-TYPE 1432 SYNTAX InetAddressType 1433 MAX-ACCESS read-only 1434 STATUS current 1435 DESCRIPTION 1436 "The address type for IPv6 link local addresses. 1437 This is present only when receiving RFC 2545 1438 style double nexthops. 1440 This object is optionally present in BGP 1441 implementations that do not support IPv6. 1443 When no IPv6 link local nexthop is present, the value of 1444 this object should be unknown(0)." 1445 REFERENCE 1446 "RFC 2545, Section 3." 1447 ::= { bgp4V2NlriEntry 12 } 1449 bgp4V2NlriLinkLocalNextHopAddr OBJECT-TYPE 1450 SYNTAX InetAddress 1451 MAX-ACCESS read-only 1452 STATUS current 1453 DESCRIPTION 1454 "This value contains an IPv6 link local address 1455 and is present only when receiving RFC 2545 style 1456 double nexthops. 1458 This object is optionally present in BGP 1459 implementations that do not support IPv6. 1461 When no IPv6 link local nexthop is present, the length of 1462 this object should be zero." 1463 REFERENCE 1464 "RFC 2545, Section 3." 1465 ::= { bgp4V2NlriEntry 13 } 1467 bgp4V2NlriLocalPrefPresent OBJECT-TYPE 1468 SYNTAX TruthValue 1469 MAX-ACCESS read-only 1470 STATUS current 1471 DESCRIPTION 1472 "This value is true when the LOCAL_PREF value was sent in 1473 the UPDATE message." 1474 ::= { bgp4V2NlriEntry 14 } 1476 bgp4V2NlriLocalPref OBJECT-TYPE 1477 SYNTAX Unsigned32 1478 MAX-ACCESS read-only 1479 STATUS current 1480 DESCRIPTION 1481 "The originating BGP4 speakers degree of preference for an 1482 advertised route." 1483 REFERENCE 1484 "RFC 4271, Section 4.3. 1485 RFC 4271, Section 5.1.5." 1486 ::= { bgp4V2NlriEntry 15 } 1488 bgp4V2NlriMedPresent OBJECT-TYPE 1489 SYNTAX TruthValue 1490 MAX-ACCESS read-only 1491 STATUS current 1492 DESCRIPTION 1493 "This value is true when the MED value was sent in 1494 the UPDATE message." 1495 ::= { bgp4V2NlriEntry 16 } 1497 bgp4V2NlriMed OBJECT-TYPE 1498 SYNTAX Unsigned32 1499 MAX-ACCESS read-only 1500 STATUS current 1501 DESCRIPTION 1502 "This metric is used to discriminate between multiple 1503 exit points to an adjacent autonomous system. When the MED 1504 value is absent but has a calculated default value, this 1505 object will contain the calculated value." 1507 REFERENCE 1508 "RFC 4271, Section 4.3. 1509 RFC 4271, Section 5.1.4." 1510 ::= { bgp4V2NlriEntry 17 } 1512 bgp4V2NlriAtomicAggregate OBJECT-TYPE 1513 SYNTAX TruthValue 1514 MAX-ACCESS read-only 1515 STATUS current 1516 DESCRIPTION 1517 "This value is true when the ATOMIC_AGGREGATE Path Attribute 1518 is present and indicates that the NLRI MUST NOT be made 1519 more specific." 1520 REFERENCE 1521 "RFC 4271, Sections 5.1.6 and 9.1.4." 1522 ::= { bgp4V2NlriEntry 18 } 1524 bgp4V2NlriAggregatorPresent OBJECT-TYPE 1525 SYNTAX TruthValue 1526 MAX-ACCESS read-only 1527 STATUS current 1528 DESCRIPTION 1529 "This value is true when the AGGREGATOR path attribute 1530 was sent in the UPDATE message." 1531 ::= { bgp4V2NlriEntry 19 } 1533 bgp4V2NlriAggregatorAS OBJECT-TYPE 1534 SYNTAX InetAutonomousSystemNumber 1535 MAX-ACCESS read-only 1536 STATUS current 1537 DESCRIPTION 1538 "The AS number of the last BGP4 speaker that performed route 1539 aggregation. When bgp4V2NlriAggregatorPresent is 1540 false, the value of this object should be zero (0)." 1541 REFERENCE 1542 "RFC 4271, Section 5.1.7. 1543 RFC 4271, Section 9.2.2.2." 1544 ::= { bgp4V2NlriEntry 20 } 1546 bgp4V2NlriAggregatorAddr OBJECT-TYPE 1547 SYNTAX Bgp4V2IdentifierTC 1548 MAX-ACCESS read-only 1549 STATUS current 1550 DESCRIPTION 1551 "The IP address of the last BGP4 speaker that performed 1552 route aggregation. When bgp4V2NlriAggregatorPresent is 1553 false, the value of this object should be 0.0.0.0" 1554 REFERENCE 1555 "RFC 4271, Section 5.1.7. 1556 RFC 4271, Section 9.2.2.2." 1557 ::= { bgp4V2NlriEntry 21 } 1559 bgp4V2NlriAsPathCalcLength OBJECT-TYPE 1560 SYNTAX Unsigned32 1561 MAX-ACCESS read-only 1562 STATUS current 1563 DESCRIPTION 1564 "This value represents the calculated length of the 1565 AS Path according to the rules of the BGP 1566 specification. This value is used in route selection." 1567 REFERENCE 1568 "RFC 4271, Section 9.1.2.2.a" 1569 ::= { bgp4V2NlriEntry 22 } 1571 bgp4V2NlriAsPathString OBJECT-TYPE 1572 SYNTAX SnmpAdminString 1573 MAX-ACCESS read-only 1574 STATUS current 1575 DESCRIPTION 1576 "This is a string depicting the autonomous system 1577 path to this network which was received from the 1578 peer which advertised it. The format of the string 1579 is implementation-dependent, and should be designed 1580 for operator readability. 1582 Note that SnmpAdminString is only capable of representing a 1583 maximum of 255 characters. This may lead to the string 1584 being truncated in the presence of a large AS Path. It is 1585 RECOMMENDED that when this object's contents will be 1586 truncated that the final 3 octets be reserved for the 1587 ellipses string, '...'. bgp4V2NlriAsPath may give access 1588 to the full AS Path." 1589 ::= { bgp4V2NlriEntry 23 } 1591 -- Maximum size of the following is derived as 1592 -- 4096 max message size 1593 -- - 16 BGP message marker bytes 1594 -- - 2 BGP message size 1595 -- - 1 BGP message type (UPDATE with unknown attr) 1596 -- - 2 UPDATE routes length (even assuming no routes) 1597 -- - 2 UPDATE path attributes length 1598 -- - 1 path attribute flag octet 1599 -- --------- 1600 -- 4072 bytes maximum per-message attribute value data 1602 bgp4V2NlriAsPath OBJECT-TYPE 1603 SYNTAX OCTET STRING (SIZE(2..4072)) 1604 MAX-ACCESS read-only 1605 STATUS current 1606 DESCRIPTION 1607 "In order to provide a canonicalized form of the BGP-4 1608 AS_PATH along with the human-readable 1609 bgp4V2NlriAsPathString, which may be truncated, this object 1610 contains the contents of the BGP-4 AS_PATH Path Attribute. 1611 This object may be parsed using the rules defined for 1612 Four-octet ASes as defined in RFC 4893. RFC 4271, Section 1613 4.3, 'Path Attributes: b) AS_PATH' as amended by RFC 5065, 1614 Section 3 defines the general format of the AS_PATH path 1615 attribute and its code points. 1617 In brief, the AS_PATH is composed of a sequence of AS 1618 Segments. Each AS Segment is represented by a triple: 1619 . 1622 The path segment type and path segment length fields are 1623 one octet in length each. 1625 The path segment type field may be one of: 1626 1 - AS_SET (RFC 4721, Section 4.3) 1627 2 - AS_SEQUENCE (RFC 4721, Section 4.3) 1628 3 - AS_CONFED_SEQUENCE (RFC 3065, Section 5) 1629 4 - AS_CONFED_SET (RFC 3065, Section 5) 1631 The path segment length field contains the number of ASes 1632 (not the number of octets) in the path segment value field. 1634 The path segment value field contains one or more AS 1635 numbers, each encoded as a 4-octet length field in network 1636 byte order. 1638 Note that since an SNMP agent may truncate this object to 1639 less than its maximum theoretical length of 4072 octets 1640 users of this object should be prepared to deal with a 1641 truncated and thus malformed AS_PATH. It is RECOMMENDED 1642 that when such truncation would occur on the boundary of an 1643 encoded AS that the partial AS be discarded from this 1644 object and the object's size be adjusted accordingly. 1645 Further, it is also RECOMMENDED that when such truncation, 1646 either alone or in conjuction with the truncation of a 1647 partially encoded AS described previously, would yield an 1648 empty path segment value field that the path segment type 1649 and path segment length components of the truncated AS_PATH 1650 also be discarded and the object's size be adjusted 1651 accordingly." 1652 REFERENCE 1653 "RFC 4271, Section 4.3. 1654 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 bgp4V2NlriPrefix, 1704 bgp4V2NlriPrefixLen, 1705 bgp4V2PeerLocalAddrType, 1706 bgp4V2PeerLocalAddr, 1707 bgp4V2PeerRemoteAddrType, 1708 bgp4V2PeerRemoteAddr, 1709 bgp4V2AdjRibsOutIndex 1710 } 1711 ::= { bgp4V2AdjRibsOutTable 1 } 1713 Bgp4V2AdjRibsOutEntry ::= SEQUENCE { 1714 bgp4V2AdjRibsOutIndex 1715 Unsigned32, 1716 bgp4V2AdjRibsOutRoute 1717 RowPointer 1718 } 1720 bgp4V2AdjRibsOutIndex OBJECT-TYPE 1721 SYNTAX Unsigned32 1722 MAX-ACCESS not-accessible 1723 STATUS current 1724 DESCRIPTION 1725 "Certain extensions to BGP permit multiple instance of 1726 a per afi, per safi prefix to be advertised to a peer. 1727 This object allows the enumeration of them." 1728 ::= { bgp4V2AdjRibsOutEntry 1 } 1730 bgp4V2AdjRibsOutRoute OBJECT-TYPE 1731 SYNTAX RowPointer 1732 MAX-ACCESS read-only 1733 STATUS current 1734 DESCRIPTION 1735 "This object points to the route in the bgp4V2NlriTable 1736 that corresponds to the entry in the peer's 1737 Adj-Rib-Out. Outgoing route maps are not 1738 reflected at this point as those are part of the 1739 Update-Send process." 1740 REFERENCE 1741 "RFC 4271, Section 9.2." 1742 ::= { bgp4V2AdjRibsOutEntry 2 } 1744 -- 1745 -- Notifications 1746 -- 1748 bgp4V2EstablishedNotification NOTIFICATION-TYPE 1749 OBJECTS { 1750 bgp4V2PeerState, 1751 bgp4V2PeerLocalPort, 1752 bgp4V2PeerRemotePort 1753 } 1754 STATUS current 1755 DESCRIPTION 1756 "The BGP Established event is generated when 1757 the BGP FSM enters the established state." 1758 ::= { bgp4V2Notifications 1 } 1760 bgp4V2BackwardTransitionNotification NOTIFICATION-TYPE 1761 OBJECTS { 1762 bgp4V2PeerState, 1763 bgp4V2PeerLocalPort, 1764 bgp4V2PeerRemotePort, 1765 bgp4V2PeerLastErrorCodeReceived, 1766 bgp4V2PeerLastErrorSubCodeReceived, 1767 bgp4V2PeerLastErrorReceivedText 1768 } 1769 STATUS current 1770 DESCRIPTION 1771 "The BGPBackwardTransition Event is generated 1772 when the BGP FSM moves from a higher numbered 1773 state to a lower numbered state. 1775 Due to the nature of the BGP state machine, an 1776 implementation MAY rate limit the generation of this event. 1777 An implementation MAY also generate this notification ONLY 1778 when the state machine moves out of the established state. 1779 An implementation should document its specific behavior." 1780 ::= { bgp4V2Notifications 2 } 1782 -- 1783 -- Conformance Information 1784 -- 1786 bgp4V2Compliances OBJECT IDENTIFIER ::= 1787 { bgp4V2Conformance 1 } 1789 bgp4V2Groups OBJECT IDENTIFIER ::= 1790 { bgp4V2Conformance 2 } 1792 bgp4V2Compliance MODULE-COMPLIANCE 1793 STATUS current 1794 DESCRIPTION 1795 "The compliance statement for entities which 1796 implement the BGP4 mib." 1797 MODULE -- this module 1798 MANDATORY-GROUPS { 1799 bgp4V2StdMIBTimersGroup, 1800 bgp4V2StdMIBCountersGroup, 1801 bgp4V2StdMIBErrorsGroup, 1802 bgp4V2StdMIBPeerGroup, 1803 bgp4V2StdMIBNlriGroup, 1804 bgp4V2GlobalsGroup 1805 } 1806 GROUP bgp4V2StdMIBNotificationGroup 1807 DESCRIPTION 1808 "Implementation of BGP Notifications are completely 1809 optional in this MIB." 1811 OBJECT bgp4V2PeerLocalAddr 1812 SYNTAX InetAddress (SIZE(4|16|20)) 1813 DESCRIPTION 1814 "An implementation is required to support IPv4 peering 1815 sessions. An implementation MAY support IPv6 peering 1816 sessions. IPv6 link-local peering sessions MAY be 1817 supported by this MIB." 1819 OBJECT bgp4V2PeerRemoteAddr 1820 SYNTAX InetAddress (SIZE(4|16|20)) 1821 DESCRIPTION 1822 "An implementation is required to support IPv4 peering 1823 sessions. An implementation MAY support IPv6 peering 1824 sessions. IPv6 link-local peering sessions MAY be 1825 supported by this MIB." 1827 OBJECT bgp4V2NlriPrefix 1828 SYNTAX InetAddress (SIZE(0..16)) 1829 DESCRIPTION 1830 "An implementation is required to support IPv4 prefixes. 1831 An implementation MAY support IPv6 prefixes." 1833 OBJECT bgp4V2NlriLinkLocalNextHopAddrType 1834 SYNTAX InetAddressType 1835 DESCRIPTION 1836 "This object is only present when RFC 2545 extensions for 1837 IPv6 are supported by the implementation. When present, 1838 this object shall only have a value of ipv6z or none." 1840 OBJECT bgp4V2NlriLinkLocalNextHopAddr 1841 SYNTAX InetAddress (SIZE(0|20)) 1842 DESCRIPTION 1843 "This object is only present when RFC 2545 extensions for 1844 IPv6 are supported by the implementation. When present, 1845 this object shall only have a size of 20 or 0 when no 1846 RFC 2545 double-nexthop is present." 1848 OBJECT bgp4V2PeerInstance 1849 SYNTAX Unsigned32 (1..4294967295) 1850 DESCRIPTION 1851 "This object represents an abstract index which can utilize 1852 the full range of acceptable SNMP index values." 1854 ::= { bgp4V2Compliances 4 } 1856 bgp4V2GlobalsGroup OBJECT-GROUP 1857 OBJECTS { bgp4V2DiscontinuityTime } 1858 STATUS current 1859 DESCRIPTION 1860 "A collection of objects providing information on global 1861 BGP state." 1862 ::= { bgp4V2Groups 1 } 1864 bgp4V2StdMIBTimersGroup OBJECT-GROUP 1865 OBJECTS { 1866 bgp4V2PeerFsmEstablishedTime, 1867 bgp4V2PeerInUpdatesElapsedTime, 1868 bgp4V2PeerConnectRetryInterval, 1869 bgp4V2PeerHoldTimeConfigured, 1870 bgp4V2PeerKeepAliveConfigured, 1871 bgp4V2PeerMinASOrigInterval, 1872 bgp4V2PeerMinRouteAdverInterval, 1873 bgp4V2PeerHoldTime, 1874 bgp4V2PeerKeepAlive 1875 } 1876 STATUS current 1877 DESCRIPTION 1878 "Objects associated with BGP peering timers." 1879 ::= { bgp4V2Groups 2 } 1881 bgp4V2StdMIBCountersGroup OBJECT-GROUP 1882 OBJECTS { 1883 bgp4V2PeerInUpdates, 1884 bgp4V2PeerOutUpdates, 1885 bgp4V2PeerInTotalMessages, 1886 bgp4V2PeerOutTotalMessages, 1887 bgp4V2PeerFsmEstablishedTransitions, 1888 bgp4V2PrefixInPrefixes, 1889 bgp4V2PrefixInPrefixesAccepted, 1890 bgp4V2PrefixOutPrefixes 1891 } 1892 STATUS current 1893 DESCRIPTION 1894 "Objects to count discrete events and exchanges on BGP 1895 sessions." 1896 ::= { bgp4V2Groups 3 } 1898 bgp4V2StdMIBErrorsGroup OBJECT-GROUP 1899 OBJECTS { 1900 bgp4V2PeerLastErrorCodeReceived, 1901 bgp4V2PeerLastErrorSubCodeReceived, 1902 bgp4V2PeerLastErrorReceivedData, 1903 bgp4V2PeerLastErrorReceivedTime, 1904 bgp4V2PeerLastErrorReceivedText, 1905 bgp4V2PeerLastErrorCodeSent, 1906 bgp4V2PeerLastErrorSubCodeSent, 1907 bgp4V2PeerLastErrorSentData, 1908 bgp4V2PeerLastErrorSentTime, 1909 bgp4V2PeerLastErrorSentText 1910 } 1911 STATUS current 1912 DESCRIPTION 1913 "Errors received on BGP peering sessions." 1914 ::= { bgp4V2Groups 5 } 1916 bgp4V2StdMIBPeerGroup OBJECT-GROUP 1917 OBJECTS { 1918 bgp4V2PeerState, 1919 bgp4V2PeerAdminStatus, 1920 bgp4V2PeerLocalPort, 1921 bgp4V2PeerLocalAs, 1922 bgp4V2PeerRemotePort, 1923 bgp4V2PeerRemoteAs, 1924 bgp4V2PeerLocalIdentifier, 1925 bgp4V2PeerRemoteIdentifier, 1926 bgp4V2PeerDescription 1927 } 1928 STATUS current 1929 DESCRIPTION 1930 "Core object types on BGP peering sessions." 1931 ::= { bgp4V2Groups 6 } 1933 bgp4V2StdMIBNlriGroup OBJECT-GROUP 1934 OBJECTS { 1935 bgp4V2NlriAsPathCalcLength, 1936 bgp4V2NlriAsPathString, 1937 bgp4V2NlriBest, 1938 bgp4V2NlriCalcLocalPref, 1939 bgp4V2NlriPrefixType, 1940 bgp4V2AdjRibsOutRoute, 1941 bgp4V2NlriAggregatorPresent, 1942 bgp4V2NlriAggregatorAS, 1943 bgp4V2NlriAggregatorAddr, 1944 bgp4V2NlriAtomicAggregate, 1945 bgp4V2NlriLocalPref, 1946 bgp4V2NlriLocalPrefPresent, 1947 bgp4V2NlriMed, 1948 bgp4V2NlriMedPresent, 1949 bgp4V2NlriNextHopAddr, 1950 bgp4V2NlriNextHopAddrType, 1951 bgp4V2NlriLinkLocalNextHopAddrType, 1952 bgp4V2NlriLinkLocalNextHopAddr, 1953 bgp4V2NlriOrigin, 1954 bgp4V2NlriAsPath, 1955 bgp4V2NlriPathAttrUnknown 1956 } 1957 STATUS current 1958 DESCRIPTION 1959 "Attributes received on BGP peering sessions." 1960 ::= { bgp4V2Groups 7 } 1962 bgp4V2StdMIBNotificationGroup NOTIFICATION-GROUP 1963 NOTIFICATIONS { 1964 bgp4V2EstablishedNotification, 1965 bgp4V2BackwardTransitionNotification 1966 } 1967 STATUS current 1968 DESCRIPTION 1969 "Notifications in this modules are completely optional." 1970 ::= { bgp4V2Groups 8 } 1972 END 1974 8. Security Considerations 1976 There are no management objects defined in this MIB module that have 1977 a MAX-ACCESS clause of read-write and/or read-create. So, if this 1978 MIB module is implemented correctly, then there is no risk that an 1979 intruder can alter or create any management objects of this MIB 1980 module via direct SNMP SET operations. 1982 Some of the readable objects in this MIB module (i.e., objects with a 1983 MAX-ACCESS other than not-accessible) may be considered sensitive or 1984 vulnerable in some network environments. It is thus important to 1985 control even GET and/or NOTIFY access to these objects and possibly 1986 to even encrypt the values of these objects when sending them over 1987 the network via SNMP. These are the tables and objects and their 1988 sensitivity/vulnerability: 1990 o bgp4V2PeerLocalAddrType, bgp4V2PeerLocalAddr, bgp4V2PeerLocalPort 1991 bgp4V2PeerRemoteAddrType, bgp4V2PeerRemoteAddr, 1992 bgp4V2PeerRemotePort, bgp4V2PeerLocalAddr, bgp4V2PeerLocalPort, 1993 bgp4V2PeerRemoteAddr, bgp4V2PeerRemotePort - A BGP peer's local 1994 and remote addresses might be sensitive for ISPs who want to keep 1995 interface addresses on routers confidential in order to prevent 1996 router addresses used for a denial of service attack or spoofing. 1997 Note that other tables which share elements of these objects as 1998 indexes may similarly expose sensitive information. 2000 o bgp4V2NlriTable, bgp4V2AdjRibsOutTable - A BGP peer's routing 2001 information may be sensitive for ISPs as the contents of their 2002 routing tables may expose details related to business 2003 relationships as implemented in Internet routing. 2005 SNMP versions prior to SNMPv3 did not include adequate security. 2006 Even if the network itself is secure (for example by using IPSec), 2007 even then, there is no control as to who on the secure network is 2008 allowed to access and GET/SET (read/change/create/delete) the objects 2009 in this MIB module. 2011 It is RECOMMENDED that implementers consider the security features as 2012 provided by the SNMPv3 framework (see [RFC3410], section 8), 2013 including full support for the SNMPv3 cryptographic mechanisms (for 2014 authentication and privacy). 2016 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2017 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2018 enable cryptographic security. It is then a customer/operator 2019 responsibility to ensure that the SNMP entity giving access to an 2020 instance of this MIB module is properly configured to give access to 2021 the objects only to those principals (users) that have legitimate 2022 rights to indeed GET or SET (change/create/delete) them. 2024 9. IANA Considerations 2026 IANA is requested to assign this MIB module an OID under mib-2. 2028 10. Contributors 2030 This document owes significant thanks over the years to Wayne 2031 Tackabury, Susan Hares and the members of the IDR and OPS-NM mailing 2032 lists. This document represents several years of negotiating 2033 operational needs, Internet operational security considerations and 2034 the sheer messiness of representing the BGP protocol in SMIv2. 2036 I owe particular thanks to Susan Hares as a mentor who let me dive 2037 head-first into the world of Internet standards work by saying, "We 2038 have this MIB that just needs a little cleanup to advance in the 2039 standards process." 2041 11. Acknowledgements 2043 We would like to acknowledge the assistance of all the members of the 2044 Inter-Domain Routing Working Group, all individuals you contributed 2045 to RFCs 1269, 1657 and 4273. 2047 The origin of this document is from RFC 1269 "Definitions of Managed 2048 Objects for the Border Gateway Protocol (Version 3)" written by Steve 2049 Willis and John Burruss, which was updated by John Chu to support 2050 BGP-4 in RFC 1657. The author wishes to acknowledge the fine work of 2051 these original authors. 2053 12. References 2055 12.1. Normative References 2057 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2058 Requirement Levels", BCP 14, RFC 2119, March 1997. 2060 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2061 Schoenwaelder, Ed., "Structure of Management Information 2062 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2064 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2065 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 2066 STD 58, RFC 2579, April 1999. 2068 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2069 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2070 April 1999. 2072 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 2073 Architecture for Describing Simple Network Management 2074 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 2075 December 2002. 2077 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 2078 Protocol 4 (BGP-4)", RFC 4271, January 2006. 2080 [RFC4273] Haas, J. and S. Hares, "Definitions of Managed Objects for 2081 BGP-4", RFC 4273, January 2006. 2083 [RFC2545] Marques, P. and F. Dupont, "Use of BGP-4 Multiprotocol 2084 Extensions for IPv6 Inter-Domain Routing", RFC 2545, 2085 March 1999. 2087 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2088 Schoenwaelder, "Textual Conventions for Internet Network 2089 Addresses", RFC 4001, February 2005. 2091 [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, 2092 "Multiprotocol Extensions for BGP-4", RFC 4760, 2093 January 2007. 2095 [RFC5065] Traina, P., McPherson, D., and J. Scudder, "Autonomous 2096 System Confederations for BGP", RFC 5065, August 2007. 2098 12.2. Informative References 2100 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2101 "Introduction and Applicability Statements for Internet- 2102 Standard Management Framework", RFC 3410, December 2002. 2104 [RFC1657] Willis, S., Burruss, J., and J. Chu, "Definitions of 2105 Managed Objects for the Fourth Version of the Border 2106 Gateway Protocol (BGP-4) using SMIv2", RFC 1657, 2107 July 1994. 2109 [RFC3107] Rekhter, Y. and E. Rosen, "Carrying Label Information in 2110 BGP-4", RFC 3107, May 2001. 2112 [RFC4022] Raghunarayan, R., "Management Information Base for the 2113 Transmission Control Protocol (TCP)", RFC 4022, 2114 March 2005. 2116 [RFC4456] Bates, T., Chen, E., and R. Chandra, "BGP Route 2117 Reflection: An Alternative to Full Mesh Internal BGP 2118 (IBGP)", RFC 4456, April 2006. 2120 Author's Address 2122 Jeffrey Haas 2123 Arbor Networks 2125 Phone: 2126 EMail: jhaas@arbor.net 2128 Full Copyright Statement 2130 Copyright (C) The IETF Trust (2008). 2132 This document is subject to the rights, licenses and restrictions 2133 contained in BCP 78, and except as set forth therein, the authors 2134 retain all their rights. 2136 This document and the information contained herein are provided on an 2137 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2138 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 2139 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 2140 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 2141 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2142 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2144 Intellectual Property 2146 The IETF takes no position regarding the validity or scope of any 2147 Intellectual Property Rights or other rights that might be claimed to 2148 pertain to the implementation or use of the technology described in 2149 this document or the extent to which any license under such rights 2150 might or might not be available; nor does it represent that it has 2151 made any independent effort to identify any such rights. Information 2152 on the procedures with respect to rights in RFC documents can be 2153 found in BCP 78 and BCP 79. 2155 Copies of IPR disclosures made to the IETF Secretariat and any 2156 assurances of licenses to be made available, or the result of an 2157 attempt made to obtain a general license or permission for the use of 2158 such proprietary rights by implementers or users of this 2159 specification can be obtained from the IETF on-line IPR repository at 2160 http://www.ietf.org/ipr. 2162 The IETF invites any interested party to bring to its attention any 2163 copyrights, patents or patent applications, or other proprietary 2164 rights that may cover technology that may be required to implement 2165 this standard. Please address the information to the IETF at 2166 ietf-ipr@ietf.org. 2168 Acknowledgement 2170 Funding for the RFC Editor function is provided by the IETF 2171 Administrative Support Activity (IASA).