idnits 2.17.1 draft-ietf-mboned-ip-mcast-mib-00.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 2179. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2156. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2163. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2169. ** 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 (March 27, 2006) is 6604 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: 'RFC1766' is defined on line 2040, but no explicit reference was found in the text == Unused Reference: 'RFC2373' is defined on line 2049, but no explicit reference was found in the text == Unused Reference: 'RFC2434' is defined on line 2052, but no explicit reference was found in the text == Unused Reference: 'RFC3306' is defined on line 2071, but no explicit reference was found in the text == Unused Reference: 'RFC1075' is defined on line 2083, but no explicit reference was found in the text == Unused Reference: 'RFC1584' is defined on line 2087, but no explicit reference was found in the text == Unused Reference: 'RFC2189' is defined on line 2090, but no explicit reference was found in the text == Unused Reference: 'RFC2287' is defined on line 2094, but no explicit reference was found in the text == Unused Reference: 'RFC2934' is defined on line 2101, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-pim-sm-v2-new' is defined on line 2109, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-pim-bidir' is defined on line 2116, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1766 (Obsoleted by RFC 3066, RFC 3282) ** Obsolete normative reference: RFC 2373 (Obsoleted by RFC 3513) ** Obsolete normative reference: RFC 2434 (Obsoleted by RFC 5226) ** 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-07 Summary: 8 errors (**), 0 flaws (~~), 17 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 IETF D. McWalter 3 Internet-Draft Data Connection Ltd 4 Expires: September 28, 2006 D. Thaler 5 Microsoft Corporation 6 Obsoletes (if approved): RFC2932 A. Kessler 7 Cisco Systems 8 March 27, 2006 10 IP Multicast MIB 11 draft-ietf-mboned-ip-mcast-mib-00.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 September 28, 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 . . . . . . . . . . . . . . . . . . . 40 58 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 43 59 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 43 60 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 43 61 9.1 Normative References . . . . . . . . . . . . . . . . . . . 43 62 9.2 Informative References . . . . . . . . . . . . . . . . . . 44 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 45 64 Intellectual Property and Copyright Statements . . . . . . . . 47 66 1. Introduction 68 This MIB describes objects used for managing IP multicast function, 69 including IP multicast routing. These objects are independent of the 70 specific multicast routing protocol in use. Managed objects specific 71 to particular multicast protocols are defined elsewhere. 73 2. History 75 This document obsoletes [RFC2932]. The MIB module defined by this 76 document is a re-working of the MIB module from [RFC2932], with 77 changes that include the following. 79 o This MIB module is independent of address type, whereas [RFC2932] 80 only supported IPv4. 82 o This MIB module allows several multicast protocols to perform 83 routing on a single interface, where [RFC2932] assumed each 84 interface supported at most one multicast routing protocol. 86 o This MIB module includes objects that are not specific to 87 multicast routing. It allows management of multicast function on 88 systems that do not perform routing, whereas RFC 2932 was 89 restricted to multicast routing. 91 o This MIB module includes a table of Source-Specific Multicast 92 (SSM) address ranges to which SSM semantics [RFC3569] should be 93 applied. 95 o This MIB module includes a table of local applications that are 96 receiving multicast data. 98 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 99 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 100 document are to be interpreted as described in [RFC2119]. 102 3. The Internet-Standard Management Framework 104 For a detailed overview of the documents that describe the current 105 Internet-Standard Management Framework, please refer to section 7 of 106 [RFC3410]. 108 Managed objects are accessed via a virtual information store, termed 109 the Management Information Base or MIB. MIB objects are generally 110 accessed through the Simple Network Management Protocol (SNMP). 111 Objects in the MIB are defined using the mechanisms defined in the 112 Structure of Management Information (SMI). This memo specifies a MIB 113 module that is compliant to the SMIv2, which is described in STD 58, 115 [RFC2578], STD 58, [RFC2579] and STD 58, [RFC2580]. 117 4. Overview 119 This MIB module contains two scalars and seven tables. The tables 120 are: 122 1. The IP Multicast Interface Table containing multicast information 123 specific to interfaces. 125 2. The IP Multicast SSM Range Table, which contains one row per 126 range of multicast group addresses to which Source-Specific 127 Multicast semantics [RFC3569] should be applied. 129 3. The IP Multicast Route Table containing multicast routing 130 information for IP datagrams sent by particular sources to the IP 131 multicast groups known to a system. 133 4. The IP Multicast Routing Next Hop Table containing information on 134 next-hops for the routing of IP multicast datagrams. Each entry 135 is one of a list of next-hops on outgoing interfaces for 136 particular sources sending to a particular multicast group 137 address. 139 5. The IP Multicast Scope Boundary Table containing the boundaries 140 configured for multicast scopes [RFC2365]. 142 6. The IP Multicast Scope Name Table containing human-readable names 143 of multicast scope. 145 7. The IP Multicast Local Listener Table containing identifiers for 146 local applications that are receiving multicast data. 148 This MIB module uses textual conventions defined in the IF-MIB 149 [RFC2863], the INET-ADDRESS-MIB [RFC4001] and the IANA-RTPROTO-MIB. 151 5. Definitions 153 IPMCAST-MIB DEFINITIONS ::= BEGIN 155 IMPORTS 156 MODULE-IDENTITY, OBJECT-TYPE, 157 mib-2, Unsigned32, Counter32, 158 Counter64, Gauge32, TimeTicks FROM SNMPv2-SMI 159 RowStatus, TEXTUAL-CONVENTION, 160 TruthValue, StorageType, 161 TimeStamp FROM SNMPv2-TC 162 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 163 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 164 InterfaceIndexOrZero, 165 InterfaceIndex FROM IF-MIB 166 IANAipRouteProtocol, 167 IANAipMRouteProtocol FROM IANA-RTPROTO-MIB 168 InetAddress, InetAddressType, 169 InetAddressPrefixLength FROM INET-ADDRESS-MIB; 171 ipMcastMIB MODULE-IDENTITY 172 LAST-UPDATED "200603270000Z" -- 27 March 2006 173 ORGANIZATION "IETF MBONED Working Group" 174 CONTACT-INFO "David McWalter 175 Data Connection Limited 176 100 Church Street 177 Enfield, EN2 6BQ 178 UK 180 Phone: +44 208 366 1177 181 EMail: dmcw@dataconnection.com 183 Dave Thaler 184 Microsoft Corporation 185 One Microsoft Way 186 Redmond, WA 98052-6399 187 US 189 Phone: +1 425 703 8835 190 EMail: dthaler@dthaler.microsoft.com 192 Andrew Kessler 193 Cisco Systems 194 425 E. Tasman Drive 195 San Jose, CA 95134 196 US 198 Phone: +1 408 526 5139 199 EMail: kessler@cisco.com" 200 DESCRIPTION 201 "The MIB module for management of IP Multicast function. 203 This MIB module contains information about IP Multicast 204 routing, data forwarding, and data reception. This MIB 205 module is independent of the multicast protocol(s) and 206 address type(s) that are in use. 208 Copyright (C) The Internet Society (2006). This version of 209 this MIB module is part of RFC yyyy; see the RFC itself for 210 full legal notices." 212 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 213 REVISION "200603270000Z" -- 27 March 2006 214 DESCRIPTION 215 "Changes from RFC 2932: 217 1) This MIB module is independent of address type, whereas 218 RFC 2932 only supported IPv4. 219 2) This MIB module allows several multicast protocols to 220 perform routing on a single interface, whereas RFC 2932 221 assumed each interface supported at most one multicast 222 routing protocol. This MIB module retains but deprecates 223 the object ipMcastInterfaceProtocol. 224 3) This MIB module includes objects that are not specific to 225 multicast routing. It allows management of multicast 226 function on systems that do not perform routing, whereas 227 RFC 2932 was restricted to multicast routing. 228 4) This MIB module includes a table of Source-Specific 229 Multicast (SSM) address ranges to which RFC 3569 SSM 230 semantics should be applied. 231 5) This MIB module includes a table of local applications 232 that are receiving multicast data. 234 Published as RFC yyyy." 235 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 236 ::= { mib-2 XXX } 237 -- RFC Ed.: replace XXX with IANA-assigned number & remove this note 239 -- 240 -- Textual conventions 241 -- 243 LanguageTag ::= TEXTUAL-CONVENTION 245 DISPLAY-HINT "99a" 246 STATUS current 247 DESCRIPTION 248 "A language tag with all alphabetic characters converted to 249 lowercase. This restriction is intended to make the lexical 250 ordering imposed by SNMP useful when applied to language 251 tags. Note that it is theoretically possible for a valid 252 language tag to exceed the allowed length of this syntax, 253 and thus be impossible to represent with this syntax. 254 Sampling of language tags in current use on the Internet 255 suggests that this limit does not pose a serious problem in 256 practice." 257 REFERENCE "RFC 1766" 258 SYNTAX OCTET STRING (SIZE (1..99)) 260 -- 261 -- Top-level structure of the MIB 262 -- 264 ipMcastMIBObjects OBJECT IDENTIFIER ::= { ipMcastMIB 1 } 266 ipMcast OBJECT IDENTIFIER ::= { ipMcastMIBObjects 1 } 268 ipMcastEnable OBJECT-TYPE 269 SYNTAX INTEGER { enabled(1), disabled(2) } 270 MAX-ACCESS read-write 271 STATUS current 272 DESCRIPTION 273 "The enabled status of IP Multicast function on this 274 system." 275 ::= { ipMcast 1 } 277 ipMcastRouteEntryCount OBJECT-TYPE 278 SYNTAX Gauge32 279 MAX-ACCESS read-only 280 STATUS current 281 DESCRIPTION 282 "The number of rows in the ipMcastRouteTable. This can be 283 used to check for multicast routing activity, and to monitor 284 the multicast routing table size." 285 ::= { ipMcast 7 } 287 -- 288 -- The Multicast Interface Table 289 -- 291 ipMcastInterfaceTable OBJECT-TYPE 292 SYNTAX SEQUENCE OF IpMcastInterfaceEntry 293 MAX-ACCESS not-accessible 294 STATUS current 295 DESCRIPTION 296 "The (conceptual) table used to manage the multicast 297 protocol active on an interface." 298 ::= { ipMcast 4 } 300 ipMcastInterfaceEntry OBJECT-TYPE 301 SYNTAX IpMcastInterfaceEntry 302 MAX-ACCESS not-accessible 303 STATUS current 304 DESCRIPTION 305 "An entry (conceptual row) containing the multicast protocol 306 information for a particular interface." 307 INDEX { ipMcastInterfaceIfIndex } 308 ::= { ipMcastInterfaceTable 1 } 310 IpMcastInterfaceEntry ::= SEQUENCE { 311 ipMcastInterfaceIfIndex InterfaceIndex, 312 ipMcastInterfaceTtl Unsigned32, 313 ipMcastInterfaceProtocol IANAipMRouteProtocol, 314 ipMcastInterfaceRateLimit Unsigned32, 315 ipMcastInterfaceInMcastOctets Counter32, 316 ipMcastInterfaceOutMcastOctets Counter32, 317 ipMcastInterfaceInMcastPkts Counter32, 318 ipMcastInterfaceOutMcastPkts Counter32, 319 ipMcastInterfaceHCInMcastOctets Counter64, 320 ipMcastInterfaceHCOutMcastOctets Counter64, 321 ipMcastInterfaceHCInMcastPkts Counter64, 322 ipMcastInterfaceHCOutMcastPkts Counter64 323 } 325 ipMcastInterfaceIfIndex OBJECT-TYPE 326 SYNTAX InterfaceIndex 327 MAX-ACCESS not-accessible 328 STATUS current 329 DESCRIPTION 330 "The ifIndex value of the interface for which this entry 331 contains information." 332 ::= { ipMcastInterfaceEntry 1 } 334 ipMcastInterfaceTtl OBJECT-TYPE 335 SYNTAX Unsigned32 (0..255) 336 MAX-ACCESS read-write 337 STATUS current 338 DESCRIPTION 339 "The datagram TTL threshold for the interface. Any IP 340 multicast datagrams with a TTL (IPv4) or Hop Count (IPv6) 341 less than this threshold will not be forwarded out the 342 interface. The default value of 0 means all multicast 343 packets are forwarded out the interface." 344 DEFVAL { 0 } 345 ::= { ipMcastInterfaceEntry 2 } 347 ipMcastInterfaceProtocol OBJECT-TYPE 348 SYNTAX IANAipMRouteProtocol 349 MAX-ACCESS read-write 350 STATUS deprecated 351 DESCRIPTION 352 "The multicast protocol running on this interface. 354 More than one multicast protocol can be used on an 355 interface, so this object is ambiguous. Use of this 356 object is deprecated." 357 ::= { ipMcastInterfaceEntry 3 } 359 ipMcastInterfaceRateLimit OBJECT-TYPE 360 SYNTAX Unsigned32 (0..2147483647) 361 MAX-ACCESS read-write 362 STATUS current 363 DESCRIPTION 364 "The rate-limit, in kilobits per second, of forwarded 365 multicast traffic on the interface. A rate-limit of 0 366 indicates that no rate limiting is done." 367 DEFVAL { 0 } 368 ::= { ipMcastInterfaceEntry 4 } 370 ipMcastInterfaceInMcastOctets OBJECT-TYPE 371 SYNTAX Counter32 372 MAX-ACCESS read-only 373 STATUS current 374 DESCRIPTION 375 "The number of octets of multicast packets that have arrived 376 on the interface, including framing characters. This object 377 is similar to ifInOctets in the Interfaces MIB, except that 378 only multicast packets are counted." 379 ::= { ipMcastInterfaceEntry 5 } 381 ipMcastInterfaceOutMcastOctets OBJECT-TYPE 382 SYNTAX Counter32 383 MAX-ACCESS read-only 384 STATUS current 385 DESCRIPTION 386 "The number of octets of multicast packets that have been 387 sent on the interface." 388 ::= { ipMcastInterfaceEntry 6 } 390 ipMcastInterfaceInMcastPkts OBJECT-TYPE 391 SYNTAX Counter32 392 MAX-ACCESS read-only 393 STATUS current 394 DESCRIPTION 395 "The number of multicast packets that have arrived on the 396 interface. In many cases, this object is identical to 397 ifInMulticastPkts in the Interfaces MIB. 399 However, some implementations use ifXTable for Layer 2 400 traffic statistics and ipMcastInterfaceTable at Layer 3. In 401 this case a difference between these objects probably 402 indicates that some Layer 3 multicast packets are being 403 transmitted as unicast at Layer 2." 405 REFERENCE "RFC 2863 ifInMulticastPkts" 406 ::= { ipMcastInterfaceEntry 7 } 408 ipMcastInterfaceOutMcastPkts OBJECT-TYPE 409 SYNTAX Counter32 410 MAX-ACCESS read-only 411 STATUS current 412 DESCRIPTION 413 "The number of multicast packets that have been sent on the 414 interface. In many cases, this object is identical to 415 ifOutMulticastPkts in the Interfaces MIB. 417 However, some implementations use ifXTable for Layer 2 418 traffic statistics and ipMcastInterfaceTable at Layer 3. In 419 this case a difference between these objects probably 420 indicates that some Layer 3 multicast packets are being 421 transmitted as unicast at Layer 2." 422 REFERENCE "RFC 2863 ifOutMulticastPkts" 423 ::= { ipMcastInterfaceEntry 8 } 425 ipMcastInterfaceHCInMcastOctets OBJECT-TYPE 426 SYNTAX Counter64 427 MAX-ACCESS read-only 428 STATUS current 429 DESCRIPTION 430 "The number of octets of multicast packets that have arrived 431 on the interface, including framing characters. This object 432 is a 64-bit version of ipMcastRouteInterfaceInMcastOctets. 433 It is similar to ifHCInOctets in the Interfaces MIB, except 434 that only multicast packets are counted." 435 ::= { ipMcastInterfaceEntry 9 } 437 ipMcastInterfaceHCOutMcastOctets OBJECT-TYPE 438 SYNTAX Counter64 439 MAX-ACCESS read-only 440 STATUS current 441 DESCRIPTION 442 "The number of octets of multicast packets that have been 443 sent on the interface. This object is a 64-bit version of 444 ipMcastRouteInterfaceOutMcastOctets." 445 ::= { ipMcastInterfaceEntry 10 } 447 ipMcastInterfaceHCInMcastPkts OBJECT-TYPE 448 SYNTAX Counter64 449 MAX-ACCESS read-only 450 STATUS current 451 DESCRIPTION 452 "The number of multicast packets that have arrived on the 453 interface. In many cases, this object is identical to 454 ifHCInMulticastPkts in the Interfaces MIB. 456 However, some implementations use ifXTable for Layer 2 457 traffic statistics and ipMcastInterfaceTable at Layer 3. In 458 this case a difference between these objects probably 459 indicates that some Layer 3 multicast packets are being 460 transmitted as unicast at Layer 2." 461 REFERENCE "RFC 2863 ifHCInMulticastPkts" 462 ::= { ipMcastInterfaceEntry 11 } 464 ipMcastInterfaceHCOutMcastPkts OBJECT-TYPE 465 SYNTAX Counter64 466 MAX-ACCESS read-only 467 STATUS current 468 DESCRIPTION 469 "The number of multicast packets that have been sent on the 470 interface. In many cases, this object is identical to 471 ifHCOutMulticastPkts in the Interfaces MIB. 473 However, some implementations use ifXTable for Layer 2 474 traffic statistics and ipMcastInterfaceTable at Layer 3. In 475 this case a difference between these objects probably 476 indicates that some Layer 3 multicast packets are being 477 transmitted as unicast at Layer 2." 478 REFERENCE "RFC 2863 ifHCOutMulticastPkts" 479 ::= { ipMcastInterfaceEntry 12 } 481 -- 482 -- The SSM Range Table 483 -- 485 ipMcastSsmRangeTable OBJECT-TYPE 486 SYNTAX SEQUENCE OF IpMcastSsmRangeEntry 487 MAX-ACCESS not-accessible 488 STATUS current 489 DESCRIPTION 490 "This table is used to create and manage the range(s) of 491 group addresses to which SSM semantics should be applied." 492 REFERENCE "RFC 3569" 493 ::= { ipMcast 8 } 495 ipMcastSsmRangeEntry OBJECT-TYPE 496 SYNTAX IpMcastSsmRangeEntry 497 MAX-ACCESS not-accessible 498 STATUS current 499 DESCRIPTION 500 "An entry (conceptual row) in the ssmRangeTable." 502 INDEX { ipMcastSsmRangeAddressType, 503 ipMcastSsmRangeAddress, 504 ipMcastSsmRangePrefixLength } 505 ::= { ipMcastSsmRangeTable 1 } 507 IpMcastSsmRangeEntry ::= SEQUENCE { 508 ipMcastSsmRangeAddressType InetAddressType, 509 ipMcastSsmRangeAddress InetAddress, 510 ipMcastSsmRangePrefixLength InetAddressPrefixLength, 511 ipMcastSsmRangeRowStatus RowStatus, 512 ipMcastSsmRangeStorageType StorageType 513 } 515 ipMcastSsmRangeAddressType OBJECT-TYPE 516 SYNTAX InetAddressType 517 MAX-ACCESS not-accessible 518 STATUS current 519 DESCRIPTION 520 "The address type of the multicast group prefix." 521 ::= { ipMcastSsmRangeEntry 1 } 523 ipMcastSsmRangeAddress OBJECT-TYPE 524 SYNTAX InetAddress (SIZE (4|8|16|20)) 525 MAX-ACCESS not-accessible 526 STATUS current 527 DESCRIPTION 528 "The multicast group address which, when combined with 529 ipMcastSsmRangePrefixLength, gives the group prefix for this 530 SSM range. The InetAddressType is given by the 531 ipMcastSsmRangeAddressType object. 533 This address object is only significant up to 534 ipMcastSsmRangePrefixLength bits. The remainder of the 535 address bits are zero. This is especially important for 536 this index field, which is part of the index of this entry. 537 Any non-zero bits would signify an entirely different 538 entry. 540 For IPv6 SSM address ranges, only ranges within the space 541 FF3x::/32 are permitted (where 'x' is any valid scope). 543 To configure non-global scope SSM range entries within a 544 zone, consistent ipMcastBoundaryTable entries are required 545 on routers at the zone boundary." 546 REFERENCE "RFC 2373 section 2.7 and RFC 3306 section 6" 547 ::= { ipMcastSsmRangeEntry 2 } 549 ipMcastSsmRangePrefixLength OBJECT-TYPE 550 SYNTAX InetAddressPrefixLength (4..128) 551 MAX-ACCESS not-accessible 552 STATUS current 553 DESCRIPTION 554 "The multicast group prefix length, which, when combined 555 with ipMcastSsmRangeAddress, gives the group prefix for this 556 SSM range. The InetAddressType is given by the 557 ipMcastSsmRangeAddressType object. If 558 'ipv4' or 'ipv4z', this object must be in the range 4..32. 559 If ipMcastSsmRangeAddressType is 'ipv6' or 'ipv6z', this 560 object must be in the range 8..128." 561 ::= { ipMcastSsmRangeEntry 3 } 563 ipMcastSsmRangeRowStatus OBJECT-TYPE 564 SYNTAX RowStatus 565 MAX-ACCESS read-create 566 STATUS current 567 DESCRIPTION 568 "The status of this row, by which rows in this table can 569 be created and destroyed. 571 This status object can be set to active(1) without setting 572 any other columnar objects in this entry. 574 All writeable objects in this entry can be modified when the 575 status of this entry is active(1)." 576 ::= { ipMcastSsmRangeEntry 4 } 578 ipMcastSsmRangeStorageType OBJECT-TYPE 579 SYNTAX StorageType 580 MAX-ACCESS read-create 581 STATUS current 582 DESCRIPTION 583 "The storage type for this row. Rows having the value 584 'permanent' need not allow write-access to any columnar 585 objects in the row." 586 DEFVAL { nonVolatile } 587 ::= { ipMcastSsmRangeEntry 5 } 589 -- 590 -- The IP Multicast Routing Table 591 -- 593 ipMcastRouteTable OBJECT-TYPE 594 SYNTAX SEQUENCE OF IpMcastRouteEntry 595 MAX-ACCESS not-accessible 596 STATUS current 597 DESCRIPTION 598 "The (conceptual) table containing multicast routing 599 information for IP datagrams sent by particular sources to 600 to the IP multicast groups known to this router." 601 ::= { ipMcast 2 } 603 ipMcastRouteEntry OBJECT-TYPE 604 SYNTAX IpMcastRouteEntry 605 MAX-ACCESS not-accessible 606 STATUS current 607 DESCRIPTION 608 "An entry (conceptual row) containing the multicast routing 609 information for IP datagrams from a particular source and 610 addressed to a particular IP multicast group address." 611 INDEX { ipMcastRouteGroupAddressType, 612 ipMcastRouteGroup, 613 ipMcastRouteGroupPrefixLength, 614 ipMcastRouteSourceAddressType, 615 ipMcastRouteSource, 616 ipMcastRouteSourcePrefixLength } 617 ::= { ipMcastRouteTable 1 } 619 IpMcastRouteEntry ::= SEQUENCE { 620 ipMcastRouteGroupAddressType InetAddressType, 621 ipMcastRouteGroup InetAddress, 622 ipMcastRouteGroupPrefixLength InetAddressPrefixLength, 623 ipMcastRouteSourceAddressType InetAddressType, 624 ipMcastRouteSource InetAddress, 625 ipMcastRouteSourcePrefixLength InetAddressPrefixLength, 626 ipMcastRouteUpstreamNeighborType InetAddressType, 627 ipMcastRouteUpstreamNeighbor InetAddress, 628 ipMcastRouteInIfIndex InterfaceIndexOrZero, 629 ipMcastRouteTimeStamp TimeStamp, 630 ipMcastRouteExpiryTime TimeTicks, 631 ipMcastRoutePkts Counter32, 632 ipMcastRouteDifferentInIfPackets Counter32, 633 ipMcastRouteOctets Counter32, 634 ipMcastRouteProtocol IANAipMRouteProtocol, 635 ipMcastRouteRtProtocol IANAipRouteProtocol, 636 ipMcastRouteRtAddressType InetAddressType, 637 ipMcastRouteRtAddress InetAddress, 638 ipMcastRouteRtPrefixLength InetAddressPrefixLength, 639 ipMcastRouteRtType INTEGER, 640 ipMcastRouteHCOctets Counter64, 641 ipMcastRouteDifferentInIfOctets Counter32 642 } 644 ipMcastRouteGroupAddressType OBJECT-TYPE 645 SYNTAX InetAddressType 646 MAX-ACCESS not-accessible 647 STATUS current 648 DESCRIPTION 649 "A value indicating the address family of the address 650 contained in ipMcastRouteGroup. Legal values correspond to 651 the subset of address families for which multicast 652 forwarding is supported." 653 ::= { ipMcastRouteEntry 1 } 655 ipMcastRouteGroup OBJECT-TYPE 656 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 657 MAX-ACCESS not-accessible 658 STATUS current 659 DESCRIPTION 660 "The IP multicast group address which when combined with the 661 corresponding value specified in 662 ipMcastRouteGroupPrefixLength identifies the groups for 663 which this entry contains multicast routing information. 665 This address object is only significant up to 666 ipMcastRouteGroupPrefixLength bits. The remainder of the 667 address bits are zero. This is especially important for 668 this index field, which is part of the index of this entry. 669 Any non-zero bits would signify an entirely different 670 entry." 671 ::= { ipMcastRouteEntry 2 } 673 ipMcastRouteGroupPrefixLength OBJECT-TYPE 674 SYNTAX InetAddressPrefixLength (4..128) 675 MAX-ACCESS not-accessible 676 STATUS current 677 DESCRIPTION 678 "The length in bits of the mask which when combined with the 679 corresponding value of ipMcastRouteGroup identifies the 680 groups for which this entry contains multicast routing 681 information." 682 ::= { ipMcastRouteEntry 3 } 684 ipMcastRouteSourceAddressType OBJECT-TYPE 685 SYNTAX InetAddressType 686 MAX-ACCESS not-accessible 687 STATUS current 688 DESCRIPTION 689 "A value indicating the address family of the address 690 contained in ipMcastRouteSource. The value MUST be the same 691 as the value of ipMcastRouteGroupType." 692 ::= { ipMcastRouteEntry 4 } 694 ipMcastRouteSource OBJECT-TYPE 695 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 696 MAX-ACCESS not-accessible 697 STATUS current 698 DESCRIPTION 699 "The network address which when combined with the 700 corresponding value of ipMcastRouteSourcePrefixLength 701 identifies the sources for which this entry contains 702 multicast routing information. 704 This address object is only significant up to 705 ipMcastRouteGroupPrefixLength bits. The remainder of the 706 address bits are zero. This is especially important for 707 this index field, which is part of the index of this entry. 708 Any non-zero bits would signify an entirely different 709 entry." 710 ::= { ipMcastRouteEntry 5 } 712 ipMcastRouteSourcePrefixLength OBJECT-TYPE 713 SYNTAX InetAddressPrefixLength (4..128) 714 MAX-ACCESS not-accessible 715 STATUS current 716 DESCRIPTION 717 "The length in bits of the mask which when combined with the 718 corresponding value of ipMcastRouteSource identifies the 719 sources for which this entry contains multicast routing 720 information." 721 ::= { ipMcastRouteEntry 6 } 723 ipMcastRouteUpstreamNeighborType OBJECT-TYPE 724 SYNTAX InetAddressType 725 MAX-ACCESS read-only 726 STATUS current 727 DESCRIPTION 728 "A value indicating the address family of the address 729 contained in ipMcastRouteUpstreamNeighbor. The value MUST 730 be the same as the value of ipMcastRouteGroupType." 731 ::= { ipMcastRouteEntry 7 } 733 ipMcastRouteUpstreamNeighbor OBJECT-TYPE 734 SYNTAX InetAddress 735 MAX-ACCESS read-only 736 STATUS current 737 DESCRIPTION 738 "The address of the upstream neighbor (for example, RPF 739 neighbor) from which IP datagrams from these sources to 740 this multicast address are received. If the upstream 741 neighbor is unknown, then ipMcastRouteUpstreamNeighbor 742 will be 0.0.0.0 in the case of an IPv4 entry, and 743 0:0:0:0:0:0:0:0 in the case of an IPv6 entry (for example, 744 in BIDIR-PIM)." 745 ::= { ipMcastRouteEntry 8 } 747 ipMcastRouteInIfIndex OBJECT-TYPE 748 SYNTAX InterfaceIndexOrZero 749 MAX-ACCESS read-only 750 STATUS current 751 DESCRIPTION 752 "The value of ifIndex for the interface on which IP 753 datagrams sent by these sources to this multicast address 754 are received. A value of 0 indicates that datagrams are not 755 subject to an incoming interface check, but may be accepted 756 on multiple interfaces (for example, in BIDIR-PIM)." 757 ::= { ipMcastRouteEntry 9 } 759 ipMcastRouteTimeStamp OBJECT-TYPE 760 SYNTAX TimeStamp 761 MAX-ACCESS read-only 762 STATUS current 763 DESCRIPTION 764 "The value of sysUpTime at which the multicast routing 765 information represented by this entry was learned by the 766 router." 767 ::= { ipMcastRouteEntry 10 } 769 ipMcastRouteExpiryTime OBJECT-TYPE 770 SYNTAX TimeTicks 771 MAX-ACCESS read-only 772 STATUS current 773 DESCRIPTION 774 "The minimum amount of time remaining before this entry will 775 be aged out. The value 0 indicates that the entry is not 776 subject to aging. If ipMcastRouteNextHopState is pruned(1), 777 this object represents the remaining time until the prune 778 expires. If this timer expires, state reverts to 779 forwarding(2). Otherwise, this object represents the time 780 until this entry is removed from the table." 781 ::= { ipMcastRouteEntry 11 } 783 ipMcastRoutePkts OBJECT-TYPE 784 SYNTAX Counter32 785 MAX-ACCESS read-only 786 STATUS current 787 DESCRIPTION 788 "The number of packets routed using this multicast route 789 entry. 791 Discontinuities in this monotonically increasing value 792 occur at re-initialization of the management system. 793 Discontinuities can also occur as a result of routes being 794 removed and replaced, which can be detected by observing 795 the value of ipMcastRouteTimeStamp." 796 ::= { ipMcastRouteEntry 12 } 798 ipMcastRouteDifferentInIfPackets OBJECT-TYPE 799 SYNTAX Counter32 800 MAX-ACCESS read-only 801 STATUS current 802 DESCRIPTION 803 "The number of packets which this router has received from 804 these sources and addressed to this multicast group address, 805 which were dropped because they were not received on the 806 interface indicated by ipMcastRouteInIfIndex. Packets which 807 are not subject to an incoming interface check (for example, 808 using BIDIR-PIM) are not counted. 810 If this counter increases rapidly, this indicates a problem. 811 A significant quantity of multicast data is arriving at this 812 router on unexpected RPF paths (Reverse Path Forwarding 813 paths; the unicast routes to the expected origin of 814 multicast data flows), and is not being forwarded. 816 For guidance, if the rate of increase of this counter 817 exceeds 1% of the rate of increase of ipMcastRoutePkts, then 818 there are multicast routing problems that require 819 investigation. 821 Discontinuities in this monotonically increasing value 822 occur at re-initialization of the management system. 823 Discontinuities can also occur as a result of routes being 824 removed and replaced, which can be detected by observing 825 the value of ipMcastRouteTimeStamp." 826 ::= { ipMcastRouteEntry 13 } 828 ipMcastRouteOctets OBJECT-TYPE 829 SYNTAX Counter32 830 MAX-ACCESS read-only 831 STATUS current 832 DESCRIPTION 833 "The number of octets contained in IP datagrams which were 834 received from these sources and addressed to this multicast 835 group address, and which were forwarded by this router. 837 Discontinuities in this monotonically increasing value 838 occur at re-initialization of the management system. 840 Discontinuities can also occur as a result of routes being 841 removed and replaced, which can be detected by observing 842 the value of ipMcastRouteTimeStamp." 843 ::= { ipMcastRouteEntry 14 } 845 ipMcastRouteProtocol OBJECT-TYPE 846 SYNTAX IANAipMRouteProtocol 847 MAX-ACCESS read-only 848 STATUS current 849 DESCRIPTION 850 "The multicast routing protocol via which this multicast 851 forwarding entry was learned." 852 ::= { ipMcastRouteEntry 15 } 854 ipMcastRouteRtProtocol OBJECT-TYPE 855 SYNTAX IANAipRouteProtocol 856 MAX-ACCESS read-only 857 STATUS current 858 DESCRIPTION 859 "The routing mechanism via which the route used to find the 860 upstream or parent interface for this multicast forwarding 861 entry was learned. Inclusion of values for routing 862 protocols is not intended to imply that those protocols need 863 be supported." 864 ::= { ipMcastRouteEntry 16 } 866 ipMcastRouteRtAddressType OBJECT-TYPE 867 SYNTAX InetAddressType 868 MAX-ACCESS read-only 869 STATUS current 870 DESCRIPTION 871 "A value indicating the address family of the address 872 contained in ipMcastRouteRtAddress. The value MUST be the 873 same as the value of ipMcastRouteGroupType." 874 ::= { ipMcastRouteEntry 17 } 876 ipMcastRouteRtAddress OBJECT-TYPE 877 SYNTAX InetAddress 878 MAX-ACCESS read-only 879 STATUS current 880 DESCRIPTION 881 "The address portion of the route used to find the upstream 882 or parent interface for this multicast forwarding entry. 884 This address object is only significant up to 885 ipMcastRouteGroupPrefixLength bits. The remainder of the 886 address bits are zero." 887 ::= { ipMcastRouteEntry 18 } 889 ipMcastRouteRtPrefixLength OBJECT-TYPE 890 SYNTAX InetAddressPrefixLength (4..128) 891 MAX-ACCESS read-only 892 STATUS current 893 DESCRIPTION 894 "The length of the mask associated with the route used to 895 find the upstream or parent interface for this multicast 896 forwarding entry." 897 ::= { ipMcastRouteEntry 19 } 899 ipMcastRouteRtType OBJECT-TYPE 900 SYNTAX INTEGER { 901 unicast (1), -- Unicast route used in multicast RIB 902 multicast (2) -- Multicast route 903 } 904 MAX-ACCESS read-only 905 STATUS current 906 DESCRIPTION 907 "The reason the given route was placed in the (logical) 908 multicast Routing Information Base (RIB). A value of 909 unicast means that the route would normally be placed only 910 in the unicast RIB, but was placed in the multicast RIB 911 (instead or in addition) due to local configuration, such as 912 when running PIM over RIP. A value of multicast means that 913 the route was explicitly added to the multicast RIB by the 914 routing protocol, such as DVMRP or Multiprotocol BGP." 915 ::= { ipMcastRouteEntry 20 } 917 ipMcastRouteHCOctets OBJECT-TYPE 918 SYNTAX Counter64 919 MAX-ACCESS read-only 920 STATUS current 921 DESCRIPTION 922 "The number of octets contained in IP datagrams which were 923 received from these sources and addressed to this multicast 924 group address, and which were forwarded by this router. 925 This object is a 64-bit version of ipMcastRouteOctets. 927 Discontinuities in this monotonically increasing value 928 occur at re-initialization of the management system. 929 Discontinuities can also occur as a result of routes being 930 removed and replaced, which can be detected by observing 931 the value of ipMcastRouteTimeStamp." 932 ::= { ipMcastRouteEntry 21 } 934 ipMcastRouteDifferentInIfOctets OBJECT-TYPE 935 SYNTAX Counter32 936 MAX-ACCESS read-only 937 STATUS current 938 DESCRIPTION 939 "The number of octets contained in IP datagrams which this 940 router has received from these sources and addressed to this 941 multicast group address, which were dropped because they 942 were not received on the interface indicated by 943 ipMcastRouteInIfIndex. Octets in IP datagrams which are not 944 subject to an incoming interface check (for example, using 945 BIDIR-PIM) are not counted. 947 If this counter increases rapidly, this indicates a problem. 948 A significant quantity of multicast data is arriving at this 949 router on unexpected RPF paths (Reverse Path Forwarding 950 paths; the unicast routes to the expected origin of 951 multicast data flows), and is not being forwarded. 953 For guidance, if the rate of increase of this counter 954 exceeds 1% of the rate of increase of ipMcastRouteOctets, 955 then there are multicast routing problems that require 956 investigation. 958 Discontinuities in this monotonically increasing value 959 occur at re-initialization of the management system. 960 Discontinuities can also occur as a result of routes being 961 removed and replaced, which can be detected by observing 962 the value of ipMcastRouteTimeStamp." 963 ::= { ipMcastRouteEntry 22 } 965 -- 966 -- The IP Multicast Routing Next Hop Table 967 -- 969 ipMcastRouteNextHopTable OBJECT-TYPE 970 SYNTAX SEQUENCE OF IpMcastRouteNextHopEntry 971 MAX-ACCESS not-accessible 972 STATUS current 973 DESCRIPTION 974 "The (conceptual) table containing information on the 975 next-hops on outgoing interfaces for routing IP multicast 976 datagrams. Each entry is one of a list of next-hops on 977 outgoing interfaces for particular sources sending to a 978 particular multicast group address." 979 ::= { ipMcast 3 } 981 ipMcastRouteNextHopEntry OBJECT-TYPE 982 SYNTAX IpMcastRouteNextHopEntry 983 MAX-ACCESS not-accessible 984 STATUS current 985 DESCRIPTION 986 "An entry (conceptual row) in the list of next-hops on 987 outgoing interfaces to which IP multicast datagrams from 988 particular sources to an IP multicast group address are 989 routed." 990 INDEX { ipMcastRouteNextHopGroupAddressType, 991 ipMcastRouteNextHopGroup, 992 ipMcastRouteNextHopSourceAddressType, 993 ipMcastRouteNextHopSource, 994 ipMcastRouteNextHopSourcePrefixLength, 995 ipMcastRouteNextHopIfIndex, 996 ipMcastRouteNextHopAddressType, 997 ipMcastRouteNextHopAddress } 998 ::= { ipMcastRouteNextHopTable 1 } 1000 IpMcastRouteNextHopEntry ::= SEQUENCE { 1001 ipMcastRouteNextHopGroupAddressType InetAddressType, 1002 ipMcastRouteNextHopGroup InetAddress, 1003 ipMcastRouteNextHopSourceAddressType InetAddressType, 1004 ipMcastRouteNextHopSource InetAddress, 1005 ipMcastRouteNextHopSourcePrefixLength InetAddressPrefixLength, 1006 ipMcastRouteNextHopIfIndex InterfaceIndex, 1007 ipMcastRouteNextHopAddressType InetAddressType, 1008 ipMcastRouteNextHopAddress InetAddress, 1009 ipMcastRouteNextHopState INTEGER, 1010 ipMcastRouteNextHopTimeStamp TimeStamp, 1011 ipMcastRouteNextHopExpiryTime TimeTicks, 1012 ipMcastRouteNextHopClosestMemberHops Unsigned32, 1013 ipMcastRouteNextHopProtocol IANAipMRouteProtocol, 1014 ipMcastRouteNextHopPkts Counter32, 1015 ipMcastRouteNextHopOctets Counter32 1016 } 1018 ipMcastRouteNextHopGroupAddressType OBJECT-TYPE 1019 SYNTAX InetAddressType 1020 MAX-ACCESS not-accessible 1021 STATUS current 1022 DESCRIPTION 1023 "A value indicating the address family of the address 1024 contained in ipMcastRouteNextHopGroup. Legal values 1025 correspond to the subset of address families for which 1026 multicast forwarding is supported." 1027 ::= { ipMcastRouteNextHopEntry 1 } 1029 ipMcastRouteNextHopGroup OBJECT-TYPE 1030 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1031 MAX-ACCESS not-accessible 1032 STATUS current 1033 DESCRIPTION 1034 "The IP multicast group for which this entry specifies a 1035 next-hop on an outgoing interface." 1036 ::= { ipMcastRouteNextHopEntry 2 } 1038 ipMcastRouteNextHopSourceAddressType OBJECT-TYPE 1039 SYNTAX InetAddressType 1040 MAX-ACCESS not-accessible 1041 STATUS current 1042 DESCRIPTION 1043 "A value indicating the address family of the address 1044 contained in ipMcastRouteNextHopSource. The value MUST be 1045 the same as the value of ipMcastRouteNextHopGroupType." 1046 ::= { ipMcastRouteNextHopEntry 3 } 1048 ipMcastRouteNextHopSource OBJECT-TYPE 1049 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1050 MAX-ACCESS not-accessible 1051 STATUS current 1052 DESCRIPTION 1053 "The network address which when combined with the 1054 corresponding value of the mask specified in 1055 ipMcastRouteNextHopSourcePrefixLength identifies the sources 1056 for which this entry specifies a next-hop on an outgoing 1057 interface. 1059 This address object is only significant up to 1060 ipMcastRouteNextHopSourcePrefixLength bits. The remainder 1061 of the address bits are zero. This is especially important 1062 for this index field, which is part of the index of this 1063 entry. Any non-zero bits would signify an entirely 1064 different entry." 1065 ::= { ipMcastRouteNextHopEntry 4 } 1067 ipMcastRouteNextHopSourcePrefixLength OBJECT-TYPE 1068 SYNTAX InetAddressPrefixLength (4..128) 1069 MAX-ACCESS not-accessible 1070 STATUS current 1071 DESCRIPTION 1072 "The length in bits of the mask which when combined with the 1073 corresponding value specified in ipMcastRouteNextHopSource 1074 identifies the sources for which this entry specifies a 1075 next-hop on an outgoing interface." 1076 ::= { ipMcastRouteNextHopEntry 5 } 1078 ipMcastRouteNextHopIfIndex OBJECT-TYPE 1079 SYNTAX InterfaceIndex 1080 MAX-ACCESS not-accessible 1081 STATUS current 1082 DESCRIPTION 1083 "The ifIndex value of the interface for the outgoing 1084 interface for this next-hop." 1085 ::= { ipMcastRouteNextHopEntry 6 } 1087 ipMcastRouteNextHopAddressType OBJECT-TYPE 1088 SYNTAX InetAddressType 1089 MAX-ACCESS not-accessible 1090 STATUS current 1091 DESCRIPTION 1092 "A value indicating the address family of the address 1093 contained in ipMcastRouteNextHopAddress. The value MUST be 1094 the same as the value of ipMcastRouteNextHopGroupType." 1095 ::= { ipMcastRouteNextHopEntry 7 } 1097 ipMcastRouteNextHopAddress OBJECT-TYPE 1098 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1099 MAX-ACCESS not-accessible 1100 STATUS current 1101 DESCRIPTION 1102 "The address of the next-hop specific to this entry. For 1103 most interfaces, this is identical to 1104 ipMcastRouteNextHopGroup. NBMA interfaces, however, may 1105 have multiple next-hop addresses out a single outgoing 1106 interface." 1107 ::= { ipMcastRouteNextHopEntry 8 } 1109 ipMcastRouteNextHopState OBJECT-TYPE 1110 SYNTAX INTEGER { pruned(1), forwarding(2) } 1111 MAX-ACCESS read-only 1112 STATUS current 1113 DESCRIPTION 1114 "An indication of whether the outgoing interface and next- 1115 hop represented by this entry is currently being used to 1116 forward IP datagrams. The value 'forwarding' indicates it 1117 is currently being used; the value 'pruned' indicates it is 1118 not." 1119 ::= { ipMcastRouteNextHopEntry 9 } 1121 ipMcastRouteNextHopTimeStamp OBJECT-TYPE 1122 SYNTAX TimeStamp 1123 MAX-ACCESS read-only 1124 STATUS current 1125 DESCRIPTION 1126 "The value of sysUpTime at which the multicast routing 1127 information represented by this entry was learned by the 1128 router." 1130 ::= { ipMcastRouteNextHopEntry 10 } 1132 ipMcastRouteNextHopExpiryTime OBJECT-TYPE 1133 SYNTAX TimeTicks 1134 MAX-ACCESS read-only 1135 STATUS current 1136 DESCRIPTION 1137 "The minimum amount of time remaining before this entry will 1138 be aged out. If ipMcastRouteNextHopState is pruned(1), the 1139 remaining time until the prune expires and the state reverts 1140 to forwarding(2). Otherwise, the remaining time until this 1141 entry is removed from the table. The time remaining may be 1142 copied from ipMcastRouteExpiryTime if the protocol in use 1143 for this entry does not specify next-hop timers. The value 1144 0 indicates that the entry is not subject to aging." 1145 ::= { ipMcastRouteNextHopEntry 11 } 1147 ipMcastRouteNextHopClosestMemberHops OBJECT-TYPE 1148 SYNTAX Unsigned32 (0..2147483647) 1149 MAX-ACCESS read-only 1150 STATUS current 1151 DESCRIPTION 1152 "The minimum number of hops between this router and any 1153 member of this IP multicast group reached via this next-hop 1154 on this outgoing interface. Any IP multicast datagrams for 1155 the group which have a TTL (IPv4) or Hop Count (IPv6) less 1156 than this number of hops will not be forwarded to this 1157 next-hop. 1159 This is an optimization applied by multicast routing 1160 protocols that explicitly track hop counts to downstream 1161 listeners. Multicast protocols that are not aware of hop 1162 counts to downstream listeners set this object to zero." 1163 ::= { ipMcastRouteNextHopEntry 12 } 1165 ipMcastRouteNextHopProtocol OBJECT-TYPE 1166 SYNTAX IANAipMRouteProtocol 1167 MAX-ACCESS read-only 1168 STATUS current 1169 DESCRIPTION 1170 "The routing mechanism via which this next-hop was learned." 1171 ::= { ipMcastRouteNextHopEntry 13 } 1173 ipMcastRouteNextHopPkts OBJECT-TYPE 1174 SYNTAX Counter32 1175 MAX-ACCESS read-only 1176 STATUS current 1177 DESCRIPTION 1178 "The number of packets which have been forwarded using this 1179 route. 1181 Discontinuities in this monotonically increasing value 1182 occur at re-initialization of the management system. 1183 Discontinuities can also occur as a result of routes being 1184 removed and replaced, which can be detected by observing 1185 the value of ipMcastRouteNextHopTimeStamp." 1186 ::= { ipMcastRouteNextHopEntry 14 } 1188 ipMcastRouteNextHopOctets OBJECT-TYPE 1189 SYNTAX Counter32 1190 MAX-ACCESS read-only 1191 STATUS current 1192 DESCRIPTION 1193 "The number of octets of multicast packets that have been 1194 forwarded using this route. 1196 Discontinuities in this monotonically increasing value 1197 occur at re-initialization of the management system. 1198 Discontinuities can also occur as a result of routes being 1199 removed and replaced, which can be detected by observing 1200 the value of ipMcastRouteNextHopTimeStamp." 1201 ::= { ipMcastRouteNextHopEntry 15 } 1203 -- 1204 -- The IP Multicast Scope Boundary Table 1205 -- 1207 ipMcastBoundaryTable OBJECT-TYPE 1208 SYNTAX SEQUENCE OF IpMcastBoundaryEntry 1209 MAX-ACCESS not-accessible 1210 STATUS current 1211 DESCRIPTION 1212 "The (conceptual) table listing the system's scoped 1213 multicast address boundaries." 1214 ::= { ipMcast 5 } 1216 ipMcastBoundaryEntry OBJECT-TYPE 1217 SYNTAX IpMcastBoundaryEntry 1218 MAX-ACCESS not-accessible 1219 STATUS current 1220 DESCRIPTION 1221 "An entry (conceptual row) in the ipMcastBoundaryTable 1222 representing a scoped boundary." 1223 INDEX { ipMcastBoundaryIfIndex, 1224 ipMcastBoundaryAddressType, 1225 ipMcastBoundaryAddress, 1226 ipMcastBoundaryAddressPrefixLength } 1227 ::= { ipMcastBoundaryTable 1 } 1229 IpMcastBoundaryEntry ::= SEQUENCE { 1230 ipMcastBoundaryIfIndex InterfaceIndex, 1231 ipMcastBoundaryAddressType InetAddressType, 1232 ipMcastBoundaryAddress InetAddress, 1233 ipMcastBoundaryAddressPrefixLength InetAddressPrefixLength, 1234 ipMcastBoundaryStatus RowStatus, 1235 ipMcastBoundaryStorageType StorageType 1236 } 1238 ipMcastBoundaryIfIndex OBJECT-TYPE 1239 SYNTAX InterfaceIndex 1240 MAX-ACCESS not-accessible 1241 STATUS current 1242 DESCRIPTION 1243 "The IfIndex value for the interface to which this boundary 1244 applies. Packets with a destination address in the 1245 associated address/mask range will not be forwarded out this 1246 interface." 1247 ::= { ipMcastBoundaryEntry 1 } 1249 ipMcastBoundaryAddressType OBJECT-TYPE 1250 SYNTAX InetAddressType 1251 MAX-ACCESS not-accessible 1252 STATUS current 1253 DESCRIPTION 1254 "A value indicating the address family of the address 1255 contained in ipMcastBoundaryAddress. Legal values 1256 correspond to the subset of address families for which 1257 multicast forwarding is supported." 1258 ::= { ipMcastBoundaryEntry 2 } 1260 ipMcastBoundaryAddress OBJECT-TYPE 1261 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1262 MAX-ACCESS not-accessible 1263 STATUS current 1264 DESCRIPTION 1265 "The group address which when combined with the 1266 corresponding value of ipMcastBoundaryAddressPrefixLength 1267 identifies the group range for which the scoped boundary 1268 exists. Scoped IPv4 addresses must come from the range 1269 239.x.x.x. Scoped IPv6 addresses must come from range 1270 ff.nn.nn.nn.nn.nn.nn.nn, where nn encodes the scope type and 1271 group identifier. 1273 This address object is only significant up to 1274 ipMcastBoundaryAddressPrefixLength bits. The remainder of 1275 the address bits are zero. This is especially important for 1276 this index field, which is part of the index of this entry. 1277 Any non-zero bits would signify an entirely different 1278 entry." 1279 REFERENCE "RFC 2365, RFC 2373" 1280 ::= { ipMcastBoundaryEntry 3 } 1282 ipMcastBoundaryAddressPrefixLength OBJECT-TYPE 1283 SYNTAX InetAddressPrefixLength (4..128) 1284 MAX-ACCESS not-accessible 1285 STATUS current 1286 DESCRIPTION 1287 "The length in bits of the mask which when combined with the 1288 corresponding value of ipMcastBoundaryAddress identifies the 1289 group range for which the scoped boundary exists." 1290 ::= { ipMcastBoundaryEntry 4 } 1292 ipMcastBoundaryStatus OBJECT-TYPE 1293 SYNTAX RowStatus 1294 MAX-ACCESS read-create 1295 STATUS current 1296 DESCRIPTION 1297 "The status of this row, by which rows in this table can 1298 be created and destroyed. 1300 This status object can be set to active(1) without setting 1301 any other columnar objects in this entry. 1303 All writeable objects in this entry can be modified when the 1304 status of this entry is active(1)." 1305 ::= { ipMcastBoundaryEntry 5 } 1307 ipMcastBoundaryStorageType OBJECT-TYPE 1308 SYNTAX StorageType 1309 MAX-ACCESS read-create 1310 STATUS current 1311 DESCRIPTION 1312 "The storage type for this row. Rows having the value 1313 'permanent' need not allow write-access to any columnar 1314 objects in the row." 1315 DEFVAL { nonVolatile } 1316 ::= { ipMcastBoundaryEntry 6 } 1318 -- 1319 -- The IP Multicast Scope Name Table 1320 -- 1321 ipMcastScopeNameTable OBJECT-TYPE 1322 SYNTAX SEQUENCE OF IpMcastScopeNameEntry 1323 MAX-ACCESS not-accessible 1324 STATUS current 1325 DESCRIPTION 1326 "The (conceptual) table listing multicast scope names." 1327 ::= { ipMcast 6 } 1329 ipMcastScopeNameEntry OBJECT-TYPE 1330 SYNTAX IpMcastScopeNameEntry 1331 MAX-ACCESS not-accessible 1332 STATUS current 1333 DESCRIPTION 1334 "An entry (conceptual row) in the ipMcastScopeNameTable 1335 representing a multicast scope name." 1336 INDEX { ipMcastScopeNameAddressType, 1337 ipMcastScopeNameAddress, 1338 ipMcastScopeNameAddressPrefixLength, 1339 IMPLIED ipMcastScopeNameLanguage } 1340 ::= { ipMcastScopeNameTable 1 } 1342 IpMcastScopeNameEntry ::= SEQUENCE { 1343 ipMcastScopeNameAddressType InetAddressType, 1344 ipMcastScopeNameAddress InetAddress, 1345 ipMcastScopeNameAddressPrefixLength InetAddressPrefixLength, 1346 ipMcastScopeNameLanguage LanguageTag, 1347 ipMcastScopeNameString SnmpAdminString, 1348 ipMcastScopeNameDefault TruthValue, 1349 ipMcastScopeNameStatus RowStatus, 1350 ipMcastScopeNameStorageType StorageType 1351 } 1353 ipMcastScopeNameAddressType OBJECT-TYPE 1354 SYNTAX InetAddressType 1355 MAX-ACCESS not-accessible 1356 STATUS current 1357 DESCRIPTION 1358 "A value indicating the address family of the address 1359 contained in ipMcastScopeNameAddress. Legal values 1360 correspond to the subset of address families for which 1361 multicast forwarding is supported." 1362 ::= { ipMcastScopeNameEntry 1 } 1364 ipMcastScopeNameAddress OBJECT-TYPE 1365 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1366 MAX-ACCESS not-accessible 1367 STATUS current 1368 DESCRIPTION 1369 "The group address which when combined with the 1370 corresponding value of ipMcastScopeNameAddressPrefixLength 1371 identifies the group range associated with the multicast 1372 scope. Scoped IPv4 addresses must come from the range 1373 239.x.x.x. Scoped IPv6 addresses must come from the range 1374 ff.nn.nn.nn.nn.nn.nn.nn, where nn encodes the scope type and 1375 group identifier. 1377 This address object is only significant up to 1378 ipMcastScopeNameAddressPrefixLength bits. The remainder of 1379 the address bits are zero. This is especially important for 1380 this index field, which is part of the index of this entry. 1381 Any non-zero bits would signify an entirely different 1382 entry." 1383 REFERENCE "RFC 2365, RFC 2373" 1384 ::= { ipMcastScopeNameEntry 2 } 1386 ipMcastScopeNameAddressPrefixLength OBJECT-TYPE 1387 SYNTAX InetAddressPrefixLength (4..128) 1388 MAX-ACCESS not-accessible 1389 STATUS current 1390 DESCRIPTION 1391 "The length in bits of the mask which when combined with the 1392 corresponding value of ipMcastScopeNameAddress identifies 1393 the group range associated with the multicast scope." 1394 ::= { ipMcastScopeNameEntry 3 } 1396 ipMcastScopeNameLanguage OBJECT-TYPE 1397 SYNTAX LanguageTag 1398 MAX-ACCESS not-accessible 1399 STATUS current 1400 DESCRIPTION 1401 "Language tag associated with the scope name." 1402 REFERENCE "RFC 1766" 1403 ::= { ipMcastScopeNameEntry 4 } 1405 ipMcastScopeNameString OBJECT-TYPE 1406 SYNTAX SnmpAdminString 1407 MAX-ACCESS read-create 1408 STATUS current 1409 DESCRIPTION 1410 "The textual name associated with the multicast scope. The 1411 value of this object should be suitable for displaying to 1412 end-users, such as when allocating a multicast address in 1413 this scope. When no name is specified, the default value of 1414 this object for IPv4 should be the string 239.x.x.x/y with x 1415 and y replaced appropriately to describe the address and 1416 mask length associated with the scope. Scoped IPv6 1417 addresses must come from range ff.nn.nn.nn.nn.nn.nn.nn, 1418 where nn encodes the scope type and group identifier." 1419 ::= { ipMcastScopeNameEntry 5 } 1421 ipMcastScopeNameDefault OBJECT-TYPE 1422 SYNTAX TruthValue 1423 MAX-ACCESS read-create 1424 STATUS current 1425 DESCRIPTION 1426 "If true, indicates a preference that the name in the 1427 following language should be used by applications if no name 1428 is available in a desired language." 1429 DEFVAL { false } 1430 ::= { ipMcastScopeNameEntry 6 } 1432 ipMcastScopeNameStatus OBJECT-TYPE 1433 SYNTAX RowStatus 1434 MAX-ACCESS read-create 1435 STATUS current 1436 DESCRIPTION 1437 "The status of this row, by which rows in this table can 1438 be created and destroyed. Before the row can be activated, 1439 the object ipMcastScopeNameString must be set to a valid 1440 value. All writeable objects in this entry can be modified 1441 when the status is active(1)." 1442 ::= { ipMcastScopeNameEntry 7 } 1444 ipMcastScopeNameStorageType OBJECT-TYPE 1445 SYNTAX StorageType 1446 MAX-ACCESS read-create 1447 STATUS current 1448 DESCRIPTION 1449 "The storage type for this row. Rows having the value 1450 'permanent' need not allow write-access to any columnar 1451 objects in the row." 1452 DEFVAL { nonVolatile } 1453 ::= { ipMcastScopeNameEntry 8 } 1455 -- 1456 -- The Multicast Listeners Table 1457 -- 1459 ipMcastLocalListenerTable OBJECT-TYPE 1460 SYNTAX SEQUENCE OF IpMcastLocalListenerEntry 1461 MAX-ACCESS not-accessible 1462 STATUS current 1463 DESCRIPTION 1464 "The (conceptual) table listing local applications or 1465 services that have joined multicast groups as listeners. 1467 Entries exist for all addresses in the multicast range for 1468 all applications and services as they are classified on this 1469 device." 1470 ::= { ipMcast 9 } 1472 ipMcastLocalListenerEntry OBJECT-TYPE 1473 SYNTAX IpMcastLocalListenerEntry 1474 MAX-ACCESS not-accessible 1475 STATUS current 1476 DESCRIPTION 1477 "An entry (conceptual row) in the LocalListenerTable." 1478 INDEX { ipMcastLocalListenerGroupAddressType, 1479 ipMcastLocalListenerGroupAddress, 1480 ipMcastLocalListenerSourceAddressType, 1481 ipMcastLocalListenerSourceAddress, 1482 ipMcastLocalListenerSourcePrefixLength, 1483 ipMcastLocalListenerRunIndex } 1484 ::= { ipMcastLocalListenerTable 1 } 1486 IpMcastLocalListenerEntry ::= SEQUENCE { 1487 ipMcastLocalListenerGroupAddressType InetAddressType, 1488 ipMcastLocalListenerGroupAddress InetAddress, 1489 ipMcastLocalListenerSourceAddressType InetAddressType, 1490 ipMcastLocalListenerSourceAddress InetAddress, 1491 ipMcastLocalListenerSourcePrefixLength InetAddressPrefixLength, 1492 ipMcastLocalListenerRunIndex Unsigned32 1493 } 1495 ipMcastLocalListenerGroupAddressType OBJECT-TYPE 1496 SYNTAX InetAddressType 1497 MAX-ACCESS not-accessible 1498 STATUS current 1499 DESCRIPTION 1500 "A value indicating the address family of the address 1501 contained in ipMcastLocalListenerGroupAddress. Legal values 1502 correspond to the subset of address families for which 1503 multicast is supported." 1504 ::= { ipMcastLocalListenerEntry 1 } 1506 ipMcastLocalListenerGroupAddress OBJECT-TYPE 1507 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1508 MAX-ACCESS not-accessible 1509 STATUS current 1510 DESCRIPTION 1511 "The IP multicast group for which this entry specifies 1512 locally joined applications or services." 1514 ::= { ipMcastLocalListenerEntry 2 } 1516 ipMcastLocalListenerSourceAddressType OBJECT-TYPE 1517 SYNTAX InetAddressType 1518 MAX-ACCESS not-accessible 1519 STATUS current 1520 DESCRIPTION 1521 "A value indicating the address family of the address 1522 contained in ipMcastLocalListenerSource. The value MUST be 1523 the same as the value of ipMcastLocalListenerAddressType." 1524 ::= { ipMcastLocalListenerEntry 3 } 1526 ipMcastLocalListenerSourceAddress OBJECT-TYPE 1527 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1528 MAX-ACCESS not-accessible 1529 STATUS current 1530 DESCRIPTION 1531 "The network address which when combined with the 1532 corresponding value of the mask specified in 1533 ipMcastLocalListenerSourcePrefixLength identifies the 1534 sources for which this entry specifies a local listener. 1536 This address object is only significant up to 1537 ipMcastLocalListenerSourcePrefixLength bits. The remainder 1538 of the address bits are zero. This is especially important 1539 for this index field, which is part of the index of this 1540 entry. Any non-zero bits would signify an entirely 1541 different entry." 1542 ::= { ipMcastLocalListenerEntry 4 } 1544 ipMcastLocalListenerSourcePrefixLength OBJECT-TYPE 1545 SYNTAX InetAddressPrefixLength (4..128) 1546 MAX-ACCESS not-accessible 1547 STATUS current 1548 DESCRIPTION 1549 "The length in bits of the mask which when combined with the 1550 corresponding value specified in ipMcastLocalListenerSource 1551 identifies the sources for which this entry specifies a 1552 locally listener. A mask length of zero corresponds to all 1553 sources within the group." 1554 ::= { ipMcastLocalListenerEntry 5 } 1556 ipMcastLocalListenerRunIndex OBJECT-TYPE 1557 SYNTAX Unsigned32 (0..2147483647) 1558 MAX-ACCESS read-only 1559 STATUS current 1560 DESCRIPTION 1561 "A unique value corresponding to a piece of software running 1562 on this router or host system. Where possible, this should 1563 be the system's native, unique identification number. 1565 This identifier is platform-specific. It may correspond to 1566 a process ID or application instance number. 1568 A value of zero indicates that the application instance(s) 1569 cannot be identified. A value of zero indicates that one or 1570 more unidentified applications have joined the specified 1571 multicast groups (for the specified sources) as listeners." 1572 REFERENCE "RFC 2287 sysApplRunIndex" 1573 ::= { ipMcastLocalListenerEntry 6 } 1575 -- 1576 -- Conformance information 1577 -- 1579 ipMcastMIBConformance 1580 OBJECT IDENTIFIER ::= { ipMcastMIB 2 } 1581 ipMcastMIBCompliances 1582 OBJECT IDENTIFIER ::= { ipMcastMIBConformance 1 } 1583 ipMcastMIBGroups OBJECT IDENTIFIER ::= { ipMcastMIBConformance 2 } 1585 -- 1586 -- Compliance statements 1587 -- 1589 ipMcastMIBCompliance MODULE-COMPLIANCE 1590 STATUS current 1591 DESCRIPTION 1592 "Implementations of all the mandatory MIB groups listed 1593 below can claim full compliance. 1595 This MIB contains several InetAddressType and InetAddress 1596 objects, but not all IP address types are supported by all 1597 protocol implementations. 1599 A MIB implementation can claim full compliance if all IP 1600 address types supported by the protocol implementation are 1601 supported by the MIB implementation." 1603 MODULE -- this module 1604 MANDATORY-GROUPS { ipMcastMIBBasicGroup} 1606 OBJECT ipMcastEnable 1607 MIN-ACCESS read-only 1608 DESCRIPTION 1609 "Write access is not required." 1611 GROUP ipMcastMIBRouteGroup 1612 DESCRIPTION 1613 "This group is mandatory if the system is a router." 1615 OBJECT ipMcastInterfaceTtl 1616 MIN-ACCESS read-only 1617 DESCRIPTION 1618 "Write access is not required." 1620 OBJECT ipMcastInterfaceRateLimit 1621 MIN-ACCESS read-only 1622 DESCRIPTION 1623 "Write access is not required." 1625 GROUP ipMcastMIBHopCountGroup 1626 DESCRIPTION 1627 "This group is optional." 1629 GROUP ipMcastMIBPktsOutGroup 1630 DESCRIPTION 1631 "This group is optional." 1633 GROUP ipMcastMIBHCInterfaceGroup 1634 DESCRIPTION 1635 "This group is mandatory only for those network interfaces 1636 for which the value of the corresponding instance of ifSpeed 1637 is greater than 20,000,000 bits/second." 1639 GROUP ipMcastMIBRouteProtoGroup 1640 DESCRIPTION 1641 "This group is mandatory if the system is a router." 1643 GROUP ipMcastMIBPktsGroup 1644 DESCRIPTION 1645 "This group is optional." 1647 GROUP ipMcastMIBSsmGroup 1648 DESCRIPTION 1649 "This group is optional." 1651 GROUP ipMcastMIBLocalListenerGroup 1652 DESCRIPTION 1653 "This group is optional." 1655 GROUP ipMcastMIBBoundaryIfGroup 1656 DESCRIPTION 1657 "This group is mandatory if the system is a router that 1658 supports administratively-scoped multicast address 1659 boundaries." 1661 OBJECT ipMcastBoundaryStatus 1662 MIN-ACCESS read-only 1663 DESCRIPTION 1664 "Write access is not required." 1666 GROUP ipMcastMIBScopeNameGroup 1667 DESCRIPTION 1668 "This group is mandatory if the system is a router that 1669 supports multicast scope names." 1671 OBJECT ipMcastScopeNameString 1672 MIN-ACCESS read-only 1673 DESCRIPTION 1674 "Write access is not required." 1676 OBJECT ipMcastScopeNameDefault 1677 MIN-ACCESS read-only 1678 DESCRIPTION 1679 "Write access is not required." 1681 OBJECT ipMcastScopeNameStatus 1682 MIN-ACCESS read-only 1683 DESCRIPTION 1684 "Write access is not required." 1686 GROUP ipMcastMIBIfPktsGroup 1687 DESCRIPTION 1688 "This group is optional." 1690 GROUP ipMcastMIBRouteOctetsGroup 1691 DESCRIPTION 1692 "This group is optional." 1694 ::= { ipMcastMIBCompliances 1 } 1696 ipMcastMIBMRouteCompliance MODULE-COMPLIANCE 1697 STATUS deprecated 1698 DESCRIPTION 1699 "Implementations of this compliance statement are equivalent 1700 to compliance with the deprecated IPMROUTE-MIB module." 1702 MODULE -- this module 1703 MANDATORY-GROUPS { ipMcastMIBMRouteBasicGroup } 1705 ::= { ipMcastMIBCompliances 2 } 1706 -- 1707 -- Units of conformance 1708 -- 1709 ipMcastMIBMRouteBasicGroup OBJECT-GROUP 1710 OBJECTS { ipMcastEnable, ipMcastRouteEntryCount, 1711 ipMcastRouteUpstreamNeighborType, 1712 ipMcastRouteUpstreamNeighbor, ipMcastRouteInIfIndex, 1713 ipMcastRouteTimeStamp, ipMcastRouteExpiryTime, 1714 ipMcastRouteNextHopState, 1715 ipMcastRouteNextHopTimeStamp, 1716 ipMcastRouteNextHopExpiryTime, 1717 ipMcastRouteNextHopProtocol, 1718 ipMcastRouteNextHopPkts, 1719 ipMcastInterfaceTtl, 1720 ipMcastInterfaceProtocol, 1721 ipMcastInterfaceRateLimit, 1722 ipMcastInterfaceInMcastOctets, 1723 ipMcastInterfaceOutMcastOctets 1724 } 1725 STATUS deprecated 1726 DESCRIPTION 1727 "A collection of objects to support basic management of IP 1728 Multicast routing. 1730 This conformance group is deprecated. It is replaced by 1731 ipMcastMIBBasicGroup and ipMcastMIBRouteGroup" 1732 ::= { ipMcastMIBGroups 1 } 1734 ipMcastMIBHopCountGroup OBJECT-GROUP 1735 OBJECTS { ipMcastRouteNextHopClosestMemberHops } 1736 STATUS current 1737 DESCRIPTION 1738 "A collection of objects to support management of the use of 1739 hop counts in IP Multicast routing." 1740 ::= { ipMcastMIBGroups 2 } 1742 ipMcastMIBPktsOutGroup OBJECT-GROUP 1743 OBJECTS { ipMcastRouteNextHopPkts } 1744 STATUS current 1745 DESCRIPTION 1746 "A collection of objects to support management of packet 1747 counters for each outgoing interface entry of a route." 1748 ::= { ipMcastMIBGroups 3 } 1750 ipMcastMIBHCInterfaceGroup OBJECT-GROUP 1751 OBJECTS { ipMcastInterfaceHCInMcastOctets, 1752 ipMcastInterfaceHCOutMcastOctets, 1753 ipMcastInterfaceHCInMcastPkts, 1754 ipMcastInterfaceHCOutMcastPkts, 1755 ipMcastRouteHCOctets } 1756 STATUS current 1757 DESCRIPTION 1758 "A collection of objects providing information specific to 1759 high speed (greater than 20,000,000 bits/second) network 1760 interfaces." 1761 ::= { ipMcastMIBGroups 4 } 1763 ipMcastMIBRouteProtoGroup OBJECT-GROUP 1764 OBJECTS { ipMcastRouteProtocol, ipMcastRouteRtProtocol, 1765 ipMcastRouteRtAddressType, ipMcastRouteRtAddress, 1766 ipMcastRouteRtPrefixLength, ipMcastRouteRtType } 1767 STATUS current 1768 DESCRIPTION 1769 "A collection of objects providing information on the 1770 relationship between multicast routing information and the 1771 IP Forwarding Table." 1772 ::= { ipMcastMIBGroups 5 } 1774 ipMcastMIBPktsGroup OBJECT-GROUP 1775 OBJECTS { ipMcastRoutePkts, ipMcastRouteDifferentInIfPackets, 1776 ipMcastRouteOctets } 1777 STATUS current 1778 DESCRIPTION 1779 "A collection of objects to support management of packet 1780 counters for each forwarding entry." 1781 ::= { ipMcastMIBGroups 6 } 1783 ipMcastMIBBasicGroup OBJECT-GROUP 1784 OBJECTS { ipMcastEnable, ipMcastRouteEntryCount 1785 } 1786 STATUS current 1787 DESCRIPTION 1788 "A collection of objects to support basic management of IP 1789 Multicast protocols." 1790 ::= { ipMcastMIBGroups 7 } 1792 ipMcastMIBRouteGroup OBJECT-GROUP 1793 OBJECTS { ipMcastRouteUpstreamNeighborType, 1794 ipMcastRouteUpstreamNeighbor, ipMcastRouteInIfIndex, 1795 ipMcastRouteTimeStamp, ipMcastRouteExpiryTime, 1796 ipMcastRouteNextHopState, ipMcastRouteNextHopTimeStamp, 1797 ipMcastRouteNextHopExpiryTime, 1798 ipMcastRouteNextHopProtocol, 1799 ipMcastRouteNextHopPkts, 1800 ipMcastInterfaceTtl, 1801 ipMcastInterfaceRateLimit, 1802 ipMcastInterfaceInMcastOctets, 1803 ipMcastInterfaceOutMcastOctets 1804 } 1805 STATUS current 1806 DESCRIPTION 1807 "A collection of objects to support basic management of IP 1808 Multicast routing." 1809 ::= { ipMcastMIBGroups 8 } 1811 ipMcastMIBSsmGroup OBJECT-GROUP 1812 OBJECTS { ipMcastSsmRangeRowStatus, ipMcastSsmRangeStorageType } 1813 STATUS current 1814 DESCRIPTION 1815 "A collection of objects to support management of the use of 1816 Source-Specific Multicast routing." 1817 ::= { ipMcastMIBGroups 9 } 1819 ipMcastMIBLocalListenerGroup OBJECT-GROUP 1820 OBJECTS { ipMcastLocalListenerRunIndex } 1821 STATUS current 1822 DESCRIPTION 1823 "A collection of objects to support management of local 1824 listeners on hosts or routers." 1825 ::= { ipMcastMIBGroups 10 } 1827 ipMcastMIBBoundaryIfGroup OBJECT-GROUP 1828 OBJECTS { ipMcastBoundaryStatus, ipMcastBoundaryStorageType } 1829 STATUS current 1830 DESCRIPTION 1831 "A collection of objects to support management of scoped 1832 multicast address boundaries." 1833 ::= { ipMcastMIBGroups 11 } 1835 ipMcastMIBScopeNameGroup OBJECT-GROUP 1836 OBJECTS { ipMcastScopeNameString, ipMcastScopeNameDefault, 1837 ipMcastScopeNameStatus, ipMcastScopeNameStorageType } 1838 STATUS current 1839 DESCRIPTION 1840 "A collection of objects to support management of multicast 1841 address scope names." 1842 ::= { ipMcastMIBGroups 12 } 1844 ipMcastMIBIfPktsGroup OBJECT-GROUP 1845 OBJECTS { ipMcastInterfaceInMcastPkts, 1846 ipMcastInterfaceOutMcastPkts } 1847 STATUS current 1848 DESCRIPTION 1849 "A collection of objects to support management of packet 1850 counters for each interface entry." 1852 ::= { ipMcastMIBGroups 13 } 1854 ipMcastMIBRouteOctetsGroup OBJECT-GROUP 1855 OBJECTS { ipMcastRouteOctets, ipMcastRouteNextHopOctets, 1856 ipMcastRouteDifferentInIfOctets } 1857 STATUS current 1858 DESCRIPTION 1859 "A collection of objects to support management of octet 1860 counters for each forwarding entry." 1861 ::= { ipMcastMIBGroups 14 } 1863 END 1865 6. Security Considerations 1867 There are a number of management objects defined in this MIB module 1868 with a MAX-ACCESS clause of read-write and/or read-create. Such 1869 objects may be considered sensitive or vulnerable in some network 1870 environments. The support for SET operations in a non-secure 1871 environment without proper protection can have a negative effect on 1872 network operations. These are the tables and objects and their 1873 sensitivity/vulnerability: 1875 The following tables and objects could be employed to modify 1876 multicast routing behavior in a way that prevents or disrupts 1877 services provided by the network, including (but not limited to) 1878 multicast data traffic delivery. 1880 The following tables and objects may also be used to modify multicast 1881 routing behavior in order to intercept or subvert any information 1882 that is carried by the network. For example, attacks can be 1883 envisaged that would pass nominated multicast data streams through a 1884 nominated location, without the sources or listeners becoming aware 1885 of this subversion. 1887 ipMcastEnable 1888 ipMcastInterfaceTable 1889 ipMcastInterfaceEntry 1890 ipMcastInterfaceIfIndex 1891 ipMcastInterfaceTtl 1892 ipMcastInterfaceProtocol 1893 ipMcastInterfaceRateLimit 1894 ipMcastSsmRangeTable 1895 ipMcastSsmRangeEntry 1896 ipMcastSsmRangeAddressType 1897 ipMcastSsmRangeAddress 1898 ipMcastSsmRangePrefixLength 1899 ipMcastSsmRangeRowStatus 1900 ipMcastSsmRangeStorageType 1901 ipMcastBoundaryTable 1902 ipMcastBoundaryEntry 1903 ipMcastBoundaryIfIndex 1904 ipMcastBoundaryAddressType 1905 ipMcastBoundaryAddress 1906 ipMcastBoundaryAddressPrefixLength 1907 ipMcastBoundaryStatus 1908 ipMcastBoundaryStorageType 1909 ipMcastScopeNameTable 1910 ipMcastScopeNameEntry 1911 ipMcastScopeNameAddressType 1912 ipMcastScopeNameAddress 1913 ipMcastScopeNameAddressPrefixLength 1914 ipMcastScopeNameLanguage 1915 ipMcastScopeNameString 1916 ipMcastScopeNameDefault 1917 ipMcastScopeNameStatus 1918 ipMcastScopeNameStorageType 1920 Some of the readable objects in this MIB module (i.e., objects with a 1921 MAX-ACCESS other than not-accessible) may be considered sensitive or 1922 vulnerable in some network environments. It is thus important to 1923 control even GET and/or NOTIFY access to these objects and possibly 1924 to even encrypt the values of these objects when sending them over 1925 the network via SNMP. These are the tables and objects and their 1926 sensitivity/vulnerability: 1928 The following tables and objects could be employed to determine the 1929 topology, disposition, and composition of the network. This 1930 information may be commercially sensitive, and may also be used in 1931 preparation for attacks, including any of the attacks described 1932 above. 1934 The following tables and objects may also be used to determine 1935 whether multicast data is flowing in the network, or has flowed 1936 recently. They may also be used to determine the network location of 1937 senders and recipients. An attacker can apply 'traffic analysis' to 1938 this data. In some cases, the information revealed by traffic 1939 analyses can be as damaging as full knowledge of the data being 1940 transported. 1942 ipMcastRouteEntryCount 1943 ipMcastInterfaceInMcastOctets 1944 ipMcastInterfaceOutMcastOctets 1945 ipMcastInterfaceInMcastPkts 1946 ipMcastInterfaceOutMcastPkts 1947 ipMcastInterfaceHCInMcastOctets 1948 ipMcastInterfaceHCOutMcastOctets 1949 ipMcastInterfaceHCInMcastPkts 1950 ipMcastInterfaceHCOutMcastPkts 1951 ipMcastRouteTable 1952 ipMcastRouteEntry 1953 ipMcastRouteGroupAddressType 1954 ipMcastRouteGroup 1955 ipMcastRouteGroupPrefixLength 1956 ipMcastRouteSourceAddressType 1957 ipMcastRouteSource 1958 ipMcastRouteSourcePrefixLength 1959 ipMcastRouteUpstreamNeighborType 1960 ipMcastRouteUpstreamNeighbor 1961 ipMcastRouteInIfIndex 1962 ipMcastRouteTimeStamp 1963 ipMcastRouteExpiryTime 1964 ipMcastRoutePkts 1965 ipMcastRouteDifferentInIfPackets 1966 ipMcastRouteOctets 1967 ipMcastRouteProtocol 1968 ipMcastRouteRtProtocol 1969 ipMcastRouteRtAddressType 1970 ipMcastRouteRtAddress 1971 ipMcastRouteRtPrefixLength 1972 ipMcastRouteRtType 1973 ipMcastRouteHCOctets 1974 ipMcastRouteDifferentInIfOctets 1975 ipMcastRouteNextHopTable 1976 ipMcastRouteNextHopEntry 1977 ipMcastRouteNextHopGroupAddressType 1978 ipMcastRouteNextHopGroup 1979 ipMcastRouteNextHopSourceAddressType 1980 ipMcastRouteNextHopSource 1981 ipMcastRouteNextHopSourcePrefixLength 1982 ipMcastRouteNextHopIfIndex 1983 ipMcastRouteNextHopAddressType 1984 ipMcastRouteNextHopAddress 1985 ipMcastRouteNextHopState 1986 ipMcastRouteNextHopTimeStamp 1987 ipMcastRouteNextHopExpiryTime 1988 ipMcastRouteNextHopClosestMemberHops 1989 ipMcastRouteNextHopProtocol 1990 ipMcastRouteNextHopPkts 1991 ipMcastRouteNextHopOctets 1992 ipMcastLocalListenerTable 1993 ipMcastLocalListenerEntry 1994 ipMcastLocalListenerGroupAddressType 1995 ipMcastLocalListenerGroupAddress 1996 ipMcastLocalListenerSourceAddressType 1997 ipMcastLocalListenerSourceAddress 1998 ipMcastLocalListenerSourcePrefixLength 1999 ipMcastLocalListenerRunIndex 2001 SNMP versions prior to SNMPv3 did not include adequate security. 2002 Even if the network itself is secure (for example by using IPSec), 2003 there is still no control over whom on the secure network is allowed 2004 to access (read/change/create/delete) the objects in this MIB module. 2006 It is RECOMMENDED that implementers consider the security features as 2007 provided by the SNMPv3 framework (see [RFC3410], section 8), 2008 including full support for the SNMPv3 cryptographic mechanisms (for 2009 authentication and privacy). 2011 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2012 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2013 enable cryptographic security. It is then a customer/operator 2014 responsibility to ensure that the SNMP entity giving access to an 2015 instance of this MIB module is properly configured to give access to 2016 the objects only to those principals (users) that have legitimate 2017 rights to access (read/change/create/delete) them. 2019 7. IANA Considerations 2021 IP-MCAST-MIB should be rooted under the mib-2 subtree. IANA is 2022 requested to assign { mib-2 XXX } to the IP-MCAST-MIB module 2023 specified in this document. 2025 8. Acknowledgements 2027 This MIB module is based on the original work in [RFC2932] by K. 2028 McCloghrie, D. Farinacci and D. Thaler. 2030 Suggested IPv6 multicast MIBs by R. Sivaramu and R. Raghunarayan have 2031 been used for comparison while editing this MIB module. 2033 The authors are also grateful to Bharat Joshi for his input and for 2034 several corrections. 2036 9. References 2038 9.1 Normative References 2040 [RFC1766] Alvestrand, H., "Tags for the Identification of 2041 Languages", RFC 1766, March 1995. 2043 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2044 Requirement Levels", BCP 14, RFC 2119, March 1997. 2046 [RFC2365] Meyer, D., "Administratively Scoped IP Multicast", BCP 23, 2047 RFC 2365, July 1998. 2049 [RFC2373] Hinden, R. and S. Deering, "IP Version 6 Addressing 2050 Architecture", RFC 2373, July 1998. 2052 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an 2053 IANA Considerations Section in RFCs", BCP 26, RFC 2434, 2054 October 1998. 2056 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2057 Schoenwaelder, Ed., "Structure of Management Information 2058 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2060 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2061 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 2062 STD 58, RFC 2579, April 1999. 2064 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2065 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2066 April 1999. 2068 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 2069 MIB", RFC 2863, June 2000. 2071 [RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 2072 Multicast Addresses", RFC 3306, August 2002. 2074 [RFC3569] Bhattacharyya, S., "An Overview of Source-Specific 2075 Multicast (SSM)", RFC 3569, July 2003. 2077 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2078 Schoenwaelder, "Textual Conventions for Internet Network 2079 Addresses", RFC 4001, February 2005. 2081 9.2 Informative References 2083 [RFC1075] Waitzman, D., Partridge, C., and S. Deering, "Distance 2084 Vector Multicast Routing Protocol", RFC 1075, 2085 November 1988. 2087 [RFC1584] Moy, J., "Multicast Extensions to OSPF", RFC 1584, 2088 March 1994. 2090 [RFC2189] Ballardie, T., "Core Based Trees (CBT version 2) Multicast 2091 Routing -- Protocol Specification --", RFC 2189, 2092 September 1997. 2094 [RFC2287] Krupczak, C. and J. Saperia, "Definitions of System-Level 2095 Managed Objects for Applications", RFC 2287, 2096 February 1998. 2098 [RFC2932] McCloghrie, K., Farinacci, D., and D. Thaler, "IPv4 2099 Multicast Routing MIB", RFC 2932, October 2000. 2101 [RFC2934] McCloghrie, K., Farinacci, D., Thaler, D., and B. Fenner, 2102 "Protocol Independent Multicast MIB for IPv4", RFC 2934, 2103 October 2000. 2105 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2106 "Introduction and Applicability Statements for Internet- 2107 Standard Management Framework", RFC 3410, December 2002. 2109 [I-D.ietf-pim-sm-v2-new] 2110 Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, 2111 "Protocol Independent Multicast - Sparse Mode PIM-SM): 2112 Protocol Specification (Revised)", 2113 draft-ietf-pim-sm-v2-new-12 (work in progress), 2114 March 2006. 2116 [I-D.ietf-pim-bidir] 2117 Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano, 2118 "Bi-directional Protocol Independent Multicast (BIDIR- 2119 PIM)", draft-ietf-pim-bidir-07 (work in progress), 2120 March 2005. 2122 Authors' Addresses 2124 David McWalter 2125 Data Connection Ltd 2126 100 Church Street 2127 Enfield EN2 6BQ 2128 UK 2130 Email: dmcw@dataconnection.com 2131 Dave Thaler 2132 Microsoft Corporation 2133 One Microsoft Way 2134 Redmond WA 98052-6399 2135 USA 2137 Email: dthaler@windows.microsoft.com 2139 Andrew Kessler 2140 Cisco Systems 2141 425 E. Tasman Drive 2142 San Jose CA 95134 2143 USA 2145 Email: kessler@cisco.com 2147 Intellectual Property Statement 2149 The IETF takes no position regarding the validity or scope of any 2150 Intellectual Property Rights or other rights that might be claimed to 2151 pertain to the implementation or use of the technology described in 2152 this document or the extent to which any license under such rights 2153 might or might not be available; nor does it represent that it has 2154 made any independent effort to identify any such rights. Information 2155 on the procedures with respect to rights in RFC documents can be 2156 found in BCP 78 and BCP 79. 2158 Copies of IPR disclosures made to the IETF Secretariat and any 2159 assurances of licenses to be made available, or the result of an 2160 attempt made to obtain a general license or permission for the use of 2161 such proprietary rights by implementers or users of this 2162 specification can be obtained from the IETF on-line IPR repository at 2163 http://www.ietf.org/ipr. 2165 The IETF invites any interested party to bring to its attention any 2166 copyrights, patents or patent applications, or other proprietary 2167 rights that may cover technology that may be required to implement 2168 this standard. Please address the information to the IETF at 2169 ietf-ipr@ietf.org. 2171 Disclaimer of Validity 2173 This document and the information contained herein are provided on an 2174 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2175 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 2176 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 2177 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 2178 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2179 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2181 Copyright Statement 2183 Copyright (C) The Internet Society (2006). This document is subject 2184 to the rights, licenses and restrictions contained in BCP 78, and 2185 except as set forth therein, the authors retain all their rights. 2187 Acknowledgment 2189 Funding for the RFC Editor function is currently provided by the 2190 Internet Society.