idnits 2.17.1 draft-ietf-idr-bgp4-mibv2-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document is more than 15 pages and seems to lack a Table of Contents. == No 'Intended status' indicated for this document; assuming Proposed Standard -- Found 98 instances of the string 'FORMFEED[Page...' -- is this a case of missing nroff postprocessing? Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There are 2914 instances of lines with control characters in the document. == There are 2 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 2967: '...dicates that the NLRI MUST NOT be made...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 244 has weird spacing: '...ient of the l...' == Line 353 has weird spacing: '...mmTable conta...' == Line 1171 has weird spacing: '... on the sessi...' == Line 4085 has weird spacing: '... There are ...' -- 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 (January 12, 2004) is 7408 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: 'REF' is mentioned on line 4104, but not defined == Unused Reference: 'RFC2574' is defined on line 4204, but no explicit reference was found in the text == Unused Reference: 'RFC2580' is defined on line 4216, but no explicit reference was found in the text == Unused Reference: 'RFC3411' is defined on line 4220, but no explicit reference was found in the text == Unused Reference: 'RFC3413' is defined on line 4224, but no explicit reference was found in the text == Unused Reference: 'RFC3415' is defined on line 4227, but no explicit reference was found in the text == Unused Reference: 'RFC3416' is defined on line 4231, but no explicit reference was found in the text == Unused Reference: 'RFC3417' is defined on line 4235, but no explicit reference was found in the text == Unused Reference: 'RFC1213' is defined on line 4238, but no explicit reference was found in the text == Unused Reference: 'RFC1771' is defined on line 4252, but no explicit reference was found in the text == Unused Reference: 'RFC1772' is defined on line 4255, but no explicit reference was found in the text == Unused Reference: 'BGP-EXTCOMM' is defined on line 4270, but no explicit reference was found in the text == Unused Reference: 'RFC1901' is defined on line 4278, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1657 (Obsoleted by RFC 4273) == Outdated reference: A later version (-15) exists of draft-ietf-idr-bgp4-mib-06 ** Obsolete normative reference: RFC 1771 (Obsoleted by RFC 4271) ** Obsolete normative reference: RFC 3065 (Obsoleted by RFC 5065) ** Obsolete normative reference: RFC 2858 (Obsoleted by RFC 4760) ** Obsolete normative reference: RFC 2796 (Obsoleted by RFC 4456) -- Possible downref: Non-RFC (?) normative reference: ref. 'BGP-EXTCOMM' ** Obsolete normative reference: RFC 3107 (Obsoleted by RFC 8277) -- Obsolete informational reference (is this intentional?): RFC 2576 (Obsoleted by RFC 3584) Summary: 13 errors (**), 0 flaws (~~), 21 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Inter-Domain Routing Working Group J. Haas 2 Internet Draft NextHop 3 S. Hares 4 NextHop 5 W. Tackabury 6 Gold Wire Technology 8 January 12, 2004 10 Definitions of Managed Objects 11 for the Fourth Version of Border Gateway Protocol (BGP-4), 12 Second Version 13 15 Status of this Memo 17 This document is an Internet-Draft and is in full conformance with 18 all provisions of Section 10 of RFC2026. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference mate- 28 rial or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 Copyright Notice 38 Copyright (C) The Internet Society (2002). All Rights Reserved. 40 Abstract 42 This memo defines a portion of the Management Information Base (MIB) 43 for use with network management protocols in TCP/IP-based internets. 44 In particular, this MIB defines objects that facilitate the 45 management of the Border Gateway Protocol Version 4 (BGP4). 47 Distribution of this memo is unlimited. 49 1. Introduction 51 This memo defines a portion of the Management Information Base (MIB) 52 for use with network management protocols in the Internet community. 53 In particular, it describes managed objects used for managing the 54 Border Gateway Protocol Version 4. 56 The Internet-Standard Management Framework 58 For a detailed overview of the documents that describe the current 59 Internet-Standard Management Framework, please refer to section 7 of 60 RFC 3410 [RFC3410]. 62 Managed objects are accessed via a virtual information store, termed 63 the Management Information Base or MIB. MIB objects are generally 64 accessed through the Simple Network Management Protocol (SNMP). 65 Objects in the MIB are defined using the mechanisms defined in the 66 Structure of Management Information (SMI). This memo specifies a MIB 67 module that is compliant to the SMIv2, which is described in STD 58, 68 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 70 2. Objectives 72 This MIB Module is meant to broadly update and replace a prior MIB 73 Module defined in RFC 1657 [RFC1657]. Additionally, there is another 74 effort underway to address very specific limited objectives in updat- 75 ing points in the RFC 1657 object definition and managed object 76 attributes [MIB-DRAFT]. The MIB Module described herein is intended 77 to fully serve the functions and scope of RFC 1657 and these RFC 1657 78 updates. 80 2.1. Protocol Extensions 82 Additionally, however, there are a number of ways in which the BGP 83 Protocol has been enhanced through its ability for added capabili- 84 ties. Implementations of those capabilities have not been able to 85 have any management capabilities present in RFC 1657-compliant MIB 86 module agents, since the capabilities themselves postdated the adop- 87 tion of RFC 1657. For several significant capabilities, in the form 88 of BGP Communities [RFC1997], Autonomous System Confederation 90 [RFC3065] , BGP Multiprotocol Extensions [RFC2858], and Route Reflec- 91 tion [RFC2796], the MIB Module defined in this document exposes 92 object types to manage those extended capabilities and their opera- 93 tion. 95 One of these extensions in particular (the multiprotocol extensions) 96 requires a thorough redefinition of MIB table row indices from the 97 RFC 1657 state. This allows transport-independent address indices 98 consistent with the Address Family Identifier (AFI) and Subsequent 99 Address Family Identifier (SAFI) mechanisms of that extension. 101 2.2. Mechanisms for MIB Extensibility 103 Moreover, the requirement for the incremental update of support for 104 capabilities such as these begs the issue of placing modular extensi- 105 bility for protocol extensions within the framework of the MIB 106 itself. Going forward, it would be very desirable to have attributes 107 of the MIB structure, and administrative procedures, to allow the 108 incremental update of the MIB scope to cover any such new protocol 109 extensions, without requiring a reissue of the entire MIB. In this 110 sense, we seek to structure the MIB much like the underlying BGP4 111 itself, allowing capability-by-capability update. 113 2.3. BGP Configuration 115 Finally, the definition and adoption of Version 3 of the SNMP has 116 occurred since the adoption of the RFC 1657 MIB. As a result, the 117 ability to deploy secure configuration of managed elements via SNMP 118 in a standardized way has become a reality for managed networks. In 119 this MIB definition effort, we seek to expose a more thorough capac- 120 ity for configuration of BGP4 and its capabilities than was present 121 in RFC 1657 or than was common practice at the time of its adoption. 123 3. MIB Organization 125 The MIB is broken down into several top level sections. This sec- 126 tionalization is important to create an organization for extensibil- 127 ity. 129 In general, a top level section of the MIB module will identify some 130 number of "core" scalar and tabular objects rooted off of it. If 131 there is sufficient depth within a subsection of one of these top- 132 level sections, the "core" subdivision off of the top level section 133 may provide multiple levels to the OBJECT IDENTIFIER scope necessary 134 to define its management data. 136 Once this core section is defined, however, each top-level section 137 has an explicit provision for an 'extensions' section OBJECT IDENTI- 138 FIER. The intent of the extensions section is to be containment for 139 discrete per-extension sections. By 'extension' here, we refer to 140 protocol mechanisms, capabilities, and exchanges which are not 141 defined in the base Border Gateway Protocol definition, or is not 142 configuration for protocol operations of similarly 'core' status. 143 Currently, we propose keying the identification within the per-exten- 144 sion section in one of two ways. 146 Where the extension is keyed to a defined capability which has an 147 associated BGP capability number assigned by IANA (for example, mul- 148 tiprotocol BGP extensions), the per extension section will be that 149 defined IANA capability number. Where the extension has management 150 information suitable for a MIB extension but does not correspond to 151 an exchanged protocol capability (for example, BGP Route Reflection), 152 the extension section shall have its final OBJECT IDENTIFIER fragment 153 correspond to the RFC number which first uniquely defined the exten- 154 sion (i.e., not requiring renumbering at the time a defining RFC for 155 a protocol mechanism is outdated by a later RFC). 157 3.1. bgpM2BaseScalars 159 The bgpM2BaseScalars section (and corresponding OBJECT IDENTIFIER) is 160 used to delineate object types used for basic management and monitor- 161 ing of the protocol implementation. These are core parameters for 162 the local configuration. While notifications are designed to be 163 extensible into any other section in the MIB module, the currently 164 defined traps are located here, in a subsection 'bgpM2BaseNotifica- 165 tions'. This is rooted at index level zero (0) here, owing to con- 166 ventions established in [RFC2576]. 168 Support for multiple concurrently supported versions of BGP is 169 exposed through the entries of the bgpM2VersionTable. Similarly, 170 support for multiple capabilities and authentication mechanisms, as 171 identified by their assigned numbers, are reported in the bgpM2Sup- 172 portedCapabilitiesTable and bgpM2SupportedAuthTable respectively. 174 In the MIB document, there are currently scalar extension mechanisms 175 to allow the agent to report membership of a local BGP Confederation 176 [RFC3065] or Route Reflection Cluster ID [RFC2796], as well as 177 whether these capabilities are in fact supported by the implementa- 178 tion. These are consistent with the non-capability based extension 179 section indexing guidelines as presented above. 181 bgpM2BaseScalars also is the root for a subsection, bgpM2BaseScalar- 182 Configuration, which contains the companion configuration objects for 183 the base scalar objects delineated in the preceding paragraphs. 184 These are presented as a series of scalar read-write objects, with a 185 single OBJECT-TYPE of syntax StorageType to designate the persistence 186 of the instance value data for these configuration scalars. 188 3.2. bgpM2PeerData 190 The bgpM2PeerData section is per-peer object type definitions. The 191 predominant table of read-only STATUS object types in that section 192 (bgpM2PeerTable) describes the session, negotiation state, and 193 authentication state on a per peer basis. A second table (bgpM2Pre- 194 fixCountersTable) exposes information about individual route prefixes 195 received over each peer session. A separate subsection and its sub- 196 ordinate table (bgpM2PeerErrorsTable) reports information about the 197 last error encountered on a given peering session. 199 Further subsections report authentication state with the peer, peer- 200 ing session detected errors, and elapsed time it has taken to 201 advance the peering session into various states defined in the proto- 202 col FSM. 204 The bgpM2PeerConfiguredTimersTable reports and allows dynamic reset 205 of key timers on the peer session. These currently allow reset of 206 hold time and keepalive timer, for compatibility with the same capa- 207 bilities in RFC 1657 [RFC1657]. For these resettable timers, their 208 end-to-end negotiated current values are reflected in the 209 bgpM2PeerNegotiatedTimersTable. 211 As currently defined, these tables describing authentication, error 212 state, and timer values (in addition to the configuration tables for 213 session timers) are tightly coupled enough to the logical per-row 214 view exposed in the bgpM2PeerTable row entries on a session that 215 these subordinate "tables" are defined as AUGMENTing the 216 bgpM2PeerTable itself. The other primary design criterion behind 217 this decision is that using this AUGMENTation does not increase the 218 per-row-data requirements of bgpM2PeerTable instance retrieval so as 219 to make such per-row retrieval unwieldy for the management applica- 220 tion. 222 3.2.1. bgpM2PeerCapabilities 224 bgpM2PeerCapabilitiesData has objects and tables to describe BGP 225 capabilities locally supported, and those reported and negotiated 226 over each peer session. For tables supporting each of these capa- 227 bility sets, capability code and data value are provided. Attention 228 must be given to the fact that multiple instances of a given 229 capability can be transmitted between BGP speakers. 231 3.2.2. bgpM2PeerCounters 233 The bgpM2CountersTable and bgpM2PrefixCountersTable report protocol 234 exchanges/FSM transitions, and discrete number of NLRIs exchanged per 235 peering session, respectively. This is independent of actual 236 exchanged path attributes, which are tabularized later in the MIB 237 module. Note that session transitions as reflected in changes of 238 instances within this table may also be reflected in issuance of 239 bgpM2Established and bgpM2BackwardTransition NOTIFICATION-TYPE PDUs. 241 3.2.3. Peering Data Extensions 243 Route reflector status on a per-peer basis (whether the peer is a 244 client or nonClient of the local BGP router's reflected route propa- 245 gation), and peer confederation membership is reported in non capa- 246 bility extensions of the peering data section. 248 3.2.4. Configuring Peering Sessions 250 The MIB has several tables indexed on a per-peer level of granularity 251 to control creation and activation of new peering sessions, and to 252 allow control on running sessions (those reflected in bgpM2PeerTable 253 row instances) regardless of what caused their creation in the BGP 254 routing process. 256 The bgpM2CfgPeerAdminStatusTable allows creation and specification of 257 a row by a bgpM2PeerIndex value (which is how its associated row 258 instance is identified in the bgpM2PeerTable). For each such row 259 instance, the set of the bgpM2CfgPeerAdminStatus OBJECT-TYPE of MAX- 260 ACCESS read-write can allow management application start and stop of 261 the session. 263 This is contrasted with the function of the bgpM2CfgPeerTable, and 264 its related AUGMENTed tables bgpM2CfgPeerTimersTable and bgpM2Cfg- 265 PeerAuthTable. These are used to facilitate direct creation of peer- 266 ing sessions by the management application. The function of columnar 267 OBJECT-TYPEs within the bgpM2CfgPeerTable for local and remote 268 address, version negotiation, and various row-administrative 269 attributes (RowStatus and StorageType SYNTAXes) are straightforward 270 enough. The only subtlety with respect to how peering sessions are 271 activated from usage of this table, and how the activated sessions 272 are reflected through their bgpM2PeerTable and bgpM2CfgPeerAdminSta- 273 tusTable entries, is in the usage of the bgpM2CfgPeerTable columnar 274 object bgpM2CfgPeerStatus. bgpM2CfgPeerStatus can take on two 275 values. When a peering session, as reflected through its row 276 instance in the bgpM2CfgPeerTable, has the bgpM2CfgPeerStatus 277 instance value in that row set to running(2) at the time of the SYN- 278 TAX RowStatus object instance of bgpM2CfgPeerRowEntryStatus set to 279 active(1), the peering session will in fact be activated in the BGP 280 routing process (in addition to having its row instance created in 281 the bgpM2CfgPeerTable and bgpM2CfgPeerAdminStatusTable). In this 282 case, the associated row of the bgpM2CfgPeerAdminStatusTable row 283 bgpM2CfgPeerAdminStatus instance would have the value of start(2). 284 If, in the prior example, the bgpM2CfgPeerStatus is halted(1) at the 285 time of the bgpM2CfgPeerRowEntryStatus instance set to active(1), 286 only the peering table entries would be created at this time of acti- 287 vation, without the peering session being automatically started. The 288 bgpM2CfgPeerAdminStatusTable row bgpM2CfgPeerAdminStatus instance 289 associated with the session would in this case reflect a value of 290 stop(1). 292 Since the row entries of the per-peer configuration tables which AUG- 293 MENT the bgpM2CfgPeerTable logically fate-share the row instances in 294 the bgpM2CfgPeerTable which they are AUGMENTing, they also share the 295 same StorageType and RowStatus SYNTAX object sense of the bgpM2Cfg- 296 PeerTable rows which they augment. 298 3.3. BGP Routing Information Base Data 300 An important table for providing index information for other tables 301 in the MIB module is the bgpM2NlriTable. This discriminates on a 302 given network prefix (by AFI/SAFI), and the peer which advertised the 303 prefix (since it can be heard of from multiple speakers). The 304 bgpM2PathAttrIndex column which identifies each row in this table is 305 used as an index for other per-attribute tables through the remainder 306 of the MIB module. 308 RFC 3107 [RFC3107] specifies a capability for exchanged routes 309 between BGP peers to attach attribute information to a route indicat- 310 ing, specifically, related MPLS label path information. The MIB sup- 311 ports the presentation of this attribute information by generalizing 312 how these attributes are presented to accommodate further extensions 313 of this particular type. Within a given bgpM2NlriTable entry, we 314 speak of attribute data of this type as being 'opaque' to BGP, and 315 use the columnar OBJECT-TYPEs bgpM2NlriOpaqueType and bgpM2Nlri- 316 OpaquePointer to refer to it. In the case of the RFC 3107 MPLS label 317 encoding (which is the only usage of these columnar fields in the 318 bgpM2NlriTable right now), a MPLS label stack would be referenced by 319 bgpM2NlriOpaquePointer by its per-NLRI instance pointing to a row 320 instance in the MPLS LSR MIB mplsLabelStackTable, and the bgpM2Nlri- 321 OpaqueType instance having a value of bgpMplsLabelStack(1). 323 The bgpM2AdjRibsOutTable row entries reflect data on routes which 324 have been placed, per peering session, in the Adj-Rib-Out for adver- 325 tisement to the associated peer. 327 The bgpM2PathAttrTable provides discrete BGP NLRI attributes which 328 were received with the advertisement of the prefix by its advertising 329 peer. Specific information about the autonomous system path (AS 330 Path) advertised with the NLRI, on a per AS value, is to be found in 331 the bgpM2AsPathTable. 333 Finally, where attributes which were unable to be reported in the 334 bgpM2PathAttrTable, the AS Path table, or any defined per-NLRI tables 335 in the agent were received with the prefix, those attributes are 336 reported via the bgpM2PathAttrUnknownTable. Short of advertised 337 attribute type, no semantic breakdown of the unknown attribute data 338 is provided. That data is only available as a raw OCTET STRING in 339 the bgpM2PathAttrUnknownValue column of this table. 341 3.3.1. Routing Information Base Extensions 343 There are two extension sections and five subordinate tables to the 344 bgpM2PathAttrTable and RIB data OBJECT IDENTIFIER-delimited MIB mod- 345 ule section. The bgpM2PathAttrRouteReflectionExts and its contained 346 bgpM2PathAttrOriginatorIdTable report on the originating route 347 reflector. The bgpM2PathAttrClusterTable specifically reports on the 348 reflection route a NLRI has traversed to get to the local BGP routing 349 process. 351 The bgpM2PathAttrCommunityExts section deals with extended and non- 352 extended communities for network routes. The bgpM2PathAttrCommTable 353 bgpM2PathAttrExtCommTable contained herein report community member- 354 ship (if any) on a per network-prefix basis. 356 3.4. Consideration On Table Indexing 358 There are certain efficiency concerns for row index management for 359 management applications which are useful to take into consideration, 360 given the nature of some of the tables implied in the preceding sec- 361 tion. 363 In the first place, it is valuable to exploit the direct relationship 364 of entries in, for example, the bgpM2PrefixCountersTable as they 365 relate to the entry in the bgpM2PeerTable to which they are related. 366 More compelling is the example case of the one-to-many relationship 367 between a row entry in the bgpM2PeerTable and the bgpM2PathAttrTable, 368 the latter of which maintains per-row entries for potentially many 369 NLRIs as received from a peer in a BGP UPDATE message. From the 370 point of view of normalizing these relationships, it would be useful 371 to have a direct reference to the "governing" bgpM2PeerTable row 372 entry for the peer which is a "dependency" for the subordinate table 373 row entry for other peer data. 375 Second, the nature of protocol-independent addressing makes the 376 indexing of these entries indirectly even more compelling. Even 377 accounting for the addressing requirements of IPv6 and the provision 378 of AFI and SAFI qualifiers, the logical addressing of a row in the 379 bgpPathAttrClusterTable (for example) would extend out some 50 bytes 380 if there was no direct index linkage to the "governing" bgpPathAt- 381 trTable, and bgpPeerTable entries. 383 For this reason, the tables are structured in such a way that, where 384 there is such a linkage to a "dependent" table (where, for example, 385 the bgpPrefixCountersTable "depends on" the bgpPeerTable), a table 386 will contain a per-row numeric index (e.g., bgpPeerIndex), which the 387 "dependent" table will use as one of its own row index values. These 388 indices are manufactured by the agent, and are otherwise opaque to 389 the management application (or, for that matter, even to the organi- 390 zation of the "dependent" table[s]). 392 Where considerations of per-row retrieval overhead (in terms of typi- 393 cal row instance data size, as a function of liability to have a sin- 394 gle row retrieval exceed PDU size, for example), and those of general 395 logical data organization permit, certain tables logically at the 396 sub-peering-session level have been specified as AUGMENTing the pri- 397 mary tables (bgpM2PeerTable and bgpM2CfgPeerTable) to which those 398 sub-peering-session row entries relate. This is to facilitate ease 399 on the part of a management application of assembling (for example, 400 via GET-BULK operations across a lexicographically contiguous row 401 scope) a management image of control information on a given peering 402 session. 404 4. Definitions 406 BGP4-V2-MIB DEFINITIONS ::= BEGIN 408 IMPORTS 409 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 410 Counter32, Gauge32, mib-2, Unsigned32, Integer32, 411 TimeTicks 412 FROM SNMPv2-SMI 413 InetAddressType, InetAddress, InetPortNumber, 414 InetAutonomousSystemNumber, InetAddressPrefixLength 415 FROM INET-ADDRESS-MIB 416 TEXTUAL-CONVENTION, TruthValue, RowPointer, StorageType, 417 RowStatus 418 FROM SNMPv2-TC 419 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 420 FROM SNMPv2-CONF 421 SnmpAdminString 422 FROM SNMP-FRAMEWORK-MIB; 424 bgpM2 MODULE-IDENTITY 425 LAST-UPDATED "200401120000Z" 426 ORGANIZATION "IETF IDR Working Group" 427 CONTACT-INFO "E-mail: idr@merit.net 429 Jeffrey Haas (Editor) 430 825 Victors Way, Suite 100 431 Ann Arbor, MI 48108 432 Tel: +1 734 222-1600 433 Fax: +1 734 222-1602 434 E-mail: jhaas@nexthop.com" 436 DESCRIPTION 437 "This MIB module defines management objects for 438 the Border Gateway Protocol, Version 4." 439 ::= { mib-2 XXX } 440 -- RFC Ed.: replace XXX with IANA-assigned number & remove this note 442 BgpM2Identifier ::= TEXTUAL-CONVENTION 443 DISPLAY-HINT "1d." 444 STATUS current 445 DESCRIPTION 446 "The representation of a BGP Identifier. The BGP 447 Identifier should be represented in the OCTET STRING 448 as with the first OCTET of the string containing 449 the first OCTET of the BGP Identifier received or sent 450 in the OPEN packet and so on. 452 Even though the BGP Identifier is trending away from 453 an IP address it is still displayed as if it was one, 454 even when it would be an illegal IP address." 455 SYNTAX OCTET STRING(SIZE (4)) 457 BgpM2Afi ::= TEXTUAL-CONVENTION 458 DISPLAY-HINT "d" 459 STATUS current 460 DESCRIPTION 461 "The representation of a BGP AFI" 462 SYNTAX Unsigned32(0..65535) 463 BgpM2Safi ::= TEXTUAL-CONVENTION 464 DISPLAY-HINT "d" 465 STATUS current 466 DESCRIPTION 467 "The representation of a BGP SAFI" 468 SYNTAX Unsigned32(0..255) 470 BgpM2Community ::= TEXTUAL-CONVENTION 471 DISPLAY-HINT "2d:" 472 STATUS current 473 DESCRIPTION 474 "The representation of a BGP Community." 475 SYNTAX OCTET STRING(SIZE(4)) 477 BgpM2ExtendedCommunity ::= TEXTUAL-CONVENTION 478 DISPLAY-HINT "1x:" 479 STATUS current 480 DESCRIPTION 481 "The representation of a BGP Extended Community." 482 SYNTAX OCTET STRING(SIZE(8)) 484 bgpM2BaseScalars 485 OBJECT IDENTIFIER ::= { bgpM2 1 } 487 -- 488 -- Notifications 489 -- 491 bgpM2BaseNotifications 492 OBJECT IDENTIFIER ::= { bgpM2BaseScalars 0 } 494 bgpM2Established NOTIFICATION-TYPE 495 OBJECTS { 496 bgpM2PeerLocalAddrType, 497 bgpM2PeerLocalAddr, 498 bgpM2PeerRemoteAddrType, 499 bgpM2PeerRemoteAddr, 500 bgpM2PeerLastErrorReceived, 501 bgpM2PeerState 502 } 503 STATUS current 504 DESCRIPTION 505 "The BGP Established event is generated when 506 the BGP FSM enters the ESTABLISHED state." 507 ::= { bgpM2BaseNotifications 1 } 509 bgpM2BackwardTransition NOTIFICATION-TYPE 510 OBJECTS { 511 bgpM2PeerLocalAddrType, 512 bgpM2PeerLocalAddr, 513 bgpM2PeerRemoteAddrType, 514 bgpM2PeerRemoteAddr, 515 bgpM2PeerLastErrorReceived, 516 bgpM2PeerLastErrorReceivedText, 517 bgpM2PeerState 518 } 519 STATUS current 520 DESCRIPTION 521 "The BGPBackwardTransition Event is generated 522 when the BGP FSM moves from a higher numbered 523 state to a lower numbered state." 524 ::= { bgpM2BaseNotifications 2 } 526 -- 527 -- BGP Supported Version Table 528 -- 530 bgpM2Version 531 OBJECT IDENTIFIER ::= { bgpM2BaseScalars 1 } 533 bgpM2VersionTable OBJECT-TYPE 534 SYNTAX SEQUENCE OF BgpM2VersionEntry 535 MAX-ACCESS not-accessible 536 STATUS current 537 DESCRIPTION 538 "Table of supported BGP versions." 539 ::= { bgpM2Version 1 } 541 bgpM2VersionEntry OBJECT-TYPE 542 SYNTAX BgpM2VersionEntry 543 MAX-ACCESS not-accessible 544 STATUS current 545 DESCRIPTION 546 "Entry containing data on a given supported version 547 of the Border Gateway Protocol and the level of 548 support provided. It is expected that any agent 549 implementation supporting this MIB module will 550 report support for Version 4 of the Border Gateway 551 Protocol at the very minimum." 552 INDEX { 553 bgpM2VersionIndex 554 } 555 ::= { bgpM2VersionTable 1 } 557 BgpM2VersionEntry ::= SEQUENCE { 558 bgpM2VersionIndex 559 Unsigned32, 560 bgpM2VersionSupported 561 TruthValue 562 } 564 bgpM2VersionIndex OBJECT-TYPE 565 SYNTAX Unsigned32(0..255) 566 MAX-ACCESS read-only 567 STATUS current 568 DESCRIPTION 569 "The version number of the BGP Protocol." 570 ::= { bgpM2VersionEntry 1 } 572 bgpM2VersionSupported OBJECT-TYPE 573 SYNTAX TruthValue 574 MAX-ACCESS read-only 575 STATUS current 576 DESCRIPTION 577 "This value is TRUE if this version of the BGP protocol 578 identified in 'bgpM2VersionIndex' is supported. The absence 579 of a row for a particular bgpM2VersionIndex indicates that 580 that bgpM2VersionIndex protocol version number is not 581 supported." 582 ::= { bgpM2VersionEntry 2 } 584 -- 585 -- Supported BGP Capabilities 586 -- 588 bgpM2SupportedCapabilities 589 OBJECT IDENTIFIER ::= { bgpM2BaseScalars 2 } 591 bgpM2CapabilitySupportAvailable OBJECT-TYPE 592 SYNTAX TruthValue 593 MAX-ACCESS read-only 594 STATUS current 595 DESCRIPTION 596 "This value is TRUE if capability support is 597 available and is enabled." 598 ::= { bgpM2SupportedCapabilities 1 } 600 bgpM2SupportedCapabilitiesTable OBJECT-TYPE 601 SYNTAX SEQUENCE OF BgpM2SupportedCapabilityEntry 602 MAX-ACCESS not-accessible 603 STATUS current 604 DESCRIPTION 605 "Table of supported BGP-4 capabilities." 606 ::= { bgpM2SupportedCapabilities 2 } 608 bgpM2SupportedCapabilitiesEntry OBJECT-TYPE 609 SYNTAX BgpM2SupportedCapabilityEntry 610 MAX-ACCESS not-accessible 611 STATUS current 612 DESCRIPTION 613 "Information about supported capabilities indexed 614 by capability number." 615 INDEX { 616 bgpM2SupportedCapabilityCode 617 } 618 ::= { bgpM2SupportedCapabilitiesTable 1 } 620 BgpM2SupportedCapabilityEntry ::= SEQUENCE { 621 bgpM2SupportedCapabilityCode 622 Unsigned32, 623 bgpM2SupportedCapability 624 TruthValue 625 } 627 bgpM2SupportedCapabilityCode OBJECT-TYPE 628 SYNTAX Unsigned32 (0..255) 629 MAX-ACCESS read-only 630 STATUS current 631 DESCRIPTION 632 "Index of supported capability. The index directly 633 corresponds with the BGP-4 Capability Advertisement 634 Capability Code." 635 ::= { bgpM2SupportedCapabilitiesEntry 1 } 636 bgpM2SupportedCapability OBJECT-TYPE 637 SYNTAX TruthValue 638 MAX-ACCESS read-only 639 STATUS current 640 DESCRIPTION 641 "This value is True if this capability is supported, 642 False otherwise." 643 ::= { bgpM2SupportedCapabilitiesEntry 2 } 645 -- 646 -- Base Scalars 647 -- 649 bgpM2AsSize OBJECT-TYPE 650 SYNTAX INTEGER { 651 twoOctet(1), 652 fourOctet(2) 653 } 654 MAX-ACCESS read-only 655 STATUS current 656 DESCRIPTION 657 "The size of the AS value in this implementation. 659 The semantics of this are determined as per the 660 as-4bytes draft." 661 REFERENCE 662 "draft-ietf-idr-as4bytes-04" 663 ::= { bgpM2BaseScalars 4 } 665 bgpM2LocalAs OBJECT-TYPE 666 SYNTAX InetAutonomousSystemNumber 667 MAX-ACCESS read-only 668 STATUS current 669 DESCRIPTION 670 "The local autonomous system number. 672 If the bgpM2AsSize is twoOctet, then the range is 673 constrained to be 0-65535." 674 ::= { bgpM2BaseScalars 5 } 676 bgpM2LocalIdentifier OBJECT-TYPE 677 SYNTAX BgpM2Identifier 678 MAX-ACCESS read-only 679 STATUS current 680 DESCRIPTION 681 "The BGP Identifier of local system. 683 Current practice is trending away from this value being 684 treated as an IP address and more as a generic 685 identifier." 686 ::= { bgpM2BaseScalars 6 } 688 -- 689 -- Base Scalar Extensions 690 -- 692 bgpM2BaseScalarExtensions 693 OBJECT IDENTIFIER ::= { bgpM2BaseScalars 7 } 695 bgpM2BaseScalarNonCapExts 696 OBJECT IDENTIFIER ::= { bgpM2BaseScalarExtensions 1 } 698 bgpM2BaseScalarCapExts 699 OBJECT IDENTIFIER ::= { bgpM2BaseScalarExtensions 2 } 701 -- 702 -- Base Scalar Route Reflection Extensions 703 -- 705 bgpM2BaseScalarRouteReflectExts OBJECT IDENTIFIER ::= 706 { bgpM2BaseScalarNonCapExts 2796 } 708 bgpM2RouteReflector OBJECT-TYPE 709 SYNTAX TruthValue 710 MAX-ACCESS read-only 711 STATUS current 712 DESCRIPTION 713 "This value is TRUE if this implementation supports the 714 BGP Route Reflection Extension and is enabled as a 715 route reflector. If the BGP Route Reflection extension 716 is not supported this value must be FALSE." 717 REFERENCE 718 "RFC 2796 - BGP Route Reflection" 719 ::= { bgpM2BaseScalarRouteReflectExts 1 } 721 bgpM2ClusterId OBJECT-TYPE 723 SYNTAX BgpM2Identifier 724 MAX-ACCESS read-only 725 STATUS current 726 DESCRIPTION 727 "The configured Cluster-ID of the BGP Speaker. This will 728 default to the BGP Speaker's BgpM2Identifier if this 729 speaker is functioning as a route reflector and an 730 explicit Cluster-ID has not been configured. 732 A value of 0.0.0.0 will be present if Route Reflection is 733 not enabled." 734 REFERENCE 735 "RFC 2796 - BGP Route Reflection" 736 ::= { bgpM2BaseScalarRouteReflectExts 2 } 738 -- 739 -- Base Scalar AS Confederation Extensions 740 -- 742 bgpM2BaseScalarASConfedExts OBJECT IDENTIFIER ::= 743 { bgpM2BaseScalarNonCapExts 3065 } 745 bgpM2ConfederationRouter OBJECT-TYPE 746 SYNTAX TruthValue 747 MAX-ACCESS read-only 748 STATUS current 749 DESCRIPTION 750 "This value is TRUE if this implementation supports the 751 BGP AS Confederations Extension and this router is 752 configured to be in a confederation." 753 REFERENCE 754 "RFC 3065 - Autonomous System Confederations for BGP" 755 ::= { bgpM2BaseScalarASConfedExts 1 } 757 bgpM2ConfederationId OBJECT-TYPE 758 SYNTAX InetAutonomousSystemNumber 759 MAX-ACCESS read-only 760 STATUS current 761 DESCRIPTION 762 "The local Confederation Identification Number. 764 This value will be zero (0) if this BGP Speaker is not 765 a confederation router." 766 REFERENCE 767 "RFC 3065 - Autonomous System Confederations for BGP" 768 ::= { bgpM2BaseScalarASConfedExts 2 } 770 -- 771 -- Base Configuration Objects 772 -- 774 bgpM2BaseScalarConfiguration 775 OBJECT IDENTIFIER ::= { bgpM2BaseScalars 8 } 777 bgpM2CfgBaseScalarStorageType OBJECT-TYPE 778 SYNTAX StorageType 779 MAX-ACCESS read-write 780 STATUS current 781 DESCRIPTION 782 "This object specifies the intended storage type for 783 all configurable base scalars." 784 ::= { bgpM2BaseScalarConfiguration 1 } 786 bgpM2CfgLocalAs OBJECT-TYPE 787 SYNTAX InetAutonomousSystemNumber 788 MAX-ACCESS read-write 789 STATUS current 790 DESCRIPTION 791 "The local autonomous system number. 793 If the bgpM2AsSize is twoOctet, then the range is 794 constrained to be 0-65535." 795 ::= { bgpM2BaseScalarConfiguration 2 } 797 bgpM2CfgLocalIdentifier OBJECT-TYPE 798 SYNTAX BgpM2Identifier 799 MAX-ACCESS read-write 800 STATUS current 801 DESCRIPTION 802 "The BGP Identifier of local system. 804 Current practice is trending away from this value being 805 treated as an IP address and more as a generic 806 identifier." 807 ::= { bgpM2BaseScalarConfiguration 3 } 809 -- 810 -- Base Scalar Extensions 811 -- 813 bgpM2CfgBaseScalarExtensions 814 OBJECT IDENTIFIER ::= { bgpM2BaseScalarConfiguration 4 } 816 bgpM2CfgBaseScalarNonCapExts 817 OBJECT IDENTIFIER ::= { bgpM2CfgBaseScalarExtensions 1 } 819 bgpM2CfgBaseScalarCapExts 820 OBJECT IDENTIFIER ::= { bgpM2CfgBaseScalarExtensions 2 } 822 -- 823 -- Base Scalar Route Reflection Extensions 824 -- 826 bgpM2CfgBaseScalarReflectorExts 827 OBJECT IDENTIFIER ::= { bgpM2CfgBaseScalarNonCapExts 2796 } 829 bgpM2CfgRouteReflector OBJECT-TYPE 830 SYNTAX TruthValue 831 MAX-ACCESS read-write 832 STATUS current 833 DESCRIPTION 834 "This value is set to true if this implementation will 835 be supporting route reflection." 836 REFERENCE 837 "RFC 2796 - BGP Route Reflection" 838 ::= { bgpM2CfgBaseScalarReflectorExts 1 } 840 bgpM2CfgClusterId OBJECT-TYPE 841 SYNTAX BgpM2Identifier 842 MAX-ACCESS read-write 843 STATUS current 844 DESCRIPTION 845 "The configured Cluster-ID of the BGP Speaker. This will 846 default to the BGP Speaker's BgpM2Identifier if this 847 speaker is functioning as a route reflector and an 848 explicit Cluster-ID has not been configured. 850 A value of 0.0.0.0 will be present if Route Reflection is 851 not enabled." 852 REFERENCE 853 "RFC 2796 - BGP Route Reflection" 854 ::= { bgpM2CfgBaseScalarReflectorExts 2 } 856 -- 857 -- Base Scalar AS Confederation Extensions 858 -- 860 bgpM2CfgBaseScalarASConfedExts 861 OBJECT IDENTIFIER ::= { bgpM2CfgBaseScalarNonCapExts 3065 } 863 bgpM2CfgConfederationRouter OBJECT-TYPE 864 SYNTAX TruthValue 865 MAX-ACCESS read-write 866 STATUS current 867 DESCRIPTION 868 "This value is set to true if this implementation will be 869 supporting BGP AS Confederations." 870 REFERENCE 871 "RFC 3065 - Autonomous System Confederations for BGP" 872 ::= { bgpM2CfgBaseScalarASConfedExts 1 } 874 bgpM2CfgConfederationId OBJECT-TYPE 875 SYNTAX InetAutonomousSystemNumber 876 MAX-ACCESS read-write 877 STATUS current 878 DESCRIPTION 879 "The local Confederation Identification Number. 881 This value will be zero (0) if this BGP Speaker is not 882 a confederation router." 883 REFERENCE 884 "RFC 3065 - Autonomous System Confederations for BGP" 885 ::= { bgpM2CfgBaseScalarASConfedExts 2 } 887 -- 888 -- BGP Peer Data 889 -- 891 bgpM2Peer 892 OBJECT IDENTIFIER ::= { bgpM2 2 } 894 bgpM2PeerData 895 OBJECT IDENTIFIER ::= { bgpM2Peer 1 } 896 bgpM2PeerTable OBJECT-TYPE 897 SYNTAX SEQUENCE OF BgpM2PeerEntry 898 MAX-ACCESS not-accessible 899 STATUS current 900 DESCRIPTION 901 "BGP peer table. 903 This table contains, one entry per remote BGP peer, 904 any information about the connections with the remote 905 BGP peers." 906 ::= { bgpM2PeerData 1 } 908 bgpM2PeerEntry OBJECT-TYPE 909 SYNTAX BgpM2PeerEntry 910 MAX-ACCESS not-accessible 911 STATUS current 912 DESCRIPTION 913 "Entry containing information about the connection with 914 a remote BGP peer." 915 INDEX { 916 bgpM2PeerInstance, 917 bgpM2PeerLocalAddrType, 918 bgpM2PeerLocalAddr, 919 bgpM2PeerRemoteAddrType, 920 bgpM2PeerRemoteAddr 921 } 922 ::= { bgpM2PeerTable 1 } 924 BgpM2PeerEntry ::= SEQUENCE { 925 bgpM2PeerInstance 926 Unsigned32, 927 bgpM2PeerIdentifier 928 BgpM2Identifier, 929 bgpM2PeerState 930 INTEGER, 931 bgpM2PeerStatus 932 INTEGER, 933 bgpM2PeerConfiguredVersion 934 Unsigned32, 935 bgpM2PeerNegotiatedVersion 936 Unsigned32, 937 bgpM2PeerLocalAddrType 938 InetAddressType, 939 bgpM2PeerLocalAddr 940 InetAddress, 941 bgpM2PeerLocalPort 942 InetPortNumber, 943 bgpM2PeerLocalAs 944 InetAutonomousSystemNumber, 945 bgpM2PeerRemoteAddrType 946 InetAddressType, 947 bgpM2PeerRemoteAddr 948 InetAddress, 949 bgpM2PeerRemotePort 950 InetPortNumber, 951 bgpM2PeerRemoteAs 952 InetAutonomousSystemNumber, 953 bgpM2PeerIndex 954 Unsigned32 955 } 957 bgpM2PeerInstance OBJECT-TYPE 958 SYNTAX Unsigned32 959 MAX-ACCESS read-only 960 STATUS current 961 DESCRIPTION 962 "The routing instance index. 964 Some BGP implementations permit the creation of 965 multiple instances of a BGP routing process. An 966 example includes RFC 2547 PE-CE routers. 968 Implementations that do not support multiple 969 routing instances should return 1 for this object. 971 XXX TODO - We need to provide a way to configure these 972 in the peer configuration table." 973 ::= { bgpM2PeerEntry 1 } 975 bgpM2PeerIdentifier OBJECT-TYPE 976 SYNTAX BgpM2Identifier 977 MAX-ACCESS read-only 978 STATUS current 979 DESCRIPTION 980 "The BGP Identifier of this entry's remote BGP peer. 982 This entry should be 0.0.0.0 unless the bgpM2PeerState is 983 in the OpenConfirm or the Established state." 984 REFERENCE 985 "draft-ietf-idr-bgp4-17.txt, Sec. 4.2" 986 ::= { bgpM2PeerEntry 2 } 987 bgpM2PeerState OBJECT-TYPE 988 SYNTAX INTEGER { 989 idle(1), 990 connect(2), 991 active(3), 992 opensent(4), 993 openconfirm(5), 994 established(6) 995 } 996 MAX-ACCESS read-only 997 STATUS current 998 DESCRIPTION 999 "The remote BGP peer's FSM state." 1000 REFERENCE 1001 "draft-ietf-idr-bgp4-17.txt, Sec. 8" 1002 ::= { bgpM2PeerEntry 3 } 1004 bgpM2PeerStatus OBJECT-TYPE 1005 SYNTAX INTEGER { 1006 halted(1), 1007 running(2) 1008 } 1009 MAX-ACCESS read-only 1010 STATUS current 1011 DESCRIPTION 1012 "Whether or not the BGP FSM for this remote peer is halted 1013 or running. The BGP FSM for a remote peer is halted after 1014 processing a Stop event. Likewise, it is in the running 1015 state after a Start event. 1017 The bgpM2PeerState will generally be in the idle state when 1018 the FSM is halted, although some extensions such as 1019 Graceful Restart will leave the peer in the Idle state 1020 but with the FSM running." 1021 ::= { bgpM2PeerEntry 4 } 1023 bgpM2PeerConfiguredVersion OBJECT-TYPE 1024 SYNTAX Unsigned32 (1..255) 1025 MAX-ACCESS read-only 1026 STATUS current 1027 DESCRIPTION 1028 "The configured version to originally start with this 1029 remote peer. The BGP speaker may permit negotiation to a 1030 lower version number of the protocol." 1031 ::= { bgpM2PeerEntry 5 } 1032 bgpM2PeerNegotiatedVersion OBJECT-TYPE 1033 SYNTAX Unsigned32 (1..255) 1034 MAX-ACCESS read-only 1035 STATUS current 1036 DESCRIPTION 1037 "The negotiated version of BGP running between the two 1038 peers." 1039 ::= { bgpM2PeerEntry 6 } 1041 bgpM2PeerLocalAddrType OBJECT-TYPE 1042 SYNTAX InetAddressType 1043 MAX-ACCESS read-only 1044 STATUS current 1045 DESCRIPTION 1046 "The address family of the local end of the peering 1047 session." 1048 ::= { bgpM2PeerEntry 7 } 1050 bgpM2PeerLocalAddr OBJECT-TYPE 1051 SYNTAX InetAddress (SIZE(4..20)) 1052 MAX-ACCESS read-only 1053 STATUS current 1054 DESCRIPTION 1055 "The address of the local end of the peering session." 1056 ::= { bgpM2PeerEntry 8 } 1058 bgpM2PeerLocalPort OBJECT-TYPE 1059 SYNTAX InetPortNumber 1060 MAX-ACCESS read-only 1061 STATUS current 1062 DESCRIPTION 1063 "The local port for the TCP connection between the BGP 1064 peers." 1065 ::= { bgpM2PeerEntry 9 } 1067 bgpM2PeerLocalAs OBJECT-TYPE 1068 SYNTAX InetAutonomousSystemNumber 1069 MAX-ACCESS read-only 1070 STATUS current 1071 DESCRIPTION 1072 "Some implementations of BGP can represent themselves 1073 as multiple ASs. This is the AS that this peering 1074 session is representing itself as to the remote peer." 1075 ::= { bgpM2PeerEntry 10 } 1076 bgpM2PeerRemoteAddrType OBJECT-TYPE 1077 SYNTAX InetAddressType 1078 MAX-ACCESS read-only 1079 STATUS current 1080 DESCRIPTION 1081 "The address family of the remote end of the peering 1082 session." 1083 ::= { bgpM2PeerEntry 11 } 1085 bgpM2PeerRemoteAddr OBJECT-TYPE 1086 SYNTAX InetAddress (SIZE(4..20)) 1087 MAX-ACCESS read-only 1088 STATUS current 1089 DESCRIPTION 1090 "The address of the remote end of the peering session." 1091 ::= { bgpM2PeerEntry 12 } 1093 bgpM2PeerRemotePort OBJECT-TYPE 1094 SYNTAX InetPortNumber 1095 MAX-ACCESS read-only 1096 STATUS current 1097 DESCRIPTION 1098 "The remote port for the TCP connection between the BGP 1099 peers. In the case of a transport for which the notion 1100 of 'port' is irrelevant, an instance value of -1 1101 should be returned by the agent for this object. 1103 Note that the objects bgpM2PeerLocalAddr, 1104 bgpM2PeerLocalPort, bgpM2PeerRemoteAddr and 1105 bgpM2PeerRemotePort provide the appropriate reference to 1106 the standard MIB TCP connection table. or even the ipv6 1107 TCP MIB as in rfc2452." 1108 REFERENCE 1109 "RFC 2012 - SNMPv2 Management Information Base for the 1110 Transmission Control Protocol using SMIv2. 1111 RFC 2542 - IP Version 6 Management Information Base 1112 for the Transmission Control Protocol." 1113 ::= { bgpM2PeerEntry 13 } 1115 bgpM2PeerRemoteAs OBJECT-TYPE 1116 SYNTAX InetAutonomousSystemNumber 1117 MAX-ACCESS read-only 1118 STATUS current 1119 DESCRIPTION 1120 "The remote autonomous system number." 1121 ::= { bgpM2PeerEntry 14 } 1123 bgpM2PeerIndex OBJECT-TYPE 1124 SYNTAX Unsigned32 1125 MAX-ACCESS read-only 1126 STATUS current 1127 DESCRIPTION 1128 "This value is a unique index for the remote peer entry 1129 in the bgpM2PeerTable. It is assigned by the agent 1130 at the point of creation of the bgpM2PeerTable row 1131 entry. While its value is guaranteed to be unique at 1132 any time, it is otherwise opaque to the management 1133 application with respect to its value or the contiguity 1134 of bgpM2PeerIndex row instance values across rows of 1135 the bgpM2PeerTable. It is used to provide an index 1136 structure for other tables whose data is logically 1137 per-peer. 1139 For explicitly configured peers, this value will remain 1140 consistent until this row is deleted by deleting the 1141 configured peers. Unconfigured peers will generate 1142 a monotonically increasing number when a BGP FSM is 1143 built to process the peering session. Values in the 1144 bgpM2PeerTable and other tables utilizing bgpM2PeerIndex 1145 are expected to remain in existence for an arbitrary 1146 time after the unconfigured peer has been deleted 1147 in order to allow management applications to extract 1148 useful management information for those peers. Thus, 1149 an unconfigured peer using the same indices as the 1150 bgpM2PeerTable that comes up while this row still 1151 exists will re-utilize the same row." 1152 ::= { bgpM2PeerEntry 15 } 1154 -- 1155 -- Errors 1156 -- 1158 bgpM2PeerErrors 1159 OBJECT IDENTIFIER ::= { bgpM2Peer 2 } 1161 bgpM2PeerErrorsTable OBJECT-TYPE 1162 SYNTAX SEQUENCE OF BgpM2PeerErrorsEntry 1163 MAX-ACCESS not-accessible 1164 STATUS current 1165 DESCRIPTION 1166 "On a per peer basis, this table reflects the last 1167 protocol-defined error encountered and reported on 1168 the peer session. If no entry for a given peer, 1169 by its bgpM2PeerIndex, exists in this table, then no 1170 such errors have been observed, reported, and 1171 recorded on the session." 1172 ::= { bgpM2PeerErrors 1 } 1174 bgpM2PeerErrorsEntry OBJECT-TYPE 1175 SYNTAX BgpM2PeerErrorsEntry 1176 MAX-ACCESS not-accessible 1177 STATUS current 1178 DESCRIPTION 1179 "Each entry contains information about errors sent 1180 and received for a particular BGP peer." 1181 AUGMENTS { 1182 bgpM2PeerEntry 1183 } 1184 ::= { bgpM2PeerErrorsTable 1 } 1186 BgpM2PeerErrorsEntry ::= SEQUENCE { 1187 bgpM2PeerLastErrorReceived 1188 OCTET STRING, 1189 bgpM2PeerLastErrorSent 1190 OCTET STRING, 1191 bgpM2PeerLastErrorReceivedTime 1192 TimeTicks, 1193 bgpM2PeerLastErrorSentTime 1194 TimeTicks, 1195 bgpM2PeerLastErrorReceivedText 1196 SnmpAdminString, 1197 bgpM2PeerLastErrorSentText 1198 SnmpAdminString, 1199 bgpM2PeerLastErrorReceivedData 1200 OCTET STRING, 1201 bgpM2PeerLastErrorSentData 1202 OCTET STRING 1203 } 1205 bgpM2PeerLastErrorReceived OBJECT-TYPE 1206 SYNTAX OCTET STRING (SIZE (2)) 1207 MAX-ACCESS read-only 1208 STATUS current 1209 DESCRIPTION 1210 "The last error code and subcode received by this BGP 1211 Speaker via a NOTIFICATION message for this peer. 1213 If no error has occurred, this field is zero. 1214 Otherwise, the first byte of this two byte 1215 OCTET STRING contains the error code, and the second 1216 byte contains the subcode." 1217 REFERENCE 1218 "draft-ietf-idr-bgp4-15.txt, Sec. 4.5" 1219 ::= { bgpM2PeerErrorsEntry 1 } 1221 bgpM2PeerLastErrorSent OBJECT-TYPE 1222 SYNTAX OCTET STRING (SIZE (2)) 1223 MAX-ACCESS read-only 1224 STATUS current 1225 DESCRIPTION 1226 "The last error code and subcode sent by this BGP 1227 Speaker via a NOTIFICATION message to this peer. 1228 If no error has occurred, this field is zero. 1229 Otherwise, the first byte of this two byte 1230 OCTET STRING contains the error code, and the second 1231 byte contains the subcode." 1232 REFERENCE 1233 "draft-ietf-idr-bgp4-15.txt, Sec. 4.5" 1234 ::= { bgpM2PeerErrorsEntry 2 } 1236 bgpM2PeerLastErrorReceivedTime OBJECT-TYPE 1237 SYNTAX TimeTicks 1238 MAX-ACCESS read-only 1239 STATUS current 1240 DESCRIPTION 1241 "The timestamp that the last NOTIFICATION was received from 1242 this peer." 1243 REFERENCE 1244 "draft-ietf-idr-bgp4-15.txt, Sec. 4.5" 1245 ::= { bgpM2PeerErrorsEntry 3 } 1247 bgpM2PeerLastErrorSentTime OBJECT-TYPE 1248 SYNTAX TimeTicks 1249 MAX-ACCESS read-only 1250 STATUS current 1251 DESCRIPTION 1252 "The timestamp that the last NOTIFICATION was sent to 1253 this peer." 1254 REFERENCE 1255 "draft-ietf-idr-bgp4-15.txt, Sec. 4.5" 1256 ::= { bgpM2PeerErrorsEntry 4 } 1257 bgpM2PeerLastErrorReceivedText OBJECT-TYPE 1258 SYNTAX SnmpAdminString 1259 MAX-ACCESS read-only 1260 STATUS current 1261 DESCRIPTION 1262 "This object contains an implementation specific 1263 explanation of the error that was reported." 1264 ::= { bgpM2PeerErrorsEntry 5 } 1266 bgpM2PeerLastErrorSentText OBJECT-TYPE 1267 SYNTAX SnmpAdminString 1268 MAX-ACCESS read-only 1269 STATUS current 1270 DESCRIPTION 1271 "This object contains an implementation specific 1272 explanation of the error that is being reported." 1273 ::= { bgpM2PeerErrorsEntry 6 } 1275 bgpM2PeerLastErrorReceivedData OBJECT-TYPE 1276 SYNTAX OCTET STRING (SIZE(0..4075)) 1277 MAX-ACCESS read-only 1278 STATUS current 1279 DESCRIPTION 1280 "The last error code's data seen by this peer." 1281 REFERENCE 1282 "draft-ietf-idr-bgp4-15.txt, Sec. 4.5" 1283 ::= { bgpM2PeerErrorsEntry 7 } 1285 bgpM2PeerLastErrorSentData OBJECT-TYPE 1286 SYNTAX OCTET STRING (SIZE(0..4075)) 1287 MAX-ACCESS read-only 1288 STATUS current 1289 DESCRIPTION 1290 "The last error code's data sent to this peer." 1291 REFERENCE 1292 "draft-ietf-idr-bgp4-15.txt, Sec. 4.5" 1293 ::= { bgpM2PeerErrorsEntry 8 } 1295 -- 1296 -- Peer Event Times 1297 -- 1299 bgpM2PeerTimers 1300 OBJECT IDENTIFIER ::= { bgpM2Peer 3 } 1301 bgpM2PeerEventTimesTable OBJECT-TYPE 1302 SYNTAX SEQUENCE OF BgpM2PeerEventTimesEntry 1303 MAX-ACCESS not-accessible 1304 STATUS current 1305 DESCRIPTION 1306 "A table reporting the per-peering session amount 1307 of time elapsed and update events since the peering 1308 session advanced into the Established state." 1309 ::= { bgpM2PeerTimers 1 } 1311 bgpM2PeerEventTimesEntry OBJECT-TYPE 1312 SYNTAX BgpM2PeerEventTimesEntry 1313 MAX-ACCESS not-accessible 1314 STATUS current 1315 DESCRIPTION 1316 "Each row contains a set of statistics about time 1317 spent and events encountered in the peer session 1318 Established state." 1319 AUGMENTS { 1320 bgpM2PeerEntry 1321 } 1322 ::= { bgpM2PeerEventTimesTable 1 } 1324 BgpM2PeerEventTimesEntry ::= SEQUENCE { 1325 bgpM2PeerFsmEstablishedTime 1326 Gauge32, 1327 bgpM2PeerInUpdatesElapsedTime 1328 Gauge32 1329 } 1331 bgpM2PeerFsmEstablishedTime OBJECT-TYPE 1332 SYNTAX Gauge32 1333 MAX-ACCESS read-only 1334 STATUS current 1335 DESCRIPTION 1336 "This timer indicates how long (in seconds) this 1337 peer has been in the Established state or how long 1338 since this peer was last in the Established state. 1339 It is set to zero when a new peer is configured or 1340 the router is booted." 1341 ::= { bgpM2PeerEventTimesEntry 1 } 1343 bgpM2PeerInUpdatesElapsedTime OBJECT-TYPE 1344 SYNTAX Gauge32 1345 MAX-ACCESS read-only 1346 STATUS current 1347 DESCRIPTION 1348 "Elapsed time in seconds since the last BGP UPDATE 1349 message was received from the peer. Each time 1350 bgpM2PeerInUpdates is incremented, the value of this 1351 object is set to zero (0). This value shall also be 1352 zero (0) when the peer is not in the Established state" 1353 ::= { bgpM2PeerEventTimesEntry 2 } 1355 -- 1356 -- Peer Configured Timers 1357 -- 1359 bgpM2PeerConfiguredTimersTable OBJECT-TYPE 1360 SYNTAX SEQUENCE OF BgpM2PeerConfiguredTimersEntry 1361 MAX-ACCESS not-accessible 1362 STATUS current 1363 DESCRIPTION 1364 "Per peer management data on BGP session timers." 1365 ::= { bgpM2PeerTimers 2 } 1367 bgpM2PeerConfiguredTimersEntry OBJECT-TYPE 1368 SYNTAX BgpM2PeerConfiguredTimersEntry 1369 MAX-ACCESS not-accessible 1370 STATUS current 1371 DESCRIPTION 1372 "Each entry corresponds to the current state of 1373 BGP timers on a given peering session." 1374 AUGMENTS { 1375 bgpM2PeerEntry 1376 } 1377 ::= { bgpM2PeerConfiguredTimersTable 1 } 1379 BgpM2PeerConfiguredTimersEntry ::= SEQUENCE { 1380 bgpM2PeerConnectRetryInterval 1381 Unsigned32, 1382 bgpM2PeerHoldTimeConfigured 1383 Unsigned32, 1384 bgpM2PeerKeepAliveConfigured 1385 Unsigned32, 1386 bgpM2PeerMinASOrigInterval 1387 Unsigned32, 1388 bgpM2PeerMinRouteAdverInterval 1389 Unsigned32 1390 } 1391 bgpM2PeerConnectRetryInterval OBJECT-TYPE 1392 SYNTAX Unsigned32 (1..65535) 1393 MAX-ACCESS read-only 1394 STATUS current 1395 DESCRIPTION 1396 "Time interval in seconds for the ConnectRetry 1397 timer. The suggested value for this timer is 120 1398 seconds." 1399 ::= { bgpM2PeerConfiguredTimersEntry 1 } 1401 bgpM2PeerHoldTimeConfigured OBJECT-TYPE 1402 SYNTAX Unsigned32 ( 0 | 3..65535 ) 1403 MAX-ACCESS read-only 1404 STATUS current 1405 DESCRIPTION 1406 "Time interval in seconds for the Hold Time configured 1407 for this BGP speaker with this peer. This value 1408 is placed in an OPEN message sent to this peer by 1409 this BGP speaker, and is compared with the Hold 1410 Time field in an OPEN message received from the 1411 peer when determining the Hold Time (bgpM2PeerHoldTime) 1412 with the peer. This value must not be less than 1413 three seconds if it is not zero (0) in which case 1414 the Hold Time is NOT to be established with the 1415 peer. The suggested value for this timer is 90 1416 seconds." 1417 REFERENCE 1418 "draft-ietf-idr-bgp4-17.txt, Appendix 6.4" 1419 ::= { bgpM2PeerConfiguredTimersEntry 2 } 1421 bgpM2PeerKeepAliveConfigured OBJECT-TYPE 1422 SYNTAX Unsigned32 ( 0 | 1..21845 ) 1423 MAX-ACCESS read-only 1424 STATUS current 1425 DESCRIPTION 1426 "Time interval in seconds for the KeepAlive timer 1427 configured for this BGP speaker with this peer. 1428 The value of this object will only determine the 1429 KEEPALIVE messages frequency relative to the value 1430 specified in bgpM2PeerHoldTimeConfigured; the actual 1431 time interval for the KEEPALIVE messages is indicated 1432 by bgpM2PeerKeepAlive. A reasonable maximum value 1433 for this timer would be configured to be one third 1434 of that of bgpM2PeerHoldTimeConfigured. 1436 If the value of this object is zero (0), no 1437 periodical KEEPALIVE messages are sent to the peer 1438 after the BGP connection has been established. 1439 The suggested value for this timer is 30 seconds." 1440 REFERENCE 1441 "draft-ietf-idr-bgp4-17.txt, Appendix 6.4" 1442 ::= { bgpM2PeerConfiguredTimersEntry 3 } 1444 bgpM2PeerMinASOrigInterval OBJECT-TYPE 1445 SYNTAX Unsigned32 (0..65535) 1446 MAX-ACCESS read-only 1447 STATUS current 1448 DESCRIPTION 1449 "Time interval in seconds for the MinASOriginationInterval 1450 timer. The suggested value for this timer is 15 1451 seconds." 1452 ::= { bgpM2PeerConfiguredTimersEntry 4 } 1454 bgpM2PeerMinRouteAdverInterval OBJECT-TYPE 1455 SYNTAX Unsigned32 (0..65535) 1456 MAX-ACCESS read-only 1457 STATUS current 1458 DESCRIPTION 1459 "Time interval in seconds for the 1460 MinRouteAdvertisementInterval timer. The suggested 1461 value for this timer is 30 seconds." 1462 ::= { bgpM2PeerConfiguredTimersEntry 5 } 1464 -- 1465 -- Peer Negotiated Timers 1466 -- 1468 bgpM2PeerNegotiatedTimersTable OBJECT-TYPE 1469 SYNTAX SEQUENCE OF BgpM2PeerNegotiatedTimersEntry 1470 MAX-ACCESS not-accessible 1471 STATUS current 1472 DESCRIPTION 1473 "Current values of per-peer timers which can be 1474 dynamically set in the bgpM2PeerConfiguredTimersTable. 1475 Values reflected in this table are the current 1476 operational values, after negotiation from values 1477 derived from initial configuration or last set from 1478 bgpM2PeerConfiguredTimersTable row instances." 1479 ::= { bgpM2PeerTimers 3 } 1480 bgpM2PeerNegotiatedTimersEntry OBJECT-TYPE 1481 SYNTAX BgpM2PeerNegotiatedTimersEntry 1482 MAX-ACCESS not-accessible 1483 STATUS current 1484 DESCRIPTION 1485 "Each entry reflects a value of the currently 1486 operational, negotiated timers as reflected in the 1487 BgpM2PeerNegotiatedTimersEntry." 1488 AUGMENTS { 1489 bgpM2PeerEntry 1490 } 1491 ::= { bgpM2PeerNegotiatedTimersTable 1 } 1493 BgpM2PeerNegotiatedTimersEntry ::= SEQUENCE { 1494 bgpM2PeerHoldTime 1495 Unsigned32, 1496 bgpM2PeerKeepAlive 1497 Unsigned32 1498 } 1500 bgpM2PeerHoldTime OBJECT-TYPE 1501 SYNTAX Unsigned32 ( 0 | 3..65535 ) 1502 MAX-ACCESS read-only 1503 STATUS current 1504 DESCRIPTION 1505 "The value of this object is calculated by this BGP 1506 Speaker as being; 1508 zero (0) - if this was the value sent by the peer and 1509 this value is permitted by this BGP Speaker. In this 1510 case, no keepalive messages are sent and the Hold Timer 1511 is not set. 1513 At least three (3). This value is the smaller of 1514 the value sent by this peer in the OPEN message and 1515 bgpM2PeerHoldTimeConfigured for this peer. 1517 This value is only defined when the peering session is 1518 in the Established state." 1519 REFERENCE 1520 "draft-ietf-idr-bgp4-17.txt, Sec. 4.2" 1521 ::= { bgpM2PeerNegotiatedTimersEntry 1 } 1523 bgpM2PeerKeepAlive OBJECT-TYPE 1524 SYNTAX Unsigned32 ( 0 | 1..21845 ) 1525 MAX-ACCESS read-only 1526 STATUS current 1527 DESCRIPTION 1528 "Time interval in seconds for the KeepAlive timer 1529 established with the peer. The value of this object 1530 is calculated by this BGP speaker such that, when 1531 compared with bgpM2PeerHoldTime, it has the same 1532 proportion as what bgpM2PeerKeepAliveConfigured has 1533 when compared with bgpM2PeerHoldTimeConfigured. If 1534 the value of this object is zero (0), it indicates 1535 that the KeepAlive timer has not been established 1536 with the peer, or, the value of 1537 bgpM2PeerKeepAliveConfigured is zero (0). 1539 This value is only defined when the peering session is 1540 in the Established state." 1541 REFERENCE 1542 "draft-ietf-idr-bgp4-17, Sec. 4.4" 1543 ::= { bgpM2PeerNegotiatedTimersEntry 2 } 1545 -- 1546 -- Peer Capabilities 1547 -- 1549 bgpM2PeerCapabilities 1550 OBJECT IDENTIFIER ::= { bgpM2Peer 4 } 1552 -- 1553 -- Announced Capabilities 1554 -- 1556 bgpM2PeerCapsAnnouncedTable OBJECT-TYPE 1557 SYNTAX SEQUENCE OF BgpM2PeerCapsAnnouncedEntry 1558 MAX-ACCESS not-accessible 1559 STATUS current 1560 DESCRIPTION 1561 "This table contains the capabilities 1562 that are supported for a given peer." 1563 ::= { bgpM2PeerCapabilities 1 } 1565 bgpM2PeerCapsAnnouncedEntry OBJECT-TYPE 1566 SYNTAX BgpM2PeerCapsAnnouncedEntry 1567 MAX-ACCESS not-accessible 1568 STATUS current 1569 DESCRIPTION 1570 "These entries are keyed by a BGP-4 peer remote 1571 address and the BGP Capability Code" 1572 INDEX { 1573 bgpM2PeerIndex, 1574 bgpM2PeerCapAnnouncedCode, 1575 bgpM2PeerCapAnnouncedIndex 1576 } 1577 ::= { bgpM2PeerCapsAnnouncedTable 1 } 1579 BgpM2PeerCapsAnnouncedEntry ::= SEQUENCE { 1580 bgpM2PeerCapAnnouncedCode 1581 Unsigned32, 1582 bgpM2PeerCapAnnouncedIndex 1583 Unsigned32, 1584 bgpM2PeerCapAnnouncedValue 1585 OCTET STRING 1586 } 1588 bgpM2PeerCapAnnouncedCode OBJECT-TYPE 1589 SYNTAX Unsigned32 (0..255) 1590 MAX-ACCESS read-only 1591 STATUS current 1592 DESCRIPTION 1593 "The BGP Capability Advertisement Capability Code." 1594 ::= { bgpM2PeerCapsAnnouncedEntry 1 } 1596 bgpM2PeerCapAnnouncedIndex OBJECT-TYPE 1597 SYNTAX Unsigned32 (1..128) 1598 MAX-ACCESS read-only 1599 STATUS current 1600 DESCRIPTION 1601 "Multiple instances of a given capability may be sent 1602 bgp a BGP speaker. This variable is used to index them." 1603 ::= { bgpM2PeerCapsAnnouncedEntry 2 } 1605 bgpM2PeerCapAnnouncedValue OBJECT-TYPE 1606 SYNTAX OCTET STRING (SIZE(0..255)) 1607 MAX-ACCESS read-only 1608 STATUS current 1609 DESCRIPTION 1610 "The value of the announced capability." 1611 ::= { bgpM2PeerCapsAnnouncedEntry 3 } 1612 -- 1613 -- Received Capabilities 1614 -- 1616 bgpM2PeerCapsReceivedTable OBJECT-TYPE 1617 SYNTAX SEQUENCE OF BgpM24PeerCapsReceivedEntry 1618 MAX-ACCESS not-accessible 1619 STATUS current 1620 DESCRIPTION 1621 "This table contains the capabilities 1622 that are supported for a given peer." 1623 ::= { bgpM2PeerCapabilities 2 } 1625 bgpM2PeerCapsReceivedEntry OBJECT-TYPE 1626 SYNTAX BgpM24PeerCapsReceivedEntry 1627 MAX-ACCESS not-accessible 1628 STATUS current 1629 DESCRIPTION 1630 "These entries are keyed by a BGP-4 peer remote 1631 address and the BGP Capability Code" 1632 INDEX { 1633 bgpM2PeerIndex, 1634 bgpM2PeerCapReceivedCode, 1635 bgpM2PeerCapReceivedIndex 1636 } 1637 ::= { bgpM2PeerCapsReceivedTable 1 } 1639 BgpM24PeerCapsReceivedEntry ::= SEQUENCE { 1640 bgpM2PeerCapReceivedCode 1641 Unsigned32, 1642 bgpM2PeerCapReceivedIndex 1643 Unsigned32, 1644 bgpM2PeerCapReceivedValue 1645 OCTET STRING 1646 } 1648 bgpM2PeerCapReceivedCode OBJECT-TYPE 1649 SYNTAX Unsigned32 (0..255) 1650 MAX-ACCESS read-only 1651 STATUS current 1652 DESCRIPTION 1653 "The BGP Capability Advertisement Capability Code." 1654 ::= { bgpM2PeerCapsReceivedEntry 1 } 1655 bgpM2PeerCapReceivedIndex OBJECT-TYPE 1656 SYNTAX Unsigned32 (1..128) 1657 MAX-ACCESS read-only 1658 STATUS current 1659 DESCRIPTION 1660 "Multiple instances of a given capability may be sent 1661 bgp a BGP speaker. This variable is used to index them." 1662 ::= { bgpM2PeerCapsReceivedEntry 2 } 1664 bgpM2PeerCapReceivedValue OBJECT-TYPE 1665 SYNTAX OCTET STRING (SIZE(0..255)) 1666 MAX-ACCESS read-only 1667 STATUS current 1668 DESCRIPTION 1669 "The value of the announced capability." 1670 ::= { bgpM2PeerCapsReceivedEntry 3 } 1672 -- 1673 -- Per-peer counters 1674 -- 1676 bgpM2PeerCounters 1677 OBJECT IDENTIFIER ::= { bgpM2Peer 6 } 1679 bgpM2PeerCountersTable OBJECT-TYPE 1680 SYNTAX SEQUENCE OF BgpM2PeerCountersEntry 1681 MAX-ACCESS not-accessible 1682 STATUS current 1683 DESCRIPTION 1684 "The counters associated with a BGP Peer." 1685 ::= { bgpM2PeerCounters 1 } 1687 bgpM2PeerCountersEntry OBJECT-TYPE 1688 SYNTAX BgpM2PeerCountersEntry 1689 MAX-ACCESS not-accessible 1690 STATUS current 1691 DESCRIPTION 1692 "Each entry contains counters of message transmissions 1693 and FSM transitions for a given BGP Peering session." 1694 AUGMENTS { 1695 bgpM2PeerEntry 1696 } 1697 ::= { bgpM2PeerCountersTable 1 } 1698 BgpM2PeerCountersEntry ::= SEQUENCE { 1699 bgpM2PeerInUpdates 1700 Counter32, 1701 bgpM2PeerOutUpdates 1702 Counter32, 1703 bgpM2PeerInTotalMessages 1704 Counter32, 1705 bgpM2PeerOutTotalMessages 1706 Counter32, 1707 bgpM2PeerFsmEstablishedTrans 1708 Counter32 1709 } 1711 -- +++wayne need to describe what happens if connection is broken 1712 -- and then reestablished. Does the prior counter value accumulate? 1713 bgpM2PeerInUpdates OBJECT-TYPE 1714 SYNTAX Counter32 1715 MAX-ACCESS read-only 1716 STATUS current 1717 DESCRIPTION 1718 "The number of BGP UPDATE messages received on this 1719 connection. This object should be initialized to zero 1720 (0) when the connection is established." 1721 ::= { bgpM2PeerCountersEntry 1 } 1723 bgpM2PeerOutUpdates OBJECT-TYPE 1724 SYNTAX Counter32 1725 MAX-ACCESS read-only 1726 STATUS current 1727 DESCRIPTION 1728 "The number of BGP UPDATE messages transmitted on this 1729 connection. This object should be initialized to zero 1730 (0) when the connection is established." 1731 ::= { bgpM2PeerCountersEntry 2 } 1733 bgpM2PeerInTotalMessages OBJECT-TYPE 1734 SYNTAX Counter32 1735 MAX-ACCESS read-only 1736 STATUS current 1737 DESCRIPTION 1738 "The total number of messages received from the remote 1739 peer on this connection. This object should be 1740 initialized to zero when the connection is established." 1741 ::= { bgpM2PeerCountersEntry 3 } 1742 bgpM2PeerOutTotalMessages OBJECT-TYPE 1743 SYNTAX Counter32 1744 MAX-ACCESS read-only 1745 STATUS current 1746 DESCRIPTION 1747 "The total number of messages transmitted to the remote 1748 peer on this connection. This object should be 1749 initialized to zero when the connection is established." 1750 ::= { bgpM2PeerCountersEntry 4 } 1752 bgpM2PeerFsmEstablishedTrans OBJECT-TYPE 1753 SYNTAX Counter32 1754 MAX-ACCESS read-only 1755 STATUS current 1756 DESCRIPTION 1757 "The total number of times the BGP FSM 1758 transitioned into the established state 1759 for this peer." 1760 ::= { bgpM2PeerCountersEntry 5 } 1762 -- 1763 -- Per-Peer Prefix Counters 1764 -- 1766 bgpM2PrefixCountersTable OBJECT-TYPE 1767 SYNTAX SEQUENCE OF BgpM2PrefixCountersEntry 1768 MAX-ACCESS not-accessible 1769 STATUS current 1770 DESCRIPTION 1771 "Additional per-peer, per AFI SAFI counters for prefixes" 1772 ::= { bgpM2PeerCounters 2 } 1774 bgpM2PrefixCountersEntry OBJECT-TYPE 1775 SYNTAX BgpM2PrefixCountersEntry 1776 MAX-ACCESS not-accessible 1777 STATUS current 1778 DESCRIPTION 1779 "Entry containing information about a bgp-peers prefix 1780 counters." 1781 INDEX { 1782 bgpM2PeerIndex, 1783 bgpM2PrefixCountersAfi, 1784 bgpM2PrefixCountersSafi 1785 } 1786 ::= { bgpM2PrefixCountersTable 1 } 1787 BgpM2PrefixCountersEntry ::= SEQUENCE { 1788 bgpM2PrefixCountersAfi 1789 BgpM2Afi, 1790 bgpM2PrefixCountersSafi 1791 BgpM2Safi, 1792 bgpM2PrefixInPrefixes 1793 Gauge32, 1794 bgpM2PrefixInPrefixesAccepted 1795 Gauge32, 1796 bgpM2PrefixInPrefixesRejected 1797 Gauge32, 1798 bgpM2PrefixOutPrefixes 1799 Gauge32 1800 } 1802 bgpM2PrefixCountersAfi OBJECT-TYPE 1803 SYNTAX BgpM2Afi 1804 MAX-ACCESS read-only 1805 STATUS current 1806 DESCRIPTION 1807 "The AFI index of the per-peer, per prefix counters" 1808 ::= { bgpM2PrefixCountersEntry 1 } 1810 bgpM2PrefixCountersSafi OBJECT-TYPE 1811 SYNTAX BgpM2Safi 1812 MAX-ACCESS read-only 1813 STATUS current 1814 DESCRIPTION 1815 "The SAFI index of the per-peer, per prefix counters" 1816 ::= { bgpM2PrefixCountersEntry 2 } 1818 bgpM2PrefixInPrefixes OBJECT-TYPE 1819 SYNTAX Gauge32 1820 MAX-ACCESS read-only 1821 STATUS current 1822 DESCRIPTION 1823 "The number of prefixes received from a peer and are 1824 stored in the Adj-Ribs-In for that peer." 1825 -- jmh - note that we are allowing stuff to be discarded 1826 ::= { bgpM2PrefixCountersEntry 7 } 1828 bgpM2PrefixInPrefixesAccepted OBJECT-TYPE 1829 SYNTAX Gauge32 1830 MAX-ACCESS read-only 1831 STATUS current 1832 DESCRIPTION 1833 "The number of prefixes for a peer that are installed 1834 in the Adj-Ribs-In and are eligible to become active 1835 in the Loc-Rib." 1836 ::= { bgpM2PrefixCountersEntry 8 } 1838 bgpM2PrefixInPrefixesRejected OBJECT-TYPE 1839 SYNTAX Gauge32 1840 MAX-ACCESS read-only 1841 STATUS current 1842 DESCRIPTION 1843 "The number of prefixes for a peer that are installed 1844 in the Adj-Ribs-In and are NOT eligible to become active 1845 in the Loc-Rib." 1846 ::= { bgpM2PrefixCountersEntry 9 } 1848 bgpM2PrefixOutPrefixes OBJECT-TYPE 1849 SYNTAX Gauge32 1850 MAX-ACCESS read-only 1851 STATUS current 1852 DESCRIPTION 1853 "The number of prefixes for a peer that are installed 1854 in that peers Adj-Ribs-Out." 1855 ::= { bgpM2PrefixCountersEntry 10 } 1857 bgpM2PeerExtensions 1858 OBJECT IDENTIFIER ::= { bgpM2Peer 7 } 1860 bgpM2PeerNonCapExts 1861 OBJECT IDENTIFIER ::= { bgpM2PeerExtensions 1 } 1863 bgpM2PeerCapExts 1864 OBJECT IDENTIFIER ::= { bgpM2PeerExtensions 2 } 1866 -- 1867 -- Peer Route Reflection Extensions 1868 -- 1870 bgpM2PeerRouteReflectionExts 1871 OBJECT IDENTIFIER ::= { bgpM2PeerNonCapExts 2796 } 1872 bgpM2PeerReflectorClientTable OBJECT-TYPE 1873 SYNTAX SEQUENCE OF BgpM2PeerReflectorClientEntry 1874 MAX-ACCESS not-accessible 1875 STATUS current 1876 DESCRIPTION 1877 "Table of route reflection client settings on a per-peer 1878 basis." 1879 REFERENCE 1880 "RFC 2796 - BGP Route Reflection" 1881 ::= { bgpM2PeerRouteReflectionExts 1 } 1883 bgpM2PeerReflectorClientEntry OBJECT-TYPE 1884 SYNTAX BgpM2PeerReflectorClientEntry 1885 MAX-ACCESS not-accessible 1886 STATUS current 1887 DESCRIPTION 1888 "Entry containing data on a per-peer basis on whether 1889 the peer is configured as a route reflector client." 1890 REFERENCE 1891 "RFC 2796 - BGP Route Reflection" 1892 AUGMENTS { 1893 bgpM2PeerEntry 1894 } 1895 ::= { bgpM2PeerReflectorClientTable 1 } 1897 BgpM2PeerReflectorClientEntry ::= SEQUENCE { 1898 bgpM2PeerReflectorClient 1899 INTEGER 1900 } 1902 bgpM2PeerReflectorClient OBJECT-TYPE 1903 SYNTAX INTEGER { 1904 nonClient(0), 1905 client(1), 1906 meshedClient(2) 1907 } 1908 MAX-ACCESS read-only 1909 STATUS current 1910 DESCRIPTION 1911 "This value indicates whether the given peer is a 1912 reflector client of this router, or not. A value of 1913 nonClient indicates that this peer is not a reflector 1914 client. A value of client indicates that this peer is a 1915 reflector client that is not fully meshed with other 1916 reflector clients. A value of meshedClient indicates 1917 that the peer is a reflector client and is fully meshed 1918 with all other reflector clients. 1920 This value must be nonClient (0) for BGP external peers." 1921 REFERENCE 1922 "RFC 2796 - BGP Route Reflection" 1923 ::= { bgpM2PeerReflectorClientEntry 1 } 1925 -- 1926 -- Peer AS Confederations Extensions 1927 -- 1929 bgpM2PeerASConfederationExts 1930 OBJECT IDENTIFIER ::= { bgpM2PeerNonCapExts 3065 } 1932 bgpM2PeerConfedMemberTable OBJECT-TYPE 1933 SYNTAX SEQUENCE OF BgpM2PeerConfedMemberEntry 1934 MAX-ACCESS not-accessible 1935 STATUS current 1936 DESCRIPTION 1937 "Table of confederation member settings on a per-peer 1938 basis." 1939 REFERENCE 1940 "RFC 3065 - BGP Confederations" 1941 ::= { bgpM2PeerASConfederationExts 1 } 1943 bgpM2PeerConfedMemberEntry OBJECT-TYPE 1944 SYNTAX BgpM2PeerConfedMemberEntry 1945 MAX-ACCESS not-accessible 1946 STATUS current 1947 DESCRIPTION 1948 "Entry containing data on a per-peer basis on whether 1949 the peer is configured as a BGP confederation member." 1950 REFERENCE 1951 "RFC 3065 - BGP Confederations" 1952 AUGMENTS { 1953 bgpM2PeerEntry 1954 } 1955 ::= { bgpM2PeerConfedMemberTable 1 } 1957 BgpM2PeerConfedMemberEntry ::= SEQUENCE { 1958 bgpM2PeerConfedMember 1959 TruthValue 1960 } 1961 bgpM2PeerConfedMember OBJECT-TYPE 1962 SYNTAX TruthValue 1963 MAX-ACCESS read-only 1964 STATUS current 1965 DESCRIPTION 1966 "This value indicates whether the given peer is in our 1967 confederation or not." 1968 REFERENCE 1969 "RFC 3065 - BGP Confederations" 1970 ::= { bgpM2PeerConfedMemberEntry 1 } 1972 -- 1973 -- Peer configuration objects 1974 -- 1976 bgpM2PeerConfiguration 1977 OBJECT IDENTIFIER ::= { bgpM2Peer 8 } 1979 -- 1980 -- Administering activated peering sessions 1981 -- 1983 bgpM2CfgPeerAdminStatusTable OBJECT-TYPE 1984 SYNTAX SEQUENCE OF BgpM2CfgPeerAdminStatusEntry 1985 MAX-ACCESS not-accessible 1986 STATUS current 1987 DESCRIPTION 1988 "Table containing rows for administratively starting and 1989 stopping peering sessions." 1990 ::= { bgpM2PeerConfiguration 1 } 1992 bgpM2CfgPeerAdminStatusEntry OBJECT-TYPE 1993 SYNTAX BgpM2CfgPeerAdminStatusEntry 1994 MAX-ACCESS not-accessible 1995 STATUS current 1996 DESCRIPTION 1997 "Entry containing row for administratively starting and 1998 stopping peers." 1999 INDEX { 2000 bgpM2PeerIndex 2001 } 2002 ::= { bgpM2CfgPeerAdminStatusTable 1 } 2004 BgpM2CfgPeerAdminStatusEntry ::= SEQUENCE { 2006 bgpM2CfgPeerAdminStatus 2007 INTEGER 2008 } 2010 bgpM2CfgPeerAdminStatus OBJECT-TYPE 2011 SYNTAX INTEGER { 2012 stop(1), 2013 start(2) 2014 } 2015 MAX-ACCESS read-write 2016 STATUS current 2017 DESCRIPTION 2018 "This object allows the Manual Stop and Manual Start 2019 events to be sent to an activated peering session." 2020 ::= { bgpM2CfgPeerAdminStatusEntry 1 } 2022 -- 2023 -- Peer Configuration 2024 -- 2026 bgpM2CfgPeerNextIndex OBJECT-TYPE 2027 SYNTAX Integer32 (0..65535) 2028 MAX-ACCESS read-only 2029 STATUS current 2030 DESCRIPTION 2031 "This object contains the next appropriate value to 2032 use as an index for creation of a row instance in 2033 in the bgpM2CfgPeerTable. If the number of available 2034 entries in the bgpM2CfgPeerTable is exhausted, a 2035 retrieval value of this object instance will return 2036 0. A value of 0 may also be returned if the agent 2037 is otherwise incapable of bgpM2CfgPeerTable row creation 2038 at the time of bgpM2CfgPeerNextIndex retrieval." 2039 ::= { bgpM2PeerConfiguration 2 } 2041 bgpM2CfgPeerTable OBJECT-TYPE 2042 SYNTAX SEQUENCE OF BgpM2CfgPeerEntry 2043 MAX-ACCESS not-accessible 2044 STATUS current 2045 DESCRIPTION 2046 "BGP configuration peer table. 2048 This table allows the configuration of the parameters 2049 for a session with a BGP peer. 2051 +++wayne provide description of how config should be done 2052 for a peer per table." 2053 ::= { bgpM2PeerConfiguration 3 } 2055 bgpM2CfgPeerEntry OBJECT-TYPE 2056 SYNTAX BgpM2CfgPeerEntry 2057 MAX-ACCESS not-accessible 2058 STATUS current 2059 DESCRIPTION 2060 "Entry containing information set up by a management 2061 entity to configure a connection with a BGP peer." 2062 INDEX { bgpM2CfgPeerIndex } 2063 ::= { bgpM2CfgPeerTable 1 } 2065 BgpM2CfgPeerEntry ::= SEQUENCE { 2066 bgpM2CfgPeerConfiguredVersion 2067 Unsigned32, 2068 bgpM2CfgAllowVersionNegotiation 2069 TruthValue, 2070 bgpM2CfgPeerLocalAddrType 2071 InetAddressType, 2072 bgpM2CfgPeerLocalAddr 2073 InetAddress, 2074 bgpM2CfgPeerLocalAs 2075 InetAutonomousSystemNumber, 2076 bgpM2CfgPeerRemoteAddrType 2077 InetAddressType, 2078 bgpM2CfgPeerRemoteAddr 2079 InetAddress, 2080 bgpM2CfgPeerRemoteAs 2081 InetAutonomousSystemNumber, 2082 bgpM2CfgPeerEntryStorageType 2083 StorageType, 2084 bgpM2CfgPeerError 2085 INTEGER, 2086 bgpM2CfgPeerBgpPeerEntry 2087 RowPointer, 2088 bgpM2CfgPeerRowEntryStatus 2089 RowStatus, 2090 bgpM2CfgPeerIndex 2091 Integer32, 2092 bgpM2CfgPeerStatus 2093 INTEGER 2094 } 2095 bgpM2CfgPeerConfiguredVersion OBJECT-TYPE 2096 SYNTAX Unsigned32 (1..255) 2097 MAX-ACCESS read-create 2098 STATUS current 2099 DESCRIPTION 2100 "The configured version to originally start with 2101 this peer. The BGP speaker may permit negotiation 2102 to a lower version number of the protocol depending on the 2103 set value of bgpM2CfgAllowVersionNegotiation." 2104 DEFVAL { 4 } 2105 ::= { bgpM2CfgPeerEntry 1 } 2107 bgpM2CfgAllowVersionNegotiation OBJECT-TYPE 2108 SYNTAX TruthValue 2109 MAX-ACCESS read-create 2110 STATUS current 2111 DESCRIPTION 2112 "If set to true, during session establishment with this 2113 peer, negotiation to a version lower than that specified 2114 in bgpM2CfgPeerConfiguredVersion will be allowed." 2115 DEFVAL { false } 2116 ::= { bgpM2CfgPeerEntry 2 } 2118 bgpM2CfgPeerLocalAddrType OBJECT-TYPE 2119 SYNTAX InetAddressType 2120 MAX-ACCESS read-create 2121 STATUS current 2122 DESCRIPTION 2123 "The address family of the speakers of this BGP 2124 session." 2125 ::= { bgpM2CfgPeerEntry 3 } 2127 bgpM2CfgPeerLocalAddr OBJECT-TYPE 2128 SYNTAX InetAddress (SIZE (4..20)) 2129 MAX-ACCESS read-create 2130 STATUS current 2131 DESCRIPTION 2132 "The address of the local end of the peering session." 2133 ::= { bgpM2CfgPeerEntry 4 } 2135 bgpM2CfgPeerLocalAs OBJECT-TYPE 2136 SYNTAX InetAutonomousSystemNumber 2137 MAX-ACCESS read-create 2138 STATUS current 2139 DESCRIPTION 2140 "Autonomous system represented to peer on peering 2141 session initialization. Some implementations of 2142 BGP can represent themselves as multiple ASes. 2143 These implementations can set this to an alternate 2144 autonomous system. If this object is set to zero 2145 (0) at the point this row instance is set to active, 2146 then the implementation will initialize this session 2147 representing itself as the value of bgpM2CfgLocalAs." 2148 DEFVAL { 0 } 2149 ::= { bgpM2CfgPeerEntry 5 } 2151 bgpM2CfgPeerRemoteAddrType OBJECT-TYPE 2152 SYNTAX InetAddressType 2153 MAX-ACCESS read-create 2154 STATUS current 2155 DESCRIPTION 2156 "The address family of the speakers of the remote BGP 2157 session." 2158 ::= { bgpM2CfgPeerEntry 6 } 2160 bgpM2CfgPeerRemoteAddr OBJECT-TYPE 2161 SYNTAX InetAddress (SIZE(4..20)) 2162 MAX-ACCESS read-create 2163 STATUS current 2164 DESCRIPTION 2165 "The address of the remote end (destination address 2166 of peer) for peering session." 2167 ::= { bgpM2CfgPeerEntry 7 } 2169 bgpM2CfgPeerRemoteAs OBJECT-TYPE 2170 SYNTAX InetAutonomousSystemNumber 2171 MAX-ACCESS read-create 2172 STATUS current 2173 DESCRIPTION 2174 "Autonomous system number of the remote peer." 2175 ::= { bgpM2CfgPeerEntry 8 } 2177 bgpM2CfgPeerEntryStorageType OBJECT-TYPE 2178 SYNTAX StorageType 2179 MAX-ACCESS read-create 2180 STATUS current 2181 DESCRIPTION 2182 "This object type specifies the intended storage 2183 type for the bgpM2CfgPeerEntry row instance." 2184 ::= { bgpM2CfgPeerEntry 9 } 2186 bgpM2CfgPeerError OBJECT-TYPE 2187 SYNTAX INTEGER { 2188 unknown(0), 2189 notActivated (1), 2190 errDuplicatePeeringSession (2), 2191 activated (3) 2192 -- +++wayne more to follow 2193 } 2194 MAX-ACCESS read-only 2195 STATUS current 2196 DESCRIPTION 2197 "This value indicates the current error status of 2198 the row denoting the configured error status. 2200 If this row is still under creation (has not been activated 2201 bgpM2CfgPeerRowEntryStatus), then this instance will be set to 2202 not-activated (1). 2204 At the point that the row is activated, bgpM2CfgPeerError 2205 will reflect the error status of the row data itself. If 2206 there is another session already activated with the same 2207 local and remote addresses as denoted by 2208 {bgpM2CfgPeerLocalAddrType, bgpM2CfgPeerLocalAddr, 2209 bgpM2CfgPeerRemoteAddr}, then 2210 the value of this will be set to 2211 err-duplicate-peering-session (2). 2213 If this row is associated with a peer session whose 2214 initialization has been attempted, the value will be 2215 set to activated (3) (and, bgpM2PeerCfgPeerEntry will 2216 be set to the row instance of the entry in the 2217 bgpM2PeerTable which reflects the state of the peering 2218 session). 2220 Note that this object only reflects the error as a 2221 function of the attempted activation of this row as 2222 containing data for a bgp peering session. The actual 2223 state of the session at the point of any protocol exchange 2224 or session state machine initiation is reflected in the 2225 bgpM2PeerTable row instance (as reflected through 2226 bgpM2CfgPeerPeerEntry) associated with this row instance." 2227 ::= { bgpM2CfgPeerEntry 10 } 2228 bgpM2CfgPeerBgpPeerEntry OBJECT-TYPE 2229 SYNTAX RowPointer 2230 MAX-ACCESS read-only 2231 STATUS current 2232 DESCRIPTION 2233 "Upon activation of the session data contained in this 2234 row instance, this object points to an instance of a row 2235 within the bgpM2PeerTable reflecting the session in its 2236 initializing or operational state. Retrieval of this 2237 column instance will always yield a value of {0.0} unless 2238 the session has successfully been activated (via 2239 bgpM2CfgPeerRowEntryStatus). Such row instances will always 2240 have a value of bgpM2CfgPeerError which is activated (3)." 2241 ::= { bgpM2CfgPeerEntry 11 } 2243 bgpM2CfgPeerRowEntryStatus OBJECT-TYPE 2244 SYNTAX RowStatus 2245 MAX-ACCESS read-create 2246 STATUS current 2247 DESCRIPTION 2248 "This object type is used to control creation, 2249 activation, and deletion of this row instance." 2250 -- +++wayne need better directions for agent auto-removal 2251 -- of row instances which have moved to active or error 2252 -- state 2253 ::= { bgpM2CfgPeerEntry 12 } 2255 bgpM2CfgPeerIndex OBJECT-TYPE 2256 SYNTAX Integer32 (1..65535) 2257 MAX-ACCESS accessible-for-notify 2258 STATUS current 2259 DESCRIPTION 2260 "Uniquely identifies an instance of a peer row, as 2261 an element of configuration." 2262 ::= { bgpM2CfgPeerEntry 13 } 2264 bgpM2CfgPeerStatus OBJECT-TYPE 2265 SYNTAX INTEGER { 2266 halted(1), 2267 running(2) 2268 } 2269 MAX-ACCESS read-create 2270 STATUS current 2271 DESCRIPTION 2272 "This specifies the state of the peering session upon 2273 activation. If disabled, the FSM is in the halted 2274 state and no Automatic Start events are generated. 2275 If enabled, the FSM is in the running state and 2276 Automatic Start events may be generated." 2277 ::= { bgpM2CfgPeerEntry 14 } 2279 -- 2280 -- Per-peer timers table 2281 -- 2283 bgpM2CfgPeerTimersTable OBJECT-TYPE 2284 SYNTAX SEQUENCE OF BgpM2CfgPeerTimersEntry 2285 MAX-ACCESS not-accessible 2286 STATUS current 2287 DESCRIPTION 2288 "Table for configuration of per-peer timers." 2289 ::= { bgpM2PeerConfiguration 4 } 2291 bgpM2CfgPeerTimersEntry OBJECT-TYPE 2292 SYNTAX BgpM2CfgPeerTimersEntry 2293 MAX-ACCESS not-accessible 2294 STATUS current 2295 DESCRIPTION 2296 "Entry containing per-peer timer configuration." 2297 AUGMENTS { 2298 bgpM2CfgPeerEntry 2299 } 2300 ::= { bgpM2CfgPeerTimersTable 1 } 2302 BgpM2CfgPeerTimersEntry ::= SEQUENCE { 2303 bgpM2CfgPeerConnectRetryInterval 2304 Unsigned32, 2305 bgpM2CfgPeerHoldTimeConfigured 2306 Unsigned32, 2307 bgpM2CfgPeerKeepAliveConfigured 2308 Unsigned32, 2309 bgpM2CfgPeerMinASOrigInterval 2310 Unsigned32, 2311 bgpM2CfgPeerMinRouteAdverInter 2312 Unsigned32 2313 } 2315 bgpM2CfgPeerConnectRetryInterval OBJECT-TYPE 2316 SYNTAX Unsigned32 (1..65535) 2317 MAX-ACCESS read-create 2318 STATUS current 2319 DESCRIPTION 2320 "Time interval in seconds for the ConnectRetry 2321 timer. The suggested value for this timer is 120 2322 seconds." 2323 DEFVAL { 2324 120 2325 } 2326 ::= { bgpM2CfgPeerTimersEntry 1 } 2328 bgpM2CfgPeerHoldTimeConfigured OBJECT-TYPE 2329 SYNTAX Unsigned32 ( 0 | 3..65535 ) 2330 MAX-ACCESS read-create 2331 STATUS current 2332 DESCRIPTION 2333 "Time interval in seconds for the Hold Time configured 2334 for this BGP speaker with this peer. This value 2335 is placed in an OPEN message sent to this peer by 2336 this BGP speaker, and is compared with the Hold 2337 Time field in an OPEN message received from the 2338 peer when determining the Hold Time (bgpM2PeerHoldTime) 2339 with the peer. This value must not be less than 2340 three seconds if it is not zero (0) in which case 2341 the Hold Time is NOT to be established with the 2342 peer. The suggested value for this timer is 90 2343 seconds." 2344 REFERENCE 2345 "draft-ietf-idr-bgp4-17.txt, Appendix 6.4" 2346 DEFVAL { 2347 90 2348 } 2349 ::= { bgpM2CfgPeerTimersEntry 2 } 2351 bgpM2CfgPeerKeepAliveConfigured OBJECT-TYPE 2352 SYNTAX Unsigned32 ( 0 | 1..21845 ) 2353 MAX-ACCESS read-create 2354 STATUS current 2355 DESCRIPTION 2356 "Time interval in seconds for the KeepAlive timer 2357 configured for this BGP speaker with this peer. 2358 The value of this object will only determine the 2359 KEEPALIVE messages frequency relative to the value 2360 specified in bgpM2PeerHoldTimeConfigured; the actual 2361 time interval for the KEEPALIVE messages is indicated 2362 by bgpM2PeerKeepAlive. A reasonable maximum value 2363 for this timer would be configured to be one third 2364 of that of bgpM2PeerHoldTimeConfigured. 2366 If the value of this object is zero (0), no 2367 periodical KEEPALIVE messages are sent to the peer 2368 after the BGP connection has been established. 2369 The suggested value for this timer is 30 seconds." 2370 REFERENCE 2371 "draft-ietf-idr-bgp4-17.txt, Appendix 6.4" 2372 DEFVAL { 2373 30 2374 } 2375 ::= { bgpM2CfgPeerTimersEntry 3 } 2377 bgpM2CfgPeerMinASOrigInterval OBJECT-TYPE 2378 SYNTAX Unsigned32 (0..65535) 2379 MAX-ACCESS read-create 2380 STATUS current 2381 DESCRIPTION 2382 "Time interval in seconds for the MinASOriginationInterval 2383 timer. The suggested value for this timer is 15 2384 seconds." 2385 DEFVAL { 2386 15 2387 } 2388 ::= { bgpM2CfgPeerTimersEntry 4 } 2390 bgpM2CfgPeerMinRouteAdverInter OBJECT-TYPE 2391 SYNTAX Unsigned32 (0..65535) 2392 MAX-ACCESS read-create 2393 STATUS current 2394 DESCRIPTION 2395 "Time interval in seconds for the 2396 MinRouteAdvertisementInterval timer. The suggested 2397 value for this timer is 30 seconds." 2398 DEFVAL { 2399 30 2400 } 2401 ::= { bgpM2CfgPeerTimersEntry 5 } 2403 -- 2404 -- Per-peer configuration extensions 2405 -- 2407 bgpM2CfgPeerExtensions 2409 OBJECT IDENTIFIER ::= { bgpM2PeerConfiguration 5 } 2411 bgpM2CfgPeerNonCapExts 2412 OBJECT IDENTIFIER ::= { bgpM2CfgPeerExtensions 1 } 2414 bgpM2CfgPeerCapExts 2415 OBJECT IDENTIFIER ::= { bgpM2CfgPeerExtensions 2 } 2417 -- 2418 -- Peer route reflection configuration 2419 -- 2421 bgpM2CfgPeerRouteReflectionExts 2422 OBJECT IDENTIFIER ::= { bgpM2CfgPeerNonCapExts 2796 } 2424 bgpM2CfgPeerReflectorClientTable OBJECT-TYPE 2425 SYNTAX SEQUENCE OF BgpM2CfgPeerReflectorClientEntry 2426 MAX-ACCESS not-accessible 2427 STATUS current 2428 DESCRIPTION 2429 "Table of route reflection client settings on a per-peer 2430 basis." 2431 REFERENCE 2432 "RFC 2796 - BGP Route Reflection" 2433 ::= { bgpM2CfgPeerRouteReflectionExts 1 } 2435 bgpM2CfgPeerReflectorClientEntry OBJECT-TYPE 2436 SYNTAX BgpM2CfgPeerReflectorClientEntry 2437 MAX-ACCESS not-accessible 2438 STATUS current 2439 DESCRIPTION 2440 "Entry containing data on a per-peer basis on whether 2441 the peer is configured as a route reflector client." 2442 REFERENCE 2443 "RFC 2796 - BGP Route Reflection" 2444 AUGMENTS { 2445 bgpM2CfgPeerEntry 2446 } 2447 ::= { bgpM2CfgPeerReflectorClientTable 1 } 2449 BgpM2CfgPeerReflectorClientEntry ::= SEQUENCE { 2450 bgpM2CfgPeerReflectorClient 2451 INTEGER 2452 } 2454 bgpM2CfgPeerReflectorClient OBJECT-TYPE 2455 SYNTAX INTEGER { 2456 nonClient(0), 2457 client(1), 2458 meshedClient(2) 2459 } 2460 MAX-ACCESS read-create 2461 STATUS current 2462 DESCRIPTION 2463 "This value indicates whether the given peer is a 2464 reflector client of this router, or not. A value of 2465 nonClient indicates that this peer is not a reflector 2466 client. A value of client indicates that this peer is a 2467 reflector client that is not fully meshed with other 2468 reflector clients. A value of meshedClient indicates 2469 that the peer is a reflector client and is fully meshed 2470 with all other reflector clients. 2472 This value must be nonClient (0) for BGP external peers." 2473 REFERENCE 2474 "RFC 2796 - BGP Route Reflection" 2475 ::= { bgpM2CfgPeerReflectorClientEntry 1 } 2477 -- 2478 -- Peer AS Confederations Extensions 2479 -- 2481 bgpM2CfgPeerASConfederationExts 2482 OBJECT IDENTIFIER ::= { bgpM2CfgPeerNonCapExts 3065 } 2484 bgpM2CfgPeerConfedMemberTable OBJECT-TYPE 2485 SYNTAX SEQUENCE OF BgpM2CfgPeerConfedMemberEntry 2486 MAX-ACCESS not-accessible 2487 STATUS current 2488 DESCRIPTION 2489 "Table of confederation member settings on a per-peer 2490 basis." 2491 REFERENCE 2492 "RFC 3065 - BGP Confederations" 2493 ::= { bgpM2CfgPeerASConfederationExts 1 } 2495 bgpM2CfgPeerConfedMemberEntry OBJECT-TYPE 2497 SYNTAX BgpM2CfgPeerConfedMemberEntry 2498 MAX-ACCESS not-accessible 2499 STATUS current 2500 DESCRIPTION 2501 "Entry containing data on a per-peer basis on whether 2502 the peer is configured as a BGP confederation member." 2503 REFERENCE 2504 "RFC 3065 - BGP Confederations" 2505 AUGMENTS { 2506 bgpM2PeerEntry 2507 } 2508 ::= { bgpM2CfgPeerConfedMemberTable 1 } 2510 BgpM2CfgPeerConfedMemberEntry ::= SEQUENCE { 2511 bgpM2CfgPeerConfedMember 2512 TruthValue 2513 } 2515 bgpM2CfgPeerConfedMember OBJECT-TYPE 2516 SYNTAX TruthValue 2517 MAX-ACCESS read-create 2518 STATUS current 2519 DESCRIPTION 2520 "This value indicates whether the given peer is in our 2521 confederation or not." 2522 REFERENCE 2523 "RFC 3065 - BGP Confederations" 2524 ::= { bgpM2CfgPeerConfedMemberEntry 1 } 2526 -- 2527 -- BGP NLRI Data 2528 -- 2530 bgpM2Rib 2531 OBJECT IDENTIFIER ::= { bgpM2 3 } 2533 -- 2534 -- NLRI Table 2535 -- 2537 bgpM2NlriTable OBJECT-TYPE 2538 SYNTAX SEQUENCE OF BgpM2NlriEntry 2539 MAX-ACCESS not-accessible 2540 STATUS current 2541 DESCRIPTION 2542 "The BGP-4 Received Path Attribute Table contains 2543 information about paths to destination networks 2544 received from all BGP4 peers. Collectively, this 2545 represents the Adj-Ribs-In. The route where 2546 bgpM2NlriBest is TRUE represents, for this NLRI, 2547 the route that is installed in the LocRib from the 2548 Adj-Ribs-In." 2549 ::= { bgpM2Rib 1 } 2551 bgpM2NlriEntry OBJECT-TYPE 2552 SYNTAX BgpM2NlriEntry 2553 MAX-ACCESS not-accessible 2554 STATUS current 2555 DESCRIPTION 2556 "Information about a path to a network." 2557 INDEX { 2558 bgpM2PeerIndex, 2559 bgpM2NlriAfi, 2560 bgpM2NlriSafi, 2561 bgpM2NlriPrefix, 2562 bgpM2NlriPrefixLen, 2563 bgpM2NlriIndex 2564 } 2565 ::= { bgpM2NlriTable 1 } 2567 BgpM2NlriEntry ::= SEQUENCE { 2568 bgpM2NlriIndex 2569 Unsigned32, 2570 bgpM2NlriAfi 2571 BgpM2Afi, 2572 bgpM2NlriSafi 2573 BgpM2Safi, 2574 bgpM2NlriPrefixType 2575 InetAddressType, 2576 bgpM2NlriPrefix 2577 InetAddress, 2578 bgpM2NlriPrefixLen 2579 InetAddressPrefixLength, 2580 bgpM2NlriBest 2581 TruthValue, 2582 bgpM2NlriCalcLocalPref 2583 Unsigned32, 2584 bgpM2PathAttrIndex 2585 Unsigned32, 2586 bgpM2NlriOpaqueType 2587 INTEGER, 2588 bgpM2NlriOpaquePointer 2589 RowPointer 2590 } 2592 bgpM2NlriIndex OBJECT-TYPE 2593 SYNTAX Unsigned32 2594 MAX-ACCESS read-only 2595 STATUS current 2596 DESCRIPTION 2597 "This index allows for multiple instances of a base 2598 prefix for a certain AFI SAFI from a given peer. 2599 This is currently useful for two things: 2600 1. Allowing for a peer in future implementations to 2601 send more than a single route instance. 2602 2. Allow for extensions which extend the NLRI field 2603 to send the same prefix while utilizing other 2604 extension specific information. An example of 2605 this is RFC 3107 - Carrying MPLS labels in BGP." 2606 REFERENCE 2607 "RFC 3107 - Carrying Label Information in BGP-4" 2608 ::= { bgpM2NlriEntry 1 } 2610 bgpM2NlriAfi OBJECT-TYPE 2611 SYNTAX BgpM2Afi 2612 MAX-ACCESS read-only 2613 STATUS current 2614 DESCRIPTION 2615 "The address family of the prefix for this NLRI." 2616 ::= { bgpM2NlriEntry 2 } 2618 bgpM2NlriSafi OBJECT-TYPE 2619 SYNTAX BgpM2Safi 2620 MAX-ACCESS read-only 2621 STATUS current 2622 DESCRIPTION 2623 "The subsequent address family of the prefix for 2624 this NLRI" 2625 REFERENCE 2626 "RFC 2858 - Multiprotocol Extensions for BGP-4" 2627 ::= { bgpM2NlriEntry 3 } 2629 bgpM2NlriPrefixType OBJECT-TYPE 2630 SYNTAX InetAddressType 2631 MAX-ACCESS read-only 2632 STATUS current 2633 DESCRIPTION 2634 "The type of the IP address prefix in the 2635 Network Layer Reachability Information field. 2636 The value of this object is derived from the 2637 appropriate value from the bgpM2NlriAfi field. 2638 Where an appropriate InetAddressType is not 2639 available, the value of the object must be 2640 unknown(0). 2642 XXX TODO - This seems like a hack." 2643 ::= { bgpM2NlriEntry 4 } 2645 bgpM2NlriPrefix OBJECT-TYPE 2646 SYNTAX InetAddress (SIZE (4..20)) 2647 MAX-ACCESS read-only 2648 STATUS current 2649 DESCRIPTION 2650 "An IP address prefix in the Network Layer 2651 Reachability Information field. This object 2652 is an IP address containing the prefix with 2653 length specified by 2654 bgpM2PathAttrAddrPrefixLen. 2655 Any bits beyond the length specified by 2656 bgpM2PathAttrAddrPrefixLen are zeroed." 2657 ::= { bgpM2NlriEntry 5 } 2659 bgpM2NlriPrefixLen OBJECT-TYPE 2660 SYNTAX InetAddressPrefixLength 2661 MAX-ACCESS read-only 2662 STATUS current 2663 DESCRIPTION 2664 "Length in bits of the address prefix in 2665 the Network Layer Reachability Information field." 2666 ::= { bgpM2NlriEntry 6 } 2668 bgpM2NlriBest OBJECT-TYPE 2669 SYNTAX TruthValue 2670 MAX-ACCESS read-only 2671 STATUS current 2672 DESCRIPTION 2673 "An indication of whether or not this route 2674 was chosen as the best BGP4 route." 2675 ::= { bgpM2NlriEntry 7 } 2676 bgpM2NlriCalcLocalPref OBJECT-TYPE 2677 SYNTAX Unsigned32 2678 MAX-ACCESS read-only 2679 STATUS current 2680 DESCRIPTION 2681 "The degree of preference calculated by the 2682 receiving BGP4 speaker for an advertised 2683 route." 2684 ::= { bgpM2NlriEntry 8 } 2686 bgpM2PathAttrIndex OBJECT-TYPE 2687 SYNTAX Unsigned32 2688 MAX-ACCESS read-only 2689 STATUS current 2690 DESCRIPTION 2691 "This value is a unique index for the per-NLRI entry 2692 in the bgpM2PathAttrTable. It is assigned by the 2693 agent at the point of creation of the bgpM2PathAttrTable 2694 row entry. While its value is guaranteed to be unique 2695 at any time, it is otherwise opaque to the management 2696 application with respect to its value or the contiguity 2697 of bgpM2PathAttrIndex row instance values across rows 2698 of the bgpM2PeerAttrTable. It is used to provide an 2699 index structure for other tables whose data is logically 2700 per-peer, per-NLRI." 2701 ::= { bgpM2NlriEntry 9 } 2703 bgpM2NlriOpaqueType OBJECT-TYPE 2704 SYNTAX INTEGER { 2705 none(0), 2706 bgpMplsLabelStack(1) 2707 } 2708 MAX-ACCESS read-only 2709 STATUS current 2710 DESCRIPTION 2711 "This object enumerates the type of the row that is 2712 pointed to in the table row bgpM2NlriOpaquePointer 2713 instance, if bgpM2NlriOpaquePointer is in fact not 2714 a zero length. bgpM2NlriOpaqueType is necessary since 2715 the data referenced by bgpM2NlriOpaquePointer is 2716 opaque to BGP. For example, in the case of RFC 3107, 2717 the label stack that is pointed to may occur in the 2718 mplsLabelStackTable from the MPLS-LSR-MIB, and the 2719 instance value of bgpM2NlriOpaqueType would be 2720 bgpMplsLabelStack(1)." 2721 REFERENCE 2722 "RFC 3107 - Carrying Label Information in BGP-4 2723 draft-ietf-mpls-lsr-mib-08.txt" 2724 ::= { bgpM2NlriEntry 10 } 2726 bgpM2NlriOpaquePointer OBJECT-TYPE 2727 SYNTAX RowPointer 2728 MAX-ACCESS read-only 2729 STATUS current 2730 DESCRIPTION 2731 "Pointer to a row that decomposes the data that is 2732 opaque to the BGP MIB but is sent in the NLRI. 2733 This RowPointer has zero (0) length data instance 2734 if bgpM2NlriOpaqueType is none." 2735 ::= { bgpM2NlriEntry 11 } 2737 -- 2738 -- Adj-Ribs-Out Table 2739 -- 2741 bgpM2AdjRibsOutTable OBJECT-TYPE 2742 SYNTAX SEQUENCE OF BgpM2AdjRibsOutEntry 2743 MAX-ACCESS not-accessible 2744 STATUS current 2745 DESCRIPTION 2746 "This table contains on a per-peer basis one or more 2747 routes from the bgpM2NlriTable that have been 2748 placed in this peer's Adj-Ribs-Out." 2749 REFERENCE 2750 "draft-ietf-idr-bgp4-17.txt, Sec. 3.2" 2751 ::= { bgpM2Rib 2 } 2753 bgpM2AdjRibsOutEntry OBJECT-TYPE 2754 SYNTAX BgpM2AdjRibsOutEntry 2755 MAX-ACCESS not-accessible 2756 STATUS current 2757 DESCRIPTION 2758 "List of BGP routes that have been placed into a 2759 peer's Adj-Ribs-Out." 2760 INDEX { 2761 bgpM2PeerIndex, 2762 bgpM2NlriAfi, 2763 bgpM2NlriSafi, 2764 bgpM2NlriPrefix, 2765 bgpM2NlriPrefixLen, 2766 bgpM2AdjRibsOutIndex 2767 } 2768 ::= { bgpM2AdjRibsOutTable 1 } 2770 BgpM2AdjRibsOutEntry ::= SEQUENCE { 2771 bgpM2AdjRibsOutIndex 2772 Unsigned32, 2773 bgpM2AdjRibsOutRoute 2774 RowPointer 2775 } 2777 bgpM2AdjRibsOutIndex OBJECT-TYPE 2778 SYNTAX Unsigned32 2779 MAX-ACCESS read-only 2780 STATUS current 2781 DESCRIPTION 2782 "Certain extensions to BGP permit multiple instance of 2783 a per afi, per safi prefix to be advertised to a peer. 2784 This object allows the enumeration of them." 2785 ::= { bgpM2AdjRibsOutEntry 1 } 2787 bgpM2AdjRibsOutRoute OBJECT-TYPE 2788 SYNTAX RowPointer 2789 MAX-ACCESS read-only 2790 STATUS current 2791 DESCRIPTION 2792 "This object points to the route in the bgpM2NlriTable 2793 that corresponds to the entry in the peer's 2794 Adj-Rib-Out. Outgoing route maps are not 2795 reflected at this point as those are part of the 2796 Update-Send process." 2797 REFERENCE 2798 "draft-ietf-idr-bgp4-17.txt, Sec. 9.2" 2799 ::= { bgpM2AdjRibsOutEntry 2 } 2801 -- 2802 -- BGP Rib Path Attributes Table 2803 -- 2805 -- 2806 -- Path Attribute Counter 2807 -- 2809 bgpM2PathAttrCount OBJECT-TYPE 2810 SYNTAX Counter32 2811 MAX-ACCESS read-only 2812 STATUS current 2813 DESCRIPTION 2814 "The number of entries in the bgpM2PathAttrTable." 2815 ::= { bgpM2Rib 3 } 2817 -- 2818 -- Path Attributes Table 2819 -- 2821 bgpM2PathAttrTable OBJECT-TYPE 2822 SYNTAX SEQUENCE OF BgpM2PathAttrEntry 2823 MAX-ACCESS not-accessible 2824 STATUS current 2825 DESCRIPTION 2826 "Provides per advertised network-prefix attribute data, 2827 as advertised over a peering session." 2828 ::= { bgpM2Rib 4 } 2830 bgpM2PathAttrEntry OBJECT-TYPE 2831 SYNTAX BgpM2PathAttrEntry 2832 MAX-ACCESS not-accessible 2833 STATUS current 2834 DESCRIPTION 2835 "Each entry contains data about a given network 2836 prefix, per-prefix and per-advertising peer." 2837 INDEX { 2838 bgpM2PathAttrIndex 2839 } 2840 ::= { bgpM2PathAttrTable 1 } 2842 BgpM2PathAttrEntry ::= SEQUENCE { 2843 bgpM2PathAttrOrigin 2844 INTEGER, 2845 bgpM2PathAttrNextHopAddrType 2846 InetAddressType, 2847 bgpM2PathAttrNextHop 2848 InetAddress, 2849 bgpM2PathAttrMedPresent 2850 TruthValue, 2851 bgpM2PathAttrMed 2852 Unsigned32, 2853 bgpM2PathAttrLocalPrefPresent 2854 TruthValue, 2855 bgpM2PathAttrLocalPref 2856 Unsigned32, 2857 bgpM2PathAttrAtomicAggregate 2858 INTEGER, 2859 bgpM2PathAttrAggregatorAS 2860 InetAutonomousSystemNumber, 2861 bgpM2PathAttrAggregatorAddr 2862 BgpM2Identifier, 2863 bgpM2AsPathCalcLength 2864 Unsigned32, 2865 bgpM2AsPathString 2866 SnmpAdminString, 2867 bgpM2AsPathIndex 2868 Unsigned32 2869 } 2871 bgpM2PathAttrOrigin OBJECT-TYPE 2872 SYNTAX INTEGER { 2873 igp(1),-- networks are interior 2874 egp(2),-- networks learned via the EGP protocol 2875 incomplete(3) -- undetermined 2876 } 2877 MAX-ACCESS read-only 2878 STATUS current 2879 DESCRIPTION 2880 "The ultimate origin of the path information." 2881 ::= { bgpM2PathAttrEntry 1 } 2883 bgpM2PathAttrNextHopAddrType OBJECT-TYPE 2884 SYNTAX InetAddressType 2885 MAX-ACCESS read-only 2886 STATUS current 2887 DESCRIPTION 2888 "The address family of the address for 2889 the border router that should be used 2890 to access the destination network." 2891 ::= { bgpM2PathAttrEntry 2 } 2893 bgpM2PathAttrNextHop OBJECT-TYPE 2894 SYNTAX InetAddress (SIZE(4..20)) 2895 MAX-ACCESS read-only 2896 STATUS current 2897 DESCRIPTION 2898 "The address of the border router that 2899 should be used to access the destination 2900 network. This address is the nexthop 2901 address received in the UPDATE packet. 2902 The address family of this object will be the 2903 same as that of the prefix in this row. 2905 Note that for RFC2545 style double nexthops, 2906 this object will always contain the global scope 2907 nexthop. bgpM2LinkLocalNextHopTable will contain 2908 the linklocal scope nexthop. 2910 In the case that the mechanism documented in 2911 draft-kato-bgp-ipv6-link-local-00.txt is used and 2912 only a link local nexthop has been sent, , 2913 bgpM2LinkLocalNextHopPresent will be false 2914 and bgpM2PathAttrNextHop will contain the link local 2915 nexthop." 2916 ::= { bgpM2PathAttrEntry 3 } 2918 bgpM2PathAttrMedPresent OBJECT-TYPE 2919 SYNTAX TruthValue 2920 MAX-ACCESS read-only 2921 STATUS current 2922 DESCRIPTION 2923 "Whether or not the MED value is present. 2924 If it is not present, the bgpM2PathAttrMed 2925 object has no useful value and should be set to 0." 2926 ::= { bgpM2PathAttrEntry 4 } 2928 bgpM2PathAttrMed OBJECT-TYPE 2929 SYNTAX Unsigned32 2930 MAX-ACCESS read-only 2931 STATUS current 2932 DESCRIPTION 2933 "This metric is used to discriminate 2934 between multiple exit points to an 2935 adjacent autonomous system." 2936 ::= { bgpM2PathAttrEntry 5 } 2938 bgpM2PathAttrLocalPrefPresent OBJECT-TYPE 2939 SYNTAX TruthValue 2940 MAX-ACCESS read-only 2941 STATUS current 2942 DESCRIPTION 2943 "Whether or not the LocalPref value is present. 2944 If it is not present, the bgpM2PathAttrLocalPref 2945 object has no useful value and should be set to 0." 2946 ::= { bgpM2PathAttrEntry 6 } 2948 bgpM2PathAttrLocalPref OBJECT-TYPE 2949 SYNTAX Unsigned32 2950 MAX-ACCESS read-only 2951 STATUS current 2952 DESCRIPTION 2953 "The originating BGP4 speakers degree of 2954 preference for an advertised route." 2955 ::= { bgpM2PathAttrEntry 7 } 2957 bgpM2PathAttrAtomicAggregate OBJECT-TYPE 2958 SYNTAX INTEGER { 2959 atomicAggregatePresent(1), 2960 atomicAggregateMissing(2) 2961 } 2962 MAX-ACCESS read-only 2963 STATUS current 2964 DESCRIPTION 2965 "When this object is set to atomicAggregatePresent, 2966 the ATOMIC_AGGREGATE Path Attribute is present 2967 and indicates that the NLRI MUST NOT be made 2968 more specific." 2969 ::= { bgpM2PathAttrEntry 8 } 2971 bgpM2PathAttrAggregatorAS OBJECT-TYPE 2972 SYNTAX InetAutonomousSystemNumber 2973 MAX-ACCESS read-only 2974 STATUS current 2975 DESCRIPTION 2976 "The AS number of the last BGP4 speaker that 2977 performed route aggregation. A value of 2978 zero (0) indicates the absence of this 2979 attribute. 2981 Note propagation of AS of zero is illegal in 2982 the Internet." 2983 ::= { bgpM2PathAttrEntry 9 } 2985 bgpM2PathAttrAggregatorAddr OBJECT-TYPE 2986 SYNTAX BgpM2Identifier 2987 MAX-ACCESS read-only 2988 STATUS current 2989 DESCRIPTION 2990 "The IP address of the last BGP4 speaker 2991 that performed route aggregation. A 2992 value of 0.0.0.0 indicates the absence 2993 of this attribute." 2994 ::= { bgpM2PathAttrEntry 10 } 2996 bgpM2AsPathCalcLength OBJECT-TYPE 2997 SYNTAX Unsigned32 2998 MAX-ACCESS read-only 2999 STATUS current 3000 DESCRIPTION 3001 "This value represents the calculated length of the 3002 AS Path according to the rules of the BGP specification. 3003 This value is used in route selection." 3004 REFERENCE 3005 "draft-ietf-idr-bgp4-17.txt, Sec. 9.1.2.2.a" 3006 ::= { bgpM2PathAttrEntry 11 } 3008 bgpM2AsPathString OBJECT-TYPE 3009 SYNTAX SnmpAdminString 3010 MAX-ACCESS read-only 3011 STATUS current 3012 DESCRIPTION 3013 "This is a string depicting the autonomous system 3014 path to this network which was received from the 3015 peer which advertised it. The format of the string 3016 is implementation-dependent, and should be designed 3017 for operator readability." 3018 ::= { bgpM2PathAttrEntry 12 } 3020 bgpM2AsPathIndex OBJECT-TYPE 3021 SYNTAX Unsigned32 3022 MAX-ACCESS read-only 3023 STATUS current 3024 DESCRIPTION 3025 "This value is a unique index for the decomposed AS Path 3026 in the bgpM2AsPathTable. It is assigned by the 3027 agent at the point of creation of the bgpM2AsPathTable 3028 row entry. While its value is guaranteed to be unique 3029 at any time, it is otherwise opaque to the management 3030 application with respect to its value or the contiguity 3031 of bgpM2AsPathIndex row instance values across rows 3032 of the bgpM2AsPathTable." 3033 ::= { bgpM2PathAttrEntry 13 } 3034 -- 3035 -- As-4 byte AS_PATH 3036 -- 3038 bgpM2AsPath4byteTable OBJECT-TYPE 3039 SYNTAX SEQUENCE OF BgpM2AsPath4byteEntry 3040 MAX-ACCESS not-accessible 3041 STATUS current 3042 DESCRIPTION 3043 "This table is present for BGP speakers that support 3044 the AS 4byte specification and are functioning as 3045 a router between 2-byte and 4-byte AS space." 3046 REFERENCE 3047 "draft-ietf-idr-as4bytes-04.txt - BGP support for 3048 four-octet AS number space" 3049 ::= { bgpM2Rib 5 } 3051 bgpM2AsPath4byteEntry OBJECT-TYPE 3052 SYNTAX BgpM2AsPath4byteEntry 3053 MAX-ACCESS not-accessible 3054 STATUS current 3055 DESCRIPTION 3056 "Each row contains the information for the AS 4-byte 3057 extension's NEW_AS_PATH and NEW_AGGREGATOR attributes." 3058 AUGMENTS { 3059 bgpM2PathAttrEntry 3060 } 3061 ::= { bgpM2AsPath4byteTable 1 } 3063 BgpM2AsPath4byteEntry ::= SEQUENCE { 3064 bgpM2AsPath4bytePathPresent 3065 TruthValue, 3066 bgpM2AsPath4byteAggregatorAS 3067 InetAutonomousSystemNumber, 3068 bgpM2AsPath4byteCalcLength 3069 Unsigned32, 3070 bgpM2AsPath4byteString 3071 SnmpAdminString, 3072 bgpM2AsPath4byteIndex 3073 Unsigned32 3074 } 3076 bgpM2AsPath4bytePathPresent OBJECT-TYPE 3077 SYNTAX TruthValue 3078 MAX-ACCESS read-only 3079 STATUS current 3080 DESCRIPTION 3081 "This value may only be true if this BGP Speaker 3082 is functioning as a router between ASs that 3083 are in 2-byte and 4-byte AS space. If this 3084 value is true, then the NEW_AS_PATH attributes 3085 are present and the 4-byte versions of the 3086 appropriate path attributes are in this row. 3088 If this value is false, then the following values 3089 will be present in the row: 3091 bgpM2PathAttrAggregatorAS - zero (0). 3092 bgpM2AsPathCalcLength - zero (0). 3093 bgpM2AsPathString - zero (0) length string. 3094 bgpM2AsPathIndex - zero (0)." 3095 ::= { bgpM2AsPath4byteEntry 1 } 3097 bgpM2AsPath4byteAggregatorAS OBJECT-TYPE 3098 SYNTAX InetAutonomousSystemNumber 3099 MAX-ACCESS read-only 3100 STATUS current 3101 DESCRIPTION 3102 "The NEW_AGGREGATOR AS number of the last BGP4 speaker 3103 that performed route aggregation. A value of 3104 zero (0) indicates the absence of this 3105 attribute. 3107 Note propagation of AS of zero is illegal in 3108 the Internet." 3109 ::= { bgpM2AsPath4byteEntry 2 } 3111 bgpM2AsPath4byteCalcLength OBJECT-TYPE 3112 SYNTAX Unsigned32 3113 MAX-ACCESS read-only 3114 STATUS current 3115 DESCRIPTION 3116 "This value represents the calculated length of the 3117 NEW_AS_PATH according to the rules of the BGP specification. 3118 This value is used in route selection." 3119 REFERENCE 3120 "draft-ietf-idr-bgp4-17.txt, Sec. 9.1.2.2.a" 3121 ::= { bgpM2AsPath4byteEntry 3 } 3123 bgpM2AsPath4byteString OBJECT-TYPE 3125 SYNTAX SnmpAdminString 3126 MAX-ACCESS read-only 3127 STATUS current 3128 DESCRIPTION 3129 "This is a string depicting the autonomous system 3130 path to this network which was received from the 3131 peer which advertised it. The format of the string 3132 is implementation-dependent, and should be designed 3133 for operator readability." 3134 ::= { bgpM2AsPath4byteEntry 4 } 3136 bgpM2AsPath4byteIndex OBJECT-TYPE 3137 SYNTAX Unsigned32 3138 MAX-ACCESS read-only 3139 STATUS current 3140 DESCRIPTION 3141 "This value is a unique index for the decomposed AS Path 3142 in the bgpM2AsPathTable. It is assigned by the 3143 agent at the point of creation of the bgpM2AsPathTable 3144 row entry. While its value is guaranteed to be unique 3145 at any time, it is otherwise opaque to the management 3146 application with respect to its value or the contiguity 3147 of bgpM2AsPathIndex row instance values across rows 3148 of the bgpM2AsPathTable. " 3149 ::= { bgpM2AsPath4byteEntry 5 } 3151 -- BGP 4 Path attribute AS Path Table. There is one row in 3152 -- this table for each AS which is advertised for a given 3153 -- route as provided from a peer. 3155 -- JMH 3156 -- We need one of these for the NewAsPath for the 4byte draft 3158 bgpM2AsPathTable OBJECT-TYPE 3159 SYNTAX SEQUENCE OF BgpM2AsPathEntry 3160 MAX-ACCESS not-accessible 3161 STATUS current 3162 DESCRIPTION 3163 "The BGP-4 Path Attribute AS Path Table 3164 contains the per network path (NLRI) 3165 AS PATH data received from the 3166 advertising BGP peer." 3167 ::= { bgpM2Rib 6 } 3169 bgpM2AsPathTableEntry OBJECT-TYPE 3171 SYNTAX BgpM2AsPathEntry 3172 MAX-ACCESS not-accessible 3173 STATUS current 3174 DESCRIPTION 3175 "Information about an AS path provided with a path to 3176 a network." 3177 INDEX { 3178 bgpM2PathAttrIndex, 3179 bgpM2AsPathSegmentIndex, 3180 bgpM2AsPathElementIndex 3181 } 3182 ::= { bgpM2AsPathTable 1 } 3184 BgpM2AsPathEntry ::= SEQUENCE { 3185 bgpM2AsPathSegmentIndex 3186 Unsigned32, 3187 bgpM2AsPathElementIndex 3188 Unsigned32, 3189 bgpM2AsPathType 3190 INTEGER, 3191 bgpM2AsPathElementValue 3192 InetAutonomousSystemNumber 3193 } 3195 bgpM2AsPathSegmentIndex OBJECT-TYPE 3196 SYNTAX Unsigned32 3197 MAX-ACCESS read-only 3198 STATUS current 3199 DESCRIPTION 3200 "A per-AS path segment index. This will index a set of 3201 autonomous systems in an AS path which are part 3202 of the same sequence or set (as determined by 3203 the row value of bgpM2AsPathType, which 3204 should be the same value for each bgpM2AsPathTable 3205 entry indexed by the same (bgpM2PathAttrIndex, 3206 bgpM2AsPathIndex) pair)." 3207 ::= { bgpM2AsPathTableEntry 1 } 3209 bgpM2AsPathElementIndex OBJECT-TYPE 3210 SYNTAX Unsigned32 3211 MAX-ACCESS read-only 3212 STATUS current 3213 DESCRIPTION 3214 "A per-AS element index. This will index a particular 3215 AS within a sequence or set of autonomous systems in 3216 an AS path." 3217 ::= { bgpM2AsPathTableEntry 2 } 3219 bgpM2AsPathType OBJECT-TYPE 3220 SYNTAX INTEGER { 3221 asSet(1), 3222 asSequence(2), 3223 confedSequence(3), 3224 confedSet(4) 3225 } 3226 MAX-ACCESS read-only 3227 STATUS current 3228 DESCRIPTION 3229 "The type of sequence in which this asPath 3230 was advertised as an attribute. Note that 3231 all asPath row instances for a given (bgpM2PathAttrIndex, 3232 bgpM2AsPathIndex) index pair will have their 3233 bgpM2AsPathType set to the same value. 3234 The values for bgpM2AsPathType are 3235 interpreted as defined in the base BGP document 3236 and the BGP AS Confederations document." 3237 REFERENCE 3238 "draft-ietf-idr-bgp4-16 3239 RFC 3065 - BGP AS Confederations" 3240 ::= { bgpM2AsPathTableEntry 3 } 3242 bgpM2AsPathElementValue OBJECT-TYPE 3243 SYNTAX InetAutonomousSystemNumber 3244 MAX-ACCESS read-only 3245 STATUS current 3246 DESCRIPTION 3247 "An AS value for an AS the related NLRI traversed 3248 in the propagation of its advertisement. This 3249 value is to be interpreted in the context of the 3250 sequence implied by bgpM2AsPathIndex and 3251 bgpM2AsPathType (and, in sequence of the 3252 other table rows with the same value of 3253 bgpM2PathAttrIndex and bgpM2AsPathIndex)." 3254 ::= { bgpM2AsPathTableEntry 4 } 3256 -- BGP 4 Path unknown attribute. There is one row in 3257 -- this table for each attribute not known by this BGP 3258 -- implementation (or agent instrumentation), but provided 3259 -- from a peer. 3261 bgpM2PathAttrUnknownTable OBJECT-TYPE 3262 SYNTAX SEQUENCE OF BgpM2PathAttrUnknownEntry 3263 MAX-ACCESS not-accessible 3264 STATUS current 3265 DESCRIPTION 3266 "The BGP-4 Path Attribute Unknown Table 3267 contains the per network path (NLRI) 3268 data on the path attributes advertised 3269 with a route but not known to the local BGP implementation 3270 or not otherwise capable of being returned from this agent. 3272 The absence of row data for a given index value for 3273 bgpM2PathAttrIndex indicates a lack of such unknown 3274 attribute information for the indicated network path 3275 (as indexed by that bgpM2PathAttrIndex value in the 3276 bgpM2PathAttrTable)." 3277 ::= { bgpM2Rib 7 } 3279 bgpM2PathAttrUnknownEntry OBJECT-TYPE 3280 SYNTAX BgpM2PathAttrUnknownEntry 3281 MAX-ACCESS not-accessible 3282 STATUS current 3283 DESCRIPTION 3284 "Information about an unknown attribute 3285 provided with a path to a network." 3286 INDEX { 3287 bgpM2PathAttrIndex, 3288 bgpM2PathAttrUnknownIndex 3289 } 3290 ::= { bgpM2PathAttrUnknownTable 1 } 3292 BgpM2PathAttrUnknownEntry ::= SEQUENCE { 3293 bgpM2PathAttrUnknownIndex 3294 Unsigned32, 3295 bgpM2PathAttrUnknownType 3296 Unsigned32, 3297 bgpM2PathAttrUnknownValue 3298 OCTET STRING 3299 } 3301 bgpM2PathAttrUnknownIndex OBJECT-TYPE 3302 SYNTAX Unsigned32 3303 MAX-ACCESS read-only 3304 STATUS current 3305 DESCRIPTION 3306 "An integer index for a row in this table." 3307 ::= { bgpM2PathAttrUnknownEntry 1 } 3309 bgpM2PathAttrUnknownType OBJECT-TYPE 3310 SYNTAX Unsigned32 3311 MAX-ACCESS read-only 3312 STATUS current 3313 DESCRIPTION 3314 "The attribute type advertised with this unknown 3315 attribute by the peer." 3316 ::= { bgpM2PathAttrUnknownEntry 2 } 3318 -- Maximum size of the following is derived as 3319 -- 4096 max message size 3320 -- - 16 BGP message marker bytes 3321 -- - 2 BGP message size 3322 -- - 1 BGP message type (UPDATE with unknown attr) 3323 -- - 2 UPDATE routes length (even assuming no routes) 3324 -- - 2 UPDATE path attributes length 3325 -- - 1 path attribute flag octet 3326 -- - 2 unknown path attr type (in bgpM2PathAttrUnknownType) 3327 -- --------- 3328 -- 4070 bytes maximum per-message attribute value data 3330 bgpM2PathAttrUnknownValue OBJECT-TYPE 3331 SYNTAX OCTET STRING (SIZE(0..4070)) 3332 MAX-ACCESS read-only 3333 STATUS current 3334 DESCRIPTION 3335 "Value of path attribute not understood 3336 by the base BGP-4 document. 3338 Octets beyond the maximum size, if any, 3339 are not recorded by this row object. " 3340 ::= { bgpM2PathAttrUnknownEntry 3 } 3342 -- 3343 -- Path Attribute Extensions 3344 -- 3346 bgpM2PathAttrExtensions 3347 OBJECT IDENTIFIER ::= { bgpM2Rib 8 } 3348 bgpM2PathAttrNonCapExts 3349 OBJECT IDENTIFIER ::= { bgpM2PathAttrExtensions 1 } 3351 bgpM2PathAttrCapExts 3352 OBJECT IDENTIFIER ::= { bgpM2PathAttrExtensions 2 } 3354 -- 3355 -- Path Attribute Route Reflection Extensions 3356 -- 3358 -- 3359 -- Originator ID Table 3360 -- 3362 bgpM2PathAttrRouteReflectionExts 3363 OBJECT IDENTIFIER ::= { bgpM2PathAttrNonCapExts 2796 } 3365 bgpM2PathAttrOriginatorIdTable OBJECT-TYPE 3366 SYNTAX SEQUENCE OF BgpM2PathAttrOriginatorIdEntry 3367 MAX-ACCESS not-accessible 3368 STATUS current 3369 DESCRIPTION 3370 "Per prefix data pertinent to advertisement of a 3371 network prefix through an originator." 3372 REFERENCE 3373 "RFC 2796 - BGP Route Reflection" 3374 ::= { bgpM2PathAttrRouteReflectionExts 1 } 3376 bgpM2PathAttrOriginatorIdEntry OBJECT-TYPE 3377 SYNTAX BgpM2PathAttrOriginatorIdEntry 3378 MAX-ACCESS not-accessible 3379 STATUS current 3380 DESCRIPTION 3381 "Each entry contains data pertinent to a network 3382 prefix as received through its originating BGP 3383 route reflector." 3384 REFERENCE 3385 "RFC 2796 - BGP Route Reflection" 3386 INDEX { 3387 bgpM2PathAttrIndex 3388 } 3389 ::= { bgpM2PathAttrOriginatorIdTable 1 } 3390 BgpM2PathAttrOriginatorIdEntry ::= SEQUENCE { 3391 bgpM2PathAttrOriginatorId 3392 BgpM2Identifier 3393 } 3395 bgpM2PathAttrOriginatorId OBJECT-TYPE 3396 SYNTAX BgpM2Identifier 3397 MAX-ACCESS read-only 3398 STATUS current 3399 DESCRIPTION 3400 "The Originator-ID identifying the router that initially 3401 advertised this destination to a Route Reflector. A 3402 value of 0.0.0.0 indicates the absence of this attribute." 3403 REFERENCE 3404 "This attribute is defined in [RFC2796]." 3405 ::= { bgpM2PathAttrOriginatorIdEntry 1 } 3407 -- 3408 -- Cluster table 3409 -- 3411 bgpM2PathAttrClusterTable OBJECT-TYPE 3412 SYNTAX SEQUENCE OF BgpM2PathAttrClusterEntry 3413 MAX-ACCESS not-accessible 3414 STATUS current 3415 DESCRIPTION 3416 "The BGP-4 Path Attribute Cluster Table 3417 contains the per network path (NLRI) 3418 data on the reflection path which a 3419 route has traversed. The absence of row 3420 data for a given index value for bgpM2PathAttrIndex 3421 indicates a lack of this attribute information 3422 for the indicated network path (as indexed by 3423 that bgpM2PathAttrIndex value in the bgpM2PathAttrTable)." 3424 ::= { bgpM2PathAttrRouteReflectionExts 2 } 3426 bgpM2PathAttrClusterEntry OBJECT-TYPE 3427 SYNTAX BgpM2PathAttrClusterEntry 3428 MAX-ACCESS not-accessible 3429 STATUS current 3430 DESCRIPTION 3431 "Information about a cluster traversal 3432 provided with a path to a network." 3433 INDEX { 3434 bgpM2PathAttrIndex, 3435 bgpM2PathAttrClusterIndex 3436 } 3437 ::= { bgpM2PathAttrClusterTable 1 } 3439 BgpM2PathAttrClusterEntry ::= SEQUENCE { 3440 bgpM2PathAttrClusterIndex 3441 Unsigned32, 3442 bgpM2PathAttrClusterValue 3443 BgpM2Identifier 3444 } 3446 bgpM2PathAttrClusterIndex OBJECT-TYPE 3447 SYNTAX Unsigned32 3448 MAX-ACCESS read-only 3449 STATUS current 3450 DESCRIPTION 3451 "An integral index for a row in this table." 3452 ::= { bgpM2PathAttrClusterEntry 1 } 3454 bgpM2PathAttrClusterValue OBJECT-TYPE 3455 SYNTAX BgpM2Identifier 3456 MAX-ACCESS read-only 3457 STATUS current 3458 DESCRIPTION 3459 "A four octet long value representing a part of the 3460 reflection path that the route has passed. Each such four 3461 octet long value represents the ID of a cluster that 3462 the route has traversed. The sequence of this path as 3463 received in the route advertisement will be preserved in 3464 the sequence of bgpM2PathAttrClusterTable rows (and the 3465 bgpM2PathAttrClusterValues in each row) as returned for 3466 a given bgpM2PathAttrIndex value, and the monotonically 3467 increasing sequence of bgpM2PathAttrClusterIndex values 3468 for that bgpM2PathAttrIndex." 3469 REFERENCE 3470 "This attribute is defined in [RFC2796]." 3471 ::= { bgpM2PathAttrClusterEntry 2 } 3473 -- 3474 -- BGP Communities 3475 -- 3477 bgpM2PathAttrCommunityExts 3478 OBJECT IDENTIFIER ::= { bgpM2PathAttrNonCapExts 1997 } 3479 bgpM2PathAttrCommTable OBJECT-TYPE 3480 SYNTAX SEQUENCE OF BgpM2PathAttrCommEntry 3481 MAX-ACCESS not-accessible 3482 STATUS current 3483 DESCRIPTION 3484 "The BGP-4 Path Attribute Community Table 3485 contains the per network path (NLRI) 3486 data on the community membership advertised 3487 with a route. The absence of row 3488 data for a given index value for bgpM2PathAttrIndex 3489 indicates a lack of this attribute information 3490 for the indicated network path (as indexed by 3491 that bgpM2PathAttrIndex value in the bgpM2PathAttrTable)." 3492 ::= { bgpM2PathAttrCommunityExts 1 } 3494 bgpM2PathAttrCommEntry OBJECT-TYPE 3495 SYNTAX BgpM2PathAttrCommEntry 3496 MAX-ACCESS not-accessible 3497 STATUS current 3498 DESCRIPTION 3499 "Information about a community association 3500 provided with a path to a network." 3501 INDEX { 3502 bgpM2PathAttrIndex, 3503 bgpM2PathAttrCommIndex 3504 } 3505 ::= { bgpM2PathAttrCommTable 1 } 3507 BgpM2PathAttrCommEntry ::= SEQUENCE { 3508 bgpM2PathAttrCommIndex 3509 Unsigned32, 3510 bgpM2PathAttrCommValue 3511 BgpM2Community 3512 } 3514 bgpM2PathAttrCommIndex OBJECT-TYPE 3515 SYNTAX Unsigned32 3516 MAX-ACCESS read-only 3517 STATUS current 3518 DESCRIPTION 3519 "An integer index for a row in this table." 3520 ::= { bgpM2PathAttrCommEntry 1 } 3522 bgpM2PathAttrCommValue OBJECT-TYPE 3524 SYNTAX BgpM2Community 3525 MAX-ACCESS read-only 3526 STATUS current 3527 DESCRIPTION 3528 "A value representing a community. There are certain 3529 4-octet long values which could be returned in this 3530 columnar row data that carry additional semantics." 3531 REFERENCE 3532 "RFC 1997 - BGP Communities Attribute" 3533 ::= { bgpM2PathAttrCommEntry 2 } 3535 -- 3536 -- BGP Extended Communities 3537 -- 3539 bgpM2PathAttrExtCommTable OBJECT-TYPE 3540 SYNTAX SEQUENCE OF BgpM2PathAttrExtCommEntry 3541 MAX-ACCESS not-accessible 3542 STATUS current 3543 DESCRIPTION 3544 "The BGP-4 Path Attribute Community Table 3545 contains the per network path (NLRI) 3546 data on the extended community membership advertised 3547 with a route. The absence of row 3548 data for a given index value for bgpM2PathAttrIndex 3549 indicates a lack of this attribute information 3550 for the indicated network path (as indexed by 3551 that bgpM2PathAttrIndex value in the bgpM2PathAttrTable). 3553 XXX JMH - can not assign the OID until an RFC is published." 3554 ::= { bgpM2PathAttrNonCapExts XXX } 3556 bgpM2PathAttrExtCommEntry OBJECT-TYPE 3557 SYNTAX BgpM2PathAttrExtCommEntry 3558 MAX-ACCESS not-accessible 3559 STATUS current 3560 DESCRIPTION 3561 "Information about an extended community association 3562 provided with a path to a network." 3563 INDEX { 3564 bgpM2PathAttrIndex, 3565 bgpM2PathAttrExtCommIndex 3566 } 3567 ::= { bgpM2PathAttrExtCommTable 1 } 3568 BgpM2PathAttrExtCommEntry ::= SEQUENCE { 3569 bgpM2PathAttrExtCommIndex 3570 Unsigned32, 3571 bgpM2PathAttrExtCommValue 3572 BgpM2ExtendedCommunity 3573 } 3575 bgpM2PathAttrExtCommIndex OBJECT-TYPE 3576 SYNTAX Unsigned32 3577 MAX-ACCESS read-only 3578 STATUS current 3579 DESCRIPTION 3580 "An integral index for a row in this table." 3581 ::= { bgpM2PathAttrExtCommEntry 1 } 3583 bgpM2PathAttrExtCommValue OBJECT-TYPE 3584 SYNTAX BgpM2ExtendedCommunity 3585 MAX-ACCESS read-only 3586 STATUS current 3587 DESCRIPTION 3588 "A value representing an extended community which was 3589 received with the route implied by the bgpM2PathAttr 3590 Index value of this row data. There are certain 3591 8-octet long values which could be returned in this 3592 columnar row data that carry additional semantics." 3593 REFERENCE 3594 "BGP-EXTCOMM - BGP Extended Communities Attribute" 3595 ::= { bgpM2PathAttrExtCommEntry 2 } 3597 -- 3598 -- RFC 2545 link local nexthop 3599 -- 3601 bgpM2LinkLocalNextHopTable OBJECT-TYPE 3602 SYNTAX SEQUENCE OF BgpM2LinkLocalNextHopEntry 3603 MAX-ACCESS not-accessible 3604 STATUS current 3605 DESCRIPTION 3606 "Table of link local nexthops as sent by RFC 2545 3607 for IPv6 BGP Speakers." 3608 REFERENCE 3609 "RFC 2545 - Use of BGP-4 Multiprotocol Extensions 3610 for IPv6 Inter-Domain Routing" 3611 ::= { bgpM2PathAttrNonCapExts 2545 } 3612 bgpM2LinkLocalNextHopEntry OBJECT-TYPE 3613 SYNTAX BgpM2LinkLocalNextHopEntry 3614 MAX-ACCESS not-accessible 3615 STATUS current 3616 DESCRIPTION 3617 "Entry containing the link-local nexthops as sent 3618 by a BGP speaker running RFC 2545 extensions for 3619 double-nexthops." 3620 INDEX { 3621 bgpM2PathAttrIndex 3622 } 3623 ::= { bgpM2LinkLocalNextHopTable 1 } 3625 BgpM2LinkLocalNextHopEntry ::= SEQUENCE { 3626 bgpM2LinkLocalNextHopPresent 3627 TruthValue, 3628 bgpM2LinkLocalNextHop 3629 InetAddress 3630 } 3632 bgpM2LinkLocalNextHopPresent OBJECT-TYPE 3633 SYNTAX TruthValue 3634 MAX-ACCESS read-only 3635 STATUS current 3636 DESCRIPTION 3637 "This value is TRUE if and only if the BGP 3638 speaker is receiving IPv6 NLRI using the 3639 RFC 2545 double nexthop convention and it 3640 has received a link local scope nexthop in 3641 addition to the global scope nexthop." 3642 ::= { bgpM2LinkLocalNextHopEntry 1 } 3644 bgpM2LinkLocalNextHop OBJECT-TYPE 3645 SYNTAX InetAddress (SIZE(20)) 3646 MAX-ACCESS read-only 3647 STATUS current 3648 DESCRIPTION 3649 "This value contains an IPv6 link local address of 3650 InetAddressType of type ipv6z. This value is only 3651 present if bgpM2LinkLocalNextHopPresent is true." 3652 ::= { bgpM2LinkLocalNextHopEntry 2 } 3654 -- 3655 -- Conformance Information 3656 -- 3658 bgpM2Conformance 3659 OBJECT IDENTIFIER ::= { bgpM2 4 } 3661 bgpM2MIBCompliances OBJECT IDENTIFIER ::= 3662 { bgpM2Conformance 1 } 3664 bgpM2MIBGroups OBJECT IDENTIFIER ::= 3665 { bgpM2Conformance 2 } 3667 bgpM2MIBCompliance MODULE-COMPLIANCE 3668 STATUS current 3669 DESCRIPTION 3670 "The compliance statement for entities which 3671 implement the BGP4 mib." 3672 MODULE -- this module 3673 MANDATORY-GROUPS { 3674 bgpM2TimersGroup, 3675 bgpM2CountersGroup, 3676 bgpM2AsPathGroup, 3677 bgpM2As4byteGroup, 3678 bgpM2BaseGroup, 3679 bgpM2ErrorsGroup, 3680 bgpM2PeerGroup, 3681 bgpM2PathAttributesGroup 3682 } 3683 GROUP bgpM2MIBNotificationsGroup 3684 DESCRIPTION 3685 "The notifications group is completely optional, 3686 but highly recommended." 3687 GROUP bgpM2CommunitiesGroup 3688 DESCRIPTION 3689 "The communities group is mandatory only for those 3690 which support the BGP community attribute." 3691 GROUP bgpM2ExtCommunitiesGroup 3692 DESCRIPTION 3693 "The communities group is mandatory only for those 3694 which support the BGP extended community attribute." 3695 GROUP bgpM2RouteReflectionGroup 3696 DESCRIPTION 3697 "The communities group is mandatory only for those 3698 which support the BGP route reflection relationships." 3699 GROUP bgpM2AsConfederationGroup 3700 DESCRIPTION 3701 "The communities group is mandatory only for those 3702 which support the BGP confederation membership." 3703 GROUP bgpM2TimersGroup 3704 DESCRIPTION 3705 "This group is mandatory for all agent implementations." 3706 GROUP bgpM2CountersGroup 3707 DESCRIPTION 3708 "This group is mandatory for all agent implementations." 3709 GROUP bgpM2CapabilitiesGroup 3710 DESCRIPTION 3711 "This group is mandatory for all agent implementations." 3712 GROUP bgpM2AsPathGroup 3713 DESCRIPTION 3714 "This group is mandatory for all agent implementations." 3715 GROUP bgpM2As4byteGroup 3716 DESCRIPTION 3717 "This group is mandatory for all agent implementations." 3718 GROUP bgpM2BaseGroup 3719 DESCRIPTION 3720 "This group is mandatory for all agent implementations." 3721 GROUP bgpM2ErrorsGroup 3722 DESCRIPTION 3723 "This group is mandatory for all agent implementations." 3724 GROUP bgpM2PeerGroup 3725 DESCRIPTION 3726 "This group is mandatory for all agent implementations." 3727 GROUP bgpM2PathAttributesGroup 3728 DESCRIPTION 3729 "This group is mandatory for all agent implementations." 3730 GROUP bgpM2PeerConfigurationGroup 3731 DESCRIPTION 3732 "This group is optional for implementations that wish to 3733 support configuration via SNMP." 3734 GROUP bgpM2PeerRouteReflectorCfgGroup 3735 DESCRIPTION 3736 "This group is optional for implementations that wish to 3737 support configuration of route reflection via SNMP. 3738 Implementation of this feature requires support of the 3739 bgpM2PeerConfigurationGroup." 3740 GROUP bgpM2PeerAsConfederationCfgGroup 3741 DESCRIPTION 3742 "This group is optional for implementations that wish to 3743 support configuration of BGP AS Confederations via SNMP. 3744 Implementation of this feature requires support of the 3745 bgpM2PeerConfigurationGroup." 3746 GROUP bgpM2Rfc2545Group 3747 DESCRIPTION 3748 "This group is required for peers that support exchanging 3749 of IPv6 NLRI per RFC 2545." 3750 ::= { bgpM2MIBCompliances 1 } 3752 bgpM2CommunitiesGroup OBJECT-GROUP 3753 OBJECTS { 3754 bgpM2PathAttrCommIndex, 3755 bgpM2PathAttrCommValue 3756 } 3757 STATUS current 3758 DESCRIPTION 3759 "Objects associated with BGP communities." 3760 ::= { bgpM2MIBGroups 1 } 3762 bgpM2ExtCommunitiesGroup OBJECT-GROUP 3763 OBJECTS { 3764 bgpM2PathAttrExtCommIndex, 3765 bgpM2PathAttrExtCommValue 3766 } 3767 STATUS current 3768 DESCRIPTION 3769 "Objects associated with BGP extended communities." 3770 ::= { bgpM2MIBGroups 2 } 3772 bgpM2RouteReflectionGroup OBJECT-GROUP 3773 OBJECTS { 3774 bgpM2RouteReflector, 3775 bgpM2ClusterId, 3776 bgpM2PeerReflectorClient, 3777 bgpM2PathAttrOriginatorId, 3778 bgpM2PathAttrClusterIndex, 3779 bgpM2PathAttrClusterValue 3780 } 3781 STATUS current 3782 DESCRIPTION 3783 "Objects associated with BGP route reflection." 3784 ::= { bgpM2MIBGroups 3 } 3786 bgpM2AsConfederationGroup OBJECT-GROUP 3787 OBJECTS { 3788 bgpM2ConfederationRouter, 3789 bgpM2ConfederationId, 3790 bgpM2PeerConfedMember 3791 } 3792 STATUS current 3793 DESCRIPTION 3794 "Objects associated with BGP confederation membership." 3795 ::= { bgpM2MIBGroups 4 } 3797 bgpM2TimersGroup OBJECT-GROUP 3798 OBJECTS { 3799 bgpM2PeerFsmEstablishedTime, 3800 bgpM2PeerInUpdatesElapsedTime, 3801 bgpM2PeerConnectRetryInterval, 3802 bgpM2PeerHoldTimeConfigured, 3803 bgpM2PeerKeepAliveConfigured, 3804 bgpM2PeerMinASOrigInterval, 3805 bgpM2PeerMinRouteAdverInterval, 3806 bgpM2PeerHoldTime, 3807 bgpM2PeerKeepAlive 3808 } 3809 STATUS current 3810 DESCRIPTION 3811 "Objects associated with BGP peering timers." 3812 ::= { bgpM2MIBGroups 5 } 3814 bgpM2CountersGroup OBJECT-GROUP 3815 OBJECTS { 3816 bgpM2PeerInUpdates, 3817 bgpM2PeerOutUpdates, 3818 bgpM2PeerInTotalMessages, 3819 bgpM2PeerOutTotalMessages, 3820 bgpM2PeerFsmEstablishedTrans, 3821 bgpM2PrefixCountersAfi, 3822 bgpM2PrefixCountersSafi, 3823 bgpM2PrefixInPrefixes, 3824 bgpM2PrefixInPrefixesAccepted, 3825 bgpM2PrefixInPrefixesRejected, 3826 bgpM2PrefixOutPrefixes 3827 } 3828 STATUS current 3829 DESCRIPTION 3830 "Objects to count discrete events and exchanges on BGP 3831 sessions." 3832 ::= { bgpM2MIBGroups 6 } 3834 bgpM2CapabilitiesGroup OBJECT-GROUP 3835 OBJECTS { 3836 bgpM2CapabilitySupportAvailable, 3837 bgpM2SupportedCapabilityCode, 3838 bgpM2SupportedCapability, 3839 bgpM2PeerCapAnnouncedCode, 3840 bgpM2PeerCapAnnouncedIndex, 3841 bgpM2PeerCapAnnouncedValue, 3842 bgpM2PeerCapReceivedCode, 3843 bgpM2PeerCapReceivedIndex, 3844 bgpM2PeerCapReceivedValue 3845 } 3846 STATUS current 3847 DESCRIPTION 3848 "Objects to report capabilities as received on BGP 3849 sessions." 3850 ::= { bgpM2MIBGroups 7 } 3852 bgpM2AsPathGroup OBJECT-GROUP 3853 OBJECTS { 3854 bgpM2AsPathSegmentIndex, 3855 bgpM2AsPathElementIndex, 3856 bgpM2AsPathType, 3857 bgpM2AsPathElementValue 3858 } 3859 STATUS current 3860 DESCRIPTION 3861 "Objects to report AS paths received on BGP NLRIs." 3862 ::= { bgpM2MIBGroups 8 } 3864 bgpM2As4byteGroup OBJECT-GROUP 3865 OBJECTS { 3866 bgpM2AsSize, 3867 bgpM2AsPath4bytePathPresent, 3868 bgpM2AsPath4byteAggregatorAS, 3869 bgpM2AsPath4byteCalcLength, 3870 bgpM2AsPath4byteString, 3871 bgpM2AsPath4byteIndex 3872 } 3873 STATUS current 3874 DESCRIPTION 3875 "AS Size objects." 3876 ::= { bgpM2MIBGroups 9 } 3878 bgpM2BaseGroup OBJECT-GROUP 3879 OBJECTS { 3880 bgpM2LocalAs, 3881 bgpM2LocalIdentifier, 3882 bgpM2VersionIndex, 3883 bgpM2VersionSupported 3884 } 3885 STATUS current 3886 DESCRIPTION 3887 "Basic objects in local BGP implementation." 3888 ::= { bgpM2MIBGroups 10 } 3890 bgpM2ErrorsGroup OBJECT-GROUP 3891 OBJECTS { 3892 bgpM2PeerLastErrorReceived, 3893 bgpM2PeerLastErrorReceivedData, 3894 bgpM2PeerLastErrorReceivedTime, 3895 bgpM2PeerLastErrorReceivedText, 3896 bgpM2PeerLastErrorSent, 3897 bgpM2PeerLastErrorSentData, 3898 bgpM2PeerLastErrorSentTime, 3899 bgpM2PeerLastErrorSentText 3900 } 3901 STATUS current 3902 DESCRIPTION 3903 "Errors received on BGP peering sessions." 3904 ::= { bgpM2MIBGroups 11 } 3906 bgpM2PeerGroup OBJECT-GROUP 3907 OBJECTS { 3908 bgpM2PeerInstance, 3909 bgpM2PeerIdentifier, 3910 bgpM2PeerState, 3911 bgpM2PeerStatus, 3912 bgpM2PeerConfiguredVersion, 3913 bgpM2PeerNegotiatedVersion, 3914 bgpM2PeerLocalAddrType, 3915 bgpM2PeerLocalAddr, 3916 bgpM2PeerLocalPort, 3917 bgpM2PeerLocalAs, 3918 bgpM2PeerRemoteAddrType, 3919 bgpM2PeerRemoteAddr, 3920 bgpM2PeerRemotePort, 3921 bgpM2PeerRemoteAs, 3922 bgpM2PeerIndex 3923 } 3924 STATUS current 3925 DESCRIPTION 3926 "Core object types on BGP peering sessions." 3927 ::= { bgpM2MIBGroups 12 } 3928 bgpM2PathAttributesGroup OBJECT-GROUP 3929 OBJECTS { 3930 bgpM2PathAttrCount, 3931 bgpM2AsPathCalcLength, 3932 bgpM2AsPathElementValue, 3933 bgpM2AsPathIndex, 3934 bgpM2AsPathString, 3935 bgpM2AsPathType, 3936 bgpM2NlriAfi, 3937 bgpM2NlriBest, 3938 bgpM2NlriPrefixType, 3939 bgpM2NlriPrefix, 3940 bgpM2NlriPrefixLen, 3941 bgpM2NlriSafi, 3942 bgpM2NlriOpaqueType, 3943 bgpM2NlriOpaquePointer, 3944 bgpM2NlriIndex, 3945 bgpM2NlriCalcLocalPref, 3946 bgpM2AdjRibsOutIndex, 3947 bgpM2AdjRibsOutRoute, 3948 bgpM2PathAttrAggregatorAS, 3949 bgpM2PathAttrAggregatorAddr, 3950 bgpM2PathAttrAtomicAggregate, 3951 bgpM2PathAttrIndex, 3952 bgpM2PathAttrLocalPref, 3953 bgpM2PathAttrLocalPrefPresent, 3954 bgpM2PathAttrMed, 3955 bgpM2PathAttrMedPresent, 3956 bgpM2PathAttrNextHop, 3957 bgpM2PathAttrNextHopAddrType, 3958 bgpM2PathAttrOrigin, 3959 bgpM2PathAttrUnknownIndex, 3960 bgpM2PathAttrUnknownType, 3961 bgpM2PathAttrUnknownValue 3962 } 3963 STATUS current 3964 DESCRIPTION 3965 "Attributes received on BGP peering sessions." 3966 ::= { bgpM2MIBGroups 13 } 3968 bgpM2PeerConfigurationGroup OBJECT-GROUP 3969 OBJECTS { 3970 bgpM2CfgBaseScalarStorageType, 3971 bgpM2CfgLocalAs, 3972 bgpM2CfgLocalIdentifier, 3973 bgpM2CfgPeerAdminStatus, 3974 bgpM2CfgPeerNextIndex, 3975 bgpM2CfgPeerConfiguredVersion, 3976 bgpM2CfgAllowVersionNegotiation, 3977 bgpM2CfgPeerLocalAddrType, 3978 bgpM2CfgPeerLocalAddr, 3979 bgpM2CfgPeerLocalAs, 3980 bgpM2CfgPeerRemoteAddrType, 3981 bgpM2CfgPeerRemoteAddr, 3982 bgpM2CfgPeerRemoteAs, 3983 bgpM2CfgPeerEntryStorageType, 3984 bgpM2CfgPeerError, 3985 bgpM2CfgPeerBgpPeerEntry, 3986 bgpM2CfgPeerRowEntryStatus, 3987 bgpM2CfgPeerIndex, 3988 bgpM2CfgPeerStatus, 3989 bgpM2CfgPeerConnectRetryInterval, 3990 bgpM2CfgPeerHoldTimeConfigured, 3991 bgpM2CfgPeerKeepAliveConfigured, 3992 bgpM2CfgPeerMinASOrigInterval, 3993 bgpM2CfgPeerMinRouteAdverInter 3994 } 3995 STATUS current 3996 DESCRIPTION 3997 "Configuration objects for BGP peers." 3998 ::= { bgpM2MIBGroups 14 } 4000 bgpM2PeerRouteReflectorCfgGroup OBJECT-GROUP 4001 OBJECTS { 4002 bgpM2CfgRouteReflector, 4003 bgpM2CfgClusterId, 4004 bgpM2CfgPeerReflectorClient 4005 } 4006 STATUS current 4007 DESCRIPTION 4008 "Configuration objects for BGP peers that support route 4009 reflection." 4010 ::= { bgpM2MIBGroups 15 } 4012 bgpM2PeerAsConfederationCfgGroup OBJECT-GROUP 4013 OBJECTS { 4014 bgpM2CfgConfederationRouter, 4015 bgpM2CfgConfederationId, 4016 bgpM2CfgPeerConfedMember 4017 } 4018 STATUS current 4019 DESCRIPTION 4020 "Configuration objects for BGP peers that support BGP 4021 confederations." 4022 ::= { bgpM2MIBGroups 16 } 4024 bgpM2MIBNotificationsGroup NOTIFICATION-GROUP 4025 NOTIFICATIONS { 4026 bgpM2Established, 4027 bgpM2BackwardTransition 4028 } 4029 STATUS current 4030 DESCRIPTION 4031 "This group contains objects for notifications 4032 supported by this mib module." 4033 ::= { bgpM2MIBGroups 17 } 4035 bgpM2Rfc2545Group OBJECT-GROUP 4036 OBJECTS { 4037 bgpM2LinkLocalNextHopPresent, 4038 bgpM2LinkLocalNextHop 4039 } 4040 STATUS current 4041 DESCRIPTION 4042 "This group is required for peers that support exchanging 4043 of IPv6 NLRI per RFC 2545." 4044 ::= { bgpM2MIBGroups 18 } 4046 END 4048 5. Intellectual Property Rights 4050 The IETF takes no position regarding the validity or scope of any 4051 intellectual property or other rights that might be claimed to per- 4052 tain to the implementation or use of the technology described in this 4053 document or the extent to which any license under such rights might 4054 or might not be available; neither does it represent that it has made 4055 any effort to identify any such rights. Information on the IETF's 4056 procedures with respect to rights in standards-track and standards- 4057 related documentation can be found in BCP-11. Copies of claims of 4058 rights made available for publication and any assurances of licenses 4059 to be made available, or the result of an attempt made to obtain a 4060 general license or permission for the use of such proprietary rights 4061 by implementors or users of this specification can be obtained from 4062 the IETF Secretariat. 4064 The IETF invites any interested party to bring to its attention any 4065 copyrights, patents or patent applications, or other proprietary 4066 rights which may cover technology that may be required to practice 4067 this standard. Please address the information to the IETF Executive 4068 Director. 4070 6. Security Considerations 4072 This MIB relates to a system providing inter-domain routing. As 4073 such, improper manipulation of the objects represented by this MIB 4074 may result in denial of service to a large number of end-users. 4076 There are several management objects defined in this MIB that have a 4077 MAX-ACCESS clause of read-write and/or read-create. Such objects 4078 should be considered sensitive or vulnerable in most network environ- 4079 ments. The support for SET operations in a non-secure environment 4080 without proper protection can have a negative effect on network oper- 4081 ations. These objects include: 4083 XXX TODO 4085 There are a number of managed objects in this MIB that con- 4086 tain sensitive information regarding the operation of a network. For 4087 example, a BGP peer's local and remote addresses might be sensitive 4088 for ISPs who want to keep interface addresses on routers confiden- 4089 tial to prevent router addresses used for a denial of service attack 4090 or spoofing. 4092 Therefore, it is important in most environments to control read 4093 access to these objects and possibly to even encrypt the values of 4094 these object when sending them over the network via SNMP. 4096 SNMPv1 by itself is not a secure environment. Even if the network 4097 itself is secure (for example by using IPSec), there is still no con- 4098 trol as to who on the secure network is allowed to access and GET/SET 4099 (read/change/create/delete) the objects in this MIB. 4101 It is recommended that the implementers consider the security fea- 4102 tures as provided by the SNMPv3 framework.[REF] Specifically, the 4103 implementation and use of the User-based Security Model [REF] and the 4104 View-based Access Control Model [REF] is recommended to provide 4105 appropriate security controls. 4107 It is then an operator/user responsibility to ensure that the SNMP 4108 entity giving access to an instance of this MIB, is properly config- 4109 ured to give access to the objects only to those principals (users) 4110 that have legitimate rights to indeed GET or SET (change/cre- 4111 ate/delete) them. 4113 7. Acknowledgements 4115 Tom Nadeau, Cisco Systems, Inc. 4116 Jon Saperia, JDS Consulting, Inc. 4117 Bill Fenner, AT&T Research 4118 Mike McFaden, Riverstone Networks, Inc. 4119 Joel Krauska, Exodus Communications, Inc. 4120 Carl W. Kalbfleisch, Verio Networks, Inc. 4121 Joe Dupre, Gold Wire Technology 4123 others TBD... 4125 8. Changes From Last Version 4127 This section is used to track changes from version to version of this 4128 document. This section will be removed from the document prior to 4129 being issued to IDR working group last call. 4131 * Changes from draft-ietf-idr-bgp4-mibv2-03.txt to draft-ietf- 4132 idr-bgp4-mibv2-04.txt (12 January 2004) 4134 Remove all objects related to BGP authentication as BGP 4135 authentication has been officially removed. 4137 Removed bgpM2AsPathElementValue from bgpM2AsPathTable 4139 Add current OPS group MIB boilerplate and security boiler- 4140 plate. Work still needs to be done in the security section. 4142 Split references into Normative References and Informational 4143 References. Add IETF Intellectual Property Rights statement. 4144 Update copyright dates. 4146 Add new TEXTUAL-CONVENTION, BgpM2Afi to more properly reflect 4147 BGP Multi-Protocol Extensions. 4149 Add bgpM2NlriPrefixType to bgpM2NlriTable as an interim mecha- 4150 nism to support "proper" translation of an AFI to an InetAd- 4151 dressType. Further thought must be put into this. 4153 Delete bgpM2CfgPeerRemotePort object. Deployed implementa- 4154 tions do not seem to allow this to be configured. 4156 Add bgpM2PeerInstance to permit multiple BGP routing instances 4157 to be supported. 4159 Renumber numerous OIDs to account for re-organizing objects. 4160 Update conformance statements to match. 4162 * Changes from draft-ietf-idr-bgp4-mibv2-02.txt to draft-ietf- 4163 idr-bgp4-mibv2-03.txt (4 November 2002): 4165 Changed the order of the bgpM2NlriPrefixLen and 4166 bgpM2NlriPrefix objects and renumbered them. This was to make 4167 it consistant with user expectations. 4169 Clarify the peer table description text to specify the remote 4170 peer. 4172 Use SnmpAdminString instead of DisplayString. 4174 Correct TEXTUAL CONVENTION for extended communities. 4176 Changed enumerations of bgpM2PathATtrAtomicAggregate. 4178 Added link local table for RFC 2545 nexthops. 4180 * Changes from draft-ietf-idr-bgp4-mibv2-01.txt to draft-ietf- 4181 idr-bgp4-mibv2-02.txt (28 February 2002) 4183 Lots of changes in this rewrite, these are the most dramatic: 4185 Configuration objects and tables added. 4187 All references to 'bgp' in object descriptors changed to 4188 'bgpM2' to disambiguate from RFC 1657 and its OBSOLETing MIB. 4190 Community Textual conventions added to beginning of MIB. 4192 bgpM2CalcLength and PathString columns added to bgpM2PathAttr 4193 table. 4195 Creation of separate bgpM2AdjRibsOutTable. 4197 Appearance of NLRI table notions such as 'opaque type'. 4199 Overhaul of specification of AS Path types to accommodate eas- 4200 ier management at time of route aggregation. 4202 9. Normative References 4204 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 4205 (USM) for version 3 of the Simple Network Management 4206 Protocol (SNMPv3)", RFC 2574, April 1999. 4208 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 4209 Rose, M., and S. Waldbusser, "Structure of Management Infor- 4210 mation Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 4212 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 4213 Rose, M., and S. Waldbusser, "Textual Conventions for 4214 SMIv2", STD 58, RFC 2579, April 1999. 4216 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 4217 Rose, M., and S. Waldbusser, "Conformance Statements for 4218 SMIv2", STD 58, RFC 2580, April 1999. 4220 [RFC3411] D. Harrington, R. Presuhn, B. Wijnen, "An Architecture for 4221 Describing Simple Network Management Protocol (SNMP) Manage- 4222 ment Frameworks", RFC 3411, December 2002. 4224 [RFC3413] D. Levi, P. Meyer, B. Stewart, "Simple Network Management 4225 Protocol (SNMP) Applications", RFC 3413, December 2002. 4227 [RFC3415] B. Wijnen, R. Presuhn, K. McCloghrie, "View-based Access 4228 Control Model (VACM) for the Simple Network Management Pro- 4229 tocol (SNMP)", RFC 3415, December 2002. 4231 [RFC3416] Presuhn, R., Editor, "Version 2 of the Protool Operations 4232 for the Simple Network Management Protocol (SNMP)", RFC 4233 3416, December 2002. 4235 [RFC3417] Presuhn, R., Editor, "Transport Mappings for the Simple Net- 4236 work Management Protocol (SNMP)", RFC 3417, December 2002. 4238 [RFC1213] McCloghrie, K. and M. Rose, Editors, "Management Information 4239 Base for Network Management of TCP/IP-based Internets: MIB- 4240 II", STD 17, RFC 1213, Hughes LAN Systems, Performance Sys- 4241 tems International, March 1991. 4243 [RFC1657] Willis, S., Burruss, J., and Chu, J., "Definitions of Man- 4244 aged Objects for the Fourth Version of the Border Gateway 4245 Protocol (BGP-4) using SMIv2", RFC 1657, July 1994. 4247 [MIB-DRAFT] Hares, S., Haas, J., Willis, S., Burruss, J., and Chu, J., 4248 "Definitions of Managed Objects for the Fourth Version of 4249 Border Gateway Protocol (BGP-4)", draft-ietf-idr- 4250 bgp4-mib-06.txt, Work-in-progress. 4252 [RFC1771] Rekhter, Y., Li, T., "A Border Gateway Protocol 4 (BGP-4)", 4253 RFC 1771, March 1995. 4255 [RFC1772] Rekhter, Y., Gross, P., "Application of the Border Gateway 4256 Protocol in the Internet", RFC 1772, March 1995. 4258 [RFC3065] Traina, P., McPherson, D., and Scudder, J., "Autonomous Sys- 4259 tem Confederations for BGP", RFC 3065, February, 2001. 4261 [RFC1997] Chandra, R., Traina, P., and Li, T., "BGP Communities 4262 Attribute", RFC 1997, August, 1996. 4264 [RFC2858] Bates, T., Rekhter, Y., Chandra, R., and Katz, D., "Multi- 4265 protocol Extensions for BGP-4", RFC 2858, June, 2000. 4267 [RFC2796] Bates, T., Chandra, R., and Chen, E., "BGP Route Reflection 4268 - An Alternative to Full Mesh IBGP", RFC 2796, April 2000. 4270 [BGP-EXTCOMM] Sangli, S., Tappan, D., and Rekhter, Y., "BGP Extended 4271 Communities Attribute", Work-in-progress. 4273 [RFC3107] Rehkter, Y., and Rosen, E., "Carrying Label Information in 4274 BGP-4", RFC 3107, May 2001. 4276 10. Informative References 4278 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 4279 "Introduction to Community-based SNMPv2", RFC 1901, January 4280 1996. 4282 [RFC2576] Frye, R., Levi, D., Routhier, S. and B. Wijnen, "Coexistence 4283 between Version 1, Version 2, and Version 3 of the Internet- 4284 Standard Network Management Framework", RFC 2576, March 4285 2000. 4287 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduc- 4288 tion and Applicability Statements for Internet- Standard 4289 Management Framework", RFC 3410, December 2002. 4291 11. Authors' Addresses 4293 Jeff Haas 4294 NextHop Technologies 4295 825 Victors Way, Suite 100 4296 Ann Arbor, MI 48108 4297 Phone: +1 734 222-1600 4298 Fax: +1 734 222-1602 4299 Email: jhaas@nexthop.com 4300 Susan Hares 4301 NextHop Technologies 4302 825 Victors Way, Suite 100 4303 Ann Arbor, MI 48108 4304 Phone: +1 734 222-1600 4305 Fax: +1 734 222-1602 4306 Email: skh@nexthop.com 4308 Wayne Tackabury 4309 Gold Wire Technology 4310 411 Waverley Oaks Rd. 4311 Waltham, MA 02452-8401 4312 Phone: +1 781 398-8819 4313 Fax: +1 781 398-8811 4314 Email: wayne@goldwiretech.com 4316 12. Full Copyright Statement 4318 Copyright (C) The Internet Society (2004). All Rights Reserved. 4320 This document and translations of it may be copied and furnished to 4321 others, and derivative works that comment on or otherwise explain it 4322 or assist in its implementation may be prepared, copied, published 4323 and distributed, in whole or in part, without restriction of any 4324 kind, provided that the above copyright notice and this paragraph are 4325 included on all such copies and derivative works. However, this doc- 4326 ument itself may not be modified in any way, such as by removing the 4327 copyright notice or references to the Internet Society or other 4328 Internet organizations, except as needed for the purpose of develop- 4329 ing Internet standards in which case the procedures for copyrights 4330 defined in the Internet Standards process must be followed, or as 4331 required to translate it into languages other than English. 4333 The limited permissions granted above are perpetual and will not be 4334 revoked by the Internet Society or its successors or assigns. 4336 This document and the information contained herein is provided on an 4337 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 4338 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 4339 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 4340 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MER- 4341 CHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 4343 Table of Contents 4345 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2 4346 2. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 4347 2.1. Protocol Extensions . . . . . . . . . . . . . . . . . . . . . . 2 4348 2.2. Mechanisms for MIB Extensibility . . . . . . . . . . . . . . . 3 4349 2.3. BGP Configuration . . . . . . . . . . . . . . . . . . . . . . . 3 4350 3. MIB Organization . . . . . . . . . . . . . . . . . . . . . . . . 3 4351 3.1. bgpM2BaseScalars . . . . . . . . . . . . . . . . . . . . . . . 4 4352 3.2. bgpM2PeerData . . . . . . . . . . . . . . . . . . . . . . . . . 5 4353 3.2.1. bgpM2PeerCapabilities . . . . . . . . . . . . . . . . . . . . 5 4354 3.2.2. bgpM2PeerCounters . . . . . . . . . . . . . . . . . . . . . . 6 4355 3.2.3. Peering Data Extensions . . . . . . . . . . . . . . . . . . . 6 4356 3.2.4. Configuring Peering Sessions . . . . . . . . . . . . . . . . 6 4357 3.3. BGP Routing Information Base Data . . . . . . . . . . . . . . . 7 4358 3.3.1. Routing Information Base Extensions . . . . . . . . . . . . . 8 4359 3.4. Considerations on Table Indexing . . . . . . . . . . . . . . . 8 4360 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4361 5. Intellectual Property Rights . . . . . . . . . . . . . . . . . . 91 4362 6. Security Considerations . . . . . . . . . . . . . . . . . . . . . 92 4363 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 93 4364 8. Changes From Last Version . . . . . . . . . . . . . . . . . . . . 93 4365 9. Normative References . . . . . . . . . . . . . . . . . . . . . . 94 4366 10. Informative References . . . . . . . . . . . . . . . . . . . . . 96 4367 11. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 96 4368 12. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 97