| < draft-ietf-pim-mib-v2-09.txt | draft-ietf-pim-mib-v2-10.txt > | |||
|---|---|---|---|---|
| PIM WG R. Sivaramu | PIM WG R. Sivaramu | |||
| Internet-Draft Cisco Systems | Internet-Draft Cisco Systems | |||
| Expires: June 17, 2007 J. Lingard | Proposed Status: Standards Track J. Lingard | |||
| D. McWalter | Expires: September 3, 2007 Arastra, Inc | |||
| Obsoletes: 2934 (if approved) D. McWalter | ||||
| Data Connection Ltd | Data Connection Ltd | |||
| B. Joshi | B. Joshi | |||
| Infosys Technologies Ltd | Infosys Technologies Ltd | |||
| December 14, 2006 | March 2, 2007 | |||
| Protocol Independent Multicast MIB | Protocol Independent Multicast MIB | |||
| draft-ietf-pim-mib-v2-09.txt | draft-ietf-pim-mib-v2-10.txt | |||
| Status of this Memo | Status of this Memo | |||
| By submitting this Internet-Draft, each author represents that any | By submitting this Internet-Draft, each author represents that any | |||
| applicable patent or other IPR claims of which he or she is aware | applicable patent or other IPR claims of which he or she is aware | |||
| have been or will be disclosed, and any of which he or she becomes | have been or will be disclosed, and any of which he or she becomes | |||
| aware will be disclosed, in accordance with Section 6 of BCP 79. | aware will be disclosed, in accordance with Section 6 of BCP 79. | |||
| Internet-Drafts are working documents of the Internet Engineering | Internet-Drafts are working documents of the Internet Engineering | |||
| Task Force (IETF), its areas, and its working groups. Note that | Task Force (IETF), its areas, and its working groups. Note that | |||
| skipping to change at page 1, line 38 ¶ | skipping to change at page 1, line 39 ¶ | |||
| and may be updated, replaced, or obsoleted by other documents at any | and may be updated, replaced, or obsoleted by other documents at any | |||
| time. It is inappropriate to use Internet-Drafts as reference | time. It is inappropriate to use Internet-Drafts as reference | |||
| material or to cite them other than as "work in progress." | material or to cite them other than as "work in progress." | |||
| The list of current Internet-Drafts can be accessed at | The list of current Internet-Drafts can be accessed at | |||
| http://www.ietf.org/ietf/1id-abstracts.txt. | http://www.ietf.org/ietf/1id-abstracts.txt. | |||
| The list of Internet-Draft Shadow Directories can be accessed at | The list of Internet-Draft Shadow Directories can be accessed at | |||
| http://www.ietf.org/shadow.html. | http://www.ietf.org/shadow.html. | |||
| This Internet-Draft will expire on June 17, 2007. | This Internet-Draft will expire on September 3, 2007. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (C) The IETF Trust (2006). | Copyright (C) The IETF Trust (2007). | |||
| Abstract | Abstract | |||
| This memo defines a portion of the Management Information Base (MIB) | This memo defines a portion of the Management Information Base (MIB) | |||
| for use with network management protocols in the Internet community. | for use with network management protocols in the Internet community. | |||
| In particular, it describes managed objects used for managing the | In particular, it describes managed objects used for managing the | |||
| Protocol Independent Multicast (PIM) protocols (PIM-SM, BIDIR-PIM and | Protocol Independent Multicast (PIM) protocols (PIM-SM, BIDIR-PIM and | |||
| PIM-DM). This document is part of work in progress to obsolete RFC | PIM-DM). This document is part of work in progress to obsolete RFC | |||
| 2934, and is to be preferred where the two documents overlap. This | 2934, and is to be preferred where the two documents overlap. This | |||
| document does not obsolete RFC 2934. | document does not obsolete RFC 2934. | |||
| Table of Contents | Table of Contents | |||
| 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 | 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 2. The Internet-Standard Management Framework . . . . . . . . . . 3 | 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 | |||
| 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 | 3. The Internet-Standard Management Framework . . . . . . . . . . 3 | |||
| 4. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 | 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 | |||
| 5. Security Considerations . . . . . . . . . . . . . . . . . . . 81 | 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 | |||
| 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 88 | 6. Security Considerations . . . . . . . . . . . . . . . . . . . 82 | |||
| 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 88 | 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 89 | |||
| 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 89 | 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 90 | |||
| 8.1 Normative References . . . . . . . . . . . . . . . . . . . 89 | 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 90 | |||
| 8.2 Informative References . . . . . . . . . . . . . . . . . . 90 | 9.1 Normative References . . . . . . . . . . . . . . . . . . . 90 | |||
| Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 90 | 9.2 Informative References . . . . . . . . . . . . . . . . . . 91 | |||
| Intellectual Property and Copyright Statements . . . . . . . . 92 | Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 92 | |||
| Intellectual Property and Copyright Statements . . . . . . . . 93 | ||||
| 1. Introduction | 1. Introduction | |||
| This memo defines a portion of the Management Information Base (MIB) | This memo defines a portion of the Management Information Base (MIB) | |||
| for use with network management protocols in the Internet community. | for use with network management protocols in the Internet community. | |||
| In particular, it describes managed objects used for managing the | In particular, it describes managed objects used for managing the | |||
| Protocol Independent Multicast (PIM) protocols (PIM-SM [RFC4601], | Protocol Independent Multicast (PIM) protocols (PIM-SM [RFC4601], | |||
| BIDIR-PIM [I-D.ietf-pim-bidir] and PIM-DM [RFC3973]). | BIDIR-PIM [I-D.ietf-pim-bidir] and PIM-DM [RFC3973]). | |||
| This document is part of work in progress to obsolete RFC 2934 | This document is part of work in progress to obsolete RFC 2934 | |||
| skipping to change at page 3, line 37 ¶ | skipping to change at page 3, line 37 ¶ | |||
| o This MIB module does not include support for managing PIM-SM v1. | o This MIB module does not include support for managing PIM-SM v1. | |||
| o This MIB module does not depend on the IPv4 Multicast Routing MIB | o This MIB module does not depend on the IPv4 Multicast Routing MIB | |||
| defined in RFC 2932 [RFC2932]. | defined in RFC 2932 [RFC2932]. | |||
| o This MIB module includes support for configuring static RPs. | o This MIB module includes support for configuring static RPs. | |||
| o This MIB module includes support for configuring anycast RPs | o This MIB module includes support for configuring anycast RPs | |||
| [RFC4610]. | [RFC4610]. | |||
| 2. Terminology | ||||
| The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", | |||
| "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this | "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this | |||
| document are to be interpreted as described in RFC 2119 [RFC2119]. | document are to be interpreted as described in RFC 2119 [RFC2119]. | |||
| 2. The Internet-Standard Management Framework | 3. The Internet-Standard Management Framework | |||
| For a detailed overview of the documents that describe the current | For a detailed overview of the documents that describe the current | |||
| Internet-Standard Management Framework, please refer to section 7 of | Internet-Standard Management Framework, please refer to section 7 of | |||
| RFC 3410 [RFC3410]. | RFC 3410 [RFC3410]. | |||
| Managed objects are accessed via a virtual information store, termed | Managed objects are accessed via a virtual information store, termed | |||
| the Management Information Base or MIB. MIB objects are generally | the Management Information Base or MIB. MIB objects are generally | |||
| accessed through the Simple Network Management Protocol (SNMP). | accessed through the Simple Network Management Protocol (SNMP). | |||
| Objects in the MIB are defined using the mechanisms defined in the | Objects in the MIB are defined using the mechanisms defined in the | |||
| Structure of Management Information (SMI). This memo specifies a MIB | Structure of Management Information (SMI). This memo specifies a MIB | |||
| module that is compliant to the SMIv2, which is described in STD 58, | module that is compliant to the SMIv2, which is described in STD 58, | |||
| RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 | RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 | |||
| [RFC2580]. | [RFC2580]. | |||
| 3. Overview | 4. Overview | |||
| This MIB module contains the following tables. | This MIB module contains the following tables. | |||
| 1. The PIM Interface Table, which contains one row per IP version | 1. The PIM Interface Table, which contains one row per IP version | |||
| for each interface of the router which is running PIM. | for each interface of the router which is running PIM. | |||
| 2. The PIM Neighbor Table, which contains one row for each of the | 2. The PIM Neighbor Table, which contains one row for each of the | |||
| router's PIM neighbors. | router's PIM neighbors. | |||
| 3. The PIM Neighbor Secondary Address Table, which contains one row | 3. The PIM Neighbor Secondary Address Table, which contains one row | |||
| skipping to change at page 5, line 18 ¶ | skipping to change at page 5, line 19 ¶ | |||
| regardless of the source of the group mapping information. | regardless of the source of the group mapping information. | |||
| 13. The PIM Anycast-RP Set Table, which contains one row for each RP | 13. The PIM Anycast-RP Set Table, which contains one row for each RP | |||
| within each Anycast-RP set of which the local router is a | within each Anycast-RP set of which the local router is a | |||
| member. | member. | |||
| This MIB module uses textual conventions defined in the IF-MIB | This MIB module uses textual conventions defined in the IF-MIB | |||
| [RFC2863], the INET-ADDRESS-MIB [RFC4001] and the IANA-RTPROTO-MIB | [RFC2863], the INET-ADDRESS-MIB [RFC4001] and the IANA-RTPROTO-MIB | |||
| [RTPROTO]. | [RTPROTO]. | |||
| 4. Definitions | 5. Definitions | |||
| PIM-STD-MIB DEFINITIONS ::= BEGIN | PIM-STD-MIB DEFINITIONS ::= BEGIN | |||
| IMPORTS | IMPORTS | |||
| MODULE-IDENTITY, OBJECT-TYPE, mib-2, | MODULE-IDENTITY, OBJECT-TYPE, mib-2, | |||
| NOTIFICATION-TYPE, Unsigned32, | NOTIFICATION-TYPE, Unsigned32, | |||
| Counter32, Counter64, Gauge32, | Counter32, Counter64, Gauge32, | |||
| TimeTicks FROM SNMPv2-SMI -- [RFC2578] | TimeTicks FROM SNMPv2-SMI -- [RFC2578] | |||
| TEXTUAL-CONVENTION, | TEXTUAL-CONVENTION, | |||
| RowStatus, TruthValue, | RowStatus, TruthValue, | |||
| skipping to change at page 5, line 40 ¶ | skipping to change at page 5, line 41 ¶ | |||
| MODULE-COMPLIANCE, OBJECT-GROUP, | MODULE-COMPLIANCE, OBJECT-GROUP, | |||
| NOTIFICATION-GROUP FROM SNMPv2-CONF -- [RFC2580] | NOTIFICATION-GROUP FROM SNMPv2-CONF -- [RFC2580] | |||
| InterfaceIndexOrZero, | InterfaceIndexOrZero, | |||
| InterfaceIndex FROM IF-MIB -- [RFC2863] | InterfaceIndex FROM IF-MIB -- [RFC2863] | |||
| InetAddressType, | InetAddressType, | |||
| InetAddressPrefixLength, | InetAddressPrefixLength, | |||
| InetAddress, InetVersion FROM INET-ADDRESS-MIB -- [RFC4001] | InetAddress, InetVersion FROM INET-ADDRESS-MIB -- [RFC4001] | |||
| IANAipRouteProtocol FROM IANA-RTPROTO-MIB; -- [RTPROTO] | IANAipRouteProtocol FROM IANA-RTPROTO-MIB; -- [RTPROTO] | |||
| pimStdMIB MODULE-IDENTITY | pimStdMIB MODULE-IDENTITY | |||
| LAST-UPDATED "200612140000Z" -- 14 December 2006 | LAST-UPDATED "200703020000Z" -- 2 March 2007 | |||
| ORGANIZATION | ORGANIZATION | |||
| "IETF Protocol Independent Multicast (PIM) Working Group" | "IETF Protocol Independent Multicast (PIM) Working Group" | |||
| CONTACT-INFO | CONTACT-INFO | |||
| "Email: pim@ietf.org | "Email: pim@ietf.org | |||
| WG charter: | WG charter: | |||
| http://www.ietf.org/html.charters/pim-charter.html" | http://www.ietf.org/html.charters/pim-charter.html" | |||
| DESCRIPTION | DESCRIPTION | |||
| "The MIB module for management of PIM routers. | "The MIB module for management of PIM routers. | |||
| Copyright (C) The IETF Trust (2006). This version of this | Copyright (C) The IETF Trust (2007). This version of this | |||
| MIB module is part of RFC yyyy; see the RFC itself for full | MIB module is part of RFC yyyy; see the RFC itself for full | |||
| legal notices." | legal notices." | |||
| -- RFC Ed.: replace yyyy with actual RFC number & remove this note | -- RFC Ed.: replace yyyy with actual RFC number & remove this note | |||
| REVISION "200612140000Z" -- 14 December 2006 | REVISION "200703020000Z" -- 2 March 2007 | |||
| DESCRIPTION "Initial version, published as RFC yyyy." | DESCRIPTION "Initial version, published as RFC yyyy." | |||
| -- RFC Ed.: replace yyyy with actual RFC number & remove this note | -- RFC Ed.: replace yyyy with actual RFC number & remove this note | |||
| ::= { mib-2 XXX } | ::= { mib-2 XXX } | |||
| -- RFC Ed.: replace XXX with IANA-assigned number & remove this note | -- RFC Ed.: replace XXX with IANA-assigned number & remove this note | |||
| -- | -- | |||
| -- Textual Conventions | -- Textual Conventions | |||
| -- | -- | |||
| PimMode ::= TEXTUAL-CONVENTION | PimMode ::= TEXTUAL-CONVENTION | |||
| skipping to change at page 7, line 33 ¶ | skipping to change at page 7, line 35 ¶ | |||
| bsr(4), | bsr(4), | |||
| autoRP(5), | autoRP(5), | |||
| embedded(6), | embedded(6), | |||
| other(7) | other(7) | |||
| } | } | |||
| -- | -- | |||
| -- Top-level structure | -- Top-level structure | |||
| -- | -- | |||
| pimTraps OBJECT IDENTIFIER ::= { pimStdMIB 0 } | pimNotifications OBJECT IDENTIFIER ::= { pimStdMIB 0 } | |||
| pim OBJECT IDENTIFIER ::= { pimStdMIB 1 } | pim OBJECT IDENTIFIER ::= { pimStdMIB 1 } | |||
| pimKeepalivePeriod OBJECT-TYPE | pimKeepalivePeriod OBJECT-TYPE | |||
| SYNTAX Unsigned32 (0..65535) | SYNTAX Unsigned32 (0..65535) | |||
| UNITS "seconds" | UNITS "seconds" | |||
| MAX-ACCESS read-write | MAX-ACCESS read-write | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The duration of the Keepalive Timer. This is the period | "The duration of the Keepalive Timer. This is the period | |||
| during which the PIM router will maintain (S,G) state in the | during which the PIM router will maintain (S,G) state in the | |||
| absence of explicit (S,G) local membership or (S,G) join | absence of explicit (S,G) local membership or (S,G) join | |||
| messages received to maintain it. This timer period is | messages received to maintain it. This timer period is | |||
| called the Keepalive_Period in the PIM-SM specification. It | called the Keepalive_Period in the PIM-SM specification. It | |||
| is called the SourceLifetime in the PIM-DM specification." | is called the SourceLifetime in the PIM-DM specification. | |||
| The storage type of this object is determined by | ||||
| pimDeviceConfigStorageType." | ||||
| REFERENCE "RFC 4601 section 4.11" | REFERENCE "RFC 4601 section 4.11" | |||
| DEFVAL { 210 } | DEFVAL { 210 } | |||
| ::= { pim 14 } | ::= { pim 14 } | |||
| pimRegisterSuppressionTime OBJECT-TYPE | pimRegisterSuppressionTime OBJECT-TYPE | |||
| SYNTAX Unsigned32 (0..65535) | SYNTAX Unsigned32 (0..65535) | |||
| UNITS "seconds" | UNITS "seconds" | |||
| MAX-ACCESS read-write | MAX-ACCESS read-write | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The duration of the Register Suppression Timer. This is | "The duration of the Register Suppression Timer. This is | |||
| the period during which a PIM Designated Router (DR) stops | the period during which a PIM Designated Router (DR) stops | |||
| sending Register-encapsulated data to the Rendezvous Point | sending Register-encapsulated data to the Rendezvous Point | |||
| (RP) after receiving a Register-Stop message. This object | (RP) after receiving a Register-Stop message. This object | |||
| is used to run timers both at the DR and at the RP. This | is used to run timers both at the DR and at the RP. This | |||
| timer period is called the Register_Suppression_Time in the | timer period is called the Register_Suppression_Time in the | |||
| PIM-SM specification." | PIM-SM specification. | |||
| The storage type of this object is determined by | ||||
| pimDeviceConfigStorageType." | ||||
| REFERENCE "RFC 4601 section 4.11" | REFERENCE "RFC 4601 section 4.11" | |||
| DEFVAL { 60 } | DEFVAL { 60 } | |||
| ::= { pim 15 } | ::= { pim 15 } | |||
| pimStarGEntries OBJECT-TYPE | pimStarGEntries OBJECT-TYPE | |||
| SYNTAX Gauge32 | SYNTAX Gauge32 | |||
| MAX-ACCESS read-only | MAX-ACCESS read-only | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The number of entries in the pimStarGTable." | "The number of entries in the pimStarGTable." | |||
| skipping to change at page 9, line 26 ¶ | skipping to change at page 9, line 34 ¶ | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The number of entries in the pimSGRptITable." | "The number of entries in the pimSGRptITable." | |||
| ::= { pim 21 } | ::= { pim 21 } | |||
| pimOutAsserts OBJECT-TYPE | pimOutAsserts OBJECT-TYPE | |||
| SYNTAX Counter64 | SYNTAX Counter64 | |||
| MAX-ACCESS read-only | MAX-ACCESS read-only | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The number of Asserts sent by this router." | "The number of Asserts sent by this router. | |||
| Discontinuities in the value of this counter can occur at | ||||
| re-initialization of the management system, for example | ||||
| when the device is rebooted." | ||||
| REFERENCE "RFC 4601 section 4.6" | REFERENCE "RFC 4601 section 4.6" | |||
| ::= { pim 22 } | ::= { pim 22 } | |||
| pimInAsserts OBJECT-TYPE | pimInAsserts OBJECT-TYPE | |||
| SYNTAX Counter64 | SYNTAX Counter64 | |||
| MAX-ACCESS read-only | MAX-ACCESS read-only | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The number of Asserts received by this router. Asserts | "The number of Asserts received by this router. Asserts | |||
| are multicast to all routers on a network. This counter is | are multicast to all routers on a network. This counter is | |||
| incremented by all routers that receive an assert, not only | incremented by all routers that receive an assert, not only | |||
| those routers that are contesting the assert." | those routers that are contesting the assert. | |||
| Discontinuities in the value of this counter can occur at | ||||
| re-initialization of the management system, for example | ||||
| when the device is rebooted." | ||||
| REFERENCE "RFC 4601 section 4.6" | REFERENCE "RFC 4601 section 4.6" | |||
| ::= { pim 23 } | ::= { pim 23 } | |||
| pimLastAssertInterface OBJECT-TYPE | pimLastAssertInterface OBJECT-TYPE | |||
| SYNTAX InterfaceIndexOrZero | SYNTAX InterfaceIndexOrZero | |||
| MAX-ACCESS read-only | MAX-ACCESS read-only | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The interface on which this router most recently sent or | "The interface on which this router most recently sent or | |||
| received an assert, or zero if this router has not sent or | received an assert, or zero if this router has not sent or | |||
| skipping to change at page 10, line 48 ¶ | skipping to change at page 11, line 15 ¶ | |||
| pimLastAssertSourceAddress OBJECT-TYPE | pimLastAssertSourceAddress OBJECT-TYPE | |||
| SYNTAX InetAddress (SIZE (0|4|8|16|20)) | SYNTAX InetAddress (SIZE (0|4|8|16|20)) | |||
| MAX-ACCESS read-only | MAX-ACCESS read-only | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The multicast source address in the most recently sent or | "The multicast source address in the most recently sent or | |||
| received assert. The InetAddressType is given by the | received assert. The InetAddressType is given by the | |||
| pimLastAssertSourceAddressType object." | pimLastAssertSourceAddressType object." | |||
| ::= { pim 28 } | ::= { pim 28 } | |||
| pimNeighborLossTrapPeriod OBJECT-TYPE | pimNeighborLossNotificationPeriod OBJECT-TYPE | |||
| SYNTAX Unsigned32 (0..65535) | SYNTAX Unsigned32 (0..65535) | |||
| UNITS "seconds" | UNITS "seconds" | |||
| MAX-ACCESS read-write | MAX-ACCESS read-write | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The minimum time that must elapse between pimNeighborLoss | "The minimum time that must elapse between pimNeighborLoss | |||
| traps originated by this router. The maximum value 65535 | notifications originated by this router. The maximum value | |||
| represents an 'infinite' time, in which case no | 65535 represents an 'infinite' time, in which case no | |||
| pimNeighborLoss traps are ever sent." | pimNeighborLoss notifications are ever sent. | |||
| The storage type of this object is determined by | ||||
| pimDeviceConfigStorageType." | ||||
| DEFVAL { 0 } | DEFVAL { 0 } | |||
| ::= { pim 29 } | ::= { pim 29 } | |||
| pimNeighborLossCount OBJECT-TYPE | pimNeighborLossCount OBJECT-TYPE | |||
| SYNTAX Counter32 | SYNTAX Counter32 | |||
| MAX-ACCESS read-only | MAX-ACCESS read-only | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The number of neighbor loss events that have occurred. | "The number of neighbor loss events that have occurred. | |||
| This counter is incremented when the neighbor timer expires, | This counter is incremented when the neighbor timer expires, | |||
| and the router has no other neighbors on the same interface | and the router has no other neighbors on the same interface | |||
| with the same IP version and a lower IP address than itself. | with the same IP version and a lower IP address than itself. | |||
| This counter is incremented whenever a pimNeighborLoss trap | This counter is incremented whenever a pimNeighborLoss | |||
| would be generated." | notification would be generated. | |||
| Discontinuities in the value of this counter can occur at | ||||
| re-initialization of the management system, for example | ||||
| when the device is rebooted." | ||||
| REFERENCE "RFC 4601 section 4.3.2" | REFERENCE "RFC 4601 section 4.3.2" | |||
| ::= { pim 30 } | ::= { pim 30 } | |||
| pimInvalidRegisterTrapPeriod OBJECT-TYPE | pimInvalidRegisterNotificationPeriod OBJECT-TYPE | |||
| SYNTAX Unsigned32 (10..65535) | SYNTAX Unsigned32 (10..65535) | |||
| UNITS "seconds" | UNITS "seconds" | |||
| MAX-ACCESS read-write | MAX-ACCESS read-write | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The minimum time that must elapse between | "The minimum time that must elapse between | |||
| pimInvalidRegister traps originated by this router. The | pimInvalidRegister notifications originated by this router. | |||
| default value of 65535 represents an 'infinite' time, in | The default value of 65535 represents an 'infinite' time, in | |||
| which case no pimInvalidRegister traps are ever sent. | which case no pimInvalidRegister notifications are ever | |||
| sent. | ||||
| The non-zero minimum allowed value provides resilience | The non-zero minimum allowed value provides resilience | |||
| against propagation of denial-of-service attacks from the | against propagation of denial-of-service attacks from the | |||
| data and control planes to the network management plane." | data and control planes to the network management plane. | |||
| The storage type of this object is determined by | ||||
| pimDeviceConfigStorageType." | ||||
| DEFVAL { 65535 } | DEFVAL { 65535 } | |||
| ::= { pim 31 } | ::= { pim 31 } | |||
| pimInvalidRegisterMsgsRcvd OBJECT-TYPE | pimInvalidRegisterMsgsRcvd OBJECT-TYPE | |||
| SYNTAX Counter32 | SYNTAX Counter32 | |||
| MAX-ACCESS read-only | MAX-ACCESS read-only | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The number of invalid PIM Register messages that have been | "The number of invalid PIM Register messages that have been | |||
| received by this device. | received by this device. | |||
| skipping to change at page 12, line 27 ¶ | skipping to change at page 13, line 5 ¶ | |||
| The active Group to RP mapping on this device is specified | The active Group to RP mapping on this device is specified | |||
| by the object pimGroupMappingPimMode. If there is no such | by the object pimGroupMappingPimMode. If there is no such | |||
| mapping, then the object pimGroupMappingPimMode is absent. | mapping, then the object pimGroupMappingPimMode is absent. | |||
| The RP address contained in the invalid Register is | The RP address contained in the invalid Register is | |||
| pimInvalidRegisterRp. | pimInvalidRegisterRp. | |||
| Multicast data carried by invalid Register messages is | Multicast data carried by invalid Register messages is | |||
| discarded. The discarded data is from a source directly | discarded. The discarded data is from a source directly | |||
| connected to pimInvalidRegisterOrigin, and is addressed to | connected to pimInvalidRegisterOrigin, and is addressed to | |||
| pimInvalidRegisterGroup." | pimInvalidRegisterGroup. | |||
| Discontinuities in the value of this counter can occur at | ||||
| re-initialization of the management system, for example | ||||
| when the device is rebooted." | ||||
| REFERENCE "RFC 4601 section 4.4.2, RFC 3569 and | REFERENCE "RFC 4601 section 4.4.2, RFC 3569 and | |||
| I-D.ietf-mboned-ip-mcast-mib ipMcastSsmRangeTable" | I-D.ietf-mboned-ip-mcast-mib ipMcastSsmRangeTable" | |||
| ::= { pim 32 } | ::= { pim 32 } | |||
| pimInvalidRegisterAddressType OBJECT-TYPE | pimInvalidRegisterAddressType OBJECT-TYPE | |||
| SYNTAX InetAddressType | SYNTAX InetAddressType | |||
| MAX-ACCESS read-only | MAX-ACCESS read-only | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The address type stored in pimInvalidRegisterOrigin, | "The address type stored in pimInvalidRegisterOrigin, | |||
| skipping to change at page 13, line 23 ¶ | skipping to change at page 14, line 5 ¶ | |||
| pimInvalidRegisterRp OBJECT-TYPE | pimInvalidRegisterRp OBJECT-TYPE | |||
| SYNTAX InetAddress (SIZE (0|4|8|16|20)) | SYNTAX InetAddress (SIZE (0|4|8|16|20)) | |||
| MAX-ACCESS read-only | MAX-ACCESS read-only | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The RP address to which the last unexpected Register | "The RP address to which the last unexpected Register | |||
| message received by this device was delivered." | message received by this device was delivered." | |||
| ::= { pim 36 } | ::= { pim 36 } | |||
| pimInvalidJoinPruneTrapPeriod OBJECT-TYPE | pimInvalidJoinPruneNotificationPeriod OBJECT-TYPE | |||
| SYNTAX Unsigned32 (10..65535) | SYNTAX Unsigned32 (10..65535) | |||
| UNITS "seconds" | UNITS "seconds" | |||
| MAX-ACCESS read-write | MAX-ACCESS read-write | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The minimum time that must elapse between | "The minimum time that must elapse between | |||
| pimInvalidJoinPrune traps originated by this router. The | pimInvalidJoinPrune notifications originated by this router. | |||
| default value of 65535 represents an 'infinite' time, in | The default value of 65535 represents an 'infinite' time, in | |||
| which case no pimInvalidJoinPrune traps are ever sent. | which case no pimInvalidJoinPrune notifications are ever | |||
| sent. | ||||
| The non-zero minimum allowed value provides resilience | The non-zero minimum allowed value provides resilience | |||
| against propagation of denial-of-service attacks from the | against propagation of denial-of-service attacks from the | |||
| control plane to the network management plane." | control plane to the network management plane. | |||
| The storage type of this object is determined by | ||||
| pimDeviceConfigStorageType." | ||||
| DEFVAL { 65535 } | DEFVAL { 65535 } | |||
| ::= { pim 37 } | ::= { pim 37 } | |||
| pimInvalidJoinPruneMsgsRcvd OBJECT-TYPE | pimInvalidJoinPruneMsgsRcvd OBJECT-TYPE | |||
| SYNTAX Counter32 | SYNTAX Counter32 | |||
| MAX-ACCESS read-only | MAX-ACCESS read-only | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The number of invalid PIM Join/Prune messages that have | "The number of invalid PIM Join/Prune messages that have | |||
| been received by this device. | been received by this device. | |||
| skipping to change at page 14, line 4 ¶ | skipping to change at page 14, line 38 ¶ | |||
| MAX-ACCESS read-only | MAX-ACCESS read-only | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The number of invalid PIM Join/Prune messages that have | "The number of invalid PIM Join/Prune messages that have | |||
| been received by this device. | been received by this device. | |||
| A PIM Join/Prune message is invalid if either | A PIM Join/Prune message is invalid if either | |||
| o the Group to RP mapping specified by this message does not | o the Group to RP mapping specified by this message does not | |||
| match the Group to RP mapping on this device, or | match the Group to RP mapping on this device, or | |||
| o this device believes the group address to be within an | o this device believes the group address to be within an | |||
| SSM address range, but this Join/Prune (*,G) or (S,G,rpt) | SSM address range, but this Join/Prune (*,G) or (S,G,rpt) | |||
| implies ASM usage. | implies ASM usage. | |||
| These conditions can occur transiently while RP mapping | These conditions can occur transiently while RP mapping | |||
| changes propagate through the network. If this counter is | changes propagate through the network. If this counter is | |||
| incremented repeatedly over several minutes, then there is a | incremented repeatedly over several minutes, then there is a | |||
| persisting configuration error that requires correction. | persisting configuration error that requires correction. | |||
| The active Group to RP mapping on this device is specified | The active Group to RP mapping on this device is specified | |||
| by the object pimGroupMappingPimMode. If there is no such | by the object pimGroupMappingPimMode. If there is no such | |||
| mapping, then the object pimGroupMappingPimMode is absent. | mapping, then the object pimGroupMappingPimMode is absent. | |||
| The RP address contained in the invalid Join/Prune is | The RP address contained in the invalid Join/Prune is | |||
| pimInvalidJoinPruneRp. | pimInvalidJoinPruneRp. | |||
| Invalid Join/Prune messages are discarded. This may result | Invalid Join/Prune messages are discarded. This may result | |||
| in loss of multicast data affecting listeners downstream of | in loss of multicast data affecting listeners downstream of | |||
| pimInvalidJoinPruneOrigin, for multicast data addressed to | pimInvalidJoinPruneOrigin, for multicast data addressed to | |||
| pimInvalidJoinPruneGroup." | pimInvalidJoinPruneGroup. | |||
| Discontinuities in the value of this counter can occur at | ||||
| re-initialization of the management system, for example | ||||
| when the device is rebooted." | ||||
| REFERENCE "RFC 4601 section 4.5.2, RFC 3569 and | REFERENCE "RFC 4601 section 4.5.2, RFC 3569 and | |||
| I-D.ietf-mboned-ip-mcast-mib ipMcastSsmRangeTable" | I-D.ietf-mboned-ip-mcast-mib ipMcastSsmRangeTable" | |||
| ::= { pim 38 } | ::= { pim 38 } | |||
| pimInvalidJoinPruneAddressType OBJECT-TYPE | pimInvalidJoinPruneAddressType OBJECT-TYPE | |||
| SYNTAX InetAddressType | SYNTAX InetAddressType | |||
| MAX-ACCESS read-only | MAX-ACCESS read-only | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The address type stored in pimInvalidJoinPruneOrigin, | "The address type stored in pimInvalidJoinPruneOrigin, | |||
| skipping to change at page 15, line 18 ¶ | skipping to change at page 16, line 7 ¶ | |||
| pimInvalidJoinPruneRp OBJECT-TYPE | pimInvalidJoinPruneRp OBJECT-TYPE | |||
| SYNTAX InetAddress (SIZE (0|4|8|16|20)) | SYNTAX InetAddress (SIZE (0|4|8|16|20)) | |||
| MAX-ACCESS read-only | MAX-ACCESS read-only | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The RP address carried in the last unexpected Join/Prune | "The RP address carried in the last unexpected Join/Prune | |||
| message received by this device." | message received by this device." | |||
| ::= { pim 42 } | ::= { pim 42 } | |||
| pimRPMappingTrapPeriod OBJECT-TYPE | pimRPMappingNotificationPeriod OBJECT-TYPE | |||
| SYNTAX Unsigned32 (0..65535) | SYNTAX Unsigned32 (0..65535) | |||
| UNITS "seconds" | UNITS "seconds" | |||
| MAX-ACCESS read-write | MAX-ACCESS read-write | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The minimum time that must elapse between | "The minimum time that must elapse between | |||
| pimRPMappingChange traps originated by this router. The | pimRPMappingChange notifications originated by this router. | |||
| default value of 65535 represents an 'infinite' time, in | The default value of 65535 represents an 'infinite' time, in | |||
| which case no pimRPMappingChange traps are ever sent." | which case no pimRPMappingChange notifications are ever | |||
| sent. | ||||
| The storage type of this object is determined by | ||||
| pimDeviceConfigStorageType." | ||||
| DEFVAL { 65535 } | DEFVAL { 65535 } | |||
| ::= { pim 43 } | ::= { pim 43 } | |||
| pimRPMappingChangeCount OBJECT-TYPE | pimRPMappingChangeCount OBJECT-TYPE | |||
| SYNTAX Counter32 | SYNTAX Counter32 | |||
| MAX-ACCESS read-only | MAX-ACCESS read-only | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The number of changes to active RP mappings on this device. | "The number of changes to active RP mappings on this device. | |||
| Information about active RP mappings is available in | Information about active RP mappings is available in | |||
| pimGroupMappingTable. Only changes to active mappings cause | pimGroupMappingTable. Only changes to active mappings cause | |||
| this counter to be incremented. That is, changes that | this counter to be incremented. That is, changes that | |||
| modify the pimGroupMappingEntry with the highest precedence | modify the pimGroupMappingEntry with the highest precedence | |||
| for a group (lowest value of pimGroupMappingPrecedence). | for a group (lowest value of pimGroupMappingPrecedence). | |||
| Such changes may result from manual configuration of this | Such changes may result from manual configuration of this | |||
| device, or from automatic RP mapping discovery methods | device, or from automatic RP mapping discovery methods | |||
| including the PIM Bootstrap Router (BSR) mechanism." | including the PIM Bootstrap Router (BSR) mechanism. | |||
| Discontinuities in the value of this counter can occur at | ||||
| re-initialization of the management system, for example | ||||
| when the device is rebooted." | ||||
| REFERENCE "I-D.ietf-pim-sm-bsr" | REFERENCE "I-D.ietf-pim-sm-bsr" | |||
| ::= { pim 44 } | ::= { pim 44 } | |||
| pimInterfaceElectionTrapPeriod OBJECT-TYPE | pimInterfaceElectionNotificationPeriod OBJECT-TYPE | |||
| SYNTAX Unsigned32 (0..65535) | SYNTAX Unsigned32 (0..65535) | |||
| UNITS "seconds" | UNITS "seconds" | |||
| MAX-ACCESS read-write | MAX-ACCESS read-write | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The minimum time that must elapse between | "The minimum time that must elapse between | |||
| pimInterfaceElection traps originated by this router. The | pimInterfaceElection notifications originated by this | |||
| default value of 65535 represents an 'infinite' time, in | router. The default value of 65535 represents an 'infinite' | |||
| which case no pimInterfaceElection traps are ever sent." | time, in which case no pimInterfaceElection notifications | |||
| are ever sent. | ||||
| The storage type of this object is determined by | ||||
| pimDeviceConfigStorageType." | ||||
| DEFVAL { 65535 } | DEFVAL { 65535 } | |||
| ::= { pim 45 } | ::= { pim 45 } | |||
| pimInterfaceElectionWinCount OBJECT-TYPE | pimInterfaceElectionWinCount OBJECT-TYPE | |||
| SYNTAX Counter32 | SYNTAX Counter32 | |||
| MAX-ACCESS read-only | MAX-ACCESS read-only | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The number of times this device has been elected DR or DF | "The number of times this device has been elected DR or DF | |||
| on any interface. | on any interface. | |||
| Elections occur frequently on newly-active interfaces, as | Elections occur frequently on newly-active interfaces, as | |||
| triggered Hellos establish adjacencies. This counter is not | triggered Hellos establish adjacencies. This counter is not | |||
| incremented for elections on an interface until the first | incremented for elections on an interface until the first | |||
| periodic Hello has been sent. If this router is the DR or | periodic Hello has been sent. If this router is the DR or | |||
| DF at the time of sending the first periodic Hello after | DF at the time of sending the first periodic Hello after | |||
| interface activation, then this counter is incremented | interface activation, then this counter is incremented | |||
| (once) at that time." | (once) at that time. | |||
| Discontinuities in the value of this counter can occur at | ||||
| re-initialization of the management system, for example | ||||
| when the device is rebooted." | ||||
| REFERENCE "RFC 4601 section 4.3.2 and | REFERENCE "RFC 4601 section 4.3.2 and | |||
| I-D.ietf-pim-bidir section 3.5.2" | I-D.ietf-pim-bidir section 3.5.2" | |||
| ::= { pim 46 } | ::= { pim 46 } | |||
| pimRefreshInterval OBJECT-TYPE | pimRefreshInterval OBJECT-TYPE | |||
| SYNTAX Unsigned32 (0..65535) | SYNTAX Unsigned32 (0..65535) | |||
| UNITS "seconds" | UNITS "seconds" | |||
| MAX-ACCESS read-write | MAX-ACCESS read-write | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The interval between successive State Refresh messages sent | "The interval between successive State Refresh messages sent | |||
| by an Originator. This timer period is called the | by an Originator. This timer period is called the | |||
| RefreshInterval in the PIM-DM specification. This object is | RefreshInterval in the PIM-DM specification. This object is | |||
| used only by PIM-DM." | used only by PIM-DM. | |||
| The storage type of this object is determined by | ||||
| pimDeviceConfigStorageType." | ||||
| REFERENCE "RFC 3973 section 4.8" | REFERENCE "RFC 3973 section 4.8" | |||
| DEFVAL { 60 } | DEFVAL { 60 } | |||
| ::= { pim 47 } | ::= { pim 47 } | |||
| pimDeviceConfigStorageType OBJECT-TYPE | pimDeviceConfigStorageType OBJECT-TYPE | |||
| SYNTAX StorageType | SYNTAX StorageType | |||
| MAX-ACCESS read-write | MAX-ACCESS read-write | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The storage type used for the global PIM configuration of | "The storage type used for the global PIM configuration of | |||
| this device, comprised of the objects listed below. If this | this device, comprised of the objects listed below. If this | |||
| storage type takes the value 'permanent', write-access to | storage type takes the value 'permanent', write-access to | |||
| the listed objects need not be allowed. | the listed objects need not be allowed. | |||
| The objects described by this storage type are: | The objects described by this storage type are: | |||
| pimKeepalivePeriod, pimRegisterSuppressionTime, | pimKeepalivePeriod, pimRegisterSuppressionTime, | |||
| pimNeighborLossTrapPeriod, pimInvalidRegisterTrapPeriod, | pimNeighborLossNotificationPeriod, | |||
| pimInvalidJoinPruneTrapPeriod, pimRPMappingTrapPeriod, | pimInvalidRegisterNotificationPeriod, | |||
| pimInterfaceElectionTrapPeriod and pimRefreshInterval." | pimInvalidJoinPruneNotificationPeriod, | |||
| pimRPMappingNotificationPeriod, | ||||
| pimInterfaceElectionNotificationPeriod and | ||||
| pimRefreshInterval." | ||||
| DEFVAL { nonVolatile } | DEFVAL { nonVolatile } | |||
| ::= { pim 48 } | ::= { pim 48 } | |||
| -- | -- | |||
| -- The PIM Interface Table | -- The PIM Interface Table | |||
| -- | -- | |||
| pimInterfaceTable OBJECT-TYPE | pimInterfaceTable OBJECT-TYPE | |||
| SYNTAX SEQUENCE OF PimInterfaceEntry | SYNTAX SEQUENCE OF PimInterfaceEntry | |||
| MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
| STATUS current | STATUS current | |||
| skipping to change at page 26, line 4 ¶ | skipping to change at page 27, line 15 ¶ | |||
| All writeable objects in this entry can be modified when the | All writeable objects in this entry can be modified when the | |||
| status of this entry is active(1)." | status of this entry is active(1)." | |||
| ::= { pimInterfaceEntry 27 } | ::= { pimInterfaceEntry 27 } | |||
| pimInterfaceStorageType OBJECT-TYPE | pimInterfaceStorageType OBJECT-TYPE | |||
| SYNTAX StorageType | SYNTAX StorageType | |||
| MAX-ACCESS read-create | MAX-ACCESS read-create | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The storage type for this row. Rows having the value | "The storage type for this row. Rows having the value | |||
| 'permanent' need not allow write-access to any columnar | 'permanent' need not allow write-access to any columnar | |||
| objects in the row." | objects in the row." | |||
| DEFVAL { nonVolatile } | DEFVAL { nonVolatile } | |||
| ::= { pimInterfaceEntry 28 } | ::= { pimInterfaceEntry 28 } | |||
| -- | -- | |||
| -- The PIM Neighbor Table | -- The PIM Neighbor Table | |||
| -- | -- | |||
| pimNeighborTable OBJECT-TYPE | pimNeighborTable OBJECT-TYPE | |||
| SYNTAX SEQUENCE OF PimNeighborEntry | SYNTAX SEQUENCE OF PimNeighborEntry | |||
| MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
| skipping to change at page 62, line 25 ¶ | skipping to change at page 63, line 35 ¶ | |||
| All writeable objects in this entry can be modified when the | All writeable objects in this entry can be modified when the | |||
| status of this entry is active(1)." | status of this entry is active(1)." | |||
| ::= { pimStaticRPEntry 8 } | ::= { pimStaticRPEntry 8 } | |||
| pimStaticRPStorageType OBJECT-TYPE | pimStaticRPStorageType OBJECT-TYPE | |||
| SYNTAX StorageType | SYNTAX StorageType | |||
| MAX-ACCESS read-create | MAX-ACCESS read-create | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The storage type for this row. Rows having the value | "The storage type for this row. Rows having the value | |||
| 'permanent' need not allow write-access to any columnar | 'permanent' need not allow write-access to any columnar | |||
| objects in the row." | objects in the row." | |||
| DEFVAL { nonVolatile } | DEFVAL { nonVolatile } | |||
| ::= { pimStaticRPEntry 9 } | ::= { pimStaticRPEntry 9 } | |||
| -- | -- | |||
| -- The PIM Anycast-RP Set Table | -- The PIM Anycast-RP Set Table | |||
| -- | -- | |||
| pimAnycastRPSetTable OBJECT-TYPE | pimAnycastRPSetTable OBJECT-TYPE | |||
| SYNTAX SEQUENCE OF PimAnycastRPSetEntry | SYNTAX SEQUENCE OF PimAnycastRPSetEntry | |||
| MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
| skipping to change at page 64, line 50 ¶ | skipping to change at page 66, line 14 ¶ | |||
| All writeable objects in this entry can be modified when the | All writeable objects in this entry can be modified when the | |||
| status of this entry is active(1)." | status of this entry is active(1)." | |||
| ::= { pimAnycastRPSetEntry 5 } | ::= { pimAnycastRPSetEntry 5 } | |||
| pimAnycastRPSetStorageType OBJECT-TYPE | pimAnycastRPSetStorageType OBJECT-TYPE | |||
| SYNTAX StorageType | SYNTAX StorageType | |||
| MAX-ACCESS read-create | MAX-ACCESS read-create | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "The storage type for this row. Rows having the value | "The storage type for this row. Rows having the value | |||
| 'permanent' need not allow write-access to any columnar | 'permanent' need not allow write-access to any columnar | |||
| objects in the row." | objects in the row." | |||
| DEFVAL { nonVolatile } | DEFVAL { nonVolatile } | |||
| ::= { pimAnycastRPSetEntry 6 } | ::= { pimAnycastRPSetEntry 6 } | |||
| -- | -- | |||
| -- The PIM Group Mapping Table | -- The PIM Group Mapping Table | |||
| -- | -- | |||
| pimGroupMappingTable OBJECT-TYPE | pimGroupMappingTable OBJECT-TYPE | |||
| SYNTAX SEQUENCE OF PimGroupMappingEntry | SYNTAX SEQUENCE OF PimGroupMappingEntry | |||
| MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
| skipping to change at page 66, line 18 ¶ | skipping to change at page 67, line 29 ¶ | |||
| Given the collection of rows in this table at any point in | Given the collection of rows in this table at any point in | |||
| time, the PIM mode and RP address to use for a particular | time, the PIM mode and RP address to use for a particular | |||
| group is determined using the following algorithm. | group is determined using the following algorithm. | |||
| 1. From the set of all rows, the subset whose group prefix | 1. From the set of all rows, the subset whose group prefix | |||
| contains the group in question are selected. | contains the group in question are selected. | |||
| 2. If there are no such rows, the behavior is undefined. | 2. If there are no such rows, the behavior is undefined. | |||
| 3. If there is at least one such row, from the selected | 3. From the selected subset of rows, the subset that have | |||
| subset of rows, the subset that have the lowest value | ||||
| of pimGroupMappingPrecedence are selected. | ||||
| 4. From the selected subset of rows, the subset that have | ||||
| the greatest value of pimGroupMappingGrpPrefixLength are | the greatest value of pimGroupMappingGrpPrefixLength are | |||
| selected. | selected. | |||
| 5. If there are multiple selected rows, the subset that have | 4. If there are multiple selected rows, and a subset are | |||
| the highest precedence (the lowest numerical value for | defined by pimStaticRPTable (pimGroupMappingOrigin value | |||
| pimGroupMappingPrecedence) are selected. | of 'configRp') with pimStaticRPOverrideDynamic set to | |||
| TRUE, then this subset is selected. | ||||
| 6. If there are multiple selected rows, the row selected is | 5. If there are still multiple selected rows, the subset | |||
| implementation dependent; the implementation might or | that have the highest precedence (the lowest numerical | |||
| might not apply the PIM hash function to select the row. | value for pimGroupMappingPrecedence) are selected. | |||
| 6. If there are still multiple selected rows, the row | ||||
| selected is implementation dependent; the implementation | ||||
| might or might not apply the PIM hash function to select | ||||
| the row. | ||||
| 7. The group mode to use is given by the value of | 7. The group mode to use is given by the value of | |||
| pimGroupMappingPimMode from the single selected row; the | pimGroupMappingPimMode from the single selected row; the | |||
| RP to use is given by the value of | RP to use is given by the value of | |||
| pimGroupMappingRPAddress, unless pimGroupMappingOrigin is | pimGroupMappingRPAddress, unless pimGroupMappingOrigin is | |||
| 'embedded', in which case the RP is extracted from the | 'embedded', in which case the RP is extracted from the | |||
| group address in question." | group address in question." | |||
| REFERENCE "RFC 4601 section 3.7, RFC 3956 and RFC 4610" | REFERENCE "RFC 4601 section 3.7, RFC 3956 and RFC 4610" | |||
| ::= { pim 13 } | ::= { pim 13 } | |||
| pimGroupMappingEntry OBJECT-TYPE | pimGroupMappingEntry OBJECT-TYPE | |||
| SYNTAX PimGroupMappingEntry | SYNTAX PimGroupMappingEntry | |||
| MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "An entry (conceptual row) in the pimGroupMappingTable." | "An entry (conceptual row) in the pimGroupMappingTable." | |||
| INDEX { pimGroupMappingOrigin, | INDEX { pimGroupMappingOrigin, | |||
| skipping to change at page 69, line 18 ¶ | skipping to change at page 70, line 32 ¶ | |||
| (described above). Numerically higher values for this | (described above). Numerically higher values for this | |||
| object indicate lower precedences, with the value zero | object indicate lower precedences, with the value zero | |||
| denoting the highest precedence. | denoting the highest precedence. | |||
| The absolute values of this object have a significance only | The absolute values of this object have a significance only | |||
| on the local router and do not need to be coordinated with | on the local router and do not need to be coordinated with | |||
| other routers." | other routers." | |||
| ::= { pimGroupMappingEntry 8 } | ::= { pimGroupMappingEntry 8 } | |||
| -- | -- | |||
| -- PIM Notifications | ||||
| -- | -- | |||
| pimNeighborLoss NOTIFICATION-TYPE | pimNeighborLoss NOTIFICATION-TYPE | |||
| OBJECTS { pimNeighborUpTime } | OBJECTS { pimNeighborUpTime } | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "A pimNeighborLoss trap signifies the loss of an adjacency | "A pimNeighborLoss notification signifies the loss of an | |||
| with a neighbor. This trap should be generated when the | adjacency with a neighbor. This notification should be | |||
| neighbor timer expires, and the router has no other | generated when the neighbor timer expires, and the router | |||
| neighbors on the same interface with the same IP version and | has no other neighbors on the same interface with the same | |||
| a lower IP address than itself. | IP version and a lower IP address than itself. | |||
| This notification is generated whenever the counter | This notification is generated whenever the counter | |||
| pimNeighborLossCount is incremented, subject | pimNeighborLossCount is incremented, subject | |||
| to the rate limit specified by pimNeighborLossTrapPeriod." | to the rate limit specified by | |||
| pimNeighborLossNotificationPeriod." | ||||
| REFERENCE "RFC 4601 section 4.3.2" | REFERENCE "RFC 4601 section 4.3.2" | |||
| ::= { pimTraps 1 } | ::= { pimNotifications 1 } | |||
| pimInvalidRegister NOTIFICATION-TYPE | pimInvalidRegister NOTIFICATION-TYPE | |||
| OBJECTS { pimGroupMappingPimMode, | OBJECTS { pimGroupMappingPimMode, | |||
| pimInvalidRegisterAddressType, | pimInvalidRegisterAddressType, | |||
| pimInvalidRegisterOrigin, | pimInvalidRegisterOrigin, | |||
| pimInvalidRegisterGroup, | pimInvalidRegisterGroup, | |||
| pimInvalidRegisterRp | pimInvalidRegisterRp | |||
| } | } | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "A pimInvalidRegister trap signifies that an invalid PIM | "A pimInvalidRegister notification signifies that an invalid | |||
| Register message was received by this device. | PIM Register message was received by this device. | |||
| This notification is generated whenever the counter | This notification is generated whenever the counter | |||
| pimInvalidRegisterMsgsRcvd is incremented, subject to the | pimInvalidRegisterMsgsRcvd is incremented, subject to the | |||
| rate limit specified by pimInvalidRegisterTrapPeriod." | rate limit specified by | |||
| pimInvalidRegisterNotificationPeriod." | ||||
| REFERENCE "RFC 4601 section 4.4.2" | REFERENCE "RFC 4601 section 4.4.2" | |||
| ::= { pimTraps 2 } | ::= { pimNotifications 2 } | |||
| pimInvalidJoinPrune NOTIFICATION-TYPE | pimInvalidJoinPrune NOTIFICATION-TYPE | |||
| OBJECTS { pimGroupMappingPimMode, | OBJECTS { pimGroupMappingPimMode, | |||
| pimInvalidJoinPruneAddressType, | pimInvalidJoinPruneAddressType, | |||
| pimInvalidJoinPruneOrigin, | pimInvalidJoinPruneOrigin, | |||
| pimInvalidJoinPruneGroup, | pimInvalidJoinPruneGroup, | |||
| pimInvalidJoinPruneRp, | pimInvalidJoinPruneRp, | |||
| pimNeighborUpTime | pimNeighborUpTime | |||
| } | } | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "A pimInvalidJoinPrune trap signifies that an invalid PIM | "A pimInvalidJoinPrune notification signifies that an | |||
| Join/Prune message was received by this device. | invalid PIM Join/Prune message was received by this device. | |||
| This notification is generated whenever the counter | This notification is generated whenever the counter | |||
| pimInvalidJoinPruneMsgsRcvd is incremented, subject to the | pimInvalidJoinPruneMsgsRcvd is incremented, subject to the | |||
| rate limit specified by pimInvalidJoinPruneTrapPeriod." | rate limit specified by | |||
| pimInvalidJoinPruneNotificationPeriod." | ||||
| REFERENCE "RFC 4601 section 4.5.2" | REFERENCE "RFC 4601 section 4.5.2" | |||
| ::= { pimTraps 3 } | ::= { pimNotifications 3 } | |||
| pimRPMappingChange NOTIFICATION-TYPE | pimRPMappingChange NOTIFICATION-TYPE | |||
| OBJECTS { pimGroupMappingPimMode, | OBJECTS { pimGroupMappingPimMode, | |||
| pimGroupMappingPrecedence | pimGroupMappingPrecedence | |||
| } | } | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "A pimRPMappingChange trap signifies a change to the active | "A pimRPMappingChange notification signifies a change to the | |||
| RP mapping on this device. | active RP mapping on this device. | |||
| This notification is generated whenever the counter | This notification is generated whenever the counter | |||
| pimRPMappingChangeCount is incremented, subject to the | pimRPMappingChangeCount is incremented, subject to the | |||
| rate limit specified by pimRPMappingChangeTrapPeriod." | rate limit specified by | |||
| ::= { pimTraps 4 } | pimRPMappingChangeNotificationPeriod." | |||
| ::= { pimNotifications 4 } | ||||
| pimInterfaceElection NOTIFICATION-TYPE | pimInterfaceElection NOTIFICATION-TYPE | |||
| OBJECTS { pimInterfaceAddressType, | OBJECTS { pimInterfaceAddressType, | |||
| pimInterfaceAddress } | pimInterfaceAddress } | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "A pimInterfaceElection trap signifies that a new DR or DF | "A pimInterfaceElection notification signifies that a new DR | |||
| has been elected on a network. | or DF has been elected on a network. | |||
| This notification is generated whenever the counter | This notification is generated whenever the counter | |||
| pimInterfaceElectionWinCount is incremented, subject to the | pimInterfaceElectionWinCount is incremented, subject to the | |||
| rate limit specified by pimInterfaceElectionTrapPeriod." | rate limit specified by | |||
| pimInterfaceElectionNotificationPeriod." | ||||
| REFERENCE "RFC 4601 section 4.3.2 and | REFERENCE "RFC 4601 section 4.3.2 and | |||
| I-D.ietf-pim-bidir section 3.5.2" | I-D.ietf-pim-bidir section 3.5.2" | |||
| ::= { pimTraps 5 } | ::= { pimNotifications 5 } | |||
| -- | -- | |||
| -- Conformance Information | -- Conformance Information | |||
| -- | -- | |||
| pimMIBConformance OBJECT IDENTIFIER ::= { pimStdMIB 2 } | pimMIBConformance OBJECT IDENTIFIER ::= { pimStdMIB 2 } | |||
| pimMIBCompliances OBJECT IDENTIFIER ::= { pimMIBConformance 1 } | pimMIBCompliances OBJECT IDENTIFIER ::= { pimMIBConformance 1 } | |||
| pimMIBGroups OBJECT IDENTIFIER ::= { pimMIBConformance 2 } | pimMIBGroups OBJECT IDENTIFIER ::= { pimMIBConformance 2 } | |||
| -- | -- | |||
| skipping to change at page 79, line 31 ¶ | skipping to change at page 81, line 4 ¶ | |||
| pimStaticRPPrecedenceGroup OBJECT-GROUP | pimStaticRPPrecedenceGroup OBJECT-GROUP | |||
| OBJECTS { pimStaticRPPrecedence } | OBJECTS { pimStaticRPPrecedence } | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "A collection of objects to allow fine control of | "A collection of objects to allow fine control of | |||
| interactions between static RP configuration and | interactions between static RP configuration and | |||
| dynamically acquired group to RP mappings." | dynamically acquired group to RP mappings." | |||
| ::= { pimMIBGroups 10 } | ::= { pimMIBGroups 10 } | |||
| pimNetMgmtNotificationObjects OBJECT-GROUP | pimNetMgmtNotificationObjects OBJECT-GROUP | |||
| OBJECTS { pimInvalidRegisterTrapPeriod, | OBJECTS { pimInvalidRegisterNotificationPeriod, | |||
| pimInvalidRegisterMsgsRcvd, | pimInvalidRegisterMsgsRcvd, | |||
| pimInvalidRegisterAddressType, | pimInvalidRegisterAddressType, | |||
| pimInvalidRegisterOrigin, | pimInvalidRegisterOrigin, | |||
| pimInvalidRegisterGroup, | pimInvalidRegisterGroup, | |||
| pimInvalidRegisterRp, | pimInvalidRegisterRp, | |||
| pimInvalidJoinPruneTrapPeriod, | pimInvalidJoinPruneNotificationPeriod, | |||
| pimInvalidJoinPruneMsgsRcvd, | pimInvalidJoinPruneMsgsRcvd, | |||
| pimInvalidJoinPruneAddressType, | pimInvalidJoinPruneAddressType, | |||
| pimInvalidJoinPruneOrigin, | pimInvalidJoinPruneOrigin, | |||
| pimInvalidJoinPruneGroup, | pimInvalidJoinPruneGroup, | |||
| pimInvalidJoinPruneRp, | pimInvalidJoinPruneRp, | |||
| pimRPMappingTrapPeriod, | pimRPMappingNotificationPeriod, | |||
| pimRPMappingChangeCount, | pimRPMappingChangeCount, | |||
| pimInterfaceElectionTrapPeriod, | pimInterfaceElectionNotificationPeriod, | |||
| pimInterfaceElectionWinCount | pimInterfaceElectionWinCount | |||
| } | } | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "A collection of objects to support notification of PIM | "A collection of objects to support notification of PIM | |||
| network management events." | network management events." | |||
| ::= { pimMIBGroups 11 } | ::= { pimMIBGroups 11 } | |||
| pimNetMgmtNotificationGroup NOTIFICATION-GROUP | pimNetMgmtNotificationGroup NOTIFICATION-GROUP | |||
| NOTIFICATIONS { pimInvalidRegister, | NOTIFICATIONS { pimInvalidRegister, | |||
| pimInvalidJoinPrune, | pimInvalidJoinPrune, | |||
| pimRPMappingChange, | pimRPMappingChange, | |||
| pimInterfaceElection | pimInterfaceElection | |||
| } | } | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| skipping to change at page 80, line 27 ¶ | skipping to change at page 81, line 47 ¶ | |||
| ::= { pimMIBGroups 12 } | ::= { pimMIBGroups 12 } | |||
| pimDiagnosticsGroup OBJECT-GROUP | pimDiagnosticsGroup OBJECT-GROUP | |||
| OBJECTS { pimInAsserts, | OBJECTS { pimInAsserts, | |||
| pimOutAsserts, | pimOutAsserts, | |||
| pimLastAssertInterface, | pimLastAssertInterface, | |||
| pimLastAssertGroupAddressType, | pimLastAssertGroupAddressType, | |||
| pimLastAssertGroupAddress, | pimLastAssertGroupAddress, | |||
| pimLastAssertSourceAddressType, | pimLastAssertSourceAddressType, | |||
| pimLastAssertSourceAddress, | pimLastAssertSourceAddress, | |||
| pimNeighborLossTrapPeriod, | pimNeighborLossNotificationPeriod, | |||
| pimNeighborLossCount | pimNeighborLossCount | |||
| } | } | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "Objects providing additional diagnostics related to a PIM | "Objects providing additional diagnostics related to a PIM | |||
| router." | router." | |||
| ::= { pimMIBGroups 13 } | ::= { pimMIBGroups 13 } | |||
| pimDmGroup OBJECT-GROUP | pimDmGroup OBJECT-GROUP | |||
| OBJECTS { | OBJECTS { | |||
| skipping to change at page 81, line 19 ¶ | skipping to change at page 82, line 40 ¶ | |||
| OBJECTS { pimDeviceConfigStorageType | OBJECTS { pimDeviceConfigStorageType | |||
| } | } | |||
| STATUS current | STATUS current | |||
| DESCRIPTION | DESCRIPTION | |||
| "An object that specifies the volatility of global PIM | "An object that specifies the volatility of global PIM | |||
| configuration settings on this device." | configuration settings on this device." | |||
| ::= { pimMIBGroups 15 } | ::= { pimMIBGroups 15 } | |||
| END | END | |||
| 5. Security Considerations | 6. Security Considerations | |||
| There are a number of management objects defined in this MIB module | There are a number of management objects defined in this MIB module | |||
| with a MAX-ACCESS clause of read-write and/or read-create. Such | with a MAX-ACCESS clause of read-write and/or read-create. Such | |||
| objects may be considered sensitive or vulnerable in some network | objects may be considered sensitive or vulnerable in some network | |||
| environments. The support for SET operations in a non-secure | environments. The support for SET operations in a non-secure | |||
| environment without proper protection can have a negative effect on | environment without proper protection can have a negative effect on | |||
| network operations. These are the tables and objects and their | network operations. These are the tables and objects and their | |||
| sensitivity/vulnerability: | sensitivity/vulnerability: | |||
| The following tables and objects could be employed to modify | The following tables and objects could be employed to modify | |||
| multicast routing behavior in a way that prevents, disrupts, or | multicast routing behavior in a way that prevents, disrupts, or | |||
| subverts services provided by the network, including (but not limited | subverts services provided by the network, including (but not limited | |||
| to) multicast data traffic delivery. For example, attacks can be | to) multicast data traffic delivery. For example, attacks can be | |||
| envisaged that would pass nominated multicast data streams through a | envisaged that would pass nominated multicast data streams through a | |||
| nominated location, without the sources or listeners becoming aware | nominated location, without the sources or listeners becoming aware | |||
| of this subversion. | of this subversion. | |||
| pimKeepalivePeriod | pimKeepalivePeriod | |||
| pimRegisterSuppressionTime | pimRegisterSuppressionTime | |||
| pimNeighborLossTrapPeriod | pimNeighborLossNotificationPeriod | |||
| pimInvalidRegisterTrapPeriod | pimInvalidRegisterNotificationPeriod | |||
| pimInvalidJoinPruneTrapPeriod | pimInvalidJoinPruneNotificationPeriod | |||
| pimRPMappingTrapPeriod | pimRPMappingNotificationPeriod | |||
| pimInterfaceElectionTrapPeriod | pimInterfaceElectionNotificationPeriod | |||
| pimRefreshInterval | pimRefreshInterval | |||
| pimInterfaceTable | pimInterfaceTable | |||
| pimInterfaceEntry | pimInterfaceEntry | |||
| pimInterfaceIfIndex | pimInterfaceIfIndex | |||
| pimInterfaceIPVersion | pimInterfaceIPVersion | |||
| pimInterfaceHelloInterval | pimInterfaceHelloInterval | |||
| pimInterfaceTrigHelloInterval | pimInterfaceTrigHelloInterval | |||
| pimInterfaceJoinPruneInterval | pimInterfaceJoinPruneInterval | |||
| pimInterfaceDFElectionRobustness | pimInterfaceDFElectionRobustness | |||
| pimInterfaceHelloHoldtime | pimInterfaceHelloHoldtime | |||
| skipping to change at page 83, line 20 ¶ | skipping to change at page 84, line 41 ¶ | |||
| pimSGIEntries | pimSGIEntries | |||
| pimSGRptEntries | pimSGRptEntries | |||
| pimSGRptIEntries | pimSGRptIEntries | |||
| pimOutAsserts | pimOutAsserts | |||
| pimInAsserts | pimInAsserts | |||
| pimLastAssertInterface | pimLastAssertInterface | |||
| pimLastAssertGroupAddressType | pimLastAssertGroupAddressType | |||
| pimLastAssertGroupAddress | pimLastAssertGroupAddress | |||
| pimLastAssertSourceAddressType | pimLastAssertSourceAddressType | |||
| pimLastAssertSourceAddress | pimLastAssertSourceAddress | |||
| pimNeighborLossTrapPeriod | pimNeighborLossNotificationPeriod | |||
| pimNeighborLossCount | pimNeighborLossCount | |||
| pimInvalidRegisterTrapPeriod | pimInvalidRegisterNotificationPeriod | |||
| pimInvalidRegisterMsgsRcvd | pimInvalidRegisterMsgsRcvd | |||
| pimInvalidRegisterAddressType | pimInvalidRegisterAddressType | |||
| pimInvalidRegisterOrigin | pimInvalidRegisterOrigin | |||
| pimInvalidRegisterGroup | pimInvalidRegisterGroup | |||
| pimInvalidRegisterRp | pimInvalidRegisterRp | |||
| pimInvalidJoinPruneTrapPeriod | pimInvalidJoinPruneNotificationPeriod | |||
| pimInvalidJoinPruneMsgsRcvd | pimInvalidJoinPruneMsgsRcvd | |||
| pimInvalidJoinPruneAddressType | pimInvalidJoinPruneAddressType | |||
| pimInvalidJoinPruneOrigin | pimInvalidJoinPruneOrigin | |||
| pimInvalidJoinPruneGroup | pimInvalidJoinPruneGroup | |||
| pimInvalidJoinPruneRp | pimInvalidJoinPruneRp | |||
| pimRPMappingTrapPeriod | pimRPMappingNotificationPeriod | |||
| pimRPMappingChangeCount | pimRPMappingChangeCount | |||
| pimInterfaceElectionTrapPeriod | pimInterfaceElectionNotificationPeriod | |||
| pimInterfaceElectionWinCount | pimInterfaceElectionWinCount | |||
| pimRefreshInterval | pimRefreshInterval | |||
| pimInterfaceTable | pimInterfaceTable | |||
| pimInterfaceEntry | pimInterfaceEntry | |||
| pimInterfaceIfIndex | pimInterfaceIfIndex | |||
| pimInterfaceIPVersion | pimInterfaceIPVersion | |||
| pimInterfaceAddressType | pimInterfaceAddressType | |||
| pimInterfaceAddress | pimInterfaceAddress | |||
| pimInterfaceDR | pimInterfaceDR | |||
| pimInterfaceHelloInterval | pimInterfaceHelloInterval | |||
| skipping to change at page 87, line 37 ¶ | skipping to change at page 89, line 11 ¶ | |||
| pimGroupMappingPrecedence | pimGroupMappingPrecedence | |||
| There is also a specific danger arising from the notification | There is also a specific danger arising from the notification | |||
| pimInvalidRegister. This is originated by devices that receive an | pimInvalidRegister. This is originated by devices that receive an | |||
| incorrect unicast-encapsulated multicast data packet, which poses a | incorrect unicast-encapsulated multicast data packet, which poses a | |||
| clear danger of propagating a DoS (Denial of Service) attack from the | clear danger of propagating a DoS (Denial of Service) attack from the | |||
| data or control plane to the network management plane. The following | data or control plane to the network management plane. The following | |||
| steps are taken to guard against this. | steps are taken to guard against this. | |||
| 1. The notification is disabled by default. The writeable field | 1. The notification is disabled by default. The writeable field | |||
| pimInvalidRegisterTrapPeriod must be set in order to enable it. | pimInvalidRegisterNotificationPeriod must be set in order to | |||
| enable it. | ||||
| 2. The syntax of pimInvalidRegisterTrapPeriod prevents any given | 2. The syntax of pimInvalidRegisterNotificationPeriod prevents any | |||
| device from originating the notification more frequently than | given device from originating the notification more frequently | |||
| once every 10 seconds. | than once every 10 seconds. | |||
| 3. The counter pimInvalidRegisterMsgsRcvd provides equivalent | 3. The counter pimInvalidRegisterMsgsRcvd provides equivalent | |||
| function to the notification. Management applications are | function to the notification. Management applications are | |||
| encouraged to monitor this counter in preference to enabling the | encouraged to monitor this counter in preference to enabling the | |||
| notification. | notification. | |||
| The same measures are taken in respect of pimInvalidJoinPrune, though | The same measures are taken in respect of pimInvalidJoinPrune, though | |||
| as this notification can only arise as a result of non-routable | as this notification can only arise as a result of non-routable | |||
| control packets, the risk is not so acute. | control packets, the risk is not so acute. | |||
| skipping to change at page 88, line 24 ¶ | skipping to change at page 89, line 46 ¶ | |||
| authentication and privacy). | authentication and privacy). | |||
| Further, deployment of SNMP versions prior to SNMPv3 is NOT | Further, deployment of SNMP versions prior to SNMPv3 is NOT | |||
| RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to | RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to | |||
| enable cryptographic security. It is then a customer/operator | enable cryptographic security. It is then a customer/operator | |||
| responsibility to ensure that the SNMP entity giving access to an | responsibility to ensure that the SNMP entity giving access to an | |||
| instance of this MIB module is properly configured to give access to | instance of this MIB module is properly configured to give access to | |||
| the objects only to those principals (users) that have legitimate | the objects only to those principals (users) that have legitimate | |||
| rights to indeed GET or SET (change/create/delete) them. | rights to indeed GET or SET (change/create/delete) them. | |||
| 6. IANA Considerations | 7. IANA Considerations | |||
| The MIB module in this document uses the following IANA-assigned | The MIB module in this document uses the following IANA-assigned | |||
| OBJECT IDENTIFIER values recorded in the SMI Numbers registry: | OBJECT IDENTIFIER values recorded in the SMI Numbers registry: | |||
| Descriptor OBJECT IDENTIFIER value | Descriptor OBJECT IDENTIFIER value | |||
| ---------- ----------------------- | ---------- ----------------------- | |||
| pimStdMIB { mib-2 XXX } | pimStdMIB { mib-2 XXX } | |||
| Editor's Note (to be removed prior to publication): the IANA is | Editor's Note (to be removed prior to publication): the IANA is | |||
| requested to assign a value for "XXX" under the 'mib-2' subtree and | requested to assign a value for "XXX" under the 'mib-2' subtree and | |||
| to record the assignment in the SMI Numbers registry. When the | to record the assignment in the SMI Numbers registry. When the | |||
| assignment has been made, the RFC Editor is asked to replace "XXX" | assignment has been made, the RFC Editor is asked to replace "XXX" | |||
| (here and in the MIB module) with the assigned value and to remove | (here and in the MIB module) with the assigned value and to remove | |||
| this note. | this note. | |||
| 7. Acknowledgements | 8. Acknowledgements | |||
| This MIB module is based on the original work in RFC 2934 [RFC2934] | This MIB module is based on the original work in RFC 2934 [RFC2934] | |||
| by K. McCloghrie, D. Farinacci, D. Thaler and W. Fenner and has been | by K. McCloghrie, D. Farinacci, D. Thaler and W. Fenner and has been | |||
| updated based on feedback from the IETF's Protocol Independent | updated based on feedback from the IETF's Protocol Independent | |||
| Multicast (PIM) Working Group. | Multicast (PIM) Working Group. | |||
| Jonathan Nicholas was the editor of early versions of this document, | Jonathan Nicholas was the editor of early versions of this document, | |||
| and contributed the objects for management of PIM-DM. | and contributed the objects for management of PIM-DM. | |||
| Andrew Kessler should be credited with the good work done on revising | Andrew Kessler should be credited with the good work done on revising | |||
| traps, and much reviewing besides. | notifications, and much reviewing besides. | |||
| 8. References | 9. References | |||
| 8.1 Normative References | 9.1 Normative References | |||
| [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate | |||
| Requirement Levels", BCP 14, RFC 2119, March 1997. | Requirement Levels", BCP 14, RFC 2119, March 1997. | |||
| [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. | [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. | |||
| Schoenwaelder, Ed., "Structure of Management Information | Schoenwaelder, Ed., "Structure of Management Information | |||
| Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. | Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. | |||
| [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. | [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. | |||
| Schoenwaelder, Ed., "Textual Conventions for SMIv2", | Schoenwaelder, Ed., "Textual Conventions for SMIv2", | |||
| skipping to change at page 89, line 49 ¶ | skipping to change at page 91, line 25 ¶ | |||
| [RFC4610] Farinacci, D. and Y. Cai, "Anycast-RP Using Protocol | [RFC4610] Farinacci, D. and Y. Cai, "Anycast-RP Using Protocol | |||
| Independent Multicast (PIM)", RFC 4610, August 2006. | Independent Multicast (PIM)", RFC 4610, August 2006. | |||
| [RTPROTO] IANA, "IP Route Protocol MIB", | [RTPROTO] IANA, "IP Route Protocol MIB", | |||
| http://www.iana.org/assignments/ianaiprouteprotocol-mib, | http://www.iana.org/assignments/ianaiprouteprotocol-mib, | |||
| September 2000. | September 2000. | |||
| [I-D.ietf-pim-bidir] | [I-D.ietf-pim-bidir] | |||
| Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano, | Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano, | |||
| "Bi-directional Protocol Independent Multicast (BIDIR- | "Bi-directional Protocol Independent Multicast (BIDIR- | |||
| PIM)", draft-ietf-pim-bidir-08 (work in progress), | PIM)", draft-ietf-pim-bidir-09 (work in progress), | |||
| October 2005. | February 2007. | |||
| [I-D.ietf-pim-sm-bsr] | [I-D.ietf-pim-sm-bsr] | |||
| Bhaskar, N., "Bootstrap Router (BSR) Mechanism for PIM", | Bhaskar, N., "Bootstrap Router (BSR) Mechanism for PIM", | |||
| draft-ietf-pim-sm-bsr-08 (work in progress), June 2006. | draft-ietf-pim-sm-bsr-10 (work in progress), | |||
| February 2007. | ||||
| [I-D.ietf-mboned-ip-mcast-mib] | ||||
| McWalter, D., "IP Multicast MIB", | ||||
| draft-ietf-mboned-ip-mcast-mib-04 (work in progress), | ||||
| November 2006. | ||||
| 8.2 Informative References | 9.2 Informative References | |||
| [RFC2932] McCloghrie, K., Farinacci, D., and D. Thaler, "IPv4 | [RFC2932] McCloghrie, K., Farinacci, D., and D. Thaler, "IPv4 | |||
| Multicast Routing MIB", RFC 2932, October 2000. | Multicast Routing MIB", RFC 2932, October 2000. | |||
| [RFC2934] McCloghrie, K., Farinacci, D., Thaler, D., and B. Fenner, | [RFC2934] McCloghrie, K., Farinacci, D., Thaler, D., and B. Fenner, | |||
| "Protocol Independent Multicast MIB for IPv4", RFC 2934, | "Protocol Independent Multicast MIB for IPv4", RFC 2934, | |||
| October 2000. | October 2000. | |||
| [RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. | [RFC3376] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. | |||
| Thyagarajan, "Internet Group Management Protocol, Version | Thyagarajan, "Internet Group Management Protocol, Version | |||
| 3", RFC 3376, Updated by RFC4604, October 2002. | 3", RFC 3376, October 2002. | |||
| [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, | [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, | |||
| "Introduction and Applicability Statements for Internet- | "Introduction and Applicability Statements for Internet- | |||
| Standard Management Framework", RFC 3410, December 2002. | Standard Management Framework", RFC 3410, December 2002. | |||
| [RFC3569] Bhattacharyya, S., "An Overview of Source-Specific | [RFC3569] Bhattacharyya, S., "An Overview of Source-Specific | |||
| Multicast (SSM)", RFC 3569, July 2003. | Multicast (SSM)", RFC 3569, July 2003. | |||
| [RFC3618] Fenner, B. and D. Meyer, "Multicast Source Discovery | [RFC3618] Fenner, B. and D. Meyer, "Multicast Source Discovery | |||
| Protocol (MSDP)", RFC 3618, October 2003. | Protocol (MSDP)", RFC 3618, October 2003. | |||
| [RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery | [RFC3810] Vida, R. and L. Costa, "Multicast Listener Discovery | |||
| Version 2 (MLDv2) for IPv6", RFC 3810, June 2004. | Version 2 (MLDv2) for IPv6", RFC 3810, June 2004. | |||
| [I-D.mcwalter-ip-mcast-mib] | ||||
| McWalter, D., "IP Multicast MIB", | ||||
| draft-mcwalter-ip-mcast-mib-05 (work in progress), | ||||
| March 2007. | ||||
| Authors' Addresses | Authors' Addresses | |||
| Raghava Sivaramu | Raghava Sivaramu | |||
| Cisco Systems | Cisco Systems | |||
| 425 E. Tasman Drive | 425 E. Tasman Drive | |||
| San Jose CA 95134 | San Jose CA 95134 | |||
| USA | USA | |||
| Email: raghava@cisco.com | Email: raghava@cisco.com | |||
| James Lingard | James Lingard | |||
| Data Connection Ltd | Arastra, Inc | |||
| 100 Church Street | P.O. Box 10905 | |||
| Enfield EN2 6BQ | Palo Alto CA 94303 | |||
| United Kingdom | USA | |||
| Email: james.lingard@dataconnection.com | Email: jchl@arastra.com | |||
| David McWalter | David McWalter | |||
| Data Connection Ltd | Data Connection Ltd | |||
| 100 Church Street | 100 Church Street | |||
| Enfield EN2 6BQ | Enfield EN2 6BQ | |||
| United Kingdom | United Kingdom | |||
| Email: dmcw@dataconnection.com | Email: dmcw@dataconnection.com | |||
| Bharat Joshi | Bharat Joshi | |||
| skipping to change at page 92, line 41 ¶ | skipping to change at page 93, line 41 ¶ | |||
| This document and the information contained herein are provided on an | This document and the information contained herein are provided on an | |||
| "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS | "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS | |||
| OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND | OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND | |||
| THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS | THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS | |||
| OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF | OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF | |||
| THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED | THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED | |||
| WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. | WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. | |||
| Copyright Statement | Copyright Statement | |||
| Copyright (C) The IETF Trust (2006). This document is subject to the | Copyright (C) The IETF Trust (2007). This document is subject to the | |||
| rights, licenses and restrictions contained in BCP 78, and except as | rights, licenses and restrictions contained in BCP 78, and except as | |||
| set forth therein, the authors retain all their rights. | set forth therein, the authors retain all their rights. | |||
| Acknowledgment | Acknowledgment | |||
| Funding for the RFC Editor function is currently provided by the | Funding for the RFC Editor function is currently provided by the | |||
| Internet Society. | Internet Society. | |||
| End of changes. 92 change blocks. | ||||
| 154 lines changed or deleted | 230 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||