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