draft-ietf-idmr-multicast-routmib-06.txt   draft-ietf-idmr-multicast-routmib-07.txt 
IDMR Working Group Keith McCloghrie IDMR Working Group Keith McCloghrie
INTERNET-DRAFT Dino Farinacci INTERNET-DRAFT Dino Farinacci
Expires May 1998 cisco Systems Expires January 1999 cisco Systems
Dave Thaler Dave Thaler
University of Michigan Microsoft
20 November 1997 23 July 1998
IP Multicast Routing MIB IP Multicast Routing MIB
<draft-ietf-idmr-multicast-routmib-06.txt> <draft-ietf-idmr-multicast-routmib-07.txt>
Status of this Memo Status of this Memo
This document is an Internet Draft. Internet Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its Areas, and documents of the Internet Engineering Task Force (IETF), its areas, and
its Working Groups. Note that other groups may also distribute working its working groups. Note that other groups may also distribute working
documents as Internet Drafts. documents as Internet-Drafts.
Internet Drafts are valid for a maximum of six months and may be Internet-Drafts are draft documents valid for a maximum of six months
updated, replaced, or obsoleted by other documents at any time. It is and may be updated, replaced, or obsoleted by other documents at any
inappropriate to use Internet Drafts as reference material or to cite time. It is inappropriate to use Internet- Drafts as reference material
them other than as a "work in progress". or to cite them other than as ``work in progress.''
To learn the current status of any Internet-Draft, please check the
``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow
Directories on ftp.ietf.org (US East Coast), nic.nordu.net (Europe),
ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim).
Copyright Notice
Copyright (C) The Internet Society (1998). All Rights Reserved.
1. Introduction 1. Introduction
This memo defines an experimental portion of the Management Information This memo defines an experimental portion of the Management Information
Base (MIB) for use with network management protocols in the Internet Base (MIB) for use with network management protocols in the Internet
community. In particular, it describes managed objects used for community. In particular, it describes managed objects used for
managing IP Multicast Routing [5], independent of the specific multicast managing IP Multicast Routing [16], independent of the specific
routing protocol [6,7,8,9,10] in use. Managed objects specific to
particular multicast routing protocols are specified elsewhere.
Draft IP Multicast Routing MIB November 1997 Draft IP Multicast Routing MIB July 1998
multicast routing protocol [17-21] in use. Managed objects specific to
particular multicast routing protocols are specified elsewhere.
2. Revision History 2. Revision History
A record of changes which will be removed before publication. A record of changes which will be removed before publication.
23 July 1998
(1) added ipMRouteRtProto, ipMRouteRtAddr, ipMRouteRtMask, and
ipMRouteRtType to get the route used by the multicast forwarding
entry. This provides functionality equivalent to mtrace.
(2) added ipMRouteScopeTable for mapping admin boundaries to user-
friendly scope names.
(3) changed comments on pimSparseMode and pimDenseMode enumeration
values to clarify that they may be used for PIMv1.
(4) added security considerations and copyright notice
20 November 1997 20 November 1997
(1) made ipMRouteInterfaceProtocol read-only. (1) made ipMRouteInterfaceProtocol read-only.
(2) added ipMRouteInterfaceRateLimit, ipMRouteInterfaceInMcastOctets, (2) added ipMRouteInterfaceRateLimit, ipMRouteInterfaceInMcastOctets,
ipMRouteInterfaceOutMcastOctets, ipMRouteInterfaceHCInMcastOctets, ipMRouteInterfaceOutMcastOctets, ipMRouteInterfaceHCInMcastOctets,
and ipMRouteInterfaceHCOutMcastOctets, with the HC objects in a new and ipMRouteInterfaceHCOutMcastOctets, with the HC objects in a new
conformance group. conformance group.
26 March 26 March
skipping to change at page 2, line 34 skipping to change at page 3, line 5
(2) added protocol values for PIM-DM, PIM-SM, and IGMP-only links. (2) added protocol values for PIM-DM, PIM-SM, and IGMP-only links.
26 November 26 November
(1) moved ipMRouteNextHopPkts to its own conformance group. (1) moved ipMRouteNextHopPkts to its own conformance group.
9 June 9 June
(1) added the ipMRouteBoundaryTable and ipMRouteNextHopPkts. (1) added the ipMRouteBoundaryTable and ipMRouteNextHopPkts.
Draft IP Multicast Routing MIB July 1998
(2) updated references, etc. (2) updated references, etc.
28 March 28 March
(1) renamed ipMRouteNextHopClosestMember to (1) renamed ipMRouteNextHopClosestMember to
ipMRouteNextHopClosestMemberHops, and ipMRouteDifferentInIfIndexes ipMRouteNextHopClosestMemberHops, and ipMRouteDifferentInIfIndexes
to ipMRouteDifferentInIfPacket. to ipMRouteDifferentInIfPacket.
26 February 26 February
(1) added ipMRouteNextHopAddress as a INDEX variable for the (1) added ipMRouteNextHopAddress as a INDEX variable for the
ipMRouteNextHopTable. ipMRouteNextHopTable.
(2) added ipMRouteNextHopClosestMember and ipMRouteNextHopProtocol (2) added ipMRouteNextHopClosestMember and ipMRouteNextHopProtocol
(3) added ipMRouteMIBHopCountGroup. (3) added ipMRouteMIBHopCountGroup.
Draft IP Multicast Routing MIB November 1997
(4) specified that an expiry-time of zero means that an entry is not (4) specified that an expiry-time of zero means that an entry is not
subject to aging. subject to aging.
(5) added references for MOSPF and CBT. (5) added references for MOSPF and CBT.
4 February 4 February
(1) removed ipMRouteOutList (1) removed ipMRouteOutList
(2) Modified ipMRouteNextHopTable to be INDEX-ed by (2) Modified ipMRouteNextHopTable to be INDEX-ed by
ipMRouteNextHopGroup, ipMRouteNextHopSource, ipMRouteNextHopGroup, ipMRouteNextHopSource,
ipMRouteNextHopSourceMask, and ipMRouteNextHopIfIndex. ipMRouteNextHopSourceMask, and ipMRouteNextHopIfIndex.
(3) added ipMRouteProtocol (3) added ipMRouteProtocol
(4) replaced "RPF" terminology with "Upstream neighbor". (4) replaced "RPF" terminology with "Upstream neighbor".
15 July - initial version. 15 July - initial version.
Draft IP Multicast Routing MIB November 1997 3. The SNMP Management Framework
3. The SNMP Network Management Framework The SNMP Management Framework presently consists of five major
components:
The SNMP Network Management Framework presently consists of three major o An overall architecture, described in RFC 2271 [1].
components. They are:
o RFC 1902 [1] which defines the SMI, the mechanisms used for Draft IP Multicast Routing MIB July 1998
describing and naming objects for the purpose of management.
o STD 17, RFC 1213 [2] defines MIB-II, the core set of managed o Mechanisms for describing and naming objects and events for the
objects for the Internet suite of protocols. purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in RFC
1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, called
SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 1904 [7].
o RFC 1157 [3] and RFC 1905 [4] which define two versions of the o Message protocols for transferring management information. The
protocol used for network access to managed objects. first version of the SNMP message protocol is called SNMPv1 and
described in RFC 1157 [8]. A second version of the SNMP message
protocol, which is not an Internet standards track protocol, is
called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10].
The third version of the message protocol is called SNMPv3 and
described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12].
The Framework permits new objects to be defined for the purpose of o Protocol operations for accessing management information. The first
experimentation and evaluation. set of protocol operations and associated PDU formats is described
in RFC 1157 [8]. A second set of protocol operations and associated
PDU formats is described in RFC 1905 [13].
o A set of fundamental applications described in RFC 2273 [14] and
the view-based access control mechanism described in RFC 2275 [15].
Managed objects are accessed via a virtual information store, termed the
Management Information Base or MIB. Objects in the MIB are defined
using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A MIB
conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the
MIB.
3.1. Object Definitions 3.1. Object Definitions
Managed objects are accessed via a virtual information store, termed the Managed objects are accessed via a virtual information store, termed the
Management Information Base or MIB. Objects in the MIB are defined Management Information Base or MIB. Objects in the MIB are defined
using the subset of Abstract Syntax Notation One (ASN.1) defined in the using the subset of Abstract Syntax Notation One (ASN.1) defined in the
SMI. In particular, each object type is named by an OBJECT IDENTIFIER, SMI. In particular, each object type is named by an OBJECT IDENTIFIER,
an administratively assigned name. The object type together with an an administratively assigned name. The object type together with an
object instance serves to uniquely identify a specific instantiation of object instance serves to uniquely identify a specific instantiation of
Draft IP Multicast Routing MIB July 1998
the object. For human convenience, we often use a textual string, the object. For human convenience, we often use a textual string,
termed the descriptor, to refer to the object type. termed the descriptor, to refer to the object type.
Draft IP Multicast Routing MIB November 1997
4. Overview 4. Overview
This MIB module contains one scalar and four tables. The tables are: This MIB module contains one scalar and five tables. The tables are:
(1) the IP Multicast Route Table containing multicast routing (1) the IP Multicast Route Table containing multicast routing
information for IP datagrams sent by particular sources to the IP information for IP datagrams sent by particular sources to the IP
multicast groups known to a router; multicast groups known to a router.
(2) the IP Multicast Routing Next Hop Table containing information on (2) the IP Multicast Routing Next Hop Table containing information on
the next hops for the routing IP multicast datagrams. Each entry the next hops for the routing IP multicast datagrams. Each entry
is one of a list of next hops on outgoing interfaces for particular is one of a list of next hops on outgoing interfaces for particular
sources sending to a particular multicast group address." sources sending to a particular multicast group address.
(3) the IP Multicast Routing Interface Table containing multicast (3) the IP Multicast Routing Interface Table containing multicast
routing information specific to interfaces. routing information specific to interfaces.
(4) the IP Multicast Scoped Boundary Table containing the scoped (4) the IP Multicast Scope Table containing multicast scopes [22].
multicast address boundaries.
Draft IP Multicast Routing MIB November 1997 (5) the IP Multicast Scoped Boundary Table containing the boundaries
configured for multicast scopes.
Draft IP Multicast Routing MIB July 1998
5. Definitions 5. Definitions
IPMROUTE-MIB DEFINITIONS ::= BEGIN IPMROUTE-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, experimental, MODULE-IDENTITY, OBJECT-TYPE, experimental,
Integer32, Counter32, Counter64, Integer32, Counter32, Counter64,
IpAddress, TimeTicks FROM SNMPv2-SMI IpAddress, TimeTicks FROM SNMPv2-SMI
RowStatus FROM SNMPv2-TC DisplayString, RowStatus FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
ipMRouteMIB MODULE-IDENTITY ipMRouteMIB MODULE-IDENTITY
LAST-UPDATED "9711201700Z" LAST-UPDATED "9807231200Z"
ORGANIZATION "IETF IDMR Working Group." ORGANIZATION "IETF IDMR Working Group."
CONTACT-INFO CONTACT-INFO
" Keith McCloghrie " Dave Thaler
Cisco Systems, Inc. Microsoft Corporation
170 West Tasman Drive One Microsoft Way
San Jose, CA 95134-1706 Redmond, WA 48105-6399
US US
Phone: +1 408 526 5260 Phone: +1 425 703 8835
EMail: kzm@cisco.com" EMail: dthaler@microsoft.com"
DESCRIPTION DESCRIPTION
"The MIB module for management of IP Multicast routing, but "The MIB module for management of IP Multicast routing, but
independent of the specific multicast routing protocol in independent of the specific multicast routing protocol in
use." use."
::= { experimental 60 } ::= { experimental 60 }
ipMRouteMIBObjects OBJECT IDENTIFIER ::= { ipMRouteMIB 1 } ipMRouteMIBObjects OBJECT IDENTIFIER ::= { ipMRouteMIB 1 }
ipMRoute OBJECT IDENTIFIER ::= { ipMRouteMIBObjects 1 } ipMRoute OBJECT IDENTIFIER ::= { ipMRouteMIBObjects 1 }
Draft IP Multicast Routing MIB November 1997 Draft IP Multicast Routing MIB July 1998
-- the IP Multicast Routing MIB-Group -- the IP Multicast Routing MIB-Group
-- --
-- a collection of objects providing information about -- a collection of objects providing information about
-- IP Multicast Groups -- IP Multicast Groups
ipMRouteEnable OBJECT-TYPE ipMRouteEnable OBJECT-TYPE
SYNTAX INTEGER { enabled(1), disabled(2) } SYNTAX INTEGER { enabled(1), disabled(2) }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
skipping to change at page 8, line 5 skipping to change at page 8, line 5
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) containing the multicast routing "An entry (conceptual row) containing the multicast routing
information for IP datagrams from a particular source and information for IP datagrams from a particular source and
addressed to a particular IP multicast group address." addressed to a particular IP multicast group address."
INDEX { ipMRouteGroup, INDEX { ipMRouteGroup,
ipMRouteSource, ipMRouteSource,
ipMRouteSourceMask } ipMRouteSourceMask }
::= { ipMRouteTable 1 } ::= { ipMRouteTable 1 }
Draft IP Multicast Routing MIB November 1997 Draft IP Multicast Routing MIB July 1998
IpMRouteEntry ::= SEQUENCE { IpMRouteEntry ::= SEQUENCE {
ipMRouteGroup IpAddress, ipMRouteGroup IpAddress,
ipMRouteSource IpAddress, ipMRouteSource IpAddress,
ipMRouteSourceMask IpAddress, ipMRouteSourceMask IpAddress,
ipMRouteUpstreamNeighbor IpAddress, ipMRouteUpstreamNeighbor IpAddress,
ipMRouteInIfIndex Integer32, ipMRouteInIfIndex Integer32,
ipMRouteUpTime TimeTicks, ipMRouteUpTime TimeTicks,
ipMRouteExpiryTime TimeTicks, ipMRouteExpiryTime TimeTicks,
ipMRoutePkts Counter32, ipMRoutePkts Counter32,
ipMRouteDifferentInIfPackets Counter32, ipMRouteDifferentInIfPackets Counter32,
ipMRouteOctets Counter32, ipMRouteOctets Counter32,
ipMRouteProtocol INTEGER ipMRouteProtocol INTEGER,
ipMRouteRtProto INTEGER,
ipMRouteRtAddress IpAddress,
ipMRouteRtMask IpAddress,
ipMRouteRtType INTEGER
} }
ipMRouteGroup OBJECT-TYPE ipMRouteGroup OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IP multicast group address for which this entry "The IP multicast group address for which this entry
contains multicast routing information." contains multicast routing information."
::= { ipMRouteEntry 1 } ::= { ipMRouteEntry 1 }
skipping to change at page 8, line 48 skipping to change at page 9, line 4
information." information."
::= { ipMRouteEntry 2 } ::= { ipMRouteEntry 2 }
ipMRouteSourceMask OBJECT-TYPE ipMRouteSourceMask OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network mask which when combined with the corresponding "The network mask which when combined with the corresponding
value of ipMRouteSource identifies the sources for which value of ipMRouteSource identifies the sources for which
Draft IP Multicast Routing MIB July 1998
this entry contains multicast routing information." this entry contains multicast routing information."
::= { ipMRouteEntry 3 } ::= { ipMRouteEntry 3 }
ipMRouteUpstreamNeighbor OBJECT-TYPE ipMRouteUpstreamNeighbor OBJECT-TYPE
Draft IP Multicast Routing MIB November 1997
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The address of the upstream neighbor (e.g., RPF neighbor) "The address of the upstream neighbor (e.g., RPF neighbor)
from which IP datagrams from these sources to this multicast from which IP datagrams from these sources to this multicast
address are received, or 0.0.0.0 if the upstream neighbor is address are received, or 0.0.0.0 if the upstream neighbor is
unknown (e.g., in CBT)." unknown (e.g., in CBT)."
::= { ipMRouteEntry 4 } ::= { ipMRouteEntry 4 }
skipping to change at page 9, line 48 skipping to change at page 10, line 5
ipMRouteExpiryTime OBJECT-TYPE ipMRouteExpiryTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum amount of time remaining before this entry will "The minimum amount of time remaining before this entry will
be aged out. The value 0 indicates that the entry is not be aged out. The value 0 indicates that the entry is not
subject to aging." subject to aging."
::= { ipMRouteEntry 7 } ::= { ipMRouteEntry 7 }
Draft IP Multicast Routing MIB July 1998
ipMRoutePkts OBJECT-TYPE ipMRoutePkts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
Draft IP Multicast Routing MIB November 1997
DESCRIPTION DESCRIPTION
"The number of packets which this router has received from "The number of packets which this router has received from
these sources and addressed to this multicast group these sources and addressed to this multicast group
address." address."
::= { ipMRouteEntry 8 } ::= { ipMRouteEntry 8 }
ipMRouteDifferentInIfPackets OBJECT-TYPE ipMRouteDifferentInIfPackets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 10, line 43 skipping to change at page 10, line 47
ipMRouteProtocol OBJECT-TYPE ipMRouteProtocol OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), -- none of the following other(1), -- none of the following
local(2), -- e.g., manually configured local(2), -- e.g., manually configured
netmgmt(3), -- set via net.mgmt protocol netmgmt(3), -- set via net.mgmt protocol
dvmrp(4), dvmrp(4),
mospf(5), mospf(5),
pimSparseDense(6), -- PIMv1, both DM and SM pimSparseDense(6), -- PIMv1, both DM and SM
cbt(7), cbt(7),
pimSparseMode(8), -- PIM-SMv2 pimSparseMode(8), -- PIM-SM
pimDenseMode(9), -- PIM-DMv2 pimDenseMode(9), -- PIM-DM
igmpOnly(10) igmpOnly(10)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
Draft IP Multicast Routing MIB July 1998
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The routing mechanism via which this route was learned." "The multicast routing protocol via which this multicast
forwarding entry was learned. Inclusion of values for
multicast routing protocols is not intended to imply that
those protocols need be supported."
::= { ipMRouteEntry 11 } ::= { ipMRouteEntry 11 }
Draft IP Multicast Routing MIB November 1997 ipMRouteRtProto OBJECT-TYPE
SYNTAX INTEGER {
other (1), -- not specified
local (2), -- local interface
netmgmt (3), -- static route
icmp (4), -- result of ICMP Redirect
-- the following are all dynamic
-- routing protocols
egp (5), -- Exterior Gateway Protocol
ggp (6), -- Gateway-Gateway Protocol
hello (7), -- FuzzBall HelloSpeak
rip (8), -- Berkeley RIP or RIP-II
isIs (9), -- Dual IS-IS
esIs (10), -- ISO 9542
ciscoIgrp (11), -- Cisco IGRP
bbnSpfIgp (12), -- BBN SPF IGP
ospf (13), -- Open Shortest Path First
bgp (14), -- Border Gateway Protocol
idpr (15), -- InterDomain Policy Routing
ciscoEigrp (16), -- Cisco EIGRP
dvmrp (17) -- DVMRP
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The routing mechanism via which the route used for this
multicast forwarding entry was learned. Inclusion of values
for routing protocols is not intended to imply that those
protocols need be supported."
::= { ipMRouteEntry 12 }
ipMRouteRtAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The address portion of the route used for this multicast
Draft IP Multicast Routing MIB July 1998
forwarding entry."
::= { ipMRouteEntry 13 }
ipMRouteRtMask OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The mask associated with the route used for this multicast
forwarding entry."
::= { ipMRouteEntry 14 }
ipMRouteRtType OBJECT-TYPE
SYNTAX INTEGER {
unicast (1), -- Unicast route used in multicast RIB
multicast (2) -- Multicast route
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The reason the given route was placed in the (logical)
multicast RIB. A value of unicast means that the route
would normally be placed only in the unicast RIB, but was
placed in the multicast RIB (instead or in addition) due to
local configuration, such as when running PIM over RIP. A
value of multicast means that the route was explicitly added
to the multicast RIB by the routing protocol, such as DVMRP
or Multiprotocol BGP."
::= { ipMRouteEntry 15 }
Draft IP Multicast Routing MIB July 1998
-- --
-- The IP Multicast Routing Next Hop Table -- The IP Multicast Routing Next Hop Table
-- --
ipMRouteNextHopTable OBJECT-TYPE ipMRouteNextHopTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpMRouteNextHopEntry SYNTAX SEQUENCE OF IpMRouteNextHopEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 12, line 5 skipping to change at page 14, line 5
DESCRIPTION DESCRIPTION
"An entry (conceptual row) in the list of next hops on "An entry (conceptual row) in the list of next hops on
outgoing interfaces to which IP multicast datagrams from outgoing interfaces to which IP multicast datagrams from
particular sources to a IP multicast group address are particular sources to a IP multicast group address are
routed." routed."
INDEX { ipMRouteNextHopGroup, ipMRouteNextHopSource, INDEX { ipMRouteNextHopGroup, ipMRouteNextHopSource,
ipMRouteNextHopSourceMask, ipMRouteNextHopIfIndex, ipMRouteNextHopSourceMask, ipMRouteNextHopIfIndex,
ipMRouteNextHopAddress } ipMRouteNextHopAddress }
::= { ipMRouteNextHopTable 1 } ::= { ipMRouteNextHopTable 1 }
Draft IP Multicast Routing MIB November 1997 Draft IP Multicast Routing MIB July 1998
IpMRouteNextHopEntry ::= SEQUENCE { IpMRouteNextHopEntry ::= SEQUENCE {
ipMRouteNextHopGroup IpAddress, ipMRouteNextHopGroup IpAddress,
ipMRouteNextHopSource IpAddress, ipMRouteNextHopSource IpAddress,
ipMRouteNextHopSourceMask IpAddress, ipMRouteNextHopSourceMask IpAddress,
ipMRouteNextHopIfIndex Integer32, ipMRouteNextHopIfIndex Integer32,
ipMRouteNextHopAddress IpAddress, ipMRouteNextHopAddress IpAddress,
ipMRouteNextHopState INTEGER, ipMRouteNextHopState INTEGER,
ipMRouteNextHopUpTime TimeTicks, ipMRouteNextHopUpTime TimeTicks,
ipMRouteNextHopExpiryTime TimeTicks, ipMRouteNextHopExpiryTime TimeTicks,
skipping to change at page 13, line 5 skipping to change at page 15, line 5
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The network mask which when combined with the corresponding "The network mask which when combined with the corresponding
value of ipMRouteNextHopSource identifies the sources for value of ipMRouteNextHopSource identifies the sources for
which this entry specifies a next hop on an outgoing which this entry specifies a next hop on an outgoing
interface." interface."
::= { ipMRouteNextHopEntry 3 } ::= { ipMRouteNextHopEntry 3 }
Draft IP Multicast Routing MIB November 1997 Draft IP Multicast Routing MIB July 1998
ipMRouteNextHopIfIndex OBJECT-TYPE ipMRouteNextHopIfIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ifIndex value of the interface for the outgoing "The ifIndex value of the interface for the outgoing
interface for this next hop." interface for this next hop."
::= { ipMRouteNextHopEntry 4 } ::= { ipMRouteNextHopEntry 4 }
skipping to change at page 14, line 5 skipping to change at page 16, line 5
DESCRIPTION DESCRIPTION
"The time since the multicast routing information "The time since the multicast routing information
represented by this entry was learned by the router." represented by this entry was learned by the router."
::= { ipMRouteNextHopEntry 7 } ::= { ipMRouteNextHopEntry 7 }
ipMRouteNextHopExpiryTime OBJECT-TYPE ipMRouteNextHopExpiryTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
Draft IP Multicast Routing MIB November 1997 Draft IP Multicast Routing MIB July 1998
DESCRIPTION DESCRIPTION
"The minimum amount of time remaining before this entry will "The minimum amount of time remaining before this entry will
be aged out. The value 0 indicates that the entry is not be aged out. The value 0 indicates that the entry is not
subject to aging." subject to aging."
::= { ipMRouteNextHopEntry 8 } ::= { ipMRouteNextHopEntry 8 }
ipMRouteNextHopClosestMemberHops OBJECT-TYPE ipMRouteNextHopClosestMemberHops OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 14, line 34 skipping to change at page 16, line 34
ipMRouteNextHopProtocol OBJECT-TYPE ipMRouteNextHopProtocol OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), -- none of the following other(1), -- none of the following
local(2), -- e.g., manually configured local(2), -- e.g., manually configured
netmgmt(3), -- set via net.mgmt protocol netmgmt(3), -- set via net.mgmt protocol
dvmrp(4), dvmrp(4),
mospf(5), mospf(5),
pimSparseDense(6), -- PIMv1, both DM and SM pimSparseDense(6), -- PIMv1, both DM and SM
cbt(7), cbt(7),
pimSparseMode(8), -- PIM-SMv2 pimSparseMode(8), -- PIM-SM
pimDenseMode(9), -- PIM-DMv2 pimDenseMode(9), -- PIM-DM
igmpOnly(10) igmpOnly(10)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The routing mechanism via which this next-hop was learned." "The routing mechanism via which this next-hop was learned."
::= { ipMRouteNextHopEntry 10 } ::= { ipMRouteNextHopEntry 10 }
ipMRouteNextHopPkts OBJECT-TYPE ipMRouteNextHopPkts OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of packets which have been forwarded using this "The number of packets which have been forwarded using this
route." route."
::= { ipMRouteNextHopEntry 11 } ::= { ipMRouteNextHopEntry 11 }
Draft IP Multicast Routing MIB November 1997 Draft IP Multicast Routing MIB July 1998
-- --
-- The Multicast Routing Interface Table -- The Multicast Routing Interface Table
-- --
ipMRouteInterfaceTable OBJECT-TYPE ipMRouteInterfaceTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpMRouteInterfaceEntry SYNTAX SEQUENCE OF IpMRouteInterfaceEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 16, line 5 skipping to change at page 18, line 5
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The ifIndex value of the interface for which this entry "The ifIndex value of the interface for which this entry
contains information." contains information."
::= { ipMRouteInterfaceEntry 1 } ::= { ipMRouteInterfaceEntry 1 }
ipMRouteInterfaceTtl OBJECT-TYPE ipMRouteInterfaceTtl OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
Draft IP Multicast Routing MIB November 1997 Draft IP Multicast Routing MIB July 1998
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The datagram TTL threshold for the interface. Any IP "The datagram TTL threshold for the interface. Any IP
multicast datagrams with a TTL less than this threshold will multicast datagrams with a TTL less than this threshold will
not be forwarded out the interface. The default value of 0 not be forwarded out the interface. The default value of 0
means all multicast packets are forwarded out the means all multicast packets are forwarded out the
interface." interface."
::= { ipMRouteInterfaceEntry 2 } ::= { ipMRouteInterfaceEntry 2 }
ipMRouteInterfaceProtocol OBJECT-TYPE ipMRouteInterfaceProtocol OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), -- none of the following other(1), -- none of the following
local(2), -- e.g., static routing local(2), -- e.g., static routing
netmgmt(3), -- set via net.mgmt protocol netmgmt(3), -- set via net.mgmt protocol
dvmrp(4), dvmrp(4),
mospf(5), mospf(5),
pimSparseDense(6), -- PIMv1, both DM and SM pimSparseDense(6), -- PIMv1, both DM and SM
cbt(7), cbt(7),
pimSparseMode(8), -- PIM-SMv2 pimSparseMode(8), -- PIM-SM
pimDenseMode(9), -- PIM-DMv2 pimDenseMode(9), -- PIM-DM
igmpOnly(10) igmpOnly(10)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The routing protocol running on this interface." "The routing protocol running on this interface."
::= { ipMRouteInterfaceEntry 3 } ::= { ipMRouteInterfaceEntry 3 }
ipMRouteInterfaceRateLimit OBJECT-TYPE ipMRouteInterfaceRateLimit OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
skipping to change at page 17, line 5 skipping to change at page 19, line 5
indicates that no rate limiting is done." indicates that no rate limiting is done."
DEFVAL { 0 } DEFVAL { 0 }
::= { ipMRouteInterfaceEntry 4 } ::= { ipMRouteInterfaceEntry 4 }
ipMRouteInterfaceInMcastOctets OBJECT-TYPE ipMRouteInterfaceInMcastOctets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
Draft IP Multicast Routing MIB November 1997 Draft IP Multicast Routing MIB July 1998
"The number of octets of multicast packets that have arrived "The number of octets of multicast packets that have arrived
on the interface." on the interface."
::= { ipMRouteInterfaceEntry 5 } ::= { ipMRouteInterfaceEntry 5 }
ipMRouteInterfaceOutMcastOctets OBJECT-TYPE ipMRouteInterfaceOutMcastOctets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 18, line 5 skipping to change at page 20, line 5
ipMRouteInterfaceHCOutMcastOctets OBJECT-TYPE ipMRouteInterfaceHCOutMcastOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of octets of multicast packets that have been "The number of octets of multicast packets that have been
sent on the interface. This object is a 64-bit version of sent on the interface. This object is a 64-bit version of
ipMRouteInterfaceOutMcastOctets." ipMRouteInterfaceOutMcastOctets."
::= { ipMRouteInterfaceEntry 8 } ::= { ipMRouteInterfaceEntry 8 }
Draft IP Multicast Routing MIB November 1997 Draft IP Multicast Routing MIB July 1998
-- --
-- The IP Multicast Scoped Boundary Table -- The IP Multicast Scoped Boundary Table
-- --
ipMRouteBoundaryTable OBJECT-TYPE ipMRouteBoundaryTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpMRouteBoundaryEntry SYNTAX SEQUENCE OF IpMRouteBoundaryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The (conceptual) table listing the router's scoped "The (conceptual) table listing the router's scoped
multicast address boundaries." multicast address boundaries."
::= { ipMRoute 5 } ::= { ipMRoute 5 }
ipMRouteBoundaryEntry OBJECT-TYPE ipMRouteBoundaryEntry OBJECT-TYPE
SYNTAX IpMRouteBoundaryEntry SYNTAX IpMRouteBoundaryEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry (conceptual row) in the "An entry (conceptual row) in the ipMRouteBoundaryTable
ipMRouteBoundaryTable representing a scoped representing a scoped boundary."
boundary."
INDEX { ipMRouteBoundaryIfIndex, ipMRouteBoundaryAddress, INDEX { ipMRouteBoundaryIfIndex, ipMRouteBoundaryAddress,
ipMRouteBoundaryAddressMask } ipMRouteBoundaryAddressMask }
::= { ipMRouteBoundaryTable 1 } ::= { ipMRouteBoundaryTable 1 }
IpMRouteBoundaryEntry ::= SEQUENCE { IpMRouteBoundaryEntry ::= SEQUENCE {
ipMRouteBoundaryIfIndex Integer32, ipMRouteBoundaryIfIndex Integer32,
ipMRouteBoundaryAddress IpAddress, ipMRouteBoundaryAddress IpAddress,
ipMRouteBoundaryAddressMask IpAddress, ipMRouteBoundaryAddressMask IpAddress,
ipMRouteBoundaryStatus RowStatus ipMRouteBoundaryStatus RowStatus
} }
ipMRouteBoundaryIfIndex OBJECT-TYPE ipMRouteBoundaryIfIndex OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The IfIndex value for the interface to which "The IfIndex value for the interface to which this boundary
this boundary applies. Packets with a applies. Packets with a destination address in the
destination address in the associated associated address/mask range will not be forwarded out this
address/mask range will not be forwarded out this
interface." interface."
::= { ipMRouteBoundaryEntry 1 } ::= { ipMRouteBoundaryEntry 1 }
ipMRouteBoundaryAddress OBJECT-TYPE ipMRouteBoundaryAddress OBJECT-TYPE
Draft IP Multicast Routing MIB November 1997
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
Draft IP Multicast Routing MIB July 1998
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The group address which when combined with the "The group address which when combined with the
corresponding value of ipMRouteBoundaryAddressMask corresponding value of ipMRouteBoundaryAddressMask
identifies the group range for which the scoped identifies the group range for which the scoped boundary
boundary exists. Scoped addresses must come from exists. Scoped addresses must come from the range
the range 239.x.x.x." 239.x.x.x."
::= { ipMRouteBoundaryEntry 2 } ::= { ipMRouteBoundaryEntry 2 }
ipMRouteBoundaryAddressMask OBJECT-TYPE ipMRouteBoundaryAddressMask OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The group address mask which when combined with "The group address mask which when combined with the
the corresponding value of ipMRouteBoundaryAddress corresponding value of ipMRouteBoundaryAddress identifies
identifies the group range for which the scoped the group range for which the scoped boundary exists."
boundary exists."
::= { ipMRouteBoundaryEntry 3 } ::= { ipMRouteBoundaryEntry 3 }
ipMRouteBoundaryStatus OBJECT-TYPE ipMRouteBoundaryStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this row, by which new entries may be "The status of this row, by which new entries may be
created, or old entries deleted from this table." created, or old entries deleted from this table. Adding an
entry in this from this table should have the additional
effect of adding a row for the prefix in the
ipMRouteScopeTable if no such already exists."
::= { ipMRouteBoundaryEntry 4 } ::= { ipMRouteBoundaryEntry 4 }
Draft IP Multicast Routing MIB November 1997 --
-- The IP Multicast Scope Table
--
ipMRouteScopeTable OBJECT-TYPE
SYNTAX SEQUENCE OF IpMRouteScopeEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The (conceptual) table listing the multicast scopes for
which the router has scope boundaries."
::= { ipMRoute 6 }
Draft IP Multicast Routing MIB July 1998
ipMRouteScopeEntry OBJECT-TYPE
SYNTAX IpMRouteScopeEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry (conceptual row) in the ipMRouteScopeTable
representing a multicast scope."
INDEX { ipMRouteScopeAddress,
ipMRouteScopeAddressMask }
::= { ipMRouteScopeTable 1 }
IpMRouteScopeEntry ::= SEQUENCE {
ipMRouteScopeAddress IpAddress,
ipMRouteScopeAddressMask IpAddress,
ipMRouteScopeName DisplayString,
ipMRouteScopeStatus RowStatus
}
ipMRouteScopeAddress OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The group address which when combined with the
corresponding value of ipMRouteScopeAddressMask identifies
the group range associated with the multicast scope. Scoped
addresses must come from the range 239.x.x.x."
::= { ipMRouteScopeEntry 1 }
ipMRouteScopeAddressMask OBJECT-TYPE
SYNTAX IpAddress
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"The group address mask which when combined with the
corresponding value of ipMRouteScopeAddress identifies the
group range associated with the multicast scope."
::= { ipMRouteScopeEntry 2 }
ipMRouteScopeName OBJECT-TYPE
SYNTAX DisplayString (SIZE (1..255))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The textual name associated with the multicast scope. The
Draft IP Multicast Routing MIB July 1998
value of this object should be suitable for displaying to
end-users, such as when allocating a multicast address in
this scope. When no name is specified, the default value of
this object should be the string 239.x.x.x/y with x and y
replaced appropriately to describe the address and mask
length associated with the scope."
::= { ipMRouteScopeEntry 3 }
ipMRouteScopeStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The status of this row, by which new entries may be
created, or old entries deleted from this table. Deleting
an entry from this table should have the additional effect
of removing all boundaries for this scope from the
ipMRouteBoundaryTable."
::= { ipMRouteScopeEntry 4 }
Draft IP Multicast Routing MIB July 1998
-- conformance information -- conformance information
ipMRouteMIBConformance ipMRouteMIBConformance
OBJECT IDENTIFIER ::= { ipMRouteMIB 2 } OBJECT IDENTIFIER ::= { ipMRouteMIB 2 }
ipMRouteMIBCompliances ipMRouteMIBCompliances
OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 1 } OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 1 }
ipMRouteMIBGroups OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 2 } ipMRouteMIBGroups OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 2 }
-- compliance statements -- compliance statements
ipMRouteMIBCompliance MODULE-COMPLIANCE ipMRouteMIBCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for the IP Multicast MIB." "The compliance statement for the IP Multicast MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { ipMRouteMIBBasicGroup } MANDATORY-GROUPS { ipMRouteMIBBasicGroup,
ipMRouteMIBRouteGroup}
GROUP ipMRouteMIBBoundaryGroup GROUP ipMRouteMIBBoundaryGroup
DESCRIPTION DESCRIPTION
"This group is only required to support management of "This group is only required to support management of scoped
scoped multicast address boundaries." multicast address boundaries."
OBJECT ipMRouteBoundaryStatus OBJECT ipMRouteBoundaryStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT ipMRouteScopeStatus
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
GROUP ipMRouteMIBHCInterfaceGroup GROUP ipMRouteMIBHCInterfaceGroup
DESCRIPTION DESCRIPTION
"This group is mandatory only for those network "This group is mandatory only for those network interfaces
interfaces for which the value of the corresponding for which the value of the corresponding instance of ifSpeed
instance of ifSpeed is greater than 20,000,000 is greater than 20,000,000 bits/second."
bits/second."
::= { ipMRouteMIBCompliances 1 } ::= { ipMRouteMIBCompliances 1 }
-- units of conformance -- units of conformance
Draft IP Multicast Routing MIB July 1998
ipMRouteMIBBasicGroup OBJECT-GROUP ipMRouteMIBBasicGroup OBJECT-GROUP
OBJECTS { ipMRouteEnable, ipMRouteUpstreamNeighbor, OBJECTS { ipMRouteEnable, ipMRouteUpstreamNeighbor,
ipMRouteInIfIndex, ipMRouteInIfIndex,
ipMRouteUpTime, ipMRouteExpiryTime, ipMRouteUpTime, ipMRouteExpiryTime,
ipMRoutePkts, ipMRouteDifferentInIfPackets, ipMRoutePkts, ipMRouteDifferentInIfPackets,
Draft IP Multicast Routing MIB November 1997
ipMRouteOctets, ipMRouteOctets,
ipMRouteNextHopState, ipMRouteNextHopState,
ipMRouteNextHopUpTime, ipMRouteNextHopUpTime,
ipMRouteNextHopExpiryTime, ipMRouteNextHopExpiryTime,
ipMRouteNextHopProtocol, ipMRouteNextHopProtocol,
ipMRouteNextHopPkts, ipMRouteNextHopPkts,
ipMRouteInterfaceTtl, ipMRouteInterfaceTtl,
ipMRouteInterfaceProtocol, ipMRouteInterfaceRateLimit, ipMRouteInterfaceProtocol, ipMRouteInterfaceRateLimit,
ipMRouteInterfaceInMcastOctets, ipMRouteInterfaceInMcastOctets,
ipMRouteInterfaceOutMcastOctets, ipMRouteInterfaceOutMcastOctets,
ipMRouteProtocol ipMRouteProtocol
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects to support basic management of "A collection of objects to support basic management of IP
IP Multicast routing." Multicast routing."
::= { ipMRouteMIBGroups 1 } ::= { ipMRouteMIBGroups 1 }
ipMRouteMIBHopCountGroup OBJECT-GROUP ipMRouteMIBHopCountGroup OBJECT-GROUP
OBJECTS { ipMRouteNextHopClosestMemberHops } OBJECTS { ipMRouteNextHopClosestMemberHops }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects to support management of the use "A collection of objects to support management of the use of
of hop counts in IP Multicast routing." hop counts in IP Multicast routing."
::= { ipMRouteMIBGroups 2 } ::= { ipMRouteMIBGroups 2 }
ipMRouteMIBBoundaryGroup OBJECT-GROUP ipMRouteMIBBoundaryGroup OBJECT-GROUP
OBJECTS { ipMRouteBoundaryStatus } OBJECTS { ipMRouteBoundaryStatus, ipMRouteScopeName,
ipMRouteScopeStatus }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects to support management of scoped "A collection of objects to support management of scoped
multicast address boundaries." multicast address boundaries."
::= { ipMRouteMIBGroups 3 } ::= { ipMRouteMIBGroups 3 }
ipMRouteMIBPktsOutGroup OBJECT-GROUP ipMRouteMIBPktsOutGroup OBJECT-GROUP
OBJECTS { ipMRouteNextHopPkts } OBJECTS { ipMRouteNextHopPkts }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects to support management of packet "A collection of objects to support management of packet
Draft IP Multicast Routing MIB July 1998
counters for each outgoing interface entry of a route." counters for each outgoing interface entry of a route."
::= { ipMRouteMIBGroups 4 } ::= { ipMRouteMIBGroups 4 }
ipMRouteMIBHCInterfaceGroup OBJECT-GROUP ipMRouteMIBHCInterfaceGroup OBJECT-GROUP
OBJECTS { ipMRouteInterfaceHCInMcastOctets, OBJECTS { ipMRouteInterfaceHCInMcastOctets,
ipMRouteInterfaceHCOutMcastOctets } ipMRouteInterfaceHCOutMcastOctets }
Draft IP Multicast Routing MIB November 1997
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing information specific to "A collection of objects providing information specific to
high speed (greater than 20,000,000 bits/second) network high speed (greater than 20,000,000 bits/second) network
interfaces." interfaces."
::= { ipMRouteMIBGroups 5 } ::= { ipMRouteMIBGroups 5 }
ipMRouteMIBRouteGroup OBJECT-GROUP
OBJECTS { ipMRouteRtProto, ipMRouteRtAddress,
ipMRouteRtMask, ipMRouteRtType }
STATUS current
DESCRIPTION
"A collection of objects providing information on the
relationship between multicast routing information, and the
IP Forwarding Table."
::= { ipMRouteMIBGroups 6 }
END END
Draft IP Multicast Routing MIB November 1997 Draft IP Multicast Routing MIB July 1998
6. Acknowledgements 6. Security Considerations
This MIB contains readable objects whose values provide information
related to multicast routing, including information on what machines are
sending to which groups. There are also a number of objects that have a
MAX-ACCESS clause of read-write and/or read-create, such as those which
allow an administrator to configure multicast boundaries.
While unauthorized access to the readable objects is relatively
innocuous, unauthorized access to the write-able objects could cause a
denial of service, or could cause wider distribution of packets intended
only for local distribution. Hence, the support for SET operations in a
non-secure environment without proper protection can have a negative
effect on network operations.
SNMPv1 by itself is such an insecure environment. Even if the network
itself is secure (for example by using IPSec), even then, there is no
control as to who on the secure network is allowed to access and SET
(change/create/delete) the objects in this MIB.
It is recommended that the implementers consider the security features
as provided by the SNMPv3 framework. Specifically, the use of the
User-based Security Model RFC 2274 [12] and the View-based Access
Control Model RFC 2275 [15] is recommended.
It is then a customer/user responsibility to ensure that the SNMP entity
giving access to this MIB, is properly configured to give access to
those objects only to those principals (users) that have legitimate
rights to access them.
7. Acknowledgements
This MIB module was updated based on feedback from the IETF's Inter- This MIB module was updated based on feedback from the IETF's Inter-
Domain Multicast Routing (IDMR) Working Group. Domain Multicast Routing (IDMR) Working Group.
7. References 8. Authors' Address
[1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and Keith McCloghrie
S. Waldbusser, "Structure of Management Information for version 2 cisco Systems, Inc.
of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 170 West Tasman Drive
San Jose, CA 95134-1706
Draft IP Multicast Routing MIB July 1998
Phone: +1 408 526 5260
EMail: kzm@cisco.com
Dino Farinacci
cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
Phone: +1 408 526 4696
EMail: dino@cisco.com
Dave Thaler
Microsoft Corporation
One Microsoft Way
Redmond, WA 48105-6399
Phone: +1 425 703 8835
EMail: dthaler@microsoft.com
9. References
[1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for
Describing SNMP Management Frameworks", RFC 2271, Cabletron
Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research,
January 1998.
[2] Rose, M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", RFC 1155,
Performance Systems International, Hughes LAN Systems, May 1990.
[3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212,
Performance Systems International, Hughes LAN Systems, March 1991.
[4] M. Rose, "A Convention for Defining Traps for use with the SNMP",
RFC 1215, Performance Systems International, March 1991.
[5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure
of Management Information for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco
Systems, Inc., Dover Beach Consulting, Inc., International Network
Services, January 1996.
[6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual
Conventions for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc.,
Draft IP Multicast Routing MIB July 1998
Dover Beach Consulting, Inc., International Network Services,
January 1996. January 1996.
[2] McCloghrie, K., and M. Rose, Editors, "Management Information Base [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance
for Network Management of TCP/IP-based internets: MIB-II", STD 17, Statements for Version 2 of the Simple Network Management Protocol
RFC 1213, March 1991. (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, Inc.,
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network
Management Protocol", RFC 1157, May 1990. Management Protocol", RFC 1157, SNMP Research, Performance Systems
International, Performance Systems International, MIT Laboratory
for Computer Science, May 1990.
[4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
S. Waldbusser, "Protocol Operations for version 2 of the Simple "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research,
Network Management Protocol (SNMPv2)", RFC 1905, January 1996. Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc.,
International Network Services, January 1996.
[5] Deering, S., "Multicast Routing in a Datagram Internetwork", PhD [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport
Mappings for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc.,
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems,
Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998.
[12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for
version 3 of the Simple Network Management Protocol (SNMPv3)", RFC
2274, IBM T. J. Watson Research, January 1998.
[13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
Operations for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc.,
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[14] Levi, D., Meyer, P., and B. Stewart, "MPv3 Applications", RFC 2273,
SNMP Research, Inc., Secure Computing Corporation, Cisco Systems,
January 1998.
Draft IP Multicast Routing MIB July 1998
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc.,
Cisco Systems, Inc., January 1998.
[16] Deering, S., "Multicast Routing in a Datagram Internetwork", PhD
thesis, Electrical Engineering Dept., Stanford University, December thesis, Electrical Engineering Dept., Stanford University, December
1991. 1991.
[6] Waitzman, D., Partridge, C., and S.E. Deering, "Distance Vector [17] Waitzman, D., Partridge, C., and S.E. Deering, "Distance Vector
Multicast Routing Protocol", RFC 1075, November 1988. Multicast Routing Protocol", RFC 1075, November 1988.
[7] Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering, S., [18] Estrin, D., Farinacci, D., Helmy, A., Thaler, D., Deering, S.,
Handley, M., Jacobson, V., Liu, C., Sharma, P., and L. Wei, Handley, M., Jacobson, V., Liu, C., Sharma, P., and L. Wei,
"Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol "Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol
Specification", RFC 2117, June 1997. Specification", RFC 2362, June 1998.
[8] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Helmy, A., [19] Deering, S., Estrin, D., Farinacci, D., Jacobson, V., Helmy, A.,
and L. Wei, "Protocol Independent Multicast Version 2, Dense Mode and L. Wei, "Protocol Independent Multicast Version 2, Dense Mode
Specification". May 1997. Specification". May 1997.
[9] Moy, J., "Multicast Extensions to OSPF", RFC 1584, March 1994. [20] Moy, J., "Multicast Extensions to OSPF", RFC 1584, March 1994.
[10] Ballardie, A. J., "Core Based Trees (CBT version 2) Multicast [21] Ballardie, A. J., "Core Based Trees (CBT version 2) Multicast
Routing", RFC 2189, September 1997. Routing", RFC 2189, September 1997.
Draft IP Multicast Routing MIB November 1997 [22] Meyer, D., "Administratively Scoped IP Multicast", RFC 2365, July
1998.
8. Security Considerations
Security issues are not discussed in this memo. Draft IP Multicast Routing MIB July 1998
9. Authors' Address 10. Full Copyright Statement
Keith McCloghrie Copyright (C) The Internet Society (1998). All Rights Reserved.
cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
Phone: +1 408 526 5260
EMail: kzm@cisco.com
Dino Farinacci This document and translations of it may be copied and furnished to
cisco Systems, Inc. others, and derivative works that comment on or otherwise explain it or
170 West Tasman Drive assist in its implmentation may be prepared, copied, published and
San Jose, CA 95134-1706 distributed, in whole or in part, without restriction of any kind,
Phone: +1 408 526 4696 provided that the above copyright notice and this paragraph are included
EMail: dino@cisco.com on all such copies and derivative works. However, this document itself
may not be modified in any way, such as by removing the copyright notice
or references to the Internet Society or other Internet organizations,
except as needed for the purpose of developing Internet standards in
which case the procedures for copyrights defined in the Internet
Standards process must be followed, or as required to translate it into
languages other than English.
Dave Thaler The limited permissions granted above are perpetual and will not be
Department of Electrical Engineering and Computer Science revoked by the Internet Society or its successors or assigns.
University of Michigan
1301 Beal Ave.
Ann Arbor, MI 48109-2122
Phone: +1 313 763 5243
EMail: thalerd@eecs.umich.edu
Draft IP Multicast Routing MIB November 1997 This document and the information contained herein is provided on an "AS
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE."
Table of Contents Table of Contents
1 Introduction .................................................... 1 1 Introduction .................................................... 1
2 Revision History ................................................ 2 2 Revision History ................................................ 2
3 The SNMP Network Management Framework ........................... 4 3 The SNMP Management Framework ................................... 3
3.1 Object Definitions ............................................ 4 3.1 Object Definitions ............................................ 4
4 Overview ........................................................ 5 4 Overview ........................................................ 5
5 Definitions ..................................................... 6 5 Definitions ..................................................... 6
6 Acknowledgements ................................................ 23 6 Security Considerations ......................................... 27
7 References ...................................................... 23 7 Acknowledgements ................................................ 27
8 Security Considerations ......................................... 24 8 Authors' Address ................................................ 27
9 Authors' Address ................................................ 24 9 References ...................................................... 28
10 Full Copyright Statement ....................................... 31
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/