idnits 2.17.1 draft-ietf-mpls-lsr-mib-07.txt: ** The Abstract section seems to be numbered 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: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 53 longer pages, the longest (page 2) being 59 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 54 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([MPLSArch,MPLSFW]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 2612 has weird spacing: '...for the purpo...' -- 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 2001) is 8502 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'SNMPv1MIBDef' is mentioned on line 120, but not defined == Unused Reference: 'Assigned' is defined on line 2457, but no explicit reference was found in the text == Unused Reference: 'RFC2572' is defined on line 2482, but no explicit reference was found in the text == Unused Reference: 'RFC2574' is defined on line 2487, but no explicit reference was found in the text == Unused Reference: 'RFC1905' is defined on line 2492, but no explicit reference was found in the text == Unused Reference: 'RFC2573' is defined on line 2497, but no explicit reference was found in the text == Unused Reference: 'RFC2575' is defined on line 2500, but no explicit reference was found in the text == Unused Reference: 'RFC2570' is defined on line 2505, 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. 'LblStk' ** Obsolete normative reference: RFC 1700 (ref. 'Assigned') (Obsoleted by RFC 3232) -- Possible downref: Non-RFC (?) normative reference: ref. 'IANAFamily' ** 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 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** 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) -- Duplicate reference: RFC2574, mentioned in 'SNMPv3USM', was also mentioned in 'RFC2574'. ** Obsolete normative reference: RFC 2574 (ref. 'SNMPv3USM') (Obsoleted by RFC 3414) -- Duplicate reference: RFC1905, mentioned in 'SNMPv2PO', was also mentioned in 'RFC1905'. ** Obsolete normative reference: RFC 1905 (ref. 'SNMPv2PO') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2273 (ref. 'SNMPv3App') (Obsoleted by RFC 2573) -- Duplicate reference: RFC2575, mentioned in 'SNMPv3VACM', was also mentioned in 'RFC2575'. ** Obsolete normative reference: RFC 2575 (ref. 'SNMPv3VACM') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2401 (ref. 'IPSEC') (Obsoleted by RFC 4301) ** Obsolete normative reference: RFC 2233 (ref. 'IFMIB') (Obsoleted by RFC 2863) Summary: 27 errors (**), 0 flaws (~~), 12 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 Networks, Inc. 3 Expires: July 2001 4 Arun Viswanathan 5 Force10 Networks, Inc. 7 Thomas D. Nadeau 8 Cisco Systems, Inc. 9 January 2001 11 MPLS Label Switch Router Management Information Base Using SMIv2 13 draft-ietf-mpls-lsr-mib-07.txt 15 Status of this Memo 17 This document is an Internet-Draft and is in full conformance with 18 all provisions of Section 10 of RFC 2026. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that 22 other groups may also distribute working documents as Internet- 23 Drafts. 25 Internet-Drafts are draft documents valid for a maximum of six 26 months and may be updated, replaced, or obsoleted by other 27 documents at any time. It is inappropriate to use Internet- 28 Drafts as reference material or to cite them other than as "work 29 in progress." 31 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt. 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html. 37 Table of Contents 39 1. Abstract............................................2 40 2. Introduction........................................2 41 3. Terminology.........................................2 42 4. The SNMP Management Framework.......................3 43 4.1. Object Definitions..................................4 44 5. Feature Checklist...................................4 45 6. Outline.............................................5 46 6.1. Summary of LSR MIB..................................5 47 7. Brief Description of MIB Objects....................6 48 7.1. mplsInterfaceConfTable..............................6 49 7.2. mplsInterfacePerfTable..............................6 50 7.3. mplsInSegmentTable..................................6 51 7.4. mplsInSegmentPerfTable..............................7 52 7.5. mplsOutSegmentTable.................................7 53 7.6. mplsOutSegmentPerfTable............................7 54 7.7. mplsXCTable........................................7 55 7.8. mplsLabelStackTable................................8 56 7.9. mplsTrafficParamTable..............................8 57 8. Example of LSP Setup...............................8 58 9. Application of the Interface Group to MPLS........10 59 9.1. Support of the MPLS Layer by ifTable..............10 60 10. The Use of RowPointer.............................12 61 11. MPLS Label Switch Router MIB Definitions..........12 62 12. Security Considerations...........................49 63 13. Acknowledgments...................................50 64 14. References........................................50 65 15. Authors' Addresses................................53 66 16. Full Copyright Statement..........................53 68 1. Abstract 70 This memo defines an experimental portion of the Management 71 Information Base (MIB) for use with network management protocols 72 in the Internet community. In particular, it describes managed 73 objects for modeling a Multi-Protocol Label Switching (MPLS) 74 [MPLSArch, MPLSFW] Label Switch Router (LSR). 76 Note: There have been no changes to this document. This is only an 77 update to prevent the document from expiring while in IESG review. 79 2. Introduction 81 This memo defines an experimental portion of the Management 82 Information Base (MIB) for use with network management protocols 83 in the Internet community. In particular, it describes managed 84 objects for modeling a Multi-Protocol Label Switching (MPLS) 85 [MPLSArch, MPLSFW] Label Switch Router (LSR). 87 Comments should be made directly to the MPLS mailing list at 88 mpls@uu.net. 90 This memo does not, in its draft form, specify a standard for the 91 Internet community. 93 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 94 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 95 "OPTIONAL" in this document are to be interpreted as described in 96 RFC 2119, reference [BCP14]. 98 3. Terminology 100 This document uses terminology from the document describing the 101 MPLS architecture [MPLSArch]. A label switched path (LSP) is 102 modeled as a connection consisting of one or more incoming 103 segments (in-segments) and/or one or more outgoing segments (out- 104 segments) at a label switch router (LSR). The association or 105 interconnection of the in-segments and out-segments is 106 accomplished by using a cross-connect. We use the terminology 107 "connection" and "LSP" interchangeably where the meaning is clear 108 from the context. 110 4. The SNMP Management Framework 112 The SNMP Management Framework presently consists of five major 113 components: 115 - An overall architecture, described in RFC 2271 [SNMPArch]. 117 - Mechanisms for describing and naming objects and events for the 118 purpose of management. The first version of this Structure of 119 Management Information (SMI) is called SMIv1 and described in 120 RFC 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215 121 [SNMPv1Traps]. The second version, called SMIv2, is described 122 in RFC 1902 [SMIv2], RFC 1903 [SNMPv2TC] and RFC 1904 123 [SNMPv2Conf]. 125 - Message protocols for transferring management information. The 126 first version of the SNMP message protocol is called SNMPv1 127 and described in RFC 1157 [SNMPv1]. A second version of the 128 SNMP message protocol, which is not an Internet standards 129 track protocol, is called SNMPv2c and described in RFC 1901 130 [SNMPv2c] and RFC 1906 [SNMPv2TM]. The third version of the 131 message protocol is called SNMPv3 and described in RFC 1906 132 [SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC 2574 [SNMPv3USM]. 134 - Protocol operations for accessing management information. The 135 first set of protocol operations and associated PDU formats is 136 described in RFC 1157 [SNMPv1]. A second set of protocol 137 operations and associated PDU formats is described in RFC 1905 138 [SNMPv2PO]. 140 - A set of fundamental applications described in RFC 2273 141 [SNMPv3App] and the view-based access control mechanism 142 described in RFC 2575 [SNMPv3VACM]. 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 mechanisms defined in the SMI. This memo 147 specifies a MIB module that is compliant to the SMIv2. A MIB 148 conforming to the SMIv1 can be produced through the appropriate 149 translations. The resulting translated MIB must be semantically 150 equivalent, except where objects or events are omitted because no 151 translation is possible (use of Counter64). Some machine-readable 152 information in SMIv2 will be converted into textual descriptions 153 in SMIv1 during the translation process. However, this loss of 154 machine-readable information is not considered to change the 155 semantics of the MIB. 157 4.1. Object Definitions 159 Managed objects are accessed via a virtual information store, 160 termed the Management Information Base or MIB. Objects in the MIB 161 are defined using the subset of Abstract Syntax Notation One 162 (ASN.1) defined in the SMI. In particular, each object type is 163 named by an OBJECT IDENTIFIER, an administratively assigned name. 164 The object type together with an object instance serves to 165 uniquely identify a specific instantiation of the object. For 166 human convenience, we often use a textual string, termed the 167 descriptor, to also refer to the object type. 169 5. Feature Checklist 171 The MPLS label switch router MIB (LSR-MIB) is designed to satisfy 172 the following requirements and constraints: 174 - The MIB supports both manually configured LSPs as well as those 175 configured via any MPLS signaling protocol. 177 - The MIB supports the enabling and disabling of MPLS capability 178 on MPLS capable interfaces of an LSR. 180 - The MIB allows resource sharing between two or more LSPs. 182 - Both per-platform and per-interface label spaces are supported. 184 - MPLS packets can be forwarded solely based on an incoming top 185 label [MPLSArch, LblStk]. 187 - Support is provided for next-hop resolution when the outgoing 188 interface is a shared media interface. In the point-to- 189 multipoint case, each outgoing segment can reside on a 190 different shared media interface. 192 - The MIB supports point-to-point, point-to-multipoint and 193 multipoint-to-point connections at an LSR. 195 - For multipoint-to-point connections all outgoing packets can 196 have the same top label. 198 - For multipoint-to-point connections, the outgoing resources of 199 the merged connections can be shared. 201 - For multipoint-to-point connections, packets from different 202 incoming connections can have distinct outgoing label stacks 203 beneath the (identical) top label. 205 - In the point-to-multipoint case each outgoing connection can 206 have a distinct label stack including the top label. 208 - All the members of a point-to-multipoint connection can share 209 the resources allocated for the ingress segments. 211 - The MIB provides cross-connect capability to "pop" an incoming 212 label and forward the packet with the remainder of the label 213 stack unchanged and without pushing any labels ("pop-and-go") 214 [LblStk]. 216 - The MIB supports persistent as well as non-persistent LSPs. 218 - Performance counters are provided for in-segments and out- 219 segments as well as for measuring MPLS performance on a per- 220 interface basis. 222 6. Outline 224 Configuring LSPs through an LSR involves the following steps: 226 - Enabling MPLS on MPLS capable interfaces. 228 - Configuring in-segments and out-segments. 230 - Setting up the cross-connect table to associate segments and/or 231 to indicate connection origination and termination. 233 - Optionally specifying label stack actions. 235 - Optionally specifying segment traffic parameters. 237 6.1. Summary of LSR MIB 239 The MIB objects for performing these actions consist of the 240 following tables: 242 - The interface configuration table (mplsInterfaceConfTable), 243 which is used for enabling the MPLS protocol on MPLS-capable 244 interfaces. 246 - The in-segment (mplsInSegmentTable) and out-segment 247 (mplsOutSegmentTable) tables, which are used for configuring 248 LSP segments at an LSR. 250 - The cross-connect table (mplsXCTable), which is used to 251 associate in and out segments together, in order to form a 252 cross-connect. 254 - The label stack table (mplsLabelStackTable), which is used for 255 specifying label stack operations. 257 - The Traffic Parameter table (mplsTrafficParamTable), which is 258 used for specifying LSP-related traffic parameters. 260 Further, the MPLS in-segment and out-segment performance tables, 261 mplsInSegmentPerfTable and mplsOutSegmentPerfTable, contain the 262 objects necessary to measure the performance of LSPs, and 263 mplsInterfacePerfTable has objects to measure MPLS performance on 264 a per-interface basis. 266 These tables are described in the subsequent sections. 268 7. Brief Description of MIB Objects 270 Sections 7.1-7.2 describe objects pertaining to MPLS-capable 271 interfaces of an LSR. The objects described in Sections 7.3-7.8, 272 were derived from the Incoming Label Map (ILM) and Next Hop Label 273 Forwarding Entry (NHLFE) as specified in the MPLS architecture 274 document [MPLSArch]. Section 7.9 describes objects for specifying 275 traffic parameters for in and out segments. It is appropriate to 276 note that the in-segment, out-segment, and cross-connect tables 277 were modeled after similar tables found in [ATOMMIB]. 279 7.1. mplsInterfaceConfTable 281 This table represents the interfaces that are MPLS capable. An 282 LSR creates an entry in this table for every MPLS capable 283 interface on that LSR. 285 7.2. mplsInterfacePerfTable 287 This table contains objects to measure the MPLS performance of 288 MPLS capable interfaces and is an AUGMENT to 289 mplsInterfaceConfTable. High capacity counters are provided for 290 objects that are likely to wrap around quickly on high-speed 291 interfaces. 293 7.3. mplsInSegmentTable 294 This table contains a description of the incoming MPLS segments to 295 an LSR and their associated parameters. 297 The administrative and operational status objects for this table 298 are used to control packet transmission on this segment. If 299 either the administrative and operational status objects for this 300 table are set to 'down', this implies that packets will not be 301 forwarded. Likewise, if the values are set to 'up' this implies 302 that packets are forwarded. These values are particularly useful 303 in cases where multi-point connections utilize a single cross- 304 connect and the administrator wishes to disable some, but not all 305 of the streams. In these cases, the administrator may set the 306 administrative status object to 'down' on some of the in-segments. 308 7.4. mplsInSegmentPerfTable 310 The MPLS In-Segment Performance Table has objects to measure the 311 performance of an incoming segment configured on an LSR. It is an 312 AUGMENT to mplsInSegmentTable. High capacity counters are 313 provided for objects that are likely to wrap around quickly on 314 high-speed interfaces. 316 7.5. mplsOutSegmentTable 318 The Out-Segment Table contains a description of the outgoing MPLS 319 segments at an LSR and their associated parameters. 321 The administrative and operational status objects for this table 322 are used to control packet transmission on this segment. If 323 either the administrative and operational status objects are set 324 to 'down', this implies that packets will not be forwarded. 325 Likewise, if the values are set to 'up' this implies that packets 326 are forwarded. These values are particularly useful in cases 327 where multicast connections utilize a single cross-connect and the 328 administrator wishes to disable some, but not all of the streams. 329 In these cases, the administrator may set the administrative 330 status object to 'down' on some of the out-segments. 332 7.6. mplsOutSegmentPerfTable 334 The MPLS Out-Segment Table contains objects to measure the 335 performance of an outgoing segment configured on an LSR. It is an 336 AUGMENT to mplsOutSegmentTable. High capacity counters are 337 provided for objects that are likely to wrap around quickly on 338 high-speed interfaces. 340 7.7. mplsXCTable 341 The mplsXCTable specifies information for associating segments 342 together in order to instruct the LSR to switch between the 343 specified segments. It supports point-to-point, point-to-multi- 344 point and multi-point-to-point connections. 346 The administrative and operational status objects for this table 347 imply control of packet forwarding to and from a XCEntry. When 348 the administrative and operational status objects are set to 349 'down' for example, this implies that the specified XCEntry will 350 not forward packets. Likewise, when either is set to 'up' this 351 implies that packets will be forwarded. 353 7.8. mplsLabelStackTable 355 The mplsLabelStackTable specifies the label stack to be pushed 356 onto a packet, beneath the top label. Entries to this table are 357 referred to from mplsXCTable. 359 7.9. mplsTrafficParamTable 361 The mplsTrafficParamTable contains objects for specifying the 362 traffic parameters of in-segments and out-segments. Entries in 363 this table are referred to from mplsInSegmentTable and 364 mplsOutSegmentTable. 366 8. Example of LSP Setup 368 In this section we provide a brief example of using the MIB 369 objects described in section 11. to set up an LSP. While this 370 example is not meant to illustrate every nuance of the MIB, it is 371 intended as an aid to understanding some of the key concepts. It 372 is meant to be read after going through the MIB itself. 374 Suppose that one would like to manually create a best-effort, 375 unidirectional LSP. Assume that the LSP enters the LSR via MPLS 376 interface A with ifIndex 12 and exits the LSR via MPLS interface B 377 with ifIndex 13. Let us assume that we do not wish to have a 378 label stack beneath the top label on the outgoing labeled packets. 379 The following example illustrates which rows and corresponding 380 objects might be created to accomplish this. 382 First, the traffic parameter entries must be set-up for both 383 segments. 385 In mplsTrafficParamTable for the incoming direction: 386 { 387 mplsTrafficParamIndex = 5 388 mplsTrafficParamMaxRate = 100000, 389 mplsTrafficParamMeanRate = 100000, 390 mplsTrafficParamMaxBurstSize = 2000, 391 mplsTrafficParamRowStatus = createAndGo(4) 392 } 394 In mplsTrafficParamTable for the outgoing direction: 395 { 396 mplsTrafficParamIndex = 6 397 mplsTrafficParamMaxRate = 100000, 398 mplsTrafficParamMeanRate = 100000, 399 mplsTrafficParamMaxBurstSize = 2000, 400 mplsTrafficParamRowStatus = createAndGo(4) 401 } 403 Note that if we were setting up a bi-directional LSP, the segments 404 in the reverse direction can share the traffic parameter entries 405 (and hence resources) with the segments in the forward direction. 407 We must next create the appropriate in-segment and out-segment 408 entries with suitable traffic parameters by pointing to the 409 appropriate traffic parameter entries that we have just created. 411 In mplsInSegmentTable: 412 { 413 mplsInSegmentIfIndex = 12, -- incoming interface 414 mplsInSegmentLabel = 21, -- incoming label 415 mplsInSegmentNPop = 1, 416 mplsInSegmentTrafficParamPtr = mplsTrafficParamIndex.5, 417 mplsInSegmentRowStatus = createAndGo(4) 418 } 420 In mplsOutSegmentTable: 421 { 422 mplsOutSegmentIndex = 1, 423 mplsOutSegmentIfIndex = 13, -- outgoing interface 424 mplsOutSegmentPushTopLabel = true(1), 425 mplsOutSegmentTopLabel = 22, -- outgoing label 426 mplsOutSegmentTrafficParamPtr = mplsTrafficParamIndex.6, 427 mplsOutSegmentRowStatus = createAndGo(4) 428 } 430 Next, a cross-connect entry is created thereby associating the 431 newly created segments together. 433 In mplsXCTable: 434 { 435 mplsXCIndex = 2, 436 mplsXCLspId = 'c021041502'H, -- 192.33.4.21.2 437 mplsInSegmentIfIndex = 12, 438 mplsInSegmentLabel = 21, 439 mplsOutSegmentIndex = 1, 440 mplsXCIsPersistent = false (1), 441 mplsLabelStackIndex = 0, -- only a single 442 -- outgoing label 443 mplsXCRowStatus = createAndGo(4) 444 } 446 Note that the mplsInSegmentXCIndex and mplsOutSegmentXCIndex 447 objects will automatically be populated with the value 2 when 448 these segments are referred to from the corresponding cross- 449 connect entry. 451 9. Application of the Interface Group to MPLS 453 The Interfaces Group of MIB II defines generic managed objects for 454 managing interfaces. This memo contains the media-specific 455 extensions to the Interfaces Group for managing MPLS interfaces. 457 This memo assumes the interpretation of the Interfaces Group to be 458 in accordance with [IFMIB] which states that the interfaces table 459 (ifTable) contains information on the managed resource's 460 interfaces and that each sub-layer below the internetwork layer of 461 a network interface is considered an interface. Thus, the MPLS 462 interface is represented as an entry in the ifTable. The inter- 463 relation of entries in the ifTable is defined by Interfaces Stack 464 Group defined in [IFMIB]. 466 When using MPLS interfaces, the interface stack table might appear 467 as follows: 469 +----------------------------------------+ 470 | MPLS-interface ifType = mpls(166) + 471 +----------------------------------------+ 472 | Underlying Layer... + 473 +----------------------------------------+ 475 In the above diagram, "Underlying Layer..." refers to the ifIndex 476 of any interface type, which has been defined for MPLS 477 interworking. Examples include ATM, Frame Relay, Ethernet, etc. 479 9.1. Support of the MPLS Layer by ifTable 481 Some specific interpretations of ifTable for the MPLS layer 482 follow. 484 Object Use for the MPLS layer 486 ifIndex Each MPLS interface is represented by an ifEntry. 488 ifDescr Description of the MPLS interface. 490 ifType The value that is allocated for MPLS is 166. 492 ifSpeed The total bandwidth in bits per second for use by 493 the MPLS layer. 495 ifPhysAddress Unused. 497 ifAdminStatus This variable indicates the administrator's intent 498 as to whether MPLS should be enabled, disabled, or 499 running in some diagnostic testing mode on this 500 interface. Also see [IFMIB]. 502 ifOperStatus This value reflects the actual or operational 503 status of MPLS on this interface. 505 ifLastChange See [IFMIB]. 507 ifInOctets The number of received octets over the interface, 508 i.e., the number of received, octets received as 509 labeled packets. 511 ifOutOctets The number of transmitted octets over the 512 interface, i.e., the number of octets transmitted 513 as labeled packets. 515 ifInErrors The number of labeled packets dropped due to 516 uncorrectable errors. 518 ifInUnknownProtos 519 The number of received packets discarded during 520 packet header validation, including packets with 521 unrecognized label values. 523 ifOutErrors See [IFMIB]. 525 ifName Textual name (unique on this system) of the 526 interface or an octet string of zero length. 528 ifLinkUpDownTrapEnable 529 Default is disabled (2). 531 ifConnectorPresent 532 Set to false (2). 534 ifHighSpeed See [IFMIB]. 536 ifHCInOctets The 64-bit version of ifInOctets; supported if 537 required by the compliance statements in [IFMIB]. 539 ifHCOutOctets The 64-bit version of ifOutOctets; supported if 540 required by the compliance statements in [IFMIB]. 542 ifAlias The non-volatile 'alias' name for the interface as 543 specified by a network manager. 545 ifCounterDiscontinuityTime 546 See [IFMIB]. 548 10. The Use of RowPointer 550 RowPointer is a textual convention used to identify a conceptual 551 row in an SNMP Table by pointing to one of its objects. In this 552 MIB, it is used in mplsInSegmentTable and mplsOutSegmentTable 553 for the following purposes. First, it indicates a particular 554 traffic parameter table. An example of such a table is 555 mplsTrafficParamTable. Second, it is used to indicate a specific 556 instance of a traffic parameter entry that is associated with a 557 given in-segment or out-segment entry. In the in-segment and out- 558 segment tables, the trafficParamPtr SHOULD point to the first 559 column of the appropriate conceptual row. 561 11. MPLS Label Switch Router MIB Definitions 563 MPLS-LSR-MIB DEFINITIONS ::= BEGIN 565 IMPORTS 566 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 567 experimental, Integer32, Counter32, Unsigned32, 568 Counter64, Gauge32 569 FROM SNMPv2-SMI 571 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 572 FROM SNMPv2-CONF 574 TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType, 575 RowPointer, TimeStamp 576 FROM SNMPv2-TC 578 InterfaceIndex, InterfaceIndexOrZero 579 FROM IF-MIB 581 AddressFamilyNumbers 582 FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB 584 InetAddressIPv4, InetAddressIPv6, InetAddressType 585 FROM INET-ADDRESS-MIB; 587 mplsLsrMIB MODULE-IDENTITY 588 LAST-UPDATED "200007121200Z" -- 12 July 2000 12:00:00 EST 589 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 590 CONTACT-INFO 591 " Cheenu Srinivasan 592 Postal: Tachion Networks, Inc. 593 Monmouth Park Corporate Center I 594 Building C, 185 Monmouth Parkway 595 West Long Branch, NJ 07764 596 Tel: +1-732-542-7750 x1234 597 Email: cheenu@tachion.com 599 Arun Viswanathan 600 Postal: Force10 Networks, Inc. 601 1440 McCarthy Blvd 602 Milpitas, CA 95035 603 Tel: +1-408-571-3516 604 Email: arun@force10networks.com 606 Thomas D. Nadeau 607 Postal: Cisco Systems, Inc. 608 250 Apollo Drive 609 Chelmsford, MA 01824 610 Tel: +1-978-244-3051 611 Email: tnadeau@cisco.com" 613 DESCRIPTION 614 "This MIB contains managed object definitions for the 615 Multiprotocol Label Switching (MPLS) Router as 616 defined in: Rosen, E., Viswanathan, A., and R. 617 Callon, Multiprotocol Label Switching Architecture, 618 Internet Draft , 619 August 1999." 621 -- Revision history. 622 REVISION 623 "200007121200Z" -- 12 July 2000 12:00:00 EST 624 DESCRIPTION 625 "Seventh draft version. Fix minor compilation errors." 626 REVISION 627 "200007071200Z" -- 07 July 2000 12:00:00 EST 628 DESCRIPTION 629 "Sixth draft version. Made minor typographical corrections 630 noted from WG mailing list during second working group last 631 call." 632 REVISION 633 "200004261200Z" -- 26 April 2000 12:00:00 EST 634 DESCRIPTION 635 "Fifth draft version. Made minor typographical corrections 636 noted from WG mailing list." 637 REVISION 638 "200004211200Z" -- 21 April 2000 12:00:00 EST 639 DESCRIPTION 640 "Fourth draft version. Made corrections from WG Last 641 Call comments." 642 REVISION 643 "200003061200Z" -- 6 March 2000 12:00:00 EST 644 DESCRIPTION 645 "Third draft version." 646 REVISION 647 "200002161200Z" -- 16 February 2000 12:00:00 EST 648 DESCRIPTION 649 "Second draft version." 650 REVISION 651 "199906161200Z" -- 16 June 1999 12:00:00 EST 652 DESCRIPTION 653 "Initial draft version." 654 ::= { experimental 96 } 656 -- Textual Conventions. 658 MplsLSPID ::= TEXTUAL-CONVENTION 659 STATUS current 660 DESCRIPTION 661 "An identifier that is assigned to each LSP and is 662 used to uniquely identify it. This is assigned at 663 the head end of the LSP and can be used by all LSRs 664 to identify this LSP. This value is piggybacked by 665 the signaling protocol when this LSP is signaled 666 within the network. This identifier can then be 667 used at each LSR to identify which labels are being 668 swapped to other labels for this LSP. For IPv4 669 addresses this results in a 6-octet long cookie." 670 SYNTAX OCTET STRING (SIZE (0..31)) 672 -- An MPLS label. 673 MplsLabel ::= TEXTUAL-CONVENTION 674 STATUS current 675 DESCRIPTION 676 "This value represents an MPLS label. Note that the 677 contents of a label field are interpreted in an 678 interface-type specific fashion. For example, the 679 20-bit wide label carried in the MPLS shim header is 680 contained in bits 0-19 and bits 20-31 must be zero. 681 The frame relay label can be either 10 or 23 bits 682 wide depending on the size of the DLCI field and 683 bits 10-31, or 23-31 must be zero, respectively. 684 For an ATM interface, bits 0-15 must be interpreted 685 as the VCI, bits 16-23 as the VPI and bits 24-31 686 must be zero. Note that the permissible label 687 values are also a function of the interface type. 688 For example, the value 3 has special semantics in 689 the control plane for an MPLS shim header label and 690 is not a valid label value in the data path." 691 REFERENCE 692 "1. MPLS Label Stack Encoding, Rosen et al, draft- 693 ietf-mpls-label-encaps-07.txt, March 2000. 694 2. Use of Label Switching on Frame Relay Networks, 695 Conta et al, draft-ietf-mpls-fr-03.txt, Nov. 696 1998. 697 3. MPLS using LDP and ATM VC switching, Davie et al, 698 draft-ietf-mpls-atm-02.txt, April 1999." 699 SYNTAX Unsigned32 (0..4294967295) 701 MplsBitRate ::= TEXTUAL-CONVENTION 702 DISPLAY-HINT "d" 703 STATUS current 704 DESCRIPTION 705 "An estimate of bandwidth in units of 1,000 bits per 706 second. If this object reports a value of 'n' then 707 the rate of the object is somewhere in the range of 708 'n-500' to 'n+499'. For objects which do not vary in 709 bitrate, or for those where no accurate estimation 710 can be made, this object should contain the nominal 711 bitrate." 712 SYNTAX Integer32 (1..2147483647) 714 MplsBurstSize ::= TEXTUAL-CONVENTION 715 DISPLAY-HINT "d" 716 STATUS current 717 DESCRIPTION 718 "The number of octets of MPLS data that the stream 719 may send back-to-back without concern for policing." 720 SYNTAX Integer32 (1..2147483647) 722 MplsObjectOwner ::= TEXTUAL-CONVENTION 723 STATUS current 724 DESCRIPTION 725 "The entity which owns the object in question." 726 SYNTAX INTEGER { 727 other(1), 728 snmp(2), 729 ldp(3), 730 rsvp(4), 731 crldp(5), 732 policyAgent(6), 733 unknown (7) 734 } 736 -- Top level components of this MIB. 738 -- Tables, Scalars 739 mplsLsrObjects OBJECT IDENTIFIER ::= { mplsLsrMIB 1 } 740 -- traps 741 mplsLsrNotifications OBJECT IDENTIFIER ::= { mplsLsrMIB 2 } 742 mplsLsrNotifyPrefix OBJECT IDENTIFIER ::= { mplsLsrNotifications 0 } 743 -- conformance 744 mplsLsrConformance OBJECT IDENTIFIER ::= { mplsLsrMIB 3 } 746 -- MPLS Interface Configuration Table. 748 mplsInterfaceConfTable OBJECT-TYPE 749 SYNTAX SEQUENCE OF MplsInterfaceConfEntry 750 MAX-ACCESS not-accessible 751 STATUS current 752 DESCRIPTION 753 "This table specifies per-interface MPLS capability 754 and associated information." 755 ::= { mplsLsrObjects 1 } 757 mplsInterfaceConfEntry OBJECT-TYPE 758 SYNTAX MplsInterfaceConfEntry 759 MAX-ACCESS not-accessible 760 STATUS current 761 DESCRIPTION 762 "An entry in this table is created by an LSR for 763 every interface capable of supporting MPLS. The 764 entry with index 0 represents the per-platform label 765 space and contains parameters that apply to all 766 interfaces that participate in the per-platform 767 label space. Other entries defined in this table 768 represent additional MPLS interfaces that may 769 participate in either the per-platform or per- 770 interface label spaces, or both. Additional 771 information about label space participation of an 772 interface is provided in the description clause of 773 mplsInterfaceLabelParticipationType." 774 INDEX { mplsInterfaceConfIndex } 775 ::= { mplsInterfaceConfTable 1 } 777 MplsInterfaceConfEntry ::= SEQUENCE { 778 mplsInterfaceConfIndex InterfaceIndexOrZero, 779 mplsInterfaceLabelMinIn MplsLabel, 780 mplsInterfaceLabelMaxIn MplsLabel, 781 mplsInterfaceLabelMinOut MplsLabel, 782 mplsInterfaceLabelMaxOut MplsLabel, 783 mplsInterfaceTotalBandwidth MplsBitRate, 784 mplsInterfaceAvailableBandwidth MplsBitRate, 785 mplsInterfaceLabelParticipationType BITS, 786 mplsInterfaceConfStorageType StorageType 787 } 789 mplsInterfaceConfIndex OBJECT-TYPE 790 SYNTAX InterfaceIndexOrZero 791 MAX-ACCESS not-accessible 792 STATUS current 793 DESCRIPTION 794 "This is a unique index for an entry in the 795 MplsInterfaceConfTable. A non-zero index for an 796 entry indicates the ifIndex for the corresponding 797 interface entry in of the MPLS-layer in the ifTable. 798 Note that the per-platform label space may apply to 799 several interfaces, and therefore the configuration 800 of the per-platform label space interface parameters 801 will apply to all of the interfaces that are 802 participating in the per-platform label space." 803 REFERENCE 804 "RFC 2233 - The Interfaces Group MIB using SMIv2, 805 McCloghrie, K., and F. Kastenholtz, Nov. 1997" 806 ::= { mplsInterfaceConfEntry 1 } 808 mplsInterfaceLabelMinIn OBJECT-TYPE 809 SYNTAX MplsLabel 810 MAX-ACCESS read-only 811 STATUS current 812 DESCRIPTION 813 "This is the minimum value of an MPLS label that this 814 LSR is willing to receive on this interface." 815 ::= { mplsInterfaceConfEntry 2 } 817 mplsInterfaceLabelMaxIn OBJECT-TYPE 818 SYNTAX MplsLabel 819 MAX-ACCESS read-only 820 STATUS current 821 DESCRIPTION 822 "This is the maximum value of an MPLS label that this 823 LSR is willing to receive on this interface." 824 ::= { mplsInterfaceConfEntry 3 } 826 mplsInterfaceLabelMinOut OBJECT-TYPE 827 SYNTAX MplsLabel 828 MAX-ACCESS read-only 829 STATUS current 830 DESCRIPTION 831 "This is the minimum value of an MPLS label that this 832 LSR is willing to send on this interface." 833 ::= { mplsInterfaceConfEntry 4 } 835 mplsInterfaceLabelMaxOut OBJECT-TYPE 836 SYNTAX MplsLabel 837 MAX-ACCESS read-only 838 STATUS current 839 DESCRIPTION 840 "This is the maximum value of an MPLS label that this 841 LSR is willing to send on this interface." 842 ::= { mplsInterfaceConfEntry 5 } 844 mplsInterfaceTotalBandwidth OBJECT-TYPE 845 SYNTAX MplsBitRate 846 MAX-ACCESS read-only 847 STATUS current 848 DESCRIPTION 849 "This value indicates the total amount of usable 850 bandwidth on this interface and is specified in 851 kilobits per second (Kbps). This variable is 852 not applicable when applied to the interface with 853 index 0." 854 ::= { mplsInterfaceConfEntry 6 } 856 mplsInterfaceAvailableBandwidth OBJECT-TYPE 857 SYNTAX MplsBitRate 858 MAX-ACCESS read-only 859 STATUS current 860 DESCRIPTION 861 "This value indicates the total amount of available 862 bandwidth available on this interface and is 863 specified in kilobits per second (Kbps). This 864 value is calculated as the difference between the 865 amount of bandwidth currently in use and that 866 specified in mplsInterfaceTotalBandwidth. This 867 variable is not applicable when applied to the 868 interface with index 0." 869 ::= { mplsInterfaceConfEntry 7 } 871 mplsInterfaceLabelParticipationType OBJECT-TYPE 872 SYNTAX BITS { 873 perPlatform (0), 874 perInterface (1) 875 } 876 MAX-ACCESS read-only 877 STATUS current 878 DESCRIPTION 879 "Either the perPlatform(0) or perInterface(1) bit 880 MUST be set. If the value of the 881 mplsInterfaceConfIndex for this entry is zero, then 882 only the perPlatform(0) bit MUST be set and the 883 perInterface(1) bit is meaningless. If the 884 perInterface(1) bit is set then the value of 885 mplsInterfaceLabelMinIn, mplsInterfaceLabelMaxIn, 886 mplsInterfaceLabelMinOut, and 887 mplsInterfaceLabelMaxOut for this entry reflect the 888 label ranges for this interface. If only the 889 perPlatform(0) bit is set, then the value of 890 mplsInterfaceLabelMinIn, mplsInterfaceLabelMaxIn, 891 mplsInterfaceLabelMinOut, and 892 mplsInterfaceLabelMaxOut for this entry must be 893 identical to the instance of these objects with 894 index 0." 895 REFERENCE 896 "Multiprotocol Label Switching, Rosen et al, draft-ietf-mpls- 897 arch-06.txt, August 1999." 898 ::= { mplsInterfaceConfEntry 8 } 900 mplsInterfaceConfStorageType OBJECT-TYPE 901 SYNTAX StorageType 902 MAX-ACCESS read-create 903 STATUS current 904 DESCRIPTION 905 "The storage type for this entry." 906 ::= { mplsInterfaceConfEntry 9 } 908 -- End of mplsInterfaceConfTable 910 -- MPLS Interface Performance Table. 911 mplsInterfacePerfTable OBJECT-TYPE 912 SYNTAX SEQUENCE OF MplsInterfacePerfEntry 913 MAX-ACCESS not-accessible 914 STATUS current 915 DESCRIPTION 916 "This table provides MPLS performance information on 917 a per-interface basis." 918 ::= { mplsLsrObjects 2 } 920 mplsInterfacePerfEntry OBJECT-TYPE 921 SYNTAX MplsInterfacePerfEntry 922 MAX-ACCESS not-accessible 923 STATUS current 924 DESCRIPTION 925 "An entry in this table is created by the LSR for 926 every interface capable of supporting MPLS. Its is 927 an extension to the mplsInterfaceConfEntry table." 929 AUGMENTS { mplsInterfaceConfEntry } 930 ::= { mplsInterfacePerfTable 1 } 932 MplsInterfacePerfEntry ::= SEQUENCE { 933 -- incoming direction 934 mplsInterfaceInLabelsUsed Gauge32, 935 mplsInterfaceFailedLabelLookup Counter32, 937 -- outgoing direction 938 mplsInterfaceOutLabelsUsed Gauge32, 939 mplsInterfaceOutFragments Counter32 940 } 942 mplsInterfaceInLabelsUsed OBJECT-TYPE 943 SYNTAX Gauge32 944 MAX-ACCESS read-only 945 STATUS current 946 DESCRIPTION 947 "This object counts the number of labels 948 that are in use at this point in time on this 949 interface in the incoming direction. If the interface 950 participates in the per-platform label space only, 951 then this instance of this object MUST be identical 952 with the instance with index 0. If the interface 953 participates in the per-interface label space, then this 954 this instance of this object MUST represent the number of 955 of per-interface labels that are in use at this point in 956 time on this interface." 957 ::= { mplsInterfacePerfEntry 1 } 959 mplsInterfaceFailedLabelLookup OBJECT-TYPE 960 SYNTAX Counter32 961 MAX-ACCESS read-only 962 STATUS current 963 DESCRIPTION 964 "This object counts the number of labeled packets 965 that have been received on this interface and were 966 discarded because there was no matching cross-connect 967 entry. This object MUST count on a per-interface basis 968 regardless of which label space the interface participates 969 in." 970 ::= { mplsInterfacePerfEntry 2 } 972 mplsInterfaceOutLabelsUsed OBJECT-TYPE 973 SYNTAX Gauge32 974 MAX-ACCESS read-only 975 STATUS current 976 DESCRIPTION 977 "This object counts the number of top-most labels in the 978 outgoing label stacks that are in use at this point 979 in time on this interface. This object 980 MUST count on a per-interface basis regardless of 981 which label space the interface participates in." 982 ::= { mplsInterfacePerfEntry 3 } 984 mplsInterfaceOutFragments OBJECT-TYPE 985 SYNTAX Counter32 986 MAX-ACCESS read-only 987 STATUS current 988 DESCRIPTION 989 "This object counts the number of outgoing MPLS 990 packets that required fragmentation before 991 transmission on this interface. This object 992 transmission on this interface. This object 993 MUST count on a per-interface basis regardless of 994 which label space the interface participates in." 995 ::= { mplsInterfacePerfEntry 4 } 997 -- In-segment table. 999 mplsInSegmentTable OBJECT-TYPE 1000 SYNTAX SEQUENCE OF MplsInSegmentEntry 1001 MAX-ACCESS not-accessible 1002 STATUS current 1003 DESCRIPTION 1004 "This table contains a collection of incoming 1005 segments to an LSR." 1006 ::= { mplsLsrObjects 3 } 1008 mplsInSegmentEntry OBJECT-TYPE 1009 SYNTAX MplsInSegmentEntry 1010 MAX-ACCESS not-accessible 1011 STATUS current 1012 DESCRIPTION 1013 "An entry in this table represents one incoming 1014 segment. An entry can be created by a network 1015 administrator or an SNMP agent, or an MPLS signaling 1016 protocol. The creator of the entry is denoted by 1017 mplsInSegmentOwner. An entry in this table is 1018 indexed by the ifIndex of the incoming interface and 1019 the (top) label." 1020 INDEX { mplsInSegmentIfIndex, mplsInSegmentLabel } 1021 ::= { mplsInSegmentTable 1 } 1023 MplsInSegmentEntry ::= SEQUENCE { 1024 mplsInSegmentIfIndex InterfaceIndexOrZero, 1025 mplsInSegmentLabel MplsLabel, 1026 mplsInSegmentNPop Integer32, 1027 mplsInSegmentAddrFamily AddressFamilyNumbers, 1028 mplsInSegmentXCIndex Integer32, 1029 mplsInSegmentOwner MplsObjectOwner, 1030 mplsInSegmentTrafficParamPtr RowPointer, 1031 mplsInSegmentRowStatus RowStatus, 1032 mplsInSegmentStorageType StorageType 1033 } 1035 mplsInSegmentIfIndex OBJECT-TYPE 1036 SYNTAX InterfaceIndexOrZero 1037 MAX-ACCESS accessible-for-notify 1038 STATUS current 1039 DESCRIPTION 1040 "This is a unique index for an entry in the 1041 MplsInSegmentTable. This value represents the 1042 interface index for the incoming MPLS interface. A 1043 value of zero represents an incoming label from the 1044 per-platform label space. In this case, the 1045 mplsInSegmentLabel is interpreted to be an MPLS-type 1046 label." 1047 ::= { mplsInSegmentEntry 1 } 1049 mplsInSegmentLabel OBJECT-TYPE 1050 SYNTAX MplsLabel 1051 MAX-ACCESS accessible-for-notify 1052 STATUS current 1053 DESCRIPTION 1054 "The incoming label for this segment." 1055 ::= { mplsInSegmentEntry 2 } 1057 mplsInSegmentNPop OBJECT-TYPE 1058 SYNTAX Integer32 (1..2147483647) 1059 MAX-ACCESS read-create 1060 STATUS current 1061 DESCRIPTION 1062 "The number of labels to pop from the incoming 1063 packet. Normally only the top label is popped from 1064 the packet and used for all switching decisions for 1065 that packet. Note that technologies which do not 1066 support label popping should set this value to its 1067 default value of 1." 1068 DEFVAL { 1 } 1069 ::= { mplsInSegmentEntry 3 } 1071 mplsInSegmentAddrFamily OBJECT-TYPE 1072 SYNTAX AddressFamilyNumbers 1073 MAX-ACCESS read-create 1074 STATUS current 1075 DESCRIPTION 1076 "The IANA address family [IANAFamily] of the incoming 1077 packet. A value of other(0) indicates that the 1078 family type is either unknown or undefined." 1080 DEFVAL { other } 1081 ::= { mplsInSegmentEntry 4 } 1083 mplsInSegmentXCIndex OBJECT-TYPE 1084 SYNTAX Integer32 (0..2147483647) 1085 MAX-ACCESS read-only 1086 STATUS current 1087 DESCRIPTION 1088 "Index into mplsXCTable which identifies which cross- 1089 connect entry this segment is part of. A value of 1090 zero indicates that this entry is not referred to by 1091 any cross-connect entry. When a cross-connect entry 1092 is created which this in-segment is a part of, this 1093 object is automatically updated to reflect the value 1094 of mplsXCIndex of that cross-connect entry." 1095 DEFVAL { 0 } 1096 ::= { mplsInSegmentEntry 5 } 1098 mplsInSegmentOwner OBJECT-TYPE 1099 SYNTAX MplsObjectOwner 1100 MAX-ACCESS read-create 1101 STATUS current 1102 DESCRIPTION 1103 "Denotes the entity that created and is responsible 1104 for managing this segment." 1105 DEFVAL { unknown } 1106 ::= { mplsInSegmentEntry 6 } 1108 mplsInSegmentTrafficParamPtr OBJECT-TYPE 1109 SYNTAX RowPointer 1110 MAX-ACCESS read-create 1111 STATUS current 1112 DESCRIPTION 1113 "This variable represents a pointer to the traffic 1114 parameter specification for this in-segment. This 1115 value may point at an entry in the 1116 mplsTrafficParamTable to indicate which 1117 mplsTrafficParamEntry is to be assigned to this 1118 segment. This value may optionally point at an 1119 externally defined traffic parameter specification 1120 table. A value of zero-dot-zero indicates best-effort 1121 treatment. By having the same value of this object, 1122 two or more segments can indicate resource sharing." 1123 ::= { mplsInSegmentEntry 7 } 1125 mplsInSegmentRowStatus OBJECT-TYPE 1126 SYNTAX RowStatus 1127 MAX-ACCESS read-create 1128 STATUS current 1129 DESCRIPTION 1130 "This variable is used to create, modify, and/or 1131 delete a row in this table." 1132 ::= { mplsInSegmentEntry 8 } 1134 mplsInSegmentStorageType OBJECT-TYPE 1135 SYNTAX StorageType 1136 MAX-ACCESS read-create 1137 STATUS current 1138 DESCRIPTION 1139 "This variable indicates the storage type for this 1140 object." 1141 ::= { mplsInSegmentEntry 9 } 1143 -- End of mplsInSegmentTable 1145 -- In-segment performance table. 1147 mplsInSegmentPerfTable OBJECT-TYPE 1148 SYNTAX SEQUENCE OF MplsInSegmentPerfEntry 1149 MAX-ACCESS not-accessible 1150 STATUS current 1151 DESCRIPTION 1152 "This table contains statistical information for 1153 incoming MPLS segments to an LSR." 1154 ::= { mplsLsrObjects 4 } 1156 mplsInSegmentPerfEntry OBJECT-TYPE 1157 SYNTAX MplsInSegmentPerfEntry 1158 MAX-ACCESS not-accessible 1159 STATUS current 1160 DESCRIPTION 1161 "An entry in this table contains statistical 1162 information about one incoming segment which was 1163 configured in the mplsInSegmentTable. The counters 1164 in this entry should behave in a manner similar to 1165 that of the interface." 1166 AUGMENTS { mplsInSegmentEntry } 1167 ::= { mplsInSegmentPerfTable 1 } 1169 MplsInSegmentPerfEntry ::= SEQUENCE { 1170 mplsInSegmentOctets Counter32, 1171 mplsInSegmentPackets Counter32, 1172 mplsInSegmentErrors Counter32, 1173 mplsInSegmentDiscards Counter32, 1175 -- high capacity counter 1176 mplsInSegmentHCOctets Counter64, 1178 mplsInSegmentPerfDiscontinuityTime TimeStamp 1179 } 1181 mplsInSegmentOctets OBJECT-TYPE 1182 SYNTAX Counter32 1183 MAX-ACCESS read-only 1184 STATUS current 1185 DESCRIPTION 1186 "This value represents the total number of octets 1187 received by this segment." 1188 ::= { mplsInSegmentPerfEntry 1 } 1190 mplsInSegmentPackets OBJECT-TYPE 1191 SYNTAX Counter32 1192 MAX-ACCESS read-only 1193 STATUS current 1194 DESCRIPTION 1195 "Total number of packets received by this segment." 1196 ::= { mplsInSegmentPerfEntry 2 } 1198 mplsInSegmentErrors OBJECT-TYPE 1199 SYNTAX Counter32 1200 MAX-ACCESS read-only 1201 STATUS current 1202 DESCRIPTION 1203 "The number of errored packets received on this 1204 segment." 1205 ::= { mplsInSegmentPerfEntry 3 } 1207 mplsInSegmentDiscards OBJECT-TYPE 1208 SYNTAX Counter32 1209 MAX-ACCESS read-only 1210 STATUS current 1211 DESCRIPTION 1212 "The number of labeled packets received on this in- 1213 segment, which were chosen to be discarded even 1214 though no errors had been detected to prevent their 1215 being transmitted. One possible reason for 1216 discarding such a labeled packet could be to free up 1217 buffer space." 1218 ::= { mplsInSegmentPerfEntry 4 } 1220 mplsInSegmentHCOctets OBJECT-TYPE 1221 SYNTAX Counter64 1222 MAX-ACCESS read-only 1223 STATUS current 1224 DESCRIPTION 1225 "The total number of octets received. This is the 64 1226 bit version of mplsInSegmentOctets." 1227 ::= { mplsInSegmentPerfEntry 5 } 1229 mplsInSegmentPerfDiscontinuityTime OBJECT-TYPE 1230 SYNTAX TimeStamp 1231 MAX-ACCESS read-only 1232 STATUS current 1233 DESCRIPTION 1234 "The value of sysUpTime on the most recent occasion at 1235 which any one or more of this segment's Counter32 or 1236 Counter64 suffered a discontinuity. If no such 1237 discontinuities have occurred since the last re- 1238 initialization of the local management subsystem, then 1239 this object contains a zero value." 1240 ::= { mplsInSegmentPerfEntry 6 } 1242 -- End of mplsInSegmentPerfTable. 1244 -- Out-segment table. 1246 mplsOutSegmentIndexNext OBJECT-TYPE 1247 SYNTAX Integer32 (0..2147483647) 1248 MAX-ACCESS read-only 1249 STATUS current 1250 DESCRIPTION 1251 "This object contains the next appropriate value to 1252 be used for mplsOutSegmentIndex when creating 1253 entries in the mplsOutSegmentTable. If the number 1254 of unassigned entries is exhausted, this object will 1255 take on the value of 0. To obtain the 1256 mplsOutSegmentIndex value for a new entry, the 1257 manager must first issue a management protocol 1258 retrieval operation to obtain the current value of 1259 this object. The agent should modify the value to 1260 reflect the next unassigned index after each 1261 retrieval operation. After a manager retrieves a 1262 value the agent will determine through its local 1263 policy when this index value will be made available 1264 for reuse." 1265 ::= { mplsLsrObjects 5 } 1267 mplsOutSegmentTable OBJECT-TYPE 1268 SYNTAX SEQUENCE OF MplsOutSegmentEntry 1269 MAX-ACCESS not-accessible 1270 STATUS current 1271 DESCRIPTION 1272 "This table contains a representation of the outgoing 1273 segments from an LSR." 1274 ::= { mplsLsrObjects 6 } 1276 mplsOutSegmentEntry OBJECT-TYPE 1277 SYNTAX MplsOutSegmentEntry 1278 MAX-ACCESS not-accessible 1279 STATUS current 1280 DESCRIPTION 1281 "An entry in this table represents one outgoing 1282 segment. An entry can be created by a network 1283 administrator or an SNMP agent, or an MPLS signaling 1284 protocol. The object mplsOutSegmentOwner indicates 1285 the creator of this entry." 1286 INDEX { mplsOutSegmentIndex } 1287 ::= { mplsOutSegmentTable 1 } 1289 MplsOutSegmentEntry ::= SEQUENCE { 1290 mplsOutSegmentIndex Integer32, 1291 mplsOutSegmentIfIndex InterfaceIndex, 1292 mplsOutSegmentPushTopLabel TruthValue, 1293 mplsOutSegmentTopLabel MplsLabel, 1294 mplsOutSegmentNextHopIpAddrType InetAddressType, 1295 mplsOutSegmentNextHopIpv4Addr InetAddressIPv4, 1296 mplsOutSegmentNextHopIpv6Addr InetAddressIPv6, 1297 mplsOutSegmentXCIndex Integer32, 1298 mplsOutSegmentOwner MplsObjectOwner, 1299 mplsOutSegmentTrafficParamPtr RowPointer, 1300 mplsOutSegmentRowStatus RowStatus, 1301 mplsOutSegmentStorageType StorageType 1302 } 1304 mplsOutSegmentIndex OBJECT-TYPE 1305 SYNTAX Integer32(0..2147483647) 1306 MAX-ACCESS accessible-for-notify 1307 STATUS current 1308 DESCRIPTION 1309 "This value contains a unique index for this row. 1310 While a value of 0 is not valid as an index for this 1311 row it can be supplied as a valid value to index 1312 mplsXCTable to access entries for which no out- 1313 segment has been configured." 1314 ::= { mplsOutSegmentEntry 1 } 1316 mplsOutSegmentIfIndex OBJECT-TYPE 1317 SYNTAX InterfaceIndex 1318 MAX-ACCESS read-create 1319 STATUS current 1320 DESCRIPTION 1321 "This value contains the interface index of the 1322 outgoing interface." 1323 ::= { mplsOutSegmentEntry 2 } 1325 mplsOutSegmentPushTopLabel OBJECT-TYPE 1326 SYNTAX TruthValue 1327 MAX-ACCESS read-create 1328 STATUS current 1329 DESCRIPTION 1330 "This value indicates whether or not a top label 1331 should be pushed onto the outgoing packet's label 1332 stack. The value of this variable must be set to 1333 true if the outgoing interface does not support pop- 1334 and-go (for example an ATM interface) or if it is a 1335 tunnel origination. Note that it is considered an 1336 error in the case that mplsOutSegmentPushTopLabel is 1337 set to false, but the cross-connect entry which 1338 refers to this out-segment has a non-zero 1339 mplsLabelStackIndex. The LSR MUST ensure that this 1340 situation does not happen " 1341 ::= { mplsOutSegmentEntry 3 } 1343 mplsOutSegmentTopLabel OBJECT-TYPE 1344 SYNTAX MplsLabel 1345 MAX-ACCESS read-create 1346 STATUS current 1347 DESCRIPTION 1348 "If mplsOutSegmentPushTopLabel is true then this 1349 represents the label that should be pushed onto the 1350 top of the outgoing packet's label stack." 1351 ::= { mplsOutSegmentEntry 4 } 1353 mplsOutSegmentNextHopIpAddrType OBJECT-TYPE 1354 SYNTAX InetAddressType 1355 MAX-ACCESS read-create 1356 STATUS current 1357 DESCRIPTION 1358 "Indicates whether the next hop address is IPv4 or 1359 IPv6. Note that a value of unknown (0) is valid 1360 only when the outgoing interface is of type point-to- 1361 point." 1362 DEFVAL { unknown } 1363 ::= { mplsOutSegmentEntry 5 } 1365 mplsOutSegmentNextHopIpv4Addr OBJECT-TYPE 1366 SYNTAX InetAddressIPv4 1367 MAX-ACCESS read-create 1368 STATUS current 1369 DESCRIPTION 1370 "IPv4 Address of the next hop. Its value is 1371 significant only when 1372 mplsOutSegmentNextHopIpAddrType is ipV4 (1), 1373 otherwise it should return a value of 0." 1374 ::= { mplsOutSegmentEntry 6 } 1376 mplsOutSegmentNextHopIpv6Addr OBJECT-TYPE 1377 SYNTAX InetAddressIPv6 1378 MAX-ACCESS read-create 1379 STATUS current 1380 DESCRIPTION 1381 "IPv6 address of the next hop. Its value is 1382 significant only when 1383 mplsOutSegmentNextHopIpAddrType is ipV6 (2), 1384 otherwise it should return a value of 0." 1385 ::= { mplsOutSegmentEntry 7 } 1387 mplsOutSegmentXCIndex OBJECT-TYPE 1388 SYNTAX Integer32 (0..2147483647) 1389 MAX-ACCESS read-only 1390 STATUS current 1391 DESCRIPTION 1392 "Index into mplsXCTable which identifies which cross- 1393 connect entry this segment is part of. A value of 1394 zero indicates that this entry is not referred to by 1395 any cross-connect entry. When a cross-connect entry 1396 is created which this out-segment is a part of, this 1397 object is automatically updated to reflect the value 1398 of mplsXCIndex of that cross-connect entry." 1399 DEFVAL { 0 } 1400 ::= { mplsOutSegmentEntry 8 } 1402 mplsOutSegmentOwner OBJECT-TYPE 1403 SYNTAX MplsObjectOwner 1404 MAX-ACCESS read-create 1405 STATUS current 1406 DESCRIPTION 1407 "Denotes the entity which created and is responsible 1408 for managing this segment." 1409 DEFVAL { unknown } 1410 ::= { mplsOutSegmentEntry 9 } 1412 mplsOutSegmentTrafficParamPtr OBJECT-TYPE 1413 SYNTAX RowPointer 1414 MAX-ACCESS read-create 1415 STATUS current 1416 DESCRIPTION 1417 "This variable represents a pointer to the traffic 1418 parameter specification for this out-segment. This 1419 value may point at an entry in the 1420 mplsTrafficParamTable to indicate which 1421 mplsTrafficParamEntry is to be assigned to this 1422 segment. This value may optionally point at an 1423 externally defined traffic parameter specification 1424 table. A value of zero-dot-zero indicates best- 1425 effort treatment. By having the same value of this 1426 object, two or more segments can indicate resource 1427 sharing." 1429 ::= { mplsOutSegmentEntry 10 } 1431 mplsOutSegmentRowStatus OBJECT-TYPE 1432 SYNTAX RowStatus 1433 MAX-ACCESS read-create 1434 STATUS current 1435 DESCRIPTION 1436 "For creating, modifying, and deleting this row." 1437 ::= { mplsOutSegmentEntry 11 } 1439 mplsOutSegmentStorageType OBJECT-TYPE 1440 SYNTAX StorageType 1441 MAX-ACCESS read-create 1442 STATUS current 1443 DESCRIPTION 1444 "This variable indicates the storage type for this 1445 object." 1446 ::= { mplsOutSegmentEntry 12 } 1448 -- End of mplsOutSegmentTable 1450 -- Out-segment performance table. 1452 mplsOutSegmentPerfTable OBJECT-TYPE 1453 SYNTAX SEQUENCE OF MplsOutSegmentPerfEntry 1454 MAX-ACCESS not-accessible 1455 STATUS current 1456 DESCRIPTION 1457 "This table contains statistical information about 1458 outgoing segments from an LSR. The counters in this 1459 entry should behave in a manner similar to that of 1460 the interface." 1461 ::= { mplsLsrObjects 7 } 1463 mplsOutSegmentPerfEntry OBJECT-TYPE 1464 SYNTAX MplsOutSegmentPerfEntry 1465 MAX-ACCESS not-accessible 1466 STATUS current 1467 DESCRIPTION 1468 "An entry in this table contains statistical 1469 information about one outgoing segment configured in 1470 mplsOutSegmentTable." 1471 AUGMENTS { mplsOutSegmentEntry } 1472 ::= { mplsOutSegmentPerfTable 1 } 1474 MplsOutSegmentPerfEntry ::= SEQUENCE { 1475 mplsOutSegmentOctets Counter32, 1476 mplsOutSegmentPackets Counter32, 1477 mplsOutSegmentErrors Counter32, 1478 mplsOutSegmentDiscards Counter32, 1480 -- HC counter 1481 mplsOutSegmentHCOctets Counter64, 1483 mplsOutSegmentPerfDiscontinuityTime TimeStamp 1484 } 1486 mplsOutSegmentOctets OBJECT-TYPE 1487 SYNTAX Counter32 1488 MAX-ACCESS read-only 1489 STATUS current 1490 DESCRIPTION 1491 "This value contains the total number of octets sent 1492 on this segment." 1493 ::= { mplsOutSegmentPerfEntry 1 } 1495 mplsOutSegmentPackets OBJECT-TYPE 1496 SYNTAX Counter32 1497 MAX-ACCESS read-only 1498 STATUS current 1499 DESCRIPTION 1500 "This value contains the total number of packets sent 1501 on this segment." 1502 ::= { mplsOutSegmentPerfEntry 2 } 1504 mplsOutSegmentErrors OBJECT-TYPE 1505 SYNTAX Counter32 1506 MAX-ACCESS read-only 1507 STATUS current 1508 DESCRIPTION 1509 "Number of packets that could not be sent due to 1510 errors on this segment." 1511 ::= { mplsOutSegmentPerfEntry 3 } 1513 mplsOutSegmentDiscards OBJECT-TYPE 1514 SYNTAX Counter32 1515 MAX-ACCESS read-only 1516 STATUS current 1517 DESCRIPTION 1518 "The number of labeled packets received on this out- 1519 segment, which were chosen to be discarded even 1520 though no errors had been detected to prevent their 1521 being transmitted. One possible reason for 1522 discarding such a labeled packet could be to free up 1523 buffer space." 1524 ::= { mplsOutSegmentPerfEntry 4 } 1526 mplsOutSegmentHCOctets OBJECT-TYPE 1527 SYNTAX Counter64 1528 MAX-ACCESS read-only 1529 STATUS current 1530 DESCRIPTION 1531 "Total number of octets sent. This is the 64 bit 1532 version of mplsOutSegmentOctets." 1533 ::= { mplsOutSegmentPerfEntry 5 } 1535 mplsOutSegmentPerfDiscontinuityTime OBJECT-TYPE 1536 SYNTAX TimeStamp 1537 MAX-ACCESS read-only 1538 STATUS current 1539 DESCRIPTION 1540 "The value of sysUpTime on the most recent occasion at 1541 which any one or more of this segment's Counter32 or 1542 Counter64 suffered a discontinuity. If no such 1543 discontinuities have occurred since the last re- 1544 initialization of the local management subsystem, then 1545 this object contains a zero value." 1546 ::= { mplsOutSegmentPerfEntry 6 } 1548 -- End of mplsOutSegmentPerfTable. 1550 -- Cross-connect table. 1552 mplsXCIndexNext OBJECT-TYPE 1553 SYNTAX Integer32 (0..2147483647) 1554 MAX-ACCESS read-only 1555 STATUS current 1556 DESCRIPTION 1557 "This object contains an appropriate value to be used 1558 for mplsXCIndex when creating entries in the 1559 mplsXCTable. The value 0 indicates that no 1560 unassigned entries are available. To obtain the 1561 value of mplsXCIndex for a new entry in the 1562 mplsXCTable, the manager issues a management 1563 protocol retrieval operation to obtain the current 1564 value of mplsXCIndex. After each retrieval 1565 operation, the agent should modify the value to 1566 reflect the next unassigned index. After a manager 1567 retrieves a value the agent will determine through 1568 its local policy when this index value will be made 1569 available for reuse." 1570 ::= { mplsLsrObjects 8 } 1572 mplsXCTable OBJECT-TYPE 1573 SYNTAX SEQUENCE OF MplsXCEntry 1574 MAX-ACCESS not-accessible 1575 STATUS current 1576 DESCRIPTION 1577 "This table specifies information for switching 1578 between LSP segments. It supports point-to-point, 1579 point-to-multipoint and multipoint-to-point 1580 connections. mplsLabelStackTable specifies the 1581 label stack information for a cross-connect LSR and 1582 is referred to from mplsXCTable." 1583 ::= { mplsLsrObjects 9 } 1585 mplsXCEntry OBJECT-TYPE 1586 SYNTAX MplsXCEntry 1587 MAX-ACCESS not-accessible 1588 STATUS current 1589 DESCRIPTION 1590 "A row in this table represents one cross-connect 1591 entry. The following objects index it: 1593 - cross-connect index mplsXCIndex that uniquely 1594 identifies a group of cross-connect entries 1595 - interface index of the in-segment, 1596 mplsInSegmentIfIndex 1597 - incoming label(s), mplsInSegmentLabel 1598 - out-segment index, mplsOutSegmentIndex 1600 Originating LSPs: 1601 These are represented by using the special 1602 combination of values mplsInSegmentIfIndex=0 and 1603 mplsInSegmentLabel=0 as indexes. In this case the 1604 mplsOutSegmentIndex MUST be non-zero. 1606 Terminating LSPs: 1607 These are represented by using the special value 1608 mplsOutSegmentIndex=0 as index. 1610 Special labels: 1611 Entries indexed by reserved MPLS label values 0 1612 through 15 imply terminating LSPs and MUST have 1613 mplsOutSegmentIfIndex = 0. Note that situations 1614 where LSPs are terminated with incoming label equal 1615 to 0, should have mplsInSegmentIfIndex = 0 as well, 1616 but can be distinguished from originating LSPs 1617 because the mplsOutSegmentIfIndex = 0. The 1618 mplsOutSegmentIfIndex MUST only be set to 0 in 1619 cases of terminating LSPs. 1621 An entry can be created by a network administrator 1622 or by an SNMP agent as instructed by an MPLS 1623 signaling protocol." 1624 INDEX { mplsXCIndex, mplsInSegmentIfIndex, 1625 mplsInSegmentLabel, 1626 mplsOutSegmentIndex } 1628 ::= { mplsXCTable 1 } 1630 MplsXCEntry ::= SEQUENCE { 1631 mplsXCIndex Integer32, 1632 mplsXCLspId MplsLSPID, 1633 mplsXCLabelStackIndex Integer32, 1634 mplsXCIsPersistent TruthValue, 1635 mplsXCOwner MplsObjectOwner, 1636 mplsXCRowStatus RowStatus, 1637 mplsXCStorageType StorageType, 1638 mplsXCAdminStatus INTEGER, 1639 mplsXCOperStatus INTEGER 1640 } 1642 mplsXCIndex OBJECT-TYPE 1643 SYNTAX Integer32 (1..2147483647) 1644 MAX-ACCESS accessible-for-notify 1645 STATUS current 1646 DESCRIPTION 1647 "Primary index for the conceptual row identifying 1648 a group of cross-connect segments." 1649 ::= { mplsXCEntry 1 } 1651 mplsXCLspId OBJECT-TYPE 1652 SYNTAX MplsLSPID 1653 MAX-ACCESS read-create 1654 STATUS current 1655 DESCRIPTION 1656 "This value identifies the label switched path that 1657 this cross-connect entry belongs to." 1658 ::= { mplsXCEntry 2 } 1660 mplsXCLabelStackIndex OBJECT-TYPE 1661 SYNTAX Integer32 (0..2147483647) 1662 MAX-ACCESS read-create 1663 STATUS current 1664 DESCRIPTION 1665 "Primary index into mplsLabelStackTable identifying a 1666 stack of labels to be pushed beneath the top label. 1667 Note that the top label identified by the out- 1668 segment ensures that all the components of a 1669 multipoint-to-point connection have the same 1670 outgoing label. A value of 0 indicates that no 1671 labels are to be stacked beneath the top label." 1672 ::= { mplsXCEntry 3 } 1674 mplsXCIsPersistent OBJECT-TYPE 1675 SYNTAX TruthValue 1676 MAX-ACCESS read-create 1677 STATUS current 1678 DESCRIPTION 1679 "Denotes whether or not this cross-connect entry and 1680 associated in- and out-segments should be restored 1681 automatically after failures. This value MUST be 1682 set to false in cases where this cross-connect entry 1683 was created by a signaling protocol." 1684 DEFVAL { false } 1685 ::= { mplsXCEntry 4 } 1687 mplsXCOwner OBJECT-TYPE 1688 SYNTAX MplsObjectOwner 1689 MAX-ACCESS read-create 1690 STATUS current 1691 DESCRIPTION 1692 "Denotes the entity that created and is responsible 1693 for managing this cross-connect." 1694 ::= { mplsXCEntry 5 } 1696 mplsXCRowStatus OBJECT-TYPE 1697 SYNTAX RowStatus 1698 MAX-ACCESS read-create 1699 STATUS current 1700 DESCRIPTION 1701 "For creating, modifying, and deleting this row." 1702 ::= { mplsXCEntry 6 } 1704 mplsXCStorageType OBJECT-TYPE 1705 SYNTAX StorageType 1706 MAX-ACCESS read-create 1707 STATUS current 1708 DESCRIPTION 1709 "Defines the storage type for this object." 1710 ::= { mplsXCEntry 7 } 1712 mplsXCAdminStatus OBJECT-TYPE 1713 SYNTAX INTEGER { 1714 up(1), -- ready to pass packets 1715 down(2), 1716 testing(3) -- in some test mode 1717 } 1718 MAX-ACCESS read-create 1719 STATUS current 1720 DESCRIPTION 1721 "The desired operational status of this segment." 1722 ::= { mplsXCEntry 8 } 1724 mplsXCOperStatus OBJECT-TYPE 1725 SYNTAX INTEGER { 1726 up(1), -- ready to pass packets 1727 down(2), 1728 testing(3), -- in some test mode 1729 unknown(4), -- status cannot be determined 1730 -- for some reason. 1731 dormant(5), 1732 notPresent(6), -- some component is missing 1733 lowerLayerDown(7) -- down due to the state of 1734 -- lower layer interfaces 1735 } 1736 MAX-ACCESS read-only 1737 STATUS current 1738 DESCRIPTION 1739 "The actual operational status of this cross- 1740 connect." 1741 ::= { mplsXCEntry 9 } 1743 -- End of mplsXCTable 1745 -- Label stack table. 1746 mplsMaxLabelStackDepth OBJECT-TYPE 1747 SYNTAX Integer32 (1..2147483647) 1748 MAX-ACCESS read-only 1749 STATUS current 1750 DESCRIPTION 1751 "The maximum stack depth supported by this LSR." 1752 ::= { mplsLsrObjects 10 } 1754 mplsLabelStackIndexNext OBJECT-TYPE 1755 SYNTAX Integer32 (0..2147483647) 1756 MAX-ACCESS read-only 1757 STATUS current 1758 DESCRIPTION 1759 "This object contains an appropriate value to be used 1760 for mplsLabelStackIndex when creating entries in the 1761 mplsLabelStackTable. The value 0 indicates that no 1762 unassigned entries are available. To obtain an 1763 mplsLabelStackIndex value for a new entry, the 1764 manager issues a management protocol retrieval 1765 operation to obtain the current value of this 1766 object. After each retrieval operation, the agent 1767 should modify the value to reflect the next 1768 unassigned index. After a manager retrieves a value 1769 the agent will determine through its local policy 1770 when this index value will be made available for 1771 reuse." 1772 ::= { mplsLsrObjects 11 } 1774 mplsLabelStackTable OBJECT-TYPE 1775 SYNTAX SEQUENCE OF MplsLabelStackEntry 1776 MAX-ACCESS not-accessible 1777 STATUS current 1778 DESCRIPTION 1779 "This table specifies the label stack to be pushed 1780 onto a packet, beneath the top label. Entries into 1781 this table are referred to from mplsXCTable." 1782 ::= { mplsLsrObjects 12 } 1784 mplsLabelStackEntry OBJECT-TYPE 1785 SYNTAX MplsLabelStackEntry 1786 MAX-ACCESS not-accessible 1787 STATUS current 1788 DESCRIPTION 1789 "An entry in this table represents one label which is 1790 to be pushed onto an outgoing packet, beneath the 1791 top label. An entry can be created by a network 1792 administrator or by an SNMP agent as instructed by 1793 an MPLS signaling protocol." 1794 INDEX { mplsLabelStackIndex, mplsLabelStackLabelIndex } 1795 ::= { mplsLabelStackTable 1 } 1797 MplsLabelStackEntry ::= SEQUENCE { 1798 mplsLabelStackIndex Integer32, 1799 mplsLabelStackLabelIndex Integer32, 1800 mplsLabelStackLabel MplsLabel, 1801 mplsLabelStackRowStatus RowStatus, 1802 mplsLabelStackStorageType StorageType 1803 } 1805 mplsLabelStackIndex OBJECT-TYPE 1806 SYNTAX Integer32 (1..2147483647) 1807 MAX-ACCESS not-accessible 1808 STATUS current 1809 DESCRIPTION 1810 "Primary index for this row identifying a stack of 1811 labels to be pushed on an outgoing packet, beneath 1812 the top label." 1813 ::= { mplsLabelStackEntry 1 } 1815 mplsLabelStackLabelIndex OBJECT-TYPE 1816 SYNTAX Integer32 (1..2147483647) 1817 MAX-ACCESS not-accessible 1818 STATUS current 1819 DESCRIPTION 1820 "Secondary index for this row identifying one label 1821 of the stack. Note that an entry with a smaller 1822 mplsLabelStackLabelIndex would refer to a label 1823 higher up the label stack and would be popped at a 1824 downstream LSR before a label represented by a 1825 higher mplsLabelStackLabelIndex at a downstream 1826 LSR." 1828 ::= { mplsLabelStackEntry 2 } 1830 mplsLabelStackLabel OBJECT-TYPE 1831 SYNTAX MplsLabel 1832 MAX-ACCESS read-create 1833 STATUS current 1834 DESCRIPTION 1835 "The label to pushed." 1836 ::= { mplsLabelStackEntry 3 } 1838 mplsLabelStackRowStatus OBJECT-TYPE 1839 SYNTAX RowStatus 1840 MAX-ACCESS read-create 1841 STATUS current 1842 DESCRIPTION 1843 "For creating, modifying, and deleting this row." 1844 ::= { mplsLabelStackEntry 4 } 1846 mplsLabelStackStorageType OBJECT-TYPE 1847 SYNTAX StorageType 1848 MAX-ACCESS read-create 1849 STATUS current 1850 DESCRIPTION 1851 "Defines the storage type for this object." 1852 ::= { mplsLabelStackEntry 5 } 1854 -- End of mplsLabelStackTable 1856 -- Traffic Parameter table. 1858 mplsTrafficParamIndexNext OBJECT-TYPE 1859 SYNTAX Integer32 (0..2147483647) 1860 MAX-ACCESS read-only 1861 STATUS current 1862 DESCRIPTION 1863 "This object contains an appropriate value which will 1864 be used for mplsTrafficParamIndex when creating 1865 entries in the mplsTrafficParamTable. The value 0 1866 indicates that no unassigned entries are available. 1867 To obtain the mplsTrafficParamIndex value for a new 1868 entry, the manager issues a management protocol 1869 retrieval operation to obtain the current value of 1870 this object. After each retrieval operation, the 1871 agent should modify the value to reflect the next 1872 unassigned index. After a manager retrieves a value 1873 the agent will determine through its local policy 1874 when this index value will be made available for 1875 reuse." 1876 ::= { mplsLsrObjects 13 } 1878 mplsTrafficParamTable OBJECT-TYPE 1879 SYNTAX SEQUENCE OF MplsTrafficParamEntry 1880 MAX-ACCESS not-accessible 1881 STATUS current 1882 DESCRIPTION 1883 "This table specifies the Traffic Parameter objects 1884 for in and out-segments." 1885 ::= { mplsLsrObjects 14 } 1887 mplsTrafficParamEntry OBJECT-TYPE 1888 SYNTAX MplsTrafficParamEntry 1889 MAX-ACCESS not-accessible 1890 STATUS current 1891 DESCRIPTION 1892 "An entry in this table represents the TrafficParam 1893 objects for one or more in or out segments. A 1894 single entry can be pointed to by multiple segments 1895 indicating resource sharing." 1896 INDEX { mplsTrafficParamIndex } 1897 ::= { mplsTrafficParamTable 1 } 1899 MplsTrafficParamEntry ::= SEQUENCE { 1900 mplsTrafficParamIndex Integer32, 1901 mplsTrafficParamMaxRate MplsBitRate, 1902 mplsTrafficParamMeanRate MplsBitRate, 1903 mplsTrafficParamMaxBurstSize MplsBurstSize, 1904 mplsTrafficParamRowStatus RowStatus, 1905 mplsTrafficParamStorageType StorageType 1906 } 1908 mplsTrafficParamIndex OBJECT-TYPE 1909 SYNTAX Integer32 (1..2147483647) 1910 MAX-ACCESS not-accessible 1911 STATUS current 1912 DESCRIPTION 1913 "Uniquely identifies this row of the table. Note 1914 that zero represents an invalid index." 1915 ::= { mplsTrafficParamEntry 1 } 1917 mplsTrafficParamMaxRate OBJECT-TYPE 1918 SYNTAX MplsBitRate 1919 UNITS "kilobits per second" 1920 MAX-ACCESS read-create 1921 STATUS current 1922 DESCRIPTION 1923 "Maximum rate in kilobits/second." 1924 ::= { mplsTrafficParamEntry 2 } 1926 mplsTrafficParamMeanRate OBJECT-TYPE 1927 SYNTAX MplsBitRate 1928 UNITS "kilobits per second" 1929 MAX-ACCESS read-create 1930 STATUS current 1931 DESCRIPTION 1932 "Mean rate in kilobits/second." 1933 ::= { mplsTrafficParamEntry 3 } 1935 mplsTrafficParamMaxBurstSize OBJECT-TYPE 1936 SYNTAX MplsBurstSize 1937 UNITS "bytes" 1938 MAX-ACCESS read-create 1939 STATUS current 1940 DESCRIPTION 1941 "Maximum burst size in bytes." 1942 ::= { mplsTrafficParamEntry 4 } 1944 mplsTrafficParamRowStatus OBJECT-TYPE 1945 SYNTAX RowStatus 1946 MAX-ACCESS read-create 1947 STATUS current 1948 DESCRIPTION 1949 "For creating, modifying, and deleting this row." 1950 ::= { mplsTrafficParamEntry 5 } 1952 mplsTrafficParamStorageType OBJECT-TYPE 1953 SYNTAX StorageType 1954 MAX-ACCESS read-create 1955 STATUS current 1956 DESCRIPTION 1957 "The storage type for this object." 1958 ::= { mplsTrafficParamEntry 6 } 1960 -- End of mplsTrafficParamTable 1962 -- Notification Configuration 1964 mplsXCTrapEnable OBJECT-TYPE 1965 SYNTAX TruthValue 1966 MAX-ACCESS read-write 1967 STATUS current 1968 DESCRIPTION 1969 "If this object is true, then it enables the 1970 generation of mplsXCUp and mplsXCDown traps, 1971 otherwise these traps are not emitted." 1972 DEFVAL { false } 1973 ::= { mplsLsrObjects 15 } 1975 -- Cross-connect. 1977 mplsXCUp NOTIFICATION-TYPE 1978 OBJECTS { mplsXCIndex, 1979 mplsInSegmentIfIndex, 1980 mplsInSegmentLabel, 1981 mplsOutSegmentIndex, 1982 mplsXCAdminStatus, 1983 mplsXCOperStatus } 1984 STATUS current 1985 DESCRIPTION 1986 "This notification is generated when a 1987 mplsXCOperStatus object for one of the configured 1988 cross-connect entries is about to leave the down 1989 state and transition into some other state (but not 1990 into the notPresent state). This other state is 1991 indicated by the included value of 1992 mplsXCOperStatus." 1993 ::= { mplsLsrNotifyPrefix 1 } 1995 mplsXCDown NOTIFICATION-TYPE 1996 OBJECTS { mplsXCIndex, 1997 mplsInSegmentIfIndex, 1998 mplsInSegmentLabel, 1999 mplsOutSegmentIndex, 2000 mplsXCAdminStatus, 2001 mplsXCOperStatus } 2002 STATUS current 2003 DESCRIPTION 2004 "This notification is generated when a 2005 mplsXCOperStatus object for one of the configured 2006 cross-connect entries is about to enter the down 2007 state from some other state (but not from the 2008 notPresent state). This other state is indicated by 2009 the included value of mplsXCOperStatus." 2010 ::= { mplsLsrNotifyPrefix 2 } 2012 -- End of notifications. 2014 -- Module compliance. 2016 mplsLsrGroups 2017 OBJECT IDENTIFIER ::= { mplsLsrConformance 1 } 2019 mplsLsrCompliances 2020 OBJECT IDENTIFIER ::= { mplsLsrConformance 2 } 2022 mplsLsrModuleCompliance MODULE-COMPLIANCE 2023 STATUS current 2024 DESCRIPTION 2025 "Compliance statement for agents that support the 2026 MPLS LSR MIB." 2028 MODULE -- this module 2030 -- The mandatory groups have to be implemented 2031 -- by all LSRs. However, they may all be supported 2032 -- as read-only objects in the case where manual 2033 -- configuration is unsupported. 2035 MANDATORY-GROUPS { mplsInSegmentGroup, 2036 mplsOutSegmentGroup, 2037 mplsXCGroup, 2038 mplsInterfaceGroup, 2039 mplsPerfGroup, 2040 mplsSegmentDiscontinuityGroup } 2042 GROUP mplsHCInSegmentPerfGroup 2043 DESCRIPTION 2044 "This group is mandatory for those in-segment 2045 entries for which the object 2046 mplsInSegmentOutOctets wraps around too 2047 quickly." 2049 GROUP mplsHCOutSegmentPerfGroup 2050 DESCRIPTION 2051 "This group is mandatory for those out-segment 2052 entries for which the object 2053 mplsOutSegmentOctets wraps around too quickly." 2055 GROUP mplsTrafficParamGroup 2056 DESCRIPTION 2057 "This group is mandatory for those LSRs that 2058 support QoS resource reservation." 2060 -- Depending on whether the device implements 2061 -- persistent cross-connects or not one of the 2062 -- following two groups is mandatory. 2064 GROUP mplsXCIsPersistentGroup 2065 DESCRIPTION 2066 "This group is mandatory for devices which 2067 support persistent cross-connects. The 2068 following constraints apply: mplsXCIsPersistent 2069 must at least be read-only returning true(2)." 2071 GROUP mplsXCIsNotPersistentGroup 2072 DESCRIPTION 2073 "This group is mandatory for devices which 2074 support non-persistent cross-connects. The 2075 following constraints apply: mplsXCIsPersistent 2076 must at least be read-only returning false(1)." 2078 -- mplsInterfaceConfTable 2080 OBJECT mplsInterfaceConfStorageType 2081 SYNTAX INTEGER { other(1) } 2082 MIN-ACCESS read-only 2083 DESCRIPTION 2084 "Only other(1) needs to be supported." 2086 -- mplsInSegmentTable 2088 OBJECT mplsInSegmentXCIndex 2089 DESCRIPTION 2090 "Write access is not required." 2092 OBJECT mplsInSegmentNPop 2093 MIN-ACCESS read-only 2094 DESCRIPTION 2095 "Write access if not required. This object 2096 should be set to 1 if it is read-only." 2098 OBJECT mplsInSegmentAddrFamily 2099 DESCRIPTION 2100 "Write access is not required. A , 2445 August 1999. 2447 [MPLSFW] Callon, R., Doolan, P., Feldman, N., Fredette, A., 2448 Swallow, G., and A. Viswanathan, "A Framework for 2449 Multiprotocol Label Switching", Internet Draft 2450 , September 1999. 2452 [LblStk] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D., 2453 Federokow, G., Li, T., and A. Conta, "MPLS Label 2454 Stack Encoding", Internet Draft , September 1999. 2457 [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", 2458 RFC 1700, October 1994. See also: 2459 http://www.isi.edu/in-notes/iana/assignments/smi- 2460 numbers 2462 [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS 2463 FAMILY NUMBERS,(http://www.isi.edu/in- 2464 notes/iana/assignements/address-family-numbers), 2465 for MIB see: 2466 ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib 2468 [SNMPArch] Harrington, D., Presuhn, R., and B. Wijnen, "An 2469 Architecture for Describing SNMP Management 2470 Frameworks", RFC 2271, January 1998. 2472 [SMIv1] Rose, M., and K. McCloghrie, "Structure and 2473 Identification of Management Information for TCP/IP- 2474 based Internets", RFC 1155, May 1990. 2476 [SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB 2477 Definitions", RFC 1212, March 1991. 2479 [SNMPv1Traps] M. Rose, "A Convention for Defining Traps for use 2480 with the SNMP", RFC 1215, March 1991. 2482 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2483 "Message Processing and Dispatching for the Simple 2484 Network Management Protocol (SNMP)", RFC 2572, 2485 April 1999. 2487 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 2488 Model (USM) for version 3 of the Simple Network 2489 Management Protocol (SNMPv3)", RFC 2574, April 2490 1999. 2492 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. 2493 Waldbusser, "Protocol Operations for Version 2 of 2494 the Simple Network Management Protocol (SNMPv2)", 2495 RFC 1905, January 1996. 2497 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2498 Applications", RFC 2573, April 1999. 2500 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- 2501 based Access Control Model (VACM) for the Simple 2502 Network Management Protocol (SNMP)", RFC 2575, 2503 April 1999. 2505 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 2506 "Introduction to Version 3 of the Internet-standard 2507 Network Management Framework", RFC 2570, April 2508 1999. 2510 [SMIv2] Case, J., McCloghrie, K., Rose, M., and S. 2511 Waldbusser, "Structure of Management Information 2512 for Version 2 of the Simple Network Management 2513 Protocol (SNMPv2)", RFC 1902, January 1996. 2515 [SNMPv2TC] Case, J., McCloghrie, K., Rose, M., and S. 2516 Waldbusser, "Textual Conventions for Version 2 of 2517 the Simple Network Management Protocol (SNMPv2)", 2518 RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., 2519 January 1996. 2521 [SNMPv2Conf] Case, J., McCloghrie, K., Rose, M., and S. 2522 Waldbusser, "Conformance Statements for Version 2 2523 of the Simple Network Management Protocol 2524 (SNMPv2)", RFC 1904, January 1996. 2526 [SNMPv1] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 2527 "Simple Network Management Protocol", RFC 1157, May 2528 1990. 2530 [SNMPv2c] Case, J., McCloghrie, K., Rose, M., and S. 2531 Waldbusser, "Introduction to Community-based 2532 SNMPv2", RFC 1901, January 1996. 2534 [SNMPv2TM] Case, J., McCloghrie, K., Rose, M., and S. 2535 Waldbusser, "Transport Mappings for Version 2 of 2536 the Simple Network Management Protocol (SNMPv2)", 2537 RFC 1906, January 1996. 2539 [SNMPv3MP] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2540 "Message Processing and Dispatching for the Simple 2541 Network Management Protocol (SNMP)", RFC 2272, 2542 January 1998. 2544 [SNMPv3USM] Blumenthal, U., and B. Wijnen, "User-based Security 2545 Model (USM) for version 3 of the Simple Network 2546 Management Protocol (SNMPv3)", RFC 2574, April 2547 1999. 2549 [SNMPv2PO] Case, J., McCloghrie, K., Rose, M., and S. 2550 Waldbusser, "Protocol Operations for Version 2 of 2551 the Simple Network Management Protocol (SNMPv2)", 2552 RFC 1905, January 1996. 2554 [SNMPv3App] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2555 Applications", RFC 2273, January 1998. 2557 [SNMPv3VACM] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- 2558 based Access Control Model (VACM) for the Simple 2559 Network Management Protocol (SNMP)", RFC 2575, 2560 April 1999. 2562 [IPSEC] Kent, S., and Atkinson, R., "Security Architecture 2563 for the Internet Protocol", RFC 2401, November 2564 1998. 2566 [IFMIB] McCloghrie, K., and F. Kastenholtz, "The Interfaces 2567 Group MIB using SMIv2", RFC 2233, Nov. 1997 2569 [ATOMMIB] Tesink, K., "Definitions of Managed Objects for ATM 2570 Management", RFC 2515, Feb. 1999 2572 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 2573 Requirement Levels", BCP 14, RFC 2119, March 1997. 2575 15. Authors' Addresses 2577 Cheenu Srinivasan 2578 Tachion Networks, Inc. 2579 Monmouth Park Corporate Center I 2580 Building C, 185 Monmouth Parkway 2581 West Long Branch, NJ 07764 2582 Phone: +1-732-542-7750 x1234 2583 Email: cheenu@tachion.com 2585 Arun Viswanathan 2586 Force10 Networks, Inc. 2587 1440 McCarthy Blvd 2588 Milpitas, CA 95035 2589 Phone: +1-408-571-3516 2590 Email: arun@force10networks.com 2592 Thomas D. Nadeau 2593 Cisco Systems, Inc. 2594 250 Apollo Drive 2595 Chelmsford, MA 01824 2596 Phone: +1-978-244-3051 2597 Email: tnadeau@cisco.com 2599 16. Full Copyright Statement 2601 Copyright (C) The Internet Society (2000). All Rights Reserved. 2603 This document and translations of it may be copied and furnished 2604 to others, and derivative works that comment on or otherwise 2605 explain it or assist in its implementation may be prepared, 2606 copied, published and distributed, in whole or in part, without 2607 restriction of any kind, provided that the above copyright notice 2608 and this paragraph are included on all such copies and derivative 2609 works. However, this document itself may not be modified in any 2610 way, such as by removing the copyright notice or references to the 2611 Internet Society or other Internet organizations, except as needed 2612 for the purpose of developing Internet standards in which case 2613 the procedures for copyrights defined in the Internet Standards 2614 process must be followed, or as required to translate it into 2615 languages other than English. 2617 The limited permissions granted above are perpetual and will not 2618 be revoked by the Internet Society or its successors or assigns. 2619 This document and the information contained herein is provided on 2620 an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 2621 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 2622 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 2623 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2624 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.