idnits 2.17.1 draft-ietf-l2vpn-vpls-mib-15.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to contain a disclaimer for pre-RFC5378 work, and may have content which was first submitted before 10 November 2008. The disclaimer is necessary when there are original authors that you have been unable to contact, or if some do not wish to grant the BCP78 rights to the IETF Trust. If you are able to get all authors (current and original) to grant those rights, you can and should remove the disclaimer; otherwise, the disclaimer is needed and you can ignore this comment. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (Feburary 19, 2014) is 3774 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: 'RFC3414' is mentioned on line 2117, but not defined == Missing Reference: 'RFC3826' is mentioned on line 2117, but not defined == Missing Reference: 'RFC5591' is mentioned on line 2119, but not defined == Missing Reference: 'RFC5592' is mentioned on line 2120, but not defined == Missing Reference: 'RFC6353' is mentioned on line 2120, but not defined == Unused Reference: 'RFC3413' is defined on line 2175, but no explicit reference was found in the text == Unused Reference: 'RFC4364' is defined on line 2191, but no explicit reference was found in the text == Unused Reference: 'RFC6074' is defined on line 2233, but no explicit reference was found in the text Summary: 0 errors (**), 0 flaws (~~), 10 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 L2VPN Working Group Thomas D. Nadeau (Ed.) 2 Internet Draft Lucid Vision 3 Intended status: Standards Track 4 Expires: Aug 2014 Agrahara S Kiran Koushik (Ed.) 5 Cisco Systems, Inc. 7 Rohit Mediratta (Ed.) 8 Alcatel-Lucent 10 Feburary 19, 2014 12 Virtual Private Lan Services (VPLS) Management Information Base 14 draft-ietf-l2vpn-vpls-mib-15.txt 16 Status of this Memo 18 This Internet-Draft is submitted in full conformance with the 19 provisions of BCP 78 and BCP 79. 21 This document may contain material from IETF Documents or IETF 22 Contributions published or made publicly available before November 23 10, 2008. The person(s) controlling the copyright in some of this 24 material may not have granted the IETF Trust the right to allow 25 modifications of such material outside the IETF Standards Process. 26 Without obtaining an adequate license from the person(s) controlling 27 the copyright in such materials, this document may not be modified 28 outside the IETF Standards Process, and derivative works of it may 29 not be created outside the IETF Standards Process, except to format 30 it for publication as an RFC or to translate it into languages other 31 than English. 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 39 months and may be updated, replaced, or obsoleted by other documents 40 at any time. It is inappropriate to use Internet-Drafts as 41 reference 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/ietf/1id-abstracts.txt 46 The list of Internet-Draft Shadow Directories can be accessed at 47 http://www.ietf.org/shadow.html 48 VPLS Management Information Base Feb, 2014 50 This Internet-Draft will expire on July 30, 2014. 52 Copyright Notice 54 Copyright (c) 2014 IETF Trust and the persons identified as the 55 document authors. All rights reserved. 57 This document is subject to BCP 78 and the IETF Trust's Legal 58 Provisions Relating to IETF Documents 59 (http://trustee.ietf.org/license-info) in effect on the date of 60 publication of this document. Please review these documents 61 carefully, as they describe your rights and restrictions with 62 respect to this document. Code Components extracted from this 63 document must include Simplified BSD License text as described in 64 Section 4.e of the Trust Legal Provisions and are provided without 65 warranty as described in the Simplified BSD License. 67 Abstract 69 This memo defines a portion of the Management Information Base (MIB) 70 for use with network management protocols in the Internet community. 71 In particular, it describes managed objects for to configure and/or 72 monitor Virtual Private LAN services. It needs to be used in 73 conjunction with The Pseudowire (PW) Management Information Base. 75 Table of Contents 77 1. Introduction...................................................3 78 2. Terminology....................................................3 79 2.1. Conventions used in this document.........................3 80 3. The Internet-Standard Management Framework.....................4 81 4. VPLS MIB Module Architecture...................................4 82 4.1. VPLS-GENERIC-MIB Module Usage.............................5 83 4.2. VPLS-LDP-MIB Module Usage.................................5 84 4.3. VPLS-BGP-MIB Module Usage.................................5 85 4.4. Relations to other MIB modules............................6 86 5. Example of the VPLS MIB modules usage..........................6 87 6. Object definitions.............................................7 88 6.1. VPLS-GENERIC-MIB..........................................7 89 6.2. VPLS-LDP-MIB Object definitions..........................28 90 6.3. VPLS-BGP-MIB Object definitions..........................34 91 VPLS Management Information Base Feb, 2014 93 7. Security Considerations.......................................42 94 8. IANA Considerations...........................................43 95 9. References....................................................43 96 9.1. Normative References.....................................43 97 9.2. Informative References...................................44 98 10. Acknowledgments..............................................45 99 11. Authors' Addresses...........................................45 100 12. Full Copyright Statement.....................................45 102 1. Introduction 104 This memo defines a portion of the Management Information 105 Base (MIB) for use with network management protocols in the Internet 106 community. In particular, it defines three MIB modules that can be 107 used to manage VPLS (Virtual Private LAN Services) for transmission 108 over a packet Switched Network (PSN) using LDP [RFC4762] or 109 BGP [RFC4761] signaling. This MIB module provides generic management 110 of VPLS services as defined by the IETF L2VPN Working Group. 111 Additional MIB modules are also defined for management of LDP VPLS 112 and BGP VPLS services as defined by the IETF L2VPN Working Group. 114 2. Terminology 116 This document adopts the definitions, acronyms and mechanisms 117 described in [RFC3985]. Unless otherwise stated, the mechanisms of 118 [RFC3985] apply and will not be re-described here. 120 2.1. Conventions used in this document 122 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 123 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 124 document are to be interpreted as described in [RFC2119]. 126 3. The Internet-Standard Management Framework 128 For a detailed overview of the documents that describe the current 129 Internet-Standard Management Framework, please refer to section 7 130 of RFC 3410 [RFC3410]. 132 Managed objects are accessed via a virtual information store, 133 termed the Management Information Base or MIB. MIB objects are 134 generally accessed through the Simple Network Management Protocol 135 (SNMP). Objects in the MIB are defined using the mechanisms 136 defined in the Structure of Management Information (SMI). This 137 memo specifies a set of MIB modules that are compliant to the SMIv2, 138 which is described in STD 58 [RFC2578][RFC2579][RFC2580]. 140 4. VPLS MIB Module Architecture 141 VPLS Management Information Base Feb, 2014 143 The MIB structure for defining a VPLS service is composed from 144 three MIB modules. 146 The first is the VPLS-GENERIC-MIB module, which configures 147 general parameters of the VPLS service that are common to all 148 types of VPLS services. 150 The second is the VPLS-LDP-MIB module, which configures 151 VPLS-LDP [RFC4762] specific parameters of the VPLS service. 153 The third is the VPLS-BGP-MIB module, which configures 154 VPLS-BGP [RFC4761] specific parameters of the VPLS service. 156 The arrows in Figure A indicate whether we can map data from 157 one module into another. 159 -------- ----------------- 160 PW Mapping | | | | 161 -----> | PW-MIB |-->|PW-ENET/MPLS-MIB | 162 __________ / | | | | 163 | | / -------- ----------------- 164 | VPLS MIB | / ------------ 165 | |----------------------> | | 166 ---------- MAC addr. mapping using | BRIDGE-MIB | 167 [SNMP-CONTEXT-MAP-MIB] | | 168 ------------ 170 Figure A 171 -------- 173 Additionally service-specific modules may be defined in other 174 documents. 176 4.1. VPLS-GENERIC-MIB Module Usage 178 An entry in the vplsConfigTable MUST exist for every VPLS service. 179 This table holds generic parameters which apply to a VPLS service 180 which can be signaled via LDP or BGP. 182 A conceptual row can be created in the vplsConfigTable in one of 183 the following ways: 185 1) An NMS creates a row in the vplsConfigTable using SNMP Set 186 requests which causes the node to create and start a new VPLS 187 service. The agent MUST support the creation of VPLS 188 services in this way. 190 2) The agent MAY create a row in the vplsConfigTable automatically 191 due to some auto discovery application, or based on 192 VPLS Management Information Base Feb, 2014 194 configuration that is done through non-SNMP applications. 195 This mode is OPTIONAL. 197 At least one entry in the vplsPwBindTable MUST exist for 198 each VPLS service. 199 This binding table links one VPLS service with one or many 200 pseudowires (defined in [RFC5601]). Each pseudowire may 201 be used as a spoke or as part of a mesh based on the parameters 202 defined in this table. 204 For each VPLS service, an entry in the vplsBgpAdConfigTable MUST 205 exist if Auto-discovery has been enabled for that service. 206 This table stores the information required for auto-discovery. 208 For each VPLS service, at least one entry in the 209 vplsBgpRteTargetTable MUST exist if auto-discovery 210 has been configured for that service. One service can import 211 and export multiple Route Targets. 213 4.2. VPLS-LDP-MIB Module Usage 215 An entry in the vplsLdpConfigTable MUST be created by the agent 216 for a VPLS service signaled using LDP. 218 4.3. VPLS-BGP-MIB Module Usage 220 An entry in the vplsBgpConfigTable MUST be created by the agent 221 for a VPLS service signaled using BGP. 223 4.4. Relations to other MIB modules 225 - The vplsPwBindTable links the VPLS entry to the pwTable in 226 [RFC5601] 228 - The association of MAC addresses to VPLS entries is possible 229 by adding a turnstile function to interpret the entries in 230 [SNMP-CONTEXT-MAP-MIB]. In [SNMP-CONTEXT-MAP-MIB] there is 231 a mapping between the vacmContextName [RFC3415] to 232 dot1dBasePort [RFC4188] and vplsConfigIndex. This mapping can 233 be used to map the vplsConfigIndex to a dot1dBasePort 234 in the BRIDGE-MIB. This resulting value of dot1dBasePort 235 can be used to access corresponding MAC addresses that belong 236 to a particular vplsConfigIndex. 238 - Unless all the necessary entries in the applicable tables have 239 been created and all the parameters have been consistently 240 configured in those tables, signaling cannot be performed 241 VPLS Management Information Base Feb, 2014 243 from the local node, and the vplsConfigRowStatus should report 244 'notReady'. 246 - Statistics can be gathered from the Pseudowire performance 247 tables in [RFC5601] 249 5. Example of the VPLS MIB modules usage 251 In this section we provide an example of using the MIB objects 252 described in section 7 to set up a VPLS service over MPLS. While 253 this example is not meant to illustrate every permutation of the 254 MIB, it is intended as an aid to understanding some of the key 255 concepts. It is meant to be read after going through the MIB 256 itself. 257 In this example a VPLS service (VPLS-A) is setup using LDP for 258 signaling the pseudowire. The binding between the VPLS service 259 and the pseudowire is reflected in the VplsPwBindTable. 260 The pseudowire configuration is defined in RFC 5601. 262 In the VPLS-GENERIC-MIB module: 264 Row in vplsConfigTable: 265 { 266 vplsConfigIndex 10, 267 vplsConfigName "VPLS-A" 268 vplsConfigAdminStatus 1(up), 269 vplsConfigMacLearning 1(true), 270 vplsConfigDiscardUnknownDest 2(false), 271 vplsConfigMacAging 1(true), 272 vplsConfigVpnId "100:10" 273 vplsConfigRowStatus 1(active) 274 } 276 Row in vplsStatusTable: 277 { 278 vplsStatusOperStatus 1(up), 279 vplsStatusPeerCount 1 280 } 282 Row in VplsPwBindTable : 283 { 284 vplsPwBindConfigType manual, 285 vplsPwBindType spoke, 286 vplsPwBindRowStatus 1(active), 287 vplsPwBindStorageType volatile 288 } 289 VPLS Management Information Base Feb, 2014 291 In the VPLS-LDP-MIB module: 293 Row in vplsLdpConfigTable: 294 { 295 vplsLdpConfigMacAddrWithdraw 1(true), 297 } 299 Row in vplsLdpPwBindTable: 300 { 301 vplsLdpPwBindType 1(mesh), 302 vplsLdpPwBindMacAddressLimit 100 303 } 305 6. Object definitions 307 6.1. VPLS-GENERIC-MIB 309 This MIB module makes references to the following documents. 310 [RFC2578], [RFC2579], [RFC2580], [RFC3411], 311 [RFC2863], [RFC4265] and [RFC3813]. 313 VPLS-GENERIC-MIB DEFINITIONS ::= BEGIN 315 IMPORTS 316 NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, 317 Unsigned32, Counter32, transmission 318 FROM SNMPv2-SMI -- RFC2578 320 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 321 FROM SNMPv2-CONF -- RFC2580 323 TruthValue, RowStatus, StorageType, TEXTUAL-CONVENTION 324 FROM SNMPv2-TC -- RFC2579 326 SnmpAdminString 327 FROM SNMP-FRAMEWORK-MIB -- RFC3411 329 pwIndex 330 FROM PW-STD-MIB 332 VPNIdOrZero 333 FROM VPN-TC-STD-MIB -- RFC4265 335 VPLS Management Information Base Feb, 2014 337 ; 339 vplsGenericDraft01MIB MODULE-IDENTITY 340 -- RFC Editor: Please replace vplsGenericDraft01MIB with 341 -- vplsGenericMIB throughout the MIB and remove 342 -- this note. 343 LAST-UPDATED "201401301200Z" -- 30 Jan 2014 12:00:00 GMT 344 ORGANIZATION "Layer 2 Virtual Private Networks (L2VPN) 345 Working Group" 346 CONTACT-INFO 347 " 348 Thomas D. Nadeau 349 Email: tnadeau@lucidvison.com 351 The L2VPN Working Group (email distribution l2vpn@ietf.org, 352 http://www.ietf.org/html.charters/l2vpn-charter.html) 353 " 355 DESCRIPTION 356 "Copyright (C) The IETF Trust (2014). The initial 357 version of this MIB module was published in RFC XXXX. 358 -- RFC Editor: Please replace XXXX with RFC number & remove 359 -- this note. 361 For full legal notices see the RFC itself or see: 362 http://www.ietf.org/copyrights/ianamib.html 363 This MIB module contains generic managed object definitions 364 for Virtual Private LAN Services as define in RFC4762 and 365 RFC4761. 367 This MIB module enables the use of any underlying Pseudowire 368 network." 370 -- Revision history. 371 REVISION 372 "201401301200Z" -- 30 Jan 2014 12:00:00 GMT 373 VPLS Management Information Base Feb, 2014 375 DESCRIPTION "Initial version published as part of RFC YYYY." 376 -- RFC Editor: please replace YYYY with IANA assigned value, and 377 -- delete this note. 379 ::= { transmission AAA } 381 -- RFC Editor: please replace AAA with IANA assigned value, and 382 -- delete this note. 383 -- VPLS BGP Auto-Discovery specific Textual Convention 384 VplsBgpRouteDistinguisher ::= TEXTUAL-CONVENTION 385 STATUS current 386 DESCRIPTION 387 "Syntax for a route distinguisher that matches the 388 definition in RFC4364. For a complete 389 definition of a route distinguisher, see RFC4364. 390 For more details on use of a route distinguisher 391 for a VPLS service, see RFC4761." 392 REFERENCE 393 "RFC4364" 394 SYNTAX OCTET STRING(SIZE (0..256)) 396 VplsBgpRouteTarget ::= TEXTUAL-CONVENTION 397 STATUS current 398 DESCRIPTION 399 "Syntax for a route target that matches the 400 definition in RFC4364. For a complete 401 definition of a route target, see RFC4364." 402 REFERENCE 403 "RFC4364" 404 SYNTAX OCTET STRING(SIZE (0..256)) 406 VplsBgpRouteTargetType ::= TEXTUAL-CONVENTION 407 STATUS current 408 DESCRIPTION 409 "Used to define the type of a route target usage. 410 Route targets can be specified to be imported, 411 exported, or both. For a complete definition of a 412 route target, see RFC4364." 413 REFERENCE 414 VPLS Management Information Base Feb, 2014 416 "RFC4364" 417 SYNTAX INTEGER { import(1), export(2), both(3) } 419 -- Top-level components of this MIB. 421 -- Notifications 422 vplsNotifications OBJECT IDENTIFIER 423 ::= { vplsGenericDraft01MIB 0 } 424 -- Tables, Scalars 425 vplsObjects OBJECT IDENTIFIER 426 ::= { vplsGenericDraft01MIB 1 } 427 -- Conformance 428 vplsConformance OBJECT IDENTIFIER 429 ::= { vplsGenericDraft01MIB 2 } 431 -- PW Virtual Connection Table 433 vplsConfigIndexNext OBJECT-TYPE 434 SYNTAX Unsigned32 435 MAX-ACCESS read-only 436 STATUS current 437 DESCRIPTION 438 "This object contains an appropriate value to be used 439 for vplsConfigIndex when creating entries in the 440 vplsConfigTable. The value 0 indicates that no 441 unassigned entries are available. To obtain the 442 value of vplsConfigIndex for a new entry in the 443 vplsConfigTable, the manager issues a management 444 protocol retrieval operation to obtain the current 445 value of vplsConfigIndex. After each retrieval 446 operation, the agent should modify the value to 447 reflect the next unassigned index. After a manager 448 retrieves a value the agent will determine through 449 its local policy when this index value will be made 450 available for reuse." 451 ::= { vplsObjects 1 } 453 vplsConfigTable OBJECT-TYPE 454 SYNTAX SEQUENCE OF VplsConfigEntry 455 MAX-ACCESS not-accessible 456 STATUS current 457 DESCRIPTION 458 "This table specifies information for configuring 459 and monitoring Virtual Private Lan Services(VPLS). 460 " 461 ::= { vplsObjects 2 } 462 VPLS Management Information Base Feb, 2014 464 vplsConfigEntry OBJECT-TYPE 465 SYNTAX VplsConfigEntry 466 MAX-ACCESS not-accessible 467 STATUS current 468 DESCRIPTION 469 "A row in this table represents a Virtual Private Lan 470 Service(VPLS) in a packet network. It is indexed by 471 vplsConfigIndex, which uniquely identifies a single VPLS. 473 A row is created via SNMP or by the agent if a 474 VPLS service is created by a non-SNMP application or 475 due to the Auto-Discovery process. 477 All of the read-create objects values except 478 vplsConfigSignalingType can be changed when 479 vplsConfigRowStatus is in the active(1) 480 state. Changes for vplsConfigSignalingType are only 481 allowed when the vplsConfigRowStatus is in 482 notInService(2) or notReady(3) states. 483 " 484 INDEX { vplsConfigIndex } 485 ::= { vplsConfigTable 1 } 487 VplsConfigEntry ::= 488 SEQUENCE { 489 vplsConfigIndex Unsigned32, 490 vplsConfigName SnmpAdminString, 491 vplsConfigDescr SnmpAdminString, 492 vplsConfigAdminStatus INTEGER, 493 vplsConfigMacLearning TruthValue, 494 vplsConfigDiscardUnknownDest TruthValue, 495 vplsConfigMacAging TruthValue, 496 vplsConfigFwdFullHighWatermark Unsigned32, 497 vplsConfigFwdFullLowWatermark Unsigned32, 498 vplsConfigRowStatus RowStatus, 499 vplsConfigMtu Unsigned32, 500 vplsConfigVpnId VPNIdOrZero, 501 vplsConfigStorageType StorageType, 502 vplsConfigSignalingType INTEGER 503 } 505 vplsConfigIndex OBJECT-TYPE 506 SYNTAX Unsigned32 (1..2147483647) 507 MAX-ACCESS not-accessible 508 VPLS Management Information Base Feb, 2014 510 STATUS current 511 DESCRIPTION 512 "Unique index for the conceptual row identifying 513 a VPLS service." 514 ::= { vplsConfigEntry 1 } 516 vplsConfigName OBJECT-TYPE 517 SYNTAX SnmpAdminString 518 MAX-ACCESS read-create 519 STATUS current 520 DESCRIPTION 521 "A textual name of the VPLS. 522 If there is no local name, or this object is 523 otherwise not applicable, then this object MUST 524 contain a zero-length octet string." 525 DEFVAL { "" } 526 ::= { vplsConfigEntry 2 } 528 vplsConfigDescr OBJECT-TYPE 529 SYNTAX SnmpAdminString 530 MAX-ACCESS read-create 531 STATUS current 532 DESCRIPTION 533 "A textual string containing information about the 534 VPLS service. If there is no information for this VPLS 535 service, then this object MUST contain a zero-length 536 octet string." 537 DEFVAL { "" } 538 ::= { vplsConfigEntry 3 } 540 vplsConfigAdminStatus OBJECT-TYPE 541 SYNTAX INTEGER { 542 up(1), 543 down(2), 544 testing(3) -- in some test mode 546 } 547 MAX-ACCESS read-create 548 STATUS current 549 DESCRIPTION 550 "The desired administrative state of the VPLS 551 service. If the administrative status of the 552 VPLS service is changed to enabled then this 553 service is able to utilize pseudowires to 554 perform the tasks of a VPLS service. 555 The testing(3) state indicates that no operational 556 packets can be passed. " 557 DEFVAL { down } 558 VPLS Management Information Base Feb, 2014 560 ::= { vplsConfigEntry 4 } 562 vplsConfigMacLearning OBJECT-TYPE 563 SYNTAX TruthValue 564 MAX-ACCESS read-create 565 STATUS current 566 DESCRIPTION 567 "This object specifies if MAC Learning is enabled 568 in this service. If this object is true then MAC 569 Learning is enabled. If false, then MAC Learning is 570 disabled." 571 DEFVAL { true } 572 ::= { vplsConfigEntry 6 } 574 vplsConfigDiscardUnknownDest OBJECT-TYPE 575 SYNTAX TruthValue 576 MAX-ACCESS read-create 577 STATUS current 578 DESCRIPTION 579 "If the value of this object is 'true', then frames 580 received with an unknown destination MAC are discarded 581 in this VPLS. If 'false', then the packets are 582 processed." 583 DEFVAL { false } 584 ::= { vplsConfigEntry 7 } 586 vplsConfigMacAging OBJECT-TYPE 587 SYNTAX TruthValue 588 MAX-ACCESS read-create 589 STATUS current 590 DESCRIPTION 591 "If the value of this object is 'true' 592 then the MAC aging process is enabled in 593 this VPLS. If 'false', then the MAC aging process 594 is disabled" 595 DEFVAL { true } 596 ::= { vplsConfigEntry 8 } 598 vplsConfigFwdFullHighWatermark OBJECT-TYPE 599 SYNTAX Unsigned32 (0..100) 600 UNITS "percentage" 601 MAX-ACCESS read-create 602 STATUS current 603 DESCRIPTION 604 "This object specifies the utilization of the 605 forwarding database for this VPLS instance at 606 which the vplsFwdFullAlarmRaised notification 607 will be sent. The value of this object must 608 be higher than vplsConfigFwdFullLowWatermark." 610 VPLS Management Information Base Feb, 2014 612 DEFVAL { 95 } 613 ::= { vplsConfigEntry 10 } 615 vplsConfigFwdFullLowWatermark OBJECT-TYPE 616 SYNTAX Unsigned32 (0..99) 617 UNITS "percentage" 618 MAX-ACCESS read-create 619 STATUS current 620 DESCRIPTION 621 "This object specifies the utilization of the 622 forwarding database for this VPLS instance 623 at which the vplsFwdFullAlarmCleared 624 notification will be sent. The value of this 625 object must be less than 626 vplsConfigFwdFullHighWatermark" 627 DEFVAL { 90 } 628 ::= { vplsConfigEntry 11 } 630 vplsConfigRowStatus OBJECT-TYPE 631 SYNTAX RowStatus 632 MAX-ACCESS read-create 633 STATUS current 634 DESCRIPTION 635 "For creating, modifying, and deleting this row. 637 All other objects in this row must be set to valid 638 values before this object can be set to active(1). 640 None of the read-create objects in the 641 conceptual rows may be changed when this 642 object is in the active(1) state. 644 If this object is set to destroy(6) or deleted by the 645 agent, all associated entries in the vplsPWBindTable, 646 vplsBGPRteTargetTable and vplsBgpVETable shall be 647 deleted." 648 ::= { vplsConfigEntry 12 } 650 vplsConfigMtu OBJECT-TYPE 651 SYNTAX Unsigned32 (64..9192) 652 MAX-ACCESS read-create 653 STATUS current 654 DESCRIPTION 655 "The value of this object specifies the MTU of this 656 vpls instance. This can be used to limit the MTU to a 657 value lower than the MTU supported by the associated 658 Pseudowires" 659 DEFVAL { 1518 } 660 ::= { vplsConfigEntry 13 } 661 VPLS Management Information Base Feb, 2014 663 vplsConfigVpnId OBJECT-TYPE 664 SYNTAX VPNIdOrZero 665 MAX-ACCESS read-create 666 STATUS current 667 DESCRIPTION 668 "This objects indicates the IEEE 802-1990 669 VPN ID of the associated VPLS service." 670 ::= { vplsConfigEntry 14 } 672 vplsConfigStorageType OBJECT-TYPE 673 SYNTAX StorageType 674 MAX-ACCESS read-create 675 STATUS current 676 DESCRIPTION 677 "This variable indicates the storage type for this row." 678 DEFVAL { nonVolatile } 679 ::= { vplsConfigEntry 15 } 681 vplsConfigSignalingType OBJECT-TYPE 682 SYNTAX INTEGER { 683 ldp(1), 684 bgp(2), 685 none(3) 687 } 688 MAX-ACCESS read-create 689 STATUS current 690 DESCRIPTION 691 "Desired signaling type of the VPLS service. 693 If the value of this object is ldp(1), then a 694 corresponding entry in vplsLdpConfigTable is required. 696 If the value of this object is bgp(2), then a 697 corresponding entry in vplsBgpConfigTable is required. 699 If the value of this object is none(3), then it 700 indicates a static configuration of PW labels." 701 DEFVAL { none } 702 ::= { vplsConfigEntry 16 } 704 -- VPLS Status table 706 vplsStatusTable OBJECT-TYPE 707 SYNTAX SEQUENCE OF VplsStatusEntry 708 MAX-ACCESS not-accessible 709 STATUS current 710 VPLS Management Information Base Feb, 2014 712 DESCRIPTION 713 "This table provides information for monitoring 714 Virtual Private Lan Services (VPLS). 715 " 716 ::= { vplsObjects 3 } 718 vplsStatusEntry OBJECT-TYPE 719 SYNTAX VplsStatusEntry 720 MAX-ACCESS not-accessible 721 STATUS current 722 DESCRIPTION 723 "A row in this table represents a Virtual Private Lan 724 Service(VPLS) in a packet network. It is indexed by 725 vplsConfigIndex, which uniquely identifies a single VPLS. 727 A row in this table is automatically created by the agent 728 when a VPLS service is first set to active. 729 " 730 AUGMENTS { vplsConfigEntry } 731 ::= { vplsStatusTable 1 } 733 VplsStatusEntry ::= 734 SEQUENCE { 735 vplsStatusOperStatus INTEGER, 736 vplsStatusPeerCount Counter32 737 } 739 vplsStatusOperStatus OBJECT-TYPE 740 SYNTAX INTEGER { 741 other(0), 742 up(1), 743 down(2) 744 } 745 MAX-ACCESS read-only 746 STATUS current 747 DESCRIPTION 748 "The current operational state of this VPLS Service." 749 ::= { vplsStatusEntry 1 } 751 vplsStatusPeerCount OBJECT-TYPE 752 SYNTAX Counter32 753 MAX-ACCESS read-only 754 STATUS current 755 DESCRIPTION 756 "This objects specifies the number of peers 757 (pseudowires) present in this VPLS instance." 758 ::= { vplsStatusEntry 2 } 759 VPLS Management Information Base Feb, 2014 761 -- VPLS PW Binding Table 763 vplsPwBindTable OBJECT-TYPE 764 SYNTAX SEQUENCE OF VplsPwBindEntry 765 MAX-ACCESS not-accessible 766 STATUS current 767 DESCRIPTION 768 "This table provides an association between a 769 VPLS service and the corresponding pseudowires. 770 A service can have more than one pseudowire 771 association. Pseudowires are defined in 772 the pwTable" 773 ::= { vplsObjects 4 } 775 vplsPwBindEntry OBJECT-TYPE 776 SYNTAX VplsPwBindEntry 777 MAX-ACCESS not-accessible 778 STATUS current 779 DESCRIPTION 780 "Each row represents an association between a 781 VPLS instance and a pseudowire 782 defined in the pwTable. Each index is unique 783 in describing an entry in this table. However 784 both indexes are required to define the one 785 to many association of service to 786 pseudowire. 788 Entries in this table may be created or deleted 789 through SNMP, as side-effects of console or other 790 non-SNMP management commands, or upon learning via 791 autodiscovery. 793 It is optional for the agent to allow entries to be 794 created that point to non-existent entries in 795 vplsConfigTable." 796 INDEX { vplsConfigIndex, pwIndex } 797 ::= { vplsPwBindTable 1 } 799 VplsPwBindEntry ::= 800 SEQUENCE { 801 vplsPwBindConfigType INTEGER, 802 vplsPwBindType INTEGER, 803 vplsPwBindRowStatus RowStatus, 804 vplsPwBindStorageType StorageType 805 } 807 vplsPwBindConfigType OBJECT-TYPE 808 SYNTAX INTEGER { 809 VPLS Management Information Base Feb, 2014 811 manual (1), 812 autodiscovery (2) 813 } 814 MAX-ACCESS read-create 815 STATUS current 816 DESCRIPTION 817 "The value of this object indicates 818 whether the Pseudo Wire binding was created 819 via SNMP/Console or via Auto-Discovery. 821 The value of this object must be 822 specified when the row is created and cannot 823 be changed while the row status is active(1)" 824 ::= { vplsPwBindEntry 1 } 826 vplsPwBindType OBJECT-TYPE 827 SYNTAX INTEGER { 828 mesh (1), 829 spoke (2) 830 } 831 MAX-ACCESS read-create 832 STATUS current 833 DESCRIPTION 834 "The value of this object indicates 835 whether the pseudowire binding is of 836 type mesh or spoke. 838 The value of this object must be 839 specified when the row is created and cannot 840 be changed while the row status is active(1)" 841 ::= { vplsPwBindEntry 2 } 843 vplsPwBindRowStatus OBJECT-TYPE 844 SYNTAX RowStatus 845 MAX-ACCESS read-create 846 STATUS current 847 DESCRIPTION 848 "For creating, modifying, and deleting this row. 850 All other objects in this row must be set to valid 851 values before this object can be set to active(1). 853 None of the read-create objects in the 854 conceptual rows may be changed when this 855 object is in the active(1) state. 857 If autodiscovered entries are deleted they would 858 likely re-appear in the next autodiscovery interval." 860 VPLS Management Information Base Feb, 2014 862 ::= { vplsPwBindEntry 3 } 864 vplsPwBindStorageType OBJECT-TYPE 865 SYNTAX StorageType 866 MAX-ACCESS read-create 867 STATUS current 868 DESCRIPTION 869 "This variable indicates the storage type for this row." 870 DEFVAL { volatile } 871 ::= { vplsPwBindEntry 4 } 873 -- vplsBgpADConfigTable 875 vplsBgpADConfigTable OBJECT-TYPE 876 SYNTAX SEQUENCE OF VplsBgpADConfigEntry 877 MAX-ACCESS not-accessible 878 STATUS current 879 DESCRIPTION 880 "This table specifies information for configuring 881 BGP Auto-Discovery parameters for a given VPLS service. 882 " 883 ::= { vplsObjects 5 } 885 vplsBgpADConfigEntry OBJECT-TYPE 886 SYNTAX VplsBgpADConfigEntry 887 MAX-ACCESS not-accessible 888 STATUS current 889 DESCRIPTION 890 "A row in this table indicates that BGP based Auto- 891 Discovery is in use for this instance of VPLS. 892 A row in this table is indexed by vplsConfigIndex, which 893 uniquely identifies a single VPLS. 895 Entries in this table may be created or deleted 896 through SNMP, as side-effects of console or other 897 non-SNMP management commands, or upon learning via 898 autodiscovery. 900 All of the read-create objects can be changed when 901 vplsBGPADConfigRowStatus is in active(1) state." 902 VPLS Management Information Base Feb, 2014 904 INDEX { vplsConfigIndex } 905 ::= { vplsBgpADConfigTable 1 } 907 VplsBgpADConfigEntry ::= 908 SEQUENCE { 909 vplsBgpADConfigRouteDistinguisher VplsBgpRouteDistinguisher, 910 vplsBgpADConfigPrefix Unsigned32, 911 vplsBgpADConfigVplsId VplsBgpRouteDistinguisher, 912 vplsBgpADConfigRowStatus RowStatus, 913 vplsBgpADConfigStorageType StorageType 914 } 916 vplsBgpADConfigRouteDistinguisher OBJECT-TYPE 917 SYNTAX VplsBgpRouteDistinguisher 918 MAX-ACCESS read-create 919 STATUS current 920 DESCRIPTION 921 " The route distinguisher for this VPLS. See RFC4364 922 for a complete definition of a route distinguisher. 923 for more details on use of a route distinguisher 924 for a VPLS service, see RFC4761. When not configured, the 925 value is derived from the lower 6 bytes of 926 vplsBgpADConfigVplsId. 927 " 928 ::= { vplsBgpADConfigEntry 1 } 930 vplsBgpADConfigPrefix OBJECT-TYPE 931 SYNTAX Unsigned32 932 MAX-ACCESS read-create 933 STATUS current 934 DESCRIPTION 935 " In case of auto-discovery the default prefix advertised 936 is the IP address of the loopback. In case the user wants 937 to override the loopback address, vplsBgpADConfigPrefix 938 should be set. When this value is non-zero this value is 939 used along with vplsBgpADConfigRouteDistinguisher in the 940 NLRI, see RFC6074 941 " 942 DEFVAL { 0 } 943 ::= { vplsBgpADConfigEntry 2 } 945 vplsBgpADConfigVplsId OBJECT-TYPE 946 SYNTAX VplsBgpRouteDistinguisher 947 MAX-ACCESS read-create 948 STATUS current 949 DESCRIPTION 950 " VplsId is a unique identifier for all VSIs belonging to 951 VPLS Management Information Base Feb, 2014 953 the same VPLS. It is advertised as an extended community. 954 " 955 ::= { vplsBgpADConfigEntry 3 } 957 vplsBgpADConfigRowStatus OBJECT-TYPE 958 SYNTAX RowStatus 959 MAX-ACCESS read-create 960 STATUS current 961 DESCRIPTION 962 "For creating, modifying, and deleting this row. 964 All other objects in this row must be set to valid 965 values before this object can be set to active(1). 967 None of the read-create objects in the 968 conceptual rows may be changed when this 969 object is in the active(1) state." 970 ::= { vplsBgpADConfigEntry 4 } 972 vplsBgpADConfigStorageType OBJECT-TYPE 973 SYNTAX StorageType 974 MAX-ACCESS read-create 975 STATUS current 976 DESCRIPTION 977 "This variable indicates the storage type for this row." 978 DEFVAL { nonVolatile } 979 ::= { vplsBgpADConfigEntry 5 } 981 -- vplsBgpRteTargetTable 983 vplsBgpRteTargetTable OBJECT-TYPE 984 SYNTAX SEQUENCE OF VplsBgpRteTargetEntry 985 MAX-ACCESS not-accessible 986 STATUS current 987 DESCRIPTION 988 " This table specifies the list of Route Targets 989 imported or exported by BGP during 990 auto-discovery of VPLS. 991 " 992 ::= { vplsObjects 6 } 994 vplsBgpRteTargetEntry OBJECT-TYPE 995 SYNTAX VplsBgpRteTargetEntry 996 MAX-ACCESS not-accessible 997 STATUS current 998 DESCRIPTION 999 "An entry in this table specifies the value of the 1000 Route Target being used by BGP. Depending on the value 1001 of vplsBgpRteTargetType a Route Target might be 1002 VPLS Management Information Base Feb, 2014 1004 exported or imported or both. Every VPLS which 1005 uses auto-discovery for finding peer nodes can 1006 import and export multiple Route Targets. This 1007 representation allows support for hierarchical VPLS. 1009 Entries in this table may be created or deleted 1010 through SNMP, as side-effects of console or other 1011 non-SNMP management commands, or upon learning via 1012 autodiscovery. 1014 It is optional for the agent to allow entries to be 1015 created that point to non-existent entries in 1016 vplsConfigTable." 1017 INDEX { vplsConfigIndex, vplsBgpRteTargetIndex } 1018 ::= { vplsBgpRteTargetTable 1 } 1020 VplsBgpRteTargetEntry ::= 1021 SEQUENCE { 1022 vplsBgpRteTargetIndex Unsigned32, 1023 vplsBgpRteTargetRTType VplsBgpRouteTargetType, 1024 vplsBgpRteTargetRT VplsBgpRouteTarget, 1025 vplsBgpRteTargetRowStatus RowStatus, 1026 vplsBgpRteTargetStorageType StorageType 1027 } 1029 vplsBgpRteTargetIndex OBJECT-TYPE 1030 SYNTAX Unsigned32 1031 MAX-ACCESS not-accessible 1032 STATUS current 1033 DESCRIPTION 1034 "This index along with vplsConfigIndex, identifies one 1035 entry in the vplsBgpRteTargetTable. By keeping 1036 vplsConfigIndex constant and using new value of 1037 vplsBgpRteTargetIndex users can configure multiple 1038 Route Targets for the same VPLS. 1039 " 1040 ::= { vplsBgpRteTargetEntry 1 } 1042 vplsBgpRteTargetRTType OBJECT-TYPE 1043 SYNTAX VplsBgpRouteTargetType 1044 MAX-ACCESS read-create 1045 STATUS current 1046 DESCRIPTION 1047 " Used to define the type of a route target usage. 1048 Route targets can be specified to be imported, 1049 exported, or both. For a complete definition of a 1050 route target, see RFC4364." 1051 ::= { vplsBgpRteTargetEntry 2 } 1052 VPLS Management Information Base Feb, 2014 1054 vplsBgpRteTargetRT OBJECT-TYPE 1055 SYNTAX VplsBgpRouteTarget 1056 MAX-ACCESS read-create 1057 STATUS current 1058 DESCRIPTION 1059 " The route target associated with the VPLS service. 1060 For more details on use of route targets 1061 for a VPLS service, see RFC4761. 1062 " 1063 ::= { vplsBgpRteTargetEntry 3 } 1065 vplsBgpRteTargetRowStatus OBJECT-TYPE 1066 SYNTAX RowStatus 1067 MAX-ACCESS read-create 1068 STATUS current 1069 DESCRIPTION 1070 "This variable is used to create, modify, and/or 1071 delete a row in this table. 1073 All other objects in this row must be set to valid 1074 values before this object can be set to active(1). 1076 When a row in this table is in active(1) state, no 1077 objects in that row can be modified. 1079 If autodiscovered entries are deleted they would 1080 likely re-appear in the next autodiscovery interval." 1081 ::= { vplsBgpRteTargetEntry 4 } 1083 vplsBgpRteTargetStorageType OBJECT-TYPE 1084 SYNTAX StorageType 1085 MAX-ACCESS read-create 1086 STATUS current 1087 DESCRIPTION 1088 "This variable indicates the storage type for this row." 1089 DEFVAL { volatile } 1090 ::= { vplsBgpRteTargetEntry 5 } 1092 vplsStatusNotifEnable OBJECT-TYPE 1093 SYNTAX TruthValue 1094 MAX-ACCESS read-write 1095 STATUS current 1096 DESCRIPTION 1097 "If this object is set to true(1), then it enables 1098 the emission of vplsStatusChanged 1099 notification, otherwise this notification is not 1100 VPLS Management Information Base Feb, 2014 1102 emitted." 1103 REFERENCE 1104 "See also RFC3413 for explanation that 1105 notifications are under the ultimate control of the 1106 MIB module in this document." 1107 DEFVAL { false } 1108 ::= { vplsObjects 7 } 1110 vplsNotificationMaxRate OBJECT-TYPE 1111 SYNTAX Unsigned32 1112 MAX-ACCESS read-write 1113 STATUS current 1114 DESCRIPTION 1115 "This object indicates the maximum number of 1116 notifications issued per second. If events occur 1117 more rapidly, the implementation may simply fail to 1118 emit these notifications during that period, or may 1119 queue them until an appropriate time. A value of 0 1120 means no throttling is applied and events may be 1121 notified at the rate at which they occur." 1122 DEFVAL { 0 } 1123 ::= { vplsObjects 8 } 1124 -- VPLS Service Notifications 1126 vplsStatusChanged NOTIFICATION-TYPE 1127 OBJECTS { 1128 vplsConfigVpnId, 1129 vplsConfigAdminStatus, 1130 vplsStatusOperStatus 1131 } 1132 STATUS current 1133 DESCRIPTION 1134 "The vplsStatusChanged notification is generated 1135 when there is a change in the administrative or 1136 operating status of a VPLS service. 1138 The object instances included in the notification 1139 are the ones associated with the VPLS service 1140 whose status has changed." 1141 ::= { vplsNotifications 1 } 1143 vplsFwdFullAlarmRaised NOTIFICATION-TYPE 1144 OBJECTS { 1145 vplsConfigVpnId, 1146 vplsConfigFwdFullHighWatermark, 1147 vplsConfigFwdFullLowWatermark 1148 } 1149 STATUS current 1150 VPLS Management Information Base Feb, 2014 1152 DESCRIPTION 1153 "The vplsFwdFullAlarmRaised notification is 1154 generated when the utilization of the Forwarding 1155 database is above the value specified by 1156 vplsConfigFwdFullHighWatermark. 1157 The object instances included in the notification 1158 are the ones associated with the VPLS service 1159 which has exceeded the threshold." 1160 ::= { vplsNotifications 2 } 1162 vplsFwdFullAlarmCleared NOTIFICATION-TYPE 1163 OBJECTS { 1164 vplsConfigVpnId, 1165 vplsConfigFwdFullHighWatermark, 1166 vplsConfigFwdFullLowWatermark 1167 } 1168 STATUS current 1169 DESCRIPTION 1170 "The vplsFwdFullAlarmCleared notification is 1171 generated when the utilization of the Forwarding 1172 database is below the value specified by 1173 vplsConfigFwdFullLowWatermark. 1175 The object instances included in the notification 1176 are the ones associated with the VPLS service 1177 which has fallen below the threshold." 1178 ::= { vplsNotifications 3 } 1180 -- Conformance Section 1182 vplsCompliances 1183 OBJECT IDENTIFIER ::= { vplsConformance 1 } 1184 -- Compliance requirement for fully compliant implementations 1186 vplsModuleFullCompliance MODULE-COMPLIANCE 1187 STATUS current 1188 DESCRIPTION 1189 "Compliance requirement for implementations that 1190 provide full support for VPLS-GENERIC-MIB. 1191 Such devices can then be monitored and configured using 1192 this MIB module." 1193 MODULE -- this module 1195 MANDATORY-GROUPS { 1196 vplsGroup, 1197 vplsPwBindGroup, 1198 vplsNotificationGroup 1199 } 1200 VPLS Management Information Base Feb, 2014 1202 ::= { vplsCompliances 1 } 1204 -- Compliance requirement for read-only implementations. 1206 vplsModuleReadOnlyCompliance MODULE-COMPLIANCE 1207 STATUS current 1208 DESCRIPTION 1209 "Compliance requirement for implementations that only 1210 provide read-only support for VPLS-GENERIC-MIB. 1211 Such devices can then be monitored but cannot be 1212 configured using this MIB modules." 1214 MODULE -- this module 1216 MANDATORY-GROUPS { 1217 vplsGroup, 1218 vplsPwBindGroup, 1219 vplsNotificationGroup 1220 } 1222 OBJECT vplsConfigName 1223 MIN-ACCESS read-only 1224 DESCRIPTION 1225 "Write access is not required." 1227 OBJECT vplsConfigDescr 1228 MIN-ACCESS read-only 1229 DESCRIPTION 1230 "Write access is not required." 1232 OBJECT vplsConfigAdminStatus 1233 MIN-ACCESS read-only 1234 DESCRIPTION 1236 "Write access is not required." 1238 OBJECT vplsConfigMacLearning 1239 MIN-ACCESS read-only 1240 DESCRIPTION 1241 "Write access is not required." 1243 OBJECT vplsConfigDiscardUnknownDest 1244 MIN-ACCESS read-only 1245 DESCRIPTION 1246 "Write access is not required." 1248 VPLS Management Information Base Feb, 2014 1250 OBJECT vplsConfigMacAging 1251 MIN-ACCESS read-only 1252 DESCRIPTION 1253 "Write access is not required." 1255 OBJECT vplsConfigFwdFullHighWatermark 1256 MIN-ACCESS read-only 1257 DESCRIPTION 1259 "Write access is not required." 1261 OBJECT vplsConfigFwdFullLowWatermark 1262 MIN-ACCESS read-only 1263 DESCRIPTION 1264 "Write access is not required." 1266 OBJECT vplsConfigRowStatus 1267 MIN-ACCESS read-only 1268 DESCRIPTION 1269 "Write access is not required." 1271 OBJECT vplsConfigMtu 1272 MIN-ACCESS read-only 1273 DESCRIPTION 1274 "Write access is not required." 1276 OBJECT vplsPwBindConfigType 1277 MIN-ACCESS read-only 1278 DESCRIPTION 1279 "Write access is not required." 1281 OBJECT vplsPwBindType 1282 MIN-ACCESS read-only 1283 DESCRIPTION 1284 "Write access is not required." 1286 OBJECT vplsPwBindRowStatus 1287 MIN-ACCESS read-only 1288 DESCRIPTION 1289 "Write access is not required." 1291 ::= { vplsCompliances 2 } 1293 -- Units of conformance. 1295 vplsGroups 1296 OBJECT IDENTIFIER ::= { vplsConformance 2 } 1297 VPLS Management Information Base Feb, 2014 1299 vplsGroup OBJECT-GROUP 1300 OBJECTS { 1301 vplsConfigName, 1302 vplsBgpADConfigRouteDistinguisher, 1303 vplsBgpRteTargetRTType, 1304 vplsBgpRteTargetRT, 1305 vplsBgpRteTargetRowStatus, 1306 vplsBgpRteTargetStorageType, 1307 vplsBgpADConfigPrefix, 1308 vplsBgpADConfigVplsId, 1309 vplsBgpADConfigRowStatus, 1310 vplsBgpADConfigStorageType, 1311 vplsConfigDescr, 1312 vplsConfigAdminStatus, 1313 vplsConfigMacLearning, 1314 vplsConfigDiscardUnknownDest, 1315 vplsConfigMacAging, 1316 vplsConfigVpnId, 1317 vplsConfigFwdFullHighWatermark, 1318 vplsConfigFwdFullLowWatermark, 1319 vplsConfigRowStatus, 1320 vplsConfigIndexNext, 1321 vplsConfigMtu, 1322 vplsConfigStorageType, 1323 vplsConfigSignalingType, 1324 vplsStatusOperStatus, 1325 vplsStatusPeerCount, 1326 vplsStatusNotifEnable, 1327 vplsNotificationMaxRate 1328 } 1329 STATUS current 1330 DESCRIPTION 1331 "The group of objects supporting 1332 management of L2VPN VPLS services" 1333 ::= { vplsGroups 1 } 1335 vplsPwBindGroup OBJECT-GROUP 1336 OBJECTS { 1337 vplsPwBindConfigType, 1338 vplsPwBindType, 1339 vplsPwBindRowStatus, 1340 vplsPwBindStorageType 1341 } 1342 STATUS current 1343 DESCRIPTION 1344 "The group of objects supporting 1345 management of 1347 VPLS Management Information Base Feb, 2014 1349 Pseudo Wire (PW) Binding to VPLS." 1350 ::= { vplsGroups 2 } 1352 vplsNotificationGroup NOTIFICATION-GROUP 1353 NOTIFICATIONS { 1354 vplsStatusChanged, 1355 vplsFwdFullAlarmRaised, 1356 vplsFwdFullAlarmCleared 1357 } 1358 STATUS current 1359 DESCRIPTION 1360 "The group of notifications supporting 1361 the Notifications generated for 1362 VPLS Services" 1363 ::= { vplsGroups 3 } 1365 END 1367 6.2. VPLS-LDP-MIB Object definitions 1369 This MIB module makes references to the following documents. 1370 [RFC2578], [RFC2579], [RFC2580], [RFC3411], 1371 [RFC2863], [RFC4265] and [RFC3813]. 1373 VPLS-LDP-MIB DEFINITIONS ::= BEGIN 1375 IMPORTS 1376 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 1377 Unsigned32, transmission 1378 FROM SNMPv2-SMI -- RFC2578 1380 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 1381 FROM SNMPv2-CONF -- RFC2580 1383 TruthValue 1384 FROM SNMPv2-TC -- RFC2579 1385 pwIndex, pwID 1386 FROM PW-STD-MIB 1388 vplsConfigIndex, vplsConfigName 1389 FROM VPLS-GENERIC-MIB; 1391 vplsLdpDraft01MIB MODULE-IDENTITY 1392 -- RFC Editor: Please replace vplsLdpDraft01MIB with 1393 -- vplsLdpMIB throughout the MIB and remove 1394 -- this note. 1396 VPLS Management Information Base Feb, 2014 1398 LAST-UPDATED "201401301200Z" -- 30 Jan 2014 12:00:00 GMT 1399 ORGANIZATION "Layer 2 Virtual Private Networks (L2VPN) 1400 Working Group" 1401 CONTACT-INFO 1402 " 1403 Rohit Mediratta 1404 Email: Rohit.mediratta@alcatel-lucent.com 1406 The L2VPN Working Group 1407 (email distribution l2vpn@ietf.org, 1408 http://www.ietf.org/html.charters/l2vpn-charter.html) 1409 " 1411 DESCRIPTION 1412 "Copyright (C) The IETF Trust (2014). The initial 1413 version of this MIB module was published in RFC XXXX. 1415 -- RFC Editor: Please replace XXXX with RFC number & remove 1416 -- this note. 1418 For full legal notices see the RFC itself or see: 1419 http://www.ietf.org/copyrights/ianamib.html 1421 This MIB module contains managed object definitions for 1422 LDP signaled Virtual Private LAN Services as in 1423 RFC4762 1425 This MIB module enables the use of any 1426 underlying pseudowire network. " 1428 -- Revision history. 1429 REVISION 1430 "201401230200Z" -- 30 Jan 2014 12:00:00 GMT 1432 DESCRIPTION "Initial version published as part of RFC YYYY." 1433 -- RFC Editor: please replace YYYY with IANA assigned value, and 1434 -- delete this note. 1436 ::= { transmission BBB } 1437 -- RFC Editor: please replace BBB with IANA assigned value, and 1438 -- delete this note. 1440 -- Top-level components of this MIB. 1441 -- Notifications 1442 VPLS Management Information Base Feb, 2014 1444 vplsLdpNotifications OBJECT IDENTIFIER 1445 ::= { vplsLdpDraft01MIB 0 } 1447 -- Tables, Scalars 1448 vplsLdpObjects OBJECT IDENTIFIER 1449 ::= { vplsLdpDraft01MIB 1 } 1450 -- Conformance 1451 vplsLdpConformance OBJECT IDENTIFIER 1452 ::= { vplsLdpDraft01MIB 2 } 1454 vplsLdpConfigTable OBJECT-TYPE 1455 SYNTAX SEQUENCE OF VplsLdpConfigEntry 1456 MAX-ACCESS not-accessible 1457 STATUS current 1458 DESCRIPTION 1459 "This table specifies information for configuring 1460 and monitoring LDP specific parameters for 1461 Virtual Private Lan Services (VPLS)." 1462 ::= { vplsLdpObjects 1 } 1464 vplsLdpConfigEntry OBJECT-TYPE 1465 SYNTAX VplsLdpConfigEntry 1466 MAX-ACCESS not-accessible 1467 STATUS current 1468 DESCRIPTION 1469 "A row in this table represents LDP specific information 1470 for Virtual Private Lan Services (VPLS) in a packet 1471 network. It is indexed by vplsConfigIndex, which uniquely 1472 identifies a single VPLS. 1474 A row is automatically created when a VPLS service is 1475 configured using LDP signaling. 1477 All of the writable objects values can be 1478 changed when vplsConfigRowStatus is in the active(1) 1479 state. 1480 " 1481 INDEX { vplsConfigIndex } 1482 ::= { vplsLdpConfigTable 1 } 1483 VPLS Management Information Base Feb, 2014 1485 VplsLdpConfigEntry ::= 1486 SEQUENCE { 1487 vplsLdpConfigMacAddrWithdraw TruthValue 1488 } 1490 vplsLdpConfigMacAddrWithdraw OBJECT-TYPE 1491 SYNTAX TruthValue 1492 MAX-ACCESS read-write 1493 STATUS current 1494 DESCRIPTION 1495 "This object specifies if MAC address withdrawal 1496 is enabled in this service. If this object is true 1497 then MAC address withdrawal is enabled. If false, 1498 then MAC address withdrawal is disabled." 1499 DEFVAL { true } 1500 ::= { vplsLdpConfigEntry 1 } 1502 -- VPLS LDP PW Binding Table 1504 vplsLdpPwBindTable OBJECT-TYPE 1505 SYNTAX SEQUENCE OF VplsLdpPwBindEntry 1506 MAX-ACCESS not-accessible 1507 STATUS current 1508 DESCRIPTION 1509 "This table provides LDP specific information for 1510 an association between a VPLS service and the 1511 corresponding pseudowires. A service can have more 1512 than one pseudowire association. Pseudowires are 1513 defined in the pwTable." 1514 ::= { vplsLdpObjects 2 } 1516 vplsLdpPwBindEntry OBJECT-TYPE 1517 SYNTAX VplsLdpPwBindEntry 1518 MAX-ACCESS not-accessible 1519 STATUS current 1520 DESCRIPTION 1521 "Each row represents an association between a 1522 VPLS instance and one or more pseudowires 1523 defined in the pwTable. Each index is unique 1524 in describing an entry in this table. However 1525 both indexes are required to define the one 1526 to many association of service to pseudowire. 1528 An entry in this table in instantiated only when 1529 LDP signaling is used to configure VPLS service. 1531 Each entry in this table provides LDP specific 1532 information for the VPLS represented by 1534 VPLS Management Information Base Feb, 2014 1536 vplsConfigIndex." 1537 INDEX { vplsConfigIndex, pwIndex } 1538 ::= { vplsLdpPwBindTable 1 } 1540 VplsLdpPwBindEntry ::= 1541 SEQUENCE { 1542 vplsLdpPwBindMacAddressLimit Unsigned32 1543 } 1545 vplsLdpPwBindMacAddressLimit OBJECT-TYPE 1546 SYNTAX Unsigned32 (0..4294967295) 1547 MAX-ACCESS read-write 1548 STATUS current 1549 DESCRIPTION 1550 "The value of this object specifies the maximum 1551 number of learned and static entries allowed in the 1552 Forwarding database for this PW Binding. The value 0 1553 means there is no limit for this PW Binding." 1554 DEFVAL { 0 } 1555 ::= { vplsLdpPwBindEntry 1 } 1557 -- VPLS LDP Service Notifications 1559 vplsLdpPwBindMacTableFull NOTIFICATION-TYPE 1560 OBJECTS { 1561 vplsConfigName, 1562 pwID 1563 } 1564 STATUS current 1565 DESCRIPTION 1566 "The vplsLdpPwBindMacTableFull notification is generated 1567 when the number of learned MAC-Addresses increases to 1568 the value specified in vplsLdpPwBindMacAddressLimit." 1569 ::= { vplsLdpNotifications 1 } 1571 -- Conformance Section 1573 vplsLdpCompliances 1574 OBJECT IDENTIFIER ::= { vplsLdpConformance 1 } 1576 -- Compliance requirement for fully compliant implementations 1578 vplsLdpModuleFullCompliance MODULE-COMPLIANCE 1579 STATUS current 1580 DESCRIPTION 1581 "Compliance requirement for implementations that 1582 VPLS Management Information Base Feb, 2014 1584 provide full support for VPLS-LDP-MIB. 1585 Such devices can then be monitored and configured using 1586 this MIB module." 1588 MODULE -- this module 1590 MANDATORY-GROUPS { 1591 vplsLdpGroup, 1592 vplsLdpNotificationGroup 1593 } 1595 ::= { vplsLdpCompliances 1 } 1597 -- Compliance requirement for read-only implementations. 1599 vplsLdpModuleReadOnlyCompliance MODULE-COMPLIANCE 1600 STATUS current 1601 DESCRIPTION 1602 "Compliance requirement for implementations that only 1603 provide read-only support for VPLS-LDP-MIB. 1604 Such devices can then be monitored but cannot be 1605 configured using this MIB modules." 1607 MODULE -- this module 1609 MANDATORY-GROUPS { 1610 vplsLdpGroup, 1611 vplsLdpNotificationGroup 1612 } 1614 OBJECT vplsLdpConfigMacAddrWithdraw 1615 MIN-ACCESS read-only 1616 DESCRIPTION 1617 "Write access is not required." 1619 OBJECT vplsLdpPwBindMacAddressLimit 1620 MIN-ACCESS read-only 1621 DESCRIPTION 1622 "Write access is not required." 1624 ::= { vplsLdpCompliances 2 } 1626 -- Units of conformance. 1628 vplsLdpGroups 1629 OBJECT IDENTIFIER ::= { vplsLdpConformance 2 } 1630 VPLS Management Information Base Feb, 2014 1632 vplsLdpGroup OBJECT-GROUP 1633 OBJECTS { 1634 vplsLdpConfigMacAddrWithdraw, 1635 vplsLdpPwBindMacAddressLimit 1636 } 1637 STATUS current 1638 DESCRIPTION 1639 "The group of objects supporting 1640 management of L2VPN VPLS services using LDP." 1641 ::= { vplsLdpGroups 1 } 1643 vplsLdpNotificationGroup NOTIFICATION-GROUP 1644 NOTIFICATIONS { 1645 vplsLdpPwBindMacTableFull 1647 } 1648 STATUS current 1649 DESCRIPTION 1650 "The group of notifications supporting 1651 the Notifications generated for 1652 VPLS Ldp Service" 1653 ::= { vplsLdpGroups 2 } 1655 END 1657 6.3. VPLS-BGP-MIB Object definitions 1659 VPLS-BGP-MIB DEFINITIONS ::= BEGIN 1661 IMPORTS 1662 MODULE-IDENTITY, OBJECT-TYPE, 1663 Unsigned32, transmission 1664 FROM SNMPv2-SMI -- RFC2578 1666 MODULE-COMPLIANCE, OBJECT-GROUP 1667 FROM SNMPv2-CONF -- RFC2580 1669 RowStatus, StorageType 1670 FROM SNMPv2-TC -- RFC2579 1672 SnmpAdminString 1673 FROM SNMP-FRAMEWORK-MIB -- RFC3411 1675 pwIndex 1676 FROM PW-STD-MIB -- RFC5601 1678 vplsConfigIndex 1679 VPLS Management Information Base Feb, 2014 1681 FROM VPLS-GENERIC-MIB 1682 ; 1684 vplsBgpDraft01MIB MODULE-IDENTITY 1685 -- RFC Editor: Please replace vplsBgpDraft01MIB with 1686 -- vplsBgpMIB throughout the MIB and remove 1687 -- this note. 1688 LAST-UPDATED "201401301200Z" -- 30 Jan 2014 12:00:00 GMT 1689 ORGANIZATION "Layer 2 Virtual Private Networks (L2VPN) 1690 Working Group" 1691 CONTACT-INFO 1693 " 1694 V. J. Shah 1695 Email: vshah@juniper.net 1697 The L2VPN Working Group (email distribution l2vpn@ietf.org, 1698 http://www.ietf.org/html.charters/l2vpn-charter.html) 1699 " 1701 DESCRIPTION 1702 "Copyright (C) The IETF Trust (2014). The initial 1703 version of this MIB module was published in RFC XXXX. 1704 -- RFC Editor: Please replace XXXX with RFC number & remove 1705 -- this note. 1707 For full legal notices see the RFC itself or see: 1708 http://www.ietf.org/copyrights/ianamib.html 1710 This MIB module contains managed object definitions for 1711 BGP signaled Virtual Private LAN Services as in 1712 RFC4761 1714 This MIB module enables the use of any underlying 1715 pseudowire network. " 1717 -- Revision history. 1718 REVISION 1719 "201401301200Z" -- 30 Jan 2014 12:00:00 GMT 1720 DESCRIPTION "Initial version published as part of RFC YYYY." 1721 -- RFC Editor: please replace YYYY with IANA assigned value, and 1722 -- delete this note. 1723 ::= { transmission CCC } 1724 -- RFC Editor: please replace CCC with IANA assigned value, and 1725 -- delete this note. 1727 -- Top-level components of this MIB. 1729 VPLS Management Information Base Feb, 2014 1731 -- Tables, Scalars 1732 vplsBgpObjects OBJECT IDENTIFIER 1733 ::= { vplsBgpDraft01MIB 1 } 1734 -- Conformance 1735 vplsBgpConformance OBJECT IDENTIFIER 1736 ::= { vplsBgpDraft01MIB 2 } 1738 -- Vpls Bgp Config Table 1740 vplsBgpConfigTable OBJECT-TYPE 1741 SYNTAX SEQUENCE OF VplsBgpConfigEntry 1742 MAX-ACCESS not-accessible 1743 STATUS current 1744 DESCRIPTION 1745 "This table specifies information for configuring 1746 and monitoring BGP specific parameters for 1747 Virtual Private LAN Services (VPLS)." 1748 ::= { vplsBgpObjects 1 } 1750 vplsBgpConfigEntry OBJECT-TYPE 1751 SYNTAX VplsBgpConfigEntry 1752 MAX-ACCESS not-accessible 1753 STATUS current 1754 DESCRIPTION 1755 "A row in this table represents BGP specific information 1756 for Virtual Private LAN Services (VPLS) in a packet 1757 network. It is indexed by vplsConfigIndex, which uniquely 1758 identifies a single instance of a VPLS service. 1760 A row is automatically created when a VPLS service is 1761 created that is configured to use BGP signaling. 1762 All of the writable objects values can be 1763 changed when vplsConfigRowStatus is in the active(1) 1764 state. 1765 " 1766 INDEX { vplsConfigIndex } 1767 ::= { vplsBgpConfigTable 1 } 1769 VplsBgpConfigEntry ::= 1770 VPLS Management Information Base Feb, 2014 1772 SEQUENCE { 1773 vplsBgpConfigVERangeSize Unsigned32 1774 } 1776 vplsBgpConfigVERangeSize OBJECT-TYPE 1777 SYNTAX Unsigned32 (0..65535) 1778 MAX-ACCESS read-write 1779 STATUS current 1780 DESCRIPTION 1781 "Specifies the size of the range of VE ID in this 1782 VPLS service. This number controls the size of the 1783 label block advertised for this VE by the PE. 1784 A value of 0 indicates that the range is not 1785 configured and the PE derives the range value 1786 from received advertisements from other PEs. 1788 The VE ID takes 2 octets in VPLS BGP NLRI according 1789 to RFC 4761. Hence we have limited the the range of 1790 this object to 65535." 1791 DEFVAL { 0 } 1792 ::= { vplsBgpConfigEntry 1 } 1794 -- Vpls Edge Device (VE) Identifier Table 1796 vplsBgpVETable OBJECT-TYPE 1797 SYNTAX SEQUENCE OF VplsBgpVEEntry 1798 MAX-ACCESS not-accessible 1799 STATUS current 1800 DESCRIPTION 1801 "This table associates VPLS Edge devices to a VPLS service" 1802 ::= { vplsBgpObjects 2 } 1804 vplsBgpVEEntry OBJECT-TYPE 1805 SYNTAX VplsBgpVEEntry 1806 MAX-ACCESS not-accessible 1807 STATUS current 1808 DESCRIPTION 1809 "An entry in this table is created for each VE Id 1810 configured on a PE for a particular VPLS service 1811 instance. 1813 Entries in this table may be created or deleted 1814 through SNMP, as side-effects of console or other 1815 non-SNMP management commands, or upon learning via 1816 autodiscovery. 1818 It is optional for the agent to allow entries to be 1819 created that point to non-existent entries in 1820 vplsConfigTable." 1821 INDEX { vplsConfigIndex, vplsBgpVEId } 1822 ::= { vplsBgpVETable 1 } 1823 VPLS Management Information Base Feb, 2014 1825 VplsBgpVEEntry ::= SEQUENCE { 1826 vplsBgpVEId Unsigned32, 1827 vplsBgpVEName SnmpAdminString, 1828 vplsBgpVEPreference Unsigned32, 1829 vplsBgpVERowStatus RowStatus, 1830 vplsBgpVEStorageType StorageType 1831 } 1833 vplsBgpVEId OBJECT-TYPE 1834 SYNTAX Unsigned32 (1..65535) 1835 MAX-ACCESS not-accessible 1836 STATUS current 1837 DESCRIPTION 1838 "A secondary index identifying a VE within an 1839 instance of a VPLS service. 1840 The VE ID takes 2 octets in VPLS BGP NLRI according 1841 to RFC 4761. Hence we have limited the the range of 1842 this object to 65535." 1843 ::= { vplsBgpVEEntry 1 } 1845 vplsBgpVEName OBJECT-TYPE 1846 SYNTAX SnmpAdminString 1847 MAX-ACCESS read-create 1848 STATUS current 1849 DESCRIPTION 1850 "Descriptive name for the site or u-PE associated with 1851 this VE Id." 1852 DEFVAL { "" } 1853 ::= { vplsBgpVEEntry 2 } 1855 vplsBgpVEPreference OBJECT-TYPE 1856 SYNTAX Unsigned32 (0..65535) 1857 MAX-ACCESS read-create 1858 STATUS current 1859 DESCRIPTION 1860 "Specifies the preference of the VE Id on this PE 1861 if the site is multi-homed and VE Id is re-used." 1862 DEFVAL { 0 } 1863 ::= { vplsBgpVEEntry 3 } 1865 vplsBgpVERowStatus OBJECT-TYPE 1866 SYNTAX RowStatus 1867 MAX-ACCESS read-create 1868 STATUS current 1869 DESCRIPTION 1870 "This variable is used to create, modify, and/or 1871 delete a row in this table. 1873 All other objects in this row must be set to valid 1874 values before this object can be set to active(1). 1876 VPLS Management Information Base Feb, 2014 1878 When a row in this table is in active(1) state, no 1879 objects in that row can be modified except 1880 vplsBgpSiteRowStatus." 1881 ::= { vplsBgpVEEntry 5 } 1883 vplsBgpVEStorageType OBJECT-TYPE 1884 SYNTAX StorageType 1885 MAX-ACCESS read-create 1886 STATUS current 1887 DESCRIPTION 1888 "This variable indicates the storage type for this 1889 row." 1890 DEFVAL { volatile } 1891 ::= { vplsBgpVEEntry 6 } 1893 -- VPLS BGP PW Binding Table 1895 vplsBgpPwBindTable OBJECT-TYPE 1896 SYNTAX SEQUENCE OF VplsBgpPwBindEntry 1897 MAX-ACCESS not-accessible 1898 STATUS current 1899 DESCRIPTION 1900 "This table provides BGP specific information for 1901 an association between a VPLS service and the 1902 corresponding pseudowires. A service can have more 1903 than one pseudowire association. Pseudowires are 1904 defined in the pwTable." 1905 ::= { vplsBgpObjects 3 } 1907 vplsBgpPwBindEntry OBJECT-TYPE 1908 SYNTAX VplsBgpPwBindEntry 1909 MAX-ACCESS not-accessible 1910 STATUS current 1911 DESCRIPTION 1912 "Each row represents an association between a 1913 VPLS instance and one or more Pseudowires 1914 defined in the pwTable. Each index is unique 1915 in describing an entry in this table. However 1916 both indexes are required to define the one 1917 to many association of service to pseudowire. 1919 An entry in this table in instantiated only when 1920 BGP signaling is used to configure VPLS service. 1922 Each entry in this table provides BGP specific 1923 information for the VPlS represented by 1924 vplsConfigIndex." 1925 INDEX { vplsConfigIndex, pwIndex } 1926 ::= { vplsBgpPwBindTable 1 } 1927 VPLS Management Information Base Feb, 2014 1929 VplsBgpPwBindEntry ::= 1930 SEQUENCE { 1931 vplsBgpPwBindLocalVEId Unsigned32, 1932 vplsBgpPwBindRemoteVEId Unsigned32 1933 } 1934 vplsBgpPwBindLocalVEId OBJECT-TYPE 1935 SYNTAX Unsigned32 (1..65535) 1936 MAX-ACCESS read-only 1937 STATUS current 1938 DESCRIPTION 1939 "Identifies the local VE that this pseudowire 1940 is associated with. 1941 The VE ID takes 2 octets in VPLS BGP NLRI according 1942 to RFC 4761. Hence we have limited the the range of 1943 this object to 65535." 1944 ::= { vplsBgpPwBindEntry 1 } 1946 vplsBgpPwBindRemoteVEId OBJECT-TYPE 1947 SYNTAX Unsigned32 (1..65535) 1948 MAX-ACCESS read-only 1949 STATUS current 1950 DESCRIPTION 1951 "Identifies the remote VE that this pseudowire 1952 is associated with. 1953 The VE ID takes 2 octets in VPLS BGP NLRI according 1954 to RFC 4761. Hence we have limited the the range of 1955 this object to 65535." 1956 ::= { vplsBgpPwBindEntry 2 } 1958 -- Conformance Section 1960 -- Compliance requirement for fully compliant implementations 1962 vplsBgpCompliances 1963 OBJECT IDENTIFIER ::= { vplsBgpConformance 1 } 1965 vplsBgpModuleFullCompliance MODULE-COMPLIANCE 1966 STATUS current 1967 DESCRIPTION 1968 "Compliance requirement for implementations that 1969 provide full support for VPLS-BGP-MIB. 1970 Such devices can then be monitored and configured using 1971 this MIB module." 1973 MODULE -- this module 1975 MANDATORY-GROUPS { 1976 vplsBgpConfigGroup, 1977 vplsBgpVEGroup, 1978 vplsBgpPwBindGroup 1980 VPLS Management Information Base Feb, 2014 1982 } 1983 ::= { vplsBgpCompliances 1 } 1985 -- Compliance requirement for read-only implementations. 1987 vplsBgpModuleReadOnlyCompliance MODULE-COMPLIANCE 1988 STATUS current 1989 DESCRIPTION 1990 "Compliance requirement for implementations that only 1991 provide read-only support for VPLS-BGP-MIB. 1992 Such devices can then be monitored but cannot be 1993 configured using this MIB modules." 1995 MODULE -- this module 1997 MANDATORY-GROUPS { 1998 vplsBgpConfigGroup, 1999 vplsBgpVEGroup, 2000 vplsBgpPwBindGroup 2001 } 2003 OBJECT vplsBgpConfigVERangeSize 2004 MIN-ACCESS read-only 2005 DESCRIPTION 2006 "Write access is not required." 2008 OBJECT vplsBgpVEName 2009 MIN-ACCESS read-only 2010 DESCRIPTION 2011 "Write access is not required." 2013 OBJECT vplsBgpVEPreference 2014 MIN-ACCESS read-only 2015 DESCRIPTION 2016 "Write access is not required." 2018 OBJECT vplsBgpVERowStatus 2019 MIN-ACCESS read-only 2020 DESCRIPTION 2021 "Write access is not required." 2023 ::= { vplsBgpCompliances 2 } 2025 -- Units of conformance. 2027 vplsBgpGroups 2028 VPLS Management Information Base Feb, 2014 2030 OBJECT IDENTIFIER ::= { vplsBgpConformance 2 } 2032 vplsBgpConfigGroup OBJECT-GROUP 2033 OBJECTS { 2034 vplsBgpConfigVERangeSize 2035 } 2036 STATUS current 2037 DESCRIPTION 2038 "The group of objects supporting configuration 2039 of L2VPN VPLS services using BGP" 2040 ::= { vplsBgpGroups 1 } 2042 vplsBgpVEGroup OBJECT-GROUP 2043 OBJECTS { 2044 vplsBgpVEName, 2045 vplsBgpVEPreference, 2046 vplsBgpVERowStatus, 2047 vplsBgpVEStorageType 2048 } 2049 STATUS current 2050 DESCRIPTION 2051 "The group of objects supporting management of VPLS 2052 Edge devices for L2VPN VPLS services using BGP" 2053 ::= { vplsBgpGroups 2 } 2055 vplsBgpPwBindGroup OBJECT-GROUP 2056 OBJECTS { 2057 vplsBgpPwBindLocalVEId, 2058 vplsBgpPwBindRemoteVEId 2059 } 2060 STATUS current 2061 DESCRIPTION 2062 "The group of objects supporting management of 2063 Pseudo Wires for L2VPN VPLS services using BGP" 2064 ::= { vplsBgpGroups 3 } 2066 END 2068 7. Security Considerations 2070 There are a number of management objects defined in this MIB 2071 module with a MAX-ACCESS clause of read-write and/or read-create. 2072 Such objects may be considered sensitive or vulnerable in some 2073 network environments.The support for SET operations in a 2074 non-secure environment without proper protection can have a 2075 negative effect on network operations. These are the tables 2076 and their sensitivity/vulnerability: 2078 VPLS Management Information Base Feb, 2014 2079 o vplsConfigTable: 2080 o vplsPwBindTable: 2081 o vplsBgpADConfigTable: 2082 o vplsBgpRteTargetTable: 2083 o vplsLdpPwBindTable: 2084 o vplsLdpConfigTable: 2085 o vplsBgpConfigTable: 2086 o vplsBgpVETable: 2087 These tables contain read-create/read-write objects which 2088 can be used to configure or modify a LDP/BGP VPLS service. 2089 Any improper configuration or modification of objects in 2090 these tables can disrupt VPLS services. 2091 The use of stronger mechanisms such as SNMPv3 security 2092 should be considered where possible for configuring these 2093 objects. Specifically, SNMPv3 VACM and USM MUST be used 2094 with any v3 agent which provides SET access to these tables. 2096 o vplsNotificationMaxRate 2097 Setting of a very high value to this object can cause a 2098 notification storm which may disrupt network service. 2100 Most of the readable objects in this MIB module (i.e., objects 2101 with a MAX-ACCESS other than not-accessible) may be considered 2102 sensitive or vulnerable in some network environments.It is 2103 thus important to control even GET and/or NOTIFY access to these 2104 objects and possibly to even encrypt the values of these objects 2105 when sending them over the network via SNMP. 2107 SNMP versions prior to SNMPv3 did not include adequate security. 2108 Even if the network itself is secure (for example by using 2109 IPsec), there is no control as to who on the secure network 2110 is allowed to access and GET/SET (read/change/create/delete) 2111 the objects in this MIB module. 2113 Implementations SHOULD provide the security features described 2114 by the SNMPv3 framework (see [RFC3410]), and implementations 2115 claiming compliance to the SNMPv3 standard MUST include full 2116 support for authentication and privacy via the User-based Security 2117 Model (USM) [RFC3414] with the AES cipher algorithm [RFC3826]. 2118 Implementations MAY also provide support for the Transport Security 2119 Model (TSM) [RFC5591] in combination with a secure transport such 2120 as SSH [RFC5592] or TLS/DTLS [RFC6353]. 2122 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2123 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2124 enable cryptographic security. It is then a customer/operator 2125 responsibility to ensure that the SNMP entity giving access to an 2126 instance of this MIB module is properly configured to give access 2127 to the objects only to those principals (users) that have 2128 legitimate rights to indeed GET or SET (change/create/delete) them. 2130 VPLS Management Information Base Feb, 2014 2132 8. IANA Considerations 2134 The MIB modules in this document uses the following IANA-assigned 2135 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 2136 8.1. IANA Considerations for VPLS-GENERIC-MIB 2137 The IANA is requested to assign { transmission AAA } to the 2138 VPLS-GENERIC-MIB module specified in this document. 2139 8.2. IANA Considerations for VPLS-LDP-MIB 2140 The IANA is requested to assign { transmission BBB } to the 2141 VPLS-LDP-MIB module specified in this document. 2142 8.3. IANA Considerations for VPLS-BGP-MIB 2143 The IANA is requested to assign { transmission CCC } to the 2144 VPLS-BGP-MIB MIB module specified in this document. 2145 -- Editor's Note (to be removed prior to publication): the IANA is 2146 -- requested to assign a value for "AAA", "BBB" and "CCC" under 2147 -- the transmission subtree and to record the assignments in the 2148 -- SMI Numbers registry. When the assignments have been made, the 2149 -- RFC Editor is asked to replace "AAA", "BBB" and "CCC" (here and 2150 -- in the MIB modules) with the assigned values and to remove this 2151 -- note. 2153 9. References 2155 9.1. Normative References 2157 [RFC2119] S. Bradner, "Key Words for use in RFCs to Indicate 2158 Requirement Levels", RFC 2119, BCP 14, March 1997. 2160 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2161 J., Rose, M., and S. Waldbusser, "Structure of 2162 Management Information Version 2 (SMIv2)", STD 58, RFC 2163 2578, April 1999. 2165 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2166 J., Rose, M., and S. Waldbusser, "Textual Conventions 2167 for SMIv2", STD 58, RFC 2579, April 1999. 2169 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2170 J., Rose, M., and S. Waldbusser, "Conformance 2171 Statements for SMIv2", STD 58, RFC 2580, April 1999. 2173 VPLS Management Information Base Feb, 2014 2175 [RFC3413] Levi, D., Meyer, P., and B. Stewart, "Simple Network 2176 Management Protocol (SNMP) Applications", STD 62, RFC 2177 3413, December 2002. 2179 [RFC3415] Wijnen, B., Presuhn, R. and K. McCloghrie, "View- 2180 based Access Control Model (VACM) for the Simple 2181 Network Management Protocol (SNMP)", STD 62, RFC 2182 3415, December 2002. 2184 [RFC4188] Norseth, K., and Bell, E., "Definitions of Managed 2185 Objects for Bridges", RFC 4188, Sept 2006. 2187 [RFC4265] Schliesser, B. and T. Nadeau, "Definition of Textual 2188 Conventions for Virtual Private Network (VPN) 2189 Management", RFC 4265, November 2005. 2191 [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private 2192 Networks (VPNs)", RFC 4364, February 2006. 2194 [RFC4761] Kompella, K. and Y. Rekhter, "Virtual Private LAN Service 2195 (VPLS) Using BGP for Auto-Discovery and Signaling",RFC 2196 4761, January 2007. 2198 [RFC4762] Lasserre, M. and Kompella, V. (Editors), "Virtual Private 2199 LAN Service (VPLS) Using Label Distribution Protocol (LDP) 2200 Signaling", RFC 4762, January 2007. 2202 [RFC5601] T. Nadeau, Ed., D. Zelig, Ed., "Pseudowire (PW) 2203 Management Information Base (MIB)", RFC 5601, July 2009. 2205 9.2. Informative References 2207 [RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces Group 2208 MIB", RFC 2863, June 2000. 2210 VPLS Management Information Base Feb, 2014 2212 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 2213 "Introduction and Applicability Statements for 2214 Internet-Standard Management Framework", RFC 3410, 2215 December 2002. 2217 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 2218 Architecture for Describing Simple Network Management 2219 Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, 2220 December 2002. 2222 [RFC3813] Srinivasan, C., Viswanathan, A. and Nadeau, T., 2223 "Multiprotocol Label Switching (MPLS) Label Switching 2224 Router (LSR) Management Information Base", 2225 RFC 3813, June 2004 2227 [SNMP-CONTEXT-MAP-MIB] SNMP Context Mapping MIB, AS, Kiran Koushik, 2228 Nadeau, T, draft-kkoushik-snmp-context-map-mib. 2230 [RFC3985] Bryant, S. and P. Pate, "Pseudo Wire Emulation Edge-to- 2231 Edge (PWE3) Architecture", RFC 3985, March 2005. 2233 [RFC6074] E. Rosen et. al., "Provisioning, Autodiscovery, and 2234 Signaling in L2VPNs", RFC 6074, January 2011. 2236 10. Acknowledgments 2238 We wish to thank Marcelo Mourier and Reva Bailey for their 2239 valuable feedback. Some portion of the work has been referenced 2240 from their original Timetra Enterprise MIB work. 2242 We wish to thank Praveen Muley, VJ Shah, Li Wentao, Kong Yong, Luo 2243 Jian, Feng Jun, Takeshi Usui for their feedback. 2245 11. Authors' Addresses 2247 Thomas D. Nadeau 2248 Lucid Vision 2249 Email: tnadeau@lucidvision.com 2251 A S Kiran Koushik 2252 Cisco Systems Inc. 2253 12515 Research Blvd, Bldg 4, 2254 Austin, TX 78759 2255 Email: kkoushik@cisco.com 2257 Rohit Mediratta 2258 Alcatel-Lucent, 2259 701 E Middlefield Rd. 2260 Mountain View, CA 94040 2261 Email: rohit.mediratta@alcatel-lucent.com 2262 VPLS Management Information Base Feb, 2014 2264 12. Full Copyright Statement 2266 Copyright (c) 2014 IETF Trust and the persons identified as the 2267 document authors. All rights reserved. 2269 This document is subject to BCP 78 and the IETF Trust's Legal 2270 Provisions Relating to IETF Documents 2271 (http://trustee.ietf.org/license-info) in effect on the date of 2272 publication of this document. Please review these documents 2273 carefully, as they describe your rights and restrictions with 2274 respect to this document. Code Components extracted from this 2275 document must include Simplified BSD License text as described in 2276 Section 4.e of the Trust Legal Provisions and are provided without 2277 warranty as described in the Simplified BSD License. 2279 This document may contain material from IETF Documents or IETF 2280 Contributions published or made publicly available before November 2281 10, 2008. The person(s) controlling the copyright in some of this 2283 material may not have granted the IETF Trust the right to allow 2284 modifications of such material outside the IETF Standards Process. 2285 Without obtaining an adequate license from the person(s) 2286 controlling the copyright in such materials, this document may not 2287 be modified outside the IETF Standards Process, and derivative 2288 works of it may not be created outside the IETF Standards Process, 2289 except to format it for publication as an RFC or to translate it 2290 into languages other than English.