idnits 2.17.1 draft-ietf-mpls-lsr-mib-04.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == There is 1 instance of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 57 longer pages, the longest (page 14) being 64 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 58 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([MPLSArch,MPLSFW]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 2838 has weird spacing: '...for the purpo...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'SNMPv1MIBDef' is mentioned on line 116, but not defined == Unused Reference: 'Assigned' is defined on line 2683, but no explicit reference was found in the text == Unused Reference: 'RFC2572' is defined on line 2708, but no explicit reference was found in the text == Unused Reference: 'RFC2574' is defined on line 2713, but no explicit reference was found in the text == Unused Reference: 'RFC1905' is defined on line 2718, but no explicit reference was found in the text == Unused Reference: 'RFC2573' is defined on line 2723, but no explicit reference was found in the text == Unused Reference: 'RFC2575' is defined on line 2726, but no explicit reference was found in the text == Unused Reference: 'RFC2570' is defined on line 2731, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'MPLSArch' -- Possible downref: Non-RFC (?) normative reference: ref. 'MPLSFW' -- Possible downref: Non-RFC (?) normative reference: ref. 'LblStk' ** Obsolete normative reference: RFC 1700 (ref. 'Assigned') (Obsoleted by RFC 3232) -- Possible downref: Non-RFC (?) normative reference: ref. 'IANAFamily' ** Obsolete normative reference: RFC 2271 (ref. 'SNMPArch') (Obsoleted by RFC 2571) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. 'SNMPv1Traps') ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 1902 (ref. 'SMIv2') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. 'SNMPv2TC') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. 'SNMPv2Conf') (Obsoleted by RFC 2580) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. 'SNMPv1') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. 'SNMPv2c') ** Obsolete normative reference: RFC 1906 (ref. 'SNMPv2TM') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2272 (ref. 'SNMPv3MP') (Obsoleted by RFC 2572) -- Duplicate reference: RFC2574, mentioned in 'SNMPv3USM', was also mentioned in 'RFC2574'. ** Obsolete normative reference: RFC 2574 (ref. 'SNMPv3USM') (Obsoleted by RFC 3414) -- Duplicate reference: RFC1905, mentioned in 'SNMPv2PO', was also mentioned in 'RFC1905'. ** Obsolete normative reference: RFC 1905 (ref. 'SNMPv2PO') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2273 (ref. 'SNMPv3App') (Obsoleted by RFC 2573) -- Duplicate reference: RFC2575, mentioned in 'SNMPv3VACM', was also mentioned in 'RFC2575'. ** Obsolete normative reference: RFC 2575 (ref. 'SNMPv3VACM') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2401 (ref. 'IPSEC') (Obsoleted by RFC 4301) ** Obsolete normative reference: RFC 2233 (ref. 'IFMIB') (Obsoleted by RFC 2863) Summary: 27 errors (**), 0 flaws (~~), 13 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Cheenu Srinivasan 2 Internet Draft Tachion Networks, Inc. 3 Expires: October 2000 4 Arun Viswanathan 5 Force10 Networks, Inc. 7 Thomas D. Nadeau 8 Cisco Systems, Inc. 10 MPLS Label Switch Router Management Information Base Using SMIv2 12 draft-ietf-mpls-lsr-mib-04.txt 14 Status of this Memo 16 This document is an Internet-Draft and is in full conformance with 17 all provisions of Section 10 of RFC 2026. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as Internet- 22 Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six 25 months and may be updated, replaced, or obsoleted by other 26 documents at any time. It is inappropriate to use Internet- 27 Drafts as reference material or to cite them other than as "work 28 in progress." 30 The list of current Internet-Drafts can be accessed at 31 http://www.ietf.org/ietf/1id-abstracts.txt. 33 The list of Internet-Draft Shadow Directories can be accessed at 34 http://www.ietf.org/shadow.html. 36 Table of Contents 38 1.Abstract..............................................2 39 2. Introduction.........................................2 40 3. Terminology..........................................2 41 4. The SNMP Management Framework........................3 42 4.1. Object Definitions.................................4 43 5. Feature Checklist....................................4 44 6. Outline..............................................5 45 6.1. Summary of LSR MIB.................................5 46 7. Brief Description of MIB Objects.....................5 47 7.1. mplsInterfaceConfTable.............................6 48 7.2. mplsInterfacePerfTable.............................6 49 7.3. mplsInSegmentTable.................................6 50 7.4. mplsInSegmentPerfTable.............................7 51 7.5. mplsOutSegmentTable................................7 52 7.6. mplsOutSegmentPerfTable............................7 53 7.7. mplsXCTable........................................8 54 7.8. mplsLabelStackTable................................8 55 7.9. mplsTrafficParamTable..............................8 56 8. Example of LSP Setup.................................8 57 9. Application of the Interface Group to MPLS..........10 58 9.1. Support of the MPLS Layer by ifTable..............10 59 10. The Use of RowPointer..............................12 60 11. MPLS Label Switch Router MIB Definitions...........12 61 12. Security Considerations............................53 62 13. Acknowledgments....................................54 63 14. References.........................................55 64 15. Authors' Addresses.................................57 65 16. Full Copyright Statement...........................58 67 1. Abstract 69 This memo defines an experimental portion of the Management 70 Information Base (MIB) for use with network management protocols 71 in the Internet community. In particular, it describes managed 72 objects for modeling a Multi-Protocol Label Switching (MPLS) 73 [MPLSArch, MPLSFW] Label Switch Router (LSR). 75 2. Introduction 77 This memo defines an experimental portion of the Management 78 Information Base (MIB) for use with network management protocols 79 in the Internet community. In particular, it describes managed 80 objects for modeling a Multi-Protocol Label Switching (MPLS) 81 [MPLSArch, MPLSFW] Label Switch Router (LSR). 83 Comments should be made directly to the MPLS mailing list at 84 mpls@uu.net. 86 This memo does not, in its draft form, specify a standard for the 87 Internet community. 89 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 90 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 91 "OPTIONAL" in this document are to be interpreted as described in 92 RFC 2119, reference [BCP14]. 94 3. Terminology 96 This document uses terminology from the document describing the 97 MPLS architecture [MPLSArch]. A label switched path (LSP) is 98 modeled as a connection consisting of one or more incoming 99 segments (in-segments) and/or one or more outgoing segments (out- 100 segments) at a label switch router (LSR). The association or 101 interconnection of the in-segments and out-segments is 102 accomplished by using a cross-connect. We use the terminology 103 "connection" and "LSP" interchangeably where the meaning is clear 104 from the context. 106 4. The SNMP Management Framework 108 The SNMP Management Framework presently consists of five major 109 components: 111 - An overall architecture, described in RFC 2271 [SNMPArch]. 113 - Mechanisms for describing and naming objects and events for the 114 purpose of management. The first version of this Structure of 115 Management Information (SMI) is called SMIv1 and described in 116 RFC 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215 117 [SNMPv1Traps]. The second version, called SMIv2, is described 118 in RFC 1902 [SMIv2], RFC 1903 [SNMPv2TC] and RFC 1904 119 [SNMPv2Conf]. 121 - Message protocols for transferring management information. The 122 first version of the SNMP message protocol is called SNMPv1 123 and described in RFC 1157 [SNMPv1]. A second version of the 124 SNMP message protocol, which is not an Internet standards 125 track protocol, is called SNMPv2c and described in RFC 1901 126 [SNMPv2c] and RFC 1906 [SNMPv2TM]. The third version of the 127 message protocol is called SNMPv3 and described in RFC 1906 128 [SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC 2574 [SNMPv3USM]. 130 - Protocol operations for accessing management information. The 131 first set of protocol operations and associated PDU formats is 132 described in RFC 1157 [SNMPv1]. A second set of protocol 133 operations and associated PDU formats is described in RFC 1905 134 [SNMPv2PO]. 136 - A set of fundamental applications described in RFC 2273 137 [SNMPv3App] and the view-based access control mechanism 138 described in RFC 2575 [SNMPv3VACM]. 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. This memo 143 specifies a MIB module that is compliant to the SMIv2. A MIB 144 conforming to the SMIv1 can be produced through the appropriate 145 translations. The resulting translated MIB must be semantically 146 equivalent, except where objects or events are omitted because no 147 translation is possible (use of Counter64). Some machine-readable 148 information in SMIv2 will be converted into textual descriptions 149 in SMIv1 during the translation process. However, this loss of 150 machine-readable information is not considered to change the 151 semantics of the MIB. 153 4.1. Object Definitions 155 Managed objects are accessed via a virtual information store, 156 termed the Management Information Base or MIB. Objects in the MIB 157 are defined using the subset of Abstract Syntax Notation One 158 (ASN.1) defined in the SMI. In particular, each object type is 159 named by an OBJECT IDENTIFIER, an administratively assigned name. 160 The object type together with an object instance serves to 161 uniquely identify a specific instantiation of the object. For 162 human convenience, we often use a textual string, termed the 163 descriptor, to also refer to the object type. 165 5. Feature Checklist 167 The MPLS label switch router MIB (LSR-MIB) is designed to satisfy 168 the following requirements and constraints: 170 - The MIB supports both manually configured LSPs as well as those 171 configured via any MPLS signaling protocol. 173 - The MIB supports the enabling and disabling of MPLS capability 174 on MPLS capable interfaces of an LSR. 176 - The MIB allows resource sharing between two or more LSPs. 178 - Both per-platform and per-interface label spaces are supported. 180 - MPLS packets can be forwarded solely based on an incoming top 181 label [MPLSArch, LblStk]. 183 - Support is provided for next-hop resolution when the outgoing 184 interface is a shared media interface. In the point-to- 185 multipoint case, each outgoing segment can reside on a 186 different shared media interface. 188 - The MIB supports point-to-point, point-to-multipoint and 189 multipoint-to-point connections at an LSR. 191 - For multipoint-to-point connections all outgoing packets can 192 have the same top label. 194 - For multipoint-to-point connections, the outgoing resources of 195 the merged connections can be shared. 197 - For multipoint-to-point connections, packets from different 198 incoming connections can have distinct outgoing label stacks 199 beneath the (identical) top label. 201 - In the point-to-multipoint case each outgoing connection can 202 have a distinct label stack including the top label. 204 - All the members of a point-to-multipoint connection can share 205 the resources allocated for the ingress segments. 207 - The MIB provides cross-connect capability to "pop" an incoming 208 label and forward the packet with the remainder of the label 209 stack unchanged and without pushing any labels ("pop-and-go") 210 [LblStk]. 212 - The MIB supports persistent as well as non-persistent LSPs. 214 - Performance counters are provided for in-segments and out- 215 segments as well as for measuring MPLS performance on a per- 216 interface basis. 218 6. Outline 220 Configuring LSPs through an LSR involves the following steps: 222 - Enabling MPLS on MPLS capable interfaces. 224 - Configuring in-segments and out-segments. 226 - Setting up the cross-connect table to associate segments and/or 227 to indicate connection origination and termination. 229 - Optionally specifying label stack actions. 231 - Optionally specifying segment traffic parameters. 233 6.1. Summary of LSR MIB 235 The MIB objects for performing these actions consist of the 236 following tables: 238 - The interface configuration table (mplsInterfaceConfTable), 239 which is used for enabling the MPLS protocol on MPLS-capable 240 interfaces. 242 - The in-segment (mplsInSegmentTable) and out-segment 243 (mplsOutSegmentTable) tables, which are used for configuring 244 LSP segments at an LSR. 246 - The cross-connect table (mplsXCTable), which is used to 247 associate in and out segments together, in order to form a 248 cross-connect. 250 - The label stack table (mplsLabelStackTable), which is used for 251 specifying label stack operations. 253 - The Traffic Parameter table (mplsTrafficParamTable), which is 254 used for specifying LSP-related traffic parameters. 256 Further, the MPLS in-segment and out-segment performance tables, 257 mplsInSegmentPerfTable and mplsOutSegmentPerfTable, contain the 258 objects necessary to measure the performance of LSPs, and 259 mplsInterfacePerfTable has objects to measure MPLS performance on 260 a per-interface basis. 262 These tables are described in the subsequent sections. 264 7. Brief Description of MIB Objects 266 Sections 7.1-7.2 describe objects pertaining to MPLS capable 267 interfaces of an LSR. The objects described in Sections 7.3-7.8, 268 when considered together, are equivalent to the tables described 269 in the MPLS architecture document [MPLSArch], that is, the 270 Incoming Label Map (ILM) and the Next Hop Label Forwarding Entry 271 (NHLFE) tables. Section 7.9 describes objects for specifying 272 traffic parameters for in and out segments. It is appropriate to 273 note that the in-segment, out-segment, and cross-connect tables 274 were modeled after similar tables found in [ATOMMIB]. 276 7.1. mplsInterfaceConfTable 278 This table represents the interfaces that are MPLS capable. An 279 LSR creates an entry in this table for every MPLS capable 280 interface on that LSR. 282 7.2. mplsInterfacePerfTable 284 This table contains objects to measure the MPLS performance of 285 MPLS capable interfaces and is an AUGMENT to 286 mplsInterfaceConfTable. High capacity counters are provided for 287 objects that are likely to wrap around quickly on high-speed 288 interfaces. 290 7.3. mplsInSegmentTable 291 This table contains a description of the incoming MPLS segments to 292 an LSR and their associated parameters. 294 The administrative and operational status objects for this table 295 are used to control packet transmission on this segment. If 296 either the administrative and operational status objects for this 297 table are set to 'down', this implies that packets will not be 298 forwarded. Likewise, if the values are set to 'up' this implies 299 that packets are forwarded. These values are particularly useful 300 in cases where multi-point connections utilize a single cross- 301 connect and the administrator wishes to disable some, but not all 302 of the streams. In these cases, the administrator may set the 303 administrative status object to 'down' on some of the in-segments. 305 7.4. mplsInSegmentPerfTable 307 The MPLS In-Segment Performance Table has objects to measure the 308 performance of an incoming segment configured on an LSR. It is an 309 AUGMENT to mplsInSegmentTable. High capacity counters are 310 provided for objects that are likely to wrap around quickly on 311 high-speed interfaces. 313 7.5. mplsOutSegmentTable 315 The Out-Segment Table contains a description of the outgoing MPLS 316 segments at an LSR and their associated parameters. 318 The administrative and operational status objects for this table 319 are used to control packet transmission on this segment. If 320 either the administrative and operational status objects are set 321 to 'down', this implies that packets will not be forwarded. 322 Likewise, if the values are set to 'up' this implies that packets 323 are forwarded. These values are particularly useful in cases 324 where multicast connections utilize a single cross-connect and the 325 administrator wishes to disable some, but not all of the streams. 326 In these cases, the administrator may set the administrative 327 status object to 'down' on some of the out-segments. 329 7.6. mplsOutSegmentPerfTable 331 The MPLS Out-Segment Table contains objects to measure the 332 performance of an outgoing segment configured on an LSR. It is an 333 AUGMENT to mplsOutSegmentTable. High capacity counters are 334 provided for objects that are likely to wrap around quickly on 335 high-speed interfaces. 337 7.7. mplsXCTable 339 The mplsXCTable specifies information for associating segments 340 together in order to instruct the LSR to switch between the 341 specified segments. It supports point-to-point, point-to-multi- 342 point and multi-point-to-point connections. 344 The administrative and operational status objects for this table 345 imply control of packet forwarding to and from a XCEntry. When 346 the administrative and operational status objects are set to 347 'down' for example, this implies that the specified XCEntry will 348 not forward packets. Likewise, when either is set to 'up' this 349 implies that packets will be forwarded. 351 7.8. mplsLabelStackTable 353 The mplsLabelStackTable specifies the label stack to be pushed 354 onto a packet, beneath the top label. Entries to this table are 355 referred to from mplsXCTable. 357 7.9. mplsTrafficParamTable 359 The mplsTrafficParamTable contains objects for specifying the 360 traffic parameters of in-segments and out-segments. Entries in 361 this table are referred to from mplsInSegmentTable and 362 mplsOutSegmentTable. 364 8. Example of LSP Setup 366 In this section we provide a brief example of using the MIB 367 objects described in section 11. to set up an LSP. While this 368 example is not meant to illustrate every nuance of the MIB, it is 369 intended as an aid to understanding some of the key concepts. It 370 is meant to be read after going through the MIB itself. 372 Suppose that one would like to manually create a best-effort, 373 unidirectional LSP. Assume that the LSP enters the LSR via MPLS 374 interface A with ifIndex 12 and exits the LSR via MPLS interface B 375 with ifIndex 13. Let us assume that we do not wish to have a 376 label stack beneath the top label on the outgoing labeled packets. 377 The following example illustrates which rows and corresponding 378 objects might be created to accomplish this. 380 First, the traffic parameter entries must be set-up for both 381 segments. 383 In mplsTrafficParamTable for the incoming direction: 385 { 386 mplsTrafficParamIndex = 5 387 mplsTrafficParamMaxRate = 100000, 388 mplsTrafficParamMeanRate = 100000, 389 mplsTrafficParamMaxBurstSize = 2000, 390 mplsTrafficParamRowStatus = createAndGo(4) 391 } 393 In mplsTrafficParamTable for the outgoing direction: 394 { 395 mplsTrafficParamIndex = 6 396 mplsTrafficParamMaxRate = 100000, 397 mplsTrafficParamMeanRate = 100000, 398 mplsTrafficParamMaxBurstSize = 2000, 399 mplsTrafficParamRowStatus = createAndGo(4) 400 } 402 Note that if we were setting up a bi-directional LSP, the segments 403 in the reverse direction can share the traffic parameter entries 404 (and hence resources) with the segments in the forward direction. 406 We must next create the appropriate in-segment and out-segment 407 entries with suitable traffic parameters by pointing to the 408 appropriate traffic parameter entries that we have just created. 410 In mplsInSegmentTable: 411 { 412 mplsInSegmentIfIndex = 12, -- incoming interface 413 mplsInSegmentLabel = 21, -- incoming label 414 mplsInSegmentNPop = 1, 415 mplsInSegmentTrafficParamPtr = mplsTrafficParamIndex.5, 416 mplsInSegmentRowStatus = createAndGo(4) 417 } 419 In mplsOutSegmentTable: 420 { 421 mplsOutSegmentIndex = 1, 422 mplsOutSegmentIfIndex = 13, -- outgoing interface 423 mplsOutSegmentPushTopLabel = true(1), 424 mplsOutSegmentTopLabel = 22, -- outgoing label 425 mplsOutSegmentTrafficParamPtr = mplsTrafficParamIndex.6, 426 mplsOutSegmentRowStatus = createAndGo(4) 427 } 429 Next, a cross-connect entry is created thereby associating the 430 newly created segments together. 432 In mplsXCTable: 433 { 434 mplsXCIndex = 2, 435 mplsXCLspId = 'c021041502'H, -- 192.33.4.21.2 436 mplsInSegmentIfIndex = 12, 437 mplsInSegmentLabel = 21, 438 mplsOutSegmentIndex = 1, 439 mplsXCIsPersistent = false (1), 440 mplsLabelStackIndex = 0, -- only a single 441 -- outgoing label 442 mplsXCRowStatus = createAndGo(4) 443 } 445 Note that the mplsInSegmentXCIndex and mplsOutSegmentXCIndex 446 objects will automatically be populated with the value 2 when 447 these segments are referred to from the corresponding cross- 448 connect entry. 450 9. Application of the Interface Group to MPLS 452 The Interfaces Group of MIB II defines generic managed objects for 453 managing interfaces. This memo contains the media-specific 454 extensions to the Interfaces Group for managing MPLS interfaces. 456 This memo assumes the interpretation of the Interfaces Group to be 457 in accordance with [IFMIB] which states that the interfaces table 458 (ifTable) contains information on the managed resource's 459 interfaces and that each sub-layer below the internetwork layer of 460 a network interface is considered an interface. Thus, the MPLS 461 interface is represented as an entry in the ifTable. The inter- 462 relation of entries in the ifTable is defined by Interfaces Stack 463 Group defined in [IFMIB]. 465 When using MPLS interfaces, the interface stack table might appear 466 as follows: 468 +----------------------------------------+ 469 | MPLS-interface ifType = mpls(166) + 470 +----------------------------------------+ 471 | Underlying Layer... + 472 +----------------------------------------+ 474 In the above diagram, "Underlying Layer..." refers to the ifIndex 475 of any interface type, which has been defined for MPLS 476 interworking. Examples include ATM, Frame Relay, Ethernet, etc. 478 9.1. Support of the MPLS Layer by ifTable 480 Some specific interpretations of ifTable for the MPLS layer 481 follow. 483 Object Use for the MPLS layer 485 ifIndex Each MPLS interface is represented by an ifEntry. 487 ifDescr Description of the MPLS interface. 489 ifType The value that is allocated for MPLS is 166. 491 ifSpeed The total bandwidth in bits per second for use by 492 the MPLS layer. 494 ifPhysAddress Unused. 496 ifAdminStatus This variable indicates the administrator's intent 497 as to whether MPLS should be enabled, disabled, or 498 running in some diagnostic testing mode on this 499 interface. Also see [IFMIB]. 501 ifOperStatus This value reflects the actual or operational 502 status of MPLS on this interface. 504 ifLastChange See [IFMIB]. 506 ifInOctets The number of received octets over the interface, 507 i.e., the number of received, octets received as 508 labeled packets. 510 ifOutOctets The number of transmitted octets over the 511 interface, i.e., the number of octets transmitted 512 as labeled packets. 514 ifInErrors The number of labeled packets dropped due to 515 uncorrectable errors. 517 ifInUnknownProtos 518 The number of received packets discarded during 519 packet header validation, including packets with 520 unrecognized label values. 522 ifOutErrors See [IFMIB]. 524 ifName Textual name (unique on this system) of the 525 interface or an octet string of zero length. 527 ifLinkUpDownTrapEnable 528 Default is disabled (2). 530 ifConnectorPresent 531 Set to false (2). 533 ifHighSpeed See [IFMIB]. 535 ifHCInOctets The 64-bit version of ifInOctets; supported if 536 required by the compliance statements in [IFMIB]. 538 ifHCOutOctets The 64-bit version of ifOutOctets; supported if 539 required by the compliance statements in [IFMIB]. 541 ifAlias The non-volatile 'alias' name for the interface as 542 specified by a network manager. 544 ifCounterDiscontinuityTime 545 See [IFMIB]. 547 10. The Use of RowPointer 549 RowPointer is a textual convention used to identify a conceptual 550 row in an SNMP Table by pointing to one of its objects. In this 551 MIB, it is used in mplsInSegmentTable and mplsOutSegmentTable 552 for the following purposes. First, it indicates a particular 553 traffic parameter table. An example of such a table is 554 mplsTrafficParamTable. Second, it is used to indicate a specific 555 instance of a traffic parameter entry that is associated with a 556 given in-segment or out-segment entry. In the in-segment and out- 557 segment tables, the trafficParamPtr SHOULD point to the first 558 column of the appropriate conceptual row. 560 11. MPLS Label Switch Router MIB Definitions 562 MPLS-LSR-MIB DEFINITIONS ::= BEGIN 564 IMPORTS 565 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 566 experimental, Integer32, Counter32, Unsigned32, 567 Counter64, Gauge32, BITS 568 FROM SNMPv2-SMI 570 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 571 FROM SNMPv2-CONF 573 TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType, 574 RowPointer, TimeStamp 575 FROM SNMPv2-TC 577 InterfaceIndex, InterfaceIndexOrZero 578 FROM IF-MIB 580 AddressFamilyNumbers 581 FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB 583 InetAddressIPv4, InetAddressIPv6, InetAddressType 584 FROM INET-ADDRESS-MIB; 586 mplsLsrMIB MODULE-IDENTITY 587 LAST-UPDATED "200004261200Z" -- 26 April 2000 12:00:00 EST 588 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 589 CONTACT-INFO 590 " Cheenu Srinivasan 591 Postal: Tachion Networks, Inc. 592 Monmouth Park Corporate Center I 593 Building C, 185 Monmouth Parkway 594 West Long Branch, NJ 07764 595 Tel: +1-732-542-7750 x1234 596 Email: cheenu@tachion.com 598 Arun Viswanathan 599 Postal: Force10 Networks, Inc. 600 1440 McCarthy Blvd 601 Milpitas, CA 95035 602 Tel: +1-408-571-3516 603 Email: arun@force10networks.com 605 Thomas D. Nadeau 606 Postal: Cisco Systems, Inc. 607 250 Apollo Drive 608 Chelmsford, MA 01824 609 Tel: +1-978-244-3051 610 Email: tnadeau@cisco.com" 612 DESCRIPTION 613 "This MIB contains managed object definitions for the 614 Multiprotocol Label Switching (MPLS) Router as 615 defined in: Rosen, E., Viswanathan, A., and R. 616 Callon, Multiprotocol Label Switching Architecture, 617 Internet Draft , 618 February 2000." 620 -- Revision history. 621 REVISION 622 "199906161200Z" -- 16 June 1999 12:00:00 EST 623 DESCRIPTION 624 "Initial draft version." 625 REVISION 626 "200002161200Z" -- 16 February 2000 12:00:00 EST 627 DESCRIPTION 628 "Second draft version." 629 REVISION 630 "200003061200Z" -- 6 March 2000 12:00:00 EST 631 DESCRIPTION 632 "Third draft version." 633 REVISION 634 "200004211200Z" -- 21 April 2000 12:00:00 EST 635 DESCRIPTION 636 "Fourth draft version. Made corrections from WG Last 637 Call comments." 638 REVISION 639 "200004261200Z" -- 26 April 2000 12:00:00 EST 640 DESCRIPTION 641 "Fifth draft version. Made minor typographical corrections 642 noted from WG mailing list." 643 ::= { experimental 96 } 645 -- Textual Conventions. 647 MplsLSPID ::= TEXTUAL-CONVENTION 648 STATUS current 649 DESCRIPTION 650 "An identifier that is assigned to each LSP and is 651 used to uniquely identify it. This is assigned at 652 the head end of the LSP and can be used by all LSRs 653 to identify this LSP. This value is piggybacked by 654 the signaling protocol when this LSP is signaled 655 within the network. This identifier can then be 656 used at each LSR to identify which labels are being 657 swapped to other labels for this LSP. For IPv4 658 addresses this results in a 6-octet long cookie." 659 SYNTAX OCTET STRING (SIZE (0..31)) 661 -- An MPLS label. 662 MplsLabel ::= TEXTUAL-CONVENTION 663 STATUS current 664 DESCRIPTION 665 "This value represents an MPLS label. Note that the 666 contents of a label field are interpreted in an 667 interface-type specific fashion. For example, the 668 20-bit wide label carried in the MPLS shim header is 669 contained in bits 0-19 and bits 20-31 must be zero. 670 The frame relay label can be either 10 or 23 bits 671 wide depending on the size of the DLCI field and 672 bits 10-31, or 23-31 must be zero, respectively. 673 For an ATM interface, bits 0-15 must be interpreted 674 as the VCI, bits 16-23 as the VPI and bits 24-31 675 must be zero. Note that the permissible label 676 values are also a function of the interface type. 677 For example, the value 3 has special semantics in 678 the control plane for an MPLS shim header label and 679 is not a valid label value in the data path." 680 REFERENCE 681 "1. MPLS Label Stack Encoding, Rosen et al, draft- 682 ietf-mpls-label-encaps-07.txt, March 2000. 683 2. Use of Label Switching on Frame Relay Networks, 684 Conta et al, draft-ietf-mpls-fr-03.txt, Nov. 685 1998. 686 3. MPLS using LDP and ATM VC switching, Davie et al, 687 draft-ietf-mpls-atm-02.txt, April 1999." 688 SYNTAX Unsigned32 (0..4294967295) 690 MplsBitRate ::= TEXTUAL-CONVENTION 691 DISPLAY-HINT "d" 692 STATUS current 693 DESCRIPTION 694 "An estimate of bandwidth in units of 1,000 bits per 695 second. If this object reports a value of 'n' then 696 the rate of the object is somewhere in the range of 697 'n-500' to 'n+499'. For objects which do not vary in 698 bitrate, or for those where no accurate estimation 699 can be made, this object should contain the nominal 700 bitrate." 701 SYNTAX Integer32 (1..2147483647) 703 MplsBurstSize ::= TEXTUAL-CONVENTION 704 DISPLAY-HINT "d" 705 STATUS current 706 DESCRIPTION 707 "The number of octets of MPLS data that the stream 708 may send back-to-back without concern for policing." 709 SYNTAX Integer32 (1..2147483647) 711 MplsBufferSize ::= TEXTUAL-CONVENTION 712 DISPLAY-HINT "d" 713 STATUS current 714 DESCRIPTION 715 "Size of buffer in octets of MPLS data." 716 SYNTAX Integer32 (1..2147483647) 718 MplsObjectOwner ::= TEXTUAL-CONVENTION 719 STATUS current 720 DESCRIPTION 721 "The entity which owns the object in question." 722 SYNTAX INTEGER { 723 other(1), 724 snmp(2), 725 ldp(3), 726 rsvp(4), 727 policyAgent(5), 728 unknown (6) 729 } 731 -- Top level components of this MIB. 733 -- Tables, Scalars 734 mplsLsrObjects OBJECT IDENTIFIER ::= { mplsLsrMIB 1 } 735 -- traps 736 mplsLsrNotifications OBJECT IDENTIFIER ::= { mplsLsrMIB 2 } 737 -- conformance 738 mplsLsrConformance OBJECT IDENTIFIER ::= { mplsLsrMIB 3 } 740 -- MPLS Interface Configuration Table. 742 mplsInterfaceConfTable OBJECT-TYPE 743 SYNTAX SEQUENCE OF MplsInterfaceConfEntry 744 MAX-ACCESS not-accessible 745 STATUS current 746 DESCRIPTION 747 "This table specifies per-interface MPLS capability 748 and associated information." 749 ::= { mplsLsrObjects 1 } 751 mplsInterfaceConfEntry OBJECT-TYPE 752 SYNTAX MplsInterfaceConfEntry 753 MAX-ACCESS not-accessible 754 STATUS current 755 DESCRIPTION 756 "An entry in this table is created by an LSR for 757 every interface capable of supporting MPLS. The 758 entry with index 0 represents the per-platform label 759 space and contains parameters that apply to all 760 interfaces that participate in the per-platform 761 label space. Other entries defined in this table 762 represent additional MPLS interfaces that may 763 participate in either the per-platform or per- 764 interface label spaces, or both. Additional 765 information about label space participation of an 766 interface is provided in the description clause of 767 mplsInterfaceLabelParticipationType." 768 INDEX { mplsInterfaceConfIndex } 769 ::= { mplsInterfaceConfTable 1 } 771 MplsInterfaceConfEntry ::= SEQUENCE { 772 mplsInterfaceConfIndex InterfaceIndexOrZero, 773 mplsInterfaceLabelMinIn MplsLabel, 774 mplsInterfaceLabelMaxIn MplsLabel, 775 mplsInterfaceLabelMinOut MplsLabel, 776 mplsInterfaceLabelMaxOut MplsLabel, 777 mplsInterfaceTotalBandwidth MplsBitRate, 778 mplsInterfaceAvailableBandwidth MplsBitRate, 779 mplsInterfaceTotalBuffer MplsBufferSize, 780 mplsInterfaceAvailableBuffer MplsBufferSize, 781 mplsInterfaceLabelParticipationType BITS, 782 mplsInterfaceConfStorageType StorageType 783 } 785 mplsInterfaceConfIndex OBJECT-TYPE 786 SYNTAX InterfaceIndexOrZero 787 MAX-ACCESS not-accessible 788 STATUS current 789 DESCRIPTION 790 "This is a unique index for an entry in the 791 MplsInterfaceConfTable. A non-zero index for an 792 entry indicates the ifIndex for the corresponding 793 interface entry in of the MPLS-layer in the ifTable. 794 Note that the per-platform label space may apply to 795 several interfaces, and therefore the configuration 796 of the per-platform label space interface parameters 797 will apply to all of the interfaces that are 798 participating in the per-platform label space." 799 REFERENCE 800 "RFC 2233 - The Interfaces Group MIB using SMIv2, 801 McCloghrie, K., and F. Kastenholtz, Nov. 1997" 802 ::= { mplsInterfaceConfEntry 1 } 804 mplsInterfaceLabelMinIn OBJECT-TYPE 805 SYNTAX MplsLabel 806 MAX-ACCESS read-only 807 STATUS current 808 DESCRIPTION 809 "This is the minimum value of an MPLS label that this 810 LSR is willing to receive on this interface." 811 ::= { mplsInterfaceConfEntry 2 } 813 mplsInterfaceLabelMaxIn OBJECT-TYPE 814 SYNTAX MplsLabel 815 MAX-ACCESS read-only 816 STATUS current 817 DESCRIPTION 818 "This is the maximum value of an MPLS label that this 819 LSR is willing to receive on this interface." 820 ::= { mplsInterfaceConfEntry 3 } 822 mplsInterfaceLabelMinOut OBJECT-TYPE 823 SYNTAX MplsLabel 824 MAX-ACCESS read-only 825 STATUS current 826 DESCRIPTION 827 "This is the minimum value of an MPLS label that this 828 LSR is willing to send on this interface." 829 ::= { mplsInterfaceConfEntry 4 } 831 mplsInterfaceLabelMaxOut OBJECT-TYPE 832 SYNTAX MplsLabel 833 MAX-ACCESS read-only 834 STATUS current 835 DESCRIPTION 836 "This is the maximum value of an MPLS label that this 837 LSR is willing to send on this interface." 838 ::= { mplsInterfaceConfEntry 5 } 840 mplsInterfaceTotalBandwidth OBJECT-TYPE 841 SYNTAX MplsBitRate 842 MAX-ACCESS read-only 843 STATUS current 844 DESCRIPTION 845 "This value indicates the total amount of usable 846 bandwidth on this interface and is specified in 847 kilobits per second (Kbps). This variable is 848 not applicable when applied to the interface with 849 index 0." 850 ::= { mplsInterfaceConfEntry 6 } 852 mplsInterfaceAvailableBandwidth OBJECT-TYPE 853 SYNTAX MplsBitRate 854 MAX-ACCESS read-only 855 STATUS current 856 DESCRIPTION 857 "This value indicates the total amount of available 858 bandwidth available on this interface and is 859 specified in kilobits per second (Kbps). This 860 value is calculated as the difference between the 861 amount of bandwidth currently in use and that 862 specified in mplsInterfaceTotalBandwidth. This 863 variable is not applicable when applied to the 864 interface with index 0." 865 ::= { mplsInterfaceConfEntry 7 } 867 mplsInterfaceTotalBuffer OBJECT-TYPE 868 SYNTAX MplsBufferSize 869 MAX-ACCESS read-only 870 STATUS current 871 DESCRIPTION 872 "This value indicates the total amount of buffer 873 space allocated for this interface. This variable 874 is not applicable when applied to the interface with 875 index 0." 876 ::= { mplsInterfaceConfEntry 8 } 878 mplsInterfaceAvailableBuffer OBJECT-TYPE 879 SYNTAX MplsBufferSize 880 MAX-ACCESS read-only 881 STATUS current 882 DESCRIPTION 883 "This value reflects the total amount of buffer space 884 available on this interface. This variable is not 885 applicable when applied to the interface with index 886 0." 887 ::= { mplsInterfaceConfEntry 9 } 889 mplsInterfaceLabelParticipationType OBJECT-TYPE 890 SYNTAX BITS { 891 perPlatform (0), 892 perInterface (1) 893 } 894 MAX-ACCESS read-only 895 STATUS current 896 DESCRIPTION 897 "Either the perPlatform(0) or perInterface(1) bit 898 MUST be set. If the value of the 899 mplsInterfaceConfIndex for this entry is zero, then 900 only the perPlatform(0) bit MUST be set and the 901 perInterface(1) bit is meaningless. If the 902 perInterface(1) bit is set then the value of 903 mplsInterfaceLabelMinIn, mplsInterfaceLabelMaxIn, 904 mplsInterfaceLabelMinOut, and 905 mplsInterfaceLabelMaxOut for this entry reflect the 906 label ranges for this interface. If only the 907 perPlatform(0) bit is set, then the value of 908 mplsInterfaceLabelMinIn, mplsInterfaceLabelMaxIn, 909 mplsInterfaceLabelMinOut, and 910 mplsInterfaceLabelMaxOut for this entry must be 911 identical to the instance of these objects with 912 index 0." 913 REFERENCE 914 "Multiprotocol Label Switching, Rosen et al, draft-ietf-mpls- 915 arch-06.txt, August 1999." 916 ::= { mplsInterfaceConfEntry 10 } 918 mplsInterfaceConfStorageType OBJECT-TYPE 919 SYNTAX StorageType 920 MAX-ACCESS read-create 921 STATUS current 922 DESCRIPTION 923 "The storage type for this entry." 924 ::= { mplsInterfaceConfEntry 11 } 926 -- End of mplsInterfaceConfTable 928 -- MPLS Interface Performance Table. 930 mplsInterfacePerfTable OBJECT-TYPE 931 SYNTAX SEQUENCE OF MplsInterfacePerfEntry 932 MAX-ACCESS not-accessible 933 STATUS current 934 DESCRIPTION 935 "This table provides MPLS performance information on 936 a per-interface basis." 937 ::= { mplsLsrObjects 2 } 939 mplsInterfacePerfEntry OBJECT-TYPE 940 SYNTAX MplsInterfacePerfEntry 941 MAX-ACCESS not-accessible 942 STATUS current 943 DESCRIPTION 944 "An entry in this table is created by the LSR for 945 every interface capable of supporting MPLS. Its is 946 an extension to the mplsInterfaceConfEntry table." 947 AUGMENTS { mplsInterfaceConfEntry } 948 ::= { mplsInterfacePerfTable 1 } 950 MplsInterfacePerfEntry ::= SEQUENCE { 951 -- incoming direction 952 mplsInterfaceInLabelsUsed Gauge32, 953 mplsInterfaceInPackets Counter32, 954 mplsInterfaceInDiscards Counter32, 955 mplsInterfaceFailedLabelLookup Counter32, 957 -- outgoing direction 958 mplsInterfaceOutLabelsUsed Gauge32, 959 mplsInterfaceOutPackets Counter32, 960 mplsInterfaceOutDiscards Counter32, 961 mplsInterfaceOutFragments Counter32 962 } 964 mplsInterfaceInLabelsUsed OBJECT-TYPE 965 SYNTAX Gauge32 966 MAX-ACCESS read-only 967 STATUS current 968 DESCRIPTION 969 "This value indicates the specific number of labels 970 that are in use at this point in time on this 971 interface in the incoming direction." 972 ::= { mplsInterfacePerfEntry 1 } 974 mplsInterfaceInPackets OBJECT-TYPE 975 SYNTAX Counter32 976 MAX-ACCESS read-only 977 STATUS current 978 DESCRIPTION 979 "This variable reflects the number of labeled packets 980 that have been received on this interface." 981 ::= { mplsInterfacePerfEntry 2 } 983 mplsInterfaceInDiscards OBJECT-TYPE 984 SYNTAX Counter32 985 MAX-ACCESS read-only 986 STATUS current 987 DESCRIPTION 988 "The number of inbound labeled packets, which were 989 chosen to be discarded even though no errors had 990 been detected to prevent their being transmitted. 991 One possible reason for discarding such a labeled 992 packet could be to free up buffer space." 993 ::= { mplsInterfacePerfEntry 3 } 995 mplsInterfaceFailedLabelLookup OBJECT-TYPE 996 SYNTAX Counter32 997 MAX-ACCESS read-only 998 STATUS current 999 DESCRIPTION 1000 "This value indicates the number of labeled packets 1001 that have been received on this interface and were 1002 discarded because there were no matching entries 1003 found for them in mplsInSegmentTable." 1004 ::= { mplsInterfacePerfEntry 4 } 1006 mplsInterfaceOutLabelsUsed OBJECT-TYPE 1007 SYNTAX Gauge32 1008 MAX-ACCESS read-only 1009 STATUS current 1010 DESCRIPTION 1011 "Indicates the number of top-most labels in the 1012 outgoing label stacks that are in use at this point 1013 in time on this interface." 1014 ::= { mplsInterfacePerfEntry 5 } 1016 mplsInterfaceOutPackets OBJECT-TYPE 1017 SYNTAX Counter32 1018 MAX-ACCESS read-only 1019 STATUS current 1020 DESCRIPTION 1021 "This variable contains the number of labeled packets 1022 that have been transmitted on this interface." 1023 ::= { mplsInterfacePerfEntry 6 } 1025 mplsInterfaceOutDiscards OBJECT-TYPE 1026 SYNTAX Counter32 1027 MAX-ACCESS read-only 1028 STATUS current 1029 DESCRIPTION 1030 "The number of outbound labeled packets, which were 1031 chosen to be discarded even though no errors had 1032 been detected to prevent their being transmitted. 1033 One possible reason for discarding such a labeled 1034 packet could be to free up buffer space." 1035 ::= { mplsInterfacePerfEntry 7 } 1037 mplsInterfaceOutFragments OBJECT-TYPE 1038 SYNTAX Counter32 1039 MAX-ACCESS read-only 1040 STATUS current 1041 DESCRIPTION 1042 "This variable indicates the number of outgoing MPLS 1043 packets that required fragmentation before 1044 transmission on this interface." 1045 ::= { mplsInterfacePerfEntry 8 } 1047 -- In-segment table. 1049 mplsInSegmentTable OBJECT-TYPE 1050 SYNTAX SEQUENCE OF MplsInSegmentEntry 1051 MAX-ACCESS not-accessible 1052 STATUS current 1053 DESCRIPTION 1054 "This table contains a collection of incoming 1055 segments to an LSR." 1056 ::= { mplsLsrObjects 3 } 1058 mplsInSegmentEntry OBJECT-TYPE 1059 SYNTAX MplsInSegmentEntry 1060 MAX-ACCESS not-accessible 1061 STATUS current 1062 DESCRIPTION 1063 "An entry in this table represents one incoming 1064 segment. An entry can be created by a network 1065 administrator or an SNMP agent, or an MPLS signaling 1066 protocol. The creator of the entry is denoted by 1067 mplsInSegmentOwner. An entry in this table is 1068 indexed by the ifIndex of the incoming interface and 1069 the (top) label." 1070 INDEX { mplsInSegmentIfIndex, mplsInSegmentLabel } 1071 ::= { mplsInSegmentTable 1 } 1073 MplsInSegmentEntry ::= SEQUENCE { 1074 mplsInSegmentIfIndex InterfaceIndexOrZero, 1075 mplsInSegmentLabel MplsLabel, 1076 mplsInSegmentNPop Integer32, 1077 mplsInSegmentAddrFamily AddressFamilyNumbers, 1078 mplsInSegmentXCIndex Integer32, 1079 mplsInSegmentOwner MplsObjectOwner, 1080 mplsInSegmentTrafficParamPtr RowPointer, 1081 mplsInSegmentRowStatus RowStatus, 1082 mplsInSegmentStorageType StorageType, 1083 mplsInSegmentAdminStatus INTEGER, 1084 mplsInSegmentOperStatus INTEGER 1085 } 1087 mplsInSegmentIfIndex OBJECT-TYPE 1088 SYNTAX InterfaceIndexOrZero 1089 MAX-ACCESS not-accessible 1090 STATUS current 1091 DESCRIPTION 1092 "This is a unique index for an entry in the 1093 MplsInSegmentTable. This value represents the 1094 interface index for the incoming MPLS interface. A 1095 value of zero represents an incoming label from the 1096 per-platform label space. In this case, the 1097 mplsInSegmentLabel is interpreted to be an MPLS-type 1098 label." 1099 ::= { mplsInSegmentEntry 1 } 1101 mplsInSegmentLabel OBJECT-TYPE 1102 SYNTAX MplsLabel 1103 MAX-ACCESS not-accessible 1104 STATUS current 1105 DESCRIPTION 1106 "The incoming label for this segment." 1107 ::= { mplsInSegmentEntry 2 } 1109 mplsInSegmentNPop OBJECT-TYPE 1110 SYNTAX Integer32 (1..2147483647) 1111 MAX-ACCESS read-create 1112 STATUS current 1113 DESCRIPTION 1114 "The number of labels to pop from the incoming 1115 packet. Normally only the top label is popped from 1116 the packet and used for all switching decisions for 1117 that packet. Note that technologies which do not 1118 support label popping should set this value to its 1119 default value of 1." 1120 DEFVAL { 1 } 1121 ::= { mplsInSegmentEntry 3 } 1123 mplsInSegmentAddrFamily OBJECT-TYPE 1124 SYNTAX AddressFamilyNumbers 1125 MAX-ACCESS read-create 1126 STATUS current 1127 DESCRIPTION 1128 "The IANA address family [IANAFamily] of the incoming 1129 packet. A value of other(0) indicates that the 1130 family type is either unknown or undefined." 1131 DEFVAL { other } 1132 ::= { mplsInSegmentEntry 4 } 1134 mplsInSegmentXCIndex OBJECT-TYPE 1135 SYNTAX Integer32 (0..2147483647) 1136 MAX-ACCESS read-only 1137 STATUS current 1138 DESCRIPTION 1139 "Index into mplsXCTable which identifies which cross- 1140 connect entry this segment is part of. A value of 1141 zero indicates that this entry is not referred to by 1142 any cross-connect entry. When a cross-connect entry 1143 is created which this in-segment is a part of, this 1144 object is automatically updated to reflect the value 1145 of mplsXCIndex of that cross-connect entry." 1146 DEFVAL { 0 } 1147 ::= { mplsInSegmentEntry 5 } 1149 mplsInSegmentOwner OBJECT-TYPE 1150 SYNTAX MplsObjectOwner 1151 MAX-ACCESS read-create 1152 STATUS current 1153 DESCRIPTION 1154 "Denotes the entity that created and is responsible 1155 for managing this segment." 1156 DEFVAL { unknown } 1157 ::= { mplsInSegmentEntry 6 } 1159 mplsInSegmentTrafficParamPtr OBJECT-TYPE 1160 SYNTAX RowPointer 1161 MAX-ACCESS read-create 1162 STATUS current 1163 DESCRIPTION 1164 "This variable represents a pointer to the traffic 1165 parameter specification for this in-segment. This 1166 value may point at an entry in the 1167 mplsTrafficParamTable to indicate which 1168 mplsTrafficParamEntry is to be assigned to this 1169 segment. This value may optionally point at an 1170 externally defined traffic parameter specification 1171 table. A value of zero-dot-zero indicates best-effort 1172 treatment. By having the same value of this object, 1173 two or more segments can indicate resource sharing." 1174 ::= { mplsInSegmentEntry 7 } 1176 mplsInSegmentRowStatus OBJECT-TYPE 1177 SYNTAX RowStatus 1178 MAX-ACCESS read-create 1179 STATUS current 1180 DESCRIPTION 1181 "This variable is used to create, modify, and/or 1182 delete a row in this table." 1183 ::= { mplsInSegmentEntry 8 } 1185 mplsInSegmentStorageType OBJECT-TYPE 1186 SYNTAX StorageType 1187 MAX-ACCESS read-create 1188 STATUS current 1189 DESCRIPTION 1190 "This variable indicates the storage type for this 1191 object." 1192 ::= { mplsInSegmentEntry 9 } 1194 mplsInSegmentAdminStatus OBJECT-TYPE 1195 SYNTAX INTEGER { 1196 up(1), -- ready to pass packets 1197 down(2), 1198 testing(3) -- in some test mode 1199 } 1200 MAX-ACCESS read-create 1201 STATUS current 1202 DESCRIPTION 1203 "This value is used to represent the manager�s 1204 desired operational status of this segment." 1205 ::= { mplsInSegmentEntry 10 } 1207 mplsInSegmentOperStatus OBJECT-TYPE 1208 SYNTAX INTEGER { 1209 up(1), -- ready to pass packets 1210 down(2), 1211 testing(3), -- in some test mode 1212 unknown(4), -- status cannot be determined for 1213 -- some reason 1214 dormant(5), 1215 notPresent(6), -- some component is missing 1216 lowerLayerDown(7) -- down due to the state of 1217 -- lower layer interfaces 1218 } 1219 MAX-ACCESS read-only 1220 STATUS current 1221 DESCRIPTION 1222 "This value represents the actual operational status 1223 of this segment." 1224 ::= { mplsInSegmentEntry 11 } 1226 -- End of mplsInSegmentTable 1227 -- In-segment performance table. 1229 mplsInSegmentPerfTable OBJECT-TYPE 1230 SYNTAX SEQUENCE OF MplsInSegmentPerfEntry 1231 MAX-ACCESS not-accessible 1232 STATUS current 1233 DESCRIPTION 1234 "This table contains statistical information for 1235 incoming MPLS segments to an LSR." 1236 ::= { mplsLsrObjects 4 } 1238 mplsInSegmentPerfEntry OBJECT-TYPE 1239 SYNTAX MplsInSegmentPerfEntry 1240 MAX-ACCESS not-accessible 1241 STATUS current 1242 DESCRIPTION 1243 "An entry in this table contains statistical 1244 information about one incoming segment which was 1245 configured in the mplsInSegmentTable. The counters 1246 in this entry should behave in a manner similar to 1247 that of the interface." 1248 AUGMENTS { mplsInSegmentEntry } 1249 ::= { mplsInSegmentPerfTable 1 } 1251 MplsInSegmentPerfEntry ::= SEQUENCE { 1252 mplsInSegmentOctets Counter32, 1253 mplsInSegmentPackets Counter32, 1254 mplsInSegmentErrors Counter32, 1255 mplsInSegmentDiscards Counter32, 1257 -- high capacity counter 1258 mplsInSegmentHCOctets Counter64, 1260 mplsInSegmentPerfDiscontinuityTime TimeStamp 1261 } 1263 mplsInSegmentOctets OBJECT-TYPE 1264 SYNTAX Counter32 1265 MAX-ACCESS read-only 1266 STATUS current 1267 DESCRIPTION 1268 "This value represents the total number of octets 1269 received by this segment." 1270 ::= { mplsInSegmentPerfEntry 1 } 1272 mplsInSegmentPackets OBJECT-TYPE 1273 SYNTAX Counter32 1274 MAX-ACCESS read-only 1275 STATUS current 1276 DESCRIPTION 1277 "Total number of packets received by this segment." 1278 ::= { mplsInSegmentPerfEntry 2 } 1280 mplsInSegmentErrors OBJECT-TYPE 1281 SYNTAX Counter32 1282 MAX-ACCESS read-only 1283 STATUS current 1284 DESCRIPTION 1285 "The number of errored packets received on this 1286 segment." 1287 ::= { mplsInSegmentPerfEntry 3 } 1289 mplsInSegmentDiscards OBJECT-TYPE 1290 SYNTAX Counter32 1291 MAX-ACCESS read-only 1292 STATUS current 1293 DESCRIPTION 1294 "The number of labeled packets received on this in- 1295 segment, which were chosen to be discarded even 1296 though no errors had been detected to prevent their 1297 being transmitted. One possible reason for 1298 discarding such a labeled packet could be to free up 1299 buffer space." 1300 ::= { mplsInSegmentPerfEntry 4 } 1302 mplsInSegmentHCOctets OBJECT-TYPE 1303 SYNTAX Counter64 1304 MAX-ACCESS read-only 1305 STATUS current 1306 DESCRIPTION 1307 "The total number of octets received. This is the 64 1308 bit version of mplsInSegmentOctets." 1309 ::= { mplsInSegmentPerfEntry 5 } 1311 mplsInSegmentPerfDiscontinuityTime OBJECT-TYPE 1312 SYNTAX TimeStamp 1313 MAX-ACCESS read-only 1314 STATUS current 1315 DESCRIPTION 1316 "The value of sysUpTime on the most recent occasion at 1317 which any one or more of this segment's Counter32 or 1318 Counter64 suffered a discontinuity. If no such 1319 discontinuities have occurred since the last re- 1320 initialization of the local management subsystem, then 1321 this object contains a zero value." 1322 ::= { mplsInSegmentPerfEntry 6 } 1324 -- End of mplsInSegmentPerfTable. 1326 -- Out-segment table. 1328 mplsOutSegmentIndexNext OBJECT-TYPE 1329 SYNTAX Integer32 (0..2147483647) 1330 MAX-ACCESS read-only 1331 STATUS current 1332 DESCRIPTION 1333 "This object contains the next appropriate value to 1334 be used for mplsOutSegmentIndex when creating 1335 entries in the mplsOutSegmentTable. If the number 1336 of unassigned entries is exhausted, this object will 1337 take on the value of 0. To obtain the 1338 mplsOutSegmentIndex value for a new entry, the 1339 manager must first issue a management protocol 1340 retrieval operation to obtain the current value of 1341 this object. The agent should modify the value to 1342 reflect the next unassigned index after each 1343 retrieval operation. After a manager retrieves a 1344 value the agent will determine through its local 1345 policy when this index value will be made available 1346 for reuse." 1347 ::= { mplsLsrObjects 5 } 1349 mplsOutSegmentTable OBJECT-TYPE 1350 SYNTAX SEQUENCE OF MplsOutSegmentEntry 1351 MAX-ACCESS not-accessible 1352 STATUS current 1353 DESCRIPTION 1354 "This table contains a representation of the outgoing 1355 segments from an LSR." 1356 ::= { mplsLsrObjects 6 } 1358 mplsOutSegmentEntry OBJECT-TYPE 1359 SYNTAX MplsOutSegmentEntry 1360 MAX-ACCESS not-accessible 1361 STATUS current 1362 DESCRIPTION 1363 "An entry in this table represents one outgoing 1364 segment. An entry can be created by a network 1365 administrator or an SNMP agent, or an MPLS signaling 1366 protocol. The object mplsOutSegmentOwner indicates 1367 the creator of this entry." 1368 INDEX { mplsOutSegmentIndex } 1369 ::= { mplsOutSegmentTable 1 } 1371 MplsOutSegmentEntry ::= SEQUENCE { 1372 mplsOutSegmentIndex Integer32, 1373 mplsOutSegmentIfIndex InterfaceIndex, 1374 mplsOutSegmentPushTopLabel TruthValue, 1375 mplsOutSegmentTopLabel MplsLabel, 1376 mplsOutSegmentNextHopIpAddrType InetAddressType, 1377 mplsOutSegmentNextHopIpv4Addr InetAddressIPv4, 1378 mplsOutSegmentNextHopIpv6Addr InetAddressIPv6, 1379 mplsOutSegmentXCIndex Integer32, 1380 mplsOutSegmentOwner MplsObjectOwner, 1381 mplsOutSegmentTrafficParamPtr RowPointer, 1382 mplsOutSegmentRowStatus RowStatus, 1383 mplsOutSegmentStorageType StorageType, 1384 mplsOutSegmentAdminStatus INTEGER, 1385 mplsOutSegmentOperStatus INTEGER 1386 } 1388 mplsOutSegmentIndex OBJECT-TYPE 1389 SYNTAX Integer32(0..2147483647) 1390 MAX-ACCESS not-accessible 1391 STATUS current 1392 DESCRIPTION 1393 "This value contains a unique index for this row. 1394 While a value of 0 is not valid as an index for this 1395 row it can be supplied as a valid value to index 1396 mplsXCTable to access entries for which no out- 1397 segment has been configured." 1398 ::= { mplsOutSegmentEntry 1 } 1400 mplsOutSegmentIfIndex OBJECT-TYPE 1401 SYNTAX InterfaceIndex 1402 MAX-ACCESS read-create 1403 STATUS current 1404 DESCRIPTION 1405 "This value contains the interface index of the 1406 outgoing interface." 1407 ::= { mplsOutSegmentEntry 2 } 1409 mplsOutSegmentPushTopLabel OBJECT-TYPE 1410 SYNTAX TruthValue 1411 MAX-ACCESS read-create 1412 STATUS current 1413 DESCRIPTION 1414 "This value indicates whether or not a top label 1415 should be pushed onto the outgoing packet's label 1416 stack. The value of this variable must be set to 1417 true if the outgoing interface does not support pop- 1418 and-go (for example an ATM interface) or if it is a 1419 tunnel origination. Note that it is considered an 1420 error in the case that mplsOutSegmentPushTopLabel is 1421 set to false, but the cross-connect entry which 1422 refers to this out-segment has a non-zero 1423 mplsLabelStackIndex. The LSR MUST ensure that this 1424 situation does not happen " 1425 ::= { mplsOutSegmentEntry 3 } 1427 mplsOutSegmentTopLabel OBJECT-TYPE 1428 SYNTAX MplsLabel 1429 MAX-ACCESS read-create 1430 STATUS current 1431 DESCRIPTION 1432 "If mplsOutSegmentPushTopLabel is true then this 1433 represents the label that should be pushed onto the 1434 top of the outgoing packet's label stack." 1435 ::= { mplsOutSegmentEntry 4 } 1437 mplsOutSegmentNextHopIpAddrType OBJECT-TYPE 1438 SYNTAX InetAddressType 1439 MAX-ACCESS read-create 1440 STATUS current 1441 DESCRIPTION 1442 "Indicates whether the next hop address is IPv4 or 1443 IPv6. Note that a value of unknown (0) is valid 1444 only when the outgoing interface is of type point-to- 1445 point." 1446 DEFVAL { unknown } 1447 ::= { mplsOutSegmentEntry 5 } 1449 mplsOutSegmentNextHopIpv4Addr OBJECT-TYPE 1450 SYNTAX InetAddressIPv4 1451 MAX-ACCESS read-create 1452 STATUS current 1453 DESCRIPTION 1454 "IPv4 Address of the next hop. Its value is 1455 significant only when 1456 mplsOutSegmentNextHopIpAddrType is ipV4 (1), 1457 otherwise it should return a value of 0." 1458 ::= { mplsOutSegmentEntry 6 } 1460 mplsOutSegmentNextHopIpv6Addr OBJECT-TYPE 1461 SYNTAX InetAddressIPv6 1462 MAX-ACCESS read-create 1463 STATUS current 1464 DESCRIPTION 1465 "IPv6 address of the next hop. Its value is 1466 significant only when 1467 mplsOutSegmentNextHopIpAddrType is ipV6 (2), 1468 otherwise it should return a value of 0." 1469 ::= { mplsOutSegmentEntry 7 } 1471 mplsOutSegmentXCIndex OBJECT-TYPE 1472 SYNTAX Integer32 (0..2147483647) 1473 MAX-ACCESS read-only 1474 STATUS current 1475 DESCRIPTION 1476 "Index into mplsXCTable which identifies which cross- 1477 connect entry this segment is part of. A value of 1478 zero indicates that this entry is not referred to by 1479 any cross-connect entry. When a cross-connect entry 1480 is created which this out-segment is a part of, this 1481 object is automatically updated to reflect the value 1482 of mplsXCIndex of that cross-connect entry." 1483 DEFVAL { 0 } 1484 ::= { mplsOutSegmentEntry 8 } 1486 mplsOutSegmentOwner OBJECT-TYPE 1487 SYNTAX MplsObjectOwner 1488 MAX-ACCESS read-create 1489 STATUS current 1490 DESCRIPTION 1491 "Denotes the entity which created and is responsible 1492 for managing this segment." 1493 DEFVAL { unknown } 1494 ::= { mplsOutSegmentEntry 9 } 1496 mplsOutSegmentTrafficParamPtr OBJECT-TYPE 1497 SYNTAX RowPointer 1498 MAX-ACCESS read-create 1499 STATUS current 1500 DESCRIPTION 1501 "This variable represents a pointer to the traffic 1502 parameter specification for this out-segment. This 1503 value may point at an entry in the 1504 mplsTrafficParamTable to indicate which 1505 mplsTrafficParamEntry is to be assigned to this 1506 segment. This value may optionally point at an 1507 externally defined traffic parameter specification 1508 table. A value of zero-dot-zero indicates best- 1509 effort treatment. By having the same value of this 1510 object, two or more segments can indicate resource 1511 sharing." 1512 ::= { mplsOutSegmentEntry 10 } 1514 mplsOutSegmentRowStatus OBJECT-TYPE 1515 SYNTAX RowStatus 1516 MAX-ACCESS read-create 1517 STATUS current 1518 DESCRIPTION 1519 "For creating, modifying, and deleting this row." 1520 ::= { mplsOutSegmentEntry 11 } 1522 mplsOutSegmentStorageType OBJECT-TYPE 1523 SYNTAX StorageType 1524 MAX-ACCESS read-create 1525 STATUS current 1526 DESCRIPTION 1527 "This variable indicates the storage type for this 1528 object." 1529 ::= { mplsOutSegmentEntry 12 } 1531 mplsOutSegmentAdminStatus OBJECT-TYPE 1532 SYNTAX INTEGER { 1533 up(1), -- ready to pass packets 1534 down(2), 1535 testing(3) -- in some test mode 1536 } 1537 MAX-ACCESS read-create 1538 STATUS current 1539 DESCRIPTION 1540 "The desired operational status of this segment." 1541 ::= { mplsOutSegmentEntry 13 } 1543 mplsOutSegmentOperStatus OBJECT-TYPE 1544 SYNTAX INTEGER { 1545 up(1), -- ready to pass packets 1546 down(2), 1547 testing(3), -- in some test mode 1548 unknown(4), -- status cannot be determined 1549 -- for some reason 1550 dormant(5), 1551 notPresent(6), -- some component is missing 1552 lowerLayerDown(7) -- down due to the state 1553 -- of lower layer interfaces 1554 } 1555 MAX-ACCESS read-only 1556 STATUS current 1557 DESCRIPTION 1558 "The actual operational status of this segment." 1559 ::= { mplsOutSegmentEntry 14 } 1561 -- End of mplsOutSegmentTable 1563 -- Out-segment performance table. 1565 mplsOutSegmentPerfTable OBJECT-TYPE 1566 SYNTAX SEQUENCE OF MplsOutSegmentPerfEntry 1567 MAX-ACCESS not-accessible 1568 STATUS current 1569 DESCRIPTION 1570 "This table contains statistical information about 1571 outgoing segments from an LSR. The counters in this 1572 entry should behave in a manner similar to that of 1573 the interface." 1574 ::= { mplsLsrObjects 7 } 1576 mplsOutSegmentPerfEntry OBJECT-TYPE 1577 SYNTAX MplsOutSegmentPerfEntry 1578 MAX-ACCESS not-accessible 1579 STATUS current 1580 DESCRIPTION 1581 "An entry in this table contains statistical 1582 information about one outgoing segment configured in 1583 mplsOutSegmentTable." 1584 AUGMENTS { mplsOutSegmentEntry } 1585 ::= { mplsOutSegmentPerfTable 1 } 1587 MplsOutSegmentPerfEntry ::= SEQUENCE { 1588 mplsOutSegmentOctets Counter32, 1589 mplsOutSegmentPackets Counter32, 1590 mplsOutSegmentErrors Counter32, 1591 mplsOutSegmentDiscards Counter32, 1593 -- HC counter 1594 mplsOutSegmentHCOctets Counter64, 1596 mplsOutSegmentPerfDiscontinuityTime TimeStamp 1597 } 1599 mplsOutSegmentOctets OBJECT-TYPE 1600 SYNTAX Counter32 1601 MAX-ACCESS read-only 1602 STATUS current 1603 DESCRIPTION 1604 "This value contains the total number of octets sent 1605 on this segment." 1606 ::= { mplsOutSegmentPerfEntry 1 } 1608 mplsOutSegmentPackets OBJECT-TYPE 1609 SYNTAX Counter32 1610 MAX-ACCESS read-only 1611 STATUS current 1612 DESCRIPTION 1613 "This value contains the total number of packets sent 1614 on this segment." 1615 ::= { mplsOutSegmentPerfEntry 2 } 1617 mplsOutSegmentErrors OBJECT-TYPE 1618 SYNTAX Counter32 1619 MAX-ACCESS read-only 1620 STATUS current 1621 DESCRIPTION 1622 "Number of packets that could not be sent due to 1623 errors on this segment." 1624 ::= { mplsOutSegmentPerfEntry 3 } 1626 mplsOutSegmentDiscards OBJECT-TYPE 1627 SYNTAX Counter32 1628 MAX-ACCESS read-only 1629 STATUS current 1630 DESCRIPTION 1631 "The number of labeled packets received on this out- 1632 segment, which were chosen to be discarded even 1633 though no errors had been detected to prevent their 1634 being transmitted. One possible reason for 1635 discarding such a labeled packet could be to free up 1636 buffer space." 1637 ::= { mplsOutSegmentPerfEntry 4 } 1639 mplsOutSegmentHCOctets OBJECT-TYPE 1640 SYNTAX Counter64 1641 MAX-ACCESS read-only 1642 STATUS current 1643 DESCRIPTION 1644 "Total number of octets sent. This is the 64 bit 1645 version of mplsOutSegmentOctets." 1646 ::= { mplsOutSegmentPerfEntry 5 } 1648 mplsOutSegmentPerfDiscontinuityTime OBJECT-TYPE 1649 SYNTAX TimeStamp 1650 MAX-ACCESS read-only 1651 STATUS current 1652 DESCRIPTION 1653 "The value of sysUpTime on the most recent occasion at 1654 which any one or more of this segment's Counter32 or 1655 Counter64 suffered a discontinuity. If no such 1656 discontinuities have occurred since the last re- 1657 initialization of the local management subsystem, then 1658 this object contains a zero value." 1659 ::= { mplsOutSegmentPerfEntry 6 } 1661 -- End of mplsOutSegmentPerfTable. 1663 -- Cross-connect table. 1665 mplsXCIndexNext OBJECT-TYPE 1666 SYNTAX Integer32 (0..2147483647) 1667 MAX-ACCESS read-only 1668 STATUS current 1669 DESCRIPTION 1670 "This object contains an appropriate value to be used 1671 for mplsXCIndex when creating entries in the 1672 mplsXCTable. The value 0 indicates that no 1673 unassigned entries are available. To obtain the 1674 value of mplsXCIndex for a new entry in the 1675 mplsXCTable, the manager issues a management 1676 protocol retrieval operation to obtain the current 1677 value of mplsXCIndex. After each retrieval 1678 operation, the agent should modify the value to 1679 reflect the next unassigned index. After a manager 1680 retrieves a value the agent will determine through 1681 its local policy when this index value will be made 1682 available for reuse." 1683 ::= { mplsLsrObjects 8 } 1685 mplsXCTable OBJECT-TYPE 1686 SYNTAX SEQUENCE OF MplsXCEntry 1687 MAX-ACCESS not-accessible 1688 STATUS current 1689 DESCRIPTION 1690 "This table specifies information for switching 1691 between LSP segments. It supports point-to-point, 1692 point-to-multipoint and multipoint-to-point 1693 connections. mplsLabelStackTable specifies the 1694 label stack information for a cross-connect LSR and 1695 is referred to from mplsXCTable." 1696 ::= { mplsLsrObjects 9 } 1698 mplsXCEntry OBJECT-TYPE 1699 SYNTAX MplsXCEntry 1700 MAX-ACCESS not-accessible 1701 STATUS current 1702 DESCRIPTION 1703 "A row in this table represents one cross-connect 1704 entry. The following objects index it: 1706 - cross-connect index mplsXCIndex that uniquely 1707 identifies a group of cross-connect entries 1708 - interface index of the in-segment, 1709 mplsInSegmentIfIndex 1710 - incoming label(s), mplsInSegmentLabel 1711 - out-segment index, mplsOutSegmentIndex 1713 Originating LSPs: 1714 These are represented by using the special 1715 combination of values mplsInSegmentIfIndex=0 and 1716 mplsInSegmentLabel=0 as indexes. In this case the 1717 mplsOutSegmentIndex MUST be non-zero. 1719 Terminating LSPs: 1720 These are represented by using the special value 1721 mplsOutSegmentIndex=0 as index. 1723 Special labels: 1724 Entries indexed by reserved MPLS label values 0 1725 through 15 imply terminating LSPs and MUST have 1726 mplsOutSegmentIfIndex = 0. Note that situations 1727 where LSPs are terminated with incoming label equal 1728 to 0, should have mplsInSegmentIfIndex = 0 as well, 1729 but can be distinguished from originating LSPs 1730 because the mplsOutSegmentIfIndex = 0. The 1731 mplsOutSegmentIfIndex MUST only be set to 0 in 1732 cases of terminating LSPs. 1734 An entry can be created by a network administrator 1735 or by an SNMP agent as instructed by an MPLS 1736 signaling protocol." 1737 INDEX { mplsXCIndex, mplsInSegmentIfIndex, 1738 mplsInSegmentLabel, 1739 mplsOutSegmentIndex } 1740 ::= { mplsXCTable 1 } 1742 MplsXCEntry ::= SEQUENCE { 1743 mplsXCIndex Integer32, 1744 mplsXCLspId MplsLSPID, 1745 mplsXCLabelStackIndex Integer32, 1746 mplsXCIsPersistent TruthValue, 1747 mplsXCOwner MplsObjectOwner, 1748 mplsXCRowStatus RowStatus, 1749 mplsXCStorageType StorageType, 1750 mplsXCAdminStatus INTEGER, 1751 mplsXCOperStatus INTEGER 1752 } 1754 mplsXCIndex OBJECT-TYPE 1755 SYNTAX Integer32 (1..2147483647) 1756 MAX-ACCESS not-accessible 1757 STATUS current 1758 DESCRIPTION 1759 "Primary index for the row identifying a group of 1760 cross-connect segments." 1761 ::= { mplsXCEntry 1 } 1763 mplsXCLspId OBJECT-TYPE 1764 SYNTAX MplsLSPID 1765 MAX-ACCESS read-create 1766 STATUS current 1767 DESCRIPTION 1768 "This value identifies the label switched path that 1769 this cross-connect entry belongs to." 1770 ::= { mplsXCEntry 2 } 1772 mplsXCLabelStackIndex OBJECT-TYPE 1773 SYNTAX Integer32 (0..2147483647) 1774 MAX-ACCESS read-create 1775 STATUS current 1776 DESCRIPTION 1777 "Primary index into mplsLabelStackTable identifying a 1778 stack of labels to be pushed beneath the top label. 1779 Note that the top label identified by the out- 1780 segment ensures that all the components of a 1781 multipoint-to-point connection have the same 1782 outgoing label. A value of 0 indicates that no 1783 labels are to be stacked beneath the top label." 1784 ::= { mplsXCEntry 3 } 1786 mplsXCIsPersistent OBJECT-TYPE 1787 SYNTAX TruthValue 1788 MAX-ACCESS read-create 1789 STATUS current 1790 DESCRIPTION 1791 "Denotes whether or not this cross-connect entry and 1792 associated in- and out-segments should be restored 1793 automatically after failures. This value MUST be 1794 set to false in cases where this cross-connect entry 1795 was created by a signaling protocol." 1796 DEFVAL { false } 1797 ::= { mplsXCEntry 4 } 1799 mplsXCOwner OBJECT-TYPE 1800 SYNTAX MplsObjectOwner 1801 MAX-ACCESS read-create 1802 STATUS current 1803 DESCRIPTION 1804 "Denotes the entity that created and is responsible 1805 for managing this cross-connect." 1806 ::= { mplsXCEntry 5 } 1808 mplsXCRowStatus OBJECT-TYPE 1809 SYNTAX RowStatus 1810 MAX-ACCESS read-create 1811 STATUS current 1812 DESCRIPTION 1813 "For creating, modifying, and deleting this row." 1814 ::= { mplsXCEntry 6 } 1816 mplsXCStorageType OBJECT-TYPE 1817 SYNTAX StorageType 1818 MAX-ACCESS read-create 1819 STATUS current 1820 DESCRIPTION 1821 "Defines the storage type for this object." 1823 ::= { mplsXCEntry 7 } 1825 mplsXCAdminStatus OBJECT-TYPE 1826 SYNTAX INTEGER { 1827 up(1), -- ready to pass packets 1828 down(2), 1829 testing(3) -- in some test mode 1830 } 1831 MAX-ACCESS read-create 1832 STATUS current 1833 DESCRIPTION 1834 "The desired operational status of this segment." 1835 ::= { mplsXCEntry 8 } 1837 mplsXCOperStatus OBJECT-TYPE 1838 SYNTAX INTEGER { 1839 up(1), -- ready to pass packets 1840 down(2), 1841 testing(3), -- in some test mode 1842 unknown(4), -- status cannot be determined 1843 -- for some reason. 1844 dormant(5), 1845 notPresent(6), -- some component is missing 1846 lowerLayerDown(7) -- down due to the state of 1847 -- lower layer interfaces 1848 } 1849 MAX-ACCESS read-only 1850 STATUS current 1851 DESCRIPTION 1852 "The actual operational status of this cross- 1853 connect." 1854 ::= { mplsXCEntry 9 } 1856 -- End of mplsXCTable 1858 -- Label stack table. 1859 mplsMaxLabelStackDepth OBJECT-TYPE 1860 SYNTAX Integer32 (1..2147483647) 1861 MAX-ACCESS read-only 1862 STATUS current 1863 DESCRIPTION 1864 "The maximum stack depth supported by this LSR." 1865 ::= { mplsLsrObjects 10 } 1867 mplsLabelStackIndexNext OBJECT-TYPE 1868 SYNTAX Integer32 (0..2147483647) 1869 MAX-ACCESS read-only 1870 STATUS current 1871 DESCRIPTION 1872 "This object contains an appropriate value to be used 1873 for mplsLabelStackIndex when creating entries in the 1874 mplsLabelStackTable. The value 0 indicates that no 1875 unassigned entries are available. To obtain an 1876 mplsLabelStackIndex value for a new entry, the 1877 manager issues a management protocol retrieval 1878 operation to obtain the current value of this 1879 object. After each retrieval operation, the agent 1880 should modify the value to reflect the next 1881 unassigned index. After a manager retrieves a value 1882 the agent will determine through its local policy 1883 when this index value will be made available for 1884 reuse." 1885 ::= { mplsLsrObjects 11 } 1887 mplsLabelStackTable OBJECT-TYPE 1888 SYNTAX SEQUENCE OF MplsLabelStackEntry 1889 MAX-ACCESS not-accessible 1890 STATUS current 1891 DESCRIPTION 1892 "This table specifies the label stack to be pushed 1893 onto a packet, beneath the top label. Entries into 1894 this table are referred to from mplsXCTable." 1895 ::= { mplsLsrObjects 12 } 1897 mplsLabelStackEntry OBJECT-TYPE 1898 SYNTAX MplsLabelStackEntry 1899 MAX-ACCESS not-accessible 1900 STATUS current 1901 DESCRIPTION 1902 "An entry in this table represents one label which is 1903 to be pushed onto an outgoing packet, beneath the 1904 top label. An entry can be created by a network 1905 administrator or by an SNMP agent as instructed by 1906 an MPLS signaling protocol." 1907 INDEX { mplsLabelStackIndex, mplsLabelStackLabelIndex } 1908 ::= { mplsLabelStackTable 1 } 1910 MplsLabelStackEntry ::= SEQUENCE { 1911 mplsLabelStackIndex Integer32, 1912 mplsLabelStackLabelIndex Integer32, 1913 mplsLabelStackLabel MplsLabel, 1914 mplsLabelStackRowStatus RowStatus, 1915 mplsLabelStackStorageType StorageType 1916 } 1918 mplsLabelStackIndex OBJECT-TYPE 1919 SYNTAX Integer32 (1..2147483647) 1920 MAX-ACCESS not-accessible 1921 STATUS current 1922 DESCRIPTION 1923 "Primary index for this row identifying a stack of 1924 labels to be pushed on an outgoing packet, beneath 1925 the top label." 1926 ::= { mplsLabelStackEntry 1 } 1928 mplsLabelStackLabelIndex OBJECT-TYPE 1929 SYNTAX Integer32 (1..2147483647) 1930 MAX-ACCESS not-accessible 1931 STATUS current 1932 DESCRIPTION 1933 "Secondary index for this row identifying one label 1934 of the stack. Note that an entry with a smaller 1935 mplsLabelStackLabelIndex would refer to a label 1936 higher up the label stack and would be popped at a 1937 downstream LSR before a label represented by a 1938 higher mplsLabelStackLabelIndex at a downstream 1939 LSR." 1940 ::= { mplsLabelStackEntry 2 } 1942 mplsLabelStackLabel OBJECT-TYPE 1943 SYNTAX MplsLabel 1944 MAX-ACCESS read-create 1945 STATUS current 1946 DESCRIPTION 1947 "The label to pushed." 1948 ::= { mplsLabelStackEntry 3 } 1950 mplsLabelStackRowStatus OBJECT-TYPE 1951 SYNTAX RowStatus 1952 MAX-ACCESS read-create 1953 STATUS current 1954 DESCRIPTION 1955 "For creating, modifying, and deleting this row." 1956 ::= { mplsLabelStackEntry 4 } 1958 mplsLabelStackStorageType OBJECT-TYPE 1959 SYNTAX StorageType 1960 MAX-ACCESS read-create 1961 STATUS current 1962 DESCRIPTION 1963 "Defines the storage type for this object." 1964 ::= { mplsLabelStackEntry 5 } 1966 -- End of mplsLabelStackTable 1968 -- Traffic Parameter table. 1970 mplsTrafficParamIndexNext OBJECT-TYPE 1971 SYNTAX Integer32 (0..2147483647) 1972 MAX-ACCESS read-only 1973 STATUS current 1974 DESCRIPTION 1975 "This object contains an appropriate value which will 1976 be used for mplsTrafficParamIndex when creating 1977 entries in the mplsTrafficParamTable. The value 0 1978 indicates that no unassigned entries are available. 1979 To obtain the mplsTrafficParamIndex value for a new 1980 entry, the manager issues a management protocol 1981 retrieval operation to obtain the current value of 1982 this object. After each retrieval operation, the 1983 agent should modify the value to reflect the next 1984 unassigned index. After a manager retrieves a value 1985 the agent will determine through its local policy 1986 when this index value will be made available for 1987 reuse." 1988 ::= { mplsLsrObjects 13 } 1990 mplsTrafficParamTable OBJECT-TYPE 1991 SYNTAX SEQUENCE OF MplsTrafficParamEntry 1992 MAX-ACCESS not-accessible 1993 STATUS current 1994 DESCRIPTION 1995 "This table specifies the Traffic Parameter objects 1996 for in and out-segments." 1997 ::= { mplsLsrObjects 14 } 1999 mplsTrafficParamEntry OBJECT-TYPE 2000 SYNTAX MplsTrafficParamEntry 2001 MAX-ACCESS not-accessible 2002 STATUS current 2003 DESCRIPTION 2004 "An entry in this table represents the TrafficParam 2005 objects for one or more in or out segments. A 2006 single entry can be pointed to by multiple segments 2007 indicating resource sharing." 2008 INDEX { mplsTrafficParamIndex } 2009 ::= { mplsTrafficParamTable 1 } 2011 MplsTrafficParamEntry ::= SEQUENCE { 2012 mplsTrafficParamIndex Integer32, 2013 mplsTrafficParamMaxRate MplsBitRate, 2014 mplsTrafficParamMeanRate MplsBitRate, 2015 mplsTrafficParamMaxBurstSize MplsBurstSize, 2016 mplsTrafficParamRowStatus RowStatus, 2017 mplsTrafficParamStorageType StorageType 2018 } 2020 mplsTrafficParamIndex OBJECT-TYPE 2021 SYNTAX Integer32 (1..2147483647) 2022 MAX-ACCESS not-accessible 2023 STATUS current 2024 DESCRIPTION 2025 "Uniquely identifies this row of the table. Note 2026 that zero represents an invalid index." 2027 ::= { mplsTrafficParamEntry 1 } 2029 mplsTrafficParamMaxRate OBJECT-TYPE 2030 SYNTAX MplsBitRate 2031 UNITS "kilobits per second" 2032 MAX-ACCESS read-create 2033 STATUS current 2034 DESCRIPTION 2035 "Maximum rate in kilobits/second." 2036 ::= { mplsTrafficParamEntry 4 } 2038 mplsTrafficParamMeanRate OBJECT-TYPE 2039 SYNTAX MplsBitRate 2040 UNITS "kilobits per second" 2041 MAX-ACCESS read-create 2042 STATUS current 2043 DESCRIPTION 2044 "Mean rate in kilobits/second." 2045 ::= { mplsTrafficParamEntry 5 } 2047 mplsTrafficParamMaxBurstSize OBJECT-TYPE 2048 SYNTAX MplsBurstSize 2049 UNITS "bytes" 2050 MAX-ACCESS read-create 2051 STATUS current 2052 DESCRIPTION 2053 "Maximum burst size in bytes." 2054 ::= { mplsTrafficParamEntry 6 } 2056 mplsTrafficParamRowStatus OBJECT-TYPE 2057 SYNTAX RowStatus 2058 MAX-ACCESS read-create 2059 STATUS current 2060 DESCRIPTION 2061 "For creating, modifying, and deleting this row." 2062 ::= { mplsTrafficParamEntry 7 } 2064 mplsTrafficParamStorageType OBJECT-TYPE 2065 SYNTAX StorageType 2066 MAX-ACCESS read-create 2067 STATUS current 2068 DESCRIPTION 2069 "The storage type for this object." 2070 ::= { mplsTrafficParamEntry 8 } 2072 -- End of mplsTrafficParamTable 2074 -- Notification Configuration 2076 mplsInSegmentTrapEnable OBJECT-TYPE 2077 SYNTAX TruthValue 2078 MAX-ACCESS read-write 2079 STATUS current 2080 DESCRIPTION 2081 "If this object is true, then it enables the 2082 generation of mplsInSegmentUp and mplsInSegmentDown 2083 traps, otherwise these traps are not emitted." 2084 DEFVAL { false } 2085 ::= { mplsLsrObjects 15 } 2087 mplsOutSegmentTrapEnable OBJECT-TYPE 2088 SYNTAX TruthValue 2089 MAX-ACCESS read-write 2090 STATUS current 2091 DESCRIPTION 2092 "If this object is true, then it enables the 2093 generation of mplsOutSegmentUp and 2094 mplsOutSegmentDown traps, otherwise these traps are 2095 not emitted." 2096 DEFVAL { false } 2097 ::= { mplsLsrObjects 16 } 2099 mplsXCTrapEnable OBJECT-TYPE 2100 SYNTAX TruthValue 2101 MAX-ACCESS read-write 2102 STATUS current 2103 DESCRIPTION 2104 "If this object is true, then it enables the 2105 generation of mplsXCUp and mplsXCDown traps, 2106 otherwise these traps are not emitted." 2107 DEFVAL { false } 2108 ::= { mplsLsrObjects 17 } 2110 -- Interface 2112 -- In-segment. 2114 mplsInSegmentUp NOTIFICATION-TYPE 2115 OBJECTS { mplsInSegmentIfIndex, 2116 mplsInSegmentLabel, 2117 mplsInSegmentAdminStatus, 2118 mplsInSegmentOperStatus } 2119 STATUS current 2120 DESCRIPTION 2121 "This notification is generated when a 2122 mplsInSegmentOperStatus object for one of the 2123 configured in-segments is about to leave the down 2124 state and transition into some other state (but not 2125 into the notPresent state). This other state is 2126 indicated by the included value of 2127 mplsInSegmentOperStatus." 2128 ::= { mplsLsrNotifications 1 } 2130 mplsInSegmentDown NOTIFICATION-TYPE 2131 OBJECTS { mplsInSegmentIfIndex, 2132 mplsInSegmentLabel, 2133 mplsInSegmentAdminStatus, 2134 mplsInSegmentOperStatus } 2135 STATUS current 2136 DESCRIPTION 2137 "This notification is generated when a 2138 mplsInSegmentOperStatus object for one of the 2139 configured in-segments is about to enter the down 2140 state from some other state (but not from the 2141 notPresent state). This other state is indicated by 2142 the included value of mplsInSegmentOperStatus." 2143 ::= { mplsLsrNotifications 2 } 2145 -- Out-segment. 2147 mplsOutSegmentUp NOTIFICATION-TYPE 2148 OBJECTS { mplsOutSegmentIndex, 2149 mplsInSegmentAdminStatus, 2150 mplsInSegmentOperStatus } 2151 STATUS current 2152 DESCRIPTION 2153 "This notification is generated when a 2154 mplsOutSegmentOperStatus object for one of the 2155 configured out-segments is about to leave the down 2156 state and transition into some other state (but not 2157 into the notPresent state). This other state is 2158 indicated by the included value of 2159 mplsOutSegmentOperStatus." 2160 ::= { mplsLsrNotifications 3 } 2162 mplsOutSegmentDown NOTIFICATION-TYPE 2163 OBJECTS { mplsOutSegmentIndex, 2164 mplsInSegmentAdminStatus, 2165 mplsInSegmentOperStatus } 2166 STATUS current 2167 DESCRIPTION 2168 "This notification is generated when a 2169 mplsOutSegmentOperStatus object for one of the 2170 configured out-segments is about to enter the down 2171 state from some other state (but not from the 2172 notPresent state). This other state is indicated by 2173 the included value of mplsOutSegmentOperStatus." 2174 ::= { mplsLsrNotifications 4 } 2176 -- Cross-connect. 2178 mplsXCUp NOTIFICATION-TYPE 2179 OBJECTS { mplsXCIndex, 2180 mplsInSegmentIfIndex, 2181 mplsInSegmentLabel, 2182 mplsOutSegmentIndex, 2183 mplsXCAdminStatus, 2184 mplsXCOperStatus } 2185 STATUS current 2186 DESCRIPTION 2187 "This notification is generated when a 2188 mplsXCOperStatus object for one of the configured 2189 cross-connect entries is about to leave the down 2190 state and transition into some other state (but not 2191 into the notPresent state). This other state is 2192 indicated by the included value of 2193 mplsXCOperStatus." 2194 ::= { mplsLsrNotifications 5 } 2196 mplsXCDown NOTIFICATION-TYPE 2197 OBJECTS { mplsXCIndex, 2198 mplsInSegmentIfIndex, 2199 mplsInSegmentLabel, 2200 mplsOutSegmentIndex, 2201 mplsXCAdminStatus, 2202 mplsXCOperStatus } 2203 STATUS current 2204 DESCRIPTION 2205 "This notification is generated when a 2206 mplsXCOperStatus object for one of the configured 2207 cross-connect entries is about to enter the down 2208 state from some other state (but not from the 2209 notPresent state). This other state is indicated by 2210 the included value of mplsXCOperStatus." 2211 ::= { mplsLsrNotifications 6 } 2213 -- End of notifications. 2215 -- Module compliance. 2217 mplsLsrGroups 2218 OBJECT IDENTIFIER ::= { mplsLsrConformance 1 } 2220 mplsLsrCompliances 2221 OBJECT IDENTIFIER ::= { mplsLsrConformance 2 } 2223 mplsLsrModuleCompliance MODULE-COMPLIANCE 2224 STATUS current 2225 DESCRIPTION 2226 "Compliance statement for agents that support the 2227 MPLS LSR MIB." 2228 MODULE -- this module 2230 -- The mandatory groups have to be implemented 2231 -- by all LSRs. However, they may all be supported 2232 -- as read-only objects in the case where manual 2233 -- configuration is unsupported. 2235 MANDATORY-GROUPS { mplsInSegmentGroup, 2236 mplsOutSegmentGroup, 2237 mplsXCGroup, 2238 mplsInterfaceGroup, 2239 mplsPerfGroup, 2240 mplsSegmentDiscontinuityGroup } 2242 GROUP mplsHCInSegmentPerfGroup 2243 DESCRIPTION 2244 "This group is mandatory for those in-segment 2245 entries for which the object 2246 mplsInSegmentOutOctets wraps around too 2247 quickly." 2249 GROUP mplsHCOutSegmentPerfGroup 2250 DESCRIPTION 2251 "This group is mandatory for those out-segment 2252 entries for which the object 2253 mplsOutSegmentOctets wraps around too quickly." 2255 GROUP mplsTrafficParamGroup 2256 DESCRIPTION 2257 "This group is mandatory for those LSRs that 2258 support QoS resource reservation." 2260 -- Depending on whether the device implements 2261 -- persistent cross-connects or not one of the 2262 -- following two groups is mandatory. 2264 GROUP mplsXCIsPersistentGroup 2265 DESCRIPTION 2266 "This group is mandatory for devices which 2267 support persistent cross-connects. The 2268 following constraints apply: mplsXCIsPersistent 2269 must at least be read-only returning true(2)." 2271 GROUP mplsXCIsNotPersistentGroup 2272 DESCRIPTION 2273 "This group is mandatory for devices which 2274 support non-persistent cross-connects. The 2275 following constraints apply: mplsXCIsPersistent 2276 must at least be read-only returning false(1)." 2278 -- mplsInterfaceConfTable 2280 OBJECT mplsInterfaceConfStorageType 2281 SYNTAX INTEGER { other(1) } 2282 MIN-ACCESS read-only 2283 DESCRIPTION 2284 "Only other(1) needs to be supported." 2286 -- mplsInSegmentTable 2288 OBJECT mplsInSegmentXCIndex 2289 DESCRIPTION 2290 "Write access is not required." 2292 OBJECT mplsInSegmentNPop 2293 MIN-ACCESS read-only 2294 DESCRIPTION 2295 "Write access if not required. This object 2296 should be set to 1 if it is read-only." 2298 OBJECT mplsInSegmentAddrFamily 2299 DESCRIPTION 2300 "Write access is not required. A , 2671 August 1999. 2673 [MPLSFW] Callon, R., Doolan, P., Feldman, N., Fredette, A., 2674 Swallow, G., and A. Viswanathan, "A Framework for 2675 Multiprotocol Label Switching", Internet Draft 2676 , September 1999. 2678 [LblStk] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D., 2679 Federokow, G., Li, T., and A. Conta, "MPLS Label 2680 Stack Encoding", Internet Draft , September 1999. 2683 [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", 2684 RFC 1700, October 1994. See also: 2685 http://www.isi.edu/in-notes/iana/assignments/smi- 2686 numbers 2688 [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS 2689 FAMILY NUMBERS,(http://www.isi.edu/in- 2690 notes/iana/assignements/address-family-numbers), 2691 for MIB see: 2692 ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib 2694 [SNMPArch] Harrington, D., Presuhn, R., and B. Wijnen, "An 2695 Architecture for Describing SNMP Management 2696 Frameworks", RFC 2271, January 1998. 2698 [SMIv1] Rose, M., and K. McCloghrie, "Structure and 2699 Identification of Management Information for TCP/IP- 2700 based Internets", RFC 1155, May 1990. 2702 [SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB 2703 Definitions", RFC 1212, March 1991. 2705 [SNMPv1Traps] M. Rose, "A Convention for Defining Traps for use 2706 with the SNMP", RFC 1215, March 1991. 2708 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2709 "Message Processing and Dispatching for the Simple 2710 Network Management Protocol (SNMP)", RFC 2572, 2711 April 1999. 2713 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 2714 Model (USM) for version 3 of the Simple Network 2715 Management Protocol (SNMPv3)", RFC 2574, April 2716 1999. 2718 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. 2719 Waldbusser, "Protocol Operations for Version 2 of 2720 the Simple Network Management Protocol (SNMPv2)", 2721 RFC 1905, January 1996. 2723 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2724 Applications", RFC 2573, April 1999. 2726 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- 2727 based Access Control Model (VACM) for the Simple 2728 Network Management Protocol (SNMP)", RFC 2575, 2729 April 1999. 2731 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 2732 "Introduction to Version 3 of the Internet-standard 2733 Network Management Framework", RFC 2570, April 2734 1999. 2736 [SMIv2] Case, J., McCloghrie, K., Rose, M., and S. 2737 Waldbusser, "Structure of Management Information 2738 for Version 2 of the Simple Network Management 2739 Protocol (SNMPv2)", RFC 1902, January 1996. 2741 [SNMPv2TC] Case, J., McCloghrie, K., Rose, M., and S. 2742 Waldbusser, "Textual Conventions for Version 2 of 2743 the Simple Network Management Protocol (SNMPv2)", 2744 RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., 2745 January 1996. 2747 [SNMPv2Conf] Case, J., McCloghrie, K., Rose, M., and S. 2748 Waldbusser, "Conformance Statements for Version 2 2749 of the Simple Network Management Protocol 2750 (SNMPv2)", RFC 1904, January 1996. 2752 [SNMPv1] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 2753 "Simple Network Management Protocol", RFC 1157, May 2754 1990. 2756 [SNMPv2c] Case, J., McCloghrie, K., Rose, M., and S. 2757 Waldbusser, "Introduction to Community-based 2758 SNMPv2", RFC 1901, January 1996. 2760 [SNMPv2TM] Case, J., McCloghrie, K., Rose, M., and S. 2761 Waldbusser, "Transport Mappings for Version 2 of 2762 the Simple Network Management Protocol (SNMPv2)", 2763 RFC 1906, January 1996. 2765 [SNMPv3MP] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2766 "Message Processing and Dispatching for the Simple 2767 Network Management Protocol (SNMP)", RFC 2272, 2768 January 1998. 2770 [SNMPv3USM] Blumenthal, U., and B. Wijnen, "User-based Security 2771 Model (USM) for version 3 of the Simple Network 2772 Management Protocol (SNMPv3)", RFC 2574, April 2773 1999. 2775 [SNMPv2PO] Case, J., McCloghrie, K., Rose, M., and S. 2776 Waldbusser, "Protocol Operations for Version 2 of 2777 the Simple Network Management Protocol (SNMPv2)", 2778 RFC 1905, January 1996. 2780 [SNMPv3App] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2781 Applications", RFC 2273, January 1998. 2783 [SNMPv3VACM] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- 2784 based Access Control Model (VACM) for the Simple 2785 Network Management Protocol (SNMP)", RFC 2575, 2786 April 1999. 2788 [IPSEC] Kent, S., and Atkinson, R., "Security Architecture 2789 for the Internet Protocol", RFC 2401, November 2790 1998. 2792 [IFMIB] McCloghrie, K., and F. Kastenholtz, "The Interfaces 2793 Group MIB using SMIv2", RFC 2233, Nov. 1997 2795 [ATOMMIB] Tesink, K., "Definitions of Managed Objects for ATM 2796 Management", RFC 2515, Feb. 1999 2798 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 2799 Requirement Levels", BCP 14, RFC 2119, March 1997. 2801 15. Authors' Addresses 2803 Cheenu Srinivasan 2804 Tachion Networks, Inc. 2805 Monmouth Park Corporate Center I 2806 Building C, 185 Monmouth Parkway 2807 West Long Branch, NJ 07764 2808 Phone: +1-732-542-7750 x1234 2809 Email: cheenu@tachion.com 2811 Arun Viswanathan 2812 Force10 Networks, Inc. 2813 1440 McCarthy Blvd 2814 Milpitas, CA 95035 2815 Phone: +1-408-571-3516 2816 Email: arun@force10networks.com 2818 Thomas D. Nadeau 2819 Cisco Systems, Inc. 2820 250 Apollo Drive 2821 Chelmsford, MA 01824 2822 Phone: +1-978-244-3051 2823 Email: tnadeau@cisco.com 2825 16. Full Copyright Statement 2827 Copyright (C) The Internet Society (2000). All Rights Reserved. 2829 This document and translations of it may be copied and furnished 2830 to others, and derivative works that comment on or otherwise 2831 explain it or assist in its implementation may be prepared, 2832 copied, published and distributed, in whole or in part, without 2833 restriction of any kind, provided that the above copyright notice 2834 and this paragraph are included on all such copies and derivative 2835 works. However, this document itself may not be modified in any 2836 way, such as by removing the copyright notice or references to the 2837 Internet Society or other Internet organizations, except as needed 2838 for the purpose of developing Internet standards in which case 2839 the procedures for copyrights defined in the Internet Standards 2840 process must be followed, or as required to translate it into 2841 languages other than English. 2843 The limited permissions granted above are perpetual and will not 2844 be revoked by the Internet Society or its successors or assigns. 2845 This document and the information contained herein is provided on 2846 an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET 2847 ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR 2848 IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 2849 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2850 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.