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