idnits 2.17.1 draft-ietf-l3vpn-mvpn-mib-03.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 31 instances of too long lines in the document, the longest one being 10 characters in excess of 72. ** There is 1 instance of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (2013-08-29) is 3887 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: 'RFC2119' is mentioned on line 119, but not defined == Missing Reference: 'L3VPN-MIB' is mentioned on line 173, but not defined == Unused Reference: 'KEYWORDS' is defined on line 1251, but no explicit reference was found in the text == Unused Reference: 'RFC4382' is defined on line 1254, but no explicit reference was found in the text == Unused Reference: 'BGP-MVPN' is defined on line 1264, but no explicit reference was found in the text Summary: 2 errors (**), 0 flaws (~~), 7 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT Saud Asif 3 Intended Status: Proposed Standard AT&T 4 Expires: 2014-03-01 Andy Green 5 BT 6 Sameer Gulrajani 7 Cisco 8 Pradeep Jain 9 Alcatel-Lucent 10 Jeffrey Zhang 11 Juniper 12 2013-08-29 14 MPLS/BGP Layer 3 VPN Multicast 15 Management Information Base 17 draft-ietf-l3vpn-mvpn-mib-03 19 Abstract 21 This memo defines an portion of the Management Information Base (MIB) 22 for use with network management protocols in the Internet community. 24 In particular, it describes managed objects to configure and/or 25 monitor multicast in MPLS/BGP-based Layer-3 VPN (MVPN) on an MVPN 26 router. 28 Status of this Memo 30 This Internet-Draft is submitted to IETF 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), its areas, and its working groups. Note that 35 other groups may also distribute working documents as 36 Internet-Drafts. 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 The list of current Internet-Drafts can be accessed at 44 http://www.ietf.org/1id-abstracts.html 46 The list of Internet-Draft Shadow Directories can be accessed at 47 http://www.ietf.org/shadow.html 49 Copyright and License Notice 51 Copyright (c) 2013 IETF Trust and the persons identified as the 52 document authors. All rights reserved. 54 This document is subject to BCP 78 and the IETF Trust's Legal 55 Provisions Relating to IETF Documents 56 (http://trustee.ietf.org/license-info) in effect on the date of 57 publication of this document. Please review these documents 58 carefully, as they describe your rights and restrictions with respect 59 to this document. Code Components extracted from this document must 60 include Simplified BSD License text as described in Section 4.e of 61 the Trust Legal Provisions and are provided without warranty as 62 described in the Simplified BSD License. 64 Table of Contents 66 0 Draft history . . . . . . . . . . . . . . . . . . . . . . . . . 3 67 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 68 1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 69 2 MVPN MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 70 2.1 Summary of MIB Module . . . . . . . . . . . . . . . . . . . 4 71 2.2 MIB Module Definitions . . . . . . . . . . . . . . . . . . 5 72 3 Security Considerations . . . . . . . . . . . . . . . . . . . . 26 73 4 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 27 74 5 Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . 27 75 6 References . . . . . . . . . . . . . . . . . . . . . . . . . . 27 76 6.1 Normative References . . . . . . . . . . . . . . . . . . . 27 77 6.2 Informative References . . . . . . . . . . . . . . . . . . 27 78 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 27 80 0 Draft history 82 This draft is a first pass at a MIB document for [MVPN]. As such, it 83 should be considered as a early work. 85 Some aspects of BGP-MVPN (see definition below in "Introduction"), 86 such as exranet, may be specified in future revisions. 88 [note to author/reviewers: conformance groups to be added ] 90 [this section should be removed as soon as its stops being relevant] 92 1 Introduction 94 Multicast in MPLS/BGP L3 VPNs is specified in {[MVPN], [BGP-MVPN]}. 95 These specifications support either PIM or BGP as the protocol for 96 exchanging VPN multicast (referred to as C-multicast states, where 97 'C-' stands for 'VPN Customer-') among PEs. In the rest of this 98 document we'll use the term "PIM-MVPN" to refer to {[MVPN], [BGP- 99 MVPN]} with PIM being used for exchanging C-multicast states, and 100 "BGP-MVPN" to refer to {[MVPN], [BGP-MVPN]} with BGP is used for 101 exchanging C-multicast states. 103 This document defines a standard MIB for MVPN-specific objects that 104 are generic to both PIM-MVPN and BGP-MVPN. 106 This document borrowed some text from Cisco PIM-MVPN MIB [CISCO-MIB]. 107 For PIM-MVPN this document attempts to provide coverage comparable 108 to [CISCO-MIB], but in a generic way that applies to both PIM-MVPN 109 and BGP-MVPN. 111 Comments should be made directly to the Layer-3 VPN (L3VPN) WG at 112 l3vpn@ietf.org. 114 1.1 Terminology 116 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 117 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 118 document are to be interpreted as described in RFC 2119 [RFC2119]. 120 This document adopts the definitions, acronyms and mechanisms 121 described in [MVPN] and other documents that [MVPN] refers to. 122 Familiarity with Multicast, MPLS, L3VPN, MVPN concepts and/or 123 mechanisms is assumed. 125 Interchangeably, the term MVRF and MVPN are used to refer to a 126 partiular Multicast VPN instantiation on a particular PE device. 128 2 MVPN MIB 130 This MIB enables configuring and/or monitoring of MVPNs on PE 131 devices: the whole multicast VPN machinery and the per-MVRFs 132 information, including the configuration, status and operational 133 details, such as different PMSIs and the provider tunnels 134 implementing them. 136 2.1 Summary of MIB Module 138 The configuration and states specific to an MVPN include the 139 following: 141 - C-multicast routing exchange protocol (PIM or BGP) 143 - I-PMSI, S-PMSI and corresponding provider tunnels 145 - Mapping of c-multicast states to PMSI/tunnels 147 To represent them, the following tables are defined. 149 +--------------+ 150 | MvpnBgp | 151 | General | 152 +--------------+ +-------------------+ +-----------------+ 153 | MvpnGeneral | -> | MvpnPmsiConfig | <- | MvpnSpmsiConfig | 154 +--------------+ +-------------------+ +-----------------+ 156 +--------------+ +-------------------+ +-----------------+ 157 | MvpnIpmsi | -> | L2L3VpnMcastPmsi | <- | MvpnSpmsi | 158 +--------------+ | TunnelAttribute | +-----------------+ 159 -> +-------------------+ 160 / ^ 161 / | 162 +--------------+ +-------------------+ 163 | MvpnInterAs | | MvpnMroute | 164 | Ipmsi | +-------------------+ 165 +--------------+ 167 - mvpnGeneralTable/Entry 169 An entry in this table is created for every MVRF in the device, for 170 general configuration/states of the MVRF, including I-PMSI 171 configuration. 173 Existence of the corresponding VRF in [L3VPN-MIB] is necessary for 174 a row to exist in this table. 176 - mvpnBgpGeneralTable/Entry 178 This table augments mvpnGeneralTable and is for BGP-MVPN specific 179 information. 181 - mvpnSpmsiConfigTable/Entry 183 This table contains objects for S-PMSI configurations in an MVRF. 185 - mvpnPmsiConfigTable/Entry 187 Both I-PMSI configuration (in mvpnGeneralEntry) and S-PMSI 188 configuration (in mvpnSpmsiConfigEntry) refer to entries in this 189 table. 191 - mvpnIpmsiTable/Entry 193 This table contains all advertised or received intra-as I-PMSIs. 194 With PIM-MVPN, it is applicable only when BGP-Based Autodiscovery 195 of MVPN Membership is used. 197 - mvpnInterAsIpmsiTable/Entry 199 This table contains all advertised or received inter-as I-PMSIs. 200 With PIM-MVPN, it is applicable only when BGP-Based Autodiscovery 201 of MVPN Membership is used. 203 - mvpnSpmsiTable/Etnry 205 This table contains all advertised or received S-PMSIs. 207 - l2l3VpnMcastPmsiTunnelAttributeTable/Entry 209 This table is defined separately in l2L3VpnMcastMIB [L2L3MVPN-MIB], 210 which is common for both VPLS Multicast and MVPN. It contains 211 sent/received PMSI attribute entries referred to by mvpnIpmsiEntry, 212 mvpnSpmsiEntry, mvpnInterAsIpmsiEntry, and other MIB objects (e.g., 213 VPLS Multicast ones). 215 - mvpnMrouteTable/Entry 217 This table augments ipMcastMIB.ipMcast.ipMcastRouteTable, for some 218 MVPN specific information. 219 2.2 MIB Module Definitions 220 MCAST-VPN-MIB DEFINITIONS ::= BEGIN 222 IMPORTS 223 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 224 experimental, Unsigned32 225 FROM SNMPv2-SMI 227 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 228 FROM SNMPv2-CONF 230 TruthValue, RowPointer, RowStatus, TimeStamp, TimeInterval 231 FROM SNMPv2-TC 233 SnmpAdminString 234 FROM SNMP-FRAMEWORK-MIB 236 InetAddress, InetAddressType 237 FROM INET-ADDRESS-MIB 239 MplsLabel 240 FROM MPLS-TC-STD-MIB 242 mplsL3VpnVrfName, MplsL3VpnRouteDistinguisher 243 FROM MPLS-L3VPN-STD-MIB 245 ipMcastRouteEntry 246 FROM IPMCAST-MIB 248 L2L3VpnMcastProviderTunnelType 249 FROM L2L3-VPN-MCAST-MIB; 251 mvpnMIB MODULE-IDENTITY 252 LAST-UPDATED "201301071200Z" -- 07 January 2013 12:00:00 GMT 253 ORGANIZATION "IETF Layer-3 Virtual Private 254 Networks Working Group." 255 CONTACT-INFO 256 " Jeffrey (Zhaohui) Zhang 257 zzhang@juniper.net 259 Comments and discussion to l3vpn@ietf.org" 261 DESCRIPTION 262 "This MIB contains managed object definitions for 263 multicast in BGP/MPLS IP VPNs defined by [MVPN]. 264 Copyright (C) The Internet Society (2013)." 266 -- Revision history. 267 REVISION "201301071200Z" -- 07 January 2013 12:00:00 GMT 268 DESCRIPTION 269 "Initial version of the draft." 270 ::= { experimental 99 } -- number to be assigned 272 -- Top level components of this MIB. 273 mvpnNotifications OBJECT IDENTIFIER ::= { mvpnMIB 0 } 275 -- tables, scalars 276 mvpnObjects OBJECT IDENTIFIER ::= { mvpnMIB 1 } 278 mvpnScalars OBJECT IDENTIFIER ::= { mvpnObjects 1 } 279 mvpnGeneral OBJECT IDENTIFIER ::= { mvpnObjects 2 } 280 mvpnConfig OBJECT IDENTIFIER ::= { mvpnObjects 3 } 281 mvpnStates OBJECT IDENTIFIER ::= { mvpnObjects 4 } 283 -- Scalar Objects 285 mvpnMvrfNumber OBJECT-TYPE 286 SYNTAX Unsigned32 287 MAX-ACCESS read-only 288 STATUS current 289 DESCRIPTION 290 "The number of MVRFs for IPv4 or IPv6 or mLDP C-Multicast 291 that are present in this device." 292 ::= { mvpnScalars 1 } 294 mvpnMvrfNumberV4 OBJECT-TYPE 295 SYNTAX Unsigned32 296 MAX-ACCESS read-only 297 STATUS current 298 DESCRIPTION 299 "The number of MVRFs for IPv4 C-Multicast that are present 300 in this device." 301 ::= { mvpnScalars 2 } 303 mvpnMvrfNumberV6 OBJECT-TYPE 304 SYNTAX Unsigned32 305 MAX-ACCESS read-only 306 STATUS current 307 DESCRIPTION 308 "The number of MVRFs for IPv6 C-Multicast that are present 309 in this device." 310 ::= { mvpnScalars 3 } 312 mvpnMvrfNumberPimV4 OBJECT-TYPE 313 SYNTAX Unsigned32 314 MAX-ACCESS read-only 315 STATUS current 316 DESCRIPTION 317 "The number of PIM-MVPN MVRFs for IPv4 C-Multicast that are present 318 in this device." 319 ::= { mvpnScalars 4 } 321 mvpnMvrfNumberPimV6 OBJECT-TYPE 322 SYNTAX Unsigned32 323 MAX-ACCESS read-only 324 STATUS current 325 DESCRIPTION 326 "The number of PIM-MVPN MVRFs for IPv6 C-Multicast that are present 327 in this device." 328 ::= { mvpnScalars 5 } 330 mvpnMvrfNumberBgpV4 OBJECT-TYPE 331 SYNTAX Unsigned32 332 MAX-ACCESS read-only 333 STATUS current 334 DESCRIPTION 335 "The number of BGP-MVPN MVRFs for IPv4 C-Multicast that are present 336 in this device." 337 ::= { mvpnScalars 6 } 339 mvpnMvrfNumberBgpV6 OBJECT-TYPE 340 SYNTAX Unsigned32 341 MAX-ACCESS read-only 342 STATUS current 343 DESCRIPTION 344 "The number of BGP-MVPN MVRFs for IPv6 C-Multicast that are present 345 in this device." 346 ::= { mvpnScalars 7 } 348 mvpnMvrfNumberMldp OBJECT-TYPE 349 SYNTAX Unsigned32 350 MAX-ACCESS read-only 351 STATUS current 352 DESCRIPTION 353 "The number of BGP-MVPN MVRFs for mLDP C-Multicast that are present 354 in this device." 355 ::= { mvpnScalars 8 } 357 mvpnNotificationEnable OBJECT-TYPE 358 SYNTAX TruthValue 359 MAX-ACCESS read-write 360 STATUS current 361 DESCRIPTION 362 "If this object is TRUE, then the generation of all 363 notifications defined in this MIB is enabled." 365 DEFVAL { false } 366 ::= { mvpnScalars 9 } 368 -- General MVRF Information Table 370 mvpnGeneralTable OBJECT-TYPE 371 SYNTAX SEQUENCE OF MvpnGeneralEntry 372 MAX-ACCESS not-accessible 373 STATUS current 374 DESCRIPTION 375 "This table specifies the general information about the MVRFs 376 present in this device." 377 ::= { mvpnGeneral 1 } 379 mvpnGeneralEntry OBJECT-TYPE 380 SYNTAX MvpnGeneralEntry 381 MAX-ACCESS not-accessible 382 STATUS current 383 DESCRIPTION 384 "An entry in this table is created for every MVRF in the 385 device." 386 INDEX { mplsL3VpnVrfName } 387 ::= { mvpnGeneralTable 1 } 389 MvpnGeneralEntry ::= SEQUENCE { 390 mvpnGenOperStatusChange INTEGER, 391 mvpnGenOperChangeTime TimeStamp, 392 mvpnGenCmcastRouteProtocolV4 INTEGER, 393 mvpnGenCmcastRouteProtocolV6 INTEGER, 394 mvpnGenIpmsiConfigV4 RowPointer, 395 mvpnGenIpmsiConfigV6 RowPointer, 396 mvpnGenInterAsPmsiConfigV4 RowPointer, 397 mvpnGenInterAsPmsiConfigV6 RowPointer, 398 mvpnGenRowStatus RowStatus 399 } 401 mvpnGenOperStatusChange OBJECT-TYPE 402 SYNTAX INTEGER { createdMvrf(1), 403 deletedMvrf(2), 404 modifiedMvrfIpmsiConfig(3), 405 modifiedMvrfSpmsiConfig(4) 406 } 407 MAX-ACCESS read-only 408 STATUS current 409 DESCRIPTION 410 "This object describes the last operational change that 411 happened for the given MVRF. 413 createdMvrf - indicates that the MVRF was created in the 414 device. 416 deletedMvrf - indicates that the MVRF was deleted from the 417 device. A row in this table will never have 418 mvpnGenOperStatusChange equal to deletedMvrf(2), 419 because in that case the row itself will be deleted from the 420 table. This value for mvpnGenOperStatusChange is defined 421 mainly for use in mvpnMvrfChange notification. 423 modifiedMvrfIpmsiConfig - indicates that the I-PMSI 424 for the MVRF was configured, deleted or changed. 426 modifiedMvrfSpmsiConfig - indicates that the S-PMSI 427 for the MVRF was configured, deleted or changed." 428 DEFVAL { createdMvrf } 429 ::= { mvpnGeneralEntry 1 } 431 mvpnGenOperChangeTime OBJECT-TYPE 432 SYNTAX TimeStamp 433 MAX-ACCESS read-only 434 STATUS current 435 DESCRIPTION 436 "The time at which the last operational change for the MVRF in 437 question took place. The last operational change is specified 438 by mvpnGenOperStatusChange." 439 ::= { mvpnGeneralEntry 2 } 441 mvpnGenCmcastRouteProtocolV4 OBJECT-TYPE 442 SYNTAX INTEGER { pim (1), 443 bgp (2) 444 } 445 MAX-ACCESS read-write 446 STATUS current 447 DESCRIPTION 448 "Protocol used to signal IPv4 C-multicast states across the 449 provider core. 450 pim(1): PIM (PIM-MVPN). 451 bgp(2): BGP (BGP-MVPN)." 452 ::= { mvpnGeneralEntry 3 } 454 mvpnGenCmcastRouteProtocolV6 OBJECT-TYPE 455 SYNTAX INTEGER { pim (1), 456 bgp (2) 457 } 458 MAX-ACCESS read-write 459 STATUS current 460 DESCRIPTION 461 "Protocol used to signal IPv6 C-multicast states across the 462 provider core. 463 pim(1): PIM (PIM-MVPN). 464 bgp(2): BGP (BGP-MVPN)." 465 ::= { mvpnGeneralEntry 4 } 467 mvpnGenIpmsiConfigV4 OBJECT-TYPE 468 SYNTAX RowPointer 469 MAX-ACCESS read-write 470 STATUS current 471 DESCRIPTION 472 "This points to a row in mvpnPmsiConfigTable, 473 for I-PMSI configuration for IPv4." 474 ::= { mvpnGeneralEntry 5 } 476 mvpnGenIpmsiConfigV6 OBJECT-TYPE 477 SYNTAX RowPointer 478 MAX-ACCESS read-write 479 STATUS current 480 DESCRIPTION 481 "This points to a row in mvpnPmsiConfigTable, 482 for I-PMSI configuration for IPv6." 483 ::= { mvpnGeneralEntry 6 } 485 mvpnGenInterAsPmsiConfigV4 OBJECT-TYPE 486 SYNTAX RowPointer 487 MAX-ACCESS read-write 488 STATUS current 489 DESCRIPTION 490 "This points to a row in mvpnPmsiConfigTable, 491 for inter-as I-PMSI configuration for IPv4, in case of segmented 492 inter-as provider tunnels." 493 ::= { mvpnGeneralEntry 7 } 495 mvpnGenInterAsPmsiConfigV6 OBJECT-TYPE 496 SYNTAX RowPointer 497 MAX-ACCESS read-write 498 STATUS current 499 DESCRIPTION 500 "This points to a row in mvpnPmsiConfigTable, 501 for inter-as I-PMSI configuration for IPv6, in case of segmented 502 inter-as provider tunnels." 503 ::= { mvpnGeneralEntry 8 } 505 mvpnGenRowStatus OBJECT-TYPE 506 SYNTAX RowStatus 507 MAX-ACCESS read-create 508 STATUS current 509 DESCRIPTION 510 "This is used to create or delete a row in this table." 511 ::= { mvpnGeneralEntry 9 } 513 -- General BGP-MVPN table 515 mvpnBgpGeneralTable OBJECT-TYPE 516 SYNTAX SEQUENCE OF MvpnBgpGeneralEntry 517 MAX-ACCESS not-accessible 518 STATUS current 519 DESCRIPTION 520 "This table augments the mvpnGeneralTable and is for BGP-MVPN 521 specific information." 522 ::= { mvpnGeneral 2 } 524 mvpnBgpGeneralEntry OBJECT-TYPE 525 SYNTAX MvpnBgpGeneralEntry 526 MAX-ACCESS not-accessible 527 STATUS current 528 DESCRIPTION 529 "The mvpnBgpGeneralEntry matches and augments an mvpnGeneralEntry 530 for a BGP-MVPN instance, with BGP-MVPN specific informatoin." 531 AUGMENTS { mvpnGeneralEntry } 532 ::= { mvpnBgpGeneralTable 1 } 534 MvpnBgpGeneralEntry ::= SEQUENCE { 535 mvpnBgpGenMode INTEGER, 536 mvpnBgpGenUmhSelection INTEGER, 537 mvpnBgpGenSiteType INTEGER, 538 mvpnBgpGenCmcastImportRt MplsL3VpnRouteDistinguisher, 539 mvpnBgpGenSrcAs Unsigned32, 540 mvpnBgpGenSptnlLimit Unsigned32 541 } 543 mvpnBgpGenMode OBJECT-TYPE 544 SYNTAX INTEGER { 545 rpt-spt (1), 546 spt-only (2) 547 } 548 MAX-ACCESS read-write 549 STATUS current 550 DESCRIPTION 551 "For two different BGP-MVPN modes: 552 rpt-spt(1): intersite-site shared tree mode 553 spt-only(2): inter-site source-only tree mode." 554 ::= { mvpnBgpGeneralEntry 1} 556 mvpnBgpGenUmhSelection OBJECT-TYPE 557 SYNTAX INTEGER { 558 highest-pe-address (1), 559 c-root-group-hashing (2), 560 ucast-umh-route (3) 561 } 562 MAX-ACCESS read-write 563 STATUS current 564 DESCRIPTION 565 "The UMH selection method for this mvpn, as specified in section 566 5.1.3 of [MVPN]: 567 highest-pe-address (1): PE with the highest address 568 c-root-group-hashing (2): hashing based on (c-root, c-group) 569 uncast-umh-route (3): per ucast route towards c-root" 571 ::= { mvpnBgpGeneralEntry 2} 573 mvpnBgpGenSiteType OBJECT-TYPE 574 SYNTAX INTEGER { 575 sender-receiver (1), 576 receiver-only (2), 577 sender-only (3) 578 } 579 MAX-ACCESS read-write 580 STATUS current 581 DESCRIPTION 582 "Whether this site is a receiver-only site or not. 583 sender-receiver (1): both sender and receiver site. 584 receiver-only (2): receiver-only site. 585 sender-only (3): sender-only site." 586 ::= { mvpnBgpGeneralEntry 3} 588 mvpnBgpGenCmcastImportRt OBJECT-TYPE 589 SYNTAX MplsL3VpnRouteDistinguisher 590 MAX-ACCESS read-write 591 STATUS current 592 DESCRIPTION 593 "The C-multicast Import RT that this device adds to 594 unicast vpn routes that it advertises for this mvpn." 595 ::= { mvpnBgpGeneralEntry 4} 597 mvpnBgpGenSrcAs OBJECT-TYPE 598 SYNTAX Unsigned32 599 MAX-ACCESS read-only 600 STATUS current 601 DESCRIPTION 602 "The Source AS number in Source AS Extended Community that this device 603 adds to the unicast vpn routes that it advertises for this mvpn." 604 ::= { mvpnBgpGeneralEntry 5} 606 mvpnBgpGenSptnlLimit OBJECT-TYPE 607 SYNTAX Unsigned32 608 MAX-ACCESS read-write 609 STATUS current 610 DESCRIPTION 611 "The max number of selective provider tunnels this device allows 612 for this mvpn." 613 ::= { mvpnBgpGeneralEntry 6} 615 -- PMSI Configuration Table 617 mvpnPmsiConfigTable OBJECT-TYPE 618 SYNTAX SEQUENCE OF MvpnPmsiConfigEntry 619 MAX-ACCESS not-accessible 620 STATUS current 621 DESCRIPTION 622 "This table specifies the configured PMSIs." 623 ::= { mvpnConfig 1 } 625 mvpnPmsiConfigEntry OBJECT-TYPE 626 SYNTAX MvpnPmsiConfigEntry 627 MAX-ACCESS not-accessible 628 STATUS current 629 DESCRIPTION 630 "An entry in this table is created for each PMSI configured 631 on this router. It can be referred to by either I-PMSI 632 configuration (in mvpnGeneralEntry) or S-PMSI configuration 633 (in mvpnSpmsiConfigEntry)" 634 INDEX { mvpnPmsiConfigTunnelType, 635 mvpnPmsiConfigTunnelAuxInfo, 636 mvpnPmsiConfigTunnelPimGroupAddressType, 637 mvpnPmsiConfigTunnelPimGroupAddress, 638 mvpnPmsiConfigTunnelOrTemplateName } 639 ::= { mvpnPmsiConfigTable 1 } 641 MvpnPmsiConfigEntry ::= SEQUENCE { 642 mvpnPmsiConfigTunnelType L2L3VpnMcastProviderTunnelType, 643 mvpnPmsiConfigTunnelAuxInfo Unsigned32, 644 mvpnPmsiConfigTunnelPimGroupAddressType InetAddressType, 645 mvpnPmsiConfigTunnelPimGroupAddress InetAddress, 646 mvpnPmsiConfigTunnelOrTemplateName SnmpAdminString, 647 mvpnPmsiConfigEncapsType INTEGER, 648 mvpnPmsiConfigRowStatus RowStatus 649 } 651 mvpnPmsiConfigTunnelType OBJECT-TYPE 652 SYNTAX L2L3VpnMcastProviderTunnelType 653 MAX-ACCESS not-accessible 654 STATUS current 655 DESCRIPTION 656 "Type of tunnel used to instantiate the PMSI." 657 ::= { mvpnPmsiConfigEntry 1 } 659 mvpnPmsiConfigTunnelAuxInfo OBJECT-TYPE 660 SYNTAX Unsigned32 661 MAX-ACCESS not-accessible 662 STATUS current 663 DESCRIPTION 664 "Additional tunnel information depending on the type. 665 pim: In case of S-PMSI, number of groups starting at 666 mvpnPmsiConfigTunnelPimGroupAddress. 667 This allows a range of PIM provider tunnel 668 group addresses to be specified in S-PMSI case. 669 In I-PMSI case, it must be 1. 670 rsvp-p2mp: 1 for statically specified rsvp-p2mp tunnel 671 2 for dynamically created rsvp-p2mp tunnel 672 ingress-replication: 673 1 for using any existing p2p/mp2p lsp 674 2 for dynamically creating new p2p lsp" 675 ::= { mvpnPmsiConfigEntry 2 } 677 mvpnPmsiConfigTunnelPimGroupAddressType OBJECT-TYPE 678 SYNTAX InetAddressType 679 MAX-ACCESS not-accessible 680 STATUS current 681 DESCRIPTION 682 "In case of PIM provider tunnel, the type of tunnel address." 683 ::= { mvpnPmsiConfigEntry 3 } 685 mvpnPmsiConfigTunnelPimGroupAddress OBJECT-TYPE 686 SYNTAX InetAddress 687 MAX-ACCESS not-accessible 688 STATUS current 689 DESCRIPTION 690 "In case of PIM provider tunnel, the provider tunnel address." 691 ::= { mvpnPmsiConfigEntry 4 } 693 mvpnPmsiConfigTunnelOrTemplateName OBJECT-TYPE 694 SYNTAX SnmpAdminString 695 MAX-ACCESS not-accessible 696 STATUS current 697 DESCRIPTION 698 "The tunnel name or template name used to create tunnels. 699 Depending on mvpnPmsiConfigTunnelType and 700 mvpnPmsiConfigTunnelAuxInfo: 702 dynamically created rsvp-p2mp tunnel: template name 703 statically specified rsvp-p2mp tunnel: tunnel name 704 ingress-replication using 705 dynamically created lsps: template name 706 other: null" 707 ::= { mvpnPmsiConfigEntry 5 } 709 mvpnPmsiConfigEncapsType OBJECT-TYPE 710 SYNTAX INTEGER { greIp (1), 711 ipIp (2), 712 mpls (3) 713 } 714 MAX-ACCESS read-write 715 STATUS current 716 DESCRIPTION 717 "The encapsulation type to be used, in case of PIM tunnel or 718 ingress-replication." 719 ::= { mvpnPmsiConfigEntry 6 } 721 mvpnPmsiConfigRowStatus OBJECT-TYPE 722 SYNTAX RowStatus 723 MAX-ACCESS read-create 724 STATUS current 725 DESCRIPTION 726 "Used to create/modify/delete a row in this table." 727 ::= { mvpnPmsiConfigEntry 7 } 729 -- S-PMSI configuration table 731 mvpnSpmsiConfigTable OBJECT-TYPE 732 SYNTAX SEQUENCE OF MvpnSpmsiConfigEntry 733 MAX-ACCESS not-accessible 734 STATUS current 735 DESCRIPTION 736 "This table specifies S-PMSI configuration." 737 ::= { mvpnConfig 2 } 739 mvpnSpmsiConfigEntry OBJECT-TYPE 740 SYNTAX MvpnSpmsiConfigEntry 741 MAX-ACCESS not-accessible 742 STATUS current 743 DESCRIPTION 744 "An entry is created for each S-PMSI configuration." 745 INDEX { mplsL3VpnVrfName, 746 mvpnSpmsiConfigCmcastAddressType, 747 mvpnSpmsiConfigCmcastGroupAddress, 748 mvpnSpmsiConfigCmcastGroupPrefixLen, 749 mvpnSpmsiConfigCmcastSourceAddress, 750 mvpnSpmsiConfigCmcastSourcePrefixLen } 751 ::= { mvpnSpmsiConfigTable 1 } 753 MvpnSpmsiConfigEntry ::= SEQUENCE { 754 mvpnSpmsiConfigCmcastAddressType InetAddressType, 755 mvpnSpmsiConfigCmcastGroupAddress InetAddress, 756 mvpnSpmsiConfigCmcastGroupPrefixLen Unsigned32, 757 mvpnSpmsiConfigCmcastSourceAddress InetAddress, 758 mvpnSpmsiConfigCmcastSourcePrefixLen Unsigned32, 759 mvpnSpmsiConfigThreshold Unsigned32, 760 mvpnSpmsiConfigPmsiPointer RowPointer, 761 mvpnSpmsiConfigRowStatus RowStatus 762 } 764 mvpnSpmsiConfigCmcastAddressType OBJECT-TYPE 765 SYNTAX InetAddressType 766 MAX-ACCESS not-accessible 767 STATUS current 768 DESCRIPTION 769 "Type of C-multicast address" 770 ::= { mvpnSpmsiConfigEntry 1 } 772 mvpnSpmsiConfigCmcastGroupAddress OBJECT-TYPE 773 SYNTAX InetAddress 774 MAX-ACCESS not-accessible 775 STATUS current 776 DESCRIPTION 777 "C-multicast group address" 778 ::= { mvpnSpmsiConfigEntry 2 } 780 mvpnSpmsiConfigCmcastGroupPrefixLen OBJECT-TYPE 781 SYNTAX Unsigned32 782 MAX-ACCESS not-accessible 783 STATUS current 784 DESCRIPTION 785 "C-multicast group address prefix length. 786 A group 0 (or ::0) with prefix length 32 (or 128) 787 indicates wildcard group, while a group 0 (or ::0) 788 with prefix length 0 indicates any group." 789 ::= { mvpnSpmsiConfigEntry 3 } 791 mvpnSpmsiConfigCmcastSourceAddress OBJECT-TYPE 792 SYNTAX InetAddress 793 MAX-ACCESS not-accessible 794 STATUS current 795 DESCRIPTION 796 "C-multicast source address" 797 ::= { mvpnSpmsiConfigEntry 4 } 799 mvpnSpmsiConfigCmcastSourcePrefixLen OBJECT-TYPE 800 SYNTAX Unsigned32 801 MAX-ACCESS not-accessible 802 STATUS current 803 DESCRIPTION 804 "C-multicast source address prefix length. 805 A source 0 (or ::0) with prefix length 32 (or 128) 806 indicates a wildcard source, while a source 0 (or ::0) 807 with prefix length 0 indicates any source." 808 ::= { mvpnSpmsiConfigEntry 5 } 810 mvpnSpmsiConfigThreshold OBJECT-TYPE 811 SYNTAX Unsigned32 (0..4294967295) 812 UNITS "kilobits per second" 813 MAX-ACCESS read-write 814 STATUS current 815 DESCRIPTION 816 "The bandwidth threshold value which when exceeded for a 817 multicast routing entry in the given MVRF, triggers usage 818 of S-PMSI." 819 ::= { mvpnSpmsiConfigEntry 6 } 821 mvpnSpmsiConfigPmsiPointer OBJECT-TYPE 822 SYNTAX RowPointer 823 MAX-ACCESS read-write 824 STATUS current 825 DESCRIPTION 826 "This points to a row in mvpnPmsiConfigTable, 827 to specify tunnel attributes." 828 ::= { mvpnSpmsiConfigEntry 7 } 830 mvpnSpmsiConfigRowStatus OBJECT-TYPE 831 SYNTAX RowStatus 832 MAX-ACCESS read-create 833 STATUS current 834 DESCRIPTION 835 "Used to create/modify/delete a row in this table." 836 ::= { mvpnSpmsiConfigEntry 8 } 838 -- Table of intra-as I-PMSIs advertised/received 840 mvpnIpmsiTable OBJECT-TYPE 841 SYNTAX SEQUENCE OF MvpnIpmsiEntry 842 MAX-ACCESS not-accessible 843 STATUS current 844 DESCRIPTION 845 "This table is for all advertised/received I-PMSI 846 advertisements." 848 ::= { mvpnStates 1 } 850 mvpnIpmsiEntry OBJECT-TYPE 851 SYNTAX MvpnIpmsiEntry 852 MAX-ACCESS not-accessible 853 STATUS current 854 DESCRIPTION 855 "An entry in this table corresponds to an I-PMSI 856 advertisement that is advertised/received on this router. 857 This represents all the sender PEs in the MVPN, 858 with the provider tunnel they use to send traffic." 859 INDEX { mplsL3VpnVrfName, 860 mvpnIpmsiAfi, 861 mvpnIpmsiRD, 862 mvpnIpmsiOrigAddrType, 863 mvpnIpmsiOrigAddress } 864 ::= { mvpnIpmsiTable 1 } 866 MvpnIpmsiEntry ::= SEQUENCE { 867 mvpnIpmsiAfi Unsigned32, 868 mvpnIpmsiRD MplsL3VpnRouteDistinguisher, 869 mvpnIpmsiOrigAddrType InetAddressType, 870 mvpnIpmsiOrigAddress InetAddress, 871 mvpnIpmsiUpTime TimeInterval, 872 mvpnIpmsiAttribute RowPointer 873 } 875 mvpnIpmsiAfi OBJECT-TYPE 876 SYNTAX Unsigned32 (1|2) 877 MAX-ACCESS not-accessible 878 STATUS current 879 DESCRIPTION 880 "The address family this I-PMSI is for. 881 1 - IPv4 882 2 - IPv6" 883 ::= { mvpnIpmsiEntry 1 } 885 mvpnIpmsiRD OBJECT-TYPE 886 SYNTAX MplsL3VpnRouteDistinguisher 887 MAX-ACCESS not-accessible 888 STATUS current 889 DESCRIPTION 890 "The Route Distinguisher in this I-PMSI." 891 ::= { mvpnIpmsiEntry 2 } 893 mvpnIpmsiOrigAddrType OBJECT-TYPE 894 SYNTAX InetAddressType 895 MAX-ACCESS not-accessible 896 STATUS current 897 DESCRIPTION 898 "The Internet address type of mvpnIpmsiOrigAddress." 899 ::= { mvpnIpmsiEntry 3 } 901 mvpnIpmsiOrigAddress OBJECT-TYPE 902 SYNTAX InetAddress 903 MAX-ACCESS not-accessible 904 STATUS current 905 DESCRIPTION 906 "The BGP address of the device that originated the I-PMSI." 907 ::= { mvpnIpmsiEntry 4 } 909 mvpnIpmsiUpTime OBJECT-TYPE 910 SYNTAX TimeInterval 911 MAX-ACCESS read-only 912 STATUS current 913 DESCRIPTION 914 "The time since this I-PMSI 915 was first advertised/received by the device." 916 ::= { mvpnIpmsiEntry 5 } 918 mvpnIpmsiAttribute OBJECT-TYPE 919 SYNTAX RowPointer 920 MAX-ACCESS read-only 921 STATUS current 922 DESCRIPTION 923 "Points to a row in the l2L3VpnMcastPmsiTunnelAttributeTable." 924 ::= { mvpnIpmsiEntry 6 } 926 -- Table of inter-as I-PMSIs advertised/received 928 mvpnInterAsIpmsiTable OBJECT-TYPE 929 SYNTAX SEQUENCE OF MvpnInterAsIpmsiEntry 930 MAX-ACCESS not-accessible 931 STATUS current 932 DESCRIPTION 933 "This table is for all advertised/received inter-as I-PMSI 934 advertisements." 935 ::= { mvpnStates 2 } 937 mvpnInterAsIpmsiEntry OBJECT-TYPE 938 SYNTAX MvpnInterAsIpmsiEntry 939 MAX-ACCESS not-accessible 940 STATUS current 941 DESCRIPTION 942 "An entry in this table corresponds to an inter-as I-PMSI 943 advertisement that is advertised/received on this router. 945 This represents all the ASes in the MVPN, 946 with the provider tunnel used to send traffic to." 947 INDEX { mplsL3VpnVrfName, 948 mvpnInterAsIpmsiAfi, 949 mvpnInterAsIpmsiRD, 950 mvpnInterAsIpmsiSrcAs } 951 ::= { mvpnInterAsIpmsiTable 1 } 953 MvpnInterAsIpmsiEntry ::= SEQUENCE { 954 mvpnInterAsIpmsiAfi Unsigned32, 955 mvpnInterAsIpmsiRD MplsL3VpnRouteDistinguisher, 956 mvpnInterAsIpmsiSrcAs Unsigned32, 957 mvpnInterAsIpmsiAttribute RowPointer 958 } 960 mvpnInterAsIpmsiAfi OBJECT-TYPE 961 SYNTAX Unsigned32 (1|2) 962 MAX-ACCESS not-accessible 963 STATUS current 964 DESCRIPTION 965 "The address family this I-PMSI is for. 966 1 - IPv4 967 2 - IPv6" 968 ::= { mvpnInterAsIpmsiEntry 1 } 970 mvpnInterAsIpmsiRD OBJECT-TYPE 971 SYNTAX MplsL3VpnRouteDistinguisher 972 MAX-ACCESS not-accessible 973 STATUS current 974 DESCRIPTION 975 "The Route Distinguisher in this inter-as I-PMSI." 976 ::= { mvpnInterAsIpmsiEntry 2 } 978 mvpnInterAsIpmsiSrcAs OBJECT-TYPE 979 SYNTAX Unsigned32 980 MAX-ACCESS not-accessible 981 STATUS current 982 DESCRIPTION 983 "The source-as in this inter-as I-PMSI." 984 ::= { mvpnInterAsIpmsiEntry 3 } 986 mvpnInterAsIpmsiAttribute OBJECT-TYPE 987 SYNTAX RowPointer 988 MAX-ACCESS read-only 989 STATUS current 990 DESCRIPTION 991 "Points to a row in the l2L3VpnMcastPmsiTunnelAttributeTable." 992 ::= { mvpnInterAsIpmsiEntry 4 } 994 -- Table of S-PMSIs advertised/received 996 mvpnSpmsiTable OBJECT-TYPE 997 SYNTAX SEQUENCE OF MvpnSpmsiEntry 998 MAX-ACCESS not-accessible 999 STATUS current 1000 DESCRIPTION 1001 "This table has information about the S-PMSIs sent/received 1002 by a device." 1003 ::= { mvpnStates 3 } 1005 mvpnSpmsiEntry OBJECT-TYPE 1006 SYNTAX MvpnSpmsiEntry 1007 MAX-ACCESS not-accessible 1008 STATUS current 1009 DESCRIPTION 1010 "An entry in this table is created or updated for every S-PMSI 1011 advertised/received in a particular MVRF." 1012 INDEX { mplsL3VpnVrfName, 1013 mvpnSpmsiCmcastAddrType, 1014 mvpnSpmsiCmcastGroup, 1015 mvpnSpmsiCmcastGroupPrefixLen, 1016 mvpnSpmsiCmcastSource, 1017 mvpnSpmsiCmcastSourcePrefixLen, 1018 mvpnSpmsiOrigAddrType, 1019 mvpnSpmsiOrigAddress} 1020 ::= { mvpnSpmsiTable 1 } 1022 MvpnSpmsiEntry ::= SEQUENCE { 1023 mvpnSpmsiCmcastAddrType InetAddressType, 1024 mvpnSpmsiCmcastGroup InetAddress, 1025 mvpnSpmsiCmcastGroupPrefixLen Unsigned32, 1026 mvpnSpmsiCmcastSource InetAddress, 1027 mvpnSpmsiCmcastSourcePrefixLen Unsigned32, 1028 mvpnSpmsiOrigAddrType InetAddressType, 1029 mvpnSpmsiOrigAddress InetAddress, 1030 mvpnSpmsiTunnelAttribute RowPointer, 1031 mvpnSpmsiUpTime TimeInterval, 1032 mvpnSpmsiExpTime TimeInterval, 1033 mvpnSpmsiRefCnt Unsigned32 1034 } 1036 mvpnSpmsiCmcastAddrType OBJECT-TYPE 1037 SYNTAX InetAddressType 1038 MAX-ACCESS not-accessible 1039 STATUS current 1040 DESCRIPTION 1041 "The Internet address type of mvpnSpmsiCmcastGroup/Source." 1043 ::= { mvpnSpmsiEntry 1 } 1045 mvpnSpmsiCmcastGroup OBJECT-TYPE 1046 SYNTAX InetAddress 1047 MAX-ACCESS not-accessible 1048 STATUS current 1049 DESCRIPTION 1050 "S-PMSI C-multicast group address. 1051 If it is 0 (or ::0), this is a wildcard group, 1052 and mvpnSpmsiCmcastGroupPrefixLen must be 32 (or 128)." 1053 ::= { mvpnSpmsiEntry 2 } 1055 mvpnSpmsiCmcastGroupPrefixLen OBJECT-TYPE 1056 SYNTAX Unsigned32 1057 MAX-ACCESS not-accessible 1058 STATUS current 1059 DESCRIPTION 1060 "S-PMSI C-multicast group address prefix length." 1061 ::= { mvpnSpmsiEntry 3 } 1063 mvpnSpmsiCmcastSource OBJECT-TYPE 1064 SYNTAX InetAddress 1065 MAX-ACCESS not-accessible 1066 STATUS current 1067 DESCRIPTION 1068 "S-PMSI C-multicast source address 1069 If it is 0 (or ::0), this is a wildcard source, 1070 and mvpnSpmsiCmcastSourcePrefixLen must be 32 (or 128)." 1071 ::= { mvpnSpmsiEntry 4 } 1073 mvpnSpmsiCmcastSourcePrefixLen OBJECT-TYPE 1074 SYNTAX Unsigned32 1075 MAX-ACCESS not-accessible 1076 STATUS current 1077 DESCRIPTION 1078 "S-PMSI C-multicast source address prefix length." 1079 ::= { mvpnSpmsiEntry 5 } 1081 mvpnSpmsiOrigAddrType OBJECT-TYPE 1082 SYNTAX InetAddressType 1083 MAX-ACCESS not-accessible 1084 STATUS current 1085 DESCRIPTION 1086 "The Internet address type of mvpnSpmsiOrigAddress." 1087 ::= { mvpnSpmsiEntry 6 } 1089 mvpnSpmsiOrigAddress OBJECT-TYPE 1090 SYNTAX InetAddress 1091 MAX-ACCESS not-accessible 1092 STATUS current 1093 DESCRIPTION 1094 "The BGP address of the device that originated the S-PMSI." 1095 ::= { mvpnSpmsiEntry 7 } 1097 mvpnSpmsiTunnelAttribute OBJECT-TYPE 1098 SYNTAX RowPointer 1099 MAX-ACCESS read-only 1100 STATUS current 1101 DESCRIPTION 1102 "A row pointer to the l2L3VpnMcastPmsiTunnelAttributeTable" 1103 ::= { mvpnSpmsiEntry 8 } 1105 mvpnSpmsiUpTime OBJECT-TYPE 1106 SYNTAX TimeInterval 1107 MAX-ACCESS read-only 1108 STATUS current 1109 DESCRIPTION 1110 "The time since this S-PMSI 1111 was first advertised/received by the device." 1112 ::= { mvpnSpmsiEntry 9 } 1114 mvpnSpmsiExpTime OBJECT-TYPE 1115 SYNTAX TimeInterval 1116 MAX-ACCESS read-only 1117 STATUS current 1118 DESCRIPTION 1119 "For UDP-based S-PMSI signaling for PIM-MVPN, 1120 the amount of time remaining before this 1121 received S-PMSI Join Message expires, 1122 or the next S-PMSI Join Message refresh is to be 1123 advertised again from the device. 1124 Otherwise, it is 0." 1125 ::= { mvpnSpmsiEntry 10 } 1127 mvpnSpmsiRefCnt OBJECT-TYPE 1128 SYNTAX Unsigned32 1129 MAX-ACCESS read-only 1130 STATUS current 1131 DESCRIPTION 1132 "The number of c-multicast routes that are mapped to 1133 this S-PMSI." 1134 ::= { mvpnSpmsiEntry 11 } 1136 -- Table of multicast routes in an MVPN 1138 mvpnMrouteTable OBJECT-TYPE 1139 SYNTAX SEQUENCE OF MvpnMrouteEntry 1140 MAX-ACCESS not-accessible 1141 STATUS current 1142 DESCRIPTION 1143 "This table augments ipMcastRouteTable, to provide some MVPN 1144 specific information." 1145 ::= { mvpnStates 4 } 1147 mvpnMrouteEntry OBJECT-TYPE 1148 SYNTAX MvpnMrouteEntry 1149 MAX-ACCESS not-accessible 1150 STATUS current 1151 DESCRIPTION 1152 "The mvpnMrouteEntry matches and augments an ipMcastRouteEntry, 1153 with MVPN specific information, such as PMSI used." 1154 AUGMENTS { ipMcastRouteEntry } 1155 ::= { mvpnMrouteTable 1 } 1157 MvpnMrouteEntry ::= SEQUENCE { 1158 mvpnMroutePmsiPointer RowPointer, 1159 mvpnMrouteNumberOfLocalReplication Unsigned32, 1160 mvpnMrouteNumberOfRemoteReplication Unsigned32, 1161 mvpnMrouteDataRate Unsigned32 1162 } 1164 mvpnMroutePmsiPointer OBJECT-TYPE 1165 SYNTAX RowPointer 1166 MAX-ACCESS read-only 1167 STATUS current 1168 DESCRIPTION 1169 "The I-PMSI or S-PMSI this C-multicast route is using. 1170 This is important because an implementation may not have an 1171 interface corresponding to a provider tunnel, 1172 that can be used in ipMcastRouteNextHopEntry." 1173 ::= { mvpnMrouteEntry 1 } 1175 mvpnMrouteNumberOfLocalReplication OBJECT-TYPE 1176 SYNTAX Unsigned32 1177 MAX-ACCESS read-only 1178 STATUS current 1179 DESCRIPTION 1180 "Number of replications to local receivers." 1181 ::= { mvpnMrouteEntry 2 } 1183 mvpnMrouteNumberOfRemoteReplication OBJECT-TYPE 1184 SYNTAX Unsigned32 1185 MAX-ACCESS read-only 1186 STATUS current 1187 DESCRIPTION 1188 "Number of (local) replications to remote receivers." 1189 ::= { mvpnMrouteEntry 3 } 1191 mvpnMrouteDataRate OBJECT-TYPE 1192 SYNTAX Unsigned32 (0..4294967295) 1193 UNITS "kilobits per second" 1194 MAX-ACCESS read-only 1195 STATUS current 1196 DESCRIPTION 1197 "The data rate for traffic following this route." 1198 ::= { mvpnMrouteEntry 4 } 1200 -- MVPN Notifications 1202 mvpnMvrfChange NOTIFICATION-TYPE 1203 OBJECTS { 1204 mvpnGenOperStatusChange 1205 } 1206 STATUS current 1207 DESCRIPTION 1208 "A mvpnMvrfChange notification signifies a change about 1209 a MVRF in the device. The change event can be creation of 1210 the MVRF, deletion of the MVRF or an update on the I-PMSI 1211 or S-PMSI configuration of the MVRF. The change event 1212 is indicated by mvpnGenOperStatusChange embedded in 1213 the notification. The user can then query 1214 mvpnGeneralTable, and/or mvpnSpmsiConfigTable to 1215 get the details of the change as necessary. 1217 Note: Since the creation of a MVRF is often followed by 1218 configuration of I-PMSI and/or S-PMSIs for the MVRF, 1219 more than one (three at most) notifications for a MVRF may 1220 be generated serially, and it is really not necessary to 1221 generate all three of them. An agent may choose to generate a 1222 notification for the last event only, that is for S-PMSI 1223 configuration. 1225 Similarly, deletion of I-PMSI and S-PMSI configuration on a 1226 MVRF happens before a MVRF is deleted and it is recommended 1227 that the agent send the notification for MVRF deletion 1228 event only." 1229 ::= { mvpnNotifications 2 } 1230 END 1232 3 Security Considerations 1234 1236 4 IANA Considerations 1238 1240 5 Acknowledgement 1242 Some of the text has been taken almost verbatim from [CISCO-MIB]. 1244 We would like to thank Yakov Rekhter, Jeffrey Haas, Huajin Jeng, 1245 Durga Prasad Velamuri for their helpful comments. 1247 6 References 1249 6.1 Normative References 1251 [KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate 1252 Requirement Levels", BCP 14, RFC 2119, March 1997. 1254 [RFC4382] Nadeau, T., Ed., and H. van der Linde, Ed., "MPLS/BGP 1255 Layer 3 Virtual Private Network (VPN) Management 1256 Information Base", RFC 4382, February 2006. 1258 [MROUTE-MIB]McWalter, D., Thaler, D., and A. Kessler, "IP Multicast 1259 MIB", RFC 5132, December 2007. 1261 [MVPN] Eric C. Rosen, Rahul Aggarwal, et. al., Multicast in MPLS/BGP 1262 IP VPNs, RFC 6513. 1264 [BGP-MVPN] R. Aggarwal, E. Rosen, T. Morin, Y. Rekhter, BGP Encodings 1265 and Procedures for Multicast in MPLS/BGP IP VPNs, RFC 1266 6514. 1268 [L2L3MVPN-MIB] Zhang, J., L2L3 VPN Multicast MIB, draft-zzhang-l2l3- 1269 vpn-mcast-mib, Work In Progress. 1271 6.2 Informative References 1273 [CISCO-MIB] Susheela Vaidya, Thomas D. Nadeau, Harmen Van der Linde, 1274 Multicast in BGP/MPLS IP VPNs Management Information Base, 1275 draft-svaidya-mcast-vpn-mib-02.txt, Work In Progress, 1276 April 2005. 1278 Authors' Addresses 1280 Saud Asif 1281 AT&T 1282 C5-3D30 1283 200 South Laurel Avenue 1284 Middletown, NJ 07748 1285 USA 1286 Email: sasif@att.com 1288 Andy Green 1289 BT Design 21CN Converged Core IP & Data 1290 01473 629360 1291 Adastral Park, Martlesham Heath, Ipswich IP5 3RE 1292 UK 1293 Email: andy.da.green@bt.com 1295 Sameer Gulrajani 1296 Cisco Systems 1297 Tasman Drive 1298 San Jose, CA 95134 1299 USA 1301 EMail: sameerg@cisco.com 1303 Pradeep G. Jain 1304 Alcatel-Lucent Inc 1305 701 E Middlefield road 1306 Mountain view, CA 94043 1307 USA 1308 Email: pradeep.jain@alcatel-lucent.com 1310 Jeffrey (Zhaohui) Zhang 1311 Juniper Networks, Inc. 1312 10 Technology Park Drive 1313 Westford, MA 01886 1314 USA 1315 Email: zzhang@juniper.net