idnits 2.17.1 draft-ietf-mpls-te-mib-05.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 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 ([MPLSArch]), 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 572: '...e identifier for an MPLS LSR. This MAY...' RFC 2119 keyword, line 1194: '...nce represents. This value MUST be set...' RFC 2119 keyword, line 1196: '... This value MUST be set to transi...' RFC 2119 keyword, line 1198: '...rted. This value MUST be set to tail(3...' RFC 2119 keyword, line 1210: '...is unavailable, it MUST return a value...' (1 more instance...) Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 325 has weird spacing: '... tunnel is do...' == Line 661 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 (November 21, 2000) is 8557 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 93, but not defined == Unused Reference: 'LblStk' is defined on line 2669, but no explicit reference was found in the text == Unused Reference: 'Assigned' is defined on line 2685, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'MPLSArch' -- 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 (~~), 8 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Cheenu Srinivasan 2 Internet Draft Tachion Networks, Inc. 3 Expires: May 2001 4 Arun Viswanathan 5 Force10 Networks, Inc. 7 Thomas D. Nadeau 8 Cisco Systems, Inc. 10 November 21, 2000 12 MPLS Traffic Engineering Management Information Base Using 13 SMIv2 15 draft-ietf-mpls-te-mib-05.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 RFC2026. 22 Internet-Drafts are working documents of the Internet 23 Engineering Task Force (IETF), its areas, and its working 24 groups. Note that other groups may also distribute working 25 documents as Internet-Drafts. 27 Internet-Drafts are draft documents valid for a maximum of 28 six months and may be updated, replaced, or obsoleted by 29 other documents at any time. It is inappropriate to use 30 Internet-Drafts as reference material or to cite them other 31 than as "work in progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/ietf/1id-abstracts.txt. 36 The list of Internet-Draft Shadow Directories can be 37 accessed at http://www.ietf.org/shadow.html. 39 Abstract 41 This memo defines an experimental portion of the Management 42 Information Base (MIB) for use with network management 43 protocols in the Internet community. In particular, it 44 describes managed objects for Multi-Protocol Label 45 Switching (MPLS) [MPLSArch] based traffic engineering. 47 1. Introduction 49 This memo defines an experimental portion of the Management 50 Information Base (MIB) for use with network management 51 protocols in the Internet community. In particular, it 52 describes managed objects for modeling a Multi-Protocol 53 Label Switching (MPLS) [MPLSArch] based traffic 54 engineering. This MIB should be used in conjunction with 55 the companion document [LSRMIB] for MPLS based traffic 56 engineering configuration and management. 58 Comments should be made directly to the MPLS mailing list 59 at mpls@uu.net. 61 This memo does not, in its draft form, specify a standard 62 for the Internet community. 64 2. Terminology 66 This document uses terminology from the MPLS architecture 67 document [MPLSArch] and MPLS Label Switch Router MIB 68 [LSRMIB]. Some frequently used terms are described next. 70 An explicitly routed LSP (ERLSP) is referred to as an MPLS 71 tunnel. It consists of one in-segment and/or one out- 72 segment at the ingress/egress LSRs, each segment being 73 associated with one MPLS interface. These are also 74 referred to as tunnel segments. Additionally, at an 75 intermediate LSR, we model a connection as consisting of 76 one or more in-segments and/or one or more out-segments. 77 The binding or interconnection between in-segments and out- 78 segments in performed using a cross-connect. These objects 79 are defined in the MPLS Label Switch Router MIB [LSRMIB]. 81 3. The SNMP Management Framework 83 The SNMP Management Framework presently consists of five 84 major components: 86 - An overall architecture, described in RFC 2271 87 [SNMPArch]. 89 - Mechanisms for describing and naming objects and events 90 for the purpose of management. The first version of 91 this Structure of Management Information (SMI) is 92 called SMIv1 and described in RFC 1155 [SMIv1], RFC 93 1212 [SNMPv1MIBDef] and RFC 1215 [SNMPv1Traps]. The 94 second version, called SMIv2, is described in RFC 1902 95 [SMIv2], RFC 1903 [SNMPv2TC] and RFC 1904 [SNMPv2Conf]. 97 - Message protocols for transferring management 98 information. The first version of the SNMP message 99 protocol is called SNMPv1 and described in RFC 1157 100 [SNMPv1]. A second version of the SNMP message 101 protocol, which is not an Internet standards track 102 protocol, is called SNMPv2c and described in RFC 1901 103 [SNMPv2c] and RFC 1906 [SNMPv2TM]. The third version 104 of the message protocol is called SNMPv3 and described 105 in RFC 1906 [SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC 106 2574 [SNMPv3USM]. 108 - Protocol operations for accessing management 109 information. The first set of protocol operations and 110 associated PDU formats is described in RFC 1157 111 [SNMPv1]. A second set of protocol operations and 112 associated PDU formats is described in RFC 1905 113 [SNMPv2PO]. 115 - A set of fundamental applications described in RFC 2273 116 [SNMPv3App] and the view-based access control mechanism 117 described in RFC 2575 [SNMPv3VACM]. 119 Managed objects are accessed via a virtual information 120 store, termed the Management Information Base or MIB. 121 Objects in the MIB are defined using the mechanisms defined 122 in the SMI. This memo specifies a MIB module that is 123 compliant to the SMIv2. A MIB conforming to the SMIv1 can 124 be produced through the appropriate translations. The 125 resulting translated MIB must be semantically equivalent, 126 except where objects or events are omitted because no 127 translation is possible (use of Counter64). Some machine- 128 readable information in SMIv2 will be converted into 129 textual descriptions in SMIv1 during the translation 130 process. However, this loss of machine-readable 131 information is not considered to change the semantics of 132 the MIB. 134 3.1. Object Definitions 136 Managed objects are accessed via a virtual information 137 store, termed the Management Information Base or MIB. 138 Objects in the MIB are defined using the subset of Abstract 139 Syntax Notation One (ASN.1) defined in the SMI. In 140 particular, each object type is named by an OBJECT 141 IDENTIFIER, an administratively assigned name. The object 142 type together with an object instance serves to uniquely 143 identify a specific instantiation of the object. For human 144 convenience, we often use a textual string, termed the 145 descriptor, to also refer to the object type. 147 4. Feature List 149 The MPLS traffic engineering MIB is designed to satisfy the 150 following requirements and constraints. 152 - The MIB supports configuration of point-to-point 153 unidirectional tunnels. 155 - MPLS tunnels need not be interfaces, but it is possible 156 to configure a tunnel as an interface. 158 - The MIB supports manually configured MPLS tunnels as 159 well as those set up via any MPLS signaling protocol. 161 - The MIB supports persistent as well as non-persistent 162 tunnels. 164 5. Outline 166 Traffic engineering support for MPLS tunnels requires the 167 following configuration. 169 - Setting up MPLS tunnels along with appropriate 170 configuration parameters. 172 - Configuring tunnel loose and strict source routed hops. 174 These actions may need to be accompanied with corresponding 175 actions using [LSRMIB] to establish and configure tunnel 176 segments, if this is done manually. Also, the in-segment 177 and out-segment performance tables, mplsInSegmentPerfTable 178 and mplsOutSegmentPerfTable [LSRMIB], should be used to 179 determine performance of the tunnels and tunnel segments. 181 5.1. Summary of Traffic Engineering MIB 183 The MIB objects for performing these actions consist of the 184 following tables. 186 - Tunnel table (mplsTunnelTable) for setting up MPLS 187 tunnels. 189 - Resource table (mplsTunnelResourceTable) for setting up 190 the tunnel resources. 192 - Tunnel hop table (mplsTunnelHopTable) for configuring 193 strict and loose source routed MPLS tunnels hops. 195 When a tunnel is signaled via a MPLS signaling protocol, 196 the mplsTunnelARHopTable gives the actual list of hops 197 traversed by the tunnel as reported by the signaling 198 protocol. These tables are described in the subsequent 199 sections. 201 6. Brief Description of MIB Objects 203 The objects described in this section support the 204 functionality described in documents [RSVPTun][CR-LDP]. 205 The tables support both manually configured and signaled 206 tunnels. 208 6.1. mplsTunnelTable 210 The mplsTunnelTable allows new MPLS tunnels to be created 211 between an MPLS LSR and a remote endpoint, and existing 212 tunnels to be reconfigured or removed. Note that we only 213 support point-to-point tunnel segments, although multi- 214 point-to-point and point-to-multi-point connections are 215 supported by an LSR acting as a cross-connect. Each MPLS 216 tunnel can thus have one out-segment originating at an LSR 217 and/or one in-segment terminating at that LSR. 219 mplsTunnelTable does not define the in and out segments 220 forming the tunnel. Instead, these are defined by creating 221 rows in the in-segment and out-segment tables, defining 222 relationships in the cross-connect table and referring to 223 these rows in the mplsTunnelTable using a cross-connect 224 index, mplsTunnelXCIndex. These segment and cross-connect 225 related objects are defined in [LSRMIB]. 227 6.2. mplsTunnelResourceTable 229 mplsTunnelResourceTable is used to indicate the resources 230 required for a tunnel. Multiple tunnels may share the same 231 resource by pointing to the same entry in this table. 232 Tunnels that do not share resource must point to separate 233 entries in this table. 235 6.3. mplsTunnelHopTable 237 mplsTunnelHopTable is used to indicate the hops, strict or 238 loose, for an MPLS tunnel defined in mplsTunnelTable, when 239 it is established via signaling. Multiple tunnels may 240 share the same hops by pointing to the same entry in this 241 table. Each row also has a secondary index, 242 mplsTunnelHopIndex, corresponding to the next hop of this 243 tunnel. The scalar mplsTunnelMaxHops indicates the maximum 244 number of hops that can be specified on each tunnel 245 supported by this LSR. 247 6.4. mplsTunnelARHopTable 249 mplsTunnelARHopTable is used to indicate the actual hops 250 traversed by a tunnel as reported by the MPLS signaling 251 protocol after the tunnel is setup. The support of this 252 table is optional since not all MPLS signaling protocol may 253 support this feature. 255 6.5. mplsTunnelCHoptable 257 mplsTunnelCHopTable lists the actual hops computed by a 258 constraint-based routing algorithm based on the 259 mplsTunnelHopTable. The support of this table is optional 260 since not all implementations may support computation of 261 hop list using a constraint-based routing protocol. 263 6.6. mplsTunnelPerfTable 265 mplsTunnelPerfTable provides several counters to measure 266 the performance of the MPLS tunnels. This table auguments 267 mplsTunnelTable. 269 7. Application of the Interface Group to MPLS Tunnels 271 The Interfaces Group of MIB II defines generic managed 272 objects for managing interfaces. This memo contains the 273 media-specific extensions to the Interfaces Group for 274 managing MPLS Tunnels as logical interfaces. 276 This memo assumes the interpretation of the Interfaces 277 Group to be in accordance with [IFMIB] which states that 278 the interfaces table (ifTable) contains information on the 279 managed resource's interfaces and that each sub-layer below 280 the internetwork layer of a network interface is considered 281 an interface. Thus, the MPLS interface is represented as 282 an entry in the ifTable. The interrelation of entries in 283 the ifTable is defined by Interfaces Stack Group defined in 284 [IFMIB]. 286 When using MPLS Tunnels as interfaces, the interface stack 287 table might appear as follows: 289 +------------------------------------------------+ 290 | MPLS-Tunnel-interface ifType = mplsTunnel(150) | 291 +------------------------------------------------+ 292 | MPLS-interface ifType = mpls(166) | 293 +------------------------------------------------+ 294 | Underlying Layer | 295 +------------------------------------------------+ 297 In the above diagram, "Underlying Layer" refers to the 298 ifIndex of any interface type, which has been defined for 299 MPLS interworking. Examples include ATM, Frame Relay, 300 Ethernet, etc. 302 7.1. Support of the MPLS Tunnel Interface by ifTable 304 Some specific interpretations of ifTable for those MPLS 305 tunnels represented as interfaces follow: 307 Object Use for the MPLS tunnel. 309 ifIndex Each MPLS tunnel is represented by an 310 ifEntry. 312 ifDescr Description of the MPLS tunnel. 314 ifType The value that is allocated for MPLS 315 tunnel is 150. 317 ifSpeed The total bandwidth in bits per second 318 for use by the MPLS tunnel. 320 ifPhysAddress Unused. 322 ifAdminStatus See [IFMIB]. 324 ifOperStatus Assumes the value down(2) if the MPLS 325 tunnel is down. 327 ifLastChange See [IFMIB]. 329 ifInOctets The number of octets received over the 330 MPLS tunnel. 332 ifOutOctets The number of octets transmitted over 333 the MPLS tunnel. 335 ifInErrors The number of labeled packets dropped 336 due to uncorrectable errors. 338 ifInUnknownProtos The number of received packets 339 discarded during packet header 340 validation, including packets with 341 unrecognized label values. 343 ifOutErrors See [IFMIB]. 345 ifName Textual name (unique on this system) of 346 the MPLS tunnel or an octet string of 347 zero length. 349 ifLinkUpDownTrapEnable 350 Default is disabled (2). 352 ifConnectorPresent Set to false (2). 354 ifHighSpeed See [IFMIB]. 356 ifHCInOctets The 64-bit version of ifInOctets; 357 supported if required by the compliance 358 statements in [IFMIB]. 360 ifHCOutOctets The 64-bit version of ifOutOctets; 361 supported if required by the compliance 362 statements in [IFMIB]. 364 ifAlias The non-volatile 'alias' name for the 365 MPLS tunnel as specified by a network 366 manager. 368 8. Example of Tunnel Setup 370 This section contains an example of which MIB objects 371 should be modified if one would like to create a best 372 effort, loosely routed, unidirectional traffic engineered 373 tunnel, which spans two hops of a simple network. Note 374 that these objects should be created on the "head-end" 375 LSR. 377 In mplsTunnelTable: 378 { 379 mplsTunnelIndex = 1, 380 mplsTunnelInstance = 1, 381 mplsTunnelIngressLSRId = 123.123.125.1, 382 mplsTunnelEgressLSRId = 123.123.126.1, 383 mplsTunnelName = "My first tunnel", 384 mplsTunnelDescr = "Here to there", 385 mplsTunnelIsIf = true (1), 386 mplsTunnelXCPointer = mplsXCIndex.2.0.0.15, 387 mplsTunnelSignallingProto = none (1), 388 mplsTunnelSetupPrio = 0, 389 mplsTunnelHoldingPrio = 0, 390 mplsTunnelSessionAttributes = 0, 391 mplsTunnelOwner = snmp (1), 392 mplsTunnelLocalProtectInUse = false (0), 393 mplsTunnelResourcePointer = mplsTunnelResourceIndex.5, 394 mplsTunnelInstancePriority = 1, 395 mplsTunnelHopTableIndex = 1, 396 mplsTunnelPrimaryInstance = 0, 397 mplsTunnelIncludeAnyAffinity = 0, 398 mplsTunnelIncludeAllAffinity = 0, 399 mplsTunnelExcludeAllAffinity = 0, 400 mplsTunnelPathInUse = 1, 401 mplsTunnelRole = head(1), 402 mplsTunnelRowStatus = createAndGo (4) 403 } 405 In mplsTunnelResourceTable: 406 { 407 mplsTunnelResourceIndex = 5, 408 mplsTunnelResourceMaxRate = 0, 409 mplsTunnelResourceMeanRate = 0, 410 mplsTunnelResourceMaxBurstSize = 0, 411 mplsTunnelResourceRowStatus = createAndGo (4) 412 } 414 The next two instances of mplsTunnelHopEntry are used to 415 denote the hops this tunnel will take across the network. 417 The following denotes the beginning of the network, or the 418 first hop. We have used the fictitious LSR identified by 419 "123.123.125.1" as our example head-end router. 421 In mplsTunnelHopTable: 422 { 423 mplsTunnelHopListIndex = 1, 424 mplsTunnelPathOptionIndex = 1, 425 mplsTunnelHopIndex = 1, 426 mplsTunnelHopAddrType = 1, 427 mplsTunnelHopIpv4Addr = 123.123.125.1, 428 mplsTunnelHopIpv4PrefixLen = 9, 429 mplsTunnelHopType = loose (2), 430 mplsTunnelHopRowStatus = createAndGo (4) 431 } 433 The following denotes the end of the network, or the last 434 hop in our example. We have used the fictitious LSR 435 identified by "123.123.126.1" as our end router. 437 In mplsTunnelHopTable: 438 { 439 mplsTunnelHopListIndex = 1, 440 mplsTunnelPathOptionIndex = 1, 441 mplsTunnelHopIndex = 2, 442 mplsTunnelHopAddrType = 1, 443 mplsTunnelHopIpv4Addr = 123.123.126.1, 444 mplsTunnelHopIpv4PrefixLen = 9, 445 mplsTunnelHopType = loose (2), 446 mplsTunnelHopRowStatus = createAndGo (4) 447 } 449 9. The Use of RowPointer 451 RowPointer is a textual convention used to identify a 452 conceptual row in an SNMP Table by pointing to one of its 453 objects. In this MIB, in mplsTunnelTable, the objects 454 mplsTunnelXCPointer and mplsTunnelResourcePointer are of 455 type RowPointer. The object mplsTunnelXCPointer points to a 456 specific entry in the mplsXCTable [LSRMIB]. This entry in 457 the mplsXCTable is the associated LSP for the given MPLS 458 tunnel entry. The object mplsTunnelResourcePointer points 459 to a specific entry in a traffic parameter table. An 460 example of such a traffic parameter table is 461 mplsTunnelResourceTable. It indicates a specific instance 462 of a traffic parameter entry that is associated with a 463 given MPLS tunnel entry. 465 10. MPLS Traffic Engineering MIB Definitions 467 MPLS-TE-MIB DEFINITIONS ::= BEGIN 469 IMPORTS 470 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 471 experimental, Integer32, Unsigned32, Counter32, 472 Counter64, TimeTicks, TimeStamp 473 FROM SNMPv2-SMI 475 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 476 FROM SNMPv2-CONF 478 TEXTUAL-CONVENTION, TruthValue, RowStatus, RowPointer, 479 StorageType, DisplayString 480 FROM SNMPv2-TC 482 InterfaceIndexOrZero 483 FROM IF-MIB 485 MplsBitRate, MplsBurstSize, MplsLSPID 486 FROM MPLS-LSR-MIB 488 InetAddressIPv4, InetAddressIPv6 489 FROM INET-ADDRESS-MIB; 491 mplsTeMIB MODULE-IDENTITY 492 LAST-UPDATED 493 "200011211200Z" -- November 21 2000 12:00:00 EST 494 ORGANIZATION 495 "Multiprotocol Label Switching (MPLS) Working Group" 496 CONTACT-INFO 497 " Cheenu Srinivasan 498 Postal: Tachion Networks, Inc. 499 Monmouth Park Corporate Center I 500 Building C, 185 Monmouth Park Highway 501 West Long Branch, NJ 07764 502 Tel: +1-732-542-7750 x1234 503 Email: cheenu@tachion.com 505 Arun Viswanathan 506 Postal: Force10 Networks, Inc. 507 1440 McCarthy Blvd 508 Milpitas, CA 95035 509 Tel: +1-408-571-3516 510 Email: arun@force10networks.com 512 Thomas D. Nadeau 513 Postal: Cisco Systems, Inc. 514 250 Apollo Drive 515 Chelmsford, MA 01824 516 Tel: +1-978-244-3051 517 Email: tnadeau@cisco.com" 518 DESCRIPTION 519 "This MIB module contains managed object 520 definitions for MPLS Traffic Engineering (TE) as 521 defined in: Extensions to RSVP for LSP Tunnels, 522 Awduche et al, Internet Draft , August 2000; Constraint- 524 Based LSP Setup using LDP, B. Jamoussi, Internet 525 Draft , July 2000; 526 Requirements for Traffic Engineering Over MPLS, 527 Awduche, D., J. Malcolm, J., Agogbua, J., O'Dell, 528 M., J. McManus, , September 1999." 530 -- Revision history. 532 REVISION 533 "200011271200Z" -- 21 November 2000 12:00:00 EST 534 DESCRIPTION 535 "Updates based on MPLS WG feedback" 536 REVISION 537 "200007141200Z" -- 14 July 2000 12:00:00 EST 538 DESCRIPTION 539 "Updates based on MPLS WG feedback" 540 REVISION 541 "200005261200Z" -- 26 May 2000 12:00:00 EST 542 DESCRIPTION 543 "Updates based on MPLS WG feedback" 544 REVISION 545 "200003031200Z" -- 3 March 2000 12:00:00 EST 546 DESCRIPTION 547 "Updates based on MPLS WG feedback" 548 REVISION 549 "199907161200Z" -- 16 July 1999 12:00:00 EST 550 DESCRIPTION 551 "Initial draft version." 553 ::= { experimental 95 } 555 -- Textual Conventions. 557 MplsTunnelIndex ::= TEXTUAL-CONVENTION 558 STATUS current 559 DESCRIPTION 560 "Index into mplsTunnelTable." 561 SYNTAX Integer32 (1..65535) 563 MplsTunnelInstanceIndex ::= TEXTUAL-CONVENTION 564 STATUS current 565 DESCRIPTION 566 "Instance index into mplsTunnelTable." 567 SYNTAX Unsigned32 (0..65535) 569 MplsLsrId ::= TEXTUAL-CONVENTION 570 STATUS current 571 DESCRIPTION 572 "A unique identifier for an MPLS LSR. This MAY 573 represent an IpV4 address." 574 SYNTAX Unsigned32 576 MplsPathIndex ::= TEXTUAL-CONVENTION 577 STATUS current 578 DESCRIPTION 579 "A unique identifier used to identify a specific 580 path used by a tunnel." 581 SYNTAX Unsigned32 583 MplsPathIndexOrZero ::= TEXTUAL-CONVENTION 584 STATUS current 585 DESCRIPTION 586 "A unique identifier used to identify a specific 587 path used by a tunnel. If this value is set to 0, 588 it indicates that no path is in use." 589 SYNTAX Unsigned32 591 -- Top level components of this MIB. 593 -- tables, scalars 594 mplsTeScalars OBJECT IDENTIFIER ::= { mplsTeMIB 1 } 595 mplsTeObjects OBJECT IDENTIFIER ::= { mplsTeMIB 2 } 597 -- traps 598 mplsTeNotifications OBJECT IDENTIFIER ::= { mplsTeMIB 3 } 599 mplsTeNotifyPrefix OBJECT IDENTIFIER ::= { mplsTeNotifications 0 } 601 -- conformance 602 mplsTeConformance OBJECT IDENTIFIER ::= { mplsTeMIB 4 } 604 -- MPLS Tunnel scalars. 606 mplsTunnelConfigured OBJECT-TYPE 607 SYNTAX Unsigned32 608 MAX-ACCESS read-only 609 STATUS current 610 DESCRIPTION 611 "The number of tunnels configured on this device. A 612 tunnel is considered configured if the 613 mplsTunnelRowStatus is active(1)." 614 ::= { mplsTeScalars 1 } 616 mplsTunnelActive OBJECT-TYPE 617 SYNTAX Unsigned32 618 MAX-ACCESS read-only 619 STATUS current 620 DESCRIPTION 621 "The number of tunnels active on this device. A 622 tunnel is considered active if the 623 mplsTunnelOperStatus is up(1)." 624 ::= { mplsTeScalars 2 } 626 mplsTunnelTEDistProto OBJECT-TYPE 627 SYNTAX BITS { 628 other (0), 629 ospf (1), 630 isis (2) 631 } 632 MAX-ACCESS read-only 633 STATUS current 634 DESCRIPTION 635 "The traffic engineering distribution protocol(s) 636 used by this LSR. Note that an LSR may support 637 more than one distribution protocols 638 simultaneously." 639 ::= { mplsTeScalars 3 } 641 mplsTunnelMaxHops OBJECT-TYPE 642 SYNTAX Unsigned32 643 MAX-ACCESS read-only 644 STATUS current 645 DESCRIPTION 646 "The maximum number of hops that can be specified 647 for a tunnel on this device." 648 ::= { mplsTeScalars 4 } 650 -- End of MPLS Tunnel scalars. 652 -- MPLS tunnel table. 654 mplsTunnelIndexNext OBJECT-TYPE 655 SYNTAX Integer32 (0..65535) 656 MAX-ACCESS read-only 657 STATUS current 658 DESCRIPTION 659 "This object contains the next appropriate value to 660 be used for mplsTunnelIndex when creating entries 661 in mplsTunnelTable. If the number of unassigned 662 entries is exhausted, a retrival operation will 663 return a value of 0. This object may also return 664 a value of 0 when the LSR is unable to accept 665 conceptual row creation, for example, if the 666 mplsTunnelTable is implemented as read-only. To 667 obtain the value of mplsTunnelIndex for a new 668 entry, the manager must first issue a management 669 protocol retrieval operation to obtain the current 670 value of this object. The agent should modify the 671 value to reflect the next unassigned index after 672 each retrieval operation. After a manager 673 retrieves a value the agent will determine through 674 its local policy when this index value will be 675 made available for reuse." 676 ::= { mplsTeObjects 1 } 678 mplsTunnelTable OBJECT-TYPE 679 SYNTAX SEQUENCE OF MplsTunnelEntry 680 MAX-ACCESS not-accessible 681 STATUS current 682 DESCRIPTION 683 "The mplsTunnelTable allows new MPLS tunnels to be 684 created between an LSR and a remote endpoint, and 685 existing tunnels to be reconfigured or removed. 686 Note that only point-to-point tunnel segments are 687 supported, although multi-point-to-point and point- 688 to-multi-point connections are supported by an LSR 689 acting as a cross-connect. Each MPLS tunnel can 690 thus have one out-segment originating at this LSR 691 and/or one in-segment terminating at this LSR." 692 ::= { mplsTeObjects 2 } 694 mplsTunnelEntry OBJECT-TYPE 695 SYNTAX MplsTunnelEntry 696 MAX-ACCESS not-accessible 697 STATUS current 698 DESCRIPTION 699 "An entry in this table represents an MPLS tunnel. 700 An entry can be created by a network administrator 701 or by an SNMP agent as instructed by an MPLS 702 signaling protocol. Whenever a new entry is 703 created with mplsTunnelIsIf set to true(1), then a 704 corresponding entry is created in ifTable as well 705 (see RFC 2233). The ifType of this entry is 706 mplsTunnel(150)." 707 REFERENCE 708 "1. RFC 2233 - The Interfaces Group MIB using 709 SMIv2, McCloghrie, K., and F. Kastenholtz, Nov. 710 1997 711 2. RFC 1700 - Assigned Numbers, Reynolds, J. and 712 J. Postel, Oct. 1994" 713 INDEX { mplsTunnelIndex, mplsTunnelInstance, 714 mplsTunnelIngressLSRId, mplsTunnelEgressLSRId 715 } 716 ::= { mplsTunnelTable 1 } 718 MplsTunnelEntry ::= SEQUENCE { 719 mplsTunnelIndex MplsTunnelIndex, 720 mplsTunnelInstance MplsTunnelInstanceIndex, 721 mplsTunnelIngressLSRId MplsLsrId, 722 mplsTunnelEgressLSRId MplsLsrId, 723 mplsTunnelName DisplayString, 724 mplsTunnelDescr DisplayString, 725 mplsTunnelIsIf TruthValue, 726 mplsTunnelIfIndex InterfaceIndexOrZero, 727 mplsTunnelXCPointer RowPointer, 728 mplsTunnelSignallingProto INTEGER, 729 mplsTunnelSetupPrio INTEGER, 730 mplsTunnelHoldingPrio INTEGER, 731 mplsTunnelSessionAttributes BITS, 732 mplsTunnelOwner INTEGER, 733 mplsTunnelLocalProtectInUse TruthValue, 734 mplsTunnelResourcePointer RowPointer, 735 mplsTunnelInstancePriority Unsigned32, 736 mplsTunnelHopTableIndex MplsPathIndexOrZero, 737 mplsTunnelARHopTableIndex MplsPathIndexOrZero, 738 mplsTunnelCHopTableIndex MplsPathIndexOrZero, 739 mplsTunnelPrimaryInstance MplsTunnelInstanceIndex, 740 mplsTunnelPrimaryTimeUp TimeTicks, 741 mplsTunnelPathChanges Counter32, 742 mplsTunnelLastPathChange TimeTicks, 743 mplsTunnelCreationTime TimeStamp, 744 mplsTunnelStateTransitions Unsigned32, 745 mplsTunnelIncludeAnyAffinity Unsigned32, 746 mplsTunnelIncludeAllAffinity Unsigned32, 747 mplsTunnelExcludeAllAffinity Unsigned32, 748 mplsTunnelPathInUse MplsPathIndexOrZero, 749 mplsTunnelRole INTEGER, 750 mplsTunnelTotalUpTime TimeTicks, 751 mplsTunnelInstanceUpTime TimeTicks, 752 mplsTunnelAdminStatus INTEGER, 753 mplsTunnelOperStatus INTEGER, 754 mplsTunnelRowStatus RowStatus, 755 mplsTunnelStorageType StorageType 756 } 758 mplsTunnelIndex OBJECT-TYPE 759 SYNTAX MplsTunnelIndex 760 MAX-ACCESS accessible-for-notify 761 STATUS current 762 DESCRIPTION 763 "Uniquely identifies this row." 764 ::= { mplsTunnelEntry 1 } 766 mplsTunnelInstance OBJECT-TYPE 767 SYNTAX MplsTunnelInstanceIndex 768 MAX-ACCESS accessible-for-notify 769 STATUS current 770 DESCRIPTION 771 "Uniquely identifies an instance of a tunnel. It is 772 useful to identify multiple instances of tunnels 773 for the purposes of backup and parallel tunnels." 774 ::= { mplsTunnelEntry 2 } 776 mplsTunnelIngressLSRId OBJECT-TYPE 777 SYNTAX MplsLsrId 778 MAX-ACCESS accessible-for-notify 779 STATUS current 780 DESCRIPTION 781 "The purpose of this object is to uniquely identity 782 a tunnel within a network. When the MPLS 783 signalling protoocol is rsvp(2) this value should 784 mimic the Extended Tunnel Id field in the Session 785 object. When the MPLS signalling protoocol is 786 crldp(3) this value should mimic the Ingress LSR 787 Router ID field in the LSPID TLV object." 788 REFERENCE 789 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 790 Awduche et al, Internet Draft , August 2000., 792 2. Constraint-Based LSP Setup using LDP, Jamoussi, 793 Internet Draft , 794 July 2000." 795 ::= { mplsTunnelEntry 3 } 797 mplsTunnelEgressLSRId OBJECT-TYPE 798 SYNTAX MplsLsrId 799 MAX-ACCESS accessible-for-notify 800 STATUS current 801 DESCRIPTION 802 "Specifies the egress LSR Id." 803 ::= { mplsTunnelEntry 4 } 805 mplsTunnelName OBJECT-TYPE 806 SYNTAX DisplayString 807 MAX-ACCESS read-create 808 STATUS current 809 DESCRIPTION 810 "The canonical name assigned to the tunnel. This 811 name can be used to refer to the tunnel on the 812 LSR�s console port. If mplsTunnelIsIf is set to 813 true then the ifName of the interface 814 corresponding to this tunnel should have a value 815 equal to mplsTunnelName. Also see the description 816 of ifName in RFC 2233." 817 REFERENCE 818 "RFC 2233 - The Interfaces Group MIB using SMIv2, 819 McCloghrie, K., and F. Kastenholtz, Nov. 1997" 820 ::= { mplsTunnelEntry 5 } 822 mplsTunnelDescr OBJECT-TYPE 823 SYNTAX DisplayString 824 MAX-ACCESS read-create 825 STATUS current 826 DESCRIPTION 827 "A textual string containing information about the 828 tunnel. If there is no description this object 829 contains a zero length string." 830 ::= { mplsTunnelEntry 6 } 832 mplsTunnelIsIf OBJECT-TYPE 833 SYNTAX TruthValue 834 MAX-ACCESS read-create 835 STATUS current 836 DESCRIPTION 837 "Denotes whether or not this tunnel corresponds to 838 an interface represented in the interfaces group 839 table. Note that if this variable is set to true 840 then the ifName of the interface corresponding to 841 this tunnel should have a value equal to 842 mplsTunnelName. Also see the description of 843 ifName in RFC 2233." 844 REFERENCE 845 "RFC 2233 - The Interfaces Group MIB using SMIv2, 846 McCloghrie, K., and F. Kastenholtz, Nov. 1997" 847 DEFVAL { false } 848 ::= { mplsTunnelEntry 7 } 850 mplsTunnelIfIndex OBJECT-TYPE 851 SYNTAX InterfaceIndexOrZero 852 MAX-ACCESS read-only 853 STATUS current 854 DESCRIPTION 855 "If mplsTunnelIsIf is set to true, then this value 856 contains the LSR-assigned ifIndex which 857 corresponds to an entry in the interfaces table. 858 Otherwise this variable should contain the value 859 of zero indicating that a valid ifIndex was not 860 assigned to this tunnel interface." 861 REFERENCE 862 "RFC 2233 - The Interfaces Group MIB using SMIv2, 863 McCloghrie, K., and F. Kastenholtz, Nov. 1997" 864 ::= { mplsTunnelEntry 8 } 866 mplsTunnelXCPointer OBJECT-TYPE 867 SYNTAX RowPointer 868 MAX-ACCESS read-create 869 STATUS current 870 DESCRIPTION 871 "This variable points to a row in the mplsXCTable. 872 This table identifies the segments that compose 873 this tunnel, their characteristics, and 874 relationships to each other. A value of 875 zeroDotZero indicates that no LSP has been 876 associated with this tunnel yet." 877 REFERENCE 878 "Srinivasan, C., Viswanathan, A., and T. Nadeau, 879 MPLS Label Switch Router Management Information 880 Base Using SMIv2, Internet Draft , July 2000." 882 ::= { mplsTunnelEntry 9 } 884 mplsTunnelSignallingProto OBJECT-TYPE 885 SYNTAX INTEGER { 886 none(1), 887 rsvp(2), 888 crldp(3), 889 other(4) 890 } 891 MAX-ACCESS read-create 892 STATUS current 893 DESCRIPTION 894 "The signaling protocol, if any, which was used to 895 setup this tunnel." 896 DEFVAL { none } 897 ::= { mplsTunnelEntry 10 } 899 mplsTunnelSetupPrio OBJECT-TYPE 900 SYNTAX INTEGER (0..7) 901 MAX-ACCESS read-create 902 STATUS current 903 DESCRIPTION 904 "Indicates the setup priority of this tunnel." 905 REFERENCE 906 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 907 Awduche et al, Internet Draft , August 2000., 909 2. Constraint-Based LSP Setup using LDP, Jamoussi, 910 Internet Draft , 911 July 2000." 912 ::= { mplsTunnelEntry 11 } 914 mplsTunnelHoldingPrio OBJECT-TYPE 915 SYNTAX INTEGER (0..7) 916 MAX-ACCESS read-create 917 STATUS current 918 DESCRIPTION 919 "Indicates the holding priority for this tunnel." 920 REFERENCE 921 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 922 Awduche et al, Internet Draft , August 2000., 924 2. Constraint-Based LSP Setup using LDP, Jamoussi, 925 Internet Draft , 926 July 2000." 927 ::= { mplsTunnelEntry 12 } 929 mplsTunnelSessionAttributes OBJECT-TYPE 930 SYNTAX BITS { 931 fastReroute (0), 932 mergingPermitted (1), 933 isPersistent (2), 934 isPinned (3), 935 isComputed (4), 936 recordRoute(5) 937 } 938 MAX-ACCESS read-create 939 STATUS current 940 DESCRIPTION 941 "This bitmask indicates optional session values for 942 this tunnel. The following describes these 943 bitfields: 945 fastRerouteThis flag indicates that the any tunnel 946 hop may choose to reroute this tunnel without 947 tearing it down. 948 This flag permits transit routers to use a local 949 repair mechanism which may result in violation of 950 the explicit routing of this tunnel. When a fault 951 is detected on an adjacent downstream link or 952 node, a transit router can reroute traffic for 953 fast service restoration. 955 mergingPermitted This flag permits transit routers 956 to merge this session with other RSVP sessions for 957 the purpose of reducing resource overhead on 958 downstream transit routers, thereby providing 959 better network scalability. 961 isPersistent Indicates whether this tunnel should 962 be restored automatically after a failure occurs. 964 isPinned This flag indicates whether the loose- 965 routed hops of this tunnel are to be pinned. 967 isComputed This flag indicates whether the tunnel 968 path is computed using a constraint-based routing 969 algorithm based on the mplsTunnelHopTable entries. 971 recordRoute This flag indicates 972 whether or not the signaling protocol should 973 remember the tunnel path after it has been 974 signaled." 976 REFERENCE 977 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 978 Awduche et al, Internet Draft , August 2000." 980 DEFVAL { 0 } 981 ::= { mplsTunnelEntry 13 } 983 mplsTunnelOwner OBJECT-TYPE 984 SYNTAX INTEGER { 985 -- represents all management entities 986 admin(1), 987 rsvp(2), 988 crldp(3), 989 policyAgent(4), 990 other(5) 991 } 992 MAX-ACCESS read-create 993 STATUS current 994 DESCRIPTION 995 "Indicates which protocol created and is 996 responsible for managing this tunnel. Values 997 rsvp(2) and crldp(3) should not be used at the 998 head-end of a MPLS tunnel." 999 ::= { mplsTunnelEntry 14 } 1001 mplsTunnelLocalProtectInUse OBJECT-TYPE 1002 SYNTAX TruthValue 1003 MAX-ACCESS read-create 1004 STATUS current 1005 DESCRIPTION 1006 "Indicates that the local repair mechanism is in 1007 use to maintain this tunnel (usually in the face 1008 of an outage of the link it was previously routed 1009 over)." 1010 ::= { mplsTunnelEntry 15 } 1012 mplsTunnelResourcePointer OBJECT-TYPE 1013 SYNTAX RowPointer 1014 MAX-ACCESS read-create 1015 STATUS current 1016 DESCRIPTION 1017 "This variable represents a pointer to the traffic 1018 parameter specification for this tunnel. This 1019 value may point at an entry in the 1020 mplsTunnelResourceEntry to indicate which 1021 mplsTunnelResourceEntry is to be assigned to this 1022 segment. This value may optionally point at an 1023 externally defined traffic parameter specification 1024 table. A value of zeroDotZero indicates best- 1025 effort treatment. By having the same value of 1026 this object, two or more segments can indicate 1027 resource sharing." 1028 ::= { mplsTunnelEntry 16 } 1030 mplsTunnelInstancePriority OBJECT-TYPE 1031 SYNTAX Unsigned32 1032 MAX-ACCESS read-create 1033 STATUS current 1034 DESCRIPTION 1035 "This value indicates which priority, in descending 1036 order, with 0 indicating the lowest priority, 1037 within a group of tunnel instances. A group of 1038 tunnel instances is defined as a set of tunnels 1039 with the same mplsTunnelIndex in this table, but 1040 with a different mplsTunnelInstance. Tunnel group 1041 priorities are used to denote the priority at 1042 which a particular tunnel instance will supercede 1043 another. Instances of tunnels containing the same 1044 mplsTunnelInstancePriority will be used for load 1045 sharing." 1046 DEFVAL { 0 } 1047 ::= { mplsTunnelEntry 17 } 1049 mplsTunnelHopTableIndex OBJECT-TYPE 1050 SYNTAX MplsPathIndexOrZero 1051 MAX-ACCESS read-create 1052 STATUS current 1053 DESCRIPTION 1054 "Index into the mplsTunnelHopTable entry that 1055 specifies the explicit route hops for this 1056 tunnel." 1057 ::= { mplsTunnelEntry 18 } 1059 mplsTunnelARHopTableIndex OBJECT-TYPE 1060 SYNTAX MplsPathIndexOrZero 1061 MAX-ACCESS read-only 1062 STATUS current 1063 DESCRIPTION 1064 "Index into the mplsTunnelARHopTable entry that 1065 specifies the actual hops traversed by the 1066 tunnel." 1067 ::= { mplsTunnelEntry 19 } 1069 mplsTunnelCHopTableIndex OBJECT-TYPE 1070 SYNTAX MplsPathIndexOrZero 1071 MAX-ACCESS read-only 1072 STATUS current 1073 DESCRIPTION 1074 "Index into the mplsTunnelCHopTable entry that 1075 specifies the computed hops traversed by the 1076 tunnel." 1077 ::= { mplsTunnelEntry 20 } 1079 mplsTunnelPrimaryInstance OBJECT-TYPE 1080 SYNTAX MplsTunnelInstanceIndex 1081 MAX-ACCESS read-only 1082 STATUS current 1083 DESCRIPTION 1084 "Specifies the instance index of the primary 1085 instance of this tunnel." 1086 ::= { mplsTunnelEntry 21 } 1088 mplsTunnelPrimaryTimeUp OBJECT-TYPE 1089 SYNTAX TimeTicks 1090 MAX-ACCESS read-only 1091 STATUS current 1092 DESCRIPTION 1093 "Specifies the total time the primary instance of 1094 this tunnel has been active. The primary instance 1095 of this tunnel is defined in 1096 mplsTunnelPrimaryInstance." 1097 ::= { mplsTunnelEntry 22 } 1099 mplsTunnelPathChanges OBJECT-TYPE 1100 SYNTAX Counter32 1101 MAX-ACCESS read-only 1102 STATUS current 1103 DESCRIPTION 1104 "Specifies the number of times the paths has 1105 changed for this tunnel." 1106 ::= { mplsTunnelEntry 23 } 1108 mplsTunnelLastPathChange OBJECT-TYPE 1109 SYNTAX TimeTicks 1110 MAX-ACCESS read-only 1111 STATUS current 1112 DESCRIPTION 1113 "Specifies the time since the last path change for 1114 this tunnel." 1115 ::= { mplsTunnelEntry 24 } 1117 mplsTunnelCreationTime OBJECT-TYPE 1118 SYNTAX TimeStamp 1119 MAX-ACCESS read-only 1120 STATUS current 1121 DESCRIPTION 1122 "Specifies the value of SysUpTime when the first 1123 instance of this tunnel came into existence." 1124 ::= { mplsTunnelEntry 25 } 1126 mplsTunnelStateTransitions OBJECT-TYPE 1127 SYNTAX Counter32 1128 MAX-ACCESS read-only 1129 STATUS current 1130 DESCRIPTION 1131 "Specifies the number of times the state of this 1132 tunnel instance has changed." 1133 ::= { mplsTunnelEntry 26 } 1135 mplsTunnelIncludeAnyAffinity OBJECT-TYPE 1136 SYNTAX Unsigned32 1137 MAX-ACCESS read-create 1138 STATUS current 1139 DESCRIPTION 1140 "A link satisfies the include-any constraint if and 1141 only if the constraint is zero, or the link and 1142 the constraint have a resource class in common." 1143 REFERENCE "RSVP-TE: Extensions to RSVP for LSP 1144 Tunnels, 1145 draft-ietf-mpls-rsvp-lsp-tunnel-07.txt" 1146 ::= { mplsTunnelEntry 27 } 1148 mplsTunnelIncludeAllAffinity OBJECT-TYPE 1149 SYNTAX Unsigned32 1150 MAX-ACCESS read-create 1151 STATUS current 1152 DESCRIPTION 1153 "A link satisfies the include-all constraint if and 1154 only if the link contains all of the adminstrative 1155 groups specified in the constraint." 1156 REFERENCE "RSVP-TE: Extensions to RSVP for LSP 1157 Tunnels, draft-ietf-mpls-rsvp-lsp-tunnel-07.txt" 1158 ::= { mplsTunnelEntry 28 } 1160 mplsTunnelExcludeAllAffinity OBJECT-TYPE 1161 SYNTAX Unsigned32 1162 MAX-ACCESS read-create 1163 STATUS current 1164 DESCRIPTION 1165 "A link satisfies the exclude-all constraint if and 1166 only if the link contains none of the 1167 adminstrative groups specifie in the constraint." 1168 REFERENCE "RSVP-TE: Extensions to RSVP for LSP 1169 Tunnels, draft-ietf-mpls-rsvp-lsp-tunnel-07.txt" 1170 ::= { mplsTunnelEntry 29 } 1172 mplsTunnelPathInUse OBJECT-TYPE 1173 SYNTAX MplsPathIndexOrZero 1174 MAX-ACCESS read-create 1175 STATUS current 1176 DESCRIPTION 1177 "This value denotes the configured path that was 1178 chosen for this tunnel. This value reflects the 1179 secondary index into the TunnelHopTable. This path 1180 may not exactly match the one in the ARHopTable 1181 due to the fact that some CSPF modification may 1182 have taken place. See the ARHopTable for the 1183 actual path being taken by the tunnel. A value of 1184 zero denotes that no path is currently in use or 1185 available." 1186 ::= { mplsTunnelEntry 30 } 1188 mplsTunnelRole OBJECT-TYPE 1189 SYNTAX INTEGER { head(1), transit(2), tail(3) } 1190 MAX-ACCESS read-create 1191 STATUS current 1192 DESCRIPTION 1193 "This value signifies the role that this tunnel 1194 entry/instance represents. This value MUST be set 1195 to head(1) at the originating point of the tunnel. 1196 This value MUST be set to transit(2) at transit 1197 points along the tunnel, if transit points are 1198 supported. This value MUST be set to tail(3) at 1199 the terminating point of the tunnel if tunnel 1200 tails are supported." 1201 ::= { mplsTunnelEntry 31 } 1203 mplsTunnelTotalUpTime OBJECT-TYPE 1204 SYNTAX TimeTicks 1205 MAX-ACCESS read-create 1206 STATUS current 1207 DESCRIPTION 1208 "This value represents the aggregate up time for 1209 all instances of this tunnel, if available. If 1210 this value is unavailable, it MUST return a value 1211 of 0." 1212 ::= { mplsTunnelEntry 32 } 1214 mplsTunnelInstanceUpTime OBJECT-TYPE 1215 SYNTAX TimeTicks 1216 MAX-ACCESS read-create 1217 STATUS current 1218 DESCRIPTION 1219 "This value identifies the total time that this 1220 tunnel instance's operStatus has been Up(1)." 1221 ::= { mplsTunnelEntry 33 } 1223 mplsTunnelAdminStatus OBJECT-TYPE 1224 SYNTAX INTEGER { 1225 -- ready to pass packets 1226 up(1), 1227 down(2), 1228 -- in some test mode 1229 testing(3) 1230 } 1231 MAX-ACCESS read-create 1232 STATUS current 1233 DESCRIPTION 1234 "Indicates the desired operational status of this 1235 tunnel." 1236 ::= { mplsTunnelEntry 34 } 1238 mplsTunnelOperStatus OBJECT-TYPE 1239 SYNTAX INTEGER { 1240 -- ready to pass packets 1241 up(1), 1242 down(2), 1243 -- in some test mode 1244 testing(3), 1245 -- status cannot be determined 1246 unknown(4), 1247 dormant(5), 1248 -- some component is missing 1249 notPresent(6), 1250 -- down due to the state of 1251 -- lower layer interfaces 1252 lowerLayerDown(7) 1253 } 1254 MAX-ACCESS read-only 1255 STATUS current 1256 DESCRIPTION 1257 "Indicates the actual operational status of this 1258 tunnel, which is typically but not limited to, a 1259 function of the state of individual segments of 1260 this tunnel." 1261 ::= { mplsTunnelEntry 35 } 1263 mplsTunnelRowStatus OBJECT-TYPE 1264 SYNTAX RowStatus 1265 MAX-ACCESS read-create 1266 STATUS current 1267 DESCRIPTION 1268 "This variable is used to create, modify, and/or 1269 delete a row in this table." 1270 ::= { mplsTunnelEntry 36 } 1272 mplsTunnelStorageType OBJECT-TYPE 1273 SYNTAX StorageType 1274 MAX-ACCESS read-create 1275 STATUS current 1276 DESCRIPTION 1277 "This variable indicates the storage type for this 1278 object." 1279 ::= { mplsTunnelEntry 37 } 1281 -- End of mplsTunnelTable 1283 mplsTunnelHopListIndexNext OBJECT-TYPE 1284 SYNTAX Unsigned32 (0..2147483647) 1285 MAX-ACCESS read-only 1286 STATUS current 1287 DESCRIPTION 1288 "This object contains an appropriate value to be 1289 used for mplsTunnelHopListIndex when creating 1290 entries in the mplsTunnelHopTable. If the number 1291 of unassigned entries is exhausted, a retrival 1292 operation will return a value of 0. This object 1293 may also return a value of 0 when the LSR is 1294 unable to accept conceptual row creation, for 1295 example, if the mplsTunnelHopTable is implemented 1296 as read-only. To obtain the value of 1297 mplsTunnelHopListIndex for a new entry in the 1298 mplsTunnelHopTable, the manager issues a 1299 management protocol retrieval operation to obtain 1300 the current value of mplsTunnelHopIndex. After 1301 each retrieval operation, the agent should modify 1302 the value to reflect the next unassigned index. 1303 After a manager retrieves a value the agent will 1304 determine through its local policy when this index 1305 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 1314 hops, strict or loose, for an MPLS tunnel defined 1315 in 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 1320 to 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. 1336 An entry is created by a network administrator for 1337 signaled ERLSP set up by an MPLS signaling 1338 protocol." 1339 INDEX { mplsTunnelHopListIndex, mplsTunnelPathOptionIndex, 1340 mplsTunnelHopIndex } 1341 ::= { mplsTunnelHopTable 1 } 1343 MplsTunnelHopEntry ::= SEQUENCE { 1344 mplsTunnelHopListIndex MplsPathIndex, 1345 mplsTunnelPathOptionIndex MplsPathIndex, 1346 mplsTunnelHopIndex MplsPathIndex, 1347 mplsTunnelHopAddrType INTEGER, 1348 mplsTunnelHopIpv4Addr InetAddressIPv4, 1349 mplsTunnelHopIpv4PrefixLen Unsigned32, 1350 mplsTunnelHopIpv6Addr InetAddressIPv6, 1351 mplsTunnelHopIpv6PrefixLen Unsigned32, 1352 mplsTunnelHopAsNumber Unsigned32, 1353 mplsTunnelHopLspId MplsLSPID, 1354 mplsTunnelHopType INTEGER, 1355 mplsTunnelHopRowStatus RowStatus, 1356 mplsTunnelHopStorageType StorageType 1357 } 1359 mplsTunnelHopListIndex OBJECT-TYPE 1360 SYNTAX MplsPathIndex 1361 MAX-ACCESS not-accessible 1362 STATUS current 1363 DESCRIPTION 1364 "Primary index into this table identifying a 1365 particular explicit route object." 1366 ::= { mplsTunnelHopEntry 1 } 1368 mplsTunnelPathOptionIndex OBJECT-TYPE 1369 SYNTAX MplsPathIndex 1370 MAX-ACCESS not-accessible 1371 STATUS current 1372 DESCRIPTION 1373 "Secondary index into this table identifying a 1374 particular group of hops representing a particular 1375 configured path. This is otherwise known as a path 1376 option." 1377 ::= { mplsTunnelHopEntry 2 } 1379 mplsTunnelHopIndex OBJECT-TYPE 1380 SYNTAX MplsPathIndex 1381 MAX-ACCESS not-accessible 1382 STATUS current 1383 DESCRIPTION 1384 "Secondary index into this table identifying a 1385 particular hop." 1386 ::= { mplsTunnelHopEntry 3 } 1388 mplsTunnelHopAddrType OBJECT-TYPE 1389 SYNTAX INTEGER { 1390 ipV4(1), 1391 ipV6(2), 1392 asNumber(3), 1393 lspid(4) 1394 } 1395 MAX-ACCESS read-create 1396 STATUS current 1397 DESCRIPTION 1398 "Denotes the address type of this tunnel hop." 1399 DEFVAL { ipV4 } 1400 ::= { mplsTunnelHopEntry 4 } 1402 mplsTunnelHopIpv4Addr OBJECT-TYPE 1403 SYNTAX InetAddressIPv4 1404 MAX-ACCESS read-create 1405 STATUS current 1406 DESCRIPTION 1407 "If mplsTunnelHopAddrType is set to ipV4(1), then 1408 this value will contain the IPv4 address of this 1409 hop. This object is otherwise insignificant and 1410 should contain a value of 0." 1411 ::= { mplsTunnelHopEntry 5 } 1413 mplsTunnelHopIpv4PrefixLen OBJECT-TYPE 1414 SYNTAX Unsigned32 (0..32) 1415 MAX-ACCESS read-create 1416 STATUS current 1417 DESCRIPTION 1418 "If mplsTunnelHopAddrType is ipV4(1), then the 1419 prefix length for this hop's IPv4 address is 1420 contained herein. This object is otherwise 1421 insignificant and should contain a value of 0." 1422 ::= { mplsTunnelHopEntry 6 } 1424 mplsTunnelHopIpv6Addr OBJECT-TYPE 1425 SYNTAX InetAddressIPv6 1426 MAX-ACCESS read-create 1427 STATUS current 1428 DESCRIPTION 1429 "If the mplsTunnelHopAddrType is set to ipV6(2), 1430 then this variable contains the IPv6 address of 1431 this hop. This object is otherwise insignificant 1432 and should contain a value of 0." 1433 ::= { mplsTunnelHopEntry 7 } 1435 mplsTunnelHopIpv6PrefixLen OBJECT-TYPE 1436 SYNTAX Unsigned32 (0..128) 1437 MAX-ACCESS read-create 1438 STATUS current 1439 DESCRIPTION 1440 "If mplsTunnelHopAddrType is set to ipV6(2), this 1441 value will contain the prefix length for this 1442 hop's IPv6 address. This object is otherwise 1443 insignificant and should contain a value of 0." 1444 ::= { mplsTunnelHopEntry 8 } 1446 mplsTunnelHopAsNumber OBJECT-TYPE 1447 SYNTAX Unsigned32 (0..65535) 1448 MAX-ACCESS read-create 1449 STATUS current 1450 DESCRIPTION 1451 "If mplsTunnelHopAddrType is set to asNumber(3), 1452 then this value will contain the AS number of this 1453 hop. This object is otherwise insignificant and 1454 should contain a value of 0 to indicate this 1455 fact." 1456 ::= { mplsTunnelHopEntry 9 } 1458 mplsTunnelHopLspId OBJECT-TYPE 1459 SYNTAX MplsLSPID 1460 MAX-ACCESS read-create 1461 STATUS current 1462 DESCRIPTION 1463 "If mplsTunnelHopAddrType is set to lspid(4), then 1464 this value will contain the LSPID of a tunnel of 1465 this hop. The present tunnel being configured is 1466 �tunneled� through this hop (using label 1467 stacking). This object is otherwise insignificant 1468 and should contain a value of 0 to indicate this 1469 fact." 1470 ::= { mplsTunnelHopEntry 10 } 1472 mplsTunnelHopType OBJECT-TYPE 1473 SYNTAX INTEGER { 1474 strict(1), 1475 loose(2) 1476 } 1477 MAX-ACCESS read-create 1478 STATUS current 1479 DESCRIPTION 1480 "Denotes whether this tunnel hop is routed in a 1481 strict or loose fashion." 1482 ::= { mplsTunnelHopEntry 11 } 1484 mplsTunnelHopRowStatus OBJECT-TYPE 1485 SYNTAX RowStatus 1486 MAX-ACCESS read-create 1487 STATUS current 1488 DESCRIPTION 1489 "This variable is used to create, modify, and/or 1490 delete a row in this table." 1491 ::= { mplsTunnelHopEntry 12 } 1493 mplsTunnelHopStorageType OBJECT-TYPE 1494 SYNTAX StorageType 1495 MAX-ACCESS read-create 1496 STATUS current 1497 DESCRIPTION 1498 "This variable indicates the storage type for this 1499 object." 1500 ::= { mplsTunnelHopEntry 13 } 1502 -- End of mplsTunnelHopTable 1504 -- Begin of mplsTunnelResourceTable 1506 mplsTunnelResourceIndexNext OBJECT-TYPE 1507 SYNTAX Unsigned32 (0.. 2147483647) 1508 MAX-ACCESS read-only 1509 STATUS current 1510 DESCRIPTION 1511 "This object contains the next appropriate value to 1512 be used for mplsTunnelResourceIndex when creating 1513 entries in the mplsTunnelResourceTable. If the 1514 number of unassigned entries is exhausted, a 1515 retrival operation will return a value of 0. This 1516 object may also return a value of 0 when the LSR 1517 is unable to accept conceptual row creation, for 1518 example, if the mplsTunnelTable is implemented as 1519 read-only. To obtain the mplsTunnelResourceIndex 1520 value for a new entry, the manager must first 1521 issue a management protocol retrieval operation to 1522 obtain the current value of this object. The agent 1523 should modify the value to reflect the next 1524 unassigned index after each retrieval operation. 1525 After a manager retrieves a value the agent will 1526 determine through its local policy when this index 1527 value will be made available for reuse." 1528 ::= { mplsTeObjects 5 } 1530 mplsTunnelResourceTable OBJECT-TYPE 1531 SYNTAX SEQUENCE OF MplsTunnelResourceEntry 1532 MAX-ACCESS not-accessible 1533 STATUS current 1534 DESCRIPTION 1535 "The mplsTunnelResourceTable allows a manager to 1536 specify which resources are desired for an MPLS 1537 tunnel. This table also allows several tunnels to 1538 point to a single entry in this table, implying 1539 that these tunnels should share resources." 1540 ::= { mplsTeObjects 6 } 1542 mplsTunnelResourceEntry OBJECT-TYPE 1543 SYNTAX MplsTunnelResourceEntry 1544 MAX-ACCESS not-accessible 1545 STATUS current 1546 DESCRIPTION 1547 "An entry in this table represents a set of 1548 resources for an MPLS tunnel. An entry can be 1549 created by a network administrator or by an SNMP 1550 agent as instructed by any MPLS signaling 1551 protocol." 1552 INDEX { mplsTunnelResourceIndex } 1553 ::= { mplsTunnelResourceTable 1 } 1555 MplsTunnelResourceEntry ::= SEQUENCE { 1556 mplsTunnelResourceIndex Unsigned32, 1557 mplsTunnelResourceMaxRate MplsBitRate, 1558 mplsTunnelResourceMeanRate MplsBitRate, 1559 mplsTunnelResourceMaxBurstSize MplsBurstSize, 1560 mplsTunnelResourceRowStatus RowStatus, 1561 mplsTunnelResourceStorageType StorageType 1562 } 1564 mplsTunnelResourceIndex OBJECT-TYPE 1565 SYNTAX Unsigned32 (1..2147483647) 1566 MAX-ACCESS not-accessible 1567 STATUS current 1568 DESCRIPTION 1569 "Uniquely identifies this row." 1570 ::= { mplsTunnelResourceEntry 1 } 1572 mplsTunnelResourceMaxRate OBJECT-TYPE 1573 SYNTAX MplsBitRate 1574 UNITS "bits per second" 1575 MAX-ACCESS read-create 1576 STATUS current 1577 DESCRIPTION 1578 "The maximum rate in bits/second. Note that 1579 setting mplsTunnelResourceMaxRate, 1580 mplsTunnelResourceMeanRate, and 1581 mplsTunnelResourceMaxBurstSize to 0 indicates best- 1582 effort treatment. 1583 This object is copied to an instance of 1584 mplsTrafficParamMaxRate in mplsTrafficParamTable 1585 the OID of which is copied into the corresponding 1586 mplsInSegmentTrafficParamPtr." 1587 REFERENCE 1588 "Srinivasan, C., Viswanathan, A., and T. Nadeau, 1589 MPLS Label Switch Router Management Information 1590 Base Using SMIv2, Internet Draft , July 2000." 1592 ::= { mplsTunnelResourceEntry 2 } 1594 mplsTunnelResourceMeanRate OBJECT-TYPE 1595 SYNTAX MplsBitRate 1596 UNITS "bits per second" 1597 MAX-ACCESS read-create 1598 STATUS current 1599 DESCRIPTION 1600 "This object is copied into an instance of 1601 mplsTrafficParamMeanRate in the 1602 mplsTrafficParamTable. The OID of this table entry 1603 is then copied into the corresponding 1604 mplsInSegmentTrafficParamPtr. 1606 When resource allocation is performed as requested 1607 by this TSpec object, it is copied into an entry 1608 in mplsTrafficParamTable [LSRMIB]: 1609 mplsTunnelInMeanRate to mplsTrafficParamMeanRate. 1610 The OID of this entry is copied to 1611 mplsInSegmentTrafficParamPtr of the corresponding 1612 in-segment entry." 1614 REFERENCE 1615 "Srinivasan, C., Viswanathan, A., and T. Nadeau, 1616 MPLS Label Switch Router Management Information 1617 Base Using SMIv2, Internet Draft , July 2000." 1619 ::= { mplsTunnelResourceEntry 3 } 1621 mplsTunnelResourceMaxBurstSize OBJECT-TYPE 1622 SYNTAX MplsBurstSize 1623 UNITS "bytes" 1624 MAX-ACCESS read-create 1625 STATUS current 1626 DESCRIPTION 1627 "The maximum burst size in bytes. This object is 1628 copied to mplsInSegmentMaxBurstSize of the 1629 corresponding in-segment. 1631 When resource allocation is performed as requested 1632 by this TSpec object, it is copied into an entry 1633 in mplsTrafficParamTable [LSRMIB]: 1634 mplsTunnelInMaxBurstSize to 1635 mplsTrafficParamMaxBurstSize. The OID of this 1636 entry is copied to mplsInSegmentTrafficParamPtr of 1637 the corresponding in-segment entry." 1638 REFERENCE 1639 "Srinivasan, C., Viswanathan, A., and T. Nadeau, 1640 MPLS Label Switch Router Management Information 1641 Base Using SMIv2, Internet Draft , July 2000." 1643 ::= { mplsTunnelResourceEntry 4 } 1645 mplsTunnelResourceRowStatus OBJECT-TYPE 1646 SYNTAX RowStatus 1647 MAX-ACCESS read-create 1648 STATUS current 1649 DESCRIPTION 1650 "This variable is used to create, modify, and/or 1651 delete a row in this table." 1652 ::= { mplsTunnelResourceEntry 5 } 1654 mplsTunnelResourceStorageType OBJECT-TYPE 1655 SYNTAX StorageType 1656 MAX-ACCESS read-create 1657 STATUS current 1658 DESCRIPTION 1659 "This variable indicates the storage type for this 1660 object." 1661 ::= { mplsTunnelResourceEntry 6 } 1663 -- End mplsTunnelResourceTable 1665 -- Tunnel Actual Route Hop table. 1667 mplsTunnelARHopTable OBJECT-TYPE 1668 SYNTAX SEQUENCE OF MplsTunnelARHopEntry 1669 MAX-ACCESS not-accessible 1670 STATUS current 1671 DESCRIPTION 1672 "The mplsTunnelARHopTable is used to indicate the 1673 hops, strict or loose, for an MPLS tunnel defined 1674 in mplsTunnelTable, as reported by the MPLS 1675 signaling protocol, for the outgoing direction of 1676 the tunnel. Each row in this table is indexed by 1677 mplsTunnelARHopListIndex. Each row also has a 1678 secondary index mplsTunnelARHopIndex, 1679 corresponding to the next hop that this row 1680 corresponds to. The first row in the table is the 1681 first hop after the origination point of the 1682 tunnel. In case we want to specify a particular 1683 interface on the originating LSR of an outgoing 1684 tunnel by which we want packets to exit the LSR, 1685 we specify this as the first hop for this tunnel 1686 in mplsTunnelARHopTable. 1688 Please note that since the information necessary 1689 to build entries within this table are not 1690 provided by some MPLS signaling protocols, 1691 implementation of this table is optional. 1692 Furthermore, since the information in this table 1693 is actually provided by the MPLS signaling 1694 protocol after the path has been set-up, the 1695 entries in this table are provided only for 1696 observation, and hence, all variables in this 1697 table are accessible exclusively as read-only." 1698 ::= { mplsTeObjects 7 } 1700 mplsTunnelARHopEntry OBJECT-TYPE 1701 SYNTAX MplsTunnelARHopEntry 1702 MAX-ACCESS not-accessible 1703 STATUS current 1704 DESCRIPTION 1705 "An entry in this table represents a tunnel hop. 1706 An entry is created by a network administrator for 1707 signaled ERLSP set up by an MPLS signaling 1708 protocol." 1709 INDEX { mplsTunnelARHopListIndex, mplsTunnelARHopIndex } 1710 ::= { mplsTunnelARHopTable 1 } 1712 MplsTunnelARHopEntry ::= SEQUENCE { 1713 mplsTunnelARHopListIndex MplsPathIndex, 1714 mplsTunnelARHopIndex MplsPathIndex, 1715 mplsTunnelARHopAddrType INTEGER, 1716 mplsTunnelARHopIpv4Addr InetAddressIPv4, 1717 mplsTunnelARHopIpv4PrefixLen Unsigned32, 1718 mplsTunnelARHopIpv6Addr InetAddressIPv6, 1719 mplsTunnelARHopIpv6PrefixLen Unsigned32, 1720 mplsTunnelARHopAsNumber Unsigned32, 1721 mplsTunnelARHopType INTEGER 1723 } 1725 mplsTunnelARHopListIndex OBJECT-TYPE 1726 SYNTAX MplsPathIndex 1727 MAX-ACCESS not-accessible 1728 STATUS current 1729 DESCRIPTION 1730 "Primary index into this table identifying a 1731 particular recorded hop list." 1732 ::= { mplsTunnelARHopEntry 1 } 1734 mplsTunnelARHopIndex OBJECT-TYPE 1735 SYNTAX MplsPathIndex 1736 MAX-ACCESS not-accessible 1737 STATUS current 1738 DESCRIPTION 1739 "Secondary index into this table identifying the 1740 particular hop." 1741 ::= { mplsTunnelARHopEntry 2 } 1743 mplsTunnelARHopAddrType OBJECT-TYPE 1744 SYNTAX INTEGER { 1745 ipV4(1), 1746 ipV6(2), 1747 asNumber(3) 1748 } 1749 MAX-ACCESS read-only 1750 STATUS current 1751 DESCRIPTION 1752 "Denotes the address type of this tunnel hop." 1753 DEFVAL { ipV4 } 1754 ::= { mplsTunnelARHopEntry 3 } 1756 mplsTunnelARHopIpv4Addr OBJECT-TYPE 1757 SYNTAX InetAddressIPv4 1758 MAX-ACCESS read-only 1759 STATUS current 1760 DESCRIPTION 1761 "If mplsTunnelARHopAddrType is set to ipV4(1), then 1762 this value will contain the IPv4 address of this 1763 hop. This object is otherwise insignificant and 1764 should contain a value of 0." 1765 ::= { mplsTunnelARHopEntry 4 } 1767 mplsTunnelARHopIpv4PrefixLen OBJECT-TYPE 1768 SYNTAX Unsigned32 (0..32) 1769 MAX-ACCESS read-only 1770 STATUS current 1771 DESCRIPTION 1772 "If mplsTunnelARHopAddrType is ipV4(1), then the 1773 prefix length for this hop's IPv4 address is 1774 contained herein. This object is otherwise 1775 insignificant and should contain a value of 0." 1776 ::= { mplsTunnelARHopEntry 5 } 1778 mplsTunnelARHopIpv6Addr OBJECT-TYPE 1779 SYNTAX InetAddressIPv6 1780 MAX-ACCESS read-only 1781 STATUS current 1782 DESCRIPTION 1783 "If the mplsTunnelARHopAddrType is set to ipV6(2), 1784 then this variable contains the IPv6 address of 1785 this hop. This object is otherwise insignificant 1786 and should contain a value of 0." 1787 ::= { mplsTunnelARHopEntry 6 } 1789 mplsTunnelARHopIpv6PrefixLen OBJECT-TYPE 1790 SYNTAX Unsigned32 (0..128) 1791 MAX-ACCESS read-only 1792 STATUS current 1793 DESCRIPTION 1794 "If mplsTunnelARHopAddrType is set to ipV6(2), this 1795 value will contain the prefix length for this 1796 hop's IPv6 address. This object is otherwise 1797 insignificant and should contain a value of 0." 1798 ::= { mplsTunnelARHopEntry 7 } 1800 mplsTunnelARHopAsNumber OBJECT-TYPE 1801 SYNTAX Unsigned32 (0..65535) 1802 MAX-ACCESS read-only 1803 STATUS current 1804 DESCRIPTION 1805 "If mplsTunnelARHopAddrType is set to asNumber(3), 1806 then this value will contain the AS number of this 1807 hop. This object is otherwise insignificant and 1808 should contain a value of 0 to indicate this 1809 fact." 1810 ::= { mplsTunnelARHopEntry 8 } 1812 mplsTunnelARHopType OBJECT-TYPE 1813 SYNTAX INTEGER { 1814 strict(1), 1815 loose(2) 1816 } 1817 MAX-ACCESS read-only 1818 STATUS current 1819 DESCRIPTION 1820 "Denotes whether this is tunnel hop is routed in a 1821 strict or loose fashion." 1822 ::= { mplsTunnelARHopEntry 9 } 1824 -- End of mplsTunnelARHopTable 1826 -- Tunnel Computed Hop table. 1828 mplsTunnelCHopTable OBJECT-TYPE 1829 SYNTAX SEQUENCE OF MplsTunnelCHopEntry 1830 MAX-ACCESS not-accessible 1831 STATUS current 1832 DESCRIPTION 1833 "The mplsTunnelCHopTable is used to indicate the 1834 hops, strict or loose, for an MPLS tunnel defined 1835 in mplsTunnelTable, as computed by a constraint- 1836 based routing protocol, based on the 1837 mplsTunnelHopTable for the outgoing direction of 1838 the tunnel. Each row in this table is indexed by 1839 mplsTunnelCHopListIndex. Each row also has a 1840 secondary index mplsTunnelCHopIndex, corresponding 1841 to the next hop that this row corresponds to. The 1842 first row in the table is the first hop after the 1843 origination point of the tunnel. In case we want 1844 to specify a particular interface on the 1845 originating LSR of an outgoing tunnel by which we 1846 want packets to exit the LSR, we specify this as 1847 the first hop for this tunnel in 1848 mplsTunnelCHopTable. 1850 Please note that since the information necessary 1851 to build entries within this table may not be 1852 supported by some LSRs, implementation of this 1853 table is optional. Furthermore, since the 1854 information in this table is actually provided by 1855 routing protocol after the path has been computed, 1856 the entries in this table are provided only for 1857 observation, and hence, all variables in this 1858 table are accessible exclusively as read-only." 1859 ::= { mplsTeObjects 8 } 1861 mplsTunnelCHopEntry OBJECT-TYPE 1862 SYNTAX MplsTunnelCHopEntry 1863 MAX-ACCESS not-accessible 1864 STATUS current 1865 DESCRIPTION 1866 "An entry in this table represents a tunnel hop. 1867 An entry in this table is created by a constraint- 1868 based routing protocol based on the hops specified 1869 in the corresponding mplsTunnelHopTable." 1870 INDEX { mplsTunnelCHopListIndex, mplsTunnelCHopIndex } 1871 ::= { mplsTunnelCHopTable 1 } 1873 MplsTunnelCHopEntry ::= SEQUENCE { 1874 mplsTunnelCHopListIndex MplsPathIndex, 1875 mplsTunnelCHopIndex MplsPathIndex, 1876 mplsTunnelCHopAddrType INTEGER, 1877 mplsTunnelCHopIpv4Addr InetAddressIPv4, 1878 mplsTunnelCHopIpv4PrefixLen Unsigned32, 1879 mplsTunnelCHopIpv6Addr InetAddressIPv6, 1880 mplsTunnelCHopIpv6PrefixLen Unsigned32, 1881 mplsTunnelCHopAsNumber Unsigned32, 1882 mplsTunnelCHopType INTEGER 1883 } 1885 mplsTunnelCHopListIndex OBJECT-TYPE 1886 SYNTAX MplsPathIndex 1887 MAX-ACCESS not-accessible 1888 STATUS current 1889 DESCRIPTION 1890 "Primary index into this table identifying a 1891 particular computed hop list." 1892 ::= { mplsTunnelCHopEntry 1 } 1894 mplsTunnelCHopIndex OBJECT-TYPE 1895 SYNTAX MplsPathIndex 1896 MAX-ACCESS not-accessible 1897 STATUS current 1898 DESCRIPTION 1899 "Secondary index into this table identifying the 1900 particular hop." 1901 ::= { mplsTunnelCHopEntry 2 } 1903 mplsTunnelCHopAddrType OBJECT-TYPE 1904 SYNTAX INTEGER { 1905 ipV4(1), 1906 ipV6(2), 1907 asNumber(3) 1908 } 1909 MAX-ACCESS read-only 1910 STATUS current 1911 DESCRIPTION 1912 "Denotes the address type of this tunnel hop." 1913 DEFVAL { ipV4 } 1914 ::= { mplsTunnelCHopEntry 3 } 1916 mplsTunnelCHopIpv4Addr OBJECT-TYPE 1917 SYNTAX InetAddressIPv4 1918 MAX-ACCESS read-only 1919 STATUS current 1920 DESCRIPTION 1921 "If mplsTunnelCHopAddrType is set to ipV4(1), then 1922 this value will contain the IPv4 address of this 1923 hop. This object is otherwise insignificant and 1924 should contain a value of 0." 1925 ::= { mplsTunnelCHopEntry 4 } 1927 mplsTunnelCHopIpv4PrefixLen OBJECT-TYPE 1928 SYNTAX Unsigned32 (0..32) 1929 MAX-ACCESS read-only 1930 STATUS current 1931 DESCRIPTION 1932 "If mplsTunnelCHopAddrType is ipV4(1), then the 1933 prefix length for this hop's IPv4 address is 1934 contained herein. This object is otherwise 1935 insignificant and should contain a value of 0." 1936 ::= { mplsTunnelCHopEntry 5 } 1938 mplsTunnelCHopIpv6Addr OBJECT-TYPE 1939 SYNTAX InetAddressIPv6 1940 MAX-ACCESS read-only 1941 STATUS current 1942 DESCRIPTION 1943 "If the mplsTunnelCHopAddrType is set to ipV6(2), 1944 then this variable contains the IPv6 address of 1945 this hop. This object is otherwise insignificant 1946 and should contain a value of 0." 1947 ::= { mplsTunnelCHopEntry 6 } 1949 mplsTunnelCHopIpv6PrefixLen OBJECT-TYPE 1950 SYNTAX Unsigned32 (0..128) 1951 MAX-ACCESS read-only 1952 STATUS current 1953 DESCRIPTION 1954 "If mplsTunnelCHopAddrType is set to ipV6(2), this 1955 value will contain the prefix length for this 1956 hop's IPv6 address. This object is otherwise 1957 insignificant and should contain a value of 0." 1958 ::= { mplsTunnelCHopEntry 7 } 1960 mplsTunnelCHopAsNumber OBJECT-TYPE 1961 SYNTAX Unsigned32 (0..65535) 1962 MAX-ACCESS read-only 1963 STATUS current 1964 DESCRIPTION 1965 "If mplsTunnelCHopAddrType is set to asNumber(3), 1966 then this value will contain the AS number of this 1967 hop. This object is otherwise insignificant and 1968 should contain a value of 0 to indicate this 1969 fact." 1970 ::= { mplsTunnelCHopEntry 8 } 1972 mplsTunnelCHopType OBJECT-TYPE 1973 SYNTAX INTEGER { 1974 strict(1), 1975 loose(2) 1976 } 1977 MAX-ACCESS read-only 1978 STATUS current 1979 DESCRIPTION 1980 "Denotes whether this is tunnel hop is routed in a 1981 strict or loose fashion." 1982 ::= { mplsTunnelCHopEntry 9 } 1984 -- End of mplsTunnelCHopTable 1986 -- MPLS Tunnel Performance Table. 1988 mplsTunnelPerfTable OBJECT-TYPE 1989 SYNTAX SEQUENCE OF MplsTunnelPerfEntry 1990 MAX-ACCESS not-accessible 1991 STATUS current 1992 DESCRIPTION 1993 "This table provides per-tunnel MPLS performance 1994 information." 1995 ::= { mplsTeObjects 9 } 1997 mplsTunnelPerfEntry OBJECT-TYPE 1998 SYNTAX MplsTunnelPerfEntry 1999 MAX-ACCESS not-accessible 2000 STATUS current 2001 DESCRIPTION 2002 "An entry in this table is created by the LSR for 2003 every tunnel. Its is an extension to 2004 mplsTunnelEntry." 2005 AUGMENTS { mplsTunnelEntry } 2006 ::= { mplsTunnelPerfTable 1 } 2008 MplsTunnelPerfEntry ::= SEQUENCE { 2009 mplsTunnelPerfPackets Counter32, 2010 mplsTunnelPerfHCPackets Counter64, 2011 mplsTunnelPerfErrors Counter32, 2012 mplsTunnelPerfBytes Counter32, 2013 mplsTunnelPerfHCBytes Counter64 2014 } 2016 mplsTunnelPerfPackets OBJECT-TYPE 2017 SYNTAX Counter32 2018 MAX-ACCESS read-only 2019 STATUS current 2020 DESCRIPTION 2021 "Number of packets forwarded by the tunnel." 2022 ::= { mplsTunnelPerfEntry 1 } 2024 mplsTunnelPerfHCPackets OBJECT-TYPE 2025 SYNTAX Counter64 2026 MAX-ACCESS read-only 2027 STATUS current 2028 DESCRIPTION 2029 "High capacity counter for number of packets 2030 forwarded by the tunnel." 2031 ::= { mplsTunnelPerfEntry 2 } 2033 mplsTunnelPerfErrors OBJECT-TYPE 2034 SYNTAX Counter32 2035 MAX-ACCESS read-only 2036 STATUS current 2037 DESCRIPTION 2038 "Number of errored packets." 2039 ::= { mplsTunnelPerfEntry 3 } 2041 mplsTunnelPerfBytes OBJECT-TYPE 2042 SYNTAX Counter32 2043 MAX-ACCESS read-only 2044 STATUS current 2045 DESCRIPTION 2046 "Number of bytes forwarded by the tunnel." 2047 ::= { mplsTunnelPerfEntry 4 } 2049 mplsTunnelPerfHCBytes OBJECT-TYPE 2050 SYNTAX Counter64 2051 MAX-ACCESS read-only 2052 STATUS current 2053 DESCRIPTION 2054 "High capacity counter for number of bytes 2055 forwarded by the tunnel." 2056 ::= { mplsTunnelPerfEntry 5 } 2058 -- End of mplsTunnelPerfTable 2060 -- Notifications. 2062 mplsTunnelTrapEnable OBJECT-TYPE 2063 SYNTAX TruthValue 2064 MAX-ACCESS read-write 2065 STATUS current 2066 DESCRIPTION 2067 "If this object is true, then it enables the 2068 generation of mplsTunnelUp and mplsTunnelDown 2069 traps, otherwise these traps are not emitted." 2071 DEFVAL { false } 2072 ::= { mplsTeObjects 10 } 2074 mplsTunnelUp NOTIFICATION-TYPE 2075 OBJECTS { mplsTunnelIndex, 2076 mplsTunnelInstance, 2077 mplsTunnelIngressLSRId, 2078 mplsTunnelEgressLSRId, 2079 mplsTunnelAdminStatus, 2080 mplsTunnelOperStatus 2081 } 2082 STATUS current 2083 DESCRIPTION 2084 "This notification is generated when a 2085 mplsTunnelOperStatus object for one of the 2086 configured tunnels is about to leave the down 2087 state and transition into some other state (but 2088 not into the notPresent state). This other state 2089 is indicated by the included value of 2090 mplsTunnelOperStatus." 2091 ::= { mplsTeNotifyPrefix 1 } 2093 mplsTunnelDown NOTIFICATION-TYPE 2094 OBJECTS { mplsTunnelIndex, 2095 mplsTunnelInstance, 2096 mplsTunnelIngressLSRId, 2097 mplsTunnelEgressLSRId, 2098 mplsTunnelAdminStatus, 2099 mplsTunnelOperStatus 2100 } 2101 STATUS current 2102 DESCRIPTION 2103 "This notification is generated when a 2104 mplsTunnelOperStatus object for one of the 2105 configured tunnels is about to enter the down 2106 state from some other state (but not from the 2107 notPresent state). This other state is indicated 2108 by the included value of mplsTunnelOperStatus." 2109 ::= { mplsTeNotifyPrefix 2 } 2111 mplsTunnelRerouted NOTIFICATION-TYPE 2112 OBJECTS { mplsTunnelIndex, 2113 mplsTunnelInstance, 2114 mplsTunnelIngressLSRId, 2115 mplsTunnelEgressLSRId, 2116 mplsTunnelAdminStatus, 2117 mplsTunnelOperStatus 2118 } 2119 STATUS current 2120 DESCRIPTION 2121 "This notification is generated when a tunnel is 2122 rerouted or re-optimized. If the Actual Path is 2123 used, then this object MAY contain the new path 2124 for this tunnel some time after this trap is 2125 issued by the agent." 2126 ::= { mplsTeNotifyPrefix 3 } 2128 -- End of notifications. 2130 -- Module compliance. 2132 mplsTeGroups 2133 OBJECT IDENTIFIER ::= { mplsTeConformance 1 } 2135 mplsTeCompliances 2136 OBJECT IDENTIFIER ::= { mplsTeConformance 2 } 2138 mplsTeModuleCompliance MODULE-COMPLIANCE 2139 STATUS current 2140 DESCRIPTION 2141 "Compliance statement for agents that support the 2142 MPLS TE MIB." 2143 MODULE -- this module 2145 -- The mandatory group has to be implemented by all 2146 -- LSRs that originate/terminate ESLSPs/tunnels. 2147 -- In addition, depending on the type of tunnels 2148 -- supported, other groups become mandatory as 2149 -- explained below. 2151 MANDATORY-GROUPS { mplsTunnelGroup, 2152 mplsTunnelScalarGroup 2153 } 2155 GROUP mplsTunnelManualGroup 2156 DESCRIPTION 2157 "This group is mandatory for devices which support 2158 manual configuration of tunnels, in addition to 2159 mplsTunnelGroup. The following constraints apply: 2160 mplsTunnelSignallingProto should be at least read- 2161 only with a value of none(1)." 2163 GROUP mplsTunnelSignaledGroup 2164 DESCRIPTION 2165 "This group is mandatory for devices which support 2166 signaled tunnel set up, in addition to 2167 mplsTunnelGroup. The following constraints apply: 2168 mplsTunnelSignallingProto should be at least read- 2169 only returning a value of ldp(2), or rsvp(3)." 2171 GROUP mplsTunnelIsNotIntfcGroup 2172 DESCRIPTION 2173 "This group is mandatory for devices which support 2174 tunnels that are not interfaces, in addition to 2175 mplsTunnelGroup. The following constraints apply: 2176 mplsTunnelIsIf must at least be read-only 2177 returning false(1)." 2179 GROUP mplsTunnelIsIntfcGroup 2180 DESCRIPTION 2181 "This group is mandatory for devices which support 2182 tunnels that are interfaces, in addition to 2183 mplsTunnelGroup. The following constraints apply: 2184 mplsTunnelIsIf must at least be read-only 2185 returning true(2)." 2187 GROUP mplsTunnelOptionalGroup 2188 DESCRIPTION 2189 "Objects in this group are optional." 2191 -- mplsTunnelTable 2193 OBJECT mplsTunnelName 2194 MIN-ACCESS read-only 2195 DESCRIPTION 2196 "Write access is not required." 2198 OBJECT mplsTunnelDescr 2199 MIN-ACCESS read-only 2200 DESCRIPTION 2201 "Write access is not required." 2203 OBJECT mplsTunnelIsIf 2204 MIN-ACCESS read-only 2205 DESCRIPTION 2206 "Write access is not required." 2208 OBJECT mplsTunnelIfIndex 2209 DESCRIPTION 2210 "Write access is not required." 2212 OBJECT mplsTunnelXCPointer 2213 MIN-ACCESS read-only 2214 DESCRIPTION 2215 "Write access is not required." 2217 OBJECT mplsTunnelSignallingProto 2218 MIN-ACCESS read-only 2219 DESCRIPTION 2220 "Write access is not required." 2222 OBJECT mplsTunnelSetupPrio 2223 MIN-ACCESS read-only 2224 DESCRIPTION 2225 "Write access is not required." 2227 OBJECT mplsTunnelHoldingPrio 2228 MIN-ACCESS read-only 2229 DESCRIPTION 2230 "Write access is not required." 2232 OBJECT mplsTunnelSessionAttributes 2233 MIN-ACCESS read-only 2234 DESCRIPTION 2235 "Write access is not required." 2237 OBJECT mplsTunnelOwner 2238 MIN-ACCESS read-only 2239 DESCRIPTION 2240 "Write access is not required." 2242 OBJECT mplsTunnelLocalProtectInUse 2243 MIN-ACCESS read-only 2244 DESCRIPTION 2245 "Write access is not required." 2247 OBJECT mplsTunnelResourcePointer 2248 MIN-ACCESS read-only 2249 DESCRIPTION 2250 "Write access is not required." 2252 OBJECT mplsTunnelInstancePriority 2253 MIN-ACCESS read-only 2254 DESCRIPTION 2255 "Write access is not required." 2257 OBJECT mplsTunnelHopTableIndex 2258 MIN-ACCESS read-only 2259 DESCRIPTION 2260 "Write access is not required." 2262 OBJECT mplsTunnelPrimaryInstance 2263 MIN-ACCESS read-only 2264 DESCRIPTION 2265 "Write access is not required." 2267 OBJECT mplsTunnelPrimaryTimeUp 2268 MIN-ACCESS read-only 2269 DESCRIPTION 2270 "Write access is not required." 2272 OBJECT mplsTunnelPathChanges 2273 MIN-ACCESS read-only 2274 DESCRIPTION 2275 "Write access is not required." 2277 OBJECT mplsTunnelLastPathChange 2278 MIN-ACCESS read-only 2279 DESCRIPTION 2280 "Write access is not required." 2282 OBJECT mplsTunnelCreationTime 2283 MIN-ACCESS read-only 2284 DESCRIPTION 2285 "Write access is not required." 2287 OBJECT mplsTunnelStateTransitions 2288 MIN-ACCESS read-only 2289 DESCRIPTION 2290 "Write access is not required." 2292 OBJECT mplsTunnelARHopTableIndex 2293 DESCRIPTION 2294 "Write access is not required." 2296 OBJECT mplsTunnelCHopTableIndex 2297 DESCRIPTION 2298 "Write access is not required." 2300 OBJECT mplsTunnelAdminStatus 2301 SYNTAX INTEGER { up (1), down (2) } 2302 MIN-ACCESS read-only 2303 DESCRIPTION 2304 "Only up and down states must be supported. Write 2305 access is not required." 2307 OBJECT mplsTunnelOperStatus 2308 SYNTAX INTEGER { up (1), down (2) } 2309 DESCRIPTION 2310 "Only up and down states must be supported. Write 2311 access is not required." 2313 OBJECT mplsTunnelRowStatus 2314 SYNTAX INTEGER { active(1), notInService(2), 2315 createAndGo(4), destroy(6) } 2316 MIN-ACCESS read-only 2317 DESCRIPTION 2318 "The notReady(3) and createAndWait(5) states need 2319 not be supported. Write access is not required." 2321 OBJECT mplsTunnelStorageType 2322 SYNTAX INTEGER { other(1) } 2323 MIN-ACCESS read-only 2324 DESCRIPTION 2325 "Only other (1) needs to be supported." 2327 OBJECT mplsTunnelPathInUse 2328 MIN-ACCESS read-only 2329 DESCRIPTION 2330 "Read-only support is required." 2332 OBJECT mplsTunnelRole 2333 SYNTAX INTEGER { head(1) } 2334 MIN-ACCESS read-only 2335 DESCRIPTION 2336 "Only support for head is required." 2338 OBJECT mplsTunnelTotalUpTime 2339 MIN-ACCESS read-only 2340 DESCRIPTION 2341 "Read-only support is required." 2343 OBJECT mplsTunnelInstanceUpTime 2344 MIN-ACCESS read-only 2345 DESCRIPTION 2346 "Read-only support is required." 2348 -- mplsTunnelHopTable 2350 OBJECT mplsTunnelHopAddrType 2351 MIN-ACCESS read-only 2352 DESCRIPTION 2353 "Write access is not required." 2355 OBJECT mplsTunnelHopIpv4Addr 2356 MIN-ACCESS read-only 2357 DESCRIPTION 2358 "Write access is not required." 2360 OBJECT mplsTunnelHopIpv4PrefixLen 2361 MIN-ACCESS read-only 2362 DESCRIPTION 2363 "Write access is not required." 2365 OBJECT mplsTunnelHopIpv6Addr 2366 MIN-ACCESS read-only 2367 DESCRIPTION 2368 "Write access is not required." 2370 OBJECT mplsTunnelHopIpv6PrefixLen 2371 MIN-ACCESS read-only 2372 DESCRIPTION 2373 "Write access is not required." 2375 OBJECT mplsTunnelHopAsNumber 2376 MIN-ACCESS read-only 2377 DESCRIPTION 2378 "Write access is not required." 2380 OBJECT mplsTunnelHopLspId 2381 MIN-ACCESS read-only 2382 DESCRIPTION 2383 "Write access is not required." 2385 OBJECT mplsTunnelHopType 2386 SYNTAX INTEGER { strict(1) } 2387 MIN-ACCESS read-only 2388 DESCRIPTION 2389 "loose(2) need not be supported. Write access is 2390 not required." 2392 OBJECT mplsTunnelHopRowStatus 2393 SYNTAX INTEGER { active(1), notInService(2), 2394 createAndGo(4), destroy(6) } 2395 MIN-ACCESS read-only 2396 DESCRIPTION 2397 "The notReady(3) and createAndWait(5) states need 2398 not be supported. Write access is not required." 2400 OBJECT mplsTunnelHopStorageType 2401 SYNTAX INTEGER { other(1) } 2402 MIN-ACCESS read-only 2403 DESCRIPTION 2404 "Only other (1) needs to be supported." 2406 -- mplsTunnelResourceTable 2408 OBJECT mplsTunnelResourceMaxRate 2409 MIN-ACCESS read-only 2410 DESCRIPTION 2411 "Write access is not required." 2413 OBJECT mplsTunnelResourceMeanRate 2414 MIN-ACCESS read-only 2415 DESCRIPTION 2416 "Write access is not required." 2418 OBJECT mplsTunnelResourceMaxBurstSize 2419 MIN-ACCESS read-only 2420 DESCRIPTION 2421 "Write access is not required." 2423 OBJECT mplsTunnelResourceRowStatus 2424 SYNTAX INTEGER { active(1), notInService(2), 2425 createAndGo(4), destroy(6) } 2426 MIN-ACCESS read-only 2427 DESCRIPTION 2428 "The notReady(3) and createAndWait(5) states need 2429 not be supported. Write access is not required." 2431 OBJECT mplsTunnelResourceStorageType 2432 SYNTAX INTEGER { other(1) } 2433 MIN-ACCESS read-only 2434 DESCRIPTION 2435 "Only other (1) needs to be supported." 2437 -- mplsTunnelPerfTable 2439 OBJECT mplsTunnelPerfPackets 2440 MIN-ACCESS read-only 2441 DESCRIPTION 2442 "Write access is not required." 2444 OBJECT mplsTunnelPerfHCPackets 2445 MIN-ACCESS read-only 2446 DESCRIPTION 2447 "Write access is not required." 2449 OBJECT mplsTunnelPerfErrors 2450 MIN-ACCESS read-only 2451 DESCRIPTION 2452 "Write access is not required." 2454 OBJECT mplsTunnelPerfBytes 2455 MIN-ACCESS read-only 2456 DESCRIPTION 2457 "Write access is not required." 2459 OBJECT mplsTunnelPerfHCBytes 2460 MIN-ACCESS read-only 2461 DESCRIPTION 2462 "Write access is not required." 2464 ::= { mplsTeCompliances 1 } 2466 -- Units of conformance. 2468 mplsTunnelGroup OBJECT-GROUP 2469 OBJECTS { mplsTunnelIndexNext, 2470 mplsTunnelName, 2471 mplsTunnelDescr, 2472 mplsTunnelOwner, 2473 mplsTunnelXCPointer, 2474 mplsTunnelIfIndex, 2475 mplsTunnelHopTableIndex, 2476 mplsTunnelARHopTableIndex, 2477 mplsTunnelCHopTableIndex, 2478 mplsTunnelAdminStatus, 2479 mplsTunnelOperStatus, 2480 mplsTunnelRowStatus, 2481 mplsTunnelTrapEnable, 2482 mplsTunnelStorageType, 2483 mplsTunnelConfigured, 2484 mplsTunnelActive, 2485 mplsTunnelPrimaryInstance, 2486 mplsTunnelPrimaryTimeUp, 2487 mplsTunnelPathChanges, 2488 mplsTunnelLastPathChange, 2489 mplsTunnelCreationTime, 2490 mplsTunnelStateTransitions, 2491 mplsTunnelEgressLSRId, 2492 mplsTunnelIncludeAnyAffinity, 2493 mplsTunnelIncludeAllAffinity, 2494 mplsTunnelExcludeAllAffinity, 2495 mplsTunnelPerfPackets, 2496 mplsTunnelPerfHCPackets, 2497 mplsTunnelPerfErrors, 2498 mplsTunnelPerfBytes, 2499 mplsTunnelPerfHCBytes, 2500 mplsTunnelResourcePointer, 2501 mplsTunnelInstancePriority, 2502 mplsTunnelPathInUse, 2503 mplsTunnelRole, 2504 mplsTunnelTotalUpTime, 2505 mplsTunnelInstanceUpTime 2506 } 2507 STATUS current 2508 DESCRIPTION 2509 "Necessary, but not sufficient, set of objects to 2510 implement tunnels. In addition, depending on the 2511 type of the tunnels supported (for example, 2512 manually configured or signaled, persistent or non- 2513 persistent, etc.), the following other groups 2514 defined below are mandatory: mplsTunnelManualGroup 2515 and/or mplsTunnelSignaledGroup, 2516 mplsTunnelIsNotIntfcGroup and/or 2517 mplsTunnelIsIntfcGroup." 2518 ::= { mplsTeGroups 1 } 2520 mplsTunnelManualGroup OBJECT-GROUP 2521 OBJECTS { mplsTunnelSignallingProto } 2522 STATUS current 2523 DESCRIPTION 2524 "Object(s) needed to implement manually configured 2525 tunnels." 2526 ::= { mplsTeGroups 2 } 2528 mplsTunnelSignaledGroup OBJECT-GROUP 2529 OBJECTS { mplsTunnelSetupPrio, 2530 mplsTunnelHoldingPrio, 2531 mplsTunnelSignallingProto, 2532 mplsTunnelLocalProtectInUse, 2533 mplsTunnelSessionAttributes, 2534 mplsTunnelHopListIndexNext, 2535 mplsTunnelHopAddrType, 2536 mplsTunnelHopIpv4Addr, 2537 mplsTunnelHopIpv4PrefixLen, 2538 mplsTunnelHopIpv6Addr, 2539 mplsTunnelHopIpv6PrefixLen, 2540 mplsTunnelHopAsNumber, 2541 mplsTunnelHopLspId, 2542 mplsTunnelHopType, 2543 mplsTunnelHopRowStatus, 2544 mplsTunnelHopStorageType 2545 } 2546 STATUS current 2547 DESCRIPTION 2548 "Object needed to implement signaled tunnels." 2549 ::= { mplsTeGroups 3 } 2551 mplsTunnelScalarGroup OBJECT-GROUP 2552 OBJECTS { mplsTunnelConfigured, 2553 mplsTunnelActive, 2554 mplsTunnelTEDistProto, 2555 mplsTunnelMaxHops 2556 } 2557 STATUS current 2558 DESCRIPTION 2559 "Scalar object needed to implement MPLS tunnels." 2560 ::= { mplsTeGroups 4 } 2562 mplsTunnelIsIntfcGroup OBJECT-GROUP 2563 OBJECTS { mplsTunnelIsIf } 2564 STATUS current 2565 DESCRIPTION 2566 "Objects needed to implement tunnels that are 2567 interfaces." 2568 ::= { mplsTeGroups 5 } 2570 mplsTunnelIsNotIntfcGroup OBJECT-GROUP 2571 OBJECTS { mplsTunnelIsIf } 2572 STATUS current 2573 DESCRIPTION 2574 "Objects needed to implement tunnels that are not 2575 interfaces." 2576 ::= { mplsTeGroups 6 } 2578 mplsTunnelOptionalGroup OBJECT-GROUP 2579 OBJECTS { mplsTunnelResourceIndexNext, 2580 mplsTunnelResourceMaxRate, 2581 mplsTunnelResourceMeanRate, 2582 mplsTunnelResourceMaxBurstSize, 2583 mplsTunnelResourceRowStatus, 2584 mplsTunnelResourceStorageType, 2585 mplsTunnelARHopAddrType, 2586 mplsTunnelARHopIpv4Addr, 2587 mplsTunnelARHopIpv4PrefixLen, 2588 mplsTunnelARHopIpv6Addr, 2589 mplsTunnelARHopIpv6PrefixLen, 2590 mplsTunnelARHopAsNumber, 2591 mplsTunnelARHopType, 2592 mplsTunnelCHopAddrType, 2593 mplsTunnelCHopIpv4Addr, 2594 mplsTunnelCHopIpv4PrefixLen, 2595 mplsTunnelCHopIpv6Addr, 2596 mplsTunnelCHopIpv6PrefixLen, 2597 mplsTunnelCHopAsNumber, 2598 mplsTunnelCHopType 2599 } 2600 STATUS current 2601 DESCRIPTION 2602 "The objects in this group are optional." 2603 ::= { mplsTeGroups 7 } 2605 mplsTeNotificationGroup NOTIFICATION-GROUP 2606 NOTIFICATIONS { mplsTunnelUp, 2607 mplsTunnelDown, 2608 mplsTunnelRerouted 2609 } 2610 STATUS current 2611 DESCRIPTION 2612 "Set of notifications implemented in this module. 2613 None is mandatory." 2614 ::= { mplsTeGroups 8 } 2616 -- End of MPLS-TE-MIB 2617 END 2618 11. Security Considerations 2620 There are a number of management objects defined in this 2621 MIB that have a MAX-ACCESS clause of read-write and/or 2622 read-create. Such objects may be considered sensitive or 2623 vulnerable in some network environments. The support for 2624 SET operations in a non-secure environment without proper 2625 protection can have a negative effect on network 2626 operations. 2628 It is thus important to control even GET access to these 2629 objects and possibly to even encrypt the values of these 2630 object when sending them over the network via SNMP. Not 2631 all versions of SNMP provide features for such a secure 2632 environment. 2634 SNMPv1 by itself is not a secure environment. Even if the 2635 network itself is secure (for example by using IPSec 2636 [IPSEC]), there is no control as to who on the secure 2637 network is allowed to access and GET/SET 2638 (read/change/create/delete) the objects in this MIB. It is 2639 recommended that the implementers consider the security 2640 features as provided by the SNMPv3 framework. 2641 Specifically, the use of the User-based Security Model 2642 [SNMPv3USM] and the View- based Access Control 2643 [SNMPv3VACM] is recommended. It is then a customer/user 2644 responsibility to ensure that the SNMP entity giving 2645 access to an instance of this MIB, is properly configured 2646 to give access to the objects only to those principals 2647 (users) that have legitimate rights to indeed GET or SET 2648 (change/create/delete) them. 2650 12. Acknowledgments 2652 We wish to thank Adrian Farrel, Eric Gray, Patrick 2653 Kerharo, Pramod Koppol, Paul Langille and Mike Piecuch for 2654 their comments on this draft. 2656 13. References 2658 [MPLSArch] Rosen, E., Viswanathan, A., and R. Callon, 2659 "Multiprotocol Label Switching 2660 Architecture", Internet Draft , July 2000. 2663 [LSRMIB] Srinivasan, C., Viswanathan, A. and T. 2664 Nadeau, "MPLS Label Switch Router Management 2665 Information Base Using SMIv2", Internet 2666 Draft , July 2667 2000. 2669 [LblStk] Rosen, E., Rekhter, Y., Tappan, D., 2670 Farinacci, D., Federokow, G., Li, T., and A. 2671 Conta, "MPLS Label Stack Encoding", Internet 2672 Draft , 2673 July 2000. 2675 [RSVPTun] Awaduche, D., Berger, L., Der-Haw, G., Li, 2676 T., Swallow, G., and V. Srinivasan, 2677 "Extensions to RSVP for LSP Tunnels", 2678 Internet Draft , August 2000. 2681 [CR-LDP] B. Jamoussi (Editor), "Constraint-Based LSP 2682 Setup using LDP", Internet Draft , July 2000. 2685 [Assigned] Reynolds, J., and J. Postel, "Assigned 2686 Numbers", RFC 1700, October 1994. See also: 2687 http://www.isi.edu/in- 2688 notes/iana/assignments/smi-numbers 2690 [SNMPArch] Harrington, D., Presuhn, R., and B. Wijnen, 2691 "An Architecture for Describing SNMP 2692 Management Frameworks", RFC 2271, January 2693 1998. 2695 [SMIv1] Rose, M., and K. McCloghrie, "Structure and 2696 Identification of Management Information for 2697 TCP/IP-based Internets", RFC 1155, May 1990. 2699 [SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB 2700 Definitions", RFC 1212, March 1991. 2702 [SNMPv1Traps] M. Rose, "A Convention for Defining Traps 2703 for use with the SNMP", RFC 1215, March 2704 1991. 2706 [SMIv2] Case, J., McCloghrie, K., Rose, M., and S. 2707 Waldbusser, "Structure of Management 2708 Information for Version 2 of the Simple 2709 Network Management Protocol (SNMPv2)", RFC 2710 1902, January 1996. 2712 [SNMPv2TC] Case, J., McCloghrie, K., Rose, M., and S. 2713 Waldbusser, "Textual Conventions for Version 2714 2 of the Simple Network Management Protocol 2715 (SNMPv2)", RFC 1903, SNMP Research, Inc., 2716 Cisco Systems, Inc., January 1996. 2718 [SNMPv2Conf] Case, J., McCloghrie, K., Rose, M., and S. 2719 Waldbusser, "Conformance Statements for 2720 Version 2 of the Simple Network Management 2721 Protocol (SNMPv2)", RFC 1904, January 1996. 2723 [SNMPv1] Case, J., Fedor, M., Schoffstall, M., and J. 2724 Davin, "Simple Network Management Protocol", 2725 RFC 1157, May 1990. 2727 [SNMPv2c] Case, J., McCloghrie, K., Rose, M., and S. 2728 Waldbusser, "Introduction to Community-based 2729 SNMPv2", RFC 1901, January 1996. 2731 [SNMPv2TM] Case, J., McCloghrie, K., Rose, M., and S. 2732 Waldbusser, "Transport Mappings for Version 2733 2 of the Simple Network Management Protocol 2734 (SNMPv2)", RFC 1906, January 1996. 2736 [SNMPv3MP] Case, J., Harrington D., Presuhn R., and B. 2737 Wijnen, "Message Processing and Dispatching 2738 for the Simple Network Management Protocol 2739 (SNMP)", RFC 2272, January 1998. 2741 [SNMPv3USM] Blumenthal, U., and B. Wijnen, "User-based 2742 Security Model (USM) for version 3 of the 2743 Simple Network Management Protocol 2744 (SNMPv3)", RFC 2574, April 1999. 2746 [SNMPv2PO] Case, J., McCloghrie, K., Rose, M., and S. 2747 Waldbusser, "Protocol Operations for Version 2748 2 of the Simple Network Management Protocol 2749 (SNMPv2)", RFC 1905, January 1996. 2751 [SNMPv3App] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2752 Applications", RFC 2273, January 1998. 2754 [SNMPv3VACM] Wijnen, B., Presuhn, R., and K. McCloghrie, 2755 "View-based Access Control Model (VACM) for 2756 the Simple Network Management Protocol 2757 (SNMP)", RFC 2575, April 1999. 2759 [IPSEC] Kent, S., and Atkinson, R., "Security 2760 Architecture for the Internet Protocol", RFC 2761 2401, November 1998. 2763 [IFMIB] McCloghrie, K., and F. Kastenholtz, "The 2764 Interfaces Group MIB using SMIv2", RFC 2233, 2765 Nov. 1997. 2767 14. Authors' Addresses 2769 Cheenu Srinivasan 2770 Tachion Networks, Inc. 2771 Monmouth Park Corporate Center I 2772 Building C, 185 Monmouth Park Highway 2773 West Long Branch, NJ 07764 2774 Phone: +1-732-542-7750 x1234 2775 Email: cheenu@tachion.com 2777 Arun Viswanathan 2778 Force10 Networks, Inc. 2779 1440 McCarthy Blvd 2780 Milpitas, CA 95035 2781 Phone: +1-408-571-3516 2782 Email: arun@force10networks.com 2784 Thomas D. Nadeau 2785 Cisco Systems, Inc. 2786 300 Apollo Drive 2787 Chelmsford, MA 01824 2788 Phone: +1-978-244-3051 2789 Email: tnadeau@cisco.com 2791 15. Full Copyright Statement 2793 Copyright (C) The Internet Society (2000). All Rights 2794 Reserved. 2796 This document and translations of it may be copied and 2797 furnished to others, and derivative works that comment on 2798 or otherwise explain it or assist in its implementation may 2799 be prepared, copied, published and distributed, in whole or 2800 in part, without restriction of any kind, provided that the 2801 above copyright notice and this paragraph are included on 2802 all such copies and derivative works. However, this 2803 document itself may not be modified in any way, such as by 2804 removing the copyright notice or references to the Internet 2805 Society or other Internet organizations, except as needed 2806 for the purpose of developing Internet standards in which 2807 case the procedures for copyrights defined in the Internet 2808 Standards process must be followed, or as required to 2809 translate it into languages other than English. 2811 The limited permissions granted above are perpetual and 2812 will not be revoked by the Internet Society or its 2813 successors or assigns. This document and the information 2814 contained herein is provided on an "AS IS" basis and THE 2815 INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE 2816 DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 2817 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2818 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2819 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 2820 PURPOSE.