idnits 2.17.1 draft-srinivasan-mpls-te-mib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-24) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** 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 138 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? ** There are 8 instances of too long lines in the document, the longest one being 4 characters in excess of 72. ** There are 556 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 17 has weird spacing: '... This docum...' == Line 18 has weird spacing: '...cuments of t...' == Line 19 has weird spacing: '... groups may ...' == Line 22 has weird spacing: '...maximum of s...' == Line 24 has weird spacing: '... other docum...' == (133 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.) -- The document date (January 11, 1999) is 9235 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '2' is defined on line 2283, but no explicit reference was found in the text == Unused Reference: '6' is defined on line 2302, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. '1' -- Possible downref: Non-RFC (?) normative reference: ref. '2' -- Possible downref: Non-RFC (?) normative reference: ref. '3' -- Possible downref: Non-RFC (?) normative reference: ref. '4' -- Possible downref: Non-RFC (?) normative reference: ref. '5' ** Obsolete normative reference: RFC 1700 (ref. '6') (Obsoleted by RFC 3232) ** Obsolete normative reference: RFC 2271 (ref. '7') (Obsoleted by RFC 2571) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '10') ** Obsolete normative reference: RFC 1902 (ref. '11') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '12') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '13') (Obsoleted by RFC 2580) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '14') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '15') ** Obsolete normative reference: RFC 1906 (ref. '16') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2272 (ref. '17') (Obsoleted by RFC 2572) ** Obsolete normative reference: RFC 2274 (ref. '18') (Obsoleted by RFC 2574) ** Obsolete normative reference: RFC 1905 (ref. '19') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2273 (ref. '20') (Obsoleted by RFC 2573) ** Obsolete normative reference: RFC 2275 (ref. '21') (Obsoleted by RFC 2575) Summary: 28 errors (**), 0 flaws (~~), 9 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 MPLS Traffic Engineering Management Information Base 3 draft-srinivasan-mpls-te-mib-01.txt 5 January 11, 1999 7 Cheenu Srinivasan 8 Lucent Technologies 9 cheenu@lucent.com 11 Arun Viswanathan 12 Lucent Technologies 13 arunv@lucent.com 15 Status of this Memo 17 This document is an Internet Draft. Internet Drafts are working 18 documents of the Internet Engineering Task Force (IETF), its 19 Areas, and its Working Groups. Note that other groups may also 20 distribute working documents as Internet Drafts. 22 Internet Drafts are draft documents valid for a maximum of six 23 months. Internet Drafts may be updated, replaced, or obsoleted by 24 other documents at any time. It is not appropriate to use 25 Internet Drafts as reference material or to cite them other than 26 as a "working draft" or "work in progress." 28 Please check the I-D abstract listing contained in each Internet 29 Draft directory to learn the current status of this or any other 30 Internet Draft. 32 Abstract 34 This memo defines an experimental portion of the Management 35 Information Base (MIB) for use with network management protocols 36 in the Internet community. In particular it describes managed 37 objects for Multi-Protocol Label Switching (MPLS) [1, 2] based 38 traffic engineering. 40 1. Introduction 42 This memo defines an experimental portion of the Management 43 Information Base (MIB) for use with network management protocols 44 in the Internet community. In particular it describes managed 45 objects for Multi-Protocol Label Switching (MPLS) [1, 2] based 46 traffic engineering, including tunnels and cross-connects. 47 Comments should be made directly to the MPLS mailing list at 48 mpls@external.cisco.com. 50 This memo does not, in its draft form, specify a standard for the 51 Internet community. 53 2. Terminology 55 This document uses terminology from the MPLS architecture document 56 [1]. 58 An explicitly routed LSP is referred to as an MPLS tunnel. It 59 consists of one in-segment and/or one out-segment at the 60 ingress/egress LSRs. These are also referred to as tunnel 61 segments. Additionally, at an intermediate LSR, we model a 62 connection as consisting of one or more in-segments and/or one or 63 more out-segments. The binding or interconnection between in- 64 segments and out-segments in performed using a cross-connect. 66 3. The SNMP Management Framework 68 The SNMP Management Framework presently consists of five major 69 components: 71 - An overall architecture, described in RFC 2271 [7]. 73 - Mechanisms for describing and naming objects and events for the 74 purpose of management. The first version of this Structure of 75 Management Information (SMI) is called SMIv1 and described in 76 RFC 1155 [8], RFC 1212 [9] and RFC 1215 [10]. The second 77 version, called SMIv2, is described in RFC 1902 [11], RFC 1903 78 [12] and RFC 1904 [13]. 80 - Message protocols for transferring management information. The 81 first version of the SNMP message protocol is called SNMPv1 82 and described in RFC 1157 [14]. A second version of the SNMP 83 message protocol, which is not an Internet standards track 84 protocol, is called SNMPv2c and described in RFC 1901 [15] and 85 RFC 1906 [16]. The third version of the message protocol is 86 called SNMPv3 and described in RFC 1906 [16], RFC 2272 [17] 87 and RFC 2274 [18]. 89 - Protocol operations for accessing management information. The 90 first set of protocol operations and associated PDU formats is 91 described in RFC 1157 [14]. A second set of protocol 92 operations and associated PDU formats is described in RFC 1905 93 [19]. 95 - A set of fundamental applications described in RFC 2273 [20] 96 and the view-based access control mechanism described in RFC 97 2275 [21]. Managed objects are accessed via a virtual 98 information store, termed the Management Information Base or 99 MIB. Objects in the MIB are defined using the mechanisms 100 defined in the SMI. This memo specifies a MIB module that is 101 compliant to the SMIv2. A MIB conforming to the SMIv1 can be 102 produced through the appropriate translations. The resulting 103 translated MIB must be semantically equivalent, except where 104 objects or events are omitted because no translation is 105 possible (use of Counter64). Some machine readable 106 information in SMIv2 will be converted into textual 107 descriptions in SMIv1 during the translation process. 108 However, this loss of machine readable information is not 109 considered to change the semantics of the MIB. 111 3.1. Object Definitions 113 Managed objects are accessed via a virtual information store, 114 termed the Management Information Base or MIB. Objects in the MIB 115 are defined using the subset of Abstract Syntax Notation One 116 (ASN.1) defined in the SMI. In particular, each object type is 117 named by an OBJECT IDENTIFIER, an administratively assigned name. 118 The object type together with an object instance serves to 119 uniquely identify a specific instantiation of the object. For 120 human convenience, we often use a textual string, termed the 121 descriptor, to also refer to the object type. 123 4. Feature Checklist 125 The MPLS traffic engineering MIB is designed to satisfy the 126 following requirements and constraints. 128 - The MIB must support the configuration of point-to-point uni- 129 directional tunnels. 131 - The MIB should be able to support the configuration of point-to- 132 point bi-directional tunnels. 134 - The MIB should be able to support the configuration of 135 multipoint-to-point unidirectional tunnels. 137 - MPLS tunnels need not be interfaces, but it should be possible 138 to configure a tunnel as an interface. 140 - The MIB should be able to support both manually configured MPLS 141 tunnels and cross-connects as well as via LDP and/or RSVP 142 signalling. 144 - MPLS packets must be forwarded solely based on an incoming top 145 label [1, 3]. 147 - Support must be provided for next-hop resolution when the 148 outgoing interface is a shared media interface. In the 149 multicast case, each outgoing segment can be on a different 150 shared media interface. 152 - The MIB must support point-to-point, point-to-multipoint 153 (multicast) and multipoint-to-point connections at a cross- 154 connect LSR. 156 - For multipoint-to-point connections all the outgoing packets 157 must have the same top label. 159 - For multipoint-to-point connections the outgoing resources of 160 the merged connections must be shared. 162 - For multipoint-to-point connections, packets from different 163 incoming connections may have distinct outgoing label stacks, 164 beneath the (identical) top label. 166 - In the multicast case each outgoing connection can have a 167 distinct label stack including the top label. 169 - In a multicast connection the ingress resources are shared by 170 all the members of the connection. 172 - The MIB must provide cross-connect capability to "pop" an 173 incoming label and forward the packet with the rest of the 174 label stack unchanged and without pushing any labels ("pop-and- 175 go") [3]. 177 - It must be possible to assign or remap COS bits [3] on the 178 outgoing label. In the multipoint-to-point case, each in- 179 segment can have a different outgoing COS value. In the 180 multicast case, each out-segment can have a different outgoing 181 COS value. 183 - It should be possible to support persistent as well as non- 184 persistent tunnels and cross-connects. 186 - Performance counters must be provided for in-segments and out- 187 segments. 189 5. Outline 191 Traffic engineering support for MPLS tunnels and cross-connects 192 requires the following configuration. 194 - Setting up MPLS tunnels with the appropriate configuration 195 parameters. 197 - Setting up tunnel segments with appropriate traffic parameters. 199 - Setting up the cross-connect table to switch between segments. 201 - Specifying label stack actions. 203 5.1. Summary of MPLS MIB 205 The MIB objects for performing these actions consist of the 206 following tables. 208 - Tunnel Table (mplsTunnelTable) and Tunnel Hop Table 209 (mplsTunnelHopTable) to configure MPLS tunnels. 211 - In-Segment (mplsInSegmentTable) and Out-Segment 212 (mplsOutSegmentTable) Tables for configuring in and out 213 segment of a tunnel at the ingress and egress LSRs of the 214 tunnel. These tables are also used for defining the segments 215 comprising a cross-connect entry at intermediate LSRs of a 216 tunnel. 218 - Cross-Connect Table (mplsXCTable) for configuring MPLS cross- 219 connects and creating relationships between in and out tunnel 220 segments constituing a cross-connect. 222 - Label Stack Table (mplsLabelStackTable) for specifying label 223 stack operations. 225 Further, the MPLS In-Segment and Out-Segment Performance Tables 226 contain the objects necessary to measure the performance of both 227 tunnels and cross-connects. These tables are described in the 228 subsequent sections. 230 6. MPLS Tunnels 232 The tables described in this section support the functionality 233 described in documents [4, 5]. The tables support both manually 234 configured and signalled tunnels. Moreover, it provides the 235 capability to associate two uni-directional tunnels to form a 236 single bi-directional tunnel. 238 6.1. mplsTunnelTable 240 The mplsTunnelTable allows new MPLS tunnels to be created between 241 an MPLS LSR and a remote endpoint, and existing tunnels to be 242 reconfigured or removed. Note that we only support point-to-point 243 tunnel segments, although multipoint-to-point and point-to- 244 multipoint connections are supported by an LSR acting as a cross- 245 connect. Each MPLS tunnel can thus have one out-segment 246 originating at this LSR and/or one in-segment terminating at this 247 LSR. 249 mplsTunnelTable does not define the in and out segments forming 250 the tunnel. Instead, these are defined by creating rows in the in- 251 segment and out-segment tables, defining relationships in the 252 cross-connect table (Section 5) and referring to these rows in the 253 mplsTunnelTable using a cross-connect index, mplsTunnelXCID. 254 Section 5.7 provides a detailed explanation. 256 6.2. mplsTunnelHopTable 258 mplsTunnelHopTable is used to indicate the hops, strict or loose, 259 for an MPLS tunnel defined in mplsTunnelTable, when it is 260 established via signalling. Each row in this table is indexed 261 primarily by the same index mplsTunnelIndex as the row of the 262 corresponding tunnel in mplsTunnelTable. Each row also has a 263 secondary index mplsTunnelHopIndex corresponding to the next hop 264 of this tunnel. The scalar mplsTunnelMaxHops, indicates the 265 maximum number of hops that can be specified per tunnel on this 266 LSR. 268 7. MPLS Cross-Connect 270 The tables described in this section, when considered together, 271 are equivalent to the tables described in the MPLS architecture 272 document [1], that is, the Next Hop Label Forwarding Entry (NHLFE) 273 and the Incoming Label Map (ILM) tables. 275 7.1. mplsInSegmentTable 277 This table contains a description of the the incoming MPLS 278 segments to an LSR and their traffic parameters. 280 7.2. mplsInSegmentPerfTable 282 The MPLS In-Segment Performance Table has objects to measure the 283 performance of an incoming segment configured on an LSR. It is an 284 AUGMENT to mplsInSegmentTable. 286 7.3. mplsOutSegmentTable 288 The Out-Segment Table contains a description of the the outgoing 289 MPLS segments at an LSR and their traffic parameters. 291 7.4. mplsOutSegmentPerfTable 293 The MPLS Out-Segment Table contains objects to measure the 294 performance of an outgoing segment configured on an LSR. It is an 295 AUGMENT to mplsOutSegmentTable. 297 7.5. mplsXCTable 299 mplsXCTable specifies information for switching between segments. 300 It supports point-to-point, point-to-multipoint (multicasting), 301 and multipoint-to-point (multiplexing) connections. 303 7.6. mplsLabelStackTable 305 mplsLabelStackTable specifies the label stack to be pushed onto a 306 packet, beneath the top label. Entries to this table are referred 307 to from mplsXCTable. 309 7.7. Specifying the Segments of a Tunnel 311 Suppose that we want to manually create a bi-directional tunnel, 312 consiting of an in-segment and an out-segment on an LSR (with no 313 label stack beneath the top label on the outgoing labeled 314 packets). The following rows and corresponding objects need to be 315 created to do this. 317 First, the in-segment and the out-segment are created with the 318 appropriate traffic parameters. 320 In mplsInSegmentTable: 321 { 322 mplsInSegmentIfIndex = i1, 323 mplsInSegmentLabel = l1, 324 mplsInSegmentNPop = 1, 325 mplsInSegmentMaxRate, 326 mplsInSegmentMeanRate, 327 mplsInSegmentMaxBurstSize, 328 mplsInSegmentRowStatus = createAndGo(3) 329 } 331 In mplsOutSegmentTable: 332 { 333 mplsOutSegmentIndex = o, 334 mplsOutSegmentIfIndex = i2, 335 mplsOutSegmentPushTopLabel = true(1), 336 mplsOutSegmentTopLabel = l2, 337 mplsOutSegmentMaxRate, 338 mplsOutSegmentMeanRate, 339 mplsOutSegmentMaxBurstSize, 340 mplsOutSegmentRowStatus = createAndGo(3) 341 } 343 Next, two cross-connect entries associating these two segments by 344 sharing the same mplsXCIndex are created. 346 In mplsXCTable, for the in-segment: 347 { 348 mplsXCIndex = x, 349 mplsInSegmentIfIndex = i1, 350 mplsInSegmentLabel = l1, 351 mplsOutSegmentIndex = 0, 352 mplsLabelStackIndex = 0, 353 mplsXCRowStatus = createAndGo(3) 354 } 356 In mplsXCTable, for the out-segment: 357 { 358 mplsXCIndex = x, 359 mplsInSegmentIfIndex = 0, 360 mplsInSegmentLabel = 0, 361 mplsOutSegmentIndex = o, 362 mplsXCLabelStackIndex = 0, 363 mplsXCRowStatus = createAndGo(3) 364 } 366 Note that the objects mplsInSegmentXCIndex and 367 mplsOutSegmentXCIndex will automatically get populated with the 368 value "x" when these segments are referred to from the 369 corresponding cross-connect entries. 371 Finally, the tunnel entry is created, which points to the 372 appropriate cross-connect entries. 374 In mplsTunnelTable: 375 { 376 mplsTunnelIndex, 377 mplsTunnelXCIndex = mplsXCIndex = x, 378 ... 379 mplsTunnelDirection = in-out(3), 380 mplsXCRowStatus = createAndGo(3) 381 } 383 8. MPLS Traffic Engineering MIB Definitions 385 MPLS-TE-MIB DEFINITIONS ::= BEGIN 387 IMPORTS 388 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 389 experimental, Integer32, Counter32, IpAddress 390 FROM SNMPv2-SMI 391 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 392 FROM SNMPv2-CONF 393 TEXTUAL-CONVENTION, TruthValue, RowStatus 394 FROM SNMPv2-TC 395 InterfaceIndex, InterfaceIndexOrZero 396 FROM IF-MIB 397 BitRate, BurstSize 398 FROM INTEGRATED-SERVICES-MIB; 400 mplsTeMIB MODULE-IDENTITY 401 LAST-UPDATED "9901111930Z" -- 11 January 1999 19:30:00 EST 402 ORGANIZATION "Lucent Technologies" 403 CONTACT-INFO 404 " Cheenu Srinivasan 405 Postal: Lucent Technologies 406 4F535, 101 Crawfords Corner Road 407 Holmdel, NJ 07733 408 Tel: +1 732 949 0709 409 Email: cheenu@lucent.com 411 Arun Viswanathan 412 Postal: Lucent Technologies 413 4D537, 101 Crawfords Corner Road 414 Holmdel, NJ 07733 415 Tel: +1 732 332 5163 416 Email: arunv@lucent.com" 417 DESCRIPTION 418 "Proposed MIB module for MPLS Traffic Engineering (TE) as 419 defined in: Extensions to RSVP for LSP Tunnels, Awduche et 420 al, Internet Draft , 421 Nov. 1998; Explicit Routing over LDP Specification, 422 Jamoussi et al, Internet Draft , Nov. 1998." 424 ::= { experimental 9877 } -- to be assigned 426 -- Textual Conventions. 428 MplsTeIANAAddrFamily ::= TEXTUAL-CONVENTION 429 STATUS current 430 DESCRIPTION 431 "An address family. Values are defined in RFC 1700 - Assigned 432 Numbers. All values may not be relevant in all contexts 433 when used in this MIB, but are included for completeness." 434 REFERENCE 435 "RFC 1700 - Assigned Numbers, Reynolds and Postel, Oct. 1994" 436 SYNTAX INTEGER { 437 other(0), 438 ipv4(1), 439 ipv6(2), 440 nsap(3), 441 hdlc(4), 442 bbn1822(5), 443 ieee802(6), 444 e163(7), 445 e164(8), 446 f69(9), 447 x121(10), 448 ipx(11), 449 appleTalk(12), 450 decnetIV(13), 451 banyanVines(14), 452 e164WithNsap(15) 453 } 455 -- An MPLS label. 456 MplsLabel ::= TEXTUAL-CONVENTION 457 STATUS current 458 DESCRIPTION 459 "Represents an MPLS label. Note that the contents of a 460 label field are interpreted in an interface-type specific 461 fashion. For example, the label carried in the MPLS shim 462 header is 20 bits wide and the top 12 bits must be zero. 463 The frame relay label can be either 10, 17 or 23 bits wide 464 depending on the size of the DLCI field size and the top 22, 465 15, or 9 bits must be zero, respectively. For an ATM 466 interface, the lowermost 16 bits 467 are interpreted as the VCI, the next 8 bits as the VPI 468 and the remaining bits must be zero. Also note the 469 permissible label values are also a function of the inter- 470 face type. For example, the value 3 has special semantics 471 in the control plane for an MPLS shim header label and is 472 not a valid label value in the datapath." 473 REFERENCE 474 "1. MPLS Label Stack Encoding, Rosen et al, 475 draft-ietf-mpls-label-encaps-03.txt, Sept. 1998 476 2. Use of Label Switching on Frame Relay Networks, Conta 477 et al, draft-ietf-mpls-fr-03.txt, Nov. 1998." 478 SYNTAX Integer32 480 MplsTunnelIndex ::= TEXTUAL-CONVENTION 481 STATUS current 482 DESCRIPTION 483 "Index into mplsTunnelTable." 484 SYNTAX INTEGER (0..65535) 486 MplsTunnelCookie ::= TEXTUAL-CONVENTION 487 STATUS current 488 DESCRIPTION 489 "A globally unique identifier that is assigned to each 490 ERLSP. This is assigned at the head end of the ERLSP and 491 can be used by all LSRs to identify this ERLSP. At the 492 head end this cookie is maintained in the tunnel table 493 as mplsTunnelLocalCookie. For signalled tunnels this 494 cookie is piggybacked by the signalling protocol to 495 the remote end where the cookie is stored in the 496 remote LSR's tunnel table as mplsTunnelRemoteCookie 497 for the tunnel. For creating bi-directional tunnels 498 the cookie is used to associate the two uni- 499 directional ERLSPs as belonging to the same tunnel. 501 It is recommended that the cookie value be assigned 502 by concatenating the head-end LSR's IP address with the 503 tunnel index. For IPv4 addresses this results in a 504 6-octet long cookie." 505 SYNTAX OCTET STRING (SIZE(6)) 507 Ipv6Address ::= TEXTUAL-CONVENTION 508 STATUS current 509 DESCRIPTION 510 "IPv6 address." 511 SYNTAX OCTET STRING (SIZE(16)) 513 -- Top level components of this MIB. 515 mplsTeObjects OBJECT IDENTIFIER ::= { mplsTeMIB 1 } -- tables, scalars 516 mplsTeNotifications OBJECT IDENTIFIER ::= { mplsTeMIB 2 } -- traps 517 mplsTeConformance OBJECT IDENTIFIER ::= { mplsTeMIB 3 } -- conformance 519 -- MPLS tunnel table. 521 mplsTunnelTable OBJECT-TYPE 522 SYNTAX SEQUENCE OF MplsTunnelEntry 523 MAX-ACCESS not-accessible 524 STATUS current 525 DESCRIPTION 526 " The mplsTunnelTable allows new MPLS tunnels to be created 527 between an LSR and a remote endpoint, and existing 528 tunnels to be reconfigured or removed. Note that only 529 point-to-point tunnel segments are supported, although 530 multipoint-to-point and point-to-multipoint connections 531 are supported by an LSR acting as a cross-connect. Each 532 MPLS tunnel can thus have one out-segment originating at 533 this LSR and/or one in-segment terminating at this LSR." 534 ::= { mplsTeObjects 1 } 536 mplsTunnelEntry OBJECT-TYPE 537 SYNTAX MplsTunnelEntry 538 MAX-ACCESS not-accessible 539 STATUS current 540 DESCRIPTION 541 "An entry in this table represents an MPLS tunnel. 542 An entry can be created by a network administrator 543 or by an SNMP agent as instructed by LDP or RSVP." 544 INDEX { mplsTunnelIndex } 545 ::= { mplsTunnelTable 1 } 547 MplsTunnelEntry ::= SEQUENCE { 548 mplsTunnelIndex MplsTunnelIndex, 549 mplsTunnelName DisplayString, 550 mplsTunnelDescr DisplayString, 551 mplsTunnelIsIf TruthValue, 552 mplsTunnelIfIndex InterfaceIndexOrZero, 553 mplsTunnelDirection INTEGER, 554 mplsTunnelXCIndex Integer32, 555 mplsTunnelSignallingProto INTEGER, 556 mplsTunnelLocalCookie MplsTunnelCookie, 557 mplsTunnelRemoteCookie MplsTunnelCookie, 558 mplsTunnelIsMergeable TruthValue, 559 mplsTunnelSetupPrio INTEGER, 560 mplsTunnelHoldingPrio INTEGER, 561 mplsTunnelInMaxRate BitRate, 562 mplsTunnelInMeanRate BitRate, 563 mplsTunnelInMaxBurstSize BurstSize, 564 mplsTunnelOutMaxRate BitRate, 565 mplsTunnelOutMeanRate BitRate, 566 mplsTunnelOutMaxBurstSize BurstSize, 567 mplsTunnelIsPinned TruthValue, 568 mplsTunnelIsPersistent TruthValue, 569 mplsTunnelAdminStatus INTEGER, 570 mplsTunnelOperStatus INTEGER, 571 mplsTunnelRowStatus RowStatus 572 } 574 mplsTunnelIndex OBJECT-TYPE 575 SYNTAX Integer32 576 MAX-ACCESS read-create 577 STATUS current 578 DESCRIPTION 579 "Uniquely identifies this row." 580 ::= { mplsTunnelEntry 1 } 582 mplsTunnelName OBJECT-TYPE 583 SYNTAX DisplayString 584 MAX-ACCESS read-create 585 STATUS current 586 DESCRIPTION 587 "The `canonical' name assigned to the tunnel that 588 can be used to refer to it on the `console' port. 589 If mplsTunnelIsIf is set to true ifName 590 of the interface corresponding to this tunnel 591 should have a value equal to mplsTunnelName. 592 Also see the description of ifName in RFC 2233." 593 REFERENCE 594 "RFC 2233 - The Interfaces Group MIB using SMIv2, 595 McCloghrie and Kastenholtz, Nov. 1997" 596 ::= { mplsTunnelEntry 2 } 598 mplsTunnelDescr OBJECT-TYPE 599 SYNTAX DisplayString 600 MAX-ACCESS read-create 601 STATUS current 602 DESCRIPTION 603 "A textual string containing information about the 604 tunnel. If there is no description this object 605 contains a zero length string." 606 ::= { mplsTunnelEntry 3 } 608 mplsTunnelIsIf OBJECT-TYPE 609 SYNTAX TruthValue 610 MAX-ACCESS read-create 611 STATUS current 612 DESCRIPTION 613 "Is this tunnel also an interface?" 614 DEFVAL { false } 615 ::= { mplsTunnelEntry 4 } 617 mplsTunnelIfIndex OBJECT-TYPE 618 SYNTAX InterfaceIndexOrZero 619 MAX-ACCESS read-only 620 STATUS current 621 DESCRIPTION 622 "If this tunnel is an interface then the LSR assigned ifIndex. 623 Otherwise this is set to zero." 624 DEFVAL { 0 } 625 ::= { mplsTunnelEntry 5 } 627 mplsTunnelDirection OBJECT-TYPE 628 SYNTAX INTEGER { in(1), out(2), in-out(3) } 629 MAX-ACCESS read-create 630 STATUS current 631 DESCRIPTION 632 "Whether this tunnel is unidirectional-incoming, unidirectional- 633 outgoing, or bidirectional." 634 ::= { mplsTunnelEntry 6 } 636 mplsTunnelXCIndex OBJECT-TYPE 637 SYNTAX Integer32 638 MAX-ACCESS read-create 639 STATUS current 640 DESCRIPTION 641 "Index into mplsXCTable identifying the segments that compose this 642 tunnel, their characteristics, relationship etc." 643 DEFVAL { 0 } 644 ::= { mplsTunnelEntry 7 } 646 mplsTunnelSignallingProto OBJECT-TYPE 647 SYNTAX INTEGER { none(1), ldp(2), rsvp(3) } 648 MAX-ACCESS read-create 649 STATUS current 650 DESCRIPTION 651 "The signalling protocol, if any, that set up this tunnel." 652 DEFVAL { none } 653 ::= { mplsTunnelEntry 8 } 655 mplsTunnelLocalCookie OBJECT-TYPE 656 SYNTAX MplsTunnelCookie 657 MAX-ACCESS read-only 658 STATUS current 659 DESCRIPTION 660 "The local cookie assigned to the outgoing direction of 661 this tunnel at this LSR." 662 ::= { mplsTunnelEntry 9 } 664 mplsTunnelRemoteCookie OBJECT-TYPE 665 SYNTAX MplsTunnelCookie 666 MAX-ACCESS read-only 667 STATUS current 668 DESCRIPTION 669 "The remote cookie assigned to the incoming direction of 670 tunnel by the remote (head-end) LSR." 671 ::= { mplsTunnelEntry 10 } 673 mplsTunnelIsMergeable OBJECT-TYPE 674 SYNTAX TruthValue 675 MAX-ACCESS read-create 676 STATUS current 677 DESCRIPTION 678 "Whether this tunnel can be merged at an LSR downstream with 679 another tunnel." 680 DEFVAL { true } 681 ::= { mplsTunnelEntry 11 } 683 mplsTunnelSetupPrio OBJECT-TYPE 684 SYNTAX INTEGER (0..7) 685 MAX-ACCESS read-create 686 STATUS current 687 DESCRIPTION 688 "The setup priority of this tunnel." 689 REFERENCE 690 "Extensions to RSVP for LSP Tunnels, Awduche et 691 al, Internet Draft , 692 Nov. 1998. Explicit Routing over LDP Specification, 693 Jamoussi et al, Internet Draft , Nov. 1998." 695 ::= { mplsTunnelEntry 12 } 697 mplsTunnelHoldingPrio OBJECT-TYPE 698 SYNTAX INTEGER (0..7) 699 MAX-ACCESS read-create 700 STATUS current 701 DESCRIPTION 702 "The holding priority for this tunnel." 703 REFERENCE 704 "Extensions to RSVP for LSP Tunnels, Awduche et 705 al, Internet Draft , 706 Nov. 1998; Explicit Routing over LDP Specification, 707 Jamoussi et al, Internet Draft , Nov. 1998." 709 ::= { mplsTunnelEntry 13 } 711 mplsTunnelInMaxRate OBJECT-TYPE 712 SYNTAX BitRate 713 UNITS "bits per second" 714 MAX-ACCESS read-create 715 STATUS current 716 DESCRIPTION 717 "The maximum incoming rate in bits/second. Note that setting 718 mplsTunnelInMaxRate, mplsTunnelInMeanRate, and 719 mplsTunnelInMaxBurstSize to 0 indicates best-effort 720 treatment. This object is copied to mplsInSegmentMaxRate 721 of the corresponding in-segment." 722 DEFVAL { 0 } 723 ::= { mplsTunnelEntry 14 } 725 mplsTunnelInMeanRate OBJECT-TYPE 726 SYNTAX BitRate 727 UNITS "bits per second" 728 MAX-ACCESS read-create 729 STATUS current 730 DESCRIPTION 731 "The mean incoming rate in bits/second. This object is copied 732 to mplsInSegmentMeanRate of the corresponding in-segment." 733 DEFVAL { 0 } 734 ::= { mplsTunnelEntry 15 } 736 mplsTunnelInMaxBurstSize OBJECT-TYPE 737 SYNTAX BurstSize 738 UNITS "bytes" 739 MAX-ACCESS read-create 740 STATUS current 741 DESCRIPTION 742 "The maximum burst size in bytes. This object is copied 743 to mplsInSegmentMaxBurstSize of the corresponding in-segment." 744 DEFVAL { 0 } 745 ::= { mplsTunnelEntry 16 } 747 mplsTunnelOutMaxRate OBJECT-TYPE 748 SYNTAX BitRate 749 UNITS "bits per second" 750 MAX-ACCESS read-create 751 STATUS current 752 DESCRIPTION 753 "The maximum outgoing rate in bits/second. Note that setting 754 mplsTunnelOutMaxRate, mplsTunnelOutMeanRate, and 755 mplsTunnelOutMaxBurstSize to 0 indicates best-effort 756 treatment. This object is copied to mplsOutSegmentMaxRate 757 of the corresponding out-segment." 758 DEFVAL { 0 } 759 ::= { mplsTunnelEntry 17 } 761 mplsTunnelOutMeanRate OBJECT-TYPE 762 SYNTAX BitRate 763 UNITS "bits per second" 764 MAX-ACCESS read-create 765 STATUS current 766 DESCRIPTION 767 "The mean outgoing rate in bits/second. This object is copied 768 to mplsOutSegmentMeanRate of the corresponding out-segment." 769 DEFVAL { 0 } 770 ::= { mplsTunnelEntry 18 } 772 mplsTunnelOutMaxBurstSize OBJECT-TYPE 773 SYNTAX BurstSize 774 UNITS "bytes" 775 MAX-ACCESS read-create 776 STATUS current 777 DESCRIPTION 778 "The maximum burst size in bytes. This object is copied 779 to mplsOutSegmentMaxBurstSize of the corresponding out-segment." 780 DEFVAL { 0 } 781 ::= { mplsTunnelEntry 19 } 783 mplsTunnelIsPinned OBJECT-TYPE 784 SYNTAX TruthValue 785 MAX-ACCESS read-create 786 STATUS current 787 DESCRIPTION 788 "Indicates whether the loose-routed hops of this tunnel 789 are to be pinned." 790 DEFVAL { false } 791 ::= { mplsTunnelEntry 20 } 793 mplsTunnelIsPersistent OBJECT-TYPE 794 SYNTAX TruthValue 795 MAX-ACCESS read-create 796 STATUS current 797 DESCRIPTION 798 "Indicates whether this tunnel should be restored automatically 799 after failures." 800 DEFVAL { true } 801 ::= { mplsTunnelEntry 21 } 803 mplsTunnelAdminStatus OBJECT-TYPE 804 SYNTAX INTEGER { 805 up(1), -- ready to pass packets 806 down(2), 807 testing(3) -- in some test mode 808 } 809 MAX-ACCESS read-create 810 STATUS current 811 DESCRIPTION 812 "Desired status of this tunnel." 813 ::= { mplsTunnelEntry 22 } 815 mplsTunnelOperStatus OBJECT-TYPE 816 SYNTAX INTEGER { 817 up(1), -- ready to pass packets 818 down(2), 819 testing(3), -- in some test mode 820 unknown(4), -- status cannot be determined for 821 -- some reason 822 dormant(5), 823 notPresent(6), -- some component is missing 824 lowerLayerNotPresent(7) 825 -- down due to the state of 826 -- lower layer interfaces 827 } 828 MAX-ACCESS read-only 829 STATUS current 830 DESCRIPTION 831 "The operational status of this tunnel, typically a function of 832 the state of individual segments of this tunnel, among other 833 things." 834 ::= { mplsTunnelEntry 23 } 836 mplsTunnelRowStatus OBJECT-TYPE 837 SYNTAX RowStatus 838 MAX-ACCESS read-create 839 STATUS current 840 DESCRIPTION 841 "For controlling the state of this row." 842 ::= { mplsTunnelEntry 24 } 844 -- End of mplsTunnelTable 846 -- Maximum number of tunnel hops supported. 848 mplsTunnelMaxHops OBJECT-TYPE 849 SYNTAX RowStatus 850 MAX-ACCESS read-only 851 STATUS current 852 DESCRIPTION 853 "The maximum number of hops that can be specified for a tunnel 854 on this device." 855 ::= { mplsTeObjects 2 } 857 -- Tunnel hop table. 859 mplsTunnelHopTable OBJECT-TYPE 860 SYNTAX SEQUENCE OF MplsTunnelEntry 861 MAX-ACCESS not-accessible 862 STATUS current 863 DESCRIPTION 864 "The mplsTunnelHopTable is used to indicate the hops, strict 865 or loose, for an MPLS tunnel defined in mplsTunnelTable, 866 when it is established via signalling, for the outgoing 867 direction of the tunnel. Each row in this table 868 is indexed primarily by the same index, mplsTunnelIndex, as 869 the row of the corresponding tunnel in mplsTunnelTable. Each 870 row also has a secondary index mplsTunnelHopIndex 871 corresponding to the next hop that this row corresponds to. 872 The first row in the table is the first hop after the 873 origination point of the tunnel. In case we want to specify 874 a particular interface on the originating LSR of an outgoing 875 tunnel by which we want packets to exit the LSR, we specify 876 this as the first hop for this tunnel in mplsTunnelHopTable." 877 ::= { mplsTeObjects 3 } 879 mplsTunnelHopEntry OBJECT-TYPE 880 SYNTAX MplsTunnelHopEntry 881 MAX-ACCESS not-accessible 882 STATUS current 883 DESCRIPTION 884 "An entry in this table represents a tunnel hop. 885 An entry is created by a network administrator 886 for signalled ERLSP set up by LDP or RSVP." 887 INDEX { mplsTunnelIndex, mplsTunnelHopIndex } 888 ::= { mplsTunnelHopTable 1 } 890 MplsTunnelHopEntry ::= SEQUENCE { 891 mplsTunnelHopIndex Integer32, 892 mplsTunnelHopAddrType INTEGER, 893 mplsTunnelHopIpv4Addr IpAddress, 894 mplsTunnelHopIpv4PrefixLen INTEGER, 895 mplsTunnelHopIpv6Addr Ipv6Address, 896 mplsTunnelHopIpv6PrefixLen INTEGER, 897 mplsTunnelHopAsNumber INTEGER, 898 mplsTunnelHopStrictOrLoose INTEGER, 899 mplsTunnelHopRowStatus RowStatus 900 } 902 mplsTunnelHopIndex OBJECT-TYPE 903 SYNTAX Integer32 904 MAX-ACCESS not-accessible 905 STATUS current 906 DESCRIPTION 907 "Secondary index into this table identifying the particular 908 hop." 909 ::= { mplsTunnelHopEntry 1 } 911 mplsTunnelHopAddrType OBJECT-TYPE 912 SYNTAX INTEGER { ipV4(1), ipV6(2), asNumber(3) } 913 MAX-ACCESS read-create 914 STATUS current 915 DESCRIPTION 916 "Address type of this hop." 917 DEFVAL { ipV4 } 918 ::= { mplsTunnelHopEntry 2 } 920 mplsTunnelHopIpv4Addr OBJECT-TYPE 921 SYNTAX IpAddress 922 MAX-ACCESS read-create 923 STATUS current 924 DESCRIPTION 925 "If mplsTunnelHopAddrType is ipV4(1), IPv4 address of this hop. 926 This object is not significant otherwise and should return a 927 value of 0." 928 ::= { mplsTunnelHopEntry 3 } 930 mplsTunnelHopIpv4PrefixLen OBJECT-TYPE 931 SYNTAX INTEGER (0..31) 932 MAX-ACCESS read-create 933 STATUS current 934 DESCRIPTION 935 "If mplsTunnelHopAddrType is ipV4(1), prefix length for this hop's 936 IPv4 address. This object is not significant otherwise and should 937 return a value of 0." 938 ::= { mplsTunnelHopEntry 4 } 940 mplsTunnelHopIpv6Addr OBJECT-TYPE 941 SYNTAX Ipv6Address 942 MAX-ACCESS read-create 943 STATUS current 944 DESCRIPTION 945 "If mplsTunnelHopAddrType is ipV6(2), the IPv6 address of this hop. 946 This object is not significant otherwise and should return a 947 value of 0." 948 ::= { mplsTunnelHopEntry 5 } 950 mplsTunnelHopIpv6PrefixLen OBJECT-TYPE 951 SYNTAX INTEGER (0..127) 952 MAX-ACCESS read-create 953 STATUS current 954 DESCRIPTION 955 "If mplsTunnelHopAddrType is ipV6(2), prefix length for this 956 hop's IPv6 address. This object is not significant otherwise and 957 should return a value of 0." 958 ::= { mplsTunnelHopEntry 6 } 960 mplsTunnelHopAsNumber OBJECT-TYPE 961 SYNTAX INTEGER (0..65535) 962 MAX-ACCESS read-create 963 STATUS current 964 DESCRIPTION 965 "If mplsTunnelHopAddrType is asNumber(3), the AS number this 966 hop. This object is not significant otherwise and should 967 return a value of 0." 968 ::= { mplsTunnelHopEntry 7 } 970 mplsTunnelHopStrictOrLoose OBJECT-TYPE 971 SYNTAX INTEGER { strict(1), loose(2) } 972 MAX-ACCESS read-create 973 STATUS current 974 DESCRIPTION 975 "Whether this is a strict or loose hop." 976 ::= { mplsTunnelHopEntry 8 } 978 mplsTunnelHopRowStatus OBJECT-TYPE 979 SYNTAX RowStatus 980 MAX-ACCESS read-create 981 STATUS current 982 DESCRIPTION 983 "For creating, modifying and deleting this row." 984 ::= { mplsTunnelHopEntry 9 } 986 -- End of mplsTunnelHopTable 988 -- In-segment table. 990 mplsInSegmentTable OBJECT-TYPE 991 SYNTAX SEQUENCE OF MplsInSegmentEntry 992 MAX-ACCESS not-accessible 993 STATUS current 994 DESCRIPTION 995 "This table contains a description of the incoming segments 996 to a LSR." 997 ::= { mplsTeObjects 4 } 999 mplsInSegmentEntry OBJECT-TYPE 1000 SYNTAX MplsInSegmentEntry 1001 MAX-ACCESS not-accessible 1002 STATUS current 1003 DESCRIPTION 1004 "An entry in this table represents one incoming segment. 1005 An entry can be created by a network administrator 1006 or by an SNMP agent as instructed by LDP or RSVP. It is 1007 indexed by the incoming interface index and (top) 1008 label. Note that some of the segments are associated 1009 with a tunnel, the traffic parameters of these rows are 1010 supported as read-only objects and their modification 1011 can be done only via the tunnel table." 1013 INDEX { mplsInSegmentIfIndex, mplsInSegmentLabel } 1014 ::= { mplsInSegmentTable 1 } 1016 MplsInSegmentEntry ::= SEQUENCE { 1017 mplsInSegmentIfIndex InterfaceIndex, 1018 mplsInSegmentLabel MplsLabel, 1019 mplsInSegmentNPop Integer32, 1020 mplsInSegmentAddrFamily MplsTeIANAAddrFamily, 1021 mplsInSegmentXCIndex Integer32, 1022 mplsInSegmentMaxRate BitRate, 1023 mplsInSegmentMeanRate BitRate, 1024 mplsInSegmentMaxBurstSize BurstSize, 1025 mplsInSegmentAdminStatus INTEGER, 1026 mplsInSegmentOperStatus INTEGER, 1027 mplsInSegmentRowStatus RowStatus 1028 } 1030 mplsInSegmentIfIndex OBJECT-TYPE 1031 SYNTAX InterfaceIndexOrZero 1032 MAX-ACCESS read-create 1033 STATUS current 1034 DESCRIPTION 1035 "Incoming interface index. While the value 0 is not 1036 valid as an index for this row, it can be supplied 1037 as a valid index for mplsXCTable to refer to entries 1038 for which no in-segment has been configured." 1039 ::= { mplsInSegmentEntry 1 } 1041 mplsInSegmentLabel OBJECT-TYPE 1042 SYNTAX MplsLabel 1043 MAX-ACCESS not-accessible 1044 STATUS current 1045 DESCRIPTION 1046 "The incoming label." 1047 ::= { mplsInSegmentEntry 2 } 1049 mplsInSegmentNPop OBJECT-TYPE 1050 SYNTAX Integer32 1051 MAX-ACCESS read-create 1052 STATUS current 1053 DESCRIPTION 1054 "The number of labels to pop from the incoming packet. 1055 Normally only the top label is popped (based on which 1056 all switching decisions are taken)." 1057 DEFVAL { 1 } 1058 ::= { mplsInSegmentEntry 3 } 1060 mplsInSegmentAddrFamily OBJECT-TYPE 1061 SYNTAX MplsTeIANAAddrFamily 1062 MAX-ACCESS read-create 1063 STATUS current 1064 DESCRIPTION 1065 "The IANA address family of the incoming packet. A value of 1066 zero indicates that the family type is either unknown or 1067 undefined (which could happen for example when streams of 1068 different types are merged in a multipoint-to-point conn- 1069 ection)." 1070 REFERENCE 1071 "RFC 1700 - Assigned Numbers, Reynolds and Postel, October 1994." 1072 DEFVAL { 0 } 1073 ::= { mplsInSegmentEntry 4 } 1075 mplsInSegmentXCIndex OBJECT-TYPE 1076 SYNTAX Integer32 1077 MAX-ACCESS read-only 1078 STATUS current 1079 DESCRIPTION 1080 "Index into mplsXCTable to identify which cross-connect entry 1081 this segment is part of. A value of zero indicates that it 1082 is not being referred to by any cross-connect entry." 1083 DEFVAL { 0 } 1084 ::= { mplsInSegmentEntry 5 } 1086 mplsInSegmentMaxRate OBJECT-TYPE 1087 SYNTAX BitRate 1088 UNITS "bits per second" 1089 MAX-ACCESS read-create 1090 STATUS current 1091 DESCRIPTION 1092 "The maximum incoming rate in bits/second. Note that setting 1093 mplsInSegmentMaxRate, mplsInSegmentMeanRate, and 1094 mplsInSegmentMaxBurstSize to 0 indicates best-effort 1095 treatment." 1096 DEFVAL { 0 } 1097 ::= { mplsInSegmentEntry 6 } 1099 mplsInSegmentMeanRate OBJECT-TYPE 1100 SYNTAX BitRate 1101 UNITS "bits per second" 1102 MAX-ACCESS read-create 1103 STATUS current 1104 DESCRIPTION 1105 "The mean incoming rate in bits/second." 1106 DEFVAL { 0 } 1107 ::= { mplsInSegmentEntry 7 } 1109 mplsInSegmentMaxBurstSize OBJECT-TYPE 1110 SYNTAX BurstSize 1111 UNITS "bytes" 1112 MAX-ACCESS read-create 1113 STATUS current 1114 DESCRIPTION 1115 "The maximum burst size in bytes." 1116 DEFVAL { 0 } 1117 ::= { mplsInSegmentEntry 8 } 1119 mplsInSegmentAdminStatus OBJECT-TYPE 1120 SYNTAX INTEGER { 1121 up(1), -- ready to pass packets 1122 down(2), 1123 testing(3) -- in some test mode 1124 } 1125 MAX-ACCESS read-create 1126 STATUS current 1127 DESCRIPTION 1128 "Desired status of this segment." 1129 ::= { mplsInSegmentEntry 9 } 1131 mplsInSegmentOperStatus OBJECT-TYPE 1132 SYNTAX INTEGER { 1133 up(1), -- ready to pass packets 1134 down(2), 1135 testing(3), -- in some test mode 1136 unknown(4), -- status cannot be determined for 1137 -- some reason 1138 dormant(5), 1139 notPresent(6), -- some component is missing 1140 lowerLayerNotPresent(7) 1141 -- down due to the state of 1142 -- lower layer interfaces 1143 } 1144 MAX-ACCESS read-only 1145 STATUS current 1146 DESCRIPTION 1147 "The operational status of this segment." 1148 ::= { mplsInSegmentEntry 10 } 1150 mplsInSegmentRowStatus OBJECT-TYPE 1151 SYNTAX RowStatus 1152 MAX-ACCESS read-create 1153 STATUS current 1154 DESCRIPTION 1155 "For creating, modifying, and deleting this row." 1156 ::= { mplsInSegmentEntry 11 } 1158 -- End of mplsInSegmentTable 1160 -- In-segment performance table. 1162 mplsInSegmentPerfTable OBJECT-TYPE 1163 SYNTAX SEQUENCE OF MplsInSegmentPerfEntry 1164 MAX-ACCESS not-accessible 1165 STATUS current 1166 DESCRIPTION 1167 "This table contains statistical information about incoming 1168 MPLS segments to an LSR." 1169 ::= { mplsTeObjects 5 } 1171 mplsInSegmentPerfEntry OBJECT-TYPE 1172 SYNTAX MplsInSegmentPerfEntry 1173 MAX-ACCESS not-accessible 1174 STATUS current 1175 DESCRIPTION 1176 "An entry in this table contains statistical information 1177 about one incoming segment configured in mplsInSegmentTable." 1178 AUGMENTS { mplsInSegmentEntry } 1179 ::= { mplsInSegmentPerfTable 1 } 1181 MplsInSegmentPerfEntry ::= SEQUENCE { 1182 mplsInSegmentOctets Counter32, 1183 mplsInSegmentPackets Counter32, 1184 mplsInSegmentErrors Counter32, 1185 mplsInSegmentDiscards Counter32 1186 } 1188 mplsInSegmentOctets OBJECT-TYPE 1189 SYNTAX Counter32 1190 MAX-ACCESS read-only 1191 STATUS current 1192 DESCRIPTION 1193 "Total number of octets received." 1194 ::= { mplsInSegmentPerfEntry 1 } 1196 mplsInSegmentPackets OBJECT-TYPE 1197 SYNTAX Counter32 1198 MAX-ACCESS read-only 1199 STATUS current 1200 DESCRIPTION 1201 "Total number of packets received." 1202 ::= { mplsInSegmentPerfEntry 2 } 1204 mplsInSegmentErrors OBJECT-TYPE 1205 SYNTAX Counter32 1206 MAX-ACCESS read-only 1207 STATUS current 1208 DESCRIPTION 1209 "Number of errored packets received." 1210 ::= { mplsInSegmentPerfEntry 3 } 1212 mplsInSegmentDiscards OBJECT-TYPE 1213 SYNTAX Counter32 1214 MAX-ACCESS read-only 1215 STATUS current 1216 DESCRIPTION 1217 "Number of packets received that had to be dropped either 1218 because of errors or for other reasons such as buffer 1219 overflows." 1220 ::= { mplsInSegmentPerfEntry 4 } 1222 -- End of mplsInSegmentPerfTable. 1224 -- Out-segment table. 1226 mplsOutSegmentTable OBJECT-TYPE 1227 SYNTAX SEQUENCE OF MplsOutSegmentEntry 1228 MAX-ACCESS not-accessible 1229 STATUS current 1230 DESCRIPTION 1231 "This table contains a description of the outgoing segments 1232 from an LSR." 1233 ::= { mplsTeObjects 6 } 1235 mplsOutSegmentEntry OBJECT-TYPE 1236 SYNTAX MplsOutSegmentEntry 1237 MAX-ACCESS not-accessible 1238 STATUS current 1239 DESCRIPTION 1240 "An entry in this table represents one outgoing segment. 1241 An entry can be created by a network administrator 1242 or by an SNMP agent as instructed by LDP or RSVP. 1243 Note that some of the segments are associated 1244 with a tunnel, the traffic parameters of these rows are 1245 supported as read-only objects and their modification 1246 can be done only via the tunnel table." 1247 INDEX { mplsOutSegmentIndex } 1248 ::= { mplsOutSegmentTable 1 } 1250 MplsOutSegmentEntry ::= SEQUENCE { 1251 mplsOutSegmentIndex Integer32, 1252 mplsOutSegmentIfIndex InterfaceIndex, 1253 mplsOutSegmentPushTopLabel TruthValue, 1254 mplsOutSegmentTopLabel MplsLabel, 1255 mplsOutSegmentNextHopIpAddrType INTEGER, 1256 mplsOutSegmentNextHopIpv4Addr IpAddress, 1257 mplsOutSegmentNextHopIpv6Addr Ipv6Address, 1258 mplsOutSegmentXCIndex Integer32, 1259 mplsOutSegmentMaxRate BitRate, 1260 mplsOutSegmentMeanRate BitRate, 1261 mplsOutSegmentMaxBurstSize BurstSize, 1262 mplsOutSegmentAdminStatus INTEGER, 1263 mplsOutSegmentOperStatus INTEGER, 1264 mplsOutSegmentRowStatus RowStatus 1265 } 1267 mplsOutSegmentIndex OBJECT-TYPE 1268 SYNTAX Integer32 1269 MAX-ACCESS not-accessible 1270 STATUS current 1271 DESCRIPTION 1272 "Unique index for this row. While a value of 0 is not 1273 valid as an index for this row it can be supplied 1274 as a valid value to index mplsXCTable to access entries 1275 for which no out-segment has been configured." 1276 ::= { mplsOutSegmentEntry 1 } 1278 mplsOutSegmentIfIndex OBJECT-TYPE 1279 SYNTAX InterfaceIndex 1280 MAX-ACCESS read-create 1281 STATUS current 1282 DESCRIPTION 1283 "Interface index of the outgoing interface." 1284 ::= { mplsOutSegmentEntry 2 } 1286 mplsOutSegmentPushTopLabel OBJECT-TYPE 1287 SYNTAX TruthValue 1288 MAX-ACCESS read-create 1289 STATUS current 1290 DESCRIPTION 1291 "Whether a top label should be pushed onto the outgoing 1292 packet's label stack. Its value has to be true if 1293 the outgoing interface is ATM (which does not support 1294 `pop-and-go') or if it is a tunnel origination. Note 1295 also that the case where mplsOutSegmentPushTopLabel is 1296 set to false but the cross-connect entry that refers 1297 to this out-segment has a non-zero mplsLabelStackIndex 1298 is an error which the LSR should ensure doesn't happen." 1299 ::= { mplsOutSegmentEntry 3 } 1301 mplsOutSegmentTopLabel OBJECT-TYPE 1302 SYNTAX MplsLabel 1303 MAX-ACCESS read-create 1304 STATUS current 1305 DESCRIPTION 1306 "If mplsOutSegmentPushTopLabel is true then this is the 1307 label that should be pushed onto the outgoing packet's 1308 label stack. Note that the contents of the label field 1309 can be interpreted in an outgoing interface specific fashion. 1310 For example, the label carried in the MPLS shim header is 1311 20 bits wide and the top 12 bits must be zero. The 1312 Frame Relay label is 24 bits wide and the top 8 bits 1313 must be zero. For ATM interfaces the lowermost 16 bits 1314 are interpreted as the VCI, the next 8 bits as the 1315 VPI and the remaining bits must be zero." 1316 ::= { mplsOutSegmentEntry 4 } 1318 mplsOutSegmentNextHopIpAddrType OBJECT-TYPE 1319 SYNTAX INTEGER { none (1), ipV4 (2), ipV6 (3) } 1320 MAX-ACCESS read-create 1321 STATUS current 1322 DESCRIPTION 1323 "Whether the next hop address is IPv4 or IPv6. A value 1324 of none (1) is valid (only) when the outgoing interface 1325 is of type point-to-point." 1326 DEFVAL { none } 1327 ::= { mplsOutSegmentEntry 5 } 1329 mplsOutSegmentNextHopIpv4Addr OBJECT-TYPE 1330 SYNTAX IpAddress 1331 MAX-ACCESS read-create 1332 STATUS current 1333 DESCRIPTION 1334 "IPv4 Address of the next hop. Its value is significant only 1335 when mplsOutSegmentNextHopIpAddrType is ipV4 (2), otherwise 1336 it should return a value of 0." 1337 ::= { mplsOutSegmentEntry 6 } 1339 mplsOutSegmentNextHopIpv6Addr OBJECT-TYPE 1340 SYNTAX Ipv6Address 1341 MAX-ACCESS read-create 1342 STATUS current 1343 DESCRIPTION 1344 "IPv6 address of the next hop. Its value is significant only 1345 when mplsOutSegmentNextHopIpAddrType is ipV6 (3), otherwise 1346 it should return a value of 0." 1347 ::= { mplsOutSegmentEntry 7 } 1349 mplsOutSegmentXCIndex OBJECT-TYPE 1350 SYNTAX Integer32 1351 MAX-ACCESS read-create 1352 STATUS current 1353 DESCRIPTION 1354 "Index into mplsXCTable to identify which cross-connect entry 1355 this segment is part of. A value of zero indicates that it 1356 is not being referred to by any cross-connect entry." 1357 DEFVAL { 0 } 1358 ::= { mplsOutSegmentEntry 8 } 1360 mplsOutSegmentMaxRate OBJECT-TYPE 1361 SYNTAX BitRate 1362 UNITS "bits per second" 1363 MAX-ACCESS read-create 1364 STATUS current 1365 DESCRIPTION 1366 "Maximum outgoing rate in bits/second. Note that setting 1367 mplsOutSegmentMaxRate, mplsOutSegmentMeanRate, and 1368 mplsOutSegmentMaxBurstSize to 0 indicates best-effort 1369 treatment." 1370 DEFVAL { 0 } 1371 ::= { mplsOutSegmentEntry 9 } 1373 mplsOutSegmentMeanRate OBJECT-TYPE 1374 SYNTAX BitRate 1375 UNITS "bits per second" 1376 MAX-ACCESS read-create 1377 STATUS current 1378 DESCRIPTION 1379 "Mean outgoing rate in bits/second." 1380 DEFVAL { 0 } 1381 ::= { mplsOutSegmentEntry 10 } 1383 mplsOutSegmentMaxBurstSize OBJECT-TYPE 1384 SYNTAX BurstSize 1385 UNITS "bytes" 1386 MAX-ACCESS read-create 1387 STATUS current 1388 DESCRIPTION 1389 "Maximum burst size in bytes." 1390 DEFVAL { 0 } 1391 ::= { mplsOutSegmentEntry 11 } 1393 mplsOutSegmentAdminStatus OBJECT-TYPE 1394 SYNTAX INTEGER { 1395 up(1), -- ready to pass packets 1396 down(2), 1397 testing(3) -- in some test mode 1398 } 1399 MAX-ACCESS read-create 1400 STATUS current 1401 DESCRIPTION 1402 "Desired status of this segment." 1403 ::= { mplsOutSegmentEntry 12 } 1405 mplsOutSegmentOperStatus OBJECT-TYPE 1406 SYNTAX INTEGER { 1407 up(1), -- ready to pass packets 1408 down(2), 1409 testing(3), -- in some test mode 1410 unknown(4), -- status cannot be determined for 1411 -- some reason 1412 dormant(5), 1413 notPresent(6), -- some component is missing 1414 lowerLayerNotPresent(7) 1415 -- down due to the state of 1416 -- lower layer interfaces 1417 } 1418 MAX-ACCESS read-only 1419 STATUS current 1420 DESCRIPTION 1421 "The operational status of this segment." 1422 ::= { mplsOutSegmentEntry 13 } 1424 mplsOutSegmentRowStatus OBJECT-TYPE 1425 SYNTAX RowStatus 1426 MAX-ACCESS read-create 1427 STATUS current 1428 DESCRIPTION 1429 "For creating, modifying, and deleting this row." 1430 ::= { mplsOutSegmentEntry 14 } 1432 -- End of mplsOutSegmentTable 1434 -- Out-segment performance table. 1436 mplsOutSegmentPerfTable OBJECT-TYPE 1437 SYNTAX SEQUENCE OF MplsOutSegmentPerfEntry 1438 MAX-ACCESS not-accessible 1439 STATUS current 1440 DESCRIPTION 1441 "This table contains statistical information about incoming 1442 segments to an LSR." 1443 ::= { mplsTeObjects 7 } 1445 mplsOutSegmentPerfEntry OBJECT-TYPE 1446 SYNTAX MplsOutSegmentPerfEntry 1447 MAX-ACCESS not-accessible 1448 STATUS current 1449 DESCRIPTION 1450 "An entry in this table contains statistical information 1451 about one incoming segment configured in mplsOutSegmentTable." 1452 AUGMENTS { mplsOutSegmentEntry } 1453 ::= { mplsOutSegmentPerfTable 1 } 1455 MplsOutSegmentPerfEntry ::= SEQUENCE { 1456 mplsOutSegmentOctets Counter32, 1457 mplsOutSegmentPackets Counter32, 1458 mplsOutSegmentErrors Counter32, 1459 mplsOutSegmentDiscards Counter32 1460 } 1462 mplsOutSegmentOctets OBJECT-TYPE 1463 SYNTAX Counter32 1464 MAX-ACCESS read-only 1465 STATUS current 1466 DESCRIPTION 1467 "Total number of octets sent." 1468 ::= { mplsOutSegmentPerfEntry 1 } 1470 mplsOutSegmentPackets OBJECT-TYPE 1471 SYNTAX Counter32 1472 MAX-ACCESS read-only 1473 STATUS current 1474 DESCRIPTION 1475 "Total number of packets sent." 1476 ::= { mplsOutSegmentPerfEntry 2 } 1478 mplsOutSegmentErrors OBJECT-TYPE 1479 SYNTAX Counter32 1480 MAX-ACCESS read-only 1481 STATUS current 1482 DESCRIPTION 1483 "Number of errored packets sent." 1484 ::= { mplsOutSegmentPerfEntry 3 } 1486 mplsOutSegmentDiscards OBJECT-TYPE 1487 SYNTAX Counter32 1488 MAX-ACCESS read-only 1489 STATUS current 1490 DESCRIPTION 1491 "Number of packets sent that had to be dropped either 1492 because of errors or for other reasons such as buffer 1493 overflows." 1494 ::= { mplsOutSegmentPerfEntry 4 } 1496 -- End of mplsOutSegmentPerfTable. 1498 -- Cross-connect table. 1500 mplsXCTable OBJECT-TYPE 1501 SYNTAX SEQUENCE OF MplsXCEntry 1502 MAX-ACCESS not-accessible 1503 STATUS current 1504 DESCRIPTION 1505 "This table specifies information for switching between 1506 MPLS tunnels segments. It supports point-to-point, 1507 point-to-multipoint (multicast) and multipoint-to-point 1508 connections. mplsLabelStackTable specifies the label 1509 stack information for a cross-connect LSR and is 1510 referred to from mplsXCTable." 1511 ::= { mplsTeObjects 8 } 1513 mplsXCEntry OBJECT-TYPE 1514 SYNTAX MplsXCEntry 1515 MAX-ACCESS not-accessible 1516 STATUS current 1517 DESCRIPTION 1518 "A row in this table represents one cross-connect entry. 1519 It is indexed by the following objects: 1520 - cross-connect index that uniquely identifies 1521 a group of cross-connect entries 1522 - interface index of the in-segment 1523 - incoming label(s) 1524 - out-segment index 1525 An entry can be created by a network administrator 1526 or by an SNMP agent as instructed by LDP or RSVP." 1527 INDEX { mplsXCIndex, mplsInSegmentIfIndex, 1528 mplsInSegmentLabel, mplsOutSegmentIndex } 1529 ::= { mplsXCTable 1 } 1531 MplsXCEntry ::= SEQUENCE { 1532 mplsXCIndex Integer32, 1533 mplsXCLabelStackIndex Integer32, 1534 mplsXCCOS Integer32, 1535 mplsXCIsPersistent TruthValue, 1536 mplsXCAdminStatus INTEGER, 1537 mplsXCOperStatus INTEGER, 1538 mplsXCRowStatus RowStatus 1539 } 1541 mplsXCIndex OBJECT-TYPE 1542 SYNTAX Integer32 1543 MAX-ACCESS not-accessible 1544 STATUS current 1545 DESCRIPTION 1546 "Primary index for the row indentifying a group of 1547 cross-connect segments." 1548 ::= { mplsXCEntry 1 } 1550 mplsXCLabelStackIndex OBJECT-TYPE 1551 SYNTAX Integer32 1552 MAX-ACCESS read-create 1553 STATUS current 1554 DESCRIPTION 1555 "Primary index into mplsLabelStackTable identifying 1556 a stack of labels to be pushed beneath the top 1557 label. Note that the top label is identified in the 1558 out-segment which ensures that all the components of 1559 a multipoint-to-point connection have the same 1560 outgoing label. A value of 0 indicates that no labels 1561 are to be stacked beneath the top label." 1562 ::= { mplsXCEntry 2 } 1564 mplsXCCOS OBJECT-TYPE 1565 SYNTAX Integer32 1566 MAX-ACCESS read-create 1567 STATUS current 1568 DESCRIPTION 1569 "Value to override the incoming COS field with for a 1570 cross-connect or the value to assign to outgoing 1571 packets for an outgoing segment of a tunnel." 1572 ::= { mplsXCEntry 3 } 1574 mplsXCIsPersistent OBJECT-TYPE 1575 SYNTAX TruthValue 1576 MAX-ACCESS read-create 1577 STATUS current 1578 DESCRIPTION 1579 "Whether this cross-connect entry and associated in- 1580 and out-segments should be restored automatically 1581 after failures." 1582 DEFVAL { false } 1583 ::= { mplsXCEntry 4 } 1585 mplsXCAdminStatus OBJECT-TYPE 1586 SYNTAX INTEGER { 1587 up(1), -- ready to pass packets 1588 down(2), 1589 testing(3) -- in some test mode 1590 } 1591 MAX-ACCESS read-create 1592 STATUS current 1593 DESCRIPTION 1594 "Desired status of this segment." 1595 ::= { mplsXCEntry 5 } 1597 mplsXCOperStatus OBJECT-TYPE 1598 SYNTAX INTEGER { 1599 up(1), -- ready to pass packets 1600 down(2), 1601 testing(3), -- in some test mode 1602 unknown(4), -- status cannot be determined for 1603 -- some reason 1604 dormant(5), 1605 notPresent(6), -- some component is missing 1606 lowerLayerNotPresent(7) 1607 -- down due to the state of 1608 -- lower layer interfaces 1609 } 1610 MAX-ACCESS read-only 1611 STATUS current 1612 DESCRIPTION 1613 "The operational status of this segment." 1614 ::= { mplsXCEntry 6 } 1616 mplsXCRowStatus OBJECT-TYPE 1617 SYNTAX RowStatus 1618 MAX-ACCESS read-create 1619 STATUS current 1620 DESCRIPTION 1621 "For creating, modifying, and deleting this row." 1622 ::= { mplsXCEntry 7 } 1624 -- End of mplsXCTable 1626 -- Label stack table. 1628 mplsLabelStackTable OBJECT-TYPE 1629 SYNTAX SEQUENCE OF MplsLabelStackEntry 1630 MAX-ACCESS not-accessible 1631 STATUS current 1632 DESCRIPTION 1633 "This table specifies the label stack to be pushed onto 1634 a packet, beneath the top label. Entries into this 1635 table are referred to from mplsXCTable." 1636 ::= { mplsTeObjects 9 } 1638 mplsLabelStackEntry OBJECT-TYPE 1639 SYNTAX MplsLabelStackEntry 1640 MAX-ACCESS not-accessible 1641 STATUS current 1642 DESCRIPTION 1643 "An entry in this table represents one label to be 1644 pushed onto an outgoing packets beneath the top label. 1645 An entry can be created by a network administrator 1646 or by an SNMP agent as instructed by LDP or RSVP." 1647 INDEX { mplsLabelStackIndex } 1648 ::= { mplsLabelStackTable 1 } 1650 MplsLabelStackEntry ::= SEQUENCE { 1651 mplsLabelStackIndex Integer32, 1652 mplsLabelStackLabelIndex Integer32, 1653 mplsLabelStackLabel MplsLabel, 1654 mplsLabelStackRowStatus RowStatus 1655 } 1657 mplsLabelStackIndex OBJECT-TYPE 1658 SYNTAX Integer32 1659 MAX-ACCESS not-accessible 1660 STATUS current 1661 DESCRIPTION 1662 "Primary index for this row identifying a stack of labels 1663 to be pushed on an outgoing packet beneath the top label." 1664 ::= { mplsLabelStackEntry 1 } 1666 mplsLabelStackLabelIndex OBJECT-TYPE 1667 SYNTAX Integer32 1668 MAX-ACCESS not-accessible 1669 STATUS current 1670 DESCRIPTION 1671 "Secondary index for this row identifying one label of 1672 the stack." 1673 ::= { mplsLabelStackEntry 2 } 1675 mplsLabelStackLabel OBJECT-TYPE 1676 SYNTAX MplsLabel 1677 MAX-ACCESS read-create 1678 STATUS current 1679 DESCRIPTION 1680 "Label to pushed." 1681 ::= { mplsLabelStackEntry 3 } 1683 mplsLabelStackRowStatus OBJECT-TYPE 1684 SYNTAX RowStatus 1685 MAX-ACCESS read-create 1686 STATUS current 1687 DESCRIPTION 1688 "For creating, modifying, and deleting this row." 1689 ::= { mplsLabelStackEntry 4 } 1691 -- End of mplsLabelStackTable 1693 -- Notifications. 1695 -- Tunnel. 1697 mplsTunnelUp NOTIFICATION-TYPE 1698 OBJECTS { mplsTunnelIndex, mplsTunnelAdminStatus, 1699 mplsTunnelOperStatus } 1700 STATUS current 1701 DESCRIPTION 1702 "This notification is generated when a mplsTunnelOperStatus 1703 object for one of the configured tunnels is about to leave 1704 the down state and transition into some other state (but not into 1705 the notPresent state). This other state is indicated by the 1706 included value of mplsTunnelOperStatus." 1707 ::= { mplsTeNotifications 1 } 1709 mplsTunnelDown NOTIFICATION-TYPE 1710 OBJECTS { mplsTunnelIndex, mplsTunnelAdminStatus, 1711 mplsTunnelOperStatus } 1712 STATUS current 1713 DESCRIPTION 1714 "This notification is generated when a mplsTunnelOperStatus 1715 object for one of the configured tunnels is about to enter the 1716 down state from some other state (but not from the notPresent 1717 state). This other state is indicated by the included value of 1718 mplsTunnelOperStatus." 1719 ::= { mplsTeNotifications 2 } 1721 -- In-segment. 1723 mplsInSegmentUp NOTIFICATION-TYPE 1724 OBJECTS { mplsInSegmentIfIndex, mplsInSegmentLabel, 1725 mplsInSegmentAdminStatus, mplsInSegmentOperStatus } 1726 STATUS current 1727 DESCRIPTION 1728 "This notification is generated when a mplsInSegmentOperStatus 1729 object for one of the configured in-segments is about to leave the 1730 down state and transition into some other state (but not into 1731 the notPresent state). This other state is indicated by the 1732 included value of mplsInSegmentOperStatus." 1733 ::= { mplsTeNotifications 3 } 1735 mplsInSegmentDown NOTIFICATION-TYPE 1736 OBJECTS { mplsInSegmentIfIndex, mplsInSegmentLabel, 1737 mplsInSegmentAdminStatus, mplsInSegmentOperStatus } 1738 STATUS current 1739 DESCRIPTION 1740 "This notification is generated when a mplsInSegmentOperStatus 1741 object for one of the configured in-segments is about to enter the 1742 down state from some other state (but not from the notPresent 1743 state). This other state is indicated by the included value of 1744 mplsInSegmentOperStatus." 1745 ::= { mplsTeNotifications 4 } 1747 -- Out-segment. 1749 mplsOutSegmentUp NOTIFICATION-TYPE 1750 OBJECTS { mplsOutSegmentIndex, mplsInSegmentAdminStatus, 1751 mplsInSegmentOperStatus } 1752 STATUS current 1753 DESCRIPTION 1754 "This notification is generated when a mplsOutSegmentOperStatus 1755 object for one of the configured out-segments is about to leave the 1756 down state and transition into some other state (but not into 1757 the notPresent state). This other state is indicated by the 1758 included value of mplsOutSegmentOperStatus." 1759 ::= { mplsTeNotifications 5 } 1761 mplsOutSegmentDown NOTIFICATION-TYPE 1762 OBJECTS { mplsOutSegmentIndex, mplsInSegmentAdminStatus, 1763 mplsInSegmentOperStatus } 1764 STATUS current 1765 DESCRIPTION 1766 "This notification is generated when a mplsOutSegmentOperStatus 1767 object for one of the configured out-segments is about to enter the 1768 down state from some other state (but not from the notPresent 1769 state). This other state is indicated by the included value of 1770 mplsOutSegmentOperStatus." 1771 ::= { mplsTeNotifications 6 } 1773 -- Cross-connect. 1775 mplsXCUp NOTIFICATION-TYPE 1776 OBJECTS { mplsXCIndex, 1777 mplsInSegmentIfIndex, mplsInSegmentLabel, 1778 mplsOutSegmentIndex, 1779 mplsXCAdminStatus, mplsXCOperStatus } 1780 STATUS current 1781 DESCRIPTION 1782 "This notification is generated when a mplsXCOperStatus 1783 object for one of the configured cross-connect entries is about 1784 to leave the down state and transition into some other state 1785 (but not into the notPresent state). This other state is 1786 indicated by the included value of mplsXCOperStatus." 1787 ::= { mplsTeNotifications 7 } 1789 mplsXCDown NOTIFICATION-TYPE 1790 OBJECTS { mplsXCIndex, 1791 mplsInSegmentIfIndex, mplsInSegmentLabel, 1792 mplsOutSegmentIndex, 1793 mplsXCAdminStatus, mplsXCOperStatus } 1794 STATUS current 1795 DESCRIPTION 1796 "This notification is generated when a mplsXCOperStatus 1797 object for one of the configured cross-connect entries is about 1798 to enter the down state from some other state (but not from 1799 the notPresent state). This other state is indicated by the 1800 included value of mplsXCOperStatus." 1801 ::= { mplsTeNotifications 8 } 1803 -- End of notifications. 1805 -- Module compliance. 1807 mplsTeGroups 1808 OBJECT IDENTIFIER ::= { mplsTeConformance 1 } 1810 mplsTeCompliances 1811 OBJECT IDENTIFIER ::= { mplsTeConformance 2 } 1813 mplsTeModuleCompliance MODULE-COMPLIANCE 1814 STATUS current 1815 DESCRIPTION 1816 "Compliance statement for agents that support the MPLS TE MIB." 1817 MODULE -- this module 1819 -- These groups have to be implemented by all LSRs. 1820 -- However they may all be supported as read-only objects 1821 -- in the case where manual configuration is not 1822 -- supported. 1824 MANDATORY-GROUPS { mplsInSegmentGroup, mplsOutSegmentGroup, 1825 mplsXCGroup } 1827 GROUP mplsTunnelGroup 1828 DESCRIPTION 1829 "This group is mandatory for devices which 1830 support tunnels. In addition, depending on the 1831 type of the tunnel (for example, manually configured 1832 or signalled, persistent or non-persistent, etc.), 1833 the following other groups are mandatory: 1834 mplsTunnelManualGroup and/or mplsTunnelSignalledGroup, 1835 mplsTunnelIsNotIntfcGroup and/or mplsTunnelIsIntfcGroup, 1836 mplsTunnelIsPersistent and/or mplsTunnelIsNotPersistent." 1838 GROUP mplsTunnelManualGroup 1839 DESCRIPTION 1840 "This group is mandatory for devices which 1841 support manual configuration of tunnels, in 1842 addition to mplsTunnelGroup. 1843 The following constraints apply: 1844 mplsTunnelSignallingProto should be at least 1845 read-only with a value of none(1)." 1847 GROUP mplsTunnelSignalledGroup 1848 DESCRIPTION 1849 "This group is mandatory for devices which 1850 support signalled tunnel set up, in addition to 1851 mplsTunnelGroup. 1852 The following constraints apply: 1853 mplsTunnelSignallingProto should be at least 1855 read-only with a value of ldp(2), or rsvp(3)." 1857 GROUP mplsTunnelIsNotIntfcGroup 1858 DESCRIPTION 1859 "This group is mandatory for devices which 1860 support tunnels that are not interfaces, in 1861 addition to mplsTunnelGroup. 1862 The following constraints apply: 1863 mplsTunnelIsIf must at least be read-only returning 1864 false(1)." 1866 GROUP mplsTunnelIsIntfcGroup 1867 DESCRIPTION 1868 "This group is mandatory for devices which 1869 support tunnels that are interfaces, in addition to 1870 mplsTunnelGroup. 1871 The following constraints apply: 1872 mplsTunnelIsIf must at least be read-only returning 1873 true(2)." 1875 GROUP mplsTunnelIsPersistentGroup 1876 DESCRIPTION 1877 "This group is mandatory for devices which 1878 support persistent tunnels, in addition to 1879 mplsTunnelGroup. 1880 The following constraints apply: 1881 mplsTunnelIsPersistent must at least be read-only 1882 returning true(2)." 1884 GROUP mplsTunnelIsNotPersistentGroup 1885 DESCRIPTION 1886 "This group is mandatory for devices which 1887 support non-persistent tunnels, in addition to 1888 mplsTunnelGroup. 1889 The following constraints apply: 1890 mplsTunnelIsPersistent must at least be read-only 1891 returning false(1)." 1893 -- Depending on whether the device implements persistent 1894 -- cross-connects or not one of the following two groups 1895 -- is mandatory. 1897 GROUP mplsXCIsPersistentGroup 1898 DESCRIPTION 1899 "This group is mandatory for devices which 1900 support persistent cross-connects. 1901 The following constraints apply: 1902 mplsXCIsPersistent must at least be read-only 1903 returning true(2)." 1905 GROUP mplsXCIsNotPersistentGroup 1906 DESCRIPTION 1907 "This group is mandatory for devices which 1908 support non-persistent cross-connects. 1909 The following constraints apply: 1910 mplsXCIsPersistent must at least be read-only 1911 returning false(1)." 1913 -- mplsTunnelTable 1915 OBJECT mplsTunnelDirection 1916 SYNTAX INTEGER { in(1), out(2) } 1917 DESCRIPTION 1918 "in-out(3) need not be supported." 1920 OBJECT mplsTunnelAdminStatus 1921 SYNTAX INTEGER { up (1), down (2) } 1922 DESCRIPTION 1923 "Only up and down states need to be supported." 1925 OBJECT mplsTunnelOperStatus 1926 SYNTAX INTEGER { up (1), down (2) } 1927 DESCRIPTION 1928 "Only up and down states need to be supported." 1930 OBJECT mplsTunnelRowStatus 1931 SYNTAX INTEGER { active(1), notInService(2), createAndGo(4), 1932 destroy(6) } 1933 DESCRIPTION 1934 "The notReady(3) and createAndWait(5) states need 1935 not be supported." 1937 -- mplsTunnelHopTable 1939 OBJECT mplsTunnelHopStrictOrLoose 1940 SYNTAX INTEGER { strict(1) } 1941 DESCRIPTION 1942 "loose(2) need not be supported." 1944 OBJECT mplsTunnelHopRowStatus 1945 SYNTAX INTEGER { active(1), notInService(2), createAndGo(4), 1946 destroy(6) } 1948 DESCRIPTION 1949 "The notReady(3) and createAndWait(5) states need 1950 not be supported." 1951 -- mplsInSegmentTable 1953 OBJECT mplsInSegmentIfIndex 1954 MIN-ACCESS read-only 1955 DESCRIPTION 1956 "Write access is not required." 1958 OBJECT mplsInSegmentLabel 1959 MIN-ACCESS read-only 1960 DESCRIPTION 1961 "Write access is not required." 1963 OBJECT mplsInSegmentXCIndex 1964 MIN-ACCESS read-only 1965 DESCRIPTION 1966 "Write access is not required." 1968 OBJECT mplsInSegmentMaxRate 1969 MIN-ACCESS read-only 1970 DESCRIPTION 1971 "Write access is not required." 1973 OBJECT mplsInSegmentMeanRate 1974 MIN-ACCESS read-only 1975 DESCRIPTION 1976 "Write access is not required." 1978 OBJECT mplsInSegmentMaxBurstSize 1979 MIN-ACCESS read-only 1980 DESCRIPTION 1981 "Write access is not required." 1983 OBJECT mplsInSegmentNPop 1984 MIN-ACCESS read-only 1985 DESCRIPTION 1986 "Write access if not required. This object should 1987 be set to 1 if it is read-only." 1989 OBJECT mplsInSegmentAddrFamily 1990 SYNTAX INTEGER { other(0) } 1991 MIN-ACCESS read-only 1992 DESCRIPTION 1993 "Write access is not required. A value of other(0) 1994 should be supported." 1996 OBJECT mplsInSegmentAdminStatus 1997 SYNTAX INTEGER { up(1), down(2) } 1998 MIN-ACCESS read-only 1999 DESCRIPTION 2000 "A value of testing(3) need not be supported." 2001 OBJECT mplsInSegmentOperStatus 2002 SYNTAX INTEGER { up(1), down(2) } 2003 MIN-ACCESS read-only 2004 DESCRIPTION 2005 "Only up(1) and down(2) need to be supported." 2007 OBJECT mplsInSegmentRowStatus 2008 SYNTAX INTEGER { active(1), notInService(2), createAndGo(4), 2009 destroy(6) } 2010 MIN-ACCESS read-only 2011 DESCRIPTION 2012 "The notReady(3) and createAndWait(5) states need 2013 not be supported." 2015 -- mplsOutSegmentTable 2017 OBJECT mplsOutSegmentIndex 2018 MIN-ACCESS read-only 2019 DESCRIPTION 2020 "Write access is not required." 2022 OBJECT mplsOutSegmentIfIndex 2023 MIN-ACCESS read-only 2024 DESCRIPTION 2025 "Write access is not required." 2027 OBJECT mplsOutSegmentPushTopLabel 2028 MIN-ACCESS read-only 2029 DESCRIPTION 2030 "Write access is not required." 2032 OBJECT mplsOutSegmentTopLabel 2033 MIN-ACCESS read-only 2034 DESCRIPTION 2035 "Write access is not required." 2037 OBJECT mplsOutSegmentNextHopIpAddrType 2038 SYNTAX INTEGER { none(1), ipV4(2) } 2039 MIN-ACCESS read-only 2040 DESCRIPTION 2041 "ipV6(3) need not be supported." 2043 OBJECT mplsOutSegmentNextHopIpv4Addr 2044 MIN-ACCESS read-only 2045 DESCRIPTION 2046 "Write access is not required." 2048 OBJECT mplsOutSegmentNextHopIpv6Addr 2049 MIN-ACCESS read-only 2050 DESCRIPTION 2051 "Write access is not required." 2053 OBJECT mplsOutSegmentXCIndex 2054 MIN-ACCESS read-only 2055 DESCRIPTION 2056 "Write access is not required." 2058 OBJECT mplsOutSegmentMaxRate 2059 MIN-ACCESS read-only 2060 DESCRIPTION 2061 "Write access is not required." 2063 OBJECT mplsOutSegmentMeanRate 2064 MIN-ACCESS read-only 2065 DESCRIPTION 2066 "Write access is not required." 2068 OBJECT mplsOutSegmentMaxBurstSize 2069 MIN-ACCESS read-only 2070 DESCRIPTION 2071 "Write access is not required." 2073 OBJECT mplsOutSegmentAdminStatus 2074 SYNTAX INTEGER { up(1), down(2) } 2075 MIN-ACCESS read-only 2076 DESCRIPTION 2077 "A value of testing(3) need not be supported." 2079 OBJECT mplsOutSegmentOperStatus 2080 SYNTAX INTEGER { up(1), down(2) } 2081 MIN-ACCESS read-only 2082 DESCRIPTION 2083 "Only up(1) and down(2) need to be supported." 2085 OBJECT mplsOutSegmentRowStatus 2086 SYNTAX INTEGER { active(1), notInService(2), createAndGo(4), 2087 destroy(6) } 2088 MIN-ACCESS read-only 2089 DESCRIPTION 2090 "The notReady(3) and createAndWait(5) states need 2091 not be supported." 2093 -- mplsXCTable 2095 OBJECT mplsXCIndex 2096 MIN-ACCESS read-only 2097 DESCRIPTION 2098 "Write access is not required." 2100 OBJECT mplsXCLabelStackIndex 2101 MIN-ACCESS read-only 2102 DESCRIPTION 2103 "Write access is not required." 2105 OBJECT mplsXCCOS 2106 MIN-ACCESS read-only 2107 DESCRIPTION 2108 "Write access is not required." 2110 OBJECT mplsXCIsPersistent 2111 MIN-ACCESS read-only 2112 DESCRIPTION 2113 "Write access is not required." 2115 OBJECT mplsXCAdminStatus 2116 SYNTAX INTEGER { up(1), down(2) } 2117 MIN-ACCESS read-only 2118 DESCRIPTION 2119 "A value of testing(3) need not be supported." 2121 OBJECT mplsXCOperStatus 2122 SYNTAX INTEGER { up(1), down(2) } 2123 MIN-ACCESS read-only 2124 DESCRIPTION 2125 "Only up(1) and down(2) need to be supported." 2127 OBJECT mplsXCRowStatus 2128 SYNTAX INTEGER { active(1), notInService(2), createAndGo(4), 2129 destroy(6) } 2130 MIN-ACCESS read-only 2131 DESCRIPTION 2132 "The notReady(3) and createAndWait(5) states need 2133 not be supported." 2135 ::= { mplsTeCompliances 1 } 2137 -- Units of conformance. 2139 mplsInSegmentGroup OBJECT-GROUP 2140 OBJECTS { mplsInSegmentIfIndex, mplsInSegmentLabel, 2141 mplsInSegmentNPop, mplsInSegmentAddrFamily, 2142 mplsInSegmentXCIndex, 2143 mplsInSegmentAdminStatus, mplsInSegmentOperStatus, 2144 mplsInSegmentRowStatus, 2145 mplsInSegmentOctets, mplsInSegmentDiscards } 2146 STATUS current 2147 DESCRIPTION 2149 "Collection of objects needed to implement an in-segment." 2150 ::= { mplsTeGroups 1 } 2152 mplsOutSegmentGroup OBJECT-GROUP 2153 OBJECTS { mplsOutSegmentIndex, mplsOutSegmentIfIndex, 2154 mplsOutSegmentPushTopLabel, mplsOutSegmentTopLabel, 2155 mplsOutSegmentNextHopIpAddrType, 2156 mplsOutSegmentNextHopIpv4Addr, 2157 mplsOutSegmentNextHopIpv6Addr, 2158 mplsOutSegmentXCIndex, 2159 mplsOutSegmentAdminStatus, mplsOutSegmentOperStatus, 2160 mplsOutSegmentRowStatus, 2161 mplsOutSegmentOctets, mplsOutSegmentDiscards } 2162 STATUS current 2163 DESCRIPTION 2164 "Collection of objects needed to implement an out-segment." 2165 ::= { mplsTeGroups 2 } 2167 mplsXCGroup OBJECT-GROUP 2168 OBJECTS { mplsXCIndex, mplsXCLabelStackIndex, 2169 mplsXCAdminStatus, mplsXCOperStatus, mplsXCRowStatus } 2170 STATUS current 2171 DESCRIPTION 2172 "Collection of objects needed to implement a cross- 2173 connect entry." 2174 ::= { mplsTeGroups 3 } 2176 mplsTunnelGroup OBJECT-GROUP 2177 OBJECTS { mplsTunnelIndex, mplsTunnelName, 2178 mplsTunnelDirection, mplsTunnelXCIndex, 2179 mplsTunnelIfIndex, 2180 mplsTunnelAdminStatus, mplsTunnelOperStatus, 2181 mplsTunnelRowStatus } 2182 STATUS current 2183 DESCRIPTION 2184 "Necessary, but not sufficient, set of objects to implement 2185 tunnels. Other objects are required depending on the type of 2186 tunnel supported, such as signalled, manual etc., as defined 2187 in the groups below." 2188 ::= { mplsTeGroups 4 } 2190 mplsTunnelManualGroup OBJECT-GROUP 2191 OBJECTS { mplsTunnelSignallingProto } 2192 STATUS current 2193 DESCRIPTION 2194 "Object(s) needed to implement manually configured tunnels." 2195 ::= { mplsTeGroups 5 } 2197 mplsTunnelSignalledGroup OBJECT-GROUP 2198 OBJECTS { mplsTunnelSignallingProto, 2199 mplsTunnelLocalCookie, mplsTunnelRemoteCookie, 2200 mplsTunnelHopIndex, mplsTunnelHopAddrType, 2201 mplsTunnelHopIpv4Addr, mplsTunnelHopIpv4PrefixLen, 2202 mplsTunnelHopIpv6Addr, mplsTunnelHopIpv6PrefixLen, 2203 mplsTunnelHopStrictOrLoose, mplsTunnelHopRowStatus } 2204 STATUS current 2205 DESCRIPTION 2206 "Object needed to implement signalled tunnels." 2207 ::= { mplsTeGroups 6 } 2209 mplsTunnelIsIntfcGroup OBJECT-GROUP 2210 OBJECTS { mplsTunnelIsIf } 2211 STATUS current 2212 DESCRIPTION 2213 "Objects needed to implement tunnels that are interfaces." 2214 ::= { mplsTeGroups 7 } 2216 mplsTunnelIsNotIntfcGroup OBJECT-GROUP 2217 OBJECTS { mplsTunnelIsIf } 2218 STATUS current 2219 DESCRIPTION 2220 "Objects needed to implement tunnels that are not interfaces." 2221 ::= { mplsTeGroups 8 } 2223 mplsTunnelIsPersistentGroup OBJECT-GROUP 2224 OBJECTS { mplsTunnelIsPersistent } 2225 STATUS current 2226 DESCRIPTION 2227 "Objects needed to support persistent tunnels." 2228 ::= { mplsTeGroups 9 } 2230 mplsTunnelIsNotPersistentGroup OBJECT-GROUP 2231 OBJECTS { mplsTunnelIsPersistent } 2232 STATUS current 2233 DESCRIPTION 2234 "Objects needed to support non-persistent tunnels." 2235 ::= { mplsTeGroups 10 } 2237 mplsXCIsPersistentGroup OBJECT-GROUP 2238 OBJECTS { mplsXCIsPersistent } 2239 STATUS current 2240 DESCRIPTION 2241 "Objects needed to support persistent cross-connects." 2242 ::= { mplsTeGroups 11 } 2244 mplsXCIsNotPersistentGroup OBJECT-GROUP 2245 OBJECTS { mplsXCIsPersistent } 2246 STATUS current 2247 DESCRIPTION 2248 "Objects needed to support non-persistent cross-connects." 2250 ::= { mplsTeGroups 12 } 2252 mplsTeNotificationGroup NOTIFICATION-GROUP 2253 NOTIFICATIONS { mplsTunnelUp, mplsTunnelDown, 2254 mplsInSegmentUp, mplsInSegmentDown, 2255 mplsOutSegmentUp, mplsOutSegmentDown, 2256 mplsXCUp, mplsXCDown } 2257 STATUS current 2258 DESCRIPTION 2259 "Set of notifications implemented in this 2260 module. None is mandatory." 2261 ::= { mplsTeGroups 13 } 2263 -- End of MPLS-TE-MIB 2264 END 2266 9. Security Considerations 2268 The MIBs specified in this document does not raise any security 2269 issues other than those present in the MPLS architecture [1] or 2270 those imposed by SNMP itself. 2272 10. Acknowledgments 2274 We wish to thank Patrick Kerharo, Eric Gray and Pramod Koppol for 2275 their comments on this draft. 2277 11. References 2279 [1] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol 2280 Label Switching Architecture", Internet Draft , July, 1998 2283 [2] Callon, R., Doolan, P., Feldman, N., Fredette, A., Swallow, 2284 G., and A. Viswanathan, "A Framework for Multiprotocol Label 2285 Switching", Internet Draft , 2286 November 1997. 2288 [3] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D., Federokow, 2289 G., Li, T., and A. Conta, "MPLS Label Stack Encoding", Internet 2290 Draft , September 1998. 2292 [4] Awaduche, D., Berger, L., Der-Haw, G., Li, T., Swallow, G., 2293 and V. Srinivasan, "Extensions to RSVP for LSP Tunnels", Internet 2294 Draft , November 1998. 2296 [5] Andersson, L., Fredette, A., Jamoussi, B., Callon, R., Doolan, 2297 P., Feldman, N., Gray, E., Halpern, J., Heinenan, J., Kilty, T., 2298 Malis, A., Girish, M., Sundell, K., Vaananen, P., T. Worster, Wu, 2299 L., and Dantu, R., "Explicit Routing Over LDP Specification", 2300 Internet Draft , November 1998. 2302 [6] Reynolds, J. and J. Postel, "Assigned Numbers", RFC 1700, 2303 October 1994. 2305 [7] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 2306 for Describing SNMP Management Frameworks", RFC 2271, January 2307 1998. 2309 [8] Rose, M., and K. McCloghrie, "Structure and Identification of 2310 Management Information for TCP/IP-based Internets", RFC 1155, May 2311 1990. 2313 [9] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 2314 1212, March 1991. 2316 [10] M. Rose, "A Convention for Defining Traps for use with the 2317 SNMP", RFC 1215, March 1991. 2319 [11] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2320 "Structure of Management Information for Version 2 of the Simple 2321 Network Management Protocol (SNMPv2)", RFC 1902, January 1996. 2323 [12] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2324 "Textual Conventions for Version 2 of the Simple Network 2325 Management Protocol (SNMPv2)", RFC 1903, SNMP Research, Inc., 2326 Cisco Systems, Inc., January 1996. 2328 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2329 "Conformance Statements for Version 2 of the Simple Network 2330 Management Protocol (SNMPv2)", RFC 1904, January 1996. 2332 [14] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 2333 Network Management Protocol", RFC 1157, May 1990. 2335 [15] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2336 "Introduction to Community-based SNMPv2", RFC 1901, January 1996. 2338 [16] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2339 "Transport Mappings for Version 2 of the Simple Network Management 2340 Protocol (SNMPv2)", RFC 1906, January 1996. 2342 [17] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 2343 Processing and Dispatching for the Simple Network Management 2344 Protocol (SNMP)", RFC 2272, January 1998. 2346 [18] Blumenthal, U., and B. Wijnen, "User-based Security Model 2347 (USM) for version 3 of the Simple Network Management Protocol 2348 (SNMPv3)", RFC 2274, January 1998. 2350 [19] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2351 "Protocol Operations for Version 2 of the Simple Network 2352 Management Protocol (SNMPv2)", RFC 1905, January 1996. 2354 [20] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 2355 RFC 2273, January 1998 2357 [21] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 2358 Access Control Model (VACM) for the Simple Network Management 2359 Protocol (SNMP)", RFC 2275, January 1998 2361 12. Authors's Addresses 2363 Cheenu Srinivasan 2364 Lucent Technologies 2365 4F535, 101 Crawfords Corner Road 2366 Holmdel, NJ 07733 2368 Phone: +1-732-949-0709 2369 Email: cheenu@lucent.com 2371 Arun Viswanathan 2372 Lucent Technologies 2373 4D537, 101 Crawfords Corner Road 2374 Holmdel, NJ 07733 2376 Phone: +1-732-332-5613 2377 Email: arunv@lucent.com