idnits 2.17.00 (12 Aug 2021) /tmp/idnits21476/draft-thaler-idmr-multiproto-pimmib-00.txt: ** The Abstract section seems to be numbered 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: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 27 longer pages, the longest (page 26) being 60 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 are 1 instance of lines with non-RFC3849-compliant IPv6 addresses in the document. If these are example addresses, they should be changed. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 311: '...nterfaceDR. The value MUST be the same...' RFC 2119 keyword, line 696: '...ained in pimgRPAddress. The value MUST...' RFC 2119 keyword, line 836: '... MUST be the same as the ...' RFC 2119 keyword, line 961: '... value MUST be the same as t...' Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 2000) is 8003 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) -- Missing reference section? '1' on line 50 looks like a reference -- Missing reference section? '2' on line 50 looks like a reference -- Missing reference section? '3' on line 107 looks like a reference -- Missing reference section? '4' on line 107 looks like a reference -- Missing reference section? '5' on line 50 looks like a reference -- Missing reference section? '6' on line 52 looks like a reference -- Missing reference section? '7' on line 61 looks like a reference -- Missing reference section? '8' on line 66 looks like a reference -- Missing reference section? '9' on line 66 looks like a reference -- Missing reference section? '10' on line 66 looks like a reference -- Missing reference section? '11' on line 67 looks like a reference -- Missing reference section? '12' on line 1302 looks like a reference -- Missing reference section? '13' on line 68 looks like a reference -- Missing reference section? '14' on line 80 looks like a reference -- Missing reference section? '15' on line 1303 looks like a reference -- Missing reference section? '16' on line 76 looks like a reference -- Missing reference section? '17' on line 76 looks like a reference -- Missing reference section? '18' on line 76 looks like a reference -- Missing reference section? '19' on line 81 looks like a reference -- Missing reference section? '20' on line 83 looks like a reference -- Missing reference section? '21' on line 85 looks like a reference Summary: 6 errors (**), 0 flaws (~~), 4 warnings (==), 23 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 IDMR Working Group Dave Thaler 2 Internet Draft Microsoft 3 Andrew Adams 4 William Siadak 5 Djinesys, Inc. 6 draft-thaler-idmr-multiproto-pimmib-00.txt June 2000 7 Experimental 9 Protocol Independent Multicast MIB for IP 11 Status of this Memo 13 This document is an Internet-Draft and is in full conformance with 14 all provisions of Section 10 of RFC2026. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six 22 months and may be updated, replaced, or obsoleted by other documents 23 at any time. It is inappropriate to use Internet-Drafts as 24 reference material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt. 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 Copyright Notice 34 Copyright (C) The Internet Society (2000). All Rights Reserved. 36 1. Abstract 38 This memo defines a portion of the Management Information Base (MIB) 39 for use with network management protocols in the Internet community. 40 In particular, it describes managed objects used for managing the 41 Protocol Independent Multicast (PIM) protocol for IPv4 and IPv6. 43 2. Introduction 45 This memo defines a portion of the Management Information Base (MIB) 46 for use with network management protocols in the Internet community. 47 In particular, it describes managed objects used for managing the 49 1 50 Protocol Independent Multicast (PIM) protocol [1,2,3,4,5]. This MIB 51 module is applicable to IPv4 and IPv6 multicast routers which 52 implement PIM. This MIB extends the MIB proposed in [6]. This MIB 53 does not support management of PIM for other address families. Such 54 management may be supported by other MIBs. 56 3. The SNMP Network Management Framework 58 The SNMP Management Framework presently consists of five major 59 components: 61 o An overall architecture, described in RFC 2271 [7]. 63 o Mechanisms for describing and naming objects and events for the 64 purpose of management. The first version of this Structure of 65 Management Information (SMI) is called SMIv1 and described in RFC 66 1155 [8], RFC 1212 [9] and RFC 1215 [10]. The second version, called 67 SMIv2, is described in RFC 2578 [11], RFC 2579 [12] and RFC 2580 68 [13]. 70 o Message protocols for transferring management information. The 71 first version of the SNMP message protocol is called SNMPv1 and 72 described in RFC 1157 [14]. A second version of the SNMP message 73 protocol, which is not an Internet standards track protocol, is 74 called SNMPv2c and described in RFC 1901 [15] and RFC 1906 [16]. The 75 third version of the message protocol is called SNMPv3 and described 76 in RFC 1906 [16], RFC 2572 [17] and RFC 2574 [18]. 78 o Protocol operations for accessing management information. The 79 first set of protocol operations and associated PDU formats is 80 described in RFC 1157 [14]. A second set of protocol operations and 81 associated PDU formats is described in RFC 1905 [19]. 83 o A set of fundamental applications described in RFC 2573 [20] 84 and the view-based access control mechanism described in RFC 2575 85 [21]. 87 Managed objects are accessed via a virtual information store, termed 88 the Management Information Base or MIB. Objects in the MIB are 89 defined using the mechanisms defined in the SMI. 91 This memo specifies a MIB module that is compliant to the SMIv2. A 92 MIB conforming to the SMIv1 can be produced through the appropriate 93 translations. The resulting translated MIB must be semantically 94 equivalent, except where objects or events are omitted because no 95 translation is possible (use of Counter64). Some machine readable 96 information in SMIv2 will be converted into textual descriptions in 97 SMIv1 during the translation process. However, this loss of machine 98 readable information is not considered to change the semantics of 99 the MIB. 101 Thaler,Adams,Siadak Experimental/Expires Dec 2000 2 102 4. Overview 104 This MIB module contains one scalar and eight tables. Some of the 105 objects in these tables are deprecated. This MIB contains 106 deprecated objects since they are necessary for managing PIMv1 107 routers, but PIMv1 itself is obsoleted by PIMv2 [3,4]. 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 115 router's PIM neighbors. 117 (3) The PIM IP Multicast Route Table contains one row for each 118 multicast routing entry whose incoming interface is running 119 PIM. 121 (4) The PIM Next Hop Table contains one row for each outgoing 122 interface list entry in the multicast routing table whose interface 123 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 of a 127 group. 129 (6) The PIM RP-Set Table contains the PIM (version 2) information 130 for sets of candidate Rendezvous Points (RPs) for multicast group 131 addresses with particular address prefixes. 133 (7) The PIM Candidate-RP Table contains the multicast groups for 134 which the local router is to advertise itself as a Candidate-RP. If 135 this table is empty, then the local router advertises itself as a 136 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 5. Definitions 143 PIMG-MIB DEFINITIONS ::= BEGIN 145 IMPORTS 146 MODULE-IDENTITY, OBJECT-TYPE, experimental, 147 NOTIFICATION-TYPE, 148 Integer32, TimeTicks FROM SNMPv2-SMI 149 RowStatus, TruthValue FROM SNMPv2-TC 150 MODULE-COMPLIANCE, OBJECT-GROUP, 151 NOTIFICATION-GROUP FROM SNMPv2-CONF 152 inetMRouteGroupType, inetMRouteGroup, inetMRouteGroupMaskLen, 153 inetMRouteSourceType, inetMRouteSource, inetMRouteSourceMaskLen, 155 Thaler,Adams,Siadak Experimental/Expires Dec 2000 3 156 inetMRouteNextHopGroupType, inetMRouteNextHopGroup, 157 inetMRouteNextHopSourceType, inetMRouteNextHopSource, 158 inetMRouteNextHopSourceMaskLen, 159 inetMRouteNextHopIfIndex, inetMRouteNextHopAddressType, 160 inetMRouteNextHopAddress FROM INETMROUTE-STD-MIB 161 InterfaceIndex FROM IF-MIB 162 InetAddress, InetAddressType FROM INET-ADDRESS-MIB; 164 pimgMIB MODULE-IDENTITY 165 LAST-UPDATED "200003091200Z" -- March 9, 2000 166 ORGANIZATION "IETF IDMR Working Group." 167 CONTACT-INFO 168 " Dave Thaler 169 Microsoft Corporation 170 One Microsoft Way 171 Redmond, WA 98052-6399 172 US 174 Phone: +1 425 703 8835 175 EMail: dthaler@dthaler.microsoft.com 177 Andrew Adams 178 Merit Network, Inc. 179 4251 Plymouth Rd. 180 Ann Arbor, MI 48105-2785 182 Phone: +1 734 763-6378 183 EMail: ala@merit.edu 185 William Siadak 186 Merit Network, Inc. 187 4251 Plymouth Rd. 188 Ann Arbor, MI 48105-2785 190 Phone: +1 734 936 2035 191 EMail: wfs@merit.edu" 193 DESCRIPTION 194 "The MIB module for management of PIM routers." 195 REVISION "200003091200Z" -- March 9, 2000 196 DESCRIPTION 197 "Initial version, published as RFC xxxx (to be filled in 198 by RFC-Editor)." 199 ::= { experimental XX } 201 pimgMIBObjects OBJECT IDENTIFIER ::= { pimgMIB 1 } 203 pimgTraps OBJECT IDENTIFIER ::= { pimgMIBObjects 0 } 205 pimg OBJECT IDENTIFIER ::= { pimgMIBObjects 1 } 207 pimgJoinPruneInterval OBJECT-TYPE 209 Thaler,Adams,Siadak Experimental/Expires Dec 2000 4 210 SYNTAX Integer32 211 UNITS "seconds" 212 MAX-ACCESS read-write 213 STATUS current 214 DESCRIPTION 215 "The default interval at which periodic PIM-SM 216 Join/Prune 217 messages are to be sent." 218 ::= { pimg 1 } 220 -- The PIM Interface Table 222 pimgInterfaceTable OBJECT-TYPE 223 SYNTAX SEQUENCE OF PimgInterfaceEntry 224 MAX-ACCESS not-accessible 225 STATUS current 226 DESCRIPTION 227 "The (conceptual) table listing the router's PIM 228 interfaces. IGMP and PIM are enabled on all interfaces 229 listed in this table." 230 ::= { pimg 2 } 232 pimgInterfaceEntry OBJECT-TYPE 233 SYNTAX PimgInterfaceEntry 234 MAX-ACCESS not-accessible 235 STATUS current 236 DESCRIPTION 237 "An entry (conceptual row) in the pimgInterfaceTable." 238 INDEX { pimgInterfaceIfIndex } 239 ::= { pimgInterfaceTable 1 } 241 PimgInterfaceEntry ::= SEQUENCE { 242 pimgInterfaceIfIndex InterfaceIndex, 243 pimgInterfaceAddressType InetAddressType, 244 pimgInterfaceAddress InetAddress, 245 pimgInterfaceNetMaskLen INTEGER, 246 pimgInterfaceMode INTEGER, 247 pimgInterfaceDRType InetAddressType, 248 pimgInterfaceDR InetAddress, 249 pimgInterfaceHelloInterval Integer32, 250 pimgInterfaceStatus RowStatus, 251 pimgInterfaceJoinPruneInterval Integer32, 252 pimgInterfaceCBSRPreference Integer32 253 } 255 pimgInterfaceIfIndex OBJECT-TYPE 256 SYNTAX InterfaceIndex 257 MAX-ACCESS not-accessible 258 STATUS current 259 DESCRIPTION 260 "The ifIndex value of this PIM interface." 261 ::= { pimgInterfaceEntry 1 } 263 Thaler,Adams,Siadak Experimental/Expires Dec 2000 5 264 pimgInterfaceAddressType OBJECT-TYPE 265 SYNTAX InetAddressType 266 MAX-ACCESS read-only 267 STATUS current 268 DESCRIPTION 269 "A value indicating the address family of the address 270 contained in pimgInterfaceAddress. Legal values 271 correspond to the subset of address families for which 272 PIM routing is supported." 273 ::= { pimgInterfaceEntry 2 } 275 pimgInterfaceAddress OBJECT-TYPE 276 SYNTAX InetAddress 277 MAX-ACCESS read-only 278 STATUS current 279 DESCRIPTION 280 "The IP address of the PIM interface." 281 ::= { pimgInterfaceEntry 3 } 283 pimgInterfaceNetMaskLen OBJECT-TYPE 284 SYNTAX INTEGER (0..128) 285 MAX-ACCESS read-only 286 STATUS current 287 DESCRIPTION 288 "The length in bits of the network mask which when 289 combined with the corresponding value of 290 pimgInterfaceAddress identifies the address of the 291 network 292 to which the PIM interface is attached." 293 ::= { pimgInterfaceEntry 4 } 295 pimgInterfaceMode OBJECT-TYPE 296 SYNTAX INTEGER { dense(1), sparse(2), sparseDense(3) } 297 MAX-ACCESS read-create 298 STATUS current 299 DESCRIPTION 300 "The configured mode of this PIM interface. A value of 301 sparseDense is only valid for PIMv1." 302 DEFVAL { dense } 303 ::= { pimgInterfaceEntry 5 } 305 pimgInterfaceDRType OBJECT-TYPE 306 SYNTAX InetAddressType 307 MAX-ACCESS read-only 308 STATUS current 309 DESCRIPTION 310 "A value indicating the address family of the address 311 contained in pimgInterfaceDR. The value MUST be the same 312 as 313 the value of pimgInterfaceAddressType." 314 ::= { pimgInterfaceEntry 6 } 316 pimgInterfaceDR OBJECT-TYPE 318 Thaler,Adams,Siadak Experimental/Expires Dec 2000 6 319 SYNTAX InetAddress 320 MAX-ACCESS read-only 321 STATUS current 322 DESCRIPTION 323 "The Designated Router on this PIM interface. For 324 point-to-point interfaces, pimgInterfaceDR will be 325 0.0.0.0 326 in the case of an IPv4 entry, and 0:0:0:0:0:0:0:0 in the 327 case of an IPv6 entry." 328 ::= { pimgInterfaceEntry 7 } 330 pimgInterfaceHelloInterval OBJECT-TYPE 331 SYNTAX Integer32 332 UNITS "seconds" 333 MAX-ACCESS read-create 334 STATUS current 335 DESCRIPTION 336 "The frequency at which PIM Hello messages are 337 transmitted 338 on this interface." 339 DEFVAL { 30 } 340 ::= { pimgInterfaceEntry 8 } 342 pimgInterfaceStatus OBJECT-TYPE 343 SYNTAX RowStatus 344 MAX-ACCESS read-create 345 STATUS current 346 DESCRIPTION 347 "The status of this entry. Creating the entry enables 348 PIM 349 on the interface; destroying the entry disables PIM on 350 the 351 interface." 352 ::= { pimgInterfaceEntry 9 } 354 pimgInterfaceJoinPruneInterval OBJECT-TYPE 355 SYNTAX Integer32 356 UNITS "seconds" 357 MAX-ACCESS read-create 358 STATUS current 359 DESCRIPTION 360 "The frequency at which PIM Join/Prune messages are 361 transmitted on this PIM interface. The default value of 362 this object is the pimgJoinPruneInterval." 363 ::= { pimgInterfaceEntry 10 } 365 pimgInterfaceCBSRPreference OBJECT-TYPE 366 SYNTAX Integer32 (-1..255) 367 MAX-ACCESS read-create 368 STATUS current 369 DESCRIPTION 370 "The preference value for the local interface as a 371 candidate bootstrap router. The value of -1 is used to 373 Thaler,Adams,Siadak Experimental/Expires Dec 2000 7 374 indicate that the local interface is not a candidate BSR 375 interface." 376 DEFVAL { 0 } 377 ::= { pimgInterfaceEntry 11 } 379 -- The PIM Neighbor Table 381 pimgNeighborTable OBJECT-TYPE 382 SYNTAX SEQUENCE OF PimgNeighborEntry 383 MAX-ACCESS not-accessible 384 STATUS current 385 DESCRIPTION 386 "The (conceptual) table listing the router's PIM 387 neighbors." 388 ::= { pimg 3 } 390 pimgNeighborEntry OBJECT-TYPE 391 SYNTAX PimgNeighborEntry 392 MAX-ACCESS not-accessible 393 STATUS current 394 DESCRIPTION 395 "An entry (conceptual row) in the pimgNeighborTable." 396 INDEX { pimgNeighborAddressType, pimgNeighborAddress } 397 ::= { pimgNeighborTable 1 } 399 PimgNeighborEntry ::= SEQUENCE { 400 pimgNeighborAddressType InetAddressType, 401 pimgNeighborAddress InetAddress, 402 pimgNeighborIfIndex InterfaceIndex, 403 pimgNeighborUpTime TimeTicks, 404 pimgNeighborExpiryTime TimeTicks, 405 pimgNeighborMode INTEGER 406 } 408 pimgNeighborAddressType OBJECT-TYPE 409 SYNTAX InetAddressType 410 MAX-ACCESS not-accessible 411 STATUS current 412 DESCRIPTION 413 "A value indicating the address family of the address 414 contained in pimgNeighborAddress. Legal values 415 correspond 416 to the subset of 417 address families for which PIM routing is supported." 418 ::= { pimgNeighborEntry 1 } 420 pimgNeighborAddress OBJECT-TYPE 421 SYNTAX InetAddress 422 MAX-ACCESS not-accessible 423 STATUS current 424 DESCRIPTION 425 "The IP address of the PIM neighbor for which this entry 426 contains information." 428 Thaler,Adams,Siadak Experimental/Expires Dec 2000 8 429 ::= { pimgNeighborEntry 2 } 431 pimgNeighborIfIndex OBJECT-TYPE 432 SYNTAX InterfaceIndex 433 MAX-ACCESS read-only 434 STATUS current 435 DESCRIPTION 436 "The value of ifIndex for the interface used to reach 437 this 438 PIM neighbor." 439 ::= { pimgNeighborEntry 3 } 441 pimgNeighborUpTime OBJECT-TYPE 442 SYNTAX TimeTicks 443 MAX-ACCESS read-only 444 STATUS current 445 DESCRIPTION 446 "The time since this PIM neighbor (last) became a 447 neighbor 448 of the local router." 449 ::= { pimgNeighborEntry 4 } 451 pimgNeighborExpiryTime OBJECT-TYPE 452 SYNTAX TimeTicks 453 MAX-ACCESS read-only 454 STATUS current 455 DESCRIPTION 456 "The minimum time remaining before this PIM neighbor 457 will 458 be aged out." 459 ::= { pimgNeighborEntry 5 } 461 pimgNeighborMode OBJECT-TYPE 462 SYNTAX INTEGER { dense(1), sparse(2) } 463 MAX-ACCESS read-only 464 STATUS deprecated 465 DESCRIPTION 466 "The active PIM mode of this neighbor. This object is 467 deprecated for PIMv2 routers since all neighbors on the 468 interface must be either dense or sparse as determined 469 by 470 the protocol running on the interface." 471 ::= { pimgNeighborEntry 6 } 473 -- 474 -- The PIM IP Multicast Route Table 475 -- 477 pimgInetMRouteTable OBJECT-TYPE 478 SYNTAX SEQUENCE OF PimgInetMRouteEntry 479 MAX-ACCESS not-accessible 480 STATUS current 481 DESCRIPTION 483 Thaler,Adams,Siadak Experimental/Expires Dec 2000 9 484 "The (conceptual) table listing PIM-specific information 485 on a subset of the rows of the inetMRouteTable defined 486 in 487 the Inet Multicast MIB." 488 ::= { pimg 4 } 490 pimgInetMRouteEntry OBJECT-TYPE 491 SYNTAX PimgInetMRouteEntry 492 MAX-ACCESS not-accessible 493 STATUS current 494 DESCRIPTION 495 "An entry (conceptual row) in the pimgInetMRouteTable. 496 There is one entry per entry in the inetMRouteTable 497 whose 498 incoming interface is running PIM." 499 INDEX { inetMRouteGroupType, 500 inetMRouteGroup, 501 inetMRouteGroupMaskLen, 502 inetMRouteSourceType, 503 inetMRouteSource, 504 inetMRouteSourceMaskLen } 505 ::= { pimgInetMRouteTable 1 } 507 PimgInetMRouteEntry ::= SEQUENCE { 508 pimgInetMRouteUpstreamAssertTimer TimeTicks, 509 pimgInetMRouteAssertMetric Integer32, 510 pimgInetMRouteAssertMetricPref Integer32, 511 pimgInetMRouteAssertRPTBit TruthValue, 512 pimgInetMRouteFlags BITS 514 } 516 pimgInetMRouteUpstreamAssertTimer OBJECT-TYPE 517 SYNTAX TimeTicks 518 MAX-ACCESS read-only 519 STATUS current 520 DESCRIPTION 521 "The time remaining before the router changes its 522 upstream 523 neighbor back to its RPF neighbor. This timer is called 524 the Assert timer in the PIM Sparse and Dense mode 525 specification. A value of 0 indicates that no Assert has 526 changed the upstream neighbor away from the RPF 527 neighbor." 528 ::= { pimgInetMRouteEntry 1 } 530 pimgInetMRouteAssertMetric OBJECT-TYPE 531 SYNTAX Integer32 532 MAX-ACCESS read-only 533 STATUS current 534 DESCRIPTION 535 "The metric advertised by the assert winner on the 536 upstream interface, or 0 if no such assert is in 538 Thaler,Adams,Siadak Experimental/Expires Dec 2000 10 539 received." 540 ::= { pimgInetMRouteEntry 2 } 542 pimgInetMRouteAssertMetricPref OBJECT-TYPE 543 SYNTAX Integer32 544 MAX-ACCESS read-only 545 STATUS current 546 DESCRIPTION 547 "The preference advertised by the assert winner on the 548 upstream interface, or 0 if no such assert is in 549 effect." 550 ::= { pimgInetMRouteEntry 3 } 552 pimgInetMRouteAssertRPTBit OBJECT-TYPE 553 SYNTAX TruthValue 554 MAX-ACCESS read-only 555 STATUS current 556 DESCRIPTION 557 "The value of the RPT-bit advertised by the assert 558 winner 559 on the upstream interface, or false if no such assert is 560 in effect." 561 ::= { pimgInetMRouteEntry 4 } 563 pimgInetMRouteFlags OBJECT-TYPE 564 SYNTAX BITS { 565 rpt(0), 566 spt(1) 567 } 568 MAX-ACCESS read-only 569 STATUS current 570 DESCRIPTION 571 "This object describes PIM-specific flags related 572 to a multicast state entry. See the PIM Sparse 573 Mode specification for the meaning of the RPT and 574 SPT bits." 575 ::= { pimgInetMRouteEntry 5 } 577 -- 578 -- The PIM Next Hop Table 579 -- 581 pimgInetMRouteNextHopTable OBJECT-TYPE 582 SYNTAX SEQUENCE OF PimgInetMRouteNextHopEntry 583 MAX-ACCESS not-accessible 584 STATUS current 585 DESCRIPTION 586 "The (conceptual) table listing PIM-specific 587 information on a subset of the rows of the 588 inetMRouteNextHopTable defined in the IP Multicast 589 MIB." 590 ::= { pimg 7 } 592 Thaler,Adams,Siadak Experimental/Expires Dec 2000 11 593 pimgInetMRouteNextHopEntry OBJECT-TYPE 594 SYNTAX PimgInetMRouteNextHopEntry 595 MAX-ACCESS not-accessible 596 STATUS current 597 DESCRIPTION 598 "An entry (conceptual row) in the 599 pimgInetMRouteNextHopTable. There is one entry per 600 entry in the inetMRouteNextHopTable whose interface 601 is running PIM and whose inetMRouteNextHopState is 602 pruned(1)." 603 INDEX { inetMRouteNextHopGroupType, 604 inetMRouteNextHopGroup, 605 inetMRouteNextHopSourceType, 606 inetMRouteNextHopSource, 607 inetMRouteNextHopSourceMaskLen, 608 inetMRouteNextHopIfIndex, 609 inetMRouteNextHopAddressType, 610 inetMRouteNextHopAddress } 611 ::= { pimgInetMRouteNextHopTable 1 } 613 PimgInetMRouteNextHopEntry ::= SEQUENCE { 614 pimgInetMRouteNextHopPruneReason INTEGER 615 } 617 pimgInetMRouteNextHopPruneReason OBJECT-TYPE 618 SYNTAX INTEGER { 619 other (1), 620 prune (2), 621 assert (3) 622 } 623 MAX-ACCESS read-only 624 STATUS current 625 DESCRIPTION 626 "This object indicates why the downstream interface 627 was pruned, whether in response to a PIM prune 628 message or due to PIM Assert processing." 629 ::= { pimgInetMRouteNextHopEntry 2 } 631 -- The PIM RP Table 633 pimgRPTable OBJECT-TYPE 634 SYNTAX SEQUENCE OF PimgRPEntry 635 MAX-ACCESS not-accessible 636 STATUS deprecated 637 DESCRIPTION 638 "The (conceptual) table listing PIM version 1 639 information for the Rendezvous Points (RPs) for 640 multicast groups. This table is deprecated since 641 its function is replaced by the pimgRPSetTable for 642 PIM version 2." 643 ::= { pimg 5 } 645 pimgRPEntry OBJECT-TYPE 647 Thaler,Adams,Siadak Experimental/Expires Dec 2000 12 648 SYNTAX PimgRPEntry 649 MAX-ACCESS not-accessible 650 STATUS deprecated 651 DESCRIPTION 652 "An entry (conceptual row) in the pimgRPTable. 653 There is one entry per RP address for each 654 multicast group." 655 INDEX { pimgRPGroupAddressType, pimgRPGroupAddress, 656 pimgRPAddressType, pimgRPAddress } 657 ::= { pimgRPTable 1 } 659 PimgRPEntry ::= SEQUENCE { 660 pimgRPGroupAddressType InetAddressType, 661 pimgRPGroupAddress InetAddress, 662 pimgRPAddressType InetAddressType, 663 pimgRPAddress InetAddress, 664 pimgRPState INTEGER, 665 pimgRPStateTimer TimeTicks, 666 pimgRPLastChange TimeTicks, 667 pimgRPRowStatus RowStatus 668 } 670 pimgRPGroupAddressType OBJECT-TYPE 671 SYNTAX InetAddressType 672 MAX-ACCESS not-accessible 673 STATUS deprecated 674 DESCRIPTION 675 "A value indicating the address family of the 676 address contained in pimgRPGroupAddress. Legal 677 values are: 678 unknown(0), ipv4(1), ipv6(2), dns(16)" 679 ::= { pimgRPEntry 1 } 681 pimgRPGroupAddress OBJECT-TYPE 682 SYNTAX InetAddress 683 MAX-ACCESS not-accessible 684 STATUS deprecated 685 DESCRIPTION 686 "The multicast group address for which this entry 687 contains information about an RP." 688 ::= { pimgRPEntry 2 } 690 pimgRPAddressType OBJECT-TYPE 691 SYNTAX InetAddressType 692 MAX-ACCESS not-accessible 693 STATUS deprecated 694 DESCRIPTION 695 "A value indicating the address family of the 696 address contained in pimgRPAddress. The value MUST 697 be the same as the value of 698 pimgRPGroupAddressType." 699 ::= { pimgRPEntry 3 } 701 Thaler,Adams,Siadak Experimental/Expires Dec 2000 13 702 pimgRPAddress OBJECT-TYPE 703 SYNTAX InetAddress 704 MAX-ACCESS not-accessible 705 STATUS deprecated 706 DESCRIPTION 707 "The unicast address of the RP." 708 ::= { pimgRPEntry 4 } 710 pimgRPState OBJECT-TYPE 711 SYNTAX INTEGER { up(1), down(2) } 712 MAX-ACCESS read-only 713 STATUS deprecated 714 DESCRIPTION 715 "The state of the RP." 716 ::= { pimgRPEntry 5 } 718 pimgRPStateTimer OBJECT-TYPE 719 SYNTAX TimeTicks 720 MAX-ACCESS read-only 721 STATUS deprecated 722 DESCRIPTION 723 "The minimum time remaining before the next state 724 change. When pimgRPState is up, this is the minimum 725 time which must expire until it can be declared 726 down. When pimgRPState is down, this is the time 727 until it will be declared up (in order to retry)." 728 ::= { pimgRPEntry 6 } 730 pimgRPLastChange OBJECT-TYPE 731 SYNTAX TimeTicks 732 MAX-ACCESS read-only 733 STATUS deprecated 734 DESCRIPTION 735 "The value of sysUpTime at the time when the 736 corresponding instance of pimgRPState last changed 737 its value." 738 ::= { pimgRPEntry 7 } 740 pimgRPRowStatus OBJECT-TYPE 741 SYNTAX RowStatus 742 MAX-ACCESS read-create 743 STATUS deprecated 744 DESCRIPTION 745 "The status of this row, by which new entries may 746 be created, or old entries deleted from this 747 table." 748 ::= { pimgRPEntry 8 } 750 -- The PIM RP-Set Table 752 pimgRPSetTable OBJECT-TYPE 753 SYNTAX SEQUENCE OF PimgRPSetEntry 754 MAX-ACCESS not-accessible 756 Thaler,Adams,Siadak Experimental/Expires Dec 2000 14 757 STATUS current 758 DESCRIPTION 759 "The (conceptual) table listing PIM information for 760 candidate Rendezvous Points (RPs) for multicast 761 groups. When the local router is the BSR, this 762 information is obtained from received Candidate-RP- 763 Advertisements. When the local router is not the 764 BSR, this information is obtained from received RP- 765 Set messages." 766 ::= { pimg 6 } 768 pimgRPSetEntry OBJECT-TYPE 769 SYNTAX PimgRPSetEntry 770 MAX-ACCESS not-accessible 771 STATUS current 772 DESCRIPTION 773 "An entry (conceptual row) in the pimgRPSetTable." 774 INDEX { pimgRPSetComponent, 775 pimgRPSetGroupAddressType, 776 pimgRPSetGroupAddress, 777 pimgRPSetGroupMaskLen, pimgRPSetAddressType, 778 pimgRPSetAddress } 779 ::= { pimgRPSetTable 1 } 781 PimgRPSetEntry ::= SEQUENCE { 782 pimgRPSetGroupAddressType InetAddressType, 783 pimgRPSetGroupAddress InetAddress, 784 pimgRPSetGroupMaskLen INTEGER, 785 pimgRPSetAddressType InetAddressType, 786 pimgRPSetAddress InetAddress, 787 pimgRPSetHoldTime Integer32, 788 pimgRPSetExpiryTime TimeTicks, 789 pimgRPSetComponent Integer32 790 } 792 pimgRPSetGroupAddressType OBJECT-TYPE 793 SYNTAX InetAddressType 794 MAX-ACCESS not-accessible 795 STATUS current 796 DESCRIPTION 797 "A value indicating the address family of the address 798 contained in pimgRPSetGroupAddress. Legal values 799 correspond to the subset of address families for which 800 PIM 801 routing is supported." 802 ::= { pimgRPSetEntry 1 } 804 pimgRPSetGroupAddress OBJECT-TYPE 805 SYNTAX InetAddress 806 MAX-ACCESS not-accessible 807 STATUS current 808 DESCRIPTION 809 "The IP multicast group address which, when 811 Thaler,Adams,Siadak Experimental/Expires Dec 2000 15 812 combined with 813 the value of pimgRPSetGroupMaskLen, gives the group 814 prefix for which this entry contains information 815 about the Candidate-RP." 816 ::= { pimgRPSetEntry 2 } 818 pimgRPSetGroupMaskLen OBJECT-TYPE 819 SYNTAX INTEGER (0..128) 820 MAX-ACCESS not-accessible 821 STATUS current 822 DESCRIPTION 823 "The length in bits of the mask which, when 824 combined with pimgRPSetGroupAddress, gives the 825 group prefix for which this entry contains 826 information about the Candidate-RP." 827 ::= { pimgRPSetEntry 3 } 829 pimgRPSetAddressType OBJECT-TYPE 830 SYNTAX InetAddressType 831 MAX-ACCESS not-accessible 832 STATUS current 833 DESCRIPTION 834 "A value indicating the address family of the 835 address contained in pimgRPSetAddress. The value 836 MUST be the same as the value of 837 pimgRPSetGroupAddressType." 838 ::= { pimgRPSetEntry 4 } 840 pimgRPSetAddress OBJECT-TYPE 841 SYNTAX InetAddress 842 MAX-ACCESS not-accessible 843 STATUS current 844 DESCRIPTION 845 "The address of the Candidate-RP." 846 ::= { pimgRPSetEntry 5 } 848 pimgRPSetHoldTime OBJECT-TYPE 849 SYNTAX Integer32 (0..255) 850 UNITS "seconds" 851 MAX-ACCESS read-only 852 STATUS current 853 DESCRIPTION 854 "The holdtime of a Candidate-RP. If the local 855 router is not the BSR, this value is 0." 856 ::= { pimgRPSetEntry 6 } 858 pimgRPSetExpiryTime OBJECT-TYPE 859 SYNTAX TimeTicks 860 MAX-ACCESS read-only 861 STATUS current 862 DESCRIPTION 863 "The minimum time remaining before the Candidate-RP 864 will be declared down. If the local router is not 866 Thaler,Adams,Siadak Experimental/Expires Dec 2000 16 867 the BSR, this value is 0." 868 ::= { pimgRPSetEntry 7 } 870 pimgRPSetComponent OBJECT-TYPE 871 SYNTAX Integer32 (1..255) 872 MAX-ACCESS not-accessible 873 STATUS current 874 DESCRIPTION 875 "A number uniquely identifying the component. Each 876 protocol instance connected to a separate domain 877 should have a different index value." 878 ::= { pimgRPSetEntry 8 } 880 -- The PIM Candidate-RP Table 882 pimgCandidateRPTable OBJECT-TYPE 883 SYNTAX SEQUENCE OF PimgCandidateRPEntry 884 MAX-ACCESS not-accessible 885 STATUS current 886 DESCRIPTION 887 "The (conceptual) table listing the multicast 888 groups for which the local router is to advertise 889 itself as a Candidate-RP when the value of 890 pimgComponentCRPHoldTime is non-zero. If this 891 table is empty, then the local router 892 will advertise itself as a Candidate-RP for all 893 groups (providing the value of 894 pimgComponentCRPHoldTime is non-zero)." 895 ::= { pimg 11 } 897 pimgCandidateRPEntry OBJECT-TYPE 898 SYNTAX PimgCandidateRPEntry 899 MAX-ACCESS not-accessible 900 STATUS current 901 DESCRIPTION 902 "An entry (conceptual row) in the 903 pimgCandidateRPTable." 904 INDEX { pimgCandidateRPGroupAddressType, 905 pimgCandidateRPGroupAddress, 906 pimgCandidateRPGroupMaskLen } 907 ::= { pimgCandidateRPTable 1 } 909 PimgCandidateRPEntry ::= SEQUENCE { 910 pimgCandidateRPGroupAddressType InetAddressType, 911 pimgCandidateRPGroupAddress InetAddress, 912 pimgCandidateRPGroupMaskLen INTEGER, 913 pimgCandidateRPAddressType InetAddressType, 914 pimgCandidateRPAddress InetAddress, 915 pimgCandidateRPRowStatus RowStatus 916 } 918 pimgCandidateRPGroupAddressType OBJECT-TYPE 919 SYNTAX InetAddressType 921 Thaler,Adams,Siadak Experimental/Expires Dec 2000 17 922 MAX-ACCESS not-accessible 923 STATUS current 924 DESCRIPTION 925 "A value indicating the address family of the 926 address contained in pimgCandidateRPGroupAddress. 927 Legal values correspond to the subset of address 928 families for which PIM routing is supported." 929 ::= { pimgCandidateRPEntry 1 } 931 pimgCandidateRPGroupAddress OBJECT-TYPE 932 SYNTAX InetAddress 933 MAX-ACCESS not-accessible 934 STATUS current 935 DESCRIPTION 936 "The multicast group address which, when combined 937 with the corresponding value of 938 pimgCandidateRPGroupMaskLen, identifies a group 939 prefix for which the local router will advertise 940 itself as a Candidate-RP." 941 ::= { pimgCandidateRPEntry 2 } 943 pimgCandidateRPGroupMaskLen OBJECT-TYPE 944 SYNTAX INTEGER (0..128) 945 MAX-ACCESS not-accessible 946 STATUS current 947 DESCRIPTION 948 "The length in bits of the mask which, when 949 combined with pimgCandidateRPGroupAddress, 950 identifies a group prefix for which the local 951 router will advertise itself as a Candidate-RP." 952 ::= { pimgCandidateRPEntry 3 } 954 pimgCandidateRPAddressType OBJECT-TYPE 955 SYNTAX InetAddressType 956 MAX-ACCESS read-create 957 STATUS current 958 DESCRIPTION 959 "A value indicating the address family of the 960 address contained in pimgCandidateRPAddress. The 961 value MUST be the same as the value of 962 pimgCandidateRPGroupAddressType." 963 ::= { pimgCandidateRPEntry 4 } 965 pimgCandidateRPAddress OBJECT-TYPE 966 SYNTAX InetAddress 967 MAX-ACCESS read-create 968 STATUS current 969 DESCRIPTION 970 "The (unicast) address of the interface which will 971 be advertised as a Candidate-RP." 972 ::= { pimgCandidateRPEntry 5 } 974 pimgCandidateRPRowStatus OBJECT-TYPE 976 Thaler,Adams,Siadak Experimental/Expires Dec 2000 18 977 SYNTAX RowStatus 978 MAX-ACCESS read-create 979 STATUS current 980 DESCRIPTION 981 "The status of this row, by which new entries may 982 be created, or old entries deleted from this 983 table." 984 ::= { pimgCandidateRPEntry 6 } 986 -- The PIM Component Table 988 pimgComponentTable OBJECT-TYPE 989 SYNTAX SEQUENCE OF PimgComponentEntry 990 MAX-ACCESS not-accessible 991 STATUS current 992 DESCRIPTION 993 "The (conceptual) table containing objects specific 994 to a PIM domain. One row exists for each domain to 995 which the router is connected. A PIM-SM domain is 996 defined as an area of the network over which 997 Bootstrap messages are forwarded. Typically, a PIM- 998 SM router will be a member of exactly one domain. 999 This table also supports, however, routers which 1000 may form a border between two PIM-SM domains and do 1001 not forward Bootstrap messages between them." 1002 ::= { pimg 12 } 1004 pimgComponentEntry OBJECT-TYPE 1005 SYNTAX PimgComponentEntry 1006 MAX-ACCESS not-accessible 1007 STATUS current 1008 DESCRIPTION 1009 "An entry (conceptual row) in the 1010 pimgComponentTable." 1011 INDEX { pimgComponentIndex } 1012 ::= { pimgComponentTable 1 } 1014 PimgComponentEntry ::= SEQUENCE { 1015 pimgComponentIndex Integer32, 1016 pimgComponentBSRAddressType InetAddressType, 1017 pimgComponentBSRAddress InetAddress, 1018 pimgComponentBSRExpiryTime TimeTicks, 1019 pimgComponentCRPHoldTime Integer32, 1020 pimgComponentStatus RowStatus 1021 } 1023 pimgComponentIndex OBJECT-TYPE 1024 SYNTAX Integer32 (1..255) 1025 MAX-ACCESS not-accessible 1026 STATUS current 1027 DESCRIPTION 1028 "A number uniquely identifying the component. Each 1029 protocol instance connected to a separate domain 1031 Thaler,Adams,Siadak Experimental/Expires Dec 2000 19 1032 should have a different index value. Routers that 1033 only support membership in a single PIM-SM domain 1034 should use a pimgComponentIndex value of 1." 1035 ::= { pimgComponentEntry 1 } 1037 pimgComponentBSRAddressType OBJECT-TYPE 1038 SYNTAX InetAddressType 1039 MAX-ACCESS read-only 1040 STATUS current 1041 DESCRIPTION 1042 "A value indicating the address family of the 1043 address contained in pimgComponentBSRAddress. Legal 1044 values correspond to the subset of address families 1045 for which PIM routing is supported." 1046 ::= { pimgComponentEntry 2 } 1048 pimgComponentBSRAddress OBJECT-TYPE 1049 SYNTAX InetAddress 1050 MAX-ACCESS read-only 1051 STATUS current 1052 DESCRIPTION 1053 "The address of the bootstrap router (BSR) for the 1054 local PIM region." 1055 ::= { pimgComponentEntry 3 } 1057 pimgComponentBSRExpiryTime OBJECT-TYPE 1058 SYNTAX TimeTicks 1059 MAX-ACCESS read-only 1060 STATUS current 1061 DESCRIPTION 1062 "The minimum time remaining before the bootstrap 1063 router in the local domain will be declared down. 1064 For candidate BSRs, this is the time until the 1065 component sends an RP-Set message. For other 1066 routers, this is the time until it may accept an 1067 RP-Set message from a lower candidate BSR." 1068 ::= { pimgComponentEntry 4 } 1070 pimgComponentCRPHoldTime OBJECT-TYPE 1071 SYNTAX Integer32 (0..255) 1072 UNITS "seconds" 1073 MAX-ACCESS read-create 1074 STATUS current 1075 DESCRIPTION 1076 "The holdtime of the component when it is a 1077 candidate RP in the local domain. The value of 0 1078 is used to indicate that the local system is not a 1079 Candidate-RP." 1080 DEFVAL { 0 } 1081 ::= { pimgComponentEntry 5 } 1083 pimgComponentStatus OBJECT-TYPE 1084 SYNTAX RowStatus 1086 Thaler,Adams,Siadak Experimental/Expires Dec 2000 20 1087 MAX-ACCESS read-create 1088 STATUS current 1089 DESCRIPTION 1090 "The status of this entry. Creating the entry 1091 creates another protocol instance; destroying the 1092 entry disables a protocol instance." 1093 ::= { pimgComponentEntry 6 } 1095 -- PIM Traps 1097 pimgNeighborLoss NOTIFICATION-TYPE 1098 OBJECTS { 1099 pimgNeighborIfIndex 1100 } 1101 STATUS current 1102 DESCRIPTION 1103 "A pimgNeighborLoss trap signifies the loss of an 1104 adjacency with a neighbor. This trap should be 1105 generated when the neighbor timer expires, and the 1106 router has no other neighbors on the same interface 1107 with a lower IP address than itself." 1108 ::= { pimgTraps 1 } 1110 -- conformance information 1112 pimgMIBConformance OBJECT IDENTIFIER ::= { pimgMIB 2 } 1113 pimgMIBCompliances OBJECT IDENTIFIER ::= { pimgMIBConformance 1 } 1114 pimgMIBGroups OBJECT IDENTIFIER ::= { pimgMIBConformance 2 } 1116 -- compliance statements 1118 pimgV1MIBCompliance MODULE-COMPLIANCE 1119 STATUS deprecated 1120 DESCRIPTION 1121 "The compliance statement for routers running PIMv1 1122 and implementing the PIM MIB." 1123 MODULE -- this module 1124 MANDATORY-GROUPS { pimgV1MIBGroup } 1126 ::= { pimgMIBCompliances 1 } 1128 pimgSparseV2MIBCompliance MODULE-COMPLIANCE 1129 STATUS current 1130 DESCRIPTION 1131 "The compliance statement for routers running PIM 1132 Sparse Mode and implementing the PIM MIB." 1133 MODULE -- this module 1134 MANDATORY-GROUPS { pimgV2MIBGroup } 1136 GROUP pimgV2CandidateRPMIBGroup 1137 DESCRIPTION 1138 "This group is mandatory if the router is capable 1139 of being a Candidate RP." 1141 Thaler,Adams,Siadak Experimental/Expires Dec 2000 21 1142 OBJECT pimgInterfaceStatus 1143 MIN-ACCESS read-only 1144 DESCRIPTION 1145 "Write access is not required." 1147 ::= { pimgMIBCompliances 2 } 1149 pimgDenseV2MIBCompliance MODULE-COMPLIANCE 1150 STATUS current 1151 DESCRIPTION 1152 "The compliance statement for routers running PIM 1153 Dense Mode and implementing the PIM MIB." 1154 MODULE -- this module 1155 MANDATORY-GROUPS { pimgDenseV2MIBGroup } 1157 OBJECT pimgInterfaceStatus 1158 MIN-ACCESS read-only 1159 DESCRIPTION 1160 "Write access is not required." 1162 ::= { pimgMIBCompliances 3 } 1164 -- units of conformance 1166 pimgNotificationGroup NOTIFICATION-GROUP 1167 NOTIFICATIONS { pimgNeighborLoss } 1168 STATUS current 1169 DESCRIPTION 1170 "A collection of notifications for signaling 1171 important PIM events." 1172 ::= { pimgMIBGroups 1 } 1174 pimgV2MIBGroup OBJECT-GROUP 1175 OBJECTS { pimgJoinPruneInterval, pimgNeighborIfIndex, 1176 pimgNeighborUpTime, pimgNeighborExpiryTime, 1177 pimgInterfaceAddressType, pimgInterfaceAddress, 1178 pimgInterfaceNetMaskLen, 1179 pimgInterfaceDRType, pimgInterfaceDR, 1180 pimgInterfaceHelloInterval, 1181 pimgInterfaceStatus, 1182 pimgInterfaceJoinPruneInterval, 1183 pimgInterfaceCBSRPreference, pimgInterfaceMode, 1184 pimgRPSetHoldTime, pimgRPSetExpiryTime, 1185 pimgComponentBSRAddressType, 1186 pimgComponentBSRAddress, 1187 pimgComponentBSRExpiryTime, 1188 pimgComponentCRPHoldTime, pimgComponentStatus, 1189 pimgInetMRouteFlags, 1190 pimgInetMRouteUpstreamAssertTimer 1191 } 1192 STATUS current 1193 DESCRIPTION 1195 Thaler,Adams,Siadak Experimental/Expires Dec 2000 22 1196 "A collection of objects to support management of PIM 1197 Sparse 1198 Mode (version 2) routers." 1199 ::= { pimgMIBGroups 2 } 1201 pimgDenseV2MIBGroup OBJECT-GROUP 1202 OBJECTS { pimgNeighborIfIndex, 1203 pimgNeighborUpTime, pimgNeighborExpiryTime, 1204 pimgInterfaceAddressType, pimgInterfaceAddress, 1205 pimgInterfaceNetMaskLen, 1206 pimgInterfaceDRType, pimgInterfaceDR, 1207 pimgInterfaceHelloInterval, 1208 pimgInterfaceStatus, pimgInterfaceMode 1209 } 1210 STATUS current 1211 DESCRIPTION 1212 "A collection of objects to support management of 1213 PIM Dense Mode (version 2) routers." 1214 ::= { pimgMIBGroups 7 } 1216 pimgV2CandidateRPMIBGroup OBJECT-GROUP 1217 OBJECTS { pimgCandidateRPAddressType, 1218 pimgCandidateRPAddress, 1219 pimgCandidateRPRowStatus 1220 } 1221 STATUS current 1222 DESCRIPTION 1223 "A collection of objects to support configuration 1224 of which groups a router is to advertise itself as 1225 a Candidate-RP." 1226 ::= { pimgMIBGroups 3 } 1228 pimgV1MIBGroup OBJECT-GROUP 1229 OBJECTS { pimgJoinPruneInterval, pimgNeighborIfIndex, 1230 pimgNeighborUpTime, pimgNeighborExpiryTime, 1231 pimgNeighborMode, 1232 pimgInterfaceAddressType, pimgInterfaceAddress, 1233 pimgInterfaceNetMaskLen, 1234 pimgInterfaceJoinPruneInterval, 1235 pimgInterfaceStatus, 1236 pimgInterfaceMode, 1237 pimgInterfaceDRType, pimgInterfaceDR, 1238 pimgInterfaceHelloInterval, 1239 pimgRPState, pimgRPStateTimer, 1240 pimgRPLastChange, pimgRPRowStatus 1241 } 1242 STATUS deprecated 1243 DESCRIPTION 1244 "A collection of objects to support management of 1245 PIM (version 1) routers." 1246 ::= { pimgMIBGroups 4 } 1248 pimgNextHopGroup OBJECT-GROUP 1250 Thaler,Adams,Siadak Experimental/Expires Dec 2000 23 1251 OBJECTS { pimgInetMRouteNextHopPruneReason } 1252 STATUS current 1253 DESCRIPTION 1254 "A collection of optional objects to provide per- 1255 next hop information for diagnostic purposes. 1256 Supporting this group may add a large number of 1257 instances to a tree walk, but the information in 1258 this group can be extremely useful in tracking down 1259 multicast connectivity problems." 1260 ::= { pimgMIBGroups 5 } 1262 pimgAssertGroup OBJECT-GROUP 1263 OBJECTS { pimgInetMRouteAssertMetric, 1264 pimgInetMRouteAssertMetricPref, 1265 pimgInetMRouteAssertRPTBit } 1266 STATUS current 1267 DESCRIPTION 1268 "A collection of optional objects to provide extra 1269 information about the assert election process. 1270 There is no protocol reason to keep such 1271 information, but some implementations may already 1272 keep this information and make it available. These 1273 objects can also be very useful in debugging 1274 connectivity or duplicate packet problems, 1275 especially if the assert winner does not support 1276 the PIM and Inet Multicast MIBs." 1277 ::= { pimgMIBGroups 6 } 1279 END 1281 6. Security Considerations 1283 This MIB contains readable objects whose values provide information 1284 related to multicast routing, including information on the network 1285 topology. There are also a number of objects that have a MAX-ACCESS 1286 clause of read-write and/or read-create, which allow an 1287 administrator to configure PIM in the router. 1289 While unauthorized access to the readable objects is relatively 1290 innocuous, unauthorized access to the write-able objects could cause 1291 a denial of service. Hence, the support for SET operations in a 1292 non-secure environment without proper protection can have a negative 1293 effect on network operations. 1295 SNMPv1 by itself is such an insecure environment. Even if the 1296 network itself is secure (for example by using IPSec), even then, 1297 there is no control as to who on the secure network is allowed to 1298 access and SET (change/create/delete) the objects in this MIB. 1300 It is recommended that the implementers consider the security 1301 features as provided by the SNMPv3 framework. Specifically, the use 1302 of the User-based Security Model RFC 2274 [12] and the View-based 1303 Access Control Model RFC 2275 [15] is recommended. 1305 Thaler,Adams,Siadak Experimental/Expires Dec 2000 24 1306 It is then a customer/user responsibility to ensure that the SNMP 1307 entity giving access to this MIB, is properly configured to give 1308 access to those objects only to those principals (users) that have 1309 legitimate rights to access them. 1311 7. Intellectual Property Notice 1313 The IETF takes no position regarding the validity or scope of any 1314 intellectual property or other rights that might be claimed to 1315 pertain to the implementation or use of the technology described in 1316 this document or the extent to which any license under such rights 1317 might or might not be available; neither does it represent that it 1318 has made any effort to identify any such rights. Information on the 1319 IETF's procedures with respect to rights in standards-track and 1320 standards-related documentation can be found in BCP-11. Copies of 1321 claims of rights made available for publication and any assurances 1322 of licenses to be made available, or the result of an attempt made 1323 to obtain a general license or permission for the use of such 1324 proprietary rights by implementers or users of this specification 1325 can be obtained from the IETF Secretariat. 1327 The IETF invites any interested party to bring to its attention any 1328 copyrights, patents or patent applications, or other proprietary 1329 rights which may cover technology that may be required to practice 1330 this standard. Please address the information to the IETF Executive 1331 Director. 1333 8. Acknowledgements 1335 This MIB module has been updated based on feedback from the IETF's 1336 Inter-Domain Multicast Routing (IDMR) Working Group. 1338 9. Authors' Addresses 1340 Dave Thaler 1341 Microsoft Corporation 1342 One Microsoft Way 1343 Redmond, WA 98052-6399 1344 Phone: +1 425 703 8835 1345 EMail: dthaler@dthaler.microsoft.com 1347 Andrew Adams 1348 Merit Network, Inc. 1349 4251 Plymouth Rd. 1350 Ann Arbor, MI 48105-2785 1351 Phone: +1 734 763-6378 1353 Thaler,Adams,Siadak Experimental/Expires Dec 2000 25 1354 EMail: ala@merit.edu 1356 William Siadak 1357 Merit Network, Inc. 1358 4251 Plymouth Rd. 1359 Ann Arbor, MI 48105-2785 1360 Phone: +1 734 936 2035 1361 EMail: wfs@merit.edu 1363 10. References 1365 1 Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Liu, G., and 1366 L. Wei, "Protocol Independent Multicast (PIM): Motivation and 1367 Architecture", January 1995. 1368 2 Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Liu, G., and 1369 L. Wei, "Protocol Independent Multicast (PIM): Protocol 1370 Specification", January 1995. 1371 3 Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering, S., 1372 Handley, M., Jacobson, V., Liu, C., Sharma, P., and L. Wei, 1373 "Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol 1374 Specification", RFC 2362, June 1998. 1375 4 Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Helmy, A., 1376 and L. Wei, "Protocol Independent Multicast Version 2, Dense Mode 1377 Specification". Work in Progress, May 1997. 1378 5 Haberman, B., Sandick, H., Kump, G., _Protocol Independent 1379 Multicast Routing in the Internet Protocol Version 6_, Internet 1380 Draft, November 1999. 1381 6 McCloghrie, K., Farinacci, D., Thaler D., Fenner, B., _Protocol 1382 Independent Multicast MIB for IPv4_, Internet Draft, January 31, 1383 2000 1384 7 Wijnen, B., Harrington, D., and R. Presuhn, "An Architecture for 1385 Describing SNMP Management Frameworks", RFC 2571, Cabletron 1386 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 1387 April 1999. 1388 8 Rose, M., and K. McCloghrie, "Structure and Identification of 1389 Management Information for TCP/IP-based Internets", RFC 1155, STD 1390 16, Performance Systems International, Hughes LAN Systems, May 1391 1990. 1392 9 Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 1393 STD 16, Performance Systems International, Hughes LAN Systems, 1394 March 1991. 1395 10 M. Rose, "A Convention for Defining Traps for use with the SNMP", 1396 RFC 1215, Performance Systems International, March 1991. 1397 11 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1398 M., and S. Waldbusser, "Structure of Management Information 1399 Version 2 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 1400 Braunschweig, SNMP Research, First Virtual Holdings, 1401 International Network Services, April 1999. 1402 12 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1403 M., and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, 1405 Thaler,Adams,Siadak Experimental/Expires Dec 2000 26 1406 STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, 1407 First Virtual Holdings, International Network Services, April 1408 1999. 1409 13 McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1410 M., and S. Waldbusser, "Conformance Statements for SMIv2", RFC 1411 2580, STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP 1412 Research, First Virtual Holdings, International Network Services, 1413 April 1999. 1414 14 Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1415 Network Management Protocol", RFC 1157, STD 15, SNMP Research, 1416 Performance Systems International, Performance Systems 1417 International, MIT Laboratory for Computer Science, May 1990. 1418 15 Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1419 "Introduction to Community-based SNMPv2", RFC 1901, SNMP 1420 Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, 1421 Inc., International Network Services, January 1996. 1422 16 Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 1423 Mappings for Version 2 of the Simple Network Management Protocol 1424 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 1425 Dover Beach Consulting, Inc., International Network Services, 1426 January 1996. 1427 17 Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1428 Processing and Dispatching for the Simple Network Management 1429 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron 1430 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 1431 April 1999. 1432 18 Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) 1433 for version 3 of the Simple Network Management Protocol 1434 (SNMPv3)", RFC 2574, IBM T. J. Watson Research, April 1999. 1435 19 Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1436 Operations for Version 2 of the Simple Network Management 1437 Protocol (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, 1438 Inc., Dover Beach Consulting, Inc., International Network 1439 Services, January 1996. 1440 20 Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1441 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 1442 Systems, April 1999. 1443 21 Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1444 Control Model (VACM) for the Simple Network Management Protocol 1445 (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., 1446 Cisco Systems, Inc., April 1999. 1448 11. Full Copyright Statement 1450 Copyright (C) The Internet Society (2000). All Rights Reserved. 1452 This document and translations of it may be copied and furnished to 1453 others, and derivative works that comment on or otherwise explain it 1454 or assist in its implementation may be prepared, copied, published 1455 and distributed, in whole or in part, without restriction of any 1457 Thaler,Adams,Siadak Experimental/Expires Dec 2000 27 1458 kind, provided that the above copyright notice and this paragraph 1459 are included on all such copies and derivative works. However, this 1460 document itself may not be modified in any way, such as by removing 1461 the copyright notice or references to the Internet Society or other 1462 Internet organizations, except as needed for the purpose of 1463 developing Internet standards in which case the procedures for 1464 copyrights defined in the Internet Standards process must be 1465 followed, or as required to translate it into languages other than 1466 English. 1468 The limited permissions granted above are perpetual and will not be 1469 revoked by the Internet Society or its successors or assigns. 1471 This document and the information contained herein is provided on an 1472 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1473 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1474 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1475 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1476 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1478 Table of Contents 1479 1. Abstract.......................................................1 1480 2. Introduction...................................................1 1481 3. The SNMP Network Management Framework..........................2 1482 4. Overview.......................................................3 1483 5. Definitions....................................................3 1484 6. Security Considerations.......................................24 1485 7. Intellectual Property Notice..................................25 1486 8. Acknowledgements..............................................25 1487 9. Authors' Addresses............................................25 1488 10. References...................................................26 1489 11. Full Copyright Statement.....................................27 1491 Thaler,Adams,Siadak Experimental/Expires Dec 2000 28