idnits 2.17.1 draft-ietf-idmr-pim-mib-05.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: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** 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. 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 (28 July 1998) is 9402 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) ** Obsolete normative reference: RFC 2271 (ref. '1') (Obsoleted by RFC 2571) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Obsolete normative reference: RFC 1902 (ref. '5') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '6') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '7') (Obsoleted by RFC 2580) ** 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 2272 (ref. '11') (Obsoleted by RFC 2572) ** Obsolete normative reference: RFC 2274 (ref. '12') (Obsoleted by RFC 2574) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2273 (ref. '14') (Obsoleted by RFC 2573) -- Possible downref: Non-RFC (?) normative reference: ref. '15' -- Possible downref: Non-RFC (?) normative reference: ref. '16' -- Possible downref: Non-RFC (?) normative reference: ref. '17' ** Obsolete normative reference: RFC 2362 (ref. '18') (Obsoleted by RFC 4601, RFC 5059) -- Possible downref: Non-RFC (?) normative reference: ref. '19' Summary: 22 errors (**), 0 flaws (~~), 2 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IDMR Working Group Keith McCloghrie 3 INTERNET-DRAFT Dino Farinacci 4 Expires January 1999 cisco Systems 5 Dave Thaler 6 Microsoft 7 28 July 1998 9 Protocol Independent Multicast MIB 10 12 Status of this Memo 14 This document is an Internet-Draft. Internet-Drafts are working 15 documents of the Internet Engineering Task Force (IETF), its areas, and 16 its working groups. Note that other groups may also distribute working 17 documents as Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six months 20 and may be updated, replaced, or obsoleted by other documents at any 21 time. It is inappropriate to use Internet-Drafts as reference material 22 or to cite them other than as ``work in progress.'' 24 Copyright Notice 26 Copyright (C) The Internet Society (1998). All Rights Reserved. 28 1. Introduction 30 This memo defines an experimental portion of the Management Information 31 Base (MIB) for use with network management protocols in the Internet 32 community. In particular, it describes managed objects used for 33 managing the Protocol Independent Multicast (PIM) protocol 34 [16,17,18,19]. This MIB module is applicable to IP multicast routers 35 which implement PIM. 37 Draft PIM MIB July 1998 39 2. Revision History 41 A record of changes which will be removed before publication. 43 28 July 1998 45 (1) added sparseDense as a legal value for pimInterfaceMode for 46 backwards compatability with PIMv1 routers which can do both modes 47 on the same interface. 49 (2) filled in Security Considerations, added copyright, updated SNMP 50 boilerplate, and updated references 52 20 November 1997 54 (1) undeprecated pimInterfaceMode since ipMRouteInterfaceProtocol was 55 changed to read-only. 57 (2) added pimRPSetComponent as an index to the RP-Set Table. 59 25 March 61 (1) deprecated pimInterfaceMode, which is obsoleted by 62 ipMRouteInterfaceProtocol in the IP Multicast MIB. 64 (2) deprecated pimNeighborMode (to retain support for PIM version 1). 66 (3) moved pimCandidateBSRPreference to the PIM Interface Table and 67 renamed it pimInterfaceCBSRPreference. 69 (4) moved pimBSRAddress, pimBSRExpiryTime, and pimCandidateRPHoldTime 70 to the new PIM Component Table, to manage border routers connected 71 to multiple PIM-SM domains. 73 (5) renamed pimMessageInterval to pimJoinPruneInterval and 74 pimInterfaceQueryInterval to pimInterfaceHelloInterval. 76 (6) added pimInterfaceJoinPruneInterval. 78 (7) added pimRPSetComponent as an INDEX in the PIM RP-Set Table 80 9 June: 82 (1) added pimRPSetTable and pimCandidateRPTable. 84 Draft PIM MIB July 1998 86 (2) deprecated pimRPTable (to retain support for PIM version 1). 88 (3) removed pimGroupTable. 90 (4) added pimBSRAddress, pimBSRExpiryTime, pimCandidateBSRPreference 91 and pimCandidateRPHoldTime. 93 4 November: 95 (1) changed the PIM Group table to hold information common to all RPs 96 of a group. 98 (2) added the PIM RP table with each entry specific to an RP of a 99 group. 101 (3) added pimNeighborMode 103 (4) modified the pimGroupTable to be indexed by pimGroupAddress and 104 pimGroupRP, in order to allow for multiple RPs per group. 106 15 July - initial version. 108 3. The SNMP Network Management Framework 110 The SNMP Management Framework presently consists of five major 111 components: 113 o An overall architecture, described in RFC 2271 [1]. 115 o Mechanisms for describing and naming objects and events for the 116 purpose of management. The first version of this Structure of 117 Management Information (SMI) is called SMIv1 and described in RFC 118 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, called 119 SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 1904 [7]. 121 o Message protocols for transferring management information. The 122 first version of the SNMP message protocol is called SNMPv1 and 123 described in RFC 1157 [8]. A second version of the SNMP message 124 protocol, which is not an Internet standards track protocol, is 125 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 126 The third version of the message protocol is called SNMPv3 and 127 described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. 129 Draft PIM MIB July 1998 131 o Protocol operations for accessing management information. The first 132 set of protocol operations and associated PDU formats is described 133 in RFC 1157 [8]. A second set of protocol operations and associated 134 PDU formats is described in RFC 1905 [13]. 136 o A set of fundamental applications described in RFC 2273 [14] and 137 the view-based access control mechanism described in RFC 2275 [15]. 139 Managed objects are accessed via a virtual information store, termed the 140 Management Information Base or MIB. Objects in the MIB are defined 141 using the mechanisms defined in the SMI. 143 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 144 conforming to the SMIv1 can be produced through the appropriate 145 translations. The resulting translated MIB must be semantically 146 equivalent, except where objects or events are omitted because no 147 translation is possible (use of Counter64). Some machine readable 148 information in SMIv2 will be converted into textual descriptions in 149 SMIv1 during the translation process. However, this loss of machine 150 readable information is not considered to change the semantics of the 151 MIB. 153 3.1. Object Definitions 155 Managed objects are accessed via a virtual information store, termed the 156 Management Information Base or MIB. Objects in the MIB are defined 157 using the subset of Abstract Syntax Notation One (ASN.1) defined in the 158 SMI. In particular, each object type is named by an OBJECT IDENTIFIER, 159 an administratively assigned name. The object type together with an 160 object instance serves to uniquely identify a specific instantiation of 161 the object. For human convenience, we often use a textual string, 162 termed the descriptor, to refer to the object type. 164 4. Overview 166 This MIB module contains one scalar and six tables. The tables are: 168 (1) the PIM Interface Table which contains one row for each of the 169 router's PIM interfaces; 171 (2) the PIM Neighbor Table which contains one row for each of the 172 router's PIM neighbors; and 174 Draft PIM MIB July 1998 176 (3) the PIM RP-Set Table which contains the PIM (version 2) information 177 for sets of candidate Rendezvous Points (RPs) for IP multicast 178 group addresses with particular address prefixes. 180 (4) the PIM Candidate-RP Table which contains the IP multicast groups 181 for which the local router is to advertise itself as a Candidate- 182 RP. If this table is empty, then the local router advertises 183 itself as a Candidate-RP for all groups. 185 (5) the (deprecated) PIM RP Table which contains the PIM (version 1) 186 information for IP multicast groups which is common to all RPs of a 187 group; 189 (6) the PIM Component Table which contains one row for each of the PIM 190 domains to which the router is connected. 192 Draft PIM MIB July 1998 194 5. Definitions 196 PIM-MIB DEFINITIONS ::= BEGIN 198 IMPORTS 199 MODULE-IDENTITY, OBJECT-TYPE, experimental, 200 Integer32, IpAddress, TimeTicks FROM SNMPv2-SMI 201 RowStatus FROM SNMPv2-TC 202 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 204 pimMIB MODULE-IDENTITY 205 LAST-UPDATED "9807281630Z" 206 ORGANIZATION "IETF IDMR Working Group." 207 CONTACT-INFO 208 " Keith McCloghrie 209 Cisco Systems, Inc. 210 170 West Tasman Drive 211 San Jose, CA 95134-1706 212 US 214 Phone: +1 408 526 5260 215 EMail: kzm@cisco.com" 216 DESCRIPTION 217 "The MIB module for management of PIM routers." 218 ::= { experimental 61 } 220 pimMIBObjects OBJECT IDENTIFIER ::= { pimMIB 1 } 222 pim OBJECT IDENTIFIER ::= { pimMIBObjects 1 } 224 pimJoinPruneInterval OBJECT-TYPE 225 SYNTAX Integer32 226 UNITS "seconds" 227 MAX-ACCESS read-write 228 STATUS current 229 DESCRIPTION 230 "The default interval at which periodic PIM-SM Join/Prune 231 messages are to be sent." 232 ::= { pim 1 } 234 Draft PIM MIB July 1998 236 -- The PIM Interface Table 238 pimInterfaceTable OBJECT-TYPE 239 SYNTAX SEQUENCE OF PimInterfaceEntry 240 MAX-ACCESS not-accessible 241 STATUS current 242 DESCRIPTION 243 "The (conceptual) table listing the router's PIM interfaces. 244 IGMP and PIM are enabled on all interfaces listed in this 245 table." 246 ::= { pim 2 } 248 pimInterfaceEntry OBJECT-TYPE 249 SYNTAX PimInterfaceEntry 250 MAX-ACCESS not-accessible 251 STATUS current 252 DESCRIPTION 253 "An entry (conceptual row) in the pimInterfaceTable." 254 INDEX { pimInterfaceIfIndex } 255 ::= { pimInterfaceTable 1 } 257 PimInterfaceEntry ::= SEQUENCE { 258 pimInterfaceIfIndex Integer32, 259 pimInterfaceAddress IpAddress, 260 pimInterfaceNetMask IpAddress, 261 pimInterfaceMode INTEGER, 262 pimInterfaceDR IpAddress, 263 pimInterfaceHelloInterval Integer32, 264 pimInterfaceStatus RowStatus, 265 pimInterfaceJoinPruneInterval Integer32, 266 pimInterfaceCBSRPreference Integer32 267 } 269 pimInterfaceIfIndex OBJECT-TYPE 270 SYNTAX Integer32 271 MAX-ACCESS not-accessible 272 STATUS current 273 DESCRIPTION 274 "The ifIndex value of this PIM interface." 275 ::= { pimInterfaceEntry 1 } 277 pimInterfaceAddress OBJECT-TYPE 278 SYNTAX IpAddress 279 MAX-ACCESS read-only 280 STATUS current 282 Draft PIM MIB July 1998 284 DESCRIPTION 285 "The IP address of the PIM interface." 286 ::= { pimInterfaceEntry 2 } 288 pimInterfaceNetMask OBJECT-TYPE 289 SYNTAX IpAddress 290 MAX-ACCESS read-only 291 STATUS current 292 DESCRIPTION 293 "The network mask for the IP address of the PIM interface." 294 ::= { pimInterfaceEntry 3 } 296 pimInterfaceMode OBJECT-TYPE 297 SYNTAX INTEGER { dense(1), sparse(2), sparseDense(3) } 298 MAX-ACCESS read-create 299 STATUS current 300 DESCRIPTION 301 "The configured mode of this PIM interface. A value of 302 sparseDense is only valid for PIMv1." 303 DEFVAL { dense } 304 ::= { pimInterfaceEntry 4 } 306 pimInterfaceDR OBJECT-TYPE 307 SYNTAX IpAddress 308 MAX-ACCESS read-only 309 STATUS current 310 DESCRIPTION 311 "The Designated Router on this PIM interface. For point- 312 to-point interfaces, this object has the value 0.0.0.0." 313 ::= { pimInterfaceEntry 5 } 315 pimInterfaceHelloInterval OBJECT-TYPE 316 SYNTAX Integer32 317 UNITS "seconds" 318 MAX-ACCESS read-create 319 STATUS current 320 DESCRIPTION 321 "The frequency at which PIM Hello messages are transmitted 322 on this interface." 323 DEFVAL { 30 } 324 ::= { pimInterfaceEntry 6 } 326 pimInterfaceStatus OBJECT-TYPE 327 SYNTAX RowStatus 328 MAX-ACCESS read-create 330 Draft PIM MIB July 1998 332 STATUS current 333 DESCRIPTION 334 "The status of this entry. Creating the entry enables PIM 335 on the interface; destroying the entry disables PIM on the 336 interface." 337 ::= { pimInterfaceEntry 7 } 339 pimInterfaceJoinPruneInterval OBJECT-TYPE 340 SYNTAX Integer32 341 UNITS "seconds" 342 MAX-ACCESS read-create 343 STATUS current 344 DESCRIPTION 345 "The frequency at which PIM Join/Prune messages are 346 transmitted on this PIM interface. The default value of 347 this object is the pimJoinPruneInterval." 348 ::= { pimInterfaceEntry 8 } 350 pimInterfaceCBSRPreference OBJECT-TYPE 351 SYNTAX Integer32 (-1..255) 352 MAX-ACCESS read-create 353 STATUS current 354 DESCRIPTION 355 "The preference value for the local interface as a candidate 356 bootstrap router. The value of -1 is used to indicate that 357 the local interface is not a candidate BSR interface." 358 DEFVAL { 0 } 359 ::= { pimInterfaceEntry 9 } 361 -- The PIM Neighbor Table 363 pimNeighborTable OBJECT-TYPE 364 SYNTAX SEQUENCE OF PimNeighborEntry 365 MAX-ACCESS not-accessible 366 STATUS current 367 DESCRIPTION 368 "The (conceptual) table listing the router's PIM neighbors." 369 ::= { pim 3 } 371 pimNeighborEntry OBJECT-TYPE 372 SYNTAX PimNeighborEntry 373 MAX-ACCESS not-accessible 374 STATUS current 375 DESCRIPTION 377 Draft PIM MIB July 1998 379 "An entry (conceptual row) in the pimNeighborTable." 380 INDEX { pimNeighborAddress } 381 ::= { pimNeighborTable 1 } 383 PimNeighborEntry ::= SEQUENCE { 384 pimNeighborAddress IpAddress, 385 pimNeighborIfIndex Integer32, 386 pimNeighborUpTime TimeTicks, 387 pimNeighborExpiryTime TimeTicks, 388 pimNeighborMode INTEGER 389 } 391 pimNeighborAddress OBJECT-TYPE 392 SYNTAX IpAddress 393 MAX-ACCESS not-accessible 394 STATUS current 395 DESCRIPTION 396 "The IP address of the PIM neighbor for which this entry 397 contains information." 398 ::= { pimNeighborEntry 1 } 400 pimNeighborIfIndex OBJECT-TYPE 401 SYNTAX Integer32 402 MAX-ACCESS read-only 403 STATUS current 404 DESCRIPTION 405 "The value of ifIndex for the interface used to reach this 406 PIM neighbor." 407 ::= { pimNeighborEntry 2 } 409 pimNeighborUpTime OBJECT-TYPE 410 SYNTAX TimeTicks 411 MAX-ACCESS read-only 412 STATUS current 413 DESCRIPTION 414 "The time since this PIM neighbor (last) became a neighbor 415 of the local router." 416 ::= { pimNeighborEntry 3 } 418 pimNeighborExpiryTime OBJECT-TYPE 419 SYNTAX TimeTicks 420 MAX-ACCESS read-only 421 STATUS current 422 DESCRIPTION 423 "The minimum time remaining before this PIM neighbor will be 425 Draft PIM MIB July 1998 427 aged out." 428 ::= { pimNeighborEntry 4 } 430 pimNeighborMode OBJECT-TYPE 431 SYNTAX INTEGER { dense(1), sparse(2) } 432 MAX-ACCESS read-only 433 STATUS deprecated 434 DESCRIPTION 435 "The active PIM mode of this neighbor. This object is 436 deprecated for PIMv2 routers since all neighbors on the 437 interface must be either dense or sparse as determined by 438 the protocol running on the interface." 439 ::= { pimNeighborEntry 5 } 441 -- The PIM RP Table 443 pimRPTable OBJECT-TYPE 444 SYNTAX SEQUENCE OF PimRPEntry 445 MAX-ACCESS not-accessible 446 STATUS deprecated 447 DESCRIPTION 448 "The (conceptual) table listing PIM version 1 information 449 for the Rendezvous Points (RPs) for IP multicast groups. 450 This table is deprecated since its function is replaced by 451 the pimRPSetTable for PIM version 2." 452 ::= { pim 5 } 454 pimRPEntry OBJECT-TYPE 455 SYNTAX PimRPEntry 456 MAX-ACCESS not-accessible 457 STATUS deprecated 458 DESCRIPTION 459 "An entry (conceptual row) in the pimRPTable. There is one 460 entry per RP address for each IP multicast group." 461 INDEX { pimRPGroupAddress, pimRPAddress } 462 ::= { pimRPTable 1 } 464 Draft PIM MIB July 1998 466 PimRPEntry ::= SEQUENCE { 467 pimRPGroupAddress IpAddress, 468 pimRPAddress IpAddress, 469 pimRPState INTEGER, 470 pimRPStateTimer TimeTicks, 471 pimRPLastChange TimeTicks, 472 pimRPRowStatus RowStatus 473 } 475 pimRPGroupAddress OBJECT-TYPE 476 SYNTAX IpAddress 477 MAX-ACCESS not-accessible 478 STATUS deprecated 479 DESCRIPTION 480 "The IP multicast group address for which this entry 481 contains information about an RP." 482 ::= { pimRPEntry 1 } 484 pimRPAddress OBJECT-TYPE 485 SYNTAX IpAddress 486 MAX-ACCESS not-accessible 487 STATUS deprecated 488 DESCRIPTION 489 "The IP multicast group address for which this entry 490 contains PIM version 1 information about an RP." 491 ::= { pimRPEntry 2 } 493 pimRPState OBJECT-TYPE 494 SYNTAX INTEGER { up(1), down(2) } 495 MAX-ACCESS read-only 496 STATUS deprecated 497 DESCRIPTION 498 "The state of the RP." 499 ::= { pimRPEntry 3 } 501 pimRPStateTimer OBJECT-TYPE 502 SYNTAX TimeTicks 503 MAX-ACCESS read-only 504 STATUS deprecated 505 DESCRIPTION 506 "The minimum time remaining before the next state change. 507 When pimRPState is up, this is the minimum time which must 508 expire until it can be declared down. When pimRPState is 509 down, this is the time until it will be declared up (in 510 order to retry)." 512 Draft PIM MIB July 1998 514 ::= { pimRPEntry 4 } 516 pimRPLastChange OBJECT-TYPE 517 SYNTAX TimeTicks 518 MAX-ACCESS read-only 519 STATUS deprecated 520 DESCRIPTION 521 "The value of sysUpTime at the time when the corresponding 522 instance of pimRPState last changed its value." 523 ::= { pimRPEntry 5 } 525 pimRPRowStatus OBJECT-TYPE 526 SYNTAX RowStatus 527 MAX-ACCESS read-create 528 STATUS deprecated 529 DESCRIPTION 530 "The status of this row, by which new entries may be 531 created, or old entries deleted from this table." 532 ::= { pimRPEntry 6 } 534 -- The PIM RP-Set Table 536 pimRPSetTable OBJECT-TYPE 537 SYNTAX SEQUENCE OF PimRPSetEntry 538 MAX-ACCESS not-accessible 539 STATUS current 540 DESCRIPTION 541 "The (conceptual) table listing PIM information for 542 candidate Rendezvous Points (RPs) for IP multicast groups. 543 When the local router is the BSR, this information is 544 obtained from received Candidate-RP-Advertisements. When 545 the local router is not the BSR, this information is 546 obtained from received RP-Set messages." 547 ::= { pim 6 } 549 pimRPSetEntry OBJECT-TYPE 550 SYNTAX PimRPSetEntry 551 MAX-ACCESS not-accessible 552 STATUS current 553 DESCRIPTION 554 "An entry (conceptual row) in the pimRPSetTable." 555 INDEX { pimRPSetComponent, pimRPSetGroupAddress, 556 pimRPSetGroupMask, pimRPSetAddress } 557 ::= { pimRPSetTable 1 } 559 Draft PIM MIB July 1998 561 PimRPSetEntry ::= SEQUENCE { 562 pimRPSetGroupAddress IpAddress, 563 pimRPSetGroupMask IpAddress, 564 pimRPSetAddress IpAddress, 565 pimRPSetHoldTime Integer32, 566 pimRPSetExpiryTime TimeTicks, 567 pimRPSetComponent Integer32 568 } 570 pimRPSetGroupAddress OBJECT-TYPE 571 SYNTAX IpAddress 572 MAX-ACCESS not-accessible 573 STATUS current 574 DESCRIPTION 575 "The IP multicast group address which, when combined with 576 pimRPSetGroupMask, gives the group prefix for which this 577 entry contains information about the Candidate-RP." 578 ::= { pimRPSetEntry 1 } 580 pimRPSetGroupMask OBJECT-TYPE 581 SYNTAX IpAddress 582 MAX-ACCESS not-accessible 583 STATUS current 584 DESCRIPTION 585 "The multicast group address mask which, when combined with 586 pimRPSetGroupAddress, gives the group prefix for which this 587 entry contains information about the Candidate-RP." 588 ::= { pimRPSetEntry 2 } 590 pimRPSetAddress OBJECT-TYPE 591 SYNTAX IpAddress 592 MAX-ACCESS not-accessible 593 STATUS current 594 DESCRIPTION 595 "The IP address of the Candidate-RP." 596 ::= { pimRPSetEntry 3 } 598 pimRPSetHoldTime OBJECT-TYPE 599 SYNTAX Integer32 (0..255) 600 UNITS "seconds" 601 MAX-ACCESS read-only 602 STATUS current 603 DESCRIPTION 604 "The holdtime of a Candidate-RP. If the local router is not 605 the BSR, this value is 0." 607 Draft PIM MIB July 1998 609 ::= { pimRPSetEntry 4 } 611 pimRPSetExpiryTime OBJECT-TYPE 612 SYNTAX TimeTicks 613 MAX-ACCESS read-only 614 STATUS current 615 DESCRIPTION 616 "The minimum time remaining before the Candidate-RP will be 617 declared down. If the local router is not the BSR, this 618 value is 0." 619 ::= { pimRPSetEntry 5 } 621 pimRPSetComponent OBJECT-TYPE 622 SYNTAX Integer32 623 MAX-ACCESS not-accessible 624 STATUS current 625 DESCRIPTION 626 "A number uniquely identifying the component. Each protocol 627 instance connected to a separate domain should have a 628 different index value." 629 ::= { pimRPSetEntry 6 } 631 -- The PIM Candidate-RP Table 633 pimCandidateRPTable OBJECT-TYPE 634 SYNTAX SEQUENCE OF PimCandidateRPEntry 635 MAX-ACCESS not-accessible 636 STATUS current 637 DESCRIPTION 638 "The (conceptual) table listing the IP multicast groups for 639 which the local router is to advertise itself as a 640 Candidate-RP when the value of pimCandidateRPHoldTime is 641 non-zero. If this table is empty, then the local router 642 will advertise itself as a Candidate-RP for all groups 643 (providing the value of pimCandidateRPHoldTime is non- 644 zero)." 645 ::= { pim 11 } 647 pimCandidateRPEntry OBJECT-TYPE 648 SYNTAX PimCandidateRPEntry 649 MAX-ACCESS not-accessible 650 STATUS current 651 DESCRIPTION 652 "An entry (conceptual row) in the pimCandidateRPTable." 654 Draft PIM MIB July 1998 656 INDEX { pimCandidateRPGroupAddress, 657 pimCandidateRPGroupMask } 658 ::= { pimCandidateRPTable 1 } 660 PimCandidateRPEntry ::= SEQUENCE { 661 pimCandidateRPGroupAddress IpAddress, 662 pimCandidateRPGroupMask IpAddress, 663 pimCandidateRPAddress IpAddress, 664 pimCandidateRPRowStatus RowStatus 665 } 667 pimCandidateRPGroupAddress OBJECT-TYPE 668 SYNTAX IpAddress 669 MAX-ACCESS not-accessible 670 STATUS current 671 DESCRIPTION 672 "The IP multicast group address which, when combined with 673 pimCandidateRPGroupMask, identifies a group prefix for which 674 the local router will advertise itself as a Candidate-RP." 675 ::= { pimCandidateRPEntry 1 } 677 pimCandidateRPGroupMask OBJECT-TYPE 678 SYNTAX IpAddress 679 MAX-ACCESS not-accessible 680 STATUS current 681 DESCRIPTION 682 "The multicast group address mask which, when combined with 683 pimCandidateRPGroupMask, identifies a group prefix for which 684 the local router will advertise itself as a Candidate-RP." 685 ::= { pimCandidateRPEntry 2 } 687 pimCandidateRPAddress OBJECT-TYPE 688 SYNTAX IpAddress 689 MAX-ACCESS read-create 690 STATUS current 691 DESCRIPTION 692 "The (unicast) address of the interface which will be 693 advertised as a Candidate-RP." 694 ::= { pimCandidateRPEntry 3 } 696 pimCandidateRPRowStatus OBJECT-TYPE 697 SYNTAX RowStatus 698 MAX-ACCESS read-create 699 STATUS current 700 DESCRIPTION 702 Draft PIM MIB July 1998 704 "The status of this row, by which new entries may be 705 created, or old entries deleted from this table." 706 ::= { pimCandidateRPEntry 4 } 708 -- The PIM Component Table 710 pimComponentTable OBJECT-TYPE 711 SYNTAX SEQUENCE OF PimComponentEntry 712 MAX-ACCESS not-accessible 713 STATUS current 714 DESCRIPTION 715 "The (conceptual) table containing objects specific to a PIM 716 domain. One row exists for each domain to which the router 717 is connected." 718 ::= { pim 12 } 720 pimComponentEntry OBJECT-TYPE 721 SYNTAX PimComponentEntry 722 MAX-ACCESS not-accessible 723 STATUS current 724 DESCRIPTION 725 "An entry (conceptual row) in the pimComponentTable." 726 INDEX { pimComponentIndex } 727 ::= { pimComponentTable 1 } 729 PimComponentEntry ::= SEQUENCE { 730 pimComponentIndex Integer32, 731 pimComponentBSRAddress IpAddress, 732 pimComponentBSRExpiryTime TimeTicks, 733 pimComponentCRPHoldTime Integer32, 734 pimComponentStatus RowStatus 735 } 737 pimComponentIndex OBJECT-TYPE 738 SYNTAX Integer32 739 MAX-ACCESS not-accessible 740 STATUS current 741 DESCRIPTION 742 "A number uniquely identifying the component. Each protocol 743 instance connected to a separate domain should have a 744 different index value." 745 ::= { pimComponentEntry 1 } 747 pimComponentBSRAddress OBJECT-TYPE 748 SYNTAX IpAddress 750 Draft PIM MIB July 1998 752 MAX-ACCESS read-only 753 STATUS current 754 DESCRIPTION 755 "The IP address of the bootstrap router (BSR) for the local 756 PIM region." 757 ::= { pimComponentEntry 2 } 759 pimComponentBSRExpiryTime OBJECT-TYPE 760 SYNTAX TimeTicks 761 MAX-ACCESS read-only 762 STATUS current 763 DESCRIPTION 764 "The minimum time remaining before the bootstrap router in 765 the local domain will be declared down. For candidate BSRs, 766 this is the time until the component sends an RP-Set 767 message. For other routers, this is the time until it may 768 accept an RP-Set message from a lower candidate BSR." 769 ::= { pimComponentEntry 3 } 771 pimComponentCRPHoldTime OBJECT-TYPE 772 SYNTAX Integer32 (0..255) 773 UNITS "seconds" 774 MAX-ACCESS read-create 775 STATUS current 776 DESCRIPTION 777 "The holdtime of the component when it is a candidate RP in 778 the local domain. The value of 0 is used to indicate that 779 the local system is not a Candidate-RP." 780 DEFVAL { 0 } 781 ::= { pimComponentEntry 4 } 783 pimComponentStatus OBJECT-TYPE 784 SYNTAX RowStatus 785 MAX-ACCESS read-create 786 STATUS current 787 DESCRIPTION 788 "The status of this entry. Creating the entry creates 789 another protocol instance; destroying the entry disables a 790 protocol instance." 791 ::= { pimComponentEntry 5 } 793 Draft PIM MIB July 1998 795 -- conformance information 797 pimMIBConformance OBJECT IDENTIFIER ::= { pimMIB 2 } 798 pimMIBCompliances OBJECT IDENTIFIER ::= { pimMIBConformance 1 } 799 pimMIBGroups OBJECT IDENTIFIER ::= { pimMIBConformance 2 } 801 -- compliance statements 803 pimV1MIBCompliance MODULE-COMPLIANCE 804 STATUS deprecated 805 DESCRIPTION 806 "The compliance statement for routers running PIMv1 and 807 implementing the PIM MIB." 808 MODULE -- this module 809 MANDATORY-GROUPS { pimV1MIBGroup } 811 ::= { pimMIBCompliances 1 } 813 pimSparseV2MIBCompliance MODULE-COMPLIANCE 814 STATUS current 815 DESCRIPTION 816 "The compliance statement for routers running PIM Sparse 817 Mode and implementing the PIM MIB." 818 MODULE -- this module 819 MANDATORY-GROUPS { pimV2MIBGroup } 821 OBJECT pimInterfaceStatus 822 MIN-ACCESS read-only 823 DESCRIPTION 824 "Write access is not required." 826 ::= { pimMIBCompliances 2 } 828 pimDenseV2MIBCompliance MODULE-COMPLIANCE 829 STATUS current 830 DESCRIPTION 831 "The compliance statement for routers running PIM Dense Mode 832 and implementing the PIM MIB." 833 MODULE -- this module 834 MANDATORY-GROUPS { pimDenseV2MIBGroup } 836 OBJECT pimInterfaceStatus 837 MIN-ACCESS read-only 838 DESCRIPTION 840 Draft PIM MIB July 1998 842 "Write access is not required." 844 ::= { pimMIBCompliances 3 } 846 -- units of conformance 848 pimV2MIBGroup OBJECT-GROUP 849 OBJECTS { pimJoinPruneInterval, pimNeighborIfIndex, 850 pimNeighborUpTime, pimNeighborExpiryTime, 851 pimInterfaceAddress, pimInterfaceNetMask, 852 pimInterfaceDR, pimInterfaceHelloInterval, 853 pimInterfaceStatus, pimInterfaceJoinPruneInterval, 854 pimInterfaceCBSRPreference, pimInterfaceMode, 855 pimRPSetHoldTime, pimRPSetExpiryTime, 856 pimComponentBSRAddress, pimComponentBSRExpiryTime, 857 pimComponentCRPHoldTime, pimComponentStatus 858 } 859 STATUS current 860 DESCRIPTION 861 "A collection of objects to support management of PIM Sparse 862 Mode (version 2) routers." 863 ::= { pimMIBGroups 2 } 865 pimDenseV2MIBGroup OBJECT-GROUP 866 OBJECTS { pimNeighborIfIndex, 867 pimNeighborUpTime, pimNeighborExpiryTime, 868 pimInterfaceAddress, pimInterfaceNetMask, 869 pimInterfaceDR, pimInterfaceHelloInterval, 870 pimInterfaceStatus, pimInterfaceMode 871 } 872 STATUS current 873 DESCRIPTION 874 "A collection of objects to support management of PIM Dense 875 Mode (version 2) routers." 876 ::= { pimMIBGroups 5 } 878 pimV2CandidateRPMIBGroup OBJECT-GROUP 879 OBJECTS { pimCandidateRPAddress, 880 pimCandidateRPRowStatus 881 } 882 STATUS current 883 DESCRIPTION 884 "A collection of objects to support configuration of which 885 groups a router is to advertise itself as a Candidate-RP." 887 Draft PIM MIB July 1998 889 ::= { pimMIBGroups 3 } 891 pimV1MIBGroup OBJECT-GROUP 892 OBJECTS { pimJoinPruneInterval, pimNeighborIfIndex, 893 pimNeighborUpTime, pimNeighborExpiryTime, 894 pimNeighborMode, 895 pimInterfaceAddress, pimInterfaceNetMask, 896 pimInterfaceMode, pimInterfaceDR, 897 pimInterfaceHelloInterval, 898 pimRPState, pimRPStateTimer, 899 pimRPLastChange, pimRPRowStatus 900 } 901 STATUS deprecated 902 DESCRIPTION 903 "A collection of objects to support management of PIM 904 (version 1) routers." 905 ::= { pimMIBGroups 4 } 907 END 908 Draft PIM MIB July 1998 910 6. Security Considerations 912 This MIB contains readable objects whose values provide information 913 related to multicast routing, including information on the network 914 topology. There are also a number of objects that have a MAX-ACCESS 915 clause of read-write and/or read-create, which allow an administrator to 916 configure PIM in the router. 918 While unauthorized access to the readable objects is relatively 919 innocuous, unauthorized access to the write-able objects could cause a 920 denial of service. Hence, the support for SET operations in a non- 921 secure environment without proper protection can have a negative effect 922 on network operations. 924 SNMPv1 by itself is such an insecure environment. Even if the network 925 itself is secure (for example by using IPSec), even then, there is no 926 control as to who on the secure network is allowed to access and SET 927 (change/create/delete) the objects in this MIB. 929 It is recommended that the implementers consider the security features 930 as provided by the SNMPv3 framework. Specifically, the use of the 931 User-based Security Model RFC 2274 [12] and the View-based Access 932 Control Model RFC 2275 [15] is recommended. 934 It is then a customer/user responsibility to ensure that the SNMP entity 935 giving access to this MIB, is properly configured to give access to 936 those objects only to those principals (users) that have legitimate 937 rights to access them. 939 7. Acknowledgements 941 This MIB module has been updated based on feedback from the IETF's 942 Inter-Domain Multicast Routing (IDMR) Working Group. 944 8. Authors' Addresses 946 Keith McCloghrie 947 cisco Systems, Inc. 948 170 West Tasman Drive 949 San Jose, CA 95134-1706 950 Phone: +1 408 526 5260 952 Draft PIM MIB July 1998 954 EMail: kzm@cisco.com 956 Dino Farinacci 957 cisco Systems, Inc. 958 170 West Tasman Drive 959 San Jose, CA 95134-1706 960 Phone: +1 408 526 4696 961 EMail: dino@cisco.com 963 Dave Thaler 964 Microsoft Corporation 965 One Microsoft Way 966 Redmond, WA 48105-6399 967 Phone: +1 425 703 8835 968 EMail: dthaler@microsoft.com 970 9. References 972 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 973 Describing SNMP Management Frameworks", RFC 2271, Cabletron 974 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 975 January 1998. 977 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 978 Management Information for TCP/IP-based Internets", RFC 1155, 979 Performance Systems International, Hughes LAN Systems, May 1990. 981 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 982 Performance Systems International, Hughes LAN Systems, March 1991. 984 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 985 RFC 1215, Performance Systems International, March 1991. 987 [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure 988 of Management Information for Version 2 of the Simple Network 989 Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco 990 Systems, Inc., Dover Beach Consulting, Inc., International Network 991 Services, January 1996. 993 [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 994 Conventions for Version 2 of the Simple Network Management Protocol 995 (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., 996 Dover Beach Consulting, Inc., International Network Services, 998 Draft PIM MIB July 1998 1000 January 1996. 1002 [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance 1003 Statements for Version 2 of the Simple Network Management Protocol 1004 (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, Inc., 1005 Dover Beach Consulting, Inc., International Network Services, 1006 January 1996. 1008 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 1009 Management Protocol", RFC 1157, SNMP Research, Performance Systems 1010 International, Performance Systems International, MIT Laboratory 1011 for Computer Science, May 1990. 1013 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1014 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 1015 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1016 International Network Services, January 1996. 1018 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 1019 Mappings for Version 2 of the Simple Network Management Protocol 1020 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 1021 Dover Beach Consulting, Inc., International Network Services, 1022 January 1996. 1024 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1025 Processing and Dispatching for the Simple Network Management 1026 Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems, 1027 Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998. 1029 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 1030 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 1031 2274, IBM T. J. Watson Research, January 1998. 1033 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1034 Operations for Version 2 of the Simple Network Management Protocol 1035 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 1036 Dover Beach Consulting, Inc., International Network Services, 1037 January 1996. 1039 [14] Levi, D., Meyer, P., and B. Stewart, "MPv3 Applications", RFC 2273, 1040 SNMP Research, Inc., Secure Computing Corporation, Cisco Systems, 1041 January 1998. 1043 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1044 Control Model (VACM) for the Simple Network Management Protocol 1046 Draft PIM MIB July 1998 1048 (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc., 1049 Cisco Systems, Inc., January 1998. 1051 [16] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Liu, G., and 1052 L. Wei, "Protocol Independent Multicast (PIM): Motivation and 1053 Architecture", January 1995. 1055 [17] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Liu, G., and 1056 L. Wei, "Protocol Independent Multicast (PIM): Protocol 1057 Specification", January 1995. 1059 [18] Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering, S., 1060 Handley, M., Jacobson, V., Liu, C., Sharma, P., and L. Wei, 1061 "Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol 1062 Specification", RFC 2362, June 1998. 1064 [19] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Helmy, A., 1065 and L. Wei, "Protocol Independent Multicast Version 2, Dense Mode 1066 Specification". May 1997. 1068 10. Full Copyright Statement 1070 Copyright (C) The Internet Society (1998). All Rights Reserved. 1072 This document and translations of it may be copied and furnished to 1073 others, and derivative works that comment on or otherwise explain it or 1074 assist in its implmentation may be prepared, copied, published and 1075 distributed, in whole or in part, without restriction of any kind, 1076 provided that the above copyright notice and this paragraph are included 1077 on all such copies and derivative works. However, this document itself 1078 may not be modified in any way, such as by removing the copyright notice 1079 or references to the Internet Society or other Internet organizations, 1080 except as needed for the purpose of developing Internet standards in 1081 which case the procedures for copyrights defined in the Internet 1082 Standards process must be followed, or as required to translate it into 1083 languages other than English. 1085 The limited permissions granted above are perpetual and will not be 1086 revoked by the Internet Society or its successors or assigns. 1088 This document and the information contained herein is provided on an "AS 1089 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 1090 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 1091 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 1092 Draft PIM MIB July 1998 1094 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 1095 FITNESS FOR A PARTICULAR PURPOSE." 1097 Table of Contents 1099 1 Introduction .................................................... 1 1100 2 Revision History ................................................ 2 1101 3 The SNMP Network Management Framework ........................... 3 1102 3.1 Object Definitions ............................................ 4 1103 4 Overview ........................................................ 4 1104 5 Definitions ..................................................... 6 1105 6 Security Considerations ......................................... 22 1106 7 Acknowledgements ................................................ 22 1107 8 Authors' Addresses .............................................. 22 1108 9 References ...................................................... 23 1109 10 Full Copyright Statement ....................................... 25