idnits 2.17.1 draft-ietf-mpls-te-mib-01.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: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document is more than 15 pages and seems to lack a Table of Contents. == 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 an Authors' Addresses Section. ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 248 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? ** The abstract seems to contain references ([LSRMIB], [MPLSArch,MPLSFW]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 17 has weird spacing: '.... Note that...' == Line 18 has weird spacing: '... other group...' == Line 22 has weird spacing: '... months and ...' == Line 23 has weird spacing: '...cuments at a...' == Line 24 has weird spacing: '... Drafts as re...' == (243 more instances...) -- 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.) -- Couldn't find a document date in the document -- date freshness check skipped. 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 106, but not defined == Unused Reference: 'LDPMIB' is defined on line 1296, but no explicit reference was found in the text == Unused Reference: 'LblStk' is defined on line 1302, but no explicit reference was found in the text == Unused Reference: 'Assigned' is defined on line 1316, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'MPLSArch' -- Possible downref: Non-RFC (?) normative reference: ref. 'MPLSFW' -- Possible downref: Non-RFC (?) normative reference: ref. 'LSRMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'LDPMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'LblStk' -- Possible downref: Non-RFC (?) normative reference: ref. 'RSVPTun' -- Possible downref: Non-RFC (?) normative reference: ref. 'CRLDP' ** 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 2274 (ref. 'SNMPv3USM') (Obsoleted by RFC 2574) ** 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 2275 (ref. 'SNMPv3VACM') (Obsoleted by RFC 2575) Summary: 22 errors (**), 0 flaws (~~), 11 warnings (==), 9 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 Network Technologies 3 Expires: December 1999 4 Arun Viswanathan 5 Lucent Technologies 7 MPLS Traffic Engineering Management Information Base Using SMIv2 9 draft-ietf-mpls-te-mib-01.txt 11 Status of this Memo 13 This document is an Internet-Draft and is in full conformance with 14 all provisions of Section 10 of RFC2026. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six 22 months and may be updated, replaced, or obsoleted by other 23 documents at any time. It is inappropriate to use Internet- 24 Drafts as reference material or to cite them other than as "work 25 in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 Abstract 35 This memo defines an experimental portion of the Management 36 Information Base (MIB) for use with network management protocols 37 in the Internet community. In particular, it describes managed 38 objects for Multi-Protocol Label Switching (MPLS) [MPLSArch, 39 MPLSFW] based traffic engineering. 41 Open Issues 43 - Do we need to introduce a separate table of tunnel performance 44 objects or is the current method of using the objects in 45 mplsInSegmentTable and mplsOutSegmentTable [LSRMIB] to 46 determine tunnel performance adequate? We think the latter 47 since we need to be able to measure the individual performance 48 of each tunnel segment anyway which will imply replicating all 49 the segment related objects in this MIB; but this needs some 50 more thought. 52 - Support for "make-before-break" tunnel re-routing using shared- 53 explicit RSVP filters. 55 - Support for signalled COS value. 57 - Do we need objects to keep track of ownership of entries in 58 various tables? 60 - More descriptive text and detailed example. 62 - Session attribute flag for fast-reroute. 64 1. Introduction 66 This memo defines an experimental portion of the Management 67 Information Base (MIB) for use with network management protocols 68 in the Internet community. In particular, it describes managed 69 objects for modeling an Multi-Protocol Label Switching (MPLS) 70 [MPLSArch, MPLSFW] based traffic engineering. This MIB should be 71 used in conjunction with the companion document [LSRMIB] for MPLS 72 based traffic engineering configuration and management. 74 Comments should be made directly to the MPLS mailing list at 75 mpls@uu.net. 77 This memo does not, in its draft form, specify a standard for the 78 Internet community. 80 2. Terminology 82 This document uses terminology from the MPLS architecture document 83 [MPLSArch] and MPLS Label Switch Router MIB [LSRMIB]. Some 84 frequently used terms are described next. 86 An explicitly routed LSP (ERLSP) is referred to as an MPLS tunnel. 87 It consists of one in-segment and/or one out-segment at the 88 ingress/egress LSRs. These are also referred to as tunnel 89 segments. Additionally, at an intermediate LSR, we model a 90 connection as consisting of one or more in-segments and/or one or 91 more out-segments. The binding or interconnection between in- 92 segments and out-segments in performed using a cross-connect. 93 These objects are defined in the MPLS Label Switch Router MIB 94 [LSRMIB]. 96 3. The SNMP Management Framework 98 The SNMP Management Framework presently consists of five major 99 components: 101 - An overall architecture, described in RFC 2271 [SNMPArch]. 103 - Mechanisms for describing and naming objects and events for the 104 purpose of management. The first version of this Structure of 105 Management Information (SMI) is called SMIv1 and described in 106 RFC 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215 107 [SNMPv1Traps]. The second version, called SMIv2, is described 108 in RFC 1902 [SMIv2], RFC 1903 [SNMPv2TC] and RFC 1904 109 [SNMPv2Conf]. 111 - Message protocols for transferring management information. The 112 first version of the SNMP message protocol is called SNMPv1 113 and described in RFC 1157 [SNMPv1]. A second version of the 114 SNMP message protocol, which is not an Internet standards 115 track protocol, is called SNMPv2c and described in RFC 1901 116 [SNMPv2c] and RFC 1906 [SNMPv2TM]. The third version of the 117 message protocol is called SNMPv3 and described in RFC 1906 118 [SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC 2274 [SNMPv3USM]. 120 - Protocol operations for accessing management information. The 121 first set of protocol operations and associated PDU formats is 122 described in RFC 1157 [SNMPv1]. A second set of protocol 123 operations and associated PDU formats is described in RFC 1905 124 [SNMPv2PO]. 126 - A set of fundamental applications described in RFC 2273 127 [SNMPv3App] and the view-based access control mechanism 128 described in RFC 2275 [SNMPv3VACM]. Managed objects are 129 accessed via a virtual information store, termed the 130 Management Information Base or MIB. Objects in the MIB are 131 defined using the mechanisms defined in the SMI. This memo 132 specifies a MIB module that is compliant to the SMIv2. A MIB 133 conforming to the SMIv1 can be produced through the 134 appropriate translations. The resulting translated MIB must 135 be semantically equivalent, except where objects or events are 136 omitted because no translation is possible (use of Counter64). 137 Some machine readable information in SMIv2 will be converted 138 into textual descriptions in SMIv1 during the translation 139 process. However, this loss of machine readable information 140 is not considered to change the semantics of the MIB. 142 3.1. Object Definitions 144 Managed objects are accessed via a virtual information store, 145 termed the Management Information Base or MIB. Objects in the MIB 146 are defined using the subset of Abstract Syntax Notation One 147 (ASN.1) defined in the SMI. In particular, each object type is 148 named by an OBJECT IDENTIFIER, an administratively assigned name. 149 The object type together with an object instance serves to 150 uniquely identify a specific instantiation of the object. For 151 human convenience, we often use a textual string, termed the 152 descriptor, to also refer to the object type. 154 4. Feature Checklist 156 The MPLS traffic engineering MIB is designed to satisfy the 157 following requirements and constraints. 159 - The MIB must support the configuration of point-to-point uni- 160 directional tunnels. 162 - The MIB should be able to support the configuration of point-to- 163 point bi-directional tunnels. 165 - The MIB should be able to support the configuration of 166 multipoint-to-point unidirectional tunnels. 168 - MPLS tunnels need not be interfaces, but it should be possible 169 to configure a tunnel as an interface. 171 - The MIB should be able to support both manually configured MPLS 172 tunnels as well as via LDP and/or RSVP signaling. 174 - It should be possible to support persistent as well as non- 175 persistent tunnels. 177 5. Outline 179 Traffic engineering support for MPLS tunnels requires the 180 following configuration. 182 - Setting up MPLS tunnels along with appropriate configuration 183 parameters. 185 - Configuring tunnel loose and strict source routed hops. 187 These actions may need to be accompanied with corresponding 188 actions using [LSRMIB] to establish and configure tunnel segments, 189 if this is done manually. Also, the in-segment and out-segment 190 performance tables, mplsInSegmentPerfTable and 191 mplsOutSegmentPerfTable [LSRMIB], should be used to determine 192 performance of the tunnels and tunnel segments. 194 5.1. Summary of Trafic Engineering MIB 196 The MIB objects for performing these actions consist of the 197 following tables. 199 - Tunnel table (mplsTunnelTable) for setting up MPLS tunnels. 201 - Tunnel hop table (mplsTunnelHopTable) for configuring strict 202 and loose source routed MPLS tunnels hops. 204 These tables are described in the subsequent sections. 206 6. Brief Description of MIB Objects 208 The objects described in this section support the functionality 209 described in documents [RSVPTun, CRLDP]. The tables support both 210 manually configured and signalled tunnels. Moreover, they provide 211 the capability to associate two uni-directional tunnels to form a 212 single bi-directional tunnel. 214 6.1. mplsTunnelTable 216 The mplsTunnelTable allows new MPLS tunnels to be created between 217 an MPLS LSR and a remote endpoint, and existing tunnels to be 218 reconfigured or removed. Note that we only support point-to-point 219 tunnel segments, although multipoint-to-point and point-to- 220 multipoint connections are supported by an LSR acting as a cross- 221 connect. Each MPLS tunnel can thus have one out-segment 222 originating at an LSR and/or one in-segment terminating at that 223 LSR. 225 mplsTunnelTable does not define the in and out segments forming 226 the tunnel. Instead, these are defined by creating rows in the in- 227 segment and out-segment tables, defining relationships in the 228 cross-connect table and referring to these rows in the 229 mplsTunnelTable using a cross-connect index, mplsTunnelXCID. These 230 segment and cross-connect related objects are defined in [LSRMIB]. 232 6.2. mplsTunnelHopTable 233 mplsTunnelHopTable is used to indicate the hops, strict or loose, 234 for an MPLS tunnel defined in mplsTunnelTable, when it is 235 established via signaling. Each row in this table is indexed 236 primarily by the same index mplsTunnelIndex as the row of the 237 corresponding tunnel in mplsTunnelTable. Each row also has a 238 secondary index, mplsTunnelHopIndex, corresponding to the next hop 239 of this tunnel. The scalar mplsTunnelMaxHops, indicates the 240 maximum number of hops that can be specified per tunnel on this 241 LSR. 243 7. MPLS Traffic Engineering MIB Definitions 245 MPLS-TE-MIB DEFINITIONS ::= BEGIN 247 IMPORTS 248 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 249 experimental, Integer32, Counter32, Counter64, Gauge32, IpAddress 250 FROM SNMPv2-SMI 251 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 252 FROM SNMPv2-CONF 253 TEXTUAL-CONVENTION, TruthValue, RowStatus 254 FROM SNMPv2-TC 255 ifIndex, InterfaceIndex, InterfaceIndexOrZero 256 FROM IF-MIB 257 BitRate, BurstSize 258 FROM INTEGRATED-SERVICES-MIB; 260 mplsTeMIB MODULE-IDENTITY 261 LAST-UPDATED "9906161200Z" -- 16 June 1999 12:00:00 EST 262 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 263 CONTACT-INFO 264 " Cheenu Srinivasan 265 Postal: Tachion Network Technologies 266 2 Meridian Road 267 Eatontown, NJ 07724 268 Tel: +1 732 542 7750 x234 269 Email: cheenu@tachion.com 271 Arun Viswanathan 272 Postal: Lucent Technologies 273 4D537, 101 Crawfords Corner Road 274 Holmdel, NJ 07733 275 Tel: +1 732 332 5163 276 Email: arunv@lucent.com" 277 DESCRIPTION 278 "Proposed MIB module for MPLS Traffic Engineering 279 (TE) as defined in: Extensions to RSVP for LSP 280 Tunnels, Awduche et al, Internet Draft , March 1999; Constraint- 282 Based LSP Setup using LDP, Jamoussi, Internet Draft 283 < draft-ietf-mpls-cr-ldp-01.txt>, Feb. 1999." 284 ::= { experimental 95 } 286 -- Textual Conventions. 288 -- An MPLS label. 289 MplsLabel ::= TEXTUAL-CONVENTION 290 STATUS current 291 DESCRIPTION 292 "Represents an MPLS label. Note that the contents of 293 a label field are interpreted in an interface-type 294 specific fashion. For example, the label carried in 295 the MPLS shim header is 20 bits wide and the top 12 296 bits must be zero. The frame relay label can be 297 either 10, 17 or 23 bits wide depending on the size 298 of the DLCI field size and the top 22, 15, or 9 bits 299 must be zero, respectively. For an ATM interface, 300 the lowermost 16 bits are interpreted as the VCI, 301 the next 8 bits as the VPI and the remaining bits 302 must be zero. Also note the permissible label 303 values are also a function of the interface type. 304 For example, the value 3 has special semantics in 305 the control plane for an MPLS shim header label and 306 is not a valid label value in the datapath." 307 REFERENCE 308 "1. MPLS Label Stack Encoding, Rosen et al, draft- 309 ietf-mpls-label-encaps-04.txt, April 1999. 310 2. Use of Label Switching on Frame Relay Networks, 311 Conta et al, draft-ietf-mpls-fr-03.txt, Nov. 1998." 312 SYNTAX Integer32 314 MplsTunnelIndex ::= TEXTUAL-CONVENTION 315 STATUS current 316 DESCRIPTION 317 "Index into mplsTunnelTable." 318 SYNTAX INTEGER (0..65535) 320 MplsTunnelCookie ::= TEXTUAL-CONVENTION 321 STATUS current 322 DESCRIPTION 323 "A globally unique identifier that is assigned to 324 each ERLSP. This is assigned at the head end of the 325 ERLSP and can be used by all LSRs to identify this 326 ERLSP. At the head end this cookie is maintained in 327 the tunnel table as mplsTunnelLocalCookie. For 328 signalled tunnels this cookie is piggybacked by the 329 signaling protocol to the remote end where the 330 cookie is stored in the remote LSR's tunnel table as 331 mplsTunnelRemoteCookie for the tunnel. For creating 332 bi-directional tunnels the cookie is used to 333 associate the two uni-directional ERLSPs as 334 belonging to the same tunnel. 336 It is recommended that the cookie value be assigned 337 by concatenating the head-end LSR's IP address with 338 the tunnel index. For IPv4 addresses this results 339 in a 6-octet long cookie." 340 SYNTAX OCTET STRING (SIZE(6)) 342 Ipv6Address ::= TEXTUAL-CONVENTION 343 STATUS current 344 DESCRIPTION 345 "IPv6 address." 346 SYNTAX OCTET STRING (SIZE(16)) 348 -- Top level components of this MIB. 350 -- tables, scalars 351 mplsTeObjects OBJECT IDENTIFIER ::= { mplsTeMIB 1 } 352 -- traps 353 mplsTeNotifications OBJECT IDENTIFIER ::= { mplsTeMIB 2 } 354 -- conformance 355 mplsTeConformance OBJECT IDENTIFIER ::= { mplsTeMIB 3 } 357 -- MPLS tunnel table. 359 mplsTunnelTable OBJECT-TYPE 360 SYNTAX SEQUENCE OF MplsTunnelEntry 361 MAX-ACCESS not-accessible 362 STATUS current 363 DESCRIPTION 364 "The mplsTunnelTable allows new MPLS tunnels to be 365 created between an LSR and a remote endpoint, and 366 existing tunnels to be reconfigured or removed. 367 Note that only point-to-point tunnel segments are 368 supported, although multipoint-to-point and point-to- 369 multipoint connections are supported by an LSR 370 acting as a cross-connect. Each MPLS tunnel can 371 thus have one out-segment originating at this LSR 372 and/or one in-segment terminating at this LSR." 373 ::= { mplsTeObjects 1 } 375 mplsTunnelEntry OBJECT-TYPE 376 SYNTAX MplsTunnelEntry 377 MAX-ACCESS not-accessible 378 STATUS current 379 DESCRIPTION 380 "An entry in this table represents an MPLS tunnel. 381 An entry can be created by a network administrator 382 or by an SNMP agent as instructed by LDP or RSVP. 383 Whenever an new entry is created with mplsTunnelIsIf 384 set to true(1), then a corresponding entry is 385 created in ifTable as well (see RFC 2233). The 386 ifType of this entry is mplsTunnel(150) (see 387 http://www.isi.edu/in-notes/iana/assignments/smi- 388 numbers)." 389 INDEX { mplsTunnelIndex } 390 ::= { mplsTunnelTable 1 } 392 MplsTunnelEntry ::= SEQUENCE { 393 mplsTunnelIndex MplsTunnelIndex, 394 mplsTunnelName DisplayString, 395 mplsTunnelDescr DisplayString, 396 mplsTunnelIsIf TruthValue, 397 mplsTunnelIfIndex InterfaceIndexOrZero, 398 mplsTunnelDirection INTEGER, 399 mplsTunnelXCIndex Integer32, 400 mplsTunnelSignallingProto INTEGER, 401 mplsTunnelLocalCookie MplsTunnelCookie, 402 mplsTunnelRemoteCookie MplsTunnelCookie, 403 mplsTunnelIsMergeable TruthValue, 404 mplsTunnelSetupPrio INTEGER, 405 mplsTunnelHoldingPrio INTEGER, 406 mplsTunnelInMaxRate BitRate, 407 mplsTunnelInMeanRate BitRate, 408 mplsTunnelInMaxBurstSize BurstSize, 409 mplsTunnelOutMaxRate BitRate, 410 mplsTunnelOutMeanRate BitRate, 411 mplsTunnelOutMaxBurstSize BurstSize, 412 mplsTunnelIsPinned TruthValue, 413 mplsTunnelIsPersistent TruthValue, 414 mplsTunnelAdminStatus INTEGER, 415 mplsTunnelOperStatus INTEGER, 416 mplsTunnelRowStatus RowStatus 417 } 419 mplsTunnelIndex OBJECT-TYPE 420 SYNTAX Integer32 421 MAX-ACCESS read-create 422 STATUS current 423 DESCRIPTION 424 "Uniquely identifies this row." 425 ::= { mplsTunnelEntry 1 } 427 mplsTunnelName OBJECT-TYPE 428 SYNTAX DisplayString 429 MAX-ACCESS read-create 430 STATUS current 431 DESCRIPTION 432 "The 'canonical' name assigned to the tunnel that can 433 be used to refer to it on the 'console' port. If 434 mplsTunnelIsIf is set to true ifName of the 435 interface corresponding to this tunnel should have a 436 value equal to mplsTunnelName. Also see the 437 description of ifName in RFC 2233." 438 REFERENCE 439 "RFC 2233 - The Interfaces Group MIB using SMIv2, 440 McCloghrie and Kastenholtz, Nov. 1997" 441 ::= { mplsTunnelEntry 2 } 443 mplsTunnelDescr OBJECT-TYPE 444 SYNTAX DisplayString 445 MAX-ACCESS read-create 446 STATUS current 447 DESCRIPTION 448 "A textual string containing information about the 449 tunnel. If there is no description this object 450 contains a zero length string." 451 ::= { mplsTunnelEntry 3 } 453 mplsTunnelIsIf OBJECT-TYPE 454 SYNTAX TruthValue 455 MAX-ACCESS read-create 456 STATUS current 457 DESCRIPTION 458 "Is this tunnel also an interface?" 459 DEFVAL { false } 460 ::= { mplsTunnelEntry 4 } 462 mplsTunnelIfIndex OBJECT-TYPE 463 SYNTAX InterfaceIndexOrZero 464 MAX-ACCESS read-only 465 STATUS current 466 DESCRIPTION 467 "If this tunnel is an interface then the LSR assigned 468 ifIndex. Otherwise this is set to zero." 469 DEFVAL { 0 } 470 ::= { mplsTunnelEntry 5 } 472 mplsTunnelDirection OBJECT-TYPE 473 SYNTAX INTEGER { in(1), out(2), in-out(3) } 474 MAX-ACCESS read-create 475 STATUS current 476 DESCRIPTION 477 "Whether this tunnel is unidirectional-incoming, 478 unidirectional-outgoing, or bidirectional." 479 ::= { mplsTunnelEntry 6 } 481 mplsTunnelXCIndex OBJECT-TYPE 482 SYNTAX Integer32 483 MAX-ACCESS read-create 484 STATUS current 485 DESCRIPTION 486 "Index into mplsXCTable identifying the segments that 487 compose this tunnel, their characteristics, 488 relationship etc." 489 REFERENCE 490 " Srinivasan, C., and A. Viswanathan, MPLS Label 491 Switch Router Management Information Base Using 492 SMIv2, Internet Draft , June 1999." 494 DEFVAL { 0 } 495 ::= { mplsTunnelEntry 7 } 497 mplsTunnelSignallingProto OBJECT-TYPE 498 SYNTAX INTEGER { none(1), ldp(2), rsvp(3) } 499 MAX-ACCESS read-create 500 STATUS current 501 DESCRIPTION 502 "The signaling protocol, if any, that set up this 503 tunnel." 504 DEFVAL { none } 505 ::= { mplsTunnelEntry 8 } 507 mplsTunnelLocalCookie OBJECT-TYPE 508 SYNTAX MplsTunnelCookie 509 MAX-ACCESS read-only 510 STATUS current 511 DESCRIPTION 512 "The local cookie assigned to the outgoing direction 513 of this tunnel at this LSR." 514 ::= { mplsTunnelEntry 9 } 516 mplsTunnelRemoteCookie OBJECT-TYPE 517 SYNTAX MplsTunnelCookie 518 MAX-ACCESS read-only 519 STATUS current 520 DESCRIPTION 521 "The remote cookie assigned to the incoming direction 522 of tunnel by the remote (head-end) LSR." 523 ::= { mplsTunnelEntry 10 } 525 mplsTunnelIsMergeable OBJECT-TYPE 526 SYNTAX TruthValue 527 MAX-ACCESS read-create 528 STATUS current 529 DESCRIPTION 530 "Whether this tunnel can be merged at an LSR 531 downstream with another tunnel." 532 DEFVAL { true } 533 ::= { mplsTunnelEntry 11 } 535 mplsTunnelSetupPrio OBJECT-TYPE 536 SYNTAX INTEGER (0..7) 537 MAX-ACCESS read-create 538 STATUS current 539 DESCRIPTION 540 "The setup priority of this tunnel." 541 REFERENCE 542 "Extensions to RSVP for LSP Tunnels, Awduche et al, 543 Internet Draft , 544 March 1999., Constraint-Based LSP Setup using LDP, 545 Jamoussi, Internet Draft , Feb. 1999." 547 ::= { mplsTunnelEntry 12 } 549 mplsTunnelHoldingPrio OBJECT-TYPE 550 SYNTAX INTEGER (0..7) 551 MAX-ACCESS read-create 552 STATUS current 553 DESCRIPTION 554 "The holding priority for this tunnel." 555 REFERENCE 556 " Extensions to RSVP for LSP Tunnels, Awduche et al, 557 Internet Draft , 558 March 1999., Constraint-Based LSP Setup using LDP, 559 Jamoussi, Internet Draft , Feb. 1999." 561 ::= { mplsTunnelEntry 13 } 563 -- When resource allocation is performed as requested by 564 -- the following incoming TSpec objects, they are copied 565 -- into an entry in mplsTSpecTable [LSRMIB]: mplsTunnelInMaxRate 566 -- to mplsTSpecMaxRate, mplsTunnelInMeanRate to 567 -- mplsTSpecMeanRate, and mplsTunnelInMaxBurstSize 568 -- to mplsTSpecMaxBurstSize; mplsTSpecDirection of this 569 -- entry is set to in(1). The mplsTSpecIndex value of this 570 -- entry is copied to mplsInSegmentTSpecIndex of the 571 -- corresponding in-segment entry. 573 mplsTunnelInMaxRate OBJECT-TYPE 574 SYNTAX BitRate 575 UNITS "bits per second" 576 MAX-ACCESS read-create 577 STATUS current 578 DESCRIPTION 579 "The maximum incoming rate in bits/second. Note that 580 setting mplsTunnelInMaxRate, mplsTunnelInMeanRate, 581 and mplsTunnelInMaxBurstSize to 0 indicates best- 582 effort treatment. This object is copied to an 583 instance of mplsTSpecMaxRate in mplsTSpecTable the 584 index of which is copied into the corresponding 585 mplsInSegmentTSpecIndex." 586 REFERENCE 587 "MPLS Label Switch Router Management Information Base 588 Using SMIv2, Srinivasan and Viswanathan, draft-ietf- 589 mpls-lsr-mib-00.txt, June 1999." 590 DEFVAL { 0 } 591 ::= { mplsTunnelEntry 14 } 593 mplsTunnelInMeanRate OBJECT-TYPE 594 SYNTAX BitRate 595 UNITS "bits per second" 596 MAX-ACCESS read-create 597 STATUS current 598 DESCRIPTION 599 "This object is copied to an instance of 600 mplsTSpecMeanRate in mplsTSpecTable the index of 601 which is copied into the corresponding 602 mplsInSegmentTSpecIndex." 603 REFERENCE 604 "MPLS Label Switch Router Management Information Base 605 Using SMIv2, Srinivasan and Viswanathan, draft-ietf- 606 mpls-lsr-mib-00.txt, June 1999." 607 DEFVAL { 0 } 608 ::= { mplsTunnelEntry 15 } 610 mplsTunnelInMaxBurstSize OBJECT-TYPE 611 SYNTAX BurstSize 612 UNITS "bytes" 613 MAX-ACCESS read-create 614 STATUS current 615 DESCRIPTION 616 "The maximum burst size in bytes. This object is 617 copied to mplsInSegmentMaxBurstSize of the 618 corresponding in-segment." 619 REFERENCE 620 "MPLS Label Switch Router Management Information Base 621 Using SMIv2, Srinivasan and Viswanathan, draft-ietf- 622 mpls-lsr-mib-00.txt, June 1999." 623 DEFVAL { 0 } 624 ::= { mplsTunnelEntry 16 } 626 -- When resource allocation is performed as requested by 627 -- the following outgoing TSpec objects, they are copied 628 -- into an entry in mplsTSpecTable [LSRMIB]: mplsTunnelOutMaxRate 629 -- to mplsTSpecMaxRate, mplsTunnelOutMeanRate to 630 -- mplsTSpecMeanRate, and mplsTunnelOutMaxBurstSize 631 -- to mplsTSpecMaxBurstSize; mplsTSpecDirection of this 632 -- entry is set to out(2). The mplsTSpecIndex value of this 633 -- entry is copied to mplsOutSegmentTSpecIndex of the 634 -- corresponding out-segment entry. 636 mplsTunnelOutMaxRate OBJECT-TYPE 637 SYNTAX BitRate 638 UNITS "bits per second" 639 MAX-ACCESS read-create 640 STATUS current 641 DESCRIPTION 642 "The maximum outgoing rate in bits/second. Note that 643 setting mplsTunnelOutMaxRate, mplsTunnelOutMeanRate, 644 and mplsTunnelOutMaxBurstSize to 0 indicates best- 645 effort treatment. This object is copied to 646 mplsOutSegmentMaxRate of the corresponding out- 647 segment." 648 REFERENCE 649 "MPLS Label Switch Router Management Information Base 650 Using SMIv2, Srinivasan and Viswanathan, draft-ietf- 651 mpls-lsr-mib-00.txt, June 1999." 652 DEFVAL { 0 } 653 ::= { mplsTunnelEntry 17 } 655 mplsTunnelOutMeanRate OBJECT-TYPE 656 SYNTAX BitRate 657 UNITS "bits per second" 658 MAX-ACCESS read-create 659 STATUS current 660 DESCRIPTION 661 "The mean outgoing rate in bits/second. This object 662 is copied to mplsOutSegmentMeanRate of the 663 corresponding out-segment." 664 REFERENCE 665 "MPLS Label Switch Router Management Information Base 666 Using SMIv2, Srinivasan and Viswanathan, draft-ietf- 667 mpls-lsr-mib-00.txt, June 1999." 668 DEFVAL { 0 } 669 ::= { mplsTunnelEntry 18 } 671 mplsTunnelOutMaxBurstSize OBJECT-TYPE 672 SYNTAX BurstSize 673 UNITS "bytes" 674 MAX-ACCESS read-create 675 STATUS current 676 DESCRIPTION 677 "The maximum burst size in bytes. This object is 678 copied to mplsOutSegmentMaxBurstSize of the 679 corresponding out-segment." 680 REFERENCE 681 "MPLS Label Switch Router Management Information Base 682 Using SMIv2, Srinivasan and Viswanathan, draft-ietf- 683 mpls-lsr-mib-00.txt, June 1999." 684 DEFVAL { 0 } 685 ::= { mplsTunnelEntry 19 } 687 mplsTunnelIsPinned OBJECT-TYPE 688 SYNTAX TruthValue 689 MAX-ACCESS read-create 690 STATUS current 691 DESCRIPTION 692 "Indicates whether the loose-routed hops of this 693 tunnel are to be pinned." 694 DEFVAL { false } 695 ::= { mplsTunnelEntry 20 } 697 mplsTunnelIsPersistent OBJECT-TYPE 698 SYNTAX TruthValue 699 MAX-ACCESS read-create 700 STATUS current 701 DESCRIPTION 702 "Indicates whether this tunnel should be restored 703 automatically after failures." 704 DEFVAL { true } 705 ::= { mplsTunnelEntry 21 } 707 mplsTunnelAdminStatus OBJECT-TYPE 708 SYNTAX INTEGER { 709 up(1), -- ready to pass packets 710 down(2), 711 testing(3) -- in some test mode 712 } 713 MAX-ACCESS read-create 714 STATUS current 715 DESCRIPTION 716 "Desired status of this tunnel." 717 ::= { mplsTunnelEntry 22 } 719 mplsTunnelOperStatus OBJECT-TYPE 720 SYNTAX INTEGER { 721 up(1), -- ready to pass packets 722 down(2), 723 testing(3), -- in some test mode 724 unknown(4), -- status cannot be determined for some 725 -- reason 726 dormant(5), 727 notPresent(6), -- some component is missing 728 lowerLayerNotPresent(7) 729 -- down due to the state of 730 -- lower layer interfaces 731 } 732 MAX-ACCESS read-only 733 STATUS current 734 DESCRIPTION 735 "The operational status of this tunnel, typically a 736 function of the state of individual segments of this 737 tunnel, among other things." 738 ::= { mplsTunnelEntry 23 } 740 mplsTunnelRowStatus OBJECT-TYPE 741 SYNTAX RowStatus 742 MAX-ACCESS read-create 743 STATUS current 744 DESCRIPTION 745 "For controlling the state of this row." 746 ::= { mplsTunnelEntry 24 } 748 -- End of mplsTunnelTable 750 -- Maximum number of tunnel hops supported. 752 mplsTunnelMaxHops OBJECT-TYPE 753 SYNTAX RowStatus 754 MAX-ACCESS read-only 755 STATUS current 756 DESCRIPTION 757 "The maximum number of hops that can be specified for 758 a tunnel on this device." 759 ::= { mplsTeObjects 2 } 761 -- Tunnel hop table. 763 mplsTunnelHopTable OBJECT-TYPE 764 SYNTAX SEQUENCE OF MplsTunnelEntry 765 MAX-ACCESS not-accessible 766 STATUS current 767 DESCRIPTION 768 "The mplsTunnelHopTable is used to indicate the hops, 769 strict or loose, for an MPLS tunnel defined in 770 mplsTunnelTable, when it is established via 771 signaling, for the outgoing direction of the tunnel. 772 Each row in this table is indexed primarily by the 773 same index, mplsTunnelIndex, as the row of the 774 corresponding tunnel in mplsTunnelTable. Each row 775 also has a secondary index mplsTunnelHopIndex 776 corresponding to the next hop that this row 777 corresponds to. The first row in the table is the 778 first hop after the origination point of the tunnel. 779 In case we want to specify a particular interface on 780 the originating LSR of an outgoing tunnel by which 781 we want packets to exit the LSR, we specify this as 782 the first hop for this tunnel in 783 mplsTunnelHopTable." 784 ::= { mplsTeObjects 3 } 786 mplsTunnelHopEntry OBJECT-TYPE 787 SYNTAX MplsTunnelHopEntry 788 MAX-ACCESS not-accessible 789 STATUS current 790 DESCRIPTION 791 "An entry in this table represents a tunnel hop. An 792 entry is created by a network administrator for 793 signalled ERLSP set up by LDP or RSVP." 794 INDEX { mplsTunnelIndex, mplsTunnelHopIndex } 795 ::= { mplsTunnelHopTable 1 } 797 MplsTunnelHopEntry ::= SEQUENCE { 798 mplsTunnelHopIndex Integer32, 799 mplsTunnelHopAddrType INTEGER, 800 mplsTunnelHopIpv4Addr IpAddress, 801 mplsTunnelHopIpv4PrefixLen INTEGER, 802 mplsTunnelHopIpv6Addr Ipv6Address, 803 mplsTunnelHopIpv6PrefixLen INTEGER, 804 mplsTunnelHopAsNumber INTEGER, 805 mplsTunnelHopStrictOrLoose INTEGER, 806 mplsTunnelHopRowStatus RowStatus 807 } 809 mplsTunnelHopIndex OBJECT-TYPE 810 SYNTAX Integer32 811 MAX-ACCESS not-accessible 812 STATUS current 813 DESCRIPTION 814 "Secondary index into this table identifying the 815 particular hop." 816 ::= { mplsTunnelHopEntry 1 } 818 mplsTunnelHopAddrType OBJECT-TYPE 819 SYNTAX INTEGER { ipV4(1), ipV6(2), asNumber(3) } 820 MAX-ACCESS read-create 821 STATUS current 822 DESCRIPTION 823 "Address type of this hop." 824 DEFVAL { ipV4 } 825 ::= { mplsTunnelHopEntry 2 } 827 mplsTunnelHopIpv4Addr OBJECT-TYPE 828 SYNTAX IpAddress 829 MAX-ACCESS read-create 830 STATUS current 831 DESCRIPTION 832 "If mplsTunnelHopAddrType is ipV4(1), IPv4 address of 833 this hop. This object is not significant otherwise 834 and should return a value of 0." 835 ::= { mplsTunnelHopEntry 3 } 837 mplsTunnelHopIpv4PrefixLen OBJECT-TYPE 838 SYNTAX INTEGER (1..32) 839 MAX-ACCESS read-create 840 STATUS current 841 DESCRIPTION 842 "If mplsTunnelHopAddrType is ipV4(1), prefix length 843 for this hop's IPv4 address. This object is not 844 significant otherwise and should return a value of 845 0." 846 ::= { mplsTunnelHopEntry 4 } 848 mplsTunnelHopIpv6Addr OBJECT-TYPE 849 SYNTAX Ipv6Address 850 MAX-ACCESS read-create 851 STATUS current 852 DESCRIPTION 853 "If mplsTunnelHopAddrType is ipV6(2), the IPv6 854 address of this hop. This object is not significant 855 otherwise and should return a value of 0." 856 ::= { mplsTunnelHopEntry 5 } 858 mplsTunnelHopIpv6PrefixLen OBJECT-TYPE 859 SYNTAX INTEGER (1..128) 860 MAX-ACCESS read-create 861 STATUS current 862 DESCRIPTION 863 "If mplsTunnelHopAddrType is ipV6(2), prefix length 864 for this hop's IPv6 address. This object is not 865 significant otherwise and should return a value of 866 0." 867 ::= { mplsTunnelHopEntry 6 } 869 mplsTunnelHopAsNumber OBJECT-TYPE 870 SYNTAX INTEGER (0..65535) 871 MAX-ACCESS read-create 872 STATUS current 873 DESCRIPTION 874 "If mplsTunnelHopAddrType is asNumber(3), the AS 875 number this hop. This object is not significant 876 otherwise and should return a value of 0." 877 ::= { mplsTunnelHopEntry 7 } 879 mplsTunnelHopStrictOrLoose OBJECT-TYPE 880 SYNTAX INTEGER { strict(1), loose(2) } 881 MAX-ACCESS read-create 882 STATUS current 883 DESCRIPTION 884 "Whether this is a strict or loose hop." 885 ::= { mplsTunnelHopEntry 8 } 887 mplsTunnelHopRowStatus OBJECT-TYPE 888 SYNTAX RowStatus 889 MAX-ACCESS read-create 890 STATUS current 891 DESCRIPTION 892 "For creating, modifying and deleting this row." 893 ::= { mplsTunnelHopEntry 9 } 895 -- End of mplsTunnelHopTable 897 -- Notifications. 899 mplsTunnelUp NOTIFICATION-TYPE 900 OBJECTS { mplsTunnelIndex, mplsTunnelAdminStatus, 901 mplsTunnelOperStatus } 902 STATUS current 903 DESCRIPTION 904 "This notification is generated when a 905 mplsTunnelOperStatus object for one of the 906 configured tunnels is about to leave the down state 907 and transition into some other state (but not into 908 the notPresent state). This other state is 909 indicated by the included value of 910 mplsTunnelOperStatus." 911 ::= { mplsTeNotifications 1 } 913 mplsTunnelDown NOTIFICATION-TYPE 914 OBJECTS { mplsTunnelIndex, mplsTunnelAdminStatus, 915 mplsTunnelOperStatus } 916 STATUS current 917 DESCRIPTION 918 "This notification is generated when a 919 mplsTunnelOperStatus object for one of the 920 configured tunnels is about to enter the down state 921 from some other state (but not from the notPresent 922 state). This other state is indicated by the 923 included value of mplsTunnelOperStatus." 924 ::= { mplsTeNotifications 2 } 926 -- End of notifications. 928 -- Module compliance. 930 mplsTeGroups 931 OBJECT IDENTIFIER ::= { mplsTeConformance 1 } 933 mplsTeCompliances 934 OBJECT IDENTIFIER ::= { mplsTeConformance 2 } 936 mplsTeModuleCompliance MODULE-COMPLIANCE 937 STATUS current 938 DESCRIPTION 939 "Compliance statement for agents that support the 940 MPLS TE MIB." 941 MODULE -- this module 943 -- The mandatory group has to be implemented by all LSRs 944 -- that originate/terminate ESLSPs/tunnels. 945 -- In addition, depending on the type of tunnels 946 -- supported, other groups become mandatory as explained 947 -- below. 949 MANDATORY-GROUPS { mplsTunnelGroup } 951 GROUP mplsTunnelManualGroup 952 DESCRIPTION 953 "This group is mandatory for devices which 954 support manual configuration of tunnels, in 955 addition to mplsTunnelGroup. The following 956 constraints apply: mplsTunnelSignallingProto 957 should be at least read-only with a value of 958 none(1)." 960 GROUP mplsTunnelSignalledGroup 961 DESCRIPTION 962 "This group is mandatory for devices which 963 support signalled tunnel set up, in addition to 964 mplsTunnelGroup. The following constraints 965 apply: mplsTunnelSignallingProto should be at 966 least read-only returning a value of ldp(2), or 967 rsvp(3)." 969 GROUP mplsTunnelIsNotIntfcGroup 970 DESCRIPTION 971 "This group is mandatory for devices which 972 support tunnels that are not interfaces, in 973 addition to mplsTunnelGroup. The following 974 constraints apply: mplsTunnelIsIf must at least 975 be read-only returning false(1)." 977 GROUP mplsTunnelIsIntfcGroup 978 DESCRIPTION 979 "This group is mandatory for devices which 980 support tunnels that are interfaces, in addition 981 to mplsTunnelGroup. The following constraints 982 apply: mplsTunnelIsIf must at least be read-only 983 returning true(2)." 985 GROUP mplsTunnelIsPersistentGroup 986 DESCRIPTION 987 "This group is mandatory for devices which 988 support persistent tunnels, in addition to 989 mplsTunnelGroup. The following constraints 990 apply: mplsTunnelIsPersistent must at least be 991 read-only returning true(2)." 993 GROUP mplsTunnelIsNotPersistentGroup 994 DESCRIPTION 995 "This group is mandatory for devices which 996 support non-persistent tunnels, in addition to 997 mplsTunnelGroup. The following constraints 998 apply: mplsTunnelIsPersistent must at least be 999 read-only returning false(1)." 1001 -- mplsTunnelTable 1003 OBJECT mplsTunnelIndex 1004 MIN-ACCESS read-only 1005 DESCRIPTION 1006 "Write access is not required." 1008 OBJECT mplsTunnelName 1009 MIN-ACCESS read-only 1010 DESCRIPTION 1011 "Write access is not required." 1013 OBJECT mplsTunnelDescr 1014 MIN-ACCESS read-only 1015 DESCRIPTION 1016 "Write access is not required." 1018 OBJECT mplsTunnelIsIf 1019 MIN-ACCESS read-only 1020 DESCRIPTION 1021 "Write access is not required." 1023 OBJECT mplsTunnelIfIndex 1024 MIN-ACCESS read-only 1025 DESCRIPTION 1026 "Write access is not required." 1028 OBJECT mplsTunnelDirection 1029 SYNTAX INTEGER { out(2) } 1030 MIN-ACCESS read-only 1031 DESCRIPTION 1032 "The values in(1) and in-out(3) need not be 1033 supported." 1035 OBJECT mplsTunnelXCIndex 1036 MIN-ACCESS read-only 1037 DESCRIPTION 1038 "Write access is not required." 1040 OBJECT mplsTunnelSignallingProto 1041 MIN-ACCESS read-only 1042 DESCRIPTION 1043 "Write access is not required." 1045 OBJECT mplsTunnelLocalCookie 1046 MIN-ACCESS read-only 1047 DESCRIPTION 1048 "Write access is not required." 1050 OBJECT mplsTunnelRemoteCookie 1051 MIN-ACCESS read-only 1052 DESCRIPTION 1053 "Write access is not required." 1055 OBJECT mplsTunnelIsMergeable 1056 MIN-ACCESS read-only 1057 DESCRIPTION 1058 "Write access is not required." 1060 OBJECT mplsTunnelSetupPrio 1061 MIN-ACCESS read-only 1062 DESCRIPTION 1063 "Write access is not required." 1065 OBJECT mplsTunnelHoldingPrio 1066 MIN-ACCESS read-only 1067 DESCRIPTION 1068 "Write access is not required." 1070 OBJECT mplsTunnelInMaxRate 1071 MIN-ACCESS read-only 1072 DESCRIPTION 1073 "Write access is not required." 1075 OBJECT mplsTunnelInMeanRate 1076 MIN-ACCESS read-only 1077 DESCRIPTION 1078 "Write access is not required." 1080 OBJECT mplsTunnelInMaxBurstSize 1081 MIN-ACCESS read-only 1082 DESCRIPTION 1083 "Write access is not required." 1085 OBJECT mplsTunnelOutMaxRate 1086 MIN-ACCESS read-only 1087 DESCRIPTION 1088 "Write access is not required." 1090 OBJECT mplsTunnelOutMeanRate 1091 MIN-ACCESS read-only 1092 DESCRIPTION 1093 "Write access is not required." 1095 OBJECT mplsTunnelOutMaxBurstSize 1096 MIN-ACCESS read-only 1097 DESCRIPTION 1098 "Write access is not required." 1100 OBJECT mplsTunnelIsPinned 1101 MIN-ACCESS read-only 1102 DESCRIPTION 1103 "Write access is not required." 1105 OBJECT mplsTunnelIsPersistent 1106 MIN-ACCESS read-only 1107 DESCRIPTION 1108 "Write access is not required." 1110 OBJECT mplsTunnelAdminStatus 1111 SYNTAX INTEGER { up (1), down (2) } 1112 MIN-ACCESS read-only 1113 DESCRIPTION 1114 "Only up and down states need to be supported. 1115 Write access is not required." 1117 OBJECT mplsTunnelOperStatus 1118 SYNTAX INTEGER { up (1), down (2) } 1119 MIN-ACCESS read-only 1120 DESCRIPTION 1121 "Only up and down states need to be supported. 1122 Write access is not required." 1124 OBJECT mplsTunnelRowStatus 1125 SYNTAX INTEGER { active(1), notInService(2), 1126 createAndGo(4), destroy(6) } 1127 MIN-ACCESS read-only 1128 DESCRIPTION 1129 "The notReady(3) and createAndWait(5) states need 1130 not be supported. Write access is not required." 1132 -- mplsTunnelHopTable 1134 OBJECT mplsTunnelHopIndex 1135 MIN-ACCESS read-only 1136 DESCRIPTION 1137 "Write access is not required." 1139 OBJECT mplsTunnelHopAddrType 1140 MIN-ACCESS read-only 1141 DESCRIPTION 1142 "Write access is not required." 1144 OBJECT mplsTunnelHopIpv4Addr 1145 MIN-ACCESS read-only 1146 DESCRIPTION 1147 "Write access is not required." 1149 OBJECT mplsTunnelHopIpv4PrefixLen 1150 MIN-ACCESS read-only 1151 DESCRIPTION 1152 "Write access is not required." 1154 OBJECT mplsTunnelHopIpv6Addr 1155 MIN-ACCESS read-only 1156 DESCRIPTION 1157 "Write access is not required." 1159 OBJECT mplsTunnelHopIpv6PrefixLen 1160 MIN-ACCESS read-only 1161 DESCRIPTION 1162 "Write access is not required." 1164 OBJECT mplsTunnelHopAsNumber 1165 MIN-ACCESS read-only 1166 DESCRIPTION 1167 "Write access is not required." 1169 OBJECT mplsTunnelHopStrictOrLoose 1170 SYNTAX INTEGER { strict(1) } 1171 MIN-ACCESS read-only 1172 DESCRIPTION 1173 "loose(2) need not be supported. Write access is 1174 not required." 1176 OBJECT mplsTunnelHopRowStatus 1177 SYNTAX INTEGER { active(1), notInService(2), 1178 createAndGo(4), destroy(6) } 1179 MIN-ACCESS read-only 1180 DESCRIPTION 1181 "The notReady(3) and createAndWait(5) states need 1182 not be supported. Write access is not required." 1184 ::= { mplsTeCompliances 1 } 1186 -- Units of conformance. 1188 mplsTunnelGroup OBJECT-GROUP 1189 OBJECTS { mplsTunnelIndex, mplsTunnelName, 1190 mplsTunnelDirection, mplsTunnelXCIndex, 1191 mplsTunnelIfIndex, 1192 mplsTunnelAdminStatus, mplsTunnelOperStatus, 1193 mplsTunnelRowStatus } 1194 STATUS current 1195 DESCRIPTION 1196 "Necessary, but not sufficient, set of objects to 1197 implement tunnels. In addition, depending on the 1198 type of the tunnels supported (for example, manually 1199 configured or signalled, persistent or non- 1200 persistent, etc.), the following other groups 1201 defined below are mandatory: mplsTunnelManualGroup 1202 and/or mplsTunnelSignalledGroup, 1203 mplsTunnelIsNotIntfcGroup and/or 1204 mplsTunnelIsIntfcGroup, mplsTunnelIsPersistent 1205 and/or mplsTunnelIsNotPersistent." 1206 ::= { mplsTeGroups 1 } 1208 mplsTunnelManualGroup OBJECT-GROUP 1209 OBJECTS { mplsTunnelSignallingProto } 1210 STATUS current 1211 DESCRIPTION 1212 "Object(s) needed to implement manually configured 1213 tunnels." 1214 ::= { mplsTeGroups 2 } 1216 mplsTunnelSignalledGroup OBJECT-GROUP 1217 OBJECTS { mplsTunnelSignallingProto, 1218 mplsTunnelLocalCookie, mplsTunnelRemoteCookie, 1219 mplsTunnelHopIndex, mplsTunnelHopAddrType, 1220 mplsTunnelHopIpv4Addr, mplsTunnelHopIpv4PrefixLen, 1221 mplsTunnelHopIpv6Addr, mplsTunnelHopIpv6PrefixLen, 1222 mplsTunnelHopStrictOrLoose, mplsTunnelHopRowStatus } 1223 STATUS current 1224 DESCRIPTION 1225 "Object needed to implement signalled tunnels." 1226 ::= { mplsTeGroups 3 } 1228 mplsTunnelIsIntfcGroup OBJECT-GROUP 1229 OBJECTS { mplsTunnelIsIf } 1230 STATUS current 1231 DESCRIPTION 1232 "Objects needed to implement tunnels that are 1233 interfaces." 1234 ::= { mplsTeGroups 4 } 1236 mplsTunnelIsNotIntfcGroup OBJECT-GROUP 1237 OBJECTS { mplsTunnelIsIf } 1238 STATUS current 1239 DESCRIPTION 1240 "Objects needed to implement tunnels that are not 1241 interfaces." 1242 ::= { mplsTeGroups 5 } 1244 mplsTunnelIsPersistentGroup OBJECT-GROUP 1245 OBJECTS { mplsTunnelIsPersistent } 1246 STATUS current 1247 DESCRIPTION 1248 "Objects needed to support persistent tunnels." 1249 ::= { mplsTeGroups 6 } 1251 mplsTunnelIsNotPersistentGroup OBJECT-GROUP 1252 OBJECTS { mplsTunnelIsPersistent } 1253 STATUS current 1254 DESCRIPTION 1255 "Objects needed to support non-persistent tunnels." 1256 ::= { mplsTeGroups 7 } 1258 mplsTeNotificationGroup NOTIFICATION-GROUP 1259 NOTIFICATIONS { mplsTunnelUp, mplsTunnelDown } 1260 STATUS current 1261 DESCRIPTION 1262 "Set of notifications implemented in this module. 1263 None is mandatory." 1264 ::= { mplsTeGroups 8 } 1266 -- End of MPLS-TE-MIB 1267 END 1268 8. Security Considerations 1270 The MIB specified in this document does not raise any security 1271 issues other than those present in the MPLS architecture 1272 [MPLSArch] or those imposed by SNMP itself. 1274 9. Acknowledgments 1276 We wish to thank Eric Gray, Patrick Kerharo, and Pramod Koppol for 1277 their comments on this draft. 1279 10. References 1281 [MPLSArch] Rosen, E., Viswanathan, A., and R. Callon, 1282 "Multiprotocol Label Switching Architecture", 1283 Internet Draft , 1284 February 1999. 1286 [MPLSFW] Callon, R., Doolan, P., Feldman, N., Fredette, A., 1287 Swallow, G., and A. Viswanathan, "A Framework for 1288 Multiprotocol Label Switching", Internet Draft 1289 , November 1997. 1291 [LSRMIB] Srinivasan, C., and A. Viswanathan, "MPLS Label 1292 Switch Router Management Information Base Using 1293 SMIv2", Internet Draft , June 1999. 1296 [LDPMIB] Cucchiara, J., Sjostrand, H., and J. Luciani, 1297 "Definitions of Managed Objects for the 1298 Multiprotocol Label Switching, Label Distribution 1299 Protocol (LDP)", Internet Draft , August 1998. 1302 [LblStk] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D., 1303 Federokow, G., Li, T., and A. Conta, "MPLS Label 1304 Stack Encoding", Internet Draft , April 1999. 1307 [RSVPTun] Awaduche, D., Berger, L., Der-Haw, G., Li, T., 1308 Swallow, G., and V. Srinivasan, "Extensions to RSVP 1309 for LSP Tunnels", Internet Draft , March 1999. 1312 [CRLDP] B. Jamoussi (Editor), "Constraint-Based LSP Setup 1313 using LDP", Internet Draft , February 1999. 1316 [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", 1317 RFC 1700, October 1994. See also: 1318 http://www.isi.edu/in-notes/iana/assignments/smi- 1319 numbers 1321 [SNMPArch] Harrington, D., Presuhn, R., and B. Wijnen, "An 1322 Architecture for Describing SNMP Management 1323 Frameworks", RFC 2271, January 1998. 1325 [SMIv1] Rose, M., and K. McCloghrie, "Structure and 1326 Identification of Management Information for TCP/IP- 1327 based Internets", RFC 1155, May 1990. 1329 [SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB 1330 Definitions", RFC 1212, March 1991. 1332 [SNMPv1Traps] M. Rose, "A Convention for Defining Traps for use 1333 with the SNMP", RFC 1215, March 1991. 1335 [SMIv2] Case, J., McCloghrie, K., Rose, M., and S. 1336 Waldbusser, "Structure of Management Information 1337 for Version 2 of the Simple Network Management 1338 Protocol (SNMPv2)", RFC 1902, January 1996. 1340 [SNMPv2TC] Case, J., McCloghrie, K., Rose, M., and S. 1341 Waldbusser, "Textual Conventions for Version 2 of 1342 the Simple Network Management Protocol (SNMPv2)", 1343 RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., 1344 January 1996. 1346 [SNMPv2Conf] Case, J., McCloghrie, K., Rose, M., and S. 1347 Waldbusser, "Conformance Statements for Version 2 1348 of the Simple Network Management Protocol 1349 (SNMPv2)", RFC 1904, January 1996. 1351 [SNMPv1] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 1352 "Simple Network Management Protocol", RFC 1157, May 1353 1990. 1355 [SNMPv2c] Case, J., McCloghrie, K., Rose, M., and S. 1356 Waldbusser, "Introduction to Community-based 1357 SNMPv2", RFC 1901, January 1996. 1359 [SNMPv2TM] Case, J., McCloghrie, K., Rose, M., and S. 1360 Waldbusser, "Transport Mappings for Version 2 of 1361 the Simple Network Management Protocol (SNMPv2)", 1362 RFC 1906, January 1996. 1364 [SNMPv3MP] Case, J., Harrington D., Presuhn R., and B. Wijnen, 1365 "Message Processing and Dispatching for the Simple 1366 Network Management Protocol (SNMP)", RFC 2272, 1367 January 1998. 1369 [SNMPv3USM] Blumenthal, U., and B. Wijnen, "User-based Security 1370 Model (USM) for version 3 of the Simple Network 1371 Management Protocol (SNMPv3)", RFC 2274, January 1372 1998. 1374 [SNMPv2PO] Case, J., McCloghrie, K., Rose, M., and S. 1375 Waldbusser, "Protocol Operations for Version 2 of 1376 the Simple Network Management Protocol (SNMPv2)", 1377 RFC 1905, January 1996. 1379 [SNMPv3App] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 1380 Applications", RFC 2273, January 1998 1382 [SNMPv3VACM] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- 1383 based Access Control Model (VACM) for the Simple 1384 Network Management Protocol (SNMP)", RFC 2275, 1385 January 1998 1387 11. Authors's Addresses 1389 Cheenu Srinivasan 1390 Tachion Network Technologies 1391 2 Meridian Road 1392 Eatontown, NJ 07724 1394 Phone: +1-732-542-7750 x234 1395 Email: cheenu@tachion.com 1397 Arun Viswanathan 1398 Lucent Technologies 1399 4D537, 101 Crawfords Corner Road 1400 Holmdel, NJ 07733 1402 Phone: +1-732-332-5163 1403 Email: arunv@lucent.com