idnits 2.17.1 draft-ietf-mpls-te-mib-04.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: ---------------------------------------------------------------------------- ** The document is more than 15 pages and seems to lack a Table of Contents. == There are 4 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 ([MPLSArch], [MPLSFW]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 2 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 1582: '...then this object MAY contain the new p...' Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 313 has weird spacing: '... tunnel is do...' -- 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 (July 14, 2000) is 8680 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'SNMPv1MIBDef' is mentioned on line 95, but not defined == Unused Reference: 'LblStk' is defined on line 2012, but no explicit reference was found in the text == Unused Reference: 'Assigned' is defined on line 2028, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'MPLSArch' -- Possible downref: Non-RFC (?) normative reference: ref. 'MPLSFW' -- Possible downref: Non-RFC (?) normative reference: ref. 'LSRMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'LblStk' -- Possible downref: Non-RFC (?) normative reference: ref. 'RSVPTun' -- Possible downref: Non-RFC (?) normative reference: ref. 'CR-LDP' ** Obsolete normative reference: RFC 1700 (ref. 'Assigned') (Obsoleted by RFC 3232) ** Obsolete normative reference: RFC 2271 (ref. 'SNMPArch') (Obsoleted by RFC 2571) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. 'SNMPv1Traps') ** Obsolete normative reference: RFC 1902 (ref. 'SMIv2') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. 'SNMPv2TC') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. 'SNMPv2Conf') (Obsoleted by RFC 2580) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. 'SNMPv1') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. 'SNMPv2c') ** Obsolete normative reference: RFC 1906 (ref. 'SNMPv2TM') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2272 (ref. 'SNMPv3MP') (Obsoleted by RFC 2572) ** Obsolete normative reference: RFC 2574 (ref. 'SNMPv3USM') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. 'SNMPv2PO') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2273 (ref. 'SNMPv3App') (Obsoleted by RFC 2573) ** Obsolete normative reference: RFC 2575 (ref. 'SNMPv3VACM') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2401 (ref. 'IPSEC') (Obsoleted by RFC 4301) ** Obsolete normative reference: RFC 2233 (ref. 'IFMIB') (Obsoleted by RFC 2863) Summary: 22 errors (**), 0 flaws (~~), 7 warnings (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Cheenu Srinivasan 3 Internet Draft Tachion Networks, Inc. 4 Expires: January 2001 5 Arun Viswanathan 6 Force10 Networks, Inc. 8 Thomas D. Nadeau 9 Cisco Systems, Inc. 11 July 14, 2000 13 MPLS Traffic Engineering Management Information Base Using 14 SMIv2 16 draft-ietf-mpls-te-mib-04.txt 18 Status of this Memo 20 This document is an Internet-Draft and is in full 21 conformance with all provisions of Section 10 of 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 Abstract 42 This memo defines an experimental portion of the Management 43 Information Base (MIB) for use with network management 44 protocols in the Internet community. In particular, it 45 describes managed objects for Multi-Protocol Label 46 Switching (MPLS) [MPLSArch] [MPLSFW] based traffic 47 engineering. 49 1. Introduction 51 This memo defines an experimental portion of the Management 52 Information Base (MIB) for use with network management 53 protocols in the Internet community. In particular, it 54 describes managed objects for modeling a Multi-Protocol 55 Label Switching (MPLS) [MPLSArch][MPLSFW] based traffic 56 engineering. This MIB should be used in conjunction with 57 the companion document [LSRMIB] for MPLS based traffic 58 engineering configuration and management. 60 Comments should be made directly to the MPLS mailing list 61 at mpls@uu.net. 63 This memo does not, in its draft form, specify a standard 64 for the Internet community. 66 2. Terminology 68 This document uses terminology from the MPLS architecture 69 document [MPLSArch] and MPLS Label Switch Router MIB 70 [LSRMIB]. Some frequently used terms are described next. 72 An explicitly routed LSP (ERLSP) is referred to as an MPLS 73 tunnel. It consists of one in-segment and/or one out- 74 segment at the ingress/egress LSRs, each segment being 75 associated with one MPLS interface. These are also 76 referred to as tunnel segments. Additionally, at an 77 intermediate LSR, we model a connection as consisting of 78 one or more in-segments and/or one or more out-segments. 79 The binding or interconnection between in-segments and out- 80 segments in performed using a cross-connect. These objects 81 are defined in the MPLS Label Switch Router MIB [LSRMIB]. 83 3. The SNMP Management Framework 85 The SNMP Management Framework presently consists of five 86 major components: 88 - An overall architecture, described in RFC 2271 89 [SNMPArch]. 91 - Mechanisms for describing and naming objects and events 92 for the purpose of management. The first version of 93 this Structure of Management Information (SMI) is 94 called SMIv1 and described in RFC 1155 [SMIv1], RFC 95 1212 [SNMPv1MIBDef] and RFC 1215 [SNMPv1Traps]. The 96 second version, called SMIv2, is described in RFC 1902 97 [SMIv2], RFC 1903 [SNMPv2TC] and RFC 1904 [SNMPv2Conf]. 99 - Message protocols for transferring management 100 information. The first version of the SNMP message 101 protocol is called SNMPv1 and described in RFC 1157 102 [SNMPv1]. A second version of the SNMP message 103 protocol, which is not an Internet standards track 104 protocol, is called SNMPv2c and described in RFC 1901 105 [SNMPv2c] and RFC 1906 [SNMPv2TM]. The third version 106 of the message protocol is called SNMPv3 and described 107 in RFC 1906 [SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC 108 2574 [SNMPv3USM]. 110 - Protocol operations for accessing management 111 information. The first set of protocol operations and 112 associated PDU formats is described in RFC 1157 113 [SNMPv1]. A second set of protocol operations and 114 associated PDU formats is described in RFC 1905 115 [SNMPv2PO]. 117 - A set of fundamental applications described in RFC 2273 118 [SNMPv3App] and the view-based access control mechanism 119 described in RFC 2575 [SNMPv3VACM]. 121 Managed objects are accessed via a virtual information 122 store, termed the Management Information Base or MIB. 123 Objects in the MIB are defined using the mechanisms defined 124 in the SMI. This memo specifies a MIB module that is 125 compliant to the SMIv2. A MIB conforming to the SMIv1 can 126 be produced through the appropriate translations. The 127 resulting translated MIB must be semantically equivalent, 128 except where objects or events are omitted because no 129 translation is possible (use of Counter64). Some machine- 130 readable information in SMIv2 will be converted into 131 textual descriptions in SMIv1 during the translation 132 process. However, this loss of machine-readable 133 information is not considered to change the semantics of 134 the MIB. 136 3.1. Object Definitions 138 Managed objects are accessed via a virtual information 139 store, termed the Management Information Base or MIB. 140 Objects in the MIB are defined using the subset of Abstract 141 Syntax Notation One (ASN.1) defined in the SMI. In 142 particular, each object type is named by an OBJECT 143 IDENTIFIER, an administratively assigned name. The object 144 type together with an object instance serves to uniquely 145 identify a specific instantiation of the object. For human 146 convenience, we often use a textual string, termed the 147 descriptor, to also refer to the object type. 149 4. Feature List 151 The MPLS traffic engineering MIB is designed to satisfy the 152 following requirements and constraints. 154 - The MIB supports configuration of point-to-point 155 unidirectional tunnels. 157 - MPLS tunnels need not be interfaces, but it is possible 158 to configure a tunnel as an interface. 160 - The MIB supports manually configured MPLS tunnels as 161 well as those set up via any MPLS signaling protocol. 163 - The MIB supports persistent as well as non-persistent 164 tunnels. 166 5. Outline 168 Traffic engineering support for MPLS tunnels requires the 169 following configuration. 171 - Setting up MPLS tunnels along with appropriate 172 configuration parameters. 174 - Configuring tunnel loose and strict source routed hops. 176 These actions may need to be accompanied with corresponding 177 actions using [LSRMIB] to establish and configure tunnel 178 segments, if this is done manually. Also, the in-segment 179 and out-segment performance tables, mplsInSegmentPerfTable 180 and mplsOutSegmentPerfTable [LSRMIB], should be used to 181 determine performance of the tunnels and tunnel segments. 183 5.1. Summary of Traffic Engineering MIB 185 The MIB objects for performing these actions consist of the 186 following tables. 188 - Tunnel table (mplsTunnelTable) for setting up MPLS 189 tunnels. 191 - Resource table (mplsTunnelResourceTable) for setting up 192 the tunnel resources. 194 - Tunnel hop table (mplsTunnelHopTable) for configuring 195 strict and loose source routed MPLS tunnels hops. 197 When a tunnel is signaled via a MPLS signaling protocol, 198 the mplsTunnelARHopTable gives the actual list of hops 199 traversed by the tunnel as reported by the signaling 200 protocol. These tables are described in the subsequent 201 sections. 203 6. Brief Description of MIB Objects 205 The objects described in this section support the 206 functionality described in documents [RSVPTun][CR-LDP]. 207 The tables support both manually configured and signaled 208 tunnels. 210 6.1. mplsTunnelTable 212 The mplsTunnelTable allows new MPLS tunnels to be created 213 between an MPLS LSR and a remote endpoint, and existing 214 tunnels to be reconfigured or removed. Note that we only 215 support point-to-point tunnel segments, although multi- 216 point-to-point and point-to-multi-point connections are 217 supported by an LSR acting as a cross-connect. Each MPLS 218 tunnel can thus have one out-segment originating at an LSR 219 and/or one in-segment terminating at that LSR. 221 mplsTunnelTable does not define the in and out segments 222 forming the tunnel. Instead, these are defined by creating 223 rows in the in-segment and out-segment tables, defining 224 relationships in the cross-connect table and referring to 225 these rows in the mplsTunnelTable using a cross-connect 226 index, mplsTunnelXCID. These segment and cross-connect 227 related objects are defined in [LSRMIB]. 229 6.2. mplsTunnelResourceTable 231 mplsTunnelResourceTable is used to indicate the resources 232 required for a tunnel. Multiple tunnels may share the same 233 resource by pointing to the same entry in this table. 234 Tunnel that do not share resource must point to separate 235 entries in this table. 237 6.3. mplsTunnelHopTable 239 mplsTunnelHopTable is used to indicate the hops, strict or 240 loose, for an MPLS tunnel defined in mplsTunnelTable, when 241 it is established via signaling. Multiple tunnels may 242 share the same hops by pointing to the same entry in this 243 table. Each row also has a secondary index, 244 mplsTunnelHopIndex, corresponding to the next hop of this 245 tunnel. The scalar mplsTunnelMaxHops indicates the maximum 246 number of hops that can be specified on each tunnel 247 supported by this LSR. 249 6.4. mplsTunnelARHopTable 251 mplsTunnelARHopTable is used to indicate the actual hops 252 traversed by a tunnel as reported by the MPLS signaling 253 protocol after the tunnel is setup. The support of this 254 table is optional since not all MPLS signaling protocol may 255 support this feature. 257 7. Application of the Interface Group to MPLS Tunnels 259 The Interfaces Group of MIB II defines generic managed 260 objects for managing interfaces. This memo contains the 261 media-specific extensions to the Interfaces Group for 262 managing MPLS Tunnels as logical interfaces. 264 This memo assumes the interpretation of the Interfaces 265 Group to be in accordance with [IFMIB] which states that 266 the interfaces table (ifTable) contains information on the 267 managed resource's interfaces and that each sub-layer below 268 the internetwork layer of a network interface is considered 269 an interface. Thus, the MPLS interface is represented as 270 an entry in the ifTable. The interrelation of entries in 271 the ifTable is defined by Interfaces Stack Group defined in 272 [IFMIB]. 274 When using MPLS Tunnels as interfaces, the interface stack 275 table might appear as follows: 277 +------------------------------------------+ 278 | MPLS-Tunnel-interface ifType = mpls(150) | 279 +------------------------------------------+ 280 | MPLS-interface ifType = mpls(166) | 281 +------------------------------------------+ 282 | Underlying Layer | 283 +------------------------------------------+ 285 In the above diagram, "Underlying Layer" refers to the 286 ifIndex of any interface type, which has been defined for 287 MPLS interworking. Examples include ATM, Frame Relay, 288 Ethernet, etc. 290 7.1. Support of the MPLS Tunnel Interface by ifTable 292 Some specific interpretations of ifTable for those MPLS 293 tunnels represented as interfaces follow: 295 Object Use for the MPLS tunnel. 297 ifIndex Each MPLS tunnel is represented by an 298 ifEntry. 300 ifDescr Description of the MPLS tunnel. 302 ifType The value that is allocated for MPLS 303 tunnel is 150. 305 ifSpeed The total bandwidth in bits per second 306 for use by the MPLS tunnel. 308 ifPhysAddress Unused. 310 ifAdminStatus See [IFMIB]. 312 ifOperStatus Assumes the value down(2) if the MPLS 313 tunnel is down. 315 ifLastChange See [IFMIB]. 317 ifInOctets The number of octets received over the 318 MPLS tunnel. 320 ifOutOctets The number of octets transmitted over 321 the MPLS tunnel. 323 ifInErrors The number of labeled packets dropped 324 due to uncorrectable errors. 326 ifInUnknownProtos The number of received packets 327 discarded during packet header 328 validation, including packets with 329 unrecognized label values. 331 ifOutErrors See [IFMIB]. 333 ifName Textual name (unique on this system) of 334 the MPLS tunnel or an octet string of 335 zero length. 337 ifLinkUpDownTrapEnable 338 Default is disabled (2). 340 ifConnectorPresent Set to false (2). 342 ifHighSpeed See [IFMIB]. 344 ifHCInOctets The 64-bit version of ifInOctets; 345 supported if required by the compliance 346 statements in [IFMIB]. 348 ifHCOutOctets The 64-bit version of ifOutOctets; 349 supported if required by the compliance 350 statements in [IFMIB]. 352 ifAlias The non-volatile 'alias' name for the 353 MPLS tunnel as specified by a network 354 manager. 356 8. Example of Tunnel Setup 358 This section contains an example of which MIB objects 359 should be modified if one would like to create a best 360 effort, loosely routed, unidirectional traffic engineered 361 tunnel, which spans two hops of a simple network. Note 362 that these objects should be created on the "head-end" 363 LSR. 365 In mplsTunnelTable: 366 { 367 mplsTunnelIndex = 1, 368 mplsTunnelInstance = 1, 369 mplsTunnelName = "My first tunnel", 370 mplsTunnelDescr = "Here to there", 371 mplsTunnelIsIf = true (1), 372 mplsTunnelIfIndex = 12, 373 mplsTunnelXCPointer = mplsXCIndex.2.0.0.15, 374 mplsTunnelSignallingProto = none (1), 375 mplsTunnelSetupPrio = 0, 376 mplsTunnelHoldingPrio = 0, 377 mplsTunnelSessionAttributes = 0, 378 mplsTunnelOwner = snmp (1), 379 mplsTunnelLocalProtectInUse = false (0), 380 mplsTunnelResourcePointer = mplsTunnelResourceIndex.5, 381 mplsTunnelInstancePriority = 1, 382 mplsTunnelHopTableIndex = 1, 383 mplsTunnelRowStatus = createAndGo (4) 384 } 386 In mplsTunnelResourceTable: 387 { 388 mplsTunnelResourceIndex = 5, 389 mplsTunnelResourceMaxRate = 0, 390 mplsTunnelResourceMeanRate = 0, 391 mplsTunnelResourceMaxBurstSize = 0, 392 mplsTunnelResourceRowStatus = createAndGo (4) 393 } 395 The next two instances of mplsTunnelHopEntry are used to 396 denote the hops this tunnel will take across the network. 398 The following denotes the beginning of the network, or the 399 first hop. We have used the fictitious LSR identified by 400 "123.123.125.1" as our example head-end router. 402 In mplsTunnelHopTable: 403 { 404 mplsTunnelHopListIndex = 1, 405 mplsTunnelHopIndex = 1, 406 mplsTunnelHopAddrType = 1, 407 mplsTunnelHopIpv4Addr = 123.123.125.1, 408 mplsTunnelHopIpv4PrefixLen = 9, 409 mplsTunnelHopStrictOrLoose = loose (2), 410 mplsTunnelHopRowStatus = createAndGo (4) 411 } 413 The following denotes the end of the network, or the last 414 hop in our example. We have used the fictitious LSR 415 identified by "123.123.126.1" as our end router. 417 In mplsTunnelHopTable: 419 { 420 mplsTunnelHopListIndex = 1, 421 mplsTunnelHopIndex = 2, 422 mplsTunnelHopAddrType = 1, 423 mplsTunnelHopIpv4Addr = 123.123.126.1, 424 mplsTunnelHopIpv4PrefixLen = 9, 425 mplsTunnelHopStrictOrLoose = loose (2), 426 mplsTunnelHopRowStatus = createAndGo (4) 427 } 429 9. The Use of RowPointer 431 RowPointer is a textual convention used to identify a 432 conceptual row in an SNMP Table by pointing to one of its 433 objects. In this MIB, in mplsTunnelTable, the objects 434 mplsTunnelXCPointer and mplsTunnelResourcePointer are of 435 type RowPointer. The object mplsTunnelXCPointer points to a 436 specific entry in the mplsXCTable [LSRMIB]. This entry in 437 the mplsXCTable is the associated LSP for the given MPLS 438 tunnel entry. The object mplsTunnelResourcePointer points 439 to a specific entry in a traffic parameter table. An 440 example of such a traffic parameter table is 441 mplsTunnelResourceTable. It indicates a specific instance 442 of a traffic parameter entry that is associated with a 443 given MPLS tunnel entry. 445 10. MPLS Traffic Engineering MIB Definitions 447 MPLS-TE-MIB DEFINITIONS ::= BEGIN 449 IMPORTS 450 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 451 experimental, Integer32 452 FROM SNMPv2-SMI 454 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 455 FROM SNMPv2-CONF 457 TEXTUAL-CONVENTION, TruthValue, RowStatus, RowPointer, 458 StorageType, DisplayString, Unsigned32 459 FROM SNMPv2-TC 461 InterfaceIndexOrZero 462 FROM IF-MIB 464 MplsBitRate, MplsBurstSize, MplsLSPID 465 FROM MPLS-LSR-MIB 467 InetAddressIPv4, InetAddressIPv6 468 FROM INET-ADDRESS-MIB; 470 mplsTeMIB MODULE-IDENTITY 471 LAST-UPDATED 472 "200007141200Z" -- 14 July 2000 12:00:00 EST 473 ORGANIZATION 474 "Multiprotocol Label Switching (MPLS) Working Group" 475 CONTACT-INFO 476 " Cheenu Srinivasan 477 Postal: Tachion Networks, Inc. 478 Monmouth Park Corporate Center I 479 Building C, 185 Monmouth Park Highway 480 West Long Branch, NJ 07764 481 Tel: +1-732-542-7750 x1234 482 Email: cheenu@tachion.com 484 Arun Viswanathan 485 Postal: Force10 Networks, Inc. 486 1440 McCarthy Blvd 487 Milpitas, CA 95035 488 Tel: +1-408-571-3516 489 Email: arun@force10networks.com 491 Thomas D. Nadeau 492 Postal: Cisco Systems, Inc. 493 250 Apollo Drive 494 Chelmsford, MA 01824 495 Tel: +1-978-244-3051 496 Email: tnadeau@cisco.com" 497 DESCRIPTION 498 "This MIB module contains managed object definitions 499 for MPLS Traffic Engineering (TE) as defined in: 500 Extensions to RSVP for LSP Tunnels, Awduche et al, 501 Internet Draft , 502 March 1999; Constraint-Based LSP Setup using LDP, B. 503 Jamoussi, Internet Draft , Feb. 1999; Requirements for Traffic 505 Engineering Over MPLS, Awduche, D., J. Malcolm, J., 506 Agogbua, J., O'Dell, M., J. McManus, , 507 September 1999." 509 -- Revision history. 511 REVISION 512 "200007141200Z" -- 14 July 2000 12:00:00 EST 513 DESCRIPTION 514 "Updates based on MPLS WG feedback" 515 REVISION 516 "200005261200Z" -- 26 May 2000 12:00:00 EST 517 DESCRIPTION 518 "Updates based on MPLS WG feedback" 519 REVISION 520 "200003031200Z" -- 3 March 2000 12:00:00 EST 521 DESCRIPTION 522 "Updates based on MPLS WG feedback" 523 REVISION 524 "199907161200Z" -- 16 July 1999 12:00:00 EST 525 DESCRIPTION 526 "Initial draft version." 528 ::= { experimental 95 } 530 -- Textual Conventions. 532 MplsTunnelIndex ::= TEXTUAL-CONVENTION 533 STATUS current 534 DESCRIPTION 535 "Index into mplsTunnelTable." 536 SYNTAX Integer32 (0..65535) 538 -- Top level components of this MIB. 540 -- tables, scalars 541 mplsTeObjects OBJECT IDENTIFIER ::= { mplsTeMIB 1 } 542 -- traps 543 mplsTeNotifications OBJECT IDENTIFIER ::= { mplsTeMIB 2 } 544 mplsTeNotifyPrefix OBJECT IDENTIFIER ::= { mplsTeNotifications 0 } 545 -- conformance 546 mplsTeConformance OBJECT IDENTIFIER ::= { mplsTeMIB 3 } 548 -- MPLS tunnel table. 550 mplsTunnelIndexNext OBJECT-TYPE 551 SYNTAX Integer32 (0..65535) 552 MAX-ACCESS read-only 553 STATUS current 554 DESCRIPTION 555 "This object contains the next appropriate value to 556 be used for mplsTunnelIndex when creating entries in 557 mplsTunnelTable. If the number of unassigned entries 558 is exhausted, a retrival operation will return a 559 value of 0. This object may also return a value of 560 0 when the LSR is unable to accept conceptual row 561 creation, for example, if the mplsTunnelTable is 562 implemented as read-only. To obtain the value of 563 mplsTunnelIndex for a new entry, the manager must 564 first issue a management protocol retrieval 565 operation to obtain the current value of this 566 object. The agent should modify the value to reflect 567 the next unassigned index after each retrieval 568 operation. After a manager retrieves a value the 569 agent will determine through its local policy when 570 this index value will be made available for reuse." 571 ::= { mplsTeObjects 1 } 573 mplsTunnelTable OBJECT-TYPE 574 SYNTAX SEQUENCE OF MplsTunnelEntry 575 MAX-ACCESS not-accessible 576 STATUS current 577 DESCRIPTION 578 "The mplsTunnelTable allows new MPLS tunnels to be 579 created between an LSR and a remote endpoint, and 580 existing tunnels to be reconfigured or removed. 581 Note that only point-to-point tunnel segments are 582 supported, although multi-point-to-point and point- 583 to-multi-point connections are supported by an LSR 584 acting as a cross-connect. Each MPLS tunnel can 585 thus have one out-segment originating at this LSR 586 and/or one in-segment terminating at this LSR." 587 ::= { mplsTeObjects 2 } 589 mplsTunnelEntry OBJECT-TYPE 590 SYNTAX MplsTunnelEntry 591 MAX-ACCESS not-accessible 592 STATUS current 593 DESCRIPTION 594 "An entry in this table represents an MPLS tunnel. 595 An entry can be created by a network administrator 596 or by an SNMP agent as instructed by an MPLS 597 signaling protocol. Whenever a new entry is created 598 with mplsTunnelIsIf set to true(1), then a 599 corresponding entry is created in ifTable as well 600 (see RFC 2233). The ifType of this entry is 601 mplsTunnel(150)." 602 REFERENCE 603 "1. RFC 2233 - The Interfaces Group MIB using SMIv2, 604 McCloghrie, K., and F. Kastenholtz, Nov. 1997 605 2. RFC 1700 - Assigned Numbers, Reynolds, J. and J. 606 Postel, Oct. 1994" 607 INDEX { mplsTunnelIndex, mplsTunnelInstance, 608 mplsTunnelIngressLSRId } 609 ::= { mplsTunnelTable 1 } 611 MplsTunnelEntry ::= SEQUENCE { 612 mplsTunnelIndex MplsTunnelIndex, 613 mplsTunnelInstance MplsTunnelIndex, 614 mplsTunnelIngressLSRId Unsigned32, 615 mplsTunnelName DisplayString, 616 mplsTunnelDescr DisplayString, 617 mplsTunnelIsIf TruthValue, 618 mplsTunnelIfIndex InterfaceIndexOrZero, 619 mplsTunnelXCPointer RowPointer, 620 mplsTunnelSignallingProto INTEGER, 621 mplsTunnelSetupPrio INTEGER, 622 mplsTunnelHoldingPrio INTEGER, 623 mplsTunnelSessionAttributes BITS, 624 mplsTunnelOwner INTEGER, 625 mplsTunnelLocalProtectInUse TruthValue, 626 mplsTunnelResourcePointer RowPointer, 627 mplsTunnelInstancePriority Integer32, 628 mplsTunnelHopTableIndex Integer32, 629 mplsTunnelARHopTableIndex Integer32, 630 mplsTunnelAdminStatus INTEGER, 631 mplsTunnelOperStatus INTEGER, 632 mplsTunnelRowStatus RowStatus, 633 mplsTunnelStorageType StorageType 634 } 636 mplsTunnelIndex OBJECT-TYPE 637 SYNTAX MplsTunnelIndex 638 MAX-ACCESS not-accessible 639 STATUS current 640 DESCRIPTION 641 "Uniquely identifies this row." 642 ::= { mplsTunnelEntry 1 } 644 mplsTunnelInstance OBJECT-TYPE 645 SYNTAX MplsTunnelIndex 646 MAX-ACCESS not-accessible 647 STATUS current 648 DESCRIPTION 649 "Uniquely identifies an instance of a tunnel. It is 650 useful to identify multiple instances of tunnels for 651 the purposes of backup and parallel tunnels." 652 ::= { mplsTunnelEntry 2 } 654 mplsTunnelIngressLSRId OBJECT-TYPE 655 SYNTAX Unsigned32 (0..4294967295) 656 MAX-ACCESS not-accessible 657 STATUS current 658 DESCRIPTION 659 "The purpose of this object is to uniquely identity a 660 tunnel within a network. When the MPLS signalling 661 protoocol is rsvp(2) this value should mimic the 662 Extended Tunnel Id field in the Session object. When 663 the MPLS signalling protoocol is crldp(3) this value 664 should mimic the Ingress LSR Router ID field in the 665 LSPID TLV object." 666 REFERENCE 667 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 668 Awduche et al, Internet Draft , February 2000., 670 2. Constraint-Based LSP Setup using LDP, Jamoussi, 671 Internet Draft , 672 September 1999." 673 ::= { mplsTunnelEntry 3 } 675 mplsTunnelName OBJECT-TYPE 676 SYNTAX DisplayString 677 MAX-ACCESS read-create 678 STATUS current 679 DESCRIPTION 680 "The canonical name assigned to the tunnel. This name 681 can be used to refer to the tunnel on the LSR�s 682 console port. If mplsTunnelIsIf is set to true then 683 the ifName of the interface corresponding to this 684 tunnel should have a value equal to mplsTunnelName. 685 Also see the description of ifName in RFC 2233." 686 REFERENCE 687 "RFC 2233 - The Interfaces Group MIB using SMIv2, 688 McCloghrie, K., and F. Kastenholtz, Nov. 1997" 689 ::= { mplsTunnelEntry 4 } 691 mplsTunnelDescr OBJECT-TYPE 692 SYNTAX DisplayString 693 MAX-ACCESS read-create 694 STATUS current 695 DESCRIPTION 696 "A textual string containing information about the 697 tunnel. If there is no description this object 698 contains a zero length string." 699 ::= { mplsTunnelEntry 5 } 701 mplsTunnelIsIf OBJECT-TYPE 702 SYNTAX TruthValue 703 MAX-ACCESS read-create 704 STATUS current 705 DESCRIPTION 706 "Denotes whether or not this tunnel corresponds to an 707 interface represented in the interfaces group table. 708 Note that if this variable is set to true then the 709 ifName of the interface corresponding to this tunnel 710 should have a value equal to mplsTunnelName. Also 711 see the description of ifName in RFC 2233." 712 REFERENCE 713 "RFC 2233 - The Interfaces Group MIB using SMIv2, 714 McCloghrie, K., and F. Kastenholtz, Nov. 1997" 715 DEFVAL { false } 716 ::= { mplsTunnelEntry 6 } 718 mplsTunnelIfIndex OBJECT-TYPE 719 SYNTAX InterfaceIndexOrZero 720 MAX-ACCESS read-only 721 STATUS current 722 DESCRIPTION 723 "If mplsTunnelIsIf is set to true, then this value 724 contains the LSR-assigned ifIndex which corresponds 725 to an entry in the interfaces table. Otherwise this 726 variable should contain the value of zero indicating 727 that a valid ifIndex was not assigned to this tunnel 728 interface." 729 REFERENCE 730 "RFC 2233 - The Interfaces Group MIB using SMIv2, 731 McCloghrie, K., and F. Kastenholtz, Nov. 1997" 732 ::= { mplsTunnelEntry 7 } 734 mplsTunnelXCPointer OBJECT-TYPE 735 SYNTAX RowPointer 736 MAX-ACCESS read-create 737 STATUS current 738 DESCRIPTION 739 "This variable points to a row in the mplsXCTable. 740 This table identifies the segments that compose this 741 tunnel, their characteristics, and relationships to 742 each other. A value of zeroDotZero indicates that no 743 LSP has been associated with this tunnel yet." 744 REFERENCE 745 "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS 746 Label Switch Router Management Information Base 747 Using SMIv2, Internet Draft , April 26, 2000." 750 ::= { mplsTunnelEntry 8 } 752 mplsTunnelSignallingProto OBJECT-TYPE 753 SYNTAX INTEGER { 754 none(1), 755 rsvp(2), 756 crldp(3), 757 other(4) 758 } 759 MAX-ACCESS read-create 760 STATUS current 761 DESCRIPTION 762 "The signaling protocol, if any, which was used to 763 setup this tunnel." 764 DEFVAL { none } 765 ::= { mplsTunnelEntry 9 } 767 mplsTunnelSetupPrio OBJECT-TYPE 768 SYNTAX INTEGER (0..7) 769 MAX-ACCESS read-create 770 STATUS current 771 DESCRIPTION 772 "Indicates the setup priority of this tunnel." 773 REFERENCE 774 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 775 Awduche et al, Internet Draft , February 2000., 777 2. Constraint-Based LSP Setup using LDP, Jamoussi, 778 Internet Draft , 779 September 1999." 780 ::= { mplsTunnelEntry 10 } 782 mplsTunnelHoldingPrio OBJECT-TYPE 783 SYNTAX INTEGER (0..7) 784 MAX-ACCESS read-create 785 STATUS current 786 DESCRIPTION 787 "Indicates the holding priority for this tunnel." 788 REFERENCE 789 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 790 Awduche et al, Internet Draft , February 2000., 792 2. Constraint-Based LSP Setup using LDP, Jamoussi, 793 Internet Draft , 794 September 1999." 795 ::= { mplsTunnelEntry 11 } 797 mplsTunnelSessionAttributes OBJECT-TYPE 798 SYNTAX BITS { 799 fastReroute (0), 800 mergingPermitted (1), 801 isPersistent (2), 802 localProtectionAvailable (3), 803 isPinned (4) 804 } 805 MAX-ACCESS read-create 806 STATUS current 807 DESCRIPTION 808 "This bitmask indicates optional session values for 809 this tunnel. The following describes these 810 bitfields: 812 fastReroute This flag indicates that the 813 any tunnel hop may choose to 814 reroute this tunnel without 815 tearing it down. 817 mergingPermitted This flag permits transit 818 routers to merge this session 819 with other RSVP sessions for 820 the purpose of reducing 821 resource overhead on 822 downstream transit routers, 823 thereby providing better 824 network scalability. 826 isPersistant Indicates whether this tunnel 827 should be restored 828 automatically after a failure 829 occurs. 831 localProtectionAvailable This flag permits transit 832 routers to use a local repair 833 mechanism which may result in 834 violation of the explicit 835 routing of this tunnel. When a 836 fault is detected on an 837 adjacent downstream link or 838 node, a transit router can 839 reroute traffic for fast 840 service restoration. 842 isPinned This flag indicates whether 843 the loose-routed hops of this 844 tunnel are to be pinned." 845 REFERENCE 846 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 847 Awduche et al, Internet Draft , February 2000." 849 DEFVAL { 0 } 850 ::= { mplsTunnelEntry 12 } 852 mplsTunnelOwner OBJECT-TYPE 853 SYNTAX INTEGER { 854 admin(1), -- represents all management entities 855 rsvp(2), 856 crldp(3), 857 policyAgent(4), 858 other(5) 859 } 860 MAX-ACCESS read-create 861 STATUS current 862 DESCRIPTION 863 "Indicates which protocol created and is responsible 864 for managing this tunnel. Values rsvp(2) and 865 crldp(3) should not be used at the head-end of a 866 MPLS tunnel." 867 ::= { mplsTunnelEntry 13 } 869 mplsTunnelLocalProtectInUse OBJECT-TYPE 870 SYNTAX TruthValue 871 MAX-ACCESS read-create 872 STATUS current 873 DESCRIPTION 874 "Indicates that the local repair mechanism is in use 875 to maintain this tunnel (usually in the face of an 876 outage of the link it was previously routed over)." 877 ::= { mplsTunnelEntry 14 } 879 mplsTunnelResourcePointer OBJECT-TYPE 880 SYNTAX RowPointer 881 MAX-ACCESS read-create 882 STATUS current 883 DESCRIPTION 884 "This variable represents a pointer to the traffic 885 parameter specification for this tunnel. This value 886 may point at an entry in the mplsTunnelResourceEntry 887 to indicate which mplsTunnelResourceEntry is to be 888 assigned to this segment. This value may optionally 889 point at an externally defined traffic parameter 890 specification table. A value of zeroDotZero 891 indicates best-effort treatment. By having the same 892 value of this object, two or more segments can 893 indicate resource sharing." 895 ::= { mplsTunnelEntry 15 } 897 mplsTunnelInstancePriority OBJECT-TYPE 898 SYNTAX Integer32 (0..2147483647) 899 MAX-ACCESS read-create 900 STATUS current 901 DESCRIPTION 902 "This value indicates which priority, in descending 903 order with 0 indicating the lowest priority, within 904 a group of tunnel instances. A group of tunnel 905 instances is defined as a set of tunnels with the 906 same mplsTunnelIndex in this table, but with a 907 different mplsTunnelInstance. Tunnel group 908 priorities are used to denote the priority at which 909 a particular tunnel instance will supercede another. 910 Instances of tunnels containing the same 911 mplsTunnelInstancePriority will be used for load 912 sharing." 913 DEFVAL { 0 } 914 ::= { mplsTunnelEntry 16 } 916 mplsTunnelHopTableIndex OBJECT-TYPE 917 SYNTAX Integer32 (0..2147483647) 918 MAX-ACCESS read-create 919 STATUS current 920 DESCRIPTION 921 "Index into the mplsTunnelHopTable entry that 922 specifies the explicit route hops for this tunnel." 923 ::= { mplsTunnelEntry 17 } 925 mplsTunnelARHopTableIndex OBJECT-TYPE 926 SYNTAX Integer32 (0..2147483647) 927 MAX-ACCESS read-only 928 STATUS current 929 DESCRIPTION 930 "Index into the mplsTunnelARHopTable entry that 931 specifies the actual hops traversed by the tunnel." 932 ::= { mplsTunnelEntry 18 } 934 mplsTunnelAdminStatus OBJECT-TYPE 935 SYNTAX INTEGER { 936 up(1), -- ready to pass packets 937 down(2), 938 testing(3) -- in some test mode 939 } 940 MAX-ACCESS read-create 941 STATUS current 942 DESCRIPTION 943 "Indicates the desired operational status of this 944 tunnel." 945 ::= { mplsTunnelEntry 19 } 947 mplsTunnelOperStatus OBJECT-TYPE 948 SYNTAX INTEGER { 949 up(1), -- ready to pass packets 950 down(2), 951 testing(3), -- in some test mode 952 unknown(4), -- status cannot be determined 953 dormant(5), 954 notPresent(6), -- some component is missing 955 lowerLayerDown(7) -- down due to the state of 956 -- lower layer interfaces 957 } 958 MAX-ACCESS read-only 959 STATUS current 960 DESCRIPTION 961 "Indicates the actual operational status of this 962 tunnel, which is typically but not limited to, a 963 function of the state of individual segments of this 964 tunnel." 965 ::= { mplsTunnelEntry 20 } 967 mplsTunnelRowStatus OBJECT-TYPE 968 SYNTAX RowStatus 969 MAX-ACCESS read-create 970 STATUS current 971 DESCRIPTION 972 "This variable is used to create, modify, and/or 973 delete a row in this table." 974 ::= { mplsTunnelEntry 21 } 976 mplsTunnelStorageType OBJECT-TYPE 977 SYNTAX StorageType 978 MAX-ACCESS read-create 979 STATUS current 980 DESCRIPTION 981 "This variable indicates the storage type for this 982 object." 983 ::= { mplsTunnelEntry 22 } 985 -- End of mplsTunnelTable 987 -- Maximum number of tunnel hops supported. 989 mplsTunnelMaxHops OBJECT-TYPE 990 SYNTAX Integer32 (1..2147483647) 991 MAX-ACCESS read-only 992 STATUS current 993 DESCRIPTION 994 "The maximum number of hops that can be specified for 995 a tunnel on this device." 996 ::= { mplsTeObjects 3 } 998 -- Tunnel hop table. 1000 mplsTunnelHopIndexNext OBJECT-TYPE 1001 SYNTAX Integer32 (0..2147483647) 1002 MAX-ACCESS read-only 1003 STATUS current 1004 DESCRIPTION 1005 "This object contains an appropriate value to be used 1006 for mplsTunnelHopListIndex when creating entries in 1007 the mplsTunnelHopTable. If the number of unassigned 1008 entries is exhausted, a retrival operation will 1009 return a value of 0. This object may also return a 1010 value of 0 when the LSR is unable to accept 1011 conceptual row creation, for example, if the 1012 mplsTunnelHopTable is implemented as read-only. To 1013 obtain the value of mplsTunnelHopListIndex for a new 1014 entry in the mplsTunnelHopTable, the manager issues 1015 a management protocol retrieval operation to obtain 1016 the current value of mplsTunnelHopIndex. After each 1017 retrieval operation, the agent should modify the 1018 value to reflect the next unassigned index. After a 1019 manager retrieves a value the agent will determine 1020 through its local policy when this index value will 1021 be made available for reuse." 1022 ::= { mplsTeObjects 4 } 1024 mplsTunnelHopTable OBJECT-TYPE 1025 SYNTAX SEQUENCE OF MplsTunnelHopEntry 1026 MAX-ACCESS not-accessible 1027 STATUS current 1028 DESCRIPTION 1029 "The mplsTunnelHopTable is used to indicate the hops, 1030 strict or loose, for an MPLS tunnel defined in 1031 mplsTunnelTable, when it is established via 1032 signaling, for the outgoing direction of the tunnel. 1033 Each row in this table is indexed primarily by the 1034 same index, mplsTunnelIndex, as the row of the 1035 corresponding tunnel in mplsTunnelTable. Each row 1036 also has a secondary index mplsTunnelHopIndex 1037 corresponding to the next hop that this row 1038 corresponds to. The first row in the table is the 1039 first hop after the origination point of the tunnel. 1040 In case we want to specify a particular interface on 1041 the originating LSR of an outgoing tunnel by which 1042 we want packets to exit the LSR, we specify this as 1043 the first hop for this tunnel in 1044 mplsTunnelHopTable." 1045 ::= { mplsTeObjects 5 } 1047 mplsTunnelHopEntry OBJECT-TYPE 1048 SYNTAX MplsTunnelHopEntry 1049 MAX-ACCESS not-accessible 1050 STATUS current 1051 DESCRIPTION 1052 "An entry in this table represents a tunnel hop. An 1053 entry is created by a network administrator for 1054 signaled ERLSP set up by an MPLS signaling 1055 protocol." 1056 INDEX { mplsTunnelHopListIndex, mplsTunnelHopIndex } 1057 ::= { mplsTunnelHopTable 1 } 1059 MplsTunnelHopEntry ::= SEQUENCE { 1060 mplsTunnelHopListIndex Integer32, 1061 mplsTunnelHopIndex Integer32, 1062 mplsTunnelHopAddrType INTEGER, 1063 mplsTunnelHopIpv4Addr InetAddressIPv4, 1064 mplsTunnelHopIpv4PrefixLen INTEGER, 1065 mplsTunnelHopIpv6Addr InetAddressIPv6, 1066 mplsTunnelHopIpv6PrefixLen INTEGER, 1067 mplsTunnelHopAsNumber INTEGER, 1068 mplsTunnelHopLspId MplsLSPID, 1069 mplsTunnelHopStrictOrLoose INTEGER, 1070 mplsTunnelHopRowStatus RowStatus, 1071 mplsTunnelHopStorageType StorageType 1072 } 1074 mplsTunnelHopListIndex OBJECT-TYPE 1075 SYNTAX Integer32 (1..2147483647) 1076 MAX-ACCESS not-accessible 1077 STATUS current 1078 DESCRIPTION 1079 "Primary index into this table identifying a 1080 particular explicit route object." 1081 ::= { mplsTunnelHopEntry 1 } 1083 mplsTunnelHopIndex OBJECT-TYPE 1084 SYNTAX Integer32 (1..2147483647) 1085 MAX-ACCESS not-accessible 1086 STATUS current 1087 DESCRIPTION 1088 "Secondary index into this table identifying a 1089 particular hop." 1090 ::= { mplsTunnelHopEntry 2 } 1092 mplsTunnelHopAddrType OBJECT-TYPE 1093 SYNTAX INTEGER { 1094 ipV4(1), 1095 ipV6(2), 1096 asNumber(3), 1097 lspid(4) 1098 } 1099 MAX-ACCESS read-create 1100 STATUS current 1101 DESCRIPTION 1102 "Denotes the address type of this tunnel hop." 1103 DEFVAL { ipV4 } 1104 ::= { mplsTunnelHopEntry 3 } 1106 mplsTunnelHopIpv4Addr OBJECT-TYPE 1107 SYNTAX InetAddressIPv4 1108 MAX-ACCESS read-create 1109 STATUS current 1110 DESCRIPTION 1111 "If mplsTunnelHopAddrType is set to ipV4(1), then 1112 this value will contain the IPv4 address of this 1113 hop. This object is otherwise insignificant and 1114 should contain a value of 0." 1115 ::= { mplsTunnelHopEntry 4 } 1117 mplsTunnelHopIpv4PrefixLen OBJECT-TYPE 1118 SYNTAX INTEGER (1..32) 1119 MAX-ACCESS read-create 1120 STATUS current 1121 DESCRIPTION 1122 "If mplsTunnelHopAddrType is ipV4(1), then the prefix 1123 length for this hop's IPv4 address is contained 1124 herein. This object is otherwise insignificant and 1125 should contain a value of 0." 1126 ::= { mplsTunnelHopEntry 5 } 1128 mplsTunnelHopIpv6Addr OBJECT-TYPE 1129 SYNTAX InetAddressIPv6 1130 MAX-ACCESS read-create 1131 STATUS current 1132 DESCRIPTION 1133 "If the mplsTunnelHopAddrType is set to ipV6(2), then 1134 this variable contains the IPv6 address of this hop. 1135 This object is otherwise insignificant and should 1136 contain a value of 0." 1137 ::= { mplsTunnelHopEntry 6 } 1139 mplsTunnelHopIpv6PrefixLen OBJECT-TYPE 1140 SYNTAX INTEGER (1..128) 1141 MAX-ACCESS read-create 1142 STATUS current 1143 DESCRIPTION 1144 "If mplsTunnelHopAddrType is set to ipV6(2), this 1145 value will contain the prefix length for this hop's 1146 IPv6 address. This object is otherwise insignificant 1147 and should contain a value of 0." 1148 ::= { mplsTunnelHopEntry 7 } 1150 mplsTunnelHopAsNumber OBJECT-TYPE 1151 SYNTAX INTEGER (0..65535) 1152 MAX-ACCESS read-create 1153 STATUS current 1154 DESCRIPTION 1155 "If mplsTunnelHopAddrType is set to asNumber(3), then 1156 this value will contain the AS number of this hop. 1157 This object is otherwise insignificant and should 1158 contain a value of 0 to indicate this fact." 1159 ::= { mplsTunnelHopEntry 8 } 1161 mplsTunnelHopLspId OBJECT-TYPE 1162 SYNTAX MplsLSPID 1163 MAX-ACCESS read-create 1164 STATUS current 1165 DESCRIPTION 1166 "If mplsTunnelHopAddrType is set to lspid(4), then 1167 this value will contain the LSPID of a tunnel of 1168 this hop. The present tuunel being configured is 1169 �tunneled� through this hop (using label stacking). 1170 This object is otherwise insignificant and should 1171 contain a value of 0 to indicate this fact." 1172 ::= { mplsTunnelHopEntry 9 } 1174 mplsTunnelHopStrictOrLoose OBJECT-TYPE 1175 SYNTAX INTEGER { 1176 strict(1), 1177 loose(2) 1178 } 1179 MAX-ACCESS read-create 1180 STATUS current 1181 DESCRIPTION 1182 "Denotes whether this tunnel hop is routed in a 1183 strict or loose fashion." 1184 ::= { mplsTunnelHopEntry 10 } 1186 mplsTunnelHopRowStatus OBJECT-TYPE 1187 SYNTAX RowStatus 1188 MAX-ACCESS read-create 1189 STATUS current 1190 DESCRIPTION 1191 "This variable is used to create, modify, and/or 1192 delete a row in this table." 1193 ::= { mplsTunnelHopEntry 11 } 1195 mplsTunnelHopStorageType OBJECT-TYPE 1196 SYNTAX StorageType 1197 MAX-ACCESS read-create 1198 STATUS current 1199 DESCRIPTION 1200 "This variable indicates the storage type for this 1201 object." 1202 ::= { mplsTunnelHopEntry 12 } 1204 -- End of mplsTunnelHopTable 1206 -- Begin of mplsTunnelResourceTable 1208 mplsTunnelResourceIndexNext OBJECT-TYPE 1209 SYNTAX Integer32 (0..2147483647) 1210 MAX-ACCESS read-only 1211 STATUS current 1212 DESCRIPTION 1213 "This object contains the next appropriate value to 1214 be used for mplsTunnelResourceIndex when creating 1215 entries in the mplsTunnelResourceTable. If the 1216 number of unassigned entries is exhausted, a 1217 retrival operation will return a value of 0. This 1218 object may also return a value of 0 when the LSR is 1219 unable to accept conceptual row creation, for 1220 example, if the mplsTunnelTable is implemented as 1221 read-only. To obtain the mplsTunnelResourceIndex 1222 value for a new entry, the manager must first issue 1223 a management protocol retrieval operation to obtain 1224 the current value of this object. The agent should 1225 modify the value to reflect the next unassigned 1226 index after each retrieval operation. After a 1227 manager retrieves a value the agent will determine 1228 through its local policy when this index value will 1229 be made available for reuse." 1230 ::= { mplsTeObjects 6 } 1232 mplsTunnelResourceTable OBJECT-TYPE 1233 SYNTAX SEQUENCE OF MplsTunnelResourceEntry 1234 MAX-ACCESS not-accessible 1235 STATUS current 1236 DESCRIPTION 1237 "The mplsTunnelResourceTable allows a manager to 1238 specify which resources are desired for an MPLS 1239 tunnel. This table also allows several tunnels to 1240 point to a single entry in this table, implying that 1241 these tunnels should share resources." 1242 ::= { mplsTeObjects 7 } 1244 mplsTunnelResourceEntry OBJECT-TYPE 1245 SYNTAX MplsTunnelResourceEntry 1246 MAX-ACCESS not-accessible 1247 STATUS current 1248 DESCRIPTION 1249 "An entry in this table represents a set of resources 1250 for an MPLS tunnel. An entry can be created by a 1251 network administrator or by an SNMP agent as 1252 instructed by any MPLS signaling protocol." 1253 INDEX { mplsTunnelResourceIndex } 1254 ::= { mplsTunnelResourceTable 1 } 1256 MplsTunnelResourceEntry ::= SEQUENCE { 1257 mplsTunnelResourceIndex Integer32, 1258 mplsTunnelResourceMaxRate MplsBitRate, 1259 mplsTunnelResourceMeanRate MplsBitRate, 1260 mplsTunnelResourceMaxBurstSize MplsBurstSize, 1261 mplsTunnelResourceRowStatus RowStatus, 1262 mplsTunnelResourceStorageType StorageType 1263 } 1265 mplsTunnelResourceIndex OBJECT-TYPE 1266 SYNTAX Integer32 (1..2147483647) 1267 MAX-ACCESS not-accessible 1268 STATUS current 1269 DESCRIPTION 1270 "Uniquely identifies this row." 1271 ::= { mplsTunnelResourceEntry 1 } 1273 mplsTunnelResourceMaxRate OBJECT-TYPE 1274 SYNTAX MplsBitRate 1275 UNITS "bits per second" 1276 MAX-ACCESS read-create 1277 STATUS current 1278 DESCRIPTION 1279 "The maximum rate in bits/second. Note that setting 1280 mplsTunnelResourceMaxRate, 1281 mplsTunnelResourceMeanRate, and 1282 mplsTunnelResourceMaxBurstSize to 0 indicates best- 1283 effort treatment. 1284 This object is copied to an instance of 1285 mplsTSpecMaxRate in mplsTSpecTable the index of 1286 which is copied into the corresponding 1287 mplsInSegmentTSpecIndex." 1288 REFERENCE 1289 "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS 1290 Label Switch Router Management Information Base 1291 Using SMIv2, Internet Draft , April 26, 2000." 1293 ::= { mplsTunnelResourceEntry 2 } 1295 mplsTunnelResourceMeanRate OBJECT-TYPE 1296 SYNTAX MplsBitRate 1297 UNITS "bits per second" 1298 MAX-ACCESS read-create 1299 STATUS current 1300 DESCRIPTION 1301 "This object is copied into an instance of 1302 mplsTSpecMeanRate in the mplsTSpecTable. The index 1303 of this table is then copied into the corresponding 1304 mplsInSegmentTSpecIndex. 1306 When resource allocation is performed as requested 1307 by this TSpec object, it is copied into an entry in 1308 mplsTSpecTable [LSRMIB]: mplsTunnelInMeanRate to 1309 mplsTSpecMeanRate. The mplsTSpecDirection of this 1310 entry is set to �in�(1). The mplsTSpecIndex value 1311 of this entry is copied to mplsInSegmentTSpecIndex 1312 of the corresponding in-segment entry." 1314 REFERENCE 1315 "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS 1316 Label Switch Router Management Information Base 1317 Using SMIv2, Internet Draft , April 26, 2000." 1319 ::= { mplsTunnelResourceEntry 3 } 1321 mplsTunnelResourceMaxBurstSize OBJECT-TYPE 1322 SYNTAX MplsBurstSize 1323 UNITS "bytes" 1324 MAX-ACCESS read-create 1325 STATUS current 1326 DESCRIPTION 1327 "The maximum burst size in bytes. This object is 1328 copied to mplsInSegmentMaxBurstSize of the 1329 corresponding in-segment. 1331 When resource allocation is performed as requested 1332 by this TSpec object, it is copied into an entry in 1333 mplsTSpecTable [LSRMIB]: mplsTunnelInMaxBurstSize to 1334 mplsTSpecMaxBurstSize. The mplsTSpecDirection of 1335 this entry is set to �in�(1). The mplsTSpecIndex 1336 value of this entry is copied to 1337 mplsInSegmentTSpecIndex of the corresponding in- 1338 segment entry." 1339 REFERENCE 1340 "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS 1341 Label Switch Router Management Information Base 1342 Using SMIv2, Internet Draft , April 26, 2000." 1344 ::= { mplsTunnelResourceEntry 4 } 1346 mplsTunnelResourceRowStatus OBJECT-TYPE 1347 SYNTAX RowStatus 1348 MAX-ACCESS read-create 1349 STATUS current 1350 DESCRIPTION 1351 "This variable is used to create, modify, and/or 1352 delete a row in this table." 1353 ::= { mplsTunnelResourceEntry 5 } 1355 mplsTunnelResourceStorageType OBJECT-TYPE 1356 SYNTAX StorageType 1357 MAX-ACCESS read-create 1358 STATUS current 1359 DESCRIPTION 1360 "This variable indicates the storage type for this 1361 object." 1362 ::= { mplsTunnelResourceEntry 6 } 1364 -- End mplsTunnelResourceTable 1366 -- Tunnel Actual Route Hop table. 1368 mplsTunnelARHopTable OBJECT-TYPE 1369 SYNTAX SEQUENCE OF MplsTunnelARHopEntry 1370 MAX-ACCESS not-accessible 1371 STATUS current 1372 DESCRIPTION 1373 "The mplsTunnelARHopTable is used to indicate the 1374 hops, strict or loose, for an MPLS tunnel defined in 1375 mplsTunnelTable, as reported by the MPLS signaling 1376 protocol, for the outgoing direction of the tunnel. 1377 Each row in this table is indexed primarily by the 1378 same indices, mplsTunnelIndex and 1379 mplsTunnelInstance, as the row of the corresponding 1380 tunnel in mplsTunnelTable. Each row also has a 1381 third index mplsTunnelARHopIndex, corresponding to 1382 the next hop that this row corresponds to. The 1383 first row in the table is the first hop after the 1384 origination point of the tunnel. In case we want to 1385 specify a particular interface on the originating 1386 LSR of an outgoing tunnel by which we want packets 1387 to exit the LSR, we specify this as the first hop 1388 for this tunnel in mplsTunnelARHopTable. 1390 Please note that since the information necessary to 1391 build entries within this table are not provided by 1392 some MPLS signaling protocols, implementation of 1393 this table is optional. Furthermore, since the 1394 information in this table is actually provided by 1395 the MPLS signaling protocol after the path has been 1396 set-up, the entries in this table are provided only 1397 for observation, and hence, all variables in this 1398 table are accessible exclusively as read-only." 1399 ::= { mplsTeObjects 8 } 1401 mplsTunnelARHopEntry OBJECT-TYPE 1402 SYNTAX MplsTunnelARHopEntry 1403 MAX-ACCESS not-accessible 1404 STATUS current 1405 DESCRIPTION 1406 "An entry in this table represents a tunnel hop. An 1407 entry is created by a network administrator for 1408 signaled ERLSP set up by an MPLS signaling 1409 protocol." 1410 INDEX { mplsTunnelARHopListIndex, mplsTunnelARHopIndex } 1411 ::= { mplsTunnelARHopTable 1 } 1413 MplsTunnelARHopEntry ::= SEQUENCE { 1414 mplsTunnelARHopListIndex Integer32, 1415 mplsTunnelARHopIndex Integer32, 1416 mplsTunnelARHopAddrType INTEGER, 1417 mplsTunnelARHopIpv4Addr InetAddressIPv4, 1418 mplsTunnelARHopIpv4PrefixLen INTEGER, 1419 mplsTunnelARHopIpv6Addr InetAddressIPv6, 1420 mplsTunnelARHopIpv6PrefixLen INTEGER, 1421 mplsTunnelARHopAsNumber INTEGER, 1422 mplsTunnelARHopStrictOrLoose INTEGER 1423 } 1425 mplsTunnelARHopListIndex OBJECT-TYPE 1426 SYNTAX Integer32 (1..2147483647) 1427 MAX-ACCESS not-accessible 1428 STATUS current 1429 DESCRIPTION 1430 "Primary index into this table identifying a 1431 particular recorded hop list." 1432 ::= { mplsTunnelARHopEntry 1 } 1434 mplsTunnelARHopIndex OBJECT-TYPE 1435 SYNTAX Integer32 (1..2147483647) 1436 MAX-ACCESS not-accessible 1437 STATUS current 1438 DESCRIPTION 1439 "Secondary index into this table identifying the 1440 particular hop." 1441 ::= { mplsTunnelARHopEntry 2 } 1443 mplsTunnelARHopAddrType OBJECT-TYPE 1444 SYNTAX INTEGER { 1445 ipV4(1), 1446 ipV6(2), 1447 asNumber(3) 1448 } 1449 MAX-ACCESS read-only 1450 STATUS current 1451 DESCRIPTION 1452 "Denotes the address type of this tunnel hop." 1453 DEFVAL { ipV4 } 1454 ::= { mplsTunnelARHopEntry 3 } 1456 mplsTunnelARHopIpv4Addr OBJECT-TYPE 1457 SYNTAX InetAddressIPv4 1458 MAX-ACCESS read-only 1459 STATUS current 1460 DESCRIPTION 1461 "If mplsTunnelARHopAddrType is set to ipV4(1), then 1462 this value will contain the IPv4 address of this 1463 hop. This object is otherwise insignificant and 1464 should contain a value of 0." 1465 ::= { mplsTunnelARHopEntry 4 } 1467 mplsTunnelARHopIpv4PrefixLen OBJECT-TYPE 1468 SYNTAX INTEGER (1..32) 1469 MAX-ACCESS read-only 1470 STATUS current 1471 DESCRIPTION 1472 "If mplsTunnelARHopAddrType is ipV4(1), then the 1473 prefix length for this hop's IPv4 address is 1474 contained herein. This object is otherwise 1475 insignificant and should contain a value of 0." 1476 ::= { mplsTunnelARHopEntry 5 } 1478 mplsTunnelARHopIpv6Addr OBJECT-TYPE 1479 SYNTAX InetAddressIPv6 1480 MAX-ACCESS read-only 1481 STATUS current 1482 DESCRIPTION 1483 "If the mplsTunnelARHopAddrType is set to ipV6(2), 1484 then this variable contains the IPv6 address of this 1485 hop. This object is otherwise insignificant and 1486 should contain a value of 0." 1487 ::= { mplsTunnelARHopEntry 6 } 1489 mplsTunnelARHopIpv6PrefixLen OBJECT-TYPE 1490 SYNTAX INTEGER (1..128) 1491 MAX-ACCESS read-only 1492 STATUS current 1493 DESCRIPTION 1494 "If mplsTunnelARHopAddrType is set to ipV6(2), this 1495 value will contain the prefix length for this hop's 1496 IPv6 address. This object is otherwise insignificant 1497 and should contain a value of 0." 1498 ::= { mplsTunnelARHopEntry 7 } 1500 mplsTunnelARHopAsNumber OBJECT-TYPE 1501 SYNTAX INTEGER (0..65535) 1502 MAX-ACCESS read-only 1503 STATUS current 1504 DESCRIPTION 1505 "If mplsTunnelARHopAddrType is set to asNumber(3), 1506 then this value will contain the AS number of this 1507 hop. This object is otherwise insignificant and 1508 should contain a value of 0 to indicate this fact." 1509 ::= { mplsTunnelARHopEntry 8 } 1511 mplsTunnelARHopStrictOrLoose OBJECT-TYPE 1512 SYNTAX INTEGER { 1513 strict(1), 1514 loose(2) 1515 } 1517 MAX-ACCESS read-only 1518 STATUS current 1519 DESCRIPTION 1520 "Denotes whether this is tunnel hop is routed in a 1521 strict or loose fashion." 1522 ::= { mplsTunnelARHopEntry 9 } 1524 -- End of mplsTunnelARHopTable 1526 -- Notifications. 1528 mplsTunnelTrapEnable OBJECT-TYPE 1529 SYNTAX TruthValue 1530 MAX-ACCESS read-write 1531 STATUS current 1532 DESCRIPTION 1533 "If this object is true, then it enables the 1534 generation of mplsTunnelUp and mplsTunnelDown traps, 1535 otherwise these traps are not emitted." 1536 DEFVAL { false } 1537 ::= { mplsTeObjects 9 } 1539 mplsTunnelUp NOTIFICATION-TYPE 1540 OBJECTS { mplsTunnelIndex, 1541 mplsTunnelInstance, 1542 mplsTunnelAdminStatus, 1543 mplsTunnelOperStatus 1544 } 1545 STATUS current 1546 DESCRIPTION 1547 "This notification is generated when a 1548 mplsTunnelOperStatus object for one of the 1549 configured tunnels is about to leave the down state 1550 and transition into some other state (but not into 1551 the notPresent state). This other state is 1552 indicated by the included value of 1553 mplsTunnelOperStatus." 1554 ::= { mplsTeNotifyPrefix 1 } 1556 mplsTunnelDown NOTIFICATION-TYPE 1557 OBJECTS { mplsTunnelIndex, 1558 mplsTunnelInstance, 1559 mplsTunnelAdminStatus, 1560 mplsTunnelOperStatus 1561 } 1562 STATUS current 1563 DESCRIPTION 1564 "This notification is generated when a 1565 mplsTunnelOperStatus object for one of the 1566 configured tunnels is about to enter the down state 1567 from some other state (but not from the notPresent 1568 state). This other state is indicated by the 1569 included value of mplsTunnelOperStatus." 1570 ::= { mplsTeNotifyPrefix 2 } 1572 mplsTunnelRerouted NOTIFICATION-TYPE 1573 OBJECTS { mplsTunnelIndex, 1574 mplsTunnelInstance, 1575 mplsTunnelAdminStatus, 1576 mplsTunnelOperStatus 1577 } 1578 STATUS current 1579 DESCRIPTION 1580 "This notification is generated when a tunnel is 1581 rerouted or re-optimized. If the Actual Path is 1582 used, then this object MAY contain the new path for 1583 this tunnel some time after this trap is issued by 1584 the agent." 1585 ::= { mplsTeNotifyPrefix 3 } 1587 -- End of notifications. 1589 -- Module compliance. 1591 mplsTeGroups 1592 OBJECT IDENTIFIER ::= { mplsTeConformance 1 } 1594 mplsTeCompliances 1595 OBJECT IDENTIFIER ::= { mplsTeConformance 2 } 1597 mplsTeModuleCompliance MODULE-COMPLIANCE 1598 STATUS current 1599 DESCRIPTION 1600 "Compliance statement for agents that support the 1601 MPLS TE MIB." 1602 MODULE -- this module 1604 -- The mandatory group has to be implemented by all 1605 -- LSRs that originate/terminate ESLSPs/tunnels. 1606 -- In addition, depending on the type of tunnels 1607 -- supported, other groups become mandatory as 1608 -- explained below. 1610 MANDATORY-GROUPS { mplsTunnelGroup } 1611 GROUP mplsTunnelManualGroup 1612 DESCRIPTION 1613 "This group is mandatory for devices which support 1614 manual configuration of tunnels, in addition to 1615 mplsTunnelGroup. The following constraints apply: 1616 mplsTunnelSignallingProto should be at least read- 1617 only with a value of none(1)." 1619 GROUP mplsTunnelSignaledGroup 1620 DESCRIPTION 1621 "This group is mandatory for devices which support 1622 signaled tunnel set up, in addition to 1623 mplsTunnelGroup. The following constraints apply: 1624 mplsTunnelSignallingProto should be at least read- 1625 only returning a value of ldp(2), or rsvp(3)." 1627 GROUP mplsTunnelIsNotIntfcGroup 1628 DESCRIPTION 1629 "This group is mandatory for devices which support 1630 tunnels that are not interfaces, in addition to 1631 mplsTunnelGroup. The following constraints apply: 1632 mplsTunnelIsIf must at least be read-only 1633 returning false(1)." 1635 GROUP mplsTunnelIsIntfcGroup 1636 DESCRIPTION 1637 "This group is mandatory for devices which support 1638 tunnels that are interfaces, in addition to 1639 mplsTunnelGroup. The following constraints apply: 1640 mplsTunnelIsIf must at least be read-only 1641 returning true(2)." 1643 GROUP mplsTunnelOptionalGroup 1644 DESCRIPTION 1645 "Objects in this group are optional." 1647 -- mplsTunnelTable 1649 OBJECT mplsTunnelName 1650 MIN-ACCESS read-only 1651 DESCRIPTION 1652 "Write access is not required." 1654 OBJECT mplsTunnelDescr 1655 MIN-ACCESS read-only 1656 DESCRIPTION 1657 "Write access is not required." 1659 OBJECT mplsTunnelIsIf 1660 MIN-ACCESS read-only 1661 DESCRIPTION 1662 "Write access is not required." 1664 OBJECT mplsTunnelIfIndex 1665 DESCRIPTION 1666 "Write access is not required." 1668 OBJECT mplsTunnelXCPointer 1669 MIN-ACCESS read-only 1670 DESCRIPTION 1671 "Write access is not required." 1673 OBJECT mplsTunnelSignallingProto 1674 MIN-ACCESS read-only 1675 DESCRIPTION 1676 "Write access is not required." 1678 OBJECT mplsTunnelSetupPrio 1679 MIN-ACCESS read-only 1680 DESCRIPTION 1681 "Write access is not required." 1683 OBJECT mplsTunnelHoldingPrio 1684 MIN-ACCESS read-only 1685 DESCRIPTION 1686 "Write access is not required." 1688 OBJECT mplsTunnelSessionAttributes 1689 MIN-ACCESS read-only 1690 DESCRIPTION 1691 "Write access is not required." 1693 OBJECT mplsTunnelOwner 1694 MIN-ACCESS read-only 1695 DESCRIPTION 1696 "Write access is not required." 1698 OBJECT mplsTunnelLocalProtectInUse 1699 MIN-ACCESS read-only 1700 DESCRIPTION 1701 "Write access is not required." 1703 OBJECT mplsTunnelResourcePointer 1704 MIN-ACCESS read-only 1705 DESCRIPTION 1706 "Write access is not required." 1708 OBJECT mplsTunnelInstancePriority 1709 MIN-ACCESS read-only 1710 DESCRIPTION 1711 "Write access is not required." 1713 OBJECT mplsTunnelHopTableIndex 1714 MIN-ACCESS read-only 1715 DESCRIPTION 1716 "Write access is not required." 1718 OBJECT mplsTunnelARHopTableIndex 1719 DESCRIPTION 1720 "Write access is not required." 1722 OBJECT mplsTunnelAdminStatus 1723 SYNTAX INTEGER { up (1), down (2) } 1724 MIN-ACCESS read-only 1725 DESCRIPTION 1726 "Only up and down states must be supported. Write 1727 access is not required." 1729 OBJECT mplsTunnelOperStatus 1730 SYNTAX INTEGER { up (1), down (2) } 1731 DESCRIPTION 1732 "Only up and down states must be supported. Write 1733 access is not required." 1735 OBJECT mplsTunnelRowStatus 1736 SYNTAX INTEGER { active(1), notInService(2), 1737 createAndGo(4), destroy(6) } 1738 MIN-ACCESS read-only 1739 DESCRIPTION 1740 "The notReady(3) and createAndWait(5) states need 1741 not be supported. Write access is not required." 1743 OBJECT mplsTunnelStorageType 1744 SYNTAX INTEGER { other(1) } 1745 MIN-ACCESS read-only 1746 DESCRIPTION 1747 "Only other (1) needs to be supported." 1749 -- mplsTunnelHopTable 1751 OBJECT mplsTunnelHopAddrType 1752 MIN-ACCESS read-only 1753 DESCRIPTION 1754 "Write access is not required." 1756 OBJECT mplsTunnelHopIpv4Addr 1757 MIN-ACCESS read-only 1758 DESCRIPTION 1759 "Write access is not required." 1761 OBJECT mplsTunnelHopIpv4PrefixLen 1762 MIN-ACCESS read-only 1763 DESCRIPTION 1764 "Write access is not required." 1766 OBJECT mplsTunnelHopIpv6Addr 1767 MIN-ACCESS read-only 1768 DESCRIPTION 1769 "Write access is not required." 1771 OBJECT mplsTunnelHopIpv6PrefixLen 1772 MIN-ACCESS read-only 1773 DESCRIPTION 1774 "Write access is not required." 1776 OBJECT mplsTunnelHopAsNumber 1777 MIN-ACCESS read-only 1778 DESCRIPTION 1779 "Write access is not required." 1781 OBJECT mplsTunnelHopLspId 1782 MIN-ACCESS read-only 1783 DESCRIPTION 1784 "Write access is not required." 1786 OBJECT mplsTunnelHopStrictOrLoose 1787 SYNTAX INTEGER { strict(1) } 1788 MIN-ACCESS read-only 1789 DESCRIPTION 1790 "loose(2) need not be supported. Write access is 1791 not required." 1793 OBJECT mplsTunnelHopRowStatus 1794 SYNTAX INTEGER { active(1), notInService(2), 1795 createAndGo(4), destroy(6) } 1796 MIN-ACCESS read-only 1797 DESCRIPTION 1798 "The notReady(3) and createAndWait(5) states need 1799 not be supported. Write access is not required." 1801 OBJECT mplsTunnelHopStorageType 1802 SYNTAX INTEGER { other(1) } 1803 MIN-ACCESS read-only 1804 DESCRIPTION 1805 "Only other (1) needs to be supported." 1807 -- mplsTunnelResourceTable 1809 OBJECT mplsTunnelResourceMaxRate 1810 MIN-ACCESS read-only 1811 DESCRIPTION 1812 "Write access is not required." 1814 OBJECT mplsTunnelResourceMeanRate 1815 MIN-ACCESS read-only 1816 DESCRIPTION 1817 "Write access is not required." 1819 OBJECT mplsTunnelResourceMaxBurstSize 1820 MIN-ACCESS read-only 1821 DESCRIPTION 1822 "Write access is not required." 1824 OBJECT mplsTunnelResourceRowStatus 1825 SYNTAX INTEGER { active(1), notInService(2), 1826 createAndGo(4), destroy(6) } 1827 MIN-ACCESS read-only 1828 DESCRIPTION 1829 "The notReady(3) and createAndWait(5) states need 1830 not be supported. Write access is not required." 1832 OBJECT mplsTunnelResourceStorageType 1833 SYNTAX INTEGER { other(1) } 1834 MIN-ACCESS read-only 1835 DESCRIPTION 1836 "Only other (1) needs to be supported." 1838 ::= { mplsTeCompliances 1 } 1840 -- Units of conformance. 1842 mplsTunnelGroup OBJECT-GROUP 1843 OBJECTS { mplsTunnelIndexNext, 1844 mplsTunnelName, 1845 mplsTunnelDescr, 1846 mplsTunnelOwner, 1847 mplsTunnelXCPointer, 1848 mplsTunnelIfIndex, 1849 mplsTunnelHopTableIndex, 1850 mplsTunnelARHopTableIndex, 1851 mplsTunnelAdminStatus, 1852 mplsTunnelOperStatus, 1853 mplsTunnelRowStatus, 1854 mplsTunnelTrapEnable, 1855 mplsTunnelStorageType, 1856 mplsTunnelMaxHops, 1857 mplsTunnelResourcePointer, 1858 mplsTunnelInstancePriority 1859 } 1860 STATUS current 1861 DESCRIPTION 1862 "Necessary, but not sufficient, set of objects to 1863 implement tunnels. In addition, depending on the 1864 type of the tunnels supported (for example, manually 1865 configured or signaled, persistent or non- 1866 persistent, etc.), the following other groups 1867 defined below are mandatory: mplsTunnelManualGroup 1868 and/or mplsTunnelSignaledGroup, 1869 mplsTunnelIsNotIntfcGroup and/or 1870 mplsTunnelIsIntfcGroup." 1871 ::= { mplsTeGroups 1 } 1873 mplsTunnelManualGroup OBJECT-GROUP 1874 OBJECTS { mplsTunnelSignallingProto } 1875 STATUS current 1876 DESCRIPTION 1877 "Object(s) needed to implement manually configured 1878 tunnels." 1879 ::= { mplsTeGroups 2 } 1881 mplsTunnelSignaledGroup OBJECT-GROUP 1882 OBJECTS { mplsTunnelSetupPrio, 1883 mplsTunnelHoldingPrio, 1884 mplsTunnelSignallingProto, 1885 mplsTunnelLocalProtectInUse, 1886 mplsTunnelSessionAttributes, 1887 mplsTunnelHopIndexNext, 1888 mplsTunnelHopAddrType, 1889 mplsTunnelHopIpv4Addr, 1890 mplsTunnelHopIpv4PrefixLen, 1891 mplsTunnelHopIpv6Addr, 1892 mplsTunnelHopIpv6PrefixLen, 1893 mplsTunnelHopAsNumber, 1894 mplsTunnelHopLspId, 1895 mplsTunnelHopStrictOrLoose, 1896 mplsTunnelHopRowStatus, 1897 mplsTunnelHopStorageType 1898 } 1899 STATUS current 1900 DESCRIPTION 1901 "Object needed to implement signaled tunnels." 1902 ::= { mplsTeGroups 3 } 1904 mplsTunnelIsIntfcGroup OBJECT-GROUP 1905 OBJECTS { mplsTunnelIsIf } 1906 STATUS current 1907 DESCRIPTION 1908 "Objects needed to implement tunnels that are 1909 interfaces." 1910 ::= { mplsTeGroups 4 } 1912 mplsTunnelIsNotIntfcGroup OBJECT-GROUP 1913 OBJECTS { mplsTunnelIsIf } 1914 STATUS current 1915 DESCRIPTION 1916 "Objects needed to implement tunnels that are not 1917 interfaces." 1918 ::= { mplsTeGroups 5 } 1920 mplsTunnelOptionalGroup OBJECT-GROUP 1921 OBJECTS { mplsTunnelResourceIndexNext, 1922 mplsTunnelResourceMaxRate, 1923 mplsTunnelResourceMeanRate, 1924 mplsTunnelResourceMaxBurstSize, 1925 mplsTunnelResourceRowStatus, 1926 mplsTunnelResourceStorageType, 1927 mplsTunnelARHopAddrType, 1928 mplsTunnelARHopIpv4Addr, 1929 mplsTunnelARHopIpv4PrefixLen, 1930 mplsTunnelARHopIpv6Addr, 1931 mplsTunnelARHopIpv6PrefixLen, 1932 mplsTunnelARHopAsNumber, 1933 mplsTunnelARHopStrictOrLoose 1934 } 1935 STATUS current 1936 DESCRIPTION 1937 "The objects in this group are optional." 1938 ::= { mplsTeGroups 6 } 1940 mplsTeNotificationGroup NOTIFICATION-GROUP 1941 NOTIFICATIONS { mplsTunnelUp, 1942 mplsTunnelDown, 1943 mplsTunnelRerouted 1945 } 1946 STATUS current 1947 DESCRIPTION 1948 "Set of notifications implemented in this module. 1949 None is mandatory." 1950 ::= { mplsTeGroups 7 } 1952 -- End of MPLS-TE-MIB 1953 END 1955 11. Security Considerations 1957 There are a number of management objects defined in this 1958 MIB that have a MAX-ACCESS clause of read-write and/or 1959 read-create. Such objects may be considered sensitive or 1960 vulnerable in some network environments. The support for 1961 SET operations in a non-secure environment without proper 1962 protection can have a negative effect on network 1963 operations. 1965 It is thus important to control even GET access to these 1966 objects and possibly to even encrypt the values of these 1967 object when sending them over the network via SNMP. Not 1968 all versions of SNMP provide features for such a secure 1969 environment. 1971 SNMPv1 by itself is not a secure environment. Even if the 1972 network itself is secure (for example by using IPSec 1973 [IPSEC]), there is no control as to who on the secure 1974 network is allowed to access and GET/SET 1975 (read/change/create/delete) the objects in this MIB. It is 1976 recommended that the implementers consider the security 1977 features as provided by the SNMPv3 framework. 1978 Specifically, the use of the User-based Security Model 1979 [SNMPv3USM] and the View- based Access Control 1980 [SNMPv3VACM] is recommended. It is then a customer/user 1981 responsibility to ensure that the SNMP entity giving 1982 access to an instance of this MIB, is properly configured 1983 to give access to the objects only to those principals 1984 (users) that have legitimate rights to indeed GET or SET 1985 (change/create/delete) them. 1987 12. Acknowledgments 1989 We wish to thank Adrian Farrel, Eric Gray, Patrick 1990 Kerharo, and Pramod Koppol for their comments on this 1991 draft. 1993 13. References 1995 [MPLSArch] Rosen, E., Viswanathan, A., and R. Callon, 1996 "Multiprotocol Label Switching 1997 Architecture", Internet Draft , August 1999. 2000 [MPLSFW] Callon, R., Doolan, P., Feldman, N., 2001 Fredette, A., Swallow, G., and A. 2002 Viswanathan, "A Framework for Multiprotocol 2003 Label Switching", Internet Draft , September 1999. 2006 [LSRMIB] Srinivasan, C., Viswanathan, A. and T. 2007 Nadeau, "MPLS Label Switch Router Management 2008 Information Base Using SMIv2", Internet 2009 Draft , 2010 April 26, 2000. 2012 [LblStk] Rosen, E., Rekhter, Y., Tappan, D., 2013 Farinacci, D., Federokow, G., Li, T., and A. 2014 Conta, "MPLS Label Stack Encoding", Internet 2015 Draft , 2016 September 1999. 2018 [RSVPTun] Awaduche, D., Berger, L., Der-Haw, G., Li, 2019 T., Swallow, G., and V. Srinivasan, 2020 "Extensions to RSVP for LSP Tunnels", 2021 Internet Draft , February 2000. 2024 [CR-LDP] B. Jamoussi (Editor), "Constraint-Based LSP 2025 Setup using LDP", Internet Draft , September 1999. 2028 [Assigned] Reynolds, J., and J. Postel, "Assigned 2029 Numbers", RFC 1700, October 1994. See also: 2030 http://www.isi.edu/in- 2031 notes/iana/assignments/smi-numbers 2033 [SNMPArch] Harrington, D., Presuhn, R., and B. Wijnen, 2034 "An Architecture for Describing SNMP 2035 Management Frameworks", RFC 2271, January 2036 1998. 2038 [SMIv1] Rose, M., and K. McCloghrie, "Structure and 2039 Identification of Management Information for 2040 TCP/IP-based Internets", RFC 1155, May 1990. 2042 [SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB 2043 Definitions", RFC 1212, March 1991. 2045 [SNMPv1Traps] M. Rose, "A Convention for Defining Traps 2046 for use with the SNMP", RFC 1215, March 2047 1991. 2049 [SMIv2] Case, J., McCloghrie, K., Rose, M., and S. 2050 Waldbusser, "Structure of Management 2051 Information for Version 2 of the Simple 2052 Network Management Protocol (SNMPv2)", RFC 2053 1902, January 1996. 2055 [SNMPv2TC] Case, J., McCloghrie, K., Rose, M., and S. 2056 Waldbusser, "Textual Conventions for Version 2057 2 of the Simple Network Management Protocol 2058 (SNMPv2)", RFC 1903, SNMP Research, Inc., 2059 Cisco Systems, Inc., January 1996. 2061 [SNMPv2Conf] Case, J., McCloghrie, K., Rose, M., and S. 2062 Waldbusser, "Conformance Statements for 2063 Version 2 of the Simple Network Management 2064 Protocol (SNMPv2)", RFC 1904, January 1996. 2066 [SNMPv1] Case, J., Fedor, M., Schoffstall, M., and J. 2067 Davin, "Simple Network Management Protocol", 2068 RFC 1157, May 1990. 2070 [SNMPv2c] Case, J., McCloghrie, K., Rose, M., and S. 2071 Waldbusser, "Introduction to Community-based 2072 SNMPv2", RFC 1901, January 1996. 2074 [SNMPv2TM] Case, J., McCloghrie, K., Rose, M., and S. 2075 Waldbusser, "Transport Mappings for Version 2076 2 of the Simple Network Management Protocol 2077 (SNMPv2)", RFC 1906, January 1996. 2079 [SNMPv3MP] Case, J., Harrington D., Presuhn R., and B. 2080 Wijnen, "Message Processing and Dispatching 2081 for the Simple Network Management Protocol 2082 (SNMP)", RFC 2272, January 1998. 2084 [SNMPv3USM] Blumenthal, U., and B. Wijnen, "User-based 2085 Security Model (USM) for version 3 of the 2086 Simple Network Management Protocol 2087 (SNMPv3)", RFC 2574, April 1999. 2089 [SNMPv2PO] Case, J., McCloghrie, K., Rose, M., and S. 2090 Waldbusser, "Protocol Operations for Version 2091 2 of the Simple Network Management Protocol 2092 (SNMPv2)", RFC 1905, January 1996. 2094 [SNMPv3App] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2095 Applications", RFC 2273, January 1998. 2097 [SNMPv3VACM] Wijnen, B., Presuhn, R., and K. McCloghrie, 2098 "View-based Access Control Model (VACM) for 2099 the Simple Network Management Protocol 2100 (SNMP)", RFC 2575, April 1999. 2102 [IPSEC] Kent, S., and Atkinson, R., "Security 2103 Architecture for the Internet Protocol", RFC 2104 2401, November 1998. 2106 [IFMIB] McCloghrie, K., and F. Kastenholtz, "The 2107 Interfaces Group MIB using SMIv2", RFC 2233, 2108 Nov. 1997. 2110 14. Authors' Addresses 2112 Cheenu Srinivasan 2113 Tachion Networks, Inc. 2114 Monmouth Park Corporate Center I 2115 Building C, 185 Monmouth Park Highway 2116 West Long Branch, NJ 07764 2117 Phone: +1-732-542-7750 x1234 2118 Email: cheenu@tachion.com 2120 Arun Viswanathan 2121 Force10 Networks, Inc. 2122 1440 McCarthy Blvd 2123 Milpitas, CA 95035 2124 Phone: +1-408-571-3516 2125 Email: arun@force10networks.com 2127 Thomas D. Nadeau 2128 Cisco Systems, Inc. 2129 300 Apollo Drive 2130 Chelmsford, MA 01824 2131 Phone: +1-978-244-3051 2132 Email: tnadeau@cisco.com 2134 15. Full Copyright Statement 2136 Copyright (C) The Internet Society (2000). All Rights 2137 Reserved. 2139 This document and translations of it may be copied and 2140 furnished to others, and derivative works that comment on 2141 or otherwise explain it or assist in its implementation may 2142 be prepared, copied, published and distributed, in whole or 2143 in part, without restriction of any kind, provided that the 2144 above copyright notice and this paragraph are included on 2145 all such copies and derivative works. However, this 2146 document itself may not be modified in any way, such as by 2147 removing the copyright notice or references to the Internet 2148 Society or other Internet organizations, except as needed 2149 for the purpose of developing Internet standards in which 2150 case the procedures for copyrights defined in the Internet 2151 Standards process must be followed, or as required to 2152 translate it into languages other than English. 2154 The limited permissions granted above are perpetual and 2155 will not be revoked by the Internet Society or its 2156 successors or assigns. This document and the information 2157 contained herein is provided on an "AS IS" basis and THE 2158 INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE 2159 DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 2160 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2161 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2162 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 2163 PURPOSE.