idnits 2.17.1 draft-ietf-mpls-tp-linear-protection-mib-01.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 date (August 7, 2013) is 3912 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) == Outdated reference: A later version (-11) exists of draft-ietf-mpls-tp-oam-id-mib-01 Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force Kingston Smiler Selvaraj 3 Internet-Draft IpInfusion 4 Intended status: Standards Track M.Venkatesan 5 Expires: February 8, 2014 Dell Inc. 6 V. Manral 7 Hewlett-Packard Corp 8 Daniel King 9 Old Dog Consulting 10 Sam Aldrin 11 Huawei Technologies 12 August 7, 2013 14 MPLS Transport Profile Linear Protection MIB 15 draft-ietf-mpls-tp-linear-protection-mib-01 17 Abstract 19 This memo defines a portion of the Management Information Base (MIB) for 20 use with network management protocols. In particular it defines objects 21 for managing MPLS Transport Profile (MPLS-TP) Linear Protection. 23 Status of This Memo 25 This Internet-Draft is submitted to IETF in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering Task 29 Force (IETF), its areas, and its working groups. Note that other groups 30 may also distribute working documents as Internet-Drafts. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference material 35 or to cite them other than as "work in progress." 37 The list of current Internet-Drafts can be accessed at 38 http://www.ietf.org/ietf/1id-abstracts.txt. 40 The list of Internet-Draft Shadow Directories can be accessed at 41 http://www.ietf.org/shadow.html. 43 This Internet-Draft will expire on February 8, 2014. 45 Copyright and License Notice 47 Copyright (c) 2013 IETF Trust and the persons identified as the document 48 authors. All rights reserved. 50 This document is subject to BCP 78 and the IETF Trust's Legal Provisions 51 Relating to IETF Documents (http://trustee.ietf.org/license-info) in 52 effect on the date of publication of this document. Please review these 53 documents carefully, as they describe your rights and restrictions with 54 respect to this document. Code Components extracted from this document 55 must include Simplified BSD License text as described in Section 4.e of 56 the Trust Legal Provisions and are provided without warranty as 57 described in the Simplified BSD License. 59 Table of Contents 61 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 62 2. The Internet-Standard Management Framework . . . . . . . . . . 3 63 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 64 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 65 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 3 66 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 3 67 5.2. The MPLS TP Linear Protection Subtree . . . . . . . . . . . 4 68 5.3. The Notifications Subtree . . . . . . . . . . . . . . . . . 4 69 5.4. The Table Structures . . . . . . . . . . . . . . . . . . . 4 70 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 5 71 6.1. Relationship to the MPLS OAM maintenance identifiers MIB 72 module . . . . . . . . . . . . . . . . . . . . . . . . . . 5 73 6.2. MIB modules required for IMPORTS . . . . . . . . . . . . . 5 74 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 5 75 8. Security Considerations . . . . . . . . . . . . . . . . . . . 26 76 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 27 77 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 27 78 10.1. Normative References . . . . . . . . . . . . . . . . . . 27 79 10.2. Informative References . . . . . . . . . . . . . . . . . 28 80 11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 28 81 12. Author's Address . . . . . . . . . . . . . . . . . . . . . . . 28 83 1. Introduction 85 This memo defines a portion of the Management Information Base (MIB) for 86 use with network management protocols. In particular it defines objects 87 for managing MPLS Transport Profile (MPLS-TP) Linear Protection. 89 This MIB module should be used for configuring and managing the MPLS TP 90 linear protection for MPLS TP LSPs. 92 2. The Internet-Standard Management Framework 94 For a detailed overview of the documents that describe the current 95 Internet-Standard Management Framework, please refer to section 7 of RFC 96 3410 [RFC3410]. 98 Managed objects are accessed via a virtual information store, termed the 99 Management Information Base or MIB. MIB objects are generally accessed 100 through the Simple Network Management Protocol (SNMP). Objects in the 101 MIB are defined using the mechanisms defined in the Structure of 102 Management Information (SMI). This memo specifies a MIB module that is 103 compliant to the SMIv2, which is described in STD 58, RFC 2578 104 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 106 3. Conventions 108 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 109 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 110 document are to be interpreted as described in RFC 2119 [RFC2119]. 112 4. Overview 114 [RFC6378] defines the protocol to provide a linear protection 115 switching mechanism for MPLS transport profile with protection 116 domain as point-to-point LSP. The detailed protocol specification of 117 MPLS transport profile linear protection is described in [RFC6378]. 118 This document specifies a MIB module for the LER that supports MPLS 119 TP Linear protection (which includes 1:n protection architecture) 120 and a MIB module that defines textual conventions. 122 5. Structure of the MIB Module 124 5.1. Textual Conventions 126 The following new textual conventions are defined in a separate MIB 127 module in this document 128 MplsLpsReq 129 MplsLpsFpathPath 130 MplsLpsCommand 132 5.2. The MPLS TP Linear Protection Subtree 134 MPLS-LPS-MIB is the MIB module defined in this document, and it is 135 put under mplsStdMIB. 137 5.3. The Notifications Subtree 139 Notifications are defined to inform the management station about 140 switchover and mode mismatch of linear protection switching group. 141 Two notifications are defined for this purpose. The notification, 142 mplsLpsEventSwitchover is to inform the management station about the 143 switchover of the active path and the notification 144 mplsLpsEventModeMismatch is to inform the management station about 145 the mismatch in the revertive mode across the end point of the 146 protection domain. 148 5.4. The Table Structures 150 The MPLS TP Linear protection MIB module has four tables. The tables 151 are as follows 153 o mplsLpsConfigTable 155 This table is used to configure MPLS TP Linear protection 156 switching Group. The protection switching group is identified by 157 mplsLpsConfigGroupName. The other attributes in this table can be 158 used to configure properties that are specific to the protection 159 switching group. 161 o mplsLpsStatusTable 163 This table provides the current status information of mpls linear 164 protection groups that have been configured on the system. When a 165 protection group is configured or deleted in the 166 mplsLpsConfigTable, then the corresponding row of that session in 167 the mplsLpsStatusTable is, respectively, automatically created or 168 deleted. 170 o mplsLpsMeConfigTable 172 This table is used to associate the Maintenance Entities (MEs) to 173 the protection switching group. The ME is identified by 174 mplsOamIdMegIndex, mplsOamIdMeIndex and mplsOamIdMeMpIndex. 176 o mplsLpsMeStatusTable 178 This table provides the current information about the protection 179 state of MEs that have been configured on the system. When a 180 ME configured or deleted in the mplsLpsMeConfigTable, then the 181 corresponding row of that session in the mplsLpsMeStatusTable 182 is, respectively, automatically created or deleted. 184 6. Relationship to Other MIB Modules 186 6.1. Relationship to the MPLS OAM maintenance identifiers MIB module 188 The mplsLpsMeConfigTable entry is extended by entry in the 189 mplsOamIdMeTable [MPLS-OAM-ID-STD-MIB] defined in draft-ietf-mpls-tp- 190 oam-id-mib. Note that the nature of the 'extends' relationship is a 191 sparse augmentation so that the entry in the mplsLpsMeConfigTable has 192 the same index values as the entry in the mplsOamIdMeTable. Each time 193 that an entry is created in the mplsOamIdMeTable for which the LER 194 supports MPLS TP Linear protection a row is created automatically in 195 the mplsLpsMeConfigTable. 197 6.2. MIB modules required for IMPORTS 199 The MPLS-LPS-MIB module requires following MIB modules for IMPORTS: 201 o SNMPv2-SMI defined in [RFC2578] 203 o SNMPv2-CONF defined in [RFC2580] 205 o SNMPv2-TC defined in [RFC2579] 207 o MPLS-OAM-ID-STD-MIB defined in [draft-ietf-mpls-tp-oam-id-mib] 209 7. Definitions 210 MPLS-LPS-MIB DEFINITIONS ::= BEGIN 212 IMPORTS 213 MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-TYPE, 214 Gauge32, Counter32, Integer32, Unsigned32 215 FROM SNMPv2-SMI 216 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 217 FROM SNMPv2-CONF -- [RFC2580] 218 TEXTUAL-CONVENTION, RowStatus, 219 TimeStamp, StorageType 220 FROM SNMPv2-TC 221 SnmpAdminString 222 FROM SNMP-FRAMEWORK-MIB 223 mplsStdMIB 224 FROM MPLS-TC-STD-MIB -- [RFC3811] 225 mplsOamIdMegIndex, mplsOamIdMeIndex, mplsOamIdMeMpIndex 226 FROM MPLS-OAM-ID-STD-MIB; 228 mplsLpsMIB MODULE-IDENTITY 229 LAST-UPDATED "201301210000Z" -- January 21, 2013 230 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 231 CONTACT-INFO 233 " 234 Kingston Smiler Selvaraj 235 Ipinfusion 236 Email:kingstons@ipinfusion.com 238 Venkatesan Mahalingam 239 Dell Inc. 240 350 Holger way, San Jose, CA, USA 241 Email: venkat.mahalingams@gmail.com 243 Vishwas Manral 244 Hewlet-Packard, Inc. 245 19111 Pruneridge Ave., Cupertino, CA, 95014 246 Phone: 408-447-1497 247 Email: vishwas.manral@hp.com 249 Daniel King 250 Old Dog Consulting 251 UK 252 Email:daniel@olddog.co.uk 254 Sam Aldrin 255 Huawei Technologies, co. 256 2330 Central Express Way, 257 Santa Clara, CA 95051, USA 258 Email: aldrin.ietf@gmail.com" 259 DESCRIPTION 260 "This management information module supports the 261 configuration and management of MPLS TP linear 262 protection groups. " 263 REVISION 264 "201301210000Z" -- January 21, 2013 265 DESCRIPTION 266 "MPLS Protection Switching Group objects for LSP 267 MEPs" 269 ::= { mplsStdMIB xxx } -- xxx to be replaced with 270 -- correct value 272 -- Top level components of this MIB module. 273 -- Notifications 274 mplsLpsNotifications 275 OBJECT IDENTIFIER ::= { mplsLpsMIB 0 } 276 -- tables, scalars 277 mplsLpsObjects 278 OBJECT IDENTIFIER ::= { mplsLpsMIB 1 } 279 -- conformance 281 mplsLpsConformance 282 OBJECT IDENTIFIER ::= { mplsLpsMIB 2 } 284 MplsLpsReq ::= TEXTUAL-CONVENTION 285 STATUS current 286 DESCRIPTION 287 "This Textual Convention describes an object that stores 288 the PSC Request field of the PSC control packet. The values 289 are as follows 291 1110 Lockout of Protection 292 1100 Forced Switch 293 1010 Signal Fail (SF) 294 0111 Signal Degrade (SD) 295 0101 Manual Switch 296 0100 Wait-to-Restore 297 0001 Do Not Revert 298 0000 No Request" 299 REFERENCE 300 "Section 4.2.2 of RFC6378" 301 SYNTAX OCTET STRING (SIZE (2)) 303 MplsLpsFpathPath ::= TEXTUAL-CONVENTION 304 STATUS current 305 DESCRIPTION 306 "This Textual Convention describes an object that stores 307 the Fault Path (FPath) field and Data Path (Path) field of 308 the PSC control packet. 310 FPath is located in the first octet and Path is 311 located in the second octet. Bits are numbered from left to 312 right. 314 The value and the interpretation of FPath field is as follows 315 2-255 for future extensions 316 1 the anomaly condition is on the working path 317 0 the anomaly condition is on the protection path 319 The value and the interpretation of Path field is as follows 321 2-255 for future extensions 322 1 protection path is transporting user data traffic 323 0 protection path is not transporting user data traffic 324 " 325 REFERENCE 326 "Section 4.2.5 and 4.2.6 of RFC6378" 327 SYNTAX OCTET STRING (SIZE (2)) 329 MplsLpsCommand ::= TEXTUAL-CONVENTION 330 STATUS current 331 DESCRIPTION 332 "This command allows a user to perform any action over ME. 333 If the protection command cannot be executed because an 334 equal or higher priority request is in effect, an 335 inconsistentValue error is returned. 337 The command values are: 339 noCmd 341 This value should be returned by a read request when no command 342 has been written to the object in question since 343 initialization. This value may not be used in a write 344 operation. If noCmd is used in a write operation a wrongValue 345 error is returned. 347 clear 349 Clears all of the commands listed below for the specified ME. 351 lockoutOfProtection 353 Prevents any of the working ME from switching to the protection 354 ME. The specified ME should be the protection ME, otherwise an 355 inconsistentValue error is returned. 357 forcedSwitchWorkToProtect 359 Switches the specified working ME to the protection path. 360 If the protection ME is specified an inconsistentValue 361 error is returned. 363 manualSwitchWorkToProtect 365 Switches the specified working ME to the protection ME. 366 If the protection ME is specified an inconsistentValue 367 error is returned." 369 SYNTAX INTEGER { 370 noCmd(1), 371 clear(2), 372 lockoutOfProtection(3), 373 forcedSwitchWorkToProtect(4), 374 manualSwitchWorkToProtect(5) 375 } 377 -- Start of MPLS Transport Profile Protection Switching 378 -- Table 379 -- MPLS TP Protection Switching Configuration Table 380 -- This table supports the addition, configuration and deletion 381 -- of MPLS TP Protection Switching groups. 383 mplsLpsConfigGroups OBJECT-TYPE 384 SYNTAX Gauge32 385 MAX-ACCESS read-only 386 STATUS current 387 DESCRIPTION 388 "The object hold the count of MPLS Protection Switching 389 groups. This count includes all rows in mplsLpsConfigTable, 390 regardless of the value of mplsLpsConfigRowStatus." 391 ::= { mplsLpsObjects 1 } 393 mplsLpsConfigTable OBJECT-TYPE 394 SYNTAX SEQUENCE OF MplsLpsConfigEntry 395 MAX-ACCESS not-accessible 396 STATUS current 397 DESCRIPTION 398 "This table lists the mpls linear protection groups that 399 have been configured on the system." 400 ::= { mplsLpsObjects 2 } 402 mplsLpsConfigEntry OBJECT-TYPE 403 SYNTAX MplsLpsConfigEntry 404 MAX-ACCESS not-accessible 405 STATUS current 406 DESCRIPTION 407 "A conceptual row in the mplsLpsConfigTable." 408 INDEX { mplsLpsConfigGroupIndex } 409 ::= { mplsLpsConfigTable 1 } 411 MplsLpsConfigEntry ::= SEQUENCE { 412 mplsLpsConfigGroupIndex Unsigned32, 413 mplsLpsConfigGroupName SnmpAdminString, 414 mplsLpsConfigMode INTEGER, 415 mplsLpsConfigRevertive INTEGER, 416 mplsLpsConfigProtectionScheme INTEGER, 417 mplsLpsConfigSdThreshold Integer32, 418 mplsLpsConfigWaitToRestore Integer32, 419 mplsLpsConfigContinualTxInterval Integer32, 420 mplsLpsConfigRapidTxInterval Integer32, 421 mplsLpsConfigCreationTime TimeStamp, 422 mplsLpsConfigRowStatus RowStatus, 423 mplsLpsConfigStorageType StorageType 425 } 427 mplsLpsConfigGroupIndex OBJECT-TYPE 428 SYNTAX Unsigned32 429 MAX-ACCESS not-accessible 430 STATUS current 431 DESCRIPTION 432 "Index for the conceptual row identifying a protection group." 433 ::= { mplsLpsConfigEntry 1 } 435 mplsLpsConfigGroupName OBJECT-TYPE 436 SYNTAX SnmpAdminString (SIZE (1..32)) 437 MAX-ACCESS read-create 438 STATUS current 439 DESCRIPTION 440 "Textual name represents the mpls tp protection group. 441 Each Protection Group is identified by a unique 442 protection group name. " 443 ::= { mplsLpsConfigEntry 2 } 445 mplsLpsConfigMode OBJECT-TYPE 446 SYNTAX INTEGER { 447 onePlusOne(1), 448 oneColonOne(2), 449 oneColonN(3) 450 } 451 MAX-ACCESS read-create 452 STATUS current 453 DESCRIPTION 454 "The architectural mode of the Protection group. This can 455 either be 1+1, 1:1, 1:n. 457 1+1 459 In the 1+1 protection scheme, a fully dedicated 460 protection entity is allocated. Data traffic is copied 462 and fed at the source to both the working and the 463 protection entities. The traffic on the working and the 464 protection entities is transmitted simultaneously to 465 the sink of the protection domain, where selection 466 between the working and protection entities is performed 468 1:1 470 In the 1:1 scheme, a protection path is allocated to 471 protect against a defect, failure, or a degradation in a 472 working path. In normal conditions, data traffic is 473 transmitted over the working entity, while the 474 protection entity functions in the idle state. If there 475 is a defect on the working entity or a specific 476 administrative request, traffic is switched to the 477 protection entity. 479 1:n 481 In case of 1:n linear protection, one protection entity 482 is allocated to protect n working entities. The protection 483 entity might not have sufficient resources to protect all the 484 working entities that may be affected by fault conditions at a 485 specific time. In this case, in order to guaranteed 486 protection, the protection entity should support enough 487 capacity and bandwidth to protect any of the n working 488 entities." 490 DEFVAL {onePlusOne} 491 ::= { mplsLpsConfigEntry 3 } 493 mplsLpsConfigRevertive OBJECT-TYPE 494 SYNTAX INTEGER { nonrevertive(1), revertive(2) } 495 MAX-ACCESS read-create 496 STATUS current 497 DESCRIPTION 498 "This object represents the reversion mode of the Linear 499 Protection Switching group. The reversion mode of 501 protection mechanism may be either revertive or 502 non-revertive. 504 nonrevertive 506 In non-revertive mode, after a service has been 507 recovered, traffic will be forwarded on the recovery 509 path 511 revertive 513 In revertive mode, after a service has been 514 recovered, traffic will be redirected back onto the 515 original working path." 517 DEFVAL { nonrevertive } 518 ::= { mplsLpsConfigEntry 4 } 520 mplsLpsConfigProtectionScheme OBJECT-TYPE 521 SYNTAX INTEGER { bidirectional(1), unidirectional(2) } 522 MAX-ACCESS read-create 523 STATUS current 524 DESCRIPTION 525 "The object represents the operational scheme of 526 protection switching group. The protection scheme may 527 either be unidirectional or bidirectional. 529 bidirectional 531 In bidirectional protection scheme, both the directions 532 will be switched simultaneously even if the fault 533 applies to only one direction of the path. 535 unidirectional 537 In unidirectional protection scheme protection switching 538 will be performed independently for each direction of a 539 bidirectional transport path 541 This object may not be modified if the associated 542 mplsLpsConfigRowStatus object is equal to active(1). " 544 DEFVAL {bidirectional} 545 ::= { mplsLpsConfigEntry 5 } 547 mplsLpsConfigSdThreshold OBJECT-TYPE 548 SYNTAX Integer32 (1..9) 549 MAX-ACCESS read-create 550 STATUS current 551 DESCRIPTION 552 "This object holds the threshold value of the Signal 553 Degrade. 555 When the MPLS DM OAM reaches this threshold value, the 557 Signal Degrade event will be given to this 558 protection domain. 560 This object may be modified if the associated 561 mplsLpsConfigRowStatus object is equal to active(1)." 562 ::= { mplsLpsConfigEntry 6 } 564 mplsLpsConfigWaitToRestore OBJECT-TYPE 565 SYNTAX Integer32 (0..720) 566 UNITS "seconds" 567 MAX-ACCESS read-create 568 STATUS current 569 DESCRIPTION 570 "This object hold the Wait To Restore timer value in 571 seconds. 572 The WTR timer is used to delay reversion of PSC state 573 to Normal state when recovering from a failure 574 condition on the working path when the protection 575 domain is configured for revertive behavior 577 This object may not be modified if the associated 578 mplsLpsConfigRowStatus object is equal to active(1)." 579 DEFVAL { 300 } 580 ::= { mplsLpsConfigEntry 7 } 582 mplsLpsConfigContinualTxInterval OBJECT-TYPE 583 SYNTAX Integer32 (1..20) 584 UNITS "seconds" 585 MAX-ACCESS read-create 586 STATUS current 587 DESCRIPTION 588 "The Continual Tx Time in Seconds. Represents the time 589 interval to send the continual LPS packet to the other 590 end based on the current state." 591 DEFVAL { 5 } 592 ::= { mplsLpsConfigEntry 8 } 594 mplsLpsConfigRapidTxInterval OBJECT-TYPE 595 SYNTAX Integer32 (1000..20000) 596 UNITS "micro-seconds" 597 MAX-ACCESS read-create 598 STATUS current 599 DESCRIPTION 600 "The Rapid Tx interval in micro-Seconds. Represents the time 601 interval to send the LPS packet to the other end, when 602 there is a change in state of Linear Protection domain due 603 to local input. The default value is 3.3 milli-seconds 604 which is 3300 micro-seconds" 606 DEFVAL { 3300 } 607 ::= { mplsLpsConfigEntry 9 } 609 mplsLpsConfigCreationTime OBJECT-TYPE 610 SYNTAX TimeStamp 611 MAX-ACCESS read-only 612 STATUS current 613 DESCRIPTION 614 "The value of sysUpTime at the time the row was 615 created" 617 ::= { mplsLpsConfigEntry 10 } 619 mplsLpsConfigRowStatus OBJECT-TYPE 620 SYNTAX RowStatus 621 MAX-ACCESS read-create 622 STATUS current 623 DESCRIPTION 624 "This represents the status of the MPLS TP Linear 625 Protection group Entry. This variable is used to 626 create, modify, and/or delete a row in this table. 627 An entry may not exist in the active state unless all 628 objects in the entry have an appropriate value." 629 ::= { mplsLpsConfigEntry 11 } 631 mplsLpsConfigStorageType OBJECT-TYPE 632 SYNTAX StorageType 633 MAX-ACCESS read-create 634 STATUS current 635 DESCRIPTION 636 "The storage type for this conceptual row. 637 Conceptual rows having the value 'permanent' need not 638 allow write-access to any columnar objects in the row." 639 DEFVAL { nonVolatile } 640 ::= { mplsLpsConfigEntry 12 } 642 -- 643 -- MPLS TP Linear Protection Switching Status Table 644 -- 645 -- This table provides Protection Switching group statistics. 646 -- 648 mplsLpsStatusTable OBJECT-TYPE 649 SYNTAX SEQUENCE OF MplsLpsStatusEntry 651 MAX-ACCESS not-accessible 652 STATUS current 653 DESCRIPTION 654 "This table provides status information about mpls 655 linear protection groups that have been configured 656 on the system." 657 ::= { mplsLpsObjects 3 } 659 mplsLpsStatusEntry OBJECT-TYPE 660 SYNTAX MplsLpsStatusEntry 661 MAX-ACCESS not-accessible 662 STATUS current 663 DESCRIPTION 664 "A conceptual row in the mplsLpsStatusTable." 665 AUGMENTS { mplsLpsConfigEntry } 666 ::= { mplsLpsStatusTable 1 } 668 MplsLpsStatusEntry ::= SEQUENCE { 669 mplsLpsStatusReqRcv MplsLpsReq, 670 mplsLpsStatusReqSent MplsLpsReq, 671 mplsLpsStatusFpathPathRcv MplsLpsFpathPath, 672 mplsLpsStatusFpathPathSent MplsLpsFpathPath, 673 mplsLpsStatusModeMismatches Counter32 674 } 676 mplsLpsStatusReqRcv OBJECT-TYPE 677 SYNTAX MplsLpsReq 678 MAX-ACCESS read-only 679 STATUS current 680 DESCRIPTION 681 "The current value of the PSC Request field received on 682 more recent PSC packet" 683 ::= { mplsLpsStatusEntry 1 } 685 mplsLpsStatusReqSent OBJECT-TYPE 686 SYNTAX MplsLpsReq 687 MAX-ACCESS read-only 688 STATUS current 689 DESCRIPTION 690 "The current value of the PSC Request field sent on the 691 more recent PSC packet" 692 ::= { mplsLpsStatusEntry 2 } 694 mplsLpsStatusFpathPathRcv OBJECT-TYPE 695 SYNTAX MplsLpsFpathPath 696 MAX-ACCESS read-only 698 STATUS current 700 DESCRIPTION 701 "The current value of the FPath and Path fields received 702 on more recent PSC packet" 703 ::= { mplsLpsStatusEntry 3 } 705 mplsLpsStatusFpathPathSent OBJECT-TYPE 706 SYNTAX MplsLpsFpathPath 707 MAX-ACCESS read-only 708 STATUS current 709 DESCRIPTION 710 "The current value of the FPath and Path fields sent 711 on more recent PSC packet" 713 ::= { mplsLpsStatusEntry 4 } 715 mplsLpsStatusModeMismatches OBJECT-TYPE 716 SYNTAX Counter32 717 MAX-ACCESS read-only 718 STATUS current 719 DESCRIPTION 720 "This object holds number of occurrences of mismatch in 721 revertive mode across the protection domain end points." 722 ::= { mplsLpsStatusEntry 5 } 724 -- MPLS Linear Protection ME Association Configuration Table 725 -- This table supports the addition, configuration and deletion 726 -- of MPLS Linear Protection Maintenance Entities in Protection 727 -- Switching groups. 729 mplsLpsMeConfigTable OBJECT-TYPE 731 SYNTAX SEQUENCE OF MplsLpsMeConfigEntry 732 MAX-ACCESS not-accessible 733 STATUS current 734 DESCRIPTION 735 "This table lists Maintenance Association that have been 736 configured in Protection groups." 737 ::= { mplsLpsObjects 4 } 739 mplsLpsMeConfigEntry OBJECT-TYPE 740 SYNTAX MplsLpsMeConfigEntry 741 MAX-ACCESS not-accessible 742 STATUS current 743 DESCRIPTION 745 "A conceptual row in the mplsLpsMeConfigTable." 746 INDEX {mplsOamIdMegIndex, mplsOamIdMeIndex, mplsOamIdMeMpIndex} 747 ::= { mplsLpsMeConfigTable 1 } 749 MplsLpsMeConfigEntry ::= SEQUENCE { 750 mplsLpsMeConfigGroupIndex Unsigned32, 751 mplsLpsMeConfigState INTEGER, 752 mplsLpsMeConfigCommand MplsLpsCommand, 753 mplsLpsMeConfigHoldOff Integer32 754 } 756 mplsLpsMeConfigGroupIndex OBJECT-TYPE 757 SYNTAX Unsigned32 758 MAX-ACCESS not-accessible 759 STATUS current 760 DESCRIPTION 761 "This object holds the Protection group index wherein 762 this ME included in. If this ME is not part of any protection 763 group then this object contains value 0. " 764 DEFVAL { 0 } 765 ::= { mplsLpsMeConfigEntry 1 } 767 mplsLpsMeConfigState OBJECT-TYPE 768 SYNTAX INTEGER { primary(1), backup(2) } 770 MAX-ACCESS read-create 771 STATUS current 772 DESCRIPTION 773 "This object represents the operational state of the ME 774 as either primary or backup" 775 ::= { mplsLpsMeConfigEntry 2 } 777 mplsLpsMeConfigCommand OBJECT-TYPE 778 SYNTAX MplsLpsCommand 779 MAX-ACCESS read-write 780 STATUS current 781 DESCRIPTION 783 "Allows the initiation of an MPLS Linear protection command on 784 the protection group and the ME specified by the index values. 785 When read this object returns the last command written 786 or noCmd if no command has been written to this ME 787 since initialization. The return of the last command 788 written does not imply that this command is currently in 789 effect. This request may have been preempted by a higher 790 priority local or remote request. 792 The value lockoutOfProtection should only be applied to the 793 protection path / ME since that switch command prevents any 794 of the working path / ME from switching to the protection path. 795 Following the same logic, forcedSwitchWorkToProtect and 796 manualSwitchWorkToProtect should only be applied to a working 797 ME." 798 ::= { mplsLpsMeConfigEntry 3 } 800 mplsLpsMeConfigHoldOff OBJECT-TYPE 801 SYNTAX Integer32 (0..10000) 802 UNITS "milli-seconds" 803 MAX-ACCESS read-create 804 STATUS current 805 DESCRIPTION 806 "The hold-off time in milliseconds. Represents the time 807 between SF/SD condition detection and declaration of 808 an SF/SD request to the protection switching logic. 809 It is intended to avoid unnecessary switching when a lower- 810 layer protection mechanism is in place. 811 Can be configured in steps of 100" 812 DEFVAL { 0 } 813 ::= { mplsLpsMeConfigEntry 4 } 815 -- MPLS Linear Protection ME Status Table 816 -- This table provides Protection Switching ME statistics. 818 mplsLpsMeStatusTable OBJECT-TYPE 819 SYNTAX SEQUENCE OF MplsLpsMeStatusEntry 820 MAX-ACCESS not-accessible 821 STATUS current 822 DESCRIPTION 823 "This table contains status information of all the ME 824 that are included in MPLS Protection groups." 825 ::= { mplsLpsObjects 5 } 827 mplsLpsMeStatusEntry OBJECT-TYPE 828 SYNTAX MplsLpsMeStatusEntry 829 MAX-ACCESS not-accessible 830 STATUS current 831 DESCRIPTION 832 "A conceptual row in the mplsLpsMeStatusTable." 833 AUGMENTS { mplsLpsMeConfigEntry } 834 ::= { mplsLpsMeStatusTable 1 } 836 MplsLpsMeStatusEntry ::= SEQUENCE { 837 mplsLpsMeStatusCurrent BITS, 838 mplsLpsMeStatusSignalDegrades Counter32, 839 mplsLpsMeStatusSignalFailures Counter32, 840 mplsLpsMeStatusSwitchovers Counter32, 841 mplsLpsMeStatusLastSwitchover TimeStamp, 842 mplsLpsMeStatusSwitchoverSeconds Counter32 843 } 845 mplsLpsMeStatusCurrent OBJECT-TYPE 846 SYNTAX BITS { 847 localLockedOut(0), 848 localSd(1), 849 localSf(2), 850 localSwitched(3), 851 localWtr(4), 852 remoteLockedout(5) 853 remoteSd(6), 854 remoteSf(7), 855 remoteSwitched(8), 856 remoteWtr(9) 857 } 858 MAX-ACCESS read-only 859 STATUS current 860 DESCRIPTION 861 "Indicates the current state of the MA. 863 localLockedOut 865 This bit, when it is set on a working ME or working path 866 indicates that the working path is prevented from 867 switching to the protection path because of local request. 868 When it is set on protection / backup path, this bit 869 indicates that none of the working path (in case of 870 1:n) can switch to the protection path. 872 localSd 874 This bit implies that local signal degrade condition is 875 in effect on this ME / path. 877 localSf 879 This bit implies that local signal failure condition is 880 in effect on this ME / path. 882 localSwitched 884 This bit is only applicable to the working ME / path. 885 It implies that the working path is currently switched 886 to the protection path because of local request. 888 local wtr 890 This bit implies that local Wait-to-Restore state is 891 in effect." 893 remoteLockedOut 895 This bit, when it is set on a working ME or working path 896 indicates that the working path is prevented from 897 switching to the protection path because of remote request. 898 When it is set on protection / backup path, this bit 899 indicates that none of the working path (in case of 900 1:n) can switch to the protection path. 902 remoteSd 903 This bit implies that remote signal degrade condition is 904 in effect on this ME / path. 906 remoteSf 908 This bit implies that remote signal failure condition is 909 in effect on this ME / path. 911 remoteSwitched 913 This bit is only applicable to the working ME / path. 914 It implies that the working path is currently switched 915 to the protection path because of remote request. 917 remoteWtr 919 This bit implies that remote Wait-to-Restore state is 920 in effect." 921 ::= { mplsLpsMeStatusEntry 1 } 923 mplsLpsMeStatusSignalDegrades OBJECT-TYPE 924 SYNTAX Counter32 925 MAX-ACCESS read-only 926 STATUS current 927 DESCRIPTION 928 "Represents the count of Signal Degrade conditions. 929 This condition occurs when the DM exceeds the 930 currently configured value of the relevant instance of 931 mplsLpsConfigSdThreshold." 932 ::= { mplsLpsMeStatusEntry 2 } 934 mplsLpsMeStatusSignalFailures OBJECT-TYPE 936 SYNTAX Counter32 937 MAX-ACCESS read-only 938 STATUS current 939 DESCRIPTION 940 "Represents the count of Signal failure conditions. 941 This condition occurs when the OAM running on this MA 942 detects the Signal Fail event." 943 ::= { mplsLpsMeStatusEntry 3 } 945 mplsLpsMeStatusSwitchovers OBJECT-TYPE 946 SYNTAX Counter32 947 MAX-ACCESS read-only 948 STATUS current 949 DESCRIPTION 950 "Represents the count of SwitchOvers happened in this 951 MA. 953 When the mplsLpsMeConfigState is primary, this 954 object will return the number of times this path 955 has switched to the protection path. 957 When the mplsLpsMeConfigState is backup, this object 958 will return the number of times that any working paths 959 has been switched back to the working path from this 960 protection path." 961 ::= { mplsLpsMeStatusEntry 4 } 963 mplsLpsMeStatusLastSwitchover OBJECT-TYPE 964 SYNTAX TimeStamp 965 MAX-ACCESS read-only 966 STATUS current 967 DESCRIPTION 968 "This object holds the value of sysUpTime wherein the 969 last switchover happened. 971 When the mplsLpsMeConfigState is primary, this object 972 will return the value of sysUpTime when this path last 973 completed a switchover. If this path has never switched 974 to the protection line, the value 0 will be returned. 976 When the mplsLpsMeConfigState is backup, this object 977 will return the value of sysUpTime the last time that 978 a working path was switched back to the working path 979 from this protection path. If no working path has ever 980 switched back to the working path from this protection 981 path, the value 0 will be returned." 983 ::= { mplsLpsMeStatusEntry 5 } 985 mplsLpsMeStatusSwitchoverSeconds OBJECT-TYPE 986 SYNTAX Counter32 987 MAX-ACCESS read-only 988 STATUS current 989 DESCRIPTION 990 "The cumulative Protection Switching Duration (PSD) time 991 in seconds. 993 ForM a working path, this is the cumulative number of 994 seconds that traffic was carried on the protection 995 path. 997 For the protection path, this is the cumulative number 998 of seconds that the protection path has been used to 999 carry any working path traffic." 1001 ::= { mplsLpsMeStatusEntry 6 } 1003 mplsLpsNotificationEnable OBJECT-TYPE 1004 SYNTAX BITS { 1005 switchover(0), 1006 modeMismatch(1) 1007 } 1008 MAX-ACCESS read-write 1009 STATUS current 1011 DESCRIPTION 1012 "Provides the ability to enable and disable notifications 1013 defined in this MIB. 1015 switchover 1017 Indicates mplsLpsEventSwitchover notifications 1018 should be generated. 1020 modeMismatch 1022 Indicates mplsLpsEventModeMismatch notifications 1023 should be generated." 1025 DEFVAL { { } } 1026 ::= { mplsLpsObjects 6 } 1028 -- MPLS Linear Protection EVENTS 1030 mplsLpsEventSwitchover NOTIFICATION-TYPE 1031 OBJECTS { mplsLpsMeStatusSwitchovers, mplsLpsMeStatusCurrent } 1032 STATUS current 1033 DESCRIPTION 1034 "An mplsLpsEventSwitchover notification is sent when the 1035 value of an instance of mplsLpsMeStatusSwitchovers increments." 1036 ::= { mplsLpsNotifications 1 } 1038 mplsLpsEventModeMismatch NOTIFICATION-TYPE 1039 OBJECTS { mplsLpsStatusModeMismatches } 1040 STATUS current 1041 DESCRIPTION 1042 "An mplsLpsEventModeMismatch notification is sent when the 1043 value of an instance of mplsLpsStatusModeMismatches increments." 1045 ::= { mplsLpsNotifications 2 } 1047 -- End of Notifications. 1049 -- Module Compliance. 1051 mplsLpsCompliances 1052 OBJECT IDENTIFIER ::= { mplsLpsConformance 1 } 1054 mplsLpsGroups 1055 OBJECT IDENTIFIER ::= { mplsLpsConformance 2 } 1057 -- Compliance requirement for fully compliant implementations. 1059 mplsLpsModuleFullCompliance MODULE-COMPLIANCE 1061 STATUS current 1062 DESCRIPTION "Compliance statement for agents that provide full 1063 support for MPLS-LPS-MIB. Such devices can 1064 provide linear protection and also be configured using 1065 this MIB module." 1067 MODULE -- This module. 1068 MANDATORY-GROUPS { 1069 mplsLpsScalarGroup, 1070 mplsLpsConfigTableGroup, 1071 mplsLpsMeTableGroup 1072 } 1074 GROUP mplsLpsNotificationGroup 1075 DESCRIPTION "This group is only mandatory for those 1076 implementations which can efficiently implement 1077 the notifications contained in this group." 1079 ::= { mplsLpsCompliances 1 } 1081 -- Units of conformance. 1083 mplsLpsScalarGroup OBJECT-GROUP 1084 OBJECTS { 1085 mplsLpsConfigGroups, 1086 mplsLpsNotificationEnable 1087 } 1088 STATUS current 1089 DESCRIPTION 1090 "Collection of objects needed for MPLS Linear Protection." 1091 ::= { mplsLpsGroups 1 } 1093 mplsLpsConfigTableGroup OBJECT-GROUP 1094 OBJECTS { 1095 mplsLpsConfigGroupName, 1096 mplsLpsConfigRowStatus, 1097 mplsLpsConfigMode, 1098 mplsLpsConfigRevertive, 1099 mplsLpsConfigProtectionScheme, 1100 mplsLpsConfigSdThreshold, 1101 mplsLpsConfigWaitToRestore, 1102 mplsLpsConfigHoldOff, 1103 mplsLpsConfigContinualTxInterval, 1104 mplsLpsConfigRapidTxInterval, 1105 mplsLpsConfigCreationTime, 1106 mplsLpsConfigStorageType, 1107 mplsLpsStatusReqRcv, 1108 mplsLpsStatusReqSent, 1110 mplsLpsStatusFpathPathRcv, 1111 mplsLpsStatusFpathPathSent, 1112 mplsLpsStatusModeMismatches 1113 } 1114 STATUS current 1115 DESCRIPTION 1116 "Collection of objects needed for MPLS Linear Protection 1117 configuration and statistics." 1118 ::= { mplsLpsGroups 2 } 1120 mplsLpsMeTableGroup OBJECT-GROUP 1121 OBJECTS { 1122 mplsLpsMeConfigState, 1123 mplsLpsMeConfigCommand, 1124 mplsLpsMeStatusCurrent, 1126 mplsLpsMeStatusSignalDegrades, 1127 mplsLpsMeStatusSignalFailures, 1128 mplsLpsMeStatusSwitchovers, 1129 mplsLpsMeStatusLastSwitchover, 1130 mplsLpsMeStatusSwitchoverSeconds 1131 } 1132 STATUS current 1133 DESCRIPTION 1134 "Collection of objects needed for MPLS Linear Protection 1135 ME configuration and statistics." 1136 ::= { mplsLpsGroups 3 } 1138 mplsLpsNotificationGroup NOTIFICATION-GROUP 1139 NOTIFICATIONS { 1140 mplsLpsEventSwitchover, 1141 mplsLpsEventModeMismatch 1142 } 1143 STATUS current 1144 DESCRIPTION 1145 "Collection of objects needed to implement notifications." 1146 ::= { mplsLpsGroups 4 } 1148 -- MPLS-LPS-MIB module ends 1149 END 1151 8. Security Considerations 1153 There are a number of management objects defined in this MIB module 1154 with a MAX-ACCESS clause of read-write and/or read-create. Such 1155 objects may be considered sensitive or vulnerable in some networks in 1156 a non-secure environment without proper protection can have a 1157 negative effect on network operations. These are the tables and 1158 objects and their sensitivity/vulnerability: 1160 Some of the readable objects in this MIB module (i.e., objects with a 1161 MAX-ACCESS other than not-accessible) may be considered sensitive or 1162 vulnerable in some network environments. It is thus important to 1163 control even GET and/or NOTIFY access to these objects and possibly 1164 to even encrypt the values of these objects when sending them over 1165 the network via SNMP. These are the tables and objects and their 1166 sensitivity/vulnerability: 1168 SNMP versions prior to SNMPv3 did not include adequate security. Even 1169 if the network itself is secure (for example by using IPsec), even 1170 then, there is no control as to who on the secure network is allowed 1171 to access and GET/SET (read/change/create/delete) the objects in this 1172 MIB module. 1174 It is RECOMMENDED that implementers consider the security features as 1175 provided by the SNMPv3 framework (see [RFC3410], section 8), 1176 including full support for the SNMPv3 cryptographic mechanisms (for 1177 authentication and privacy). 1179 Further, deployment of SNMP versions prior to SNMPv3 is not 1180 recommended. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1181 enable cryptographic security. It is then a customer/operator 1182 responsibility to ensure that the SNMP entity giving access to an 1183 instance of this MIB module is properly configured to give access to 1184 the objects only to those principals (users) that have legitimate 1185 rights to indeed GET or SET (change/create/delete) them. 1187 9. IANA Considerations 1189 To be added in a later version of this document. 1191 10. References 1193 10.1. Normative References 1195 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1196 Requirement Levels", BCP 14, RFC 2119, March 1997. 1198 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1199 Schoenwaelder, Ed., "Structure of Management 1200 Information Version 2 (SMIv2)", STD 58, RFC 2578, 1201 April 1999. 1203 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1204 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 1205 STD 58, RFC 2579, April 1999. 1207 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 1208 "Conformance Statements for SMIv2", STD 58, RFC 2580, 1209 April 1999. 1211 10.2. Informative References 1213 [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction and 1214 Applicability Statement for Internet Standard Management 1215 Framework", RFC 3410, December 2002. 1217 [RFC3811] Nadeau, T., Ed., and J. Cucchiara, Ed., "Definitions of 1218 Textual Conventions (TCs) for Multiprotocol Label Switching 1219 (MPLS) Management", RFC 3811, June 2004. 1221 [RFC6378] Weingarten, Y., Osborne, E., Sprecher, N., Fulignoli, 1222 A., Ed., and Y. Weingarten, Ed., "MPLS-TP Linear 1223 Protection", October 2011. 1225 [MPLS-OAM-ID-STD-MIB] Sam Aldrin, M.Venkatesan, Kannan KV Sampath, 1226 Thomas D. Nadeau, Sami Boutros, Ping Pan, 1227 "MPLS-TP Operations, Administration, and 1228 Management (OAM) Identifiers Management 1229 Information Base (MIB)", ID 1230 draft-ietf-mpls-tp-oam-id-mib-01, October 2012. 1231 11. Acknowledgments 1233 The authors wish to thank Joan Cucchiara for her review as MIB 1234 Doctor, Joan's detailed comments were of great help for improving the 1235 quality of this document. 1237 12. Author's Address 1239 Kingston Smiler Selvaraj 1240 IpInfusion 1241 India 1242 Email: kingstons@ipinfusion.com 1244 Venkatesan Mahalingam 1245 Dell Inc. 1246 350 Holger way, San Jose, CA, USA 1247 Email: venkat.mahalingams@gmail.com 1249 Vishwas Manral 1250 Hewlet-Packard, Inc. 1251 19111 Pruneridge Ave., Cupertino, CA, 95014 1252 Phone: 408-447-1497 1253 Email: vishwas.manral@hp.com 1255 Daniel King 1256 Old Dog Consulting 1257 UK 1258 Email:daniel@olddog.co.uk 1260 Sam Aldrin 1261 Huawei Technologies, co. 1262 2330 Central Express Way, 1263 Santa Clara, CA 95051, USA 1264 Email: aldrin.ietf@gmail.com