idnits 2.17.1 draft-ietf-mboned-ip-mcast-mib-06.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, updated by RFC 4748 on line 2801. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2778. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2785. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2791. ** The document seems to lack an RFC 3978 Section 5.4 Reference to BCP 78. 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 multicast IPv4 addresses in the document. If these are generic example addresses, they should be changed to use the 233.252.0.x range defined in RFC 5771 == The 'Obsoletes: ' line in the draft header should list only the _numbers_ of the RFCs which will be obsoleted by this document (if approved); it should not include the word 'RFC' in the list. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust 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 (July 30, 2007) is 6105 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) == Missing Reference: 'RFCzzzz' is mentioned on line 205, but not defined == Unused Reference: 'I-D.mcwalter-langtag-mib' is defined on line 2710, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-pim-bidir' is defined on line 2738, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 3569 -- Obsolete informational reference (is this intentional?): RFC 2932 (Obsoleted by RFC 5132) -- Obsolete informational reference (is this intentional?): RFC 4601 (Obsoleted by RFC 7761) -- Obsolete informational reference (is this intentional?): RFC 4646 (Obsoleted by RFC 5646) Summary: 3 errors (**), 0 flaws (~~), 8 warnings (==), 10 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 Proposed Status: Standards Track D. Thaler 5 Obsoletes: RFC 2932 (if approved) Microsoft Corporation 6 Expires: January 31, 2008 A. Kessler 7 Cisco Systems 8 July 30, 2007 10 IP Multicast MIB 11 draft-ietf-mboned-ip-mcast-mib-06.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 January 31, 2008. 38 Copyright Notice 40 Copyright (C) The IETF Trust (2007). 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. IMPORTed MIB Modules and REFERENCE Clauses . . . . . . . . . 4 57 6. Definitions . . . . . . . . . . . . . . . . . . . . . . . . 5 58 7. Security Considerations . . . . . . . . . . . . . . . . . . 54 59 7.1 SNMPv3 . . . . . . . . . . . . . . . . . . . . . . . . . . 54 60 7.2 Writeable objects . . . . . . . . . . . . . . . . . . . . 54 61 7.3 Readable objects . . . . . . . . . . . . . . . . . . . . . 55 62 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . 56 63 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 56 64 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 56 65 10.1 Normative References . . . . . . . . . . . . . . . . . . 56 66 10.2 Informative References . . . . . . . . . . . . . . . . . 57 67 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 58 68 Intellectual Property and Copyright Statements . . . . . . . 60 70 1. Introduction 72 This MIB describes objects used for managing IP multicast function, 73 including IP multicast routing. These objects are independent of the 74 specific multicast routing protocol in use. Managed objects specific 75 to particular multicast protocols are defined elsewhere. 77 2. History 79 This document obsoletes [RFC2932]. The MIB module defined by this 80 document is a re-working of the MIB module from [RFC2932], with 81 changes that include the following. 83 o This MIB module includes support for IPv6 addressing and the IPv6 84 scoped address architecture. [RFC2932] supported only IPv4. 86 o This MIB module allows several multicast protocols to perform 87 routing on a single interface, where [RFC2932] assumed each 88 interface supported at most one multicast routing protocol. 89 Multicast routing protocols are now per-route, see 90 ipMcastRouteProtocol. 92 o This MIB module includes objects that are not specific to 93 multicast routing. It allows management of multicast function on 94 systems that do not perform routing, whereas [RFC2932] was 95 restricted to multicast routing. 97 o This MIB module includes a table of Source-Specific Multicast 98 (SSM) address ranges to which SSM semantics [RFC3569] should be 99 applied. 101 o This MIB module includes a table of local applications that are 102 receiving multicast data. 104 o This MIB module includes a table of multicast scope zones. 106 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 107 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 108 document are to be interpreted as described in [RFC2119]. 110 3. The Internet-Standard Management Framework 112 For a detailed overview of the documents that describe the current 113 Internet-Standard Management Framework, please refer to section 7 of 114 [RFC3410]. 116 Managed objects are accessed via a virtual information store, termed 117 the Management Information Base or MIB. MIB objects are generally 118 accessed through the Simple Network Management Protocol (SNMP). 119 Objects in the MIB are defined using the mechanisms defined in the 120 Structure of Management Information (SMI). This memo specifies a MIB 121 module that is compliant to the SMIv2, which is described in STD 58, 122 ([RFC2578], [RFC2579] and [RFC2580]). 124 4. Overview 126 This MIB module contains two scalars and eight tables. The tables 127 are: 129 1. The IP Multicast Interface Table, which contains multicast 130 information specific to interfaces. 132 2. The IP Multicast SSM Range Table, which contains one row per 133 range of multicast group addresses to which Source-Specific 134 Multicast semantics [RFC3569] should be applied. 136 3. The IP Multicast Route Table, which contains multicast routing 137 information for IP datagrams sent by particular sources to the IP 138 multicast groups known to a system. 140 4. The IP Multicast Routing Next Hop Table, which contains 141 information about next-hops for the routing of IP multicast 142 datagrams. Each entry is one of a list of next-hops on outgoing 143 interfaces for particular sources sending to a particular 144 multicast group address. 146 5. The IP Multicast Scope Boundary Table, which contains the 147 boundaries configured for multicast scopes [RFC2365]. 149 6. The IP Multicast Scope Name Table, which contains human-readable 150 names for multicast scopes. 152 7. The IP Multicast Local Listener Table, which contains identifiers 153 for local applications that are receiving multicast data. 155 8. The IP Multicast Zone Table, which contains an entry for each 156 scope zone known to a system, and maps each zone to the multicast 157 address range that is the corresponding scope. 159 This MIB module uses textual conventions defined in the IF-MIB 160 [RFC2863], the INET-ADDRESS-MIB [RFC4001] and the IANA-RTPROTO-MIB. 162 5. IMPORTed MIB Modules and REFERENCE Clauses 164 The MIB modules defined in this document IMPORTs definitions 165 normatively from the following MIB modules, beyond [RFC2578], 167 [RFC2579], and [RFC2580]: HCNUM-TC [RFC2856], IF-MIB [RFC2863], IANA- 168 RTPROTO-MIB, SNMP-FRAMEWORK-MIB [RFC3411], INET-ADDRESS-MIB [RFC4001] 169 and LANGTAG-TC-MIB [RFCzzzz]. 171 -- Note to RFC Editor.: replace zzzz with LangTag MIB RFC number & 172 remove this note 174 This MIB module also includes REFERENCE clauses that make normative 175 references to Administratively Scoped IP Multicast [RFC2365], 176 Unicast-Prefix-based IPv6 Multicast Addresses [RFC3306], Source- 177 Specific Multicast, [RFC3569], IPv6 Scoped Address Architecture, 178 [RFC4007], and IPv6 Addressing Architecture, [RFC4291]. 180 Finally, this MIB module makes informative references to several RFCs 181 in text of DESCRIPTION clauses, including sysApplMIB [RFC2287], IP- 182 MIB [RFC4293], PIM-SMv2 Protocol Specification [RFC4601], and Tags 183 for Identifying Languages, [RFC4646]. 185 6. Definitions 187 IPMCAST-MIB DEFINITIONS ::= BEGIN 189 IMPORTS 190 MODULE-IDENTITY, OBJECT-TYPE, 191 mib-2, Unsigned32, Counter64, 192 Gauge32, TimeTicks FROM SNMPv2-SMI -- [RFC2578] 193 RowStatus, TruthValue, 194 StorageType, TimeStamp FROM SNMPv2-TC -- [RFC2579] 195 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- [RFC2580] 196 CounterBasedGauge64 FROM HCNUM-TC -- [RFC2856] 197 InterfaceIndexOrZero, 198 InterfaceIndex FROM IF-MIB -- [RFC2863] 199 IANAipRouteProtocol, 200 IANAipMRouteProtocol FROM IANA-RTPROTO-MIB 201 SnmpAdminString FROM SNMP-FRAMEWORK-MIB -- [RFC3411] 202 InetAddress, InetAddressType, 203 InetAddressPrefixLength, 204 InetZoneIndex, InetVersion FROM INET-ADDRESS-MIB -- [RFC4001] 205 LangTag FROM LANGTAG-TC-MIB; -- [RFCzzzz] 206 -- RFC Ed.: replace zzzz with LangTag MIB RFC number & remove this note 208 ipMcastMIB MODULE-IDENTITY 209 LAST-UPDATED "200707300000Z" -- 30 July 2007 210 ORGANIZATION "IETF MBONE Deployment (MBONED) Working Group" 211 CONTACT-INFO "David McWalter 212 Data Connection Limited 213 100 Church Street 214 Enfield, EN2 6BQ 215 UK 217 Phone: +44 208 366 1177 218 EMail: dmcw@dataconnection.com 220 Dave Thaler 221 Microsoft Corporation 222 One Microsoft Way 223 Redmond, WA 98052-6399 224 US 226 Phone: +1 425 703 8835 227 EMail: dthaler@dthaler.microsoft.com 229 Andrew Kessler 230 Cisco Systems 231 425 E. Tasman Drive 232 San Jose, CA 95134 233 US 235 Phone: +1 408 526 5139 236 EMail: kessler@cisco.com" 237 DESCRIPTION 238 "The MIB module for management of IP Multicast, including 239 multicast routing, data forwarding, and data reception. 241 Copyright (C) The IETF Trust (2007). This version of this 242 MIB module is part of RFC yyyy; see the RFC itself for full 243 legal notices." 244 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 245 REVISION "200707300000Z" -- 30 July 2007 246 DESCRIPTION "Initial version, published as RFC yyyy. 248 This MIB module obsoletes IPMROUTE-STD-MIB defined by 249 [RFC2932]. Changes include the following. 251 o This MIB module includes support for IPv6 addressing 252 and the IPv6 scoped address architecture. [RFC2932] 253 supported only IPv4. 255 o This MIB module allows several multicast protocols 256 to perform routing on a single interface, where 257 [RFC2932] assumed each interface supported at most 258 one multicast routing protocol. Multicast routing 259 protocols are now per-route, see 260 ipMcastRouteProtocol. 262 o This MIB module includes objects that are not 263 specific to multicast routing. It allows management 264 of multicast function on systems that do not perform 265 routing, whereas [RFC2932] was restricted to 266 multicast routing. 268 o This MIB module includes a table of Source-Specific 269 Multicast (SSM) address ranges to which SSM 270 semantics [RFC3569] should be applied. 272 o This MIB module includes a table of local 273 applications that are receiving multicast data. 275 o This MIB module includes a table of multicast scope 276 zones." 277 -- RFC Ed.: replace yyyy with actual RFC number & remove this note 278 ::= { mib-2 XXX } 279 -- RFC Ed.: replace XXX with IANA-assigned number & remove this note 281 -- 282 -- Top-level structure of the MIB 283 -- 285 ipMcast OBJECT IDENTIFIER ::= { ipMcastMIB 1 } 287 ipMcastEnabled OBJECT-TYPE 288 SYNTAX TruthValue 289 MAX-ACCESS read-write 290 STATUS current 291 DESCRIPTION 292 "The enabled status of IP Multicast function on this 293 system. 295 The storage type of this object is determined by 296 ipMcastDeviceConfigStorageType." 297 ::= { ipMcast 1 } 299 ipMcastRouteEntryCount OBJECT-TYPE 300 SYNTAX Gauge32 301 MAX-ACCESS read-only 302 STATUS current 303 DESCRIPTION 304 "The number of rows in the ipMcastRouteTable. This can be 305 used to check for multicast routing activity, and to monitor 306 the multicast routing table size." 307 ::= { ipMcast 2 } 309 ipMcastDeviceConfigStorageType OBJECT-TYPE 310 SYNTAX StorageType 311 MAX-ACCESS read-write 312 STATUS current 313 DESCRIPTION 314 "The storage type used for the global IP multicast 315 configuration of this device, comprised of the objects 316 listed below. If this storage type takes the value 317 'permanent', write-access to the listed objects need not be 318 allowed. 320 The objects described by this storage type are: 321 ipMcastEnabled." 322 DEFVAL { nonVolatile } 323 ::= { ipMcast 11 } 325 -- 326 -- The Multicast Interface Table 327 -- 329 ipMcastInterfaceTable OBJECT-TYPE 330 SYNTAX SEQUENCE OF IpMcastInterfaceEntry 331 MAX-ACCESS not-accessible 332 STATUS current 333 DESCRIPTION 334 "The (conceptual) table used to manage the multicast 335 protocol active on an interface." 336 ::= { ipMcast 3 } 338 ipMcastInterfaceEntry OBJECT-TYPE 339 SYNTAX IpMcastInterfaceEntry 340 MAX-ACCESS not-accessible 341 STATUS current 342 DESCRIPTION 343 "An entry (conceptual row) containing the multicast protocol 344 information for a particular interface. 346 Per-interface multicast forwarding statistics are also 347 available in ipIfStatsTable." 348 REFERENCE "RFC 4293 ipIfStatsTable" 349 INDEX { ipMcastInterfaceIPVersion, 350 ipMcastInterfaceIfIndex } 351 ::= { ipMcastInterfaceTable 1 } 353 IpMcastInterfaceEntry ::= SEQUENCE { 354 ipMcastInterfaceIPVersion InetVersion, 355 ipMcastInterfaceIfIndex InterfaceIndex, 356 ipMcastInterfaceTtl Unsigned32, 357 ipMcastInterfaceRateLimit Unsigned32, 358 ipMcastInterfaceStorageType StorageType 360 } 362 ipMcastInterfaceIPVersion OBJECT-TYPE 363 SYNTAX InetVersion 364 MAX-ACCESS not-accessible 365 STATUS current 366 DESCRIPTION 367 "The IP version of this row." 368 ::= { ipMcastInterfaceEntry 1 } 370 ipMcastInterfaceIfIndex OBJECT-TYPE 371 SYNTAX InterfaceIndex 372 MAX-ACCESS not-accessible 373 STATUS current 374 DESCRIPTION 375 "The index value that uniquely identifies the interface to 376 which this entry is applicable. The interface identified by 377 a particular value of this index is the same interface as 378 identified by the same value of the IF-MIB's ifIndex." 379 ::= { ipMcastInterfaceEntry 2 } 381 ipMcastInterfaceTtl OBJECT-TYPE 382 SYNTAX Unsigned32 (0..256) 383 MAX-ACCESS read-write 384 STATUS current 385 DESCRIPTION 386 "The datagram TTL threshold for the interface. Any IP 387 multicast datagrams with a TTL (IPv4) or Hop Limit (IPv6) 388 less than this threshold will not be forwarded out the 389 interface. The default value of 0 means all multicast 390 packets are forwarded out the interface. A value of 256 391 means that no multicast packets are forwarded out the 392 interface." 393 DEFVAL { 0 } 394 ::= { ipMcastInterfaceEntry 3 } 396 ipMcastInterfaceRateLimit OBJECT-TYPE 397 SYNTAX Unsigned32 398 MAX-ACCESS read-write 399 STATUS current 400 DESCRIPTION 401 "The rate-limit, in kilobits per second, of forwarded 402 multicast traffic on the interface. A rate-limit of 0 403 indicates that no rate limiting is done." 404 DEFVAL { 0 } 405 ::= { ipMcastInterfaceEntry 4 } 407 ipMcastInterfaceStorageType OBJECT-TYPE 408 SYNTAX StorageType 409 MAX-ACCESS read-write 410 STATUS current 411 DESCRIPTION 412 "The storage type for this row. Rows having the value 413 'permanent' need not allow write-access to any columnar 414 objects in the row." 415 DEFVAL { nonVolatile } 416 ::= { ipMcastInterfaceEntry 5 } 418 -- 419 -- The SSM Range Table 420 -- 422 ipMcastSsmRangeTable OBJECT-TYPE 423 SYNTAX SEQUENCE OF IpMcastSsmRangeEntry 424 MAX-ACCESS not-accessible 425 STATUS current 426 DESCRIPTION 427 "This table is used to create and manage the range(s) of 428 group addresses to which SSM semantics should be applied." 429 REFERENCE "RFC 3569" 430 ::= { ipMcast 4 } 432 ipMcastSsmRangeEntry OBJECT-TYPE 433 SYNTAX IpMcastSsmRangeEntry 434 MAX-ACCESS not-accessible 435 STATUS current 436 DESCRIPTION 437 "An entry (conceptual row) containing a range of group 438 addresses to which SSM semantics should be applied." 439 REFERENCE "RFC 3569" 440 INDEX { ipMcastSsmRangeAddressType, 441 ipMcastSsmRangeAddress, 442 ipMcastSsmRangePrefixLength } 443 ::= { ipMcastSsmRangeTable 1 } 445 IpMcastSsmRangeEntry ::= SEQUENCE { 446 ipMcastSsmRangeAddressType InetAddressType, 447 ipMcastSsmRangeAddress InetAddress, 448 ipMcastSsmRangePrefixLength InetAddressPrefixLength, 449 ipMcastSsmRangeRowStatus RowStatus, 450 ipMcastSsmRangeStorageType StorageType 451 } 453 ipMcastSsmRangeAddressType OBJECT-TYPE 454 SYNTAX InetAddressType 455 MAX-ACCESS not-accessible 456 STATUS current 457 DESCRIPTION 458 "The address type of the multicast group prefix." 459 ::= { ipMcastSsmRangeEntry 1 } 461 ipMcastSsmRangeAddress OBJECT-TYPE 462 SYNTAX InetAddress 463 MAX-ACCESS not-accessible 464 STATUS current 465 DESCRIPTION 466 "The multicast group address which, when combined with 467 ipMcastSsmRangePrefixLength, gives the group prefix for this 468 SSM range. The InetAddressType is given by 469 ipMcastSsmRangeAddressType. 471 This address object is only significant up to 472 ipMcastSsmRangePrefixLength bits. The remainder of the 473 address bits are zero. This is especially important for 474 this index field, which is part of the index of this entry. 475 Any non-zero bits would signify an entirely different 476 entry. 478 For IPv6 SSM address ranges, only ranges prefixed by 479 FF3x::/16 are permitted, where 'x' is a valid IPv6 RFC 4291 480 multicast address scope. The syntax of the address range is 481 given by RFC 3306 sections 4 and 7. 483 For addresses of type ipv4z or ipv6z, the appended zone 484 index is significant even though it lies beyond the prefix 485 length. The use of these address types indicate that this 486 SSM range entry applies only within the given zone. Zone 487 index zero is not valid in this table. 489 If non-global scope SSM range entries are present, then 490 consistent ipMcastBoundaryTable entries are required on 491 routers at the zone boundary." 492 REFERENCE "RFC 2365, RFC 4291 section 2.7, RFC 3306 sections 4, 6 493 and 7" 494 ::= { ipMcastSsmRangeEntry 2 } 496 ipMcastSsmRangePrefixLength OBJECT-TYPE 497 SYNTAX InetAddressPrefixLength 498 MAX-ACCESS not-accessible 499 STATUS current 500 DESCRIPTION 501 "The length in bits of the mask which, when combined with 502 ipMcastSsmRangeAddress, gives the group prefix for this SSM 503 range. 505 The InetAddressType is given by ipMcastSsmRangeAddressType. 506 For values 'ipv4' and 'ipv4z', this object must be in the 507 range 4..32. For values 'ipv6' and 'ipv6z', this object 508 must be in the range 8..128." 509 REFERENCE "RFC 2365, RFC 4291 section 2.7, RFC 3306 sections 4, 6 510 and 7" 511 ::= { ipMcastSsmRangeEntry 3 } 513 ipMcastSsmRangeRowStatus OBJECT-TYPE 514 SYNTAX RowStatus 515 MAX-ACCESS read-create 516 STATUS current 517 DESCRIPTION 518 "The status of this row, by which rows in this table can 519 be created and destroyed. 521 This status object can be set to active(1) without setting 522 any other columnar objects in this entry. 524 All writeable objects in this entry can be modified when the 525 status of this entry is active(1)." 526 ::= { ipMcastSsmRangeEntry 4 } 528 ipMcastSsmRangeStorageType OBJECT-TYPE 529 SYNTAX StorageType 530 MAX-ACCESS read-create 531 STATUS current 532 DESCRIPTION 533 "The storage type for this row. Rows having the value 534 'permanent' need not allow write-access to any columnar 535 objects in the row." 536 DEFVAL { nonVolatile } 537 ::= { ipMcastSsmRangeEntry 5 } 539 -- 540 -- The IP Multicast Routing Table 541 -- 543 ipMcastRouteTable OBJECT-TYPE 544 SYNTAX SEQUENCE OF IpMcastRouteEntry 545 MAX-ACCESS not-accessible 546 STATUS current 547 DESCRIPTION 548 "The (conceptual) table containing multicast routing 549 information for IP datagrams sent by particular sources to 550 to the IP multicast groups known to this router." 551 ::= { ipMcast 5 } 553 ipMcastRouteEntry OBJECT-TYPE 554 SYNTAX IpMcastRouteEntry 555 MAX-ACCESS not-accessible 556 STATUS current 557 DESCRIPTION 558 "An entry (conceptual row) containing the multicast routing 559 information for IP datagrams from a particular source and 560 addressed to a particular IP multicast group address." 561 INDEX { ipMcastRouteGroupAddressType, 562 ipMcastRouteGroup, 563 ipMcastRouteGroupPrefixLength, 564 ipMcastRouteSourceAddressType, 565 ipMcastRouteSource, 566 ipMcastRouteSourcePrefixLength } 567 ::= { ipMcastRouteTable 1 } 569 IpMcastRouteEntry ::= SEQUENCE { 570 ipMcastRouteGroupAddressType InetAddressType, 571 ipMcastRouteGroup InetAddress, 572 ipMcastRouteGroupPrefixLength InetAddressPrefixLength, 573 ipMcastRouteSourceAddressType InetAddressType, 574 ipMcastRouteSource InetAddress, 575 ipMcastRouteSourcePrefixLength InetAddressPrefixLength, 576 ipMcastRouteUpstreamNeighborType InetAddressType, 577 ipMcastRouteUpstreamNeighbor InetAddress, 578 ipMcastRouteInIfIndex InterfaceIndexOrZero, 579 ipMcastRouteTimeStamp TimeStamp, 580 ipMcastRouteExpiryTime TimeTicks, 581 ipMcastRouteProtocol IANAipMRouteProtocol, 582 ipMcastRouteRtProtocol IANAipRouteProtocol, 583 ipMcastRouteRtAddressType InetAddressType, 584 ipMcastRouteRtAddress InetAddress, 585 ipMcastRouteRtPrefixLength InetAddressPrefixLength, 586 ipMcastRouteRtType INTEGER, 587 ipMcastRouteOctets Counter64, 588 ipMcastRoutePkts Counter64, 589 ipMcastRouteTtlDropOctets Counter64, 590 ipMcastRouteTtlDropPackets Counter64, 591 ipMcastRouteDifferentInIfOctets Counter64, 592 ipMcastRouteDifferentInIfPackets Counter64, 593 ipMcastRouteBps CounterBasedGauge64 594 } 596 ipMcastRouteGroupAddressType OBJECT-TYPE 597 SYNTAX InetAddressType 598 MAX-ACCESS not-accessible 599 STATUS current 600 DESCRIPTION 601 "A value indicating the address family of the address 602 contained in ipMcastRouteGroup. Legal values correspond to 603 the subset of address families for which multicast 604 forwarding is supported." 605 ::= { ipMcastRouteEntry 1 } 607 ipMcastRouteGroup OBJECT-TYPE 608 SYNTAX InetAddress 609 MAX-ACCESS not-accessible 610 STATUS current 611 DESCRIPTION 612 "The IP multicast group address which, when combined with 613 the corresponding value specified in 614 ipMcastRouteGroupPrefixLength, identifies the groups for 615 which this entry contains multicast routing information. 617 This address object is only significant up to 618 ipMcastRouteGroupPrefixLength bits. The remainder of the 619 address bits are zero. This is especially important for 620 this index field, which is part of the index of this entry. 621 Any non-zero bits would signify an entirely different 622 entry. 624 For addresses of type ipv4z or ipv6z, the appended zone 625 index is significant even though it lies beyond the prefix 626 length. The use of these address types indicate that this 627 forwarding state applies only within the given zone. Zone 628 index zero is not valid in this table." 629 ::= { ipMcastRouteEntry 2 } 631 ipMcastRouteGroupPrefixLength OBJECT-TYPE 632 SYNTAX InetAddressPrefixLength 633 MAX-ACCESS not-accessible 634 STATUS current 635 DESCRIPTION 636 "The length in bits of the mask which, when combined with 637 the corresponding value of ipMcastRouteGroup, identifies the 638 groups for which this entry contains multicast routing 639 information. 641 The InetAddressType is given by 642 ipMcastRouteGroupAddressType. For values 'ipv4' and 643 'ipv4z', this object must be in the range 4..32. For values 644 'ipv6' and 'ipv6z', this object must be in the range 645 8..128." 646 ::= { ipMcastRouteEntry 3 } 648 ipMcastRouteSourceAddressType OBJECT-TYPE 649 SYNTAX InetAddressType 650 MAX-ACCESS not-accessible 651 STATUS current 652 DESCRIPTION 653 "A value indicating the address family of the address 654 contained in ipMcastRouteSource. The value MUST be the same 655 as the value of ipMcastRouteGroupType." 656 ::= { ipMcastRouteEntry 4 } 658 ipMcastRouteSource OBJECT-TYPE 659 SYNTAX InetAddress 660 MAX-ACCESS not-accessible 661 STATUS current 662 DESCRIPTION 663 "The network address which, when combined with the 664 corresponding value of ipMcastRouteSourcePrefixLength, 665 identifies the sources for which this entry contains 666 multicast routing information. 668 This address object is only significant up to 669 ipMcastRouteGroupPrefixLength bits. The remainder of the 670 address bits are zero. This is especially important for 671 this index field, which is part of the index of this entry. 672 Any non-zero bits would signify an entirely different 673 entry. 675 For addresses of type ipv4z or ipv6z, the appended zone 676 index is significant even though it lies beyond the prefix 677 length. The use of these address types indicate that this 678 source address applies only within the given zone. Zone 679 index zero is not valid in this table." 680 ::= { ipMcastRouteEntry 5 } 682 ipMcastRouteSourcePrefixLength OBJECT-TYPE 683 SYNTAX InetAddressPrefixLength 684 MAX-ACCESS not-accessible 685 STATUS current 686 DESCRIPTION 687 "The length in bits of the mask which, when combined with 688 the corresponding value of ipMcastRouteSource, identifies 689 the sources for which this entry contains multicast routing 690 information. 692 The InetAddressType is given by 693 ipMcastRouteSourceAddressType. For values 'ipv4' and 694 'ipv4z', this object must be in the range 4..32. For values 695 'ipv6' and 'ipv6z', this object must be in the range 696 8..128." 698 ::= { ipMcastRouteEntry 6 } 700 ipMcastRouteUpstreamNeighborType OBJECT-TYPE 701 SYNTAX InetAddressType 702 MAX-ACCESS read-only 703 STATUS current 704 DESCRIPTION 705 "A value indicating the address family of the address 706 contained in ipMcastRouteUpstreamNeighbor. 708 An address type of unknown(0) indicates that the upstream 709 neighbor is unknown, for example in BIDIR-PIM." 710 REFERENCE "I-D.ietf-pim-bidir" 711 ::= { ipMcastRouteEntry 7 } 713 ipMcastRouteUpstreamNeighbor OBJECT-TYPE 714 SYNTAX InetAddress 715 MAX-ACCESS read-only 716 STATUS current 717 DESCRIPTION 718 "The address of the upstream neighbor (for example, RPF 719 neighbor) from which IP datagrams from these sources to 720 this multicast address are received." 721 ::= { ipMcastRouteEntry 8 } 723 ipMcastRouteInIfIndex OBJECT-TYPE 724 SYNTAX InterfaceIndexOrZero 725 MAX-ACCESS read-only 726 STATUS current 727 DESCRIPTION 728 "The value of ifIndex for the interface on which IP 729 datagrams sent by these sources to this multicast address 730 are received. A value of 0 indicates that datagrams are not 731 subject to an incoming interface check, but may be accepted 732 on multiple interfaces (for example, in BIDIR-PIM)." 733 REFERENCE "I-D.ietf-pim-bidir" 734 ::= { ipMcastRouteEntry 9 } 736 ipMcastRouteTimeStamp OBJECT-TYPE 737 SYNTAX TimeStamp 738 MAX-ACCESS read-only 739 STATUS current 740 DESCRIPTION 741 "The value of sysUpTime at which the multicast routing 742 information represented by this entry was learned by the 743 router. 745 If this information was present at the most recent re- 746 initialization of the local management subsystem, then this 747 object contains a zero value." 748 ::= { ipMcastRouteEntry 10 } 750 ipMcastRouteExpiryTime OBJECT-TYPE 751 SYNTAX TimeTicks 752 MAX-ACCESS read-only 753 STATUS current 754 DESCRIPTION 755 "The minimum amount of time remaining before this entry will 756 be aged out. The value 0 indicates that the entry is not 757 subject to aging. If ipMcastRouteNextHopState is pruned(1), 758 this object represents the remaining time until the prune 759 expires. If this timer expires, state reverts to 760 forwarding(2). Otherwise, this object represents the time 761 until this entry is removed from the table." 762 ::= { ipMcastRouteEntry 11 } 764 ipMcastRouteProtocol OBJECT-TYPE 765 SYNTAX IANAipMRouteProtocol 766 MAX-ACCESS read-only 767 STATUS current 768 DESCRIPTION 769 "The multicast routing protocol via which this multicast 770 forwarding entry was learned." 771 ::= { ipMcastRouteEntry 12 } 773 ipMcastRouteRtProtocol OBJECT-TYPE 774 SYNTAX IANAipRouteProtocol 775 MAX-ACCESS read-only 776 STATUS current 777 DESCRIPTION 778 "The routing mechanism via which the route used to find the 779 upstream or parent interface for this multicast forwarding 780 entry was learned." 781 ::= { ipMcastRouteEntry 13 } 783 ipMcastRouteRtAddressType OBJECT-TYPE 784 SYNTAX InetAddressType 785 MAX-ACCESS read-only 786 STATUS current 787 DESCRIPTION 788 "A value indicating the address family of the address 789 contained in ipMcastRouteRtAddress." 790 ::= { ipMcastRouteEntry 14 } 792 ipMcastRouteRtAddress OBJECT-TYPE 793 SYNTAX InetAddress 794 MAX-ACCESS read-only 795 STATUS current 796 DESCRIPTION 797 "The address portion of the route used to find the upstream 798 or parent interface for this multicast forwarding entry. 800 This address object is only significant up to 801 ipMcastRouteGroupPrefixLength bits. The remainder of the 802 address bits are zero. 804 For addresses of type ipv4z or ipv6z, the appended zone 805 index is significant even though it lies beyond the prefix 806 length. The use of these address types indicate that this 807 forwarding state applies only within the given zone. Zone 808 index zero is not valid in this table." 809 ::= { ipMcastRouteEntry 15 } 811 ipMcastRouteRtPrefixLength OBJECT-TYPE 812 SYNTAX InetAddressPrefixLength 813 MAX-ACCESS read-only 814 STATUS current 815 DESCRIPTION 816 "The length in bits of the mask associated with the route 817 used to find the upstream or parent interface for this 818 multicast forwarding entry. 820 The InetAddressType is given by ipMcastRouteRtAddressType. 821 For values 'ipv4' and 'ipv4z', this object must be in the 822 range 4..32. For values 'ipv6' and 'ipv6z', this object 823 must be in the range 8..128." 824 ::= { ipMcastRouteEntry 16 } 826 ipMcastRouteRtType OBJECT-TYPE 827 SYNTAX INTEGER { 828 unicast (1), -- Unicast route used in multicast RIB 829 multicast (2) -- Multicast route 830 } 831 MAX-ACCESS read-only 832 STATUS current 833 DESCRIPTION 834 "The reason the given route was placed in the (logical) 835 multicast Routing Information Base (RIB). A value of 836 unicast means that the route would normally be placed only 837 in the unicast RIB, but was placed in the multicast RIB 838 (instead or in addition) due to local configuration, such as 839 when running PIM over RIP. A value of multicast means that 840 the route was explicitly added to the multicast RIB by the 841 routing protocol, such as DVMRP or Multiprotocol BGP." 843 ::= { ipMcastRouteEntry 17 } 845 ipMcastRouteOctets OBJECT-TYPE 846 SYNTAX Counter64 847 MAX-ACCESS read-only 848 STATUS current 849 DESCRIPTION 850 "The number of octets contained in IP datagrams which were 851 received from these sources and addressed to this multicast 852 group address, and which were forwarded by this router. 854 Discontinuities in this monotonically increasing value 855 occur at re-initialization of the management system. 856 Discontinuities can also occur as a result of routes being 857 removed and replaced, which can be detected by observing 858 the value of ipMcastRouteTimeStamp." 859 ::= { ipMcastRouteEntry 18 } 861 ipMcastRoutePkts OBJECT-TYPE 862 SYNTAX Counter64 863 MAX-ACCESS read-only 864 STATUS current 865 DESCRIPTION 866 "The number of packets routed using this multicast route 867 entry. 869 Discontinuities in this monotonically increasing value 870 occur at re-initialization of the management system. 871 Discontinuities can also occur as a result of routes being 872 removed and replaced, which can be detected by observing 873 the value of ipMcastRouteTimeStamp." 874 ::= { ipMcastRouteEntry 19 } 876 ipMcastRouteTtlDropOctets OBJECT-TYPE 877 SYNTAX Counter64 878 MAX-ACCESS read-only 879 STATUS current 880 DESCRIPTION 881 "The number of octets contained in IP datagrams which this 882 router has received from these sources and addressed to this 883 multicast group address, which were dropped because the TTL 884 (IPv4) or Hop Limit (IPv6) was decremented to zero, or to a 885 value less than ipMcastInterfaceTtl for all next hops. 887 Discontinuities in this monotonically increasing value 888 occur at re-initialization of the management system. 889 Discontinuities can also occur as a result of routes being 890 removed and replaced, which can be detected by observing 891 the value of ipMcastRouteTimeStamp." 892 ::= { ipMcastRouteEntry 20 } 894 ipMcastRouteTtlDropPackets OBJECT-TYPE 895 SYNTAX Counter64 896 MAX-ACCESS read-only 897 STATUS current 898 DESCRIPTION 899 "The number of packets which this router has received from 900 these sources and addressed to this multicast group address, 901 which were dropped because the TTL (IPv4) or Hop Limit 902 (IPv6) was decremented to zero, or to a value less than 903 ipMcastInterfaceTtl for all next hops. 905 Discontinuities in this monotonically increasing value 906 occur at re-initialization of the management system. 907 Discontinuities can also occur as a result of routes being 908 removed and replaced, which can be detected by observing 909 the value of ipMcastRouteTimeStamp." 910 ::= { ipMcastRouteEntry 21 } 912 ipMcastRouteDifferentInIfOctets OBJECT-TYPE 913 SYNTAX Counter64 914 MAX-ACCESS read-only 915 STATUS current 916 DESCRIPTION 917 "The number of octets contained in IP datagrams which this 918 router has received from these sources and addressed to this 919 multicast group address, which were dropped because they 920 were received on an unexpected interface. 922 For RPF checking protocols (such as PIM-SM), these packets 923 arrived on interfaces other than ipMcastRouteInIfIndex, and 924 were dropped because of this failed RPF check. (RPF paths 925 are 'Reverse Path Forwarding' path; the unicast routes to 926 the expected origin of multicast data flows). 928 Other protocols may drop packets on an incoming interface 929 check for different reasons (for example, BIDIR-PIM performs 930 a DF check on receipt of packets). All packets dropped as a 931 result of an incoming interface check are counted here. 933 If this counter increases rapidly, this indicates a problem. 934 A significant quantity of multicast data is arriving at this 935 router on unexpected interfaces, and is not being forwarded. 937 For guidance, if the rate of increase of this counter 938 exceeds 1% of the rate of increase of ipMcastRouteOctets, 939 then there are multicast routing problems that require 940 investigation. 942 Discontinuities in this monotonically increasing value 943 occur at re-initialization of the management system. 944 Discontinuities can also occur as a result of routes being 945 removed and replaced, which can be detected by observing 946 the value of ipMcastRouteTimeStamp." 947 REFERENCE "RFC 4601 and I-D.ietf-pim-bidir" 948 ::= { ipMcastRouteEntry 22 } 950 ipMcastRouteDifferentInIfPackets OBJECT-TYPE 951 SYNTAX Counter64 952 MAX-ACCESS read-only 953 STATUS current 954 DESCRIPTION 955 "The number of packets which this router has received from 956 these sources and addressed to this multicast group address, 957 which were dropped because they were received on an 958 unexpected interface. 960 For RPF checking protocols (such as PIM-SM), these packets 961 arrived on interfaces other than ipMcastRouteInIfIndex, and 962 were dropped because of this failed RPF check. (RPF paths 963 are 'Reverse Path Forwarding' path; the unicast routes to 964 the expected origin of multicast data flows). 966 Other protocols may drop packets on an incoming interface 967 check for different reasons (for example, BIDIR-PIM performs 968 a DF check on receipt of packets). All packets dropped as a 969 result of an incoming interface check are counted here. 971 If this counter increases rapidly, this indicates a problem. 972 A significant quantity of multicast data is arriving at this 973 router on unexpected interfaces, and is not being forwarded. 975 For guidance, if the rate of increase of this counter 976 exceeds 1% of the rate of increase of ipMcastRoutePkts, then 977 there are multicast routing problems that require 978 investigation. 980 Discontinuities in this monotonically increasing value 981 occur at re-initialization of the management system. 982 Discontinuities can also occur as a result of routes being 983 removed and replaced, which can be detected by observing 984 the value of ipMcastRouteTimeStamp." 985 REFERENCE "RFC 4601 and I-D.ietf-pim-bidir" 986 ::= { ipMcastRouteEntry 23 } 988 ipMcastRouteBps OBJECT-TYPE 989 SYNTAX CounterBasedGauge64 990 UNITS "bits per second" 991 MAX-ACCESS read-only 992 STATUS current 993 DESCRIPTION 994 "Bits per second forwarded by this router using this 995 multicast routing entry. 997 This value is a sample; it is the number of bits forwarded 998 during the last whole 1 second sampling period. The value 999 during the current 1 second sampling period is not made 1000 available until the period is completed. 1002 The quantity being sampled is the same as that measured by 1003 ipMcastRouteOctets. The units and the sampling method are 1004 different." 1005 ::= { ipMcastRouteEntry 24 } 1006 -- 1007 -- The IP Multicast Routing Next Hop Table 1008 -- 1010 ipMcastRouteNextHopTable OBJECT-TYPE 1011 SYNTAX SEQUENCE OF IpMcastRouteNextHopEntry 1012 MAX-ACCESS not-accessible 1013 STATUS current 1014 DESCRIPTION 1015 "The (conceptual) table containing information on the 1016 next-hops on outgoing interfaces for routing IP multicast 1017 datagrams. Each entry is one of a list of next-hops on 1018 outgoing interfaces for particular sources sending to a 1019 particular multicast group address." 1020 ::= { ipMcast 6 } 1022 ipMcastRouteNextHopEntry OBJECT-TYPE 1023 SYNTAX IpMcastRouteNextHopEntry 1024 MAX-ACCESS not-accessible 1025 STATUS current 1026 DESCRIPTION 1027 "An entry (conceptual row) in the list of next-hops on 1028 outgoing interfaces to which IP multicast datagrams from 1029 particular sources to an IP multicast group address are 1030 routed." 1031 INDEX { ipMcastRouteNextHopGroupAddressType, 1032 ipMcastRouteNextHopGroup, 1033 ipMcastRouteNextHopGroupPrefixLength, 1034 ipMcastRouteNextHopSourceAddressType, 1035 ipMcastRouteNextHopSource, 1036 ipMcastRouteNextHopSourcePrefixLength, 1037 ipMcastRouteNextHopIfIndex, 1038 ipMcastRouteNextHopAddressType, 1039 ipMcastRouteNextHopAddress } 1040 ::= { ipMcastRouteNextHopTable 1 } 1042 IpMcastRouteNextHopEntry ::= SEQUENCE { 1043 ipMcastRouteNextHopGroupAddressType InetAddressType, 1044 ipMcastRouteNextHopGroup InetAddress, 1045 ipMcastRouteNextHopGroupPrefixLength InetAddressPrefixLength, 1046 ipMcastRouteNextHopSourceAddressType InetAddressType, 1047 ipMcastRouteNextHopSource InetAddress, 1048 ipMcastRouteNextHopSourcePrefixLength InetAddressPrefixLength, 1049 ipMcastRouteNextHopIfIndex InterfaceIndex, 1050 ipMcastRouteNextHopAddressType InetAddressType, 1051 ipMcastRouteNextHopAddress InetAddress, 1052 ipMcastRouteNextHopState INTEGER, 1053 ipMcastRouteNextHopTimeStamp TimeStamp, 1054 ipMcastRouteNextHopExpiryTime TimeTicks, 1055 ipMcastRouteNextHopClosestMemberHops Unsigned32, 1056 ipMcastRouteNextHopProtocol IANAipMRouteProtocol, 1057 ipMcastRouteNextHopOctets Counter64, 1058 ipMcastRouteNextHopPkts Counter64 1059 } 1061 ipMcastRouteNextHopGroupAddressType OBJECT-TYPE 1062 SYNTAX InetAddressType 1063 MAX-ACCESS not-accessible 1064 STATUS current 1065 DESCRIPTION 1066 "A value indicating the address family of the address 1067 contained in ipMcastRouteNextHopGroup. Legal values 1068 correspond to the subset of address families for which 1069 multicast forwarding is supported." 1070 ::= { ipMcastRouteNextHopEntry 1 } 1072 ipMcastRouteNextHopGroup OBJECT-TYPE 1073 SYNTAX InetAddress 1074 MAX-ACCESS not-accessible 1075 STATUS current 1076 DESCRIPTION 1077 "The IP multicast group address which, when combined with 1078 the corresponding value specified in 1079 ipMcastRouteNextHopGroupPrefixLength, identifies the groups 1080 for which this entry contains multicast forwarding 1081 information. 1083 This address object is only significant up to 1084 ipMcastRouteNextHopGroupPrefixLength bits. The remainder of 1085 the address bits are zero. This is especially important for 1086 this index field, which is part of the index of this entry. 1087 Any non-zero bits would signify an entirely different 1088 entry. 1090 For addresses of type ipv4z or ipv6z, the appended zone 1091 index is significant even though it lies beyond the prefix 1092 length. The use of these address types indicate that this 1093 forwarding state applies only within the given zone. Zone 1094 index zero is not valid in this table." 1095 ::= { ipMcastRouteNextHopEntry 2 } 1097 ipMcastRouteNextHopGroupPrefixLength OBJECT-TYPE 1098 SYNTAX InetAddressPrefixLength 1099 MAX-ACCESS not-accessible 1100 STATUS current 1101 DESCRIPTION 1102 "The length in bits of the mask which, when combined with 1103 the corresponding value of ipMcastRouteGroup, identifies the 1104 groups for which this entry contains multicast routing 1105 information. 1107 The InetAddressType is given by 1108 ipMcastRouteNextHopGroupAddressType. For values 'ipv4' and 1109 'ipv4z', this object must be in the range 4..32. For values 1110 'ipv6' and 'ipv6z', this object must be in the range 1111 8..128." 1112 ::= { ipMcastRouteNextHopEntry 3 } 1114 ipMcastRouteNextHopSourceAddressType OBJECT-TYPE 1115 SYNTAX InetAddressType 1116 MAX-ACCESS not-accessible 1117 STATUS current 1118 DESCRIPTION 1119 "A value indicating the address family of the address 1120 contained in ipMcastRouteNextHopSource. The value MUST be 1121 the same as the value of ipMcastRouteNextHopGroupType." 1122 ::= { ipMcastRouteNextHopEntry 4 } 1124 ipMcastRouteNextHopSource OBJECT-TYPE 1125 SYNTAX InetAddress 1126 MAX-ACCESS not-accessible 1127 STATUS current 1128 DESCRIPTION 1129 "The network address which, when combined with the 1130 corresponding value of the mask specified in 1131 ipMcastRouteNextHopSourcePrefixLength, identifies the 1132 sources for which this entry specifies a next-hop on an 1133 outgoing interface. 1135 This address object is only significant up to 1136 ipMcastRouteNextHopSourcePrefixLength bits. The remainder 1137 of the address bits are zero. This is especially important 1138 for this index field, which is part of the index of this 1139 entry. Any non-zero bits would signify an entirely 1140 different entry. 1142 For addresses of type ipv4z or ipv6z, the appended zone 1143 index is significant even though it lies beyond the prefix 1144 length. The use of these address types indicate that this 1145 source address applies only within the given zone. Zone 1146 index zero is not valid in this table." 1147 ::= { ipMcastRouteNextHopEntry 5 } 1149 ipMcastRouteNextHopSourcePrefixLength OBJECT-TYPE 1150 SYNTAX InetAddressPrefixLength 1151 MAX-ACCESS not-accessible 1152 STATUS current 1153 DESCRIPTION 1154 "The length in bits of the mask which, when combined with 1155 the corresponding value specified in 1156 ipMcastRouteNextHopSource, identifies the sources for which 1157 this entry specifies a next-hop on an outgoing interface. 1159 The InetAddressType is given by 1160 ipMcastRouteNextHopSourceAddressType. For values 'ipv4' and 1161 'ipv4z', this object must be in the range 4..32. For values 1162 'ipv6' and 'ipv6z', this object must be in the range 1163 8..128." 1164 ::= { ipMcastRouteNextHopEntry 6 } 1166 ipMcastRouteNextHopIfIndex OBJECT-TYPE 1167 SYNTAX InterfaceIndex 1168 MAX-ACCESS not-accessible 1169 STATUS current 1170 DESCRIPTION 1171 "The ifIndex value of the interface for the outgoing 1172 interface for this next-hop." 1173 ::= { ipMcastRouteNextHopEntry 7 } 1175 ipMcastRouteNextHopAddressType OBJECT-TYPE 1176 SYNTAX InetAddressType 1177 MAX-ACCESS not-accessible 1178 STATUS current 1179 DESCRIPTION 1180 "A value indicating the address family of the address 1181 contained in ipMcastRouteNextHopAddress." 1182 ::= { ipMcastRouteNextHopEntry 8 } 1184 ipMcastRouteNextHopAddress OBJECT-TYPE 1185 SYNTAX InetAddress 1186 MAX-ACCESS not-accessible 1187 STATUS current 1188 DESCRIPTION 1189 "The address of the next-hop specific to this entry. For 1190 most interfaces, this is identical to 1191 ipMcastRouteNextHopGroup. NBMA interfaces, however, may 1192 have multiple next-hop addresses out a single outgoing 1193 interface." 1194 ::= { ipMcastRouteNextHopEntry 9 } 1196 ipMcastRouteNextHopState OBJECT-TYPE 1197 SYNTAX INTEGER { pruned(1), forwarding(2) } 1198 MAX-ACCESS read-only 1199 STATUS current 1200 DESCRIPTION 1201 "An indication of whether the outgoing interface and next- 1202 hop represented by this entry is currently being used to 1203 forward IP datagrams. The value 'forwarding' indicates it 1204 is currently being used; the value 'pruned' indicates it is 1205 not." 1206 ::= { ipMcastRouteNextHopEntry 10 } 1208 ipMcastRouteNextHopTimeStamp OBJECT-TYPE 1209 SYNTAX TimeStamp 1210 MAX-ACCESS read-only 1211 STATUS current 1212 DESCRIPTION 1213 "The value of sysUpTime at which the multicast routing 1214 information represented by this entry was learned by the 1215 router. 1217 If this infomration was present at the most recent re- 1218 initialization of the local management subsystem, then this 1219 object contains a zero value." 1220 ::= { ipMcastRouteNextHopEntry 11 } 1222 ipMcastRouteNextHopExpiryTime OBJECT-TYPE 1223 SYNTAX TimeTicks 1224 MAX-ACCESS read-only 1225 STATUS current 1226 DESCRIPTION 1227 "The minimum amount of time remaining before this entry will 1228 be aged out. If ipMcastRouteNextHopState is pruned(1), the 1229 remaining time until the prune expires and the state reverts 1230 to forwarding(2). Otherwise, the remaining time until this 1231 entry is removed from the table. The time remaining may be 1232 copied from ipMcastRouteExpiryTime if the protocol in use 1233 for this entry does not specify next-hop timers. The value 1234 0 indicates that the entry is not subject to aging." 1235 ::= { ipMcastRouteNextHopEntry 12 } 1237 ipMcastRouteNextHopClosestMemberHops OBJECT-TYPE 1238 SYNTAX Unsigned32 (0..256) 1239 MAX-ACCESS read-only 1240 STATUS current 1241 DESCRIPTION 1242 "The minimum number of hops between this router and any 1243 member of this IP multicast group reached via this next-hop 1244 on this outgoing interface. Any IP multicast datagrams for 1245 the group which have a TTL (IPv4) or Hop Count (IPv6) less 1246 than this number of hops will not be forwarded to this 1247 next-hop. 1249 A value of 0 means all multicast datagrams are forwarded out 1250 the interface. A value of 256 means that no multicast 1251 datagrams are forwarded out the interface. 1253 This is an optimization applied by multicast routing 1254 protocols that explicitly track hop counts to downstream 1255 listeners. Multicast protocols that are not aware of hop 1256 counts to downstream listeners set this object to 0." 1257 ::= { ipMcastRouteNextHopEntry 13 } 1259 ipMcastRouteNextHopProtocol OBJECT-TYPE 1260 SYNTAX IANAipMRouteProtocol 1261 MAX-ACCESS read-only 1262 STATUS current 1263 DESCRIPTION 1264 "The routing mechanism via which this next-hop was learned." 1265 ::= { ipMcastRouteNextHopEntry 14 } 1267 ipMcastRouteNextHopOctets OBJECT-TYPE 1268 SYNTAX Counter64 1269 MAX-ACCESS read-only 1270 STATUS current 1271 DESCRIPTION 1272 "The number of octets of multicast packets that have been 1273 forwarded using this route. 1275 Discontinuities in this monotonically increasing value 1276 occur at re-initialization of the management system. 1277 Discontinuities can also occur as a result of routes being 1278 removed and replaced, which can be detected by observing 1279 the value of ipMcastRouteNextHopTimeStamp." 1280 ::= { ipMcastRouteNextHopEntry 15 } 1282 ipMcastRouteNextHopPkts OBJECT-TYPE 1283 SYNTAX Counter64 1284 MAX-ACCESS read-only 1285 STATUS current 1286 DESCRIPTION 1287 "The number of packets which have been forwarded using this 1288 route. 1290 Discontinuities in this monotonically increasing value 1291 occur at re-initialization of the management system. 1292 Discontinuities can also occur as a result of routes being 1293 removed and replaced, which can be detected by observing 1294 the value of ipMcastRouteNextHopTimeStamp." 1295 ::= { ipMcastRouteNextHopEntry 16 } 1297 -- 1298 -- The IP Multicast Scope Boundary Table 1299 -- 1301 ipMcastBoundaryTable OBJECT-TYPE 1302 SYNTAX SEQUENCE OF IpMcastBoundaryEntry 1303 MAX-ACCESS not-accessible 1304 STATUS current 1305 DESCRIPTION 1306 "The (conceptual) table listing the system's multicast scope 1307 zone boundaries." 1308 REFERENCE "RFC 4007 section 5" 1309 ::= { ipMcast 7 } 1311 ipMcastBoundaryEntry OBJECT-TYPE 1312 SYNTAX IpMcastBoundaryEntry 1313 MAX-ACCESS not-accessible 1314 STATUS current 1315 DESCRIPTION 1316 "An entry (conceptual row) describing one of this device's 1317 multicast scope zone boundaries." 1318 REFERENCE "RFC 2365 section 5, RFC 4007 section 5" 1319 INDEX { ipMcastBoundaryIfIndex, 1320 ipMcastBoundaryAddressType, 1321 ipMcastBoundaryAddress, 1322 ipMcastBoundaryAddressPrefixLength } 1323 ::= { ipMcastBoundaryTable 1 } 1325 IpMcastBoundaryEntry ::= SEQUENCE { 1326 ipMcastBoundaryIfIndex InterfaceIndex, 1327 ipMcastBoundaryAddressType InetAddressType, 1328 ipMcastBoundaryAddress InetAddress, 1329 ipMcastBoundaryAddressPrefixLength InetAddressPrefixLength, 1330 ipMcastBoundaryTimeStamp TimeStamp, 1331 ipMcastBoundaryDroppedMcastOctets Counter64, 1332 ipMcastBoundaryDroppedMcastPkts Counter64, 1333 ipMcastBoundaryStatus RowStatus, 1334 ipMcastBoundaryStorageType StorageType 1335 } 1337 ipMcastBoundaryIfIndex OBJECT-TYPE 1338 SYNTAX InterfaceIndex 1339 MAX-ACCESS not-accessible 1340 STATUS current 1341 DESCRIPTION 1342 "The IfIndex value for the interface to which this boundary 1343 applies. Packets with a destination address in the 1344 associated address/mask range will not be forwarded over 1345 this interface. 1347 For IPv4, zone boundaries cut through links. Therefore this 1348 is an external interface. This may be either a physical or 1349 virtual interface (tunnel, encapsulation, and so forth.) 1351 For IPv6, zone boundaries cut through nodes. Therefore this 1352 is a virtual interface within the node. This is not an 1353 external interface, either real or virtual. Packets 1354 crossing this interface neither arrive at nor leave the 1355 node, but only move between zones within the node." 1356 REFERENCE "RFC 2365 section 5, RFC 4007 section 5" 1357 ::= { ipMcastBoundaryEntry 1 } 1359 ipMcastBoundaryAddressType OBJECT-TYPE 1360 SYNTAX InetAddressType 1361 MAX-ACCESS not-accessible 1362 STATUS current 1363 DESCRIPTION 1364 "A value indicating the address family of the address 1365 contained in ipMcastBoundaryAddress. Legal values 1366 correspond to the subset of address families for which 1367 multicast forwarding is supported." 1368 ::= { ipMcastBoundaryEntry 2 } 1370 ipMcastBoundaryAddress OBJECT-TYPE 1371 SYNTAX InetAddress 1372 MAX-ACCESS not-accessible 1373 STATUS current 1374 DESCRIPTION 1375 "The group address which, when combined with the 1376 corresponding value of ipMcastBoundaryAddressPrefixLength, 1377 identifies the group range for which the scoped boundary 1378 exists. Scoped IPv4 multicast address ranges must be 1379 prefixed by 239.0.0.0/8. Scoped IPv6 multicast address 1380 ranges are FF0x::/16, where x is a valid RFC 4291 multicast 1381 scope. 1383 An IPv6 address prefixed by FF1x::/16 is a non-permanently- 1384 assigned address. An IPv6 address prefixed by FF3x::/16 is 1385 a unicast-prefix-based multicast addresses. A zone boundary 1386 for FF0x::/16 implies an identical boundary for these other 1387 prefixes. No separate FF1x::/16 or FF3x::/16 entries exist 1388 in this table. 1390 This address object is only significant up to 1391 ipMcastBoundaryAddressPrefixLength bits. The remainder of 1392 the address bits are zero. This is especially important for 1393 this index field, which is part of the index of this entry. 1394 Any non-zero bits would signify an entirely different 1395 entry." 1396 ::= { ipMcastBoundaryEntry 3 } 1398 ipMcastBoundaryAddressPrefixLength OBJECT-TYPE 1399 SYNTAX InetAddressPrefixLength 1400 MAX-ACCESS not-accessible 1401 STATUS current 1402 DESCRIPTION 1403 "The length in bits of the mask which when, combined with 1404 the corresponding value of ipMcastBoundaryAddress, 1405 identifies the group range for which the scoped boundary 1406 exists. 1408 The InetAddressType is given by ipMcastBoundaryAddressType. 1409 For values 'ipv4' and 'ipv4z', this object must be in the 1410 range 4..32. For values 'ipv6' and 'ipv6z', this object 1411 must be set to 16." 1412 ::= { ipMcastBoundaryEntry 4 } 1414 ipMcastBoundaryTimeStamp OBJECT-TYPE 1415 SYNTAX TimeStamp 1416 MAX-ACCESS read-only 1417 STATUS current 1418 DESCRIPTION 1419 "The value of sysUpTime at which the multicast boundary 1420 information represented by this entry was learned by the 1421 router. 1423 If this infomration was present at the most recent re- 1424 initialization of the local management subsystem, then this 1425 object contains a zero value." 1426 ::= { ipMcastBoundaryEntry 5 } 1428 ipMcastBoundaryDroppedMcastOctets OBJECT-TYPE 1429 SYNTAX Counter64 1430 MAX-ACCESS read-only 1431 STATUS current 1432 DESCRIPTION 1433 "The number of octets of multicast packets that have been 1434 dropped as a result of this zone boundary configuration. 1436 Discontinuities in this monotonically increasing value 1437 occur at re-initialization of the management system. 1438 Discontinuities can also occur as a result of boundary 1439 configuration being removed and replaced, which can be 1440 detected by observing the value of 1441 ipMcastBoundaryTimeStamp." 1442 ::= { ipMcastBoundaryEntry 6 } 1444 ipMcastBoundaryDroppedMcastPkts OBJECT-TYPE 1445 SYNTAX Counter64 1446 MAX-ACCESS read-only 1447 STATUS current 1448 DESCRIPTION 1449 "The number of multicast packets that have been dropped as a 1450 result of this zone boundary configuration. 1452 Discontinuities in this monotonically increasing value 1453 occur at re-initialization of the management system. 1454 Discontinuities can also occur as a result of boundary 1455 configuration being removed and replaced, which can be 1456 detected by observing the value of 1457 ipMcastBoundaryTimeStamp." 1458 ::= { ipMcastBoundaryEntry 7 } 1460 ipMcastBoundaryStatus OBJECT-TYPE 1461 SYNTAX RowStatus 1462 MAX-ACCESS read-create 1463 STATUS current 1464 DESCRIPTION 1465 "The status of this row, by which rows in this table can 1466 be created and destroyed. 1468 This status object can be set to active(1) without setting 1469 any other columnar objects in this entry. 1471 All writeable objects in this entry can be modified when the 1472 status of this entry is active(1)." 1473 ::= { ipMcastBoundaryEntry 8 } 1475 ipMcastBoundaryStorageType OBJECT-TYPE 1476 SYNTAX StorageType 1477 MAX-ACCESS read-create 1478 STATUS current 1479 DESCRIPTION 1480 "The storage type for this row. Rows having the value 1481 'permanent' need not allow write-access to any columnar 1482 objects in the row." 1483 DEFVAL { nonVolatile } 1484 ::= { ipMcastBoundaryEntry 9 } 1486 -- 1487 -- The IP Multicast Scope Name Table 1488 -- 1490 ipMcastScopeNameTable OBJECT-TYPE 1491 SYNTAX SEQUENCE OF IpMcastScopeNameEntry 1492 MAX-ACCESS not-accessible 1493 STATUS current 1494 DESCRIPTION 1495 "The (conceptual) table listing multicast scope names." 1496 REFERENCE "RFC 4007 section 4" 1497 ::= { ipMcast 8 } 1499 ipMcastScopeNameEntry OBJECT-TYPE 1500 SYNTAX IpMcastScopeNameEntry 1501 MAX-ACCESS not-accessible 1502 STATUS current 1503 DESCRIPTION 1504 "An entry (conceptual row) that names a multicast address 1505 scope." 1506 REFERENCE "RFC 4007 section 4" 1507 INDEX { ipMcastScopeNameAddressType, 1508 ipMcastScopeNameAddress, 1509 ipMcastScopeNameAddressPrefixLength, 1510 ipMcastScopeNameLanguage } 1511 ::= { ipMcastScopeNameTable 1 } 1513 IpMcastScopeNameEntry ::= SEQUENCE { 1514 ipMcastScopeNameAddressType InetAddressType, 1515 ipMcastScopeNameAddress InetAddress, 1516 ipMcastScopeNameAddressPrefixLength InetAddressPrefixLength, 1517 ipMcastScopeNameLanguage LangTag, 1518 ipMcastScopeNameString SnmpAdminString, 1519 ipMcastScopeNameDefault TruthValue, 1520 ipMcastScopeNameStatus RowStatus, 1521 ipMcastScopeNameStorageType StorageType 1522 } 1524 ipMcastScopeNameAddressType OBJECT-TYPE 1525 SYNTAX InetAddressType 1526 MAX-ACCESS not-accessible 1527 STATUS current 1528 DESCRIPTION 1529 "A value indicating the address family of the address 1530 contained in ipMcastScopeNameAddress. Legal values 1531 correspond to the subset of address families for which 1532 multicast forwarding is supported." 1533 ::= { ipMcastScopeNameEntry 1 } 1535 ipMcastScopeNameAddress OBJECT-TYPE 1536 SYNTAX InetAddress 1537 MAX-ACCESS not-accessible 1538 STATUS current 1539 DESCRIPTION 1540 "The group address which, when combined with the 1541 corresponding value of ipMcastScopeNameAddressPrefixLength, 1542 identifies the group range associated with the multicast 1543 scope. Scoped IPv4 multicast address ranges must be 1544 prefixed by 239.0.0.0/8. Scoped IPv6 multicast address 1545 ranges are FF0x::/16, where x is a valid RFC 4291 multicast 1546 scope. 1548 An IPv6 address prefixed by FF1x::/16 is a non-permanently- 1549 assigned address. An IPv6 address prefixed by FF3x::/16 is 1550 a unicast-prefix-based multicast addresses. A scope 1551 FF0x::/16 implies an identical scope name for these other 1552 prefixes. No separate FF1x::/16 or FF3x::/16 entries exist 1553 in this table. 1555 This address object is only significant up to 1556 ipMcastScopeNameAddressPrefixLength bits. The remainder of 1557 the address bits are zero. This is especially important for 1558 this index field, which is part of the index of this entry. 1559 Any non-zero bits would signify an entirely different 1560 entry." 1561 ::= { ipMcastScopeNameEntry 2 } 1563 ipMcastScopeNameAddressPrefixLength OBJECT-TYPE 1564 SYNTAX InetAddressPrefixLength 1565 MAX-ACCESS not-accessible 1566 STATUS current 1567 DESCRIPTION 1568 "The length in bits of the mask which, when combined with 1569 the corresponding value of ipMcastScopeNameAddress, 1570 identifies the group range associated with the multicast 1571 scope. 1573 The InetAddressType is given by ipMcastScopeNameAddressType. 1574 For values 'ipv4' and 'ipv4z', this object must be in the 1575 range 4..32. For values 'ipv6' and 'ipv6z', this object 1576 must be set to 16." 1577 ::= { ipMcastScopeNameEntry 3 } 1579 ipMcastScopeNameLanguage OBJECT-TYPE 1580 SYNTAX LangTag 1581 MAX-ACCESS not-accessible 1582 STATUS current 1583 DESCRIPTION 1584 "Language tag associated with the scope name." 1585 REFERENCE "RFC 4646" 1586 ::= { ipMcastScopeNameEntry 4 } 1588 ipMcastScopeNameString OBJECT-TYPE 1589 SYNTAX SnmpAdminString 1590 MAX-ACCESS read-create 1591 STATUS current 1592 DESCRIPTION 1593 "The textual name associated with the multicast scope. The 1594 value of this object should be suitable for displaying to 1595 end-users, such as when allocating a multicast address in 1596 this scope. 1598 When no name is specified, the default value of this object 1599 for IPv4 should is the string 239.x.x.x/y with x and y 1600 replaced with decimal values to describe the address and 1601 mask length associated with the scope. 1603 When no name is specified, the default value of this object 1604 for IPv6 should is the string FF0x::/16, with x replaced by 1605 the hexadecimal value for the RFC 4291 multicast scope. 1607 An IPv6 address prefixed by FF1x::/16 is a non-permanently- 1608 assigned address. An IPv6 address prefixed by FF3x::/16 is 1609 a unicast-prefix-based multicast addresses. A scope 1610 FF0x::/16 implies an identical scope name for these other 1611 prefixes. No separate FF1x::/16 or FF3x::/16 entries exist 1612 in this table." 1614 REFERENCE "RFC 2365, RFC 3306 section 4, RFC 4291 section 2.7" 1615 ::= { ipMcastScopeNameEntry 5 } 1617 ipMcastScopeNameDefault OBJECT-TYPE 1618 SYNTAX TruthValue 1619 MAX-ACCESS read-create 1620 STATUS current 1621 DESCRIPTION 1622 "If true, indicates a preference that the name in the 1623 following language should be used by applications if no name 1624 is available in a desired language." 1625 DEFVAL { false } 1626 ::= { ipMcastScopeNameEntry 6 } 1628 ipMcastScopeNameStatus OBJECT-TYPE 1629 SYNTAX RowStatus 1630 MAX-ACCESS read-create 1631 STATUS current 1632 DESCRIPTION 1633 "The status of this row, by which rows in this table can 1634 be created and destroyed. Before the row can be activated, 1635 the object ipMcastScopeNameString must be set to a valid 1636 value. All writeable objects in this entry can be modified 1637 when the status is active(1)." 1638 ::= { ipMcastScopeNameEntry 7 } 1640 ipMcastScopeNameStorageType OBJECT-TYPE 1641 SYNTAX StorageType 1642 MAX-ACCESS read-create 1643 STATUS current 1644 DESCRIPTION 1645 "The storage type for this row. Rows having the value 1646 'permanent' need not allow write-access to any columnar 1647 objects in the row." 1648 DEFVAL { nonVolatile } 1649 ::= { ipMcastScopeNameEntry 8 } 1651 -- 1652 -- The Multicast Listeners Table 1653 -- 1655 ipMcastLocalListenerTable OBJECT-TYPE 1656 SYNTAX SEQUENCE OF IpMcastLocalListenerEntry 1657 MAX-ACCESS not-accessible 1658 STATUS current 1659 DESCRIPTION 1660 "The (conceptual) table listing local applications or 1661 services that have joined multicast groups as listeners. 1663 Entries exist for all addresses in the multicast range for 1664 all applications and services as they are classified on this 1665 device." 1666 ::= { ipMcast 9 } 1668 ipMcastLocalListenerEntry OBJECT-TYPE 1669 SYNTAX IpMcastLocalListenerEntry 1670 MAX-ACCESS not-accessible 1671 STATUS current 1672 DESCRIPTION 1673 "An entry (conceptual row) identifying a local application 1674 or service that has joined a multicast group as a listener." 1675 INDEX { ipMcastLocalListenerGroupAddressType, 1676 ipMcastLocalListenerGroupAddress, 1677 ipMcastLocalListenerSourceAddressType, 1678 ipMcastLocalListenerSourceAddress, 1679 ipMcastLocalListenerSourcePrefixLength, 1680 ipMcastLocalListenerIfIndex, 1681 ipMcastLocalListenerRunIndex } 1682 ::= { ipMcastLocalListenerTable 1 } 1684 IpMcastLocalListenerEntry ::= SEQUENCE { 1685 ipMcastLocalListenerGroupAddressType InetAddressType, 1686 ipMcastLocalListenerGroupAddress InetAddress, 1687 ipMcastLocalListenerSourceAddressType InetAddressType, 1688 ipMcastLocalListenerSourceAddress InetAddress, 1689 ipMcastLocalListenerSourcePrefixLength InetAddressPrefixLength, 1690 ipMcastLocalListenerIfIndex InterfaceIndex, 1691 ipMcastLocalListenerRunIndex Unsigned32 1692 } 1694 ipMcastLocalListenerGroupAddressType OBJECT-TYPE 1695 SYNTAX InetAddressType 1696 MAX-ACCESS not-accessible 1697 STATUS current 1698 DESCRIPTION 1699 "A value indicating the address family of the address 1700 contained in ipMcastLocalListenerGroupAddress. Legal values 1701 correspond to the subset of address families for which 1702 multicast is supported." 1703 ::= { ipMcastLocalListenerEntry 1 } 1705 ipMcastLocalListenerGroupAddress OBJECT-TYPE 1706 SYNTAX InetAddress 1707 MAX-ACCESS not-accessible 1708 STATUS current 1709 DESCRIPTION 1710 "The IP multicast group for which this entry specifies 1711 locally joined applications or services." 1712 ::= { ipMcastLocalListenerEntry 2 } 1714 ipMcastLocalListenerSourceAddressType OBJECT-TYPE 1715 SYNTAX InetAddressType 1716 MAX-ACCESS not-accessible 1717 STATUS current 1718 DESCRIPTION 1719 "A value indicating the address family of the address 1720 contained in ipMcastLocalListenerSource. The value MUST be 1721 the same as the value of 1722 ipMcastLocalListenerGroupAddressType." 1723 ::= { ipMcastLocalListenerEntry 3 } 1725 ipMcastLocalListenerSourceAddress OBJECT-TYPE 1726 SYNTAX InetAddress 1727 MAX-ACCESS not-accessible 1728 STATUS current 1729 DESCRIPTION 1730 "The network address which, when combined with the 1731 corresponding value of the mask specified in 1732 ipMcastLocalListenerSourcePrefixLength, identifies the 1733 sources for which this entry specifies a local listener. 1735 This address object is only significant up to 1736 ipMcastLocalListenerSourcePrefixLength bits. The remainder 1737 of the address bits are zero. This is especially important 1738 for this index field, which is part of the index of this 1739 entry. Any non-zero bits would signify an entirely 1740 different entry. 1742 For addresses of type ipv4z or ipv6z, the appended zone 1743 index is significant even though it lies beyond the prefix 1744 length. The use of these address types indicate that this 1745 listener address applies only within the given zone. Zone 1746 index zero is not valid in this table." 1747 ::= { ipMcastLocalListenerEntry 4 } 1749 ipMcastLocalListenerSourcePrefixLength OBJECT-TYPE 1750 SYNTAX InetAddressPrefixLength 1751 MAX-ACCESS not-accessible 1752 STATUS current 1753 DESCRIPTION 1754 "The length in bits of the mask which, when combined with 1755 the corresponding value specified in 1756 ipMcastLocalListenerSource, identifies the sources for which 1757 this entry specifies a local listener. A mask length of 1758 zero corresponds to all sources within the group. 1760 The InetAddressType is given by 1761 ipMcastLocalListenerSourceAddressType. For values 'ipv4' 1762 and 'ipv4z', this object must be in the range 4..32. For 1763 values 'ipv6' and 'ipv6z', this object must be in the range 1764 8..128." 1765 ::= { ipMcastLocalListenerEntry 5 } 1767 ipMcastLocalListenerIfIndex OBJECT-TYPE 1768 SYNTAX InterfaceIndex 1769 MAX-ACCESS not-accessible 1770 STATUS current 1771 DESCRIPTION 1772 "The IfIndex value of the interface for which this entry 1773 specifies a local listener." 1774 ::= { ipMcastLocalListenerEntry 6 } 1776 ipMcastLocalListenerRunIndex OBJECT-TYPE 1777 SYNTAX Unsigned32 (0..2147483647) 1778 MAX-ACCESS read-only 1779 STATUS current 1780 DESCRIPTION 1781 "A unique value corresponding to a piece of software running 1782 on this router or host system. Where possible, this should 1783 be the system's native, unique identification number. 1785 This identifier is platform-specific. It may correspond to 1786 a process ID or application instance number. 1788 A value of zero indicates that the application instance(s) 1789 cannot be identified. A value of zero indicates that one or 1790 more unidentified applications have joined the specified 1791 multicast groups (for the specified sources) as listeners." 1792 REFERENCE "RFC 2287 sysApplRunIndex" 1793 ::= { ipMcastLocalListenerEntry 7 } 1795 -- 1796 -- The Multicast Zone Table 1797 -- 1799 ipMcastZoneTable OBJECT-TYPE 1800 SYNTAX SEQUENCE OF IpMcastZoneEntry 1801 MAX-ACCESS not-accessible 1802 STATUS current 1803 DESCRIPTION 1804 "The (conceptual) table listing scope zones on this device." 1805 REFERENCE "RFC 4007 section 5" 1806 ::= { ipMcast 10 } 1808 ipMcastZoneEntry OBJECT-TYPE 1809 SYNTAX IpMcastZoneEntry 1810 MAX-ACCESS not-accessible 1811 STATUS current 1812 DESCRIPTION 1813 "An entry (conceptual row) describing a scope zone on this 1814 device." 1815 REFERENCE "RFC 4007 section 5" 1816 INDEX { ipMcastZoneIndex } 1817 ::= { ipMcastZoneTable 1 } 1819 IpMcastZoneEntry ::= SEQUENCE { 1820 ipMcastZoneIndex InetZoneIndex, 1821 ipMcastZoneScopeDefaultZoneIndex InetZoneIndex, 1822 ipMcastZoneScopeAddressType InetAddressType, 1823 ipMcastZoneScopeAddress InetAddress, 1824 ipMcastZoneScopeAddressPrefixLength InetAddressPrefixLength 1825 } 1827 ipMcastZoneIndex OBJECT-TYPE 1828 SYNTAX InetZoneIndex (1..4294967295) 1829 MAX-ACCESS not-accessible 1830 STATUS current 1831 DESCRIPTION 1832 "This zone index uniquely identifies a zone on a device. 1834 Each zone is for a given scope. Scope-level information in 1835 this table is for the unique scope that corresponds to this 1836 zone. 1838 Zero is a special value used to request the default zone for 1839 a given scope. Zero is not a valid value for this object. 1841 To test whether ipMcastZoneIndex is the default zone for 1842 this scope, test whether ipMcastZoneIndex is equal to 1843 ipMcastZoneScopeDefaultZoneIndex." 1844 ::= { ipMcastZoneEntry 1 } 1846 ipMcastZoneScopeDefaultZoneIndex OBJECT-TYPE 1847 SYNTAX InetZoneIndex (1..4294967295) 1848 MAX-ACCESS read-only 1849 STATUS current 1850 DESCRIPTION 1851 "The default zone index for this scope. This is the zone 1852 that this device will use if the default (zero) zone is 1853 requested for this scope. 1855 Zero is not a valid value for this object." 1857 ::= { ipMcastZoneEntry 2 } 1859 ipMcastZoneScopeAddressType OBJECT-TYPE 1860 SYNTAX InetAddressType 1861 MAX-ACCESS read-only 1862 STATUS current 1863 DESCRIPTION 1864 "The IP address type for which this scope zone exists." 1865 ::= { ipMcastZoneEntry 3 } 1867 ipMcastZoneScopeAddress OBJECT-TYPE 1868 SYNTAX InetAddress 1869 MAX-ACCESS read-only 1870 STATUS current 1871 DESCRIPTION 1872 "The multicast group address which, when combined with 1873 ipMcastZoneScopeAddressPrefixLength, gives the multicast 1874 address range for this scope. The InetAddressType is given 1875 by ipMcastZoneScopeAddressType. 1877 Scoped IPv4 multicast address ranges are prefixed by 1878 239.0.0.0/8. Scoped IPv6 multicast address ranges are 1879 FF0x::/16, where x is a valid RFC 4291 multicast scope. 1881 An IPv6 address prefixed by FF1x::/16 is a non-permanently- 1882 assigned address. An IPv6 address prefixed by FF3x::/16 is 1883 a unicast-prefix-based multicast addresses. A scope 1884 FF0x::/16 implies an identical scope for these other 1885 prefixes. No separate FF1x::/16 or FF3x::/16 entries exist 1886 in this table. 1888 This address object is only significant up to 1889 ipMcastZoneScopeAddressPrefixLength bits. The remainder of 1890 the address bits are zero." 1891 REFERENCE "RFC 2365, RFC 3306 section 4, RFC 4291 section 2.7" 1892 ::= { ipMcastZoneEntry 4 } 1894 ipMcastZoneScopeAddressPrefixLength OBJECT-TYPE 1895 SYNTAX InetAddressPrefixLength 1896 MAX-ACCESS read-only 1897 STATUS current 1898 DESCRIPTION 1899 "The length in bits of the mask which, when combined 1900 with ipMcastZoneScopeAddress, gives the multicast address 1901 prefix for this scope. 1903 The InetAddressType is given by ipMcastZoneScopeAddressType. 1904 For values 'ipv4' and 'ipv4z', this object must be in the 1905 range 4..32. For values 'ipv6' and 'ipv6z', this object 1906 must be set to 16." 1907 ::= { ipMcastZoneEntry 5 } 1909 -- 1910 -- Conformance information 1911 -- 1913 ipMcastMIBConformance 1914 OBJECT IDENTIFIER ::= { ipMcastMIB 2 } 1915 ipMcastMIBCompliances 1916 OBJECT IDENTIFIER ::= { ipMcastMIBConformance 1 } 1917 ipMcastMIBGroups OBJECT IDENTIFIER ::= { ipMcastMIBConformance 2 } 1919 -- 1920 -- Compliance statements 1921 -- 1923 ipMcastMIBComplianceHost MODULE-COMPLIANCE 1924 STATUS current 1925 DESCRIPTION 1926 "The compliance statement for hosts supporting IPMCAST-MIB. 1928 Support for either InetAddressType ipv4 or ipv6 is 1929 mandatory; support for both InetAddressTypes ipv4 and ipv6 1930 is optional. Support for types ipv4z and ipv6z is 1931 optional. 1933 -- OBJECT ipMcastLocalListenerGroupAddressType 1934 -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), 1935 -- ipv4z(3), ipv6z(4)} 1936 -- DESCRIPTION 1937 -- This compliance requires support for ipv4 or ipv6. 1938 -- 1939 -- OBJECT ipMcastLocalListenerGroupAddress 1940 -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1941 -- DESCRIPTION 1942 -- This compliance requires support for ipv4 or ipv6. 1943 -- 1944 -- OBJECT ipMcastLocalListenerSourceAddressType 1945 -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), 1946 -- ipv4z(3), ipv6z(4)} 1947 -- DESCRIPTION 1948 -- This compliance requires support for ipv4 or ipv6. 1949 -- 1950 -- OBJECT ipMcastLocalListenerSourceAddress 1951 -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) 1952 -- DESCRIPTION 1953 -- This compliance requires support for ipv4 or ipv6." 1955 MODULE -- this module 1956 MANDATORY-GROUPS { ipMcastMIBLocalListenerGroup, 1957 ipMcastMIBBasicGroup } 1959 OBJECT ipMcastEnabled 1960 MIN-ACCESS read-only 1961 DESCRIPTION 1962 "Write access is not required." 1964 OBJECT ipMcastDeviceConfigStorageType 1965 MIN-ACCESS read-only 1966 DESCRIPTION 1967 "Write access is not required." 1969 GROUP ipMcastMIBSsmGroup 1970 DESCRIPTION 1971 "This group is optional." 1973 GROUP ipMcastMIBRouteGroup 1974 DESCRIPTION 1975 "This group is optional." 1977 GROUP ipMcastMIBRouteDiagnosticsGroup 1978 DESCRIPTION 1979 "This group is optional." 1981 GROUP ipMcastMIBBoundaryIfGroup 1982 DESCRIPTION 1983 "This group is optional." 1985 GROUP ipMcastMIBScopeNameGroup 1986 DESCRIPTION 1987 "This group is optional." 1989 ::= { ipMcastMIBCompliances 1 } 1991 ipMcastMIBComplianceRouter MODULE-COMPLIANCE 1992 STATUS current 1993 DESCRIPTION 1994 "The compliance statement for routers supporting 1995 IPMCAST-MIB. 1997 Support for either InetAddressType ipv4 or ipv6 is 1998 mandatory; support for both InetAddressTypes ipv4 and ipv6 1999 is optional. Support for types ipv4z and ipv6z is 2000 optional. 2002 -- OBJECT ipMcastSsmRangeAddressType 2003 -- SYNTAX InetAddressType {ipv4(1), ipv6(2), ipv4z(3), 2004 -- ipv6z(4)} 2005 -- DESCRIPTION 2006 -- This compliance requires support for ipv4 or ipv6. 2007 -- 2008 -- OBJECT ipMcastSsmRangeAddress 2009 -- SYNTAX InetAddress (SIZE (4|8|16|20)) 2010 -- DESCRIPTION 2011 -- This compliance requires support for ipv4 or ipv6. 2012 -- 2013 -- OBJECT ipMcastRouteGroupAddressType 2014 -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), 2015 -- ipv4z(3), ipv6z(4)} 2016 -- DESCRIPTION 2017 -- This compliance requires support for unknown and 2018 -- either ipv4 or ipv6. 2019 -- 2020 -- OBJECT ipMcastRouteGroup 2021 -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) 2022 -- DESCRIPTION 2023 -- This compliance requires support for unknown and 2024 -- either ipv4 or ipv6. 2025 -- 2026 -- OBJECT ipMcastRouteSourceAddressType 2027 -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), 2028 -- ipv4z(3), ipv6z(4)} 2029 -- DESCRIPTION 2030 -- This compliance requires support for unknown and 2031 -- either ipv4 or ipv6. 2032 -- 2033 -- OBJECT ipMcastRouteSource 2034 -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) 2035 -- DESCRIPTION 2036 -- This compliance requires support for unknown and 2037 -- either ipv4 or ipv6. 2038 -- 2039 -- OBJECT ipMcastRouteNextHopGroupAddressType 2040 -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), 2041 -- ipv4z(3), ipv6z(4)} 2042 -- DESCRIPTION 2043 -- This compliance requires support for unknown and 2044 -- either ipv4 or ipv6. 2045 -- 2046 -- OBJECT ipMcastRouteNextHopGroup 2047 -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) 2048 -- DESCRIPTION 2049 -- This compliance requires support for unknown and 2050 -- either ipv4 or ipv6. 2051 -- 2052 -- OBJECT ipMcastRouteNextHopSourceAddressType 2053 -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), 2054 -- ipv4z(3), ipv6z(4)} 2055 -- DESCRIPTION 2056 -- This compliance requires support for unknown and 2057 -- either ipv4 or ipv6. 2058 -- 2059 -- OBJECT ipMcastRouteNextHopSource 2060 -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) 2061 -- DESCRIPTION 2062 -- This compliance requires support for unknown and 2063 -- either ipv4 or ipv6. 2064 -- 2065 -- OBJECT ipMcastRouteNextHopAddressType 2066 -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), 2067 -- ipv4z(3), ipv6z(4)} 2068 -- DESCRIPTION 2069 -- This compliance requires support for unknown and 2070 -- either ipv4 or ipv6. 2071 -- 2072 -- OBJECT ipMcastRouteNextHopAddress 2073 -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) 2074 -- DESCRIPTION 2075 -- This compliance requires support for unknown and 2076 -- either ipv4 or ipv6." 2078 MODULE -- this module 2079 MANDATORY-GROUPS { ipMcastMIBRouteProtoGroup, 2080 ipMcastMIBBasicGroup, 2081 ipMcastMIBSsmGroup, 2082 ipMcastMIBRouteGroup } 2084 OBJECT ipMcastEnabled 2085 MIN-ACCESS read-only 2086 DESCRIPTION 2087 "Write access is not required." 2089 OBJECT ipMcastDeviceConfigStorageType 2090 MIN-ACCESS read-only 2091 DESCRIPTION 2092 "Write access is not required." 2094 OBJECT ipMcastInterfaceTtl 2095 MIN-ACCESS read-only 2096 DESCRIPTION 2097 "Write access is not required." 2099 OBJECT ipMcastInterfaceRateLimit 2100 MIN-ACCESS read-only 2101 DESCRIPTION 2102 "Write access is not required." 2104 OBJECT ipMcastInterfaceStorageType 2105 MIN-ACCESS read-only 2106 DESCRIPTION 2107 "Write access is not required." 2109 OBJECT ipMcastRouteUpstreamNeighborType 2110 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2), 2111 ipv4z(3), ipv6z(4) } 2112 MIN-ACCESS read-only 2113 DESCRIPTION 2114 "This compliance requires support for unknown and either ipv4 2115 or ipv6." 2117 OBJECT ipMcastRouteUpstreamNeighbor 2118 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 2119 MIN-ACCESS read-only 2120 DESCRIPTION 2121 "This compliance requires support for unknown and either ipv4 2122 or ipv6." 2124 OBJECT ipMcastRouteRtAddressType 2125 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2), 2126 ipv4z(3), ipv6z(4) } 2127 MIN-ACCESS read-only 2128 DESCRIPTION 2129 "This compliance requires support for unknown and either ipv4 2130 or ipv6." 2132 OBJECT ipMcastRouteRtAddress 2133 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 2134 MIN-ACCESS read-only 2135 DESCRIPTION 2136 "This compliance requires support for unknown and either ipv4 2137 or ipv6." 2139 OBJECT ipMcastSsmRangeRowStatus 2140 MIN-ACCESS read-only 2141 DESCRIPTION 2142 "Write access is not required." 2144 OBJECT ipMcastSsmRangeStorageType 2145 MIN-ACCESS read-only 2146 DESCRIPTION 2147 "Write access is not required." 2149 GROUP ipMcastMIBRouteDiagnosticsGroup 2150 DESCRIPTION 2151 "This group is not mandatory, but SHOULD be supported where 2152 hardware permits." 2154 GROUP ipMcastMIBPktsOutGroup 2155 DESCRIPTION 2156 "This group is optional." 2158 GROUP ipMcastMIBHopCountGroup 2159 DESCRIPTION 2160 "This group is optional." 2162 GROUP ipMcastMIBRouteOctetsGroup 2163 DESCRIPTION 2164 "This group is optional." 2166 GROUP ipMcastMIBRouteBpsGroup 2167 DESCRIPTION 2168 "This group is optional." 2170 GROUP ipMcastMIBLocalListenerGroup 2171 DESCRIPTION 2172 "This group is optional." 2174 GROUP ipMcastMIBBoundaryIfGroup 2175 DESCRIPTION 2176 "This group is optional." 2178 GROUP ipMcastMIBScopeNameGroup 2179 DESCRIPTION 2180 "This group is optional." 2182 ::= { ipMcastMIBCompliances 2 } 2184 ipMcastMIBComplianceBorderRouter MODULE-COMPLIANCE 2185 STATUS current 2186 DESCRIPTION 2187 "The compliance statement for routers on scope 2188 boundaries supporting IPMCAST-MIB. 2190 Support for either InetAddressType ipv4z or ipv6z is 2191 mandatory; support for both InetAddressTypes ipv4z and 2192 ipv6z is optional. 2194 -- OBJECT ipMcastSsmRangeAddressType 2195 -- SYNTAX InetAddressType {ipv4(1), ipv6(2), ipv4z(3), 2196 -- ipv6z(4)} 2197 -- DESCRIPTION 2198 -- This compliance requires support for ipv4 or ipv6. 2199 -- 2200 -- OBJECT ipMcastSsmRangeAddress 2201 -- SYNTAX InetAddress (SIZE (4|8|16|20)) 2202 -- DESCRIPTION 2203 -- This compliance requires support for ipv4 or ipv6. 2204 -- 2205 -- OBJECT ipMcastRouteGroupAddressType 2206 -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), 2207 -- ipv4z(3), ipv6z(4)} 2208 -- DESCRIPTION 2209 -- This compliance requires support for unknown and 2210 -- either ipv4 or ipv6. 2211 -- 2212 -- OBJECT ipMcastRouteGroup 2213 -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) 2214 -- DESCRIPTION 2215 -- This compliance requires support for unknown and 2216 -- either ipv4 and ipv4z or ipv6 and ipv6z. 2217 -- 2218 -- OBJECT ipMcastRouteSourceAddressType 2219 -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), 2220 -- ipv4z(3), ipv6z(4)} 2221 -- DESCRIPTION 2222 -- This compliance requires support for unknown and 2223 -- either ipv4 and ipv4z or ipv6 and ipv6z. 2224 -- 2225 -- OBJECT ipMcastRouteSource 2226 -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) 2227 -- DESCRIPTION 2228 -- This compliance requires support for unknown and 2229 -- either ipv4 and ipv4z or ipv6 and ipv6z. 2230 -- 2231 -- OBJECT ipMcastRouteNextHopGroupAddressType 2232 -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), 2233 -- ipv4z(3), ipv6z(4)} 2234 -- DESCRIPTION 2235 -- This compliance requires support for unknown and 2236 -- either ipv4 and ipv4z or ipv6 and ipv6z. 2237 -- 2238 -- OBJECT ipMcastRouteNextHopGroup 2239 -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) 2240 -- DESCRIPTION 2241 -- This compliance requires support for unknown and 2242 -- either ipv4 and ipv4z or ipv6 and ipv6z. 2244 -- 2245 -- OBJECT ipMcastRouteNextHopSourceAddressType 2246 -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), 2247 -- ipv4z(3), ipv6z(4)} 2248 -- DESCRIPTION 2249 -- This compliance requires support for unknown and 2250 -- either ipv4 and ipv4z or ipv6 and ipv6z. 2251 -- 2252 -- OBJECT ipMcastRouteNextHopSource 2253 -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) 2254 -- DESCRIPTION 2255 -- This compliance requires support for unknown and 2256 -- either ipv4 and ipv4z or ipv6 and ipv6z. 2257 -- 2258 -- OBJECT ipMcastRouteNextHopAddressType 2259 -- SYNTAX InetAddressType {unknown(0), ipv4(1), ipv6(2), 2260 -- ipv4z(3), ipv6z(4)} 2261 -- DESCRIPTION 2262 -- This compliance requires support for unknown and 2263 -- either ipv4 and ipv4z or ipv6 and ipv6z. 2264 -- 2265 -- OBJECT ipMcastRouteNextHopAddress 2266 -- SYNTAX InetAddress (SIZE (0|4|8|16|20)) 2267 -- DESCRIPTION 2268 -- This compliance requires support for unknown and 2269 -- either ipv4 and ipv4z or ipv6 and ipv6z. 2270 -- 2271 -- OBJECT ipMcastBoundaryAddressType 2272 -- SYNTAX InetAddressType {ipv4(1), ipv6(2)} 2273 -- DESCRIPTION 2274 -- This compliance requires support for ipv4 or ipv6. 2275 -- 2276 -- OBJECT ipMcastBoundaryAddress 2277 -- SYNTAX InetAddress (SIZE (4|16) 2278 -- DESCRIPTION 2279 -- This compliance requires support for ipv4 or ipv6. 2280 -- 2281 -- OBJECT ipMcastScopeNameAddressType 2282 -- SYNTAX InetAddressType {ipv4(1), ipv6(2)} 2283 -- DESCRIPTION 2284 -- This compliance requires support for ipv4 or ipv6. 2285 -- 2286 -- OBJECT ipMcastScopeNameAddress 2287 -- SYNTAX InetAddress (SIZE (4|16) 2288 -- DESCRIPTION 2289 -- This compliance requires support for ipv4 or ipv6." 2291 MODULE -- this module 2292 MANDATORY-GROUPS { ipMcastMIBRouteProtoGroup, 2293 ipMcastMIBBasicGroup, 2294 ipMcastMIBSsmGroup, 2295 ipMcastMIBRouteGroup, 2296 ipMcastMIBBoundaryIfGroup, 2297 ipMcastMIBScopeNameGroup } 2299 OBJECT ipMcastEnabled 2300 MIN-ACCESS read-only 2301 DESCRIPTION 2302 "Write access is not required." 2304 OBJECT ipMcastDeviceConfigStorageType 2305 MIN-ACCESS read-only 2306 DESCRIPTION 2307 "Write access is not required." 2309 OBJECT ipMcastInterfaceTtl 2310 MIN-ACCESS read-only 2311 DESCRIPTION 2312 "Write access is not required." 2314 OBJECT ipMcastInterfaceRateLimit 2315 MIN-ACCESS read-only 2316 DESCRIPTION 2317 "Write access is not required." 2319 OBJECT ipMcastInterfaceStorageType 2320 MIN-ACCESS read-only 2321 DESCRIPTION 2322 "Write access is not required." 2324 OBJECT ipMcastRouteUpstreamNeighborType 2325 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2), 2326 ipv4z(3), ipv6z(4) } 2327 MIN-ACCESS read-only 2328 DESCRIPTION 2329 "This compliance requires support for unknown and either ipv4 2330 and ipv4z, or ipv6 and ipv6z." 2332 OBJECT ipMcastRouteUpstreamNeighbor 2333 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 2334 MIN-ACCESS read-only 2335 DESCRIPTION 2336 "This compliance requires support for unknown and either ipv4 2337 and ipv4z, or ipv6 and ipv6z." 2339 OBJECT ipMcastRouteRtAddressType 2340 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2), 2341 ipv4z(3), ipv6z(4) } 2342 MIN-ACCESS read-only 2343 DESCRIPTION 2344 "This compliance requires support for unknown and either ipv4 2345 and ipv4z, or ipv6 and ipv6z." 2347 OBJECT ipMcastRouteRtAddress 2348 SYNTAX InetAddress (SIZE (0|4|8|16|20)) 2349 MIN-ACCESS read-only 2350 DESCRIPTION 2351 "This compliance requires support for unknown and either ipv4 2352 and ipv4z, or ipv6 and ipv6z." 2354 OBJECT ipMcastSsmRangeRowStatus 2355 MIN-ACCESS read-only 2356 DESCRIPTION 2357 "Write access is not required." 2359 OBJECT ipMcastSsmRangeStorageType 2360 MIN-ACCESS read-only 2361 DESCRIPTION 2362 "Write access is not required." 2364 GROUP ipMcastMIBRouteDiagnosticsGroup 2365 DESCRIPTION 2366 "This group is not mandatory, but SHOULD be supported where 2367 hardware permits." 2369 GROUP ipMcastMIBPktsOutGroup 2370 DESCRIPTION 2371 "This group is optional." 2373 GROUP ipMcastMIBHopCountGroup 2374 DESCRIPTION 2375 "This group is optional." 2377 GROUP ipMcastMIBRouteOctetsGroup 2378 DESCRIPTION 2379 "This group is optional." 2381 GROUP ipMcastMIBRouteBpsGroup 2382 DESCRIPTION 2383 "This group is optional." 2385 GROUP ipMcastMIBLocalListenerGroup 2386 DESCRIPTION 2387 "This group is optional." 2389 OBJECT ipMcastZoneScopeAddressType 2390 SYNTAX InetAddressType { ipv4(1), ipv6(2) } 2391 MIN-ACCESS read-only 2392 DESCRIPTION 2393 "This compliance requires support for ipv4 or ipv6." 2395 OBJECT ipMcastZoneScopeAddress 2396 SYNTAX InetAddress (SIZE (4|16)) 2397 MIN-ACCESS read-only 2398 DESCRIPTION 2399 "This compliance requires support for ipv4 or ipv6." 2401 ::= { ipMcastMIBCompliances 3 } 2403 -- 2404 -- Units of conformance 2405 -- 2406 ipMcastMIBBasicGroup OBJECT-GROUP 2407 OBJECTS { ipMcastEnabled, 2408 ipMcastRouteEntryCount, 2409 ipMcastDeviceConfigStorageType 2410 } 2411 STATUS current 2412 DESCRIPTION 2413 "A collection of objects to support basic management of IP 2414 Multicast protocols." 2415 ::= { ipMcastMIBGroups 1 } 2417 ipMcastMIBSsmGroup OBJECT-GROUP 2418 OBJECTS { ipMcastSsmRangeRowStatus, 2419 ipMcastSsmRangeStorageType } 2420 STATUS current 2421 DESCRIPTION 2422 "A collection of objects to support management of Source- 2423 Specific Multicast routing." 2424 ::= { ipMcastMIBGroups 2 } 2426 ipMcastMIBRouteGroup OBJECT-GROUP 2427 OBJECTS { ipMcastInterfaceTtl, 2428 ipMcastInterfaceRateLimit, 2429 ipMcastInterfaceStorageType, 2430 ipMcastRouteUpstreamNeighborType, 2431 ipMcastRouteUpstreamNeighbor, 2432 ipMcastRouteInIfIndex, 2433 ipMcastRouteTimeStamp, 2434 ipMcastRouteExpiryTime, 2435 ipMcastRouteNextHopState, 2436 ipMcastRouteNextHopTimeStamp, 2437 ipMcastRouteNextHopExpiryTime 2438 } 2439 STATUS current 2440 DESCRIPTION 2441 "A collection of objects to support basic management of IP 2442 Multicast routing." 2443 ::= { ipMcastMIBGroups 3 } 2445 ipMcastMIBRouteDiagnosticsGroup OBJECT-GROUP 2446 OBJECTS { ipMcastRoutePkts, 2447 ipMcastRouteTtlDropPackets, 2448 ipMcastRouteDifferentInIfPackets 2449 } 2450 STATUS current 2451 DESCRIPTION 2452 "A collection of routing diagnostic packet counters." 2453 ::= { ipMcastMIBGroups 4 } 2455 ipMcastMIBPktsOutGroup OBJECT-GROUP 2456 OBJECTS { ipMcastRouteNextHopTimeStamp, 2457 ipMcastRouteNextHopPkts } 2458 STATUS current 2459 DESCRIPTION 2460 "A collection of objects to support management of packet 2461 counters for each outgoing interface entry of a route." 2462 ::= { ipMcastMIBGroups 5 } 2464 ipMcastMIBHopCountGroup OBJECT-GROUP 2465 OBJECTS { ipMcastRouteNextHopClosestMemberHops } 2466 STATUS current 2467 DESCRIPTION 2468 "A collection of objects to support management of the use of 2469 hop counts in IP Multicast routing." 2470 ::= { ipMcastMIBGroups 6 } 2472 ipMcastMIBRouteOctetsGroup OBJECT-GROUP 2473 OBJECTS { ipMcastRouteTimeStamp, 2474 ipMcastRouteOctets, 2475 ipMcastRouteTtlDropOctets, 2476 ipMcastRouteDifferentInIfOctets, 2477 ipMcastRouteNextHopTimeStamp, 2478 ipMcastRouteNextHopOctets } 2479 STATUS current 2480 DESCRIPTION 2481 "A collection of objects to support management of octet 2482 counters for each forwarding entry." 2483 ::= { ipMcastMIBGroups 7 } 2485 ipMcastMIBRouteBpsGroup OBJECT-GROUP 2486 OBJECTS { ipMcastRouteBps } 2487 STATUS current 2488 DESCRIPTION 2489 "A collection of objects to support sampling of data rate 2490 in bits per second for each forwarding entry." 2491 ::= { ipMcastMIBGroups 8 } 2493 ipMcastMIBRouteProtoGroup OBJECT-GROUP 2494 OBJECTS { ipMcastRouteProtocol, ipMcastRouteRtProtocol, 2495 ipMcastRouteRtAddressType, ipMcastRouteRtAddress, 2496 ipMcastRouteRtPrefixLength, ipMcastRouteRtType, 2497 ipMcastRouteNextHopProtocol } 2498 STATUS current 2499 DESCRIPTION 2500 "A collection of objects providing information on the 2501 relationship between multicast routing information and the 2502 IP Forwarding Table." 2503 ::= { ipMcastMIBGroups 9 } 2505 ipMcastMIBLocalListenerGroup OBJECT-GROUP 2506 OBJECTS { ipMcastLocalListenerRunIndex } 2507 STATUS current 2508 DESCRIPTION 2509 "A collection of objects to support management of local 2510 listeners on hosts or routers." 2511 ::= { ipMcastMIBGroups 10 } 2513 ipMcastMIBBoundaryIfGroup OBJECT-GROUP 2514 OBJECTS { ipMcastBoundaryTimeStamp, 2515 ipMcastBoundaryDroppedMcastOctets, 2516 ipMcastBoundaryDroppedMcastPkts, 2517 ipMcastBoundaryStatus, 2518 ipMcastBoundaryStorageType, 2519 ipMcastZoneScopeDefaultZoneIndex, 2520 ipMcastZoneScopeAddressType, 2521 ipMcastZoneScopeAddress, 2522 ipMcastZoneScopeAddressPrefixLength 2523 } 2524 STATUS current 2525 DESCRIPTION 2526 "A collection of objects to support management of multicast 2527 scope zone boundaries." 2528 ::= { ipMcastMIBGroups 11 } 2530 ipMcastMIBScopeNameGroup OBJECT-GROUP 2531 OBJECTS { ipMcastScopeNameString, ipMcastScopeNameDefault, 2532 ipMcastScopeNameStatus, ipMcastScopeNameStorageType } 2534 STATUS current 2535 DESCRIPTION 2536 "A collection of objects to support management of multicast 2537 address scope names." 2538 ::= { ipMcastMIBGroups 12 } 2540 END 2542 7. Security Considerations 2544 7.1 SNMPv3 2546 SNMP versions prior to SNMPv3 did not include adequate security. 2547 Even if the network itself is secured (for example by using IPSec), 2548 there is still no control over whom on the secure network is allowed 2549 to access (read/change/create/delete) the objects in this MIB module. 2551 It is RECOMMENDED that implementers consider the security features as 2552 provided by the SNMPv3 framework (see [RFC3410], section 8), 2553 including full support for the SNMPv3 cryptographic mechanisms (for 2554 authentication and privacy). 2556 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2557 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2558 enable cryptographic security. It is then a customer/operator 2559 responsibility to ensure that the SNMP entity giving access to an 2560 instance of this MIB module is properly configured to give access to 2561 the objects only to those principals (users) that have legitimate 2562 rights to access (read/change/create/delete) them. 2564 7.2 Writeable objects 2566 There are a number of management objects defined in this MIB module 2567 with a MAX-ACCESS clause of read-write and/or read-create. This 2568 section discusses and lists these elements. 2570 Such objects may be considered sensitive or vulnerable in some 2571 network environments. The support for SET operations in a non-secure 2572 environment without proper protection can have a negative effect on 2573 network operations. 2575 In this MIB module, possible effects that can be induced by SET 2576 operations on writeable objects include: 2578 o Modifications to multicast routing behavior that prevent or 2579 disrupt services provided by the network, including (but not 2580 limited to) multicast data traffic delivery. 2582 o Modifications to multicast routing behavior that allow 2583 interception or subversion of information that is carried by the 2584 network. For example, attacks can be envisaged that would pass 2585 nominated multicast data streams through a nominated location, 2586 without the sources or listeners becoming aware of this 2587 subversion. 2589 The following are the read-write and read-create objects defined in 2590 this MIB module. 2592 ipMcastEnabled 2593 ipMcastDeviceConfigStorageType 2594 ipMcastInterfaceTtl 2595 ipMcastInterfaceRateLimit 2596 ipMcastInterfaceStorageType 2597 ipMcastSsmRangeRowStatus 2598 ipMcastSsmRangeStorageType 2599 ipMcastBoundaryStatus 2600 ipMcastBoundaryStorageType 2601 ipMcastScopeNameTable 2602 ipMcastScopeNameString 2603 ipMcastScopeNameDefault 2604 ipMcastScopeNameStatus 2605 ipMcastScopeNameStorageType 2607 7.3 Readable objects 2609 As well as the writeable objects discussed above, there are a number 2610 of readable objects (i.e., objects with a MAX-ACCESS other than not- 2611 accessible) that may be considered sensitive or vulnerable in some 2612 network environments. It is thus important to control even GET 2613 and/or NOTIFY access to these objects and possibly to even encrypt 2614 the values of these objects when sending them over the network via 2615 SNMP. 2617 In this MIB module, possible effects that can be induced by GET 2618 and/or NOTIFY operations include: 2620 o Determination of the topology, disposition, and composition of the 2621 network. This information may be commercially sensitive, and may 2622 also be used in preparation for attacks, including any of the 2623 attacks described above. 2625 o Determinion of whether multicast data is flowing in the network, 2626 or has flowed recently, as well as the locations of senders and 2627 recipients. An attacker can apply 'traffic analysis' to this 2628 data. In some cases, the information revealed by traffic analyses 2629 can be as damaging as full knowledge of the data being 2630 transported. 2632 8. IANA Considerations 2634 The MIB module in this document uses the following IANA-assigned 2635 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 2637 Descriptor OBJECT IDENTIFIER value 2638 ----------------------------------------- 2639 ipMcastMIB { mib-2 XXX } 2641 Editor's Note (to be removed prior to publication): the IANA is 2642 requested to assign a value for "XXX" under the 'mib-2' subtree and 2643 to record the assignment in the SMI Numbers registry. When the 2644 assignment has been made, the RFC Editor is asked to replace "XXX" 2645 (here and in the MIB module) with the assigned value and to remove 2646 this note. 2648 9. Acknowledgements 2650 This MIB module is based on the original work in [RFC2932] by K. 2651 McCloghrie, D. Farinacci and D. Thaler. 2653 Suggested IPv6 multicast MIBs by R. Sivaramu and R. Raghunarayan have 2654 been used for comparison while editing this MIB module. 2656 The authors are also grateful to Bill Fenner for fine ideas, and to 2657 Bharat Joshi for input and several corrections. 2659 10. References 2661 10.1 Normative References 2663 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2664 Requirement Levels", BCP 14, RFC 2119, March 1997. 2666 [RFC2365] Meyer, D., "Administratively Scoped IP Multicast", BCP 23, 2667 RFC 2365, July 1998. 2669 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2670 Schoenwaelder, Ed., "Structure of Management Information 2671 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2673 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2674 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 2675 STD 58, RFC 2579, April 1999. 2677 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 2678 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2679 April 1999. 2681 [RFC2856] Bierman, A., McCloghrie, K., and R. Presuhn, "Textual 2682 Conventions for Additional High Capacity Data Types", 2683 RFC 2856, June 2000. 2685 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 2686 MIB", RFC 2863, June 2000. 2688 [RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 2689 Multicast Addresses", RFC 3306, August 2002. 2691 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 2692 Architecture for Describing Simple Network Management 2693 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 2694 December 2002. 2696 [RFC3569] Bhattacharyya, S., "An Overview of Source-Specific 2697 Multicast (SSM)", RFC 3569, July 2003. 2699 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2700 Schoenwaelder, "Textual Conventions for Internet Network 2701 Addresses", RFC 4001, February 2005. 2703 [RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and 2704 B. Zill, "IPv6 Scoped Address Architecture", RFC 4007, 2705 March 2005. 2707 [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing 2708 Architecture", RFC 4291, February 2006. 2710 [I-D.mcwalter-langtag-mib] 2711 McWalter, D., "Language Tag MIB", 2712 draft-mcwalter-langtag-mib-03 (work in progress), I-D 2713 Status active, March 2007. 2715 10.2 Informative References 2717 [RFC2287] Krupczak, C. and J. Saperia, "Definitions of System-Level 2718 Managed Objects for Applications", RFC 2287, 2719 February 1998. 2721 [RFC2932] McCloghrie, K., Farinacci, D., and D. Thaler, "IPv4 2722 Multicast Routing MIB", RFC 2932, October 2000. 2724 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2725 "Introduction and Applicability Statements for Internet- 2726 Standard Management Framework", RFC 3410, December 2002. 2728 [RFC4293] Routhier, S., "Management Information Base for the 2729 Internet Protocol (IP)", RFC 4293, April 2006. 2731 [RFC4601] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, 2732 "Protocol Independent Multicast - Sparse Mode (PIM-SM): 2733 Protocol Specification (Revised)", RFC 4601, August 2006. 2735 [RFC4646] Phillips, A. and M. Davis, "Tags for Identifying 2736 Languages", BCP 47, RFC 4646, September 2006. 2738 [I-D.ietf-pim-bidir] 2739 Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano, 2740 "Bi-directional Protocol Independent Multicast (BIDIR- 2741 PIM)", draft-ietf-pim-bidir-09 (work in progress), 2742 March 2007. 2744 Authors' Addresses 2746 David McWalter 2747 Data Connection Ltd 2748 100 Church Street 2749 Enfield EN2 6BQ 2750 UK 2752 Email: dmcw@dataconnection.com 2754 Dave Thaler 2755 Microsoft Corporation 2756 One Microsoft Way 2757 Redmond WA 98052-6399 2758 USA 2760 Email: dthaler@windows.microsoft.com 2761 Andrew Kessler 2762 Cisco Systems 2763 425 E. Tasman Drive 2764 San Jose CA 95134 2765 USA 2767 Email: kessler@cisco.com 2769 Intellectual Property Statement 2771 The IETF takes no position regarding the validity or scope of any 2772 Intellectual Property Rights or other rights that might be claimed to 2773 pertain to the implementation or use of the technology described in 2774 this document or the extent to which any license under such rights 2775 might or might not be available; nor does it represent that it has 2776 made any independent effort to identify any such rights. Information 2777 on the procedures with respect to rights in RFC documents can be 2778 found in BCP 78 and BCP 79. 2780 Copies of IPR disclosures made to the IETF Secretariat and any 2781 assurances of licenses to be made available, or the result of an 2782 attempt made to obtain a general license or permission for the use of 2783 such proprietary rights by implementers or users of this 2784 specification can be obtained from the IETF on-line IPR repository at 2785 http://www.ietf.org/ipr. 2787 The IETF invites any interested party to bring to its attention any 2788 copyrights, patents or patent applications, or other proprietary 2789 rights that may cover technology that may be required to implement 2790 this standard. Please address the information to the IETF at 2791 ietf-ipr@ietf.org. 2793 Disclaimer of Validity 2795 This document and the information contained herein are provided on an 2796 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2797 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 2798 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 2799 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 2800 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2801 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2803 Copyright Statement 2805 Copyright (C) The IETF Trust (2007). This document is subject to the 2806 rights, licenses and restrictions contained in BCP 78, and except as 2807 set forth therein, the authors retain all their rights. 2809 Acknowledgment 2811 Funding for the RFC Editor function is currently provided by the 2812 Internet Society.