home *** CD-ROM | disk | FTP | other *** search
Text File | 1997-03-27 | 31.6 KB | 1,353 lines |
-
-
- IDMR Working Group Keith McCloghrie
- INTERNET-DRAFT Dino Farinacci
- Expires September 1997 cisco Systems
- Dave Thaler
- University of Michigan
- 25 March 1997
-
-
-
- IP Multicast Routing MIB
- <draft-ietf-idmr-multicast-routmib-05.txt>
-
-
-
-
-
- Status of this Memo
-
- This document is an Internet Draft. Internet Drafts are working
- documents of the Internet Engineering Task Force (IETF), its Areas, and
- its Working Groups. Note that other groups may also distribute working
- documents as Internet Drafts.
-
- Internet Drafts are valid for a maximum of six months and may be
- updated, replaced, or obsoleted by other documents at any time. It is
- inappropriate to use Internet Drafts as reference material or to cite
- them other than as a "work in progress".
-
-
- 1. Introduction
-
- This memo defines an experimental 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 IP Multicast Routing [5], independent of the specific multicast
- routing protocol [6,7,8,9,10] in use. Managed objects specific to
- particular multicast routing protocols are specified elsewhere.
-
-
-
-
-
-
-
-
-
-
-
-
-
- Expires September 1997 [Page 1]
-
-
-
-
-
- Draft IP Multicast Routing MIB March 1997
-
-
- 2. Revision History
-
- A record of changes which will be removed before publication.
-
- 26 March
-
- (1) added ipMRouteInterfaceProtocol.
-
- added protocol values for PIM-DM, PIM-SM, and IGMP-only links.
-
- 26 November
-
- (1) moved ipMRouteNextHopPkts to its own conformance group.
-
- 9 June
-
- (1) added the ipMRouteBoundaryTable and ipMRouteNextHopPkts.
-
- (2) updated references, etc.
-
- 28 March
-
- (1) renamed ipMRouteNextHopClosestMember to
- ipMRouteNextHopClosestMemberHops, and ipMRouteDifferentInIfIndexes
- to ipMRouteDifferentInIfPacket.
-
- 26 February
-
- (1) added ipMRouteNextHopAddress as a INDEX variable for the
- ipMRouteNextHopTable.
-
- (2) added ipMRouteNextHopClosestMember and ipMRouteNextHopProtocol
-
- (3) added ipMRouteMIBHopCountGroup.
-
- (4) specified that an expiry-time of zero means that an entry is not
- subject to aging.
-
- (5) added references for MOSPF and CBT.
-
- 4 February
-
- (1) removed ipMRouteOutList
-
-
-
-
-
-
-
- Expires September 1997 [Page 2]
-
-
-
-
-
- Draft IP Multicast Routing MIB March 1997
-
-
- (2) Modified ipMRouteNextHopTable to be INDEX-ed by
- ipMRouteNextHopGroup, ipMRouteNextHopSource,
- ipMRouteNextHopSourceMask, and ipMRouteNextHopIfIndex.
-
- (3) added ipMRouteProtocol
-
- (4) replaced "RPF" terminology with "Upstream neighbor".
-
- 15 July - initial version.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Expires September 1997 [Page 3]
-
-
-
-
-
- Draft IP Multicast Routing MIB March 1997
-
-
- 3. The SNMP Network Management Framework
-
- The SNMP Network Management Framework presently consists of three major
- components. They are:
-
- o RFC 1902 [1] which defines the SMI, the mechanisms used for
- describing and naming objects for the purpose of management.
-
- o STD 17, RFC 1213 [2] defines MIB-II, the core set of managed
- objects for the Internet suite of protocols.
-
- o RFC 1157 [3] and RFC 1905 [4] which define two versions of the
- protocol used for network access to managed objects.
-
- The Framework permits new objects to be defined for the purpose of
- experimentation and evaluation.
-
-
- 3.1. Object Definitions
-
- Managed objects are accessed via a virtual information store, termed the
- Management Information Base or MIB. Objects in the MIB are defined
- 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,
- an administratively assigned name. The object type together with an
- object instance serves to uniquely identify a specific instantiation of
- the object. For human convenience, we often use a textual string,
- termed the descriptor, to refer to the object type.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Expires September 1997 [Page 4]
-
-
-
-
-
- Draft IP Multicast Routing MIB March 1997
-
-
- 4. Overview
-
- This MIB module contains one scalar and four tables. The tables are:
-
- (1) the IP Multicast Route Table containing multicast routing
- information for IP datagrams sent by particular sources to the IP
- multicast groups known to a router;
-
- (2) the IP Multicast Routing Next Hop Table containing information on
- the next hops for the routing IP multicast datagrams. Each entry
- is one of a list of next hops on outgoing interfaces for particular
- sources sending to a particular multicast group address."
-
- (3) the IP Multicast Routing Interface Table containing multicast
- routing information specific to interfaces.
-
- (4) the IP Multicast Scoped Boundary Table containing the scoped
- multicast address boundaries.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Expires September 1997 [Page 5]
-
-
-
-
-
- Draft IP Multicast Routing MIB March 1997
-
-
- 5. Definitions
-
- IPMROUTE-MIB DEFINITIONS ::= BEGIN
-
- IMPORTS
- MODULE-IDENTITY, OBJECT-TYPE, experimental,
- Integer32, Counter32,
- IpAddress, TimeTicks FROM SNMPv2-SMI
- RowStatus FROM SNMPv2-TC
- MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF;
-
- ipMRouteMIB MODULE-IDENTITY
- LAST-UPDATED "9703261620Z"
- ORGANIZATION "IETF IDMR Working Group."
- CONTACT-INFO
- " Keith McCloghrie
- Cisco Systems, Inc.
- 170 West Tasman Drive
- San Jose, CA 95134-1706
- US
-
- Phone: +1 408 526 5260
- EMail: kzm@cisco.com"
- DESCRIPTION
- "The MIB module for management of IP Multicast routing, but
- independent of the specific multicast routing protocol in
- use."
- ::= { experimental 60 }
-
-
- ipMRouteMIBObjects OBJECT IDENTIFIER ::= { ipMRouteMIB 1 }
-
- ipMRoute OBJECT IDENTIFIER ::= { ipMRouteMIBObjects 1 }
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Expires September 1997 [Page 6]
-
-
-
-
-
- Draft IP Multicast Routing MIB March 1997
-
-
- -- the IP Multicast Routing MIB-Group
- --
- -- a collection of objects providing information about
- -- IP Multicast Groups
-
-
- ipMRouteEnable OBJECT-TYPE
- SYNTAX INTEGER { enabled(1), disabled(2) }
- MAX-ACCESS read-write
- STATUS current
- DESCRIPTION
- "The enabled status of IP Multicast routing on this router."
- ::= { ipMRoute 1 }
-
-
- ipMRouteTable OBJECT-TYPE
- SYNTAX SEQUENCE OF IpMRouteEntry
- MAX-ACCESS not-accessible
- STATUS current
- DESCRIPTION
- "The (conceptual) table containing multicast routing
- information for IP datagrams sent by particular sources to
- the IP multicast groups known to this router."
- ::= { ipMRoute 2 }
-
- ipMRouteEntry OBJECT-TYPE
- SYNTAX IpMRouteEntry
- MAX-ACCESS not-accessible
- STATUS current
- DESCRIPTION
- "An entry (conceptual row) containing the multicast routing
- information for IP datagrams from a particular source and
- addressed to a particular IP multicast group address."
- INDEX { ipMRouteGroup,
- ipMRouteSource,
- ipMRouteSourceMask }
- ::= { ipMRouteTable 1 }
-
-
-
-
-
-
-
-
-
-
-
-
-
- Expires September 1997 [Page 7]
-
-
-
-
-
- Draft IP Multicast Routing MIB March 1997
-
-
- IpMRouteEntry ::= SEQUENCE {
- ipMRouteGroup IpAddress,
- ipMRouteSource IpAddress,
- ipMRouteSourceMask IpAddress,
- ipMRouteUpstreamNeighbor IpAddress,
- ipMRouteInIfIndex Integer32,
- ipMRouteUpTime TimeTicks,
- ipMRouteExpiryTime TimeTicks,
- ipMRoutePkts Counter32,
- ipMRouteDifferentInIfPackets Counter32,
- ipMRouteOctets Counter32,
- ipMRouteProtocol INTEGER
- }
-
- ipMRouteGroup OBJECT-TYPE
- SYNTAX IpAddress
- MAX-ACCESS not-accessible
- STATUS current
- DESCRIPTION
- "The IP multicast group address for which this entry
- contains multicast routing information."
- ::= { ipMRouteEntry 1 }
-
- ipMRouteSource OBJECT-TYPE
- SYNTAX IpAddress
- MAX-ACCESS not-accessible
- STATUS current
- DESCRIPTION
- "The network address which when combined with the
- corresponding value of ipMRouteSourceMask identifies the
- sources for which this entry contains multicast routing
- information."
- ::= { ipMRouteEntry 2 }
-
- ipMRouteSourceMask OBJECT-TYPE
- SYNTAX IpAddress
- MAX-ACCESS not-accessible
- STATUS current
- DESCRIPTION
- "The network mask which when combined with the corresponding
- value of ipMRouteSource identifies the sources for which
- this entry contains multicast routing information."
- ::= { ipMRouteEntry 3 }
-
- ipMRouteUpstreamNeighbor OBJECT-TYPE
-
-
-
-
-
- Expires September 1997 [Page 8]
-
-
-
-
-
- Draft IP Multicast Routing MIB March 1997
-
-
- SYNTAX IpAddress
- MAX-ACCESS read-only
- STATUS current
- DESCRIPTION
- "The address of the upstream neighbor (e.g., RPF neighbor)
- from which IP datagrams from these sources to this multicast
- address are received."
- ::= { ipMRouteEntry 4 }
-
- ipMRouteInIfIndex OBJECT-TYPE
- SYNTAX Integer32
- MAX-ACCESS read-only
- STATUS current
- DESCRIPTION
- "The value of ifIndex for the interface on which IP
- datagrams sent by these sources to this multicast address
- are received."
- ::= { ipMRouteEntry 5 }
-
- ipMRouteUpTime OBJECT-TYPE
- SYNTAX TimeTicks
- MAX-ACCESS read-only
- STATUS current
- DESCRIPTION
- "The time since the multicast routing information
- represented by this entry was learned by the router."
- ::= { ipMRouteEntry 6 }
-
- ipMRouteExpiryTime OBJECT-TYPE
- SYNTAX TimeTicks
- MAX-ACCESS read-only
- STATUS current
- DESCRIPTION
- "The minimum amount of time remaining before this entry will
- be aged out. The value 0 indicates that the entry is not
- subject to aging."
- ::= { ipMRouteEntry 7 }
-
- ipMRoutePkts OBJECT-TYPE
- SYNTAX Counter32
- MAX-ACCESS read-only
- STATUS current
- DESCRIPTION
- "The number of packets which this router has received from
- these sources and addressed to this multicast group
-
-
-
-
-
- Expires September 1997 [Page 9]
-
-
-
-
-
- Draft IP Multicast Routing MIB March 1997
-
-
- address."
- ::= { ipMRouteEntry 8 }
-
- ipMRouteDifferentInIfPackets OBJECT-TYPE
- SYNTAX Counter32
- MAX-ACCESS read-only
- STATUS current
- DESCRIPTION
- "The number of packets which this router has received from
- these sources and addressed to this multicast group address,
- which were not received from the interface indicated by
- ipMRouteInIfIndex."
- ::= { ipMRouteEntry 9 }
-
- ipMRouteOctets OBJECT-TYPE
- SYNTAX Counter32
- MAX-ACCESS read-only
- STATUS current
- DESCRIPTION
- "The number of octets contained in IP datagrams which were
- received from these sources and addressed to this multicast
- group address, and which were forwarded by this router."
- ::= { ipMRouteEntry 10 }
-
- ipMRouteProtocol OBJECT-TYPE
- SYNTAX INTEGER {
- other(1), -- none of the following
- local(2), -- e.g., manually configured
- netmgmt(3), -- set via net.mgmt protocol
- dvmrp(4),
- mospf(5),
- pimSparseDense(6), -- PIMv1, both DM and SM
- cbt(7),
- pimSparseMode(8), -- PIM-SMv2
- pimDenseMode(9), -- PIM-DMv2
- igmpOnly(10)
- }
- MAX-ACCESS read-only
- STATUS current
- DESCRIPTION
- "The routing mechanism via which this route was learned."
- ::= { ipMRouteEntry 11 }
-
-
-
-
-
-
-
-
- Expires September 1997 [Page 10]
-
-
-
-
-
- Draft IP Multicast Routing MIB March 1997
-
-
- --
- -- The IP Multicast Routing Next Hop Table
- --
-
- ipMRouteNextHopTable OBJECT-TYPE
- SYNTAX SEQUENCE OF IpMRouteNextHopEntry
- MAX-ACCESS not-accessible
- STATUS current
- DESCRIPTION
- "The (conceptual) table containing information on the next
- hops on outgoing interfaces for routing IP multicast
- datagrams. Each entry is one of a list of next hops on
- outgoing interfaces for particular sources sending to a
- particular multicast group address."
- ::= { ipMRoute 3 }
-
- ipMRouteNextHopEntry OBJECT-TYPE
- SYNTAX IpMRouteNextHopEntry
- MAX-ACCESS not-accessible
- STATUS current
- DESCRIPTION
- "An entry (conceptual row) in the list of next hops on
- outgoing interfaces to which IP multicast datagrams from
- particular sources to a IP multicast group address are
- routed."
- INDEX { ipMRouteNextHopGroup, ipMRouteNextHopSource,
- ipMRouteNextHopSourceMask, ipMRouteNextHopIfIndex,
- ipMRouteNextHopAddress }
- ::= { ipMRouteNextHopTable 1 }
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Expires September 1997 [Page 11]
-
-
-
-
-
- Draft IP Multicast Routing MIB March 1997
-
-
- IpMRouteNextHopEntry ::= SEQUENCE {
- ipMRouteNextHopGroup IpAddress,
- ipMRouteNextHopSource IpAddress,
- ipMRouteNextHopSourceMask IpAddress,
- ipMRouteNextHopIfIndex Integer32,
- ipMRouteNextHopAddress IpAddress,
- ipMRouteNextHopState INTEGER,
- ipMRouteNextHopUpTime TimeTicks,
- ipMRouteNextHopExpiryTime TimeTicks,
- ipMRouteNextHopClosestMemberHops Integer32,
- ipMRouteNextHopProtocol INTEGER,
- ipMRouteNextHopPkts Counter32
- }
-
- ipMRouteNextHopGroup OBJECT-TYPE
- SYNTAX IpAddress
- MAX-ACCESS not-accessible
- STATUS current
- DESCRIPTION
- "The IP multicast group for which this entry specifies a
- next hop on an outgoing interface."
- ::= { ipMRouteNextHopEntry 1 }
-
- ipMRouteNextHopSource OBJECT-TYPE
- SYNTAX IpAddress
- MAX-ACCESS not-accessible
- STATUS current
- DESCRIPTION
- "The network address which when combined with the
- corresponding value of ipMRouteNextHopSourceMask identifies
- the sources for which this entry specifies a next hop on an
- outgoing interface."
- ::= { ipMRouteNextHopEntry 2 }
-
- ipMRouteNextHopSourceMask OBJECT-TYPE
- SYNTAX IpAddress
- MAX-ACCESS not-accessible
- STATUS current
- DESCRIPTION
- "The network mask which when combined with the corresponding
- value of ipMRouteNextHopSource identifies the sources for
- which this entry specifies a next hop on an outgoing
- interface."
- ::= { ipMRouteNextHopEntry 3 }
-
-
-
-
-
-
- Expires September 1997 [Page 12]
-
-
-
-
-
- Draft IP Multicast Routing MIB March 1997
-
-
- ipMRouteNextHopIfIndex OBJECT-TYPE
- SYNTAX Integer32
- MAX-ACCESS not-accessible
- STATUS current
- DESCRIPTION
- "The ifIndex value of the interface for the outgoing
- interface for this next hop."
- ::= { ipMRouteNextHopEntry 4 }
-
- ipMRouteNextHopAddress OBJECT-TYPE
- SYNTAX IpAddress
- MAX-ACCESS not-accessible
- STATUS current
- DESCRIPTION
- "The address of the next hop."
- ::= { ipMRouteNextHopEntry 5 }
-
- ipMRouteNextHopState OBJECT-TYPE
- SYNTAX INTEGER { pruned(1), forwarding(2) }
- MAX-ACCESS read-only
- STATUS current
- DESCRIPTION
- "An indication of whether the outgoing interface and next
- hop represented by this entry is currently being used to
- forward IP datagrams. The value 'forwarding' indicates it
- is currently being used; the value 'pruned' indicates it is
- not."
- ::= { ipMRouteNextHopEntry 6 }
-
- ipMRouteNextHopUpTime OBJECT-TYPE
- SYNTAX TimeTicks
- MAX-ACCESS read-only
- STATUS current
- DESCRIPTION
- "The time since the multicast routing information
- represented by this entry was learned by the router."
- ::= { ipMRouteNextHopEntry 7 }
-
- ipMRouteNextHopExpiryTime OBJECT-TYPE
- SYNTAX TimeTicks
- MAX-ACCESS read-only
- STATUS current
- DESCRIPTION
- "The minimum amount of time remaining before this entry will
- be aged out. The value 0 indicates that the entry is not
-
-
-
-
-
- Expires September 1997 [Page 13]
-
-
-
-
-
- Draft IP Multicast Routing MIB March 1997
-
-
- subject to aging."
- ::= { ipMRouteNextHopEntry 8 }
-
- ipMRouteNextHopClosestMemberHops OBJECT-TYPE
- SYNTAX Integer32
- MAX-ACCESS read-only
- STATUS current
- DESCRIPTION
- "The minimum number of hops between this router and any
- member of this IP multicast group reached via this next hop
- on this outgoing interface. Any IP multicast datagrams for
- the group which have a TTL less than this number of hops
- will not be forwarded to this next hop."
- ::= { ipMRouteNextHopEntry 9 }
-
- ipMRouteNextHopProtocol OBJECT-TYPE
- SYNTAX INTEGER {
- other(1), -- none of the following
- local(2), -- e.g., manually configured
- netmgmt(3), -- set via net.mgmt protocol
- dvmrp(4),
- mospf(5),
- pimSparseDense(6), -- PIMv1, both DM and SM
- cbt(7),
- pimSparseMode(8), -- PIM-SMv2
- pimDenseMode(9), -- PIM-DMv2
- igmpOnly(10)
- }
- MAX-ACCESS read-only
- STATUS current
- DESCRIPTION
- "The routing mechanism via which this route was learned."
- ::= { ipMRouteNextHopEntry 10 }
-
- ipMRouteNextHopPkts OBJECT-TYPE
- SYNTAX Counter32
- MAX-ACCESS read-only
- STATUS current
- DESCRIPTION
- "The number of packets which have been forwarded using this
- route."
- ::= { ipMRouteNextHopEntry 11 }
-
-
-
-
-
-
-
-
- Expires September 1997 [Page 14]
-
-
-
-
-
- Draft IP Multicast Routing MIB March 1997
-
-
- --
- -- The Multicast Routing Interface Table
- --
-
- ipMRouteInterfaceTable OBJECT-TYPE
- SYNTAX SEQUENCE OF IpMRouteInterfaceEntry
- MAX-ACCESS not-accessible
- STATUS current
- DESCRIPTION
- "The (conceptual) table containg multicast routing
- information specific to interfaces."
- ::= { ipMRoute 4 }
-
- ipMRouteInterfaceEntry OBJECT-TYPE
- SYNTAX IpMRouteInterfaceEntry
- MAX-ACCESS not-accessible
- STATUS current
- DESCRIPTION
- "An entry (conceptual row) containing the multicast routing
- information for a particular interface."
- INDEX { ipMRouteInterfaceIfIndex }
- ::= { ipMRouteInterfaceTable 1 }
-
- IpMRouteInterfaceEntry ::= SEQUENCE {
- ipMRouteInterfaceIfIndex Integer32,
- ipMRouteInterfaceTtl Integer32,
- ipMRouteInterfaceProtocol INTEGER
- }
-
- ipMRouteInterfaceIfIndex OBJECT-TYPE
- SYNTAX Integer32
- MAX-ACCESS not-accessible
- STATUS current
- DESCRIPTION
- "The ifIndex value of the interface for which this entry
- contains information."
- ::= { ipMRouteInterfaceEntry 1 }
-
- ipMRouteInterfaceTtl OBJECT-TYPE
- SYNTAX Integer32
- MAX-ACCESS read-write
- STATUS current
- DESCRIPTION
- "The datagram TTL threshold for the interface. Any IP
- multicast datagrams with a TTL less than this threshold will
-
-
-
-
-
- Expires September 1997 [Page 15]
-
-
-
-
-
- Draft IP Multicast Routing MIB March 1997
-
-
- not be forwarded out the interface. The default value of 0
- means all multicast packets are forwarded out the
- interface."
- ::= { ipMRouteInterfaceEntry 2 }
-
- ipMRouteInterfaceProtocol OBJECT-TYPE
- SYNTAX INTEGER {
- other(1), -- none of the following
- local(2), -- e.g., static routing
- netmgmt(3), -- set via net.mgmt protocol
- dvmrp(4),
- mospf(5),
- pimSparseDense(6), -- PIMv1, both DM and SM
- cbt(7),
- pimSparseMode(8), -- PIM-SMv2
- pimDenseMode(9), -- PIM-DMv2
- igmpOnly(10)
- }
- MAX-ACCESS read-write
- STATUS current
- DESCRIPTION
- "The routing protocol running on this interface."
- ::= { ipMRouteInterfaceEntry 3 }
-
-
- --
- -- The IP Multicast Scoped Boundary Table
- --
-
- ipMRouteBoundaryTable OBJECT-TYPE
- SYNTAX SEQUENCE OF IpMRouteBoundaryEntry
- MAX-ACCESS not-accessible
- STATUS current
- DESCRIPTION
- "The (conceptual) table listing the router's scoped
- multicast address boundaries."
- ::= { ipMRoute 5 }
-
- ipMRouteBoundaryEntry OBJECT-TYPE
- SYNTAX IpMRouteBoundaryEntry
- MAX-ACCESS not-accessible
- STATUS current
- DESCRIPTION
- "An entry (conceptual row) in the
- ipMRouteBoundaryTable representing a scoped
-
-
-
-
-
- Expires September 1997 [Page 16]
-
-
-
-
-
- Draft IP Multicast Routing MIB March 1997
-
-
- boundary."
- INDEX { ipMRouteBoundaryIfIndex, ipMRouteBoundaryAddress,
- ipMRouteBoundaryAddressMask }
- ::= { ipMRouteBoundaryTable 1 }
-
- IpMRouteBoundaryEntry ::= SEQUENCE {
- ipMRouteBoundaryIfIndex Integer32,
- ipMRouteBoundaryAddress IpAddress,
- ipMRouteBoundaryAddressMask IpAddress,
- ipMRouteBoundaryStatus RowStatus
- }
-
- ipMRouteBoundaryIfIndex OBJECT-TYPE
- SYNTAX Integer32
- MAX-ACCESS not-accessible
- STATUS current
- DESCRIPTION
- "The IfIndex value for the interface to which
- this boundary applies. Packets with a
- destination address in the associated
- address/mask range will not be forwarded out this
- interface."
- ::= { ipMRouteBoundaryEntry 1 }
-
- ipMRouteBoundaryAddress OBJECT-TYPE
- SYNTAX IpAddress
- MAX-ACCESS not-accessible
- STATUS current
- DESCRIPTION
- "The group address which when combined with the
- corresponding value of ipMRouteBoundaryAddressMask
- identifies the group range for which the scoped
- boundary exists. Scoped addresses must come from
- the range 239.x.x.x."
- ::= { ipMRouteBoundaryEntry 2 }
-
- ipMRouteBoundaryAddressMask OBJECT-TYPE
- SYNTAX IpAddress
- MAX-ACCESS not-accessible
- STATUS current
- DESCRIPTION
- "The group address mask which when combined with
- the corresponding value of ipMRouteBoundaryAddress
- identifies the group range for which the scoped
- boundary exists."
-
-
-
-
-
- Expires September 1997 [Page 17]
-
-
-
-
-
- Draft IP Multicast Routing MIB March 1997
-
-
- ::= { ipMRouteBoundaryEntry 3 }
-
- ipMRouteBoundaryStatus 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."
- ::= { ipMRouteBoundaryEntry 4 }
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Expires September 1997 [Page 18]
-
-
-
-
-
- Draft IP Multicast Routing MIB March 1997
-
-
- -- conformance information
-
- ipMRouteMIBConformance
- OBJECT IDENTIFIER ::= { ipMRouteMIB 2 }
- ipMRouteMIBCompliances
- OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 1 }
- ipMRouteMIBGroups OBJECT IDENTIFIER ::= { ipMRouteMIBConformance 2 }
-
-
- -- compliance statements
-
- ipMRouteMIBCompliance MODULE-COMPLIANCE
- STATUS current
- DESCRIPTION
- "The compliance statement for the IP Multicast MIB."
- MODULE -- this module
- MANDATORY-GROUPS { ipMRouteMIBBasicGroup }
-
- GROUP ipMRouteMIBBoundaryGroup
- DESCRIPTION
- "This group is only required to support management of
- scoped multicast address boundaries."
-
- OBJECT ipMRouteBoundaryStatus
- MIN-ACCESS read-only
- DESCRIPTION
- "Write access is not required."
-
- ::= { ipMRouteMIBCompliances 1 }
-
-
- -- units of conformance
-
- ipMRouteMIBBasicGroup OBJECT-GROUP
- OBJECTS { ipMRouteEnable, ipMRouteUpstreamNeighbor,
- ipMRouteInIfIndex,
- ipMRouteUpTime, ipMRouteExpiryTime,
- ipMRoutePkts, ipMRouteDifferentInIfPackets,
- ipMRouteOctets,
- ipMRouteNextHopState,
- ipMRouteNextHopUpTime,
- ipMRouteNextHopExpiryTime,
- ipMRouteNextHopProtocol,
- ipMRouteNextHopPkts,
- ipMRouteInterfaceTtl,
-
-
-
-
-
- Expires September 1997 [Page 19]
-
-
-
-
-
- Draft IP Multicast Routing MIB March 1997
-
-
- ipMRouteInterfaceProtocol,
- ipMRouteProtocol
- }
- STATUS current
- DESCRIPTION
- "A collection of objects to support basic management of
- IP Multicast routing."
- ::= { ipMRouteMIBGroups 1 }
-
- ipMRouteMIBHopCountGroup OBJECT-GROUP
- OBJECTS { ipMRouteNextHopClosestMemberHops }
- STATUS current
- DESCRIPTION
- "A collection of objects to support management of the use
- of hop counts in IP Multicast routing."
- ::= { ipMRouteMIBGroups 2 }
-
- ipMRouteMIBBoundaryGroup OBJECT-GROUP
- OBJECTS { ipMRouteBoundaryStatus }
- STATUS current
- DESCRIPTION
- "A collection of objects to support management of scoped
- multicast address boundaries."
- ::= { ipMRouteMIBGroups 3 }
-
- ipMRouteMIBPktsOutGroup OBJECT-GROUP
- OBJECTS { ipMRouteNextHopPkts }
- STATUS current
- DESCRIPTION
- "A collection of objects to support management of packet
- counters for each outgoing interface entry of a route."
- ::= { ipMRouteMIBGroups 4 }
-
-
- END
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Expires September 1997 [Page 20]
-
-
-
-
-
- Draft IP Multicast Routing MIB March 1997
-
-
- 6. Acknowledgements
-
- This MIB module was updated based on feedback from the IETF's Inter-
- Domain Multicast Routing (IDMR) Working Group.
-
-
-
- 7. References
-
- [1] SNMPv2 Working Group, 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,
- January 1996.
-
- [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base
- for Network Management of TCP/IP-based internets: MIB-II", STD 17,
- RFC 1213, March 1991.
-
- [3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network
- Management Protocol", RFC 1157, May 1990.
-
- [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
- S. Waldbusser, "Protocol Operations for version 2 of the Simple
- Network Management Protocol (SNMPv2)", RFC 1905, January 1996.
-
- [5] Deering, S., "Multicast Routing in a Datagram Internetwork", PhD
- thesis, Electrical Engineering Dept., Stanford University, December
- 1991.
-
- [6] Waitzman, D., Partridge, C., and S.E. Deering, "Distance Vector
- Multicast Routing Protocol", RFC 1075, Bolt Beranek and Newman,
- Stanford University, November 1988.
-
- [7] 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): Protocol
- Specification", November 1996.
-
- [8] Estrin, D., Farinacci, D., Jacobson, V., Liu, C., Wei, L., Sharma,
- P., and A. Helmy, "Protocol Independent Multicast - Dense Mode
- (PIM-DM): Protocol Specification", January 1996.
-
- [9] Moy, J., "Multicast Extensions to OSPF", RFC 1584, Proteon, March
- 1994.
-
-
-
-
-
-
- Expires September 1997 [Page 21]
-
-
-
-
-
- Draft IP Multicast Routing MIB March 1997
-
-
- [10] Ballardie, A. J., "Core Based Trees (CBT) Multicast: Architectural
- Overview and Specification", University College London, November
- 1994.
-
-
-
-
- 8. Security Considerations
-
- Security issues are not discussed in this memo.
-
-
-
- 9. Authors' Address
-
- Keith McCloghrie
- cisco Systems, Inc.
- 170 West Tasman Drive
- San Jose, CA 95134-1706
- 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
- Department of Electrical Engineering and Computer Science
- University of Michigan
- 1301 Beal Ave.
- Ann Arbor, MI 48109-2122
- Phone: +1 313 763 5243
- EMail: thalerd@eecs.umich.edu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Expires September 1997 [Page 22]
-
-
-
-
-
- Draft IP Multicast Routing MIB March 1997
-
-
- Table of Contents
-
-
- 1 Introduction .................................................... 1
- 2 Revision History ................................................ 2
- 3 The SNMP Network Management Framework ........................... 4
- 3.1 Object Definitions ............................................ 4
- 4 Overview ........................................................ 5
- 5 Definitions ..................................................... 6
- 6 Acknowledgements ................................................ 21
- 7 References ...................................................... 21
- 8 Security Considerations ......................................... 22
- 9 Authors' Address ................................................ 22
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Expires September 1997 [Page 23]
-
-