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