idnits 2.17.1 draft-tiruveedhula-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 55 instances of too long lines in the document, the longest one being 28 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 974 has weird spacing: '... of the mplsM...' == Line 1002 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 12, 2015) is 3112 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 435, but not defined == Missing Reference: 'RFC3414' is mentioned on line 1513, but not defined == Missing Reference: 'RFC3826' is mentioned on line 1513, but not defined == Missing Reference: 'RFC5591' is mentioned on line 1515, but not defined == Missing Reference: 'RFC5592' is mentioned on line 1516, but not defined == Missing Reference: 'RFC6353' is mentioned on line 1516, 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 1568, but no explicit reference was found in the text == Unused Reference: 'RFC5561' is defined on line 1590, but no explicit reference was found in the text == Unused Reference: 'RFC6826' is defined on line 1601, but no explicit reference was found in the text == Unused Reference: 'RFC7060' is defined on line 1607, but no explicit reference was found in the text == Unused Reference: 'RFC6389' is defined on line 1612, but no explicit reference was found in the text == Unused Reference: 'RFC2223' is defined on line 1618, but no explicit reference was found in the text == Unused Reference: 'RFC2629' is defined on line 1628, but no explicit reference was found in the text == Unused Reference: 'RFC4181' is defined on line 1632, but no explicit reference was found in the text == Unused Reference: 'RFC4001' is defined on line 1636, but no explicit reference was found in the text -- 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: 1 error (**), 0 flaws (~~), 20 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force Kishore Tiruveedhula, Ed. 3 Internet-Draft Juniper Networks 4 Intended status: Standards Track Uwe Joorde 5 Expires: April 14, 2016 Deutsche Telekom 6 Arvind Venkateswaran 7 Cisco Systems 9 October 12, 2015 11 Definitions of Managed Objects for the LDP Point-to-Multipoint and 12 Multipoint-to-Multipoint Label Switched Paths 13 draft-tiruveedhula-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 http://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 14, 2016. 41 Copyright Notice 43 Copyright (c) 2015 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 (http://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 . . . . . . . . . . . . . . . . . . . . . . . . . 4 61 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 4 62 5. Future Considerations . . . . . . . . . . . . . . . . . . . . 5 63 6. Structure of the MIB Module . . . . . . . . . . . . . . . . . 5 64 6.1. Summary of mLDP Scalar Objects . . . . . . . . . . . . . 5 65 6.2. Summary of mLDP Table Objects . . . . . . . . . . . . . . 5 66 7. mLDP Scalar Objects . . . . . . . . . . . . . . . . . . . . . 6 67 7.1. mplsMldpP2mpCapable . . . . . . . . . . . . . . . . . . . 6 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 . . . . . . . . . . . . . . . . . . . 7 75 7.9. mplsMldpProtLsrCapable . . . . . . . . . . . . . . . . . 7 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 Upstreaam Session Table: 84 mplsMldpFecUpstreamSessTable . . . . . . . . . . . . . . 8 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 . . . . . . . . . . . . . . . . . . . . . 33 95 14. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 33 96 15. References . . . . . . . . . . . . . . . . . . . . . . . . . 33 97 15.1. Normative References . . . . . . . . . . . . . . . . . . 33 98 15.2. Informative References . . . . . . . . . . . . . . . . . 35 99 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 37 100 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . 37 101 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 37 103 1. Introduction 105 This memo defines a portion of the Management Information Base (MIB) 106 for use with network management protocols. In particular it defines 107 objects for managing multicast LDP point-to-multipoint (P2MP) and 108 multipoint-to-multipoint (MP2MP) Label Switched Paths. The MIB 109 module defined in this document is extension of LDP MIB defined in 110 RFC3815 which supports only for LDP point-to-point LSPs. 112 The RFC3815 describes only unicast Managed objects for the Label 113 distribution protocol. The RFC6388 describes LDP protocol extensions 114 for the point to multipoint and multipoint to multipoint LSPs. The 115 RFC 6826 describes multicast LDP inband signalling for P2MP and MP2MP 116 LSPs. 118 This document defines a MIB module for managing and controlling mLDP 119 P2MP and MP2MP LSPs. It builds on the objects and tables defined in 120 [RFC3815] for mLDP MIB. 122 2. The Internet-Standard Management Framework 124 [[CREF1: The title and text for this section has been copied from the 125 official boilerplate, and should not be modified unless the official 126 boilerplate text from the OPS Area web site has changed. See RFC4818 127 section 3.1 for a discussion of the boilerplate section.]] 129 For a detailed overview of the documents that describe the current 130 Internet-Standard Management Framework, please refer to section 7 of 131 RFC 3410 [RFC3410]. 133 Managed objects are accessed via a virtual information store, termed 134 the Management Information Base or MIB. MIB objects are generally 135 accessed through the Simple Network Management Protocol (SNMP). 136 Objects in the MIB are defined using the mechanisms defined in the 137 Structure of Management Information (SMI). This memo specifies a MIB 138 module that is compliant to the SMIv2, which is described in STD 58, 139 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 140 [RFC2580]. 142 3. Conventions 144 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 145 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 146 document are to be interpreted as described in BCP 14, RFC 2119 147 [RFC2119]. 149 4. Overview 151 This document focusses on the management of following multicast LDP 152 (mLDP) features, which were defined after unicast LDP [RFC5036]. 154 RFC6388: Label Distribution Protocol Extensions for Point-to- 155 Multipoint and Multipoint-to-Multipoint Label Switched Paths. 157 RFC6826: Multipoint LDP In-Band Signaling for Point-to-Multipoint 158 and Multipoint-to-Multipoint Label Switched Paths. 160 RFC7060: Using LDP Multipoint Extensions on Targeted LDP Sessions. 162 [I-D.ietf-rtgwg-mofrr] Multicast only Fast Re-Route. 164 [I-D.ietf-mpls-mldp-node-protection] mLDP Node Protection. 166 For all the above features, the mLDP MIB needs to include the 167 following information: 169 - Session Capability (P2MP, MP2MP) information: configured 170 capability, negotiated capability. 172 - mLDP FECs: include opaque information (Generic LSP Identifier, 173 source and group address) and MoFRR enable. 175 - Primary and backup upstream session when mLDP MoFRR enabled. 177 - Active and inactive upstream session for make before break. 179 - mLDP Traffic stats per mLDP Fec: The traffic stats for mLDP fec. 181 - mLDP Traffic stats per per Interface: The mLDP traffic stats per 182 Interface. 184 - Traps when mLDP Fec LSP up, down. 186 5. Future Considerations 188 Any new opaque TLVs added for any other mLDP features, the opaque 189 value object in the mplsMldpFecTable need to be enhanced accordingly. 191 6. Structure of the MIB Module 193 This section describes the structure of the mLDP MIB. In this MIB 194 MPLS-MLDP-STD-MIB, scalar objects, table objects and notifications 195 are defined. Following section describes in details about each 196 object. 198 6.1. Summary of mLDP Scalar Objects 200 New scalar objects mplsMldpP2mpCapable and mplsMldpMp2mpCapable are 201 defined to provide the mLDP capabilities of P2MP, MP2MP support. 203 New scalar objects mplsMldpMbbCapable and mplsMldpMbbTime are defined 204 to provide MBB capability information. 206 New scalar object mplsMldpNumFecs which will give the total number of 207 mLDP FECs setup on the LSR. 209 Another New scalar object mplsMldpNumFecsActive, which will give the 210 total number of active mLDP FECs. 212 New scalar objects mplsMldpPlrCapable, mplsMldpMptCapable, 213 mplsMldpProtLsrCapable and mplsMldpNodeProtCapable are defined to 214 provide mLDP node protection capabilities. 216 6.2. Summary of mLDP Table Objects 218 mplsLdpPeerCapabilityTable to include peer capability information. 220 mplsMldpSessionStatsTable : This table contains the number of mLDP 221 FECs received and advertised to particular LDP session. 223 mplsMldpFecTable: This table is similar to point to point 224 mplsLdpFecTable and will have mLDP specific Fec information. 226 mplsMldpFecBranchStatsTable : This table contains the traffic 227 statistics for the given mLDP FECs on particular interface. 229 mplsMldpFecUpstreamSessTable : Includes the upstream session info for 230 the particular mLDP Fec and also includes the primary or backup 231 upstream session, that may be used for mLDP MoFRR. 233 mplsMldpInterfaceStatsTable : This table contains the traffic 234 statistics for all mLDP related FECs. 236 7. mLDP Scalar Objects 238 There are ten scalars, listed below are defined for this MIB module. 240 7.1. mplsMldpP2mpCapable 242 The mplsMldpP2mpCapable scalar object denotes whether the LSR is 243 capable of supporting multicast LDP with Point-to-Multipoint 244 capability. 246 7.2. mplsMldpMp2mpCapable 248 The mplsMldpMp2mpCapable scalar object denotes whether the LSR is 249 capable of supporting multicast LDP with Multipoint-to-Multipoint 250 LSPs. 252 7.3. mplsMldpMbbCapable 254 The mplsMldpMbbCapable scalar object denotes whether the LSR is 255 capable of supporting multicast LDP with MBB (make before break) 256 feature mentioned in the section 8 of RFC 6388 . 258 7.4. mplsMldpMbbTime 260 The mplsMldpMbbTime scalar object denotes MBB time for which LSR is 261 waiting for MBB Ack from upstream node. This timer helps LSR to 262 prevent waiting indefinitely for the MBB Notification from upstream 263 node. 265 7.5. mplsMldpNumFecs 267 The mplsMldpNumFecs provides a read-only counter of the number of 268 mLDP FECs setup on this LSR. 270 7.6. mplsMldpNumFecsActive 272 The mplsMldpNumFecsActive provides a read-only counter of the number 273 of mLDP FECs Active on this LSR. 275 7.7. mplsMldpPlrCapable 277 The mplsMldpPlrCapable scalar object denotes whether the LSR is 278 capable of supporting PLR capability as specified in the section 5.1 279 of [I-D.ietf-mpls-mldp-node-protection]. 281 7.8. mplsMldpMptCapable 283 The mplsMldpMptCapable scalar object denotes whether the LSR is 284 capable of supporting MPT capability as specified in the section 5.2 285 of [I-D.ietf-mpls-mldp-node-protection]. 287 7.9. mplsMldpProtLsrCapable 289 The mplsMldpProtLsrCapable scalar object denotes whether the LSR is 290 capable of supporting the "Protected LSR" capability as specified in 291 the section 5.3 of [I-D.ietf-mpls-mldp-node-protection]. 293 7.10. mplsMldpNodeProtCapable 295 The mplsMldpNodeProtCapable scalar object denotes whether the LSR is 296 capable of supporting the "Node Protection" capability as specified 297 in the section 5.4 of [I-D.ietf-mpls-mldp-node-protection]. 299 8. mLDP Table Objects 301 8.1. LDP Peer Capability Table mplsLdpPeerCapabilityTable 303 The new table mplsLdpPeerCapabilityTable is read-only table, which 304 contains learned capability information from LDP peer. This table 305 augments the mplsLdpPeerTable, which is defined in RFC 3815. 307 8.2. mLDP Session Stats Table: mplsMldpSessionStatsTable 309 The mplsMldpSessionStatsTable is a read-only table which contains 310 mLDP statistical information on sessions. This table augments the 311 mplsLdpSessionStatsTable, which is defined in the RFC 3815. 313 8.3. mLDP Fec Table: mplsMldpFecTable 315 The mplsMldpFecTable is a table which contains FEC (Forwarding 316 Equivalence Class) information relating to point to multi-point and 317 multipoint to multipoint LDP LSP. Each entry/row represents a single 318 FEC Element. This table is similar LDP LSP FEC Table, 319 mplsLdpLspFecTable, which is defined in the RFC 3815, which 320 associates FECs with the LSPs. 322 8.4. mLDP Fec Branch Traffic statistics Table: 323 mplsMldpFecBranchStatsTable 325 This table mplsMldpFecBranchStatsTable gives the information about 326 number of packets and number of bytes sent out on particualr 327 downstream session or on outgoing interface. 329 8.5. mLDP Fec Upstreaam Session Table: mplsMldpFecUpstreamSessTable 331 The mplsMldpFecUpstreamSessTable is a read-only table which contains 332 mLDP upstream session information for mLDP Fec. This table is 333 similar to mplsInSegmentLdpLspTable. This table will also have 334 information about primary, backup upstream session, and also 335 indicates whether the label is in MBB request or MBB Ack received 336 state. 338 8.6. mLDP Interface Traffic statistics Table: 339 mplsMldpInterfaceStatsTable 341 This table mplsMldpInterfaceStatsTable gives the information about 342 number of mLDP packets and number of mLDP bytes sent and received on 343 particualr interface for all mLDP FECs. 345 9. The mLDP Notifications 347 The RFC 3815 defined some of the notifications related to session and 348 P2P Fec. In this MIB, the following notification added to support 349 mLDP features. 351 The mplsMldpFecUp and mplsMldpFecDown notifications are generated 352 when mLDP FEC changes the state to UP and Down. 354 The mplsMldpMoFrrStatusChange notification is generated when mLDP 355 MoFRR status switches from primary to backup path and vice versa. 357 10. Relationship to Other MIB Modules 359 This section describes relationships between MIB tables defined in 360 this document as part of MPLS-MLDP-STD-MIB, and the tables defined in 361 MPLS-LDP-STD-MIB [RFC3815] and MPLS-LSR-STD-MIB [RFC3813]. 363 The Figure 1 shows the diagrammatic representation of the 364 relationship between MPLS-MLDP-STD-MIB, MPLS-LDP-STD-MIB and MPLS- 365 LSR-STD-MIB. An arrow in the Figure shows that the MIB table pointed 366 from contains a reference to the MIB table pointed to. 368 10.1. Diagrammatic Representation 369 mplsMldpFecTable 370 | 371 | 372 v 373 mplsLdpLspFecTable 374 | | | 375 | | +----------------+ 376 | | | 377 | +---------------+ v 378 | | mplsMldpFecUpstreamSessTable 379 +--->mplsXCTable--+ | 380 | | 381 | | 382 | | 383 | mplsMldpFecBranchStatsTable 384 | | 385 | | 386 | | 387 mplsInSegmentTable<------+ | 388 | | 389 v | 390 mplsOutSegmentTable<-+ 392 Figure 1 : Dependencies Between MIB Tables 394 Figure 1 396 10.2. Relationship to the LSR MIB 398 The LSR MIB [RFC3813] have below tables, which cross connects the 399 incoming label to outgoing label. Below Tables will be used for mLDP 400 also in the similar way as in the point to point LDP LSPs. 402 mplsXCTable 404 mplsInSegmentTable 406 mplsOutSegmentTable 408 10.3. Relationship to the LDP MIB 410 The MIB module defined in this document is extension of MPLS-LDP-STD- 411 MIB to support multicast LDP features. 413 Below optional tables in MPLS-LDP-STD-MIB, will also be used in mLDP 414 for associating the mLDP LSPs to LSR-MIB tables. 416 mplsLdpLspFecTable 418 mplsInSegmentLdpLspTable 420 mplsOutSegmentLdpLspTable 422 11. Multicast MPLS Label Distribution Protocol MIB Definitions 424 MPLS-MLDP-STD-MIB DEFINITIONS ::= BEGIN 425 IMPORTS 426 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 427 Unsigned32, Counter32, Counter64, TimeTicks 428 FROM SNMPv2-SMI -- RFC 2578 429 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 430 FROM SNMPv2-CONF -- RFC 2580 431 TruthValue, RowStatus, StorageType, TimeStamp 432 FROM SNMPv2-TC -- RFC 2579 434 InterfaceIndex 435 FROM IF-MIB -- [RFC2020] 437 mplsStdMIB, MplsLdpIdentifier 438 FROM MPLS-TC-STD-MIB -- RFC 3811 440 MplsIndexType 441 FROM MPLS-LSR-STD-MIB -- RFC 3813 443 IndexInteger, IndexIntegerNextFree 444 FROM DIFFSERV-MIB -- RFC 3289 446 InetAddress, InetAddressType 447 FROM INET-ADDRESS-MIB -- RFC 4001 449 mplsLdpStdMIB 450 FROM MPLS-LDP-STD-MIB -- RFC 3815 451 ; 453 mplsMldpStdMIB MODULE-IDENTITY 454 LAST-UPDATED "201510120000Z" -- October 12, 2015 455 ORGANIZATION "Multiprotocol Label Switching (mpls) 456 Working Group" 457 CONTACT-INFO 459 " Kishore Tiruveedhula 460 Juniper Networks 461 Email: kishoret@juniper.net 462 Uwe Joorde 463 Deutsche Telekom 464 Email: Uwe.Joorde@telekom.de 466 Arvind Venkateswaran 467 Cisco Systems 468 EMail: arvvenka@cisco.com 470 Comments about this document should be emailed 471 directly to the MPLS working group mailing list at 472 mpls@lists.ietf.org" 474 DESCRIPTION 475 "Copyright (c) 2009 IETF Trust and the persons identified as 476 the document authors. All rights reserved. 478 This document is subject to BCP 78 and the IETF Trust's 479 Legal Provisions Relating to IETF Documents in effect on the 480 date of publication of this document 481 (http://trustee.ietf.org/license-info). Please review these 482 documents carefully, as they describe your rights and 483 restrictions with respect to this document. 485 The initial version of this MIB module was published in 486 RFC XXXX. For full legal notices see the RFC itself or see: 487 http://www.ietf.org/copyrights/ianamib.html 488 -- RFC Editor. Please replace XXXX with the RFC number for this 489 -- document and remove this note. 491 This MIB module contains managed object definitions for mLDP LSPS 492 defined in Label Distribution Protocol Extensions Point-to-Multipoint and 493 Multipoint-to-Multipoint Label Switched Paths, RFC 6388, November 494 2011." 496 REVISION "2015101200Z" -- October 12, 2015 497 DESCRIPTION 498 "Initial version issued as part of RFC XXXX." 499 -- RFC Editor. Please replace XXXX with the RFC number for this 500 -- document and remove this note. 502 ::= { mplsStdMIB YYY } 503 -- RFC Editor. Please replace YYY with the codepoint issued by IANA 504 -- and remove this note. 506 -- Top level components of this MIB module. 508 -- notifications 509 mplsMldpNotifications OBJECT IDENTIFIER ::= { mplsMldpStdMIB 0 } 510 -- tables, scalars 511 mplsMldpScalars OBJECT IDENTIFIER ::= { mplsMldpStdMIB 1 } 512 mplsMldpObjects OBJECT IDENTIFIER ::= { mplsMldpStdMIB 2 } 514 -- MPLS mLDP LSP scalars. 516 mplsMldpP2mpCapable OBJECT-TYPE 517 SYNTAX INTEGER { 518 enable(1), 519 disable(2) 520 } 521 MAX-ACCESS read-only 522 STATUS current 523 DESCRIPTION 524 "This object provides the P2MP capability of the LSR." 526 REFERENCE 527 "Section 2.1 of [RFC6388]." 529 ::= { mplsMldpScalars 1 } 531 mplsMldpMp2mpCapable OBJECT-TYPE 532 SYNTAX INTEGER { 533 enable(1), 534 disable(2) 535 } 536 MAX-ACCESS read-only 537 STATUS current 538 DESCRIPTION 539 "This object provides MP2MP capability of the LSR." 541 REFERENCE 542 "Section 3.1 of [RFC6388]." 544 ::= { mplsMldpScalars 2 } 546 mplsMldpMbbCapable OBJECT-TYPE 547 SYNTAX INTEGER { 548 enable(1), 549 disable(2) 550 } 551 MAX-ACCESS read-only 552 STATUS current 553 DESCRIPTION 554 "This object provides MBB (make before break) capability of the LSR." 556 REFERENCE 557 "Section 8.3 of [RFC6388]." 559 ::= { mplsMldpScalars 3 } 561 mplsMldpMbbTime OBJECT-TYPE 562 SYNTAX Unsigned32 (1..300) 563 UNITS "seconds" 564 MAX-ACCESS read-only 565 STATUS current 566 DESCRIPTION 567 "The 32-bit unsigned integer value provides the time for waiting MBB Ack 568 from upstream node." 570 DEFVAL { 30 } 571 ::= { mplsMldpScalars 4 } 573 mplsMldpNumFecs OBJECT-TYPE 574 SYNTAX Unsigned32 575 MAX-ACCESS read-only 576 STATUS current 577 DESCRIPTION 578 "The number of active and passive mLdp Fecs on this device." 580 ::= { mplsMldpScalars 5 } 582 mplsMldpNumFecsActive OBJECT-TYPE 583 SYNTAX Unsigned32 584 MAX-ACCESS read-only 585 STATUS current 586 DESCRIPTION 587 "The number of mLdp FECs Active on this device. The mLDP FEC is 588 considered active if the mplsMldpFecOperStatus is up(1)." 590 ::= { mplsMldpScalars 6 } 592 mplsMldpPlrCapable OBJECT-TYPE 593 SYNTAX INTEGER { 594 enable(1), 595 disable(2) 596 } 597 MAX-ACCESS read-only 598 STATUS current 599 DESCRIPTION 600 "This object provides Point of Local Repair (PLR) 601 capability of the LSR." 603 REFERENCE 604 "Section 5.1 of [I-D.ietf-mpls-mldp-node-protection]." 606 ::= { mplsMldpScalars 7 } 608 mplsMldpMptCapable OBJECT-TYPE 609 SYNTAX INTEGER { 610 enable(1), 611 disable(2) 612 } 613 MAX-ACCESS read-only 614 STATUS current 615 DESCRIPTION 616 "This object provides Merge Point (MPT) capability of the LSR." 618 REFERENCE 619 "Section 5.2 of [I-D.ietf-mpls-mldp-node-protection]." 621 ::= { mplsMldpScalars 8 } 623 mplsMldProtLsrCapable OBJECT-TYPE 624 SYNTAX INTEGER { 625 enable(1), 626 disable(2) 627 } 628 MAX-ACCESS read-only 629 STATUS current 630 DESCRIPTION 631 "This object provides Protected LSR capability." 633 REFERENCE 634 "Section 5.3 of [I-D.ietf-mpls-mldp-node-protection]." 636 ::= { mplsMldpScalars 9 } 638 mplsMldProtNodeProtCapable OBJECT-TYPE 639 SYNTAX INTEGER { 640 enable(1), 641 disable(2) 642 } 643 MAX-ACCESS read-only 644 STATUS current 645 DESCRIPTION 646 "This object provides Node Protection capability of the LSR." 648 REFERENCE 649 "Section 5.3 of [I-D.ietf-mpls-mldp-node-protection]." 651 ::= { mplsMldpScalars 10 } 653 -- End of MPLS mLDP scalars. 655 -- MPLS mLDP tables. 657 -- 658 -- The MPLS LDP Peer Capability Table 659 -- 661 mplsLdpPeerCapabilityTable OBJECT-TYPE 662 SYNTAX SEQUENCE OF MplsLdpPeerCapabilityEntry 663 MAX-ACCESS not-accessible 664 STATUS current 665 DESCRIPTION 666 "This table will have learned information relating to Mldp. 667 ::= { mplsMldpObjects 1 } 669 mplsLdpPeerCapabilityEntry OBJECT-TYPE 670 SYNTAX MplsLdpPeerCapabilityEntry 671 MAX-ACCESS not-accessible 672 STATUS current 673 DESCRIPTION 674 "Information about a single Peer which is related 675 to a Session. This table is augmented by 676 the mplsLdpSessionTable." 677 INDEX { mplsLdpEntityLdpId, 678 mplsLdpEntityIndex, 679 mplsLdpPeerLdpId } 681 ::= { mplsLdpPeerCapabilityTable 1 } 683 mplsLdpPeerCapabilityEntry ::= SEQUENCE { 684 mplsLdpPeerLdpId MplsLdpIdentifier, 685 mplsLdpPeerCapability Integer32, 686 } 688 mplsLdpPeerCapability OBJECT-TYPE 689 SYNTAX BITS { 690 none (0), 691 p2mp (1), 692 mp2mp(2), 693 mbb (3), 694 upstream-label-assignment (4), 695 dynamic (5), 696 plr (6), 697 mpt (7), 698 prot-lsr (8), 699 node-prot (9) 700 } 701 MAX-ACCESS read-only 702 STATUS current 703 DESCRIPTION 704 " This will indicate the LDP capability information about peer. 705 The p2mp indicates peer supports P2MP Capability. 706 The mp2mp indicates peer supports MP2MP Capability. 707 The mbb indicates peer supports MBB Capability. 708 The upstream-label-assignment indicates peer supports Upstream label 709 assignment Capability. 710 The dynamic indicates peer supports dynamic Capability. 711 The plr indicates Point of Local Repair Capability. 712 The mpt indicates Point of Merge Point Capability. 713 The prot-lsr indicates Protected LSR Capability. 714 The node-prot indicates Node Protection LSR Capability. 715 " 717 REFERENCE 718 "RFC6388, Section 2.1 for P2MP Capability TLV. 719 and the section 3.1 for MP2MP Capability TLV. 720 The RFC6388 for MBB Capability TLV. 721 RFC5561 Section 9 for Dynamic Capability Announcement TLV. 722 RFC6389 Section 3 for Upstream Label Assignment Capability TLV. 723 Section 5 of [I-D.ietf-mpls-mldp-node-protection] describes for Point of Local Repair (plr) 724 capability, Merge Point (mpt) capability, 725 The Protected LSR (port-lsr) and Node Protection (node-prot) Capability. " 727 ::= { mplsLdpPeerCapability 2 } 729 -- 730 -- The MPLS mLDP Session Statistics Table 731 -- 733 mplsMldpSessionStatsTable OBJECT-TYPE 734 SYNTAX SEQUENCE OF MplsMldpSessionStatsEntry 735 MAX-ACCESS not-accessible 736 STATUS current 737 DESCRIPTION 738 "A table of statistics related to mLDP on Sessions. 739 This table AUGMENTS the mplsLdpSessionStatsTable." 740 ::= { mplsMldpObjects 2 } 742 mplsMldpSessionStatsEntry OBJECT-TYPE 743 SYNTAX MplsMldpSessionStatsEntry 744 MAX-ACCESS not-accessible 745 STATUS current 746 DESCRIPTION 747 "An entry in this table represents mLDP statistical 748 information on a single session between an LDP 749 Entity and LDP Peer." 751 AUGMENTS { mplsLdpSessionStatsEntry } 752 ::= { mplsmMldpSessionStatsTable 1 } 754 MplsMldpSessionStatsEntry ::= SEQUENCE { 755 mplsMldpSessionStatsNumFecsSent Counter32, 756 mplsMldpSessionStatsNumMbbReqSentState Counter32, 757 mplsMldpSessionStatsNumFecsRcvd Counter32, 758 mplsMldpSessionStatsNumMbbReqRcvdState Counter32, 759 mplsMldpSessionStatsNumMbbResetAckByTimer Counter32 760 } 762 mplsMldpSessionStatsNumFecsSent OBJECT-TYPE 763 SYNTAX Counter32 764 MAX-ACCESS read-only 765 STATUS current 766 DESCRIPTION 767 "This object counts the number of mLDP FECs sent on this 768 session. If the FEC is withdrawn, then this number is 769 decremented. 771 Discontinuities in the value of this counter can occur 772 at re-initialization of the management system, and at 773 other times as indicated by the value of 774 mplsLdpSessionDiscontinuityTime." 776 ::= { mplsMldpSessionStatsEntry 1 } 778 mplsMldpSessionStatsNumMbbReqSentState OBJECT-TYPE 779 SYNTAX Counter32 780 MAX-ACCESS read-only 781 STATUS current 782 DESCRIPTION 783 "This object counts the number of mLDP FECs sent on this 784 session and waiting for MBB Ack. This counter will get incremented 785 when MBB req sent for a label on this session and will get 786 decremented when the MBB Ack received. 788 ::= { mplsMldpSessionStatsEntry 2 } 790 mplsMldpSessionStatsNumFecsRcvd OBJECT-TYPE 791 SYNTAX Counter32 792 MAX-ACCESS read-only 793 STATUS current 794 DESCRIPTION 795 "This object counts the number of mLDP FECs received on this 796 session. If the FEC is withdrawn from the downstream session, 797 then this is decremented. 799 Discontinuities in the value of this counter can occur 800 at re-initialization of the management system, and at 801 other times as indicated by the value of 802 mplsLdpSessionDiscontinuityTime." 804 ::= { mplsMldpSessionStatsEntry 3 } 806 mplsMldpSessionStatsNumMbbReqRcvdState OBJECT-TYPE 807 SYNTAX Counter32 808 MAX-ACCESS read-only 809 STATUS current 810 DESCRIPTION 811 "This object counts the number of mLDP FECs received on this 812 session and waiting for sending MBB Ack. This counter will get 813 incremented when MBB req is received for a label on this session 814 and will get decremented when the MBB Ack sent." 816 ::= { mplsMldpSessionStatsEntry 4 } 818 mplsMldpSessionStatsNumMbbResetAckByTimer OBJECT-TYPE 819 SYNTAX Counter32 820 MAX-ACCESS read-only 821 STATUS current 822 DESCRIPTION 823 "This object counts the number mLDP FECs for which the MBB Ack is 824 reset by MBB timer, in which the LSR is waiting for MBB ack. 826 ::= { mplsMldpSessionStatsEntry 5 } 828 -- 829 -- Mpls mLDP FEC Table 830 -- 832 mplsMldpFecTable OBJECT-TYPE 833 SYNTAX SEQUENCE OF MplsFecEntry 834 MAX-ACCESS not-accessible 835 STATUS current 836 DESCRIPTION 837 "This table represents the FEC 838 (Forwarding Equivalence Class) 839 Information associated with an mLDP LSP." 841 ::= { mplsMldpObjects 3 } 843 mplsMldpFecEntry OBJECT-TYPE 844 SYNTAX MplsMldpFecEntry 845 MAX-ACCESS not-accessible 846 STATUS current 847 DESCRIPTION 848 "Each row represents a single mLDP FEC Element." 849 INDEX { mplsMldpFecIndex } 851 ::= { mplsMldpFecTable 1 } 853 MplsMldpFecEntry ::= SEQUENCE { 854 mplsMldpFecIndex IndexInteger, 855 mplsMldpFecType INTEGER, 856 mplsMldpFecRootAddrType InetAddressType, 857 mplsMldpFecRootAddr InetAddress, 858 mplsMldpFecOpaqueType INTEGER, 859 mplsMldpFecOpaqueGenLspId Unsigned32, 860 mplsMldpFecOpaqueTransitSourceOrBidirAddrType InetAddressType, 861 mplsMldpFecOpaqueTransitSourceOrBidirAddr InetAddress, 862 mplsMldpFecOpaqueTransitGroupAddrType InetAddressType, 863 mplsMldpFecOpaqueTransitGroupAddr InetAddress, 864 mplsMldpFecAdminStatus INTEGER, 865 mplsMldpFecOperStatus INTEGER, 866 mplsMldpFecMoFrr INTEGER, 867 mplsMldpFecLsrState INTEGER, 868 mplsMldpFecUpTime TimeStamp 869 } 871 mplsMldpFecIndex OBJECT-TYPE 872 SYNTAX IndexInteger 873 MAX-ACCESS not-accessible 874 STATUS current 875 DESCRIPTION 876 "The index which uniquely identifies this entry." 878 ::= { mplsMldpFecEntry 1 } 880 mplsMldpFecType OBJECT-TYPE 881 SYNTAX INTEGER { 882 p2mp(6), 883 mp2mpUpstream(7), 884 mp2mpDownstream(8) 885 } 886 MAX-ACCESS read-only 887 STATUS current 888 MAX-ACCESS read-only 889 STATUS current 890 DESCRIPTION 891 "The type of the FEC. If the value of this object 892 is 6, then it is P2MP Fec Type, and 7, 8 are correspond to 893 MP2MP upstream and downstream type." 895 REFERENCE 896 "RFC6388, Section 2.2. The P2MP FEC Element and the section 3.3 897 for the MP2MP Fec elements." 899 ::= { mplsMldpFecEntry 2 } 901 mplsMldpFecRootAddrType OBJECT-TYPE 902 SYNTAX InetAddressType 903 MAX-ACCESS read-only 904 STATUS current 905 DESCRIPTION 906 "The value of this object is the type of the 907 Internet address. The value of this object, 908 decides how the value of the mplsMldpFecRootAddr object 909 is interpreted." 910 REFERENCE 911 "RFC6388, Section 2.2. The P2MP FEC Element and the section 3.3 912 for the MP2MP Fec elements." 914 ::= { mplsMldpFecEntry 3 } 916 mplsMldpFecRootAddr OBJECT-TYPE 917 SYNTAX InetAddress 918 MAX-ACCESS read-only 919 STATUS current 920 DESCRIPTION 921 "The value of this object is interpreted based 922 on the value of the mplsMldpFecRootAddrType object. 923 This is ingress node address for the mLDP LSP." 925 REFERENCE 926 "RFC6388, Section 2.2. The P2MP FEC Element and the section 3.3 927 for the MP2MP Fec elements." 929 ::= { mplsMldpFecEntry 4 } 931 mplsMldpFecOpaqueType OBJECT-TYPE 932 SYNTAX INTEGER { 933 genericLspId(1), 934 transitIpv4Source(3), 935 transitIpv6Source(4), 936 transitIpv4Bidir(5), 937 transitIpv6Bidir(6) 938 } 939 MAX-ACCESS read-only 940 STATUS current 941 DESCRIPTION 942 "This is opaque type of the mLDP FEC. The value of this object is 943 shown below. 945 1 - The Generic LSP Identifier 946 3 - Transit IPv4 Source TLV 947 4 - Transit IPv6 Source TLV 948 5 - Transit IPv4 Bidir TLV 949 6 - Transit IPv6 Bidir TLV. 950 " 951 ::= { mplsMldpFecEntry 5 } 953 mplsMldpFecOpaqueGenLspId OBJECT-TYPE 954 SYNTAX Unsigned32 955 MAX-ACCESS read-only 956 STATUS current 957 DESCRIPTION 958 "The 32-bit unsigned integer value which is to represent Generic 959 LSP ID. This value is only valid if the mplsMldpFecOpaqueType is 960 genericLspId(1), otherwise 0 must be returned." 962 REFERENCE 963 "RFC6388, Section 2.3.1." 965 ::= { mplsMldpFecEntry 6 } 967 mplsMldpFecOpaqueTransitSourceOrBidirAddrType OBJECT-TYPE 968 SYNTAX InetAddressType 969 MAX-ACCESS read-only 970 STATUS current 971 DESCRIPTION 972 "The value of this object is the type of the 973 Internet address. The value of this object, 974 decides how the value of the mplsMldpFecOpaqueTransitSourceOrBidirAddr 975 object is interpreted." 976 REFERENCE 977 "RFC6826, Section 3.1." 979 ::= { mplsMldpFecEntry 7 } 981 mplsMldpFecOpaqueTransitSourceOrBidirAddr OBJECT-TYPE 982 SYNTAX InetAddress 983 MAX-ACCESS read-only 984 STATUS current 985 DESCRIPTION 986 "The value of this object is interpreted based 987 on the value of the mplsMldpFecOpaqueTransitSourceOrBidirAddrType 988 object. This is source node address for the mLDP inband LSP." 990 REFERENCE 991 "RFC6826, Section 3.1." 993 ::= { mplsMldpFecEntry 8 } 995 mplsMldpFecOpaqueTransitGroupAddrType OBJECT-TYPE 996 SYNTAX InetAddressType 997 MAX-ACCESS read-only 998 STATUS current 999 DESCRIPTION 1000 "The value of this object is the type of the 1001 Internet address. The value of this object, 1002 decides how the value of the mplsMldpFecOpaqueTransitGroupAddr 1003 object is interpreted." 1005 REFERENCE 1006 "RFC6826, Section 3.2." 1008 ::= { mplsMldpFecEntry 9 } 1010 mplsMldpFecOpaqueTransitGroupAddr OBJECT-TYPE 1011 SYNTAX InetAddress 1012 MAX-ACCESS read-only 1013 STATUS current 1014 DESCRIPTION 1015 "The value of this object is interpreted based 1016 on the value of the mplsMldpFecOpaqueTransitGroupAddrType 1017 object. This is group node address for the mLDP inband LSP." 1019 REFERENCE 1020 "RFC6826, Section 3.2." 1022 ::= { mplsMldpFecEntry 10 } 1024 mplsMldpFecAdminStatus OBJECT-TYPE 1025 SYNTAX INTEGER { 1026 up(1), -- ready to pass data 1027 down(2) -- out of service 1028 } 1030 MAX-ACCESS read-only 1031 STATUS current 1032 DESCRIPTION 1033 "Indicates the admin status of this mLDP FEC." 1035 DEFVAL { up } 1037 ::= { mplsMldpFecEntry 11 } 1039 mplsMldpFecOperStatus OBJECT-TYPE 1040 SYNTAX INTEGER { 1041 up(1), -- ready to pass data 1042 down(2) -- out of service 1043 } 1044 MAX-ACCESS read-only 1045 STATUS current 1046 DESCRIPTION 1047 "Indicates the actual operational status of this mLDP Fec." 1049 ::= { mplsMldpFecEntry 12 } 1051 mplsMldpFecMoFrr OBJECT-TYPE 1052 SYNTAX INTEGER { 1053 enable(1), 1054 disable(2) 1055 } 1056 MAX-ACCESS read-only 1057 STATUS current 1058 DESCRIPTION 1059 "This object provides whether MoFRR enabled for this mLDP FEC. 1060 on this mLDP FEC. As mentioned in the section 3.2 of [I-D.ietf-rtgwg-mofrr], 1061 When this is enabled, then mLDP may select two upstream sessions, 1062 one is primary and other one is backup. The backup traffic is 1063 discarded when the primary upstream session is UP. When the 1064 primary upstream session goes down, the traffic from the backup 1065 upstream session will be forwarded to downstream. 1066 " 1068 ::= { mplsMldpFecEntry 13 } 1070 mplsMldpFecLsrState OBJECT-TYPE 1071 SYNTAX INTEGER { 1072 egress(1), 1073 bud(2), 1074 transit(3), 1075 ingress(4) 1076 } 1077 MAX-ACCESS read-only 1078 STATUS current 1079 DESCRIPTION 1080 "Indicates the role of FEC either egress, bud, transit or ingress" 1082 ::= { mplsMldpFecEntry 14 } 1084 mplsMldpFecUpTime OBJECT-TYPE 1085 SYNTAX TimeStamp 1086 MAX-ACCESS read-only 1087 STATUS current 1088 DESCRIPTION 1089 "This values shows Fec UP time. This is time since mplsMldpFecOperStatus is UP." 1091 ::= { mplsMldpFecEntry 15 } 1093 -- MPLS mLDP LSP Branch Traffic Stats Table. 1095 mplsMldpFecBranchStatsTable OBJECT-TYPE 1096 SYNTAX SEQUENCE OF MplsMldpFecBranchStatsEntry 1097 MAX-ACCESS not-accessible 1098 STATUS current 1099 DESCRIPTION 1100 "This table provides mLDP Fec branch MPLS Traffic Stats 1101 information." 1103 ::= { mplsMldpObjects 4 } 1105 mplsMldpFecBranchStatsEntry OBJECT-TYPE 1106 SYNTAX MplsMldpFecBranchStatsEntry 1107 MAX-ACCESS not-accessible 1108 STATUS current 1109 DESCRIPTION 1110 "An entry in this table is created by the LSR for each 1111 downstream branch (out-segment) from this LSR for this mLDP 1112 LSP. Each downstream session may represent a single out-segment. 1114 Each entry in the table is indexed by the four identifiers 1115 of the mLDP LSP, and the out-segment that identifies the 1116 outgoing branch." 1118 INDEX { mplsLdpEntityLdpId, 1119 mplsLdpEntityIndex, 1120 mplsLdpPeerLdpId, 1121 mplsMldpFecBranchFecIndex, 1122 mplsMldpFecBranchOutSegIndex 1123 } 1125 ::= { mplsMldpFecBranchStatsTable 1 } 1127 MplsMldpFecBranchStatsEntry ::= SEQUENCE { 1128 mplsMldpFecBranchFecIndex MplsIndexType, 1129 mplsMldpFecBranchOutSegIndex MplsIndexType, 1130 mplsMldpFecBranchStatsPackets Counter64, 1131 mplsMldpFecBranchStatsBytes Counter64, 1132 mplsMldpFecBranchStatsDiscontinuityTime TimeStamp 1133 } 1135 mplsMldpFecBranchFecIndex OBJECT-TYPE 1136 SYNTAX MplsIndexType 1137 MAX-ACCESS not-accessible 1138 STATUS current 1139 DESCRIPTION 1140 "This index identifies the mLDP FEC entry in the 1141 mplsMldpFecTable. This is same as mplsMldpFecIndex." 1143 ::= { mplsMldpFecBranchStatsEntry 1 } 1145 mplsMldpFecBranchOutSegIndex OBJECT-TYPE 1146 SYNTAX MplsIndexType 1147 MAX-ACCESS not-accessible 1148 STATUS current 1149 DESCRIPTION 1150 "This object identifies an outgoing branch from this mLDP LSP 1151 Its value is unique within the context of the mLDP LSP. 1153 This contains the same value as the mplsOutSegmentIndex in the 1154 MPLS-LSR-STD-MIBs mplsOutSegmentTable." 1156 ::= { mplsMldpFecBranchStatsEntry 2 } 1158 mplsMldpFecBranchStatsPackets OBJECT-TYPE 1159 SYNTAX Counter64 1160 MAX-ACCESS read-only 1161 STATUS current 1162 DESCRIPTION 1163 "This object represent the 64-bit value, which gives the number 1164 of packets forwarded by the mLDP LSP onto this branch. 1165 This object should be read in conjunction with 1166 mplsMldpFecBranchStatsDiscontinuityTime." 1168 ::= { mplsMldpFecBranchStatsEntry 3 } 1170 mplsMldpFecBranchStatsBytes OBJECT-TYPE 1171 SYNTAX Counter64 1172 MAX-ACCESS read-only 1173 STATUS current 1174 DESCRIPTION 1175 "This object represent the 64-bit value, which gives the number 1176 of bytes forwarded by the mLDP LSP onto this branch. 1177 This object should be read in conjunction with 1178 mplsMldpFecBranchStatsDiscontinuityTime." 1180 ::= { mplsMldpFecBranchStatsEntry 4 } 1182 mplsMldpFecBranchStatsDiscontinuityTime OBJECT-TYPE 1183 SYNTAX TimeStamp 1184 MAX-ACCESS read-only 1185 STATUS current 1186 DESCRIPTION 1187 "The value of sysUpTime on the most recent occasion at which 1188 any one or more of this rows Counter32 or Counter64 objects 1189 experienced a discontinuity. If no such discontinuity has 1190 occurred since the last re-initialization of the local 1191 management subsystem, then this object contains a zero 1192 value." 1193 ::= { mplsMldpFecBranchStatsEntry 5 } 1195 -- End of mplsMldpFecBranchStatsTable 1197 -- MPLS mLDP LSP Upstream Session Table. 1199 mplsMldpFecUpstreamSessTable OBJECT-TYPE 1200 SYNTAX SEQUENCE OF MplsMldpFecUpstreamSessEntry 1201 MAX-ACCESS not-accessible 1202 STATUS current 1203 DESCRIPTION 1204 "This table provides mLDP Fec upstream Session information." 1206 ::= { mplsMldpObjects 5 } 1208 mplsMldpFecUpstreamSessEntry OBJECT-TYPE 1209 SYNTAX MplsMldpFecUpstreamSessEntry 1210 MAX-ACCESS not-accessible 1211 STATUS current 1212 DESCRIPTION 1213 "An entry in this table is created by the LSR for each 1214 upstream session (in-segment) from this LSR for this mLDP 1215 LSP. Each upstream session may represent a single in-segment. 1217 Each entry in the table is indexed by the four identifiers 1218 of the mLDP LSP, and the in-segment that identifies the 1219 incoming traffic." 1221 INDEX { mplsLdpEntityLdpId, 1222 mplsLdpEntityIndex, 1223 mplsLdpPeerLdpId, 1224 mplsMldpFecUpstreamSessFecIndex, 1225 mplsMldpFecUpstreamSessInSegIndex 1226 } 1228 ::= { mplsMldpFecUpstreamSessTable 1 } 1230 MplsmLdpFecUpstreamSessEntry ::= SEQUENCE { 1231 mplsMldpFecUpstreamSessFecIndex MplsIndexType, 1232 mplsMldpFecUpstreamSessInSegIndex MplsIndexType, 1233 mplsMldpFecUpstreamSessPrimary INTEGER, 1234 mplsMldpFecUpstreamSessActive INTEGER, 1235 mplsMldpFecUpstreamSessPackets Counter64, 1236 mplsMldpFecUpstreamSessBytes Counter64, 1237 mplsMldpFecUpstreamSessDiscontinuityTime TimeStamp 1238 } 1240 mplsMldpFecUpstreamSessFecIndex OBJECT-TYPE 1241 SYNTAX MplsIndexType 1242 MAX-ACCESS not-accessible 1243 STATUS current 1244 DESCRIPTION 1245 "This index identifies the mLDP FEC entry in the 1246 mplsMldpFecTable." 1248 ::= { mplsMldpFecUpstreamSessEntry 1 } 1250 mplsMldpFecUpstreamSessInSegIndex OBJECT-TYPE 1251 SYNTAX MplsIndexType 1252 MAX-ACCESS not-accessible 1253 STATUS current 1254 DESCRIPTION 1255 "This object identifies an upstream session from this mLDP LSP 1256 Its value is unique within the context of the mLDP LSP. 1258 This contains the same value as the mplsInSegmentIndex in the 1259 MPLS-LSR-STD-MIBs mplsInSegmentTable." 1261 ::= { mplsMldpFecUpstreamSessEntry 2 } 1263 mplsMldpFecUpstreamSessPrimary OBJECT-TYPE 1264 SYNTAX INTEGER { 1265 primary(1), 1266 backup(2) 1267 } 1269 MAX-ACCESS read-only 1270 STATUS current 1271 DESCRIPTION 1272 "This indicated wether the received traffic from upstream is 1273 primary or backup. This is valid only if the MoFRR 1274 (mplsMldpFecMoFrr) is enabled on this FEC." 1276 ::= { mplsMldpFecUpstreamSessEntry 3 } 1278 mplsMldpFecUpstreamSessActive OBJECT-TYPE 1279 SYNTAX INTEGER { 1280 active(1), 1281 inactive(2) 1282 } 1283 MAX-ACCESS read-only 1284 STATUS current 1285 DESCRIPTION 1286 "This indicates whether the upstream session is active, means the 1287 LSR programmed the forwarding engine to receive the traffic from 1288 this upstream session. This will be Inactive if the LSR is wating 1289 for MBB Ack." 1291 ::= { mplsMldpFecUpstreamSessEntry 4 } 1293 mplsMldpFecUpstreamSessPackets OBJECT-TYPE 1294 SYNTAX Counter64 1295 MAX-ACCESS read-only 1296 STATUS current 1297 DESCRIPTION 1298 "This object represent the 64-bit value, which gives the number 1299 of packets received by the mLDP LSP from this upstream 1300 session. This object should be read in conjunction with 1301 mplsMldpFecUpstreamSessDiscontinuityTime." 1303 ::= { mplsMldpFecUpstreamSessEntry 5 } 1305 mplsMldpFecUpstreamSessBytes OBJECT-TYPE 1306 SYNTAX Counter64 1307 MAX-ACCESS read-only 1308 STATUS current 1309 DESCRIPTION 1310 "This object represent the 64-bit value, which gives the number 1311 of bytes received by the mLDP LSP from this upstream 1312 session. This object should be read in conjunction with 1313 mplsMldpFecUpstreamSessDiscontinuityTime." 1315 ::= { mplsMldpFecUpstreamSessEntry 6 } 1317 mplsMldpFecUpstreamSessDiscontinuityTime OBJECT-TYPE 1318 SYNTAX TimeStamp 1319 MAX-ACCESS read-only 1320 STATUS current 1321 DESCRIPTION 1322 "The value of sysUpTime on the most recent occasion at which 1323 any one or more of this rows Counter32 or Counter64 objects 1324 experienced a discontinuity. If no such discontinuity has 1325 occurred since the last re-initialization of the local 1326 management subsystem, then this object contains a zero 1327 value." 1328 ::= { mplsMldpFecUpstreamSessEntry 7 } 1330 -- End of mplsMldpFecBranchStatsTable 1332 -- MPLS mLDP Interface Traffic Stats Table. 1334 mplsMldpInterfaceStatsTable OBJECT-TYPE 1335 SYNTAX SEQUENCE OF MplsMldpInterfaceStatsEntry 1336 MAX-ACCESS not-accessible 1337 STATUS current 1338 DESCRIPTION 1339 "This table provides mLDP Traffic Stats on specified interface." 1341 ::= { mplsMldpObjects 6 } 1343 mplsMldpInterfaceStatsEntry OBJECT-TYPE 1344 SYNTAX MplsMldpInterfaceStatsEntry 1345 MAX-ACCESS not-accessible 1346 STATUS current 1347 DESCRIPTION 1348 "An entry in this table is created by the LSR for each 1349 downstream branch (out-segment) from this LSR for this mLDP 1350 LSP. Each downstream session may represent a single out-segment. 1352 Each entry in the table is indexed by the four identifiers 1353 of the mLDP LSP, and the out-segment that identifies the 1354 outgoing branch." 1356 INDEX { mplsMldpInterfaceIndex 1357 } 1359 ::= { mplsMldpInterfaceStatsTable 1 } 1361 MplsMldpInterfaceStatsEntry ::= SEQUENCE { 1362 mplsMldpInterfaceIndex InterfaceIndex, 1363 mplsMldpInterfaceStatsSentPackets Counter64, 1364 mplsMldpInterfaceStatsSentBytes Counter64, 1365 mplsMldpInterfaceStatsRecvPackets Counter64, 1366 mplsMldpInterfaceStatsRecvBytes Counter64 1367 } 1369 mplsMldpInterfaceIndex OBJECT-TYPE 1370 SYNTAX InterfaceIndex 1371 MAX-ACCESS not-accessible 1372 STATUS current 1373 DESCRIPTION 1374 "This index identifies the specific interface. " 1376 ::= { mplsMldpInterfaceStatsEntry 1 } 1378 mplsMldpInterfaceStatsSentPackets OBJECT-TYPE 1379 SYNTAX Counter64 1380 MAX-ACCESS read-only 1381 STATUS current 1382 DESCRIPTION 1383 "This is 64 bit value, which gives the number of packets 1384 forwarded by all mLDP LSPs onto this interface." 1386 ::= { mplsMldpInterfaceStatsEntry 2 } 1388 mplsMldpInterfaceStatsSentBytes OBJECT-TYPE 1389 SYNTAX Counter64 1390 MAX-ACCESS read-only 1391 STATUS current 1392 DESCRIPTION 1393 "This is 64 bit value, which gives the number of bytes 1394 forwarded by all mLDP LSPs onto this interface." 1396 ::= { mplsMldpInterfaceStatsEntry 3 } 1398 mplsMldpInterfaceRecvPackets OBJECT-TYPE 1399 SYNTAX Counter64 1400 MAX-ACCESS read-only 1401 STATUS current 1402 DESCRIPTION 1403 "This is 64 bit value, which gives the number of packets 1404 received by all mLDP LSPs from this interface." 1406 ::= { mplsMldpInterfaceStatsEntry 4 } 1408 mplsMldpInterfaceStatsRecvBytes OBJECT-TYPE 1409 SYNTAX Counter64 1410 MAX-ACCESS read-only 1411 STATUS current 1412 DESCRIPTION 1413 "This is 64 bit value, which gives the number of bytes 1414 received by all mLDP LSPs from this interface." 1416 ::= { mplsMldpInterfaceStatsEntry 5 } 1418 -- End of mplsMldpInterfaceStatsTable 1420 -- Notifications. 1422 mplsMldpFecUp NOTIFICATION-TYPE 1423 OBJECTS { 1424 mplsMldpFecAdminStatus, 1425 mplsMldpFecOperStatus 1426 } 1427 STATUS current 1428 DESCRIPTION 1429 "This notification is generated when a mplsMldpFecOperStatus 1430 object changes from down to up." 1432 ::= { mplsMldpNotifications 1 } 1434 mplsMldpFecDown NOTIFICATION-TYPE 1435 OBJECTS { 1436 mplsMldpFecAdminStatus, 1437 mplsMldpFecOperStatus 1438 } 1439 STATUS current 1440 DESCRIPTION 1441 "This notification is generated when a mplsMldpFecOperStatus 1442 object changes from up to down." 1444 ::= { mplsMldpNotifications 2 } 1446 mplsMldpMoFrrStatusChange NOTIFICATION-TYPE 1447 OBJECTS { 1448 mplsMldpFecUpstreamSessPrimary, 1449 } 1450 STATUS current 1451 DESCRIPTION 1452 "This notification is generated when a mplsMldpFecUpstreamSessPrimary 1453 object changes from primary to backup and vice versa." 1455 ::= { mplsMldpNotifications 3 } 1457 -- End of notifications. 1459 12. Security Considerations 1461 This MIB module is useful for the configuration of certain objects 1462 and monitoring of mLDP LSPs. 1464 There are no management objects defined in this MIB module that have 1465 a MAX-ACCESS clause of read-write and/or read-create. So, if this 1466 MIB module is implemented correctly, then there is no risk that an 1467 intruder can alter or create any management objects of this MIB 1468 module via direct SNMP SET operations. 1470 Some of the readable objects in this MIB module (i.e., objects with a 1471 MAX-ACCESS other than not-accessible) may be considered sensitive or 1472 vulnerable in some network environments. It is thus important to 1473 control even GET and/or NOTIFY access to these objects and possibly 1474 to even encrypt the values of these objects when sending them over 1475 the network via SNMP. These are the tables and objects and their 1476 sensitivity/vulnerability: 1478 o mplsMldpFecTable 1480 o mplsLdpPeerCapabilityTable 1482 o mplsMldpSessionStatsTable 1484 o mplsMldpFecBranchStatsTable 1486 o mplsMldpFecUpstreamSessTable 1488 o mplsMldpInterfaceStatsTable 1490 o mplsMldpNumFecs 1492 o mplsMldpNumFecsActive 1494 o mplsMldpMbbTime 1496 Above listed tables and objects show information about the mLDP LSPs, 1497 its route through the network, and its traffic statistics. Knowledge 1498 of this information could be used to compromise the network, or 1499 simply to breach confidentiality. If an Administrator does not want 1500 to reveal this information, these tables and objects should be 1501 considered sensitive/vulnerable. 1503 SNMP versions prior to SNMPv3 did not include adequate security. 1504 Even if the network itself is secure (for example by using IPsec), 1505 there is no control as to who on the secure network is allowed to 1506 access and GET/SET (read/change/create/delete) the objects in this 1507 MIB module. 1509 Implementations SHOULD provide the security features described by the 1510 SNMPv3 framework (see [RFC3410]), and implementations claiming 1511 compliance to the SNMPv3 standard MUST include full support for 1512 authentication and privacy via the User-based Security Model (USM) 1513 [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations 1514 MAY also provide support for the Transport Security Model (TSM) 1515 [RFC5591] in combination with a secure transport such as SSH 1516 [RFC5592] or TLS/DTLS [RFC6353]. 1518 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1519 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1520 enable cryptographic security. It is then a customer/operator 1521 responsibility to ensure that the SNMP entity giving access to an 1522 instance of this MIB module is properly configured to give access to 1523 the objects only to those principals (users) that have legitimate 1524 rights to indeed GET or SET (change/create/delete) them. 1526 13. IANA Considerations 1528 This is new MPLS MIB module, contained in this document and IANA is 1529 requested to assign an oid (mplsStdMIB YYY) under the mplsStdMIB 1530 subtree to the MPLS-MLDP-STD-MIB module specified in this document. 1532 14. Acknowledgments 1534 The authors wish to thank Santosh Esale, Alia Atlas and Martin Ehlers 1535 for doing the detailed review. Thanks to Adrian Farrel and Raveendra 1536 Torvi for their input to this work and for many helpful suggestions. 1538 15. References 1540 15.1. Normative References 1542 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1543 Requirement Levels", BCP 14, RFC 2119, 1544 DOI 10.17487/RFC2119, March 1997, 1545 . 1547 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1548 Schoenwaelder, Ed., "Structure of Management Information 1549 Version 2 (SMIv2)", STD 58, RFC 2578, 1550 DOI 10.17487/RFC2578, April 1999, 1551 . 1553 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1554 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 1555 STD 58, RFC 2579, DOI 10.17487/RFC2579, April 1999, 1556 . 1558 [RFC2580] McCloghrie, K., Ed., Perkins, D., Ed., and J. 1559 Schoenwaelder, Ed., "Conformance Statements for SMIv2", 1560 STD 58, RFC 2580, DOI 10.17487/RFC2580, April 1999, 1561 . 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 [RFC3811] Nadeau, T., Ed. and J. Cucchiara, Ed., "Definitions of 1569 Textual Conventions (TCs) for Multiprotocol Label 1570 Switching (MPLS) Management", RFC 3811, 1571 DOI 10.17487/RFC3811, June 2004, 1572 . 1574 [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, 1575 "Multiprotocol Label Switching (MPLS) Label Switching 1576 Router (LSR) Management Information Base (MIB)", RFC 3813, 1577 DOI 10.17487/RFC3813, June 2004, 1578 . 1580 [RFC3815] Cucchiara, J., Sjostrand, H., and J. Luciani, "Definitions 1581 of Managed Objects for the Multiprotocol Label Switching 1582 (MPLS), Label Distribution Protocol (LDP)", RFC 3815, 1583 DOI 10.17487/RFC3815, June 2004, 1584 . 1586 [RFC5036] Andersson, L., Ed., Minei, I., Ed., and B. Thomas, Ed., 1587 "LDP Specification", RFC 5036, DOI 10.17487/RFC5036, 1588 October 2007, . 1590 [RFC5561] Thomas, B., Raza, K., Aggarwal, S., Aggarwal, R., and JL. 1591 Le Roux, "LDP Capabilities", RFC 5561, 1592 DOI 10.17487/RFC5561, July 2009, 1593 . 1595 [RFC6388] Wijnands, IJ., Ed., Minei, I., Ed., Kompella, K., and B. 1596 Thomas, "Label Distribution Protocol Extensions for Point- 1597 to-Multipoint and Multipoint-to-Multipoint Label Switched 1598 Paths", RFC 6388, DOI 10.17487/RFC6388, November 2011, 1599 . 1601 [RFC6826] Wijnands, IJ., Ed., Eckert, T., Leymann, N., and M. 1602 Napierala, "Multipoint LDP In-Band Signaling for Point-to- 1603 Multipoint and Multipoint-to-Multipoint Label Switched 1604 Paths", RFC 6826, DOI 10.17487/RFC6826, January 2013, 1605 . 1607 [RFC7060] Napierala, M., Rosen, E., and IJ. Wijnands, "Using LDP 1608 Multipoint Extensions on Targeted LDP Sessions", RFC 7060, 1609 DOI 10.17487/RFC7060, November 2013, 1610 . 1612 [RFC6389] Aggarwal, R. and JL. Le Roux, "MPLS Upstream Label 1613 Assignment for LDP", RFC 6389, DOI 10.17487/RFC6389, 1614 November 2011, . 1616 15.2. Informative References 1618 [RFC2223] Postel, J. and J. Reynolds, "Instructions to RFC Authors", 1619 RFC 2223, DOI 10.17487/RFC2223, October 1997, 1620 . 1622 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 1623 "Introduction and Applicability Statements for Internet- 1624 Standard Management Framework", RFC 3410, 1625 DOI 10.17487/RFC3410, December 2002, 1626 . 1628 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 1629 DOI 10.17487/RFC2629, June 1999, 1630 . 1632 [RFC4181] Heard, C., Ed., "Guidelines for Authors and Reviewers of 1633 MIB Documents", BCP 111, RFC 4181, DOI 10.17487/RFC4181, 1634 September 2005, . 1636 [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. 1637 Schoenwaelder, "Textual Conventions for Internet Network 1638 Addresses", RFC 4001, DOI 10.17487/RFC4001, February 2005, 1639 . 1641 [I-D.ietf-rtgwg-mofrr] 1642 Karan, A., Filsfils, C., Wijnands, I., and B. Decraene, 1643 "Multicast only Fast Re-Route", draft-ietf-rtgwg-mofrr-08 1644 (work in progress), May 2015. 1646 [I-D.ietf-mpls-mldp-node-protection] 1647 Wijnands, I., Raza, K., Atlas, A., Tantsura, J., and Q. 1648 Zhao, "mLDP Node Protection", draft-ietf-mpls-mldp-node- 1649 protection-08 (work in progress), September 2015. 1651 Appendix A. Change Log 1653 Appendix B. Open Issues 1655 Authors' Addresses 1657 Kishore Tiruveedhula (editor) 1658 Juniper Networks 1659 10 Technology Park Drive 1660 Westford MA 01886 1661 USA 1663 Phone: +1 9785898861 1664 EMail: kishoret@juniper.net 1666 Uwe Joorde 1667 Deutsche Telekom 1668 Dahlweg 100 1669 Munster 48153 1670 Germany 1672 EMail: Uwe.Joorde@telekom.de 1674 Arvind Venkateswaran 1675 Cisco Systems 1676 510 McCarthy Blvd 1677 Milpitas CA 95035 1678 USA 1680 EMail: arvvenka@cisco.com