idnits 2.17.1 draft-ietf-mpls-te-mib-07.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: ---------------------------------------------------------------------------- == There are 2 instances of lines with non-ascii characters in the document. == 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. ** The abstract seems to contain references ([RFC3031]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == 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 796: '...is rsvp(2) this value SHOULD mimic the...' RFC 2119 keyword, line 799: '... value SHOULD mimic the Ingre...' RFC 2119 keyword, line 1196: '...nce represents. This value MUST be set...' RFC 2119 keyword, line 1198: '... This value MUST be set to transi...' RFC 2119 keyword, line 1200: '...rted. This value MUST be set to tail(3...' (3 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 358 has weird spacing: '... tunnel is do...' == Line 671 has weird spacing: '... 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 (August 2001) is 8280 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) == Unused Reference: 'Assigned' is defined on line 2998, but no explicit reference was found in the text == Unused Reference: 'TCMIB' is defined on line 3003, but no explicit reference was found in the text == Unused Reference: 'RFC2702' is defined on line 3105, but no explicit reference was found in the text == Unused Reference: 'RFC2851' is defined on line 3115, 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' -- Possible downref: Non-RFC (?) normative reference: ref. 'RSVPTE' -- Possible downref: Non-RFC (?) normative reference: ref. 'CRLDP' ** 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 2233 (Obsoleted by RFC 2863) ** 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) ** Downref: Normative reference to an Informational RFC: RFC 2702 ** Obsolete normative reference: RFC 2851 (Obsoleted by RFC 3291) Summary: 21 errors (**), 0 flaws (~~), 9 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Cheenu Srinivasan 2 Internet Draft Alphion Corp. 3 Expires: February 2002 4 Arun Viswanathan 5 Force10 Networks, Inc. 7 Thomas D. Nadeau 8 Cisco Systems, Inc. 10 August 2001 12 Multiprotocol Label Switching (MPLS) Traffic Engineering 13 Management Information Base 15 draft-ietf-mpls-te-mib-07.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 21 [RFC2026]. 23 Internet-Drafts are working documents of the Internet 24 Engineering Task Force (IETF), its areas, and its working 25 groups. Note that other groups may also distribute working 26 documents as Internet-Drafts. 28 Internet-Drafts are draft documents valid for a maximum of 29 six months and may be updated, replaced, or obsoleted by 30 other documents at any time. It is inappropriate to use 31 Internet-Drafts as reference material or to cite them other 32 than as "work in progress." 34 The list of current Internet-Drafts can be accessed at 35 http://www.ietf.org/ietf/1id-abstracts.txt. 37 The list of Internet-Draft Shadow Directories can be 38 accessed at http://www.ietf.org/shadow.html. 40 Table of Contents 42 Abstract ................................................ 2 43 1. Introduction ......................................... 2 44 2. Terminology .......................................... 2 45 3. The SNMP Management Framework ........................ 3 46 4. Feature List ......................................... 4 47 5. Outline .............................................. 4 48 5.1. Summary of Traffic Engineering MIB ................ 5 49 6. Brief Description of MIB Objects ..................... 5 50 6.1. mplsTunnelTable ................................... 5 51 6.2. mplsTunnelResourceTable ........................... 6 52 6.3. mplsTunnelHopTable ................................ 6 53 6.4. mplsTunnelARHopTable .............................. 6 54 6.5. mplsTunnelCHoptable ............................... 6 55 6.6. mplsTunnelPerfTable ............................... 6 56 6.7. mplsTunnelCRLDPResTable ........................... 7 57 7. Application of the Interface Group to MPLS Tunnels ... 7 58 7.1. Support of the MPLS Tunnel Interface by ifTable ... 8 59 8. Example of Tunnel Setup .............................. 9 60 9. The Use of RowPointer ............................... 11 61 10. MPLS Traffic Engineering MIB Definitions ........... 11 62 11. Security Considerations ............................ 60 63 12. Acknowledgments .................................... 61 64 13. References ......................................... 61 65 14. Authors' Addresses ................................. 64 66 15. Full Copyright Statement ........................... 64 68 Abstract 70 This memo defines an experimental portion of the Management 71 Information Base (MIB) for use with network management 72 protocols in the Internet community. In particular, it 73 describes managed objects for Multi-Protocol Label 74 Switching (MPLS) [RFC3031] based traffic engineering. 76 1. Introduction 78 This memo defines an experimental portion of the Management 79 Information Base (MIB) for use with network management 80 protocols in the Internet community. In particular, it 81 describes managed objects for modeling a Multi-Protocol 82 Label Switching (MPLS) [RFC3031] based traffic engineering. 83 This MIB should be used in conjunction with the companion 84 document [LSRMIB] for MPLS based traffic engineering 85 configuration and management. 87 Comments should be made directly to the MPLS mailing list 88 at mpls@uu.net. 90 This memo does not, in its draft form, specify a standard 91 for the Internet community. 93 2. Terminology 95 This document uses terminology from the MPLS architecture 96 document [RFC3031] and MPLS Label Switch Router MIB 97 [LSRMIB]. Some frequently used terms are described next. 99 An explicitly routed LSP (ERLSP) is referred to as an MPLS 100 tunnel. It consists of one in-segment and/or one out- 101 segment at the ingress/egress LSRs, each segment being 102 associated with one MPLS interface. These are also 103 referred to as tunnel segments. Additionally, at an 104 intermediate LSR, we model a connection as consisting of 105 one or more in-segments and/or one or more out-segments. 106 The binding or interconnection between in-segments and out- 107 segments in performed using a cross-connect. These objects 108 are defined in the MPLS Label Switch Router MIB [LSRMIB]. 110 3. The SNMP Management Framework 112 The SNMP Management Framework presently consists of five 113 major components: 115 - An overall architecture, described in RFC 2571 116 [RFC2571]. 118 - Mechanisms for describing and naming objects and events 119 for the purpose of management. The first version of 120 this Structure of Management Information (SMI) is 121 called SMIv1 and described in STD 16, RFC 1155 122 [RFC1155], STD 16, RFC 1212 [RFC1212] and STD 16, RFC 123 1215 [RFC1215]. The second version, called SMIv2, is 124 described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 125 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 127 - Message protocols for transferring management 128 information. The first version of the SNMP message 129 protocol is called SNMPv1 and described in STD 15, RFC 130 1157 [RFC1157]. A second version of the SNMP message 131 protocol, which is not an Internet standards track 132 protocol, is called SNMPv2c and described in RFC 1901 133 [RFC1901] and RFC 1906 [RFC1906]. The third version of 134 the message protocol is called SNMPv3 and described in 135 RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 136 [RFC2574]. 138 - Protocol operations for accessing management 139 information. The first set of protocol operations and 140 associated PDU formats is described in STD 15, RFC 1157 141 [RFC1157]. A second set of protocol operations and 142 associated PDU formats is described in RFC 1905 143 [RFC1905]. 145 - A set of fundamental applications described in RFC 2573 146 [RFC2573] and the view-based access control mechanism 147 described in RFC 2575 [RFC2575]. 149 A more detailed introduction to the current SNMP Management 150 Framework can be found in RFC 2570 [RFC2570]. 152 Managed objects are accessed via a virtual information 153 store, termed the Management Information Base or MIB. 154 Objects in the MIB are defined using the mechanisms defined 155 in the SMI. 157 This memo specifies a MIB module that is compliant to the 158 SMIv2. A MIB conforming to the SMIv1 can be produced 159 through the appropriate translations. The resulting 160 translated MIB must be semantically equivalent, except 161 where objects or events are omitted because no translation 162 is possible (use of Counter64). Some machine-readable 163 information in SMIv2 will be converted into textual 164 descriptions in SMIv1 during the translation process. 165 However, this loss of machine-readable information is not 166 considered to change the semantics of the MIB. 168 4. Feature List 170 The MPLS traffic engineering MIB is designed to satisfy the 171 following requirements and constraints. 173 - The MIB supports configuration of point-to-point 174 unidirectional tunnels. 176 - MPLS tunnels need not be interfaces, but it is possible 177 to configure a tunnel as an interface. 179 - The MIB supports manually configured MPLS tunnels as 180 well as those set up via an MPLS signaling protocol. 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 signaling. 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 signaling 274 protocol after the tunnel is setup. The support of this 275 table is optional since not all MPLS signaling protocol may 276 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 287 mplsTunnelPerfTable provides several counters to measure 288 the performance of the MPLS tunnels. This table augments 289 mplsTunnelTable. 291 6.7. mplsTunnelCRLDPResTable 293 mplsTunnelCRLDPResTable contains resource information for 294 those tunnels that are signaled using CRLDP [CRLDP]. This 295 is a sparse extension to mplsTunnelResourceTable and is 296 also indexed by mplsTunnelResourceIndex. As with 297 mplsTunnelResourceTable, multiple tunnels may share the 298 same resources by pointing to the same entry in this table. 299 Tunnels that do not share resources must point to separate 300 entries in this table. 302 7. Application of the Interface Group to MPLS Tunnels 304 The Interfaces Group of MIB II defines generic managed 305 objects for managing interfaces. This memo contains the 306 media-specific extensions to the Interfaces Group for 307 managing MPLS Tunnels as logical interfaces. 309 This memo assumes the interpretation of the Interfaces 310 Group to be in accordance with [RFC2233] which states that 311 the interfaces table (ifTable) contains information on the 312 managed resource's interfaces and that each sub-layer below 313 the internetwork layer of a network interface is considered 314 an interface. Thus, the MPLS interface is represented as 315 an entry in the ifTable. The interrelation of entries in 316 the ifTable is defined by the Interfaces Stack Group 317 defined in [RFC2233]. 319 When using MPLS Tunnels as interfaces, the interface stack 320 table might appear as follows: 322 +------------------------------------------------+ 323 | MPLS tunnel interface ifType = mplsTunnel(150) | 324 +------------------------------------------------+ 325 | MPLS interface ifType = mpls(166) | 326 +------------------------------------------------+ 327 | Underlying layer | 328 +------------------------------------------------+ 330 In the above diagram, "Underlying Layer" refers to the 331 ifIndex of any interface type, which has been defined for 332 MPLS interworking. Examples include ATM, Frame Relay, and 333 Ethernet. 335 7.1. Support of the MPLS Tunnel Interface by ifTable 337 Some specific interpretations of ifTable for those MPLS 338 tunnels represented as interfaces follow: 340 Object Use for the MPLS tunnel. 342 ifIndex Each MPLS tunnel is represented by an 343 ifEntry. 345 ifDescr Description of the MPLS tunnel. 347 ifType The value that is allocated for MPLS 348 tunnel is 150. 350 ifSpeed The total bandwidth in bits per second 351 for use by the MPLS tunnel. 353 ifPhysAddress Unused. 355 ifAdminStatus See [RFC2233]. 357 ifOperStatus Assumes the value down(2) if the MPLS 358 tunnel is down. 360 ifLastChange See [RFC2233]. 362 ifInOctets The number of octets received over the 363 MPLS tunnel. 365 ifOutOctets The number of octets transmitted over 366 the MPLS tunnel. 368 ifInErrors The number of labeled packets dropped 369 due to uncorrectable errors. 371 ifInUnknownProtos The number of received packets 372 discarded during packet header 373 validation, including packets with 374 unrecognized label values. 376 ifOutErrors See [RFC2233]. 378 ifName Textual name (unique on this system) of 379 the MPLS tunnel or an octet string of 380 zero length. 382 ifLinkUpDownTrapEnable 383 Default is disabled (2). 385 ifConnectorPresent Set to false (2). 387 ifHighSpeed See [RFC2233]. 389 ifHCInOctets The 64-bit version of ifInOctets; 390 supported if required by the compliance 391 statements in [RFC2233]. 393 ifHCOutOctets The 64-bit version of ifOutOctets; 394 supported if required by the compliance 395 statements in [RFC2233]. 397 ifAlias The non-volatile 'alias' name for the 398 MPLS tunnel as specified by a network 399 manager. 401 8. Example of Tunnel Setup 403 This section contains an example of which MIB objects 404 should be modified if one would like to create a best 405 effort, loosely routed, unidirectional traffic engineered 406 tunnel, which spans two hops of a simple network. Note 407 that these objects should be created on the "head-end" 408 LSR. 410 In mplsTunnelTable: 411 { 412 mplsTunnelIndex = 1, 413 mplsTunnelInstance = 1, 414 mplsTunnelIngressLSRId = 123.123.125.1, 415 mplsTunnelEgressLSRId = 123.123.126.1, 416 mplsTunnelName = "My first tunnel", 417 mplsTunnelDescr = "Here to there", 418 mplsTunnelIsIf = true (1), 419 mplsTunnelXCPointer = mplsXCIndex.2.0.0.15, 420 mplsTunnelSignallingProto = none (1), 421 mplsTunnelSetupPrio = 0, 422 mplsTunnelHoldingPrio = 0, 423 mplsTunnelSessionAttributes = 0, 424 mplsTunnelOwner = snmp (1), 425 mplsTunnelLocalProtectInUse = false (0), 426 mplsTunnelResourcePointer = mplsTunnelResourceIndex.5, 427 mplsTunnelInstancePriority = 1, 428 mplsTunnelHopTableIndex = 1, 429 mplsTunnelPrimaryInstance = 0, 430 mplsTunnelIncludeAnyAffinity = 0, 431 mplsTunnelIncludeAllAffinity = 0, 432 mplsTunnelExcludeAllAffinity = 0, 433 mplsTunnelPathInUse = 1, 434 mplsTunnelRole = head(1), 435 mplsTunnelRowStatus = createAndGo (4) 436 } 438 In mplsTunnelResourceTable: 439 { 440 mplsTunnelResourceIndex = 5, 441 mplsTunnelResourceMaxRate = 0, 442 mplsTunnelResourceMeanRate = 0, 443 mplsTunnelResourceMaxBurstSize = 0, 444 mplsTunnelResourceRowStatus = createAndGo (4) 445 } 447 The next two instances of mplsTunnelHopEntry are used to 448 denote the hops this tunnel will take across the network. 450 The following denotes the beginning of the network, or the 451 first hop. We have used the fictitious LSR identified by 452 "123.123.125.1" as our example head-end router. 454 In mplsTunnelHopTable: 455 { 456 mplsTunnelHopListIndex = 1, 457 mplsTunnelPathOptionIndex = 1, 458 mplsTunnelHopIndex = 1, 459 mplsTunnelHopAddrType = 1, 460 mplsTunnelHopIpv4Addr = 123.123.125.1, 461 mplsTunnelHopIpv4PrefixLen = 9, 462 mplsTunnelHopType = loose (2), 463 mplsTunnelHopRowStatus = createAndGo (4) 464 } 466 The following denotes the end of the network, or the last 467 hop in our example. We have used the fictitious LSR 468 identified by "123.123.126.1" as our end router. 470 In mplsTunnelHopTable: 471 { 472 mplsTunnelHopListIndex = 1, 473 mplsTunnelPathOptionIndex = 1, 474 mplsTunnelHopIndex = 2, 475 mplsTunnelHopAddrType = 1, 476 mplsTunnelHopIpv4Addr = 123.123.126.1, 477 mplsTunnelHopIpv4PrefixLen = 9, 478 mplsTunnelHopType = loose (2), 479 mplsTunnelHopRowStatus = createAndGo (4) 480 } 482 9. The Use of RowPointer 484 RowPointer is a textual convention used to identify a 485 conceptual row in an SNMP Table by pointing to one of its 486 objects. In this MIB, in mplsTunnelTable, the objects 487 mplsTunnelXCPointer and mplsTunnelResourcePointer are of 488 type RowPointer. The object mplsTunnelXCPointer points to 489 a specific entry in the mplsXCTable [LSRMIB]. This entry 490 in the mplsXCTable is the associated LSP for the given MPLS 491 tunnel entry. The object mplsTunnelResourcePointer points 492 to a specific entry in a traffic parameter table. An 493 example of such a traffic parameter table is 494 mplsTunnelResourceTable. It indicates a specific instance 495 of a traffic parameter entry that is associated with a 496 given MPLS tunnel entry. 498 10. MPLS Traffic Engineering MIB Definitions 500 MPLS-TE-MIB DEFINITIONS ::= BEGIN 502 IMPORTS 503 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 504 experimental, Integer32, Unsigned32, Counter32, 505 Counter64, TimeTicks 506 FROM SNMPv2-SMI 507 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 508 FROM SNMPv2-CONF 509 TEXTUAL-CONVENTION, TruthValue, RowStatus, RowPointer, 510 StorageType, DisplayString, TimeStamp 511 FROM SNMPv2-TC 512 InterfaceIndexOrZero 513 FROM IF-MIB 514 MplsBitRate, MplsBurstSize, MplsLSPID, 515 MplsTunnelIndex, MplsTunnelInstanceIndex, 516 MplsTunnelAffinity, MplsLsrIdentifier, MplsPathIndex, 517 MplsPathIndexOrZero 518 FROM MPLS-TC-MIB 519 InetAddressIPv4, InetAddressIPv6 520 FROM INET-ADDRESS-MIB 521 ; 523 mplsTeMIB MODULE-IDENTITY 524 LAST-UPDATED 525 "200108241200Z" -- August 24, 2001 12:00:00 GMT 526 ORGANIZATION 527 "Multiprotocol Label Switching (MPLS) Working Group" 528 CONTACT-INFO 529 " 530 Cheenu Srinivasan 531 Postal: Alphion Corp. 532 4 Industrial Way West 533 Eatontown, NJ 07724 534 Tel: +1-732-676-7066 535 Email: cheenu@alphion.com 537 Arun Viswanathan 538 Postal: Force10 Networks, Inc. 539 1440 McCarthy Blvd 540 Milpitas, CA 95035 541 Tel: +1-408-571-3516 542 Email: arun@force10networks.com 544 Thomas D. Nadeau 545 Postal: Cisco Systems, Inc. 546 250 Apollo Drive 547 Chelmsford, MA 01824 548 Tel: +1-978-244-3051 549 Email: tnadeau@cisco.com 551 " 552 DESCRIPTION 553 "This MIB module contains managed object definitions 554 for MPLS Traffic Engineering (TE) as defined in: 555 1. Extensions to RSVP for LSP Tunnels, Awduche et 556 al, Internet Draft , February 2001 558 2. Constraint-Based LSP Setup using LDP, B. Jamoussi 559 (Editor), Internet Draft , February 2001 561 3. Requirements for Traffic Engineering Over MPLS, 562 Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., 563 and J. McManus, RFC 2702, September 1999" 565 -- Revision history. 567 REVISION 568 "200108241200Z" -- 24 August 2001 12:00:00 GMT 569 DESCRIPTION 570 "Removed SMIv2 from title. Upgraded SNMP boilerplate. 571 Updated references to reflect this change. Removed 572 TCs; Updated IMPORTS clause to import them from 573 MPLS TC MIB. Updated author contact information. 574 Introduced a TOC." 575 REVISION 576 "200103021200Z" -- 2 March 2001 12:00:00 GMT 577 DESCRIPTION 578 "Updates based on MPLS WG last call feedback." 579 REVISION 580 "200011211200Z" -- 21 November 2000 12:00:00 GMT 581 DESCRIPTION 582 "Updates based on MPLS WG feedback." 583 REVISION 584 "200007141200Z" -- 14 July 2000 12:00:00 GMT 585 DESCRIPTION 586 "Updates based on MPLS WG feedback." 587 REVISION 588 "200005261200Z" -- 26 May 2000 12:00:00 GMT 589 DESCRIPTION 590 "Updates based on MPLS WG feedback." 591 REVISION 592 "200003031200Z" -- 3 March 2000 12:00:00 GMT 593 DESCRIPTION 594 "Updates based on MPLS WG feedback." 595 REVISION 596 "199907161200Z" -- 16 July 1999 12:00:00 GMT 597 DESCRIPTION 598 "Initial draft version." 600 ::= { experimental 95 } 602 -- Top level components of this MIB. 604 -- tables, scalars 605 mplsTeScalars OBJECT IDENTIFIER ::= { mplsTeMIB 1 } 606 mplsTeObjects OBJECT IDENTIFIER ::= { mplsTeMIB 2 } 608 -- traps 609 mplsTeNotifications OBJECT IDENTIFIER ::= { mplsTeMIB 3 } 610 mplsTeNotifyPrefix OBJECT IDENTIFIER ::= { mplsTeNotifications 0 } 612 -- conformance 613 mplsTeConformance OBJECT IDENTIFIER ::= { mplsTeMIB 4 } 615 -- MPLS Tunnel scalars. 617 mplsTunnelConfigured OBJECT-TYPE 618 SYNTAX Unsigned32 619 MAX-ACCESS read-only 620 STATUS current 621 DESCRIPTION 622 "The number of tunnels configured on this device. A 623 tunnel is considered configured if the 624 mplsTunnelRowStatus is active(1)." 625 ::= { mplsTeScalars 1 } 627 mplsTunnelActive OBJECT-TYPE 628 SYNTAX Unsigned32 629 MAX-ACCESS read-only 630 STATUS current 631 DESCRIPTION 632 "The number of tunnels active on this device. A 633 tunnel is considered active if the 634 mplsTunnelOperStatus is up(1)." 635 ::= { mplsTeScalars 2 } 637 mplsTunnelTEDistProto OBJECT-TYPE 638 SYNTAX BITS { 639 other (0), 640 ospf (1), 641 isis (2) 642 } 643 MAX-ACCESS read-only 644 STATUS current 645 DESCRIPTION 646 "The traffic engineering distribution protocol(s) 647 used by this LSR. Note that an LSR may support more 648 than one distribution protocol simultaneously." 649 ::= { mplsTeScalars 3 } 651 mplsTunnelMaxHops OBJECT-TYPE 652 SYNTAX Unsigned32 653 MAX-ACCESS read-only 654 STATUS current 655 DESCRIPTION 656 "The maximum number of hops that can be specified for 657 a tunnel on this device." 658 ::= { mplsTeScalars 4 } 660 -- End of MPLS Tunnel scalars. 662 -- MPLS tunnel table. 664 mplsTunnelIndexNext OBJECT-TYPE 665 SYNTAX Integer32 (0..65535) 666 MAX-ACCESS read-only 667 STATUS current 668 DESCRIPTION 669 "This object contains the next appropriate value to 670 be used for mplsTunnelIndex when creating entries 671 in mplsTunnelTable. If the number of unassigned 672 entries is exhausted, a retrival operation will 673 return a value of 0. This object may also return a 674 value of 0 when the LSR is unable to accept 675 conceptual row creation, for example, if the 676 mplsTunnelTable is implemented as read-only. To 677 obtain the value of mplsTunnelIndex for a new 678 entry, the manager must first issue a management 679 protocol retrieval operation to obtain the current 680 value of this object. The agent should modify the 681 value to reflect the next unassigned index after 682 each retrieval operation. After a manager retrieves 683 a value the agent will determine through its local 684 policy when this index value will be made available 685 for reuse." 686 ::= { mplsTeObjects 1 } 688 mplsTunnelTable OBJECT-TYPE 689 SYNTAX SEQUENCE OF MplsTunnelEntry 690 MAX-ACCESS not-accessible 691 STATUS current 692 DESCRIPTION 693 "The mplsTunnelTable allows new MPLS tunnels to be 694 created between an LSR and a remote endpoint, and 695 existing tunnels to be reconfigured or removed. 696 Note that only point-to-point tunnel segments are 697 supported, although multi-point-to-point and point- 698 to-multi-point connections are supported by an LSR 699 acting as a cross-connect. Each MPLS tunnel can 700 thus have one out-segment originating at this LSR 701 and/or one in-segment terminating at this LSR." 702 ::= { mplsTeObjects 2 } 704 mplsTunnelEntry OBJECT-TYPE 705 SYNTAX MplsTunnelEntry 706 MAX-ACCESS not-accessible 707 STATUS current 708 DESCRIPTION 709 "An entry in this table represents an MPLS tunnel. 710 An entry can be created by a network administrator 711 or by an SNMP agent as instructed by an MPLS 712 signaling protocol. Whenever a new entry is created 713 with mplsTunnelIsIf set to true(1), then a 714 corresponding entry is created in ifTable as well 715 (see RFC 2233). The ifType of this entry is 716 mplsTunnel(150)." 717 REFERENCE 718 "1. RFC 2233 - The Interfaces Group MIB using SMIv2, 719 McCloghrie, K., and F. Kastenholtz, Nov. 1997 720 2. RFC 1700 - Assigned Numbers, Reynolds, J. and J. 721 Postel, Oct. 1994" 722 INDEX { 723 mplsTunnelIndex, 724 mplsTunnelInstance, 725 mplsTunnelIngressLSRId, 726 mplsTunnelEgressLSRId 727 } 728 ::= { mplsTunnelTable 1 } 730 MplsTunnelEntry ::= SEQUENCE { 731 mplsTunnelIndex MplsTunnelIndex, 732 mplsTunnelInstance MplsTunnelInstanceIndex, 733 mplsTunnelIngressLSRId MplsLsrIdentifier, 734 mplsTunnelEgressLSRId MplsLsrIdentifier, 735 mplsTunnelName DisplayString, 736 mplsTunnelDescr DisplayString, 737 mplsTunnelIsIf TruthValue, 738 mplsTunnelIfIndex InterfaceIndexOrZero, 739 mplsTunnelXCPointer RowPointer, 740 mplsTunnelSignallingProto INTEGER, 741 mplsTunnelSetupPrio INTEGER, 742 mplsTunnelHoldingPrio INTEGER, 743 mplsTunnelSessionAttributes BITS, 744 mplsTunnelOwner INTEGER, 745 mplsTunnelLocalProtectInUse TruthValue, 746 mplsTunnelResourcePointer RowPointer, 747 mplsTunnelInstancePriority Unsigned32, 748 mplsTunnelHopTableIndex MplsPathIndexOrZero, 749 mplsTunnelARHopTableIndex MplsPathIndexOrZero, 750 mplsTunnelCHopTableIndex MplsPathIndexOrZero, 751 mplsTunnelPrimaryInstance MplsTunnelInstanceIndex, 752 mplsTunnelPrimaryTimeUp TimeTicks, 753 mplsTunnelPathChanges Counter32, 754 mplsTunnelLastPathChange TimeTicks, 755 mplsTunnelCreationTime TimeStamp, 756 mplsTunnelStateTransitions Counter32, 757 mplsTunnelIncludeAnyAffinity MplsTunnelAffinity, 758 mplsTunnelIncludeAllAffinity MplsTunnelAffinity, 759 mplsTunnelExcludeAllAffinity MplsTunnelAffinity, 760 mplsTunnelPathInUse MplsPathIndexOrZero, 761 mplsTunnelRole INTEGER, 762 mplsTunnelTotalUpTime TimeTicks, 763 mplsTunnelInstanceUpTime TimeTicks, 764 mplsTunnelAdminStatus INTEGER, 765 mplsTunnelOperStatus INTEGER, 766 mplsTunnelRowStatus RowStatus, 767 mplsTunnelStorageType StorageType 768 } 770 mplsTunnelIndex OBJECT-TYPE 771 SYNTAX MplsTunnelIndex 772 MAX-ACCESS accessible-for-notify 773 STATUS current 774 DESCRIPTION 775 "Uniquely identifies this row." 777 ::= { mplsTunnelEntry 1 } 779 mplsTunnelInstance OBJECT-TYPE 780 SYNTAX MplsTunnelInstanceIndex 781 MAX-ACCESS accessible-for-notify 782 STATUS current 783 DESCRIPTION 784 "Uniquely identifies an instance of a tunnel. It is 785 useful to identify multiple instances of tunnels 786 for the purposes of backup and parallel tunnels." 787 ::= { mplsTunnelEntry 2 } 789 mplsTunnelIngressLSRId OBJECT-TYPE 790 SYNTAX MplsLsrIdentifier 791 MAX-ACCESS accessible-for-notify 792 STATUS current 793 DESCRIPTION 794 "The purpose of this object is to uniquely identity a 795 tunnel within a network. When the MPLS signalling 796 protoocol is rsvp(2) this value SHOULD mimic the 797 Extended Tunnel Id field in the SESSION object. 798 When the MPLS signalling protoocol is crldp(3) this 799 value SHOULD mimic the Ingress LSR Router ID field 800 in the LSPID TLV object." 801 REFERENCE 802 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 803 Awduche et al, Internet Draft , February 2001., 805 2. Constraint-Based LSP Setup using LDP, Jamoussi, 806 Internet Draft , 807 February 2001." 808 ::= { mplsTunnelEntry 3 } 810 mplsTunnelEgressLSRId OBJECT-TYPE 811 SYNTAX MplsLsrIdentifier 812 MAX-ACCESS accessible-for-notify 813 STATUS current 814 DESCRIPTION 815 "Specifies the egress LSR ID." 816 ::= { mplsTunnelEntry 4 } 818 mplsTunnelName OBJECT-TYPE 819 SYNTAX DisplayString 820 MAX-ACCESS read-create 821 STATUS current 822 DESCRIPTION 823 "The canonical name assigned to the tunnel. This name 824 can be used to refer to the tunnel on the LSR�s 825 console port. If mplsTunnelIsIf is set to true 826 then the ifName of the interface corresponding to 827 this tunnel should have a value equal to 828 mplsTunnelName. Also see the description of ifName 829 in RFC 2233." 830 REFERENCE 831 "RFC 2233 - The Interfaces Group MIB using SMIv2, 832 McCloghrie, K., and F. Kastenholtz, Nov. 1997" 833 ::= { mplsTunnelEntry 5 } 835 mplsTunnelDescr OBJECT-TYPE 836 SYNTAX DisplayString 837 MAX-ACCESS read-create 838 STATUS current 839 DESCRIPTION 840 "A textual string containing information about the 841 tunnel. If there is no description this object 842 contains a zero length string." 843 ::= { mplsTunnelEntry 6 } 845 mplsTunnelIsIf OBJECT-TYPE 846 SYNTAX TruthValue 847 MAX-ACCESS read-create 848 STATUS current 849 DESCRIPTION 850 "Denotes whether or not this tunnel corresponds to an 851 interface represented in the interfaces group 852 table. Note that if this variable 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 2233." 857 REFERENCE 858 "RFC 2233 - The Interfaces Group MIB using SMIv2, 859 McCloghrie, K., and F. Kastenholtz, Nov. 1997" 860 DEFVAL { false } 861 ::= { mplsTunnelEntry 7 } 863 mplsTunnelIfIndex OBJECT-TYPE 864 SYNTAX InterfaceIndexOrZero 865 MAX-ACCESS read-only 866 STATUS current 867 DESCRIPTION 868 "If mplsTunnelIsIf is set to true, then this value 869 contains the LSR-assigned ifIndex which corresponds 870 to an entry in the interfaces table. Otherwise 871 this variable should contain the value of zero 872 indicating that a valid ifIndex was not assigned to 873 this tunnel interface." 874 REFERENCE 875 "RFC 2233 - The Interfaces Group MIB using SMIv2, 876 McCloghrie, K., and F. Kastenholtz, Nov. 1997" 878 ::= { mplsTunnelEntry 8 } 880 mplsTunnelXCPointer OBJECT-TYPE 881 SYNTAX RowPointer 882 MAX-ACCESS read-create 883 STATUS current 884 DESCRIPTION 885 "This variable points to a row in the mplsXCTable. 886 This table identifies the segments that compose 887 this tunnel, their characteristics, and 888 relationships to each other. A value of zeroDotZero 889 indicates that no LSP has been associated with this 890 tunnel yet." 891 REFERENCE 892 "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS 893 Label Switch Router Management Information Base 894 Using SMIv2, Internet Draft , July 2000." 896 ::= { mplsTunnelEntry 9 } 898 mplsTunnelSignallingProto OBJECT-TYPE 899 SYNTAX INTEGER { 900 none(1), 901 rsvp(2), 902 crldp(3), 903 other(4) 904 } 905 MAX-ACCESS read-create 906 STATUS current 907 DESCRIPTION 908 "The signaling protocol, if any, which was used to 909 setup this tunnel." 910 DEFVAL { none } 911 ::= { mplsTunnelEntry 10 } 913 mplsTunnelSetupPrio OBJECT-TYPE 914 SYNTAX INTEGER (0..7) 915 MAX-ACCESS read-create 916 STATUS current 917 DESCRIPTION 918 "Indicates the setup priority of this tunnel." 919 REFERENCE 920 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 921 Awduche et al, Internet Draft , August 2000., 923 2. Constraint-Based LSP Setup using LDP, Jamoussi, 924 Internet Draft , 925 July 2000." 926 ::= { mplsTunnelEntry 11 } 928 mplsTunnelHoldingPrio OBJECT-TYPE 929 SYNTAX INTEGER (0..7) 930 MAX-ACCESS read-create 931 STATUS current 932 DESCRIPTION 933 "Indicates the holding priority for this tunnel." 934 REFERENCE 935 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 936 Awduche et al, Internet Draft , August 2000., 938 2. Constraint-Based LSP Setup using LDP, Jamoussi, 939 Internet Draft , 940 July 2000." 941 ::= { mplsTunnelEntry 12 } 943 mplsTunnelSessionAttributes OBJECT-TYPE 944 SYNTAX BITS { 945 fastReroute (0), 946 mergingPermitted (1), 947 isPersistent (2), 948 isPinned (3), 949 recordRoute(4) 950 } 951 MAX-ACCESS read-create 952 STATUS current 953 DESCRIPTION 954 "This bitmask indicates optional session values for 955 this tunnel. The following describes these 956 bitfields: 958 fastRerouteThis flag indicates that the any tunnel 959 hop may choose to reroute this tunnel without 960 tearing it down. This flag permits transit routers 961 to use a local repair mechanism which may result in 962 violation of the explicit routing of this tunnel. 963 When a fault is detected on an adjacent downstream 964 link or node, a transit router can reroute traffic 965 for fast service restoration. 967 mergingPermitted This flag permits transit routers 968 to merge this session with other RSVP sessions for 969 the purpose of reducing resource overhead on 970 downstream transit routers, thereby providing 971 better network scalability. 973 isPersistent Indicates whether this tunnel should 974 be restored automatically after a failure occurs. 976 isPinned This flag indicates whether the loose- 977 routed hops of this tunnel are to be pinned. 979 recordRouteThis flag indicates whether or not the 980 signaling protocol should remember the tunnel path 981 after it has been signaled." 983 REFERENCE 984 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 985 Awduche et al, Internet Draft , August 2000." 987 DEFVAL { 0 } 988 ::= { mplsTunnelEntry 13 } 990 mplsTunnelOwner OBJECT-TYPE 991 SYNTAX INTEGER { 992 admin(1), -- represents all management entities 993 rsvp(2), 994 crldp(3), 995 policyAgent(4), 996 other(5) 997 } 998 MAX-ACCESS read-create 999 STATUS current 1000 DESCRIPTION 1001 "Indicates which protocol created and is responsible 1002 for managing this tunnel. Values rsvp(2) and 1003 crldp(3) should not be used at the head-end of a 1004 MPLS tunnel." 1005 ::= { mplsTunnelEntry 14 } 1007 mplsTunnelLocalProtectInUse OBJECT-TYPE 1008 SYNTAX TruthValue 1009 MAX-ACCESS read-create 1010 STATUS current 1011 DESCRIPTION 1012 "Indicates that the local repair mechanism is in use 1013 to maintain this tunnel (usually in the face of an 1014 outage of the link it was previously routed over)." 1015 ::= { mplsTunnelEntry 15 } 1017 mplsTunnelResourcePointer OBJECT-TYPE 1018 SYNTAX RowPointer 1019 MAX-ACCESS read-create 1020 STATUS current 1021 DESCRIPTION 1022 "This variable represents a pointer to the traffic 1023 parameter specification for this tunnel. This 1024 value may point at an entry in the 1025 mplsTunnelResourceEntry to indicate which 1026 mplsTunnelResourceEntry is to be assigned to this 1027 segment. This value may optionally point at an 1028 externally defined traffic parameter specification 1029 table. A value of zeroDotZero indicates best- 1030 effort treatment. By having the same value of this 1031 object, two or more segments can indicate resource 1032 sharing." 1033 ::= { mplsTunnelEntry 16 } 1035 mplsTunnelInstancePriority OBJECT-TYPE 1036 SYNTAX Unsigned32 1037 MAX-ACCESS read-create 1038 STATUS current 1039 DESCRIPTION 1040 "This value indicates which priority, in descending 1041 order, with 0 indicating the lowest priority, 1042 within a group of tunnel instances. A group of 1043 tunnel instances is defined as a set of tunnels 1044 with the same mplsTunnelIndex in this table, but 1045 with a different mplsTunnelInstance. Tunnel group 1046 priorities are used to denote the priority at which 1047 a particular tunnel instance will supercede 1048 another. Instances of tunnels containing the same 1049 mplsTunnelInstancePriority will be used for load 1050 sharing." 1051 DEFVAL { 0 } 1052 ::= { mplsTunnelEntry 17 } 1054 mplsTunnelHopTableIndex OBJECT-TYPE 1055 SYNTAX MplsPathIndexOrZero 1056 MAX-ACCESS read-create 1057 STATUS current 1058 DESCRIPTION 1059 "Index into the mplsTunnelHopTable entry that 1060 specifies the explicit route hops for this tunnel." 1061 ::= { mplsTunnelEntry 18 } 1063 mplsTunnelARHopTableIndex OBJECT-TYPE 1064 SYNTAX MplsPathIndexOrZero 1065 MAX-ACCESS read-only 1066 STATUS current 1067 DESCRIPTION 1068 "Index into the mplsTunnelARHopTable entry that 1069 specifies the actual hops traversed by the tunnel." 1070 ::= { mplsTunnelEntry 19 } 1072 mplsTunnelCHopTableIndex OBJECT-TYPE 1073 SYNTAX MplsPathIndexOrZero 1074 MAX-ACCESS read-only 1075 STATUS current 1076 DESCRIPTION 1077 "Index into the mplsTunnelCHopTable entry that 1078 specifies the computed hops traversed by the 1079 tunnel." 1080 ::= { mplsTunnelEntry 20 } 1082 mplsTunnelPrimaryInstance OBJECT-TYPE 1083 SYNTAX MplsTunnelInstanceIndex 1084 MAX-ACCESS read-only 1085 STATUS current 1086 DESCRIPTION 1087 "Specifies the instance index of the primary instance 1088 of this tunnel." 1089 ::= { mplsTunnelEntry 21 } 1091 mplsTunnelPrimaryTimeUp OBJECT-TYPE 1092 SYNTAX TimeTicks 1093 MAX-ACCESS read-only 1094 STATUS current 1095 DESCRIPTION 1096 "Specifies the total time the primary instance of 1097 this tunnel has been active. The primary instance 1098 of this tunnel is defined in 1099 mplsTunnelPrimaryInstance." 1100 ::= { mplsTunnelEntry 22 } 1102 mplsTunnelPathChanges OBJECT-TYPE 1103 SYNTAX Counter32 1104 MAX-ACCESS read-only 1105 STATUS current 1106 DESCRIPTION 1107 "Specifies the number of times the paths has changed 1108 for this tunnel." 1109 ::= { mplsTunnelEntry 23 } 1111 mplsTunnelLastPathChange OBJECT-TYPE 1112 SYNTAX TimeTicks 1113 MAX-ACCESS read-only 1114 STATUS current 1115 DESCRIPTION 1116 "Specifies the time since the last path change for 1117 this tunnel." 1118 ::= { mplsTunnelEntry 24 } 1120 mplsTunnelCreationTime OBJECT-TYPE 1121 SYNTAX TimeStamp 1122 MAX-ACCESS read-only 1123 STATUS current 1124 DESCRIPTION 1125 "Specifies the value of SysUpTime when the first 1126 instance of this tunnel came into existence." 1127 ::= { mplsTunnelEntry 25 } 1129 mplsTunnelStateTransitions OBJECT-TYPE 1130 SYNTAX Counter32 1131 MAX-ACCESS read-only 1132 STATUS current 1133 DESCRIPTION 1134 "Specifies the number of times the state of this 1135 tunnel instance has changed." 1136 ::= { mplsTunnelEntry 26 } 1138 mplsTunnelIncludeAnyAffinity OBJECT-TYPE 1139 SYNTAX MplsTunnelAffinity 1140 MAX-ACCESS read-create 1141 STATUS current 1142 DESCRIPTION 1143 "A link satisfies the include-any constraint if and 1144 only if the constraint is zero, or the link and the 1145 constraint have a resource class in common." 1146 REFERENCE "RSVP-TE: Extensions to RSVP for LSP 1147 Tunnels, 1148 draft-ietf-mpls-rsvp-lsp-tunnel-07.txt" 1149 ::= { mplsTunnelEntry 27 } 1151 mplsTunnelIncludeAllAffinity OBJECT-TYPE 1152 SYNTAX MplsTunnelAffinity 1153 MAX-ACCESS read-create 1154 STATUS current 1155 DESCRIPTION 1156 "A link satisfies the include-all constraint if and 1157 only if the link contains all of the adminstrative 1158 groups specified in the constraint." 1159 REFERENCE "RSVP-TE: Extensions to RSVP for LSP 1160 Tunnels, draft-ietf-mpls-rsvp-lsp-tunnel-07.txt" 1161 ::= { mplsTunnelEntry 28 } 1163 mplsTunnelExcludeAllAffinity OBJECT-TYPE 1164 SYNTAX MplsTunnelAffinity 1165 MAX-ACCESS read-create 1166 STATUS current 1167 DESCRIPTION 1168 "A link satisfies the exclude-all constraint if and 1169 only if the link contains none of the adminstrative 1170 groups specifie in the constraint." 1171 REFERENCE "RSVP-TE: Extensions to RSVP for LSP 1172 Tunnels, draft-ietf-mpls-rsvp-lsp-tunnel-07.txt" 1173 ::= { mplsTunnelEntry 29 } 1175 mplsTunnelPathInUse OBJECT-TYPE 1176 SYNTAX MplsPathIndexOrZero 1177 MAX-ACCESS read-create 1178 STATUS current 1179 DESCRIPTION 1180 "This value denotes the configured path that was 1181 chosen for this tunnel. This value reflects the 1182 secondary index into the TunnelHopTable. This path 1183 may not exactly match the one in the ARHopTable due 1184 to the fact that some CSPF modification may have 1185 taken place. See the ARHopTable for the actual path 1186 being taken by the tunnel. A value of zero denotes 1187 that no path is currently in use or available." 1188 ::= { mplsTunnelEntry 30 } 1190 mplsTunnelRole OBJECT-TYPE 1191 SYNTAX INTEGER { head(1), transit(2), tail(3) } 1192 MAX-ACCESS read-create 1193 STATUS current 1194 DESCRIPTION 1195 "This value signifies the role that this tunnel 1196 entry/instance represents. This value MUST be set 1197 to head(1) at the originating point of the tunnel. 1198 This value MUST be set to transit(2) at transit 1199 points along the tunnel, if transit points are 1200 supported. This value MUST be set to tail(3) at the 1201 terminating point of the tunnel if tunnel tails are 1202 supported." 1203 ::= { mplsTunnelEntry 31 } 1205 mplsTunnelTotalUpTime OBJECT-TYPE 1206 SYNTAX TimeTicks 1207 MAX-ACCESS read-create 1208 STATUS current 1209 DESCRIPTION 1210 "This value represents the aggregate up time for all 1211 instances of this tunnel, if available. If this 1212 value is unavailable, it MUST return a value of 0." 1213 ::= { mplsTunnelEntry 32 } 1215 mplsTunnelInstanceUpTime OBJECT-TYPE 1216 SYNTAX TimeTicks 1217 MAX-ACCESS read-create 1218 STATUS current 1219 DESCRIPTION 1220 "This value identifies the total time that this 1221 tunnel instance's operStatus has been Up(1)." 1222 ::= { mplsTunnelEntry 33 } 1224 mplsTunnelAdminStatus OBJECT-TYPE 1225 SYNTAX INTEGER { 1226 -- ready to pass packets 1227 up(1), 1228 down(2), 1229 -- in some test mode 1230 testing(3) 1231 } 1232 MAX-ACCESS read-create 1233 STATUS current 1234 DESCRIPTION 1235 "Indicates the desired operational status of this 1236 tunnel." 1237 ::= { mplsTunnelEntry 34 } 1239 mplsTunnelOperStatus OBJECT-TYPE 1240 SYNTAX INTEGER { 1241 -- ready to pass packets 1242 up(1), 1243 down(2), 1244 -- in some test mode 1245 testing(3), 1246 -- status cannot be determined 1247 unknown(4), 1248 dormant(5), 1249 -- some component is missing 1250 notPresent(6), 1251 -- down due to the state of 1252 -- lower layer interfaces 1253 lowerLayerDown(7) 1254 } 1255 MAX-ACCESS read-only 1256 STATUS current 1257 DESCRIPTION 1258 "Indicates the actual operational status of this 1259 tunnel, which is typically but not limited to, a 1260 function of the state of individual segments of 1261 this tunnel." 1262 ::= { mplsTunnelEntry 35 } 1264 mplsTunnelRowStatus OBJECT-TYPE 1265 SYNTAX RowStatus 1266 MAX-ACCESS read-create 1267 STATUS current 1268 DESCRIPTION 1269 "This variable is used to create, modify, and/or 1270 delete a row in this table." 1271 ::= { mplsTunnelEntry 36 } 1273 mplsTunnelStorageType OBJECT-TYPE 1274 SYNTAX StorageType 1275 MAX-ACCESS read-create 1276 STATUS current 1277 DESCRIPTION 1278 "This variable indicates the storage type for this 1279 object." 1280 ::= { mplsTunnelEntry 37 } 1282 -- End of mplsTunnelTable 1284 mplsTunnelHopListIndexNext OBJECT-TYPE 1285 SYNTAX Unsigned32 (0..2147483647) 1286 MAX-ACCESS read-only 1287 STATUS current 1288 DESCRIPTION 1289 "This object contains an appropriate value to be used 1290 for mplsTunnelHopListIndex when creating entries in 1291 the mplsTunnelHopTable. If the number of 1292 unassigned entries is exhausted, a retrival 1293 operation will return a value of 0. This object 1294 may also return a value of 0 when the LSR is unable 1295 to accept conceptual row creation, for example, if 1296 the mplsTunnelHopTable is implemented as read-only. 1297 To obtain the value of mplsTunnelHopListIndex for a 1298 new entry in the mplsTunnelHopTable, the manager 1299 issues a management protocol retrieval operation to 1300 obtain the current value of mplsTunnelHopIndex. 1301 After each retrieval operation, the agent should 1302 modify the value to reflect the next unassigned 1303 index. After a manager retrieves a value the agent 1304 will determine through its local policy when this 1305 index value will be made available for reuse." 1306 ::= { mplsTeObjects 3 } 1308 mplsTunnelHopTable OBJECT-TYPE 1309 SYNTAX SEQUENCE OF MplsTunnelHopEntry 1310 MAX-ACCESS not-accessible 1311 STATUS current 1312 DESCRIPTION 1313 "The mplsTunnelHopTable is used to indicate the hops, 1314 strict or loose, for an MPLS tunnel defined in 1315 mplsTunnelTable, when it is established via 1316 signaling, for the outgoing direction of the 1317 tunnel. Each row in this table is indexed by 1318 mplsTunnelHopListIndex. Each row also has a 1319 secondary index mplsTunnelHopIndex corresponding to 1320 the next hop that this row corresponds to. The 1321 first row in the table is the first hop after the 1322 origination point of the tunnel. In case we want 1323 to specify a particular interface on the 1324 originating LSR of an outgoing tunnel by which we 1325 want packets to exit the LSR, we specify this as 1326 the first hop for this tunnel in 1327 mplsTunnelHopTable." 1328 ::= { mplsTeObjects 4 } 1330 mplsTunnelHopEntry OBJECT-TYPE 1331 SYNTAX MplsTunnelHopEntry 1332 MAX-ACCESS not-accessible 1333 STATUS current 1334 DESCRIPTION 1335 "An entry in this table represents a tunnel hop. An 1336 entry is created by a network administrator for 1337 signaled ERLSP set up by an MPLS signaling 1338 protocol." 1339 INDEX { 1340 mplsTunnelHopListIndex, 1341 mplsTunnelHopPathOptionIndex, 1342 mplsTunnelHopIndex 1343 } 1344 ::= { mplsTunnelHopTable 1 } 1346 MplsTunnelHopEntry ::= SEQUENCE { 1347 mplsTunnelHopListIndex MplsPathIndex, 1348 mplsTunnelHopPathOptionIndex MplsPathIndex, 1349 mplsTunnelHopIndex MplsPathIndex, 1350 mplsTunnelHopAddrType INTEGER, 1351 mplsTunnelHopIpv4Addr InetAddressIPv4, 1352 mplsTunnelHopIpv4PrefixLen Unsigned32, 1353 mplsTunnelHopIpv6Addr InetAddressIPv6, 1354 mplsTunnelHopIpv6PrefixLen Unsigned32, 1355 mplsTunnelHopAsNumber Unsigned32, 1356 mplsTunnelHopLspId MplsLSPID, 1357 mplsTunnelHopType INTEGER, 1358 mplsTunnelHopIncludeExclude INTEGER, 1359 mplsTunnelHopPathOptionName DisplayString, 1360 mplsTunnelHopEntryPathComp INTEGER, 1361 mplsTunnelHopRowStatus RowStatus, 1362 mplsTunnelHopStorageType StorageType 1363 } 1365 mplsTunnelHopListIndex OBJECT-TYPE 1366 SYNTAX MplsPathIndex 1367 MAX-ACCESS not-accessible 1368 STATUS current 1369 DESCRIPTION 1370 "Primary index into this table identifying a 1371 particular explicit route object." 1372 ::= { mplsTunnelHopEntry 1 } 1374 mplsTunnelHopPathOptionIndex OBJECT-TYPE 1375 SYNTAX MplsPathIndex 1376 MAX-ACCESS not-accessible 1377 STATUS current 1378 DESCRIPTION 1379 "Secondary index into this table identifying a 1380 particular group of hops representing a particular 1381 configured path. This is otherwise known as a path 1382 option." 1383 ::= { mplsTunnelHopEntry 2 } 1385 mplsTunnelHopIndex OBJECT-TYPE 1386 SYNTAX MplsPathIndex 1387 MAX-ACCESS not-accessible 1388 STATUS current 1389 DESCRIPTION 1390 "Secondary index into this table identifying a 1391 particular hop." 1392 ::= { mplsTunnelHopEntry 3 } 1394 mplsTunnelHopAddrType OBJECT-TYPE 1395 SYNTAX INTEGER { 1396 ipV4(1), 1397 ipV6(2), 1398 asNumber(3), 1399 lspid(4) 1400 } 1401 MAX-ACCESS read-create 1402 STATUS current 1403 DESCRIPTION 1404 "Denotes the address type of this tunnel hop." 1405 DEFVAL { ipV4 } 1406 ::= { mplsTunnelHopEntry 4 } 1408 mplsTunnelHopIpv4Addr OBJECT-TYPE 1409 SYNTAX InetAddressIPv4 1410 MAX-ACCESS read-create 1411 STATUS current 1412 DESCRIPTION 1413 "If mplsTunnelHopAddrType is set to ipV4(1), then 1414 this value will contain the IPv4 address of this 1415 hop. If mplsTunnelHopAddrType is set to lspid(4), 1416 then this value will contain the Ingress LSR Router 1417 ID of the Tunnel. This object is otherwise 1418 insignificant and should contain a value of 0." 1419 ::= { mplsTunnelHopEntry 5 } 1421 mplsTunnelHopIpv4PrefixLen OBJECT-TYPE 1422 SYNTAX Unsigned32 (0..32) 1423 MAX-ACCESS read-create 1424 STATUS current 1425 DESCRIPTION 1426 "If mplsTunnelHopAddrType is ipV4(1), then the prefix 1427 length for this hop's IPv4 address is contained 1428 herein. This object is otherwise insignificant and 1429 should contain a value of 0." 1430 ::= { mplsTunnelHopEntry 6 } 1432 mplsTunnelHopIpv6Addr OBJECT-TYPE 1433 SYNTAX InetAddressIPv6 1434 MAX-ACCESS read-create 1435 STATUS current 1436 DESCRIPTION 1437 "If the mplsTunnelHopAddrType is set to ipV6(2), then 1438 this variable contains the IPv6 address of this 1439 hop. This object is otherwise insignificant and 1440 should contain a value of 0." 1441 ::= { mplsTunnelHopEntry 7 } 1443 mplsTunnelHopIpv6PrefixLen OBJECT-TYPE 1444 SYNTAX Unsigned32 (0..128) 1445 MAX-ACCESS read-create 1446 STATUS current 1447 DESCRIPTION 1448 "If mplsTunnelHopAddrType is set to ipV6(2), this 1449 value will contain the prefix length for this hop's 1450 IPv6 address. This object is otherwise 1451 insignificant and should contain a value of 0." 1452 ::= { mplsTunnelHopEntry 8 } 1454 mplsTunnelHopAsNumber OBJECT-TYPE 1455 SYNTAX Unsigned32 (0..65535) 1456 MAX-ACCESS read-create 1457 STATUS current 1458 DESCRIPTION 1459 "If mplsTunnelHopAddrType is set to asNumber(3), then 1460 this value will contain the AS number of this hop. 1461 This object is otherwise insignificant and should 1462 contain a value of 0 to indicate this fact." 1463 ::= { mplsTunnelHopEntry 9 } 1465 mplsTunnelHopLspId OBJECT-TYPE 1466 SYNTAX MplsLSPID 1467 MAX-ACCESS read-create 1468 STATUS current 1469 DESCRIPTION 1470 "If mplsTunnelHopAddrType is set to lspid(4), then 1471 this value will contain the LSPID of a tunnel of 1472 this hop. The present tunnel being configured is 1473 �tunneled� through this hop (using label stacking). 1474 This object is otherwise insignificant and should 1475 contain a value of 0 to indicate this fact." 1476 ::= { mplsTunnelHopEntry 10 } 1478 mplsTunnelHopType OBJECT-TYPE 1479 SYNTAX INTEGER { 1480 strict(1), 1481 loose(2) 1482 } 1483 MAX-ACCESS read-create 1484 STATUS current 1485 DESCRIPTION 1486 "Denotes whether this tunnel hop is routed in a 1487 strict or loose fashion." 1488 ::= { mplsTunnelHopEntry 11 } 1490 mplsTunnelHopIncludeExclude OBJECT-TYPE 1491 SYNTAX INTEGER { 1492 include(1), 1493 exclude(2) 1494 } 1495 MAX-ACCESS read-create 1496 STATUS current 1497 DESCRIPTION 1498 "If this value is set to include(1), then this 1499 indicates that this hop must be included in the 1500 tunnel's path. If this value is set to exclude(2), 1501 then this hop must be avoided when calculating the 1502 path for this tunnel. The default value of this 1503 object is include(1), so that by default all 1504 indicated hops are included in the CSPF path 1505 computation." 1506 DEFVAL { include } 1507 ::= { mplsTunnelHopEntry 12 } 1509 mplsTunnelHopPathOptionName OBJECT-TYPE 1510 SYNTAX DisplayString 1511 MAX-ACCESS read-create 1512 STATUS current 1513 DESCRIPTION 1514 "The description of this series of hops as they 1515 relate to the 1516 specified path option." 1517 ::= { mplsTunnelHopEntry 13 } 1519 mplsTunnelHopEntryPathComp OBJECT-TYPE 1520 SYNTAX INTEGER { 1521 dynamic(1), -- CSPF computed 1522 explicit(2) -- strict hop 1523 } 1524 MAX-ACCESS read-create 1525 STATUS current 1526 DESCRIPTION 1527 "If this value is set to dynamic, then the user 1528 should only specify the source and destination of 1529 the path and expect that the CSPF will calculate 1530 the remainder of the path. If this value is set to 1531 explicit, the user should specify the entire path 1532 for the tunnel to take. This path may contain 1533 strict or loose hops. Each hop along a specific 1534 path should have this object set to the same value" 1535 ::= { mplsTunnelHopEntry 14 } 1537 mplsTunnelHopRowStatus OBJECT-TYPE 1538 SYNTAX RowStatus 1539 MAX-ACCESS read-create 1540 STATUS current 1541 DESCRIPTION 1542 "This variable is used to create, modify, and/or 1543 delete a row in this table." 1544 ::= { mplsTunnelHopEntry 15 } 1546 mplsTunnelHopStorageType OBJECT-TYPE 1547 SYNTAX StorageType 1548 MAX-ACCESS read-create 1549 STATUS current 1550 DESCRIPTION 1551 "This variable indicates the storage type for this 1552 object." 1553 ::= { mplsTunnelHopEntry 16 } 1555 -- End of mplsTunnelHopTable 1557 -- Begin of mplsTunnelResourceTable 1559 mplsTunnelResourceIndexNext OBJECT-TYPE 1560 SYNTAX Unsigned32 (0.. 2147483647) 1561 MAX-ACCESS read-only 1562 STATUS current 1563 DESCRIPTION 1564 "This object contains the next appropriate value to 1565 be used for mplsTunnelResourceIndex when creating 1566 entries in the mplsTunnelResourceTable. If the 1567 number of unassigned entries is exhausted, a 1568 retrival operation will return a value of 0. This 1569 object may also return a value of 0 when the LSR is 1570 unable to accept conceptual row creation, for 1571 example, if the mplsTunnelTable is implemented as 1572 read-only. To obtain the mplsTunnelResourceIndex 1573 value for a new entry, the manager must first issue 1574 a management protocol retrieval operation to obtain 1575 the current value of this object. The agent should 1576 modify the value to reflect the next unassigned 1577 index after each retrieval operation. After a 1578 manager retrieves a value the agent will determine 1579 through its local policy when this index value will 1580 be made available for reuse." 1581 ::= { mplsTeObjects 5 } 1583 mplsTunnelResourceTable OBJECT-TYPE 1584 SYNTAX SEQUENCE OF MplsTunnelResourceEntry 1585 MAX-ACCESS not-accessible 1586 STATUS current 1587 DESCRIPTION 1588 "The mplsTunnelResourceTable allows a manager to 1589 specify which resources are desired for an MPLS 1590 tunnel. This table also allows several tunnels to 1591 point to a single entry in this table, implying 1592 that these tunnels should share resources." 1593 ::= { mplsTeObjects 6 } 1595 mplsTunnelResourceEntry OBJECT-TYPE 1596 SYNTAX MplsTunnelResourceEntry 1597 MAX-ACCESS not-accessible 1598 STATUS current 1599 DESCRIPTION 1600 "An entry in this table represents a set of resources 1601 for an MPLS tunnel. An entry can be created by a 1602 network administrator or by an SNMP agent as 1603 instructed by any MPLS signaling protocol." 1604 INDEX { mplsTunnelResourceIndex } 1605 ::= { mplsTunnelResourceTable 1 } 1607 MplsTunnelResourceEntry ::= SEQUENCE { 1608 mplsTunnelResourceIndex Unsigned32, 1609 mplsTunnelResourceMaxRate MplsBitRate, 1610 mplsTunnelResourceMeanRate MplsBitRate, 1611 mplsTunnelResourceMaxBurstSize MplsBurstSize, 1612 mplsTunnelResourceMeanBurstSize MplsBurstSize, 1613 mplsTunnelResourceExcessBurstSize MplsBurstSize, 1614 mplsTunnelResourceFrequency INTEGER, 1615 mplsTunnelResourceWeight Unsigned32, 1616 mplsTunnelResourceRowStatus RowStatus, 1617 mplsTunnelResourceStorageType StorageType 1618 } 1620 mplsTunnelResourceIndex OBJECT-TYPE 1621 SYNTAX Unsigned32 (1..2147483647) 1622 MAX-ACCESS not-accessible 1623 STATUS current 1624 DESCRIPTION 1625 "Uniquely identifies this row." 1626 ::= { mplsTunnelResourceEntry 1 } 1628 mplsTunnelResourceMaxRate OBJECT-TYPE 1629 SYNTAX MplsBitRate 1630 UNITS "bits per second" 1631 MAX-ACCESS read-create 1632 STATUS current 1633 DESCRIPTION 1634 "The maximum rate in bits/second. Note that setting 1635 mplsTunnelResourceMaxRate, 1636 mplsTunnelResourceMeanRate, and 1637 mplsTunnelResourceMaxBurstSize to 0 indicates best- 1638 effort treatment. 1639 This object is copied to an instance of 1640 mplsTrafficParamMaxRate in mplsTrafficParamTable 1641 the OID of which is copied into the corresponding 1642 mplsInSegmentTrafficParamPtr." 1643 REFERENCE 1644 "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS 1645 Label Switch Router Management Information Base 1646 Using SMIv2, Internet Draft , July 2000." 1648 ::= { mplsTunnelResourceEntry 2 } 1650 mplsTunnelResourceMeanRate OBJECT-TYPE 1651 SYNTAX MplsBitRate 1652 UNITS "bits per second" 1653 MAX-ACCESS read-create 1654 STATUS current 1655 DESCRIPTION 1656 "This object is copied into an instance of 1657 mplsTrafficParamMeanRate in the 1658 mplsTrafficParamTable. The OID of this table entry 1659 is then copied into the corresponding 1660 mplsInSegmentTrafficParamPtr. 1662 When resource allocation is performed as requested 1663 by this TSpec object, it is copied into an entry in 1664 mplsTrafficParamTable [LSRMIB]: 1665 mplsTunnelInMeanRate to mplsTrafficParamMeanRate. 1666 The OID of this entry is copied to 1667 mplsInSegmentTrafficParamPtr of the corresponding 1668 in-segment entry." 1670 REFERENCE 1671 "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS 1672 Label Switch Router Management Information Base 1673 Using SMIv2, Internet Draft , July 2000." 1675 ::= { mplsTunnelResourceEntry 3 } 1677 mplsTunnelResourceMaxBurstSize OBJECT-TYPE 1678 SYNTAX MplsBurstSize 1679 UNITS "bytes" 1680 MAX-ACCESS read-create 1681 STATUS current 1682 DESCRIPTION 1683 "The maximum burst size in bytes. This object is 1684 copied to mplsInSegmentMaxBurstSize of the 1685 corresponding in-segment. 1687 When resource allocation is performed as requested 1688 by this TSpec object, it is copied into an entry in 1689 mplsTrafficParamTable [LSRMIB]: 1690 mplsTunnelInMaxBurstSize to 1691 mplsTrafficParamMaxBurstSize. The OID of this entry 1692 is copied to mplsInSegmentTrafficParamPtr of the 1693 corresponding in-segment entry." 1694 REFERENCE 1695 "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS 1696 Label Switch Router Management Information Base 1697 Using SMIv2, Internet Draft , July 2000." 1699 ::= { mplsTunnelResourceEntry 4 } 1701 mplsTunnelResourceMeanBurstSize OBJECT-TYPE 1702 SYNTAX MplsBurstSize 1703 UNITS "bytes" 1704 MAX-ACCESS read-create 1705 STATUS current 1706 DESCRIPTION 1707 "The mean burst size in bytes. The implementations 1708 which do not implement this variable must return 0 1709 for this value and must not allow a user to set 1710 this value." 1711 ::= { mplsTunnelResourceEntry 5 } 1713 mplsTunnelResourceExcessBurstSize OBJECT-TYPE 1714 SYNTAX MplsBurstSize 1715 UNITS "bytes" 1716 MAX-ACCESS read-create 1717 STATUS current 1718 DESCRIPTION 1719 "The Excess burst size in bytes. The implementations 1720 which do not implement this variable must return 0 1721 for this value and must not allow a user to set 1722 this value." 1723 REFERENCE 1724 "CR-LDP Specification, Section 4.3." 1725 ::= { mplsTunnelResourceEntry 6 } 1727 mplsTunnelResourceFrequency OBJECT-TYPE 1728 SYNTAX INTEGER { 1729 unspecified(1), 1730 frequent(2), 1731 veryFrequent(3) 1732 } 1733 MAX-ACCESS read-create 1734 STATUS current 1735 DESCRIPTION 1736 "The granularity of the availability of committed 1737 rate. The implementations which do not implement 1738 this variable must return unspecified(1) for this 1739 value and must not allow a user to set this value." 1740 REFERENCE 1741 "CR-LDP Specification, Section 4.3." 1742 ::= { mplsTunnelResourceEntry 7 } 1744 mplsTunnelResourceWeight OBJECT-TYPE 1745 SYNTAX Unsigned32(0..255) 1746 MAX-ACCESS read-create 1747 STATUS current 1748 DESCRIPTION 1749 "The relative weight for using excess bandwidth above 1750 its committed rate. The value of 0 means that 1751 weight is not applicable for the CR-LSP." 1752 REFERENCE 1753 "CR-LDP Specification, Section 4.3." 1754 ::= { mplsTunnelResourceEntry 8 } 1756 mplsTunnelResourceRowStatus OBJECT-TYPE 1757 SYNTAX RowStatus 1758 MAX-ACCESS read-create 1759 STATUS current 1760 DESCRIPTION 1761 "This variable is used to create, modify, and/or 1762 delete a row in this table." 1763 ::= { mplsTunnelResourceEntry 9 } 1765 mplsTunnelResourceStorageType OBJECT-TYPE 1766 SYNTAX StorageType 1767 MAX-ACCESS read-create 1768 STATUS current 1769 DESCRIPTION 1770 "This variable indicates the storage type for this 1771 object." 1772 ::= { mplsTunnelResourceEntry 10 } 1774 -- End mplsTunnelResourceTable 1775 -- Tunnel Actual Route Hop table. 1777 mplsTunnelARHopTable OBJECT-TYPE 1778 SYNTAX SEQUENCE OF MplsTunnelARHopEntry 1779 MAX-ACCESS not-accessible 1780 STATUS current 1781 DESCRIPTION 1782 "The mplsTunnelARHopTable is used to indicate the 1783 hops, strict or loose, for an MPLS tunnel defined 1784 in mplsTunnelTable, as reported by the MPLS 1785 signaling protocol, for the outgoing direction of 1786 the tunnel. Each row in this table is indexed by 1787 mplsTunnelARHopListIndex. Each row also has a 1788 secondary index mplsTunnelARHopIndex, corresponding 1789 to the next hop that this row corresponds to. The 1790 first row in the table is the first hop after the 1791 origination point of the tunnel. In case we want 1792 to specify a particular interface on the 1793 originating LSR of an outgoing tunnel by which we 1794 want packets to exit the LSR, we specify this as 1795 the first hop for this tunnel in 1796 mplsTunnelARHopTable. 1798 Please note that since the information necessary to 1799 build entries within this table are not provided by 1800 some MPLS signaling protocols, implementation of 1801 this table is optional. Furthermore, since the 1802 information in this table is actually provided by 1803 the MPLS signaling protocol after the path has been 1804 set-up, the entries in this table are provided only 1805 for observation, and hence, all variables in this 1806 table are accessible exclusively as read-only." 1807 ::= { mplsTeObjects 7 } 1809 mplsTunnelARHopEntry OBJECT-TYPE 1810 SYNTAX MplsTunnelARHopEntry 1811 MAX-ACCESS not-accessible 1812 STATUS current 1813 DESCRIPTION 1814 "An entry in this table represents a tunnel hop. An 1815 entry is created by a network administrator for 1816 signaled ERLSP set up by an MPLS signaling 1817 protocol." 1818 INDEX { mplsTunnelARHopListIndex, mplsTunnelARHopIndex } 1819 ::= { mplsTunnelARHopTable 1 } 1821 MplsTunnelARHopEntry ::= SEQUENCE { 1822 mplsTunnelARHopListIndex MplsPathIndex, 1823 mplsTunnelARHopIndex MplsPathIndex, 1824 mplsTunnelARHopAddrType INTEGER, 1825 mplsTunnelARHopIpv4Addr InetAddressIPv4, 1826 mplsTunnelARHopIpv4PrefixLen Unsigned32, 1827 mplsTunnelARHopIpv6Addr InetAddressIPv6, 1828 mplsTunnelARHopIpv6PrefixLen Unsigned32, 1829 mplsTunnelARHopAsNumber Unsigned32, 1830 mplsTunnelARHopLspId MplsLSPID 1831 } 1833 mplsTunnelARHopListIndex OBJECT-TYPE 1834 SYNTAX MplsPathIndex 1835 MAX-ACCESS not-accessible 1836 STATUS current 1837 DESCRIPTION 1838 "Primary index into this table identifying a 1839 particular recorded hop list." 1840 ::= { mplsTunnelARHopEntry 1 } 1842 mplsTunnelARHopIndex OBJECT-TYPE 1843 SYNTAX MplsPathIndex 1844 MAX-ACCESS not-accessible 1845 STATUS current 1846 DESCRIPTION 1847 "Secondary index into this table identifying the 1848 particular hop." 1849 ::= { mplsTunnelARHopEntry 2 } 1851 mplsTunnelARHopAddrType OBJECT-TYPE 1852 SYNTAX INTEGER { 1853 ipV4(1), 1854 ipV6(2), 1855 asNumber(3) 1856 } 1857 MAX-ACCESS read-only 1858 STATUS current 1859 DESCRIPTION 1860 "Denotes the address type of this tunnel hop." 1861 DEFVAL { ipV4 } 1862 ::= { mplsTunnelARHopEntry 3 } 1864 mplsTunnelARHopIpv4Addr OBJECT-TYPE 1865 SYNTAX InetAddressIPv4 1866 MAX-ACCESS read-only 1867 STATUS current 1868 DESCRIPTION 1869 "If mplsTunnelARHopAddrType is set to ipV4(1), then 1870 this value will contain the IPv4 address of this 1871 hop. This object is otherwise insignificant and 1872 should contain a value of 0." 1873 ::= { mplsTunnelARHopEntry 4 } 1875 mplsTunnelARHopIpv4PrefixLen OBJECT-TYPE 1876 SYNTAX Unsigned32 (0..32) 1877 MAX-ACCESS read-only 1878 STATUS current 1879 DESCRIPTION 1880 "If mplsTunnelARHopAddrType is ipV4(1), then the 1881 prefix length for this hop's IPv4 address is 1882 contained herein. This object is otherwise 1883 insignificant and should contain a value of 0." 1884 ::= { mplsTunnelARHopEntry 5 } 1886 mplsTunnelARHopIpv6Addr OBJECT-TYPE 1887 SYNTAX InetAddressIPv6 1888 MAX-ACCESS read-only 1889 STATUS current 1890 DESCRIPTION 1891 "If the mplsTunnelARHopAddrType is set to ipV6(2), 1892 then this variable contains the IPv6 address of 1893 this hop. This object is otherwise insignificant 1894 and should contain a value of 0." 1895 ::= { mplsTunnelARHopEntry 6 } 1897 mplsTunnelARHopIpv6PrefixLen OBJECT-TYPE 1898 SYNTAX Unsigned32 (0..128) 1899 MAX-ACCESS read-only 1900 STATUS current 1901 DESCRIPTION 1902 "If mplsTunnelARHopAddrType is set to ipV6(2), this 1903 value will contain the prefix length for this hop's 1904 IPv6 address. This object is otherwise 1905 insignificant and should contain a value of 0." 1906 ::= { mplsTunnelARHopEntry 7 } 1908 mplsTunnelARHopAsNumber OBJECT-TYPE 1909 SYNTAX Unsigned32 (0..65535) 1910 MAX-ACCESS read-only 1911 STATUS current 1912 DESCRIPTION 1913 "If mplsTunnelARHopAddrType is set to asNumber(3), 1914 then this value will contain the AS number of this 1915 hop. This object is otherwise insignificant and 1916 should contain a value of 0 to indicate this fact." 1917 ::= { mplsTunnelARHopEntry 8 } 1919 mplsTunnelARHopLspId OBJECT-TYPE 1920 SYNTAX MplsLSPID 1921 MAX-ACCESS read-only 1922 STATUS current 1923 DESCRIPTION 1924 "If mplsTunnelARHopAddrType is set to lspid(4), then 1925 this value will contain the LSP ID of this hop. 1926 This object is otherwise insignificant and should 1927 contain a value of 0 to indicate this fact." 1928 ::= { mplsTunnelARHopEntry 9 } 1930 -- End of mplsTunnelARHopTable 1932 -- Tunnel Computed Hop table. 1934 mplsTunnelCHopTable OBJECT-TYPE 1935 SYNTAX SEQUENCE OF MplsTunnelCHopEntry 1936 MAX-ACCESS not-accessible 1937 STATUS current 1938 DESCRIPTION 1939 "The mplsTunnelCHopTable is used to indicate the 1940 hops, strict or loose, for an MPLS tunnel defined 1941 in mplsTunnelTable, as computed by a constraint- 1942 based routing protocol, based on the 1943 mplsTunnelHopTable for the outgoing direction of 1944 the tunnel. Each row in this table is indexed by 1945 mplsTunnelCHopListIndex. Each row also has a 1946 secondary index mplsTunnelCHopIndex, corresponding 1947 to the next hop that this row corresponds to. The 1948 first row in the table is the first hop after the 1949 origination point of the tunnel. In case we want 1950 to specify a particular interface on the 1951 originating LSR of an outgoing tunnel by which we 1952 want packets to exit the LSR, we specify this as 1953 the first hop for this tunnel in 1954 mplsTunnelCHopTable. 1956 Please note that since the information necessary to 1957 build entries within this table may not be 1958 supported by some LSRs, implementation of this 1959 table is optional. Furthermore, since the 1960 information in this table is actually provided by 1961 routing protocol after the path has been computed, 1962 the entries in this table are provided only for 1963 observation, and hence, all variables in this table 1964 are accessible exclusively as read-only." 1965 ::= { mplsTeObjects 8 } 1967 mplsTunnelCHopEntry OBJECT-TYPE 1968 SYNTAX MplsTunnelCHopEntry 1969 MAX-ACCESS not-accessible 1970 STATUS current 1971 DESCRIPTION 1972 "An entry in this table represents a tunnel hop. An 1973 entry in this table is created by a constraint- 1974 based routing protocol based on the hops specified 1975 in the corresponding mplsTunnelHopTable." 1976 INDEX { mplsTunnelCHopListIndex, mplsTunnelCHopIndex } 1977 ::= { mplsTunnelCHopTable 1 } 1979 MplsTunnelCHopEntry ::= SEQUENCE { 1980 mplsTunnelCHopListIndex MplsPathIndex, 1981 mplsTunnelCHopIndex MplsPathIndex, 1982 mplsTunnelCHopAddrType INTEGER, 1983 mplsTunnelCHopIpv4Addr InetAddressIPv4, 1984 mplsTunnelCHopIpv4PrefixLen Unsigned32, 1985 mplsTunnelCHopIpv6Addr InetAddressIPv6, 1986 mplsTunnelCHopIpv6PrefixLen Unsigned32, 1987 mplsTunnelCHopAsNumber Unsigned32, 1988 mplsTunnelCHopType INTEGER 1989 } 1991 mplsTunnelCHopListIndex OBJECT-TYPE 1992 SYNTAX MplsPathIndex 1993 MAX-ACCESS not-accessible 1994 STATUS current 1995 DESCRIPTION 1996 "Primary index into this table identifying a 1997 particular computed hop list." 1998 ::= { mplsTunnelCHopEntry 1 } 2000 mplsTunnelCHopIndex OBJECT-TYPE 2001 SYNTAX MplsPathIndex 2002 MAX-ACCESS not-accessible 2003 STATUS current 2004 DESCRIPTION 2005 "Secondary index into this table identifying the 2006 particular hop." 2007 ::= { mplsTunnelCHopEntry 2 } 2009 mplsTunnelCHopAddrType OBJECT-TYPE 2010 SYNTAX INTEGER { 2011 ipV4(1), 2012 ipV6(2), 2013 asNumber(3) 2014 } 2015 MAX-ACCESS read-only 2016 STATUS current 2017 DESCRIPTION 2018 "Denotes the address type of this tunnel hop." 2019 DEFVAL { ipV4 } 2020 ::= { mplsTunnelCHopEntry 3 } 2022 mplsTunnelCHopIpv4Addr OBJECT-TYPE 2023 SYNTAX InetAddressIPv4 2024 MAX-ACCESS read-only 2025 STATUS current 2026 DESCRIPTION 2027 "If mplsTunnelCHopAddrType is set to ipV4(1), then 2028 this value will contain the IPv4 address of this 2029 hop. This object is otherwise insignificant and 2030 should contain a value of 0." 2031 ::= { mplsTunnelCHopEntry 4 } 2033 mplsTunnelCHopIpv4PrefixLen OBJECT-TYPE 2034 SYNTAX Unsigned32 (0..32) 2035 MAX-ACCESS read-only 2036 STATUS current 2037 DESCRIPTION 2038 "If mplsTunnelCHopAddrType is ipV4(1), then the 2039 prefix length for this hop's IPv4 address is 2040 contained herein. This object is otherwise 2041 insignificant and should contain a value of 0." 2042 ::= { mplsTunnelCHopEntry 5 } 2044 mplsTunnelCHopIpv6Addr OBJECT-TYPE 2045 SYNTAX InetAddressIPv6 2046 MAX-ACCESS read-only 2047 STATUS current 2048 DESCRIPTION 2049 "If the mplsTunnelCHopAddrType is set to ipV6(2), 2050 then this variable contains the IPv6 address of 2051 this hop. This object is otherwise insignificant 2052 and should contain a value of 0." 2053 ::= { mplsTunnelCHopEntry 6 } 2055 mplsTunnelCHopIpv6PrefixLen OBJECT-TYPE 2056 SYNTAX Unsigned32 (0..128) 2057 MAX-ACCESS read-only 2058 STATUS current 2059 DESCRIPTION 2060 "If mplsTunnelCHopAddrType is set to ipV6(2), this 2061 value will contain the prefix length for this hop's 2062 IPv6 address. This object is otherwise 2063 insignificant and should contain a value of 0." 2064 ::= { mplsTunnelCHopEntry 7 } 2066 mplsTunnelCHopAsNumber OBJECT-TYPE 2067 SYNTAX Unsigned32 (0..65535) 2068 MAX-ACCESS read-only 2069 STATUS current 2070 DESCRIPTION 2071 "If mplsTunnelCHopAddrType is set to asNumber(3), 2072 then this value will contain the AS number of this 2073 hop. This object is otherwise insignificant and 2074 should contain a value of 0 to indicate this fact." 2075 ::= { mplsTunnelCHopEntry 8 } 2077 mplsTunnelCHopType OBJECT-TYPE 2078 SYNTAX INTEGER { 2079 strict(1), 2080 loose(2) 2081 } 2082 MAX-ACCESS read-only 2083 STATUS current 2084 DESCRIPTION 2085 "Denotes whether this is tunnel hop is routed in a 2086 strict or loose fashion." 2087 ::= { mplsTunnelCHopEntry 9 } 2089 -- End of mplsTunnelCHopTable 2091 -- MPLS Tunnel Performance Table. 2093 mplsTunnelPerfTable OBJECT-TYPE 2094 SYNTAX SEQUENCE OF MplsTunnelPerfEntry 2095 MAX-ACCESS not-accessible 2096 STATUS current 2097 DESCRIPTION 2098 "This table provides per-tunnel MPLS performance 2099 information." 2100 ::= { mplsTeObjects 9 } 2102 mplsTunnelPerfEntry OBJECT-TYPE 2103 SYNTAX MplsTunnelPerfEntry 2104 MAX-ACCESS not-accessible 2105 STATUS current 2106 DESCRIPTION 2107 "An entry in this table is created by the LSR for 2108 every tunnel. Its is an extension to 2109 mplsTunnelEntry." 2110 AUGMENTS { mplsTunnelEntry } 2111 ::= { mplsTunnelPerfTable 1 } 2113 MplsTunnelPerfEntry ::= SEQUENCE { 2114 mplsTunnelPerfPackets Counter32, 2115 mplsTunnelPerfHCPackets Counter64, 2116 mplsTunnelPerfErrors Counter32, 2117 mplsTunnelPerfBytes Counter32, 2118 mplsTunnelPerfHCBytes Counter64 2119 } 2121 mplsTunnelPerfPackets OBJECT-TYPE 2122 SYNTAX Counter32 2123 MAX-ACCESS read-only 2124 STATUS current 2125 DESCRIPTION 2126 "Number of packets forwarded by the tunnel." 2127 ::= { mplsTunnelPerfEntry 1 } 2129 mplsTunnelPerfHCPackets OBJECT-TYPE 2130 SYNTAX Counter64 2131 MAX-ACCESS read-only 2132 STATUS current 2133 DESCRIPTION 2134 "High capacity counter for number of packets 2135 forwarded by the tunnel." 2136 ::= { mplsTunnelPerfEntry 2 } 2138 mplsTunnelPerfErrors OBJECT-TYPE 2139 SYNTAX Counter32 2140 MAX-ACCESS read-only 2141 STATUS current 2142 DESCRIPTION 2143 "Number of errored packets." 2144 ::= { mplsTunnelPerfEntry 3 } 2146 mplsTunnelPerfBytes OBJECT-TYPE 2147 SYNTAX Counter32 2148 MAX-ACCESS read-only 2149 STATUS current 2150 DESCRIPTION 2151 "Number of bytes forwarded by the tunnel." 2152 ::= { mplsTunnelPerfEntry 4 } 2154 mplsTunnelPerfHCBytes OBJECT-TYPE 2155 SYNTAX Counter64 2156 MAX-ACCESS read-only 2157 STATUS current 2158 DESCRIPTION 2159 "High capacity counter for number of bytes forwarded 2160 by the tunnel." 2161 ::= { mplsTunnelPerfEntry 5 } 2163 -- End of mplsTunnelPerfTable 2165 -- CR-LDP Tunnel Resource Table 2167 mplsTunnelCRLDPResTable OBJECT-TYPE 2168 SYNTAX SEQUENCE OF MplsTunnelCRLDPResEntry 2169 MAX-ACCESS not-accessible 2170 STATUS current 2171 DESCRIPTION 2172 "The mplsTunnelCRLDPResTable allows a manager to 2173 specify which CR-LDP-specific resources are desired 2174 for an MPLS tunnel if that tunnel is signaled using 2175 CR-LDP. Note that these attributes are in addition 2176 to those specified in mplsTunnelResourceTable. This 2177 table also allows several tunnels to point to a 2178 single entry in this table, implying that these 2179 tunnels should share resources." 2180 ::= { mplsTeObjects 10 } 2182 mplsTunnelCRLDPResEntry OBJECT-TYPE 2183 SYNTAX MplsTunnelCRLDPResEntry 2184 MAX-ACCESS not-accessible 2185 STATUS current 2186 DESCRIPTION 2187 "An entry in this table represents a set of resources 2188 for an MPLS tunnel established using CRLDP 2189 (mplsTunnelSignallingProto equal to crldp (3)). An 2190 entry can be created by a network administrator or 2191 by an SNMP agent as instructed by any MPLS 2192 signaling protocol." 2193 INDEX { mplsTunnelResourceIndex } 2194 ::= { mplsTunnelCRLDPResTable 1 } 2196 MplsTunnelCRLDPResEntry ::= SEQUENCE { 2197 mplsTunnelCRLDPResMeanBurstSize MplsBurstSize, 2198 mplsTunnelCRLDPResExcessBurstSize MplsBurstSize, 2199 mplsTunnelCRLDPResFrequency Integer32, 2200 mplsTunnelCRLDPResWeight Unsigned32, 2201 mplsTunnelCRLDPResFlags Unsigned32, 2202 mplsTunnelCRLDPResRowStatus RowStatus, 2203 mplsTunnelCRLDPResStorageType StorageType 2204 } 2206 mplsTunnelCRLDPResMeanBurstSize OBJECT-TYPE 2207 SYNTAX MplsBurstSize 2208 UNITS "bytes" 2209 MAX-ACCESS read-create 2210 STATUS current 2211 DESCRIPTION 2212 "The mean burst size in bytes." 2213 ::= { mplsTunnelCRLDPResEntry 2 } 2215 mplsTunnelCRLDPResExcessBurstSize OBJECT-TYPE 2216 SYNTAX MplsBurstSize 2217 UNITS "bytes" 2218 MAX-ACCESS read-create 2219 STATUS current 2220 DESCRIPTION 2221 "The Excess burst size in bytes." 2222 REFERENCE 2223 "CR-LDP Specification, Section 4.3." 2224 ::= { mplsTunnelCRLDPResEntry 3 } 2226 mplsTunnelCRLDPResFrequency OBJECT-TYPE 2227 SYNTAX INTEGER { 2228 unspecified(1), 2229 frequent(2), 2230 veryFrequent(3) 2231 } 2232 MAX-ACCESS read-create 2233 STATUS current 2234 DESCRIPTION 2235 "The granularity of the availability of committed 2236 rate." 2237 REFERENCE 2238 "CR-LDP Specification, Section 4.3." 2239 ::= { mplsTunnelCRLDPResEntry 4 } 2241 mplsTunnelCRLDPResWeight OBJECT-TYPE 2242 SYNTAX Unsigned32(0..255) 2243 MAX-ACCESS read-create 2244 STATUS current 2245 DESCRIPTION 2246 "The relative weight for using excess bandwidth above 2247 its committed rate. The value of 0 means that 2248 weight is not applicable for the CR-LSP." 2249 REFERENCE 2250 "CR-LDP Specification, Section 4.3." 2251 DEFVAL { 0 } 2252 ::= { mplsTunnelCRLDPResEntry 5 } 2254 mplsTunnelCRLDPResFlags OBJECT-TYPE 2255 SYNTAX Unsigned32 (0..63) 2256 MAX-ACCESS read-create 2257 STATUS current 2258 DESCRIPTION 2259 "The value of the 1 byte Flags conveyed as part of 2260 the traffic parameters during the establishment of 2261 the CRLSP. The bits in this object are to be 2262 interpreted as follows. 2264 +--+--+--+--+--+--+--+--+ 2265 | Res |F6|F5|F4|F3|F2|F1| 2266 +--+--+--+--+--+--+--+--+ 2268 Res - These bits are reserved. Zero on transmission. 2269 Ignored on receipt. 2270 F1 - Corresponds to the PDR. 2272 F2 - Corresponds to the PBS. 2273 F3 - Corresponds to the CDR. 2274 F4 - Corresponds to the CBS. 2275 F5 - Corresponds to the EBS. 2276 F6 - Corresponds to the Weight. 2278 Each flag if is a Negotiable Flag corresponding to a 2279 Traffic Parameter. The Negotiable Flag value zero 2280 denotes Not Negotiable and value one denotes 2281 Negotiable." 2282 REFERENCE 2283 "Section 4.3, Constraint-Based LSP Setup using LDP, 2284 Jamoussi, et. al,, 2285 July 2000." 2286 DEFVAL { 0 } 2287 ::= { mplsTunnelCRLDPResEntry 6 } 2289 mplsTunnelCRLDPResRowStatus OBJECT-TYPE 2290 SYNTAX RowStatus 2291 MAX-ACCESS read-create 2292 STATUS current 2293 DESCRIPTION 2294 "This variable is used to create, modify, and/or 2295 delete a row in this table." 2296 ::= { mplsTunnelCRLDPResEntry 7 } 2298 mplsTunnelCRLDPResStorageType OBJECT-TYPE 2299 SYNTAX StorageType 2300 MAX-ACCESS read-create 2301 STATUS current 2302 DESCRIPTION 2303 "This variable indicates the storage type for this 2304 object." 2305 ::= { mplsTunnelCRLDPResEntry 8 } 2307 -- Notifications. 2309 mplsTunnelTrapEnable OBJECT-TYPE 2310 SYNTAX TruthValue 2311 MAX-ACCESS read-write 2312 STATUS current 2313 DESCRIPTION 2314 "If this object is true, then it enables the 2315 generation of mplsTunnelUp and mplsTunnelDown 2316 traps, otherwise these traps are not emitted." 2317 DEFVAL { false } 2318 ::= { mplsTeObjects 11 } 2320 mplsTunnelUp NOTIFICATION-TYPE 2321 OBJECTS { 2322 mplsTunnelIndex, 2323 mplsTunnelInstance, 2324 mplsTunnelIngressLSRId, 2325 mplsTunnelEgressLSRId, 2326 mplsTunnelAdminStatus, 2327 mplsTunnelOperStatus 2328 } 2329 STATUS current 2330 DESCRIPTION 2331 "This notification is generated when a 2332 mplsTunnelOperStatus object for one of the 2333 configured tunnels is about to leave the down state 2334 and transition into some other state (but not into 2335 the notPresent state). This other state is 2336 indicated by the included value of 2337 mplsTunnelOperStatus." 2338 ::= { mplsTeNotifyPrefix 1 } 2340 mplsTunnelDown NOTIFICATION-TYPE 2341 OBJECTS { 2342 mplsTunnelIndex, 2343 mplsTunnelInstance, 2344 mplsTunnelIngressLSRId, 2345 mplsTunnelEgressLSRId, 2346 mplsTunnelAdminStatus, 2347 mplsTunnelOperStatus 2348 } 2349 STATUS current 2350 DESCRIPTION 2351 "This notification is generated when a 2352 mplsTunnelOperStatus object for one of the 2353 configured tunnels is about to enter the down state 2354 from some other state (but not from the notPresent 2355 state). This other state is indicated by the 2356 included value of mplsTunnelOperStatus." 2357 ::= { mplsTeNotifyPrefix 2 } 2359 mplsTunnelRerouted NOTIFICATION-TYPE 2360 OBJECTS { 2361 mplsTunnelIndex, 2362 mplsTunnelInstance, 2363 mplsTunnelIngressLSRId, 2364 mplsTunnelEgressLSRId, 2365 mplsTunnelAdminStatus, 2366 mplsTunnelOperStatus 2367 } 2368 STATUS current 2369 DESCRIPTION 2370 "This notification is generated when a tunnel is 2371 rerouted. If the actual path is used, then this 2372 object MAY contain the new path for this tunnel 2373 some time after this trap is issued by the agent." 2374 ::= { mplsTeNotifyPrefix 3 } 2376 mplsTunnelReoptimized NOTIFICATION-TYPE 2377 OBJECTS { 2378 mplsTunnelIndex, 2379 mplsTunnelInstance, 2380 mplsTunnelIngressLSRId, 2381 mplsTunnelEgressLSRId, 2382 mplsTunnelAdminStatus, 2383 mplsTunnelOperStatus 2384 } 2385 STATUS current 2386 DESCRIPTION 2387 "This notification is generated when a tunnel is 2388 reoptimized. If the actual path is used, then this 2389 object MAY contain the new path for this tunnel 2390 some time after this trap is issued by the agent." 2391 ::= { mplsTeNotifyPrefix 4 } 2393 -- End of notifications. 2395 -- Module compliance. 2397 mplsTeGroups 2398 OBJECT IDENTIFIER ::= { mplsTeConformance 1 } 2400 mplsTeCompliances 2401 OBJECT IDENTIFIER ::= { mplsTeConformance 2 } 2403 mplsTeModuleCompliance MODULE-COMPLIANCE 2404 STATUS current 2405 DESCRIPTION 2406 "Compliance statement for agents that support the 2407 MPLS TE MIB." 2408 MODULE -- this module 2410 -- The mandatory group has to be implemented by all 2411 -- LSRs that originate/terminate ESLSPs/tunnels. 2412 -- In addition, depending on the type of tunnels 2413 -- supported, other groups become mandatory as 2414 -- explained below. 2416 MANDATORY-GROUPS { 2417 mplsTunnelGroup, 2418 mplsTunnelScalarGroup 2419 } 2420 GROUP mplsTunnelManualGroup 2421 DESCRIPTION 2422 "This group is mandatory for devices which support 2423 manual configuration of tunnels, in addition to 2424 mplsTunnelGroup. The following constraints apply: 2425 mplsTunnelSignallingProto should be at least read- 2426 only with a value of none(1)." 2428 GROUP mplsTunnelSignaledGroup 2429 DESCRIPTION 2430 "This group is mandatory for devices which support 2431 signaled tunnel set up, in addition to 2432 mplsTunnelGroup. The following constraints apply: 2433 mplsTunnelSignallingProto should be at least read- 2434 only returning a value of ldp(2), or rsvp(3)." 2436 GROUP mplsTunnelIsNotIntfcGroup 2437 DESCRIPTION 2438 "This group is mandatory for devices which support 2439 tunnels that are not interfaces, in addition to 2440 mplsTunnelGroup. The following constraints apply: 2441 mplsTunnelIsIf must at least be read-only 2442 returning false(1)." 2444 GROUP mplsTunnelIsIntfcGroup 2445 DESCRIPTION 2446 "This group is mandatory for devices which support 2447 tunnels that are interfaces, in addition to 2448 mplsTunnelGroup. The following constraints apply: 2449 mplsTunnelIsIf must at least be read-only 2450 returning true(2)." 2452 GROUP mplsTunnelOptionalGroup 2453 DESCRIPTION 2454 "Objects in this group are optional." 2456 -- mplsTunnelTable 2458 OBJECT mplsTunnelName 2459 MIN-ACCESS read-only 2460 DESCRIPTION 2461 "Write access is not required." 2463 OBJECT mplsTunnelDescr 2464 MIN-ACCESS read-only 2465 DESCRIPTION 2466 "Write access is not required." 2468 OBJECT mplsTunnelIsIf 2469 MIN-ACCESS read-only 2470 DESCRIPTION 2471 "Write access is not required." 2473 OBJECT mplsTunnelIfIndex 2474 DESCRIPTION 2475 "Write access is not required." 2477 OBJECT mplsTunnelXCPointer 2478 MIN-ACCESS read-only 2479 DESCRIPTION 2480 "Write access is not required." 2482 OBJECT mplsTunnelSignallingProto 2483 MIN-ACCESS read-only 2484 DESCRIPTION 2485 "Write access is not required." 2487 OBJECT mplsTunnelSetupPrio 2488 MIN-ACCESS read-only 2489 DESCRIPTION 2490 "Write access is not required." 2492 OBJECT mplsTunnelHoldingPrio 2493 MIN-ACCESS read-only 2494 DESCRIPTION 2495 "Write access is not required." 2497 OBJECT mplsTunnelSessionAttributes 2498 MIN-ACCESS read-only 2499 DESCRIPTION 2500 "Write access is not required." 2502 OBJECT mplsTunnelOwner 2503 MIN-ACCESS read-only 2504 DESCRIPTION 2505 "Write access is not required." 2507 OBJECT mplsTunnelLocalProtectInUse 2508 MIN-ACCESS read-only 2509 DESCRIPTION 2510 "Write access is not required." 2512 OBJECT mplsTunnelResourcePointer 2513 MIN-ACCESS read-only 2514 DESCRIPTION 2515 "Write access is not required." 2517 OBJECT mplsTunnelInstancePriority 2518 MIN-ACCESS read-only 2519 DESCRIPTION 2520 "Write access is not required." 2522 OBJECT mplsTunnelHopTableIndex 2523 MIN-ACCESS read-only 2524 DESCRIPTION 2525 "Write access is not required." 2527 OBJECT mplsTunnelPrimaryInstance 2528 MIN-ACCESS read-only 2529 DESCRIPTION 2530 "Write access is not required." 2532 OBJECT mplsTunnelPrimaryTimeUp 2533 MIN-ACCESS read-only 2534 DESCRIPTION 2535 "Write access is not required." 2537 OBJECT mplsTunnelPathChanges 2538 MIN-ACCESS read-only 2539 DESCRIPTION 2540 "Write access is not required." 2542 OBJECT mplsTunnelLastPathChange 2543 MIN-ACCESS read-only 2544 DESCRIPTION 2545 "Write access is not required." 2547 OBJECT mplsTunnelCreationTime 2548 MIN-ACCESS read-only 2549 DESCRIPTION 2550 "Write access is not required." 2552 OBJECT mplsTunnelStateTransitions 2553 MIN-ACCESS read-only 2554 DESCRIPTION 2555 "Write access is not required." 2557 OBJECT mplsTunnelARHopTableIndex 2558 DESCRIPTION 2559 "Write access is not required." 2561 OBJECT mplsTunnelCHopTableIndex 2562 DESCRIPTION 2563 "Write access is not required." 2565 OBJECT mplsTunnelAdminStatus 2566 SYNTAX INTEGER { up (1), down (2) } 2567 MIN-ACCESS read-only 2568 DESCRIPTION 2569 "Only up and down states must be supported. Write 2570 access is not required." 2572 OBJECT mplsTunnelOperStatus 2573 SYNTAX INTEGER { up (1), down (2) } 2574 DESCRIPTION 2575 "Only up and down states must be supported. Write 2576 access is not required." 2578 OBJECT mplsTunnelRowStatus 2579 SYNTAX INTEGER { 2580 active(1), 2581 notInService(2), 2582 createAndGo(4), 2583 destroy(6) 2584 } 2585 MIN-ACCESS read-only 2586 DESCRIPTION 2587 "The notReady(3) and createAndWait(5) states need 2588 not be supported. Write access is not required." 2590 OBJECT mplsTunnelStorageType 2591 SYNTAX INTEGER { other(1) } 2592 MIN-ACCESS read-only 2593 DESCRIPTION 2594 "Only other (1) needs to be supported." 2596 OBJECT mplsTunnelPathInUse 2597 MIN-ACCESS read-only 2598 DESCRIPTION 2599 "Read-only support is required." 2601 OBJECT mplsTunnelRole 2602 SYNTAX INTEGER { head(1) } 2603 MIN-ACCESS read-only 2604 DESCRIPTION 2605 "Only support for head is required." 2607 OBJECT mplsTunnelTotalUpTime 2608 MIN-ACCESS read-only 2609 DESCRIPTION 2610 "Read-only support is required." 2612 OBJECT mplsTunnelInstanceUpTime 2613 MIN-ACCESS read-only 2614 DESCRIPTION 2615 "Read-only support is required." 2617 -- mplsTunnelHopTable 2618 OBJECT mplsTunnelHopAddrType 2619 MIN-ACCESS read-only 2620 DESCRIPTION 2621 "Write access is not required." 2623 OBJECT mplsTunnelHopIpv4Addr 2624 MIN-ACCESS read-only 2625 DESCRIPTION 2626 "Write access is not required." 2628 OBJECT mplsTunnelHopIpv4PrefixLen 2629 MIN-ACCESS read-only 2630 DESCRIPTION 2631 "Write access is not required." 2633 OBJECT mplsTunnelHopIpv6Addr 2634 MIN-ACCESS read-only 2635 DESCRIPTION 2636 "Write access is not required." 2638 OBJECT mplsTunnelHopIpv6PrefixLen 2639 MIN-ACCESS read-only 2640 DESCRIPTION 2641 "Write access is not required." 2643 OBJECT mplsTunnelHopAsNumber 2644 MIN-ACCESS read-only 2645 DESCRIPTION 2646 "Write access is not required." 2648 OBJECT mplsTunnelHopLspId 2649 MIN-ACCESS read-only 2650 DESCRIPTION 2651 "Write access is not required." 2653 OBJECT mplsTunnelHopType 2654 SYNTAX INTEGER { strict(1) } 2655 MIN-ACCESS read-only 2656 DESCRIPTION 2657 "loose(2) need not be supported. Write access is 2658 not required." 2660 OBJECT mplsTunnelHopIncludeExclude 2661 MIN-ACCESS read-only 2662 DESCRIPTION 2663 "Write access is not required." 2665 OBJECT mplsTunnelHopPathOptionName 2666 MIN-ACCESS read-only 2667 DESCRIPTION 2668 "Write access is not required." 2670 OBJECT mplsTunnelHopEntryPathComp 2671 MIN-ACCESS read-only 2672 DESCRIPTION 2673 "Write access is not required." 2675 OBJECT mplsTunnelHopRowStatus 2676 SYNTAX INTEGER { 2677 active(1), 2678 notInService(2), 2679 createAndGo(4), 2680 destroy(6) 2681 } 2682 MIN-ACCESS read-only 2683 DESCRIPTION 2684 "The notReady(3) and createAndWait(5) states need 2685 not be supported. Write access is not required." 2687 OBJECT mplsTunnelHopStorageType 2688 SYNTAX INTEGER { other(1) } 2689 MIN-ACCESS read-only 2690 DESCRIPTION 2691 "Only other (1) needs to be supported." 2693 -- mplsTunnelResourceTable 2695 OBJECT mplsTunnelResourceMaxRate 2696 MIN-ACCESS read-only 2697 DESCRIPTION 2698 "Write access is not required." 2700 OBJECT mplsTunnelResourceMeanRate 2701 MIN-ACCESS read-only 2702 DESCRIPTION 2703 "Write access is not required." 2705 OBJECT mplsTunnelResourceMaxBurstSize 2706 MIN-ACCESS read-only 2707 DESCRIPTION 2708 "Write access is not required." 2710 OBJECT mplsTunnelResourceMeanBurstSize 2711 MIN-ACCESS read-only 2712 DESCRIPTION 2713 "Write access is not required." 2715 OBJECT mplsTunnelResourceExcessBurstSize 2716 MIN-ACCESS read-only 2717 DESCRIPTION 2718 "Write access is not required." 2720 OBJECT mplsTunnelResourceFrequency 2721 MIN-ACCESS read-only 2722 DESCRIPTION 2723 "Write access is not required." 2725 OBJECT mplsTunnelResourceWeight 2726 MIN-ACCESS read-only 2727 DESCRIPTION 2728 "Write access is not required." 2730 OBJECT mplsTunnelResourceRowStatus 2731 SYNTAX INTEGER { 2732 active(1), 2733 notInService(2), 2734 createAndGo(4), 2735 destroy(6) 2736 } 2737 MIN-ACCESS read-only 2738 DESCRIPTION 2739 "The notReady(3) and createAndWait(5) states need 2740 not be supported. Write access is not required." 2742 OBJECT mplsTunnelResourceStorageType 2743 SYNTAX INTEGER { other(1) } 2744 MIN-ACCESS read-only 2745 DESCRIPTION 2746 "Only other (1) needs to be supported." 2748 -- mplsTunnelPerfTable 2750 OBJECT mplsTunnelPerfPackets 2751 MIN-ACCESS read-only 2752 DESCRIPTION 2753 "Write access is not required." 2755 OBJECT mplsTunnelPerfHCPackets 2756 MIN-ACCESS read-only 2757 DESCRIPTION 2758 "Write access is not required." 2760 OBJECT mplsTunnelPerfErrors 2761 MIN-ACCESS read-only 2762 DESCRIPTION 2763 "Write access is not required." 2765 OBJECT mplsTunnelPerfBytes 2766 MIN-ACCESS read-only 2767 DESCRIPTION 2768 "Write access is not required." 2770 OBJECT mplsTunnelPerfHCBytes 2771 MIN-ACCESS read-only 2772 DESCRIPTION 2773 "Write access is not required." 2775 ::= { mplsTeCompliances 1 } 2777 -- Units of conformance. 2779 mplsTunnelGroup OBJECT-GROUP 2780 OBJECTS { 2781 mplsTunnelIndexNext, 2782 mplsTunnelName, 2783 mplsTunnelDescr, 2784 mplsTunnelOwner, 2785 mplsTunnelXCPointer, 2786 mplsTunnelIfIndex, 2787 mplsTunnelHopTableIndex, 2788 mplsTunnelARHopTableIndex, 2789 mplsTunnelCHopTableIndex, 2790 mplsTunnelAdminStatus, 2791 mplsTunnelOperStatus, 2792 mplsTunnelRowStatus, 2793 mplsTunnelTrapEnable, 2794 mplsTunnelStorageType, 2795 mplsTunnelConfigured, 2796 mplsTunnelActive, 2797 mplsTunnelPrimaryInstance, 2798 mplsTunnelPrimaryTimeUp, 2799 mplsTunnelPathChanges, 2800 mplsTunnelLastPathChange, 2801 mplsTunnelCreationTime, 2802 mplsTunnelStateTransitions, 2803 mplsTunnelEgressLSRId, 2804 mplsTunnelIncludeAnyAffinity, 2805 mplsTunnelIncludeAllAffinity, 2806 mplsTunnelExcludeAllAffinity, 2807 mplsTunnelPerfPackets, 2808 mplsTunnelPerfHCPackets, 2809 mplsTunnelPerfErrors, 2810 mplsTunnelPerfBytes, 2811 mplsTunnelPerfHCBytes, 2812 mplsTunnelResourcePointer, 2813 mplsTunnelInstancePriority, 2814 mplsTunnelPathInUse, 2815 mplsTunnelRole, 2816 mplsTunnelTotalUpTime, 2817 mplsTunnelInstanceUpTime 2818 } 2819 STATUS current 2820 DESCRIPTION 2821 "Necessary, but not sufficient, set of objects to 2822 implement tunnels. In addition, depending on the 2823 type of the tunnels supported (for example, 2824 manually configured or signaled, persistent or non- 2825 persistent, etc.), the following other groups 2826 defined below are mandatory: mplsTunnelManualGroup 2827 and/or mplsTunnelSignaledGroup, 2828 mplsTunnelIsNotIntfcGroup and/or 2829 mplsTunnelIsIntfcGroup." 2830 ::= { mplsTeGroups 1 } 2832 mplsTunnelManualGroup OBJECT-GROUP 2833 OBJECTS { mplsTunnelSignallingProto } 2834 STATUS current 2835 DESCRIPTION 2836 "Object(s) needed to implement manually configured 2837 tunnels." 2838 ::= { mplsTeGroups 2 } 2840 mplsTunnelSignaledGroup OBJECT-GROUP 2841 OBJECTS { 2842 mplsTunnelSetupPrio, 2843 mplsTunnelHoldingPrio, 2844 mplsTunnelSignallingProto, 2845 mplsTunnelLocalProtectInUse, 2846 mplsTunnelSessionAttributes, 2847 mplsTunnelHopListIndexNext, 2848 mplsTunnelHopAddrType, 2849 mplsTunnelHopIpv4Addr, 2850 mplsTunnelHopIpv4PrefixLen, 2851 mplsTunnelHopIpv6Addr, 2852 mplsTunnelHopIpv6PrefixLen, 2853 mplsTunnelHopAsNumber, 2854 mplsTunnelHopLspId, 2855 mplsTunnelHopType, 2856 mplsTunnelHopIncludeExclude, 2857 mplsTunnelHopPathOptionName, 2858 mplsTunnelHopEntryPathComp, 2859 mplsTunnelHopRowStatus, 2860 mplsTunnelHopStorageType 2861 } 2862 STATUS current 2863 DESCRIPTION 2864 "Object needed to implement signaled tunnels." 2865 ::= { mplsTeGroups 3 } 2867 mplsTunnelScalarGroup OBJECT-GROUP 2868 OBJECTS { 2869 mplsTunnelConfigured, 2870 mplsTunnelActive, 2871 mplsTunnelTEDistProto, 2872 mplsTunnelMaxHops 2873 } 2874 STATUS current 2875 DESCRIPTION 2876 "Scalar object needed to implement MPLS tunnels." 2877 ::= { mplsTeGroups 4 } 2879 mplsTunnelIsIntfcGroup OBJECT-GROUP 2880 OBJECTS { mplsTunnelIsIf } 2881 STATUS current 2882 DESCRIPTION 2883 "Objects needed to implement tunnels that are 2884 interfaces." 2885 ::= { mplsTeGroups 5 } 2887 mplsTunnelIsNotIntfcGroup OBJECT-GROUP 2888 OBJECTS { mplsTunnelIsIf } 2889 STATUS current 2890 DESCRIPTION 2891 "Objects needed to implement tunnels that are not 2892 interfaces." 2893 ::= { mplsTeGroups 6 } 2895 mplsTunnelOptionalGroup OBJECT-GROUP 2896 OBJECTS { 2897 mplsTunnelResourceIndexNext, 2898 mplsTunnelResourceMaxRate, 2899 mplsTunnelResourceMeanRate, 2900 mplsTunnelResourceMaxBurstSize, 2901 mplsTunnelResourceMeanBurstSize, 2902 mplsTunnelResourceExcessBurstSize, 2903 mplsTunnelResourceFrequency, 2904 mplsTunnelResourceWeight, 2905 mplsTunnelResourceRowStatus, 2906 mplsTunnelResourceStorageType, 2907 mplsTunnelARHopAddrType, 2908 mplsTunnelARHopIpv4Addr, 2909 mplsTunnelARHopIpv4PrefixLen, 2910 mplsTunnelARHopIpv6Addr, 2911 mplsTunnelARHopIpv6PrefixLen, 2912 mplsTunnelARHopAsNumber, 2913 mplsTunnelCHopAddrType, 2914 mplsTunnelCHopIpv4Addr, 2915 mplsTunnelCHopIpv4PrefixLen, 2916 mplsTunnelCHopIpv6Addr, 2917 mplsTunnelCHopIpv6PrefixLen, 2918 mplsTunnelCHopAsNumber, 2919 mplsTunnelCHopType 2920 } 2921 STATUS current 2922 DESCRIPTION 2923 "The objects in this group are optional." 2924 ::= { mplsTeGroups 7 } 2926 mplsTunnelCRLDPResOptionalGroup OBJECT-GROUP 2927 OBJECTS { 2928 mplsTunnelCRLDPResMeanBurstSize, 2929 mplsTunnelCRLDPResExcessBurstSize, 2930 mplsTunnelCRLDPResFrequency, 2931 mplsTunnelCRLDPResWeight, 2932 mplsTunnelCRLDPResFlags, 2933 mplsTunnelCRLDPResRowStatus, 2934 mplsTunnelCRLDPResStorageType 2935 } 2936 STATUS current 2937 DESCRIPTION 2938 "Set of objects implemented for resources applicable 2939 for tunnels signaled using CR-LDP." 2940 ::= { mplsTeGroups 8 } 2942 mplsTeNotificationGroup NOTIFICATION-GROUP 2943 NOTIFICATIONS { 2944 mplsTunnelUp, 2945 mplsTunnelDown, 2946 mplsTunnelRerouted, 2947 mplsTunnelReoptimized 2948 } 2949 STATUS current 2950 DESCRIPTION 2951 "Set of notifications implemented in this module. 2952 None is mandatory." 2953 ::= { mplsTeGroups 9 } 2955 -- End of MPLS-TE-MIB 2956 END 2958 11. Security Considerations 2960 There are a number of management objects defined in this 2961 MIB that have a MAX-ACCESS clause of read-write and/or 2962 read-create. Such objects may be considered sensitive or 2963 vulnerable in some network environments. The support for 2964 SET operations in a non-secure environment without proper 2965 protection can have a negative effect on network 2966 operations. 2968 It is thus important to control even GET access to these 2969 objects and possibly to even encrypt the values of these 2970 object when sending them over the network via SNMP. Not 2971 all versions of SNMP provide features for such a secure 2972 environment. 2974 SNMPv1 by itself is not a secure environment. Even if the 2975 network itself is secure (for example by using IPSec 2976 [RFC2401]), there is no control as to who on the secure 2977 network is allowed to access and GET/SET 2978 (read/change/create/delete) the objects in this MIB. It is 2979 recommended that the implementers consider the security 2980 features as provided by the SNMPv3 framework. 2981 Specifically, the use of the User-based Security Model 2982 [RFC2574] and the View- based Access Control [RFC2575] is 2983 recommended. It is then a customer/user responsibility to 2984 ensure that the SNMP entity giving access to an instance 2985 of this MIB, is properly configured to give access to the 2986 objects only to those principals (users) that have 2987 legitimate rights to indeed GET or SET 2988 (change/create/delete) them. 2990 12. Acknowledgments 2992 We wish to thank Adrian Farrel, Eric Gray, Joan Cucchiara, 2993 Patrick Kerharo, Paul Langille and Mike Piecuch for their 2994 comments on this draft. 2996 13. References 2998 [Assigned] Reynolds, J., and J. Postel, "Assigned 2999 Numbers", RFC 1700, October 1994. See also: 3000 http://www.isi.edu/in- 3001 notes/iana/assignments/smi-numbers 3003 [TCMIB] Nadeau, T., Cucchiara, J., Srinivasan, C, 3004 Viswanathan, A. and H. Sjostrand, 3005 "Definition of Textual Conventions and 3006 OBJECT-IDENTITIES for Multi-Protocol Label 3007 Switching (MPLS) Management", Internet Draft 3008 , August 3009 2001. 3011 [LSRMIB] Srinivasan, C., Viswanathan, A. and T. 3012 Nadeau, "MPLS Label Switch Router Management 3013 Information Base Using SMIv2", Internet 3014 Draft , 3015 January 2001. 3017 [RSVPTE] Awaduche, D., Berger, L., Der-Haw, G., Li, 3018 T., Swallow, G., and V. Srinivasan, 3019 "Extensions to RSVP for LSP Tunnels", 3020 Internet Draft , February 2001. 3023 [CRLDP] B. Jamoussi (Editor), "Constraint-Based LSP 3024 Setup using LDP", Internet Draft , February 2001. 3027 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 3028 Identification of Management Information for 3029 TCP/IP-based Internets", RFC 1155, May 1990. 3031 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. 3032 Davin, "Simple Network Management Protocol", 3033 RFC 1157, May 1990. 3035 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB 3036 Definitions", RFC 1212, March 1991. 3038 [RFC1215] M. Rose, "A Convention for Defining Traps 3039 for use with the SNMP", RFC 1215, March 3040 1991. 3042 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. 3043 Waldbusser, "Introduction to Community-based 3044 SNMPv2", RFC 1901, January 1996. 3046 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. 3047 Waldbusser, "Protocol Operations for Version 3048 2 of the Simple Network Management Protocol 3049 (SNMPv2)", RFC 1905, January 1996. 3051 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. 3052 Waldbusser, "Transport Mappings for Version 3053 2 of the Simple Network Management Protocol 3054 (SNMPv2)", RFC 1906, January 1996. 3056 [RFC2026] S. Bradner, "The Internet Standards Process 3057 -- Revision 3", RFC 2026, October 1996. 3059 [RFC2233] McCloghrie, K. and F. Kastenholtz, "The 3060 Interface Group MIB Using SMIv2", RFC 2233, 3061 November 1997. 3063 [RFC2401] Kent, S., and Atkinson, R., "Security 3064 Architecture for the Internet Protocol", RFC 3065 2401, November 1998. 3067 [RFC2570] Case, J., Mundy, R., Partain, D., and B. 3068 Stewart, "Introduction to Version 3 of the 3069 Internet-standard Network Management 3070 Framework", RFC 2570, April 1999. 3072 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, 3073 "An Architecture for Describing SNMP 3074 Management Frameworks", RFC 2571, April 3075 1999. 3077 [RFC2572] Case, J., Harrington D., Presuhn R., and B. 3078 Wijnen, "Message Processing and Dispatching 3079 for the Simple Network Management Protocol 3080 (SNMP)", RFC 2572, April 1999. 3082 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 3083 Applications", RFC 2573, April 1999. 3085 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based 3086 Security Model (USM) for version 3 of the 3087 Simple Network Management Protocol 3088 (SNMPv3)", RFC 2574, April 1999. 3090 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, 3091 "View-based Access Control Model (VACM) for 3092 the Simple Network Management Protocol 3093 (SNMP)", RFC 2575, April 1999. 3095 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, 3096 J., Case, J., Rose, M., and S. Waldbusser, 3097 "Structure of Management Information Version 3098 2 (SMIv2)", STD 58, RFC 2578, April 1999. 3100 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, 3101 J., Case, J., Rose, M., and S. Waldbusser, 3102 "Textual Conventions for SMIv2", STD 58, RFC 3103 2579, April 1999. 3105 [RFC2702] Awduche, D., Malcolm, J., Agogbua, J., 3106 O'Dell, M., and J. McManus, "Requirements 3107 for Traffic Engineering Over MPLS", RFC 3108 2702, September 1999. 3110 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, 3111 J., Case, J., Rose, M., and S. Waldbusser, 3112 "Conformance Statements for SMIv2", STD 58, 3113 RFC 2580, April 1999. 3115 [RFC2851] Daniele, M., Haberman, B., Routhier, S., and 3116 J. Schoenwaelder, "Textual Conventions for 3117 Internet Network Addresses", RFC 2851, June 3118 2000. 3120 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 3121 "Multiprotocol Label Switching 3122 Architecture", RFC 3031, January 2001. 3124 14. Authors' Addresses 3126 Cheenu Srinivasan 3127 Alphion Corp. 3128 4 Industrial Way West 3129 Eatontown, NJ 07724 3130 Phone: +1-732-676-7066 3131 Email: cheenu@alphion.com 3133 Arun Viswanathan 3134 Force10 Networks, Inc. 3135 1440 McCarthy Blvd 3136 Milpitas, CA 95035 3137 Phone: +1-408-571-3516 3138 Email: arun@force10networks.com 3140 Thomas D. Nadeau 3141 Cisco Systems, Inc. 3142 300 Apollo Drive 3143 Chelmsford, MA 01824 3144 Phone: +1-978-244-3051 3145 Email: tnadeau@cisco.com 3147 15. Full Copyright Statement 3149 Copyright (C) The Internet Society (2001). All Rights 3150 Reserved. 3152 This document and translations of it may be copied and 3153 furnished to others, and derivative works that comment on 3154 or otherwise explain it or assist in its implementation may 3155 be prepared, copied, published and distributed, in whole or 3156 in part, without restriction of any kind, provided that the 3157 above copyright notice and this paragraph are included on 3158 all such copies and derivative works. However, this 3159 document itself may not be modified in any way, such as by 3160 removing the copyright notice or references to the Internet 3161 Society or other Internet organizations, except as needed 3162 for the purpose of developing Internet standards in which 3163 case the procedures for copyrights defined in the Internet 3164 Standards process must be followed, or as required to 3165 translate it into languages other than English. 3167 The limited permissions granted above are perpetual and 3168 will not be revoked by the Internet Society or its 3169 successors or assigns. This document and the information 3170 contained herein is provided on an "AS IS" basis and THE 3171 INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE 3172 DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 3173 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 3174 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 3175 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 3176 PURPOSE.