idnits 2.17.1 draft-ietf-bess-mvpn-mib-12.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 date (September 17, 2018) is 2047 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'RTPROTO' Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 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 September 17, 2018 5 Expires: March 21, 2019 7 BGP/MPLS Layer 3 VPN Multicast Management Information Base 8 draft-ietf-bess-mvpn-mib-12 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 March 21, 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. BGP-MPLS-LAYER3-VPN-MULTICAST-MIB . . . . . . . . . . . . . . 4 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 . . . . . . . . . . . . . . . . . . . . . . . . . 54 63 7.1. Normative References . . . . . . . . . . . . . . . . . . 54 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", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 120 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 121 "OPTIONAL" in this document are to be interpreted as described in BCP 122 14 [RFC2119] [RFC8174] when, and only when, they appear in all 123 capitals, as shown here. 125 2. The Internet-Standard Management Framework 127 For a detailed overview of the documents that describe the current 128 Internet-Standard Management Framework, please refer to section 7 of 129 RFC 3410 [RFC3410]. 131 Managed objects are accessed via a virtual information store, termed 132 the Management Information Base or MIB. MIB objects are generally 133 accessed through the Simple Network Management Protocol (SNMP). 134 Objects in the MIB are defined using the mechanisms defined in the 135 Structure of Management Information (SMI). This memo specifies a MIB 136 module that is compliant to the SMIv2, which is described in STD 58, 137 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 138 [RFC2580]. 140 3. BGP-MPLS-LAYER3-VPN-MULTICAST-MIB 142 This document defines BGP-MPLS-LAYER3-VPN-MULTICAST-MIB, a MIB module 143 for monitoring and/or configuring MVPNs on PEs. This MIB module will 144 be used in conjunction with MPLS-L3VPN-STD-MIB [RFC4382] and IPMCAST- 145 MIB [RFC5132]. 147 3.1. Summary of MIB Module 149 BGP-MPLS-LAYER3-VPN-MULTICAST-MIB provides the following 150 functionalities. 152 o Monitoring attributes of MVPNs on a PE 154 o Configuring timers and thresholds related to an MVPN on a PE 156 o Notifying creation, deletion, and modification of MVRFs on a PE 158 o Monitoring PMSI attributes 160 o Monitoring statistics of advertisements exchanged by a PE 162 o Monitoring routing information for multicast destinations 164 o Monitoring next-hops for each multicast destination 166 To provide these functionalities, BGP-MPLS-LAYER3-VPN-MULTICAST-MIB 167 defines following tables. 169 o mvpnGenericTable 171 This table contains generic information about MVPNs on a PE. Each 172 entry in this table represents an instance of an MVPN on a PE and 173 contains generic information related to the MVPN. For each entry 174 in this table there MUST be a corresponding VRF in MPLS-L3VPN-STD- 175 MIB [RFC4382]. 177 o mvpnBgpTable 179 This table contains information specific to BGP-MVPNs. Each BGP- 180 MVPN on a PE will have an entry in this table. 182 o mvpnPmsiTable 184 This table contains managed objects representing attribute 185 information that is common to I-PMSIs and S-PMSIs on a PE. 187 o mvpnSpmsiTable 188 This table contains managed objects representing attribute 189 information specific to S-PMSIs. An S-PMSI represented in this 190 table will have a corresponding entry in mvpnPmsiTable. 192 o mvpnAdvtStatsTable 194 This table contains statistics pertaining to I-PMSI and S-PMSI 195 advertisements sent/received. 197 o mvpnMrouteTable 199 This table contains multicast routing information in MVRFs on a 200 PE. 202 o mvpnMrouteNextHopTable 204 This table contains information on the next-hops for routing IP 205 multicast datagrams in MVPNs on a PE. 207 3.2. MIB Module Definitions 209 BGP-MPLS-LAYER3-VPN-MULTICAST-MIB DEFINITIONS ::= BEGIN 211 IMPORTS 212 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 213 Counter32, Counter64, Gauge32, Unsigned32, TimeTicks, 214 mib-2 215 FROM SNMPv2-SMI -- [RFC2578] 217 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 218 FROM SNMPv2-CONF -- [RFC2580] 220 RowPointer, TimeStamp, DateAndTime 221 FROM SNMPv2-TC -- [RFC2579] 223 InterfaceIndex, InterfaceIndexOrZero 224 FROM IF-MIB -- [RFC2863] 226 InetAddress, InetAddressType, InetAddressPrefixLength 227 FROM INET-ADDRESS-MIB -- [RFC4001] 229 mplsL3VpnVrfName, MplsL3VpnRouteDistinguisher 230 FROM MPLS-L3VPN-STD-MIB -- [RFC4382] 232 IANAipRouteProtocol, IANAipMRouteProtocol 233 FROM IANA-RTPROTO-MIB -- [RTPROTO] 235 L2L3VpnMcastProviderTunnelType 236 FROM L2L3-VPN-MULTICAST-TC-MIB; -- [RFCXXXX] 238 -- RFC Ed.: replace XXXX here and in the References Section 239 -- with the actual RFC number assigned to 240 -- I-D ietf-bess-l2l3-vpn-mcast-mib and remove this note. 242 mvpnMIB MODULE-IDENTITY 243 LAST-UPDATED "201809071200Z" -- 7th September 2018 12:00:00 GMT 244 ORGANIZATION "IETF BESS Working Group." 245 CONTACT-INFO 246 " Hiroshi Tsunoda 247 Tohoku Institute of Technology 248 35-1, Yagiyama Kasumi-cho 249 Taihaku-ku, Sendai, 982-8577 250 Japan 251 Email: tsuno@m.ieice.org 253 Comments and discussion to bess@ietf.org" 255 DESCRIPTION 256 "This MIB module contains managed object definitions to 257 configure and/or monitor Multicast communication over IP 258 Virtual Private Networks (VPNs) supported by MultiProtocol 259 Label Switching/Border Gateway Protocol (MPLS/BGP) on a 260 Provider Edge router (PE). 261 Copyright (C) The Internet Society (2018). 262 " 264 -- Revision history. 266 REVISION "201809071200Z" -- 7th September, 2018 267 DESCRIPTION 268 "Initial version, published as RFC YYYY." 270 -- RFC Ed.: replace YYYY with the actual RFC number and 271 -- remove this note 273 ::= { mib-2 AAAA } 275 -- IANA Reg.: Please assign a value for "AAAA" under the 276 -- 'mib-2' subtree and record the assignment in the SMI 277 -- Numbers registry. 279 -- RFC Ed.: When the above assignment has been made, please 280 -- remove the above note 281 -- replace "AAAA" here with the assigned value and 282 -- remove this note. 284 -- Top level components of this MIB module. 285 mvpnNotifications OBJECT IDENTIFIER ::= { mvpnMIB 0 } 287 -- scalars, tables 288 mvpnObjects OBJECT IDENTIFIER ::= { mvpnMIB 1 } 290 -- conformance information 291 mvpnConformance OBJECT IDENTIFIER ::= { mvpnMIB 2 } 293 -- mvpn Objects 294 mvpnScalars OBJECT IDENTIFIER ::= { mvpnObjects 1 } 296 -- Scalar Objects 298 mvpnMvrfs OBJECT-TYPE 299 SYNTAX Gauge32 300 MAX-ACCESS read-only 301 STATUS current 302 DESCRIPTION 303 "The total number of Multicast Virtual Routing and 304 Forwarding tables (MVRFs) that are present on 305 this Provider Edge router (PE). This includes MVRFs 306 for IPv4, IPv6, and mLDP C-Multicast. 307 " 308 ::= { mvpnScalars 1 } 310 mvpnV4Mvrfs OBJECT-TYPE 311 SYNTAX Gauge32 312 MAX-ACCESS read-only 313 STATUS current 314 DESCRIPTION 315 "The number of MVRFs for IPv4 C-Multicast on this PE. 316 " 317 ::= { mvpnScalars 2 } 319 mvpnV6Mvrfs OBJECT-TYPE 320 SYNTAX Gauge32 321 MAX-ACCESS read-only 322 STATUS current 323 DESCRIPTION 324 "The number of MVRFs for IPv6 C-Multicast on this PE. 325 " 326 ::= { mvpnScalars 3 } 328 mvpnMldpMvrfs OBJECT-TYPE 329 SYNTAX Gauge32 330 MAX-ACCESS read-only 331 STATUS current 332 DESCRIPTION 333 "The number of MVRFs on this PE that use BGP for 334 exchanging Multipoint Label Distribution Protocol (mLDP) 335 C-Multicast routing information. 336 " 337 ::= { mvpnScalars 4 } 339 mvpnPimV4Mvrfs OBJECT-TYPE 340 SYNTAX Gauge32 341 MAX-ACCESS read-only 342 STATUS current 343 DESCRIPTION 344 "The number of MVRFs on this PE that use Provider 345 Independent Multicast (PIM) for exchanging IPv4 346 C-Multicast routing information. 347 " 348 ::= { mvpnScalars 5 } 350 mvpnPimV6Mvrfs OBJECT-TYPE 351 SYNTAX Gauge32 352 MAX-ACCESS read-only 353 STATUS current 354 DESCRIPTION 355 "The number of MVRFs on this PE that use PIM for 356 exchanging IPv6 C-Multicast routing information. 357 " 358 ::= { mvpnScalars 6 } 360 mvpnBgpV4Mvrfs OBJECT-TYPE 361 SYNTAX Gauge32 362 MAX-ACCESS read-only 363 STATUS current 364 DESCRIPTION 365 "The number of MVRFs on this PE that use BGP for 366 exchanging IPv4 C-Multicast routing information. 367 " 368 ::= { mvpnScalars 7 } 370 mvpnBgpV6Mvrfs OBJECT-TYPE 371 SYNTAX Gauge32 372 MAX-ACCESS read-only 373 STATUS current 374 DESCRIPTION 375 "The number of MVRFs on this PE that use BGP for 376 exchanging IPv6 C-Multicast routing information. 377 " 378 ::= { mvpnScalars 8 } 380 mvpnSPTunnelLimit OBJECT-TYPE 381 SYNTAX Unsigned32 (1..4294967295) 382 MAX-ACCESS read-write 383 STATUS current 384 DESCRIPTION 385 "The maximum number of selective provider tunnels that 386 this PE allows for a particular MVPN on this PE. 387 " 388 REFERENCE 389 "RFC6513, Section 13" 390 ::= { mvpnScalars 9 } 392 mvpnBgpCmcastRouteWithdrawalTimer OBJECT-TYPE 393 SYNTAX Unsigned32 394 UNITS "milliseconds" 395 MAX-ACCESS read-write 396 STATUS current 397 DESCRIPTION 398 "A configurable timer to control the delay 399 of C-multicast route withdrawal advertisements. 400 " 401 REFERENCE 402 "RFC6514, Section 16.1.1" 403 ::= { mvpnScalars 10 } 405 mvpnBgpSrcSharedTreeJoinTimer OBJECT-TYPE 406 SYNTAX Unsigned32 407 UNITS "milliseconds" 408 MAX-ACCESS read-write 409 STATUS current 410 DESCRIPTION 411 "A configurable timer to control the delay 412 of Source/Shared Tree Join C-multicast route 413 advertisements. 414 " 415 REFERENCE 416 "RFC6514, Section 16.1.2" 417 ::= { mvpnScalars 11 } 419 -- Generic MVRF Information Table 421 mvpnGenericTable OBJECT-TYPE 422 SYNTAX SEQUENCE OF MvpnGenericEntry 423 MAX-ACCESS not-accessible 424 STATUS current 425 DESCRIPTION 426 "A conceptual table containing generic information about MVPNs 427 on this PE. 429 " 430 ::= { mvpnObjects 2 } 432 mvpnGenericEntry OBJECT-TYPE 433 SYNTAX MvpnGenericEntry 434 MAX-ACCESS not-accessible 435 STATUS current 436 DESCRIPTION 437 "A conceptual row that represents an MVPN on this PE. 438 The MVPN represented by this entry will have one or more 439 corresponding P-Multicast Service Interfaces (PMSIs) 440 and a corresponding VRF in MPLS-L3VPN-STD-MIB [RFC4382]. 441 " 442 INDEX { 443 mplsL3VpnVrfName 444 } 445 ::= { mvpnGenericTable 1 } 447 MvpnGenericEntry ::= SEQUENCE { 448 mvpnGenMvrfLastAction INTEGER, 449 mvpnGenMvrfLastActionTime DateAndTime, 450 mvpnGenMvrfCreationTime DateAndTime, 451 mvpnGenCmcastRouteProtocol INTEGER, 452 mvpnGenIpmsiInfo RowPointer, 453 mvpnGenInterAsPmsiInfo RowPointer, 454 mvpnGenUmhSelection INTEGER, 455 mvpnGenCustomerSiteType INTEGER 456 } 458 mvpnGenMvrfLastAction OBJECT-TYPE 459 SYNTAX INTEGER { 460 createdMvrf (1), 461 deletedMvrf (2), 462 modifiedMvrfIpmsiConfig (3), 463 modifiedMvrfSpmsiConfig (4) 464 } 465 MAX-ACCESS read-only 466 STATUS current 467 DESCRIPTION 468 "This object describes the last action pertaining 469 to the MVPN represented by this entry. 471 The enumerated action types and the corresponding 472 descriptions are as follows: 474 createdMvrf: 475 MVRF was created for this MVPN on the PE. 477 deletedMvrf: 478 MVRF for this MVPN was deleted from the PE. 479 A conceptual row in this table will never have 480 mvpnGenMvrfLastAction equal to deletedMvrf, 481 because in that case the row itself will not exist 482 in the table. 483 This value for mvpnGenMvrfLastAction is defined 484 solely for use in mvpnMvrfActionChange notification. 486 modifiedMvrfIpmsiConfig: 487 an I-PMSI for this MVPN was configured, deleted or 488 changed. 490 modifiedMvrfSpmsiConfig: 491 an S-PMSI for this MVPN was configured, deleted or 492 changed. 493 " 494 ::= { mvpnGenericEntry 2 } 496 mvpnGenMvrfLastActionTime OBJECT-TYPE 497 SYNTAX DateAndTime 498 MAX-ACCESS read-only 499 STATUS current 500 DESCRIPTION 501 "The timestamp when the last action, given in 502 the corresponding mvpnGenMvrfLastAction object, 503 was carried out. 504 " 505 ::= { mvpnGenericEntry 3 } 507 mvpnGenMvrfCreationTime OBJECT-TYPE 508 SYNTAX DateAndTime 509 MAX-ACCESS read-only 510 STATUS current 511 DESCRIPTION 512 "The timestamp when the MVRF was created for 513 the MVPN represented by this entry. 514 " 515 ::= { mvpnGenericEntry 4 } 517 mvpnGenCmcastRouteProtocol OBJECT-TYPE 518 SYNTAX INTEGER { 519 pim (1), 520 bgp (2) 521 } 522 MAX-ACCESS read-only 523 STATUS current 524 DESCRIPTION 525 "The protocol used to signal C-multicast routing 526 information across the provider core for the MVPN 527 represented by this entry. 529 The enumerated protocols and the corresponding 530 descriptions are as follows: 532 pim : PIM (PIM-MVPN) 533 bgp : BGP (BGP-MVPN) 534 " 535 REFERENCE 536 "RFC6513, Section 5" 537 ::= { mvpnGenericEntry 5 } 539 mvpnGenIpmsiInfo OBJECT-TYPE 540 SYNTAX RowPointer 541 MAX-ACCESS read-only 542 STATUS current 543 DESCRIPTION 544 "A pointer to a conceptual row representing 545 the corresponding I-PMSI in mvpnPmsiTable. 546 If there is no I-PMSI for the MVPN 547 represented by this entry, the 548 value of this object will be zeroDotZero. 549 " 550 ::= { mvpnGenericEntry 6 } 552 mvpnGenInterAsPmsiInfo OBJECT-TYPE 553 SYNTAX RowPointer 554 MAX-ACCESS read-only 555 STATUS current 556 DESCRIPTION 557 "A pointer to a conceptual row representing 558 the corresponding segmented Inter-AS I-PMSI in mvpnPmsiTable. 559 If there is no segmented Inter-AS I-PMSI for the MVPN, 560 the value of this object will be zeroDotZero. 561 " 562 ::= { mvpnGenericEntry 7 } 564 mvpnGenUmhSelection OBJECT-TYPE 565 SYNTAX INTEGER { 566 highestPeAddress (1), 567 cRootGroupHashing (2), 568 ucastUmhRoute (3) 569 } 570 MAX-ACCESS read-only 571 STATUS current 572 DESCRIPTION 573 "The Upstream Multicast Hop (UMH) selection method for the MVPN 574 represented by this entry. 576 The enumerated methods and the corresponding 577 descriptions are as follows: 579 highestPeAddress : PE with the highest address 580 (see RFC6513, Section 5.1.3) 581 cRootGroupHashing : hashing based on (c-root, c-group) 582 ucastUmhRoute : per unicast route towards c-root 583 " 584 REFERENCE 585 "RFC6513, Section 5.1" 586 ::= { mvpnGenericEntry 8 } 588 mvpnGenCustomerSiteType OBJECT-TYPE 589 SYNTAX INTEGER { 590 senderReceiver (1), 591 receiverOnly (2), 592 senderOnly (3) 593 } 594 MAX-ACCESS read-only 595 STATUS current 596 DESCRIPTION 597 "The type of the customer site, connected to 598 the MVPN represented by this entry. 600 The enumerated types and the corresponding 601 descriptions are as follows: 603 senderReceiver : Site is both sender and receiver 604 receiverOnly : Site is receiver-only 605 senderOnly : Site is sender-only 606 " 607 REFERENCE 608 "RFC6513, Section 2.3" 609 ::= { mvpnGenericEntry 9 } 611 -- Generic BGP-MVPN table 613 mvpnBgpTable OBJECT-TYPE 614 SYNTAX SEQUENCE OF MvpnBgpEntry 615 MAX-ACCESS not-accessible 616 STATUS current 617 DESCRIPTION 618 "A conceptual table that supplements mvpnGenericTable 619 with BGP-MVPN specific information for BGP-MVPNs on this PE. 620 " 622 ::= { mvpnObjects 3 } 624 mvpnBgpEntry OBJECT-TYPE 625 SYNTAX MvpnBgpEntry 626 MAX-ACCESS not-accessible 627 STATUS current 628 DESCRIPTION 629 "A conceptual row corresponding to a BGP-MVPN on this PE. 630 " 631 INDEX { 632 mplsL3VpnVrfName 633 } 634 ::= { mvpnBgpTable 1 } 636 MvpnBgpEntry ::= SEQUENCE { 637 mvpnBgpMode INTEGER, 638 mvpnBgpVrfRouteImportExtendedCommunity MplsL3VpnRouteDistinguisher, 639 mvpnBgpSrcASExtendedCommunity Unsigned32, 640 mvpnBgpMsgRateLimit Unsigned32, 641 mvpnBgpMaxSpmsiAdRoutes Unsigned32, 642 mvpnBgpMaxSpmsiAdRouteFreq Unsigned32, 643 mvpnBgpMaxSrcActiveAdRoutes Unsigned32, 644 mvpnBgpMaxSrcActiveAdRouteFreq Unsigned32 645 } 647 mvpnBgpMode OBJECT-TYPE 648 SYNTAX INTEGER { 649 other (0), 650 rptSpt (1), 651 sptOnly (2) 652 } 653 MAX-ACCESS read-only 654 STATUS current 655 DESCRIPTION 656 "The inter-site C-tree mode used by the BGP-MVPN 657 represented by this entry. 659 other : none of the following 660 rptSpt : inter-site shared tree mode 661 (Rendezvous Point Tree (RPT) and 662 source-specific shortest-path tree (SPT)) 663 sptOnly : inter-site source-only tree mode 664 " 665 REFERENCE 666 "RFC6513, Section 9.3.1" 667 ::= { mvpnBgpEntry 1 } 669 mvpnBgpVrfRouteImportExtendedCommunity OBJECT-TYPE 670 SYNTAX MplsL3VpnRouteDistinguisher 671 MAX-ACCESS read-only 672 STATUS current 673 DESCRIPTION 674 "The VRF Route Import Extended Community added by this PE 675 to unicast VPN routes that it advertises for the BGP-MVPN 676 corresponding to this entry. 677 " 678 REFERENCE 679 "RFC6514, Section 7 680 " 681 ::= { mvpnBgpEntry 2 } 683 mvpnBgpSrcASExtendedCommunity OBJECT-TYPE 684 SYNTAX Unsigned32 685 MAX-ACCESS read-only 686 STATUS current 687 DESCRIPTION 688 "The Source AS Extended Community added by this PE 689 to the unicast VPN routes that it advertises for 690 the BGP-MVPN represented by this entry. 691 " 692 REFERENCE 693 "RFC6514, Section 6 694 " 695 ::= { mvpnBgpEntry 3 } 697 mvpnBgpMsgRateLimit OBJECT-TYPE 698 SYNTAX Unsigned32 (0..4294967295) 699 UNITS "messages per second" 700 MAX-ACCESS read-write 701 STATUS current 702 DESCRIPTION 703 "The configurable upper bound for the rate of BGP C-multicast 704 routing information message exchange between this PE and other 705 PEs in the BGP-MVPN corresponding to this entry. 706 " 707 REFERENCE 708 "RFC6514, Section 17" 709 ::= { mvpnBgpEntry 4 } 711 mvpnBgpMaxSpmsiAdRoutes OBJECT-TYPE 712 SYNTAX Unsigned32 (0..4294967295) 713 MAX-ACCESS read-write 714 STATUS current 715 DESCRIPTION 716 "The configurable upper bound for the number of 717 S-PMSI A-D routes for the BGP-MVPN corresponding to 718 this entry. 719 " 720 REFERENCE 721 "RFC6514, Section 17" 722 ::= { mvpnBgpEntry 5 } 724 mvpnBgpMaxSpmsiAdRouteFreq OBJECT-TYPE 725 SYNTAX Unsigned32 (0..4294967295) 726 UNITS "routes per second" 727 MAX-ACCESS read-write 728 STATUS current 729 DESCRIPTION 730 "The configurable upper bound for the frequency of 731 S-PMSI A-D route generation for the BGP-MVPN corresponding 732 to this entry. 733 " 734 REFERENCE 735 "RFC6514, Section 17" 736 ::= { mvpnBgpEntry 6 } 738 mvpnBgpMaxSrcActiveAdRoutes OBJECT-TYPE 739 SYNTAX Unsigned32 (0..4294967295) 740 MAX-ACCESS read-write 741 STATUS current 742 DESCRIPTION 743 "The configurable upper bound for the number of 744 Source Active A-D routes for the BGP-MVPN corresponding 745 to this entry. 746 " 747 REFERENCE 748 "RFC6514, Section 17" 749 ::= { mvpnBgpEntry 7 } 751 mvpnBgpMaxSrcActiveAdRouteFreq OBJECT-TYPE 752 SYNTAX Unsigned32 (0..4294967295) 753 UNITS "routes per second" 754 MAX-ACCESS read-write 755 STATUS current 756 DESCRIPTION 757 "The configurable upper bound for the frequency of Source 758 Active A-D route generation for the BGP-MVPN corresponding 759 to this entry. 760 " 761 REFERENCE 762 "RFC6514, Section 17" 763 ::= { mvpnBgpEntry 8 } 765 -- Table of PMSI information 766 mvpnPmsiTable OBJECT-TYPE 767 SYNTAX SEQUENCE OF MvpnPmsiEntry 768 MAX-ACCESS not-accessible 769 STATUS current 770 DESCRIPTION 771 "A conceptual table containing information related 772 to PMSIs on this PE. 773 " 774 ::= { mvpnObjects 4 } 776 mvpnPmsiEntry OBJECT-TYPE 777 SYNTAX MvpnPmsiEntry 778 MAX-ACCESS not-accessible 779 STATUS current 780 DESCRIPTION 781 "A conceptual row corresponding to a 782 PMSI on this PE. 783 " 784 INDEX { 785 mvpnPmsiTunnelIfIndex 786 } 787 ::= { mvpnPmsiTable 1 } 789 MvpnPmsiEntry ::= SEQUENCE { 790 mvpnPmsiTunnelIfIndex InterfaceIndex, 791 mvpnPmsiRD MplsL3VpnRouteDistinguisher, 792 mvpnPmsiTunnelType L2L3VpnMcastProviderTunnelType, 793 mvpnPmsiTunnelAttribute RowPointer, 794 mvpnPmsiTunnelPimGroupAddrType InetAddressType, 795 mvpnPmsiTunnelPimGroupAddr InetAddress, 796 mvpnPmsiEncapsulationType INTEGER 797 } 799 mvpnPmsiTunnelIfIndex OBJECT-TYPE 800 SYNTAX InterfaceIndex 801 MAX-ACCESS not-accessible 802 STATUS current 803 DESCRIPTION 804 "A unique value for this conceptual row. Its value 805 will be the same as that of the ifIndex object instance 806 for the corresponding PMSI in ifTable. 807 " 808 REFERENCE 809 "RFC2863 Sec. 3.1.5 810 " 811 ::= { mvpnPmsiEntry 1 } 813 mvpnPmsiRD OBJECT-TYPE 814 SYNTAX MplsL3VpnRouteDistinguisher 815 MAX-ACCESS read-only 816 STATUS current 817 DESCRIPTION 818 "The Route Distinguisher for this I-PMSI." 819 ::= { mvpnPmsiEntry 3 } 821 mvpnPmsiTunnelType OBJECT-TYPE 822 SYNTAX L2L3VpnMcastProviderTunnelType 823 MAX-ACCESS read-only 824 STATUS current 825 DESCRIPTION 826 "The type of tunnel used to 827 instantiate the PMSI corresponding to this entry. 828 " 829 REFERENCE 830 "RFC6513, Sec. 2.6 831 " 832 ::= { mvpnPmsiEntry 4 } 834 mvpnPmsiTunnelAttribute OBJECT-TYPE 835 SYNTAX RowPointer 836 MAX-ACCESS read-only 837 STATUS current 838 DESCRIPTION 839 "A pointer to a conceptual row representing 840 the P-tunnel used by the PMSI in 841 l2L3VpnMcastPmsiTunnelAttributeTable. 842 " 843 ::= { mvpnPmsiEntry 5 } 845 mvpnPmsiTunnelPimGroupAddrType OBJECT-TYPE 846 SYNTAX InetAddressType 847 MAX-ACCESS read-only 848 STATUS current 849 DESCRIPTION 850 "The InetAddressType of the mvpnPmsiTunnelPimGroupAddr object 851 that follows. 852 When the PMSI corresponding to this entry does not use 853 the PIM provider tunnel, i.e., 854 the value of mvpnPmsiTunnelType is not one of 855 pimSsm(3), pimAsm(4), or pimBidir(5), 856 this object should be unknown(0). 857 " 858 ::= { mvpnPmsiEntry 6 } 860 mvpnPmsiTunnelPimGroupAddr OBJECT-TYPE 861 SYNTAX InetAddress 862 MAX-ACCESS read-only 863 STATUS current 864 DESCRIPTION 865 "The tunnel address which is used by the PMSI 866 corresponding to this entry. 867 When the PMSI corresponding to this entry does not 868 use PIM provider tunnel, i.e., 869 the value of mvpnPmsiTunnelType is not one of 870 pimSsm(3), pimAsm(4), or pimBidir(5), 871 this object should be a zero-length octet string. 872 " 873 ::= { mvpnPmsiEntry 7 } 875 mvpnPmsiEncapsulationType OBJECT-TYPE 876 SYNTAX INTEGER { 877 greIp (1), 878 ipIp (2), 879 mpls (3) 880 } 881 MAX-ACCESS read-only 882 STATUS current 883 DESCRIPTION 884 "The encapsulation type used for sending 885 packets through the PMSI corresponding to this entry. 887 The enumerated encapsulation types and the corresponding 888 descriptions are as follows: 890 greIp : GRE (Generic Routing Encapsulation) 891 encapsulation [RFC2784] 892 ipIp : IP-in-IP encapsulation [RFC2003] 893 mpls : MPLS encapsulation [RFC3032] 894 " 895 REFERENCE 896 "RFC2003 897 RFC2784 898 RFC3032 899 RFC6513, Sec. 12.1 900 " 901 ::= { mvpnPmsiEntry 8 } 903 -- Table of S-PMSI specific information 905 mvpnSpmsiTable OBJECT-TYPE 906 SYNTAX SEQUENCE OF MvpnSpmsiEntry 907 MAX-ACCESS not-accessible 908 STATUS current 909 DESCRIPTION 910 "A conceptual table containing information related 911 to S-PMSIs on this PE. 912 This table stores only S-PMSI specific attribute 913 information. Generic PMSI attribute information of 914 S-PMSIs is stored in mvpnPmsiTable. 915 " 916 ::= { mvpnObjects 5 } 918 mvpnSpmsiEntry OBJECT-TYPE 919 SYNTAX MvpnSpmsiEntry 920 MAX-ACCESS not-accessible 921 STATUS current 922 DESCRIPTION 923 "A conceptual row corresponding to an S-PMSI on this PE. 924 Implementers need to be aware that if the total number of 925 octets in mplsL3VpnVrfName, mvpnSpmsiCmcastGroupAddr and 926 mvpnSpmsiCmcastSourceAddr exceeds 113, the OIDs of column 927 instances in this row will have more than 128 sub-identifiers 928 and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 929 " 930 INDEX { 931 mplsL3VpnVrfName, 932 mvpnSpmsiCmcastGroupAddrType, 933 mvpnSpmsiCmcastGroupAddr, 934 mvpnSpmsiCmcastGroupPrefixLen, 935 mvpnSpmsiCmcastSourceAddrType, 936 mvpnSpmsiCmcastSourceAddr, 937 mvpnSpmsiCmcastSourcePrefixLen 938 } 939 ::= { mvpnSpmsiTable 1 } 941 MvpnSpmsiEntry ::= SEQUENCE { 942 mvpnSpmsiCmcastGroupAddrType InetAddressType, 943 mvpnSpmsiCmcastGroupAddr InetAddress, 944 mvpnSpmsiCmcastGroupPrefixLen InetAddressPrefixLength, 945 mvpnSpmsiCmcastSourceAddrType InetAddressType, 946 mvpnSpmsiCmcastSourceAddr InetAddress, 947 mvpnSpmsiCmcastSourcePrefixLen InetAddressPrefixLength, 948 mvpnSpmsiPmsiPointer RowPointer 949 } 951 mvpnSpmsiCmcastGroupAddrType OBJECT-TYPE 952 SYNTAX InetAddressType 953 MAX-ACCESS not-accessible 954 STATUS current 955 DESCRIPTION 956 "The InetAddressType of the mvpnSpmsiCmcastGroupAddr object 957 that follows. 959 " 960 ::= { mvpnSpmsiEntry 1 } 962 mvpnSpmsiCmcastGroupAddr OBJECT-TYPE 963 SYNTAX InetAddress 964 MAX-ACCESS not-accessible 965 STATUS current 966 DESCRIPTION 967 "The group address of the C-flow assigned to the 968 S-PMSI corresponding to this entry." 969 REFERENCE 970 "RFC6513, Sec. 3.1" 971 ::= { mvpnSpmsiEntry 2 } 973 mvpnSpmsiCmcastGroupPrefixLen OBJECT-TYPE 974 SYNTAX InetAddressPrefixLength 975 MAX-ACCESS not-accessible 976 STATUS current 977 DESCRIPTION 978 "The prefix length of the corresponding 979 mvpnSpmsiCmcastGroupAddr object. 980 " 981 ::= { mvpnSpmsiEntry 3 } 983 mvpnSpmsiCmcastSourceAddrType OBJECT-TYPE 984 SYNTAX InetAddressType 985 MAX-ACCESS not-accessible 986 STATUS current 987 DESCRIPTION 988 "The InetAddressType of the mvpnSpmsiCmcastSourceAddr object 989 that follows. 990 " 991 ::= { mvpnSpmsiEntry 4 } 993 mvpnSpmsiCmcastSourceAddr OBJECT-TYPE 994 SYNTAX InetAddress 995 MAX-ACCESS not-accessible 996 STATUS current 997 DESCRIPTION 998 "The source address of the C-flow assigned to the 999 S-PMSI corresponding to this entry." 1000 ::= { mvpnSpmsiEntry 5 } 1002 mvpnSpmsiCmcastSourcePrefixLen OBJECT-TYPE 1003 SYNTAX InetAddressPrefixLength 1004 MAX-ACCESS not-accessible 1005 STATUS current 1006 DESCRIPTION 1007 "The prefix length of the corresponding 1008 mvpnSpmsiCmcastSourceAddr object. 1009 " 1010 ::= { mvpnSpmsiEntry 6 } 1012 mvpnSpmsiPmsiPointer OBJECT-TYPE 1013 SYNTAX RowPointer 1014 MAX-ACCESS read-only 1015 STATUS current 1016 DESCRIPTION 1017 "A pointer to a conceptual row representing 1018 generic information of this S-PMSI in mvpnPmsiTable. 1019 " 1020 ::= { mvpnSpmsiEntry 7 } 1022 -- Table of statistics pertaining to 1023 -- advertisements sent/received 1025 mvpnAdvtStatsTable OBJECT-TYPE 1026 SYNTAX SEQUENCE OF MvpnAdvtStatsEntry 1027 MAX-ACCESS not-accessible 1028 STATUS current 1029 DESCRIPTION 1030 "A conceptual table containing statistics pertaining to 1031 I-PMSI and S-PMSI advertisements sent/received by this PE. 1032 " 1033 ::= { mvpnObjects 6 } 1035 mvpnAdvtStatsEntry OBJECT-TYPE 1036 SYNTAX MvpnAdvtStatsEntry 1037 MAX-ACCESS not-accessible 1038 STATUS current 1039 DESCRIPTION 1040 "A conceptual row corresponding to statistics 1041 pertaining to advertisements sent/received 1042 for a particular MVPN on this PE. 1044 Implementers need to be aware that if the total number of 1045 octets in mplsL3VpnVrfName and mvpnAdvtPeerAddr exceeds 115, 1046 then OIDs of column instances in this row will have more than 1047 128 sub-identifiers and cannot be accessed using SNMPv1, 1048 SNMPv2c, or SNMPv3. 1049 " 1050 INDEX { 1051 mplsL3VpnVrfName, 1052 mvpnAdvtType, 1053 mvpnAdvtPeerAddrType, 1054 mvpnAdvtPeerAddr 1056 } 1057 ::= { mvpnAdvtStatsTable 1 } 1059 MvpnAdvtStatsEntry ::= SEQUENCE { 1060 mvpnAdvtType INTEGER, 1061 mvpnAdvtPeerAddrType InetAddressType, 1062 mvpnAdvtPeerAddr InetAddress, 1063 mvpnAdvtSent Counter32, 1064 mvpnAdvtReceived Counter32, 1065 mvpnAdvtReceivedError Counter32, 1066 mvpnAdvtReceivedMalformedTunnelType Counter32, 1067 mvpnAdvtReceivedMalformedTunnelId Counter32, 1068 mvpnAdvtLastSentTime DateAndTime, 1069 mvpnAdvtLastReceivedTime DateAndTime, 1070 mvpnAdvtCounterDiscontinuityTime TimeStamp 1071 } 1073 mvpnAdvtType OBJECT-TYPE 1074 SYNTAX INTEGER { 1075 intraAsIpmsi (0), 1076 interAsIpmsi (1), 1077 sPmsi (2) 1078 } 1079 MAX-ACCESS not-accessible 1080 STATUS current 1081 DESCRIPTION 1082 "The PMSI type. 1084 The enumerated PMSI types and corresponding 1085 descriptions are as follows: 1087 intraAsIpmsi : Intra-AS Inclusive PMSI 1088 interAsIpmsi : Inter-AS Inclusive PMSI 1089 sPmsi : Selective PMSI 1090 " 1091 REFERENCE 1092 "RFC6513, Sec. 3.2.1" 1093 ::= { mvpnAdvtStatsEntry 1 } 1095 mvpnAdvtPeerAddrType OBJECT-TYPE 1096 SYNTAX InetAddressType 1097 MAX-ACCESS not-accessible 1098 STATUS current 1099 DESCRIPTION 1100 "The InternetAddressType of the mvpnAdvtPeerAddr object 1101 that follows. 1102 " 1104 ::= { mvpnAdvtStatsEntry 2 } 1106 mvpnAdvtPeerAddr OBJECT-TYPE 1107 SYNTAX InetAddress 1108 MAX-ACCESS not-accessible 1109 STATUS current 1110 DESCRIPTION 1111 "The address of a peer PE that exchanges advertisement with 1112 this PE. 1113 " 1114 ::= { mvpnAdvtStatsEntry 3 } 1116 mvpnAdvtSent OBJECT-TYPE 1117 SYNTAX Counter32 1118 MAX-ACCESS read-only 1119 STATUS current 1120 DESCRIPTION 1121 "The number of advertisements successfully 1122 sent to the peer PE specified by the corresponding 1123 mvpnAdvtPeerAddr. 1125 Discontinuities in the value of this counter can 1126 occur at re-initialization of the management system, 1127 and at other times as indicated by the corresponding 1128 mvpnAdvtCounterDiscontinuityTime object. 1129 " 1130 ::= { mvpnAdvtStatsEntry 4 } 1132 mvpnAdvtReceived OBJECT-TYPE 1133 SYNTAX Counter32 1134 MAX-ACCESS read-only 1135 STATUS current 1136 DESCRIPTION 1137 "The number of advertisements received from the peer PE 1138 specified by the corresponding mvpnAdvtPeerAddr object. 1139 This includes advertisements that were discarded. 1141 Discontinuities in the value of this counter can 1142 occur at re-initialization of the management system, 1143 and at other times as indicated by the corresponding 1144 mvpnAdvtCounterDiscontinuityTime object. 1145 " 1146 ::= { mvpnAdvtStatsEntry 5 } 1148 mvpnAdvtReceivedError OBJECT-TYPE 1149 SYNTAX Counter32 1150 MAX-ACCESS read-only 1151 STATUS current 1152 DESCRIPTION 1153 "The total number of advertisements received from a peer PE, 1154 specified by the corresponding mvpnAdvtPeerAddr object, 1155 that were rejected due to error(s) in the advertisement. 1156 The value of this object includes 1157 the error cases counted in the corresponding 1158 mvpnAdvtReceivedMalformedTunnelType and 1159 mvpnAdvtReceivedMalformedTunnelId objects. 1161 Discontinuities in the value of this counter can 1162 occur at re-initialization of the management system, 1163 and at other times as indicated by the corresponding 1164 mvpnAdvtCounterDiscontinuityTime object. 1165 " 1166 ::= { mvpnAdvtStatsEntry 6 } 1168 mvpnAdvtReceivedMalformedTunnelType OBJECT-TYPE 1169 SYNTAX Counter32 1170 MAX-ACCESS read-only 1171 STATUS current 1172 DESCRIPTION 1173 "The total number of advertisements received from the peer PE 1174 specified by the corresponding mvpnAdvtPeerAddr object, 1175 that were rejected due to malformed Tunnel Type 1176 in the PMSI Tunnel attribute. 1178 Discontinuities in the value of this counter can 1179 occur at re-initialization of the management system, 1180 and at other times as indicated by the corresponding 1181 mvpnAdvtCounterDiscontinuityTime object. 1182 " 1183 REFERENCE 1184 "RFC6514 Sec.5" 1185 ::= { mvpnAdvtStatsEntry 7 } 1187 mvpnAdvtReceivedMalformedTunnelId OBJECT-TYPE 1188 SYNTAX Counter32 1189 MAX-ACCESS read-only 1190 STATUS current 1191 DESCRIPTION 1192 "The total number of advertisements received from the peer PE 1193 specified by the corresponding mvpnAdvtPeerAddr object, 1194 that were rejected due to malformed Tunnel Identifier 1195 in the PMSI Tunnel attribute. 1196 Discontinuities in the value of this counter can 1197 occur at re-initialization of the management system, 1198 and at other times as indicated by the corresponding 1199 mvpnAdvtCounterDiscontinuityTime object. 1201 " 1202 REFERENCE 1203 "RFC6514 Sec.5" 1204 ::= { mvpnAdvtStatsEntry 8 } 1206 mvpnAdvtLastSentTime OBJECT-TYPE 1207 SYNTAX DateAndTime 1208 MAX-ACCESS read-only 1209 STATUS current 1210 DESCRIPTION 1211 "The timestamp when the last advertisement 1212 was successfully sent by this PE. 1213 If no advertisement has been sent since the 1214 last re-initialization of this PE, then this 1215 object will have a zero-length string. 1216 " 1217 ::= { mvpnAdvtStatsEntry 9 } 1219 mvpnAdvtLastReceivedTime OBJECT-TYPE 1220 SYNTAX DateAndTime 1221 MAX-ACCESS read-only 1222 STATUS current 1223 DESCRIPTION 1224 "The timestamp when the last advertisement 1225 was successfully received from the peer PE specified 1226 by the corresponding mvpnAdvtPeerAddr object and 1227 processed by this PE. 1228 If no advertisement has been received since the 1229 last re-initialization of this PE, then this 1230 object will have a zero-length string. 1231 " 1232 ::= { mvpnAdvtStatsEntry 10 } 1234 mvpnAdvtCounterDiscontinuityTime OBJECT-TYPE 1235 SYNTAX TimeStamp 1236 MAX-ACCESS read-only 1237 STATUS current 1238 DESCRIPTION 1239 "The value of sysUpTime on the most recent occasion 1240 at which any one or more of this application's 1241 counters, viz., counters with OID prefix 1242 'mvpnAdvtSent' or 1243 'mvpnAdvtReceived' or 1244 'mvpnAdvtReceivedError' or 1245 'mvpnAdvtReceivedMalformedTunnelType' or 1246 'mvpnAdvtReceivedMalformedTunnelId' suffered a 1247 discontinuity. 1248 If no such discontinuities have occurred since the 1249 last re-initialization of the local management 1250 subsystem, then this object will have a zero value. 1251 " 1252 ::= { mvpnAdvtStatsEntry 11 } 1254 -- Table of multicast routes in an MVPN 1256 mvpnMrouteTable OBJECT-TYPE 1257 SYNTAX SEQUENCE OF MvpnMrouteEntry 1258 MAX-ACCESS not-accessible 1259 STATUS current 1260 DESCRIPTION 1261 "A conceptual table containing multicast routing information 1262 corresponding to the MVRFs present on the PE. 1263 " 1264 ::= { mvpnObjects 7 } 1266 mvpnMrouteEntry OBJECT-TYPE 1267 SYNTAX MvpnMrouteEntry 1268 MAX-ACCESS not-accessible 1269 STATUS current 1270 DESCRIPTION 1271 "A conceptual row corresponding to a route for IP datagrams 1272 from a particular source and addressed to a particular IP 1273 multicast group address. 1275 Implementers need to be aware that if the total number of 1276 octets in mplsL3VpnVrfName, mvpnMrouteCmcastGroupAddr and 1277 mvpnMrouteCmcastSourceAddrs exceeds 113, the OIDs of column 1278 instances in this row will have more than 128 sub-identifiers 1279 and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 1280 " 1281 INDEX { 1282 mplsL3VpnVrfName, 1283 mvpnMrouteCmcastGroupAddrType, 1284 mvpnMrouteCmcastGroupAddr, 1285 mvpnMrouteCmcastGroupPrefixLength, 1286 mvpnMrouteCmcastSourceAddrType, 1287 mvpnMrouteCmcastSourceAddrs, 1288 mvpnMrouteCmcastSourcePrefixLength 1289 } 1290 ::= { mvpnMrouteTable 1 } 1292 MvpnMrouteEntry ::= SEQUENCE { 1293 mvpnMrouteCmcastGroupAddrType InetAddressType, 1294 mvpnMrouteCmcastGroupAddr InetAddress, 1295 mvpnMrouteCmcastGroupPrefixLength InetAddressPrefixLength, 1296 mvpnMrouteCmcastSourceAddrType InetAddressType, 1297 mvpnMrouteCmcastSourceAddrs InetAddress, 1298 mvpnMrouteCmcastSourcePrefixLength InetAddressPrefixLength, 1299 mvpnMrouteUpstreamNeighborAddrType InetAddressType, 1300 mvpnMrouteUpstreamNeighborAddr InetAddress, 1301 mvpnMrouteInIfIndex InterfaceIndexOrZero, 1302 mvpnMrouteExpiryTime TimeTicks, 1303 mvpnMrouteProtocol IANAipMRouteProtocol, 1304 mvpnMrouteRtProtocol IANAipRouteProtocol, 1305 mvpnMrouteRtAddrType InetAddressType, 1306 mvpnMrouteRtAddr InetAddress, 1307 mvpnMrouteRtPrefixLength InetAddressPrefixLength, 1308 mvpnMrouteRtType INTEGER, 1309 mvpnMrouteOctets Counter64, 1310 mvpnMroutePkts Counter64, 1311 mvpnMrouteTtlDroppedOctets Counter64, 1312 mvpnMrouteTtlDroppedPackets Counter64, 1313 mvpnMrouteDroppedInOctets Counter64, 1314 mvpnMrouteDroppedInPackets Counter64, 1315 mvpnMroutePmsiPointer RowPointer, 1316 mvpnMrouteNumberOfLocalReplication Unsigned32, 1317 mvpnMrouteNumberOfRemoteReplication Unsigned32, 1318 mvpnMrouteCounterDiscontinuityTime TimeStamp 1319 } 1321 mvpnMrouteCmcastGroupAddrType OBJECT-TYPE 1322 SYNTAX InetAddressType 1323 MAX-ACCESS not-accessible 1324 STATUS current 1325 DESCRIPTION 1326 "The InetAddressType of the mvpnMrouteCmcastGroupAddr object 1327 that follows. 1328 " 1329 ::= { mvpnMrouteEntry 1 } 1331 mvpnMrouteCmcastGroupAddr OBJECT-TYPE 1332 SYNTAX InetAddress 1333 MAX-ACCESS not-accessible 1334 STATUS current 1335 DESCRIPTION 1336 "The IP multicast group address which, along with 1337 the corresponding mvpnMrouteCmcastGroupPrefixLength object, 1338 identifies destinations for which this entry contains 1339 multicast routing information. 1341 This address object is only significant up to 1342 mvpnMrouteCmcastGroupPrefixLength bits. The remaining address 1343 bits MUST be set to zero. 1345 For addresses of type 'ipv4z' or 'ipv6z', the appended zone 1346 index is significant even though it lies beyond the prefix 1347 length. The use of these address types indicate that this 1348 forwarding state applies only within the given zone. Zone 1349 index zero is not valid in this table. 1350 " 1351 ::= { mvpnMrouteEntry 2 } 1353 mvpnMrouteCmcastGroupPrefixLength OBJECT-TYPE 1354 SYNTAX InetAddressPrefixLength 1355 MAX-ACCESS not-accessible 1356 STATUS current 1357 DESCRIPTION 1358 "The length in bits of the mask which, along with 1359 the corresponding mvpnMrouteCmcastGroupAddr object, 1360 identifies destinations for which this entry contains 1361 multicast routing information. 1363 If the corresponding InetAddressType is 'ipv4' or 'ipv4z', 1364 this object must be in the range 4..32. 1365 If the corresponding InetAddressType is 'ipv6' or 'ipv6z', 1366 this object must be in the range 8..128. 1367 " 1368 ::= { mvpnMrouteEntry 3 } 1370 mvpnMrouteCmcastSourceAddrType OBJECT-TYPE 1371 SYNTAX InetAddressType 1372 MAX-ACCESS not-accessible 1373 STATUS current 1374 DESCRIPTION 1375 "The InetAddressType of the mvpnMrouteCmcastSourceAddrs object 1376 that follows. 1378 A value of unknown(0) indicates a non-source-specific entry, 1379 corresponding to all sources in the group. Otherwise, the 1380 value MUST be the same as the value of 1381 mvpnMrouteCmcastGroupAddrType. 1382 " 1383 ::= { mvpnMrouteEntry 4 } 1385 mvpnMrouteCmcastSourceAddrs OBJECT-TYPE 1386 SYNTAX InetAddress 1387 MAX-ACCESS not-accessible 1388 STATUS current 1389 DESCRIPTION 1390 "The network address which, along with the 1391 corresponding mvpnMrouteCmcastSourcePrefixLength object, 1392 identifies the sources for which this entry contains 1393 multicast routing information. 1395 This address object is only significant up to 1396 mvpnMrouteCmcastSourcePrefixLength bits. 1397 The remaining address bits MUST be set to zero. 1399 For addresses of type 'ipv4z' or 'ipv6z', the appended zone 1400 index is significant even though it lies beyond the prefix 1401 length. The use of these address types indicate that this 1402 source address applies only within the given zone. Zone 1403 index zero is not valid in this table. 1404 " 1405 ::= { mvpnMrouteEntry 5 } 1407 mvpnMrouteCmcastSourcePrefixLength OBJECT-TYPE 1408 SYNTAX InetAddressPrefixLength 1409 MAX-ACCESS not-accessible 1410 STATUS current 1411 DESCRIPTION 1412 "The length in bits of the mask which, along with 1413 the corresponding mvpnMrouteCmcastSourceAddr object, 1414 identifies the sources for which this entry contains 1415 multicast routing information. 1417 If the corresponding InetAddressType is 'ipv4' or 'ipv4z', 1418 this object must be in the range 4..32. 1419 If the corresponding InetAddressType is 'ipv6' or 'ipv6z', 1420 this object must be in the range 8..128. 1421 If the corresponding InetAddressType is 'unknown', 1422 this object must be zero. 1423 " 1424 ::= { mvpnMrouteEntry 6 } 1426 mvpnMrouteUpstreamNeighborAddrType OBJECT-TYPE 1427 SYNTAX InetAddressType 1428 MAX-ACCESS read-only 1429 STATUS current 1430 DESCRIPTION 1431 "The InetAddressType of the mvpnMrouteUpstreamNeighborAddr 1432 object that follows. 1434 A value of unknown(0) indicates that the upstream 1435 neighbor is unknown, for example in BIDIR-PIM." 1436 REFERENCE 1437 "RFC 5015" 1438 ::= { mvpnMrouteEntry 7 } 1440 mvpnMrouteUpstreamNeighborAddr OBJECT-TYPE 1441 SYNTAX InetAddress 1442 MAX-ACCESS read-only 1443 STATUS current 1444 DESCRIPTION 1445 "The address of the upstream neighbor (for example, 1446 Reverse Path Forwarding (RPF) neighbor) from which 1447 IP datagrams from these sources represented by 1448 this entry to this multicast address are received. 1449 " 1450 ::= { mvpnMrouteEntry 8 } 1452 mvpnMrouteInIfIndex OBJECT-TYPE 1453 SYNTAX InterfaceIndexOrZero 1454 MAX-ACCESS read-only 1455 STATUS current 1456 DESCRIPTION 1457 "The value of ifIndex for the interface on which IP 1458 datagrams sent by these sources represented by this entry to 1459 this multicast address are received. 1461 A value 0 indicates that datagrams are not 1462 subject to an incoming interface check, but may be accepted 1463 on multiple interfaces (for example, in BIDIR-PIM). 1464 " 1465 REFERENCE 1466 "RFC 5015" 1467 ::= { mvpnMrouteEntry 9 } 1469 mvpnMrouteExpiryTime OBJECT-TYPE 1470 SYNTAX TimeTicks 1471 MAX-ACCESS read-only 1472 STATUS current 1473 DESCRIPTION 1474 "The minimum amount of time remaining before this entry will 1475 be aged out. The value 0 indicates that the entry is not 1476 subject to aging. If the corresponding mvpnMrouteNextHopState 1477 object is pruned(1), this object represents the remaining 1478 time for the prune to expire after which the state will 1479 return to forwarding(2). 1480 If the corresponding mvpnMrouteNextHopState object is 1481 forwarding(2), this object indicates the time after which 1482 this entry will be removed from the table. 1483 " 1484 ::= { mvpnMrouteEntry 10 } 1486 mvpnMrouteProtocol OBJECT-TYPE 1487 SYNTAX IANAipMRouteProtocol 1488 MAX-ACCESS read-only 1489 STATUS current 1490 DESCRIPTION 1491 "The multicast routing protocol via which this multicast 1492 forwarding entry was learned. 1493 " 1494 ::= { mvpnMrouteEntry 11 } 1496 mvpnMrouteRtProtocol OBJECT-TYPE 1497 SYNTAX IANAipRouteProtocol 1498 MAX-ACCESS read-only 1499 STATUS current 1500 DESCRIPTION 1501 "The routing protocol via which the route used to find the 1502 upstream or parent interface for this multicast forwarding 1503 entry was learned. 1504 " 1505 ::= { mvpnMrouteEntry 12 } 1507 mvpnMrouteRtAddrType OBJECT-TYPE 1508 SYNTAX InetAddressType 1509 MAX-ACCESS read-only 1510 STATUS current 1511 DESCRIPTION 1512 "The InetAddressType of the mvpnMrouteRtAddr object 1513 that follows. 1514 " 1515 ::= { mvpnMrouteEntry 13 } 1517 mvpnMrouteRtAddr OBJECT-TYPE 1518 SYNTAX InetAddress 1519 MAX-ACCESS read-only 1520 STATUS current 1521 DESCRIPTION 1522 "The address portion of the route used to find the upstream 1523 or parent interface for this multicast forwarding entry. 1525 This address object is only significant up to 1526 mvpnMrouteRtPrefixLength bits. The remaining address bits 1527 MUST be set to zero. 1529 For addresses of type 'ipv4z' or 'ipv6z', the appended zone 1530 index is significant even though it lies beyond the prefix 1531 length. The use of these address types indicate that this 1532 forwarding state applies only within the given zone. Zone 1533 index zero is not valid in this table. 1534 " 1535 ::= { mvpnMrouteEntry 14 } 1537 mvpnMrouteRtPrefixLength OBJECT-TYPE 1538 SYNTAX InetAddressPrefixLength 1539 MAX-ACCESS read-only 1540 STATUS current 1541 DESCRIPTION 1542 "The length in bits of the mask associated with the route 1543 used to find the upstream or parent interface for this 1544 multicast forwarding entry. 1546 If the corresponding InetAddressType is 'ipv4' or 'ipv4z', 1547 this object must be in the range 4..32. 1548 If the corresponding InetAddressType is 'ipv6' or 'ipv6z', 1549 this object must be in the range 8..128. 1550 " 1551 ::= { mvpnMrouteEntry 15 } 1553 mvpnMrouteRtType OBJECT-TYPE 1554 SYNTAX INTEGER { 1555 unicast (1), 1556 multicast (2) 1557 } 1558 MAX-ACCESS read-only 1559 STATUS current 1560 DESCRIPTION 1561 "The reason for placing the route in the (logical) 1562 multicast Routing Information Base (RIB). 1564 The enumerated reasons and the corresponding 1565 descriptions are as follows: 1567 unicast: 1568 The route would normally be placed only in 1569 the unicast RIB, but was placed in the multicast RIB 1570 by local configuration, such as when running PIM over 1571 RIP. 1573 multicast: 1574 The route was explicitly added to the multicast RIB by 1575 the routing protocol, such as the Distance Vector 1576 Multicast Routing Protocol (DVMRP) or Multiprotocol BGP. 1577 " 1578 ::= { mvpnMrouteEntry 16 } 1580 mvpnMrouteOctets OBJECT-TYPE 1581 SYNTAX Counter64 1582 MAX-ACCESS read-only 1583 STATUS current 1584 DESCRIPTION 1585 "The number of octets contained in IP datagrams that were 1586 received from sources represented by this entry and 1587 addressed to this multicast group address, and which were 1588 forwarded by this router. 1590 Discontinuities in the value of this counter can 1591 occur at re-initialization of the management system, 1592 and at other times as indicated by the corresponding 1593 mvpnMrouteCounterDiscontinuityTime object. 1594 " 1595 ::= { mvpnMrouteEntry 17 } 1597 mvpnMroutePkts OBJECT-TYPE 1598 SYNTAX Counter64 1599 MAX-ACCESS read-only 1600 STATUS current 1601 DESCRIPTION 1602 "The number of packets routed using this multicast route 1603 entry. 1605 Discontinuities in the value of this counter can 1606 occur at re-initialization of the management system, 1607 and at other times as indicated by the corresponding 1608 mvpnMrouteCounterDiscontinuityTime object. 1609 " 1610 ::= { mvpnMrouteEntry 18 } 1612 mvpnMrouteTtlDroppedOctets OBJECT-TYPE 1613 SYNTAX Counter64 1614 MAX-ACCESS read-only 1615 STATUS current 1616 DESCRIPTION 1617 "The number of octets contained in IP datagrams that this 1618 router has received from sources represented by 1619 this entry and addressed to this multicast group address, 1620 which were dropped due to Time To Live (TTL) issues. 1621 TTL issues occur when the TTL (IPv4) or Hop Limit (IPv6) 1622 of the incoming packet was decremented to zero, or to a 1623 value less than ipMcastInterfaceTtl of the corresponding 1624 interface. 1626 The ipMcastInterfaceTtl object is defined in IPMCAST-MIB 1627 [RFC5132] and represents the datagram TTL 1628 threshold for the interface. Any IP multicast datagrams 1629 with a TTL (IPv4) or Hop Limit (IPv6) less than this 1630 threshold will not be forwarded out of the interface. 1631 The default value of 0 means all multicast packets are 1632 forwarded out of the interface. A value of 256 means that 1633 no multicast packets are forwarded out of the interface. 1635 Discontinuities in the value of this counter can 1636 occur at re-initialization of the management system, 1637 and at other times as indicated by the corresponding 1638 mvpnMrouteCounterDiscontinuityTime object. 1639 " 1640 REFERENCE 1641 "RFC5132, Sec. 6 1642 " 1643 ::= { mvpnMrouteEntry 19 } 1645 mvpnMrouteTtlDroppedPackets OBJECT-TYPE 1646 SYNTAX Counter64 1647 MAX-ACCESS read-only 1648 STATUS current 1649 DESCRIPTION 1650 "The number of packets that this router has received from 1651 the sources represented by this entry and addressed to this 1652 multicast group address, which were dropped due to 1653 Time To Live (TTL) issues. TTL issues occur when the 1654 TTL (IPv4) or Hop Limit (IPv6) of the incoming packet was 1655 decremented to zero, or to a value less than 1656 ipMcastInterfaceTtl of the corresponding interface. 1658 The ipMcastInterfaceTtl object is defined in IPMCAST-MIB 1659 [RFC5132] and represents the datagram TTL 1660 threshold for the interface. Any IP multicast datagrams 1661 with a TTL (IPv4) or Hop Limit (IPv6) less than this 1662 threshold will not be forwarded out of the interface. 1663 The default value of 0 means all multicast packets are 1664 forwarded out of the interface. A value of 256 means that 1665 no multicast packets are forwarded out of the interface. 1667 Discontinuities in the value of this counter can 1668 occur at re-initialization of the management system, 1669 and at other times as indicated by the corresponding 1670 mvpnMrouteCounterDiscontinuityTime object. 1671 " 1672 REFERENCE 1673 "RFC5132, Sec. 6 1674 " 1675 ::= { mvpnMrouteEntry 20 } 1677 mvpnMrouteDroppedInOctets OBJECT-TYPE 1678 SYNTAX Counter64 1679 MAX-ACCESS read-only 1680 STATUS current 1681 DESCRIPTION 1682 "The number of octets contained in IP datagrams that this 1683 router has received from sources represented by 1684 this entry and addressed to this multicast group address, 1685 which were dropped due to error(s). 1686 The value of this object includes the octets counted 1687 in the corresponding mvpnMrouteTtlDroppedOctets object. 1689 Discontinuities in the value of this counter can 1690 occur at re-initialization of the management system, 1691 and at other times as indicated by the corresponding 1692 mvpnMrouteCounterDiscontinuityTime object. 1693 " 1694 ::= { mvpnMrouteEntry 21 } 1696 mvpnMrouteDroppedInPackets OBJECT-TYPE 1697 SYNTAX Counter64 1698 MAX-ACCESS read-only 1699 STATUS current 1700 DESCRIPTION 1701 "The number of packets which this router has received from 1702 sources represented by this entry and addressed to this 1703 multicast group address, which were dropped due to error(s). 1704 The value of this object includes the number of octets 1705 counted in the corresponding mvpnMrouteTtlDroppedPackets 1706 object. 1708 Discontinuities in the value of this counter can 1709 occur at re-initialization of the management system, 1710 and at other times as indicated by the corresponding 1711 mvpnMrouteCounterDiscontinuityTime object. 1712 " 1713 ::= { mvpnMrouteEntry 22 } 1715 mvpnMroutePmsiPointer OBJECT-TYPE 1716 SYNTAX RowPointer 1717 MAX-ACCESS read-only 1718 STATUS current 1719 DESCRIPTION 1720 "A pointer to a conceptual row representing 1721 the corresponding I-PMSI in mvpnPmsiTable or S-PMSI 1722 in mvpnSpmsiTable, that this C-multicast route is using. 1723 " 1724 ::= { mvpnMrouteEntry 23 } 1726 mvpnMrouteNumberOfLocalReplication OBJECT-TYPE 1727 SYNTAX Unsigned32 1728 MAX-ACCESS read-only 1729 STATUS current 1730 DESCRIPTION 1731 "Number of replications for local receivers. 1732 For example, if an ingress PE needs to send traffic out of 1733 N PE-CE interfaces, then mvpnMrouteNumberOfLocalReplication 1734 is N. 1735 " 1736 ::= { mvpnMrouteEntry 24 } 1738 mvpnMrouteNumberOfRemoteReplication OBJECT-TYPE 1739 SYNTAX Unsigned32 1740 MAX-ACCESS read-only 1741 STATUS current 1742 DESCRIPTION 1743 "Number of local replications for remote PEs. For example, 1744 if the number of remote PEs that need to receive traffic is N, 1745 then mvpnMrouteNumberOfRemoteReplication is N in case of 1746 Ingress Replication, but may be less than N in case of RSVP-TE 1747 or mLDP P2MP tunnels, depending on the actual number of 1748 replications the PE needs to do. 1749 " 1750 ::= { mvpnMrouteEntry 25 } 1752 mvpnMrouteCounterDiscontinuityTime OBJECT-TYPE 1753 SYNTAX TimeStamp 1754 MAX-ACCESS read-only 1755 STATUS current 1756 DESCRIPTION 1757 "The value of sysUpTime on the most recent occasion 1758 at which any one or more of this application's 1759 counters, viz., counters with OID prefix 1760 'mvpnMrouteOctets' or 'mvpnMroutePkts' or 1761 'mvpnMrouteTtlDroppedOctets' or 1762 'mvpnMrouteTtlDroppedPackets' or 1763 'mvpnMrouteDroppedInOctets' or 'mvpnMrouteDroppedInPackets' 1764 suffered a discontinuity. 1765 If no such discontinuities have occurred since the 1766 last re-initialization of the local management 1767 subsystem, then this object will have a zero value. 1768 " 1769 ::= { mvpnMrouteEntry 26 } 1771 -- Table of next hops for multicast routes in an MVPN 1773 mvpnMrouteNextHopTable OBJECT-TYPE 1774 SYNTAX SEQUENCE OF MvpnMrouteNextHopEntry 1775 MAX-ACCESS not-accessible 1776 STATUS current 1777 DESCRIPTION 1778 "A conceptual table containing information on the 1779 next-hops for routing IP multicast datagrams. 1780 Each entry is one of a list of next-hops for 1781 a set of sources sending to a multicast group 1782 address. 1783 " 1784 ::= { mvpnObjects 8 } 1786 mvpnMrouteNextHopEntry OBJECT-TYPE 1787 SYNTAX MvpnMrouteNextHopEntry 1788 MAX-ACCESS not-accessible 1789 STATUS current 1790 DESCRIPTION 1791 "A conceptual row corresponding to a next-hop to which 1792 IP multicast datagrams from a set of sources to 1793 an IP multicast group address are routed. 1795 Implementers need to be aware that if the total number of 1796 octets in mplsL3VpnVrfName, mvpnMrouteNextHopGroupAddr, 1797 mvpnMrouteNextHopSourceAddrs, and mvpnMrouteNextHopAddr 1798 exceeds 111, the OIDs of column instances in this row 1799 will have more than 128 sub-identifiers and cannot be 1800 accessed using SNMPv1, SNMPv2c, or SNMPv3. 1801 " 1802 INDEX { 1803 mplsL3VpnVrfName, 1804 mvpnMrouteNextHopGroupAddrType, 1805 mvpnMrouteNextHopGroupAddr, 1806 mvpnMrouteNextHopGroupPrefixLength, 1807 mvpnMrouteNextHopSourceAddrType, 1808 mvpnMrouteNextHopSourceAddrs, 1809 mvpnMrouteNextHopSourcePrefixLength, 1810 mvpnMrouteNextHopIfIndex, 1811 mvpnMrouteNextHopAddrType, 1812 mvpnMrouteNextHopAddr 1813 } 1814 ::= { mvpnMrouteNextHopTable 1 } 1816 MvpnMrouteNextHopEntry ::= SEQUENCE { 1817 mvpnMrouteNextHopGroupAddrType InetAddressType, 1818 mvpnMrouteNextHopGroupAddr InetAddress, 1819 mvpnMrouteNextHopGroupPrefixLength InetAddressPrefixLength, 1820 mvpnMrouteNextHopSourceAddrType InetAddressType, 1821 mvpnMrouteNextHopSourceAddrs InetAddress, 1822 mvpnMrouteNextHopSourcePrefixLength InetAddressPrefixLength, 1823 mvpnMrouteNextHopIfIndex InterfaceIndex, 1824 mvpnMrouteNextHopAddrType InetAddressType, 1825 mvpnMrouteNextHopAddr InetAddress, 1826 mvpnMrouteNextHopState INTEGER, 1827 mvpnMrouteNextHopExpiryTime TimeTicks, 1828 mvpnMrouteNextHopClosestMemberHops Unsigned32, 1829 mvpnMrouteNextHopProtocol IANAipMRouteProtocol, 1830 mvpnMrouteNextHopOctets Counter64, 1831 mvpnMrouteNextHopPkts Counter64, 1832 mvpnMrouteNextHopCounterDiscontinuityTime TimeStamp 1833 } 1835 mvpnMrouteNextHopGroupAddrType OBJECT-TYPE 1836 SYNTAX InetAddressType 1837 MAX-ACCESS not-accessible 1838 STATUS current 1839 DESCRIPTION 1840 "The InetAddressType of the mvpnMrouteNextHopGroupAddr object 1841 that follows. 1842 " 1843 ::= { mvpnMrouteNextHopEntry 1 } 1845 mvpnMrouteNextHopGroupAddr OBJECT-TYPE 1846 SYNTAX InetAddress 1847 MAX-ACCESS not-accessible 1848 STATUS current 1849 DESCRIPTION 1850 "The IP multicast group address which, along with 1851 the corresponding mvpnMrouteNextHopGroupPrefixLength object, 1852 identifies destinations for which this entry contains 1853 multicast forwarding information. 1855 This address object is only significant up to 1856 mvpnMrouteNextHopGroupPrefixLength bits. The remaining 1857 address bits MUST be set to zero. 1859 For addresses of type 'ipv4z' or 'ipv6z', the appended zone 1860 index is significant even though it lies beyond the prefix 1861 length. The use of these address types indicate that this 1862 forwarding state applies only within the given zone. Zone 1863 index zero is not valid in this table. 1864 " 1865 ::= { mvpnMrouteNextHopEntry 2 } 1867 mvpnMrouteNextHopGroupPrefixLength OBJECT-TYPE 1868 SYNTAX InetAddressPrefixLength 1869 MAX-ACCESS not-accessible 1870 STATUS current 1871 DESCRIPTION 1872 "The length in bits of the mask which, along with 1873 the corresponding mvpnMrouteGroupAddr object, 1874 identifies destinations for which this entry contains 1875 multicast routing information. 1877 If the corresponding InetAddressType is 'ipv4' or 'ipv4z', 1878 this object must be in the range 4..32. 1879 If the corresponding InetAddressType is 'ipv6' or 'ipv6z', 1880 this object must be in the range 8..128. 1881 " 1882 ::= { mvpnMrouteNextHopEntry 3 } 1884 mvpnMrouteNextHopSourceAddrType OBJECT-TYPE 1885 SYNTAX InetAddressType 1886 MAX-ACCESS not-accessible 1887 STATUS current 1888 DESCRIPTION 1889 "The InetAddressType of mvpnMrouteNextHopSourceAddrs object 1890 that follows. 1892 A value of unknown(0) indicates a non-source-specific entry, 1893 corresponding to all sources in the group. Otherwise, the 1894 value MUST be the same as the value of 1895 mvpnMrouteNextHopGroupAddrType." 1896 ::= { mvpnMrouteNextHopEntry 4 } 1898 mvpnMrouteNextHopSourceAddrs OBJECT-TYPE 1899 SYNTAX InetAddress 1900 MAX-ACCESS not-accessible 1901 STATUS current 1902 DESCRIPTION 1903 "The network address which, along with the 1904 corresponding mvpnMrouteNextHopSourcePrefixLength object, 1905 identifies the sources for which this entry specifies 1906 a next-hop. 1908 This address object is only significant up to 1909 mvpnMrouteNextHopSourcePrefixLength bits. The remaining 1910 address bits MUST be set to zero. 1912 For addresses of type 'ipv4z' or 'ipv6z', the appended zone 1913 index is significant even though it lies beyond the prefix 1914 length. The use of these address types indicate that this 1915 source address applies only within the given zone. Zone 1916 index zero is not valid in this table. 1917 " 1918 ::= { mvpnMrouteNextHopEntry 5 } 1920 mvpnMrouteNextHopSourcePrefixLength OBJECT-TYPE 1921 SYNTAX InetAddressPrefixLength 1922 MAX-ACCESS not-accessible 1923 STATUS current 1924 DESCRIPTION 1925 "The length in bits of the mask which, along with 1926 the corresponding mvpnMrouteNextHopSourceAddrs object, 1927 identifies the sources for which this entry specifies 1928 a next-hop. 1930 If the corresponding InetAddressType is 'ipv4' or 'ipv4z', 1931 this object must be in the range 4..32. 1932 If the corresponding InetAddressType is 'ipv6' or 'ipv6z', 1933 this object must be in the range 8..128. 1934 If the corresponding InetAddressType is 'unknown', 1935 this object must be zero. 1936 " 1937 ::= { mvpnMrouteNextHopEntry 6 } 1939 mvpnMrouteNextHopIfIndex OBJECT-TYPE 1940 SYNTAX InterfaceIndex 1941 MAX-ACCESS not-accessible 1942 STATUS current 1943 DESCRIPTION 1944 "The ifIndex value of the outgoing interface 1945 for this next-hop. 1946 " 1947 ::= { mvpnMrouteNextHopEntry 7 } 1949 mvpnMrouteNextHopAddrType OBJECT-TYPE 1950 SYNTAX InetAddressType 1951 MAX-ACCESS not-accessible 1952 STATUS current 1953 DESCRIPTION 1954 "The InetAddressType of the mvpnMrouteNextHopAddr object 1955 that follows. 1956 " 1957 ::= { mvpnMrouteNextHopEntry 8 } 1959 mvpnMrouteNextHopAddr OBJECT-TYPE 1960 SYNTAX InetAddress 1961 MAX-ACCESS not-accessible 1962 STATUS current 1963 DESCRIPTION 1964 "The address of the next-hop specific to this entry. For 1965 most interfaces, this is identical to 1966 mvpnMrouteNextHopGroupAddr. Non-Broadcast Multi-Access 1967 (NBMA) interfaces, however, may have multiple next-hop 1968 addresses out of a single outgoing interface. 1970 " 1971 ::= { mvpnMrouteNextHopEntry 9 } 1973 mvpnMrouteNextHopState OBJECT-TYPE 1974 SYNTAX INTEGER { 1975 pruned(1), 1976 forwarding(2) 1977 } 1978 MAX-ACCESS read-only 1979 STATUS current 1980 DESCRIPTION 1981 "An indication of whether the outgoing interface and next- 1982 hop represented by this entry is currently being used to 1983 forward IP datagrams. 1985 The enumerated states and the corresponding 1986 descriptions are as follows: 1988 pruned : this entry is not currently being used. 1989 forwarding : this entry is currently being used. 1990 " 1991 ::= { mvpnMrouteNextHopEntry 10 } 1993 mvpnMrouteNextHopExpiryTime OBJECT-TYPE 1994 SYNTAX TimeTicks 1995 MAX-ACCESS read-only 1996 STATUS current 1997 DESCRIPTION 1998 "The minimum amount of time remaining before this entry will 1999 be aged out. If mvpnMrouteNextHopState is pruned(1), 2000 this object represents the remaining time for the prune 2001 to expire after which the state will return to forwarding(2). 2002 If mvpnMrouteNextHopState is forwarding(2), 2003 this object indicates the time after which this 2004 entry will be removed from the table. 2006 The value of 0 indicates that the entry is not subject to 2007 aging. 2008 " 2009 ::= { mvpnMrouteNextHopEntry 11 } 2011 mvpnMrouteNextHopClosestMemberHops OBJECT-TYPE 2012 SYNTAX Unsigned32 (0..256) 2013 MAX-ACCESS read-only 2014 STATUS current 2015 DESCRIPTION 2016 "The minimum number of hops between this router and any 2017 member of this IP multicast group reached via this next-hop 2018 on the corresponding outgoing interface. Any IP multicast 2019 datagram for the group that has a TTL (IPv4) or Hop Count 2020 (IPv6) less than mvpnMrouteNextHopClosestMemberHops will 2021 not be forwarded through this interface. 2023 A value of 0 means all multicast datagrams are forwarded out 2024 of the interface. A value of 256 means that no multicast 2025 datagrams are forwarded out of the interface. 2027 This is an optimization applied by multicast routing 2028 protocols that explicitly track hop counts to downstream 2029 listeners. Multicast protocols that are not aware of hop 2030 counts to downstream listeners set this object to 0. 2031 " 2032 ::= { mvpnMrouteNextHopEntry 12 } 2034 mvpnMrouteNextHopProtocol OBJECT-TYPE 2035 SYNTAX IANAipMRouteProtocol 2036 MAX-ACCESS read-only 2037 STATUS current 2038 DESCRIPTION 2039 "The routing protocol via which this next-hop was learned." 2040 ::= { mvpnMrouteNextHopEntry 13 } 2042 mvpnMrouteNextHopOctets OBJECT-TYPE 2043 SYNTAX Counter64 2044 MAX-ACCESS read-only 2045 STATUS current 2046 DESCRIPTION 2047 "The number of octets of multicast packets that have been 2048 forwarded using this route. 2050 Discontinuities in the value of this counter can 2051 occur at re-initialization of the management system, 2052 and at other times as indicated by the corresponding 2053 mvpnMrouteNextHopCounterDiscontinuityTime object. 2054 " 2055 ::= { mvpnMrouteNextHopEntry 14 } 2057 mvpnMrouteNextHopPkts OBJECT-TYPE 2058 SYNTAX Counter64 2059 MAX-ACCESS read-only 2060 STATUS current 2061 DESCRIPTION 2062 "The number of packets which have been forwarded using this 2063 route. 2065 Discontinuities in the value of this counter can 2066 occur at re-initialization of the management system, 2067 and at other times as indicated by the corresponding 2068 mvpnMrouteNextHopCounterDiscontinuityTime object. 2069 " 2070 ::= { mvpnMrouteNextHopEntry 15 } 2072 mvpnMrouteNextHopCounterDiscontinuityTime OBJECT-TYPE 2073 SYNTAX TimeStamp 2074 MAX-ACCESS read-only 2075 STATUS current 2076 DESCRIPTION 2077 "The value of sysUpTime on the most recent occasion 2078 at which any one or more of this application's 2079 counters, viz., counters with OID prefix 2080 'mvpnMrouteNextHopOctets' or 'mvpnMrouteNextHopPackets' 2081 suffered a discontinuity. 2082 If no such discontinuities have occurred since the 2083 last re-initialization of the local management 2084 subsystem, then this object will have a zero value. 2085 " 2086 ::= { mvpnMrouteNextHopEntry 16 } 2088 -- MVPN Notifications 2090 mvpnMvrfActionTaken NOTIFICATION-TYPE 2091 OBJECTS { 2092 mvpnGenMvrfCreationTime, 2093 mvpnGenMvrfLastAction, 2094 mvpnGenMvrfLastActionTime, 2095 mvpnGenMvrfCreationTime, 2096 mvpnGenCmcastRouteProtocol, 2097 mvpnGenUmhSelection, 2098 mvpnGenCustomerSiteType 2099 } 2100 STATUS current 2101 DESCRIPTION 2102 "mvpnMvrfActionTaken notifies about a change 2103 in a MVRF on the PE. The change itself will be given by 2104 mvpnGenMvrfLastAction. 2105 " 2106 ::= { mvpnNotifications 1 } 2108 -- MVPN MIB Conformance Information 2110 mvpnGroups OBJECT IDENTIFIER ::= { mvpnConformance 1 } 2111 mvpnCompliances OBJECT IDENTIFIER ::= { mvpnConformance 2 } 2113 -- Compliance Statements 2114 mvpnModuleFullCompliance MODULE-COMPLIANCE 2115 STATUS current 2116 DESCRIPTION 2117 "Compliance statement for agents that provide full support 2118 for the BGP-MPLS-LAYER3-VPN-MULTICAST-MIB 2119 " 2120 MODULE -- this module 2121 MANDATORY-GROUPS { 2122 mvpnScalarGroup, 2123 mvpnGenericGroup, 2124 mvpnPmsiGroup, 2125 mvpnAdvtStatsGroup, 2126 mvpnMrouteGroup, 2127 mvpnMrouteNextHopGroup, 2128 mvpnNotificationGroup 2129 } 2131 GROUP mvpnBgpScalarGroup 2132 DESCRIPTION 2133 "This group is mandatory for systems that support 2134 BGP-MVPN. 2135 " 2137 GROUP mvpnBgpGroup 2138 DESCRIPTION 2139 "This group is mandatory for systems that support 2140 BGP-MVPN. 2141 " 2143 ::= { mvpnCompliances 1 } 2145 mvpnModuleReadOnlyCompliance MODULE-COMPLIANCE 2146 STATUS current 2147 DESCRIPTION "Compliance requirement for implementations that 2148 only provide read-only support for 2149 BGP-MPLS-LAYER3-VPN-MULTICAST-MIB. Such devices 2150 can then be monitored but cannot be configured 2151 using this MIB module. 2152 " 2153 MODULE -- this module 2154 MANDATORY-GROUPS { 2155 mvpnScalarGroup, 2156 mvpnGenericGroup, 2157 mvpnPmsiGroup, 2158 mvpnAdvtStatsGroup, 2159 mvpnMrouteGroup, 2160 mvpnMrouteNextHopGroup, 2161 mvpnNotificationGroup 2163 } 2165 GROUP mvpnBgpScalarGroup 2166 DESCRIPTION 2167 "This group is mandatory for systems that support 2168 BGP-MVPN. 2169 " 2171 GROUP mvpnBgpGroup 2172 DESCRIPTION 2173 "This group is mandatory for systems that support 2174 BGP-MVPN. 2175 " 2177 OBJECT mvpnSPTunnelLimit 2178 MIN-ACCESS read-only 2179 DESCRIPTION "Write access is not required." 2181 OBJECT mvpnBgpCmcastRouteWithdrawalTimer 2182 MIN-ACCESS read-only 2183 DESCRIPTION "Write access is not required." 2185 OBJECT mvpnBgpSrcSharedTreeJoinTimer 2186 MIN-ACCESS read-only 2187 DESCRIPTION "Write access is not required." 2189 OBJECT mvpnBgpMsgRateLimit 2190 MIN-ACCESS read-only 2191 DESCRIPTION "Write access is not required." 2193 OBJECT mvpnBgpMaxSpmsiAdRoutes 2194 MIN-ACCESS read-only 2195 DESCRIPTION "Write access is not required." 2197 OBJECT mvpnBgpMaxSpmsiAdRouteFreq 2198 MIN-ACCESS read-only 2199 DESCRIPTION "Write access is not required." 2201 OBJECT mvpnBgpMaxSrcActiveAdRoutes 2202 MIN-ACCESS read-only 2203 DESCRIPTION "Write access is not required." 2205 OBJECT mvpnBgpMaxSrcActiveAdRouteFreq 2206 MIN-ACCESS read-only 2207 DESCRIPTION "Write access is not required." 2209 ::= { mvpnCompliances 2 } 2211 mvpnModuleAdvtStatsCompliance MODULE-COMPLIANCE 2212 STATUS current 2213 DESCRIPTION 2214 "Compliance statement for agents that support 2215 monitoring of the statistics pertaining to 2216 advertisements sent/received by a PE. 2217 " 2218 MODULE -- this module 2219 MANDATORY-GROUPS { 2220 mvpnAdvtStatsGroup 2221 } 2223 ::= { mvpnCompliances 3 } 2225 -- units of conformance 2227 mvpnScalarGroup OBJECT-GROUP 2228 OBJECTS { 2229 mvpnMvrfs, 2230 mvpnV4Mvrfs, 2231 mvpnV6Mvrfs, 2232 mvpnPimV4Mvrfs, 2233 mvpnPimV6Mvrfs, 2234 mvpnSPTunnelLimit 2235 } 2236 STATUS current 2237 DESCRIPTION 2238 "These objects are used to monitor/manage 2239 global statistics and parameters. 2240 " 2241 ::= { mvpnGroups 1 } 2243 mvpnBgpScalarGroup OBJECT-GROUP 2244 OBJECTS { 2245 mvpnMldpMvrfs, 2246 mvpnBgpV4Mvrfs, 2247 mvpnBgpV6Mvrfs, 2248 mvpnBgpCmcastRouteWithdrawalTimer, 2249 mvpnBgpSrcSharedTreeJoinTimer 2250 } 2251 STATUS current 2252 DESCRIPTION 2253 "These objects are used to monitor/manage 2254 BGP-MVPN specific global parameters. 2255 " 2256 ::= { mvpnGroups 2 } 2258 mvpnGenericGroup OBJECT-GROUP 2259 OBJECTS { 2260 mvpnGenMvrfLastAction, 2261 mvpnGenMvrfLastActionTime, 2262 mvpnGenMvrfCreationTime, 2263 mvpnGenCmcastRouteProtocol, 2264 mvpnGenIpmsiInfo, 2265 mvpnGenInterAsPmsiInfo, 2266 mvpnGenUmhSelection, 2267 mvpnGenCustomerSiteType 2268 } 2269 STATUS current 2270 DESCRIPTION 2271 "These objects are used to monitor MVPNs on a PE. 2272 " 2273 ::= { mvpnGroups 3 } 2275 mvpnBgpGroup OBJECT-GROUP 2276 OBJECTS { 2277 mvpnBgpMode, 2278 mvpnBgpVrfRouteImportExtendedCommunity, 2279 mvpnBgpSrcASExtendedCommunity, 2280 mvpnBgpMsgRateLimit, 2281 mvpnBgpMaxSpmsiAdRoutes, 2282 mvpnBgpMaxSpmsiAdRouteFreq, 2283 mvpnBgpMaxSrcActiveAdRoutes, 2284 mvpnBgpMaxSrcActiveAdRouteFreq 2285 } 2286 STATUS current 2287 DESCRIPTION 2288 "These objects are used to monitor/manage 2289 the MVPN-wise BGP specific parameters. 2290 " 2291 ::= { mvpnGroups 4 } 2293 mvpnPmsiGroup OBJECT-GROUP 2294 OBJECTS { 2295 mvpnPmsiRD, 2296 mvpnPmsiTunnelType, 2297 mvpnPmsiTunnelAttribute, 2298 mvpnPmsiTunnelPimGroupAddrType, 2299 mvpnPmsiTunnelPimGroupAddr, 2300 mvpnPmsiEncapsulationType, 2301 mvpnSpmsiPmsiPointer 2302 } 2303 STATUS current 2304 DESCRIPTION 2305 "These objects are used to monitor 2306 I-PMSIs and S-PMSIs tunnel on a PE. 2308 " 2309 ::= { mvpnGroups 5 } 2311 mvpnAdvtStatsGroup OBJECT-GROUP 2312 OBJECTS { 2313 mvpnAdvtSent, 2314 mvpnAdvtReceived, 2315 mvpnAdvtReceivedError, 2316 mvpnAdvtReceivedMalformedTunnelType, 2317 mvpnAdvtReceivedMalformedTunnelId, 2318 mvpnAdvtLastSentTime, 2319 mvpnAdvtLastReceivedTime, 2320 mvpnAdvtCounterDiscontinuityTime 2321 } 2322 STATUS current 2323 DESCRIPTION 2324 "These objects are used to monitor 2325 the statistics pertaining to I-PMSI and S-PMSI 2326 advertisements sent/received by a PE. 2327 " 2328 ::= { mvpnGroups 6 } 2330 mvpnMrouteGroup OBJECT-GROUP 2331 OBJECTS { 2332 mvpnMrouteUpstreamNeighborAddrType, 2333 mvpnMrouteUpstreamNeighborAddr, 2334 mvpnMrouteInIfIndex, 2335 mvpnMrouteExpiryTime, 2336 mvpnMrouteProtocol, 2337 mvpnMrouteRtProtocol, 2338 mvpnMrouteRtAddrType, 2339 mvpnMrouteRtAddr, 2340 mvpnMrouteRtPrefixLength, 2341 mvpnMrouteRtType, 2342 mvpnMrouteOctets, 2343 mvpnMroutePkts, 2344 mvpnMrouteTtlDroppedOctets, 2345 mvpnMrouteTtlDroppedPackets, 2346 mvpnMrouteDroppedInOctets, 2347 mvpnMrouteDroppedInPackets, 2348 mvpnMroutePmsiPointer, 2349 mvpnMrouteNumberOfLocalReplication, 2350 mvpnMrouteNumberOfRemoteReplication, 2351 mvpnMrouteCounterDiscontinuityTime 2352 } 2353 STATUS current 2354 DESCRIPTION 2355 "These objects are used to monitor multicast routing 2356 information corresponding to the MVRFs on a PE. 2357 " 2358 ::= { mvpnGroups 7 } 2360 mvpnMrouteNextHopGroup OBJECT-GROUP 2361 OBJECTS { 2362 mvpnMrouteNextHopState, 2363 mvpnMrouteNextHopExpiryTime, 2364 mvpnMrouteNextHopClosestMemberHops, 2365 mvpnMrouteNextHopProtocol, 2366 mvpnMrouteNextHopOctets, 2367 mvpnMrouteNextHopPkts, 2368 mvpnMrouteNextHopCounterDiscontinuityTime 2369 } 2370 STATUS current 2371 DESCRIPTION 2372 "These objects are used to monitor the information on 2373 next-hops for routing datagrams to MVPNs on a PE. 2374 " 2375 ::= { mvpnGroups 8 } 2377 mvpnNotificationGroup NOTIFICATION-GROUP 2378 NOTIFICATIONS { 2379 mvpnMvrfActionTaken 2380 } 2381 STATUS current 2382 DESCRIPTION 2383 "Objects required for MVPN notifications." 2384 ::= { mvpnGroups 9 } 2386 END 2388 4. Security Considerations 2390 This MIB module contains some read-only objects that may be deemed 2391 sensitive. It also contains some read-write objects, whose setting 2392 will change the device's MVPN related behavior. Appropriate security 2393 procedures related to SNMP in general but not specific to this MIB 2394 module need to be implemented by concerned operators. 2396 There are a number of management objects defined in this MIB module 2397 with a MAX-ACCESS clause of read-write. Such objects may be 2398 considered sensitive or vulnerable in some network environments. The 2399 support for SET operations in a non-secure environment without proper 2400 protection opens devices to attack. These are the tables and objects 2401 and their sensitivity/vulnerability: 2403 o mvpnSPTunnelLimit 2404 The value of this object is used to control the maximum number of 2405 selective provider tunnels that a PE allows for a particular MVPN. 2406 Access to this object may be abused to impact the performance of 2407 the PE or prevent the PE from having new selective provider 2408 tunnels. 2410 o mvpnBgpCmcastRouteWithdrawalTimer 2412 The value of this object is used to control the delay for the 2413 advertisement of withdrawals of C-multicast routes. Access to 2414 this object may be abused to impact the performance of a PE. 2416 o mvpnBgpSrcSharedTreeJoinTimer 2418 The value of this object is used to control the delay for the 2419 advertisement of Source/Shared Tree Join C-multicast routes. 2420 Access to this object may be abused to impact the propagation of 2421 C-multicast routing information. 2423 o mvpnBgpMsgRateLimit 2425 The value of this object is used to control the upper bound for 2426 the rate of BGP C-multicast routing information message exchange 2427 among PEs. Access to this object may be abused to impact the 2428 performance of the PE or disrupt the C-multicast routing 2429 information message exchange using BGP. 2431 o mvpnBgpMaxSpmsiAdRoutes 2433 The value of this object is used to control the upper bound for 2434 the number of S-PMSI A-D routes. Access to this object may be 2435 abused to impact the performance of the PE or prevent the PE from 2436 receiving S-PMSI A-D routes. 2438 o mvpnBgpMaxSpmsiAdRouteFreq 2440 The value of this object is used to control the upper bound for 2441 the frequency of S-PMSI A-D route generation. Access to this 2442 object may be abused to impact the performance of the PE or 2443 prevent the PE from generating new S-PMSI A-D routes. 2445 o mvpnBgpMaxSrcActiveAdRoutes 2447 The value of this object is used to control the upper bound for 2448 the number of Source Active A-D routes. Access to this object may 2449 be abused to impact the performance of the PE or prevent the PE 2450 from receiving Source Active A-D routes. 2452 o mvpnBgpMaxSrcActiveAdRouteFreq 2454 The value of this object is used to control the upper bound for 2455 the frequency of Source Active A-D route generation. Access to 2456 this object may be abused to impact the performance of the PE or 2457 prevent the PE from generating new Source Active A-D routes. 2459 Some of the readable objects in this MIB module (e.g., objects with a 2460 MAX-ACCESS other than not-accessible) may be considered sensitive or 2461 vulnerable in some network environments. It is thus important to 2462 control even GET and/or NOTIFY access to these objects and possibly 2463 to even encrypt the values of these objects when sending them over 2464 the network via SNMP. These are the tables and objects and their 2465 sensitivity/vulnerability: 2467 o The address-related objects in this MIB module may have impact on 2468 privacy and security. These objects may reveal the locations of 2469 senders and recipients. 2471 * mvpnPmsiTunnelPimGroupAddr 2473 * mvpnSpmsiCmcastGroupAddr 2475 * mvpnSpmsiCmcastSourceAddr 2477 * mvpnAdvtPeerAddr 2479 * mvpnMrouteCmcastGroupAddr 2481 * mvpnMrouteCmcastSourceAddrs 2483 * mvpnMrouteUpstreamNeighborAddr 2485 * mvpnMrouteRtAddr 2487 * mvpnMrouteNextHopGroupAddr 2489 * mvpnMrouteNextHopSourceAddrs 2491 * mvpnMrouteNextHopAddr 2493 SNMP versions prior to SNMPv3 did not include adequate security. 2494 Even if the network itself is secure (for example by using IPsec), 2495 there is no control as to who on the secure network is allowed to 2496 access and GET/SET (read/change/create/delete) the objects in this 2497 MIB module. 2499 Implementations SHOULD provide the security features described by the 2500 SNMPv3 framework (see [RFC3410]), and implementations claiming 2501 compliance to the SNMPv3 standard MUST include full support for 2502 authentication and privacy via the User-based Security Model (USM) 2503 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 2504 MAY also provide support for the Transport Security Model (TSM) 2505 [RFC5591] in combination with a secure transport such as SSH 2506 [RFC5592] or TLS/DTLS [RFC6353]. 2508 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2509 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2510 enable cryptographic security. It is then a customer/operator 2511 responsibility to ensure that the SNMP entity giving access to an 2512 instance of this MIB module is properly configured to give access to 2513 the objects only to those principals (users) that have legitimate 2514 rights to indeed GET or SET (change/create/delete) them. 2516 5. IANA Considerations 2518 The MIB module in this document uses the following IANA-assigned 2519 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 2521 Name Description OBJECT IDENTIFIER value 2522 ------- --------------------------------- ---------------------- 2523 mvpnMIB BGP-MPLS-LAYER3-VPN-MULTICAST-MIB { mib-2 AAAA } 2525 Editor's Note (to be removed prior to publication): the IANA is 2526 requested to assign a value for "AAAA" under the 'mib-2' subtree and 2527 to record the assignment in the SMI Numbers registry. When the 2528 assignment has been made, the RFC Editor is asked to replace "AAAA" 2529 (here and in the MIB module) with the assigned value and to remove 2530 this note. 2532 6. Acknowledgement 2534 An earlier draft version of this document was coauthored by Zhaohui 2535 (Jeffrey) Zhang, Saud Asif, Andy Green, Sameer Gulrajani, and Pradeep 2536 G. Jain, based on an earlier draft written by Susheela Vaidya, 2537 Thomas D. Nadeau, and Harmen Van der Linde. 2539 This document also borrows heavily from the design and descriptions 2540 of ipMcastRouteTable and ipMcastRouteNextHopTable from IPMCAST- 2541 MIB[RFC5132]. 2543 Glenn Mansfield Keeni did the MIB Doctor review and provided valuable 2544 comments. 2546 7. References 2548 7.1. Normative References 2550 [RFC2003] Perkins, C., "IP Encapsulation within IP", RFC 2003, DOI 2551 10.17487/RFC2003, October 1996, . 2554 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2555 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 2556 RFC2119, March 1997, . 2559 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2560 Schoenwaelder, Ed., "Structure of Management Information 2561 Version 2 (SMIv2)", STD 58, RFC 2578, DOI 10.17487/ 2562 RFC2578, April 1999, . 2565 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2566 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 2567 58, RFC 2579, DOI 10.17487/RFC2579, April 1999, 2568 . 2570 [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2571 Schoenwaelder, Ed., "Conformance Statements for SMIv2", 2572 STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999, 2573 . 2575 [RFC2784] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. 2576 Traina, "Generic Routing Encapsulation (GRE)", RFC 2784, 2577 DOI 10.17487/RFC2784, March 2000, . 2580 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 2581 MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000, 2582 . 2584 [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., 2585 Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack 2586 Encoding", RFC 3032, DOI 10.17487/RFC3032, January 2001, 2587 . 2589 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 2590 (USM) for version 3 of the Simple Network Management 2591 Protocol (SNMPv3)", STD 62, RFC 3414, DOI 10.17487/ 2592 RFC3414, December 2002, . 2595 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 2596 Advanced Encryption Standard (AES) Cipher Algorithm in the 2597 SNMP User-based Security Model", RFC 3826, DOI 10.17487/ 2598 RFC3826, June 2004, . 2601 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2602 Schoenwaelder, "Textual Conventions for Internet Network 2603 Addresses", RFC 4001, DOI 10.17487/RFC4001, February 2005, 2604 . 2606 [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private 2607 Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February 2608 2006, . 2610 [RFC4382] Nadeau, T., Ed. and H. van der Linde, Ed., "MPLS/BGP Layer 2611 3 Virtual Private Network (VPN) Management Information 2612 Base", RFC 4382, DOI 10.17487/RFC4382, February 2006, 2613 . 2615 [RFC5132] McWalter, D., Thaler, D., and A. Kessler, "IP Multicast 2616 MIB", RFC 5132, DOI 10.17487/RFC5132, December 2007, 2617 . 2619 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 2620 for the Simple Network Management Protocol (SNMP)", STD 2621 78, RFC 5591, DOI 10.17487/RFC5591, June 2009, 2622 . 2624 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 2625 Shell Transport Model for the Simple Network Management 2626 Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June 2627 2009, . 2629 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 2630 Model for the Simple Network Management Protocol (SNMP)", 2631 STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011, 2632 . 2634 [RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/ 2635 BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February 2636 2012, . 2638 [RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP 2639 Encodings and Procedures for Multicast in MPLS/BGP IP 2640 VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012, 2641 . 2643 [RFC6625] Rosen, E., Ed., Rekhter, Y., Ed., Hendrickx, W., and R. 2644 Qiu, "Wildcards in Multicast VPN Auto-Discovery Routes", 2645 RFC 6625, DOI 10.17487/RFC6625, May 2012, 2646 . 2648 [RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I., 2649 Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent 2650 Multicast - Sparse Mode (PIM-SM): Protocol Specification 2651 (Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March 2652 2016, . 2654 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2655 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2656 May 2017, . 2658 [RFCXXXX] Zhang, Z. and H. Tsunoda, "L2L3 VPN Multicast MIB", draft- 2659 ietf-bess-l2l3-vpn-mcast-mib-16 (work in progress), 2660 September 2018. 2662 [RTPROTO] IANA, "IP Route Protocol MIB", 2016, 2663 . 2665 7.2. Informative References 2667 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2668 "Introduction and Applicability Statements for Internet- 2669 Standard Management Framework", RFC 3410, DOI 10.17487/ 2670 RFC3410, December 2002, . 2673 Author's Address 2675 Hiroshi Tsunoda 2676 Tohoku Institute of Technology 2677 35-1, Yagiyama Kasumi-cho, Taihaku-ku 2678 Sendai 982-8577 2679 Japan 2681 Phone: +81-22-305-3411 2682 Email: tsuno@m.ieice.org