idnits 2.17.1 draft-ietf-mboned-ip-mcast-mib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 18. -- Found old boilerplate from RFC 3978, Section 5.5 on line 2235. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2212. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2219. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2225. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** The document seems to lack an RFC 3978 Section 5.4 Reference to BCP 78. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 3 instances of lines with non-RFC2606-compliant FQDNs in the document. == There are 1 instance of lines with non-RFC3849-compliant IPv6 addresses in the document. If these are example addresses, they should be changed. -- The abstract seems to indicate that this document obsoletes RFC2932, but the header doesn't have an 'Obsoletes:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (June 5, 2006) is 6528 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC2434' is defined on line 2102, but no explicit reference was found in the text == Unused Reference: 'RFC3283' is defined on line 2121, but no explicit reference was found in the text == Unused Reference: 'RFC3306' is defined on line 2124, but no explicit reference was found in the text == Unused Reference: 'RFC4291' is defined on line 2134, but no explicit reference was found in the text == Unused Reference: 'RFC1075' is defined on line 2139, but no explicit reference was found in the text == Unused Reference: 'RFC1584' is defined on line 2143, but no explicit reference was found in the text == Unused Reference: 'RFC2189' is defined on line 2146, but no explicit reference was found in the text == Unused Reference: 'RFC2287' is defined on line 2150, but no explicit reference was found in the text == Unused Reference: 'RFC2934' is defined on line 2157, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-pim-sm-v2-new' is defined on line 2165, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-pim-bidir' is defined on line 2172, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2434 (Obsoleted by RFC 5226) ** Downref: Normative reference to an Informational RFC: RFC 3283 ** Downref: Normative reference to an Informational RFC: RFC 3569 -- Obsolete informational reference (is this intentional?): RFC 2932 (Obsoleted by RFC 5132) == Outdated reference: A later version (-09) exists of draft-ietf-pim-bidir-08 Summary: 7 errors (**), 0 flaws (~~), 17 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 MBONED WG D. McWalter 3 Internet-Draft Data Connection Ltd 4 Expires: December 7, 2006 D. Thaler 5 Microsoft Corporation 6 Obsoletes (if approved): RFC2932 A. Kessler 7 Cisco Systems 8 June 5, 2006 10 IP Multicast MIB 11 draft-ietf-mboned-ip-mcast-mib-01.txt 13 Status of this Memo 15 By submitting this Internet-Draft, each author represents that any 16 applicable patent or other IPR claims of which he or she is aware 17 have been or will be disclosed, and any of which he or she becomes 18 aware will be disclosed, in accordance with Section 6 of BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six months 26 and may be updated, replaced, or obsoleted by other documents at any 27 time. It is inappropriate to use Internet-Drafts as reference 28 material or to cite them other than as "work in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 This Internet-Draft will expire on December 7, 2006. 38 Copyright Notice 40 Copyright (C) The Internet Society (2006). 42 Abstract 44 This memo defines a portion of the Management Information Base (MIB) 45 for use with network management protocols in the Internet community. 46 In particular, it describes objects used for managing multicast 47 function, independent of the specific multicast protocol(s) in use. 48 This document obsoletes RFC 2932. 50 Table of Contents 52 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 53 2. History . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 3. The Internet-Standard Management Framework . . . . . . . . . . 3 55 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 56 5. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 4 57 6. Security Considerations . . . . . . . . . . . . . . . . . . . 41 58 6.1 SNMPv2 . . . . . . . . . . . . . . . . . . . . . . . . . . 41 59 6.2 Writeable objects . . . . . . . . . . . . . . . . . . . . 41 60 6.3 Readable objects . . . . . . . . . . . . . . . . . . . . . 42 61 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 44 62 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 44 63 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 45 64 9.1 Normative References . . . . . . . . . . . . . . . . . . . 45 65 9.2 Informative References . . . . . . . . . . . . . . . . . . 45 66 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 46 67 Intellectual Property and Copyright Statements . . . . . . . . 48 69 1. Introduction 71 This MIB describes objects used for managing IP multicast function, 72 including IP multicast routing. These objects are independent of the 73 specific multicast routing protocol in use. Managed objects specific 74 to particular multicast protocols are defined elsewhere. 76 2. History 78 This document obsoletes [RFC2932]. The MIB module defined by this 79 document is a re-working of the MIB module from [RFC2932], with 80 changes that include the following. 82 o This MIB module is independent of address type, whereas [RFC2932] 83 only supported IPv4. 85 o This MIB module allows several multicast protocols to perform 86 routing on a single interface, where [RFC2932] assumed each 87 interface supported at most one multicast routing protocol. 89 o This MIB module includes objects that are not specific to 90 multicast routing. It allows management of multicast function on 91 systems that do not perform routing, whereas RFC 2932 was 92 restricted to multicast routing. 94 o This MIB module includes a table of Source-Specific Multicast 95 (SSM) address ranges to which SSM semantics [RFC3569] should be 96 applied. 98 o This MIB module includes a table of local applications that are 99 receiving multicast data. 101 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 102 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 103 document are to be interpreted as described in [RFC2119]. 105 3. The Internet-Standard Management Framework 107 For a detailed overview of the documents that describe the current 108 Internet-Standard Management Framework, please refer to section 7 of 109 [RFC3410]. 111 Managed objects are accessed via a virtual information store, termed 112 the Management Information Base or MIB. MIB objects are generally 113 accessed through the Simple Network Management Protocol (SNMP). 114 Objects in the MIB are defined using the mechanisms defined in the 115 Structure of Management Information (SMI). This memo specifies a MIB 116 module that is compliant to the SMIv2, which is described in STD 58, 117 ([RFC2578], [RFC2579] and [RFC2580]). 119 4. Overview 121 This MIB module contains two scalars and seven tables. The tables 122 are: 124 1. The IP Multicast Interface Table containing multicast information 125 specific to interfaces. 127 2. The IP Multicast SSM Range Table, which contains one row per 128 range of multicast group addresses to which Source-Specific 129 Multicast semantics [RFC3569] should be applied. 131 3. The IP Multicast Route Table containing multicast routing 132 information for IP datagrams sent by particular sources to the IP 133 multicast groups known to a system. 135 4. The IP Multicast Routing Next Hop Table containing information on 136 next-hops for the routing of IP multicast datagrams. Each entry 137 is one of a list of next-hops on outgoing interfaces for 138 particular sources sending to a particular multicast group 139 address. 141 5. The IP Multicast Scope Boundary Table containing the boundaries 142 configured for multicast scopes [RFC2365]. 144 6. The IP Multicast Scope Name Table containing human-readable names 145 of multicast scope. 147 7. The IP Multicast Local Listener Table containing identifiers for 148 local applications that are receiving multicast data. 150 This MIB module uses textual conventions defined in the IF-MIB 151 [RFC2863], the INET-ADDRESS-MIB [RFC4001] and the IANA-RTPROTO-MIB. 153 5. Definitions 155 IPMCAST-MIB DEFINITIONS ::= BEGIN 157 IMPORTS 158 MODULE-IDENTITY, OBJECT-TYPE, 159 mib-2, Unsigned32, Counter32, 160 Counter64, Gauge32, TimeTicks FROM SNMPv2-SMI 161 RowStatus, TEXTUAL-CONVENTION, 162 TruthValue, StorageType, 163 TimeStamp FROM SNMPv2-TC 164 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 165 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 166 InterfaceIndexOrZero, 167 InterfaceIndex FROM IF-MIB 168 IANAipRouteProtocol, 169 IANAipMRouteProtocol FROM IANA-RTPROTO-MIB 170 InetAddress, InetAddressType, 171 InetAddressPrefixLength FROM INET-ADDRESS-MIB; 173 ipMcastMIB MODULE-IDENTITY 174 LAST-UPDATED "200606050000Z" -- 5 June 2006 175 ORGANIZATION "IETF MBONED Working Group" 176 CONTACT-INFO "David McWalter 177 Data Connection Limited 178 100 Church Street 179 Enfield, EN2 6BQ 180 UK 182 Phone: +44 208 366 1177 183 EMail: dmcw@dataconnection.com 185 Dave Thaler 186 Microsoft Corporation 187 One Microsoft Way 188 Redmond, WA 98052-6399 189 US 191 Phone: +1 425 703 8835 192 EMail: dthaler@dthaler.microsoft.com 194 Andrew Kessler 195 Cisco Systems 196 425 E. Tasman Drive 197 San Jose, CA 95134 198 US 200 Phone: +1 408 526 5139 201 EMail: kessler@cisco.com" 202 DESCRIPTION 203 "The MIB module for management of IP Multicast function. 205 This MIB module contains information about IP Multicast 206 routing, data forwarding, and data reception. This MIB 207 module is independent of the multicast protocol(s) and 208 address type(s) that are in use. 210 Copyright (C) The Internet Society (2006). This version of 211 this MIB module is part of RFC yyyy; see the RFC itself for 212 full legal notices." 214 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 215 REVISION "200606050000Z" -- 5 June 2006 216 DESCRIPTION 217 "Changes from RFC 2932: 219 1) This MIB module is independent of address type, whereas 220 RFC 2932 only supported IPv4. 221 2) This MIB module allows several multicast protocols to 222 perform routing on a single interface, whereas RFC 2932 223 assumed each interface supported at most one multicast 224 routing protocol. This MIB module retains but deprecates 225 the object ipMcastInterfaceProtocol. 226 3) This MIB module includes objects that are not specific to 227 multicast routing. It allows management of multicast 228 function on systems that do not perform routing, whereas 229 RFC 2932 was restricted to multicast routing. 230 4) This MIB module includes a table of Source-Specific 231 Multicast (SSM) address ranges to which RFC 3569 SSM 232 semantics should be applied. 233 5) This MIB module includes a table of local applications 234 that are receiving multicast data. 236 Published as RFC yyyy." 237 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 238 ::= { mib-2 XXX } 239 -- RFC Ed.: replace XXX with IANA-assigned number & remove this note 241 -- 242 -- Textual conventions 243 -- 245 LanguageTag ::= TEXTUAL-CONVENTION 247 DISPLAY-HINT "99a" 248 STATUS current 249 DESCRIPTION 250 "A language tag with all alphabetic characters converted to 251 lowercase. This restriction is intended to make the lexical 252 ordering imposed by SNMP useful when applied to language 253 tags. Note that it is theoretically possible for a valid 254 language tag to exceed the allowed length of this syntax, 255 and thus be impossible to represent with this syntax. 256 Sampling of language tags in current use on the Internet 257 suggests that this limit does not pose a serious problem in 258 practice." 259 REFERENCE "RFC 3283" 260 SYNTAX OCTET STRING (SIZE (1..99)) 262 -- 263 -- Top-level structure of the MIB 264 -- 266 ipMcastMIBObjects OBJECT IDENTIFIER ::= { ipMcastMIB 1 } 268 ipMcast OBJECT IDENTIFIER ::= { ipMcastMIBObjects 1 } 270 ipMcastEnable OBJECT-TYPE 271 SYNTAX INTEGER { enabled(1), disabled(2) } 272 MAX-ACCESS read-write 273 STATUS current 274 DESCRIPTION 275 "The enabled status of IP Multicast function on this 276 system." 277 ::= { ipMcast 1 } 279 ipMcastRouteEntryCount OBJECT-TYPE 280 SYNTAX Gauge32 281 MAX-ACCESS read-only 282 STATUS current 283 DESCRIPTION 284 "The number of rows in the ipMcastRouteTable. This can be 285 used to check for multicast routing activity, and to monitor 286 the multicast routing table size." 287 ::= { ipMcast 7 } 289 -- 290 -- The Multicast Interface Table 291 -- 293 ipMcastInterfaceTable OBJECT-TYPE 294 SYNTAX SEQUENCE OF IpMcastInterfaceEntry 295 MAX-ACCESS not-accessible 296 STATUS current 297 DESCRIPTION 298 "The (conceptual) table used to manage the multicast 299 protocol active on an interface." 300 ::= { ipMcast 4 } 302 ipMcastInterfaceEntry OBJECT-TYPE 303 SYNTAX IpMcastInterfaceEntry 304 MAX-ACCESS not-accessible 305 STATUS current 306 DESCRIPTION 307 "An entry (conceptual row) containing the multicast protocol 308 information for a particular interface." 309 INDEX { ipMcastInterfaceIfIndex } 310 ::= { ipMcastInterfaceTable 1 } 312 IpMcastInterfaceEntry ::= SEQUENCE { 313 ipMcastInterfaceIfIndex InterfaceIndex, 314 ipMcastInterfaceTtl Unsigned32, 315 ipMcastInterfaceProtocol IANAipMRouteProtocol, 316 ipMcastInterfaceRateLimit Unsigned32, 317 ipMcastInterfaceInMcastOctets Counter32, 318 ipMcastInterfaceOutMcastOctets Counter32, 319 ipMcastInterfaceInMcastPkts Counter32, 320 ipMcastInterfaceOutMcastPkts Counter32, 321 ipMcastInterfaceHCInMcastOctets Counter64, 322 ipMcastInterfaceHCOutMcastOctets Counter64, 323 ipMcastInterfaceHCInMcastPkts Counter64, 324 ipMcastInterfaceHCOutMcastPkts Counter64 325 } 327 ipMcastInterfaceIfIndex OBJECT-TYPE 328 SYNTAX InterfaceIndex 329 MAX-ACCESS not-accessible 330 STATUS current 331 DESCRIPTION 332 "The ifIndex value of the interface for which this entry 333 contains information." 334 ::= { ipMcastInterfaceEntry 1 } 336 ipMcastInterfaceTtl OBJECT-TYPE 337 SYNTAX Unsigned32 (0..255) 338 MAX-ACCESS read-write 339 STATUS current 340 DESCRIPTION 341 "The datagram TTL threshold for the interface. Any IP 342 multicast datagrams with a TTL (IPv4) or Hop Count (IPv6) 343 less than this threshold will not be forwarded out the 344 interface. The default value of 0 means all multicast 345 packets are forwarded out the interface." 346 DEFVAL { 0 } 347 ::= { ipMcastInterfaceEntry 2 } 349 ipMcastInterfaceProtocol OBJECT-TYPE 350 SYNTAX IANAipMRouteProtocol 351 MAX-ACCESS read-write 352 STATUS deprecated 353 DESCRIPTION 354 "The multicast protocol running on this interface. 356 More than one multicast protocol can be used on an 357 interface, so this object is ambiguous. Use of this 358 object is deprecated." 359 ::= { ipMcastInterfaceEntry 3 } 361 ipMcastInterfaceRateLimit OBJECT-TYPE 362 SYNTAX Unsigned32 (0..2147483647) 363 MAX-ACCESS read-write 364 STATUS current 365 DESCRIPTION 366 "The rate-limit, in kilobits per second, of forwarded 367 multicast traffic on the interface. A rate-limit of 0 368 indicates that no rate limiting is done." 369 DEFVAL { 0 } 370 ::= { ipMcastInterfaceEntry 4 } 372 ipMcastInterfaceInMcastOctets OBJECT-TYPE 373 SYNTAX Counter32 374 MAX-ACCESS read-only 375 STATUS current 376 DESCRIPTION 377 "The number of octets of multicast packets that have arrived 378 on the interface, including framing characters. This object 379 is similar to ifInOctets in the Interfaces MIB, except that 380 only multicast packets are counted." 381 ::= { ipMcastInterfaceEntry 5 } 383 ipMcastInterfaceOutMcastOctets OBJECT-TYPE 384 SYNTAX Counter32 385 MAX-ACCESS read-only 386 STATUS current 387 DESCRIPTION 388 "The number of octets of multicast packets that have been 389 sent on the interface." 390 ::= { ipMcastInterfaceEntry 6 } 392 ipMcastInterfaceInMcastPkts OBJECT-TYPE 393 SYNTAX Counter32 394 MAX-ACCESS read-only 395 STATUS current 396 DESCRIPTION 397 "The number of multicast packets that have arrived on the 398 interface. In many cases, this object is identical to 399 ifInMulticastPkts in the Interfaces MIB. 401 However, some implementations use ifXTable for Layer 2 402 traffic statistics and ipMcastInterfaceTable at Layer 3. In 403 this case a difference between these objects probably 404 indicates that some Layer 3 multicast packets are being 405 transmitted as unicast at Layer 2." 407 REFERENCE "RFC 2863 ifInMulticastPkts" 408 ::= { ipMcastInterfaceEntry 7 } 410 ipMcastInterfaceOutMcastPkts OBJECT-TYPE 411 SYNTAX Counter32 412 MAX-ACCESS read-only 413 STATUS current 414 DESCRIPTION 415 "The number of multicast packets that have been sent on the 416 interface. In many cases, this object is identical to 417 ifOutMulticastPkts in the Interfaces MIB. 419 However, some implementations use ifXTable for Layer 2 420 traffic statistics and ipMcastInterfaceTable at Layer 3. In 421 this case a difference between these objects probably 422 indicates that some Layer 3 multicast packets are being 423 transmitted as unicast at Layer 2." 424 REFERENCE "RFC 2863 ifOutMulticastPkts" 425 ::= { ipMcastInterfaceEntry 8 } 427 ipMcastInterfaceHCInMcastOctets OBJECT-TYPE 428 SYNTAX Counter64 429 MAX-ACCESS read-only 430 STATUS current 431 DESCRIPTION 432 "The number of octets of multicast packets that have arrived 433 on the interface, including framing characters. This object 434 is a 64-bit version of ipMcastRouteInterfaceInMcastOctets. 435 It is similar to ifHCInOctets in the Interfaces MIB, except 436 that only multicast packets are counted." 437 ::= { ipMcastInterfaceEntry 9 } 439 ipMcastInterfaceHCOutMcastOctets OBJECT-TYPE 440 SYNTAX Counter64 441 MAX-ACCESS read-only 442 STATUS current 443 DESCRIPTION 444 "The number of octets of multicast packets that have been 445 sent on the interface. This object is a 64-bit version of 446 ipMcastRouteInterfaceOutMcastOctets." 447 ::= { ipMcastInterfaceEntry 10 } 449 ipMcastInterfaceHCInMcastPkts OBJECT-TYPE 450 SYNTAX Counter64 451 MAX-ACCESS read-only 452 STATUS current 453 DESCRIPTION 454 "The number of multicast packets that have arrived on the 455 interface. In many cases, this object is identical to 456 ifHCInMulticastPkts in the Interfaces MIB. 458 However, some implementations use ifXTable for Layer 2 459 traffic statistics and ipMcastInterfaceTable at Layer 3. In 460 this case a difference between these objects probably 461 indicates that some Layer 3 multicast packets are being 462 transmitted as unicast at Layer 2." 463 REFERENCE "RFC 2863 ifHCInMulticastPkts" 464 ::= { ipMcastInterfaceEntry 11 } 466 ipMcastInterfaceHCOutMcastPkts OBJECT-TYPE 467 SYNTAX Counter64 468 MAX-ACCESS read-only 469 STATUS current 470 DESCRIPTION 471 "The number of multicast packets that have been sent on the 472 interface. In many cases, this object is identical to 473 ifHCOutMulticastPkts in the Interfaces MIB. 475 However, some implementations use ifXTable for Layer 2 476 traffic statistics and ipMcastInterfaceTable at Layer 3. In 477 this case a difference between these objects probably 478 indicates that some Layer 3 multicast packets are being 479 transmitted as unicast at Layer 2." 480 REFERENCE "RFC 2863 ifHCOutMulticastPkts" 481 ::= { ipMcastInterfaceEntry 12 } 483 -- 484 -- The SSM Range Table 485 -- 487 ipMcastSsmRangeTable OBJECT-TYPE 488 SYNTAX SEQUENCE OF IpMcastSsmRangeEntry 489 MAX-ACCESS not-accessible 490 STATUS current 491 DESCRIPTION 492 "This table is used to create and manage the range(s) of 493 group addresses to which SSM semantics should be applied." 494 REFERENCE "RFC 3569" 495 ::= { ipMcast 8 } 497 ipMcastSsmRangeEntry OBJECT-TYPE 498 SYNTAX IpMcastSsmRangeEntry 499 MAX-ACCESS not-accessible 500 STATUS current 501 DESCRIPTION 502 "An entry (conceptual row) in the ssmRangeTable." 504 INDEX { ipMcastSsmRangeAddressType, 505 ipMcastSsmRangeAddress, 506 ipMcastSsmRangePrefixLength } 507 ::= { ipMcastSsmRangeTable 1 } 509 IpMcastSsmRangeEntry ::= SEQUENCE { 510 ipMcastSsmRangeAddressType InetAddressType, 511 ipMcastSsmRangeAddress InetAddress, 512 ipMcastSsmRangePrefixLength InetAddressPrefixLength, 513 ipMcastSsmRangeRowStatus RowStatus, 514 ipMcastSsmRangeStorageType StorageType 515 } 517 ipMcastSsmRangeAddressType OBJECT-TYPE 518 SYNTAX InetAddressType 519 MAX-ACCESS not-accessible 520 STATUS current 521 DESCRIPTION 522 "The address type of the multicast group prefix." 523 ::= { ipMcastSsmRangeEntry 1 } 525 ipMcastSsmRangeAddress OBJECT-TYPE 526 SYNTAX InetAddress (SIZE (4|8|16|20)) 527 MAX-ACCESS not-accessible 528 STATUS current 529 DESCRIPTION 530 "The multicast group address which, when combined with 531 ipMcastSsmRangePrefixLength, gives the group prefix for this 532 SSM range. The InetAddressType is given by the 533 ipMcastSsmRangeAddressType object. 535 This address object is only significant up to 536 ipMcastSsmRangePrefixLength bits. The remainder of the 537 address bits are zero. This is especially important for 538 this index field, which is part of the index of this entry. 539 Any non-zero bits would signify an entirely different 540 entry. 542 For IPv6 SSM address ranges, only ranges within the space 543 FF3x::/32 are permitted (where 'x' is any valid scope). 545 To configure non-global scope SSM range entries within a 546 zone, consistent ipMcastBoundaryTable entries are required 547 on routers at the zone boundary." 548 REFERENCE "RFC 4291 section 2.7 and RFC 3306 section 6" 549 ::= { ipMcastSsmRangeEntry 2 } 551 ipMcastSsmRangePrefixLength OBJECT-TYPE 552 SYNTAX InetAddressPrefixLength (4..128) 553 MAX-ACCESS not-accessible 554 STATUS current 555 DESCRIPTION 556 "The multicast group prefix length, which, when combined 557 with ipMcastSsmRangeAddress, gives the group prefix for this 558 SSM range. The InetAddressType is given by the 559 ipMcastSsmRangeAddressType object. If 560 'ipv4' or 'ipv4z', this object must be in the range 4..32. 561 If ipMcastSsmRangeAddressType is 'ipv6' or 'ipv6z', this 562 object must be in the range 8..128." 563 ::= { ipMcastSsmRangeEntry 3 } 565 ipMcastSsmRangeRowStatus OBJECT-TYPE 566 SYNTAX RowStatus 567 MAX-ACCESS read-create 568 STATUS current 569 DESCRIPTION 570 "The status of this row, by which rows in this table can 571 be created and destroyed. 573 This status object can be set to active(1) without setting 574 any other columnar objects in this entry. 576 All writeable objects in this entry can be modified when the 577 status of this entry is active(1)." 578 ::= { ipMcastSsmRangeEntry 4 } 580 ipMcastSsmRangeStorageType OBJECT-TYPE 581 SYNTAX StorageType 582 MAX-ACCESS read-create 583 STATUS current 584 DESCRIPTION 585 "The storage type for this row. Rows having the value 586 'permanent' need not allow write-access to any columnar 587 objects in the row." 588 DEFVAL { nonVolatile } 589 ::= { ipMcastSsmRangeEntry 5 } 591 -- 592 -- The IP Multicast Routing Table 593 -- 595 ipMcastRouteTable OBJECT-TYPE 596 SYNTAX SEQUENCE OF IpMcastRouteEntry 597 MAX-ACCESS not-accessible 598 STATUS current 599 DESCRIPTION 600 "The (conceptual) table containing multicast routing 601 information for IP datagrams sent by particular sources to 602 to the IP multicast groups known to this router." 603 ::= { ipMcast 2 } 605 ipMcastRouteEntry OBJECT-TYPE 606 SYNTAX IpMcastRouteEntry 607 MAX-ACCESS not-accessible 608 STATUS current 609 DESCRIPTION 610 "An entry (conceptual row) containing the multicast routing 611 information for IP datagrams from a particular source and 612 addressed to a particular IP multicast group address." 613 INDEX { ipMcastRouteGroupAddressType, 614 ipMcastRouteGroup, 615 ipMcastRouteGroupPrefixLength, 616 ipMcastRouteSourceAddressType, 617 ipMcastRouteSource, 618 ipMcastRouteSourcePrefixLength } 619 ::= { ipMcastRouteTable 1 } 621 IpMcastRouteEntry ::= SEQUENCE { 622 ipMcastRouteGroupAddressType InetAddressType, 623 ipMcastRouteGroup InetAddress, 624 ipMcastRouteGroupPrefixLength InetAddressPrefixLength, 625 ipMcastRouteSourceAddressType InetAddressType, 626 ipMcastRouteSource InetAddress, 627 ipMcastRouteSourcePrefixLength InetAddressPrefixLength, 628 ipMcastRouteUpstreamNeighborType InetAddressType, 629 ipMcastRouteUpstreamNeighbor InetAddress, 630 ipMcastRouteInIfIndex InterfaceIndexOrZero, 631 ipMcastRouteTimeStamp TimeStamp, 632 ipMcastRouteExpiryTime TimeTicks, 633 ipMcastRoutePkts Counter32, 634 ipMcastRouteDifferentInIfPackets Counter32, 635 ipMcastRouteOctets Counter32, 636 ipMcastRouteProtocol IANAipMRouteProtocol, 637 ipMcastRouteRtProtocol IANAipRouteProtocol, 638 ipMcastRouteRtAddressType InetAddressType, 639 ipMcastRouteRtAddress InetAddress, 640 ipMcastRouteRtPrefixLength InetAddressPrefixLength, 641 ipMcastRouteRtType INTEGER, 642 ipMcastRouteHCOctets Counter64, 643 ipMcastRouteDifferentInIfOctets Counter32 644 } 646 ipMcastRouteGroupAddressType OBJECT-TYPE 647 SYNTAX InetAddressType 648 MAX-ACCESS not-accessible 649 STATUS current 650 DESCRIPTION 651 "A value indicating the address family of the address 652 contained in ipMcastRouteGroup. Legal values correspond to 653 the subset of address families for which multicast 654 forwarding is supported." 655 ::= { ipMcastRouteEntry 1 } 657 ipMcastRouteGroup OBJECT-TYPE 658 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 659 MAX-ACCESS not-accessible 660 STATUS current 661 DESCRIPTION 662 "The IP multicast group address which when combined with the 663 corresponding value specified in 664 ipMcastRouteGroupPrefixLength identifies the groups for 665 which this entry contains multicast routing information. 667 This address object is only significant up to 668 ipMcastRouteGroupPrefixLength bits. The remainder of the 669 address bits are zero. This is especially important for 670 this index field, which is part of the index of this entry. 671 Any non-zero bits would signify an entirely different 672 entry." 673 ::= { ipMcastRouteEntry 2 } 675 ipMcastRouteGroupPrefixLength OBJECT-TYPE 676 SYNTAX InetAddressPrefixLength (4..128) 677 MAX-ACCESS not-accessible 678 STATUS current 679 DESCRIPTION 680 "The length in bits of the mask which when combined with the 681 corresponding value of ipMcastRouteGroup identifies the 682 groups for which this entry contains multicast routing 683 information." 684 ::= { ipMcastRouteEntry 3 } 686 ipMcastRouteSourceAddressType OBJECT-TYPE 687 SYNTAX InetAddressType 688 MAX-ACCESS not-accessible 689 STATUS current 690 DESCRIPTION 691 "A value indicating the address family of the address 692 contained in ipMcastRouteSource. The value MUST be the same 693 as the value of ipMcastRouteGroupType." 694 ::= { ipMcastRouteEntry 4 } 696 ipMcastRouteSource OBJECT-TYPE 697 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 698 MAX-ACCESS not-accessible 699 STATUS current 700 DESCRIPTION 701 "The network address which when combined with the 702 corresponding value of ipMcastRouteSourcePrefixLength 703 identifies the sources for which this entry contains 704 multicast routing information. 706 This address object is only significant up to 707 ipMcastRouteGroupPrefixLength bits. The remainder of the 708 address bits are zero. This is especially important for 709 this index field, which is part of the index of this entry. 710 Any non-zero bits would signify an entirely different 711 entry." 712 ::= { ipMcastRouteEntry 5 } 714 ipMcastRouteSourcePrefixLength OBJECT-TYPE 715 SYNTAX InetAddressPrefixLength (4..128) 716 MAX-ACCESS not-accessible 717 STATUS current 718 DESCRIPTION 719 "The length in bits of the mask which when combined with the 720 corresponding value of ipMcastRouteSource identifies the 721 sources for which this entry contains multicast routing 722 information." 723 ::= { ipMcastRouteEntry 6 } 725 ipMcastRouteUpstreamNeighborType OBJECT-TYPE 726 SYNTAX InetAddressType 727 MAX-ACCESS read-only 728 STATUS current 729 DESCRIPTION 730 "A value indicating the address family of the address 731 contained in ipMcastRouteUpstreamNeighbor. The value MUST 732 be the same as the value of ipMcastRouteGroupType." 733 ::= { ipMcastRouteEntry 7 } 735 ipMcastRouteUpstreamNeighbor OBJECT-TYPE 736 SYNTAX InetAddress 737 MAX-ACCESS read-only 738 STATUS current 739 DESCRIPTION 740 "The address of the upstream neighbor (for example, RPF 741 neighbor) from which IP datagrams from these sources to 742 this multicast address are received. If the upstream 743 neighbor is unknown, then ipMcastRouteUpstreamNeighbor 744 will be 0.0.0.0 in the case of an IPv4 entry, and 745 0:0:0:0:0:0:0:0 in the case of an IPv6 entry (for example, 746 in BIDIR-PIM)." 747 ::= { ipMcastRouteEntry 8 } 749 ipMcastRouteInIfIndex OBJECT-TYPE 750 SYNTAX InterfaceIndexOrZero 751 MAX-ACCESS read-only 752 STATUS current 753 DESCRIPTION 754 "The value of ifIndex for the interface on which IP 755 datagrams sent by these sources to this multicast address 756 are received. A value of 0 indicates that datagrams are not 757 subject to an incoming interface check, but may be accepted 758 on multiple interfaces (for example, in BIDIR-PIM)." 759 ::= { ipMcastRouteEntry 9 } 761 ipMcastRouteTimeStamp OBJECT-TYPE 762 SYNTAX TimeStamp 763 MAX-ACCESS read-only 764 STATUS current 765 DESCRIPTION 766 "The value of sysUpTime at which the multicast routing 767 information represented by this entry was learned by the 768 router." 769 ::= { ipMcastRouteEntry 10 } 771 ipMcastRouteExpiryTime OBJECT-TYPE 772 SYNTAX TimeTicks 773 MAX-ACCESS read-only 774 STATUS current 775 DESCRIPTION 776 "The minimum amount of time remaining before this entry will 777 be aged out. The value 0 indicates that the entry is not 778 subject to aging. If ipMcastRouteNextHopState is pruned(1), 779 this object represents the remaining time until the prune 780 expires. If this timer expires, state reverts to 781 forwarding(2). Otherwise, this object represents the time 782 until this entry is removed from the table." 783 ::= { ipMcastRouteEntry 11 } 785 ipMcastRoutePkts OBJECT-TYPE 786 SYNTAX Counter32 787 MAX-ACCESS read-only 788 STATUS current 789 DESCRIPTION 790 "The number of packets routed using this multicast route 791 entry. 793 Discontinuities in this monotonically increasing value 794 occur at re-initialization of the management system. 795 Discontinuities can also occur as a result of routes being 796 removed and replaced, which can be detected by observing 797 the value of ipMcastRouteTimeStamp." 798 ::= { ipMcastRouteEntry 12 } 800 ipMcastRouteDifferentInIfPackets OBJECT-TYPE 801 SYNTAX Counter32 802 MAX-ACCESS read-only 803 STATUS current 804 DESCRIPTION 805 "The number of packets which this router has received from 806 these sources and addressed to this multicast group address, 807 which were dropped because they were not received on the 808 interface indicated by ipMcastRouteInIfIndex. Packets which 809 are not subject to an incoming interface check (for example, 810 using BIDIR-PIM) are not counted. 812 If this counter increases rapidly, this indicates a problem. 813 A significant quantity of multicast data is arriving at this 814 router on unexpected RPF paths (Reverse Path Forwarding 815 paths; the unicast routes to the expected origin of 816 multicast data flows), and is not being forwarded. 818 For guidance, if the rate of increase of this counter 819 exceeds 1% of the rate of increase of ipMcastRoutePkts, then 820 there are multicast routing problems that require 821 investigation. 823 Discontinuities in this monotonically increasing value 824 occur at re-initialization of the management system. 825 Discontinuities can also occur as a result of routes being 826 removed and replaced, which can be detected by observing 827 the value of ipMcastRouteTimeStamp." 828 ::= { ipMcastRouteEntry 13 } 830 ipMcastRouteOctets OBJECT-TYPE 831 SYNTAX Counter32 832 MAX-ACCESS read-only 833 STATUS current 834 DESCRIPTION 835 "The number of octets contained in IP datagrams which were 836 received from these sources and addressed to this multicast 837 group address, and which were forwarded by this router. 839 Discontinuities in this monotonically increasing value 840 occur at re-initialization of the management system. 842 Discontinuities can also occur as a result of routes being 843 removed and replaced, which can be detected by observing 844 the value of ipMcastRouteTimeStamp." 845 ::= { ipMcastRouteEntry 14 } 847 ipMcastRouteProtocol OBJECT-TYPE 848 SYNTAX IANAipMRouteProtocol 849 MAX-ACCESS read-only 850 STATUS current 851 DESCRIPTION 852 "The multicast routing protocol via which this multicast 853 forwarding entry was learned." 854 ::= { ipMcastRouteEntry 15 } 856 ipMcastRouteRtProtocol OBJECT-TYPE 857 SYNTAX IANAipRouteProtocol 858 MAX-ACCESS read-only 859 STATUS current 860 DESCRIPTION 861 "The routing mechanism via which the route used to find the 862 upstream or parent interface for this multicast forwarding 863 entry was learned. Inclusion of values for routing 864 protocols is not intended to imply that those protocols need 865 be supported." 866 ::= { ipMcastRouteEntry 16 } 868 ipMcastRouteRtAddressType OBJECT-TYPE 869 SYNTAX InetAddressType 870 MAX-ACCESS read-only 871 STATUS current 872 DESCRIPTION 873 "A value indicating the address family of the address 874 contained in ipMcastRouteRtAddress. The value MUST be the 875 same as the value of ipMcastRouteGroupType." 876 ::= { ipMcastRouteEntry 17 } 878 ipMcastRouteRtAddress OBJECT-TYPE 879 SYNTAX InetAddress 880 MAX-ACCESS read-only 881 STATUS current 882 DESCRIPTION 883 "The address portion of the route used to find the upstream 884 or parent interface for this multicast forwarding entry. 886 This address object is only significant up to 887 ipMcastRouteGroupPrefixLength bits. The remainder of the 888 address bits are zero." 889 ::= { ipMcastRouteEntry 18 } 891 ipMcastRouteRtPrefixLength OBJECT-TYPE 892 SYNTAX InetAddressPrefixLength (4..128) 893 MAX-ACCESS read-only 894 STATUS current 895 DESCRIPTION 896 "The length of the mask associated with the route used to 897 find the upstream or parent interface for this multicast 898 forwarding entry." 899 ::= { ipMcastRouteEntry 19 } 901 ipMcastRouteRtType OBJECT-TYPE 902 SYNTAX INTEGER { 903 unicast (1), -- Unicast route used in multicast RIB 904 multicast (2) -- Multicast route 905 } 906 MAX-ACCESS read-only 907 STATUS current 908 DESCRIPTION 909 "The reason the given route was placed in the (logical) 910 multicast Routing Information Base (RIB). A value of 911 unicast means that the route would normally be placed only 912 in the unicast RIB, but was placed in the multicast RIB 913 (instead or in addition) due to local configuration, such as 914 when running PIM over RIP. A value of multicast means that 915 the route was explicitly added to the multicast RIB by the 916 routing protocol, such as DVMRP or Multiprotocol BGP." 917 ::= { ipMcastRouteEntry 20 } 919 ipMcastRouteHCOctets OBJECT-TYPE 920 SYNTAX Counter64 921 MAX-ACCESS read-only 922 STATUS current 923 DESCRIPTION 924 "The number of octets contained in IP datagrams which were 925 received from these sources and addressed to this multicast 926 group address, and which were forwarded by this router. 927 This object is a 64-bit version of ipMcastRouteOctets. 929 Discontinuities in this monotonically increasing value 930 occur at re-initialization of the management system. 931 Discontinuities can also occur as a result of routes being 932 removed and replaced, which can be detected by observing 933 the value of ipMcastRouteTimeStamp." 934 ::= { ipMcastRouteEntry 21 } 936 ipMcastRouteDifferentInIfOctets OBJECT-TYPE 937 SYNTAX Counter32 938 MAX-ACCESS read-only 939 STATUS current 940 DESCRIPTION 941 "The number of octets contained in IP datagrams which this 942 router has received from these sources and addressed to this 943 multicast group address, which were dropped because they 944 were not received on the interface indicated by 945 ipMcastRouteInIfIndex. Octets in IP datagrams which are not 946 subject to an incoming interface check (for example, using 947 BIDIR-PIM) are not counted. 949 If this counter increases rapidly, this indicates a problem. 950 A significant quantity of multicast data is arriving at this 951 router on unexpected RPF paths (Reverse Path Forwarding 952 paths; the unicast routes to the expected origin of 953 multicast data flows), and is not being forwarded. 955 For guidance, if the rate of increase of this counter 956 exceeds 1% of the rate of increase of ipMcastRouteOctets, 957 then there are multicast routing problems that require 958 investigation. 960 Discontinuities in this monotonically increasing value 961 occur at re-initialization of the management system. 962 Discontinuities can also occur as a result of routes being 963 removed and replaced, which can be detected by observing 964 the value of ipMcastRouteTimeStamp." 965 ::= { ipMcastRouteEntry 22 } 967 -- 968 -- The IP Multicast Routing Next Hop Table 969 -- 971 ipMcastRouteNextHopTable OBJECT-TYPE 972 SYNTAX SEQUENCE OF IpMcastRouteNextHopEntry 973 MAX-ACCESS not-accessible 974 STATUS current 975 DESCRIPTION 976 "The (conceptual) table containing information on the 977 next-hops on outgoing interfaces for routing IP multicast 978 datagrams. Each entry is one of a list of next-hops on 979 outgoing interfaces for particular sources sending to a 980 particular multicast group address." 981 ::= { ipMcast 3 } 983 ipMcastRouteNextHopEntry OBJECT-TYPE 984 SYNTAX IpMcastRouteNextHopEntry 985 MAX-ACCESS not-accessible 986 STATUS current 987 DESCRIPTION 988 "An entry (conceptual row) in the list of next-hops on 989 outgoing interfaces to which IP multicast datagrams from 990 particular sources to an IP multicast group address are 991 routed." 992 INDEX { ipMcastRouteNextHopGroupAddressType, 993 ipMcastRouteNextHopGroup, 994 ipMcastRouteNextHopSourceAddressType, 995 ipMcastRouteNextHopSource, 996 ipMcastRouteNextHopSourcePrefixLength, 997 ipMcastRouteNextHopIfIndex, 998 ipMcastRouteNextHopAddressType, 999 ipMcastRouteNextHopAddress } 1000 ::= { ipMcastRouteNextHopTable 1 } 1002 IpMcastRouteNextHopEntry ::= SEQUENCE { 1003 ipMcastRouteNextHopGroupAddressType InetAddressType, 1004 ipMcastRouteNextHopGroup InetAddress, 1005 ipMcastRouteNextHopSourceAddressType InetAddressType, 1006 ipMcastRouteNextHopSource InetAddress, 1007 ipMcastRouteNextHopSourcePrefixLength InetAddressPrefixLength, 1008 ipMcastRouteNextHopIfIndex InterfaceIndex, 1009 ipMcastRouteNextHopAddressType InetAddressType, 1010 ipMcastRouteNextHopAddress InetAddress, 1011 ipMcastRouteNextHopState INTEGER, 1012 ipMcastRouteNextHopTimeStamp TimeStamp, 1013 ipMcastRouteNextHopExpiryTime TimeTicks, 1014 ipMcastRouteNextHopClosestMemberHops Unsigned32, 1015 ipMcastRouteNextHopProtocol IANAipMRouteProtocol, 1016 ipMcastRouteNextHopPkts Counter32, 1017 ipMcastRouteNextHopOctets Counter32 1018 } 1020 ipMcastRouteNextHopGroupAddressType OBJECT-TYPE 1021 SYNTAX InetAddressType 1022 MAX-ACCESS not-accessible 1023 STATUS current 1024 DESCRIPTION 1025 "A value indicating the address family of the address 1026 contained in ipMcastRouteNextHopGroup. Legal values 1027 correspond to the subset of address families for which 1028 multicast forwarding is supported." 1029 ::= { ipMcastRouteNextHopEntry 1 } 1031 ipMcastRouteNextHopGroup OBJECT-TYPE 1032 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1033 MAX-ACCESS not-accessible 1034 STATUS current 1035 DESCRIPTION 1036 "The IP multicast group for which this entry specifies a 1037 next-hop on an outgoing interface." 1038 ::= { ipMcastRouteNextHopEntry 2 } 1040 ipMcastRouteNextHopSourceAddressType OBJECT-TYPE 1041 SYNTAX InetAddressType 1042 MAX-ACCESS not-accessible 1043 STATUS current 1044 DESCRIPTION 1045 "A value indicating the address family of the address 1046 contained in ipMcastRouteNextHopSource. The value MUST be 1047 the same as the value of ipMcastRouteNextHopGroupType." 1048 ::= { ipMcastRouteNextHopEntry 3 } 1050 ipMcastRouteNextHopSource OBJECT-TYPE 1051 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1052 MAX-ACCESS not-accessible 1053 STATUS current 1054 DESCRIPTION 1055 "The network address which when combined with the 1056 corresponding value of the mask specified in 1057 ipMcastRouteNextHopSourcePrefixLength identifies the sources 1058 for which this entry specifies a next-hop on an outgoing 1059 interface. 1061 This address object is only significant up to 1062 ipMcastRouteNextHopSourcePrefixLength bits. The remainder 1063 of the address bits are zero. This is especially important 1064 for this index field, which is part of the index of this 1065 entry. Any non-zero bits would signify an entirely 1066 different entry." 1067 ::= { ipMcastRouteNextHopEntry 4 } 1069 ipMcastRouteNextHopSourcePrefixLength OBJECT-TYPE 1070 SYNTAX InetAddressPrefixLength (4..128) 1071 MAX-ACCESS not-accessible 1072 STATUS current 1073 DESCRIPTION 1074 "The length in bits of the mask which when combined with the 1075 corresponding value specified in ipMcastRouteNextHopSource 1076 identifies the sources for which this entry specifies a 1077 next-hop on an outgoing interface." 1078 ::= { ipMcastRouteNextHopEntry 5 } 1080 ipMcastRouteNextHopIfIndex OBJECT-TYPE 1081 SYNTAX InterfaceIndex 1082 MAX-ACCESS not-accessible 1083 STATUS current 1084 DESCRIPTION 1085 "The ifIndex value of the interface for the outgoing 1086 interface for this next-hop." 1087 ::= { ipMcastRouteNextHopEntry 6 } 1089 ipMcastRouteNextHopAddressType OBJECT-TYPE 1090 SYNTAX InetAddressType 1091 MAX-ACCESS not-accessible 1092 STATUS current 1093 DESCRIPTION 1094 "A value indicating the address family of the address 1095 contained in ipMcastRouteNextHopAddress. The value MUST be 1096 the same as the value of ipMcastRouteNextHopGroupType." 1097 ::= { ipMcastRouteNextHopEntry 7 } 1099 ipMcastRouteNextHopAddress OBJECT-TYPE 1100 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1101 MAX-ACCESS not-accessible 1102 STATUS current 1103 DESCRIPTION 1104 "The address of the next-hop specific to this entry. For 1105 most interfaces, this is identical to 1106 ipMcastRouteNextHopGroup. NBMA interfaces, however, may 1107 have multiple next-hop addresses out a single outgoing 1108 interface." 1109 ::= { ipMcastRouteNextHopEntry 8 } 1111 ipMcastRouteNextHopState OBJECT-TYPE 1112 SYNTAX INTEGER { pruned(1), forwarding(2) } 1113 MAX-ACCESS read-only 1114 STATUS current 1115 DESCRIPTION 1116 "An indication of whether the outgoing interface and next- 1117 hop represented by this entry is currently being used to 1118 forward IP datagrams. The value 'forwarding' indicates it 1119 is currently being used; the value 'pruned' indicates it is 1120 not." 1121 ::= { ipMcastRouteNextHopEntry 9 } 1123 ipMcastRouteNextHopTimeStamp OBJECT-TYPE 1124 SYNTAX TimeStamp 1125 MAX-ACCESS read-only 1126 STATUS current 1127 DESCRIPTION 1128 "The value of sysUpTime at which the multicast routing 1129 information represented by this entry was learned by the 1130 router." 1132 ::= { ipMcastRouteNextHopEntry 10 } 1134 ipMcastRouteNextHopExpiryTime OBJECT-TYPE 1135 SYNTAX TimeTicks 1136 MAX-ACCESS read-only 1137 STATUS current 1138 DESCRIPTION 1139 "The minimum amount of time remaining before this entry will 1140 be aged out. If ipMcastRouteNextHopState is pruned(1), the 1141 remaining time until the prune expires and the state reverts 1142 to forwarding(2). Otherwise, the remaining time until this 1143 entry is removed from the table. The time remaining may be 1144 copied from ipMcastRouteExpiryTime if the protocol in use 1145 for this entry does not specify next-hop timers. The value 1146 0 indicates that the entry is not subject to aging." 1147 ::= { ipMcastRouteNextHopEntry 11 } 1149 ipMcastRouteNextHopClosestMemberHops OBJECT-TYPE 1150 SYNTAX Unsigned32 (0..255) 1151 MAX-ACCESS read-only 1152 STATUS current 1153 DESCRIPTION 1154 "The minimum number of hops between this router and any 1155 member of this IP multicast group reached via this next-hop 1156 on this outgoing interface. Any IP multicast datagrams for 1157 the group which have a TTL (IPv4) or Hop Count (IPv6) less 1158 than this number of hops will not be forwarded to this 1159 next-hop. 1161 This is an optimization applied by multicast routing 1162 protocols that explicitly track hop counts to downstream 1163 listeners. Multicast protocols that are not aware of hop 1164 counts to downstream listeners set this object to zero." 1165 ::= { ipMcastRouteNextHopEntry 12 } 1167 ipMcastRouteNextHopProtocol OBJECT-TYPE 1168 SYNTAX IANAipMRouteProtocol 1169 MAX-ACCESS read-only 1170 STATUS current 1171 DESCRIPTION 1172 "The routing mechanism via which this next-hop was learned." 1173 ::= { ipMcastRouteNextHopEntry 13 } 1175 ipMcastRouteNextHopPkts OBJECT-TYPE 1176 SYNTAX Counter32 1177 MAX-ACCESS read-only 1178 STATUS current 1179 DESCRIPTION 1180 "The number of packets which have been forwarded using this 1181 route. 1183 Discontinuities in this monotonically increasing value 1184 occur at re-initialization of the management system. 1185 Discontinuities can also occur as a result of routes being 1186 removed and replaced, which can be detected by observing 1187 the value of ipMcastRouteNextHopTimeStamp." 1188 ::= { ipMcastRouteNextHopEntry 14 } 1190 ipMcastRouteNextHopOctets OBJECT-TYPE 1191 SYNTAX Counter32 1192 MAX-ACCESS read-only 1193 STATUS current 1194 DESCRIPTION 1195 "The number of octets of multicast packets that have been 1196 forwarded using this route. 1198 Discontinuities in this monotonically increasing value 1199 occur at re-initialization of the management system. 1200 Discontinuities can also occur as a result of routes being 1201 removed and replaced, which can be detected by observing 1202 the value of ipMcastRouteNextHopTimeStamp." 1203 ::= { ipMcastRouteNextHopEntry 15 } 1205 -- 1206 -- The IP Multicast Scope Boundary Table 1207 -- 1209 ipMcastBoundaryTable OBJECT-TYPE 1210 SYNTAX SEQUENCE OF IpMcastBoundaryEntry 1211 MAX-ACCESS not-accessible 1212 STATUS current 1213 DESCRIPTION 1214 "The (conceptual) table listing the system's scoped 1215 multicast address boundaries." 1216 ::= { ipMcast 5 } 1218 ipMcastBoundaryEntry OBJECT-TYPE 1219 SYNTAX IpMcastBoundaryEntry 1220 MAX-ACCESS not-accessible 1221 STATUS current 1222 DESCRIPTION 1223 "An entry (conceptual row) in the ipMcastBoundaryTable 1224 representing a scoped boundary." 1225 INDEX { ipMcastBoundaryIfIndex, 1226 ipMcastBoundaryAddressType, 1227 ipMcastBoundaryAddress, 1228 ipMcastBoundaryAddressPrefixLength } 1229 ::= { ipMcastBoundaryTable 1 } 1231 IpMcastBoundaryEntry ::= SEQUENCE { 1232 ipMcastBoundaryIfIndex InterfaceIndex, 1233 ipMcastBoundaryAddressType InetAddressType, 1234 ipMcastBoundaryAddress InetAddress, 1235 ipMcastBoundaryAddressPrefixLength InetAddressPrefixLength, 1236 ipMcastBoundaryStatus RowStatus, 1237 ipMcastBoundaryStorageType StorageType, 1238 ipMcastBoundaryDroppedMcastOctets Counter32, 1239 ipMcastBoundaryDroppedMcastPkts Counter32, 1240 ipMcastBoundaryHCDroppedMcastOctets Counter64, 1241 ipMcastBoundaryHCDroppedMcastPkts Counter64 1242 } 1244 ipMcastBoundaryIfIndex OBJECT-TYPE 1245 SYNTAX InterfaceIndex 1246 MAX-ACCESS not-accessible 1247 STATUS current 1248 DESCRIPTION 1249 "The IfIndex value for the interface to which this boundary 1250 applies. Packets with a destination address in the 1251 associated address/mask range will not be forwarded out this 1252 interface." 1253 ::= { ipMcastBoundaryEntry 1 } 1255 ipMcastBoundaryAddressType OBJECT-TYPE 1256 SYNTAX InetAddressType 1257 MAX-ACCESS not-accessible 1258 STATUS current 1259 DESCRIPTION 1260 "A value indicating the address family of the address 1261 contained in ipMcastBoundaryAddress. Legal values 1262 correspond to the subset of address families for which 1263 multicast forwarding is supported." 1264 ::= { ipMcastBoundaryEntry 2 } 1266 ipMcastBoundaryAddress OBJECT-TYPE 1267 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1268 MAX-ACCESS not-accessible 1269 STATUS current 1270 DESCRIPTION 1271 "The group address which when combined with the 1272 corresponding value of ipMcastBoundaryAddressPrefixLength 1273 identifies the group range for which the scoped boundary 1274 exists. Scoped IPv4 addresses must come from the range 1275 239.x.x.x. Scoped IPv6 addresses must come from range 1276 ff.nn.nn.nn.nn.nn.nn.nn, where nn encodes the scope type and 1277 group identifier. 1279 This address object is only significant up to 1280 ipMcastBoundaryAddressPrefixLength bits. The remainder of 1281 the address bits are zero. This is especially important for 1282 this index field, which is part of the index of this entry. 1283 Any non-zero bits would signify an entirely different 1284 entry." 1285 REFERENCE "RFC 2365, RFC 4291" 1286 ::= { ipMcastBoundaryEntry 3 } 1288 ipMcastBoundaryAddressPrefixLength OBJECT-TYPE 1289 SYNTAX InetAddressPrefixLength (4..128) 1290 MAX-ACCESS not-accessible 1291 STATUS current 1292 DESCRIPTION 1293 "The length in bits of the mask which when combined with the 1294 corresponding value of ipMcastBoundaryAddress identifies the 1295 group range for which the scoped boundary exists." 1296 ::= { ipMcastBoundaryEntry 4 } 1298 ipMcastBoundaryStatus OBJECT-TYPE 1299 SYNTAX RowStatus 1300 MAX-ACCESS read-create 1301 STATUS current 1302 DESCRIPTION 1303 "The status of this row, by which rows in this table can 1304 be created and destroyed. 1306 This status object can be set to active(1) without setting 1307 any other columnar objects in this entry. 1309 All writeable objects in this entry can be modified when the 1310 status of this entry is active(1)." 1311 ::= { ipMcastBoundaryEntry 5 } 1313 ipMcastBoundaryStorageType OBJECT-TYPE 1314 SYNTAX StorageType 1315 MAX-ACCESS read-create 1316 STATUS current 1317 DESCRIPTION 1318 "The storage type for this row. Rows having the value 1319 'permanent' need not allow write-access to any columnar 1320 objects in the row." 1321 DEFVAL { nonVolatile } 1322 ::= { ipMcastBoundaryEntry 6 } 1324 ipMcastBoundaryDroppedMcastOctets OBJECT-TYPE 1325 SYNTAX Counter32 1326 MAX-ACCESS read-only 1327 STATUS current 1328 DESCRIPTION 1329 "The number of octets of multicast packets that have been 1330 dropped as a result of this zone boundary configuration." 1331 ::= { ipMcastBoundaryEntry 7 } 1333 ipMcastBoundaryDroppedMcastPkts OBJECT-TYPE 1334 SYNTAX Counter32 1335 MAX-ACCESS read-only 1336 STATUS current 1337 DESCRIPTION 1338 "The number of multicast packets that have been dropped as a 1339 result of this zone boundary configuration." 1340 ::= { ipMcastBoundaryEntry 8 } 1342 ipMcastBoundaryHCDroppedMcastOctets OBJECT-TYPE 1343 SYNTAX Counter64 1344 MAX-ACCESS read-only 1345 STATUS current 1346 DESCRIPTION 1347 "The number of octets of multicast packets that have been 1348 dropped as a result of this zone boundary configuration. 1350 This object is a 64-bit version of 1351 ipMcastBoundaryDroppedMcastOctets." 1352 ::= { ipMcastBoundaryEntry 9 } 1354 ipMcastBoundaryHCDroppedMcastPkts OBJECT-TYPE 1355 SYNTAX Counter64 1356 MAX-ACCESS read-only 1357 STATUS current 1358 DESCRIPTION 1359 "The number of multicast packets that have been dropped as a 1360 result of this zone boundary configuration. 1362 This object is a 64-bit version of 1363 ipMcastBoundaryDroppedMcastPkts." 1364 ::= { ipMcastBoundaryEntry 10 } 1366 -- 1367 -- The IP Multicast Scope Name Table 1368 -- 1370 ipMcastScopeNameTable OBJECT-TYPE 1371 SYNTAX SEQUENCE OF IpMcastScopeNameEntry 1372 MAX-ACCESS not-accessible 1373 STATUS current 1374 DESCRIPTION 1375 "The (conceptual) table listing multicast scope names." 1376 ::= { ipMcast 6 } 1378 ipMcastScopeNameEntry OBJECT-TYPE 1379 SYNTAX IpMcastScopeNameEntry 1380 MAX-ACCESS not-accessible 1381 STATUS current 1382 DESCRIPTION 1383 "An entry (conceptual row) in the ipMcastScopeNameTable 1384 representing a multicast scope name." 1385 INDEX { ipMcastScopeNameAddressType, 1386 ipMcastScopeNameAddress, 1387 ipMcastScopeNameAddressPrefixLength, 1388 IMPLIED ipMcastScopeNameLanguage } 1389 ::= { ipMcastScopeNameTable 1 } 1391 IpMcastScopeNameEntry ::= SEQUENCE { 1392 ipMcastScopeNameAddressType InetAddressType, 1393 ipMcastScopeNameAddress InetAddress, 1394 ipMcastScopeNameAddressPrefixLength InetAddressPrefixLength, 1395 ipMcastScopeNameLanguage LanguageTag, 1396 ipMcastScopeNameString SnmpAdminString, 1397 ipMcastScopeNameDefault TruthValue, 1398 ipMcastScopeNameStatus RowStatus, 1399 ipMcastScopeNameStorageType StorageType 1400 } 1402 ipMcastScopeNameAddressType OBJECT-TYPE 1403 SYNTAX InetAddressType 1404 MAX-ACCESS not-accessible 1405 STATUS current 1406 DESCRIPTION 1407 "A value indicating the address family of the address 1408 contained in ipMcastScopeNameAddress. Legal values 1409 correspond to the subset of address families for which 1410 multicast forwarding is supported." 1411 ::= { ipMcastScopeNameEntry 1 } 1413 ipMcastScopeNameAddress OBJECT-TYPE 1414 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1415 MAX-ACCESS not-accessible 1416 STATUS current 1417 DESCRIPTION 1418 "The group address which when combined with the 1419 corresponding value of ipMcastScopeNameAddressPrefixLength 1420 identifies the group range associated with the multicast 1421 scope. Scoped IPv4 addresses must come from the range 1422 239.x.x.x. Scoped IPv6 addresses must come from the range 1423 ff.nn.nn.nn.nn.nn.nn.nn, where nn encodes the scope type and 1424 group identifier. 1426 This address object is only significant up to 1427 ipMcastScopeNameAddressPrefixLength bits. The remainder of 1428 the address bits are zero. This is especially important for 1429 this index field, which is part of the index of this entry. 1430 Any non-zero bits would signify an entirely different 1431 entry." 1432 REFERENCE "RFC 2365, RFC 4291" 1433 ::= { ipMcastScopeNameEntry 2 } 1435 ipMcastScopeNameAddressPrefixLength OBJECT-TYPE 1436 SYNTAX InetAddressPrefixLength (4..128) 1437 MAX-ACCESS not-accessible 1438 STATUS current 1439 DESCRIPTION 1440 "The length in bits of the mask which when combined with the 1441 corresponding value of ipMcastScopeNameAddress identifies 1442 the group range associated with the multicast scope." 1443 ::= { ipMcastScopeNameEntry 3 } 1445 ipMcastScopeNameLanguage OBJECT-TYPE 1446 SYNTAX LanguageTag 1447 MAX-ACCESS not-accessible 1448 STATUS current 1449 DESCRIPTION 1450 "Language tag associated with the scope name." 1451 REFERENCE "RFC 3283" 1452 ::= { ipMcastScopeNameEntry 4 } 1454 ipMcastScopeNameString OBJECT-TYPE 1455 SYNTAX SnmpAdminString 1456 MAX-ACCESS read-create 1457 STATUS current 1458 DESCRIPTION 1459 "The textual name associated with the multicast scope. The 1460 value of this object should be suitable for displaying to 1461 end-users, such as when allocating a multicast address in 1462 this scope. When no name is specified, the default value of 1463 this object for IPv4 should be the string 239.x.x.x/y with x 1464 and y replaced appropriately to describe the address and 1465 mask length associated with the scope. Scoped IPv6 1466 addresses must come from range ff.nn.nn.nn.nn.nn.nn.nn, 1467 where nn encodes the scope type and group identifier." 1469 ::= { ipMcastScopeNameEntry 5 } 1471 ipMcastScopeNameDefault OBJECT-TYPE 1472 SYNTAX TruthValue 1473 MAX-ACCESS read-create 1474 STATUS current 1475 DESCRIPTION 1476 "If true, indicates a preference that the name in the 1477 following language should be used by applications if no name 1478 is available in a desired language." 1479 DEFVAL { false } 1480 ::= { ipMcastScopeNameEntry 6 } 1482 ipMcastScopeNameStatus OBJECT-TYPE 1483 SYNTAX RowStatus 1484 MAX-ACCESS read-create 1485 STATUS current 1486 DESCRIPTION 1487 "The status of this row, by which rows in this table can 1488 be created and destroyed. Before the row can be activated, 1489 the object ipMcastScopeNameString must be set to a valid 1490 value. All writeable objects in this entry can be modified 1491 when the status is active(1)." 1492 ::= { ipMcastScopeNameEntry 7 } 1494 ipMcastScopeNameStorageType OBJECT-TYPE 1495 SYNTAX StorageType 1496 MAX-ACCESS read-create 1497 STATUS current 1498 DESCRIPTION 1499 "The storage type for this row. Rows having the value 1500 'permanent' need not allow write-access to any columnar 1501 objects in the row." 1502 DEFVAL { nonVolatile } 1503 ::= { ipMcastScopeNameEntry 8 } 1505 -- 1506 -- The Multicast Listeners Table 1507 -- 1509 ipMcastLocalListenerTable OBJECT-TYPE 1510 SYNTAX SEQUENCE OF IpMcastLocalListenerEntry 1511 MAX-ACCESS not-accessible 1512 STATUS current 1513 DESCRIPTION 1514 "The (conceptual) table listing local applications or 1515 services that have joined multicast groups as listeners. 1517 Entries exist for all addresses in the multicast range for 1518 all applications and services as they are classified on this 1519 device." 1520 ::= { ipMcast 9 } 1522 ipMcastLocalListenerEntry OBJECT-TYPE 1523 SYNTAX IpMcastLocalListenerEntry 1524 MAX-ACCESS not-accessible 1525 STATUS current 1526 DESCRIPTION 1527 "An entry (conceptual row) in the LocalListenerTable." 1528 INDEX { ipMcastLocalListenerGroupAddressType, 1529 ipMcastLocalListenerGroupAddress, 1530 ipMcastLocalListenerSourceAddressType, 1531 ipMcastLocalListenerSourceAddress, 1532 ipMcastLocalListenerSourcePrefixLength, 1533 ipMcastLocalListenerRunIndex } 1534 ::= { ipMcastLocalListenerTable 1 } 1536 IpMcastLocalListenerEntry ::= SEQUENCE { 1537 ipMcastLocalListenerGroupAddressType InetAddressType, 1538 ipMcastLocalListenerGroupAddress InetAddress, 1539 ipMcastLocalListenerSourceAddressType InetAddressType, 1540 ipMcastLocalListenerSourceAddress InetAddress, 1541 ipMcastLocalListenerSourcePrefixLength InetAddressPrefixLength, 1542 ipMcastLocalListenerRunIndex Unsigned32 1543 } 1545 ipMcastLocalListenerGroupAddressType OBJECT-TYPE 1546 SYNTAX InetAddressType 1547 MAX-ACCESS not-accessible 1548 STATUS current 1549 DESCRIPTION 1550 "A value indicating the address family of the address 1551 contained in ipMcastLocalListenerGroupAddress. Legal values 1552 correspond to the subset of address families for which 1553 multicast is supported." 1554 ::= { ipMcastLocalListenerEntry 1 } 1556 ipMcastLocalListenerGroupAddress OBJECT-TYPE 1557 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1558 MAX-ACCESS not-accessible 1559 STATUS current 1560 DESCRIPTION 1561 "The IP multicast group for which this entry specifies 1562 locally joined applications or services." 1563 ::= { ipMcastLocalListenerEntry 2 } 1565 ipMcastLocalListenerSourceAddressType OBJECT-TYPE 1566 SYNTAX InetAddressType 1567 MAX-ACCESS not-accessible 1568 STATUS current 1569 DESCRIPTION 1570 "A value indicating the address family of the address 1571 contained in ipMcastLocalListenerSource. The value MUST be 1572 the same as the value of ipMcastLocalListenerAddressType." 1573 ::= { ipMcastLocalListenerEntry 3 } 1575 ipMcastLocalListenerSourceAddress OBJECT-TYPE 1576 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1577 MAX-ACCESS not-accessible 1578 STATUS current 1579 DESCRIPTION 1580 "The network address which when combined with the 1581 corresponding value of the mask specified in 1582 ipMcastLocalListenerSourcePrefixLength identifies the 1583 sources for which this entry specifies a local listener. 1585 This address object is only significant up to 1586 ipMcastLocalListenerSourcePrefixLength bits. The remainder 1587 of the address bits are zero. This is especially important 1588 for this index field, which is part of the index of this 1589 entry. Any non-zero bits would signify an entirely 1590 different entry." 1591 ::= { ipMcastLocalListenerEntry 4 } 1593 ipMcastLocalListenerSourcePrefixLength OBJECT-TYPE 1594 SYNTAX InetAddressPrefixLength (4..128) 1595 MAX-ACCESS not-accessible 1596 STATUS current 1597 DESCRIPTION 1598 "The length in bits of the mask which when combined with the 1599 corresponding value specified in ipMcastLocalListenerSource 1600 identifies the sources for which this entry specifies a 1601 locally listener. A mask length of zero corresponds to all 1602 sources within the group." 1603 ::= { ipMcastLocalListenerEntry 5 } 1605 ipMcastLocalListenerRunIndex OBJECT-TYPE 1606 SYNTAX Unsigned32 (0..2147483647) 1607 MAX-ACCESS read-only 1608 STATUS current 1609 DESCRIPTION 1610 "A unique value corresponding to a piece of software running 1611 on this router or host system. Where possible, this should 1612 be the system's native, unique identification number. 1614 This identifier is platform-specific. It may correspond to 1615 a process ID or application instance number. 1617 A value of zero indicates that the application instance(s) 1618 cannot be identified. A value of zero indicates that one or 1619 more unidentified applications have joined the specified 1620 multicast groups (for the specified sources) as listeners." 1621 REFERENCE "RFC 2287 sysApplRunIndex" 1622 ::= { ipMcastLocalListenerEntry 6 } 1624 -- 1625 -- Conformance information 1626 -- 1628 ipMcastMIBConformance 1629 OBJECT IDENTIFIER ::= { ipMcastMIB 2 } 1630 ipMcastMIBCompliances 1631 OBJECT IDENTIFIER ::= { ipMcastMIBConformance 1 } 1632 ipMcastMIBGroups OBJECT IDENTIFIER ::= { ipMcastMIBConformance 2 } 1634 -- 1635 -- Compliance statements 1636 -- 1638 ipMcastMIBCompliance MODULE-COMPLIANCE 1639 STATUS current 1640 DESCRIPTION 1641 "Implementations of all the mandatory MIB groups listed 1642 below can claim full compliance. 1644 This MIB contains several InetAddressType and InetAddress 1645 objects, but not all IP address types are supported by all 1646 protocol implementations. 1648 A MIB implementation can claim full compliance if all IP 1649 address types supported by the protocol implementation are 1650 supported by the MIB implementation." 1652 MODULE -- this module 1653 MANDATORY-GROUPS { ipMcastMIBBasicGroup } 1655 OBJECT ipMcastEnable 1656 MIN-ACCESS read-only 1657 DESCRIPTION 1658 "Write access is not required." 1660 GROUP ipMcastMIBRouteGroup 1661 DESCRIPTION 1662 "This group is mandatory if the system is a router." 1664 OBJECT ipMcastInterfaceTtl 1665 MIN-ACCESS read-only 1666 DESCRIPTION 1667 "Write access is not required." 1669 OBJECT ipMcastInterfaceRateLimit 1670 MIN-ACCESS read-only 1671 DESCRIPTION 1672 "Write access is not required." 1674 GROUP ipMcastMIBHopCountGroup 1675 DESCRIPTION 1676 "This group is optional." 1678 GROUP ipMcastMIBPktsOutGroup 1679 DESCRIPTION 1680 "This group is optional." 1682 GROUP ipMcastMIBHCInterfaceGroup 1683 DESCRIPTION 1684 "This group is mandatory only for those network interfaces 1685 for which the value of the corresponding instance of ifSpeed 1686 is greater than 20,000,000 bits/second." 1688 GROUP ipMcastMIBRouteProtoGroup 1689 DESCRIPTION 1690 "This group is mandatory if the system is a router." 1692 GROUP ipMcastMIBSsmGroup 1693 DESCRIPTION 1694 "This group is optional." 1696 GROUP ipMcastMIBLocalListenerGroup 1697 DESCRIPTION 1698 "This group is optional." 1700 GROUP ipMcastMIBBoundaryIfGroup 1701 DESCRIPTION 1702 "This group is mandatory if the system is a router that 1703 supports administratively-scoped multicast address 1704 boundaries." 1706 OBJECT ipMcastBoundaryStatus 1707 MIN-ACCESS read-only 1708 DESCRIPTION 1709 "Write access is not required." 1711 GROUP ipMcastMIBScopeNameGroup 1712 DESCRIPTION 1713 "This group is mandatory if the system is a router that 1714 supports multicast scope names." 1716 OBJECT ipMcastScopeNameString 1717 MIN-ACCESS read-only 1718 DESCRIPTION 1719 "Write access is not required." 1721 OBJECT ipMcastScopeNameDefault 1722 MIN-ACCESS read-only 1723 DESCRIPTION 1724 "Write access is not required." 1726 OBJECT ipMcastScopeNameStatus 1727 MIN-ACCESS read-only 1728 DESCRIPTION 1729 "Write access is not required." 1731 GROUP ipMcastMIBIfPktsGroup 1732 DESCRIPTION 1733 "This group is optional." 1735 GROUP ipMcastMIBRouteOctetsGroup 1736 DESCRIPTION 1737 "This group is optional." 1739 ::= { ipMcastMIBCompliances 1 } 1741 ipMcastMIBMRouteCompliance MODULE-COMPLIANCE 1742 STATUS deprecated 1743 DESCRIPTION 1744 "Implementations of this compliance statement are equivalent 1745 to compliance with the deprecated IPMROUTE-MIB module." 1747 MODULE -- this module 1748 MANDATORY-GROUPS { ipMcastMIBMRouteBasicGroup } 1750 ::= { ipMcastMIBCompliances 2 } 1751 -- 1752 -- Units of conformance 1753 -- 1754 ipMcastMIBMRouteBasicGroup OBJECT-GROUP 1755 OBJECTS { ipMcastEnable, ipMcastRouteEntryCount, 1756 ipMcastRouteUpstreamNeighborType, 1757 ipMcastRouteUpstreamNeighbor, ipMcastRouteInIfIndex, 1758 ipMcastRouteTimeStamp, ipMcastRouteExpiryTime, 1759 ipMcastRouteNextHopState, 1760 ipMcastRouteNextHopTimeStamp, 1761 ipMcastRouteNextHopExpiryTime, 1762 ipMcastRouteNextHopProtocol, 1763 ipMcastRouteNextHopPkts, 1764 ipMcastInterfaceTtl, 1765 ipMcastInterfaceProtocol, 1766 ipMcastInterfaceRateLimit, 1767 ipMcastInterfaceInMcastOctets, 1768 ipMcastInterfaceOutMcastOctets 1769 } 1770 STATUS deprecated 1771 DESCRIPTION 1772 "A collection of objects to support basic management of IP 1773 Multicast routing. 1775 This conformance group is deprecated. It is replaced by 1776 ipMcastMIBBasicGroup and ipMcastMIBRouteGroup" 1777 ::= { ipMcastMIBGroups 1 } 1779 ipMcastMIBHopCountGroup OBJECT-GROUP 1780 OBJECTS { ipMcastRouteNextHopClosestMemberHops } 1781 STATUS current 1782 DESCRIPTION 1783 "A collection of objects to support management of the use of 1784 hop counts in IP Multicast routing." 1785 ::= { ipMcastMIBGroups 2 } 1787 ipMcastMIBPktsOutGroup OBJECT-GROUP 1788 OBJECTS { ipMcastRouteNextHopPkts } 1789 STATUS current 1790 DESCRIPTION 1791 "A collection of objects to support management of packet 1792 counters for each outgoing interface entry of a route." 1793 ::= { ipMcastMIBGroups 3 } 1795 ipMcastMIBHCInterfaceGroup OBJECT-GROUP 1796 OBJECTS { ipMcastInterfaceHCInMcastOctets, 1797 ipMcastInterfaceHCOutMcastOctets, 1798 ipMcastInterfaceHCInMcastPkts, 1799 ipMcastInterfaceHCOutMcastPkts, 1800 ipMcastRouteHCOctets, 1801 ipMcastBoundaryHCDroppedMcastOctets, 1802 ipMcastBoundaryHCDroppedMcastPkts } 1803 STATUS current 1804 DESCRIPTION 1805 "A collection of objects providing information specific to 1806 high speed (greater than 20,000,000 bits/second) network 1807 interfaces." 1808 ::= { ipMcastMIBGroups 4 } 1810 ipMcastMIBRouteProtoGroup OBJECT-GROUP 1811 OBJECTS { ipMcastRouteProtocol, ipMcastRouteRtProtocol, 1812 ipMcastRouteRtAddressType, ipMcastRouteRtAddress, 1813 ipMcastRouteRtPrefixLength, ipMcastRouteRtType } 1814 STATUS current 1815 DESCRIPTION 1816 "A collection of objects providing information on the 1817 relationship between multicast routing information and the 1818 IP Forwarding Table." 1819 ::= { ipMcastMIBGroups 5 } 1821 ipMcastMIBBasicGroup OBJECT-GROUP 1822 OBJECTS { ipMcastEnable, ipMcastRouteEntryCount 1823 } 1824 STATUS current 1825 DESCRIPTION 1826 "A collection of objects to support basic management of IP 1827 Multicast protocols." 1828 ::= { ipMcastMIBGroups 6 } 1830 ipMcastMIBRouteGroup OBJECT-GROUP 1831 OBJECTS { ipMcastRouteUpstreamNeighborType, 1832 ipMcastRouteUpstreamNeighbor, ipMcastRouteInIfIndex, 1833 ipMcastRouteTimeStamp, ipMcastRouteExpiryTime, 1834 ipMcastRoutePkts, 1835 ipMcastRouteDifferentInIfPackets, 1836 ipMcastRouteOctets, 1837 ipMcastRouteNextHopState, ipMcastRouteNextHopTimeStamp, 1838 ipMcastRouteNextHopExpiryTime, 1839 ipMcastRouteNextHopProtocol, 1840 ipMcastRouteNextHopPkts, 1841 ipMcastInterfaceTtl, 1842 ipMcastInterfaceRateLimit, 1843 ipMcastInterfaceInMcastOctets, 1844 ipMcastInterfaceOutMcastOctets 1845 } 1846 STATUS current 1847 DESCRIPTION 1848 "A collection of objects to support basic management of IP 1849 Multicast routing." 1850 ::= { ipMcastMIBGroups 7 } 1852 ipMcastMIBSsmGroup OBJECT-GROUP 1853 OBJECTS { ipMcastSsmRangeRowStatus, ipMcastSsmRangeStorageType } 1854 STATUS current 1855 DESCRIPTION 1856 "A collection of objects to support management of the use of 1857 Source-Specific Multicast routing." 1858 ::= { ipMcastMIBGroups 8 } 1860 ipMcastMIBLocalListenerGroup OBJECT-GROUP 1861 OBJECTS { ipMcastLocalListenerRunIndex } 1862 STATUS current 1863 DESCRIPTION 1864 "A collection of objects to support management of local 1865 listeners on hosts or routers." 1866 ::= { ipMcastMIBGroups 9 } 1868 ipMcastMIBBoundaryIfGroup OBJECT-GROUP 1869 OBJECTS { ipMcastBoundaryStatus, 1870 ipMcastBoundaryStorageType, 1871 ipMcastBoundaryDroppedMcastOctets, 1872 ipMcastBoundaryDroppedMcastPkts } 1873 STATUS current 1874 DESCRIPTION 1875 "A collection of objects to support management of scoped 1876 multicast address boundaries." 1877 ::= { ipMcastMIBGroups 10 } 1879 ipMcastMIBScopeNameGroup OBJECT-GROUP 1880 OBJECTS { ipMcastScopeNameString, ipMcastScopeNameDefault, 1881 ipMcastScopeNameStatus, ipMcastScopeNameStorageType } 1882 STATUS current 1883 DESCRIPTION 1884 "A collection of objects to support management of multicast 1885 address scope names." 1886 ::= { ipMcastMIBGroups 11 } 1888 ipMcastMIBIfPktsGroup OBJECT-GROUP 1889 OBJECTS { ipMcastInterfaceInMcastPkts, 1890 ipMcastInterfaceOutMcastPkts } 1891 STATUS current 1892 DESCRIPTION 1893 "A collection of objects to support management of packet 1894 counters for each interface entry." 1895 ::= { ipMcastMIBGroups 12 } 1897 ipMcastMIBRouteOctetsGroup OBJECT-GROUP 1898 OBJECTS { ipMcastRouteOctets, ipMcastRouteNextHopOctets, 1899 ipMcastRouteDifferentInIfOctets } 1900 STATUS current 1901 DESCRIPTION 1902 "A collection of objects to support management of octet 1903 counters for each forwarding entry." 1904 ::= { ipMcastMIBGroups 13 } 1906 END 1908 6. Security Considerations 1910 6.1 SNMPv2 1912 SNMP versions prior to SNMPv3 did not include adequate security. 1913 Even if the network itself is secured (for example by using IPSec), 1914 there is still no control over whom on the secure network is allowed 1915 to access (read/change/create/delete) the objects in this MIB module. 1917 It is RECOMMENDED that implementers consider the security features as 1918 provided by the SNMPv3 framework (see [RFC3410], section 8), 1919 including full support for the SNMPv3 cryptographic mechanisms (for 1920 authentication and privacy). 1922 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1923 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1924 enable cryptographic security. It is then a customer/operator 1925 responsibility to ensure that the SNMP entity giving access to an 1926 instance of this MIB module is properly configured to give access to 1927 the objects only to those principals (users) that have legitimate 1928 rights to access (read/change/create/delete) them. 1930 6.2 Writeable objects 1932 There are a number of management objects defined in this MIB module 1933 with a MAX-ACCESS clause of read-write and/or read-create. This 1934 section discusses and lists these elements. 1936 Such objects may be considered sensitive or vulnerable in some 1937 network environments. The support for SET operations in a non-secure 1938 environment without proper protection can have a negative effect on 1939 network operations. 1941 In this MIB module, possible effects that can be induced by SET 1942 operations on writeable objects include: 1944 o Modifications multicast routing behavior that prevent or disrupt 1945 services provided by the network, including (but not limited to) 1946 multicast data traffic delivery. 1948 o Modifications multicast routing behavior that allow interception 1949 or subversion of information that is carried by the network. For 1950 example, attacks can be envisaged that would pass nominated 1951 multicast data streams through a nominated location, without the 1952 sources or listeners becoming aware of this subversion. 1954 The following are the read-write and read-create objects defined in 1955 this MIB module. 1957 ipMcastEnable 1958 ipMcastInterfaceTable 1959 ipMcastInterfaceEntry 1960 ipMcastInterfaceIfIndex 1961 ipMcastInterfaceTtl 1962 ipMcastInterfaceProtocol 1963 ipMcastInterfaceRateLimit 1964 ipMcastSsmRangeTable 1965 ipMcastSsmRangeEntry 1966 ipMcastSsmRangeAddressType 1967 ipMcastSsmRangeAddress 1968 ipMcastSsmRangePrefixLength 1969 ipMcastSsmRangeRowStatus 1970 ipMcastSsmRangeStorageType 1971 ipMcastBoundaryTable 1972 ipMcastBoundaryEntry 1973 ipMcastBoundaryIfIndex 1974 ipMcastBoundaryAddressType 1975 ipMcastBoundaryAddress 1976 ipMcastBoundaryAddressPrefixLength 1977 ipMcastBoundaryStatus 1978 ipMcastBoundaryStorageType 1979 ipMcastScopeNameTable 1980 ipMcastScopeNameEntry 1981 ipMcastScopeNameAddressType 1982 ipMcastScopeNameAddress 1983 ipMcastScopeNameAddressPrefixLength 1984 ipMcastScopeNameLanguage 1985 ipMcastScopeNameString 1986 ipMcastScopeNameDefault 1987 ipMcastScopeNameStatus 1988 ipMcastScopeNameStorageType 1990 6.3 Readable objects 1992 As well as the writeable objects discussed above, there are a number 1993 of readable objects (i.e., objects with a MAX-ACCESS other than not- 1994 accessible) that may be considered sensitive or vulnerable in some 1995 network environments. It is thus important to control even GET 1996 and/or NOTIFY access to these objects and possibly to even encrypt 1997 the values of these objects when sending them over the network via 1998 SNMP. 2000 In this MIB module, possible effects that can be induced by GET 2001 and/or NOTIFY operations include: 2003 o Determination of the topology, disposition, and composition of the 2004 network. This information may be commercially sensitive, and may 2005 also be used in preparation for attacks, including any of the 2006 attacks described above. 2008 o Determinion of whether multicast data is flowing in the network, 2009 or has flowed recently, as well as the locations of senders and 2010 recipients. An attacker can apply 'traffic analysis' to this 2011 data. In some cases, the information revealed by traffic analyses 2012 can be as damaging as full knowledge of the data being 2013 transported. 2015 The following are the read-only objects defined in this MIB module. 2017 ipMcastRouteEntryCount 2018 ipMcastInterfaceInMcastOctets 2019 ipMcastInterfaceOutMcastOctets 2020 ipMcastInterfaceInMcastPkts 2021 ipMcastInterfaceOutMcastPkts 2022 ipMcastInterfaceHCInMcastOctets 2023 ipMcastInterfaceHCOutMcastOctets 2024 ipMcastInterfaceHCInMcastPkts 2025 ipMcastInterfaceHCOutMcastPkts 2026 ipMcastRouteTable 2027 ipMcastRouteEntry 2028 ipMcastRouteGroupAddressType 2029 ipMcastRouteGroup 2030 ipMcastRouteGroupPrefixLength 2031 ipMcastRouteSourceAddressType 2032 ipMcastRouteSource 2033 ipMcastRouteSourcePrefixLength 2034 ipMcastRouteUpstreamNeighborType 2035 ipMcastRouteUpstreamNeighbor 2036 ipMcastRouteInIfIndex 2037 ipMcastRouteTimeStamp 2038 ipMcastRouteExpiryTime 2039 ipMcastRoutePkts 2040 ipMcastRouteDifferentInIfPackets 2041 ipMcastRouteOctets 2042 ipMcastRouteProtocol 2043 ipMcastRouteRtProtocol 2044 ipMcastRouteRtAddressType 2045 ipMcastRouteRtAddress 2046 ipMcastRouteRtPrefixLength 2047 ipMcastRouteRtType 2048 ipMcastRouteHCOctets 2049 ipMcastRouteDifferentInIfOctets 2050 ipMcastRouteNextHopTable 2051 ipMcastRouteNextHopEntry 2052 ipMcastRouteNextHopGroupAddressType 2053 ipMcastRouteNextHopGroup 2054 ipMcastRouteNextHopSourceAddressType 2055 ipMcastRouteNextHopSource 2056 ipMcastRouteNextHopSourcePrefixLength 2057 ipMcastRouteNextHopIfIndex 2058 ipMcastRouteNextHopAddressType 2059 ipMcastRouteNextHopAddress 2060 ipMcastRouteNextHopState 2061 ipMcastRouteNextHopTimeStamp 2062 ipMcastRouteNextHopExpiryTime 2063 ipMcastRouteNextHopClosestMemberHops 2064 ipMcastRouteNextHopProtocol 2065 ipMcastRouteNextHopPkts 2066 ipMcastRouteNextHopOctets 2067 ipMcastLocalListenerTable 2068 ipMcastLocalListenerEntry 2069 ipMcastLocalListenerGroupAddressType 2070 ipMcastLocalListenerGroupAddress 2071 ipMcastLocalListenerSourceAddressType 2072 ipMcastLocalListenerSourceAddress 2073 ipMcastLocalListenerSourcePrefixLength 2074 ipMcastLocalListenerRunIndex 2076 7. IANA Considerations 2078 IP-MCAST-MIB should be rooted under the mib-2 subtree. IANA is 2079 requested to assign { mib-2 XXX } to the IP-MCAST-MIB module 2080 specified in this document. 2082 8. Acknowledgements 2084 This MIB module is based on the original work in [RFC2932] by K. 2085 McCloghrie, D. Farinacci and D. Thaler. 2087 Suggested IPv6 multicast MIBs by R. Sivaramu and R. Raghunarayan have 2088 been used for comparison while editing this MIB module. 2090 The authors are also grateful to Bharat Joshi for his input and for 2091 several corrections. 2093 9. References 2094 9.1 Normative References 2096 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2097 Requirement Levels", BCP 14, RFC 2119, March 1997. 2099 [RFC2365] Meyer, D., "Administratively Scoped IP Multicast", BCP 23, 2100 RFC 2365, July 1998. 2102 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an 2103 IANA Considerations Section in RFCs", BCP 26, RFC 2434, 2104 October 1998. 2106 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2107 Schoenwaelder, Ed., "Structure of Management Information 2108 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2110 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2111 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 2112 STD 58, RFC 2579, April 1999. 2114 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2115 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2116 April 1999. 2118 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 2119 MIB", RFC 2863, June 2000. 2121 [RFC3283] Mahoney, B., Babics, G., and A. Taler, "Guide to Internet 2122 Calendaring", RFC 3283, June 2002. 2124 [RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 2125 Multicast Addresses", RFC 3306, August 2002. 2127 [RFC3569] Bhattacharyya, S., "An Overview of Source-Specific 2128 Multicast (SSM)", RFC 3569, July 2003. 2130 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2131 Schoenwaelder, "Textual Conventions for Internet Network 2132 Addresses", RFC 4001, February 2005. 2134 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 2135 Architecture", RFC 4291, February 2006. 2137 9.2 Informative References 2139 [RFC1075] Waitzman, D., Partridge, C., and S. Deering, "Distance 2140 Vector Multicast Routing Protocol", RFC 1075, 2141 November 1988. 2143 [RFC1584] Moy, J., "Multicast Extensions to OSPF", RFC 1584, 2144 March 1994. 2146 [RFC2189] Ballardie, T., "Core Based Trees (CBT version 2) Multicast 2147 Routing -- Protocol Specification --", RFC 2189, 2148 September 1997. 2150 [RFC2287] Krupczak, C. and J. Saperia, "Definitions of System-Level 2151 Managed Objects for Applications", RFC 2287, 2152 February 1998. 2154 [RFC2932] McCloghrie, K., Farinacci, D., and D. Thaler, "IPv4 2155 Multicast Routing MIB", RFC 2932, October 2000. 2157 [RFC2934] McCloghrie, K., Farinacci, D., Thaler, D., and B. Fenner, 2158 "Protocol Independent Multicast MIB for IPv4", RFC 2934, 2159 October 2000. 2161 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2162 "Introduction and Applicability Statements for Internet- 2163 Standard Management Framework", RFC 3410, December 2002. 2165 [I-D.ietf-pim-sm-v2-new] 2166 Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, 2167 "Protocol Independent Multicast - Sparse Mode PIM-SM): 2168 Protocol Specification (Revised)", 2169 draft-ietf-pim-sm-v2-new-12 (work in progress), 2170 March 2006. 2172 [I-D.ietf-pim-bidir] 2173 Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano, 2174 "Bi-directional Protocol Independent Multicast (BIDIR- 2175 PIM)", draft-ietf-pim-bidir-08 (work in progress), 2176 October 2005. 2178 Authors' Addresses 2180 David McWalter 2181 Data Connection Ltd 2182 100 Church Street 2183 Enfield EN2 6BQ 2184 UK 2186 Email: dmcw@dataconnection.com 2187 Dave Thaler 2188 Microsoft Corporation 2189 One Microsoft Way 2190 Redmond WA 98052-6399 2191 USA 2193 Email: dthaler@windows.microsoft.com 2195 Andrew Kessler 2196 Cisco Systems 2197 425 E. Tasman Drive 2198 San Jose CA 95134 2199 USA 2201 Email: kessler@cisco.com 2203 Intellectual Property Statement 2205 The IETF takes no position regarding the validity or scope of any 2206 Intellectual Property Rights or other rights that might be claimed to 2207 pertain to the implementation or use of the technology described in 2208 this document or the extent to which any license under such rights 2209 might or might not be available; nor does it represent that it has 2210 made any independent effort to identify any such rights. Information 2211 on the procedures with respect to rights in RFC documents can be 2212 found in BCP 78 and BCP 79. 2214 Copies of IPR disclosures made to the IETF Secretariat and any 2215 assurances of licenses to be made available, or the result of an 2216 attempt made to obtain a general license or permission for the use of 2217 such proprietary rights by implementers or users of this 2218 specification can be obtained from the IETF on-line IPR repository at 2219 http://www.ietf.org/ipr. 2221 The IETF invites any interested party to bring to its attention any 2222 copyrights, patents or patent applications, or other proprietary 2223 rights that may cover technology that may be required to implement 2224 this standard. Please address the information to the IETF at 2225 ietf-ipr@ietf.org. 2227 Disclaimer of Validity 2229 This document and the information contained herein are provided on an 2230 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2231 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 2232 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 2233 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 2234 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2235 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2237 Copyright Statement 2239 Copyright (C) The Internet Society (2006). This document is subject 2240 to the rights, licenses and restrictions contained in BCP 78, and 2241 except as set forth therein, the authors retain all their rights. 2243 Acknowledgment 2245 Funding for the RFC Editor function is currently provided by the 2246 Internet Society.