idnits 2.17.1 draft-ietf-idr-bgp4-mibv2-02.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. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 267 has weird spacing: '...ient of the l...' == Line 375 has weird spacing: '...mmTable conta...' == Line 1222 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 (February 28, 2002) is 8093 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 3697 == Unused Reference: '20' is defined on line 4406, but no explicit reference was found in the text == Unused Reference: '22' is defined on line 4412, but no explicit reference was found in the text == Unused Reference: '23' is defined on line 4415, but no explicit reference was found in the text == Unused Reference: '25' is defined on line 4421, 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: 21 errors (**), 0 flaws (~~), 11 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 February 28, 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] 85 and the view-based access control mechanism described in RFC 86 2575 [15]. 88 A more detailed introduction to the current SNMP Management Framework 89 can be found in RFC 2570 [18]. 91 Managed objects are accessed via a virtual information store, termed 92 the Management Information Base or MIB. Objects in the MIB are 93 defined using the mechanisms defined in the SMI. 95 2. Objectives 97 This MIB Module is meant to broadly update and replace a prior MIB 98 Module defined in RFC 1657 [12]. Additionally, there is another 99 effort underway to address very specific limited objectives in updat- 100 ing points in the RFC 1657 object definition and managed object 101 attributes [13]. The MIB Module described herein is intended to 102 fully serve the functions and scope of RFC 1657 and these RFC 1657 103 updates. 105 2.1. Protocol Extensions 107 Additionally, however, there are a number of ways in which the BGP 108 Protocol has been enhanced through its ability for added capabili- 109 ties. Implementations of those capabilities have not been able to 110 have any management capabilities present in RFC 1657-compliant MIB 111 module agents, since the capabilities themselves postdated the adop- 112 tion of RFC 1657. For several significant capabilities, in the form 113 of BGP Communities [17], Autonomous System Confederation [16] , BGP 114 Multiprotocol Extensions [18], and Route Reflection [19], the MIB 115 Module defined in this document exposes object types to manage those 116 extended capabilities and their operation. 118 One of these extensions in particular (the multiprotocol extensions) 119 requires a thorough redefinition of MIB table row indices from the 120 RFC 1657 state. This allows transport-independent address indices 121 consistent with the Address Family Identifier (AFI) and Subsequent 122 Address Family Identifier (SAFI) mechanisms of that extension. 124 2.2. Mechanisms for MIB Extensibility 126 Moreover, the requirement for the incremental update of support for 127 capabilities such as these begs the issue of placing modular extensi- 128 bility for protocol extensions within the framework of the MIB 129 itself. Going forward, it would be very desirable to have attributes 130 of the MIB structure, and administrative procedures, to allow the 131 incremental update of the MIB scope to cover any such new protocol 132 extensions, without requiring a reissue of the entire MIB. In this 133 sense, we seek to structure the MIB much like the underlying BGP4 134 itself, allowing capability-by-capability update. 136 2.3. BGP Configuration 138 Finally, the definition and adoption of Version 3 of the SNMP has 139 occurred since the adoption of the RFC 1657 MIB. As a result, the 140 ability to deploy secure configuration of managed elements via SNMP 141 in a standardized way has become a reality for managed networks. In 142 this MIB definition effort, we seek to expose a more thorough capac- 143 ity for configuration of BGP4 and its capabilities than was present 144 in RFC 1657 or than was common practice at the time of its adoption. 146 3. MIB Organization 148 The MIB is broken down into several top level sections. This sec- 149 tionalization is important to create an organization for extensibil- 150 ity. 152 In general, a top level section of the MIB module will identify some 153 number of "core" scalar and tabular objects rooted off of it. If 154 there is sufficient depth within a subsection of one of these top- 155 level sections, the "core" subdivision off of the top level section 156 may provide multiple levels to the OBJECT IDENTIFIER scope necessary 157 to define its management data. 159 Once this core section is defined, however, each top-level section 160 has an explicit provision for an 'extensions' section OBJECT IDENTI- 161 FIER. The intent of the extensions section is to be containment for 162 discrete per-extension sections. By 'extension' here, we refer to 163 protocol mechanisms, capabilities, and exchanges which are not 164 defined in the base Border Gateway Protocol definition, or is not 165 configuration for protocol operations of similarly 'core' status. 166 Currently, we propose keying the identification within the per-exten- 167 sion section in one of two ways. 169 Where the extension is keyed to a defined capability which has an 170 associated BGP capability number assigned by IANA (for example, mul- 171 tiprotocol BGP extensions), the per extension section will be that 172 defined IANA capability number. Where the extension has management 173 information suitable for a MIB extension but does not correspond to 174 an exchanged protocol capability (for example, BGP Route Reflection), 175 the extension section shall have its final OBJECT IDENTIFIER fragment 176 correspond to the RFC number which first uniquely defined the exten- 177 sion (i.e., not requiring renumbering at the time a defining RFC for 178 a protocol mechanism is outdated by a later RFC). 180 3.1. bgpM2BaseScalars 182 The bgpM2BaseScalars section (and corresponding OBJECT IDENTIFIER) is 183 used to delineate object types used for basic management and monitor- 184 ing of the protocol implementation. These are core parameters for 185 the local configuration. While notifications are designed to be 186 extensible into any other section in the MIB module, the currently 187 defined traps are located here, in a subsection 'bgpM2BaseNotifica- 188 tions'. This is rooted at index level zero (0) here, owing to con- 189 ventions established in [4]. 191 Support for multiple concurrently supported versions of BGP is 192 exposed through the entries of the bgpM2VersionTable. Similarly, 193 support for multiple capabilities and authentication mechanisms, as 194 identified by their assigned numbers, are reported in the bgpM2Sup- 195 portedCapabilitiesTable and bgpM2SupportedAuthTable respectively. 197 In the MIB document, there are currently scalar extension mechanisms 198 to allow the agent to report membership of a local BGP Confederation 199 [21] or Route Reflection Cluster ID [24], as well as whether these 200 capabilities are in fact supported by the implementation. These are 201 consistent with the non-capability based extension section indexing 202 guidelines as presented above. 204 bgpM2BaseScalars also is the root for a subsection, bgpM2BaseScalar- 205 Configuration, which contains the companion configuration objects for 206 the base scalar objects delineated in the preceding paragraphs. 207 These are presented as a series of scalar read-write objects, with a 208 single OBJECT-TYPE of syntax StorageType to designate the persistence 209 of the instance value data for these configuration scalars. 211 3.2. bgpM2PeerData 213 The bgpM2PeerData section is per-peer object type definitions. The 214 predominant table of read-only STATUS object types in that section 215 (bgpM2PeerTable) describes the session, negotiation state, and 216 authentication state on a per peer basis. A second table (bgpM2Pre- 217 fixCountersTable) exposes information about individual route prefixes 218 received over each peer session. A separate subsection and its sub- 219 ordinate table (bgpM2PeerErrorsTable) reports information about the 220 last error encountered on a given peering session. 222 Further subsections report authentication state with the peer, peer- 223 ing session detected errors, and elapsed time it has taken to 224 advance the peering session into various states defined in the proto- 225 col FSM. 227 The bgpM2PeerConfiguredTimersTable reports and allows dynamic reset 228 of key timers on the peer session. These currently allow reset of 229 hold time and keepalive timer, for compatibility with the same capa- 230 bilities in RFC 1657 [17]. For these resettable timers, their end-to- 231 end negotiated current values are reflected in the bgpM2PeerNegotiat- 232 edTimersTable. 234 As currently defined, these tables describing authentication, error 235 state, and timer values (in addition to the configuration tables for 236 session timers) are tightly coupled enough to the logical per-row 237 view exposed in the bgpM2PeerTable row entries on a session that 238 these subordinate "tables" are defined as AUGMENTing the 239 bgpM2PeerTable itself. The other primary design criterion behind 240 this decision is that using this AUGMENTation does not increase the 241 per-row-data requirements of bgpM2PeerTable instance retrieval so as 242 to make such per-row retrieval unwieldy for the management applica- 243 tion. 245 3.2.1. bgpM2PeerCapabilities 247 bgpM2PeerCapabilitiesData has objects and tables to describe BGP 248 capabilities locally supported, and those reported and negotiated 249 over each peer session. For tables supporting each of these capa- 250 bility sets, capability code and data value are provided. Attention 251 must be given to the fact that multiple instances of a given capabil- 252 ity can be transmitted between BGP speakers. 254 3.2.2. bgpM2PeerCounters 256 The bgpM2CountersTable and bgpM2PrefixCountersTable report protocol 257 exchanges/FSM transitions, and discrete number of NLRIs exchanged per 258 peering session, respectively. This is independent of actual 259 exchanged path attributes, which are tabularized later in the MIB 260 module. Note that session transitions as reflected in changes of 261 instances within this table may also be reflected in issuance of 262 bgpM2Established and bgpM2BackwardTransition NOTIFICATION-TYPE PDUs. 264 3.2.3. Peering Data Extensions 266 Route reflector status on a per-peer basis (whether the peer is a 267 client or nonClient of the local BGP router's reflected route propa- 268 gation), and peer confederation membership is reported in non capa- 269 bility extensions of the peering data section. 271 3.2.4. Configuring Peering Sessions 273 The MIB has several tables indexed on a per-peer level of granularity 274 to control creation and activation of new peering sessions, and to 275 allow control on running sessions (those reflected in bgpM2PeerTable 276 row instances) regardless of what caused their creation in the BGP 277 routing process. 279 The bgpM2CfgPeerAdminStatusTable allows creation and specification of 280 a row by a bgpM2PeerIndex value (which is how its associated row 281 instance is identified in the bgpM2PeerTable). For each such row 282 instance, the set of the bgpM2CfgPeerAdminStatus OBJECT-TYPE of MAX- 283 ACCESS read-write can allow management application start and stop of 284 the session. 286 This is contrasted with the function of the bgpM2CfgPeerTable, and 287 its related AUGMENTed tables bgpM2CfgPeerTimersTable and bgpM2Cfg- 288 PeerAuthTable. These are used to facilitate direct creation of peer- 289 ing sessions by the management application. The function of columnar 290 OBJECT-TYPEs within the bgpM2CfgPeerTable for local and remote 291 address, version negotiation, and various row-administrative 292 attributes (RowStatus and StorageType SYNTAXes) are straightforward 293 enough. The only subtlety with respect to how peering sessions are 294 activated from usage of this table, and how the activated sessions 295 are reflected through their bgpM2PeerTable and bgpM2CfgPeerAdminSta- 296 tusTable entries, is in the usage of the bgpM2CfgPeerTable columnar 297 object bgpM2CfgPeerStatus. bgpM2CfgPeerStatus can take on two val- 298 ues. When a peering session, as reflected through its row instance 299 in the bgpM2CfgPeerTable, has the bgpM2CfgPeerStatus instance value 300 in that row set to running(2) at the time of the SYNTAX RowStatus 301 object instance of bgpM2CfgPeerRowEntryStatus set to active(1), the 302 peering session will in fact be activated in the BGP routing process 303 (in addition to having its row instance created in the bgpM2Cfg- 304 PeerTable and bgpM2CfgPeerAdminStatusTable). In this case, the asso- 305 ciated row of the bgpM2CfgPeerAdminStatusTable row bgpM2CfgPeerAdmin- 306 Status instance would have the value of start(2). If, in the prior 307 example, the bgpM2CfgPeerStatus is halted(1) at the time of the 308 bgpM2CfgPeerRowEntryStatus instance set to active(1), only the peer- 309 ing table entries would be created at this time of activation, with- 310 out the peering session being automatically started. The bgpM2Cfg- 311 PeerAdminStatusTable row bgpM2CfgPeerAdminStatus instance associated 312 with the session would in this case reflect a value of stop(1). 314 Since the row entries of the per-peer configuration tables which AUG- 315 MENT the bgpM2CfgPeerTable logically fate-share the row instances in 316 the bgpM2CfgPeerTable which they are AUGMENTing, they also share the 317 same StorageType and RowStatus SYNTAX object sense of the 318 bgpM2CfgPeerTable rows which they augment. 320 3.3. BGP Routing Information Base Data 322 An important table for providing index information for other tables 323 in the MIB module is the bgpM2NlriTable. This discriminates on a 324 given network prefix (by AFI/SAFI), and the peer which advertised the 325 prefix (since it can be heard of from multiple speakers). The 326 bgpM2PathAttrIndex column which identifies each row in this table is 327 used as an index for other per-attribute tables through the remainder 328 of the MIB module. 330 RFC 3107 [26] specifies a capability for exchanged routes between BGP 331 peers to attach attribute information to a route indicating, specifi- 332 cally, related MPLS label path information. The MIB supports the 333 presentation of this attribute information by generalizing how these 334 attributes are presented to accommodate further extensions of this 335 particular type. Within a given bgpM2NlriTable entry, we speak of 336 attribute data of this type as being 'opaque' to BGP, and use the 337 columnar OBJECT-TYPEs bgpM2NlriOpaqueType and bgpM2NlriOpaquePointer 338 to refer to it. In the case of the RFC 3107 MPLS label encoding 339 (which is the only usage of these columnar fields in the bgpM2NlriTa- 340 ble right now), a MPLS label stack would be referenced by bgpM2Nlri- 341 OpaquePointer by its per-NLRI instance pointing to a row instance in 342 the MPLS LSR MIB mplsLabelStackTable, and the bgpM2NlriOpaqueType 343 instance having a value of bgpMplsLabelStack(1). 345 The bgpM2AdjRibsOutTable row entries reflect data on routes which 346 have been placed, per peering session, in the Adj-Rib-Out for adver- 347 tisement to the associated peer. 349 The bgpM2PathAttrTable provides discrete BGP NLRI attributes which 350 were received with the advertisement of the prefix by its advertising 351 peer. Specific information about the autonomous system path (AS 352 Path) advertised with the NLRI, on a per AS value, is to be found in 353 the bgpM2AsPathTable. 355 Finally, where attributes which were unable to be reported in the 356 bgpM2PathAttrTable, the AS Path table, or any defined per-NLRI tables 357 in the agent were received with the prefix, those attributes are 358 reported via the bgpM2PathAttrUnknownTable. Short of advertised 359 attribute type, no semantic breakdown of the unknown attribute data 360 is provided. That data is only available as a raw OCTET STRING in 361 the bgpM2PathAttrUnknownValue column of this table. 363 3.3.1. Routing Information Base Extensions 365 There are two extension sections and five subordinate tables to the 366 bgpM2PathAttrTable and RIB data OBJECT IDENTIFIER-delimited MIB mod- 367 ule section. The bgpM2PathAttrRouteReflectionExts and its contained 368 bgpM2PathAttrOriginatorIdTable report on the originating route 369 reflector. The bgpM2PathAttrClusterTable specifically reports on the 370 reflection route a NLRI has traversed to get to the local BGP routing 371 process. 373 The bgpM2PathAttrCommunityExts section deals with extended and non- 374 extended communities for network routes. The bgpM2PathAttrCommTable 375 bgpM2PathAttrExtCommTable contained herein report community member- 376 ship (if any) on a per network-prefix basis. 378 3.4. Consideration On Table Indexing 380 There are certain efficiency concerns for row index management for 381 management applications which are useful to take into consideration, 382 given the nature of some of the tables implied in the preceding sec- 383 tion. 385 In the first place, it is valuable to exploit the direct relationship 386 of entries in, for example, the bgpM2PrefixCountersTable as they 387 relate to the entry in the bgpM2PeerTable to which they are related. 388 More compelling is the example case of the one-to-many relationship 389 between a row entry in the bgpM2PeerTable and the bgpM2PathAttrTable, 390 the latter of which maintains per-row entries for potentially many 391 NLRIs as received from a peer in a BGP UPDATE message. From the 392 point of view of normalizing these relationships, it would be useful 393 to have a direct reference to the "governing" bgpM2PeerTable row 394 entry for the peer which is a "dependency" for the subordinate table 395 row entry for other peer data. 397 Second, the nature of protocol-independent addressing makes the 398 indexing of these entries indirectly even more compelling. Even 399 accounting for the addressing requirements of IPv6 and the provision 400 of AFI and SAFI qualifiers, the logical addressing of a row in the 401 bgpPathAttrClusterTable (for example) would extend out some 50 bytes 402 if there was no direct index linkage to the "governing" bgpPathAt- 403 trTable, and bgpPeerTable entries. 405 For this reason, the tables are structured in such a way that, where 406 there is such a linkage to a "dependent" table (where, for example, 407 the bgpPrefixCountersTable "depends on" the bgpPeerTable), a table 408 will contain a per-row numeric index (e.g., bgpPeerIndex), which the 409 "dependent" table will use as one of its own row index values. These 410 indices are manufactured by the agent, and are otherwise opaque to 411 the management application (or, for that matter, even to the organi- 412 zation of the "dependent" table[s]). 414 Where considerations of per-row retrieval overhead (in terms of typi- 415 cal row instance data size, as a function of liability to have a sin- 416 gle row retrieval exceed PDU size, for example), and those of general 417 logical data organization permit, certain tables logically at the 418 sub-peering-session level have been specified as AUGMENTing the pri- 419 mary tables (bgpM2PeerTable and bgpM2CfgPeerTable) to which those 420 sub-peering-session row entries relate. This is to facilitate ease 421 on the part of a management application of assembling (for example, 422 via GET-BULK operations across a lexicographically contiguous row 423 scope) a management image of control information on a given peering 424 session. 426 1. 428 BGP4-V2-MIB DEFINITIONS ::= BEGIN 430 IMPORTS 431 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 432 Counter32, Gauge32, mib-2, Unsigned32, Integer32 433 FROM SNMPv2-SMI 434 -- Note that the following reference to INET-ADDRESS-MIB 435 -- refers to the version as published in the RFC 2851 436 -- update internet draft. 437 InetAddressType, InetAddress, InetPortNumber, 438 InetAutonomousSystemNumber, InetAddressPrefixLength 439 FROM INET-ADDRESS-MIB 440 TEXTUAL-CONVENTION, TruthValue, DisplayString, RowPointer, 441 StorageType, RowStatus 442 FROM SNMPv2-TC 443 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 444 FROM SNMPv2-CONF; 446 bgpM2 MODULE-IDENTITY 447 LAST-UPDATED "200202270000Z" 448 ORGANIZATION "IETF IDR Working Group" 449 CONTACT-INFO "E-mail: idr@merit.net 451 Jeffrey Haas (Editor) 452 825 Victors Way, Suite 100 453 Ann Arbor, MI 48108 454 Tel: +1 734 973-2200 455 Fax: +1 734 615-3241 456 E-mail: jhaas@nexthop.com" 458 DESCRIPTION 459 "This MIB module defines management objects for 460 the Border Gateway Protocol, Version 4." 461 ::= { mib-2 XXX } 463 BgpM2Identifier ::= TEXTUAL-CONVENTION 464 DISPLAY-HINT "1d." 465 STATUS current 466 DESCRIPTION 467 "The representation of a BGP Identifier. The BGP 468 Identifier should be represented in the OCTET STRING 469 as with the first OCTET of the string containing 470 the first OCTET of the BGP Identifier received or sent 471 in the OPEN packet and so on. 473 Even though the BGP Identifier is trending away from 474 an IP address it is still displayed as if it was one, 475 even when it would be an illegal IP address." 476 SYNTAX OCTET STRING(SIZE (4)) 478 BgpM2Safi ::= TEXTUAL-CONVENTION 479 DISPLAY-HINT "d" 480 STATUS current 481 DESCRIPTION 482 "The representation of a BGP Safi" 483 SYNTAX Unsigned32(0..255) 485 BgpM2Community ::= TEXTUAL-CONVENTION 486 DISPLAY-HINT "2d:" 487 STATUS current 488 DESCRIPTION 489 "The representation of a BGP Community." 490 SYNTAX OCTET STRING(SIZE(4)) 492 BgpM2ExtendedCommunity ::= TEXTUAL-CONVENTION 493 DISPLAY-HINT "1x:1x:1x1x1x1x1x1x" 494 STATUS current 495 DESCRIPTION 496 "The representation of a BGP Extended Community." 497 SYNTAX OCTET STRING(SIZE(8)) 499 bgpM2BaseScalars 500 OBJECT IDENTIFIER ::= { bgp 1 } 502 -- 503 -- Notifications 504 -- 506 bgpM2BaseNotifications 507 OBJECT IDENTIFIER ::= { bgpM2BaseScalars 0 } 509 bgpM2Established NOTIFICATION-TYPE 510 OBJECTS { 511 bgpM2PeerLocalAddrType, 512 bgpM2PeerLocalAddr, 513 bgpM2PeerRemoteAddrType, 514 bgpM2PeerRemoteAddr, 515 bgpM2PeerLastErrorReceived, 516 bgpM2PeerState 517 } 518 STATUS current 519 DESCRIPTION 520 "The BGP Established event is generated when 521 the BGP FSM enters the ESTABLISHED state." 522 ::= { bgpM2BaseNotifications 1 } 524 bgpM2BackwardTransition NOTIFICATION-TYPE 525 OBJECTS { 526 bgpM2PeerLocalAddrType, 527 bgpM2PeerLocalAddr, 528 bgpM2PeerRemoteAddrType, 529 bgpM2PeerRemoteAddr, 530 bgpM2PeerLastErrorReceived, 531 bgpM2PeerLastErrorReceivedText, 532 bgpM2PeerState 533 } 534 STATUS current 535 DESCRIPTION 536 "The BGPBackwardTransition Event is generated 537 when the BGP FSM moves from a higher numbered 538 state to a lower numbered state." 539 ::= { bgpM2BaseNotifications 2 } 541 -- 542 -- BGP Supported Version Table 543 -- 545 bgpM2Version 546 OBJECT IDENTIFIER ::= { bgpM2BaseScalars 1 } 548 bgpM2VersionTable OBJECT-TYPE 549 SYNTAX SEQUENCE OF BgpM2VersionEntry 550 MAX-ACCESS not-accessible 551 STATUS current 552 DESCRIPTION 553 "Table of supported BGP versions." 554 ::= { bgpM2Version 1 } 556 bgpM2VersionEntry OBJECT-TYPE 557 SYNTAX BgpM2VersionEntry 558 MAX-ACCESS not-accessible 559 STATUS current 560 DESCRIPTION 561 "Entry containing data on a given supported version 562 of the Border Gateway Protocol and the level of 563 support provided. It is expected that any agent 564 implementation supporting this MIB module will 565 report support for Version 4 of the Border Gateway 566 Protocol at the very minimum." 567 INDEX { 568 bgpM2VersionIndex 569 } 570 ::= { bgpM2VersionTable 1 } 572 BgpM2VersionEntry ::= SEQUENCE { 573 bgpM2VersionIndex 574 Unsigned32, 575 bgpM2VersionSupported 576 TruthValue 577 } 579 bgpM2VersionIndex OBJECT-TYPE 580 SYNTAX Unsigned32(0..255) 581 MAX-ACCESS read-only 582 STATUS current 583 DESCRIPTION 584 "The version number of the BGP Protocol." 585 ::= { bgpM2VersionEntry 1 } 587 bgpM2VersionSupported OBJECT-TYPE 588 SYNTAX TruthValue 589 MAX-ACCESS read-only 590 STATUS current 591 DESCRIPTION 592 "This value is TRUE if this version of the BGP protocol 593 identified in 'bgpM2VersionIndex' is supported. The absence 594 of a row for a particular bgpM2VersionIndex indicates that 595 that bgpM2VersionIndex protocol version number is not 596 supported." 597 ::= { bgpM2VersionEntry 2 } 599 -- 600 -- Supported authentication mechanisms 601 -- 603 bgpM2SupportedAuthentication 604 OBJECT IDENTIFIER ::= { bgpM2BaseScalars 2 } 606 bgpM2SupportedAuthTable OBJECT-TYPE 607 SYNTAX SEQUENCE OF BgpM2SupportedAuthEntry 608 MAX-ACCESS not-accessible 609 STATUS current 610 DESCRIPTION 611 "The supported BGP authentication mechanisms." 612 ::= { bgpM2SupportedAuthentication 1 } 614 bgpM2SupportedAuthEntry OBJECT-TYPE 615 SYNTAX BgpM2SupportedAuthEntry 616 MAX-ACCESS not-accessible 617 STATUS current 618 DESCRIPTION 619 "Entry containing information whether a given BGP 620 authentication mechanism is supported by this 621 implementation." 622 INDEX { 623 bgpM2SupportedAuthCode 624 } 625 ::= { bgpM2SupportedAuthTable 1 } 627 BgpM2SupportedAuthEntry ::= SEQUENCE { 628 bgpM2SupportedAuthCode 629 Unsigned32, 630 bgpM2SupportedAuthValue 631 TruthValue 632 } 634 bgpM2SupportedAuthCode OBJECT-TYPE 635 SYNTAX Unsigned32(0..255) 636 MAX-ACCESS read-only 637 STATUS current 638 DESCRIPTION 639 "The BGP authentication code." 640 ::= { bgpM2SupportedAuthEntry 1 } 642 bgpM2SupportedAuthValue OBJECT-TYPE 643 SYNTAX TruthValue 644 MAX-ACCESS read-only 645 STATUS current 646 DESCRIPTION 647 "This value is TRUE if a given authentication method 648 is supported by the local implementation." 649 ::= { bgpM2SupportedAuthEntry 2 } 651 -- 652 -- Supported BGP Capabilities 653 -- 655 bgpM2SupportedCapabilities 656 OBJECT IDENTIFIER ::= { bgpM2BaseScalars 3 } 658 bgpM2CapabilitySupportAvailable OBJECT-TYPE 659 SYNTAX TruthValue 660 MAX-ACCESS read-only 661 STATUS current 662 DESCRIPTION 663 "This value is TRUE if capability support is 664 available and is enabled." 665 ::= { bgpM2SupportedCapabilities 1 } 667 bgpM2SupportedCapabilitiesTable OBJECT-TYPE 668 SYNTAX SEQUENCE OF BgpM2SupportedCapabilityEntry 669 MAX-ACCESS not-accessible 670 STATUS current 671 DESCRIPTION 672 "Table of supported BGP-4 capabilities." 673 ::= { bgpM2SupportedCapabilities 2 } 675 bgpM2SupportedCapabilitiesEntry OBJECT-TYPE 676 SYNTAX BgpM2SupportedCapabilityEntry 677 MAX-ACCESS not-accessible 678 STATUS current 679 DESCRIPTION 680 "Information about supported capabilities indexed 681 by capability number." 682 INDEX { 683 bgpM2SupportedCapabilityCode 684 } 685 ::= { bgpM2SupportedCapabilitiesTable 1 } 687 BgpM2SupportedCapabilityEntry ::= SEQUENCE { 688 bgpM2SupportedCapabilityCode 689 Unsigned32, 690 bgpM2SupportedCapability 691 TruthValue 692 } 694 bgpM2SupportedCapabilityCode OBJECT-TYPE 695 SYNTAX Unsigned32 (0..255) 696 MAX-ACCESS read-only 697 STATUS current 698 DESCRIPTION 699 "Index of supported capability. The index directly 700 corresponds with the BGP-4 Capability Advertisement 701 Capability Code." 702 ::= { bgpM2SupportedCapabilitiesEntry 1 } 704 bgpM2SupportedCapability OBJECT-TYPE 705 SYNTAX TruthValue 706 MAX-ACCESS read-only 707 STATUS current 708 DESCRIPTION 709 "This value is True if this capability is supported, 710 False otherwise." 711 ::= { bgpM2SupportedCapabilitiesEntry 2 } 713 -- 714 -- Base Scalars 715 -- 717 bgpM2AsSize OBJECT-TYPE 718 SYNTAX INTEGER { 719 twoOctet(1), 720 fourOctet(2) 722 } 723 MAX-ACCESS read-only 724 STATUS current 725 DESCRIPTION 726 "The size of the AS value in this implementation. 728 The semantics of this are determined as per the 729 as-4bytes draft." 730 REFERENCE 731 "draft-ietf-idr-as4bytes-04" 732 ::= { bgpM2BaseScalars 4 } 734 bgpM2LocalAs OBJECT-TYPE 735 SYNTAX InetAutonomousSystemNumber 736 MAX-ACCESS read-only 737 STATUS current 738 DESCRIPTION 739 "The local autonomous system number. 741 If the bgpM2AsSize is twoOctet, then the range is 742 constrained to be 0-65535." 743 ::= { bgpM2BaseScalars 5 } 745 bgpM2LocalIdentifier OBJECT-TYPE 746 SYNTAX BgpM2Identifier 747 MAX-ACCESS read-only 748 STATUS current 749 DESCRIPTION 750 "The BGP Identifier of local system. 752 Current practice is trending away from this value being 753 treated as an IP address and more as a generic 754 identifier." 755 ::= { bgpM2BaseScalars 6 } 757 -- 758 -- Base Scalar Extensions 759 -- 761 bgpM2BaseScalarExtensions 762 OBJECT IDENTIFIER ::= { bgpM2BaseScalars 7 } 764 bgpM2BaseScalarNonCapExts 765 OBJECT IDENTIFIER ::= { bgpM2BaseScalarExtensions 1 } 767 bgpM2BaseScalarCapExts 768 OBJECT IDENTIFIER ::= { bgpM2BaseScalarExtensions 2 } 770 -- 771 -- Base Scalar Route Reflection Extensions 772 -- 774 bgpM2BaseScalarRouteReflectExts OBJECT IDENTIFIER ::= 775 { bgpM2BaseScalarNonCapExts 2796 } 777 bgpM2RouteReflector OBJECT-TYPE 778 SYNTAX TruthValue 779 MAX-ACCESS read-only 780 STATUS current 781 DESCRIPTION 782 "This value is TRUE if this implementation supports the 783 BGP Route Reflection Extension and is enabled as a 784 route reflector. If the BGP Route Reflection extension 785 is not supported this value must be FALSE." 786 REFERENCE 787 "RFC 2796 - BGP Route Reflection" 788 ::= { bgpM2BaseScalarRouteReflectExts 1 } 790 bgpM2ClusterId OBJECT-TYPE 791 SYNTAX BgpM2Identifier 792 MAX-ACCESS read-only 793 STATUS current 794 DESCRIPTION 795 "The configured Cluster-ID of the BGP Speaker. This will 796 default to the BGP Speaker's BgpM2Identifier if this 797 speaker is functioning as a route reflector and an 798 explicit Cluster-ID has not been configured. 800 A value of 0.0.0.0 will be present if Route Reflection is 801 not enabled." 802 REFERENCE 803 "RFC 2796 - BGP Route Reflection" 804 ::= { bgpM2BaseScalarRouteReflectExts 2 } 806 -- 807 -- Base Scalar AS Confederation Extensions 808 -- 810 bgpM2BaseScalarASConfedExts OBJECT IDENTIFIER ::= 811 { bgpM2BaseScalarNonCapExts 3065 } 813 bgpM2ConfederationRouter OBJECT-TYPE 814 SYNTAX TruthValue 815 MAX-ACCESS read-only 816 STATUS current 817 DESCRIPTION 818 "This value is TRUE if this implementation supports the 819 BGP AS Confederations Extension and this router is 820 configured to be in a confederation." 821 REFERENCE 822 "RFC 3065 - Autonomous System Confederations for BGP" 823 ::= { bgpM2BaseScalarASConfedExts 1 } 825 bgpM2ConfederationId OBJECT-TYPE 826 SYNTAX InetAutonomousSystemNumber 827 MAX-ACCESS read-only 828 STATUS current 829 DESCRIPTION 830 "The local Confederation Identification Number. 832 This value will be zero (0) if this BGP Speaker is not 833 a confederation router." 834 REFERENCE 835 "RFC 3065 - Autonomous System Confederations for BGP" 836 ::= { bgpM2BaseScalarASConfedExts 2 } 838 -- 839 -- Base Configuration Objects 840 -- 842 bgpM2BaseScalarConfiguration 843 OBJECT IDENTIFIER ::= { bgpM2BaseScalars 8 } 845 bgpM2CfgBaseScalarStorageType OBJECT-TYPE 846 SYNTAX StorageType 847 MAX-ACCESS read-write 848 STATUS current 849 DESCRIPTION 850 "This object specifies the intended storage type for 851 all configurable base scalars." 852 ::= { bgpM2BaseScalarConfiguration 1 } 854 bgpM2CfgLocalAs OBJECT-TYPE 855 SYNTAX InetAutonomousSystemNumber 856 MAX-ACCESS read-write 857 STATUS current 858 DESCRIPTION 859 "The local autonomous system number. 861 If the bgpM2AsSize is twoOctet, then the range is 862 constrained to be 0-65535." 863 ::= { bgpM2BaseScalarConfiguration 2 } 865 bgpM2CfgLocalIdentifier OBJECT-TYPE 866 SYNTAX BgpM2Identifier 867 MAX-ACCESS read-write 868 STATUS current 869 DESCRIPTION 870 "The BGP Identifier of local system. 872 Current practice is trending away from this value being 873 treated as an IP address and more as a generic 874 identifier." 875 ::= { bgpM2BaseScalarConfiguration 3 } 877 -- 878 -- Base Scalar Extensions 879 -- 881 bgpM2CfgBaseScalarExtensions 882 OBJECT IDENTIFIER ::= { bgpM2BaseScalarConfiguration 4 } 884 bgpM2CfgBaseScalarNonCapExts 885 OBJECT IDENTIFIER ::= { bgpM2CfgBaseScalarExtensions 1 } 887 bgpM2CfgBaseScalarCapExts 888 OBJECT IDENTIFIER ::= { bgpM2CfgBaseScalarExtensions 2 } 890 -- 891 -- Base Scalar Route Reflection Extensions 892 -- 894 bgpM2CfgBaseScalarReflectorExts 895 OBJECT IDENTIFIER ::= { bgpM2CfgBaseScalarNonCapExts 2796 } 897 bgpM2CfgRouteReflector OBJECT-TYPE 898 SYNTAX TruthValue 899 MAX-ACCESS read-write 900 STATUS current 901 DESCRIPTION 902 "This value is set to true if this implementation will 903 be supporting route reflection." 904 REFERENCE 905 "RFC 2796 - BGP Route Reflection" 906 ::= { bgpM2CfgBaseScalarReflectorExts 1 } 908 bgpM2CfgClusterId OBJECT-TYPE 909 SYNTAX BgpM2Identifier 910 MAX-ACCESS read-write 911 STATUS current 912 DESCRIPTION 913 "The configured Cluster-ID of the BGP Speaker. This will 914 default to the BGP Speaker's BgpM2Identifier if this 915 speaker is functioning as a route reflector and an 916 explicit Cluster-ID has not been configured. 918 A value of 0.0.0.0 will be present if Route Reflection is 919 not enabled." 920 REFERENCE 921 "RFC 2796 - BGP Route Reflection" 922 ::= { bgpM2CfgBaseScalarReflectorExts 2 } 924 -- 925 -- Base Scalar AS Confederation Extensions 926 -- 928 bgpM2CfgBaseScalarASConfedExts 929 OBJECT IDENTIFIER ::= { bgpM2CfgBaseScalarNonCapExts 3065 } 931 bgpM2CfgConfederationRouter OBJECT-TYPE 932 SYNTAX TruthValue 933 MAX-ACCESS read-write 934 STATUS current 935 DESCRIPTION 936 "This value is set to true if this implementation will be 937 supporting BGP AS Confederations." 938 REFERENCE 939 "RFC 3065 - Autonomous System Confederations for BGP" 940 ::= { bgpM2CfgBaseScalarASConfedExts 1 } 942 bgpM2CfgConfederationId OBJECT-TYPE 943 SYNTAX InetAutonomousSystemNumber 944 MAX-ACCESS read-write 945 STATUS current 946 DESCRIPTION 947 "The local Confederation Identification Number. 949 This value will be zero (0) if this BGP Speaker is not 950 a confederation router." 951 REFERENCE 952 "RFC 3065 - Autonomous System Confederations for BGP" 953 ::= { bgpM2CfgBaseScalarASConfedExts 2 } 955 -- 956 -- BGP Peer Data 957 -- 959 bgpM2Peer 960 OBJECT IDENTIFIER ::= { bgp 2 } 962 bgpM2PeerData 963 OBJECT IDENTIFIER ::= { bgpM2Peer 1 } 965 bgpM2PeerTable OBJECT-TYPE 966 SYNTAX SEQUENCE OF BgpM2PeerEntry 967 MAX-ACCESS not-accessible 968 STATUS current 969 DESCRIPTION 970 "BGP peer table. 972 This table contains, one entry per BGP peer, 973 and information about the connections with BGP 974 peers." 975 ::= { bgpM2PeerData 1 } 977 bgpM2PeerEntry OBJECT-TYPE 978 SYNTAX BgpM2PeerEntry 979 MAX-ACCESS not-accessible 980 STATUS current 981 DESCRIPTION 982 "Entry containing information about the connection with 983 a BGP peer." 984 INDEX { 985 bgpM2PeerLocalAddrType, 986 bgpM2PeerLocalAddr, 987 bgpM2PeerRemoteAddrType, 988 bgpM2PeerRemoteAddr 989 } 990 ::= { bgpM2PeerTable 1 } 992 BgpM2PeerEntry ::= SEQUENCE { 993 bgpM2PeerIdentifier 994 BgpM2Identifier, 995 bgpM2PeerState 996 INTEGER, 997 bgpM2PeerStatus 998 INTEGER, 999 bgpM2PeerConfiguredVersion 1000 Unsigned32, 1001 bgpM2PeerNegotiatedVersion 1002 Unsigned32, 1003 bgpM2PeerLocalAddrType 1004 InetAddressType, 1005 bgpM2PeerLocalAddr 1006 InetAddress, 1007 bgpM2PeerLocalPort 1008 InetPortNumber, 1009 bgpM2PeerLocalAs 1010 InetAutonomousSystemNumber, 1011 bgpM2PeerRemoteAddrType 1012 InetAddressType, 1013 bgpM2PeerRemoteAddr 1014 InetAddress, 1015 bgpM2PeerRemotePort 1016 InetPortNumber, 1017 bgpM2PeerRemoteAs 1018 InetAutonomousSystemNumber, 1019 bgpM2PeerIndex 1020 Unsigned32 1021 } 1023 bgpM2PeerIdentifier OBJECT-TYPE 1024 SYNTAX BgpM2Identifier 1025 MAX-ACCESS read-only 1026 STATUS current 1027 DESCRIPTION 1028 "The BGP Identifier of this entry's BGP peer. 1030 This entry should be 0.0.0.0 unless the bgpM2PeerState is 1031 in the OpenConfirm or the Established state." 1033 REFERENCE 1034 "draft-ietf-idr-bgp4-17.txt, Sec. 4.2" 1035 ::= { bgpM2PeerEntry 1 } 1037 bgpM2PeerState OBJECT-TYPE 1038 SYNTAX INTEGER { 1039 idle(1), 1040 connect(2), 1041 active(3), 1042 opensent(4), 1043 openconfirm(5), 1044 established(6) 1045 } 1046 MAX-ACCESS read-only 1047 STATUS current 1048 DESCRIPTION 1049 "The BGP peer's FSM state." 1050 REFERENCE 1051 "draft-ietf-idr-bgp4-17.txt, Sec. 8" 1052 ::= { bgpM2PeerEntry 2 } 1054 bgpM2PeerStatus OBJECT-TYPE 1055 SYNTAX INTEGER { 1056 halted(1), 1057 running(2) 1058 } 1059 MAX-ACCESS read-only 1060 STATUS current 1061 DESCRIPTION 1062 "Whether or not the BGP FSM for this peer is halted or 1063 running. The BGP FSM for a peer is halted after 1064 processing a Stop event. Likewise, it is in the running 1065 state after a Start event. 1067 The bgpM2PeerState will generally be in the idle state when 1068 the FSM is halted, although some extensions such as 1069 Graceful Restart will leave the peer in the Idle state 1070 but with the FSM running." 1071 ::= { bgpM2PeerEntry 3 } 1073 bgpM2PeerConfiguredVersion OBJECT-TYPE 1074 SYNTAX Unsigned32 (1..255) 1075 MAX-ACCESS read-only 1076 STATUS current 1077 DESCRIPTION 1078 "The configured version to originally start with this 1079 peer. The BGP speaker may permit negotiation to a 1080 lower version number of the protocol." 1081 ::= { bgpM2PeerEntry 4 } 1083 bgpM2PeerNegotiatedVersion OBJECT-TYPE 1084 SYNTAX Unsigned32 (1..255) 1085 MAX-ACCESS read-only 1086 STATUS current 1087 DESCRIPTION 1088 "The negotiated version of BGP running between the two 1089 peers." 1090 ::= { bgpM2PeerEntry 5 } 1092 bgpM2PeerLocalAddrType OBJECT-TYPE 1093 SYNTAX InetAddressType 1094 MAX-ACCESS read-only 1095 STATUS current 1096 DESCRIPTION 1097 "The address family of the local end of the peering 1098 session." 1099 ::= { bgpM2PeerEntry 6 } 1101 bgpM2PeerLocalAddr OBJECT-TYPE 1102 SYNTAX InetAddress (SIZE(4..20)) 1103 MAX-ACCESS read-only 1104 STATUS current 1105 DESCRIPTION 1106 "The address of the local end of the peering session." 1107 ::= { bgpM2PeerEntry 7 } 1109 bgpM2PeerLocalPort OBJECT-TYPE 1110 SYNTAX InetPortNumber 1111 MAX-ACCESS read-only 1112 STATUS current 1113 DESCRIPTION 1114 "The local port for the TCP connection between the BGP 1115 peers." 1116 ::= { bgpM2PeerEntry 8 } 1118 bgpM2PeerLocalAs OBJECT-TYPE 1119 SYNTAX InetAutonomousSystemNumber 1120 MAX-ACCESS read-only 1121 STATUS current 1122 DESCRIPTION 1123 "Some implementations of BGP can represent themselves 1124 as multiple ASs. This is the AS that this peering 1125 session is representing itself as to the remote peer." 1126 ::= { bgpM2PeerEntry 9 } 1128 bgpM2PeerRemoteAddrType OBJECT-TYPE 1129 SYNTAX InetAddressType 1130 MAX-ACCESS read-only 1131 STATUS current 1132 DESCRIPTION 1133 "The address family of the remote end of the peering 1134 session." 1135 ::= { bgpM2PeerEntry 10 } 1137 bgpM2PeerRemoteAddr OBJECT-TYPE 1138 SYNTAX InetAddress (SIZE(4..20)) 1139 MAX-ACCESS read-only 1140 STATUS current 1141 DESCRIPTION 1142 "The address of the remote end of the peering session." 1143 ::= { bgpM2PeerEntry 11 } 1145 bgpM2PeerRemotePort OBJECT-TYPE 1146 SYNTAX InetPortNumber 1147 MAX-ACCESS read-only 1148 STATUS current 1149 DESCRIPTION 1150 "The remote port for the TCP connection between the BGP 1151 peers. In the case of a transport for which the notion 1152 of 'port' is irrelevant, an instance value of -1 1153 should be returned by the agent for this object. 1155 Note that the objects bgpM2PeerLocalAddr, 1156 bgpM2PeerLocalPort, bgpM2PeerRemoteAddr and 1157 bgpM2PeerRemotePort provide the appropriate reference to 1158 the standard MIB TCP connection table. or even the ipv6 1159 TCP MIB as in rfc2452." 1160 REFERENCE 1161 "RFC 2012 - SNMPv2 Management Information Base for the 1162 Transmission Control Protocol using SMIv2. 1163 RFC 2542 - IP Version 6 Management Information Base 1164 for the Transmission Control Protocol." 1165 ::= { bgpM2PeerEntry 12 } 1167 bgpM2PeerRemoteAs OBJECT-TYPE 1168 SYNTAX InetAutonomousSystemNumber 1169 MAX-ACCESS read-only 1170 STATUS current 1171 DESCRIPTION 1172 "The remote autonomous system number." 1173 ::= { bgpM2PeerEntry 13 } 1175 bgpM2PeerIndex OBJECT-TYPE 1176 SYNTAX Unsigned32 1177 MAX-ACCESS read-only 1178 STATUS current 1179 DESCRIPTION 1180 "This value is a unique index for the peer entry in the 1181 bgpM2PeerTable. It is assigned by the agent at the point 1182 of creation of the bgpM2PeerTable row entry. While its 1183 value is guaranteed to be unique at any time, it is 1184 otherwise opaque to the management application with 1185 respect to its value or the contiguity of bgpM2PeerIndex 1186 row instance values across rows of the bgpM2PeerTable. It 1187 is used to provide an index structure for other tables 1188 whose data is logically per-peer. 1190 For explicitly configured peers, this value will remain 1191 consistent until this row is deleted by deleting the 1192 configured peers. Unconfigured peers will generate 1193 a monotonically increasing number when a BGP FSM is 1194 built to process the peering session. Values in the 1195 bgpM2PeerTable and other tables utilizing bgpM2PeerIndex 1196 are expected to remain in existence for an arbitrary 1197 time after the unconfigured peer has been deleted 1198 in order to allow management applications to extract 1199 useful management information for those peers. Thus, 1200 an unconfigured peer using the same indices as the 1201 bgpM2PeerTable that comes up while this row still 1202 exists will re-utilize the same row." 1203 ::= { bgpM2PeerEntry 14 } 1205 -- 1206 -- Errors 1207 -- 1209 bgpM2PeerErrors 1210 OBJECT IDENTIFIER ::= { bgpM2Peer 2 } 1212 bgpM2PeerErrorsTable OBJECT-TYPE 1213 SYNTAX SEQUENCE OF BgpM2PeerErrorsEntry 1214 MAX-ACCESS not-accessible 1215 STATUS current 1216 DESCRIPTION 1217 "On a per peer basis, this table reflects the last 1218 protocol-defined error encountered and reported on 1219 the peer session. If no entry for a given peer, 1220 by its bgpM2PeerIndex, exists in this table, then no 1221 such errors have been observed, reported, and 1222 recorded on the session." 1223 ::= { bgpM2PeerErrors 1 } 1225 bgpM2PeerErrorsEntry OBJECT-TYPE 1226 SYNTAX BgpM2PeerErrorsEntry 1227 MAX-ACCESS not-accessible 1228 STATUS current 1229 DESCRIPTION 1230 "Each entry contains information about errors sent 1231 and received for a particular BGP peer." 1232 AUGMENTS { 1233 bgpM2PeerEntry 1234 } 1235 ::= { bgpM2PeerErrorsTable 1 } 1237 BgpM2PeerErrorsEntry ::= SEQUENCE { 1238 bgpM2PeerLastErrorReceived 1239 OCTET STRING, 1240 bgpM2PeerLastErrorSent 1241 OCTET STRING, 1242 bgpM2PeerLastErrorReceivedTime 1243 TimeTicks, 1244 bgpM2PeerLastErrorSentTime 1245 TimeTicks, 1246 bgpM2PeerLastErrorReceivedText 1247 DisplayString, 1248 bgpM2PeerLastErrorSentText 1249 DisplayString, 1250 bgpM2PeerLastErrorReceivedData 1251 OCTET STRING, 1252 bgpM2PeerLastErrorSentData 1253 OCTET STRING 1254 } 1256 bgpM2PeerLastErrorReceived OBJECT-TYPE 1257 SYNTAX OCTET STRING (SIZE (2)) 1258 MAX-ACCESS read-only 1259 STATUS current 1260 DESCRIPTION 1261 "The last error code and subcode received by this BGP 1262 Speaker via a NOTIFICATION message for this peer. 1263 If no error has occurred, this field is zero. 1264 Otherwise, the first byte of this two byte 1265 OCTET STRING contains the error code, and the second 1266 byte contains the subcode." 1267 REFERENCE 1268 "draft-ietf-idr-bgp4-15.txt, Sec. 4.5" 1269 ::= { bgpM2PeerErrorsEntry 1 } 1271 bgpM2PeerLastErrorSent OBJECT-TYPE 1272 SYNTAX OCTET STRING (SIZE (2)) 1273 MAX-ACCESS read-only 1274 STATUS current 1275 DESCRIPTION 1276 "The last error code and subcode sent by this BGP 1277 Speaker via a NOTIFICATION message to this peer. 1278 If no error has occurred, this field is zero. 1279 Otherwise, the first byte of this two byte 1280 OCTET STRING contains the error code, and the second 1281 byte contains the subcode." 1282 REFERENCE 1283 "draft-ietf-idr-bgp4-15.txt, Sec. 4.5" 1284 ::= { bgpM2PeerErrorsEntry 2 } 1286 bgpM2PeerLastErrorReceivedTime OBJECT-TYPE 1287 SYNTAX TimeTicks 1288 MAX-ACCESS read-only 1289 STATUS current 1290 DESCRIPTION 1291 "The timestamp that the last NOTIFICATION was received from 1292 this peer." 1293 REFERENCE 1294 "draft-ietf-idr-bgp4-15.txt, Sec. 4.5" 1295 ::= { bgpM2PeerErrorsEntry 3 } 1297 bgpM2PeerLastErrorSentTime OBJECT-TYPE 1298 SYNTAX TimeTicks 1299 MAX-ACCESS read-only 1300 STATUS current 1301 DESCRIPTION 1302 "The timestamp that the last NOTIFICATION was sent to 1303 this peer." 1304 REFERENCE 1305 "draft-ietf-idr-bgp4-15.txt, Sec. 4.5" 1306 ::= { bgpM2PeerErrorsEntry 4 } 1308 bgpM2PeerLastErrorReceivedText OBJECT-TYPE 1309 SYNTAX DisplayString 1310 MAX-ACCESS read-only 1311 STATUS current 1312 DESCRIPTION 1313 "This object contains an implementation specific 1314 explanation of the error that was reported." 1315 ::= { bgpM2PeerErrorsEntry 5 } 1317 bgpM2PeerLastErrorSentText OBJECT-TYPE 1318 SYNTAX DisplayString 1319 MAX-ACCESS read-only 1320 STATUS current 1321 DESCRIPTION 1322 "This object contains an implementation specific 1323 explanation of the error that is being reported." 1324 ::= { bgpM2PeerErrorsEntry 6 } 1326 bgpM2PeerLastErrorReceivedData OBJECT-TYPE 1327 SYNTAX OCTET STRING (SIZE(0..4075)) 1328 MAX-ACCESS read-only 1329 STATUS current 1330 DESCRIPTION 1331 "The last error code's data seen by this peer." 1332 REFERENCE 1333 "draft-ietf-idr-bgp4-15.txt, Sec. 4.5" 1334 ::= { bgpM2PeerErrorsEntry 7 } 1336 bgpM2PeerLastErrorSentData OBJECT-TYPE 1337 SYNTAX OCTET STRING (SIZE(0..4075)) 1338 MAX-ACCESS read-only 1339 STATUS current 1340 DESCRIPTION 1341 "The last error code's data sent to this peer." 1342 REFERENCE 1343 "draft-ietf-idr-bgp4-15.txt, Sec. 4.5" 1344 ::= { bgpM2PeerErrorsEntry 8 } 1346 -- 1347 -- Peer Authentication 1348 -- 1350 bgpM2PeerAuthentication 1351 OBJECT IDENTIFIER ::= { bgpM2Peer 3 } 1353 bgpM2PeerAuthTable OBJECT-TYPE 1354 SYNTAX SEQUENCE OF BgpM2PeerAuthEntry 1355 MAX-ACCESS not-accessible 1356 STATUS current 1357 DESCRIPTION 1358 "BGP peer authentication table. 1360 This table contains, one entry per BGP peer, 1361 information about the authentication with BGP peers." 1362 ::= { bgpM2PeerAuthentication 1 } 1364 bgpM2PeerAuthEntry OBJECT-TYPE 1365 SYNTAX BgpM2PeerAuthEntry 1366 MAX-ACCESS not-accessible 1367 STATUS current 1368 DESCRIPTION 1369 "Entry containing information about the authentication 1370 with a BGP peer." 1371 AUGMENTS { 1372 bgpM2PeerEntry 1373 } 1374 ::= { bgpM2PeerAuthTable 1 } 1376 BgpM2PeerAuthEntry ::= SEQUENCE { 1377 bgpM2PeerAuthSent 1378 TruthValue, 1379 bgpM2PeerAuthSentCode 1380 Unsigned32, 1381 bgpM2PeerAuthSentValue 1382 OCTET STRING, 1383 bgpM2PeerAuthRcvd 1384 TruthValue, 1385 bgpM2PeerAuthRcvdCode 1386 Unsigned32, 1387 bgpM2PeerAuthRcvdValue 1388 OCTET STRING 1389 } 1390 bgpM2PeerAuthSent OBJECT-TYPE 1391 SYNTAX TruthValue 1392 MAX-ACCESS read-only 1393 STATUS current 1394 DESCRIPTION 1395 "The local peer has sent authentication information 1396 to the remote peer in the BGP Authentication field." 1397 ::= { bgpM2PeerAuthEntry 1 } 1399 bgpM2PeerAuthSentCode OBJECT-TYPE 1400 SYNTAX Unsigned32 (0..255) 1401 MAX-ACCESS read-only 1402 STATUS current 1403 DESCRIPTION 1404 "The code of the authentication information sent to 1405 the remote peer." 1406 ::= { bgpM2PeerAuthEntry 2 } 1408 bgpM2PeerAuthSentValue OBJECT-TYPE 1409 SYNTAX OCTET STRING (SIZE (0..252)) 1410 MAX-ACCESS read-only 1411 STATUS current 1412 DESCRIPTION 1413 "The payload of the authentication information 1414 from the remote peer." 1415 ::= { bgpM2PeerAuthEntry 3 } 1417 bgpM2PeerAuthRcvd OBJECT-TYPE 1418 SYNTAX TruthValue 1419 MAX-ACCESS read-only 1420 STATUS current 1421 DESCRIPTION 1422 "The local peer has received authentication information 1423 from the remote peer in the BGP Authentication field." 1424 ::= { bgpM2PeerAuthEntry 4 } 1426 bgpM2PeerAuthRcvdCode OBJECT-TYPE 1427 SYNTAX Unsigned32 (0..255) 1428 MAX-ACCESS read-only 1429 STATUS current 1430 DESCRIPTION 1431 "The code of the authentication information received from 1432 the remote peer." 1433 ::= { bgpM2PeerAuthEntry 5 } 1435 bgpM2PeerAuthRcvdValue OBJECT-TYPE 1436 SYNTAX OCTET STRING (SIZE (0..252)) 1437 MAX-ACCESS read-only 1438 STATUS current 1439 DESCRIPTION 1440 "The payload of the authentication information from 1441 the remote peer." 1442 ::= { bgpM2PeerAuthEntry 6 } 1444 -- 1445 -- Peer Event Times 1446 -- 1448 bgpM2PeerTimers 1449 OBJECT IDENTIFIER ::= { bgpM2Peer 4 } 1451 bgpM2PeerEventTimesTable OBJECT-TYPE 1452 SYNTAX SEQUENCE OF BgpM2PeerEventTimesEntry 1453 MAX-ACCESS not-accessible 1454 STATUS current 1455 DESCRIPTION 1456 "A table reporting the per-peering session amount 1457 of time elapsed and update events since the peering 1458 session advanced into the Established state." 1459 ::= { bgpM2PeerTimers 1 } 1461 bgpM2PeerEventTimesEntry OBJECT-TYPE 1462 SYNTAX BgpM2PeerEventTimesEntry 1463 MAX-ACCESS not-accessible 1464 STATUS current 1465 DESCRIPTION 1466 "Each row contains a set of statistics about time 1467 spent and events encountered in the peer session 1468 Established state." 1469 AUGMENTS { 1470 bgpM2PeerEntry 1471 } 1472 ::= { bgpM2PeerEventTimesTable 1 } 1474 BgpM2PeerEventTimesEntry ::= SEQUENCE { 1475 bgpM2PeerFsmEstablishedTime 1476 Gauge32, 1477 bgpM2PeerInUpdatesElapsedTime 1478 Gauge32 1480 } 1482 bgpM2PeerFsmEstablishedTime OBJECT-TYPE 1483 SYNTAX Gauge32 1484 MAX-ACCESS read-only 1485 STATUS current 1486 DESCRIPTION 1487 "This timer indicates how long (in seconds) this 1488 peer has been in the Established state or how long 1489 since this peer was last in the Established state. 1490 It is set to zero when a new peer is configured or 1491 the router is booted." 1492 ::= { bgpM2PeerEventTimesEntry 1 } 1494 bgpM2PeerInUpdatesElapsedTime OBJECT-TYPE 1495 SYNTAX Gauge32 1496 MAX-ACCESS read-only 1497 STATUS current 1498 DESCRIPTION 1499 "Elapsed time in seconds since the last BGP UPDATE 1500 message was received from the peer. Each time 1501 bgpM2PeerInUpdates is incremented, the value of this 1502 object is set to zero (0). This value shall also be 1503 zero (0) when the peer is not in the Established state" 1504 ::= { bgpM2PeerEventTimesEntry 2 } 1506 -- 1507 -- Peer Configured Timers 1508 -- 1510 bgpM2PeerConfiguredTimersTable OBJECT-TYPE 1511 SYNTAX SEQUENCE OF BgpM2PeerConfiguredTimersEntry 1512 MAX-ACCESS not-accessible 1513 STATUS current 1514 DESCRIPTION 1515 "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." 1526 AUGMENTS { 1527 bgpM2PeerEntry 1528 } 1529 ::= { bgpM2PeerConfiguredTimersTable 1 } 1531 BgpM2PeerConfiguredTimersEntry ::= SEQUENCE { 1532 bgpM2PeerConnectRetryInterval 1533 Unsigned32, 1534 bgpM2PeerHoldTimeConfigured 1535 Unsigned32, 1536 bgpM2PeerKeepAliveConfigured 1537 Unsigned32, 1538 bgpM2PeerMinASOrigInterval 1539 Unsigned32, 1540 bgpM2PeerMinRouteAdverInterval 1541 Unsigned32 1542 } 1544 bgpM2PeerConnectRetryInterval OBJECT-TYPE 1545 SYNTAX Unsigned32 (1..65535) 1546 MAX-ACCESS read-only 1547 STATUS current 1548 DESCRIPTION 1549 "Time interval in seconds for the ConnectRetry 1550 timer. The suggested value for this timer is 120 1551 seconds." 1552 ::= { bgpM2PeerConfiguredTimersEntry 1 } 1554 bgpM2PeerHoldTimeConfigured OBJECT-TYPE 1555 SYNTAX Unsigned32 ( 0 | 3..65535 ) 1556 MAX-ACCESS read-only 1557 STATUS current 1558 DESCRIPTION 1559 "Time interval in seconds for the Hold Time configured 1560 for this BGP speaker with this peer. This value 1561 is placed in an OPEN message sent to this peer by 1562 this BGP speaker, and is compared with the Hold 1563 Time field in an OPEN message received from the 1564 peer when determining the Hold Time (bgpM2PeerHoldTime) 1565 with the peer. This value must not be less than 1566 three seconds if it is not zero (0) in which case 1567 the Hold Time is NOT to be established with the 1568 peer. The suggested value for this timer is 90 1569 seconds." 1570 REFERENCE 1571 "draft-ietf-idr-bgp4-17.txt, Appendix 6.4" 1572 ::= { bgpM2PeerConfiguredTimersEntry 2 } 1574 bgpM2PeerKeepAliveConfigured OBJECT-TYPE 1575 SYNTAX Unsigned32 ( 0 | 1..21845 ) 1576 MAX-ACCESS read-only 1577 STATUS current 1578 DESCRIPTION 1579 "Time interval in seconds for the KeepAlive timer 1580 configured for this BGP speaker with this peer. 1581 The value of this object will only determine the 1582 KEEPALIVE messages frequency relative to the value 1583 specified in bgpM2PeerHoldTimeConfigured; the actual 1584 time interval for the KEEPALIVE messages is indicated 1585 by bgpM2PeerKeepAlive. A reasonable maximum value 1586 for this timer would be configured to be one third 1587 of that of bgpM2PeerHoldTimeConfigured. 1589 If the value of this object is zero (0), no 1590 periodical KEEPALIVE messages are sent to the peer 1591 after the BGP connection has been established. 1592 The suggested value for this timer is 30 seconds." 1593 REFERENCE 1594 "draft-ietf-idr-bgp4-17.txt, Appendix 6.4" 1595 ::= { bgpM2PeerConfiguredTimersEntry 3 } 1597 bgpM2PeerMinASOrigInterval OBJECT-TYPE 1598 SYNTAX Unsigned32 (0..65535) 1599 MAX-ACCESS read-only 1600 STATUS current 1601 DESCRIPTION 1602 "Time interval in seconds for the MinASOriginationInterval 1603 timer. The suggested value for this timer is 15 1604 seconds." 1605 ::= { bgpM2PeerConfiguredTimersEntry 4 } 1607 bgpM2PeerMinRouteAdverInterval OBJECT-TYPE 1608 SYNTAX Unsigned32 (0..65535) 1609 MAX-ACCESS read-only 1610 STATUS current 1611 DESCRIPTION 1612 "Time interval in seconds for the 1613 MinRouteAdvertisementInterval timer. The suggested 1614 value for this timer is 30 seconds." 1615 ::= { bgpM2PeerConfiguredTimersEntry 5 } 1617 -- 1618 -- Peer Negotiated Timers 1619 -- 1621 bgpM2PeerNegotiatedTimersTable OBJECT-TYPE 1622 SYNTAX SEQUENCE OF BgpM2PeerNegotiatedTimersEntry 1623 MAX-ACCESS not-accessible 1624 STATUS current 1625 DESCRIPTION 1626 "Current values of per-peer timers which can be 1627 dynamically set in the bgpM2PeerConfiguredTimersTable. 1628 Values reflected in this table are the current 1629 operational values, after negotiation from values 1630 derived from initial configuration or last set from 1631 bgpM2PeerConfiguredTimersTable row instances." 1632 ::= { bgpM2PeerTimers 3 } 1634 bgpM2PeerNegotiatedTimersEntry OBJECT-TYPE 1635 SYNTAX BgpM2PeerNegotiatedTimersEntry 1636 MAX-ACCESS not-accessible 1637 STATUS current 1638 DESCRIPTION 1639 "Each entry reflects a value of the currently 1640 operational, negotiated timers as reflected in the 1641 BgpM2PeerNegotiatedTimersEntry." 1642 AUGMENTS { 1643 bgpM2PeerEntry 1644 } 1645 ::= { bgpM2PeerNegotiatedTimersTable 1 } 1647 BgpM2PeerNegotiatedTimersEntry ::= SEQUENCE { 1648 bgpM2PeerHoldTime 1649 Unsigned32, 1650 bgpM2PeerKeepAlive 1651 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; 1661 zero (0) - if this was the value sent by the peer and 1662 this value is permitted by this BGP Speaker. In this 1663 case, no keepalive messages are sent and the Hold Timer 1664 is not set. 1666 At least three (3). This value is the smaller of 1667 the value sent by this peer in the OPEN message and 1668 bgpM2PeerHoldTimeConfigured for this peer. 1670 This value is only defined when the peering session is 1671 in the Established state." 1672 REFERENCE 1673 "draft-ietf-idr-bgp4-17.txt, Sec. 4.2" 1674 ::= { bgpM2PeerNegotiatedTimersEntry 1 } 1676 bgpM2PeerKeepAlive OBJECT-TYPE 1677 SYNTAX Unsigned32 ( 0 | 1..21845 ) 1678 MAX-ACCESS read-only 1679 STATUS current 1680 DESCRIPTION 1681 "Time interval in seconds for the KeepAlive timer 1682 established with the peer. The value of this object 1683 is calculated by this BGP speaker such that, when 1684 compared with bgpM2PeerHoldTime, it has the same 1685 proportion as what bgpM2PeerKeepAliveConfigured has 1686 when compared with bgpM2PeerHoldTimeConfigured. If 1687 the value of this object is zero (0), it indicates 1688 that the KeepAlive timer has not been established 1689 with the peer, or, the value of 1690 bgpM2PeerKeepAliveConfigured is zero (0). 1692 This value is only defined when the peering session is 1693 in the Established state." 1694 REFERENCE 1695 "draft-ietf-idr-bgp4-17, Sec. 4.4" 1696 ::= { bgpM2PeerNegotiatedTimersEntry 2 } 1698 -- 1699 -- Peer Capabilities 1700 -- 1702 bgpM2PeerCapabilities 1703 OBJECT IDENTIFIER ::= { bgpM2Peer 5 } 1705 -- 1706 -- Announced Capabilities 1707 -- 1709 bgpM2PeerCapsAnnouncedTable OBJECT-TYPE 1710 SYNTAX SEQUENCE OF BgpM2PeerCapsAnnouncedEntry 1711 MAX-ACCESS not-accessible 1712 STATUS current 1713 DESCRIPTION 1714 "This table contains the capabilities 1715 that are supported for a given peer." 1716 ::= { bgpM2PeerCapabilities 1 } 1718 bgpM2PeerCapsAnnouncedEntry OBJECT-TYPE 1719 SYNTAX BgpM2PeerCapsAnnouncedEntry 1720 MAX-ACCESS not-accessible 1721 STATUS current 1722 DESCRIPTION 1723 "These entries are keyed by a BGP-4 peer remote 1724 address and the BGP Capability Code" 1725 INDEX { 1726 bgpM2PeerIndex, 1727 bgpM2PeerCapAnnouncedCode, 1728 bgpM2PeerCapAnnouncedIndex 1729 } 1730 ::= { bgpM2PeerCapsAnnouncedTable 1 } 1732 BgpM2PeerCapsAnnouncedEntry ::= SEQUENCE { 1733 bgpM2PeerCapAnnouncedCode 1734 Unsigned32, 1735 bgpM2PeerCapAnnouncedIndex 1736 Unsigned32, 1737 bgpM2PeerCapAnnouncedValue 1738 OCTET STRING 1739 } 1741 bgpM2PeerCapAnnouncedCode OBJECT-TYPE 1742 SYNTAX Unsigned32 (0..255) 1743 MAX-ACCESS read-only 1744 STATUS current 1745 DESCRIPTION 1746 "The BGP Capability Advertisement Capability Code." 1747 ::= { bgpM2PeerCapsAnnouncedEntry 1 } 1749 bgpM2PeerCapAnnouncedIndex OBJECT-TYPE 1750 SYNTAX Unsigned32 (1..128) 1751 MAX-ACCESS read-only 1752 STATUS current 1753 DESCRIPTION 1754 "Multiple instances of a given capability may be sent 1755 bgp a BGP speaker. This variable is used to index them." 1756 ::= { bgpM2PeerCapsAnnouncedEntry 2 } 1758 bgpM2PeerCapAnnouncedValue OBJECT-TYPE 1759 SYNTAX OCTET STRING (SIZE(0..255)) 1760 MAX-ACCESS read-only 1761 STATUS current 1762 DESCRIPTION 1763 "The value of the announced capability." 1764 ::= { bgpM2PeerCapsAnnouncedEntry 3 } 1766 -- 1767 -- Received Capabilities 1768 -- 1770 bgpM2PeerCapsReceivedTable OBJECT-TYPE 1771 SYNTAX SEQUENCE OF BgpM24PeerCapsReceivedEntry 1772 MAX-ACCESS not-accessible 1773 STATUS current 1774 DESCRIPTION 1775 "This table contains the capabilities 1776 that are supported for a given peer." 1777 ::= { bgpM2PeerCapabilities 2 } 1779 bgpM2PeerCapsReceivedEntry OBJECT-TYPE 1780 SYNTAX BgpM24PeerCapsReceivedEntry 1781 MAX-ACCESS not-accessible 1782 STATUS current 1783 DESCRIPTION 1784 "These entries are keyed by a BGP-4 peer remote 1785 address and the BGP Capability Code" 1786 INDEX { 1787 bgpM2PeerIndex, 1788 bgpM2PeerCapReceivedCode, 1789 bgpM2PeerCapReceivedIndex 1790 } 1791 ::= { bgpM2PeerCapsReceivedTable 1 } 1793 BgpM24PeerCapsReceivedEntry ::= SEQUENCE { 1794 bgpM2PeerCapReceivedCode 1795 Unsigned32, 1796 bgpM2PeerCapReceivedIndex 1797 Unsigned32, 1798 bgpM2PeerCapReceivedValue 1799 OCTET STRING 1800 } 1802 bgpM2PeerCapReceivedCode OBJECT-TYPE 1803 SYNTAX Unsigned32 (0..255) 1804 MAX-ACCESS read-only 1805 STATUS current 1806 DESCRIPTION 1807 "The BGP Capability Advertisement Capability Code." 1808 ::= { bgpM2PeerCapsReceivedEntry 1 } 1810 bgpM2PeerCapReceivedIndex OBJECT-TYPE 1811 SYNTAX Unsigned32 (1..128) 1812 MAX-ACCESS read-only 1813 STATUS current 1814 DESCRIPTION 1815 "Multiple instances of a given capability may be sent 1816 bgp a BGP speaker. This variable is used to index them." 1817 ::= { bgpM2PeerCapsReceivedEntry 2 } 1819 bgpM2PeerCapReceivedValue OBJECT-TYPE 1820 SYNTAX OCTET STRING (SIZE(0..255)) 1821 MAX-ACCESS read-only 1822 STATUS current 1823 DESCRIPTION 1824 "The value of the announced capability." 1825 ::= { bgpM2PeerCapsReceivedEntry 3 } 1827 -- 1828 -- Per-peer counters 1829 -- 1831 bgpM2PeerCounters 1832 OBJECT IDENTIFIER ::= { bgpM2Peer 6 } 1834 bgpM2PeerCountersTable OBJECT-TYPE 1835 SYNTAX SEQUENCE OF BgpM2PeerCountersEntry 1836 MAX-ACCESS not-accessible 1837 STATUS current 1838 DESCRIPTION 1839 "The counters associated with a BGP Peer." 1840 ::= { bgpM2PeerCounters 1 } 1842 bgpM2PeerCountersEntry OBJECT-TYPE 1843 SYNTAX BgpM2PeerCountersEntry 1844 MAX-ACCESS not-accessible 1845 STATUS current 1846 DESCRIPTION 1847 "Each entry contains counters of message transmissions 1848 and FSM transitions for a given BGP Peering session." 1849 AUGMENTS { 1850 bgpM2PeerEntry 1851 } 1852 ::= { bgpM2PeerCountersTable 1 } 1854 BgpM2PeerCountersEntry ::= SEQUENCE { 1855 bgpM2PeerInUpdates 1856 Counter32, 1857 bgpM2PeerOutUpdates 1858 Counter32, 1859 bgpM2PeerInTotalMessages 1860 Counter32, 1861 bgpM2PeerOutTotalMessages 1862 Counter32, 1863 bgpM2PeerFsmEstablishedTrans 1864 Counter32 1865 } 1867 -- +++wayne need to describe what happens if connection is broken 1868 -- and then reestablished. Does the prior counter value accumulate? 1869 bgpM2PeerInUpdates OBJECT-TYPE 1870 SYNTAX Counter32 1871 MAX-ACCESS read-only 1872 STATUS current 1873 DESCRIPTION 1874 "The number of BGP UPDATE messages received on this 1875 connection. This object should be initialized to zero 1876 (0) when the connection is established." 1877 ::= { bgpM2PeerCountersEntry 1 } 1879 bgpM2PeerOutUpdates OBJECT-TYPE 1880 SYNTAX Counter32 1881 MAX-ACCESS read-only 1882 STATUS current 1883 DESCRIPTION 1884 "The number of BGP UPDATE messages transmitted on this 1885 connection. This object should be initialized to zero 1886 (0) when the connection is established." 1887 ::= { bgpM2PeerCountersEntry 2 } 1889 bgpM2PeerInTotalMessages OBJECT-TYPE 1890 SYNTAX Counter32 1891 MAX-ACCESS read-only 1892 STATUS current 1893 DESCRIPTION 1894 "The total number of messages received from the remote 1895 peer on this connection. This object should be 1896 initialized to zero when the connection is established." 1897 ::= { bgpM2PeerCountersEntry 3 } 1899 bgpM2PeerOutTotalMessages OBJECT-TYPE 1900 SYNTAX Counter32 1901 MAX-ACCESS read-only 1902 STATUS current 1903 DESCRIPTION 1904 "The total number of messages transmitted to the remote 1905 peer on this connection. This object should be 1906 initialized to zero when the connection is established." 1907 ::= { bgpM2PeerCountersEntry 4 } 1909 bgpM2PeerFsmEstablishedTrans OBJECT-TYPE 1910 SYNTAX Counter32 1911 MAX-ACCESS read-only 1912 STATUS current 1913 DESCRIPTION 1914 "The total number of times the BGP FSM 1915 transitioned into the established state 1916 for this peer." 1917 ::= { bgpM2PeerCountersEntry 5 } 1919 -- 1920 -- Per-Peer Prefix Counters 1921 -- 1923 bgpM2PrefixCountersTable OBJECT-TYPE 1924 SYNTAX SEQUENCE OF BgpM2PrefixCountersEntry 1925 MAX-ACCESS not-accessible 1926 STATUS current 1927 DESCRIPTION 1928 "Additional per-peer, per AFI SAFI counters for prefixes" 1929 ::= { bgpM2PeerCounters 2 } 1931 bgpM2PrefixCountersEntry OBJECT-TYPE 1932 SYNTAX BgpM2PrefixCountersEntry 1933 MAX-ACCESS not-accessible 1934 STATUS current 1935 DESCRIPTION 1936 "Entry containing information about a bgp-peers prefix 1937 counters." 1938 INDEX { 1939 bgpM2PeerIndex, 1940 bgpM2PrefixCountersAfi, 1941 bgpM2PrefixCountersSafi 1942 } 1943 ::= { bgpM2PrefixCountersTable 1 } 1945 BgpM2PrefixCountersEntry ::= SEQUENCE { 1946 bgpM2PrefixCountersAfi 1947 InetAddressType, 1948 bgpM2PrefixCountersSafi 1949 BgpM2Safi, 1950 bgpM2PrefixInPrefixes 1951 Gauge32, 1952 bgpM2PrefixInPrefixesAccepted 1953 Gauge32, 1954 bgpM2PrefixInPrefixesRejected 1955 Gauge32, 1956 bgpM2PrefixOutPrefixes 1957 Gauge32 1958 } 1960 bgpM2PrefixCountersAfi OBJECT-TYPE 1961 SYNTAX InetAddressType 1962 MAX-ACCESS read-only 1963 STATUS current 1964 DESCRIPTION 1965 "The AFI index of the per-peer, per prefix counters" 1966 ::= { bgpM2PrefixCountersEntry 1 } 1968 bgpM2PrefixCountersSafi OBJECT-TYPE 1969 SYNTAX BgpM2Safi 1970 MAX-ACCESS read-only 1971 STATUS current 1972 DESCRIPTION 1973 "The SAFI index of the per-peer, per prefix counters" 1974 ::= { bgpM2PrefixCountersEntry 2 } 1976 bgpM2PrefixInPrefixes OBJECT-TYPE 1977 SYNTAX Gauge32 1978 MAX-ACCESS read-only 1979 STATUS current 1980 DESCRIPTION 1981 "The number of prefixes received from a peer and are 1982 stored in the Adj-Ribs-In for that peer." 1983 -- jmh - note that we are allowing stuff to be discarded 1984 ::= { bgpM2PrefixCountersEntry 7 } 1986 bgpM2PrefixInPrefixesAccepted OBJECT-TYPE 1987 SYNTAX Gauge32 1988 MAX-ACCESS read-only 1989 STATUS current 1990 DESCRIPTION 1991 "The number of prefixes for a peer that are installed 1992 in the Adj-Ribs-In and are eligible to become active 1993 in the Loc-Rib." 1994 ::= { bgpM2PrefixCountersEntry 8 } 1996 bgpM2PrefixInPrefixesRejected OBJECT-TYPE 1997 SYNTAX Gauge32 1998 MAX-ACCESS read-only 1999 STATUS current 2000 DESCRIPTION 2001 "The number of prefixes for a peer that are installed 2002 in the Adj-Ribs-In and are NOT eligible to become active 2003 in the Loc-Rib." 2004 ::= { bgpM2PrefixCountersEntry 9 } 2006 bgpM2PrefixOutPrefixes OBJECT-TYPE 2007 SYNTAX Gauge32 2008 MAX-ACCESS read-only 2009 STATUS current 2010 DESCRIPTION 2011 "The number of prefixes for a peer that are installed 2012 in that peers Adj-Ribs-Out." 2014 ::= { bgpM2PrefixCountersEntry 10 } 2016 bgpM2PeerExtensions 2017 OBJECT IDENTIFIER ::= { bgpM2Peer 7 } 2019 bgpM2PeerNonCapExts 2020 OBJECT IDENTIFIER ::= { bgpM2PeerExtensions 1 } 2022 bgpM2PeerCapExts 2023 OBJECT IDENTIFIER ::= { bgpM2PeerExtensions 2 } 2025 -- 2026 -- Peer Route Reflection Extensions 2027 -- 2029 bgpM2PeerRouteReflectionExts 2030 OBJECT IDENTIFIER ::= { bgpM2PeerNonCapExts 2796 } 2032 bgpM2PeerReflectorClientTable OBJECT-TYPE 2033 SYNTAX SEQUENCE OF BgpM2PeerReflectorClientEntry 2034 MAX-ACCESS not-accessible 2035 STATUS current 2036 DESCRIPTION 2037 "Table of route reflection client settings on a per-peer 2038 basis." 2039 REFERENCE 2040 "RFC 2796 - BGP Route Reflection" 2041 ::= { bgpM2PeerRouteReflectionExts 1 } 2043 bgpM2PeerReflectorClientEntry OBJECT-TYPE 2044 SYNTAX BgpM2PeerReflectorClientEntry 2045 MAX-ACCESS not-accessible 2046 STATUS current 2047 DESCRIPTION 2048 "Entry containing data on a per-peer basis on whether 2049 the peer is configured as a route reflector client." 2050 REFERENCE 2051 "RFC 2796 - BGP Route Reflection" 2052 AUGMENTS { 2053 bgpM2PeerEntry 2054 } 2055 ::= { bgpM2PeerReflectorClientTable 1 } 2057 BgpM2PeerReflectorClientEntry ::= SEQUENCE { 2058 bgpM2PeerReflectorClient 2059 INTEGER 2060 } 2062 bgpM2PeerReflectorClient OBJECT-TYPE 2063 SYNTAX INTEGER { 2064 nonClient(0), 2065 client(1), 2066 meshedClient(2) 2067 } 2068 MAX-ACCESS read-only 2069 STATUS current 2070 DESCRIPTION 2071 "This value indicates whether the given peer is a 2072 reflector client of this router, or not. A value of 2073 nonClient indicates that this peer is not a reflector 2074 client. A value of client indicates that this peer is a 2075 reflector client that is not fully meshed with other 2076 reflector clients. A value of meshedClient indicates 2077 that the peer is a reflector client and is fully meshed 2078 with all other reflector clients. 2080 This value must be nonClient (0) for BGP external peers." 2081 REFERENCE 2082 "RFC 2796 - BGP Route Reflection" 2083 ::= { bgpM2PeerReflectorClientEntry 1 } 2085 -- 2086 -- Peer AS Confederations Extensions 2087 -- 2089 bgpM2PeerASConfederationExts 2090 OBJECT IDENTIFIER ::= { bgpM2PeerNonCapExts 3065 } 2092 bgpM2PeerConfedMemberTable OBJECT-TYPE 2093 SYNTAX SEQUENCE OF BgpM2PeerConfedMemberEntry 2094 MAX-ACCESS not-accessible 2095 STATUS current 2096 DESCRIPTION 2097 "Table of confederation member settings on a per-peer 2098 basis." 2099 REFERENCE 2100 "RFC 3065 - BGP Confederations" 2101 ::= { bgpM2PeerASConfederationExts 1 } 2103 bgpM2PeerConfedMemberEntry OBJECT-TYPE 2104 SYNTAX BgpM2PeerConfedMemberEntry 2105 MAX-ACCESS not-accessible 2106 STATUS current 2107 DESCRIPTION 2108 "Entry containing data on a per-peer basis on whether 2109 the peer is configured as a BGP confederation member." 2110 REFERENCE 2111 "RFC 3065 - BGP Confederations" 2112 AUGMENTS { 2113 bgpM2PeerEntry 2114 } 2115 ::= { bgpM2PeerConfedMemberTable 1 } 2117 BgpM2PeerConfedMemberEntry ::= SEQUENCE { 2118 bgpM2PeerConfedMember 2119 TruthValue 2120 } 2122 bgpM2PeerConfedMember OBJECT-TYPE 2123 SYNTAX TruthValue 2124 MAX-ACCESS read-only 2125 STATUS current 2126 DESCRIPTION 2127 "This value indicates whether the given peer is in our 2128 confederation or not." 2129 REFERENCE 2130 "RFC 3065 - BGP Confederations" 2131 ::= { bgpM2PeerConfedMemberEntry 1 } 2133 -- 2134 -- Peer configuration objects 2135 -- 2137 bgpM2PeerConfiguration 2138 OBJECT IDENTIFIER ::= { bgpM2Peer 8 } 2140 -- 2141 -- Administering activated peering sessions 2142 -- 2143 bgpM2CfgPeerAdminStatusTable OBJECT-TYPE 2144 SYNTAX SEQUENCE OF BgpM2CfgPeerAdminStatusEntry 2145 MAX-ACCESS not-accessible 2146 STATUS current 2147 DESCRIPTION 2148 "Table containing rows for administratively starting and 2149 stopping peering sessions." 2150 ::= { bgpM2PeerConfiguration 1 } 2152 bgpM2CfgPeerAdminStatusEntry OBJECT-TYPE 2153 SYNTAX BgpM2CfgPeerAdminStatusEntry 2154 MAX-ACCESS not-accessible 2155 STATUS current 2156 DESCRIPTION 2157 "Entry containing row for administratively starting and 2158 stopping peers." 2159 INDEX { 2160 bgpM2PeerIndex 2161 } 2162 ::= { bgpM2CfgPeerAdminStatusTable 1 } 2164 BgpM2CfgPeerAdminStatusEntry ::= SEQUENCE { 2165 bgpM2CfgPeerAdminStatus 2166 INTEGER 2167 } 2169 bgpM2CfgPeerAdminStatus OBJECT-TYPE 2170 SYNTAX INTEGER { 2171 stop(1), 2172 start(2) 2173 } 2174 MAX-ACCESS read-write 2175 STATUS current 2176 DESCRIPTION 2177 "This object allows the Manual Stop and Manual Start 2178 events to be sent to an activated peering session." 2179 ::= { bgpM2CfgPeerAdminStatusEntry 1 } 2181 -- 2182 -- Peer Configuration 2183 -- 2185 bgpM2CfgPeerNextIndex OBJECT-TYPE 2186 SYNTAX Integer32 (0..65535) 2187 MAX-ACCESS read-only 2188 STATUS current 2189 DESCRIPTION 2190 "This object contains the next appropriate value to 2191 use as an index for creation of a row instance in 2192 in the bgpM2CfgPeerTable. If the number of available 2193 entries in the bgpM2CfgPeerTable is exhausted, a 2194 retrieval value of this object instance will return 2195 0. A value of 0 may also be returned if the agent 2196 is otherwise incapable of bgpM2CfgPeerTable row creation 2197 at the time of bgpM2CfgPeerNextIndex retrieval." 2198 ::= { bgpM2PeerConfiguration 2 } 2200 bgpM2CfgPeerTable OBJECT-TYPE 2201 SYNTAX SEQUENCE OF BgpM2CfgPeerEntry 2202 MAX-ACCESS not-accessible 2203 STATUS current 2204 DESCRIPTION 2205 "BGP configuration peer table. 2207 This table allows the configuration of the parameters 2208 for a session with a BGP peer. 2210 +++wayne provide description of how config should be done 2211 for a peer per table." 2212 ::= { bgpM2PeerConfiguration 3 } 2214 bgpM2CfgPeerEntry OBJECT-TYPE 2215 SYNTAX BgpM2CfgPeerEntry 2216 MAX-ACCESS not-accessible 2217 STATUS current 2218 DESCRIPTION 2219 "Entry containing information set up by a management 2220 entity to configure a connection with a BGP peer." 2221 INDEX { bgpM2CfgPeerIndex } 2222 ::= { bgpM2CfgPeerTable 1 } 2224 BgpM2CfgPeerEntry ::= SEQUENCE { 2225 bgpM2CfgPeerConfiguredVersion 2226 Unsigned32, 2227 bgpM2CfgAllowVersionNegotiation 2228 TruthValue, 2229 bgpM2CfgPeerLocalAddrType 2230 InetAddressType, 2231 bgpM2CfgPeerLocalAddr 2232 InetAddress, 2233 bgpM2CfgPeerLocalAs 2234 InetAutonomousSystemNumber, 2235 bgpM2CfgPeerRemoteAddrType 2236 InetAddressType, 2237 bgpM2CfgPeerRemoteAddr 2238 InetAddress, 2239 bgpM2CfgPeerRemotePort 2240 Integer32, 2241 bgpM2CfgPeerRemoteAs 2242 InetAutonomousSystemNumber, 2243 bgpM2CfgPeerEntryStorageType 2244 StorageType, 2245 bgpM2CfgPeerError 2246 INTEGER, 2247 bgpM2CfgPeerBgpPeerEntry 2248 RowPointer, 2249 bgpM2CfgPeerRowEntryStatus 2250 RowStatus, 2251 bgpM2CfgPeerIndex 2252 Integer32, 2253 bgpM2CfgPeerStatus 2254 INTEGER 2255 } 2257 bgpM2CfgPeerConfiguredVersion OBJECT-TYPE 2258 SYNTAX Unsigned32 (1..255) 2259 MAX-ACCESS read-create 2260 STATUS current 2261 DESCRIPTION 2262 "The configured version to originally start with 2263 this peer. The BGP speaker may permit negotiation 2264 to a lower version number of the protocol depending on the 2265 set value of bgpM2CfgAllowVersionNegotiation." 2266 DEFVAL { 4 } 2267 ::= { bgpM2CfgPeerEntry 1 } 2269 bgpM2CfgAllowVersionNegotiation OBJECT-TYPE 2270 SYNTAX TruthValue 2271 MAX-ACCESS read-create 2272 STATUS current 2273 DESCRIPTION 2274 "If set to true, during session establishment with this 2275 peer, negotiation to a version lower than that specified 2276 in bgpM2CfgPeerConfiguredVersion will be allowed." 2277 DEFVAL { false } 2278 ::= { bgpM2CfgPeerEntry 2 } 2280 bgpM2CfgPeerLocalAddrType OBJECT-TYPE 2281 SYNTAX InetAddressType 2282 MAX-ACCESS read-create 2283 STATUS current 2284 DESCRIPTION 2285 "The address family of the speakers of this BGP 2286 session." 2287 ::= { bgpM2CfgPeerEntry 3 } 2289 bgpM2CfgPeerLocalAddr OBJECT-TYPE 2290 SYNTAX InetAddress (SIZE (4..20)) 2291 MAX-ACCESS read-create 2292 STATUS current 2293 DESCRIPTION 2294 "The address of the local end of the peering session." 2295 ::= { bgpM2CfgPeerEntry 4 } 2297 bgpM2CfgPeerLocalAs OBJECT-TYPE 2298 SYNTAX InetAutonomousSystemNumber 2299 MAX-ACCESS read-create 2300 STATUS current 2301 DESCRIPTION 2302 "Autonomous system represented to peer on peering 2303 session initialization. Some implementations of 2304 BGP can represent themselves as multiple ASes. 2305 These implementations can set this to an alternate 2306 autonomous system. If this object is set to zero 2307 (0) at the point this row instance is set to active, 2308 then the implementation will initialize this session 2309 representing itself as the value of bgpM2CfgLocalAs." 2310 DEFVAL { 0 } 2311 ::= { bgpM2CfgPeerEntry 5 } 2313 bgpM2CfgPeerRemoteAddrType OBJECT-TYPE 2314 SYNTAX InetAddressType 2315 MAX-ACCESS read-create 2316 STATUS current 2317 DESCRIPTION 2318 "The address family of the speakers of the remote BGP 2319 session." 2320 ::= { bgpM2CfgPeerEntry 6 } 2322 bgpM2CfgPeerRemoteAddr OBJECT-TYPE 2323 SYNTAX InetAddress (SIZE(4..20)) 2324 MAX-ACCESS read-create 2325 STATUS current 2326 DESCRIPTION 2327 "The address of the remote end (destination address 2328 of peer) for peering session." 2329 ::= { bgpM2CfgPeerEntry 7 } 2331 -- JMH - this isn't compatible with InetPortNumber 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 -- JMH - Can we mix caps the enumerations? 2362 bgpM2CfgPeerError OBJECT-TYPE 2363 SYNTAX INTEGER { 2364 unknown(0), 2365 notactivated (1), 2366 errduplicatepeeringsession (2), 2367 activated (3) 2368 -- +++wayne more to follow 2369 } 2370 MAX-ACCESS read-only 2371 STATUS current 2372 DESCRIPTION 2373 "This value indicates the current error status of 2374 the row denoting the configured error status. 2376 If this row is still under creation (has not been activated 2377 bgpM2CfgPeerRowEntryStatus), then this instance will be set to 2378 not-activated (1). 2380 At the point that the row is activated, bgpM2CfgPeerError 2381 will reflect the error status of the row data itself. If 2382 there is another session already activated with the same 2383 local and remote addresses as denoted by 2384 {bgpM2CfgPeerLocalAddrType, bgpM2CfgPeerLocalAddr, 2385 bgpM2CfgPeerRemoteAddr, bgpM2CfgPeerRemotePort}, then 2386 the value of this will be set to 2387 err-duplicate-peering-session (2). 2389 If this row is associated with a peer session whose 2390 initialization has been attempted, the value will be 2391 set to activated (3) (and, bgpM2PeerCfgPeerEntry will 2392 be set to the row instance of the entry in the 2393 bgpM2PeerTable which reflects the state of the peering 2394 session). 2396 Note that this object only reflects the error as a 2397 function of the attempted activation of this row as 2398 containing data for a bgp peering session. The actual 2399 state of the session at the point of any protocol exchange 2400 or session state machine initiation is reflected in the 2401 bgpM2PeerTable row instance (as reflected through 2402 bgpM2CfgPeerPeerEntry) associated with this row instance." 2403 ::= { bgpM2CfgPeerEntry 11 } 2405 bgpM2CfgPeerBgpPeerEntry OBJECT-TYPE 2406 SYNTAX RowPointer 2407 MAX-ACCESS read-only 2408 STATUS current 2409 DESCRIPTION 2410 "Upon activation of the session data contained in this 2411 row instance, this object points to an instance of a row 2412 within the bgpM2PeerTable reflecting the session in its 2413 initializing or operational state. Retrieval of this 2414 column instance will always yield a value of {0.0} unless 2415 the session has successfully been activated (via 2416 bgpM2CfgPeerRowEntryStatus). Such row instances will always 2417 have a value of bgpM2CfgPeerError which is activated (3)." 2418 ::= { bgpM2CfgPeerEntry 12 } 2420 bgpM2CfgPeerRowEntryStatus OBJECT-TYPE 2421 SYNTAX RowStatus 2422 MAX-ACCESS read-create 2423 STATUS current 2424 DESCRIPTION 2425 "This object type is used to control creation, 2426 activation, and deletion of this row instance." 2427 -- +++wayne need better directions for agent auto-removal 2428 -- of row instances which have moved to active or error 2429 -- state 2430 ::= { bgpM2CfgPeerEntry 13 } 2432 bgpM2CfgPeerIndex OBJECT-TYPE 2433 SYNTAX Integer32 (1..65535) 2434 MAX-ACCESS accessible-for-notify 2435 STATUS current 2436 DESCRIPTION 2437 "Uniquely identifies an instance of a peer row, as 2438 an element of configuration." 2439 ::= { bgpM2CfgPeerEntry 14 } 2441 bgpM2CfgPeerStatus OBJECT-TYPE 2442 SYNTAX INTEGER { 2443 halted(1), 2444 running(2) 2445 } 2446 MAX-ACCESS read-create 2447 STATUS current 2448 DESCRIPTION 2449 "This specifies the state of the peering session upon 2450 activation. If disabled, the FSM is in the halted 2451 state and no Automatic Start events are generated. 2452 If enabled, the FSM is in the running state and 2453 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." 2498 DEFVAL { 2499 false 2500 } 2501 ::= { bgpM2CfgPeerAuthEntry 1 } 2503 bgpM2CfgPeerAuthCode OBJECT-TYPE 2504 SYNTAX Unsigned32(0..255) 2505 MAX-ACCESS read-create 2506 STATUS current 2507 DESCRIPTION 2508 "The authentication code for the BGP Authentication 2509 mechanism." 2510 REFERENCE 2511 "draft-ietf-idr-bgp4-17.txt, Sec. 4.1.a" 2512 ::= { bgpM2CfgPeerAuthEntry 2 } 2514 bgpM2CfgPeerAuthValue OBJECT-TYPE 2515 SYNTAX OCTET STRING (SIZE(0..252)) 2516 MAX-ACCESS read-create 2517 STATUS current 2518 DESCRIPTION 2519 "The authentication payload for the BGP authentication 2520 mechanism. This value has semantic meaning within 2521 the context of the authentication code." 2522 REFERENCE 2523 "draft-ietf-idr-bgp4-17.txt, Sec. 4.1.a" 2524 ::= { bgpM2CfgPeerAuthEntry 3 } 2526 -- 2527 -- Per-peer timers table 2528 -- 2530 bgpM2CfgPeerTimersTable OBJECT-TYPE 2531 SYNTAX SEQUENCE OF BgpM2CfgPeerTimersEntry 2532 MAX-ACCESS not-accessible 2533 STATUS current 2534 DESCRIPTION 2535 "Table for configuration of per-peer timers." 2536 ::= { bgpM2PeerConfiguration 5 } 2538 bgpM2CfgPeerTimersEntry OBJECT-TYPE 2539 SYNTAX BgpM2CfgPeerTimersEntry 2540 MAX-ACCESS not-accessible 2541 STATUS current 2542 DESCRIPTION 2543 "Entry containing per-peer timer configuration." 2544 AUGMENTS { 2545 bgpM2CfgPeerEntry 2546 } 2547 ::= { bgpM2CfgPeerTimersTable 1 } 2549 BgpM2CfgPeerTimersEntry ::= SEQUENCE { 2550 bgpM2CfgPeerConnectRetryInterval 2551 Unsigned32, 2552 bgpM2CfgPeerHoldTimeConfigured 2553 Unsigned32, 2554 bgpM2CfgPeerKeepAliveConfigured 2555 Unsigned32, 2556 bgpM2CfgPeerMinASOrigInterval 2557 Unsigned32, 2558 bgpM2CfgPeerMinRouteAdverInter 2559 Unsigned32 2560 } 2562 bgpM2CfgPeerConnectRetryInterval OBJECT-TYPE 2563 SYNTAX Unsigned32 (1..65535) 2564 MAX-ACCESS read-create 2565 STATUS current 2566 DESCRIPTION 2567 "Time interval in seconds for the ConnectRetry 2568 timer. The suggested value for this timer is 120 2569 seconds." 2570 DEFVAL { 2571 120 2572 } 2573 ::= { bgpM2CfgPeerTimersEntry 1 } 2575 bgpM2CfgPeerHoldTimeConfigured OBJECT-TYPE 2576 SYNTAX Unsigned32 ( 0 | 3..65535 ) 2577 MAX-ACCESS read-create 2578 STATUS current 2579 DESCRIPTION 2580 "Time interval in seconds for the Hold Time configured 2581 for this BGP speaker with this peer. This value 2582 is placed in an OPEN message sent to this peer by 2583 this BGP speaker, and is compared with the Hold 2584 Time field in an OPEN message received from the 2585 peer when determining the Hold Time (bgpM2PeerHoldTime) 2586 with the peer. This value must not be less than 2587 three seconds if it is not zero (0) in which case 2588 the Hold Time is NOT to be established with the 2589 peer. The suggested value for this timer is 90 2590 seconds." 2591 REFERENCE 2592 "draft-ietf-idr-bgp4-17.txt, Appendix 6.4" 2593 DEFVAL { 2594 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" 2722 ::= { bgpM2CfgPeerReflectorClientEntry 1 } 2724 -- 2725 -- Peer AS Confederations Extensions 2726 -- 2728 bgpM2CfgPeerASConfederationExts 2729 OBJECT IDENTIFIER ::= { bgpM2CfgPeerNonCapExts 3065 } 2731 bgpM2CfgPeerConfedMemberTable OBJECT-TYPE 2732 SYNTAX SEQUENCE OF BgpM2CfgPeerConfedMemberEntry 2733 MAX-ACCESS not-accessible 2734 STATUS current 2735 DESCRIPTION 2736 "Table of confederation member settings on a per-peer 2737 basis." 2738 REFERENCE 2739 "RFC 3065 - BGP Confederations" 2740 ::= { bgpM2CfgPeerASConfederationExts 1 } 2742 bgpM2CfgPeerConfedMemberEntry OBJECT-TYPE 2743 SYNTAX BgpM2CfgPeerConfedMemberEntry 2744 MAX-ACCESS not-accessible 2745 STATUS current 2746 DESCRIPTION 2747 "Entry containing data on a per-peer basis on whether 2748 the peer is configured as a BGP confederation member." 2749 REFERENCE 2750 "RFC 3065 - BGP Confederations" 2751 AUGMENTS { 2752 bgpM2PeerEntry 2753 } 2754 ::= { bgpM2CfgPeerConfedMemberTable 1 } 2756 BgpM2CfgPeerConfedMemberEntry ::= SEQUENCE { 2757 bgpM2CfgPeerConfedMember 2758 TruthValue 2759 } 2761 bgpM2CfgPeerConfedMember OBJECT-TYPE 2762 SYNTAX TruthValue 2763 MAX-ACCESS read-create 2764 STATUS current 2765 DESCRIPTION 2766 "This value indicates whether the given peer is in our 2767 confederation or not." 2768 REFERENCE 2769 "RFC 3065 - BGP Confederations" 2770 ::= { bgpM2CfgPeerConfedMemberEntry 1 } 2772 -- 2773 -- BGP NLRI Data 2774 -- 2776 bgpM2Rib 2777 OBJECT IDENTIFIER ::= { bgp 3 } 2779 -- 2780 -- NLRI Table 2781 -- 2783 bgpM2NlriTable OBJECT-TYPE 2784 SYNTAX SEQUENCE OF BgpM2NlriEntry 2785 MAX-ACCESS not-accessible 2786 STATUS current 2787 DESCRIPTION 2788 "The BGP-4 Received Path Attribute Table contains 2789 information about paths to destination networks 2790 received from all BGP4 peers. Collectively, this 2791 represents the Adj-Ribs-In. The route where 2792 bgpM2NlriBest is TRUE represents, for this NLRI, 2793 the route that is installed in the LocRib from the 2794 Adj-Ribs-In." 2795 ::= { bgpM2Rib 1 } 2797 bgpM2NlriEntry OBJECT-TYPE 2798 SYNTAX BgpM2NlriEntry 2799 MAX-ACCESS not-accessible 2800 STATUS current 2801 DESCRIPTION 2802 "Information about a path to a network." 2803 INDEX { 2804 bgpM2PeerIndex, 2805 bgpM2NlriAfi, 2806 bgpM2NlriSafi, 2807 bgpM2NlriPrefixLen, 2808 bgpM2NlriPrefix, 2809 bgpM2NlriIndex 2810 } 2811 ::= { bgpM2NlriTable 1 } 2813 BgpM2NlriEntry ::= SEQUENCE { 2814 bgpM2NlriIndex 2815 Unsigned32, 2816 bgpM2NlriAfi 2817 InetAddressType, 2818 bgpM2NlriSafi 2819 BgpM2Safi, 2820 bgpM2NlriPrefixLen 2821 InetAddressPrefixLength, 2822 bgpM2NlriPrefix 2823 InetAddress, 2824 bgpM2NlriBest 2825 TruthValue, 2826 bgpM2NlriCalcLocalPref 2827 Unsigned32, 2828 bgpM2PathAttrIndex 2829 Unsigned32, 2830 bgpM2NlriOpaqueType 2831 INTEGER, 2832 bgpM2NlriOpaquePointer 2833 RowPointer 2834 } 2836 bgpM2NlriIndex OBJECT-TYPE 2837 SYNTAX Unsigned32 2838 MAX-ACCESS read-only 2839 STATUS current 2840 DESCRIPTION 2841 "This index allows for multiple instances of a base 2842 prefix for a certain AFI SAFI from a given peer. 2843 This is currently useful for two things: 2844 1. Allowing for a peer in future implementations to 2845 send more than a single route instance. 2846 2. Allow for extensions which extend the NLRI field 2847 to send the same prefix while utilizing other 2848 extension specific information. An example of 2849 this is RFC 3107 - Carrying MPLS labels in BGP." 2850 REFERENCE 2851 "RFC 3107 - Carrying Label Information in BGP-4" 2852 ::= { bgpM2NlriEntry 1 } 2854 bgpM2NlriAfi OBJECT-TYPE 2855 SYNTAX InetAddressType 2856 MAX-ACCESS read-only 2857 STATUS current 2858 DESCRIPTION 2859 "The address family of the prefix for this NLRI." 2860 ::= { bgpM2NlriEntry 2 } 2862 bgpM2NlriSafi OBJECT-TYPE 2863 SYNTAX BgpM2Safi 2864 MAX-ACCESS read-only 2865 STATUS current 2866 DESCRIPTION 2867 "The subsequent address family of the prefix for 2868 this NLRI" 2869 REFERENCE 2870 "RFC 2858 - Multiprotocol Extensions for BGP-4" 2871 ::= { bgpM2NlriEntry 3 } 2873 bgpM2NlriPrefixLen OBJECT-TYPE 2874 SYNTAX InetAddressPrefixLength 2875 MAX-ACCESS read-only 2876 STATUS current 2877 DESCRIPTION 2878 "Length in bits of the address prefix in 2879 the Network Layer Reachability Information field." 2880 ::= { bgpM2NlriEntry 4 } 2882 bgpM2NlriPrefix OBJECT-TYPE 2883 SYNTAX InetAddress (SIZE (4..20)) 2884 MAX-ACCESS read-only 2885 STATUS current 2886 DESCRIPTION 2887 "An IP address prefix in the Network Layer 2888 Reachability Information field. This object 2889 is an IP address containing the prefix with 2890 length specified by 2891 bgpM2PathAttrAddrPrefixLen. 2892 Any bits beyond the length specified by 2893 bgpM2PathAttrAddrPrefixLen are zeroed." 2894 ::= { bgpM2NlriEntry 5 } 2896 bgpM2NlriBest OBJECT-TYPE 2897 SYNTAX TruthValue 2898 MAX-ACCESS read-only 2899 STATUS current 2900 DESCRIPTION 2901 "An indication of whether or not this route 2902 was chosen as the best BGP4 route." 2903 ::= { bgpM2NlriEntry 6 } 2905 bgpM2NlriCalcLocalPref OBJECT-TYPE 2906 SYNTAX Unsigned32 2907 MAX-ACCESS read-only 2908 STATUS current 2909 DESCRIPTION 2910 "The degree of preference calculated by the 2911 receiving BGP4 speaker for an advertised 2912 route." 2913 ::= { bgpM2NlriEntry 7 } 2915 bgpM2PathAttrIndex OBJECT-TYPE 2916 SYNTAX Unsigned32 2917 MAX-ACCESS read-only 2918 STATUS current 2919 DESCRIPTION 2920 "This value is a unique index for the per-NLRI entry 2921 in the bgpM2PeerAttrTable. It is assigned by the 2922 agent at the point of creation of the bgpM2PeerAttrTable 2923 row entry. While its value is guaranteed to be unique 2924 at any time, it is otherwise opaque to the management 2925 application with respect to its value or the contiguity 2926 of bgpM2PeerAttrIndex row instance values across rows 2927 of the bgpM2PeerAttrTable. It is used to provide an 2928 index structure for other tables whose data is logically 2929 per-peer, per-NLRI." 2930 ::= { bgpM2NlriEntry 8 } 2932 bgpM2NlriOpaqueType OBJECT-TYPE 2933 SYNTAX INTEGER { 2934 none(0), 2935 bgpMplsLabelStack(1) 2936 } 2937 MAX-ACCESS read-only 2938 STATUS current 2939 DESCRIPTION 2940 "This object enumerates the type of the row that is 2941 pointed to in the table row bgpM2NlriOpaquePointer 2942 instance, if bgpM2NlriOpaquePointer is in fact not 2943 a zero length. bgpM2NlriOpaqueType is necessary since 2944 the data referenced by bgpM2NlriOpaquePointer is 2945 opaque to BGP. For example, in the case of RFC 3107, 2946 the label stack that is pointed to may occur in the 2947 mplsLabelStackTable from the MPLS-LSR-MIB, and the 2948 instance value of bgpM2NlriOpaqueType would be 2949 bgpMplsLabelStack(1)." 2950 REFERENCE 2951 "RFC 3107 - Carrying Label Information in BGP-4 2952 draft-ietf-mpls-lsr-mib-08.txt" 2953 ::= { bgpM2NlriEntry 9 } 2955 bgpM2NlriOpaquePointer OBJECT-TYPE 2956 SYNTAX RowPointer 2957 MAX-ACCESS read-only 2958 STATUS current 2959 DESCRIPTION 2960 "Pointer to a row that decomposes the data that is 2961 opaque to the BGP MIB but is sent in the NLRI. 2962 This RowPointer has zero (0) length data instance 2963 if bgpM2NlriOpaqueType is none." 2964 ::= { bgpM2NlriEntry 10 } 2966 -- 2967 -- Adj-Ribs-Out Table 2968 -- 2970 bgpM2AdjRibsOutTable OBJECT-TYPE 2971 SYNTAX SEQUENCE OF BgpM2AdjRibsOutEntry 2972 MAX-ACCESS not-accessible 2973 STATUS current 2974 DESCRIPTION 2975 "This table contains on a per-peer basis one or more 2976 routes from the bgpM2NlriTable that have been 2977 placed in this peer's Adj-Ribs-Out." 2978 REFERENCE 2979 "draft-ietf-idr-bgp4-17.txt, Sec. 3.2" 2980 ::= { bgpM2Rib 2 } 2982 bgpM2AdjRibsOutEntry OBJECT-TYPE 2983 SYNTAX BgpM2AdjRibsOutEntry 2984 MAX-ACCESS not-accessible 2985 STATUS current 2986 DESCRIPTION 2987 "List of BGP routes that have been placed into a 2988 peer's Adj-Ribs-Out." 2989 INDEX { 2990 bgpM2PeerIndex, 2991 bgpM2NlriAfi, 2992 bgpM2NlriSafi, 2993 bgpM2NlriPrefixLen, 2994 bgpM2NlriPrefix, 2995 bgpM2AdjRibsOutIndex 2996 } 2997 ::= { bgpM2AdjRibsOutTable 1 } 2999 BgpM2AdjRibsOutEntry ::= SEQUENCE { 3000 bgpM2AdjRibsOutIndex 3001 Unsigned32, 3002 bgpM2AdjRibsOutRoute 3003 RowPointer 3004 } 3006 bgpM2AdjRibsOutIndex OBJECT-TYPE 3007 SYNTAX Unsigned32 3008 MAX-ACCESS read-only 3009 STATUS current 3010 DESCRIPTION 3011 "Certain extensions to BGP permit multiple instance of 3012 a per afi, per safi prefix to be advertised to a peer. 3013 This object allows the enumeration of them." 3014 ::= { bgpM2AdjRibsOutEntry 1 } 3016 bgpM2AdjRibsOutRoute OBJECT-TYPE 3017 SYNTAX RowPointer 3018 MAX-ACCESS read-only 3019 STATUS current 3020 DESCRIPTION 3021 "This object points to the route in the bgpM2NlriTable 3022 that corresponds to the entry in the peer's 3023 Adj-Rib-Out. Outgoing route maps are not 3024 reflected at this point as those are part of the 3025 Update-Send process." 3026 REFERENCE 3027 "draft-ietf-idr-bgp4-17.txt, Sec. 9.2" 3028 ::= { bgpM2AdjRibsOutEntry 2 } 3030 -- 3031 -- BGP Rib Path Attributes Table 3032 -- 3034 -- 3035 -- Path Attribute Counter 3036 -- 3038 bgpM2PathAttrCount OBJECT-TYPE 3039 SYNTAX Counter32 3040 MAX-ACCESS read-only 3041 STATUS current 3042 DESCRIPTION 3043 "The number of entries in the bgpM2PathAttrTable." 3044 ::= { bgpM2Rib 3 } 3046 -- 3047 -- Path Attributes Table 3048 -- 3050 bgpM2PathAttrTable OBJECT-TYPE 3051 SYNTAX SEQUENCE OF BgpM2PathAttrEntry 3052 MAX-ACCESS not-accessible 3053 STATUS current 3054 DESCRIPTION 3055 "Provides per advertised network-prefix attribute data, 3056 as advertised over a peering session." 3057 ::= { bgpM2Rib 4 } 3059 bgpM2PathAttrEntry OBJECT-TYPE 3060 SYNTAX BgpM2PathAttrEntry 3061 MAX-ACCESS not-accessible 3062 STATUS current 3063 DESCRIPTION 3064 "Each entry contains data about a given network 3065 prefix, per-prefix and per-advertising peer." 3066 INDEX { 3067 bgpM2PathAttrIndex 3068 } 3069 ::= { bgpM2PathAttrTable 1 } 3071 BgpM2PathAttrEntry ::= SEQUENCE { 3072 bgpM2PathAttrOrigin 3073 INTEGER, 3074 bgpM2PathAttrNextHopAddrType 3075 InetAddressType, 3076 bgpM2PathAttrNextHop 3077 InetAddress, 3078 bgpM2PathAttrMedPresent 3079 TruthValue, 3080 bgpM2PathAttrMed 3081 Unsigned32, 3082 bgpM2PathAttrLocalPrefPresent 3083 TruthValue, 3084 bgpM2PathAttrLocalPref 3085 Unsigned32, 3087 bgpM2PathAttrAtomicAggregate 3088 INTEGER, 3089 bgpM2PathAttrAggregatorAS 3090 InetAutonomousSystemNumber, 3091 bgpM2PathAttrAggregatorAddr 3092 BgpM2Identifier, 3093 bgpM2AsPathCalcLength 3094 Unsigned32, 3095 bgpM2AsPathString 3096 DisplayString, 3097 bgpM2AsPathIndex 3098 Unsigned32 3099 } 3101 bgpM2PathAttrOrigin OBJECT-TYPE 3102 SYNTAX INTEGER { 3103 igp(1),-- networks are interior 3104 egp(2),-- networks learned via the EGP protocol 3105 incomplete(3) -- undetermined 3106 } 3107 MAX-ACCESS read-only 3108 STATUS current 3109 DESCRIPTION 3110 "The ultimate origin of the path information." 3111 ::= { bgpM2PathAttrEntry 1 } 3113 bgpM2PathAttrNextHopAddrType OBJECT-TYPE 3114 SYNTAX InetAddressType 3115 MAX-ACCESS read-only 3116 STATUS current 3117 DESCRIPTION 3118 "The address family of the address for 3119 the border router that should be used 3120 to access the destination network." 3121 ::= { bgpM2PathAttrEntry 2 } 3123 -- JMH - this is wrong for RFC2545! 3124 -- We need to extend InetAddressType so we have a valid InetAddress 3125 -- for this. 3126 bgpM2PathAttrNextHop OBJECT-TYPE 3127 SYNTAX InetAddress (SIZE(4..20)) 3128 MAX-ACCESS read-only 3129 STATUS current 3130 DESCRIPTION 3131 "The address of the border router that 3132 should be used to access the destination 3133 network. This address is the nexthop 3134 address received in the UPDATE packet. 3135 The address family of this object will be the 3136 same as that of the prefix in this row." 3137 ::= { bgpM2PathAttrEntry 3 } 3139 bgpM2PathAttrMedPresent OBJECT-TYPE 3140 SYNTAX TruthValue 3141 MAX-ACCESS read-only 3142 STATUS current 3143 DESCRIPTION 3144 "Whether or not the MED value is present. 3145 If it is not present, the bgpM2PathAttrMed 3146 object has no useful value and should be set to 0." 3147 ::= { bgpM2PathAttrEntry 4 } 3149 bgpM2PathAttrMed OBJECT-TYPE 3150 SYNTAX Unsigned32 3151 MAX-ACCESS read-only 3152 STATUS current 3153 DESCRIPTION 3154 "This metric is used to discriminate 3155 between multiple exit points to an 3156 adjacent autonomous system." 3157 ::= { bgpM2PathAttrEntry 5 } 3159 bgpM2PathAttrLocalPrefPresent OBJECT-TYPE 3160 SYNTAX TruthValue 3161 MAX-ACCESS read-only 3162 STATUS current 3163 DESCRIPTION 3164 "Whether or not the LocalPref value is present. 3165 If it is not present, the bgpM2PathAttrLocalPref 3166 object has no useful value and should be set to 0." 3167 ::= { bgpM2PathAttrEntry 6 } 3169 bgpM2PathAttrLocalPref OBJECT-TYPE 3170 SYNTAX Unsigned32 3171 MAX-ACCESS read-only 3172 STATUS current 3173 DESCRIPTION 3174 "The originating BGP4 speakers degree of 3175 preference for an advertised route." 3177 ::= { bgpM2PathAttrEntry 7 } 3179 -- JMH 3180 -- See comment in v1 draft about this. 3182 bgpM2PathAttrAtomicAggregate OBJECT-TYPE 3183 SYNTAX INTEGER { 3184 lessSpecificRouteNotSelected(1), 3185 lessSpecificRouteSelected(2) 3186 } 3187 MAX-ACCESS read-only 3188 STATUS current 3189 DESCRIPTION 3190 "Whether or not a system has selected 3191 a less specific route without 3192 selecting a more specific route." 3193 ::= { bgpM2PathAttrEntry 8 } 3195 bgpM2PathAttrAggregatorAS OBJECT-TYPE 3196 SYNTAX InetAutonomousSystemNumber 3197 MAX-ACCESS read-only 3198 STATUS current 3199 DESCRIPTION 3200 "The AS number of the last BGP4 speaker that 3201 performed route aggregation. A value of 3202 zero (0) indicates the absence of this 3203 attribute. 3205 Note propagation of AS of zero is illegal in 3206 the Internet." 3207 ::= { bgpM2PathAttrEntry 9 } 3209 bgpM2PathAttrAggregatorAddr OBJECT-TYPE 3210 SYNTAX BgpM2Identifier 3211 MAX-ACCESS read-only 3212 STATUS current 3213 DESCRIPTION 3214 "The IP address of the last BGP4 speaker 3215 that performed route aggregation. A 3216 value of 0.0.0.0 indicates the absence 3217 of this attribute." 3218 ::= { bgpM2PathAttrEntry 10 } 3220 bgpM2AsPathCalcLength OBJECT-TYPE 3221 SYNTAX Unsigned32 3222 MAX-ACCESS read-only 3223 STATUS current 3224 DESCRIPTION 3225 "This value represents the calculated length of the 3226 AS Path according to the rules of the BGP specification. 3227 This value is used in route selection." 3228 REFERENCE 3229 "draft-ietf-idr-bgp4-17.txt, Sec. 9.1.2.2.a" 3230 ::= { bgpM2PathAttrEntry 11 } 3232 bgpM2AsPathString OBJECT-TYPE 3233 SYNTAX DisplayString 3234 MAX-ACCESS read-only 3235 STATUS current 3236 DESCRIPTION 3237 "This is a string depicting the autonomous system 3238 path to this network which was received from the 3239 peer which advertised it. The format of the string 3240 is implementation-dependent, and should be designed 3241 for operator readability." 3242 ::= { bgpM2PathAttrEntry 12 } 3244 bgpM2AsPathIndex OBJECT-TYPE 3245 SYNTAX Unsigned32 3246 MAX-ACCESS read-only 3247 STATUS current 3248 DESCRIPTION 3249 "This value is a unique index for the decomposed AS Path 3250 in the bgpM2AsPathTable. It is assigned by the 3251 agent at the point of creation of the bgpM2AsPathTable 3252 row entry. While its value is guaranteed to be unique 3253 at any time, it is otherwise opaque to the management 3254 application with respect to its value or the contiguity 3255 of bgpM2AsPathIndex row instance values across rows 3256 of the bgpM2AsPathTable." 3257 ::= { bgpM2PathAttrEntry 13 } 3259 -- 3260 -- As-4 byte AS_PATH 3261 -- 3263 bgpM2AsPath4byteTable OBJECT-TYPE 3264 SYNTAX SEQUENCE OF BgpM2AsPath4byteEntry 3265 MAX-ACCESS not-accessible 3266 STATUS current 3267 DESCRIPTION 3268 "This table is present for BGP speakers that support 3269 the AS 4byte specification and are functioning as 3270 a router between 2-byte and 4-byte AS space." 3271 REFERENCE 3272 "draft-ietf-idr-as4bytes-04.txt - BGP support for 3273 four-octet AS number space" 3274 ::= { bgpM2Rib 5 } 3276 bgpM2AsPath4byteEntry OBJECT-TYPE 3277 SYNTAX BgpM2AsPath4byteEntry 3278 MAX-ACCESS not-accessible 3279 STATUS current 3280 DESCRIPTION 3281 "Each row contains the information for the AS 4-byte 3282 extension's NEW_AS_PATH and NEW_AGGREGATOR attributes." 3283 AUGMENTS { 3284 bgpM2PathAttrEntry 3285 } 3286 ::= { bgpM2AsPath4byteTable 1 } 3288 BgpM2AsPath4byteEntry ::= SEQUENCE { 3289 bgpM2AsPath4bytePathPresent 3290 TruthValue, 3291 bgpM2AsPath4byteAggregatorAS 3292 InetAutonomousSystemNumber, 3293 bgpM2AsPath4byteCalcLength 3294 Unsigned32, 3295 bgpM2AsPath4byteString 3296 DisplayString, 3297 bgpM2AsPath4byteIndex 3298 Unsigned32 3299 } 3301 bgpM2AsPath4bytePathPresent OBJECT-TYPE 3302 SYNTAX TruthValue 3303 MAX-ACCESS read-only 3304 STATUS current 3305 DESCRIPTION 3306 "This value may only be true if this BGP Speaker 3307 is functioning as a router between ASs that 3308 are in 2-byte and 4-byte AS space. If this 3309 value is true, then the NEW_AS_PATH attributes 3310 are present and the 4-byte versions of the 3311 appropriate path attributes are in this row. 3313 If this value is false, then the following values 3314 will be present in the row: 3316 bgpM2PathAttrAggregatorAS - zero (0). 3317 bgpM2AsPathCalcLength - zero (0). 3318 bgpM2AsPathString - zero (0) length string. 3319 bgpM2AsPathIndex - zero (0)." 3320 ::= { bgpM2AsPath4byteEntry 1 } 3322 bgpM2AsPath4byteAggregatorAS OBJECT-TYPE 3323 SYNTAX InetAutonomousSystemNumber 3324 MAX-ACCESS read-only 3325 STATUS current 3326 DESCRIPTION 3327 "The NEW_AGGREGATOR AS number of the last BGP4 speaker 3328 that performed route aggregation. A value of 3329 zero (0) indicates the absence of this 3330 attribute. 3332 Note propagation of AS of zero is illegal in 3333 the Internet." 3334 ::= { bgpM2AsPath4byteEntry 2 } 3336 bgpM2AsPath4byteCalcLength OBJECT-TYPE 3337 SYNTAX Unsigned32 3338 MAX-ACCESS read-only 3339 STATUS current 3340 DESCRIPTION 3341 "This value represents the calculated length of the 3342 NEW_AS_PATH according to the rules of the BGP specification. 3343 This value is used in route selection." 3344 REFERENCE 3345 "draft-ietf-idr-bgp4-17.txt, Sec. 9.1.2.2.a" 3346 ::= { bgpM2AsPath4byteEntry 3 } 3348 bgpM2AsPath4byteString OBJECT-TYPE 3349 SYNTAX DisplayString 3350 MAX-ACCESS read-only 3351 STATUS current 3352 DESCRIPTION 3353 "This is a string depicting the autonomous system 3354 path to this network which was received from the 3355 peer which advertised it. The format of the string 3356 is implementation-dependent, and should be designed 3357 for operator readability." 3358 ::= { bgpM2AsPath4byteEntry 4 } 3360 bgpM2AsPath4byteIndex OBJECT-TYPE 3361 SYNTAX Unsigned32 3362 MAX-ACCESS read-only 3363 STATUS current 3364 DESCRIPTION 3365 "This value is a unique index for the decomposed AS Path 3366 in the bgpM2AsPathTable. It is assigned by the 3367 agent at the point of creation of the bgpM2AsPathTable 3368 row entry. While its value is guaranteed to be unique 3369 at any time, it is otherwise opaque to the management 3370 application with respect to its value or the contiguity 3371 of bgpM2AsPathIndex row instance values across rows 3372 of the bgpM2AsPathTable. " 3373 ::= { bgpM2AsPath4byteEntry 5 } 3375 -- BGP 4 Path attribute AS Path Table. There is one row in 3376 -- this table for each AS which is advertised for a given 3377 -- route as provided from a peer. 3379 -- JMH 3380 -- We need one of these for the NewAsPath for the 4byte draft 3382 bgpM2AsPathTable OBJECT-TYPE 3383 SYNTAX SEQUENCE OF BgpM2AsPathEntry 3384 MAX-ACCESS not-accessible 3385 STATUS current 3386 DESCRIPTION 3387 "The BGP-4 Path Attribute AS Path Table 3388 contains the per network path (NLRI) 3389 AS PATH data received from the 3390 advertising BGP peer." 3391 ::= { bgpM2Rib 6 } 3393 bgpM2AsPathTableEntry OBJECT-TYPE 3394 SYNTAX BgpM2AsPathEntry 3395 MAX-ACCESS not-accessible 3396 STATUS current 3397 DESCRIPTION 3398 "Information about an AS path provided with a path to 3399 a network." 3400 INDEX { 3401 bgpM2PathAttrIndex, 3402 bgpM2AsPathSegmentIndex, 3403 bgpM2AsPathElementIndex, 3404 bgpM2AsPathElementValue 3405 } 3406 ::= { bgpM2AsPathTable 1 } 3408 BgpM2AsPathEntry ::= SEQUENCE { 3409 bgpM2AsPathSegmentIndex 3410 Unsigned32, 3411 bgpM2AsPathElementIndex 3412 Unsigned32, 3413 bgpM2AsPathType 3414 INTEGER, 3415 bgpM2AsPathElementValue 3416 InetAutonomousSystemNumber 3417 } 3419 bgpM2AsPathSegmentIndex OBJECT-TYPE 3420 SYNTAX Unsigned32 3421 MAX-ACCESS read-only 3422 STATUS current 3423 DESCRIPTION 3424 "A per-AS path segment index. This will index a set of 3425 autonomous systems in an AS path which are part 3426 of the same sequence or set (as determined by 3427 the row value of bgpM2AsPathType, which 3428 should be the same value for each bgpM2AsPathTable 3429 entry indexed by the same (bgpM2PathAttrIndex, 3430 bgpM2AsPathIndex) pair)." 3431 ::= { bgpM2AsPathTableEntry 1 } 3433 bgpM2AsPathElementIndex OBJECT-TYPE 3434 SYNTAX Unsigned32 3435 MAX-ACCESS read-only 3436 STATUS current 3437 DESCRIPTION 3438 "A per-AS element index. This will index a particular 3439 AS within a sequence or set of autonomous systems in 3440 an AS path." 3441 ::= { bgpM2AsPathTableEntry 2 } 3443 bgpM2AsPathType OBJECT-TYPE 3444 SYNTAX INTEGER { 3445 asSet(1), 3446 asSequence(2), 3447 confedSequence(3), 3448 confedSet(4) 3449 } 3450 MAX-ACCESS read-only 3451 STATUS current 3452 DESCRIPTION 3453 "The type of sequence in which this asPath 3454 was advertised as an attribute. Note that 3455 all asPath row instances for a given (bgpM2PathAttrIndex, 3456 bgpM2AsPathIndex) index pair will have their 3457 bgpM2AsPathType set to the same value. 3458 The values for bgpM2AsPathType are 3459 interpreted as defined in the base BGP document 3460 and the BGP AS Confederations document." 3461 REFERENCE 3462 "draft-ietf-idr-bgp4-16 3463 RFC 3065 - BGP AS Confederations" 3464 ::= { bgpM2AsPathTableEntry 3 } 3466 bgpM2AsPathElementValue OBJECT-TYPE 3467 SYNTAX InetAutonomousSystemNumber 3468 MAX-ACCESS read-only 3469 STATUS current 3470 DESCRIPTION 3471 "An AS value for an AS the related NLRI traversed 3472 in the propagation of its advertisement. This 3473 value is to be interpreted in the context of the 3474 sequence implied by bgpM2AsPathIndex and 3475 bgpM2AsPathType (and, in sequence of the 3476 other table rows with the same value of 3477 bgpM2PathAttrIndex and bgpM2AsPathIndex)." 3478 ::= { bgpM2AsPathTableEntry 4 } 3480 -- BGP 4 Path unknown attribute. There is one row in 3481 -- this table for each attribute not known by this BGP 3482 -- implementation (or agent instrumentation), but provided 3483 -- from a peer. 3485 bgpM2PathAttrUnknownTable OBJECT-TYPE 3486 SYNTAX SEQUENCE OF BgpM2PathAttrUnknownEntry 3487 MAX-ACCESS not-accessible 3488 STATUS current 3489 DESCRIPTION 3490 "The BGP-4 Path Attribute Unknown Table 3491 contains the per network path (NLRI) 3492 data on the path attributes advertised 3493 with a route but not known to the local BGP implementation 3494 or not otherwise capable of being returned from this agent. 3496 The absence of row data for a given index value for 3497 bgpM2PathAttrIndex indicates a lack of such unknown 3498 attribute information for the indicated network path 3499 (as indexed by that bgpM2PathAttrIndex value in the 3500 bgpM2PathAttrTable)." 3501 ::= { bgpM2Rib 7 } 3503 bgpM2PathAttrUnknownEntry OBJECT-TYPE 3504 SYNTAX BgpM2PathAttrUnknownEntry 3505 MAX-ACCESS not-accessible 3506 STATUS current 3507 DESCRIPTION 3508 "Information about an unknown attribute 3509 provided with a path to a network." 3510 INDEX { 3511 bgpM2PathAttrIndex, 3512 bgpM2PathAttrUnknownIndex 3513 } 3514 ::= { bgpM2PathAttrUnknownTable 1 } 3516 BgpM2PathAttrUnknownEntry ::= SEQUENCE { 3517 bgpM2PathAttrUnknownIndex 3518 Unsigned32, 3519 bgpM2PathAttrUnknownType 3520 Unsigned32, 3521 bgpM2PathAttrUnknownValue 3522 OCTET STRING 3523 } 3525 bgpM2PathAttrUnknownIndex OBJECT-TYPE 3526 SYNTAX Unsigned32 3527 MAX-ACCESS read-only 3528 STATUS current 3529 DESCRIPTION 3530 "An integer index for a row in this table." 3531 ::= { bgpM2PathAttrUnknownEntry 1 } 3533 bgpM2PathAttrUnknownType OBJECT-TYPE 3534 SYNTAX Unsigned32 3535 MAX-ACCESS read-only 3536 STATUS current 3537 DESCRIPTION 3538 "The attribute type advertised with this unknown 3539 attribute by the peer." 3540 ::= { bgpM2PathAttrUnknownEntry 2 } 3542 -- Maximum size of the following is derived as 3543 -- 4096 max message size 3544 -- - 16 BGP message marker bytes 3545 -- - 2 BGP message size 3546 -- - 1 BGP message type (UPDATE with unknown attr) 3547 -- - 2 UPDATE routes length (even assuming no routes) 3548 -- - 2 UPDATE path attributes length 3549 -- - 1 path attribute flag octet 3550 -- - 2 unknown path attr type (in bgpM2PathAttrUnknownType) 3551 -- --------- 3552 -- 4070 bytes maximum per-message attribute value data 3554 bgpM2PathAttrUnknownValue OBJECT-TYPE 3555 SYNTAX OCTET STRING (SIZE(0..4070)) 3556 MAX-ACCESS read-only 3557 STATUS current 3558 DESCRIPTION 3559 "Value of path attribute not understood 3560 by the base BGP-4 document. 3562 Octets beyond the maximum size, if any, 3563 are not recorded by this row object. " 3564 ::= { bgpM2PathAttrUnknownEntry 3 } 3566 -- 3567 -- Path Attribute Extensions 3568 -- 3570 bgpM2PathAttrExtensions 3571 OBJECT IDENTIFIER ::= { bgpM2Rib 8 } 3573 bgpM2PathAttrNonCapExts 3574 OBJECT IDENTIFIER ::= { bgpM2PathAttrExtensions 1 } 3576 bgpM2PathAttrCapExts 3577 OBJECT IDENTIFIER ::= { bgpM2PathAttrExtensions 2 } 3579 -- 3580 -- Path Attribute Route Reflection Extensions 3581 -- 3583 -- 3584 -- Originator ID Table 3585 -- 3587 bgpM2PathAttrRouteReflectionExts 3588 OBJECT IDENTIFIER ::= { bgpM2PathAttrNonCapExts 2796 } 3590 bgpM2PathAttrOriginatorIdTable OBJECT-TYPE 3591 SYNTAX SEQUENCE OF BgpM2PathAttrOriginatorIdEntry 3592 MAX-ACCESS not-accessible 3593 STATUS current 3594 DESCRIPTION 3595 "Per prefix data pertinent to advertisement of a 3596 network prefix through an originator." 3597 REFERENCE 3598 "RFC 2796 - BGP Route Reflection" 3599 ::= { bgpM2PathAttrRouteReflectionExts 1 } 3601 bgpM2PathAttrOriginatorIdEntry OBJECT-TYPE 3602 SYNTAX BgpM2PathAttrOriginatorIdEntry 3603 MAX-ACCESS not-accessible 3604 STATUS current 3605 DESCRIPTION 3606 "Each entry contains data pertinent to a network 3607 prefix as received through its originating BGP 3608 route reflector." 3609 REFERENCE 3610 "RFC 2796 - BGP Route Reflection" 3611 INDEX { 3612 bgpM2PathAttrIndex 3613 } 3614 ::= { bgpM2PathAttrOriginatorIdTable 1 } 3616 BgpM2PathAttrOriginatorIdEntry ::= SEQUENCE { 3617 bgpM2PathAttrOriginatorId 3618 BgpM2Identifier 3619 } 3621 bgpM2PathAttrOriginatorId OBJECT-TYPE 3622 SYNTAX BgpM2Identifier 3623 MAX-ACCESS read-only 3624 STATUS current 3625 DESCRIPTION 3626 "The Originator-ID identifying the router that initially 3627 advertised this destination to a Route Reflector. A 3628 value of 0.0.0.0 indicates the absence of this attribute." 3629 REFERENCE 3630 "This attribute is defined in [RFC2796]." 3631 ::= { bgpM2PathAttrOriginatorIdEntry 1 } 3633 -- 3634 -- Cluster table 3635 -- 3637 bgpM2PathAttrClusterTable OBJECT-TYPE 3638 SYNTAX SEQUENCE OF BgpM2PathAttrClusterEntry 3639 MAX-ACCESS not-accessible 3640 STATUS current 3641 DESCRIPTION 3642 "The BGP-4 Path Attribute Cluster Table 3643 contains the per network path (NLRI) 3644 data on the reflection path which a 3645 route has traversed. The absence of row 3646 data for a given index value for bgpM2PathAttrIndex 3647 indicates a lack of this attribute information 3648 for the indicated network path (as indexed by 3649 that bgpM2PathAttrIndex value in the bgpM2PathAttrTable)." 3650 ::= { bgpM2PathAttrRouteReflectionExts 2 } 3652 bgpM2PathAttrClusterEntry OBJECT-TYPE 3653 SYNTAX BgpM2PathAttrClusterEntry 3654 MAX-ACCESS not-accessible 3655 STATUS current 3656 DESCRIPTION 3657 "Information about a cluster traversal 3658 provided with a path to a network." 3659 INDEX { 3660 bgpM2PathAttrIndex, 3661 bgpM2PathAttrClusterIndex 3662 } 3663 ::= { bgpM2PathAttrClusterTable 1 } 3665 BgpM2PathAttrClusterEntry ::= SEQUENCE { 3666 bgpM2PathAttrClusterIndex 3667 Unsigned32, 3669 bgpM2PathAttrClusterValue 3670 Unsigned32 3671 } 3673 bgpM2PathAttrClusterIndex OBJECT-TYPE 3674 SYNTAX Unsigned32 3675 MAX-ACCESS read-only 3676 STATUS current 3677 DESCRIPTION 3678 "An integral index for a row in this table." 3679 ::= { bgpM2PathAttrClusterEntry 1 } 3681 bgpM2PathAttrClusterValue OBJECT-TYPE 3682 SYNTAX BgpM2Identifier 3683 MAX-ACCESS read-only 3684 STATUS current 3685 DESCRIPTION 3686 "A four octet long value representing a part of the 3687 reflection path that the route has passed. Each such four 3688 octet long value represents the ID of a cluster that 3689 the route has traversed. The sequence of this path as 3690 received in the route advertisement will be preserved in 3691 the sequence of bgpM2PathAttrClusterTable rows (and the 3692 bgpM2PathAttrClusterValues in each row) as returned for 3693 a given bgpM2PathAttrIndex value, and the monotonically 3694 increasing sequence of bgpM2PathAttrClusterIndex values 3695 for that bgpM2PathAttrIndex." 3696 REFERENCE 3697 "This attribute is defined in [RFC2796]." 3698 ::= { bgpM2PathAttrClusterEntry 2 } 3700 -- 3701 -- BGP Communities 3702 -- 3704 bgpM2PathAttrCommunityExts 3705 OBJECT IDENTIFIER ::= { bgpM2PathAttrNonCapExts 1997 } 3707 bgpM2PathAttrCommTable OBJECT-TYPE 3708 SYNTAX SEQUENCE OF BgpM2PathAttrCommEntry 3709 MAX-ACCESS not-accessible 3710 STATUS current 3711 DESCRIPTION 3712 "The BGP-4 Path Attribute Community Table 3713 contains the per network path (NLRI) 3714 data on the community membership advertised 3715 with a route. The absence of row 3716 data for a given index value for bgpM2PathAttrIndex 3717 indicates a lack of this attribute information 3718 for the indicated network path (as indexed by 3719 that bgpM2PathAttrIndex value in the bgpM2PathAttrTable)." 3720 ::= { bgpM2PathAttrCommunityExts 1 } 3722 bgpM2PathAttrCommEntry OBJECT-TYPE 3723 SYNTAX BgpM2PathAttrCommEntry 3724 MAX-ACCESS not-accessible 3725 STATUS current 3726 DESCRIPTION 3727 "Information about a community association 3728 provided with a path to a network." 3729 INDEX { 3730 bgpM2PathAttrIndex, 3731 bgpM2PathAttrCommIndex 3732 } 3733 ::= { bgpM2PathAttrCommTable 1 } 3735 BgpM2PathAttrCommEntry ::= SEQUENCE { 3736 bgpM2PathAttrCommIndex 3737 Unsigned32, 3738 bgpM2PathAttrCommValue 3739 BgpM2Community 3740 } 3742 bgpM2PathAttrCommIndex OBJECT-TYPE 3743 SYNTAX Unsigned32 3744 MAX-ACCESS read-only 3745 STATUS current 3746 DESCRIPTION 3747 "An integer index for a row in this table." 3748 ::= { bgpM2PathAttrCommEntry 1 } 3750 bgpM2PathAttrCommValue OBJECT-TYPE 3751 SYNTAX BgpM2Community 3752 MAX-ACCESS read-only 3753 STATUS current 3754 DESCRIPTION 3755 "A value representing a community. There are certain 3756 4-octet long values which could be returned in this 3757 columnar row data that carry additional semantics." 3758 REFERENCE 3759 "RFC 1997 - BGP Communities Attribute" 3760 ::= { bgpM2PathAttrCommEntry 2 } 3762 -- 3763 -- BGP Extended Communities 3764 -- 3766 bgpM2PathAttrExtCommTable OBJECT-TYPE 3767 SYNTAX SEQUENCE OF BgpM2PathAttrExtCommEntry 3768 MAX-ACCESS not-accessible 3769 STATUS current 3770 DESCRIPTION 3771 "The BGP-4 Path Attribute Community Table 3772 contains the per network path (NLRI) 3773 data on the extended community membership advertised 3774 with a route. The absence of row 3775 data for a given index value for bgpM2PathAttrIndex 3776 indicates a lack of this attribute information 3777 for the indicated network path (as indexed by 3778 that bgpM2PathAttrIndex value in the bgpM2PathAttrTable). 3780 XXX JMH - can not assign the OID until an RFC is published." 3781 ::= { bgpM2PathAttrNonCapExts XXX } 3783 bgpM2PathAttrExtCommEntry OBJECT-TYPE 3784 SYNTAX BgpM2PathAttrExtCommEntry 3785 MAX-ACCESS not-accessible 3786 STATUS current 3787 DESCRIPTION 3788 "Information about an extended community association 3789 provided with a path to a network." 3790 INDEX { 3791 bgpM2PathAttrIndex, 3792 bgpM2PathAttrExtCommIndex 3793 } 3794 ::= { bgpM2PathAttrExtCommTable 1 } 3796 BgpM2PathAttrExtCommEntry ::= SEQUENCE { 3797 bgpM2PathAttrExtCommIndex 3798 Unsigned32, 3799 bgpM2PathAttrExtCommValue 3800 BgpM2ExtendedCommunity 3801 } 3802 bgpM2PathAttrExtCommIndex OBJECT-TYPE 3803 SYNTAX Unsigned32 3804 MAX-ACCESS read-only 3805 STATUS current 3806 DESCRIPTION 3807 "An integral index for a row in this table." 3808 ::= { bgpM2PathAttrExtCommEntry 1 } 3810 bgpM2PathAttrExtCommValue OBJECT-TYPE 3811 SYNTAX BgpM2ExtendedCommunity 3812 MAX-ACCESS read-only 3813 STATUS current 3814 DESCRIPTION 3815 "A value representing an extended community which was 3816 received with the route implied by the bgpM2PathAttr 3817 Index value of this row data. There are certain 3818 8-octet long values which could be returned in this 3819 columnar row data that carry additional semantics." 3820 REFERENCE 3821 "BGP-EXTCOMM - BGP Extended Communities Attribute" 3822 ::= { bgpM2PathAttrExtCommEntry 2 } 3824 -- 3825 -- Conformance Information 3826 -- 3828 bgpM2Conformance 3829 OBJECT IDENTIFIER ::= { bgp 4 } 3831 bgpM2MIBCompliances OBJECT IDENTIFIER ::= 3832 { bgpM2Conformance 1 } 3834 bgpM2MIBGroups OBJECT IDENTIFIER ::= 3835 { bgpM2Conformance 2 } 3837 bgpM2MIBCompliance MODULE-COMPLIANCE 3838 STATUS current 3839 DESCRIPTION 3840 "The compliance statement for entities which 3841 implement the BGP4 mib." 3842 MODULE -- this module 3843 MANDATORY-GROUPS { 3844 bgpM2TimersGroup, 3845 bgpM2CountersGroup, 3846 bgpM2AsPathGroup, 3847 bgpM2As4byteGroup, 3848 bgpM2BaseGroup, 3849 bgpM2ErrorsGroup, 3850 bgpM2PeerGroup, 3851 bgpM2PathAttributesGroup 3852 } 3853 GROUP bgpM2MIBNotificationsGroup 3854 DESCRIPTION 3855 "The notifications group is completely optional, 3856 but highly recommended." 3857 GROUP bgpM2AuthenticationGroup 3858 DESCRIPTION 3859 "The authentication group is 3860 mandatory only for those implementations which 3861 support sending and receiving authentication 3862 information with peers in the BGP Authentication 3863 Field." 3864 GROUP bgpM2CommunitiesGroup 3865 DESCRIPTION 3866 "The communities group is mandatory only for those 3867 which support the BGP community attribute." 3868 GROUP bgpM2ExtCommunitiesGroup 3869 DESCRIPTION 3870 "The communities group is mandatory only for those 3871 which support the BGP extended community attribute." 3872 GROUP bgpM2RouteReflectionGroup 3873 DESCRIPTION 3874 "The communities group is mandatory only for those 3875 which support the BGP route reflection relationships." 3876 GROUP bgpM2AsConfederationGroup 3877 DESCRIPTION 3878 "The communities group is mandatory only for those 3879 which support the BGP confederation membership." 3880 GROUP bgpM2TimersGroup 3881 DESCRIPTION 3882 "This group is mandatory for all agent implementations." 3883 GROUP bgpM2CountersGroup 3884 DESCRIPTION 3885 "This group is mandatory for all agent implementations." 3886 GROUP bgpM2CapabilitiesGroup 3887 DESCRIPTION 3888 "This group is mandatory for all agent implementations." 3889 GROUP bgpM2AsPathGroup 3890 DESCRIPTION 3891 "This group is mandatory for all agent implementations." 3893 GROUP bgpM2As4byteGroup 3894 DESCRIPTION 3895 "This group is mandatory for all agent implementations." 3896 GROUP bgpM2BaseGroup 3897 DESCRIPTION 3898 "This group is mandatory for all agent implementations." 3899 GROUP bgpM2ErrorsGroup 3900 DESCRIPTION 3901 "This group is mandatory for all agent implementations." 3902 GROUP bgpM2PeerGroup 3903 DESCRIPTION 3904 "This group is mandatory for all agent implementations." 3905 GROUP bgpM2PathAttributesGroup 3906 DESCRIPTION 3907 "This group is mandatory for all agent implementations." 3908 GROUP bgpM2PeerConfigurationGroup 3909 DESCRIPTION 3910 "This group is optional for implementations that wish to 3911 support configuration via SNMP." 3912 GROUP bgpM2PeerAuthConfigurationGroup 3913 DESCRIPTION 3914 "This group is optional for implementations that wish to 3915 support configuration of BGP authentication via SNMP. 3916 Implementation of this feature requires support of the 3917 bgpM2PeerConfigurationGroup." 3918 GROUP bgpM2PeerRouteReflectorCfgGroup 3919 DESCRIPTION 3920 "This group is optional for implementations that wish to 3921 support configuration of route reflection via SNMP. 3922 Implementation of this feature requires support of the 3923 bgpM2PeerConfigurationGroup." 3924 GROUP bgpM2PeerAsConfederationCfgGroup 3925 DESCRIPTION 3926 "This group is optional for implementations that wish to 3927 support configuration of BGP AS Confederations via SNMP. 3928 Implementation of this feature requires support of the 3929 bgpM2PeerConfigurationGroup." 3930 ::= { bgpM2MIBCompliances 1 } 3932 bgpM2AuthenticationGroup OBJECT-GROUP 3933 OBJECTS { 3934 bgpM2SupportedAuthCode, 3935 bgpM2SupportedAuthValue, 3936 bgpM2PeerAuthSent, 3937 bgpM2PeerAuthSentCode, 3938 bgpM2PeerAuthSentValue, 3939 bgpM2PeerAuthRcvd, 3940 bgpM2PeerAuthRcvdCode, 3941 bgpM2PeerAuthRcvdValue 3942 } 3943 STATUS current 3944 DESCRIPTION 3945 "Objects associated with BGP authentication." 3946 ::= { bgpM2MIBGroups 1 } 3948 bgpM2CommunitiesGroup OBJECT-GROUP 3949 OBJECTS { 3950 bgpM2PathAttrCommIndex, 3951 bgpM2PathAttrCommValue 3952 } 3953 STATUS current 3954 DESCRIPTION 3955 "Objects associated with BGP communities." 3956 ::= { bgpM2MIBGroups 2 } 3958 bgpM2ExtCommunitiesGroup OBJECT-GROUP 3959 OBJECTS { 3960 bgpM2PathAttrExtCommIndex, 3961 bgpM2PathAttrExtCommValue 3962 } 3963 STATUS current 3964 DESCRIPTION 3965 "Objects associated with BGP extended communities." 3966 ::= { bgpM2MIBGroups 3 } 3968 bgpM2RouteReflectionGroup OBJECT-GROUP 3969 OBJECTS { 3970 bgpM2RouteReflector, 3971 bgpM2ClusterId, 3972 bgpM2PeerReflectorClient, 3973 bgpM2PathAttrOriginatorId, 3974 bgpM2PathAttrClusterIndex, 3975 bgpM2PathAttrClusterValue 3976 } 3977 STATUS current 3978 DESCRIPTION 3979 "Objects associated with BGP route reflection." 3980 ::= { bgpM2MIBGroups 4 } 3982 bgpM2AsConfederationGroup OBJECT-GROUP 3983 OBJECTS { 3984 bgpM2ConfederationRouter, 3985 bgpM2ConfederationId, 3986 bgpM2PeerConfedMember 3987 } 3988 STATUS current 3989 DESCRIPTION 3990 "Objects associated with BGP confederation membership." 3991 ::= { bgpM2MIBGroups 5 } 3993 bgpM2TimersGroup OBJECT-GROUP 3994 OBJECTS { 3995 bgpM2PeerFsmEstablishedTime, 3996 bgpM2PeerInUpdatesElapsedTime, 3997 bgpM2PeerConnectRetryInterval, 3998 bgpM2PeerHoldTimeConfigured, 3999 bgpM2PeerKeepAliveConfigured, 4000 bgpM2PeerMinASOrigInterval, 4001 bgpM2PeerMinRouteAdverInterval, 4002 bgpM2PeerHoldTime, 4003 bgpM2PeerKeepAlive 4004 } 4005 STATUS current 4006 DESCRIPTION 4007 "Objects associated with BGP peering timers." 4008 ::= { bgpM2MIBGroups 6 } 4010 bgpM2CountersGroup OBJECT-GROUP 4011 OBJECTS { 4012 bgpM2PeerInUpdates, 4013 bgpM2PeerOutUpdates, 4014 bgpM2PeerInTotalMessages, 4015 bgpM2PeerOutTotalMessages, 4016 bgpM2PeerFsmEstablishedTrans, 4017 bgpM2PrefixCountersAfi, 4018 bgpM2PrefixCountersSafi, 4019 bgpM2PrefixInPrefixes, 4020 bgpM2PrefixInPrefixesAccepted, 4021 bgpM2PrefixInPrefixesRejected, 4022 bgpM2PrefixOutPrefixes 4023 } 4024 STATUS current 4025 DESCRIPTION 4026 "Objects to count discrete events and exchanges on BGP 4027 sessions." 4028 ::= { bgpM2MIBGroups 7 } 4030 bgpM2CapabilitiesGroup OBJECT-GROUP 4031 OBJECTS { 4032 bgpM2CapabilitySupportAvailable, 4033 bgpM2SupportedCapabilityCode, 4034 bgpM2SupportedCapability, 4035 bgpM2PeerCapAnnouncedCode, 4036 bgpM2PeerCapAnnouncedIndex, 4037 bgpM2PeerCapAnnouncedValue, 4038 bgpM2PeerCapReceivedCode, 4039 bgpM2PeerCapReceivedIndex, 4040 bgpM2PeerCapReceivedValue 4041 } 4042 STATUS current 4043 DESCRIPTION 4044 "Objects to report capabilities as received on BGP 4045 sessions." 4046 ::= { bgpM2MIBGroups 8 } 4048 bgpM2AsPathGroup OBJECT-GROUP 4049 OBJECTS { 4050 bgpM2AsPathSegmentIndex, 4051 bgpM2AsPathElementIndex, 4052 bgpM2AsPathType, 4053 bgpM2AsPathElementValue 4054 } 4055 STATUS current 4056 DESCRIPTION 4057 "Objects to report AS paths received on BGP NLRIs." 4058 ::= { bgpM2MIBGroups 9 } 4060 bgpM2As4byteGroup OBJECT-GROUP 4061 OBJECTS { 4062 bgpM2AsSize, 4063 bgpM2AsPath4bytePathPresent, 4064 bgpM2AsPath4byteAggregatorAS, 4065 bgpM2AsPath4byteCalcLength, 4066 bgpM2AsPath4byteString, 4067 bgpM2AsPath4byteIndex 4068 } 4069 STATUS current 4070 DESCRIPTION 4071 "AS Size objects." 4072 ::= { bgpM2MIBGroups 10 } 4074 bgpM2BaseGroup OBJECT-GROUP 4075 OBJECTS { 4076 bgpM2LocalAs, 4077 bgpM2LocalIdentifier, 4078 bgpM2VersionIndex, 4079 bgpM2VersionSupported 4080 } 4081 STATUS current 4082 DESCRIPTION 4083 "Basic objects in local BGP implementation." 4084 ::= { bgpM2MIBGroups 11 } 4086 bgpM2ErrorsGroup OBJECT-GROUP 4087 OBJECTS { 4088 bgpM2PeerLastErrorReceived, 4089 bgpM2PeerLastErrorReceivedData, 4090 bgpM2PeerLastErrorReceivedTime, 4091 bgpM2PeerLastErrorReceivedText, 4092 bgpM2PeerLastErrorSent, 4093 bgpM2PeerLastErrorSentData, 4094 bgpM2PeerLastErrorSentTime, 4095 bgpM2PeerLastErrorSentText 4096 } 4097 STATUS current 4098 DESCRIPTION 4099 "Errors received on BGP peering sessions." 4100 ::= { bgpM2MIBGroups 12 } 4102 bgpM2PeerGroup OBJECT-GROUP 4103 OBJECTS { 4104 bgpM2PeerIdentifier, 4105 bgpM2PeerState, 4106 bgpM2PeerStatus, 4107 bgpM2PeerConfiguredVersion, 4108 bgpM2PeerNegotiatedVersion, 4109 bgpM2PeerLocalAddrType, 4110 bgpM2PeerLocalAddr, 4111 bgpM2PeerLocalPort, 4112 bgpM2PeerLocalAs, 4113 bgpM2PeerRemoteAddrType, 4114 bgpM2PeerRemoteAddr, 4115 bgpM2PeerRemotePort, 4116 bgpM2PeerRemoteAs, 4117 bgpM2PeerIndex 4118 } 4119 STATUS current 4120 DESCRIPTION 4121 "Core object types on BGP peering sessions." 4122 ::= { bgpM2MIBGroups 13 } 4124 bgpM2PathAttributesGroup OBJECT-GROUP 4125 OBJECTS { 4126 bgpM2PathAttrCount, 4127 bgpM2AsPathCalcLength, 4128 bgpM2AsPathElementValue, 4129 bgpM2AsPathIndex, 4130 bgpM2AsPathString, 4131 bgpM2AsPathType, 4132 bgpM2NlriAfi, 4133 bgpM2NlriBest, 4134 bgpM2NlriPrefix, 4135 bgpM2NlriPrefixLen, 4136 bgpM2NlriSafi, 4137 bgpM2NlriOpaqueType, 4138 bgpM2NlriOpaquePointer, 4139 bgpM2NlriIndex, 4140 bgpM2NlriCalcLocalPref, 4141 bgpM2AdjRibsOutIndex, 4142 bgpM2AdjRibsOutRoute, 4143 bgpM2PathAttrAggregatorAS, 4144 bgpM2PathAttrAggregatorAddr, 4145 bgpM2PathAttrAtomicAggregate, 4146 bgpM2PathAttrIndex, 4147 bgpM2PathAttrLocalPref, 4148 bgpM2PathAttrLocalPrefPresent, 4149 bgpM2PathAttrMed, 4150 bgpM2PathAttrMedPresent, 4151 bgpM2PathAttrNextHop, 4152 bgpM2PathAttrNextHopAddrType, 4153 bgpM2PathAttrOrigin, 4154 bgpM2PathAttrUnknownIndex, 4155 bgpM2PathAttrUnknownType, 4156 bgpM2PathAttrUnknownValue 4157 } 4158 STATUS current 4159 DESCRIPTION 4160 "Attributes received on BGP peering sessions." 4161 ::= { bgpM2MIBGroups 14 } 4163 bgpM2PeerConfigurationGroup OBJECT-GROUP 4164 OBJECTS { 4165 bgpM2CfgBaseScalarStorageType, 4166 bgpM2CfgLocalAs, 4167 bgpM2CfgLocalIdentifier, 4168 bgpM2CfgPeerAdminStatus, 4169 bgpM2CfgPeerNextIndex, 4170 bgpM2CfgPeerConfiguredVersion, 4171 bgpM2CfgAllowVersionNegotiation, 4172 bgpM2CfgPeerLocalAddrType, 4173 bgpM2CfgPeerLocalAddr, 4174 bgpM2CfgPeerLocalAs, 4175 bgpM2CfgPeerRemoteAddrType, 4176 bgpM2CfgPeerRemoteAddr, 4177 bgpM2CfgPeerRemotePort, 4178 bgpM2CfgPeerRemoteAs, 4179 bgpM2CfgPeerEntryStorageType, 4180 bgpM2CfgPeerError, 4181 bgpM2CfgPeerBgpPeerEntry, 4182 bgpM2CfgPeerRowEntryStatus, 4183 bgpM2CfgPeerIndex, 4184 bgpM2CfgPeerStatus, 4185 bgpM2CfgPeerConnectRetryInterval, 4186 bgpM2CfgPeerHoldTimeConfigured, 4187 bgpM2CfgPeerKeepAliveConfigured, 4188 bgpM2CfgPeerMinASOrigInterval, 4189 bgpM2CfgPeerMinRouteAdverInter 4190 } 4191 STATUS current 4192 DESCRIPTION 4193 "Configuration objects for BGP peers." 4194 ::= { bgpM2MIBGroups 15 } 4196 bgpM2PeerAuthConfigurationGroup OBJECT-GROUP 4197 OBJECTS { 4198 bgpM2CfgPeerAuthEnabled, 4199 bgpM2CfgPeerAuthCode, 4200 bgpM2CfgPeerAuthValue 4201 } 4202 STATUS current 4203 DESCRIPTION 4204 "Configuration objects for BGP peers that support 4205 authentication." 4206 ::= { bgpM2MIBGroups 16 } 4208 bgpM2PeerRouteReflectorCfgGroup OBJECT-GROUP 4209 OBJECTS { 4210 bgpM2CfgRouteReflector, 4211 bgpM2CfgClusterId, 4212 bgpM2CfgPeerReflectorClient 4213 } 4214 STATUS current 4215 DESCRIPTION 4216 "Configuration objects for BGP peers that support route 4217 reflection." 4218 ::= { bgpM2MIBGroups 17 } 4220 bgpM2PeerAsConfederationCfgGroup OBJECT-GROUP 4221 OBJECTS { 4222 bgpM2CfgConfederationRouter, 4223 bgpM2CfgConfederationId, 4224 bgpM2CfgPeerConfedMember 4225 } 4226 STATUS current 4227 DESCRIPTION 4228 "Configuration objects for BGP peers that support BGP 4229 confederations." 4230 ::= { bgpM2MIBGroups 18 } 4232 bgpM2MIBNotificationsGroup NOTIFICATION-GROUP 4233 NOTIFICATIONS { 4234 bgpM2Established, 4235 bgpM2BackwardTransition 4236 } 4237 STATUS current 4238 DESCRIPTION 4239 "This group contains objects for notifications 4240 supported by this mib module." 4241 ::= { bgpM2MIBGroups 19 } 4243 END 4245 2. Security Considerations 4247 This MIB module contains controls which relate to core services for 4248 interdomain routing using the Border Gateway Protocol. In particu- 4249 lar, this MIB allows configuration of operational elements for those 4250 services. If such configuration is done without consideration for 4251 the effects of such configuration activity, or malicious configura- 4252 tion activity is allowed on the managed elements, the effect could be 4253 denial of service to the processes and end users in the affected 4254 domain(s). 4256 SNMPv1 is not considered a sufficiently secure environment for the 4257 deployment of such configuration ability. Even if the management 4258 data path is secure at the network protocol layer (by the deployment 4259 of secure IP, for example), there are still points of exposure around 4260 such issues as to what operators and applications are allowed to 4261 access and modify the configuration as exposed through this MIB mod- 4262 ule. 4264 It is strongly recommended that the agent implementor considers the 4265 security features afforded by the SNMP Version 3 framework in expos- 4266 ing the configuration features of this MIB module. In particular, 4267 the availability and usage of the User-based Security Model [12] 4268 and/or the View-based Access Control Model [15] is highly recom- 4269 mended. 4271 It is then incumbent upon the customer deploying network management 4272 applications which make use of these configuration features to also 4273 consider and deploy a security discipline to make use of these SNMP 4274 Version 3 security features. In particular, the operational staff 4275 who have access to the configuration controls in their ability to 4276 create, set, and delete them, should be carefully considered. 4278 3. Intellectual Property 4280 The IETF takes no position regarding the validity or scope of any 4281 intellectual property or other rights that might be claimed to per- 4282 tain to the implementation or use of the technology described in this 4283 document or the extent to which any license under such rights might 4284 or might not be available; neither does it represent that it has made 4285 any effort to identify any such rights. Information on the IETF's 4286 procedures with respect to rights in standards-track and standards- 4287 related documentation can be found in BCP-11. Copies of claims of 4288 rights made available for publication and any assurances of licenses 4289 to be made available, or the result of an attempt made to obtain a 4290 general license or permission for the use of such proprietary rights 4291 by implementors or users of this specification can be obtained from 4292 the IETF Secretariat. 4294 4. Acknowledgements 4296 Tom Nadeau, Cisco Systems, Inc. 4297 Jon Saperia, JDS Consulting, Inc. 4298 Bill Fenner, AT&T Research 4299 Mike McFaden, Riverstone Networks, Inc. 4300 Joel Krauska, Exodus Networks, Inc. 4301 Carl W. Kalbfleisch, Verio Networks, Inc. 4302 Joe Dupre, Gold Wire Technology 4303 others TBD... 4305 5. Changes From Last Version 4307 This section is used to track changes from version to version of this 4308 document. This section will be removed from the document prior to 4309 being issued to IDR working group last call. 4311 * Changes from draft-ietf-idr-bgp4-mibv2-01.txt to draft-ietf- 4312 idr-bgp4-mibv2-02.txt (28 February 2002) 4314 Lots of changes in this rewrite, these are the most dramatic: 4316 Configuration objects and tables added. 4318 All references to 'bgp' in object descriptors changed to 4319 'bgpM2' to disambiguate from RFC 1657 and its OBSOLETing MIB. 4321 Community Textual conventions added to beginning of MIB. 4323 bgpM2CalcLength and PathString columns added to bgpM2PathAttr 4324 table. 4326 Creation of separate bgpM2AdjRibsOutTable. 4328 Appearance of NLRI table notions such as 'opaque type'. 4330 Overhaul of specification of AS Path types to accommodate eas- 4331 ier management at time of route aggregation. 4333 6. References 4335 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 4336 Describing SNMP Management Frameworks", RFC 2571, April 1999. 4338 [2] Rose, M., and K. McCloghrie, "Structure and Identification of Man- 4339 agement Information for TCP/IP-based Internets", STD 16, RFC 1155, 4340 May 1990. 4342 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 4343 1212, March 1991. 4345 [4] Rose, M., "A Convention for Defining Traps for use with the SNMP", 4346 RFC 1215, March 1991. 4348 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 4349 and S. Waldbusser, "Structure of Management Information Version 2 4350 (SMIv2)", STD 58, RFC 2578, April 1999. 4352 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 4353 and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 4354 2579, April 1999. 4356 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 4357 and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 4358 2580, April 1999. 4360 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 4361 Management Protocol", STD 15, RFC 1157, May 1990. 4363 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Introduc- 4364 tion to Community-based SNMPv2", RFC 1901, January 1996. 4366 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 4367 Mappings for Version 2 of the Simple Network Management Protocol 4368 (SNMPv2)", RFC 1906, January 1996. 4370 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message Pro- 4371 cessing and Dispatching for the Simple Network Management Protocol 4372 (SNMP)", RFC 2572, April 1999. 4374 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 4375 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 4376 2574, April 1999. 4378 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 4379 Operations for Version 2 of the Simple Network Management Protocol 4380 (SNMPv2)", RFC 1905, January 1996. 4382 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 4383 2573, April 1999. 4385 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Con- 4386 trol Model (VACM) for the Simple Network Management Protocol 4387 (SNMP)", RFC 2575, April 1999. 4389 [16] McCloghrie, K. and M. Rose, Editors, "Management Information Base 4390 for Network Management of TCP/IP-based Internets: MIB-II", STD 17, 4391 RFC 1213, Hughes LAN Systems, Performance Systems International, 4392 March 1991. 4394 [17] Willis, S., Burruss, J., and Chu, J., "Definitions of Managed 4395 Objects for the Fourth Version of the Border Gateway Protocol 4396 (BGP-4) using SMIv2", RFC 1657, July 1994. 4398 [18] Hares, S., Haas, J., Willis, S., Burruss, J., and Chu, J., "Defini- 4399 tions of Managed Objects for the Fourth Version of Border Gateway 4400 Protocol (BGP-4)", draft-ietf-idr-bgp4-mib-06.txt, Work-in- 4401 progress. 4403 [19] Rekhter, Y., Li, T., "A Border Gateway Protocol 4 (BGP-4)", RFC 4404 1771, March 1995. 4406 [20] Rekhter, Y., Gross, P., "Application of the Border Gateway Proto- 4407 col in the Internet", RFC 1772, March 1995. 4409 [21] Traina, P., McPherson, D., and Scudder, J., "Autonomous System 4410 Confederations for BGP", RFC 3065, February, 2001. 4412 [22] Chandra, R., Traina, P., and Li, T., "BGP Communities Attribute", 4413 RFC 1997, August, 1996. 4415 [23] Bates, T., Rekhter, Y., Chandra, R., and Katz, D., "Multiprotocol 4416 Extensions for BGP-4", June, 2000. 4418 [24] Bates, T., Chandra, R., and Chen, E., "BGP Route Reflection - An 4419 Alternative to Full Mesh IBGP", RFC 2796, April 2000. 4421 [25] Sangli, S., Tappan, D., and Rekhter, Y., "BGP Extended Communities 4422 Attribute", Work-in-progress. 4424 [26] Rehkter, Y., and Rosen, E., "Carrying Label Information in BGP-4", 4425 RFC 3107, May 2001. 4427 7. Authors' Addresses 4429 Jeff Haas 4430 NextHop Technologies 4431 825 Victors Way, Suite 100 4432 Ann Arbor, MI 48108 4433 Phone: +1 734 222-1600 4434 Fax: +1 734 222-1602 4435 Email: jhaas@nexthop.com 4436 Susan Hares 4437 NextHop Technologies 4438 825 Victors Way, Suite 100 4439 Ann Arbor, MI 48108 4440 Phone: +1 734 222-1600 4441 Fax: +1 734 222-1602 4442 Email: skh@nexthop.com 4444 Wayne Tackabury 4445 Gold Wire Technology 4446 411 Waverley Oaks Rd. 4447 Waltham, MA 02452-8401 4448 Phone: +1 781 398-8819 4449 Fax: +1 781 398-8811 4450 Email: wayne@goldwiretech.com 4452 8. Full Copyright Statement 4454 Copyright (C) The Internet Society (2002). All Rights Reserved. 4456 This document and translations of it may be copied and furnished to 4457 others, and derivative works that comment on or otherwise explain it 4458 or assist in its implementation may be prepared, copied, published 4459 and distributed, in whole or in part, without restriction of any 4460 kind, provided that the above copyright notice and this paragraph are 4461 included on all such copies and derivative works. However, this doc- 4462 ument itself may not be modified in any way, such as by removing the 4463 copyright notice or references to the Internet Society or other 4464 Internet organizations, except as needed for the purpose of develop- 4465 ing Internet standards in which case the procedures for copyrights 4466 defined in the Internet Standards process must be followed, or as 4467 required to translate it into languages other than English. 4469 The limited permissions granted above are perpetual and will not be 4470 revoked by the Internet Society or its successors or assigns. 4472 This document and the information contained herein is provided on an 4473 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 4474 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 4475 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 4476 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MER- 4477 CHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 4479 Table of Contents 4481 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2 4482 2. Objectives . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 4483 2.1. Protocol Extensions . . . . . . . . . . . . . . . . . . . . . . 3 4484 2.2. Mechanisms for MIB Extensibility . . . . . . . . . . . . . . . 3 4485 2.3. BGP Configuration . . . . . . . . . . . . . . . . . . . . . . . 4 4486 3. MIB Organization . . . . . . . . . . . . . . . . . . . . . . . . 4 4487 3.1. bgpM2BaseScalars . . . . . . . . . . . . . . . . . . . . . . . 5 4488 3.2. bgpM2PeerData . . . . . . . . . . . . . . . . . . . . . . . . . 5 4489 3.2.1. bgpM2PeerCapabilities . . . . . . . . . . . . . . . . . . . . 6 4490 3.2.2. bgpM2PeerCounters . . . . . . . . . . . . . . . . . . . . . . 6 4491 3.2.3. Peering Data Extensions . . . . . . . . . . . . . . . . . . . 6 4492 3.2.4. Configuring Peering Sessions . . . . . . . . . . . . . . . . 7 4493 3.3. BGP Routing Information Base Data . . . . . . . . . . . . . . . 8 4494 3.3.1. Routing Information Base Extensions . . . . . . . . . . . . . 9 4495 3.4. Considerations on Table Indexing . . . . . . . . . . . . . . . 9 4496 1. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 4497 2. Security Considerations . . . . . . . . . . . . . . . . . . . . . 95 4498 3. Intellectual Property . . . . . . . . . . . . . . . . . . . . . . 96 4499 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 96 4500 5. Changes From Last Version . . . . . . . . . . . . . . . . . . . . 97 4501 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 4502 7. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 99 4503 8. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 100