idnits 2.17.1 draft-ietf-mpls-lsr-mib-09.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 seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents -- however, there's a paragraph with a matching beginning. Boilerplate error? == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 60 lines 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. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 2594 has weird spacing: '...for the purpo...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 2002) is 7864 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC1212' is mentioned on line 113, but not defined == Unused Reference: 'Assigned' is defined on line 2448, but no explicit reference was found in the text == Unused Reference: 'TCMIB' is defined on line 2460, but no explicit reference was found in the text == Unused Reference: 'RFC2702' is defined on line 2542, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1700 (ref. 'Assigned') (Obsoleted by RFC 3232) -- Possible downref: Non-RFC (?) normative reference: ref. 'IANAFamily' -- Possible downref: Non-RFC (?) normative reference: ref. 'TCMIB' ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2401 (Obsoleted by RFC 4301) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Downref: Normative reference to an Informational RFC: RFC 2702 Summary: 18 errors (**), 0 flaws (~~), 7 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Cheenu Srinivasan 3 Internet Draft Parama Networks, Inc. 4 Expires: April 2003 5 Arun Viswanathan 6 Force10 Networks, Inc. 8 Thomas D. Nadeau 9 Cisco Systems, Inc. 11 October 2002 13 Multiprotocol Label Switching (MPLS) Label Switching Router (LSR) 14 Management Information Base 16 draft-ietf-mpls-lsr-mib-09.txt 18 Status of this Memo 20 This document is an Internet-Draft and is in full conformance with 21 all provisions of Section 10 of RFC 2026. 23 Internet-Drafts are working documents of the In ternet Engineering 24 Task Force (IETF), its areas, and its working groups. Note that 25 other groups may also distribute working documents as Internet- 26 Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six 29 months and may be updated, replaced, or obsoleted by other 30 documents at any time. It is inappropriate to use Internet- 31 Drafts as reference material or to cite them other than as "work 32 in progress." 34 The list of current Internet-Drafts can be accessed at 35 http://www.ietf.org/ietf/1id-abstracts.txt. 37 The list of Internet-Draft Shadow Directories can be accessed at 38 http://www.ietf.org/shadow.html. 40 Abstract 42 This memo defines a portion of the Management Information Base 43 (MIB) for use with network management protocols in the Internet 44 community. In particular, it describes managed objects for 45 modeling a Multiprotocol Label Switching (MPLS) Label Switching 46 Router (LSR). 48 Table of Contents 50 1. Introduction 2 51 2. Terminology 3 52 3. The SNMP Management Framework 3 53 4. Feature Checklist 4 54 5. Outline 5 55 5.1. Summary of LSR MIB 5 56 6. Brief Description of MIB Objects 5 57 6.1. mplsInterfaceConfTable 6 58 6.2. mplsInterfacePerfTable 6 59 6.3. mplsInSegmentTable 6 60 6.4. mplsInSegmentPerfTable 6 61 6.5. mplsOutSegmentTable 6 62 6.6. mplsOutSegmentPerfTable 6 63 6.7. mplsXCTable 6 64 6.8. mplsLabelStackTable 7 65 6.9. mplsTrafficParamTable 7 66 7. Use of 32-bit and 64-bit Counters 7 67 8. Example of LSP Setup 7 68 9. Application of the Interface Group to MPLS 9 69 9.1. Support of the MPLS Layer by ifTable 9 70 10. The Use of RowPointer 10 71 11. MPLS Label Switching Router MIB Definitions 11 72 12. Security Considerations 41 73 13. Acknowledgments 42 74 14. References 42 75 15. Authors' Addresses 44 76 16. Full Copyright Statement 44 78 1. Introduction 80 This memo defines a portion of the Management Information Base 81 (MIB) for use with network management protocols in the Internet 82 community. In particular, it describes managed objects for 83 modeling a Multi-Protocol Label Switching (MPLS) [RFC3031] Label 84 Switching Router (LSR). 86 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 87 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 88 "OPTIONAL" in this document are to be interpreted as described in 89 RFC 2119, reference [RFC2119]. 91 2. Terminology 93 This document uses terminology from the document describing the 94 MPLS architecture [RFC3031]. A label switched path (LSP) is 95 modeled as a connection consisting of one or more incoming 96 segments (in-segments) and/or one or more outgoing segments (out- 97 segments) at a Label Switching Router (LSR). The association or 98 interconnection of the in-segments and out-segments is 99 accomplished by using a cross-connect. We use the terminology 100 "connection" and "LSP" interchangeably where the meaning is clear 101 from the context. 103 3. The SNMP Management Framework 105 The SNMP Management Framework presently consists of five major 106 components: 108 - An overall architecture, described in RFC 2571 [RFC2571]. 110 - Mechanisms for describing and naming objects and events for the 111 purpose of management. The first version of this Structure of 112 Management Information (SMI) is called SMIv1 and described in 113 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and STD 114 16, RFC 1215 [RFC1215]. The second version, called SMIv2, is 115 described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 116 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 118 - Message protocols for transferring management information. The 119 first version of the SNMP message protocol is called SNMPv1 120 and described in STD 15, RFC 1157 [RFC1157]. A second version 121 of the SNMP message protocol, which is not an Internet 122 standards track protocol, is called SNMPv2c and described in 123 RFC 1901 [RFC1901] and RFC 1906 [RFC1906]. The third version 124 of the message protocol is called SNMPv3 and described in RFC 125 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 127 - Protocol operations for accessing management information. The 128 first set of protocol operations and associated PDU formats is 129 described in STD 15, RFC 1157 [RFC1157]. A second set of 130 protocol operations and associated PDU formats is described in 131 RFC 1905 [RFC1905]. 133 - A set of fundamental applications described in RFC 2573 134 [RFC2573] and the view-based access control mechanism 135 described in RFC 2575 [RFC2575]. 137 A more detailed introduction to the current SNMP Management 138 Framework can be found in RFC 2570 [RFC2570]. 140 Managed objects are accessed via a virtual information store, 141 termed the Management Information Base or MIB. Objects in the MIB 142 are defined using the mechanisms defined in the SMI. 144 This memo specifies a MIB module that is compliant to the SMIv2. 145 A MIB conforming to the SMIv1 can be produced through the 146 appropriate translations. The resulting translated MIB must be 147 semantically equivalent, except where objects or events are 148 omitted because no translation is possible (use of Counter64). 150 Some machine readable information in SMIv2 will be converted into 151 textual descriptions in SMIv1 during the translation process. 152 However, this loss of machine readable information is not 153 considered to change the semantics of the MIB. 155 4. Feature Checklist 157 The MPLS Label Switching Router MIB (LSR MIB) is designed to 158 satisfy the following requirements and constraints: 160 - The MIB supports LSP establishment via an MPLS signaling 161 protocol wherein the LSP parameters are specified using this 162 MIB at the head end of the LSP and end-to-end LSP 163 establishment is accomplished via signaling. The MIB also 164 supports manually configured LSPs, i.e. those for which label 165 associations at each hop of the LSP are provisioned by the 166 administrator via this MIB. 168 - The MIB supports the enabling and disabling of MPLS capability 169 on MPLS capable interfaces of an LSR. 171 - The MIB allows resource sharing between two or more LSPs, i.e. 172 it allows specification of sharing of bandwidth and other LSR 173 resources between different LSPs. 175 - Both per-platform and per-interface label spaces are supported. 177 - MPLS packets can be forwarded solely based on an incoming top 178 label [RFC3031, RFC3032]. 180 - Support is provided for next-hop resolution when the outgoing 181 interface is a shared media interface. In the point-to- 182 multipoint case, each outgoing segment can reside on a 183 different shared media interface. 185 - The MIB supports point-to-point, point-to-multipoint and 186 multipoint-to-point connections at an LSR. 188 - For multipoint-to-point connections all outgoing packets can 189 have the same top label. 191 - For multipoint-to-point connections, the outgoing resources of 192 the merged connections can be shared. 194 - For multipoint-to-point connections, packets from different 195 incoming connections can have distinct outgoing label stacks 196 beneath the (identical) top label. 198 - In the point-to-multipoint case each outgoing connection can 199 have a distinct label stack including the top label. 201 - All the members of a point-to-multipoint connection can share 202 the resources allocated for the ingress segments. 204 - The MIB provides cross-connect capability to "pop" an incoming 205 label and forward the packet with the remainder of the label 206 stack unchanged and without pushing any labels ("pop-and-go") 207 [RFC3032]. 209 - The MIB supports persistent as well as non-persistent LSPs. 211 - Performance counters are provided for in-segments and out- 212 segments as well as for measuring MPLS performance on a per- 213 interface basis. 215 5. Outline 217 Configuring LSPs through an LSR involves the following steps: 219 - Enabling MPLS on MPLS capable interfaces. 221 - Configuring in-segments and out-segments. 223 - Setting up the cross-connect table to associate segments and/or 224 to indicate connection origination and termination. 226 - Optionally specifying label stack actions. 228 - Optionally specifying segment traffic parameters. 230 5.1. Summary of LSR MIB 232 The MIB objects for performing these actions consist of the 233 following tables: 235 - The interface configuration table (mplsInterfaceConfTable), 236 which is used for enabling the MPLS protocol on MPLS-capable 237 interfaces. 239 - The in-segment (mplsInSegmentTable) and out-segment 240 (mplsOutSegmentTable) tables, which are used for configuring 241 LSP segments at an LSR. 243 - The cross-connect table (mplsXCTable), which is used to 244 associate in and out segments together, in order to form a 245 cross-connect. 247 - The label stack table (mplsLabelStackTable), which is used for 248 specifying label stack operations. 250 - The Traffic Parameter table (mplsTrafficParamTable), which is 251 used for specifying LSP-related traffic parameters. 253 Further, the MPLS in-segment and out-segment performance tables, 254 mplsInSegmentPerfTable and mplsOutSegmentPerfTable, contain the 255 objects necessary to measure the performance of LSPs, and 256 mplsInterfacePerfTable has objects to measure MPLS performance on 257 a per-interface basis. 259 These tables are described in the subsequent sections. 261 6. Brief Description of MIB Objects 263 Sections 6.1-6.2 describe objects pertaining to MPLS-capable 264 interfaces of an LSR. The objects described in Sections 6.3-6.8, 265 were derived from the Incoming Label Map (ILM) and Next Hop Label 266 Forwarding Entry (NHLFE) as specified in the MPLS architecture 267 document [RFC3031]. Section 6.9 describes objects for specifying 268 traffic parameters for in and out segments. It is appropriate to 269 note that the in-segment, out-segment, and cross-connect tables 270 were modeled after similar tables found in [RFC2515]. 272 6.1. mplsInterfaceConfTable 274 This table represents the interfaces that are MPLS capable. An 275 LSR creates an entry in this table for every MPLS capable 276 interface on that LSR. 278 6.2. mplsInterfacePerfTable 280 This table contains objects to measure the MPLS performance of 281 MPLS capable interfaces and is an AUGMENT to 282 mplsInterfaceConfTable. 284 6.3. mplsInSegmentTable 286 This table contains a description of the incoming MPLS segments to 287 an LSR and their associated parameters. 289 6.4. mplsInSegmentPerfTable 291 The MPLS In-Segment Performance Table has objects to help measure 292 the performance of an incoming segment configured on an LSR. It 293 is an AUGMENT to mplsInSegmentTable. High capacity counters are 294 provided for objects that are likely to wrap around quickly on 295 high-speed interfaces. 297 6.5. mplsOutSegmentTable 299 The Out-Segment Table contains a description of the outgoing MPLS 300 segments at an LSR and their associated parameters. 302 6.6. mplsOutSegmentPerfTable 304 The MPLS Out-Segment Table contains objects to help measure the 305 performance of an outgoing segment configured on an LSR. It is an 306 AUGMENT to mplsOutSegmentTable. High capacity counters are 307 provided for objects that are likely to wrap around quickly on 308 high-speed interfaces. 310 6.7. mplsXCTable 312 The mplsXCTable specifies information for associating segments 313 together in order to instruct the LSR to switch between the 314 specified segments. It supports point-to-point, point-to-multi- 315 point and multi-point-to-point connections. 317 The operational status object indicates the packet forwarding 318 state of a cross-connect entry. For example, when the operational 319 status objects is 'down' it indicates that the specified cross- 320 connect entry will not forward packets. Likewise, when it is set 321 to 'up' it indicates that packets will be forwarded. 323 The administrative status object indicates the forwarding state 324 desired by the operator. 326 6.8. mplsLabelStackTable 328 The mplsLabelStackTable specifies the label stack to be pushed 329 onto a packet, beneath the top label. Entries to this table are 330 referred to from mplsXCTable. 332 6.9. mplsTrafficParamTable 334 The mplsTrafficParamTable contains objects for specifying the 335 traffic parameters of in-segments and out-segments. Entries in 336 this table are referred to from mplsInSegmentTable and 337 mplsOutSegmentTable. 339 7. Use of 32-bit and 64-bit Counters 341 64-bit counters are provided in this MIB for high speed interfaces 342 where the use of 32-bit counters might be impractical. The 343 requirements on the use of 32-bit and 64-bit counters (copied 344 verbatim from [RFC2863]) are as follows. 346 For interfaces that operate at 20,000,000 (20 million) bits per 347 second or less, 32-bit byte and packet counters MUST be supported. 348 For interfaces that operate faster than 20,000,000 bits/second, 349 and slower than 650,000,000 bits/second, 32-bit packet counters 350 MUST be supported and 64-bit octet counters MUST be supported. 351 For interfaces that operate at 650,000,000 bits/second or faster, 352 64-bit packet counters AND 64-bit octet counters MUST be 353 supported. 355 8. Example of LSP Setup 357 In this section we provide a brief example of setting up an LSP 358 using the MIB objects described in section 11. While this example 359 is not meant to illustrate every nuance of the MIB, it is intended 360 as an aid to understanding some of the key concepts. It is meant 361 to be read after going through the MIB itself. 363 Suppose that one would like to manually create a best-effort, 364 unidirectional LSP. Assume that the LSP enters the LSR via MPLS 365 interface A with ifIndex 12 and exits the LSR via MPLS interface B 366 with ifIndex 13. Let us assume that we do not wish to have a 367 label stack beneath the top label on the outgoing labeled packets. 368 The following example illustrates which rows and corresponding 369 objects might be created to accomplish this. Those objects 370 relevant to illustrating the relationships amongst different 371 tables are shown here. Other objects may be needed before 372 conceptual row activation can happen. 374 The RowStatus values shown in this section are those to be used in 375 the set request, typically createAndGo(4) which is used to create 376 the conceptual row and have its status immediately set to active. 377 A subsequent retrieval operation on the conceptual will return a 378 different value, such as active(1). Please see [RFC2579] for a 379 detailed discussion on the use of RowStatus. 381 First, the traffic parameter entries must be set-up for both 382 segments. 384 In mplsTrafficParamTable for the incoming direction: 386 { 387 mplsTrafficParamIndex = 5 388 mplsTrafficParamMaxRate = 100000, 389 mplsTrafficParamMeanRate = 100000, 390 mplsTrafficParamMaxBurstSize = 2000, 391 mplsTrafficParamRowStatus = createAndGo(4) 392 } 394 In mplsTrafficParamTable for the outgoing direction: 395 { 396 mplsTrafficParamIndex = 6 397 mplsTrafficParamMaxRate = 100000, 398 mplsTrafficParamMeanRate = 100000, 399 mplsTrafficParamMaxBurstSize = 2000, 400 mplsTrafficParamRowStatus = createAndGo(4) 401 } 403 Note that if we were setting up a bi-directional LSP, the segments 404 in the reverse direction can share the traffic parameter entries 405 (and hence resources) with the segments in the forward direction. 407 We must next create the appropriate in-segment and out-segment 408 entries with suitable traffic parameters by pointing to the 409 appropriate traffic parameter entries that we have just created. 411 In mplsInSegmentTable: 412 { 413 mplsInSegmentIfIndex = 12, -- incoming interface 414 mplsInSegmentLabel = 21, -- incoming label 415 mplsInSegmentNPop = 1, 416 -- RowPointer MUST point to the first accesible column. 417 mplsInSegmentTrafficParamPtr = mplsTrafficParamMaxRate.5, 418 mplsInSegmentRowStatus = createAndGo(4) 419 } 421 In mplsOutSegmentTable: 422 { 423 mplsOutSegmentIndex = 1, 424 mplsOutSegmentIfIndex = 13, -- outgoing interface 425 mplsOutSegmentPushTopLabel = true(1), 426 mplsOutSegmentTopLabel = 22, -- outgoing label 427 -- RowPointer MUST point to the first accesible column. 428 mplsOutSegmentTrafficParamPtr = mplsTrafficParamMaxRate.6, 429 -- Other mandatory parameters needed to activate the row go 430 here. 431 mplsOutSegmentRowStatus = createAndGo(4) 432 } 433 Next, a cross-connect entry is created thereby associating the 434 newly created segments together. 436 In mplsXCTable: 437 { 438 mplsXCIndex = 2, 439 mplsXCLspId = 'c021041502'H, -- 192.33.4.21.2 440 mplsInSegmentIfIndex = 12, 441 mplsInSegmentLabel = 21, 442 mplsOutSegmentIndex = 1, 443 mplsXCIsPersistent = false (1), 444 mplsLabelStackIndex = 0, -- only a single 445 -- outgoing label 446 -- Other mandatory parameters for activating the row go here. 447 mplsXCRowStatus = createAndGo(4) 448 } 450 Note that the mplsInSegmentXCIndex and mplsOutSegmentXCIndex 451 objects will automatically be populated with the value 2 when 452 these segments are referred to from the corresponding cross- 453 connect entry. 455 9. Application of the Interface Group to MPLS 457 The Interfaces Group of MIB II defines generic managed objects for 458 managing interfaces. This memo contains the media-specific 459 extensions to the Interfaces Group for managing MPLS interfaces. 461 This memo assumes the interpretation of the Interfaces Group to be 462 in accordance with [RFC2863] which states that the interfaces 463 table (ifTable) contains information on the managed resource's 464 interfaces and that each sub-layer below the internetwork layer of 465 a network interface is considered an interface. Thus, the MPLS 466 interface is represented as an entry in the ifTable. The inter- 467 relation of entries in the ifTable is defined by Interfaces Stack 468 Group defined in [RFC2863]. 470 When using MPLS interfaces, the interface stack table might appear 471 as follows: 473 +----------------------------------------+ 474 | MPLS interface; ifType = mpls(166) + 475 +----------------------------------------+ 476 | Underlying Layer + 477 +----------------------------------------+ 479 In the above diagram, "Underlying Layer" refers to the ifIndex of 480 any interface type for which MPLS interworking has been defined. 481 Examples include ATM, Frame Relay, Ethernet, etc. 483 9.1. Support of the MPLS Layer by ifTable 485 Some specific interpretations of ifTable for the MPLS layer 486 follow. 488 Object Use for the MPLS layer 490 ifIndex Each MPLS interface is represented by an ifEntry. 492 ifDescr Description of the MPLS interface. 494 ifType The value that is allocated for MPLS is 166. 496 ifSpeed The total bandwidth in bits per second for use by 497 the MPLS layer. 499 ifPhysAddress Unused. 501 ifAdminStatus This variable indicates the administrator's intent 502 as to whether MPLS should be enabled, disabled, or 503 running in some diagnostic testing mode on this 504 interface. Also see [RFC2863]. 506 ifOperStatus This value reflects the actual operational status 507 of MPLS on this interface. 509 ifLastChange See [RFC2863]. 511 ifInOctets The number of received octets over the interface, 512 i.e., the number of received, octets received as 513 labeled packets. 515 ifOutOctets The number of transmitted octets over the 516 interface, i.e., the number of octets transmitted 517 as labeled packets. 519 ifInErrors The number of labeled packets dropped due to 520 uncorrectable errors. 522 ifInUnknownProtos 523 The number of received packets discarded during 524 packet header validation, including packets with 525 unrecognized label values. 527 ifOutErrors See [RFC2863]. 529 ifName Textual name (unique on this system) of the 530 interface or an octet string of zero length. 532 ifLinkUpDownTrapEnable 533 Default is disabled (2). 535 ifConnectorPresent 536 Set to false (2). 538 ifHighSpeed See [RFC2863]. 540 ifHCInOctets The 64-bit version of ifInOctets; supported if 541 required by the compliance statements in [RFC2863]. 543 ifHCOutOctets The 64-bit version of ifOutOctets; supported if 544 required by the compliance statements in [RFC2863]. 546 ifAlias The non-volatile 'alias' name for the interface as 547 specified by a network manager. 549 ifCounterDiscontinuityTime 550 See [RFC2863]. 552 10. The Use of RowPointer 554 RowPointer is a textual convention used to identify a conceptual 555 row in an SNMP Table by pointing to one of its objects. In this 556 MIB, it is used in mplsInSegmentTable and mplsOutSegmentTable for 557 the following purposes. First, it indicates a particular traffic 558 parameter table. An example of such a table is 559 mplsTrafficParamTable. Second, it is used to indicate a specific 560 instance of a traffic parameter entry that is associated with a 561 given in-segment or out-segment entry. In the in-segment and out- 562 segment tables, mplsTrafficParamPtr MUST point to the first 563 column of the appropriate conceptual row []. 565 11. MPLS Label Switching Router MIB Definitions 567 MPLS-LSR-MIB DEFINITIONS ::= BEGIN 569 IMPORTS 570 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 571 Integer32, Counter32, Unsigned32, Counter64, Gauge32, 572 zeroDotZero 573 FROM SNMPv2-SMI 574 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 575 FROM SNMPv2-CONF 576 TruthValue, RowStatus, StorageType, RowPointer, 577 TimeStamp 578 FROM SNMPv2-TC 580 InterfaceIndex, InterfaceIndexOrZero 581 FROM IF-MIB 582 mplsMIB, MplsLSPID, MplsLabel, MplsBitRate, MplsBurstSize, 583 MplsOwner 584 FROM MPLS-TC-MIB 585 AddressFamilyNumbers 586 FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB 587 InetAddress, InetAddressType 588 FROM INET-ADDRESS-MIB 589 ; 591 mplsLsrMIB MODULE-IDENTITY 592 LAST-UPDATED "200210051200Z" -- 5 October 2002 12:00:00 GMT 593 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 594 CONTACT-INFO 595 " 596 Cheenu Srinivasan 597 Postal: Parama Networks, Inc. 598 1030 Broad Street 599 Shrewsbury, NJ 07702 600 Tel: +1-732-544-9120 x731 601 Email: cheenu@paramanet.com 603 Arun Viswanathan 604 Postal: Force10 Networks, Inc. 605 1440 McCarthy Blvd 606 Milpitas, CA 95035 607 Tel: +1-408-571-3516 608 Email: arun@force10networks.com 610 Thomas D. Nadeau 611 Postal: Cisco Systems, Inc. 612 250 Apollo Drive 613 Chelmsford, MA 01824 614 Tel: +1-978-244-3051 615 Email: tnadeau@cisco.com 617 Comments about this document should be emailed 618 directly to the MPLS working group mailing list at 619 mpls@uu.net. 620 " 621 DESCRIPTION 622 "This MIB contains managed object definitions for the 623 Multiprotocol Label Switching (MPLS) Router as 624 defined in: Rosen, E., Viswanathan, A., and R. 625 Callon, Multiprotocol Label Switching Architecture, 626 RFC 3031, January 2001." 628 -- Revision history. 629 REVISION 630 "200210051200Z" -- 5 October 2002 12:00:00 GMT 631 DESCRIPTION 632 "Initial revision, published as part of RFC XXXX." 633 ::= { mplsMIB 2 } 635 -- Top level components of this MIB. 637 -- Notifications 638 mplsLsrNotifications OBJECT IDENTIFIER ::= { mplsLsrMIB 0 } 639 -- Tables, Scalars 640 mplsLsrObjects OBJECT IDENTIFIER ::= { mplsLsrMIB 1 } 641 -- Conformance 642 mplsLsrConformance OBJECT IDENTIFIER ::= { mplsLsrMIB 2 } 644 -- MPLS Interface Configuration Table. 646 mplsInterfaceConfTable OBJECT-TYPE 647 SYNTAX SEQUENCE OF MplsInterfaceConfEntry 648 MAX-ACCESS not-accessible 649 STATUS current 650 DESCRIPTION 651 "This table specifies per-interface MPLS capability 652 and associated information." 653 ::= { mplsLsrObjects 1 } 655 mplsInterfaceConfEntry OBJECT-TYPE 656 SYNTAX MplsInterfaceConfEntry 657 MAX-ACCESS not-accessible 658 STATUS current 659 DESCRIPTION 660 "A conceptual row in this table is created 661 automatically by an LSR for every interface capable 662 of supporting MPLS and is enabled to do so. A 663 conceptual row in this table will exist iff a 664 corresponding entry in ifTable exists with ifType = 665 mpls(166). If this associated entry in ifTable is 666 operationally disabled (thus disabling MPLS on that 667 interface), the corresponding entry in this table 668 MUST be deleted shortly thereafter. An conceptual 669 row with index 0 is created if the LSR supports per- 670 platform labels. This conceptual row represents the 671 per-platform label space and contains parameters 672 that apply to all interfaces that participate in the 673 per-platform label space. Other conceptual rows in 674 this table represent MPLS interfaces that may 675 participate in either the per-platform or per- 676 interface label spaces, or both. Further information 677 about label space participation of an interface is 678 provided in the DESCRIPTION clause of 679 mplsInterfaceLabelParticipationType." 680 INDEX { mplsInterfaceConfIndex } 681 ::= { mplsInterfaceConfTable 1 } 683 MplsInterfaceConfEntry ::= SEQUENCE { 684 mplsInterfaceConfIndex InterfaceIndexOrZero, 685 mplsInterfaceLabelMinIn MplsLabel, 686 mplsInterfaceLabelMaxIn MplsLabel, 687 mplsInterfaceLabelMinOut MplsLabel, 688 mplsInterfaceLabelMaxOut MplsLabel, 689 mplsInterfaceTotalBandwidth MplsBitRate, 690 mplsInterfaceAvailableBandwidth MplsBitRate, 691 mplsInterfaceLabelParticipationType BITS 692 } 694 mplsInterfaceConfIndex OBJECT-TYPE 695 SYNTAX InterfaceIndexOrZero 696 MAX-ACCESS not-accessible 697 STATUS current 698 DESCRIPTION 699 "This is a unique index for an entry in the 700 MplsInterfaceConfTable. A non-zero index for an 701 entry indicates the ifIndex for the corresponding 702 interface entry in of the MPLS-layer in the ifTable. 703 Note that the per-platform label space may apply to 704 several interfaces, and therefore the configuration 705 of the per-platform label space interface parameters 706 will apply to all of the interfaces that are 707 participating in the per-platform label space." 708 REFERENCE 709 "RFC 2863 - The Interfaces Group MIB, McCloghrie, K., 710 and F. Kastenholtz, June 2000" 711 ::= { mplsInterfaceConfEntry 1 } 713 mplsInterfaceLabelMinIn OBJECT-TYPE 714 SYNTAX MplsLabel 715 MAX-ACCESS read-only 716 STATUS current 717 DESCRIPTION 718 "This is the minimum value of an MPLS label that this 719 LSR is willing to receive on this interface." 720 ::= { mplsInterfaceConfEntry 2 } 722 mplsInterfaceLabelMaxIn OBJECT-TYPE 723 SYNTAX MplsLabel 724 MAX-ACCESS read-only 725 STATUS current 726 DESCRIPTION 727 "This is the maximum value of an MPLS label that this 728 LSR is willing to receive on this interface." 730 ::= { mplsInterfaceConfEntry 3 } 732 mplsInterfaceLabelMinOut OBJECT-TYPE 733 SYNTAX MplsLabel 734 MAX-ACCESS read-only 735 STATUS current 736 DESCRIPTION 737 "This is the minimum value of an MPLS label that this 738 LSR is willing to send on this interface." 739 ::= { mplsInterfaceConfEntry 4 } 741 mplsInterfaceLabelMaxOut OBJECT-TYPE 742 SYNTAX MplsLabel 743 MAX-ACCESS read-only 744 STATUS current 745 DESCRIPTION 746 "This is the maximum value of an MPLS label that this 747 LSR is willing to send on this interface." 748 ::= { mplsInterfaceConfEntry 5 } 750 mplsInterfaceTotalBandwidth OBJECT-TYPE 751 SYNTAX MplsBitRate 752 MAX-ACCESS read-only 753 STATUS current 754 DESCRIPTION 755 "This value indicates the total amount of usable 756 bandwidth on this interface and is specified in 757 kilobits per second (Kbps). This variable is not 758 applicable when applied to the interface with index 759 0. When this value cannot be measured, this value 760 should contain the nominal bandwidth." 761 ::= { mplsInterfaceConfEntry 6 } 763 mplsInterfaceAvailableBandwidth OBJECT-TYPE 764 SYNTAX MplsBitRate 765 MAX-ACCESS read-only 766 STATUS current 767 DESCRIPTION 768 "This value indicates the total amount of available 769 bandwidth available on this interface and is 770 specified in kilobits per second (Kbps). This value 771 is calculated as the difference between the amount 772 of bandwidth currently in use and that specified in 773 mplsInterfaceTotalBandwidth. This variable is not 774 applicable when applied to the interface with index 775 0. When this value cannot be measured, this value 776 should contain the nominal bandwidth." 777 ::= { mplsInterfaceConfEntry 7 } 779 mplsInterfaceLabelParticipationType OBJECT-TYPE 780 SYNTAX BITS { 781 perPlatform (0), 782 perInterface (1) 783 } 784 MAX-ACCESS read-only 785 STATUS current 786 DESCRIPTION 787 "Either the perPlatform(0) or perInterface(1) bit 788 MUST be set. Note however that an interface could 789 participate in both label spaces in which case both 790 bits would be set. If the value of the 791 mplsInterfaceConfIndex for this entry is zero, then 792 only the perPlatform(0) bit MUST be set and the 793 perInterface(1) bit is meaningless. If the 794 perInterface(1) bit is set then the value of 795 mplsInterfaceLabelMinIn, mplsInterfaceLabelMaxIn, 796 mplsInterfaceLabelMinOut, and 797 mplsInterfaceLabelMaxOut for this entry reflect the 798 label ranges for this interface. If only the 799 perPlatform(0) bit is set, then the value of 800 mplsInterfaceLabelMinIn, mplsInterfaceLabelMaxIn, 801 mplsInterfaceLabelMinOut, and 802 mplsInterfaceLabelMaxOut for this entry must be 803 identical to the instance of these objects with 804 index 0." 805 REFERENCE 806 "Rosen, E., Viswanathan, A., and R. Callon, 807 Multiprotocol Label Switching Architecture, RFC 808 3031, January 2001." 809 ::= { mplsInterfaceConfEntry 8 } 811 -- End of mplsInterfaceConfTable 813 -- MPLS Interface Performance Table. 815 mplsInterfacePerfTable OBJECT-TYPE 816 SYNTAX SEQUENCE OF MplsInterfacePerfEntry 817 MAX-ACCESS not-accessible 818 STATUS current 819 DESCRIPTION 820 "This table provides MPLS performance information on 821 a per-interface basis." 822 ::= { mplsLsrObjects 2 } 824 mplsInterfacePerfEntry OBJECT-TYPE 825 SYNTAX MplsInterfacePerfEntry 826 MAX-ACCESS not-accessible 827 STATUS current 828 DESCRIPTION 829 "An entry in this table is created by the LSR for 830 every interface capable of supporting MPLS. Its is 831 an extension to the mplsInterfaceConfEntry table." 832 AUGMENTS { mplsInterfaceConfEntry } 833 ::= { mplsInterfacePerfTable 1 } 835 MplsInterfacePerfEntry ::= SEQUENCE { 836 -- incoming direction 837 mplsInterfaceInLabelsUsed Gauge32, 838 mplsInterfaceLabelLookupFailures Counter32, 840 -- outgoing direction 841 mplsInterfaceOutLabelsUsed Gauge32, 842 mplsInterfaceOutFragments Counter32 843 } 845 mplsInterfaceInLabelsUsed OBJECT-TYPE 846 SYNTAX Gauge32 847 MAX-ACCESS read-only 848 STATUS current 849 DESCRIPTION 850 "This object counts the number of labels that are in 851 use at this point in time on this interface in the 852 incoming direction. If the interface participates in 853 the per-platform label space only, then the value of 854 this instance of this object MUST be identical with 855 the value of the instance with index 0. If the 856 interface participates in the per-interface label 857 space, then this instance of this object MUST 858 represent the number of of per-interface labels that 859 are in use at this point in time on this interface." 860 ::= { mplsInterfacePerfEntry 1 } 862 mplsInterfaceLabelLookupFailures OBJECT-TYPE 863 SYNTAX Counter32 864 MAX-ACCESS read-only 865 STATUS current 866 DESCRIPTION 867 "This object counts the number of labeled packets 868 that have been received on this interface and were 869 discarded because there was no matching cross- 870 connect entry. This object MUST count on a per- 871 interface basis regardless of which label space the 872 interface participates in." 873 ::= { mplsInterfacePerfEntry 2 } 875 mplsInterfaceOutLabelsUsed OBJECT-TYPE 876 SYNTAX Gauge32 877 MAX-ACCESS read-only 878 STATUS current 879 DESCRIPTION 880 "This object counts the number of top-most labels in 881 the outgoing label stacks that are in use at this 882 point in time on this interface. This object MUST 883 count on a per-interface basis regardless of which 884 label space the interface participates in." 885 ::= { mplsInterfacePerfEntry 3 } 887 mplsInterfaceOutFragments OBJECT-TYPE 888 SYNTAX Counter32 889 MAX-ACCESS read-only 890 STATUS current 891 DESCRIPTION 892 "This object counts the number of outgoing MPLS 893 packets that required fragmentation before 894 transmission on this interface. This object MUST 895 count on a per-interface basis regardless of which 896 label space the interface participates in." 897 ::= { mplsInterfacePerfEntry 4 } 899 -- In-segment table. 901 mplsInSegmentTable OBJECT-TYPE 902 SYNTAX SEQUENCE OF MplsInSegmentEntry 903 MAX-ACCESS not-accessible 904 STATUS current 905 DESCRIPTION 906 "This table contains the collection of incoming 907 segments to an LSR." 908 ::= { mplsLsrObjects 3 } 910 mplsInSegmentEntry OBJECT-TYPE 911 SYNTAX MplsInSegmentEntry 912 MAX-ACCESS not-accessible 913 STATUS current 914 DESCRIPTION 915 "An entry in this table represents one incoming 916 segment. An entry can be created by a network 917 administrator or an SNMP agent, or an MPLS signaling 918 protocol. The creator of the entry is denoted by 919 mplsInSegmentOwner. An entry in this table is 920 indexed by the ifIndex of the incoming interface and 921 the (top) label. The value of mplsInSegmentRowStatus 922 cannot be active(1)unless the ifTable entry 923 corresponding to mplsInSegmentIfIndex exists. An 924 entry in this table must match any incoming packets 925 for further processing. A match indicates an 926 instance of mplsXCEntry based on which 927 forwarding/switching actions are taken." 928 INDEX { mplsInSegmentIfIndex, mplsInSegmentLabel } 929 ::= { mplsInSegmentTable 1 } 931 MplsInSegmentEntry ::= SEQUENCE { 932 mplsInSegmentIfIndex InterfaceIndexOrZero, 933 mplsInSegmentLabel MplsLabel, 934 mplsInSegmentNPop Integer32, 935 mplsInSegmentAddrFamily AddressFamilyNumbers, 936 mplsInSegmentXCIndex Unsigned32, 937 mplsInSegmentOwner MplsOwner , 938 mplsInSegmentTrafficParamPtr RowPointer, 939 mplsInSegmentRowStatus RowStatus, 940 mplsInSegmentStorageType StorageType 941 } 943 mplsInSegmentIfIndex OBJECT-TYPE 944 SYNTAX InterfaceIndexOrZero 945 MAX-ACCESS not-accessible 946 STATUS current 947 DESCRIPTION 948 "This is a unique index for an entry in the 949 MplsInSegmentTable. This value represents the 950 interface index for the incoming MPLS interface. A 951 value of zero represents an incoming label from the 952 per-platform label space. In this case, the 953 mplsInSegmentLabel is interpreted to be an MPLS-type 954 label." 955 ::= { mplsInSegmentEntry 1 } 957 mplsInSegmentLabel OBJECT-TYPE 958 SYNTAX MplsLabel 959 MAX-ACCESS not-accessible 960 STATUS current 961 DESCRIPTION 962 "The incoming label for this segment." 963 ::= { mplsInSegmentEntry 2 } 965 mplsInSegmentNPop OBJECT-TYPE 966 SYNTAX Integer32 (1..2147483647) 967 MAX-ACCESS read-create 968 STATUS current 969 DESCRIPTION 970 "The number of labels to pop from the incoming 971 packet. Normally only the top label is popped from 972 the packet and used for all switching decisions for 973 that packet. Note that technologies which do not 974 support label popping should set this value to its 975 default value of 1. This object cannot be modified 976 if mplsInSegmentRowStatus is active(1)." 977 DEFVAL { 1 } 978 ::= { mplsInSegmentEntry 3 } 980 mplsInSegmentAddrFamily OBJECT-TYPE 981 SYNTAX AddressFamilyNumbers 982 MAX-ACCESS read-create 983 STATUS current 984 DESCRIPTION 985 "The IANA address family [IANAFamily] of the incoming 986 packet which is used at an egress LSR to deliver 987 packets to the appropriate layer 3 entity. A value 988 of other(0) indicates that the family type is either 989 unknown or undefined; this is not a legal value at 990 an egress LSR. This object cannot be modified if 991 mplsInSegmentRowStatus is active(1)." 992 ::= { mplsInSegmentEntry 4 } 994 mplsInSegmentXCIndex OBJECT-TYPE 995 SYNTAX Unsigned32 (0..4294967295) 996 MAX-ACCESS read-only 997 STATUS current 998 DESCRIPTION 999 "Index into mplsXCTable which identifies which cross- 1000 connect entry this segment is part of. A value of 1001 zero indicates that this entry is not referred to by 1002 any cross-connect entry. When a cross-connect entry 1003 is created which this in-segment is a part of, this 1004 object is automatically updated to reflect the value 1005 of mplsXCIndex of that cross-connect entry." 1006 ::= { mplsInSegmentEntry 5 } 1008 mplsInSegmentOwner OBJECT-TYPE 1009 SYNTAX MplsOwner 1010 MAX-ACCESS read-only 1011 STATUS current 1012 DESCRIPTION 1013 "Denotes the entity that created and is responsible 1014 for managing this segment." 1015 ::= { mplsInSegmentEntry 6 } 1017 mplsInSegmentTrafficParamPtr OBJECT-TYPE 1018 SYNTAX RowPointer 1019 MAX-ACCESS read-create 1020 STATUS current 1021 DESCRIPTION 1022 "This variable represents a pointer to the traffic 1023 parameter specification for this in-segment. This 1024 value may point at an entry in the 1025 mplsTrafficParamTable to indicate which 1026 mplsTrafficParamEntry is to be assigned to this 1027 segment. This value may optionally point at an 1028 externally defined traffic parameter specification 1029 table. A value of zeroDotZero indicates best-effort 1030 treatment. By having the same value of this object, 1031 two or more segments can indicate resource sharing. 1032 This object cannot be modified if 1033 mplsInSegmentRowStatus is active(1)." 1034 DEFVAL { zeroDotZero } 1035 ::= { mplsInSegmentEntry 7 } 1037 mplsInSegmentRowStatus OBJECT-TYPE 1038 SYNTAX RowStatus 1039 MAX-ACCESS read-create 1040 STATUS current 1041 DESCRIPTION 1042 "This variable is used to create, modify, and/or 1043 delete a row in this table." 1044 ::= { mplsInSegmentEntry 8 } 1046 mplsInSegmentStorageType OBJECT-TYPE 1047 SYNTAX StorageType 1048 MAX-ACCESS read-create 1049 STATUS current 1050 DESCRIPTION 1051 "This variable indicates the storage type for this 1052 object. This object cannot be modified if 1053 mplsInSegmentRowStatus is active(1). If this 1054 variable is set to readOnly(5), and the 1055 corresponding LFIB entry is removed, then the agent 1056 must remove this row shortly thereafter [RFC2579]." 1057 ::= { mplsInSegmentEntry 9 } 1059 -- End of mplsInSegmentTable 1061 -- In-segment performance table. 1063 mplsInSegmentPerfTable OBJECT-TYPE 1064 SYNTAX SEQUENCE OF MplsInSegmentPerfEntry 1065 MAX-ACCESS not-accessible 1066 STATUS current 1067 DESCRIPTION 1068 "This table contains statistical information for 1069 incoming MPLS segments to an LSR." 1070 ::= { mplsLsrObjects 4 } 1072 mplsInSegmentPerfEntry OBJECT-TYPE 1073 SYNTAX MplsInSegmentPerfEntry 1074 MAX-ACCESS not-accessible 1075 STATUS current 1076 DESCRIPTION 1077 "An entry in this table contains statistical 1078 information about one incoming segment which was 1079 configured in the mplsInSegmentTable. The counters 1080 in this entry should behave in a manner similar to 1081 that of the interface. 1082 mplsInSegmentPerfDiscontinuityTime indicates the 1083 time of the last discontinuity in these objects." 1084 AUGMENTS { mplsInSegmentEntry } 1085 ::= { mplsInSegmentPerfTable 1 } 1087 MplsInSegmentPerfEntry ::= SEQUENCE { 1088 mplsInSegmentOctets Counter32, 1089 mplsInSegmentPackets Counter32, 1090 mplsInSegmentErrors Counter32, 1091 mplsInSegmentDiscards Counter32, 1093 -- high capacity counter 1094 mplsInSegmentHCOctets Counter64, 1096 mplsInSegmentPerfDiscontinuityTime TimeStamp 1097 } 1099 mplsInSegmentOctets OBJECT-TYPE 1100 SYNTAX Counter32 1101 MAX-ACCESS read-only 1102 STATUS current 1103 DESCRIPTION 1104 "This value represents the total number of octets 1105 received by this segment. It MUST be equal to the 1106 least significant 32 bits of mplsInSegmentHCOctets." 1107 ::= { mplsInSegmentPerfEntry 1 } 1109 mplsInSegmentPackets OBJECT-TYPE 1110 SYNTAX Counter32 1111 MAX-ACCESS read-only 1112 STATUS current 1113 DESCRIPTION 1114 "Total number of packets received by this segment." 1115 ::= { mplsInSegmentPerfEntry 2 } 1117 mplsInSegmentErrors OBJECT-TYPE 1118 SYNTAX Counter32 1119 MAX-ACCESS read-only 1120 STATUS current 1121 DESCRIPTION 1122 "The number of errored packets received on this 1123 segment." 1124 ::= { mplsInSegmentPerfEntry 3 } 1126 mplsInSegmentDiscards OBJECT-TYPE 1127 SYNTAX Counter32 1128 MAX-ACCESS read-only 1129 STATUS current 1130 DESCRIPTION 1131 "The number of labeled packets received on this in- 1132 segment, which were chosen to be discarded even 1133 though no errors had been detected to prevent their 1134 being transmitted. One possible reason for 1135 discarding such a labeled packet could be to free up 1136 buffer space." 1137 ::= { mplsInSegmentPerfEntry 4 } 1139 mplsInSegmentHCOctets OBJECT-TYPE 1140 SYNTAX Counter64 1141 MAX-ACCESS read-only 1142 STATUS current 1143 DESCRIPTION 1144 "The total number of octets received. This is the 64 1145 bit version of mplsInSegmentOctets." 1146 ::= { mplsInSegmentPerfEntry 5 } 1148 mplsInSegmentPerfDiscontinuityTime OBJECT-TYPE 1149 SYNTAX TimeStamp 1150 MAX-ACCESS read-only 1151 STATUS current 1152 DESCRIPTION 1153 "The value of sysUpTime on the most recent occasion 1154 at which any one or more of this segment's Counter32 1155 or Counter64 suffered a discontinuity. If no such 1156 discontinuities have occurred since the last re- 1157 initialization of the local management subsystem, 1158 then this object contains a zero value." 1159 ::= { mplsInSegmentPerfEntry 6 } 1161 -- End of mplsInSegmentPerfTable. 1163 -- Out-segment table. 1165 mplsOutSegmentIndexNext OBJECT-TYPE 1166 SYNTAX Unsigned32 (0..4294967295) 1167 MAX-ACCESS read-only 1168 STATUS current 1169 DESCRIPTION 1170 "This object contains the next appropriate value to 1171 be used for mplsOutSegmentIndex when creating 1172 entries in the mplsOutSegmentTable. If the number 1173 of unassigned entries is exhausted, this object will 1174 take on the value of 0. To obtain the 1175 mplsOutSegmentIndex value for a new entry, the 1176 manager must first issue a management protocol 1177 retrieval operation to obtain the current value of 1178 this object. The agent should modify the value to 1179 reflect the next unassigned index after each 1180 retrieval operation. After a manager retrieves a 1181 value the agent will determine through its local 1182 policy when this index value will be made available 1183 for reuse." 1184 ::= { mplsLsrObjects 5 } 1186 mplsOutSegmentTable OBJECT-TYPE 1187 SYNTAX SEQUENCE OF MplsOutSegmentEntry 1188 MAX-ACCESS not-accessible 1189 STATUS current 1190 DESCRIPTION 1191 "This table contains a representation of the outgoing 1192 segments from an LSR." 1193 ::= { mplsLsrObjects 6 } 1195 mplsOutSegmentEntry OBJECT-TYPE 1196 SYNTAX MplsOutSegmentEntry 1197 MAX-ACCESS not-accessible 1198 STATUS current 1199 DESCRIPTION 1200 "An entry in this table represents one outgoing 1201 segment. An entry can be created by a network 1202 administrator or an SNMP agent, or an MPLS signaling 1203 protocol. The object mplsOutSegmentOwner indicates 1204 the creator of this entry. The value of 1205 mplsOutSegmentRowStatus cannot be active(1)unless 1206 the ifTable entry corresponding to 1207 mplsOutSegmentIfIndex exists." 1208 INDEX { mplsOutSegmentIndex } 1209 ::= { mplsOutSegmentTable 1 } 1211 MplsOutSegmentEntry ::= SEQUENCE { 1212 mplsOutSegmentIndex Unsigned32, 1213 mplsOutSegmentIfIndex InterfaceIndexOrZero, 1214 mplsOutSegmentPushTopLabel TruthValue, 1215 mplsOutSegmentTopLabel MplsLabel, 1216 mplsOutSegmentNextHopIpAddrType InetAddressType, 1217 mplsOutSegmentNextHopIpAddr InetAddress, 1218 mplsOutSegmentXCIndex Unsigned32, 1219 mplsOutSegmentOwner MplsOwner , 1220 mplsOutSegmentTrafficParamPtr RowPointer, 1221 mplsOutSegmentRowStatus RowStatus, 1222 mplsOutSegmentStorageType StorageType 1223 } 1225 mplsOutSegmentIndex OBJECT-TYPE 1226 SYNTAX Unsigned32(0..2147483647) 1227 MAX-ACCESS not-accessible 1228 STATUS current 1229 DESCRIPTION 1230 "This value contains a unique index for this row. 1231 While a value of 0 is not valid as an index for this 1232 row it can be supplied as a valid value to index 1233 mplsXCTable to access entries for which no out- 1234 segment has been configured." 1235 ::= { mplsOutSegmentEntry 1 } 1237 mplsOutSegmentIfIndex OBJECT-TYPE 1238 SYNTAX InterfaceIndex 1239 MAX-ACCESS read-create 1240 STATUS current 1241 DESCRIPTION 1242 "This value must contain the interface index of the 1243 outgoing interface. This object cannot be modified 1244 if mplsOutSegmentRowStatus is active(1). The 1245 mplsOutSegmentRowStatus cannot be set to active(1) 1246 until this object is set to a value corresponding to 1247 a valid ifEntry." 1248 ::= { mplsOutSegmentEntry 2 } 1250 mplsOutSegmentPushTopLabel OBJECT-TYPE 1251 SYNTAX TruthValue 1252 MAX-ACCESS read-create 1253 STATUS current 1254 DESCRIPTION 1255 "This value indicates whether or not a top label 1256 should be pushed onto the outgoing packet's label 1257 stack. The value of this variable MUST be set to 1258 true if the outgoing interface does not support pop- 1259 and-go (for example an ATM interface) or if it is a 1260 tunnel origination. Note that it is considered an 1261 error in the case that mplsOutSegmentPushTopLabel is 1262 set to false, but the cross-connect entry which 1263 refers to this out-segment has a non-zero 1264 mplsLabelStackIndex. The LSR MUST ensure that this 1265 situation does not happen. This object cannot be 1266 modified if mplsOutSegmentRowStatus is active(1)." 1267 DEFVAL { true } 1268 ::= { mplsOutSegmentEntry 3 } 1270 mplsOutSegmentTopLabel OBJECT-TYPE 1271 SYNTAX MplsLabel 1272 MAX-ACCESS read-create 1273 STATUS current 1274 DESCRIPTION 1275 "If mplsOutSegmentPushTopLabel is true then this 1276 represents the label that should be pushed onto the 1277 top of the outgoing packet's label stack. Otherwise 1278 this value SHOULD be set to 0 by the management 1279 station and MUST be ignored by the agent. This 1280 object cannot be modified if mplsOutSegmentRowStatus 1281 is active(1)." 1282 DEFVAL { 0 } 1283 ::= { mplsOutSegmentEntry 4 } 1285 mplsOutSegmentNextHopIpAddrType OBJECT-TYPE 1286 SYNTAX InetAddressType 1287 MAX-ACCESS read-create 1288 STATUS current 1289 DESCRIPTION 1290 "Indicates that the next hop address type is IPv4 1291 when set to ipv4 (1) or IPv6 when set to ipv6 (2). 1292 A value of unknown (0) is allowed only when the 1293 outgoing interface is of type point-to-point. If any 1294 other values are attempted in a set operation the 1295 agent MUST return an inconsistentValue error. This 1296 object cannot be modified if mplsOutSegmentRowStatus 1297 is active(1)." 1298 ::= { mplsOutSegmentEntry 5 } 1300 mplsOutSegmentNextHopIpAddr OBJECT-TYPE 1301 SYNTAX InetAddress 1302 MAX-ACCESS read-create 1303 STATUS current 1304 DESCRIPTION 1305 "The IPv4 or IPv6 address of the next hop. Its value 1306 is significant only when 1307 mplsOutSegmentNextHopIpAddrType is ipv4 (1) or ipv6 1308 (2). Otherwise a management entity SHOULD set this 1309 to 0 and an agent MUST ignore it. Likewise an agent 1310 MUST return a value of 0 for a retrieval operation. 1311 This object cannot be modified if 1312 mplsOutSegmentRowStatus is active(1)." 1313 ::= { mplsOutSegmentEntry 6 } 1315 mplsOutSegmentXCIndex OBJECT-TYPE 1316 SYNTAX Unsigned32 (0..4294967295) 1317 MAX-ACCESS read-only 1318 STATUS current 1319 DESCRIPTION 1320 "Index into mplsXCTable which identifies which cross- 1321 connect entry this segment is part of. A value of 1322 zero indicates that this entry is not referred to by 1323 any cross-connect entry. When a cross-connect entry 1324 is created which this out-segment is a part of, this 1325 object is MUST be updated by the agent to reflect 1326 the value of mplsXCIndex of that cross-connect 1327 entry." 1328 ::= { mplsOutSegmentEntry 7 } 1330 mplsOutSegmentOwner OBJECT-TYPE 1331 SYNTAX MplsOwner 1332 MAX-ACCESS read-only 1333 STATUS current 1334 DESCRIPTION 1335 "Denotes the entity which created and is responsible 1336 for managing this segment." 1337 ::= { mplsOutSegmentEntry 8 } 1339 mplsOutSegmentTrafficParamPtr OBJECT-TYPE 1340 SYNTAX RowPointer 1341 MAX-ACCESS read-create 1342 STATUS current 1343 DESCRIPTION 1344 "This variable represents a pointer to the traffic 1345 parameter specification for this out-segment. This 1346 value may point at an entry in the 1347 mplsTrafficParamTable to indicate which 1348 mplsTrafficParamEntry is to be assigned to this 1349 segment. This value may optionally point at an 1350 externally defined traffic parameter specification 1351 table. A value of zeroDotZero indicates best-effort 1352 treatment. By having the same value of this object, 1353 two or more segments can indicate resource sharing. 1354 This object cannot be modified if 1355 mplsOutSegmentRowStatus is active(1)." 1356 DEFVAL { zeroDotZero } 1357 ::= { mplsOutSegmentEntry 9 } 1359 mplsOutSegmentRowStatus OBJECT-TYPE 1360 SYNTAX RowStatus 1361 MAX-ACCESS read-create 1362 STATUS current 1363 DESCRIPTION 1364 "For creating, modifying, and deleting this row." 1365 ::= { mplsOutSegmentEntry 10 } 1367 mplsOutSegmentStorageType OBJECT-TYPE 1368 SYNTAX StorageType 1369 MAX-ACCESS read-create 1370 STATUS current 1371 DESCRIPTION 1372 "This variable indicates the storage type for this 1373 object. This object cannot be modified if 1374 mplsOutSegmentRowStatus is active(1). If this 1375 variable is set to readOnly(5), and the 1376 corresponding LFIB entry is removed, then the agent 1377 must remove this row shortly thereafter." 1378 ::= { mplsOutSegmentEntry 11 } 1380 -- End of mplsOutSegmentTable 1382 -- Out-segment performance table. 1384 mplsOutSegmentPerfTable OBJECT-TYPE 1385 SYNTAX SEQUENCE OF MplsOutSegmentPerfEntry 1386 MAX-ACCESS not-accessible 1387 STATUS current 1388 DESCRIPTION 1389 "This table contains statistical information about 1390 outgoing segments from an LSR. The counters in this 1391 entry should behave in a manner similar to that of 1392 the interface." 1393 ::= { mplsLsrObjects 7 } 1395 mplsOutSegmentPerfEntry OBJECT-TYPE 1396 SYNTAX MplsOutSegmentPerfEntry 1397 MAX-ACCESS not-accessible 1398 STATUS current 1399 DESCRIPTION 1400 "An entry in this table contains statistical 1401 information about one outgoing segment configured in 1402 mplsOutSegmentTable. 1403 mplsOutSegmentPerfDiscontinuityTime indicates the 1404 time of the last discontinuity in these objects. " 1405 AUGMENTS { mplsOutSegmentEntry } 1406 ::= { mplsOutSegmentPerfTable 1 } 1408 MplsOutSegmentPerfEntry ::= SEQUENCE { 1409 mplsOutSegmentOctets Counter32, 1410 mplsOutSegmentPackets Counter32, 1411 mplsOutSegmentErrors Counter32, 1412 mplsOutSegmentDiscards Counter32, 1414 -- HC counter 1415 mplsOutSegmentHCOctets Counter64, 1417 mplsOutSegmentPerfDiscontinuityTime TimeStamp 1418 } 1420 mplsOutSegmentOctets OBJECT-TYPE 1421 SYNTAX Counter32 1422 MAX-ACCESS read-only 1423 STATUS current 1424 DESCRIPTION 1425 "This value contains the total number of octets sent 1426 on this segment. It MUST be equal to the least 1427 significant 32 bits of mplsOutSegmentHCOctets." 1428 ::= { mplsOutSegmentPerfEntry 1 } 1430 mplsOutSegmentPackets OBJECT-TYPE 1431 SYNTAX Counter32 1432 MAX-ACCESS read-only 1433 STATUS current 1434 DESCRIPTION 1435 "This value contains the total number of packets sent 1436 on this segment." 1437 ::= { mplsOutSegmentPerfEntry 2 } 1439 mplsOutSegmentErrors OBJECT-TYPE 1440 SYNTAX Counter32 1441 MAX-ACCESS read-only 1442 STATUS current 1443 DESCRIPTION 1444 "Number of packets that could not be sent due to 1445 errors on this segment." 1446 ::= { mplsOutSegmentPerfEntry 3 } 1448 mplsOutSegmentDiscards OBJECT-TYPE 1449 SYNTAX Counter32 1450 MAX-ACCESS read-only 1451 STATUS current 1452 DESCRIPTION 1453 "The number of labeled packets received on this out- 1454 segment, which were chosen to be discarded even 1455 though no errors had been detected to prevent their 1456 being transmitted. One possible reason for 1457 discarding such a labeled packet could be to free up 1458 buffer space." 1459 ::= { mplsOutSegmentPerfEntry 4 } 1461 mplsOutSegmentHCOctets OBJECT-TYPE 1462 SYNTAX Counter64 1463 MAX-ACCESS read-only 1464 STATUS current 1465 DESCRIPTION 1466 "Total number of octets sent. This is the 64 bit 1467 version of mplsOutSegmentOctets." 1468 ::= { mplsOutSegmentPerfEntry 5 } 1470 mplsOutSegmentPerfDiscontinuityTime OBJECT-TYPE 1471 SYNTAX TimeStamp 1472 MAX-ACCESS read-only 1473 STATUS current 1474 DESCRIPTION 1475 "The value of sysUpTime on the most recent occasion 1476 at which any one or more of this segment's Counter32 1477 or Counter64 suffered a discontinuity. If no such 1478 discontinuities have occurred since the last re- 1479 initialization of the local management subsystem, 1480 then this object contains a zero value." 1481 ::= { mplsOutSegmentPerfEntry 6 } 1483 -- End of mplsOutSegmentPerfTable. 1485 -- Cross-connect table. 1487 mplsXCIndexNext OBJECT-TYPE 1488 SYNTAX Unsigned32 (0..4294967295) 1489 MAX-ACCESS read-only 1490 STATUS current 1491 DESCRIPTION 1492 "This object contains an appropriate value to be used 1493 for mplsXCIndex when creating entries in the 1494 mplsXCTable. The value 0 indicates that no 1495 unassigned entries are available. To obtain the 1496 value of mplsXCIndex for a new entry in the 1497 mplsXCTable, the manager issues a management 1498 protocol retrieval operation to obtain the current 1499 value of mplsXCIndex. After each retrieval 1500 operation, the agent should modify the value to 1501 reflect the next unassigned index. After a manager 1502 retrieves a value the agent will determine through 1503 its local policy when this index value will be made 1504 available for reuse." 1505 ::= { mplsLsrObjects 8 } 1507 mplsXCTable OBJECT-TYPE 1508 SYNTAX SEQUENCE OF MplsXCEntry 1509 MAX-ACCESS not-accessible 1510 STATUS current 1511 DESCRIPTION 1512 "This table specifies information for switching 1513 between LSP segments. It supports point-to-point, 1514 point-to-multipoint and multipoint-to-point 1515 connections. mplsLabelStackTable specifies the 1516 label stack information for a cross-connect LSR and 1517 is referred to from mplsXCTable." 1518 ::= { mplsLsrObjects 9 } 1520 mplsXCEntry OBJECT-TYPE 1521 SYNTAX MplsXCEntry 1522 MAX-ACCESS not-accessible 1523 STATUS current 1524 DESCRIPTION 1525 "A row in this table represents one cross-connect 1526 entry. It is indexed by the following objects: 1528 - cross-connect index mplsXCIndex that uniquely 1529 identifies a group of cross-connect entries 1530 - interface index of the in-segment, 1531 mplsXCInSegmentIfIndex 1532 - incoming label(s), mplsXCInSegmentLabel 1533 - out-segment index, mplsXCOutSegmentIndex 1535 LSPs originating at this LSR: 1536 These are represented by using the special 1537 combination of values mplsXCInSegmentIfIndex=0 and 1538 mplsXCInSegmentLabel=0 as indexes. In this case 1539 the mplsXCOutSegmentIndex MUST be non-zero. 1541 LSPs terminating at this LSR: 1542 These are represented by using the special value 1543 mplsXCOutSegmentIndex=0 as index. 1545 Special labels: 1546 Entries indexed by reserved MPLS label values 0 1547 through 15 imply LSPs terminating at this LSR and 1548 MUST have mplsXCOutSegmentIfIndex = 0. Note that 1549 situations where LSPs are terminated with incoming 1550 label equal to 0, should have 1551 mplsXCInSegmentIfIndex = 0 as well, but can be 1552 distinguished from LSPs originating at this LSR 1553 because the mplsXCOutSegmentIfIndex = 0. The 1554 mplsXCOutSegmentIfIndex MUST only be set to 0 in 1555 the case of LSPs terminating at this LSR. 1557 An entry can be created by a network administrator 1558 or by an SNMP agent as instructed by an MPLS 1559 signaling protocol." 1560 INDEX { 1561 mplsXCIndex, 1562 mplsXCInSegmentIfIndex, 1563 mplsXCInSegmentLabel, 1564 mplsXCOutSegmentIndex 1565 } 1566 ::= { mplsXCTable 1 } 1568 MplsXCEntry ::= SEQUENCE { 1569 mplsXCIndex Unsigned32, 1570 mplsXCInSegmentIfIndex InterfaceIndexOrZero, 1571 mplsXCInSegmentLabel MplsLabel, 1572 mplsXCOutSegmentIndex Unsigned32, 1573 mplsXCLspId MplsLSPID, 1574 mplsXCLabelStackIndex Unsigned32, 1575 mplsXCIsPersistent TruthValue, 1576 mplsXCOwner MplsOwner , 1577 mplsXCRowStatus RowStatus, 1578 mplsXCStorageType StorageType, 1579 mplsXCAdminStatus INTEGER, 1580 mplsXCOperStatus INTEGER 1581 } 1583 mplsXCIndex OBJECT-TYPE 1584 SYNTAX Unsigned32 (1..2147483647) 1585 MAX-ACCESS not-accessible 1586 STATUS current 1587 DESCRIPTION 1588 "Primary index for the conceptual row identifying a 1589 group of cross-connect segments." 1590 ::= { mplsXCEntry 1 } 1592 mplsXCInSegmentIfIndex OBJECT-TYPE 1593 SYNTAX InterfaceIndexOrZero 1594 MAX-ACCESS not-accessible 1595 STATUS current 1596 DESCRIPTION 1597 "Interface index of the in-segment for LSPs not 1598 originating at this LSR. Zero (along with 1599 mplsXCInSegmentLabel) otherwise." 1600 ::= { mplsXCEntry 2 } 1602 mplsXCInSegmentLabel OBJECT-TYPE 1603 SYNTAX MplsLabel 1604 MAX-ACCESS not-accessible 1605 STATUS current 1606 DESCRIPTION 1607 "Incoming label." 1608 ::= { mplsXCEntry 3 } 1610 mplsXCOutSegmentIndex OBJECT-TYPE 1611 SYNTAX Unsigned32 (1..2147483647) 1612 MAX-ACCESS not-accessible 1613 STATUS current 1614 DESCRIPTION 1615 "Index of out-segment for LSPs not terminating on 1616 this LSR; zero otherwise." 1617 ::= { mplsXCEntry 4 } 1619 mplsXCLspId OBJECT-TYPE 1620 SYNTAX MplsLSPID 1621 MAX-ACCESS read-create 1622 STATUS current 1623 DESCRIPTION 1624 "This value identifies the label switched path that 1625 this cross-connect entry belongs to. This object 1626 cannot be modified if mplsXCRowStatus is active(1)." 1627 ::= { mplsXCEntry 5 } 1629 mplsXCLabelStackIndex OBJECT-TYPE 1630 SYNTAX Unsigned32 (0..4294967295) 1631 MAX-ACCESS read-create 1632 STATUS current 1633 DESCRIPTION 1634 "Primary index into mplsLabelStackTable identifying a 1635 stack of labels to be pushed beneath the top label. 1636 Note that the top label identified by the out- 1637 segment ensures that all the components of a 1638 multipoint-to-point connection have the same 1639 outgoing label. A value of 0 indicates that no 1640 labels are to be stacked beneath the top label. This 1641 object cannot be modified if mplsXCRowStatus is 1642 active(1)." 1643 ::= { mplsXCEntry 6 } 1645 mplsXCIsPersistent OBJECT-TYPE 1646 SYNTAX TruthValue 1647 MAX-ACCESS read-create 1648 STATUS current 1649 DESCRIPTION 1650 "Denotes whether or not this cross-connect entry and 1651 associated in- and out-segments should be restored 1652 automatically after failures. This value MUST be 1653 set to false in cases where this cross-connect entry 1654 was created by a signaling protocol. This object 1655 cannot be modified if mplsXCRowStatus is active(1)." 1656 DEFVAL { false } 1657 ::= { mplsXCEntry 7 } 1659 mplsXCOwner OBJECT-TYPE 1660 SYNTAX MplsOwner 1661 MAX-ACCESS read-only 1662 STATUS current 1663 DESCRIPTION 1664 "Denotes the entity that created and is responsible 1665 for managing this cross-connect. This object cannot 1666 be modified if mplsXCRowStatus is active(1)." 1667 ::= { mplsXCEntry 8 } 1669 mplsXCRowStatus OBJECT-TYPE 1670 SYNTAX RowStatus 1671 MAX-ACCESS read-create 1672 STATUS current 1673 DESCRIPTION 1674 "For creating, modifying, and deleting this row." 1675 ::= { mplsXCEntry 9 } 1677 mplsXCStorageType OBJECT-TYPE 1678 SYNTAX StorageType 1679 MAX-ACCESS read-only 1680 STATUS current 1681 DESCRIPTION 1682 "Defines the storage type support provided for this 1683 object by the agent. If this variable is set to 1684 readOnly(5), and the corresponding LFIB entry is 1685 removed, then the agent must remove this row shortly 1686 thereafter." 1687 ::= { mplsXCEntry 10 } 1689 mplsXCAdminStatus OBJECT-TYPE 1690 SYNTAX INTEGER { 1691 up(1), -- ready to pass packets 1692 down(2), 1693 testing(3) -- in some test mode 1694 } 1695 MAX-ACCESS read-create 1696 STATUS current 1697 DESCRIPTION 1698 "The desired operational status of this segment." 1699 ::= { mplsXCEntry 11 } 1701 mplsXCOperStatus OBJECT-TYPE 1702 SYNTAX INTEGER { 1703 up(1), -- ready to pass packets 1704 down(2), 1705 testing(3), -- in some test mode 1706 unknown(4), -- status cannot be determined 1707 -- for some reason. 1708 dormant(5), 1709 notPresent(6), -- some component is missing 1710 lowerLayerDown(7) -- down due to the state of 1711 -- lower layer interfaces 1712 } 1713 MAX-ACCESS read-only 1714 STATUS current 1715 DESCRIPTION 1716 "The actual operational status of this cross- 1717 connect." 1718 ::= { mplsXCEntry 12 } 1720 -- End of mplsXCTable 1722 -- Label stack table. 1724 mplsMaxLabelStackDepth OBJECT-TYPE 1725 SYNTAX Integer32 (1..2147483647) 1726 MAX-ACCESS read-only 1727 STATUS current 1728 DESCRIPTION 1729 "The maximum stack depth supported by this LSR." 1730 ::= { mplsLsrObjects 10 } 1732 mplsLabelStackIndexNext OBJECT-TYPE 1733 SYNTAX Unsigned32 (0..4294967295) 1734 MAX-ACCESS read-only 1735 STATUS current 1736 DESCRIPTION 1737 "This object contains an appropriate value to be used 1738 for mplsLabelStackIndex when creating entries in the 1739 mplsLabelStackTable. The value 0 indicates that no 1740 unassigned entries are available. To obtain an 1741 mplsLabelStackIndex value for a new entry, the 1742 manager issues a management protocol retrieval 1743 operation to obtain the current value of this 1744 object. After each retrieval operation, the agent 1745 should modify the value to reflect the next 1746 unassigned index. After a manager retrieves a value 1747 the agent will determine through its local policy 1748 when this index value will be made available for 1749 reuse." 1750 ::= { mplsLsrObjects 11 } 1752 mplsLabelStackTable OBJECT-TYPE 1753 SYNTAX SEQUENCE OF MplsLabelStackEntry 1754 MAX-ACCESS not-accessible 1755 STATUS current 1756 DESCRIPTION 1757 "This table specifies the label stack to be pushed 1758 onto a packet, beneath the top label. Entries into 1759 this table are referred to from mplsXCTable." 1760 ::= { mplsLsrObjects 12 } 1762 mplsLabelStackEntry OBJECT-TYPE 1763 SYNTAX MplsLabelStackEntry 1764 MAX-ACCESS not-accessible 1765 STATUS current 1766 DESCRIPTION 1767 "An entry in this table represents one label which is 1768 to be pushed onto an outgoing packet, beneath the 1769 top label. An entry can be created by a network 1770 administrator or by an SNMP agent as instructed by 1771 an MPLS signaling protocol." 1772 INDEX { mplsLabelStackIndex, mplsLabelStackLabelIndex } 1773 ::= { mplsLabelStackTable 1 } 1775 MplsLabelStackEntry ::= SEQUENCE { 1776 mplsLabelStackIndex Unsigned32, 1777 mplsLabelStackLabelIndex Unsigned32, 1778 mplsLabelStackLabel MplsLabel, 1779 mplsLabelStackRowStatus RowStatus, 1780 mplsLabelStackStorageType StorageType 1781 } 1783 mplsLabelStackIndex OBJECT-TYPE 1784 SYNTAX Unsigned32 (1..2147483647) 1785 MAX-ACCESS not-accessible 1786 STATUS current 1787 DESCRIPTION 1788 "Primary index for this row identifying a stack of 1789 labels to be pushed on an outgoing packet, beneath 1790 the top label." 1791 ::= { mplsLabelStackEntry 1 } 1793 mplsLabelStackLabelIndex OBJECT-TYPE 1794 SYNTAX Unsigned32 (1..2147483647) 1795 MAX-ACCESS not-accessible 1796 STATUS current 1797 DESCRIPTION 1798 "Secondary index for this row identifying one label 1799 of the stack. Note that an entry with a smaller 1800 mplsLabelStackLabelIndex would refer to a label 1801 higher up the label stack and would be popped at a 1802 downstream LSR before a label represented by a 1803 higher mplsLabelStackLabelIndex at a downstream 1804 LSR." 1805 ::= { mplsLabelStackEntry 2 } 1807 mplsLabelStackLabel OBJECT-TYPE 1808 SYNTAX MplsLabel 1809 MAX-ACCESS read-create 1810 STATUS current 1811 DESCRIPTION 1812 "The label to pushed." 1813 ::= { mplsLabelStackEntry 3 } 1815 mplsLabelStackRowStatus OBJECT-TYPE 1816 SYNTAX RowStatus 1817 MAX-ACCESS read-create 1818 STATUS current 1819 DESCRIPTION 1820 "For creating, modifying, and deleting this row." 1821 ::= { mplsLabelStackEntry 4 } 1823 mplsLabelStackStorageType OBJECT-TYPE 1824 SYNTAX StorageType 1825 MAX-ACCESS read-create 1826 STATUS current 1827 DESCRIPTION 1828 " Defines the storage type support provided for this 1829 object by the agent. If this variable is set to 1830 readOnly(5), and the corresponding LFIB entry is 1831 removed, then the agent must remove this row shortly 1832 thereafter." 1833 ::= { mplsLabelStackEntry 5 } 1835 -- End of mplsLabelStackTable 1837 -- Traffic Parameter table. 1839 mplsTrafficParamIndexNext OBJECT-TYPE 1840 SYNTAX Unsigned32 (0..4294967295) 1841 MAX-ACCESS read-only 1842 STATUS current 1843 DESCRIPTION 1844 "This object contains an appropriate value which will 1845 be used for mplsTrafficParamIndex when creating 1846 entries in the mplsTrafficParamTable. The value 0 1847 indicates that no unassigned entries are available. 1848 To obtain the mplsTrafficParamIndex value for a new 1849 entry, the manager issues a management protocol 1850 retrieval operation to obtain the current value of 1851 this object. After each retrieval operation, the 1852 agent should modify the value to reflect the next 1853 unassigned index. After a manager retrieves a value 1854 the agent will determine through its local policy 1855 when this index value will be made available for 1856 reuse." 1857 ::= { mplsLsrObjects 13 } 1859 mplsTrafficParamTable OBJECT-TYPE 1860 SYNTAX SEQUENCE OF MplsTrafficParamEntry 1861 MAX-ACCESS not-accessible 1862 STATUS current 1863 DESCRIPTION 1864 "This table specifies the Traffic Parameter objects 1865 for in and out-segments." 1866 ::= { mplsLsrObjects 14 } 1868 mplsTrafficParamEntry OBJECT-TYPE 1869 SYNTAX MplsTrafficParamEntry 1870 MAX-ACCESS not-accessible 1871 STATUS current 1872 DESCRIPTION 1873 "An entry in this table represents the TrafficParam 1874 objects for one or more in or out segments. A 1875 single entry can be pointed to by multiple segments 1876 indicating resource sharing." 1877 INDEX { mplsTrafficParamIndex } 1878 ::= { mplsTrafficParamTable 1 } 1880 MplsTrafficParamEntry ::= SEQUENCE { 1881 mplsTrafficParamIndex Unsigned32, 1882 mplsTrafficParamMaxRate MplsBitRate, 1883 mplsTrafficParamMeanRate MplsBitRate, 1884 mplsTrafficParamMaxBurstSize MplsBurstSize, 1885 mplsTrafficParamRowStatus RowStatus, 1886 mplsTrafficParamStorageType StorageType 1887 } 1889 mplsTrafficParamIndex OBJECT-TYPE 1890 SYNTAX Unsigned32 (1..2147483647) 1891 MAX-ACCESS not-accessible 1892 STATUS current 1893 DESCRIPTION 1894 "Uniquely identifies this row of the table. Note 1895 that zero represents an invalid index." 1896 ::= { mplsTrafficParamEntry 1 } 1898 mplsTrafficParamMaxRate OBJECT-TYPE 1899 SYNTAX MplsBitRate 1900 UNITS "kilobits per second" 1901 MAX-ACCESS read-create 1902 STATUS current 1903 DESCRIPTION 1904 "Maximum rate in kilobits/second." 1905 ::= { mplsTrafficParamEntry 2 } 1907 mplsTrafficParamMeanRate OBJECT-TYPE 1908 SYNTAX MplsBitRate 1909 UNITS "kilobits per second" 1910 MAX-ACCESS read-create 1911 STATUS current 1912 DESCRIPTION 1913 "Mean rate in kilobits/second." 1914 ::= { mplsTrafficParamEntry 3 } 1916 mplsTrafficParamMaxBurstSize OBJECT-TYPE 1917 SYNTAX MplsBurstSize 1918 UNITS "bytes" 1919 MAX-ACCESS read-create 1920 STATUS current 1921 DESCRIPTION 1922 "Maximum burst size in bytes." 1923 ::= { mplsTrafficParamEntry 4 } 1925 mplsTrafficParamRowStatus OBJECT-TYPE 1926 SYNTAX RowStatus 1927 MAX-ACCESS read-create 1928 STATUS current 1929 DESCRIPTION 1930 "For creating, modifying, and deleting this row." 1931 ::= { mplsTrafficParamEntry 5 } 1933 mplsTrafficParamStorageType OBJECT-TYPE 1934 SYNTAX StorageType 1935 MAX-ACCESS read-create 1936 STATUS current 1937 DESCRIPTION 1938 " Defines the storage type support provided for this 1939 object by the agent. If this variable is set to 1940 readOnly(5), and the corresponding LFIB entry is 1941 removed, then the agent must remove this row shortly 1942 thereafter." 1943 ::= { mplsTrafficParamEntry 6 } 1945 -- End of mplsTrafficParamTable 1947 -- Notification Configuration 1949 mplsXCNotificationsEnable OBJECT-TYPE 1950 SYNTAX TruthValue 1951 MAX-ACCESS read-write 1952 STATUS current 1953 DESCRIPTION 1954 "If this object is set to true(1), then it enables 1955 the emission of mplsXCUp and mplsXCDown 1956 notifications; otherwise these notifications are not 1957 emitted." 1958 DEFVAL { false } 1959 ::= { mplsLsrObjects 15 } 1961 -- Cross-connect. 1963 mplsXCUp NOTIFICATION-TYPE 1964 OBJECTS { 1965 mplsXCOperStatus, -- start of range 1966 mplsXCOperStatus -- end of range 1967 } 1968 STATUS current 1969 DESCRIPTION 1970 "This notification is generated when the 1971 mplsXCOperStatus object for one or more contiguous 1972 entries in mplsXCTable are about to enter the up(1) 1973 state from some other. The included values of 1974 mplsXCOperStatus MUST both be set equal to this 1975 other state. The two instances of mplsXCOperStatus 1976 in this notification indicate the range of indexes 1977 that are affected. Note that all the indexes of the 1978 two ends of the range can be derived from the 1979 instance identifiers of these two objects. For 1980 cases where a contiguous range of cross-connects 1981 have transitioned into the up(1) state at roughly 1982 the same time, the device SHOULD issue a single 1983 notification for each range of contiguous indexes in 1984 an effort to minimize the emission of a large number 1985 of notifications. If a notification has to be 1986 issued for just a single cross-connect entry, then 1987 the instance identifier (and values) of the two 1988 mplsXCOperStatus objects MUST be the identical." 1989 ::= { mplsLsrNotifications 1 } 1991 mplsXCDown NOTIFICATION-TYPE 1992 OBJECTS { 1993 mplsXCOperStatus, -- start of range 1994 mplsXCOperStatus -- end of range 1995 } 1996 STATUS current 1997 DESCRIPTION 1998 " This notification is generated when the 1999 mplsXCOperStatus object for one or more contiguous 2000 entries in mplsXCTable are about to enter the 2001 down(2) state from some other. The included values 2002 of mplsXCOperStatus MUST both be set equal to this 2003 other state. The two instances of mplsXCOperStatus 2004 in this notification indicate the range of indexes 2005 that are affected. Note that all the indexes of the 2006 two ends of the range can be derived from the 2007 instance identifiers of these two objects. For 2008 cases where a contiguous range of cross-connects 2009 have transitioned into the down(2) state at roughly 2010 the same time, the device SHOULD issue a single 2011 notification for each range of contiguous indexes in 2012 an effort to minimize the emission of a large number 2013 of notifications. If a notification has to be 2014 issued for just a single cross-connect entry, then 2015 the instance identifier (and values) of the two 2016 mplsXCOperStatus objects MUST be the identical." 2017 ::= { mplsLsrNotifications 2 } 2019 -- End of notifications. 2021 -- Module compliance. 2023 mplsLsrGroups 2024 OBJECT IDENTIFIER ::= { mplsLsrConformance 1 } 2026 mplsLsrCompliances 2027 OBJECT IDENTIFIER ::= { mplsLsrConformance 2 } 2029 mplsLsrModuleCompliance MODULE-COMPLIANCE 2030 STATUS current 2031 DESCRIPTION 2032 "Compliance statement for agents that support the 2033 MPLS-LSR-MIB." 2034 MODULE -- this module 2036 -- The mandatory groups have to be implemented 2037 -- by all LSRs. However, they may all be supported 2038 -- as read-only objects in the case where manual 2039 -- configuration is unsupported. 2041 MANDATORY-GROUPS { 2042 mplsInterfaceGroup, 2043 mplsInSegmentGroup, 2044 mplsOutSegmentGroup, 2045 mplsXCGroup, 2046 mplsPerfGroup, 2047 mplsSegmentDiscontinuityGroup 2048 } 2050 GROUP mplsHCInSegmentPerfGroup 2051 DESCRIPTION 2052 "This group is mandatory for those in-segment 2053 entries for which the object 2054 mplsInSegmentOutOctets wraps around too 2055 quickly." 2057 GROUP mplsHCOutSegmentPerfGroup 2058 DESCRIPTION 2059 "This group is mandatory for those out-segment 2060 entries for which the object 2061 mplsOutSegmentOctets wraps around too quickly." 2063 GROUP mplsTrafficParamGroup 2064 DESCRIPTION 2065 "This group is mandatory for those LSRs that 2066 support QoS resource reservation." 2068 -- Depending on whether the device implements 2069 -- persistent cross-connects or not one of the 2070 -- following two groups is mandatory. 2072 GROUP mplsXCIsPersistentGroup 2073 DESCRIPTION 2074 "This group is mandatory for devices which 2075 support persistent cross-connects. The 2076 following constraints apply: mplsXCIsPersistent 2077 must at least be read-only returning true(2)." 2079 GROUP mplsXCIsNotPersistentGroup 2080 DESCRIPTION 2081 "This group is mandatory for devices which 2082 support non-persistent cross-connects. The 2083 following constraints apply: mplsXCIsPersistent 2084 must at least be read-only returning false(1)." 2086 -- mplsInSegmentTable 2088 OBJECT mplsInSegmentXCIndex 2089 DESCRIPTION 2090 "Write access is not required." 2092 OBJECT mplsInSegmentNPop 2093 MIN-ACCESS read-only 2094 DESCRIPTION 2095 "Write access is not required. This object 2096 should be set to 1 if it is read-only." 2098 OBJECT mplsInSegmentAddrFamily 2099 DESCRIPTION 2100 "Write access is not required. A value of 2101 other(0) should be supported because there may 2102 be cases where the agent may not know about or 2103 support any address types." 2105 OBJECT mplsInSegmentStorageType 2106 SYNTAX INTEGER { other(1) } 2107 DESCRIPTION 2108 "Only other(1) needs to be supported." 2110 -- mplsOutSegmentTable 2112 OBJECT mplsOutSegmentIfIndex 2113 MIN-ACCESS read-only 2114 DESCRIPTION 2115 "Write access is not required." 2117 OBJECT mplsOutSegmentPushTopLabel 2118 MIN-ACCESS read-only 2119 DESCRIPTION 2120 "Write access is not required." 2122 OBJECT mplsOutSegmentTopLabel 2123 MIN-ACCESS read-only 2124 DESCRIPTION 2125 "Write access is not required." 2127 OBJECT mplsOutSegmentNextHopIpAddrType 2128 SYNTAX InetAddressType { unknown(0), ipv4(1), ipv6(2) } 2129 MIN-ACCESS read-only 2130 DESCRIPTION 2131 "An implementation is only required to support 2132 ipv4(1) and ipv6(2)." 2134 OBJECT mplsOutSegmentNextHopIpAddr 2135 SYNTAX InetAddress (SIZE(0|4|16)) 2136 MIN-ACCESS read-only 2137 DESCRIPTION 2138 "An implementation is only required to support 2139 IPv4 and globally unique IPv6 addresses. Write 2140 access is not required." 2142 OBJECT mplsOutSegmentRowStatus 2143 SYNTAX INTEGER { 2144 active(1), 2145 notInService(2), 2146 createAndGo(4), 2147 destroy(6) 2148 } 2149 MIN-ACCESS read-only 2150 DESCRIPTION 2151 "The notReady(3) and createAndWait(5) states need 2152 not be supported." 2153 OBJECT mplsOutSegmentStorageType 2154 SYNTAX INTEGER { other(1) } 2155 DESCRIPTION 2156 "Only other(1) needs to be supported." 2158 -- mplsXCTable 2160 OBJECT mplsXCLabelStackIndex 2161 MIN-ACCESS read-only 2162 DESCRIPTION 2163 "Write access is not required." 2165 OBJECT mplsXCIsPersistent 2166 MIN-ACCESS read-only 2167 DESCRIPTION 2168 "Write access is not required." 2170 OBJECT mplsXCAdminStatus 2171 SYNTAX INTEGER { up(1), down(2) } 2172 MIN-ACCESS read-only 2173 DESCRIPTION 2174 "A value of testing(3) need not be supported." 2176 OBJECT mplsXCOperStatus 2177 SYNTAX INTEGER { up(1), down(2) } 2178 DESCRIPTION 2179 "Only up(1) and down(2) need to be supported." 2181 OBJECT mplsXCRowStatus 2182 SYNTAX INTEGER { 2183 active(1), 2184 notInService(2), 2185 createAndGo(4), 2186 destroy(6) 2187 } 2188 MIN-ACCESS read-only 2189 DESCRIPTION 2190 "The notReady(3) and createAndWait(5) states need 2191 not be supported." 2193 OBJECT mplsXCStorageType 2194 SYNTAX INTEGER { other(1) } 2195 DESCRIPTION 2196 "Only other(1) needs to be supported." 2198 ::= { mplsLsrCompliances 1 } 2200 -- Units of conformance. 2202 mplsInterfaceGroup OBJECT-GROUP 2203 OBJECTS { 2204 mplsInterfaceLabelMinIn, 2205 mplsInterfaceLabelMaxIn, 2206 mplsInterfaceLabelMinOut, 2207 mplsInterfaceLabelMaxOut, 2208 mplsInterfaceTotalBandwidth, 2209 mplsInterfaceAvailableBandwidth, 2210 mplsInterfaceLabelParticipationType 2211 } 2212 STATUS current 2213 DESCRIPTION 2214 "Collection of objects needed for MPLS interface 2215 configuration and performance information." 2216 ::= { mplsLsrGroups 1 } 2218 mplsInSegmentGroup OBJECT-GROUP 2219 OBJECTS { 2220 mplsInSegmentNPop, 2221 mplsInSegmentAddrFamily, 2222 mplsInSegmentXCIndex, 2223 mplsInSegmentOctets, 2224 mplsInSegmentDiscards, 2225 mplsInSegmentOwner, 2226 mplsInSegmentRowStatus, 2227 mplsInSegmentStorageType, 2228 mplsInSegmentTrafficParamPtr 2229 } 2230 STATUS current 2231 DESCRIPTION 2232 "Collection of objects needed to implement an in- 2233 segment." 2234 ::= { mplsLsrGroups 2 } 2236 mplsOutSegmentGroup OBJECT-GROUP 2237 OBJECTS { 2238 mplsOutSegmentIndexNext, 2239 mplsOutSegmentIfIndex, 2240 mplsOutSegmentPushTopLabel, 2241 mplsOutSegmentTopLabel, 2242 mplsOutSegmentNextHopIpAddrType, 2243 mplsOutSegmentNextHopIpAddr, 2244 mplsOutSegmentXCIndex, 2245 mplsOutSegmentOwner, 2246 mplsOutSegmentOctets, 2247 mplsOutSegmentDiscards, 2248 mplsOutSegmentErrors, 2249 mplsOutSegmentRowStatus, 2250 mplsOutSegmentStorageType, 2251 mplsOutSegmentTrafficParamPtr 2252 } 2253 STATUS current 2254 DESCRIPTION 2255 "Collection of objects needed to implement an out- 2256 segment." 2257 ::= { mplsLsrGroups 3 } 2259 mplsXCGroup OBJECT-GROUP 2260 OBJECTS { 2261 mplsXCIndexNext, 2262 mplsXCLabelStackIndex, 2263 mplsXCOwner, 2264 mplsXCAdminStatus, 2265 mplsXCOperStatus, 2266 mplsXCRowStatus, 2267 mplsXCNotificationsEnable, 2268 mplsXCStorageType 2269 } 2270 STATUS current 2271 DESCRIPTION 2272 "Collection of objects needed to implement a 2273 cross-connect entry." 2274 ::= { mplsLsrGroups 4 } 2276 mplsXCOptionalGroup OBJECT-GROUP 2277 OBJECTS { mplsXCLspId } 2278 STATUS current 2279 DESCRIPTION 2280 "Collection of optional objects for implementing 2281 a cross-connect entry." 2282 ::= { mplsLsrGroups 5 } 2284 mplsPerfGroup OBJECT-GROUP 2285 OBJECTS { 2286 mplsInSegmentOctets, 2287 mplsInSegmentPackets, 2288 mplsInSegmentErrors, 2289 mplsInSegmentDiscards, 2290 mplsOutSegmentOctets, 2291 mplsOutSegmentPackets, 2292 mplsOutSegmentDiscards, 2293 mplsInterfaceInLabelsUsed, 2294 mplsInterfaceLabelLookupFailures , 2295 mplsInterfaceOutFragments, 2296 mplsInterfaceOutLabelsUsed 2297 } 2299 STATUS current 2300 DESCRIPTION 2301 "Collection of objects providing performance 2302 information 2303 about an LSR." 2304 ::= { mplsLsrGroups 6 } 2306 mplsHCInSegmentPerfGroup OBJECT-GROUP 2307 OBJECTS { mplsInSegmentHCOctets } 2308 STATUS current 2309 DESCRIPTION 2310 "Object(s) providing performance information 2311 specific to out-segments for which the object 2312 mplsInterfaceInOctets wraps around too quickly." 2313 ::= { mplsLsrGroups 7 } 2315 mplsHCOutSegmentPerfGroup OBJECT-GROUP 2316 OBJECTS { mplsOutSegmentHCOctets } 2317 STATUS current 2318 DESCRIPTION 2319 "Object(s) providing performance information 2320 specific to out-segments for which the object 2321 mplsInterfaceOutOctets wraps around too 2322 quickly." 2323 ::= { mplsLsrGroups 8 } 2325 mplsTrafficParamGroup OBJECT-GROUP 2326 OBJECTS { 2327 mplsTrafficParamIndexNext, 2328 mplsTrafficParamMaxRate, 2329 mplsTrafficParamMeanRate, 2330 mplsTrafficParamMaxBurstSize, 2331 mplsTrafficParamRowStatus, 2332 mplsTrafficParamStorageType 2333 } 2334 STATUS current 2335 DESCRIPTION 2336 "Object(s) required for supporting QoS resource 2337 reservation." 2338 ::= { mplsLsrGroups 9 } 2340 mplsXCIsPersistentGroup OBJECT-GROUP 2341 OBJECTS { mplsXCIsPersistent } 2342 STATUS current 2343 DESCRIPTION 2344 "Objects needed to support persistent cross- 2345 connects." 2346 ::= { mplsLsrGroups 10 } 2348 mplsXCIsNotPersistentGroup OBJECT-GROUP 2349 OBJECTS { mplsXCIsPersistent } 2350 STATUS current 2351 DESCRIPTION 2352 "Objects needed to support non-persistent cross- 2353 connects." 2354 ::= { mplsLsrGroups 11 } 2356 mplsLabelStackGroup OBJECT-GROUP 2357 OBJECTS { 2358 mplsLabelStackLabel, 2359 mplsLabelStackRowStatus, 2360 mplsLabelStackStorageType, 2361 mplsMaxLabelStackDepth, 2362 mplsLabelStackIndexNext 2363 } 2364 STATUS current 2365 DESCRIPTION 2366 "Objects needed to support label stacking which 2367 is an optional feature for an LSR." 2368 ::= { mplsLsrGroups 12 } 2370 mplsSegmentDiscontinuityGroup OBJECT-GROUP 2371 OBJECTS { 2372 mplsInSegmentPerfDiscontinuityTime, 2373 mplsOutSegmentPerfDiscontinuityTime 2374 } 2375 STATUS current 2376 DESCRIPTION 2377 " A collection of objects providing information 2378 specific to segment discontinuities.." 2379 ::= { mplsLsrGroups 13 } 2381 mplsLsrNotificationGroup NOTIFICATION-GROUP 2382 NOTIFICATIONS { 2383 mplsXCUp, 2384 mplsXCDown 2385 } 2386 STATUS current 2387 DESCRIPTION 2388 "Set of notifications implemented in this module. 2389 None is mandatory." 2390 ::= { mplsLsrGroups 14 } 2392 END 2394 12. Security Considerations 2396 It is clear that this MIB is potentially useful for monitoring of 2397 MPLS LSRs. This MIB can also be used for configuration of certain 2398 objects, and anything that can be configured can be incorrectly 2399 configured, with potentially disastrous results. 2401 At this writing, no security holes have been identified beyond 2402 those that SNMP Security [RFC2571] is itself intended to address. 2403 These relate to primarily controlled access to sensitive 2404 information and the ability to configure a device - or which might 2405 result from operator error, which is beyond the scope of any 2406 security architecture. 2408 There are a number of management objects defined in this MIB which 2409 have a MAX-ACCESS clause of read-write and/or read-create. Such 2410 objects may be considered sensitive or vulnerable in some network 2411 environments. The support for SET operations in a non-secure 2412 environment without proper protection can have a negative effect 2413 on network operations. The use of SNMP Version 3 is recommended 2414 over prior versions, for configuration control, as its security 2415 model is improved. 2417 SNMPv1 or SNMPv2 are by themselves not a secure environment. Even 2418 if the network itself is secure (for example by using IPSec 2419 [RFC2401]), there is no control as to who on the secure network is 2420 allowed to access and GET/SET (read/change/create/delete) the 2421 objects in this MIB. It is recommended that the implementers 2422 consider the security features as provided by the SNMPv3 2423 framework. Specifically, the use of the User-based Security Model 2424 [RFC2574] and the View-based Access Control [RFC2575] is 2425 recommended. It is then a customer/user responsibility to ensure 2426 that the SNMP entity giving access to an instance of this MIB is 2427 properly configured to give access to the objects only to those 2428 principals (users) that have legitimate rights to indeed GET or 2429 SET (change/create/delete) them. 2431 There are a number of managed objects in this MIB that may contain 2432 information that may be sensitive from a business perspective, in 2433 that they represent a customer's interface to the MPLS network. 2434 Allowing uncontrolled access to these objects could result in 2435 malicious and unwanted disruptions of network traffic or incorrect 2436 configurations for these customers. There are no objects that are 2437 particularly sensitive in their own right, such as passwords or 2438 monetary amounts. 2440 13. Acknowledgments 2442 We wish to thank Ron Bonica, Adrian Farrel, Eric Gray, Tim 2443 Mancour, Keith McCloghrie, Bala Rajagopalan, Dan Tappan, Vasanthi 2444 Thirumalai, Joseph Benoit and Joan Cucchiara. 2446 14. References 2448 [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", 2449 RFC 1700, October 1994. See also: 2450 http://www.isi.edu/in-notes/iana/assignments/smi- 2451 numbers 2453 [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS 2454 FAMILY NUMBERS, (http://www.isi.edu/in- 2455 notes/iana/assignements/address-family-numbers), 2456 for MIB see: 2457 ftp://ftp.isi.edu/mib/iana.mib/ianaaddressfamilynum 2458 bers.mib 2460 [TCMIB] Nadeau, T., Cucchiara, J., Srinivasan, C, 2461 Viswanathan, A. and H. Sjostrand, "Definition of 2462 Textual Conventions and OBJECT-IDENTITIES for Multi- 2463 Protocol Label Switching (MPLS) Management", 2464 Internet Draft , 2465 January 2002. 2467 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 2468 Identification of Management Information for TCP/IP- 2469 based Internets", RFC 1155, May 1990. 2471 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 2472 "Simple Network Management Protocol", RFC 1157, May 2473 1990. 2475 [RFC1215] M. Rose, "A Convention for Defining Traps for use 2476 with the SNMP", RFC 1215, March 1991. 2478 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. 2479 Waldbusser, "Introduction to Community-based 2480 SNMPv2", RFC 1901, January 1996. 2482 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. 2483 Waldbusser, "Protocol Operations for Version 2 of 2484 the Simple Network Management Protocol (SNMPv2)", 2485 RFC 1905, January 1996. 2487 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. 2488 Waldbusser, "Transport Mappings for Version 2 of 2489 the Simple Network Management Protocol (SNMPv2)", 2490 RFC 1906, January 1996. 2492 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2493 Requirement Levels", BCP 14, RFC 2119, March 1997. 2495 [RFC2863] McCloghrie, K., and F. Kastenholtz, "The Interfaces 2496 Group MIB using SMIv2", RFC 2863, June 2000 2498 [RFC2401] Kent, S., and Atkinson, R., "Security Architecture 2499 for the Internet Protocol", RFC 2401, November 2500 1998. 2502 [RFC2515] Tesink, K., "Definitions of Managed Objects for ATM 2503 Management", RFC 2515, Feb. 1999 2505 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 2506 "Introduction to Version 3 of the Internet-standard 2507 Network Management Framework", RFC 2570, April 2508 1999. 2510 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 2511 Architecture for Describing SNMP Management 2512 Frameworks", RFC 2571, April 1999. 2514 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2515 "Message Processing and Dispatching for the Simple 2516 Network Management Protocol (SNMP)", RFC 2572, 2517 April 1999. 2519 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2520 Applications", RFC 2573, April 1999. 2522 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 2523 Model (USM) for version 3 of the Simple Network 2524 Management Protocol (SNMPv3)", RFC 2574, April 2525 1999. 2527 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- 2528 based Access Control Model (VACM) for the Simple 2529 Network Management Protocol (SNMP)", RFC 2575, 2530 April 1999. 2532 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., 2533 Case, J., Rose, M., and S. Waldbusser, "Structure 2534 of Management Information Version 2 (SMIv2)", STD 2535 58, RFC 2578, April 1999. 2537 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., 2538 Case, J., Rose, M., and S. Waldbusser, "Textual 2539 Conventions for SMIv2", STD 58, RFC 2579, April 2540 1999. 2542 [RFC2702] Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., 2543 and J. McManus, "Requirements for Traffic 2544 Engineering Over MPLS", RFC 2702, September 1999. 2546 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., 2547 Case, J., Rose, M., and S. Waldbusser, "Conformance 2548 Statements for SMIv2", STD 58, RFC 2580, April 2549 1999. 2551 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 2552 "Multiprotocol Label Switching Architecture", RFC 2553 3031, January 2001. 2555 [RFC3032] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D., 2556 Federokow, G., Li, T., and A. Conta, "MPLS Label 2557 Stack Encoding", RFC 3032, January 2001. 2559 15. Authors' Addresses 2561 Cheenu Srinivasan 2562 Parama Networks, Inc. 2563 1030 Broad Street 2564 Shrewsbury, NJ 07702 2565 Phone: +1-732-544-9120 x731 2566 Email: cheenu@paramanet.com 2567 Arun Viswanathan 2568 Force10 Networks, Inc. 2569 1440 McCarthy Blvd 2570 Milpitas, CA 95035 2571 Phone: +1-408-571-3516 2572 Email: arun@force10networks.com 2574 Thomas D. Nadeau 2575 Cisco Systems, Inc. 2576 250 Apollo Drive 2577 Chelmsford, MA 01824 2578 Phone: +1-978-244-3051 2579 Email: tnadeau@cisco.com 2581 16. Full Copyright Statement 2583 Copyright (C) The Internet Society (2001). All Rights Reserved. 2585 This document and translations of it may be copied and furnished 2586 to others, and derivative works that comment on or otherwise 2587 explain it or assist in its implementation may be prepared, 2588 copied, published and distributed, in whole or in part, without 2589 restriction of any kind, provided that the above copyright notice 2590 and this paragraph are included on all such copies and derivative 2591 works. However, this document itself may not be modified in any 2592 way, such as by removing the copyright notice or references to the 2593 Internet Society or other Internet organizations, except as needed 2594 for the purpose of developing Internet standards in which case 2595 the procedures for copyrights defined in the Internet Standards 2596 process must be followed, or as required to translate it into 2597 languages other than English. 2599 The limited permissions granted above are perpetual and will not 2600 be revoked by the Internet Society or its successors or assigns. 2601 This document and the information contained herein is provided on 2602 an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 2603 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 2604 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 2605 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2606 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.