idnits 2.17.1 draft-ietf-mpls-te-mib-09.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. == There are 4 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 312: '...2-bit byte and packet counters MUST be...' RFC 2119 keyword, line 315: '... packet counters MUST be supported and...' RFC 2119 keyword, line 316: '...t octet counters MUST be supported. Fo...' RFC 2119 keyword, line 318: '...ters AND 64-bit octet counters MUST be...' RFC 2119 keyword, line 450: '... -- RowPointer MUST point to the fir...' (26 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 699 has weird spacing: '...ries in mplsT...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (November 2002) is 7832 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 227, but not defined == Unused Reference: 'Assigned' is defined on line 3027, but no explicit reference was found in the text == Unused Reference: 'TCMIB' is defined on line 3032, but no explicit reference was found in the text == Unused Reference: 'RFC2026' is defined on line 3078, but no explicit reference was found in the text == Unused Reference: 'RFC2851' is defined on line 3128, but no explicit reference was found in the text == Unused Reference: 'RFC3209' is defined on line 3140, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1700 (ref. 'Assigned') (Obsoleted by RFC 3232) -- Possible downref: Non-RFC (?) normative reference: ref. 'TCMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'LSRMIB' ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2401 (Obsoleted by RFC 4301) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2851 (Obsoleted by RFC 3291) Summary: 18 errors (**), 0 flaws (~~), 9 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Cheenu Srinivasan 2 Internet Draft Parama Networks, Inc. 3 Expires: May 2003 4 Arun Viswanathan 5 Force10 Networks, Inc. 7 Thomas D. Nadeau 8 Cisco Systems, Inc. 10 November 2002 12 Multiprotocol Label Switching (MPLS) Traffic Engineering 13 Management Information Base 15 draft-ietf-mpls-te-mib-09.txt 17 Status of this Memo 19 This document is an Internet-Draft and is in full 20 conformance with all provisions of Section 10 of RFC 2026. 22 Internet-Drafts are working documents of the Internet 23 Engineering Task Force (IETF), its areas, and its working 24 groups. Note that other groups may also distribute working 25 documents as Internet-Drafts. 27 Internet-Drafts are draft documents valid for a maximum of 28 six months and may be updated, replaced, or obsoleted by 29 other documents at any time. It is inappropriate to use 30 Internet-Drafts as reference material or to cite them other 31 than as "work in progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/ietf/1id-abstracts.txt. 36 The list of Internet-Draft Shadow Directories can be 37 accessed at http://www.ietf.org/shadow.html. 39 Abstract 41 This memo defines a portion of the Management Information 42 Base (MIB) for use with network management protocols in 43 the Internet community. In particular, it describes 44 managed objects for Multiprotocol Label Switching (MPLS) 45 based traffic engineering. 47 Table of Contents 49 1. Introduction ........................................... 2 50 2. Terminology ............................................ 2 51 3. The SNMP Management Framework .......................... 3 52 4. Feature List ........................................... 4 53 5. Outline ................................................ 4 54 5.1. Summary of Traffic Engineering MIB ................... 5 55 6. Brief Description of MIB Objects ....................... 5 56 6.1. mplsTunnelTable ...................................... 5 57 6.2. mplsTunnelResourceTable .............................. 6 58 6.3. mplsTunnelHopTable ................................... 6 59 6.4. mplsTunnelARHopTable ................................. 6 60 6.5. mplsTunnelCHoptable .................................. 7 61 6.6. mplsTunnelPerfTable .................................. 7 62 6.7. mplsTunnelCRLDPResTable .............................. 7 63 7. Use of 32-bit and 64-bit Counters ...................... 7 64 8. Application of the Interface Group to MPLS Tunnels ..... 7 65 8.1. Support of the MPLS Tunnel Interface by ifTable ...... 8 66 9. Example of Tunnel Setup ............................... 10 67 10. The Use of RowPointer ................................ 12 68 11. MPLS Traffic Engineering MIB Definitions ............. 12 69 12. Security Considerations .............................. 63 70 13. Acknowledgments ...................................... 64 71 14. References ........................................... 64 72 15. Authors' Addresses ................................... 67 73 16. Full Copyright Statement ............................. 67 75 1. Introduction 77 This memo defines a portion of the Management Information 78 Base (MIB) for use with network management protocols in the 79 Internet community. In particular, it describes managed 80 objects for modeling a Multi-Protocol Label Switching 81 (MPLS) [RFC3031] based traffic engineering. This MIB should 82 be used in conjunction with the companion document [LSRMIB] 83 for MPLS based traffic engineering configuration and 84 management. 86 2. Terminology 88 This document uses terminology from the MPLS architecture 89 document [RFC3031] and MPLS Label Switching Router MIB 90 [LSRMIB]. Some frequently used terms are described next. 92 An explicitly routed LSP (ERLSP) is referred to as an MPLS 93 tunnel. It consists of one in-segment and/or one out- 94 segment at the ingress/egress LSRs, each segment being 95 associated with one MPLS interface. These are also 96 referred to as tunnel segments. Additionally, at an 97 intermediate LSR, we model a connection as consisting of 98 one or more in-segments and/or one or more out-segments. 99 The binding or interconnection between in-segments and out- 100 segments in performed using a cross-connect. These objects 101 are defined in the MPLS Label Switching Router MIB 102 [LSRMIB]. 104 3. The SNMP Management Framework 106 The SNMP Management Framework presently consists of five 107 major components: 109 - An overall architecture, described in RFC 2571 110 [RFC2571]. 112 - Mechanisms for describing and naming objects and events 113 for the purpose of management. The first version of 114 this Structure of Management Information (SMI) is 115 called SMIv1 and described in STD 16, RFC 1155 116 [RFC1155], STD 16, RFC 1212 [RFC1212] and STD 16, RFC 117 1215 [RFC1215]. The second version, called SMIv2, is 118 described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 119 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 121 - Message protocols for transferring management 122 information. The first version of the SNMP message 123 protocol is called SNMPv1 and described in STD 15, RFC 124 1157 [RFC1157]. A second version of the SNMP message 125 protocol, which is not an Internet standards track 126 protocol, is called SNMPv2c and described in RFC 1901 127 [RFC1901] and RFC 1906 [RFC1906]. The third version of 128 the message protocol is called SNMPv3 and described in 129 RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 130 [RFC2574]. 132 - Protocol operations for accessing management 133 information. The first set of protocol operations and 134 associated PDU formats is described in STD 15, RFC 1157 135 [RFC1157]. A second set of protocol operations and 136 associated PDU formats is described in RFC 1905 137 [RFC1905]. 139 - A set of fundamental applications described in RFC 2573 140 [RFC2573] and the view-based access control mechanism 141 described in RFC 2575 [RFC2575]. 143 A more detailed introduction to the current SNMP Management 144 Framework can be found in RFC 2570 [RFC2570]. 146 Managed objects are accessed via a virtual information 147 store, termed the Management Information Base or MIB. 148 Objects in the MIB are defined using the mechanisms defined 149 in the SMI. 151 This memo specifies a MIB module that is compliant to the 152 SMIv2. A MIB conforming to the SMIv1 can be produced 153 through the appropriate translations. The resulting 154 translated MIB must be semantically equivalent, except 155 where objects or events are omitted because no translation 156 is possible (use of Counter64). Some machine-readable 157 information in SMIv2 will be converted into textual 158 descriptions in SMIv1 during the translation process. 159 However, this loss of machine-readable information is not 160 considered to change the semantics of the MIB. 162 4. Feature List 164 The MPLS traffic engineering MIB is designed to satisfy the 165 following requirements and constraints. 167 - The MIB supports configuration of point-to-point 168 unidirectional tunnels. 170 - MPLS tunnels need not be interfaces, but it is possible 171 to configure a tunnel as an interface. 173 - The MIB supports tunnel establishment via an MPLS 174 signalling protocol wherein the tunnel parameters are 175 specified using this MIB at the head end of the LSP and 176 end-to-end tunnel LSP establishment is accomplished via 177 signalling. The MIB also supports manually configured 178 tunnels, i.e. those for which label associations at 179 each hop of the tunnel LSP are provisioned by the 180 administrator via the LSR MIB [LSRMIB]. 182 - The MIB supports persistent as well as non-persistent 183 tunnels. 185 5. Outline 187 Traffic engineering support for MPLS tunnels requires the 188 following configuration. 190 - Setting up MPLS tunnels along with appropriate 191 configuration parameters. 193 - Configuring tunnel loose and strict source routed hops. 195 These actions may need to be accompanied with corresponding 196 actions using [LSRMIB] to establish and configure tunnel 197 segments, if this is done manually. Also, the in-segment 198 and out-segment performance tables, mplsInSegmentPerfTable 199 and mplsOutSegmentPerfTable [LSRMIB], should be used to 200 determine performance of the tunnels and tunnel segments. 202 5.1. Summary of Traffic Engineering MIB 204 The MIB objects for performing these actions consist of the 205 following tables. 207 - Tunnel table (mplsTunnelTable) for setting up MPLS 208 tunnels. 210 - Resource table (mplsTunnelResourceTable) for setting up 211 the tunnel resources. 213 - Tunnel specified, actual, and computed hop tables 214 (mplsTunnelHopTable, mplsTunnelARHopTable, and 215 mplsTunnelCHopTable) for strict and loose source routed 216 MPLS tunnel hops. 218 - CRLDP resource table (mplsTunnelCRLDPResTable) for 219 specifying resource objects applicable to tunnels 220 signaled using CRLDP. 222 These tables are described in the subsequent sections. 224 6. Brief Description of MIB Objects 226 The objects described in this section support the 227 functionality described in documents [RSVPTE] and [CRLDP]. 228 The tables support both manually configured and signaled 229 tunnels. 231 6.1. mplsTunnelTable 233 The mplsTunnelTable allows new MPLS tunnels to be created 234 between an MPLS LSR and a remote endpoint, and existing 235 tunnels to be reconfigured or removed. Note that we only 236 support point-to-point tunnel segments, although multi- 237 point-to-point and point-to-multi-point connections are 238 supported by an LSR acting as a cross-connect. Each MPLS 239 tunnel can thus have one out-segment originating at an LSR 240 and/or one in-segment terminating at that LSR. 242 mplsTunnelTable does not define the in and out segments 243 forming the tunnel. Instead, these are defined by creating 244 rows in the in-segment and out-segment tables, defining 245 relationships in the cross-connect table and referring to 246 these rows in the mplsTunnelTable using a cross-connect 247 index, mplsTunnelXCIndex. These segment and cross-connect 248 related objects are defined in [LSRMIB]. 250 6.2. mplsTunnelResourceTable 252 mplsTunnelResourceTable is used to indicate the resources 253 required for a tunnel. Multiple tunnels may share the same 254 resources by pointing to the same entry in this table. 255 Tunnels that do not share resources must point to separate 256 entries in this table. 258 6.3. mplsTunnelHopTable 260 mplsTunnelHopTable is used to indicate the hops, strict or 261 loose, for an MPLS tunnel defined in mplsTunnelTable, when 262 it is established via signalling. Multiple tunnels may 263 share the same hops by pointing to the same entry in this 264 table. Each row also has a secondary index, 265 mplsTunnelHopIndex, corresponding to the next hop of this 266 tunnel. The scalar mplsTunnelMaxHops indicates the maximum 267 number of hops that can be specified on each tunnel 268 supported by this LSR. 270 6.4. mplsTunnelARHopTable 272 mplsTunnelARHopTable is used to indicate the actual hops 273 traversed by a tunnel as reported by the MPLS signalling 274 protocol after the tunnel is setup. The support of this 275 table is optional since not all MPLS signalling protocol 276 may support this feature. 278 6.5. mplsTunnelCHoptable 280 mplsTunnelCHopTable lists the actual hops computed by a 281 constraint-based routing algorithm based on the 282 mplsTunnelHopTable. The support of this table is optional 283 since not all implementations may support computation of 284 hop list using a constraint-based routing protocol. 286 6.6. mplsTunnelPerfTable 288 mplsTunnelPerfTable provides several counters to measure 289 the performance of the MPLS tunnels. This table augments 290 mplsTunnelTable. 292 6.7. mplsTunnelCRLDPResTable 294 mplsTunnelCRLDPResTable contains resource information for 295 those tunnels that are signaled using CRLDP [CRLDP]. This 296 is a sparse extension to mplsTunnelResourceTable and is 297 also indexed by mplsTunnelResourceIndex. As with 298 mplsTunnelResourceTable, multiple tunnels may share the 299 same resources by pointing to the same entry in this table. 300 Tunnels that do not share resources must point to separate 301 entries in this table. 303 7. Use of 32-bit and 64-bit Counters 305 64-bit counters are provided in this MIB for high-speed 306 interfaces where the use of 32-bit counters might be 307 impractical. The requirements on the use of 32-bit and 64- 308 bit counters (copied verbatim from [RFC2863]) are as 309 follows. 311 For interfaces that operate at 20,000,000 (20 million) bits 312 per second or less, 32-bit byte and packet counters MUST be 313 supported. For interfaces that operate faster than 314 20,000,000 bits/second, and slower than 650,000,000 315 bits/second, 32-bit packet counters MUST be supported and 316 64-bit octet counters MUST be supported. For interfaces 317 that operate at 650,000,000 bits/second or faster, 64-bit 318 packet counters AND 64-bit octet counters MUST be 319 supported. 321 8. Application of the Interface Group to MPLS Tunnels 322 The Interfaces Group of MIB II defines generic managed 323 objects for managing interfaces. This memo contains the 324 media-specific extensions to the Interfaces Group for 325 managing MPLS Tunnels as logical interfaces. 327 This memo assumes the interpretation of the Interfaces 328 Group to be in accordance with [RFC2863] which states that 329 the interfaces table (ifTable) contains information on the 330 managed resource's interfaces and that each sub-layer below 331 the internetwork layer of a network interface is considered 332 an interface. Thus, the MPLS interface is represented as 333 an entry in the ifTable. The interrelation of entries in 334 the ifTable is defined by the Interfaces Stack Group 335 defined in [RFC2863]. 337 When using MPLS Tunnels as interfaces, the interface stack 338 table might appear as follows: 340 +------------------------------------------------+ 341 | MPLS tunnel interface ifType = mplsTunnel(150) | 342 +------------------------------------------------+ 343 | MPLS interface ifType = mpls(166) | 344 +------------------------------------------------+ 345 | Underlying layer | 346 +------------------------------------------------+ 348 In the above diagram, "Underlying Layer" refers to the 349 ifIndex of any interface type for which MPLS 350 internetworking has been defined. Examples include ATM, 351 Frame Relay, and Ethernet. 353 8.1. Support of the MPLS Tunnel Interface by ifTable 355 Some specific interpretations of ifTable for those MPLS 356 tunnels represented as interfaces follow: 358 Object Use for the MPLS tunnel. 360 ifIndex Each MPLS tunnel is represented by an 361 ifEntry. 363 ifDescr Description of the MPLS tunnel. 365 ifType The value that is allocated for MPLS 366 tunnel is 150. 368 ifSpeed The total bandwidth in bits per second 369 for use by the MPLS tunnel. 371 ifPhysAddress Unused. 373 ifAdminStatus See [RFC2863]. 375 ifOperStatus This value reflects the actual 376 operational status of MPLS tunnel. 377 Assumes the value down(2) if the MPLS 378 tunnel is down. 380 ifLastChange See [RFC2863]. 382 ifInOctets The number of octets received over the 383 MPLS tunnel. 385 ifOutOctets The number of octets transmitted over 386 the MPLS tunnel. 388 ifInErrors The number of labeled packets dropped 389 due to uncorrectable errors. 391 ifInUnknownProtos The number of received packets 392 discarded during packet header 393 validation, including packets with 394 unrecognized label values. 396 ifOutErrors See [RFC2863]. 398 ifName Textual name (unique on this system) of 399 the MPLS tunnel or an octet string of 400 zero length. 402 ifLinkUpDownTrapEnable 403 Default is disabled (2). 405 ifConnectorPresent Set to false (2). 407 ifHighSpeed See [RFC2863]. 409 ifHCInOctets The 64-bit version of ifInOctets; 410 supported if required by the compliance 411 statements in [RFC2863]. 413 ifHCOutOctets The 64-bit version of ifOutOctets; 414 supported if required by the compliance 415 statements in [RFC2863]. 417 ifAlias The non-volatile 'alias' name for the 418 MPLS tunnel as specified by a network 419 manager. 421 9. Example of Tunnel Setup 423 This section contains an example of which MIB objects 424 should be modified if one would like to create a best 425 effort, loosely routed, unidirectional traffic engineered 426 tunnel, which spans two hops of a simple network. Note 427 that these objects should be created on the "head-end" 428 LSR. Those objects relevant to illustrating the 429 relationships amongst different tables are shown here. 430 Other objects may be needed before conceptual row 431 activation can happen. 433 The RowStatus values shown in this section are those to be 434 used in the set request, typically createAndGo(4) which is 435 used to create the conceptual row and have its status 436 immediately set to active. A subsequent retrieval 437 operation on the conceptual row will return a different 438 value, such as active(1). Please see [RFC2579] for a 439 detailed discussion on the use of RowStatus. 441 In mplsTunnelTable: 442 { 443 mplsTunnelIndexIndex = 1, 444 mplsTunnelInstance = 1, 445 mplsTunnelIngressLSRId = 123.123.125.1, 446 mplsTunnelEgressLSRId = 123.123.126.1, 447 mplsTunnelName = "My first tunnel", 448 mplsTunnelDescr = "Here to there", 449 mplsTunnelIsIf = true (1), 450 -- RowPointer MUST point to the first accessible column 451 mplsTunnelXCPointer = mplsXCIndex.2.0.0.15, 452 mplsTunnelSignallingProto = none (1), 453 mplsTunnelSetupPrio = 0, 454 mplsTunnelHoldingPrio = 0, 455 mplsTunnelSessionAttributes = 0, 456 mplsTunnelOwner = snmp (1), 457 mplsTunnelLocalProtectInUse = false (0), 458 -- RowPointer MUST point to the first accessible column 459 mplsTunnelResourcePointer = mplsTunnelResourceIndex.5, 460 mplsTunnelInstancePriority = 1, 461 mplsTunnelHopTableIndex = 1, 462 mplsTunnelPrimaryInstance = 0, 463 mplsTunnelIncludeAnyAffinity = 0, 464 mplsTunnelIncludeAllAffinity = 0, 465 mplsTunnelExcludeAllAffinity = 0, 466 mplsTunnelPathInUse = 1, 467 mplsTunnelRole = head (1), 468 -- Mandatory parameters needed to activate the row go here 469 mplsTunnelRowStatus = createAndGo (4) 470 } 472 In mplsTunnelResourceTable: 473 { 474 mplsTunnelResourceIndex = 5, 475 mplsTunnelResourceMaxRate = 0, 476 mplsTunnelResourceMeanRate = 0, 477 mplsTunnelResourceMaxBurstSize = 0, 478 -- Mandatory parameters needed to activate the row go here 479 mplsTunnelResourceRowStatus = createAndGo (4) 480 } 482 The next two instances of mplsTunnelHopEntry are used to 483 denote the hops this tunnel will take across the network. 485 The following denotes the beginning of the network, or the 486 first hop. We have used the fictitious LSR identified by 487 "123.123.125.1" as our example head-end router. 489 In mplsTunnelHopTable: 490 { 491 mplsTunnelHopListIndex = 1, 492 mplsTunnelPathOptionIndex = 1, 493 mplsTunnelHopIndex = 1, 494 mplsTunnelHopAddrType = 1, 495 mplsTunnelHopIpAddrType = ipV4 (1) 496 mplsTunnelHopIpAddr = 123.123.125.1, 497 mplsTunnelHopIpPrefixLen = 9, 498 mplsTunnelHopType = loose (2), 499 -- Mandatory parameters needed to activate the row go here 500 mplsTunnelHopRowStatus = createAndGo (4) 501 } 503 The following denotes the end of the network, or the last 504 hop in our example. We have used the fictitious LSR 505 identified by "123.123.126.1" as our end router. 507 In mplsTunnelHopTable: 508 { 509 mplsTunnelHopListIndex = 1, 510 mplsTunnelPathOptionIndex = 1, 511 mplsTunnelHopIndex = 2, 512 mplsTunnelHopAddrType = 1, 513 mplsTunnelHopIpAddrType = ipV4 (1), 514 mplsTunnelHopIpAddr = 123.123.126.1, 515 mplsTunnelHopIpPrefixLen = 9, 516 mplsTunnelHopType = loose (2), 517 -- Mandatory parameters needed to activate the row go here 518 mplsTunnelHopRowStatus = createAndGo (4) 519 } 521 10. The Use of RowPointer 523 RowPointer is a textual convention used to identify a 524 conceptual row in an SNMP Table by pointing to one of its 525 objects. In this MIB, in mplsTunnelTable, the objects 526 mplsTunnelXCPointer and mplsTunnelResourcePointer are of 527 type RowPointer. The object mplsTunnelXCPointer points to 528 a specific entry in the mplsXCTable [LSRMIB]. This entry 529 in the mplsXCTable is the associated LSP for the given MPLS 530 tunnel entry. The object mplsTunnelResourcePointer points 531 to a specific entry in a traffic parameter table. An 532 example of such a traffic parameter table is 533 mplsTunnelResourceTable. It indicates a specific instance 534 of a traffic parameter entry that is associated with a 535 given MPLS tunnel entry. Row pointers mplsTunnelXCPointer 536 and mplsTunnelResourcePointer MUST point to the first 537 column of the appropriate conceptual row. 539 11. MPLS Traffic Engineering MIB Definitions 541 MPLS-TE-MIB DEFINITIONS ::= BEGIN 543 IMPORTS 544 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 545 Integer32, Unsigned32, Counter32, Counter64, TimeTicks, 546 zeroDotZero 547 FROM SNMPv2-SMI 548 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 549 FROM SNMPv2-CONF 550 TruthValue, RowStatus, RowPointer, StorageType, 551 DisplayString, TimeStamp 552 FROM SNMPv2-TC 553 InterfaceIndexOrZero 554 FROM IF-MIB 555 mplsMIB, MplsBitRate, MplsBurstSize, MplsLSPID, 556 MplsTunnelIndex, MplsTunnelInstanceIndex, 557 MplsTunnelAffinity, MplsLsrIdentifier, MplsPathIndex, 558 MplsPathIndexOrZero, MplsOwner 559 FROM MPLS-TC-MIB 560 InetAddress, InetAddressType, InetAddressPrefixLength 561 FROM INET-ADDRESS-MIB 562 ; 564 mplsTeMIB MODULE-IDENTITY 565 LAST-UPDATED 566 "200211041200Z" -- 4 November 2002 12:00:00 GMT 567 ORGANIZATION 568 "Multiprotocol Label Switching (MPLS) Working Group" 569 CONTACT-INFO 570 " 571 Cheenu Srinivasan 572 Postal: Parama Networks, Inc. 573 1030 Broad Street 574 Shrewsbury, NJ 07702 575 Tel: +1-732-544-9120 x731 576 Email: cheenu@paramanet.com 578 Arun Viswanathan 579 Postal: Force10 Networks, Inc. 580 1440 McCarthy Blvd 581 Milpitas, CA 95035 582 Tel: +1-408-571-3516 583 Email: arun@force10networks.com 585 Thomas D. Nadeau 586 Postal: Cisco Systems, Inc. 587 250 Apollo Drive 588 Chelmsford, MA 01824 589 Tel: +1-978-244-3051 590 Email: tnadeau@cisco.com 592 Comments about this document should be 593 emailed 594 directly to the MPLS working group mailing 595 list at 596 mpls@uu.net. 597 " 598 DESCRIPTION 599 "This MIB module contains managed object definitions 600 for MPLS Traffic Engineering (TE) as defined in: 601 1. Extensions to RSVP for LSP Tunnels, Awduche et 602 al, RFC 3209, December 2001 603 2. Constraint-Based LSP Setup using LDP, Jamoussi 604 (Editor), RFC 3212, January 2002 605 3. Requirements for Traffic Engineering Over MPLS, 606 Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., 607 and J. McManus, RFC 2702, September 1999" 609 -- Revision history. 611 REVISION 612 "200211041200Z" -- 4 November 2002 12:00:00 GMT 613 DESCRIPTION 614 "Initial draft version issues as part of RFC XXXX." 616 ::= { mplsMIB 3 } 618 -- Top level components of this MIB. 620 -- traps 621 mplsTeNotifications OBJECT IDENTIFIER ::= { mplsTeMIB 0 } 622 -- tables, scalars 623 mplsTeScalars OBJECT IDENTIFIER ::= { mplsTeMIB 1 } 624 mplsTeObjects OBJECT IDENTIFIER ::= { mplsTeMIB 2 } 625 -- conformance 626 mplsTeConformance OBJECT IDENTIFIER ::= { mplsTeMIB 3 } 628 -- MPLS Tunnel scalars. 630 mplsTunnelConfigured OBJECT-TYPE 631 SYNTAX Unsigned32 632 MAX-ACCESS read-only 633 STATUS current 634 DESCRIPTION 635 "The number of tunnels configured on this device. A 636 tunnel is considered configured if the 637 mplsTunnelRowStatus is active(1)." 638 ::= { mplsTeScalars 1 } 640 mplsTunnelActive OBJECT-TYPE 641 SYNTAX Unsigned32 642 MAX-ACCESS read-only 643 STATUS current 644 DESCRIPTION 645 "The number of tunnels active on this device. A 646 tunnel is considered active if the 647 mplsTunnelOperStatus is up(1)." 648 ::= { mplsTeScalars 2 } 650 mplsTunnelTEDistProto OBJECT-TYPE 651 SYNTAX BITS { 652 other (0), 653 ospf (1), 654 isis (2) 655 } 656 MAX-ACCESS read-only 657 STATUS current 658 DESCRIPTION 659 "The traffic engineering distribution protocol(s) 660 used by this LSR. Note that an LSR may support more 661 than one distribution protocol simultaneously." 662 ::= { mplsTeScalars 3 } 664 mplsTunnelMaxHops OBJECT-TYPE 665 SYNTAX Unsigned32 666 MAX-ACCESS read-only 667 STATUS current 668 DESCRIPTION 669 "The maximum number of hops that can be specified for 670 a tunnel on this device." 671 ::= { mplsTeScalars 4 } 673 mplsTunnelNotifMaxRate OBJECT-TYPE 674 SYNTAX Unsigned32 675 MAX-ACCESS read-write 676 STATUS current 677 DESCRIPTION 678 "This variable indicates the number of milliseconds 679 that must elapse between notification emissions. If 680 events occur more rapidly, the implementation may 681 simply fail to emit these notifications during that 682 period, or may queue them until an appropriate 683 time. A value of 0 means no minimum elapsed period 684 is specified." 685 DEFVAL { 0 } 686 ::= { mplsTeScalars 5 } 688 -- End of MPLS Tunnel scalars. 690 -- MPLS tunnel table. 692 mplsTunnelIndexNext OBJECT-TYPE 693 SYNTAX Integer32 (0..65535) 694 MAX-ACCESS read-only 695 STATUS current 696 DESCRIPTION 697 "This object contains the next appropriate value to 698 be used for mplsTunnelIndexIndex when creating 699 entries in mplsTunnelTable. If the number of 700 unassigned entries is exhausted, a retrival 701 operation will return a value of 0. This object 702 may also return a value of 0 when the LSR is unable 703 to accept conceptual row creation, for example, if 704 the mplsTunnelTable is implemented as read-only. To 705 obtain the value of mplsTunnelIndexIndex for a new 706 entry, the manager must first issue a management 707 protocol retrieval operation to obtain the current 708 value of this object. The agent should modify the 709 value to reflect the next unassigned index after 710 each retrieval operation. After a manager retrieves 711 a value the agent will determine through its local 712 policy when this index value will be made available 713 for reuse." 714 ::= { mplsTeObjects 1 } 716 mplsTunnelTable OBJECT-TYPE 717 SYNTAX SEQUENCE OF MplsTunnelEntry 718 MAX-ACCESS not-accessible 719 STATUS current 720 DESCRIPTION 721 "The mplsTunnelTable allows new MPLS tunnels to be 722 created between an LSR and a remote endpoint, and 723 existing tunnels to be reconfigured or removed. 724 Note that only point-to-point tunnel segments are 725 supported, although multi-point-to-point and point- 726 to-multi-point connections are supported by an LSR 727 acting as a cross-connect. Each MPLS tunnel can 728 thus have one out-segment originating at this LSR 729 and/or one in-segment terminating at this LSR." 730 ::= { mplsTeObjects 2 } 732 mplsTunnelEntry OBJECT-TYPE 733 SYNTAX MplsTunnelEntry 734 MAX-ACCESS not-accessible 735 STATUS current 736 DESCRIPTION 737 "An entry in this table represents an MPLS tunnel. 738 An entry can be created by a network administrator 739 or by an SNMP agent as instructed by an MPLS 740 signalling protocol. Whenever a new entry is 741 created with mplsTunnelIsIf set to true(1), then a 742 corresponding entry is created in ifTable as well 743 (see RFC 2863). The ifType of this entry is 744 mplsTunnel(150)." 746 REFERENCE 747 "1. RFC 2863 - The Interfaces Group MIB, McCloghrie, 748 K., and F. Kastenholtz, June 2000 749 2. RFC 1700 - Assigned Numbers, Reynolds, J. and J. 750 Postel, Oct. 1994" 751 INDEX { 752 mplsTunnelIndexIndex, 753 mplsTunnelInstance, 754 mplsTunnelIngressLSRId, 755 mplsTunnelEgressLSRId 756 } 757 ::= { mplsTunnelTable 1 } 759 MplsTunnelEntry ::= SEQUENCE { 760 mplsTunnelIndexIndex MplsTunnelIndex, 761 mplsTunnelInstance MplsTunnelInstanceIndex, 762 mplsTunnelIngressLSRId MplsLsrIdentifier, 763 mplsTunnelEgressLSRId MplsLsrIdentifier, 764 mplsTunnelName DisplayString, 765 mplsTunnelDescr DisplayString, 766 mplsTunnelIsIf TruthValue, 767 mplsTunnelIfIndex InterfaceIndexOrZero, 768 mplsTunnelXCPointer RowPointer, 769 mplsTunnelSignallingProto INTEGER, 770 mplsTunnelSetupPrio Integer32, 771 mplsTunnelHoldingPrio Integer32, 772 mplsTunnelSessionAttributes BITS, 773 mplsTunnelOwner MplsOwner, 774 mplsTunnelLocalProtectInUse TruthValue, 775 mplsTunnelResourcePointer RowPointer, 776 mplsTunnelInstancePriority Unsigned32, 777 mplsTunnelHopTableIndex MplsPathIndexOrZero, 778 mplsTunnelARHopTableIndex MplsPathIndexOrZero, 779 mplsTunnelCHopTableIndex MplsPathIndexOrZero, 780 mplsTunnelPrimaryInstance MplsTunnelInstanceIndex, 781 mplsTunnelPrimaryTimeUp TimeTicks, 782 mplsTunnelPathChanges Counter32, 783 mplsTunnelLastPathChange TimeTicks, 784 mplsTunnelCreationTime TimeStamp, 785 mplsTunnelStateTransitions Counter32, 786 mplsTunnelIncludeAnyAffinity MplsTunnelAffinity, 787 mplsTunnelIncludeAllAffinity MplsTunnelAffinity, 788 mplsTunnelExcludeAllAffinity MplsTunnelAffinity, 789 mplsTunnelPathInUse MplsPathIndexOrZero, 790 mplsTunnelRole INTEGER, 791 mplsTunnelTotalUpTime TimeTicks, 792 mplsTunnelInstanceUpTime TimeTicks, 793 mplsTunnelAdminStatus INTEGER, 794 mplsTunnelOperStatus INTEGER, 795 mplsTunnelRowStatus RowStatus, 796 mplsTunnelStorageType StorageType 797 } 799 mplsTunnelIndexIndex OBJECT-TYPE 800 SYNTAX MplsTunnelIndex 801 MAX-ACCESS not-accessible 802 STATUS current 803 DESCRIPTION 804 "Uniquely identifies this row." 805 ::= { mplsTunnelEntry 1 } 807 mplsTunnelInstance OBJECT-TYPE 808 SYNTAX MplsTunnelInstanceIndex 809 MAX-ACCESS not-accessible 810 STATUS current 811 DESCRIPTION 812 "Uniquely identifies an instance of a tunnel. It is 813 useful to identify multiple instances of tunnels 814 for the purposes of backup and parallel tunnels." 815 ::= { mplsTunnelEntry 2 } 817 mplsTunnelIngressLSRId OBJECT-TYPE 818 SYNTAX MplsLsrIdentifier 819 MAX-ACCESS not-accessible 820 STATUS current 821 DESCRIPTION 822 "The purpose of this object is to uniquely identity a 823 tunnel within a network. When the MPLS signalling 824 protocol is rsvp(2) this value SHOULD mimic the 825 Extended Tunnel Id field in the SESSION object. 826 When the MPLS signalling protocol is crldp(3) this 827 value SHOULD mimic the Ingress LSR Router ID field 828 in the LSPID TLV object." 829 REFERENCE 830 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 831 Awduche et al, RFC 3209, December 2001 832 2. Constraint-Based LSP Setup using LDP, Jamoussi 833 (Editor), RFC 3212, January 2002" 834 ::= { mplsTunnelEntry 3 } 836 mplsTunnelEgressLSRId OBJECT-TYPE 837 SYNTAX MplsLsrIdentifier 838 MAX-ACCESS not-accessible 839 STATUS current 840 DESCRIPTION 841 "Specifies the egress LSR ID." 843 ::= { mplsTunnelEntry 4 } 845 mplsTunnelName OBJECT-TYPE 846 SYNTAX DisplayString 847 MAX-ACCESS read-create 848 STATUS current 849 DESCRIPTION 850 "The canonical name assigned to the tunnel. This name 851 can be used to refer to the tunnel on the LSR's 852 console port. If mplsTunnelIsIf is set to true 853 then the ifName of the interface corresponding to 854 this tunnel should have a value equal to 855 mplsTunnelName. Also see the description of ifName 856 in RFC 2863." 857 REFERENCE 858 "RFC 2863 - The Interfaces Group MIB, McCloghrie, K., 859 and F. Kastenholtz, June 2000" 860 ::= { mplsTunnelEntry 5 } 862 mplsTunnelDescr OBJECT-TYPE 863 SYNTAX DisplayString 864 MAX-ACCESS read-create 865 STATUS current 866 DESCRIPTION 867 "A textual string containing information about the 868 tunnel. If there is no description this object 869 contains a zero length string." 870 ::= { mplsTunnelEntry 6 } 872 mplsTunnelIsIf OBJECT-TYPE 873 SYNTAX TruthValue 874 MAX-ACCESS read-create 875 STATUS current 876 DESCRIPTION 877 "Denotes whether or not this tunnel corresponds to an 878 interface represented in the interfaces group 879 table. Note that if this variable is set to true 880 then the ifName of the interface corresponding to 881 this tunnel should have a value equal to 882 mplsTunnelName. Also see the description of ifName 883 in RFC 2863." 884 REFERENCE 885 "RFC 2863 - The Interfaces Group MIB, McCloghrie, K., 886 and F. Kastenholtz, June 2000" 887 DEFVAL { false } 888 ::= { mplsTunnelEntry 7 } 890 mplsTunnelIfIndex OBJECT-TYPE 891 SYNTAX InterfaceIndexOrZero 892 MAX-ACCESS read-only 893 STATUS current 894 DESCRIPTION 895 "If mplsTunnelIsIf is set to true, then this value 896 contains the LSR-assigned ifIndex which corresponds 897 to an entry in the interfaces table. Otherwise 898 this variable should contain the value of zero 899 indicating that a valid ifIndex was not assigned to 900 this tunnel interface." 901 REFERENCE 902 "RFC 2863 - The Interfaces Group MIB, McCloghrie, K., 903 and F. Kastenholtz, June 2000" 904 ::= { mplsTunnelEntry 8 } 906 mplsTunnelXCPointer OBJECT-TYPE 907 SYNTAX RowPointer 908 MAX-ACCESS read-create 909 STATUS current 910 DESCRIPTION 911 "This variable points to a row in the mplsXCTable. 912 This table identifies the segments that compose 913 this tunnel, their characteristics, and 914 relationships to each other. A value of zeroDotZero 915 indicates that no LSP has been associated with this 916 tunnel yet." 917 REFERENCE 918 "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS 919 Label Switching Router Management Information Base, 920 Internet Draft , 921 October 2002." 922 DEFVAL { zeroDotZero } 923 ::= { mplsTunnelEntry 9 } 925 mplsTunnelSignallingProto OBJECT-TYPE 926 SYNTAX INTEGER { 927 none(1), 928 rsvp(2), 929 crldp(3), 930 other(4) 931 } 932 MAX-ACCESS read-create 933 STATUS current 934 DESCRIPTION 935 "The signalling protocol, if any, which was used to 936 setup this tunnel." 937 DEFVAL { none } 938 ::= { mplsTunnelEntry 10 } 940 mplsTunnelSetupPrio OBJECT-TYPE 941 SYNTAX Integer32 (0..7) 942 MAX-ACCESS read-create 943 STATUS current 944 DESCRIPTION 945 "Indicates the setup priority of this tunnel." 946 REFERENCE 947 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 948 Awduche et al, RFC 3209, December 2001 949 2. Constraint-Based LSP Setup using LDP, Jamoussi 950 (Editor), Internet Draft , November 2001" 952 ::= { mplsTunnelEntry 11 } 954 mplsTunnelHoldingPrio OBJECT-TYPE 955 SYNTAX Integer32 (0..7) 956 MAX-ACCESS read-create 957 STATUS current 958 DESCRIPTION 959 "Indicates the holding priority for this tunnel." 960 REFERENCE 961 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 962 Awduche et al, RFC3209, December 2001 963 2. Constraint-Based LSP Setup using LDP, Jamoussi 964 (Editor), RFC 3212, January 2002" 965 ::= { mplsTunnelEntry 12 } 967 mplsTunnelSessionAttributes OBJECT-TYPE 968 SYNTAX BITS { 969 fastReroute (0), 970 mergingPermitted (1), 971 isPersistent (2), 972 isPinned (3), 973 recordRoute(4) 974 } 975 MAX-ACCESS read-create 976 STATUS current 977 DESCRIPTION 978 "This bit mask indicates optional session values for 979 this tunnel. The following describes these bit 980 fields: 982 fastRerouteThis flag indicates that the any tunnel 983 hop may choose to reroute this tunnel without 984 tearing it down. This flag permits transit routers 985 to use a local repair mechanism which may result in 986 violation of the explicit routing of this tunnel. 988 When a fault is detected on an adjacent downstream 989 link or node, a transit router can re-route traffic 990 for fast service restoration. 992 mergingPermitted This flag permits transit routers 993 to merge this session with other RSVP sessions for 994 the purpose of reducing resource overhead on 995 downstream transit routers, thereby providing 996 better network scaling. 998 isPersistent Indicates whether this tunnel should 999 be restored automatically after a failure occurs. 1001 isPinned This flag indicates whether the loose- 1002 routed hops of this tunnel are to be pinned. 1004 recordRouteThis flag indicates whether or not the 1005 signalling protocol should remember the tunnel path 1006 after it has been signaled." 1008 REFERENCE 1009 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 1010 Awduche et al, RFC 3209, December 2001." 1011 ::= { mplsTunnelEntry 13 } 1013 mplsTunnelOwner OBJECT-TYPE 1014 SYNTAX MplsOwner 1015 MAX-ACCESS read-only 1016 STATUS current 1017 DESCRIPTION 1018 "Denotes the entity that created and is responsible 1019 for managing this tunnel. This object cannot be 1020 modified if mplsTunnelRowStatus is active(1). " 1021 ::= { mplsTunnelEntry 14 } 1023 mplsTunnelLocalProtectInUse OBJECT-TYPE 1024 SYNTAX TruthValue 1025 MAX-ACCESS read-create 1026 STATUS current 1027 DESCRIPTION 1028 "Indicates that the local repair mechanism is in use 1029 to maintain this tunnel (usually in the face of an 1030 outage of the link it was previously routed over)." 1031 ::= { mplsTunnelEntry 15 } 1033 mplsTunnelResourcePointer OBJECT-TYPE 1034 SYNTAX RowPointer 1035 MAX-ACCESS read-create 1036 STATUS current 1037 DESCRIPTION 1038 "This variable represents a pointer to the traffic 1039 parameter specification for this tunnel. This 1040 value may point at an entry in the 1041 mplsTunnelResourceEntry to indicate which 1042 mplsTunnelResourceEntry is to be assigned to this 1043 segment. This value may optionally point at an 1044 externally defined traffic parameter specification 1045 table. A value of zeroDotZero indicates best- 1046 effort treatment. By having the same value of this 1047 object, two or more segments can indicate resource 1048 sharing." 1049 DEFVAL { zeroDotZero } 1050 ::= { mplsTunnelEntry 16 } 1052 mplsTunnelInstancePriority OBJECT-TYPE 1053 SYNTAX Unsigned32 1054 MAX-ACCESS read-create 1055 STATUS current 1056 DESCRIPTION 1057 "This value indicates which priority, in descending 1058 order, with 0 indicating the lowest priority, 1059 within a group of tunnel instances. A group of 1060 tunnel instances is defined as a set of tunnels 1061 with the same mplsTunnelIndexIndex in this table, 1062 but with a different mplsTunnelInstance. Tunnel 1063 group priorities are used to denote the priority at 1064 which a particular tunnel instance will supercede 1065 another. Instances of tunnels containing the same 1066 mplsTunnelInstancePriority will be used for load 1067 sharing." 1068 DEFVAL { 0 } 1069 ::= { mplsTunnelEntry 17 } 1071 mplsTunnelHopTableIndex OBJECT-TYPE 1072 SYNTAX MplsPathIndexOrZero 1073 MAX-ACCESS read-create 1074 STATUS current 1075 DESCRIPTION 1076 "Index into the mplsTunnelHopTable entry that 1077 specifies the explicit route hops for this tunnel." 1078 ::= { mplsTunnelEntry 18 } 1080 mplsTunnelARHopTableIndex OBJECT-TYPE 1081 SYNTAX MplsPathIndexOrZero 1082 MAX-ACCESS read-only 1083 STATUS current 1084 DESCRIPTION 1085 "Index into the mplsTunnelARHopTable entry that 1086 specifies the actual hops traversed by the tunnel." 1087 ::= { mplsTunnelEntry 19 } 1089 mplsTunnelCHopTableIndex OBJECT-TYPE 1090 SYNTAX MplsPathIndexOrZero 1091 MAX-ACCESS read-only 1092 STATUS current 1093 DESCRIPTION 1094 "Index into the mplsTunnelCHopTable entry that 1095 specifies the computed hops traversed by the 1096 tunnel." 1097 ::= { mplsTunnelEntry 20 } 1099 mplsTunnelPrimaryInstance OBJECT-TYPE 1100 SYNTAX MplsTunnelInstanceIndex 1101 MAX-ACCESS read-only 1102 STATUS current 1103 DESCRIPTION 1104 "Specifies the instance index of the primary instance 1105 of this tunnel." 1106 ::= { mplsTunnelEntry 21 } 1108 mplsTunnelPrimaryTimeUp OBJECT-TYPE 1109 SYNTAX TimeTicks 1110 MAX-ACCESS read-only 1111 STATUS current 1112 DESCRIPTION 1113 "Specifies the total time the primary instance of 1114 this tunnel has been active. The primary instance 1115 of this tunnel is defined in 1116 mplsTunnelPrimaryInstance." 1117 ::= { mplsTunnelEntry 22 } 1119 mplsTunnelPathChanges OBJECT-TYPE 1120 SYNTAX Counter32 1121 MAX-ACCESS read-only 1122 STATUS current 1123 DESCRIPTION 1124 "Specifies the number of times the paths has changed 1125 for this tunnel." 1126 ::= { mplsTunnelEntry 23 } 1128 mplsTunnelLastPathChange OBJECT-TYPE 1129 SYNTAX TimeTicks 1130 MAX-ACCESS read-only 1131 STATUS current 1132 DESCRIPTION 1133 "Specifies the time since the last path change for 1134 this tunnel." 1135 ::= { mplsTunnelEntry 24 } 1137 mplsTunnelCreationTime OBJECT-TYPE 1138 SYNTAX TimeStamp 1139 MAX-ACCESS read-only 1140 STATUS current 1141 DESCRIPTION 1142 "Specifies the value of SysUpTime when the first 1143 instance of this tunnel came into existence." 1144 ::= { mplsTunnelEntry 25 } 1146 mplsTunnelStateTransitions OBJECT-TYPE 1147 SYNTAX Counter32 1148 MAX-ACCESS read-only 1149 STATUS current 1150 DESCRIPTION 1151 "Specifies the number of times the state of this 1152 tunnel instance has changed." 1153 ::= { mplsTunnelEntry 26 } 1155 mplsTunnelIncludeAnyAffinity OBJECT-TYPE 1156 SYNTAX MplsTunnelAffinity 1157 MAX-ACCESS read-create 1158 STATUS current 1159 DESCRIPTION 1160 "A link satisfies the include-any constraint if and 1161 only if the constraint is zero, or the link and the 1162 constraint have a resource class in common." 1163 REFERENCE 1164 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 1165 Awduche et al, RFC 3209, December 2001." 1166 ::= { mplsTunnelEntry 27 } 1168 mplsTunnelIncludeAllAffinity OBJECT-TYPE 1169 SYNTAX MplsTunnelAffinity 1170 MAX-ACCESS read-create 1171 STATUS current 1172 DESCRIPTION 1173 "A link satisfies the include-all constraint if and 1174 only if the link contains all of the administrative 1175 groups specified in the constraint." 1176 REFERENCE 1177 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 1178 Awduche et al, RFC 3209, December 2001." 1179 ::= { mplsTunnelEntry 28 } 1181 mplsTunnelExcludeAllAffinity OBJECT-TYPE 1182 SYNTAX MplsTunnelAffinity 1183 MAX-ACCESS read-create 1184 STATUS current 1185 DESCRIPTION 1186 "A link satisfies the exclude-all constraint if and 1187 only if the link contains none of the 1188 administrative groups specified in the constraint." 1189 REFERENCE 1190 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 1191 Awduche et al, RFC 3209, December 2001." 1192 ::= { mplsTunnelEntry 29 } 1194 mplsTunnelPathInUse OBJECT-TYPE 1195 SYNTAX MplsPathIndexOrZero 1196 MAX-ACCESS read-create 1197 STATUS current 1198 DESCRIPTION 1199 "This value denotes the configured path that was 1200 chosen for this tunnel. This value reflects the 1201 secondary index into mplsTunnelHopTable. This path 1202 may not exactly match the one in 1203 mplsTunnelARHopTable due to the fact that some CSPF 1204 modification may have taken place. See 1205 mplsTunnelARHopTable for the actual path being 1206 taken by the tunnel. A value of zero denotes that 1207 no path is currently in use or available." 1208 ::= { mplsTunnelEntry 30 } 1210 mplsTunnelRole OBJECT-TYPE 1211 SYNTAX INTEGER { head(1), transit(2), tail(3) } 1212 MAX-ACCESS read-create 1213 STATUS current 1214 DESCRIPTION 1215 "This value signifies the role that this tunnel 1216 entry/instance represents. This value MUST be set 1217 to head(1) at the originating point of the tunnel. 1218 This value MUST be set to transit(2) at transit 1219 points along the tunnel, if transit points are 1220 supported. This value MUST be set to tail(3) at the 1221 terminating point of the tunnel if tunnel tails are 1222 supported." 1223 ::= { mplsTunnelEntry 31 } 1225 mplsTunnelTotalUpTime OBJECT-TYPE 1226 SYNTAX TimeTicks 1227 MAX-ACCESS read-create 1228 STATUS current 1229 DESCRIPTION 1230 "This value represents the aggregate up time for all 1231 instances of this tunnel, if available. If this 1232 value is unavailable, it MUST return a value of 0." 1233 ::= { mplsTunnelEntry 32 } 1235 mplsTunnelInstanceUpTime OBJECT-TYPE 1236 SYNTAX TimeTicks 1237 MAX-ACCESS read-create 1238 STATUS current 1239 DESCRIPTION 1240 "This value identifies the total time that this 1241 tunnel instance's operStatus has been Up(1)." 1242 ::= { mplsTunnelEntry 33 } 1244 mplsTunnelAdminStatus OBJECT-TYPE 1245 SYNTAX INTEGER { 1246 -- ready to pass packets 1247 up(1), 1248 down(2), 1249 -- in some test mode 1250 testing(3) 1251 } 1252 MAX-ACCESS read-create 1253 STATUS current 1254 DESCRIPTION 1255 "Indicates the desired operational status of this 1256 tunnel." 1257 ::= { mplsTunnelEntry 34 } 1259 mplsTunnelOperStatus OBJECT-TYPE 1260 SYNTAX INTEGER { 1261 -- ready to pass packets 1262 up(1), 1263 down(2), 1264 -- in some test mode 1265 testing(3), 1266 -- status cannot be determined 1267 unknown(4), 1268 dormant(5), 1269 -- some component is missing 1270 notPresent(6), 1271 -- down due to the state of 1272 -- lower layer interfaces 1273 lowerLayerDown(7) 1274 } 1275 MAX-ACCESS read-only 1276 STATUS current 1277 DESCRIPTION 1278 "Indicates the actual operational status of this 1279 tunnel, which is typically but not limited to, a 1280 function of the state of individual segments of 1281 this tunnel." 1282 ::= { mplsTunnelEntry 35 } 1284 mplsTunnelRowStatus OBJECT-TYPE 1285 SYNTAX RowStatus 1286 MAX-ACCESS read-create 1287 STATUS current 1288 DESCRIPTION 1289 "This variable is used to create, modify, and/or 1290 delete a row in this table." 1291 ::= { mplsTunnelEntry 36 } 1293 mplsTunnelStorageType OBJECT-TYPE 1294 SYNTAX StorageType 1295 MAX-ACCESS read-create 1296 STATUS current 1297 DESCRIPTION 1298 "This variable indicates the storage type for this 1299 object. This object cannot be modified if 1300 mplsTunnelRowStatus is active(1). If this variable 1301 is set to readOnly(5), and the corresponding entry 1302 is removed, then the agent must remove this row 1303 shortly thereafter [RFC2579]." 1304 ::= { mplsTunnelEntry 37 } 1306 -- End of mplsTunnelTable 1308 mplsTunnelHopListIndexNext OBJECT-TYPE 1309 SYNTAX Unsigned32 (0..2147483647) 1310 MAX-ACCESS read-only 1311 STATUS current 1312 DESCRIPTION 1313 "This object contains an appropriate value to be used 1314 for mplsTunnelHopListIndex when creating entries in 1315 the mplsTunnelHopTable. If the number of 1316 unassigned entries is exhausted, a retrival 1317 operation will return a value of 0. This object 1318 may also return a value of 0 when the LSR is unable 1319 to accept conceptual row creation, for example, if 1320 the mplsTunnelHopTable is implemented as read-only. 1321 To obtain the value of mplsTunnelHopListIndex for a 1322 new entry in the mplsTunnelHopTable, the manager 1323 issues a management protocol retrieval operation to 1324 obtain the current value of mplsTunnelHopIndex. 1325 After each retrieval operation, the agent should 1326 modify the value to reflect the next unassigned 1327 index. After a manager retrieves a value the agent 1328 will determine through its local policy when this 1329 index value will be made available for reuse." 1330 ::= { mplsTeObjects 3 } 1332 mplsTunnelHopTable OBJECT-TYPE 1333 SYNTAX SEQUENCE OF MplsTunnelHopEntry 1334 MAX-ACCESS not-accessible 1335 STATUS current 1336 DESCRIPTION 1337 "The mplsTunnelHopTable is used to indicate the hops, 1338 strict or loose, for an MPLS tunnel defined in 1339 mplsTunnelTable, when it is established via 1340 signalling, for the outgoing direction of the 1341 tunnel. Each row in this table is indexed by 1342 mplsTunnelHopListIndex. Each row also has a 1343 secondary index mplsTunnelHopIndex corresponding to 1344 the next hop that this row corresponds to. The 1345 first row in the table is the first hop after the 1346 origination point of the tunnel. In case we want 1347 to specify a particular interface on the 1348 originating LSR of an outgoing tunnel by which we 1349 want packets to exit the LSR, we specify this as 1350 the first hop for this tunnel in 1351 mplsTunnelHopTable." 1352 ::= { mplsTeObjects 4 } 1354 mplsTunnelHopEntry OBJECT-TYPE 1355 SYNTAX MplsTunnelHopEntry 1356 MAX-ACCESS not-accessible 1357 STATUS current 1358 DESCRIPTION 1359 "An entry in this table represents a tunnel hop. An 1360 entry is created by a network administrator for 1361 signaled ERLSP set up by an MPLS signalling 1362 protocol." 1363 INDEX { 1364 mplsTunnelHopListIndex, 1365 mplsTunnelHopPathOptionIndex, 1366 mplsTunnelHopIndex 1367 } 1368 ::= { mplsTunnelHopTable 1 } 1370 MplsTunnelHopEntry ::= SEQUENCE { 1371 mplsTunnelHopListIndex MplsPathIndex, 1372 mplsTunnelHopPathOptionIndex MplsPathIndex, 1373 mplsTunnelHopIndex MplsPathIndex, 1374 mplsTunnelHopAddrType INTEGER, 1375 mplsTunnelHopIpAddrType InetAddressType, 1376 mplsTunnelHopIpAddr InetAddress, 1377 mplsTunnelHopIpPrefixLen InetAddressPrefixLength, 1378 mplsTunnelHopAsNumber Unsigned32, 1379 mplsTunnelHopLspId MplsLSPID, 1380 mplsTunnelHopType INTEGER, 1381 mplsTunnelHopIncludeExclude INTEGER, 1382 mplsTunnelHopPathOptionName DisplayString, 1383 mplsTunnelHopEntryPathComp INTEGER, 1384 mplsTunnelHopRowStatus RowStatus, 1385 mplsTunnelHopStorageType StorageType 1386 } 1388 mplsTunnelHopListIndex OBJECT-TYPE 1389 SYNTAX MplsPathIndex 1390 MAX-ACCESS not-accessible 1391 STATUS current 1392 DESCRIPTION 1393 "Primary index into this table identifying a 1394 particular explicit route object." 1395 ::= { mplsTunnelHopEntry 1 } 1397 mplsTunnelHopPathOptionIndex OBJECT-TYPE 1398 SYNTAX MplsPathIndex 1399 MAX-ACCESS not-accessible 1400 STATUS current 1401 DESCRIPTION 1402 "Secondary index into this table identifying a 1403 particular group of hops representing a particular 1404 configured path. This is otherwise known as a path 1405 option." 1406 ::= { mplsTunnelHopEntry 2 } 1408 mplsTunnelHopIndex OBJECT-TYPE 1409 SYNTAX MplsPathIndex 1410 MAX-ACCESS not-accessible 1411 STATUS current 1412 DESCRIPTION 1413 "Secondary index into this table identifying a 1414 particular hop." 1415 ::= { mplsTunnelHopEntry 3 } 1417 mplsTunnelHopAddrType OBJECT-TYPE 1418 SYNTAX INTEGER { 1419 ipAddr(1), 1420 asNumber(2), 1421 lspId(3) 1422 } 1423 MAX-ACCESS read-create 1424 STATUS current 1425 DESCRIPTION 1426 "Denotes the address type of this tunnel hop. If set 1427 to ipAddr(1), this value denotes an IP address type 1428 and also indicates that the 1429 mplsTunnelHopIpAddrType, mplsTunnelHopIpAddr, and 1430 mplsTunnelHopIpPrefixLen should be used to refer to 1431 the IP address of this hop. The values contained in 1432 mplsTunnelHopAsNumber, and mplsTunnelHopLspId 1433 should be ignored. If this object is set to 1434 asNumber(2), the IP address related objects should 1435 be ignored, and the mplsTunnelHopAsNumber should be 1436 refered to. If the object is set to lspId(3), then 1437 all but the mplsTunnelHopLspId should be referred 1438 to. Note that lspId(3) is a valid option only for 1439 tunnels signaled via CRLDP." 1440 DEFVAL { ipAddr } 1441 ::= { mplsTunnelHopEntry 4 } 1443 mplsTunnelHopIpAddrType OBJECT-TYPE 1444 SYNTAX InetAddressType 1445 MAX-ACCESS read-create 1446 STATUS current 1447 DESCRIPTION 1448 "If mplsTunnelHopAddrType is set to ipAddr(1) then 1449 this value will contain the IP address type of this 1450 hop. If mplsTunnelHopAddrType is set to lspId(3) 1451 then this value will contain the IP address type of 1452 the Ingress LSR Router ID contained in object 1453 mplsTunnelHopIpAddr. Otherwise a management entity 1454 SHOULD ignore this object." 1455 ::= { mplsTunnelHopEntry 5 } 1457 mplsTunnelHopIpAddr OBJECT-TYPE 1458 SYNTAX InetAddress 1459 MAX-ACCESS read-create 1460 STATUS current 1461 DESCRIPTION 1462 "If mplsTunnelHopIpAddrType is set to ipV4(1) or 1463 ipV6(2), then this value will contain respectively 1464 the IPv4 address or the IPv6 address of this hop. 1465 If mplsTunnelHopAddrType is set to lspId(3), then 1466 this value will contain the Ingress LSR Router ID 1467 of the Tunnel. Otherwise a management entity SHOULD 1468 set this to 0 and an agent MUST ignore it. Likewise 1469 an agent MUST return a value of 0 for a retrieval 1470 operation." 1471 ::= { mplsTunnelHopEntry 6 } 1473 mplsTunnelHopIpPrefixLen OBJECT-TYPE 1474 SYNTAX InetAddressPrefixLength 1475 MAX-ACCESS read-create 1476 STATUS current 1477 DESCRIPTION 1478 "If mplsTunnelHopIpAddrType is set to ipV4(1) or 1479 ipV6(2), then this value will contain an 1480 appropriate prefix length for this hop. Otherwise a 1481 management entity SHOULD set this object to 0 and 1482 an agent MUST ignore it." 1483 ::= { mplsTunnelHopEntry 7 } 1485 mplsTunnelHopAsNumber OBJECT-TYPE 1486 SYNTAX Unsigned32 (0..65535) 1487 MAX-ACCESS read-create 1488 STATUS current 1489 DESCRIPTION 1490 "If mplsTunnelHopAddrType is set to asNumber(2), then 1491 this value will contain the AS number of this hop. 1492 This object is otherwise insignificant and should 1493 contain a value of 0 to indicate this fact." 1494 ::= { mplsTunnelHopEntry 8 } 1496 mplsTunnelHopLspId OBJECT-TYPE 1497 SYNTAX MplsLSPID 1498 MAX-ACCESS read-create 1499 STATUS current 1500 DESCRIPTION 1501 "If mplsTunnelHopAddrType is set to lspId(3), then 1502 this value will contain the LSPID of a tunnel of 1503 this hop. The present tunnel being configured is 1504 tunneled through this hop (using label stacking). 1505 This object is otherwise insignificant and should 1506 contain a value of 0 to indicate this fact." 1507 ::= { mplsTunnelHopEntry 9 } 1509 mplsTunnelHopType OBJECT-TYPE 1510 SYNTAX INTEGER { 1511 strict(1), 1512 loose(2) 1513 } 1514 MAX-ACCESS read-create 1515 STATUS current 1516 DESCRIPTION 1517 "Denotes whether this tunnel hop is routed in a 1518 strict or loose fashion." 1519 ::= { mplsTunnelHopEntry 10 } 1521 mplsTunnelHopIncludeExclude OBJECT-TYPE 1522 SYNTAX INTEGER { 1523 include(1), 1524 exclude(2) 1525 } 1526 MAX-ACCESS read-create 1527 STATUS current 1528 DESCRIPTION 1529 "If this value is set to include(1), then this 1530 indicates that this hop must be included in the 1531 tunnel's path. If this value is set to exclude(2), 1532 then this hop must be avoided when calculating the 1533 path for this tunnel. The default value of this 1534 object is include(1), so that by default all 1535 indicated hops are included in the CSPF path 1536 computation." 1537 DEFVAL { include } 1538 ::= { mplsTunnelHopEntry 11 } 1540 mplsTunnelHopPathOptionName OBJECT-TYPE 1541 SYNTAX DisplayString 1542 MAX-ACCESS read-create 1543 STATUS current 1544 DESCRIPTION 1545 "The description of this series of hops as they 1546 relate to the specified path option." 1547 ::= { mplsTunnelHopEntry 12 } 1549 mplsTunnelHopEntryPathComp OBJECT-TYPE 1550 SYNTAX INTEGER { 1551 dynamic(1), -- CSPF computed 1552 explicit(2) -- strict hop 1553 } 1554 MAX-ACCESS read-create 1555 STATUS current 1556 DESCRIPTION 1557 "If this value is set to dynamic, then the user 1558 should only specify the source and destination of 1559 the path and expect that the CSPF will calculate 1560 the remainder of the path. If this value is set to 1561 explicit, the user should specify the entire path 1562 for the tunnel to take. This path may contain 1563 strict or loose hops. Each hop along a specific 1564 path should have this object set to the same value" 1565 ::= { mplsTunnelHopEntry 13 } 1567 mplsTunnelHopRowStatus OBJECT-TYPE 1568 SYNTAX RowStatus 1569 MAX-ACCESS read-create 1570 STATUS current 1571 DESCRIPTION 1572 "This variable is used to create, modify, and/or 1573 delete a row in this table." 1574 ::= { mplsTunnelHopEntry 14 } 1576 mplsTunnelHopStorageType OBJECT-TYPE 1577 SYNTAX StorageType 1578 MAX-ACCESS read-create 1579 STATUS current 1580 DESCRIPTION 1581 "This variable indicates the storage type for this 1582 object. This object cannot be modified if 1583 mplsTunnelHopRowStatus is active(1). If this 1584 variable is set to readOnly(5), and the 1585 corresponding entry is removed, then the agent must 1586 remove this row shortly thereafter [RFC2579]." 1587 ::= { mplsTunnelHopEntry 15 } 1589 -- End of mplsTunnelHopTable 1591 -- Begin of mplsTunnelResourceTable 1593 mplsTunnelResourceIndexNext OBJECT-TYPE 1594 SYNTAX Unsigned32 (0.. 2147483647) 1595 MAX-ACCESS read-only 1596 STATUS current 1597 DESCRIPTION 1598 "This object contains the next appropriate value to 1599 be used for mplsTunnelResourceIndex when creating 1600 entries in the mplsTunnelResourceTable. If the 1601 number of unassigned entries is exhausted, a 1602 retrival operation will return a value of 0. This 1603 object may also return a value of 0 when the LSR is 1604 unable to accept conceptual row creation, for 1605 example, if the mplsTunnelTable is implemented as 1606 read-only. To obtain the mplsTunnelResourceIndex 1607 value for a new entry, the manager must first issue 1608 a management protocol retrieval operation to obtain 1609 the current value of this object. The agent should 1610 modify the value to reflect the next unassigned 1611 index after each retrieval operation. After a 1612 manager retrieves a value the agent will determine 1613 through its local policy when this index value will 1614 be made available for reuse." 1615 ::= { mplsTeObjects 5 } 1617 mplsTunnelResourceTable OBJECT-TYPE 1618 SYNTAX SEQUENCE OF MplsTunnelResourceEntry 1619 MAX-ACCESS not-accessible 1620 STATUS current 1621 DESCRIPTION 1622 "The mplsTunnelResourceTable allows a manager to 1623 specify which resources are desired for an MPLS 1624 tunnel. This table also allows several tunnels to 1625 point to a single entry in this table, implying 1626 that these tunnels should share resources." 1627 ::= { mplsTeObjects 6 } 1629 mplsTunnelResourceEntry OBJECT-TYPE 1630 SYNTAX MplsTunnelResourceEntry 1631 MAX-ACCESS not-accessible 1632 STATUS current 1633 DESCRIPTION 1634 "An entry in this table represents a set of resources 1635 for an MPLS tunnel. An entry can be created by a 1636 network administrator or by an SNMP agent as 1637 instructed by any MPLS signalling protocol." 1638 INDEX { mplsTunnelResourceIndex } 1639 ::= { mplsTunnelResourceTable 1 } 1641 MplsTunnelResourceEntry ::= SEQUENCE { 1642 mplsTunnelResourceIndex Unsigned32, 1643 mplsTunnelResourceMaxRate MplsBitRate, 1644 mplsTunnelResourceMeanRate MplsBitRate, 1645 mplsTunnelResourceMaxBurstSize MplsBurstSize, 1646 mplsTunnelResourceMeanBurstSize MplsBurstSize, 1647 mplsTunnelResourceExBurstSize MplsBurstSize, 1648 mplsTunnelResourceFrequency INTEGER, 1649 mplsTunnelResourceWeight Unsigned32, 1650 mplsTunnelResourceRowStatus RowStatus, 1651 mplsTunnelResourceStorageType StorageType 1652 } 1654 mplsTunnelResourceIndex OBJECT-TYPE 1655 SYNTAX Unsigned32 (1..2147483647) 1656 MAX-ACCESS not-accessible 1657 STATUS current 1658 DESCRIPTION 1659 "Uniquely identifies this row." 1660 ::= { mplsTunnelResourceEntry 1 } 1662 mplsTunnelResourceMaxRate OBJECT-TYPE 1663 SYNTAX MplsBitRate 1664 UNITS "bits per second" 1665 MAX-ACCESS read-create 1666 STATUS current 1667 DESCRIPTION 1668 "The maximum rate in bits/second. Note that setting 1669 mplsTunnelResourceMaxRate, 1670 mplsTunnelResourceMeanRate, and 1671 mplsTunnelResourceMaxBurstSize to 0 indicates best- 1672 effort treatment. 1673 This object is copied to an instance of 1674 mplsTrafficParamMaxRate in mplsTrafficParamTable 1675 the OID of which is copied into the corresponding 1676 mplsInSegmentTrafficParamPtr." 1677 REFERENCE 1678 "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS 1679 Label Switching Router Management Information Base, 1680 Internet Draft , 1681 October 2002." 1682 ::= { mplsTunnelResourceEntry 2 } 1684 mplsTunnelResourceMeanRate OBJECT-TYPE 1685 SYNTAX MplsBitRate 1686 UNITS "bits per second" 1687 MAX-ACCESS read-create 1688 STATUS current 1689 DESCRIPTION 1690 "This object is copied into an instance of 1691 mplsTrafficParamMeanRate in the 1692 mplsTrafficParamTable. The OID of this table entry 1693 is then copied into the corresponding 1694 mplsInSegmentTrafficParamPtr. 1696 When resource allocation is performed as requested 1697 by this TSpec object, it is copied into an entry in 1698 mplsTrafficParamTable [LSRMIB]: 1699 mplsTunnelInMeanRate to mplsTrafficParamMeanRate. 1700 The OID of this entry is copied to 1701 mplsInSegmentTrafficParamPtr of the corresponding 1702 in-segment entry." 1703 REFERENCE 1704 "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS 1705 Label Switching Router Management Information Base, 1706 Internet Draft , 1707 October 2002." 1708 ::= { mplsTunnelResourceEntry 3 } 1710 mplsTunnelResourceMaxBurstSize OBJECT-TYPE 1711 SYNTAX MplsBurstSize 1712 UNITS "bytes" 1713 MAX-ACCESS read-create 1714 STATUS current 1715 DESCRIPTION 1716 "The maximum burst size in bytes. This object is 1717 copied to mplsInSegmentMaxBurstSize of the 1718 corresponding in-segment. 1720 When resource allocation is performed as requested 1721 by this TSpec object, it is copied into an entry in 1722 mplsTrafficParamTable [LSRMIB]: 1723 mplsTunnelInMaxBurstSize to 1724 mplsTrafficParamMaxBurstSize. The OID of this entry 1725 is copied to mplsInSegmentTrafficParamPtr of the 1726 corresponding in-segment entry." 1727 REFERENCE 1728 "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS 1729 Label Switching Router Management Information Base, 1730 Internet Draft , 1731 October 2002." 1732 ::= { mplsTunnelResourceEntry 4 } 1734 mplsTunnelResourceMeanBurstSize OBJECT-TYPE 1735 SYNTAX MplsBurstSize 1736 UNITS "bytes" 1737 MAX-ACCESS read-create 1738 STATUS current 1739 DESCRIPTION 1740 "The mean burst size in bytes. The implementations 1741 which do not implement this variable must return 0 1742 for this value and must not allow a user to set 1743 this value." 1744 ::= { mplsTunnelResourceEntry 5 } 1746 mplsTunnelResourceExBurstSize OBJECT-TYPE 1747 SYNTAX MplsBurstSize 1748 UNITS "bytes" 1749 MAX-ACCESS read-create 1750 STATUS current 1751 DESCRIPTION 1752 "The Excess burst size in bytes. The implementations 1753 which do not implement this variable must return 0 1754 for this value and must not allow a user to set 1755 this value." 1756 REFERENCE 1757 "CR-LDP Specification, Section 4.3." 1758 ::= { mplsTunnelResourceEntry 6 } 1760 mplsTunnelResourceFrequency OBJECT-TYPE 1761 SYNTAX INTEGER { 1762 unspecified(1), 1763 frequent(2), 1764 veryFrequent(3) 1765 } 1766 MAX-ACCESS read-create 1767 STATUS current 1768 DESCRIPTION 1769 "The granularity of the availability of committed 1770 rate. The implementations which do not implement 1771 this variable must return unspecified(1) for this 1772 value and must not allow a user to set this value." 1773 REFERENCE 1774 "CR-LDP Specification, Section 4.3." 1775 ::= { mplsTunnelResourceEntry 7 } 1777 mplsTunnelResourceWeight OBJECT-TYPE 1778 SYNTAX Unsigned32(0..255) 1779 MAX-ACCESS read-create 1780 STATUS current 1781 DESCRIPTION 1782 "The relative weight for using excess bandwidth above 1783 its committed rate. The value of 0 means that 1784 weight is not applicable for the CR-LSP." 1785 REFERENCE 1786 "CR-LDP Specification, Section 4.3." 1787 ::= { mplsTunnelResourceEntry 8 } 1789 mplsTunnelResourceRowStatus OBJECT-TYPE 1790 SYNTAX RowStatus 1791 MAX-ACCESS read-create 1792 STATUS current 1793 DESCRIPTION 1794 "This variable is used to create, modify, and/or 1795 delete a row in this table." 1796 ::= { mplsTunnelResourceEntry 9 } 1798 mplsTunnelResourceStorageType OBJECT-TYPE 1799 SYNTAX StorageType 1800 MAX-ACCESS read-create 1801 STATUS current 1802 DESCRIPTION 1803 "This variable indicates the storage type for this 1804 object. This object cannot be modified if 1805 mplsTunnelResourceRowStatus is active(1). If this 1806 variable is set to readOnly(5), and the 1807 corresponding entry is removed, then the agent must 1808 remove this row shortly thereafter [RFC2579]." 1809 ::= { mplsTunnelResourceEntry 10 } 1811 -- End mplsTunnelResourceTable 1813 -- Tunnel Actual Route Hop table. 1815 mplsTunnelARHopTable OBJECT-TYPE 1816 SYNTAX SEQUENCE OF MplsTunnelARHopEntry 1817 MAX-ACCESS not-accessible 1818 STATUS current 1819 DESCRIPTION 1820 "The mplsTunnelARHopTable is used to indicate the 1821 hops, strict or loose, for an MPLS tunnel defined 1822 in mplsTunnelTable, as reported by the MPLS 1823 signalling protocol, for the outgoing direction of 1824 the tunnel. Each row in this table is indexed by 1825 mplsTunnelARHopListIndex. Each row also has a 1826 secondary index mplsTunnelARHopIndex, corresponding 1827 to the next hop that this row corresponds to. The 1828 first row in the table is the first hop after the 1829 origination point of the tunnel. In case we want 1830 to specify a particular interface on the 1831 originating LSR of an outgoing tunnel by which we 1832 want packets to exit the LSR, we specify this as 1833 the first hop for this tunnel in 1834 mplsTunnelARHopTable. 1836 Please note that since the information necessary to 1837 build entries within this table are not provided by 1838 some MPLS signalling protocols, implementation of 1839 this table is optional. Furthermore, since the 1840 information in this table is actually provided by 1841 the MPLS signalling protocol after the path has 1842 been set-up, the entries in this table are provided 1843 only for observation, and hence, all variables in 1844 this table are accessible exclusively as read- 1845 only." 1846 ::= { mplsTeObjects 7 } 1848 mplsTunnelARHopEntry OBJECT-TYPE 1849 SYNTAX MplsTunnelARHopEntry 1850 MAX-ACCESS not-accessible 1851 STATUS current 1852 DESCRIPTION 1853 "An entry in this table represents a tunnel hop. An 1854 entry is created by a network administrator for 1855 signaled ERLSP set up by an MPLS signalling 1856 protocol." 1857 INDEX { mplsTunnelARHopListIndex, mplsTunnelARHopIndex } 1858 ::= { mplsTunnelARHopTable 1 } 1860 MplsTunnelARHopEntry ::= SEQUENCE { 1861 mplsTunnelARHopListIndex MplsPathIndex, 1862 mplsTunnelARHopIndex MplsPathIndex, 1863 mplsTunnelARHopAddrType INTEGER, 1864 mplsTunnelARHopIpAddrType InetAddressType, 1865 mplsTunnelARHopIpAddr InetAddress, 1866 mplsTunnelARHopIpPrefixLen InetAddressPrefixLength, 1867 mplsTunnelARHopAsNumber Unsigned32, 1868 mplsTunnelARHopLspId MplsLSPID 1869 } 1871 mplsTunnelARHopListIndex OBJECT-TYPE 1872 SYNTAX MplsPathIndex 1873 MAX-ACCESS not-accessible 1874 STATUS current 1875 DESCRIPTION 1876 "Primary index into this table identifying a 1877 particular recorded hop list." 1878 ::= { mplsTunnelARHopEntry 1 } 1880 mplsTunnelARHopIndex OBJECT-TYPE 1881 SYNTAX MplsPathIndex 1882 MAX-ACCESS not-accessible 1883 STATUS current 1884 DESCRIPTION 1885 "Secondary index into this table identifying the 1886 particular hop." 1887 ::= { mplsTunnelARHopEntry 2 } 1889 mplsTunnelARHopAddrType OBJECT-TYPE 1890 SYNTAX INTEGER { 1891 ipAddr(1), 1892 asNumber(2), 1893 lspId(3) 1894 } 1895 MAX-ACCESS read-only 1896 STATUS current 1897 DESCRIPTION 1898 "Denotes the address type of this tunnel hop." 1899 DEFVAL { ipAddr } 1900 ::= { mplsTunnelARHopEntry 3 } 1902 mplsTunnelARHopIpAddrType OBJECT-TYPE 1903 SYNTAX InetAddressType 1904 MAX-ACCESS read-create 1905 STATUS current 1906 DESCRIPTION 1907 "If mplsTunnelARHopAddrType is set to ipAddr(1) then 1908 this value will contain the IP address type of this 1909 hop. If mplsTunnelARHopAddrType is set to 1910 asNumber(2) or lspId(3) then a management entity 1911 SHOULD ignore this object." 1912 ::= { mplsTunnelARHopEntry 4 } 1914 mplsTunnelARHopIpAddr OBJECT-TYPE 1915 SYNTAX InetAddress 1916 MAX-ACCESS read-only 1917 STATUS current 1918 DESCRIPTION 1919 "If mplsTunnelARHopIpAddrType is set to ipV4(1) or 1920 ipV6(2), then this value will contain respectively 1921 the IPv4 address or the IPv6 address of this hop. 1922 Otherwise a management entity SHOULD set this to 0 1923 and an agent MUST ignore it. Likewise an agent MUST 1924 return a value of 0 for a retrieval operation." 1925 ::= { mplsTunnelARHopEntry 5 } 1927 mplsTunnelARHopIpPrefixLen OBJECT-TYPE 1928 SYNTAX InetAddressPrefixLength 1929 MAX-ACCESS read-only 1930 STATUS current 1931 DESCRIPTION 1932 "If mplsTunnelARHopIpAddrType is set to ipV4(1) or 1933 ipV6(2), then this value will contain an 1934 appropriate prefix length for this hop. Otherwise a 1935 management entity SHOULD set this object to 0 and 1936 an agent MUST ignore it." 1937 ::= { mplsTunnelARHopEntry 6 } 1939 mplsTunnelARHopAsNumber OBJECT-TYPE 1940 SYNTAX Unsigned32 (0..65535) 1941 MAX-ACCESS read-only 1942 STATUS current 1943 DESCRIPTION 1944 "If mplsTunnelARHopAddrType is set to asNumber(2), 1945 then this value will contain the AS number of this 1946 hop. This object is otherwise insignificant and 1947 should contain a value of 0 to indicate this fact." 1948 ::= { mplsTunnelARHopEntry 7 } 1950 mplsTunnelARHopLspId OBJECT-TYPE 1951 SYNTAX MplsLSPID 1952 MAX-ACCESS read-only 1953 STATUS current 1954 DESCRIPTION 1955 "If mplsTunnelARHopAddrType is set to lspId(3), then 1956 this value will contain the LSP ID of this hop. 1957 This object is otherwise insignificant and should 1958 contain a value of 0 to indicate this fact." 1959 ::= { mplsTunnelARHopEntry 8 } 1961 -- End of mplsTunnelARHopTable 1963 -- Tunnel Computed Hop table. 1965 mplsTunnelCHopTable OBJECT-TYPE 1966 SYNTAX SEQUENCE OF MplsTunnelCHopEntry 1967 MAX-ACCESS not-accessible 1968 STATUS current 1969 DESCRIPTION 1970 "The mplsTunnelCHopTable is used to indicate the 1971 hops, strict or loose, for an MPLS tunnel defined 1972 in mplsTunnelTable, as computed by a constraint- 1973 based routing protocol, based on the 1974 mplsTunnelHopTable for the outgoing direction of 1975 the tunnel. Each row in this table is indexed by 1976 mplsTunnelCHopListIndex. Each row also has a 1977 secondary index mplsTunnelCHopIndex, corresponding 1978 to the next hop that this row corresponds to. The 1979 first row in the table is the first hop after the 1980 origination point of the tunnel. In case we want 1981 to specify a particular interface on the 1982 originating LSR of an outgoing tunnel by which we 1983 want packets to exit the LSR, we specify this as 1984 the first hop for this tunnel in 1985 mplsTunnelCHopTable. 1987 Please note that since the information necessary to 1988 build entries within this table may not be 1989 supported by some LSRs, implementation of this 1990 table is optional. Furthermore, since the 1991 information in this table is actually provided by 1992 routing protocol after the path has been computed, 1993 the entries in this table are provided only for 1994 observation, and hence, all variables in this table 1995 are accessible exclusively as read-only." 1996 ::= { mplsTeObjects 8 } 1998 mplsTunnelCHopEntry OBJECT-TYPE 1999 SYNTAX MplsTunnelCHopEntry 2000 MAX-ACCESS not-accessible 2001 STATUS current 2002 DESCRIPTION 2003 "An entry in this table represents a tunnel hop. An 2004 entry in this table is created by a constraint- 2005 based routing protocol based on the hops specified 2006 in the corresponding mplsTunnelHopTable." 2007 INDEX { mplsTunnelCHopListIndex, mplsTunnelCHopIndex } 2008 ::= { mplsTunnelCHopTable 1 } 2010 MplsTunnelCHopEntry ::= SEQUENCE { 2011 mplsTunnelCHopListIndex MplsPathIndex, 2012 mplsTunnelCHopIndex MplsPathIndex, 2013 mplsTunnelCHopAddrType INTEGER, 2014 mplsTunnelCHopIpAddrType InetAddressType, 2015 mplsTunnelCHopIpAddr InetAddress, 2016 mplsTunnelCHopIpPrefixLen InetAddressPrefixLength, 2017 mplsTunnelCHopAsNumber Unsigned32, 2018 mplsTunnelCHopLspId MplsLSPID, 2019 mplsTunnelCHopType INTEGER 2020 } 2022 mplsTunnelCHopListIndex OBJECT-TYPE 2023 SYNTAX MplsPathIndex 2024 MAX-ACCESS not-accessible 2025 STATUS current 2026 DESCRIPTION 2027 "Primary index into this table identifying a 2028 particular computed hop list." 2029 ::= { mplsTunnelCHopEntry 1 } 2031 mplsTunnelCHopIndex OBJECT-TYPE 2032 SYNTAX MplsPathIndex 2033 MAX-ACCESS not-accessible 2034 STATUS current 2035 DESCRIPTION 2036 "Secondary index into this table identifying the 2037 particular hop." 2038 ::= { mplsTunnelCHopEntry 2 } 2040 mplsTunnelCHopAddrType OBJECT-TYPE 2041 SYNTAX INTEGER { 2042 ipAddr(1), 2043 asNumber(2), 2044 lspId(3) 2045 } 2046 MAX-ACCESS read-only 2047 STATUS current 2048 DESCRIPTION 2049 "Denotes the address type of this tunnel hop. Note 2050 that lspId(3) is a valid option only for tunnels 2051 signaled via CRLDP." 2052 DEFVAL { ipAddr } 2053 ::= { mplsTunnelCHopEntry 3 } 2055 mplsTunnelCHopIpAddrType OBJECT-TYPE 2056 SYNTAX InetAddressType 2057 MAX-ACCESS read-create 2058 STATUS current 2059 DESCRIPTION 2060 "If mplsTunnelCHopAddrType is set to ipAddr(1) then 2061 this value will contain the IP address type of this 2062 hop. If mplsTunnelCHopAddrType is set to 2063 asNumber(2) or lspId(3) then a management entity 2064 SHOULD ignore this object." 2065 ::= { mplsTunnelCHopEntry 4 } 2067 mplsTunnelCHopIpAddr OBJECT-TYPE 2068 SYNTAX InetAddress 2069 MAX-ACCESS read-only 2070 STATUS current 2071 DESCRIPTION 2072 "If mplsTunnelCHopIpAddrType is set to ipV4(1) or 2073 ipV6(2), then this value will contain respectively 2074 the IPv4 address or the IPv6 address of this hop. 2075 Otherwise a management entity SHOULD set this to 0 2076 and an agent MUST ignore it. Likewise an agent MUST 2077 return a value of 0 for a retrieval operation." 2078 ::= { mplsTunnelCHopEntry 5 } 2080 mplsTunnelCHopIpPrefixLen OBJECT-TYPE 2081 SYNTAX InetAddressPrefixLength 2082 MAX-ACCESS read-only 2083 STATUS current 2084 DESCRIPTION 2085 "If mplsTunnelCHopIpAddrType is set to ipV4(1) or 2086 ipV6(2), then this value will contain an 2087 appropriate prefix length for this hop. Otherwise a 2088 management entity SHOULD set this object to 0 and 2089 an agent MUST ignore it. " 2090 ::= { mplsTunnelCHopEntry 6 } 2092 mplsTunnelCHopAsNumber OBJECT-TYPE 2093 SYNTAX Unsigned32 (0..65535) 2094 MAX-ACCESS read-only 2095 STATUS current 2096 DESCRIPTION 2097 "If mplsTunnelCHopAddrType is set to asNumber(2), 2098 then this value will contain the AS number of this 2099 hop. This object is otherwise insignificant and 2100 should contain a value of 0 to indicate this fact." 2101 ::= { mplsTunnelCHopEntry 7 } 2103 mplsTunnelCHopLspId OBJECT-TYPE 2104 SYNTAX MplsLSPID 2105 MAX-ACCESS read-only 2106 STATUS current 2107 DESCRIPTION 2108 "If mplsTunnelCHopAddrType is set to lspId(3), then 2109 this value will contain the LSP ID of this hop. 2110 This object is otherwise insignificant and should 2111 contain a value of 0 to indicate this fact." 2112 ::= { mplsTunnelCHopEntry 8 } 2114 mplsTunnelCHopType OBJECT-TYPE 2115 SYNTAX INTEGER { 2116 strict(1), 2117 loose(2) 2118 } 2119 MAX-ACCESS read-only 2120 STATUS current 2121 DESCRIPTION 2122 "Denotes whether this is tunnel hop is routed in a 2123 strict or loose fashion." 2124 ::= { mplsTunnelCHopEntry 9 } 2126 -- End of mplsTunnelCHopTable 2128 -- MPLS Tunnel Performance Table. 2130 mplsTunnelPerfTable OBJECT-TYPE 2131 SYNTAX SEQUENCE OF MplsTunnelPerfEntry 2132 MAX-ACCESS not-accessible 2133 STATUS current 2134 DESCRIPTION 2135 "This table provides per-tunnel MPLS performance 2136 information." 2137 ::= { mplsTeObjects 9 } 2139 mplsTunnelPerfEntry OBJECT-TYPE 2140 SYNTAX MplsTunnelPerfEntry 2141 MAX-ACCESS not-accessible 2142 STATUS current 2143 DESCRIPTION 2144 "An entry in this table is created by the LSR for 2145 every tunnel. Its is an extension to 2146 mplsTunnelEntry." 2147 AUGMENTS { mplsTunnelEntry } 2148 ::= { mplsTunnelPerfTable 1 } 2150 MplsTunnelPerfEntry ::= SEQUENCE { 2151 mplsTunnelPerfPackets Counter32, 2152 mplsTunnelPerfHCPackets Counter64, 2153 mplsTunnelPerfErrors Counter32, 2154 mplsTunnelPerfBytes Counter32, 2155 mplsTunnelPerfHCBytes Counter64 2156 } 2158 mplsTunnelPerfPackets OBJECT-TYPE 2159 SYNTAX Counter32 2160 MAX-ACCESS read-only 2161 STATUS current 2162 DESCRIPTION 2163 "Number of packets forwarded by the tunnel." 2164 ::= { mplsTunnelPerfEntry 1 } 2166 mplsTunnelPerfHCPackets OBJECT-TYPE 2167 SYNTAX Counter64 2168 MAX-ACCESS read-only 2169 STATUS current 2170 DESCRIPTION 2171 "High capacity counter for number of packets 2172 forwarded by the tunnel." 2173 ::= { mplsTunnelPerfEntry 2 } 2175 mplsTunnelPerfErrors OBJECT-TYPE 2176 SYNTAX Counter32 2177 MAX-ACCESS read-only 2178 STATUS current 2179 DESCRIPTION 2180 "Number of packets with errors." 2181 ::= { mplsTunnelPerfEntry 3 } 2183 mplsTunnelPerfBytes OBJECT-TYPE 2184 SYNTAX Counter32 2185 MAX-ACCESS read-only 2186 STATUS current 2187 DESCRIPTION 2188 "Number of bytes forwarded by the tunnel." 2189 ::= { mplsTunnelPerfEntry 4 } 2191 mplsTunnelPerfHCBytes OBJECT-TYPE 2192 SYNTAX Counter64 2193 MAX-ACCESS read-only 2194 STATUS current 2195 DESCRIPTION 2196 "High capacity counter for number of bytes forwarded 2197 by the tunnel." 2198 ::= { mplsTunnelPerfEntry 5 } 2200 -- End of mplsTunnelPerfTable 2202 -- CR-LDP Tunnel Resource Table 2204 mplsTunnelCRLDPResTable OBJECT-TYPE 2205 SYNTAX SEQUENCE OF MplsTunnelCRLDPResEntry 2206 MAX-ACCESS not-accessible 2207 STATUS current 2208 DESCRIPTION 2209 "The mplsTunnelCRLDPResTable allows a manager to 2210 specify which CR-LDP-specific resources are desired 2211 for an MPLS tunnel if that tunnel is signaled using 2212 CR-LDP. Note that these attributes are in addition 2213 to those specified in mplsTunnelResourceTable. This 2214 table also allows several tunnels to point to a 2215 single entry in this table, implying that these 2216 tunnels should share resources." 2217 ::= { mplsTeObjects 10 } 2219 mplsTunnelCRLDPResEntry OBJECT-TYPE 2220 SYNTAX MplsTunnelCRLDPResEntry 2221 MAX-ACCESS not-accessible 2222 STATUS current 2223 DESCRIPTION 2224 "An entry in this table represents a set of resources 2225 for an MPLS tunnel established using CRLDP 2226 (mplsTunnelSignallingProto equal to crldp (3)). An 2227 entry can be created by a network administrator or 2228 by an SNMP agent as instructed by any MPLS 2229 signalling protocol." 2230 INDEX { mplsTunnelResourceIndex } 2231 ::= { mplsTunnelCRLDPResTable 1 } 2233 MplsTunnelCRLDPResEntry ::= SEQUENCE { 2234 mplsTunnelCRLDPResMeanBurstSize MplsBurstSize, 2235 mplsTunnelCRLDPResExBurstSize MplsBurstSize, 2236 mplsTunnelCRLDPResFrequency INTEGER, 2237 mplsTunnelCRLDPResWeight Unsigned32, 2238 mplsTunnelCRLDPResFlags Unsigned32, 2239 mplsTunnelCRLDPResRowStatus RowStatus, 2240 mplsTunnelCRLDPResStorageType StorageType 2241 } 2243 mplsTunnelCRLDPResMeanBurstSize OBJECT-TYPE 2244 SYNTAX MplsBurstSize 2245 UNITS "bytes" 2246 MAX-ACCESS read-create 2247 STATUS current 2248 DESCRIPTION 2249 "The mean burst size in bytes." 2250 ::= { mplsTunnelCRLDPResEntry 2 } 2252 mplsTunnelCRLDPResExBurstSize OBJECT-TYPE 2253 SYNTAX MplsBurstSize 2254 UNITS "bytes" 2255 MAX-ACCESS read-create 2256 STATUS current 2257 DESCRIPTION 2258 "The Excess burst size in bytes." 2259 REFERENCE 2260 "CR-LDP Specification, Section 4.3." 2261 ::= { mplsTunnelCRLDPResEntry 3 } 2263 mplsTunnelCRLDPResFrequency OBJECT-TYPE 2264 SYNTAX INTEGER { 2265 unspecified(1), 2266 frequent(2), 2267 veryFrequent(3) 2268 } 2269 MAX-ACCESS read-create 2270 STATUS current 2271 DESCRIPTION 2272 "The granularity of the availability of committed 2273 rate." 2274 REFERENCE 2275 "CR-LDP Specification, Section 4.3." 2276 ::= { mplsTunnelCRLDPResEntry 4 } 2278 mplsTunnelCRLDPResWeight OBJECT-TYPE 2279 SYNTAX Unsigned32(0..255) 2280 MAX-ACCESS read-create 2281 STATUS current 2282 DESCRIPTION 2283 "The relative weight for using excess bandwidth above 2284 its committed rate. The value of 0 means that 2285 weight is not applicable for the CR-LSP." 2286 REFERENCE 2287 "CR-LDP Specification, Section 4.3." 2288 DEFVAL { 0 } 2289 ::= { mplsTunnelCRLDPResEntry 5 } 2291 mplsTunnelCRLDPResFlags OBJECT-TYPE 2292 SYNTAX Unsigned32 (0..63) 2293 MAX-ACCESS read-create 2294 STATUS current 2295 DESCRIPTION 2296 "The value of the 1 byte Flags conveyed as part of 2297 the traffic parameters during the establishment of 2298 the CRLSP. The bits in this object are to be 2299 interpreted as follows. 2301 +--+--+--+--+--+--+--+--+ 2302 | Res |F6|F5|F4|F3|F2|F1| 2303 +--+--+--+--+--+--+--+--+ 2305 Res - These bits are reserved. Zero on transmission. 2306 Ignored on receipt. 2307 F1 - Corresponds to the PDR. 2308 F2 - Corresponds to the PBS. 2309 F3 - Corresponds to the CDR. 2310 F4 - Corresponds to the CBS. 2311 F5 - Corresponds to the EBS. 2312 F6 - Corresponds to the Weight. 2314 Each flag if is a Negotiable Flag corresponding to a 2315 Traffic Parameter. The Negotiable Flag value zero 2316 denotes Not Negotiable and value one denotes 2317 Negotiable." 2318 REFERENCE 2319 "1. Section 4.3, Constraint-Based LSP Setup using 2320 LDP, Jamoussi (Editor), RFC 3212, January 2002" 2321 DEFVAL { 0 } 2322 ::= { mplsTunnelCRLDPResEntry 6 } 2324 mplsTunnelCRLDPResRowStatus OBJECT-TYPE 2325 SYNTAX RowStatus 2326 MAX-ACCESS read-create 2327 STATUS current 2328 DESCRIPTION 2329 "This variable is used to create, modify, and/or 2330 delete a row in this table." 2331 ::= { mplsTunnelCRLDPResEntry 7 } 2333 mplsTunnelCRLDPResStorageType OBJECT-TYPE 2334 SYNTAX StorageType 2335 MAX-ACCESS read-create 2336 STATUS current 2337 DESCRIPTION 2338 "This variable indicates the storage type for this 2339 object. This object cannot be modified if 2340 mplsTunnelCRLDPResResourceRowStatus is active(1). 2341 If this variable is set to readOnly(5), and the 2342 corresponding entry is removed, then the agent must 2343 remove this row shortly thereafter [RFC2579]." 2344 ::= { mplsTunnelCRLDPResEntry 8 } 2346 -- Notifications. 2348 mplsTunnelNotificationEnable OBJECT-TYPE 2349 SYNTAX TruthValue 2350 MAX-ACCESS read-write 2351 STATUS current 2352 DESCRIPTION 2353 "If this object is true, then it enables the 2354 generation of mplsTunnelUp and mplsTunnelDown 2355 traps, otherwise these traps are not emitted." 2356 DEFVAL { false } 2357 ::= { mplsTeObjects 11 } 2359 mplsTunnelUp NOTIFICATION-TYPE 2360 OBJECTS { 2361 mplsTunnelAdminStatus, 2362 mplsTunnelOperStatus 2363 } 2364 STATUS current 2365 DESCRIPTION 2366 "This notification is generated when a 2367 mplsTunnelOperStatus object for one of the 2368 configured tunnels is about to leave the down state 2369 and transition into some other state (but not into 2370 the notPresent state). This other state is 2371 indicated by the included value of 2372 mplsTunnelOperStatus." 2373 ::= { mplsTeNotifications 1 } 2375 mplsTunnelDown NOTIFICATION-TYPE 2376 OBJECTS { 2377 mplsTunnelAdminStatus, 2378 mplsTunnelOperStatus 2379 } 2380 STATUS current 2381 DESCRIPTION 2382 "This notification is generated when a 2383 mplsTunnelOperStatus object for one of the 2384 configured tunnels is about to enter the down state 2385 from some other state (but not from the notPresent 2386 state). This other state is indicated by the 2387 included value of mplsTunnelOperStatus." 2388 ::= { mplsTeNotifications 2 } 2390 mplsTunnelRerouted NOTIFICATION-TYPE 2391 OBJECTS { 2392 mplsTunnelAdminStatus, 2393 mplsTunnelOperStatus 2394 } 2395 STATUS current 2396 DESCRIPTION 2397 "This notification is generated when a tunnel is 2398 rerouted. If the actual path is used, then this 2399 tunnel's entry MAY contain the new path for this 2400 tunnel some time after this trap is issued by the 2401 agent." 2402 ::= { mplsTeNotifications 3 } 2404 mplsTunnelReoptimized NOTIFICATION-TYPE 2405 OBJECTS { 2406 mplsTunnelAdminStatus, 2407 mplsTunnelOperStatus 2408 } 2409 STATUS current 2410 DESCRIPTION 2411 "This notification is generated when a tunnel is 2412 reoptimized. If the actual path is used, then this 2413 tunnel's entry MAY contain the new path for this 2414 tunnel some time after this trap is issued by the 2415 agent." 2416 ::= { mplsTeNotifications 4 } 2418 -- End of notifications. 2420 -- Module compliance. 2422 mplsTeGroups 2423 OBJECT IDENTIFIER ::= { mplsTeConformance 1 } 2425 mplsTeCompliances 2426 OBJECT IDENTIFIER ::= { mplsTeConformance 2 } 2428 mplsTeModuleCompliance MODULE-COMPLIANCE 2429 STATUS current 2430 DESCRIPTION 2431 "Compliance statement for agents that support the 2432 MPLS-TE-MIB." 2433 MODULE -- this module 2435 -- The mandatory group has to be implemented by all 2436 -- LSRs that originate/terminate ESLSPs/tunnels. 2437 -- In addition, depending on the type of tunnels 2438 -- supported, other groups become mandatory as 2439 -- explained below. 2441 MANDATORY-GROUPS { 2442 mplsTunnelGroup, 2443 mplsTunnelScalarGroup 2444 } 2446 GROUP mplsTunnelManualGroup 2447 DESCRIPTION 2448 "This group is mandatory for devices which support 2449 manual configuration of tunnels, in addition to 2450 mplsTunnelGroup. The following constraints apply: 2451 mplsTunnelSignallingProto should be at least read- 2452 only with a value of none(1)." 2454 GROUP mplsTunnelSignaledGroup 2455 DESCRIPTION 2456 "This group is mandatory for devices which support 2457 signaled tunnel set up, in addition to 2458 mplsTunnelGroup. The following constraints apply: 2459 mplsTunnelSignallingProto should be at least read- 2460 only returning a value of ldp(2), or rsvp(3)." 2462 GROUP mplsTunnelIsNotIntfcGroup 2463 DESCRIPTION 2464 "This group is mandatory for devices which support 2465 tunnels that are not interfaces, in addition to 2466 mplsTunnelGroup. The following constraints apply: 2468 mplsTunnelIsIf must at least be read-only 2469 returning false(1)." 2471 GROUP mplsTunnelIsIntfcGroup 2472 DESCRIPTION 2473 "This group is mandatory for devices which support 2474 tunnels that are interfaces, in addition to 2475 mplsTunnelGroup. The following constraints apply: 2476 mplsTunnelIsIf must at least be read-only 2477 returning true(2)." 2479 GROUP mplsTeNotificationGroup 2480 DESCRIPTION 2481 "Objects in this group are optional unless 2482 notifications are supported." 2484 GROUP mplsTunnelCRLDPResOptionalGroup 2485 DESCRIPTION 2486 "Objects in this group are oiptional except for 2487 implementations supporting the CR-LDP protocol for 2488 signalling of TE tunnels." 2490 GROUP mplsTunnelOptionalGroup 2491 DESCRIPTION 2492 "Objects in this group are optional." 2494 -- mplsTunnelTable 2496 OBJECT mplsTunnelName 2497 MIN-ACCESS read-only 2498 DESCRIPTION 2499 "Write access is not required." 2501 OBJECT mplsTunnelDescr 2502 MIN-ACCESS read-only 2503 DESCRIPTION 2504 "Write access is not required." 2506 OBJECT mplsTunnelIsIf 2507 MIN-ACCESS read-only 2508 DESCRIPTION 2509 "Write access is not required." 2511 OBJECT mplsTunnelIfIndex 2512 DESCRIPTION 2513 "Write access is not required." 2515 OBJECT mplsTunnelXCPointer 2516 MIN-ACCESS read-only 2517 DESCRIPTION 2518 "Write access is not required." 2520 OBJECT mplsTunnelSignallingProto 2521 MIN-ACCESS read-only 2522 DESCRIPTION 2523 "Write access is not required." 2525 OBJECT mplsTunnelSetupPrio 2526 MIN-ACCESS read-only 2527 DESCRIPTION 2528 "Write access is not required." 2530 OBJECT mplsTunnelHoldingPrio 2531 MIN-ACCESS read-only 2532 DESCRIPTION 2533 "Write access is not required." 2535 OBJECT mplsTunnelSessionAttributes 2536 MIN-ACCESS read-only 2537 DESCRIPTION 2538 "Write access is not required." 2540 OBJECT mplsTunnelOwner 2541 MIN-ACCESS read-only 2542 DESCRIPTION 2543 "Write access is not required." 2545 OBJECT mplsTunnelLocalProtectInUse 2546 MIN-ACCESS read-only 2547 DESCRIPTION 2548 "Write access is not required." 2550 OBJECT mplsTunnelResourcePointer 2551 MIN-ACCESS read-only 2552 DESCRIPTION 2553 "Write access is not required." 2555 OBJECT mplsTunnelInstancePriority 2556 MIN-ACCESS read-only 2557 DESCRIPTION 2558 "Write access is not required." 2560 OBJECT mplsTunnelHopTableIndex 2561 MIN-ACCESS read-only 2562 DESCRIPTION 2563 "Write access is not required." 2565 OBJECT mplsTunnelPrimaryInstance 2566 MIN-ACCESS read-only 2567 DESCRIPTION 2568 "Write access is not required." 2570 OBJECT mplsTunnelPrimaryTimeUp 2571 MIN-ACCESS read-only 2572 DESCRIPTION 2573 "Write access is not required." 2575 OBJECT mplsTunnelPathChanges 2576 MIN-ACCESS read-only 2577 DESCRIPTION 2578 "Write access is not required." 2580 OBJECT mplsTunnelLastPathChange 2581 MIN-ACCESS read-only 2582 DESCRIPTION 2583 "Write access is not required." 2585 OBJECT mplsTunnelCreationTime 2586 MIN-ACCESS read-only 2587 DESCRIPTION 2588 "Write access is not required." 2590 OBJECT mplsTunnelStateTransitions 2591 MIN-ACCESS read-only 2592 DESCRIPTION 2593 "Write access is not required." 2595 OBJECT mplsTunnelARHopTableIndex 2596 DESCRIPTION 2597 "Write access is not required." 2599 OBJECT mplsTunnelCHopTableIndex 2600 DESCRIPTION 2601 "Write access is not required." 2603 OBJECT mplsTunnelAdminStatus 2604 SYNTAX INTEGER { up (1), down (2) } 2605 MIN-ACCESS read-only 2606 DESCRIPTION 2607 "Only up and down states must be supported. Write 2608 access is not required." 2610 OBJECT mplsTunnelOperStatus 2611 SYNTAX INTEGER { up (1), down (2) } 2612 DESCRIPTION 2613 "Only up and down states must be supported. Write 2614 access is not required." 2616 OBJECT mplsTunnelRowStatus 2617 SYNTAX INTEGER { 2618 active(1), 2619 notInService(2), 2620 createAndGo(4), 2621 destroy(6) 2622 } 2623 MIN-ACCESS read-only 2624 DESCRIPTION 2625 "The notReady(3) and createAndWait(5) states need 2626 not be supported. Write access is not required." 2628 OBJECT mplsTunnelStorageType 2629 SYNTAX INTEGER { other(1) } 2630 DESCRIPTION 2631 "Only other (1) needs to be supported." 2633 OBJECT mplsTunnelPathInUse 2634 MIN-ACCESS read-only 2635 DESCRIPTION 2636 "Read-only support is required." 2638 OBJECT mplsTunnelRole 2639 SYNTAX INTEGER { head(1) } 2640 MIN-ACCESS read-only 2641 DESCRIPTION 2642 "Only support for head is required." 2644 OBJECT mplsTunnelTotalUpTime 2645 MIN-ACCESS read-only 2646 DESCRIPTION 2647 "Read-only support is required." 2649 OBJECT mplsTunnelInstanceUpTime 2650 MIN-ACCESS read-only 2651 DESCRIPTION 2652 "Read-only support is required." 2654 -- mplsTunnelHopTable 2656 OBJECT mplsTunnelHopAddrType 2657 MIN-ACCESS read-only 2658 DESCRIPTION 2659 "Write access is not required." 2661 OBJECT mplsTunnelHopIpAddrType 2662 MIN-ACCESS read-only 2663 DESCRIPTION 2664 "Write access is not required." 2666 OBJECT mplsTunnelHopIpAddr 2667 MIN-ACCESS read-only 2668 DESCRIPTION 2669 "Write access is not required." 2671 OBJECT mplsTunnelHopIpPrefixLen 2672 MIN-ACCESS read-only 2673 DESCRIPTION 2674 "Write access is not required." 2676 OBJECT mplsTunnelHopAsNumber 2677 MIN-ACCESS read-only 2678 DESCRIPTION 2679 "Write access is not required." 2681 OBJECT mplsTunnelHopLspId 2682 MIN-ACCESS read-only 2683 DESCRIPTION 2684 "Write access is not required." 2686 OBJECT mplsTunnelHopType 2687 SYNTAX INTEGER { strict(1) } 2688 MIN-ACCESS read-only 2689 DESCRIPTION 2690 "loose(2) need not be supported. Write access is 2691 not required." 2693 OBJECT mplsTunnelHopIncludeExclude 2694 MIN-ACCESS read-only 2695 DESCRIPTION 2696 "Write access is not required." 2698 OBJECT mplsTunnelHopPathOptionName 2699 MIN-ACCESS read-only 2700 DESCRIPTION 2701 "Write access is not required." 2703 OBJECT mplsTunnelHopEntryPathComp 2704 MIN-ACCESS read-only 2705 DESCRIPTION 2706 "Write access is not required." 2708 OBJECT mplsTunnelHopRowStatus 2709 SYNTAX INTEGER { 2710 active(1), 2711 notInService(2), 2712 createAndGo(4), 2713 destroy(6) 2714 } 2715 MIN-ACCESS read-only 2716 DESCRIPTION 2717 "The notReady(3) and createAndWait(5) states need 2718 not be supported. Write access is not required." 2720 OBJECT mplsTunnelHopStorageType 2721 SYNTAX INTEGER { other(1) } 2722 DESCRIPTION 2723 "Only other (1) needs to be supported." 2725 -- mplsTunnelResourceTable 2727 OBJECT mplsTunnelResourceMaxRate 2728 MIN-ACCESS read-only 2729 DESCRIPTION 2730 "Write access is not required." 2732 OBJECT mplsTunnelResourceMeanRate 2733 MIN-ACCESS read-only 2734 DESCRIPTION 2735 "Write access is not required." 2737 OBJECT mplsTunnelResourceMaxBurstSize 2738 MIN-ACCESS read-only 2739 DESCRIPTION 2740 "Write access is not required." 2742 OBJECT mplsTunnelResourceMeanBurstSize 2743 MIN-ACCESS read-only 2744 DESCRIPTION 2745 "Write access is not required." 2747 OBJECT mplsTunnelResourceExBurstSize 2748 MIN-ACCESS read-only 2749 DESCRIPTION 2750 "Write access is not required." 2752 OBJECT mplsTunnelResourceFrequency 2753 MIN-ACCESS read-only 2754 DESCRIPTION 2755 "Write access is not required." 2757 OBJECT mplsTunnelResourceWeight 2758 MIN-ACCESS read-only 2759 DESCRIPTION 2760 "Write access is not required." 2762 OBJECT mplsTunnelResourceRowStatus 2763 SYNTAX INTEGER { 2764 active(1), 2765 notInService(2), 2766 createAndGo(4), 2767 destroy(6) 2768 } 2769 MIN-ACCESS read-only 2770 DESCRIPTION 2771 "The notReady(3) and createAndWait(5) states need 2772 not be supported. Write access is not required." 2774 OBJECT mplsTunnelResourceStorageType 2775 SYNTAX INTEGER { other(1) } 2776 DESCRIPTION 2777 "Only other (1) needs to be supported." 2779 -- mplsTunnelPerfTable 2781 OBJECT mplsTunnelPerfPackets 2782 MIN-ACCESS read-only 2783 DESCRIPTION 2784 "Write access is not required." 2786 OBJECT mplsTunnelPerfHCPackets 2787 MIN-ACCESS read-only 2788 DESCRIPTION 2789 "Write access is not required." 2791 OBJECT mplsTunnelPerfErrors 2792 MIN-ACCESS read-only 2793 DESCRIPTION 2794 "Write access is not required." 2796 OBJECT mplsTunnelPerfBytes 2797 MIN-ACCESS read-only 2798 DESCRIPTION 2799 "Write access is not required." 2801 OBJECT mplsTunnelPerfHCBytes 2802 MIN-ACCESS read-only 2803 DESCRIPTION 2804 "Write access is not required." 2806 ::= { mplsTeCompliances 1 } 2808 -- Units of conformance. 2810 mplsTunnelGroup OBJECT-GROUP 2811 OBJECTS { 2812 mplsTunnelIndexNext, 2813 mplsTunnelName, 2814 mplsTunnelDescr, 2815 mplsTunnelOwner, 2816 mplsTunnelXCPointer, 2817 mplsTunnelIfIndex, 2818 mplsTunnelHopTableIndex, 2819 mplsTunnelARHopTableIndex, 2820 mplsTunnelCHopTableIndex, 2821 mplsTunnelAdminStatus, 2822 mplsTunnelOperStatus, 2823 mplsTunnelRowStatus, 2824 mplsTunnelNotificationEnable, 2825 mplsTunnelStorageType, 2826 mplsTunnelConfigured, 2827 mplsTunnelActive, 2828 mplsTunnelPrimaryInstance, 2829 mplsTunnelPrimaryTimeUp, 2830 mplsTunnelPathChanges, 2831 mplsTunnelLastPathChange, 2832 mplsTunnelCreationTime, 2833 mplsTunnelStateTransitions, 2834 mplsTunnelIncludeAnyAffinity, 2835 mplsTunnelIncludeAllAffinity, 2836 mplsTunnelExcludeAllAffinity, 2837 mplsTunnelPerfPackets, 2838 mplsTunnelPerfHCPackets, 2839 mplsTunnelPerfErrors, 2840 mplsTunnelPerfBytes, 2841 mplsTunnelPerfHCBytes, 2842 mplsTunnelResourcePointer, 2843 mplsTunnelInstancePriority, 2844 mplsTunnelPathInUse, 2845 mplsTunnelRole, 2846 mplsTunnelTotalUpTime, 2847 mplsTunnelInstanceUpTime 2848 } 2849 STATUS current 2850 DESCRIPTION 2851 "Necessary, but not sufficient, set of objects to 2852 implement tunnels. In addition, depending on the 2853 type of the tunnels supported (for example, 2854 manually configured or signaled, persistent or non- 2855 persistent, etc.), the following other groups 2856 defined below are mandatory: mplsTunnelManualGroup 2857 and/or mplsTunnelSignaledGroup, 2858 mplsTunnelIsNotIntfcGroup and/or 2859 mplsTunnelIsIntfcGroup." 2860 ::= { mplsTeGroups 1 } 2862 mplsTunnelManualGroup OBJECT-GROUP 2863 OBJECTS { mplsTunnelSignallingProto } 2864 STATUS current 2865 DESCRIPTION 2866 "Object(s) needed to implement manually configured 2867 tunnels." 2868 ::= { mplsTeGroups 2 } 2870 mplsTunnelSignaledGroup OBJECT-GROUP 2871 OBJECTS { 2872 mplsTunnelSetupPrio, 2873 mplsTunnelHoldingPrio, 2874 mplsTunnelSignallingProto, 2875 mplsTunnelLocalProtectInUse, 2876 mplsTunnelSessionAttributes, 2877 mplsTunnelHopListIndexNext, 2878 mplsTunnelHopAddrType, 2879 mplsTunnelHopIpAddrType, 2880 mplsTunnelHopIpAddr, 2881 mplsTunnelHopIpPrefixLen, 2882 mplsTunnelHopAsNumber, 2883 mplsTunnelHopLspId, 2884 mplsTunnelHopType, 2885 mplsTunnelHopIncludeExclude, 2886 mplsTunnelHopPathOptionName, 2887 mplsTunnelHopEntryPathComp, 2888 mplsTunnelHopRowStatus, 2889 mplsTunnelHopStorageType 2890 } 2891 STATUS current 2892 DESCRIPTION 2893 "Object needed to implement signaled tunnels." 2894 ::= { mplsTeGroups 3 } 2896 mplsTunnelScalarGroup OBJECT-GROUP 2897 OBJECTS { 2898 mplsTunnelConfigured, 2899 mplsTunnelActive, 2900 mplsTunnelTEDistProto, 2901 mplsTunnelMaxHops, 2902 mplsTunnelNotifMaxRate 2903 } 2904 STATUS current 2905 DESCRIPTION 2906 "Scalar object needed to implement MPLS tunnels." 2907 ::= { mplsTeGroups 4 } 2909 mplsTunnelIsIntfcGroup OBJECT-GROUP 2910 OBJECTS { mplsTunnelIsIf } 2911 STATUS current 2912 DESCRIPTION 2913 "Objects needed to implement tunnels that are 2914 interfaces." 2915 ::= { mplsTeGroups 5 } 2917 mplsTunnelIsNotIntfcGroup OBJECT-GROUP 2918 OBJECTS { mplsTunnelIsIf } 2919 STATUS current 2920 DESCRIPTION 2921 "Objects needed to implement tunnels that are not 2922 interfaces." 2923 ::= { mplsTeGroups 6 } 2925 mplsTunnelOptionalGroup OBJECT-GROUP 2926 OBJECTS { 2927 mplsTunnelResourceIndexNext, 2928 mplsTunnelResourceMaxRate, 2929 mplsTunnelResourceMeanRate, 2930 mplsTunnelResourceMaxBurstSize, 2931 mplsTunnelResourceMeanBurstSize, 2932 mplsTunnelResourceExBurstSize, 2933 mplsTunnelResourceFrequency, 2934 mplsTunnelResourceWeight, 2935 mplsTunnelResourceRowStatus, 2936 mplsTunnelResourceStorageType, 2937 mplsTunnelARHopAddrType, 2938 mplsTunnelARHopIpAddrType, 2939 mplsTunnelARHopIpAddr, 2940 mplsTunnelARHopIpPrefixLen, 2941 mplsTunnelARHopAsNumber, 2942 mplsTunnelARHopLspId, 2943 mplsTunnelCHopAddrType, 2944 mplsTunnelCHopIpAddrType, 2945 mplsTunnelCHopIpAddr, 2946 mplsTunnelCHopIpPrefixLen, 2947 mplsTunnelCHopAsNumber, 2948 mplsTunnelCHopLspId, 2949 mplsTunnelCHopType 2950 } 2951 STATUS current 2952 DESCRIPTION 2953 "The objects in this group are optional." 2954 ::= { mplsTeGroups 7 } 2956 mplsTunnelCRLDPResOptionalGroup OBJECT-GROUP 2957 OBJECTS { 2958 mplsTunnelCRLDPResMeanBurstSize, 2959 mplsTunnelCRLDPResExBurstSize, 2960 mplsTunnelCRLDPResFrequency, 2961 mplsTunnelCRLDPResWeight, 2962 mplsTunnelCRLDPResFlags, 2963 mplsTunnelCRLDPResRowStatus, 2964 mplsTunnelCRLDPResStorageType 2965 } 2966 STATUS current 2967 DESCRIPTION 2968 "Set of objects implemented for resources applicable 2969 for tunnels signaled using CR-LDP." 2970 ::= { mplsTeGroups 8 } 2972 mplsTeNotificationGroup NOTIFICATION-GROUP 2973 NOTIFICATIONS { 2974 mplsTunnelUp, 2975 mplsTunnelDown, 2976 mplsTunnelRerouted, 2977 mplsTunnelReoptimized 2978 } 2979 STATUS current 2980 DESCRIPTION 2981 "Set of notifications implemented in this module. 2982 None is mandatory." 2983 ::= { mplsTeGroups 9 } 2985 END 2987 12. Security Considerations 2989 There are a number of management objects defined in this 2990 MIB that have a MAX-ACCESS clause of read-write and/or 2991 read-create. Such objects may be considered sensitive or 2992 vulnerable in some network environments. The support for 2993 SET operations in a non-secure environment without proper 2994 protection can have a negative effect on network 2995 operations. 2997 It is thus important to control even GET access to these 2998 objects and possibly to even encrypt the values of these 2999 object when sending them over the network via SNMP. Not 3000 all versions of SNMP provide features for such a secure 3001 environment. 3003 SNMPv1 by itself is not a secure environment. Even if the 3004 network itself is secure (for example by using IPSec 3005 [RFC2401]), there is no control as to who on the secure 3006 network is allowed to access and GET/SET 3007 (read/change/create/delete) the objects in this MIB. It is 3008 recommended that the implementers consider the security 3009 features as provided by the SNMPv3 framework. 3010 Specifically, the use of the User-based Security Model 3011 [RFC2574] and the View- based Access Control [RFC2575] is 3012 recommended. It is then a customer/user responsibility to 3013 ensure that the SNMP entity giving access to an instance 3014 of this MIB, is properly configured to give access to the 3015 objects only to those principals (users) that have 3016 legitimate rights to indeed GET or SET 3017 (change/create/delete) them. 3019 13. Acknowledgments 3021 We wish to thank Adrian Farrel, Eric Gray, Joan Cucchiara, 3022 Patrick Kerharo, Paul Langille and Mike Piecuch for their 3023 comments on this draft. 3025 14. References 3027 [Assigned] Reynolds, J., and J. Postel, "Assigned 3028 Numbers", RFC 1700, October 1994. See also: 3029 http://www.isi.edu/in- 3030 notes/iana/assignments/smi-numbers 3032 [TCMIB] Nadeau, T., Cucchiara, J., Srinivasan, C, 3033 Viswanathan, A. and H. Sjostrand, 3034 "Definition of Textual Conventions and 3035 OBJECT-IDENTITIES for Multi-Protocol Label 3036 Switching (MPLS) Management", Internet Draft 3037 , October 3038 2002. 3040 [LSRMIB] Srinivasan, C., Viswanathan, A. and T. 3041 Nadeau, "MPLS Multiprotocol Label Switching 3042 (MPLS) Label Switching Router Management 3043 Information Base ", Internet Draft , October 2002. 3046 [CRLDP] B. Jamoussi (Editor), "Constraint-Based LSP 3047 Setup using LDP", RFC 3212, January 2002. 3049 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 3050 Identification of Management Information for 3051 TCP/IP-based Internets", RFC 1155, May 1990. 3053 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. 3054 Davin, "Simple Network Management Protocol", 3055 RFC 1157, May 1990. 3057 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB 3058 Definitions", RFC 1212, March 1991. 3060 [RFC1215] M. Rose, "A Convention for Defining Traps 3061 for use with the SNMP", RFC 1215, March 3062 1991. 3064 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. 3065 Waldbusser, "Introduction to Community-based 3066 SNMPv2", RFC 1901, January 1996. 3068 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. 3069 Waldbusser, "Protocol Operations for Version 3070 2 of the Simple Network Management Protocol 3071 (SNMPv2)", RFC 1905, January 1996. 3073 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. 3074 Waldbusser, "Transport Mappings for Version 3075 2 of the Simple Network Management Protocol 3076 (SNMPv2)", RFC 1906, January 1996. 3078 [RFC2026] S. Bradner, "The Internet Standards Process 3079 -- Revision 3", RFC 2026, October 1996. 3081 [RFC2401] Kent, S., and Atkinson, R., "Security 3082 Architecture for the Internet Protocol", RFC 3083 2401, November 1998. 3085 [RFC2570] Case, J., Mundy, R., Partain, D., and B. 3086 Stewart, "Introduction to Version 3 of the 3087 Internet-standard Network Management 3088 Framework", RFC 2570, April 1999. 3090 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, 3091 "An Architecture for Describing SNMP 3092 Management Frameworks", RFC 2571, April 3093 1999. 3095 [RFC2572] Case, J., Harrington D., Presuhn R., and B. 3096 Wijnen, "Message Processing and Dispatching 3097 for the Simple Network Management Protocol 3098 (SNMP)", RFC 2572, April 1999. 3100 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 3101 Applications", RFC 2573, April 1999. 3103 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based 3104 Security Model (USM) for version 3 of the 3105 Simple Network Management Protocol 3106 (SNMPv3)", RFC 2574, April 1999. 3108 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, 3109 "View-based Access Control Model (VACM) for 3110 the Simple Network Management Protocol 3111 (SNMP)", RFC 2575, April 1999. 3113 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, 3114 J., Case, J., Rose, M., and S. Waldbusser, 3115 "Structure of Management Information Version 3116 2 (SMIv2)", STD 58, RFC 2578, April 1999. 3118 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, 3119 J., Case, J., Rose, M., and S. Waldbusser, 3120 "Textual Conventions for SMIv2", STD 58, RFC 3121 2579, April 1999. 3123 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, 3124 J., Case, J., Rose, M., and S. Waldbusser, 3125 "Conformance Statements for SMIv2", STD 58, 3126 RFC 2580, April 1999. 3128 [RFC2851] Daniele, M., Haberman, B., Routhier, S., and 3129 J. Schoenwaelder, "Textual Conventions for 3130 Internet Network Addresses", RFC 2851, June 3131 2000. 3133 [RFC2863] McCloghrie, K. and F. Kastenholtz, "The 3134 Interfaces Group MIB ", RFC 2863, June 2000. 3136 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 3137 "Multiprotocol Label Switching 3138 Architecture", RFC 3031, January 2001. 3140 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., 3141 Srinivasan, V., and G. Swallow, "RSVP-TE: 3142 Extensions to RSVP for LSP Tunnels", RFC 3143 3209, December 2001. 3145 15. Authors' Addresses 3147 Cheenu Srinivasan 3148 Parama Networks, Inc. 3149 1030 Broad Street 3150 Shrewsbury, NJ 07702 3151 Phone: +1-732-544-9120 x731 3152 Email: cheenu@paramanet.com 3154 Arun Viswanathan 3155 Force10 Networks, Inc. 3156 1440 McCarthy Blvd 3157 Milpitas, CA 95035 3158 Phone: +1-408-571-3516 3159 Email: arun@force10networks.com 3161 Thomas D. Nadeau 3162 Cisco Systems, Inc. 3163 300 Apollo Drive 3164 Chelmsford, MA 01824 3165 Phone: +1-978-244-3051 3166 Email: tnadeau@cisco.com 3168 16. Full Copyright Statement 3170 Copyright (C) The Internet Society (2001). All Rights 3171 Reserved. 3173 This document and translations of it may be copied and 3174 furnished to others, and derivative works that comment on 3175 or otherwise explain it or assist in its implementation may 3176 be prepared, copied, published and distributed, in whole or 3177 in part, without restriction of any kind, provided that the 3178 above copyright notice and this paragraph are included on 3179 all such copies and derivative works. However, this 3180 document itself may not be modified in any way, such as by 3181 removing the copyright notice or references to the Internet 3182 Society or other Internet organizations, except as needed 3183 for the purpose of developing Internet standards in which 3184 case the procedures for copyrights defined in the Internet 3185 Standards process must be followed, or as required to 3186 translate it into languages other than English. 3188 The limited permissions granted above are perpetual and 3189 will not be revoked by the Internet Society or its 3190 successors or assigns. This document and the information 3191 contained herein is provided on an "AS IS" basis and THE 3192 INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE 3193 DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 3194 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 3195 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 3196 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 3197 PURPOSE.