RFC relevance of independent

As per Relevance of the word independent, we have this rfc below:

Network Working Group K.
Request for Comments: 2934 cisco
Category: Experimental D.
Procket
D.

B.
AT&T
October 2000

Protocol Independent Multicast MIB for IPv

Status of this

This memo defines an Experimental Protocol for the
community. It does not specify an Internet standard of any kind
Discussion and suggestions for improvement are requested
Distribution of this memo is unlimited

Copyright

Copyright (C) The Internet Society (2000). All Rights Reserved

This memo defines a portion of the Management Information Base (MIB
for use with network management protocols in the Internet community
In particular, it describes managed objects used for managing
Protocol Independent Multicast (PIM) protocol for IPv4.

Table of

1 Introduction ................................................. 2
2 The SNMP Network Management Framework ........................ 2
3 Overview ..................................................... 3
4 Definitions .................................................. 4
5 Security Considerations ...................................... 22
6 Intellectual Property Notice ................................. 23
7 Acknowledgements ............................................. 23
8 Authors' Addresses ........................................... 24
9 References ................................................... 24
10 Full Copyright Statement .................................... 27

McCloghrie, et al. Experimental [Page 1]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

1.

This memo defines a portion of the Management Information Base (MIB
for use with network management protocols in the Internet community
In particular, it describes managed objects used for managing
Protocol Independent Multicast (PIM) protocol [16,17,18,19].
MIB module is applicable to IPv4 multicast routers which
PIM. This MIB does not support management of PIM for other
families, including IPv6. Such management may be supported by
MIBs

2. The SNMP Network Management

The SNMP Management Framework presently consists of five
components

o An overall architecture, described in RFC 2271 [1].

o Mechanisms for describing and naming objects and events for
purpose of management. The first version of this Structure
Management Information (SMI) is called SMIv1 and described
STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4].
The second version, called SMIv2, is described in STD 58,
2578 [5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7].

o Message protocols for transferring management information.
first version of the SNMP message protocol is called SNMPv1
described in STD 15, RFC 1157 [8]. A second version of the
message protocol, which is not an Internet standards
protocol, is called SNMPv2c and described in RFC 1901 [9]
RFC 1906 [10]. The third version of the message protocol
called SNMPv3 and described in RFC 1906 [10], RFC 2572 [11]
RFC 2574 [12].

o Protocol operations for accessing management information.
first set of protocol operations and associated PDU formats
described in STD 15, RFC 1157 [8]. A second set of
operations and associated PDU formats is described in RFC 1905
[13].

o A set of fundamental applications described in RFC 2573 [14]
the view-based access control mechanism described in RFC 2575
[15].

Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the mechanisms defined in the SMI

McCloghrie, et al. Experimental [Page 2]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

This memo specifies a MIB module that is compliant to the SMIv2.
MIB conforming to the SMIv1 can be produced through the
translations. The resulting translated MIB must be
equivalent, except where objects or events are omitted because
translation is possible (use of Counter64). Some machine
information in SMIv2 will be converted into textual descriptions
SMIv1 during the translation process. However, this loss of
readable information is not considered to change the semantics of
MIB

3.

This MIB module contains one scalar and eight tables. Some of
objects in these tables are deprecated. This MIB contains
objects since they are necessary for managing PIMv1 routers,
PIMv1 itself is obsoleted by PIMv2 [18,19].

The tables contained in this MIB are

(1) The PIM Interface Table contains one row for each of
router's PIM interfaces

(2) The PIM Neighbor Table contains one row for each of the router'
PIM neighbors

(3) The PIM IP Multicast Route Table contains one row for
multicast routing entry whose incoming interface is running PIM

(4) The PIM Next Hop Table which contains one row for each
interface list entry in the multicast routing table
interface is running PIM, and whose state is pruned

(5) The (deprecated) PIM RP Table contains the PIM (version 1)
information for IP multicast groups which is common to all
of a group

(6) The PIM RP-Set Table contains the PIM (version 2)
for sets of candidate Rendezvous Points (RPs) for IP
group addresses with particular address prefixes

(7) The PIM Candidate-RP Table contains the IP multicast groups
which the local router is to advertise itself as a Candidate-RP
If this table is empty, then the local router advertises
as a Candidate-RP for all groups

(8) The PIM Component Table contains one row for each of the
domains to which the router is connected

McCloghrie, et al. Experimental [Page 3]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

4.

PIM-MIB DEFINITIONS ::=

MODULE-IDENTITY, OBJECT-TYPE, experimental
NOTIFICATION-TYPE
Integer32, IpAddress, TimeTicks FROM SNMPv2-
RowStatus, TruthValue FROM SNMPv2-
MODULE-COMPLIANCE, OBJECT-GROUP
NOTIFICATION-GROUP FROM SNMPv2-
ipMRouteGroup, ipMRouteSource
ipMRouteSourceMask, ipMRouteNextHopGroup
ipMRouteNextHopSource, ipMRouteNextHopSourceMask
ipMRouteNextHopIfIndex
ipMRouteNextHopAddress FROM IPMROUTE-STD-
InterfaceIndex FROM IF-MIB

pimMIB MODULE-
LAST-UPDATED "200009280000Z" -- September 28, 2000
ORGANIZATION "IETF IDMR Working Group."
CONTACT-
" Dave
Microsoft
One Microsoft
Redmond, WA 98052-6399

Phone: +1 425 703 8835
EMail: dthaler@microsoft.com

"The MIB module for management of PIM routers."
REVISION "200009280000Z" -- September 28, 2000

"Initial version, published as RFC 2934."
::= { experimental 61 }

pimMIBObjects OBJECT IDENTIFIER ::= { pimMIB 1 }

pimTraps OBJECT IDENTIFIER ::= { pimMIBObjects 0 }

pim OBJECT IDENTIFIER ::= { pimMIBObjects 1 }

pimJoinPruneInterval OBJECT-
SYNTAX Integer32
UNITS "seconds
MAX-ACCESS read-
STATUS

McCloghrie, et al. Experimental [Page 4]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

"The default interval at which periodic PIM-SM Join/
messages are to be sent."
::= { pim 1 }

-- The PIM Interface

pimInterfaceTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

"The (conceptual) table listing the router's PIM interfaces
IGMP and PIM are enabled on all interfaces listed in
table."
::= { pim 2 }

pimInterfaceEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"An entry (conceptual row) in the pimInterfaceTable."
INDEX { pimInterfaceIfIndex }
::= { pimInterfaceTable 1 }

PimInterfaceEntry ::= SEQUENCE {
pimInterfaceIfIndex InterfaceIndex
pimInterfaceAddress IpAddress
pimInterfaceNetMask IpAddress
pimInterfaceMode INTEGER
pimInterfaceDR IpAddress
pimInterfaceHelloInterval Integer32,
pimInterfaceStatus RowStatus
pimInterfaceJoinPruneInterval Integer32,
pimInterfaceCBSRPreference Integer32

pimInterfaceIfIndex OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"The ifIndex value of this PIM interface."
::= { pimInterfaceEntry 1 }

pimInterfaceAddress OBJECT-
SYNTAX

McCloghrie, et al. Experimental [Page 5]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

MAX-ACCESS read-
STATUS

"The IP address of the PIM interface."
::= { pimInterfaceEntry 2 }

pimInterfaceNetMask OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The network mask for the IP address of the PIM interface."
::= { pimInterfaceEntry 3 }

pimInterfaceMode OBJECT-
SYNTAX INTEGER { dense(1), sparse(2), sparseDense(3) }
MAX-ACCESS read-
STATUS

"The configured mode of this PIM interface. A value
sparseDense is only valid for PIMv1."
DEFVAL { dense }
::= { pimInterfaceEntry 4 }

pimInterfaceDR OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The Designated Router on this PIM interface. For point-to
point interfaces, this object has the value 0.0.0.0."
::= { pimInterfaceEntry 5 }

pimInterfaceHelloInterval OBJECT-
SYNTAX Integer32
UNITS "seconds
MAX-ACCESS read-
STATUS

"The frequency at which PIM Hello messages are
on this interface."
DEFVAL { 30 }
::= { pimInterfaceEntry 6 }

pimInterfaceStatus OBJECT-
SYNTAX
MAX-ACCESS read-

McCloghrie, et al. Experimental [Page 6]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

STATUS

"The status of this entry. Creating the entry enables
on the interface; destroying the entry disables PIM on
interface."
::= { pimInterfaceEntry 7 }

pimInterfaceJoinPruneInterval OBJECT-
SYNTAX Integer32
UNITS "seconds
MAX-ACCESS read-
STATUS

"The frequency at which PIM Join/Prune messages
transmitted on this PIM interface. The default value
this object is the pimJoinPruneInterval."
::= { pimInterfaceEntry 8 }

pimInterfaceCBSRPreference OBJECT-
SYNTAX Integer32 (-1..255)
MAX-ACCESS read-
STATUS

"The preference value for the local interface as a
bootstrap router. The value of -1 is used to indicate
the local interface is not a candidate BSR interface."
DEFVAL { 0 }
::= { pimInterfaceEntry 9 }

-- The PIM Neighbor

pimNeighborTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

"The (conceptual) table listing the router's PIM neighbors."
::= { pim 3 }

pimNeighborEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"An entry (conceptual row) in the pimNeighborTable."
INDEX { pimNeighborAddress }
::= { pimNeighborTable 1 }

McCloghrie, et al. Experimental [Page 7]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

PimNeighborEntry ::= SEQUENCE {
pimNeighborAddress IpAddress
pimNeighborIfIndex InterfaceIndex
pimNeighborUpTime TimeTicks
pimNeighborExpiryTime TimeTicks
pimNeighborMode

pimNeighborAddress OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"The IP address of the PIM neighbor for which this
contains information."
::= { pimNeighborEntry 1 }

pimNeighborIfIndex OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The value of ifIndex for the interface used to reach
PIM neighbor."
::= { pimNeighborEntry 2 }

pimNeighborUpTime OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The time since this PIM neighbor (last) became a
of the local router."
::= { pimNeighborEntry 3 }

pimNeighborExpiryTime OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The minimum time remaining before this PIM neighbor will
aged out."
::= { pimNeighborEntry 4 }

pimNeighborMode OBJECT-
SYNTAX INTEGER { dense(1), sparse(2) }
MAX-ACCESS read-
STATUS

McCloghrie, et al. Experimental [Page 8]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

"The active PIM mode of this neighbor. This object
deprecated for PIMv2 routers since all neighbors on
interface must be either dense or sparse as determined
the protocol running on the interface."
::= { pimNeighborEntry 5 }

--
-- The PIM IP Multicast Route
--

pimIpMRouteTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

"The (conceptual) table listing PIM-specific information
a subset of the rows of the ipMRouteTable defined in the
Multicast MIB."
::= { pim 4 }

pimIpMRouteEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"An entry (conceptual row) in the pimIpMRouteTable.
is one entry per entry in the ipMRouteTable whose
interface is running PIM."
INDEX { ipMRouteGroup, ipMRouteSource, ipMRouteSourceMask }
::= { pimIpMRouteTable 1 }

PimIpMRouteEntry ::= SEQUENCE {
pimIpMRouteUpstreamAssertTimer TimeTicks
pimIpMRouteAssertMetric Integer32,
pimIpMRouteAssertMetricPref Integer32,
pimIpMRouteAssertRPTBit TruthValue
pimIpMRouteFlags

pimIpMRouteUpstreamAssertTimer OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The time remaining before the router changes its
neighbor back to its RPF neighbor. This timer is called
Assert timer in the PIM Sparse and Dense mode specification

McCloghrie, et al. Experimental [Page 9]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

A value of 0 indicates that no Assert has changed
upstream neighbor away from the RPF neighbor."
::= { pimIpMRouteEntry 1 }

pimIpMRouteAssertMetric OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS

"The metric advertised by the assert winner on the
interface, or 0 if no such assert is in received."
::= { pimIpMRouteEntry 2 }

pimIpMRouteAssertMetricPref OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS

"The preference advertised by the assert winner on
upstream interface, or 0 if no such assert is in effect."
::= { pimIpMRouteEntry 3 }

pimIpMRouteAssertRPTBit OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The value of the RPT-bit advertised by the assert winner
the upstream interface, or false if no such assert is
effect."
::= { pimIpMRouteEntry 4 }

pimIpMRouteFlags OBJECT-
SYNTAX BITS {
rpt(0),
spt(1)
}
MAX-ACCESS read-
STATUS

"This object describes PIM-specific flags related to
multicast state entry. See the PIM Sparse
specification for the meaning of the RPT and SPT bits."
::= { pimIpMRouteEntry 5 }

--
-- The PIM Next Hop
--

McCloghrie, et al. Experimental [Page 10]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

pimIpMRouteNextHopTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

"The (conceptual) table listing PIM-specific information
a subset of the rows of the ipMRouteNextHopTable defined
the IP Multicast MIB."
::= { pim 7 }

pimIpMRouteNextHopEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"An entry (conceptual row) in the pimIpMRouteNextHopTable
There is one entry per entry in the
whose interface is running PIM and
ipMRouteNextHopState is pruned(1)."
INDEX { ipMRouteNextHopGroup, ipMRouteNextHopSource
ipMRouteNextHopSourceMask, ipMRouteNextHopIfIndex
ipMRouteNextHopAddress }
::= { pimIpMRouteNextHopTable 1 }

PimIpMRouteNextHopEntry ::= SEQUENCE {
pimIpMRouteNextHopPruneReason

pimIpMRouteNextHopPruneReason OBJECT-
SYNTAX INTEGER {
other (1),
prune (2),
assert (3)
}
MAX-ACCESS read-
STATUS

"This object indicates why the downstream interface
pruned, whether in response to a PIM prune message or due
PIM Assert processing."
::= { pimIpMRouteNextHopEntry 2 }

-- The PIM RP

pimRPTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

McCloghrie, et al. Experimental [Page 11]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

"The (conceptual) table listing PIM version 1
for the Rendezvous Points (RPs) for IP multicast groups
This table is deprecated since its function is replaced
the pimRPSetTable for PIM version 2."
::= { pim 5 }

pimRPEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"An entry (conceptual row) in the pimRPTable. There is
entry per RP address for each IP multicast group."
INDEX { pimRPGroupAddress, pimRPAddress }
::= { pimRPTable 1 }

PimRPEntry ::= SEQUENCE {
pimRPGroupAddress IpAddress
pimRPAddress IpAddress
pimRPState INTEGER
pimRPStateTimer TimeTicks
pimRPLastChange TimeTicks
pimRPRowStatus

pimRPGroupAddress OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"The IP multicast group address for which this
contains information about an RP."
::= { pimRPEntry 1 }

pimRPAddress OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"The unicast address of the RP."
::= { pimRPEntry 2 }

pimRPState OBJECT-
SYNTAX INTEGER { up(1), down(2) }
MAX-ACCESS read-
STATUS

McCloghrie, et al. Experimental [Page 12]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

"The state of the RP."
::= { pimRPEntry 3 }

pimRPStateTimer OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The minimum time remaining before the next state change
When pimRPState is up, this is the minimum time which
expire until it can be declared down. When pimRPState
down, this is the time until it will be declared up (
order to retry)."
::= { pimRPEntry 4 }

pimRPLastChange OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The value of sysUpTime at the time when the
instance of pimRPState last changed its value."
::= { pimRPEntry 5 }

pimRPRowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The status of this row, by which new entries may
created, or old entries deleted from this table."
::= { pimRPEntry 6 }

-- The PIM RP-Set

pimRPSetTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

"The (conceptual) table listing PIM information
candidate Rendezvous Points (RPs) for IP multicast groups
When the local router is the BSR, this information
obtained from received Candidate-RP-Advertisements.
the local router is not the BSR, this information
obtained from received RP-Set messages."
::= { pim 6 }

McCloghrie, et al. Experimental [Page 13]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

pimRPSetEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"An entry (conceptual row) in the pimRPSetTable."
INDEX { pimRPSetComponent, pimRPSetGroupAddress
pimRPSetGroupMask, pimRPSetAddress }
::= { pimRPSetTable 1 }

PimRPSetEntry ::= SEQUENCE {

pimRPSetGroupAddress IpAddress
pimRPSetGroupMask IpAddress
pimRPSetAddress IpAddress
pimRPSetHoldTime Integer32,
pimRPSetExpiryTime TimeTicks
pimRPSetComponent Integer32

pimRPSetGroupAddress OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"The IP multicast group address which, when combined
pimRPSetGroupMask, gives the group prefix for which
entry contains information about the Candidate-RP."
::= { pimRPSetEntry 1 }

pimRPSetGroupMask OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"The multicast group address mask which, when combined
pimRPSetGroupAddress, gives the group prefix for which
entry contains information about the Candidate-RP."
::= { pimRPSetEntry 2 }

pimRPSetAddress OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"The IP address of the Candidate-RP."
::= { pimRPSetEntry 3 }

McCloghrie, et al. Experimental [Page 14]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

pimRPSetHoldTime OBJECT-
SYNTAX Integer32 (0..255)
UNITS "seconds
MAX-ACCESS read-
STATUS

"The holdtime of a Candidate-RP. If the local router is
the BSR, this value is 0."
::= { pimRPSetEntry 4 }

pimRPSetExpiryTime OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The minimum time remaining before the Candidate-RP will
declared down. If the local router is not the BSR,
value is 0."
::= { pimRPSetEntry 5 }

pimRPSetComponent OBJECT-
SYNTAX Integer32 (1..255)
MAX-ACCESS not-
STATUS

" A number uniquely identifying the component.
protocol instance connected to a separate domain should
a different index value."
::= { pimRPSetEntry 6 }

--
-- Note: { pim 8 } through { pim 10 } were used in older
-- of this MIB. Since some earlier versions of this MIB have
-- widely-deployed, these values must not be used in the future
-- as long the MIB is rooted under { experimental 61 }.
--

-- The PIM Candidate-RP

pimCandidateRPTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

"The (conceptual) table listing the IP multicast groups
which the local router is to advertise itself as
Candidate-RP when the value of pimComponentCRPHoldTime
non-zero. If this table is empty, then the local

McCloghrie, et al. Experimental [Page 15]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

will advertise itself as a Candidate-RP for all
(providing the value of pimComponentCRPHoldTime is non
zero)."
::= { pim 11 }

pimCandidateRPEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"An entry (conceptual row) in the pimCandidateRPTable."
INDEX { pimCandidateRPGroupAddress
pimCandidateRPGroupMask }
::= { pimCandidateRPTable 1 }

PimCandidateRPEntry ::= SEQUENCE {
pimCandidateRPGroupAddress IpAddress
pimCandidateRPGroupMask IpAddress
pimCandidateRPAddress IpAddress
pimCandidateRPRowStatus

pimCandidateRPGroupAddress OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"The IP multicast group address which, when combined
pimCandidateRPGroupMask, identifies a group prefix for
the local router will advertise itself as a Candidate-RP."
::= { pimCandidateRPEntry 1 }

pimCandidateRPGroupMask OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"The multicast group address mask which, when combined
pimCandidateRPGroupMask, identifies a group prefix for
the local router will advertise itself as a Candidate-RP."
::= { pimCandidateRPEntry 2 }

pimCandidateRPAddress OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The (unicast) address of the interface which will

McCloghrie, et al. Experimental [Page 16]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

advertised as a Candidate-RP."
::= { pimCandidateRPEntry 3 }

pimCandidateRPRowStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The status of this row, by which new entries may
created, or old entries deleted from this table."
::= { pimCandidateRPEntry 4 }

-- The PIM Component

pimComponentTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS

"The (conceptual) table containing objects specific to a
domain. One row exists for each domain to which the
is connected. A PIM-SM domain is defined as an area of
network over which Bootstrap messages are forwarded
Typically, a PIM-SM router will be a member of exactly
domain. This table also supports, however, routers
may form a border between two PIM-SM domains and do
forward Bootstrap messages between them."
::= { pim 12 }

pimComponentEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS

"An entry (conceptual row) in the pimComponentTable."
INDEX { pimComponentIndex }
::= { pimComponentTable 1 }

PimComponentEntry ::= SEQUENCE {
pimComponentIndex Integer32,
pimComponentBSRAddress IpAddress
pimComponentBSRExpiryTime TimeTicks
pimComponentCRPHoldTime Integer32,
pimComponentStatus

pimComponentIndex OBJECT-
SYNTAX Integer32 (1..255)

McCloghrie, et al. Experimental [Page 17]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

MAX-ACCESS not-
STATUS

"A number uniquely identifying the component. Each
instance connected to a separate domain should have
different index value. Routers that only support
in a single PIM-SM domain should use a
value of 1."
::= { pimComponentEntry 1 }

pimComponentBSRAddress OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The IP address of the bootstrap router (BSR) for the
PIM region."
::= { pimComponentEntry 2 }

pimComponentBSRExpiryTime OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

"The minimum time remaining before the bootstrap router
the local domain will be declared down. For candidate BSRs
this is the time until the component sends an RP-
message. For other routers, this is the time until it
accept an RP-Set message from a lower candidate BSR."
::= { pimComponentEntry 3 }

pimComponentCRPHoldTime OBJECT-
SYNTAX Integer32 (0..255)
UNITS "seconds
MAX-ACCESS read-
STATUS

"The holdtime of the component when it is a candidate RP
the local domain. The value of 0 is used to indicate
the local system is not a Candidate-RP."
DEFVAL { 0 }
::= { pimComponentEntry 4 }

pimComponentStatus OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS

McCloghrie, et al. Experimental [Page 18]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

"The status of this entry. Creating the entry
another protocol instance; destroying the entry disables
protocol instance."
::= { pimComponentEntry 5 }

-- PIM

pimNeighborLoss NOTIFICATION-
OBJECTS {

}
STATUS

"A pimNeighborLoss trap signifies the loss of an
with a neighbor. This trap should be generated when
neighbor timer expires, and the router has no
neighbors on the same interface with a lower IP address
itself."
::= { pimTraps 1 }

-- conformance

pimMIBConformance OBJECT IDENTIFIER ::= { pimMIB 2 }
pimMIBCompliances OBJECT IDENTIFIER ::= { pimMIBConformance 1 }
pimMIBGroups OBJECT IDENTIFIER ::= { pimMIBConformance 2 }

-- compliance

pimV1MIBCompliance MODULE-
STATUS

"The compliance statement for routers running PIMv1
implementing the PIM MIB."
MODULE -- this
MANDATORY-GROUPS { pimV1MIBGroup }

::= { pimMIBCompliances 1 }

pimSparseV2MIBCompliance MODULE-
STATUS

"The compliance statement for routers running PIM
Mode and implementing the PIM MIB."
MODULE -- this
MANDATORY-GROUPS { pimV2MIBGroup }

GROUP pimV2

McCloghrie, et al. Experimental [Page 19]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

"This group is mandatory if the router is capable of being
Candidate RP."

OBJECT
MIN-ACCESS read-

"Write access is not required."

::= { pimMIBCompliances 2 }

pimDenseV2MIBCompliance MODULE-
STATUS

"The compliance statement for routers running PIM Dense
and implementing the PIM MIB."
MODULE -- this

MANDATORY-GROUPS { pimDenseV2MIBGroup }

OBJECT
MIN-ACCESS read-

"Write access is not required."

::= { pimMIBCompliances 3 }

-- units of

pimNotificationGroup NOTIFICATION-
NOTIFICATIONS { pimNeighborLoss }
STATUS

"A collection of notifications for signaling important
events."
::= { pimMIBGroups 1 }

pimV2MIBGroup OBJECT-
OBJECTS { pimJoinPruneInterval, pimNeighborIfIndex
pimNeighborUpTime, pimNeighborExpiryTime
pimInterfaceAddress, pimInterfaceNetMask
pimInterfaceDR, pimInterfaceHelloInterval
pimInterfaceStatus, pimInterfaceJoinPruneInterval
pimInterfaceCBSRPreference, pimInterfaceMode
pimRPSetHoldTime, pimRPSetExpiryTime
pimComponentBSRAddress, pimComponentBSRExpiryTime
pimComponentCRPHoldTime, pimComponentStatus
pimIpMRouteFlags,

McCloghrie, et al. Experimental [Page 20]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

}
STATUS

"A collection of objects to support management of PIM
Mode (version 2) routers."
::= { pimMIBGroups 2 }

pimDenseV2MIBGroup OBJECT-
OBJECTS { pimNeighborIfIndex
pimNeighborUpTime, pimNeighborExpiryTime
pimInterfaceAddress, pimInterfaceNetMask
pimInterfaceDR, pimInterfaceHelloInterval
pimInterfaceStatus,
}
STATUS

"A collection of objects to support management of PIM
Mode (version 2) routers."
::= { pimMIBGroups 5 }

pimV2CandidateRPMIBGroup OBJECT-
OBJECTS { pimCandidateRPAddress

}
STATUS

"A collection of objects to support configuration of
groups a router is to advertise itself as a Candidate-RP."
::= { pimMIBGroups 3 }

pimV1MIBGroup OBJECT-
OBJECTS { pimJoinPruneInterval, pimNeighborIfIndex
pimNeighborUpTime, pimNeighborExpiryTime
pimNeighborMode
pimInterfaceAddress, pimInterfaceNetMask
pimInterfaceJoinPruneInterval, pimInterfaceStatus
pimInterfaceMode, pimInterfaceDR
pimInterfaceHelloInterval
pimRPState, pimRPStateTimer
pimRPLastChange,
}
STATUS

"A collection of objects to support management of
(version 1) routers."
::= { pimMIBGroups 4 }

pimNextHopGroup OBJECT-

McCloghrie, et al. Experimental [Page 21]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

OBJECTS { pimIpMRouteNextHopPruneReason }
STATUS

"A collection of optional objects to provide per-next
information for diagnostic purposes. Supporting this
may add a large number of instances to a tree walk, but
information in this group can be extremely useful
tracking down multicast connectivity problems."
::= { pimMIBGroups 6 }

pimAssertGroup OBJECT-
OBJECTS { pimIpMRouteAssertMetric, pimIpMRouteAssertMetricPref
pimIpMRouteAssertRPTBit }
STATUS

"A collection of optional objects to provide
information about the assert election process. There is
protocol reason to keep such information, but
implementations may already keep this information and
it available. These objects can also be very useful
debugging connectivity or duplicate packet problems
especially if the assert winner does not support the PIM
IP Multicast MIBs."
::= { pimMIBGroups 7 }

5. Security

This MIB contains readable objects whose values provide
related to multicast routing, including information on the
topology. There are also a number of objects that have a MAX-
clause of read-write and/or read-create, which allow an
to configure PIM in the router

While unauthorized access to the readable objects is
innocuous, unauthorized access to the write-able objects could
a denial of service. Hence, the support for SET operations in
non-secure environment without proper protection can have a
effect on network operations

SNMPv1 by itself is such an insecure environment. Even if
network itself is secure (for example by using IPSec), even then
there is no control as to who on the secure network is allowed
access and SET (change/create/delete) the objects in this MIB

McCloghrie, et al. Experimental [Page 22]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

It is recommended that the implementers consider the
features as provided by the SNMPv3 framework. Specifically, the
of the User-based Security Model RFC 2274 [12] and the View-
Access Control Model RFC 2275 [15] is recommended

It is then a customer/user responsibility to ensure that the
entity giving access to this MIB, is properly configured to
access to those objects only to those principals (users) that
legitimate rights to access them

6. Intellectual Property

The IETF takes no position regarding the validity or scope of
intellectual property or other rights that might be claimed
pertain to the implementation or use of the technology described
this document or the extent to which any license under such
might or might not be available; neither does it represent that
has made any effort to identify any such rights. Information on
IETF's procedures with respect to rights in standards-track
standards-related documentation can be found in BCP-11. Copies
claims of rights made available for publication and any assurances
licenses to be made available, or the result of an attempt made
obtain a general license or permission for the use of
proprietary rights by implementers or users of this specification
be obtained from the IETF Secretariat

The IETF invites any interested party to bring to its attention
copyrights, patents or patent applications, or other
rights which may cover technology that may be required to
this standard. Please address the information to the IETF
Director

7.

This MIB module has been updated based on feedback from the IETF'
Inter-Domain Multicast Routing (IDMR) Working Group

McCloghrie, et al. Experimental [Page 23]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

8. Authors'

Keith
cisco Systems, Inc
170 West Tasman
San Jose, CA 95134-1706

Phone: +1 408 526 5260
EMail: kzm@cisco.

Dino
Procket
3850 North First
San Jose, CA 95134

Phone: +1 408-954-7909
Email: dino@procket.

Dave
Microsoft
One Microsoft
Redmond, WA 98052-6399

Phone: +1 425 703 8835
EMail: dthaler@microsoft.

Bill
AT&T Labs -
75 Willow Rd
Menlo Park, CA 94025

Phone: +1 650 330 7893
EMail: fenner@research.att.

9.

[1] Wijnen, B., Harrington, D. and R. Presuhn, "An Architecture
Describing SNMP Management Frameworks", RFC 2571, April 1999.

[2] Rose, M. and K. McCloghrie, "Structure and Identification
Management Information for TCP/IP-based Internets", STD 16,
1155, May 1990.

[3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16,
RFC 1212, March 1991.

McCloghrie, et al. Experimental [Page 24]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

[4] Rose, M., "A Convention for Defining Traps for use with
SNMP", RFC 1215, March 1991.

[5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose
M. and S. Waldbusser, "Structure of Management
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.

[6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose
M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58,
RFC 2579, April 1999.

[7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose
M. and S. Waldbusser, "Conformance Statements for SMIv2",
58, RFC 2580, April 1999.

[8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "
Network Management Protocol", STD 15, RFC 1157, May 1990.

[9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser
"Introduction to Community-based SNMPv2", RFC 1901,
1996.

[10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "
Mappings for Version 2 of the Simple Network Management
(SNMPv2)", RFC 1906, January 1996.

[11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "
Processing and Dispatching for the Simple Network
Protocol (SNMP)", RFC 2572, April 1999.

[12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM
for version 3 of the Simple Network Management
(SNMPv3)", RFC 2574, April 1999.

[13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "
Operations for Version 2 of the Simple Network
Protocol (SNMPv2)", RFC 1905, January 1996.

[14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications",
2573, April 1999.

[15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
Control Model (VACM) for the Simple Network Management
(SNMP)", RFC 2575, April 1999.

[16] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Liu, G
and L. Wei, "Protocol Independent Multicast (PIM):
and Architecture", Work in Progress

McCloghrie, et al. Experimental [Page 25]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

[17] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Liu, G
and L. Wei, "Protocol Independent Multicast (PIM):
Specification", Work in Progress

[18] Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering, S.,
Handley, M., Jacobson, V., Liu, C., Sharma, P. and L. Wei
"Protocol Independent Multicast - Sparse Mode (PIM-SM):
Specification", RFC 2362, June 1998.

[19] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Helmy, A
and L. Wei, "Protocol Independent Multicast Version 2,
Mode Specification", Work in Progress

[20] McCloghrie, K., Farinacci, D. and D. Thaler, "IPv4
Routing MIB", RFC 2932, October 2000.

McCloghrie, et al. Experimental [Page 26]

RFC 2934 Protocol Independent Multicast MIB for IPv4 October 2000

10. Full Copyright

Copyright (C) The Internet Society (2000). All Rights Reserved

This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English

The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns

This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE

Funding for the RFC Editor function is currently provided by
Internet Society

McCloghrie, et al. Experimental [Page 27]

if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.

RFC documents can be found at I.E.T.F.

Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX