idnits 2.17.1 draft-ietf-mpls-lsr-mib-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document is more than 15 pages and seems to lack a Table of Contents. == There is 1 instance of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 91 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. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 697: '...eIsLocalLabelSpace MUST be set to true...' RFC 2119 keyword, line 904: '...his interface. The operStatus MUST NOT...' RFC 2119 keyword, line 1685: '... mplsOutSegmentIndex MUST be non-zero....' RFC 2119 keyword, line 1694: '...5 imply terminating LSPs and MUST have...' RFC 2119 keyword, line 1700: '...utSegmentIfIndex MUST only be set to 0...' (1 more instance...) Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 2829 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.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'SNMPv1MIBDef' is mentioned on line 79, but not defined == Unused Reference: 'LDPMIB' is defined on line 2695, but no explicit reference was found in the text == Unused Reference: 'RSVPTun' is defined on line 2706, but no explicit reference was found in the text == Unused Reference: 'CRLDP' is defined on line 2711, but no explicit reference was found in the text == Unused Reference: 'Assigned' is defined on line 2715, 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. 'TEMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'LDPMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'LblStk' -- Possible downref: Non-RFC (?) normative reference: ref. 'RSVPTun' -- Possible downref: Non-RFC (?) normative reference: ref. 'CRLDP' ** Obsolete normative reference: RFC 1700 (ref. 'Assigned') (Obsoleted by RFC 3232) ** Obsolete normative reference: RFC 2271 (ref. 'SNMPArch') (Obsoleted by RFC 2571) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. 'SNMPv1Traps') ** Obsolete normative reference: RFC 1902 (ref. 'SMIv2') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. 'SNMPv2TC') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. 'SNMPv2Conf') (Obsoleted by RFC 2580) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. 'SNMPv1') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. 'SNMPv2c') ** Obsolete normative reference: RFC 1906 (ref. 'SNMPv2TM') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2272 (ref. 'SNMPv3MP') (Obsoleted by RFC 2572) ** Obsolete normative reference: RFC 2574 (ref. 'SNMPv3USM') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. 'SNMPv2PO') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2273 (ref. 'SNMPv3App') (Obsoleted by RFC 2573) ** Obsolete normative reference: RFC 2575 (ref. 'SNMPv3VACM') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2401 (ref. 'IPSEC') (Obsoleted by RFC 4301) ** Obsolete normative reference: RFC 2233 (ref. 'IFMIB') (Obsoleted by RFC 2863) Summary: 22 errors (**), 0 flaws (~~), 9 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: September 2000 4 Arun Viswanathan 5 Force10 Networks 7 Thomas D. Nadeau 8 Cisco Systems, Inc. 10 MPLS Label Switch Router Management Information Base Using SMIv2 12 draft-ietf-mpls-lsr-mib-02.txt 14 Status of this Memo 16 This document is an Internet-Draft and is in full conformance with 17 all provisions of Section 10 of RFC 2026. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as Internet- 22 Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six 25 months and may be updated, replaced, or obsoleted by other 26 documents at any time. It is inappropriate to use Internet- 27 Drafts as reference material or to cite them other than as "work 28 in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 Abstract 38 This memo defines an experimental portion of the Management 39 Information Base (MIB) for use with network management protocols 40 in the Internet community. In particular, it describes managed 41 objects for modeling a Multi-Protocol Label Switching (MPLS) 42 [MPLSArch, MPLSFW] Label Switch Router (LSR). 44 1. Introduction 46 This memo defines an experimental portion of the Management 47 Information Base (MIB) for use with network management protocols 48 in the Internet community. In particular, it describes managed 49 objects for modeling a Multi-Protocol Label Switching (MPLS) 50 [MPLSArch, MPLSFW] Label Switch Router (LSR). 52 Comments should be made directly to the MPLS mailing list at 53 mpls@uu.net. 55 This memo does not, in its draft form, specify a standard for the 56 Internet community. 58 2. Terminology 59 This document uses terminology from the document describing the 60 MPLS architecture [MPLSArch]. A label switched path (LSP) is 61 modeled as a connection consisting of one or more incoming 62 segments (in-segments) and/or one or more outgoing segments (out- 63 segments) at a label switch router (LSR). The association or 64 interconnection of the in-segments and out-segments is 65 accomplished by using a cross-connect. We use the terminology 66 "connection" and "LSP" interchangeably where the meaning is clear 67 from the context. 69 3. The SNMP Management Framework 71 The SNMP Management Framework presently consists of five major 72 components: 74 - An overall architecture, described in RFC 2271 [SNMPArch]. 76 - Mechanisms for describing and naming objects and events for the 77 purpose of management. The first version of this Structure of 78 Management Information (SMI) is called SMIv1 and described in 79 RFC 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215 80 [SNMPv1Traps]. The second version, called SMIv2, is described 81 in RFC 1902 [SMIv2], RFC 1903 [SNMPv2TC] and RFC 1904 82 [SNMPv2Conf]. 84 - Message protocols for transferring management information. The 85 first version of the SNMP message protocol is called SNMPv1 86 and described in RFC 1157 [SNMPv1]. A second version of the 87 SNMP message protocol, which is not an Internet standards 88 track protocol, is called SNMPv2c and described in RFC 1901 89 [SNMPv2c] and RFC 1906 [SNMPv2TM]. The third version of the 90 message protocol is called SNMPv3 and described in RFC 1906 91 [SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC 2574 [SNMPv3USM]. 93 - Protocol operations for accessing management information. The 94 first set of protocol operations and associated PDU formats is 95 described in RFC 1157 [SNMPv1]. A second set of protocol 96 operations and associated PDU formats is described in RFC 1905 97 [SNMPv2PO]. 99 - A set of fundamental applications described in RFC 2273 100 [SNMPv3App] and the view-based access control mechanism 101 described in RFC 2575 [SNMPv3VACM]. 103 Managed objects are accessed via a virtual information store, 104 termed the Management Information Base or MIB. Objects in the MIB 105 are defined using the mechanisms defined in the SMI. This memo 106 specifies a MIB module that is compliant to the SMIv2. A MIB 107 conforming to the SMIv1 can be produced through the appropriate 108 translations. The resulting translated MIB must be semantically 109 equivalent, except where objects or events are omitted because no 110 translation is possible (use of Counter64). Some machine-readable 111 information in SMIv2 will be converted into textual descriptions 112 in SMIv1 during the translation process. However, this loss of 113 machine-readable information is not considered to change the 114 semantics of the MIB. 116 3.1. Object Definitions 118 Managed objects are accessed via a virtual information store, 119 termed the Management Information Base or MIB. Objects in the MIB 120 are defined using the subset of Abstract Syntax Notation One 121 (ASN.1) defined in the SMI. In particular, each object type is 122 named by an OBJECT IDENTIFIER, an administratively assigned name. 123 The object type together with an object instance serves to 124 uniquely identify a specific instantiation of the object. For 125 human convenience, we often use a textual string, termed the 126 descriptor, to also refer to the object type. 128 4. Feature Checklist 130 The MPLS label switch router MIB (LSR-MIB) is designed to satisfy 131 the following requirements and constraints: 133 - The MIB should be able to support both manually configured LSPs 134 as well as those configured via LDP and/or RSVP signaling. 136 - The MIB must support the enabling and disabling of MPLS 137 capability on MPLS capable interfaces of an LSR. 139 - The MIB should allow resource sharing between two or more LSPs. 141 - Both per-platform and per-interface label spaces must be 142 supported. 144 - MPLS packets must be forwarded solely based on an incoming top 145 label [MPLSArch, LblStk]. 147 - Support must be provided for next-hop resolution when the 148 outgoing interface is a shared media interface. In the point- 149 to-multipoint case, each outgoing segment can reside on a 150 different shared media interface. 152 - The MIB must support point-to-point, point-to-multipoint and 153 multipoint-to-point connections at an LSR. 155 - For multipoint-to-point connections all outgoing packets must 156 have the same top label. 158 - For multipoint-to-point connections, the outgoing resources of 159 the merged connections must be shared. 161 - For multipoint-to-point connections, packets from different 162 incoming connections may have distinct outgoing label stacks 163 beneath the (identical) top label. 165 - In the point-to-multipoint case each outgoing connection can 166 have a distinct label stack including the top label. 168 - All the members of a point-to-multipoint connection share the 169 resources allocated for the ingress segments. 171 - The MIB must provide cross-connect capability to "pop" an 172 incoming label and forward the packet with the remainder of 173 the label stack unchanged and without pushing any labels ("pop- 174 and-go") [LblStk]. 176 - It must be possible to assign or re-map the Class of Service 177 (COS) bits [LblStk] on the outgoing label. In the multipoint- 178 to-point case, each in-segment can have a different outgoing 179 COS value. In the point-to-multipoint case, each out-segment 180 can have a different outgoing COS value. 182 - It should be possible to support persistent as well as non- 183 persistent LSPs. 185 - Performance counters must be provided for in-segments and out- 186 segments as well as for measuring MPLS performance on a per- 187 interface basis. 189 5. Outline 191 Configuring LSPs through an LSR involves the following steps: 193 - Enabling MPLS on MPLS capable interfaces. 195 - Configuring in-segments and out-segments. 197 - Setting up the cross-connect table to associate segments and/or 198 to indicate connection origination and termination. 200 - Optionally specifying label stack actions. 202 - Optionally specifying segment traffic parameters. 204 5.1. Summary of LSR MIB 206 The MIB objects for performing these actions consist of the 207 following tables: 209 - The interface configuration table (mplsInterfaceConfTable), 210 which is used for enabling the MPLS protocol on MPLS-capable 211 interfaces. 213 - The in-segment (mplsInSegmentTable) and out-segment 214 (mplsOutSegmentTable) tables, which are used for configuring 215 LSP segments at an LSR. 217 - The cross-connect table (mplsXCTable), which is used to 218 associate in and out segments together, in order to form a 219 cross-connect. 221 - The label stack table (mplsLabelStackTable), which is used for 222 specifying label stack operations. 224 - The TSpec table (mplsTSpecTable), which is used for specifying 225 LSP-related traffic parameters. 227 Further, the MPLS in-segment and out-segment performance tables, 228 mplsInSegmentPerfTable and mplsOutSegmentPerfTable, contain the 229 objects necessary to measure the performance of LSPs, and 230 mplsInterfacePerfTable has objects to measure MPLS performance on 231 a per-interface basis. 233 These tables are described in the subsequent sections. 235 6. Brief Description of MIB Objects 237 Sections 6.1-6.3 describe objects pertaining to MPLS capable 238 interfaces of an LSR. The objects described in Sections 6.4-6.9, 239 when considered together, are equivalent to the tables described 240 in the MPLS architecture document [MPLSArch], that is, the 241 Incoming Label Map (ILM) and the Next Hop Label Forwarding Entry 242 (NHLFE) tables. Section 6.10 describes objects for specifying 243 traffic parameters for in and out segments. 245 6.1. mplsInterfaceConfTable 247 This table represents the interfaces that are MPLS capable. An 248 LSR creates an entry in this table for every MPLS capable 249 interface on that LSR. Each entry contains information about per- 250 interface label ranges. The administrator can specify the desired 251 MPLS status (enable/up, disable/down, testing) of an interface by 252 writing the object mplsInterfaceAdminStatus. The actual status is 253 indicated by the object mplsInterfaceOperStatus. 255 6.2. mplsInterfaceResTable 257 This table provides resource information such as available and 258 allocated bandwidth and buffers on each MPLS capable interface for 259 each priority level. 261 6.3. mplsInterfacePerfTable 263 This table contains objects to measure the MPLS performance of 264 MPLS capable interfaces and is an AUGMENT to 265 mplsInterfaceConfTable. High capacity counters are provided for 266 objects that are likely to wrap around quickly on high-speed 267 interfaces. 269 6.4. mplsInSegmentTable 271 This table contains a description of the incoming MPLS segments to 272 an LSR and their associated parameters. 274 6.5. mplsInSegmentPerfTable 276 The MPLS In-Segment Performance Table has objects to measure the 277 performance of an incoming segment configured on an LSR. It is an 278 AUGMENT to mplsInSegmentTable. High capacity counters are 279 provided for objects that are likely to wrap around quickly on 280 high-speed interfaces. 282 6.6. mplsOutSegmentTable 284 The Out-Segment Table contains a description of the outgoing MPLS 285 segments at an LSR and their associated parameters. 287 6.7. mplsOutSegmentPerfTable 289 The MPLS Out-Segment Table contains objects to measure the 290 performance of an outgoing segment configured on an LSR. It is an 291 AUGMENT to mplsOutSegmentTable. High capacity counters are 292 provided for objects that are likely to wrap around quickly on 293 high-speed interfaces. 295 6.8. mplsXCTable 297 The mplsXCTable specifies information for associating segments 298 together in order to instruct the LSR to switch between the 299 specified segments. It supports point-to-point, point-to-multi- 300 point and multi-point-to-point connections. 302 6.9. mplsLabelStackTable 304 The mplsLabelStackTable specifies the label stack to be pushed 305 onto a packet, beneath the top label. Entries to this table are 306 referred to from mplsXCTable. 308 6.10. mplsTSpecTable 310 The mplsTSpecTable contains objects for specifying the traffic 311 parameters of in-segments and out-segments. Entries in this table 312 are referred to from mplsInSegmentTable and mplsOutSegmentTable. 314 7. Example of LSP Setup 316 In this section we provide a brief example of using the MIB 317 objects described in Section 8 to set up an LSP. While this 318 example is not meant to illustrate every nuance of the MIB, it is 319 intended as an aid to understanding some of the key concepts. It 320 is meant to be read after going through the MIB itself. 322 Suppose that one would like to manually create a best-effort, 323 unidirectional LSP. Assume that the LSP enters the LSR via MPLS 324 interface A with ifIndex 12 and exits the LSR via MPLS interface B 325 with ifIndex 13. Let us assume that we do not wish to have a label 326 stack beneath the top label on the outgoing labeled packets. The 327 following example illustrates which rows and corresponding objects 328 might be created to accomplish this. 330 First, the TSpec entries must be set-up for both segments. 332 In mplsTSpecTable for the incoming direction: 334 { 335 mplsTSpecIndex = 5 336 mplsTSpecMaxRate = 100000, 337 mplsTSpecMeanRate = 100000, 338 mplsTSpecMaxBurstSize = 2000, 339 mplsTSpecRowStatus = createAndGo(4) 340 } 342 In mplsTSpecTable for the outgoing direction: 343 { 344 mplsTSpecIndex = 6 345 mplsTSpecMaxRate = 100000, 346 mplsTSpecMeanRate = 100000, 347 mplsTSpecMaxBurstSize = 2000, 348 mplsTSpecRowStatus = createAndGo(4) 349 } 351 Note that if we were setting up a bi-directional LSP, the segments 352 in the reverse direction can share the TSpec entries (and hence 353 resources) with the segments in the forward direction. 355 We must next create the appropriate in-segment and out-segment 356 entries with suitable traffic parameters by pointing to the 357 appropriate TSpec entries that we have just created. 359 In mplsInSegmentTable: 360 { 361 mplsInSegmentIfIndex = 12, -- incoming interface 362 mplsInSegmentLabel = 21, -- incoming label 363 mplsInSegmentNPop = 1, 364 mplsInSegmentTSpecIndex = 5, 365 mplsInSegmentRowStatus = createAndGo(4) 366 } 368 In mplsOutSegmentTable: 369 { 370 mplsOutSegmentIndex = 1, 371 mplsOutSegmentIfIndex = 13, -- outgoing interface 372 mplsOutSegmentPushTopLabel = true(1), 373 mplsOutSegmentTopLabel = 22, -- outgoing label 374 mplsOutSegmentTSpecIndex = 6, 375 mplsOutSegmentRowStatus = createAndGo(4) 376 } 378 Next, a cross-connect entry is created thereby associating the 379 newly created segments together. 381 In mplsXCTable: 382 { 383 mplsXCIndex = 2, 384 mplsXCLspId = "1.2.3.4-2", 385 mplsInSegmentIfIndex = 12, 386 mplsInSegmentLabel = 21, 387 mplsOutSegmentIndex = 1, 388 mplsXCCOS = 0, 389 mplsXCIsPersistent = false (1), 390 mplsLabelStackIndex = 0, -- only a single outgoing label 391 mplsXCRowStatus = createAndGo(4) 392 } 393 Note that the mplsInSegmentXCIndex and mplsOutSegmentXCIndex 394 objects will automatically be populated with the value 2 when 395 these segments are referred to from the corresponding cross- 396 connect entry. 398 8. Application of the Interface Group to MPLS 400 The Interfaces Group of MIB II defines generic managed objects for 401 managing interfaces. This memo contains the media-specific 402 extensions to the Interfaces Group for managing MPLS interfaces. 404 This memo assumes the interpretation of the Interfaces Group to be 405 in accordance with [IFMIB] which states that the interfaces table 406 (ifTable) contains information on the managed resource's 407 interfaces and that each sub-layer below the internetwork layer of 408 a network interface is considered an interface. Thus, the MPLS 409 layer interface is represented as an entry in the ifTable. This 410 entry is concerned with the MPLS layer as a whole, and not with 411 individual LSPs/tunnels which are managed via the MPLS-specific 412 managed objects specified in this memo and [TEMIB]. The inter- 413 relation of entries in the ifTable is defined by Interfaces Stack 414 Group defined in [IFMIB]. 416 8.1. Support of the MPLS Layer by ifTable 418 Some specific interpretations of ifTable for the MPLS layer 419 follow. 421 Object Use for the MPLS layer 422 ifIndex Each MPLS interface is represented by an ifEntry. 424 ifDescr Description of the MPLS interface. 426 ifType The value that is allocated for MPLS is 166. 428 ifSpeed The total bandwidth in bits per second for use by 429 the MPLS layer. 431 ifPhysAddress Unused. 433 ifAdminStatus See [IFMIB]. 435 ifOperStatus Assumes the value down(2) if the MPLS layer is 436 down. 438 ifLastChange See [IFMIB]. 440 ifInOctets The number of received octets over the interface, 441 i.e., the number of received, octets received as 442 labeled packets. 444 ifOutOctets The number of transmitted octets over the 445 interface, i.e., the number of octets transmitted 446 as labeled packets. 448 ifInErrors The number of labeled packets dropped due to 449 uncorrectable errors. 451 ifInUnknownProtos 452 The number of received packets discarded during 453 packet header validation, including packets with 454 unrecognized label values. 456 ifOutErrors See [IFMIB]. 458 ifName Textual name (unique on this system) of the 459 interface or an octet string of zero length. 461 ifLinkUpDownTrapEnable 462 Default is disabled (2). 464 ifConnectorPresent 465 Set to false (2). 467 ifHighSpeed See [IFMIB]. 469 ifHCInOctets The 64-bit version of ifInOctets; supported if 470 required by the compliance statements in [IFMIB]. 472 ifHCOutOctets The 64-bit version of ifOutOctets; supported if 473 required by the compliance statements in [IFMIB]. 475 ifAlias The non-volatile 'alias' name for the interface as 476 specified by a network manager. 478 9. MPLS Label Switch Router MIB Definitions 480 MPLS-LSR-MIB DEFINITIONS ::= BEGIN 482 IMPORTS 483 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 484 experimental, Integer32, Unsigned32, Counter32, 485 Counter64, Gauge32, IpAddress 486 FROM SNMPv2-SMI 487 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 488 FROM SNMPv2-CONF 489 TEXTUAL-CONVENTION, TruthValue, RowStatus 490 FROM SNMPv2-TC 491 ifIndex, InterfaceIndex, InterfaceIndexOrZero 492 FROM IF-MIB; 494 mplsLsrMIB MODULE-IDENTITY 495 LAST-UPDATED "200002161200Z" -- 16 February 2000 12:00:00 EST 496 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 497 CONTACT-INFO 498 " Cheenu Srinivasan 499 Postal: Tachion Networks, Inc. 500 2 Meridian Road 501 Eatontown, NJ 0772 502 Tel: +1 732 542 7750 x234 503 Email: cheenu@tachion.com 505 Arun Viswanathan 506 Postal: Force10 Networks 507 1440 McCarthy Blvd 508 Milpitas, CA 95035 509 Tel: +1-408-571-3516 510 Email: arun@force10networks.com 512 Thomas D. Nadeau 513 Postal: Cisco Systems, Inc. 514 250 Apollo Drive 515 Chelmsford, MA 01824 517 Tel: +1-978-244-3051 518 Email: tnadeau@cisco.com" 520 DESCRIPTION 521 "This MIB contains managed object definitions for the 522 Multiprotocol Label Switching (MPLS) Router as 523 defined in: Rosen, E., Viswanathan, A., and R. 524 Callon, Multiprotocol Label Switching Architecture, 525 Internet Draft , 526 February 2000." 528 -- Revision history. 529 REVISION 530 "199907161200Z" -- 16 July 1999 12:00:00 EST 531 DESCRIPTION 532 "Initial draft version." 533 REVISION 534 "200002161200Z" -- 16 February 2000 12:00:00 EST 535 DESCRIPTION 536 "Second draft version." 537 REVISION 538 "200003061200Z" -- 6 March 2000 12:00:00 EST 539 DESCRIPTION 540 "Third draft version." 542 ::= { experimental 96 } 544 -- Textual Conventions. 546 MplsLSPID ::= TEXTUAL-CONVENTION 547 STATUS current 548 DESCRIPTION 549 "An identifier that is assigned to each LSP and is 550 used to uniquely identify it. This is assigned at 551 the head end of the LSP and can be used by all LSRs 552 to identify this LSP. This value is piggybacked by 553 the signaling protocol when this LSP is signaled 554 within the network. This identifier can then be used 555 at each LSR to identify which labels are being 556 swapped to other labels for this LSP. For IPv4 557 addresses this results in a 6-octet long cookie." 558 SYNTAX OCTET STRING (SIZE (0..63)) 560 MplsLsrIANAAddrFamily ::= TEXTUAL-CONVENTION 561 STATUS current 562 DESCRIPTION 563 "An address family. These values are defined in RFC 564 1700 and are maintained by The IANA. All values may 565 not be relevant in all contexts when used in this 566 MIB, but are included for completeness." 567 REFERENCE 568 "RFC 1700 - Assigned Numbers, Reynolds, J. and J. 569 Postel, Oct. 1994" 570 SYNTAX INTEGER { 571 other(0), 572 ipv4(1), 573 ipv6(2), 574 nsap(3), 575 hdlc(4), 576 bbn1822(5), 577 ieee802(6), 578 e163(7), 579 e164(8), 580 f69(9), 581 x121(10), 582 ipx(11), 583 appleTalk(12), 584 decnetIV(13), 585 banyanVines(14), 586 e164WithNsap(15) 587 } 589 -- An MPLS label. 590 MplsLabel ::= TEXTUAL-CONVENTION 591 STATUS current 592 DESCRIPTION 593 "Represents an MPLS label. Note that the contents of 594 a label field are interpreted in an interface-type 595 specific fashion. For example, the 20-bit wide 596 label carried in the MPLS shim header is contained 597 in bits 0-19 and bits 20-31 must be zero. The frame 598 relay label can be either 10, 17 or 23 bits wide 599 depending on the size of the DLCI field and bits 10- 600 31, 17-31 or 23-31 must be zero, respectively. For 601 an ATM interface, bits 0-15 must be interpreted as 602 the VCI, bits 16-23 as the VPI and bits 24-31 must 603 be zero. Note that the permissible label values are 604 also a function of the interface type. For example, 605 the value 3 has special semantics in the control 606 plane for an MPLS shim header label and is not a 607 valid label value in the data path." 608 REFERENCE 609 "1. MPLS Label Stack Encoding, Rosen et al, draft- 610 ietf-mpls-label-encaps-07.txt, March 2000. 611 2. Use of Label Switching on Frame Relay Networks, 612 Conta et al, draft-ietf-mpls-fr-03.txt, Nov. 613 1998." 614 SYNTAX Integer32 616 Ipv6Address ::= TEXTUAL-CONVENTION 617 STATUS current 618 DESCRIPTION 619 "IPv6 address." 620 SYNTAX OCTET STRING (SIZE(16)) 622 MplsBitRate ::= TEXTUAL-CONVENTION 623 DISPLAY-HINT "d" 624 STATUS current 625 DESCRIPTION 626 "An estimate of bandwidth in units of 1,000 bits per 627 second. If this object reports a value of 'n' then 628 the rate of the object is somewhere in the range of 629 'n-500' to 'n+499'. For objects which do not vary in 630 bitrate, or for those where no accurate estimation 631 can be made, this object should contain the nominal 632 bitrate." 633 SYNTAX Integer32 (1..2147483647) 635 MplsBurstSize ::= TEXTUAL-CONVENTION 636 DISPLAY-HINT "d" 637 STATUS current 638 DESCRIPTION 639 "The number of octets of MPLS data that the stream 640 may send back-to-back without concern for policing." 641 SYNTAX Integer32 (1..2147483647) 643 MplsBufferSize ::= TEXTUAL-CONVENTION 644 DISPLAY-HINT "d" 645 STATUS current 646 DESCRIPTION 647 "Size of buffer in octets of MPLS data." 648 SYNTAX Integer32 (1..2147483647) 650 -- Top level components of this MIB. 652 -- tables, scalars 653 mplsLsrObjects OBJECT IDENTIFIER ::= { mplsLsrMIB 1 } 654 -- traps 655 mplsLsrNotifications OBJECT IDENTIFIER ::= { mplsLsrMIB 2 } 656 -- conformance 657 mplsLsrConformance OBJECT IDENTIFIER ::= { mplsLsrMIB 3 } 659 -- MPLS Interface Configuration Table. 661 mplsInterfaceConfTable OBJECT-TYPE 662 SYNTAX SEQUENCE OF MplsInterfaceConfEntry 663 MAX-ACCESS not-accessible 664 STATUS current 665 DESCRIPTION 666 "This table specifies per-interface MPLS capability 667 and associated information." 668 ::= { mplsLsrObjects 1 } 670 mplsInterfaceConfEntry OBJECT-TYPE 671 SYNTAX MplsInterfaceConfEntry 672 MAX-ACCESS not-accessible 673 STATUS current 674 DESCRIPTION 675 "An entry in this table is created by an LSR for 676 every interface capable of supporting MPLS. When the 677 global label space is in use, an entry with index 0 678 is created in this table. This entry contains 679 parameters that apply to all interfaces that 680 participate in the global label space. Other 681 interfaces defined in this table indicate whether or 682 not they participate in the global label space by 683 setting the mplsInterfaceIsGlobalLabelSpace variable 684 to true. Note that interfaces which have specified 685 that they participate in an interface-specific label 686 space may also participate in the global label space 687 simultaneously. In this case, the interface with 688 index 0 should referenced for global label space 689 parameters such as the label ranges. It may be 690 useful to configure additional interfaces in this 691 table for interfaces which participate in the global 692 label space so that parameters such as bandwidth and 693 buffer resources maybe specified individually. 695 Please note that either 696 mplsInterfaceIsGlobalLabelSpace or 697 mplsInterfaceIsLocalLabelSpace MUST be set to true 698 on every interface configured in this table." 699 INDEX { mplsInterfaceConfIndex } 700 ::= { mplsInterfaceConfTable 1 } 702 MplsInterfaceConfEntry ::= SEQUENCE { 703 mplsInterfaceConfIndex InterfaceIndexOrZero, 704 mplsInterfaceLabelMinIn MplsLabel, 705 mplsInterfaceLabelMaxIn MplsLabel, 706 mplsInterfaceLabelMinOut MplsLabel, 707 mplsInterfaceLabelMaxOut MplsLabel, 708 mplsInterfaceTotalBandwidth MplsBitRate, 709 mplsInterfaceAvailableBandwidth MplsBitRate, 710 mplsInterfaceTotalBuffer MplsBufferSize, 711 mplsInterfaceAvailableBuffer MplsBufferSize, 712 mplsInterfaceIsGlobalLabelSpace TruthValue, 713 mplsInterfaceIsLocalLabelSpace TruthValue, 714 mplsInterfaceAdminStatus INTEGER, 715 mplsInterfaceOperStatus INTEGER 716 } 718 mplsInterfaceConfIndex OBJECT-TYPE 719 SYNTAX InterfaceIndexOrZero 720 MAX-ACCESS read-only 721 STATUS current 722 DESCRIPTION 723 "This is a unique index for an entry in the 724 MplsInterfaceConfTable. A non-zero index for an 725 entry indicates the ifIndex for the corresponding 726 interface entry in of the MPLS-layer in the ifTable. 727 Note that the global label space may apply to 728 several interfaces, and therefore the configuration 729 of the global label space interface parameters will 730 apply to all of the interfaces that are 731 participating in the global label space." 732 REFERENCE 733 "RFC 2233 - The Interfaces Group MIB using SMIv2, 734 McCloghrie, K., and F. Kastenholtz, Nov. 1997" 735 ::= { mplsInterfaceConfEntry 1 } 737 mplsInterfaceLabelMinIn OBJECT-TYPE 738 SYNTAX MplsLabel 739 MAX-ACCESS read-only 740 STATUS current 741 DESCRIPTION 742 "This is the minimum value of an MPLS label that this 743 LSR is willing to receive on this interface. Please 744 note that in the case that the 745 mplsInterfaceIsLocalLabelSpace is set to true, this 746 value indicates the value appropriate for the per- 747 interface label range. If the 748 mplsInterfaceIsGlobalLabelSpace is true, please 749 refer to the interface whose index is 0 for the 750 value which applies to the global label space." 751 ::= { mplsInterfaceConfEntry 2 } 753 mplsInterfaceLabelMaxIn OBJECT-TYPE 754 SYNTAX MplsLabel 755 MAX-ACCESS read-only 756 STATUS current 757 DESCRIPTION 758 "This is the maximum value of an MPLS label that this 759 LSR is willing to receive on this interface. Please 760 note that in the case that the 761 mplsInterfaceIsLocalLabelSpace is set to true, this 762 value indicates the value appropriate for the per- 763 interface label range. If the 764 mplsInterfaceIsGlobalLabelSpace is true, please 765 refer to the interface whose index is 0 for the 766 value which applies to the global label space." 767 ::= { mplsInterfaceConfEntry 3 } 769 mplsInterfaceLabelMinOut OBJECT-TYPE 770 SYNTAX MplsLabel 771 MAX-ACCESS read-only 772 STATUS current 773 DESCRIPTION 774 "This is the minimum value of an MPLS label that this 775 LSR is willing to send on this interface. Please 776 note that in the case that the 777 mplsInterfaceIsLocalLabelSpace is set to true, this 778 value indicates the value appropriate for the per- 779 interface label range. If the 780 mplsInterfaceIsGlobalLabelSpace is true, please 781 refer to the interface whose index is 0 for the 782 value which applies to the global label space." 783 ::= { mplsInterfaceConfEntry 4 } 785 mplsInterfaceLabelMaxOut OBJECT-TYPE 786 SYNTAX MplsLabel 787 MAX-ACCESS read-only 788 STATUS current 789 DESCRIPTION 790 "This is the maximum value of an MPLS label that this 791 LSR is willing to send on this interface. Please 792 note that in the case that the 793 mplsInterfaceIsLocalLabelSpace is set to true, this 794 value indicates the value appropriate for the per- 795 interface label range. If the 796 mplsInterfaceIsGlobalLabelSpace is true, please 797 refer to the interface whose index is 0 for the 798 value which applies to the global label space." 799 ::= { mplsInterfaceConfEntry 5 } 801 mplsInterfaceTotalBandwidth OBJECT-TYPE 802 SYNTAX MplsBitRate 803 MAX-ACCESS read-only 804 STATUS current 805 DESCRIPTION 806 "This value indicates the total amount of usable 807 bandwidth on this interface and is specified in 808 kilobits per second (Kbps/sec). This variable is not 809 applicable when applied to the interface with index 810 0." 811 ::= { mplsInterfaceConfEntry 6 } 813 mplsInterfaceAvailableBandwidth OBJECT-TYPE 814 SYNTAX MplsBitRate 815 MAX-ACCESS read-only 816 STATUS current 817 DESCRIPTION 818 "This value indicates the total amount of available 819 bandwidth available on this interface and is 820 specified in kilobits per second (Kbps/sec). This 821 value is calculated as the difference between the 822 amount of bandwidth currently in use and that 823 specified in mplsInterfaceTotalBandwidth. This 824 variable is not applicable when applied to the 825 interface with index 0." 826 ::= { mplsInterfaceConfEntry 7 } 828 mplsInterfaceTotalBuffer OBJECT-TYPE 829 SYNTAX MplsBufferSize 830 MAX-ACCESS read-only 831 STATUS current 832 DESCRIPTION 833 "This value indicates the total amount of buffer 834 space allocated for this interface. This variable is 835 not applicable when applied to the interface with 836 index 0." 837 ::= { mplsInterfaceConfEntry 8 } 839 mplsInterfaceAvailableBuffer OBJECT-TYPE 840 SYNTAX MplsBufferSize 841 MAX-ACCESS read-only 842 STATUS current 843 DESCRIPTION 844 "This value reflects the total amount of buffer space 845 available on this interface. This variable is not 846 applicable when applied to the interface with index 847 0." 848 ::= { mplsInterfaceConfEntry 9 } 850 mplsInterfaceIsGlobalLabelSpace OBJECT-TYPE 851 SYNTAX TruthValue 852 MAX-ACCESS read-only 853 STATUS current 854 DESCRIPTION 855 "This value indicates whether or not this interface 856 participates in the global label space." 857 DEFVAL { false } 858 ::= { mplsInterfaceConfEntry 10 } 860 mplsInterfaceIsLocalLabelSpace OBJECT-TYPE 861 SYNTAX TruthValue 862 MAX-ACCESS read-only 863 STATUS current 864 DESCRIPTION 865 "This value indicates whether or not this interface 866 uses in the local or per-interface label space." 867 DEFVAL { false } 868 ::= { mplsInterfaceConfEntry 11 } 870 mplsInterfaceAdminStatus OBJECT-TYPE 871 SYNTAX INTEGER { 872 up(1), -- enable MPLS on this interface 873 down(2), -- disable MPLS on this interface 874 testing(3) -- in some test mode 875 } 876 MAX-ACCESS read-write 877 STATUS current 878 DESCRIPTION 879 "This variable indicates the administrator's intent 880 as to whether MPLS should be enabled, disabled, or 881 running in some diagnostic testing mode on this 882 interface." 883 DEFVAL { down } 884 ::= { mplsInterfaceConfEntry 12 } 886 mplsInterfaceOperStatus OBJECT-TYPE 887 SYNTAX INTEGER { 888 up(1), -- ready to pass packets 889 down(2), 890 testing(3), -- in some test mode 891 unknown(4), -- status cannot be determined for some 892 -- reason 893 dormant(5), 894 notPresent(6), -- some component is missing 895 lowerLayerDown(7) 896 -- down due to the state of 897 -- lower layer interfaces 899 } 900 MAX-ACCESS read-only 901 STATUS current 902 DESCRIPTION 903 "This value reflects the actual or operational status 904 of MPLS on this interface. The operStatus MUST NOT 905 enter the up state unless either 906 mplsInterfaceIsGlobalLabelSpace or 907 mplsInterfaceIsLocalLabelSpace is set to true." 908 ::= { mplsInterfaceConfEntry 13 } 910 -- End of mplsInterfaceConfTable 912 -- MPLS Interface Performance Table. 914 mplsInterfacePerfTable OBJECT-TYPE 915 SYNTAX SEQUENCE OF MplsInterfacePerfEntry 916 MAX-ACCESS not-accessible 917 STATUS current 918 DESCRIPTION 919 "This table provides MPLS performance information on 920 a per-interface basis." 921 ::= { mplsLsrObjects 2 } 923 mplsInterfacePerfEntry OBJECT-TYPE 924 SYNTAX MplsInterfacePerfEntry 925 MAX-ACCESS not-accessible 926 STATUS current 927 DESCRIPTION 928 "An entry in this table is created by the LSR for 929 every interface capable of supporting MPLS. Its is 930 an extension to the mplsInterfaceConfEntry table." 931 AUGMENTS { mplsInterfaceConfEntry } 932 ::= { mplsInterfacePerfTable 1 } 934 MplsInterfacePerfEntry ::= SEQUENCE { 935 -- incoming direction 936 mplsInterfaceInLabelsUsed Gauge32, 937 mplsInterfaceInPackets Counter32, 938 mplsInterfaceInDiscards Counter32, 939 mplsInterfaceFailedLabelLookup Counter32, 941 -- outgoing direction 942 mplsInterfaceOutLabelsUsed Gauge32, 943 mplsInterfaceOutPackets Counter32, 944 mplsInterfaceOutDiscards Counter32, 945 mplsInterfaceOutFragments Counter32 946 } 948 mplsInterfaceInLabelsUsed OBJECT-TYPE 949 SYNTAX Gauge32 950 MAX-ACCESS read-only 951 STATUS current 952 DESCRIPTION 953 "This value indicates the specific number of labels 954 that are in use at this point in time on this 955 interface in the incoming direction." 956 ::= { mplsInterfacePerfEntry 1 } 958 mplsInterfaceInPackets OBJECT-TYPE 959 SYNTAX Counter32 960 MAX-ACCESS read-only 961 STATUS current 962 DESCRIPTION 963 "This variable reflects the number of labeled packets 964 that have been received on this interface." 965 ::= { mplsInterfacePerfEntry 2 } 967 mplsInterfaceInDiscards OBJECT-TYPE 968 SYNTAX Counter32 969 MAX-ACCESS read-only 970 STATUS current 971 DESCRIPTION 972 "The number of inbound labeled packets, which were 973 chosen to be discarded even though no errors had 974 been detected to prevent their being transmitted. 975 One possible reason for discarding such a labeled 976 packet could be to free up buffer space." 977 ::= { mplsInterfacePerfEntry 3 } 979 mplsInterfaceFailedLabelLookup OBJECT-TYPE 980 SYNTAX Counter32 981 MAX-ACCESS read-only 982 STATUS current 983 DESCRIPTION 984 "This value indicates the number of labeled packets 985 that have been received on this interface and were 986 discarded because there were no matching entries 987 found for them in mplsInSegmentTable." 988 ::= { mplsInterfacePerfEntry 4 } 990 mplsInterfaceOutLabelsUsed OBJECT-TYPE 991 SYNTAX Gauge32 992 MAX-ACCESS read-only 993 STATUS current 994 DESCRIPTION 995 "Indicates the number of top-most labels in the 996 outgoing label stacks that are in use at this point 997 in time on this interface." 998 ::= { mplsInterfacePerfEntry 5 } 1000 mplsInterfaceOutPackets OBJECT-TYPE 1001 SYNTAX Counter32 1002 MAX-ACCESS read-only 1003 STATUS current 1004 DESCRIPTION 1005 "This variable contains the number of labeled packets 1006 that have been transmitted on this interface." 1007 ::= { mplsInterfacePerfEntry 6 } 1009 mplsInterfaceOutDiscards OBJECT-TYPE 1010 SYNTAX Counter32 1011 MAX-ACCESS read-only 1012 STATUS current 1013 DESCRIPTION 1014 "The number of outbound labeled packets, which were 1015 chosen to be discarded even though no errors had 1016 been detected to prevent their being transmitted. 1017 One possible reason for discarding such a labeled 1018 packet could be to free up buffer space." 1019 ::= { mplsInterfacePerfEntry 7 } 1021 mplsInterfaceOutFragments OBJECT-TYPE 1022 SYNTAX Counter32 1023 MAX-ACCESS read-only 1024 STATUS current 1025 DESCRIPTION 1026 "This variable indicates the number of outgoing MPLS 1027 packets that required fragmentation before 1028 transmission on this interface." 1029 ::= { mplsInterfacePerfEntry 8 } 1031 -- End of mplsInterfacePerfTable 1033 -- In-segment table. 1035 mplsInSegmentTable OBJECT-TYPE 1036 SYNTAX SEQUENCE OF MplsInSegmentEntry 1037 MAX-ACCESS not-accessible 1038 STATUS current 1039 DESCRIPTION 1040 "This table contains a collection of incoming 1041 segments to an LSR." 1042 ::= { mplsLsrObjects 3 } 1044 mplsInSegmentEntry OBJECT-TYPE 1045 SYNTAX MplsInSegmentEntry 1046 MAX-ACCESS not-accessible 1047 STATUS current 1048 DESCRIPTION 1049 "An entry in this table represents one incoming 1050 segment. An entry can be created by a network 1051 administrator or an SNMP agent, or an MPLS signaling 1052 protocol. The creator of the entry is denoted by 1053 mplsInSegmentOwner. An entry in this table is 1054 indexed by the ifIndex of the incoming interface and 1055 the (top) label. Note that some segments are 1056 associated with a tunnel, so the traffic parameters 1057 of these rows are supported as read-only objects and 1058 their modification can be done only via the tunnel 1059 table, mplsTunnelTable." 1060 REFERENCE 1061 "MPLS Traffic Engineering Management Information Base 1062 Using SMIv2, Srinivasan, Viswanathan and Nadeau, 1063 draft-ietf-mpls-te-mib-02.txt, February 2000." 1064 INDEX { mplsInSegmentIfIndex, mplsInSegmentLabel } 1065 ::= { mplsInSegmentTable 1 } 1067 MplsInSegmentEntry ::= SEQUENCE { 1068 mplsInSegmentIfIndex InterfaceIndex, 1069 mplsInSegmentLabel MplsLabel, 1070 mplsInSegmentNPop Integer32, 1071 mplsInSegmentAddrFamily MplsLsrIANAAddrFamily, 1072 mplsInSegmentXCIndex Integer32, 1073 mplsInSegmentTSpecIndex Integer32, 1074 mplsInSegmentOwner INTEGER, 1075 mplsInSegmentAdminStatus INTEGER, 1076 mplsInSegmentOperStatus INTEGER, 1077 mplsInSegmentRowStatus RowStatus 1078 } 1080 mplsInSegmentIfIndex OBJECT-TYPE 1081 SYNTAX InterfaceIndexOrZero 1082 MAX-ACCESS read-create 1083 STATUS current 1084 DESCRIPTION 1085 "This is a unique index for an entry in the 1086 MplsInSegmentTable. This value represents the 1087 interface index for the incoming MPLS interface. A 1088 value of zero represents an incoming label from the 1089 per-platform label space. In this case, the 1090 mplsInSegmentLabel is interpreted to be an MPLS-type 1091 label." 1092 ::= { mplsInSegmentEntry 1 } 1094 mplsInSegmentLabel OBJECT-TYPE 1095 SYNTAX MplsLabel 1096 MAX-ACCESS read-create 1097 STATUS current 1098 DESCRIPTION 1099 "The incoming label for this segment." 1100 ::= { mplsInSegmentEntry 2 } 1102 mplsInSegmentNPop OBJECT-TYPE 1103 SYNTAX Integer32 (1..2147483647) 1104 MAX-ACCESS read-create 1105 STATUS current 1106 DESCRIPTION 1107 "The number of labels to pop from the incoming 1108 packet. Normally only the top label is popped from 1109 the packet and used for all switching decisions for 1110 that packet." 1111 DEFVAL { 1 } 1112 ::= { mplsInSegmentEntry 3 } 1114 mplsInSegmentAddrFamily OBJECT-TYPE 1115 SYNTAX MplsLsrIANAAddrFamily 1116 MAX-ACCESS read-create 1117 STATUS current 1118 DESCRIPTION 1119 "The IANA address family of the incoming packet. A 1120 value of zero indicates that the family type is 1121 either unknown or undefined. This latter case is 1122 possible for example, when packet streams of 1123 different types are merged in a multipoint-to-point 1124 connection." 1125 REFERENCE 1126 "RFC 1700 - Assigned Numbers, Reynolds and Postel, 1127 October 1994." 1128 DEFVAL { 0 } 1129 ::= { mplsInSegmentEntry 4 } 1131 mplsInSegmentXCIndex OBJECT-TYPE 1132 SYNTAX Integer32 (1..2147483647) 1133 MAX-ACCESS read-only 1134 STATUS current 1135 DESCRIPTION 1136 "The index into mplsXCTable is used to identify which 1137 cross-connect entry this segment is part of. Note 1138 that a value of zero indicates that it is not being 1139 referred to by any cross-connect entry." 1140 DEFVAL { 0 } 1141 ::= { mplsInSegmentEntry 5 } 1143 mplsInSegmentTSpecIndex OBJECT-TYPE 1144 SYNTAX Integer32 (1..2147483647) 1145 MAX-ACCESS read-create 1146 STATUS current 1147 DESCRIPTION 1148 "This variable represents a pointer into the 1149 mplsTSpecTable and indicates the TSpec which is to 1150 be assigned to this segment. A value of zero 1151 indicates best-effort treatment. Two or more 1152 segments can indicate resource sharing by pointing 1153 to the same entry in mplsTSpecTable." 1154 DEFVAL { 0 } 1155 ::= { mplsInSegmentEntry 6 } 1157 mplsInSegmentOwner OBJECT-TYPE 1158 SYNTAX INTEGER { 1159 snmp(1), 1160 ldp(2), 1161 rsvp(3), 1162 policyAgent(4), 1163 other(5) 1164 } 1165 MAX-ACCESS read-create 1166 STATUS current 1167 DESCRIPTION 1168 "Denotes the entity that created and is responsible 1169 for managing this segment." 1170 ::= { mplsInSegmentEntry 7 } 1172 mplsInSegmentAdminStatus OBJECT-TYPE 1173 SYNTAX INTEGER { 1174 up(1), -- ready to pass packets 1175 down(2), 1176 testing(3) -- in some test mode 1177 } 1178 MAX-ACCESS read-create 1179 STATUS current 1180 DESCRIPTION 1181 "This value is used to represent the manager�s 1182 desired operational status of this segment." 1183 ::= { mplsInSegmentEntry 8 } 1185 mplsInSegmentOperStatus OBJECT-TYPE 1186 SYNTAX INTEGER { 1187 up(1), -- ready to pass packets 1188 down(2), 1189 testing(3), -- in some test mode 1190 unknown(4), -- status cannot be determined for 1191 -- some reason 1192 dormant(5), 1193 notPresent(6), -- some component is missing 1194 lowerLayerDown(7) 1195 -- down due to the state of 1196 -- lower layer interfaces 1197 } 1198 MAX-ACCESS read-only 1199 STATUS current 1200 DESCRIPTION 1201 "This value represents the actual operational status 1202 of this segment." 1203 ::= { mplsInSegmentEntry 9 } 1205 mplsInSegmentRowStatus OBJECT-TYPE 1206 SYNTAX RowStatus 1207 MAX-ACCESS read-create 1208 STATUS current 1209 DESCRIPTION 1210 "This variable is used to create, modify, and/or 1211 delete a row in this table." 1212 ::= { mplsInSegmentEntry 10 } 1214 -- End of mplsInSegmentTable 1215 -- In-segment performance table. 1217 mplsInSegmentPerfTable OBJECT-TYPE 1218 SYNTAX SEQUENCE OF MplsInSegmentPerfEntry 1219 MAX-ACCESS not-accessible 1220 STATUS current 1221 DESCRIPTION 1222 "This table contains statistical information for 1223 incoming MPLS segments to an LSR." 1224 ::= { mplsLsrObjects 4 } 1226 mplsInSegmentPerfEntry OBJECT-TYPE 1227 SYNTAX MplsInSegmentPerfEntry 1228 MAX-ACCESS not-accessible 1229 STATUS current 1230 DESCRIPTION 1231 "An entry in this table contains statistical 1232 information about one incoming segment which was 1233 configured in the mplsInSegmentTable. The counters 1234 in this entry should behave in a manner similar to 1235 that of the interface." 1236 AUGMENTS { mplsInSegmentEntry } 1237 ::= { mplsInSegmentPerfTable 1 } 1239 MplsInSegmentPerfEntry ::= SEQUENCE { 1240 mplsInSegmentOctets Counter32, 1241 mplsInSegmentPackets Counter32, 1242 mplsInSegmentErrors Counter32, 1243 mplsInSegmentDiscards Counter32, 1245 -- high capacity counter 1246 mplsInSegmentHCOctets Counter64 1248 } 1250 mplsInSegmentOctets OBJECT-TYPE 1251 SYNTAX Counter32 1252 MAX-ACCESS read-only 1253 STATUS current 1254 DESCRIPTION 1255 "This value represents the total number of octets 1256 received by this segment." 1257 ::= { mplsInSegmentPerfEntry 1 } 1259 mplsInSegmentPackets OBJECT-TYPE 1260 SYNTAX Counter32 1261 MAX-ACCESS read-only 1262 STATUS current 1263 DESCRIPTION 1264 "Total number of packets received by this segment." 1265 ::= { mplsInSegmentPerfEntry 2 } 1267 mplsInSegmentErrors OBJECT-TYPE 1268 SYNTAX Counter32 1269 MAX-ACCESS read-only 1270 STATUS current 1271 DESCRIPTION 1272 "The number of errored packets received on this 1273 segment." 1274 ::= { mplsInSegmentPerfEntry 3 } 1276 mplsInSegmentDiscards OBJECT-TYPE 1277 SYNTAX Counter32 1278 MAX-ACCESS read-only 1279 STATUS current 1280 DESCRIPTION 1281 "The number of labeled packets received on this in- 1282 segment, which were chosen to be discarded even 1283 though no errors had been detected to prevent their 1284 being transmitted. One possible reason for 1285 discarding such a labeled packet could be to free up 1286 buffer space." 1287 ::= { mplsInSegmentPerfEntry 4 } 1289 mplsInSegmentHCOctets OBJECT-TYPE 1290 SYNTAX Counter32 1291 MAX-ACCESS read-only 1292 STATUS current 1293 DESCRIPTION 1294 "The total number of octets received. This is the 64 1295 bit version of mplsInSegmentOctets." 1296 ::= { mplsInSegmentPerfEntry 5 } 1298 -- End of mplsInSegmentPerfTable. 1300 -- Out-segment table. 1302 mplsOutSegmentIndexNext OBJECT-TYPE 1303 SYNTAX Integer32 (1..2147483647) 1304 MAX-ACCESS read-only 1305 STATUS current 1306 DESCRIPTION 1307 "This object contains the next appropriate value to 1308 be used for mplsOutSegmentIndex when creating 1309 entries in the mplsOutSegmentTable. If the number of 1310 unassigned entries is exhausted, this object will 1311 take on the value of 0. To obtain the 1312 mplsOutSegmentIndex value for a new entry, the 1313 manager must first issue a management protocol 1314 retrieval operation to obtain the current value of 1315 this object. The agent should modify the value to 1316 reflect the next unassigned index after each 1317 retrieval operation. After a manager retrieves a 1318 value the agent will determine through its local 1319 policy when this index value will be made available 1320 for reuse." 1321 ::= { mplsLsrObjects 5 } 1323 mplsOutSegmentTable OBJECT-TYPE 1324 SYNTAX SEQUENCE OF MplsOutSegmentEntry 1325 MAX-ACCESS not-accessible 1326 STATUS current 1327 DESCRIPTION 1328 "This table contains a representation of the outgoing 1329 segments from an LSR." 1330 ::= { mplsLsrObjects 6 } 1332 mplsOutSegmentEntry OBJECT-TYPE 1333 SYNTAX MplsOutSegmentEntry 1334 MAX-ACCESS not-accessible 1335 STATUS current 1336 DESCRIPTION 1337 "An entry in this table represents one incoming 1338 segment. An entry can be created by a network 1339 administrator or an SNMP agent, or an MPLS signaling 1340 protocol. The creator of the entry is denoted by 1341 mplsOutSegmentOwner. An entry in this table is 1342 indexed by the ifIndex of the incoming interface and 1343 the (top) label. Note that since it is possible 1344 that some segments are associated with a tunnel, 1345 traffic parameters of these rows are supported as 1346 read-only objects and their modification can be done 1347 only via the tunnel table, mplsTunnelTable." 1348 REFERENCE 1349 "MPLS Traffic Engineering Management Information Base 1350 Using SMIv2, Srinivasan, Viswanathan and Nadeau, 1351 draft-ietf-mpls-te-mib-02.txt, February 2000." 1353 INDEX { mplsOutSegmentIndex } 1354 ::= { mplsOutSegmentTable 1 } 1356 MplsOutSegmentEntry ::= SEQUENCE { 1357 mplsOutSegmentIndex Integer32, 1358 mplsOutSegmentIfIndex InterfaceIndex, 1359 mplsOutSegmentPushTopLabel TruthValue, 1360 mplsOutSegmentTopLabel MplsLabel, 1361 mplsOutSegmentNextHopIpAddrType INTEGER, 1362 mplsOutSegmentNextHopIpv4Addr IpAddress, 1363 mplsOutSegmentNextHopIpv6Addr Ipv6Address, 1364 mplsOutSegmentXCIndex Integer32, 1365 mplsOutSegmentTSpecIndex Unsigned32, 1366 mplsOutSegmentOwner INTEGER, 1367 mplsOutSegmentAdminStatus INTEGER, 1368 mplsOutSegmentOperStatus INTEGER, 1369 mplsOutSegmentRowStatus RowStatus 1370 } 1372 mplsOutSegmentIndex OBJECT-TYPE 1373 SYNTAX Integer32 (1..2147483647) 1374 MAX-ACCESS read-create 1375 STATUS current 1376 DESCRIPTION 1377 "This value contains a unique index for this row. 1378 While a value of 0 is not valid as an index for this 1379 row it can be supplied as a valid value to index 1380 mplsXCTable to access entries for which no out- 1381 segment has been configured." 1382 ::= { mplsOutSegmentEntry 1 } 1384 mplsOutSegmentIfIndex OBJECT-TYPE 1385 SYNTAX InterfaceIndex 1386 MAX-ACCESS read-create 1387 STATUS current 1388 DESCRIPTION 1389 "This value contains the interface index of the 1390 outgoing interface." 1391 ::= { mplsOutSegmentEntry 2 } 1393 mplsOutSegmentPushTopLabel OBJECT-TYPE 1394 SYNTAX TruthValue 1395 MAX-ACCESS read-create 1396 STATUS current 1397 DESCRIPTION 1398 "This value indicates whether or not a top label 1399 should be pushed onto the outgoing packet's label 1400 stack. The value of this variable must be set to 1401 true if the outgoing interface is ATM, which does 1402 not support pop-and-go, or if it is a tunnel 1403 origination. Note that it is considered an error in 1404 the case that mplsOutSegmentPushTopLabel is set to 1405 false, but the cross-connect entry which refers to 1406 this out-segment has a non-zero mplsLabelStackIndex. 1407 The LSR should ensure that this situation cannot 1408 happen " 1409 ::= { mplsOutSegmentEntry 3 } 1411 mplsOutSegmentTopLabel OBJECT-TYPE 1412 SYNTAX MplsLabel 1413 MAX-ACCESS read-create 1414 STATUS current 1415 DESCRIPTION 1416 "If mplsOutSegmentPushTopLabel is true then this is 1417 the label that should be pushed onto the outgoing 1418 packet's label stack. Note that the contents of the 1419 label field can be interpreted in an outgoing 1420 interface specific fashion. For example, the label 1421 carried in the MPLS shim header is 20 bits wide and 1422 the top 12 bits must be zero. The Frame Relay label 1423 is 24 bits wide and the top 8 bits must be zero. 1424 For ATM interfaces the lowermost 16 bits are 1425 interpreted as the VCI, the next 8 bits as the VPI 1426 and the remaining bits must be zero." 1427 ::= { mplsOutSegmentEntry 4 } 1429 mplsOutSegmentNextHopIpAddrType OBJECT-TYPE 1430 SYNTAX INTEGER { none (1), ipV4 (2), ipV6 (3) } 1431 MAX-ACCESS read-create 1432 STATUS current 1433 DESCRIPTION 1434 "Indicates whether the next hop address is IPv4 or 1435 IPv6. Note that a value of none (1) is valid only 1436 when the outgoing interface is of type point-to- 1437 point." 1439 DEFVAL { none } 1440 ::= { mplsOutSegmentEntry 5 } 1442 mplsOutSegmentNextHopIpv4Addr OBJECT-TYPE 1443 SYNTAX IpAddress 1444 MAX-ACCESS read-create 1445 STATUS current 1446 DESCRIPTION 1447 "IPv4 Address of the next hop. Its value is 1448 significant only when 1449 mplsOutSegmentNextHopIpAddrType is ipV4 (2), 1450 otherwise it should return a value of 0." 1451 ::= { mplsOutSegmentEntry 6 } 1453 mplsOutSegmentNextHopIpv6Addr OBJECT-TYPE 1454 SYNTAX Ipv6Address 1455 MAX-ACCESS read-create 1456 STATUS current 1457 DESCRIPTION 1458 "IPv6 address of the next hop. Its value is 1459 significant only when 1460 mplsOutSegmentNextHopIpAddrType is ipV6 (3), 1461 otherwise it should return a value of 0." 1462 ::= { mplsOutSegmentEntry 7 } 1464 mplsOutSegmentXCIndex OBJECT-TYPE 1465 SYNTAX Integer32 (1..2147483647) 1466 MAX-ACCESS read-create 1467 STATUS current 1468 DESCRIPTION 1469 "Index into mplsXCTable which identifies which cross- 1470 connect entry this segment is part of. A value of 1471 zero indicates that this entry is not referred to by 1472 any cross-connect entry." 1473 DEFVAL { 0 } 1474 ::= { mplsOutSegmentEntry 8 } 1476 mplsOutSegmentTSpecIndex OBJECT-TYPE 1477 SYNTAX Unsigned32 1478 MAX-ACCESS read-create 1479 STATUS current 1480 DESCRIPTION 1481 "A pointer into the mplsTSpecTable indicating the 1482 TSpec to be assigned for this segment. A value of 1483 zero indicates best-effort treatment. Two or more 1484 segments can indicate resource sharing by pointing 1485 to the same entry in mplsTSpecTable." 1486 DEFVAL { 0 } 1487 ::= { mplsOutSegmentEntry 9 } 1489 mplsOutSegmentOwner OBJECT-TYPE 1490 SYNTAX INTEGER { 1491 snmp(1), 1492 ldp(2), 1493 rsvp(3), 1494 policyAgent(4), 1495 other(5) 1496 } 1497 MAX-ACCESS read-create 1498 STATUS current 1499 DESCRIPTION 1500 "Denotes the entity which created and is responsible 1501 for managing this segment." 1503 ::= { mplsOutSegmentEntry 10 } 1505 mplsOutSegmentAdminStatus OBJECT-TYPE 1506 SYNTAX INTEGER { 1507 up(1), -- ready to pass packets 1508 down(2), 1509 testing(3) -- in some test mode 1510 } 1511 MAX-ACCESS read-create 1512 STATUS current 1513 DESCRIPTION 1514 "The desired operational status of this segment." 1515 ::= { mplsOutSegmentEntry 11 } 1517 mplsOutSegmentOperStatus OBJECT-TYPE 1518 SYNTAX INTEGER { 1519 up(1), -- ready to pass packets 1520 down(2), 1521 testing(3), -- in some test mode 1522 unknown(4), -- status cannot be determined for 1523 -- some reason 1524 dormant(5), 1525 notPresent(6), -- some component is missing 1526 lowerLayerDown(7) 1527 -- down due to the state of 1528 -- lower layer interfaces 1529 } 1530 MAX-ACCESS read-only 1531 STATUS current 1532 DESCRIPTION 1533 "The actual operational status of this segment." 1534 ::= { mplsOutSegmentEntry 12 } 1536 mplsOutSegmentRowStatus OBJECT-TYPE 1537 SYNTAX RowStatus 1538 MAX-ACCESS read-create 1539 STATUS current 1540 DESCRIPTION 1541 "For creating, modifying, and deleting this row." 1542 ::= { mplsOutSegmentEntry 13 } 1544 -- End of mplsOutSegmentTable 1546 -- Out-segment performance table. 1548 mplsOutSegmentPerfTable OBJECT-TYPE 1549 SYNTAX SEQUENCE OF MplsOutSegmentPerfEntry 1550 MAX-ACCESS not-accessible 1551 STATUS current 1552 DESCRIPTION 1553 "This table contains statistical information about 1554 incoming segments to an LSR. The counters in this 1555 entry should behave in a manner similar to that of 1556 the interface." 1557 ::= { mplsLsrObjects 7 } 1559 mplsOutSegmentPerfEntry OBJECT-TYPE 1560 SYNTAX MplsOutSegmentPerfEntry 1561 MAX-ACCESS not-accessible 1562 STATUS current 1563 DESCRIPTION 1564 "An entry in this table contains statistical 1565 information about one incoming segment configured in 1566 mplsOutSegmentTable." 1567 AUGMENTS { mplsOutSegmentEntry } 1568 ::= { mplsOutSegmentPerfTable 1 } 1570 MplsOutSegmentPerfEntry ::= SEQUENCE { 1571 mplsOutSegmentOctets Counter32, 1572 mplsOutSegmentPackets Counter32, 1573 mplsOutSegmentErrors Counter32, 1574 mplsOutSegmentDiscards Counter32, 1576 -- HC counter 1577 mplsOutSegmentHCOctets Counter64 1578 } 1580 mplsOutSegmentOctets OBJECT-TYPE 1581 SYNTAX Counter32 1582 MAX-ACCESS read-only 1583 STATUS current 1584 DESCRIPTION 1585 "This value contains the total number of octets sent 1586 on this segment." 1587 ::= { mplsOutSegmentPerfEntry 1 } 1589 mplsOutSegmentPackets OBJECT-TYPE 1590 SYNTAX Counter32 1591 MAX-ACCESS read-only 1592 STATUS current 1593 DESCRIPTION 1594 "This value contains the total number of packets sent 1595 on this segment." 1596 ::= { mplsOutSegmentPerfEntry 2 } 1598 mplsOutSegmentErrors OBJECT-TYPE 1599 SYNTAX Counter32 1600 MAX-ACCESS read-only 1601 STATUS current 1602 DESCRIPTION 1603 "Number of packets that could not be sent due to 1604 errors on this segment." 1605 ::= { mplsOutSegmentPerfEntry 3 } 1607 mplsOutSegmentDiscards OBJECT-TYPE 1608 SYNTAX Counter32 1609 MAX-ACCESS read-only 1610 STATUS current 1611 DESCRIPTION 1612 "The number of labeled packets received on this out- 1613 segment, which were chosen to be discarded even 1614 though no errors had been detected to prevent their 1615 being transmitted. One possible reason for 1616 discarding such a labeled packet could be to free up 1617 buffer space." 1618 ::= { mplsOutSegmentPerfEntry 4 } 1620 mplsOutSegmentHCOctets OBJECT-TYPE 1621 SYNTAX Counter64 1622 MAX-ACCESS read-only 1623 STATUS current 1624 DESCRIPTION 1625 "Total number of octets sent. This is the 64 bit 1626 version of mplsOutSegmentOctets." 1627 ::= { mplsOutSegmentPerfEntry 5 } 1629 -- End of mplsOutSegmentPerfTable. 1631 -- Cross-connect table. 1633 mplsXCIndexNext OBJECT-TYPE 1634 SYNTAX Integer32 (1..2147483647) 1635 MAX-ACCESS read-only 1636 STATUS current 1637 DESCRIPTION 1638 "This object contains an appropriate value to be used 1639 for mplsXCIndex when creating entries in the 1640 mplsXCTable. The value 0 indicates that no 1641 unassigned entries are available. To obtain the 1642 value of mplsXCIndex for a new entry in the 1643 mplsXCTable, the manager issues a management 1644 protocol retrieval operation to obtain the current 1645 value of mplsXCIndex. After each retrieval 1646 operation, the agent should modify the value to 1647 reflect the next unassigned index. After a manager 1648 retrieves a value the agent will determine through 1649 its local policy when this index value will be made 1650 available for reuse." 1651 ::= { mplsLsrObjects 8 } 1653 mplsXCTable OBJECT-TYPE 1654 SYNTAX SEQUENCE OF MplsXCEntry 1655 MAX-ACCESS not-accessible 1656 STATUS current 1657 DESCRIPTION 1658 "This table specifies information for switching 1659 between LSP segments. It supports point-to-point, 1660 point-to-multipoint and multipoint-to-point 1661 connections. mplsLabelStackTable specifies the 1662 label stack information for a cross-connect LSR and 1663 is referred to from mplsXCTable." 1664 ::= { mplsLsrObjects 9 } 1666 mplsXCEntry OBJECT-TYPE 1667 SYNTAX MplsXCEntry 1668 MAX-ACCESS not-accessible 1669 STATUS current 1670 DESCRIPTION 1671 "A row in this table represents one cross-connect 1672 entry. The following objects index it: 1674 - cross-connect index mplsXCIndex that uniquely 1675 identifies a group of cross-connect entries 1676 - interface index of the in-segment, 1677 mplsInSegmentIfIndex 1678 - incoming label(s), mplsInSegmentLabel 1679 - out-segment index, mplsOutSegmentIndex 1681 Originating LSPs: 1682 These are represented by using the special 1683 combination of values mplsInSegmentIfIndex=0 and 1684 mplsInSegmentLabel=0 as indexes. In this case the 1685 mplsOutSegmentIndex MUST be non-zero. 1687 Terminating LSPs: 1688 These are represented by using the special value 1689 mplsOutSegmentIndex=0 as index. 1691 Special labels: 1693 Entries indexed by reserved MPLS label values 0 1694 through 15 imply terminating LSPs and MUST have 1695 mplsOutSegmentIfIndex = 0. Note that situations 1696 where LSPs are terminated with incoming label equal 1697 to 0, should have mplsInSegmentIfIndex = 0 as well, 1698 but can be distinguished from originating LSPs 1699 because the mplsOutSegmentIfIndex = 0. The 1700 mplsOutSegmentIfIndex MUST only be set to 0 in 1701 cases of terminating LSPs. 1703 An entry can be created by a network administrator 1704 or by an SNMP agent as instructed by an MPLS 1705 signaling protocol." 1706 INDEX { mplsXCIndex, mplsInSegmentIfIndex, 1707 mplsInSegmentLabel, mplsOutSegmentIndex } 1708 ::= { mplsXCTable 1 } 1710 MplsXCEntry ::= SEQUENCE { 1711 mplsXCIndex Integer32, 1712 mplsXCLspId MplsLSPID, 1713 mplsXCLabelStackIndex Integer32, 1714 mplsXCCOS Integer32, 1715 mplsXCIsPersistent TruthValue, 1716 mplsXCOwner INTEGER, 1717 mplsXCAdminStatus INTEGER, 1718 mplsXCOperStatus INTEGER, 1719 mplsXCRowStatus RowStatus 1720 } 1722 mplsXCIndex OBJECT-TYPE 1723 SYNTAX Integer32 1724 MAX-ACCESS read-create 1725 STATUS current 1726 DESCRIPTION 1727 "Primary index for the row identifying a group of 1728 cross-connect segments." 1729 ::= { mplsXCEntry 1 } 1731 mplsXCLspId OBJECT-TYPE 1732 SYNTAX MplsLSPID 1733 MAX-ACCESS read-create 1734 STATUS current 1735 DESCRIPTION 1736 "This value identifies the label switched path that 1737 this cross-connect entry belongs to." 1738 ::= { mplsXCEntry 2 } 1740 mplsXCLabelStackIndex OBJECT-TYPE 1741 SYNTAX Integer32 1742 MAX-ACCESS read-create 1743 STATUS current 1744 DESCRIPTION 1745 "Primary index into mplsLabelStackTable identifying a 1746 stack of labels to be pushed beneath the top label. 1747 Note that the top label identified by the out- 1748 segment ensures that all the components of a 1749 multipoint-to-point connection have the same 1750 outgoing label. A value of 0 indicates that no 1751 labels are to be stacked beneath the top label." 1752 ::= { mplsXCEntry 3 } 1754 mplsXCCOS OBJECT-TYPE 1755 SYNTAX Integer32 1756 MAX-ACCESS read-create 1757 STATUS current 1758 DESCRIPTION 1759 "This value is used to override the incoming COS 1760 field for a cross-connect. It may also be used as a 1761 value to assign to outgoing packets for an outgoing 1762 segment of a tunnel. Note that packet treatment at 1763 this LSR is determined by the incoming COS value and 1764 the new COS value only impacts packet treatment at a 1765 downstream LSR." 1766 ::= { mplsXCEntry 4 } 1768 mplsXCIsPersistent OBJECT-TYPE 1769 SYNTAX TruthValue 1770 MAX-ACCESS read-create 1771 STATUS current 1772 DESCRIPTION 1773 "Denotes whether or not this cross-connect entry and 1774 associated in- and out-segments should be restored 1775 automatically after failures. This value MUST be set 1776 to false in cases where this cross-connect entry was 1777 created by a signaling protocol." 1778 DEFVAL { false } 1779 ::= { mplsXCEntry 5 } 1781 mplsXCOwner OBJECT-TYPE 1782 SYNTAX INTEGER { 1783 snmp(1), 1784 ldp(2), 1785 rsvp(3), 1786 policyAgent(4), 1787 other(5) 1788 } 1790 MAX-ACCESS read-create 1791 STATUS current 1792 DESCRIPTION 1793 "Denotes the entity that created and is responsible 1794 for managing this cross-connect." 1795 ::= { mplsXCEntry 6 } 1797 mplsXCAdminStatus OBJECT-TYPE 1798 SYNTAX INTEGER { 1799 up(1), -- ready to pass packets 1800 down(2), 1801 testing(3) -- in some test mode 1802 } 1803 MAX-ACCESS read-create 1804 STATUS current 1805 DESCRIPTION 1806 "The desired operational status of this segment." 1807 ::= { mplsXCEntry 7 } 1809 mplsXCOperStatus OBJECT-TYPE 1810 SYNTAX INTEGER { 1811 up(1), -- ready to pass packets 1812 down(2), 1813 testing(3), -- in some test mode 1814 unknown(4), -- status cannot be determined for 1815 -- some reason 1816 dormant(5), 1817 notPresent(6), -- some component is missing 1818 lowerLayerDown(7) 1819 -- down due to the state of 1820 -- lower layer interfaces 1821 } 1823 MAX-ACCESS read-only 1824 STATUS current 1825 DESCRIPTION 1826 "The actual operational status of this cross- 1827 connect." 1828 ::= { mplsXCEntry 8 } 1830 mplsXCRowStatus OBJECT-TYPE 1831 SYNTAX RowStatus 1832 MAX-ACCESS read-create 1833 STATUS current 1834 DESCRIPTION 1835 "For creating, modifying, and deleting this row." 1836 ::= { mplsXCEntry 9 } 1838 -- End of mplsXCTable 1840 -- Label stack table. 1841 mplsMaxLabelStackDepth OBJECT-TYPE 1842 SYNTAX Integer32 1843 MAX-ACCESS read-only 1844 STATUS current 1845 DESCRIPTION 1846 "The maximum stack depth supported by this LSR." 1847 ::= { mplsLsrObjects 10 } 1849 mplsLabelStackIndexNext OBJECT-TYPE 1850 SYNTAX Unsigned32 1851 MAX-ACCESS read-only 1852 STATUS current 1853 DESCRIPTION 1854 "This object contains an appropriate value to be used 1855 for mplsLabelStackIndex when creating entries in the 1856 mplsLabelStackTable. The value 0 indicates that no 1857 unassigned entries are available. To obtain an 1858 mplsLabelStackIndex value for a new entry, the 1859 manager issues a management protocol retrieval 1860 operation to obtain the current value of this 1861 object. After each retrieval operation, the agent 1862 should modify the value to reflect the next 1863 unassigned index. After a manager retrieves a value 1864 the agent will determine through its local policy 1865 when this index value will be made available for 1866 reuse." 1867 ::= { mplsLsrObjects 11 } 1869 mplsLabelStackTable OBJECT-TYPE 1870 SYNTAX SEQUENCE OF MplsLabelStackEntry 1871 MAX-ACCESS not-accessible 1872 STATUS current 1873 DESCRIPTION 1874 "This table specifies the label stack to be pushed 1875 onto a packet, beneath the top label. Entries into 1876 this table are referred to from mplsXCTable." 1877 ::= { mplsLsrObjects 12 } 1879 mplsLabelStackEntry OBJECT-TYPE 1880 SYNTAX MplsLabelStackEntry 1881 MAX-ACCESS not-accessible 1882 STATUS current 1883 DESCRIPTION 1884 "An entry in this table represents one label which is 1885 to be pushed onto an outgoing packet, beneath the 1886 top label. An entry can be created by a network 1887 administrator or by an SNMP agent as instructed by 1888 an MPLS signaling protocol." 1889 INDEX { mplsLabelStackIndex, mplsLabelStackLabelIndex } 1890 ::= { mplsLabelStackTable 1 } 1892 MplsLabelStackEntry ::= SEQUENCE { 1893 mplsLabelStackIndex Integer32, 1894 mplsLabelStackLabelIndex Integer32, 1895 mplsLabelStackLabel MplsLabel, 1896 mplsLabelStackRowStatus RowStatus 1897 } 1899 mplsLabelStackIndex OBJECT-TYPE 1900 SYNTAX Integer32 (1..2147483647) 1901 MAX-ACCESS read-create 1902 STATUS current 1903 DESCRIPTION 1904 "Primary index for this row identifying a stack of 1905 labels to be pushed on an outgoing packet, beneath 1906 the top label." 1907 ::= { mplsLabelStackEntry 1 } 1909 mplsLabelStackLabelIndex OBJECT-TYPE 1910 SYNTAX Integer32 (1..2147483647) 1911 MAX-ACCESS not-accessible 1912 STATUS current 1913 DESCRIPTION 1914 "Secondary index for this row identifying one label 1915 of the stack. Note that an entry with a smaller 1916 mplsLabelStackLabelIndex would refer to a label 1917 higher up the label stack and would be popped at a 1918 downstream LSR before a label represented by a 1919 higher mplsLabelStackLabelIndex at a downstream 1920 LSR." 1921 ::= { mplsLabelStackEntry 2 } 1923 mplsLabelStackLabel OBJECT-TYPE 1924 SYNTAX MplsLabel 1925 MAX-ACCESS read-create 1926 STATUS current 1927 DESCRIPTION 1928 "The label to pushed." 1929 ::= { mplsLabelStackEntry 3 } 1931 mplsLabelStackRowStatus OBJECT-TYPE 1932 SYNTAX RowStatus 1933 MAX-ACCESS read-create 1934 STATUS current 1935 DESCRIPTION 1936 "For creating, modifying, and deleting this row." 1937 ::= { mplsLabelStackEntry 4 } 1939 -- End of mplsLabelStackTable 1941 -- TSpec table. 1943 mplsTSpecIndexNext OBJECT-TYPE 1944 SYNTAX Integer32 (1..2147483647) 1945 MAX-ACCESS read-only 1946 STATUS current 1947 DESCRIPTION 1948 "This object contains an appropriate value which will 1949 be used for mplsTSpecIndex when creating entries in 1950 the mplsTSpecTable. The value 0 indicates that no 1951 unassigned entries are available. To obtain the 1952 mplsTSpecIndex value for a new entry, the manager 1953 issues a management protocol retrieval operation to 1954 obtain the current value of this object. After each 1955 retrieval operation, the agent should modify the 1956 value to reflect the next unassigned index. After a 1957 manager retrieves a value the agent will determine 1958 through its local policy when this index value will 1959 be made available for reuse." 1960 ::= { mplsLsrObjects 13 } 1962 mplsTSpecTable OBJECT-TYPE 1963 SYNTAX SEQUENCE OF MplsTSpecEntry 1964 MAX-ACCESS not-accessible 1965 STATUS current 1966 DESCRIPTION 1967 "This table specifies the Traffic Specification 1968 (TSpec) objects for in and out-segments." 1969 ::= { mplsLsrObjects 14 } 1971 mplsTSpecEntry OBJECT-TYPE 1972 SYNTAX MplsTSpecEntry 1973 MAX-ACCESS not-accessible 1974 STATUS current 1975 DESCRIPTION 1976 "An entry in this table represents the TSpec objects 1977 for one or more in or out segments. A single entry 1978 can be pointed to by multiple segments indicating 1979 resource sharing." 1980 INDEX { mplsTSpecIndex } 1981 ::= { mplsTSpecTable 1 } 1983 MplsTSpecEntry ::= SEQUENCE { 1984 mplsTSpecIndex Integer32, 1985 mplsTSpecMaxRate MplsBitRate, 1986 mplsTSpecMeanRate MplsBitRate, 1987 mplsTSpecMaxBurstSize MplsBurstSize, 1988 mplsTSpecRowStatus RowStatus 1989 } 1991 mplsTSpecIndex OBJECT-TYPE 1992 SYNTAX Integer32 (1..2147483647) 1993 MAX-ACCESS read-create 1994 STATUS current 1995 DESCRIPTION 1996 "Uniquely identifies this row of the table. Note 1997 that zero represents an invalid index." 1998 ::= { mplsTSpecEntry 1 } 2000 mplsTSpecMaxRate OBJECT-TYPE 2001 SYNTAX MplsBitRate 2002 UNITS "bits per second" 2003 MAX-ACCESS read-create 2004 STATUS current 2005 DESCRIPTION 2006 "Maximum rate in bits/second." 2007 ::= { mplsTSpecEntry 4 } 2009 mplsTSpecMeanRate OBJECT-TYPE 2010 SYNTAX MplsBitRate 2011 UNITS "bits per second" 2012 MAX-ACCESS read-create 2013 STATUS current 2014 DESCRIPTION 2015 "Mean rate in bits/second." 2016 ::= { mplsTSpecEntry 5 } 2018 mplsTSpecMaxBurstSize OBJECT-TYPE 2019 SYNTAX MplsBurstSize 2020 UNITS "bytes" 2021 MAX-ACCESS read-create 2022 STATUS current 2023 DESCRIPTION 2024 "Maximum burst size in bytes." 2025 ::= { mplsTSpecEntry 6 } 2027 mplsTSpecRowStatus OBJECT-TYPE 2028 SYNTAX RowStatus 2029 MAX-ACCESS read-create 2030 STATUS current 2031 DESCRIPTION 2032 "For creating, modifying, and deleting this row." 2033 ::= { mplsTSpecEntry 7 } 2035 -- End of mplsTSpecTable 2037 -- Notification Configuration 2039 mplsInterfaceTrapEnable OBJECT-TYPE 2040 SYNTAX TruthValue 2041 MAX-ACCESS read-write 2042 STATUS current 2043 DESCRIPTION 2044 "If this object is true, then it enables the 2045 generation of mplsInterfaceUp and mplsInterfaceDown 2046 traps, otherwise these traps are not emitted." 2047 DEFVAL { false } 2048 ::= { mplsLsrObjects 15 } 2050 mplsInSegmentTrapEnable OBJECT-TYPE 2051 SYNTAX TruthValue 2052 MAX-ACCESS read-write 2053 STATUS current 2054 DESCRIPTION 2055 "If this object is true, then it enables the 2056 generation of mplsInSegmentUp and mplsInSegmentDown 2057 traps, otherwise these traps are not emitted." 2058 DEFVAL { false } 2059 ::= { mplsLsrObjects 16 } 2061 mplsOutSegmentTrapEnable OBJECT-TYPE 2062 SYNTAX TruthValue 2063 MAX-ACCESS read-write 2064 STATUS current 2065 DESCRIPTION 2066 "If this object is true, then it enables the 2067 generation of mplsOutSegmentUp and 2068 mplsOutSegmentDown traps, otherwise these traps are 2069 not emitted." 2070 DEFVAL { false } 2071 ::= { mplsLsrObjects 17 } 2073 mplsXCTrapEnable OBJECT-TYPE 2074 SYNTAX TruthValue 2075 MAX-ACCESS read-write 2076 STATUS current 2077 DESCRIPTION 2078 "If this object is true, then it enables the 2079 generation of mplsXCUp and mplsXCDown traps, 2080 otherwise these traps are not emitted." 2081 DEFVAL { false } 2082 ::= { mplsLsrObjects 18 } 2084 -- Interface 2086 mplsInterfaceUp NOTIFICATION-TYPE 2087 OBJECTS { mplsInterfaceConfIndex, 2088 mplsInterfaceAdminStatus, mplsInterfaceOperStatus } 2089 STATUS current 2090 DESCRIPTION 2091 "This notification is generated when a 2092 mplsInterfaceOperStatus object for one of the 2093 entries in mplsInterfaceConfTable is about to leave 2094 the down state and transition into some other state 2095 (but not into the notPresent state). This other 2096 state is indicated by the included value of 2097 mplsInterfaceOperStatus." 2098 ::= { mplsLsrNotifications 1 } 2100 mplsInterfaceDown NOTIFICATION-TYPE 2101 OBJECTS { mplsInterfaceConfIndex, 2102 mplsInterfaceAdminStatus, mplsInterfaceOperStatus } 2103 STATUS current 2104 DESCRIPTION 2105 "This notification is generated when a 2106 mplsInterfaceOperStatus object for one of the 2107 entries in mplsInterfaceConfTable is about to enter 2108 the down state from some other state (but not from 2109 the notPresent state). This other state is 2110 indicated by the included value of 2111 mplsInterfaceOperStatus." 2112 ::= { mplsLsrNotifications 2 } 2114 -- In-segment. 2116 mplsInSegmentUp NOTIFICATION-TYPE 2117 OBJECTS { mplsInSegmentIfIndex, mplsInSegmentLabel, 2118 mplsInSegmentAdminStatus, mplsInSegmentOperStatus } 2119 STATUS current 2120 DESCRIPTION 2121 "This notification is generated when a 2122 mplsInSegmentOperStatus object for one of the 2123 configured in-segments is about to leave the down 2124 state and transition into some other state (but not 2125 into the notPresent state). This other state is 2126 indicated by the included value of 2127 mplsInSegmentOperStatus." 2128 ::= { mplsLsrNotifications 3 } 2130 mplsInSegmentDown NOTIFICATION-TYPE 2131 OBJECTS { mplsInSegmentIfIndex, mplsInSegmentLabel, 2132 mplsInSegmentAdminStatus, mplsInSegmentOperStatus } 2133 STATUS current 2134 DESCRIPTION 2135 "This notification is generated when a 2136 mplsInSegmentOperStatus object for one of the 2137 configured in-segments is about to enter the down 2138 state from some other state (but not from the 2139 notPresent state). This other state is indicated by 2140 the included value of mplsInSegmentOperStatus." 2142 ::= { mplsLsrNotifications 4 } 2144 -- Out-segment. 2146 mplsOutSegmentUp NOTIFICATION-TYPE 2147 OBJECTS { mplsOutSegmentIndex, mplsInSegmentAdminStatus, 2148 mplsInSegmentOperStatus } 2149 STATUS current 2150 DESCRIPTION 2151 "This notification is generated when a 2152 mplsOutSegmentOperStatus object for one of the 2153 configured out-segments is about to leave the down 2154 state and transition into some other state (but not 2155 into the notPresent state). This other state is 2156 indicated by the included value of 2157 mplsOutSegmentOperStatus." 2158 ::= { mplsLsrNotifications 5 } 2160 mplsOutSegmentDown NOTIFICATION-TYPE 2161 OBJECTS { mplsOutSegmentIndex, mplsInSegmentAdminStatus, 2162 mplsInSegmentOperStatus } 2163 STATUS current 2164 DESCRIPTION 2165 "This notification is generated when a 2166 mplsOutSegmentOperStatus object for one of the 2167 configured out-segments is about to enter the down 2168 state from some other state (but not from the 2169 notPresent state). This other state is indicated by 2170 the included value of mplsOutSegmentOperStatus." 2171 ::= { mplsLsrNotifications 6 } 2173 -- Cross-connect. 2175 mplsXCUp NOTIFICATION-TYPE 2176 OBJECTS { mplsXCIndex, 2177 mplsInSegmentIfIndex, mplsInSegmentLabel, 2178 mplsOutSegmentIndex, 2179 mplsXCAdminStatus, mplsXCOperStatus } 2180 STATUS current 2181 DESCRIPTION 2182 "This notification is generated when a 2183 mplsXCOperStatus object for one of the configured 2184 cross-connect entries is about to leave the down 2185 state and transition into some other state (but not 2186 into the notPresent state). This other state is 2187 indicated by the included value of 2188 mplsXCOperStatus." 2189 ::= { mplsLsrNotifications 7 } 2191 mplsXCDown NOTIFICATION-TYPE 2192 OBJECTS { mplsXCIndex, 2193 mplsInSegmentIfIndex, mplsInSegmentLabel, 2194 mplsOutSegmentIndex, 2195 mplsXCAdminStatus, mplsXCOperStatus } 2196 STATUS current 2197 DESCRIPTION 2198 "This notification is generated when a 2199 mplsXCOperStatus object for one of the configured 2200 cross-connect entries is about to enter the down 2201 state from some other state (but not from the 2202 notPresent state). This other state is indicated by 2203 the included value of mplsXCOperStatus." 2204 ::= { mplsLsrNotifications 8 } 2206 -- End of notifications. 2208 -- Module compliance. 2210 mplsLsrGroups 2211 OBJECT IDENTIFIER ::= { mplsLsrConformance 1 } 2213 mplsLsrCompliances 2214 OBJECT IDENTIFIER ::= { mplsLsrConformance 2 } 2216 mplsLsrModuleCompliance MODULE-COMPLIANCE 2217 STATUS current 2218 DESCRIPTION 2219 "Compliance statement for agents that support the 2220 MPLS LSR MIB." 2221 MODULE -- this module 2223 -- The mandatory groups have to be implemented by all LSRs. 2224 -- However, they may all be supported as read-only objects 2225 -- in the case where manual configuration is unsupported. 2227 MANDATORY-GROUPS { mplsInSegmentGroup, mplsOutSegmentGroup, 2228 mplsXCGroup, mplsInterfaceGroup, 2229 mplsPerfGroup } 2231 GROUP mplsHCInterfacePerfGroup 2232 DESCRIPTION 2233 "This group is mandatory for high-speed MPLS 2234 capable interfaces for which the objects 2235 mplsInterfaceInOctets and mplsInterfaceOutOctets 2236 wrap around too quickly." 2238 GROUP mplsHCInSegmentPerfGroup 2239 DESCRIPTION 2240 "This group is mandatory for those in-segment 2241 entries for which the object 2242 mplsInSegmentOutOctets wraps around too 2243 quickly." 2245 GROUP mplsHCOutSegmentPerfGroup 2246 DESCRIPTION 2247 "This group is mandatory for those out-segment 2248 entries for which the object 2249 mplsOutSegmentOctets wraps around too quickly." 2251 GROUP mplsTSpecGroup 2252 DESCRIPTION 2253 "This group is mandatory for those LSRs that 2254 support Int-Serv style resource reservation." 2256 -- Depending on whether the device implements persistent 2257 -- cross-connects or not one of the following two groups 2258 -- is mandatory. 2260 GROUP mplsXCIsPersistentGroup 2261 DESCRIPTION 2262 "This group is mandatory for devices which 2263 support persistent cross-connects. The 2264 following constraints apply: mplsXCIsPersistent 2265 must at least be read-only returning true(2)." 2267 GROUP mplsXCIsNotPersistentGroup 2268 DESCRIPTION 2269 "This group is mandatory for devices which 2270 support non-persistent cross-connects. The 2271 following constraints apply: mplsXCIsPersistent 2272 must at least be read-only returning false(1)." 2274 -- mplsInterfaceConfTable 2276 OBJECT mplsInterfaceAdminStatus 2277 SYNTAX INTEGER { up(1), down(2) } 2278 MIN-ACCESS read-only 2279 DESCRIPTION 2280 "A value of testing(3) need not be supported." 2282 OBJECT mplsInterfaceOperStatus 2283 SYNTAX INTEGER { up(1), down(2) } 2284 MIN-ACCESS read-only 2285 DESCRIPTION 2286 "Only up(1) and down(2) need to be supported." 2288 -- mplsInSegmentTable 2290 OBJECT mplsInSegmentIfIndex 2291 MIN-ACCESS read-only 2292 DESCRIPTION 2293 "Write access is not required." 2295 OBJECT mplsInSegmentLabel 2296 MIN-ACCESS read-only 2297 DESCRIPTION 2298 "Write access is not required." 2300 OBJECT mplsInSegmentXCIndex 2301 MIN-ACCESS read-only 2302 DESCRIPTION 2303 "Write access is not required." 2305 OBJECT mplsInSegmentTSpecIndex 2306 MIN-ACCESS read-only 2307 DESCRIPTION 2308 "Write access is not required." 2310 OBJECT mplsInSegmentNPop 2311 MIN-ACCESS read-only 2312 DESCRIPTION 2313 "Write access if not required. This object 2314 should be set to 1 if it is read-only." 2316 OBJECT mplsInSegmentAddrFamily 2317 SYNTAX INTEGER { other(0) } 2318 MIN-ACCESS read-only 2319 DESCRIPTION 2320 "Write access is not required. A value of 2321 other(0) should be supported." 2323 OBJECT mplsInSegmentAdminStatus 2324 SYNTAX INTEGER { up(1), down(2) } 2325 MIN-ACCESS read-only 2326 DESCRIPTION 2327 "A value of testing(3) need not be supported." 2329 OBJECT mplsInSegmentOperStatus 2330 SYNTAX INTEGER { up(1), down(2) } 2331 MIN-ACCESS read-only 2332 DESCRIPTION 2333 "Only up(1) and down(2) need to be supported." 2335 -- mplsOutSegmentTable 2337 OBJECT mplsOutSegmentIndexNext 2338 MIN-ACCESS read-only 2339 DESCRIPTION 2340 "Write access is not required." 2342 OBJECT mplsOutSegmentIndex 2343 MIN-ACCESS read-only 2344 DESCRIPTION 2345 "Write access is not required." 2347 OBJECT mplsOutSegmentIfIndex 2348 MIN-ACCESS read-only 2349 DESCRIPTION 2350 "Write access is not required." 2352 OBJECT mplsOutSegmentPushTopLabel 2353 MIN-ACCESS read-only 2354 DESCRIPTION 2355 "Write access is not required." 2357 OBJECT mplsOutSegmentTopLabel 2358 MIN-ACCESS read-only 2359 DESCRIPTION 2360 "Write access is not required." 2362 OBJECT mplsOutSegmentNextHopIpAddrType 2363 SYNTAX INTEGER { none(1), ipV4(2) } 2364 MIN-ACCESS read-only 2365 DESCRIPTION 2366 "ipV6(3) need not be supported." 2368 OBJECT mplsOutSegmentNextHopIpv4Addr 2369 MIN-ACCESS read-only 2370 DESCRIPTION 2371 "Write access is not required." 2373 OBJECT mplsOutSegmentNextHopIpv6Addr 2374 MIN-ACCESS read-only 2375 DESCRIPTION 2376 "Write access is not required." 2378 OBJECT mplsOutSegmentXCIndex 2379 MIN-ACCESS read-only 2380 DESCRIPTION 2381 "Write access is not required." 2383 OBJECT mplsOutSegmentTSpecIndex 2384 MIN-ACCESS read-only 2385 DESCRIPTION 2386 "Write access is not required." 2388 OBJECT mplsOutSegmentAdminStatus 2389 SYNTAX INTEGER { up(1), down(2) } 2390 MIN-ACCESS read-only 2391 DESCRIPTION 2392 "A value of testing(3) need not be supported." 2394 OBJECT mplsOutSegmentOperStatus 2395 SYNTAX INTEGER { up(1), down(2) } 2396 MIN-ACCESS read-only 2397 DESCRIPTION 2398 "Only up(1) and down(2) need to be supported." 2400 OBJECT mplsOutSegmentRowStatus 2401 SYNTAX INTEGER { active(1), notInService(2), 2402 createAndGo(4), destroy(6) } 2403 MIN-ACCESS read-only 2404 DESCRIPTION 2405 "The notReady(3) and createAndWait(5) states need 2406 not be supported." 2408 -- mplsXCTable 2410 OBJECT mplsXCIndexNext 2411 MIN-ACCESS read-only 2412 DESCRIPTION 2413 "Write access is not required." 2415 OBJECT mplsXCIndex 2416 MIN-ACCESS read-only 2417 DESCRIPTION 2418 "Write access is not required." 2420 OBJECT mplsXCLabelStackIndexNext 2421 MIN-ACCESS read-only 2422 DESCRIPTION 2423 "Write access is not required." 2425 OBJECT mplsXCLabelStackIndex 2426 MIN-ACCESS read-only 2427 DESCRIPTION 2428 "Write access is not required." 2430 OBJECT mplsXCCOS 2431 MIN-ACCESS read-only 2432 DESCRIPTION 2433 "Write access is not required." 2435 OBJECT mplsXCIsPersistent 2436 MIN-ACCESS read-only 2437 DESCRIPTION 2438 "Write access is not required." 2440 OBJECT mplsXCAdminStatus 2441 SYNTAX INTEGER { up(1), down(2) } 2442 MIN-ACCESS read-only 2443 DESCRIPTION 2444 "A value of testing(3) need not be supported." 2446 OBJECT mplsXCOperStatus 2447 SYNTAX INTEGER { up(1), down(2) } 2448 MIN-ACCESS read-only 2449 DESCRIPTION 2450 "Only up(1) and down(2) need to be supported." 2452 OBJECT mplsXCRowStatus 2453 SYNTAX INTEGER { active(1), notInService(2), 2454 createAndGo(4), destroy(6) } 2455 MIN-ACCESS read-only 2456 DESCRIPTION 2457 "The notReady(3) and createAndWait(5) states need 2458 not be supported." 2460 ::= { mplsLsrCompliances 1 } 2462 -- Units of conformance. 2464 mplsInterfaceGroup OBJECT-GROUP 2465 OBJECTS { mplsInterfaceConfIndex, 2466 mplsInterfaceLabelMinIn, mplsInterfaceLabelMaxIn, 2467 mplsInterfaceLabelMinOut, mplsInterfaceLabelMaxOut, 2468 mplsInterfaceInLabelsUsed, mplsInterfaceOutLabelsUsed, 2469 mplsInterfaceIsGlobalLabelSpace, 2470 mplsInterfaceIsLocalLabelSpace, 2471 mplsInterfaceAdminStatus, mplsInterfaceOperStatus, 2472 mplsInterfaceTrapEnable 2473 } 2475 STATUS current 2476 DESCRIPTION 2477 "Collection of objects needed for MPLS interface 2478 configuration and performance information." 2479 ::= { mplsLsrGroups 1 } 2481 mplsInSegmentGroup OBJECT-GROUP 2482 OBJECTS { mplsInSegmentIfIndex, 2483 mplsInSegmentLabel, 2484 mplsInSegmentNPop, 2485 mplsInSegmentAddrFamily, 2486 mplsInSegmentXCIndex, 2487 mplsInSegmentTSpecIndex, 2488 mplsInSegmentOctets, 2489 mplsInSegmentDiscards, 2490 mplsInSegmentOwner, 2491 mplsInSegmentAdminStatus, 2492 mplsInSegmentOperStatus, 2493 mplsInSegmentRowStatus, 2494 mplsInSegmentTrapEnable 2495 } 2496 STATUS current 2497 DESCRIPTION 2498 "Collection of objects needed to implement an in- 2499 segment." 2500 ::= { mplsLsrGroups 2 } 2502 mplsOutSegmentGroup OBJECT-GROUP 2503 OBJECTS { mplsOutSegmentIndexNext, 2504 mplsOutSegmentIndex, 2505 mplsOutSegmentIfIndex, 2506 mplsOutSegmentPushTopLabel, 2507 mplsOutSegmentTopLabel, 2508 mplsOutSegmentNextHopIpAddrType, 2509 mplsOutSegmentNextHopIpv4Addr, 2510 mplsOutSegmentNextHopIpv6Addr, 2511 mplsOutSegmentXCIndex, 2512 mplsOutSegmentTSpecIndex, 2513 mplsOutSegmentOwner, 2514 mplsOutSegmentOctets, 2515 mplsOutSegmentDiscards, 2516 mplsOutSegmentAdminStatus, 2517 mplsOutSegmentOperStatus, 2518 mplsOutSegmentRowStatus, 2519 mplsOutSegmentTrapEnable 2521 } 2522 STATUS current 2523 DESCRIPTION 2524 "Collection of objects needed to implement an out- 2525 segment." 2526 ::= { mplsLsrGroups 3 } 2528 mplsXCGroup OBJECT-GROUP 2529 OBJECTS { mplsXCIndexNext, 2530 mplsXCIndex, 2531 mplsXCLabelStackIndex, 2532 mplsXCAdminStatus, 2533 mplsXCOperStatus, 2534 mplsXCRowStatus, 2535 mplsXCTrapEnable 2536 } 2537 STATUS current 2538 DESCRIPTION 2539 "Collection of objects needed to implement a 2540 cross-connect entry." 2541 ::= { mplsLsrGroups 4 } 2543 mplsPerfGroup OBJECT-GROUP 2544 OBJECTS { mplsInterfaceInPackets, 2545 mplsInterfaceInDiscards, 2546 mplsInterfaceOutPackets, 2547 mplsInterfaceOutDiscards, 2548 mplsInSegmentOctets, 2549 mplsInSegmentPackets, 2550 mplsInSegmentDiscards, 2551 mplsOutSegmentOctets, 2552 mplsOutSegmentPackets, 2553 mplsOutSegmentDiscards } 2554 STATUS current 2555 DESCRIPTION 2556 "Collection of objects providing performance 2557 information 2558 about an LSR." 2559 ::= { mplsLsrGroups 5 } 2561 mplsHCInSegmentPerfGroup OBJECT-GROUP 2562 OBJECTS { mplsInSegmentHCOctets } 2563 STATUS current 2564 DESCRIPTION 2565 "Object(s) providing performance information 2566 specific to out-segments for which the object 2567 mplsInterfaceInOctets wraps around too quickly." 2568 ::= { mplsLsrGroups 6 } 2570 mplsHCOutSegmentPerfGroup OBJECT-GROUP 2571 OBJECTS { mplsOutSegmentHCOctets } 2572 STATUS current 2573 DESCRIPTION 2574 "Object(s) providing performance information 2575 specific to out-segments for which the object 2576 mplsInterfaceOutOctets wraps around too 2577 quickly." 2578 ::= { mplsLsrGroups 7 } 2580 mplsTSpecGroup OBJECT-GROUP 2581 OBJECTS { mplsTSpecIndex, 2582 mplsTSpecMaxRate, 2583 mplsTSpecMeanRate, 2584 mplsTSpecMaxBurstSize, 2585 mplsTSpecRowStatus } 2586 STATUS current 2587 DESCRIPTION 2588 "Object(s) required for supporting Int-Serv style 2589 resource reservation." 2590 ::= { mplsLsrGroups 8 } 2592 mplsXCIsPersistentGroup OBJECT-GROUP 2593 OBJECTS { mplsXCIsPersistent } 2594 STATUS current 2595 DESCRIPTION 2596 "Objects needed to support persistent cross- 2597 connects." 2598 ::= { mplsLsrGroups 9 } 2600 mplsXCIsNotPersistentGroup OBJECT-GROUP 2601 OBJECTS { mplsXCIsPersistent } 2602 STATUS current 2603 DESCRIPTION 2604 "Objects needed to support non-persistent cross- 2605 connects." 2606 ::= { mplsLsrGroups 10 } 2608 mplsLsrNotificationGroup NOTIFICATION-GROUP 2609 NOTIFICATIONS { mplsInterfaceUp, 2610 mplsInterfaceDown, 2611 mplsInSegmentUp, 2612 mplsInSegmentDown, 2613 mplsOutSegmentUp, 2614 mplsXCUp, 2615 mplsXCDown 2616 } 2618 STATUS current 2619 DESCRIPTION 2620 "Set of notifications implemented in this module. 2621 None is mandatory." 2622 ::= { mplsLsrGroups 11 } 2624 -- End of MPLS-LSR-MIB 2625 END 2627 10. Security Considerations 2629 It is clear that this MIB is potentially useful for monitoring of 2630 MPLS LSRs. This MIB can also be used for configuration of certain 2631 objects, and anything that can be configured can be incorrectly 2632 configured, with potentially disastrous results. 2634 At this writing, no security holes have been identified beyond 2635 those that SNMP Security [SNMPArch] is itself intended to address. 2636 These relate to primarily controlled access to sensitive 2637 information and the ability to configure a device - or which might 2638 result from operator error, which is beyond the scope of any 2639 security architecture. 2641 There are a number of management objects defined in this MIB which 2642 have a MAX-ACCESS clause of read-write and/or read-create. Such 2643 objects may be considered sensitive or vulnerable in some network 2644 environments. The support for SET operations in a non-secure 2645 environment without proper protection can have a negative effect 2646 on network operations. The use of SNMP Version 3 is recommended 2647 over prior versions, for configuration control, as its security 2648 model is improved. 2650 SNMPv1 or SNMPv2 are by themselves not a secure environment. Even 2651 if the network itself is secure (for example by using IPSec 2652 [IPSEC]), there is no control as to who on the secure network is 2653 allowed to access and GET/SET (read/change/create/delete) the 2654 objects in this MIB. It is recommended that the implementers 2655 consider the security features as provided by the SNMPv3 2656 framework. Specifically, the use of the User-based Security Model 2657 [SNMPv3USM] and the View-based Access Control [SNMPv3VACM] is 2658 recommended. It is then a customer/user responsibility to ensure 2659 that the SNMP entity giving access to an instance of this MIB is 2660 properly configured to give access to the objects only to those 2661 principals (users) that have legitimate rights to indeed GET or 2662 SET (change/create/delete) them. 2664 There are a number of managed objects in this MIB that may contain 2665 information that may be sensitive from a business perspective, in 2666 that they represent a customer's interface to the MPLS network. 2667 Allowing uncontrolled access to these objects could result in 2668 malicious and unwanted disruptions of network traffic or incorrect 2669 configurations for these customers. There are no objects that are 2670 particularly sensitive in their own right, such as passwords or 2671 monetary amounts. 2673 11. Acknowledgments 2675 We wish to thank Ron Bonica, Keith McCloghrie, Dan Tappan, Bala 2676 Rajagopalan, Eric Gray, Vasanthi Thirumalai and Adrian Farrel. 2678 12. References 2680 [MPLSArch] Rosen, E., Viswanathan, A., and R. Callon, 2681 "Multiprotocol Label Switching Architecture", 2682 Internet Draft , 2683 August 1999. 2685 [MPLSFW] Callon, R., Doolan, P., Feldman, N., Fredette, A., 2686 Swallow, G., and A. Viswanathan, "A Framework for 2687 Multiprotocol Label Switching", Internet Draft 2688 , September 1999. 2690 [TEMIB] Srinivasan, C., Viswanathan, A. and Nadeau, T., 2691 "MPLS Traffic Engineering Management Information 2692 Base Using SMIv2", Internet Draft , February 2000. 2695 [LDPMIB] Cucchiara, J., Sjostrand, H., and J. Luciani, " 2696 Definitions of Managed Objects for the 2697 Multiprotocol Label Switching, Label Distribution 2698 Protocol (LDP)", Internet Draft , February 2000. 2701 [LblStk] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D., 2702 Federokow, G., Li, T., and A. Conta, "MPLS Label 2703 Stack Encoding", Internet Draft , September 1999. 2706 [RSVPTun] Awaduche, D., Berger, L., Der-Haw, G., Li, T., 2707 Swallow, G., and V. Srinivasan, "Extensions to RSVP 2708 for LSP Tunnels", Internet Draft , September 1999. 2711 [CRLDP] B. Jamoussi (Editor), "Constraint-Based LSP Setup 2712 using LDP", Internet Draft , September 1999. 2715 [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", 2716 RFC 1700, October 1994. See also: 2717 http://www.isi.edu/in-notes/iana/assignments/smi- 2718 numbers 2720 [SNMPArch] Harrington, D., Presuhn, R., and B. Wijnen, "An 2721 Architecture for Describing SNMP Management 2722 Frameworks", RFC 2271, January 1998. 2724 [SMIv1] Rose, M., and K. McCloghrie, "Structure and 2725 Identification of Management Information for TCP/IP- 2726 based Internets", RFC 1155, May 1990. 2728 [SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB 2729 Definitions", RFC 1212, March 1991. 2731 [SNMPv1Traps] M. Rose, "A Convention for Defining Traps for use 2732 with the SNMP", RFC 1215, March 1991. 2734 [SMIv2] Case, J., McCloghrie, K., Rose, M., and S. 2735 Waldbusser, "Structure of Management Information 2736 for Version 2 of the Simple Network Management 2737 Protocol (SNMPv2)", RFC 1902, January 1996. 2739 [SNMPv2TC] Case, J., McCloghrie, K., Rose, M., and S. 2740 Waldbusser, "Textual Conventions for Version 2 of 2741 the Simple Network Management Protocol (SNMPv2)", 2742 RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., 2743 January 1996. 2745 [SNMPv2Conf] Case, J., McCloghrie, K., Rose, M., and S. 2746 Waldbusser, "Conformance Statements for Version 2 2747 of the Simple Network Management Protocol 2748 (SNMPv2)", RFC 1904, January 1996. 2750 [SNMPv1] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 2751 "Simple Network Management Protocol", RFC 1157, May 2752 1990. 2754 [SNMPv2c] Case, J., McCloghrie, K., Rose, M., and S. 2755 Waldbusser, "Introduction to Community-based 2756 SNMPv2", RFC 1901, January 1996. 2758 [SNMPv2TM] Case, J., McCloghrie, K., Rose, M., and S. 2759 Waldbusser, "Transport Mappings for Version 2 of 2760 the Simple Network Management Protocol (SNMPv2)", 2761 RFC 1906, January 1996. 2763 [SNMPv3MP] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2764 "Message Processing and Dispatching for the Simple 2765 Network Management Protocol (SNMP)", RFC 2272, 2766 January 1998. 2768 [SNMPv3USM] Blumenthal, U., and B. Wijnen, "User-based Security 2769 Model (USM) for version 3 of the Simple Network 2770 Management Protocol (SNMPv3)", RFC 2574, April 2771 1999. 2773 [SNMPv2PO] Case, J., McCloghrie, K., Rose, M., and S. 2774 Waldbusser, "Protocol Operations for Version 2 of 2775 the Simple Network Management Protocol (SNMPv2)", 2776 RFC 1905, January 1996. 2778 [SNMPv3App] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2779 Applications", RFC 2273, January 1998. 2781 [SNMPv3VACM] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- 2782 based Access Control Model (VACM) for the Simple 2783 Network Management Protocol (SNMP)", RFC 2575, 2784 April 1999. 2786 [IPSEC] Kent, S., and Atkinson, R., "Security Architecture 2787 for the Internet Protocol", RFC 2401, November 2788 1998. 2790 [IFMIB] McCloghrie, K., and F. Kastenholtz, "The Interfaces 2791 Group MIB using SMIv2", RFC 2233, Nov. 1997 2793 13. Authors' Addresses 2795 Cheenu Srinivasan 2796 Tachion Networks, Inc. 2797 2 Meridian Road 2798 Eatontown, NJ 07724 2799 Phone: +1-732-542-7750 x234 2800 Email: cheenu@tachion.com 2802 Arun Viswanathan 2803 Force10 Networks 2804 1440 McCarthy Blvd 2805 Milpitas, CA 95035 2806 Phone: +1-408-571-3516 2807 Email: arun@force10networks.com 2809 Thomas D. Nadeau 2810 Cisco Systems, Inc. 2811 250 Apollo Drive 2812 Chelmsford, MA 01824 2813 Phone: +1-978-244-3051 2814 Email: tnadeau@cisco.com 2816 14. Full Copyright Statement 2818 Copyright (C) The Internet Society (2000). All Rights Reserved. 2820 This document and translations of it may be copied and furnished 2821 to others, and derivative works that comment on or otherwise 2822 explain it or assist in its implementation may be prepared, 2823 copied, published and distributed, in whole or in part, without 2824 restriction of any kind, provided that the above copyright notice 2825 and this paragraph are included on all such copies and derivative 2826 works. However, this document itself may not be modified in any 2827 way, such as by removing the copyright notice or references to the 2828 Internet Society or other Internet organizations, except as needed 2829 for the purpose of developing Internet standards in which case 2830 the procedures for copyrights defined in the Internet Standards 2831 process must be followed, or as required to translate it into 2832 languages other than English. 2834 The limited permissions granted above are perpetual and will not 2835 be revoked by the Internet Society or its successors or assigns. 2836 This document and the information contained herein is provided on 2837 an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 2838 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 2839 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 2840 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2841 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.