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