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