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