idnits 2.17.1 draft-ietf-bfd-mpls-mib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- -- The document has examples using IPv4 documentation addresses according to RFC6890, but does not use any IPv6 documentation addresses. Maybe there should be IPv6 examples, too? Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (June 27, 2012) is 4314 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) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group 3 INTERNET-DRAFT Sam Aldrin 4 Intended Status: Standards Track Huawei Technologies 5 Expires: December 29, 2012 M.Venkatesan 6 Dell Inc. 7 Kannan KV Sampath 8 Aricent Group 9 Thomas D. Nadeau 10 Juniper Networks 12 June 27, 2012 14 BFD Management Information Base (MIB) extensions 15 for MPLS and MPLS-TP Networks 16 draft-ietf-bfd-mpls-mib-00 18 Abstract 20 This draft defines a portion of the Management Information Base (MIB) 21 for use with network management protocols in the Internet community. 22 In particular, it extends the BFD Management Information Base BFD- 23 STD-MIB and describes the managed objects for modeling Bidirectional 24 Forwarding Detection (BFD) protocol for MPLS and MPLS-TP networks. 26 Status of this Memo 28 This Internet-Draft is submitted to IETF in full conformance with the 29 provisions of BCP 78 and BCP 79. 31 Internet-Drafts are working documents of the Internet Engineering 32 Task Force (IETF), its areas, and its working groups. Note that 33 other groups may also distribute working documents as Internet- 34 Drafts. 36 Internet-Drafts are draft documents valid for a maximum of six months 37 and may be updated, replaced, or obsoleted by other documents at any 38 time. It is inappropriate to use Internet-Drafts as reference 39 material or to cite them other than as "work in progress." 41 The list of current Internet-Drafts can be accessed at 42 http://www.ietf.org/ietf/1id-abstracts.txt. 44 The list of Internet-Draft Shadow Directories can be accessed at 45 http://www.ietf.org/shadow.html. 47 This Internet-Draft will expire on December 29, 2012. 49 Copyright Notice 51 Copyright (c) 2012 IETF Trust and the persons identified as the 52 document authors. All rights reserved. 54 This document is subject to BCP 78 and the IETF Trust's Legal 55 Provisions Relating to IETF Documents 56 (http://trustee.ietf.org/license-info) in effect on the date of 57 publication of this document. Please review these documents 58 carefully, as they describe your rights and restrictions with respect 59 to this document. Code Components extracted from this document must 60 include Simplified BSD License text as described in Section 4.e of 61 the Trust Legal Provisions and are provided without warranty as 62 described in the Simplified BSD License. 64 Table of Contents 66 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 67 2. The Internet-Standard Management Framework . . . . . . . . . . 3 68 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 69 3.1 Conventions used in this document . . . . . . . . . . . . . 3 70 3.2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 71 4. Acronyms . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 72 5. Brief description of MIB Objects . . . . . . . . . . . . . . . 4 73 5.1. Extensions to the BFD session table (bfdSessionTable) . . . 4 74 5.2. Example of BFD session configuration . . . . . . . . . . . 6 75 5.2.1 Example of BFD Session configuration for MPLS TE 76 tunnel . . . . . . . . . . . . . . . . . . . . . . . . . 6 77 5.2.2 Example of BFD Session configuration for Maintenance 78 Entity of MPLS-TP TE tunnel . . . . . . . . . . . . . . 7 79 5.3. BFD objects for session performance counters . . . . . . . 9 80 5.4. Notification Objects . . . . . . . . . . . . . . . . . . . 9 81 6. BFD MPLS-MPLS-TP MIB Module Definition . . . . . . . . . . . . 10 82 7. Security Considerations . . . . . . . . . . . . . . . . . . . . 17 83 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 18 84 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 18 85 9.1 Normative References . . . . . . . . . . . . . . . . . . . . 18 86 9.2 Informative References . . . . . . . . . . . . . . . . . . . 18 87 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 19 88 11. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 19 90 1 Introduction 92 Current MIB for BFD as defined by BFD-STD-MIB is used for neighbor 93 monitoring in IP networks. The BFD session association to the 94 neighbors being monitored is done using the source and destination IP 95 addresses of the neighbors configured using the respective MIB 96 objects. 98 To monitor MPLS/MPLS-TP paths like tunnels or Pseudowires, there is a 99 necessity to identify or associate the BFD session to those paths. 101 This memo defines an portion of the Management Information Base (MIB) 102 for use with network management protocols in the Internet community. 103 In particular, it extends the BFD Management Information Base BFD- 104 STD-MIB and describes the managed objects to configure and/or monitor 105 Bidirectional Forwarding Detection (BFD) protocol for MPLS [BFD-MPLS] 106 and MPLS-TP networks [RFC6428]. 108 2. The Internet-Standard Management Framework 110 For a detailed overview of the documents that describe the current 111 Internet-Standard Management Framework, please refer to section 7 of 112 RFC3410 [RFC3410]. 114 Managed objects are accessed via a virtual information store, termed 115 the Management Information Base or MIB. MIB objects are generally 116 accessed through the Simple Network Management Protocol (SNMP). 117 Objects in the MIB are defined using the mechanisms defined in the 118 Structure of Management Information (SMI). This memo specifies a MIB 119 module that is compliant to the SMIv2, which is described in STD 58, 120 RFC2578, STD 58, RFC2579 and STD58, RFC2580. 122 3. Overview 124 3.1 Conventions used in this document 126 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 127 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 128 document are to be interpreted as described in RFC-2119 [RFC2119]. 130 3.2 Terminology 132 This document adopts the definitions, acronyms and mechanisms 133 described in [BFD], [BFD-1HOP], [BFD-MH], [BFD-MPLS], [RFC6428]. 134 Unless otherwise stated, the mechanisms described therein will not be 135 re-described here. 137 4. Acronyms 139 BFD: Bidirectional Forwarding Detection 140 IP: Internet Protocol 141 LSP: Label Switching Path 142 LSR: Label Switching Router 143 MIB: Management Information Base 144 MPLS: Multi-Protocol Label Switching 145 MPLS-TP: MPLS Transport Profile 146 ME: Maintenance Entity 147 MEG: Maintenance Entity Group 148 MEP: Maintenance Entity End-Point 149 PW: Pseudowire 150 TP: Transport Profile 152 5. Brief description of MIB Objects 154 The objects described in this section support the functionality 155 described in documents [BFD-MPLS] and [RFC6428]. The objects are 156 defined as an extension to the BFD base MIB defined by BFD-STD-MIB. 158 5.1. Extensions to the BFD session table (bfdSessionTable) 160 The BFD session table used to identify a BFD session between a pair 161 of nodes, as defined in BFD-STD-MIB, is extended with managed objects 162 to achieve the required functionality in MPLS and MPLS-TP networks as 163 described below: 165 1. SessionRole - Active/Passive role specification for the BFD 166 session configured on the node. Either end of a BFD session 167 can be configured as Active/Passive to determine which 168 end starts transmitting the BFD control packets. 170 2. SessionMode - Defines the mode in which BFD 171 session is running, defined as below: 172 i. CC - Only Continuity Check and RDI functionality is 173 performed. 175 ii. CV - Provides for Continuity Check, Connectivity 176 Verification and RDI functionalities to be 177 supported. 179 3. Timer Negotiation Flag - Provides for timer negotiation 180 to be enabled or disabled. This object can be used to tune 181 the detection of period-misconfiguration. 183 4. Map Type - Indicates the type of the path being monitored by 184 the BFD session. 186 This object can take the following values: 188 For BFD session over MPLS based paths: 190 nonTeIpv4 (1) - BFD session configured for Non-TE 191 Ipv4 path 192 nonTeIpv6 (2) - BFD session configured for Non-TE 193 Ipv6 path 194 teIpv4 (3) - BFD session configured for a TE 195 Ipv4 path 196 teIpv6 (4) - BFD session configured for a TE 197 Ipv6 path 198 pw (5) - BFD session configured for a PW 200 For MPLS-TP based paths: 202 mep (6) - BFD session configured for an MPLS-TP path 203 (Bidirectional tunnel, PW or Sections) will map to 204 the corresponding maintenance entity. 206 5. Map Pointer 208 A Row Pointer object which can be used to point to the first 209 accessible object in the respective instance of the table entry 210 identifying the path being monitored (mplsXCEntry/mplsTunnelEntry/ 211 pwEntry respectively for LSP/Tunnel/PW). 213 For NON-TE LSP, the Map pointer points to the corresponding 214 mplsXCEntry. 216 For TE based tunnel, the Map pointer points to the corresponding 217 instance of the mplsTunnelEntry. 219 For PW, this object points to the corresponding instance of 220 pwEntry. 222 For MPLS-TP paths, this object points to the corresponding 223 instance of mplsOamIdMeEntry configured to monitor the 224 MPLS-TP path associated with the BFD session. 226 6. Usage of existing object bfdSessType: 228 Additionally existing object "bfdSessType" in the base MIB can be 229 used with the already defined value multiHopOutOfBandSignaling(3) 230 to specify an OOB (Out of band) mechanism [E.g. LSP Ping] for 231 bootstrapping the BFD session. 233 5.2. Example of BFD session configuration 235 This section provides an example of BFD session configuration 236 for an MPLS and MPLS-TP TE tunnel. This example is only meant 237 to enable an understanding of the proposed extension and does not 238 illustrate every permutation of the MIB. 240 5.2.1 Example of BFD Session configuration for MPLS TE tunnel 242 This section provides an example BFD session configuration 243 for an MPLS TE tunnel. This example is only meant to enable 244 an understanding of the proposed extension and does not 245 illustrate every permutation of the MIB. 247 The following denotes the configured tunnel "head" entry: 249 In mplsTunnelTable: 250 { 251 mplsTunnelIndex = 100, 252 mplsTunnelInstance = 1, 253 mplsTunnelIngressLSRId = 192.0.2.1, 254 mplsTunnelEgressLSRId = 192.0.2.3, 255 mplsTunnelName = "Tunnel", 256 ... 257 mplsTunnelSignallingProto = none (1), 258 mplsTunnelSetupPrio = 0, 259 mplsTunnelHoldingPrio = 0, 260 mplsTunnelSessionAttributes = 0, 261 mplsTunnelLocalProtectInUse = false (0), 262 mplsTunnelResourcePointer = mplsTunnelResourceMaxRate.5, 263 mplsTunnelInstancePriority = 1, 264 mplsTunnelHopTableIndex = 1, 265 mplsTunnelIncludeAnyAffinity = 0, 266 mplsTunnelIncludeAllAffinity = 0, 267 mplsTunnelExcludeAnyAffinity = 0, 268 mplsTunnelPathInUse = 1, 269 mplsTunnelRole = head (1), 270 ... 271 mplsTunnelRowStatus = Active 272 } 274 BFD session parameters used to monitor this tunnel should be 275 configured on head-end as follows: 277 In bfdSessTable: 278 BfdSessEntry ::= SEQUENCE { 279 -- BFD session index 280 bfdSessIndex = 2, 281 bfdSessVersionNumber = 1, 282 -- LSP Ping used for OOB bootstrapping 283 bfdSessType = multiHopOutOfBandSignaling, 284 ... 285 bfdSessAdminStatus = start, 286 ... 287 bfdSessDemandModeDesiredFlag = false, 288 bfdSessControlPlaneIndepFlag = false, 289 bfdSessMultipointFlag = false, 290 bfdSessDesiredMinTxInterval = 100000, 291 bfdSessReqMinRxInterval = 100000, 292 ... 293 -- Indicates that the BFD session is to monitor 294 -- an MPLS TE tunnel 295 bfdMplsSessMapType = teIpv4(3), 297 -- OID of the first accessible object (mplsTunnelName) of 298 -- the mplsTunnelEntry identifying the MPLS TE tunnel (being 299 -- monitored using BFD) in the MPLS tunnel table. 300 -- A value of zeroDotzero indicates that no association 301 -- has been made as yet between the BFD session and the path 302 -- being monitored. 303 -- In the above OID example: 304 -- 100 -> Tunnel Index 305 -- 1 -> Tunnel instance 306 -- 3221225985 -> Ingress LSR Id 192.0.2.1 307 -- 3221225987 -> Egress LSR Id 192.0.2.3 308 bfdMplsSessMapPointer 309 = mplsTunnelName.100.1.3221225985.3221225987, 310 bfdSessRowStatus = createAndGo 311 } 313 Similarly BFD session would be configured on the tail-end of 314 the tunnel. Creating the above row will trigger 315 the bootstrapping of the session using LSP Ping and its 316 subsequent establishment over the path by de-multiplexing of 317 the control packets using the BFD session discriminators. 319 5.2.2 Example of BFD Session configuration for Maintenance Entity of 320 MPLS-TP TE tunnel 322 This example considers the OAM identifiers configuration on a 323 head-end LSR to manage and monitor a co-routed bidirectional MPLS 324 tunnel. 325 Only relevant objects which are applicable for IP based OAM 326 identifiers of co-routed MPLS tunnel are illustrated here. 328 In mplsOamIdMegTable: 330 { 331 -- MEG index (Index to the table) 332 mplsOamIdMegIndex = 1, 333 mplsOamIdMegName = "MEG1", 334 mplsOamIdMegOperatorType = ipCompatible (1), 335 mplsOamIdMegServiceType = lsp (1), 336 mplsOamIdMegMpLocation = perNode(1), 337 -- Mandatory parameters needed to activate the row go here 338 mplsOamIdMegRowStatus = createAndGo (4) 339 } 341 This will create an entry in the mplsOamIdMegTable to manage and 342 monitor the MPLS tunnel. 344 The following ME table is used to associate the path information 345 to a MEG. 347 In mplsOamIdMeTable: 348 { 349 -- ME index (Index to the table) 350 mplsOamIdMeIndex = 1, 351 -- MP index (Index to the table) 352 mplsOamIdMeMpIndex = 1, 353 mplsOamIdMeName = "ME1", 354 mplsOamIdMeMpIfIndex = 0, 355 -- Source MEP id is derived from the IP compatible MPLS tunnel 356 mplsOamIdMeSourceMepIndex = 0, 357 -- Source MEP id is derived from the IP compatible MPLS tunnel 358 mplsOamIdMeSinkMepIndex = 0, 359 mplsOamIdMeMpType = mep (1), 360 mplsOamIdMeMepDirection = down (2), 361 mplsOamIdMeProactiveOamPhbTCValue = 0, 362 mplsOamIdMeOnDemandOamPhbTCValue = 0, 363 -- RowPointer MUST point to the first accessible column of an 364 -- MPLS tunnel 365 mplsOamIdMeServicePointer = mplsTunnelName.1.1.1.2, 366 -- Mandatory parameters needed to activate the row go here 367 mplsOamIdMeRowStatus = createAndGo (4) 368 } 370 BFD session parameters used to monitor this tunnel should be 371 configured on head-end as follows: 373 In bfdSessTable: 374 BfdSessEntry ::= SEQUENCE { 375 -- BFD session index 376 bfdSessIndex = 2, 377 bfdSessVersionNumber = 1, 378 -- LSP Ping used for OOB bootstrapping 379 bfdSessType = multiHopOutOfBandSignaling, 380 ... 381 bfdSessAdminStatus = start, 382 ... 383 bfdSessDemandModeDesiredFlag = false, 384 bfdSessControlPlaneIndepFlag = false, 385 bfdSessMultipointFlag = false, 386 bfdSessDesiredMinTxInterval = 100000, 387 bfdSessReqMinRxInterval = 100000, 388 ... 389 -- Indicates that the BFD session is to monitor 390 -- a ME of an MPLS-TP TE tunnel 391 bfdMplsSessMapType = mep(6), 393 bfdMplsSessMapPointer 394 = mplsOamIdMeName.1.1.1, 395 bfdSessRowStatus = createAndGo 396 } 398 Similarly BFD session would be configured on the tail-end of 399 the tunnel. Creating the above row will trigger the bootstrapping 400 of the session using LSP Ping and its subsequent establishment 401 over the path by de-multiplexing of the control packets using 402 the BFD session discriminators. 404 5.3. BFD objects for session performance counters 406 BFD-STD-MIB defines BFD Session Performance Table 407 (bfdSessionPerfTable), for collecting per-session BFD performance 408 counters, as an extension to the bfdSessionTable. 410 The bfdSessionPerfTable is extended with the performance counters 411 to collect Mis-connectivity Defect, Loss of Continuity Defect 412 and RDI (Remote Defect Indication) counters. 414 1. bfdMplsSessPerfMisDefCount - Mis-connectivity defect count 415 for this BFD session. 416 2. bfdMplsSessPerfLocDefCount - Loss of continuity defect count for 417 this BFD session. 418 3. bfdMplsSessPerfRdiInCount - Total number of RDI messages 419 received for this BFD session. 420 4. bfdMplsSessPerfRdiOutCount - Total number of RDI messages sent 421 for this BFD session. 423 5.4. Notification Objects 425 To be added in the next version of this document. 427 6. BFD MPLS-MPLS-TP MIB Module Definition 428 BFD-EXT-STD-MIB DEFINITIONS ::= BEGIN 430 IMPORTS 431 MODULE-IDENTITY, OBJECT-TYPE, mib-2, 432 Counter32, zeroDotZero 433 FROM SNMPv2-SMI -- [RFC2578] 435 RowPointer,TruthValue,TEXTUAL-CONVENTION 436 FROM SNMPv2-TC -- [RFC2579] 438 MODULE-COMPLIANCE, OBJECT-GROUP 439 FROM SNMPv2-CONF -- [RFC2580] 441 bfdSessIndex 442 FROM BFD-STD-MIB; 444 bfdMplsMib MODULE-IDENTITY 445 LAST-UPDATED "201204190000Z" -- April 19 2012 446 ORGANIZATION "IETF Bidirectional Forwarding Detection 447 Working Group" 448 CONTACT-INFO 449 " 450 Sam Aldrin 451 Huawei Technologies 452 2330 Central Express Way, 453 Santa Clara, CA 95051, USA 454 Email: aldrin.ietf@gmail.com 456 Venkatesan Mahalingam 457 Dell Inc. 458 350 Holger Way, 459 San Jose, CA 95134, USA 460 Email: venkat.mahalingams@gmail.com 462 Kannan KV Sampath 463 Aricent 464 India 465 Email: Kannan.Sampath@aricent.com 467 Thomas D. Nadeau 468 Juniper Networks 469 10 Technology Park Drive, Westford, MA 01886 470 Email: tnadeau@juniper.net" 472 DESCRIPTION 473 " Copyright (c) 2012 IETF Trust and the persons identified 474 as the document authors. All rights reserved. 476 This MIB module is an initial version containing objects 477 to provide a proactive mechanism to detect faults using 478 BFD for MPLS and MPLS-TP networks" 479 REVISION "201204190000Z" -- April 19 2012 480 DESCRIPTION 481 " Initial version published as RFC xxx " 482 -- RFC Ed.: RFC-editor pls fill in xxxx 483 ::= { mib-2 XXX } -- XXX to be replaced with correct value 484 -- RFC Ed.: assigned by IANA 486 -- ------------------------------------------------------------ 487 -- groups in the MIB 488 -- ------------------------------------------------------------ 490 bfdMplsObjects OBJECT IDENTIFIER ::= { bfdMplsMib 0 } 491 bfdMplsConformance OBJECT IDENTIFIER ::= { bfdMplsMib 1 } 493 -- ------------------------------------------------------------ 494 -- Textual Conventions 495 -- ------------------------------------------------------------ 497 SessionMapTypeTC ::= TEXTUAL-CONVENTION 498 STATUS current 499 DESCRIPTION 500 "Used to indicate the type of MPLS or MPLS-TP path 501 associated to the session" 502 SYNTAX INTEGER { 503 nonTeIpv4(1), -- mapping into LDP IPv4 504 nonTeIpv6(2), -- mapping into LDP IPv6 505 teIpv4(3), -- mapping into TE IPv4 506 teIpv6(4), -- mapping into TE IPv6 507 pw(5), -- mapping into Pseudowires 509 mep(6) -- mapping into MEPs in MPLS-TP 511 } 513 -- ------------------------------------------------------------------ 514 -- BFD session table extensions for BFD on MPLS and MPLS-TP 515 -- ------------------------------------------------------------------ 516 -- bfdMplsSessTable - bfdSessTable Extension 518 bfdMplsSessTable OBJECT-TYPE 519 SYNTAX SEQUENCE OF BfdMplsSessEntry 520 MAX-ACCESS not-accessible 521 STATUS current 522 DESCRIPTION 523 "This table is an extension to the bfdSessTable for 524 configuring BFD sessions for MPLS or MPLS-TP paths." 525 ::= { bfdMplsObjects 1 } 527 bfdMplsSessEntry OBJECT-TYPE 528 SYNTAX BfdMplsSessEntry 529 MAX-ACCESS not-accessible 530 STATUS current 531 DESCRIPTION 532 "A row in this table extends a row in bfdSessTable." 533 INDEX { bfdSessIndex } 534 ::= { bfdMplsSessTable 1 } 536 BfdMplsSessEntry ::= SEQUENCE { 537 bfdMplsSessRole INTEGER, 538 bfdMplsSessMode INTEGER, 539 bfdMplsSessTmrNegotiate TruthValue, 540 bfdMplsSessMapType SessionMapTypeTC, 541 bfdMplsSessMapPointer RowPointer 542 } 544 bfdMplsSessRole OBJECT-TYPE 545 SYNTAX INTEGER { 546 active(1), 547 passive(2) 548 } 549 MAX-ACCESS read-create 550 STATUS current 551 DESCRIPTION 552 "This object specifies whether the system is playing the 553 active(1) role or the passive(2) role for this 554 BFD session." 555 REFERENCE 556 "RFC 5880, Section 6.1" 558 DEFVAL { active } 559 ::= { bfdMplsSessEntry 1 } 561 bfdMplsSessMode OBJECT-TYPE 562 SYNTAX INTEGER { 563 cc(1), 564 cv(2) 565 } 566 MAX-ACCESS read-create 567 STATUS current 568 DESCRIPTION 569 "This object specifies whether the BFD session is running 570 in Continuity Check(CC) or the Connectivity 571 Verification(CV) mode." 572 REFERENCE 573 "1.RFC6428, Proactive Connectivity Verification, 574 Continuity Check and Remote Defect Indication 575 for MPLS Transport Profile." 576 DEFVAL { cc } 577 ::= { bfdMplsSessEntry 2 } 579 bfdMplsSessTmrNegotiate OBJECT-TYPE 580 SYNTAX TruthValue 581 MAX-ACCESS read-create 582 STATUS current 583 DESCRIPTION 584 "This object specifies if timer negotiation is required for 585 the BFD session. When set to false, timer negotiation is 586 disabled" 587 DEFVAL { true } 588 ::= { bfdMplsSessEntry 3 } 590 bfdMplsSessMapType OBJECT-TYPE 591 SYNTAX SessionMapTypeTC 592 MAX-ACCESS read-create 593 STATUS current 594 DESCRIPTION 595 "This object indicates the type of path being monitored 596 by this BFD session entry." 597 DEFVAL { nonTeIpv4 } 598 ::= { bfdMplsSessEntry 4 } 600 bfdMplsSessMapPointer OBJECT-TYPE 601 SYNTAX RowPointer 602 MAX-ACCESS read-create 603 STATUS current 604 DESCRIPTION 605 "If bfdMplsSessMapType is nonTeIpv4(1) or nonTeIpv6(2), 606 then this object MUST contain zeroDotZero or point to 607 an instance of the mplsXCEntry indicating the LDP-based 608 LSP associated with this BFD session. 610 If bfdMplsSessMapType is teIpv4(3) or teIpv6(4), then 611 this object MUST contain zeroDotZero or point to 612 an instance of the mplsTunnelEntry indicating 613 the RSVP-based MPLS TE tunnel associated with this 614 BFD session. 616 If bfdMplsSessMapType is pw(5), then this object MUST 617 contain zeroDotZero or point to an instance of 618 the pwEntry indicating the MPLS Pseudowire associated 619 with this BFD session. 621 If bfdMplsSessMapTpye is mep(6). then this object MUST 622 contain zeroDotZero or point to an instance identifying 623 the mplsOamIdMeEntry configured for monitoring the MPLS-TP 624 path associated with this BFD session. 626 If this object points to a conceptual row instance 627 in a table consistent with bfdMplsSessMapType but this 628 instance does not currently exist then no valid 629 path is associated with this session entry. 631 If this object contains zeroDotZero then no valid path is 632 associated with this BFD session entry till it is 633 populated with a valid pointer consistent with 634 the value of bfdMplsSessMapType as explained above." 635 DEFVAL { zeroDotZero } 636 ::= { bfdMplsSessEntry 5 } 638 -- ------------------------------------------------------------------ 639 -- BFD Objects for Session performance 640 -- ----------------------------------------------------------------- 641 -- bfdMplsSessPerfTable - bfdSessPerfTable Extension 643 bfdMplsSessPerfTable OBJECT-TYPE 644 SYNTAX SEQUENCE OF BfdMplsSessPerfEntry 645 MAX-ACCESS not-accessible 646 STATUS current 647 DESCRIPTION 648 "This table is an extension to the bfdSessPerfTable" 649 ::= { bfdMplsObjects 2 } 651 bfdMplsSessPerfEntry OBJECT-TYPE 652 SYNTAX BfdMplsSessPerfEntry 653 MAX-ACCESS not-accessible 654 STATUS current 655 DESCRIPTION 656 "A row in this table extends the bfdSessPerfTable" 657 INDEX { bfdSessIndex } 658 ::= { bfdMplsSessPerfTable 1 } 660 BfdMplsSessPerfEntry ::= SEQUENCE { 661 bfdMplsSessPerfMisDefCount Counter32, 662 bfdMplsSessPerfLocDefCount Counter32, 663 bfdMplsSessPerfRdiInCount Counter32, 664 bfdMplsSessPerfRdiOutCount Counter32 665 } 667 bfdMplsSessPerfMisDefCount OBJECT-TYPE 668 SYNTAX Counter32 669 MAX-ACCESS read-only 670 STATUS current 671 DESCRIPTION 672 "This object gives a count of the mis-connectivity defects 673 detected for the BFD session. For instance, this count 674 will be incremented when the received BFD control packet 675 carries an incorrect globally unique source 676 MEP identifier." 677 ::= { bfdMplsSessPerfEntry 1 } 679 bfdMplsSessPerfLocDefCount OBJECT-TYPE 680 SYNTAX Counter32 681 MAX-ACCESS read-only 682 STATUS current 683 DESCRIPTION 684 "This object gives a count of the Loss of continuity 685 defects detected in MPLS and MPLS-TP paths" 686 ::= { bfdMplsSessPerfEntry 2 } 688 bfdMplsSessPerfRdiInCount OBJECT-TYPE 689 SYNTAX Counter32 690 MAX-ACCESS read-only 691 STATUS current 692 DESCRIPTION 693 "This object gives a count of the Remote Defect 694 Indications received for the BFD session." 695 ::= { bfdMplsSessPerfEntry 3 } 697 bfdMplsSessPerfRdiOutCount OBJECT-TYPE 698 SYNTAX Counter32 699 MAX-ACCESS read-only 700 STATUS current 701 DESCRIPTION 702 "This object gives a count of the Remote Defect 703 Indications sent by the BFD session" 704 ::= { bfdMplsSessPerfEntry 4 } 706 -- Module compliance 707 bfdMplsGroups 708 OBJECT IDENTIFIER ::= { bfdMplsConformance 1 } 710 bfdMplsCompliances 711 OBJECT IDENTIFIER ::= { bfdMplsConformance 2 } 713 -- Compliance requirement for fully compliant implementations. 715 bfdMplsModuleFullCompliance MODULE-COMPLIANCE 716 STATUS current 717 DESCRIPTION 718 "Compliance statement for agents that provide full 719 support for the BFD-EXT-STD-MIB module. " 721 MODULE -- This module. 723 MANDATORY-GROUPS { 724 bfdSessionExtGroup, 725 bfdSessionExtPerfGroup 726 } 727 ::= { bfdMplsCompliances 1 } 729 bfdMplsModuleReadOnlyCompliance MODULE-COMPLIANCE 730 STATUS current 731 DESCRIPTION 732 "Compliance requirement for implementations that only 733 provide read-only support for BFD-EXT-STD-MIB. Such devices 734 can then be monitored but cannot be configured using 735 this MIB module." 737 MODULE -- This module. 739 MANDATORY-GROUPS { 740 bfdSessionExtGroup, 741 bfdSessionExtPerfGroup 742 } 744 OBJECT bfdMplsSessRole 745 MIN-ACCESS read-only 746 DESCRIPTION "Write access is not required." 748 OBJECT bfdMplsSessMode 749 MIN-ACCESS read-only 750 DESCRIPTION "Write access is not required." 752 OBJECT bfdMplsSessTmrNegotiate 753 MIN-ACCESS read-only 754 DESCRIPTION "Write access is not required." 755 OBJECT bfdMplsSessMapType 756 MIN-ACCESS read-only 757 DESCRIPTION "Write access is not required." 759 OBJECT bfdMplsSessMapPointer 760 MIN-ACCESS read-only 761 DESCRIPTION "Write access is not required." 763 ::= { bfdMplsCompliances 2 } 765 -- Units of conformance. 767 bfdSessionExtGroup OBJECT-GROUP 768 OBJECTS { 769 bfdMplsSessRole, 770 bfdMplsSessMode, 771 bfdMplsSessTmrNegotiate, 772 bfdMplsSessMapType, 773 bfdMplsSessMapPointer 774 } 775 STATUS current 776 DESCRIPTION 777 "Collection of objects needed for BFD monitoring for 778 MPLS and MPLS-TP paths" 779 ::= { bfdMplsGroups 1 } 781 bfdSessionExtPerfGroup OBJECT-GROUP 782 OBJECTS { 783 bfdMplsSessPerfMisDefCount, 784 bfdMplsSessPerfLocDefCount, 785 bfdMplsSessPerfRdiInCount, 786 bfdMplsSessPerfRdiOutCount 787 } 788 STATUS current 789 DESCRIPTION 790 "Collection of objects needed to monitor the 791 performance of BFD sessions on MPLS and MPLS-TP 792 paths" 793 ::= { bfdMplsGroups 2 } 795 END 797 7. Security Considerations 799 To be added in the next version of this document. 801 8. IANA Considerations 803 To be added in the next version of this document. 805 9. References 807 9.1 Normative References 809 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 810 Requirement Levels", BCP 14, RFC 2119, March 1997. 812 [BFD] Katz, D. and D. Ward, "Bidirectional Forwarding 813 Detection (BFD)", RFC 5880, June 2010. 815 [BFD-1HOP] Katz, D. and D. Ward, "Bidirectional Forwarding 816 Detection (BFD) for IPv4 and IPv6 (Single Hop)", 817 RFC 5881, June 2010. 819 [BFD-MH] Katz, D. and D. Ward, "Bidirectional Forwarding 820 Detection (BFD) for Multihop Paths", RFC 5883, 821 June 2010. 823 [BFD-MPLS] Aggarwal, R. et.al., "Bidirectional Forwarding 824 Detection (BFD) for MPLS Label Switched Paths (LSPs)", 825 RFC 5884, June 2010 827 [RFC6428] Allan, D., Swallow, G., Drake, J., "Proactive 828 Connectivity Verification, Continuity Check and Remote 829 Defect indication for MPLS Transport Profile", RFC 830 6428, November 2011. 832 [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 833 "Structure of Management Information Version 2 (SMIv2)", 834 STD 58, RFC 2578, April 1999. 836 [RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 837 "Textual Conventions for SMIv2", STD 58, RFC 2579, April 838 1999. 840 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 841 "Conformance Statements for SMIv2", STD 58, RFC 2580, 842 April 1999. 844 9.2 Informative References 846 [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction 847 and Applicability Statement for Internet Standard 848 Management Framework", RFC 3410, December 2002. 850 10. Acknowledgments 852 The authors would like to thank Jeffrey Haas, Mukund Mani and 853 Lavanya Srivatsa for their valuable comments. 855 11. Authors' Addresses 857 Sam Aldrin 858 Huawei Technologies 859 2330 Central Express Way, 860 Santa Clara, CA 95051, USA 861 Email: aldrin.ietf@gmail.com 863 Venkatesan Mahalingam 864 Dell Inc. 865 350 Holger Way, 866 San Jose, CA 95134, USA 867 Email: venkat.mahalingams@gmail.com 869 Kannan KV Sampath 870 Aricent 871 India 872 Email: Kannan.Sampath@aricent.com 874 Thomas D. Nadeau 875 Juniper Networks 876 10 Technology Park Drive, Westford, MA 01886 877 Email: tnadeau@juniper.net