idnits 2.17.1 draft-ietf-mpls-mldp-mib-03.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 59 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 985 has weird spacing: '... of the mplsM...' == Line 1013 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 (October 1, 2017) is 2398 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 430, but not defined == Missing Reference: 'RFC3414' is mentioned on line 1534, but not defined == Missing Reference: 'RFC3826' is mentioned on line 1534, but not defined == Missing Reference: 'RFC5591' is mentioned on line 1536, but not defined == Missing Reference: 'RFC5592' is mentioned on line 1537, but not defined == Missing Reference: 'RFC6353' is mentioned on line 1537, but not defined == Unused Reference: 'RFC3031' is defined on line 1563, but no explicit reference was found in the text == Unused Reference: 'RFC3811' is defined on line 1574, but no explicit reference was found in the text == Unused Reference: 'RFC5561' is defined on line 1596, but no explicit reference was found in the text == Unused Reference: 'RFC6389' is defined on line 1607, but no explicit reference was found in the text == Unused Reference: 'RFC6826' is defined on line 1611, but no explicit reference was found in the text == Unused Reference: 'RFC7060' is defined on line 1617, but no explicit reference was found in the text == Unused Reference: 'RFC7431' is defined on line 1622, but no explicit reference was found in the text == Unused Reference: 'RFC7715' is defined on line 1627, but no explicit reference was found in the text == Unused Reference: 'RFC2223' is defined on line 1639, but no explicit reference was found in the text == Unused Reference: 'RFC2629' is defined on line 1659, but no explicit reference was found in the text == Unused Reference: 'RFC4001' is defined on line 1663, but no explicit reference was found in the text == Unused Reference: 'RFC4181' is defined on line 1668, 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: April 4, 2018 Deutsche Telekom 6 A. Venkateswaran 7 Cisco Systems 9 October 1, 2017 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-03 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 April 4, 2018. 41 Copyright Notice 43 Copyright (c) 2017 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 . . . . . . . . . . . . . . . . . . . 32 94 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 34 95 14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 34 96 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 34 97 15.1. Normative References . . . . . . . . . . . . . . . . . . 34 98 15.2. Informative References . . . . . . . . . . . . . . . . . 35 99 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 36 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 11. Multicast MPLS Label Distribution Protocol MIB Definitions 419 MPLS-MLDP-STD-MIB DEFINITIONS ::= BEGIN 420 IMPORTS 421 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 422 Unsigned32, Counter32, Counter64, TimeTicks 423 FROM SNMPv2-SMI -- RFC 2578 424 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 425 FROM SNMPv2-CONF -- RFC 2580 426 TruthValue, RowStatus, StorageType, TimeStamp 427 FROM SNMPv2-TC -- RFC 2579 429 InterfaceIndex 430 FROM IF-MIB -- [RFC2020] 432 mplsStdMIB, MplsLdpIdentifier 433 FROM MPLS-TC-STD-MIB -- RFC 3811 435 MplsIndexType 436 FROM MPLS-LSR-STD-MIB -- RFC 3813 438 IndexInteger, IndexIntegerNextFree 439 FROM DIFFSERV-MIB -- RFC 3289 441 InetAddress, InetAddressType 442 FROM INET-ADDRESS-MIB -- RFC 4001 444 mplsLdpStdMIB, mplsLdpEntityLdpId, mplsLdpEntityIndex, 445 mplsLdpPeerLdpId, mplsLdpSessionStatsEntry 446 FROM MPLS-LDP-STD-MIB -- RFC 3815 447 ; 449 mplsMldpStdMIB MODULE-IDENTITY 450 LAST-UPDATED "201710010000Z" -- Octiber 1, 2017 451 ORGANIZATION "Multiprotocol Label Switching (mpls) 452 Working Group" 453 CONTACT-INFO 455 " Kishore Tiruveedhula 456 Juniper Networks 457 Email: kishoret@juniper.net 459 Uwe Joorde 460 Deutsche Telekom 461 Email: Uwe.Joorde@telekom.de 463 Arvind Venkateswaran 464 Cisco Systems 465 EMail: arvvenka@cisco.com 467 Comments about this document should be emailed 468 directly to the MPLS working group mailing list at 469 mpls@lists.ietf.org" 471 DESCRIPTION 472 "Copyright (c) 2009 IETF Trust and the persons identified as 473 the document authors. All rights reserved. 475 This document is subject to BCP 78 and the IETF Trust's 476 Legal Provisions Relating to IETF Documents in effect on the 477 date of publication of this document 478 (http://trustee.ietf.org/license-info). Please review these 479 documents carefully, as they describe your rights and 480 restrictions with respect to this document. 482 The initial version of this MIB module was published in 483 RFC XXXX. For full legal notices see the RFC itself or see: 484 http://www.ietf.org/copyrights/ianamib.html 485 -- RFC Editor. Please replace XXXX with the RFC number for this 486 -- document and remove this note. 488 This MIB module contains managed object definitions for mLDP LSPS 489 defined in Label Distribution Protocol Extensions Point-to-Multipoint and 490 Multipoint-to-Multipoint Label Switched Paths, RFC 6388, November 491 2011." 493 REVISION "201710010000Z" -- October 1, 2017 494 DESCRIPTION 495 "Initial version issued as part of RFC XXXX." 496 -- RFC Editor. Please replace XXXX with the RFC number for this 497 -- document and remove this note. 499 ::= { mplsStdMIB YYY } 500 -- RFC Editor. Please replace YYY with the codepoint issued by IANA 501 -- and remove this note. 503 -- Top level components of this MIB module. 505 -- notifications 507 mplsMldpNotifications OBJECT IDENTIFIER ::= { mplsMldpStdMIB 0 } 508 -- tables, scalars 509 mplsMldpScalars OBJECT IDENTIFIER ::= { mplsMldpStdMIB 1 } 510 mplsMldpObjects OBJECT IDENTIFIER ::= { mplsMldpStdMIB 2 } 512 -- MPLS mLDP LSP scalars. 514 mplsMldpP2mpCapable OBJECT-TYPE 515 SYNTAX INTEGER { 516 enable(1), 517 disable(2) 518 } 519 MAX-ACCESS read-only 520 STATUS current 521 DESCRIPTION 522 "This object provides the P2MP capability of the LSR." 524 REFERENCE 525 "Section 2.1 of [RFC6388]." 527 ::= { mplsMldpScalars 1 } 529 mplsMldpMp2mpCapable OBJECT-TYPE 530 SYNTAX INTEGER { 531 enable(1), 532 disable(2) 533 } 534 MAX-ACCESS read-only 535 STATUS current 536 DESCRIPTION 537 "This object provides MP2MP capability of the LSR." 539 REFERENCE 540 "Section 3.1 of [RFC6388]." 542 ::= { mplsMldpScalars 2 } 544 mplsMldpMbbCapable OBJECT-TYPE 545 SYNTAX INTEGER { 546 enable(1), 547 disable(2) 548 } 549 MAX-ACCESS read-only 550 STATUS current 551 DESCRIPTION 552 "This object provides MBB (make before break) capability of the LSR." 554 REFERENCE 555 "Section 8.3 of [RFC6388]." 557 ::= { mplsMldpScalars 3 } 559 mplsMldpMbbTime OBJECT-TYPE 560 SYNTAX Unsigned32 (1..300) 561 UNITS "seconds" 562 MAX-ACCESS read-only 563 STATUS current 564 DESCRIPTION 565 "The 32-bit unsigned integer value provides the time for waiting MBB Ack 566 from upstream node." 568 DEFVAL { 30 } 569 ::= { mplsMldpScalars 4 } 571 mplsMldpNumFecs OBJECT-TYPE 572 SYNTAX Unsigned32 573 MAX-ACCESS read-only 574 STATUS current 575 DESCRIPTION 576 "The number of active and passive mLdp Fecs on this device." 578 ::= { mplsMldpScalars 5 } 580 mplsMldpNumFecsActive OBJECT-TYPE 581 SYNTAX Unsigned32 582 MAX-ACCESS read-only 583 STATUS current 584 DESCRIPTION 585 "The number of mLdp FECs Active on this device. The mLDP FEC is 586 considered active if the mplsMldpFecOperStatus is up(1)." 588 ::= { mplsMldpScalars 6 } 590 mplsMldpPlrCapable OBJECT-TYPE 591 SYNTAX INTEGER { 592 enable(1), 593 disable(2) 594 } 595 MAX-ACCESS read-only 596 STATUS current 597 DESCRIPTION 598 "This object provides Point of Local Repair (PLR) 599 capability of the LSR." 601 REFERENCE 602 "Section 5.1 of RFC7715]." 604 ::= { mplsMldpScalars 7 } 606 mplsMldpMptCapable OBJECT-TYPE 607 SYNTAX INTEGER { 608 enable(1), 609 disable(2) 610 } 611 MAX-ACCESS read-only 612 STATUS current 613 DESCRIPTION 614 "This object provides Merge Point (MPT) capability of the LSR." 616 REFERENCE 617 "Section 5.2 of RFC7715]." 619 ::= { mplsMldpScalars 8 } 621 mplsMldProtLsrCapable OBJECT-TYPE 622 SYNTAX INTEGER { 623 enable(1), 624 disable(2) 625 } 626 MAX-ACCESS read-only 627 STATUS current 628 DESCRIPTION 629 "This object provides Protected LSR capability." 631 REFERENCE 632 "Section 5.3 of RFC7715]." 634 ::= { mplsMldpScalars 9 } 636 mplsMldProtNodeProtCapable OBJECT-TYPE 637 SYNTAX INTEGER { 638 enable(1), 639 disable(2) 640 } 641 MAX-ACCESS read-only 642 STATUS current 643 DESCRIPTION 644 "This object provides Node Protection capability of the LSR." 646 REFERENCE 647 "Section 5.3 of RFC7715]." 649 ::= { mplsMldpScalars 10 } 651 -- End of MPLS mLDP scalars. 653 -- MPLS mLDP tables. 655 -- 656 -- The MPLS LDP Peer Capability Table 657 -- 659 mplsLdpPeerCapabilityTable OBJECT-TYPE 660 SYNTAX SEQUENCE OF MplsLdpPeerCapabilityEntry 661 MAX-ACCESS not-accessible 662 STATUS current 663 DESCRIPTION 664 "This table will have learned information relating to Mldp." 665 ::= { mplsMldpObjects 1 } 667 mplsLdpPeerCapabilityEntry OBJECT-TYPE 668 SYNTAX MplsLdpPeerCapabilityEntry 669 MAX-ACCESS not-accessible 670 STATUS current 671 DESCRIPTION 672 "Information about a single Peer which is related 673 to a Session. This table is augmented by 674 the mplsLdpSessionTable." 675 INDEX { mplsLdpEntityLdpId, 676 mplsLdpEntityIndex, 677 mplsLdpPeerLdpId 678 } 679 ::= { mplsLdpPeerCapabilityTable 1 } 681 MplsLdpPeerCapabilityEntry ::= SEQUENCE { 682 mplsLdpPeerLdpId MplsLdpIdentifier, 683 mplsLdpPeerCapability BITS 684 } 686 mplsLdpPeerLdpId OBJECT-TYPE 687 SYNTAX MplsLdpIdentifier 688 MAX-ACCESS read-only 689 STATUS current 690 DESCRIPTION 691 "The LDP identifier of this LDP Peer." 693 ::= { mplsLdpPeerCapabilityEntry 1 } 695 mplsLdpPeerCapability OBJECT-TYPE 696 SYNTAX BITS { 697 none (0), 698 p2mp (1), 699 mp2mp(2), 700 mbb (3), 701 upstreamLabelAssignment (4), 702 dynamic (5), 703 plr (6), 704 mpt (7), 705 protLsr (8), 706 nodeProt (9) 707 } 708 MAX-ACCESS read-only 709 STATUS current 710 DESCRIPTION 711 " This will indicate the LDP capability information about peer. 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. 729 Section 3 of RFC6389 for Upstream Label Assignment Capability TLV. 730 Section 5 of RFC7715 describes for Point of Local Repair (plr) 731 capability, Merge Point (mpt) capability, 732 The Protected LSR (port-lsr) and Node Protection (node-prot) Capability. " 734 ::= { mplsLdpPeerCapabilityEntry 2 } 736 -- 737 -- The MPLS mLDP Session Statistics Table 738 -- 740 mplsMldpSessionStatsTable OBJECT-TYPE 741 SYNTAX SEQUENCE OF MplsMldpSessionStatsEntry 742 MAX-ACCESS not-accessible 743 STATUS current 744 DESCRIPTION 745 "A table of statistics related to mLDP on Sessions. 746 This table AUGMENTS the mplsLdpSessionStatsTable." 747 ::= { mplsMldpObjects 2 } 749 mplsMldpSessionStatsEntry OBJECT-TYPE 750 SYNTAX MplsMldpSessionStatsEntry 751 MAX-ACCESS not-accessible 752 STATUS current 753 DESCRIPTION 754 "An entry in this table represents mLDP statistical 755 information on a single session between an LDP 756 Entity and LDP Peer." 758 INDEX { mplsLdpEntityLdpId, 759 mplsLdpEntityIndex, 760 mplsLdpPeerLdpId 761 } 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 791 STATUS current 792 DESCRIPTION 793 "This object counts the number of mLDP FECs sent on this 794 session and waiting for MBB Ack. This counter will get incremented 795 when MBB req sent for a label on this session and will get 796 decremented when the MBB Ack received." 798 ::= { mplsMldpSessionStatsEntry 2 } 800 mplsMldpSessionStatsNumFecsRcvd OBJECT-TYPE 801 SYNTAX Counter32 802 MAX-ACCESS read-only 803 STATUS current 804 DESCRIPTION 805 "This object counts the number of mLDP FECs received on this 806 session. If the FEC is withdrawn from the downstream session, 807 then this is decremented. 809 Discontinuities in the value of this counter can occur 810 at re-initialization of the management system, and at 811 other times as indicated by the value of 812 mplsLdpSessionDiscontinuityTime." 814 ::= { mplsMldpSessionStatsEntry 3 } 816 mplsMldpSessionStatsNumMbbReqRcvdState OBJECT-TYPE 817 SYNTAX Counter32 818 MAX-ACCESS read-only 819 STATUS current 820 DESCRIPTION 821 "This object counts the number of mLDP FECs received on this 822 session and waiting for sending MBB Ack. This counter will get 823 incremented when MBB req is received for a label on this session 824 and will get decremented when the MBB Ack sent." 826 ::= { mplsMldpSessionStatsEntry 4 } 828 mplsMldpSessionStatsNumMbbResetAckByTimer OBJECT-TYPE 829 SYNTAX Counter32 830 MAX-ACCESS read-only 831 STATUS current 832 DESCRIPTION 833 "This object counts the number mLDP FECs for which the MBB Ack is 834 reset by MBB timer, in which the LSR is waiting for MBB ack." 836 ::= { mplsMldpSessionStatsEntry 5 } 838 -- 839 -- Mpls mLDP FEC Table 840 -- 842 mplsMldpFecTable OBJECT-TYPE 843 SYNTAX SEQUENCE OF MplsMldpFecEntry 844 MAX-ACCESS not-accessible 845 STATUS current 846 DESCRIPTION 847 "This table represents the FEC 848 (Forwarding Equivalence Class) 849 Information associated with an mLDP LSP." 851 ::= { mplsMldpObjects 3 } 853 mplsMldpFecEntry OBJECT-TYPE 854 SYNTAX MplsMldpFecEntry 855 MAX-ACCESS not-accessible 856 STATUS current 857 DESCRIPTION 858 "Each row represents a single mLDP FEC Element." 859 INDEX { mplsLdpEntityLdpId, 860 mplsLdpEntityIndex, 861 mplsMldpFecIndex 862 } 864 ::= { mplsMldpFecTable 1 } 866 MplsMldpFecEntry ::= SEQUENCE { 867 mplsMldpFecIndex IndexInteger, 868 mplsMldpFecType INTEGER, 869 mplsMldpFecRootAddrType InetAddressType, 870 mplsMldpFecRootAddr InetAddress, 871 mplsMldpFecOpaqueType INTEGER, 872 mplsMldpFecOpaqueGenLspId Unsigned32, 873 mplsMldpFecOpaqueTransitSourceOrBidirAddrType InetAddressType, 874 mplsMldpFecOpaqueTransitSourceOrBidirAddr InetAddress, 875 mplsMldpFecOpaqueTransitGroupAddrType InetAddressType, 876 mplsMldpFecOpaqueTransitGroupAddr InetAddress, 877 mplsMldpFecAdminStatus INTEGER, 878 mplsMldpFecOperStatus INTEGER, 879 mplsMldpFecMoFrr INTEGER, 880 mplsMldpFecLsrState INTEGER, 881 mplsMldpFecUpTime TimeStamp 882 } 884 mplsMldpFecIndex OBJECT-TYPE 885 SYNTAX IndexInteger 886 MAX-ACCESS not-accessible 887 STATUS current 888 DESCRIPTION 889 "The index which uniquely identifies this entry." 891 ::= { mplsMldpFecEntry 1 } 893 mplsMldpFecType OBJECT-TYPE 894 SYNTAX INTEGER { 895 p2mp(6), 896 mp2mpUpstream(7), 897 mp2mpDownstream(8) 898 } 899 MAX-ACCESS read-only 900 STATUS current 901 DESCRIPTION 902 "The type of the FEC. If the value of this object 903 is 6, then it is P2MP Fec Type, and 7, 8 are correspond to 904 MP2MP upstream and downstream type." 906 REFERENCE 907 "RFC6388, Section 2.2. The P2MP FEC Element and the section 3.3 908 for the MP2MP Fec elements." 910 ::= { mplsMldpFecEntry 2 } 912 mplsMldpFecRootAddrType OBJECT-TYPE 913 SYNTAX InetAddressType 914 MAX-ACCESS read-only 915 STATUS current 916 DESCRIPTION 917 "The value of this object is the type of the 918 Internet address. The value of this object, 919 decides how the value of the mplsMldpFecRootAddr object 920 is interpreted." 921 REFERENCE 922 "RFC6388, Section 2.2. The P2MP FEC Element and the section 3.3 923 for the MP2MP Fec elements." 925 ::= { mplsMldpFecEntry 3 } 927 mplsMldpFecRootAddr OBJECT-TYPE 928 SYNTAX InetAddress 929 MAX-ACCESS read-only 930 STATUS current 931 DESCRIPTION 932 "The value of this object is interpreted based 933 on the value of the mplsMldpFecRootAddrType object. 934 This is ingress node address for the mLDP LSP." 936 REFERENCE 937 "RFC6388, Section 2.2. The P2MP FEC Element and the section 3.3 938 for the MP2MP Fec elements." 940 ::= { mplsMldpFecEntry 4 } 942 mplsMldpFecOpaqueType OBJECT-TYPE 943 SYNTAX INTEGER { 944 genericLspId(1), 945 transitIpv4Source(3), 946 transitIpv6Source(4), 947 transitIpv4Bidir(5), 948 transitIpv6Bidir(6) 949 } 950 MAX-ACCESS read-only 951 STATUS current 952 DESCRIPTION 953 "This is opaque type of the mLDP FEC. The value of this object is 954 shown below. 956 1 - The Generic LSP Identifier 957 3 - Transit IPv4 Source TLV 958 4 - Transit IPv6 Source TLV 959 5 - Transit IPv4 Bidir TLV 960 6 - Transit IPv6 Bidir TLV. 961 " 962 ::= { mplsMldpFecEntry 5 } 964 mplsMldpFecOpaqueGenLspId OBJECT-TYPE 965 SYNTAX Unsigned32 966 MAX-ACCESS read-only 967 STATUS current 968 DESCRIPTION 969 "The 32-bit unsigned integer value which is to represent Generic 970 LSP ID. This value is only valid if the mplsMldpFecOpaqueType is 971 genericLspId(1), otherwise 0 must be returned." 973 REFERENCE 974 "RFC6388, Section 2.3.1." 976 ::= { mplsMldpFecEntry 6 } 978 mplsMldpFecOpaqueTransitSourceOrBidirAddrType OBJECT-TYPE 979 SYNTAX InetAddressType 980 MAX-ACCESS read-only 981 STATUS current 982 DESCRIPTION 983 "The value of this object is the type of the 984 Internet address. The value of this object, 985 decides how the value of the mplsMldpFecOpaqueTransitSourceOrBidirAddr 986 object is interpreted." 987 REFERENCE 988 "RFC6826, Section 3.1." 990 ::= { mplsMldpFecEntry 7 } 992 mplsMldpFecOpaqueTransitSourceOrBidirAddr OBJECT-TYPE 993 SYNTAX InetAddress 994 MAX-ACCESS read-only 995 STATUS current 996 DESCRIPTION 997 "The value of this object is interpreted based 998 on the value of the mplsMldpFecOpaqueTransitSourceOrBidirAddrType 999 object. This is source node address for the mLDP inband LSP." 1001 REFERENCE 1002 "RFC6826, Section 3.1." 1004 ::= { mplsMldpFecEntry 8 } 1006 mplsMldpFecOpaqueTransitGroupAddrType OBJECT-TYPE 1007 SYNTAX InetAddressType 1008 MAX-ACCESS read-only 1009 STATUS current 1010 DESCRIPTION 1011 "The value of this object is the type of the 1012 Internet address. The value of this object, 1013 decides how the value of the mplsMldpFecOpaqueTransitGroupAddr 1014 object is interpreted." 1016 REFERENCE 1017 "RFC6826, Section 3.2." 1019 ::= { mplsMldpFecEntry 9 } 1021 mplsMldpFecOpaqueTransitGroupAddr OBJECT-TYPE 1022 SYNTAX InetAddress 1023 MAX-ACCESS read-only 1024 STATUS current 1025 DESCRIPTION 1026 "The value of this object is interpreted based 1027 on the value of the mplsMldpFecOpaqueTransitGroupAddrType 1028 object. This is group node address for the mLDP inband LSP." 1030 REFERENCE 1031 "RFC6826, Section 3.2." 1033 ::= { mplsMldpFecEntry 10 } 1035 mplsMldpFecAdminStatus OBJECT-TYPE 1036 SYNTAX INTEGER { 1037 up(1), -- ready to pass data 1038 down(2) -- out of service 1039 } 1040 MAX-ACCESS read-only 1041 STATUS current 1042 DESCRIPTION 1043 "Indicates the admin status of this mLDP FEC." 1045 DEFVAL { up } 1047 ::= { mplsMldpFecEntry 11 } 1049 mplsMldpFecOperStatus OBJECT-TYPE 1050 SYNTAX INTEGER { 1051 up(1), -- ready to pass data 1052 down(2) -- out of service 1053 } 1054 MAX-ACCESS read-only 1055 STATUS current 1056 DESCRIPTION 1057 "Indicates the actual operational status of this mLDP Fec." 1059 ::= { mplsMldpFecEntry 12 } 1061 mplsMldpFecMoFrr OBJECT-TYPE 1062 SYNTAX INTEGER { 1063 enable(1), 1064 disable(2) 1065 } 1066 MAX-ACCESS read-only 1067 STATUS current 1068 DESCRIPTION 1069 "This object provides whether MoFRR enabled for this mLDP FEC. 1070 on this mLDP FEC. As mentioned in the section 3.2 of [ RFC7431 ], 1071 When this is enabled, then mLDP may select two upstream sessions, 1072 one is primary and other one is backup. The backup traffic is 1073 discarded when the primary upstream session is UP. When the 1074 primary upstream session goes down, the traffic from the backup 1075 upstream session will be forwarded to downstream. 1076 " 1078 ::= { mplsMldpFecEntry 13 } 1080 mplsMldpFecLsrState OBJECT-TYPE 1081 SYNTAX INTEGER { 1082 egress(1), 1083 bud(2), 1084 transit(3), 1085 ingress(4) 1086 } 1087 MAX-ACCESS read-only 1088 STATUS current 1089 DESCRIPTION 1090 "Indicates the role of FEC either egress, bud, transit or ingress" 1092 ::= { mplsMldpFecEntry 14 } 1094 mplsMldpFecUpTime OBJECT-TYPE 1095 SYNTAX TimeStamp 1096 MAX-ACCESS read-only 1097 STATUS current 1098 DESCRIPTION 1099 "This values shows Fec UP time. This is time since mplsMldpFecOperStatus is UP." 1101 ::= { mplsMldpFecEntry 15 } 1103 -- MPLS mLDP LSP Branch Traffic Stats Table. 1105 mplsMldpFecBranchStatsTable OBJECT-TYPE 1106 SYNTAX SEQUENCE OF MplsMldpFecBranchStatsEntry 1107 MAX-ACCESS not-accessible 1108 STATUS current 1109 DESCRIPTION 1110 "This table provides mLDP Fec branch MPLS Traffic Stats 1111 information." 1113 ::= { mplsMldpObjects 4 } 1115 mplsMldpFecBranchStatsEntry OBJECT-TYPE 1116 SYNTAX MplsMldpFecBranchStatsEntry 1117 MAX-ACCESS not-accessible 1118 STATUS current 1119 DESCRIPTION 1120 "An entry in this table is created by the LSR for each 1121 downstream branch (out-segment) from this LSR for this mLDP 1122 LSP. Each downstream session may represent a single out-segment. 1124 Each entry in the table is indexed by the four identifiers 1125 of the mLDP LSP, and the out-segment that identifies the 1126 outgoing branch." 1128 INDEX { mplsLdpEntityLdpId, 1129 mplsLdpEntityIndex, 1130 mplsMldpFecBranchFecIndex, 1131 mplsMldpFecBranchOutSegIndex 1132 } 1134 ::= { mplsMldpFecBranchStatsTable 1 } 1136 MplsMldpFecBranchStatsEntry ::= SEQUENCE { 1137 mplsMldpFecBranchFecIndex MplsIndexType, 1138 mplsMldpFecBranchOutSegIndex MplsIndexType, 1139 mplsMLdpFecBranchPeerLdpId MplsLdpIdentifier, 1140 mplsMldpFecBranchStatsPackets Counter64, 1141 mplsMldpFecBranchStatsBytes Counter64, 1142 mplsMldpFecBranchStatsDiscontinuityTime TimeStamp 1143 } 1145 mplsMldpFecBranchFecIndex OBJECT-TYPE 1146 SYNTAX MplsIndexType 1147 MAX-ACCESS not-accessible 1148 STATUS current 1149 DESCRIPTION 1150 "This index identifies the mLDP FEC entry in the 1151 mplsMldpFecTable. This is same as mplsMldpFecIndex." 1153 ::= { mplsMldpFecBranchStatsEntry 1 } 1155 mplsMldpFecBranchOutSegIndex OBJECT-TYPE 1156 SYNTAX MplsIndexType 1157 MAX-ACCESS not-accessible 1158 STATUS current 1159 DESCRIPTION 1160 "This object identifies an outgoing branch from this mLDP LSP 1161 Its value is unique within the context of the mLDP LSP. 1163 This contains the same value as the mplsOutSegmentIndex in the 1164 MPLS-LSR-STD-MIBs mplsOutSegmentTable." 1166 ::= { mplsMldpFecBranchStatsEntry 2 } 1168 mplsMLdpFecBranchPeerLdpId OBJECT-TYPE 1169 SYNTAX MplsLdpIdentifier 1170 MAX-ACCESS read-only 1171 STATUS current 1172 DESCRIPTION 1173 "This object identifies an outgoing branch peer LDP ID for this 1174 mLDP LSP. Its value is unique within the context of the mLDP LSP. 1175 On Egress node, this value could be 0.0.0.0:00 as there will no 1176 downstream LDP session." 1178 ::= { mplsMldpFecBranchStatsEntry 3 } 1180 mplsMldpFecBranchStatsPackets OBJECT-TYPE 1181 SYNTAX Counter64 1182 MAX-ACCESS read-only 1183 STATUS current 1184 DESCRIPTION 1185 "This object represent the 64-bit value, which gives the number 1186 of packets forwarded by the mLDP LSP onto this branch. 1187 This object should be read in conjunction with 1188 mplsMldpFecBranchStatsDiscontinuityTime." 1190 ::= { mplsMldpFecBranchStatsEntry 4 } 1192 mplsMldpFecBranchStatsBytes OBJECT-TYPE 1193 SYNTAX Counter64 1194 MAX-ACCESS read-only 1195 STATUS current 1196 DESCRIPTION 1197 "This object represent the 64-bit value, which gives the number 1198 of bytes forwarded by the mLDP LSP onto this branch. 1199 This object should be read in conjunction with 1200 mplsMldpFecBranchStatsDiscontinuityTime." 1202 ::= { mplsMldpFecBranchStatsEntry 5 } 1204 mplsMldpFecBranchStatsDiscontinuityTime OBJECT-TYPE 1205 SYNTAX TimeStamp 1206 MAX-ACCESS read-only 1207 STATUS current 1208 DESCRIPTION 1209 "The value of sysUpTime on the most recent occasion at which 1210 any one or more of this rows Counter32 or Counter64 objects 1211 experienced a discontinuity. If no such discontinuity has 1212 occurred since the last re-initialization of the local 1213 management subsystem, then this object contains a zero 1214 value." 1215 ::= { mplsMldpFecBranchStatsEntry 6 } 1217 -- End of mplsMldpFecBranchStatsTable 1219 -- MPLS mLDP LSP Upstream Session Table. 1221 mplsMldpFecUpstreamSessTable OBJECT-TYPE 1222 SYNTAX SEQUENCE OF MplsMldpFecUpstreamSessEntry 1223 MAX-ACCESS not-accessible 1224 STATUS current 1225 DESCRIPTION 1226 "This table provides mLDP Fec upstream Session information." 1228 ::= { mplsMldpObjects 5 } 1230 mplsMldpFecUpstreamSessEntry OBJECT-TYPE 1231 SYNTAX MplsMldpFecUpstreamSessEntry 1232 MAX-ACCESS not-accessible 1233 STATUS current 1234 DESCRIPTION 1235 "An entry in this table is created by the LSR for each 1236 upstream session (in-segment) from this LSR for this mLDP 1237 LSP. Each upstream session may represent a single in-segment. 1239 Each entry in the table is indexed by the four identifiers 1240 of the mLDP LSP, and the in-segment that identifies the 1241 incoming traffic." 1242 INDEX { mplsLdpEntityLdpId, 1243 mplsLdpEntityIndex, 1244 mplsLdpPeerLdpId, 1245 mplsMldpFecUpstreamSessFecIndex, 1246 mplsMldpFecUpstreamSessInSegIndex 1247 } 1249 ::= { mplsMldpFecUpstreamSessTable 1 } 1251 MplsMLdpFecUpstreamSessEntry ::= SEQUENCE { 1252 mplsMldpFecUpstreamSessFecIndex MplsIndexType, 1253 mplsMldpFecUpstreamSessInSegIndex MplsIndexType, 1254 mplsMldpFecUpstreamSessPrimary INTEGER, 1255 mplsMldpFecUpstreamSessActive INTEGER, 1256 mplsMldpFecUpstreamSessPackets Counter64, 1257 mplsMldpFecUpstreamSessBytes Counter64, 1258 mplsMldpFecUpstreamSessDiscontinuityTime TimeStamp 1259 } 1261 mplsMldpFecUpstreamSessFecIndex OBJECT-TYPE 1262 SYNTAX MplsIndexType 1263 MAX-ACCESS not-accessible 1264 STATUS current 1265 DESCRIPTION 1266 "This index identifies the mLDP FEC entry in the 1267 mplsMldpFecTable." 1269 ::= { mplsMldpFecUpstreamSessEntry 1 } 1271 mplsMldpFecUpstreamSessInSegIndex OBJECT-TYPE 1272 SYNTAX MplsIndexType 1273 MAX-ACCESS not-accessible 1274 STATUS current 1275 DESCRIPTION 1276 "This object identifies an upstream session from this mLDP LSP 1277 Its value is unique within the context of the mLDP LSP. 1279 This contains the same value as the mplsInSegmentIndex in the 1280 MPLS-LSR-STD-MIBs mplsInSegmentTable." 1282 ::= { mplsMldpFecUpstreamSessEntry 2 } 1284 mplsMldpFecUpstreamSessPrimary OBJECT-TYPE 1285 SYNTAX INTEGER { 1286 primary(1), 1287 backup(2) 1288 } 1289 MAX-ACCESS read-only 1290 STATUS current 1291 DESCRIPTION 1292 "This indicated wether the received traffic from upstream is 1293 primary or backup. This is valid only if the MoFRR 1294 (mplsMldpFecMoFrr) is enabled on this FEC." 1296 ::= { mplsMldpFecUpstreamSessEntry 3 } 1298 mplsMldpFecUpstreamSessActive OBJECT-TYPE 1299 SYNTAX INTEGER { 1300 active(1), 1301 inactive(2) 1302 } 1303 MAX-ACCESS read-only 1304 STATUS current 1305 DESCRIPTION 1306 "This indicates whether the upstream session is active, means the 1307 LSR programmed the forwarding engine to receive the traffic from 1308 this upstream session. This will be Inactive if the LSR is wating 1309 for MBB Ack." 1310 ::= { mplsMldpFecUpstreamSessEntry 4 } 1312 mplsMldpFecUpstreamSessPackets OBJECT-TYPE 1313 SYNTAX Counter64 1314 MAX-ACCESS read-only 1315 STATUS current 1316 DESCRIPTION 1317 "This object represent the 64-bit value, which gives the number 1318 of packets received by the mLDP LSP from this upstream 1319 session. This object should be read in conjunction with 1320 mplsMldpFecUpstreamSessDiscontinuityTime." 1322 ::= { mplsMldpFecUpstreamSessEntry 5 } 1324 mplsMldpFecUpstreamSessBytes OBJECT-TYPE 1325 SYNTAX Counter64 1326 MAX-ACCESS read-only 1327 STATUS current 1328 DESCRIPTION 1329 "This object represent the 64-bit value, which gives the number 1330 of bytes received by the mLDP LSP from this upstream 1331 session. This object should be read in conjunction with 1332 mplsMldpFecUpstreamSessDiscontinuityTime." 1334 ::= { mplsMldpFecUpstreamSessEntry 6 } 1336 mplsMldpFecUpstreamSessDiscontinuityTime OBJECT-TYPE 1337 SYNTAX TimeStamp 1338 MAX-ACCESS read-only 1339 STATUS current 1340 DESCRIPTION 1341 "The value of sysUpTime on the most recent occasion at which 1342 any one or more of this rows Counter32 or Counter64 objects 1343 experienced a discontinuity. If no such discontinuity has 1344 occurred since the last re-initialization of the local 1345 management subsystem, then this object contains a zero 1346 value." 1347 ::= { mplsMldpFecUpstreamSessEntry 7 } 1349 -- End of mplsMldpFecBranchStatsTable 1351 -- MPLS mLDP Interface Traffic Stats Table. 1353 mplsMldpInterfaceStatsTable OBJECT-TYPE 1354 SYNTAX SEQUENCE OF MplsMldpInterfaceStatsEntry 1355 MAX-ACCESS not-accessible 1356 STATUS current 1357 DESCRIPTION 1358 "This table provides mLDP Traffic Stats on specified interface." 1360 ::= { mplsMldpObjects 6 } 1362 mplsMldpInterfaceStatsEntry OBJECT-TYPE 1363 SYNTAX MplsMldpInterfaceStatsEntry 1364 MAX-ACCESS not-accessible 1365 STATUS current 1366 DESCRIPTION 1367 "An entry in this table is created by the LSR for each 1368 downstream branch (out-segment) from this LSR for this mLDP 1369 LSP. Each downstream session may represent a single out-segment. 1371 Each entry in the table is indexed by the four identifiers 1372 of the mLDP LSP, and the out-segment that identifies the 1373 outgoing branch." 1375 INDEX { mplsMldpInterfaceIndex 1376 } 1378 ::= { mplsMldpInterfaceStatsTable 1 } 1380 MplsMldpInterfaceStatsEntry ::= SEQUENCE { 1381 mplsMldpInterfaceIndex InterfaceIndex, 1382 mplsMldpInterfaceStatsSentPackets Counter64, 1383 mplsMldpInterfaceStatsSentBytes Counter64, 1384 mplsMldpInterfaceStatsRecvPackets Counter64, 1385 mplsMldpInterfaceStatsRecvBytes Counter64 1386 } 1388 mplsMldpInterfaceIndex OBJECT-TYPE 1389 SYNTAX InterfaceIndex 1390 MAX-ACCESS not-accessible 1391 STATUS current 1392 DESCRIPTION 1393 "This index identifies the specific interface. " 1395 ::= { mplsMldpInterfaceStatsEntry 1 } 1397 mplsMldpInterfaceStatsSentPackets OBJECT-TYPE 1398 SYNTAX Counter64 1399 MAX-ACCESS read-only 1400 STATUS current 1401 DESCRIPTION 1402 "This is 64 bit value, which gives the number of packets 1403 forwarded by all mLDP LSPs onto this interface." 1405 ::= { mplsMldpInterfaceStatsEntry 2 } 1407 mplsMldpInterfaceStatsSentBytes OBJECT-TYPE 1408 SYNTAX Counter64 1409 MAX-ACCESS read-only 1410 STATUS current 1411 DESCRIPTION 1412 "This is 64 bit value, which gives the number of bytes 1413 forwarded by all mLDP LSPs onto this interface." 1415 ::= { mplsMldpInterfaceStatsEntry 3 } 1417 mplsMldpInterfaceStatsRecvPackets OBJECT-TYPE 1418 SYNTAX Counter64 1419 MAX-ACCESS read-only 1420 STATUS current 1421 DESCRIPTION 1422 "This is 64 bit value, which gives the number of packets 1423 received by all mLDP LSPs from this interface." 1425 ::= { mplsMldpInterfaceStatsEntry 4 } 1427 mplsMldpInterfaceStatsRecvBytes OBJECT-TYPE 1428 SYNTAX Counter64 1429 MAX-ACCESS read-only 1430 STATUS current 1431 DESCRIPTION 1432 "This is 64 bit value, which gives the number of bytes 1433 received by all mLDP LSPs from this interface." 1435 ::= { mplsMldpInterfaceStatsEntry 5 } 1437 -- End of mplsMldpInterfaceStatsTable 1439 -- Notifications. 1441 mplsMldpFecUp NOTIFICATION-TYPE 1442 OBJECTS { 1443 mplsMldpFecAdminStatus, 1444 mplsMldpFecOperStatus 1445 } 1446 STATUS current 1447 DESCRIPTION 1448 "This notification is generated when a mplsMldpFecOperStatus 1449 object changes from down to up." 1451 ::= { mplsMldpNotifications 1 } 1453 mplsMldpFecDown NOTIFICATION-TYPE 1454 OBJECTS { 1455 mplsMldpFecAdminStatus, 1456 mplsMldpFecOperStatus 1457 } 1458 STATUS current 1459 DESCRIPTION 1460 "This notification is generated when a mplsMldpFecOperStatus 1461 object changes from up to down." 1463 ::= { mplsMldpNotifications 2 } 1465 mplsMldpMoFrrStatusChange NOTIFICATION-TYPE 1466 OBJECTS { 1467 mplsMldpFecUpstreamSessPrimary 1468 } 1469 STATUS current 1470 DESCRIPTION 1471 "This notification is generated when a mplsMldpFecUpstreamSessPrimary 1472 object changes from primary to backup and vice versa." 1474 ::= { mplsMldpNotifications 3 } 1476 -- End of notifications. 1478 END 1480 12. Security Considerations 1482 This MIB module is useful for the configuration of certain objects 1483 and monitoring of mLDP LSPs. 1485 There are no management objects defined in this MIB module that have 1486 a MAX-ACCESS clause of read-write and/or read-create. So, if this 1487 MIB module is implemented correctly, then there is no risk that an 1488 intruder can alter or create any management objects of this MIB 1489 module via direct SNMP SET operations. 1491 Some of the readable objects in this MIB module (i.e., objects with a 1492 MAX-ACCESS other than not-accessible) may be considered sensitive or 1493 vulnerable in some network environments. It is thus important to 1494 control even GET and/or NOTIFY access to these objects and possibly 1495 to even encrypt the values of these objects when sending them over 1496 the network via SNMP. These are the tables and objects and their 1497 sensitivity/vulnerability: 1499 o mplsMldpFecTable 1501 o mplsLdpPeerCapabilityTable 1503 o mplsMldpSessionStatsTable 1505 o mplsMldpFecBranchStatsTable 1507 o mplsMldpFecUpstreamSessTable 1509 o mplsMldpInterfaceStatsTable 1511 o mplsMldpNumFecs 1513 o mplsMldpNumFecsActive 1515 o mplsMldpMbbTime 1517 Above listed tables and objects show information about the mLDP LSPs, 1518 its route through the network, and its traffic statistics. Knowledge 1519 of this information could be used to compromise the network, or 1520 simply to breach confidentiality. If an Administrator does not want 1521 to reveal this information, these tables and objects should be 1522 considered sensitive/vulnerable. 1524 SNMP versions prior to SNMPv3 did not include adequate security. 1525 Even if the network itself is secure (for example by using IPsec), 1526 there is no control as to who on the secure network is allowed to 1527 access and GET/SET (read/change/create/delete) the objects in this 1528 MIB module. 1530 Implementations SHOULD provide the security features described by the 1531 SNMPv3 framework (see [RFC3410]), and implementations claiming 1532 compliance to the SNMPv3 standard MUST include full support for 1533 authentication and privacy via the User-based Security Model (USM) 1534 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 1535 MAY also provide support for the Transport Security Model (TSM) 1536 [RFC5591] in combination with a secure transport such as SSH 1537 [RFC5592] or TLS/DTLS [RFC6353]. 1539 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1540 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1541 enable cryptographic security. It is then a customer/operator 1542 responsibility to ensure that the SNMP entity giving access to an 1543 instance of this MIB module is properly configured to give access to 1544 the objects only to those principals (users) that have legitimate 1545 rights to indeed GET or SET (change/create/delete) them. 1547 13. IANA Considerations 1549 This is new MPLS MIB module, contained in this document and IANA is 1550 requested to assign an oid (mplsStdMIB YYY) under the mplsStdMIB 1551 subtree to the MPLS-MLDP-STD-MIB module specified in this document. 1553 14. Acknowledgments 1555 The authors wish to thank Santosh Esale, Alia Atlas and Martin Ehlers 1556 for doing the detailed review. Thanks to Adrian Farrel and Raveendra 1557 Torvi for their input to this work and for many helpful suggestions. 1559 15. References 1561 15.1. Normative References 1563 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 1564 Label Switching Architecture", RFC 3031, 1565 DOI 10.17487/RFC3031, January 2001, 1566 . 1568 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1569 "Introduction and Applicability Statements for Internet- 1570 Standard Management Framework", RFC 3410, 1571 DOI 10.17487/RFC3410, December 2002, 1572 . 1574 [RFC3811] Nadeau, T., Ed. and J. Cucchiara, Ed., "Definitions of 1575 Textual Conventions (TCs) for Multiprotocol Label 1576 Switching (MPLS) Management", RFC 3811, 1577 DOI 10.17487/RFC3811, June 2004, 1578 . 1580 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1581 "Multiprotocol Label Switching (MPLS) Label Switching 1582 Router (LSR) Management Information Base (MIB)", RFC 3813, 1583 DOI 10.17487/RFC3813, June 2004, 1584 . 1586 [RFC3815] Cucchiara, J., Sjostrand, H., and J. Luciani, "Definitions 1587 of Managed Objects for the Multiprotocol Label Switching 1588 (MPLS), Label Distribution Protocol (LDP)", RFC 3815, 1589 DOI 10.17487/RFC3815, June 2004, 1590 . 1592 [RFC5036] Andersson, L., Ed., Minei, I., Ed., and B. Thomas, Ed., 1593 "LDP Specification", RFC 5036, DOI 10.17487/RFC5036, 1594 October 2007, . 1596 [RFC5561] Thomas, B., Raza, K., Aggarwal, S., Aggarwal, R., and JL. 1597 Le Roux, "LDP Capabilities", RFC 5561, 1598 DOI 10.17487/RFC5561, July 2009, 1599 . 1601 [RFC6388] Wijnands, IJ., Ed., Minei, I., Ed., Kompella, K., and B. 1602 Thomas, "Label Distribution Protocol Extensions for Point- 1603 to-Multipoint and Multipoint-to-Multipoint Label Switched 1604 Paths", RFC 6388, DOI 10.17487/RFC6388, November 2011, 1605 . 1607 [RFC6389] Aggarwal, R. and JL. Le Roux, "MPLS Upstream Label 1608 Assignment for LDP", RFC 6389, DOI 10.17487/RFC6389, 1609 November 2011, . 1611 [RFC6826] Wijnands, IJ., Ed., Eckert, T., Leymann, N., and M. 1612 Napierala, "Multipoint LDP In-Band Signaling for Point-to- 1613 Multipoint and Multipoint-to-Multipoint Label Switched 1614 Paths", RFC 6826, DOI 10.17487/RFC6826, January 2013, 1615 . 1617 [RFC7060] Napierala, M., Rosen, E., and IJ. Wijnands, "Using LDP 1618 Multipoint Extensions on Targeted LDP Sessions", RFC 7060, 1619 DOI 10.17487/RFC7060, November 2013, 1620 . 1622 [RFC7431] Karan, A., Filsfils, C., Wijnands, IJ., Ed., and B. 1623 Decraene, "Multicast-Only Fast Reroute", RFC 7431, 1624 DOI 10.17487/RFC7431, August 2015, 1625 . 1627 [RFC7715] Wijnands, IJ., Ed., Raza, K., Atlas, A., Tantsura, J., and 1628 Q. Zhao, "Multipoint LDP (mLDP) Node Protection", 1629 RFC 7715, DOI 10.17487/RFC7715, January 2016, 1630 . 1632 15.2. Informative References 1634 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1635 Requirement Levels", BCP 14, RFC 2119, 1636 DOI 10.17487/RFC2119, March 1997, 1637 . 1639 [RFC2223] Postel, J. and J. Reynolds, "Instructions to RFC Authors", 1640 RFC 2223, DOI 10.17487/RFC2223, October 1997, 1641 . 1643 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1644 Schoenwaelder, Ed., "Structure of Management Information 1645 Version 2 (SMIv2)", STD 58, RFC 2578, 1646 DOI 10.17487/RFC2578, April 1999, 1647 . 1649 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1650 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 1651 STD 58, RFC 2579, DOI 10.17487/RFC2579, April 1999, 1652 . 1654 [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1655 Schoenwaelder, Ed., "Conformance Statements for SMIv2", 1656 STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999, 1657 . 1659 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 1660 DOI 10.17487/RFC2629, June 1999, 1661 . 1663 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 1664 Schoenwaelder, "Textual Conventions for Internet Network 1665 Addresses", RFC 4001, DOI 10.17487/RFC4001, February 2005, 1666 . 1668 [RFC4181] Heard, C., Ed., "Guidelines for Authors and Reviewers of 1669 MIB Documents", BCP 111, RFC 4181, DOI 10.17487/RFC4181, 1670 September 2005, . 1672 Authors' Addresses 1674 Kishore Tiruveedhula (editor) 1675 Juniper Networks 1676 10 Technology Park Drive 1677 Westford MA 01886 1678 USA 1680 Phone: +1 9785898861 1681 EMail: kishoret@juniper.net 1683 Uwe Joorde 1684 Deutsche Telekom 1685 Dahlweg 100 1686 Munster 48153 1687 Germany 1689 EMail: Uwe.Joorde@telekom.de 1690 Arvind Venkateswaran 1691 Cisco Systems 1692 510 McCarthy Blvd 1693 Milpitas CA 95035 1694 USA 1696 EMail: arvvenka@cisco.com