idnits 2.17.1 draft-ietf-bess-mvpn-mib-06.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 : ---------------------------------------------------------------------------- ** There are 7 instances of too long lines in the document, the longest one being 10 characters in excess of 72. 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 (April 30, 2018) is 2181 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: 'RFC2856' is mentioned on line 272, but not defined == Missing Reference: 'RFC2851' is mentioned on line 279, but not defined ** Obsolete undefined reference: RFC 2851 (Obsoleted by RFC 3291) == Missing Reference: 'TBD' is mentioned on line 2994, but not defined == Unused Reference: 'RFC4659' is defined on line 3091, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'RTPROTO' Summary: 2 errors (**), 0 flaws (~~), 6 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Z. Zhang, Ed. 3 Internet-Draft Juniper 4 Intended status: Standards Track S. Asif 5 Expires: November 1, 2018 AT&T 6 A. Green 7 BT 8 S. Gulranjani 9 Cisco 10 P. Jain 11 Alcatel-Lucent 12 H. Tsunoda, Ed. 13 Tohoku Institute of Technology 14 April 30, 2018 16 BGP/MPLS Layer 3 VPN Multicast Management Information Base 17 draft-ietf-bess-mvpn-mib-06 19 Abstract 21 This memo defines a portion of the Management Information Base (MIB) 22 for use with network management protocols in the Internet community. 23 In particular, it describes managed objects to configure and/or 24 monitor MVPN, Multicast in MultiProtocol Label Switching/Border 25 Gateway Protocol (MPLS/BGP) IP Virtual Private Networks (VPNs) on a 26 Provider Edge router. 28 Status of This Memo 30 This Internet-Draft is submitted in full conformance with the 31 provisions of BCP 78 and BCP 79. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF). Note that other groups may also distribute 35 working documents as Internet-Drafts. The list of current Internet- 36 Drafts is at http://datatracker.ietf.org/drafts/current/. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet-Drafts as reference 41 material or to cite them other than as "work in progress." 43 This Internet-Draft will expire on November 1, 2018. 45 Copyright Notice 47 Copyright (c) 2018 IETF Trust and the persons identified as the 48 document authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal 51 Provisions Relating to IETF Documents 52 (http://trustee.ietf.org/license-info) in effect on the date of 53 publication of this document. Please review these documents 54 carefully, as they describe your rights and restrictions with respect 55 to this document. Code Components extracted from this document must 56 include Simplified BSD License text as described in Section 4.e of 57 the Trust Legal Provisions and are provided without warranty as 58 described in the Simplified BSD License. 60 Table of Contents 62 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 63 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 64 2. The Internet-Standard Management Framework . . . . . . . . . 4 65 3. MCAST-VPN-MIB . . . . . . . . . . . . . . . . . . . . . . . . 4 66 3.1. Summary of MIB Module . . . . . . . . . . . . . . . . . . 4 67 3.2. MIB Module Definitions . . . . . . . . . . . . . . . . . 6 68 4. Security Considerations . . . . . . . . . . . . . . . . . . . 62 69 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 63 70 6. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 64 71 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 64 72 7.1. Normative References . . . . . . . . . . . . . . . . . . 64 73 7.2. Informative References . . . . . . . . . . . . . . . . . 66 74 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 66 76 1. Introduction 78 [RFC6513], [RFC6514], and [RFC6625] specify procedures for supporting 79 multicast in Border Gateway Protocol/MultiProtocol Label Switching 80 (BGP/MPLS) Layer 3 (IP) Virtual Private Network (VPN). Throughout 81 this document, we will use the term "Multicast VPN (MVPN)" [RFC6513] 82 to refer to a BGP/MPLS IP VPN that supports multicast. 84 Provider Edge routers (PEs) exchange the VPN customer multicast 85 (C-multicast) routing information with each other. In [RFC6513], two 86 basic methods for exchanging C-multicast routing information are 87 defined (1) Protocol Independent Multicast (PIM) [RFC7761] and (2) 88 BGP. 90 In the rest of this document we will use the term "PIM-MVPN" to refer 91 to PIM being used for exchanging C-multicast routing information, and 92 "BGP-MVPN" to refer to BGP being used for exchanging C-multicast 93 routing information. 95 This document describes managed objects to configure and/or monitor 96 MVPN. The managed objects are common to both PIM-MVPN and BGP-MVPN. 98 Comments should be made directly to the BESS WG at bess@ietf.org. 100 1.1. Terminology 102 This document adopts the definitions, acronyms and mechanisms 103 described in [RFC6513] and other documents that [RFC6513] refers to. 104 Familiarity with Multicast, MPLS, Layer 3 (L3) VPN, MVPN concepts 105 and/or mechanisms is assumed. Some terms specifically related to 106 this document are explained below. 108 MVPN can be achieved by using various kinds of transport mechanisms 109 for forwarding a packet to all or a subset of PEs across service 110 provider networks. Such transport mechanisms are referred to as 111 provider tunnels (P-tunnels). 113 "Provider Multicast Service Interface (PMSI)" [RFC6513] is a 114 conceptual interface instantiated by a provider tunnel (P-tunnel), a 115 transport mechanism used to deliver multicast traffic. A PE uses to 116 send customer multicast traffic to all or some PEs in the same VPN. 118 There are two kinds of PMSI: "Inclusive PMSI (I-PMSI)" and "Selective 119 PMSI (S-PMSI)" [RFC6513]. An I-PMSI is a PMSI that enables a PE 120 attached to a particular MVPN to transmit a message to all PEs in the 121 same VPN. An S-PMSI is a PMSI that enables a PE attached to a 122 particular MVPN to transmit a message to some of the PEs in the same 123 VPN. 125 As described in [RFC4382], each PE router maintains one default 126 forwarding table and "Virtual Routing and Forwarding tables", or 127 "VRFs". Throughout this document, we will use the term "multicast 128 VRF (MVRF)" to refer a VRF that is configured to contain the 129 multicast routing information. 131 Interchangeably, the term MVRF and MVPN are used to refer to a 132 particular Multicast VPN instantiation on a particular PE. 134 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 135 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 136 document are to be interpreted as described in [RFC2119]. 138 2. The Internet-Standard Management Framework 140 For a detailed overview of the documents that describe the current 141 Internet-Standard Management Framework, please refer to section 7 of 142 RFC 3410 [RFC3410]. 144 Managed objects are accessed via a virtual information store, termed 145 the Management Information Base or MIB. MIB objects are generally 146 accessed through the Simple Network Management Protocol (SNMP). 147 Objects in the MIB are defined using the mechanisms defined in the 148 Structure of Management Information (SMI). This memo specifies a MIB 149 module that is compliant to the SMIv2, which is described in STD 58, 150 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 151 [RFC2580]. 153 3. MCAST-VPN-MIB 155 This document defines MCAST-VPN-MIB, a MIB module for monitoring and/ 156 or configuring MVPNs on PEs. 158 3.1. Summary of MIB Module 160 MCAST-VPN-MIB provides the following functionalities for monitoring 161 and configuring MVPN. 163 o Monitoring attribute informations of MVRFs of MVPNs presented on a 164 PE 166 o Configuring some timers related to a MVRF 168 o Notifying creation, deletion, and modification of MVRFs on a PE 170 o Monitoring attribute informations of PMSIs on a PE 172 o Monitoring advertisement exchanged by a PE 174 o Monitoring routing entries in an MVRF 176 o Monitoring information on next-hops in an MVRF 178 o Notifying events that a PE joins or leaves a multicast group 180 To provide these functionalities, MCAST-VPN-MIB defines nine tables: 181 mvpnGenericTable, mvpnBgpGenericlTable, mvpnPmsiTable, 182 mvpnSpmsiTable, mvpnIpmsiAdvtTable, mvpnInterAsIpmsiAdvtTable, 183 mvpnSpmsiAdvtTable, mvpnMrouteTable, and mvpnMrouteNextHopTable. 185 The following two tables contain information of MVRFs of MVPNs 186 configured on a PE. 188 o mvpnGenericTable 190 This table specifies the generic information about MVRFs present 191 in a PE. Each entry in this table is created for each MVRF 192 representing an instance of MVPN. The entry represetns general 193 configuration/states of the MVRF, including Inclusive PMSI 194 (I-PMSI) configuration. An MVRF represented by the entry in this 195 table must have a corresponding VRF in MPLS-L3VPN-STD-MIB 196 [RFC4382]. 198 o mvpnBgpGenericTable 200 This table specifies the specific information of MVRFs of MVPNs 201 that use BGP for exchanging C-Multicast routing information 202 present in a PE. Each MVRF of an MVPN that use BGP for exchanging 203 C-Multicast routing information will have an entry in this table. 204 The MVRF represented by this entry will have a corresponding entry 205 in the mvpnGenericTable. 207 The following two tables contain information of PMSIs configured on a 208 PE. 210 o mvpnPmsiTable 212 This table contains common managed objects representing attribute 213 information of both I-PMSI and Selective PMSI (S-PMSI) configured 214 on a PE. Both I-PMSI information (in the entry in 215 mvpnGeneralTable) and S-PMSI information (in the entry in 216 mvpnSpmsiConfigTable) refer to an entry in this table. 218 o mvpnSpmsiTable 220 This table contains managed objects representing attribute 221 information that is specific for S-PMSI associated with an MVRF on 222 a PE. 224 The following three tables are designed for monitoring advertisements 225 that is advertised/received by a PE. 227 o mvpnIpmsiAdvtTable 229 This table contains managed objects representing advertisements of 230 Intra-AS I-PMSIs advertised/received by a PE. 232 o mvpnInterAsIpmsiAdvtTable 233 This table contains managed objects representing advertisements of 234 Inter-AS I-PMSIs advertised/received by a PE. 236 o mvpnSpmsiAdvtTable 238 This table contains managed objects representing advertisements of 239 S-PMSIs advertised/received by a PE. 241 The following two tables are designed for handling routing 242 information that is advertised/received by a PE. 244 o mvpnMrouteTable 246 This table contains multicast routing information in MVRFs present 247 in a PE. 249 o mvpnMrouteNextHopTable 251 The table contains information on the next-hops on outgoing 252 interfaces for routing IP multicast datagrams in MVPNs present on 253 a PE. 255 3.2. MIB Module Definitions 257 MCAST-VPN-MIB DEFINITIONS ::= BEGIN 259 IMPORTS 260 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 261 Counter32, Counter64, Gauge32, Unsigned32, TimeTicks, 262 zeroDotZero, mib-2 263 FROM SNMPv2-SMI -- [RFC2578] 265 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 266 FROM SNMPv2-CONF -- [RFC2580] 268 RowPointer, TimeStamp, TimeInterval 269 FROM SNMPv2-TC -- [RFC2579] 271 CounterBasedGauge64 272 FROM HCNUM-TC -- [RFC2856] 274 InterfaceIndex, InterfaceIndexOrZero 275 FROM IF-MIB -- [RFC2863] 277 InetAddress, InetAddressType, InetAddressPrefixLength, 278 InetAutonomousSystemNumber 279 FROM INET-ADDRESS-MIB -- [RFC2851] 281 mplsL3VpnVrfName, MplsL3VpnRouteDistinguisher 282 FROM MPLS-L3VPN-STD-MIB -- [RFC4382] 284 IANAipRouteProtocol, IANAipMRouteProtocol 285 FROM IANA-RTPROTO-MIB -- [RTPROTO] 287 L2L3VpnMcastProviderTunnelType 288 FROM L2L3-VPN-MCAST-TC-MIB; 290 mvpnMIB MODULE-IDENTITY 291 LAST-UPDATED "201804301200Z" -- 30th April 2018 12:00:00 GMT 292 ORGANIZATION "IETF BESS Working Group." 293 CONTACT-INFO 294 " Zhaohui Zhang 295 Juniper Networks, Inc. 296 10 Technology Park Drive 297 Westford, MA 01886 298 USA 299 Email: zzhang@juniper.net 301 Saud Asif 302 AT&T 303 C5-3D30 200 South Laurel Avenue 304 Middletown, NJ 07748 305 USA 306 Email: sasif@att.com 308 Andy Green 309 BT Design 21CN Converged Core IP & Data 310 01473 629360 Adastral Park, Martlesham Heath, 311 Ipswich IP5 3RE 312 UK 313 Email: andy.da.green@bt.com 315 Sameer Gulrajani 316 Cisco Systems 317 Tasman Drive San Jose, CA 95134 318 USA 319 Email: sameerg@cisco.com 321 Pradeep G. Jain 322 Alcatel-Lucent Inc 323 701 E Middlefield road Mountain view, CA 94043 324 USA 325 Email: pradeep.jain@alcatel-lucent.com 327 Hiroshi Tsunoda 328 Tohoku Institute of Technology 329 35-1, Yagiyama Kasumi-cho 330 Taihaku-ku, Sendai, 982-8577 331 Japan 332 Email: tsuno@m.ieice.org 334 Comments and discussion to bess@ietf.org" 336 DESCRIPTION 337 "This MIB contains managed object definitions for 338 multicast in BGP/MPLS IP VPNs defined by [RFC6513]. 339 Copyright (C) The Internet Society (2018)." 341 -- Revision history. 343 REVISION "201804301200Z" -- 30th April, 2018 344 DESCRIPTION 345 "Initial version, published as RFC XXXX." 347 -- RFC Ed. replace XXXX with actual RFC number and remove this note 349 ::= { mib-2 YYYY } 351 -- IANA Reg.: Please assign a value for "YYYY" under the 352 -- 'mib-2' subtree and record the assignment in the SMI 353 -- Numbers registry. 355 -- RFC Ed.: When the above assignment has been made, please 356 -- remove the above note 357 -- replace "YYYY" here with the assigned value and 358 -- remove this note. 360 -- Top level components of this MIB. 361 mvpnNotifications OBJECT IDENTIFIER ::= { mvpnMIB 0 } 363 -- tables, scalars 364 mvpnObjects OBJECT IDENTIFIER ::= { mvpnMIB 1 } 366 -- conformance information 367 mvpnConformance OBJECT IDENTIFIER ::= { mvpnMIB 2 } 369 -- mvpn Objects 370 mvpnScalars OBJECT IDENTIFIER ::= { mvpnObjects 1 } 371 mvpnGeneric OBJECT IDENTIFIER ::= { mvpnObjects 2 } 372 mvpnConfig OBJECT IDENTIFIER ::= { mvpnObjects 3 } 373 mvpnStates OBJECT IDENTIFIER ::= { mvpnObjects 4 } 375 -- Scalar Objects 376 mvpnMvrfs OBJECT-TYPE 377 SYNTAX Gauge32 378 MAX-ACCESS read-only 379 STATUS current 380 DESCRIPTION 381 "The total number of Multicast Virtual Routing and 382 Forwarding tables (MVRFs) that are present on 383 this Provider Edge router (PE). This includes MVRFs 384 for IPv4, IPv6, and mLDP C-Multicast. 385 " 386 ::= { mvpnScalars 1 } 388 mvpnV4Mvrfs OBJECT-TYPE 389 SYNTAX Gauge32 390 MAX-ACCESS read-only 391 STATUS current 392 DESCRIPTION 393 "The number of MVRFs for IPv4 C-Multicast that are 394 present in this PE. 395 " 396 ::= { mvpnScalars 2 } 398 mvpnV6Mvrfs OBJECT-TYPE 399 SYNTAX Gauge32 400 MAX-ACCESS read-only 401 STATUS current 402 DESCRIPTION 403 "The number of MVRFs for IPv6 C-Multicast that are 404 present in this PE. 405 " 406 ::= { mvpnScalars 3 } 408 mvpnPimV4Mvrfs OBJECT-TYPE 409 SYNTAX Gauge32 410 MAX-ACCESS read-only 411 STATUS current 412 DESCRIPTION 413 "The number of MVRFs of MVPNs that use PIM for 414 exchanging IPv4 C-Multicast routing information 415 present in this PE. 416 " 417 ::= { mvpnScalars 4 } 419 mvpnPimV6Mvrfs OBJECT-TYPE 420 SYNTAX Gauge32 421 MAX-ACCESS read-only 422 STATUS current 423 DESCRIPTION 424 "The number of MVRFs of MVPNs that use PIM for 425 exchanging IPv6 C-Multicast routing information 426 present in this PE. 427 " 428 ::= { mvpnScalars 5 } 430 mvpnBgpV4Mvrfs OBJECT-TYPE 431 SYNTAX Gauge32 432 MAX-ACCESS read-only 433 STATUS current 434 DESCRIPTION 435 "The number of MVRFs of MVPNs that use BGP for 436 exchanging IPv4 C-Multicast routing information 437 present in this PE. 438 " 439 ::= { mvpnScalars 6 } 441 mvpnBgpV6Mvrfs OBJECT-TYPE 442 SYNTAX Gauge32 443 MAX-ACCESS read-only 444 STATUS current 445 DESCRIPTION 446 "The number of MVRFs of MVPNs that use BGP for 447 exchanging IPv6 C-Multicast routing information 448 present in this PE. 449 " 450 ::= { mvpnScalars 7 } 452 mvpnMldpMvrfs OBJECT-TYPE 453 SYNTAX Gauge32 454 MAX-ACCESS read-only 455 STATUS current 456 DESCRIPTION 457 "The number of MVRFs of MVPNs that use BGP for 458 exchanging mLDP C-Multicast routing information 459 present in this PE. 460 " 461 ::= { mvpnScalars 8 } 463 -- Generic MVRF Information Table 465 mvpnGenericTable OBJECT-TYPE 466 SYNTAX SEQUENCE OF MvpnGenericEntry 467 MAX-ACCESS not-accessible 468 STATUS current 469 DESCRIPTION 470 "This table specifies the generic information about the MVRFs 471 present in this PE. 473 Entries in this table are not required to survive a reboot 474 of the managed entity. 475 " 476 ::= { mvpnGeneric 1 } 478 mvpnGenericEntry OBJECT-TYPE 479 SYNTAX MvpnGenericEntry 480 MAX-ACCESS not-accessible 481 STATUS current 482 DESCRIPTION 483 "This entry represents a conceptual row in the mvpnGenericTable. 484 Each MVRF serviced by the PE will have an entry in this table. 485 The MVRF represented by this entry will have one or more 486 corresponding P-Multicast Service Interfaces (PMSIs) 487 and a corresponding VRF in MPLS-L3VPN-STD-MIB [RFC4382]. 488 " 489 INDEX { 490 mplsL3VpnVrfName, 491 mvpnGenAddressFamily 492 } 493 ::= { mvpnGenericTable 1 } 495 MvpnGenericEntry ::= SEQUENCE { 496 mvpnGenAddressFamily INTEGER, 497 mvpnGenMvrfLastOperation INTEGER, 498 mvpnGenMvrfLastOperationTime TimeStamp, 499 mvpnGenCmcastRouteProtocol INTEGER, 500 mvpnGenIpmsiInfo RowPointer, 501 mvpnGenInterAsPmsiInfo RowPointer, 502 mvpnGenUmhSelection INTEGER, 503 mvpnGenCustomerSiteType INTEGER, 504 mvpnGenSPTunnelLimit Unsigned32 505 } 507 mvpnGenAddressFamily OBJECT-TYPE 508 SYNTAX INTEGER { 509 ipv4(1), 510 ipv6(2) 511 } 512 MAX-ACCESS not-accessible 513 STATUS current 514 DESCRIPTION 515 "The Address Family of the MVRF represented by this entry" 516 REFERENCE 517 "RFC6513, Section 1 518 " 519 ::= { mvpnGenericEntry 1 } 521 mvpnGenMvrfLastOperation OBJECT-TYPE 522 SYNTAX INTEGER { 523 createdMvrf(1), 524 deletedMvrf(2), 525 modifiedMvrfIpmsiConfig(3), 526 modifiedMvrfSpmsiConfig(4) 527 } 528 MAX-ACCESS read-only 529 STATUS current 530 DESCRIPTION 531 "This object describes the last operation pertaining 532 to the MVRF represented by this entry. 534 createdMvrf(1): 535 the MVRF was created in the PE. 537 deletedMvrf(2): 538 the MVRF was deleted from the PE. 539 A row in this table will never have 540 mvpnGenMvrfLastOperation equal to deletedMvrf(2), 541 because in that case the row itself will be deleted 542 from the table. 543 This value for mvpnGenMvrfLastOperation is defined 544 mainly for use in mvpnMvrfOperationChange notification. 546 modifiedMvrfIpmsiConfig(3): 547 an I-PMSI for the MVRF was configured, 548 deleted or changed. 550 modifiedMvrfSpmsiConfig(4): 551 an S-PMSI for the MVRF was configured, 552 deleted or changed. 553 " 554 DEFVAL { createdMvrf } 555 ::= { mvpnGenericEntry 2 } 557 mvpnGenMvrfLastOperationTime OBJECT-TYPE 558 SYNTAX TimeStamp 559 MAX-ACCESS read-only 560 STATUS current 561 DESCRIPTION 562 "The time at which the last operation for the MVRF in 563 question took place. The last operational change is specified 564 by mvpnGenMvrfLastOperation. 565 The time at which the last operation, specifed 566 in mvpnGenMvrfLastOperation, for the MVRF 567 represented by this entry was carried out. 568 " 570 ::= { mvpnGenericEntry 3 } 572 mvpnGenCmcastRouteProtocol OBJECT-TYPE 573 SYNTAX INTEGER { 574 pim (1), 575 bgp (2) 576 } 577 MAX-ACCESS read-only 578 STATUS current 579 DESCRIPTION 580 "The protocol used to signal C-multicast routing 581 information across the provider core. 582 PIM (PIM-MVPN): pim(1) 583 BGP (BGP-MVPN): bgp(2) 584 " 585 REFERENCE 586 "RFC6513, Section 5" 587 ::= { mvpnGenericEntry 4 } 589 mvpnGenIpmsiInfo OBJECT-TYPE 590 SYNTAX RowPointer 591 MAX-ACCESS read-only 592 STATUS current 593 DESCRIPTION 594 "This points to a conceptual row representing 595 the corresponding I-PMSI in mvpnPmsiTable. 596 If there is no I-PMSI for the MVRF, the 597 value of this object will be zeroDotZero. 598 " 599 DEFVAL { zeroDotZero } 600 ::= { mvpnGenericEntry 5 } 602 mvpnGenInterAsPmsiInfo OBJECT-TYPE 603 SYNTAX RowPointer 604 MAX-ACCESS read-only 605 STATUS current 606 DESCRIPTION 607 "This points to a conceptual row representing 608 the corresponding Inter-AS I-PMSI in mvpnPmsiTable, 609 in case of segmented Inter-AS provider tunnels. 610 If there is no segmented Inter-AS I-PMSI for the MVRF, 611 the value of this object will be zeroDotZero. 612 " 613 DEFVAL { zeroDotZero } 614 ::= { mvpnGenericEntry 6 } 616 mvpnGenUmhSelection OBJECT-TYPE 617 SYNTAX INTEGER { 618 highestPeAddress (1), 619 cRootGroupHashing (2), 620 ucastUmhRoute (3) 621 } 622 MAX-ACCESS read-only 623 STATUS current 624 DESCRIPTION 625 "The UMH selection method for this mvpn, as specified in 626 section 5.1.3 of [RFC6513]: 627 PE with the highest address: highestPeAddress (1) 628 hashing based on (c-root, c-group): cRootGroupHashing (2) 629 per ucast route towards c-root: ucastUmhRoute (3) 630 " 631 REFERENCE 632 "RFC6513, Section 5.1" 633 ::= { mvpnGenericEntry 7 } 635 mvpnGenCustomerSiteType OBJECT-TYPE 636 SYNTAX INTEGER { 637 senderReceiver (1), 638 receiverOnly (2), 639 senderOnly (3) 640 } 641 MAX-ACCESS read-only 642 STATUS current 643 DESCRIPTION 644 "The type of a customer site, which is connected to 645 this PE, in the MVPN which has the MVRF represented 646 by this entry. 648 Site is both sender and receiver: senderReceiver (1) 649 Site is receiver-only : receiverOnly (2) 650 Site is sender-only : senderOnly (3) 651 " 652 REFERENCE 653 "RFC6513, Section 2.3" 654 ::= { mvpnGenericEntry 8 } 656 mvpnGenSPTunnelLimit OBJECT-TYPE 657 SYNTAX Unsigned32 658 MAX-ACCESS read-only 659 STATUS current 660 DESCRIPTION 661 "The maximum number of selective provider tunnels that 662 this PE allows for this MVPN. 663 " 664 REFERENCE 665 "RFC6513, Section 13" 667 ::= { mvpnGenericEntry 9 } 669 -- Generic BGP-MVPN table 671 mvpnBgpGenericTable OBJECT-TYPE 672 SYNTAX SEQUENCE OF MvpnBgpGenericEntry 673 MAX-ACCESS not-accessible 674 STATUS current 675 DESCRIPTION 676 "This table specifies the specific information of MVRFs of MVPNs 677 that use BGP for exchanging C-Multicast routing information 678 present in this PE. 679 " 680 ::= { mvpnGeneric 2 } 682 mvpnBgpGenericEntry OBJECT-TYPE 683 SYNTAX MvpnBgpGenericEntry 684 MAX-ACCESS not-accessible 685 STATUS current 686 DESCRIPTION 687 "This entry represents a conceptual row in the mvpnBgpGenericTable. 688 Each MVRF of an MVPN that use BGP for exchanging C-Multicast 689 routing information will have an entry in this table. 690 The MVRF represented by this entry will have 691 a corresponding entry in the mvpnGenericTable. 692 " 693 INDEX { 694 mplsL3VpnVrfName, 695 mvpnGenAddressFamily 696 } 697 ::= { mvpnBgpGenericTable 1 } 699 MvpnBgpGenericEntry ::= SEQUENCE { 700 mvpnBgpGenMode INTEGER, 701 mvpnBgpGenVrfRouteImport MplsL3VpnRouteDistinguisher, 702 mvpnBgpGenSrcAs InetAutonomousSystemNumber, 703 mvpnBgpGenCmcastRouteWithdrawalTimer Unsigned32, 704 mvpnBgpGenSrcSharedTreeJoinTimer Unsigned32, 705 mvpnBgpGenMsgRateLimit Unsigned32, 706 mvpnBgpGenMaxSpmsiAdRoutes Unsigned32, 707 mvpnBgpGenMaxSpmsiAdRouteFreq Unsigned32, 708 mvpnBgpGenMaxSrcActiveAdRoutes Unsigned32, 709 mvpnBgpGenMaxSrcActiveAdRouteFreq Unsigned32 710 } 712 mvpnBgpGenMode OBJECT-TYPE 713 SYNTAX INTEGER { 714 rptSpt (1), 715 sptOnly (2) 716 } 717 MAX-ACCESS read-only 718 STATUS current 719 DESCRIPTION 720 "For two different BGP-MVPN modes: 721 rptSpt(1): inter-site shared tree mode 722 sptOnly(2): inter-site source-only tree mode. 723 " 724 REFERENCE 725 "RFC6513, Section 9.3.1" 726 ::= { mvpnBgpGenericEntry 1 } 728 mvpnBgpGenVrfRouteImport OBJECT-TYPE 729 SYNTAX MplsL3VpnRouteDistinguisher 730 MAX-ACCESS read-only 731 STATUS current 732 DESCRIPTION 733 "The VRF Route Import Extended Community that this PE 734 adds to unicast VPN routes that it advertises for this MVPN. 735 " 736 REFERENCE 737 "RFC6514, Section 7 738 " 739 ::= { mvpnBgpGenericEntry 2 } 741 mvpnBgpGenSrcAs OBJECT-TYPE 742 SYNTAX InetAutonomousSystemNumber 743 MAX-ACCESS read-only 744 STATUS current 745 DESCRIPTION 746 "The Source AS number in Source AS Extended Community that this 747 PE adds to the unicast VPN routes that it advertises for 748 this MVPN. 749 " 750 REFERENCE 751 "RFC6514, Section 6 752 " 753 ::= { mvpnBgpGenericEntry 3 } 755 mvpnBgpGenCmcastRouteWithdrawalTimer OBJECT-TYPE 756 SYNTAX Unsigned32 757 MAX-ACCESS read-write 758 STATUS current 759 DESCRIPTION 760 "The configurable timer to control the delay 761 for the advertisement of withdrawals of 762 C-multicast routes. 764 " 765 REFERENCE 766 "RFC6514, Section 16.1.1" 767 ::= { mvpnBgpGenericEntry 4 } 769 mvpnBgpGenSrcSharedTreeJoinTimer OBJECT-TYPE 770 SYNTAX Unsigned32 771 MAX-ACCESS read-write 772 STATUS current 773 DESCRIPTION 774 "The configurable timer to control the delay 775 for the advertisement of Source/Shared Tree Join 776 C-multicast routes. 777 " 778 REFERENCE 779 "RFC6514, Section 16.1.2" 780 ::= { mvpnBgpGenericEntry 5 } 782 mvpnBgpGenMsgRateLimit OBJECT-TYPE 783 SYNTAX Unsigned32 784 MAX-ACCESS read-write 785 STATUS current 786 DESCRIPTION 787 "The upper bounds on rate of BGP message exchange among PEs 788 for exchanging C-multicast routing information 789 " 790 REFERENCE 791 "RFC6514, Section 17" 792 ::= { mvpnBgpGenericEntry 6 } 794 mvpnBgpGenMaxSpmsiAdRoutes OBJECT-TYPE 795 SYNTAX Unsigned32 796 MAX-ACCESS read-write 797 STATUS current 798 DESCRIPTION 799 "The upper bound on the number of S-PMSI A-D routes. 800 " 801 REFERENCE 802 "RFC6514, Section 17" 803 ::= { mvpnBgpGenericEntry 7 } 805 mvpnBgpGenMaxSpmsiAdRouteFreq OBJECT-TYPE 806 SYNTAX Unsigned32 807 MAX-ACCESS read-write 808 STATUS current 809 DESCRIPTION 810 "The upper bound on how frequently S-PMSI A-D routes 811 may be generated. 813 " 814 REFERENCE 815 "RFC6514, Section 17" 816 ::= { mvpnBgpGenericEntry 8 } 818 mvpnBgpGenMaxSrcActiveAdRoutes OBJECT-TYPE 819 SYNTAX Unsigned32 820 MAX-ACCESS read-write 821 STATUS current 822 DESCRIPTION 823 "The upper bound on the number of Source Active A-D routes. 824 " 825 REFERENCE 826 "RFC6514, Section 17" 827 ::= { mvpnBgpGenericEntry 9 } 829 mvpnBgpGenMaxSrcActiveAdRouteFreq OBJECT-TYPE 830 SYNTAX Unsigned32 831 MAX-ACCESS read-write 832 STATUS current 833 DESCRIPTION 834 "The upper bound on how frequently Source Active A-D routes 835 may be generated. 836 " 837 REFERENCE 838 "RFC6514, Section 17" 839 ::= { mvpnBgpGenericEntry 10 } 841 -- PMSI Configuration Table 843 mvpnPmsiTable OBJECT-TYPE 844 SYNTAX SEQUENCE OF MvpnPmsiEntry 845 MAX-ACCESS not-accessible 846 STATUS current 847 DESCRIPTION 848 "An entry in this table corresponds to 849 the attribute information of a specific 850 PMSI configured on a PE router. 851 " 852 ::= { mvpnConfig 1 } 854 mvpnPmsiEntry OBJECT-TYPE 855 SYNTAX MvpnPmsiEntry 856 MAX-ACCESS not-accessible 857 STATUS current 858 DESCRIPTION 859 "A conceptual row corresponding to a specific 860 PMSI on this router. 862 " 863 INDEX { 864 mvpnPmsiTunnelIfIndex 865 } 866 ::= { mvpnPmsiTable 1 } 868 MvpnPmsiEntry ::= SEQUENCE { 869 mvpnPmsiTunnelIfIndex InterfaceIndex, 870 mvpnPmsiTunnelType L2L3VpnMcastProviderTunnelType, 871 mvpnPmsiTunnelPimGroupAddrType InetAddressType, 872 mvpnPmsiTunnelPimGroupAddr InetAddress, 873 mvpnPmsiEncapsulationType INTEGER 874 } 876 mvpnPmsiTunnelIfIndex OBJECT-TYPE 877 SYNTAX InterfaceIndex 878 MAX-ACCESS not-accessible 879 STATUS current 880 DESCRIPTION 881 "This is a unique index for an entry in the 882 mvpnPmsiTable. A non-zero index for an 883 entry indicates the ifIndex for the corresponding 884 entry of PMSI in the ifTable. 885 " 886 REFERENCE 887 "RFC2863 888 " 889 ::= { mvpnPmsiEntry 1 } 891 mvpnPmsiTunnelType OBJECT-TYPE 892 SYNTAX L2L3VpnMcastProviderTunnelType 893 MAX-ACCESS not-accessible 894 STATUS current 895 DESCRIPTION 896 "This object indicates the type of tunnel used to 897 instantiate the PMSI corresponding to this entry" 898 REFERENCE 899 "RFC6513 Sec. 2.6 900 " 901 ::= { mvpnPmsiEntry 2 } 903 mvpnPmsiTunnelPimGroupAddrType OBJECT-TYPE 904 SYNTAX InetAddressType 905 MAX-ACCESS not-accessible 906 STATUS current 907 DESCRIPTION 908 "When the PIM provider tunnel is used for instantiating 909 the PMSI corresponding to this entry, i.e., 910 the value of mvpnPmsiTunnelType is 911 pimSsm(3), pimAsm(4), or pimBidir(5), 912 this object indicates the type of tunnel address. 913 Otherwise, the value of this object will be 914 unknown(0). 915 " 916 ::= { mvpnPmsiEntry 3 } 918 mvpnPmsiTunnelPimGroupAddr OBJECT-TYPE 919 SYNTAX InetAddress 920 MAX-ACCESS not-accessible 921 STATUS current 922 DESCRIPTION 923 "When the PIM provider tunnel is used for instantiating 924 the PMSI corresponding to this entry, i.e., 925 the value of mvpnPmsiTunnelType is 926 pimSsm(3), pimAsm(4), or pimBidir(5), 927 this object indicates the tunnel address. 928 Otherwise, the value of this object will be 929 a string of length zero. 930 " 931 ::= { mvpnPmsiEntry 4 } 933 mvpnPmsiEncapsulationType OBJECT-TYPE 934 SYNTAX INTEGER { 935 greIp (1), 936 ipIp (2), 937 mpls (3) 938 } 939 MAX-ACCESS read-only 940 STATUS current 941 DESCRIPTION 942 "The encapsulation type to be used for sending 943 packets through a P-tunnel. 945 The enumerated values and the corresponding 946 encapsulation types are as follows: 948 greIp (0) : GRE (Generic Routing Encapsulation) encapsulation [RFC2784] 949 ipIp (1) : IP-in-IP encapsulation [RFC2003] 950 mpls (2) : MPLS encapsulation [RFC3032] 951 " 952 REFERENCE 953 "RFC2003 954 RFC2784 955 RFC3032 956 RFC6513 Sec. 12.1 957 " 959 ::= { mvpnPmsiEntry 5 } 961 -- S-PMSI configuration table 963 mvpnSpmsiTable OBJECT-TYPE 964 SYNTAX SEQUENCE OF MvpnSpmsiEntry 965 MAX-ACCESS not-accessible 966 STATUS current 967 DESCRIPTION 968 "An entry in this table corresponds to 969 a specific S-PMSI configured on a PE router. 970 This table stores only S-PMSI specific 971 attribute information and generic attribute 972 information of the S-PMSI is stored in 973 mvpnPmsiTable. 974 Therefore, there MUST be corresponding entry 975 that pertains to the S-PMSI, in mvpnPmsiTable. 976 " 977 ::= { mvpnConfig 2 } 979 mvpnSpmsiEntry OBJECT-TYPE 980 SYNTAX MvpnSpmsiEntry 981 MAX-ACCESS not-accessible 982 STATUS current 983 DESCRIPTION 984 "A conceptual row corresponding to a specific 985 S-PMSI on this router. 987 Implementers need to be aware that there are quite a few 988 index objects that together can exceed the size allowed 989 for an Object Identifier (OID). So implementers must make 990 sure that OIDs of column instances in this table will have 991 no more than 128 sub-identifiers, otherwise they cannot be 992 accessed using SNMPv1, SNMPv2c, or SNMPv3. 993 " 994 INDEX { 995 mplsL3VpnVrfName, 996 mvpnSpmsiCmcastAddrType, 997 mvpnSpmsiCmcastGroupAddr, 998 mvpnSpmsiCmcastGroupPrefixLen, 999 mvpnSpmsiCmcastSourceAddr, 1000 mvpnSpmsiCmcastSourcePrefixLen 1001 } 1002 ::= { mvpnSpmsiTable 1 } 1004 MvpnSpmsiEntry ::= SEQUENCE { 1005 mvpnSpmsiCmcastAddrType InetAddressType, 1006 mvpnSpmsiCmcastGroupAddr InetAddress, 1007 mvpnSpmsiCmcastGroupPrefixLen InetAddressPrefixLength, 1008 mvpnSpmsiCmcastSourceAddr InetAddress, 1009 mvpnSpmsiCmcastSourcePrefixLen InetAddressPrefixLength, 1010 mvpnSpmsiThreshold Unsigned32, 1011 mvpnSpmsiPmsiPointer RowPointer 1012 } 1014 mvpnSpmsiCmcastAddrType OBJECT-TYPE 1015 SYNTAX InetAddressType 1016 MAX-ACCESS not-accessible 1017 STATUS current 1018 DESCRIPTION 1019 "Type of C-multicast source and group addresses of 1020 a particular C-flow which is assigned to an S-PMSI 1021 corresponding to this entry." 1022 ::= { mvpnSpmsiEntry 1 } 1024 mvpnSpmsiCmcastGroupAddr OBJECT-TYPE 1025 SYNTAX InetAddress 1026 MAX-ACCESS not-accessible 1027 STATUS current 1028 DESCRIPTION 1029 "A group address of a particular C-flow which is 1030 assigned to an S-PMSI corresponding to this entry." 1031 ::= { mvpnSpmsiEntry 2 } 1033 mvpnSpmsiCmcastGroupPrefixLen OBJECT-TYPE 1034 SYNTAX InetAddressPrefixLength 1035 MAX-ACCESS not-accessible 1036 STATUS current 1037 DESCRIPTION 1038 "A prefix length of mvpnSpmsiCmcastGroupAddr. 1039 A group 0 (or ::0) with prefix length 32 (or 128) 1040 indicates wildcard group, while a group 0 (or ::0) 1041 with prefix length 0 indicates any group. 1042 " 1043 ::= { mvpnSpmsiEntry 3 } 1045 mvpnSpmsiCmcastSourceAddr OBJECT-TYPE 1046 SYNTAX InetAddress 1047 MAX-ACCESS not-accessible 1048 STATUS current 1049 DESCRIPTION 1050 "A source address of a particular C-flow which is 1051 assigned to an S-PMSI corresponding to this entry." 1052 ::= { mvpnSpmsiEntry 4 } 1054 mvpnSpmsiCmcastSourcePrefixLen OBJECT-TYPE 1055 SYNTAX InetAddressPrefixLength 1056 MAX-ACCESS not-accessible 1057 STATUS current 1058 DESCRIPTION 1059 "A prefix length of mvpnSpmsiCmcastSourceAddr. 1060 A source 0 (or ::0) with prefix length 32 (or 128) 1061 indicates a wildcard source, while a source 0 (or ::0) 1062 with prefix length 0 indicates any source. 1063 " 1064 ::= { mvpnSpmsiEntry 5 } 1066 mvpnSpmsiThreshold OBJECT-TYPE 1067 SYNTAX Unsigned32 (0..4294967295) 1068 UNITS "kilobits per second" 1069 MAX-ACCESS read-write 1070 STATUS current 1071 DESCRIPTION 1072 "The bandwidth threshold value which when exceeded for a 1073 multicast routing entry in the given MVRF, triggers usage 1074 of S-PMSI. 1075 " 1076 REFERENCE 1077 "RFC6513 Sec. 7.2" 1078 ::= { mvpnSpmsiEntry 6 } 1080 mvpnSpmsiPmsiPointer OBJECT-TYPE 1081 SYNTAX RowPointer 1082 MAX-ACCESS read-only 1083 STATUS current 1084 DESCRIPTION 1085 "This points to a row in mvpnPmsiTable, 1086 to specify tunnel attributes. 1087 " 1088 ::= { mvpnSpmsiEntry 7 } 1090 -- Table of intra-as I-PMSIs advertised/received 1092 mvpnIpmsiAdvtTable OBJECT-TYPE 1093 SYNTAX SEQUENCE OF MvpnIpmsiAdvtEntry 1094 MAX-ACCESS not-accessible 1095 STATUS current 1096 DESCRIPTION 1097 "This table is for all advertised/received I-PMSI 1098 advertisements. 1099 " 1100 ::= { mvpnStates 1 } 1102 mvpnIpmsiAdvtEntry OBJECT-TYPE 1103 SYNTAX MvpnIpmsiAdvtEntry 1104 MAX-ACCESS not-accessible 1105 STATUS current 1106 DESCRIPTION 1107 "An entry in this table corresponds to an I-PMSI 1108 advertisement that is advertised/received by this router. 1109 This represents all the sender PEs in the MVPN, 1110 with the provider tunnel they use to send traffic. 1112 Implementers need to be aware that there are quite a few 1113 index objects that together can exceed the size allowed 1114 for an Object Identifier (OID). So implementers must make 1115 sure that OIDs of column instances in this table will have 1116 no more than 128 sub-identifiers, otherwise they cannot be 1117 accessed using SNMPv1, SNMPv2c, or SNMPv3. 1118 " 1119 INDEX { 1120 mplsL3VpnVrfName, 1121 mvpnIpmsiAdvtAfi, 1122 mvpnIpmsiAdvtRD, 1123 mvpnIpmsiAdvtOrigAddrType, 1124 mvpnIpmsiAdvtOrigAddr 1125 } 1126 ::= { mvpnIpmsiAdvtTable 1 } 1128 MvpnIpmsiAdvtEntry ::= SEQUENCE { 1129 mvpnIpmsiAdvtAfi INTEGER, 1130 mvpnIpmsiAdvtRD MplsL3VpnRouteDistinguisher, 1131 mvpnIpmsiAdvtOrigAddrType InetAddressType, 1132 mvpnIpmsiAdvtOrigAddr InetAddress, 1133 mvpnIpmsiAdvtTunnelAttribute RowPointer, 1134 mvpnIpmsiAdvtReceived Counter32, 1135 mvpnIpmsiAdvtReceivedError Counter32, 1136 mvpnIpmsiAdvtMalformedTunnelType Counter32, 1137 mvpnIpmsiAdvtMalformedTunnelId Counter32, 1138 mvpnIpmsiAdvtLastReceivedTime TimeStamp, 1139 mvpnIpmsiAdvtCounterDiscontinuityTime TimeStamp 1140 } 1142 mvpnIpmsiAdvtAfi OBJECT-TYPE 1143 SYNTAX INTEGER { 1144 ipv4(1), 1145 ipv6(2) 1146 } 1147 MAX-ACCESS not-accessible 1148 STATUS current 1149 DESCRIPTION 1150 "The address family this I-PMSI is for." 1152 ::= { mvpnIpmsiAdvtEntry 1 } 1154 mvpnIpmsiAdvtRD OBJECT-TYPE 1155 SYNTAX MplsL3VpnRouteDistinguisher 1156 MAX-ACCESS not-accessible 1157 STATUS current 1158 DESCRIPTION 1159 "The Route Distinguisher in this I-PMSI." 1160 ::= { mvpnIpmsiAdvtEntry 2 } 1162 mvpnIpmsiAdvtOrigAddrType OBJECT-TYPE 1163 SYNTAX InetAddressType 1164 MAX-ACCESS not-accessible 1165 STATUS current 1166 DESCRIPTION 1167 "The Internet address type of mvpnIpmsiAdvtOrigAddr." 1168 ::= { mvpnIpmsiAdvtEntry 3 } 1170 mvpnIpmsiAdvtOrigAddr OBJECT-TYPE 1171 SYNTAX InetAddress 1172 MAX-ACCESS not-accessible 1173 STATUS current 1174 DESCRIPTION 1175 "The BGP address of the PE that originated the I-PMSI." 1176 ::= { mvpnIpmsiAdvtEntry 4 } 1178 mvpnIpmsiAdvtTunnelAttribute OBJECT-TYPE 1179 SYNTAX RowPointer 1180 MAX-ACCESS read-only 1181 STATUS current 1182 DESCRIPTION 1183 "Points to a row in the l2L3VpnMcastPmsiTunnelAttributeTable." 1184 ::= { mvpnIpmsiAdvtEntry 5 } 1186 mvpnIpmsiAdvtReceived OBJECT-TYPE 1187 SYNTAX Counter32 1188 MAX-ACCESS read-only 1189 STATUS current 1190 DESCRIPTION 1191 "The number of I-PMSI advertisements received by the PE router. 1192 This includes advertisements that were discarded. 1193 Discontinuities in the value of this counter can 1194 occur at re-initialization of the management system, 1195 and at other times as indicated by the value of 1196 mvpnIpmsiAdvtCounterDiscontinuityTime. 1197 " 1198 ::= { mvpnIpmsiAdvtEntry 6 } 1200 mvpnIpmsiAdvtReceivedError OBJECT-TYPE 1201 SYNTAX Counter32 1202 MAX-ACCESS read-only 1203 STATUS current 1204 DESCRIPTION 1205 "The total number of errors in the I-PMSI advertisements 1206 received by the PE router. 1207 The value of this object is the sum of 1208 the values of mvpnIpmsiAdvtMalformedTunnelType and 1209 mvpnIpmsiAdvtMalformedTunnelId. 1210 Discontinuities in the value of this counter can 1211 occur at re-initialization of the management system, 1212 and at other times as indicated by the value of 1213 mvpnIpmsiAdvtCounterDiscontinuityTime. 1214 " 1215 ::= { mvpnIpmsiAdvtEntry 7 } 1217 mvpnIpmsiAdvtMalformedTunnelType OBJECT-TYPE 1218 SYNTAX Counter32 1219 MAX-ACCESS read-only 1220 STATUS current 1221 DESCRIPTION 1222 "The number of received I-PMSI advertisements that 1223 contain a PMSI Tunnel attribute whose Tunnel 1224 Type field has an undefined tunnel type. 1225 Discontinuities in the value of this counter can 1226 occur at re-initialization of the management system, 1227 and at other times as indicated by the value of 1228 mvpnIpmsiAdvtCounterDiscontinuityTime. 1229 " 1230 REFERENCE 1231 "RFC6514 Sec.5" 1232 ::= { mvpnIpmsiAdvtEntry 8 } 1234 mvpnIpmsiAdvtMalformedTunnelId OBJECT-TYPE 1235 SYNTAX Counter32 1236 MAX-ACCESS read-only 1237 STATUS current 1238 DESCRIPTION 1239 "The number of received I-PMSI advertisements that 1240 contain a PMSI Tunnel attribute whose Tunnel 1241 Identifier field cannot be parsed as a 1242 tunnel identifier of the tunnel types specified in 1243 the Tunnel type field of the attribute. 1244 Discontinuities in the value of this counter can 1245 occur at re-initialization of the management system, 1246 and at other times as indicated by the value of 1247 mvpnIpmsiAdvtCounterDiscontinuityTime. 1249 " 1250 REFERENCE 1251 "RFC6514 Sec.5" 1252 ::= { mvpnIpmsiAdvtEntry 9 } 1254 mvpnIpmsiAdvtLastReceivedTime OBJECT-TYPE 1255 SYNTAX TimeStamp 1256 MAX-ACCESS read-only 1257 STATUS current 1258 DESCRIPTION 1259 "The value of sysUpTime when the last I-PMSI 1260 advertisement was received by the PE router. 1261 " 1262 ::= { mvpnIpmsiAdvtEntry 10 } 1264 mvpnIpmsiAdvtCounterDiscontinuityTime OBJECT-TYPE 1265 SYNTAX TimeStamp 1266 MAX-ACCESS read-only 1267 STATUS current 1268 DESCRIPTION 1269 "The value of sysUpTime on the most recent occasion 1270 at which any one or more of this syslog application's 1271 counters, viz., counters with OID prefix 1272 'mvpnIpmsiAdvtReceived' or 1273 'mvpnIpmsiAdvtReceivedError' or 1274 'mvpnIpmsiAdvtMalformedTunnelType' or 1275 'mvpnIpmsiAdvtMalformedTunnelId' suffered a 1276 discontinuity. 1277 If no such discontinuities have occurred since the 1278 last re-initialization of the local management 1279 subsystem, then this object will have a zero value. 1280 " 1281 ::= { mvpnIpmsiAdvtEntry 11 } 1283 -- Table of inter-as I-PMSIs advertised/received 1285 mvpnInterAsIpmsiAdvtTable OBJECT-TYPE 1286 SYNTAX SEQUENCE OF MvpnInterAsIpmsiAdvtEntry 1287 MAX-ACCESS not-accessible 1288 STATUS current 1289 DESCRIPTION 1290 "This table is for all advertised/received inter-as I-PMSI 1291 advertisements." 1292 ::= { mvpnStates 2 } 1294 mvpnInterAsIpmsiAdvtEntry OBJECT-TYPE 1295 SYNTAX MvpnInterAsIpmsiAdvtEntry 1296 MAX-ACCESS not-accessible 1297 STATUS current 1298 DESCRIPTION 1299 "An entry in this table corresponds to an inter-as I-PMSI 1300 advertisement that is advertised/received by this router. 1301 This represents all the ASes in the MVPN, 1302 with the provider tunnel used to send traffic to. 1304 Implementers need to be aware that there are quite a few 1305 index objects that together can exceed the size allowed 1306 for an Object Identifier (OID). So implementers must make 1307 sure that OIDs of column instances in this table will have 1308 no more than 128 sub-identifiers, otherwise they cannot be 1309 accessed using SNMPv1, SNMPv2c, or SNMPv3. 1310 " 1311 INDEX { 1312 mplsL3VpnVrfName, 1313 mvpnInterAsIpmsiAdvtAfi, 1314 mvpnInterAsIpmsiAdvtRD, 1315 mvpnInterAsIpmsiAdvtSrcAs 1316 } 1317 ::= { mvpnInterAsIpmsiAdvtTable 1 } 1319 MvpnInterAsIpmsiAdvtEntry ::= SEQUENCE { 1320 mvpnInterAsIpmsiAdvtAfi INTEGER, 1321 mvpnInterAsIpmsiAdvtRD MplsL3VpnRouteDistinguisher, 1322 mvpnInterAsIpmsiAdvtSrcAs InetAutonomousSystemNumber, 1323 mvpnInterAsIpmsiAdvtTunnelAttribute RowPointer, 1324 mvpnInterAsIpmsiAdvtReceived Counter32, 1325 mvpnInterAsIpmsiAdvtReceivedError Counter32, 1326 mvpnInterAsIpmsiAdvtMalformedTunnelType Counter32, 1327 mvpnInterAsIpmsiAdvtMalformedTunnelId Counter32, 1328 mvpnInterAsIpmsiAdvtLastReceivedTime TimeStamp, 1329 mvpnInterAsIpmsiAdvtCounterDiscontinuityTime TimeStamp 1330 } 1332 mvpnInterAsIpmsiAdvtAfi OBJECT-TYPE 1333 SYNTAX INTEGER { 1334 ipv4(1), 1335 ipv6(2) 1336 } 1337 MAX-ACCESS not-accessible 1338 STATUS current 1339 DESCRIPTION 1340 "The address family this I-PMSI is for." 1341 ::= { mvpnInterAsIpmsiAdvtEntry 1 } 1343 mvpnInterAsIpmsiAdvtRD OBJECT-TYPE 1344 SYNTAX MplsL3VpnRouteDistinguisher 1345 MAX-ACCESS not-accessible 1346 STATUS current 1347 DESCRIPTION 1348 "The Route Distinguisher in this inter-as I-PMSI." 1349 ::= { mvpnInterAsIpmsiAdvtEntry 2 } 1351 mvpnInterAsIpmsiAdvtSrcAs OBJECT-TYPE 1352 SYNTAX InetAutonomousSystemNumber 1353 MAX-ACCESS not-accessible 1354 STATUS current 1355 DESCRIPTION 1356 "The source-as in this inter-as I-PMSI." 1357 ::= { mvpnInterAsIpmsiAdvtEntry 3 } 1359 mvpnInterAsIpmsiAdvtTunnelAttribute OBJECT-TYPE 1360 SYNTAX RowPointer 1361 MAX-ACCESS read-only 1362 STATUS current 1363 DESCRIPTION 1364 "Points to a row in the l2L3VpnMcastPmsiTunnelAttributeTable." 1365 ::= { mvpnInterAsIpmsiAdvtEntry 4 } 1367 mvpnInterAsIpmsiAdvtReceived OBJECT-TYPE 1368 SYNTAX Counter32 1369 MAX-ACCESS read-only 1370 STATUS current 1371 DESCRIPTION 1372 "The number of Inter-AS I-PMSI advertisements received 1373 by the PE router. 1374 This includes advertisements that were discarded. 1375 Discontinuities in the value of this counter can 1376 occur at re-initialization of the management system, 1377 and at other times as indicated by the value of 1378 mvpnInterAsIpmsiAdvtCounterDiscontinuityTime. 1379 " 1380 ::= { mvpnInterAsIpmsiAdvtEntry 5 } 1382 mvpnInterAsIpmsiAdvtReceivedError OBJECT-TYPE 1383 SYNTAX Counter32 1384 MAX-ACCESS read-only 1385 STATUS current 1386 DESCRIPTION 1387 "The total number of errors in the Inter-AS I-PMSI 1388 advertisements received by the PE router. 1389 The value of this object is the sum of 1390 the values of mvpnInterAsIpmsiAdvtMalformedTunnelType and 1391 mvpnInterAsIpmsiAdvtMalformedTunnelId. 1392 Discontinuities in the value of this counter can 1393 occur at re-initialization of the management system, 1394 and at other times as indicated by the value of 1395 mvpnInterAsIpmsiAdvtCounterDiscontinuityTime. 1396 " 1397 ::= { mvpnInterAsIpmsiAdvtEntry 6 } 1399 mvpnInterAsIpmsiAdvtMalformedTunnelType OBJECT-TYPE 1400 SYNTAX Counter32 1401 MAX-ACCESS read-only 1402 STATUS current 1403 DESCRIPTION 1404 "The number of received Inter-AS I-PMSI advertisements that 1405 contain a PMSI Tunnel attribute whose Tunnel 1406 Type field has an undefined tunnel type. 1407 Discontinuities in the value of this counter can 1408 occur at re-initialization of the management system, 1409 and at other times as indicated by the value of 1410 mvpnInterAsIpmsiAdvtCounterDiscontinuityTime. 1411 " 1412 REFERENCE 1413 "RFC6514 Sec.5" 1414 ::= { mvpnInterAsIpmsiAdvtEntry 7 } 1416 mvpnInterAsIpmsiAdvtMalformedTunnelId OBJECT-TYPE 1417 SYNTAX Counter32 1418 MAX-ACCESS read-only 1419 STATUS current 1420 DESCRIPTION 1421 "The number of received Inter-AS I-PMSI advertisements that 1422 contain a PMSI Tunnel attribute whose Tunnel 1423 Identifier field cannot be parsed as a 1424 tunnel identifier of the tunnel types specified in 1425 the Tunnel type field of the attribute. 1426 Discontinuities in the value of this counter can 1427 occur at re-initialization of the management system, 1428 and at other times as indicated by the value of 1429 mvpnInterAsIpmsiAdvtCounterDiscontinuityTime. 1430 " 1431 REFERENCE 1432 "RFC6514 Sec.5" 1433 ::= { mvpnInterAsIpmsiAdvtEntry 8 } 1435 mvpnInterAsIpmsiAdvtLastReceivedTime OBJECT-TYPE 1436 SYNTAX TimeStamp 1437 MAX-ACCESS read-only 1438 STATUS current 1439 DESCRIPTION 1440 "The value of sysUpTime when the last Inter-AS I-PMSI 1441 advertisement was received by the PE router. 1442 " 1443 ::= { mvpnInterAsIpmsiAdvtEntry 9 } 1445 mvpnInterAsIpmsiAdvtCounterDiscontinuityTime OBJECT-TYPE 1446 SYNTAX TimeStamp 1447 MAX-ACCESS read-only 1448 STATUS current 1449 DESCRIPTION 1450 "The value of sysUpTime on the most recent occasion 1451 at which any one or more of this syslog application's 1452 counters, viz., counters with OID prefix 1453 'mvpnInterAsIpmsiAdvtReceived' or 1454 'mvpnInterAsIpmsiAdvtReceivedError' or 1455 'mvpnInterAsIpmsiAdvtMalformedTunnelType' or 1456 'mvpnInterAsIpmsiAdvtMalformedTunnelId' suffered a 1457 discontinuity. 1458 If no such discontinuities have occurred since the 1459 last re-initialization of the local management 1460 subsystem, then this object will have a zero value. 1461 " 1462 ::= { mvpnInterAsIpmsiAdvtEntry 10 } 1464 -- Table of S-PMSIs advertised/received 1466 mvpnSpmsiAdvtTable OBJECT-TYPE 1467 SYNTAX SEQUENCE OF MvpnSpmsiAdvtEntry 1468 MAX-ACCESS not-accessible 1469 STATUS current 1470 DESCRIPTION 1471 "This table has information about the S-PMSIs sent/received 1472 by a PE. 1473 " 1474 ::= { mvpnStates 3 } 1476 mvpnSpmsiAdvtEntry OBJECT-TYPE 1477 SYNTAX MvpnSpmsiAdvtEntry 1478 MAX-ACCESS not-accessible 1479 STATUS current 1480 DESCRIPTION 1481 "An entry in this table is created or updated for each S-PMSI 1482 advertised/received in a particular MVRF. 1484 Implementers need to be aware that there are quite a few 1485 index objects that together can exceed the size allowed 1486 for an Object Identifier (OID). So implementers must make 1487 sure that OIDs of column instances in this table will have 1488 no more than 128 sub-identifiers, otherwise they cannot be 1489 accessed using SNMPv1, SNMPv2c, or SNMPv3. 1490 " 1491 INDEX { 1492 mplsL3VpnVrfName, 1493 mvpnSpmsiAdvtCmcastAddrType, 1494 mvpnSpmsiAdvtCmcastGroupAddr, 1495 mvpnSpmsiAdvtCmcastGroupPrefixLen, 1496 mvpnSpmsiAdvtCmcastSourceAddr, 1497 mvpnSpmsiAdvtCmcastSourcePrefixLen, 1498 mvpnSpmsiAdvtOrigAddrType, 1499 mvpnSpmsiAdvtOrigAddr 1500 } 1501 ::= { mvpnSpmsiAdvtTable 1 } 1503 MvpnSpmsiAdvtEntry ::= SEQUENCE { 1504 mvpnSpmsiAdvtCmcastAddrType InetAddressType, 1505 mvpnSpmsiAdvtCmcastGroupAddr InetAddress, 1506 mvpnSpmsiAdvtCmcastGroupPrefixLen InetAddressPrefixLength, 1507 mvpnSpmsiAdvtCmcastSourceAddr InetAddress, 1508 mvpnSpmsiAdvtCmcastSourcePrefixLen InetAddressPrefixLength, 1509 mvpnSpmsiAdvtOrigAddrType InetAddressType, 1510 mvpnSpmsiAdvtOrigAddr InetAddress, 1511 mvpnSpmsiAdvtTunnelAttribute RowPointer, 1512 mvpnSpmsiAdvtExpTime TimeInterval, 1513 mvpnSpmsiAdvtRefCnt Unsigned32, 1514 mvpnSpmsiAdvtReceived Counter32, 1515 mvpnSpmsiAdvtReceivedError Counter32, 1516 mvpnSpmsiAdvtMalformedTunnelType Counter32, 1517 mvpnSpmsiAdvtMalformedTunnelId Counter32, 1518 mvpnSpmsiAdvtLastReceivedTime TimeStamp, 1519 mvpnSpmsiAdvtCounterDiscontinuityTime TimeStamp 1520 } 1522 mvpnSpmsiAdvtCmcastAddrType OBJECT-TYPE 1523 SYNTAX InetAddressType 1524 MAX-ACCESS not-accessible 1525 STATUS current 1526 DESCRIPTION 1527 "The Internet address type of mvpnSpmsiAdvtCmcastGroup/Source." 1528 ::= { mvpnSpmsiAdvtEntry 1 } 1530 mvpnSpmsiAdvtCmcastGroupAddr OBJECT-TYPE 1531 SYNTAX InetAddress 1532 MAX-ACCESS not-accessible 1533 STATUS current 1534 DESCRIPTION 1535 "S-PMSI C-multicast group address. 1537 If it is 0 (or ::0), this is a wildcard group, 1538 and mvpnSpmsiAdvtCmcastGroupPrefixLen must be 32 (or 128). 1539 " 1540 ::= { mvpnSpmsiAdvtEntry 2 } 1542 mvpnSpmsiAdvtCmcastGroupPrefixLen OBJECT-TYPE 1543 SYNTAX InetAddressPrefixLength 1544 MAX-ACCESS not-accessible 1545 STATUS current 1546 DESCRIPTION 1547 "S-PMSI C-multicast group address prefix length." 1548 ::= { mvpnSpmsiAdvtEntry 3 } 1550 mvpnSpmsiAdvtCmcastSourceAddr OBJECT-TYPE 1551 SYNTAX InetAddress 1552 MAX-ACCESS not-accessible 1553 STATUS current 1554 DESCRIPTION 1555 "S-PMSI C-multicast source address 1556 If it is 0 (or ::0), this is a wildcard source, 1557 and mvpnSpmsiAdvtCmcastSourcePrefixLen must be 32 (or 128). 1558 " 1559 ::= { mvpnSpmsiAdvtEntry 4 } 1561 mvpnSpmsiAdvtCmcastSourcePrefixLen OBJECT-TYPE 1562 SYNTAX InetAddressPrefixLength 1563 MAX-ACCESS not-accessible 1564 STATUS current 1565 DESCRIPTION 1566 "S-PMSI C-multicast source address prefix length." 1567 ::= { mvpnSpmsiAdvtEntry 5 } 1569 mvpnSpmsiAdvtOrigAddrType OBJECT-TYPE 1570 SYNTAX InetAddressType 1571 MAX-ACCESS not-accessible 1572 STATUS current 1573 DESCRIPTION 1574 "The Internet address type of mvpnSpmsiAdvtOrigAddr." 1575 ::= { mvpnSpmsiAdvtEntry 6 } 1577 mvpnSpmsiAdvtOrigAddr OBJECT-TYPE 1578 SYNTAX InetAddress 1579 MAX-ACCESS not-accessible 1580 STATUS current 1581 DESCRIPTION 1582 "The BGP address of the PE that originated the S-PMSI." 1583 ::= { mvpnSpmsiAdvtEntry 7 } 1585 mvpnSpmsiAdvtTunnelAttribute OBJECT-TYPE 1586 SYNTAX RowPointer 1587 MAX-ACCESS read-only 1588 STATUS current 1589 DESCRIPTION 1590 "A row pointer to the l2L3VpnMcastPmsiTunnelAttributeTable" 1591 ::= { mvpnSpmsiAdvtEntry 8 } 1593 mvpnSpmsiAdvtExpTime OBJECT-TYPE 1594 SYNTAX TimeInterval 1595 MAX-ACCESS read-only 1596 STATUS current 1597 DESCRIPTION 1598 "For UDP-based S-PMSI signaling for PIM-MVPN, 1599 the amount of time remaining before this 1600 received S-PMSI Join Message expires, 1601 or the next S-PMSI Join Message refresh is to be 1602 advertised again from the PE. 1603 Otherwise, it is 0. 1604 " 1605 ::= { mvpnSpmsiAdvtEntry 9 } 1607 mvpnSpmsiAdvtRefCnt OBJECT-TYPE 1608 SYNTAX Unsigned32 1609 MAX-ACCESS read-only 1610 STATUS current 1611 DESCRIPTION 1612 "The number of c-multicast routes that are mapped to 1613 this S-PMSI. 1614 " 1615 ::= { mvpnSpmsiAdvtEntry 10 } 1617 mvpnSpmsiAdvtReceived OBJECT-TYPE 1618 SYNTAX Counter32 1619 MAX-ACCESS read-only 1620 STATUS current 1621 DESCRIPTION 1622 "The number of S-PMSI advertisements received by the PE router. 1623 This includes advertisements that were discarded. 1624 Discontinuities in the value of this counter can 1625 occur at re-initialization of the management system, 1626 and at other times as indicated by the value of 1627 mvpnIpmsiAdvtCounterDiscontinuityTime. 1628 " 1629 ::= { mvpnSpmsiAdvtEntry 11 } 1631 mvpnSpmsiAdvtReceivedError OBJECT-TYPE 1632 SYNTAX Counter32 1633 MAX-ACCESS read-only 1634 STATUS current 1635 DESCRIPTION 1636 "The total number of errors in the S-PMSI advertisements 1637 received by the PE router. 1638 The value of this object is the sum of 1639 the values of mvpnSpmsiAdvtMalformedTunnelType and 1640 mvpnSpmsiAdvtMalformedTunnelId. 1641 Discontinuities in the value of this counter can 1642 occur at re-initialization of the management system, 1643 and at other times as indicated by the value of 1644 mvpnSpmsiAdvtCounterDiscontinuityTime. 1645 " 1646 ::= { mvpnSpmsiAdvtEntry 12 } 1648 mvpnSpmsiAdvtMalformedTunnelType OBJECT-TYPE 1649 SYNTAX Counter32 1650 MAX-ACCESS read-only 1651 STATUS current 1652 DESCRIPTION 1653 "The number of received S-PMSI advertisements that 1654 contain a PMSI Tunnel attribute whose Tunnel 1655 Type field has an undefined tunnel type. 1656 Discontinuities in the value of this counter can 1657 occur at re-initialization of the management system, 1658 and at other times as indicated by the value of 1659 mvpnSpmsiAdvtCounterDiscontinuityTime. 1660 " 1661 REFERENCE 1662 "RFC6514 Sec.5" 1663 ::= { mvpnSpmsiAdvtEntry 13 } 1665 mvpnSpmsiAdvtMalformedTunnelId OBJECT-TYPE 1666 SYNTAX Counter32 1667 MAX-ACCESS read-only 1668 STATUS current 1669 DESCRIPTION 1670 "The number of received S-PMSI advertisements that 1671 contain a PMSI Tunnel attribute whose Tunnel 1672 Identifier field cannot be parsed as a 1673 tunnel identifier of the tunnel types specified in 1674 the Tunnel type field of the attribute. 1675 Discontinuities in the value of this counter can 1676 occur at re-initialization of the management system, 1677 and at other times as indicated by the value of 1678 mvpnSpmsiAdvtCounterDiscontinuityTime. 1679 " 1680 REFERENCE 1681 "RFC6514 Sec.5" 1682 ::= { mvpnSpmsiAdvtEntry 14 } 1684 mvpnSpmsiAdvtLastReceivedTime OBJECT-TYPE 1685 SYNTAX TimeStamp 1686 MAX-ACCESS read-only 1687 STATUS current 1688 DESCRIPTION 1689 "The value of sysUpTime when the last S-PMSI 1690 advertisement was received by the PE router. 1691 " 1692 ::= { mvpnSpmsiAdvtEntry 15 } 1694 mvpnSpmsiAdvtCounterDiscontinuityTime OBJECT-TYPE 1695 SYNTAX TimeStamp 1696 MAX-ACCESS read-only 1697 STATUS current 1698 DESCRIPTION 1699 "The value of sysUpTime on the most recent occasion 1700 at which any one or more of this syslog application's 1701 counters, viz., counters with OID prefix 1702 'mvpnSpmsiAdvtReceived' or 1703 'mvpnSpmsiAdvtReceivedError' or 1704 'mvpnSpmsiAdvtMalformedTunnelType' or 1705 'mvpnSpmsiAdvtMalformedTunnelId' suffered a 1706 discontinuity. 1707 If no such discontinuities have occurred since the 1708 last re-initialization of the local management 1709 subsystem, then this object will have a zero value. 1710 " 1711 ::= { mvpnSpmsiAdvtEntry 16 } 1713 -- Table of multicast routes in an MVPN 1715 mvpnMrouteTable OBJECT-TYPE 1716 SYNTAX SEQUENCE OF MvpnMrouteEntry 1717 MAX-ACCESS not-accessible 1718 STATUS current 1719 DESCRIPTION 1720 "This table contains multicast routing information 1721 in MVRFs present in the PE. 1722 " 1723 ::= { mvpnStates 4 } 1725 mvpnMrouteEntry OBJECT-TYPE 1726 SYNTAX MvpnMrouteEntry 1727 MAX-ACCESS not-accessible 1728 STATUS current 1729 DESCRIPTION 1730 "This entry corresponds to each of multicast routing 1731 information components for IP datagrams 1732 from a particular source and addressed to a particular 1733 IP multicast group address. 1735 OIDs are limited to 128 sub-identifiers, but this limit 1736 is not enforced by the syntax of this entry. In practice, 1737 this does not present a problem, because IP address types 1738 allowed by conformance statements do not exceed this limit. 1739 " 1740 INDEX { 1741 mplsL3VpnVrfName, 1742 mvpnMrouteCmcastGroupAddrType, 1743 mvpnMrouteCmcastGroupAddr, 1744 mvpnMrouteCmcastGroupPrefixLength, 1745 mvpnMrouteCmcastSourceAddrType, 1746 mvpnMrouteCmcastSourceAddr, 1747 mvpnMrouteCmcastSourcePrefixLength 1748 } 1749 ::= { mvpnMrouteTable 1 } 1751 MvpnMrouteEntry ::= SEQUENCE { 1752 mvpnMrouteCmcastGroupAddrType InetAddressType, 1753 mvpnMrouteCmcastGroupAddr InetAddress, 1754 mvpnMrouteCmcastGroupPrefixLength InetAddressPrefixLength, 1755 mvpnMrouteCmcastSourceAddrType InetAddressType, 1756 mvpnMrouteCmcastSourceAddr InetAddress, 1757 mvpnMrouteCmcastSourcePrefixLength InetAddressPrefixLength, 1758 mvpnMrouteUpstreamNeighborAddrType InetAddressType, 1759 mvpnMrouteUpstreamNeighborAddr InetAddress, 1760 mvpnMrouteInIfIndex InterfaceIndexOrZero, 1761 mvpnMrouteTimeStamp TimeStamp, 1762 mvpnMrouteExpiryTime TimeTicks, 1763 mvpnMrouteProtocol IANAipMRouteProtocol, 1764 mvpnMrouteRtProtocol IANAipRouteProtocol, 1765 mvpnMrouteRtAddrType InetAddressType, 1766 mvpnMrouteRtAddr InetAddress, 1767 mvpnMrouteRtPrefixLength InetAddressPrefixLength, 1768 mvpnMrouteRtType INTEGER, 1769 mvpnMrouteOctets Counter64, 1770 mvpnMroutePkts Counter64, 1771 mvpnMrouteTtlDropOctets Counter64, 1772 mvpnMrouteTtlDropPackets Counter64, 1773 mvpnMrouteDifferentInIfOctets Counter64, 1774 mvpnMrouteDifferentInIfPackets Counter64, 1775 mvpnMrouteBps CounterBasedGauge64, 1776 mvpnMroutePmsiPointer RowPointer, 1777 mvpnMrouteNumberOfLocalReplication Unsigned32, 1778 mvpnMrouteNumberOfRemoteReplication Unsigned32 1779 } 1781 mvpnMrouteCmcastGroupAddrType OBJECT-TYPE 1782 SYNTAX InetAddressType 1783 MAX-ACCESS not-accessible 1784 STATUS current 1785 DESCRIPTION 1786 "A value indicating the address family of the address 1787 contained in mvpnMrouteGroupAddr. Legal values correspond to 1788 the subset of address families for which multicast 1789 forwarding is supported." 1790 ::= { mvpnMrouteEntry 1 } 1792 mvpnMrouteCmcastGroupAddr OBJECT-TYPE 1793 SYNTAX InetAddress 1794 MAX-ACCESS not-accessible 1795 STATUS current 1796 DESCRIPTION 1797 "The IP multicast group address which, when combined with 1798 the corresponding value specified in 1799 mvpnMrouteGroupPrefixLength, identifies the groups for 1800 which this entry contains multicast routing information. 1802 This address object is only significant up to 1803 mvpnMrouteGroupPrefixLength bits. The remaining address 1804 bits are set to zero. This is especially important for this 1805 index field, which is part of the index of this entry. Any 1806 non-zero bits would signify an entirely different entry. 1808 For addresses of type ipv4z or ipv6z, the appended zone 1809 index is significant even though it lies beyond the prefix 1810 length. The use of these address types indicate that this 1811 forwarding state applies only within the given zone. Zone 1812 index zero is not valid in this table." 1813 ::= { mvpnMrouteEntry 2 } 1815 mvpnMrouteCmcastGroupPrefixLength OBJECT-TYPE 1816 SYNTAX InetAddressPrefixLength 1817 MAX-ACCESS not-accessible 1818 STATUS current 1819 DESCRIPTION 1820 "The length in bits of the mask which, when combined with 1821 the corresponding value of mvpnMrouteGroupAddr, identifies the 1822 groups for which this entry contains multicast routing 1823 information. 1825 The InetAddressType is given by 1826 mvpnMrouteGroupAddrType. For values 'ipv4' and 1827 'ipv4z', this object must be in the range 4..32. For values 1828 'ipv6' and 'ipv6z', this object must be in the range 1829 8..128. 1830 " 1831 ::= { mvpnMrouteEntry 3 } 1833 mvpnMrouteCmcastSourceAddrType OBJECT-TYPE 1834 SYNTAX InetAddressType 1835 MAX-ACCESS not-accessible 1836 STATUS current 1837 DESCRIPTION 1838 "A value indicating the address family of the address 1839 contained in mvpnMrouteSourceAddr. 1841 A value of unknown(0) indicates a non-source-specific entry, 1842 corresponding to all sources in the group. Otherwise, the 1843 value MUST be the same as the value of 1844 mvpnMrouteGroupAddrType. 1845 " 1846 ::= { mvpnMrouteEntry 4 } 1848 mvpnMrouteCmcastSourceAddr OBJECT-TYPE 1849 SYNTAX InetAddress 1850 MAX-ACCESS not-accessible 1851 STATUS current 1852 DESCRIPTION 1853 "The network address which, when combined with the 1854 corresponding value of mvpnMrouteSourcePrefixLength, 1855 identifies the sources for which this entry contains 1856 multicast routing information. 1858 This address object is only significant up to 1859 mvpnMrouteSourcePrefixLength bits. The remaining address 1860 bits are set to zero. This is especially important for this 1861 index field, which is part of the index of this entry. Any 1862 non-zero bits would signify an entirely different entry. 1864 For addresses of type ipv4z or ipv6z, the appended zone 1865 index is significant even though it lies beyond the prefix 1866 length. The use of these address types indicate that this 1867 source address applies only within the given zone. Zone 1868 index zero is not valid in this table. 1869 " 1870 ::= { mvpnMrouteEntry 5 } 1872 mvpnMrouteCmcastSourcePrefixLength OBJECT-TYPE 1873 SYNTAX InetAddressPrefixLength 1874 MAX-ACCESS not-accessible 1875 STATUS current 1876 DESCRIPTION 1877 "The length in bits of the mask which, when combined with 1878 the corresponding value of mvpnMrouteSource, identifies 1879 the sources for which this entry contains multicast routing 1880 information. 1882 The InetAddressType is given by 1883 mvpnMrouteSourceAddrType. For the value 'unknown', 1884 this object must be zero. For values 'ipv4' and 'ipv4z', 1885 this object must be in the range 4..32. For values 'ipv6' 1886 and 'ipv6z', this object must be in the range 8..128." 1887 ::= { mvpnMrouteEntry 6 } 1889 mvpnMrouteUpstreamNeighborAddrType OBJECT-TYPE 1890 SYNTAX InetAddressType 1891 MAX-ACCESS read-only 1892 STATUS current 1893 DESCRIPTION 1894 "A value indicating the address family of the address 1895 contained in mvpnMrouteUpstreamNeighborAddr. 1897 An address type of unknown(0) indicates that the upstream 1898 neighbor is unknown, for example in BIDIR-PIM." 1899 REFERENCE "RFC 5015" 1900 ::= { mvpnMrouteEntry 7 } 1902 mvpnMrouteUpstreamNeighborAddr OBJECT-TYPE 1903 SYNTAX InetAddress 1904 MAX-ACCESS read-only 1905 STATUS current 1906 DESCRIPTION 1907 "The address of the upstream neighbor (for example, RPF 1908 neighbor) from which IP datagrams from these sources to 1909 this multicast address are received. 1910 " 1911 ::= { mvpnMrouteEntry 8 } 1913 mvpnMrouteInIfIndex OBJECT-TYPE 1914 SYNTAX InterfaceIndexOrZero 1915 MAX-ACCESS read-only 1916 STATUS current 1917 DESCRIPTION 1918 "The value of ifIndex for the interface on which IP 1919 datagrams sent by these sources to this multicast address 1920 are received. A value of 0 indicates that datagrams are not 1921 subject to an incoming interface check, but may be accepted 1922 on multiple interfaces (for example, in BIDIR-PIM). 1923 " 1924 REFERENCE 1925 "RFC 5015" 1926 ::= { mvpnMrouteEntry 9 } 1928 mvpnMrouteTimeStamp OBJECT-TYPE 1929 SYNTAX TimeStamp 1930 MAX-ACCESS read-only 1931 STATUS current 1932 DESCRIPTION 1933 "The value of sysUpTime at which the multicast routing 1934 information represented by this entry was learned by the 1935 router. 1937 If this information was present at the most recent re- 1938 initialization of the local management subsystem, then this 1939 object contains a zero value. 1940 " 1941 ::= { mvpnMrouteEntry 10 } 1943 mvpnMrouteExpiryTime OBJECT-TYPE 1944 SYNTAX TimeTicks 1945 MAX-ACCESS read-only 1946 STATUS current 1947 DESCRIPTION 1948 "The minimum amount of time remaining before this entry will 1949 be aged out. The value 0 indicates that the entry is not 1950 subject to aging. If mvpnMrouteNextHopState is pruned(1), 1951 this object represents the remaining time until the prune 1952 expires. If this timer expires, state reverts to 1953 forwarding(2). Otherwise, this object represents the time 1954 until this entry is removed from the table. 1955 " 1956 ::= { mvpnMrouteEntry 11 } 1958 mvpnMrouteProtocol OBJECT-TYPE 1959 SYNTAX IANAipMRouteProtocol 1960 MAX-ACCESS read-only 1961 STATUS current 1962 DESCRIPTION 1963 "The multicast routing protocol via which this multicast 1964 forwarding entry was learned. 1965 " 1966 ::= { mvpnMrouteEntry 12 } 1968 mvpnMrouteRtProtocol OBJECT-TYPE 1969 SYNTAX IANAipRouteProtocol 1970 MAX-ACCESS read-only 1971 STATUS current 1972 DESCRIPTION 1973 "The routing mechanism via which the route used to find the 1974 upstream or parent interface for this multicast forwarding 1975 entry was learned. 1976 " 1977 ::= { mvpnMrouteEntry 13 } 1979 mvpnMrouteRtAddrType OBJECT-TYPE 1980 SYNTAX InetAddressType 1981 MAX-ACCESS read-only 1982 STATUS current 1983 DESCRIPTION 1984 "A value indicating the address family of the address 1985 contained in mvpnMrouteRtAddr. 1986 " 1987 ::= { mvpnMrouteEntry 14 } 1989 mvpnMrouteRtAddr OBJECT-TYPE 1990 SYNTAX InetAddress 1991 MAX-ACCESS read-only 1992 STATUS current 1993 DESCRIPTION 1994 "The address portion of the route used to find the upstream 1995 or parent interface for this multicast forwarding entry. 1997 This address object is only significant up to 1998 mvpnMrouteRtPrefixLength bits. The remaining address bits 1999 are set to zero. 2001 For addresses of type ipv4z or ipv6z, the appended zone 2002 index is significant even though it lies beyond the prefix 2003 length. The use of these address types indicate that this 2004 forwarding state applies only within the given zone. Zone 2005 index zero is not valid in this table. 2006 " 2007 ::= { mvpnMrouteEntry 15 } 2009 mvpnMrouteRtPrefixLength OBJECT-TYPE 2010 SYNTAX InetAddressPrefixLength 2011 MAX-ACCESS read-only 2012 STATUS current 2013 DESCRIPTION 2014 "The length in bits of the mask associated with the route 2015 used to find the upstream or parent interface for this 2016 multicast forwarding entry. 2018 The InetAddressType is given by mvpnMrouteRtAddressType. 2019 For values 'ipv4' and 'ipv4z', this object must be in the 2020 range 4..32. For values 'ipv6' and 'ipv6z', this object 2021 must be in the range 8..128. 2022 " 2023 ::= { mvpnMrouteEntry 16 } 2025 mvpnMrouteRtType OBJECT-TYPE 2026 SYNTAX INTEGER { 2027 unicast (1), -- Unicast route used in multicast RIB 2028 multicast (2) -- Multicast route 2029 } 2030 MAX-ACCESS read-only 2031 STATUS current 2032 DESCRIPTION 2033 "The reason the given route was placed in the (logical) 2034 multicast Routing Information Base (RIB). A value of 2035 unicast means that the route would normally be placed only 2036 in the unicast RIB, but was placed in the multicast RIB 2037 due (instead or in addition) to local configuration, such as 2038 when running PIM over RIP. A value of multicast means that 2039 the route was explicitly added to the multicast RIB by the 2040 routing protocol, such as the Distance Vector Multicast 2041 Routing Protocol (DVMRP) or Multiprotocol BGP. 2042 " 2043 ::= { mvpnMrouteEntry 17 } 2045 mvpnMrouteOctets OBJECT-TYPE 2046 SYNTAX Counter64 2047 MAX-ACCESS read-only 2048 STATUS current 2049 DESCRIPTION 2050 "The number of octets contained in IP datagrams that were 2051 received from these sources and addressed to this multicast 2052 group address, and which were forwarded by this router. 2054 Discontinuities in this monotonically increasing value 2055 occur at re-initialization of the management system. 2056 Discontinuities can also occur as a result of routes being 2057 removed and replaced, which can be detected by observing 2058 the value of mvpnMrouteTimeStamp. 2059 " 2060 ::= { mvpnMrouteEntry 18 } 2062 mvpnMroutePkts OBJECT-TYPE 2063 SYNTAX Counter64 2064 MAX-ACCESS read-only 2065 STATUS current 2066 DESCRIPTION 2067 "The number of packets routed using this multicast route 2068 entry. 2070 Discontinuities in this monotonically increasing value 2071 occur at re-initialization of the management system. 2072 Discontinuities can also occur as a result of routes being 2073 removed and replaced, which can be detected by observing 2074 the value of mvpnMrouteTimeStamp. 2075 " 2076 ::= { mvpnMrouteEntry 19 } 2078 mvpnMrouteTtlDropOctets OBJECT-TYPE 2079 SYNTAX Counter64 2080 MAX-ACCESS read-only 2081 STATUS current 2082 DESCRIPTION 2083 "The number of octets contained in IP datagrams that this 2084 router has received from these sources and addressed to this 2085 multicast group address, which were dropped because the TTL 2086 (IPv4) or Hop Limit (IPv6) was decremented to zero, or to a 2087 value less than ipMcastInterfaceTtl for all next hops. 2089 Discontinuities in this monotonically increasing value 2090 occur at re-initialization of the management system. 2091 Discontinuities can also occur as a result of routes being 2092 removed and replaced, which can be detected by observing 2093 the value of mvpnMrouteTimeStamp. 2094 " 2095 ::= { mvpnMrouteEntry 20 } 2097 mvpnMrouteTtlDropPackets OBJECT-TYPE 2098 SYNTAX Counter64 2099 MAX-ACCESS read-only 2100 STATUS current 2101 DESCRIPTION 2102 "The number of packets that this router has received from 2103 these sources and addressed to this multicast group address, 2104 which were dropped because the TTL (IPv4) or Hop Limit 2105 (IPv6) was decremented to zero, or to a value less than 2106 ipMcastInterfaceTtl for all next hops. 2108 Discontinuities in this monotonically increasing value 2109 occur at re-initialization of the management system. 2110 Discontinuities can also occur as a result of routes being 2111 removed and replaced, which can be detected by observing 2112 the value of mvpnMrouteTimeStamp. 2113 " 2114 ::= { mvpnMrouteEntry 21 } 2116 mvpnMrouteDifferentInIfOctets OBJECT-TYPE 2117 SYNTAX Counter64 2118 MAX-ACCESS read-only 2119 STATUS current 2120 DESCRIPTION 2121 "The number of octets contained in IP datagrams that this 2122 router has received from these sources and addressed to this 2123 multicast group address, which were dropped because they 2124 were received on an unexpected interface. 2126 For RPF checking protocols (such as PIM-SM), these packets 2127 arrived on interfaces other than mvpnMrouteInIfIndex, and 2128 were dropped because of this failed RPF check. (RPF paths 2129 are 'Reverse Path Forwarding' paths; the unicast routes to 2130 the expected origin of multicast data flows). 2131 Other protocols may drop packets on an incoming interface 2132 check for different reasons (for example, BIDIR-PIM performs 2133 a DF check on receipt of packets). All packets dropped as a 2134 result of an incoming interface check are counted here. 2136 If this counter increases rapidly, this indicates a problem. 2137 A significant quantity of multicast data is arriving at this 2138 router on unexpected interfaces, and is not being forwarded. 2140 For guidance, if the rate of increase of this counter 2141 exceeds 1% of the rate of increase of mvpnMrouteOctets, 2142 then there are multicast routing problems that require 2143 investigation. 2145 Discontinuities in this monotonically increasing value 2146 occur at re-initialization of the management system. 2147 Discontinuities can also occur as a result of routes being 2148 removed and replaced, which can be detected by observing 2149 the value of mvpnMrouteTimeStamp. 2150 " 2151 REFERENCE 2152 "RFC 4601 2153 RFC 5015 2154 " 2155 ::= { mvpnMrouteEntry 22 } 2157 mvpnMrouteDifferentInIfPackets OBJECT-TYPE 2158 SYNTAX Counter64 2159 MAX-ACCESS read-only 2160 STATUS current 2161 DESCRIPTION 2162 "The number of packets which this router has received from 2163 these sources and addressed to this multicast group address, 2164 which were dropped because they were received on an 2165 unexpected interface. 2167 For RPF checking protocols (such as PIM-SM), these packets 2168 arrived on interfaces other than mvpnMrouteInIfIndex, and 2169 were dropped because of this failed RPF check. (RPF paths 2170 are 'Reverse Path Forwarding' path; the unicast routes to 2171 the expected origin of multicast data flows). 2173 Other protocols may drop packets on an incoming interface 2174 check for different reasons (for example, BIDIR-PIM performs 2175 a DF check on receipt of packets). All packets dropped as a 2176 result of an incoming interface check are counted here. 2178 If this counter increases rapidly, this indicates a problem. 2179 A significant quantity of multicast data is arriving at this 2180 router on unexpected interfaces, and is not being forwarded. 2182 For guidance, if the rate of increase of this counter 2183 exceeds 1% of the rate of increase of mvpnMroutePkts, then 2184 there are multicast routing problems that require 2185 investigation. 2187 Discontinuities in this monotonically increasing value 2188 occur at re-initialization of the management system. 2189 Discontinuities can also occur as a result of routes being 2190 removed and replaced, which can be detected by observing 2191 the value of mvpnMrouteTimeStamp. 2192 " 2193 REFERENCE 2194 "RFC 4601 2195 RFC 5015 2196 " 2197 ::= { mvpnMrouteEntry 23 } 2199 mvpnMrouteBps OBJECT-TYPE 2200 SYNTAX CounterBasedGauge64 2201 UNITS "bits per second" 2202 MAX-ACCESS read-only 2203 STATUS current 2204 DESCRIPTION 2205 "Bits per second forwarded by this router using this 2206 multicast routing entry. 2208 This value is a sample; it is the number of bits forwarded 2209 during the last whole 1 second sampling period. The value 2210 during the current 1 second sampling period is not made 2211 available until the period is completed. 2213 The quantity being sampled is the same as that measured by 2214 mvpnMrouteOctets. The units and the sampling method are 2215 different. 2216 " 2217 ::= { mvpnMrouteEntry 24 } 2219 mvpnMroutePmsiPointer OBJECT-TYPE 2220 SYNTAX RowPointer 2221 MAX-ACCESS read-only 2222 STATUS current 2223 DESCRIPTION 2224 "The I-PMSI or S-PMSI this C-multicast route is using. 2225 This is important because an implementation may not have an 2226 interface corresponding to a provider tunnel, 2227 that can be used in mvpnMrouteNextHopEntry. 2228 " 2229 ::= { mvpnMrouteEntry 25 } 2231 mvpnMrouteNumberOfLocalReplication OBJECT-TYPE 2232 SYNTAX Unsigned32 2233 MAX-ACCESS read-only 2234 STATUS current 2235 DESCRIPTION 2236 "Number of replications for local receivers. 2237 For example, if an ingress PE needs to send traffic out of 2238 N PE-CE interfaces, then mvpnMrouteNumberOfLocalReplication 2239 is N. 2240 " 2241 ::= { mvpnMrouteEntry 26 } 2243 mvpnMrouteNumberOfRemoteReplication OBJECT-TYPE 2244 SYNTAX Unsigned32 2245 MAX-ACCESS read-only 2246 STATUS current 2247 DESCRIPTION 2248 "Number of local replications for remote PEs. For example, 2249 if the number of remote PEs that need to receive traffic is N, 2250 then mvpnMrouteNumberOfRemoteReplication is N in case of 2251 Ingress Replication, but may be less than N in case of RSVP-TE 2252 or mLDP P2MP tunnels, depending on the actual number of 2253 replications the PE needs do. 2254 " 2256 ::= { mvpnMrouteEntry 27 } 2258 mvpnMrouteNextHopTable OBJECT-TYPE 2259 SYNTAX SEQUENCE OF MvpnMrouteNextHopEntry 2260 MAX-ACCESS not-accessible 2261 STATUS current 2262 DESCRIPTION 2263 "The (conceptual) table containing information on the 2264 next-hops on outgoing interfaces for routing IP multicast 2265 datagrams. Each entry is one of a list of next-hops on 2266 outgoing interfaces for particular sources sending to a 2267 particular multicast group address." 2268 ::= { mvpnStates 5 } 2270 mvpnMrouteNextHopEntry OBJECT-TYPE 2271 SYNTAX MvpnMrouteNextHopEntry 2272 MAX-ACCESS not-accessible 2273 STATUS current 2274 DESCRIPTION 2275 "An entry (conceptual row) in the list of next-hops on 2276 outgoing interfaces to which IP multicast datagrams from 2277 particular sources to an IP multicast group address are 2278 routed. 2280 OIDs are limited to 128 sub-identifiers, but this limit 2281 is not enforced by the syntax of this entry. In practice, 2282 this does not present a problem, because IP address types 2283 allowed by conformance statements do not exceed this limit. 2284 " 2285 INDEX { 2286 mplsL3VpnVrfName, 2287 mvpnMrouteNextHopGroupAddrType, 2288 mvpnMrouteNextHopGroupAddr, 2289 mvpnMrouteNextHopGroupPrefixLength, 2290 mvpnMrouteNextHopSourceAddrType, 2291 mvpnMrouteNextHopSourceAddr, 2292 mvpnMrouteNextHopSourcePrefixLength, 2293 mvpnMrouteNextHopIfIndex, 2294 mvpnMrouteNextHopAddrType, 2295 mvpnMrouteNextHopAddr 2296 } 2297 ::= { mvpnMrouteNextHopTable 1 } 2299 MvpnMrouteNextHopEntry ::= SEQUENCE { 2300 mvpnMrouteNextHopGroupAddrType InetAddressType, 2301 mvpnMrouteNextHopGroupAddr InetAddress, 2302 mvpnMrouteNextHopGroupPrefixLength InetAddressPrefixLength, 2303 mvpnMrouteNextHopSourceAddrType InetAddressType, 2304 mvpnMrouteNextHopSourceAddr InetAddress, 2305 mvpnMrouteNextHopSourcePrefixLength InetAddressPrefixLength, 2306 mvpnMrouteNextHopIfIndex InterfaceIndex, 2307 mvpnMrouteNextHopAddrType InetAddressType, 2308 mvpnMrouteNextHopAddr InetAddress, 2309 mvpnMrouteNextHopState INTEGER, 2310 mvpnMrouteNextHopTimeStamp TimeStamp, 2311 mvpnMrouteNextHopExpiryTime TimeTicks, 2312 mvpnMrouteNextHopClosestMemberHops Unsigned32, 2313 mvpnMrouteNextHopProtocol IANAipMRouteProtocol, 2314 mvpnMrouteNextHopOctets Counter64, 2315 mvpnMrouteNextHopPkts Counter64 2316 } 2318 mvpnMrouteNextHopGroupAddrType OBJECT-TYPE 2319 SYNTAX InetAddressType 2320 MAX-ACCESS not-accessible 2321 STATUS current 2322 DESCRIPTION 2323 "A value indicating the address family of the address 2324 contained in mvpnMrouteNextHopGroupAddr. Legal values 2325 correspond to the subset of address families for which 2326 multicast forwarding is supported. 2327 " 2328 ::= { mvpnMrouteNextHopEntry 1 } 2330 mvpnMrouteNextHopGroupAddr OBJECT-TYPE 2331 SYNTAX InetAddress 2332 MAX-ACCESS not-accessible 2333 STATUS current 2334 DESCRIPTION 2335 "The IP multicast group address which, when combined with 2336 the corresponding value specified in 2337 mvpnMrouteNextHopGroupPrefixLength, identifies the groups 2338 for which this entry contains multicast forwarding 2339 information. 2341 This address object is only significant up to 2342 mvpnMrouteNextHopGroupPrefixLength bits. The remaining 2343 address bits are set to zero. This is especially important 2344 for this index field, which is part of the index of this 2345 entry. Any non-zero bits would signify an entirely 2346 different entry. 2348 For addresses of type ipv4z or ipv6z, the appended zone 2349 index is significant even though it lies beyond the prefix 2350 length. The use of these address types indicate that this 2351 forwarding state applies only within the given zone. Zone 2352 index zero is not valid in this table. 2353 " 2354 ::= { mvpnMrouteNextHopEntry 2 } 2356 mvpnMrouteNextHopGroupPrefixLength OBJECT-TYPE 2357 SYNTAX InetAddressPrefixLength 2358 MAX-ACCESS not-accessible 2359 STATUS current 2360 DESCRIPTION 2361 "The length in bits of the mask which, when combined with 2362 the corresponding value of mvpnMrouteGroup, identifies the 2363 groups for which this entry contains multicast routing 2364 information. 2366 The InetAddressType is given by 2367 mvpnMrouteNextHopGroupAddressType. For values 'ipv4' and 2368 'ipv4z', this object must be in the range 4..32. For values 2369 'ipv6' and 'ipv6z', this object must be in the range 2370 8..128. 2371 " 2372 ::= { mvpnMrouteNextHopEntry 3 } 2374 mvpnMrouteNextHopSourceAddrType OBJECT-TYPE 2375 SYNTAX InetAddressType 2376 MAX-ACCESS not-accessible 2377 STATUS current 2378 DESCRIPTION 2379 "A value indicating the address family of the address 2380 contained in mvpnMrouteNextHopSourceAddr. 2382 A value of unknown(0) indicates a non-source-specific entry, 2383 corresponding to all sources in the group. Otherwise, the 2384 value MUST be the same as the value of 2385 mvpnMrouteNextHopGroupAddrType." 2386 ::= { mvpnMrouteNextHopEntry 4 } 2388 mvpnMrouteNextHopSourceAddr OBJECT-TYPE 2389 SYNTAX InetAddress 2390 MAX-ACCESS not-accessible 2391 STATUS current 2392 DESCRIPTION 2393 "The network address which, when combined with the 2394 corresponding value of the mask specified in 2395 mvpnMrouteNextHopSourcePrefixLength, identifies the 2396 sources for which this entry specifies a next-hop on an 2397 outgoing interface. 2399 This address object is only significant up to 2400 mvpnMrouteNextHopSourcePrefixLength bits. The remaining 2401 address bits are set to zero. This is especially important 2402 for this index field, which is part of the index of this 2403 entry. Any non-zero bits would signify an entirely 2404 different entry. 2406 For addresses of type ipv4z or ipv6z, the appended zone 2407 index is significant even though it lies beyond the prefix 2408 length. The use of these address types indicate that this 2409 source address applies only within the given zone. Zone 2410 index zero is not valid in this table. 2411 " 2412 ::= { mvpnMrouteNextHopEntry 5 } 2414 mvpnMrouteNextHopSourcePrefixLength OBJECT-TYPE 2415 SYNTAX InetAddressPrefixLength 2416 MAX-ACCESS not-accessible 2417 STATUS current 2418 DESCRIPTION 2419 "The length in bits of the mask which, when combined with 2420 the corresponding value specified in 2421 mvpnMrouteNextHopSource, identifies the sources for which 2422 this entry specifies a next-hop on an outgoing interface. 2423 The InetAddressType is given by 2424 mvpnMrouteNextHopSourceAddressType. For the value 2425 'unknown', this object must be zero. For values 'ipv4' and 2426 'ipv4z', this object must be in the range 4..32. For values 2427 'ipv6' and 'ipv6z', this object must be in the range 2428 8..128. 2429 " 2430 ::= { mvpnMrouteNextHopEntry 6 } 2432 mvpnMrouteNextHopIfIndex OBJECT-TYPE 2433 SYNTAX InterfaceIndex 2434 MAX-ACCESS not-accessible 2435 STATUS current 2436 DESCRIPTION 2437 "The ifIndex value of the interface for the outgoing 2438 interface for this next-hop. 2439 " 2440 ::= { mvpnMrouteNextHopEntry 7 } 2442 mvpnMrouteNextHopAddrType OBJECT-TYPE 2443 SYNTAX InetAddressType 2444 MAX-ACCESS not-accessible 2445 STATUS current 2446 DESCRIPTION 2447 "A value indicating the address family of the address 2448 contained in mvpnMrouteNextHopAddr. 2449 " 2450 ::= { mvpnMrouteNextHopEntry 8 } 2452 mvpnMrouteNextHopAddr OBJECT-TYPE 2453 SYNTAX InetAddress 2454 MAX-ACCESS not-accessible 2455 STATUS current 2456 DESCRIPTION 2457 "The address of the next-hop specific to this entry. For 2458 most interfaces, this is identical to 2459 mvpnMrouteNextHopGroup. Non-Broadcast Multi-Access 2460 (NBMA) interfaces, however, may 2461 have multiple next-hop addresses out a single outgoing 2462 interface. 2463 " 2464 ::= { mvpnMrouteNextHopEntry 9 } 2466 mvpnMrouteNextHopState OBJECT-TYPE 2467 SYNTAX INTEGER { pruned(1), forwarding(2) } 2468 MAX-ACCESS read-only 2469 STATUS current 2470 DESCRIPTION 2471 "An indication of whether the outgoing interface and next- 2472 hop represented by this entry is currently being used to 2473 forward IP datagrams. The value 'forwarding' indicates it 2474 is currently being used; the value 'pruned' indicates it is 2475 not. 2476 " 2477 ::= { mvpnMrouteNextHopEntry 10 } 2479 mvpnMrouteNextHopTimeStamp OBJECT-TYPE 2480 SYNTAX TimeStamp 2481 MAX-ACCESS read-only 2482 STATUS current 2483 DESCRIPTION 2484 "The value of sysUpTime at which the multicast routing 2485 information represented by this entry was learned by the 2486 router. 2488 If this information was present at the most recent re- 2489 initialization of the local management subsystem, then this 2490 object contains a zero value. 2491 " 2492 ::= { mvpnMrouteNextHopEntry 11 } 2494 mvpnMrouteNextHopExpiryTime OBJECT-TYPE 2495 SYNTAX TimeTicks 2496 MAX-ACCESS read-only 2497 STATUS current 2498 DESCRIPTION 2499 "The minimum amount of time remaining before this entry will 2500 be aged out. If mvpnMrouteNextHopState is pruned(1), the 2501 remaining time until the prune expires and the state reverts 2502 to forwarding(2). Otherwise, the remaining time until this 2503 entry is removed from the table. The time remaining may be 2504 copied from mvpnMrouteExpiryTime if the protocol in use 2505 for this entry does not specify next-hop timers. The value 2506 0 indicates that the entry is not subject to aging. 2507 " 2508 ::= { mvpnMrouteNextHopEntry 12 } 2510 mvpnMrouteNextHopClosestMemberHops OBJECT-TYPE 2511 SYNTAX Unsigned32 (0..256) 2512 MAX-ACCESS read-only 2513 STATUS current 2514 DESCRIPTION 2515 "The minimum number of hops between this router and any 2516 member of this IP multicast group reached via this next-hop 2517 on this outgoing interface. Any IP multicast datagrams for 2518 the group that have a TTL (IPv4) or Hop Count (IPv6) less 2519 than this number of hops will not be forwarded to this 2520 next-hop. 2522 A value of 0 means all multicast datagrams are forwarded out 2523 the interface. A value of 256 means that no multicast 2524 datagrams are forwarded out the interface. 2526 This is an optimization applied by multicast routing 2527 protocols that explicitly track hop counts to downstream 2528 listeners. Multicast protocols that are not aware of hop 2529 counts to downstream listeners set this object to 0. 2530 " 2531 ::= { mvpnMrouteNextHopEntry 13 } 2533 mvpnMrouteNextHopProtocol OBJECT-TYPE 2534 SYNTAX IANAipMRouteProtocol 2535 MAX-ACCESS read-only 2536 STATUS current 2537 DESCRIPTION 2538 "The routing mechanism via which this next-hop was learned." 2539 ::= { mvpnMrouteNextHopEntry 14 } 2541 mvpnMrouteNextHopOctets OBJECT-TYPE 2542 SYNTAX Counter64 2543 MAX-ACCESS read-only 2544 STATUS current 2545 DESCRIPTION 2546 "The number of octets of multicast packets that have been 2547 forwarded using this route. 2549 Discontinuities in this monotonically increasing value 2550 occur at re-initialization of the management system. 2551 Discontinuities can also occur as a result of routes being 2552 removed and replaced, which can be detected by observing 2553 the value of mvpnMrouteNextHopTimeStamp." 2554 ::= { mvpnMrouteNextHopEntry 15 } 2556 mvpnMrouteNextHopPkts OBJECT-TYPE 2557 SYNTAX Counter64 2558 MAX-ACCESS read-only 2559 STATUS current 2560 DESCRIPTION 2561 "The number of packets which have been forwarded using this 2562 route. 2564 Discontinuities in this monotonically increasing value 2565 occur at re-initialization of the management system. 2566 Discontinuities can also occur as a result of routes being 2567 removed and replaced, which can be detected by observing 2568 the value of ipMcastRouteNextHopTimeStamp." 2569 ::= { mvpnMrouteNextHopEntry 16 } 2571 -- MVPN Notifications 2573 mvpnMvrfOperationChange NOTIFICATION-TYPE 2574 OBJECTS { 2575 mvpnGenMvrfLastOperation 2576 } 2577 STATUS current 2578 DESCRIPTION 2579 "A mvpnMvrfOperationChange notification signifies a change about 2580 a MVRF in the PE. The change event can be creation of 2581 the MVRF, deletion of the MVRF or an update on the I-PMSI 2582 or S-PMSI information of the MVRF. The change event 2583 is indicated by mvpnGenMvrfLastOperation embedded in 2584 the notification. The user can then query 2585 mvpnGenericTable, mvpnPmsiTable, and/or mvpnSpmsiTable to 2586 get the details of the change as necessary. 2588 Note: Since the creation of a MVRF is often followed by 2589 configuration of I-PMSI and/or S-PMSIs for the MVRF, 2590 more than one (three at most) notifications for a MVRF may 2591 be generated serially, and it is really not necessary to 2592 generate all three of them. An agent may choose to generate a 2593 notification for the last event only, that is for S-PMSI 2594 configuration. 2596 Similarly, deletion of I-PMSI and S-PMSI configuration on a 2597 MVRF happens before a MVRF is deleted and it is recommended 2598 that the agent send the notification for MVRF deletion 2599 event only. 2600 " 2601 ::= { mvpnNotifications 1 } 2603 mvpnMvrfGroupJoined NOTIFICATION-TYPE 2604 OBJECTS { 2605 mvpnMrouteTimeStamp 2606 } 2607 STATUS current 2608 DESCRIPTION 2609 "A mvpnMvrfGroupJoined notification signifies that 2610 this PE has joined to a new multicast group 2611 serviced in a particular MVPN. 2612 The change event is indicated by mvpnMrouteTimeStamp 2613 embedded in the notification. 2614 " 2615 ::= { mvpnNotifications 2 } 2617 mvpnMvrfGroupLeft NOTIFICATION-TYPE 2618 OBJECTS { 2619 mvpnMrouteTimeStamp 2620 } 2621 STATUS current 2622 DESCRIPTION 2623 "A mvpnMvrfGroupJoined notification signifies that 2624 this PE has left from a multicast group 2625 serviced in a particular MVPN. 2626 The change event is indicated by mvpnMrouteTimeStamp 2627 embedded in the notification. 2628 " 2629 ::= { mvpnNotifications 3 } 2631 -- MVPN MIB Conformance Information 2633 mvpnGroups OBJECT IDENTIFIER ::= { mvpnConformance 1 } 2634 mvpnCompliances OBJECT IDENTIFIER ::= { mvpnConformance 2 } 2636 -- Compliance Statements 2638 mvpnModuleFullCompliance MODULE-COMPLIANCE 2639 STATUS current 2640 DESCRIPTION 2641 "Compliance statement for agents that provide full support 2642 for the MCAST-VPN-MIB 2643 " 2644 MODULE -- this module 2645 MANDATORY-GROUPS { 2646 mvpnScalarGroup, 2647 mvpnGenericGroup, 2648 mvpnPmsiGroup, 2649 mvpnSpmsiGroup, 2650 mvpnSpmsiAdvtGroup, 2651 mvpnMrouteGroup, 2652 mvpnMrouteNextHopGroup, 2653 mvpnNotificationGroup 2654 } 2656 GROUP mvpnIpmsiGroup 2657 DESCRIPTION 2658 "This group is mandatory for systems that support 2659 BGP signaling for I-PMSI. 2660 " 2662 GROUP mvpnInterAsIpmsiGroup 2663 DESCRIPTION 2664 "This group is mandatory for systems that support 2665 Inter-AS Segmented I-PMSI. 2666 " 2668 GROUP mvpnBgpGenericGroup 2669 DESCRIPTION 2670 "This group is mandatory for systems that support 2671 BGP-MVPN. 2672 " 2674 GROUP mvpnOptionalGroup 2675 DESCRIPTION 2676 "This group is optional. 2677 " 2679 ::= { mvpnCompliances 1 } 2681 mvpnModuleReadOnlyCompliance MODULE-COMPLIANCE 2682 STATUS current 2683 DESCRIPTION "Compliance requirement for implementations that 2684 only provide read-only support for MCAST-VPN-MIB. 2685 Such devices can then be monitored but cannot be 2686 configured using this MIB module. 2688 " 2689 MODULE -- this module 2690 MANDATORY-GROUPS { 2691 mvpnScalarGroup, 2692 mvpnGenericGroup, 2693 mvpnPmsiGroup, 2694 mvpnSpmsiGroup, 2695 mvpnSpmsiAdvtGroup, 2696 mvpnMrouteGroup, 2697 mvpnMrouteNextHopGroup, 2698 mvpnNotificationGroup 2699 } 2701 GROUP mvpnIpmsiGroup 2702 DESCRIPTION 2703 "This group is mandatory for systems that support 2704 BGP signaling for I-PMSI. 2705 " 2707 GROUP mvpnInterAsIpmsiGroup 2708 DESCRIPTION 2709 "This group is mandatory for systems that support 2710 Inter-AS Segmented I-PMSI. 2711 " 2713 GROUP mvpnBgpGenericGroup 2714 DESCRIPTION 2715 "This group is mandatory for systems that support 2716 BGP-MVPN. 2717 " 2719 GROUP mvpnOptionalGroup 2720 DESCRIPTION 2721 "This group is optional. 2722 " 2724 OBJECT mvpnGenCmcastRouteProtocol 2725 MIN-ACCESS read-only 2726 DESCRIPTION "Write access is not required." 2728 OBJECT mvpnGenIpmsiInfo 2729 MIN-ACCESS read-only 2730 DESCRIPTION "Write access is not required." 2732 OBJECT mvpnGenInterAsPmsiInfo 2733 MIN-ACCESS read-only 2734 DESCRIPTION "Write access is not required." 2735 OBJECT mvpnGenUmhSelection 2736 MIN-ACCESS read-only 2737 DESCRIPTION "Write access is not required." 2739 OBJECT mvpnGenCustomerSiteType 2740 MIN-ACCESS read-only 2741 DESCRIPTION "Write access is not required." 2743 OBJECT mvpnGenSPTunnelLimit 2744 MIN-ACCESS read-only 2745 DESCRIPTION "Write access is not required." 2747 OBJECT mvpnPmsiEncapsulationType 2748 MIN-ACCESS read-only 2749 DESCRIPTION "Write access is not required." 2751 OBJECT mvpnSpmsiThreshold 2752 MIN-ACCESS read-only 2753 DESCRIPTION "Write access is not required." 2755 OBJECT mvpnSpmsiPmsiPointer 2756 MIN-ACCESS read-only 2757 DESCRIPTION "Write access is not required." 2759 ::= { mvpnCompliances 2 } 2761 -- units of conformance 2763 mvpnScalarGroup OBJECT-GROUP 2764 OBJECTS { 2765 mvpnMvrfs, 2766 mvpnV4Mvrfs, 2767 mvpnV6Mvrfs, 2768 mvpnPimV4Mvrfs, 2769 mvpnPimV6Mvrfs, 2770 mvpnBgpV4Mvrfs, 2771 mvpnBgpV6Mvrfs, 2772 mvpnMldpMvrfs 2773 } 2774 STATUS current 2775 DESCRIPTION 2776 "These objects are used to monitor/manage 2777 global MVPN parameters. 2778 " 2779 ::= { mvpnGroups 1 } 2781 mvpnGenericGroup OBJECT-GROUP 2782 OBJECTS { 2783 mvpnGenMvrfLastOperation, 2784 mvpnGenMvrfLastOperationTime, 2785 mvpnGenCmcastRouteProtocol, 2786 mvpnGenIpmsiInfo, 2787 mvpnGenInterAsPmsiInfo, 2788 mvpnGenUmhSelection, 2789 mvpnGenCustomerSiteType, 2790 mvpnGenSPTunnelLimit 2791 } 2792 STATUS current 2793 DESCRIPTION 2794 "These objects are used to monitor/manage 2795 per-VRF MVPN parameters. 2796 " 2797 ::= { mvpnGroups 2 } 2799 mvpnPmsiGroup OBJECT-GROUP 2800 OBJECTS { 2801 mvpnPmsiEncapsulationType 2802 } 2803 STATUS current 2804 DESCRIPTION 2805 "These objects are used to monitor/manage 2806 PMSI tunnel configurations. 2807 " 2808 ::= { mvpnGroups 3 } 2810 mvpnSpmsiGroup OBJECT-GROUP 2811 OBJECTS { 2812 mvpnSpmsiThreshold, 2813 mvpnSpmsiPmsiPointer 2814 } 2815 STATUS current 2816 DESCRIPTION 2817 "These objects are used to monitor/manage 2818 S-PMSI configurations. 2819 " 2820 ::= { mvpnGroups 4 } 2822 mvpnIpmsiGroup OBJECT-GROUP 2823 OBJECTS { 2824 mvpnIpmsiAdvtTunnelAttribute, 2825 mvpnIpmsiAdvtReceived, 2826 mvpnIpmsiAdvtReceivedError, 2827 mvpnIpmsiAdvtMalformedTunnelType, 2828 mvpnIpmsiAdvtMalformedTunnelId, 2829 mvpnIpmsiAdvtLastReceivedTime, 2830 mvpnIpmsiAdvtCounterDiscontinuityTime 2832 } 2833 STATUS current 2834 DESCRIPTION 2835 "These objects are used to monitor/manage 2836 Intra-AS I-PMSI attributes. 2837 " 2838 ::= { mvpnGroups 5 } 2840 mvpnInterAsIpmsiGroup OBJECT-GROUP 2841 OBJECTS { 2842 mvpnInterAsIpmsiAdvtTunnelAttribute, 2843 mvpnInterAsIpmsiAdvtReceived, 2844 mvpnInterAsIpmsiAdvtReceivedError, 2845 mvpnInterAsIpmsiAdvtMalformedTunnelType, 2846 mvpnInterAsIpmsiAdvtMalformedTunnelId, 2847 mvpnInterAsIpmsiAdvtLastReceivedTime, 2848 mvpnInterAsIpmsiAdvtCounterDiscontinuityTime 2849 } 2850 STATUS current 2851 DESCRIPTION 2852 "These objects are used to monitor/manage 2853 Inter-AS I-PMSI attributes. 2854 " 2855 ::= { mvpnGroups 6 } 2857 mvpnSpmsiAdvtGroup OBJECT-GROUP 2858 OBJECTS { 2859 mvpnSpmsiAdvtTunnelAttribute, 2860 mvpnSpmsiAdvtExpTime, 2861 mvpnSpmsiAdvtRefCnt, 2862 mvpnSpmsiAdvtReceived, 2863 mvpnSpmsiAdvtReceivedError, 2864 mvpnSpmsiAdvtMalformedTunnelType, 2865 mvpnSpmsiAdvtMalformedTunnelId, 2866 mvpnSpmsiAdvtLastReceivedTime, 2867 mvpnSpmsiAdvtCounterDiscontinuityTime 2868 } 2869 STATUS current 2870 DESCRIPTION 2871 "These objects are used to monitor/manage 2872 S-PMSI attributes. 2873 " 2874 ::= { mvpnGroups 7 } 2876 mvpnMrouteGroup OBJECT-GROUP 2877 OBJECTS { 2878 mvpnMrouteUpstreamNeighborAddrType, 2879 mvpnMrouteUpstreamNeighborAddr, 2880 mvpnMrouteInIfIndex, 2881 mvpnMrouteTimeStamp, 2882 mvpnMrouteExpiryTime, 2883 mvpnMrouteProtocol, 2884 mvpnMrouteRtProtocol, 2885 mvpnMrouteRtAddrType, 2886 mvpnMrouteRtAddr, 2887 mvpnMrouteRtPrefixLength, 2888 mvpnMrouteRtType, 2889 mvpnMrouteOctets, 2890 mvpnMroutePkts, 2891 mvpnMrouteTtlDropOctets, 2892 mvpnMrouteTtlDropPackets, 2893 mvpnMrouteDifferentInIfOctets, 2894 mvpnMrouteDifferentInIfPackets, 2895 mvpnMrouteBps, 2896 mvpnMroutePmsiPointer, 2897 mvpnMrouteNumberOfLocalReplication, 2898 mvpnMrouteNumberOfRemoteReplication 2899 } 2900 STATUS current 2901 DESCRIPTION 2902 "These objects are used to monitor/manage 2903 VPN multicast forwarding states. 2904 " 2905 ::= { mvpnGroups 8 } 2907 mvpnMrouteNextHopGroup OBJECT-GROUP 2908 OBJECTS { 2909 mvpnMrouteNextHopState, 2910 mvpnMrouteNextHopTimeStamp, 2911 mvpnMrouteNextHopExpiryTime, 2912 mvpnMrouteNextHopClosestMemberHops, 2913 mvpnMrouteNextHopProtocol, 2914 mvpnMrouteNextHopOctets, 2915 mvpnMrouteNextHopPkts 2916 } 2917 STATUS current 2918 DESCRIPTION 2919 "These objects are used to monitor/manage 2920 next hop information of VPN multicast. 2921 " 2922 ::= { mvpnGroups 9 } 2924 mvpnBgpGenericGroup OBJECT-GROUP 2925 OBJECTS { 2926 mvpnBgpGenMode, 2927 mvpnBgpGenVrfRouteImport, 2928 mvpnBgpGenSrcAs, 2929 mvpnBgpGenCmcastRouteWithdrawalTimer, 2930 mvpnBgpGenSrcSharedTreeJoinTimer, 2931 mvpnBgpGenMsgRateLimit, 2932 mvpnBgpGenMaxSpmsiAdRoutes, 2933 mvpnBgpGenMaxSpmsiAdRouteFreq, 2934 mvpnBgpGenMaxSrcActiveAdRoutes, 2935 mvpnBgpGenMaxSrcActiveAdRouteFreq 2936 } 2937 STATUS current 2938 DESCRIPTION 2939 "These objects are used to monitor/manage BGP-MVPN." 2940 ::= { mvpnGroups 10 } 2942 mvpnOptionalGroup OBJECT-GROUP 2943 OBJECTS { 2944 mvpnMroutePmsiPointer 2945 } 2946 STATUS current 2947 DESCRIPTION 2948 "Support of these object is not required." 2949 ::= { mvpnGroups 11 } 2951 mvpnNotificationGroup NOTIFICATION-GROUP 2952 NOTIFICATIONS { 2953 mvpnMvrfOperationChange, 2954 mvpnMvrfGroupJoined, 2955 mvpnMvrfGroupLeft 2956 } 2957 STATUS current 2958 DESCRIPTION 2959 "Objects required for MVPN notifications." 2960 ::= { mvpnGroups 12 } 2962 END 2964 4. Security Considerations 2966 This MIB contains some read-only objects that may be deemed senstive 2967 by some though perhaps not all operators. It also contains some 2968 read- write objects, whose setting will change the device's behavior 2969 related to MVPN. Appropriate security procedures related to SNMP in 2970 general but not specific to this MIB need to be implemented by 2971 concerned operators. 2973 There are a number of management objects defined in this MIB module 2974 with a MAX-ACCESS clause of read-write and/or read-create. Such 2975 objects may be considered sensitive or vulnerable in some network 2976 environments. The support for SET operations in a non-secure 2977 environment without proper protection opens devices to attack. These 2978 are the tables and objects and their sensitivity/vulnerability: 2980 o mvpnGenCmcastRouteProtocol, mvpnGenIpmsiInfo, 2981 mvpnGenInterAsPmsiInfo, mvpnGenUmhSelection, 2982 mvpnGenCustomerSiteType, mvpnGenSPTunnelLimit, mvpnBgpGenMode, 2983 mvpnBgpGenVrfRtImport, mvpnPmsiEncapsulationType, 2984 mvpnSpmsiThreshold, mvpnSpmsiPmsiPointer 2986 Some of the readable objects in this MIB module (i.e., objects with a 2987 MAX-ACCESS other than not-accessible) may be considered sensitive or 2988 vulnerable in some network environments. It is thus important to 2989 control even GET and/or NOTIFY access to these objects and possibly 2990 to even encrypt the values of these objects when sending them over 2991 the network via SNMP. These are the tables and objects and their 2992 sensitivity/vulnerability: 2994 o [TBD] 2996 SNMP versions prior to SNMPv3 did not include adequate security. 2997 Even if the network itself is secure (for example by using IPsec), 2998 there is no control as to who on the secure network is allowed to 2999 access and GET/SET (read/change/create/delete) the objects in this 3000 MIB module. 3002 Implementations SHOULD provide the security features described by the 3003 SNMPv3 framework (see [RFC3410]), and implementations claiming 3004 compliance to the SNMPv3 standard MUST include full support for 3005 authentication and privacy via the User-based Security Model (USM) 3006 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 3007 MAY also provide support for the Transport Security Model (TSM) 3008 [RFC5591] in combination with a secure transport such as SSH 3009 [RFC5592] or TLS/DTLS [RFC6353]. 3011 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3012 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3013 enable cryptographic security. It is then a customer/operator 3014 responsibility to ensure that the SNMP entity giving access to an 3015 instance of this MIB module is properly configured to give access to 3016 the objects only to those principals (users) that have legitimate 3017 rights to indeed GET or SET (change/create/delete) them. 3019 5. IANA Considerations 3021 IANA is requested to root MIB objects in the MIB module contained in 3022 this document under the mib-2 subtree. 3024 6. Acknowledgement 3026 This document borrowed some text from Cisco PIM-MVPN MIB 3027 [I-D.svaidya-mcast-vpn-mib]. We would like to thank Yakov Rekhter, 3028 Jeffrey Haas, Huajin Jeng, Durga Prasad Velamuri for their helpful 3029 comments. 3031 7. References 3033 7.1. Normative References 3035 [RFC2003] Perkins, C., "IP Encapsulation within IP", RFC 2003, DOI 3036 10.17487/RFC2003, October 1996, . 3039 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3040 Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ 3041 RFC2119, March 1997, . 3044 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3045 Schoenwaelder, Ed., "Structure of Management Information 3046 Version 2 (SMIv2)", STD 58, RFC 2578, DOI 10.17487/ 3047 RFC2578, April 1999, . 3050 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3051 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 3052 58, RFC 2579, DOI 10.17487/RFC2579, April 1999, 3053 . 3055 [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. 3056 Schoenwaelder, Ed., "Conformance Statements for SMIv2", 3057 STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999, 3058 . 3060 [RFC2784] Farinacci, D., Li, T., Hanks, S., Meyer, D., and P. 3061 Traina, "Generic Routing Encapsulation (GRE)", RFC 2784, 3062 DOI 10.17487/RFC2784, March 2000, . 3065 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 3066 MIB", RFC 2863, DOI 10.17487/RFC2863, June 2000, 3067 . 3069 [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., 3070 Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack 3071 Encoding", RFC 3032, DOI 10.17487/RFC3032, January 2001, 3072 . 3074 [RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model 3075 (USM) for version 3 of the Simple Network Management 3076 Protocol (SNMPv3)", STD 62, RFC 3414, DOI 10.17487/ 3077 RFC3414, December 2002, . 3080 [RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The 3081 Advanced Encryption Standard (AES) Cipher Algorithm in the 3082 SNMP User-based Security Model", RFC 3826, DOI 10.17487/ 3083 RFC3826, June 2004, . 3086 [RFC4382] Nadeau, T., Ed. and H. van der Linde, Ed., "MPLS/BGP Layer 3087 3 Virtual Private Network (VPN) Management Information 3088 Base", RFC 4382, DOI 10.17487/RFC4382, February 2006, 3089 . 3091 [RFC4659] De Clercq, J., Ooms, D., Carugi, M., and F. Le Faucheur, 3092 "BGP-MPLS IP Virtual Private Network (VPN) Extension for 3093 IPv6 VPN", RFC 4659, DOI 10.17487/RFC4659, September 2006, 3094 . 3096 [RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model 3097 for the Simple Network Management Protocol (SNMP)", STD 3098 78, RFC 5591, DOI 10.17487/RFC5591, June 2009, 3099 . 3101 [RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure 3102 Shell Transport Model for the Simple Network Management 3103 Protocol (SNMP)", RFC 5592, DOI 10.17487/RFC5592, June 3104 2009, . 3106 [RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport 3107 Model for the Simple Network Management Protocol (SNMP)", 3108 STD 78, RFC 6353, DOI 10.17487/RFC6353, July 2011, 3109 . 3111 [RFC6513] Rosen, E., Ed. and R. Aggarwal, Ed., "Multicast in MPLS/ 3112 BGP IP VPNs", RFC 6513, DOI 10.17487/RFC6513, February 3113 2012, . 3115 [RFC6514] Aggarwal, R., Rosen, E., Morin, T., and Y. Rekhter, "BGP 3116 Encodings and Procedures for Multicast in MPLS/BGP IP 3117 VPNs", RFC 6514, DOI 10.17487/RFC6514, February 2012, 3118 . 3120 [RFC6625] Rosen, E., Ed., Rekhter, Y., Ed., Hendrickx, W., and R. 3121 Qiu, "Wildcards in Multicast VPN Auto-Discovery Routes", 3122 RFC 6625, DOI 10.17487/RFC6625, May 2012, 3123 . 3125 [RFC7761] Fenner, B., Handley, M., Holbrook, H., Kouvelas, I., 3126 Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent 3127 Multicast - Sparse Mode (PIM-SM): Protocol Specification 3128 (Revised)", STD 83, RFC 7761, DOI 10.17487/RFC7761, March 3129 2016, . 3131 [RTPROTO] IANA, "IP Route Protocol MIB", 2016, 3132 . 3134 7.2. Informative References 3136 [I-D.svaidya-mcast-vpn-mib] 3137 Vaidya, S., "Multicast in BGP/MPLS IP VPNs Management 3138 Information Base", draft-svaidya-mcast-vpn-mib-02 (work in 3139 progress), March 2005. 3141 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 3142 "Introduction and Applicability Statements for Internet- 3143 Standard Management Framework", RFC 3410, DOI 10.17487/ 3144 RFC3410, December 2002, . 3147 Authors' Addresses 3149 Zhaohui (Jeffrey) Zhang (editor) 3150 Juniper Networks, Inc. 3151 10 Technology Park Drive 3152 Westford, MA 01886 3153 USA 3155 Email: zzhang@juniper.net 3156 Saud Asif 3157 AT&T 3158 C5-3D30 200 South Laurel Avenue 3159 Middletown, NJ 07748 3160 USA 3162 Email: sasif@att.com 3164 Andy Green 3165 BT Design 21CN Converged Core IP & Data 3166 01473 629360 Adastral Park, Martlesham Heath, Ipswich IP5 3RE 3167 UK 3169 Email: andy.da.green@bt.com 3171 Sameer Gulrajani 3172 Cisco Systems 3173 Tasman Drive San Jose, CA 95134 3174 USA 3176 Email: sameerg@cisco.com 3178 Pradeep G. Jain 3179 Alcatel-Lucent Inc 3180 701 E Middlefield road Mountain view, CA 94043 3181 USA 3183 Email: pradeep.jain@alcatel-lucent.com 3185 Hiroshi Tsunoda (editor) 3186 Tohoku Institute of Technology 3187 35-1, Yagiyama Kasumi-cho, Taihaku-ku 3188 Sendai 982-8577 3189 Japan 3191 Phone: +81-22-305-3411 3192 Email: tsuno@m.ieice.org