idnits 2.17.00 (12 Aug 2021) /tmp/idnits63122/draft-ietf-pim-mib-v2-00.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 == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 29) being 59 lines 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 (December 2002) is 7096 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 ** 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 Summary: 18 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 Jonathan Nicholas 3 draft-ietf-pim-mib-v2-00.txt ITT A/CD 4 June 2002 5 Expires December 2002 7 Protocol Independent Multicast MIB 9 Status of this Document 11 This document is an Internet-Draft and is in full conformance with all 12 provisions of Section 10 of RFC2026. 14 Internet-Drafts are working documents of the Internet Engineering Task 15 Force (IETF), its areas, and its working groups. Note that other groups 16 may also distribute working documents as Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six months 19 and may be updated, replaced, or obsoleted by other documents at any 20 time. It is inappropriate to use Internet- Drafts as reference material 21 or to cite them other than as "work in progress." 23 The list of current Internet-Drafts can be accessed at 24 http://www.ietf.org/ietf/1id-abstracts.txt 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 This document is a product of the IETF PIM WG. Comments should be 30 addressed to the authors, or the WG's mailing list at 31 pim@catarina.usc.edu. 33 Abstract 35 This memo defines a portion of the Management Information Base (MIB) for 36 use with network management protocols in the Internet community. In 37 particular, it describes managed objects used for managing the Protocol 38 Independent Multicast (PIM) protocol. 40 Table of Contents 42 1 Introduction ................................................. 2 43 2 The SNMP Network Management Framework ........................ 2 44 3 Overview ..................................................... 3 45 4 Definitions .................................................. 4 46 5 Security Considerations ...................................... 29 47 6 Acknowledgements ............................................. 30 48 7 Authors' Addresses ........................................... 30 49 8 References ................................................... 30 51 1. Introduction 53 This memo defines a portion of the Management Information Base (MIB) for 54 use with network management protocols in the Internet community. In 55 particular, it describes managed objects used for managing the Protocol 56 Independent Multicast (PIM) protocol [18,19]. 58 2. The SNMP Network Management Framework 60 The SNMP Management Framework presently consists of five major 61 components: 63 * An overall architecture, described in RFC 2571 [1]. 65 * Mechanisms for describing and naming objects and events for the 66 purpose of management. The first version of this Structure of 67 Management Information (SMI) is called SMIv1 and described in STD 16, 68 RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The second 69 version, called SMIv2, is described in STD 58, RFC 2578 [5], STD 58, 70 RFC 2579 [6] and STD 58, RFC 2580 [7]. 72 * Message protocols for transferring management information. The first 73 version of the SNMP message protocol is called SNMPv1 and described 74 in STD 15, RFC 1157 [8]. A second version of the SNMP message 75 protocol, which is not an Internet standards track protocol, is called 76 SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. The third 77 version of the message protocol is called SNMPv3 and described in 78 RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12]. 80 * Protocol operations for accessing management information. The first 81 set of protocol operations and associated PDU formats is described in 82 STD 15, RFC 1157 [8]. A second set of protocol operations and 83 associated PDU formats is described in RFC 1905 [13]. 85 * A set of fundamental applications described in RFC 2573 [14] and the 86 view-based access control mechanism described in RFC 2575 [15]. 88 Managed objects are accessed via a virtual information store, termed the 89 Management Information Base or MIB. Objects in the MIB are defined 90 using the mechanisms defined in the SMI. 92 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 93 conforming to the SMIv1 can be produced through the appropriate 94 translations. The resulting translated MIB must be semantically 95 equivalent, except where objects or events are omitted because no 96 translation is possible (use of Counter64). Some machine readable 97 information in SMIv2 will be converted into textual descriptions in 98 SMIv1 during the translation process. However, this loss of machine 99 readable information is not considered to change the semantics of the 100 MIB. 102 3. Overview 104 This MIB module contains one scalar and eight tables. Some of the 105 objects in these tables are deprecated. This MIB contains deprecated 106 objects since they are necessary for managing PIMv1 routers, but PIMv1 107 itself is obsoleted by PIM v2 [18,19]. 109 The tables contained in this MIB are: 111 (1) The PIM Interface Table contains one row for each of the 112 router's PIM interfaces. 114 (2) The PIM Neighbor Table contains one row for each of the router's 115 PIM neighbors. 117 (3) The PIM IP Multicast Route Table contains one row for each 118 multicast routing entry whose incoming interface is running PIM. 120 (4) The PIM Next Hop Table which contains one row for each outgoing 121 interface list entry in the multicast routing table whose 122 interface is running PIM, and whose state is pruned. 124 (5) The (deprecated) PIM RP Table contains the PIM (version 1) 125 information for IP multicast groups which is common to all RPs 126 of a group. 128 (6) The PIM RP-Set Table contains the PIM (version 2) information 129 for sets of candidate Rendezvous Points (RPs) for IP multicast 130 group addresses with particular address prefixes. 132 (7) The PIM Candidate-RP Table contains the IP multicast groups for 133 which the local router is to advertise itself as a Candidate-RP. 134 If this table is empty, then the local router advertises itself 135 as a Candidate-RP for all groups. 137 (8) The PIM Component Table contains one row for each of the PIM 138 domains to which the router is connected. 140 4. Definitions 142 PIM-MIB DEFINITIONS ::= BEGIN 144 IMPORTS 145 MODULE-IDENTITY, OBJECT-TYPE, experimental, 146 NOTIFICATION-TYPE, 147 Integer32, IpAddress, TimeTicks FROM SNMPv2-SMI 148 RowStatus, TruthValue FROM SNMPv2-TC 149 MODULE-COMPLIANCE, OBJECT-GROUP, 150 NOTIFICATION-GROUP FROM SNMPv2-CONF 151 ipMRouteGroup, ipMRouteSource, 152 ipMRouteSourceMask, ipMRouteNextHopGroup, 153 ipMRouteNextHopSource, ipMRouteNextHopSourceMask, 154 ipMRouteNextHopIfIndex, 155 ipMRouteNextHopAddress FROM IPMROUTE-STD-MIB 156 InterfaceIndex FROM IF-MIB; 158 pimMIB MODULE-IDENTITY 159 LAST-UPDATED "200206040000Z" -- June 4, 2002 160 ORGANIZATION "IETF PIM Working Group." 161 CONTACT-INFO 162 " Jonathan Nicholas 163 ITT Industries 164 Aerospace/Communications Division 165 100 Kingsland Rd 166 Clifton, NJ 07014 168 Phone: +1 973 284 2019 169 EMail: jonathan.nicholas@itt.com" 170 DESCRIPTION 171 "The MIB module for management of PIM routers." 172 REVISION "200206040000Z" -- June 4, 2002 173 DESCRIPTION 174 "Revised June 4, 2002." 175 ::= { experimental 61 } 177 pimMIBObjects OBJECT IDENTIFIER ::= { pimMIB 1 } 179 pimTraps OBJECT IDENTIFIER ::= { pimMIBObjects 0 } 181 pim OBJECT IDENTIFIER ::= { pimMIBObjects 1 } 183 pimJoinPruneInterval OBJECT-TYPE 184 SYNTAX Integer32 185 UNITS "seconds" 186 MAX-ACCESS read-write 187 STATUS current 188 DESCRIPTION 189 "The default interval at which periodic PIM-SM Join/Prune 190 messages are to be sent." 191 DEFVAL { 60 } 192 ::= { pim 1 } 194 -- The PIM Interface Table 196 pimInterfaceTable OBJECT-TYPE 197 SYNTAX SEQUENCE OF PimInterfaceEntry 198 MAX-ACCESS not-accessible 199 STATUS current 200 DESCRIPTION 201 "The (conceptual) table listing the router's PIM interfaces. 202 IGMP and PIM are enabled on all interfaces listed in this 203 table." 204 ::= { pim 2 } 206 pimInterfaceEntry OBJECT-TYPE 207 SYNTAX PimInterfaceEntry 208 MAX-ACCESS not-accessible 209 STATUS current 210 DESCRIPTION 211 "An entry (conceptual row) in the pimInterfaceTable." 212 INDEX { pimInterfaceIfIndex } 213 ::= { pimInterfaceTable 1 } 215 PimInterfaceEntry ::= SEQUENCE { 216 pimInterfaceIfIndex InterfaceIndex, 217 pimInterfaceAddress IpAddress, 218 pimInterfaceNetMask IpAddress, 219 pimInterfaceMode INTEGER, 220 pimInterfaceDR IpAddress, 221 pimInterfaceHelloInterval Integer32, 222 pimInterfaceStatus RowStatus, 223 pimInterfaceJoinPruneInterval Integer32, 224 pimInterfaceCBSRPreference Integer32, 225 pimInterfaceTrigHelloInterval Integer32, 226 pimInterfaceHelloHoldtime Integer32, 227 pimInterfaceLanPruneDelay BITS, 228 pimInterfacePropagationDelay Integer32, 229 pimInterfaceOverrideInterval Integer32, 230 pimInterfaceGenerationID BITS, 231 pimInterfaceJoinPruneHoldtime Integer32, 232 pimInterfaceGraftRetryInterval Integer32, 233 pimInterfaceMaxGraftRetries Integer32, 234 pimInterfaceSRTTLThreshold Integer32, 235 pimInterfaceLanDelayEnabled TruthValue, 236 pimInterfaceSRCapable TruthValue, 237 pimInterfaceDRPriority Integer32 238 } 240 pimInterfaceIfIndex OBJECT-TYPE 241 SYNTAX InterfaceIndex 242 MAX-ACCESS not-accessible 243 STATUS current 244 DESCRIPTION 245 "The ifIndex value of this PIM interface." 246 ::= { pimInterfaceEntry 1 } 248 pimInterfaceAddress OBJECT-TYPE 249 SYNTAX IpAddress 250 MAX-ACCESS read-only 251 STATUS current 252 DESCRIPTION 253 "The IP address of the PIM interface." 254 ::= { pimInterfaceEntry 2 } 256 pimInterfaceNetMask OBJECT-TYPE 257 SYNTAX IpAddress 258 MAX-ACCESS read-only 259 STATUS current 260 DESCRIPTION 261 "The network mask for the IP address of the PIM interface." 262 ::= { pimInterfaceEntry 3 } 264 pimInterfaceMode OBJECT-TYPE 265 SYNTAX INTEGER { dense(1), sparse(2), sparseDense(3) } 266 MAX-ACCESS read-create 267 STATUS current 268 DESCRIPTION 269 "The configured mode of this PIM interface. A value of 270 sparseDense is only valid for PIMv1." 271 DEFVAL { dense } 272 ::= { pimInterfaceEntry 4 } 274 pimInterfaceDR OBJECT-TYPE 275 SYNTAX IpAddress 276 MAX-ACCESS read-only 277 STATUS current 278 DESCRIPTION 279 "The Designated Router on this PIM interface." 280 ::= { pimInterfaceEntry 5 } 282 pimInterfaceHelloInterval OBJECT-TYPE 283 SYNTAX Integer32 284 UNITS "seconds" 285 MAX-ACCESS read-create 286 STATUS current 287 DESCRIPTION 288 "The frequency at which PIM Hello messages are transmitted 289 on this interface." 290 DEFVAL { 30 } 291 ::= { pimInterfaceEntry 6 } 293 pimInterfaceStatus OBJECT-TYPE 294 SYNTAX RowStatus 295 MAX-ACCESS read-create 296 STATUS current 297 DESCRIPTION 298 "The status of this entry. Creating the entry enables PIM 299 on the interface; destroying the entry disables PIM on the 300 interface." 301 ::= { pimInterfaceEntry 7 } 303 pimInterfaceJoinPruneInterval OBJECT-TYPE 304 SYNTAX Integer32 305 UNITS "seconds" 306 MAX-ACCESS read-create 307 STATUS current 308 DESCRIPTION 309 "The frequency at which PIM Join/Prune messages are 310 transmitted on this PIM interface. The default value of 311 this object is the pimJoinPruneInterval." 312 ::= { pimInterfaceEntry 8 } 314 pimInterfaceCBSRPreference OBJECT-TYPE 315 SYNTAX Integer32 (-1..255) 316 MAX-ACCESS read-create 317 STATUS current 318 DESCRIPTION 319 "The preference value for the local interface as a candidate 320 bootstrap router. The value of -1 is used to indicate that 321 the local interface is not a candidate BSR interface." 322 DEFVAL { 0 } 323 ::= { pimInterfaceEntry 9 } 325 pimInterfaceTrigHelloInterval OBJECT-TYPE 326 SYNTAX Integer32 327 UNITS "seconds" 328 MAX-ACCESS read-create 329 STATUS current 330 DESCRIPTION "The maximum time before a triggered PIM Hello message 331 is transmitted on this interface." 332 DEFVAL { 5 } 333 ::= { pimInterfaceEntry 10 } 335 pimInterfaceHelloHoldtime OBJECT-TYPE 336 SYNTAX Integer32 (0..65535) 337 UNITS "seconds" 338 MAX-ACCESS read-create 339 STATUS current 340 DESCRIPTION "The value set in the Holdtime field of Hello messages 341 transmitted on this interface. This should be 3.5 342 times the value of pimInterfaceHelloInterval." 343 DEFVAL { 105 } 344 ::= { pimInterfaceEntry 11 } 346 pimInterfaceLanPruneDelay OBJECT-TYPE 347 SYNTAX BITS { off (0), on (1) } 348 MAX-ACCESS read-create 349 STATUS current 350 DESCRIPTION "Turns the LAN Prune Delay Option off and on on this 351 interface." 352 DEFVAL { off } 353 ::= { pimInterfaceEntry 12 } 355 pimInterfacePropagationDelay OBJECT-TYPE 356 SYNTAX Integer32 (0..32767) 357 UNITS "milliseconds" 358 MAX-ACCESS read-create 359 STATUS current 360 DESCRIPTION "The value inserted into the LAN Prune Delay field of a 361 LAN Prune Delay option on this interface." 362 DEFVAL { 500 } 363 ::= { pimInterfaceEntry 13 } 365 pimInterfaceOverrideInterval OBJECT-TYPE 366 SYNTAX Integer32 (0..65535) 367 MAX-ACCESS read-create 368 STATUS current 369 DESCRIPTION "The value inserted into the Override Interval field of 370 a LAN Prune Delay option on this interface." 371 DEFVAL { 2500 } 372 ::= { pimInterfaceEntry 14 } 374 pimInterfaceGenerationID OBJECT-TYPE 375 SYNTAX BITS { off (0), on (1) } 376 MAX-ACCESS read-create 377 STATUS current 378 DESCRIPTION "Turns the Generation ID Option off and on on this 379 interface." 380 DEFVAL { off } 381 ::= { pimInterfaceEntry 15 } 383 pimInterfaceJoinPruneHoldtime OBJECT_TYPE 384 SYNTAX Integer32 (0..65535) 385 UNITS "seconds" 386 MAX-ACCESS read-create 387 STATUS current 388 DESCRIPTION "The value inserted into the Holdtime field of a Join/ 389 Prune message sent on this interface. The value should 390 be 3.5 times pimInterfaceJoinPruneInterval." 391 DEFVAL { 210 } 392 ::= { pimInterfaceEntry 16 } 394 pimInterfaceGraftRetryInterval OBJECT-TYPE 395 SYNTAX Integer32 396 UNITS "seconds" 397 MAX-ACCESS read-create 398 STATUS current 399 DESCRIPTION "The interval a PIM router waits for a Graft Ack before 400 resending a Graft on this interface." 401 DEFVAL { 3 } 402 ::= { pimInterfaceEntry 17 } 404 pimInterfaceMaxGraftRetries OBJECT-TYPE 405 SYNTAX Integer32 406 MAX-ACCESS read-create 407 STATUS current 408 DESCRIPTION "The maximum number of times this router will resend a 409 Graft on this interface." 410 DEFVAL { 2 } 411 ::= { pimInterfaceEntry 18 } 413 pimInterfaceSRTTLThreshold OBJECT-TYPE 414 SYNTAX Integer32 415 MAX-ACCESS read-create 416 STATUS current 417 DESCRIPTION "The Time To Live in a PIM-DM State Refresh message at 418 which it is not forwarded on this interface." 419 DEFVAL { 0 } 420 ::= { pimInterfaceEntry 19 } 422 pimInterfaceLanDelayEnabled OBJECT-TYPE 423 SYNTAX TruthValue 424 MAX-ACCESS read-only 425 STATUS current 426 DESCRIPTION "Evaluates to TRUE if all routers on this interface are 427 using the LAN Prune Delay Option." 428 ::= { pimInterfaceEntry 20 } 430 pimInterfaceSRCapable OBJECT-TYPE 431 SYNTAX TruthValue 432 MAX-ACCESS read-only 433 STATUS current 434 DESCRIPTION "Evaluates to TRUE if all routers on this interface are 435 using the State Refresh Capable Option." 436 ::= { pimInterfaceEntry 21 } 438 pimInterfaceDRPriority OBJECT-TYPE 439 SYNTAX Integer32 440 MAX-ACCESS read-create 441 STATUS current 442 DESCRIPTION "The Designater Router Priority inserted into the DR 443 priority option on this interface." 444 DEFVAL { 1 } 445 ::= { pimInterfaceEntry 22 } 447 -- The PIM Neighbor Table 449 pimNeighborTable OBJECT-TYPE 450 SYNTAX SEQUENCE OF PimNeighborEntry 451 MAX-ACCESS not-accessible 452 STATUS current 453 DESCRIPTION 454 "The (conceptual) table listing the router's PIM neighbors." 455 ::= { pim 3 } 457 pimNeighborEntry OBJECT-TYPE 458 SYNTAX PimNeighborEntry 459 MAX-ACCESS not-accessible 460 STATUS current 461 DESCRIPTION 462 "An entry (conceptual row) in the pimNeighborTable." 463 INDEX { pimNeighborAddress } 464 ::= { pimNeighborTable 1 } 466 PimNeighborEntry ::= SEQUENCE { 467 pimNeighborAddress IpAddress, 468 pimNeighborIfIndex InterfaceIndex, 469 pimNeighborUpTime TimeTicks, 470 pimNeighborExpiryTime TimeTicks, 471 pimNeighborMode INTEGER, 472 pimNeighborLanPruneDelay Integer32, 473 pimNeighborOverrideInterval Integer32, 474 pimNeighborTBit BITS, 475 pimNeighborSRCapable TruthValue, 476 pimNeighborDRPresent TruthValue 477 } 479 pimNeighborAddress OBJECT-TYPE 480 SYNTAX IpAddress 481 MAX-ACCESS not-accessible 482 STATUS current 483 DESCRIPTION 484 "The IP address of the PIM neighbor for which this entry 485 contains information." 486 ::= { pimNeighborEntry 1 } 488 pimNeighborIfIndex OBJECT-TYPE 489 SYNTAX InterfaceIndex 490 MAX-ACCESS read-only 491 STATUS current 492 DESCRIPTION 493 "The value of ifIndex for the interface used to reach this 494 PIM neighbor." 495 ::= { pimNeighborEntry 2 } 497 pimNeighborUpTime OBJECT-TYPE 498 SYNTAX TimeTicks 499 MAX-ACCESS read-only 500 STATUS current 501 DESCRIPTION 502 "The time since this PIM neighbor (last) became a neighbor 503 of the local router." 504 ::= { pimNeighborEntry 3 } 506 pimNeighborExpiryTime OBJECT-TYPE 507 SYNTAX TimeTicks 508 MAX-ACCESS read-only 509 STATUS current 510 DESCRIPTION 511 "The minimum time remaining before this PIM neighbor will be 512 aged out." 513 ::= { pimNeighborEntry 4 } 515 pimNeighborMode OBJECT-TYPE 516 SYNTAX INTEGER { dense(1), sparse(2) } 517 MAX-ACCESS read-only 518 STATUS deprecated 519 DESCRIPTION 520 "The active PIM mode of this neighbor. This object is 521 deprecated for PIMv2 routers since all neighbors on the 522 interface must be either dense or sparse as determined by 523 the protocol running on the interface." 524 ::= { pimNeighborEntry 5 } 526 pimNeighborLANPruneDelay OBJECT-TYPE 527 SYNTAX Integer32 528 MAX-ACCESS read-only 529 STATUS current 530 DESCRIPTION "The value of LAN Prune Delay field of the LAN Prune 531 Delay Option received from this neighbor. A value of 532 0 indicates that no LAN Prune Delay Option was 533 received from this neigbor." 534 ::= { pimNeighborEntry 6 } 536 pimNeighborOverrideInterval OBJECT-TYPE 537 SYNTAX Integer32 538 MAX-ACCESS read-only 539 STATUS current 540 DESCRIPTION "The value of Override Interval field of the LAN Prune 541 Delay Option received from this neighbor. A value of 542 0 indicates that no LAN Prune Delay Option was 543 received from this neigbor." 544 ::= { pimNeighborEntry 7 } 546 pimNeighborTBit OBJECT-TYPE 547 SYNTAX BITS 548 MAX-ACCESS read-only 549 STATUS current 550 DESCRIPTION "The value of the T bit field of the LAN Prune 551 Delay Option received from this neighbor. The T bit 552 specifies the ability of the neighbor to disable 553 join suppression." 554 ::= { pimNeighborEntry 8 } 556 pimNeighborSRCapable OBJECT-TYPE 557 SYNTAX TruthValue 558 MAX-ACCESS read-only 559 STATUS current 560 DESCRIPTION "Evaluates to TRUE if this neighbor is using the State 561 Refresh Capable Option." 562 ::= { pimNeighborEntry 9 } 564 pimNeighborDRPresent OBJECT-TYPE 565 SYNTAX TruthValue 566 MAX-ACCESS read-only 567 STATUS current 568 DESCRIPTION "Evaluates to TRUE if this neighbor is using the 569 Designated Router Option." 570 ::= { pimNeighborEntry 10 } 572 -- 573 -- The PIM IP Multicast Route Table 574 -- 576 pimIpMRouteTable OBJECT-TYPE 577 SYNTAX SEQUENCE OF PimIpMRouteEntry 578 MAX-ACCESS not-accessible 579 STATUS current 580 DESCRIPTION 581 "The (conceptual) table listing PIM-specific information on 582 a subset of the rows of the ipMRouteTable defined in the IP 583 Multicast MIB." 584 ::= { pim 4 } 586 pimIpMRouteEntry OBJECT-TYPE 587 SYNTAX PimIpMRouteEntry 588 MAX-ACCESS not-accessible 589 STATUS current 590 DESCRIPTION 591 "An entry (conceptual row) in the pimIpMRouteTable. There 592 is one entry per entry in the ipMRouteTable whose incoming 593 interface is running PIM." 594 INDEX { ipMRouteGroup, ipMRouteSource, ipMRouteSourceMask } 595 ::= { pimIpMRouteTable 1 } 597 PimIpMRouteEntry ::= SEQUENCE { 598 pimIpMRouteUpstreamAssertTimer TimeTicks, 599 pimIpMRouteAssertMetric Integer32, 600 pimIpMRouteAssertMetricPref Integer32, 601 pimIpMRouteAssertRPTBit TruthValue, 602 pimIpMRouteFlags BITS, 603 pimIpMRouteRPFNeighbor IpAddress, 604 pimIpMRouteSourceTimer TimeTicks, 605 pimIpMRouteOriginatorSRTTL Integer32 606 } 608 pimIpMRouteUpstreamAssertTimer OBJECT-TYPE 609 SYNTAX TimeTicks 610 MAX-ACCESS read-only 611 STATUS current 612 DESCRIPTION 613 "The time remaining before the router changes its upstream 614 neighbor back to its RPF neighbor. This timer is called the 615 Assert timer in the PIM Sparse and Dense mode specification. 616 A value of 0 indicates that no Assert has changed the 617 upstream neighbor away from the RPF neighbor." 618 ::= { pimIpMRouteEntry 1 } 620 pimIpMRouteAssertMetric OBJECT-TYPE 621 SYNTAX Integer32 622 MAX-ACCESS read-only 623 STATUS current 624 DESCRIPTION 625 "The metric advertised by the assert winner on the upstream 626 interface, or 0 if no such assert is in received." 627 ::= { pimIpMRouteEntry 2 } 629 pimIpMRouteAssertMetricPref OBJECT-TYPE 630 SYNTAX Integer32 631 MAX-ACCESS read-only 632 STATUS current 633 DESCRIPTION 634 "The preference advertised by the assert winner on the 635 upstream interface, or 0 if no such assert is in effect." 636 ::= { pimIpMRouteEntry 3 } 638 pimIpMRouteAssertRPTBit OBJECT-TYPE 639 SYNTAX TruthValue 640 MAX-ACCESS read-only 641 STATUS current 642 DESCRIPTION 643 "The value of the RPT-bit advertised by the assert winner on 644 the upstream interface, or false if no such assert is in 645 effect." 646 ::= { pimIpMRouteEntry 4 } 648 pimIpMRouteFlags OBJECT-TYPE 649 SYNTAX BITS { 650 rpt(0), 651 spt(1) 652 } 653 MAX-ACCESS read-only 654 STATUS current 655 DESCRIPTION 656 "This object describes PIM-specific flags related to a 657 multicast state entry. See the PIM Sparse Mode 658 specification for the meaning of the RPT and SPT bits." 659 ::= { pimIpMRouteEntry 5 } 661 pimIpMRouteRPFNeighbor OBJECT-TYPE 662 SYNTAX IpAddress 663 MAX-ACCESS read-only 664 STATUS current 665 DESCRIPTION "The IP Address of the current RPF neighbor. If there 666 is an upstream Assert Winner, it will be the RPF 667 neighbor. Otherwise, the RPF neighbor will be 668 the next hop indicated by unicast routing." 669 ::= { pimIpMRouteEntry 6 } 671 pimIpMRouteSourceTimer OBJECT-TYPE 672 SYNTAX TimeTicks 673 MAX-ACCESS read-only 674 STATUS current 675 DESCRIPTION "The time before this router ceases originating State 676 Refresh messages for this route." 677 ::= { pimIpMRouteEntry 7 } 679 pimIpMRouteOriginatorSRTTL OBJECT-TYPE 680 SYNTAX Integer32 681 MAX_ACCESS read-only 682 STATUS current 683 DESCRIPTION "The TTL used in State Refresh messages originated by 684 this router for this route." 685 ::= { pimIpMRouteEntry 8 } 687 -- 688 -- The PIM Next Hop Table 689 -- 691 pimIpMRouteNextHopTable OBJECT-TYPE 692 SYNTAX SEQUENCE OF PimIpMRouteNextHopEntry 693 MAX-ACCESS not-accessible 694 STATUS current 695 DESCRIPTION 696 "The (conceptual) table listing PIM-specific information on 697 a subset of the rows of the ipMRouteNextHopTable defined in 698 the IP Multicast MIB." 699 ::= { pim 7 } 701 pimIpMRouteNextHopEntry OBJECT-TYPE 702 SYNTAX PimIpMRouteNextHopEntry 703 MAX-ACCESS not-accessible 704 STATUS current 705 DESCRIPTION 706 "An entry (conceptual row) in the pimIpMRouteNextHopTable. 707 There is one entry per entry in the ipMRouteNextHopTable 708 whose interface is running PIM and whose 709 ipMRouteNextHopState is pruned(1)." 710 INDEX { ipMRouteNextHopGroup, ipMRouteNextHopSource, 711 ipMRouteNextHopSourceMask, ipMRouteNextHopIfIndex, 712 ipMRouteNextHopAddress } 713 ::= { pimIpMRouteNextHopTable 1 } 715 PimIpMRouteNextHopEntry ::= SEQUENCE { 716 pimIpMRouteNextHopPruneReason INTEGER, 717 pimIpMRouteNextHopAssertWinner IpAddress, 718 pimIpMRouteNextHopAssertTimer TimeTicks, 719 pimIpMRouteNextHopAssertMetric Integer32, 720 pimIpMRouteNextHopAssertMetricPref Integer32, 721 pimIpMRouteNextHopJoinPruneTimer TimeTicks 722 } 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 } 754 pimIpMRouteNextHopAssertMetric OBJECT-TYPE 755 SYNTAX Integer32 756 MAX-ACCESS read-only 757 STATUS current 758 DESCRIPTION "The metric advertised by the Assert Winner." 759 ::= { pimIpMRouteNextHopEntry 5 } 761 pimIpMRouteNextHopAssertMetricPref OBJECT-TYPE 762 SYNTAX Integer32 763 MAX-ACCESS read-only 764 STATUS current 765 DESCRIPTION "The metric preference advertised by the Assert Winner." 766 ::= { pimIpMRouteNextHopEntry 6 } 768 pimIpMRouteNextHopJoinPruneTimer OBJECT-TYPE 769 SYNTAX TimeTicks 770 MAX-ACCESS read-only 771 STATUS current 772 DESCRIPTION "The time remaining before the PIM router reverts to 773 default operation on this interface. PIM-SM will 774 cease forwarding, PIM-DM will resume forwarding." 775 ::= { pimIpMRouteNextHopEntry 7 } 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 { pimRPGroupAddress, pimRPAddress } 798 ::= { pimRPTable 1 } 800 PimRPEntry ::= SEQUENCE { 801 pimRPGroupAddress IpAddress, 802 pimRPAddress IpAddress, 803 pimRPState INTEGER, 804 pimRPStateTimer TimeTicks, 805 pimRPLastChange TimeTicks, 806 pimRPRowStatus RowStatus 807 } 809 pimRPGroupAddress OBJECT-TYPE 810 SYNTAX IpAddress 811 MAX-ACCESS not-accessible 812 STATUS deprecated 813 DESCRIPTION 814 "The IP multicast group address for which this entry 815 contains information about an RP." 816 ::= { pimRPEntry 1 } 818 pimRPAddress OBJECT-TYPE 819 SYNTAX IpAddress 820 MAX-ACCESS not-accessible 821 STATUS deprecated 822 DESCRIPTION 823 "The unicast address of the RP." 824 ::= { pimRPEntry 2 } 826 pimRPState OBJECT-TYPE 827 SYNTAX INTEGER { up(1), down(2) } 828 MAX-ACCESS read-only 829 STATUS deprecated 830 DESCRIPTION 831 "The state of the RP." 832 ::= { pimRPEntry 3 } 834 pimRPStateTimer OBJECT-TYPE 835 SYNTAX TimeTicks 836 MAX-ACCESS read-only 837 STATUS deprecated 838 DESCRIPTION 839 "The minimum time remaining before the next state change. 840 When pimRPState is up, this is the minimum time which must 841 expire until it can be declared down. When pimRPState is 842 down, this is the time until it will be declared up (in 843 order to retry)." 844 ::= { pimRPEntry 4 } 846 pimRPLastChange OBJECT-TYPE 847 SYNTAX TimeTicks 848 MAX-ACCESS read-only 849 STATUS deprecated 850 DESCRIPTION 851 "The value of sysUpTime at the time when the corresponding 852 instance of pimRPState last changed its value." 853 ::= { pimRPEntry 5 } 855 pimRPRowStatus OBJECT-TYPE 856 SYNTAX RowStatus 857 MAX-ACCESS read-create 858 STATUS deprecated 859 DESCRIPTION 860 "The status of this row, by which new entries may be 861 created, or old entries deleted from this table." 862 ::= { pimRPEntry 6 } 864 -- The PIM RP-Set Table 866 pimRPSetTable OBJECT-TYPE 867 SYNTAX SEQUENCE OF PimRPSetEntry 868 MAX-ACCESS not-accessible 869 STATUS current 870 DESCRIPTION 871 "The (conceptual) table listing PIM information for 872 candidate Rendezvous Points (RPs) for IP multicast groups. 873 When the local router is the BSR, this information is 874 obtained from received Candidate-RP-Advertisements. When 875 the local router is not the BSR, this information is 876 obtained from received RP-Set messages." 877 ::= { pim 6 } 879 pimRPSetEntry OBJECT-TYPE 880 SYNTAX PimRPSetEntry 881 MAX-ACCESS not-accessible 882 STATUS current 883 DESCRIPTION 884 "An entry (conceptual row) in the pimRPSetTable." 885 INDEX { pimRPSetComponent, pimRPSetGroupAddress, 886 pimRPSetGroupMask, pimRPSetAddress } 887 ::= { pimRPSetTable 1 } 889 PimRPSetEntry ::= SEQUENCE { 891 pimRPSetGroupAddress IpAddress, 892 pimRPSetGroupMask IpAddress, 893 pimRPSetAddress IpAddress, 894 pimRPSetHoldTime Integer32, 895 pimRPSetExpiryTime TimeTicks, 896 pimRPSetComponent Integer32 897 } 898 pimRPSetGroupAddress OBJECT-TYPE 899 SYNTAX IpAddress 900 MAX-ACCESS not-accessible 901 STATUS current 902 DESCRIPTION 903 "The IP multicast group address which, when combined with 904 pimRPSetGroupMask, gives the group prefix for which this 905 entry contains information about the Candidate-RP." 906 ::= { pimRPSetEntry 1 } 908 pimRPSetGroupMask OBJECT-TYPE 909 SYNTAX IpAddress 910 MAX-ACCESS not-accessible 911 STATUS current 912 DESCRIPTION 913 "The multicast group address mask which, when combined with 914 pimRPSetGroupAddress, gives the group prefix for which this 915 entry contains information about the Candidate-RP." 916 ::= { pimRPSetEntry 2 } 918 pimRPSetAddress OBJECT-TYPE 919 SYNTAX IpAddress 920 MAX-ACCESS not-accessible 921 STATUS current 922 DESCRIPTION 923 "The IP address of the Candidate-RP." 924 ::= { pimRPSetEntry 3 } 926 pimRPSetHoldTime OBJECT-TYPE 927 SYNTAX Integer32 (0..255) 928 UNITS "seconds" 929 MAX-ACCESS read-only 930 STATUS current 931 DESCRIPTION 932 "The holdtime of a Candidate-RP. If the local router is not 933 the BSR, this value is 0." 934 ::= { pimRPSetEntry 4 } 936 pimRPSetExpiryTime OBJECT-TYPE 937 SYNTAX TimeTicks 938 MAX-ACCESS read-only 939 STATUS current 940 DESCRIPTION 941 "The minimum time remaining before the Candidate-RP will be 942 declared down. If the local router is not the BSR, this 943 value is 0." 944 ::= { pimRPSetEntry 5 } 946 pimRPSetComponent OBJECT-TYPE 947 SYNTAX Integer32 (1..255) 948 MAX-ACCESS not-accessible 949 STATUS current 950 DESCRIPTION 951 " A number uniquely identifying the component. Each 952 protocol instance connected to a separate domain should have 953 a different index value." 954 ::= { pimRPSetEntry 6 } 956 -- 957 -- Note: { pim 8 } through { pim 10 } were used in older versions 958 -- of this MIB. Since some earlier versions of this MIB have been 959 -- widely-deployed, these values must not be used in the future, 960 -- as long the MIB is rooted under { experimental 61 }. 961 -- 963 -- The PIM Candidate-RP Table 965 pimCandidateRPTable OBJECT-TYPE 966 SYNTAX SEQUENCE OF PimCandidateRPEntry 967 MAX-ACCESS not-accessible 968 STATUS current 969 DESCRIPTION 970 "The (conceptual) table listing the IP multicast groups for 971 which the local router is to advertise itself as a 972 Candidate-RP when the value of pimComponentCRPHoldTime is 973 non-zero. If this table is empty, then the local router 974 will advertise itself as a Candidate-RP for all groups 975 (providing the value of pimComponentCRPHoldTime is non- 976 zero)." 977 ::= { pim 11 } 979 pimCandidateRPEntry OBJECT-TYPE 980 SYNTAX PimCandidateRPEntry 981 MAX-ACCESS not-accessible 982 STATUS current 983 DESCRIPTION 984 "An entry (conceptual row) in the pimCandidateRPTable." 985 INDEX { pimCandidateRPGroupAddress, 986 pimCandidateRPGroupMask } 987 ::= { pimCandidateRPTable 1 } 989 PimCandidateRPEntry ::= SEQUENCE { 990 pimCandidateRPGroupAddress IpAddress, 991 pimCandidateRPGroupMask IpAddress, 992 pimCandidateRPAddress IpAddress, 993 pimCandidateRPRowStatus RowStatus 994 } 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 } 1067 pimComponentIndex OBJECT-TYPE 1068 SYNTAX Integer32 (1..255) 1069 MAX-ACCESS not-accessible 1070 STATUS current 1071 DESCRIPTION 1072 "A number uniquely identifying the component. Each protocol 1073 instance connected to a separate domain should have a 1074 different index value. Routers that only support membership 1075 in a single PIM-SM domain should use a pimComponentIndex 1076 value of 1." 1077 ::= { pimComponentEntry 1 } 1079 pimComponentBSRAddress OBJECT-TYPE 1080 SYNTAX IpAddress 1081 MAX-ACCESS read-only 1082 STATUS current 1083 DESCRIPTION 1084 "The IP address of the bootstrap router (BSR) for the local 1085 PIM region." 1086 ::= { pimComponentEntry 2 } 1088 pimComponentBSRExpiryTime OBJECT-TYPE 1089 SYNTAX TimeTicks 1090 MAX-ACCESS read-only 1091 STATUS current 1092 DESCRIPTION 1093 "The minimum time remaining before the bootstrap router in 1094 the local domain will be declared down. For candidate BSRs, 1095 this is the time until the component sends an RP-Set 1096 message. For other routers, this is the time until it may 1097 accept an RP-Set message from a lower candidate BSR." 1098 ::= { pimComponentEntry 3 } 1100 pimComponentCRPHoldTime OBJECT-TYPE 1101 SYNTAX Integer32 (0..255) 1102 UNITS "seconds" 1103 MAX-ACCESS read-create 1104 STATUS current 1105 DESCRIPTION 1106 "The holdtime of the component when it is a candidate RP in 1107 the local domain. The value of 0 is used to indicate that 1108 the local system is not a Candidate-RP." 1109 DEFVAL { 0 } 1110 ::= { pimComponentEntry 4 } 1112 pimComponentStatus OBJECT-TYPE 1113 SYNTAX RowStatus 1114 MAX-ACCESS read-create 1115 STATUS current 1116 DESCRIPTION 1117 "The status of this entry. Creating the entry creates 1118 another protocol instance; destroying the entry disables a 1119 protocol instance." 1120 ::= { pimComponentEntry 5 } 1122 -- PIM State Refresh Objects 1124 pimSourceLifetime OBJECT-TYPE 1125 SYNTAX Integer32 1126 UNITS "seconds" 1127 MAX-ACCESS read-create 1128 STATUS current 1129 DESCRIPTION "The maximum time this router will continue to 1130 originate State Refresh messages in the absence of 1131 traffic from the source itself." 1132 DEFVAL { 210 } 1133 ::= { pim 13 } 1135 pimStateRefreshInterval OBJECT-TYPE 1136 SYNTAX Integer32 (1..255) 1137 UNITS "seconds" 1138 MAX-ACCESS read-create 1139 STATUS current 1140 DESCRIPTION "The interval between successive State Refresh 1141 messages originated by this router." 1142 DEFVAL { 60 } 1143 ::= { pim 14 } 1145 pimStateRefreshLimitInterval OBJECT-TYPE 1146 SYNTAX TimeTicks 1147 MAX-ACCESS read-create 1148 STATUS current 1149 DESCRIPTION "This router will not forward successive State Refresh 1150 messages received at less than this interval." 1151 DEFVAL { 0 } 1152 ::= { pim 15 } 1154 pimStateRefreshTimeToLive OBJECT-TYPE 1155 SYNTAX Integer32 1156 MAX-ACCESS read-create 1157 STATUS current 1158 DESCRIPTION "The TTL to be used by this router's originated State 1159 Refresh messages if the data packet's TTL is not 1160 recorded." 1161 DEFVAL { 16 } 1162 ::= { pim 16 } 1163 -- PIM Traps 1165 pimNeighborLoss NOTIFICATION-TYPE 1166 OBJECTS { 1167 pimNeighborIfIndex 1168 } 1169 STATUS current 1170 DESCRIPTION 1171 "A pimNeighborLoss trap signifies the loss of an adjacency 1172 with a neighbor. This trap should be generated when the 1173 neighbor timer expires, and the router has no other 1174 neighbors on the same interface with a lower IP address than 1175 itself." 1176 ::= { pimTraps 1 } 1178 -- conformance information 1180 pimMIBConformance OBJECT IDENTIFIER ::= { pimMIB 2 } 1181 pimMIBCompliances OBJECT IDENTIFIER ::= { pimMIBConformance 1 } 1182 pimMIBGroups OBJECT IDENTIFIER ::= { pimMIBConformance 2 } 1184 -- compliance statements 1186 pimV1MIBCompliance MODULE-COMPLIANCE 1187 STATUS deprecated 1188 DESCRIPTION 1189 "The compliance statement for routers running PIMv1 and 1190 implementing the PIM MIB." 1191 MODULE -- this module 1192 MANDATORY-GROUPS { pimV1MIBGroup } 1194 ::= { pimMIBCompliances 1 } 1196 pimSparseV2MIBCompliance MODULE-COMPLIANCE 1197 STATUS current 1198 DESCRIPTION 1199 "The compliance statement for routers running PIM Sparse 1200 Mode and implementing the PIM MIB." 1201 MODULE -- this module 1202 MANDATORY-GROUPS { pimV2MIBGroup } 1204 GROUP pimV2CandidateRPMIBGroup 1205 DESCRIPTION 1206 "This group is mandatory if the router is capable of being a 1207 Candidate RP." 1209 OBJECT pimInterfaceStatus 1210 MIN-ACCESS read-only 1211 DESCRIPTION 1212 "Write access is not required." 1214 ::= { pimMIBCompliances 2 } 1216 pimDenseV2MIBCompliance MODULE-COMPLIANCE 1217 STATUS current 1218 DESCRIPTION 1219 "The compliance statement for routers running PIM Dense Mode 1220 and implementing the PIM MIB." 1221 MODULE -- this module 1223 MANDATORY-GROUPS { pimDenseV2MIBGroup } 1225 OBJECT pimInterfaceStatus 1226 MIN-ACCESS read-only 1227 DESCRIPTION 1228 "Write access is not required." 1230 ::= { pimMIBCompliances 3 } 1232 -- units of conformance 1234 pimNotificationGroup NOTIFICATION-GROUP 1235 NOTIFICATIONS { pimNeighborLoss } 1236 STATUS current 1237 DESCRIPTION 1238 "A collection of notifications for signaling important PIM 1239 events." 1240 ::= { pimMIBGroups 1 } 1242 pimV2MIBGroup OBJECT-GROUP 1243 OBJECTS { pimJoinPruneInterval, pimInterfaceIfIndex, 1244 pimInterfaceAddress, pimInterfaceNetMask, 1245 pimInterfaceMode, pimInterfaceDR, 1246 pimInterfaceHelloInterval, pimInterfaceStatus, 1247 pimInterfaceJoinPruneInterval, 1248 pimInterfaceCBSRPreference, pimInterfaceTrigHelloInterval, 1249 pimInterfaceHelloHoldtime, pimInterfaceLanPruneDelay, 1250 pimInterfacePropagationDelay, 1251 pimInterfaceOverrideInterval, pimInterfaceGenerationID, 1252 pimInterfaceJoinPruneHoldtime, 1253 pimInterfaceLanDelayEnabled, pimInterfaceDRPriority, 1254 pimNeighborAddress, pimNeighborInterfaceIfIndex, 1255 pimNeighborUpTime, pimNeighborExpiryTime, 1256 pimNeighborLANPruneDelay, pimNeighborOverrideInterval, 1257 pimNeighborTBit, pimNeighborDRPresent, 1258 pimIpMRouteUpstreamAssertTimer, pimIpMRouteAssertMetric, 1259 pimIpMRouteIpRouteAssertMetricPref, 1260 pimIpMRouteAssertRPTBit, pimIpMRouteFlags, 1261 pimIpMRouteRPFNeighbor, pimIpMRouteNextHopPruneReason, 1262 pimRPSetGroupAddress, pimRPSetGroupMask, pimRPSetAddress, 1263 pimRPSetHoldTime, pimRPSetExpiryTime, pimRPSetComponent, 1264 pimComponentBSRAddress, pimComponentBSRExpiryTime, 1265 pimComponentCRPHoldTime, pimComponentStatus 1266 } 1267 STATUS current 1268 DESCRIPTION 1269 "A collection of objects to support management of PIM Sparse 1270 Mode (version 2) routers." 1271 ::= { pimMIBGroups 2 } 1273 pimDenseV2MIBGroup OBJECT-GROUP 1274 OBJECTS { pimInterfaceIfIndex, pimInterfaceAddress, 1275 pimInterfaceNetMask, pimInterfaceHelloInterval, 1276 pimInterfaceStatus, pimInterfaceTrigHelloInterval, 1277 pimInterfaceHelloHoldtime, pimInterfaceLanPruneDelay, 1278 pimInterfacePropagationDelay, pimInterfaceOverrideInterval, 1279 pimInterfaceGenerationID, pimInterfaceJoinPruneHoldtime, 1280 pimInterfaceGraftRetryInterval, 1281 pimInterfaceMaxGraftRetries, pimInterfaceSRTTLThreshold, 1282 pimInterfaceLanDelayEnabled, pimInterfaceSRCapable, 1283 pimNeighborIfIndex, pimNeighborUpTime, 1284 pimNeighborExpiryTime, pimNeighborLANPruneDelay, 1285 pimNeighborOverrideInterval, pimNeighborSRCapable, 1286 pimIpMRouteSourceTimer, pimIpMRouteOriginatorSRTTL, 1287 pimSourceLifetime, pimStateRefreshInterval, 1288 pimStateRefreshLimitInterval, pimStateRefreshTimeToLive 1289 } 1290 STATUS current 1291 DESCRIPTION 1292 "A collection of objects to support management of PIM Dense 1293 Mode (version 2) routers." 1294 ::= { pimMIBGroups 5 } 1296 pimV2CandidateRPMIBGroup OBJECT-GROUP 1297 OBJECTS { pimCandidateRPAddress, 1298 pimCandidateRPRowStatus 1299 } 1300 STATUS current 1301 DESCRIPTION 1302 "A collection of objects to support configuration of which 1303 groups a router is to advertise itself as a Candidate-RP." 1304 ::= { pimMIBGroups 3 } 1306 pimV1MIBGroup OBJECT-GROUP 1307 OBJECTS { pimJoinPruneInterval, pimNeighborIfIndex, 1308 pimNeighborUpTime, pimNeighborExpiryTime, 1309 pimNeighborMode, 1310 pimInterfaceAddress, pimInterfaceNetMask, 1311 pimInterfaceJoinPruneInterval, pimInterfaceStatus, 1312 pimInterfaceMode, pimInterfaceDR, 1313 pimInterfaceHelloInterval, 1314 pimRPState, pimRPStateTimer, 1315 pimRPLastChange, pimRPRowStatus 1316 } 1317 STATUS deprecated 1318 DESCRIPTION 1319 "A collection of objects to support management of PIM 1320 (version 1) routers." 1321 ::= { pimMIBGroups 4 } 1323 pimNextHopGroup OBJECT-GROUP 1324 OBJECTS { pimIpMRouteNextHopPruneReason, 1325 pimIpMRouteNextHopAssertWinner, 1326 pimIpMRouteNextHopAssertTimer, 1327 pimIpMRouteNextHopAssertMetric, 1328 pimIpMRouteNextHopAssertMetricPref, 1329 pimIpMRouteNextHopJoinPruneTimer 1330 } 1331 STATUS current 1332 DESCRIPTION 1333 "A collection of optional objects to provide per-next hop 1334 information for diagnostic purposes. Supporting this group 1335 may add a large number of instances to a tree walk, but the 1336 information in this group can be extremely useful in 1337 tracking down multicast connectivity problems." 1338 ::= { pimMIBGroups 6 } 1340 pimAssertGroup OBJECT-GROUP 1341 OBJECTS { pimIpMRouteAssertMetric, pimIpMRouteAssertMetricPref, 1342 pimIpMRouteAssertRPTBit, pimIpMRouteRPFNeighbor} 1343 STATUS current 1344 DESCRIPTION 1345 "A collection of optional objects to provide extra 1346 information about the assert election process. There is no 1347 protocol reason to keep such information, but some 1348 implementations may already keep this information and make 1349 it available. These objects can also be very useful in 1350 debugging connectivity or duplicate packet problems, 1351 especially if the assert winner does not support the PIM and 1352 IP Multicast MIBs." 1353 ::= { pimMIBGroups 7 } 1355 END 1357 5. Security Considerations 1359 This MIB contains readable objects whose values provide information 1360 related to multicast routing, including information on the network 1361 topology. There are also a number of objects that have a MAX-ACCESS 1362 clause of read-write and/or read-create, which allow an administrator 1363 to configure PIM in the router. 1365 While unauthorized access to the readable objects is relatively 1366 innocuous, unauthorized access to the write-able objects could cause 1367 a denial of service. Hence, the support for SET operations in a 1368 non-secure environment without proper protection can have a negative 1369 effect on network operations. 1371 SNMPv1 by itself is such an insecure environment. Even if the 1372 network itself is secure (for example by using IPSec), even then, 1373 there is no control as to who on the secure network is allowed to 1374 access and SET (change/create/delete) the objects in this MIB. 1376 It is recommended that the implementers consider the security 1377 features as provided by the SNMPv3 framework. Specifically, the use 1378 of the User-based Security Model RFC 2274 [12] and the View-based 1379 Access Control Model RFC 2275 [15] is recommended. 1381 It is then a customer/user responsibility to ensure that the SNMP 1382 entity giving access to this MIB, is properly configured to give 1383 access to those objects only to those principals (users) that have 1384 legitimate rights to access them. 1386 6. Acknowledgements 1388 This MIB module has been updated based on feedback from the IETF's 1389 Protocol Independent 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-01.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.