idnits 2.17.1 draft-ietf-idr-bgp4-mibv2-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document is more than 15 pages and seems to lack a Table of Contents. == No 'Intended status' indicated for this document; assuming Proposed Standard 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.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 6 instances of too long lines in the document, the longest one being 3 characters in excess of 72. == 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 3198: '...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 262 has weird spacing: '...ient of the l...' == Line 370 has weird spacing: '...mmTable conta...' == Line 1219 has weird spacing: '... on the sessi...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (November 4, 2002) is 7843 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) -- Looks like a reference, but probably isn't: 'RFC2796' on line 3704 == Unused Reference: '15' is defined on line 4448, but no explicit reference was found in the text == Unused Reference: '20' is defined on line 4469, but no explicit reference was found in the text == Unused Reference: '22' is defined on line 4475, but no explicit reference was found in the text == Unused Reference: '23' is defined on line 4478, but no explicit reference was found in the text == Unused Reference: '25' is defined on line 4484, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (ref. '1') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (ref. '11') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. '12') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (ref. '14') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. '15') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 1657 (ref. '17') (Obsoleted by RFC 4273) == Outdated reference: A later version (-15) exists of draft-ietf-idr-bgp4-mib-06 ** Obsolete normative reference: RFC 1771 (ref. '19') (Obsoleted by RFC 4271) ** Obsolete normative reference: RFC 3065 (ref. '21') (Obsoleted by RFC 5065) -- Possible downref: Non-RFC (?) normative reference: ref. '23' ** Obsolete normative reference: RFC 2796 (ref. '24') (Obsoleted by RFC 4456) -- Possible downref: Non-RFC (?) normative reference: ref. '25' ** Obsolete normative reference: RFC 3107 (ref. '26') (Obsoleted by RFC 8277) Summary: 22 errors (**), 0 flaws (~~), 12 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Inter-Domain Routing Working Group J. Haas 3 Internet Draft NextHop 4 S. Hares 5 NextHop 6 W. Tackabury 7 Gold Wire Technology 9 November 4, 2002 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 Copyright Notice 39 Copyright (C) The Internet Society (2002). All Rights Reserved. 41 Abstract 43 This memo defines a portion of the Management Information Base (MIB) 44 for use with network management protocols in TCP/IP-based internets. 45 In particular, this MIB defines objects that facilitate the 46 management of the Border Gateway Protocol Version 4 (BGP4). 48 Distribution of this memo is unlimited. 50 1. Introduction 52 This memo defines a portion of the Management Information Base (MIB) 53 for use with network management protocols in the Internet community. 54 In particular, it describes managed objects used for managing the 55 Border Gateway Protocol Version 4. 57 The SNMP Management Framework presently consists of five major compo- 58 nents: 60 o An overall architecture, described in RFC 2571 [1]. 62 o Mechanisms for describing and naming objects and events for 63 the purpose of management. The first version of this Structure 64 of Management Information (SMI) is called SMIv1 and described 65 in STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 66 [4]. The second version, called SMIv2, is described in STD 58, 67 RFC 2578 [5], RFC 2579 [6] and RFC 2580 [7]. 69 o Message protocols for transferring management information. The 70 first version of the SNMP message protocol is called SNMPv1 71 and described in STD 15, RFC 1157 [8]. A second version of the 72 SNMP message protocol, which is not an Internet standards 73 track protocol, is called SNMPv2c and described in RFC 1901 74 [9] and RFC 1906 [10]. The third version of the message proto- 75 col is called SNMPv3 and described in RFC 1906 [10], RFC 2572 76 [11] and RFC 2574 [12]. 78 o Protocol operations for accessing management information. The 79 first set of protocol operations and associated PDU formats is 80 described in STD 15, RFC 1157 [8]. A second set of protocol 81 operations and associated PDU formats is described in RFC 1905 82 [13]. 84 o A set of fundamental applications described in RFC 2573 [14] 86 Managed objects are accessed via a virtual information store, termed 87 the Management Information Base or MIB. Objects in the MIB are 88 defined using the mechanisms defined in the SMI. 90 2. Objectives 92 This MIB Module is meant to broadly update and replace a prior MIB 93 Module defined in RFC 1657 [12]. Additionally, there is another 94 effort underway to address very specific limited objectives in updat- 95 ing points in the RFC 1657 object definition and managed object 96 attributes [13]. The MIB Module described herein is intended to 97 fully serve the functions and scope of RFC 1657 and these RFC 1657 98 updates. 100 2.1. Protocol Extensions 102 Additionally, however, there are a number of ways in which the BGP 103 Protocol has been enhanced through its ability for added capabili- 104 ties. Implementations of those capabilities have not been able to 105 have any management capabilities present in RFC 1657-compliant MIB 106 module agents, since the capabilities themselves postdated the adop- 107 tion of RFC 1657. For several significant capabilities, in the form 108 of BGP Communities [17], Autonomous System Confederation [16] , BGP 109 Multiprotocol Extensions [18], and Route Reflection [19], the MIB 110 Module defined in this document exposes object types to manage those 111 extended capabilities and their operation. 113 One of these extensions in particular (the multiprotocol extensions) 114 requires a thorough redefinition of MIB table row indices from the 115 RFC 1657 state. This allows transport-independent address indices 116 consistent with the Address Family Identifier (AFI) and Subsequent 117 Address Family Identifier (SAFI) mechanisms of that extension. 119 2.2. Mechanisms for MIB Extensibility 121 Moreover, the requirement for the incremental update of support for 122 capabilities such as these begs the issue of placing modular extensi- 123 bility for protocol extensions within the framework of the MIB 124 itself. Going forward, it would be very desirable to have attributes 125 of the MIB structure, and administrative procedures, to allow the 126 incremental update of the MIB scope to cover any such new protocol 127 extensions, without requiring a reissue of the entire MIB. In this 128 sense, we seek to structure the MIB much like the underlying BGP4 129 itself, allowing capability-by-capability update. 131 2.3. BGP Configuration 133 Finally, the definition and adoption of Version 3 of the SNMP has 134 occurred since the adoption of the RFC 1657 MIB. As a result, the 135 ability to deploy secure configuration of managed elements via SNMP 136 in a standardized way has become a reality for managed networks. In 137 this MIB definition effort, we seek to expose a more thorough capac- 138 ity for configuration of BGP4 and its capabilities than was present 139 in RFC 1657 or than was common practice at the time of its adoption. 141 3. MIB Organization 143 The MIB is broken down into several top level sections. This sec- 144 tionalization is important to create an organization for extensibil- 145 ity. 147 In general, a top level section of the MIB module will identify some 148 number of "core" scalar and tabular objects rooted off of it. If 149 there is sufficient depth within a subsection of one of these top- 150 level sections, the "core" subdivision off of the top level section 151 may provide multiple levels to the OBJECT IDENTIFIER scope necessary 152 to define its management data. 154 Once this core section is defined, however, each top-level section 155 has an explicit provision for an 'extensions' section OBJECT IDENTI- 156 FIER. The intent of the extensions section is to be containment for 157 discrete per-extension sections. By 'extension' here, we refer to 158 protocol mechanisms, capabilities, and exchanges which are not 159 defined in the base Border Gateway Protocol definition, or is not 160 configuration for protocol operations of similarly 'core' status. 161 Currently, we propose keying the identification within the per-exten- 162 sion section in one of two ways. 164 Where the extension is keyed to a defined capability which has an 165 associated BGP capability number assigned by IANA (for example, mul- 166 tiprotocol BGP extensions), the per extension section will be that 167 defined IANA capability number. Where the extension has management 168 information suitable for a MIB extension but does not correspond to 169 an exchanged protocol capability (for example, BGP Route Reflection), 170 the extension section shall have its final OBJECT IDENTIFIER fragment 171 correspond to the RFC number which first uniquely defined the exten- 172 sion (i.e., not requiring renumbering at the time a defining RFC for 173 a protocol mechanism is outdated by a later RFC). 175 3.1. bgpM2BaseScalars 177 The bgpM2BaseScalars section (and corresponding OBJECT IDENTIFIER) is 178 used to delineate object types used for basic management and monitor- 179 ing of the protocol implementation. These are core parameters for 180 the local configuration. While notifications are designed to be 181 extensible into any other section in the MIB module, the currently 182 defined traps are located here, in a subsection 'bgpM2BaseNotifica- 183 tions'. This is rooted at index level zero (0) here, owing to con- 184 ventions established in [4]. 186 Support for multiple concurrently supported versions of BGP is 187 exposed through the entries of the bgpM2VersionTable. Similarly, 188 support for multiple capabilities and authentication mechanisms, as 189 identified by their assigned numbers, are reported in the bgpM2Sup- 190 portedCapabilitiesTable and bgpM2SupportedAuthTable respectively. 192 In the MIB document, there are currently scalar extension mechanisms 193 to allow the agent to report membership of a local BGP Confederation 194 [21] or Route Reflection Cluster ID [24], as well as whether these 195 capabilities are in fact supported by the implementation. These are 196 consistent with the non-capability based extension section indexing 197 guidelines as presented above. 199 bgpM2BaseScalars also is the root for a subsection, bgpM2BaseScalar- 200 Configuration, which contains the companion configuration objects for 201 the base scalar objects delineated in the preceding paragraphs. 202 These are presented as a series of scalar read-write objects, with a 203 single OBJECT-TYPE of syntax StorageType to designate the persistence 204 of the instance value data for these configuration scalars. 206 3.2. bgpM2PeerData 208 The bgpM2PeerData section is per-peer object type definitions. The 209 predominant table of read-only STATUS object types in that section 210 (bgpM2PeerTable) describes the session, negotiation state, and 211 authentication state on a per peer basis. A second table (bgpM2Pre- 212 fixCountersTable) exposes information about individual route prefixes 213 received over each peer session. A separate subsection and its sub- 214 ordinate table (bgpM2PeerErrorsTable) reports information about the 215 last error encountered on a given peering session. 217 Further subsections report authentication state with the peer, peer- 218 ing session detected errors, and elapsed time it has taken to 219 advance the peering session into various states defined in the proto- 220 col FSM. 222 The bgpM2PeerConfiguredTimersTable reports and allows dynamic reset 223 of key timers on the peer session. These currently allow reset of 224 hold time and keepalive timer, for compatibility with the same capa- 225 bilities in RFC 1657 [17]. For these resettable timers, their end-to- 226 end negotiated current values are reflected in the bgpM2PeerNegotiat- 227 edTimersTable. 229 As currently defined, these tables describing authentication, error 230 state, and timer values (in addition to the configuration tables for 231 session timers) are tightly coupled enough to the logical per-row 232 view exposed in the bgpM2PeerTable row entries on a session that 233 these subordinate "tables" are defined as AUGMENTing the 234 bgpM2PeerTable itself. The other primary design criterion behind 235 this decision is that using this AUGMENTation does not increase the 236 per-row-data requirements of bgpM2PeerTable instance retrieval so as 237 to make such per-row retrieval unwieldy for the management applica- 238 tion. 240 3.2.1. bgpM2PeerCapabilities 242 bgpM2PeerCapabilitiesData has objects and tables to describe BGP 243 capabilities locally supported, and those reported and negotiated 244 over each peer session. For tables supporting each of these capa- 245 bility sets, capability code and data value are provided. Attention 246 must be given to the fact that multiple instances of a given capabil- 247 ity can be transmitted between BGP speakers. 249 3.2.2. bgpM2PeerCounters 251 The bgpM2CountersTable and bgpM2PrefixCountersTable report protocol 252 exchanges/FSM transitions, and discrete number of NLRIs exchanged per 253 peering session, respectively. This is independent of actual 254 exchanged path attributes, which are tabularized later in the MIB 255 module. Note that session transitions as reflected in changes of 256 instances within this table may also be reflected in issuance of 257 bgpM2Established and bgpM2BackwardTransition NOTIFICATION-TYPE PDUs. 259 3.2.3. Peering Data Extensions 261 Route reflector status on a per-peer basis (whether the peer is a 262 client or nonClient of the local BGP router's reflected route propa- 263 gation), and peer confederation membership is reported in non capa- 264 bility extensions of the peering data section. 266 3.2.4. Configuring Peering Sessions 268 The MIB has several tables indexed on a per-peer level of granularity 269 to control creation and activation of new peering sessions, and to 270 allow control on running sessions (those reflected in bgpM2PeerTable 271 row instances) regardless of what caused their creation in the BGP 272 routing process. 274 The bgpM2CfgPeerAdminStatusTable allows creation and specification of 275 a row by a bgpM2PeerIndex value (which is how its associated row 276 instance is identified in the bgpM2PeerTable). For each such row 277 instance, the set of the bgpM2CfgPeerAdminStatus OBJECT-TYPE of MAX- 278 ACCESS read-write can allow management application start and stop of 279 the session. 281 This is contrasted with the function of the bgpM2CfgPeerTable, and 282 its related AUGMENTed tables bgpM2CfgPeerTimersTable and bgpM2Cfg- 283 PeerAuthTable. These are used to facilitate direct creation of peer- 284 ing sessions by the management application. The function of columnar 285 OBJECT-TYPEs within the bgpM2CfgPeerTable for local and remote 286 address, version negotiation, and various row-administrative 287 attributes (RowStatus and StorageType SYNTAXes) are straightforward 288 enough. The only subtlety with respect to how peering sessions are 289 activated from usage of this table, and how the activated sessions 290 are reflected through their bgpM2PeerTable and bgpM2CfgPeerAdminSta- 291 tusTable entries, is in the usage of the bgpM2CfgPeerTable columnar 292 object bgpM2CfgPeerStatus. bgpM2CfgPeerStatus can take on two val- 293 ues. When a peering session, as reflected through its row instance 294 in the bgpM2CfgPeerTable, has the bgpM2CfgPeerStatus instance value 295 in that row set to running(2) at the time of the SYNTAX RowStatus 296 object instance of bgpM2CfgPeerRowEntryStatus set to active(1), the 297 peering session will in fact be activated in the BGP routing process 298 (in addition to having its row instance created in the bgpM2Cfg- 299 PeerTable and bgpM2CfgPeerAdminStatusTable). In this case, the asso- 300 ciated row of the bgpM2CfgPeerAdminStatusTable row bgpM2CfgPeerAdmin- 301 Status instance would have the value of start(2). If, in the prior 302 example, the bgpM2CfgPeerStatus is halted(1) at the time of the 303 bgpM2CfgPeerRowEntryStatus instance set to active(1), only the peer- 304 ing table entries would be created at this time of activation, with- 305 out the peering session being automatically started. The bgpM2Cfg- 306 PeerAdminStatusTable row bgpM2CfgPeerAdminStatus instance associated 307 with the session would in this case reflect a value of stop(1). 309 Since the row entries of the per-peer configuration tables which AUG- 310 MENT the bgpM2CfgPeerTable logically fate-share the row instances in 311 the bgpM2CfgPeerTable which they are AUGMENTing, they also share the 312 same StorageType and RowStatus SYNTAX object sense of the 313 bgpM2CfgPeerTable rows which they augment. 315 3.3. BGP Routing Information Base Data 317 An important table for providing index information for other tables 318 in the MIB module is the bgpM2NlriTable. This discriminates on a 319 given network prefix (by AFI/SAFI), and the peer which advertised the 320 prefix (since it can be heard of from multiple speakers). The 321 bgpM2PathAttrIndex column which identifies each row in this table is 322 used as an index for other per-attribute tables through the remainder 323 of the MIB module. 325 RFC 3107 [26] specifies a capability for exchanged routes between BGP 326 peers to attach attribute information to a route indicating, specifi- 327 cally, related MPLS label path information. The MIB supports the 328 presentation of this attribute information by generalizing how these 329 attributes are presented to accommodate further extensions of this 330 particular type. Within a given bgpM2NlriTable entry, we speak of 331 attribute data of this type as being 'opaque' to BGP, and use the 332 columnar OBJECT-TYPEs bgpM2NlriOpaqueType and bgpM2NlriOpaquePointer 333 to refer to it. In the case of the RFC 3107 MPLS label encoding 334 (which is the only usage of these columnar fields in the bgpM2NlriTa- 335 ble right now), a MPLS label stack would be referenced by bgpM2Nlri- 336 OpaquePointer by its per-NLRI instance pointing to a row instance in 337 the MPLS LSR MIB mplsLabelStackTable, and the bgpM2NlriOpaqueType 338 instance having a value of bgpMplsLabelStack(1). 340 The bgpM2AdjRibsOutTable row entries reflect data on routes which 341 have been placed, per peering session, in the Adj-Rib-Out for adver- 342 tisement to the associated peer. 344 The bgpM2PathAttrTable provides discrete BGP NLRI attributes which 345 were received with the advertisement of the prefix by its advertising 346 peer. Specific information about the autonomous system path (AS 347 Path) advertised with the NLRI, on a per AS value, is to be found in 348 the bgpM2AsPathTable. 350 Finally, where attributes which were unable to be reported in the 351 bgpM2PathAttrTable, the AS Path table, or any defined per-NLRI tables 352 in the agent were received with the prefix, those attributes are 353 reported via the bgpM2PathAttrUnknownTable. Short of advertised 354 attribute type, no semantic breakdown of the unknown attribute data 355 is provided. That data is only available as a raw OCTET STRING in 356 the bgpM2PathAttrUnknownValue column of this table. 358 3.3.1. Routing Information Base Extensions 360 There are two extension sections and five subordinate tables to the 361 bgpM2PathAttrTable and RIB data OBJECT IDENTIFIER-delimited MIB mod- 362 ule section. The bgpM2PathAttrRouteReflectionExts and its contained 363 bgpM2PathAttrOriginatorIdTable report on the originating route 364 reflector. The bgpM2PathAttrClusterTable specifically reports on the 365 reflection route a NLRI has traversed to get to the local BGP routing 366 process. 368 The bgpM2PathAttrCommunityExts section deals with extended and non- 369 extended communities for network routes. The bgpM2PathAttrCommTable 370 bgpM2PathAttrExtCommTable contained herein report community member- 371 ship (if any) on a per network-prefix basis. 373 3.4. Consideration On Table Indexing 375 There are certain efficiency concerns for row index management for 376 management applications which are useful to take into consideration, 377 given the nature of some of the tables implied in the preceding sec- 378 tion. 380 In the first place, it is valuable to exploit the direct relationship 381 of entries in, for example, the bgpM2PrefixCountersTable as they 382 relate to the entry in the bgpM2PeerTable to which they are related. 383 More compelling is the example case of the one-to-many relationship 384 between a row entry in the bgpM2PeerTable and the bgpM2PathAttrTable, 385 the latter of which maintains per-row entries for potentially many 386 NLRIs as received from a peer in a BGP UPDATE message. From the 387 point of view of normalizing these relationships, it would be useful 388 to have a direct reference to the "governing" bgpM2PeerTable row 389 entry for the peer which is a "dependency" for the subordinate table 390 row entry for other peer data. 392 Second, the nature of protocol-independent addressing makes the 393 indexing of these entries indirectly even more compelling. Even 394 accounting for the addressing requirements of IPv6 and the provision 395 of AFI and SAFI qualifiers, the logical addressing of a row in the 396 bgpPathAttrClusterTable (for example) would extend out some 50 bytes 397 if there was no direct index linkage to the "governing" bgpPathAt- 398 trTable, and bgpPeerTable entries. 400 For this reason, the tables are structured in such a way that, where 401 there is such a linkage to a "dependent" table (where, for example, 402 the bgpPrefixCountersTable "depends on" the bgpPeerTable), a table 403 will contain a per-row numeric index (e.g., bgpPeerIndex), which the 404 "dependent" table will use as one of its own row index values. These 405 indices are manufactured by the agent, and are otherwise opaque to 406 the management application (or, for that matter, even to the organi- 407 zation of the "dependent" table[s]). 409 Where considerations of per-row retrieval overhead (in terms of typi- 410 cal row instance data size, as a function of liability to have a sin- 411 gle row retrieval exceed PDU size, for example), and those of general 412 logical data organization permit, certain tables logically at the 413 sub-peering-session level have been specified as AUGMENTing the pri- 414 mary tables (bgpM2PeerTable and bgpM2CfgPeerTable) to which those 415 sub-peering-session row entries relate. This is to facilitate ease 416 on the part of a management application of assembling (for example, 417 via GET-BULK operations across a lexicographically contiguous row 418 scope) a management image of control information on a given peering 419 session. 421 1. 423 BGP4-V2-MIB DEFINITIONS ::= BEGIN 425 IMPORTS 426 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 427 Counter32, Gauge32, mib-2, Unsigned32, Integer32 428 FROM SNMPv2-SMI 429 -- Note that the following reference to INET-ADDRESS-MIB 430 -- refers to the version as published in the RFC 2851 431 -- update internet draft. 432 InetAddressType, InetAddress, InetPortNumber, 433 InetAutonomousSystemNumber, InetAddressPrefixLength 434 FROM INET-ADDRESS-MIB 435 TEXTUAL-CONVENTION, TruthValue, RowPointer, StorageType, 436 RowStatus 437 FROM SNMPv2-TC 438 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 439 FROM SNMPv2-CONF 440 SnmpAdminString 441 FROM SNMP-FRAMEWORK-MIB; 443 bgpM2 MODULE-IDENTITY 444 LAST-UPDATED "200211040000Z" 445 ORGANIZATION "IETF IDR Working Group" 446 CONTACT-INFO "E-mail: idr@merit.net 448 Jeffrey Haas (Editor) 449 825 Victors Way, Suite 100 450 Ann Arbor, MI 48108 451 Tel: +1 734 222-1600 452 Fax: +1 734 222-1602 453 E-mail: jhaas@nexthop.com" 455 DESCRIPTION 456 "This MIB module defines management objects for 457 the Border Gateway Protocol, Version 4." 458 ::= { mib-2 XXX } 460 BgpM2Identifier ::= TEXTUAL-CONVENTION 461 DISPLAY-HINT "1d." 462 STATUS current 463 DESCRIPTION 464 "The representation of a BGP Identifier. The BGP 465 Identifier should be represented in the OCTET STRING 466 as with the first OCTET of the string containing 467 the first OCTET of the BGP Identifier received or sent 468 in the OPEN packet and so on. 470 Even though the BGP Identifier is trending away from 471 an IP address it is still displayed as if it was one, 472 even when it would be an illegal IP address." 473 SYNTAX OCTET STRING(SIZE (4)) 475 BgpM2Safi ::= TEXTUAL-CONVENTION 476 DISPLAY-HINT "d" 477 STATUS current 478 DESCRIPTION 479 "The representation of a BGP Safi" 480 SYNTAX Unsigned32(0..255) 482 BgpM2Community ::= TEXTUAL-CONVENTION 483 DISPLAY-HINT "2d:" 484 STATUS current 485 DESCRIPTION 486 "The representation of a BGP Community." 487 SYNTAX OCTET STRING(SIZE(4)) 489 BgpM2ExtendedCommunity ::= TEXTUAL-CONVENTION 490 DISPLAY-HINT "1x:" 491 STATUS current 492 DESCRIPTION 493 "The representation of a BGP Extended Community." 494 SYNTAX OCTET STRING(SIZE(8)) 496 bgpM2BaseScalars 497 OBJECT IDENTIFIER ::= { bgpM2 1 } 499 -- 500 -- Notifications 501 -- 503 bgpM2BaseNotifications 504 OBJECT IDENTIFIER ::= { bgpM2BaseScalars 0 } 506 bgpM2Established NOTIFICATION-TYPE 507 OBJECTS { 508 bgpM2PeerLocalAddrType, 509 bgpM2PeerLocalAddr, 510 bgpM2PeerRemoteAddrType, 511 bgpM2PeerRemoteAddr, 512 bgpM2PeerLastErrorReceived, 513 bgpM2PeerState 514 } 515 STATUS current 516 DESCRIPTION 517 "The BGP Established event is generated when 518 the BGP FSM enters the ESTABLISHED state." 519 ::= { bgpM2BaseNotifications 1 } 521 bgpM2BackwardTransition NOTIFICATION-TYPE 522 OBJECTS { 523 bgpM2PeerLocalAddrType, 524 bgpM2PeerLocalAddr, 525 bgpM2PeerRemoteAddrType, 526 bgpM2PeerRemoteAddr, 527 bgpM2PeerLastErrorReceived, 528 bgpM2PeerLastErrorReceivedText, 529 bgpM2PeerState 530 } 531 STATUS current 532 DESCRIPTION 533 "The BGPBackwardTransition Event is generated 534 when the BGP FSM moves from a higher numbered 535 state to a lower numbered state." 536 ::= { bgpM2BaseNotifications 2 } 538 -- 539 -- BGP Supported Version Table 540 -- 541 bgpM2Version 542 OBJECT IDENTIFIER ::= { bgpM2BaseScalars 1 } 544 bgpM2VersionTable OBJECT-TYPE 545 SYNTAX SEQUENCE OF BgpM2VersionEntry 546 MAX-ACCESS not-accessible 547 STATUS current 548 DESCRIPTION 549 "Table of supported BGP versions." 550 ::= { bgpM2Version 1 } 552 bgpM2VersionEntry OBJECT-TYPE 553 SYNTAX BgpM2VersionEntry 554 MAX-ACCESS not-accessible 555 STATUS current 556 DESCRIPTION 557 "Entry containing data on a given supported version 558 of the Border Gateway Protocol and the level of 559 support provided. It is expected that any agent 560 implementation supporting this MIB module will 561 report support for Version 4 of the Border Gateway 562 Protocol at the very minimum." 563 INDEX { 564 bgpM2VersionIndex 565 } 566 ::= { bgpM2VersionTable 1 } 568 BgpM2VersionEntry ::= SEQUENCE { 569 bgpM2VersionIndex 570 Unsigned32, 571 bgpM2VersionSupported 572 TruthValue 573 } 575 bgpM2VersionIndex OBJECT-TYPE 576 SYNTAX Unsigned32(0..255) 577 MAX-ACCESS read-only 578 STATUS current 579 DESCRIPTION 580 "The version number of the BGP Protocol." 581 ::= { bgpM2VersionEntry 1 } 583 bgpM2VersionSupported OBJECT-TYPE 584 SYNTAX TruthValue 585 MAX-ACCESS read-only 586 STATUS current 587 DESCRIPTION 588 "This value is TRUE if this version of the BGP protocol 589 identified in 'bgpM2VersionIndex' is supported. The absence 590 of a row for a particular bgpM2VersionIndex indicates that 591 that bgpM2VersionIndex protocol version number is not 592 supported." 593 ::= { bgpM2VersionEntry 2 } 595 -- 596 -- Supported authentication mechanisms 597 -- 599 bgpM2SupportedAuthentication 600 OBJECT IDENTIFIER ::= { bgpM2BaseScalars 2 } 602 bgpM2SupportedAuthTable OBJECT-TYPE 603 SYNTAX SEQUENCE OF BgpM2SupportedAuthEntry 604 MAX-ACCESS not-accessible 605 STATUS current 606 DESCRIPTION 607 "The supported BGP authentication mechanisms." 608 ::= { bgpM2SupportedAuthentication 1 } 610 bgpM2SupportedAuthEntry OBJECT-TYPE 611 SYNTAX BgpM2SupportedAuthEntry 612 MAX-ACCESS not-accessible 613 STATUS current 614 DESCRIPTION 615 "Entry containing information whether a given BGP 616 authentication mechanism is supported by this 617 implementation." 618 INDEX { 619 bgpM2SupportedAuthCode 620 } 621 ::= { bgpM2SupportedAuthTable 1 } 623 BgpM2SupportedAuthEntry ::= SEQUENCE { 624 bgpM2SupportedAuthCode 625 Unsigned32, 626 bgpM2SupportedAuthValue 627 TruthValue 629 } 631 bgpM2SupportedAuthCode OBJECT-TYPE 632 SYNTAX Unsigned32(0..255) 633 MAX-ACCESS read-only 634 STATUS current 635 DESCRIPTION 636 "The BGP authentication code." 637 ::= { bgpM2SupportedAuthEntry 1 } 639 bgpM2SupportedAuthValue OBJECT-TYPE 640 SYNTAX TruthValue 641 MAX-ACCESS read-only 642 STATUS current 643 DESCRIPTION 644 "This value is TRUE if a given authentication method 645 is supported by the local implementation." 646 ::= { bgpM2SupportedAuthEntry 2 } 648 -- 649 -- Supported BGP Capabilities 650 -- 652 bgpM2SupportedCapabilities 653 OBJECT IDENTIFIER ::= { bgpM2BaseScalars 3 } 655 bgpM2CapabilitySupportAvailable OBJECT-TYPE 656 SYNTAX TruthValue 657 MAX-ACCESS read-only 658 STATUS current 659 DESCRIPTION 660 "This value is TRUE if capability support is 661 available and is enabled." 662 ::= { bgpM2SupportedCapabilities 1 } 664 bgpM2SupportedCapabilitiesTable OBJECT-TYPE 665 SYNTAX SEQUENCE OF BgpM2SupportedCapabilityEntry 666 MAX-ACCESS not-accessible 667 STATUS current 668 DESCRIPTION 669 "Table of supported BGP-4 capabilities." 670 ::= { bgpM2SupportedCapabilities 2 } 672 bgpM2SupportedCapabilitiesEntry OBJECT-TYPE 673 SYNTAX BgpM2SupportedCapabilityEntry 674 MAX-ACCESS not-accessible 675 STATUS current 676 DESCRIPTION 677 "Information about supported capabilities indexed 678 by capability number." 679 INDEX { 680 bgpM2SupportedCapabilityCode 681 } 682 ::= { bgpM2SupportedCapabilitiesTable 1 } 684 BgpM2SupportedCapabilityEntry ::= SEQUENCE { 685 bgpM2SupportedCapabilityCode 686 Unsigned32, 687 bgpM2SupportedCapability 688 TruthValue 689 } 691 bgpM2SupportedCapabilityCode OBJECT-TYPE 692 SYNTAX Unsigned32 (0..255) 693 MAX-ACCESS read-only 694 STATUS current 695 DESCRIPTION 696 "Index of supported capability. The index directly 697 corresponds with the BGP-4 Capability Advertisement 698 Capability Code." 699 ::= { bgpM2SupportedCapabilitiesEntry 1 } 701 bgpM2SupportedCapability OBJECT-TYPE 702 SYNTAX TruthValue 703 MAX-ACCESS read-only 704 STATUS current 705 DESCRIPTION 706 "This value is True if this capability is supported, 707 False otherwise." 708 ::= { bgpM2SupportedCapabilitiesEntry 2 } 710 -- 711 -- Base Scalars 712 -- 714 bgpM2AsSize OBJECT-TYPE 715 SYNTAX INTEGER { 716 twoOctet(1), 717 fourOctet(2) 718 } 719 MAX-ACCESS read-only 720 STATUS current 721 DESCRIPTION 722 "The size of the AS value in this implementation. 724 The semantics of this are determined as per the 725 as-4bytes draft." 726 REFERENCE 727 "draft-ietf-idr-as4bytes-04" 728 ::= { bgpM2BaseScalars 4 } 730 bgpM2LocalAs OBJECT-TYPE 731 SYNTAX InetAutonomousSystemNumber 732 MAX-ACCESS read-only 733 STATUS current 734 DESCRIPTION 735 "The local autonomous system number. 737 If the bgpM2AsSize is twoOctet, then the range is 738 constrained to be 0-65535." 739 ::= { bgpM2BaseScalars 5 } 741 bgpM2LocalIdentifier OBJECT-TYPE 742 SYNTAX BgpM2Identifier 743 MAX-ACCESS read-only 744 STATUS current 745 DESCRIPTION 746 "The BGP Identifier of local system. 748 Current practice is trending away from this value being 749 treated as an IP address and more as a generic 750 identifier." 751 ::= { bgpM2BaseScalars 6 } 753 -- 754 -- Base Scalar Extensions 755 -- 757 bgpM2BaseScalarExtensions 758 OBJECT IDENTIFIER ::= { bgpM2BaseScalars 7 } 760 bgpM2BaseScalarNonCapExts 761 OBJECT IDENTIFIER ::= { bgpM2BaseScalarExtensions 1 } 763 bgpM2BaseScalarCapExts 764 OBJECT IDENTIFIER ::= { bgpM2BaseScalarExtensions 2 } 766 -- 767 -- Base Scalar Route Reflection Extensions 768 -- 770 bgpM2BaseScalarRouteReflectExts OBJECT IDENTIFIER ::= 771 { bgpM2BaseScalarNonCapExts 2796 } 773 bgpM2RouteReflector OBJECT-TYPE 774 SYNTAX TruthValue 775 MAX-ACCESS read-only 776 STATUS current 777 DESCRIPTION 778 "This value is TRUE if this implementation supports the 779 BGP Route Reflection Extension and is enabled as a 780 route reflector. If the BGP Route Reflection extension 781 is not supported this value must be FALSE." 782 REFERENCE 783 "RFC 2796 - BGP Route Reflection" 784 ::= { bgpM2BaseScalarRouteReflectExts 1 } 786 bgpM2ClusterId OBJECT-TYPE 787 SYNTAX BgpM2Identifier 788 MAX-ACCESS read-only 789 STATUS current 790 DESCRIPTION 791 "The configured Cluster-ID of the BGP Speaker. This will 792 default to the BGP Speaker's BgpM2Identifier if this 793 speaker is functioning as a route reflector and an 794 explicit Cluster-ID has not been configured. 796 A value of 0.0.0.0 will be present if Route Reflection is 797 not enabled." 798 REFERENCE 799 "RFC 2796 - BGP Route Reflection" 800 ::= { bgpM2BaseScalarRouteReflectExts 2 } 802 -- 803 -- Base Scalar AS Confederation Extensions 804 -- 806 bgpM2BaseScalarASConfedExts OBJECT IDENTIFIER ::= 807 { bgpM2BaseScalarNonCapExts 3065 } 809 bgpM2ConfederationRouter OBJECT-TYPE 810 SYNTAX TruthValue 811 MAX-ACCESS read-only 812 STATUS current 813 DESCRIPTION 814 "This value is TRUE if this implementation supports the 815 BGP AS Confederations Extension and this router is 816 configured to be in a confederation." 817 REFERENCE 818 "RFC 3065 - Autonomous System Confederations for BGP" 819 ::= { bgpM2BaseScalarASConfedExts 1 } 821 bgpM2ConfederationId OBJECT-TYPE 822 SYNTAX InetAutonomousSystemNumber 823 MAX-ACCESS read-only 824 STATUS current 825 DESCRIPTION 826 "The local Confederation Identification Number. 828 This value will be zero (0) if this BGP Speaker is not 829 a confederation router." 830 REFERENCE 831 "RFC 3065 - Autonomous System Confederations for BGP" 832 ::= { bgpM2BaseScalarASConfedExts 2 } 834 -- 835 -- Base Configuration Objects 836 -- 838 bgpM2BaseScalarConfiguration 839 OBJECT IDENTIFIER ::= { bgpM2BaseScalars 8 } 841 bgpM2CfgBaseScalarStorageType OBJECT-TYPE 842 SYNTAX StorageType 843 MAX-ACCESS read-write 844 STATUS current 845 DESCRIPTION 846 "This object specifies the intended storage type for 847 all configurable base scalars." 848 ::= { bgpM2BaseScalarConfiguration 1 } 850 bgpM2CfgLocalAs OBJECT-TYPE 851 SYNTAX InetAutonomousSystemNumber 852 MAX-ACCESS read-write 853 STATUS current 854 DESCRIPTION 855 "The local autonomous system number. 857 If the bgpM2AsSize is twoOctet, then the range is 858 constrained to be 0-65535." 859 ::= { bgpM2BaseScalarConfiguration 2 } 861 bgpM2CfgLocalIdentifier OBJECT-TYPE 862 SYNTAX BgpM2Identifier 863 MAX-ACCESS read-write 864 STATUS current 865 DESCRIPTION 866 "The BGP Identifier of local system. 868 Current practice is trending away from this value being 869 treated as an IP address and more as a generic 870 identifier." 871 ::= { bgpM2BaseScalarConfiguration 3 } 873 -- 874 -- Base Scalar Extensions 875 -- 877 bgpM2CfgBaseScalarExtensions 878 OBJECT IDENTIFIER ::= { bgpM2BaseScalarConfiguration 4 } 880 bgpM2CfgBaseScalarNonCapExts 881 OBJECT IDENTIFIER ::= { bgpM2CfgBaseScalarExtensions 1 } 883 bgpM2CfgBaseScalarCapExts 884 OBJECT IDENTIFIER ::= { bgpM2CfgBaseScalarExtensions 2 } 886 -- 887 -- Base Scalar Route Reflection Extensions 888 -- 889 bgpM2CfgBaseScalarReflectorExts 890 OBJECT IDENTIFIER ::= { bgpM2CfgBaseScalarNonCapExts 2796 } 892 bgpM2CfgRouteReflector OBJECT-TYPE 893 SYNTAX TruthValue 894 MAX-ACCESS read-write 895 STATUS current 896 DESCRIPTION 897 "This value is set to true if this implementation will 898 be supporting route reflection." 899 REFERENCE 900 "RFC 2796 - BGP Route Reflection" 901 ::= { bgpM2CfgBaseScalarReflectorExts 1 } 903 bgpM2CfgClusterId OBJECT-TYPE 904 SYNTAX BgpM2Identifier 905 MAX-ACCESS read-write 906 STATUS current 907 DESCRIPTION 908 "The configured Cluster-ID of the BGP Speaker. This will 909 default to the BGP Speaker's BgpM2Identifier if this 910 speaker is functioning as a route reflector and an 911 explicit Cluster-ID has not been configured. 913 A value of 0.0.0.0 will be present if Route Reflection is 914 not enabled." 915 REFERENCE 916 "RFC 2796 - BGP Route Reflection" 917 ::= { bgpM2CfgBaseScalarReflectorExts 2 } 919 -- 920 -- Base Scalar AS Confederation Extensions 921 -- 923 bgpM2CfgBaseScalarASConfedExts 924 OBJECT IDENTIFIER ::= { bgpM2CfgBaseScalarNonCapExts 3065 } 926 bgpM2CfgConfederationRouter OBJECT-TYPE 927 SYNTAX TruthValue 928 MAX-ACCESS read-write 929 STATUS current 930 DESCRIPTION 931 "This value is set to true if this implementation will be 932 supporting BGP AS Confederations." 934 REFERENCE 935 "RFC 3065 - Autonomous System Confederations for BGP" 936 ::= { bgpM2CfgBaseScalarASConfedExts 1 } 938 bgpM2CfgConfederationId OBJECT-TYPE 939 SYNTAX InetAutonomousSystemNumber 940 MAX-ACCESS read-write 941 STATUS current 942 DESCRIPTION 943 "The local Confederation Identification Number. 945 This value will be zero (0) if this BGP Speaker is not 946 a confederation router." 947 REFERENCE 948 "RFC 3065 - Autonomous System Confederations for BGP" 949 ::= { bgpM2CfgBaseScalarASConfedExts 2 } 951 -- 952 -- BGP Peer Data 953 -- 955 bgpM2Peer 956 OBJECT IDENTIFIER ::= { bgpM2 2 } 958 bgpM2PeerData 959 OBJECT IDENTIFIER ::= { bgpM2Peer 1 } 961 bgpM2PeerTable OBJECT-TYPE 962 SYNTAX SEQUENCE OF BgpM2PeerEntry 963 MAX-ACCESS not-accessible 964 STATUS current 965 DESCRIPTION 966 "BGP peer table. 968 This table contains, one entry per remote BGP peer, 969 any information about the connections with the remote 970 BGP peers." 971 ::= { bgpM2PeerData 1 } 973 bgpM2PeerEntry OBJECT-TYPE 974 SYNTAX BgpM2PeerEntry 975 MAX-ACCESS not-accessible 976 STATUS current 977 DESCRIPTION 978 "Entry containing information about the connection with 979 a remote BGP peer." 980 INDEX { 981 bgpM2PeerLocalAddrType, 982 bgpM2PeerLocalAddr, 983 bgpM2PeerRemoteAddrType, 984 bgpM2PeerRemoteAddr 985 } 986 ::= { bgpM2PeerTable 1 } 988 BgpM2PeerEntry ::= SEQUENCE { 989 bgpM2PeerIdentifier 990 BgpM2Identifier, 991 bgpM2PeerState 992 INTEGER, 993 bgpM2PeerStatus 994 INTEGER, 995 bgpM2PeerConfiguredVersion 996 Unsigned32, 997 bgpM2PeerNegotiatedVersion 998 Unsigned32, 999 bgpM2PeerLocalAddrType 1000 InetAddressType, 1001 bgpM2PeerLocalAddr 1002 InetAddress, 1003 bgpM2PeerLocalPort 1004 InetPortNumber, 1005 bgpM2PeerLocalAs 1006 InetAutonomousSystemNumber, 1007 bgpM2PeerRemoteAddrType 1008 InetAddressType, 1009 bgpM2PeerRemoteAddr 1010 InetAddress, 1011 bgpM2PeerRemotePort 1012 InetPortNumber, 1013 bgpM2PeerRemoteAs 1014 InetAutonomousSystemNumber, 1015 bgpM2PeerIndex 1016 Unsigned32 1017 } 1019 bgpM2PeerIdentifier OBJECT-TYPE 1020 SYNTAX BgpM2Identifier 1021 MAX-ACCESS read-only 1022 STATUS current 1023 DESCRIPTION 1024 "The BGP Identifier of this entry's remote BGP peer. 1026 This entry should be 0.0.0.0 unless the bgpM2PeerState is 1027 in the OpenConfirm or the Established state." 1028 REFERENCE 1029 "draft-ietf-idr-bgp4-17.txt, Sec. 4.2" 1030 ::= { bgpM2PeerEntry 1 } 1032 bgpM2PeerState OBJECT-TYPE 1033 SYNTAX INTEGER { 1034 idle(1), 1035 connect(2), 1036 active(3), 1037 opensent(4), 1038 openconfirm(5), 1039 established(6) 1040 } 1041 MAX-ACCESS read-only 1042 STATUS current 1043 DESCRIPTION 1044 "The remote BGP peer's FSM state." 1045 REFERENCE 1046 "draft-ietf-idr-bgp4-17.txt, Sec. 8" 1047 ::= { bgpM2PeerEntry 2 } 1049 bgpM2PeerStatus OBJECT-TYPE 1050 SYNTAX INTEGER { 1051 halted(1), 1052 running(2) 1053 } 1054 MAX-ACCESS read-only 1055 STATUS current 1056 DESCRIPTION 1057 "Whether or not the BGP FSM for this remote peer is halted 1058 or running. The BGP FSM for a remote peer is halted after 1059 processing a Stop event. Likewise, it is in the running 1060 state after a Start event. 1062 The bgpM2PeerState will generally be in the idle state when 1063 the FSM is halted, although some extensions such as 1064 Graceful Restart will leave the peer in the Idle state 1065 but with the FSM running." 1066 ::= { bgpM2PeerEntry 3 } 1068 bgpM2PeerConfiguredVersion OBJECT-TYPE 1069 SYNTAX Unsigned32 (1..255) 1070 MAX-ACCESS read-only 1071 STATUS current 1072 DESCRIPTION 1073 "The configured version to originally start with this 1074 remote peer. The BGP speaker may permit negotiation to a 1075 lower version number of the protocol." 1076 ::= { bgpM2PeerEntry 4 } 1078 bgpM2PeerNegotiatedVersion OBJECT-TYPE 1079 SYNTAX Unsigned32 (1..255) 1080 MAX-ACCESS read-only 1081 STATUS current 1082 DESCRIPTION 1083 "The negotiated version of BGP running between the two 1084 peers." 1085 ::= { bgpM2PeerEntry 5 } 1087 bgpM2PeerLocalAddrType OBJECT-TYPE 1088 SYNTAX InetAddressType 1089 MAX-ACCESS read-only 1090 STATUS current 1091 DESCRIPTION 1092 "The address family of the local end of the peering 1093 session." 1094 ::= { bgpM2PeerEntry 6 } 1096 bgpM2PeerLocalAddr OBJECT-TYPE 1097 SYNTAX InetAddress (SIZE(4..20)) 1098 MAX-ACCESS read-only 1099 STATUS current 1100 DESCRIPTION 1101 "The address of the local end of the peering session." 1102 ::= { bgpM2PeerEntry 7 } 1104 bgpM2PeerLocalPort OBJECT-TYPE 1105 SYNTAX InetPortNumber 1106 MAX-ACCESS read-only 1107 STATUS current 1108 DESCRIPTION 1109 "The local port for the TCP connection between the BGP 1110 peers." 1111 ::= { bgpM2PeerEntry 8 } 1113 bgpM2PeerLocalAs OBJECT-TYPE 1114 SYNTAX InetAutonomousSystemNumber 1115 MAX-ACCESS read-only 1116 STATUS current 1117 DESCRIPTION 1118 "Some implementations of BGP can represent themselves 1119 as multiple ASs. This is the AS that this peering 1120 session is representing itself as to the remote peer." 1121 ::= { bgpM2PeerEntry 9 } 1123 bgpM2PeerRemoteAddrType OBJECT-TYPE 1124 SYNTAX InetAddressType 1125 MAX-ACCESS read-only 1126 STATUS current 1127 DESCRIPTION 1128 "The address family of the remote end of the peering 1129 session." 1130 ::= { bgpM2PeerEntry 10 } 1132 bgpM2PeerRemoteAddr OBJECT-TYPE 1133 SYNTAX InetAddress (SIZE(4..20)) 1134 MAX-ACCESS read-only 1135 STATUS current 1136 DESCRIPTION 1137 "The address of the remote end of the peering session." 1138 ::= { bgpM2PeerEntry 11 } 1140 bgpM2PeerRemotePort OBJECT-TYPE 1141 SYNTAX InetPortNumber 1142 MAX-ACCESS read-only 1143 STATUS current 1144 DESCRIPTION 1145 "The remote port for the TCP connection between the BGP 1146 peers. In the case of a transport for which the notion 1147 of 'port' is irrelevant, an instance value of -1 1148 should be returned by the agent for this object. 1150 Note that the objects bgpM2PeerLocalAddr, 1151 bgpM2PeerLocalPort, bgpM2PeerRemoteAddr and 1152 bgpM2PeerRemotePort provide the appropriate reference to 1153 the standard MIB TCP connection table. or even the ipv6 1154 TCP MIB as in rfc2452." 1155 REFERENCE 1156 "RFC 2012 - SNMPv2 Management Information Base for the 1157 Transmission Control Protocol using SMIv2. 1159 RFC 2542 - IP Version 6 Management Information Base 1160 for the Transmission Control Protocol." 1161 ::= { bgpM2PeerEntry 12 } 1163 bgpM2PeerRemoteAs OBJECT-TYPE 1164 SYNTAX InetAutonomousSystemNumber 1165 MAX-ACCESS read-only 1166 STATUS current 1167 DESCRIPTION 1168 "The remote autonomous system number." 1169 ::= { bgpM2PeerEntry 13 } 1171 bgpM2PeerIndex OBJECT-TYPE 1172 SYNTAX Unsigned32 1173 MAX-ACCESS read-only 1174 STATUS current 1175 DESCRIPTION 1176 "This value is a unique index for the remote peer entry 1177 in the bgpM2PeerTable. It is assigned by the agent 1178 at the point of creation of the bgpM2PeerTable row 1179 entry. While its value is guaranteed to be unique at 1180 any time, it is otherwise opaque to the management 1181 application with respect to its value or the contiguity 1182 of bgpM2PeerIndex row instance values across rows of 1183 the bgpM2PeerTable. It is used to provide an index 1184 structure for other tables whose data is logically 1185 per-peer. 1187 For explicitly configured peers, this value will remain 1188 consistent until this row is deleted by deleting the 1189 configured peers. Unconfigured peers will generate 1190 a monotonically increasing number when a BGP FSM is 1191 built to process the peering session. Values in the 1192 bgpM2PeerTable and other tables utilizing bgpM2PeerIndex 1193 are expected to remain in existence for an arbitrary 1194 time after the unconfigured peer has been deleted 1195 in order to allow management applications to extract 1196 useful management information for those peers. Thus, 1197 an unconfigured peer using the same indices as the 1198 bgpM2PeerTable that comes up while this row still 1199 exists will re-utilize the same row." 1200 ::= { bgpM2PeerEntry 14 } 1202 -- 1203 -- Errors 1204 -- 1206 bgpM2PeerErrors 1207 OBJECT IDENTIFIER ::= { bgpM2Peer 2 } 1209 bgpM2PeerErrorsTable OBJECT-TYPE 1210 SYNTAX SEQUENCE OF BgpM2PeerErrorsEntry 1211 MAX-ACCESS not-accessible 1212 STATUS current 1213 DESCRIPTION 1214 "On a per peer basis, this table reflects the last 1215 protocol-defined error encountered and reported on 1216 the peer session. If no entry for a given peer, 1217 by its bgpM2PeerIndex, exists in this table, then no 1218 such errors have been observed, reported, and 1219 recorded on the session." 1220 ::= { bgpM2PeerErrors 1 } 1222 bgpM2PeerErrorsEntry OBJECT-TYPE 1223 SYNTAX BgpM2PeerErrorsEntry 1224 MAX-ACCESS not-accessible 1225 STATUS current 1226 DESCRIPTION 1227 "Each entry contains information about errors sent 1228 and received for a particular BGP peer." 1229 AUGMENTS { 1230 bgpM2PeerEntry 1231 } 1232 ::= { bgpM2PeerErrorsTable 1 } 1234 BgpM2PeerErrorsEntry ::= SEQUENCE { 1235 bgpM2PeerLastErrorReceived 1236 OCTET STRING, 1237 bgpM2PeerLastErrorSent 1238 OCTET STRING, 1239 bgpM2PeerLastErrorReceivedTime 1240 TimeTicks, 1241 bgpM2PeerLastErrorSentTime 1242 TimeTicks, 1243 bgpM2PeerLastErrorReceivedText 1244 SnmpAdminString, 1245 bgpM2PeerLastErrorSentText 1246 SnmpAdminString, 1247 bgpM2PeerLastErrorReceivedData 1248 OCTET STRING, 1249 bgpM2PeerLastErrorSentData 1250 OCTET STRING 1251 } 1253 bgpM2PeerLastErrorReceived OBJECT-TYPE 1254 SYNTAX OCTET STRING (SIZE (2)) 1255 MAX-ACCESS read-only 1256 STATUS current 1257 DESCRIPTION 1258 "The last error code and subcode received by this BGP 1259 Speaker via a NOTIFICATION message for this peer. 1260 If no error has occurred, this field is zero. 1261 Otherwise, the first byte of this two byte 1262 OCTET STRING contains the error code, and the second 1263 byte contains the subcode." 1264 REFERENCE 1265 "draft-ietf-idr-bgp4-15.txt, Sec. 4.5" 1266 ::= { bgpM2PeerErrorsEntry 1 } 1268 bgpM2PeerLastErrorSent OBJECT-TYPE 1269 SYNTAX OCTET STRING (SIZE (2)) 1270 MAX-ACCESS read-only 1271 STATUS current 1272 DESCRIPTION 1273 "The last error code and subcode sent by this BGP 1274 Speaker via a NOTIFICATION message to this peer. 1275 If no error has occurred, this field is zero. 1276 Otherwise, the first byte of this two byte 1277 OCTET STRING contains the error code, and the second 1278 byte contains the subcode." 1279 REFERENCE 1280 "draft-ietf-idr-bgp4-15.txt, Sec. 4.5" 1281 ::= { bgpM2PeerErrorsEntry 2 } 1283 bgpM2PeerLastErrorReceivedTime OBJECT-TYPE 1284 SYNTAX TimeTicks 1285 MAX-ACCESS read-only 1286 STATUS current 1287 DESCRIPTION 1288 "The timestamp that the last NOTIFICATION was received from 1289 this peer." 1290 REFERENCE 1291 "draft-ietf-idr-bgp4-15.txt, Sec. 4.5" 1292 ::= { bgpM2PeerErrorsEntry 3 } 1294 bgpM2PeerLastErrorSentTime OBJECT-TYPE 1295 SYNTAX TimeTicks 1296 MAX-ACCESS read-only 1297 STATUS current 1298 DESCRIPTION 1299 "The timestamp that the last NOTIFICATION was sent to 1300 this peer." 1301 REFERENCE 1302 "draft-ietf-idr-bgp4-15.txt, Sec. 4.5" 1303 ::= { bgpM2PeerErrorsEntry 4 } 1305 bgpM2PeerLastErrorReceivedText OBJECT-TYPE 1306 SYNTAX SnmpAdminString 1307 MAX-ACCESS read-only 1308 STATUS current 1309 DESCRIPTION 1310 "This object contains an implementation specific 1311 explanation of the error that was reported." 1312 ::= { bgpM2PeerErrorsEntry 5 } 1314 bgpM2PeerLastErrorSentText OBJECT-TYPE 1315 SYNTAX SnmpAdminString 1316 MAX-ACCESS read-only 1317 STATUS current 1318 DESCRIPTION 1319 "This object contains an implementation specific 1320 explanation of the error that is being reported." 1321 ::= { bgpM2PeerErrorsEntry 6 } 1323 bgpM2PeerLastErrorReceivedData OBJECT-TYPE 1324 SYNTAX OCTET STRING (SIZE(0..4075)) 1325 MAX-ACCESS read-only 1326 STATUS current 1327 DESCRIPTION 1328 "The last error code's data seen by this peer." 1329 REFERENCE 1330 "draft-ietf-idr-bgp4-15.txt, Sec. 4.5" 1331 ::= { bgpM2PeerErrorsEntry 7 } 1333 bgpM2PeerLastErrorSentData OBJECT-TYPE 1334 SYNTAX OCTET STRING (SIZE(0..4075)) 1335 MAX-ACCESS read-only 1336 STATUS current 1337 DESCRIPTION 1338 "The last error code's data sent to this peer." 1339 REFERENCE 1340 "draft-ietf-idr-bgp4-15.txt, Sec. 4.5" 1341 ::= { bgpM2PeerErrorsEntry 8 } 1343 -- 1344 -- Peer Authentication 1345 -- 1347 bgpM2PeerAuthentication 1348 OBJECT IDENTIFIER ::= { bgpM2Peer 3 } 1350 bgpM2PeerAuthTable OBJECT-TYPE 1351 SYNTAX SEQUENCE OF BgpM2PeerAuthEntry 1352 MAX-ACCESS not-accessible 1353 STATUS current 1354 DESCRIPTION 1355 "BGP peer authentication table. 1357 This table contains, one entry per BGP peer, 1358 information about the authentication with BGP peers." 1359 ::= { bgpM2PeerAuthentication 1 } 1361 bgpM2PeerAuthEntry OBJECT-TYPE 1362 SYNTAX BgpM2PeerAuthEntry 1363 MAX-ACCESS not-accessible 1364 STATUS current 1365 DESCRIPTION 1366 "Entry containing information about the authentication 1367 with a BGP peer." 1368 AUGMENTS { 1369 bgpM2PeerEntry 1370 } 1371 ::= { bgpM2PeerAuthTable 1 } 1373 BgpM2PeerAuthEntry ::= SEQUENCE { 1374 bgpM2PeerAuthSent 1375 TruthValue, 1376 bgpM2PeerAuthSentCode 1377 Unsigned32, 1378 bgpM2PeerAuthSentValue 1379 OCTET STRING, 1380 bgpM2PeerAuthRcvd 1381 TruthValue, 1383 bgpM2PeerAuthRcvdCode 1384 Unsigned32, 1385 bgpM2PeerAuthRcvdValue 1386 OCTET STRING 1387 } 1389 bgpM2PeerAuthSent OBJECT-TYPE 1390 SYNTAX TruthValue 1391 MAX-ACCESS read-only 1392 STATUS current 1393 DESCRIPTION 1394 "The local peer has sent authentication information 1395 to the remote peer in the BGP Authentication field." 1396 ::= { bgpM2PeerAuthEntry 1 } 1398 bgpM2PeerAuthSentCode OBJECT-TYPE 1399 SYNTAX Unsigned32 (0..255) 1400 MAX-ACCESS read-only 1401 STATUS current 1402 DESCRIPTION 1403 "The code of the authentication information sent to 1404 the remote peer." 1405 ::= { bgpM2PeerAuthEntry 2 } 1407 bgpM2PeerAuthSentValue OBJECT-TYPE 1408 SYNTAX OCTET STRING (SIZE (0..252)) 1409 MAX-ACCESS read-only 1410 STATUS current 1411 DESCRIPTION 1412 "The payload of the authentication information 1413 from the remote peer." 1414 ::= { bgpM2PeerAuthEntry 3 } 1416 bgpM2PeerAuthRcvd OBJECT-TYPE 1417 SYNTAX TruthValue 1418 MAX-ACCESS read-only 1419 STATUS current 1420 DESCRIPTION 1421 "The local peer has received authentication information 1422 from the remote peer in the BGP Authentication field." 1423 ::= { bgpM2PeerAuthEntry 4 } 1425 bgpM2PeerAuthRcvdCode OBJECT-TYPE 1426 SYNTAX Unsigned32 (0..255) 1427 MAX-ACCESS read-only 1428 STATUS current 1429 DESCRIPTION 1430 "The code of the authentication information received from 1431 the remote peer." 1432 ::= { bgpM2PeerAuthEntry 5 } 1434 bgpM2PeerAuthRcvdValue OBJECT-TYPE 1435 SYNTAX OCTET STRING (SIZE (0..252)) 1436 MAX-ACCESS read-only 1437 STATUS current 1438 DESCRIPTION 1439 "The payload of the authentication information from 1440 the remote peer." 1441 ::= { bgpM2PeerAuthEntry 6 } 1443 -- 1444 -- Peer Event Times 1445 -- 1447 bgpM2PeerTimers 1448 OBJECT IDENTIFIER ::= { bgpM2Peer 4 } 1450 bgpM2PeerEventTimesTable OBJECT-TYPE 1451 SYNTAX SEQUENCE OF BgpM2PeerEventTimesEntry 1452 MAX-ACCESS not-accessible 1453 STATUS current 1454 DESCRIPTION 1455 "A table reporting the per-peering session amount 1456 of time elapsed and update events since the peering 1457 session advanced into the Established state." 1458 ::= { bgpM2PeerTimers 1 } 1460 bgpM2PeerEventTimesEntry OBJECT-TYPE 1461 SYNTAX BgpM2PeerEventTimesEntry 1462 MAX-ACCESS not-accessible 1463 STATUS current 1464 DESCRIPTION 1465 "Each row contains a set of statistics about time 1466 spent and events encountered in the peer session 1467 Established state." 1468 AUGMENTS { 1469 bgpM2PeerEntry 1471 } 1472 ::= { bgpM2PeerEventTimesTable 1 } 1474 BgpM2PeerEventTimesEntry ::= SEQUENCE { 1475 bgpM2PeerFsmEstablishedTime 1476 Gauge32, 1477 bgpM2PeerInUpdatesElapsedTime 1478 Gauge32 1479 } 1481 bgpM2PeerFsmEstablishedTime OBJECT-TYPE 1482 SYNTAX Gauge32 1483 MAX-ACCESS read-only 1484 STATUS current 1485 DESCRIPTION 1486 "This timer indicates how long (in seconds) this 1487 peer has been in the Established state or how long 1488 since this peer was last in the Established state. 1489 It is set to zero when a new peer is configured or 1490 the router is booted." 1491 ::= { bgpM2PeerEventTimesEntry 1 } 1493 bgpM2PeerInUpdatesElapsedTime OBJECT-TYPE 1494 SYNTAX Gauge32 1495 MAX-ACCESS read-only 1496 STATUS current 1497 DESCRIPTION 1498 "Elapsed time in seconds since the last BGP UPDATE 1499 message was received from the peer. Each time 1500 bgpM2PeerInUpdates is incremented, the value of this 1501 object is set to zero (0). This value shall also be 1502 zero (0) when the peer is not in the Established state" 1503 ::= { bgpM2PeerEventTimesEntry 2 } 1505 -- 1506 -- Peer Configured Timers 1507 -- 1509 bgpM2PeerConfiguredTimersTable OBJECT-TYPE 1510 SYNTAX SEQUENCE OF BgpM2PeerConfiguredTimersEntry 1511 MAX-ACCESS not-accessible 1512 STATUS current 1513 DESCRIPTION 1514 "Per peer management data on BGP session timers." 1516 ::= { bgpM2PeerTimers 2 } 1518 bgpM2PeerConfiguredTimersEntry OBJECT-TYPE 1519 SYNTAX BgpM2PeerConfiguredTimersEntry 1520 MAX-ACCESS not-accessible 1521 STATUS current 1522 DESCRIPTION 1523 "Each entry corresponds to the current state of 1524 BGP timers on a given peering session." 1525 AUGMENTS { 1526 bgpM2PeerEntry 1527 } 1528 ::= { bgpM2PeerConfiguredTimersTable 1 } 1530 BgpM2PeerConfiguredTimersEntry ::= SEQUENCE { 1531 bgpM2PeerConnectRetryInterval 1532 Unsigned32, 1533 bgpM2PeerHoldTimeConfigured 1534 Unsigned32, 1535 bgpM2PeerKeepAliveConfigured 1536 Unsigned32, 1537 bgpM2PeerMinASOrigInterval 1538 Unsigned32, 1539 bgpM2PeerMinRouteAdverInterval 1540 Unsigned32 1541 } 1543 bgpM2PeerConnectRetryInterval OBJECT-TYPE 1544 SYNTAX Unsigned32 (1..65535) 1545 MAX-ACCESS read-only 1546 STATUS current 1547 DESCRIPTION 1548 "Time interval in seconds for the ConnectRetry 1549 timer. The suggested value for this timer is 120 1550 seconds." 1551 ::= { bgpM2PeerConfiguredTimersEntry 1 } 1553 bgpM2PeerHoldTimeConfigured OBJECT-TYPE 1554 SYNTAX Unsigned32 ( 0 | 3..65535 ) 1555 MAX-ACCESS read-only 1556 STATUS current 1557 DESCRIPTION 1558 "Time interval in seconds for the Hold Time configured 1559 for this BGP speaker with this peer. This value 1560 is placed in an OPEN message sent to this peer by 1561 this BGP speaker, and is compared with the Hold 1562 Time field in an OPEN message received from the 1563 peer when determining the Hold Time (bgpM2PeerHoldTime) 1564 with the peer. This value must not be less than 1565 three seconds if it is not zero (0) in which case 1566 the Hold Time is NOT to be established with the 1567 peer. The suggested value for this timer is 90 1568 seconds." 1569 REFERENCE 1570 "draft-ietf-idr-bgp4-17.txt, Appendix 6.4" 1571 ::= { bgpM2PeerConfiguredTimersEntry 2 } 1573 bgpM2PeerKeepAliveConfigured OBJECT-TYPE 1574 SYNTAX Unsigned32 ( 0 | 1..21845 ) 1575 MAX-ACCESS read-only 1576 STATUS current 1577 DESCRIPTION 1578 "Time interval in seconds for the KeepAlive timer 1579 configured for this BGP speaker with this peer. 1580 The value of this object will only determine the 1581 KEEPALIVE messages frequency relative to the value 1582 specified in bgpM2PeerHoldTimeConfigured; the actual 1583 time interval for the KEEPALIVE messages is indicated 1584 by bgpM2PeerKeepAlive. A reasonable maximum value 1585 for this timer would be configured to be one third 1586 of that of bgpM2PeerHoldTimeConfigured. 1588 If the value of this object is zero (0), no 1589 periodical KEEPALIVE messages are sent to the peer 1590 after the BGP connection has been established. 1591 The suggested value for this timer is 30 seconds." 1592 REFERENCE 1593 "draft-ietf-idr-bgp4-17.txt, Appendix 6.4" 1594 ::= { bgpM2PeerConfiguredTimersEntry 3 } 1596 bgpM2PeerMinASOrigInterval OBJECT-TYPE 1597 SYNTAX Unsigned32 (0..65535) 1598 MAX-ACCESS read-only 1599 STATUS current 1600 DESCRIPTION 1601 "Time interval in seconds for the MinASOriginationInterval 1602 timer. The suggested value for this timer is 15 1603 seconds." 1604 ::= { bgpM2PeerConfiguredTimersEntry 4 } 1606 bgpM2PeerMinRouteAdverInterval OBJECT-TYPE 1607 SYNTAX Unsigned32 (0..65535) 1608 MAX-ACCESS read-only 1609 STATUS current 1610 DESCRIPTION 1611 "Time interval in seconds for the 1612 MinRouteAdvertisementInterval timer. The suggested 1613 value for this timer is 30 seconds." 1614 ::= { bgpM2PeerConfiguredTimersEntry 5 } 1616 -- 1617 -- Peer Negotiated Timers 1618 -- 1620 bgpM2PeerNegotiatedTimersTable OBJECT-TYPE 1621 SYNTAX SEQUENCE OF BgpM2PeerNegotiatedTimersEntry 1622 MAX-ACCESS not-accessible 1623 STATUS current 1624 DESCRIPTION 1625 "Current values of per-peer timers which can be 1626 dynamically set in the bgpM2PeerConfiguredTimersTable. 1627 Values reflected in this table are the current 1628 operational values, after negotiation from values 1629 derived from initial configuration or last set from 1630 bgpM2PeerConfiguredTimersTable row instances." 1631 ::= { bgpM2PeerTimers 3 } 1633 bgpM2PeerNegotiatedTimersEntry OBJECT-TYPE 1634 SYNTAX BgpM2PeerNegotiatedTimersEntry 1635 MAX-ACCESS not-accessible 1636 STATUS current 1637 DESCRIPTION 1638 "Each entry reflects a value of the currently 1639 operational, negotiated timers as reflected in the 1640 BgpM2PeerNegotiatedTimersEntry." 1641 AUGMENTS { 1642 bgpM2PeerEntry 1643 } 1644 ::= { bgpM2PeerNegotiatedTimersTable 1 } 1646 BgpM2PeerNegotiatedTimersEntry ::= SEQUENCE { 1647 bgpM2PeerHoldTime 1648 Unsigned32, 1649 bgpM2PeerKeepAlive 1650 Unsigned32 1652 } 1654 bgpM2PeerHoldTime OBJECT-TYPE 1655 SYNTAX Unsigned32 ( 0 | 3..65535 ) 1656 MAX-ACCESS read-only 1657 STATUS current 1658 DESCRIPTION 1659 "The value of this object is calculated by this BGP 1660 Speaker as being; 1662 zero (0) - if this was the value sent by the peer and 1663 this value is permitted by this BGP Speaker. In this 1664 case, no keepalive messages are sent and the Hold Timer 1665 is not set. 1667 At least three (3). This value is the smaller of 1668 the value sent by this peer in the OPEN message and 1669 bgpM2PeerHoldTimeConfigured for this peer. 1671 This value is only defined when the peering session is 1672 in the Established state." 1673 REFERENCE 1674 "draft-ietf-idr-bgp4-17.txt, Sec. 4.2" 1675 ::= { bgpM2PeerNegotiatedTimersEntry 1 } 1677 bgpM2PeerKeepAlive OBJECT-TYPE 1678 SYNTAX Unsigned32 ( 0 | 1..21845 ) 1679 MAX-ACCESS read-only 1680 STATUS current 1681 DESCRIPTION 1682 "Time interval in seconds for the KeepAlive timer 1683 established with the peer. The value of this object 1684 is calculated by this BGP speaker such that, when 1685 compared with bgpM2PeerHoldTime, it has the same 1686 proportion as what bgpM2PeerKeepAliveConfigured has 1687 when compared with bgpM2PeerHoldTimeConfigured. If 1688 the value of this object is zero (0), it indicates 1689 that the KeepAlive timer has not been established 1690 with the peer, or, the value of 1691 bgpM2PeerKeepAliveConfigured is zero (0). 1693 This value is only defined when the peering session is 1694 in the Established state." 1695 REFERENCE 1696 "draft-ietf-idr-bgp4-17, Sec. 4.4" 1697 ::= { bgpM2PeerNegotiatedTimersEntry 2 } 1699 -- 1700 -- Peer Capabilities 1701 -- 1703 bgpM2PeerCapabilities 1704 OBJECT IDENTIFIER ::= { bgpM2Peer 5 } 1706 -- 1707 -- Announced Capabilities 1708 -- 1710 bgpM2PeerCapsAnnouncedTable OBJECT-TYPE 1711 SYNTAX SEQUENCE OF BgpM2PeerCapsAnnouncedEntry 1712 MAX-ACCESS not-accessible 1713 STATUS current 1714 DESCRIPTION 1715 "This table contains the capabilities 1716 that are supported for a given peer." 1717 ::= { bgpM2PeerCapabilities 1 } 1719 bgpM2PeerCapsAnnouncedEntry OBJECT-TYPE 1720 SYNTAX BgpM2PeerCapsAnnouncedEntry 1721 MAX-ACCESS not-accessible 1722 STATUS current 1723 DESCRIPTION 1724 "These entries are keyed by a BGP-4 peer remote 1725 address and the BGP Capability Code" 1726 INDEX { 1727 bgpM2PeerIndex, 1728 bgpM2PeerCapAnnouncedCode, 1729 bgpM2PeerCapAnnouncedIndex 1730 } 1731 ::= { bgpM2PeerCapsAnnouncedTable 1 } 1733 BgpM2PeerCapsAnnouncedEntry ::= SEQUENCE { 1734 bgpM2PeerCapAnnouncedCode 1735 Unsigned32, 1736 bgpM2PeerCapAnnouncedIndex 1737 Unsigned32, 1738 bgpM2PeerCapAnnouncedValue 1739 OCTET STRING 1740 } 1742 bgpM2PeerCapAnnouncedCode OBJECT-TYPE 1743 SYNTAX Unsigned32 (0..255) 1744 MAX-ACCESS read-only 1745 STATUS current 1746 DESCRIPTION 1747 "The BGP Capability Advertisement Capability Code." 1748 ::= { bgpM2PeerCapsAnnouncedEntry 1 } 1750 bgpM2PeerCapAnnouncedIndex OBJECT-TYPE 1751 SYNTAX Unsigned32 (1..128) 1752 MAX-ACCESS read-only 1753 STATUS current 1754 DESCRIPTION 1755 "Multiple instances of a given capability may be sent 1756 bgp a BGP speaker. This variable is used to index them." 1757 ::= { bgpM2PeerCapsAnnouncedEntry 2 } 1759 bgpM2PeerCapAnnouncedValue OBJECT-TYPE 1760 SYNTAX OCTET STRING (SIZE(0..255)) 1761 MAX-ACCESS read-only 1762 STATUS current 1763 DESCRIPTION 1764 "The value of the announced capability." 1765 ::= { bgpM2PeerCapsAnnouncedEntry 3 } 1767 -- 1768 -- Received Capabilities 1769 -- 1771 bgpM2PeerCapsReceivedTable OBJECT-TYPE 1772 SYNTAX SEQUENCE OF BgpM24PeerCapsReceivedEntry 1773 MAX-ACCESS not-accessible 1774 STATUS current 1775 DESCRIPTION 1776 "This table contains the capabilities 1777 that are supported for a given peer." 1778 ::= { bgpM2PeerCapabilities 2 } 1780 bgpM2PeerCapsReceivedEntry OBJECT-TYPE 1781 SYNTAX BgpM24PeerCapsReceivedEntry 1782 MAX-ACCESS not-accessible 1783 STATUS current 1784 DESCRIPTION 1785 "These entries are keyed by a BGP-4 peer remote 1786 address and the BGP Capability Code" 1788 INDEX { 1789 bgpM2PeerIndex, 1790 bgpM2PeerCapReceivedCode, 1791 bgpM2PeerCapReceivedIndex 1792 } 1793 ::= { bgpM2PeerCapsReceivedTable 1 } 1795 BgpM24PeerCapsReceivedEntry ::= SEQUENCE { 1796 bgpM2PeerCapReceivedCode 1797 Unsigned32, 1798 bgpM2PeerCapReceivedIndex 1799 Unsigned32, 1800 bgpM2PeerCapReceivedValue 1801 OCTET STRING 1802 } 1804 bgpM2PeerCapReceivedCode OBJECT-TYPE 1805 SYNTAX Unsigned32 (0..255) 1806 MAX-ACCESS read-only 1807 STATUS current 1808 DESCRIPTION 1809 "The BGP Capability Advertisement Capability Code." 1810 ::= { bgpM2PeerCapsReceivedEntry 1 } 1812 bgpM2PeerCapReceivedIndex OBJECT-TYPE 1813 SYNTAX Unsigned32 (1..128) 1814 MAX-ACCESS read-only 1815 STATUS current 1816 DESCRIPTION 1817 "Multiple instances of a given capability may be sent 1818 bgp a BGP speaker. This variable is used to index them." 1819 ::= { bgpM2PeerCapsReceivedEntry 2 } 1821 bgpM2PeerCapReceivedValue OBJECT-TYPE 1822 SYNTAX OCTET STRING (SIZE(0..255)) 1823 MAX-ACCESS read-only 1824 STATUS current 1825 DESCRIPTION 1826 "The value of the announced capability." 1827 ::= { bgpM2PeerCapsReceivedEntry 3 } 1829 -- 1830 -- Per-peer counters 1831 -- 1833 bgpM2PeerCounters 1834 OBJECT IDENTIFIER ::= { bgpM2Peer 6 } 1836 bgpM2PeerCountersTable OBJECT-TYPE 1837 SYNTAX SEQUENCE OF BgpM2PeerCountersEntry 1838 MAX-ACCESS not-accessible 1839 STATUS current 1840 DESCRIPTION 1841 "The counters associated with a BGP Peer." 1842 ::= { bgpM2PeerCounters 1 } 1844 bgpM2PeerCountersEntry OBJECT-TYPE 1845 SYNTAX BgpM2PeerCountersEntry 1846 MAX-ACCESS not-accessible 1847 STATUS current 1848 DESCRIPTION 1849 "Each entry contains counters of message transmissions 1850 and FSM transitions for a given BGP Peering session." 1851 AUGMENTS { 1852 bgpM2PeerEntry 1853 } 1854 ::= { bgpM2PeerCountersTable 1 } 1856 BgpM2PeerCountersEntry ::= SEQUENCE { 1857 bgpM2PeerInUpdates 1858 Counter32, 1859 bgpM2PeerOutUpdates 1860 Counter32, 1861 bgpM2PeerInTotalMessages 1862 Counter32, 1863 bgpM2PeerOutTotalMessages 1864 Counter32, 1865 bgpM2PeerFsmEstablishedTrans 1866 Counter32 1867 } 1869 -- +++wayne need to describe what happens if connection is broken 1870 -- and then reestablished. Does the prior counter value accumulate? 1871 bgpM2PeerInUpdates OBJECT-TYPE 1872 SYNTAX Counter32 1873 MAX-ACCESS read-only 1874 STATUS current 1875 DESCRIPTION 1876 "The number of BGP UPDATE messages received on this 1877 connection. This object should be initialized to zero 1878 (0) when the connection is established." 1879 ::= { bgpM2PeerCountersEntry 1 } 1881 bgpM2PeerOutUpdates OBJECT-TYPE 1882 SYNTAX Counter32 1883 MAX-ACCESS read-only 1884 STATUS current 1885 DESCRIPTION 1886 "The number of BGP UPDATE messages transmitted on this 1887 connection. This object should be initialized to zero 1888 (0) when the connection is established." 1889 ::= { bgpM2PeerCountersEntry 2 } 1891 bgpM2PeerInTotalMessages OBJECT-TYPE 1892 SYNTAX Counter32 1893 MAX-ACCESS read-only 1894 STATUS current 1895 DESCRIPTION 1896 "The total number of messages received from the remote 1897 peer on this connection. This object should be 1898 initialized to zero when the connection is established." 1899 ::= { bgpM2PeerCountersEntry 3 } 1901 bgpM2PeerOutTotalMessages OBJECT-TYPE 1902 SYNTAX Counter32 1903 MAX-ACCESS read-only 1904 STATUS current 1905 DESCRIPTION 1906 "The total number of messages transmitted to the remote 1907 peer on this connection. This object should be 1908 initialized to zero when the connection is established." 1909 ::= { bgpM2PeerCountersEntry 4 } 1911 bgpM2PeerFsmEstablishedTrans OBJECT-TYPE 1912 SYNTAX Counter32 1913 MAX-ACCESS read-only 1914 STATUS current 1915 DESCRIPTION 1916 "The total number of times the BGP FSM 1917 transitioned into the established state 1918 for this peer." 1919 ::= { bgpM2PeerCountersEntry 5 } 1921 -- 1922 -- Per-Peer Prefix Counters 1923 -- 1925 bgpM2PrefixCountersTable OBJECT-TYPE 1926 SYNTAX SEQUENCE OF BgpM2PrefixCountersEntry 1927 MAX-ACCESS not-accessible 1928 STATUS current 1929 DESCRIPTION 1930 "Additional per-peer, per AFI SAFI counters for prefixes" 1931 ::= { bgpM2PeerCounters 2 } 1933 bgpM2PrefixCountersEntry OBJECT-TYPE 1934 SYNTAX BgpM2PrefixCountersEntry 1935 MAX-ACCESS not-accessible 1936 STATUS current 1937 DESCRIPTION 1938 "Entry containing information about a bgp-peers prefix 1939 counters." 1940 INDEX { 1941 bgpM2PeerIndex, 1942 bgpM2PrefixCountersAfi, 1943 bgpM2PrefixCountersSafi 1944 } 1945 ::= { bgpM2PrefixCountersTable 1 } 1947 BgpM2PrefixCountersEntry ::= SEQUENCE { 1948 bgpM2PrefixCountersAfi 1949 InetAddressType, 1950 bgpM2PrefixCountersSafi 1951 BgpM2Safi, 1952 bgpM2PrefixInPrefixes 1953 Gauge32, 1954 bgpM2PrefixInPrefixesAccepted 1955 Gauge32, 1956 bgpM2PrefixInPrefixesRejected 1957 Gauge32, 1958 bgpM2PrefixOutPrefixes 1959 Gauge32 1960 } 1962 bgpM2PrefixCountersAfi OBJECT-TYPE 1963 SYNTAX InetAddressType 1964 MAX-ACCESS read-only 1965 STATUS current 1966 DESCRIPTION 1967 "The AFI index of the per-peer, per prefix counters" 1968 ::= { bgpM2PrefixCountersEntry 1 } 1970 bgpM2PrefixCountersSafi OBJECT-TYPE 1971 SYNTAX BgpM2Safi 1972 MAX-ACCESS read-only 1973 STATUS current 1974 DESCRIPTION 1975 "The SAFI index of the per-peer, per prefix counters" 1976 ::= { bgpM2PrefixCountersEntry 2 } 1978 bgpM2PrefixInPrefixes OBJECT-TYPE 1979 SYNTAX Gauge32 1980 MAX-ACCESS read-only 1981 STATUS current 1982 DESCRIPTION 1983 "The number of prefixes received from a peer and are 1984 stored in the Adj-Ribs-In for that peer." 1985 -- jmh - note that we are allowing stuff to be discarded 1986 ::= { bgpM2PrefixCountersEntry 7 } 1988 bgpM2PrefixInPrefixesAccepted OBJECT-TYPE 1989 SYNTAX Gauge32 1990 MAX-ACCESS read-only 1991 STATUS current 1992 DESCRIPTION 1993 "The number of prefixes for a peer that are installed 1994 in the Adj-Ribs-In and are eligible to become active 1995 in the Loc-Rib." 1996 ::= { bgpM2PrefixCountersEntry 8 } 1998 bgpM2PrefixInPrefixesRejected OBJECT-TYPE 1999 SYNTAX Gauge32 2000 MAX-ACCESS read-only 2001 STATUS current 2002 DESCRIPTION 2003 "The number of prefixes for a peer that are installed 2004 in the Adj-Ribs-In and are NOT eligible to become active 2005 in the Loc-Rib." 2006 ::= { bgpM2PrefixCountersEntry 9 } 2008 bgpM2PrefixOutPrefixes OBJECT-TYPE 2009 SYNTAX Gauge32 2010 MAX-ACCESS read-only 2011 STATUS current 2012 DESCRIPTION 2013 "The number of prefixes for a peer that are installed 2014 in that peers Adj-Ribs-Out." 2015 ::= { bgpM2PrefixCountersEntry 10 } 2017 bgpM2PeerExtensions 2018 OBJECT IDENTIFIER ::= { bgpM2Peer 7 } 2020 bgpM2PeerNonCapExts 2021 OBJECT IDENTIFIER ::= { bgpM2PeerExtensions 1 } 2023 bgpM2PeerCapExts 2024 OBJECT IDENTIFIER ::= { bgpM2PeerExtensions 2 } 2026 -- 2027 -- Peer Route Reflection Extensions 2028 -- 2030 bgpM2PeerRouteReflectionExts 2031 OBJECT IDENTIFIER ::= { bgpM2PeerNonCapExts 2796 } 2033 bgpM2PeerReflectorClientTable OBJECT-TYPE 2034 SYNTAX SEQUENCE OF BgpM2PeerReflectorClientEntry 2035 MAX-ACCESS not-accessible 2036 STATUS current 2037 DESCRIPTION 2038 "Table of route reflection client settings on a per-peer 2039 basis." 2040 REFERENCE 2041 "RFC 2796 - BGP Route Reflection" 2042 ::= { bgpM2PeerRouteReflectionExts 1 } 2044 bgpM2PeerReflectorClientEntry OBJECT-TYPE 2045 SYNTAX BgpM2PeerReflectorClientEntry 2046 MAX-ACCESS not-accessible 2047 STATUS current 2048 DESCRIPTION 2049 "Entry containing data on a per-peer basis on whether 2050 the peer is configured as a route reflector client." 2051 REFERENCE 2052 "RFC 2796 - BGP Route Reflection" 2053 AUGMENTS { 2054 bgpM2PeerEntry 2055 } 2056 ::= { bgpM2PeerReflectorClientTable 1 } 2058 BgpM2PeerReflectorClientEntry ::= SEQUENCE { 2059 bgpM2PeerReflectorClient 2060 INTEGER 2061 } 2063 bgpM2PeerReflectorClient OBJECT-TYPE 2064 SYNTAX INTEGER { 2065 nonClient(0), 2066 client(1), 2067 meshedClient(2) 2068 } 2069 MAX-ACCESS read-only 2070 STATUS current 2071 DESCRIPTION 2072 "This value indicates whether the given peer is a 2073 reflector client of this router, or not. A value of 2074 nonClient indicates that this peer is not a reflector 2075 client. A value of client indicates that this peer is a 2076 reflector client that is not fully meshed with other 2077 reflector clients. A value of meshedClient indicates 2078 that the peer is a reflector client and is fully meshed 2079 with all other reflector clients. 2081 This value must be nonClient (0) for BGP external peers." 2082 REFERENCE 2083 "RFC 2796 - BGP Route Reflection" 2084 ::= { bgpM2PeerReflectorClientEntry 1 } 2086 -- 2087 -- Peer AS Confederations Extensions 2088 -- 2090 bgpM2PeerASConfederationExts 2091 OBJECT IDENTIFIER ::= { bgpM2PeerNonCapExts 3065 } 2093 bgpM2PeerConfedMemberTable OBJECT-TYPE 2094 SYNTAX SEQUENCE OF BgpM2PeerConfedMemberEntry 2095 MAX-ACCESS not-accessible 2096 STATUS current 2097 DESCRIPTION 2098 "Table of confederation member settings on a per-peer 2099 basis." 2100 REFERENCE 2101 "RFC 3065 - BGP Confederations" 2102 ::= { bgpM2PeerASConfederationExts 1 } 2104 bgpM2PeerConfedMemberEntry OBJECT-TYPE 2105 SYNTAX BgpM2PeerConfedMemberEntry 2106 MAX-ACCESS not-accessible 2107 STATUS current 2108 DESCRIPTION 2109 "Entry containing data on a per-peer basis on whether 2110 the peer is configured as a BGP confederation member." 2111 REFERENCE 2112 "RFC 3065 - BGP Confederations" 2113 AUGMENTS { 2114 bgpM2PeerEntry 2115 } 2116 ::= { bgpM2PeerConfedMemberTable 1 } 2118 BgpM2PeerConfedMemberEntry ::= SEQUENCE { 2119 bgpM2PeerConfedMember 2120 TruthValue 2121 } 2123 bgpM2PeerConfedMember OBJECT-TYPE 2124 SYNTAX TruthValue 2125 MAX-ACCESS read-only 2126 STATUS current 2127 DESCRIPTION 2128 "This value indicates whether the given peer is in our 2129 confederation or not." 2130 REFERENCE 2131 "RFC 3065 - BGP Confederations" 2132 ::= { bgpM2PeerConfedMemberEntry 1 } 2134 -- 2135 -- Peer configuration objects 2136 -- 2137 bgpM2PeerConfiguration 2138 OBJECT IDENTIFIER ::= { bgpM2Peer 8 } 2140 -- 2141 -- Administering activated peering sessions 2142 -- 2144 bgpM2CfgPeerAdminStatusTable OBJECT-TYPE 2145 SYNTAX SEQUENCE OF BgpM2CfgPeerAdminStatusEntry 2146 MAX-ACCESS not-accessible 2147 STATUS current 2148 DESCRIPTION 2149 "Table containing rows for administratively starting and 2150 stopping peering sessions." 2151 ::= { bgpM2PeerConfiguration 1 } 2153 bgpM2CfgPeerAdminStatusEntry OBJECT-TYPE 2154 SYNTAX BgpM2CfgPeerAdminStatusEntry 2155 MAX-ACCESS not-accessible 2156 STATUS current 2157 DESCRIPTION 2158 "Entry containing row for administratively starting and 2159 stopping peers." 2160 INDEX { 2161 bgpM2PeerIndex 2162 } 2163 ::= { bgpM2CfgPeerAdminStatusTable 1 } 2165 BgpM2CfgPeerAdminStatusEntry ::= SEQUENCE { 2166 bgpM2CfgPeerAdminStatus 2167 INTEGER 2168 } 2170 bgpM2CfgPeerAdminStatus OBJECT-TYPE 2171 SYNTAX INTEGER { 2172 stop(1), 2173 start(2) 2174 } 2175 MAX-ACCESS read-write 2176 STATUS current 2177 DESCRIPTION 2178 "This object allows the Manual Stop and Manual Start 2179 events to be sent to an activated peering session." 2180 ::= { bgpM2CfgPeerAdminStatusEntry 1 } 2182 -- 2183 -- Peer Configuration 2184 -- 2186 bgpM2CfgPeerNextIndex OBJECT-TYPE 2187 SYNTAX Integer32 (0..65535) 2188 MAX-ACCESS read-only 2189 STATUS current 2190 DESCRIPTION 2191 "This object contains the next appropriate value to 2192 use as an index for creation of a row instance in 2193 in the bgpM2CfgPeerTable. If the number of available 2194 entries in the bgpM2CfgPeerTable is exhausted, a 2195 retrieval value of this object instance will return 2196 0. A value of 0 may also be returned if the agent 2197 is otherwise incapable of bgpM2CfgPeerTable row creation 2198 at the time of bgpM2CfgPeerNextIndex retrieval." 2199 ::= { bgpM2PeerConfiguration 2 } 2201 bgpM2CfgPeerTable OBJECT-TYPE 2202 SYNTAX SEQUENCE OF BgpM2CfgPeerEntry 2203 MAX-ACCESS not-accessible 2204 STATUS current 2205 DESCRIPTION 2206 "BGP configuration peer table. 2208 This table allows the configuration of the parameters 2209 for a session with a BGP peer. 2211 +++wayne provide description of how config should be done 2212 for a peer per table." 2213 ::= { bgpM2PeerConfiguration 3 } 2215 bgpM2CfgPeerEntry OBJECT-TYPE 2216 SYNTAX BgpM2CfgPeerEntry 2217 MAX-ACCESS not-accessible 2218 STATUS current 2219 DESCRIPTION 2220 "Entry containing information set up by a management 2221 entity to configure a connection with a BGP peer." 2222 INDEX { bgpM2CfgPeerIndex } 2223 ::= { bgpM2CfgPeerTable 1 } 2225 BgpM2CfgPeerEntry ::= SEQUENCE { 2226 bgpM2CfgPeerConfiguredVersion 2227 Unsigned32, 2228 bgpM2CfgAllowVersionNegotiation 2229 TruthValue, 2230 bgpM2CfgPeerLocalAddrType 2231 InetAddressType, 2232 bgpM2CfgPeerLocalAddr 2233 InetAddress, 2234 bgpM2CfgPeerLocalAs 2235 InetAutonomousSystemNumber, 2236 bgpM2CfgPeerRemoteAddrType 2237 InetAddressType, 2238 bgpM2CfgPeerRemoteAddr 2239 InetAddress, 2240 bgpM2CfgPeerRemotePort 2241 Integer32, 2242 bgpM2CfgPeerRemoteAs 2243 InetAutonomousSystemNumber, 2244 bgpM2CfgPeerEntryStorageType 2245 StorageType, 2246 bgpM2CfgPeerError 2247 INTEGER, 2248 bgpM2CfgPeerBgpPeerEntry 2249 RowPointer, 2250 bgpM2CfgPeerRowEntryStatus 2251 RowStatus, 2252 bgpM2CfgPeerIndex 2253 Integer32, 2254 bgpM2CfgPeerStatus 2255 INTEGER 2256 } 2258 bgpM2CfgPeerConfiguredVersion OBJECT-TYPE 2259 SYNTAX Unsigned32 (1..255) 2260 MAX-ACCESS read-create 2261 STATUS current 2262 DESCRIPTION 2263 "The configured version to originally start with 2264 this peer. The BGP speaker may permit negotiation 2265 to a lower version number of the protocol depending on the 2266 set value of bgpM2CfgAllowVersionNegotiation." 2267 DEFVAL { 4 } 2268 ::= { bgpM2CfgPeerEntry 1 } 2270 bgpM2CfgAllowVersionNegotiation OBJECT-TYPE 2271 SYNTAX TruthValue 2272 MAX-ACCESS read-create 2273 STATUS current 2274 DESCRIPTION 2275 "If set to true, during session establishment with this 2276 peer, negotiation to a version lower than that specified 2277 in bgpM2CfgPeerConfiguredVersion will be allowed." 2278 DEFVAL { false } 2279 ::= { bgpM2CfgPeerEntry 2 } 2281 bgpM2CfgPeerLocalAddrType OBJECT-TYPE 2282 SYNTAX InetAddressType 2283 MAX-ACCESS read-create 2284 STATUS current 2285 DESCRIPTION 2286 "The address family of the speakers of this BGP 2287 session." 2288 ::= { bgpM2CfgPeerEntry 3 } 2290 bgpM2CfgPeerLocalAddr OBJECT-TYPE 2291 SYNTAX InetAddress (SIZE (4..20)) 2292 MAX-ACCESS read-create 2293 STATUS current 2294 DESCRIPTION 2295 "The address of the local end of the peering session." 2296 ::= { bgpM2CfgPeerEntry 4 } 2298 bgpM2CfgPeerLocalAs OBJECT-TYPE 2299 SYNTAX InetAutonomousSystemNumber 2300 MAX-ACCESS read-create 2301 STATUS current 2302 DESCRIPTION 2303 "Autonomous system represented to peer on peering 2304 session initialization. Some implementations of 2305 BGP can represent themselves as multiple ASes. 2306 These implementations can set this to an alternate 2307 autonomous system. If this object is set to zero 2308 (0) at the point this row instance is set to active, 2309 then the implementation will initialize this session 2310 representing itself as the value of bgpM2CfgLocalAs." 2311 DEFVAL { 0 } 2312 ::= { bgpM2CfgPeerEntry 5 } 2314 bgpM2CfgPeerRemoteAddrType OBJECT-TYPE 2315 SYNTAX InetAddressType 2316 MAX-ACCESS read-create 2317 STATUS current 2318 DESCRIPTION 2319 "The address family of the speakers of the remote BGP 2320 session." 2321 ::= { bgpM2CfgPeerEntry 6 } 2323 bgpM2CfgPeerRemoteAddr OBJECT-TYPE 2324 SYNTAX InetAddress (SIZE(4..20)) 2325 MAX-ACCESS read-create 2326 STATUS current 2327 DESCRIPTION 2328 "The address of the remote end (destination address 2329 of peer) for peering session." 2330 ::= { bgpM2CfgPeerEntry 7 } 2332 bgpM2CfgPeerRemotePort OBJECT-TYPE 2333 SYNTAX Integer32 (-1 | 0..65535) 2334 MAX-ACCESS read-create 2335 STATUS current 2336 DESCRIPTION 2337 "This is the remote port for the transport connection 2338 between the BGP peers. In the case of a transport for 2339 which the notion of port is irrelevant, the value of 2340 -1 can be defaulted or set." 2341 DEFVAL { -1 } 2342 ::= { bgpM2CfgPeerEntry 8 } 2344 bgpM2CfgPeerRemoteAs OBJECT-TYPE 2345 SYNTAX InetAutonomousSystemNumber 2346 MAX-ACCESS read-create 2347 STATUS current 2348 DESCRIPTION 2349 "Autonomous system number of the remote peer." 2350 ::= { bgpM2CfgPeerEntry 9 } 2352 bgpM2CfgPeerEntryStorageType OBJECT-TYPE 2353 SYNTAX StorageType 2354 MAX-ACCESS read-create 2355 STATUS current 2356 DESCRIPTION 2357 "This object type specifies the intended storage 2358 type for the bgpM2CfgPeerEntry row instance." 2359 ::= { bgpM2CfgPeerEntry 10 } 2361 bgpM2CfgPeerError OBJECT-TYPE 2362 SYNTAX INTEGER { 2363 unknown(0), 2364 notActivated (1), 2365 errDuplicatePeeringSession (2), 2366 activated (3) 2367 -- +++wayne more to follow 2368 } 2369 MAX-ACCESS read-only 2370 STATUS current 2371 DESCRIPTION 2372 "This value indicates the current error status of 2373 the row denoting the configured error status. 2375 If this row is still under creation (has not been activated 2376 bgpM2CfgPeerRowEntryStatus), then this instance will be set to 2377 not-activated (1). 2379 At the point that the row is activated, bgpM2CfgPeerError 2380 will reflect the error status of the row data itself. If 2381 there is another session already activated with the same 2382 local and remote addresses as denoted by 2383 {bgpM2CfgPeerLocalAddrType, bgpM2CfgPeerLocalAddr, 2384 bgpM2CfgPeerRemoteAddr, bgpM2CfgPeerRemotePort}, then 2385 the value of this will be set to 2386 err-duplicate-peering-session (2). 2388 If this row is associated with a peer session whose 2389 initialization has been attempted, the value will be 2390 set to activated (3) (and, bgpM2PeerCfgPeerEntry will 2391 be set to the row instance of the entry in the 2392 bgpM2PeerTable which reflects the state of the peering 2393 session). 2395 Note that this object only reflects the error as a 2396 function of the attempted activation of this row as 2397 containing data for a bgp peering session. The actual 2398 state of the session at the point of any protocol exchange 2399 or session state machine initiation is reflected in the 2400 bgpM2PeerTable row instance (as reflected through 2401 bgpM2CfgPeerPeerEntry) associated with this row instance." 2402 ::= { bgpM2CfgPeerEntry 11 } 2404 bgpM2CfgPeerBgpPeerEntry OBJECT-TYPE 2405 SYNTAX RowPointer 2406 MAX-ACCESS read-only 2407 STATUS current 2408 DESCRIPTION 2409 "Upon activation of the session data contained in this 2410 row instance, this object points to an instance of a row 2411 within the bgpM2PeerTable reflecting the session in its 2412 initializing or operational state. Retrieval of this 2413 column instance will always yield a value of {0.0} unless 2414 the session has successfully been activated (via 2415 bgpM2CfgPeerRowEntryStatus). Such row instances will always 2416 have a value of bgpM2CfgPeerError which is activated (3)." 2417 ::= { bgpM2CfgPeerEntry 12 } 2419 bgpM2CfgPeerRowEntryStatus OBJECT-TYPE 2420 SYNTAX RowStatus 2421 MAX-ACCESS read-create 2422 STATUS current 2423 DESCRIPTION 2424 "This object type is used to control creation, 2425 activation, and deletion of this row instance." 2426 -- +++wayne need better directions for agent auto-removal 2427 -- of row instances which have moved to active or error 2428 -- state 2429 ::= { bgpM2CfgPeerEntry 13 } 2431 bgpM2CfgPeerIndex OBJECT-TYPE 2432 SYNTAX Integer32 (1..65535) 2433 MAX-ACCESS accessible-for-notify 2434 STATUS current 2435 DESCRIPTION 2436 "Uniquely identifies an instance of a peer row, as 2437 an element of configuration." 2438 ::= { bgpM2CfgPeerEntry 14 } 2440 bgpM2CfgPeerStatus OBJECT-TYPE 2441 SYNTAX INTEGER { 2442 halted(1), 2443 running(2) 2444 } 2445 MAX-ACCESS read-create 2446 STATUS current 2447 DESCRIPTION 2448 "This specifies the state of the peering session upon 2449 activation. If disabled, the FSM is in the halted 2450 state and no Automatic Start events are generated. 2451 If enabled, the FSM is in the running state and 2452 Automatic Start events may be generated." 2454 ::= { bgpM2CfgPeerEntry 15 } 2456 -- 2457 -- Per-peer authentication table. 2458 -- 2460 bgpM2CfgPeerAuthTable OBJECT-TYPE 2461 SYNTAX SEQUENCE OF BgpM2CfgPeerAuthEntry 2462 MAX-ACCESS not-accessible 2463 STATUS current 2464 DESCRIPTION 2465 "Table contain per peer configuration for BGP Authentication." 2466 ::= { bgpM2PeerConfiguration 4 } 2468 bgpM2CfgPeerAuthEntry OBJECT-TYPE 2469 SYNTAX BgpM2CfgPeerAuthEntry 2470 MAX-ACCESS not-accessible 2471 STATUS current 2472 DESCRIPTION 2473 "Entry containing information about a peer's BGP Authentication 2474 configuration." 2475 AUGMENTS { 2476 bgpM2CfgPeerEntry 2477 } 2478 ::= { bgpM2CfgPeerAuthTable 1 } 2480 BgpM2CfgPeerAuthEntry ::= SEQUENCE { 2481 bgpM2CfgPeerAuthEnabled 2482 TruthValue, 2483 bgpM2CfgPeerAuthCode 2484 Unsigned32, 2485 bgpM2CfgPeerAuthValue 2486 OCTET STRING 2487 } 2489 bgpM2CfgPeerAuthEnabled OBJECT-TYPE 2490 SYNTAX TruthValue 2491 MAX-ACCESS read-create 2492 STATUS current 2493 DESCRIPTION 2494 "This value is true if BGP Authentication is enabled for 2495 this peer. This is the authentication mechanism 2496 documented in the base BGP specification, not the MD5 2497 session protection mechanism." 2499 DEFVAL { 2500 false 2501 } 2502 ::= { bgpM2CfgPeerAuthEntry 1 } 2504 bgpM2CfgPeerAuthCode OBJECT-TYPE 2505 SYNTAX Unsigned32(0..255) 2506 MAX-ACCESS read-create 2507 STATUS current 2508 DESCRIPTION 2509 "The authentication code for the BGP Authentication 2510 mechanism." 2511 REFERENCE 2512 "draft-ietf-idr-bgp4-17.txt, Sec. 4.1.a" 2513 ::= { bgpM2CfgPeerAuthEntry 2 } 2515 bgpM2CfgPeerAuthValue OBJECT-TYPE 2516 SYNTAX OCTET STRING (SIZE(0..252)) 2517 MAX-ACCESS read-create 2518 STATUS current 2519 DESCRIPTION 2520 "The authentication payload for the BGP authentication 2521 mechanism. This value has semantic meaning within 2522 the context of the authentication code." 2523 REFERENCE 2524 "draft-ietf-idr-bgp4-17.txt, Sec. 4.1.a" 2525 ::= { bgpM2CfgPeerAuthEntry 3 } 2527 -- 2528 -- Per-peer timers table 2529 -- 2531 bgpM2CfgPeerTimersTable OBJECT-TYPE 2532 SYNTAX SEQUENCE OF BgpM2CfgPeerTimersEntry 2533 MAX-ACCESS not-accessible 2534 STATUS current 2535 DESCRIPTION 2536 "Table for configuration of per-peer timers." 2537 ::= { bgpM2PeerConfiguration 5 } 2539 bgpM2CfgPeerTimersEntry OBJECT-TYPE 2540 SYNTAX BgpM2CfgPeerTimersEntry 2541 MAX-ACCESS not-accessible 2542 STATUS current 2543 DESCRIPTION 2544 "Entry containing per-peer timer configuration." 2545 AUGMENTS { 2546 bgpM2CfgPeerEntry 2547 } 2548 ::= { bgpM2CfgPeerTimersTable 1 } 2550 BgpM2CfgPeerTimersEntry ::= SEQUENCE { 2551 bgpM2CfgPeerConnectRetryInterval 2552 Unsigned32, 2553 bgpM2CfgPeerHoldTimeConfigured 2554 Unsigned32, 2555 bgpM2CfgPeerKeepAliveConfigured 2556 Unsigned32, 2557 bgpM2CfgPeerMinASOrigInterval 2558 Unsigned32, 2559 bgpM2CfgPeerMinRouteAdverInter 2560 Unsigned32 2561 } 2563 bgpM2CfgPeerConnectRetryInterval OBJECT-TYPE 2564 SYNTAX Unsigned32 (1..65535) 2565 MAX-ACCESS read-create 2566 STATUS current 2567 DESCRIPTION 2568 "Time interval in seconds for the ConnectRetry 2569 timer. The suggested value for this timer is 120 2570 seconds." 2571 DEFVAL { 2572 120 2573 } 2574 ::= { bgpM2CfgPeerTimersEntry 1 } 2576 bgpM2CfgPeerHoldTimeConfigured OBJECT-TYPE 2577 SYNTAX Unsigned32 ( 0 | 3..65535 ) 2578 MAX-ACCESS read-create 2579 STATUS current 2580 DESCRIPTION 2581 "Time interval in seconds for the Hold Time configured 2582 for this BGP speaker with this peer. This value 2583 is placed in an OPEN message sent to this peer by 2584 this BGP speaker, and is compared with the Hold 2585 Time field in an OPEN message received from the 2586 peer when determining the Hold Time (bgpM2PeerHoldTime) 2587 with the peer. This value must not be less than 2588 three seconds if it is not zero (0) in which case 2589 the Hold Time is NOT to be established with the 2590 peer. The suggested value for this timer is 90 2591 seconds." 2592 REFERENCE 2593 "draft-ietf-idr-bgp4-17.txt, Appendix 6.4" 2594 DEFVAL { 2595 90 2596 } 2597 ::= { bgpM2CfgPeerTimersEntry 2 } 2599 bgpM2CfgPeerKeepAliveConfigured OBJECT-TYPE 2600 SYNTAX Unsigned32 ( 0 | 1..21845 ) 2601 MAX-ACCESS read-create 2602 STATUS current 2603 DESCRIPTION 2604 "Time interval in seconds for the KeepAlive timer 2605 configured for this BGP speaker with this peer. 2606 The value of this object will only determine the 2607 KEEPALIVE messages frequency relative to the value 2608 specified in bgpM2PeerHoldTimeConfigured; the actual 2609 time interval for the KEEPALIVE messages is indicated 2610 by bgpM2PeerKeepAlive. A reasonable maximum value 2611 for this timer would be configured to be one third 2612 of that of bgpM2PeerHoldTimeConfigured. 2614 If the value of this object is zero (0), no 2615 periodical KEEPALIVE messages are sent to the peer 2616 after the BGP connection has been established. 2617 The suggested value for this timer is 30 seconds." 2618 REFERENCE 2619 "draft-ietf-idr-bgp4-17.txt, Appendix 6.4" 2620 DEFVAL { 2621 30 2622 } 2623 ::= { bgpM2CfgPeerTimersEntry 3 } 2625 bgpM2CfgPeerMinASOrigInterval OBJECT-TYPE 2626 SYNTAX Unsigned32 (0..65535) 2627 MAX-ACCESS read-create 2628 STATUS current 2629 DESCRIPTION 2630 "Time interval in seconds for the MinASOriginationInterval 2631 timer. The suggested value for this timer is 15 2632 seconds." 2633 DEFVAL { 2634 15 2635 } 2636 ::= { bgpM2CfgPeerTimersEntry 4 } 2638 bgpM2CfgPeerMinRouteAdverInter OBJECT-TYPE 2639 SYNTAX Unsigned32 (0..65535) 2640 MAX-ACCESS read-create 2641 STATUS current 2642 DESCRIPTION 2643 "Time interval in seconds for the 2644 MinRouteAdvertisementInterval timer. The suggested 2645 value for this timer is 30 seconds." 2646 DEFVAL { 2647 30 2648 } 2649 ::= { bgpM2CfgPeerTimersEntry 5 } 2651 -- 2652 -- Per-peer configuration extensions 2653 -- 2655 bgpM2CfgPeerExtensions 2656 OBJECT IDENTIFIER ::= { bgpM2PeerConfiguration 6 } 2658 bgpM2CfgPeerNonCapExts 2659 OBJECT IDENTIFIER ::= { bgpM2CfgPeerExtensions 1 } 2661 bgpM2CfgPeerCapExts 2662 OBJECT IDENTIFIER ::= { bgpM2CfgPeerExtensions 2 } 2664 -- 2665 -- Peer route reflection configuration 2666 -- 2668 bgpM2CfgPeerRouteReflectionExts 2669 OBJECT IDENTIFIER ::= { bgpM2CfgPeerNonCapExts 2796 } 2671 bgpM2CfgPeerReflectorClientTable OBJECT-TYPE 2672 SYNTAX SEQUENCE OF BgpM2CfgPeerReflectorClientEntry 2673 MAX-ACCESS not-accessible 2674 STATUS current 2675 DESCRIPTION 2676 "Table of route reflection client settings on a per-peer 2677 basis." 2678 REFERENCE 2679 "RFC 2796 - BGP Route Reflection" 2680 ::= { bgpM2CfgPeerRouteReflectionExts 1 } 2682 bgpM2CfgPeerReflectorClientEntry OBJECT-TYPE 2683 SYNTAX BgpM2CfgPeerReflectorClientEntry 2684 MAX-ACCESS not-accessible 2685 STATUS current 2686 DESCRIPTION 2687 "Entry containing data on a per-peer basis on whether 2688 the peer is configured as a route reflector client." 2689 REFERENCE 2690 "RFC 2796 - BGP Route Reflection" 2691 AUGMENTS { 2692 bgpM2CfgPeerEntry 2693 } 2694 ::= { bgpM2CfgPeerReflectorClientTable 1 } 2696 BgpM2CfgPeerReflectorClientEntry ::= SEQUENCE { 2697 bgpM2CfgPeerReflectorClient 2698 INTEGER 2699 } 2701 bgpM2CfgPeerReflectorClient OBJECT-TYPE 2702 SYNTAX INTEGER { 2703 nonClient(0), 2704 client(1), 2705 meshedClient(2) 2706 } 2707 MAX-ACCESS read-create 2708 STATUS current 2709 DESCRIPTION 2710 "This value indicates whether the given peer is a 2711 reflector client of this router, or not. A value of 2712 nonClient indicates that this peer is not a reflector 2713 client. A value of client indicates that this peer is a 2714 reflector client that is not fully meshed with other 2715 reflector clients. A value of meshedClient indicates 2716 that the peer is a reflector client and is fully meshed 2717 with all other reflector clients. 2719 This value must be nonClient (0) for BGP external peers." 2720 REFERENCE 2721 "RFC 2796 - BGP Route Reflection" 2723 ::= { bgpM2CfgPeerReflectorClientEntry 1 } 2725 -- 2726 -- Peer AS Confederations Extensions 2727 -- 2729 bgpM2CfgPeerASConfederationExts 2730 OBJECT IDENTIFIER ::= { bgpM2CfgPeerNonCapExts 3065 } 2732 bgpM2CfgPeerConfedMemberTable OBJECT-TYPE 2733 SYNTAX SEQUENCE OF BgpM2CfgPeerConfedMemberEntry 2734 MAX-ACCESS not-accessible 2735 STATUS current 2736 DESCRIPTION 2737 "Table of confederation member settings on a per-peer 2738 basis." 2739 REFERENCE 2740 "RFC 3065 - BGP Confederations" 2741 ::= { bgpM2CfgPeerASConfederationExts 1 } 2743 bgpM2CfgPeerConfedMemberEntry OBJECT-TYPE 2744 SYNTAX BgpM2CfgPeerConfedMemberEntry 2745 MAX-ACCESS not-accessible 2746 STATUS current 2747 DESCRIPTION 2748 "Entry containing data on a per-peer basis on whether 2749 the peer is configured as a BGP confederation member." 2750 REFERENCE 2751 "RFC 3065 - BGP Confederations" 2752 AUGMENTS { 2753 bgpM2PeerEntry 2754 } 2755 ::= { bgpM2CfgPeerConfedMemberTable 1 } 2757 BgpM2CfgPeerConfedMemberEntry ::= SEQUENCE { 2758 bgpM2CfgPeerConfedMember 2759 TruthValue 2760 } 2762 bgpM2CfgPeerConfedMember OBJECT-TYPE 2763 SYNTAX TruthValue 2764 MAX-ACCESS read-create 2765 STATUS current 2766 DESCRIPTION 2767 "This value indicates whether the given peer is in our 2768 confederation or not." 2769 REFERENCE 2770 "RFC 3065 - BGP Confederations" 2771 ::= { bgpM2CfgPeerConfedMemberEntry 1 } 2773 -- 2774 -- BGP NLRI Data 2775 -- 2777 bgpM2Rib 2778 OBJECT IDENTIFIER ::= { bgpM2 3 } 2780 -- 2781 -- NLRI Table 2782 -- 2784 bgpM2NlriTable OBJECT-TYPE 2785 SYNTAX SEQUENCE OF BgpM2NlriEntry 2786 MAX-ACCESS not-accessible 2787 STATUS current 2788 DESCRIPTION 2789 "The BGP-4 Received Path Attribute Table contains 2790 information about paths to destination networks 2791 received from all BGP4 peers. Collectively, this 2792 represents the Adj-Ribs-In. The route where 2793 bgpM2NlriBest is TRUE represents, for this NLRI, 2794 the route that is installed in the LocRib from the 2795 Adj-Ribs-In." 2796 ::= { bgpM2Rib 1 } 2798 bgpM2NlriEntry OBJECT-TYPE 2799 SYNTAX BgpM2NlriEntry 2800 MAX-ACCESS not-accessible 2801 STATUS current 2802 DESCRIPTION 2803 "Information about a path to a network." 2804 INDEX { 2805 bgpM2PeerIndex, 2806 bgpM2NlriAfi, 2807 bgpM2NlriSafi, 2808 bgpM2NlriPrefix, 2809 bgpM2NlriPrefixLen, 2810 bgpM2NlriIndex 2812 } 2813 ::= { bgpM2NlriTable 1 } 2815 BgpM2NlriEntry ::= SEQUENCE { 2816 bgpM2NlriIndex 2817 Unsigned32, 2818 bgpM2NlriAfi 2819 InetAddressType, 2820 bgpM2NlriSafi 2821 BgpM2Safi, 2822 bgpM2NlriPrefix 2823 InetAddress, 2824 bgpM2NlriPrefixLen 2825 InetAddressPrefixLength, 2826 bgpM2NlriBest 2827 TruthValue, 2828 bgpM2NlriCalcLocalPref 2829 Unsigned32, 2830 bgpM2PathAttrIndex 2831 Unsigned32, 2832 bgpM2NlriOpaqueType 2833 INTEGER, 2834 bgpM2NlriOpaquePointer 2835 RowPointer 2836 } 2838 bgpM2NlriIndex OBJECT-TYPE 2839 SYNTAX Unsigned32 2840 MAX-ACCESS read-only 2841 STATUS current 2842 DESCRIPTION 2843 "This index allows for multiple instances of a base 2844 prefix for a certain AFI SAFI from a given peer. 2845 This is currently useful for two things: 2846 1. Allowing for a peer in future implementations to 2847 send more than a single route instance. 2848 2. Allow for extensions which extend the NLRI field 2849 to send the same prefix while utilizing other 2850 extension specific information. An example of 2851 this is RFC 3107 - Carrying MPLS labels in BGP." 2852 REFERENCE 2853 "RFC 3107 - Carrying Label Information in BGP-4" 2854 ::= { bgpM2NlriEntry 1 } 2856 bgpM2NlriAfi OBJECT-TYPE 2857 SYNTAX InetAddressType 2858 MAX-ACCESS read-only 2859 STATUS current 2860 DESCRIPTION 2861 "The address family of the prefix for this NLRI." 2862 ::= { bgpM2NlriEntry 2 } 2864 bgpM2NlriSafi OBJECT-TYPE 2865 SYNTAX BgpM2Safi 2866 MAX-ACCESS read-only 2867 STATUS current 2868 DESCRIPTION 2869 "The subsequent address family of the prefix for 2870 this NLRI" 2871 REFERENCE 2872 "RFC 2858 - Multiprotocol Extensions for BGP-4" 2873 ::= { bgpM2NlriEntry 3 } 2875 bgpM2NlriPrefix OBJECT-TYPE 2876 SYNTAX InetAddress (SIZE (4..20)) 2877 MAX-ACCESS read-only 2878 STATUS current 2879 DESCRIPTION 2880 "An IP address prefix in the Network Layer 2881 Reachability Information field. This object 2882 is an IP address containing the prefix with 2883 length specified by 2884 bgpM2PathAttrAddrPrefixLen. 2885 Any bits beyond the length specified by 2886 bgpM2PathAttrAddrPrefixLen are zeroed." 2887 ::= { bgpM2NlriEntry 4 } 2889 bgpM2NlriPrefixLen OBJECT-TYPE 2890 SYNTAX InetAddressPrefixLength 2891 MAX-ACCESS read-only 2892 STATUS current 2893 DESCRIPTION 2894 "Length in bits of the address prefix in 2895 the Network Layer Reachability Information field." 2896 ::= { bgpM2NlriEntry 5 } 2898 bgpM2NlriBest OBJECT-TYPE 2899 SYNTAX TruthValue 2900 MAX-ACCESS read-only 2901 STATUS current 2902 DESCRIPTION 2903 "An indication of whether or not this route 2904 was chosen as the best BGP4 route." 2905 ::= { bgpM2NlriEntry 6 } 2907 bgpM2NlriCalcLocalPref OBJECT-TYPE 2908 SYNTAX Unsigned32 2909 MAX-ACCESS read-only 2910 STATUS current 2911 DESCRIPTION 2912 "The degree of preference calculated by the 2913 receiving BGP4 speaker for an advertised 2914 route." 2915 ::= { bgpM2NlriEntry 7 } 2917 bgpM2PathAttrIndex OBJECT-TYPE 2918 SYNTAX Unsigned32 2919 MAX-ACCESS read-only 2920 STATUS current 2921 DESCRIPTION 2922 "This value is a unique index for the per-NLRI entry 2923 in the bgpM2PeerAttrTable. It is assigned by the 2924 agent at the point of creation of the bgpM2PeerAttrTable 2925 row entry. While its value is guaranteed to be unique 2926 at any time, it is otherwise opaque to the management 2927 application with respect to its value or the contiguity 2928 of bgpM2PeerAttrIndex row instance values across rows 2929 of the bgpM2PeerAttrTable. It is used to provide an 2930 index structure for other tables whose data is logically 2931 per-peer, per-NLRI." 2932 ::= { bgpM2NlriEntry 8 } 2934 bgpM2NlriOpaqueType OBJECT-TYPE 2935 SYNTAX INTEGER { 2936 none(0), 2937 bgpMplsLabelStack(1) 2938 } 2939 MAX-ACCESS read-only 2940 STATUS current 2941 DESCRIPTION 2942 "This object enumerates the type of the row that is 2943 pointed to in the table row bgpM2NlriOpaquePointer 2944 instance, if bgpM2NlriOpaquePointer is in fact not 2945 a zero length. bgpM2NlriOpaqueType is necessary since 2946 the data referenced by bgpM2NlriOpaquePointer is 2947 opaque to BGP. For example, in the case of RFC 3107, 2948 the label stack that is pointed to may occur in the 2949 mplsLabelStackTable from the MPLS-LSR-MIB, and the 2950 instance value of bgpM2NlriOpaqueType would be 2951 bgpMplsLabelStack(1)." 2952 REFERENCE 2953 "RFC 3107 - Carrying Label Information in BGP-4 2954 draft-ietf-mpls-lsr-mib-08.txt" 2955 ::= { bgpM2NlriEntry 9 } 2957 bgpM2NlriOpaquePointer OBJECT-TYPE 2958 SYNTAX RowPointer 2959 MAX-ACCESS read-only 2960 STATUS current 2961 DESCRIPTION 2962 "Pointer to a row that decomposes the data that is 2963 opaque to the BGP MIB but is sent in the NLRI. 2964 This RowPointer has zero (0) length data instance 2965 if bgpM2NlriOpaqueType is none." 2966 ::= { bgpM2NlriEntry 10 } 2968 -- 2969 -- Adj-Ribs-Out Table 2970 -- 2972 bgpM2AdjRibsOutTable OBJECT-TYPE 2973 SYNTAX SEQUENCE OF BgpM2AdjRibsOutEntry 2974 MAX-ACCESS not-accessible 2975 STATUS current 2976 DESCRIPTION 2977 "This table contains on a per-peer basis one or more 2978 routes from the bgpM2NlriTable that have been 2979 placed in this peer's Adj-Ribs-Out." 2980 REFERENCE 2981 "draft-ietf-idr-bgp4-17.txt, Sec. 3.2" 2982 ::= { bgpM2Rib 2 } 2984 bgpM2AdjRibsOutEntry OBJECT-TYPE 2985 SYNTAX BgpM2AdjRibsOutEntry 2986 MAX-ACCESS not-accessible 2987 STATUS current 2988 DESCRIPTION 2989 "List of BGP routes that have been placed into a 2990 peer's Adj-Ribs-Out." 2992 INDEX { 2993 bgpM2PeerIndex, 2994 bgpM2NlriAfi, 2995 bgpM2NlriSafi, 2996 bgpM2NlriPrefix, 2997 bgpM2NlriPrefixLen, 2998 bgpM2AdjRibsOutIndex 2999 } 3000 ::= { bgpM2AdjRibsOutTable 1 } 3002 BgpM2AdjRibsOutEntry ::= SEQUENCE { 3003 bgpM2AdjRibsOutIndex 3004 Unsigned32, 3005 bgpM2AdjRibsOutRoute 3006 RowPointer 3007 } 3009 bgpM2AdjRibsOutIndex OBJECT-TYPE 3010 SYNTAX Unsigned32 3011 MAX-ACCESS read-only 3012 STATUS current 3013 DESCRIPTION 3014 "Certain extensions to BGP permit multiple instance of 3015 a per afi, per safi prefix to be advertised to a peer. 3016 This object allows the enumeration of them." 3017 ::= { bgpM2AdjRibsOutEntry 1 } 3019 bgpM2AdjRibsOutRoute OBJECT-TYPE 3020 SYNTAX RowPointer 3021 MAX-ACCESS read-only 3022 STATUS current 3023 DESCRIPTION 3024 "This object points to the route in the bgpM2NlriTable 3025 that corresponds to the entry in the peer's 3026 Adj-Rib-Out. Outgoing route maps are not 3027 reflected at this point as those are part of the 3028 Update-Send process." 3029 REFERENCE 3030 "draft-ietf-idr-bgp4-17.txt, Sec. 9.2" 3031 ::= { bgpM2AdjRibsOutEntry 2 } 3033 -- 3034 -- BGP Rib Path Attributes Table 3035 -- 3036 -- 3037 -- Path Attribute Counter 3038 -- 3040 bgpM2PathAttrCount OBJECT-TYPE 3041 SYNTAX Counter32 3042 MAX-ACCESS read-only 3043 STATUS current 3044 DESCRIPTION 3045 "The number of entries in the bgpM2PathAttrTable." 3046 ::= { bgpM2Rib 3 } 3048 -- 3049 -- Path Attributes Table 3050 -- 3052 bgpM2PathAttrTable OBJECT-TYPE 3053 SYNTAX SEQUENCE OF BgpM2PathAttrEntry 3054 MAX-ACCESS not-accessible 3055 STATUS current 3056 DESCRIPTION 3057 "Provides per advertised network-prefix attribute data, 3058 as advertised over a peering session." 3059 ::= { bgpM2Rib 4 } 3061 bgpM2PathAttrEntry OBJECT-TYPE 3062 SYNTAX BgpM2PathAttrEntry 3063 MAX-ACCESS not-accessible 3064 STATUS current 3065 DESCRIPTION 3066 "Each entry contains data about a given network 3067 prefix, per-prefix and per-advertising peer." 3068 INDEX { 3069 bgpM2PathAttrIndex 3070 } 3071 ::= { bgpM2PathAttrTable 1 } 3073 BgpM2PathAttrEntry ::= SEQUENCE { 3074 bgpM2PathAttrOrigin 3075 INTEGER, 3076 bgpM2PathAttrNextHopAddrType 3077 InetAddressType, 3078 bgpM2PathAttrNextHop 3079 InetAddress, 3080 bgpM2PathAttrMedPresent 3081 TruthValue, 3082 bgpM2PathAttrMed 3083 Unsigned32, 3084 bgpM2PathAttrLocalPrefPresent 3085 TruthValue, 3086 bgpM2PathAttrLocalPref 3087 Unsigned32, 3088 bgpM2PathAttrAtomicAggregate 3089 INTEGER, 3090 bgpM2PathAttrAggregatorAS 3091 InetAutonomousSystemNumber, 3092 bgpM2PathAttrAggregatorAddr 3093 BgpM2Identifier, 3094 bgpM2AsPathCalcLength 3095 Unsigned32, 3096 bgpM2AsPathString 3097 SnmpAdminString, 3098 bgpM2AsPathIndex 3099 Unsigned32 3100 } 3102 bgpM2PathAttrOrigin OBJECT-TYPE 3103 SYNTAX INTEGER { 3104 igp(1),-- networks are interior 3105 egp(2),-- networks learned via the EGP protocol 3106 incomplete(3) -- undetermined 3107 } 3108 MAX-ACCESS read-only 3109 STATUS current 3110 DESCRIPTION 3111 "The ultimate origin of the path information." 3112 ::= { bgpM2PathAttrEntry 1 } 3114 bgpM2PathAttrNextHopAddrType OBJECT-TYPE 3115 SYNTAX InetAddressType 3116 MAX-ACCESS read-only 3117 STATUS current 3118 DESCRIPTION 3119 "The address family of the address for 3120 the border router that should be used 3121 to access the destination network." 3122 ::= { bgpM2PathAttrEntry 2 } 3124 bgpM2PathAttrNextHop OBJECT-TYPE 3125 SYNTAX InetAddress (SIZE(4..20)) 3126 MAX-ACCESS read-only 3127 STATUS current 3128 DESCRIPTION 3129 "The address of the border router that 3130 should be used to access the destination 3131 network. This address is the nexthop 3132 address received in the UPDATE packet. 3133 The address family of this object will be the 3134 same as that of the prefix in this row. 3136 Note that for RFC2545 style double nexthops, 3137 this object will always contain the global scope 3138 nexthop. bgpM2LinkLocalNextHopTable will contain 3139 the linklocal scope nexthop. 3141 In the case that the mechanism documented in 3142 draft-kato-bgp-ipv6-link-local-00.txt is used and 3143 only a link local nexthop has been sent, , 3144 bgpM2LinkLocalNextHopPresent will be false 3145 and bgpM2PathAttrNextHop will contain the link local 3146 nexthop." 3147 ::= { bgpM2PathAttrEntry 3 } 3149 bgpM2PathAttrMedPresent OBJECT-TYPE 3150 SYNTAX TruthValue 3151 MAX-ACCESS read-only 3152 STATUS current 3153 DESCRIPTION 3154 "Whether or not the MED value is present. 3155 If it is not present, the bgpM2PathAttrMed 3156 object has no useful value and should be set to 0." 3157 ::= { bgpM2PathAttrEntry 4 } 3159 bgpM2PathAttrMed OBJECT-TYPE 3160 SYNTAX Unsigned32 3161 MAX-ACCESS read-only 3162 STATUS current 3163 DESCRIPTION 3164 "This metric is used to discriminate 3165 between multiple exit points to an 3166 adjacent autonomous system." 3167 ::= { bgpM2PathAttrEntry 5 } 3169 bgpM2PathAttrLocalPrefPresent OBJECT-TYPE 3170 SYNTAX TruthValue 3171 MAX-ACCESS read-only 3172 STATUS current 3173 DESCRIPTION 3174 "Whether or not the LocalPref value is present. 3175 If it is not present, the bgpM2PathAttrLocalPref 3176 object has no useful value and should be set to 0." 3177 ::= { bgpM2PathAttrEntry 6 } 3179 bgpM2PathAttrLocalPref OBJECT-TYPE 3180 SYNTAX Unsigned32 3181 MAX-ACCESS read-only 3182 STATUS current 3183 DESCRIPTION 3184 "The originating BGP4 speakers degree of 3185 preference for an advertised route." 3186 ::= { bgpM2PathAttrEntry 7 } 3188 bgpM2PathAttrAtomicAggregate OBJECT-TYPE 3189 SYNTAX INTEGER { 3190 atomicAggregatePresent(1), 3191 atomicAggregateMissing(2) 3192 } 3193 MAX-ACCESS read-only 3194 STATUS current 3195 DESCRIPTION 3196 "When this object is set to atomicAggregatePresent, 3197 the ATOMIC_AGGREGATE Path Attribute is present 3198 and indicates that the NLRI MUST NOT be made 3199 more specific." 3200 ::= { bgpM2PathAttrEntry 8 } 3202 bgpM2PathAttrAggregatorAS OBJECT-TYPE 3203 SYNTAX InetAutonomousSystemNumber 3204 MAX-ACCESS read-only 3205 STATUS current 3206 DESCRIPTION 3207 "The AS number of the last BGP4 speaker that 3208 performed route aggregation. A value of 3209 zero (0) indicates the absence of this 3210 attribute. 3212 Note propagation of AS of zero is illegal in 3213 the Internet." 3214 ::= { bgpM2PathAttrEntry 9 } 3216 bgpM2PathAttrAggregatorAddr OBJECT-TYPE 3217 SYNTAX BgpM2Identifier 3218 MAX-ACCESS read-only 3219 STATUS current 3220 DESCRIPTION 3221 "The IP address of the last BGP4 speaker 3222 that performed route aggregation. A 3223 value of 0.0.0.0 indicates the absence 3224 of this attribute." 3225 ::= { bgpM2PathAttrEntry 10 } 3227 bgpM2AsPathCalcLength OBJECT-TYPE 3228 SYNTAX Unsigned32 3229 MAX-ACCESS read-only 3230 STATUS current 3231 DESCRIPTION 3232 "This value represents the calculated length of the 3233 AS Path according to the rules of the BGP specification. 3234 This value is used in route selection." 3235 REFERENCE 3236 "draft-ietf-idr-bgp4-17.txt, Sec. 9.1.2.2.a" 3237 ::= { bgpM2PathAttrEntry 11 } 3239 bgpM2AsPathString OBJECT-TYPE 3240 SYNTAX SnmpAdminString 3241 MAX-ACCESS read-only 3242 STATUS current 3243 DESCRIPTION 3244 "This is a string depicting the autonomous system 3245 path to this network which was received from the 3246 peer which advertised it. The format of the string 3247 is implementation-dependent, and should be designed 3248 for operator readability." 3249 ::= { bgpM2PathAttrEntry 12 } 3251 bgpM2AsPathIndex OBJECT-TYPE 3252 SYNTAX Unsigned32 3253 MAX-ACCESS read-only 3254 STATUS current 3255 DESCRIPTION 3256 "This value is a unique index for the decomposed AS Path 3257 in the bgpM2AsPathTable. It is assigned by the 3258 agent at the point of creation of the bgpM2AsPathTable 3259 row entry. While its value is guaranteed to be unique 3260 at any time, it is otherwise opaque to the management 3261 application with respect to its value or the contiguity 3262 of bgpM2AsPathIndex row instance values across rows 3263 of the bgpM2AsPathTable." 3264 ::= { bgpM2PathAttrEntry 13 } 3266 -- 3267 -- As-4 byte AS_PATH 3268 -- 3270 bgpM2AsPath4byteTable OBJECT-TYPE 3271 SYNTAX SEQUENCE OF BgpM2AsPath4byteEntry 3272 MAX-ACCESS not-accessible 3273 STATUS current 3274 DESCRIPTION 3275 "This table is present for BGP speakers that support 3276 the AS 4byte specification and are functioning as 3277 a router between 2-byte and 4-byte AS space." 3278 REFERENCE 3279 "draft-ietf-idr-as4bytes-04.txt - BGP support for 3280 four-octet AS number space" 3281 ::= { bgpM2Rib 5 } 3283 bgpM2AsPath4byteEntry OBJECT-TYPE 3284 SYNTAX BgpM2AsPath4byteEntry 3285 MAX-ACCESS not-accessible 3286 STATUS current 3287 DESCRIPTION 3288 "Each row contains the information for the AS 4-byte 3289 extension's NEW_AS_PATH and NEW_AGGREGATOR attributes." 3290 AUGMENTS { 3291 bgpM2PathAttrEntry 3292 } 3293 ::= { bgpM2AsPath4byteTable 1 } 3295 BgpM2AsPath4byteEntry ::= SEQUENCE { 3296 bgpM2AsPath4bytePathPresent 3297 TruthValue, 3298 bgpM2AsPath4byteAggregatorAS 3299 InetAutonomousSystemNumber, 3300 bgpM2AsPath4byteCalcLength 3301 Unsigned32, 3302 bgpM2AsPath4byteString 3303 SnmpAdminString, 3304 bgpM2AsPath4byteIndex 3305 Unsigned32 3307 } 3309 bgpM2AsPath4bytePathPresent OBJECT-TYPE 3310 SYNTAX TruthValue 3311 MAX-ACCESS read-only 3312 STATUS current 3313 DESCRIPTION 3314 "This value may only be true if this BGP Speaker 3315 is functioning as a router between ASs that 3316 are in 2-byte and 4-byte AS space. If this 3317 value is true, then the NEW_AS_PATH attributes 3318 are present and the 4-byte versions of the 3319 appropriate path attributes are in this row. 3321 If this value is false, then the following values 3322 will be present in the row: 3324 bgpM2PathAttrAggregatorAS - zero (0). 3325 bgpM2AsPathCalcLength - zero (0). 3326 bgpM2AsPathString - zero (0) length string. 3327 bgpM2AsPathIndex - zero (0)." 3328 ::= { bgpM2AsPath4byteEntry 1 } 3330 bgpM2AsPath4byteAggregatorAS OBJECT-TYPE 3331 SYNTAX InetAutonomousSystemNumber 3332 MAX-ACCESS read-only 3333 STATUS current 3334 DESCRIPTION 3335 "The NEW_AGGREGATOR AS number of the last BGP4 speaker 3336 that performed route aggregation. A value of 3337 zero (0) indicates the absence of this 3338 attribute. 3340 Note propagation of AS of zero is illegal in 3341 the Internet." 3342 ::= { bgpM2AsPath4byteEntry 2 } 3344 bgpM2AsPath4byteCalcLength OBJECT-TYPE 3345 SYNTAX Unsigned32 3346 MAX-ACCESS read-only 3347 STATUS current 3348 DESCRIPTION 3349 "This value represents the calculated length of the 3350 NEW_AS_PATH according to the rules of the BGP specification. 3351 This value is used in route selection." 3353 REFERENCE 3354 "draft-ietf-idr-bgp4-17.txt, Sec. 9.1.2.2.a" 3355 ::= { bgpM2AsPath4byteEntry 3 } 3357 bgpM2AsPath4byteString OBJECT-TYPE 3358 SYNTAX SnmpAdminString 3359 MAX-ACCESS read-only 3360 STATUS current 3361 DESCRIPTION 3362 "This is a string depicting the autonomous system 3363 path to this network which was received from the 3364 peer which advertised it. The format of the string 3365 is implementation-dependent, and should be designed 3366 for operator readability." 3367 ::= { bgpM2AsPath4byteEntry 4 } 3369 bgpM2AsPath4byteIndex OBJECT-TYPE 3370 SYNTAX Unsigned32 3371 MAX-ACCESS read-only 3372 STATUS current 3373 DESCRIPTION 3374 "This value is a unique index for the decomposed AS Path 3375 in the bgpM2AsPathTable. It is assigned by the 3376 agent at the point of creation of the bgpM2AsPathTable 3377 row entry. While its value is guaranteed to be unique 3378 at any time, it is otherwise opaque to the management 3379 application with respect to its value or the contiguity 3380 of bgpM2AsPathIndex row instance values across rows 3381 of the bgpM2AsPathTable. " 3382 ::= { bgpM2AsPath4byteEntry 5 } 3384 -- BGP 4 Path attribute AS Path Table. There is one row in 3385 -- this table for each AS which is advertised for a given 3386 -- route as provided from a peer. 3388 -- JMH 3389 -- We need one of these for the NewAsPath for the 4byte draft 3391 bgpM2AsPathTable OBJECT-TYPE 3392 SYNTAX SEQUENCE OF BgpM2AsPathEntry 3393 MAX-ACCESS not-accessible 3394 STATUS current 3395 DESCRIPTION 3396 "The BGP-4 Path Attribute AS Path Table 3397 contains the per network path (NLRI) 3398 AS PATH data received from the 3399 advertising BGP peer." 3400 ::= { bgpM2Rib 6 } 3402 bgpM2AsPathTableEntry OBJECT-TYPE 3403 SYNTAX BgpM2AsPathEntry 3404 MAX-ACCESS not-accessible 3405 STATUS current 3406 DESCRIPTION 3407 "Information about an AS path provided with a path to 3408 a network." 3409 INDEX { 3410 bgpM2PathAttrIndex, 3411 bgpM2AsPathSegmentIndex, 3412 bgpM2AsPathElementIndex, 3413 bgpM2AsPathElementValue 3414 } 3415 ::= { bgpM2AsPathTable 1 } 3417 BgpM2AsPathEntry ::= SEQUENCE { 3418 bgpM2AsPathSegmentIndex 3419 Unsigned32, 3420 bgpM2AsPathElementIndex 3421 Unsigned32, 3422 bgpM2AsPathType 3423 INTEGER, 3424 bgpM2AsPathElementValue 3425 InetAutonomousSystemNumber 3426 } 3428 bgpM2AsPathSegmentIndex OBJECT-TYPE 3429 SYNTAX Unsigned32 3430 MAX-ACCESS read-only 3431 STATUS current 3432 DESCRIPTION 3433 "A per-AS path segment index. This will index a set of 3434 autonomous systems in an AS path which are part 3435 of the same sequence or set (as determined by 3436 the row value of bgpM2AsPathType, which 3437 should be the same value for each bgpM2AsPathTable 3438 entry indexed by the same (bgpM2PathAttrIndex, 3439 bgpM2AsPathIndex) pair)." 3440 ::= { bgpM2AsPathTableEntry 1 } 3442 bgpM2AsPathElementIndex OBJECT-TYPE 3443 SYNTAX Unsigned32 3444 MAX-ACCESS read-only 3445 STATUS current 3446 DESCRIPTION 3447 "A per-AS element index. This will index a particular 3448 AS within a sequence or set of autonomous systems in 3449 an AS path." 3450 ::= { bgpM2AsPathTableEntry 2 } 3452 bgpM2AsPathType OBJECT-TYPE 3453 SYNTAX INTEGER { 3454 asSet(1), 3455 asSequence(2), 3456 confedSequence(3), 3457 confedSet(4) 3458 } 3459 MAX-ACCESS read-only 3460 STATUS current 3461 DESCRIPTION 3462 "The type of sequence in which this asPath 3463 was advertised as an attribute. Note that 3464 all asPath row instances for a given (bgpM2PathAttrIndex, 3465 bgpM2AsPathIndex) index pair will have their 3466 bgpM2AsPathType set to the same value. 3467 The values for bgpM2AsPathType are 3468 interpreted as defined in the base BGP document 3469 and the BGP AS Confederations document." 3470 REFERENCE 3471 "draft-ietf-idr-bgp4-16 3472 RFC 3065 - BGP AS Confederations" 3473 ::= { bgpM2AsPathTableEntry 3 } 3475 bgpM2AsPathElementValue OBJECT-TYPE 3476 SYNTAX InetAutonomousSystemNumber 3477 MAX-ACCESS read-only 3478 STATUS current 3479 DESCRIPTION 3480 "An AS value for an AS the related NLRI traversed 3481 in the propagation of its advertisement. This 3482 value is to be interpreted in the context of the 3483 sequence implied by bgpM2AsPathIndex and 3484 bgpM2AsPathType (and, in sequence of the 3485 other table rows with the same value of 3486 bgpM2PathAttrIndex and bgpM2AsPathIndex)." 3487 ::= { bgpM2AsPathTableEntry 4 } 3489 -- BGP 4 Path unknown attribute. There is one row in 3490 -- this table for each attribute not known by this BGP 3491 -- implementation (or agent instrumentation), but provided 3492 -- from a peer. 3494 bgpM2PathAttrUnknownTable OBJECT-TYPE 3495 SYNTAX SEQUENCE OF BgpM2PathAttrUnknownEntry 3496 MAX-ACCESS not-accessible 3497 STATUS current 3498 DESCRIPTION 3499 "The BGP-4 Path Attribute Unknown Table 3500 contains the per network path (NLRI) 3501 data on the path attributes advertised 3502 with a route but not known to the local BGP implementation 3503 or not otherwise capable of being returned from this agent. 3505 The absence of row data for a given index value for 3506 bgpM2PathAttrIndex indicates a lack of such unknown 3507 attribute information for the indicated network path 3508 (as indexed by that bgpM2PathAttrIndex value in the 3509 bgpM2PathAttrTable)." 3510 ::= { bgpM2Rib 7 } 3512 bgpM2PathAttrUnknownEntry OBJECT-TYPE 3513 SYNTAX BgpM2PathAttrUnknownEntry 3514 MAX-ACCESS not-accessible 3515 STATUS current 3516 DESCRIPTION 3517 "Information about an unknown attribute 3518 provided with a path to a network." 3519 INDEX { 3520 bgpM2PathAttrIndex, 3521 bgpM2PathAttrUnknownIndex 3522 } 3523 ::= { bgpM2PathAttrUnknownTable 1 } 3525 BgpM2PathAttrUnknownEntry ::= SEQUENCE { 3526 bgpM2PathAttrUnknownIndex 3527 Unsigned32, 3528 bgpM2PathAttrUnknownType 3529 Unsigned32, 3530 bgpM2PathAttrUnknownValue 3531 OCTET STRING 3532 } 3533 bgpM2PathAttrUnknownIndex OBJECT-TYPE 3534 SYNTAX Unsigned32 3535 MAX-ACCESS read-only 3536 STATUS current 3537 DESCRIPTION 3538 "An integer index for a row in this table." 3539 ::= { bgpM2PathAttrUnknownEntry 1 } 3541 bgpM2PathAttrUnknownType OBJECT-TYPE 3542 SYNTAX Unsigned32 3543 MAX-ACCESS read-only 3544 STATUS current 3545 DESCRIPTION 3546 "The attribute type advertised with this unknown 3547 attribute by the peer." 3548 ::= { bgpM2PathAttrUnknownEntry 2 } 3550 -- Maximum size of the following is derived as 3551 -- 4096 max message size 3552 -- - 16 BGP message marker bytes 3553 -- - 2 BGP message size 3554 -- - 1 BGP message type (UPDATE with unknown attr) 3555 -- - 2 UPDATE routes length (even assuming no routes) 3556 -- - 2 UPDATE path attributes length 3557 -- - 1 path attribute flag octet 3558 -- - 2 unknown path attr type (in bgpM2PathAttrUnknownType) 3559 -- --------- 3560 -- 4070 bytes maximum per-message attribute value data 3562 bgpM2PathAttrUnknownValue OBJECT-TYPE 3563 SYNTAX OCTET STRING (SIZE(0..4070)) 3564 MAX-ACCESS read-only 3565 STATUS current 3566 DESCRIPTION 3567 "Value of path attribute not understood 3568 by the base BGP-4 document. 3570 Octets beyond the maximum size, if any, 3571 are not recorded by this row object. " 3572 ::= { bgpM2PathAttrUnknownEntry 3 } 3574 -- 3575 -- Path Attribute Extensions 3576 -- 3577 bgpM2PathAttrExtensions 3578 OBJECT IDENTIFIER ::= { bgpM2Rib 8 } 3580 bgpM2PathAttrNonCapExts 3581 OBJECT IDENTIFIER ::= { bgpM2PathAttrExtensions 1 } 3583 bgpM2PathAttrCapExts 3584 OBJECT IDENTIFIER ::= { bgpM2PathAttrExtensions 2 } 3586 -- 3587 -- Path Attribute Route Reflection Extensions 3588 -- 3590 -- 3591 -- Originator ID Table 3592 -- 3594 bgpM2PathAttrRouteReflectionExts 3595 OBJECT IDENTIFIER ::= { bgpM2PathAttrNonCapExts 2796 } 3597 bgpM2PathAttrOriginatorIdTable OBJECT-TYPE 3598 SYNTAX SEQUENCE OF BgpM2PathAttrOriginatorIdEntry 3599 MAX-ACCESS not-accessible 3600 STATUS current 3601 DESCRIPTION 3602 "Per prefix data pertinent to advertisement of a 3603 network prefix through an originator." 3604 REFERENCE 3605 "RFC 2796 - BGP Route Reflection" 3606 ::= { bgpM2PathAttrRouteReflectionExts 1 } 3608 bgpM2PathAttrOriginatorIdEntry OBJECT-TYPE 3609 SYNTAX BgpM2PathAttrOriginatorIdEntry 3610 MAX-ACCESS not-accessible 3611 STATUS current 3612 DESCRIPTION 3613 "Each entry contains data pertinent to a network 3614 prefix as received through its originating BGP 3615 route reflector." 3616 REFERENCE 3617 "RFC 2796 - BGP Route Reflection" 3618 INDEX { 3619 bgpM2PathAttrIndex 3621 } 3622 ::= { bgpM2PathAttrOriginatorIdTable 1 } 3624 BgpM2PathAttrOriginatorIdEntry ::= SEQUENCE { 3625 bgpM2PathAttrOriginatorId 3626 BgpM2Identifier 3627 } 3629 bgpM2PathAttrOriginatorId OBJECT-TYPE 3630 SYNTAX BgpM2Identifier 3631 MAX-ACCESS read-only 3632 STATUS current 3633 DESCRIPTION 3634 "The Originator-ID identifying the router that initially 3635 advertised this destination to a Route Reflector. A 3636 value of 0.0.0.0 indicates the absence of this attribute." 3637 REFERENCE 3638 "This attribute is defined in [RFC2796]." 3639 ::= { bgpM2PathAttrOriginatorIdEntry 1 } 3641 -- 3642 -- Cluster table 3643 -- 3645 bgpM2PathAttrClusterTable OBJECT-TYPE 3646 SYNTAX SEQUENCE OF BgpM2PathAttrClusterEntry 3647 MAX-ACCESS not-accessible 3648 STATUS current 3649 DESCRIPTION 3650 "The BGP-4 Path Attribute Cluster Table 3651 contains the per network path (NLRI) 3652 data on the reflection path which a 3653 route has traversed. The absence of row 3654 data for a given index value for bgpM2PathAttrIndex 3655 indicates a lack of this attribute information 3656 for the indicated network path (as indexed by 3657 that bgpM2PathAttrIndex value in the bgpM2PathAttrTable)." 3658 ::= { bgpM2PathAttrRouteReflectionExts 2 } 3660 bgpM2PathAttrClusterEntry OBJECT-TYPE 3661 SYNTAX BgpM2PathAttrClusterEntry 3662 MAX-ACCESS not-accessible 3663 STATUS current 3664 DESCRIPTION 3665 "Information about a cluster traversal 3666 provided with a path to a network." 3667 INDEX { 3668 bgpM2PathAttrIndex, 3669 bgpM2PathAttrClusterIndex 3670 } 3671 ::= { bgpM2PathAttrClusterTable 1 } 3673 BgpM2PathAttrClusterEntry ::= SEQUENCE { 3674 bgpM2PathAttrClusterIndex 3675 Unsigned32, 3676 bgpM2PathAttrClusterValue 3677 BgpM2Identifier 3678 } 3680 bgpM2PathAttrClusterIndex OBJECT-TYPE 3681 SYNTAX Unsigned32 3682 MAX-ACCESS read-only 3683 STATUS current 3684 DESCRIPTION 3685 "An integral index for a row in this table." 3686 ::= { bgpM2PathAttrClusterEntry 1 } 3688 bgpM2PathAttrClusterValue OBJECT-TYPE 3689 SYNTAX BgpM2Identifier 3690 MAX-ACCESS read-only 3691 STATUS current 3692 DESCRIPTION 3693 "A four octet long value representing a part of the 3694 reflection path that the route has passed. Each such four 3695 octet long value represents the ID of a cluster that 3696 the route has traversed. The sequence of this path as 3697 received in the route advertisement will be preserved in 3698 the sequence of bgpM2PathAttrClusterTable rows (and the 3699 bgpM2PathAttrClusterValues in each row) as returned for 3700 a given bgpM2PathAttrIndex value, and the monotonically 3701 increasing sequence of bgpM2PathAttrClusterIndex values 3702 for that bgpM2PathAttrIndex." 3703 REFERENCE 3704 "This attribute is defined in [RFC2796]." 3705 ::= { bgpM2PathAttrClusterEntry 2 } 3707 -- 3708 -- BGP Communities 3709 -- 3711 bgpM2PathAttrCommunityExts 3712 OBJECT IDENTIFIER ::= { bgpM2PathAttrNonCapExts 1997 } 3714 bgpM2PathAttrCommTable OBJECT-TYPE 3715 SYNTAX SEQUENCE OF BgpM2PathAttrCommEntry 3716 MAX-ACCESS not-accessible 3717 STATUS current 3718 DESCRIPTION 3719 "The BGP-4 Path Attribute Community Table 3720 contains the per network path (NLRI) 3721 data on the community membership advertised 3722 with a route. The absence of row 3723 data for a given index value for bgpM2PathAttrIndex 3724 indicates a lack of this attribute information 3725 for the indicated network path (as indexed by 3726 that bgpM2PathAttrIndex value in the bgpM2PathAttrTable)." 3727 ::= { bgpM2PathAttrCommunityExts 1 } 3729 bgpM2PathAttrCommEntry OBJECT-TYPE 3730 SYNTAX BgpM2PathAttrCommEntry 3731 MAX-ACCESS not-accessible 3732 STATUS current 3733 DESCRIPTION 3734 "Information about a community association 3735 provided with a path to a network." 3736 INDEX { 3737 bgpM2PathAttrIndex, 3738 bgpM2PathAttrCommIndex 3739 } 3740 ::= { bgpM2PathAttrCommTable 1 } 3742 BgpM2PathAttrCommEntry ::= SEQUENCE { 3743 bgpM2PathAttrCommIndex 3744 Unsigned32, 3745 bgpM2PathAttrCommValue 3746 BgpM2Community 3747 } 3749 bgpM2PathAttrCommIndex OBJECT-TYPE 3750 SYNTAX Unsigned32 3751 MAX-ACCESS read-only 3752 STATUS current 3753 DESCRIPTION 3754 "An integer index for a row in this table." 3755 ::= { bgpM2PathAttrCommEntry 1 } 3757 bgpM2PathAttrCommValue OBJECT-TYPE 3758 SYNTAX BgpM2Community 3759 MAX-ACCESS read-only 3760 STATUS current 3761 DESCRIPTION 3762 "A value representing a community. There are certain 3763 4-octet long values which could be returned in this 3764 columnar row data that carry additional semantics." 3765 REFERENCE 3766 "RFC 1997 - BGP Communities Attribute" 3767 ::= { bgpM2PathAttrCommEntry 2 } 3769 -- 3770 -- BGP Extended Communities 3771 -- 3773 bgpM2PathAttrExtCommTable OBJECT-TYPE 3774 SYNTAX SEQUENCE OF BgpM2PathAttrExtCommEntry 3775 MAX-ACCESS not-accessible 3776 STATUS current 3777 DESCRIPTION 3778 "The BGP-4 Path Attribute Community Table 3779 contains the per network path (NLRI) 3780 data on the extended community membership advertised 3781 with a route. The absence of row 3782 data for a given index value for bgpM2PathAttrIndex 3783 indicates a lack of this attribute information 3784 for the indicated network path (as indexed by 3785 that bgpM2PathAttrIndex value in the bgpM2PathAttrTable). 3787 XXX JMH - can not assign the OID until an RFC is published." 3788 ::= { bgpM2PathAttrNonCapExts XXX } 3790 bgpM2PathAttrExtCommEntry OBJECT-TYPE 3791 SYNTAX BgpM2PathAttrExtCommEntry 3792 MAX-ACCESS not-accessible 3793 STATUS current 3794 DESCRIPTION 3795 "Information about an extended community association 3796 provided with a path to a network." 3797 INDEX { 3798 bgpM2PathAttrIndex, 3799 bgpM2PathAttrExtCommIndex 3800 } 3801 ::= { bgpM2PathAttrExtCommTable 1 } 3803 BgpM2PathAttrExtCommEntry ::= SEQUENCE { 3804 bgpM2PathAttrExtCommIndex 3805 Unsigned32, 3806 bgpM2PathAttrExtCommValue 3807 BgpM2ExtendedCommunity 3808 } 3810 bgpM2PathAttrExtCommIndex OBJECT-TYPE 3811 SYNTAX Unsigned32 3812 MAX-ACCESS read-only 3813 STATUS current 3814 DESCRIPTION 3815 "An integral index for a row in this table." 3816 ::= { bgpM2PathAttrExtCommEntry 1 } 3818 bgpM2PathAttrExtCommValue OBJECT-TYPE 3819 SYNTAX BgpM2ExtendedCommunity 3820 MAX-ACCESS read-only 3821 STATUS current 3822 DESCRIPTION 3823 "A value representing an extended community which was 3824 received with the route implied by the bgpM2PathAttr 3825 Index value of this row data. There are certain 3826 8-octet long values which could be returned in this 3827 columnar row data that carry additional semantics." 3828 REFERENCE 3829 "BGP-EXTCOMM - BGP Extended Communities Attribute" 3830 ::= { bgpM2PathAttrExtCommEntry 2 } 3832 -- 3833 -- RFC 2545 link local nexthop 3834 -- 3836 bgpM2LinkLocalNextHopTable OBJECT-TYPE 3837 SYNTAX SEQUENCE OF BgpM2LinkLocalNextHopEntry 3838 MAX-ACCESS not-accessible 3839 STATUS current 3840 DESCRIPTION 3841 "Table of link local nexthops as sent by RFC 2545 3842 for IPv6 BGP Speakers." 3843 REFERENCE 3844 "RFC 2545 - Use of BGP-4 Multiprotocol Extensions 3845 for IPv6 Inter-Domain Routing" 3846 ::= { bgpM2PathAttrNonCapExts 2545 } 3848 bgpM2LinkLocalNextHopEntry OBJECT-TYPE 3849 SYNTAX BgpM2LinkLocalNextHopEntry 3850 MAX-ACCESS not-accessible 3851 STATUS current 3852 DESCRIPTION 3853 "Entry containing the link-local nexthops as sent 3854 by a BGP speaker running RFC 2545 extensions for 3855 double-nexthops." 3856 INDEX { 3857 bgpM2PathAttrIndex 3858 } 3859 ::= { bgpM2LinkLocalNextHopTable 1 } 3861 BgpM2LinkLocalNextHopEntry ::= SEQUENCE { 3862 bgpM2LinkLocalNextHopPresent 3863 TruthValue, 3864 bgpM2LinkLocalNextHop 3865 InetAddress 3866 } 3868 bgpM2LinkLocalNextHopPresent OBJECT-TYPE 3869 SYNTAX TruthValue 3870 MAX-ACCESS read-only 3871 STATUS current 3872 DESCRIPTION 3873 "This value is TRUE if and only if the BGP 3874 speaker is receiving IPv6 NLRI using the 3875 RFC 2545 double nexthop convention and it 3876 has received a link local scope nexthop in 3877 addition to the global scope nexthop." 3878 ::= { bgpM2LinkLocalNextHopEntry 1 } 3880 bgpM2LinkLocalNextHop OBJECT-TYPE 3881 SYNTAX InetAddress (SIZE(20)) 3882 MAX-ACCESS read-only 3883 STATUS current 3884 DESCRIPTION 3885 "This value contains an IPv6 link local address of 3886 InetAddressType of type ipv6z. This value is only 3887 present if bgpM2LinkLocalNextHopPresent is true." 3888 ::= { bgpM2LinkLocalNextHopEntry 2 } 3890 -- 3891 -- Conformance Information 3892 -- 3894 bgpM2Conformance 3895 OBJECT IDENTIFIER ::= { bgpM2 4 } 3897 bgpM2MIBCompliances OBJECT IDENTIFIER ::= 3898 { bgpM2Conformance 1 } 3900 bgpM2MIBGroups OBJECT IDENTIFIER ::= 3901 { bgpM2Conformance 2 } 3903 bgpM2MIBCompliance MODULE-COMPLIANCE 3904 STATUS current 3905 DESCRIPTION 3906 "The compliance statement for entities which 3907 implement the BGP4 mib." 3908 MODULE -- this module 3909 MANDATORY-GROUPS { 3910 bgpM2TimersGroup, 3911 bgpM2CountersGroup, 3912 bgpM2AsPathGroup, 3913 bgpM2As4byteGroup, 3914 bgpM2BaseGroup, 3915 bgpM2ErrorsGroup, 3916 bgpM2PeerGroup, 3917 bgpM2PathAttributesGroup 3918 } 3919 GROUP bgpM2MIBNotificationsGroup 3920 DESCRIPTION 3921 "The notifications group is completely optional, 3922 but highly recommended." 3923 GROUP bgpM2AuthenticationGroup 3924 DESCRIPTION 3925 "The authentication group is 3926 mandatory only for those implementations which 3927 support sending and receiving authentication 3928 information with peers in the BGP Authentication 3929 Field." 3931 GROUP bgpM2CommunitiesGroup 3932 DESCRIPTION 3933 "The communities group is mandatory only for those 3934 which support the BGP community attribute." 3935 GROUP bgpM2ExtCommunitiesGroup 3936 DESCRIPTION 3937 "The communities group is mandatory only for those 3938 which support the BGP extended community attribute." 3939 GROUP bgpM2RouteReflectionGroup 3940 DESCRIPTION 3941 "The communities group is mandatory only for those 3942 which support the BGP route reflection relationships." 3943 GROUP bgpM2AsConfederationGroup 3944 DESCRIPTION 3945 "The communities group is mandatory only for those 3946 which support the BGP confederation membership." 3947 GROUP bgpM2TimersGroup 3948 DESCRIPTION 3949 "This group is mandatory for all agent implementations." 3950 GROUP bgpM2CountersGroup 3951 DESCRIPTION 3952 "This group is mandatory for all agent implementations." 3953 GROUP bgpM2CapabilitiesGroup 3954 DESCRIPTION 3955 "This group is mandatory for all agent implementations." 3956 GROUP bgpM2AsPathGroup 3957 DESCRIPTION 3958 "This group is mandatory for all agent implementations." 3959 GROUP bgpM2As4byteGroup 3960 DESCRIPTION 3961 "This group is mandatory for all agent implementations." 3962 GROUP bgpM2BaseGroup 3963 DESCRIPTION 3964 "This group is mandatory for all agent implementations." 3965 GROUP bgpM2ErrorsGroup 3966 DESCRIPTION 3967 "This group is mandatory for all agent implementations." 3968 GROUP bgpM2PeerGroup 3969 DESCRIPTION 3970 "This group is mandatory for all agent implementations." 3971 GROUP bgpM2PathAttributesGroup 3972 DESCRIPTION 3973 "This group is mandatory for all agent implementations." 3974 GROUP bgpM2PeerConfigurationGroup 3975 DESCRIPTION 3976 "This group is optional for implementations that wish to 3977 support configuration via SNMP." 3978 GROUP bgpM2PeerAuthConfigurationGroup 3979 DESCRIPTION 3980 "This group is optional for implementations that wish to 3981 support configuration of BGP authentication via SNMP. 3982 Implementation of this feature requires support of the 3983 bgpM2PeerConfigurationGroup." 3984 GROUP bgpM2PeerRouteReflectorCfgGroup 3985 DESCRIPTION 3986 "This group is optional for implementations that wish to 3987 support configuration of route reflection via SNMP. 3988 Implementation of this feature requires support of the 3989 bgpM2PeerConfigurationGroup." 3990 GROUP bgpM2PeerAsConfederationCfgGroup 3991 DESCRIPTION 3992 "This group is optional for implementations that wish to 3993 support configuration of BGP AS Confederations via SNMP. 3994 Implementation of this feature requires support of the 3995 bgpM2PeerConfigurationGroup." 3996 GROUP bgpM2Rfc2545Group 3997 DESCRIPTION 3998 "This group is required for peers that support exchanging 3999 of IPv6 NLRI per RFC 2545." 4000 ::= { bgpM2MIBCompliances 1 } 4002 bgpM2AuthenticationGroup OBJECT-GROUP 4003 OBJECTS { 4004 bgpM2SupportedAuthCode, 4005 bgpM2SupportedAuthValue, 4006 bgpM2PeerAuthSent, 4007 bgpM2PeerAuthSentCode, 4008 bgpM2PeerAuthSentValue, 4009 bgpM2PeerAuthRcvd, 4010 bgpM2PeerAuthRcvdCode, 4011 bgpM2PeerAuthRcvdValue 4012 } 4013 STATUS current 4014 DESCRIPTION 4015 "Objects associated with BGP authentication." 4016 ::= { bgpM2MIBGroups 1 } 4018 bgpM2CommunitiesGroup OBJECT-GROUP 4019 OBJECTS { 4020 bgpM2PathAttrCommIndex, 4021 bgpM2PathAttrCommValue 4022 } 4023 STATUS current 4024 DESCRIPTION 4025 "Objects associated with BGP communities." 4026 ::= { bgpM2MIBGroups 2 } 4028 bgpM2ExtCommunitiesGroup OBJECT-GROUP 4029 OBJECTS { 4030 bgpM2PathAttrExtCommIndex, 4031 bgpM2PathAttrExtCommValue 4032 } 4033 STATUS current 4034 DESCRIPTION 4035 "Objects associated with BGP extended communities." 4036 ::= { bgpM2MIBGroups 3 } 4038 bgpM2RouteReflectionGroup OBJECT-GROUP 4039 OBJECTS { 4040 bgpM2RouteReflector, 4041 bgpM2ClusterId, 4042 bgpM2PeerReflectorClient, 4043 bgpM2PathAttrOriginatorId, 4044 bgpM2PathAttrClusterIndex, 4045 bgpM2PathAttrClusterValue 4046 } 4047 STATUS current 4048 DESCRIPTION 4049 "Objects associated with BGP route reflection." 4050 ::= { bgpM2MIBGroups 4 } 4052 bgpM2AsConfederationGroup OBJECT-GROUP 4053 OBJECTS { 4054 bgpM2ConfederationRouter, 4055 bgpM2ConfederationId, 4056 bgpM2PeerConfedMember 4057 } 4058 STATUS current 4059 DESCRIPTION 4060 "Objects associated with BGP confederation membership." 4061 ::= { bgpM2MIBGroups 5 } 4063 bgpM2TimersGroup OBJECT-GROUP 4064 OBJECTS { 4065 bgpM2PeerFsmEstablishedTime, 4066 bgpM2PeerInUpdatesElapsedTime, 4067 bgpM2PeerConnectRetryInterval, 4068 bgpM2PeerHoldTimeConfigured, 4069 bgpM2PeerKeepAliveConfigured, 4070 bgpM2PeerMinASOrigInterval, 4071 bgpM2PeerMinRouteAdverInterval, 4072 bgpM2PeerHoldTime, 4073 bgpM2PeerKeepAlive 4074 } 4075 STATUS current 4076 DESCRIPTION 4077 "Objects associated with BGP peering timers." 4078 ::= { bgpM2MIBGroups 6 } 4080 bgpM2CountersGroup OBJECT-GROUP 4081 OBJECTS { 4082 bgpM2PeerInUpdates, 4083 bgpM2PeerOutUpdates, 4084 bgpM2PeerInTotalMessages, 4085 bgpM2PeerOutTotalMessages, 4086 bgpM2PeerFsmEstablishedTrans, 4087 bgpM2PrefixCountersAfi, 4088 bgpM2PrefixCountersSafi, 4089 bgpM2PrefixInPrefixes, 4090 bgpM2PrefixInPrefixesAccepted, 4091 bgpM2PrefixInPrefixesRejected, 4092 bgpM2PrefixOutPrefixes 4093 } 4094 STATUS current 4095 DESCRIPTION 4096 "Objects to count discrete events and exchanges on BGP 4097 sessions." 4098 ::= { bgpM2MIBGroups 7 } 4100 bgpM2CapabilitiesGroup OBJECT-GROUP 4101 OBJECTS { 4102 bgpM2CapabilitySupportAvailable, 4103 bgpM2SupportedCapabilityCode, 4104 bgpM2SupportedCapability, 4105 bgpM2PeerCapAnnouncedCode, 4106 bgpM2PeerCapAnnouncedIndex, 4107 bgpM2PeerCapAnnouncedValue, 4108 bgpM2PeerCapReceivedCode, 4109 bgpM2PeerCapReceivedIndex, 4110 bgpM2PeerCapReceivedValue 4111 } 4112 STATUS current 4113 DESCRIPTION 4114 "Objects to report capabilities as received on BGP 4115 sessions." 4116 ::= { bgpM2MIBGroups 8 } 4118 bgpM2AsPathGroup OBJECT-GROUP 4119 OBJECTS { 4120 bgpM2AsPathSegmentIndex, 4121 bgpM2AsPathElementIndex, 4122 bgpM2AsPathType, 4123 bgpM2AsPathElementValue 4124 } 4125 STATUS current 4126 DESCRIPTION 4127 "Objects to report AS paths received on BGP NLRIs." 4128 ::= { bgpM2MIBGroups 9 } 4130 bgpM2As4byteGroup OBJECT-GROUP 4131 OBJECTS { 4132 bgpM2AsSize, 4133 bgpM2AsPath4bytePathPresent, 4134 bgpM2AsPath4byteAggregatorAS, 4135 bgpM2AsPath4byteCalcLength, 4136 bgpM2AsPath4byteString, 4137 bgpM2AsPath4byteIndex 4138 } 4139 STATUS current 4140 DESCRIPTION 4141 "AS Size objects." 4142 ::= { bgpM2MIBGroups 10 } 4144 bgpM2BaseGroup OBJECT-GROUP 4145 OBJECTS { 4146 bgpM2LocalAs, 4147 bgpM2LocalIdentifier, 4148 bgpM2VersionIndex, 4149 bgpM2VersionSupported 4150 } 4151 STATUS current 4152 DESCRIPTION 4153 "Basic objects in local BGP implementation." 4154 ::= { bgpM2MIBGroups 11 } 4156 bgpM2ErrorsGroup OBJECT-GROUP 4157 OBJECTS { 4158 bgpM2PeerLastErrorReceived, 4159 bgpM2PeerLastErrorReceivedData, 4160 bgpM2PeerLastErrorReceivedTime, 4161 bgpM2PeerLastErrorReceivedText, 4162 bgpM2PeerLastErrorSent, 4163 bgpM2PeerLastErrorSentData, 4164 bgpM2PeerLastErrorSentTime, 4165 bgpM2PeerLastErrorSentText 4166 } 4167 STATUS current 4168 DESCRIPTION 4169 "Errors received on BGP peering sessions." 4170 ::= { bgpM2MIBGroups 12 } 4172 bgpM2PeerGroup OBJECT-GROUP 4173 OBJECTS { 4174 bgpM2PeerIdentifier, 4175 bgpM2PeerState, 4176 bgpM2PeerStatus, 4177 bgpM2PeerConfiguredVersion, 4178 bgpM2PeerNegotiatedVersion, 4179 bgpM2PeerLocalAddrType, 4180 bgpM2PeerLocalAddr, 4181 bgpM2PeerLocalPort, 4182 bgpM2PeerLocalAs, 4183 bgpM2PeerRemoteAddrType, 4184 bgpM2PeerRemoteAddr, 4185 bgpM2PeerRemotePort, 4186 bgpM2PeerRemoteAs, 4187 bgpM2PeerIndex 4188 } 4189 STATUS current 4190 DESCRIPTION 4191 "Core object types on BGP peering sessions." 4192 ::= { bgpM2MIBGroups 13 } 4194 bgpM2PathAttributesGroup OBJECT-GROUP 4195 OBJECTS { 4196 bgpM2PathAttrCount, 4197 bgpM2AsPathCalcLength, 4198 bgpM2AsPathElementValue, 4199 bgpM2AsPathIndex, 4200 bgpM2AsPathString, 4201 bgpM2AsPathType, 4202 bgpM2NlriAfi, 4203 bgpM2NlriBest, 4204 bgpM2NlriPrefix, 4205 bgpM2NlriPrefixLen, 4206 bgpM2NlriSafi, 4207 bgpM2NlriOpaqueType, 4208 bgpM2NlriOpaquePointer, 4209 bgpM2NlriIndex, 4210 bgpM2NlriCalcLocalPref, 4211 bgpM2AdjRibsOutIndex, 4212 bgpM2AdjRibsOutRoute, 4213 bgpM2PathAttrAggregatorAS, 4214 bgpM2PathAttrAggregatorAddr, 4215 bgpM2PathAttrAtomicAggregate, 4216 bgpM2PathAttrIndex, 4217 bgpM2PathAttrLocalPref, 4218 bgpM2PathAttrLocalPrefPresent, 4219 bgpM2PathAttrMed, 4220 bgpM2PathAttrMedPresent, 4221 bgpM2PathAttrNextHop, 4222 bgpM2PathAttrNextHopAddrType, 4223 bgpM2PathAttrOrigin, 4224 bgpM2PathAttrUnknownIndex, 4225 bgpM2PathAttrUnknownType, 4226 bgpM2PathAttrUnknownValue 4227 } 4228 STATUS current 4229 DESCRIPTION 4230 "Attributes received on BGP peering sessions." 4231 ::= { bgpM2MIBGroups 14 } 4233 bgpM2PeerConfigurationGroup OBJECT-GROUP 4234 OBJECTS { 4235 bgpM2CfgBaseScalarStorageType, 4236 bgpM2CfgLocalAs, 4237 bgpM2CfgLocalIdentifier, 4238 bgpM2CfgPeerAdminStatus, 4239 bgpM2CfgPeerNextIndex, 4240 bgpM2CfgPeerConfiguredVersion, 4241 bgpM2CfgAllowVersionNegotiation, 4242 bgpM2CfgPeerLocalAddrType, 4243 bgpM2CfgPeerLocalAddr, 4244 bgpM2CfgPeerLocalAs, 4245 bgpM2CfgPeerRemoteAddrType, 4246 bgpM2CfgPeerRemoteAddr, 4247 bgpM2CfgPeerRemotePort, 4248 bgpM2CfgPeerRemoteAs, 4249 bgpM2CfgPeerEntryStorageType, 4250 bgpM2CfgPeerError, 4251 bgpM2CfgPeerBgpPeerEntry, 4252 bgpM2CfgPeerRowEntryStatus, 4253 bgpM2CfgPeerIndex, 4254 bgpM2CfgPeerStatus, 4255 bgpM2CfgPeerConnectRetryInterval, 4256 bgpM2CfgPeerHoldTimeConfigured, 4257 bgpM2CfgPeerKeepAliveConfigured, 4258 bgpM2CfgPeerMinASOrigInterval, 4259 bgpM2CfgPeerMinRouteAdverInter 4260 } 4261 STATUS current 4262 DESCRIPTION 4263 "Configuration objects for BGP peers." 4264 ::= { bgpM2MIBGroups 15 } 4266 bgpM2PeerAuthConfigurationGroup OBJECT-GROUP 4267 OBJECTS { 4268 bgpM2CfgPeerAuthEnabled, 4269 bgpM2CfgPeerAuthCode, 4270 bgpM2CfgPeerAuthValue 4271 } 4272 STATUS current 4273 DESCRIPTION 4274 "Configuration objects for BGP peers that support 4275 authentication." 4276 ::= { bgpM2MIBGroups 16 } 4278 bgpM2PeerRouteReflectorCfgGroup OBJECT-GROUP 4279 OBJECTS { 4280 bgpM2CfgRouteReflector, 4281 bgpM2CfgClusterId, 4282 bgpM2CfgPeerReflectorClient 4283 } 4284 STATUS current 4285 DESCRIPTION 4286 "Configuration objects for BGP peers that support route 4287 reflection." 4288 ::= { bgpM2MIBGroups 17 } 4290 bgpM2PeerAsConfederationCfgGroup OBJECT-GROUP 4291 OBJECTS { 4292 bgpM2CfgConfederationRouter, 4293 bgpM2CfgConfederationId, 4294 bgpM2CfgPeerConfedMember 4295 } 4296 STATUS current 4297 DESCRIPTION 4298 "Configuration objects for BGP peers that support BGP 4299 confederations." 4300 ::= { bgpM2MIBGroups 18 } 4302 bgpM2MIBNotificationsGroup NOTIFICATION-GROUP 4303 NOTIFICATIONS { 4304 bgpM2Established, 4305 bgpM2BackwardTransition 4306 } 4307 STATUS current 4308 DESCRIPTION 4309 "This group contains objects for notifications 4310 supported by this mib module." 4311 ::= { bgpM2MIBGroups 19 } 4313 bgpM2Rfc2545Group OBJECT-GROUP 4314 OBJECTS { 4315 bgpM2LinkLocalNextHopPresent, 4316 bgpM2LinkLocalNextHop 4317 } 4318 STATUS current 4319 DESCRIPTION 4320 "This group is required for peers that support exchanging 4321 of IPv6 NLRI per RFC 2545." 4322 ::= { bgpM2MIBGroups 20 } 4324 END 4326 2. Security Considerations 4328 This MIB module contains controls which relate to core services for 4329 interdomain routing using the Border Gateway Protocol. In particu- 4330 lar, this MIB allows configuration of operational elements for those 4331 services. If such configuration is done without consideration for 4332 the effects of such configuration activity, or malicious configura- 4333 tion activity is allowed on the managed elements, the effect could be 4334 denial of service to the processes and end users in the affected 4335 domain(s). 4337 SNMPv1 is not considered a sufficiently secure environment for the 4338 deployment of such configuration ability. Even if the management 4339 data path is secure at the network protocol layer (by the deployment 4340 of secure IP, for example), there are still points of exposure around 4341 such issues as to what operators and applications are allowed to 4342 access and modify the configuration as exposed through this MIB mod- 4343 ule. 4345 It is strongly recommended that the agent implementor considers the 4346 security features afforded by the SNMP Version 3 framework in expos- 4347 ing the configuration features of this MIB module. In particular, 4348 the availability and usage of the User-based Security Model [12] 4350 5. Changes From Last Version 4352 This section is used to track changes from version to version of this 4353 document. This section will be removed from the document prior to 4354 being issued to IDR working group last call. 4356 * Changes from draft-ietf-idr-bgp4-mibv2-02.txt to draft-ietf- 4357 idr-bgp4-mibv2-03.txt (4 November 2002): 4359 Changed the order of the bgpM2NlriPrefixLen and 4360 bgpM2NlriPrefix objects and renumbered them. This was to make 4361 it consistant with user expectations. 4363 Clarify the peer table description text to specify the remote 4364 peer. 4366 Use SnmpAdminString instead of DisplayString. 4368 Correct TEXTUAL CONVENTION for extended communities. 4370 Changed enumerations of bgpM2PathATtrAtomicAggregate. 4372 Added link local table for RFC 2545 nexthops. 4374 * Changes from draft-ietf-idr-bgp4-mibv2-01.txt to draft-ietf- 4375 idr-bgp4-mibv2-02.txt (28 February 2002) 4377 Lots of changes in this rewrite, these are the most dramatic: 4379 Configuration objects and tables added. 4381 All references to 'bgp' in object descriptors changed to 4382 'bgpM2' to disambiguate from RFC 1657 and its OBSOLETing MIB. 4384 Community Textual conventions added to beginning of MIB. 4386 bgpM2CalcLength and PathString columns added to bgpM2PathAttr 4387 table. 4389 Creation of separate bgpM2AdjRibsOutTable. 4391 Appearance of NLRI table notions such as 'opaque type'. 4393 Overhaul of specification of AS Path types to accommodate eas- 4394 ier management at time of route aggregation. 4396 6. References 4398 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 4399 Describing SNMP Management Frameworks", RFC 2571, April 1999. 4401 [2] Rose, M., and K. McCloghrie, "Structure and Identification of Man- 4402 agement Information for TCP/IP-based Internets", STD 16, RFC 1155, 4403 May 1990. 4405 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 4406 1212, March 1991. 4408 [4] Rose, M., "A Convention for Defining Traps for use with the SNMP", 4409 RFC 1215, March 1991. 4411 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 4412 and S. Waldbusser, "Structure of Management Information Version 2 4413 (SMIv2)", STD 58, RFC 2578, April 1999. 4415 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 4416 and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 4417 2579, April 1999. 4419 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 4420 and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 4421 2580, April 1999. 4423 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 4424 Management Protocol", STD 15, RFC 1157, May 1990. 4426 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduc- 4427 tion to Community-based SNMPv2", RFC 1901, January 1996. 4429 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 4430 Mappings for Version 2 of the Simple Network Management Protocol 4431 (SNMPv2)", RFC 1906, January 1996. 4433 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message Pro- 4434 cessing and Dispatching for the Simple Network Management Protocol 4435 (SNMP)", RFC 2572, April 1999. 4437 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 4438 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 4439 2574, April 1999. 4441 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 4442 Operations for Version 2 of the Simple Network Management Protocol 4443 (SNMPv2)", RFC 1905, January 1996. 4445 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 4446 2573, April 1999. 4448 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Con- 4449 trol Model (VACM) for the Simple Network Management Protocol 4450 (SNMP)", RFC 2575, April 1999. 4452 [16] McCloghrie, K. and M. Rose, Editors, "Management Information Base 4453 for Network Management of TCP/IP-based Internets: MIB-II", STD 17, 4454 RFC 1213, Hughes LAN Systems, Performance Systems International, 4455 March 1991. 4457 [17] Willis, S., Burruss, J., and Chu, J., "Definitions of Managed 4458 Objects for the Fourth Version of the Border Gateway Protocol 4459 (BGP-4) using SMIv2", RFC 1657, July 1994. 4461 [18] Hares, S., Haas, J., Willis, S., Burruss, J., and Chu, J., "Defini- 4462 tions of Managed Objects for the Fourth Version of Border Gateway 4463 Protocol (BGP-4)", draft-ietf-idr-bgp4-mib-06.txt, Work-in- 4464 progress. 4466 [19] Rekhter, Y., Li, T., "A Border Gateway Protocol 4 (BGP-4)", RFC 4467 1771, March 1995. 4469 [20] Rekhter, Y., Gross, P., "Application of the Border Gateway Proto- 4470 col in the Internet", RFC 1772, March 1995. 4472 [21] Traina, P., McPherson, D., and Scudder, J., "Autonomous System 4473 Confederations for BGP", RFC 3065, February, 2001. 4475 [22] Chandra, R., Traina, P., and Li, T., "BGP Communities Attribute", 4476 RFC 1997, August, 1996. 4478 [23] Bates, T., Rekhter, Y., Chandra, R., and Katz, D., "Multiprotocol 4479 Extensions for BGP-4", June, 2000. 4481 [24] Bates, T., Chandra, R., and Chen, E., "BGP Route Reflection - An 4482 Alternative to Full Mesh IBGP", RFC 2796, April 2000. 4484 [25] Sangli, S., Tappan, D., and Rekhter, Y., "BGP Extended Communities 4485 Attribute", Work-in-progress. 4487 [26] Rehkter, Y., and Rosen, E., "Carrying Label Information in BGP-4", 4488 RFC 3107, May 2001. 4490 7. Authors' Addresses 4492 Jeff Haas 4493 NextHop Technologies 4494 825 Victors Way, Suite 100 4495 Ann Arbor, MI 48108 4496 Phone: +1 734 222-1600 4497 Fax: +1 734 222-1602 4498 Email: jhaas@nexthop.com 4500 Susan Hares 4501 NextHop Technologies 4502 825 Victors Way, Suite 100 4503 Ann Arbor, MI 48108 4504 Phone: +1 734 222-1600 4505 Fax: +1 734 222-1602 4506 Email: skh@nexthop.com 4508 Wayne Tackabury 4509 Gold Wire Technology 4510 411 Waverley Oaks Rd. 4511 Waltham, MA 02452-8401 4512 Phone: +1 781 398-8819 4513 Fax: +1 781 398-8811 4514 Email: wayne@goldwiretech.com 4516 8. Full Copyright Statement 4518 Copyright (C) The Internet Society (2002). All Rights Reserved. 4520 This document and translations of it may be copied and furnished to 4521 others, and derivative works that comment on or otherwise explain it 4522 or assist in its implementation may be prepared, copied, published 4523 and distributed, in whole or in part, without restriction of any 4524 kind, provided that the above copyright notice and this paragraph are 4525 included on all such copies and derivative works. However, this doc- 4526 ument itself may not be modified in any way, such as by removing the 4527 copyright notice or references to the Internet Society or other 4528 Internet organizations, except as needed for the purpose of develop- 4529 ing Internet standards in which case the procedures for copyrights 4530 defined in the Internet Standards process must be followed, or as 4531 required to translate it into languages other than English. 4533 The limited permissions granted above are perpetual and will not be 4534 revoked by the Internet Society or its successors or assigns. 4536 This document and the information contained herein is provided on an 4537 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 4538 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 4539 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 4540 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MER- 4541 CHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 4543 Table of Contents 4545 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2 4546 2. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4547 2.1. Protocol Extensions . . . . . . . . . . . . . . . . . . . . . . 3 4548 2.2. Mechanisms for MIB Extensibility . . . . . . . . . . . . . . . 3 4549 2.3. BGP Configuration . . . . . . . . . . . . . . . . . . . . . . . 4 4550 3. MIB Organization . . . . . . . . . . . . . . . . . . . . . . . . 4 4551 3.1. bgpM2BaseScalars . . . . . . . . . . . . . . . . . . . . . . . 5 4552 3.2. bgpM2PeerData . . . . . . . . . . . . . . . . . . . . . . . . . 5 4553 3.2.1. bgpM2PeerCapabilities . . . . . . . . . . . . . . . . . . . . 6 4554 3.2.2. bgpM2PeerCounters . . . . . . . . . . . . . . . . . . . . . . 6 4555 3.2.3. Peering Data Extensions . . . . . . . . . . . . . . . . . . . 6 4556 3.2.4. Configuring Peering Sessions . . . . . . . . . . . . . . . . 7 4557 3.3. BGP Routing Information Base Data . . . . . . . . . . . . . . . 8 4558 3.3.1. Routing Information Base Extensions . . . . . . . . . . . . . 9 4559 3.4. Considerations on Table Indexing . . . . . . . . . . . . . . . 9 4560 1. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 4561 2. Security Considerations . . . . . . . . . . . . . . . . . . . . . 97 4562 3. Intellectual Property . . . . . . . . . . . . . . . . . . . . . . 98 4563 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 98 4564 5. Changes From Last Version . . . . . . . . . . . . . . . . . . . . 99 4565 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 4566 7. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 102 4567 8. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 102