idnits 2.17.1 draft-ietf-bess-mvpn-mib-10.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 (August 11, 2018) is 2084 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: 'RFCXXXX' is mentioned on line 235, but not defined -- Possible downref: Non-RFC (?) normative reference: ref. 'RTPROTO' Summary: 0 errors (**), 0 flaws (~~), 2 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 August 11, 2018 5 Expires: February 12, 2019 7 BGP/MPLS Layer 3 VPN Multicast Management Information Base 8 draft-ietf-bess-mvpn-mib-10 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 February 12, 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 . . . . . . . . . . . . . . . . . . . . . . . . 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 . . . . . . . . . . . . . . . . . . . . . . . . . 53 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. MCAST-VPN-MIB 142 This document defines MCAST-VPN-MIB, a MIB module for monitoring and/ 143 or configuring MVPNs on PEs. This MIB module will be used in 144 conjunction with MPLS-L3VPN-STD-MIB [RFC4382] and IPMCAST-MIB 145 [RFC5132]. 147 3.1. Summary of MIB Module 149 MCAST-VPN-MIB provides the following functionalities. 151 o Monitoring attributes of MVPNs on a PE 153 o Configuring timers and thresholds related to an MVPN on a PE 155 o Notifying creation, deletion, and modification of MVRFs on a PE 157 o Monitoring PMSI attributes 159 o Monitoring statistics of advertisements exchanged by a PE 161 o Monitoring routing information for multicast destinations 163 o Monitoring next-hops for each multicast destination 165 To provide these functionalities, MCAST-VPN-MIB defines following 166 tables. 168 o mvpnGenericTable 170 This table contains generic information about MVPNs on a PE. Each 171 entry in this table represents an instance of an MVPN on a PE and 172 contains generic information related to the MVPN. For each entry 173 in this table there MUST be a corresponding VRF in MPLS-L3VPN-STD- 174 MIB [RFC4382]. 176 o mvpnBgpTable 178 This table contains information specific to BGP-MVPNs. Each BGP- 179 MVPN on a PE will have an entry in this table. 181 o mvpnPmsiTable 183 This table contains managed objects representing attribute 184 information that is common to I-PMSIs and S-PMSIs on a PE. 186 o mvpnSpmsiTable 187 This table contains managed objects representing attribute 188 information specific to S-PMSIs. An S-PMSI represented in this 189 table will have a corresponding entry in mvpnPmsiTable. 191 o mvpnAdvtStatsTable 193 This table contains statistics pertaining to I-PMSI and S-PMSI 194 advertisements sent/received. 196 o mvpnMrouteTable 198 This table contains multicast routing information in MVRFs on a 199 PE. 201 o mvpnMrouteNextHopTable 203 This table contains information on the next-hops for routing IP 204 multicast datagrams in MVPNs on a PE. 206 3.2. MIB Module Definitions 208 MCAST-VPN-MIB DEFINITIONS ::= BEGIN 210 IMPORTS 211 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 212 Counter32, Counter64, Gauge32, Unsigned32, TimeTicks, 213 mib-2 214 FROM SNMPv2-SMI -- [RFC2578] 216 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 217 FROM SNMPv2-CONF -- [RFC2580] 219 RowPointer, TimeStamp, DateAndTime 220 FROM SNMPv2-TC -- [RFC2579] 222 InterfaceIndex, InterfaceIndexOrZero 223 FROM IF-MIB -- [RFC2863] 225 InetAddress, InetAddressType, InetAddressPrefixLength 226 FROM INET-ADDRESS-MIB -- [RFC4001] 228 mplsL3VpnVrfName, MplsL3VpnRouteDistinguisher 229 FROM MPLS-L3VPN-STD-MIB -- [RFC4382] 231 IANAipRouteProtocol, IANAipMRouteProtocol 232 FROM IANA-RTPROTO-MIB -- [RTPROTO] 234 L2L3VpnMcastProviderTunnelType 235 FROM L2L3-VPN-MCAST-TC-MIB; -- [RFCXXXX] 237 -- RFC Ed.: replace XXXX with actual RFC number and remove this note 239 mvpnMIB MODULE-IDENTITY 240 LAST-UPDATED "201808101200Z" -- 10th August 2018 12:00:00 GMT 241 ORGANIZATION "IETF BESS Working Group." 242 CONTACT-INFO 243 " Hiroshi Tsunoda 244 Tohoku Institute of Technology 245 35-1, Yagiyama Kasumi-cho 246 Taihaku-ku, Sendai, 982-8577 247 Japan 248 Email: tsuno@m.ieice.org 250 Comments and discussion to bess@ietf.org" 252 DESCRIPTION 253 "This MIB module contains managed object definitions to 254 configure and/or monitor Multicast communication over IP 255 Virtual Private Networks (VPNs) supported by MultiProtocol 256 Label Switching/Border Gateway Protcol (MPLS/BGP) on a 257 Provider Edge router (PE). 258 Copyright (C) The Internet Society (2018). 259 " 261 -- Revision history. 263 REVISION "201808101200Z" -- 10th August, 2018 264 DESCRIPTION 265 "Initial version, published as RFC YYYY." 267 -- RFC Ed. replace YYYY with the actual RFC number and 268 -- remove this note 270 ::= { mib-2 AAAA } 272 -- IANA Reg.: Please assign a value for "AAAA" under the 273 -- 'mib-2' subtree and record the assignment in the SMI 274 -- Numbers registry. 276 -- RFC Ed.: When the above assignment has been made, please 277 -- remove the above note 278 -- replace "AAAA" here with the assigned value and 279 -- remove this note. 281 -- Top level components of this MIB module. 283 mvpnNotifications OBJECT IDENTIFIER ::= { mvpnMIB 0 } 285 -- scalars, tables 286 mvpnObjects OBJECT IDENTIFIER ::= { mvpnMIB 1 } 288 -- conformance information 289 mvpnConformance OBJECT IDENTIFIER ::= { mvpnMIB 2 } 291 -- mvpn Objects 292 mvpnScalars OBJECT IDENTIFIER ::= { mvpnObjects 1 } 294 -- Scalar Objects 296 mvpnMvrfs OBJECT-TYPE 297 SYNTAX Gauge32 298 MAX-ACCESS read-only 299 STATUS current 300 DESCRIPTION 301 "The total number of Multicast Virtual Routing and 302 Forwarding tables (MVRFs) that are present on 303 this Provider Edge router (PE). This includes MVRFs 304 for IPv4, IPv6, and mLDP C-Multicast. 305 " 306 ::= { mvpnScalars 1 } 308 mvpnV4Mvrfs OBJECT-TYPE 309 SYNTAX Gauge32 310 MAX-ACCESS read-only 311 STATUS current 312 DESCRIPTION 313 "The number of MVRFs for IPv4 C-Multicast on this PE. 314 " 315 ::= { mvpnScalars 2 } 317 mvpnV6Mvrfs OBJECT-TYPE 318 SYNTAX Gauge32 319 MAX-ACCESS read-only 320 STATUS current 321 DESCRIPTION 322 "The number of MVRFs for IPv6 C-Multicast on this PE. 323 " 324 ::= { mvpnScalars 3 } 326 mvpnMldpMvrfs OBJECT-TYPE 327 SYNTAX Gauge32 328 MAX-ACCESS read-only 329 STATUS current 330 DESCRIPTION 331 "The number of MVRFs on this PE that use BGP for 332 exchanging Multipoint Label Distribution Protocol (mLDP) 333 C-Multicast routing information. 334 " 335 ::= { mvpnScalars 4 } 337 mvpnPimV4Mvrfs OBJECT-TYPE 338 SYNTAX Gauge32 339 MAX-ACCESS read-only 340 STATUS current 341 DESCRIPTION 342 "The number of MVRFs on this PE that use Provider 343 Independent Multicast (PIM) for exchanging IPv4 344 C-Multicast routing information. 345 " 346 ::= { mvpnScalars 5 } 348 mvpnPimV6Mvrfs OBJECT-TYPE 349 SYNTAX Gauge32 350 MAX-ACCESS read-only 351 STATUS current 352 DESCRIPTION 353 "The number of MVRFs on this PE that use PIM for 354 exchanging IPv6 C-Multicast routing information. 355 " 356 ::= { mvpnScalars 6 } 358 mvpnBgpV4Mvrfs OBJECT-TYPE 359 SYNTAX Gauge32 360 MAX-ACCESS read-only 361 STATUS current 362 DESCRIPTION 363 "The number of MVRFs on this PE that use BGP for 364 exchanging IPv4 C-Multicast routing information. 365 " 366 ::= { mvpnScalars 7 } 368 mvpnBgpV6Mvrfs OBJECT-TYPE 369 SYNTAX Gauge32 370 MAX-ACCESS read-only 371 STATUS current 372 DESCRIPTION 373 "The number of MVRFs on this PE that use BGP for 374 exchanging IPv6 C-Multicast routing information. 375 " 376 ::= { mvpnScalars 8 } 378 mvpnSPTunnelLimit OBJECT-TYPE 379 SYNTAX Unsigned32 (1..4294967295) 380 MAX-ACCESS read-write 381 STATUS current 382 DESCRIPTION 383 "The maximum number of selective provider tunnels that 384 this PE allows for a particular MVPN on this PE. 385 " 386 REFERENCE 387 "RFC6513, Section 13" 388 ::= { mvpnScalars 9 } 390 mvpnBgpCmcastRouteWithdrawalTimer OBJECT-TYPE 391 SYNTAX Unsigned32 392 UNITS "milliseconds" 393 MAX-ACCESS read-write 394 STATUS current 395 DESCRIPTION 396 "A configurable timer to control the delay 397 of C-multicast route withdrawal advertisements. 398 " 399 REFERENCE 400 "RFC6514, Section 16.1.1" 401 ::= { mvpnScalars 10 } 403 mvpnBgpSrcSharedTreeJoinTimer OBJECT-TYPE 404 SYNTAX Unsigned32 405 UNITS "milliseconds" 406 MAX-ACCESS read-write 407 STATUS current 408 DESCRIPTION 409 "A configurable timer to control the delay 410 of Source/Shared Tree Join C-multicast route 411 advertisements. 412 " 413 REFERENCE 414 "RFC6514, Section 16.1.2" 415 ::= { mvpnScalars 11 } 417 -- Generic MVRF Information Table 419 mvpnGenericTable OBJECT-TYPE 420 SYNTAX SEQUENCE OF MvpnGenericEntry 421 MAX-ACCESS not-accessible 422 STATUS current 423 DESCRIPTION 424 "A conceptual table containing generic information about MVPNs 425 on this PE. 426 " 428 ::= { mvpnObjects 2 } 430 mvpnGenericEntry OBJECT-TYPE 431 SYNTAX MvpnGenericEntry 432 MAX-ACCESS not-accessible 433 STATUS current 434 DESCRIPTION 435 "A conceptual row that represents an MVPN on this PE. 436 The MVPN represented by this entry will have one or more 437 corresponding P-Multicast Service Interfaces (PMSIs) 438 and a corresponding VRF in MPLS-L3VPN-STD-MIB [RFC4382]. 439 " 440 INDEX { 441 mplsL3VpnVrfName 442 } 443 ::= { mvpnGenericTable 1 } 445 MvpnGenericEntry ::= SEQUENCE { 446 mvpnGenMvrfLastAction INTEGER, 447 mvpnGenMvrfLastActionTime DateAndTime, 448 mvpnGenMvrfCreationTime DateAndTime, 449 mvpnGenCmcastRouteProtocol INTEGER, 450 mvpnGenIpmsiInfo RowPointer, 451 mvpnGenInterAsPmsiInfo RowPointer, 452 mvpnGenUmhSelection INTEGER, 453 mvpnGenCustomerSiteType INTEGER 454 } 456 mvpnGenMvrfLastAction OBJECT-TYPE 457 SYNTAX INTEGER { 458 createdMvrf (1), 459 deletedMvrf (2), 460 modifiedMvrfIpmsiConfig (3), 461 modifiedMvrfSpmsiConfig (4) 462 } 463 MAX-ACCESS read-only 464 STATUS current 465 DESCRIPTION 466 "This object describes the last action pertaining 467 to the MVPN represented by this entry. 469 The enumerated action types and the corresponding 470 descriptions are as follows: 472 createdMvrf: 473 MVRF was created for this MVPN on the PE. 475 deletedMvrf: 477 MVRF for this MVPN was deleted from the PE. 478 A conceptual row in this table will never have 479 mvpnGenMvrfLastAction equal to deletedMvrf, 480 because in that case the row itself will not exist 481 in the table. 482 This value for mvpnGenMvrfLastAction is defined 483 solely for use in mvpnMvrfActionChange notification. 485 modifiedMvrfIpmsiConfig: 486 an I-PMSI for this MVPN was configured, deleted or 487 changed. 489 modifiedMvrfSpmsiConfig: 490 an S-PMSI for this MVPN was configured, deleted or 491 changed. 492 " 493 ::= { mvpnGenericEntry 2 } 495 mvpnGenMvrfLastActionTime OBJECT-TYPE 496 SYNTAX DateAndTime 497 MAX-ACCESS read-only 498 STATUS current 499 DESCRIPTION 500 "The timestamp when the last action, given in 501 the corresponding mvpnGenMvrfLastAction object, 502 was carried out. 503 " 504 ::= { mvpnGenericEntry 3 } 506 mvpnGenMvrfCreationTime OBJECT-TYPE 507 SYNTAX DateAndTime 508 MAX-ACCESS read-only 509 STATUS current 510 DESCRIPTION 511 "The timestamp when the MVRF was created for 512 the MVPN represented by this entry. 513 " 514 ::= { mvpnGenericEntry 4 } 516 mvpnGenCmcastRouteProtocol OBJECT-TYPE 517 SYNTAX INTEGER { 518 pim (1), 519 bgp (2) 520 } 521 MAX-ACCESS read-only 522 STATUS current 523 DESCRIPTION 524 "The protocol used to signal C-multicast routing 525 information across the provider core for the MVPN 526 represented by this entry. 528 The enumerated protocols and the corresponding 529 descriptions are as follows: 531 pim : PIM (PIM-MVPN) 532 bgp : BGP (BGP-MVPN) 533 " 534 REFERENCE 535 "RFC6513, Section 5" 536 ::= { mvpnGenericEntry 5 } 538 mvpnGenIpmsiInfo OBJECT-TYPE 539 SYNTAX RowPointer 540 MAX-ACCESS read-only 541 STATUS current 542 DESCRIPTION 543 "A pointer to a conceptual row representing 544 the corresponding I-PMSI in mvpnPmsiTable. 545 If there is no I-PMSI for the MVPN 546 represented by this entry, the 547 value of this object will be zeroDotZero. 548 " 549 ::= { mvpnGenericEntry 6 } 551 mvpnGenInterAsPmsiInfo OBJECT-TYPE 552 SYNTAX RowPointer 553 MAX-ACCESS read-only 554 STATUS current 555 DESCRIPTION 556 "A pointer to a conceptual row representing 557 the corresponding segmented Inter-AS I-PMSI in mvpnPmsiTable. 558 If there is no segmented Inter-AS I-PMSI for the MVPN, 559 the value of this object will be zeroDotZero. 560 " 561 ::= { mvpnGenericEntry 7 } 563 mvpnGenUmhSelection OBJECT-TYPE 564 SYNTAX INTEGER { 565 highestPeAddress (1), 566 cRootGroupHashing (2), 567 ucastUmhRoute (3) 568 } 569 MAX-ACCESS read-only 570 STATUS current 571 DESCRIPTION 572 "The Upstream Multicast Hop (UMH) selection method for the MVPN 573 represented by this entry. 575 The enumerated methods and the corresponding 576 descriptions are as follows: 578 highestPeAddress : PE with the highest address 579 (see RFC6513, Section 5.1.3) 580 cRootGroupHashing : hashing based on (c-root, c-group) 581 ucastUmhRoute : per unicast route towards c-root 582 " 583 REFERENCE 584 "RFC6513, Section 5.1" 585 ::= { mvpnGenericEntry 8 } 587 mvpnGenCustomerSiteType OBJECT-TYPE 588 SYNTAX INTEGER { 589 senderReceiver (1), 590 receiverOnly (2), 591 senderOnly (3) 592 } 593 MAX-ACCESS read-only 594 STATUS current 595 DESCRIPTION 596 "The type of the customer site, connected to 597 the MVPN represented by this entry. 599 The enumerated types and the corresponding 600 descriptions are as follows: 602 senderReceiver : Site is both sender and receiver 603 receiverOnly : Site is receiver-only 604 senderOnly : Site is sender-only 605 " 606 REFERENCE 607 "RFC6513, Section 2.3" 608 ::= { mvpnGenericEntry 9 } 610 -- Generic BGP-MVPN table 612 mvpnBgpTable OBJECT-TYPE 613 SYNTAX SEQUENCE OF MvpnBgpEntry 614 MAX-ACCESS not-accessible 615 STATUS current 616 DESCRIPTION 617 "A conceptual table that supplements mvpnGenericTable 618 with BGP-MVPN specific information for BGP-MVPNs on this PE. 619 " 620 ::= { mvpnObjects 3 } 622 mvpnBgpEntry OBJECT-TYPE 623 SYNTAX MvpnBgpEntry 624 MAX-ACCESS not-accessible 625 STATUS current 626 DESCRIPTION 627 "A conceptual row corresponding to a BGP-MVPN on this PE. 628 " 629 INDEX { 630 mplsL3VpnVrfName 631 } 632 ::= { mvpnBgpTable 1 } 634 MvpnBgpEntry ::= SEQUENCE { 635 mvpnBgpMode INTEGER, 636 mvpnBgpVrfRouteImportExtendedCommunity MplsL3VpnRouteDistinguisher, 637 mvpnBgpSrcASExtendedCommunity Unsigned32, 638 mvpnBgpMsgRateLimit Unsigned32, 639 mvpnBgpMaxSpmsiAdRoutes Unsigned32, 640 mvpnBgpMaxSpmsiAdRouteFreq Unsigned32, 641 mvpnBgpMaxSrcActiveAdRoutes Unsigned32, 642 mvpnBgpMaxSrcActiveAdRouteFreq Unsigned32 643 } 645 mvpnBgpMode OBJECT-TYPE 646 SYNTAX INTEGER { 647 other (0), 648 rptSpt (1), 649 sptOnly (2) 650 } 651 MAX-ACCESS read-only 652 STATUS current 653 DESCRIPTION 654 "The inter-site C-tree mode used by the BGP-MVPN 655 represented by this entry. 657 other : none of the following 658 rptSpt : inter-site shared tree mode 659 (Rendezvous Point Tree (RPT) and 660 source-specific shortest-path tree (SPT)) 661 sptOnly : inter-site source-only tree mode 662 " 663 REFERENCE 664 "RFC6513, Section 9.3.1" 665 ::= { mvpnBgpEntry 1 } 667 mvpnBgpVrfRouteImportExtendedCommunity OBJECT-TYPE 668 SYNTAX MplsL3VpnRouteDistinguisher 669 MAX-ACCESS read-only 670 STATUS current 671 DESCRIPTION 672 "The VRF Route Import Extended Community added by this PE 673 to unicast VPN routes that it advertises for the BGP-MVPN 674 corresponding to this entry. 675 " 676 REFERENCE 677 "RFC6514, Section 7 678 " 679 ::= { mvpnBgpEntry 2 } 681 mvpnBgpSrcASExtendedCommunity OBJECT-TYPE 682 SYNTAX Unsigned32 683 MAX-ACCESS read-only 684 STATUS current 685 DESCRIPTION 686 "The Source AS Extended Community added by this PE 687 to the unicast VPN routes that it advertises for 688 the BGP-MVPN represented by this entry. 689 " 690 REFERENCE 691 "RFC6514, Section 6 692 " 693 ::= { mvpnBgpEntry 3 } 695 mvpnBgpMsgRateLimit OBJECT-TYPE 696 SYNTAX Unsigned32 (0..4294967295) 697 UNITS "messages per second" 698 MAX-ACCESS read-write 699 STATUS current 700 DESCRIPTION 701 "The configurable upper bound for the rate of BGP C-multicast 702 routing information message exchange between this PE and other 703 PEs in the BGP-MVPN corresponding to this entry. 704 " 705 REFERENCE 706 "RFC6514, Section 17" 707 ::= { mvpnBgpEntry 4 } 709 mvpnBgpMaxSpmsiAdRoutes OBJECT-TYPE 710 SYNTAX Unsigned32 (0..4294967295) 711 MAX-ACCESS read-write 712 STATUS current 713 DESCRIPTION 714 "The configurable upper bound for the number of 715 S-PMSI A-D routes for the BGP-MVPN corresponding to 716 this entry. 717 " 719 REFERENCE 720 "RFC6514, Section 17" 721 ::= { mvpnBgpEntry 5 } 723 mvpnBgpMaxSpmsiAdRouteFreq OBJECT-TYPE 724 SYNTAX Unsigned32 (0..4294967295) 725 UNITS "routes per second" 726 MAX-ACCESS read-write 727 STATUS current 728 DESCRIPTION 729 "The configurable upper bound for the frequency of 730 S-PMSI A-D route generation for the BGP-MVPN corresponding 731 to this entry. 732 " 733 REFERENCE 734 "RFC6514, Section 17" 735 ::= { mvpnBgpEntry 6 } 737 mvpnBgpMaxSrcActiveAdRoutes OBJECT-TYPE 738 SYNTAX Unsigned32 (0..4294967295) 739 MAX-ACCESS read-write 740 STATUS current 741 DESCRIPTION 742 "The configurable upper bound for the number of 743 Source Active A-D routes for the BGP-MVPN corresponding 744 to this entry. 745 " 746 REFERENCE 747 "RFC6514, Section 17" 748 ::= { mvpnBgpEntry 7 } 750 mvpnBgpMaxSrcActiveAdRouteFreq OBJECT-TYPE 751 SYNTAX Unsigned32 (0..4294967295) 752 UNITS "routes per second" 753 MAX-ACCESS read-write 754 STATUS current 755 DESCRIPTION 756 "The configurable upper bound for the frequency of Source 757 Active A-D route generation for the BGP-MVPN corresponding 758 to this entry. 759 " 760 REFERENCE 761 "RFC6514, Section 17" 762 ::= { mvpnBgpEntry 8 } 764 -- 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. 958 " 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 1055 } 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 " 1103 ::= { mvpnAdvtStatsEntry 2 } 1105 mvpnAdvtPeerAddr OBJECT-TYPE 1106 SYNTAX InetAddress 1107 MAX-ACCESS not-accessible 1108 STATUS current 1109 DESCRIPTION 1110 "The address of a peer PE that exchanges advertisement with 1111 this PE. 1112 " 1113 ::= { mvpnAdvtStatsEntry 3 } 1115 mvpnAdvtSent OBJECT-TYPE 1116 SYNTAX Counter32 1117 MAX-ACCESS read-only 1118 STATUS current 1119 DESCRIPTION 1120 "The number of advertisements successfully 1121 sent to the peer PE specified by the corresponding 1122 mvpnAdvtPeerAddr. 1124 Discontinuities in the value of this counter can 1125 occur at re-initialization of the management system, 1126 and at other times as indicated by the corresponding 1127 mvpnAdvtCounterDiscontinuityTime object. 1128 " 1129 ::= { mvpnAdvtStatsEntry 4 } 1131 mvpnAdvtReceived OBJECT-TYPE 1132 SYNTAX Counter32 1133 MAX-ACCESS read-only 1134 STATUS current 1135 DESCRIPTION 1136 "The number of advertisements received from the peer PE 1137 specified by the corresponding mvpnAdvtPeerAddr object. 1138 This includes advertisements that were discarded. 1140 Discontinuities in the value of this counter can 1141 occur at re-initialization of the management system, 1142 and at other times as indicated by the corresponding 1143 mvpnAdvtCounterDiscontinuityTime object. 1144 " 1145 ::= { mvpnAdvtStatsEntry 5 } 1147 mvpnAdvtReceivedError OBJECT-TYPE 1148 SYNTAX Counter32 1149 MAX-ACCESS read-only 1150 STATUS current 1151 DESCRIPTION 1152 "The total number of advertisements received from a peer PE, 1153 specified by the corresponding mvpnAdvtPeerAddr object, 1154 that were rejected due to error(s) in the advertisement. 1155 The value of this object includes 1156 the error cases counted in the corresponding 1157 mvpnAdvtReceivedMalformedTunnelType and 1158 mvpnAdvtReceivedMalformedTunnelId objects. 1160 Discontinuities in the value of this counter can 1161 occur at re-initialization of the management system, 1162 and at other times as indicated by the corresponding 1163 mvpnAdvtCounterDiscontinuityTime object. 1164 " 1165 ::= { mvpnAdvtStatsEntry 6 } 1167 mvpnAdvtReceivedMalformedTunnelType OBJECT-TYPE 1168 SYNTAX Counter32 1169 MAX-ACCESS read-only 1170 STATUS current 1171 DESCRIPTION 1172 "The total number of advertisements received from the peer PE 1173 specified by the corresponding mvpnAdvtPeerAddr object, 1174 that were rejected due to malformed Tunnel Type 1175 in the PMSI Tunnel attribute. 1177 Discontinuities in the value of this counter can 1178 occur at re-initialization of the management system, 1179 and at other times as indicated by the corresponding 1180 mvpnAdvtCounterDiscontinuityTime object. 1181 " 1182 REFERENCE 1183 "RFC6514 Sec.5" 1184 ::= { mvpnAdvtStatsEntry 7 } 1186 mvpnAdvtReceivedMalformedTunnelId OBJECT-TYPE 1187 SYNTAX Counter32 1188 MAX-ACCESS read-only 1189 STATUS current 1190 DESCRIPTION 1191 "The total number of advertisements received from the peer PE 1192 specified by the corresponding mvpnAdvtPeerAddr object, 1193 that were rejected due to malformed Tunnel Identifier 1194 in the PMSI Tunnel attribute. 1195 Discontinuities in the value of this counter can 1196 occur at re-initialization of the management system, 1197 and at other times as indicated by the corresponding 1198 mvpnAdvtCounterDiscontinuityTime object. 1199 " 1200 REFERENCE 1201 "RFC6514 Sec.5" 1202 ::= { mvpnAdvtStatsEntry 8 } 1204 mvpnAdvtLastSentTime OBJECT-TYPE 1205 SYNTAX DateAndTime 1206 MAX-ACCESS read-only 1207 STATUS current 1208 DESCRIPTION 1209 "The timestamp when the last advertisement 1210 was successfully sent by this PE. 1211 If no advertisement has been sent since the 1212 last re-initialization of this PE, then this 1213 object will have a zero-length string. 1214 " 1215 ::= { mvpnAdvtStatsEntry 9 } 1217 mvpnAdvtLastReceivedTime OBJECT-TYPE 1218 SYNTAX DateAndTime 1219 MAX-ACCESS read-only 1220 STATUS current 1221 DESCRIPTION 1222 "The timestamp when the last advertisement 1223 was successfully received from the peer PE specified 1224 by the corresponding mvpnAdvtPeerAddr object and 1225 processed by this PE. 1226 If no advertisement has been received since the 1227 last re-initialization of this PE, then this 1228 object will have a zero-length string. 1229 " 1230 ::= { mvpnAdvtStatsEntry 10 } 1232 mvpnAdvtCounterDiscontinuityTime OBJECT-TYPE 1233 SYNTAX TimeStamp 1234 MAX-ACCESS read-only 1235 STATUS current 1236 DESCRIPTION 1237 "The value of sysUpTime on the most recent occasion 1238 at which any one or more of this application's 1239 counters, viz., counters with OID prefix 1240 'mvpnAdvtSent' or 1241 'mvpnAdvtReceived' or 1242 'mvpnAdvtReceivedError' or 1243 'mvpnAdvtReceivedMalformedTunnelType' or 1244 'mvpnAdvtReceivedMalformedTunnelId' suffered a 1245 discontinuity. 1246 If no such discontinuities have occurred since the 1247 last re-initialization of the local management 1248 subsystem, then this object will have a zero value. 1250 " 1251 ::= { mvpnAdvtStatsEntry 11 } 1253 -- Table of multicast routes in an MVPN 1255 mvpnMrouteTable OBJECT-TYPE 1256 SYNTAX SEQUENCE OF MvpnMrouteEntry 1257 MAX-ACCESS not-accessible 1258 STATUS current 1259 DESCRIPTION 1260 "A conceptual table containing multicast routing information 1261 corresponding to the MVRFs present on the PE. 1262 " 1263 ::= { mvpnObjects 7 } 1265 mvpnMrouteEntry OBJECT-TYPE 1266 SYNTAX MvpnMrouteEntry 1267 MAX-ACCESS not-accessible 1268 STATUS current 1269 DESCRIPTION 1270 "A conceptual row corresponding to a route for IP datagrams 1271 from a particular source and addressed to a particular IP 1272 multicast group address. 1274 Implementers need to be aware that if the total number of 1275 octets in mplsL3VpnVrfName, mvpnMrouteCmcastGroupAddr and 1276 mvpnMrouteCmcastSourceAddrs exceeds 113, the OIDs of column 1277 instances in this row will have more than 128 sub-identifiers 1278 and cannot be accessed using SNMPv1, SNMPv2c, or SNMPv3. 1279 " 1280 INDEX { 1281 mplsL3VpnVrfName, 1282 mvpnMrouteCmcastGroupAddrType, 1283 mvpnMrouteCmcastGroupAddr, 1284 mvpnMrouteCmcastGroupPrefixLength, 1285 mvpnMrouteCmcastSourceAddrType, 1286 mvpnMrouteCmcastSourceAddrs, 1287 mvpnMrouteCmcastSourcePrefixLength 1288 } 1289 ::= { mvpnMrouteTable 1 } 1291 MvpnMrouteEntry ::= SEQUENCE { 1292 mvpnMrouteCmcastGroupAddrType InetAddressType, 1293 mvpnMrouteCmcastGroupAddr InetAddress, 1294 mvpnMrouteCmcastGroupPrefixLength InetAddressPrefixLength, 1295 mvpnMrouteCmcastSourceAddrType InetAddressType, 1296 mvpnMrouteCmcastSourceAddrs InetAddress, 1297 mvpnMrouteCmcastSourcePrefixLength InetAddressPrefixLength, 1298 mvpnMrouteUpstreamNeighborAddrType InetAddressType, 1299 mvpnMrouteUpstreamNeighborAddr InetAddress, 1300 mvpnMrouteInIfIndex InterfaceIndexOrZero, 1301 mvpnMrouteExpiryTime TimeTicks, 1302 mvpnMrouteProtocol IANAipMRouteProtocol, 1303 mvpnMrouteRtProtocol IANAipRouteProtocol, 1304 mvpnMrouteRtAddrType InetAddressType, 1305 mvpnMrouteRtAddr InetAddress, 1306 mvpnMrouteRtPrefixLength InetAddressPrefixLength, 1307 mvpnMrouteRtType INTEGER, 1308 mvpnMrouteOctets Counter64, 1309 mvpnMroutePkts Counter64, 1310 mvpnMrouteTtlDroppedOctets Counter64, 1311 mvpnMrouteTtlDroppedPackets Counter64, 1312 mvpnMrouteDroppedInOctets Counter64, 1313 mvpnMrouteDroppedInPackets Counter64, 1314 mvpnMroutePmsiPointer RowPointer, 1315 mvpnMrouteNumberOfLocalReplication Unsigned32, 1316 mvpnMrouteNumberOfRemoteReplication Unsigned32, 1317 mvpnMrouteCounterDiscontinuityTime TimeStamp 1318 } 1320 mvpnMrouteCmcastGroupAddrType OBJECT-TYPE 1321 SYNTAX InetAddressType 1322 MAX-ACCESS not-accessible 1323 STATUS current 1324 DESCRIPTION 1325 "The InetAddressType of the mvpnMrouteCmcastGroupAddr object 1326 that follows. 1327 " 1328 ::= { mvpnMrouteEntry 1 } 1330 mvpnMrouteCmcastGroupAddr OBJECT-TYPE 1331 SYNTAX InetAddress 1332 MAX-ACCESS not-accessible 1333 STATUS current 1334 DESCRIPTION 1335 "The IP multicast group address which, along with 1336 the corresponding mvpnMrouteCmcastGroupPrefixLength object, 1337 identifies destinations for which this entry contains 1338 multicast routing information. 1340 This address object is only significant up to 1341 mvpnMrouteCmcastGroupPrefixLength bits. The remaining address 1342 bits MUST be set to zero. 1344 For addresses of type 'ipv4z' or 'ipv6z', the appended zone 1345 index is significant even though it lies beyond the prefix 1346 length. The use of these address types indicate that this 1347 forwarding state applies only within the given zone. Zone 1348 index zero is not valid in this table. 1349 " 1350 ::= { mvpnMrouteEntry 2 } 1352 mvpnMrouteCmcastGroupPrefixLength OBJECT-TYPE 1353 SYNTAX InetAddressPrefixLength 1354 MAX-ACCESS not-accessible 1355 STATUS current 1356 DESCRIPTION 1357 "The length in bits of the mask which, along with 1358 the corresponding mvpnMrouteCmcastGroupAddr object, 1359 identifies destinations for which this entry contains 1360 multicast routing information. 1362 If the corresponding InetAddressType is 'ipv4' or 'ipv4z', 1363 this object must be in the range 4..32. 1364 If the corresponding InetAddressType is 'ipv6' or 'ipv6z', 1365 this object must be in the range 8..128. 1366 " 1367 ::= { mvpnMrouteEntry 3 } 1369 mvpnMrouteCmcastSourceAddrType OBJECT-TYPE 1370 SYNTAX InetAddressType 1371 MAX-ACCESS not-accessible 1372 STATUS current 1373 DESCRIPTION 1374 "The InetAddressType of the mvpnMrouteCmcastSourceAddrs object 1375 that follows. 1377 A value of unknown(0) indicates a non-source-specific entry, 1378 corresponding to all sources in the group. Otherwise, the 1379 value MUST be the same as the value of 1380 mvpnMrouteCmcastGroupAddrType. 1381 " 1382 ::= { mvpnMrouteEntry 4 } 1384 mvpnMrouteCmcastSourceAddrs OBJECT-TYPE 1385 SYNTAX InetAddress 1386 MAX-ACCESS not-accessible 1387 STATUS current 1388 DESCRIPTION 1389 "The network address which, along with the 1390 corresponding mvpnMrouteCmcastSourcePrefixLength object, 1391 identifies the sources for which this entry contains 1392 multicast routing information. 1394 This address object is only significant up to 1395 mvpnMrouteCmcastSourcePrefixLength bits. 1396 The remaining address bits MUST be set to zero. 1398 For addresses of type 'ipv4z' or 'ipv6z', the appended zone 1399 index is significant even though it lies beyond the prefix 1400 length. The use of these address types indicate that this 1401 source address applies only within the given zone. Zone 1402 index zero is not valid in this table. 1403 " 1404 ::= { mvpnMrouteEntry 5 } 1406 mvpnMrouteCmcastSourcePrefixLength OBJECT-TYPE 1407 SYNTAX InetAddressPrefixLength 1408 MAX-ACCESS not-accessible 1409 STATUS current 1410 DESCRIPTION 1411 "The length in bits of the mask which, along with 1412 the corresponding mvpnMrouteCmcastSourceAddr object, 1413 identifies the sources for which this entry contains 1414 multicast routing information. 1416 If the corresponding InetAddressType is 'ipv4' or 'ipv4z', 1417 this object must be in the range 4..32. 1418 If the corresponding InetAddressType is 'ipv6' or 'ipv6z', 1419 this object must be in the range 8..128. 1420 If the corresponding InetAddressType is 'unknown', 1421 this object must be zero. 1422 " 1423 ::= { mvpnMrouteEntry 6 } 1425 mvpnMrouteUpstreamNeighborAddrType OBJECT-TYPE 1426 SYNTAX InetAddressType 1427 MAX-ACCESS read-only 1428 STATUS current 1429 DESCRIPTION 1430 "The InetAddressType of the mvpnMrouteUpstreamNeighborAddr 1431 object that follows. 1433 A value of unknown(0) indicates that the upstream 1434 neighbor is unknown, for example in BIDIR-PIM." 1435 REFERENCE 1436 "RFC 5015" 1437 ::= { mvpnMrouteEntry 7 } 1439 mvpnMrouteUpstreamNeighborAddr OBJECT-TYPE 1440 SYNTAX InetAddress 1441 MAX-ACCESS read-only 1442 STATUS current 1443 DESCRIPTION 1444 "The address of the upstream neighbor (for example, 1445 Reverse Path Forwarding (RPF) neighbor) from which 1446 IP datagrams from these sources represented by 1447 this entry to this multicast address are received. 1448 " 1449 ::= { mvpnMrouteEntry 8 } 1451 mvpnMrouteInIfIndex OBJECT-TYPE 1452 SYNTAX InterfaceIndexOrZero 1453 MAX-ACCESS read-only 1454 STATUS current 1455 DESCRIPTION 1456 "The value of ifIndex for the interface on which IP 1457 datagrams sent by these sources represented by this entry to 1458 this multicast address are received. 1460 A value 0 indicates that datagrams are not 1461 subject to an incoming interface check, but may be accepted 1462 on multiple interfaces (for example, in BIDIR-PIM). 1463 " 1464 REFERENCE 1465 "RFC 5015" 1466 ::= { mvpnMrouteEntry 9 } 1468 mvpnMrouteExpiryTime OBJECT-TYPE 1469 SYNTAX TimeTicks 1470 MAX-ACCESS read-only 1471 STATUS current 1472 DESCRIPTION 1473 "The minimum amount of time remaining before this entry will 1474 be aged out. The value 0 indicates that the entry is not 1475 subject to aging. If the corresponding mvpnMrouteNextHopState 1476 object is pruned(1), this object represents the remaining 1477 time for the prune to expire after which the state will 1478 return to forwarding(2). 1479 If the corresponding mvpnMrouteNextHopState object is 1480 forwarding(2), this object indicates the time after which 1481 this entry will be removed from the table. 1482 " 1483 ::= { mvpnMrouteEntry 10 } 1485 mvpnMrouteProtocol OBJECT-TYPE 1486 SYNTAX IANAipMRouteProtocol 1487 MAX-ACCESS read-only 1488 STATUS current 1489 DESCRIPTION 1490 "The multicast routing protocol via which this multicast 1491 forwarding entry was learned. 1492 " 1493 ::= { mvpnMrouteEntry 11 } 1495 mvpnMrouteRtProtocol OBJECT-TYPE 1496 SYNTAX IANAipRouteProtocol 1497 MAX-ACCESS read-only 1498 STATUS current 1499 DESCRIPTION 1500 "The routing protocol via which the route used to find the 1501 upstream or parent interface for this multicast forwarding 1502 entry was learned. 1503 " 1504 ::= { mvpnMrouteEntry 12 } 1506 mvpnMrouteRtAddrType OBJECT-TYPE 1507 SYNTAX InetAddressType 1508 MAX-ACCESS read-only 1509 STATUS current 1510 DESCRIPTION 1511 "The InetAddressType of the mvpnMrouteRtAddr object 1512 that follows. 1513 " 1514 ::= { mvpnMrouteEntry 13 } 1516 mvpnMrouteRtAddr OBJECT-TYPE 1517 SYNTAX InetAddress 1518 MAX-ACCESS read-only 1519 STATUS current 1520 DESCRIPTION 1521 "The address portion of the route used to find the upstream 1522 or parent interface for this multicast forwarding entry. 1524 This address object is only significant up to 1525 mvpnMrouteRtPrefixLength bits. The remaining address bits 1526 MUST be set to zero. 1528 For addresses of type 'ipv4z' or 'ipv6z', the appended zone 1529 index is significant even though it lies beyond the prefix 1530 length. The use of these address types indicate that this 1531 forwarding state applies only within the given zone. Zone 1532 index zero is not valid in this table. 1533 " 1534 ::= { mvpnMrouteEntry 14 } 1536 mvpnMrouteRtPrefixLength OBJECT-TYPE 1537 SYNTAX InetAddressPrefixLength 1538 MAX-ACCESS read-only 1539 STATUS current 1540 DESCRIPTION 1541 "The length in bits of the mask associated with the route 1542 used to find the upstream or parent interface for this 1543 multicast forwarding entry. 1545 If the corresponding InetAddressType is 'ipv4' or 'ipv4z', 1546 this object must be in the range 4..32. 1547 If the corresponding InetAddressType is 'ipv6' or 'ipv6z', 1548 this object must be in the range 8..128. 1549 " 1550 ::= { mvpnMrouteEntry 15 } 1552 mvpnMrouteRtType OBJECT-TYPE 1553 SYNTAX INTEGER { 1554 unicast (1), 1555 multicast (2) 1556 } 1557 MAX-ACCESS read-only 1558 STATUS current 1559 DESCRIPTION 1560 "The reason for placing the route in the (logical) 1561 multicast Routing Information Base (RIB). 1563 The enumerated reasons and the corresponding 1564 descriptions are as follows: 1566 unicast: 1567 The route would normally be placed only in 1568 the unicast RIB, but was placed in the multicast RIB 1569 by local configuration, such as when running PIM over 1570 RIP. 1572 multicast: 1573 The route was explicitly added to the multicast RIB by 1574 the routing protocol, such as the Distance Vector 1575 Multicast Routing Protocol (DVMRP) or Multiprotocol BGP. 1576 " 1577 ::= { mvpnMrouteEntry 16 } 1579 mvpnMrouteOctets OBJECT-TYPE 1580 SYNTAX Counter64 1581 MAX-ACCESS read-only 1582 STATUS current 1583 DESCRIPTION 1584 "The number of octets contained in IP datagrams that were 1585 received from sources represented by this entry and 1586 addressed to this multicast group address, and which were 1587 forwarded by this router. 1589 Discontinuities in the value of this counter can 1590 occur at re-initialization of the management system, 1591 and at other times as indicated by the corresponding 1592 mvpnMrouteCounterDiscontinuityTime object. 1593 " 1594 ::= { mvpnMrouteEntry 17 } 1596 mvpnMroutePkts OBJECT-TYPE 1597 SYNTAX Counter64 1598 MAX-ACCESS read-only 1599 STATUS current 1600 DESCRIPTION 1601 "The number of packets routed using this multicast route 1602 entry. 1604 Discontinuities in the value of this counter can 1605 occur at re-initialization of the management system, 1606 and at other times as indicated by the corresponding 1607 mvpnMrouteCounterDiscontinuityTime object. 1608 " 1609 ::= { mvpnMrouteEntry 18 } 1611 mvpnMrouteTtlDroppedOctets OBJECT-TYPE 1612 SYNTAX Counter64 1613 MAX-ACCESS read-only 1614 STATUS current 1615 DESCRIPTION 1616 "The number of octets contained in IP datagrams that this 1617 router has received from sources represented by 1618 this entry and addressed to this multicast group address, 1619 which were dropped due to Time To Live (TTL) issues. 1620 TTL issues occur when the TTL (IPv4) or Hop Limit (IPv6) 1621 of the incoming packet was decremented to zero, or to a 1622 value less than ipMcastInterfaceTtl of the corresponding 1623 interface. 1625 The ipMcastInterfaceTtl object is defined in IPMCAST-MIB 1626 [RFC5132] and represents the datagram TTL 1627 threshold for the interface. Any IP multicast datagrams 1628 with a TTL (IPv4) or Hop Limit (IPv6) less than this 1629 threshold will not be forwarded out of the interface. 1630 The default value of 0 means all multicast packets are 1631 forwarded out of the interface. A value of 256 means that 1632 no multicast packets are forwarded out of the interface. 1634 Discontinuities in the value of this counter can 1635 occur at re-initialization of the management system, 1636 and at other times as indicated by the corresponding 1637 mvpnMrouteCounterDiscontinuityTime object. 1638 " 1639 REFERENCE 1640 "RFC5132, Sec. 6 1641 " 1642 ::= { mvpnMrouteEntry 19 } 1644 mvpnMrouteTtlDroppedPackets OBJECT-TYPE 1645 SYNTAX Counter64 1646 MAX-ACCESS read-only 1647 STATUS current 1648 DESCRIPTION 1649 "The number of packets that this router has received from 1650 the sources represented by this entry and addressed to this 1651 multicast group address, which were dropped due to 1652 Time To Live (TTL) issues. TTL issues occur when the 1653 TTL (IPv4) or Hop Limit (IPv6) of the incoming packet was 1654 decremented to zero, or to a value less than 1655 ipMcastInterfaceTtl of the corresponding interface. 1657 The ipMcastInterfaceTtl object is defined in IPMCAST-MIB 1658 [RFC5132] and represents the datagram TTL 1659 threshold for the interface. Any IP multicast datagrams 1660 with a TTL (IPv4) or Hop Limit (IPv6) less than this 1661 threshold will not be forwarded out of the interface. 1662 The default value of 0 means all multicast packets are 1663 forwarded out of the interface. A value of 256 means that 1664 no multicast packets are forwarded out of the interface. 1666 Discontinuities in the value of this counter can 1667 occur at re-initialization of the management system, 1668 and at other times as indicated by the corresponding 1669 mvpnMrouteCounterDiscontinuityTime object. 1670 " 1671 REFERENCE 1672 "RFC5132, Sec. 6 1673 " 1674 ::= { mvpnMrouteEntry 20 } 1676 mvpnMrouteDroppedInOctets OBJECT-TYPE 1677 SYNTAX Counter64 1678 MAX-ACCESS read-only 1679 STATUS current 1680 DESCRIPTION 1681 "The number of octets contained in IP datagrams that this 1682 router has received from sources represented by 1683 this entry and addressed to this multicast group address, 1684 which were dropped due to error(s). 1685 The value of this object includes the octets counted 1686 in the corresponding mvpnMrouteTtlDroppedOctets object. 1688 Discontinuities in the value of this counter can 1689 occur at re-initialization of the management system, 1690 and at other times as indicated by the corresponding 1691 mvpnMrouteCounterDiscontinuityTime object. 1692 " 1693 ::= { mvpnMrouteEntry 21 } 1695 mvpnMrouteDroppedInPackets OBJECT-TYPE 1696 SYNTAX Counter64 1697 MAX-ACCESS read-only 1698 STATUS current 1699 DESCRIPTION 1700 "The number of packets which this router has received from 1701 sources represented by this entry and addressed to this 1702 multicast group address, which were dropped due to error(s). 1703 The value of this object includes the number of octets 1704 counted in the corresponding mvpnMrouteTtlDroppedPackets 1705 object. 1707 Discontinuities in the value of this counter can 1708 occur at re-initialization of the management system, 1709 and at other times as indicated by the corresponding 1710 mvpnMrouteCounterDiscontinuityTime object. 1711 " 1712 ::= { mvpnMrouteEntry 22 } 1714 mvpnMroutePmsiPointer OBJECT-TYPE 1715 SYNTAX RowPointer 1716 MAX-ACCESS read-only 1717 STATUS current 1718 DESCRIPTION 1719 "A pointer to a conceptual row representing 1720 the corresponding I-PMSI in mvpnPmsiTable or S-PMSI 1721 in mvpnSpmsiTable, that this C-multicast route is using. 1722 " 1723 ::= { mvpnMrouteEntry 23 } 1725 mvpnMrouteNumberOfLocalReplication OBJECT-TYPE 1726 SYNTAX Unsigned32 1727 MAX-ACCESS read-only 1728 STATUS current 1729 DESCRIPTION 1730 "Number of replications for local receivers. 1731 For example, if an ingress PE needs to send traffic out of 1732 N PE-CE interfaces, then mvpnMrouteNumberOfLocalReplication 1733 is N. 1734 " 1735 ::= { mvpnMrouteEntry 24 } 1737 mvpnMrouteNumberOfRemoteReplication OBJECT-TYPE 1738 SYNTAX Unsigned32 1739 MAX-ACCESS read-only 1740 STATUS current 1741 DESCRIPTION 1742 "Number of local replications for remote PEs. For example, 1743 if the number of remote PEs that need to receive traffic is N, 1744 then mvpnMrouteNumberOfRemoteReplication is N in case of 1745 Ingress Replication, but may be less than N in case of RSVP-TE 1746 or mLDP P2MP tunnels, depending on the actual number of 1747 replications the PE needs to do. 1748 " 1749 ::= { mvpnMrouteEntry 25 } 1751 mvpnMrouteCounterDiscontinuityTime OBJECT-TYPE 1752 SYNTAX TimeStamp 1753 MAX-ACCESS read-only 1754 STATUS current 1755 DESCRIPTION 1756 "The value of sysUpTime on the most recent occasion 1757 at which any one or more of this application's 1758 counters, viz., counters with OID prefix 1759 'mvpnMrouteOctets' or 'mvpnMroutePkts' or 1760 'mvpnMrouteTtlDroppedOctets' or 1761 'mvpnMrouteTtlDroppedPackets' or 1762 'mvpnMrouteDroppedInOctets' or 'mvpnMrouteDroppedInPackets' 1763 suffered a discontinuity. 1764 If no such discontinuities have occurred since the 1765 last re-initialization of the local management 1766 subsystem, then this object will have a zero value. 1767 " 1768 ::= { mvpnMrouteEntry 26 } 1770 -- Table of next hops for multicast routes in an MVPN 1772 mvpnMrouteNextHopTable OBJECT-TYPE 1773 SYNTAX SEQUENCE OF MvpnMrouteNextHopEntry 1774 MAX-ACCESS not-accessible 1775 STATUS current 1776 DESCRIPTION 1777 "A conceptual table containing information on the 1778 next-hops for routing IP multicast datagrams. 1779 Each entry is one of a list of next-hops for 1780 a set of sources sending to a multicast group 1781 address. 1782 " 1783 ::= { mvpnObjects 8 } 1785 mvpnMrouteNextHopEntry OBJECT-TYPE 1786 SYNTAX MvpnMrouteNextHopEntry 1787 MAX-ACCESS not-accessible 1788 STATUS current 1789 DESCRIPTION 1790 "A conceptual row corresponding to a next-hop to which 1791 IP multicast datagrams from a set of sources to 1792 an IP multicast group address are routed. 1794 Implementers need to be aware that if the total number of 1795 octets in mplsL3VpnVrfName, mvpnMrouteNextHopGroupAddr, 1796 mvpnMrouteNextHopSourceAddrs, and mvpnMrouteNextHopAddr 1797 exceeds 111, the OIDs of column instances in this row 1798 will have more than 128 sub-identifiers and cannot be 1799 accessed using SNMPv1, SNMPv2c, or SNMPv3. 1800 " 1801 INDEX { 1802 mplsL3VpnVrfName, 1803 mvpnMrouteNextHopGroupAddrType, 1804 mvpnMrouteNextHopGroupAddr, 1805 mvpnMrouteNextHopGroupPrefixLength, 1806 mvpnMrouteNextHopSourceAddrType, 1807 mvpnMrouteNextHopSourceAddrs, 1808 mvpnMrouteNextHopSourcePrefixLength, 1809 mvpnMrouteNextHopIfIndex, 1810 mvpnMrouteNextHopAddrType, 1811 mvpnMrouteNextHopAddr 1812 } 1813 ::= { mvpnMrouteNextHopTable 1 } 1815 MvpnMrouteNextHopEntry ::= SEQUENCE { 1816 mvpnMrouteNextHopGroupAddrType InetAddressType, 1817 mvpnMrouteNextHopGroupAddr InetAddress, 1818 mvpnMrouteNextHopGroupPrefixLength InetAddressPrefixLength, 1819 mvpnMrouteNextHopSourceAddrType InetAddressType, 1820 mvpnMrouteNextHopSourceAddrs InetAddress, 1821 mvpnMrouteNextHopSourcePrefixLength InetAddressPrefixLength, 1822 mvpnMrouteNextHopIfIndex InterfaceIndex, 1823 mvpnMrouteNextHopAddrType InetAddressType, 1824 mvpnMrouteNextHopAddr InetAddress, 1825 mvpnMrouteNextHopState INTEGER, 1826 mvpnMrouteNextHopExpiryTime TimeTicks, 1827 mvpnMrouteNextHopClosestMemberHops Unsigned32, 1828 mvpnMrouteNextHopProtocol IANAipMRouteProtocol, 1829 mvpnMrouteNextHopOctets Counter64, 1830 mvpnMrouteNextHopPkts Counter64, 1831 mvpnMrouteNextHopCounterDiscontinuityTime TimeStamp 1832 } 1834 mvpnMrouteNextHopGroupAddrType OBJECT-TYPE 1835 SYNTAX InetAddressType 1836 MAX-ACCESS not-accessible 1837 STATUS current 1838 DESCRIPTION 1839 "The InetAddressType of the mvpnMrouteNextHopGroupAddr object 1840 that follows. 1841 " 1842 ::= { mvpnMrouteNextHopEntry 1 } 1844 mvpnMrouteNextHopGroupAddr OBJECT-TYPE 1845 SYNTAX InetAddress 1846 MAX-ACCESS not-accessible 1847 STATUS current 1848 DESCRIPTION 1849 "The IP multicast group address which, along with 1850 the corresponding mvpnMrouteNextHopGroupPrefixLength object, 1851 identifies destinations for which this entry contains 1852 multicast forwarding information. 1854 This address object is only significant up to 1855 mvpnMrouteNextHopGroupPrefixLength bits. The remaining 1856 address bits MUST be set to zero. 1858 For addresses of type 'ipv4z' or 'ipv6z', the appended zone 1859 index is significant even though it lies beyond the prefix 1860 length. The use of these address types indicate that this 1861 forwarding state applies only within the given zone. Zone 1862 index zero is not valid in this table. 1863 " 1864 ::= { mvpnMrouteNextHopEntry 2 } 1866 mvpnMrouteNextHopGroupPrefixLength OBJECT-TYPE 1867 SYNTAX InetAddressPrefixLength 1868 MAX-ACCESS not-accessible 1869 STATUS current 1870 DESCRIPTION 1871 "The length in bits of the mask which, along with 1872 the corresponding mvpnMrouteGroupAddr object, 1873 identifies destinations for which this entry contains 1874 multicast routing information. 1876 If the corresponding InetAddressType is 'ipv4' or 'ipv4z', 1877 this object must be in the range 4..32. 1878 If the corresponding InetAddressType is 'ipv6' or 'ipv6z', 1879 this object must be in the range 8..128. 1880 " 1881 ::= { mvpnMrouteNextHopEntry 3 } 1883 mvpnMrouteNextHopSourceAddrType OBJECT-TYPE 1884 SYNTAX InetAddressType 1885 MAX-ACCESS not-accessible 1886 STATUS current 1887 DESCRIPTION 1888 "The InetAddressType of mvpnMrouteNextHopSourceAddrs object 1889 that follows. 1891 A value of unknown(0) indicates a non-source-specific entry, 1892 corresponding to all sources in the group. Otherwise, the 1893 value MUST be the same as the value of 1894 mvpnMrouteNextHopGroupAddrType." 1895 ::= { mvpnMrouteNextHopEntry 4 } 1897 mvpnMrouteNextHopSourceAddrs OBJECT-TYPE 1898 SYNTAX InetAddress 1899 MAX-ACCESS not-accessible 1900 STATUS current 1901 DESCRIPTION 1902 "The network address which, along with the 1903 corresponding mvpnMrouteNextHopSourcePrefixLength object, 1904 identifies the sources for which this entry specifies 1905 a next-hop. 1907 This address object is only significant up to 1908 mvpnMrouteNextHopSourcePrefixLength bits. The remaining 1909 address bits MUST be set to zero. 1911 For addresses of type 'ipv4z' or 'ipv6z', the appended zone 1912 index is significant even though it lies beyond the prefix 1913 length. The use of these address types indicate that this 1914 source address applies only within the given zone. Zone 1915 index zero is not valid in this table. 1916 " 1917 ::= { mvpnMrouteNextHopEntry 5 } 1919 mvpnMrouteNextHopSourcePrefixLength OBJECT-TYPE 1920 SYNTAX InetAddressPrefixLength 1921 MAX-ACCESS not-accessible 1922 STATUS current 1923 DESCRIPTION 1924 "The length in bits of the mask which, along with 1925 the corresponding mvpnMrouteNextHopSourceAddrs object, 1926 identifies the sources for which this entry specifies 1927 a next-hop. 1929 If the corresponding InetAddressType is 'ipv4' or 'ipv4z', 1930 this object must be in the range 4..32. 1931 If the corresponding InetAddressType is 'ipv6' or 'ipv6z', 1932 this object must be in the range 8..128. 1933 If the corresponding InetAddressType is 'unknown', 1934 this object must be zero. 1935 " 1936 ::= { mvpnMrouteNextHopEntry 6 } 1938 mvpnMrouteNextHopIfIndex OBJECT-TYPE 1939 SYNTAX InterfaceIndex 1940 MAX-ACCESS not-accessible 1941 STATUS current 1942 DESCRIPTION 1943 "The ifIndex value of the outgoing interface 1944 for this next-hop. 1945 " 1946 ::= { mvpnMrouteNextHopEntry 7 } 1948 mvpnMrouteNextHopAddrType OBJECT-TYPE 1949 SYNTAX InetAddressType 1950 MAX-ACCESS not-accessible 1951 STATUS current 1952 DESCRIPTION 1953 "The InetAddressType of the mvpnMrouteNextHopAddr object 1954 that follows. 1955 " 1956 ::= { mvpnMrouteNextHopEntry 8 } 1958 mvpnMrouteNextHopAddr OBJECT-TYPE 1959 SYNTAX InetAddress 1960 MAX-ACCESS not-accessible 1961 STATUS current 1962 DESCRIPTION 1963 "The address of the next-hop specific to this entry. For 1964 most interfaces, this is identical to 1965 mvpnMrouteNextHopGroupAddr. Non-Broadcast Multi-Access 1966 (NBMA) interfaces, however, may have multiple next-hop 1967 addresses out of a single outgoing interface. 1968 " 1969 ::= { mvpnMrouteNextHopEntry 9 } 1971 mvpnMrouteNextHopState OBJECT-TYPE 1972 SYNTAX INTEGER { 1973 pruned(1), 1974 forwarding(2) 1975 } 1976 MAX-ACCESS read-only 1977 STATUS current 1978 DESCRIPTION 1979 "An indication of whether the outgoing interface and next- 1980 hop represented by this entry is currently being used to 1981 forward IP datagrams. 1983 The enumerated states and the corresponding 1984 descriptions are as follows: 1986 pruned : this entry is not currently being used. 1987 forwarding : this entry is currently being used. 1988 " 1989 ::= { mvpnMrouteNextHopEntry 10 } 1991 mvpnMrouteNextHopExpiryTime OBJECT-TYPE 1992 SYNTAX TimeTicks 1993 MAX-ACCESS read-only 1994 STATUS current 1995 DESCRIPTION 1996 "The minimum amount of time remaining before this entry will 1997 be aged out. If mvpnMrouteNextHopState is pruned(1), 1998 this object represents the remaining time for the prune 1999 to expire after which the state will return to forwarding(2). 2000 If mvpnMrouteNextHopState is forwarding(2), 2001 this object indicates the time after which this 2002 entry will be removed from the table. 2004 The value of 0 indicates that the entry is not subject to 2005 aging. 2006 " 2007 ::= { mvpnMrouteNextHopEntry 11 } 2009 mvpnMrouteNextHopClosestMemberHops OBJECT-TYPE 2010 SYNTAX Unsigned32 (0..256) 2011 MAX-ACCESS read-only 2012 STATUS current 2013 DESCRIPTION 2014 "The minimum number of hops between this router and any 2015 member of this IP multicast group reached via this next-hop 2016 on the corresponding outgoing interface. Any IP multicast 2017 datagram for the group that has a TTL (IPv4) or Hop Count 2018 (IPv6) less than mvpnMrouteNextHopClosestMemberHops will 2019 not be forwarded through this interface. 2021 A value of 0 means all multicast datagrams are forwarded out 2022 of the interface. A value of 256 means that no multicast 2023 datagrams are forwarded out of the interface. 2025 This is an optimization applied by multicast routing 2026 protocols that explicitly track hop counts to downstream 2027 listeners. Multicast protocols that are not aware of hop 2028 counts to downstream listeners set this object to 0. 2029 " 2030 ::= { mvpnMrouteNextHopEntry 12 } 2032 mvpnMrouteNextHopProtocol OBJECT-TYPE 2033 SYNTAX IANAipMRouteProtocol 2034 MAX-ACCESS read-only 2035 STATUS current 2036 DESCRIPTION 2037 "The routing protocol via which this next-hop was learned." 2038 ::= { mvpnMrouteNextHopEntry 13 } 2040 mvpnMrouteNextHopOctets OBJECT-TYPE 2041 SYNTAX Counter64 2042 MAX-ACCESS read-only 2043 STATUS current 2044 DESCRIPTION 2045 "The number of octets of multicast packets that have been 2046 forwarded using this route. 2048 Discontinuities in the value of this counter can 2049 occur at re-initialization of the management system, 2050 and at other times as indicated by the corresponding 2051 mvpnMrouteNextHopCounterDiscontinuityTime object. 2052 " 2053 ::= { mvpnMrouteNextHopEntry 14 } 2055 mvpnMrouteNextHopPkts OBJECT-TYPE 2056 SYNTAX Counter64 2057 MAX-ACCESS read-only 2058 STATUS current 2059 DESCRIPTION 2060 "The number of packets which have been forwarded using this 2061 route. 2063 Discontinuities in the value of this counter can 2064 occur at re-initialization of the management system, 2065 and at other times as indicated by the corresponding 2066 mvpnMrouteNextHopCounterDiscontinuityTime object. 2068 " 2069 ::= { mvpnMrouteNextHopEntry 15 } 2071 mvpnMrouteNextHopCounterDiscontinuityTime OBJECT-TYPE 2072 SYNTAX TimeStamp 2073 MAX-ACCESS read-only 2074 STATUS current 2075 DESCRIPTION 2076 "The value of sysUpTime on the most recent occasion 2077 at which any one or more of this application's 2078 counters, viz., counters with OID prefix 2079 'mvpnMrouteNextHopOctets' or 'mvpnMrouteNextHopPackets' 2080 suffered a discontinuity. 2081 If no such discontinuities have occurred since the 2082 last re-initialization of the local management 2083 subsystem, then this object will have a zero value. 2084 " 2085 ::= { mvpnMrouteNextHopEntry 16 } 2087 -- MVPN Notifications 2089 mvpnMvrfActionTaken NOTIFICATION-TYPE 2090 OBJECTS { 2091 mvpnGenMvrfCreationTime, 2092 mvpnGenMvrfLastAction, 2093 mvpnGenMvrfLastActionTime, 2094 mvpnGenMvrfCreationTime, 2095 mvpnGenCmcastRouteProtocol, 2096 mvpnGenUmhSelection, 2097 mvpnGenCustomerSiteType 2098 } 2099 STATUS current 2100 DESCRIPTION 2101 "mvpnMvrfActionTaken notifies about a change 2102 in a MVRF on the PE. The change itself will be given by 2103 mvpnGenMvrfLastAction. 2104 " 2105 ::= { mvpnNotifications 1 } 2107 -- MVPN MIB Conformance Information 2109 mvpnGroups OBJECT IDENTIFIER ::= { mvpnConformance 1 } 2110 mvpnCompliances OBJECT IDENTIFIER ::= { mvpnConformance 2 } 2112 -- Compliance Statements 2114 mvpnModuleFullCompliance MODULE-COMPLIANCE 2115 STATUS current 2116 DESCRIPTION 2117 "Compliance statement for agents that provide full support 2118 for the MCAST-VPN-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 MCAST-VPN-MIB. 2149 Such devices can then be monitored but cannot be 2150 configured using this MIB module. 2151 " 2152 MODULE -- this module 2153 MANDATORY-GROUPS { 2154 mvpnScalarGroup, 2155 mvpnGenericGroup, 2156 mvpnPmsiGroup, 2157 mvpnAdvtStatsGroup, 2158 mvpnMrouteGroup, 2159 mvpnMrouteNextHopGroup, 2160 mvpnNotificationGroup 2161 } 2162 GROUP mvpnBgpScalarGroup 2163 DESCRIPTION 2164 "This group is mandatory for systems that support 2165 BGP-MVPN. 2166 " 2168 GROUP mvpnBgpGroup 2169 DESCRIPTION 2170 "This group is mandatory for systems that support 2171 BGP-MVPN. 2172 " 2174 OBJECT mvpnSPTunnelLimit 2175 MIN-ACCESS read-only 2176 DESCRIPTION "Write access is not required." 2178 OBJECT mvpnBgpCmcastRouteWithdrawalTimer 2179 MIN-ACCESS read-only 2180 DESCRIPTION "Write access is not required." 2182 OBJECT mvpnBgpSrcSharedTreeJoinTimer 2183 MIN-ACCESS read-only 2184 DESCRIPTION "Write access is not required." 2186 OBJECT mvpnBgpMsgRateLimit 2187 MIN-ACCESS read-only 2188 DESCRIPTION "Write access is not required." 2190 OBJECT mvpnBgpMaxSpmsiAdRoutes 2191 MIN-ACCESS read-only 2192 DESCRIPTION "Write access is not required." 2194 OBJECT mvpnBgpMaxSpmsiAdRouteFreq 2195 MIN-ACCESS read-only 2196 DESCRIPTION "Write access is not required." 2198 OBJECT mvpnBgpMaxSrcActiveAdRoutes 2199 MIN-ACCESS read-only 2200 DESCRIPTION "Write access is not required." 2202 OBJECT mvpnBgpMaxSrcActiveAdRouteFreq 2203 MIN-ACCESS read-only 2204 DESCRIPTION "Write access is not required." 2206 ::= { mvpnCompliances 2 } 2208 mvpnModuleAdvtStatsCompliance MODULE-COMPLIANCE 2209 STATUS current 2210 DESCRIPTION 2211 "Compliance statement for agents that support 2212 monitoring of the statistics pertaining to 2213 advertisements sent/received by a PE. 2214 " 2215 MODULE -- this module 2216 MANDATORY-GROUPS { 2217 mvpnAdvtStatsGroup 2218 } 2220 ::= { mvpnCompliances 3 } 2222 -- units of conformance 2224 mvpnScalarGroup OBJECT-GROUP 2225 OBJECTS { 2226 mvpnMvrfs, 2227 mvpnV4Mvrfs, 2228 mvpnV6Mvrfs, 2229 mvpnPimV4Mvrfs, 2230 mvpnPimV6Mvrfs, 2231 mvpnSPTunnelLimit 2232 } 2233 STATUS current 2234 DESCRIPTION 2235 "These objects are used to monitor/manage 2236 global statistics and parameters. 2237 " 2238 ::= { mvpnGroups 1 } 2240 mvpnBgpScalarGroup OBJECT-GROUP 2241 OBJECTS { 2242 mvpnMldpMvrfs, 2243 mvpnBgpV4Mvrfs, 2244 mvpnBgpV6Mvrfs, 2245 mvpnBgpCmcastRouteWithdrawalTimer, 2246 mvpnBgpSrcSharedTreeJoinTimer 2247 } 2248 STATUS current 2249 DESCRIPTION 2250 "These objects are used to monitor/manage 2251 BGP-MVPN specific global parameters. 2252 " 2253 ::= { mvpnGroups 2 } 2255 mvpnGenericGroup OBJECT-GROUP 2256 OBJECTS { 2257 mvpnGenMvrfLastAction, 2258 mvpnGenMvrfLastActionTime, 2259 mvpnGenMvrfCreationTime, 2260 mvpnGenCmcastRouteProtocol, 2261 mvpnGenIpmsiInfo, 2262 mvpnGenInterAsPmsiInfo, 2263 mvpnGenUmhSelection, 2264 mvpnGenCustomerSiteType 2265 } 2266 STATUS current 2267 DESCRIPTION 2268 "These objects are used to monitor MVPNs on a PE. 2269 " 2270 ::= { mvpnGroups 3 } 2272 mvpnBgpGroup OBJECT-GROUP 2273 OBJECTS { 2274 mvpnBgpMode, 2275 mvpnBgpVrfRouteImportExtendedCommunity, 2276 mvpnBgpSrcASExtendedCommunity, 2277 mvpnBgpMsgRateLimit, 2278 mvpnBgpMaxSpmsiAdRoutes, 2279 mvpnBgpMaxSpmsiAdRouteFreq, 2280 mvpnBgpMaxSrcActiveAdRoutes, 2281 mvpnBgpMaxSrcActiveAdRouteFreq 2282 } 2283 STATUS current 2284 DESCRIPTION 2285 "These objects are used to monitor/manage 2286 the MVPN-wise BGP specific parameters. 2287 " 2288 ::= { mvpnGroups 4 } 2290 mvpnPmsiGroup OBJECT-GROUP 2291 OBJECTS { 2292 mvpnPmsiRD, 2293 mvpnPmsiTunnelType, 2294 mvpnPmsiTunnelAttribute, 2295 mvpnPmsiTunnelPimGroupAddrType, 2296 mvpnPmsiTunnelPimGroupAddr, 2297 mvpnPmsiEncapsulationType, 2298 mvpnSpmsiPmsiPointer 2299 } 2300 STATUS current 2301 DESCRIPTION 2302 "These objects are used to monitor 2303 I-PMSIs and S-PMSIs tunnel on a PE. 2304 " 2305 ::= { mvpnGroups 5 } 2307 mvpnAdvtStatsGroup OBJECT-GROUP 2308 OBJECTS { 2309 mvpnAdvtSent, 2310 mvpnAdvtReceived, 2311 mvpnAdvtReceivedError, 2312 mvpnAdvtReceivedMalformedTunnelType, 2313 mvpnAdvtReceivedMalformedTunnelId, 2314 mvpnAdvtLastSentTime, 2315 mvpnAdvtLastReceivedTime, 2316 mvpnAdvtCounterDiscontinuityTime 2317 } 2318 STATUS current 2319 DESCRIPTION 2320 "These objects are used to monitor 2321 the statistics pertaining to I-PMSI and S-PMSI 2322 advertisements sent/received by a PE. 2323 " 2324 ::= { mvpnGroups 6 } 2326 mvpnMrouteGroup OBJECT-GROUP 2327 OBJECTS { 2328 mvpnMrouteUpstreamNeighborAddrType, 2329 mvpnMrouteUpstreamNeighborAddr, 2330 mvpnMrouteInIfIndex, 2331 mvpnMrouteExpiryTime, 2332 mvpnMrouteProtocol, 2333 mvpnMrouteRtProtocol, 2334 mvpnMrouteRtAddrType, 2335 mvpnMrouteRtAddr, 2336 mvpnMrouteRtPrefixLength, 2337 mvpnMrouteRtType, 2338 mvpnMrouteOctets, 2339 mvpnMroutePkts, 2340 mvpnMrouteTtlDroppedOctets, 2341 mvpnMrouteTtlDroppedPackets, 2342 mvpnMrouteDroppedInOctets, 2343 mvpnMrouteDroppedInPackets, 2344 mvpnMroutePmsiPointer, 2345 mvpnMrouteNumberOfLocalReplication, 2346 mvpnMrouteNumberOfRemoteReplication, 2347 mvpnMrouteCounterDiscontinuityTime 2348 } 2349 STATUS current 2350 DESCRIPTION 2351 "These objects are used to monitor multicast routing 2352 information corresponding to the MVRFs on a PE. 2353 " 2354 ::= { mvpnGroups 7 } 2356 mvpnMrouteNextHopGroup OBJECT-GROUP 2357 OBJECTS { 2358 mvpnMrouteNextHopState, 2359 mvpnMrouteNextHopExpiryTime, 2360 mvpnMrouteNextHopClosestMemberHops, 2361 mvpnMrouteNextHopProtocol, 2362 mvpnMrouteNextHopOctets, 2363 mvpnMrouteNextHopPkts, 2364 mvpnMrouteNextHopCounterDiscontinuityTime 2365 } 2366 STATUS current 2367 DESCRIPTION 2368 "These objects are used to monitor the information on 2369 next-hops for routing datagrams to MVPNs on a PE. 2370 " 2371 ::= { mvpnGroups 8 } 2373 mvpnNotificationGroup NOTIFICATION-GROUP 2374 NOTIFICATIONS { 2375 mvpnMvrfActionTaken 2376 } 2377 STATUS current 2378 DESCRIPTION 2379 "Objects required for MVPN notifications." 2380 ::= { mvpnGroups 9 } 2382 END 2384 4. Security Considerations 2386 This MIB module contains some read-only objects that may be deemed 2387 senstive. It also contains some read-write objects, whose setting 2388 will change the device's MVPN related behavior. Appropriate security 2389 procedures related to SNMP in general but not specific to this MIB 2390 module need to be implemented by concerned operators. 2392 There are a number of management objects defined in this MIB module 2393 with a MAX-ACCESS clause of read-write. Such objects may be 2394 considered sensitive or vulnerable in some network environments. The 2395 support for SET operations in a non-secure environment without proper 2396 protection opens devices to attack. These are the tables and objects 2397 and their sensitivity/vulnerability: 2399 o mvpnSPTunnelLimit 2401 The value of this object is used to control the maximum number of 2402 selective provider tunnels that a PE allows for a particular MVPN. 2403 Access to this object may be abused to impact the peformance of 2404 the PE or prevent the PE from having new selective provider 2405 tunnels. 2407 o mvpnBgpCmcastRouteWithdrawalTimer 2409 The value of this object is used to control the delay for the 2410 advertisement of withdrawals of C-multicast routes. Access to 2411 this object may be abused to impact the peformance of a PE. 2413 o mvpnBgpSrcSharedTreeJoinTimer 2415 The value of this object is used to control the delay for the 2416 advertisement of Source/Shared Tree Join C-multicast routes. 2417 Access to this object may be abused to impact the propagation of 2418 C-multicast routing information. 2420 o mvpnBgpMsgRateLimit 2422 The value of this object is used to control the upper bound for 2423 the rate of BGP C-multicast routing information message exchange 2424 among PEs. Access to this object may be abused to impact the 2425 peformance of the PE or disrupt the C-multicast routing 2426 information message exchange using BGP. 2428 o mvpnBgpMaxSpmsiAdRoutes 2430 The value of this object is used to control the upper bound for 2431 the number of S-PMSI A-D routes. Access to this object may be 2432 abused to impact the peformance of the PE or prevent the PE from 2433 receiving S-PMSI A-D routes. 2435 o mvpnBgpMaxSpmsiAdRouteFreq 2437 The value of this object is used to control the upper bound for 2438 the frequency of S-PMSI A-D route generation. Access to this 2439 object may be abused to impact the peformance of the PE or prevent 2440 the PE from generating new S-PMSI A-D routes. 2442 o mvpnBgpMaxSrcActiveAdRoutes 2444 The value of this object is used to control the upper bound for 2445 the number of Source Active A-D routes. Access to this object may 2446 be abused to impact the peformance of the PE or prevent the PE 2447 from receiving Source Active A-D routes. 2449 o mvpnBgpMaxSrcActiveAdRouteFreq 2450 The value of this object is used to control the upper bound for 2451 the frequency of Source Active A-D route generation. Access to 2452 this object may be abused to impact the peformance of the PE or 2453 prevent the PE from generating new Source Active A-D routes. 2455 Some of the readable objects in this MIB module (i.e., objects with a 2456 MAX-ACCESS other than not-accessible) may be considered sensitive or 2457 vulnerable in some network environments. It is thus important to 2458 control even GET and/or NOTIFY access to these objects and possibly 2459 to even encrypt the values of these objects when sending them over 2460 the network via SNMP. These are the tables and objects and their 2461 sensitivity/vulnerability: 2463 o The address-related objects in this MIB module may have impact on 2464 privacy and security. These objects may reveal the locations of 2465 senders and recipients. 2467 * mvpnPmsiTunnelPimGroupAddr 2469 * mvpnSpmsiCmcastGroupAddr 2471 * mvpnSpmsiCmcastSourceAddr 2473 * mvpnAdvtPeerAddr 2475 * mvpnMrouteCmcastGroupAddr 2477 * mvpnMrouteCmcastSourceAddrs 2479 * mvpnMrouteUpstreamNeighborAddr 2481 * mvpnMrouteNextHopGroupAddr 2483 * mvpnMrouteNextHopSourceAddrs 2485 * mvpnMrouteNextHopAddr 2487 SNMP versions prior to SNMPv3 did not include adequate security. 2488 Even if the network itself is secure (for example by using IPsec), 2489 there is no control as to who on the secure network is allowed to 2490 access and GET/SET (read/change/create/delete) the objects in this 2491 MIB module. 2493 Implementations SHOULD provide the security features described by the 2494 SNMPv3 framework (see [RFC3410]), and implementations claiming 2495 compliance to the SNMPv3 standard MUST include full support for 2496 authentication and privacy via the User-based Security Model (USM) 2497 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 2498 MAY also provide support for the Transport Security Model (TSM) 2499 [RFC5591] in combination with a secure transport such as SSH 2500 [RFC5592] or TLS/DTLS [RFC6353]. 2502 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2503 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2504 enable cryptographic security. It is then a customer/operator 2505 responsibility to ensure that the SNMP entity giving access to an 2506 instance of this MIB module is properly configured to give access to 2507 the objects only to those principals (users) that have legitimate 2508 rights to indeed GET or SET (change/create/delete) them. 2510 5. IANA Considerations 2512 The MIB module in this document uses the following IANA-assigned 2513 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 2515 Descriptor OBJECT IDENTIFIER value 2516 ---------- ----------------------- 2517 mvpnMIB { mib-2 AAAA } 2519 Editor's Note (to be removed prior to publication): the IANA is 2520 requested to assign a value for "AAAA" under the 'mib-2' subtree and 2521 to record the assignment in the SMI Numbers registry. When the 2522 assignment has been made, the RFC Editor is asked to replace "AAAA" 2523 (here and in the MIB module) with the assigned value and to remove 2524 this note. 2526 6. Acknowledgement 2528 An earlier draft version of this document was coauthored by Zhaohui 2529 (Jeffrey) Zhang, Saud Asif, Andy Green, Sameer Gulrajani, and Pradeep 2530 G. Jain, based on an earlier draft written by Susheela Vaidya, 2531 Thomas D. Nadeau, and Harmen Van der Linde. 2533 This document also borrows heavily from the design and descriptions 2534 of ipMcastRouteTable and ipMcastRouteNextHopTable from IPMCAST- 2535 MIB[RFC5132]. 2537 Glenn Mansfield Keeni did the MIB Doctor review and provided valuable 2538 comments. 2540 7. References 2541 7.1. Normative References 2543 [RFC2003] Perkins, C., "IP Encapsulation within IP", RFC 2003, DOI 2544 10.17487/RFC2003, October 1996, . 2547 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2548 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 2549 RFC2119, March 1997, . 2552 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2553 Schoenwaelder, Ed., "Structure of Management Information 2554 Version 2 (SMIv2)", STD 58, RFC 2578, DOI 10.17487/ 2555 RFC2578, April 1999, . 2558 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2559 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 2560 58, RFC 2579, DOI 10.17487/RFC2579, April 1999, 2561 . 2563 [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. 2564 Schoenwaelder, Ed., "Conformance Statements for SMIv2", 2565 STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999, 2566 . 2568 [RFC2784] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. 2569 Traina, "Generic Routing Encapsulation (GRE)", RFC 2784, 2570 DOI 10.17487/RFC2784, March 2000, . 2573 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 2574 MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000, 2575 . 2577 [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., 2578 Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack 2579 Encoding", RFC 3032, DOI 10.17487/RFC3032, January 2001, 2580 . 2582 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 2583 (USM) for version 3 of the Simple Network Management 2584 Protocol (SNMPv3)", STD 62, RFC 3414, DOI 10.17487/ 2585 RFC3414, December 2002, . 2588 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 2589 Advanced Encryption Standard (AES) Cipher Algorithm in the 2590 SNMP User-based Security Model", RFC 3826, DOI 10.17487/ 2591 RFC3826, June 2004, . 2594 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 2595 Schoenwaelder, "Textual Conventions for Internet Network 2596 Addresses", RFC 4001, DOI 10.17487/RFC4001, February 2005, 2597 . 2599 [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private 2600 Networks (VPNs)", RFC 4364, DOI 10.17487/RFC4364, February 2601 2006, . 2603 [RFC4382] Nadeau, T., Ed. and H. van der Linde, Ed., "MPLS/BGP Layer 2604 3 Virtual Private Network (VPN) Management Information 2605 Base", RFC 4382, DOI 10.17487/RFC4382, February 2006, 2606 . 2608 [RFC5132] McWalter, D., Thaler, D., and A. Kessler, "IP Multicast 2609 MIB", RFC 5132, DOI 10.17487/RFC5132, December 2007, 2610 . 2612 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 2613 for the Simple Network Management Protocol (SNMP)", STD 2614 78, RFC 5591, DOI 10.17487/RFC5591, June 2009, 2615 . 2617 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 2618 Shell Transport Model for the Simple Network Management 2619 Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June 2620 2009, . 2622 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 2623 Model for the Simple Network Management Protocol (SNMP)", 2624 STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011, 2625 . 2627 [RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/ 2628 BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February 2629 2012, . 2631 [RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP 2632 Encodings and Procedures for Multicast in MPLS/BGP IP 2633 VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012, 2634 . 2636 [RFC6625] Rosen, E., Ed., Rekhter, Y., Ed., Hendrickx, W., and R. 2637 Qiu, "Wildcards in Multicast VPN Auto-Discovery Routes", 2638 RFC 6625, DOI 10.17487/RFC6625, May 2012, 2639 . 2641 [RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I., 2642 Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent 2643 Multicast - Sparse Mode (PIM-SM): Protocol Specification 2644 (Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March 2645 2016, . 2647 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2648 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 2649 May 2017, . 2651 [RTPROTO] IANA, "IP Route Protocol MIB", 2016, 2652 . 2654 7.2. Informative References 2656 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2657 "Introduction and Applicability Statements for Internet- 2658 Standard Management Framework", RFC 3410, DOI 10.17487/ 2659 RFC3410, December 2002, . 2662 Author's Address 2664 Hiroshi Tsunoda 2665 Tohoku Institute of Technology 2666 35-1, Yagiyama Kasumi-cho, Taihaku-ku 2667 Sendai 982-8577 2668 Japan 2670 Phone: +81-22-305-3411 2671 Email: tsuno@m.ieice.org