idnits 2.17.1 draft-ietf-mpls-mldp-mib-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 58 instances of too long lines in the document, the longest one being 18 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 989 has weird spacing: '... of the mplsM...' == Line 1017 has weird spacing: '... of the mplsM...' == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document date (July 7, 2019) is 1754 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC2020' is mentioned on line 436, but not defined == Missing Reference: 'RFC3414' is mentioned on line 1640, but not defined == Missing Reference: 'RFC3826' is mentioned on line 1640, but not defined == Missing Reference: 'RFC5591' is mentioned on line 1642, but not defined == Missing Reference: 'RFC5592' is mentioned on line 1643, but not defined == Missing Reference: 'RFC6353' is mentioned on line 1643, but not defined == Unused Reference: 'RFC3031' is defined on line 1672, but no explicit reference was found in the text == Unused Reference: 'RFC3811' is defined on line 1683, but no explicit reference was found in the text == Unused Reference: 'RFC5561' is defined on line 1705, but no explicit reference was found in the text == Unused Reference: 'RFC6389' is defined on line 1716, but no explicit reference was found in the text == Unused Reference: 'RFC6826' is defined on line 1720, but no explicit reference was found in the text == Unused Reference: 'RFC7060' is defined on line 1726, but no explicit reference was found in the text == Unused Reference: 'RFC7431' is defined on line 1731, but no explicit reference was found in the text == Unused Reference: 'RFC7715' is defined on line 1736, but no explicit reference was found in the text == Unused Reference: 'RFC2223' is defined on line 1748, but no explicit reference was found in the text == Unused Reference: 'RFC2629' is defined on line 1768, but no explicit reference was found in the text == Unused Reference: 'RFC4001' is defined on line 1772, but no explicit reference was found in the text == Unused Reference: 'RFC4181' is defined on line 1777, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 3410 ** Downref: Normative reference to an Informational RFC: RFC 7431 -- Obsolete informational reference (is this intentional?): RFC 2223 (Obsoleted by RFC 7322) -- Obsolete informational reference (is this intentional?): RFC 2629 (Obsoleted by RFC 7749) Summary: 3 errors (**), 0 flaws (~~), 22 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force K. Tiruveedhula, Ed. 3 Internet-Draft Juniper Networks 4 Intended status: Standards Track U. Joorde 5 Expires: January 8, 2020 Deutsche Telekom 6 A. Venkateswaran 7 Cisco Systems 9 July 7, 2019 11 Definitions of Managed Objects for the LDP Point-to-Multipoint and 12 Multipoint-to-Multipoint Label Switched Paths 13 draft-ietf-mpls-mldp-mib-05 15 Abstract 17 This memo defines a portion of the Management Information Base (MIB) 18 for use with network management protocols. In particular it defines 19 objects for managing multicast LDP point-to-multipoint (P2MP) and 20 multipoint-to-multipoint (MP2MP) Label Switched Paths. The MIB 21 module defined in this document is extension of LDP MIB defined in 22 RFC3815 which supports only for LDP point-to-point LSPs. 24 Status of This Memo 26 This Internet-Draft is submitted in full conformance with the 27 provisions of BCP 78 and BCP 79. 29 Internet-Drafts are working documents of the Internet Engineering 30 Task Force (IETF). Note that other groups may also distribute 31 working documents as Internet-Drafts. The list of current Internet- 32 Drafts is at https://datatracker.ietf.org/drafts/current/. 34 Internet-Drafts are draft documents valid for a maximum of six months 35 and may be updated, replaced, or obsoleted by other documents at any 36 time. It is inappropriate to use Internet-Drafts as reference 37 material or to cite them other than as "work in progress." 39 This Internet-Draft will expire on January 8, 2020. 41 Copyright Notice 43 Copyright (c) 2019 IETF Trust and the persons identified as the 44 document authors. All rights reserved. 46 This document is subject to BCP 78 and the IETF Trust's Legal 47 Provisions Relating to IETF Documents 48 (https://trustee.ietf.org/license-info) in effect on the date of 49 publication of this document. Please review these documents 50 carefully, as they describe your rights and restrictions with respect 51 to this document. Code Components extracted from this document must 52 include Simplified BSD License text as described in Section 4.e of 53 the Trust Legal Provisions and are provided without warranty as 54 described in the Simplified BSD License. 56 Table of Contents 58 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 59 2. The Internet-Standard Management Framework . . . . . . . . . 3 60 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 61 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4 62 5. Future Considerations . . . . . . . . . . . . . . . . . . . . 4 63 6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 64 6.1. Summary of mLDP Scalar Objects . . . . . . . . . . . . . 5 65 6.2. Summary of mLDP Table Objects . . . . . . . . . . . . . . 5 66 7. mLDP Scalar Objects . . . . . . . . . . . . . . . . . . . . . 5 67 7.1. mplsMldpP2mpCapable . . . . . . . . . . . . . . . . . . . 5 68 7.2. mplsMldpMp2mpCapable . . . . . . . . . . . . . . . . . . 6 69 7.3. mplsMldpMbbCapable . . . . . . . . . . . . . . . . . . . 6 70 7.4. mplsMldpMbbTime . . . . . . . . . . . . . . . . . . . . . 6 71 7.5. mplsMldpNumFecs . . . . . . . . . . . . . . . . . . . . . 6 72 7.6. mplsMldpNumFecsActive . . . . . . . . . . . . . . . . . . 6 73 7.7. mplsMldpPlrCapable . . . . . . . . . . . . . . . . . . . 6 74 7.8. mplsMldpMptCapable . . . . . . . . . . . . . . . . . . . 6 75 7.9. mplsMldpProtLsrCapable . . . . . . . . . . . . . . . . . 6 76 7.10. mplsMldpNodeProtCapable . . . . . . . . . . . . . . . . . 7 77 8. mLDP Table Objects . . . . . . . . . . . . . . . . . . . . . 7 78 8.1. LDP Peer Capability Table mplsLdpPeerCapabilityTable . . 7 79 8.2. mLDP Session Stats Table: mplsMldpSessionStatsTable . . . 7 80 8.3. mLDP Fec Table: mplsMldpFecTable . . . . . . . . . . . . 7 81 8.4. mLDP Fec Branch Traffic statistics Table: 82 mplsMldpFecBranchStatsTable . . . . . . . . . . . . . . . 7 83 8.5. mLDP Fec Upstream Session Table: 84 mplsMldpFecUpstreamSessTable . . . . . . . . . . . . . . 7 85 8.6. mLDP Interface Traffic statistics Table: 86 mplsMldpInterfaceStatsTable . . . . . . . . . . . . . . . 8 87 9. The mLDP Notifications . . . . . . . . . . . . . . . . . . . 8 88 10. Relationship to Other MIB Modules . . . . . . . . . . . . . . 8 89 10.1. Diagrammatic Representation . . . . . . . . . . . . . . 8 90 10.2. Relationship to the LSR MIB . . . . . . . . . . . . . . 9 91 10.3. Relationship to the LDP MIB . . . . . . . . . . . . . . 9 92 11. Multicast MPLS Label Distribution Protocol MIB Definitions . 10 93 12. Security Considerations . . . . . . . . . . . . . . . . . . . 35 94 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 95 14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 37 96 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 37 97 15.1. Normative References . . . . . . . . . . . . . . . . . . 37 98 15.2. Informative References . . . . . . . . . . . . . . . . . 39 99 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 39 101 1. Introduction 103 This memo defines a portion of the Management Information Base (MIB) 104 for use with network management protocols. In particular it defines 105 objects for managing multicast LDP point-to-multipoint (P2MP) and 106 multipoint-to-multipoint (MP2MP) Label Switched Paths. The MIB 107 module defined in this document is extension of LDP MIB defined in 108 RFC3815 which supports only for LDP point-to-point LSPs. 110 The RFC3815 describes only unicast Managed objects for the Label 111 distribution protocol. The RFC6388 describes LDP protocol extensions 112 for the point to multipoint and multipoint to multipoint LSPs. The 113 RFC6826 describes multicast LDP inband signalling for P2MP and MP2MP 114 LSPs. 116 This document defines a MIB module for managing and controlling mLDP 117 P2MP and MP2MP LSPs. It builds on the objects and tables defined in 118 [RFC3815] for mLDP MIB. 120 2. The Internet-Standard Management Framework 122 For a detailed overview of the documents that describe the current 123 Internet-Standard Management Framework, please refer to section 7 of 124 RFC3410. 126 Managed objects are accessed via a virtual information store, termed 127 the Management Information Base or MIB. MIB objects are generally 128 accessed through the Simple Network Management Protocol (SNMP). 129 Objects in the MIB are defined using the mechanisms defined in the 130 Structure of Management Information (SMI). This memo specifies a MIB 131 module that is compliant to the SMIv2, which is described in STD 58, 132 RFC2578 [RFC2578], STD 58, RFC2579 [RFC2579] and STD 58, RFC2580 133 [RFC2580]. 135 3. Conventions 137 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 138 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 139 document are to be interpreted as described in BCP 14, RFC2119 140 [RFC2119]. 142 4. Overview 144 This document focusses on the management of following multicast LDP 145 (mLDP) features, which were defined after unicast LDP [RFC5036]. 147 RFC6388: Label Distribution Protocol Extensions for Point-to- 148 Multipoint and Multipoint-to-Multipoint Label Switched Paths. 150 RFC6826: Multipoint LDP In-Band Signaling for Point-to-Multipoint 151 and Multipoint-to-Multipoint Label Switched Paths. 153 RFC7060: Using LDP Multipoint Extensions on Targeted LDP Sessions. 155 RFC7431: Multicast only Fast Re-Route. 157 RFC7715: mLDP Node Protection. 159 For all the above features, the mLDP MIB needs to include the 160 following information: 162 - Session Capability (P2MP, MP2MP) information: configured 163 capability, negotiated capability. 165 - mLDP FECs: include opaque information (Generic LSP Identifier, 166 source and group address) and MoFRR enable. 168 - Primary and backup upstream session when mLDP MoFRR enabled. 170 - Active and inactive upstream session for make before break. 172 - mLDP Traffic stats per mLDP Fec: The traffic stats for mLDP fec. 174 - mLDP Traffic stats per Interface: The mLDP traffic stats per 175 Interface. 177 - Notifications when mLDP Fec LSP up, down. 179 5. Future Considerations 181 Any new opaque TLVs added for any other mLDP features, the opaque 182 value object in the mplsMldpFecTable need to be enhanced accordingly. 184 6. Structure of the MIB Module 186 This section describes the structure of the mLDP MIB. In this MIB 187 MPLS-MLDP-STD-MIB, scalar objects, table objects and notifications 188 are defined. Following section describes in details about each 189 object. 191 6.1. Summary of mLDP Scalar Objects 193 New scalar objects mplsMldpP2mpCapable and mplsMldpMp2mpCapable are 194 defined to provide the mLDP capabilities of P2MP, MP2MP support. 196 New scalar objects mplsMldpMbbCapable and mplsMldpMbbTime are defined 197 to provide MBB capability information. 199 New scalar object mplsMldpNumFecs which will give the total number of 200 mLDP FECs setup on the LSR. 202 Another New scalar object mplsMldpNumFecsActive, which will give the 203 total number of active mLDP FECs. 205 New scalar objects mplsMldpPlrCapable, mplsMldpMptCapable, 206 mplsMldpProtLsrCapable and mplsMldpNodeProtCapable are defined to 207 provide mLDP node protection capabilities. 209 6.2. Summary of mLDP Table Objects 211 mplsLdpPeerCapabilityTable to include peer capability information. 213 mplsMldpSessionStatsTable : This table contains the number of mLDP 214 FECs received and advertised to a particular LDP session. 216 mplsMldpFecTable: This table is similar to point to point 217 mplsLdpFecTable and will have mLDP specific Fec information. 219 mplsMldpFecBranchStatsTable : This table contains the traffic 220 statistics for the given mLDP FECs on particular interface. 222 mplsMldpFecUpstreamSessTable : Includes the upstream session info for 223 the particular mLDP Fec and also includes the primary or backup 224 upstream session, that may be used for mLDP MoFRR. 226 mplsMldpInterfaceStatsTable : This table contains the traffic 227 statistics for all mLDP related FECs. 229 7. mLDP Scalar Objects 231 The following scalars are defined in this MIB Module. 233 7.1. mplsMldpP2mpCapable 235 The mplsMldpP2mpCapable scalar object denotes whether the LSR is 236 capable of supporting multicast LDP with Point-to-Multipoint 237 capability. 239 7.2. mplsMldpMp2mpCapable 241 The mplsMldpMp2mpCapable scalar object denotes whether the LSR is 242 capable of supporting multicast LDP with Multipoint-to-Multipoint 243 LSPs. 245 7.3. mplsMldpMbbCapable 247 The mplsMldpMbbCapable scalar object denotes whether the LSR is 248 capable of supporting multicast LDP with MBB (make before break) 249 feature mentioned in the section 8 of RFC 6388 . 251 7.4. mplsMldpMbbTime 253 The mplsMldpMbbTime scalar object denotes MBB time for which LSR is 254 waiting for MBB Ack from upstream node. This timer helps LSR to 255 prevent waiting indefinitely for the MBB Notification from upstream 256 node. 258 7.5. mplsMldpNumFecs 260 The mplsMldpNumFecs provides a read-only counter of the number of 261 mLDP FECs setup on this LSR. 263 7.6. mplsMldpNumFecsActive 265 The mplsMldpNumFecsActive provides a read-only counter of the number 266 of mLDP FECs Active on this LSR. 268 7.7. mplsMldpPlrCapable 270 The mplsMldpPlrCapable scalar object denotes whether the LSR is 271 capable of supporting PLR capability as specified in the section 5.1 272 of RFC7715. 274 7.8. mplsMldpMptCapable 276 The mplsMldpMptCapable scalar object denotes whether the LSR is 277 capable of supporting MPT capability as specified in the section 5.2 278 of RFC7715. 280 7.9. mplsMldpProtLsrCapable 282 The mplsMldpProtLsrCapable scalar object denotes whether the LSR is 283 capable of supporting the "Protected LSR" capability as specified in 284 the section 5.3 of RFC7715. 286 7.10. mplsMldpNodeProtCapable 288 The mplsMldpNodeProtCapable scalar object denotes whether the LSR is 289 capable of supporting the "Node Protection" capability as specified 290 in the section 5.4 of RFC7715. 292 8. mLDP Table Objects 294 8.1. LDP Peer Capability Table mplsLdpPeerCapabilityTable 296 The new table mplsLdpPeerCapabilityTable is read-only table, which 297 contains learned capability information from an LDP peer. This table 298 augments the mplsLdpPeerTable, which is defined in RFC 3815. This is 299 defined in this MIB as it is not defined in the standard LDP MIB 300 (RFC3815) . 302 8.2. mLDP Session Stats Table: mplsMldpSessionStatsTable 304 The mplsMldpSessionStatsTable is a read-only table which contains 305 mLDP statistical information on sessions. This table augments the 306 mplsLdpSessionStatsTable, which is defined in the RFC 3815. 308 8.3. mLDP Fec Table: mplsMldpFecTable 310 The mplsMldpFecTable is a table which contains FEC (Forwarding 311 Equivalence Class) information relating to point to multi-point and 312 multipoint to multipoint LDP LSP. Each entry/row represents a single 313 FEC Element. This table is similar LDP LSP FEC Table, 314 mplsLdpLspFecTable, which is defined in the RFC 3815, which 315 associates FECs with the LSPs. 317 8.4. mLDP Fec Branch Traffic statistics Table: 318 mplsMldpFecBranchStatsTable 320 This table mplsMldpFecBranchStatsTable gives information about the 321 number of packets and number of bytes sent out on particualr 322 downstream session or on outgoing interface. 324 8.5. mLDP Fec Upstream Session Table: mplsMldpFecUpstreamSessTable 326 The mplsMldpFecUpstreamSessTable is a read-only table which contains 327 mLDP upstream session information for mLDP Fec. This table is 328 similar to mplsInSegmentLdpLspTable. This table will also have 329 information about primary, backup upstream session, and also 330 indicates whether the label is in MBB request or MBB Ack received 331 state. 333 8.6. mLDP Interface Traffic statistics Table: 334 mplsMldpInterfaceStatsTable 336 This table mplsMldpInterfaceStatsTable gives information about the 337 number of mLDP packets and number of mLDP bytes sent and received on 338 a particular interface for all mLDP FECs. 340 9. The mLDP Notifications 342 The RFC 3815 defined some of the notifications related to session and 343 P2P Fec. In this MIB, the following notification added to support 344 mLDP features. 346 The mplsMldpFecUp and mplsMldpFecDown notifications are generated 347 when mLDP FEC changes the state to UP and Down. 349 The mplsMldpMoFrrStatusChange notification is generated when mLDP 350 MoFRR status switches from primary to backup path and vice versa. 352 10. Relationship to Other MIB Modules 354 This section describes relationships between MIB tables defined in 355 this document as part of MPLS-MLDP-STD-MIB, and the tables defined in 356 MPLS-LDP-STD-MIB [RFC3815] and MPLS-LSR-STD-MIB [RFC3813]. 358 The Figure 1 shows the diagrammatic representation of the 359 relationship between MPLS-MLDP-STD-MIB, MPLS-LDP-STD-MIB and MPLS- 360 LSR-STD-MIB. An arrow in the Figure shows that the MIB table pointed 361 from contains a reference to the MIB table pointed to. 363 10.1. Diagrammatic Representation 364 mplsMldpFecTable 365 | 366 | 367 v 368 mplsLdpLspFecTable 369 | | | 370 | | +----------------+ 371 | | | 372 | +---------------+ v 373 | | mplsMldpFecUpstreamSessTable 374 +--->mplsXCTable--+ | 375 | | 376 | | 377 | | 378 | mplsMldpFecBranchStatsTable 379 | | 380 | | 381 | | 382 mplsInSegmentTable<------+ | 383 | | 384 v | 385 mplsOutSegmentTable<-+ 387 Figure 1 : Dependencies Between MIB Tables 389 Figure 1 391 10.2. Relationship to the LSR MIB 393 The LSR MIB [RFC3813] have below tables, which cross connects the 394 incoming label to outgoing label. Below Tables will be used for mLDP 395 also in the similar way as in the point to point LDP LSPs. 397 mplsXCTable 399 mplsInSegmentTable 401 mplsOutSegmentTable 403 10.3. Relationship to the LDP MIB 405 The MIB module defined in this document is extension of MPLS-LDP-STD- 406 MIB to support multicast LDP features. 408 Below optional tables in MPLS-LDP-STD-MIB, will also be used in mLDP 409 for associating the mLDP LSPs to LSR-MIB tables. 411 mplsLdpLspFecTable 413 mplsInSegmentLdpLspTable 415 mplsOutSegmentLdpLspTable 417 The LDP Peer Capability Table mplsLdpPeerCapabilityTable augments the 418 mplsLdpPeerTable which is defined in MPLS-LDP-STD-MIB. 420 The mLDP Session Stats Table mplsMldpSessionStatsTable augments 421 mplsLdpSessionStatsTable which is defined in MPLS-LDP-STD-MIB. 423 11. Multicast MPLS Label Distribution Protocol MIB Definitions 425 MPLS-MLDP-STD-MIB DEFINITIONS ::= BEGIN 426 IMPORTS 427 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 428 Unsigned32, Counter32, Counter64 429 FROM SNMPv2-SMI -- RFC 2578 430 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 431 FROM SNMPv2-CONF -- RFC 2580 432 TimeStamp 433 FROM SNMPv2-TC -- RFC 2579 435 InterfaceIndex 436 FROM IF-MIB -- [RFC2020] 438 mplsStdMIB, MplsLdpIdentifier 439 FROM MPLS-TC-STD-MIB -- RFC 3811 441 MplsIndexType 442 FROM MPLS-LSR-STD-MIB -- RFC 3813 444 IndexInteger 445 FROM DIFFSERV-MIB -- RFC 3289 447 InetAddress, InetAddressType 448 FROM INET-ADDRESS-MIB -- RFC 4001 450 mplsLdpEntityLdpId, mplsLdpEntityIndex, 451 mplsLdpPeerLdpId, mplsLdpPeerEntry 452 FROM MPLS-LDP-STD-MIB -- RFC 3815 453 ; 455 mplsMldpStdMIB MODULE-IDENTITY 456 LAST-UPDATED "201907070000Z" -- July 7, 2019 00:00:00 EST 457 ORGANIZATION "Multiprotocol Label Switching (mpls) 458 Working Group" 459 CONTACT-INFO 461 " Kishore Tiruveedhula 462 Juniper Networks 464 Email: kishoret@juniper.net 466 Uwe Joorde 467 Deutsche Telekom 468 Email: Uwe.Joorde@telekom.de 470 Arvind Venkateswaran 471 Cisco Systems 472 EMail: arvvenka@cisco.com 474 Comments about this document should be emailed 475 directly to the MPLS working group mailing list at 476 mpls@lists.ietf.org" 478 DESCRIPTION 479 "Copyright (c) 2009 IETF Trust and the persons identified as 480 the document authors. All rights reserved. 482 This document is subject to BCP 78 and the IETF Trust's 483 Legal Provisions Relating to IETF Documents in effect on the 484 date of publication of this document 485 (http://trustee.ietf.org/license-info). Please review these 486 documents carefully, as they describe your rights and 487 restrictions with respect to this document. 489 The initial version of this MIB module was published in 490 RFC XXXX. For full legal notices see the RFC itself or see: 491 http://www.ietf.org/copyrights/ianamib.html 492 -- RFC Editor. Please replace XXXX with the RFC number for this 493 -- document and remove this note. 495 This MIB module contains managed object definitions for mLDP LSPS 496 defined in Label Distribution Protocol Extensions Point-to-Multipoint and 497 Multipoint-to-Multipoint Label Switched Paths, RFC 6388, November 498 2011." 500 REVISION "201907070000Z" -- July 7, 2019 00:00:00 EST 501 DESCRIPTION 502 "Initial version issued as part of RFC XXXX." 503 -- RFC Editor. Please replace XXXX with the RFC number for this 504 -- document and remove this note. 506 ::= { mplsStdMIB YYY } 507 -- RFC Editor. Please replace YYY with the codepoint issued by IANA 508 -- and remove this note. 510 -- Top level components of this MIB module. 512 -- notifications 514 mplsMldpNotifications OBJECT IDENTIFIER ::= { mplsMldpStdMIB 0 } 515 -- tables, scalars 516 mplsMldpScalars OBJECT IDENTIFIER ::= { mplsMldpStdMIB 1 } 517 mplsMldpObjects OBJECT IDENTIFIER ::= { mplsMldpStdMIB 2 } 519 -- MPLS mLDP LSP scalars. 521 mplsMldpP2mpCapable OBJECT-TYPE 522 SYNTAX INTEGER { 523 enable(1), 524 disable(2) 525 } 526 MAX-ACCESS read-only 527 STATUS current 528 DESCRIPTION 529 "This object provides the P2MP capability of the LSR." 531 REFERENCE 532 "Section 2.1 of [RFC6388]." 534 ::= { mplsMldpScalars 1 } 536 mplsMldpMp2mpCapable OBJECT-TYPE 537 SYNTAX INTEGER { 538 enable(1), 539 disable(2) 540 } 541 MAX-ACCESS read-only 542 STATUS current 543 DESCRIPTION 544 "This object provides MP2MP capability of the LSR." 546 REFERENCE 547 "Section 3.1 of [RFC6388]." 549 ::= { mplsMldpScalars 2 } 551 mplsMldpMbbCapable OBJECT-TYPE 552 SYNTAX INTEGER { 553 enable(1), 554 disable(2) 555 } 556 MAX-ACCESS read-only 557 STATUS current 559 DESCRIPTION 560 "This object provides MBB (make before break) capability of the LSR." 562 REFERENCE 563 "Section 8.3 of [RFC6388]." 565 ::= { mplsMldpScalars 3 } 567 mplsMldpMbbTime OBJECT-TYPE 568 SYNTAX Unsigned32 (1..300) 569 UNITS "seconds" 570 MAX-ACCESS read-only 571 STATUS current 572 DESCRIPTION 573 "The 32-bit unsigned integer value provides the time for waiting MBB Ack 574 from upstream node." 576 DEFVAL { 30 } 577 ::= { mplsMldpScalars 4 } 579 mplsMldpNumFecs OBJECT-TYPE 580 SYNTAX Unsigned32 581 MAX-ACCESS read-only 582 STATUS current 583 DESCRIPTION 584 "The number of active and passive mLdp Fecs on this device." 586 ::= { mplsMldpScalars 5 } 588 mplsMldpNumFecsActive OBJECT-TYPE 589 SYNTAX Unsigned32 590 MAX-ACCESS read-only 591 STATUS current 592 DESCRIPTION 593 "The number of mLdp FECs Active on this device. The mLDP FEC is 594 considered active if the mplsMldpFecOperStatus is up(1)." 596 ::= { mplsMldpScalars 6 } 598 mplsMldpPlrCapable OBJECT-TYPE 599 SYNTAX INTEGER { 600 enable(1), 601 disable(2) 602 } 603 MAX-ACCESS read-only 604 STATUS current 605 DESCRIPTION 607 "This object provides Point of Local Repair (PLR) 608 capability of the LSR." 610 REFERENCE 611 "Section 5.1 of RFC7715]." 613 ::= { mplsMldpScalars 7 } 615 mplsMldpMptCapable OBJECT-TYPE 616 SYNTAX INTEGER { 617 enable(1), 618 disable(2) 619 } 620 MAX-ACCESS read-only 621 STATUS current 622 DESCRIPTION 623 "This object provides Merge Point (MPT) capability of the LSR." 625 REFERENCE 626 "Section 5.2 of RFC7715]." 628 ::= { mplsMldpScalars 8 } 630 mplsMldProtLsrCapable OBJECT-TYPE 631 SYNTAX INTEGER { 632 enable(1), 633 disable(2) 634 } 635 MAX-ACCESS read-only 636 STATUS current 637 DESCRIPTION 638 "This object provides Protected LSR capability." 640 REFERENCE 641 "Section 5.3 of RFC7715]." 643 ::= { mplsMldpScalars 9 } 645 mplsMldProtNodeProtCapable OBJECT-TYPE 646 SYNTAX INTEGER { 647 enable(1), 648 disable(2) 649 } 650 MAX-ACCESS read-only 651 STATUS current 652 DESCRIPTION 653 "This object provides Node Protection capability of the LSR." 655 REFERENCE 656 "Section 5.3 of RFC7715]." 658 ::= { mplsMldpScalars 10 } 660 -- End of MPLS mLDP scalars. 662 -- MPLS mLDP tables. 664 -- 665 -- The MPLS LDP Peer Capability Table 666 -- 668 mplsLdpPeerCapabilityTable OBJECT-TYPE 669 SYNTAX SEQUENCE OF MplsLdpPeerCapabilityEntry 670 MAX-ACCESS not-accessible 671 STATUS current 672 DESCRIPTION 673 "This table will have learned information relating to Mldp. 674 This table AUGMENTS the mplsLdpPeerTable." 676 ::= { mplsMldpObjects 1 } 678 mplsLdpPeerCapabilityEntry OBJECT-TYPE 679 SYNTAX MplsLdpPeerCapabilityEntry 680 MAX-ACCESS not-accessible 681 STATUS current 682 DESCRIPTION 683 "Information about a single Peer which is related 684 to a Session. This table augments 685 the mplsLdpPeerTable." 687 AUGMENTS { mplsLdpPeerEntry } 688 ::= { mplsLdpPeerCapabilityTable 1 } 690 MplsLdpPeerCapabilityEntry ::= SEQUENCE { 691 mplsLdpPeerCapability BITS 692 } 694 mplsLdpPeerCapability OBJECT-TYPE 695 SYNTAX BITS { 696 default (0), 697 p2mp (1), 698 mp2mp(2), 699 mbb (3), 700 upstreamLabelAssignment (4), 701 dynamic (5), 702 plr (6), 703 mpt (7), 704 protLsr (8), 705 nodeProt (9) 706 } 707 MAX-ACCESS read-only 708 STATUS current 709 DESCRIPTION 710 " This will indicate the LDP capability information about peer. 711 The default indicates P2P Capability. 712 The p2mp indicates peer supports P2MP Capability. 713 The mp2mp indicates peer supports MP2MP Capability. 714 The mbb indicates peer supports MBB Capability. 715 The upstream-label-assignment indicates peer supports Upstream label 716 assignment Capability. 717 The dynamic indicates peer supports dynamic Capability. 718 The plr indicates Point of Local Repair Capability. 719 The mpt indicates Point of Merge Point Capability. 720 The prot-lsr indicates Protected LSR Capability. 721 The node-prot indicates Node Protection LSR Capability. 722 " 724 REFERENCE 725 "Section 2.1 of RFC6388 for P2MP Capability TLV. 726 and the section 3.1 of RFC6388 for MP2MP Capability TLV. 727 The RFC6388 for MBB Capability TLV. 728 Section 9 of RFC5561 for Dynamic Capability Announcement TLV. 730 Section 3 of RFC6389 for Upstream Label Assignment Capability TLV. 731 Section 5 of RFC7715 describes for Point of Local Repair (plr) 732 capability, Merge Point (mpt) capability, 733 The Protected LSR (port-lsr) and Node Protection (node-prot) Capability. " 735 ::= { mplsLdpPeerCapabilityEntry 1 } 737 -- 738 -- The MPLS mLDP Session Statistics Table 739 -- 741 mplsMldpSessionStatsTable OBJECT-TYPE 742 SYNTAX SEQUENCE OF MplsMldpSessionStatsEntry 743 MAX-ACCESS not-accessible 745 STATUS current 746 DESCRIPTION 747 "A table of statistics related to mLDP on Sessions. 748 This table AUGMENTS the mplsLdpSessionStatsTable, which 749 AUGMENTS the mplsLdpPeerTable." 750 ::= { mplsMldpObjects 2 } 752 mplsMldpSessionStatsEntry OBJECT-TYPE 753 SYNTAX MplsMldpSessionStatsEntry 754 MAX-ACCESS not-accessible 755 STATUS current 756 DESCRIPTION 757 "An entry in this table represents mLDP statistical 758 information on a single session between an LDP 759 Entity and LDP Peer." 761 AUGMENTS { mplsLdpPeerEntry } 762 ::= { mplsMldpSessionStatsTable 1 } 764 MplsMldpSessionStatsEntry ::= SEQUENCE { 765 mplsMldpSessionStatsNumFecsSent Counter32, 766 mplsMldpSessionStatsNumMbbReqSentState Counter32, 767 mplsMldpSessionStatsNumFecsRcvd Counter32, 768 mplsMldpSessionStatsNumMbbReqRcvdState Counter32, 769 mplsMldpSessionStatsNumMbbResetAckByTimer Counter32 770 } 772 mplsMldpSessionStatsNumFecsSent OBJECT-TYPE 773 SYNTAX Counter32 774 MAX-ACCESS read-only 775 STATUS current 776 DESCRIPTION 777 "This object counts the number of mLDP FECs sent on this 778 session. If the FEC is withdrawn, then this number is 779 decremented. 781 Discontinuities in the value of this counter can occur 782 at re-initialization of the management system, and at 783 other times as indicated by the value of 784 mplsLdpSessionDiscontinuityTime." 786 ::= { mplsMldpSessionStatsEntry 1 } 788 mplsMldpSessionStatsNumMbbReqSentState OBJECT-TYPE 789 SYNTAX Counter32 790 MAX-ACCESS read-only 792 STATUS current 793 DESCRIPTION 794 "This object counts the number of mLDP FECs sent on this 795 session and waiting for MBB Ack. This counter will get incremented 796 when MBB req sent for a label on this session and will get 797 decremented when the MBB Ack received." 799 ::= { mplsMldpSessionStatsEntry 2 } 801 mplsMldpSessionStatsNumFecsRcvd OBJECT-TYPE 802 SYNTAX Counter32 803 MAX-ACCESS read-only 804 STATUS current 805 DESCRIPTION 806 "This object counts the number of mLDP FECs received on this 807 session. If the FEC is withdrawn from the downstream session, 808 then this is decremented. 810 Discontinuities in the value of this counter can occur 811 at re-initialization of the management system, and at 812 other times as indicated by the value of 813 mplsLdpSessionDiscontinuityTime." 815 ::= { mplsMldpSessionStatsEntry 3 } 817 mplsMldpSessionStatsNumMbbReqRcvdState OBJECT-TYPE 818 SYNTAX Counter32 819 MAX-ACCESS read-only 820 STATUS current 821 DESCRIPTION 822 "This object counts the number of mLDP FECs received on this 823 session and waiting for sending MBB Ack. This counter will get 824 incremented when MBB req is received for a label on this session 825 and will get decremented when the MBB Ack sent." 827 ::= { mplsMldpSessionStatsEntry 4 } 829 mplsMldpSessionStatsNumMbbResetAckByTimer OBJECT-TYPE 830 SYNTAX Counter32 831 MAX-ACCESS read-only 832 STATUS current 833 DESCRIPTION 834 "This object counts the number mLDP FECs for which the MBB Ack is 835 reset by MBB timer, in which the LSR is waiting for MBB ack." 837 ::= { mplsMldpSessionStatsEntry 5 } 839 -- 840 -- Mpls mLDP FEC Table 841 -- 843 mplsMldpFecTable OBJECT-TYPE 844 SYNTAX SEQUENCE OF MplsMldpFecEntry 845 MAX-ACCESS not-accessible 846 STATUS current 847 DESCRIPTION 848 "This table represents the FEC 849 (Forwarding Equivalence Class) 850 Information associated with a mLDP LSP." 852 ::= { mplsMldpObjects 3 } 854 mplsMldpFecEntry OBJECT-TYPE 855 SYNTAX MplsMldpFecEntry 856 MAX-ACCESS not-accessible 857 STATUS current 858 DESCRIPTION 859 "Each row represents a single mLDP FEC Element." 860 INDEX { mplsLdpEntityLdpId, 861 mplsLdpEntityIndex, 862 mplsMldpFecIndex 863 } 865 ::= { mplsMldpFecTable 1 } 867 MplsMldpFecEntry ::= SEQUENCE { 868 mplsMldpFecIndex IndexInteger, 869 mplsMldpFecType INTEGER, 870 mplsMldpFecRootAddrType InetAddressType, 871 mplsMldpFecRootAddr InetAddress, 872 mplsMldpFecOpaqueType INTEGER, 873 mplsMldpFecOpaqueGenLspId Unsigned32, 874 mplsMldpFecOpaqueTransitSourceOrBidirAddrType InetAddressType, 875 mplsMldpFecOpaqueTransitSourceOrBidirAddr InetAddress, 876 mplsMldpFecOpaqueTransitGroupAddrType InetAddressType, 877 mplsMldpFecOpaqueTransitGroupAddr InetAddress, 878 mplsMldpFecAdminStatus INTEGER, 879 mplsMldpFecOperStatus INTEGER, 880 mplsMldpFecMoFrr INTEGER, 881 mplsMldpFecLsrState INTEGER, 882 mplsMldpFecUpTime TimeStamp 883 } 885 mplsMldpFecIndex OBJECT-TYPE 887 SYNTAX IndexInteger 888 MAX-ACCESS not-accessible 889 STATUS current 890 DESCRIPTION 891 "The index which uniquely identifies this entry." 893 ::= { mplsMldpFecEntry 1 } 895 mplsMldpFecType OBJECT-TYPE 896 SYNTAX INTEGER { 897 p2mp(6), 898 mp2mpUpstream(7), 899 mp2mpDownstream(8) 900 } 901 MAX-ACCESS read-only 902 STATUS current 903 DESCRIPTION 904 "The type of the FEC. If the value of this object 905 is 6, then it is P2MP Fec Type, and 7, 8 are correspond to 906 MP2MP upstream and downstream type." 908 REFERENCE 909 "RFC6388, Section 2.2. The P2MP FEC Element and the section 3.3 910 for the MP2MP Fec elements." 912 ::= { mplsMldpFecEntry 2 } 914 mplsMldpFecRootAddrType OBJECT-TYPE 915 SYNTAX InetAddressType 916 MAX-ACCESS read-only 917 STATUS current 918 DESCRIPTION 919 "The value of this object is the type of the 920 Internet address. The value of this object, 921 decides how the value of the mplsMldpFecRootAddr object 922 is interpreted." 923 REFERENCE 924 "RFC6388, Section 2.2. The P2MP FEC Element and the section 3.3 925 for the MP2MP Fec elements." 927 ::= { mplsMldpFecEntry 3 } 929 mplsMldpFecRootAddr OBJECT-TYPE 930 SYNTAX InetAddress 931 MAX-ACCESS read-only 932 STATUS current 933 DESCRIPTION 935 "The value of this object is interpreted based 936 on the value of the mplsMldpFecRootAddrType object. 937 This is ingress node address for the mLDP LSP." 939 REFERENCE 940 "RFC6388, Section 2.2. The P2MP FEC Element and the section 3.3 941 for the MP2MP Fec elements." 943 ::= { mplsMldpFecEntry 4 } 945 mplsMldpFecOpaqueType OBJECT-TYPE 946 SYNTAX INTEGER { 947 genericLspId(1), 948 transitIpv4Source(3), 949 transitIpv6Source(4), 950 transitIpv4Bidir(5), 951 transitIpv6Bidir(6) 952 } 953 MAX-ACCESS read-only 954 STATUS current 955 DESCRIPTION 956 "This is opaque type of the mLDP FEC. The value of this object is 957 shown below. 959 1 - The Generic LSP Identifier 960 3 - Transit IPv4 Source TLV 961 4 - Transit IPv6 Source TLV 962 5 - Transit IPv4 Bidir TLV 963 6 - Transit IPv6 Bidir TLV. 964 " 965 ::= { mplsMldpFecEntry 5 } 967 mplsMldpFecOpaqueGenLspId OBJECT-TYPE 968 SYNTAX Unsigned32 969 MAX-ACCESS read-only 970 STATUS current 971 DESCRIPTION 972 "The 32-bit unsigned integer value which is to represent Generic 973 LSP ID. This value is only valid if the mplsMldpFecOpaqueType is 974 genericLspId(1), otherwise 0 must be returned." 976 REFERENCE 977 "RFC6388, Section 2.3.1." 979 ::= { mplsMldpFecEntry 6 } 981 mplsMldpFecOpaqueTransitSourceOrBidirAddrType OBJECT-TYPE 983 SYNTAX InetAddressType 984 MAX-ACCESS read-only 985 STATUS current 986 DESCRIPTION 987 "The value of this object is the type of the 988 Internet address. The value of this object, 989 decides how the value of the mplsMldpFecOpaqueTransitSourceOrBidirAddr 990 object is interpreted." 991 REFERENCE 992 "RFC6826, Section 3.1." 994 ::= { mplsMldpFecEntry 7 } 996 mplsMldpFecOpaqueTransitSourceOrBidirAddr OBJECT-TYPE 997 SYNTAX InetAddress 998 MAX-ACCESS read-only 999 STATUS current 1000 DESCRIPTION 1001 "The value of this object is interpreted based 1002 on the value of the mplsMldpFecOpaqueTransitSourceOrBidirAddrType 1003 object. This is source node address for the mLDP inband LSP." 1005 REFERENCE 1006 "RFC6826, Section 3.1." 1008 ::= { mplsMldpFecEntry 8 } 1010 mplsMldpFecOpaqueTransitGroupAddrType OBJECT-TYPE 1011 SYNTAX InetAddressType 1012 MAX-ACCESS read-only 1013 STATUS current 1014 DESCRIPTION 1015 "The value of this object is the type of the 1016 Internet address. The value of this object, 1017 decides how the value of the mplsMldpFecOpaqueTransitGroupAddr 1018 object is interpreted." 1020 REFERENCE 1021 "RFC6826, Section 3.2." 1023 ::= { mplsMldpFecEntry 9 } 1025 mplsMldpFecOpaqueTransitGroupAddr OBJECT-TYPE 1026 SYNTAX InetAddress 1027 MAX-ACCESS read-only 1028 STATUS current 1029 DESCRIPTION 1030 "The value of this object is interpreted based 1032 on the value of the mplsMldpFecOpaqueTransitGroupAddrType 1033 object. This is group node address for the mLDP inband LSP." 1035 REFERENCE 1036 "RFC6826, Section 3.2." 1038 ::= { mplsMldpFecEntry 10 } 1040 mplsMldpFecAdminStatus OBJECT-TYPE 1041 SYNTAX INTEGER { 1042 up(1), -- ready to pass data 1043 down(2) -- out of service 1044 } 1045 MAX-ACCESS read-only 1046 STATUS current 1047 DESCRIPTION 1048 "Indicates the admin status of this mLDP FEC." 1050 DEFVAL { up } 1052 ::= { mplsMldpFecEntry 11 } 1054 mplsMldpFecOperStatus OBJECT-TYPE 1055 SYNTAX INTEGER { 1056 up(1), -- ready to pass data 1057 down(2) -- out of service 1058 } 1059 MAX-ACCESS read-only 1060 STATUS current 1061 DESCRIPTION 1062 "Indicates the actual operational status of this mLDP Fec." 1064 ::= { mplsMldpFecEntry 12 } 1066 mplsMldpFecMoFrr OBJECT-TYPE 1067 SYNTAX INTEGER { 1068 enable(1), 1069 disable(2) 1070 } 1071 MAX-ACCESS read-only 1072 STATUS current 1073 DESCRIPTION 1074 "This object provides whether MoFRR enabled for this mLDP FEC. 1075 on this mLDP FEC. As mentioned in the section 3.2 of [ RFC7431 ], 1076 When this is enabled, then mLDP may select two upstream sessions, 1077 one is primary and other one is backup. The backup traffic is 1078 discarded when the primary upstream session is UP. When the 1080 primary upstream session goes down, the traffic from the backup 1081 upstream session will be forwarded to downstream. 1082 " 1084 ::= { mplsMldpFecEntry 13 } 1086 mplsMldpFecLsrState OBJECT-TYPE 1087 SYNTAX INTEGER { 1088 egress(1), 1089 bud(2), 1090 transit(3), 1091 ingress(4) 1093 } 1094 MAX-ACCESS read-only 1095 STATUS current 1096 DESCRIPTION 1097 "Indicates the role of FEC either egress, bud, transit or ingress" 1099 ::= { mplsMldpFecEntry 14 } 1101 mplsMldpFecUpTime OBJECT-TYPE 1102 SYNTAX TimeStamp 1103 MAX-ACCESS read-only 1104 STATUS current 1105 DESCRIPTION 1106 "This values shows Fec UP time. This is time since mplsMldpFecOperStatus is UP." 1108 ::= { mplsMldpFecEntry 15 } 1110 -- MPLS mLDP LSP Branch Traffic Stats Table. 1112 mplsMldpFecBranchStatsTable OBJECT-TYPE 1113 SYNTAX SEQUENCE OF MplsMldpFecBranchStatsEntry 1114 MAX-ACCESS not-accessible 1115 STATUS current 1116 DESCRIPTION 1117 "This table provides mLDP Fec branch MPLS Traffic Stats 1118 information." 1120 ::= { mplsMldpObjects 4 } 1122 mplsMldpFecBranchStatsEntry OBJECT-TYPE 1123 SYNTAX MplsMldpFecBranchStatsEntry 1124 MAX-ACCESS not-accessible 1125 STATUS current 1126 DESCRIPTION 1127 "An entry in this table is created by the LSR for each 1128 downstream branch (out-segment) from this LSR for this mLDP 1130 LSP. Each downstream session may represent a single out-segment. 1132 Each entry in the table is indexed by the four identifiers 1133 of the mLDP LSP, and the out-segment that identifies the 1134 outgoing branch." 1136 INDEX { mplsLdpEntityLdpId, 1137 mplsLdpEntityIndex, 1138 mplsMldpFecBranchFecIndex, 1139 mplsMldpFecBranchOutSegIndex 1140 } 1142 ::= { mplsMldpFecBranchStatsTable 1 } 1144 MplsMldpFecBranchStatsEntry ::= SEQUENCE { 1145 mplsMldpFecBranchFecIndex MplsIndexType, 1146 mplsMldpFecBranchOutSegIndex MplsIndexType, 1147 mplsMLdpFecBranchPeerLdpId MplsLdpIdentifier, 1148 mplsMldpFecBranchStatsPackets Counter64, 1149 mplsMldpFecBranchStatsBytes Counter64, 1150 mplsMldpFecBranchStatsDiscontinuityTime TimeStamp 1151 } 1153 mplsMldpFecBranchFecIndex OBJECT-TYPE 1154 SYNTAX MplsIndexType 1155 MAX-ACCESS not-accessible 1156 STATUS current 1157 DESCRIPTION 1158 "This index identifies the mLDP FEC entry in the 1159 mplsMldpFecTable. This is same as mplsMldpFecIndex." 1161 ::= { mplsMldpFecBranchStatsEntry 1 } 1163 mplsMldpFecBranchOutSegIndex OBJECT-TYPE 1164 SYNTAX MplsIndexType 1165 MAX-ACCESS not-accessible 1166 STATUS current 1167 DESCRIPTION 1168 "This object identifies an outgoing branch from this mLDP LSP 1169 Its value is unique within the context of the mLDP LSP. 1171 This contains the same value as the mplsOutSegmentIndex in the 1172 MPLS-LSR-STD-MIBs mplsOutSegmentTable." 1174 ::= { mplsMldpFecBranchStatsEntry 2 } 1176 mplsMLdpFecBranchPeerLdpId OBJECT-TYPE 1177 SYNTAX MplsLdpIdentifier 1178 MAX-ACCESS read-only 1179 STATUS current 1180 DESCRIPTION 1181 "This object identifies an outgoing branch peer LDP ID for this 1182 mLDP LSP. Its value is unique within the context of the mLDP LSP. 1183 On Egress node, this value could be 0.0.0.0:00 as there will no 1184 downstream LDP session." 1186 ::= { mplsMldpFecBranchStatsEntry 3 } 1188 mplsMldpFecBranchStatsPackets OBJECT-TYPE 1189 SYNTAX Counter64 1190 MAX-ACCESS read-only 1191 STATUS current 1192 DESCRIPTION 1193 "This object represent the 64-bit value, which gives the number 1194 of packets forwarded by the mLDP LSP onto this branch. 1195 This object should be read in conjunction with 1196 mplsMldpFecBranchStatsDiscontinuityTime." 1198 ::= { mplsMldpFecBranchStatsEntry 4 } 1200 mplsMldpFecBranchStatsBytes OBJECT-TYPE 1201 SYNTAX Counter64 1202 MAX-ACCESS read-only 1203 STATUS current 1204 DESCRIPTION 1205 "This object represent the 64-bit value, which gives the number 1206 of bytes forwarded by the mLDP LSP onto this branch. 1207 This object should be read in conjunction with 1208 mplsMldpFecBranchStatsDiscontinuityTime." 1210 ::= { mplsMldpFecBranchStatsEntry 5 } 1212 mplsMldpFecBranchStatsDiscontinuityTime OBJECT-TYPE 1213 SYNTAX TimeStamp 1214 MAX-ACCESS read-only 1215 STATUS current 1216 DESCRIPTION 1217 "The value of sysUpTime on the most recent occasion at which 1218 any one or more of this rows Counter32 or Counter64 objects 1219 experienced a discontinuity. If no such discontinuity has 1220 occurred since the last re-initialization of the local 1221 management subsystem, then this object contains a zero 1222 value." 1223 ::= { mplsMldpFecBranchStatsEntry 6 } 1225 -- End of mplsMldpFecBranchStatsTable 1226 -- MPLS mLDP LSP Upstream Session Table. 1228 mplsMldpFecUpstreamSessTable OBJECT-TYPE 1229 SYNTAX SEQUENCE OF MplsMldpFecUpstreamSessEntry 1230 MAX-ACCESS not-accessible 1231 STATUS current 1232 DESCRIPTION 1233 "This table provides mLDP Fec upstream Session information." 1235 ::= { mplsMldpObjects 5 } 1237 mplsMldpFecUpstreamSessEntry OBJECT-TYPE 1238 SYNTAX MplsMldpFecUpstreamSessEntry 1239 MAX-ACCESS not-accessible 1240 STATUS current 1241 DESCRIPTION 1242 "An entry in this table is created by the LSR for each 1243 upstream session (in-segment) from this LSR for this mLDP 1244 LSP. Each upstream session may represent a single in-segment. 1246 Each entry in the table is indexed by the four identifiers 1247 of the mLDP LSP, and the in-segment that identifies the 1248 incoming traffic." 1249 INDEX { mplsLdpEntityLdpId, 1250 mplsLdpEntityIndex, 1251 mplsLdpPeerLdpId, 1252 mplsMldpFecUpstreamSessFecIndex, 1253 mplsMldpFecUpstreamSessInSegIndex 1254 } 1256 ::= { mplsMldpFecUpstreamSessTable 1 } 1258 MplsMldpFecUpstreamSessEntry ::= SEQUENCE { 1259 mplsMldpFecUpstreamSessFecIndex MplsIndexType, 1260 mplsMldpFecUpstreamSessInSegIndex MplsIndexType, 1261 mplsMldpFecUpstreamSessPrimary INTEGER, 1262 mplsMldpFecUpstreamSessActive INTEGER, 1263 mplsMldpFecUpstreamSessPackets Counter64, 1264 mplsMldpFecUpstreamSessBytes Counter64, 1265 mplsMldpFecUpstreamSessDiscontinuityTime TimeStamp 1266 } 1268 mplsMldpFecUpstreamSessFecIndex OBJECT-TYPE 1269 SYNTAX MplsIndexType 1270 MAX-ACCESS not-accessible 1271 STATUS current 1272 DESCRIPTION 1273 "This index identifies the mLDP FEC entry in the 1274 mplsMldpFecTable." 1276 ::= { mplsMldpFecUpstreamSessEntry 1 } 1278 mplsMldpFecUpstreamSessInSegIndex OBJECT-TYPE 1279 SYNTAX MplsIndexType 1280 MAX-ACCESS not-accessible 1281 STATUS current 1282 DESCRIPTION 1283 "This object identifies an upstream session from this mLDP LSP 1284 Its value is unique within the context of the mLDP LSP. 1286 This contains the same value as the mplsInSegmentIndex in the 1287 MPLS-LSR-STD-MIBs mplsInSegmentTable." 1289 ::= { mplsMldpFecUpstreamSessEntry 2 } 1291 mplsMldpFecUpstreamSessPrimary OBJECT-TYPE 1292 SYNTAX INTEGER { 1293 primary(1), 1294 backup(2) 1295 } 1296 MAX-ACCESS read-only 1297 STATUS current 1298 DESCRIPTION 1299 "This indicated wether the received traffic from upstream is 1300 primary or backup. This is valid only if the MoFRR 1301 (mplsMldpFecMoFrr) is enabled on this FEC." 1303 ::= { mplsMldpFecUpstreamSessEntry 3 } 1305 mplsMldpFecUpstreamSessActive OBJECT-TYPE 1306 SYNTAX INTEGER { 1307 active(1), 1308 inactive(2) 1309 } 1310 MAX-ACCESS read-only 1311 STATUS current 1312 DESCRIPTION 1313 "This indicates whether the upstream session is active, means the 1314 LSR programmed the forwarding engine to receive the traffic from 1315 this upstream session. This will be Inactive if the LSR is wating 1316 for MBB Ack." 1317 ::= { mplsMldpFecUpstreamSessEntry 4 } 1319 mplsMldpFecUpstreamSessPackets OBJECT-TYPE 1320 SYNTAX Counter64 1321 MAX-ACCESS read-only 1322 STATUS current 1323 DESCRIPTION 1324 "This object represent the 64-bit value, which gives the number 1325 of packets received by the mLDP LSP from this upstream 1326 session. This object should be read in conjunction with 1327 mplsMldpFecUpstreamSessDiscontinuityTime." 1329 ::= { mplsMldpFecUpstreamSessEntry 5 } 1331 mplsMldpFecUpstreamSessBytes OBJECT-TYPE 1332 SYNTAX Counter64 1333 MAX-ACCESS read-only 1334 STATUS current 1335 DESCRIPTION 1336 "This object represent the 64-bit value, which gives the number 1337 of bytes received by the mLDP LSP from this upstream 1338 session. This object should be read in conjunction with 1339 mplsMldpFecUpstreamSessDiscontinuityTime." 1341 ::= { mplsMldpFecUpstreamSessEntry 6 } 1343 mplsMldpFecUpstreamSessDiscontinuityTime OBJECT-TYPE 1344 SYNTAX TimeStamp 1345 MAX-ACCESS read-only 1346 STATUS current 1347 DESCRIPTION 1348 "The value of sysUpTime on the most recent occasion at which 1349 any one or more of this rows Counter32 or Counter64 objects 1350 experienced a discontinuity. If no such discontinuity has 1351 occurred since the last re-initialization of the local 1352 management subsystem, then this object contains a zero 1353 value." 1354 ::= { mplsMldpFecUpstreamSessEntry 7 } 1356 -- End of mplsMldpFecBranchStatsTable 1358 -- MPLS mLDP Interface Traffic Stats Table. 1360 mplsMldpInterfaceStatsTable OBJECT-TYPE 1361 SYNTAX SEQUENCE OF MplsMldpInterfaceStatsEntry 1362 MAX-ACCESS not-accessible 1363 STATUS current 1364 DESCRIPTION 1365 "This table provides mLDP Traffic Stats on specified interface." 1367 ::= { mplsMldpObjects 6 } 1369 mplsMldpInterfaceStatsEntry OBJECT-TYPE 1370 SYNTAX MplsMldpInterfaceStatsEntry 1371 MAX-ACCESS not-accessible 1372 STATUS current 1373 DESCRIPTION 1374 "An entry in this table is created by the LSR for each 1375 downstream branch (out-segment) from this LSR for this mLDP 1376 LSP. Each downstream session may represent a single out-segment. 1378 Each entry in the table is indexed by the four identifiers 1379 of the mLDP LSP, and the out-segment that identifies the 1380 outgoing branch." 1382 INDEX { mplsMldpInterfaceIndex 1383 } 1385 ::= { mplsMldpInterfaceStatsTable 1 } 1387 MplsMldpInterfaceStatsEntry ::= SEQUENCE { 1388 mplsMldpInterfaceIndex InterfaceIndex, 1389 mplsMldpInterfaceStatsSentPackets Counter64, 1390 mplsMldpInterfaceStatsSentBytes Counter64, 1391 mplsMldpInterfaceStatsRecvPackets Counter64, 1392 mplsMldpInterfaceStatsRecvBytes Counter64 1393 } 1395 mplsMldpInterfaceIndex OBJECT-TYPE 1396 SYNTAX InterfaceIndex 1397 MAX-ACCESS not-accessible 1398 STATUS current 1399 DESCRIPTION 1400 "This index identifies the specific interface. " 1402 ::= { mplsMldpInterfaceStatsEntry 1 } 1404 mplsMldpInterfaceStatsSentPackets OBJECT-TYPE 1405 SYNTAX Counter64 1406 MAX-ACCESS read-only 1407 STATUS current 1408 DESCRIPTION 1409 "This is 64 bit value, which gives the number of packets 1410 forwarded by all mLDP LSPs onto this interface." 1412 ::= { mplsMldpInterfaceStatsEntry 2 } 1414 mplsMldpInterfaceStatsSentBytes OBJECT-TYPE 1415 SYNTAX Counter64 1416 MAX-ACCESS read-only 1417 STATUS current 1418 DESCRIPTION 1419 "This is 64 bit value, which gives the number of bytes 1420 forwarded by all mLDP LSPs onto this interface." 1422 ::= { mplsMldpInterfaceStatsEntry 3 } 1424 mplsMldpInterfaceStatsRecvPackets OBJECT-TYPE 1425 SYNTAX Counter64 1426 MAX-ACCESS read-only 1427 STATUS current 1428 DESCRIPTION 1429 "This is 64 bit value, which gives the number of packets 1430 received by all mLDP LSPs from this interface." 1432 ::= { mplsMldpInterfaceStatsEntry 4 } 1434 mplsMldpInterfaceStatsRecvBytes OBJECT-TYPE 1435 SYNTAX Counter64 1436 MAX-ACCESS read-only 1437 STATUS current 1438 DESCRIPTION 1439 "This is 64 bit value, which gives the number of bytes 1440 received by all mLDP LSPs from this interface." 1442 ::= { mplsMldpInterfaceStatsEntry 5 } 1444 -- End of mplsMldpInterfaceStatsTable 1446 -- Notifications. 1448 mplsMldpFecUp NOTIFICATION-TYPE 1449 OBJECTS { 1450 mplsMldpFecAdminStatus, 1451 mplsMldpFecOperStatus 1452 } 1453 STATUS current 1454 DESCRIPTION 1455 "This notification is generated when a mplsMldpFecOperStatus 1456 object changes from down to up." 1458 ::= { mplsMldpNotifications 1 } 1460 mplsMldpFecDown NOTIFICATION-TYPE 1461 OBJECTS { 1462 mplsMldpFecAdminStatus, 1463 mplsMldpFecOperStatus 1464 } 1465 STATUS current 1466 DESCRIPTION 1467 "This notification is generated when a mplsMldpFecOperStatus 1468 object changes from up to down." 1470 ::= { mplsMldpNotifications 2 } 1472 mplsMldpMoFrrStatusChange NOTIFICATION-TYPE 1473 OBJECTS { 1474 mplsMldpFecUpstreamSessPrimary 1475 } 1476 STATUS current 1477 DESCRIPTION 1478 "This notification is generated when a mplsMldpFecUpstreamSessPrimary 1479 object changes from primary to backup and vice versa." 1481 ::= { mplsMldpNotifications 3 } 1483 -- End of notifications. 1485 --**************************************************************** 1486 -- Module Conformance Statement 1487 --**************************************************************** 1489 mplsMldpConformance OBJECT IDENTIFIER ::= { mplsMldpStdMIB 3 } 1490 mplsMldpGroups OBJECT IDENTIFIER ::= { mplsMldpConformance 1 } 1491 mplsMldpCompliances OBJECT IDENTIFIER ::= { mplsMldpConformance 2 } 1493 mplsMldpModuleCompliance MODULE-COMPLIANCE 1494 STATUS current 1495 DESCRIPTION 1496 "The Module is implemented with support 1497 for read-only. Only monitoring is available 1498 when using this MODULE-COMPLIANCE." 1500 MODULE -- this module 1501 MANDATORY-GROUPS { mplsMldpScalarsGroup, 1502 mplsMldpObjectsGroup, 1503 mplsMldpNotificationsGroup 1504 } 1506 ::= { mplsMldpCompliances 1 } 1508 -- units of conformance 1510 mplsMldpScalarsGroup OBJECT-GROUP 1511 OBJECTS { 1512 mplsMldpP2mpCapable, 1513 mplsMldpP2mpCapable, 1514 mplsMldpMbbCapable, 1515 mplsMldpMbbTime, 1516 mplsMldpNumFecs, 1517 mplsMldpNumFecsActive, 1518 mplsMldpPlrCapable, 1519 mplsMldpMp2mpCapable, 1520 mplsMldpMptCapable, 1521 mplsMldProtLsrCapable, 1522 mplsMldProtLsrCapable, 1523 mplsMldProtNodeProtCapable, 1524 mplsLdpPeerCapability 1525 } 1526 STATUS current 1527 DESCRIPTION 1528 "A collection of objects providing basic statistics and 1529 capability information of mLDP implementation." 1530 ::= { mplsMldpGroups 1 } 1532 mplsMldpObjectsGroup OBJECT-GROUP 1533 OBJECTS { 1534 mplsMldpSessionStatsNumFecsSent, 1535 mplsMldpSessionStatsNumMbbReqSentState, 1536 mplsMldpSessionStatsNumFecsRcvd, 1537 mplsMldpSessionStatsNumFecsSent, 1538 mplsMldpSessionStatsNumMbbReqRcvdState, 1539 mplsMldpSessionStatsNumMbbResetAckByTimer, 1540 mplsMldpFecType, 1541 mplsMldpFecRootAddrType, 1542 mplsMldpFecRootAddr, 1543 mplsMldpFecOpaqueType, 1544 mplsMldpFecOpaqueGenLspId, 1545 mplsMldpFecOpaqueTransitSourceOrBidirAddrType, 1546 mplsMldpFecOpaqueTransitSourceOrBidirAddr, 1547 mplsMldpFecOpaqueTransitGroupAddrType, 1548 mplsMldpFecOpaqueTransitGroupAddr, 1549 mplsMldpFecAdminStatus, 1550 mplsMldpFecOperStatus, 1551 mplsMldpFecMoFrr, 1552 mplsMldpFecLsrState, 1553 mplsMldpFecUpTime, 1554 mplsMLdpFecBranchPeerLdpId, 1555 mplsMldpFecBranchStatsPackets, 1556 mplsMldpFecBranchStatsBytes, 1557 mplsMldpFecBranchStatsDiscontinuityTime, 1558 mplsMldpFecUpstreamSessPrimary, 1559 mplsMldpFecUpstreamSessActive, 1560 mplsMldpFecUpstreamSessPackets, 1561 mplsMldpFecUpstreamSessBytes, 1562 mplsMldpFecUpstreamSessDiscontinuityTime, 1563 mplsMldpInterfaceStatsSentPackets, 1564 mplsMldpInterfaceStatsSentBytes, 1565 mplsMldpInterfaceStatsRecvPackets, 1566 mplsMldpInterfaceStatsRecvBytes 1567 } 1568 STATUS current 1569 DESCRIPTION 1570 "A collection of objects providing basic information 1571 regarding mLDP implementation." 1572 ::= { mplsMldpGroups 2 } 1574 mplsMldpNotificationsGroup NOTIFICATION-GROUP 1575 NOTIFICATIONS { mplsMldpFecUp, 1576 mplsMldpFecDown, 1577 mplsMldpMoFrrStatusChange 1578 } 1579 STATUS current 1580 DESCRIPTION 1581 "A collection of notifications for mLDP implementation." 1582 ::= { mplsMldpGroups 3 } 1584 END 1586 12. Security Considerations 1588 This MIB module is useful for the configuration of certain objects 1589 and monitoring of mLDP LSPs. 1591 There are no management objects defined in this MIB module that have 1592 a MAX-ACCESS clause of read-write and/or read-create. So, if this 1593 MIB module is implemented correctly, then there is no risk that an 1594 intruder can alter or create any management objects of this MIB 1595 module via direct SNMP SET operations. 1597 Some of the readable objects in this MIB module (i.e., objects with a 1598 MAX-ACCESS other than not-accessible) may be considered sensitive or 1599 vulnerable in some network environments. It is thus important to 1600 control even GET and/or NOTIFY access to these objects and possibly 1601 to even encrypt the values of these objects when sending them over 1602 the network via SNMP. These are the tables and objects and their 1603 sensitivity/vulnerability: 1605 o mplsMldpFecTable 1607 o mplsLdpPeerCapabilityTable 1609 o mplsMldpSessionStatsTable 1611 o mplsMldpFecBranchStatsTable 1613 o mplsMldpFecUpstreamSessTable 1615 o mplsMldpInterfaceStatsTable 1617 o mplsMldpNumFecs 1619 o mplsMldpNumFecsActive 1621 o mplsMldpMbbTime 1623 Above listed tables and objects show information about the mLDP LSPs, 1624 its route through the network, and its traffic statistics. Knowledge 1625 of this information could be used to compromise the network, or 1626 simply to breach confidentiality. If an Administrator does not want 1627 to reveal this information, these tables and objects should be 1628 considered sensitive/vulnerable. 1630 SNMP versions prior to SNMPv3 did not include adequate security. 1631 Even if the network itself is secure (for example by using IPsec), 1632 there is no control as to who on the secure network is allowed to 1633 access and GET/SET (read/change/create/delete) the objects in this 1634 MIB module. 1636 Implementations SHOULD provide the security features described by the 1637 SNMPv3 framework (see [RFC3410]), and implementations claiming 1638 compliance to the SNMPv3 standard MUST include full support for 1639 authentication and privacy via the User-based Security Model (USM) 1640 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 1641 MAY also provide support for the Transport Security Model (TSM) 1642 [RFC5591] in combination with a secure transport such as SSH 1643 [RFC5592] or TLS/DTLS [RFC6353]. 1645 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1646 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1647 enable cryptographic security. It is then a customer/operator 1648 responsibility to ensure that the SNMP entity giving access to an 1649 instance of this MIB module is properly configured to give access to 1650 the objects only to those principals (users) that have legitimate 1651 rights to indeed GET or SET (change/create/delete) them. 1653 13. IANA Considerations 1655 This is new MPLS MIB module, contained in this document and IANA is 1656 requested to assign an oid (mplsStdMIB YYY) under the mplsStdMIB 1657 subtree to the MPLS-MLDP-STD-MIB module specified in this document. 1659 Below mplsMldpFecType values are defined in the section 2.2 and 3.3 1660 of RFC6388. p2mp : 6 mp2mpUpstream : 7 mp2mpDownstream : 8 1662 14. Acknowledgments 1664 The authors wish to thank Santosh Esale, Alia Atlas and Martin Ehlers 1665 for doing the detailed review. Thanks to Adrian Farrel and Raveendra 1666 Torvi for their input to this work and for many helpful suggestions. 1668 15. References 1670 15.1. Normative References 1672 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 1673 Label Switching Architecture", RFC 3031, 1674 DOI 10.17487/RFC3031, January 2001, 1675 . 1677 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1678 "Introduction and Applicability Statements for Internet- 1679 Standard Management Framework", RFC 3410, 1680 DOI 10.17487/RFC3410, December 2002, 1681 . 1683 [RFC3811] Nadeau, T., Ed. and J. Cucchiara, Ed., "Definitions of 1684 Textual Conventions (TCs) for Multiprotocol Label 1685 Switching (MPLS) Management", RFC 3811, 1686 DOI 10.17487/RFC3811, June 2004, 1687 . 1689 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1690 "Multiprotocol Label Switching (MPLS) Label Switching 1691 Router (LSR) Management Information Base (MIB)", RFC 3813, 1692 DOI 10.17487/RFC3813, June 2004, 1693 . 1695 [RFC3815] Cucchiara, J., Sjostrand, H., and J. Luciani, "Definitions 1696 of Managed Objects for the Multiprotocol Label Switching 1697 (MPLS), Label Distribution Protocol (LDP)", RFC 3815, 1698 DOI 10.17487/RFC3815, June 2004, 1699 . 1701 [RFC5036] Andersson, L., Ed., Minei, I., Ed., and B. Thomas, Ed., 1702 "LDP Specification", RFC 5036, DOI 10.17487/RFC5036, 1703 October 2007, . 1705 [RFC5561] Thomas, B., Raza, K., Aggarwal, S., Aggarwal, R., and JL. 1706 Le Roux, "LDP Capabilities", RFC 5561, 1707 DOI 10.17487/RFC5561, July 2009, 1708 . 1710 [RFC6388] Wijnands, IJ., Ed., Minei, I., Ed., Kompella, K., and B. 1711 Thomas, "Label Distribution Protocol Extensions for Point- 1712 to-Multipoint and Multipoint-to-Multipoint Label Switched 1713 Paths", RFC 6388, DOI 10.17487/RFC6388, November 2011, 1714 . 1716 [RFC6389] Aggarwal, R. and JL. Le Roux, "MPLS Upstream Label 1717 Assignment for LDP", RFC 6389, DOI 10.17487/RFC6389, 1718 November 2011, . 1720 [RFC6826] Wijnands, IJ., Ed., Eckert, T., Leymann, N., and M. 1721 Napierala, "Multipoint LDP In-Band Signaling for Point-to- 1722 Multipoint and Multipoint-to-Multipoint Label Switched 1723 Paths", RFC 6826, DOI 10.17487/RFC6826, January 2013, 1724 . 1726 [RFC7060] Napierala, M., Rosen, E., and IJ. Wijnands, "Using LDP 1727 Multipoint Extensions on Targeted LDP Sessions", RFC 7060, 1728 DOI 10.17487/RFC7060, November 2013, 1729 . 1731 [RFC7431] Karan, A., Filsfils, C., Wijnands, IJ., Ed., and B. 1732 Decraene, "Multicast-Only Fast Reroute", RFC 7431, 1733 DOI 10.17487/RFC7431, August 2015, 1734 . 1736 [RFC7715] Wijnands, IJ., Ed., Raza, K., Atlas, A., Tantsura, J., and 1737 Q. Zhao, "Multipoint LDP (mLDP) Node Protection", 1738 RFC 7715, DOI 10.17487/RFC7715, January 2016, 1739 . 1741 15.2. Informative References 1743 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1744 Requirement Levels", BCP 14, RFC 2119, 1745 DOI 10.17487/RFC2119, March 1997, 1746 . 1748 [RFC2223] Postel, J. and J. Reynolds, "Instructions to RFC Authors", 1749 RFC 2223, DOI 10.17487/RFC2223, October 1997, 1750 . 1752 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1753 Schoenwaelder, Ed., "Structure of Management Information 1754 Version 2 (SMIv2)", STD 58, RFC 2578, 1755 DOI 10.17487/RFC2578, April 1999, 1756 . 1758 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1759 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 1760 STD 58, RFC 2579, DOI 10.17487/RFC2579, April 1999, 1761 . 1763 [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1764 Schoenwaelder, Ed., "Conformance Statements for SMIv2", 1765 STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999, 1766 . 1768 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 1769 DOI 10.17487/RFC2629, June 1999, 1770 . 1772 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 1773 Schoenwaelder, "Textual Conventions for Internet Network 1774 Addresses", RFC 4001, DOI 10.17487/RFC4001, February 2005, 1775 . 1777 [RFC4181] Heard, C., Ed., "Guidelines for Authors and Reviewers of 1778 MIB Documents", BCP 111, RFC 4181, DOI 10.17487/RFC4181, 1779 September 2005, . 1781 Authors' Addresses 1782 Kishore Tiruveedhula (editor) 1783 Juniper Networks 1784 10 Technology Park Drive 1785 Westford MA 01886 1786 USA 1788 Phone: +1 9785898861 1789 EMail: kishoret@juniper.net 1791 Uwe Joorde 1792 Deutsche Telekom 1793 Dahlweg 100 1794 Munster 48153 1795 Germany 1797 EMail: uwe@ujo.de 1799 Arvind Venkateswaran 1800 Cisco Systems 1801 510 McCarthy Blvd 1802 Milpitas CA 95035 1803 USA 1805 EMail: arvvenka@cisco.com