idnits 2.17.1 draft-ietf-bess-mvpn-mib-08.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (July 30, 2018) is 2097 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: 'RFC2851' is mentioned on line 223, but not defined ** Obsolete undefined reference: RFC 2851 (Obsoleted by RFC 3291) == Unused Reference: 'RFC4659' is defined on line 2599, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'RTPROTO' Summary: 1 error (**), 0 flaws (~~), 4 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group H. Tsunoda 3 Internet-Draft Tohoku Institute of Technology 4 Intended status: Standards Track July 30, 2018 5 Expires: January 31, 2019 7 BGP/MPLS Layer 3 VPN Multicast Management Information Base 8 draft-ietf-bess-mvpn-mib-08 10 Abstract 12 This memo defines a portion of the Management Information Base (MIB) 13 for use with network management protocols in the Internet community. 14 In particular, it describes managed objects to configure and/or 15 monitor Multicast communication over IP Virtual Private Networks 16 (VPNs) supported by MultiProtocol Label Switching/Border Gateway 17 Protcol (MPLS/BGP) on a Provider Edge router. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on January 31, 2019. 36 Copyright Notice 38 Copyright (c) 2018 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2 55 2. The Internet-Standard Management Framework . . . . . . . . . 3 56 3. MCAST-VPN-MIB . . . . . . . . . . . . . . . . . . . . . . . . 3 57 3.1. Summary of MIB Module . . . . . . . . . . . . . . . . . . 4 58 3.2. MIB Module Definitions . . . . . . . . . . . . . . . . . 5 59 4. Security Considerations . . . . . . . . . . . . . . . . . . . 50 60 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 53 61 6. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 53 62 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 53 63 7.1. Normative References . . . . . . . . . . . . . . . . . . 53 64 7.2. Informative References . . . . . . . . . . . . . . . . . 56 65 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 56 67 1. Introduction 69 [RFC6513], [RFC6514], and [RFC6625] specify procedures for supporting 70 multicast in Border Gateway Protocol/MultiProtocol Label Switching 71 (BGP/MPLS) Layer 3 (IP) Virtual Private Networks (VPNs). Throughout 72 this document, we will use the term "Multicast VPN" (MVPN) [RFC6513] 73 to refer to a BGP/MPLS IP VPN that supports multicast. 75 Provider Edge routers (PEs) attaching to a particular MVPN exchange 76 customer multicast (C-multicast) routing information with neighboring 77 PEs. In [RFC6513], two basic methods for exchanging C-multicast 78 routing information are defined (1) Protocol Independent Multicast 79 (PIM) [RFC7761] and (2) BGP. 81 In the rest of this document we will use the term "PIM-MVPN" to refer 82 to the case where PIM is used for exchanging C-multicast routing 83 information, and "BGP-MVPN" to refer to the case where BGP is used 84 for exchanging C-multicast routing information. 86 This document describes managed objects to configure and/or monitor 87 MVPNs. Most of the managed objects are common to both PIM-MVPN and 88 BGP-MVPN, and some managed objects are BGP-MVPN specific. 90 1.1. Terminology 92 This document adopts the definitions, acronyms and mechanisms 93 described in [RFC4364], [RFC6513], and [RFC6514]. Familiarity with 94 Multicast, MPLS, Layer 3 (L3) VPN, MVPN concepts and/or mechanisms is 95 assumed. Some terms specifically related to this document are 96 explained below. 98 An MVPN can be realized by using various kinds of transport 99 mechanisms for forwarding a packet to all or a subset of PEs across 100 service provider networks. Such transport mechanisms are referred to 101 as provider tunnels (P-tunnels). 103 A "Provider Multicast Service Interface" (PMSI) [RFC6513] is a 104 conceptual interface instantiated by a P-tunnel. A PE uses a PMSI to 105 send customer multicast traffic to all or some PEs in the same VPN. 107 There are two kinds of PMSI: "Inclusive PMSI" (I-PMSI) and "Selective 108 PMSI" (S-PMSI) [RFC6513]. An I-PMSI enables a PE attached to a 109 particular MVPN to transmit a message to all PEs in the same MVPN. 110 An S-PMSI enables a PE to transmit a message to a selected set of PEs 111 in the same MVPN. 113 As described in [RFC4382], each PE maintains one default forwarding 114 table and zero or more "Virtual Routing and Forwarding tables" 115 (VRFs). Throughout this document, we will use the term "multicast 116 VRF" (MVRF) to refer to a VRF that contains multicast routing 117 information. 119 The key words "MUST", "SHOULD", "RECOMMENDED", and "MAY" in this 120 document are to be interpreted as described in [RFC2119]. 122 2. The Internet-Standard Management Framework 124 For a detailed overview of the documents that describe the current 125 Internet-Standard Management Framework, please refer to section 7 of 126 RFC 3410 [RFC3410]. 128 Managed objects are accessed via a virtual information store, termed 129 the Management Information Base or MIB. MIB objects are generally 130 accessed through the Simple Network Management Protocol (SNMP). 131 Objects in the MIB are defined using the mechanisms defined in the 132 Structure of Management Information (SMI). This memo specifies a MIB 133 module that is compliant to the SMIv2, which is described in STD 58, 134 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 135 [RFC2580]. 137 3. MCAST-VPN-MIB 139 This document defines MCAST-VPN-MIB, a MIB module for monitoring and/ 140 or configuring MVPNs on PEs. This MIB module will be used in 141 conjunction with MPLS-L3VPN-STD-MIB [RFC4382] and IPMCAST-MIB 142 [RFC5132]. 144 3.1. Summary of MIB Module 146 MCAST-VPN-MIB provides the following functionalities. 148 o Monitoring attributes of MVPNs on a PE 150 o Configuring timers and thresholds related to an MVPN on a PE 152 o Notifying creation, deletion, and modification of MVRFs on a PE 154 o Monitoring PMSI attributes 156 o Monitoring statistics of advertisements exchanged by a PE 158 o Monitoring routing information for multicast destinations 160 o Monitoring next-hops for each multicast destination 162 To provide these functionalities, MCAST-VPN-MIB defines following 163 tables. 165 o mvpnGenericTable 167 This table contains generic information about MVPNs on a PE. Each 168 entry in this table represents an instance of an MVPN on a PE and 169 contains generic information related to the MVPN. For each entry 170 in this table there MUST be a corresponding VRF in MPLS-L3VPN-STD- 171 MIB [RFC4382]. 173 o mvpnBgpTable 175 This table contains information specific to BGP-MVPNs. Each BGP- 176 MVPN on a PE will have an entry in this table. 178 o mvpnPmsiTable 180 This table contains managed objects representing attribute 181 information that is common to I-PMSIs and S-PMSIs on a PE. 183 o mvpnSpmsiTable 185 This table contains managed objects representing attribute 186 information specific to S-PMSIs. An S-PMSI represented in this 187 table will have a corresponding entry in mvpnPmsiTable. 189 o mvpnAdvtStatsTable 190 This table contains statistics pertaining to I-PMSI and S-PMSI 191 advertisements sent/received. 193 o mvpnMrouteTable 195 This table contains multicast routing information in MVRFs on a 196 PE. 198 o mvpnMrouteNextHopTable 200 This table contains information on the next-hops for routing IP 201 multicast datagrams in MVPNs on a PE. 203 3.2. MIB Module Definitions 205 MCAST-VPN-MIB DEFINITIONS ::= BEGIN 207 IMPORTS 208 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 209 Counter32, Counter64, Gauge32, Unsigned32, TimeTicks, 210 mib-2 211 FROM SNMPv2-SMI -- [RFC2578] 213 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 214 FROM SNMPv2-CONF -- [RFC2580] 216 RowPointer, TimeStamp, DateAndTime 217 FROM SNMPv2-TC -- [RFC2579] 219 InterfaceIndex, InterfaceIndexOrZero 220 FROM IF-MIB -- [RFC2863] 222 InetAddress, InetAddressType, InetAddressPrefixLength 223 FROM INET-ADDRESS-MIB -- [RFC2851] 225 mplsL3VpnVrfName, MplsL3VpnRouteDistinguisher 226 FROM MPLS-L3VPN-STD-MIB -- [RFC4382] 228 IANAipRouteProtocol, IANAipMRouteProtocol 229 FROM IANA-RTPROTO-MIB -- [RTPROTO] 231 L2L3VpnMcastProviderTunnelType 232 FROM L2L3-VPN-MCAST-TC-MIB; 234 mvpnMIB MODULE-IDENTITY 235 LAST-UPDATED "201807301200Z" -- 30th July 2018 12:00:00 GMT 236 ORGANIZATION "IETF BESS Working Group." 237 CONTACT-INFO 238 " Hiroshi Tsunoda 239 Tohoku Institute of Technology 240 35-1, Yagiyama Kasumi-cho 241 Taihaku-ku, Sendai, 982-8577 242 Japan 243 Email: tsuno@m.ieice.org 245 Comments and discussion to bess@ietf.org" 247 DESCRIPTION 248 "This MIB module contains managed object definitions to 249 configure and/or monitor Multicast communication over IP 250 Virtual Private Networks (VPNs) supported by MultiProtocol 251 Label Switching/Border Gateway Protcol (MPLS/BGP) on a 252 Provider Edge router (PE). 253 Copyright (C) The Internet Society (2018). 254 " 256 -- Revision history. 258 REVISION "201807301200Z" -- 30th July, 2018 259 DESCRIPTION 260 "Initial version, published as RFC XXXX." 262 -- RFC Ed. replace XXXX with the actual RFC number and 263 -- remove this note 265 ::= { mib-2 YYYY } 267 -- IANA Reg.: Please assign a value for "YYYY" under the 268 -- 'mib-2' subtree and record the assignment in the SMI 269 -- Numbers registry. 271 -- RFC Ed.: When the above assignment has been made, please 272 -- remove the above note 273 -- replace "YYYY" here with the assigned value and 274 -- remove this note. 276 -- Top level components of this MIB module. 277 mvpnNotifications OBJECT IDENTIFIER ::= { mvpnMIB 0 } 279 -- scalars, tables 280 mvpnObjects OBJECT IDENTIFIER ::= { mvpnMIB 1 } 282 -- conformance information 283 mvpnConformance OBJECT IDENTIFIER ::= { mvpnMIB 2 } 284 -- mvpn Objects 285 mvpnScalars OBJECT IDENTIFIER ::= { mvpnObjects 1 } 287 -- Scalar Objects 289 mvpnMvrfs OBJECT-TYPE 290 SYNTAX Gauge32 291 MAX-ACCESS read-only 292 STATUS current 293 DESCRIPTION 294 "The total number of Multicast Virtual Routing and 295 Forwarding tables (MVRFs) that are present on 296 this Provider Edge router (PE). This includes MVRFs 297 for IPv4, IPv6, and mLDP C-Multicast. 298 " 299 ::= { mvpnScalars 1 } 301 mvpnV4Mvrfs OBJECT-TYPE 302 SYNTAX Gauge32 303 MAX-ACCESS read-only 304 STATUS current 305 DESCRIPTION 306 "The number of MVRFs for IPv4 C-Multicast on this PE. 307 " 308 ::= { mvpnScalars 2 } 310 mvpnV6Mvrfs OBJECT-TYPE 311 SYNTAX Gauge32 312 MAX-ACCESS read-only 313 STATUS current 314 DESCRIPTION 315 "The number of MVRFs for IPv6 C-Multicast on this PE. 316 " 317 ::= { mvpnScalars 3 } 319 mvpnMldpMvrfs OBJECT-TYPE 320 SYNTAX Gauge32 321 MAX-ACCESS read-only 322 STATUS current 323 DESCRIPTION 324 "The number of MVRFs on this PE that use BGP for 325 exchanging Multipoint Label Distribution Protocol (mLDP) 326 C-Multicast routing information. 327 " 328 ::= { mvpnScalars 4 } 330 mvpnPimV4Mvrfs OBJECT-TYPE 331 SYNTAX Gauge32 332 MAX-ACCESS read-only 333 STATUS current 334 DESCRIPTION 335 "The number of MVRFs on this PE that use Provider 336 Independent Multicast (PIM) for exchanging IPv4 337 C-Multicast routing information. 338 " 339 ::= { mvpnScalars 5 } 341 mvpnPimV6Mvrfs OBJECT-TYPE 342 SYNTAX Gauge32 343 MAX-ACCESS read-only 344 STATUS current 345 DESCRIPTION 346 "The number of MVRFs on this PE that use PIM for 347 exchanging IPv6 C-Multicast routing information. 348 " 349 ::= { mvpnScalars 6 } 351 mvpnBgpV4Mvrfs OBJECT-TYPE 352 SYNTAX Gauge32 353 MAX-ACCESS read-only 354 STATUS current 355 DESCRIPTION 356 "The number of MVRFs on this PE that use BGP for 357 exchanging IPv4 C-Multicast routing information. 358 " 359 ::= { mvpnScalars 7 } 361 mvpnBgpV6Mvrfs OBJECT-TYPE 362 SYNTAX Gauge32 363 MAX-ACCESS read-only 364 STATUS current 365 DESCRIPTION 366 "The number of MVRFs on this PE that use BGP for 367 exchanging IPv6 C-Multicast routing information. 368 " 369 ::= { mvpnScalars 8 } 371 mvpnSPTunnelLimit OBJECT-TYPE 372 SYNTAX Unsigned32 (1..4294967295) 373 MAX-ACCESS read-write 374 STATUS current 375 DESCRIPTION 376 "The maximum number of selective provider tunnels that 377 this PE allows for a particular MVPN on this PE. 378 " 379 REFERENCE 380 "RFC6513, Section 13" 381 ::= { mvpnScalars 9 } 383 mvpnBgpCmcastRouteWithdrawalTimer OBJECT-TYPE 384 SYNTAX Unsigned32 385 UNITS "milliseconds" 386 MAX-ACCESS read-write 387 STATUS current 388 DESCRIPTION 389 "A configurable timer to control the delay 390 of C-multicast route withdrawal advertisements. 391 " 392 REFERENCE 393 "RFC6514, Section 16.1.1" 394 ::= { mvpnScalars 10 } 396 mvpnBgpSrcSharedTreeJoinTimer OBJECT-TYPE 397 SYNTAX Unsigned32 398 UNITS "milliseconds" 399 MAX-ACCESS read-write 400 STATUS current 401 DESCRIPTION 402 "A configurable timer to control the delay 403 of Source/Shared Tree Join C-multicast route 404 advertisements. 405 " 406 REFERENCE 407 "RFC6514, Section 16.1.2" 408 ::= { mvpnScalars 11 } 410 -- Generic MVRF Information Table 412 mvpnGenericTable OBJECT-TYPE 413 SYNTAX SEQUENCE OF MvpnGenericEntry 414 MAX-ACCESS not-accessible 415 STATUS current 416 DESCRIPTION 417 "A conceptual table containing generic information about MVPNs 418 on this PE. 419 " 420 ::= { mvpnObjects 2 } 422 mvpnGenericEntry OBJECT-TYPE 423 SYNTAX MvpnGenericEntry 424 MAX-ACCESS not-accessible 425 STATUS current 426 DESCRIPTION 427 "A conceptual row that represents an MVPN on this PE. 429 The MVPN represented by this entry will have one or more 430 corresponding P-Multicast Service Interfaces (PMSIs) 431 and a corresponding VRF in MPLS-L3VPN-STD-MIB [RFC4382]. 432 " 433 INDEX { 434 mplsL3VpnVrfName 435 } 436 ::= { mvpnGenericTable 1 } 438 MvpnGenericEntry ::= SEQUENCE { 439 mvpnGenMvrfLastAction INTEGER, 440 mvpnGenMvrfLastActionTime DateAndTime, 441 mvpnGenMvrfCreationTime DateAndTime, 442 mvpnGenCmcastRouteProtocol INTEGER, 443 mvpnGenIpmsiInfo RowPointer, 444 mvpnGenInterAsPmsiInfo RowPointer, 445 mvpnGenUmhSelection INTEGER, 446 mvpnGenCustomerSiteType INTEGER 447 } 449 mvpnGenMvrfLastAction OBJECT-TYPE 450 SYNTAX INTEGER { 451 createdMvrf (1), 452 deletedMvrf (2), 453 modifiedMvrfIpmsiConfig (3), 454 modifiedMvrfSpmsiConfig (4) 455 } 456 MAX-ACCESS read-only 457 STATUS current 458 DESCRIPTION 459 "This object describes the last action pertaining 460 to the MVPN represented by this entry. 462 The enumerated action types and the corresponding 463 descriptions are as follows: 465 createdMvrf: 466 MVRF was created for this MVPN on the PE. 468 deletedMvrf: 469 MVRF for this MVPN was deleted from the PE. 470 A conceptual row in this table will never have 471 mvpnGenMvrfLastAction equal to deletedMvrf, 472 because in that case the row itself will not exist 473 in the table. 474 This value for mvpnGenMvrfLastAction is defined 475 solely for use in mvpnMvrfActionChange notification. 477 modifiedMvrfIpmsiConfig: 478 an I-PMSI for this MVPN was configured, deleted or 479 changed. 481 modifiedMvrfSpmsiConfig: 482 an S-PMSI for this MVPN was configured, deleted or 483 changed. 484 " 485 ::= { mvpnGenericEntry 2 } 487 mvpnGenMvrfLastActionTime OBJECT-TYPE 488 SYNTAX DateAndTime 489 MAX-ACCESS read-only 490 STATUS current 491 DESCRIPTION 492 "The timestamp when the last action, given in 493 the corresponding mvpnGenMvrfLastAction object, 494 was carried out. 495 " 496 ::= { mvpnGenericEntry 3 } 498 mvpnGenMvrfCreationTime OBJECT-TYPE 499 SYNTAX DateAndTime 500 MAX-ACCESS read-only 501 STATUS current 502 DESCRIPTION 503 "The timestamp when the MVRF was created for 504 the MVPN represented by this entry. 505 " 506 ::= { mvpnGenericEntry 4 } 508 mvpnGenCmcastRouteProtocol OBJECT-TYPE 509 SYNTAX INTEGER { 510 pim (1), 511 bgp (2) 512 } 513 MAX-ACCESS read-only 514 STATUS current 515 DESCRIPTION 516 "The protocol used to signal C-multicast routing 517 information across the provider core for the MVPN 518 represented by this entry. 520 The enumerated protocols and the corresponding 521 descriptions are as follows: 523 pim : PIM (PIM-MVPN) 524 bgp : BGP (BGP-MVPN) 526 " 527 REFERENCE 528 "RFC6513, Section 5" 529 ::= { mvpnGenericEntry 5 } 531 mvpnGenIpmsiInfo OBJECT-TYPE 532 SYNTAX RowPointer 533 MAX-ACCESS read-only 534 STATUS current 535 DESCRIPTION 536 "A pointer to a conceptual row representing 537 the corresponding I-PMSI in mvpnPmsiTable. 538 If there is no I-PMSI for the MVPN 539 represented by this entry, the 540 value of this object will be zeroDotZero. 541 " 542 ::= { mvpnGenericEntry 6 } 544 mvpnGenInterAsPmsiInfo OBJECT-TYPE 545 SYNTAX RowPointer 546 MAX-ACCESS read-only 547 STATUS current 548 DESCRIPTION 549 "A pointer to a conceptual row representing 550 the corresponding segmented Inter-AS I-PMSI in mvpnPmsiTable. 551 If there is no segmented Inter-AS I-PMSI for the MVPN, 552 the value of this object will be zeroDotZero. 553 " 554 ::= { mvpnGenericEntry 7 } 556 mvpnGenUmhSelection OBJECT-TYPE 557 SYNTAX INTEGER { 558 highestPeAddress (1), 559 cRootGroupHashing (2), 560 ucastUmhRoute (3) 561 } 562 MAX-ACCESS read-only 563 STATUS current 564 DESCRIPTION 565 "The Upstream Multicast Hop (UMH) selection method for the MVPN 566 represented by this entry. 568 The enumerated methods and the corresponding 569 descriptions are as follows: 571 highestPeAddress : PE with the highest address 572 (see RFC6513, Section 5.1.3) 573 cRootGroupHashing : hashing based on (c-root, c-group) 574 ucastUmhRoute : per unicast route towards c-root 575 " 576 REFERENCE 577 "RFC6513, Section 5.1" 578 ::= { mvpnGenericEntry 8 } 580 mvpnGenCustomerSiteType OBJECT-TYPE 581 SYNTAX INTEGER { 582 senderReceiver (1), 583 receiverOnly (2), 584 senderOnly (3) 585 } 586 MAX-ACCESS read-only 587 STATUS current 588 DESCRIPTION 589 "The type of the customer site, connected to 590 the MVPN represented by this entry. 592 The enumerated types and the corresponding 593 descriptions are as follows: 595 senderReceiver : Site is both sender and receiver 596 receiverOnly : Site is receiver-only 597 senderOnly : Site is sender-only 598 " 599 REFERENCE 600 "RFC6513, Section 2.3" 601 ::= { mvpnGenericEntry 9 } 603 -- Generic BGP-MVPN table 605 mvpnBgpTable OBJECT-TYPE 606 SYNTAX SEQUENCE OF MvpnBgpEntry 607 MAX-ACCESS not-accessible 608 STATUS current 609 DESCRIPTION 610 "A conceptual table that supplements mvpnGenericTable 611 with BGP-MVPN specific information for BGP-MVPNs on this PE. 612 " 613 ::= { mvpnObjects 3 } 615 mvpnBgpEntry OBJECT-TYPE 616 SYNTAX MvpnBgpEntry 617 MAX-ACCESS not-accessible 618 STATUS current 619 DESCRIPTION 620 "A conceptual row corresponding to a BGP-MVPN on this PE. 621 " 623 INDEX { 624 mplsL3VpnVrfName 625 } 626 ::= { mvpnBgpTable 1 } 628 MvpnBgpEntry ::= SEQUENCE { 629 mvpnBgpMode INTEGER, 630 mvpnBgpVrfRouteImportExtendedCommunity MplsL3VpnRouteDistinguisher, 631 mvpnBgpSrcASExtendedCommunity Unsigned32, 632 mvpnBgpMsgRateLimit Unsigned32, 633 mvpnBgpMaxSpmsiAdRoutes Unsigned32, 634 mvpnBgpMaxSpmsiAdRouteFreq Unsigned32, 635 mvpnBgpMaxSrcActiveAdRoutes Unsigned32, 636 mvpnBgpMaxSrcActiveAdRouteFreq Unsigned32 637 } 639 mvpnBgpMode OBJECT-TYPE 640 SYNTAX INTEGER { 641 other (0), 642 rptSpt (1), 643 sptOnly (2) 644 } 645 MAX-ACCESS read-only 646 STATUS current 647 DESCRIPTION 648 "The inter-site C-tree mode used by the BGP-MVPN 649 represented by this entry. 651 other : none of the following 652 rptSpt : inter-site shared tree mode 653 (Rendezvous Point Tree (RPT) and 654 source-specific shortest-path tree (SPT)) 655 sptOnly : inter-site source-only tree mode 656 " 657 REFERENCE 658 "RFC6513, Section 9.3.1" 659 ::= { mvpnBgpEntry 1 } 661 mvpnBgpVrfRouteImportExtendedCommunity OBJECT-TYPE 662 SYNTAX MplsL3VpnRouteDistinguisher 663 MAX-ACCESS read-only 664 STATUS current 665 DESCRIPTION 666 "The VRF Route Import Extended Community added by this PE 667 to unicast VPN routes that it advertises for the BGP-MVPN 668 corresponding to this entry. 669 " 670 REFERENCE 671 "RFC6514, Section 7 672 " 673 ::= { mvpnBgpEntry 2 } 675 mvpnBgpSrcASExtendedCommunity OBJECT-TYPE 676 SYNTAX Unsigned32 677 MAX-ACCESS read-only 678 STATUS current 679 DESCRIPTION 680 "The Source AS Extended Community added by this PE 681 to the unicast VPN routes that it advertises for 682 the BGP-MVPN represented by this entry. 683 " 684 REFERENCE 685 "RFC6514, Section 6 686 " 687 ::= { mvpnBgpEntry 3 } 689 mvpnBgpMsgRateLimit OBJECT-TYPE 690 SYNTAX Unsigned32 (0..4294967295) 691 UNITS "messages per second" 692 MAX-ACCESS read-write 693 STATUS current 694 DESCRIPTION 695 "The configurable upper bound for the rate of BGP C-multicast 696 routing information message exchange between this PE and other 697 PEs in the BGP-MVPN corresponding to this entry. 698 " 699 REFERENCE 700 "RFC6514, Section 17" 701 ::= { mvpnBgpEntry 4 } 703 mvpnBgpMaxSpmsiAdRoutes OBJECT-TYPE 704 SYNTAX Unsigned32 (0..4294967295) 705 MAX-ACCESS read-write 706 STATUS current 707 DESCRIPTION 708 "The configurable upper bound for the number of 709 S-PMSI A-D routes for the BGP-MVPN corresponding to 710 this entry. 711 " 712 REFERENCE 713 "RFC6514, Section 17" 714 ::= { mvpnBgpEntry 5 } 716 mvpnBgpMaxSpmsiAdRouteFreq OBJECT-TYPE 717 SYNTAX Unsigned32 (0..4294967295) 718 UNITS "routes per second" 719 MAX-ACCESS read-write 720 STATUS current 721 DESCRIPTION 722 "The configurable upper bound for the frequency of 723 S-PMSI A-D route generation for the BGP-MVPN corresponding 724 to this entry. 725 " 726 REFERENCE 727 "RFC6514, Section 17" 728 ::= { mvpnBgpEntry 6 } 730 mvpnBgpMaxSrcActiveAdRoutes OBJECT-TYPE 731 SYNTAX Unsigned32 (0..4294967295) 732 MAX-ACCESS read-write 733 STATUS current 734 DESCRIPTION 735 "The configurable upper bound for the number of 736 Source Active A-D routes for the BGP-MVPN corresponding 737 to this entry. 738 " 739 REFERENCE 740 "RFC6514, Section 17" 741 ::= { mvpnBgpEntry 7 } 743 mvpnBgpMaxSrcActiveAdRouteFreq OBJECT-TYPE 744 SYNTAX Unsigned32 (0..4294967295) 745 UNITS "routes per second" 746 MAX-ACCESS read-write 747 STATUS current 748 DESCRIPTION 749 "The configurable upper bound for the frequency of Source 750 Active A-D route generation for the BGP-MVPN corresponding 751 to this entry. 752 " 753 REFERENCE 754 "RFC6514, Section 17" 755 ::= { mvpnBgpEntry 8 } 757 -- Table of PMSI information 759 mvpnPmsiTable OBJECT-TYPE 760 SYNTAX SEQUENCE OF MvpnPmsiEntry 761 MAX-ACCESS not-accessible 762 STATUS current 763 DESCRIPTION 764 "A conceptual table containing information related 765 to PMSIs on this PE. 766 " 768 ::= { mvpnObjects 4 } 770 mvpnPmsiEntry OBJECT-TYPE 771 SYNTAX MvpnPmsiEntry 772 MAX-ACCESS not-accessible 773 STATUS current 774 DESCRIPTION 775 "A conceptual row corresponding to a 776 PMSI on this PE. 777 " 778 INDEX { 779 mvpnPmsiTunnelIfIndex 780 } 781 ::= { mvpnPmsiTable 1 } 783 MvpnPmsiEntry ::= SEQUENCE { 784 mvpnPmsiTunnelIfIndex InterfaceIndex, 785 mvpnPmsiRD MplsL3VpnRouteDistinguisher, 786 mvpnPmsiTunnelType L2L3VpnMcastProviderTunnelType, 787 mvpnPmsiTunnelAttribute RowPointer, 788 mvpnPmsiTunnelPimGroupAddrType InetAddressType, 789 mvpnPmsiTunnelPimGroupAddr InetAddress, 790 mvpnPmsiEncapsulationType INTEGER 791 } 793 mvpnPmsiTunnelIfIndex OBJECT-TYPE 794 SYNTAX InterfaceIndex 795 MAX-ACCESS not-accessible 796 STATUS current 797 DESCRIPTION 798 "A unique value for this conceptual row. Its value 799 will be the same as that of the ifIndex object instance 800 for the corresponding PMSI in ifTable. 801 " 802 REFERENCE 803 "RFC2863 Sec. 3.1.5 804 " 805 ::= { mvpnPmsiEntry 1 } 807 mvpnPmsiRD OBJECT-TYPE 808 SYNTAX MplsL3VpnRouteDistinguisher 809 MAX-ACCESS read-only 810 STATUS current 811 DESCRIPTION 812 "The Route Distinguisher for this I-PMSI." 813 ::= { mvpnPmsiEntry 3 } 815 mvpnPmsiTunnelType OBJECT-TYPE 816 SYNTAX L2L3VpnMcastProviderTunnelType 817 MAX-ACCESS read-only 818 STATUS current 819 DESCRIPTION 820 "The type of tunnel used to 821 instantiate the PMSI corresponding to this entry. 822 " 823 REFERENCE 824 "RFC6513, Sec. 2.6 825 " 826 ::= { mvpnPmsiEntry 4 } 828 mvpnPmsiTunnelAttribute OBJECT-TYPE 829 SYNTAX RowPointer 830 MAX-ACCESS read-only 831 STATUS current 832 DESCRIPTION 833 "A pointer to a conceptual row representing 834 the P-tunnel used by the PMSI in 835 l2L3VpnMcastPmsiTunnelAttributeTable. 836 " 837 ::= { mvpnPmsiEntry 5 } 839 mvpnPmsiTunnelPimGroupAddrType OBJECT-TYPE 840 SYNTAX InetAddressType 841 MAX-ACCESS read-only 842 STATUS current 843 DESCRIPTION 844 "The InetAddressType of the mvpnPmsiTunnelPimGroupAddr object 845 that follows. 846 When the PMSI corresponding to this entry does not use 847 the PIM provider tunnel, i.e., 848 the value of mvpnPmsiTunnelType is not one of 849 pimSsm(3), pimAsm(4), or pimBidir(5), 850 this object should be unknown(0). 851 " 852 ::= { mvpnPmsiEntry 6 } 854 mvpnPmsiTunnelPimGroupAddr OBJECT-TYPE 855 SYNTAX InetAddress 856 MAX-ACCESS read-only 857 STATUS current 858 DESCRIPTION 859 "The tunnel address which is used by the PMSI 860 corresponding to this entry. 861 When the PMSI corresponding to this entry does not 862 use PIM provider tunnel, i.e., 863 the value of mvpnPmsiTunnelType is not one of 864 pimSsm(3), pimAsm(4), or pimBidir(5), 865 this object should be a zero-length octet string. 866 " 867 ::= { mvpnPmsiEntry 7 } 869 mvpnPmsiEncapsulationType OBJECT-TYPE 870 SYNTAX INTEGER { 871 greIp (1), 872 ipIp (2), 873 mpls (3) 874 } 875 MAX-ACCESS read-only 876 STATUS current 877 DESCRIPTION 878 "The encapsulation type used for sending 879 packets through the PMSI corresponding to this entry. 881 The enumerated encapsulation types and the corresponding 882 descriptions are as follows: 884 greIp : GRE (Generic Routing Encapsulation) 885 encapsulation [RFC2784] 886 ipIp : IP-in-IP encapsulation [RFC2003] 887 mpls : MPLS encapsulation [RFC3032] 888 " 889 REFERENCE 890 "RFC2003 891 RFC2784 892 RFC3032 893 RFC6513, Sec. 12.1 894 " 895 ::= { mvpnPmsiEntry 8 } 897 -- Table of S-PMSI specific information 899 mvpnSpmsiTable OBJECT-TYPE 900 SYNTAX SEQUENCE OF MvpnSpmsiEntry 901 MAX-ACCESS not-accessible 902 STATUS current 903 DESCRIPTION 904 "A conceptual table containing information related 905 to S-PMSIs on this PE. 906 This table stores only S-PMSI specific attribute 907 information. Generic PMSI attribute information of 908 S-PMSIs is stored in mvpnPmsiTable. 909 " 910 ::= { mvpnObjects 5 } 912 mvpnSpmsiEntry OBJECT-TYPE 913 SYNTAX MvpnSpmsiEntry 914 MAX-ACCESS not-accessible 915 STATUS current 916 DESCRIPTION 917 "A conceptual row corresponding to an S-PMSI on this PE. 918 Implementers need to be aware that if the total number of 919 octets in mplsL3VpnVrfName, mvpnSpmsiCmcastGroupAddr and 920 mvpnSpmsiCmcastSourceAddr exceeds 113, the OIDs of column 921 instances in this row will have more than 128 sub-identifiers 922 and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 923 " 924 INDEX { 925 mplsL3VpnVrfName, 926 mvpnSpmsiCmcastGroupAddrType, 927 mvpnSpmsiCmcastGroupAddr, 928 mvpnSpmsiCmcastGroupPrefixLen, 929 mvpnSpmsiCmcastSourceAddrType, 930 mvpnSpmsiCmcastSourceAddr, 931 mvpnSpmsiCmcastSourcePrefixLen 932 } 933 ::= { mvpnSpmsiTable 1 } 935 MvpnSpmsiEntry ::= SEQUENCE { 936 mvpnSpmsiCmcastGroupAddrType InetAddressType, 937 mvpnSpmsiCmcastGroupAddr InetAddress, 938 mvpnSpmsiCmcastGroupPrefixLen InetAddressPrefixLength, 939 mvpnSpmsiCmcastSourceAddrType InetAddressType, 940 mvpnSpmsiCmcastSourceAddr InetAddress, 941 mvpnSpmsiCmcastSourcePrefixLen InetAddressPrefixLength, 942 mvpnSpmsiPmsiPointer RowPointer 943 } 945 mvpnSpmsiCmcastGroupAddrType OBJECT-TYPE 946 SYNTAX InetAddressType 947 MAX-ACCESS not-accessible 948 STATUS current 949 DESCRIPTION 950 "The InetAddressType of the mvpnSpmsiCmcastGroupAddr object 951 that follows. 952 " 953 ::= { mvpnSpmsiEntry 1 } 955 mvpnSpmsiCmcastGroupAddr OBJECT-TYPE 956 SYNTAX InetAddress 957 MAX-ACCESS not-accessible 958 STATUS current 959 DESCRIPTION 960 "The group address of the C-flow assigned to the 961 S-PMSI corresponding to this entry." 962 REFERENCE 963 "RFC6513, Sec. 3.1" 964 ::= { mvpnSpmsiEntry 2 } 966 mvpnSpmsiCmcastGroupPrefixLen OBJECT-TYPE 967 SYNTAX InetAddressPrefixLength 968 MAX-ACCESS not-accessible 969 STATUS current 970 DESCRIPTION 971 "The prefix length of the corresponding 972 mvpnSpmsiCmcastGroupAddr object. 973 " 974 ::= { mvpnSpmsiEntry 3 } 976 mvpnSpmsiCmcastSourceAddrType OBJECT-TYPE 977 SYNTAX InetAddressType 978 MAX-ACCESS not-accessible 979 STATUS current 980 DESCRIPTION 981 "The InetAddressType of the mvpnSpmsiCmcastSourceAddr object 982 that follows. 983 " 984 ::= { mvpnSpmsiEntry 4 } 986 mvpnSpmsiCmcastSourceAddr OBJECT-TYPE 987 SYNTAX InetAddress 988 MAX-ACCESS not-accessible 989 STATUS current 990 DESCRIPTION 991 "The source address of the C-flow assigned to the 992 S-PMSI corresponding to this entry." 993 ::= { mvpnSpmsiEntry 5 } 995 mvpnSpmsiCmcastSourcePrefixLen OBJECT-TYPE 996 SYNTAX InetAddressPrefixLength 997 MAX-ACCESS not-accessible 998 STATUS current 999 DESCRIPTION 1000 "The prefix length of the corresponding 1001 mvpnSpmsiCmcastSourceAddr object. 1002 " 1003 ::= { mvpnSpmsiEntry 6 } 1005 mvpnSpmsiPmsiPointer OBJECT-TYPE 1006 SYNTAX RowPointer 1007 MAX-ACCESS read-only 1008 STATUS current 1009 DESCRIPTION 1010 "A pointer to a conceptual row representing 1011 generic information of this S-PMSI in mvpnPmsiTable. 1012 " 1013 ::= { mvpnSpmsiEntry 7 } 1015 -- Table of statistics pertaining to 1016 -- advertisements sent/received 1018 mvpnAdvtStatsTable OBJECT-TYPE 1019 SYNTAX SEQUENCE OF MvpnAdvtStatsEntry 1020 MAX-ACCESS not-accessible 1021 STATUS current 1022 DESCRIPTION 1023 "A conceptual table containing statistics pertaining to 1024 I-PMSI and S-PMSI advertisements sent/received by this PE. 1025 " 1026 ::= { mvpnObjects 6 } 1028 mvpnAdvtStatsEntry OBJECT-TYPE 1029 SYNTAX MvpnAdvtStatsEntry 1030 MAX-ACCESS not-accessible 1031 STATUS current 1032 DESCRIPTION 1033 "A conceptual row corresponding to statistics 1034 pertaining to advertisements sent/received 1035 for a particular MVPN on this PE. 1037 Implementers need to be aware that if the total number of 1038 octets in mplsL3VpnVrfName and mvpnAdvtPeerAddr exceeds 115, 1039 then OIDs of column instances in this row will have more than 1040 128 sub-identifiers and cannot be accessed using SNMPv1, 1041 SNMPv2c, or SNMPv3. 1042 " 1043 INDEX { 1044 mplsL3VpnVrfName, 1045 mvpnAdvtType, 1046 mvpnAdvtPeerAddrType, 1047 mvpnAdvtPeerAddr 1048 } 1049 ::= { mvpnAdvtStatsTable 1 } 1051 MvpnAdvtStatsEntry ::= SEQUENCE { 1052 mvpnAdvtType INTEGER, 1053 mvpnAdvtPeerAddrType InetAddressType, 1054 mvpnAdvtPeerAddr InetAddress, 1055 mvpnAdvtSent Counter32, 1056 mvpnAdvtReceived Counter32, 1057 mvpnAdvtReceivedError Counter32, 1058 mvpnAdvtReceivedMalformedTunnelType Counter32, 1059 mvpnAdvtReceivedMalformedTunnelId Counter32, 1060 mvpnAdvtLastSentTime DateAndTime, 1061 mvpnAdvtLastReceivedTime DateAndTime, 1062 mvpnAdvtCounterDiscontinuityTime TimeStamp 1063 } 1065 mvpnAdvtType OBJECT-TYPE 1066 SYNTAX INTEGER { 1067 intraAsIpmsi (0), 1068 interAsIpmsi (1), 1069 sPmsi (2) 1070 } 1071 MAX-ACCESS not-accessible 1072 STATUS current 1073 DESCRIPTION 1074 "The PMSI type. 1076 The enumerated PMSI types and corresponding 1077 descriptions are as follows: 1079 intraAsIpmsi : Intra-AS Inclusive PMSI 1080 interAsIpmsi : Inter-AS Inclusive PMSI 1081 sPmsi : Selective PMSI 1082 " 1083 REFERENCE 1084 "RFC6513, Sec. 3.2.1" 1085 ::= { mvpnAdvtStatsEntry 1 } 1087 mvpnAdvtPeerAddrType OBJECT-TYPE 1088 SYNTAX InetAddressType 1089 MAX-ACCESS not-accessible 1090 STATUS current 1091 DESCRIPTION 1092 "The InternetAddressType of the mvpnAdvtPeerAddr object 1093 that follows. 1094 " 1095 ::= { mvpnAdvtStatsEntry 2 } 1097 mvpnAdvtPeerAddr OBJECT-TYPE 1098 SYNTAX InetAddress 1099 MAX-ACCESS not-accessible 1100 STATUS current 1101 DESCRIPTION 1102 "The address of a peer PE that exchanges advertisement with 1103 this PE. 1104 " 1105 ::= { mvpnAdvtStatsEntry 3 } 1107 mvpnAdvtSent OBJECT-TYPE 1108 SYNTAX Counter32 1109 MAX-ACCESS read-only 1110 STATUS current 1111 DESCRIPTION 1112 "The number of advertisements successfully 1113 sent to the peer PE specified by the corresponding 1114 mvpnAdvtPeerAddr. 1116 Discontinuities in the value of this counter can 1117 occur at re-initialization of the management system, 1118 and at other times as indicated by the corresponding 1119 mvpnAdvtCounterDiscontinuityTime object. 1120 " 1121 ::= { mvpnAdvtStatsEntry 4 } 1123 mvpnAdvtReceived OBJECT-TYPE 1124 SYNTAX Counter32 1125 MAX-ACCESS read-only 1126 STATUS current 1127 DESCRIPTION 1128 "The number of advertisements received from the peer PE 1129 specified by the corresponding mvpnAdvtPeerAddr object. 1130 This includes advertisements that were discarded. 1132 Discontinuities in the value of this counter can 1133 occur at re-initialization of the management system, 1134 and at other times as indicated by the corresponding 1135 mvpnAdvtCounterDiscontinuityTime object. 1136 " 1137 ::= { mvpnAdvtStatsEntry 5 } 1139 mvpnAdvtReceivedError OBJECT-TYPE 1140 SYNTAX Counter32 1141 MAX-ACCESS read-only 1142 STATUS current 1143 DESCRIPTION 1144 "The total number of advertisements received from a peer PE, 1145 specified by the corresponding mvpnAdvtPeerAddr object, 1146 that were rejected due to error(s) in the advertisement. 1147 The value of this object includes 1148 the error cases counted in the corresponding 1149 mvpnAdvtReceivedMalformedTunnelType and 1150 mvpnAdvtReceivedMalformedTunnelId objects. 1152 Discontinuities in the value of this counter can 1153 occur at re-initialization of the management system, 1154 and at other times as indicated by the corresponding 1155 mvpnAdvtCounterDiscontinuityTime object. 1156 " 1157 ::= { mvpnAdvtStatsEntry 6 } 1159 mvpnAdvtReceivedMalformedTunnelType OBJECT-TYPE 1160 SYNTAX Counter32 1161 MAX-ACCESS read-only 1162 STATUS current 1163 DESCRIPTION 1164 "The total number of advertisements received from the peer PE 1165 specified by the corresponding mvpnAdvtPeerAddr object, 1166 that were rejected due to malformed Tunnel Type 1167 in the PMSI Tunnel attribute. 1169 Discontinuities in the value of this counter can 1170 occur at re-initialization of the management system, 1171 and at other times as indicated by the corresponding 1172 mvpnAdvtCounterDiscontinuityTime object. 1173 " 1174 REFERENCE 1175 "RFC6514 Sec.5" 1176 ::= { mvpnAdvtStatsEntry 7 } 1178 mvpnAdvtReceivedMalformedTunnelId OBJECT-TYPE 1179 SYNTAX Counter32 1180 MAX-ACCESS read-only 1181 STATUS current 1182 DESCRIPTION 1183 "The total number of advertisements received from the peer PE 1184 specified by the corresponding mvpnAdvtPeerAddr object, 1185 that were rejected due to malformed Tunnel Identifier 1186 in the PMSI Tunnel attribute. 1187 Discontinuities in the value of this counter can 1188 occur at re-initialization of the management system, 1189 and at other times as indicated by the corresponding 1190 mvpnAdvtCounterDiscontinuityTime object. 1191 " 1192 REFERENCE 1193 "RFC6514 Sec.5" 1194 ::= { mvpnAdvtStatsEntry 8 } 1196 mvpnAdvtLastSentTime OBJECT-TYPE 1197 SYNTAX DateAndTime 1198 MAX-ACCESS read-only 1199 STATUS current 1200 DESCRIPTION 1201 "The timestamp when the last advertisement 1202 was successfully sent by this PE. 1203 If no advertisement has been sent since the 1204 last re-initialization of this PE, then this 1205 object will have a zero-length string. 1206 " 1207 ::= { mvpnAdvtStatsEntry 9 } 1209 mvpnAdvtLastReceivedTime OBJECT-TYPE 1210 SYNTAX DateAndTime 1211 MAX-ACCESS read-only 1212 STATUS current 1213 DESCRIPTION 1214 "The timestamp when the last advertisement 1215 was successfully received from the peer PE specified 1216 by the corresponding mvpnAdvtPeerAddr object and 1217 processed by this PE. 1218 If no advertisement has been received since the 1219 last re-initialization of this PE, then this 1220 object will have a zero-length string. 1221 " 1222 ::= { mvpnAdvtStatsEntry 10 } 1224 mvpnAdvtCounterDiscontinuityTime OBJECT-TYPE 1225 SYNTAX TimeStamp 1226 MAX-ACCESS read-only 1227 STATUS current 1228 DESCRIPTION 1229 "The value of sysUpTime on the most recent occasion 1230 at which any one or more of this application's 1231 counters, viz., counters with OID prefix 1232 'mvpnAdvtSent' or 1233 'mvpnAdvtReceived' or 1234 'mvpnAdvtReceivedError' or 1235 'mvpnAdvtReceivedMalformedTunnelType' or 1236 'mvpnAdvtReceivedMalformedTunnelId' suffered a 1237 discontinuity. 1238 If no such discontinuities have occurred since the 1239 last re-initialization of the local management 1240 subsystem, then this object will have a zero value. 1241 " 1242 ::= { mvpnAdvtStatsEntry 11 } 1244 -- Table of multicast routes in an MVPN 1246 mvpnMrouteTable OBJECT-TYPE 1247 SYNTAX SEQUENCE OF MvpnMrouteEntry 1248 MAX-ACCESS not-accessible 1249 STATUS current 1250 DESCRIPTION 1251 "A conceptual table containing multicast routing information 1252 corresponding to the MVRFs present on the PE. 1253 " 1254 ::= { mvpnObjects 7 } 1256 mvpnMrouteEntry OBJECT-TYPE 1257 SYNTAX MvpnMrouteEntry 1258 MAX-ACCESS not-accessible 1259 STATUS current 1260 DESCRIPTION 1261 "A conceptual row corresponding to a route for IP datagrams 1262 from a particular source and addressed to a particular IP 1263 multicast group address. 1265 Implementers need to be aware that if the total number of 1266 octets in mplsL3VpnVrfName, mvpnMrouteCmcastGroupAddr and 1267 mvpnMrouteCmcastSourceAddrs exceeds 113, the OIDs of column 1268 instances in this row will have more than 128 sub-identifiers 1269 and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 1270 " 1271 INDEX { 1272 mplsL3VpnVrfName, 1273 mvpnMrouteCmcastGroupAddrType, 1274 mvpnMrouteCmcastGroupAddr, 1275 mvpnMrouteCmcastGroupPrefixLength, 1276 mvpnMrouteCmcastSourceAddrType, 1277 mvpnMrouteCmcastSourceAddrs, 1278 mvpnMrouteCmcastSourcePrefixLength 1279 } 1280 ::= { mvpnMrouteTable 1 } 1282 MvpnMrouteEntry ::= SEQUENCE { 1283 mvpnMrouteCmcastGroupAddrType InetAddressType, 1284 mvpnMrouteCmcastGroupAddr InetAddress, 1285 mvpnMrouteCmcastGroupPrefixLength InetAddressPrefixLength, 1286 mvpnMrouteCmcastSourceAddrType InetAddressType, 1287 mvpnMrouteCmcastSourceAddrs InetAddress, 1288 mvpnMrouteCmcastSourcePrefixLength InetAddressPrefixLength, 1289 mvpnMrouteUpstreamNeighborAddrType InetAddressType, 1290 mvpnMrouteUpstreamNeighborAddr InetAddress, 1291 mvpnMrouteInIfIndex InterfaceIndexOrZero, 1292 mvpnMrouteExpiryTime TimeTicks, 1293 mvpnMrouteProtocol IANAipMRouteProtocol, 1294 mvpnMrouteRtProtocol IANAipRouteProtocol, 1295 mvpnMrouteRtAddrType InetAddressType, 1296 mvpnMrouteRtAddr InetAddress, 1297 mvpnMrouteRtPrefixLength InetAddressPrefixLength, 1298 mvpnMrouteRtType INTEGER, 1299 mvpnMrouteOctets Counter64, 1300 mvpnMroutePkts Counter64, 1301 mvpnMrouteTtlDroppedOctets Counter64, 1302 mvpnMrouteTtlDroppedPackets Counter64, 1303 mvpnMrouteDroppedInOctets Counter64, 1304 mvpnMrouteDroppedInPackets Counter64, 1305 mvpnMroutePmsiPointer RowPointer, 1306 mvpnMrouteNumberOfLocalReplication Unsigned32, 1307 mvpnMrouteNumberOfRemoteReplication Unsigned32, 1308 mvpnMrouteCounterDiscontinuityTime TimeStamp 1309 } 1311 mvpnMrouteCmcastGroupAddrType OBJECT-TYPE 1312 SYNTAX InetAddressType 1313 MAX-ACCESS not-accessible 1314 STATUS current 1315 DESCRIPTION 1316 "The InetAddressType of the mvpnMrouteCmcastGroupAddr object 1317 that follows. 1318 " 1319 ::= { mvpnMrouteEntry 1 } 1321 mvpnMrouteCmcastGroupAddr OBJECT-TYPE 1322 SYNTAX InetAddress 1323 MAX-ACCESS not-accessible 1324 STATUS current 1325 DESCRIPTION 1326 "The IP multicast group address which, along with 1327 the corresponding mvpnMrouteCmcastGroupPrefixLength object, 1328 identifies destinations for which this entry contains 1329 multicast routing information. 1331 This address object is only significant up to 1332 mvpnMrouteCmcastGroupPrefixLength bits. The remaining address 1333 bits MUST be set to zero. 1335 For addresses of type 'ipv4z' or 'ipv6z', the appended zone 1336 index is significant even though it lies beyond the prefix 1337 length. The use of these address types indicate that this 1338 forwarding state applies only within the given zone. Zone 1339 index zero is not valid in this table. 1340 " 1341 ::= { mvpnMrouteEntry 2 } 1343 mvpnMrouteCmcastGroupPrefixLength OBJECT-TYPE 1344 SYNTAX InetAddressPrefixLength 1345 MAX-ACCESS not-accessible 1346 STATUS current 1347 DESCRIPTION 1348 "The length in bits of the mask which, along with 1349 the corresponding mvpnMrouteCmcastGroupAddr object, 1350 identifies destinations for which this entry contains 1351 multicast routing information. 1353 If the corresponding InetAddressType is 'ipv4' or 'ipv4z', 1354 this object must be in the range 4..32. 1355 If the corresponding InetAddressType is 'ipv6' or 'ipv6z', 1356 this object must be in the range 8..128. 1357 " 1358 ::= { mvpnMrouteEntry 3 } 1360 mvpnMrouteCmcastSourceAddrType OBJECT-TYPE 1361 SYNTAX InetAddressType 1362 MAX-ACCESS not-accessible 1363 STATUS current 1364 DESCRIPTION 1365 "The InetAddressType of the mvpnMrouteCmcastSourceAddrs object 1366 that follows. 1368 A value of unknown(0) indicates a non-source-specific entry, 1369 corresponding to all sources in the group. Otherwise, the 1370 value MUST be the same as the value of 1371 mvpnMrouteCmcastGroupAddrType. 1372 " 1373 ::= { mvpnMrouteEntry 4 } 1375 mvpnMrouteCmcastSourceAddrs OBJECT-TYPE 1376 SYNTAX InetAddress 1377 MAX-ACCESS not-accessible 1378 STATUS current 1379 DESCRIPTION 1380 "The network address which, along with the 1381 corresponding mvpnMrouteCmcastSourcePrefixLength object, 1382 identifies the sources for which this entry contains 1383 multicast routing information. 1385 This address object is only significant up to 1386 mvpnMrouteCmcastSourcePrefixLength bits. 1387 The remaining address bits MUST be set to zero. 1389 For addresses of type 'ipv4z' or 'ipv6z', the appended zone 1390 index is significant even though it lies beyond the prefix 1391 length. The use of these address types indicate that this 1392 source address applies only within the given zone. Zone 1393 index zero is not valid in this table. 1394 " 1395 ::= { mvpnMrouteEntry 5 } 1397 mvpnMrouteCmcastSourcePrefixLength OBJECT-TYPE 1398 SYNTAX InetAddressPrefixLength 1399 MAX-ACCESS not-accessible 1400 STATUS current 1401 DESCRIPTION 1402 "The length in bits of the mask which, along with 1403 the corresponding mvpnMrouteCmcastSourceAddr object, 1404 identifies the sources for which this entry contains 1405 multicast routing information. 1407 If the corresponding InetAddressType is 'ipv4' or 'ipv4z', 1408 this object must be in the range 4..32. 1409 If the corresponding InetAddressType is 'ipv6' or 'ipv6z', 1410 this object must be in the range 8..128. 1411 If the corresponding InetAddressType is 'unknown', 1412 this object must be zero. 1413 " 1414 ::= { mvpnMrouteEntry 6 } 1416 mvpnMrouteUpstreamNeighborAddrType OBJECT-TYPE 1417 SYNTAX InetAddressType 1418 MAX-ACCESS read-only 1419 STATUS current 1420 DESCRIPTION 1421 "The InetAddressType of the mvpnMrouteUpstreamNeighborAddr 1422 object that follows. 1424 A value of unknown(0) indicates that the upstream 1425 neighbor is unknown, for example in BIDIR-PIM." 1426 REFERENCE 1427 "RFC 5015" 1428 ::= { mvpnMrouteEntry 7 } 1430 mvpnMrouteUpstreamNeighborAddr OBJECT-TYPE 1431 SYNTAX InetAddress 1432 MAX-ACCESS read-only 1433 STATUS current 1434 DESCRIPTION 1435 "The address of the upstream neighbor (for example, 1436 Reverse Path Forwarding (RPF) neighbor) from which 1437 IP datagrams from these sources represented by 1438 this entry to this multicast address are received. 1439 " 1441 ::= { mvpnMrouteEntry 8 } 1443 mvpnMrouteInIfIndex OBJECT-TYPE 1444 SYNTAX InterfaceIndexOrZero 1445 MAX-ACCESS read-only 1446 STATUS current 1447 DESCRIPTION 1448 "The value of ifIndex for the interface on which IP 1449 datagrams sent by these sources represented by this entry to 1450 this multicast address are received. 1452 A value 0 indicates that datagrams are not 1453 subject to an incoming interface check, but may be accepted 1454 on multiple interfaces (for example, in BIDIR-PIM). 1455 " 1456 REFERENCE 1457 "RFC 5015" 1458 ::= { mvpnMrouteEntry 9 } 1460 mvpnMrouteExpiryTime OBJECT-TYPE 1461 SYNTAX TimeTicks 1462 MAX-ACCESS read-only 1463 STATUS current 1464 DESCRIPTION 1465 "The minimum amount of time remaining before this entry will 1466 be aged out. The value 0 indicates that the entry is not 1467 subject to aging. If the corresponding mvpnMrouteNextHopState 1468 object is pruned(1), this object represents the remaining 1469 time for the prune to expire after which the state will 1470 return to forwarding(2). 1471 If the corresponding mvpnMrouteNextHopState object is 1472 forwarding(2), this object indicates the time after which 1473 this entry will be removed from the table. 1474 " 1475 ::= { mvpnMrouteEntry 10 } 1477 mvpnMrouteProtocol OBJECT-TYPE 1478 SYNTAX IANAipMRouteProtocol 1479 MAX-ACCESS read-only 1480 STATUS current 1481 DESCRIPTION 1482 "The multicast routing protocol via which this multicast 1483 forwarding entry was learned. 1484 " 1485 ::= { mvpnMrouteEntry 11 } 1487 mvpnMrouteRtProtocol OBJECT-TYPE 1488 SYNTAX IANAipRouteProtocol 1489 MAX-ACCESS read-only 1490 STATUS current 1491 DESCRIPTION 1492 "The routing protocol via which the route used to find the 1493 upstream or parent interface for this multicast forwarding 1494 entry was learned. 1495 " 1496 ::= { mvpnMrouteEntry 12 } 1498 mvpnMrouteRtAddrType OBJECT-TYPE 1499 SYNTAX InetAddressType 1500 MAX-ACCESS read-only 1501 STATUS current 1502 DESCRIPTION 1503 "The InetAddressType of the mvpnMrouteRtAddr object 1504 that follows. 1505 " 1506 ::= { mvpnMrouteEntry 13 } 1508 mvpnMrouteRtAddr OBJECT-TYPE 1509 SYNTAX InetAddress 1510 MAX-ACCESS read-only 1511 STATUS current 1512 DESCRIPTION 1513 "The address portion of the route used to find the upstream 1514 or parent interface for this multicast forwarding entry. 1516 This address object is only significant up to 1517 mvpnMrouteRtPrefixLength bits. The remaining address bits 1518 MUST be set to zero. 1520 For addresses of type 'ipv4z' or 'ipv6z', the appended zone 1521 index is significant even though it lies beyond the prefix 1522 length. The use of these address types indicate that this 1523 forwarding state applies only within the given zone. Zone 1524 index zero is not valid in this table. 1525 " 1526 ::= { mvpnMrouteEntry 14 } 1528 mvpnMrouteRtPrefixLength OBJECT-TYPE 1529 SYNTAX InetAddressPrefixLength 1530 MAX-ACCESS read-only 1531 STATUS current 1532 DESCRIPTION 1533 "The length in bits of the mask associated with the route 1534 used to find the upstream or parent interface for this 1535 multicast forwarding entry. 1537 If the corresponding InetAddressType is 'ipv4' or 'ipv4z', 1538 this object must be in the range 4..32. 1539 If the corresponding InetAddressType is 'ipv6' or 'ipv6z', 1540 this object must be in the range 8..128. 1541 " 1542 ::= { mvpnMrouteEntry 15 } 1544 mvpnMrouteRtType OBJECT-TYPE 1545 SYNTAX INTEGER { 1546 unicast (1), 1547 multicast (2) 1548 } 1549 MAX-ACCESS read-only 1550 STATUS current 1551 DESCRIPTION 1552 "The reason for placing the route in the (logical) 1553 multicast Routing Information Base (RIB). 1555 The enumerated reasons and the corresponding 1556 descriptions are as follows: 1558 unicast: 1559 The route would normally be placed only in 1560 the unicast RIB, but was placed in the multicast RIB 1561 by local configuration, such as when running PIM over 1562 RIP. 1564 multicast: 1565 The route was explicitly added to the multicast RIB by 1566 the routing protocol, such as the Distance Vector 1567 Multicast Routing Protocol (DVMRP) or Multiprotocol BGP. 1568 " 1569 ::= { mvpnMrouteEntry 16 } 1571 mvpnMrouteOctets OBJECT-TYPE 1572 SYNTAX Counter64 1573 MAX-ACCESS read-only 1574 STATUS current 1575 DESCRIPTION 1576 "The number of octets contained in IP datagrams that were 1577 received from sources represented by this entry and 1578 addressed to this multicast group address, and which were 1579 forwarded by this router. 1581 Discontinuities in the value of this counter can 1582 occur at re-initialization of the management system, 1583 and at other times as indicated by the corresponding 1584 mvpnMrouteCounterDiscontinuityTime object. 1586 " 1587 ::= { mvpnMrouteEntry 17 } 1589 mvpnMroutePkts OBJECT-TYPE 1590 SYNTAX Counter64 1591 MAX-ACCESS read-only 1592 STATUS current 1593 DESCRIPTION 1594 "The number of packets routed using this multicast route 1595 entry. 1597 Discontinuities in the value of this counter can 1598 occur at re-initialization of the management system, 1599 and at other times as indicated by the corresponding 1600 mvpnMrouteCounterDiscontinuityTime object. 1601 " 1602 ::= { mvpnMrouteEntry 18 } 1604 mvpnMrouteTtlDroppedOctets OBJECT-TYPE 1605 SYNTAX Counter64 1606 MAX-ACCESS read-only 1607 STATUS current 1608 DESCRIPTION 1609 "The number of octets contained in IP datagrams that this 1610 router has received from sources represented by 1611 this entry and addressed to this multicast group address, 1612 which were dropped due to Time To Live (TTL) issues. 1613 TTL issues occur when the TTL (IPv4) or Hop Limit (IPv6) 1614 of the incoming packet was decremented to zero, or to a 1615 value less than ipMcastInterfaceTtl of the corresponding 1616 interface. 1618 The ipMcastInterfaceTtl object is defined in IPMCAST-MIB 1619 [RFC5132] and represents the datagram TTL 1620 threshold for the interface. Any IP multicast datagrams 1621 with a TTL (IPv4) or Hop Limit (IPv6) less than this 1622 threshold will not be forwarded out of the interface. 1623 The default value of 0 means all multicast packets are 1624 forwarded out of the interface. A value of 256 means that 1625 no multicast packets are forwarded out of the interface. 1627 Discontinuities in the value of this counter can 1628 occur at re-initialization of the management system, 1629 and at other times as indicated by the corresponding 1630 mvpnMrouteCounterDiscontinuityTime object. 1631 " 1632 REFERENCE 1633 "RFC5132, Sec. 6 1634 " 1635 ::= { mvpnMrouteEntry 19 } 1637 mvpnMrouteTtlDroppedPackets OBJECT-TYPE 1638 SYNTAX Counter64 1639 MAX-ACCESS read-only 1640 STATUS current 1641 DESCRIPTION 1642 "The number of packets that this router has received from 1643 the sources represented by this entry and addressed to this 1644 multicast group address, which were dropped due to 1645 Time To Live (TTL) issues. TTL issues occur when the 1646 TTL (IPv4) or Hop Limit (IPv6) of the incoming packet was 1647 decremented to zero, or to a value less than 1648 ipMcastInterfaceTtl of the corresponding interface. 1650 The ipMcastInterfaceTtl object is defined in IPMCAST-MIB 1651 [RFC5132] and represents the datagram TTL 1652 threshold for the interface. Any IP multicast datagrams 1653 with a TTL (IPv4) or Hop Limit (IPv6) less than this 1654 threshold will not be forwarded out of the interface. 1655 The default value of 0 means all multicast packets are 1656 forwarded out of the interface. A value of 256 means that 1657 no multicast packets are forwarded out of the interface. 1659 Discontinuities in the value of this counter can 1660 occur at re-initialization of the management system, 1661 and at other times as indicated by the corresponding 1662 mvpnMrouteCounterDiscontinuityTime object. 1663 " 1664 REFERENCE 1665 "RFC5132, Sec. 6 1666 " 1667 ::= { mvpnMrouteEntry 20 } 1669 mvpnMrouteDroppedInOctets OBJECT-TYPE 1670 SYNTAX Counter64 1671 MAX-ACCESS read-only 1672 STATUS current 1673 DESCRIPTION 1674 "The number of octets contained in IP datagrams that this 1675 router has received from sources represented by 1676 this entry and addressed to this multicast group address, 1677 which were dropped due to error(s). 1678 The value of this object includes the octets counted 1679 in the corresponding mvpnMrouteTtlDroppedOctets object. 1681 Discontinuities in the value of this counter can 1682 occur at re-initialization of the management system, 1683 and at other times as indicated by the corresponding 1684 mvpnMrouteCounterDiscontinuityTime object. 1685 " 1686 ::= { mvpnMrouteEntry 21 } 1688 mvpnMrouteDroppedInPackets OBJECT-TYPE 1689 SYNTAX Counter64 1690 MAX-ACCESS read-only 1691 STATUS current 1692 DESCRIPTION 1693 "The number of packets which this router has received from 1694 sources represented by this entry and addressed to this 1695 multicast group address, which were dropped due to error(s). 1696 The value of this object includes the number of octets 1697 counted in the corresponding mvpnMrouteTtlDroppedPackets 1698 object. 1700 Discontinuities in the value of this counter can 1701 occur at re-initialization of the management system, 1702 and at other times as indicated by the corresponding 1703 mvpnMrouteCounterDiscontinuityTime object. 1704 " 1705 ::= { mvpnMrouteEntry 22 } 1707 mvpnMroutePmsiPointer OBJECT-TYPE 1708 SYNTAX RowPointer 1709 MAX-ACCESS read-only 1710 STATUS current 1711 DESCRIPTION 1712 "A pointer to a conceptual row representing 1713 the corresponding I-PMSI in mvpnPmsiTable or S-PMSI 1714 in mvpnSpmsiTable, that this C-multicast route is using. 1715 " 1716 ::= { mvpnMrouteEntry 23 } 1718 mvpnMrouteNumberOfLocalReplication OBJECT-TYPE 1719 SYNTAX Unsigned32 1720 MAX-ACCESS read-only 1721 STATUS current 1722 DESCRIPTION 1723 "Number of replications for local receivers. 1724 For example, if an ingress PE needs to send traffic out of 1725 N PE-CE interfaces, then mvpnMrouteNumberOfLocalReplication 1726 is N. 1727 " 1728 ::= { mvpnMrouteEntry 24 } 1730 mvpnMrouteNumberOfRemoteReplication OBJECT-TYPE 1731 SYNTAX Unsigned32 1732 MAX-ACCESS read-only 1733 STATUS current 1734 DESCRIPTION 1735 "Number of local replications for remote PEs. For example, 1736 if the number of remote PEs that need to receive traffic is N, 1737 then mvpnMrouteNumberOfRemoteReplication is N in case of 1738 Ingress Replication, but may be less than N in case of RSVP-TE 1739 or mLDP P2MP tunnels, depending on the actual number of 1740 replications the PE needs to do. 1741 " 1742 ::= { mvpnMrouteEntry 25 } 1744 mvpnMrouteCounterDiscontinuityTime OBJECT-TYPE 1745 SYNTAX TimeStamp 1746 MAX-ACCESS read-only 1747 STATUS current 1748 DESCRIPTION 1749 "The value of sysUpTime on the most recent occasion 1750 at which any one or more of this application's 1751 counters, viz., counters with OID prefix 1752 'mvpnMrouteOctets' or 'mvpnMroutePkts' or 1753 'mvpnMrouteTtlDroppedOctets' or 1754 'mvpnMrouteTtlDroppedPackets' or 1755 'mvpnMrouteDroppedInOctets' or 'mvpnMrouteDroppedInPackets' 1756 suffered a discontinuity. 1757 If no such discontinuities have occurred since the 1758 last re-initialization of the local management 1759 subsystem, then this object will have a zero value. 1760 " 1761 ::= { mvpnMrouteEntry 26 } 1763 -- Table of next hops for multicast routes in an MVPN 1765 mvpnMrouteNextHopTable OBJECT-TYPE 1766 SYNTAX SEQUENCE OF MvpnMrouteNextHopEntry 1767 MAX-ACCESS not-accessible 1768 STATUS current 1769 DESCRIPTION 1770 "A conceptual table containing information on the 1771 next-hops for routing IP multicast datagrams. 1772 Each entry is one of a list of next-hops for 1773 a set of sources sending to a multicast group 1774 address. 1775 " 1776 ::= { mvpnObjects 8 } 1778 mvpnMrouteNextHopEntry OBJECT-TYPE 1779 SYNTAX MvpnMrouteNextHopEntry 1780 MAX-ACCESS not-accessible 1781 STATUS current 1782 DESCRIPTION 1783 "A conceptual row corresponding to a next-hop to which 1784 IP multicast datagrams from a set of sources to 1785 an IP multicast group address are routed. 1787 Implementers need to be aware that if the total number of 1788 octets in mplsL3VpnVrfName, mvpnMrouteNextHopGroupAddr, 1789 mvpnMrouteNextHopSourceAddrs, and mvpnMrouteNextHopAddr 1790 exceeds 111, the OIDs of column instances in this row 1791 will have more than 128 sub-identifiers and cannot be 1792 accessed using SNMPv1, SNMPv2c, or SNMPv3. 1793 " 1794 INDEX { 1795 mplsL3VpnVrfName, 1796 mvpnMrouteNextHopGroupAddrType, 1797 mvpnMrouteNextHopGroupAddr, 1798 mvpnMrouteNextHopGroupPrefixLength, 1799 mvpnMrouteNextHopSourceAddrType, 1800 mvpnMrouteNextHopSourceAddrs, 1801 mvpnMrouteNextHopSourcePrefixLength, 1802 mvpnMrouteNextHopIfIndex, 1803 mvpnMrouteNextHopAddrType, 1804 mvpnMrouteNextHopAddr 1805 } 1806 ::= { mvpnMrouteNextHopTable 1 } 1808 MvpnMrouteNextHopEntry ::= SEQUENCE { 1809 mvpnMrouteNextHopGroupAddrType InetAddressType, 1810 mvpnMrouteNextHopGroupAddr InetAddress, 1811 mvpnMrouteNextHopGroupPrefixLength InetAddressPrefixLength, 1812 mvpnMrouteNextHopSourceAddrType InetAddressType, 1813 mvpnMrouteNextHopSourceAddrs InetAddress, 1814 mvpnMrouteNextHopSourcePrefixLength InetAddressPrefixLength, 1815 mvpnMrouteNextHopIfIndex InterfaceIndex, 1816 mvpnMrouteNextHopAddrType InetAddressType, 1817 mvpnMrouteNextHopAddr InetAddress, 1818 mvpnMrouteNextHopState INTEGER, 1819 mvpnMrouteNextHopExpiryTime TimeTicks, 1820 mvpnMrouteNextHopClosestMemberHops Unsigned32, 1821 mvpnMrouteNextHopProtocol IANAipMRouteProtocol, 1822 mvpnMrouteNextHopOctets Counter64, 1823 mvpnMrouteNextHopPkts Counter64, 1824 mvpnMrouteNextHopCounterDiscontinuityTime TimeStamp 1825 } 1826 mvpnMrouteNextHopGroupAddrType OBJECT-TYPE 1827 SYNTAX InetAddressType 1828 MAX-ACCESS not-accessible 1829 STATUS current 1830 DESCRIPTION 1831 "The InetAddressType of the mvpnMrouteNextHopGroupAddr object 1832 that follows. 1833 " 1834 ::= { mvpnMrouteNextHopEntry 1 } 1836 mvpnMrouteNextHopGroupAddr OBJECT-TYPE 1837 SYNTAX InetAddress 1838 MAX-ACCESS not-accessible 1839 STATUS current 1840 DESCRIPTION 1841 "The IP multicast group address which, along with 1842 the corresponding mvpnMrouteNextHopGroupPrefixLength object, 1843 identifies destinations for which this entry contains 1844 multicast forwarding information. 1846 This address object is only significant up to 1847 mvpnMrouteNextHopGroupPrefixLength bits. The remaining 1848 address bits MUST be set to zero. 1850 For addresses of type 'ipv4z' or 'ipv6z', the appended zone 1851 index is significant even though it lies beyond the prefix 1852 length. The use of these address types indicate that this 1853 forwarding state applies only within the given zone. Zone 1854 index zero is not valid in this table. 1855 " 1856 ::= { mvpnMrouteNextHopEntry 2 } 1858 mvpnMrouteNextHopGroupPrefixLength OBJECT-TYPE 1859 SYNTAX InetAddressPrefixLength 1860 MAX-ACCESS not-accessible 1861 STATUS current 1862 DESCRIPTION 1863 "The length in bits of the mask which, along with 1864 the corresponding mvpnMrouteGroupAddr object, 1865 identifies destinations for which this entry contains 1866 multicast routing information. 1868 If the corresponding InetAddressType is 'ipv4' or 'ipv4z', 1869 this object must be in the range 4..32. 1870 If the corresponding InetAddressType is 'ipv6' or 'ipv6z', 1871 this object must be in the range 8..128. 1872 " 1873 ::= { mvpnMrouteNextHopEntry 3 } 1875 mvpnMrouteNextHopSourceAddrType OBJECT-TYPE 1876 SYNTAX InetAddressType 1877 MAX-ACCESS not-accessible 1878 STATUS current 1879 DESCRIPTION 1880 "The InetAddressType of mvpnMrouteNextHopSourceAddrs object 1881 that follows. 1883 A value of unknown(0) indicates a non-source-specific entry, 1884 corresponding to all sources in the group. Otherwise, the 1885 value MUST be the same as the value of 1886 mvpnMrouteNextHopGroupAddrType." 1887 ::= { mvpnMrouteNextHopEntry 4 } 1889 mvpnMrouteNextHopSourceAddrs OBJECT-TYPE 1890 SYNTAX InetAddress 1891 MAX-ACCESS not-accessible 1892 STATUS current 1893 DESCRIPTION 1894 "The network address which, along with the 1895 corresponding mvpnMrouteNextHopSourcePrefixLength object, 1896 identifies the sources for which this entry specifies 1897 a next-hop. 1899 This address object is only significant up to 1900 mvpnMrouteNextHopSourcePrefixLength bits. The remaining 1901 address bits MUST be set to zero. 1903 For addresses of type 'ipv4z' or 'ipv6z', the appended zone 1904 index is significant even though it lies beyond the prefix 1905 length. The use of these address types indicate that this 1906 source address applies only within the given zone. Zone 1907 index zero is not valid in this table. 1908 " 1909 ::= { mvpnMrouteNextHopEntry 5 } 1911 mvpnMrouteNextHopSourcePrefixLength OBJECT-TYPE 1912 SYNTAX InetAddressPrefixLength 1913 MAX-ACCESS not-accessible 1914 STATUS current 1915 DESCRIPTION 1916 "The length in bits of the mask which, along with 1917 the corresponding mvpnMrouteNextHopSourceAddrs object, 1918 identifies the sources for which this entry specifies 1919 a next-hop. 1921 If the corresponding InetAddressType is 'ipv4' or 'ipv4z', 1922 this object must be in the range 4..32. 1924 If the corresponding InetAddressType is 'ipv6' or 'ipv6z', 1925 this object must be in the range 8..128. 1926 If the corresponding InetAddressType is 'unknown', 1927 this object must be zero. 1928 " 1929 ::= { mvpnMrouteNextHopEntry 6 } 1931 mvpnMrouteNextHopIfIndex OBJECT-TYPE 1932 SYNTAX InterfaceIndex 1933 MAX-ACCESS not-accessible 1934 STATUS current 1935 DESCRIPTION 1936 "The ifIndex value of the outgoing interface 1937 for this next-hop. 1938 " 1939 ::= { mvpnMrouteNextHopEntry 7 } 1941 mvpnMrouteNextHopAddrType OBJECT-TYPE 1942 SYNTAX InetAddressType 1943 MAX-ACCESS not-accessible 1944 STATUS current 1945 DESCRIPTION 1946 "The InetAddressType of the mvpnMrouteNextHopAddr object 1947 that follows. 1948 " 1949 ::= { mvpnMrouteNextHopEntry 8 } 1951 mvpnMrouteNextHopAddr OBJECT-TYPE 1952 SYNTAX InetAddress 1953 MAX-ACCESS not-accessible 1954 STATUS current 1955 DESCRIPTION 1956 "The address of the next-hop specific to this entry. For 1957 most interfaces, this is identical to 1958 mvpnMrouteNextHopGroupAddr. Non-Broadcast Multi-Access 1959 (NBMA) interfaces, however, may have multiple next-hop 1960 addresses out of a single outgoing interface. 1961 " 1962 ::= { mvpnMrouteNextHopEntry 9 } 1964 mvpnMrouteNextHopState OBJECT-TYPE 1965 SYNTAX INTEGER { 1966 pruned(1), 1967 forwarding(2) 1968 } 1969 MAX-ACCESS read-only 1970 STATUS current 1971 DESCRIPTION 1972 "An indication of whether the outgoing interface and next- 1973 hop represented by this entry is currently being used to 1974 forward IP datagrams. 1976 The enumerated states and the corresponding 1977 descriptions are as follows: 1979 pruned : this entry is not currently being used. 1980 forwarding : this entry is currently being used. 1981 " 1982 ::= { mvpnMrouteNextHopEntry 10 } 1984 mvpnMrouteNextHopExpiryTime OBJECT-TYPE 1985 SYNTAX TimeTicks 1986 MAX-ACCESS read-only 1987 STATUS current 1988 DESCRIPTION 1989 "The minimum amount of time remaining before this entry will 1990 be aged out. If mvpnMrouteNextHopState is pruned(1), 1991 this object represents the remaining time for the prune 1992 to expire after which the state will return to forwarding(2). 1993 If mvpnMrouteNextHopState is forwarding(2), 1994 this object indicates the time after which this 1995 entry will be removed from the table. 1997 The value of 0 indicates that the entry is not subject to 1998 aging. 1999 " 2000 ::= { mvpnMrouteNextHopEntry 11 } 2002 mvpnMrouteNextHopClosestMemberHops OBJECT-TYPE 2003 SYNTAX Unsigned32 (0..256) 2004 MAX-ACCESS read-only 2005 STATUS current 2006 DESCRIPTION 2007 "The minimum number of hops between this router and any 2008 member of this IP multicast group reached via this next-hop 2009 on the corresponding outgoing interface. Any IP multicast 2010 datagram for the group that has a TTL (IPv4) or Hop Count 2011 (IPv6) less than mvpnMrouteNextHopClosestMemberHops will 2012 not be forwarded through this interface. 2014 A value of 0 means all multicast datagrams are forwarded out 2015 of the interface. A value of 256 means that no multicast 2016 datagrams are forwarded out of the interface. 2018 This is an optimization applied by multicast routing 2019 protocols that explicitly track hop counts to downstream 2020 listeners. Multicast protocols that are not aware of hop 2021 counts to downstream listeners set this object to 0. 2022 " 2023 ::= { mvpnMrouteNextHopEntry 12 } 2025 mvpnMrouteNextHopProtocol OBJECT-TYPE 2026 SYNTAX IANAipMRouteProtocol 2027 MAX-ACCESS read-only 2028 STATUS current 2029 DESCRIPTION 2030 "The routing protocol via which this next-hop was learned." 2031 ::= { mvpnMrouteNextHopEntry 13 } 2033 mvpnMrouteNextHopOctets OBJECT-TYPE 2034 SYNTAX Counter64 2035 MAX-ACCESS read-only 2036 STATUS current 2037 DESCRIPTION 2038 "The number of octets of multicast packets that have been 2039 forwarded using this route. 2041 Discontinuities in the value of this counter can 2042 occur at re-initialization of the management system, 2043 and at other times as indicated by the corresponding 2044 mvpnMrouteNextHopCounterDiscontinuityTime object. 2045 " 2046 ::= { mvpnMrouteNextHopEntry 14 } 2048 mvpnMrouteNextHopPkts OBJECT-TYPE 2049 SYNTAX Counter64 2050 MAX-ACCESS read-only 2051 STATUS current 2052 DESCRIPTION 2053 "The number of packets which have been forwarded using this 2054 route. 2056 Discontinuities in the value of this counter can 2057 occur at re-initialization of the management system, 2058 and at other times as indicated by the corresponding 2059 mvpnMrouteNextHopCounterDiscontinuityTime object. 2060 " 2061 ::= { mvpnMrouteNextHopEntry 15 } 2063 mvpnMrouteNextHopCounterDiscontinuityTime OBJECT-TYPE 2064 SYNTAX TimeStamp 2065 MAX-ACCESS read-only 2066 STATUS current 2067 DESCRIPTION 2068 "The value of sysUpTime on the most recent occasion 2069 at which any one or more of this application's 2070 counters, viz., counters with OID prefix 2071 'mvpnMrouteNextHopOctets' or 'mvpnMrouteNextHopPackets' 2072 suffered a discontinuity. 2073 If no such discontinuities have occurred since the 2074 last re-initialization of the local management 2075 subsystem, then this object will have a zero value. 2076 " 2077 ::= { mvpnMrouteNextHopEntry 16 } 2079 -- MVPN Notifications 2081 mvpnMvrfActionTaken NOTIFICATION-TYPE 2082 OBJECTS { 2083 mvpnGenMvrfCreationTime, 2084 mvpnGenMvrfLastAction, 2085 mvpnGenMvrfLastActionTime, 2086 mvpnGenMvrfCreationTime, 2087 mvpnGenCmcastRouteProtocol, 2088 mvpnGenUmhSelection, 2089 mvpnGenCustomerSiteType 2090 } 2091 STATUS current 2092 DESCRIPTION 2093 "mvpnMvrfActionTaken notifies about a change 2094 in a MVRF on the PE. The change itself will be given by 2095 mvpnGenMvrfLastAction. 2096 " 2097 ::= { mvpnNotifications 1 } 2099 -- MVPN MIB Conformance Information 2101 mvpnGroups OBJECT IDENTIFIER ::= { mvpnConformance 1 } 2102 mvpnCompliances OBJECT IDENTIFIER ::= { mvpnConformance 2 } 2104 -- Compliance Statements 2106 mvpnModuleFullCompliance MODULE-COMPLIANCE 2107 STATUS current 2108 DESCRIPTION 2109 "Compliance statement for agents that provide full support 2110 for the MCAST-VPN-MIB 2111 " 2112 MODULE -- this module 2113 MANDATORY-GROUPS { 2114 mvpnScalarGroup, 2115 mvpnGenericGroup, 2116 mvpnPmsiGroup, 2117 mvpnAdvtStatsGroup, 2118 mvpnMrouteGroup, 2119 mvpnMrouteNextHopGroup, 2120 mvpnNotificationGroup 2121 } 2123 GROUP mvpnBgpScalarGroup 2124 DESCRIPTION 2125 "This group is mandatory for systems that support 2126 BGP-MVPN. 2127 " 2129 GROUP mvpnBgpGroup 2130 DESCRIPTION 2131 "This group is mandatory for systems that support 2132 BGP-MVPN. 2133 " 2135 ::= { mvpnCompliances 1 } 2137 mvpnModuleReadOnlyCompliance MODULE-COMPLIANCE 2138 STATUS current 2139 DESCRIPTION "Compliance requirement for implementations that 2140 only provide read-only support for MCAST-VPN-MIB. 2141 Such devices can then be monitored but cannot be 2142 configured using this MIB module. 2143 " 2144 MODULE -- this module 2145 MANDATORY-GROUPS { 2146 mvpnScalarGroup, 2147 mvpnGenericGroup, 2148 mvpnPmsiGroup, 2149 mvpnAdvtStatsGroup, 2150 mvpnMrouteGroup, 2151 mvpnMrouteNextHopGroup, 2152 mvpnNotificationGroup 2153 } 2155 GROUP mvpnBgpScalarGroup 2156 DESCRIPTION 2157 "This group is mandatory for systems that support 2158 BGP-MVPN. 2159 " 2161 GROUP mvpnBgpGroup 2162 DESCRIPTION 2163 "This group is mandatory for systems that support 2164 BGP-MVPN. 2165 " 2167 OBJECT mvpnSPTunnelLimit 2168 MIN-ACCESS read-only 2169 DESCRIPTION "Write access is not required." 2171 OBJECT mvpnBgpCmcastRouteWithdrawalTimer 2172 MIN-ACCESS read-only 2173 DESCRIPTION "Write access is not required." 2175 OBJECT mvpnBgpSrcSharedTreeJoinTimer 2176 MIN-ACCESS read-only 2177 DESCRIPTION "Write access is not required." 2179 OBJECT mvpnBgpMsgRateLimit 2180 MIN-ACCESS read-only 2181 DESCRIPTION "Write access is not required." 2183 OBJECT mvpnBgpMaxSpmsiAdRoutes 2184 MIN-ACCESS read-only 2185 DESCRIPTION "Write access is not required." 2187 OBJECT mvpnBgpMaxSpmsiAdRouteFreq 2188 MIN-ACCESS read-only 2189 DESCRIPTION "Write access is not required." 2191 OBJECT mvpnBgpMaxSrcActiveAdRoutes 2192 MIN-ACCESS read-only 2193 DESCRIPTION "Write access is not required." 2195 OBJECT mvpnBgpMaxSrcActiveAdRouteFreq 2196 MIN-ACCESS read-only 2197 DESCRIPTION "Write access is not required." 2199 ::= { mvpnCompliances 2 } 2201 mvpnModuleAdvtStatsCompliance MODULE-COMPLIANCE 2202 STATUS current 2203 DESCRIPTION 2204 "Compliance statement for agents that support 2205 monitoring of the statistics pertaining to 2206 advertisements sent/received by a PE. 2207 " 2208 MODULE -- this module 2209 MANDATORY-GROUPS { 2210 mvpnAdvtStatsGroup 2212 } 2214 ::= { mvpnCompliances 3 } 2216 -- units of conformance 2218 mvpnScalarGroup OBJECT-GROUP 2219 OBJECTS { 2220 mvpnMvrfs, 2221 mvpnV4Mvrfs, 2222 mvpnV6Mvrfs, 2223 mvpnPimV4Mvrfs, 2224 mvpnPimV6Mvrfs, 2225 mvpnSPTunnelLimit 2226 } 2227 STATUS current 2228 DESCRIPTION 2229 "These objects are used to monitor/manage 2230 global statistics and parameters. 2231 " 2232 ::= { mvpnGroups 1 } 2234 mvpnBgpScalarGroup OBJECT-GROUP 2235 OBJECTS { 2236 mvpnMldpMvrfs, 2237 mvpnBgpV4Mvrfs, 2238 mvpnBgpV6Mvrfs, 2239 mvpnBgpCmcastRouteWithdrawalTimer, 2240 mvpnBgpSrcSharedTreeJoinTimer 2241 } 2242 STATUS current 2243 DESCRIPTION 2244 "These objects are used to monitor/manage 2245 BGP-MVPN specific global parameters. 2246 " 2247 ::= { mvpnGroups 2 } 2249 mvpnGenericGroup OBJECT-GROUP 2250 OBJECTS { 2251 mvpnGenMvrfLastAction, 2252 mvpnGenMvrfLastActionTime, 2253 mvpnGenMvrfCreationTime, 2254 mvpnGenCmcastRouteProtocol, 2255 mvpnGenIpmsiInfo, 2256 mvpnGenInterAsPmsiInfo, 2257 mvpnGenUmhSelection, 2258 mvpnGenCustomerSiteType 2259 } 2261 STATUS current 2262 DESCRIPTION 2263 "These objects are used to monitor MVPNs on a PE. 2264 " 2265 ::= { mvpnGroups 3 } 2267 mvpnBgpGroup OBJECT-GROUP 2268 OBJECTS { 2269 mvpnBgpMode, 2270 mvpnBgpVrfRouteImportExtendedCommunity, 2271 mvpnBgpSrcASExtendedCommunity, 2272 mvpnBgpMsgRateLimit, 2273 mvpnBgpMaxSpmsiAdRoutes, 2274 mvpnBgpMaxSpmsiAdRouteFreq, 2275 mvpnBgpMaxSrcActiveAdRoutes, 2276 mvpnBgpMaxSrcActiveAdRouteFreq 2277 } 2278 STATUS current 2279 DESCRIPTION 2280 "These objects are used to monitor/manage 2281 the MVPN-wise BGP specific parameters. 2282 " 2283 ::= { mvpnGroups 4 } 2285 mvpnPmsiGroup OBJECT-GROUP 2286 OBJECTS { 2287 mvpnPmsiRD, 2288 mvpnPmsiTunnelType, 2289 mvpnPmsiTunnelAttribute, 2290 mvpnPmsiTunnelPimGroupAddrType, 2291 mvpnPmsiTunnelPimGroupAddr, 2292 mvpnPmsiEncapsulationType, 2293 mvpnSpmsiPmsiPointer 2294 } 2295 STATUS current 2296 DESCRIPTION 2297 "These objects are used to monitor 2298 I-PMSIs and S-PMSIs tunnel on a PE. 2299 " 2300 ::= { mvpnGroups 5 } 2302 mvpnAdvtStatsGroup OBJECT-GROUP 2303 OBJECTS { 2304 mvpnAdvtSent, 2305 mvpnAdvtReceived, 2306 mvpnAdvtReceivedError, 2307 mvpnAdvtReceivedMalformedTunnelType, 2308 mvpnAdvtReceivedMalformedTunnelId, 2309 mvpnAdvtLastSentTime, 2310 mvpnAdvtLastReceivedTime, 2311 mvpnAdvtCounterDiscontinuityTime 2312 } 2313 STATUS current 2314 DESCRIPTION 2315 "These objects are used to monitor 2316 the statistics pertaining to I-PMSI and S-PMSI 2317 advertisements sent/received by a PE. 2318 " 2319 ::= { mvpnGroups 6 } 2321 mvpnMrouteGroup OBJECT-GROUP 2322 OBJECTS { 2323 mvpnMrouteUpstreamNeighborAddrType, 2324 mvpnMrouteUpstreamNeighborAddr, 2325 mvpnMrouteInIfIndex, 2326 mvpnMrouteExpiryTime, 2327 mvpnMrouteProtocol, 2328 mvpnMrouteRtProtocol, 2329 mvpnMrouteRtAddrType, 2330 mvpnMrouteRtAddr, 2331 mvpnMrouteRtPrefixLength, 2332 mvpnMrouteRtType, 2333 mvpnMrouteOctets, 2334 mvpnMroutePkts, 2335 mvpnMrouteTtlDroppedOctets, 2336 mvpnMrouteTtlDroppedPackets, 2337 mvpnMrouteDroppedInOctets, 2338 mvpnMrouteDroppedInPackets, 2339 mvpnMroutePmsiPointer, 2340 mvpnMrouteNumberOfLocalReplication, 2341 mvpnMrouteNumberOfRemoteReplication, 2342 mvpnMrouteCounterDiscontinuityTime 2343 } 2344 STATUS current 2345 DESCRIPTION 2346 "These objects are used to monitor multicast routing 2347 information corresponding to the MVRFs on a PE. 2348 " 2349 ::= { mvpnGroups 7 } 2351 mvpnMrouteNextHopGroup OBJECT-GROUP 2352 OBJECTS { 2353 mvpnMrouteNextHopState, 2354 mvpnMrouteNextHopExpiryTime, 2355 mvpnMrouteNextHopClosestMemberHops, 2356 mvpnMrouteNextHopProtocol, 2357 mvpnMrouteNextHopOctets, 2358 mvpnMrouteNextHopPkts, 2359 mvpnMrouteNextHopCounterDiscontinuityTime 2360 } 2361 STATUS current 2362 DESCRIPTION 2363 "These objects are used to monitor the information on 2364 next-hops for routing datagrams to MVPNs on a PE. 2365 " 2366 ::= { mvpnGroups 8 } 2368 mvpnNotificationGroup NOTIFICATION-GROUP 2369 NOTIFICATIONS { 2370 mvpnMvrfActionTaken 2371 } 2372 STATUS current 2373 DESCRIPTION 2374 "Objects required for MVPN notifications." 2375 ::= { mvpnGroups 9 } 2377 END 2379 4. Security Considerations 2381 This MIB module contains some read-only objects that may be deemed 2382 senstive. It also contains some read-write objects, whose setting 2383 will change the device's MVPN related behavior. Appropriate security 2384 procedures related to SNMP in general but not specific to this MIB 2385 module need to be implemented by concerned operators. 2387 There are a number of management objects defined in this MIB module 2388 with a MAX-ACCESS clause of read-write. Such objects may be 2389 considered sensitive or vulnerable in some network environments. The 2390 support for SET operations in a non-secure environment without proper 2391 protection opens devices to attack. These are the tables and objects 2392 and their sensitivity/vulnerability: 2394 o mvpnSPTunnelLimit 2396 The value of this object is used to control the maximum number of 2397 selective provider tunnels that a PE allows for a particular MVPN. 2398 Access to this object may be abused to impact the peformance of 2399 the PE or prevent the PE from having new selective provider 2400 tunnels. 2402 o mvpnBgpCmcastRouteWithdrawalTimer 2403 The value of this object is used to control the delay for the 2404 advertisement of withdrawals of C-multicast routes. Access to 2405 this object may be abused to impact the peformance of a PE. 2407 o mvpnBgpSrcSharedTreeJoinTimer 2409 The value of this object is used to control the delay for the 2410 advertisement of Source/Shared Tree Join C-multicast routes. 2411 Access to this object may be abused to impact the propagation of 2412 C-multicast routing information. 2414 o mvpnBgpMsgRateLimit 2416 The value of this object is used to control the upper bound for 2417 the rate of BGP C-multicast routing information message exchange 2418 among PEs. Access to this object may be abused to impact the 2419 peformance of the PE or disrupt the C-multicast routing 2420 information message exchange using BGP. 2422 o mvpnBgpMaxSpmsiAdRoutes 2424 The value of this object is used to control the upper bound for 2425 the number of S-PMSI A-D routes. Access to this object may be 2426 abused to impact the peformance of the PE or prevent the PE from 2427 receiving S-PMSI A-D routes. 2429 o mvpnBgpMaxSpmsiAdRouteFreq 2431 The value of this object is used to control the upper bound for 2432 the frequency of S-PMSI A-D route generation. Access to this 2433 object may be abused to impact the peformance of the PE or prevent 2434 the PE from generating new S-PMSI A-D routes. 2436 o mvpnBgpMaxSrcActiveAdRoutes 2438 The value of this object is used to control the upper bound for 2439 the number of Source Active A-D routes. Access to this object may 2440 be abused to impact the peformance of the PE or prevent the PE 2441 from receiving Source Active A-D routes. 2443 o mvpnBgpMaxSrcActiveAdRouteFreq 2445 The value of this object is used to control the upper bound for 2446 the frequency of Source Active A-D route generation. Access to 2447 this object may be abused to impact the peformance of the PE or 2448 prevent the PE from generating new Source Active A-D routes. 2450 Some of the readable objects in this MIB module (i.e., objects with a 2451 MAX-ACCESS other than not-accessible) may be considered sensitive or 2452 vulnerable in some network environments. It is thus important to 2453 control even GET and/or NOTIFY access to these objects and possibly 2454 to even encrypt the values of these objects when sending them over 2455 the network via SNMP. These are the tables and objects and their 2456 sensitivity/vulnerability: 2458 o The address-related objects in this MIB module may have impact on 2459 privacy and security. These objects may reveal the locations of 2460 senders and recipients. 2462 * mvpnPmsiTunnelPimGroupAddr 2464 * mvpnSpmsiCmcastGroupAddr 2466 * mvpnSpmsiCmcastSourceAddr 2468 * mvpnAdvtPeerAddr 2470 * mvpnMrouteCmcastGroupAddr 2472 * mvpnMrouteCmcastSourceAddrs 2474 * mvpnMrouteUpstreamNeighborAddr 2476 * mvpnMrouteNextHopGroupAddr 2478 * mvpnMrouteNextHopSourceAddrs 2480 * mvpnMrouteNextHopAddr 2482 SNMP versions prior to SNMPv3 did not include adequate security. 2483 Even if the network itself is secure (for example by using IPsec), 2484 there is no control as to who on the secure network is allowed to 2485 access and GET/SET (read/change/create/delete) the objects in this 2486 MIB module. 2488 Implementations SHOULD provide the security features described by the 2489 SNMPv3 framework (see [RFC3410]), and implementations claiming 2490 compliance to the SNMPv3 standard MUST include full support for 2491 authentication and privacy via the User-based Security Model (USM) 2492 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 2493 MAY also provide support for the Transport Security Model (TSM) 2494 [RFC5591] in combination with a secure transport such as SSH 2495 [RFC5592] or TLS/DTLS [RFC6353]. 2497 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2498 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2499 enable cryptographic security. It is then a customer/operator 2500 responsibility to ensure that the SNMP entity giving access to an 2501 instance of this MIB module is properly configured to give access to 2502 the objects only to those principals (users) that have legitimate 2503 rights to indeed GET or SET (change/create/delete) them. 2505 5. IANA Considerations 2507 The MIB module in this document uses the following IANA-assigned 2508 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 2510 Descriptor OBJECT IDENTIFIER value 2511 ---------- ----------------------- 2512 mvpnMIB { mib-2 YYYY } 2514 Editor's Note (to be removed prior to publication): the IANA is 2515 requested to assign a value for "YYYY" under the 'mib-2' subtree and 2516 to record the assignment in the SMI Numbers registry. When the 2517 assignment has been made, the RFC Editor is asked to replace "YYYY" 2518 (here and in the MIB module) with the assigned value and to remove 2519 this note. 2521 6. Acknowledgement 2523 An earlier draft version of this document was coauthored by Zhaohui 2524 (Jeffrey) Zhang, Saud Asif, Andy Green, Sameer Gulrajani, and Pradeep 2525 G. Jain, based on an earlier draft written by Susheela Vaidya, 2526 Thomas D. Nadeau, and Harmen Van der Linde. 2528 This document also borrows heavily from the design and descriptions 2529 of ipMcastRouteTable and ipMcastRouteNextHopTable from IPMCAST- 2530 MIB[RFC5132]. 2532 Glenn Mansfield Keeni did the MIB Doctor review and provided valuable 2533 comments. 2535 7. References 2537 7.1. Normative References 2539 [RFC2003] Perkins, C., "IP Encapsulation within IP", RFC 2003, DOI 2540 10.17487/RFC2003, October 1996, . 2543 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2544 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 2545 RFC2119, March 1997, . 2548 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2549 Schoenwaelder, Ed., "Structure of Management Information 2550 Version 2 (SMIv2)", STD 58, RFC 2578, DOI 10.17487/ 2551 RFC2578, April 1999, . 2554 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2555 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 2556 58, RFC 2579, DOI 10.17487/RFC2579, April 1999, 2557 . 2559 [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2560 Schoenwaelder, Ed., "Conformance Statements for SMIv2", 2561 STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999, 2562 . 2564 [RFC2784] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. 2565 Traina, "Generic Routing Encapsulation (GRE)", RFC 2784, 2566 DOI 10.17487/RFC2784, March 2000, . 2569 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 2570 MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000, 2571 . 2573 [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., 2574 Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack 2575 Encoding", RFC 3032, DOI 10.17487/RFC3032, January 2001, 2576 . 2578 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 2579 (USM) for version 3 of the Simple Network Management 2580 Protocol (SNMPv3)", STD 62, RFC 3414, DOI 10.17487/ 2581 RFC3414, December 2002, . 2584 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 2585 Advanced Encryption Standard (AES) Cipher Algorithm in the 2586 SNMP User-based Security Model", RFC 3826, DOI 10.17487/ 2587 RFC3826, June 2004, . 2590 [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private 2591 Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February 2592 2006, . 2594 [RFC4382] Nadeau, T., Ed. and H. van der Linde, Ed., "MPLS/BGP Layer 2595 3 Virtual Private Network (VPN) Management Information 2596 Base", RFC 4382, DOI 10.17487/RFC4382, February 2006, 2597 . 2599 [RFC4659] De Clercq, J., Ooms, D., Carugi, M., and F. Le Faucheur, 2600 "BGP-MPLS IP Virtual Private Network (VPN) Extension for 2601 IPv6 VPN", RFC 4659, DOI 10.17487/RFC4659, September 2006, 2602 . 2604 [RFC5132] McWalter, D., Thaler, D., and A. Kessler, "IP Multicast 2605 MIB", RFC 5132, DOI 10.17487/RFC5132, December 2007, 2606 . 2608 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 2609 for the Simple Network Management Protocol (SNMP)", STD 2610 78, RFC 5591, DOI 10.17487/RFC5591, June 2009, 2611 . 2613 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 2614 Shell Transport Model for the Simple Network Management 2615 Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June 2616 2009, . 2618 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 2619 Model for the Simple Network Management Protocol (SNMP)", 2620 STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011, 2621 . 2623 [RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/ 2624 BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February 2625 2012, . 2627 [RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP 2628 Encodings and Procedures for Multicast in MPLS/BGP IP 2629 VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012, 2630 . 2632 [RFC6625] Rosen, E., Ed., Rekhter, Y., Ed., Hendrickx, W., and R. 2633 Qiu, "Wildcards in Multicast VPN Auto-Discovery Routes", 2634 RFC 6625, DOI 10.17487/RFC6625, May 2012, 2635 . 2637 [RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I., 2638 Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent 2639 Multicast - Sparse Mode (PIM-SM): Protocol Specification 2640 (Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March 2641 2016, . 2643 [RTPROTO] IANA, "IP Route Protocol MIB", 2016, 2644 . 2646 7.2. Informative References 2648 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2649 "Introduction and Applicability Statements for Internet- 2650 Standard Management Framework", RFC 3410, DOI 10.17487/ 2651 RFC3410, December 2002, . 2654 Author's Address 2656 Hiroshi Tsunoda 2657 Tohoku Institute of Technology 2658 35-1, Yagiyama Kasumi-cho, Taihaku-ku 2659 Sendai 982-8577 2660 Japan 2662 Phone: +81-22-305-3411 2663 Email: tsuno@m.ieice.org