idnits 2.17.1 draft-ietf-mpls-te-mib-14.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 (November 2003) is 7462 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 3278, but not defined == Missing Reference: 'MPLSTCMIB' is mentioned on line 3279, but not defined == Missing Reference: 'RFC2434' is mentioned on line 3284, but not defined ** Obsolete undefined reference: RFC 2434 (Obsoleted by RFC 5226) == Unused Reference: 'RFC2702' is defined on line 3143, but no explicit reference was found in the text == Unused Reference: 'RFC3209' is defined on line 3155, but no explicit reference was found in the text == Unused Reference: 'RFC3291' is defined on line 3160, but no explicit reference was found in the text == Unused Reference: 'RFC3411' is defined on line 3165, but no explicit reference was found in the text == Unused Reference: 'TCMIB' is defined on line 3171, but no explicit reference was found in the text == Unused Reference: 'RFC2026' is defined on line 3188, but no explicit reference was found in the text == Unused Reference: 'RFC2401' is defined on line 3191, 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: May 2004 4 Arun Viswanathan 5 Force10 Networks, Inc. 7 Thomas D. Nadeau 8 Cisco Systems, Inc. 10 November 2003 12 Multiprotocol Label Switching (MPLS) Traffic Engineering 13 Management Information Base 15 draft-ietf-mpls-te-mib-14.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 .............................. 62 70 13. Acknowledgments ...................................... 63 71 14. References ........................................... 64 72 14.1. Normative References ............................... 64 73 14.2. Informative References ............................. 65 74 15. Authors' Addresses ................................... 65 75 16. Full Copyright Statement ............................. 66 76 17. Intellectual Property Notice ......................... 66 77 18. IANA Considerations ................................ 67 78 18.1. IANA Considerations for MPLS-TE-STD-MIB ............ 67 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 "200310191200Z" -- 19 October 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 "200310191200Z" -- 19 October 2003 12:00:00 GMT 626 DESCRIPTION 627 "Initial draft version issued as part of RFC XXXX." 629 ::= { mplsStdMIB XXX } -- Please see IANA considerations section 630 -- the requested mplsStdMIB subId is 3. 632 -- Top level components of this MIB module. 634 -- traps 635 mplsTeNotifications OBJECT IDENTIFIER ::= { mplsTeStdMIB 0 } 636 -- tables, scalars 637 mplsTeScalars OBJECT IDENTIFIER ::= { mplsTeStdMIB 1 } 638 mplsTeObjects OBJECT IDENTIFIER ::= { mplsTeStdMIB 2 } 639 -- conformance 640 mplsTeConformance OBJECT IDENTIFIER ::= { mplsTeStdMIB 3 } 642 -- MPLS Tunnel scalars. 644 mplsTunnelConfigured OBJECT-TYPE 645 SYNTAX Unsigned32 646 MAX-ACCESS read-only 647 STATUS current 648 DESCRIPTION 649 "The number of tunnels configured on this device. A 650 tunnel is considered configured if the 651 mplsTunnelRowStatus is active(1)." 652 ::= { mplsTeScalars 1 } 654 mplsTunnelActive OBJECT-TYPE 655 SYNTAX Unsigned32 656 MAX-ACCESS read-only 657 STATUS current 658 DESCRIPTION 659 "The number of tunnels active on this device. A 660 tunnel is considered active if the 661 mplsTunnelOperStatus is up(1)." 662 ::= { mplsTeScalars 2 } 664 mplsTunnelTEDistProto OBJECT-TYPE 665 SYNTAX BITS { 666 other (0), 667 ospf (1), 668 isis (2) 669 } 670 MAX-ACCESS read-only 671 STATUS current 672 DESCRIPTION 673 "The traffic engineering distribution protocol(s) 674 used by this LSR. Note that an LSR may support more 675 than one distribution protocol simultaneously." 676 ::= { mplsTeScalars 3 } 678 mplsTunnelMaxHops OBJECT-TYPE 679 SYNTAX Unsigned32 680 MAX-ACCESS read-only 681 STATUS current 682 DESCRIPTION 683 "The maximum number of hops that can be specified for 684 a tunnel on this device." 685 ::= { mplsTeScalars 4 } 687 mplsTunnelNotificationMaxRate OBJECT-TYPE 688 SYNTAX Unsigned32 689 MAX-ACCESS read-write 690 STATUS current 691 DESCRIPTION 692 "This variable indicates the maximum number of 693 notifications issued per second. If events occur 694 more rapidly, the implementation may simply fail to 695 emit these notifications during that period, or may 696 queue them until an appropriate time. A value of 0 697 means no throttling is applied and events may be 698 notified at the rate at which they occur." 699 DEFVAL { 0 } 700 ::= { mplsTeScalars 5 } 702 -- End of MPLS Tunnel scalars. 704 -- MPLS tunnel table. 706 mplsTunnelIndexNext OBJECT-TYPE 707 SYNTAX IndexIntegerNextFree (0..65535) 708 MAX-ACCESS read-only 709 STATUS current 710 DESCRIPTION 711 "This object contains an unused value for 712 mplsTunnelIndex, or a zero to indicate 713 that none exist. Negative values are not allowed, 714 as they do not correspond to valid values of 715 mplsTunnelIndex. 717 Note that this object offers an unused value 718 for an mplsTunnelIndex value at the ingress 719 side of a tunnel. At other LSRs the value 720 of mplsTunnelIndex SHOULD be taken from the 721 value signaled by the MPLS signaling protocol. 722 " 723 ::= { mplsTeObjects 1 } 725 mplsTunnelTable OBJECT-TYPE 726 SYNTAX SEQUENCE OF MplsTunnelEntry 727 MAX-ACCESS not-accessible 728 STATUS current 729 DESCRIPTION 730 "The mplsTunnelTable allows new MPLS tunnels to be 731 created between an LSR and a remote endpoint, and 732 existing tunnels to be reconfigured or removed. 733 Note that only point-to-point tunnel segments are 734 supported, although multi-point-to-point and point- 735 to-multi-point connections are supported by an LSR 736 acting as a cross-connect. Each MPLS tunnel can 737 thus have one out-segment originating at this LSR 738 and/or one in-segment terminating at this LSR." 739 ::= { mplsTeObjects 2 } 741 mplsTunnelEntry OBJECT-TYPE 742 SYNTAX MplsTunnelEntry 743 MAX-ACCESS not-accessible 744 STATUS current 745 DESCRIPTION 746 "An entry in this table represents an MPLS tunnel. 747 An entry can be created by a network administrator 748 or by an SNMP agent as instructed by an MPLS 749 signalling protocol. Whenever a new entry is 750 created with mplsTunnelIsIf set to true(1), then a 751 corresponding entry is created in ifTable as well 752 (see RFC 2863). The ifType of this entry is 753 mplsTunnel(150). 755 A tunnel entry needs to be uniquely identified across 756 a MPLS network. Indices mplsTunnelIndex and 757 mplsTunnelInstance uniquely identify a tunnel on 758 the LSR originating the tunnel. To uniquely 759 identify a tunnel across an MPLS network requires 760 index mplsTunnelIngressLSRId. The last index 761 mplsTunnelEgressLSRId is useful in identifying all 762 instances of a tunnel that terminate on the same 763 egress LSR." 764 REFERENCE 765 "1. RFC 2863 - The Interfaces Group MIB, McCloghrie, 766 K., and F. Kastenholtz, June 2000 " 767 INDEX { mplsTunnelIndex, 768 mplsTunnelInstance, 769 mplsTunnelIngressLSRId, 770 mplsTunnelEgressLSRId 771 } 772 ::= { mplsTunnelTable 1 } 774 MplsTunnelEntry ::= SEQUENCE { 775 mplsTunnelIndex MplsTunnelIndex, 776 mplsTunnelInstance MplsTunnelInstanceIndex, 777 mplsTunnelIngressLSRId MplsExtendedTunnelId, 778 mplsTunnelEgressLSRId MplsExtendedTunnelId, 779 mplsTunnelName SnmpAdminString, 780 mplsTunnelDescr SnmpAdminString, 781 mplsTunnelIsIf TruthValue, 782 mplsTunnelIfIndex InterfaceIndexOrZero, 783 mplsTunnelOwner MplsOwner, 784 mplsTunnelRole INTEGER, 785 mplsTunnelXCPointer RowPointer, 786 mplsTunnelSignallingProto INTEGER, 787 mplsTunnelSetupPrio Integer32, 788 mplsTunnelHoldingPrio Integer32, 789 mplsTunnelSessionAttributes BITS, 790 mplsTunnelLocalProtectInUse TruthValue, 791 mplsTunnelResourcePointer RowPointer, 792 mplsTunnelPrimaryInstance MplsTunnelInstanceIndex, 793 mplsTunnelInstancePriority Unsigned32, 794 mplsTunnelHopTableIndex MplsPathIndexOrZero, 795 mplsTunnelPathInUse MplsPathIndexOrZero, 796 mplsTunnelARHopTableIndex MplsPathIndexOrZero, 797 mplsTunnelCHopTableIndex MplsPathIndexOrZero, 798 mplsTunnelIncludeAnyAffinity MplsTunnelAffinity, 799 mplsTunnelIncludeAllAffinity MplsTunnelAffinity, 800 mplsTunnelExcludeAnyAffinity MplsTunnelAffinity, 801 mplsTunnelTotalUpTime TimeTicks, 802 mplsTunnelInstanceUpTime TimeTicks, 803 mplsTunnelPrimaryUpTime TimeTicks, 804 mplsTunnelPathChanges Counter32, 805 mplsTunnelLastPathChange TimeTicks, 806 mplsTunnelCreationTime TimeStamp, 807 mplsTunnelStateTransitions Counter32, 808 mplsTunnelAdminStatus INTEGER, 809 mplsTunnelOperStatus INTEGER, 810 mplsTunnelRowStatus RowStatus, 811 mplsTunnelStorageType StorageType 812 } 814 mplsTunnelIndex OBJECT-TYPE 815 SYNTAX MplsTunnelIndex 816 MAX-ACCESS not-accessible 817 STATUS current 818 DESCRIPTION 819 "Uniquely identifies a set of tunnel instances 820 between a pair of ingress and egress LSRs. 821 Managers should obtain new values for row 822 creation in this table by reading 823 mplsTunnelIndexNext. When 824 the MPLS signalling protocol is rsvp(2) this value 825 SHOULD be equal to the value signaled in the 826 Tunnel Id of the Session object. When the MPLS 827 signalling protocol is crldp(3) this value 828 SHOULD be equal to the value signaled in the 829 LSP ID." 830 ::= { mplsTunnelEntry 1 } 832 mplsTunnelInstance OBJECT-TYPE 833 SYNTAX MplsTunnelInstanceIndex 834 MAX-ACCESS not-accessible 835 STATUS current 836 DESCRIPTION 837 "Uniquely identifies a particular instance of a 838 tunnel between a pair of ingress and egress LSRs. 839 It is useful to identify multiple instances of 840 tunnels for the purposes of backup and parallel 841 tunnels. When the MPLS signaling protocol is 842 rsvp(2) this value SHOULD be equal to the LSP Id 843 of the Sender Template object. When the signaling 844 protocol is crldp(3) there is no equivalent 845 signaling object." 846 ::= { mplsTunnelEntry 2 } 848 mplsTunnelIngressLSRId OBJECT-TYPE 849 SYNTAX MplsExtendedTunnelId 850 MAX-ACCESS not-accessible 851 STATUS current 852 DESCRIPTION 853 "Identity of the ingress LSR associated with this 854 tunnel instance. When the MPLS signalling protocol 855 is rsvp(2) this value SHOULD be equal to the Tunnel 856 Sender Address in the Sender Template object and MAY 857 be equal to the Extended Tunnel Id field in the 858 SESSION object. When the MPLS signalling protocol is 859 crldp(3) this value SHOULD be equal to the Ingress 860 LSR Router ID field in the LSPID TLV object." 861 REFERENCE 862 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 863 Awduche et al, RFC 3209, December 2001 864 2. Constraint-Based LSP Setup using LDP, Jamoussi 865 (Editor), RFC 3212, January 2002" 866 ::= { mplsTunnelEntry 3 } 868 mplsTunnelEgressLSRId OBJECT-TYPE 869 SYNTAX MplsExtendedTunnelId 870 MAX-ACCESS not-accessible 871 STATUS current 872 DESCRIPTION 873 "Identity of the egress LSR associated with this 874 tunnel instance." 875 ::= { mplsTunnelEntry 4 } 877 mplsTunnelName OBJECT-TYPE 878 SYNTAX SnmpAdminString 879 MAX-ACCESS read-create 880 STATUS current 881 DESCRIPTION 882 "The canonical name assigned to the tunnel. This name 883 can be used to refer to the tunnel on the LSR's 884 console port. If mplsTunnelIsIf is set to true 885 then the ifName of the interface corresponding to 886 this tunnel should have a value equal to 887 mplsTunnelName. Also see the description of ifName 888 in RFC 2863." 889 REFERENCE 890 "RFC 2863 - The Interfaces Group MIB, McCloghrie, K., 891 and F. Kastenholtz, June 2000" 892 DEFVAL {""} 893 ::= { mplsTunnelEntry 5 } 895 mplsTunnelDescr OBJECT-TYPE 896 SYNTAX SnmpAdminString 897 MAX-ACCESS read-create 898 STATUS current 899 DESCRIPTION 900 "A textual string containing information about the 901 tunnel. If there is no description this object 902 contains a zero length string. This object is may 903 not be signaled by MPLS signaling protocols, 904 consequentally the value of this object at transit 905 and egress LSRs MAY be automatically generated or 906 absent." 907 DEFVAL {""} 908 ::= { mplsTunnelEntry 6 } 910 mplsTunnelIsIf OBJECT-TYPE 911 SYNTAX TruthValue 912 MAX-ACCESS read-create 913 STATUS current 914 DESCRIPTION 915 "Denotes whether or not this tunnel corresponds to an 916 interface represented in the interfaces group 917 table. Note that if this variable is set to true 918 then the ifName of the interface corresponding to 919 this tunnel should have a value equal to 920 mplsTunnelName. Also see the description of ifName 921 in RFC 2863. This object is meaningful only at the 922 ingress and egress LSRs." 923 REFERENCE 924 "RFC 2863 - The Interfaces Group MIB, McCloghrie, K., 925 and F. Kastenholtz, June 2000" 927 DEFVAL { false } 928 ::= { mplsTunnelEntry 7 } 930 mplsTunnelIfIndex OBJECT-TYPE 931 SYNTAX InterfaceIndexOrZero 932 MAX-ACCESS read-only 933 STATUS current 934 DESCRIPTION 935 "If mplsTunnelIsIf is set to true, then this value 936 contains the LSR-assigned ifIndex which corresponds 937 to an entry in the interfaces table. Otherwise 938 this variable should contain the value of zero 939 indicating that a valid ifIndex was not assigned to 940 this tunnel interface." 941 REFERENCE 942 "RFC 2863 - The Interfaces Group MIB, McCloghrie, K., 943 and F. Kastenholtz, June 2000" 944 DEFVAL { 0 } 945 ::= { mplsTunnelEntry 8 } 947 mplsTunnelOwner OBJECT-TYPE 948 SYNTAX MplsOwner 949 MAX-ACCESS read-only 950 STATUS current 951 DESCRIPTION 952 "Denotes the entity that created and is responsible 953 for managing this tunnel. This column is 954 automatically filled by the agent on creation of a 955 row." 956 ::= { mplsTunnelEntry 9 } 958 mplsTunnelRole OBJECT-TYPE 959 SYNTAX INTEGER { head(1), 960 transit(2), 961 tail(3), 962 headTail(4) } 963 MAX-ACCESS read-create 964 STATUS current 965 DESCRIPTION 966 "This value signifies the role that this tunnel 967 entry/instance represents. This value MUST be set 968 to head(1) at the originating point of the tunnel. 969 This value MUST be set to transit(2) at transit 970 points along the tunnel, if transit points are 971 supported. This value MUST be set to tail(3) at the 972 terminating point of the tunnel if tunnel tails are 973 supported. 975 The value headTail(4) is provided for tunnels that 976 begin and end on the same LSR." 978 DEFVAL { head } 979 ::= { mplsTunnelEntry 10 } 981 mplsTunnelXCPointer OBJECT-TYPE 982 SYNTAX RowPointer 983 MAX-ACCESS read-create 984 STATUS current 985 DESCRIPTION 986 "This variable points to a row in the mplsXCTable. 987 This table identifies the segments that compose 988 this tunnel, their characteristics, and 989 relationships to each other. A value of zeroDotZero 990 indicates that no LSP has been associated with this 991 tunnel yet." 992 REFERENCE 993 "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS 994 Label Switch Router Management Information Base, 995 Internet Draft , 996 June 2003." 997 DEFVAL { zeroDotZero } 998 ::= { mplsTunnelEntry 11 } 1000 mplsTunnelSignallingProto OBJECT-TYPE 1001 SYNTAX INTEGER { 1002 none(1), 1003 rsvp(2), 1004 crldp(3), 1005 other(4) 1006 } 1007 MAX-ACCESS read-create 1008 STATUS current 1009 DESCRIPTION 1010 "The signalling protocol, if any, used to setup this 1011 tunnel." 1012 DEFVAL { none } 1013 ::= { mplsTunnelEntry 12 } 1015 mplsTunnelSetupPrio OBJECT-TYPE 1016 SYNTAX Integer32 (0..7) 1017 MAX-ACCESS read-create 1018 STATUS current 1019 DESCRIPTION 1020 "Indicates the setup priority of this tunnel." 1021 REFERENCE 1022 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 1023 Awduche et al, RFC 3209, December 2001 1024 2. Constraint-Based LSP Setup using LDP, Jamoussi 1025 (Editor), RFC 3212, January 2002" 1026 DEFVAL { 0 } 1027 ::= { mplsTunnelEntry 13 } 1029 mplsTunnelHoldingPrio OBJECT-TYPE 1030 SYNTAX Integer32 (0..7) 1031 MAX-ACCESS read-create 1032 STATUS current 1033 DESCRIPTION 1034 "Indicates the holding priority for this tunnel." 1035 REFERENCE 1036 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 1037 Awduche et al, RFC3209, December 2001 1039 2. Constraint-Based LSP Setup using LDP, Jamoussi 1040 (Editor), RFC 3212, January 2002" 1041 DEFVAL { 0 } 1042 ::= { mplsTunnelEntry 14 } 1044 mplsTunnelSessionAttributes OBJECT-TYPE 1045 SYNTAX BITS { 1046 fastReroute (0), 1047 mergingPermitted (1), 1048 isPersistent (2), 1049 isPinned (3), 1050 recordRoute(4) 1051 } 1052 MAX-ACCESS read-create 1053 STATUS current 1054 DESCRIPTION 1055 "This bit mask indicates optional session values for 1056 this tunnel. The following describes these bit 1057 fields: 1059 fastRerouteThis flag indicates that the any tunnel 1060 hop may choose to reroute this tunnel without 1061 tearing it down. This flag permits transit routers 1062 to use a local repair mechanism which may result in 1063 violation of the explicit routing of this tunnel. 1064 When a fault is detected on an adjacent downstream 1065 link or node, a transit router can re-route traffic 1066 for fast service restoration. 1068 mergingPermitted This flag permits transit routers 1069 to merge this session with other RSVP sessions for 1070 the purpose of reducing resource overhead on 1071 downstream transit routers, thereby providing 1072 better network scaling. 1074 isPersistent Indicates whether this tunnel should 1075 be restored automatically after a failure occurs. 1077 isPinned This flag indicates whether the loose- 1078 routed hops of this tunnel are to be pinned. 1080 recordRouteThis flag indicates whether or not the 1081 signalling protocol should remember the tunnel path 1082 after it has been signaled." 1083 REFERENCE 1084 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 1085 Awduche et al, RFC 3209, December 2001." 1086 ::= { mplsTunnelEntry 15 } 1088 mplsTunnelLocalProtectInUse OBJECT-TYPE 1089 SYNTAX TruthValue 1090 MAX-ACCESS read-create 1091 STATUS current 1092 DESCRIPTION 1093 "Indicates that the local repair mechanism is in use 1094 to maintain this tunnel (usually in the face of an 1095 outage of the link it was previously routed over)." 1096 DEFVAL { false } 1097 ::= { mplsTunnelEntry 16 } 1099 mplsTunnelResourcePointer OBJECT-TYPE 1100 SYNTAX RowPointer 1101 MAX-ACCESS read-create 1102 STATUS current 1103 DESCRIPTION 1104 "This variable represents a pointer to the traffic 1105 parameter specification for this tunnel. This 1106 value may point at an entry in the 1107 mplsTunnelResourceEntry to indicate which 1108 mplsTunnelResourceEntry is to be assigned to this 1109 LSP instance. This value may optionally point at 1110 an externally defined traffic parameter 1111 specification table. A value of zeroDotZero 1112 indicates best-effort treatment. By having the 1113 same value of this object, two or more LSPs can 1114 indicate resource sharing." 1115 DEFVAL { zeroDotZero } 1116 ::= { mplsTunnelEntry 17 } 1118 mplsTunnelPrimaryInstance OBJECT-TYPE 1119 SYNTAX MplsTunnelInstanceIndex 1120 MAX-ACCESS read-only 1121 STATUS current 1122 DESCRIPTION 1123 "Specifies the instance index of the primary instance 1124 of this tunnel. More details of the definition of 1125 tunnel instances and the primary tunnel instance 1126 can be found in the description of the textual 1127 convention MplsTunnelInstanceIndex." 1129 DEFVAL { 0 } 1130 ::= { mplsTunnelEntry 18 } 1132 mplsTunnelInstancePriority OBJECT-TYPE 1133 SYNTAX Unsigned32 1134 MAX-ACCESS read-create 1135 STATUS current 1136 DESCRIPTION 1137 "This value indicates which priority, in descending 1138 order, with 0 indicating the lowest priority, 1139 within a group of tunnel instances. A group of 1140 tunnel instances is defined as a set of LSPs with 1141 the same mplsTunnelIndex in this table, but with a 1142 different mplsTunnelInstance. Tunnel instance 1143 priorities are used to denote the priority at which 1144 a particular tunnel instance will supercede 1145 another. Instances of tunnels containing the same 1146 mplsTunnelInstancePriority will be used for load 1147 sharing." 1148 DEFVAL { 0 } 1149 ::= { mplsTunnelEntry 19 } 1151 mplsTunnelHopTableIndex OBJECT-TYPE 1152 SYNTAX MplsPathIndexOrZero 1153 MAX-ACCESS read-create 1154 STATUS current 1155 DESCRIPTION 1156 "Index into the mplsTunnelHopTable entry that 1157 specifies the explicit route hops for this tunnel. 1158 This object is meaningful only at the head-end of 1159 the tunnel." 1160 DEFVAL { 0 } 1161 ::= { mplsTunnelEntry 20 } 1163 mplsTunnelPathInUse OBJECT-TYPE 1164 SYNTAX MplsPathIndexOrZero 1165 MAX-ACCESS read-create 1166 STATUS current 1167 DESCRIPTION 1168 "This value denotes the configured path that was 1169 chosen for this tunnel. This value reflects the 1170 secondary index into mplsTunnelHopTable. This path 1171 may not exactly match the one in 1172 mplsTunnelARHopTable due to the fact that some CSPF 1173 modification may have taken place. See 1174 mplsTunnelARHopTable for the actual path being 1175 taken by the tunnel. A value of zero denotes that 1176 no path is currently in use or available." 1177 DEFVAL { 0 } 1178 ::= { mplsTunnelEntry 21 } 1180 mplsTunnelARHopTableIndex OBJECT-TYPE 1181 SYNTAX MplsPathIndexOrZero 1182 MAX-ACCESS read-only 1183 STATUS current 1184 DESCRIPTION 1185 "Index into the mplsTunnelARHopTable entry that 1186 specifies the actual hops traversed by the tunnel. 1187 This is automatically updated by the agent when the 1188 actual hops becomes available." 1189 DEFVAL { 0 } 1190 ::= { mplsTunnelEntry 22 } 1192 mplsTunnelCHopTableIndex OBJECT-TYPE 1193 SYNTAX MplsPathIndexOrZero 1194 MAX-ACCESS read-only 1195 STATUS current 1196 DESCRIPTION 1197 "Index into the mplsTunnelCHopTable entry that 1198 specifies the computed hops traversed by the 1199 tunnel. This is automatically updated by the agent 1200 when computed hops become available or when 1201 computed hops get modified." 1202 DEFVAL { 0 } 1203 ::= { mplsTunnelEntry 23 } 1205 mplsTunnelIncludeAnyAffinity OBJECT-TYPE 1206 SYNTAX MplsTunnelAffinity 1207 MAX-ACCESS read-create 1208 STATUS current 1209 DESCRIPTION 1210 "A link satisfies the include-any constraint if and 1211 only if the constraint is zero, or the link and the 1212 constraint have a resource class in common." 1213 REFERENCE 1214 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 1215 Awduche et al, RFC 3209, December 2001." 1216 ::= { mplsTunnelEntry 24 } 1218 mplsTunnelIncludeAllAffinity OBJECT-TYPE 1219 SYNTAX MplsTunnelAffinity 1220 MAX-ACCESS read-create 1221 STATUS current 1222 DESCRIPTION 1223 "A link satisfies the include-all constraint if and 1224 only if the link contains all of the administrative 1225 groups specified in the constraint." 1226 REFERENCE 1227 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 1228 Awduche et al, RFC 3209, December 2001." 1230 ::= { mplsTunnelEntry 25 } 1232 mplsTunnelExcludeAnyAffinity OBJECT-TYPE 1233 SYNTAX MplsTunnelAffinity 1234 MAX-ACCESS read-create 1235 STATUS current 1236 DESCRIPTION 1237 "A link satisfies the exclude-any constraint if and 1238 only if the link contains none of the 1239 administrative groups specified in the constraint." 1240 REFERENCE 1241 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 1242 Awduche et al, RFC 3209, December 2001." 1243 DEFVAL { 0 } 1244 ::= { mplsTunnelEntry 26 } 1246 mplsTunnelTotalUpTime OBJECT-TYPE 1247 SYNTAX TimeTicks 1248 MAX-ACCESS read-only 1249 STATUS current 1250 DESCRIPTION 1251 "This value represents the aggregate up time for all 1252 instances of this tunnel, if available. If this 1253 value is unavailable, it MUST return a value of 0." 1254 ::= { mplsTunnelEntry 27 } 1256 mplsTunnelInstanceUpTime OBJECT-TYPE 1257 SYNTAX TimeTicks 1258 MAX-ACCESS read-only 1259 STATUS current 1260 DESCRIPTION 1261 "This value identifies the total time that this 1262 tunnel instance's operStatus has been Up(1)." 1263 ::= { mplsTunnelEntry 28 } 1265 mplsTunnelPrimaryUpTime OBJECT-TYPE 1266 SYNTAX TimeTicks 1267 MAX-ACCESS read-only 1268 STATUS current 1269 DESCRIPTION 1270 "Specifies the total time the primary instance of 1271 this tunnel has been active. The primary instance 1272 of this tunnel is defined in 1273 mplsTunnelPrimaryInstance." 1274 ::= { mplsTunnelEntry 29 } 1276 mplsTunnelPathChanges OBJECT-TYPE 1277 SYNTAX Counter32 1278 MAX-ACCESS read-only 1279 STATUS current 1280 DESCRIPTION 1281 "Specifies the number of times the actual path for 1282 this tunnel instance has changed." 1283 ::= { mplsTunnelEntry 30 } 1285 mplsTunnelLastPathChange OBJECT-TYPE 1286 SYNTAX TimeTicks 1287 MAX-ACCESS read-only 1288 STATUS current 1289 DESCRIPTION 1290 "Specifies the time since the last change to the 1291 actual path for this tunnel instance." 1292 ::= { mplsTunnelEntry 31 } 1294 mplsTunnelCreationTime OBJECT-TYPE 1295 SYNTAX TimeStamp 1296 MAX-ACCESS read-only 1297 STATUS current 1298 DESCRIPTION 1299 "Specifies the value of SysUpTime when the first 1300 instance of this tunnel came into existence. 1301 That is, when the value of mplsTunnelOperStatus 1302 was first set to up(1)." 1303 ::= { mplsTunnelEntry 32 } 1305 mplsTunnelStateTransitions OBJECT-TYPE 1306 SYNTAX Counter32 1307 MAX-ACCESS read-only 1308 STATUS current 1309 DESCRIPTION 1310 "Specifies the number of times the state 1311 (mplsTunnelOperStatus) of this tunnel instance has 1312 changed." 1313 ::= { mplsTunnelEntry 33 } 1315 mplsTunnelAdminStatus OBJECT-TYPE 1316 SYNTAX INTEGER { 1317 -- ready to pass packets 1318 up(1), 1319 down(2), 1320 -- in some test mode 1321 testing(3) 1322 } 1323 MAX-ACCESS read-create 1324 STATUS current 1325 DESCRIPTION 1326 "Indicates the desired operational status of this 1327 tunnel." 1328 ::= { mplsTunnelEntry 34 } 1330 mplsTunnelOperStatus OBJECT-TYPE 1331 SYNTAX INTEGER { 1332 -- ready to pass packets 1333 up(1), 1334 down(2), 1335 -- in some test mode 1336 testing(3), 1337 -- status cannot be determined 1338 unknown(4), 1339 dormant(5), 1340 -- some component is missing 1341 notPresent(6), 1342 -- down due to the state of 1343 -- lower layer interfaces 1344 lowerLayerDown(7) 1345 } 1346 MAX-ACCESS read-only 1347 STATUS current 1348 DESCRIPTION 1349 "Indicates the actual operational status of this 1350 tunnel, which is typically but not limited to, a 1351 function of the state of individual segments of 1352 this tunnel." 1353 ::= { mplsTunnelEntry 35 } 1355 mplsTunnelRowStatus OBJECT-TYPE 1356 SYNTAX RowStatus 1357 MAX-ACCESS read-create 1358 STATUS current 1359 DESCRIPTION 1360 "This variable is used to create, modify, and/or 1361 delete a row in this table. When a row in this 1362 table is in active(1) state, no objects in that row 1363 can be modified by the agent except 1364 mplsTunnelAdminStatus, mplsTunnelRowStatus and 1365 mplsTunnelStorageType." 1366 ::= { mplsTunnelEntry 36 } 1368 mplsTunnelStorageType OBJECT-TYPE 1369 SYNTAX StorageType 1370 MAX-ACCESS read-create 1371 STATUS current 1372 DESCRIPTION "The storage type for this tunnel entry. 1373 Conceptual rows having the value 'permanent' 1374 need not allow write-access to any columnar 1375 objects in the row." 1376 DEFVAL { volatile } 1377 ::= { mplsTunnelEntry 37 } 1379 -- End of mplsTunnelTable 1380 mplsTunnelHopListIndexNext OBJECT-TYPE 1381 SYNTAX MplsPathIndexOrZero 1382 MAX-ACCESS read-only 1383 STATUS current 1384 DESCRIPTION 1385 "This object contains an appropriate value to be used 1386 for mplsTunnelHopListIndex when creating entries in 1387 the mplsTunnelHopTable. If the number of 1388 unassigned entries is exhausted, a retrieval 1389 operation will return a value of 0. This object 1390 may also return a value of 0 when the LSR is unable 1391 to accept conceptual row creation, for example, if 1392 the mplsTunnelHopTable is implemented as read-only. 1393 To obtain the value of mplsTunnelHopListIndex for a 1394 new entry in the mplsTunnelHopTable, the manager 1395 issues a management protocol retrieval operation to 1396 obtain the current value of mplsTunnelHopIndex. 1398 When the SET is performed to create a row in the 1399 mplsTunnelHopTable, the Command Responder (agent) 1400 must determine whether the value is indeed still 1401 unused; Two Network Management Applications may 1402 attempt to create a row (configuration entry) 1403 simultaneously and use the same value. If it is 1404 currently unused, the SET succeeds and the Command 1405 Responder (agent) changes the value of this object, 1406 according to an implementation-specific algorithm. 1407 If the value is in use, however, the SET fails. The 1408 Network Management Application must then re-read 1409 this variable to obtain a new usable value." 1410 ::= { mplsTeObjects 3 } 1412 mplsTunnelHopTable OBJECT-TYPE 1413 SYNTAX SEQUENCE OF MplsTunnelHopEntry 1414 MAX-ACCESS not-accessible 1415 STATUS current 1416 DESCRIPTION 1417 "The mplsTunnelHopTable is used to indicate the hops, 1418 strict or loose, for an instance of an MPLS tunnel 1419 defined in mplsTunnelTable, when it is established 1420 via signalling, for the outgoing direction of the 1421 tunnel. Thus at a transit LSR, this table contains 1422 the desired path of the tunnel from this LSR 1423 onwards. Each row in this table is indexed by 1424 mplsTunnelHopListIndex which corresponds to a group 1425 of hop lists or path options. Each row also has a 1426 secondary index mplsTunnelHopIndex, which indicates 1427 a group of hops (also known as a path option). 1429 Finally, the third index, mplsTunnelHopIndex 1430 indicates the specific hop information for a path 1431 option. In case we want to specify a particular 1432 interface on the originating LSR of an outgoing 1433 tunnel by which we want packets to exit the LSR, 1434 we specify this as the first hop for this tunnel in 1435 mplsTunnelHopTable." 1436 ::= { mplsTeObjects 4 } 1438 mplsTunnelHopEntry OBJECT-TYPE 1439 SYNTAX MplsTunnelHopEntry 1440 MAX-ACCESS not-accessible 1441 STATUS current 1442 DESCRIPTION 1443 "An entry in this table represents a tunnel hop. An 1444 entry is created by a network administrator for 1445 signaled ERLSP set up by an MPLS signalling 1446 protocol." 1447 INDEX { 1448 mplsTunnelHopListIndex, 1449 mplsTunnelHopPathOptionIndex, 1450 mplsTunnelHopIndex 1451 } 1452 ::= { mplsTunnelHopTable 1 } 1454 MplsTunnelHopEntry ::= SEQUENCE { 1455 mplsTunnelHopListIndex MplsPathIndex, 1456 mplsTunnelHopPathOptionIndex MplsPathIndex, 1457 mplsTunnelHopIndex MplsPathIndex, 1458 mplsTunnelHopAddrType TeHopAddressType, 1459 mplsTunnelHopIpAddr TeHopAddress, 1460 mplsTunnelHopIpPrefixLen InetAddressPrefixLength, 1461 mplsTunnelHopAsNumber TeHopAddressAS, 1462 mplsTunnelHopAddrUnnum TeHopAddressUnnum, 1463 mplsTunnelHopLspId MplsLSPID, 1464 mplsTunnelHopType INTEGER, 1465 mplsTunnelHopInclude TruthValue, 1466 mplsTunnelHopPathOptionName SnmpAdminString, 1467 mplsTunnelHopEntryPathComp INTEGER, 1468 mplsTunnelHopRowStatus RowStatus, 1469 mplsTunnelHopStorageType StorageType 1470 } 1472 mplsTunnelHopListIndex OBJECT-TYPE 1473 SYNTAX MplsPathIndex 1474 MAX-ACCESS not-accessible 1475 STATUS current 1476 DESCRIPTION 1477 "Primary index into this table identifying a 1478 particular explicit route object." 1480 ::= { mplsTunnelHopEntry 1 } 1482 mplsTunnelHopPathOptionIndex OBJECT-TYPE 1483 SYNTAX MplsPathIndex 1484 MAX-ACCESS not-accessible 1485 STATUS current 1486 DESCRIPTION 1487 "Secondary index into this table identifying a 1488 particular group of hops representing a particular 1489 configured path. This is otherwise known as a path 1490 option." 1491 ::= { mplsTunnelHopEntry 2 } 1493 mplsTunnelHopIndex OBJECT-TYPE 1494 SYNTAX MplsPathIndex 1495 MAX-ACCESS not-accessible 1496 STATUS current 1497 DESCRIPTION 1498 "Tertiary index into this table identifying a 1499 particular hop." 1500 ::= { mplsTunnelHopEntry 3 } 1502 mplsTunnelHopAddrType OBJECT-TYPE 1503 SYNTAX TeHopAddressType 1504 MAX-ACCESS read-create 1505 STATUS current 1506 DESCRIPTION "The Hop Address Type of this tunnel hop. 1508 The value of this object cannot be changed 1509 if the value of the corresponding 1510 mplsTunnelHopRowStatus object is 'active'. 1512 Note that lspid(5) is a valid option only 1513 for tunnels signaled via CRLDP. 1514 " 1515 DEFVAL { ipv4 } 1516 ::= { mplsTunnelHopEntry 4 } 1518 mplsTunnelHopIpAddr OBJECT-TYPE 1519 SYNTAX TeHopAddress 1520 MAX-ACCESS read-create 1521 STATUS current 1522 DESCRIPTION "The Tunnel Hop Address for this tunnel hop. 1524 The type of this address is determined by the 1525 value of the corresponding mplsTunnelHopAddrType. 1527 The value of this object cannot be changed 1528 if the value of the corresponding 1529 mplsTunnelHopRowStatus object is 'active'. 1531 " 1532 DEFVAL { '00000000'h } -- IPv4 address 0.0.0.0 1533 ::= { mplsTunnelHopEntry 5 } 1535 mplsTunnelHopIpPrefixLen OBJECT-TYPE 1536 SYNTAX InetAddressPrefixLength 1537 MAX-ACCESS read-create 1538 STATUS current 1539 DESCRIPTION "If mplsTunnelHopAddrType is set to ipv4(1) or 1540 ipv6(2), then this value will contain an 1541 appropriate prefix length for the IP address in 1542 object mplsTunnelHopIpAddr. Otherwise this value 1543 is irrelevant and should be ignored. 1544 " 1545 DEFVAL { 32 } 1546 ::= { mplsTunnelHopEntry 6 } 1548 mplsTunnelHopAsNumber OBJECT-TYPE 1549 SYNTAX TeHopAddressAS 1550 MAX-ACCESS read-create 1551 STATUS current 1552 DESCRIPTION 1553 "If mplsTunnelHopAddrType is set to asnumber(3), then 1554 this value will contain the AS number of this hop. 1555 Otherwise the agent should set this object to zero- 1556 length string and the manager should ignore this." 1557 ::= { mplsTunnelHopEntry 7 } 1559 mplsTunnelHopAddrUnnum OBJECT-TYPE 1560 SYNTAX TeHopAddressUnnum 1561 MAX-ACCESS read-create 1562 STATUS current 1563 DESCRIPTION 1564 "If mplsTunnelHopAddrType is set to unnum(4), then 1565 this value will contain the interface identifier of 1566 the unnumbered interface for this hop. This object 1567 should be used in conjunction with 1568 mplsTunnelHopIpAddress which would contain the LSR 1569 Router ID in this case. Otherwise the agent should 1570 set this object to zero-length string and the 1571 manager should ignore this." 1572 ::= { mplsTunnelHopEntry 8 } 1574 mplsTunnelHopLspId OBJECT-TYPE 1575 SYNTAX MplsLSPID 1576 MAX-ACCESS read-create 1577 STATUS current 1578 DESCRIPTION 1579 "If mplsTunnelHopAddrType is set to lspid(5), then 1580 this value will contain the LSPID of a tunnel of 1581 this hop. The present tunnel being configured is 1582 tunneled through this hop (using label stacking). 1583 This object is otherwise insignificant and should 1584 contain a value of 0 to indicate this fact." 1585 ::= { mplsTunnelHopEntry 9 } 1587 mplsTunnelHopType OBJECT-TYPE 1588 SYNTAX INTEGER { 1589 strict(1), 1590 loose(2) 1591 } 1592 MAX-ACCESS read-create 1593 STATUS current 1594 DESCRIPTION 1595 "Denotes whether this tunnel hop is routed in a 1596 strict or loose fashion. The value of this object 1597 has no meaning if the mplsTunnelHopInclude object 1598 is set to 'false'." 1599 ::= { mplsTunnelHopEntry 10 } 1601 mplsTunnelHopInclude OBJECT-TYPE 1602 SYNTAX TruthValue 1603 MAX-ACCESS read-create 1604 STATUS current 1605 DESCRIPTION 1606 "If this value is set to true, then this indicates 1607 that this hop must be included in the tunnel's 1608 path. If this value is set to 'false', then this hop 1609 must be avoided when calculating the path for this 1610 tunnel. The default value of this object is 'true', 1611 so that by default all indicated hops are included 1612 in the CSPF path computation. If this object is set 1613 to 'false' the value of mplsTunnelHopType should be 1614 ignored." 1615 DEFVAL { true } 1616 ::= { mplsTunnelHopEntry 11 } 1618 mplsTunnelHopPathOptionName OBJECT-TYPE 1619 SYNTAX SnmpAdminString 1620 MAX-ACCESS read-create 1621 STATUS current 1622 DESCRIPTION 1623 "The description of this series of hops as they 1624 relate to the specified path option. The 1625 value of this object SHOULD be the same for 1626 each hop in the series that comprises a 1627 path option." 1628 ::= { mplsTunnelHopEntry 12 } 1630 mplsTunnelHopEntryPathComp OBJECT-TYPE 1631 SYNTAX INTEGER { 1632 dynamic(1), -- CSPF computed 1633 explicit(2) -- strict hop 1634 } 1635 MAX-ACCESS read-create 1636 STATUS current 1637 DESCRIPTION 1638 "If this value is set to dynamic, then the user 1639 should only specify the source and destination of 1640 the path and expect that the CSPF will calculate 1641 the remainder of the path. If this value is set to 1642 explicit, the user should specify the entire path 1643 for the tunnel to take. This path may contain 1644 strict or loose hops. Each hop along a specific 1645 path SHOULD have this object set to the same value" 1646 ::= { mplsTunnelHopEntry 13 } 1648 mplsTunnelHopRowStatus OBJECT-TYPE 1649 SYNTAX RowStatus 1650 MAX-ACCESS read-create 1651 STATUS current 1652 DESCRIPTION 1653 "This variable is used to create, modify, and/or 1654 delete a row in this table. When a row in this 1655 table is in active(1) state, no objects in that row 1656 can be modified by the agent except 1657 mplsTunnelHopRowStatus and 1658 mplsTunnelHopStorageType." 1659 ::= { mplsTunnelHopEntry 14 } 1661 mplsTunnelHopStorageType OBJECT-TYPE 1662 SYNTAX StorageType 1663 MAX-ACCESS read-create 1664 STATUS current 1665 DESCRIPTION 1666 "The storage type for this Hop entry. Conceptual 1667 rows having the value 'permanent' need not 1668 allow write-access to any columnar objects 1669 in the row." 1670 DEFVAL { volatile } 1671 ::= { mplsTunnelHopEntry 15 } 1673 -- End of mplsTunnelHopTable 1675 -- Begin of mplsTunnelResourceTable 1677 mplsTunnelResourceIndexNext OBJECT-TYPE 1678 SYNTAX Unsigned32 (0.. 2147483647) 1679 MAX-ACCESS read-only 1680 STATUS current 1681 DESCRIPTION 1682 "This object contains the next appropriate value to 1683 be used for mplsTunnelResourceIndex when creating 1684 entries in the mplsTunnelResourceTable. If the 1685 number of unassigned entries is exhausted, a 1686 retrieval operation will return a value of 0. This 1687 object may also return a value of 0 when the LSR is 1688 unable to accept conceptual row creation, for 1689 example, if the mplsTunnelTable is implemented as 1690 read-only. To obtain the mplsTunnelResourceIndex 1691 value for a new entry, the manager must first issue 1692 a management protocol retrieval operation to obtain 1693 the current value of this object. 1695 When the SET is performed to create a row in the 1696 mplsTunnelResourceTable, the Command Responder 1697 (agent) must determine whether the value is indeed 1698 still unused; Two Network Management Applications 1699 may attempt to create a row (configuration entry) 1700 simultaneously and use the same value. If it is 1701 currently unused, the SET succeeds and the Command 1702 Responder (agent) changes the value of this object, 1703 according to an implementation-specific algorithm. 1704 If the value is in use, however, the SET fails. The 1705 Network Management Application must then re-read 1706 this variable to obtain a new usable value." 1707 ::= { mplsTeObjects 5 } 1709 mplsTunnelResourceTable OBJECT-TYPE 1710 SYNTAX SEQUENCE OF MplsTunnelResourceEntry 1711 MAX-ACCESS not-accessible 1712 STATUS current 1713 DESCRIPTION 1714 "The mplsTunnelResourceTable allows a manager to 1715 specify which resources are desired for an MPLS 1716 tunnel. This table also allows several tunnels to 1717 point to a single entry in this table, implying 1718 that these tunnels should share resources." 1719 ::= { mplsTeObjects 6 } 1721 mplsTunnelResourceEntry OBJECT-TYPE 1722 SYNTAX MplsTunnelResourceEntry 1723 MAX-ACCESS not-accessible 1724 STATUS current 1725 DESCRIPTION 1726 "An entry in this table represents a set of resources 1727 for an MPLS tunnel. An entry can be created by a 1728 network administrator or by an SNMP agent as 1729 instructed by any MPLS signalling protocol. 1731 An entry in this table referenced by a tunnel instance 1732 with zero mplsTunnelInstance value indicates a 1733 configured set of resource parameter. An entry 1734 referenced by a tunnel instance with a non-zero 1735 mplsTunnelInstance reflects the in-use resource 1736 parameters for the tunnel instance which may have 1737 been negotiated or modified by the MPLS signaling 1738 protocols." 1739 INDEX { mplsTunnelResourceIndex } 1740 ::= { mplsTunnelResourceTable 1 } 1742 MplsTunnelResourceEntry ::= SEQUENCE { 1743 mplsTunnelResourceIndex Unsigned32, 1744 mplsTunnelResourceMaxRate MplsBitRate, 1745 mplsTunnelResourceMeanRate MplsBitRate, 1746 mplsTunnelResourceMaxBurstSize MplsBurstSize, 1747 mplsTunnelResourceMeanBurstSize MplsBurstSize, 1748 mplsTunnelResourceExBurstSize MplsBurstSize, 1749 mplsTunnelResourceFrequency INTEGER, 1750 mplsTunnelResourceWeight Unsigned32, 1751 mplsTunnelResourceRowStatus RowStatus, 1752 mplsTunnelResourceStorageType StorageType 1753 } 1755 mplsTunnelResourceIndex OBJECT-TYPE 1756 SYNTAX Unsigned32 (1..2147483647) 1757 MAX-ACCESS not-accessible 1758 STATUS current 1759 DESCRIPTION 1760 "Uniquely identifies this row." 1761 ::= { mplsTunnelResourceEntry 1 } 1763 mplsTunnelResourceMaxRate OBJECT-TYPE 1764 SYNTAX MplsBitRate 1765 UNITS "kilobits per second" 1766 MAX-ACCESS read-create 1767 STATUS current 1768 DESCRIPTION 1769 "The maximum rate in bits/second. Note that setting 1770 mplsTunnelResourceMaxRate, 1771 mplsTunnelResourceMeanRate, and 1772 mplsTunnelResourceMaxBurstSize to 0 indicates best- 1773 effort treatment." 1774 ::= { mplsTunnelResourceEntry 2 } 1776 mplsTunnelResourceMeanRate OBJECT-TYPE 1777 SYNTAX MplsBitRate 1778 UNITS "kilobits per second" 1779 MAX-ACCESS read-create 1780 STATUS current 1781 DESCRIPTION 1782 "This object is copied into an instance of 1783 mplsTrafficParamMeanRate in the 1784 mplsTrafficParamTable. The OID of this table entry 1785 is then copied into the corresponding 1786 mplsInSegmentTrafficParamPtr." 1787 ::= { mplsTunnelResourceEntry 3 } 1789 mplsTunnelResourceMaxBurstSize OBJECT-TYPE 1790 SYNTAX MplsBurstSize 1791 UNITS "bytes" 1792 MAX-ACCESS read-create 1793 STATUS current 1794 DESCRIPTION 1795 "The maximum burst size in bytes." 1796 ::= { mplsTunnelResourceEntry 4 } 1798 mplsTunnelResourceMeanBurstSize OBJECT-TYPE 1799 SYNTAX MplsBurstSize 1800 UNITS "bytes" 1801 MAX-ACCESS read-create 1802 STATUS current 1803 DESCRIPTION 1804 "The mean burst size in bytes. The implementations 1805 which do not implement this variable must return 1806 a noSuchObject exception for this object and must 1807 not allow a user to set this object." 1808 ::= { mplsTunnelResourceEntry 5 } 1810 mplsTunnelResourceExBurstSize OBJECT-TYPE 1811 SYNTAX MplsBurstSize 1812 UNITS "bytes" 1813 MAX-ACCESS read-create 1814 STATUS current 1815 DESCRIPTION 1816 "The Excess burst size in bytes. The implementations 1817 which do not implement this variable must return 1818 noSuchObject exception for this object and must 1819 not allow a user to set this value." 1820 REFERENCE 1821 "CR-LDP Specification, Section 4.3." 1822 ::= { mplsTunnelResourceEntry 6 } 1824 mplsTunnelResourceFrequency OBJECT-TYPE 1825 SYNTAX INTEGER { unspecified(1), 1826 frequent(2), 1827 veryFrequent(3) 1828 } 1829 MAX-ACCESS read-create 1830 STATUS current 1831 DESCRIPTION 1832 "The granularity of the availability of committed 1833 rate. The implementations which do not implement 1834 this variable must return unspecified(1) for this 1835 value and must not allow a user to set this value." 1836 REFERENCE 1837 "CR-LDP Specification, Section 4.3." 1838 ::= { mplsTunnelResourceEntry 7 } 1840 mplsTunnelResourceWeight OBJECT-TYPE 1841 SYNTAX Unsigned32(0..255) 1842 MAX-ACCESS read-create 1843 STATUS current 1844 DESCRIPTION 1845 "The relative weight for using excess bandwidth above 1846 its committed rate. The value of 0 means that 1847 weight is not applicable for the CR-LSP." 1848 REFERENCE 1849 "CR-LDP Specification, Section 4.3." 1850 ::= { mplsTunnelResourceEntry 8 } 1852 mplsTunnelResourceRowStatus OBJECT-TYPE 1853 SYNTAX RowStatus 1854 MAX-ACCESS read-create 1855 STATUS current 1856 DESCRIPTION 1857 "This variable is used to create, modify, and/or 1858 delete a row in this table. When a row in this 1859 table is in active(1) state, no objects in that row 1860 can be modified by the agent except 1861 mplsTunnelResourceRowStatus and 1862 mplsTunnelResourceStorageType." 1863 ::= { mplsTunnelResourceEntry 9 } 1865 mplsTunnelResourceStorageType OBJECT-TYPE 1866 SYNTAX StorageType 1867 MAX-ACCESS read-create 1868 STATUS current 1869 DESCRIPTION 1870 "The storage type for this Hop entry. Conceptual 1871 rows having the value 'permanent' need not 1872 allow write-access to any columnar objects 1873 in the row." 1874 DEFVAL { volatile } 1876 ::= { mplsTunnelResourceEntry 10 } 1878 -- End mplsTunnelResourceTable 1879 -- Tunnel Actual Route Hop table. 1881 mplsTunnelARHopTable OBJECT-TYPE 1882 SYNTAX SEQUENCE OF MplsTunnelARHopEntry 1883 MAX-ACCESS not-accessible 1884 STATUS current 1885 DESCRIPTION 1886 "The mplsTunnelARHopTable is used to indicate the 1887 hops for an MPLS tunnel defined in mplsTunnelTable, 1888 as reported by the MPLS signalling protocol. Thus at 1889 a transit LSR, this table (if the table is supported 1890 and if the signaling protocol is recording actual 1891 route information) contains the actual route of the 1892 whole tunnel. If the signaling protocol is not 1893 recording the actual route, this table MAY report 1894 the information from the mplsTunnelHopTable or the 1895 mplsTunnelCHopTable. 1897 Each row in this table is indexed by 1898 mplsTunnelARHopListIndex. Each row also has a 1899 secondary index mplsTunnelARHopIndex, corresponding 1900 to the next hop that this row corresponds to. 1902 Please note that since the information necessary to 1903 build entries within this table is not provided by 1904 some MPLS signalling protocols, implementation of 1905 this table is optional. Furthermore, since the 1906 information in this table is actually provided by 1907 the MPLS signalling protocol after the path has 1908 been set-up, the entries in this table are provided 1909 only for observation, and hence, all variables in 1910 this table are accessible exclusively as read- 1911 only. 1913 Note also that the contencts of this table may change 1914 while it is being read because of re-routing 1915 activities. A network administrator may verify that 1916 the actual route read is consistent by reference to 1917 the mplsTunnelLastPathChange object." 1918 ::= { mplsTeObjects 7 } 1920 mplsTunnelARHopEntry OBJECT-TYPE 1921 SYNTAX MplsTunnelARHopEntry 1922 MAX-ACCESS not-accessible 1923 STATUS current 1924 DESCRIPTION 1925 "An entry in this table represents a tunnel hop. An 1926 entry is created by the agent for signaled ERLSP 1927 set up by an MPLS signalling protocol." 1928 INDEX { mplsTunnelARHopListIndex, mplsTunnelARHopIndex } 1929 ::= { mplsTunnelARHopTable 1 } 1931 MplsTunnelARHopEntry ::= SEQUENCE { 1932 mplsTunnelARHopListIndex MplsPathIndex, 1933 mplsTunnelARHopIndex MplsPathIndex, 1934 mplsTunnelARHopAddrType TeHopAddressType, 1935 mplsTunnelARHopIpAddr TeHopAddress, 1936 mplsTunnelARHopAddrUnnum TeHopAddressUnnum, 1937 mplsTunnelARHopLspId MplsLSPID 1938 } 1940 mplsTunnelARHopListIndex OBJECT-TYPE 1941 SYNTAX MplsPathIndex 1942 MAX-ACCESS not-accessible 1943 STATUS current 1944 DESCRIPTION 1945 "Primary index into this table identifying a 1946 particular recorded hop list." 1947 ::= { mplsTunnelARHopEntry 1 } 1949 mplsTunnelARHopIndex OBJECT-TYPE 1950 SYNTAX MplsPathIndex 1951 MAX-ACCESS not-accessible 1952 STATUS current 1953 DESCRIPTION 1954 "Secondary index into this table identifying the 1955 particular hop." 1956 ::= { mplsTunnelARHopEntry 2 } 1958 mplsTunnelARHopAddrType OBJECT-TYPE 1959 SYNTAX TeHopAddressType 1960 MAX-ACCESS read-only 1961 STATUS current 1962 DESCRIPTION 1963 "The Hop Address Type of this tunnel hop. 1965 Note that lspid(5) is a valid option only 1966 for tunnels signaled via CRLDP." 1967 DEFVAL { ipv4 } 1968 ::= { mplsTunnelARHopEntry 3 } 1970 mplsTunnelARHopIpAddr OBJECT-TYPE 1971 SYNTAX TeHopAddress 1972 MAX-ACCESS read-only 1973 STATUS current 1974 DESCRIPTION 1975 "The Tunnel Hop Address for this tunnel hop. 1977 The type of this address is determined by the 1978 value of the corresponding mplsTunnelARHopAddrType. 1980 If mplsTunnelARHopAddrType is set to unnum(4), 1981 then this value contains the LSR Router ID of the 1982 unnumbered interface. Otherwise the agent SHOULD 1983 set this object to the zero-length string and the 1984 manager should ignore this object." 1985 DEFVAL { '00000000'h } -- IPv4 address 0.0.0.0 1986 ::= { mplsTunnelARHopEntry 4 } 1988 mplsTunnelARHopAddrUnnum OBJECT-TYPE 1989 SYNTAX TeHopAddressUnnum 1990 MAX-ACCESS read-only 1991 STATUS current 1992 DESCRIPTION 1993 "If mplsTunnelARHopAddrType is set to unnum(4), then 1994 this value will contain the interface identifier of 1995 the unnumbered interface for this hop. This object 1996 should be used in conjunction with 1997 mplsTunnelARHopIpAddr which would contain the LSR 1998 Router ID in this case. Otherwise the agent should 1999 set this object to zero-length string and the 2000 manager should ignore this." 2001 ::= { mplsTunnelARHopEntry 5 } 2003 mplsTunnelARHopLspId OBJECT-TYPE 2004 SYNTAX MplsLSPID 2005 MAX-ACCESS read-only 2006 STATUS current 2007 DESCRIPTION 2008 "If mplsTunnelARHopAddrType is set to lspid(5), then 2009 this value will contain the LSP ID of this hop. 2010 This object is otherwise insignificant and should 2011 contain a value of 0 to indicate this fact." 2012 ::= { mplsTunnelARHopEntry 6 } 2014 -- End of mplsTunnelARHopTable 2016 -- Tunnel Computed Hop table. 2018 mplsTunnelCHopTable OBJECT-TYPE 2019 SYNTAX SEQUENCE OF MplsTunnelCHopEntry 2020 MAX-ACCESS not-accessible 2021 STATUS current 2022 DESCRIPTION 2023 "The mplsTunnelCHopTable is used to indicate the 2024 hops, strict or loose, for an MPLS tunnel defined 2025 in mplsTunnelTable, as computed by a constraint- 2026 based routing protocol, based on the 2027 mplsTunnelHopTable for the outgoing direction of 2028 the tunnel. Thus at a transit LSR, this table (if 2029 the table is supported) MAY contain the path 2030 computed by the CSPF engine on (or on behalf of) 2031 this LSR. Each row in this table is indexed by 2032 mplsTunnelCHopListIndex. Each row also has a 2033 secondary index mplsTunnelCHopIndex, corresponding 2034 to the next hop that this row corresponds to. In 2035 case we want to specify a particular interface on 2036 the originating LSR of an outgoing tunnel by which 2037 we want packets to exit the LSR, we specify this as 2038 the first hop for this tunnel in 2039 mplsTunnelCHopTable. 2041 Please note that since the information necessary to 2042 build entries within this table may not be 2043 supported by some LSRs, implementation of this 2044 table is optional. Furthermore, since the 2045 information in this table describes the path 2046 computed by the CSPF engine the entries in this 2047 table are read-only." 2048 ::= { mplsTeObjects 8 } 2050 mplsTunnelCHopEntry OBJECT-TYPE 2051 SYNTAX MplsTunnelCHopEntry 2052 MAX-ACCESS not-accessible 2053 STATUS current 2054 DESCRIPTION 2055 "An entry in this table represents a tunnel hop. An 2056 entry in this table is created by a path 2057 computation engine using CSPF techniques applied to 2058 the information collected by routing protocols and 2059 the hops specified in the corresponding 2060 mplsTunnelHopTable." 2061 INDEX { mplsTunnelCHopListIndex, mplsTunnelCHopIndex } 2062 ::= { mplsTunnelCHopTable 1 } 2064 MplsTunnelCHopEntry ::= SEQUENCE { 2065 mplsTunnelCHopListIndex MplsPathIndex, 2066 mplsTunnelCHopIndex MplsPathIndex, 2067 mplsTunnelCHopAddrType TeHopAddressType, 2068 mplsTunnelCHopIpAddr TeHopAddress, 2069 mplsTunnelCHopIpPrefixLen InetAddressPrefixLength, 2070 mplsTunnelCHopAsNumber TeHopAddressAS, 2071 mplsTunnelCHopAddrUnnum TeHopAddressUnnum, 2072 mplsTunnelCHopLspId MplsLSPID, 2073 mplsTunnelCHopType INTEGER 2074 } 2076 mplsTunnelCHopListIndex OBJECT-TYPE 2077 SYNTAX MplsPathIndex 2078 MAX-ACCESS not-accessible 2079 STATUS current 2080 DESCRIPTION 2081 "Primary index into this table identifying a 2082 particular computed hop list." 2083 ::= { mplsTunnelCHopEntry 1 } 2085 mplsTunnelCHopIndex OBJECT-TYPE 2086 SYNTAX MplsPathIndex 2087 MAX-ACCESS not-accessible 2088 STATUS current 2089 DESCRIPTION 2090 "Secondary index into this table identifying the 2091 particular hop." 2092 ::= { mplsTunnelCHopEntry 2 } 2094 mplsTunnelCHopAddrType OBJECT-TYPE 2095 SYNTAX TeHopAddressType 2096 MAX-ACCESS read-only 2097 STATUS current 2098 DESCRIPTION 2099 "The Hop Address Type of this tunnel hop. 2101 Note that lspid(5) is a valid option only 2102 for tunnels signaled via CRLDP." 2103 DEFVAL { ipv4 } 2104 ::= { mplsTunnelCHopEntry 3 } 2106 mplsTunnelCHopIpAddr OBJECT-TYPE 2107 SYNTAX TeHopAddress 2108 MAX-ACCESS read-only 2109 STATUS current 2110 DESCRIPTION 2111 "The Tunnel Hop Address for this tunnel hop. 2113 The type of this address is determined by the 2114 value of the corresponding mplsTunnelCHopAddrType. 2116 If mplsTunnelCHopAddrType is set to unnum(4), then 2117 this value will contain the LSR Router ID of the 2118 unnumbered interface. Otherwise the agent should 2119 set this object to the zero-length string and the 2120 manager SHOULD ignore this object." 2121 DEFVAL { '00000000'h } -- IPv4 address 0.0.0.0 2122 ::= { mplsTunnelCHopEntry 4 } 2124 mplsTunnelCHopIpPrefixLen OBJECT-TYPE 2125 SYNTAX InetAddressPrefixLength 2126 MAX-ACCESS read-only 2127 STATUS current 2128 DESCRIPTION 2129 "If mplsTunnelCHopAddrType is set to ipv4(1) or 2130 ipv6(2), then this value will contain an 2131 appropriate prefix length for the IP address in 2132 object mplsTunnelCHopIpAddr. Otherwise this value 2133 is irrelevant and should be ignored. 2134 " 2135 DEFVAL { 32 } 2136 ::= { mplsTunnelCHopEntry 5 } 2138 mplsTunnelCHopAsNumber OBJECT-TYPE 2139 SYNTAX TeHopAddressAS 2140 MAX-ACCESS read-only 2141 STATUS current 2142 DESCRIPTION 2143 "If mplsTunnelCHopAddrType is set to asnumber(3), 2144 then this value will contain the AS number of this 2145 hop. Otherwise the agent should set this object to 2146 zero-length string and the manager should ignore 2147 this." 2148 ::= { mplsTunnelCHopEntry 6 } 2150 mplsTunnelCHopAddrUnnum OBJECT-TYPE 2151 SYNTAX TeHopAddressUnnum 2152 MAX-ACCESS read-only 2153 STATUS current 2154 DESCRIPTION 2155 "If mplsTunnelCHopAddrType is set to unnum(4), then 2156 this value will contain the unnumbered interface 2157 identifier of this hop. This object should be used 2158 in conjunction with mplsTunnelCHopIpAddr which 2159 would contain the LSR Router ID in this case. 2160 Otherwise the agent should set this object to zero- 2161 length string and the manager should ignore this." 2162 ::= { mplsTunnelCHopEntry 7 } 2164 mplsTunnelCHopLspId OBJECT-TYPE 2165 SYNTAX MplsLSPID 2166 MAX-ACCESS read-only 2167 STATUS current 2168 DESCRIPTION 2169 "If mplsTunnelCHopAddrType is set to lspid(5), then 2170 this value will contain the LSP ID of this hop. 2171 This object is otherwise insignificant and should 2172 contain a value of 0 to indicate this fact." 2173 ::= { mplsTunnelCHopEntry 8 } 2175 mplsTunnelCHopType OBJECT-TYPE 2176 SYNTAX INTEGER { strict(1), 2177 loose(2) 2179 } 2180 MAX-ACCESS read-only 2181 STATUS current 2182 DESCRIPTION 2183 "Denotes whether this is tunnel hop is routed in a 2184 strict or loose fashion." 2185 ::= { mplsTunnelCHopEntry 9 } 2187 -- End of mplsTunnelCHopTable 2189 -- MPLS Tunnel Performance Table. 2191 mplsTunnelPerfTable OBJECT-TYPE 2192 SYNTAX SEQUENCE OF MplsTunnelPerfEntry 2193 MAX-ACCESS not-accessible 2194 STATUS current 2195 DESCRIPTION 2196 "This table provides per-tunnel instance MPLS 2197 performance information." 2198 ::= { mplsTeObjects 9 } 2200 mplsTunnelPerfEntry OBJECT-TYPE 2201 SYNTAX MplsTunnelPerfEntry 2202 MAX-ACCESS not-accessible 2203 STATUS current 2204 DESCRIPTION 2205 "An entry in this table is created by the LSR for 2206 every tunnel. Its is an extension to 2207 mplsTunnelEntry." 2208 AUGMENTS { mplsTunnelEntry } 2209 ::= { mplsTunnelPerfTable 1 } 2211 MplsTunnelPerfEntry ::= SEQUENCE { 2212 mplsTunnelPerfPackets Counter32, 2213 mplsTunnelPerfHCPackets Counter64, 2214 mplsTunnelPerfErrors Counter32, 2215 mplsTunnelPerfBytes Counter32, 2216 mplsTunnelPerfHCBytes Counter64 2217 } 2219 mplsTunnelPerfPackets OBJECT-TYPE 2220 SYNTAX Counter32 2221 MAX-ACCESS read-only 2222 STATUS current 2223 DESCRIPTION 2224 "Number of packets forwarded by the tunnel. 2225 This object should represents the 32-bit 2226 value of the least significant part of the 2227 64-bit value if both mplsTunnelPerfHCPackets 2228 is returned." 2229 ::= { mplsTunnelPerfEntry 1 } 2231 mplsTunnelPerfHCPackets OBJECT-TYPE 2232 SYNTAX Counter64 2233 MAX-ACCESS read-only 2234 STATUS current 2235 DESCRIPTION 2236 "High capacity counter for number of packets 2237 forwarded by the tunnel. " 2238 ::= { mplsTunnelPerfEntry 2 } 2240 mplsTunnelPerfErrors OBJECT-TYPE 2241 SYNTAX Counter32 2242 MAX-ACCESS read-only 2243 STATUS current 2244 DESCRIPTION 2245 "Number of packets dropped because of errors or for 2246 other reasons." 2247 ::= { mplsTunnelPerfEntry 3 } 2249 mplsTunnelPerfBytes OBJECT-TYPE 2250 SYNTAX Counter32 2251 MAX-ACCESS read-only 2252 STATUS current 2253 DESCRIPTION 2254 "Number of bytes forwarded by the tunnel. 2255 This object should represents the 32-bit 2256 value of the least significant part of the 2257 64-bit value if both mplsTunnelPerfHCBytes 2258 is returned." 2259 ::= { mplsTunnelPerfEntry 4 } 2261 mplsTunnelPerfHCBytes OBJECT-TYPE 2262 SYNTAX Counter64 2263 MAX-ACCESS read-only 2264 STATUS current 2265 DESCRIPTION 2266 "High capacity counter for number of bytes forwarded 2267 by the tunnel." 2268 ::= { mplsTunnelPerfEntry 5 } 2270 -- End of mplsTunnelPerfTable 2272 -- CR-LDP Tunnel Resource Table 2274 mplsTunnelCRLDPResTable OBJECT-TYPE 2275 SYNTAX SEQUENCE OF MplsTunnelCRLDPResEntry 2276 MAX-ACCESS not-accessible 2277 STATUS current 2278 DESCRIPTION 2279 "The mplsTunnelCRLDPResTable allows a manager to 2280 specify which CR-LDP-specific resources are desired 2281 for an MPLS tunnel if that tunnel is signaled using 2282 CR-LDP. Note that these attributes are in addition 2283 to those specified in mplsTunnelResourceTable. This 2284 table also allows several tunnels to point to a 2285 single entry in this table, implying that these 2286 tunnels should share resources." 2287 ::= { mplsTeObjects 10 } 2289 mplsTunnelCRLDPResEntry OBJECT-TYPE 2290 SYNTAX MplsTunnelCRLDPResEntry 2291 MAX-ACCESS not-accessible 2292 STATUS current 2293 DESCRIPTION 2294 "An entry in this table represents a set of resources 2295 for an MPLS tunnel established using CRLDP 2296 (mplsTunnelSignallingProto equal to crldp (3)). An 2297 entry can be created by a network administrator or 2298 by an SNMP agent as instructed by any MPLS 2299 signalling protocol." 2300 INDEX { mplsTunnelResourceIndex } 2301 ::= { mplsTunnelCRLDPResTable 1 } 2303 MplsTunnelCRLDPResEntry ::= SEQUENCE { 2304 mplsTunnelCRLDPResMeanBurstSize MplsBurstSize, 2305 mplsTunnelCRLDPResExBurstSize MplsBurstSize, 2306 mplsTunnelCRLDPResFrequency INTEGER, 2307 mplsTunnelCRLDPResWeight Unsigned32, 2308 mplsTunnelCRLDPResFlags Unsigned32, 2309 mplsTunnelCRLDPResRowStatus RowStatus, 2310 mplsTunnelCRLDPResStorageType StorageType 2311 } 2313 mplsTunnelCRLDPResMeanBurstSize OBJECT-TYPE 2314 SYNTAX MplsBurstSize 2315 UNITS "bytes" 2316 MAX-ACCESS read-create 2317 STATUS current 2318 DESCRIPTION 2319 "The mean burst size in bytes." 2320 ::= { mplsTunnelCRLDPResEntry 1 } 2322 mplsTunnelCRLDPResExBurstSize OBJECT-TYPE 2323 SYNTAX MplsBurstSize 2324 UNITS "bytes" 2325 MAX-ACCESS read-create 2326 STATUS current 2327 DESCRIPTION 2328 "The Excess burst size in bytes." 2329 REFERENCE 2330 "CR-LDP Specification, Section 4.3." 2331 ::= { mplsTunnelCRLDPResEntry 2 } 2333 mplsTunnelCRLDPResFrequency OBJECT-TYPE 2334 SYNTAX INTEGER { 2335 unspecified(1), 2336 frequent(2), 2337 veryFrequent(3) 2338 } 2339 MAX-ACCESS read-create 2340 STATUS current 2341 DESCRIPTION 2342 "The granularity of the availability of committed 2343 rate." 2344 REFERENCE 2345 "CR-LDP Specification, Section 4.3." 2346 ::= { mplsTunnelCRLDPResEntry 3 } 2348 mplsTunnelCRLDPResWeight OBJECT-TYPE 2349 SYNTAX Unsigned32(0..255) 2350 MAX-ACCESS read-create 2351 STATUS current 2352 DESCRIPTION 2353 "The relative weight for using excess bandwidth above 2354 its committed rate. The value of 0 means that 2355 weight is not applicable for the CR-LSP." 2356 REFERENCE 2357 "CR-LDP Specification, Section 4.3." 2358 DEFVAL { 0 } 2359 ::= { mplsTunnelCRLDPResEntry 4 } 2361 mplsTunnelCRLDPResFlags OBJECT-TYPE 2362 SYNTAX Unsigned32 (0..63) 2363 MAX-ACCESS read-create 2364 STATUS current 2365 DESCRIPTION 2366 "The value of the 1 byte Flags conveyed as part of 2367 the traffic parameters during the establishment of 2368 the CRLSP. The bits in this object are to be 2369 interpreted as follows. 2371 +--+--+--+--+--+--+--+--+ 2372 | Res |F6|F5|F4|F3|F2|F1| 2373 +--+--+--+--+--+--+--+--+ 2375 Res - These bits are reserved. Zero on transmission. 2377 Ignored on receipt. 2378 F1 - Corresponds to the PDR. 2379 F2 - Corresponds to the PBS. 2380 F3 - Corresponds to the CDR. 2381 F4 - Corresponds to the CBS. 2382 F5 - Corresponds to the EBS. 2383 F6 - Corresponds to the Weight. 2385 Each flag if is a Negotiable Flag corresponding to a 2386 Traffic Parameter. The Negotiable Flag value zero 2387 denotes Not Negotiable and value one denotes 2388 Negotiable." 2389 REFERENCE 2390 "1. Section 4.3, Constraint-Based LSP Setup using 2391 LDP, Jamoussi (Editor), RFC 3212, January 2002" 2392 DEFVAL { 0 } 2393 ::= { mplsTunnelCRLDPResEntry 5 } 2395 mplsTunnelCRLDPResRowStatus OBJECT-TYPE 2396 SYNTAX RowStatus 2397 MAX-ACCESS read-create 2398 STATUS current 2399 DESCRIPTION 2400 "This variable is used to create, modify, and/or 2401 delete a row in this table. When a row in this 2402 table is in active(1) state, no objects in that row 2403 can be modified by the agent except 2404 mplsTunnelCRLDPResRowStatus and 2405 mplsTunnelCRLDPResStorageType." 2406 ::= { mplsTunnelCRLDPResEntry 6 } 2408 mplsTunnelCRLDPResStorageType OBJECT-TYPE 2409 SYNTAX StorageType 2410 MAX-ACCESS read-create 2411 STATUS current 2412 DESCRIPTION 2413 "The storage type for this CR-LDP Resource entry. 2414 Conceptual rows having the value 'permanent' 2415 need not allow write-access to any columnar 2416 objects in the row." 2417 DEFVAL { volatile } 2418 ::= { mplsTunnelCRLDPResEntry 7 } 2420 -- Notifications. 2422 mplsTunnelNotificationEnable OBJECT-TYPE 2423 SYNTAX TruthValue 2424 MAX-ACCESS read-write 2425 STATUS current 2426 DESCRIPTION 2427 "If this object is true, then it enables the 2428 generation of mplsTunnelUp and mplsTunnelDown 2429 traps, otherwise these traps are not emitted." 2430 DEFVAL { false } 2431 ::= { mplsTeObjects 11 } 2433 mplsTunnelUp NOTIFICATION-TYPE 2434 OBJECTS { 2435 mplsTunnelAdminStatus, 2436 mplsTunnelOperStatus 2437 } 2438 STATUS current 2439 DESCRIPTION 2440 "This notification is generated when a 2441 mplsTunnelOperStatus object for one of the 2442 configured tunnels is about to leave the down state 2443 and transition into some other state (but not into 2444 the notPresent state). This other state is 2445 indicated by the included value of 2446 mplsTunnelOperStatus." 2447 ::= { mplsTeNotifications 1 } 2449 mplsTunnelDown NOTIFICATION-TYPE 2450 OBJECTS { 2451 mplsTunnelAdminStatus, 2452 mplsTunnelOperStatus 2453 } 2454 STATUS current 2455 DESCRIPTION 2456 "This notification is generated when a 2457 mplsTunnelOperStatus object for one of the 2458 configured tunnels is about to enter the down state 2459 from some other state (but not from the notPresent 2460 state). This other state is indicated by the 2461 included value of mplsTunnelOperStatus." 2462 ::= { mplsTeNotifications 2 } 2464 mplsTunnelRerouted NOTIFICATION-TYPE 2465 OBJECTS { 2466 mplsTunnelAdminStatus, 2467 mplsTunnelOperStatus 2468 } 2469 STATUS current 2470 DESCRIPTION 2471 "This notification is generated when a tunnel is 2472 rerouted. If the mplsTunnelARHopTable is used, then 2473 this tunnel instance's entry in the 2474 mplsTunnelARHopTable MAY contain the new path for 2475 this tunnel some time after this trap is issued by 2476 the agent." 2477 ::= { mplsTeNotifications 3 } 2479 mplsTunnelReoptimized NOTIFICATION-TYPE 2480 OBJECTS { 2481 mplsTunnelAdminStatus, 2482 mplsTunnelOperStatus 2483 } 2484 STATUS current 2485 DESCRIPTION 2486 "This notification is generated when a tunnel is 2487 reoptimized. If the mplsTunnelARHopTable is used, 2488 then this tunnel instance's entry in the 2489 mplsTunnelARHopTable MAY contain the new path for 2490 this tunnel some time after this trap is issued by 2491 the agent." 2492 ::= { mplsTeNotifications 4 } 2494 -- End of notifications. 2496 -- Module compliance. 2498 mplsTeGroups 2499 OBJECT IDENTIFIER ::= { mplsTeConformance 1 } 2501 mplsTeCompliances 2502 OBJECT IDENTIFIER ::= { mplsTeConformance 2 } 2504 -- Compliance requirement for fully compliant implementations. 2506 mplsTeModuleFullCompliance MODULE-COMPLIANCE 2507 STATUS current 2508 DESCRIPTION 2509 "Compliance statement for agents that provide full 2510 support the MPLS-TE-STD-MIB module." 2512 MODULE IF-MIB -- The Interfaces Group MIB, RFC 2863. 2513 MANDATORY-GROUPS { 2514 ifGeneralInformationGroup, 2515 ifCounterDiscontinuityGroup 2516 } 2518 MODULE -- this module 2520 -- The mandatory group has to be implemented by all 2521 -- LSRs that originate/terminate ESLSPs/tunnels. 2522 -- In addition, depending on the type of tunnels 2523 -- supported, other groups become mandatory as 2524 -- explained below. 2526 MANDATORY-GROUPS { 2527 mplsTunnelGroup, 2528 mplsTunnelScalarGroup 2529 } 2531 GROUP mplsTunnelManualGroup 2532 DESCRIPTION 2533 "This group is mandatory for devices which support 2534 manual configuration of tunnels." 2536 GROUP mplsTunnelSignaledGroup 2537 DESCRIPTION 2538 "This group is mandatory for devices which support 2539 signaled tunnel set up." 2541 GROUP mplsTunnelIsNotIntfcGroup 2542 DESCRIPTION 2543 "This group is mandatory for devices which support 2544 tunnels that are not interfaces." 2546 GROUP mplsTunnelIsIntfcGroup 2547 DESCRIPTION 2548 "This group is mandatory for devices which support 2549 tunnels that are interfaces." 2551 GROUP mplsTunnelCRLDPResOptionalGroup 2552 DESCRIPTION 2553 "Objects in this group are required by 2554 implementations supporting the CR-LDP protocol for 2555 signalling of TE tunnels." 2557 GROUP mplsTeNotificationGroup 2558 DESCRIPTION "This group is mandatory for those implementations 2559 which can implement the notifications 2560 contained in this group." 2562 OBJECT mplsTunnelRowStatus 2563 SYNTAX RowStatus { active(1), notInService(2) } 2564 WRITE-SYNTAX RowStatus { active(1), notInService(2), 2565 createAndGo(4), destroy(6) 2566 } 2567 DESCRIPTION "Support for createAndWait and notReady is not 2568 required." 2570 OBJECT mplsTunnelHopRowStatus 2571 SYNTAX RowStatus { active(1), notInService(2) } 2572 WRITE-SYNTAX RowStatus { active(1), notInService(2), 2573 createAndGo(4), destroy(6) 2574 } 2576 DESCRIPTION "Support for createAndWait and notReady is not 2577 required." 2579 OBJECT mplsTunnelCRLDPResRowStatus 2580 SYNTAX RowStatus { active(1), notInService(2) } 2581 WRITE-SYNTAX RowStatus { active(1), notInService(2), 2582 createAndGo(4), destroy(6) 2583 } 2584 DESCRIPTION "Support for createAndWait and notReady is 2585 not required." 2587 ::= { mplsTeCompliances 1 } 2589 -- Compliance requirement for read-only implementations. 2591 mplsTeModuleReadOnlyCompliance MODULE-COMPLIANCE 2592 STATUS current 2593 DESCRIPTION 2594 "Compliance requirement for implementations that only 2595 provide read-only support for MPLS-TE-STD-MIB. 2596 Such devices can then be monitored but cannot be 2597 configured using this MIB modules." 2599 MODULE -- this module 2601 -- mplsTunnelTable 2603 MANDATORY-GROUPS { 2604 mplsTunnelGroup, 2605 mplsTunnelScalarGroup 2606 } 2608 GROUP mplsTunnelManualGroup 2609 DESCRIPTION 2610 "This group is mandatory for devices which support 2611 manual configuration of tunnels." 2613 GROUP mplsTunnelSignaledGroup 2614 DESCRIPTION 2615 "This group is mandatory for devices which support 2616 signaled tunnel set up." 2618 GROUP mplsTunnelIsNotIntfcGroup 2619 DESCRIPTION 2620 "This group is mandatory for devices which support 2621 tunnels that are not interfaces." 2623 GROUP mplsTunnelIsIntfcGroup 2624 DESCRIPTION 2625 "This group is mandatory for devices which support 2626 tunnels that are interfaces." 2628 GROUP mplsTunnelCRLDPResOptionalGroup 2629 DESCRIPTION 2630 "Objects in this group are required by 2631 implementations supporting the CR-LDP protocol for 2632 signalling of TE tunnels." 2634 GROUP mplsTeNotificationGroup 2635 DESCRIPTION "This group is mandatory for those implementations 2636 which can implement the notifications 2637 contained in this group." 2639 -- mplsTunnelTable 2641 OBJECT mplsTunnelName 2642 MIN-ACCESS read-only 2643 DESCRIPTION 2644 "Write access is not required." 2646 OBJECT mplsTunnelDescr 2647 MIN-ACCESS read-only 2648 DESCRIPTION 2649 "Write access is not required." 2651 OBJECT mplsTunnelIsIf 2652 MIN-ACCESS read-only 2653 DESCRIPTION 2654 "Write access is not required." 2656 OBJECT mplsTunnelIfIndex 2657 DESCRIPTION 2658 "Write access is not required." 2660 OBJECT mplsTunnelXCPointer 2661 MIN-ACCESS read-only 2662 DESCRIPTION 2663 "Write access is not required." 2665 OBJECT mplsTunnelSignallingProto 2666 MIN-ACCESS read-only 2667 DESCRIPTION 2668 "Write access is not required." 2670 OBJECT mplsTunnelSetupPrio 2671 MIN-ACCESS read-only 2672 DESCRIPTION 2673 "Write access is not required." 2675 OBJECT mplsTunnelHoldingPrio 2676 MIN-ACCESS read-only 2677 DESCRIPTION 2678 "Write access is not required." 2680 OBJECT mplsTunnelSessionAttributes 2681 MIN-ACCESS read-only 2682 DESCRIPTION 2683 "Write access is not required." 2685 OBJECT mplsTunnelLocalProtectInUse 2686 MIN-ACCESS read-only 2687 DESCRIPTION 2688 "Write access is not required." 2690 OBJECT mplsTunnelResourcePointer 2691 MIN-ACCESS read-only 2692 DESCRIPTION 2693 "Write access is not required." 2695 OBJECT mplsTunnelInstancePriority 2696 MIN-ACCESS read-only 2697 DESCRIPTION 2698 "Write access is not required." 2700 OBJECT mplsTunnelHopTableIndex 2701 MIN-ACCESS read-only 2702 DESCRIPTION 2703 "Write access is not required." 2705 OBJECT mplsTunnelIncludeAnyAffinity 2706 MIN-ACCESS read-only 2707 DESCRIPTION 2708 "Write access is not required." 2710 OBJECT mplsTunnelIncludeAllAffinity 2711 MIN-ACCESS read-only 2712 DESCRIPTION 2713 "Write access is not required." 2715 OBJECT mplsTunnelExcludeAnyAffinity 2716 MIN-ACCESS read-only 2717 DESCRIPTION 2718 "Write access is not required." 2720 OBJECT mplsTunnelPathInUse 2721 MIN-ACCESS read-only 2722 DESCRIPTION 2723 "Write access is not required." 2725 OBJECT mplsTunnelRole 2726 MIN-ACCESS read-only 2727 DESCRIPTION 2728 "Write access is not required." 2730 OBJECT mplsTunnelAdminStatus 2731 SYNTAX INTEGER { up (1), down (2) } 2732 MIN-ACCESS read-only 2733 DESCRIPTION 2734 "Only up and down states must be supported. Write 2735 access is not required." 2737 OBJECT mplsTunnelRowStatus 2738 SYNTAX RowStatus { active(1) } 2739 MIN-ACCESS read-only 2740 DESCRIPTION "Write access is not required." 2742 -- mplsTunnelHopTable 2744 OBJECT mplsTunnelHopAddrType 2745 MIN-ACCESS read-only 2746 DESCRIPTION "Write access is not required." 2748 OBJECT mplsTunnelHopIpAddr 2749 MIN-ACCESS read-only 2750 DESCRIPTION "Write access is not required." 2752 OBJECT mplsTunnelHopIpPrefixLen 2753 MIN-ACCESS read-only 2754 DESCRIPTION 2755 "Write access is not required." 2757 OBJECT mplsTunnelHopAddrUnnum 2758 MIN-ACCESS read-only 2759 DESCRIPTION 2760 "Write access is not required." 2762 OBJECT mplsTunnelHopAsNumber 2763 MIN-ACCESS read-only 2764 DESCRIPTION 2765 "Write access is not required." 2767 OBJECT mplsTunnelHopLspId 2768 MIN-ACCESS read-only 2769 DESCRIPTION 2770 "Write access is not required." 2772 OBJECT mplsTunnelHopType 2773 SYNTAX INTEGER { strict(1) } 2774 MIN-ACCESS read-only 2775 DESCRIPTION 2776 "loose(2) need not be supported. Write access is 2777 not required." 2779 OBJECT mplsTunnelHopInclude 2780 MIN-ACCESS read-only 2781 DESCRIPTION "Write access is not required." 2783 OBJECT mplsTunnelHopPathOptionName 2784 MIN-ACCESS read-only 2785 DESCRIPTION "Write access is not required." 2787 OBJECT mplsTunnelHopEntryPathComp 2788 MIN-ACCESS read-only 2789 DESCRIPTION "Write access is not required." 2791 OBJECT mplsTunnelHopRowStatus 2792 SYNTAX RowStatus { active(1) } 2793 MIN-ACCESS read-only 2794 DESCRIPTION "Write access is not required." 2796 OBJECT mplsTunnelHopStorageType 2797 MIN-ACCESS read-only 2798 DESCRIPTION "Write access is not required." 2800 -- mplsTunnelResourceTable 2802 OBJECT mplsTunnelResourceMaxRate 2803 MIN-ACCESS read-only 2804 DESCRIPTION "Write access is not required." 2806 OBJECT mplsTunnelResourceMeanRate 2807 MIN-ACCESS read-only 2808 DESCRIPTION "Write access is not required." 2810 OBJECT mplsTunnelResourceMaxBurstSize 2811 MIN-ACCESS read-only 2812 DESCRIPTION "Write access is not required." 2814 OBJECT mplsTunnelResourceMeanBurstSize 2815 MIN-ACCESS read-only 2816 DESCRIPTION "Write access is not required." 2818 OBJECT mplsTunnelResourceExBurstSize 2819 MIN-ACCESS read-only 2820 DESCRIPTION 2821 "Write access is not required." 2823 OBJECT mplsTunnelResourceFrequency 2824 MIN-ACCESS read-only 2825 DESCRIPTION "Write access is not required." 2826 OBJECT mplsTunnelResourceWeight 2827 MIN-ACCESS read-only 2828 DESCRIPTION "Write access is not required." 2830 OBJECT mplsTunnelResourceRowStatus 2831 SYNTAX RowStatus { active(1) } 2832 MIN-ACCESS read-only 2833 DESCRIPTION "Write access is not required." 2835 OBJECT mplsTunnelResourceStorageType 2836 MIN-ACCESS read-only 2837 DESCRIPTION "Write access is not required." 2839 -- mplsTunnelCRLDPResTable 2841 OBJECT mplsTunnelCRLDPResMeanBurstSize 2842 MIN-ACCESS read-only 2843 DESCRIPTION "Write access is not required." 2845 OBJECT mplsTunnelCRLDPResExBurstSize 2846 MIN-ACCESS read-only 2847 DESCRIPTION "Write access is not required." 2849 OBJECT mplsTunnelCRLDPResFrequency 2850 MIN-ACCESS read-only 2851 DESCRIPTION "Write access is not required." 2853 OBJECT mplsTunnelCRLDPResWeight 2854 MIN-ACCESS read-only 2855 DESCRIPTION "Write access is not required." 2857 OBJECT mplsTunnelCRLDPResFlags 2858 MIN-ACCESS read-only 2859 DESCRIPTION "Write access is not required." 2861 OBJECT mplsTunnelCRLDPResRowStatus 2862 SYNTAX RowStatus { active(1) } 2863 MIN-ACCESS read-only 2864 DESCRIPTION "Write access is not required." 2866 OBJECT mplsTunnelCRLDPResStorageType 2867 MIN-ACCESS read-only 2868 DESCRIPTION "Write access is not required." 2870 ::= { mplsTeCompliances 2 } 2872 -- Units of conformance. 2874 mplsTunnelGroup OBJECT-GROUP 2875 OBJECTS { 2876 mplsTunnelIndexNext, 2877 mplsTunnelName, 2878 mplsTunnelDescr, 2879 mplsTunnelOwner, 2880 mplsTunnelXCPointer, 2881 mplsTunnelIfIndex, 2882 mplsTunnelHopTableIndex, 2883 mplsTunnelARHopTableIndex, 2884 mplsTunnelCHopTableIndex, 2885 mplsTunnelAdminStatus, 2886 mplsTunnelOperStatus, 2887 mplsTunnelRowStatus, 2888 mplsTunnelNotificationEnable, 2889 mplsTunnelStorageType, 2890 mplsTunnelConfigured, 2891 mplsTunnelActive, 2892 mplsTunnelPrimaryInstance, 2893 mplsTunnelPrimaryUpTime, 2894 mplsTunnelPathChanges, 2895 mplsTunnelLastPathChange, 2896 mplsTunnelCreationTime, 2897 mplsTunnelStateTransitions, 2898 mplsTunnelIncludeAnyAffinity, 2899 mplsTunnelIncludeAllAffinity, 2900 mplsTunnelExcludeAnyAffinity, 2901 mplsTunnelPerfPackets, 2902 mplsTunnelPerfHCPackets, 2903 mplsTunnelPerfErrors, 2904 mplsTunnelPerfBytes, 2905 mplsTunnelPerfHCBytes, 2906 mplsTunnelResourcePointer, 2907 mplsTunnelInstancePriority, 2908 mplsTunnelPathInUse, 2909 mplsTunnelRole, 2910 mplsTunnelTotalUpTime, 2911 mplsTunnelInstanceUpTime, 2912 mplsTunnelResourceIndexNext, 2913 mplsTunnelResourceMaxRate, 2914 mplsTunnelResourceMeanRate, 2915 mplsTunnelResourceMaxBurstSize, 2916 mplsTunnelResourceMeanBurstSize, 2917 mplsTunnelResourceExBurstSize, 2918 mplsTunnelResourceFrequency, 2919 mplsTunnelResourceWeight, 2920 mplsTunnelResourceRowStatus, 2921 mplsTunnelResourceStorageType, 2922 mplsTunnelARHopAddrType, 2923 mplsTunnelARHopIpAddr, 2924 mplsTunnelARHopAddrUnnum, 2925 mplsTunnelARHopLspId, 2926 mplsTunnelCHopAddrType, 2927 mplsTunnelCHopIpAddr, 2928 mplsTunnelCHopIpPrefixLen, 2929 mplsTunnelCHopAsNumber, 2930 mplsTunnelCHopAddrUnnum, 2931 mplsTunnelCHopLspId, 2932 mplsTunnelCHopType 2933 } 2934 STATUS current 2935 DESCRIPTION 2936 "Necessary, but not sufficient, set of objects to 2937 implement tunnels. In addition, depending on the 2938 type of the tunnels supported (for example, 2939 manually configured or signaled, persistent or non- 2940 persistent, etc.), the following other groups 2941 defined below are mandatory: mplsTunnelManualGroup 2942 and/or mplsTunnelSignaledGroup, 2943 mplsTunnelIsNotIntfcGroup and/or 2944 mplsTunnelIsIntfcGroup." 2945 ::= { mplsTeGroups 1 } 2947 mplsTunnelManualGroup OBJECT-GROUP 2948 OBJECTS { mplsTunnelSignallingProto } 2949 STATUS current 2950 DESCRIPTION 2951 "Object(s) needed to implement manually configured 2952 tunnels." 2953 ::= { mplsTeGroups 2 } 2955 mplsTunnelSignaledGroup OBJECT-GROUP 2956 OBJECTS { 2957 mplsTunnelSetupPrio, 2958 mplsTunnelHoldingPrio, 2959 mplsTunnelSignallingProto, 2960 mplsTunnelLocalProtectInUse, 2961 mplsTunnelSessionAttributes, 2962 mplsTunnelHopListIndexNext, 2963 mplsTunnelHopAddrType, 2964 mplsTunnelHopIpAddr, 2965 mplsTunnelHopIpPrefixLen, 2966 mplsTunnelHopAddrUnnum, 2967 mplsTunnelHopAsNumber, 2968 mplsTunnelHopLspId, 2969 mplsTunnelHopType, 2970 mplsTunnelHopInclude, 2971 mplsTunnelHopPathOptionName, 2972 mplsTunnelHopEntryPathComp, 2973 mplsTunnelHopRowStatus, 2974 mplsTunnelHopStorageType 2975 } 2976 STATUS current 2977 DESCRIPTION 2978 "Objects needed to implement signaled tunnels." 2979 ::= { mplsTeGroups 3 } 2981 mplsTunnelScalarGroup OBJECT-GROUP 2982 OBJECTS { 2983 mplsTunnelConfigured, 2984 mplsTunnelActive, 2985 mplsTunnelTEDistProto, 2986 mplsTunnelMaxHops, 2987 mplsTunnelNotificationMaxRate 2988 } 2989 STATUS current 2990 DESCRIPTION 2991 "Scalar object needed to implement MPLS tunnels." 2992 ::= { mplsTeGroups 4 } 2994 mplsTunnelIsIntfcGroup OBJECT-GROUP 2995 OBJECTS { mplsTunnelIsIf } 2996 STATUS current 2997 DESCRIPTION 2998 "Objects needed to implement tunnels that are 2999 interfaces." 3000 ::= { mplsTeGroups 5 } 3002 mplsTunnelIsNotIntfcGroup OBJECT-GROUP 3003 OBJECTS { mplsTunnelIsIf } 3004 STATUS current 3005 DESCRIPTION 3006 "Objects needed to implement tunnels that are not 3007 interfaces." 3008 ::= { mplsTeGroups 6 } 3010 mplsTunnelCRLDPResOptionalGroup OBJECT-GROUP 3011 OBJECTS { 3012 mplsTunnelCRLDPResMeanBurstSize, 3013 mplsTunnelCRLDPResExBurstSize, 3014 mplsTunnelCRLDPResFrequency, 3015 mplsTunnelCRLDPResWeight, 3016 mplsTunnelCRLDPResFlags, 3017 mplsTunnelCRLDPResRowStatus, 3018 mplsTunnelCRLDPResStorageType 3019 } 3020 STATUS current 3021 DESCRIPTION 3022 "Set of objects implemented for resources applicable 3023 for tunnels signaled using CR-LDP." 3025 ::= { mplsTeGroups 7 } 3027 mplsTeNotificationGroup NOTIFICATION-GROUP 3028 NOTIFICATIONS { 3029 mplsTunnelUp, 3030 mplsTunnelDown, 3031 mplsTunnelRerouted, 3032 mplsTunnelReoptimized 3033 } 3034 STATUS current 3035 DESCRIPTION 3036 "Set of notifications implemented in this module. 3037 None is mandatory." 3038 ::= { mplsTeGroups 8 } 3040 END 3042 12. Security Considerations 3044 It is clear that this MIB module is potentially useful for 3045 monitoring of MPLS TE tunnels. This MIB module can also 3046 be used for configuration of certain objects, and anything 3047 that can be configured can be incorrectly configured, with 3048 potentially disastrous results. 3050 There are a number of management objects defined in this 3051 MIB module with a MAX-ACCESS clause of read-write and/or 3052 read-create. Such objects may be considered sensitive or 3053 vulnerable in some network environments. The support for 3054 SET operations in a non-secure environment without proper 3055 protection can have a negative effect on network 3056 operations. These are the tables and objects and their 3057 sensitivity/vulnerability: 3059 - the mplsTunnelTable, mplsTunnelHopTable, 3060 mplsTunnelResourceTable, and 3061 mplsTunnelCRLDPResTable collectively contain 3062 objects to provision MPLS tunnels, tunnel hops, and 3063 tunnel resources. Unauthorized access to objects 3064 in these tables, could result in disruption of 3065 traffic on the network. This is especially true if 3066 a tunnel has been established. The use of stronger 3067 mechanisms such as SNMPv3 security should be 3068 considered where possible. Specifically, SNMPv3 3069 VACM and USM MUST be used with any v3 agent which 3070 implements this MIB. Administrators should 3071 consider whether read access to these objects 3072 should be allowed, since read access may be 3073 undesirable under certain circumstances. 3075 Some of the readable objects in this MIB module "i.e., 3076 objects with a MAX-ACCESS other than not-accessible" may 3077 be considered sensitive or vulnerable in some network 3078 environments. It is thus important to control even GET 3079 and/or NOTIFY access to these objects and possibly to even 3080 encrypt the values of these objects when sending them over 3081 the network via SNMP. These are the tables and objects 3082 and their sensitivity/vulnerability: 3084 - the mplsTunnelTable, mplsTunnelHopTable, 3085 mplsTunnelResourceTable, mplsTunnelARHopTable, 3086 mplsTunnelCHopTable, mplsTunnelPerfTable, and 3087 mplsTunnelCRLDPResTable collectively show the MPLE- 3088 TE tunnel network topology and its performance 3089 characteristics. If an Administrator does not want 3090 to reveal this information, then these tables 3091 should be considered sensitive/vulnerable. 3093 SNMP versions prior to SNMPv3 did not include adequate 3094 security. Even if the network itself is secure "for 3095 example by using IPSec", even then, there is no control as 3096 to who on the secure network is allowed to access and 3097 GET/SET "read/change/create/delete" the objects in this 3098 MIB module. 3100 It is RECOMMENDED that implementers consider the security 3101 features as provided by the SNMPv3 framework "see 3102 [RFC3410], section 8", including full support for the 3103 SNMPv3 cryptographic mechanisms "for authentication and 3104 privacy". 3106 Further, deployment of SNMP versions prior to SNMPv3 is 3107 NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy 3108 SNMPv3 and to enable cryptographic security. It is then a 3109 customer/operator responsibility to ensure that the SNMP 3110 entity giving access to an instance of this MIB module, is 3111 properly configured to give access to the objects only to 3112 those principals "users" that have legitimate. 3114 13. Acknowledgments 3116 We wish to thank Adrian Farrel, Bert Wijnen, Eric Gray, 3117 Joan Cucchiara, Patrick Kerharo, Paul Langille, Marcus 3118 Brunner, Mike MacFaden and Mike Piecuch for their comments 3119 on this document. 3121 14. References 3122 14.1. Normative References 3124 [RFC2119] S. Bradner, "Key Words for use in RFCs to 3125 Indicate Requirement Levels", RFC 2119, BCP 3126 14, March 1997. 3128 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, 3129 J., Case, J., Rose, M., and S. Waldbusser, 3130 "Structure of Management Information Version 3131 2 (SMIv2)", STD 58, RFC 2578, April 1999. 3133 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, 3134 J., Case, J., Rose, M., and S. Waldbusser, 3135 "Textual Conventions for SMIv2", STD 58, RFC 3136 2579, April 1999. 3138 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, 3139 J., Case, J., Rose, M., and S. Waldbusser, 3140 "Conformance Statements for SMIv2", STD 58, 3141 RFC 2580, April 1999. 3143 [RFC2702] Awduche, D., Malcolm, J., Agogbua, J., 3144 O'Dell, M., and J. McManus, "Requirements 3145 for Traffic Engineering Over MPLS", RFC 3146 2702, September 1999. 3148 [RFC2863] McCloghrie, K. and F. Kastenholtz, "The 3149 Interfaces Group MIB ", RFC 2863, June 2000. 3151 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 3152 "Multiprotocol Label Switching 3153 Architecture", RFC 3031, January 2001. 3155 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., 3156 Srinivasan, V., and G. Swallow, "RSVP-TE: 3157 Extensions to RSVP for LSP Tunnels", RFC 3158 3209, December 2001. 3160 [RFC3291] Daniele, M., Haberman, B., Routhier, S., and 3161 J. Schoenwaelder, "Textual Conventions for 3162 Internet Network Addresses", RFC 3291, May 3163 2002. 3165 [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, 3166 "An Architecture for Describing Simple 3167 Network Management Protocol (SNMP) 3168 Management Frameworks", RFC 3411, December 3169 2002. 3171 [TCMIB] Nadeau, T. and J. Cucchiara (Editors), 3172 "Definition of Textual Conventions and 3173 OBJECT-IDENTITIES for Multi-Protocol Label 3174 Switching (MPLS) Management", Internet Draft 3175 , June 2003. 3177 [LSRMIB] Srinivasan, C., Viswanathan, A. and T. 3178 Nadeau, "MPLS Multiprotocol Label Switching 3179 (MPLS) Label Switch Router Management 3180 Information Base ", Internet Draft , November 2003. 3183 [CRLDP] B. Jamoussi (Editor), "Constraint-Based LSP 3184 Setup using LDP", RFC 3212, January 2002. 3186 14.2. Informative References 3188 [RFC2026] S. Bradner, "The Internet Standards Process 3189 -- Revision 3", RFC 2026, October 1996. 3191 [RFC2401] Kent, S., and R. Atkinson, "Security 3192 Architecture for the Internet Protocol", RFC 3193 2401, November 1998. 3195 [RFC3410] Case, J., Mundy, R., Partain, D., and B. 3196 Stewart, "Introduction and Applicability 3197 Statement for Internet Standard Management 3198 Framework", RFC 3410, December 2002. 3200 15. Authors' Addresses 3202 Cheenu Srinivasan 3203 Bloomberg L.P. 3204 499 Park Ave., New York, NY 10022 3205 Phone: +1-212-893-3682 3206 Email: cheenu@bloomberg.net 3208 Arun Viswanathan 3209 Force10 Networks, Inc. 3210 1440 McCarthy Blvd 3211 Milpitas, CA 95035 3212 Phone: +1-408-571-3516 3213 Email: arunv@force10networks.com 3215 Thomas D. Nadeau 3216 Cisco Systems, Inc. 3217 300 Apollo Drive 3218 Chelmsford, MA 01824 3219 Phone: +1-978-244-3051 3220 Email: tnadeau@cisco.com 3222 16. Full Copyright Statement 3224 Copyright (C) The Internet Society (2003). All Rights 3225 Reserved. 3227 This document and translations of it may be copied and 3228 furnished to others, and derivative works that comment on 3229 or otherwise explain it or assist in its implementation may 3230 be prepared, copied, published and distributed, in whole or 3231 in part, without restriction of any kind, provided that the 3232 above copyright notice and this paragraph are included on 3233 all such copies and derivative works. However, this 3234 document itself may not be modified in any way, such as by 3235 removing the copyright notice or references to the Internet 3236 Society or other Internet organizations, except as needed 3237 for the purpose of developing Internet standards in which 3238 case the procedures for copyrights defined in the Internet 3239 Standards process must be followed, or as required to 3240 translate it into languages other than English. 3242 The limited permissions granted above are perpetual and 3243 will not be revoked by the Internet Society or its 3244 successors or assigns. This document and the information 3245 contained herein is provided on an "AS IS" basis and THE 3246 INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE 3247 DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 3248 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 3249 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 3250 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 3251 PURPOSE. 3253 17. Intellectual Property Notice 3255 The IETF takes no position regarding the validity or scope 3256 of any intellectual property or other rights that might be 3257 claimed to pertain to the implementation or use of the 3258 technology described in this document or the extent to 3259 which any license under such rights might or might not be 3260 available; neither does it represent that it has made any 3261 effort to identify any such rights. Information on the 3262 IETF's procedures with respect to rights in standards-track 3263 and standards-related documentation can be found in BCP-11 3264 [RFC2028]. Copies of claims of rights made available for 3265 publication and any assurances of licenses to be made 3266 available, or the result of an attempt made to obtain a 3267 general license or permission for the use of such 3268 proprietary rights by implementors or users of this 3269 specification can be obtained from the IETF Secretariat. 3270 The IETF invites any interested party to bring to its 3271 attention any copyrights, patents or patent applications, 3272 or other proprietary rights that may cover technology that 3273 may be required to practice this standard. Please address 3274 the information to the IETF Executive Director. 3276 18. IANA Considerations 3278 As described in [MPLSMGMT] and as requested in the MPLS-TC-STD-MIB 3279 [MPLSTCMIB], MPLS related standards track MIB modules should be 3280 rooted under the mplsStdMIB subtree. There are 4 MPLS MIB Modules 3281 contained in this document, each of the following "IANA 3282 Considerations" subsections requests IANA for a new assignment under 3283 the mplsStdMIB subtree. New assignments can only be made via a 3284 Standards Action as specified in [RFC2434]. 3286 18.1. IANA Considerations for MPLS-TE-STD-MIB 3288 The IANA is requested to assign { mplsStdMIB 3 } to the 3289 MPLS-TE-STD-MIB module specified in this document.