idnits 2.17.1 draft-ietf-mboned-msdp-mib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 15. -- Found old boilerplate from RFC 3978, Section 5.5 on line 1573. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1582. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1589. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1595. ** Found boilerplate matching RFC 3978, Section 5.4, paragraph 1 (on line 38), which is fine, but *also* found old RFC 2026, Section 10.4C, paragraph 1 text on line 38. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** The document seems to lack an RFC 3978 Section 5.4 Reference to BCP 78. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == 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 a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 176: '... value MUST be 60....' RFC 2119 keyword, line 761: '...ection 5.1 says it MUST be 60 seconds....' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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 (October 2005) is 6758 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: 'SG-State-Period' on line 346 -- Looks like a reference, but probably isn't: 'SA-Advertisement-Timer' on line 759 -- Looks like a reference, but probably isn't: 'ConnectRetry-period' on line 769 -- Looks like a reference, but probably isn't: 'HoldTime-Period' on line 781 -- Looks like a reference, but probably isn't: 'KeepAlive-Period' on line 796 -- Looks like a reference, but probably isn't: 'Fenner' on line 1504 == Unused Reference: '1' is defined on line 1532, but no explicit reference was found in the text ** Downref: Normative reference to an Experimental RFC: RFC 3618 (ref. '1') Summary: 7 errors (**), 0 flaws (~~), 3 warnings (==), 13 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 MBONED Working Group Bill Fenner 2 INTERNET-DRAFT AT&T Research 3 Expires: April 2006 Dave Thaler 4 Microsoft 5 October 2005 7 Multicast Source Discovery protocol MIB 8 10 Status of this Document 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware have 14 been or will be disclosed, and any of which he or she becomes aware will 15 be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering Task 18 Force (IETF), its areas, and its working groups. Note that other groups 19 may also distribute working documents as Internet-Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet-Drafts as reference material 24 or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 This document is a product of the MBONED Working Group. Comments should 33 be addressed to the authors, or the mailing list at 34 mboned@lists.uoregon.edu. 36 Copyright Notice 38 Copyright (C) The Internet Society (2005). All Rights Reserved. 40 Abstract 42 This memo defines an experimental portion of the Management Information 43 Base (MIB) for use with network management protocols in the Internet 44 community. In particular, it describes managed objects used for 45 managing Multicast Source Discovery Protocol (MSDP) (RFC 3618) speakers. 47 Table of Contents 49 1. The Internet-Standard Management Framework. . . . . . . . . . . . 2 50 2. Revision History. . . . . . . . . . . . . . . . . . . . . . . . . 2 51 3. Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 52 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 53 5. Security Considerations . . . . . . . . . . . . . . . . . . . . . 31 54 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . . 32 55 7. Acknowledgements. . . . . . . . . . . . . . . . . . . . . . . . . 32 56 8. Authors' Addresses. . . . . . . . . . . . . . . . . . . . . . . . 32 57 9. Normative References. . . . . . . . . . . . . . . . . . . . . . . 33 58 9.1. Informative References . . . . . . . . . . . . . . . . . . . . 33 59 10. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 34 61 1. The Internet-Standard Management Framework 63 For a detailed overview of the documents that describe the current 64 Internet-Standard Management Framework, please refer to section 7 of RFC 65 3410 [7]. 67 Managed objects are accessed via a virtual information store, termed the 68 Management Information Base or MIB. MIB objects are generally accessed 69 through the Simple Network Management Protocol (SNMP). Objects in the 70 MIB are defined using the mechanisms defined in the Structure of 71 Management Information (SMI). This memo specifies a MIB module that is 72 compliant to the SMIv2, which is described in STD 58, RFC 2578 [4], STD 73 58, RFC 2579 [5] and STD 58, RFC 2580 [6]. 75 2. Revision History 77 A record of changes which will be removed before publication. 79 20 October 2005 81 Added explicit reasoning for IPv4-only-osity and for the 82 unorganized organization. 84 Updated Copyright and IPR statements. 86 Updated Security Considerations, per RFC4181. 88 Added IANA Considerations, per RFC4181. 90 Added REVISION and WG mailing list to MODULE-IDENTITY, per RFC4181. 92 Changed some TimeTicks to TimeStamp, on RFC4181's advice. 94 Added advice on non-volatile storage, row creation and column 95 modification to tables with RowStatus columns, per RFC4181. 97 Added msdpReadOnlyCompliance to permit implementations that don't 98 implement writing. 100 Clarified that msdpSAStatePeriod was an accidental duplication of 101 msdpCacheLifetime. 103 Described the epochs for TimeTicks objects, per RFC4181. Add a 104 note that msdpCacheLifetime would really be better as a 105 TimeInterval, but is TimeTicks for hysterical raisins. 107 11 July 2004 109 Renamed to draft-ietf-mboned-msdp-mib-00. 111 Fixed spec references and defaults for msdpPeerHoldTimeConfigured, 112 msdpPeerKeepAliveConfigured and msdpPeerConnectRetryInterval, as 113 pointed out by Ketan Talaulikar. 115 Deprecated all objects related to SA-Requests and notifications, 116 since RFC 3618 doesn't have either one. As pointed out by Ketan 117 Talaulikar. 119 Clarified that msdpSACachePeerLearnedFrom should be 0.0.0.0 on the 120 originator. From Mike Davison. 122 Removed msdpSAStatePeriod. I couldn't figure out what it's for; at 123 best it should be SG State Period, but that's already 124 msdpCacheLifetime. From Mike Davison. 126 17 October 2003 128 Undid most of the hard work since draft -03, which is the only 129 implementation I was able to find by querying the MSDP mailing 130 list. 132 29 May 2003 134 Republished with no changes. How did it get to be almost 2 years? 136 18 July 2001 138 Since the INET-ADDRESS-MIB relaxed restrictions on InetAddressType, 139 remove msdpPeerLocalAddressType, rename msdpSACacheGroupAddrType to 140 msdpCacheAddrType, remove msdpCacheSourceAddrType, 141 msdpSACacheOriginRPType, msdpSACachePeerLearnedFromType, 142 msdpSACacheRPFPeerType. 144 Updated the DESCRIPTION of msdpRequestsTable to describe exactly 145 how it is used. 147 Added msdpPeerDiscontinuityTime. 149 Changed msdpPeerFsmEstablishedTime to a TimeStamp instead of a 150 counting number of seconds. 152 Changed msdpPeerInMessageElapsedTime to msdpPeerInMessageTime and 153 changed it to a TimeStamp. 155 Added msdpMeshGroupTable. 157 Updated conformance information. 159 1 March 2001 161 Added msdpPeerIfIndex. 163 Converted all IpAddress items to InetAddressType/InetAddress pairs. 164 This bigtime violates RFC2578's rules about MIB evolution, so take 165 extra care when implementing this change. 167 Added msdpRequestsPriority, in order to allow configuration of 168 multiple peers to whom Requests will be sent. Note that this 169 violates RFC2578's rules about MIB evolution, so take extra care 170 when implementing this change. 172 Removed DEFVAL on scalars, since it should only be needed for table 173 row creation. 175 Removed msdpPeerSAAdvPeriod, since the spec changed to say its 176 value MUST be 60. 178 Added none(0) to msdpPeerEncapsulationType enumeration (is this OK? 179 should it be 4?) 181 Removed msdpPeerEncapsulationState since the encapsulation 182 "negotiation" was removed from the spec. 184 Added msdpRPAddress to specify the RP address to use when sourcing 185 SA messages. 187 Added msdpSACacheSourcePrefix to msdpSACacheTable, and added it to 188 the INDEX. Note that this violates RFC2578's rules about MIB 189 evolution, so take extra care when implementing this change. 191 Completely renumbered the MIB, removing the extra level of 192 msdpMIBobjects and creating an msdpScalars group to contain all 193 scalars. Note that this violates RFC2578's rules about MIB 194 evolution, so take extra care when implementing this change. 196 16 December 1999 198 Added msdpSAHoldDownPeriod, msdpPeerEncapsulationState, 199 msdpPeerEncapsulationType, msdpPeerConnectionAttempts, 200 msdpPeerInNotifications, msdpPeerOutNotifications, and 201 msdpLastError 203 Removed msdpPeerConfigMethod, since this has disappeared from the 204 spec. 206 Renamed the states in msdpPeerState to go with the state machine in 207 the spec. 209 Added msdpPeerLocalPort and msdpPeerRemotePort in order to provide 210 full information about the TCP connection in use. I'd like to 211 reorder the Peer Table but that can wait until the MIB gets 212 published as an RFC in order to only change things like that once. 214 Added msdpSACacheOriginRP as an INDEX to the msdpSACacheTable. 215 Note that this violates RFC2578's rules about MIB evolution, so 216 take extra care when implementing this change. 218 25 June 1999 220 Renamed to DRAFT-MSDP-MIB. It will be renamed back to MSDP-MIB 221 when it gets renumbered under mib-2, in order to avoid module 222 naming problems. 224 Turned msdpSendRequestsTo into a table in order to handle 225 administratively scoped groups with different RP's. 227 27 May 1999 229 Added IANA-assigned experimental OID 231 Added msdpSendRequestsTo and msdpPeerProcessRequestsFrom to 232 configure MSDP SA-Request/Response processing. 234 Added msdpPeerDataTtl to allow TTL scoping of data packets 235 forwarded across MSDP peerings. 237 Renumbered msdpSACacheInDataPackets and further items in 238 msdpSACacheTable, to eliminate duplicate OIDs 240 20 April 1999 242 initial version. 244 3. Overview 246 This MIB module contains four scalars and four tables, one deprecated. 247 The tables are: 249 o the deprecated Requests Table, containing the longest-match table 250 used to determine the peer to send SA-Requests to for a given 251 group. This table is deprecated because Requests were removed from 252 MSDP before it became an RFC; 254 o the Peer Table, containing information on the system's peers; 256 o the Source-Active Cache Table, containing the SA cache entries; and 258 o the Mesh Group Table, containing the list of MSDP mesh groups to 259 which this system belongs. 261 This MIB module uses the IpAddress SYNTAX, making it only suitable for 262 IPv4 systems. Although the desired direction for MIBs is to use 263 InetAddressType/InetAddress pairs to allow both IPv4 and IPv6 (and 264 future formats as well), the MSDP protocol itself is IPv4-only, and the 265 MSDP working group made an explicit decision to not create an IPv6 266 version of the protocol. 268 This MIB module is somewhat disorganized, with scalars before and after 269 tables, holes in the OID space, tables with the RowStatus in the middle, 270 and so on. This is because objects were added and removed as necessary 271 as the MSDP protocol evolved, and the plan was to renumber the whole MIB 272 when moving to the standard mib-2 tree. The MSDP Working Group then 273 changed direction, publishing the MSDP protcol as Experimental. Since 274 there were existing implementations using the strange object order under 275 the experimental OID, the WG decided not to renumber the MIB and to 276 publish it as experimental, keeping the experimental OID. 278 4. Definitions 280 -- 281 -- 282 DRAFT-MSDP-MIB DEFINITIONS ::= BEGIN 284 IMPORTS 285 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 286 experimental, Counter32, Gauge32, TimeTicks, Integer32, 287 IpAddress 288 FROM SNMPv2-SMI 289 RowStatus, TruthValue, TimeStamp, DisplayString 290 FROM SNMPv2-TC 291 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 292 FROM SNMPv2-CONF; 294 msdpMIB MODULE-IDENTITY 295 LAST-UPDATED "200510210000Z" 296 ORGANIZATION "IETF MBONED Working Group" 297 CONTACT-INFO 298 "Bill Fenner 299 75 Willow Road 300 Menlo Park, CA 94025 301 Phone: +1 650 867 6073 302 E-mail: fenner@research.att.com 304 Dave Thaler 305 One Microsoft Way 306 Redmond, WA 98052 307 Phone: +1 425 703 8835 308 Email: dthaler@microsoft.com 310 MBONED Working Group: mboned@lists.uoregon.edu" 311 DESCRIPTION 312 "An experimental MIB module for MSDP Management and 313 Monitoring. 315 Copyright (C) The Internet Society 2005. This version of 316 this MIB module is part of RFC XXXX; see the RFC itself for 317 full legal notices." 318 REVISION "200510210000Z" 319 DESCRIPTION 320 "Initial version, published as RFC XXXX." 321 ::= { experimental 92 } 322 -- RFC Ed.: replace XXXX with actual RFC number & remove this note 324 msdpMIBobjects OBJECT IDENTIFIER ::= { msdpMIB 1 } 326 msdp OBJECT IDENTIFIER ::= { msdpMIBobjects 1 } 328 msdpEnabled OBJECT-TYPE 329 SYNTAX TruthValue 330 MAX-ACCESS read-write 331 STATUS current 332 DESCRIPTION 333 "The state of MSDP on this MSDP speaker - globally enabled or 334 disabled. 336 Changes to this object should be stored to non-volatile 337 memory." 338 ::= { msdp 1 } 340 msdpCacheLifetime OBJECT-TYPE 341 SYNTAX TimeTicks 342 MAX-ACCESS read-write 343 STATUS current 344 DESCRIPTION 345 "The lifetime given to SA cache entries when created or 346 refreshed. This is the [SG-State-Period] in the MSDP spec. 347 A value of 0 means no SA caching is done by this MSDP 348 speaker. 350 Changes to this object should be stored to non-volatile 351 memory. 353 This object does not measure time per se; instead, it is the 354 delta from the time at which an SA message is received at 355 which it should be expired if not refreshed. (i.e., it is 356 the value of msdpSACacheExpiryTime immediately after 357 receiving an SA message applying to that row.) As such, 358 TimeInterval would be a more appropriate SYNTAX; it remains 359 TimeTicks for backwards compatability." 360 REFERENCE "RFC 3618 section 5.3" 361 ::= { msdp 2 } 363 msdpNumSACacheEntries OBJECT-TYPE 364 SYNTAX Gauge32 365 MAX-ACCESS read-only 366 STATUS current 367 DESCRIPTION 368 "The total number of entries in the SA Cache table." 369 ::= { msdp 3 } 371 -- 372 -- The spec doesn't define SA-Hold-Down-Period any more. 373 -- msdpSAHoldDownPeriod OBJECT-TYPE 374 -- ::= { msdp 9 } 376 -- This object was introduced in error, with a similar definition 377 -- to msdpCacheLifetime. 378 -- msdpSAStatePeriod OBJECT-TYPE 379 -- ::= { msdp 10 } 380 msdpRPAddress OBJECT-TYPE 381 SYNTAX IpAddress 382 MAX-ACCESS read-write 383 STATUS current 384 DESCRIPTION 385 "The RP address used when sourcing MSDP SA messages. May be 386 0.0.0.0 on non-RP's. 388 Changes to this object should be stored to non-volatile 389 memory." 390 ::= { msdp 11 } 392 -- 393 -- The MSDP Requests table 394 -- SA Requests were removed from the MSDP spec, so this entire table 395 -- is deprecated. 397 msdpRequestsTable OBJECT-TYPE 398 SYNTAX SEQUENCE OF MsdpRequestsEntry 399 MAX-ACCESS not-accessible 400 STATUS deprecated 401 DESCRIPTION 402 "The (conceptual) table listing group ranges and MSDP peers 403 used when deciding where to send an SA Request message when 404 required. If SA Requests are not enabled, this table may be 405 empty. 407 In order to choose a peer to whom to send an SA Request for 408 a given group G, the subset of entries in this table whose 409 (msdpRequestsPeerType, msdpRequestsPeer) tuple represents a 410 peer whose msdpPeerState is established are examined. The 411 set is further reduced by examining only those entries for 412 which msdpPeerRequestsGroupAddressType equals the address 413 type of G, and the entries with the highest value of 414 msdpRequestsGroupPrefix are considered, where the group G 415 falls within the range described by the combination of 416 msdpRequestsGroup and msdpRequestsGroupPrefix. (This 417 sequence is commonly known as a 'longest-match' lookup.) 419 Finally, if multiple entries remain, the entry with the 420 lowest value of msdpRequestsPriority is chosen. The SA 421 Request message is sent to the peer described by this row." 422 ::= { msdp 4 } 424 msdpRequestsEntry OBJECT-TYPE 425 SYNTAX MsdpRequestsEntry 426 MAX-ACCESS not-accessible 427 STATUS deprecated 428 DESCRIPTION 429 "An entry (conceptual row) representing a group range used 430 when deciding where to send an SA Request message." 431 INDEX { msdpRequestsGroupAddress, msdpRequestsGroupMask } 432 ::= { msdpRequestsTable 1 } 434 MsdpRequestsEntry ::= SEQUENCE { 435 msdpRequestsGroupAddress IpAddress, 436 msdpRequestsGroupMask IpAddress, 437 msdpRequestsPeer IpAddress, 438 msdpRequestsStatus RowStatus 439 } 441 msdpRequestsGroupAddress OBJECT-TYPE 442 SYNTAX IpAddress 443 MAX-ACCESS not-accessible 444 STATUS deprecated 445 DESCRIPTION 446 "The group address that, when combined with the mask in this 447 entry, represents the group range to which this row 448 applies." 449 ::= { msdpRequestsEntry 1 } 451 msdpRequestsGroupMask OBJECT-TYPE 452 SYNTAX IpAddress 453 MAX-ACCESS not-accessible 454 STATUS deprecated 455 DESCRIPTION 456 "The mask that, when combined with the group address in this 457 entry, represents the group range to which this row 458 applies." 459 ::= { msdpRequestsEntry 2 } 461 msdpRequestsPeer OBJECT-TYPE 462 SYNTAX IpAddress 463 MAX-ACCESS read-create 464 STATUS deprecated 465 DESCRIPTION 466 "The peer to which MSDP SA Requests for groups matching this 467 entry's group range will be sent. This object combined with 468 msdpRequestsPeerType must match the INDEX of a row in the 469 msdpPeerTable, and to be considered, this peer's 470 msdpPeerState must be established." 471 ::= { msdpRequestsEntry 3 } 473 msdpRequestsStatus OBJECT-TYPE 474 SYNTAX RowStatus 475 MAX-ACCESS read-create 476 STATUS deprecated 477 DESCRIPTION 478 "The status of this row, by which new rows may be added to 479 the table or old rows may be deleted." 480 ::= { msdpRequestsEntry 4 } 482 -- 483 -- The MSDP Peer table 484 -- 486 msdpPeerTable OBJECT-TYPE 487 SYNTAX SEQUENCE OF MsdpPeerEntry 488 MAX-ACCESS not-accessible 489 STATUS current 490 DESCRIPTION 491 "The (conceptual) table listing the MSDP speaker's peers." 492 ::= { msdp 5 } 494 msdpPeerEntry OBJECT-TYPE 495 SYNTAX MsdpPeerEntry 496 MAX-ACCESS not-accessible 497 STATUS current 498 DESCRIPTION 499 "An entry (conceptual row) representing an MSDP peer. 501 If row creation is supported, dynamically added rows are 502 added to the system's stable configuration (corresponding to 503 a StorageType value of nonVolatile). " 504 INDEX { msdpPeerRemoteAddress } 505 ::= { msdpPeerTable 1 } 507 MsdpPeerEntry ::= SEQUENCE { 508 msdpPeerRemoteAddress IpAddress, 509 msdpPeerState INTEGER, 510 msdpPeerRPFFailures Counter32, 511 msdpPeerInSAs Counter32, 512 msdpPeerOutSAs Counter32, 513 msdpPeerInSARequests Counter32, 514 msdpPeerOutSARequests Counter32, 515 msdpPeerInSAResponses Counter32, 516 msdpPeerOutSAResponses Counter32, 517 msdpPeerInControlMessages Counter32, 518 msdpPeerOutControlMessages Counter32, 519 msdpPeerInDataPackets Counter32, 520 msdpPeerOutDataPackets Counter32, 521 msdpPeerFsmEstablishedTransitions Counter32, 522 msdpPeerFsmEstablishedTime TimeStamp, 523 msdpPeerInMessageTime TimeStamp, 524 msdpPeerLocalAddress IpAddress, 525 msdpPeerConnectRetryInterval Integer32, 526 msdpPeerHoldTimeConfigured Integer32, 527 msdpPeerKeepAliveConfigured Integer32, 528 msdpPeerDataTtl Integer32, 529 msdpPeerProcessRequestsFrom TruthValue, 530 msdpPeerStatus RowStatus, 531 msdpPeerRemotePort Integer32, 532 msdpPeerLocalPort Integer32, 533 msdpPeerEncapsulationType INTEGER, 534 msdpPeerConnectionAttempts Counter32, 535 msdpPeerInNotifications Counter32, 536 msdpPeerOutNotifications Counter32, 537 msdpPeerLastError OCTET STRING, 538 msdpPeerDiscontinuityTime TimeStamp 539 } 541 msdpPeerRemoteAddress OBJECT-TYPE 542 SYNTAX IpAddress 543 MAX-ACCESS not-accessible 544 STATUS current 545 DESCRIPTION 546 "The address of the remote MSDP peer." 547 ::= { msdpPeerEntry 1 } 549 -- dunno what happened to 2. 551 msdpPeerState OBJECT-TYPE 552 SYNTAX INTEGER { 553 inactive(1), 554 listen(2), 555 connecting(3), 556 established(4), 557 disabled(5) 558 } 559 MAX-ACCESS read-only 560 STATUS current 561 DESCRIPTION 562 "The state of the MSDP TCP connection with this peer." 563 ::= { msdpPeerEntry 3 } 565 msdpPeerRPFFailures OBJECT-TYPE 566 SYNTAX Counter32 567 MAX-ACCESS read-only 568 STATUS current 569 DESCRIPTION 570 "The number of SA messages received from this peer which 571 failed the Peer-RPF check. 573 Discontinuities in the value of this counter can occur at 574 re-initialization of the management system, and at other 575 times as indicated by the value of 576 msdpPeerDiscontinuityTime." 577 ::= { msdpPeerEntry 4 } 579 msdpPeerInSAs OBJECT-TYPE 580 SYNTAX Counter32 581 MAX-ACCESS read-only 582 STATUS current 583 DESCRIPTION 584 "The number of MSDP SA messages received on this connection. 586 Discontinuities in the value of this counter can occur at 587 re-initialization of the management system, and at other 588 times as indicated by the value of 589 msdpPeerDiscontinuityTime." 590 ::= { msdpPeerEntry 5 } 592 msdpPeerOutSAs OBJECT-TYPE 593 SYNTAX Counter32 594 MAX-ACCESS read-only 595 STATUS current 596 DESCRIPTION 597 "The number of MSDP SA messages transmitted on this 598 connection. 600 Discontinuities in the value of this counter can occur at 601 re-initialization of the management system, and at other 602 times as indicated by the value of 603 msdpPeerDiscontinuityTime." 604 ::= { msdpPeerEntry 6 } 606 msdpPeerInSARequests OBJECT-TYPE 607 SYNTAX Counter32 608 MAX-ACCESS read-only 609 STATUS current 610 DESCRIPTION 611 "The number of MSDP SA-Request messages received on this 612 connection. 614 Discontinuities in the value of this counter can occur at 615 re-initialization of the management system, and at other 616 times as indicated by the value of 617 msdpPeerDiscontinuityTime." 618 ::= { msdpPeerEntry 7 } 620 msdpPeerOutSARequests OBJECT-TYPE 621 SYNTAX Counter32 622 MAX-ACCESS read-only 623 STATUS current 624 DESCRIPTION 625 "The number of MSDP SA-Request messages transmitted on this 626 connection. 628 Discontinuities in the value of this counter can occur at 629 re-initialization of the management system, and at other 630 times as indicated by the value of 631 msdpPeerDiscontinuityTime." 632 ::= { msdpPeerEntry 8 } 634 msdpPeerInSAResponses OBJECT-TYPE 635 SYNTAX Counter32 636 MAX-ACCESS read-only 637 STATUS deprecated 638 DESCRIPTION 639 "The number of MSDP SA-Response messages received on this 640 connection. 642 Discontinuities in the value of this counter can occur at 643 re-initialization of the management system, and at other 644 times as indicated by the value of 645 msdpPeerDiscontinuityTime." 646 ::= { msdpPeerEntry 9 } 648 msdpPeerOutSAResponses OBJECT-TYPE 649 SYNTAX Counter32 650 MAX-ACCESS read-only 651 STATUS deprecated 652 DESCRIPTION 653 "The number of MSDP SA Response messages transmitted on this 654 TCP connection. 656 Discontinuities in the value of this counter can occur at 657 re-initialization of the management system, and at other 658 times as indicated by the value of 659 msdpPeerDiscontinuityTime." 660 ::= { msdpPeerEntry 10 } 662 msdpPeerInControlMessages OBJECT-TYPE 663 SYNTAX Counter32 664 MAX-ACCESS read-only 665 STATUS current 666 DESCRIPTION 667 "The total number of MSDP messages, excluding encapsulated 668 data packets, received on this TCP connection. 670 Discontinuities in the value of this counter can occur at 671 re-initialization of the management system, and at other 672 times as indicated by the value of 673 msdpPeerDiscontinuityTime." 674 ::= { msdpPeerEntry 11 } 676 msdpPeerOutControlMessages OBJECT-TYPE 677 SYNTAX Counter32 678 MAX-ACCESS read-only 679 STATUS current 680 DESCRIPTION 681 "The total number of MSDP messages, excluding encapsulated 682 data packets, transmitted on this TCP connection. 684 Discontinuities in the value of this counter can occur at 685 re-initialization of the management system, and at other 686 times as indicated by the value of 687 msdpPeerDiscontinuityTime." 688 ::= { msdpPeerEntry 12 } 690 msdpPeerInDataPackets OBJECT-TYPE 691 SYNTAX Counter32 692 MAX-ACCESS read-only 693 STATUS current 694 DESCRIPTION 695 "The total number of encapsulated data packets received from 696 this peer. 698 Discontinuities in the value of this counter can occur at 699 re-initialization of the management system, and at other 700 times as indicated by the value of 701 msdpPeerDiscontinuityTime." 702 ::= { msdpPeerEntry 13 } 704 msdpPeerOutDataPackets OBJECT-TYPE 705 SYNTAX Counter32 706 MAX-ACCESS read-only 707 STATUS current 708 DESCRIPTION 709 "The total number of encapsulated data packets sent to this 710 peer. 712 Discontinuities in the value of this counter can occur at 713 re-initialization of the management system, and at other 714 times as indicated by the value of 715 msdpPeerDiscontinuityTime." 717 ::= { msdpPeerEntry 14 } 719 msdpPeerFsmEstablishedTransitions OBJECT-TYPE 720 SYNTAX Counter32 721 MAX-ACCESS read-only 722 STATUS current 723 DESCRIPTION 724 "The total number of times the MSDP FSM transitioned into the 725 ESTABLISHED state." 726 REFERENCE "RFC 3618 section 11" 727 ::= { msdpPeerEntry 15 } 729 msdpPeerFsmEstablishedTime OBJECT-TYPE 730 SYNTAX TimeStamp 731 MAX-ACCESS read-only 732 STATUS current 733 DESCRIPTION 734 "This timestamp is set to the value of sysUpTime when a peer 735 transitions into or out of the ESTABLISHED state. It is set 736 to zero when the MSDP speaker is booted." 737 REFERENCE "RFC 3618 section 11" 738 ::= { msdpPeerEntry 16 } 740 msdpPeerInMessageTime OBJECT-TYPE 741 SYNTAX TimeStamp 742 MAX-ACCESS read-only 743 STATUS current 744 DESCRIPTION 745 "The sysUpTime value when the last MSDP message was received 746 from the peer. It is set to zero when the MSDP speaker is 747 booted." 748 ::= { msdpPeerEntry 17 } 750 msdpPeerLocalAddress OBJECT-TYPE 751 SYNTAX IpAddress 752 MAX-ACCESS read-create 753 STATUS current 754 DESCRIPTION 755 "The local IP address used for this entry's MSDP TCP 756 connection." 757 ::= { msdpPeerEntry 18 } 759 -- msdpPeerSAAdvPeriod ([SA-Advertisement-Timer]) has been removed. 760 -- ::= { msdpPeerEntry 19 } 761 -- RFC 3618 section 5.1 says it MUST be 60 seconds. 763 msdpPeerConnectRetryInterval OBJECT-TYPE 764 SYNTAX Integer32 (1..65535) 765 UNITS "seconds" 766 MAX-ACCESS read-create 767 STATUS current 768 DESCRIPTION 769 "Time interval in seconds for the [ConnectRetry-period] for 770 this peer." 771 REFERENCE "RFC 3618 section 5.6" 772 DEFVAL { 30 } 773 ::= { msdpPeerEntry 20 } 775 msdpPeerHoldTimeConfigured OBJECT-TYPE 776 SYNTAX Integer32 (0|3..65535) 777 UNITS "seconds" 778 MAX-ACCESS read-create 779 STATUS current 780 DESCRIPTION 781 "Time interval in seconds for the [HoldTime-Period] 782 configured for this MSDP speaker with this peer. If the 783 value of this object is zero (0), the MSDP connection is 784 never torn down due to the absence of messages from the 785 peer." 786 REFERENCE "RFC 3618 section 5.4" 787 DEFVAL { 75 } 788 ::= { msdpPeerEntry 21 } 790 msdpPeerKeepAliveConfigured OBJECT-TYPE 791 SYNTAX Integer32 (0|1..21845) 792 UNITS "seconds" 793 MAX-ACCESS read-create 794 STATUS current 795 DESCRIPTION 796 "Time interval in seconds for the [KeepAlive-Period] 797 configured for this MSDP speaker with this peer. If the 798 value of this object is zero (0), no periodic KEEPALIVE 799 messages are sent to the peer after the MSDP connection has 800 been established." 801 REFERENCE "RFC 3618 section 5.5" 802 DEFVAL { 60 } 803 ::= { msdpPeerEntry 22 } 805 msdpPeerDataTtl OBJECT-TYPE 806 SYNTAX Integer32 (0..255) 807 MAX-ACCESS read-create 808 STATUS current 809 DESCRIPTION 810 "The minimum TTL a packet is required to have before it may 811 be forwarded using SA encapsulation to this peer." 813 DEFVAL { 1 } 814 ::= { msdpPeerEntry 23 } 816 msdpPeerProcessRequestsFrom OBJECT-TYPE 817 SYNTAX TruthValue 818 MAX-ACCESS read-create 819 STATUS deprecated 820 DESCRIPTION 821 "This object indicates whether or not to process MSDP SA 822 Request messages from this peer. If True(1), MSDP SA 823 Request messages from this peer are processed and replied to 824 (if appropriate) with SA Response messages. If False(2), 825 MSDP SA Request messages from this peer are silently 826 ignored. It defaults to False when msdpCacheLifetime is 0 827 and True when msdpCacheLifetime is non-0. 829 This object is deprecated because MSDP SA Requests were 830 removed from the MSDP specification." 831 ::= { msdpPeerEntry 24 } 833 msdpPeerStatus OBJECT-TYPE 834 SYNTAX RowStatus 835 MAX-ACCESS read-create 836 STATUS current 837 DESCRIPTION 838 "The RowStatus object by which peers can be added and 839 deleted. A transition to 'active' will cause the MSDP 840 'Enable MSDP peering with P' Event to be generated. A 841 transition out of the 'active' state will cause the MSDP 842 'Disable MSDP peering with P' Event to be generated. Care 843 should be used in providing write access to this object 844 without adequate authentication. 846 msdpPeerRemoteAddress is the only variable that must be set 847 to a valid value before the row can be activated. Since 848 this is the table's INDEX, a row can be activated by simply 849 setting the msdpPeerStatus variable. 851 It is possible to modify other columns in the same 852 conceptual row when the status value is active(1)." 853 REFERENCE "RFC 3618 section 11.1" 854 ::= { msdpPeerEntry 25 } 856 msdpPeerRemotePort OBJECT-TYPE 857 SYNTAX Integer32 (0..65535) 858 MAX-ACCESS read-only 859 STATUS current 860 DESCRIPTION 861 "The remote port for the TCP connection between the MSDP 862 peers." 863 DEFVAL { 639 } 864 ::= { msdpPeerEntry 26 } 866 msdpPeerLocalPort OBJECT-TYPE 867 SYNTAX Integer32 (0..65535) 868 MAX-ACCESS read-only 869 STATUS current 870 DESCRIPTION 871 "The local port for the TCP connection between the MSDP 872 peers." 873 DEFVAL { 639 } 874 ::= { msdpPeerEntry 27 } 876 -- msdpPeerEncapsulationState has been removed 877 -- because there is no longer an encapsulation 878 -- state machine. 879 -- ::= { msdpPeerEntry 28 } 881 msdpPeerEncapsulationType OBJECT-TYPE 882 SYNTAX INTEGER { 883 none(0), 884 tcp(1) 885 } 886 MAX-ACCESS read-create 887 STATUS current 888 DESCRIPTION 889 "The encapsulation in use when encapsulating data in SA 890 messages to this peer." 891 ::= { msdpPeerEntry 29 } 893 msdpPeerConnectionAttempts OBJECT-TYPE 894 SYNTAX Counter32 895 MAX-ACCESS read-only 896 STATUS current 897 DESCRIPTION 898 "The number of times the state machine has transitioned from 899 INACTIVE to CONNECTING." 900 ::= { msdpPeerEntry 30 } 902 msdpPeerInNotifications OBJECT-TYPE 903 SYNTAX Counter32 904 MAX-ACCESS read-only 905 STATUS deprecated 906 DESCRIPTION 907 "The number of MSDP Notification messages received from this 908 peer. 910 This object is deprecated because MSDP Notifications have 911 been removed from the spec." 912 ::= { msdpPeerEntry 31 } 914 msdpPeerOutNotifications OBJECT-TYPE 915 SYNTAX Counter32 916 MAX-ACCESS read-only 917 STATUS deprecated 918 DESCRIPTION 919 "The number of MSDP Notification messages transmitted to this 920 peer. 922 This object is deprecated because MSDP Notifications have 923 been removed from the spec." 924 ::= { msdpPeerEntry 32 } 926 msdpPeerLastError OBJECT-TYPE 927 SYNTAX OCTET STRING (SIZE (2)) 928 MAX-ACCESS read-only 929 STATUS deprecated 930 DESCRIPTION 931 "The last error code and subcode received via Notification 932 from this peer. If no error has occurred, this field is 933 zero. Otherwise, the first byte of this two byte OCTET 934 STRING contains the O-bit and error code, and the second 935 byte contains the subcode. 937 This object is deprecated because MSDP Notifications have 938 been removed from the spec." 939 DEFVAL { '0000'h } 940 ::= { msdpPeerEntry 33 } 942 msdpPeerDiscontinuityTime OBJECT-TYPE 943 SYNTAX TimeStamp 944 MAX-ACCESS read-only 945 STATUS current 946 DESCRIPTION 947 "The value of sysUpTime on the most recent occasion at which 948 one or more of this entry's counters suffered a 949 discontinuity. See the DESCRIPTION of each object to see if 950 it is expected to have discontinuities. These 951 discontinuities may occur at peer connection establishment. 953 If no such discontinuities have occurred since the last 954 reinitialization of the local management subsystem, then 955 this object contains a zero value." 956 ::= { msdpPeerEntry 34 } 958 -- 959 -- The MSDP Source-Active Cache table 960 -- 962 msdpSACacheTable OBJECT-TYPE 963 SYNTAX SEQUENCE OF MsdpSACacheEntry 964 MAX-ACCESS not-accessible 965 STATUS current 966 DESCRIPTION 967 "The (conceptual) table listing the MSDP SA advertisements 968 currently in the MSDP speaker's cache." 969 ::= { msdp 6 } 971 msdpSACacheEntry OBJECT-TYPE 972 SYNTAX MsdpSACacheEntry 973 MAX-ACCESS not-accessible 974 STATUS current 975 DESCRIPTION 976 "An entry (conceptual row) representing an MSDP SA 977 advertisement. The INDEX to this table includes 978 msdpSACacheOriginRP for diagnosing incorrect MSDP 979 advertisements; normally a Group and Source pair would be 980 unique. 982 Row creation is not permitted; msdpSACacheStatus may only be 983 used to delete rows from this table." 984 INDEX { msdpSACacheGroupAddr, msdpSACacheSourceAddr, 985 msdpSACacheOriginRP } 986 ::= { msdpSACacheTable 1 } 988 MsdpSACacheEntry ::= SEQUENCE { 989 msdpSACacheGroupAddr IpAddress, 990 msdpSACacheSourceAddr IpAddress, 991 msdpSACacheOriginRP IpAddress, 992 msdpSACachePeerLearnedFrom IpAddress, 993 msdpSACacheRPFPeer IpAddress, 994 msdpSACacheInSAs Counter32, 995 msdpSACacheInDataPackets Counter32, 996 msdpSACacheUpTime TimeTicks, 997 msdpSACacheExpiryTime TimeTicks, 998 msdpSACacheStatus RowStatus 999 } 1001 msdpSACacheGroupAddr OBJECT-TYPE 1002 SYNTAX IpAddress 1003 MAX-ACCESS not-accessible 1004 STATUS current 1005 DESCRIPTION 1006 "The group address of the SA Cache entry." 1007 ::= { msdpSACacheEntry 1 } 1009 msdpSACacheSourceAddr OBJECT-TYPE 1010 SYNTAX IpAddress 1011 MAX-ACCESS not-accessible 1012 STATUS current 1013 DESCRIPTION 1014 "The source address of the SA Cache entry." 1015 ::= { msdpSACacheEntry 2 } 1017 msdpSACacheOriginRP OBJECT-TYPE 1018 SYNTAX IpAddress 1019 MAX-ACCESS not-accessible 1020 STATUS current 1021 DESCRIPTION 1022 "The RP of the SA Cache entry. This field is in the INDEX in 1023 order to catch multiple RP's advertising the same source and 1024 group." 1025 ::= { msdpSACacheEntry 3 } 1027 msdpSACachePeerLearnedFrom OBJECT-TYPE 1028 SYNTAX IpAddress 1029 MAX-ACCESS read-only 1030 STATUS current 1031 DESCRIPTION 1032 "The peer from which this SA Cache entry was last accepted. 1033 This address must correspond to the msdpPeerRemoteAddress 1034 value for a row in the MSDP Peer Table. This should be 1035 0.0.0.0 on the router that originated the entry." 1036 ::= { msdpSACacheEntry 4 } 1038 msdpSACacheRPFPeer OBJECT-TYPE 1039 SYNTAX IpAddress 1040 MAX-ACCESS read-only 1041 STATUS current 1042 DESCRIPTION 1043 "The peer from which an SA message corresponding to this 1044 cache entry would be accepted (i.e. the RPF peer for 1045 msdpSACacheOriginRP). This may be different than 1046 msdpSACachePeerLearnedFrom if this entry was created by an 1047 MSDP SA-Response. This address must correspond to the 1048 msdpPeerRemoteAddress value for a row in the MSDP Peer 1049 Table, or may be 0.0.0.0 if no RPF peer exists." 1050 ::= { msdpSACacheEntry 5 } 1052 msdpSACacheInSAs OBJECT-TYPE 1053 SYNTAX Counter32 1054 MAX-ACCESS read-only 1055 STATUS current 1056 DESCRIPTION 1057 "The number of MSDP SA messages received relevant to this 1058 cache entry. This object must be initialized to zero when 1059 creating a cache entry." 1060 ::= { msdpSACacheEntry 6 } 1062 msdpSACacheInDataPackets OBJECT-TYPE 1063 SYNTAX Counter32 1064 MAX-ACCESS read-only 1065 STATUS current 1066 DESCRIPTION 1067 "The number of MSDP encapsulated data packets received 1068 relevant to this cache entry. This object must be 1069 initialized to zero when creating a cache entry." 1070 ::= { msdpSACacheEntry 7 } 1072 msdpSACacheUpTime OBJECT-TYPE 1073 SYNTAX TimeTicks 1074 MAX-ACCESS read-only 1075 STATUS current 1076 DESCRIPTION 1077 "The time since this entry was first placed in the SA cache. 1079 The first epoch is the time that the entry was first placed 1080 in the SA cache, and the second epoch is the current time." 1081 ::= { msdpSACacheEntry 8 } 1083 msdpSACacheExpiryTime OBJECT-TYPE 1084 SYNTAX TimeTicks 1085 MAX-ACCESS read-only 1086 STATUS current 1087 DESCRIPTION 1088 "The time remaining before this entry will expire from the SA 1089 cache. 1091 The first epoch is now, and the second epoch is the time 1092 that the entry will expire." 1093 ::= { msdpSACacheEntry 9 } 1095 msdpSACacheStatus OBJECT-TYPE 1096 SYNTAX RowStatus 1097 MAX-ACCESS read-write 1098 STATUS current 1099 DESCRIPTION 1100 "The status of this row in the table. The only allowable 1101 actions are to retrieve the status, which will be `active', 1102 or to set the status to `destroy' in order to remove this 1103 entry from the cache. 1105 Row creation is not permitted. 1107 No columnar objects are writable, so there are none that may 1108 be changed while the status value is active(1). " 1109 ::= { msdpSACacheEntry 10 } 1111 -- 1112 -- MSDP Mesh Group Membership table 1113 -- 1115 msdpMeshGroupTable OBJECT-TYPE 1116 SYNTAX SEQUENCE OF MsdpMeshGroupEntry 1117 MAX-ACCESS not-accessible 1118 STATUS current 1119 DESCRIPTION 1120 "The (conceptual) table listing MSDP Mesh Group 1121 configuration." 1122 ::= { msdp 12 } 1124 msdpMeshGroupEntry OBJECT-TYPE 1125 SYNTAX MsdpMeshGroupEntry 1126 MAX-ACCESS not-accessible 1127 STATUS current 1128 DESCRIPTION 1129 "An entry (conceptual row) repesenting a peer in an MSDP Mesh 1130 Group. 1132 If row creation is supported, dynamically added rows are 1133 added to the system's stable configuration (corresponding to 1134 a StorageType value of nonVolatile). " 1135 INDEX { msdpMeshGroupName, msdpMeshGroupPeerAddress } 1136 ::= { msdpMeshGroupTable 1 } 1138 MsdpMeshGroupEntry ::= SEQUENCE { 1139 msdpMeshGroupName DisplayString, 1140 msdpMeshGroupPeerAddress IpAddress, 1141 msdpMeshGroupStatus RowStatus 1142 } 1144 msdpMeshGroupName OBJECT-TYPE 1145 SYNTAX DisplayString (SIZE(1..64)) 1146 MAX-ACCESS not-accessible 1147 STATUS current 1148 DESCRIPTION 1149 "The name of the mesh group." 1150 ::= { msdpMeshGroupEntry 1 } 1152 msdpMeshGroupPeerAddress OBJECT-TYPE 1153 SYNTAX IpAddress 1154 MAX-ACCESS not-accessible 1155 STATUS current 1156 DESCRIPTION 1157 "A peer address that is a member of the mesh group with name 1158 msdpMeshGroupName. The msdpMeshGroupPeerAddress must match 1159 a row in the msdpPeerTable." 1160 ::= { msdpMeshGroupEntry 2 } 1162 msdpMeshGroupStatus OBJECT-TYPE 1163 SYNTAX RowStatus 1164 MAX-ACCESS read-create 1165 STATUS current 1166 DESCRIPTION 1167 "This entry's status, by which new entries may be added to 1168 the table and old entries deleted. 1170 msdpMeshGroupName and msdpMeshGroupPeerAddress must be set 1171 to valid values before the row can be activated. Since 1172 these are the table's INDEX, a row can be activated by 1173 simply setting the msdpMeshGroupStatus variable. 1175 It is not possible to modify other columns in the same 1176 conceptual row when the status value is active(1), because 1177 there only other objects in the row are part of the INDEX. 1178 Changing one of these changes the row, so an old row must be 1179 deleted and a new one created. " 1180 ::= { msdpMeshGroupEntry 3 } 1182 -- Traps 1184 msdpTraps OBJECT IDENTIFIER ::= { msdp 0 } 1186 msdpEstablished NOTIFICATION-TYPE 1187 OBJECTS { msdpPeerFsmEstablishedTransitions } 1188 STATUS current 1189 DESCRIPTION 1190 "The MSDP Established event is generated when the MSDP FSM 1191 enters the ESTABLISHED state." 1192 ::= { msdpTraps 1 } 1194 msdpBackwardTransition NOTIFICATION-TYPE 1195 OBJECTS { msdpPeerState } 1196 STATUS current 1197 DESCRIPTION 1198 "The MSDPBackwardTransition Event is generated when the MSDP 1199 FSM moves from a higher numbered state to a lower numbered 1200 state." 1201 ::= { msdpTraps 2 } 1203 -- conformance information 1205 msdpMIBConformance OBJECT IDENTIFIER ::= { msdp 8 } 1206 msdpMIBCompliances OBJECT IDENTIFIER ::= { msdpMIBConformance 1 } 1207 msdpMIBGroups OBJECT IDENTIFIER ::= { msdpMIBConformance 2 } 1209 -- compliance statements 1211 msdpMIBCompliance MODULE-COMPLIANCE 1212 STATUS deprecated 1213 DESCRIPTION 1214 "The compliance statement for entities which implement a pre- 1215 RFC version of MSDP. This statement is deprecated because 1216 it includes objects used for managing/monitoring aspects of 1217 MSDP that were removed before it was published as an RFC." 1218 MODULE -- this module 1219 MANDATORY-GROUPS { msdpMIBGlobalsGroup, msdpMIBPeerGroup, 1220 msdpMIBNotificationGroup } 1222 GROUP msdpMIBEncapsulationGroup 1223 DESCRIPTION 1224 "This group is mandatory if MSDP encapsulation interfaces are 1225 not given their own interface index numbers." 1226 GROUP msdpMIBSACacheGroup 1227 DESCRIPTION 1228 "This group is mandatory if the MSDP speaker has the ability 1229 to cache SA messages." 1230 GROUP msdpMIBRequestsGroup 1231 DESCRIPTION 1232 "This group is mandatory if the MSDP speaker has the ability 1233 to send SA-Request messages and parse SA-Response 1234 messages." 1235 GROUP msdpMIBRPGroup 1236 DESCRIPTION 1237 "This group is mandatory if the MSDP speaker sources (as 1238 opposed to forwards) MSDP messages." 1239 GROUP msdpMIBMeshGroupGroup 1240 DESCRIPTION 1241 "This group is mandatory if the MSDP speaker can participate 1242 in MSDP Mesh Groups." 1244 ::= { msdpMIBCompliances 1 } 1246 msdpMIBFullCompliance MODULE-COMPLIANCE 1247 STATUS current 1248 DESCRIPTION 1249 "The compliance statement for entities which implement MSDP 1250 (RFC3618)." 1251 MODULE -- this module 1252 MANDATORY-GROUPS { msdpMIBGlobalsGroup, msdpMIBPeerGroup2, 1253 msdpMIBSACacheGroup, msdpMIBEncapsulationGroup } 1254 GROUP msdpMIBRPGroup 1255 DESCRIPTION 1256 "This group is mandatory if the MSDP speaker sources (as 1257 opposed to forwards) MSDP messages." 1258 GROUP msdpMIBMeshGroupGroup 1259 DESCRIPTION 1260 "This group is mandatory if the MSDP speaker can participate 1261 in MSDP Mesh Groups." 1262 ::= { msdpMIBCompliances 2 } 1264 msdpMIBReadOnlyCompliance MODULE-COMPLIANCE 1265 STATUS current 1266 DESCRIPTION 1267 "The compliance statement for entities which implement MSDP 1268 (RFC3618), but do not permit configuration (or only permit 1269 partial configuration) via SNMP." 1270 MODULE -- this module 1271 MANDATORY-GROUPS { msdpMIBGlobalsGroup, msdpMIBPeerGroup2, 1272 msdpMIBSACacheGroup, msdpMIBEncapsulationGroup } 1273 GROUP msdpMIBRPGroup 1274 DESCRIPTION 1275 "This group is mandatory if the MSDP speaker sources (as 1276 opposed to forwards) MSDP messages." 1277 GROUP msdpMIBMeshGroupGroup 1278 DESCRIPTION 1279 "This group is mandatory if the MSDP speaker can participate 1280 in MSDP Mesh Groups." 1281 OBJECT msdpEnabled 1282 MIN-ACCESS read-only 1283 DESCRIPTION 1284 "Write access is not required." 1285 OBJECT msdpCacheLifetime 1286 MIN-ACCESS read-only 1287 DESCRIPTION 1288 "Write access is not required." 1289 OBJECT msdpPeerLocalAddress 1290 MIN-ACCESS read-only 1291 DESCRIPTION 1292 "Write access is not required." 1293 OBJECT msdpPeerConnectRetryInterval 1294 MIN-ACCESS read-only 1295 DESCRIPTION 1296 "Write access is not required." 1297 OBJECT msdpPeerHoldTimeConfigured 1298 MIN-ACCESS read-only 1299 DESCRIPTION 1300 "Write access is not required." 1301 OBJECT msdpPeerKeepAliveConfigured 1302 MIN-ACCESS read-only 1303 DESCRIPTION 1304 "Write access is not required." 1305 OBJECT msdpPeerDataTtl 1306 MIN-ACCESS read-only 1307 DESCRIPTION 1308 "Write access is not required." 1309 OBJECT msdpPeerStatus 1310 MIN-ACCESS read-only 1311 DESCRIPTION 1312 "Write access is not required." 1313 OBJECT msdpPeerEncapsulationType 1314 MIN-ACCESS read-only 1315 DESCRIPTION 1316 "Write access is not required." 1317 OBJECT msdpSACacheStatus 1318 MIN-ACCESS read-only 1319 DESCRIPTION 1320 "Write access is not required." 1321 OBJECT msdpRPAddress 1322 MIN-ACCESS read-only 1323 DESCRIPTION 1324 "Write access is not required." 1325 OBJECT msdpMeshGroupStatus 1326 MIN-ACCESS read-only 1327 DESCRIPTION 1328 "Write access is not required." 1329 ::= { msdpMIBCompliances 3 } 1331 -- units of conformance 1333 msdpMIBGlobalsGroup OBJECT-GROUP 1334 OBJECTS { msdpEnabled } 1335 STATUS current 1336 DESCRIPTION 1337 "A collection of objects providing information on global MSDP 1338 state." 1339 ::= { msdpMIBGroups 1 } 1341 msdpMIBPeerGroup OBJECT-GROUP 1342 OBJECTS { msdpPeerRPFFailures, 1343 msdpPeerState, msdpPeerInSAs, msdpPeerOutSAs, 1344 msdpPeerInSARequests, msdpPeerOutSARequests, 1345 msdpPeerInSAResponses, msdpPeerOutSAResponses, 1346 msdpPeerInNotifications, msdpPeerOutNotifications, 1347 msdpPeerInControlMessages, msdpPeerOutControlMessages, 1348 msdpPeerFsmEstablishedTransitions, 1349 msdpPeerFsmEstablishedTime, 1350 msdpPeerLocalAddress, 1351 msdpPeerRemotePort, msdpPeerLocalPort, 1352 msdpPeerConnectRetryInterval, 1353 msdpPeerHoldTimeConfigured, 1354 msdpPeerKeepAliveConfigured, 1355 msdpPeerInMessageTime, 1356 msdpPeerProcessRequestsFrom, 1357 msdpPeerConnectionAttempts, 1358 msdpPeerLastError, 1359 msdpPeerStatus, 1360 msdpPeerDiscontinuityTime 1361 } 1362 STATUS deprecated 1363 DESCRIPTION 1364 "A collection of objects for managing MSDP peers. This group 1365 is deprecated in favor of msdpMIBPeerGroup2 because it 1366 contains objects for managing aspects of MSDP that were 1367 removed before it was published as an RFC." 1368 ::= { msdpMIBGroups 2 } 1370 msdpMIBEncapsulationGroup OBJECT-GROUP 1371 OBJECTS { msdpPeerInDataPackets, msdpPeerOutDataPackets, 1372 msdpPeerDataTtl, 1373 msdpPeerEncapsulationType 1374 } 1375 STATUS current 1376 DESCRIPTION 1377 "A collection of objects for managing encapsulations if the 1378 MSDP encapsulation interfaces are not given interface 1379 indices." 1380 ::= { msdpMIBGroups 3 } 1382 msdpMIBSACacheGroup OBJECT-GROUP 1383 OBJECTS { msdpCacheLifetime, msdpNumSACacheEntries, 1384 msdpSACachePeerLearnedFrom, 1385 msdpSACacheRPFPeer, msdpSACacheInSAs, 1386 msdpSACacheInDataPackets, 1387 msdpSACacheUpTime, msdpSACacheExpiryTime, 1388 msdpSACacheStatus } 1390 STATUS current 1391 DESCRIPTION 1392 "A collection of objects for managing MSDP SA cache entries." 1393 ::= { msdpMIBGroups 4 } 1395 msdpMIBNotificationGroup NOTIFICATION-GROUP 1396 NOTIFICATIONS { msdpEstablished, 1397 msdpBackwardTransition } 1398 STATUS current 1399 DESCRIPTION 1400 "A collection of notifications for signaling changes in MSDP 1401 peer relationships." 1402 ::= { msdpMIBGroups 5 } 1404 msdpMIBRequestsGroup OBJECT-GROUP 1405 OBJECTS { msdpRequestsPeer, msdpRequestsStatus } 1406 STATUS deprecated 1407 DESCRIPTION 1408 "A collection of objects for managing MSDP Request 1409 transmission. This group is deprecated because Requests 1410 were removed from MSDP before its publication as RFC." 1411 ::= { msdpMIBGroups 6 } 1413 msdpMIBRPGroup OBJECT-GROUP 1414 OBJECTS { msdpRPAddress } 1415 STATUS current 1416 DESCRIPTION 1417 "A collection of objects for MSDP speakers that source MSDP 1418 messages." 1419 ::= { msdpMIBGroups 7 } 1421 msdpMIBMeshGroupGroup OBJECT-GROUP 1422 OBJECTS { msdpMeshGroupStatus } 1423 STATUS current 1424 DESCRIPTION 1425 "A collection of objects for MSDP speakers that can 1426 participate in MSDP mesh groups." 1427 ::= { msdpMIBGroups 8 } 1429 msdpMIBPeerGroup2 OBJECT-GROUP 1430 OBJECTS { msdpPeerRPFFailures, 1431 msdpPeerState, msdpPeerInSAs, msdpPeerOutSAs, 1432 msdpPeerInSARequests, msdpPeerOutSARequests, 1433 msdpPeerInControlMessages, msdpPeerOutControlMessages, 1434 msdpPeerFsmEstablishedTransitions, 1435 msdpPeerFsmEstablishedTime, 1436 msdpPeerLocalAddress, 1437 msdpPeerRemotePort, msdpPeerLocalPort, 1438 msdpPeerConnectRetryInterval, 1439 msdpPeerHoldTimeConfigured, 1440 msdpPeerKeepAliveConfigured, 1441 msdpPeerInMessageTime, 1442 msdpPeerConnectionAttempts, 1443 msdpPeerStatus, 1444 msdpPeerDiscontinuityTime 1445 } 1446 STATUS current 1447 DESCRIPTION 1448 "A collection of objects for managing MSDP peers." 1449 ::= { msdpMIBGroups 9 } 1451 END 1453 5. Security Considerations 1455 There are a number of management objects defined in this MIB that have a 1456 MAX-ACCESS clause of read-write and/or read-create. Such objects may be 1457 considered sensitive or vulnerable in some network environments. The 1458 support for SET operations in a non-secure environment without proper 1459 protection can have a negative effect on network operations. 1461 There are a number of managed objects in this MIB that may contain 1462 sensitive information. These are: 1464 o The entire msdpPeerTable. Peer information can result in 1465 discovering internal topology, which many want to keep secret. 1467 o msdpNumSACacheEntries. The size of the SA Cache could reveal 1468 whether this system has MSDP entries for public and/or private 1469 groups. 1471 o The entire msdpSACacheTable. The active sources and groups in a 1472 network could be private. 1474 o The entire msdpMeshGroupTable. This information can also lead to 1475 internal topology information. 1477 It is thus important to control even GET access to these objects and 1478 possibly to even encrypt the values of these object when sending them 1479 over the network via SNMP. Not all versions of SNMP provide features 1480 for such a secure environment. 1482 SNMPv1 by itself is not a secure environment. Even if the network 1483 itself is secure (for example by using IPSec), even then, there is no 1484 control as to who on the secure network is allowed to access and GET/SET 1485 (read/change/create/delete) the objects in this MIB. 1487 It is recommended that the implementers consider the security features 1488 as provided by the SNMPv3 framework. Specifically, the use of the User- 1489 based Security Model RFC 3414 [2] and the View-based Access Control 1490 Model RFC 3415 [3] is recommended. 1492 It is then a customer/user responsibility to ensure that the SNMP entity 1493 giving access to an instance of this MIB, is properly configured to give 1494 access to the objects only to those principals (users) that have 1495 legitimate rights to indeed GET or SET (change/create/delete) them. 1497 6. IANA Considerations 1499 Since this MIB is for an experimental protocol, it uses an experimental 1500 OID. 1502 Decimal Name Description References 1503 ------- ---- ----------- ---------- 1504 92 MSDP-MIB Multicast Source Discovery MIB [Fenner] 1506 The IANA is requested to change the Reference for this entry to point to 1507 this document. 1509 7. Acknowledgements 1511 Tom Pusateri and Billy Ng both provided valuable input on early versions 1512 of this draft. It was completed based upon feedback from Mike Davison 1513 and Ketan Talaulikar. Lucy Lynch provided a desperately-needed reminder 1514 to finish this document. 1516 8. Authors' Addresses 1517 Bill Fenner 1518 75 Willow Road 1519 Menlo Park, CA 94025 1520 Phone: +1 650 867 6073 1521 EMail: fenner@research.att.com 1523 Dave Thaler 1524 Microsoft Corporation 1525 One Microsoft Way 1526 Redmond, WA 98052-6399 1527 Phone: +1 425 703 8835 1528 EMail: dthaler@microsoft.com 1530 9. Normative References 1532 [1] Fenner, B. and D. Meyer, editors, "Multicast Source Discovery 1533 Protocol (MSDP)", RFC 3618, October 2003. 1535 [2] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for 1536 version 3 of the Simple Network Management Protocol (SNMPv3)", STD 1537 62, RFC 3414, December 2002. 1539 [3] Wijnen, B., Preshun, R. and K. McCloghrie, "View-based Access 1540 Control Model (VACM) for the Simple Network Management Protocol 1541 (SNMP)", STD 62, RFC 3415, December 2002. 1543 [4] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1544 and S. Waldbusser, "Structure of Management Information Version 2 1545 (SMIv2)", STD 58, RFC 2578, April 1999. 1547 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1548 and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 1549 2579, April 1999. 1551 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., 1552 and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 1553 2580, April 1999. 1555 9.1. Informative References 1557 [7] Case, J., Mundy, R., Partain, D. and B. Stewart, "Introduction and 1558 Applicability Statements for Internet-Standard Management 1559 Framework", RFC 3410, December 2002. 1561 10. Full Copyright Statement 1563 Copyright (C) The Internet Society (2005). This document is subject to 1564 the rights, licenses and restrictions contained in BCP 78, and except as 1565 set forth therein, the authors retain all their rights. 1567 This document and the information contained herein are provided on an 1568 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR 1569 IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 1570 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 1571 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 1572 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1573 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1575 The IETF takes no position regarding the validity or scope of any 1576 Intellectual Property Rights or other rights that might be claimed to 1577 pertain to the implementation or use of the technology described in this 1578 document or the extent to which any license under such rights might or 1579 might not be available; nor does it represent that it has made any 1580 independent effort to identify any such rights. Information on the 1581 procedures with respect to rights in RFC documents can be found in BCP 1582 78 and BCP 79. 1584 Copies of IPR disclosures made to the IETF Secretariat and any 1585 assurances of licenses to be made available, or the result of an attempt 1586 made to obtain a general license or permission for the use of such 1587 proprietary rights by implementers or users of this specification can be 1588 obtained from the IETF on-line IPR repository at 1589 http://www.ietf.org/ipr. 1591 The IETF invites any interested party to bring to its attention any 1592 copyrights, patents or patent applications, or other proprietary rights 1593 that may cover technology that may be required to implement this 1594 standard. Please address the information to the IETF at ietf- 1595 ipr@ietf.org.