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