idnits 2.17.1 draft-ietf-mpls-te-mib-10.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 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 are 2 instances of lines with private range IPv4 addresses in the document. If these are generic example addresses, they should be changed to use any of the ranges defined in RFC 6890 (or successor): 192.0.2.x, 198.51.100.x or 203.0.113.x. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 676 has weird spacing: '... in mplsT...' == 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 (June 2003) is 7618 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: 'RSVPTE' is mentioned on line 196, but not defined == Missing Reference: 'TEMIB' is mentioned on line 516, but not defined == Unused Reference: 'RFC2702' is defined on line 3173, but no explicit reference was found in the text == Unused Reference: 'RFC3209' is defined on line 3185, but no explicit reference was found in the text == Unused Reference: 'RFC3291' is defined on line 3190, but no explicit reference was found in the text == Unused Reference: 'RFC3411' is defined on line 3195, but no explicit reference was found in the text == Unused Reference: 'TCMIB' is defined on line 3201, but no explicit reference was found in the text == Unused Reference: 'RFC1155' is defined on line 3218, but no explicit reference was found in the text == Unused Reference: 'RFC1157' is defined on line 3222, but no explicit reference was found in the text == Unused Reference: 'RFC1212' is defined on line 3226, but no explicit reference was found in the text == Unused Reference: 'RFC1215' is defined on line 3229, but no explicit reference was found in the text == Unused Reference: 'RFC1901' is defined on line 3233, but no explicit reference was found in the text == Unused Reference: 'RFC1905' is defined on line 3237, but no explicit reference was found in the text == Unused Reference: 'RFC1906' is defined on line 3242, but no explicit reference was found in the text == Unused Reference: 'RFC2026' is defined on line 3247, but no explicit reference was found in the text == Unused Reference: 'RFC2401' is defined on line 3250, but no explicit reference was found in the text == Unused Reference: 'RFC2572' is defined on line 3254, but no explicit reference was found in the text == Unused Reference: 'RFC2573' is defined on line 3259, but no explicit reference was found in the text == Unused Reference: 'RFC2574' is defined on line 3262, but no explicit reference was found in the text == Unused Reference: 'RFC2575' is defined on line 3267, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 2702 ** Obsolete normative reference: RFC 3291 (Obsoleted by RFC 4001) -- Possible downref: Non-RFC (?) normative reference: ref. 'TCMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'LSRMIB' -- Obsolete informational reference (is this intentional?): RFC 1905 (Obsoleted by RFC 3416) -- Obsolete informational reference (is this intentional?): RFC 1906 (Obsoleted by RFC 3417) -- Obsolete informational reference (is this intentional?): RFC 2401 (Obsoleted by RFC 4301) -- Obsolete informational reference (is this intentional?): RFC 2572 (Obsoleted by RFC 3412) -- Obsolete informational reference (is this intentional?): RFC 2573 (Obsoleted by RFC 3413) -- Obsolete informational reference (is this intentional?): RFC 2574 (Obsoleted by RFC 3414) -- Obsolete informational reference (is this intentional?): RFC 2575 (Obsoleted by RFC 3415) Summary: 4 errors (**), 0 flaws (~~), 24 warnings (==), 11 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Cheenu Srinivasan 3 Internet Draft 4 Expires: December 2003 Arun Viswanathan 5 Force10 Networks, Inc. 7 Thomas D. Nadeau 8 Cisco Systems, Inc. 10 June 2003 12 Multiprotocol Label Switching (MPLS) Traffic Engineering 13 Management Information Base 15 draft-ietf-mpls-te-mib-10.txt 17 Status of this Memo 19 This document is an Internet-Draft and is in full 20 conformance with all provisions of Section 10 of RFC 2026. 22 Internet-Drafts are working documents of the Internet 23 Engineering Task Force (IETF), its areas, and its working 24 groups. Note that other groups may also distribute working 25 documents as Internet-Drafts. 27 Internet-Drafts are draft documents valid for a maximum of 28 six months and may be updated, replaced, or obsoleted by 29 other documents at any time. It is inappropriate to use 30 Internet-Drafts as reference material or to cite them other 31 than as "work in progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/ietf/1id-abstracts.txt. 36 The list of Internet-Draft Shadow Directories can be 37 accessed at http://www.ietf.org/shadow.html. 39 Abstract 41 This memo defines a portion of the Management Information 42 Base (MIB) for use with network management protocols in 43 the Internet community. In particular, it describes 44 managed objects for Multiprotocol Label Switching (MPLS) 45 based traffic engineering. 47 Table of Contents 49 1. Introduction ........................................... 2 50 2. Terminology ............................................ 3 51 3. The Internet-Standard Management Framework ............. 3 52 4. Feature List ........................................... 3 53 5. Outline ................................................ 4 54 5.1. Summary of Traffic Engineering MIB module ............ 4 55 6. Brief Description of MIB Objects ....................... 5 56 6.1. mplsTunnelTable ...................................... 5 57 6.2. mplsTunnelResourceTable .............................. 5 58 6.3. mplsTunnelHopTable ................................... 5 59 6.4. mplsTunnelARHopTable ................................. 6 60 6.5. mplsTunnelCHoptable .................................. 6 61 6.6. mplsTunnelPerfTable .................................. 6 62 6.7. mplsTunnelCRLDPResTable .............................. 6 63 7. Use of 32-bit and 64-bit Counters ...................... 6 64 8. Application of the Interface Group to MPLS Tunnels ..... 7 65 8.1. Support of the MPLS Tunnel Interface by ifTable ...... 8 66 9. Example of Tunnel Setup ................................ 9 67 10. The Use of RowPointer ................................ 11 68 11. MPLS Traffic Engineering MIB Definitions ............. 12 69 12. Security Considerations .............................. 65 70 13. Acknowledgments ...................................... 67 71 14. References ........................................... 67 72 14.1. Normative References ............................... 67 73 14.2. Informative References ............................. 68 74 15. Authors' Addresses ................................... 70 75 16. Full Copyright Statement ............................. 70 76 17. Intellectual Property Notice ......................... 71 78 1. Introduction 80 This memo defines a portion of the Management Information 81 Base (MIB) for use with network management protocols in the 82 Internet community. In particular, it describes managed 83 objects for modeling a Multi-Protocol Label Switching 84 (MPLS) [RFC3031] based traffic engineering. This MIB module 85 should be used in conjunction with the companion document 86 [LSRMIB] for MPLS based traffic engineering configuration 87 and management. 89 Comments should be made directly to the MPLS mailing list 90 at mpls@uu.net. 92 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", 93 "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", 94 and "OPTIONAL" in this document are to be interpreted as 95 described in RFC 2119, reference [RFC2119]. 97 2. Terminology 99 This document uses terminology from the MPLS architecture 100 document [RFC3031] and MPLS Label Switch Router MIB 101 [LSRMIB]. Some frequently used terms are described next. 103 An explicitly routed LSP (ERLSP) is referred to as an MPLS 104 tunnel. It consists of one in-segment and/or one out- 105 segment at the ingress/egress LSRs, each segment being 106 associated with one MPLS interface. These are also 107 referred to as tunnel segments. Additionally, at an 108 intermediate LSR, we model a connection as consisting of 109 one or more in-segments and/or one or more out-segments. 110 The binding or interconnection between in-segments and out- 111 segments in performed using a cross-connect. These objects 112 are defined in the MPLS Label Switch Router MIB [LSRMIB]. 114 3. The Internet-Standard Management Framework 116 For a detailed overview of the documents that describe the 117 current Internet-Standard Management Framework, please 118 refer to section 7 of RFC 3410 [RFC3410]. 120 Managed objects are accessed via a virtual information 121 store, termed the Management Information Base or MIB. MIB 122 objects are generally accessed through the Simple Network 123 Management Protocol (SNMP). Objects in the MIB are defined 124 using the mechanisms defined in the Structure of Management 125 Information (SMI). This memo specifies a MIB module that 126 is compliant to the SMIv2, which is described in STD 58, 127 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, 128 RFC 2580 [RFC2580]. 130 4. Feature List 132 The MPLS traffic engineering MIB module is designed to 133 satisfy the following requirements and constraints. 135 - The MIB module supports configuration of point-to-point 136 unidirectional tunnels. 138 - MPLS tunnels need not be interfaces, but it is possible 139 to configure a tunnel as an interface. 141 - The MIB module supports tunnel establishment via an MPLS 142 signalling protocol wherein the tunnel parameters are 143 specified using this MIB module at the head end of the 144 LSP and end-to-end tunnel LSP establishment is 145 accomplished via signalling. The MIB module also 146 supports manually configured tunnels, i.e. those for 147 which label associations at each hop of the tunnel LSP 148 are provisioned by the administrator via the LSR MIB 149 [LSRMIB]. 151 - The MIB module supports persistent as well as non- 152 persistent tunnels. 154 5. Outline 156 Traffic engineering support for MPLS tunnels requires the 157 following configuration. 159 - Setting up MPLS tunnels along with appropriate 160 configuration parameters. 162 - Configuring tunnel loose and strict source routed hops. 164 These actions may need to be accompanied with corresponding 165 actions using [LSRMIB] to establish and configure tunnel 166 segments, if this is done manually. Also, the in-segment 167 and out-segment performance tables, mplsInSegmentPerfTable 168 and mplsOutSegmentPerfTable [LSRMIB], should be used to 169 determine performance of the tunnels and tunnel segments. 171 5.1. Summary of Traffic Engineering MIB module 173 The MIB module objects for performing these actions consist 174 of the following tables. 176 - Tunnel table (mplsTunnelTable) for setting up MPLS 177 tunnels. 179 - Resource table (mplsTunnelResourceTable) for setting up 180 the tunnel resources. 182 - Tunnel specified, actual, and computed hop tables 183 (mplsTunnelHopTable, mplsTunnelARHopTable, and 184 mplsTunnelCHopTable) for strict and loose source routed 185 MPLS tunnel hops. 187 - CRLDP resource table (mplsTunnelCRLDPResTable) for 188 specifying resource objects applicable to tunnels 189 signaled using CRLDP. 191 These tables are described in the subsequent sections. 193 6. Brief Description of MIB Objects 195 The objects described in this section support the 196 functionality described in documents [RSVPTE] and [CRLDP]. 197 The tables support both manually configured and signaled 198 tunnels. 200 6.1. mplsTunnelTable 202 The mplsTunnelTable allows new MPLS tunnels to be created 203 between an MPLS LSR and a remote endpoint, and existing 204 tunnels to be reconfigured or removed. Note that we only 205 support point-to-point tunnel segments, although multi- 206 point-to-point and point-to-multi-point connections are 207 supported by an LSR acting as a cross-connect. Each MPLS 208 tunnel can thus have one out-segment originating at an LSR 209 and/or one in-segment terminating at that LSR. 211 mplsTunnelTable does not define the in and out segments 212 forming the tunnel. Instead, these are defined by creating 213 rows in the in-segment and out-segment tables, defining 214 relationships in the cross-connect table and referring to 215 these rows in the mplsTunnelTable using a cross-connect 216 index, mplsTunnelXCIndex. These segment and cross-connect 217 related objects are defined in [LSRMIB]. 219 6.2. mplsTunnelResourceTable 221 mplsTunnelResourceTable is used to indicate the resources 222 required for a tunnel. Multiple tunnels may share the same 223 resources by pointing to the same entry in this table. 224 Tunnels that do not share resources must point to separate 225 entries in this table. 227 6.3. mplsTunnelHopTable 229 mplsTunnelHopTable is used to indicate the hops, strict or 230 loose, for an MPLS tunnel defined in mplsTunnelTable, when 231 it is established via signalling. Multiple tunnels may 232 share the same hops by pointing to the same entry in this 233 table. Each row also has a secondary index, 234 mplsTunnelHopIndex, corresponding to the next hop of this 235 tunnel. The scalar mplsTunnelMaxHops indicates the maximum 236 number of hops that can be specified on each tunnel 237 supported by this LSR. 239 6.4. mplsTunnelARHopTable 241 mplsTunnelARHopTable is used to indicate the actual hops 242 traversed by a tunnel as reported by the MPLS signalling 243 protocol after the tunnel is setup. The support of this 244 table is optional since not all MPLS signalling protocol 245 may support this feature. 247 6.5. mplsTunnelCHoptable 249 mplsTunnelCHopTable lists the actual hops computed by a 250 constraint-based routing algorithm based on the 251 mplsTunnelHopTable. The support of this table is optional 252 since not all implementations may support computation of 253 hop list using a constraint-based routing protocol. 255 6.6. mplsTunnelPerfTable 257 mplsTunnelPerfTable provides several counters to measure 258 the performance of the MPLS tunnels. This table augments 259 mplsTunnelTable. 261 6.7. mplsTunnelCRLDPResTable 263 mplsTunnelCRLDPResTable contains resource information for 264 those tunnels that are signaled using CRLDP [CRLDP]. This 265 is a sparse extension to mplsTunnelResourceTable and is 266 also indexed by mplsTunnelResourceIndex. As with 267 mplsTunnelResourceTable, multiple tunnels may share the 268 same resources by pointing to the same entry in this table. 269 Tunnels that do not share resources must point to separate 270 entries in this table. 272 7. Use of 32-bit and 64-bit Counters 274 64-bit counters are provided in this MIB module for high- 275 speed interfaces where the use of 32-bit counters might be 276 impractical. The requirements on the use of 32-bit and 64- 277 bit counters (copied verbatim from [RFC2863]) are as 278 follows. 280 For interfaces that operate at 20,000,000 (20 million) bits 281 per second or less, 32-bit byte and packet counters MUST be 282 supported. For interfaces that operate faster than 283 20,000,000 bits/second, and slower than 650,000,000 284 bits/second, 32-bit packet counters MUST be supported and 285 64-bit octet counters MUST be supported. For interfaces 286 that operate at 650,000,000 bits/second or faster, 64-bit 287 packet counters AND 64-bit octet counters MUST be 288 supported. 290 8. Application of the Interface Group to MPLS Tunnels 292 The Interfaces Group of MIB II defines generic managed 293 objects for managing interfaces. This memo contains the 294 media-specific extensions to the Interfaces Group for 295 managing MPLS Tunnels as logical interfaces. 297 This memo assumes the interpretation of the Interfaces 298 Group to be in accordance with [RFC2863] which states that 299 the interfaces table (ifTable) contains information on the 300 managed resource's interfaces and that each sub-layer below 301 the internetwork layer of a network interface is considered 302 an interface. Thus, the MPLS interface is represented as 303 an entry in the ifTable. The interrelation of entries in 304 the ifTable is defined by the Interfaces Stack Group 305 defined in [RFC2863]. 307 When using MPLS Tunnels as interfaces, the interface stack 308 table might appear as follows: 310 +------------------------------------------------+ 311 | MPLS tunnel interface ifType = mplsTunnel(150) | 312 +------------------------------------------------+ 313 | MPLS interface ifType = mpls(166) | 314 +------------------------------------------------+ 315 | Underlying layer | 316 +------------------------------------------------+ 318 In the above diagram, "Underlying Layer" refers to the 319 ifIndex of any interface type for which MPLS 320 internetworking has been defined. Examples include ATM, 321 Frame Relay, and Ethernet. 323 8.1. Support of the MPLS Tunnel Interface by ifTable 325 Some specific interpretations of ifTable for those MPLS 326 tunnels represented as interfaces follow: 328 Object Use for the MPLS tunnel. 330 ifIndex Each MPLS tunnel is represented by an 331 ifEntry. 333 ifDescr Description of the MPLS tunnel. 335 ifType The value that is allocated for MPLS 336 tunnel is 150. 338 ifSpeed The total bandwidth in bits per second 339 for use by the MPLS tunnel. 341 ifPhysAddress Unused. 343 ifAdminStatus See [RFC2863]. 345 ifOperStatus This value reflects the actual 346 operational status of MPLS tunnel. 347 Assumes the value down(2) if the MPLS 348 tunnel is down. 350 ifLastChange See [RFC2863]. 352 ifInOctets The number of octets received over the 353 MPLS tunnel. 355 ifOutOctets The number of octets transmitted over 356 the MPLS tunnel. 358 ifInErrors The number of labeled packets dropped 359 due to uncorrectable errors. 361 ifInUnknownProtos The number of received packets 362 discarded during packet header 363 validation, including packets with 364 unrecognized label values. 366 ifOutErrors See [RFC2863]. 368 ifName Textual name (unique on this system) of 369 the MPLS tunnel or an octet string of 370 zero length. 372 ifLinkUpDownTrapEnable 373 Default is disabled (2). 375 ifConnectorPresent Set to false (2). 377 ifHighSpeed See [RFC2863]. 379 ifHCInOctets The 64-bit version of ifInOctets; 380 supported if required by the compliance 381 statements in [RFC2863]. 383 ifHCOutOctets The 64-bit version of ifOutOctets; 384 supported if required by the compliance 385 statements in [RFC2863]. 387 ifAlias The non-volatile 'alias' name for the 388 MPLS tunnel as specified by a network 389 manager. 391 9. Example of Tunnel Setup 393 This section contains an example of which MIB objects 394 should be modified if one would like to create a best 395 effort, loosely routed, unidirectional traffic engineered 396 tunnel, which spans two hops of a simple network. Note 397 that these objects should be created on the "head-end" 398 LSR. Those objects relevant to illustrating the 399 relationships amongst different tables are shown here. 400 Other objects may be needed before conceptual row 401 activation can happen. 403 The RowStatus values shown in this section are those to be 404 used in the set request, typically createAndGo(4) which is 405 used to create the conceptual row and have its status 406 immediately set to active. A subsequent retrieval 407 operation on the conceptual row will return a different 408 value, such as active(1). Please see [RFC2579] for a 409 detailed discussion on the use of RowStatus. 411 In mplsTunnelTable: 412 { 413 mplsTunnelIndex = 1, 414 mplsTunnelInstance = 1, 415 mplsTunnelIngressLSRId = 192.168.100.1, 416 mplsTunnelEgressLSRId = 192.168.101.1, 417 mplsTunnelName = "My first tunnel", 418 mplsTunnelDescr = "Here to there", 419 mplsTunnelIsIf = true (1), 420 -- RowPointer MUST point to the first accessible column 421 mplsTunnelXCPointer = mplsXCIndex.2.0.0.15, 422 mplsTunnelSignallingProto = none (1), 423 mplsTunnelSetupPrio = 0, 424 mplsTunnelHoldingPrio = 0, 425 mplsTunnelSessionAttributes = 0, 426 mplsTunnelLocalProtectInUse = false (0), 427 -- RowPointer MUST point to the first accessible column 428 mplsTunnelResourcePointer = mplsTunnelResourceIndex.5, 429 mplsTunnelInstancePriority = 1, 430 mplsTunnelHopTableIndex = 1, 431 mplsTunnelIncludeAnyAffinity = 0, 432 mplsTunnelIncludeAllAffinity = 0, 433 mplsTunnelExcludeAllAffinity = 0, 434 mplsTunnelPathInUse = 1, 435 mplsTunnelRole = head (1), 436 -- Mandatory parameters needed to activate the row go here 437 mplsTunnelRowStatus = createAndGo (4) 438 } 440 In mplsTunnelResourceTable: 441 { 442 mplsTunnelResourceIndex = 5, 443 mplsTunnelResourceMaxRate = 0, 444 mplsTunnelResourceMeanRate = 0, 445 mplsTunnelResourceMaxBurstSize = 0, 446 mplsTunnelResourceMeanBurstSize = 0, 447 mplsTunnelResourceExBurstSize = 0, 448 mplsTunnelResourceExBurstSize = unspecified (1), 449 mplsTunnelResourceWeight = 0, 450 -- Mandatory parameters needed to activate the row go here 451 mplsTunnelResourceRowStatus = createAndGo (4) 452 } 454 The next two instances of mplsTunnelHopEntry are used to 455 denote the hops this tunnel will take across the network. 457 The following denotes the beginning of the network, or the 458 first hop. We have used the fictitious LSR identified by 459 "192.168.100.1" as our example head-end router. 461 In mplsTunnelHopTable: 462 { 463 mplsTunnelHopListIndex = 1, 464 mplsTunnelPathOptionIndex = 1, 465 mplsTunnelHopIndex = 1, 466 mplsTunnelHopAddrType = ipv4 (1), 467 mplsTunnelHopIpAddr = "192.168.100.1", 468 mplsTunnelHopIpPrefixLen = 32, 469 mplsTunnelHopType = loose (2), 470 mplsTunnelHopInclude = true (1), 471 mplsTunnelHopPathOptionName = "here", 472 mplsTunnelHopEntryPathComp = explicit (2), 473 -- Mandatory parameters needed to activate the row go here 474 mplsTunnelHopRowStatus = createAndGo (4) 475 } 477 The following denotes the end of the network, or the last 478 hop in our example. We have used the fictitious LSR 479 identified by "192.168.101.1" as our end router. 481 In mplsTunnelHopTable: 482 { 483 mplsTunnelHopListIndex = 1, 484 mplsTunnelPathOptionIndex = 1, 485 mplsTunnelHopIndex = 2, 486 mplsTunnelHopAddrType = ipv4 (1), 487 mplsTunnelHopIpAddr = "192.168.101.1", 488 mplsTunnelHopIpPrefixLen = 32, 489 mplsTunnelHopType = loose (2), 490 mplsTunnelHopInclude = true (1), 491 mplsTunnelHopPathOptionName = "there", 492 mplsTunnelHopEntryPathComp = explicit (2), 493 -- Mandatory parameters needed to activate the row go here 494 mplsTunnelHopRowStatus = createAndGo (4) 495 } 497 10. The Use of RowPointer 499 RowPointer is a textual convention used to identify a 500 conceptual row in a conceptual table in a MIB by pointing 501 to the first accessible object. In this MIB module, in 502 mplsTunnelTable, the objects mplsTunnelXCPointer and 503 mplsTunnelResourcePointer are of type RowPointer. The 504 object mplsTunnelXCPointer points to a specific entry in 505 the mplsXCTable [LSRMIB]. This entry in the mplsXCTable is 506 the associated LSP for the given MPLS tunnel entry. The 507 object mplsTunnelResourcePointer points to a specific entry 508 in a traffic parameter table. An example of such a traffic 509 parameter table is mplsTunnelResourceTable. It indicates a 510 specific instance of a traffic parameter entry that is 511 associated with a given MPLS tunnel entry. These 512 RowPointer objects MUST point to the first instance of the 513 first accessible columnar object in the appropriate 514 conceptual row in order to allow the manager to find the 515 appropriate corresponding entry in either MPLS-LSR-STD-MIB 516 [LSRMIB] or MPLS-TE-STD-MIB [TEMIB]. If object 517 mplsTunnelXCPointer returns zeroDotZero it implies that 518 there is no LSP associated with that particular instance of 519 tunnel entry. If object mplsTunnelResourcePointer returns 520 zeroDotZero it implies that there is no QoS resource 521 associated with that particular instance of tunnel entry. 523 11. MPLS Traffic Engineering MIB Definitions 525 MPLS-TE-STD-MIB DEFINITIONS ::= BEGIN 527 IMPORTS 528 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 529 Integer32, Unsigned32, Counter32, Counter64, TimeTicks, 530 zeroDotZero 531 FROM SNMPv2-SMI 532 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 533 FROM SNMPv2-CONF 534 TruthValue, RowStatus, RowPointer, StorageType, 535 TimeStamp 536 FROM SNMPv2-TC 537 InterfaceIndexOrZero 538 FROM IF-MIB 539 mplsStdMIB, MplsBitRate, MplsBurstSize, MplsLSPID, 540 MplsTunnelIndex, MplsTunnelInstanceIndex, 541 MplsTunnelAffinity, MplsExtendedTunnelId, MplsPathIndex, 542 MplsPathIndexOrZero, MplsOwner, TeHopAddressType, 543 TeHopAddress, TeHopAddressAS, TeHopAddressUnnum 544 FROM MPLS-TC-STD-MIB 545 SnmpAdminString 546 FROM SNMP-FRAMEWORK-MIB 547 InetAddressPrefixLength 548 FROM INET-ADDRESS-MIB 549 ; 551 mplsTeStdMIB MODULE-IDENTITY 552 LAST-UPDATED 553 "200306231200Z" -- 23 June 2003 12:00:00 GMT 554 ORGANIZATION 555 "Multiprotocol Label Switching (MPLS) Working Group" 556 CONTACT-INFO 557 " 558 Cheenu Srinivasan 559 Email: cheenu@alumni.princeton.edu 561 Arun Viswanathan 562 Force10 Networks, Inc. 563 Email: arunv@force10networks.com 565 Thomas D. Nadeau 566 Cisco Systems, Inc. 567 Email: tnadeau@cisco.com 569 Comments about this document should be emailed 570 directly to the MPLS working group mailing list at 571 mpls@uu.net." 572 DESCRIPTION 573 "Copyright (C) The Internet Society (2003). This 574 version of this MIB module is part of RFC xxxx; see 575 the RFC itself for full legal notices. 577 This MIB module contains managed object definitions 578 for MPLS Traffic Engineering (TE) as defined in: 579 1. Extensions to RSVP for LSP Tunnels, Awduche et 580 al, RFC 3209, December 2001 581 2. Constraint-Based LSP Setup using LDP, Jamoussi 582 (Editor), RFC 3212, January 2002 583 3. Requirements for Traffic Engineering Over MPLS, 584 Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., 585 and J. McManus, RFC 2702, September 1999" 587 -- Revision history. 589 REVISION 590 "200306231200Z" -- 23 June 2003 12:00:00 GMT 591 DESCRIPTION 592 "Initial draft version issues as part of RFC XXXX." 594 ::= { mplsStdMIB 3 } 596 -- Top level components of this MIB module. 598 -- traps 599 mplsTeNotifications OBJECT IDENTIFIER ::= { mplsTeStdMIB 0 } 600 -- tables, scalars 601 mplsTeScalars OBJECT IDENTIFIER ::= { mplsTeStdMIB 1 } 602 mplsTeObjects OBJECT IDENTIFIER ::= { mplsTeStdMIB 2 } 603 -- conformance 604 mplsTeConformance OBJECT IDENTIFIER ::= { mplsTeStdMIB 3 } 605 -- MPLS Tunnel scalars. 607 mplsTunnelConfigured OBJECT-TYPE 608 SYNTAX Unsigned32 609 MAX-ACCESS read-only 610 STATUS current 611 DESCRIPTION 612 "The number of tunnels configured on this device. A 613 tunnel is considered configured if the 614 mplsTunnelRowStatus is active(1)." 615 ::= { mplsTeScalars 1 } 617 mplsTunnelActive OBJECT-TYPE 618 SYNTAX Unsigned32 619 MAX-ACCESS read-only 620 STATUS current 621 DESCRIPTION 622 "The number of tunnels active on this device. A 623 tunnel is considered active if the 624 mplsTunnelOperStatus is up(1)." 625 ::= { mplsTeScalars 2 } 627 mplsTunnelTEDistProto OBJECT-TYPE 628 SYNTAX BITS { 629 other (0), 630 ospf (1), 631 isis (2) 632 } 633 MAX-ACCESS read-only 634 STATUS current 635 DESCRIPTION 636 "The traffic engineering distribution protocol(s) 637 used by this LSR. Note that an LSR may support more 638 than one distribution protocol simultaneously." 639 ::= { mplsTeScalars 3 } 641 mplsTunnelMaxHops OBJECT-TYPE 642 SYNTAX Unsigned32 643 MAX-ACCESS read-only 644 STATUS current 645 DESCRIPTION 646 "The maximum number of hops that can be specified for 647 a tunnel on this device." 648 ::= { mplsTeScalars 4 } 650 mplsTunnelNotificationMaxRate OBJECT-TYPE 651 SYNTAX Unsigned32 652 MAX-ACCESS read-write 653 STATUS current 654 DESCRIPTION 655 "This variable indicates the maximum number of 656 notifications issued per second. If events occur 657 more rapidly, the implementation may simply fail to 658 emit these notifications during that period, or may 659 queue them until an appropriate time. A value of 0 660 means no throttling is applied and events may be 661 notified at the rate at which they occur." 662 DEFVAL { 0 } 663 ::= { mplsTeScalars 5 } 665 -- End of MPLS Tunnel scalars. 667 -- MPLS tunnel table. 669 mplsTunnelIndexNext OBJECT-TYPE 670 SYNTAX Integer32 (0..65535) 671 MAX-ACCESS read-only 672 STATUS current 673 DESCRIPTION 674 "This object contains the next appropriate value to 675 be used for mplsTunnelIndex when creating entries 676 in mplsTunnelTable. If the number of unassigned 677 entries is exhausted, a retrieval operation will 678 return a value of 0. This object may also return a 679 value of 0 when the LSR is unable to accept 680 conceptual row creation, for example, if the 681 mplsTunnelTable is implemented as read-only. To 682 obtain the value of mplsTunnelIndex for a new 683 entry, the manager must first issue a management 684 protocol retrieval operation to obtain the current 685 value of this object. The agent should modify the 686 value to reflect the next unassigned index after 687 each retrieval operation. After a manager retrieves 688 a value the agent will determine through its local 689 policy when this index value will be made available 690 for reuse." 691 ::= { mplsTeObjects 1 } 693 mplsTunnelTable OBJECT-TYPE 694 SYNTAX SEQUENCE OF MplsTunnelEntry 695 MAX-ACCESS not-accessible 696 STATUS current 697 DESCRIPTION 698 "The mplsTunnelTable allows new MPLS tunnels to be 699 created between an LSR and a remote endpoint, and 700 existing tunnels to be reconfigured or removed. 701 Note that only point-to-point tunnel segments are 702 supported, although multi-point-to-point and point- 703 to-multi-point connections are supported by an LSR 704 acting as a cross-connect. Each MPLS tunnel can 705 thus have one out-segment originating at this LSR 706 and/or one in-segment terminating at this LSR." 707 ::= { mplsTeObjects 2 } 709 mplsTunnelEntry OBJECT-TYPE 710 SYNTAX MplsTunnelEntry 711 MAX-ACCESS not-accessible 712 STATUS current 713 DESCRIPTION 714 "An entry in this table represents an MPLS tunnel. 715 An entry can be created by a network administrator 716 or by an SNMP agent as instructed by an MPLS 717 signalling protocol. Whenever a new entry is 718 created with mplsTunnelIsIf set to true(1), then a 719 corresponding entry is created in ifTable as well 720 (see RFC 2863). The ifType of this entry is 721 mplsTunnel(150). 723 A tunnel entry needs to be uniquely identified across 724 a MPLS network. Indices mplsTunnelIndex and 725 mplsTunnelInstance uniquely identify a tunnel on an 726 LSR originating the tunnel. To uniquely identify a 727 tunnel across a MPLS network requires index 728 mplsTunnelIngressLSRId. Last index 729 mplsTunnelEgressLSRId is useful in identifying all 730 instances of a tunnel that terminate on the same 731 egress LSR." 732 REFERENCE 733 "1. RFC 2863 - The Interfaces Group MIB, McCloghrie, 734 K., and F. Kastenholtz, June 2000 " 735 INDEX { 736 mplsTunnelIndex, 737 mplsTunnelInstance, 738 mplsTunnelIngressLSRId, 739 mplsTunnelEgressLSRId 740 } 741 ::= { mplsTunnelTable 1 } 743 MplsTunnelEntry ::= SEQUENCE { 744 mplsTunnelIndex MplsTunnelIndex, 745 mplsTunnelInstance MplsTunnelInstanceIndex, 746 mplsTunnelIngressLSRId MplsExtendedTunnelId, 747 mplsTunnelEgressLSRId MplsExtendedTunnelId, 748 mplsTunnelName SnmpAdminString, 749 mplsTunnelDescr SnmpAdminString, 750 mplsTunnelIsIf TruthValue, 751 mplsTunnelIfIndex InterfaceIndexOrZero, 752 mplsTunnelOwner MplsOwner, 753 mplsTunnelRole INTEGER, 754 mplsTunnelXCPointer RowPointer, 755 mplsTunnelSignallingProto INTEGER, 756 mplsTunnelSetupPrio Integer32, 757 mplsTunnelHoldingPrio Integer32, 758 mplsTunnelSessionAttributes BITS, 759 mplsTunnelLocalProtectInUse TruthValue, 760 mplsTunnelResourcePointer RowPointer, 761 mplsTunnelPrimaryInstance MplsTunnelInstanceIndex, 762 mplsTunnelInstancePriority Unsigned32, 763 mplsTunnelHopTableIndex MplsPathIndexOrZero, 764 mplsTunnelPathInUse MplsPathIndexOrZero, 765 mplsTunnelARHopTableIndex MplsPathIndexOrZero, 766 mplsTunnelCHopTableIndex MplsPathIndexOrZero, 767 mplsTunnelIncludeAnyAffinity MplsTunnelAffinity, 768 mplsTunnelIncludeAllAffinity MplsTunnelAffinity, 769 mplsTunnelExcludeAllAffinity MplsTunnelAffinity, 770 mplsTunnelTotalUpTime TimeTicks, 771 mplsTunnelInstanceUpTime TimeTicks, 772 mplsTunnelPrimaryUpTime TimeTicks, 773 mplsTunnelPathChanges Counter32, 774 mplsTunnelLastPathChange TimeTicks, 775 mplsTunnelCreationTime TimeStamp, 776 mplsTunnelStateTransitions Counter32, 777 mplsTunnelAdminStatus INTEGER, 778 mplsTunnelOperStatus INTEGER, 779 mplsTunnelRowStatus RowStatus, 780 mplsTunnelStorageType StorageType 781 } 783 mplsTunnelIndex OBJECT-TYPE 784 SYNTAX MplsTunnelIndex 785 MAX-ACCESS not-accessible 786 STATUS current 787 DESCRIPTION 788 "Uniquely identifies a set of tunnel instances 789 between a pair of ingress and egress LSRs." 790 ::= { mplsTunnelEntry 1 } 792 mplsTunnelInstance OBJECT-TYPE 793 SYNTAX MplsTunnelInstanceIndex 794 MAX-ACCESS not-accessible 795 STATUS current 796 DESCRIPTION 797 "Uniquely identifies a particular instance of a 798 tunnel between a pair of ingress and egress LSRs. 799 It is useful to identify multiple instances of 800 tunnels for the purposes of backup and parallel 801 tunnels. The tunnel entry with instance index 0 802 should refer to the configured tunnel interface (if 803 one exists), and values greater than 0 but less 804 than or equal to 65535 should be used to indicate 805 signaled (or backup) tunnel LSP instances. For 806 tunnel LSPs signaled using RSVP, this value should 807 correspond to the RSVP source port used for the 808 RSVP-TE session. Values greater than 65535 apply 809 to Fast Re-Route (FRR) detour instances " 810 ::= { mplsTunnelEntry 2 } 812 mplsTunnelIngressLSRId OBJECT-TYPE 813 SYNTAX MplsExtendedTunnelId 814 MAX-ACCESS not-accessible 815 STATUS current 816 DESCRIPTION 817 "Identity of the ingress LSR associated with this 818 tunnel instance. When the MPLS signalling protocol 819 is rsvp(2) this value SHOULD mimic the Extended 820 Tunnel Id field in the SESSION object. When the 821 MPLS signalling protocol is crldp(3) this value 822 SHOULD mimic the Ingress LSR Router ID field in the 823 LSPID TLV object." 824 REFERENCE 825 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 826 Awduche et al, RFC 3209, December 2001 827 2. Constraint-Based LSP Setup using LDP, Jamoussi 828 (Editor), RFC 3212, January 2002" 829 ::= { mplsTunnelEntry 3 } 831 mplsTunnelEgressLSRId OBJECT-TYPE 832 SYNTAX MplsExtendedTunnelId 833 MAX-ACCESS not-accessible 834 STATUS current 835 DESCRIPTION 836 "Identity of the egress LSR associated with this 837 tunnel instance." 838 ::= { mplsTunnelEntry 4 } 840 mplsTunnelName OBJECT-TYPE 841 SYNTAX SnmpAdminString 842 MAX-ACCESS read-create 843 STATUS current 844 DESCRIPTION 845 "The canonical name assigned to the tunnel. This name 846 can be used to refer to the tunnel on the LSR's 847 console port. If mplsTunnelIsIf is set to true 848 then the ifName of the interface corresponding to 849 this tunnel should have a value equal to 850 mplsTunnelName. Also see the description of ifName 851 in RFC 2863." 852 REFERENCE 853 "RFC 2863 - The Interfaces Group MIB, McCloghrie, K., 854 and F. Kastenholtz, June 2000" 855 ::= { mplsTunnelEntry 5 } 857 mplsTunnelDescr OBJECT-TYPE 858 SYNTAX SnmpAdminString 859 MAX-ACCESS read-create 860 STATUS current 861 DESCRIPTION 862 "A textual string containing information about the 863 tunnel. If there is no description this object 864 contains a zero length string." 865 DEFVAL {""} 866 ::= { mplsTunnelEntry 6 } 868 mplsTunnelIsIf OBJECT-TYPE 869 SYNTAX TruthValue 870 MAX-ACCESS read-create 871 STATUS current 872 DESCRIPTION 873 "Denotes whether or not this tunnel corresponds to an 874 interface represented in the interfaces group 875 table. Note that if this variable is set to true 876 then the ifName of the interface corresponding to 877 this tunnel should have a value equal to 878 mplsTunnelName. Also see the description of ifName 879 in RFC 2863." 880 REFERENCE 881 "RFC 2863 - The Interfaces Group MIB, McCloghrie, K., 882 and F. Kastenholtz, June 2000" 883 DEFVAL { false } 884 ::= { mplsTunnelEntry 7 } 886 mplsTunnelIfIndex OBJECT-TYPE 887 SYNTAX InterfaceIndexOrZero 888 MAX-ACCESS read-only 889 STATUS current 890 DESCRIPTION 891 "If mplsTunnelIsIf is set to true, then this value 892 contains the LSR-assigned ifIndex which corresponds 893 to an entry in the interfaces table. Otherwise 894 this variable should contain the value of zero 895 indicating that a valid ifIndex was not assigned to 896 this tunnel interface." 897 REFERENCE 898 "RFC 2863 - The Interfaces Group MIB, McCloghrie, K., 899 and F. Kastenholtz, June 2000" 900 ::= { mplsTunnelEntry 8 } 902 mplsTunnelOwner OBJECT-TYPE 903 SYNTAX MplsOwner 904 MAX-ACCESS read-only 905 STATUS current 906 DESCRIPTION 907 "Denotes the entity that created and is responsible 908 for managing this tunnel. This column is 909 automatically filled by the agent on creation of a 910 row." 911 ::= { mplsTunnelEntry 9 } 913 mplsTunnelRole OBJECT-TYPE 914 SYNTAX INTEGER { head(1), transit(2), tail(3) } 915 MAX-ACCESS read-create 916 STATUS current 917 DESCRIPTION 918 "This value signifies the role that this tunnel 919 entry/instance represents. This value MUST be set 920 to head(1) at the originating point of the tunnel. 921 This value MUST be set to transit(2) at transit 922 points along the tunnel, if transit points are 923 supported. This value MUST be set to tail(3) at the 924 terminating point of the tunnel if tunnel tails are 925 supported." 926 ::= { mplsTunnelEntry 10 } 928 mplsTunnelXCPointer OBJECT-TYPE 929 SYNTAX RowPointer 930 MAX-ACCESS read-create 931 STATUS current 932 DESCRIPTION 933 "This variable points to a row in the mplsXCTable. 934 This table identifies the segments that compose 935 this tunnel, their characteristics, and 936 relationships to each other. A value of zeroDotZero 937 indicates that no LSP has been associated with this 938 tunnel yet." 939 REFERENCE 940 "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS 941 Label Switch Router Management Information Base, 942 Internet Draft , 943 June 2003." 944 DEFVAL { zeroDotZero } 945 ::= { mplsTunnelEntry 11 } 947 mplsTunnelSignallingProto OBJECT-TYPE 948 SYNTAX INTEGER { 949 none(1), 950 rsvp(2), 951 crldp(3), 952 other(4) 953 } 954 MAX-ACCESS read-create 955 STATUS current 956 DESCRIPTION 957 "The signalling protocol, if any, used to setup this 958 tunnel." 959 DEFVAL { none } 960 ::= { mplsTunnelEntry 12 } 962 mplsTunnelSetupPrio OBJECT-TYPE 963 SYNTAX Integer32 (0..7) 964 MAX-ACCESS read-create 965 STATUS current 966 DESCRIPTION 967 "Indicates the setup priority of this tunnel." 968 REFERENCE 969 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 970 Awduche et al, RFC 3209, December 2001 971 2. Constraint-Based LSP Setup using LDP, Jamoussi 972 (Editor), RFC 3212, January 2002" 973 ::= { mplsTunnelEntry 13 } 975 mplsTunnelHoldingPrio OBJECT-TYPE 976 SYNTAX Integer32 (0..7) 977 MAX-ACCESS read-create 978 STATUS current 979 DESCRIPTION 980 "Indicates the holding priority for this tunnel." 981 REFERENCE 982 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 983 Awduche et al, RFC3209, December 2001 984 2. Constraint-Based LSP Setup using LDP, Jamoussi 985 (Editor), RFC 3212, January 2002" 987 ::= { mplsTunnelEntry 14 } 989 mplsTunnelSessionAttributes OBJECT-TYPE 990 SYNTAX BITS { 991 fastReroute (0), 992 mergingPermitted (1), 993 isPersistent (2), 994 isPinned (3), 995 recordRoute(4) 996 } 997 MAX-ACCESS read-create 998 STATUS current 999 DESCRIPTION 1000 "This bit mask indicates optional session values for 1001 this tunnel. The following describes these bit 1002 fields: 1004 fastRerouteThis flag indicates that the any tunnel 1005 hop may choose to reroute this tunnel without 1006 tearing it down. This flag permits transit routers 1007 to use a local repair mechanism which may result in 1008 violation of the explicit routing of this tunnel. 1009 When a fault is detected on an adjacent downstream 1010 link or node, a transit router can re-route traffic 1011 for fast service restoration. 1013 mergingPermitted This flag permits transit routers 1014 to merge this session with other RSVP sessions for 1015 the purpose of reducing resource overhead on 1016 downstream transit routers, thereby providing 1017 better network scaling. 1019 isPersistent Indicates whether this tunnel should 1020 be restored automatically after a failure occurs. 1022 isPinned This flag indicates whether the loose- 1023 routed hops of this tunnel are to be pinned. 1025 recordRouteThis flag indicates whether or not the 1026 signalling protocol should remember the tunnel path 1027 after it has been signaled." 1028 REFERENCE 1029 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 1030 Awduche et al, RFC 3209, December 2001." 1031 ::= { mplsTunnelEntry 15 } 1033 mplsTunnelLocalProtectInUse OBJECT-TYPE 1034 SYNTAX TruthValue 1035 MAX-ACCESS read-create 1036 STATUS current 1037 DESCRIPTION 1038 "Indicates that the local repair mechanism is in use 1039 to maintain this tunnel (usually in the face of an 1040 outage of the link it was previously routed over)." 1041 ::= { mplsTunnelEntry 16 } 1043 mplsTunnelResourcePointer OBJECT-TYPE 1044 SYNTAX RowPointer 1045 MAX-ACCESS read-create 1046 STATUS current 1047 DESCRIPTION 1048 "This variable represents a pointer to the traffic 1049 parameter specification for this tunnel. This 1050 value may point at an entry in the 1051 mplsTunnelResourceEntry to indicate which 1052 mplsTunnelResourceEntry is to be assigned to this 1053 segment. This value may optionally point at an 1054 externally defined traffic parameter specification 1055 table. A value of zeroDotZero indicates best- 1056 effort treatment. By having the same value of this 1057 object, two or more segments can indicate resource 1058 sharing." 1059 DEFVAL { zeroDotZero } 1060 ::= { mplsTunnelEntry 17 } 1062 mplsTunnelPrimaryInstance OBJECT-TYPE 1063 SYNTAX MplsTunnelInstanceIndex 1064 MAX-ACCESS read-only 1065 STATUS current 1066 DESCRIPTION 1067 "Specifies the instance index of the primary instance 1068 of this tunnel." 1069 ::= { mplsTunnelEntry 18 } 1071 mplsTunnelInstancePriority OBJECT-TYPE 1072 SYNTAX Unsigned32 1073 MAX-ACCESS read-create 1074 STATUS current 1075 DESCRIPTION 1076 "This value indicates which priority, in descending 1077 order, with 0 indicating the lowest priority, 1078 within a group of tunnel instances. A group of 1079 tunnel instances is defined as a set of tunnels 1080 with the same mplsTunnelIndex in this table, but 1081 with a different mplsTunnelInstance. Tunnel group 1082 priorities are used to denote the priority at which 1083 a particular tunnel instance will supercede 1084 another. Instances of tunnels containing the same 1085 mplsTunnelInstancePriority will be used for load 1086 sharing." 1087 DEFVAL { 0 } 1088 ::= { mplsTunnelEntry 19 } 1090 mplsTunnelHopTableIndex OBJECT-TYPE 1091 SYNTAX MplsPathIndexOrZero 1092 MAX-ACCESS read-create 1093 STATUS current 1094 DESCRIPTION 1095 "Index into the mplsTunnelHopTable entry that 1096 specifies the explicit route hops for this tunnel." 1097 ::= { mplsTunnelEntry 20 } 1099 mplsTunnelPathInUse OBJECT-TYPE 1100 SYNTAX MplsPathIndexOrZero 1101 MAX-ACCESS read-create 1102 STATUS current 1103 DESCRIPTION 1104 "This value denotes the configured path that was 1105 chosen for this tunnel. This value reflects the 1106 secondary index into mplsTunnelHopTable. This path 1107 may not exactly match the one in 1108 mplsTunnelARHopTable due to the fact that some CSPF 1109 modification may have taken place. See 1110 mplsTunnelARHopTable for the actual path being 1111 taken by the tunnel. A value of zero denotes that 1112 no path is currently in use or available." 1113 ::= { mplsTunnelEntry 21 } 1115 mplsTunnelARHopTableIndex OBJECT-TYPE 1116 SYNTAX MplsPathIndexOrZero 1117 MAX-ACCESS read-only 1118 STATUS current 1119 DESCRIPTION 1120 "Index into the mplsTunnelARHopTable entry that 1121 specifies the actual hops traversed by the tunnel. 1122 This is automatically updated by the agent when the 1123 actual hops becomes available." 1124 ::= { mplsTunnelEntry 22 } 1126 mplsTunnelCHopTableIndex OBJECT-TYPE 1127 SYNTAX MplsPathIndexOrZero 1128 MAX-ACCESS read-only 1129 STATUS current 1130 DESCRIPTION 1131 "Index into the mplsTunnelCHopTable entry that 1132 specifies the computed hops traversed by the 1133 tunnel. This is automatically updated by the agent 1134 when computed hops become available or when 1135 computed hops get modified." 1136 ::= { mplsTunnelEntry 23 } 1138 mplsTunnelIncludeAnyAffinity OBJECT-TYPE 1139 SYNTAX MplsTunnelAffinity 1140 MAX-ACCESS read-create 1141 STATUS current 1142 DESCRIPTION 1143 "A link satisfies the include-any constraint if and 1144 only if the constraint is zero, or the link and the 1145 constraint have a resource class in common." 1146 REFERENCE 1147 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 1148 Awduche et al, RFC 3209, December 2001." 1149 ::= { mplsTunnelEntry 24 } 1151 mplsTunnelIncludeAllAffinity OBJECT-TYPE 1152 SYNTAX MplsTunnelAffinity 1153 MAX-ACCESS read-create 1154 STATUS current 1155 DESCRIPTION 1156 "A link satisfies the include-all constraint if and 1157 only if the link contains all of the administrative 1158 groups specified in the constraint." 1159 REFERENCE 1160 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 1161 Awduche et al, RFC 3209, December 2001." 1162 ::= { mplsTunnelEntry 25 } 1164 mplsTunnelExcludeAllAffinity OBJECT-TYPE 1165 SYNTAX MplsTunnelAffinity 1166 MAX-ACCESS read-create 1167 STATUS current 1168 DESCRIPTION 1169 "A link satisfies the exclude-all constraint if and 1170 only if the link contains none of the 1171 administrative groups specified in the constraint." 1172 REFERENCE 1173 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 1174 Awduche et al, RFC 3209, December 2001." 1175 ::= { mplsTunnelEntry 26 } 1177 mplsTunnelTotalUpTime OBJECT-TYPE 1178 SYNTAX TimeTicks 1179 MAX-ACCESS read-only 1180 STATUS current 1181 DESCRIPTION 1182 "This value represents the aggregate up time for all 1183 instances of this tunnel, if available. If this 1184 value is unavailable, it MUST return a value of 0." 1185 ::= { mplsTunnelEntry 27 } 1187 mplsTunnelInstanceUpTime OBJECT-TYPE 1188 SYNTAX TimeTicks 1189 MAX-ACCESS read-only 1190 STATUS current 1191 DESCRIPTION 1192 "This value identifies the total time that this 1193 tunnel instance's operStatus has been Up(1)." 1194 ::= { mplsTunnelEntry 28 } 1196 mplsTunnelPrimaryUpTime OBJECT-TYPE 1197 SYNTAX TimeTicks 1198 MAX-ACCESS read-only 1199 STATUS current 1200 DESCRIPTION 1201 "Specifies the total time the primary instance of 1202 this tunnel has been active. The primary instance 1203 of this tunnel is defined in 1204 mplsTunnelPrimaryInstance." 1205 ::= { mplsTunnelEntry 29 } 1207 mplsTunnelPathChanges OBJECT-TYPE 1208 SYNTAX Counter32 1209 MAX-ACCESS read-only 1210 STATUS current 1211 DESCRIPTION 1212 "Specifies the number of times the paths has changed 1213 for this tunnel since its creation." 1214 ::= { mplsTunnelEntry 30 } 1216 mplsTunnelLastPathChange OBJECT-TYPE 1217 SYNTAX TimeTicks 1218 MAX-ACCESS read-only 1219 STATUS current 1220 DESCRIPTION 1221 "Specifies the time since the last path change for 1222 this tunnel." 1223 ::= { mplsTunnelEntry 31 } 1225 mplsTunnelCreationTime OBJECT-TYPE 1226 SYNTAX TimeStamp 1227 MAX-ACCESS read-only 1228 STATUS current 1229 DESCRIPTION 1230 "Specifies the value of SysUpTime when the first 1231 instance of this tunnel came into existence." 1232 ::= { mplsTunnelEntry 32 } 1234 mplsTunnelStateTransitions OBJECT-TYPE 1235 SYNTAX Counter32 1236 MAX-ACCESS read-only 1237 STATUS current 1238 DESCRIPTION 1239 "Specifies the number of times the state of this 1240 tunnel instance has changed." 1241 ::= { mplsTunnelEntry 33 } 1243 mplsTunnelAdminStatus OBJECT-TYPE 1244 SYNTAX INTEGER { 1245 -- ready to pass packets 1246 up(1), 1247 down(2), 1248 -- in some test mode 1249 testing(3) 1250 } 1251 MAX-ACCESS read-create 1252 STATUS current 1253 DESCRIPTION 1254 "Indicates the desired operational status of this 1255 tunnel." 1256 ::= { mplsTunnelEntry 34 } 1258 mplsTunnelOperStatus OBJECT-TYPE 1259 SYNTAX INTEGER { 1260 -- ready to pass packets 1261 up(1), 1262 down(2), 1263 -- in some test mode 1264 testing(3), 1265 -- status cannot be determined 1266 unknown(4), 1267 dormant(5), 1268 -- some component is missing 1269 notPresent(6), 1270 -- down due to the state of 1271 -- lower layer interfaces 1272 lowerLayerDown(7) 1273 } 1274 MAX-ACCESS read-only 1275 STATUS current 1276 DESCRIPTION 1277 "Indicates the actual operational status of this 1278 tunnel, which is typically but not limited to, a 1279 function of the state of individual segments of 1280 this tunnel." 1281 ::= { mplsTunnelEntry 35 } 1283 mplsTunnelRowStatus OBJECT-TYPE 1284 SYNTAX RowStatus 1285 MAX-ACCESS read-create 1286 STATUS current 1287 DESCRIPTION 1288 "This variable is used to create, modify, and/or 1289 delete a row in this tabole. When a row in this 1290 table is in active(1) state, no objects in that row 1291 can be modified except mplsTunnelRowStatus and 1292 mplsTunnelStorageType." 1293 ::= { mplsTunnelEntry 36 } 1295 mplsTunnelStorageType OBJECT-TYPE 1296 SYNTAX StorageType 1297 MAX-ACCESS read-create 1298 STATUS current 1299 DESCRIPTION 1300 "This variable indicates the storage type for this 1301 object. If this variable is set to readOnly(5), 1302 and the corresponding entry is removed, then the 1303 agent must remove this row shortly thereafter 1304 [RFC2579]. 1306 Setting this object to permanent(4) indicates that 1307 this object should be restored automatically after 1308 failures. The agent MUST ensure that the 1309 associated mplsTunnelXCPointer, 1310 mplsTunnelResourcePointer and associated row in 1311 mplsTunnelHopTable also has the same StorageType 1312 value and is restored consistently upon 1313 restoration. 1315 No objects are required to be writable for rows in 1316 this table with this object set to permanent(4). 1317 The default value is volatile(2)." 1318 DEFVAL { volatile } 1319 ::= { mplsTunnelEntry 37 } 1321 -- End of mplsTunnelTable 1322 mplsTunnelHopListIndexNext OBJECT-TYPE 1323 SYNTAX Unsigned32 (0..2147483647) 1324 MAX-ACCESS read-only 1325 STATUS current 1326 DESCRIPTION 1327 "This object contains an appropriate value to be used 1328 for mplsTunnelHopListIndex when creating entries in 1329 the mplsTunnelHopTable. If the number of 1330 unassigned entries is exhausted, a retrieval 1331 operation will return a value of 0. This object 1332 may also return a value of 0 when the LSR is unable 1333 to accept conceptual row creation, for example, if 1334 the mplsTunnelHopTable is implemented as read-only. 1335 To obtain the value of mplsTunnelHopListIndex for a 1336 new entry in the mplsTunnelHopTable, the manager 1337 issues a management protocol retrieval operation to 1338 obtain the current value of mplsTunnelHopIndex. 1339 After each retrieval operation, the agent should 1340 modify the value to reflect the next unassigned 1341 index. After a manager retrieves a value the agent 1342 will determine through its local policy when this 1343 index value will be made available for reuse." 1344 ::= { mplsTeObjects 3 } 1346 mplsTunnelHopTable OBJECT-TYPE 1347 SYNTAX SEQUENCE OF MplsTunnelHopEntry 1348 MAX-ACCESS not-accessible 1349 STATUS current 1350 DESCRIPTION 1351 "The mplsTunnelHopTable is used to indicate the hops, 1352 strict or loose, for an MPLS tunnel defined in 1353 mplsTunnelTable, when it is established via 1354 signalling, for the outgoing direction of the 1355 tunnel. Each row in this table is indexed by 1356 mplsTunnelHopListIndex. Each row also has a 1357 secondary index mplsTunnelHopIndex corresponding to 1358 the next hop that this row corresponds to. The 1359 first row in the table is the first hop after the 1360 origination point of the tunnel. In case we want 1361 to specify a particular interface on the 1362 originating LSR of an outgoing tunnel by which we 1363 want packets to exit the LSR, we specify this as 1364 the first hop for this tunnel in 1365 mplsTunnelHopTable." 1366 ::= { mplsTeObjects 4 } 1368 mplsTunnelHopEntry OBJECT-TYPE 1369 SYNTAX MplsTunnelHopEntry 1370 MAX-ACCESS not-accessible 1371 STATUS current 1372 DESCRIPTION 1373 "An entry in this table represents a tunnel hop. An 1374 entry is created by a network administrator for 1375 signaled ERLSP set up by an MPLS signalling 1376 protocol." 1377 INDEX { 1378 mplsTunnelHopListIndex, 1379 mplsTunnelHopPathOptionIndex, 1380 mplsTunnelHopIndex 1381 } 1382 ::= { mplsTunnelHopTable 1 } 1384 MplsTunnelHopEntry ::= SEQUENCE { 1385 mplsTunnelHopListIndex MplsPathIndex, 1386 mplsTunnelHopPathOptionIndex MplsPathIndex, 1387 mplsTunnelHopIndex MplsPathIndex, 1388 mplsTunnelHopAddrType TeHopAddressType, 1389 mplsTunnelHopIpAddr TeHopAddress, 1390 mplsTunnelHopIpPrefixLen InetAddressPrefixLength, 1391 mplsTunnelHopAsNumber TeHopAddressAS, 1392 mplsTunnelHopAddrUnnum TeHopAddressUnnum, 1393 mplsTunnelHopLspId MplsLSPID, 1394 mplsTunnelHopType INTEGER, 1395 mplsTunnelHopInclude TruthValue, 1396 mplsTunnelHopPathOptionName SnmpAdminString, 1397 mplsTunnelHopEntryPathComp INTEGER, 1398 mplsTunnelHopRowStatus RowStatus, 1399 mplsTunnelHopStorageType StorageType 1400 } 1402 mplsTunnelHopListIndex OBJECT-TYPE 1403 SYNTAX MplsPathIndex 1404 MAX-ACCESS not-accessible 1405 STATUS current 1406 DESCRIPTION 1407 "Primary index into this table identifying a 1408 particular explicit route object." 1409 ::= { mplsTunnelHopEntry 1 } 1411 mplsTunnelHopPathOptionIndex OBJECT-TYPE 1412 SYNTAX MplsPathIndex 1413 MAX-ACCESS not-accessible 1414 STATUS current 1415 DESCRIPTION 1416 "Secondary index into this table identifying a 1417 particular group of hops representing a particular 1418 configured path. This is otherwise known as a path 1419 option." 1420 ::= { mplsTunnelHopEntry 2 } 1422 mplsTunnelHopIndex OBJECT-TYPE 1423 SYNTAX MplsPathIndex 1424 MAX-ACCESS not-accessible 1425 STATUS current 1426 DESCRIPTION 1427 "Secondary index into this table identifying a 1428 particular hop." 1429 ::= { mplsTunnelHopEntry 3 } 1431 mplsTunnelHopAddrType OBJECT-TYPE 1432 SYNTAX TeHopAddressType 1433 MAX-ACCESS read-create 1434 STATUS current 1435 DESCRIPTION 1436 "Denotes the address type of this tunnel hop. If set 1437 to ipv4(1) or ipv6(2), it indicates that the 1438 mplsTunnelHopIpAddr contains respectively the IPv4 1439 or IPv6 address of this hop. The values contained 1440 in mplsTunnelHopAsNumber, mplsTunnelHopAddrUnnum 1441 and mplsTunnelHopLspId should be ignored. If this 1442 object is set to asnumber(3), the IP address 1443 related objects should be ignored, and the 1444 mplsTunnelHopAsNumber should be referred to. If this 1445 object is set to unnum(4), then only the object 1446 mplsTunnelHopAddrUnnum should be referred to. If 1447 the object is set to lspid(5), then all but the 1448 mplsTunnelHopLspId should be referred to. Note that 1449 lspid(5) is a valid option only for tunnels 1450 signaled via CRLDP" 1451 DEFVAL { ipv4 } 1452 ::= { mplsTunnelHopEntry 4 } 1454 mplsTunnelHopIpAddr OBJECT-TYPE 1455 SYNTAX TeHopAddress 1456 MAX-ACCESS read-create 1457 STATUS current 1458 DESCRIPTION 1459 "If mplsTunnelHopAddrType is set to ipv4(1) or 1460 ipv6(2), then this value will contain respectively 1461 the IPv4 address or the IPv6 address prefix of this 1462 hop. This object should be used in conjunction with 1463 mplsTunnelHopIpPrefixLen that provides the prefix 1464 length of the address. If mplsTunnelHopAddrType is 1465 set to lspid(5), then this value will contain the 1466 Ingress LSR Router ID of the Tunnel. Otherwise the 1467 agent should set this object to zero-length string 1468 and the manager should ignore this." 1469 ::= { mplsTunnelHopEntry 5 } 1471 mplsTunnelHopIpPrefixLen OBJECT-TYPE 1472 SYNTAX InetAddressPrefixLength 1473 MAX-ACCESS read-create 1474 STATUS current 1475 DESCRIPTION 1476 "If mplsTunnelHopAddrType is set to ipv4(1) or 1477 ipv6(2), then this value will contain an 1478 appropriate prefix length for the IP address in 1479 object mplsTunnelHopIpAddr. Otherwise a management 1480 entity SHOULD set this object to 0 and an agent 1481 MUST ignore it." 1482 ::= { mplsTunnelHopEntry 6 } 1484 mplsTunnelHopAsNumber OBJECT-TYPE 1485 SYNTAX TeHopAddressAS 1486 MAX-ACCESS read-create 1487 STATUS current 1488 DESCRIPTION 1489 "If mplsTunnelHopAddrType is set to asnumber(3), then 1490 this value will contain the AS number of this hop. 1491 Otherwise the agent should set this object to zero- 1492 length string and the manager should ignore this." 1493 ::= { mplsTunnelHopEntry 7 } 1495 mplsTunnelHopAddrUnnum OBJECT-TYPE 1496 SYNTAX TeHopAddressUnnum 1497 MAX-ACCESS read-create 1498 STATUS current 1499 DESCRIPTION 1500 "If mplsTunnelHopAddrType is set to unnum(4), then 1501 this value will contain the interface id of the 1502 unnumbered interface for this hop. Otherwise the 1503 agent should set this object to zero-length string 1504 and the manager should ignore this." 1505 ::= { mplsTunnelHopEntry 8 } 1507 mplsTunnelHopLspId OBJECT-TYPE 1508 SYNTAX MplsLSPID 1509 MAX-ACCESS read-create 1510 STATUS current 1511 DESCRIPTION 1512 "If mplsTunnelHopAddrType is set to lspid(5), then 1513 this value will contain the LSPID of a tunnel of 1514 this hop. The present tunnel being configured is 1515 tunneled through this hop (using label stacking). 1516 This object is otherwise insignificant and should 1517 contain a value of 0 to indicate this fact." 1518 ::= { mplsTunnelHopEntry 9 } 1520 mplsTunnelHopType OBJECT-TYPE 1521 SYNTAX INTEGER { 1522 strict(1), 1523 loose(2) 1524 } 1525 MAX-ACCESS read-create 1526 STATUS current 1527 DESCRIPTION 1528 "Denotes whether this tunnel hop is routed in a 1529 strict or loose fashion." 1530 ::= { mplsTunnelHopEntry 10 } 1532 mplsTunnelHopInclude OBJECT-TYPE 1533 SYNTAX TruthValue 1534 MAX-ACCESS read-create 1535 STATUS current 1536 DESCRIPTION 1537 "If this value is set to true, then this indicates 1538 that this hop must be included in the tunnel's 1539 path. If this value is set to false, then this hop 1540 must be avoided when calculating the path for this 1541 tunnel. The default value of this object is true, 1542 so that by default all indicated hops are included 1543 in the CSPF path computation." 1544 DEFVAL { true } 1545 ::= { mplsTunnelHopEntry 11 } 1547 mplsTunnelHopPathOptionName OBJECT-TYPE 1548 SYNTAX SnmpAdminString 1549 MAX-ACCESS read-create 1550 STATUS current 1551 DESCRIPTION 1552 "The description of this series of hops as they 1553 relate to the specified path option." 1554 ::= { mplsTunnelHopEntry 12 } 1556 mplsTunnelHopEntryPathComp OBJECT-TYPE 1557 SYNTAX INTEGER { 1558 dynamic(1), -- CSPF computed 1559 explicit(2) -- strict hop 1560 } 1562 MAX-ACCESS read-create 1563 STATUS current 1564 DESCRIPTION 1565 "If this value is set to dynamic, then the user 1566 should only specify the source and destination of 1567 the path and expect that the CSPF will calculate 1568 the remainder of the path. If this value is set to 1569 explicit, the user should specify the entire path 1570 for the tunnel to take. This path may contain 1571 strict or loose hops. Each hop along a specific 1572 path should have this object set to the same value" 1573 ::= { mplsTunnelHopEntry 13 } 1575 mplsTunnelHopRowStatus OBJECT-TYPE 1576 SYNTAX RowStatus 1577 MAX-ACCESS read-create 1578 STATUS current 1579 DESCRIPTION 1580 "This variable is used to create, modify, and/or 1581 delete a row in this tabole. When a row in this 1582 table is in active(1) state, no objects in that row 1583 can be modified except mplsTunnelHopRowStatus and 1584 mplsTunnelHopStorageType." 1585 ::= { mplsTunnelHopEntry 14 } 1587 mplsTunnelHopStorageType OBJECT-TYPE 1588 SYNTAX StorageType 1589 MAX-ACCESS read-create 1590 STATUS current 1591 DESCRIPTION 1592 "This variable indicates the storage type for this 1593 object. If this variable is set to readOnly(5), 1594 and the corresponding entry is removed, then the 1595 agent must remove this row shortly thereafter 1596 [RFC2579]. 1598 Setting this object to permanent(4) indicates that 1599 this object should be restored automatically after 1600 failures. 1602 No objects are required to be writable for rows in 1603 this table with this object set to permanent(4). 1604 The default value is volatile(2)." 1605 DEFVAL { volatile } 1606 ::= { mplsTunnelHopEntry 15 } 1608 -- End of mplsTunnelHopTable 1609 -- Begin of mplsTunnelResourceTable 1611 mplsTunnelResourceIndexNext OBJECT-TYPE 1612 SYNTAX Unsigned32 (0.. 2147483647) 1613 MAX-ACCESS read-only 1614 STATUS current 1615 DESCRIPTION 1616 "This object contains the next appropriate value to 1617 be used for mplsTunnelResourceIndex when creating 1618 entries in the mplsTunnelResourceTable. If the 1619 number of unassigned entries is exhausted, a 1620 retrieval operation will return a value of 0. This 1621 object may also return a value of 0 when the LSR is 1622 unable to accept conceptual row creation, for 1623 example, if the mplsTunnelTable is implemented as 1624 read-only. To obtain the mplsTunnelResourceIndex 1625 value for a new entry, the manager must first issue 1626 a management protocol retrieval operation to obtain 1627 the current value of this object. The agent should 1628 modify the value to reflect the next unassigned 1629 index after each retrieval operation. After a 1630 manager retrieves a value the agent will determine 1631 through its local policy when this index value will 1632 be made available for reuse." 1633 ::= { mplsTeObjects 5 } 1635 mplsTunnelResourceTable OBJECT-TYPE 1636 SYNTAX SEQUENCE OF MplsTunnelResourceEntry 1637 MAX-ACCESS not-accessible 1638 STATUS current 1639 DESCRIPTION 1640 "The mplsTunnelResourceTable allows a manager to 1641 specify which resources are desired for an MPLS 1642 tunnel. This table also allows several tunnels to 1643 point to a single entry in this table, implying 1644 that these tunnels should share resources." 1645 ::= { mplsTeObjects 6 } 1647 mplsTunnelResourceEntry OBJECT-TYPE 1648 SYNTAX MplsTunnelResourceEntry 1649 MAX-ACCESS not-accessible 1650 STATUS current 1651 DESCRIPTION 1652 "An entry in this table represents a set of resources 1653 for an MPLS tunnel. An entry can be created by a 1654 network administrator or by an SNMP agent as 1655 instructed by any MPLS signalling protocol." 1656 INDEX { mplsTunnelResourceIndex } 1657 ::= { mplsTunnelResourceTable 1 } 1659 MplsTunnelResourceEntry ::= SEQUENCE { 1660 mplsTunnelResourceIndex Unsigned32, 1661 mplsTunnelResourceMaxRate MplsBitRate, 1662 mplsTunnelResourceMeanRate MplsBitRate, 1663 mplsTunnelResourceMaxBurstSize MplsBurstSize, 1664 mplsTunnelResourceMeanBurstSize MplsBurstSize, 1665 mplsTunnelResourceExBurstSize MplsBurstSize, 1666 mplsTunnelResourceFrequency INTEGER, 1667 mplsTunnelResourceWeight Unsigned32, 1668 mplsTunnelResourceRowStatus RowStatus, 1669 mplsTunnelResourceStorageType StorageType 1670 } 1672 mplsTunnelResourceIndex OBJECT-TYPE 1673 SYNTAX Unsigned32 (1..2147483647) 1674 MAX-ACCESS not-accessible 1675 STATUS current 1676 DESCRIPTION 1677 "Uniquely identifies this row." 1678 ::= { mplsTunnelResourceEntry 1 } 1680 mplsTunnelResourceMaxRate OBJECT-TYPE 1681 SYNTAX MplsBitRate 1682 UNITS "bits per second" 1683 MAX-ACCESS read-create 1684 STATUS current 1685 DESCRIPTION 1686 "The maximum rate in bits/second. Note that setting 1687 mplsTunnelResourceMaxRate, 1688 mplsTunnelResourceMeanRate, and 1689 mplsTunnelResourceMaxBurstSize to 0 indicates best- 1690 effort treatment. 1691 This object is copied to an instance of 1692 mplsTrafficParamMaxRate in mplsTrafficParamTable 1693 the OID of which is copied into the corresponding 1694 mplsInSegmentTrafficParamPtr." 1695 REFERENCE 1696 "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS 1697 Label Switch Router Management Information Base, 1698 Internet Draft , 1699 June 2003." 1700 ::= { mplsTunnelResourceEntry 2 } 1702 mplsTunnelResourceMeanRate OBJECT-TYPE 1703 SYNTAX MplsBitRate 1704 UNITS "bits per second" 1705 MAX-ACCESS read-create 1706 STATUS current 1707 DESCRIPTION 1708 "This object is copied into an instance of 1709 mplsTrafficParamMeanRate in the 1710 mplsTrafficParamTable. The OID of this table entry 1711 is then copied into the corresponding 1712 mplsInSegmentTrafficParamPtr. 1714 When resource allocation is performed as requested 1715 by this TSpec object, it is copied into an entry in 1716 mplsTrafficParamTable [LSRMIB]: 1717 mplsTunnelInMeanRate to mplsTrafficParamMeanRate. 1718 The OID of this entry is copied to 1719 mplsInSegmentTrafficParamPtr of the corresponding 1720 in-segment entry." 1721 REFERENCE 1722 "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS 1723 Label Switch Router Management Information Base, 1724 Internet Draft , 1725 June 2003." 1726 ::= { mplsTunnelResourceEntry 3 } 1728 mplsTunnelResourceMaxBurstSize OBJECT-TYPE 1729 SYNTAX MplsBurstSize 1730 UNITS "bytes" 1731 MAX-ACCESS read-create 1732 STATUS current 1733 DESCRIPTION 1734 "The maximum burst size in bytes. This object is 1735 copied to mplsInSegmentMaxBurstSize of the 1736 corresponding in-segment. 1738 When resource allocation is performed as requested 1739 by this TSpec object, it is copied into an entry in 1740 mplsTrafficParamTable [LSRMIB]: 1741 mplsTunnelInMaxBurstSize to 1742 mplsTrafficParamMaxBurstSize. The OID of this entry 1743 is copied to mplsInSegmentTrafficParamPtr of the 1744 corresponding in-segment entry." 1745 REFERENCE 1746 "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS 1747 Label Switch Router Management Information Base, 1748 Internet Draft , 1749 June 2003." 1750 ::= { mplsTunnelResourceEntry 4 } 1752 mplsTunnelResourceMeanBurstSize OBJECT-TYPE 1753 SYNTAX MplsBurstSize 1754 UNITS "bytes" 1755 MAX-ACCESS read-create 1756 STATUS current 1757 DESCRIPTION 1758 "The mean burst size in bytes. The implementations 1759 which do not implement this variable must return 0 1760 for this value and must not allow a user to set 1761 this value." 1762 ::= { mplsTunnelResourceEntry 5 } 1764 mplsTunnelResourceExBurstSize OBJECT-TYPE 1765 SYNTAX MplsBurstSize 1766 UNITS "bytes" 1767 MAX-ACCESS read-create 1768 STATUS current 1769 DESCRIPTION 1770 "The Excess burst size in bytes. The implementations 1771 which do not implement this variable must return 0 1772 for this value and must not allow a user to set 1773 this value." 1774 REFERENCE 1775 "CR-LDP Specification, Section 4.3." 1776 ::= { mplsTunnelResourceEntry 6 } 1778 mplsTunnelResourceFrequency OBJECT-TYPE 1779 SYNTAX INTEGER { 1780 unspecified(1), 1781 frequent(2), 1782 veryFrequent(3) 1783 } 1784 MAX-ACCESS read-create 1785 STATUS current 1786 DESCRIPTION 1787 "The granularity of the availability of committed 1788 rate. The implementations which do not implement 1789 this variable must return unspecified(1) for this 1790 value and must not allow a user to set this value." 1791 REFERENCE 1792 "CR-LDP Specification, Section 4.3." 1793 ::= { mplsTunnelResourceEntry 7 } 1795 mplsTunnelResourceWeight OBJECT-TYPE 1796 SYNTAX Unsigned32(0..255) 1797 MAX-ACCESS read-create 1798 STATUS current 1799 DESCRIPTION 1800 "The relative weight for using excess bandwidth above 1801 its committed rate. The value of 0 means that 1802 weight is not applicable for the CR-LSP." 1803 REFERENCE 1804 "CR-LDP Specification, Section 4.3." 1805 ::= { mplsTunnelResourceEntry 8 } 1807 mplsTunnelResourceRowStatus OBJECT-TYPE 1808 SYNTAX RowStatus 1809 MAX-ACCESS read-create 1810 STATUS current 1811 DESCRIPTION 1812 "This variable is used to create, modify, and/or 1813 delete a row in this tabole. When a row in this 1814 table is in active(1) state, no objects in that row 1815 can be modified except mplsTunnelResourceRowStatus 1816 and mplsTunnelResourceStorageType." 1817 ::= { mplsTunnelResourceEntry 9 } 1819 mplsTunnelResourceStorageType OBJECT-TYPE 1820 SYNTAX StorageType 1821 MAX-ACCESS read-create 1822 STATUS current 1823 DESCRIPTION 1824 "This variable indicates the storage type for this 1825 object. If this variable is set to readOnly(5), 1826 and the corresponding entry is removed, then the 1827 agent must remove this row shortly thereafter 1828 [RFC2579]. 1830 Setting this object to permanent(4) indicates that 1831 this object should be restored automatically after 1832 failures. 1834 No objects are required to be writable for rows in 1835 this table with this object set to permanent(4). 1836 The default value is volatile(2)." 1837 DEFVAL { volatile } 1839 ::= { mplsTunnelResourceEntry 10 } 1841 -- End mplsTunnelResourceTable 1843 -- Tunnel Actual Route Hop table. 1845 mplsTunnelARHopTable OBJECT-TYPE 1846 SYNTAX SEQUENCE OF MplsTunnelARHopEntry 1847 MAX-ACCESS not-accessible 1848 STATUS current 1849 DESCRIPTION 1850 "The mplsTunnelARHopTable is used to indicate the 1851 hops, strict or loose, for an MPLS tunnel defined 1852 in mplsTunnelTable, as reported by the MPLS 1853 signalling protocol, for the outgoing direction of 1854 the tunnel. Each row in this table is indexed by 1855 mplsTunnelARHopListIndex. Each row also has a 1856 secondary index mplsTunnelARHopIndex, corresponding 1857 to the next hop that this row corresponds to. The 1858 first row in the table is the first hop after the 1859 origination point of the tunnel. In case we want 1860 to specify a particular interface on the 1861 originating LSR of an outgoing tunnel by which we 1862 want packets to exit the LSR, we specify this as 1863 the first hop for this tunnel in 1864 mplsTunnelARHopTable. 1866 Please note that since the information necessary to 1867 build entries within this table are not provided by 1868 some MPLS signalling protocols, implementation of 1869 this table is optional. Furthermore, since the 1870 information in this table is actually provided by 1871 the MPLS signalling protocol after the path has 1872 been set-up, the entries in this table are provided 1873 only for observation, and hence, all variables in 1874 this table are accessible exclusively as read- 1875 only." 1876 ::= { mplsTeObjects 7 } 1878 mplsTunnelARHopEntry OBJECT-TYPE 1879 SYNTAX MplsTunnelARHopEntry 1880 MAX-ACCESS not-accessible 1881 STATUS current 1882 DESCRIPTION 1883 "An entry in this table represents a tunnel hop. An 1884 entry is created by a network administrator for 1885 signaled ERLSP set up by an MPLS signalling 1886 protocol." 1887 INDEX { mplsTunnelARHopListIndex, mplsTunnelARHopIndex } 1888 ::= { mplsTunnelARHopTable 1 } 1890 MplsTunnelARHopEntry ::= SEQUENCE { 1891 mplsTunnelARHopListIndex MplsPathIndex, 1892 mplsTunnelARHopIndex MplsPathIndex, 1893 mplsTunnelARHopAddrType TeHopAddressType, 1894 mplsTunnelARHopIpAddr TeHopAddress, 1895 mplsTunnelARHopIpPrefixLen InetAddressPrefixLength, 1896 mplsTunnelARHopAsNumber TeHopAddressAS, 1897 mplsTunnelARHopAddrUnnum TeHopAddressUnnum, 1898 mplsTunnelARHopLspId MplsLSPID 1899 } 1901 mplsTunnelARHopListIndex OBJECT-TYPE 1902 SYNTAX MplsPathIndex 1903 MAX-ACCESS not-accessible 1904 STATUS current 1905 DESCRIPTION 1906 "Primary index into this table identifying a 1907 particular recorded hop list." 1908 ::= { mplsTunnelARHopEntry 1 } 1910 mplsTunnelARHopIndex OBJECT-TYPE 1911 SYNTAX MplsPathIndex 1912 MAX-ACCESS not-accessible 1913 STATUS current 1914 DESCRIPTION 1915 "Secondary index into this table identifying the 1916 particular hop." 1917 ::= { mplsTunnelARHopEntry 2 } 1919 mplsTunnelARHopAddrType OBJECT-TYPE 1920 SYNTAX TeHopAddressType 1921 MAX-ACCESS read-only 1922 STATUS current 1923 DESCRIPTION 1924 "Denotes the address type of this tunnel hop." 1925 DEFVAL { ipv4 } 1926 ::= { mplsTunnelARHopEntry 3 } 1928 mplsTunnelARHopIpAddr OBJECT-TYPE 1929 SYNTAX TeHopAddress 1930 MAX-ACCESS read-only 1931 STATUS current 1932 DESCRIPTION 1933 "If mplsTunnelARHopAddrType is set to ipv4(1) or 1934 ipv6(2), then this value will contain respectively 1935 the IPv4 address or the IPv6 address of this hop. 1936 Otherwise the agent should set this object to zero- 1937 length string and the manager should ignore this." 1938 ::= { mplsTunnelARHopEntry 4 } 1940 mplsTunnelARHopIpPrefixLen OBJECT-TYPE 1941 SYNTAX InetAddressPrefixLength 1942 MAX-ACCESS read-only 1943 STATUS current 1944 DESCRIPTION 1945 "If mplsTunnelARHopAddrType is set to ipv4(1) or 1946 ipv6(2), then this value will contain an 1947 appropriate prefix length for the IP address in 1948 object mplsTunnelARHopIpAddr. Otherwise a 1949 management entity SHOULD set this object to 0 and 1950 an agent MUST ignore it." 1951 ::= { mplsTunnelARHopEntry 5 } 1953 mplsTunnelARHopAsNumber OBJECT-TYPE 1954 SYNTAX TeHopAddressAS 1955 MAX-ACCESS read-only 1956 STATUS current 1957 DESCRIPTION 1958 "If mplsTunnelARHopAddrType is set to asnumber(3), 1959 then this value will contain the AS number of this 1960 hop. Otherwise the agent should set this object to 1961 zero-length string and the manager should ignore 1962 this." 1963 ::= { mplsTunnelARHopEntry 6 } 1965 mplsTunnelARHopAddrUnnum OBJECT-TYPE 1966 SYNTAX TeHopAddressUnnum 1967 MAX-ACCESS read-only 1968 STATUS current 1969 DESCRIPTION 1970 "If mplsTunnelARHopAddrType is set to unnum(4), then 1971 this value will contain the interface identifier of 1972 the unnumbered interface for this hop. Otherwise 1973 the agent should set this object to zero-length 1974 string and the manager should ignore this." 1975 ::= { mplsTunnelARHopEntry 7 } 1977 mplsTunnelARHopLspId OBJECT-TYPE 1978 SYNTAX MplsLSPID 1979 MAX-ACCESS read-only 1980 STATUS current 1981 DESCRIPTION 1982 "If mplsTunnelARHopAddrType is set to lspid(5), then 1983 this value will contain the LSP ID of this hop. 1984 This object is otherwise insignificant and should 1985 contain a value of 0 to indicate this fact." 1986 ::= { mplsTunnelARHopEntry 8 } 1988 -- End of mplsTunnelARHopTable 1990 -- Tunnel Computed Hop table. 1992 mplsTunnelCHopTable OBJECT-TYPE 1993 SYNTAX SEQUENCE OF MplsTunnelCHopEntry 1994 MAX-ACCESS not-accessible 1995 STATUS current 1996 DESCRIPTION 1997 "The mplsTunnelCHopTable is used to indicate the 1998 hops, strict or loose, for an MPLS tunnel defined 1999 in mplsTunnelTable, as computed by a constraint- 2000 based routing protocol, based on the 2001 mplsTunnelHopTable for the outgoing direction of 2002 the tunnel. Each row in this table is indexed by 2003 mplsTunnelCHopListIndex. Each row also has a 2004 secondary index mplsTunnelCHopIndex, corresponding 2005 to the next hop that this row corresponds to. The 2006 first row in the table is the first hop after the 2007 origination point of the tunnel. In case we want 2008 to specify a particular interface on the 2009 originating LSR of an outgoing tunnel by which we 2010 want packets to exit the LSR, we specify this as 2011 the first hop for this tunnel in 2012 mplsTunnelCHopTable. 2014 Please note that since the information necessary to 2015 build entries within this table may not be 2016 supported by some LSRs, implementation of this 2017 table is optional. Furthermore, since the 2018 information in this table is actually provided by 2019 routing protocol after the path has been computed, 2020 the entries in this table are provided only for 2021 observation, and hence, all variables in this table 2022 are accessible exclusively as read-only." 2023 ::= { mplsTeObjects 8 } 2025 mplsTunnelCHopEntry OBJECT-TYPE 2026 SYNTAX MplsTunnelCHopEntry 2027 MAX-ACCESS not-accessible 2028 STATUS current 2029 DESCRIPTION 2030 "An entry in this table represents a tunnel hop. An 2031 entry in this table is created by a constraint- 2032 based routing protocol based on the hops specified 2033 in the corresponding mplsTunnelHopTable." 2034 INDEX { mplsTunnelCHopListIndex, mplsTunnelCHopIndex } 2035 ::= { mplsTunnelCHopTable 1 } 2037 MplsTunnelCHopEntry ::= SEQUENCE { 2038 mplsTunnelCHopListIndex MplsPathIndex, 2039 mplsTunnelCHopIndex MplsPathIndex, 2040 mplsTunnelCHopAddrType TeHopAddressType, 2041 mplsTunnelCHopIpAddr TeHopAddress, 2042 mplsTunnelCHopIpPrefixLen InetAddressPrefixLength, 2043 mplsTunnelCHopAsNumber TeHopAddressAS, 2044 mplsTunnelCHopAddrUnnum TeHopAddressUnnum, 2045 mplsTunnelCHopLspId MplsLSPID, 2046 mplsTunnelCHopType INTEGER 2047 } 2049 mplsTunnelCHopListIndex OBJECT-TYPE 2050 SYNTAX MplsPathIndex 2051 MAX-ACCESS not-accessible 2052 STATUS current 2053 DESCRIPTION 2054 "Primary index into this table identifying a 2055 particular computed hop list." 2056 ::= { mplsTunnelCHopEntry 1 } 2058 mplsTunnelCHopIndex OBJECT-TYPE 2059 SYNTAX MplsPathIndex 2060 MAX-ACCESS not-accessible 2061 STATUS current 2062 DESCRIPTION 2063 "Secondary index into this table identifying the 2064 particular hop." 2065 ::= { mplsTunnelCHopEntry 2 } 2067 mplsTunnelCHopAddrType OBJECT-TYPE 2068 SYNTAX TeHopAddressType 2069 MAX-ACCESS read-only 2070 STATUS current 2071 DESCRIPTION 2072 "Denotes the address type of this tunnel hop. Note 2073 that lspid(5) is a valid option only for tunnels 2074 signaled via CRLDP." 2075 DEFVAL { ipv4 } 2076 ::= { mplsTunnelCHopEntry 3 } 2078 mplsTunnelCHopIpAddr OBJECT-TYPE 2079 SYNTAX TeHopAddress 2080 MAX-ACCESS read-only 2081 STATUS current 2082 DESCRIPTION 2083 "If mplsTunnelCHopAddrType is set to ipv4(1) or 2084 ipv6(2), then this value will contain respectively 2085 the IPv4 address or the IPv6 address of this hop. 2086 Otherwise the agent should set this object to zero- 2087 length string and the manager should ignore this." 2088 ::= { mplsTunnelCHopEntry 4 } 2090 mplsTunnelCHopIpPrefixLen OBJECT-TYPE 2091 SYNTAX InetAddressPrefixLength 2092 MAX-ACCESS read-only 2093 STATUS current 2094 DESCRIPTION 2095 "If mplsTunnelCHopAddrType is set to ipv4(1) or 2096 ipv6(2), then this value will contain an 2097 appropriate prefix length for the IP address in 2098 object mplsTunnelCHopIpAddr. Otherwise a management 2099 entity SHOULD set this object to 0 and an agent 2100 MUST ignore it. " 2101 ::= { mplsTunnelCHopEntry 5 } 2103 mplsTunnelCHopAsNumber OBJECT-TYPE 2104 SYNTAX TeHopAddressAS 2105 MAX-ACCESS read-only 2106 STATUS current 2107 DESCRIPTION 2108 "If mplsTunnelCHopAddrType is set to asnumber(3), 2109 then this value will contain the AS number of this 2110 hop. Otherwise the agent should set this object to 2111 zero-length string and the manager should ignore 2112 this." 2113 ::= { mplsTunnelCHopEntry 6 } 2115 mplsTunnelCHopAddrUnnum OBJECT-TYPE 2116 SYNTAX TeHopAddressUnnum 2117 MAX-ACCESS read-only 2118 STATUS current 2119 DESCRIPTION 2120 "If mplsTunnelCHopAddrType is set to unnum(4), then 2121 this value will contain the unnumbered interface 2122 identifier of this hop. Otherwise the agent should 2123 set this object to zero-length string and the 2124 manager should ignore this." 2125 ::= { mplsTunnelCHopEntry 7 } 2127 mplsTunnelCHopLspId OBJECT-TYPE 2128 SYNTAX MplsLSPID 2129 MAX-ACCESS read-only 2130 STATUS current 2131 DESCRIPTION 2132 "If mplsTunnelCHopAddrType is set to lspid(5), then 2133 this value will contain the LSP ID of this hop. 2134 This object is otherwise insignificant and should 2135 contain a value of 0 to indicate this fact." 2136 ::= { mplsTunnelCHopEntry 8 } 2138 mplsTunnelCHopType OBJECT-TYPE 2139 SYNTAX INTEGER { 2140 strict(1), 2141 loose(2) 2142 } 2143 MAX-ACCESS read-only 2144 STATUS current 2145 DESCRIPTION 2146 "Denotes whether this is tunnel hop is routed in a 2147 strict or loose fashion." 2148 ::= { mplsTunnelCHopEntry 9 } 2150 -- End of mplsTunnelCHopTable 2152 -- MPLS Tunnel Performance Table. 2154 mplsTunnelPerfTable OBJECT-TYPE 2155 SYNTAX SEQUENCE OF MplsTunnelPerfEntry 2156 MAX-ACCESS not-accessible 2157 STATUS current 2158 DESCRIPTION 2159 "This table provides per-tunnel MPLS performance 2160 information." 2161 ::= { mplsTeObjects 9 } 2163 mplsTunnelPerfEntry OBJECT-TYPE 2164 SYNTAX MplsTunnelPerfEntry 2165 MAX-ACCESS not-accessible 2166 STATUS current 2167 DESCRIPTION 2168 "An entry in this table is created by the LSR for 2169 every tunnel. Its is an extension to 2170 mplsTunnelEntry." 2171 AUGMENTS { mplsTunnelEntry } 2172 ::= { mplsTunnelPerfTable 1 } 2174 MplsTunnelPerfEntry ::= SEQUENCE { 2175 mplsTunnelPerfPackets Counter32, 2176 mplsTunnelPerfHCPackets Counter64, 2177 mplsTunnelPerfErrors Counter32, 2178 mplsTunnelPerfBytes Counter32, 2179 mplsTunnelPerfHCBytes Counter64 2180 } 2182 mplsTunnelPerfPackets OBJECT-TYPE 2183 SYNTAX Counter32 2184 MAX-ACCESS read-only 2185 STATUS current 2186 DESCRIPTION 2187 "Number of packets forwarded by the tunnel." 2188 ::= { mplsTunnelPerfEntry 1 } 2190 mplsTunnelPerfHCPackets OBJECT-TYPE 2191 SYNTAX Counter64 2192 MAX-ACCESS read-only 2193 STATUS current 2194 DESCRIPTION 2195 "High capacity counter for number of packets 2196 forwarded by the tunnel." 2197 ::= { mplsTunnelPerfEntry 2 } 2199 mplsTunnelPerfErrors OBJECT-TYPE 2200 SYNTAX Counter32 2201 MAX-ACCESS read-only 2202 STATUS current 2203 DESCRIPTION 2204 "Number of packets with errors." 2205 ::= { mplsTunnelPerfEntry 3 } 2207 mplsTunnelPerfBytes OBJECT-TYPE 2208 SYNTAX Counter32 2209 MAX-ACCESS read-only 2210 STATUS current 2211 DESCRIPTION 2212 "Number of bytes forwarded by the tunnel." 2213 ::= { mplsTunnelPerfEntry 4 } 2215 mplsTunnelPerfHCBytes OBJECT-TYPE 2216 SYNTAX Counter64 2217 MAX-ACCESS read-only 2218 STATUS current 2219 DESCRIPTION 2220 "High capacity counter for number of bytes forwarded 2221 by the tunnel." 2222 ::= { mplsTunnelPerfEntry 5 } 2224 -- End of mplsTunnelPerfTable 2226 -- CR-LDP Tunnel Resource Table 2228 mplsTunnelCRLDPResTable OBJECT-TYPE 2229 SYNTAX SEQUENCE OF MplsTunnelCRLDPResEntry 2230 MAX-ACCESS not-accessible 2231 STATUS current 2232 DESCRIPTION 2233 "The mplsTunnelCRLDPResTable allows a manager to 2234 specify which CR-LDP-specific resources are desired 2235 for an MPLS tunnel if that tunnel is signaled using 2236 CR-LDP. Note that these attributes are in addition 2237 to those specified in mplsTunnelResourceTable. This 2238 table also allows several tunnels to point to a 2239 single entry in this table, implying that these 2240 tunnels should share resources." 2241 ::= { mplsTeObjects 10 } 2243 mplsTunnelCRLDPResEntry OBJECT-TYPE 2244 SYNTAX MplsTunnelCRLDPResEntry 2245 MAX-ACCESS not-accessible 2246 STATUS current 2247 DESCRIPTION 2248 "An entry in this table represents a set of resources 2249 for an MPLS tunnel established using CRLDP 2250 (mplsTunnelSignallingProto equal to crldp (3)). An 2251 entry can be created by a network administrator or 2252 by an SNMP agent as instructed by any MPLS 2253 signalling protocol." 2254 INDEX { mplsTunnelResourceIndex } 2255 ::= { mplsTunnelCRLDPResTable 1 } 2257 MplsTunnelCRLDPResEntry ::= SEQUENCE { 2258 mplsTunnelCRLDPResMeanBurstSize MplsBurstSize, 2259 mplsTunnelCRLDPResExBurstSize MplsBurstSize, 2260 mplsTunnelCRLDPResFrequency INTEGER, 2261 mplsTunnelCRLDPResWeight Unsigned32, 2262 mplsTunnelCRLDPResFlags Unsigned32, 2263 mplsTunnelCRLDPResRowStatus RowStatus, 2264 mplsTunnelCRLDPResStorageType StorageType 2265 } 2267 mplsTunnelCRLDPResMeanBurstSize OBJECT-TYPE 2268 SYNTAX MplsBurstSize 2269 UNITS "bytes" 2270 MAX-ACCESS read-create 2271 STATUS current 2272 DESCRIPTION 2273 "The mean burst size in bytes." 2274 ::= { mplsTunnelCRLDPResEntry 2 } 2276 mplsTunnelCRLDPResExBurstSize OBJECT-TYPE 2277 SYNTAX MplsBurstSize 2278 UNITS "bytes" 2279 MAX-ACCESS read-create 2280 STATUS current 2281 DESCRIPTION 2282 "The Excess burst size in bytes." 2283 REFERENCE 2284 "CR-LDP Specification, Section 4.3." 2285 ::= { mplsTunnelCRLDPResEntry 3 } 2287 mplsTunnelCRLDPResFrequency OBJECT-TYPE 2288 SYNTAX INTEGER { 2289 unspecified(1), 2290 frequent(2), 2291 veryFrequent(3) 2292 } 2293 MAX-ACCESS read-create 2294 STATUS current 2295 DESCRIPTION 2296 "The granularity of the availability of committed 2297 rate." 2298 REFERENCE 2299 "CR-LDP Specification, Section 4.3." 2300 ::= { mplsTunnelCRLDPResEntry 4 } 2302 mplsTunnelCRLDPResWeight OBJECT-TYPE 2303 SYNTAX Unsigned32(0..255) 2304 MAX-ACCESS read-create 2305 STATUS current 2306 DESCRIPTION 2307 "The relative weight for using excess bandwidth above 2308 its committed rate. The value of 0 means that 2309 weight is not applicable for the CR-LSP." 2310 REFERENCE 2311 "CR-LDP Specification, Section 4.3." 2312 DEFVAL { 0 } 2313 ::= { mplsTunnelCRLDPResEntry 5 } 2315 mplsTunnelCRLDPResFlags OBJECT-TYPE 2316 SYNTAX Unsigned32 (0..63) 2317 MAX-ACCESS read-create 2318 STATUS current 2319 DESCRIPTION 2320 "The value of the 1 byte Flags conveyed as part of 2321 the traffic parameters during the establishment of 2322 the CRLSP. The bits in this object are to be 2323 interpreted as follows. 2325 +--+--+--+--+--+--+--+--+ 2326 | Res |F6|F5|F4|F3|F2|F1| 2327 +--+--+--+--+--+--+--+--+ 2329 Res - These bits are reserved. Zero on transmission. 2330 Ignored on receipt. 2331 F1 - Corresponds to the PDR. 2332 F2 - Corresponds to the PBS. 2333 F3 - Corresponds to the CDR. 2334 F4 - Corresponds to the CBS. 2335 F5 - Corresponds to the EBS. 2336 F6 - Corresponds to the Weight. 2338 Each flag if is a Negotiable Flag corresponding to a 2339 Traffic Parameter. The Negotiable Flag value zero 2340 denotes Not Negotiable and value one denotes 2341 Negotiable." 2342 REFERENCE 2343 "1. Section 4.3, Constraint-Based LSP Setup using 2344 LDP, Jamoussi (Editor), RFC 3212, January 2002" 2345 DEFVAL { 0 } 2346 ::= { mplsTunnelCRLDPResEntry 6 } 2348 mplsTunnelCRLDPResRowStatus OBJECT-TYPE 2349 SYNTAX RowStatus 2350 MAX-ACCESS read-create 2351 STATUS current 2352 DESCRIPTION 2353 "This variable is used to create, modify, and/or 2354 delete a row in this tabole. When a row in this 2355 table is in active(1) state, no objects in that row 2356 can be modified except mplsTunnelCRLDPResRowStatus 2357 and mplsTunnelCRLDPResStorageType." 2358 ::= { mplsTunnelCRLDPResEntry 7 } 2360 mplsTunnelCRLDPResStorageType OBJECT-TYPE 2361 SYNTAX StorageType 2362 MAX-ACCESS read-create 2363 STATUS current 2364 DESCRIPTION 2365 "This variable indicates the storage type for this 2366 object. If this variable is set to readOnly(5), 2367 and the corresponding entry is removed, then the 2368 agent must remove this row shortly thereafter 2369 [RFC2579]. 2371 Setting this object to permanent(4) indicates that 2372 this object should be restored automatically after 2373 failures. 2375 No objects are required to be writable for rows in 2376 this table with this object set to permanent(4). 2377 The default value is volatile(2)." 2378 DEFVAL { volatile } 2379 ::= { mplsTunnelCRLDPResEntry 8 } 2381 -- Notifications. 2383 mplsTunnelNotificationEnable OBJECT-TYPE 2384 SYNTAX TruthValue 2385 MAX-ACCESS read-write 2386 STATUS current 2387 DESCRIPTION 2388 "If this object is true, then it enables the 2389 generation of mplsTunnelUp and mplsTunnelDown 2390 traps, otherwise these traps are not emitted." 2391 DEFVAL { false } 2392 ::= { mplsTeObjects 11 } 2394 mplsTunnelUp NOTIFICATION-TYPE 2395 OBJECTS { 2396 mplsTunnelAdminStatus, 2397 mplsTunnelOperStatus 2398 } 2399 STATUS current 2400 DESCRIPTION 2401 "This notification is generated when a 2402 mplsTunnelOperStatus object for one of the 2403 configured tunnels is about to leave the down state 2404 and transition into some other state (but not into 2405 the notPresent state). This other state is 2406 indicated by the included value of 2407 mplsTunnelOperStatus." 2408 ::= { mplsTeNotifications 1 } 2410 mplsTunnelDown NOTIFICATION-TYPE 2411 OBJECTS { 2412 mplsTunnelAdminStatus, 2413 mplsTunnelOperStatus 2414 } 2415 STATUS current 2416 DESCRIPTION 2417 "This notification is generated when a 2418 mplsTunnelOperStatus object for one of the 2419 configured tunnels is about to enter the down state 2420 from some other state (but not from the notPresent 2421 state). This other state is indicated by the 2422 included value of mplsTunnelOperStatus." 2423 ::= { mplsTeNotifications 2 } 2425 mplsTunnelRerouted NOTIFICATION-TYPE 2426 OBJECTS { 2427 mplsTunnelAdminStatus, 2428 mplsTunnelOperStatus 2429 } 2430 STATUS current 2431 DESCRIPTION 2432 "This notification is generated when a tunnel is 2433 rerouted. If the actual path is used, then this 2434 tunnel's entry MAY contain the new path for this 2435 tunnel some time after this trap is issued by the 2436 agent." 2437 ::= { mplsTeNotifications 3 } 2439 mplsTunnelReoptimized NOTIFICATION-TYPE 2440 OBJECTS { 2441 mplsTunnelAdminStatus, 2442 mplsTunnelOperStatus 2443 } 2444 STATUS current 2445 DESCRIPTION 2446 "This notification is generated when a tunnel is 2447 reoptimized. If the actual path is used, then this 2448 tunnel's entry MAY contain the new path for this 2449 tunnel some time after this trap is issued by the 2450 agent." 2451 ::= { mplsTeNotifications 4 } 2453 -- End of notifications. 2455 -- Module compliance. 2457 mplsTeGroups 2458 OBJECT IDENTIFIER ::= { mplsTeConformance 1 } 2460 mplsTeCompliances 2461 OBJECT IDENTIFIER ::= { mplsTeConformance 2 } 2463 -- Compliance requirement for fully compliant implementations. 2465 mplsTeModuleFullCompliance MODULE-COMPLIANCE 2466 STATUS current 2467 DESCRIPTION 2468 "Compliance statement for agents that provide full 2469 support the MPLS-TE-STD-MIB module." 2471 MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863. 2472 MANDATORY-GROUPS { 2473 ifGeneralInformationGroup, 2474 ifCounterDiscontinuityGroup 2475 } 2477 MODULE -- this module 2479 -- The mandatory group has to be implemented by all 2480 -- LSRs that originate/terminate ESLSPs/tunnels. 2481 -- In addition, depending on the type of tunnels 2482 -- supported, other groups become mandatory as 2483 -- explained below. 2485 MANDATORY-GROUPS { 2486 mplsTunnelGroup, 2487 mplsTunnelScalarGroup, 2488 mplsTeNotificationGroup 2489 } 2491 GROUP mplsTunnelManualGroup 2492 DESCRIPTION 2493 "This group is mandatory for devices which support 2494 manual configuration of tunnels, in addition to 2495 mplsTunnelGroup. The following constraints apply: 2496 mplsTunnelSignallingProto should be at least read- 2497 only with a value of none(1)." 2499 GROUP mplsTunnelSignaledGroup 2500 DESCRIPTION 2501 "This group is mandatory for devices which support 2502 signaled tunnel set up, in addition to 2503 mplsTunnelGroup. The following constraints apply: 2504 mplsTunnelSignallingProto should be at least read- 2505 only returning a value of ldp(2), or rsvp(3)." 2507 GROUP mplsTunnelIsNotIntfcGroup 2508 DESCRIPTION 2509 "This group is mandatory for devices which support 2510 tunnels that are not interfaces, in addition to 2511 mplsTunnelGroup. The following constraints apply: 2512 mplsTunnelIsIf must at least be read-only 2513 returning false(1)." 2515 GROUP mplsTunnelIsIntfcGroup 2516 DESCRIPTION 2517 "This group is mandatory for devices which support 2518 tunnels that are interfaces, in addition to 2519 mplsTunnelGroup. The following constraints apply: 2520 mplsTunnelIsIf must at least be read-only 2521 returning true(2)." 2523 GROUP mplsTunnelCRLDPResOptionalGroup 2524 DESCRIPTION 2525 "Objects in this group are optional except for 2526 implementations supporting the CR-LDP protocol for 2527 signalling of TE tunnels." 2529 -- mplsTunnelTable 2531 OBJECT mplsTunnelIsIf 2532 MIN-ACCESS read-only 2533 DESCRIPTION 2534 "Write access is not required." 2536 OBJECT mplsTunnelSignallingProto 2537 MIN-ACCESS read-only 2538 DESCRIPTION 2539 "Write access is not required." 2541 OBJECT mplsTunnelAdminStatus 2542 SYNTAX INTEGER { up (1), down (2) } 2543 MIN-ACCESS read-only 2544 DESCRIPTION 2545 "Only up and down states must be supported. Write 2546 access is not required." 2548 OBJECT mplsTunnelOperStatus 2549 SYNTAX INTEGER { up (1), down (2) } 2550 DESCRIPTION 2551 "Only up and down states must be supported. Write 2552 access is not required." 2554 OBJECT mplsTunnelRowStatus 2555 SYNTAX INTEGER { 2556 active(1), 2557 notInService(2), 2558 createAndGo(4), 2559 destroy(6) 2560 } 2561 MIN-ACCESS read-only 2562 DESCRIPTION 2563 "The notReady(3) and createAndWait(5) states need 2564 not be supported. Write access is not required." 2566 OBJECT mplsTunnelStorageType 2567 SYNTAX INTEGER { other(1) } 2568 DESCRIPTION 2569 "Only other (1) needs to be supported." 2571 OBJECT mplsTunnelRole 2572 SYNTAX INTEGER { head(1) } 2573 MIN-ACCESS read-only 2574 DESCRIPTION 2575 "Only support for head is required." 2577 ::= { mplsTeCompliances 1 } 2579 -- Compliance requirement for read-only implementations. 2581 mplsTeModuleReadOnlyCompliance MODULE-COMPLIANCE 2582 STATUS current 2583 DESCRIPTION 2584 "Compliance requirement for implementations that only 2585 provide read-only support for MPLS-TE-STD-MIB. 2586 Such devices can then be monitored but cannot be 2587 configured using this MIB modules." 2589 MODULE -- this module 2591 -- mplsTunnelTable 2593 MANDATORY-GROUPS { 2594 mplsTunnelGroup, 2595 mplsTunnelManualGroup, 2596 mplsTunnelScalarGroup, 2597 mplsTunnelIsNotIntfcGroup, 2598 mplsTunnelCRLDPResOptionalGroup 2599 } 2601 GROUP mplsTunnelSignaledGroup 2602 DESCRIPTION 2603 "This group is mandatory for devices which support 2604 signaled tunnel set up, in addition to 2605 mplsTunnelGroup. The following constraints apply: 2606 mplsTunnelSignallingProto should be at least read- 2607 only returning a value of ldp(2), or rsvp(3)." 2609 -- mplsTunnelTable 2610 OBJECT mplsTunnelName 2611 MIN-ACCESS read-only 2612 DESCRIPTION 2613 "Write access is not required." 2615 OBJECT mplsTunnelDescr 2616 MIN-ACCESS read-only 2617 DESCRIPTION 2618 "Write access is not required." 2620 OBJECT mplsTunnelIsIf 2621 MIN-ACCESS read-only 2622 DESCRIPTION 2623 "Write access is not required." 2625 OBJECT mplsTunnelIfIndex 2626 DESCRIPTION 2627 "Write access is not required." 2629 OBJECT mplsTunnelXCPointer 2630 MIN-ACCESS read-only 2631 DESCRIPTION 2632 "Write access is not required." 2634 OBJECT mplsTunnelSignallingProto 2635 MIN-ACCESS read-only 2636 DESCRIPTION 2637 "Write access is not required." 2639 OBJECT mplsTunnelSetupPrio 2640 MIN-ACCESS read-only 2641 DESCRIPTION 2642 "Write access is not required." 2644 OBJECT mplsTunnelHoldingPrio 2645 MIN-ACCESS read-only 2646 DESCRIPTION 2647 "Write access is not required." 2649 OBJECT mplsTunnelSessionAttributes 2650 MIN-ACCESS read-only 2651 DESCRIPTION 2652 "Write access is not required." 2654 OBJECT mplsTunnelLocalProtectInUse 2655 MIN-ACCESS read-only 2656 DESCRIPTION 2657 "Write access is not required." 2659 OBJECT mplsTunnelResourcePointer 2660 MIN-ACCESS read-only 2661 DESCRIPTION 2662 "Write access is not required." 2664 OBJECT mplsTunnelInstancePriority 2665 MIN-ACCESS read-only 2666 DESCRIPTION 2667 "Write access is not required." 2669 OBJECT mplsTunnelHopTableIndex 2670 MIN-ACCESS read-only 2671 DESCRIPTION 2672 "Write access is not required." 2674 OBJECT mplsTunnelIncludeAnyAffinity 2675 MIN-ACCESS read-only 2676 DESCRIPTION 2677 "Write access is not required." 2679 OBJECT mplsTunnelIncludeAllAffinity 2680 MIN-ACCESS read-only 2681 DESCRIPTION 2682 "Write access is not required." 2684 OBJECT mplsTunnelExcludeAllAffinity 2685 MIN-ACCESS read-only 2686 DESCRIPTION 2687 "Write access is not required." 2689 OBJECT mplsTunnelPathInUse 2690 MIN-ACCESS read-only 2691 DESCRIPTION 2692 "Write access is not required." 2694 OBJECT mplsTunnelRole 2695 MIN-ACCESS read-only 2696 DESCRIPTION 2697 "Write access is not required." 2699 OBJECT mplsTunnelAdminStatus 2700 SYNTAX INTEGER { up (1), down (2) } 2701 MIN-ACCESS read-only 2702 DESCRIPTION 2703 "Only up and down states must be supported. Write 2704 access is not required." 2706 OBJECT mplsTunnelOperStatus 2707 SYNTAX INTEGER { up (1), down (2) } 2708 DESCRIPTION 2709 "Only up and down states must be supported. Write 2710 access is not required." 2712 OBJECT mplsTunnelRowStatus 2713 SYNTAX INTEGER { 2714 active(1), 2715 notInService(2), 2716 createAndGo(4), 2717 destroy(6) 2718 } 2719 MIN-ACCESS read-only 2720 DESCRIPTION 2721 "The notReady(3) and createAndWait(5) states need 2722 not be supported. Write access is not required." 2724 OBJECT mplsTunnelStorageType 2725 SYNTAX INTEGER { other(1) } 2726 DESCRIPTION 2727 "Only other (1) needs to be supported." 2729 -- mplsTunnelHopTable 2731 OBJECT mplsTunnelHopAddrType 2732 MIN-ACCESS read-only 2733 DESCRIPTION 2734 "Write access is not required." 2736 OBJECT mplsTunnelHopIpAddr 2737 MIN-ACCESS read-only 2738 DESCRIPTION 2739 "Write access is not required." 2741 OBJECT mplsTunnelHopIpPrefixLen 2742 MIN-ACCESS read-only 2743 DESCRIPTION 2744 "Write access is not required." 2746 OBJECT mplsTunnelHopAddrUnnum 2747 MIN-ACCESS read-only 2748 DESCRIPTION 2749 "Write access is not required." 2751 OBJECT mplsTunnelHopAsNumber 2752 MIN-ACCESS read-only 2753 DESCRIPTION 2754 "Write access is not required." 2756 OBJECT mplsTunnelHopLspId 2757 MIN-ACCESS read-only 2758 DESCRIPTION 2759 "Write access is not required." 2761 OBJECT mplsTunnelHopType 2762 SYNTAX INTEGER { strict(1) } 2763 MIN-ACCESS read-only 2764 DESCRIPTION 2765 "loose(2) need not be supported. Write access is 2766 not required." 2768 OBJECT mplsTunnelHopInclude 2769 MIN-ACCESS read-only 2770 DESCRIPTION 2771 "Write access is not required." 2773 OBJECT mplsTunnelHopPathOptionName 2774 MIN-ACCESS read-only 2775 DESCRIPTION 2776 "Write access is not required." 2778 OBJECT mplsTunnelHopEntryPathComp 2779 MIN-ACCESS read-only 2780 DESCRIPTION 2781 "Write access is not required." 2783 OBJECT mplsTunnelHopRowStatus 2784 SYNTAX INTEGER { 2785 active(1), 2786 notInService(2), 2787 createAndGo(4), 2788 destroy(6) 2789 } 2790 MIN-ACCESS read-only 2791 DESCRIPTION 2792 "The notReady(3) and createAndWait(5) states need 2793 not be supported. Write access is not required." 2795 OBJECT mplsTunnelHopStorageType 2796 SYNTAX INTEGER { other(1) } 2797 DESCRIPTION 2798 "Only other (1) needs to be supported." 2800 -- mplsTunnelResourceTable 2801 OBJECT mplsTunnelResourceMaxRate 2802 MIN-ACCESS read-only 2803 DESCRIPTION 2804 "Write access is not required." 2806 OBJECT mplsTunnelResourceMeanRate 2807 MIN-ACCESS read-only 2808 DESCRIPTION 2809 "Write access is not required." 2811 OBJECT mplsTunnelResourceMaxBurstSize 2812 MIN-ACCESS read-only 2813 DESCRIPTION 2814 "Write access is not required." 2816 OBJECT mplsTunnelResourceMeanBurstSize 2817 MIN-ACCESS read-only 2818 DESCRIPTION 2819 "Write access is not required." 2821 OBJECT mplsTunnelResourceExBurstSize 2822 MIN-ACCESS read-only 2823 DESCRIPTION 2824 "Write access is not required." 2826 OBJECT mplsTunnelResourceFrequency 2827 MIN-ACCESS read-only 2828 DESCRIPTION 2829 "Write access is not required." 2831 OBJECT mplsTunnelResourceWeight 2832 MIN-ACCESS read-only 2833 DESCRIPTION 2834 "Write access is not required." 2836 OBJECT mplsTunnelResourceRowStatus 2837 SYNTAX INTEGER { 2838 active(1), 2839 notInService(2), 2840 createAndGo(4), 2841 destroy(6) 2842 } 2843 MIN-ACCESS read-only 2844 DESCRIPTION 2845 "The notReady(3) and createAndWait(5) states need 2846 not be supported. Write access is not required." 2848 OBJECT mplsTunnelResourceStorageType 2849 SYNTAX INTEGER { other(1) } 2850 DESCRIPTION 2851 "Only other (1) needs to be supported." 2853 -- mplsTunnelCRLDPResTable 2855 OBJECT mplsTunnelCRLDPResMeanBurstSize 2856 MIN-ACCESS read-only 2857 DESCRIPTION 2858 "Write access is not required." 2860 OBJECT mplsTunnelCRLDPResExBurstSize 2861 MIN-ACCESS read-only 2862 DESCRIPTION 2863 "Write access is not required." 2865 OBJECT mplsTunnelCRLDPResFrequency 2866 MIN-ACCESS read-only 2867 DESCRIPTION 2868 "Write access is not required." 2870 OBJECT mplsTunnelCRLDPResWeight 2871 MIN-ACCESS read-only 2872 DESCRIPTION 2873 "Write access is not required." 2875 OBJECT mplsTunnelCRLDPResFlags 2876 MIN-ACCESS read-only 2877 DESCRIPTION 2878 "Write access is not required." 2880 OBJECT mplsTunnelCRLDPResRowStatus 2881 SYNTAX INTEGER { 2882 active(1), 2883 notInService(2), 2884 createAndGo(4), 2885 destroy(6) 2886 } 2887 MIN-ACCESS read-only 2888 DESCRIPTION 2889 "The notReady(3) and createAndWait(5) states need 2890 not be supported. Write access is not required." 2892 OBJECT mplsTunnelCRLDPResStorageType 2893 SYNTAX INTEGER { other(1) } 2894 DESCRIPTION 2895 "Only other (1) needs to be supported." 2897 ::= { mplsTeCompliances 2 } 2899 -- Units of conformance. 2901 mplsTunnelGroup OBJECT-GROUP 2902 OBJECTS { 2903 mplsTunnelIndexNext, 2904 mplsTunnelName, 2905 mplsTunnelDescr, 2906 mplsTunnelOwner, 2907 mplsTunnelXCPointer, 2908 mplsTunnelIfIndex, 2909 mplsTunnelHopTableIndex, 2910 mplsTunnelARHopTableIndex, 2911 mplsTunnelCHopTableIndex, 2912 mplsTunnelAdminStatus, 2913 mplsTunnelOperStatus, 2914 mplsTunnelRowStatus, 2915 mplsTunnelNotificationEnable, 2916 mplsTunnelStorageType, 2917 mplsTunnelConfigured, 2918 mplsTunnelActive, 2919 mplsTunnelPrimaryInstance, 2920 mplsTunnelPrimaryUpTime, 2921 mplsTunnelPathChanges, 2922 mplsTunnelLastPathChange, 2923 mplsTunnelCreationTime, 2924 mplsTunnelStateTransitions, 2925 mplsTunnelIncludeAnyAffinity, 2926 mplsTunnelIncludeAllAffinity, 2927 mplsTunnelExcludeAllAffinity, 2928 mplsTunnelPerfPackets, 2929 mplsTunnelPerfHCPackets, 2930 mplsTunnelPerfErrors, 2931 mplsTunnelPerfBytes, 2932 mplsTunnelPerfHCBytes, 2933 mplsTunnelResourcePointer, 2934 mplsTunnelInstancePriority, 2935 mplsTunnelPathInUse, 2936 mplsTunnelRole, 2937 mplsTunnelTotalUpTime, 2938 mplsTunnelInstanceUpTime, 2939 mplsTunnelResourceIndexNext, 2940 mplsTunnelResourceMaxRate, 2941 mplsTunnelResourceMeanRate, 2942 mplsTunnelResourceMaxBurstSize, 2943 mplsTunnelResourceMeanBurstSize, 2944 mplsTunnelResourceExBurstSize, 2945 mplsTunnelResourceFrequency, 2946 mplsTunnelResourceWeight, 2947 mplsTunnelResourceRowStatus, 2948 mplsTunnelResourceStorageType, 2949 mplsTunnelARHopAddrType, 2950 mplsTunnelARHopIpAddr, 2951 mplsTunnelARHopIpPrefixLen, 2952 mplsTunnelARHopAsNumber, 2953 mplsTunnelARHopAddrUnnum, 2954 mplsTunnelARHopLspId, 2955 mplsTunnelCHopAddrType, 2956 mplsTunnelCHopIpAddr, 2957 mplsTunnelCHopIpPrefixLen, 2958 mplsTunnelCHopAsNumber, 2959 mplsTunnelCHopAddrUnnum, 2960 mplsTunnelCHopLspId, 2961 mplsTunnelCHopType 2962 } 2963 STATUS current 2964 DESCRIPTION 2965 "Necessary, but not sufficient, set of objects to 2966 implement tunnels. In addition, depending on the 2967 type of the tunnels supported (for example, 2968 manually configured or signaled, persistent or non- 2969 persistent, etc.), the following other groups 2970 defined below are mandatory: mplsTunnelManualGroup 2971 and/or mplsTunnelSignaledGroup, 2972 mplsTunnelIsNotIntfcGroup and/or 2973 mplsTunnelIsIntfcGroup." 2974 ::= { mplsTeGroups 1 } 2976 mplsTunnelManualGroup OBJECT-GROUP 2977 OBJECTS { mplsTunnelSignallingProto } 2978 STATUS current 2979 DESCRIPTION 2980 "Object(s) needed to implement manually configured 2981 tunnels." 2982 ::= { mplsTeGroups 2 } 2984 mplsTunnelSignaledGroup OBJECT-GROUP 2985 OBJECTS { 2986 mplsTunnelSetupPrio, 2987 mplsTunnelHoldingPrio, 2988 mplsTunnelSignallingProto, 2989 mplsTunnelLocalProtectInUse, 2990 mplsTunnelSessionAttributes, 2991 mplsTunnelHopListIndexNext, 2992 mplsTunnelHopAddrType, 2993 mplsTunnelHopIpAddr, 2994 mplsTunnelHopIpPrefixLen, 2995 mplsTunnelHopAddrUnnum, 2996 mplsTunnelHopAsNumber, 2997 mplsTunnelHopLspId, 2998 mplsTunnelHopType, 2999 mplsTunnelHopInclude, 3000 mplsTunnelHopPathOptionName, 3001 mplsTunnelHopEntryPathComp, 3002 mplsTunnelHopRowStatus, 3003 mplsTunnelHopStorageType 3004 } 3005 STATUS current 3006 DESCRIPTION 3007 "Objects needed to implement signaled tunnels." 3008 ::= { mplsTeGroups 3 } 3010 mplsTunnelScalarGroup OBJECT-GROUP 3011 OBJECTS { 3012 mplsTunnelConfigured, 3013 mplsTunnelActive, 3014 mplsTunnelTEDistProto, 3015 mplsTunnelMaxHops, 3016 mplsTunnelNotificationMaxRate 3017 } 3018 STATUS current 3019 DESCRIPTION 3020 "Scalar object needed to implement MPLS tunnels." 3021 ::= { mplsTeGroups 4 } 3023 mplsTunnelIsIntfcGroup OBJECT-GROUP 3024 OBJECTS { mplsTunnelIsIf } 3025 STATUS current 3026 DESCRIPTION 3027 "Objects needed to implement tunnels that are 3028 interfaces." 3029 ::= { mplsTeGroups 5 } 3031 mplsTunnelIsNotIntfcGroup OBJECT-GROUP 3032 OBJECTS { mplsTunnelIsIf } 3033 STATUS current 3034 DESCRIPTION 3035 "Objects needed to implement tunnels that are not 3036 interfaces." 3037 ::= { mplsTeGroups 6 } 3039 mplsTunnelCRLDPResOptionalGroup OBJECT-GROUP 3040 OBJECTS { 3041 mplsTunnelCRLDPResMeanBurstSize, 3042 mplsTunnelCRLDPResExBurstSize, 3043 mplsTunnelCRLDPResFrequency, 3044 mplsTunnelCRLDPResWeight, 3045 mplsTunnelCRLDPResFlags, 3046 mplsTunnelCRLDPResRowStatus, 3047 mplsTunnelCRLDPResStorageType 3048 } 3049 STATUS current 3050 DESCRIPTION 3051 "Set of objects implemented for resources applicable 3052 for tunnels signaled using CR-LDP." 3053 ::= { mplsTeGroups 7 } 3055 mplsTeNotificationGroup NOTIFICATION-GROUP 3056 NOTIFICATIONS { 3057 mplsTunnelUp, 3058 mplsTunnelDown, 3059 mplsTunnelRerouted, 3060 mplsTunnelReoptimized 3061 } 3062 STATUS current 3063 DESCRIPTION 3064 "Set of notifications implemented in this module. 3065 None is mandatory." 3066 ::= { mplsTeGroups 8 } 3068 END 3070 12. Security Considerations 3072 It is clear that this MIB module is potentially useful for 3073 monitoring of MPLS TE tunnels. This MIB module can also 3074 be used for configuration of certain objects, and anything 3075 that can be configured can be incorrectly configured, with 3076 potentially disastrous results. 3078 There are a number of management objects defined in this 3079 MIB module with a MAX-ACCESS clause of read-write and/or 3080 read-create. Such objects may be considered sensitive or 3081 vulnerable in some network environments. The support for 3082 SET operations in a non-secure environment without proper 3083 protection can have a negative effect on network 3084 operations. These are the tables and objects and their 3085 sensitivity/vulnerability: 3087 - the mplsTunnelTable, mplsTunnelHopTable, 3088 mplsTunnelResourceTable, mplsTunnelARHopTable, 3089 mplsTunnelCHopTable, and mplsTunnelCRLDPResTable 3090 collectively contain objects to provision MPLS 3091 tunnels, tunnel hops, and tunnel resources. 3092 Unauthorized access to objects in these tables, 3093 could result in disruption of traffic on the 3094 network. This is especially true if a tunnel has 3095 been established. The use of stronger mechanisms 3096 such as SNMPv3 security should be considered where 3097 possible. Specifically, SNMPv3 VACM and USM MUST 3098 be used with any v3 agent which implements this 3099 MIB. Administrators should consider whether read 3100 access to these objects should be allowed, since 3101 read access may be undesirable under certain 3102 circumstances. 3104 Some of the readable objects in this MIB module "i.e., 3105 objects with a MAX-ACCESS other than not-accessible" may 3106 be considered sensitive or vulnerable in some network 3107 environments. It is thus important to control even GET 3108 and/or NOTIFY access to these objects and possibly to even 3109 encrypt the values of these objects when sending them over 3110 the network via SNMP. These are the tables and objects 3111 and their sensitivity/vulnerability: 3113 - the mplsTunnelTable, mplsTunnelHopTable, 3114 mplsTunnelResourceTable, mplsTunnelARHopTable, 3115 mplsTunnelCHopTable, mplsTunnelPerfTable, and 3116 mplsTunnelCRLDPResTable collectively show the MPLE- 3117 TE tunnel network topology and its performance 3118 characteristics. If an Administrator does not want 3119 to reveal this information, then these tables 3120 should be considered sensitive/vulnerable. 3122 SNMP versions prior to SNMPv3 did not include adequate 3123 security. Even if the network itself is secure "for 3124 example by using IPSec", even then, there is no control as 3125 to who on the secure network is allowed to access and 3126 GET/SET "read/change/create/delete" the objects in this 3127 MIB module. 3129 It is RECOMMENDED that implementers consider the security 3130 features as provided by the SNMPv3 framework "see 3131 [RFC3410], section 8", including full support for the 3132 SNMPv3 cryptographic mechanisms "for authentication and 3133 privacy". 3135 Further, deployment of SNMP versions prior to SNMPv3 is 3136 NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy 3137 SNMPv3 and to enable cryptographic security. It is then a 3138 customer/operator responsibility to ensure that the SNMP 3139 entity giving access to an instance of this MIB module, is 3140 properly configured to give access to the objects only to 3141 those principals "users" that have legitimate. 3143 13. Acknowledgments 3145 We wish to thank Adrian Farrel, Bert Wijnen, Eric Gray, 3146 Joan Cucchiara, Patrick Kerharo, Paul Langille, Marcus 3147 Brunner, Mike MacFaden and Mike Piecuch for their comments 3148 on this document. 3150 14. References 3152 14.1. Normative References 3154 [RFC2119] S. Bradner, "Key Words for use in RFCs to 3155 Indicate Requirement Levels", RFC 2119, BCP 3156 14, March 1997. 3158 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, 3159 J., Case, J., Rose, M., and S. Waldbusser, 3160 "Structure of Management Information Version 3161 2 (SMIv2)", STD 58, RFC 2578, April 1999. 3163 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, 3164 J., Case, J., Rose, M., and S. Waldbusser, 3165 "Textual Conventions for SMIv2", STD 58, RFC 3166 2579, April 1999. 3168 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, 3169 J., Case, J., Rose, M., and S. Waldbusser, 3170 "Conformance Statements for SMIv2", STD 58, 3171 RFC 2580, April 1999. 3173 [RFC2702] Awduche, D., Malcolm, J., Agogbua, J., 3174 O'Dell, M., and J. McManus, "Requirements 3175 for Traffic Engineering Over MPLS", RFC 3176 2702, September 1999. 3178 [RFC2863] McCloghrie, K. and F. Kastenholtz, "The 3179 Interfaces Group MIB ", RFC 2863, June 2000. 3181 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 3182 "Multiprotocol Label Switching 3183 Architecture", RFC 3031, January 2001. 3185 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., 3186 Srinivasan, V., and G. Swallow, "RSVP-TE: 3187 Extensions to RSVP for LSP Tunnels", RFC 3188 3209, December 2001. 3190 [RFC3291] Daniele, M., Haberman, B., Routhier, S., and 3191 J. Schoenwaelder, "Textual Conventions for 3192 Internet Network Addresses", RFC 3291, May 3193 2002. 3195 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, 3196 "An Architecture for Describing Simple 3197 Network Management Protocol (SNMP) 3198 Management Frameworks", RFC 3411, December 3199 2002. 3201 [TCMIB] Nadeau, T. and J. Cucchiara (Editors), 3202 "Definition of Textual Conventions and 3203 OBJECT-IDENTITIES for Multi-Protocol Label 3204 Switching (MPLS) Management", Internet Draft 3205 , June 2003. 3207 [LSRMIB] Srinivasan, C., Viswanathan, A. and T. 3208 Nadeau, "MPLS Multiprotocol Label Switching 3209 (MPLS) Label Switch Router Management 3210 Information Base ", Internet Draft , June 2003. 3213 [CRLDP] B. Jamoussi (Editor), "Constraint-Based LSP 3214 Setup using LDP", RFC 3212, January 2002. 3216 14.2. Informative References 3218 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 3219 Identification of Management Information for 3220 TCP/IP-based Internets", RFC 1155, May 1990. 3222 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. 3223 Davin, "Simple Network Management Protocol", 3224 RFC 1157, May 1990. 3226 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB 3227 Definitions", RFC 1212, March 1991. 3229 [RFC1215] M. Rose, "A Convention for Defining Traps 3230 for use with the SNMP", RFC 1215, March 3231 1991. 3233 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. 3234 Waldbusser, "Introduction to Community-based 3235 SNMPv2", RFC 1901, January 1996. 3237 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. 3238 Waldbusser, "Protocol Operations for Version 3239 2 of the Simple Network Management Protocol 3240 (SNMPv2)", RFC 1905, January 1996. 3242 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. 3243 Waldbusser, "Transport Mappings for Version 3244 2 of the Simple Network Management Protocol 3245 (SNMPv2)", RFC 1906, January 1996. 3247 [RFC2026] S. Bradner, "The Internet Standards Process 3248 -- Revision 3", RFC 2026, October 1996. 3250 [RFC2401] Kent, S., and R. Atkinson, "Security 3251 Architecture for the Internet Protocol", RFC 3252 2401, November 1998. 3254 [RFC2572] Case, J., Harrington D., Presuhn R., and B. 3255 Wijnen, "Message Processing and Dispatching 3256 for the Simple Network Management Protocol 3257 (SNMP)", RFC 2572, April 1999. 3259 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 3260 Applications", RFC 2573, April 1999. 3262 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based 3263 Security Model (USM) for version 3 of the 3264 Simple Network Management Protocol 3265 (SNMPv3)", RFC 2574, April 1999. 3267 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, 3268 "View-based Access Control Model (VACM) for 3269 the Simple Network Management Protocol 3270 (SNMP)", RFC 2575, April 1999. 3272 [RFC3410] Case, J., Mundy, R., Partain, D., and B. 3273 Stewart, "Introduction and Applicability 3274 Statement for Internet Standard Management 3275 Framework", RFC 3410, December 2002. 3277 15. Authors' Addresses 3279 Cheenu Srinivasan 3280 Email: cheenu@alumni.princeton.edu 3282 Arun Viswanathan 3283 Force10 Networks, Inc. 3284 1440 McCarthy Blvd 3285 Milpitas, CA 95035 3286 Phone: +1-408-571-3516 3287 Email: arunv@force10networks.com 3289 Thomas D. Nadeau 3290 Cisco Systems, Inc. 3291 300 Apollo Drive 3292 Chelmsford, MA 01824 3293 Phone: +1-978-244-3051 3294 Email: tnadeau@cisco.com 3296 16. Full Copyright Statement 3298 Copyright (C) The Internet Society (2001). All Rights 3299 Reserved. 3301 This document and translations of it may be copied and 3302 furnished to others, and derivative works that comment on 3303 or otherwise explain it or assist in its implementation may 3304 be prepared, copied, published and distributed, in whole or 3305 in part, without restriction of any kind, provided that the 3306 above copyright notice and this paragraph are included on 3307 all such copies and derivative works. However, this 3308 document itself may not be modified in any way, such as by 3309 removing the copyright notice or references to the Internet 3310 Society or other Internet organizations, except as needed 3311 for the purpose of developing Internet standards in which 3312 case the procedures for copyrights defined in the Internet 3313 Standards process must be followed, or as required to 3314 translate it into languages other than English. 3316 The limited permissions granted above are perpetual and 3317 will not be revoked by the Internet Society or its 3318 successors or assigns. This document and the information 3319 contained herein is provided on an "AS IS" basis and THE 3320 INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE 3321 DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 3322 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 3323 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 3324 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 3325 PURPOSE. 3327 17. Intellectual Property Notice 3329 The IETF takes no position regarding the validity or scope 3330 of any intellectual property or other rights that might be 3331 claimed to pertain to the implementation or use of the 3332 technology described in this document or the extent to 3333 which any license under such rights might or might not be 3334 available; neither does it represent that it has made any 3335 effort to identify any such rights. Information on the 3336 IETF's procedures with respect to rights in standards-track 3337 and standards-related documentation can be found in BCP-11 3338 [RFC2028]. Copies of claims of rights made available for 3339 publication and any assurances of licenses to be made 3340 available, or the result of an attempt made to obtain a 3341 general license or permission for the use of such 3342 proprietary rights by implementors or users of this 3343 specification can be obtained from the IETF Secretariat. 3344 The IETF invites any interested party to bring to its 3345 attention any copyrights, patents or patent applications, 3346 or other proprietary rights that may cover technology that 3347 may be required to practice this standard. Please address 3348 the information to the IETF Executive Director.