idnits 2.17.1 draft-ietf-ccamp-gmpls-te-mib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 42 longer pages, the longest (page 2) being 61 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There is 1 instance of too long lines in the document, the longest one being 1 character in excess of 72. == There are 4 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == 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 seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (August 2003) is 7550 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: 'GMPLSRSVPTE' is mentioned on line 190, but not defined == Missing Reference: 'GMPLSCRLDP' is mentioned on line 190, but not defined == Unused Reference: 'RFC2863' is defined on line 1982, but no explicit reference was found in the text == Unused Reference: 'RFC3209' is defined on line 1989, but no explicit reference was found in the text == Unused Reference: 'RFC3212' is defined on line 1994, but no explicit reference was found in the text == Unused Reference: 'RFC3471' is defined on line 2002, but no explicit reference was found in the text == Unused Reference: 'RFC3472' is defined on line 2006, but no explicit reference was found in the text == Unused Reference: 'RFC3473' is defined on line 2010, but no explicit reference was found in the text == Unused Reference: 'GMPLSSonetSDH' is defined on line 2018, but no explicit reference was found in the text == Unused Reference: 'GMPLS-OSPF' is defined on line 2055, but no explicit reference was found in the text == Unused Reference: 'RFC2026' is defined on line 2061, but no explicit reference was found in the text == Unused Reference: 'RFC3413' is defined on line 2064, but no explicit reference was found in the text == Unused Reference: 'RFC3411' is defined on line 2072, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLSArch' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLSSonetSDH' -- Possible downref: Non-RFC (?) normative reference: ref. 'TCMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'TEMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'LSRMIB' == Outdated reference: A later version (-16) exists of draft-ietf-ccamp-gmpls-te-mib-01 == Outdated reference: A later version (-15) exists of draft-ietf-ccamp-gmpls-lsr-mib-01 == Outdated reference: A later version (-12) exists of draft-ietf-ccamp-ospf-gmpls-extensions-07 Summary: 3 errors (**), 0 flaws (~~), 21 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 CCAMP Working Group Thomas D. Nadeau 3 Internet Draft Cisco Systems, Inc. 4 Expires: February 2004 5 Cheenu Srinivasan 6 Bloomberg L.P. 8 Adrian Farrel 9 Old Dog Consulting 11 Tim Hall 12 Ed Harrison 13 Data Connection Ltd. 15 August 2003 17 Generalized Multiprotocol Label Switching (GMPLS) Traffic 18 Engineering Management Information Base 20 draft-ietf-ccamp-gmpls-te-mib-01.txt 22 Status of this Memo 24 This document is an Internet-Draft and is in full conformance with 25 all provisions of Section 10 of RFC2026. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF), its areas, and its working groups. Note that 29 other groups may also distribute working documents as Internet- 30 Drafts. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 The list of current Internet-Drafts can be accessed at 38 http://www.ietf.org/ietf/1id-abstracts.txt. 40 The list of Internet-Draft Shadow Directories can be accessed at 41 http://www.ietf.org/shadow.html. 43 Abstract 45 This memo defines an experimental portion of the Management 46 Information Base (MIB) for use with network management protocols in 47 the Internet community. In particular, it describes managed objects 48 for Generalized Multiprotocol Label Switching (GMPLS) based traffic 49 engineering. 51 Table of Contents 53 1. Introduction 2 54 1.1. Migration Strategy 3 55 2. Terminology 3 56 3. The SNMP Management Framework 3 57 4. Outline 4 58 4.1. Summary of GMPLS Traffic Engineering MIB Module 4 59 5. Brief Description of GMPLS TE MIB Objects 4 60 5.1. gmplsTunnelTable 4 61 5.2. gmplsTunnelHopTable 5 62 5.3. gmplsTunnelARHopTable 5 63 5.4. gmplsTunnelCHopTable 5 64 5.5. gmplsTunnelErrorTable 5 65 5.6. gmplsTunnelPerfTable 5 66 6. Cross-referencing to the mplsLabelTable 5 67 7. Example of GMPLS Tunnel Setup 6 68 8. GMPLS Traffic Engineering MIB Definitions 8 69 9. Security Considerations 36 70 10. Acknowledgments 37 71 11. References 37 72 11.1. Normative Refenerces 37 73 11.2. Informational References 39 74 12. Authors' Addresses 39 75 13. Full Copyright Statement 40 76 14. Intellectual Property Notice 41 77 15. Changes and Pending Work 41 78 15.1. Pending Work 41 80 1. Introduction 82 This memo defines a portion of the Management Information Base (MIB) 83 for use with network management protocols in the Internet community. 84 In particular, it describes managed objects for modeling a 85 Generalized Multi-Protocol Label Switching (GMPLS) [GMPLSArch] based 86 traffic engineering. The tables and objects defined in this document 87 extend those defined in the equivalent document for MPLS traffic 88 engineering [TEMIB], and management of GMPLS traffic engineering is 89 built on management of MPLS traffic engineering. 91 This MIB module should be used in conjunction with the companion 92 document [GMPLSLSRMIB] for GMPLS based traffic engineering 93 configuration and management. 95 Comments should be made direct to the CCAMP mailing list at 96 ccamp@ops.ietf.org. 98 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 99 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 100 document are to be interpreted as described in RFC 2119, reference 101 [RFC2119]. 103 1.1. Migration Strategy 105 This MIB extends the traffic engineering MIB defined for use with 106 MPLS [TEMIB]. It provides additions for support of GMPLS tunnels. 108 The companion document modeling and managing GMPLS based LSRs 109 [GMPLSLSRMIB] extends MPLS LSR MIB [LSRMIB] with the same intentions. 111 Textual conventions and OBJECT-IDENTIFIERS are defined in [TCMIB] and 112 [GMPLSTCMIB]. 114 2. Terminology 116 This document uses terminology from the MPLS architecture document 117 [RFC3031], from the GMPLS architecture document [GMPLSArch], and from 118 the MPLS Label Switch Router MIB [LSRMIB]. Some frequently used terms 119 are described next. 121 An explicitly routed LSP (ERLSP) is referred to as a GMPLS tunnel. It 122 consists of in-segment(s) and/or out-segment(s) at the egress/ingress 123 LSRs, each segment being associated with one GMPLS enabled interface. 124 These are also referred to as tunnel segments. 126 Additionally, at an intermediate LSR, we model a connection as 127 consisting of one or more in-segments and/or one or more out- 128 segments. The binding or interconnection between in-segments and out- 129 segments in performed using a cross-connect. 131 These segment and cross-connect objects are defined in the MPLS Label 132 Switch Router MIB [LSRMIB], but see also the GMPLS Label Switch 133 Router MIB [GMPLSLSRMIB] for the GMPLS-specific extensions to these 134 objects. 136 3. The SNMP Management Framework 138 For a detailed overview of the documents that describe the current 139 Internet-Standard Management Framework, please refer to section 7 of 140 RFC 3410 [RFC3410]. 142 Managed objects are accessed via a virtual information store, termed 143 the Management Information Base or MIB. MIB objects are generally 144 accessed through the Simple Network Management Protocol (SNMP). 145 Objects in the MIB are defined using the mechanisms defined in the 146 Structure of Management Information (SMI). This memo specifies a 147 MIB module that is compliant to the SMIv2, which is described in STD 148 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 149 2580 [RFC2580]. 151 4. Outline 153 Support for GMPLS traffic-engineered tunnels requires the following 154 configuration. 156 - Setting up tunnels with appropriate MPLS configuration parameters 157 using [TEMIB]. 158 - Extending the tunnels with GMPLS configuration parameters. 159 - Configuring tunnel loose and strict source routed hops. 161 These actions may need to be accompanied with corresponding actions 162 using [LSRMIB] and [GMPLSLSRMIB] to establish and configure tunnel 163 segments, if this is done manually. Also, the in-segment and out- 164 segment performance tables, mplsInSegmentPerfTable and 165 mplsOutSegmentPerfTable [LSRMIB], should be used to determine 166 performance of the tunnels and tunnel segments although it should be 167 noted that those tables may not be appropriate for measuring 168 performance on some times of GMPLS links. 170 4.1. Summary of GMPLS Traffic Engineering MIB Module 172 The MIB objects for performing the actions listed above that cannot 173 be performed solely using the MIB objects defined in [TEMIB] consist 174 of the following tables. 176 - Tunnel Table (gmplsTunnelTable) for providing GMPLS-specific 177 tunnel configuration parameters. 178 - Tunnel specified, actual, and computed hop tables 179 (gmplsTunnelHopTable, gmplsTunnelARHopTable, and 180 gmplsTunnelCHopTable) for providing additional configuration of 181 strict and loose source routed tunnel hops. 182 - Performance and error reporting tables (gmplsTunnelPerfTable and 183 gmplsTunnelErrorTable). 185 These tables are described in the subsequent sections. 187 5. Brief Description of GMPLS TE MIB Objects 189 The objects described in this section support the functionality 190 described in [GMPLSRSVPTE] and [GMPLSCRLDP] for GMPLS tunnels. 191 The tables support both manually configured and signaled tunnels. 193 5.1. gmplsTunnelTable 195 The gmplsTunnelTable extends the MPLS traffic engineering MIB to 196 allow GMPLS tunnels to be created between an LSR and a remote 197 endpoint, and existing GMPLS tunnels to be reconfigured or removed. 199 Note that we only support point-to-point tunnel segments, although 200 multi-point-to-point and point-to-multi-point connections are 201 supported by an LSR acting as a cross-connect. 203 Each tunnel can thus have one out-segment originating at an LSR 204 and/or one in-segment terminating at that LSR. 206 5.2. gmplsTunnelHopTable 208 The gmplsTunnelHopTable is used to indicate additional parameters for 209 the hops, strict or loose, of a GMPLS tunnel defined in 210 gmplsTunnelTable, when it is established using signaling. Multiple 211 tunnels may share the same hops by pointing to the same entry in this 212 table. 214 5.3. gmplsTunnelARHopTable 216 The gmplsTunnelARHopTable is used to indicate the actual hops 217 traversed by a tunnel as reported by the signaling protocol after the 218 tunnel is setup. The support of this table is optional since not all 219 GMPLS signaling protocols support this feature. 221 5.4. gmplsTunnelCHoptable 223 The gmplsTunnelCHopTable lists the actual hops computed by a 224 constraint-based routing algorithm based on the gmplsTunnelHopTable. 225 The support of this table is optional since not all implementations 226 support computation of hop list using a constraint-based routing 227 protocol. 229 5.5. gmplsTunnelErrorTable 231 The gmplsTunnelErrorTable provides access to information about the 232 last error that occurred on each tunnel known about by the MIB. It 233 indicates the nature of the error, when and how it was reported and 234 can give recovery advice through a display string. 236 5.6. gmplsTunnelPerfTable 238 gmplsTunnelPerfTable provides additional counters to measure the 239 performance of GMPLS tunnels in which packets are visible. It 240 supplements the counters in mplsTunnelPerfTable and augments 241 gmplsTunnelTable. 243 Note that not all counters may be appropriate or available for some 244 types of tunnel. 246 6. Cross-referencing to the mplsLabelTable 248 The gmplsLabelTable is found in a MIB module in [GMPLSLSRMIB] and 249 provides a way to model labels in a GMPLS system where labels might 250 not be simple 32 bit integers. 252 The hop tables in this document (gmplsHopTable, gmplsCHopTable and 253 gmplsARHopTable) use arbitrary indexes to point to entries in the 254 mplsLabelTable to indicate specific label values. 256 Since the primary indexes into gmplsLabelTable are the interface 257 index and a simple 32 bit integer (gmplsLabelIndex), in systems where 258 the nature of a label is well-known, and where the label can safely 259 be encoded as a 32 bit integer (for example a conventional MPLS 260 system), the gmplsLabelTable does not need to be supported in the 261 code implementation and the index pointers to the gmplsLabelTable 262 (gmplsTunnelHopExplicitLabel, gmplsTunnelHopExplicitReverseLabel, 263 gmplsTunnelCHopExplicitLabel, gmplsTunnelCHopExplicitReverseLabel, 264 gmplsTunnelARHopExplicitLabel, gmplsTunnelARHopExplicitReverseLabel) 265 may be replaced with the direct label values. 267 This provides both a good way to support legacy systems that 268 implement the previous version of this MIB [TEMIB], and a significant 269 simplification in GMPLS systems that are limited to a single, simple 270 label type. 272 Note that gmplsLabelTable supports concatenated labels through the 273 use of a label sub-index (gmplsLabelSubindex). 275 7. Example of GMPLS Tunnel Setup 277 This section contains an example of which MIB objects should be 278 modified to create a GMPLS tunnel. This example shows a best effort, 279 loosely routed, bidirectional traffic engineered tunnel, which spans 280 two hops of a simple network, uses Generalized Label requests with 281 Lambda encoding, has label recording and shared link layer 282 protection. Note that these objects should be created on the "head- 283 end" LSR. 285 First in the mplsTunnelTable: 286 { 287 mplsTunnelIndex = 1, 288 mplsTunnelInstance = 1, 289 mplsTunnelIngressLSRId = 123.123.125.1, 290 mplsTunnelEgressLSRId = 123.123.126.1, 291 mplsTunnelName = "My first tunnel", 292 mplsTunnelDescr = "Here to there and back again", 293 mplsTunnelIsIf = true (1), 294 mplsTunnelXCPointer = mplsXCIndex.3.0.0.12, 295 mplsTunnelSignallingProto = none (1), 296 mplsTunnelSetupPrio = 0, 297 mplsTunnelHoldingPrio = 0, 298 mplsTunnelSessionAttributes = recordRoute (4), 299 mplsTunnelOwner = snmp (2), 300 mplsTunnelLocalProtectInUse = false (0), 301 mplsTunnelResourcePointer = mplsTunnelResourceIndex.6, 302 mplsTunnelInstancePriority = 1, 303 mplsTunnelHopTableIndex = 1, 304 mplsTunnelPrimaryInstance = 0, 305 mplsTunnelIncludeAnyAffinity = 0, 306 mplsTunnelIncludeAllAffinity = 0, 307 mplsTunnelExcludeAnyAffinity = 0, 308 mplsTunnelPathInUse = 1, 309 mplsTunnelRole = head(1), 310 mplsTunnelRowStatus = createAndWait (5), 311 } 312 In gmplsTunnelTable(1,1,123.123.125.1,123.123.126.1): 313 { 314 gmplsTunnelIsUnnum = true (1), 315 gmplsTunnelAttributes = labelRecordingRequired (1), 316 gmplsTunnelLSPEncoding = tunnelLspLambda (8), 317 gmplsTunnelSwitchingType = lsc (150), 318 gmplsTunnelLinkProtection = shared (2), 319 gmplsTunnelGPid = lambda (37), 320 gmplsTunnelDirection = bidirectional (1) 321 } 323 Entries in the mplsTunnelResourceTable, mplsTunnelHopTable and 324 gmplsTunnelHopTable are created and activated at this time. 326 In mplsTunnelResourceTable: 327 { 328 mplsTunnelResourceIndex = 6, 329 mplsTunnelResourceMaxRate = 0, 330 mplsTunnelResourceMeanRate = 0, 331 mplsTunnelResourceMaxBurstSize = 0, 332 mplsTunnelResourceRowStatus = createAndGo (4) 333 } 335 The next two instances of mplsTunnelHopEntry are used to denote the 336 hops this tunnel will take across the network. 338 The following denotes the beginning of the network, or the first hop. 339 We have used the fictitious LSR identified by "123.123.125.1" as our 340 example head-end router. 342 In mplsTunnelHopTable: 343 { 344 mplsTunnelHopListIndex = 1, 345 mplsTunnelPathOptionIndex = 1, 346 mplsTunnelHopIndex = 1, 347 mplsTunnelHopAddrType = ipV4 (1), 348 mplsTunnelHopIpv4Addr = 123.123.125.1, 349 mplsTunnelHopIpv4PrefixLen = 9, 350 mplsTunnelHopType = strict (1), 351 mplsTunnelHopRowStatus = createAndGo (4), 352 } 354 The following denotes the end of the network, or the last hop in our 355 example. We have used the fictitious LSR identified by 356 "123.123.126.1" as our end router. 358 In mplsTunnelHopTable: 359 { 360 mplsTunnelHopListIndex = 1, 361 mplsTunnelPathOptionIndex = 1, 362 mplsTunnelHopIndex = 2, 363 mplsTunnelHopAddrType = ipV4 (1), 364 mplsTunnelHopIpv4Addr = 123.123.126.1, 365 mplsTunnelHopIpv4PrefixLen = 9, 366 mplsTunnelHopType = loose (2), 367 } 368 Now an associated entry in the gmplsTunnelHopTable is created to 369 provide additional GMPLS hop configuration indicating that the first 370 hop is an unnumbered link using explicit forward and reverse labels. 372 In gmplsTunnelHopTable(1,1,1): 373 { 374 gmplsTunnelHopUnnumAddrType = unnumberedIpV4(2), 375 gmplsTunnelHopLabelStatuses = forwardPresent(0) 376 +reversePresent(1), 377 gmplsTunnelHopExplicitLabel = mplsLabelIndex.2756132, 378 gmplsTunnelHopExplicitReverseLabel = mplsLabelIndex.65236213 379 } 381 No gmplsTunnelHopEntry is created for the second hop as it contains 382 no special GMPLS features. 384 Finally the mplsTunnelEntry is activated: 386 In mplsTunnelTable(1,1,123.123.125.1,123.123.126.1) 387 { 388 mplsTunnelRowStatus = active(1) 389 } 391 8. GMPLS Traffic Engineering MIB Definitions 393 GMPLS-TE-STD-MIB DEFINITIONS ::= BEGIN 395 IMPORTS 396 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 397 experimental, Integer32, Unsigned32, Counter32, 398 Counter64, TimeTicks 399 FROM SNMPv2-SMI 400 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 401 FROM SNMPv2-CONF 402 TEXTUAL-CONVENTION, TruthValue, TimeStamp 403 FROM SNMPv2-TC 404 InetAddressIPv4, InetAddressIPv6 405 FROM INET-ADDRESS-MIB 406 ; 408 gmplsTeStdMIB MODULE-IDENTITY 409 LAST-UPDATED 410 "200308190900Z " -- 19 August 2003 9:00:00 GMT" 411 ORGANIZATION 412 "Common Control And Management Protocols (CCAMP) 413 Working Group" 414 CONTACT-INFO 415 " Thomas D. Nadeau 416 Cisco Systems, Inc. 417 Email: tnadeau@cisco.com 419 Cheenu Srinivasan 420 Bloomberg L.P. 421 Email: cheenu@bloomberg.net 422 Adrian Farrel 423 Old Dog Consulting 424 Email: adrian@olddog.co.uk 426 Ed Harrison 427 Data Connection Ltd. 428 Email: ed.harrison@dataconnection.com 430 Tim Hall 431 Data Connection Ltd. 432 Email: timhall@dataconnection.com 434 Comments about this document should be emailed direct to the 435 CCAMP working group mailing list at ccamp@ops.ietf.org" 436 DESCRIPTION 437 "This MIB module contains managed object definitions 438 for GMPLS Traffic Engineering (TE). 440 Copyright (C) The Internet Society (2003). This 441 version of this MIB module is part of RFCXXX; see 442 the RFC itself for full legal notices." 444 -- Revision history. 445 REVISION 446 "200308190900Z" -- 19 August 2003 09:00:00 GMT 447 DESCRIPTION 448 "Initial revision, published as part of RFC XXXX." 449 ::= { gmplsStdMIB xx } 451 -- Top level components of this MIB. 453 -- Notifications 454 -- no notifications are currently defined. 455 gmplsTeNotifications OBJECT IDENTIFIER ::= { gmplsTeStdMIB 0 } 457 -- tables, scalars 458 gmplsTeScalars OBJECT IDENTIFIER ::= { gmplsTeMIB 1 } 459 gmplsTeObjects OBJECT IDENTIFIER ::= { gmplsTeMIB 2 } 461 -- conformance 462 gmplsTeConformance OBJECT IDENTIFIER ::= { gmplsTeMIB 3 } 464 -- GMPLS Tunnel scalars. 466 gmplsTunnelsConfigured OBJECT-TYPE 467 SYNTAX Unsigned32 468 MAX-ACCESS read-only 469 STATUS current 470 DESCRIPTION 471 "The number of GMPLS tunnels configured on this 472 device. A GMPLS tunnel is considered configured if 473 an entry for the tunnel exists in the 474 gmplsTunnelTable and the associated 475 mplsTunnelRowStatusis active(1)." 476 ::= { gmplsTeScalars 1 } 477 gmplsTunnelActive OBJECT-TYPE 478 SYNTAX Unsigned32 479 MAX-ACCESS read-only 480 STATUS current 481 DESCRIPTION 482 "The number of GMPLS tunnels active on this device. 483 A GMPLS tunnel is considered active if there is an 484 entry in the gmplsTunnelTable and the associated 485 mplsTunnelOperStatus for the tunnel is up(1)." 486 ::= { gmplsTeScalars 2 } 488 -- End of GMPLS Tunnel scalars. 490 -- GMPLS tunnel table. 492 gmplsTunnelTable OBJECT-TYPE 493 SYNTAX SEQUENCE OF GmplsTunnelEntry 494 MAX-ACCESS not-accessible 495 STATUS current 496 DESCRIPTION 497 "The gmplsTunnelTable 'extends' the mplsTunnelTable. 498 It allows GMPLS tunnels to be created between an LSR 499 and a remote endpoint, and existing tunnels to be 500 reconfigured or removed. 501 Note that only point-to-point tunnel segments are 502 supported, although multi-point-to-point and point- 503 to-multi-point connections are supported by an LSR 504 acting as a cross-connect. Each tunnel can thus have 505 one out-segment originating at this LSR and/or one 506 in-segment terminating at this LSR." 507 ::= { gmplsTeObjects 1 } 509 gmplsTunnelEntry OBJECT-TYPE 510 SYNTAX GmplsTunnelEntry 511 MAX-ACCESS not-accessible 512 STATUS current 513 DESCRIPTION 514 "An entry in this table in association with the 515 corresponding entry in the mplsTunnelTable 516 represents a GMPLS tunnel. 517 An entry can be created by a network administrator 518 or by an SNMP agent as instructed by a signaling 519 protocol." 520 INDEX { 521 mplsTunnelIndex, 522 mplsTunnelInstance, 523 mplsTunnelIngressLSRId, 524 mplsTunnelEgressLSRId 525 } 526 ::= { gmplsTunnelTable 1 } 527 GmplsTunnelEntry ::= SEQUENCE { 528 gmplsTunnelUnnumIf TruthValue, 529 gmplsTunnelAttributes BITS, 530 gmplsTunnelLSPEncoding INTEGER, 531 gmplsTunnelSwitchingType INTEGER, 532 gmplsTunnelLinkProtection BITS, 533 gmplsTunnelGPid Unsigned32, 534 gmplsTunnelSecondary TruthValue, 535 gmplsTunnelDirection INTEGER, 536 gmplsTunnelPathComp INTEGER 537 } 539 gmplsTunnelUnnumIf OBJECT-TYPE 540 SYNTAX TruthValue 541 MAX-ACCESS read-create 542 STATUS current 543 DESCRIPTION 544 "Denotes whether or not this tunnel corresponds to an 545 unnumbered interface represented in the interfaces 546 group table. 547 This object is only used if mplsTunnelIsIf is set to 548 'true'. 549 If both this object and the mplsTunnelIsIf object 550 are set to 'true', the originating LSR adds an 551 LSP_TUNNEL_INTERFACE_ID object to the outgoing Path 552 message. 553 This object contains information that is only used 554 by the terminating LSR." 555 REFERENCE 556 "1. draft-ietf-mpls-crldp-unnum-06.txt - Signalling 557 Unnumbered Links in CR-LDP, Kompella, K., Rekhter, Y. 558 and Kullberg, A., June 2002. 559 2. Signalling Unnumbered Links in RSVP-TE, Kompella, K. 560 and Rekhter, Y., RFC 3477, January 2003." 561 DEFVAL { false } 562 ::= { gmplsTunnelEntry 1 } 564 gmplsTunnelAttributes OBJECT-TYPE 565 SYNTAX BITS { 566 labelRecordingDesired (0) 567 } 568 MAX-ACCESS read-create 569 STATUS current 570 DESCRIPTION 571 "This bitmask indicates optional parameters for this 572 tunnel. These bits should be taken in addition to 573 those defined in mplsTunnelSessionAttributes in 574 order to determine the full set of options to be 575 signaled (for example SESSION_ATTRIBUTES flags in 576 RSVP-TE). 577 The following describes these bitfields: 579 labelRecordingDesired 580 This flag indicates that label information should be 581 included when doing a route record. This bit is not 582 valid unless the recordRoute bit is set." 584 REFERENCE 585 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 586 Awduche et al, RFC 3209, December 2001." 587 DEFVAL { 0 } 588 ::= { gmplsTunnelEntry 2 } 590 gmplsTunnelLSPEncoding OBJECT-TYPE 591 SYNTAX INTEGER (0..255) 592 MAX-ACCESS read-create 593 STATUS current 594 DESCRIPTION 595 "This object indicates the encoding of the LSP being 596 requested. 597 A value of zero indicates that GMPLS signaling is 598 not in use. Some objects in this MIB module may be 599 of use for MPLS signaling extensions that do not use 600 GMPLS signaling. By setting this object to zero, an 601 application may indicate that only those objects 602 meaningful in MPLS should be examined. 603 The values to use are currently defined in 604 Generalized Multi-Protocol Label Switching (GMPLS) 605 Signaling Functional Description, RFC 3471. Further 606 values may be defined in future RFCs. 607 tunnelLspPacket (1), 608 tunnelLspEthernet (2), 609 tunnelLspAnsiEtsiPdh (3), 610 -- the value 4 is deprecated 611 tunnelLspSdhSonet (5), 612 -- the value 6 is deprecated 613 tunnelLspDigitalWrapper (7), 614 tunnelLspLambda (8), 615 tunnelLspFiber (9), 616 -- the value 10 is deprecated 617 tunnelLspFiberChannel (11)" 618 REFERENCE 619 "1. Berger, L., et al., Generalized Multi-Protocol 620 Label Switching (GMPLS) Signaling Functional 621 Description, RFC 3471, January 2003." 622 DEFVAL { 0 } 623 ::= { gmplsTunnelEntry 3 } 625 gmplsTunnelSwitchingType OBJECT-TYPE 626 SYNTAX INTEGER (0..255) 627 MAX-ACCESS read-create 628 STATUS current 629 DESCRIPTION 630 "Indicates the type of switching that should be 631 performed on a particular link. This field is needed 632 for links that advertise more than one type of 633 switching capability. Values of this object are as 634 the Switching Capability field defined in Internet 635 Draft OSPF Extensions in Support of Generalized 636 MPLS. 638 Further values may be defined in future RFCs. 639 unknown (0), 640 psc1 (1), 641 psc2 (2), 642 psc3 (3), 643 psc4 (4), 644 l2sc (51), 645 tdm (100), 646 lsc (150), 647 fsc (200) 649 This object is only meaningful if 650 gmplsTunnelLSPEncoding is not set to 0." 651 REFERENCE 652 "1. Kompella, K., et al., OSPF Extensions in Support 653 of Generalized MPLS, draft-ietf-ccamp-ospf-gmpls- 654 extensions-07.txt, May 2002, work in progress. 655 2. Berger, L., et al., Generalized Multi-Protocol 656 Label Switching (GMPLS) Signaling Functional 657 Description, RFC 3471, January 2003." 658 DEFVAL { unknown } 659 ::= { gmplsTunnelEntry 4 } 661 gmplsTunnelLinkProtection OBJECT-TYPE 662 SYNTAX BITS { 663 extraTraffic(1), 664 unprotected(2), 665 shared (3), 666 dedicatedOneToOne (4), 667 dedicatedOnePlusOne(5), 668 enhanced(6) 669 } 670 MAX-ACCESS read-create 671 STATUS current 672 DESCRIPTION 673 "This bitmask indicates the level of link protection 674 required. A value of zero (no bits set) indicates 675 that any protection may be used. 676 The following describes these bitfields: 678 extraTraffic 679 Indicates that the LSP should use links that are 680 protecting other (primary) traffic. Such LSPs may 681 be preempted when the links carrying the (primary) 682 traffic being protected fail. 684 unprotected 685 Indicates that the LSP should not use any link layer 686 protection. 688 shared 689 Indicates that a shared link layer protection 690 scheme, such as 1:N protection, should be used to 691 support the LSP. 693 dedicatedOneToOne 694 Indicates that a dedicated link layer protection 695 scheme, i.e., 1:1 protection, should be used to 696 support the LSP. 698 dedicatedOnePlusOne 699 Indicates that a dedicated link layer protection 700 scheme, i.e., 1+1 protection, should be used to 701 support the LSP. 703 enhanced 704 Indicates that a protection scheme that is more 705 reliable than Dedicated 1+1 should be used, e.g., 4 706 fiber BLSR/MS-SPRING. 708 This object is only meaningful if 709 gmplsTunnelLSPEncoding is not set to 0." 710 DEFVAL { 0 } 711 ::= { gmplsTunnelEntry 5 } 713 gmplsTunnelGPid OBJECT-TYPE 714 SYNTAX INTEGER (0..65535) 715 MAX-ACCESS read-create 716 STATUS current 717 DESCRIPTION 718 "This object indicates the payload carried by the 719 LSP. It is only required when GMPLS will be used for 720 this LSP. 722 The values to use are currently defined in 723 Generalized Multi-Protocol Label Switching (GMPLS) 724 Signaling Functional Description, RFC 3471. Further 725 values may be defined in future RFCs. 727 unknown(0), 728 asynchE4(5), 729 asynchDS3T3(6), 730 asynchE3(7), 731 bitsynchE3(8), 732 bytesynchE3(9), 733 asynchDS2T2(10), 734 bitsynchDS2T2(11), 735 asynchE1(13), 736 bytesynchE1(14), 737 bytesynch31ByDS0(15), 738 asynchDS1T1(16), 739 bitsynchDS1T1(17), 740 bytesynchDS1T1(18), 741 VC11VC12(19), 742 ds1SFAsynch(22), 743 ds1ESFAsynch(23), 744 ds3M23Asynch(24), 745 ds3CBitParityAsynch(25), 746 vtLovc(26), 747 stsSpeHovc(27), 748 posNoScramble16BitCrc(28), 749 posNoScramble32BitCrc(29), 750 posScramble16BitCrc(30), 751 posScramble32BitCrc(31), 752 atm(32) 753 ethernet(33), 754 sdhSonet(34), 755 digitalwrapper(36), 756 lambda(37), 757 ansiEtsiPdh (38), 758 lapsSdh (40), 759 fddi (41), 760 dqdb (42), 761 fiberChannel3 (43), 762 hdlc (44), 763 ethernetV2DixOnly (45), 764 ethernet802dot3Only (46) 766 This object is only meaningful if 767 gmplsTunnelLSPEncoding is not set to 0." 768 REFERENCE 769 "1. Berger, L., et al., Generalized Multi-Protocol 770 Label Switching (GMPLS) Signaling Functional 771 Description, RFC 3471, January 2003." 772 DEFVAL { unknown } 773 ::= { gmplsTunnelEntry 6 } 775 gmplsTunnelSecondary OBJECT-TYPE 776 SYNTAX TruthValue 777 MAX-ACCESS read-create 778 STATUS current 779 DESCRIPTION 780 "Indicates that the requested LSP is a secondary LSP. 782 This object is only meaningful if 783 gmplsTunnelLSPEncoding is not set to 0." 784 DEFVAL { false } 785 ::= { gmplsTunnelEntry 7 } 787 gmplsTunnelDirection OBJECT-TYPE 788 SYNTAX INTEGER { 789 forward (0), 790 bidirectional (1) 791 } 792 MAX-ACCESS read-create 793 STATUS current 794 DESCRIPTION 795 "Whether this tunnel carries forward data (is 796 unidirectional) or is bidirectional. 797 Values of this object other than 'forward' are 798 meaningful only if gmplsTunnelLSPEncoding is not set 799 to 0." 800 DEFVAL { forward } 801 ::= { gmplsTunnelEntry 8 } 802 gmplsTunnelPathComp OBJECT-TYPE 803 SYNTAX INTEGER { 804 dynamicFull(1),-- CSPF fully computed 805 explicit(2),-- fully specified path 806 dynamicPartial(3) -- CSPF partially computed 807 } 808 MAX-ACCESS read-create 809 STATUS current 810 DESCRIPTION 811 "This value instructs the source node on how to 812 perform path computation on the explicit route 813 specified by the associated entries in the 814 gmplsTunnelHopTable. 816 dynamicFull 817 The user specifies at least the source and 818 destination of the path and expects that the CSPF 819 will calculate the remainder of the path. 821 explicit 822 The user specifies the entire path for the tunnel to 823 take. This path may contain strict or loose hops. 824 Evaluation of the explicit route will be performed 825 hop by hop through the network. 827 dynamicPartial 828 The user specifies at least the source and 829 destination of the path and expects that the CSPF 830 will calculate the remainder of the path. The path 831 computed by CSPF is allowed to be only partially 832 computed allowing the remainder of the path to be 833 filled in across the network. 835 This object deprecates gmplsTunnelHopEntryPathComp." 836 DEFVAL { dynamicFull } 837 ::= { gmplsTunnelEntry 9 } 839 -- End of gmplsTunnelTable 841 -- Begin gmplsTunnelHopTable 843 gmplsTunnelHopTable OBJECT-TYPE 844 SYNTAX SEQUENCE OF GmplsTunnelHopEntry 845 MAX-ACCESS not-accessible 846 STATUS current 847 DESCRIPTION 848 "The gmplsTunnelHopTable 'extends' the 849 mplsTunnelHopTable. It is used to indicate the 850 explicit labels to be used in an explicit path for a 851 GMPLS tunnel defined in mplsTunnelTable and 852 gmplsTunnelTable, when it is established using 853 signaling. It does not insert new hops, but does 854 define new values for hops defined in 855 mplsTunnelHopTable. 857 Each row in this table is indexed by the same 858 indexes as mplsTunnelHopTable. It is acceptable for 859 some rows in mplsTunnelHopTable to have 860 corresponding entries in this table and some to have 861 no corresponding entry in this table. 863 The storage type for an entry in this table is 864 inherited from mplsTunnelHopStorageType in the 865 corresponding entry in mplsTunnelHopTable. 867 The row status of an entry in this table is 868 controlled by mplsTunnelHopRowStatus in the 869 corresponding entry in mplsTunnelHopTable. That is, 870 it is not permitted to create a row in this table, 871 nor to modify an existing row, when the 872 corresponding mplsTunnelHopRowStatus has value 873 active(1)." 874 ::= { gmplsTeObjects 2 } 876 gmplsTunnelHopEntry OBJECT-TYPE 877 SYNTAX GmplsTunnelHopEntry 878 MAX-ACCESS not-accessible 879 STATUS current 880 DESCRIPTION 881 "An entry in this table represents additions to a 882 tunnel hop defined in mplsTunnelHopEntry. At an 883 ingress to a tunnel an entry in this table is 884 created by a network administrator for an ERLSP to 885 be set up by a signaling protocol. At transit and 886 egress nodes an entry in this table may be used to 887 represent the explicit path instructions received 888 using the signaling protocol." 889 INDEX { 890 mplsTunnelHopListIndex, 891 mplsTunnelHopPathOptionIndex, 892 mplsTunnelHopIndex 893 } 894 ::= { gmplsTunnelHopTable 1 } 896 GmplsTunnelHopEntry ::= SEQUENCE { 897 gmplsTunnelHopLabelStatuses BITS, 898 gmplsTunnelHopExplicitLabel Unsigned32, 899 gmplsTunnelHopExplicitReverseLabel Unsigned32, 900 } 902 gmplsTunnelHopLabelStatuses OBJECT-TYPE 903 SYNTAX BITS { 904 forwardPresent (0), 905 reversePresent (1) 906 } 907 MAX-ACCESS read-only 908 STATUS current 909 DESCRIPTION 910 "This bitmask indicates the presence of labels 911 indicated by the gmplsTunnelHopExplicitLabel and 912 gmplsTunnelHopExplicitReverseLabel objects. 914 For the Present bits, a set bit indicates that a 915 label is present for this hop in the route. This 916 allows zero to be a valid label value." 917 ::= { gmplsTunnelHopEntry 1 } 919 gmplsTunnelHopExplicitLabel OBJECT-TYPE 920 SYNTAX Unsigned32 921 MAX-ACCESS read-create 922 STATUS current 923 DESCRIPTION 924 "Indicates the row entry in the gmplsLabelTable that 925 defines the explicit label to use in the explicit 926 route as the forward path label at this point. This 927 value only has meaning if the forwardPresent bit of 928 gmplsTunnelHopLabelStatuses is set. 929 Note that the other indexes in the gmplsLabelTable 930 should be interpreted as follows: 931 - The gmplsLabelInterface should be zero because 932 this label is not tied to any specific interface 933 on this LSR 934 - The gmplsLabelSubindex is used to represent label 935 concatenations. The first (or only) component 936 label SHOULD have gmplsLabelSubindex set to zero. 937 This variable is only valid for settings of 938 mplsTunnelHopAddrType which may be associated with a 939 forward path label. 940 Note that in implementations where the label may be 941 encoded within a 32 bit integer and where 942 gmplsLabelTable is not implemented, this object may 943 directly contain the label value to use." 944 ::= { gmplsTunnelHopEntry 2 } 946 gmplsTunnelHopExplicitReverseLabel OBJECT-TYPE 947 SYNTAX Unsigned32 948 MAX-ACCESS read-create 949 STATUS current 950 DESCRIPTION 951 "Indicates the row entry in the gmplsLabelTable that 952 defines the explicit label to use in the explicit 953 route as the reverse path label at this point. This 954 value only has meaning if the reversePresent bit of 955 gmplsTunnelHopLabelStatuses is set. 956 The same rules and notes apply as set out for 957 gmplsTunnelHopExplicitLabel." 958 ::= { gmplsTunnelHopEntry 3 } 960 -- End of gmplsTunnelHopTable 961 -- Tunnel Actual Route Hop table. 963 gmplsTunnelARHopTable OBJECT-TYPE 964 SYNTAX SEQUENCE OF GmplsTunnelARHopEntry 965 MAX-ACCESS not-accessible 966 STATUS current 967 DESCRIPTION 968 "The gmplsTunnelARHopTable 'extends' the 969 mplsTunnelARHopTable. It is used to indicate the 970 labels currently in use for a GMPLS tunnel defined 971 in mplsTunnelTable and gmplsTunnelTable, as reported 972 by the signaling protocol. It does not insert new 973 hops, but does define new values for hops defined in 974 mplsTunnelARHopTable. 976 Each row in this table is indexed by the same 977 indexes as mplsTunnelARHopTable. It is acceptable 978 for some rows in mplsTunnelARHopTable to have 979 corresponding entries in this table and some to have 980 no corresponding entry in this table. 982 Note that since the information necessary to build 983 entries within this table is not provided by some 984 signaling protocols and might not be returned in all 985 cases of other signaling protocols, implementation 986 of this table and mplsTunnelARHopTable is optional. 987 Furthermore, since the information in this table is 988 actually provided by the signaling protocol after 989 the path has been set-up, the entries in this table 990 are provided only for observation, and hence, all 991 variables in this table are accessible exclusively 992 as read-only." 993 ::= { gmplsTeObjects 3 } 995 gmplsTunnelARHopEntry OBJECT-TYPE 996 SYNTAX MplsTunnelARHopEntry 997 MAX-ACCESS not-accessible 998 STATUS current 999 DESCRIPTION 1000 "An entry in this table represents additions to a 1001 tunnel hop visible in mplsTunnelARHopEntry. An entry 1002 is created by the signaling protocol for a signaled 1003 ERLSP set up by the signaling protocol. 1005 At any node on the LSP (ingress, transit or egress) 1006 Thus at this table and mplsTunnelARHopTable (if the 1007 tables are supported and if the signaling protocol 1008 is recording actual route information) contains the 1009 actual route of the whole tunnel. If the signaling 1010 protocol is not recording the actual route, this 1011 table MAY report the information from the 1012 gmplsTunnelHopTable or the gmplsTunnelCHopTable. 1014 Note that the recording of actual labels is distinct 1015 from the recording of the actual route in some 1016 signaling protocols. This feature is enabled using 1017 the gmplsTunnelAttributes object." 1019 INDEX { 1020 mplsTunnelARHopListIndex, 1021 mplsTunnelARHopIndex 1022 } 1023 ::= { gmplsTunnelARHopTable 1 } 1025 GmplsTunnelARHopEntry ::= SEQUENCE { 1026 gmplsTunnelARHopLabelStatuses BITS, 1027 gmplsTunnelARHopExplicitLabel Unsigned32, 1028 gmplsTunnelARHopExplicitReverseLabel Unsigned32, 1029 gmplsTunnelARHopProtection BITS 1030 } 1032 gmplsTunnelARHopLabelStatuses OBJECT-TYPE 1033 SYNTAX BITS { 1034 forwardPresent (0), 1035 reversePresent (1), 1036 forwardGlobal (2), 1037 reverseGlobal (3) 1038 } 1039 MAX-ACCESS read-only 1040 STATUS current 1041 DESCRIPTION 1042 "This bitmask indicates the presence and status of 1043 labels indicated by the 1044 gmplsTunnelARHopExplicitLabel and 1045 gmplsTunnelARHopExplicitReverseLabel objects. 1046 For the Present bits, a set bit indicates that a 1047 label is present for this hop in the route. 1048 For the Global bits, a set bit indicates that the 1049 label comes from the Global Label Space. A clear bit 1050 indicates that this is a Per-Interface label. A 1051 Global bit only has meaning if the corresponding 1052 Present bit is set." 1053 ::= { gmplsTunnelARHopEntry 1 } 1055 gmplsTunnelARHopExplicitLabel OBJECT-TYPE 1056 SYNTAX Unsigned32 1057 MAX-ACCESS read-only 1058 STATUS current 1059 DESCRIPTION 1060 "Indicates the row entry in the gmplsLabelTable that 1061 defines the label in use as the forward path label 1062 on the path at this point. 1063 This value only has meaning if the forwardPresent 1064 bit of gmplsTunnelARHopLabelStatuses is set. 1066 Note that the other indexes in the gmplsLabelTable 1067 should be interpreted as follows: 1068 - The gmplsLabelInterface should be zero because 1069 this label is not tied to any specific interface 1070 on this LSR 1071 - The gmplsLabelSubindex is used to represent label 1072 concatenations. The first (or only) component 1073 label SHOULD have gmplsLabelSubindex set to zero. 1075 This variable is only valid for settings of 1076 mplsTunnelARHopAddrType which may be associated with 1077 a forward path label. 1079 Note that in implementations where the label may be 1080 encoded within a 32 bit integer and where 1081 gmplsLabelTable is not implemented, this object may 1082 directly contain the label value to use." 1083 ::= { gmplsTunnelARHopEntry 2 } 1085 gmplsTunnelARHopExplicitReverseLabel OBJECT-TYPE 1086 SYNTAX Unsigned32 1087 MAX-ACCESS read-only 1088 STATUS current 1089 DESCRIPTION 1090 "Indicates the row entry in the gmplsLabelTable that 1091 defines the label used in the path as reverse path 1092 at this point. 1093 This value only has meaning if the reversePresent 1094 bit of gmplsTunnelARHopLabelStatuses is set. 1095 The same rules and notes apply as set out for 1096 gmplsTunnelARHopExplicitLabel." 1097 ::= { gmplsTunnelARHopEntry 3 } 1099 gmplsTunnelARHopProtection OBJECT-TYPE 1100 SYNTAX BITS { 1101 localAvailable (0), 1102 localInUse (1) 1103 } 1104 MAX-ACCESS read-only 1105 STATUS current 1106 DESCRIPTION 1107 "Availability and usage of protection on the reported 1108 link. 1110 localAvailable 1111 Indicates that the link downstream of this node 1112 is protected via a local repair mechanism. 1113 localInUse 1114 Indicates that a local repair mechanism is in 1115 use to maintain this tunnel (usually in the 1116 face of an outage of the link it was previously 1117 routed over)." 1118 ::= { gmplsTunnelARHopEntry 4 } 1120 -- End of mplsTunnelARHopTable 1121 -- Tunnel Computed Hop table. 1123 gmplsTunnelCHopTable OBJECT-TYPE 1124 SYNTAX SEQUENCE OF GmplsTunnelCHopEntry 1125 MAX-ACCESS not-accessible 1126 STATUS current 1127 DESCRIPTION 1128 "The gmplsTunnelCHopTable 'extends' the 1129 mplsTunnelCHopTable. It is used to indicate 1130 additional information about the hops of a GMPLS 1131 tunnel defined in mplsTunnelTable and 1132 gmplsTunnelTable, as computed by a constraint-based 1133 routing protocol, based on the mplsTunnelHopTable 1134 and the gmplsTunnelHopTable. 1136 Each row in this table is indexed by the same 1137 indexes as mplsTunnelCHopTable. It is acceptable for 1138 some rows in mplsTunnelCHopTable to have 1139 corresponding entries in this table and some to have 1140 no corresponding entry in this table. 1142 Please note that since the information necessary to 1143 build entries within this table may not be supported 1144 by some LSRs, implementation of this table is 1145 optional. 1147 Furthermore, since the information in this table is 1148 actually provided by a path computation component 1149 after the path has been computed, the entries in 1150 this table are provided only for observation, and 1151 hence, all objects in this table are accessible 1152 exclusively as read-only." 1153 ::= { gmplsTeObjects 4 } 1155 gmplsTunnelCHopEntry OBJECT-TYPE 1156 SYNTAX GmplsTunnelCHopEntry 1157 MAX-ACCESS not-accessible 1158 STATUS current 1159 DESCRIPTION 1160 "An entry in this table represents additions to a 1161 computed tunnel hop visible in mplsTunnelCHopEntry. 1162 An entry is created by a path computation component 1163 based on the hops specified in the corresponding 1164 mplsTunnelHopTable and gmplsTunnelHopTable. 1166 At a transit LSR this table (if the table is 1167 supported) MAY contain the path computed by path 1168 computation engine on (or on behalf of) the transit 1169 LSR." 1170 INDEX { 1171 mplsTunnelCHopListIndex, 1172 mplsTunnelCHopIndex 1173 } 1174 ::= { gmplsTunnelCHopTable 1 } 1175 GmplsTunnelCHopEntry ::= SEQUENCE { 1176 gmplsTunnelCHopLabelStatuses BITS, 1177 gmplsTunnelCHopExplicitLabel Unsigned32, 1178 gmplsTunnelCHopExplicitReverseLabel Unsigned32, 1179 } 1181 gmplsTunnelCHopLabelStatuses OBJECT-TYPE 1182 SYNTAX BITS { 1183 forwardPresent (0), 1184 reversePresent (1) 1185 } 1186 MAX-ACCESS read-only 1187 STATUS current 1188 DESCRIPTION 1189 "This bitmask indicates the presence indicated by the 1190 gmplsTunnelCHopExplicitLabel and 1191 gmplsTunnelCHopExplicitReverseLabel objects. 1192 A set bit indicates that a label is present for this 1193 hop in the route thus allowing zero to be a valid 1194 label value." 1195 ::= { gmplsTunnelCHopEntry 1 } 1197 gmplsTunnelCHopExplicitLabel OBJECT-TYPE 1198 SYNTAX Unsigned32 1199 MAX-ACCESS read-only 1200 STATUS current 1201 DESCRIPTION 1202 "Indicates the row entry in the gmplsLabelTable that 1203 defines the label to use as the forward path label 1204 on the path at this point. 1205 This value only has meaning if the forwardPresent 1206 bit of gmplsTunnelCHopLabelStatuses is set. 1208 Note that the other indexes in the gmplsLabelTable 1209 should be interpreted as follows: 1210 - The gmplsLabelInterface should be zero because 1211 this label is not tied to any specific interface 1212 on this LSR 1213 - The gmplsLabelSubindex is used to represent label 1214 concatenations. The first (or only) component 1215 label SHOULD have gmplsLabelSubindex set to zero. 1216 This variable is only valid for settings of 1217 mplsTunnelCHopAddrType which may be associated with 1218 a forward path label. 1220 Note that in implementations where the label may be 1221 encoded within a 32 bit integer and where 1222 gmplsLabelTable is not implemented, this object may 1223 directly contain the label value to use." 1224 ::= { gmplsTunnelCHopEntry 2 } 1225 gmplsTunnelCHopExplicitReverseLabel OBJECT-TYPE 1226 SYNTAX Unsigned32 1227 MAX-ACCESS read-only 1228 STATUS current 1229 DESCRIPTION 1230 "Indicates the row entry in the gmplsLabelTable that 1231 defines the label to use in the path as reverse path 1232 at this point. 1233 This value only has meaning if the reversePresent 1234 bit of gmplsTunnelCHopLabelStatuses is set. 1235 The same rules and notes apply as set out for 1236 gmplsTunnelCHopExplicitLabel." 1237 ::= { gmplsTunnelCHopEntry 3 } 1239 -- End of gmplsTunnelCHopTable 1241 -- GMPLS Tunnel Reverse Direction Performance Table. 1243 gmplsTunnelReversePerfTable OBJECT-TYPE 1244 SYNTAX SEQUENCE OF GmplsTunnelReversePerfEntry 1245 MAX-ACCESS not-accessible 1246 STATUS current 1247 DESCRIPTION 1248 "This table 'augments' the gmplsTunnelTable to 1249 provides per-tunnel packet performance information 1250 for the reverse direction of a bidirectional tunnel. 1251 It can be seen as supplementing the 1252 mplsTunnelPerfTable which augments the 1253 mplsTunnelTable." 1254 ::= { gmplsTeObjects 5 } 1256 gmplsTunnelReversePerfEntry OBJECT-TYPE 1257 SYNTAX GmplsTunnelReversePerfEntry 1258 MAX-ACCESS not-accessible 1259 STATUS current 1260 DESCRIPTION 1261 "An entry in this table is created by the LSR for 1262 every bidirectional GMPLS tunnel where packets are 1263 visible to the LSR." 1264 AUGMENTS { gmplsTunnelEntry } 1265 ::= { gmplsTunnelReversePerfTable 1 } 1267 GmplsTunnelReversePerfEntry ::= SEQUENCE { 1268 gmplsTunnelReversePerfPackets Counter32, 1269 gmplsTunnelReversePerfHCPackets Counter64, 1270 gmplsTunnelReversePerfErrors Counter32, 1271 gmplsTunnelReversePerfBytes Counter32, 1272 gmplsTunnelReversePerfHCBytes Counter64 1273 } 1274 gmplsTunnelReversePerfPackets OBJECT-TYPE 1275 SYNTAX Counter32 1276 MAX-ACCESS read-only 1277 STATUS current 1278 DESCRIPTION 1279 "Number of packets forwarded on the tunnel in the 1280 reverse direction if it is bidirectional." 1281 ::= { gmplsTunnelReversePerfEntry 1 } 1283 gmplsTunnelReversePerfHCPackets OBJECT-TYPE 1284 SYNTAX Counter64 1285 MAX-ACCESS read-only 1286 STATUS current 1287 DESCRIPTION 1288 "High capacity counter for number of packets 1289 forwarded on the tunnel in the reverse direction if 1290 it is bidirectional." 1291 ::= { gmplsTunnelReversePerfEntry 2 } 1293 gmplsTunnelReversePerfErrors OBJECT-TYPE 1294 SYNTAX Counter32 1295 MAX-ACCESS read-only 1296 STATUS current 1297 DESCRIPTION 1298 "Number of errored packets received on the tunnel in 1299 the reverse direction if it is bidirectional." 1300 ::= { gmplsTunnelReversePerfEntry 3 } 1302 gmplsTunnelReversePerfBytes OBJECT-TYPE 1303 SYNTAX Counter32 1304 MAX-ACCESS read-only 1305 STATUS current 1306 DESCRIPTION 1307 "Number of bytes forwarded on the tunnel in the 1308 reverse direction if it is bidirectional." 1309 ::= { gmplsTunnelReversePerfEntry 4 } 1311 gmplsTunnelReversePerfHCBytes OBJECT-TYPE 1312 SYNTAX Counter64 1313 MAX-ACCESS read-only 1314 STATUS current 1315 DESCRIPTION 1316 "High capacity counter for number of bytes forwarded 1317 on the tunnel in the reverse direction if it is 1318 bidirectional." 1319 ::= { gmplsTunnelReversePerfEntry 5 } 1321 -- End of gmplsTunnelReversePerfTable 1322 -- GMPLS Tunnel Error Table. 1324 gmplsTunnelErrorTable OBJECT-TYPE 1325 SYNTAX SEQUENCE OF GmplsTunnelErrorEntry 1326 MAX-ACCESS not-accessible 1327 STATUS current 1328 DESCRIPTION 1329 "This table 'augments' the mplsTunnelTable 1331 This table provides per-tunnel information about 1332 errors. Errors may be detected locally or reported 1333 through the signaling protocol. 1335 Error reporting is not exclusive to GMPLS and this 1336 table may be applied in MPLS systems." 1337 ::= { gmplsTeObjects 6 } 1339 gmplsTunnelErrorEntry OBJECT-TYPE 1340 SYNTAX GmplsTunnelErrorEntry 1341 MAX-ACCESS not-accessible 1342 STATUS current 1343 DESCRIPTION 1344 "An entry in this table is created by the LSR for 1345 every tunnel where error information is visible to 1346 the LSR." 1347 AUGMENTS { mplsTunnelEntry } 1348 ::= { gmplsTunnelErrorTable 1 } 1350 GmplsTunnelErrorEntry ::= SEQUENCE { 1351 gmplsTunnelErrorLastErrorType INTEGER, 1352 gmplsTunnelErrorLastTime TimeStamp, 1353 gmplsTunnelErrorReporterType INTEGER, 1354 gmplsTunnelErrorReporterIpv4Addr InetAddressIPv4, 1355 gmplsTunnelErrorReporterIpv6Addr InetAddressIPv6, 1356 gmplsTunnelErrorCode Unsigned32, 1357 gmplsTunnelErrorSubcode Unsigned32, 1358 gmplsTunnelErrorHelpString DisplayString 1359 } 1361 gmplsTunnelErrorLastErrorType OBJECT-TYPE 1362 SYNTAX INTEGER { 1363 noError (0), 1364 unknown (1), 1365 localProtocol (2), 1366 remoteProtocol (3), 1367 configuration (4), 1368 pathComputation (5), 1369 localResources (6) 1370 } 1371 MAX-ACCESS read-only 1372 STATUS current 1373 DESCRIPTION 1374 "The nature of the last error. Provides 1375 interpretation context for 1376 gmplsTunnelErrorProtocolCode and 1377 gmplsTunnelErrorProtocolSubcode. A value of noError 1378 (0) shows that there is no error associated with 1379 this tunnel and means that the other objects in this 1380 entry have no meaning." 1381 ::= { gmplsTunnelErrorEntry 1 } 1383 gmplsTunnelErrorLastTime OBJECT-TYPE 1384 SYNTAX TimeStamp 1385 MAX-ACCESS read-only 1386 STATUS current 1387 DESCRIPTION 1388 "The time at which the last error occurred. This is 1389 presented as the value of SysUpTime when the error 1390 occurred or was reported to this node. 1391 If gmplsTunnelErrorLastErrorType has the value 1392 noError (0), then this object is ignored." 1393 ::= { gmplsTunnelErrorEntry 2 } 1395 gmplsTunnelErrorReporterType OBJECT-TYPE 1396 SYNTAX INTEGER { 1397 unknown (0), 1398 localNode (1), 1399 localIpV4 (2), 1400 remoteIpV4 (3), 1401 localIpV6 (4), 1402 remoteIpV6 (5) 1403 } 1404 MAX-ACCESS read-only 1405 STATUS current 1406 DESCRIPTION 1407 "The reporter of the last error recorded. 1408 This object is used principally to aid in 1409 interpretation of gmplsTunnelErrorReporterIpv4Addr 1410 and gmplsTunnelErrorReporterIpv6Addr. Where the 1411 error has been locally generated and there is no 1412 requirement to associate the error with any specific 1413 local address (such as an interface), the value 1414 localNode (2) may be used. 1415 If gmplsTunnelErrorLastError has the value noError 1416 (0), then this object is ignored." 1417 ::= { gmplsTunnelErrorEntry 3 } 1419 gmplsTunnelErrorReporterIpv4Addr OBJECT-TYPE 1420 SYNTAX InetAddressIPv4 1421 MAX-ACCESS read-only 1422 STATUS current 1423 DESCRIPTION 1424 "The address of the node reporting the last error, or 1425 the address of the resource (such as an interface) 1426 associated with the error. 1427 If gmplsTunnelErrorLastErrorType has the value 1428 noError (0), then this object is ignored. 1429 This object only has meaning if the object 1430 gmplsTunnelErrorReporterType has value localIpV4 (2) 1431 or remoteIpV4 (3). Otherwise the object should 1432 contain the value zero and should be ignored." 1433 ::= { gmplsTunnelErrorEntry 4 } 1434 gmplsTunnelErrorReporterIpv6Addr OBJECT-TYPE 1435 SYNTAX InetAddressIPv6, 1436 MAX-ACCESS read-only 1437 STATUS current 1438 DESCRIPTION 1439 "The address of the node reporting the last error, or 1440 the address of the resource (such as an interface) 1441 associated with the error. 1442 If gmplsTunnelErrorLastErrorType has the value 1443 noError (0), then this object is ignored. 1444 This object only has meaning if the object 1445 gmplsTunnelErrorReporterType has value localIpV6 (4) 1446 or remoteIpV4 (5). Otherwise the object should 1447 contain the value zero and should be ignored." 1448 ::= { gmplsTunnelErrorEntry 5 } 1450 gmplsTunnelErrorCode OBJECT-TYPE 1451 SYNTAX Unsigned32 1452 MAX-ACCESS read-only 1453 STATUS current 1454 DESCRIPTION 1455 "The primary error code associated with the last 1456 error. 1458 The interpretation of this error code depends on the 1459 value of gmplsTunnelErrorLastErrorType. If the value 1460 of gmplsTunnelErrorLastErrorType is noError (0) the 1461 value of this object should be 0 and should be 1462 ignored. If the value of 1463 gmplsTunnelErrorLastErrorType is localProtocol (2) 1464 or remoteProtocol (3) the error should be 1465 interpreted in the context of the signling protocol 1466 identified by the mplsTunnelSignallingProto object. 1468 Values in excess 32767 of are not used by signaling 1469 protocols and may safely be used as implementation- 1470 specific error codes. " 1471 ::= { gmplsTunnelErrorEntry 6 } 1473 gmplsTunnelErrorSubcode OBJECT-TYPE 1474 SYNTAX Unsigned32 1475 MAX-ACCESS read-only 1476 STATUS current 1477 DESCRIPTION 1478 "The secondary error code associated with the last 1479 error and the protocol used to signal this tunnel. 1480 This value is interprettd in the context of the 1481 value of gmplsTunnelErrorCode. 1482 If the value of gmplsTunnelErrorLastErrorType is 1483 noError (0) the value of this object should be 0 and 1484 should be ignored." 1485 ::= { gmplsTunnelErrorEntry 7 } 1486 gmplsTunnelErrorHelpString OBJECT-TYPE 1487 SYNTAX DisplayString 1488 MAX-ACCESS read-only 1489 STATUS current 1490 DESCRIPTION 1491 "A textual string containing information about the 1492 last error, recovery actions and support advice. If 1493 there is no help string this object contains a zero 1494 length string. 1495 If the value of gmplsTunnelErrorLastErrorType is 1496 noError (0) this object should contain a zero length 1497 string, but may contain a help string indicating 1498 that there is no error." 1499 ::= { gmplsTunnelErrorEntry 8 } 1501 -- Module compliance. 1503 gmplsTeGroups 1504 OBJECT IDENTIFIER ::= { gmplsTeConformance 1 } 1506 gmplsTeCompliances 1507 OBJECT IDENTIFIER ::= { gmplsTeConformance 2 } 1509 gmplsTeModuleCompliance MODULE-COMPLIANCE 1510 STATUS current 1511 DESCRIPTION 1512 "Compliance statement for agents that support the 1513 GMPLS TE MIB." 1514 MODULE -- this module 1516 -- The mandatory group has to be implemented by all 1517 -- LSRs that originate/terminate ESLSPs/tunnels. 1518 -- In addition, depending on the type of tunnels 1519 -- supported, other groups become mandatory as 1520 -- explained below. 1522 MANDATORY-GROUPS { 1523 gmplsTunnelGroup, 1524 gmplsTunnelScalarGroup 1525 } 1527 GROUP gmplsTunnelManualGroup 1528 DESCRIPTION 1529 "This group is mandatory for devices which support 1530 manual configuration of tunnels, in addition to 1531 gmplsTunnelGroup. The following constraints apply: 1533 gmplsTunnelSignallingProto should be at least read- 1534 only with a value of none(1)." 1536 GROUP gmplsTunnelSignaledGroup 1537 DESCRIPTION 1538 "This group is mandatory for devices which support 1539 signaled tunnel set up, in addition to 1540 gmplsTunnelGroup. The following constraints apply: 1542 gmplsTunnelSignallingProto should be at least read- 1543 only returning a value of ldp(2), or rsvp(3)." 1545 GROUP gmplsTunnelIsNotIntfcGroup 1546 DESCRIPTION 1547 "This group is mandatory for devices which support 1548 tunnels that are not interfaces, in addition to 1549 gmplsTunnelGroup. The following constraints apply: 1551 gmplsTunnelIsIf must at least be read-only returning 1552 no(0)." 1554 GROUP gmplsTunnelIsIntfcGroup 1555 DESCRIPTION 1556 "This group is mandatory for devices which support 1557 tunnels that are interfaces, in addition to 1558 gmplsTunnelGroup. The following constraints apply: 1560 gmplsTunnelIsUnnum must at least be read-only 1561 returning false." 1563 GROUP gmplsTunnelOptionalGroup 1564 DESCRIPTION 1565 "Objects in this group are optional." 1567 -- GMPLS Tunnel scalars. 1569 OBJECT gmplsTunnelsConfigured 1570 MIN-ACCESS read-only 1571 DESCRIPTION 1572 "Write access is not required." 1574 OBJECT gmplsTunnelActive 1575 MIN-ACCESS read-only 1576 DESCRIPTION 1577 "Write access is not required." 1579 -- gmplsTunnelTable 1581 OBJECT gmplsTunnelIsUnnum 1582 MIN-ACCESS read-only 1583 DESCRIPTION 1584 "Write access is not required." 1586 OBJECT gmplsTunnelAttributes 1587 MIN-ACCESS read-only 1588 DESCRIPTION 1589 "Write access is not required." 1591 OBJECT gmplsTunnelLSPEncoding 1592 SYNTAX INTEGER { 1593 tunnelLspNotGmpls (0), 1594 tunnelLspPacket (1), 1595 tunnelLspEthernetV2Dix (2), 1596 tunnelLspAnsiPdh (3), 1597 tunnelLspEtsiPdh (4), 1598 tunnelLspSdhItutG7071996 (5), 1599 tunnelLspSonetAnsiT11051995 (6), 1600 tunnelLspDigitalWrapper (7), 1601 tunnelLspLambda (8), 1602 tunnelLspFiber (9), 1603 tunnelLspEthernet8023 (10), 1604 tunnelLspSdhItutG7072000 (11), 1605 tunnelLspSonetAnsiT11052000 (12) 1606 } 1607 MIN-ACCESS read-only 1608 DESCRIPTION 1609 "Only tunnelLspNotGmpls (0) is required." 1611 OBJECT gmplsTunnelLinkProtection 1612 MIN-ACCESS read-only 1613 DESCRIPTION 1614 "Read-only support is required." 1616 OBJECT gmplsTunnelGPid 1617 MIN-ACCESS read-only 1618 DESCRIPTION 1619 "Read-only support is required." 1621 OBJECT gmplsTunnelSecondary 1622 SYNTAX TruthValue 1623 MIN-ACCESS read-only 1624 DESCRIPTION 1625 "Only false is required." 1627 OBJECT gmplsTunnelBiDirectional 1628 SYNTAX TruthValue 1629 MIN-ACCESS read-only 1630 DESCRIPTION 1631 "Only false is required." 1633 OBJECT gmplsTunnelPathComp 1634 SYNTAX INTEGER { 1635 dynamicFull(1), -- CSPF fully computed 1636 explicit(2), -- fully 1637 dynamicPartial(3) -- CSPF partially computed 1638 } 1639 MIN-ACCESS read-only 1640 DESCRIPTION 1641 "Only explicit (2) is required." 1643 -- gmplsTunnelHopTable 1645 OBJECT gmplsTunnelHopUnnumAddrType 1646 MIN-ACCESS read-only 1647 DESCRIPTION 1648 "Write access is not required." 1650 OBJECT gmplsTunnelHopLabelStatuses 1651 MIN-ACCESS read-only 1652 DESCRIPTION 1653 "Write access is not required." 1655 OBJECT gmplsTunnelHopExplicitLabel 1656 MIN-ACCESS read-only 1657 DESCRIPTION 1658 "Write access is not required." 1660 OBJECT gmplsTunnelHopExplicitReverseLabel 1661 MIN-ACCESS read-only 1662 DESCRIPTION 1663 "Write access is not required." 1665 OBJECT gmplsTunnelHopUnnumberedInterface 1666 MIN-ACCESS read-only 1667 DESCRIPTION 1668 "Write access is not required." 1670 -- gmplsTunnelARHopTable 1672 OBJECT gmplsTunnelARHopUnnumAddrType 1673 MIN-ACCESS read-only 1674 DESCRIPTION 1675 "Write access is not required." 1677 OBJECT gmplsTunnelARHopLabelStatuses 1678 MIN-ACCESS read-only 1679 DESCRIPTION 1680 "Write access is not required." 1682 OBJECT gmplsTunnelARHopExplicitLabel 1683 MIN-ACCESS read-only 1684 DESCRIPTION 1685 "Write access is not required." 1687 OBJECT gmplsTunnelARHopExplicitReverseLabel 1688 MIN-ACCESS read-only 1689 DESCRIPTION 1690 "Write access is not required." 1692 -- glmpsTunnelCHopTable 1694 OBJECT gmplsTunnelCHopUnnumAddrType 1695 MIN-ACCESS read-only 1696 DESCRIPTION 1697 "Write access is not required." 1699 OBJECT gmplsTunnelCHopLabelStatuses 1700 MIN-ACCESS read-only 1701 DESCRIPTION 1702 "Write access is not required." 1704 OBJECT gmplsTunnelCHopExplicitLabel 1705 MIN-ACCESS read-only 1706 DESCRIPTION 1707 "Write access is not required." 1709 OBJECT gmplsTunnelCHopExplicitReverseLabel 1710 MIN-ACCESS read-only 1711 DESCRIPTION 1712 "Write access is not required." 1714 OBJECT gmplsTunnelCHopUnnumberedInterface 1715 MIN-ACCESS read-only 1716 DESCRIPTION 1717 "Write access is not required." 1719 -- gmplsTunnelPerfTable 1721 OBJECT gmplsTunnelPacketPerfRvsPackets 1722 MIN-ACCESS read-only 1723 DESCRIPTION 1724 "Write access is not required." 1726 OBJECT gmplsTunnelPacketPerfRvsHCPackets 1727 MIN-ACCESS read-only 1728 DESCRIPTION 1729 "Write access is not required." 1731 OBJECT gmplsTunnelPacketPerfRvsErrors 1732 MIN-ACCESS read-only 1733 DESCRIPTION 1734 "Write access is not required." 1736 OBJECT gmplsTunnelPacketPerfRvsBytes 1737 MIN-ACCESS read-only 1738 DESCRIPTION 1739 "Write access is not required." 1741 OBJECT gmplsTunnelPacketPerfRvsHCBytes 1742 MIN-ACCESS read-only 1743 DESCRIPTION 1744 "Write access is not required." 1746 OBJECT gmplsTunnelErrorLastError 1747 MIN-ACCESS read-only 1748 DESCRIPTION 1749 "Write access is not required." 1751 OBJECT gmplsTunnelErrorLastTime 1752 MIN-ACCESS read-only 1753 DESCRIPTION 1754 "Write access is not required." 1756 OBJECT gmplsTunnelErrorReporterType 1757 MIN-ACCESS read-only 1758 DESCRIPTION 1759 "Write access is not required." 1761 OBJECT gmplsTunnelErrorReporterIpv4Addr 1762 MIN-ACCESS read-only 1763 DESCRIPTION 1764 "Write access is not required." 1766 OBJECT gmplsTunnelErrorReporterIpv6Addr 1767 MIN-ACCESS read-only 1768 DESCRIPTION 1769 "Write access is not required." 1771 OBJECT gmplsTunnelErrorProtocolCode 1772 MIN-ACCESS read-only 1773 DESCRIPTION 1774 "Write access is not required." 1776 OBJECT gmplsTunnelErrorProtocolSubcode 1777 MIN-ACCESS read-only 1778 DESCRIPTION 1779 "Write access is not required." 1781 OBJECT gmplsTunnelErrorHelpString 1782 MIN-ACCESS read-only 1783 DESCRIPTION 1784 "Write access is not required." 1786 ::= { gmplsTeCompliances 1 } 1788 -- Units of conformance. 1790 gmplsTunnelGroup OBJECT-GROUP 1791 OBJECTS { 1792 gmplsTunnelDirection, 1793 gmplsTunnelPacketPerfRvsPackets, 1794 gmplsTunnelPacketPerfRvsHCPackets, 1795 gmplsTunnelPacketPerfRvsErrors, 1796 gmplsTunnelPacketPerfRvsBytes, 1797 gmplsTunnelPacketPerfRvsHCBytes, 1798 gmplsTunnelErrorLastError, 1799 gmplsTunnelErrorLastTime, 1800 gmplsTunnelErrorReporterType, 1801 gmplsTunnelErrorReporterIpv4Addr, 1802 gmplsTunnelErrorReporterIpv6Addr, 1803 gmplsTunnelErrorProtocolCode, 1804 gmplsTunnelErrorProtocolSubcode, 1805 gmplsTunnelErrorHelpString 1806 } 1807 STATUS current 1808 DESCRIPTION 1809 "Necessary, but not sufficient, set of objects to 1810 implement tunnels. In addition, depending on the 1811 type of the tunnels supported (for example, manually 1812 configured or signaled, persistent or non- 1813 persistent, etc.), the following other groups 1814 defined below are mandatory: gmplsTunnelManualGroup 1815 and/or gmplsTunnelSignaledGroup, 1816 gmplsTunnelIsNotIntfcGroup and/or 1817 gmplsTunnelIsIntfcGroup." 1818 ::= { gmplsTeGroups 1 } 1820 gmplsTunnelManualGroup OBJECT-GROUP 1821 OBJECTS { 1822 gmplsTunnelSignallingProto 1823 } 1824 STATUS current 1825 DESCRIPTION 1826 "Object(s) needed to implement manually configured 1827 tunnels." 1828 ::= { gmplsTeGroups 2 } 1830 gmplsTunnelSignaledGroup OBJECT-GROUP 1831 OBJECTS { 1832 gmplsTunnelLSPEncoding, 1833 gmplsTunnelLinkProtection, 1834 gmplsTunnelGPid, 1835 gmplsTunnelSecondary, 1836 gmplsTunnelHopUnnumAddrType, 1837 gmplsTunnelHopLabelStatuses, 1838 gmplsTunnelHopExplicitLabel, 1839 gmplsTunnelHopExplicitReverseLabel, 1840 gmplsTunnelHopUnnumberedInterface 1841 } 1842 STATUS current 1843 DESCRIPTION 1844 "Objects needed to implement signaled tunnels." 1845 ::= { gmplsTeGroups 3 } 1847 gmplsTunnelScalarGroup OBJECT-GROUP 1848 OBJECTS { 1849 gmplsTunnelsConfigured, 1850 gmplsTunnelActive 1851 } 1852 STATUS current 1853 DESCRIPTION 1854 "Scalar objects needed to implement MPLS tunnels." 1855 ::= { gmplsTeGroups 4 } 1857 gmplsTunnelIsIntfcGroup OBJECT-GROUP 1858 OBJECTS { 1859 gmplsTunnelIsUnnum 1860 } 1861 STATUS current 1862 DESCRIPTION 1863 "Objects needed to implement tunnels that are 1864 interfaces." 1865 ::= { gmplsTeGroups 5 } 1866 gmplsTunnelIsNotIntfcGroup OBJECT-GROUP 1867 OBJECTS { 1868 gmplsTunnelIsUnnum 1869 } 1870 STATUS current 1871 DESCRIPTION 1872 "Objects needed to implement tunnels that are not 1873 interfaces." 1874 ::= { gmplsTeGroups 6 } 1876 gmplsTunnelOptionalGroup OBJECT-GROUP 1877 OBJECTS { 1878 gmplsTunnelARHopUnnumAddrType, 1879 gmplsTunnelARHopLabelStatuses, 1880 gmplsTunnelARHopExplicitLabel, 1881 gmplsTunnelARHopExplicitReverseLabel, 1882 gmplsTunnelCHopUnnumAddrType, 1883 gmplsTunnelCHopLabelStatuses, 1884 gmplsTunnelCHopExplicitLabel, 1885 gmplsTunnelCHopExplicitReverseLabel, 1886 gmplsTunnelCHopUnnumberedInterface 1887 } 1888 STATUS current 1889 DESCRIPTION 1890 "The objects in this group are optional." 1891 ::= { gmplsTeGroups 7 } 1893 END 1895 9. Security Considerations 1897 It is clear that the MIB modules described in this document in 1898 association with the MPLS-TE-STD-MIB are potentially useful for 1899 monitoring of MPLS and GMPLS tunnels. These MIB modules can also be 1900 used for configuration of certain objects, and anything that can be 1901 configured can be incorrectly configured, with potentially disastrous 1902 results. 1904 There are a number of management objects defined in these MIB modules 1905 with a MAX-ACCESS clause of read-write and/or read-create. Such 1906 objects may be considered sensitive or vulnerable in some network 1907 environments. The support for SET operations in a non-secure 1908 environment without proper protection can have a negative effect on 1909 network operations. These are the tables and objects and their 1910 sensitivity/vulnerability: 1912 o the gmplsTunnelTable and gmplsTunnelHopTable collectively contain 1913 objects to provision GMPLS tunnels interfaces at their ingress 1914 LSRs. Unauthorized write access to objects in these tables, could 1915 result in disruption of traffic on the network. This is especially 1916 true if a tunnel has already been established. The use of stronger 1917 mechanisms such as SNMPv3 security should be considered where 1918 possible. Specifically, SNMPv3 VACM and USM MUST be used with any 1919 SNMPv3 agent which implements these MIB modules. 1921 Some of the readable objects in these MIB modules "i.e., objects with 1922 a MAX-ACCESS other than not-accessible" may be considered sensitive 1923 or vulnerable in some network environments. It is thus important to 1924 control even GET and/or NOTIFY access to these objects and possibly 1925 to even encrypt the values of these objects when sending them over 1926 the network via SNMP. These are the tables and objects and their 1927 sensitivity/vulnerability: 1929 o the gmplsTunnelTable, gmplsTunnelHopTable, gmplsTunnelARHopTable, 1930 gmplsTunnelCHopTable, gmplsTunnelReversePerfTable, 1931 gmplsTunnelErrorTable collectively show the tunnel network 1932 topology and status. If an Administrator does not want to reveal 1933 this information, then these tables should be considered 1934 sensitive/vulnerable. 1936 SNMP versions prior to SNMPv3 did not include adequate security. Even 1937 if the network itself is secure "for example by using IPSec", even 1938 then, there is no control as to who on the secure network is allowed 1939 to access and GET/SET "read/change/create/delete" the objects in 1940 these MIB modules. It is RECOMMENDED that implementers consider the 1941 security features as provided by the SNMPv3 framework "see [RFC3410], 1942 section 8", including full support for the SNMPv3 cryptographic 1943 mechanisms "for authentication and privacy". 1945 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1946 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1947 enable cryptographic security. It is then a customer/operator 1948 responsibility to ensure that the SNMP entity giving access to an 1949 instance of this MIB module, is properly configured to give access to 1950 the objects only to those principals "users" that have legitimate 1951 rights to indeed GET or SET "change/create/delete" them. 1953 10. Acknowledgments 1955 This draft extends [TEMIB]. The authors would like to express their 1956 gratitude to all those who worked on that earlier MIB document. 1957 Thanks also to Tony Zinicola and Jeremy Crossen for their valuable 1958 contributions during an early implementation. 1960 11. References 1962 11.1. Normative References 1964 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1965 Requirement Levels", BCP 14, RFC 2119, March 1997. 1967 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., 1968 Case, J., Rose, M., and S. Waldbusser, "Structure 1969 of Management Information Version 2 (SMIv2)", STD 1970 58, RFC 2578, April 1999. 1972 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., 1973 Case, J., Rose, M., and S. Waldbusser, "Textual 1974 Conventions for SMIv2", STD 58, RFC 2579, April 1975 1999. 1977 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., 1978 Case, J., Rose, M., and S. Waldbusser, "Conformance 1979 Statements for SMIv2", STD 58, RFC 2580, April 1980 1999. 1982 [RFC2863] McCloghrie, K. and F. Kastenholtz, "The Interfaces 1983 Group MIB", RFC 2863, June 2000. 1985 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 1986 "Multiprotocol Label Switching Architecture", RFC 1987 3031, January 2001. 1989 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., 1990 Srinivasan, V., and G. Swallow, "RSVP-TE: 1991 Extensions to RSVP for LSP Tunnels", RFC 3209, 1992 December 2001. 1994 [RFC3212] Jamoussi, B., Aboul-Magd, O., Andersson, L., 1995 Ashwood-Smith, P., Hellstrand, F., Sundell, K., 1996 Callon, R., Dantu, R., Wu, L., Doolan, P., Worster, 1997 T., Feldman, N., Fredette, A., Girish, M., Gray, 1998 E., Halpern, J., Heinanen, J., Kilty, T., Malis, 1999 A., and P. Vaananen, "Constraint-Based LSP Setup 2000 using LDP", RFC 3212, December 2001." 2002 [RFC3471] Berger, L. (Editor), "Generalized Multi-Protocol 2003 Label Switching (GMPLS) Signaling Functional 2004 Description", RFC 3471, January 2003. 2006 [RFC3472] Ashwood-Smith, P., Berger, L. (Editors), 2007 "Generalized MPLS Signaling - CR-LDP Extensions", 2008 RFC 3472, January 2003. 2010 [RFC3473] Berger, L. (Editor), "Generalized MPLS Signaling - 2011 RSVP-TE Extensions", RFC 3473 January 2003. 2013 [GMPLSArch] Mannie, E. (Editor), "Generalized Multiprotocol 2014 Label Switching (GMPLS) Architecture", Internet 2015 Draft , May 2016 2003, work in progress. 2018 [GMPLSSonetSDH] Mannie, E., Papadimitriou, D. (Editors), 2019 "Generalized Multi-Protocol Label Switching 2020 Extensions for SONET and SDH Control", Internet 2021 Draft , 2022 February 2003, work in progress. 2024 [TCMIB] Nadeau, T., Cucchiara, J. (Editors) "Definitions of 2025 Textual Conventions for Multiprotocol Label 2026 Switching (MPLS) Management", Internet Draft 2027 , August 2003, work 2028 in progress. 2030 [TEMIB] Nadeau, T., Srinivasan, C, Viswanathan, A., 2031 "Multiprotocol Label Switching (MPLS) Traffic 2032 Engineering Management Information Base", Internet 2033 Draft , August 2003, 2034 work in progress. 2036 [LSRMIB] Srinivasan, C., Viswanathan, A. and T. Nadeau, 2037 "Multiprotocol Label Switching (MPLS) Label 2038 Switching Router (LSR) Management Information 2039 Base", Internet Draft , August 2003, work in progress. 2042 [GMPLSTCMIB] Nadeau, T., Srinivasan, C., Farrel, A., Hall, T., 2043 and Harrison, E., "Definitions of Textual 2044 Conventions for Multiprotocol Label Switching 2045 (MPLS) Management", draft-ietf-ccamp-gmpls-te-mib- 2046 01.txt, August 2003, work in progress. 2048 [GMPLSLSRMIB] Nadeau, T., Srinivasan, C., A., Farrel, A., Hall, 2049 T., and Harrison, E., "Generalized Multiprotocol 2050 Label Switching (GMPLS) Label Switching Router 2051 (LSR) Management Information Base", draft-ietf- 2052 ccamp-gmpls-lsr-mib-01.txt, August 2003, work in 2053 progress. 2055 [GMPLS-OSPF] Kompella, K., et al., "OSPF Extensions in Support 2056 of Generalized MPLS", draft-ietf-ccamp-ospf-gmpls- 2057 extensions-07.txt, May 2002, work in progress. 2059 11.2. Informational References 2061 [RFC2026] S. Bradner, "The Internet Standards Process -- 2062 Revision 3", RFC 2026, October 1996. 2064 [RFC3413] Levi, D., Meyer, P., Stewart, B., "SNMP 2065 Applications", RFC 3413, December 2002. 2067 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 2068 "Introduction and Applicability Statements for 2069 Internet-Standard Management Framework", RFC 3410, 2070 December 2002. 2072 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An 2073 Architecture for Describing Simple Network 2074 Management Protocol (SNMP) Management Frameworks", 2075 RFC 3411, December 2002. 2077 12. Authors' Addresses 2079 Thomas D. Nadeau 2080 Cisco Systems, Inc. 2081 300 Apollo Drive 2082 Chelmsford, MA 01824 2083 Phone: +1-978-244-3051 2084 Email: tnadeau@cisco.com 2085 Cheenu Srinivasan 2086 Bloomberg L.P. 2087 499 Park Ave., 2088 New York, NY 10022 2089 Phone: +1-212-893-3682 2090 Email: cheenu@bloomberg.net 2092 Adrian Farrel 2093 Old Dog Consulting 2094 Phone: +44-(0)-1978-860944 2095 Email: adrian@olddog.co.uk 2097 Tim Hall 2098 Data Connection Ltd. 2099 100 Church Street 2100 Enfield, Middlesex 2101 EN2 6BQ, UK 2102 Phone: +44 20 8366 1177 2103 Email: timhall@dataconnection.com 2105 Ed Harrison 2106 Data Connection Ltd. 2107 100 Church Street 2108 Enfield, Middlesex 2109 EN2 6BQ, UK 2110 Phone: +44 20 8366 1177 2111 Email: ed.harrison@dataconnection.com 2113 13. Full Copyright Statement 2115 Copyright (C) The Internet Society (2003). All Rights Reserved. 2116 This document and translations of it may be copied and furnished to 2117 others, and derivative works that comment on or otherwise explain it 2118 or assist in its implementation may be prepared, copied, published 2119 and distributed, in whole or in part, without restriction of any 2120 kind, provided that the above copyright notice and this paragraph are 2121 included on all such copies and derivative works. However, this 2122 document itself may not be modified in any way, such as by removing 2123 the copyright notice or references to the Internet Society or other 2124 Internet organizations, except as needed for the purpose of 2125 developing Internet standards in which case the procedures for 2126 copyrights defined in the Internet Standards process must be 2127 followed, or as required to translate it into languages other than 2128 English. 2130 The limited permissions granted above are perpetual and will not be 2131 revoked by the Internet Society or its successors or assigns. This 2132 document and the information contained herein is provided on an "AS 2133 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 2134 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 2135 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL 2136 NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY 2137 OR FITNESS FOR A PARTICULAR PURPOSE. 2139 14. Intellectual Property Notice 2141 The IETF takes no position regarding the validity or scope of any 2142 intellectual property or other rights that might be claimed to 2143 pertain to the implementation or use of the technology described in 2144 this document or the extent to which any license under such rights 2145 might or might not be available; neither does it represent that it 2146 has made any effort to identify any such rights. Information on the 2147 IETF's procedures with respect to rights in standards-track and 2148 standards-related documentation can be found in BCP-11 [RFC2028]. 2149 Copies of claims of rights made available for publication and any 2150 assurances of licenses to be made available, or the result of an 2151 attempt made to obtain a general license or permission for the use 2152 of such proprietary rights by implementers or users of this 2153 specification can be obtained from the IETF Secretariat. 2155 The IETF invites any interested party to bring to its attention any 2156 copyrights, patents or patent applications, or other proprietary 2157 rights that may cover technology that may be required to practice 2158 this standard. Please address the information to the IETF Executive 2159 Director. 2161 15. Changes and Pending Work 2163 This section to be removed before the draft progresses to RFC. 2165 15.1. Pending Work 2167 The following work items have been identified for this draft. They 2168 will be addressed in a future version. 2170 - Clarify which objects can be modified when rowStatus and 2171 adminStatus are set to active 2172 - Sort out conformance statement which is a mess 2173 - Expand conformance statements to give one for monitoring only, 2174 and one for monitoring and control. 2175 - Bring references up to date, include all drafts referenced from 2176 this document, and exclude those that are not referenced. 2177 - Consider a way to expose tunnel head, tunnel tail, and tunnel 2178 transit entries through distinct indexing or tables. 2179 - Provide support for configuring tunnel resources in GMPLS 2180 systems. For example, SONET/SDH or G.709. This might be done 2181 through an arbitrary RowPointer to an external MIB. 2182 - Link Ids in EROs and RROs for use of bundled links. 2183 - Crankback request and reported information. 2184 - Control and reporting of upstream and downstream Notify 2185 Recipients. 2186 - Add support for control and reporting of GMPLS Administrative 2187 Status object. 2188 - Add support for IF_ID control and error reporting. 2189 - Add support for selection and configuration of restart options. 2190 - Update enumerated types in line with latest GMPLS drafts. Examine 2191 how these can be managed by IANA. 2193 - Resolve ownership of enumerated types that are also defined in 2194 GMPLS or routing drafts. These could be owned by IANA, imported 2195 from another MIB, or manually kept in step here. If they are not 2196 maintained externally then they are likely to diverge and MIB 2197 implementations will need to provide mappings. 2198 - Update examples. 2199 - Update MIB description in section 5. 2200 - Update in-line references.