idnits 2.17.1 draft-ietf-l3vpn-mvpn-mib-00.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 58 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 date (2012-05-07) is 4362 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 == Missing Reference: 'MVPN-BGP' is mentioned on line 775, but not defined == Missing Reference: 'RFC4875' is mentioned on line 886, but not defined == Missing Reference: 'RFC4607' is mentioned on line 902, but not defined == Unused Reference: 'KEYWORDS' is defined on line 1315, but no explicit reference was found in the text == Unused Reference: 'RFC4382' is defined on line 1318, but no explicit reference was found in the text Summary: 1 error (**), 0 flaws (~~), 8 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: 2012-11-07 Andy Green 5 BT 6 Sameer Gulrajani 7 Cisco 8 Pradeep Jain 9 Alcatel-Lucent 10 Jeffrey Zhang 11 Juniper 12 2012-05-07 14 MPLS/BGP Layer 3 VPN Multicast 15 Management Information Base 17 draft-ietf-l3vpn-mvpn-mib-00 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) 2012 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 . . . . . . . . . . . . . . . . . . . . . . . . . 4 67 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 68 1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 4 69 2 MVPN MIB . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 70 2.1 Summary of MIB Module . . . . . . . . . . . . . . . . . . . 5 71 2.2 MIB Module Definitions . . . . . . . . . . . . . . . . . . 6 72 3 Security Considerations . . . . . . . . . . . . . . . . . . . . 29 73 4 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 29 74 5 Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . 29 75 6 References . . . . . . . . . . . . . . . . . . . . . . . . . . 29 76 6.1 Normative References . . . . . . . . . . . . . . . . . . . 29 77 6.2 Informative References . . . . . . . . . . . . . . . . . . 30 78 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 30 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 | -> | MvpnPmsiTunnel | <- | MvpnSpmsi | 158 +--------------+ | Attribute | +-----------------+ 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 - mvpnPmsiTunnelAttributeTable/Entry 209 This table contains sent/received PMSI attribute entries referred 210 to by mvpnIpmsiEntry and mvpnSpmsiEntry. 212 - mvpnMrouteTable/Entry 214 This table augments 215 ipMRouteStdMIB.ipMRouteMIBObject.ipMRoute.ipMRouteTable, to 216 indicate which PMSI a particular ipMRoute maps to. 218 2.2 MIB Module Definitions 219 MCAST-VPN-MIB DEFINITIONS ::= BEGIN 221 IMPORTS 222 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 223 experimental, Unsigned32 224 FROM SNMPv2-SMI 226 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 227 FROM SNMPv2-CONF 229 TruthValue, RowPointer, RowStatus, TimeStamp, TimeInterval 230 FROM SNMPv2-TC 232 SnmpAdminString 233 FROM SNMP-FRAMEWORK-MIB 235 InetAddress, InetAddressType 236 FROM INET-ADDRESS-MIB 238 MplsLabel, 239 FROM MPLS-TC-STD-MIB 241 mplsVpnVrfName, MplsVpnRouteDistinguisher 242 FROM MPLS-L3VPN-MIB; 244 mvpnMIB MODULE-IDENTITY 245 LAST-UPDATED "201203011200Z" -- 01 March 2012 12:00:00 GMT 246 ORGANIZATION "IETF Layer-3 Virtual Private 247 Networks Working Group." 248 CONTACT-INFO 249 " Jeffrey (Zhaohui) Zhang 250 zzhang@juniper.net 252 Comments and discussion to l3vpn@ietf.org" 254 DESCRIPTION 255 "This MIB contains managed object definitions for 256 multicast in BGP/MPLS IP VPNs defined by [MVPN]. 257 Copyright (C) The Internet Society (2012)." 259 -- Revision history. 260 REVISION "201203011200Z" -- 01 March 2012 12:00:00 GMT 261 DESCRIPTION 262 "Initial version of the draft." 263 ::= { mvpnExperiment 1 } -- number to be assigned 265 -- Top level components of this MIB. 266 mvpnNotifications OBJECT IDENTIFIER ::= { mvpnMIB 0 } 267 -- tables, scalars 268 mvpnObjects OBJECT IDENTIFIER ::= { mvpnMIB 1 } 270 -- conformance 271 -- mvpnConformance OBJECT IDENTIFIER ::= { mvpnMIB 2 } 273 mvpnScalars OBJECT IDENTIFIER ::= { mvpnObjects 1 } 274 mvpnGeneral OBJECT IDENTIFIER ::= { mvpnObjects 2 } 275 mvpnConfig OBJECT IDENTIFIER ::= { mvpnObjects 3 } 276 mvpnStates OBJECT IDENTIFIER ::= { mvpnObjects 4 } 278 -- Scalar Objects 280 mvpnMvrfNumber OBJECT-TYPE 281 SYNTAX Unsigned32 282 MAX-ACCESS read-only 283 STATUS current 284 DESCRIPTION 285 "The number of MVRFs that are present in this device." 286 ::= { mvpnScalars 1 } 288 mvpnMvrfNumberPim OBJECT-TYPE 289 SYNTAX Unsigned32 290 MAX-ACCESS read-only 291 STATUS current 292 DESCRIPTION 293 "The number of PIM-MVPN MVRFs that are present in this device." 294 ::= { mvpnScalars 2 } 296 mvpnMvrfNumberBgp OBJECT-TYPE 297 SYNTAX Unsigned32 298 MAX-ACCESS read-only 299 STATUS current 300 DESCRIPTION 301 "The number of BGP-MVPN MVRFs that are present in this device." 302 ::= { mvpnScalars 3 } 304 mvpnNotificationEnable OBJECT-TYPE 305 SYNTAX TruthValue 306 MAX-ACCESS read-write 307 STATUS current 308 DESCRIPTION 309 "If this object is TRUE, then the generation of all 310 notifications defined in this MIB is enabled." 311 DEFVAL { false } 312 ::= { mvpnScalars 4 } 314 -- General MVRF Information Table 315 mvpnGeneralTable OBJECT-TYPE 316 SYNTAX SEQUENCE OF MvpnGeneralEntry 317 MAX-ACCESS not-accessible 318 STATUS current 319 DESCRIPTION 320 "This table specifies the general information about the MVRFs 321 present in this device." 322 ::= { mvpnGeneral 1 } 324 mvpnGeneralEntry OBJECT-TYPE 325 SYNTAX MvpnGeneralEntry 326 MAX-ACCESS not-accessible 327 STATUS current 328 DESCRIPTION 329 "An entry in this table is created for every MVRF in the 330 device." 331 INDEX { mplsVpnVrfName } 332 ::= { mvpnGeneralTable 1 } 334 MvpnGeneralEntry ::= SEQUENCE { 335 mvpnGenOperStatusChange INTEGER, 336 mvpnGenOperChangeTime TimeStamp, 337 mvpnGenCmcastRouteProtocol INTEGER, 338 mvpnGenIpmsiConfig RowPointer, 339 mvpnGenInterasPmsiConfig RowPointer, 340 mvpnGenRowStatus RowStatus 341 } 343 mvpnGenOperStatusChange OBJECT-TYPE 344 SYNTAX INTEGER { createdMvrf(1), 345 deletedMvrf(2), 346 modifiedMvrfIpmsiConfig(3), 347 modifiedMvrfSpmsiConfig(4) 348 } 349 MAX-ACCESS read-only 350 STATUS current 351 DESCRIPTION 352 "This object describes the last operational change that 353 happened for the given MVRF. 355 createdMvrf - indicates that the MVRF was created in the 356 device. 358 deletedMvrf - indicates that the MVRF was deleted from the 359 device. A row in this table will never have 360 mvpnGenOperStatusChange equal to deletedMvrf(2), 361 because in that case the row itself will be deleted from the 362 table. This value for mvpnGenOperStatusChange is defined 363 mainly for use in mvpnMvrfChange notification. 365 modifiedMvrfIpmsiConfig - indicates that the I-PMSI 366 for the MVRF was configured, deleted or changed. 368 modifiedMvrfSpmsiConfig - indicates that the S-PMSI 369 for the MVRF was configured, deleted or changed." 370 DEFVAL { createdMvrf } 371 ::= { mvpnGeneralEntry 1 } 373 mvpnGenOperChangeTime OBJECT-TYPE 374 SYNTAX TimeStamp 375 MAX-ACCESS read-only 376 STATUS current 377 DESCRIPTION 378 "The time at which the last operational change for the MVRF in 379 question took place. The last operational change is specified 380 by mvpnGenOperStatusChange." 381 ::= { mvpnGeneralEntry 2 } 383 mvpnGenCmcastRouteProtocol OBJECT-TYPE 384 SYNTAX INTEGER { pim (1), 385 bgp (2) 386 } 387 MAX-ACCESS read-write 388 STATUS current 389 DESCRIPTION 390 "Protocol used to signal C-multicast states across the 391 provider core. 392 pim(1): PIM (PIM-MVPN). 393 bgp(2): BGP (BGP-MVPN)." 394 ::= { mvpnGeneralEntry 3 } 396 mvpnGenIpmsiConfig OBJECT-TYPE 397 SYNTAX RowPointer 398 MAX-ACCESS read-create 399 STATUS current 400 DESCRIPTION 401 "This points to a row in mvpnPmsiConfigTable, 402 for I-PMSI configuration." 403 ::= { mvpnGeneralEntry 4 } 405 mvpnGenInterasPmsiConfig OBJECT-TYPE 406 SYNTAX RowPointer 407 MAX-ACCESS read-create 408 STATUS current 409 DESCRIPTION 410 "This points to a row in mvpnPmsiConfigTable, 411 for inter-as I-PMSI configuration in case of segmented 412 inter-as provider tunnels." 413 ::= { mvpnGeneralEntry 5 } 415 mvpnGenRowStatus OBJECT-TYPE 416 SYNTAX RowStatus 417 MAX-ACCESS read-create 418 STATUS current 419 DESCRIPTION 420 "This is used to create or delete a row in this table." 421 ::= { mvpnGeneralEntry 6 } 423 -- General BGP-MVPN table 425 mvpnBgpGeneralTable OBJECT-TYPE 426 SYNTAX SEQUENCE OF MvpnBgpGeneralEntry 427 MAX-ACCESS not-accessible 428 STATUS current 429 DESCRIPTION 430 "This table augments the mvpnGeneralTable and is for BGP-MVPN 431 specific information." 432 ::= { mvpnGeneral 2 } 434 mvpnBgpGeneralEntry OBJECT-TYPE 435 SYNTAX MvpnBgpGeneralEntry 436 MAX-ACCESS not-accessible 437 STATUS current 438 DESCRIPTION 439 "The mvpnBgpGeneralEntry matches and augments an mvpnGeneralEntry 440 for a BGP-MVPN instance, with BGP-MVPN specific informatoin." 441 AUGMENTS { mvpnGeneralEntry } 442 := { mvpnBgpGeneralTable 1 } 444 MvpnBgpGeneralEntry ::= SEQUENCE { 445 mvpnBgpGenMode INTEGER, 446 mvpnBgpGenUmhSelection INTEGER, 447 mvpnBgpGenSiteType INTEGER, 448 mvpnBgpGenCmcastImportRt MplsVpnRouteDistinguisher, 449 mvpnBgpGenSrcAs Unsigned32, 450 mvpnBgpGenSptnlLimit Unsigned32 451 } 453 mvpnBgpGenMode OBJECT-TYPE 454 SYNTAX INTEGER { 455 rpt-spt (1), 456 spt-only (2) 457 } 458 MAX-ACCESS read-write 459 STATUS current 460 DESCRIPTION 461 "For two different BGP-MVPN modes: 462 rpt-spt(1): intersite-site shared tree mode 463 spt-only(2): inter-site source-only tree mode." 464 ::= { mvpnBgpGeneralEntry 1} 466 mvpnBgpGenUmhSelection OBJECT-TYPE 467 SYNTAX INTEGER { 468 highest-pe-address (1), 469 c-root-group-hashing (2), 470 ucast-umh-route (3) 471 } 472 MAX-ACCESS read-write 473 STATUS current 474 DESCRIPTION 475 "The UMH selection method for this mvpn, as specified in section 476 5.1.3 of [MVPN]: 477 highest-pe-address (1): PE with the highest address 478 c-root-group-hashing (2): hashing based on (c-root, c-group) 479 uncast-umh-route (3): per ucast route towards c-root" 481 ::= { mvpnBgpGeneralEntry 2} 483 mvpnBgpGenSiteType OBJECT-TYPE 484 SYNTAX INTEGER { 485 sender-receiver (1), 486 receiver-only (2), 487 sender-only (3) 488 } 489 MAX-ACCESS read-write 490 STATUS current 491 DESCRIPTION 492 "Whether this site is a receiver-only site or not. 493 sender-receiver (1): both sender and receiver site. 494 receiver-only (2): receiver-only site. 495 sender-only (3): sender-only site." 496 ::= { mvpnBgpGeneralEntry 3} 498 mvpnBgpGenCmcastImportRt OBJECT-TYPE 499 SYNTAX MplsVpnRouteDistinguisher 500 MAX-ACCESS read-write 501 STATUS current 502 DESCRIPTION 503 "The C-multicast Import RT that this device adds to 504 unicast vpn routes that it advertises for this mvpn." 505 ::= { mvpnBgpGeneralEntry 4} 507 mvpnBgpGenSrcAs OBJECT-TYPE 508 SYNTAX Unsiged32 509 MAX-ACCESS read-only 510 STATUS current 511 DESCRIPTION 512 "The Source AS number in Source AS Extended Community that this device 513 adds to the unicast vpn routes that it advertises for this mvpn." 514 ::= { mvpnBgpGeneralEntry 5} 516 mvpnBgpGenSptnlLimit OBJECT-TYPE 517 SYNTAX Unsigned32 518 MAX-ACCESS read-write 519 STATUS current 520 DESCRIPTION 521 "The max number of selective provider tunnels this device allows 522 for this mvpn." 523 ::= { mvpnBgpGeneralEntry 6} 525 -- PMSI Configuration Table 527 mvpnPmsiConfigTable OBJECT-TYPE 528 SYNTAX SEQUENCE OF MvpnPmsiConfigEntry 529 MAX-ACCESS not-accessible 530 STATUS current 531 DESCRIPTION 532 "This table specifies the configured PMSIs." 533 ::= { mvpnConfig 1 } 535 mvpnPmsiConfigEntry OBJECT-TYPE 536 SYNTAX MvpnPmsiConfigEntry 537 MAX-ACCESS not-accessible 538 STATUS current 539 DESCRIPTION 540 "An entry in this table is created for each PMSI configured 541 on this router. It can be referred to by either I-PMSI 542 configuration (in mvpnGeneralEntry) or S-PMSI configuration 543 (in mvpnSpmsiConfigEntry)" 544 INDEX { mplsVpnVrfName, 545 mvpnPmsiConfigTunnelType, 546 mvpnPmsiConfigTunnelAuxInfo, 547 mvpnPmsiConfigTunnelPimGroupAddressType, 548 mvpnPmsiConfigTunnelPimGroupAddress, 549 mvpnPmsiConfigTunnelOrTemplateName } 550 ::= { mvpnPmsiConfigTable 1 } 552 MvpnPmsiConfigEntry ::= SEQUENCE { 553 mvpnPmsiConfigTunnelType INTEGER, 554 mvpnPmsiConfigTunnelAuxInfo Unsigned32, 555 mvpnPmsiConfigTunnelPimGroupAddressType InetAddressType, 556 mvpnPmsiConfigTunnelPimGroupAddress InetAddress, 557 mvpnPmsiConfigTunnelOrTemplateName SnmpAdminString, 558 mvpnPmsiConfigEncapsType INTEGER, 559 mvpnPmsiConfigRowStatus RowStatus 560 } 562 mvpnPmsiConfigTunnelType OBJECT-TYPE 563 SYNTAX INTEGER { pim-asm (1), 564 pim-ssm (2), 565 pim-bidir (3), 566 rsvp-p2mp (4), 567 ldp-p2mp (5), 568 ingress-replication (6) 569 } 570 MAX-ACCESS read-write 571 STATUS current 572 DESCRIPTION 573 "Type of tunnel used to instantiate the PMSI." 574 ::= { mvpnPmsiConfigEntry 1 } 576 mvpnPmsiConfigTunnelAuxInfo OBJECT-TYPE 577 SYNTAX Unsigned32 578 MAX-ACCESS read-write 579 STATUS current 580 DESCRIPTION 581 "Additional tunnel information depending on the type. 582 pim: In case of S-PMSI, number of groups starting at 583 mvpnPmsiConfigTunnelPimGroupAddress. 584 This allows a range of PIM provider tunnel 585 group addresses to be specified in S-PMSI case. 586 In I-PMSI case, it must be 1. 587 rsvp-p2mp: 1 for statically specified rsvp-p2mp tunnel 588 2 for dynamically created rsvp-p2mp tunnel 589 ingress-replication: 590 1 for using any existing p2p/mp2p lsp 591 2 for dynamically creating new p2p lsp" 592 ::= { mvpnPmsiConfigEntry 2 } 594 mvpnPmsiConfigTunnelPimGroupAddressType OBJECT-TYPE 595 SYNTAX InetAddressType 596 MAX-ACCESS read-write 597 STATUS current 598 DESCRIPTION 599 "In case of PIM provider tunnel, the type of tunnel address." 600 ::= { mvpnPmsiConfigEntry 3 } 602 mvpnPmsiConfigTunnelPimGroupAddress OBJECT-TYPE 603 SYNTAX InetAddress 604 MAX-ACCESS read-write 605 STATUS current 606 DESCRIPTION 607 "In case of PIM provider tunnel, the provider tunnel address." 608 ::= { mvpnPmsiConfigEntry 4 } 610 mvpnPmsiConfigTunnelOrTemplateName OBJECT-TYPE 611 SYNTAX SnmpAdminString 612 MAX-ACCESS read-write 613 STATUS current 614 DESCRIPTION 615 "The tunnel name or template name used to create tunnels. 616 Depending on mvpnPmsiConfigTunnelType and 617 mvpnPmsiConfigTunnelAuxInfo: 619 dynamically created rsvp-p2mp tunnel: template name 620 statically specified rsvp-p2mp tunnel: tunnel name 621 ingress-replication using 622 dynamically created lsps: template name 623 other: null" 624 ::= { mvpnPmsiConfigEntry 5 } 626 mvpnPmsiConfigEncapsType OBJECT-TYPE 627 SYNTAX INTEGER { greIp (1), 628 ipIp (2), 629 mpls (3) 630 } 631 MAX-ACCESS read-create 632 STATUS current 633 DESCRIPTION 634 "The encapsulation type to be used, in case of PIM tunnel or 635 ingress-replication." 636 ::= { mvpnPmsiConfigEntry 6 } 638 mvpnPmsiConfigRowStatus OBJECT-TYPE 639 SYNTAX RowStatus 640 MAX-ACCESS read-create 641 STATUS current 642 DESCRIPTION 643 "Used to create/modify/delete a row in this table." 644 ::= { mvpnPmsiConfigEntry 7 } 646 -- S-PMSI configuration table 648 mvpnSpmsiConfigTable OBJECT-TYPE 649 SYNTAX SEQUENCE OF MvpnSpmsiConfigEntry 650 MAX-ACCESS not-accessible 651 STATUS current 652 DESCRIPTION 653 "This table specifies S-PMSI configuration." 654 ::= { mvpnConfig 2 } 656 mvpnSpmsiConfigEntry OBJECT-TYPE 657 SYNTAX MvpnSpmsiConfigEntry 658 MAX-ACCESS not-accessible 659 STATUS current 660 DESCRIPTION 661 "An entry is created for each S-PMSI configuration." 662 INDEX { mplsVpnVrfName, 663 mvpnSpmsiConfigCmcastAddressType, 664 mvpnSpmsiConfigCmcastGroupAddress, 665 mvpnSpmsiConfigCmcastGroupPrefixLen, 666 mvpnSpmsiConfigCmcastSourceAddress, 667 mvpnSpmsiConfigCmcastSourcePrefixLen } 668 ::= { mvpnSpmsiConfigTable 1 } 670 MvpnSpmsiConfigEntry ::= SEQUENCE { 671 mvpnSpmsiConfigCmcastAddressType InetAddressType, 672 mvpnSpmsiConfigCmcastGroupAddress InetAddress, 673 mvpnSpmsiConfigCmcastGroupPrefixLen Unsigned32, 674 mvpnSpmsiConfigCmcastSourceAddress InetAddress, 675 mvpnSpmsiConfigCmcastSourcePrefixLen Unsigned32, 676 mvpnSpmsiConfigThreshold Unsigned32, 677 mvpnSpmsiConfigPmsiPointer RowPointer, 678 mvpnSpmsiConfigRowStatus RowStatus 679 } 681 mvpnSpmsiConfigCmcastAddressType OBJECT-TYPE 682 SYNTAX InetAddressType 683 MAX-ACCESS read-create 684 STATUS current 685 DESCRIPTION 686 "Type of C-multicast address" 687 ::= { mvpnSpmsiConfigEntry 1 } 689 mvpnSpmsiConfigCmcastGroupAddress OBJECT-TYPE 690 SYNTAX InetAddress 691 MAX-ACCESS read-create 692 STATUS current 693 DESCRIPTION 694 "C-multicast group address" 695 ::= { mvpnSpmsiConfigEntry 2 } 697 mvpnSpmsiConfigCmcastGroupPrefixLen OBJECT-TYPE 698 SYNTAX Unsigned32 699 MAX-ACCESS read-create 700 STATUS current 701 DESCRIPTION 702 "C-multicast group address prefix length. 703 A group 0 (or ::0) with prefix length 32 (or 128) 704 indicates wildcard group, while a group 0 (or ::0) 705 with prefix length 0 indicates any group." 706 ::= { mvpnSpmsiConfigEntry 3 } 708 mvpnSpmsiConfigCmcastSourceAddress OBJECT-TYPE 709 SYNTAX InetAddress 710 MAX-ACCESS read-create 711 STATUS current 712 DESCRIPTION 713 "C-multicast source address" 714 ::= { mvpnSpmsiConfigEntry 4 } 716 mvpnSpmsiConfigCmcastSourcePrefixLen OBJECT-TYPE 717 SYNTAX Unsigned32 718 MAX-ACCESS read-create 719 STATUS current 720 DESCRIPTION 721 "C-multicast source address prefix length. 722 A source 0 (or ::0) with prefix length 32 (or 128) 723 indicates a wildcard source, while a source 0 (or ::0) 724 with prefix length 0 indicates any source." 725 ::= { mvpnSpmsiConfigEntry 5 } 727 mvpnSpmsiConfigThreshold OBJECT-TYPE 728 SYNTAX Unsigned32 (0..4294967295) 729 UNITS "kilobits per second" 730 MAX-ACCESS read-create 731 STATUS current 732 DESCRIPTION 733 "The bandwidth threshold value which when exceeded for a 734 multicast routing entry in the given MVRF, triggers usage 735 of S-PMSI." 736 ::= { mvpnSpmsiConfigEntry 6 } 738 mvpnSpmsiConfigPmsiPointer OBJECT-TYPE 739 SYNTAX RowPointer 740 MAX-ACCESS read-create 741 STATUS current 742 DESCRIPTION 743 "This points to a row in mvpnPmsiConfigTable, 744 to specify tunnel attributes." 745 ::= { mvpnSpmsiConfigEntry 7 } 747 mvpnSpmsiConfigRowStatus OBJECT-TYPE 748 SYNTAX RowStatus 749 MAX-ACCESS read-create 750 STATUS current 751 DESCRIPTION 752 "Used to create/modify/delete a row in this table." 753 ::= { mvpnSpmsiConfigEntry 8 } 755 -- Table of PMSI attributes 757 mvpnPmsiTunnelAttributeTable OBJECT-TYPE 758 SYNTAX SEQUENCE OF MvpnPmsiTunnelAttributeEntry 759 MAX-ACCESS not-accessible 760 STATUS current 761 DESCRIPTION 762 "This table is for advertised/received PMSI attributes, 763 to be referred to by I-PMSI or S-PMSI table entries" 764 ::= { mvpnStates 1 } 766 mvpnPmsiTunnelAttributeEntry OBJECT-TYPE 767 SYNTAX MvpnPmsiTunnelAttributeEntry 768 MAX-ACCESS not-accessible 769 STATUS current 770 DESCRIPTION 771 "An entry in this table corresponds to an PMSI attribute 772 that is advertised/received on this router. 773 For BGP-based signaling (for I-PMSI via auto-discovery 774 procedure, or for S-PMSI via S-PMSI A-D routes), 775 they are just as signaled by BGP ([MVPN-BGP] section 5, 776 'PMSI Tunnel attribute'). 777 For UDP-based S-PMSI signaling for PIM-MVPN, 778 they're derived from S-PMSI Join Message 779 ([MVPN] section 7.4.2, 'UDP-based Protocol').. 781 Note that BGP-based signaling may be used for 782 PIM-MVPN as well." 783 INDEX { 784 mvpnPmsiTunnelAttributeType, 785 mvpnPmsiTunnelAttributeLabel, 786 mvpnPmsiTunnelAttributeFlags, 787 mvpnPmsiTunnelAttributeId 788 } 789 ::= { mvpnPmsiTunnelAttributeTable 1 } 791 MvpnPmsiTunnelAttributeEntry ::= SEQUENCE { 792 mvpnPmsiTunnelAttributeType Unsigned32, 793 mvpnPmsiTunnelAttributeLabel MplsLabel, 794 mvpnPmsiTunnelAttributeFlags OCTET STRING, 795 mvpnPmsiTunnelAttributeId OCTET STRING, 796 mvpnPmsiTunnelPointer RowPointer, 797 mvpnPmsiTunnelIf RowPointer 798 } 800 mvpnPmsiTunnelAttributeType OBJECT-TYPE 801 SYNTAX Unsigned32 802 MAX-ACCESS not-accessible 803 STATUS current 804 DESCRIPTION 805 "For BGP-based I/S-PMSI signaling for either PIM or BGP-MVPN, 806 per [BGP-MVPN] section 5, 'PMSI Tunnel Attribute': 808 The Tunnel Type identifies the type of the tunneling technology used 809 to establish the PMSI tunnel. The type determines the syntax and 810 semantics of the Tunnel Identifier field. This document defines the 811 following Tunnel Types: 813 0 - No tunnel information present 814 1 - RSVP-TE P2MP LSP 815 2 - mLDP P2MP LSP 816 3 - PIM-SSM Tree 817 4 - PIM-SM Tree 818 5 - PIM-Bidir Tree 819 6 - Ingress Replication 820 7 - mLDP MP2MP LSP 822 For UDP-based S-PMSI signaling for PIM-MVPN, [MVPN] does not 823 specify if a PIM provider tunnel is SSM, SM or Bidir, 824 and an agent can use either type 3, 4, or 5 based on its 825 best knowledge." 826 ::= { mvpnPmsiTunnelAttributeEntry 1 } 828 mvpnPmsiTunnelAttributeLabel OBJECT-TYPE 829 SYNTAX MplsLabel 830 MAX-ACCESS not-accessible 831 STATUS current 832 DESCRIPTION 833 "For BGP-based I/S-PMSI signaling for either PIM- or BGP-MVPN, 834 per [BGP-MVPN] section 5, 'PMSI Tunnel Attribute': 836 If the MPLS Label field is non-zero, then it contains an MPLS label 837 encoded as 3 octets, where the high-order 20 bits contain the label 838 value. Absence of MPLS Label is indicated by setting the MPLS Label 839 field to zero. 841 For UDP-based S-PMSI signaling for PIM-MVPN, this is not 842 applicable for now, as [MVPN] does not currently specify 843 mpls encapsulation and tunnel aggregation with UDP-based 844 signaling." 845 ::= { mvpnPmsiTunnelAttributeEntry 2 } 847 mvpnPmsiTunnelAttributeFlags OBJECT-TYPE 848 SYNTAX OCTET STRING (SIZE (1)) 849 MAX-ACCESS not-accessible 850 STATUS current 851 DESCRIPTION 852 "For UDP-based S-PMSI signaling for PIM-MVPN, this is 0. 853 For BGP-based I/S-PMSI signaling for either PIM- or BGP-MVPN, 854 per [BGP-MVPN] section 5, 'PMSI Tunnel Attribute': 856 The Flags field has the following format: 858 0 1 2 3 4 5 6 7 859 +-+-+-+-+-+-+-+-+ 860 | reserved |L| 861 +-+-+-+-+-+-+-+-+ 863 This document defines the following flags: 865 + Leaf Information Required (L)" 866 ::= { mvpnPmsiTunnelAttributeEntry 3 } 868 mvpnPmsiTunnelAttributeId OBJECT-TYPE 869 SYNTAX OCTET STRING ( SIZE (4|8|12) ) 870 MAX-ACCESS not-accessible 871 STATUS current 872 DESCRIPTION 873 "For BGP-based I/S-PMSI signaling for either PIM- or BGP-MVPN, 874 per [BGP-MVPN] section 5, 'PMSI Tunnel Attribute': 876 When the type is set to 'No tunnel information present', the PMSI 877 Tunnel attribute carries no tunnel information (no Tunnel 878 Identifier). This type is to be used only in the following case: to 879 enable explicit tracking for a particular customer multicast flow (by 880 setting the Leaf Information Required flag to 1), but without binding 881 this flow to a particular provider tunnel (by omitting any tunnel 882 information). 884 When the type is set to RSVP-TE P2MP LSP, the Tunnel Identifier is 885 as carried in the 886 RSVP-TE P2MP LSP SESSION Object [RFC4875]. 888 When the type is set to mLDP P2MP LSP, the Tunnel Identifier is a 889 P2MP FEC Element [mLDP]. 891 When the type is set to PIM-SM Tree, the Tunnel Identifier is . The node that originated the attribute 893 MUST use the address carried in the Sender Address as the source IP 894 address for the IP/GRE encapsulation of the MVPN data. 896 When the type is set to PIM-SSM Tree, the Tunnel Identifier is . The node that originates the 898 attribute MUST use the address carried in the P-Root Node Address as 899 the source IP address for the IP/GRE encapsulation of the MVPN data. 900 The P-Multicast Group element of the Tunnel identifier of the Tunnel 901 attribute MUST NOT be expected to be the same group for all Intra-AS 902 A-D routes for the same MVPN. According to [RFC4607], the group 903 address can be locally allocated by the originating PE without any 904 consideration for the group address used by other PE on the same 905 MVPN. 907 When the type is set to PIM-Bidir Tree, the Tunnel Identifier is 908 . The node that originated the 909 attribute MUST use the address carried in the Sender Address as the 910 source IP address for the IP/GRE encapsulation of the MVPN data. 912 When the type is set to PIM-SM or PIM-Bidir tree, then the P- 913 Multicast group element of the Tunnel identifier of the Tunnel 914 attribute SHOULD be the same multicast group address for all Intra-AS 915 I-PMSI A-D routes for the same MVPN originated by PEs within a given 916 AS. How this multicast group address is chosen is outside the scope 917 of this specification. 919 When the type is set to Ingress Replication the Tunnel Identifier 920 carries the unicast tunnel endpoint IP address of the local PE that 921 is to be this PE's receiving endpoint address for the tunnel. 923 When the type is set to mLDP MP2MP LSP, the Tunnel Identifier is an 924 MP2MP FEC Element [mLDP]. 926 For UDP-based S-PMSI signaling for PIM-MVPN, [MVPN] only 927 specifies the 'P-Group' address, and that is filled into 928 the first four octets of this field." 929 ::= { mvpnPmsiTunnelAttributeEntry 4 } 931 mvpnPmsiTunnelPointer OBJECT-TYPE 932 SYNTAX RowPointer 933 MAX-ACCESS read-only 934 STATUS current 935 DESCRIPTION 936 "If the tunnel exists in some MIB table, this is the row pointer 937 to it." 938 ::= { mvpnPmsiTunnelAttributeEntry 5 } 940 mvpnPmsiTunnelIf OBJECT-TYPE 941 SYNTAX RowPointer 942 MAX-ACCESS read-only 943 STATUS current 944 DESCRIPTION 945 "If the tunnel has a corresponding interface, this is the 946 row pointer to the ifName table." 947 ::= { mvpnPmsiTunnelAttributeEntry 6 } 949 -- Table of intra-as I-PMSIs advertised/received 951 mvpnIpmsiTable OBJECT-TYPE 952 SYNTAX SEQUENCE OF MvpnIpmsiEntry 953 MAX-ACCESS not-accessible 954 STATUS current 955 DESCRIPTION 956 "This table is for all advertised/received I-PMSI 957 advertisements." 958 ::= { mvpnStates 2 } 960 mvpnIpmsiEntry OBJECT-TYPE 961 SYNTAX MvpnIpmsiEntry 962 MAX-ACCESS not-accessible 963 STATUS current 964 DESCRIPTION 965 "An entry in this table corresponds to an I-PMSI 966 advertisement that is advertised/received on this router. 967 This represents all the sender PEs in the MVPN, 968 with the provider tunnel they use to send traffic." 969 INDEX { mplsVpnVrfName, 970 mvpnIpmsiRD, 971 mvpnIpmsiOrigAddrType, 972 mvpnIpmsiOrigAddress } 973 ::= { mvpnIpmsiTable 1 } 975 MvpnIpmsiEntry ::= SEQUENCE { 976 mvpnIpmsiRD MplsVpnRouteDistinguisher, 977 mvpnIpmsiOrigAddrType InetAddressType, 978 mvpnIpmsiOrigAddress InetAddress, 979 mvpnIpmsiAttribute RowPointer 980 } 982 mvpnIpmsiRD OBJECT-TYPE 983 SYNTAX MplsVpnRouteDistinguisher 984 MAX-ACCESS not-accessible 985 STATUS current 986 DESCRIPTION 987 "The Route Distinguisher in this I-PMSI." 989 ::= { mvpnIpmsiEntry 1 } 991 mvpnIpmsiOrigAddrType OBJECT-TYPE 992 SYNTAX InetAddressType 993 MAX-ACCESS not-accessible 994 STATUS current 995 DESCRIPTION 996 "The Internet address type of mvpnIpmsiOrigAddress." 997 ::= { mvpnIpmsiEntry 2 } 999 mvpnIpmsiOrigAddress OBJECT-TYPE 1000 SYNTAX InetAddress 1001 MAX-ACCESS not-accessible 1002 STATUS current 1003 DESCRIPTION 1004 "The BGP address of the device that originated the I-PMSI." 1005 ::= { mvpnIpmsiEntry 3 } 1007 mvpnIpmsiAttribute OBJECT-TYPE 1008 SYNTAX RowPointer 1009 MAX-ACCESS read-only 1010 STATUS current 1011 DESCRIPTION 1012 "Points to a row in the mvpnPmsiTunnelAttributeTable." 1013 ::= { mvpnIpmsiEntry 4 } 1015 -- Table of inter-as I-PMSIs advertised/received 1017 mvpnInterasIpmsiTable OBJECT-TYPE 1018 SYNTAX SEQUENCE OF MvpnInterasIpmsiEntry 1019 MAX-ACCESS not-accessible 1020 STATUS current 1021 DESCRIPTION 1022 "This table is for all advertised/received inter-as I-PMSI 1023 advertisements." 1024 ::= { mvpnStates 3 } 1026 mvpnInterasIpmsiEntry OBJECT-TYPE 1027 SYNTAX MvpnInterasIpmsiEntry 1028 MAX-ACCESS not-accessible 1029 STATUS current 1030 DESCRIPTION 1031 "An entry in this table corresponds to an inter-as I-PMSI 1032 advertisement that is advertised/received on this router. 1033 This represents all the ASes in the MVPN, 1034 with the provider tunnel used to send traffic to." 1035 INDEX { mplsVpnVrfName, 1036 mvpnInterasIpmsiRD, 1037 mvpnInterasIpmsiSrcAs } 1038 ::= { mvpnInterasIpmsiTable 1 } 1040 MvpnInterasIpmsiEntry ::= SEQUENCE { 1041 mvpnInterasIpmsiRD MplsVpnRouteDistinguisher, 1042 mvpnInterasIpmsiSrcAs Unsigned32, 1043 mvpnInterasIpmsiAttribute RowPointer 1044 } 1046 mvpnInterasIpmsiRD OBJECT-TYPE 1047 SYNTAX MplsVpnRouteDistinguisher 1048 MAX-ACCESS not-accessible 1049 STATUS current 1050 DESCRIPTION 1051 "The Route Distinguisher in this inter-as I-PMSI." 1052 ::= { mvpnInterasIpmsiEntry 1 } 1054 mvpnInterasIpmsiSrcAs OBJECT-TYPE 1055 SYNTAX Unsigned32 1056 MAX-ACCESS not-accessible 1057 STATUS current 1058 DESCRIPTION 1059 "The source-as in this inter-as I-PMSI." 1060 ::= { mvpnInterasIpmsiEntry 2 } 1062 mvpnInterasIpmsiAttribute OBJECT-TYPE 1063 SYNTAX RowPointer 1064 MAX-ACCESS read-only 1065 STATUS current 1066 DESCRIPTION 1067 "Points to a row in the mvpnPmsiTunnelAttributeTable." 1068 ::= { mvpnInterasIpmsiEntry 3 } 1070 -- Table of S-PMSIs advertised/received 1072 mvpnSpmsiTable OBJECT-TYPE 1073 SYNTAX SEQUENCE OF MvpnSpmsiEntry 1074 MAX-ACCESS not-accessible 1075 STATUS current 1076 DESCRIPTION 1077 "This table has information about the S-PMSIs sent/received 1078 by a device." 1079 ::= { mvpnStates 4 } 1081 mvpnSpmsiEntry OBJECT-TYPE 1082 SYNTAX MvpnSpmsiEntry 1083 MAX-ACCESS not-accessible 1084 STATUS current 1085 DESCRIPTION 1086 "An entry in this table is created or updated for every S-PMSI 1087 advertised/received in a particular MVRF." 1088 INDEX { mplsVpnVrfName, 1089 mvpnSpmsiCmcastAddrType, 1090 mvpnSpmsiCmcastGroup, 1091 mvpnSpmsiCmcastGroupPrefixLen, 1092 mvpnSpmsiCmcastSource, 1093 mvpnSpmsiCmcastSourcePrefixLen, 1094 mvpnSpmsiOrigAddrType, 1095 mvpnSpmsiOrigAddress} 1096 ::= { mvpnSpmsiTable 1 } 1098 MvpnSpmsiEntry ::= SEQUENCE { 1099 mvpnSpmsiCmcastAddrType InetAddressType, 1100 mvpnSpmsiCmcastGroup InetAddress, 1101 mvpnSpmsiCmcastGroupPrefixLen InetAddress, 1102 mvpnSpmsiCmcastSource InetAddress, 1103 mvpnSpmsiCmcastSourcePrefixLen InetAddress, 1104 mvpnSpmsiOrigAddrType InetAddressType, 1105 mvpnSpmsiOrigAddress InetAddress, 1106 mvpnSpmsiTunnelAttribute RowPointer, 1107 mvpnSpmsiUpTime TimeInterval, 1108 mvpnSpmsiExpTime TimeInterval, 1109 mvpnSpmsiRefCnt Unsigned32 1110 } 1112 mvpnSpmsiCmcastAddrType OBJECT-TYPE 1113 SYNTAX InetAddressType 1114 MAX-ACCESS not-accessible 1115 STATUS current 1116 DESCRIPTION 1117 "The Internet address type of mvpnSpmsiCmcastGroup/Source." 1118 ::= { mvpnSpmsiEntry 1 } 1120 mvpnSpmsiCmcastGroup OBJECT-TYPE 1121 SYNTAX InetAddress (SIZE (4|16|20)) 1122 MAX-ACCESS not-accessible 1123 STATUS current 1124 DESCRIPTION 1125 "S-PMSI C-multicast group address. 1126 If it is 0 (or ::0), this is a wildcard group, 1127 and mvpnSpmsiCmcastGroupPrefixLen must be 32 (or 128)." 1128 ::= { mvpnSpmsiEntry 2 } 1130 mvpnSpmsiCmcastGroupPrefixLen OBJECT-TYPE 1131 SYNTAX Unsigned32 1132 MAX-ACCESS not-accessible 1133 STATUS current 1134 DESCRIPTION 1135 "S-PMSI C-multicast group address prefix length." 1136 ::= { mvpnSpmsiEntry 3 } 1138 mvpnSpmsiCmcastSource OBJECT-TYPE 1139 SYNTAX InetAddress (SIZE (4|16|20)) 1140 MAX-ACCESS not-accessible 1141 STATUS current 1142 DESCRIPTION 1143 "S-PMSI C-multicast source address 1144 If it is 0 (or ::0), this is a wildcard source, 1145 and mvpnSpmsiCmcastSourcePrefixLen must be 32 (or 128)." 1146 ::= { mvpnSpmsiEntry 4 } 1148 mvpnSpmsiCmcastSourcePrefixLen OBJECT-TYPE 1149 SYNTAX InetAddress (SIZE (4|16|20)) 1150 MAX-ACCESS not-accessible 1151 STATUS current 1152 DESCRIPTION 1153 "S-PMSI C-multicast source address prefix length." 1154 ::= { mvpnSpmsiEntry 5 } 1156 mvpnSpmsiOrigAddrType OBJECT-TYPE 1157 SYNTAX InetAddressType 1158 MAX-ACCESS not-accessible 1159 STATUS current 1160 DESCRIPTION 1161 "The Internet address type of mvpnSpmsiOrigAddress." 1162 ::= { mvpnSpmsiEntry 6 } 1164 mvpnSpmsiOrigAddress OBJECT-TYPE 1165 SYNTAX InetAddress 1166 MAX-ACCESS not-accessible 1167 STATUS current 1168 DESCRIPTION 1169 "The BGP address of the device that originated the S-PMSI." 1170 ::= { mvpnSpmsiEntry 7 } 1172 mvpnSpmsiTunnelAttribute OBJECT-TYPE 1173 SYNTAX RowPointer 1174 MAX-ACCESS read-only 1175 STATUS current 1176 DESCRIPTION 1177 "A row pointer to the mvpnPmsiTunnelAttributeTable" 1178 ::= { mvpnSpmsiEntry 8 } 1180 mvpnSpmsiUpTime OBJECT-TYPE 1181 SYNTAX TimeInterval 1182 MAX-ACCESS read-only 1183 STATUS current 1184 DESCRIPTION 1185 "The time since this S-PMSI 1186 was first advertised/received by the device." 1187 ::= { mvpnSpmsiEntry 9 } 1189 mvpnSpmsiExpTime OBJECT-TYPE 1190 SYNTAX TimeInterval 1191 MAX-ACCESS read-only 1192 STATUS current 1193 DESCRIPTION 1194 "For UDP-based S-PMSI signaling for PIM-MVPN, 1195 the amount of time remaining before this 1196 received S-PMSI Join Message expires, 1197 or the next S-PMSI Join Message refresh is to be 1198 advertised again from the device." 1199 ::= { mvpnSpmsiEntry 10 } 1201 mvpnSpmsiRefCnt OBJECT-TYPE 1202 SYNTAX Unsigned32 1203 MAX-ACCESS read-only 1204 STATUS current 1205 DESCRIPTION 1206 "The number of c-multicast routes that are mapped to 1207 this S-PMSI." 1208 ::= { mvpnSpmsiEntry 11 } 1210 -- Table of multicast routes in an MVPN 1212 mvpnMrouteTable OBJECT-TYPE 1213 SYNTAX SEQUENCE OF MvpnMrouteEntry 1214 MAX-ACCESS not-accessible 1215 STATUS current 1216 DESCRIPTION 1217 "This table augments ipMRouteTable, to provide some MVPN 1218 specific information." 1219 ::= { mvpnStates 5 } 1221 mvpnMrouteEntry OBJECT-TYPE 1222 SYNTAX MvpnMrouteEntry 1223 MAX-ACCESS not-accessible 1224 STATUS current 1225 DESCRIPTION 1226 "The mvpnMrouteEntry matches and augments an ipMRouteEntry, 1227 with MVPN specific information, such as PMSI used." 1228 AUGMENTS { ipMRouteEntry } 1229 ::= { mvpnMrouteTable 1 } 1231 MvpnMrouteEntry ::= SEQUENCE { 1232 mvpnMroutePmsiPointer RowPointer, 1233 mvpnMrouteNumberOfLocalReplication Unsiged32, 1234 mvpnMrouteNumberOfRemoteReplication Unsiged32 1235 } 1237 mvpnMroutePmsiPointer OBJECT-TYPE 1238 SYNTAX RowPointer 1239 MAX-ACCESS read-only 1240 STATUS current 1241 DESCRIPTION 1242 "The I-PMSI or S-PMSI this C-multicast route is using. 1243 This is important because an implementation may not have an 1244 interface corresponding to a provider tunnel, 1245 that can be used in ipMRouteNextHopEntry." 1246 ::= { mvpnMrouteEntry 1 } 1248 mvpnMrouteNumberOfLocalReplication OBJECT-TYPE 1249 SYNTAX Unsigned32 1250 MAX-ACCESS read-only 1251 STATUS current 1252 DESCRIPTION 1253 "Number of replications to local receivers." 1254 ::= { mvpnMrouteEntry 2 } 1256 mvpnMrouteNumberOfRemoteReplication OBJECT-TYPE 1257 SYNTAX Unsigned32 1258 MAX-ACCESS read-only 1259 STATUS current 1260 DESCRIPTION 1261 "Number of (local) replications to remote receivers." 1262 ::= { mvpnMrouteEntry 3 } 1264 -- MVPN Notifications 1266 mvpnMvrfChange NOTIFICATION-TYPE 1267 OBJECTS { 1268 mvpnGenOperStatusChange 1269 } 1270 STATUS current 1271 DESCRIPTION 1272 "A mvpnMvrfChange notification signifies a change about 1273 a MVRF in the device. The change event can be creation of 1274 the MVRF, deletion of the MVRF or an update on the I-PMSI 1275 or S-PMSI configuration of the MVRF. The change event 1276 is indicated by mvpnGenOperStatusChange embedded in 1277 the notification. The user can then query 1278 mvpnGeneralTable, and/or mvpnSpmsiConfigTable to 1279 get the details of the change as necessary. 1281 Note: Since the creation of a MVRF is often followed by 1282 configuration of I-PMSI and/or S-PMSIs for the MVRF, 1283 more than one (three at most) notifications for a MVRF may 1284 be generated serially, and it is really not necessary to 1285 generate all three of them. An agent may choose to generate a 1286 notification for the last event only, that is for S-PMSI 1287 configuration. 1289 Similarly, deletion of I-PMSI and S-PMSI configuration on a 1290 MVRF happens before a MVRF is deleted and it is recommended 1291 that the agent send the notification for MVRF deletion 1292 event only." 1293 ::= { mvpnNotifications 2 } 1294 END 1296 3 Security Considerations 1298 1300 4 IANA Considerations 1302 1304 5 Acknowledgement 1306 Some of the text has been taken almost verbatim from [CISCO-MIB]. 1308 We would like to thank Yakov Rekhter, Jeffrey Haas, Huajin Jeng, 1309 Durga Prasad Velamuri for their helpful comments. 1311 6 References 1313 6.1 Normative References 1315 [KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate 1316 Requirement Levels", BCP 14, RFC 2119, March 1997. 1318 [RFC4382] Nadeau, T., Ed., and H. van der Linde, Ed., "MPLS/BGP 1319 Layer 3 Virtual Private Network (VPN) Management 1320 Information Base", RFC 4382, February 2006. 1322 [MROUTE-MIB]McWalter, D., Thaler, D., and A. Kessler, "IP Multicast 1323 MIB", RFC 5132, December 2007. 1325 [MVPN] Eric C. Rosen, Rahul Aggarwal, et. al., Multicast in MPLS/BGP 1326 IP VPNs, draft-ietf-l3vpn-2547bis-mcast-10, Work In 1327 Progress. 1329 [BGP-MVPN] R. Aggarwal, E. Rosen, T. Morin, Y. Rekhter, BGP Encodings 1330 and Procedures for Multicast in MPLS/BGP IP VPNs, draft- 1331 ietf-l3vpn-2547bis-mcast-bgp-08.txt 1333 6.2 Informative References 1335 [CISCO-MIB] Susheela Vaidya, Thomas D. Nadeau, Harmen Van der Linde, 1336 Multicast in BGP/MPLS IP VPNs Management Information Base, 1337 draft-svaidya-mcast-vpn-mib-02.txt, Work In Progress, 1338 April 2005. 1340 Authors' Addresses 1342 Saud Asif 1343 AT&T 1344 C5-3D30 1345 200 South Laurel Avenue 1346 Middletown, NJ 07748 1347 USA 1348 Email: sasif@att.com 1350 Andy Green 1351 BT Design 21CN Converged Core IP & Data 1352 01473 629360 1353 Adastral Park, Martlesham Heath, Ipswich IP5 3RE 1354 UK 1355 Email: andy.da.green@bt.com 1357 Sameer Gulrajani 1358 Cisco Systems 1359 Tasman Drive 1360 San Jose, CA 95134 1361 USA 1363 EMail: sameerg@cisco.com 1365 Pradeep G. Jain 1366 Alcatel-Lucent Inc 1367 701 E Middlefield road 1368 Mountain view, CA 94043 1369 USA 1370 Email: pradeep.jain@alcatel-lucent.com 1371 Jeffrey (Zhaohui) Zhang 1372 Juniper Networks, Inc. 1373 10 Technology Park Drive 1374 Westford, MA 01886 1375 USA 1376 Email: zzhang@juniper.net