idnits 2.17.00 (12 Aug 2021) /tmp/idnits64909/draft-ietf-pim-mib-v2-01.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? == 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 is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- -- 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 (May 2003) is 6945 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) == Unused Reference: '20' is defined on line 1468, but no explicit reference was found in the text == Unused Reference: '21' is defined on line 1471, but no explicit reference was found in the text == Unused Reference: '22' is defined on line 1475, 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 2362 (ref. '18') (Obsoleted by RFC 4601, RFC 5059) == Outdated reference: draft-ietf-pim-dm-new-v2 has been published as RFC 3973 ** Downref: Normative reference to an Experimental draft: draft-ietf-pim-dm-new-v2 (ref. '19') ** Obsolete normative reference: RFC 2932 (ref. '20') (Obsoleted by RFC 5132) == Outdated reference: draft-ietf-pim-sm-v2-new has been published as RFC 4601 ** Downref: Normative reference to an Experimental RFC: RFC 2934 (ref. '22') Summary: 19 errors (**), 0 flaws (~~), 6 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Internet Engineering Task Force PIM-WG 2 INTERNET-DRAFT Editor 3 draft-ietf-pim-mib-v2-01.txt Jonathan Nicholas 4 ITT A/CD 5 November 2002 6 Expires May 2003 8 Protocol Independent Multicast MIB 10 Status of this Document 12 This document is an Internet-Draft and is in full conformance with all 13 provisions of Section 10 of RFC2026. 15 Internet-Drafts are working documents of the Internet Engineering Task 16 Force (IETF), its areas, and its working groups. Note that other groups 17 may also distribute working documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet- Drafts as reference material 22 or to cite them other than as "work in progress." 24 The list of current Internet-Drafts can be accessed at 25 http://www.ietf.org/ietf/1id-abstracts.txt 27 The list of Internet-Draft Shadow Directories can be accessed at 28 http://www.ietf.org/shadow.html. 30 This document is a product of the IETF PIM WG. Comments should be 31 addressed to the authors, or the WG's mailing list at 32 pim@catarina.usc.edu. 34 Abstract 36 This memo defines a portion of the Management Information Base (MIB) for 37 use with network management protocols in the Internet community. In 38 particular, it describes managed objects used for managing the Protocol 39 Independent Multicast (PIM) protocol. 41 Table of Contents 43 1 Introduction ................................................. 2 44 2 The SNMP Network Management Framework ........................ 2 45 3 Overview ..................................................... 3 46 4 Definitions .................................................. 4 47 5 Security Considerations ...................................... 29 48 6 Acknowledgements ............................................. 30 49 7 Authors' Addresses ........................................... 30 50 8 References ................................................... 30 52 1. Introduction 54 This memo defines a portion of the Management Information Base (MIB) for 55 use with network management protocols in the Internet community. In 56 particular, it describes managed objects used for managing the Protocol 57 Independent Multicast (PIM) protocol [18,19]. 59 2. The SNMP Network Management Framework 61 The SNMP Management Framework presently consists of five major 62 components: 64 * An overall architecture, described in RFC 2571 [1]. 66 * Mechanisms for describing and naming objects and events for the 67 purpose of management. The first version of this Structure of 68 Management Information (SMI) is called SMIv1 and described in STD 16, 69 RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The second 70 version, called SMIv2, is described in STD 58, RFC 2578 [5], STD 58, 71 RFC 2579 [6] and STD 58, RFC 2580 [7]. 73 * Message protocols for transferring management information. The first 74 version of the SNMP message protocol is called SNMPv1 and described 75 in STD 15, RFC 1157 [8]. A second version of the SNMP message 76 protocol, which is not an Internet standards track protocol, is called 77 SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. The third 78 version of the message protocol is called SNMPv3 and described in 79 RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12]. 81 * Protocol operations for accessing management information. The first 82 set of protocol operations and associated PDU formats is described in 83 STD 15, RFC 1157 [8]. A second set of protocol operations and 84 associated PDU formats is described in RFC 1905 [13]. 86 * A set of fundamental applications described in RFC 2573 [14] and the 87 view-based access control mechanism described in RFC 2575 [15]. 89 Managed objects are accessed via a virtual information store, termed the 90 Management Information Base or MIB. Objects in the MIB are defined 91 using the mechanisms defined in the SMI. 93 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 94 conforming to the SMIv1 can be produced through the appropriate 95 translations. The resulting translated MIB must be semantically 96 equivalent, except where objects or events are omitted because no 97 translation is possible (use of Counter64). Some machine readable 98 information in SMIv2 will be converted into textual descriptions in 99 SMIv1 during the translation process. However, this loss of machine 100 readable information is not considered to change the semantics of the 101 MIB. 103 3. Overview 105 This MIB module contains one scalar and eight tables. Some of the 106 objects in these tables are deprecated. This MIB contains deprecated 107 objects since they are necessary for managing PIMv1 routers, but PIMv1 108 itself is obsoleted by PIM v2 [18,19]. 110 The tables contained in this MIB are: 112 (1) The PIM Interface Table contains one row for each of the 113 router's PIM interfaces. 115 (2) The PIM Neighbor Table contains one row for each of the router's 116 PIM neighbors. 118 (3) The PIM IP Multicast Route Table contains one row for each 119 multicast routing entry whose incoming interface is running PIM. 121 (4) The PIM Next Hop Table which contains one row for each outgoing 122 interface list entry in the multicast routing table whose 123 interface is running PIM, and whose state is pruned. 125 (5) The (deprecated) PIM RP Table contains the PIM (version 1) 126 information for IP multicast groups which is common to all RPs 127 of a group. 129 (6) The PIM RP-Set Table contains the PIM (version 2) information 130 for sets of candidate Rendezvous Points (RPs) for IP multicast 131 group addresses with particular address prefixes. 133 (7) The PIM Candidate-RP Table contains the IP multicast groups for 134 which the local router is to advertise itself as a Candidate-RP. 135 If this table is empty, then the local router advertises itself 136 as a Candidate-RP for all groups. 138 (8) The PIM Component Table contains one row for each of the PIM 139 domains to which the router is connected. 141 4. Definitions 143 PIM-MIB DEFINITIONS ::= BEGIN 145 IMPORTS 146 MODULE-IDENTITY, OBJECT-TYPE, experimental, 147 NOTIFICATION-TYPE, 148 Integer32, IpAddress, TimeTicks FROM SNMPv2-SMI 149 RowStatus, TruthValue FROM SNMPv2-TC 150 MODULE-COMPLIANCE, OBJECT-GROUP, 151 NOTIFICATION-GROUP FROM SNMPv2-CONF 152 ipMRouteGroup, ipMRouteSource, 153 ipMRouteSourceMask, ipMRouteNextHopGroup, 154 ipMRouteNextHopSource, ipMRouteNextHopSourceMask, 155 ipMRouteNextHopIfIndex, 156 ipMRouteNextHopAddress FROM IPMROUTE-STD-MIB 157 InterfaceIndex FROM IF-MIB; 159 pimMIB MODULE-IDENTITY 160 LAST-UPDATED "200210280000Z" -- October 28, 2002 161 ORGANIZATION "IETF PIM Working Group." 162 CONTACT-INFO 163 " Jonathan Nicholas 164 ITT Industries 165 Aerospace/Communications Division 166 100 Kingsland Rd 167 Clifton, NJ 07014 169 Phone: +1 973 284 2019 170 EMail: jonathan.nicholas@itt.com" 171 DESCRIPTION 172 "The MIB module for management of PIM routers." 173 REVISION "200009280000Z" -- September 28, 2000 174 DESCRIPTION 175 "Initial version, published as RFC 2934." 176 REVISION "200210280000Z" -- October 28, 2002 177 DESCRIPTION 178 "Revised November 4, 2002." 179 ::= { experimental 61 } 181 pimMIBObjects OBJECT IDENTIFIER ::= { pimMIB 1 } 183 pimTraps OBJECT IDENTIFIER ::= { pimMIBObjects 0 } 185 pim OBJECT IDENTIFIER ::= { pimMIBObjects 1 } 186 pimJoinPruneInterval OBJECT-TYPE 187 SYNTAX Integer32 188 UNITS "seconds" 189 MAX-ACCESS read-write 190 STATUS current 191 DESCRIPTION 192 "The default interval at which periodic PIM-SM Join/Prune 193 messages are to be sent." 194 DEFVAL { 60 } 195 ::= { pim 1 } 197 -- The PIM Interface Table 199 pimInterfaceTable OBJECT-TYPE 200 SYNTAX SEQUENCE OF PimInterfaceEntry 201 MAX-ACCESS not-accessible 202 STATUS current 203 DESCRIPTION 204 "The (conceptual) table listing the router's PIM interfaces. 205 IGMP and PIM are enabled on all interfaces listed in this 206 table." 207 ::= { pim 2 } 209 pimInterfaceEntry OBJECT-TYPE 210 SYNTAX PimInterfaceEntry 211 MAX-ACCESS not-accessible 212 STATUS current 213 DESCRIPTION 214 "An entry (conceptual row) in the pimInterfaceTable." 215 INDEX { pimInterfaceIfIndex } 216 ::= { pimInterfaceTable 1 } 218 PimInterfaceEntry ::= SEQUENCE { 219 pimInterfaceIfIndex InterfaceIndex, 220 pimInterfaceAddress IpAddress, 221 pimInterfaceNetMask IpAddress, 222 pimInterfaceMode INTEGER, 223 pimInterfaceDR IpAddress, 224 pimInterfaceHelloInterval Integer32, 225 pimInterfaceStatus RowStatus, 226 pimInterfaceJoinPruneInterval Integer32, 227 pimInterfaceCBSRPreference Integer32, 228 pimInterfaceTrigHelloInterval Integer32, 229 pimInterfaceHelloHoldtime Integer32, 230 pimInterfaceLanPruneDelay BITS, 231 pimInterfacePropagationDelay Integer32, 232 pimInterfaceOverrideInterval Integer32, 233 pimInterfaceGenerationID BITS, 234 pimInterfaceJoinPruneHoldtime Integer32, 235 pimInterfaceGraftRetryInterval Integer32, 236 pimInterfaceMaxGraftRetries Integer32, 237 pimInterfaceSRTTLThreshold Integer32, 238 pimInterfaceLanDelayEnabled TruthValue, 239 pimInterfaceSRCapable TruthValue, 240 pimInterfaceDRPriority Integer32 241 } 243 pimInterfaceIfIndex OBJECT-TYPE 244 SYNTAX InterfaceIndex 245 MAX-ACCESS not-accessible 246 STATUS current 247 DESCRIPTION 248 "The ifIndex value of this PIM interface." 249 ::= { pimInterfaceEntry 1 } 251 pimInterfaceAddress OBJECT-TYPE 252 SYNTAX IpAddress 253 MAX-ACCESS read-only 254 STATUS current 255 DESCRIPTION 256 "The IP address of the PIM interface." 257 ::= { pimInterfaceEntry 2 } 259 pimInterfaceNetMask OBJECT-TYPE 260 SYNTAX IpAddress 261 MAX-ACCESS read-only 262 STATUS current 263 DESCRIPTION 264 "The network mask for the IP address of the PIM interface." 265 ::= { pimInterfaceEntry 3 } 267 pimInterfaceMode OBJECT-TYPE 268 SYNTAX INTEGER { dense(1), sparse(2), sparseDense(3) } 269 MAX-ACCESS read-create 270 STATUS current 271 DESCRIPTION 272 "The configured mode of this PIM interface. A value of 273 sparseDense is only valid for PIMv1." 274 DEFVAL { dense } 275 ::= { pimInterfaceEntry 4 } 277 pimInterfaceDR OBJECT-TYPE 278 SYNTAX IpAddress 279 MAX-ACCESS read-only 280 STATUS current 281 DESCRIPTION 282 "The Designated Router on this PIM interface." 283 ::= { pimInterfaceEntry 5 } 285 pimInterfaceHelloInterval OBJECT-TYPE 286 SYNTAX Integer32 287 UNITS "seconds" 288 MAX-ACCESS read-create 289 STATUS current 290 DESCRIPTION 291 "The frequency at which PIM Hello messages are transmitted 292 on this interface." 293 DEFVAL { 30 } 294 ::= { pimInterfaceEntry 6 } 296 pimInterfaceStatus OBJECT-TYPE 297 SYNTAX RowStatus 298 MAX-ACCESS read-create 299 STATUS current 300 DESCRIPTION 301 "The status of this entry. Creating the entry enables PIM 302 on the interface; destroying the entry disables PIM on the 303 interface." 304 ::= { pimInterfaceEntry 7 } 306 pimInterfaceJoinPruneInterval OBJECT-TYPE 307 SYNTAX Integer32 308 UNITS "seconds" 309 MAX-ACCESS read-create 310 STATUS current 311 DESCRIPTION 312 "The frequency at which PIM Join/Prune messages are 313 transmitted on this PIM interface. The default value of 314 this object is the pimJoinPruneInterval." 315 ::= { pimInterfaceEntry 8 } 317 pimInterfaceCBSRPreference OBJECT-TYPE 318 SYNTAX Integer32 (-1..255) 319 MAX-ACCESS read-create 320 STATUS current 321 DESCRIPTION 322 "The preference value for the local interface as a candidate 323 bootstrap router. The value of -1 is used to indicate that 324 the local interface is not a candidate BSR interface." 325 DEFVAL { 0 } 326 ::= { pimInterfaceEntry 9 } 328 pimInterfaceTrigHelloInterval OBJECT-TYPE 329 SYNTAX Integer32 330 UNITS "seconds" 331 MAX-ACCESS read-create 332 STATUS current 333 DESCRIPTION "The maximum time before a triggered PIM Hello message 334 is transmitted on this interface." 335 DEFVAL { 5 } 336 ::= { pimInterfaceEntry 10 } 338 pimInterfaceHelloHoldtime OBJECT-TYPE 339 SYNTAX Integer32 (0..65535) 340 UNITS "seconds" 341 MAX-ACCESS read-create 342 STATUS current 343 DESCRIPTION "The value set in the Holdtime field of Hello messages 344 transmitted on this interface. This should be 3.5 345 times the value of pimInterfaceHelloInterval." 346 DEFVAL { 105 } 347 ::= { pimInterfaceEntry 11 } 349 pimInterfaceLanPruneDelay OBJECT-TYPE 350 SYNTAX BITS { off (0), on (1) } 351 MAX-ACCESS read-create 352 STATUS current 353 DESCRIPTION "Turns the LAN Prune Delay Option off and on on this 354 interface." 355 DEFVAL { on } 356 ::= { pimInterfaceEntry 12 } 358 pimInterfacePropagationDelay OBJECT-TYPE 359 SYNTAX Integer32 (0..32767) 360 UNITS "milliseconds" 361 MAX-ACCESS read-create 362 STATUS current 363 DESCRIPTION "The value inserted into the LAN Prune Delay field of a 364 LAN Prune Delay option on this interface." 365 DEFVAL { 500 } 366 ::= { pimInterfaceEntry 13 } 368 pimInterfaceOverrideInterval OBJECT-TYPE 369 SYNTAX Integer32 (0..65535) 370 MAX-ACCESS read-create 371 STATUS current 372 DESCRIPTION "The value inserted into the Override Interval field of 373 a LAN Prune Delay option on this interface." 374 DEFVAL { 2500 } 375 ::= { pimInterfaceEntry 14 } 377 pimInterfaceGenerationID OBJECT-TYPE 378 SYNTAX BITS { off (0), on (1) } 379 MAX-ACCESS read-create 380 STATUS current 381 DESCRIPTION "Turns the Generation ID Option off and on on this 382 interface." 383 DEFVAL { off } 384 ::= { pimInterfaceEntry 15 } 386 pimInterfaceJoinPruneHoldtime OBJECT_TYPE 387 SYNTAX Integer32 (0..65535) 388 UNITS "seconds" 389 MAX-ACCESS read-create 390 STATUS current 391 DESCRIPTION "The value inserted into the Holdtime field of a Join/ 392 Prune message sent on this interface. The value should 393 be 3.5 times pimInterfaceJoinPruneInterval." 394 DEFVAL { 210 } 395 ::= { pimInterfaceEntry 16 } 397 pimInterfaceGraftRetryInterval OBJECT-TYPE 398 SYNTAX Integer32 399 UNITS "seconds" 400 MAX-ACCESS read-create 401 STATUS current 402 DESCRIPTION "The interval a PIM router waits for a Graft Ack before 403 resending a Graft on this interface." 404 DEFVAL { 3 } 405 ::= { pimInterfaceEntry 17 } 407 pimInterfaceMaxGraftRetries OBJECT-TYPE 408 SYNTAX Integer32 409 MAX-ACCESS read-create 410 STATUS current 411 DESCRIPTION "The maximum number of times this router will resend a 412 Graft on this interface." 413 DEFVAL { 2 } 414 ::= { pimInterfaceEntry 18 } 416 pimInterfaceSRTTLThreshold OBJECT-TYPE 417 SYNTAX Integer32 418 MAX-ACCESS read-create 419 STATUS current 420 DESCRIPTION "The Time To Live in a PIM-DM State Refresh message at 421 which it is not forwarded on this interface." 422 DEFVAL { 0 } 423 ::= { pimInterfaceEntry 19 } 425 pimInterfaceLanDelayEnabled OBJECT-TYPE 426 SYNTAX TruthValue 427 MAX-ACCESS read-only 428 STATUS current 429 DESCRIPTION "Evaluates to TRUE if all routers on this interface are 430 using the LAN Prune Delay Option." 431 ::= { pimInterfaceEntry 20 } 433 pimInterfaceSRCapable OBJECT-TYPE 434 SYNTAX TruthValue 435 MAX-ACCESS read-only 436 STATUS current 437 DESCRIPTION "Evaluates to TRUE if all routers on this interface are 438 using the State Refresh Capable Option." 439 ::= { pimInterfaceEntry 21 } 441 pimInterfaceDRPriority OBJECT-TYPE 442 SYNTAX Integer32 443 MAX-ACCESS read-create 444 STATUS current 445 DESCRIPTION "The Designater Router Priority inserted into the DR 446 priority option on this interface." 447 DEFVAL { 1 } 448 ::= { pimInterfaceEntry 22 } 450 -- The PIM Neighbor Table 452 pimNeighborTable OBJECT-TYPE 453 SYNTAX SEQUENCE OF PimNeighborEntry 454 MAX-ACCESS not-accessible 455 STATUS current 456 DESCRIPTION 457 "The (conceptual) table listing the router's PIM neighbors." 458 ::= { pim 3 } 460 pimNeighborEntry OBJECT-TYPE 461 SYNTAX PimNeighborEntry 462 MAX-ACCESS not-accessible 463 STATUS current 464 DESCRIPTION 465 "An entry (conceptual row) in the pimNeighborTable." 466 INDEX { pimNeighborAddress } 467 ::= { pimNeighborTable 1 } 469 PimNeighborEntry ::= SEQUENCE { 470 pimNeighborAddress IpAddress, 471 pimNeighborIfIndex InterfaceIndex, 472 pimNeighborUpTime TimeTicks, 473 pimNeighborExpiryTime TimeTicks, 474 pimNeighborMode INTEGER, 475 pimNeighborLanPruneDelay Integer32, 476 pimNeighborOverrideInterval Integer32, 477 pimNeighborTBit BITS, 478 pimNeighborSRCapable TruthValue, 479 pimNeighborDRPresent TruthValue 480 } 481 pimNeighborAddress OBJECT-TYPE 482 SYNTAX IpAddress 483 MAX-ACCESS not-accessible 484 STATUS current 485 DESCRIPTION 486 "The IP address of the PIM neighbor for which this entry 487 contains information." 488 ::= { pimNeighborEntry 1 } 490 pimNeighborIfIndex OBJECT-TYPE 491 SYNTAX InterfaceIndex 492 MAX-ACCESS read-only 493 STATUS current 494 DESCRIPTION 495 "The value of ifIndex for the interface used to reach this 496 PIM neighbor." 497 ::= { pimNeighborEntry 2 } 499 pimNeighborUpTime OBJECT-TYPE 500 SYNTAX TimeTicks 501 MAX-ACCESS read-only 502 STATUS current 503 DESCRIPTION 504 "The time since this PIM neighbor (last) became a neighbor 505 of the local router." 506 ::= { pimNeighborEntry 3 } 508 pimNeighborExpiryTime OBJECT-TYPE 509 SYNTAX TimeTicks 510 MAX-ACCESS read-only 511 STATUS current 512 DESCRIPTION 513 "The minimum time remaining before this PIM neighbor will be 514 aged out." 515 ::= { pimNeighborEntry 4 } 517 pimNeighborMode OBJECT-TYPE 518 SYNTAX INTEGER { dense(1), sparse(2) } 519 MAX-ACCESS read-only 520 STATUS deprecated 521 DESCRIPTION 522 "The active PIM mode of this neighbor. This object is 523 deprecated for PIMv2 routers since all neighbors on the 524 interface must be either dense or sparse as determined by 525 the protocol running on the interface." 526 ::= { pimNeighborEntry 5 } 528 pimNeighborLANPruneDelay OBJECT-TYPE 529 SYNTAX Integer32 530 MAX-ACCESS read-only 531 STATUS current 532 DESCRIPTION "The value of LAN Prune Delay field of the LAN Prune 533 Delay Option received from this neighbor. A value of 534 0 indicates that no LAN Prune Delay Option was 535 received from this neigbor." 536 ::= { pimNeighborEntry 6 } 538 pimNeighborOverrideInterval OBJECT-TYPE 539 SYNTAX Integer32 540 MAX-ACCESS read-only 541 STATUS current 542 DESCRIPTION "The value of Override Interval field of the LAN Prune 543 Delay Option received from this neighbor. A value of 544 0 indicates that no LAN Prune Delay Option was 545 received from this neigbor." 546 ::= { pimNeighborEntry 7 } 548 pimNeighborTBit OBJECT-TYPE 549 SYNTAX BITS 550 MAX-ACCESS read-only 551 STATUS current 552 DESCRIPTION "The value of the T bit field of the LAN Prune 553 Delay Option received from this neighbor. The T bit 554 specifies the ability of the neighbor to disable 555 join suppression." 556 ::= { pimNeighborEntry 8 } 558 pimNeighborSRCapable OBJECT-TYPE 559 SYNTAX TruthValue 560 MAX-ACCESS read-only 561 STATUS current 562 DESCRIPTION "Evaluates to TRUE if this neighbor is using the State 563 Refresh Capable Option." 564 ::= { pimNeighborEntry 9 } 566 pimNeighborDRPresent OBJECT-TYPE 567 SYNTAX TruthValue 568 MAX-ACCESS read-only 569 STATUS current 570 DESCRIPTION "Evaluates to TRUE if this neighbor is using the 571 Designated Router Option." 572 ::= { pimNeighborEntry 10 } 574 -- 575 -- The PIM IP Multicast Route Table 576 -- 578 pimIpMRouteTable OBJECT-TYPE 579 SYNTAX SEQUENCE OF PimIpMRouteEntry 580 MAX-ACCESS not-accessible 581 STATUS current 582 DESCRIPTION 583 "The (conceptual) table listing PIM-specific information on 584 a subset of the rows of the ipMRouteTable defined in the IP 585 Multicast MIB." 586 ::= { pim 4 } 588 pimIpMRouteEntry OBJECT-TYPE 589 SYNTAX PimIpMRouteEntry 590 MAX-ACCESS not-accessible 591 STATUS current 592 DESCRIPTION 593 "An entry (conceptual row) in the pimIpMRouteTable. There 594 is one entry per entry in the ipMRouteTable whose incoming 595 interface is running PIM." 596 INDEX { ipMRouteGroup, ipMRouteSource, ipMRouteSourceMask } 597 ::= { pimIpMRouteTable 1 } 599 PimIpMRouteEntry ::= SEQUENCE { 600 pimIpMRouteUpstreamAssertTimer TimeTicks, 601 pimIpMRouteAssertMetric Integer32, 602 pimIpMRouteAssertMetricPref Integer32, 603 pimIpMRouteAssertRPTBit TruthValue, 604 pimIpMRouteFlags BITS, 605 pimIpMRouteRPFNeighbor IpAddress, 606 pimIpMRouteSourceTimer TimeTicks, 607 pimIpMRouteOriginatorSRTTL Integer32 608 } 610 pimIpMRouteUpstreamAssertTimer OBJECT-TYPE 611 SYNTAX TimeTicks 612 MAX-ACCESS read-only 613 STATUS current 614 DESCRIPTION 615 "The time remaining before the router changes its upstream 616 neighbor back to its RPF neighbor. This timer is called the 617 Assert timer in the PIM Sparse and Dense mode specification. 618 A value of 0 indicates that no Assert has changed the 619 upstream neighbor away from the RPF neighbor." 620 ::= { pimIpMRouteEntry 1 } 622 pimIpMRouteAssertMetric OBJECT-TYPE 623 SYNTAX Integer32 624 MAX-ACCESS read-only 625 STATUS current 626 DESCRIPTION 627 "The metric advertised by the assert winner on the upstream 628 interface, or 0 if no such assert is in received." 629 ::= { pimIpMRouteEntry 2 } 631 pimIpMRouteAssertMetricPref OBJECT-TYPE 632 SYNTAX Integer32 633 MAX-ACCESS read-only 634 STATUS current 635 DESCRIPTION 636 "The preference advertised by the assert winner on the 637 upstream interface, or 0 if no such assert is in effect." 638 ::= { pimIpMRouteEntry 3 } 640 pimIpMRouteAssertRPTBit OBJECT-TYPE 641 SYNTAX TruthValue 642 MAX-ACCESS read-only 643 STATUS current 644 DESCRIPTION 645 "The value of the RPT-bit advertised by the assert winner on 646 the upstream interface, or false if no such assert is in 647 effect." 648 ::= { pimIpMRouteEntry 4 } 650 pimIpMRouteFlags OBJECT-TYPE 651 SYNTAX BITS { 652 rpt(0), 653 spt(1) 654 } 655 MAX-ACCESS read-only 656 STATUS current 657 DESCRIPTION 658 "This object describes PIM-specific flags related to a 659 multicast state entry. See the PIM Sparse Mode 660 specification for the meaning of the RPT and SPT bits." 661 ::= { pimIpMRouteEntry 5 } 663 pimIpMRouteRPFNeighbor OBJECT-TYPE 664 SYNTAX IpAddress 665 MAX-ACCESS read-only 666 STATUS current 667 DESCRIPTION "The IP Address of the current RPF neighbor. If there 668 is an upstream Assert Winner, it will be the RPF 669 neighbor. Otherwise, the RPF neighbor will be 670 the next hop indicated by unicast routing." 671 ::= { pimIpMRouteEntry 6 } 673 pimIpMRouteSourceTimer OBJECT-TYPE 674 SYNTAX TimeTicks 675 MAX-ACCESS read-only 676 STATUS current 677 DESCRIPTION "The time before this router ceases originating State 678 Refresh messages for this route." 679 ::= { pimIpMRouteEntry 7 } 681 pimIpMRouteOriginatorSRTTL OBJECT-TYPE 682 SYNTAX Integer32 683 MAX_ACCESS read-only 684 STATUS current 685 DESCRIPTION "The TTL used in State Refresh messages originated by 686 this router for this route." 687 ::= { pimIpMRouteEntry 8 } 689 -- 690 -- The PIM Next Hop Table 691 -- 693 pimIpMRouteNextHopTable OBJECT-TYPE 694 SYNTAX SEQUENCE OF PimIpMRouteNextHopEntry 695 MAX-ACCESS not-accessible 696 STATUS current 697 DESCRIPTION 698 "The (conceptual) table listing PIM-specific information on 699 a subset of the rows of the ipMRouteNextHopTable defined in 700 the IP Multicast MIB." 701 ::= { pim 7 } 702 pimIpMRouteNextHopEntry OBJECT-TYPE 703 SYNTAX PimIpMRouteNextHopEntry 704 MAX-ACCESS not-accessible 705 STATUS current 706 DESCRIPTION 707 "An entry (conceptual row) in the pimIpMRouteNextHopTable. 708 There is one entry per entry in the ipMRouteNextHopTable 709 whose interface is running PIM and whose 710 ipMRouteNextHopState is pruned(1)." 711 INDEX { ipMRouteNextHopGroup, ipMRouteNextHopSource, 712 ipMRouteNextHopSourceMask, ipMRouteNextHopIfIndex, 713 ipMRouteNextHopAddress } 714 ::= { pimIpMRouteNextHopTable 1 } 716 PimIpMRouteNextHopEntry ::= SEQUENCE { 717 pimIpMRouteNextHopPruneReason INTEGER, 718 pimIpMRouteNextHopAssertWinner IpAddress, 719 pimIpMRouteNextHopAssertTimer TimeTicks, 720 pimIpMRouteNextHopAssertMetric Integer32, 721 pimIpMRouteNextHopAssertMetricPref Integer32, 722 pimIpMRouteNextHopJoinPruneTimer TimeTicks 723 } 724 pimIpMRouteNextHopPruneReason OBJECT-TYPE 725 SYNTAX INTEGER { 726 other (1), 727 prune (2), 728 assert (3) 729 } 730 MAX-ACCESS read-only 731 STATUS current 732 DESCRIPTION 733 "This object indicates why the downstream interface was 734 pruned, whether in response to a PIM prune message or due to 735 PIM Assert processing." 736 ::= { pimIpMRouteNextHopEntry 2 } 738 pimIpMRouteNextHopAssertWinner OBJECT-TYPE 739 SYNTAX IpAddress 740 MAX-ACCESS read-only 741 STATUS current 742 DESCRIPTION "The IP Address of the Assert Winner." 743 ::= { pimIpMRouteNextHopEntry 3 } 745 pimIpMRouteNextHopAssertTimer OBJECT-TYPE 746 SYNTAX TimeTicks 747 MAX-ACCESS read-only 748 STATUS current 749 DESCRIPTION "The time remaining before the PIM router leaves the 750 current Assert state. A value of 0 indicates that the 751 router is in the No Info state." 752 ::= { pimIpMRouteNextHopEntry 4 } 753 pimIpMRouteNextHopAssertMetric OBJECT-TYPE 754 SYNTAX Integer32 755 MAX-ACCESS read-only 756 STATUS current 757 DESCRIPTION "The metric advertised by the Assert Winner." 758 ::= { pimIpMRouteNextHopEntry 5 } 760 pimIpMRouteNextHopAssertMetricPref OBJECT-TYPE 761 SYNTAX Integer32 762 MAX-ACCESS read-only 763 STATUS current 764 DESCRIPTION "The metric preference advertised by the Assert Winner." 765 ::= { pimIpMRouteNextHopEntry 6 } 767 pimIpMRouteNextHopJoinPruneTimer OBJECT-TYPE 768 SYNTAX TimeTicks 769 MAX-ACCESS read-only 770 STATUS current 771 DESCRIPTION "The time remaining before the PIM router reverts to 772 default operation on this interface. PIM-SM will 773 cease forwarding, PIM-DM will resume forwarding." 774 ::= { pimIpMRouteNextHopEntry 7 }ss, pimRPAddress } 775 ::= { pimRPTable 1 } 777 -- The PIM RP Table 779 pimRPTable OBJECT-TYPE 780 SYNTAX SEQUENCE OF PimRPEntry 781 MAX-ACCESS not-accessible 782 STATUS deprecated 783 DESCRIPTION 784 "The (conceptual) table listing PIM version 1 information 785 for the Rendezvous Points (RPs) for IP multicast groups. 786 This table is deprecated since its function is replaced by 787 the pimRPSetTable for PIM version 2." 788 ::= { pim 5 } 790 pimRPEntry OBJECT-TYPE 791 SYNTAX PimRPEntry 792 MAX-ACCESS not-accessible 793 STATUS deprecated 794 DESCRIPTION 795 "An entry (conceptual row) in the pimRPTable. There is one 796 entry per RP address for each IP multicast group." 797 INDEX { pimRPGroupAddre 798 PimRPEntry ::= SEQUENCE { 799 pimRPGroupAddress IpAddress, 800 pimRPAddress IpAddress, 801 pimRPState INTEGER, 802 pimRPStateTimer TimeTicks, 803 pimRPLastChange TimeTicks, 804 pimRPRowStatus RowStatus 805 } 807 pimRPGroupAddress OBJECT-TYPE 808 SYNTAX IpAddress 809 MAX-ACCESS not-accessible 810 STATUS deprecated 811 DESCRIPTION 812 "The IP multicast group address for which this entry 813 contains information about an RP." 814 ::= { pimRPEntry 1 } 816 pimRPAddress OBJECT-TYPE 817 SYNTAX IpAddress 818 MAX-ACCESS not-accessible 819 STATUS deprecated 820 DESCRIPTION 821 "The unicast address of the RP." 822 ::= { pimRPEntry 2 } 824 pimRPState OBJECT-TYPE 825 SYNTAX INTEGER { up(1), down(2) } 826 MAX-ACCESS read-only 827 STATUS deprecated 828 DESCRIPTION 829 "The state of the RP." 830 ::= { pimRPEntry 3 } 832 pimRPStateTimer OBJECT-TYPE 833 SYNTAX TimeTicks 834 MAX-ACCESS read-only 835 STATUS deprecated 836 DESCRIPTION 837 "The minimum time remaining before the next state change. 838 When pimRPState is up, this is the minimum time which must 839 expire until it can be declared down. When pimRPState is 840 down, this is the time until it will be declared up (in 841 order to retry)." 842 ::= { pimRPEntry 4 } 844 pimRPLastChange OBJECT-TYPE 845 SYNTAX TimeTicks 846 MAX-ACCESS read-only 847 STATUS deprecated 848 DESCRIPTION 849 "The value of sysUpTime at the time when the corresponding 850 instance of pimRPState last changed its value." 851 ::= { pimRPEntry 5 } 853 pimRPRowStatus OBJECT-TYPE 854 SYNTAX RowStatus 855 MAX-ACCESS read-create 856 STATUS deprecated 857 DESCRIPTION 858 "The status of this row, by which new entries may be 859 created, or old entries deleted from this table." 860 ::= { pimRPEntry 6 } 862 -- The PIM RP-Set Table 864 pimRPSetTable OBJECT-TYPE 865 SYNTAX SEQUENCE OF PimRPSetEntry 866 MAX-ACCESS not-accessible 867 STATUS current 868 DESCRIPTION 869 "The (conceptual) table listing PIM information for 870 candidate Rendezvous Points (RPs) for IP multicast groups. 871 When the local router is the BSR, this information is 872 obtained from received Candidate-RP-Advertisements. When 873 the local router is not the BSR, this information is 874 obtained from received RP-Set messages." 875 ::= { pim 6 } 877 pimRPSetEntry OBJECT-TYPE 878 SYNTAX PimRPSetEntry 879 MAX-ACCESS not-accessible 880 STATUS current 881 DESCRIPTION 882 "An entry (conceptual row) in the pimRPSetTable." 883 INDEX { pimRPSetComponent, pimRPSetGroupAddress, 884 pimRPSetGroupMask, pimRPSetAddress } 885 ::= { pimRPSetTable 1 } 887 PimRPSetEntry ::= SEQUENCE { 889 pimRPSetGroupAddress IpAddress, 890 pimRPSetGroupMask IpAddress, 891 pimRPSetAddress IpAddress, 892 pimRPSetHoldTime Integer32, 893 pimRPSetExpiryTime TimeTicks, 894 pimRPSetComponent Integer32 895 } 897 pimRPSetGroupAddress OBJECT-TYPE 898 SYNTAX IpAddress 899 MAX-ACCESS not-accessible 900 STATUS current 901 DESCRIPTION 902 "The IP multicast group address which, when combined with 903 pimRPSetGroupMask, gives the group prefix for which this 904 entry contains information about the Candidate-RP." 905 ::= { pimRPSetEntry 1 } 907 pimRPSetGroupMask OBJECT-TYPE 908 SYNTAX IpAddress 909 MAX-ACCESS not-accessible 910 STATUS current 911 DESCRIPTION 912 "The multicast group address mask which, when combined with 913 pimRPSetGroupAddress, gives the group prefix for which this 914 entry contains information about the Candidate-RP." 915 ::= { pimRPSetEntry 2 } 917 pimRPSetAddress OBJECT-TYPE 918 SYNTAX IpAddress 919 MAX-ACCESS not-accessible 920 STATUS current 921 DESCRIPTION 922 "The IP address of the Candidate-RP." 923 ::= { pimRPSetEntry 3 } 925 pimRPSetHoldTime OBJECT-TYPE 926 SYNTAX Integer32 (0..255) 927 UNITS "seconds" 928 MAX-ACCESS read-only 929 STATUS current 930 DESCRIPTION 931 "The holdtime of a Candidate-RP. If the local router is not 932 the BSR, this value is 0." 933 ::= { pimRPSetEntry 4 } 935 pimRPSetExpiryTime OBJECT-TYPE 936 SYNTAX TimeTicks 937 MAX-ACCESS read-only 938 STATUS current 939 DESCRIPTION 940 "The minimum time remaining before the Candidate-RP will be 941 declared down. If the local router is not the BSR, this 942 value is 0." 943 ::= { pimRPSetEntry 5 } 945 pimRPSetComponent OBJECT-TYPE 946 SYNTAX Integer32 (1..255) 947 MAX-ACCESS not-accessible 948 STATUS current 949 DESCRIPTION 950 " A number uniquely identifying the component. Each 951 protocol instance connected to a separate domain should have 952 a different index value." 953 ::= { pimRPSetEntry 6 } 955 -- 956 -- Note: { pim 8 } through { pim 10 } were used in older versions 957 -- of this MIB. Since some earlier versions of this MIB have been 958 -- widely-deployed, these values must not be used in the future, 959 -- as long the MIB is rooted under { experimental 61 }. 960 -- 962 -- The PIM Candidate-RP Table 964 pimCandidateRPTable OBJECT-TYPE 965 SYNTAX SEQUENCE OF PimCandidateRPEntry 966 MAX-ACCESS not-accessible 967 STATUS current 968 DESCRIPTION 969 "The (conceptual) table listing the IP multicast groups for 970 which the local router is to advertise itself as a 971 Candidate-RP when the value of pimComponentCRPHoldTime is 972 non-zero. If this table is empty, then the local router 973 will advertise itself as a Candidate-RP for all groups 974 (providing the value of pimComponentCRPHoldTime is non- 975 zero)." 976 ::= { pim 11 } 978 pimCandidateRPEntry OBJECT-TYPE 979 SYNTAX PimCandidateRPEntry 980 MAX-ACCESS not-accessible 981 STATUS current 982 DESCRIPTION 983 "An entry (conceptual row) in the pimCandidateRPTable." 984 INDEX { pimCandidateRPGroupAddress, 985 pimCandidateRPGroupMask } 986 ::= { pimCandidateRPTable 1 } 988 PimCandidateRPEntry ::= SEQUENCE { 989 pimCandidateRPGroupAddress IpAddress, 990 pimCandidateRPGroupMask IpAddress, 991 pimCandidateRPAddress IpAddress, 992 pimCandidateRPRowStatus RowStatus 993 } 995 pimCandidateRPGroupAddress OBJECT-TYPE 996 SYNTAX IpAddress 997 MAX-ACCESS not-accessible 998 STATUS current 999 DESCRIPTION 1000 "The IP multicast group address which, when combined with 1001 pimCandidateRPGroupMask, identifies a group prefix for which 1002 the local router will advertise itself as a Candidate-RP." 1003 ::= { pimCandidateRPEntry 1 } 1005 pimCandidateRPGroupMask OBJECT-TYPE 1006 SYNTAX IpAddress 1007 MAX-ACCESS not-accessible 1008 STATUS current 1009 DESCRIPTION 1010 "The multicast group address mask which, when combined with 1011 pimCandidateRPGroupMask, identifies a group prefix for which 1012 the local router will advertise itself as a Candidate-RP." 1013 ::= { pimCandidateRPEntry 2 } 1015 pimCandidateRPAddress OBJECT-TYPE 1016 SYNTAX IpAddress 1017 MAX-ACCESS read-create 1018 STATUS current 1019 DESCRIPTION 1020 "The (unicast) address of the interface which will be 1021 advertised as a Candidate-RP." 1022 ::= { pimCandidateRPEntry 3 } 1024 pimCandidateRPRowStatus OBJECT-TYPE 1025 SYNTAX RowStatus 1026 MAX-ACCESS read-create 1027 STATUS current 1028 DESCRIPTION 1029 "The status of this row, by which new entries may be 1030 created, or old entries deleted from this table." 1031 ::= { pimCandidateRPEntry 4 } 1033 -- The PIM Component Table 1035 pimComponentTable OBJECT-TYPE 1036 SYNTAX SEQUENCE OF PimComponentEntry 1037 MAX-ACCESS not-accessible 1038 STATUS current 1039 DESCRIPTION 1040 "The (conceptual) table containing objects specific to a PIM 1041 domain. One row exists for each domain to which the router 1042 is connected. A PIM-SM domain is defined as an area of the 1043 network over which Bootstrap messages are forwarded. 1044 Typically, a PIM-SM router will be a member of exactly one 1045 domain. This table also supports, however, routers which 1046 may form a border between two PIM-SM domains and do not 1047 forward Bootstrap messages between them." 1048 ::= { pim 12 } 1050 pimComponentEntry OBJECT-TYPE 1051 SYNTAX PimComponentEntry 1052 MAX-ACCESS not-accessible 1053 STATUS current 1054 DESCRIPTION 1055 "An entry (conceptual row) in the pimComponentTable." 1056 INDEX { pimComponentIndex } 1057 ::= { pimComponentTable 1 } 1059 PimComponentEntry ::= SEQUENCE { 1060 pimComponentIndex Integer32, 1061 pimComponentBSRAddress IpAddress, 1062 pimComponentBSRExpiryTime TimeTicks, 1063 pimComponentCRPHoldTime Integer32, 1064 pimComponentStatus RowStatus 1065 } 1066 pimComponentIndex OBJECT-TYPE 1067 SYNTAX Integer32 (1..255) 1068 MAX-ACCESS not-accessible 1069 STATUS current 1070 DESCRIPTION 1071 "A number uniquely identifying the component. Each protocol 1072 instance connected to a separate domain should have a 1073 different index value. Routers that only support membership 1074 in a single PIM-SM domain should use a pimComponentIndex 1075 value of 1." 1076 ::= { pimComponentEntry 1 } 1078 pimComponentBSRAddress OBJECT-TYPE 1079 SYNTAX IpAddress 1080 MAX-ACCESS read-only 1081 STATUS current 1082 DESCRIPTION 1083 "The IP address of the bootstrap router (BSR) for the local 1084 PIM region." 1085 ::= { pimComponentEntry 2 } 1087 pimComponentBSRExpiryTime OBJECT-TYPE 1088 SYNTAX TimeTicks 1089 MAX-ACCESS read-only 1090 STATUS current 1091 DESCRIPTION 1092 "The minimum time remaining before the bootstrap router in 1093 the local domain will be declared down. For candidate BSRs, 1094 this is the time until the component sends an RP-Set 1095 message. For other routers, this is the time until it may 1096 accept an RP-Set message from a lower candidate BSR." 1097 ::= { pimComponentEntry 3 } 1099 pimComponentCRPHoldTime OBJECT-TYPE 1100 SYNTAX Integer32 (0..255) 1101 UNITS "seconds" 1102 MAX-ACCESS read-create 1103 STATUS current 1104 DESCRIPTION 1105 "The holdtime of the component when it is a candidate RP in 1106 the local domain. The value of 0 is used to indicate that 1107 the local system is not a Candidate-RP." 1108 DEFVAL { 0 } 1109 ::= { pimComponentEntry 4 } 1111 pimComponentStatus OBJECT-TYPE 1112 SYNTAX RowStatus 1113 MAX-ACCESS read-create 1114 STATUS current 1115 DESCRIPTION 1116 "The status of this entry. Creating the entry creates 1117 another protocol instance; destroying the entry disables a 1118 protocol instance." 1119 ::= { pimComponentEntry 5 } 1121 -- PIM State Refresh Objects 1123 pimSourceLifetime OBJECT-TYPE 1124 SYNTAX Integer32 1125 UNITS "seconds" 1126 MAX-ACCESS read-create 1127 STATUS current 1128 DESCRIPTION "The maximum time this router will continue to 1129 originate State Refresh messages in the absence of 1130 traffic from the source itself." 1131 DEFVAL { 210 } 1132 ::= { pim 13 } 1134 pimStateRefreshInterval OBJECT-TYPE 1135 SYNTAX Integer32 (1..255) 1136 UNITS "seconds" 1137 MAX-ACCESS read-create 1138 STATUS current 1139 DESCRIPTION "The interval between successive State Refresh 1140 messages originated by this router." 1141 DEFVAL { 60 } 1142 ::= { pim 14 } 1144 pimStateRefreshLimitInterval OBJECT-TYPE 1145 SYNTAX TimeTicks 1146 MAX-ACCESS read-create 1147 STATUS current 1148 DESCRIPTION "This router will not forward successive State Refresh 1149 messages received at less than this interval." 1150 DEFVAL { 0 } 1151 ::= { pim 15 } 1153 pimStateRefreshTimeToLive OBJECT-TYPE 1154 SYNTAX Integer32 1155 MAX-ACCESS read-create 1156 STATUS current 1157 DESCRIPTION "The TTL to be used by this router's originated State 1158 Refresh messages if the data packet's TTL is not 1159 recorded." 1160 DEFVAL { 16 } 1161 ::= { pim 16 } 1162 -- PIM Traps 1164 pimNeighborLoss NOTIFICATION-TYPE 1165 OBJECTS { 1166 pimNeighborIfIndex 1167 } 1168 STATUS current 1169 DESCRIPTION 1170 "A pimNeighborLoss trap signifies the loss of an adjacency 1171 with a neighbor. This trap should be generated when the 1172 neighbor timer expires, and the router has no other 1173 neighbors on the same interface with a lower IP address than 1174 itself." 1175 ::= { pimTraps 1 } 1177 -- conformance information 1179 pimMIBConformance OBJECT IDENTIFIER ::= { pimMIB 2 } 1180 pimMIBCompliances OBJECT IDENTIFIER ::= { pimMIBConformance 1 } 1181 pimMIBGroups OBJECT IDENTIFIER ::= { pimMIBConformance 2 } 1183 -- compliance statements 1185 pimV1MIBCompliance MODULE-COMPLIANCE 1186 STATUS deprecated 1187 DESCRIPTION 1188 "The compliance statement for routers running PIMv1 and 1189 implementing the PIM MIB." 1190 MODULE -- this module 1191 MANDATORY-GROUPS { pimV1MIBGroup } 1193 ::= { pimMIBCompliances 1 } 1195 pimSparseV2MIBCompliance MODULE-COMPLIANCE 1196 STATUS current 1197 DESCRIPTION 1198 "The compliance statement for routers running PIM Sparse 1199 Mode and implementing the PIM MIB." 1200 MODULE -- this module 1201 MANDATORY-GROUPS { pimV2MIBGroup } 1203 GROUP pimV2CandidateRPMIBGroup 1204 DESCRIPTION 1205 "This group is mandatory if the router is capable of being a 1206 Candidate RP." 1208 OBJECT pimInterfaceStatus 1209 MIN-ACCESS read-only 1210 DESCRIPTION 1211 "Write access is not required." 1212 ::= { pimMIBCompliances 2 } 1214 pimDenseV2MIBCompliance MODULE-COMPLIANCE 1215 STATUS current 1216 DESCRIPTION 1217 "The compliance statement for routers running PIM Dense Mode 1218 and implementing the PIM MIB." 1219 MODULE -- this module 1221 MANDATORY-GROUPS { pimDenseV2MIBGroup } 1223 OBJECT pimInterfaceStatus 1224 MIN-ACCESS read-only 1225 DESCRIPTION 1226 "Write access is not required." 1228 ::= { pimMIBCompliances 3 } 1230 -- units of conformance 1232 pimNotificationGroup NOTIFICATION-GROUP 1233 NOTIFICATIONS { pimNeighborLoss } 1234 STATUS current 1235 DESCRIPTION 1236 "A collection of notifications for signaling important PIM 1237 events." 1238 ::= { pimMIBGroups 1 } 1240 pimV2MIBGroup OBJECT-GROUP 1241 OBJECTS { pimJoinPruneInterval, pimInterfaceIfIndex, 1242 pimInterfaceAddress, pimInterfaceNetMask, 1243 pimInterfaceMode, pimInterfaceDR, 1244 pimInterfaceHelloInterval, pimInterfaceStatus, 1245 pimInterfaceJoinPruneInterval, 1246 pimInterfaceCBSRPreference, pimInterfaceTrigHelloInterval, 1247 pimInterfaceHelloHoldtime, pimInterfaceLanPruneDelay, 1248 pimInterfacePropagationDelay, 1249 pimInterfaceOverrideInterval, pimInterfaceGenerationID, 1250 pimInterfaceJoinPruneHoldtime, 1251 pimInterfaceLanDelayEnabled, pimInterfaceDRPriority, 1252 pimNeighborAddress, pimNeighborInterfaceIfIndex, 1253 pimNeighborUpTime, pimNeighborExpiryTime, 1254 pimNeighborLANPruneDelay, pimNeighborOverrideInterval, 1255 pimNeighborTBit, pimNeighborDRPresent, 1256 pimIpMRouteUpstreamAssertTimer, pimIpMRouteAssertMetric, 1257 pimIpMRouteIpRouteAssertMetricPref, 1258 pimIpMRouteAssertRPTBit, pimIpMRouteFlags, 1259 pimIpMRouteRPFNeighbor, pimIpMRouteNextHopPruneReason, 1260 pimRPSetGroupAddress, pimRPSetGroupMask, pimRPSetAddress, 1261 pimRPSetHoldTime, pimRPSetExpiryTime, pimRPSetComponent, 1262 pimComponentBSRAddress, pimComponentBSRExpiryTime, 1263 pimComponentCRPHoldTime, pimComponentStatus 1264 } 1265 STATUS current 1266 DESCRIPTION 1267 "A collection of objects to support management of PIM Sparse 1268 Mode (version 2) routers." 1269 ::= { pimMIBGroups 2 } 1271 pimDenseV2MIBGroup OBJECT-GROUP 1272 OBJECTS { pimInterfaceIfIndex, pimInterfaceAddress, 1273 pimInterfaceNetMask, pimInterfaceHelloInterval, 1274 pimInterfaceStatus, pimInterfaceTrigHelloInterval, 1275 pimInterfaceHelloHoldtime, pimInterfaceLanPruneDelay, 1276 pimInterfacePropagationDelay, pimInterfaceOverrideInterval, 1277 pimInterfaceGenerationID, pimInterfaceJoinPruneHoldtime, 1278 pimInterfaceGraftRetryInterval, 1279 pimInterfaceMaxGraftRetries, pimInterfaceSRTTLThreshold, 1280 pimInterfaceLanDelayEnabled, pimInterfaceSRCapable, 1281 pimNeighborIfIndex, pimNeighborUpTime, 1282 pimNeighborExpiryTime, pimNeighborLANPruneDelay, 1283 pimNeighborOverrideInterval, pimNeighborSRCapable, 1284 pimIpMRouteSourceTimer, pimIpMRouteOriginatorSRTTL, 1285 pimSourceLifetime, pimStateRefreshInterval, 1286 pimStateRefreshLimitInterval, pimStateRefreshTimeToLive 1287 } 1288 STATUS current 1289 DESCRIPTION 1290 "A collection of objects to support management of PIM Dense 1291 Mode (version 2) routers." 1292 ::= { pimMIBGroups 5 } 1294 pimV2CandidateRPMIBGroup OBJECT-GROUP 1295 OBJECTS { pimCandidateRPAddress, 1296 pimCandidateRPRowStatus 1297 } 1298 STATUS current 1299 DESCRIPTION 1300 "A collection of objects to support configuration of which 1301 groups a router is to advertise itself as a Candidate-RP." 1302 ::= { pimMIBGroups 3 } 1304 pimV1MIBGroup OBJECT-GROUP 1305 OBJECTS { pimJoinPruneInterval, pimNeighborIfIndex, 1306 pimNeighborUpTime, pimNeighborExpiryTime, 1307 pimNeighborMode, 1308 pimInterfaceAddress, pimInterfaceNetMask, 1309 pimInterfaceJoinPruneInterval, pimInterfaceStatus, 1310 pimInterfaceMode, pimInterfaceDR, 1311 pimInterfaceHelloInterval, 1312 pimRPState, pimRPStateTimer, 1313 pimRPLastChange, pimRPRowStatus 1314 } 1315 STATUS deprecated 1316 DESCRIPTION 1317 "A collection of objects to support management of PIM 1318 (version 1) routers." 1319 ::= { pimMIBGroups 4 } 1321 pimNextHopGroup OBJECT-GROUP 1322 OBJECTS { pimIpMRouteNextHopPruneReason, 1323 pimIpMRouteNextHopAssertWinner, 1324 pimIpMRouteNextHopAssertTimer, 1325 pimIpMRouteNextHopAssertMetric, 1326 pimIpMRouteNextHopAssertMetricPref, 1327 pimIpMRouteNextHopJoinPruneTimer 1328 } 1329 STATUS current 1330 DESCRIPTION 1331 "A collection of optional objects to provide per-next hop 1332 information for diagnostic purposes. Supporting this group 1333 may add a large number of instances to a tree walk, but the 1334 information in this group can be extremely useful in 1335 tracking down multicast connectivity problems." 1336 ::= { pimMIBGroups 6 } 1338 pimAssertGroup OBJECT-GROUP 1339 OBJECTS { pimIpMRouteAssertMetric, pimIpMRouteAssertMetricPref, 1340 pimIpMRouteAssertRPTBit, pimIpMRouteRPFNeighbor} 1341 STATUS current 1342 DESCRIPTION 1343 "A collection of optional objects to provide extra 1344 information about the assert election process. There is no 1345 protocol reason to keep such information, but some 1346 implementations may already keep this information and make 1347 it available. These objects can also be very useful in 1348 debugging connectivity or duplicate packet problems, 1349 especially if the assert winner does not support the PIM and 1350 IP Multicast MIBs." 1351 ::= { pimMIBGroups 7 } 1353 END 1355 5. Security Considerations 1357 This MIB contains readable objects whose values provide information 1358 related to multicast routing, including information on the network 1359 topology. There are also a number of objects that have a MAX-ACCESS 1360 clause of read-write and/or read-create, which allow an administrator 1361 to configure PIM in the router. 1363 While unauthorized access to the readable objects is relatively 1364 innocuous, unauthorized access to the write-able objects could cause 1365 a denial of service. Hence, the support for SET operations in a 1366 non-secure environment without proper protection can have a negative 1367 effect on network operations. 1369 SNMPv1 by itself is such an insecure environment. Even if the 1370 network itself is secure (for example by using IPSec), even then, 1371 there is no control as to who on the secure network is allowed to 1372 access and SET (change/create/delete) the objects in this MIB. 1374 It is recommended that the implementers consider the security 1375 features as provided by the SNMPv3 framework. Specifically, the use 1376 of the User-based Security Model RFC 2274 [12] and the View-based 1377 Access Control Model RFC 2275 [15] is recommended. 1379 It is then a customer/user responsibility to ensure that the SNMP 1380 entity giving access to this MIB, is properly configured to give 1381 access to those objects only to those principals (users) that have 1382 legitimate rights to access them. 1384 6. Acknowledgements 1386 This MIB module is based on the original work in RFC 2934 by 1387 K. McCloghrie, D. Farinacci, D. Thaler and W. Fenner and has been 1388 updated based on feedback from the IETF's Protocol Independent 1389 Multicast (PIM) Working Group. 1391 7. Authors' Addresses 1393 Jonathan Nicholas 1394 ITT Industries 1395 Aerospace/Communications Division 1396 100 Kingsland Rd 1397 Clifton, NJ 07014 1399 Phone: +1 973 284 2019 1400 EMail: Jonathan.Nicholas@itt.com 1402 8. References 1404 [1] Wijnen, B., Harrington, D. and R. Presuhn, "An Architecture for 1405 Describing SNMP Management Frameworks", RFC 2571, April 1999. 1407 [2] Rose, M. and K. McCloghrie, "Structure and Identification of 1408 Management Information for TCP/IP-based Internets", STD 16, RFC 1409 1155, May 1990. 1411 [3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, 1412 RFC 1212, March 1991. 1414 [4] Rose, M., "A Convention for Defining Traps for use with the 1415 SNMP", RFC 1215, March 1991. 1417 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1418 M. and S. Waldbusser, "Structure of Management Information 1419 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 1421 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1422 M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, 1423 RFC 2579, April 1999. 1425 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1426 M. and S. Waldbusser, "Conformance Statements for SMIv2", STD 1427 58, RFC 2580, April 1999. 1429 [8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple 1430 Network Management Protocol", STD 15, RFC 1157, May 1990. 1432 [9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 1433 "Introduction to Community-based SNMPv2", RFC 1901, January 1434 1996. 1436 [10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport 1437 Mappings for Version 2 of the Simple Network Management Protocol 1438 (SNMPv2)", RFC 1906, January 1996. 1440 [11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message 1441 Processing and Dispatching for the Simple Network Management 1442 Protocol (SNMP)", RFC 2572, April 1999. 1444 [12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) 1445 for version 3 of the Simple Network Management Protocol 1446 (SNMPv3)", RFC 2574, April 1999. 1448 [13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol 1449 Operations for Version 2 of the Simple Network Management 1450 Protocol (SNMPv2)", RFC 1905, January 1996. 1452 [14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC 1453 2573, April 1999. 1455 [15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access 1456 Control Model (VACM) for the Simple Network Management Protocol 1457 (SNMP)", RFC 2575, April 1999. 1459 [18] Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering, S., 1460 Handley, M., Jacobson, V., Liu, C., Sharma, P. and L. Wei, 1461 "Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol 1462 Specification", RFC 2362, June 1998. 1464 [19] Adams, A., Nicholas, J., Siadak, W., "Protocol Independent 1465 Multicast - Dense Mode (PIM-DM): Protocol Specification 1466 (Revised)", draft-ietf-pim-dm-new-v2-02.txt, work in progress. 1468 [20] McCloghrie, K., Farinacci, D. and D. Thaler, "IPv4 Multicast 1469 Routing MIB", RFC 2932, October 2000. 1471 [21] Fenner, W., Handley, M., Holbrook, H., Kouvelas, I., 1472 "Protocol Independent Multicast - Sparse Mode (PIM-SM)", draft- 1473 ietf-pim-sm-v2-new-05.txt, work in progress. 1475 [22] McCloghrie, K., Farinacci, D., Thaler, D., Fenner, W., 1476 "Protocol Independent Multicast MIB for IPv4", RFC 2934, 1477 October 2000.