idnits 2.17.1 draft-ietf-mpls-lsr-mib-00.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: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document is more than 15 pages and seems to lack a Table of Contents. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack an Authors' Addresses Section. ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 356 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? ** The abstract seems to contain references ([MPLSArch,MPLSFW], [LDPMIB]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 1335: '... mplsOutSegmentIndex MUST be non-zero....' RFC 2119 keyword, line 1343: '...mply terminating LSPs and MUST have...' Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 17 has weird spacing: '.... Note that...' == Line 18 has weird spacing: '... other group...' == Line 22 has weird spacing: '... months and ...' == Line 23 has weird spacing: '...cuments at a...' == Line 24 has weird spacing: '... Drafts as re...' == (351 more instances...) -- 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 103, but not defined == Unused Reference: 'RSVPTun' is defined on line 2157, but no explicit reference was found in the text == Unused Reference: 'CRLDP' is defined on line 2162, but no explicit reference was found in the text == Unused Reference: 'Assigned' is defined on line 2166, 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. 'LDPMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'LblStk' -- Possible downref: Non-RFC (?) normative reference: ref. 'RSVPTun' -- Possible downref: Non-RFC (?) normative reference: ref. 'CRLDP' ** Obsolete normative reference: RFC 1700 (ref. 'Assigned') (Obsoleted by RFC 3232) ** Obsolete normative reference: RFC 2271 (ref. 'SNMPArch') (Obsoleted by RFC 2571) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. 'SNMPv1Traps') ** Obsolete normative reference: RFC 1902 (ref. 'SMIv2') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. 'SNMPv2TC') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. 'SNMPv2Conf') (Obsoleted by RFC 2580) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. 'SNMPv1') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. 'SNMPv2c') ** Obsolete normative reference: RFC 1906 (ref. 'SNMPv2TM') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2272 (ref. 'SNMPv3MP') (Obsoleted by RFC 2572) ** Obsolete normative reference: RFC 2274 (ref. 'SNMPv3USM') (Obsoleted by RFC 2574) ** Obsolete normative reference: RFC 1905 (ref. 'SNMPv2PO') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2273 (ref. 'SNMPv3App') (Obsoleted by RFC 2573) ** Obsolete normative reference: RFC 2275 (ref. 'SNMPv3VACM') (Obsoleted by RFC 2575) Summary: 23 errors (**), 0 flaws (~~), 11 warnings (==), 8 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 Network Technologies 3 Expires: December 1999 4 Arun Viswanathan 5 Lucent Technologies 7 MPLS Label Switch Router Management Information Base Using SMIv2 9 draft-ietf-mpls-lsr-mib-00.txt 11 Status of this Memo 13 This document is an Internet-Draft and is in full conformance with 14 all provisions of Section 10 of RFC2026. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six 22 months and may be updated, replaced, or obsoleted by other 23 documents at any time. It is inappropriate to use Internet- 24 Drafts as reference material or to cite them other than as "work 25 in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 Abstract 35 This memo defines an experimental portion of the Management 36 Information Base (MIB) for use with network management protocols 37 in the Internet community. In particular, it describes managed 38 objects for modeling an Multi-Protocol Label Switching (MPLS) 39 [MPLSArch, MPLSFW] Label Switch Router (LSR). 41 Open Issues 43 - Does mplsTSpecTable belong in this document? 44 - Support for signalled COS value. 46 - Do we need objects to keep track of ownership of entries in 47 various tables? 49 - More descriptive text and detailed example. 51 - Reconcile mplsInterfaceConfTable with the interface related 52 objects in the LDP MIB [LDPMIB] including objects for 53 negotiated label ranges. 55 - Address multipath related issues. 57 - Introduce a scalar to indicate the maximum supported label 58 stack depth. 60 - For each MPLS capable interface, we need objects in 61 mplsInterfaceConfTable that indicate the resource availability 62 for MPLS, such as total bandwidth, available bandwidth for 63 each priority level, available buffer etc. 65 - Fragmentation counter in mplsInterfacePerfTable. 67 1. Introduction 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 an Multi-Protocol Label Switching (MPLS) 73 [MPLSArch, MPLSFW] Label Switch Router (LSR). 75 Comments should be made directly to the MPLS mailing list at 76 mpls@uu.net. 78 This memo does not, in its draft form, specify a standard for the 79 Internet community. 81 2. Terminology 83 This document uses terminology from the MPLS architecture document 84 [MPLSArch]. 86 A label switched path (LSP) is modelled as a connection consisting 87 of one or more in-segments and/or one or more out-segments at a 88 label switch router (LSR). The binding or interconnection between 89 in-segments and out-segments in performed using a cross-connect. 90 We use the terms connection and LSP interchangeably where the 91 meaning is clear from the context. 93 3. The SNMP Management Framework 95 The SNMP Management Framework presently consists of five major 96 components: 98 - An overall architecture, described in RFC 2271 [SNMPArch]. 100 - Mechanisms for describing and naming objects and events for the 101 purpose of management. The first version of this Structure of 102 Management Information (SMI) is called SMIv1 and described in 103 RFC 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215 104 [SNMPv1Traps]. The second version, called SMIv2, is described 105 in RFC 1902 [SMIv2], RFC 1903 [SNMPv2TC] and RFC 1904 106 [SNMPv2Conf]. 108 - Message protocols for transferring management information. The 109 first version of the SNMP message protocol is called SNMPv1 110 and described in RFC 1157 [SNMPv1]. A second version of the 111 SNMP message protocol, which is not an Internet standards 112 track protocol, is called SNMPv2c and described in RFC 1901 113 [SNMPv2c] and RFC 1906 [SNMPv2TM]. The third version of the 114 message protocol is called SNMPv3 and described in RFC 1906 115 [SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC 2274 [SNMPv3USM]. 117 - Protocol operations for accessing management information. The 118 first set of protocol operations and associated PDU formats is 119 described in RFC 1157 [SNMPv1]. A second set of protocol 120 operations and associated PDU formats is described in RFC 1905 121 [SNMPv2PO]. 123 - A set of fundamental applications described in RFC 2273 124 [SNMPv3App] and the view-based access control mechanism 125 described in RFC 2275 [SNMPv3VACM]. Managed objects are 126 accessed via a virtual information store, termed the 127 Management Information Base or MIB. Objects in the MIB are 128 defined using the mechanisms defined in the SMI. This memo 129 specifies a MIB module that is compliant to the SMIv2. A MIB 130 conforming to the SMIv1 can be produced through the 131 appropriate translations. The resulting translated MIB must 132 be semantically equivalent, except where objects or events are 133 omitted because no translation is possible (use of Counter64). 134 Some machine readable information in SMIv2 will be converted 135 into textual descriptions in SMIv1 during the translation 136 process. However, this loss of machine readable information 137 is not considered to change the semantics of the MIB. 139 3.1. Object Definitions 141 Managed objects are accessed via a virtual information store, 142 termed the Management Information Base or MIB. Objects in the MIB 143 are defined using the subset of Abstract Syntax Notation One 144 (ASN.1) defined in the SMI. In particular, each object type is 145 named by an OBJECT IDENTIFIER, an administratively assigned name. 146 The object type together with an object instance serves to 147 uniquely identify a specific instantiation of the object. For 148 human convenience, we often use a textual string, termed the 149 descriptor, to also refer to the object type. 151 4. Feature Checklist 153 The MPLS label switch router (LSR) MIB is designed to satisfy the 154 following requirements and constraints. 156 - The MIB should be able to support both manually configured LSPs 157 as well as via LDP and/or RSVP signaling. 159 - The MIB must support enabling and disabling of MPLS capability 160 on MPLS capable interfaces of an LSR. 162 - The MIB should allow resource sharing between two or more LSPs. 164 - Both per-platform and per-interface label spaces must be 165 supported. 167 - MPLS packets must be forwarded solely based on an incoming top 168 label [MPLSArch, LblStk]. 170 - Support must be provided for next-hop resolution when the 171 outgoing interface is a shared media interface. In the point- 172 to-multipoint case, each outgoing segment can be on a 173 different shared media interface. 175 - The MIB must support point-to-point, point-to-multipoint and 176 multipoint-to-point connections at an LSR. 178 - For multipoint-to-point connections all the outgoing packets 179 must have the same top label. 181 - For multipoint-to-point connections the outgoing resources of 182 the merged connections must be shared. 184 - For multipoint-to-point connections, packets from different 185 incoming connections may have distinct outgoing label stacks, 186 beneath the (identical) top label. 188 - In the point-to-multipoint case each outgoing connection can 189 have a distinct label stack including the top label. 191 - In a point-to-multipoint connection the ingress resources are 192 shared by all the members of the connection. 194 - The MIB must provide cross-connect capability to "pop" an 195 incoming label and forward the packet with the rest of the 196 label stack unchanged and without pushing any labels ("pop-and- 197 go") [LblStk]. 199 - It must be possible to assign or remap COS bits [LblStk] on the 200 outgoing label. In the multipoint-to-point case, each in- 201 segment can have a different outgoing COS value. In the point- 202 to-multipoint case, each out-segment can have a different 203 outgoing COS value. 205 - It should be possible to support persistent as well as non- 206 persistent LSPs. 208 - Performance counters must be provided for in-segments and out- 209 segments as well as for measuring MPLS performance on a per- 210 interface basis. 212 5. Outline 214 Configuring LSPs through an LSR involves the following steps. 216 - Enabling MPLS on MPLS capable interfaces. 218 - Configuring in and out segments. 220 - Setting up the cross-connect table to switch between segments 221 and/or to indicate connection origination and termination. 223 - (Optionally) specifying label stack actions. 224 - (Optionally) specifying segment traffic parameters. 226 5.1. Summary of LSR MIB 228 The MIB objects for performing these actions consist of the 229 following tables. 231 - Interface configuration table (mplsInterfaceConfTable) for 232 enabling MPLS on MPLS capable interfaces. 234 - In-segment (mplsInSegmentTable) and out-segment 235 (mplsOutSegmentTable) tables for configuring LSP segments at 236 an LSR. 238 - Cross-connect table (mplsXCTable) for creating relationships 239 between in and out segments constituting a cross-connect. 241 - Label stack table (mplsLabelStackTable) for specifying label 242 stack operations. 244 - TSpec table (mplsTSpecTable) for specifying LSP related 245 traffic parameters. 247 Further, the MPLS in-segment and out-segment performance tables, 248 mplsInSegmentPerfTable and mplsOutSegmentPerfTable, contain the 249 objects necessary to measure the performance of LSPs, and 250 mplsInterfacePerfTable has objects to measure MPLS performance on 251 a per-interface basis. 253 These tables are described in the subsequent sections. 255 6. Brief Description of MIB Objects 257 Sections 6.1-6.2 describe objects pertaining to MPLS capable 258 interfaces of an LSR. The objects described in Sections 6.3-6.8, 259 when considered together, are equivalent to the tables described 260 in the MPLS architecture document [MPLSArch], that is, the 261 Incoming Label Map (ILM) and the Next Hop Label Forwarding Entry 262 (NHLFE) tables. Section 6.9 describes objects for specifying 263 traffic parameters for in and out segments. 265 6.1. mplsInterfaceConfTable 267 This table represents the interfaces that are MPLS capable. An 268 LSR creates an entry in this table for every MPLS capable 269 interface on that LSR. Each entry contains information about per- 270 interface label ranges. The administrator can specify the desired 271 MPLS status (enable/up, disable/down, testing) of an interface by 272 writing the object mplsInterfaceAdminStatus. The actual status is 273 indicated by the object mplsInterfaceOperStatus. 275 6.2. mplsInterfacePerfTable 277 This table contains objects to measure the MPLS performance of 278 MPLS capable interfaces and is an AUGMENT to 279 mplsInterfaceConfTable. High capacity counters are provided for 280 objects that are likely to wrap around quickly on high-speed 281 interfaces. 283 6.3. mplsInSegmentTable 285 This table contains a description of the incoming MPLS segments to 286 an LSR and their associated parameters. 288 6.4. mplsInSegmentPerfTable 290 The MPLS In-Segment Performance Table has objects to measure the 291 performance of an incoming segment configured on an LSR. It is an 292 AUGMENT to mplsInSegmentTable. High capacity counters are 293 provided for objects that are likely to wrap around quickly on 294 high-speed interfaces. 296 6.5. mplsOutSegmentTable 298 The Out-Segment Table contains a description of the outgoing MPLS 299 segments at an LSR and their associated parameters. 301 6.6. mplsOutSegmentPerfTable 303 The MPLS Out-Segment Table contains objects to measure the 304 performance of an outgoing segment configured on an LSR. It is an 305 AUGMENT to mplsOutSegmentTable. High capacity counters are 306 provided for objects that are likely to wrap around quickly on 307 high-speed interfaces. 309 6.7. mplsXCTable 311 mplsXCTable specifies information for switching between segments. 312 It supports point-to-point, point-to-multipoint and multipoint-to- 313 point connections. 315 6.8. mplsLabelStackTable 317 mplsLabelStackTable specifies the label stack to be pushed onto a 318 packet, beneath the top label. Entries to this table are referred 319 to from mplsXCTable. 321 6.9. mplsTSpecTable 323 mplsTSpecTable contains objects for specifying the traffic 324 parameters of in and out segments. Entries in this table are 325 referred to from mplsInSegmentTable and mplsOutSegmentTable. 327 7. Specifying the Segments of an LSR 329 Suppose that we want to manually create a best-effort bi- 330 directional LSP, consisting of an in-segment and an out-segment on 331 an LSR (with no label stack beneath the top label on the outgoing 332 labeled packets). The following rows and corresponding objects 333 need to be created to do this. 335 First, the in-segment and the out-segment are created with the 336 appropriate traffic parameters. 338 In mplsInSegmentTable: 339 { 340 mplsInSegmentIfIndex = i1, 341 mplsInSegmentLabel = l1, 342 mplsInSegmentNPop = 1, 343 mplsInSegmentTSpecIndex = 0, 344 mplsInSegmentRowStatus = createAndGo(3) 345 } 347 In mplsOutSegmentTable: 348 { 349 mplsOutSegmentIndex = o, 350 mplsOutSegmentIfIndex = i2, 351 mplsOutSegmentPushTopLabel = true(1), 352 mplsOutSegmentTopLabel = l2, 353 mplsOutSegmentTSpecIndex = 0, 354 mplsOutSegmentRowStatus = createAndGo(3) 355 } 357 Next, two cross-connect entries associating these two segments by 358 sharing the same mplsXCIndex are created. 360 In mplsXCTable, for the in-segment: 361 { 362 mplsXCIndex = x, 363 mplsInSegmentIfIndex = i1, 364 mplsInSegmentLabel = l1, 365 mplsOutSegmentIndex = 0, 366 mplsLabelStackIndex = 0, 367 mplsXCRowStatus = createAndGo(3) 368 } 370 In mplsXCTable, for the out-segment: 371 { 372 mplsXCIndex = x, 373 mplsInSegmentIfIndex = 0, 374 mplsInSegmentLabel = 0, 375 mplsOutSegmentIndex = o, 376 mplsXCLabelStackIndex = 0, 377 mplsXCRowStatus = createAndGo(3) 378 } 380 Note that the objects mplsInSegmentXCIndex and 381 mplsOutSegmentXCIndex will automatically get populated with the 382 value "x" when these segments are referred to from the 383 corresponding cross-connect entries. 385 8. MPLS Label Switch Router MIB Definitions 387 MPLS-LSR-MIB DEFINITIONS ::= BEGIN 389 IMPORTS 390 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 391 experimental, Integer32, Counter32, Counter64, Gauge32, IpAddress 392 FROM SNMPv2-SMI 393 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 394 FROM SNMPv2-CONF 395 TEXTUAL-CONVENTION, TruthValue, RowStatus 396 FROM SNMPv2-TC 397 ifIndex, InterfaceIndex, InterfaceIndexOrZero 398 FROM IF-MIB 399 BitRate, BurstSize 400 FROM INTEGRATED-SERVICES-MIB; 402 mplsLsrMIB MODULE-IDENTITY 403 LAST-UPDATED "9906161200Z" -- 16 June 1999 12:00:00 EST 404 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 405 CONTACT-INFO 406 " Cheenu Srinivasan 407 Postal: Tachion Network Technologies 408 2 Meridian Road 409 Eatontown, NJ 07724 410 Tel: +1 732 542 7750 x234 411 Email: cheenu@tachion.com 413 Arun Viswanathan 414 Postal: Lucent Technologies 415 4D537, 101 Crawfords Corner Road 416 Holmdel, NJ 07733 417 Tel: +1 732 332 5163 418 Email: arunv@lucent.com" 419 DESCRIPTION 420 "Proposed MIB module for MPLS Label Switch Router. 421 See: Rosen, E., Viswanathan, A., and R. Callon, 422 Multiprotocol Label Switching Architecture, Internet 423 Draft , February 1999." 424 ::= { experimental 96 } 426 -- Textual Conventions. 428 MplsLsrIANAAddrFamily ::= TEXTUAL-CONVENTION 429 STATUS current 430 DESCRIPTION 431 "An address family. Values are defined in RFC 1700 - 432 Assigned Numbers. All values may not be relevant in 433 all contexts when used in this MIB, but are included 434 for completeness." 435 REFERENCE 436 "RFC 1700 - Assigned Numbers, Reynolds and Postel, 437 Oct. 1994" 438 SYNTAX INTEGER { 439 other(0), 440 ipv4(1), 441 ipv6(2), 442 nsap(3), 443 hdlc(4), 444 bbn1822(5), 445 ieee802(6), 446 e163(7), 447 e164(8), 448 f69(9), 449 x121(10), 450 ipx(11), 451 appleTalk(12), 452 decnetIV(13), 453 banyanVines(14), 454 e164WithNsap(15) 455 } 457 -- An MPLS label. 458 MplsLabel ::= TEXTUAL-CONVENTION 459 STATUS current 460 DESCRIPTION 461 "Represents an MPLS label. Note that the contents of 462 a label field are interpreted in an interface-type 463 specific fashion. For example, the label carried in 464 the MPLS shim header is 20 bits wide and the top 12 465 bits must be zero. The frame relay label can be 466 either 10, 17 or 23 bits wide depending on the size 467 of the DLCI field size and the top 22, 15, or 9 bits 468 must be zero, respectively. For an ATM interface, 469 the lowermost 16 bits are interpreted as the VCI, 470 the next 8 bits as the VPI and the remaining bits 471 must be zero. Also note the permissible label 472 values are also a function of the interface type. 473 For example, the value 3 has special semantics in 474 the control plane for an MPLS shim header label and 475 is not a valid label value in the datapath." 476 REFERENCE 477 "1. MPLS Label Stack Encoding, Rosen et al, draft- 478 ietf-mpls-label-encaps-04.txt, April 1999. 479 2. Use of Label Switching on Frame Relay Networks, 480 Conta et al, draft-ietf-mpls-fr-03.txt, Nov. 1998." 481 SYNTAX Integer32 483 Ipv6Address ::= TEXTUAL-CONVENTION 484 STATUS current 485 DESCRIPTION 486 "IPv6 address." 487 SYNTAX OCTET STRING (SIZE(16)) 489 -- Top level components of this MIB. 491 -- tables, scalars 492 mplsLsrObjects OBJECT IDENTIFIER ::= { mplsLsrMIB 1 } 493 -- traps 494 mplsLsrNotifications OBJECT IDENTIFIER ::= { mplsLsrMIB 2 } 495 -- conformance 496 mplsLsrConformance OBJECT IDENTIFIER ::= { mplsLsrMIB 3 } 498 -- MPLS Interface Configuration Table. 500 mplsInterfaceConfTable OBJECT-TYPE 501 SYNTAX SEQUENCE OF MplsInterfaceConfEntry 502 MAX-ACCESS not-accessible 503 STATUS current 504 DESCRIPTION 505 "This table specifies per-interface MPLS capability 506 and associated information." 507 ::= { mplsLsrObjects 1 } 509 mplsInterfaceConfEntry OBJECT-TYPE 510 SYNTAX MplsInterfaceConfEntry 511 MAX-ACCESS not-accessible 512 STATUS current 513 DESCRIPTION 514 "An entry in this table is created by an LSR for 515 every interface capable of supporting MPLS and 516 represents the label space of that interface. A row 517 with index 0 represents the global label space." 518 INDEX { mplsInterfaceConfIndex } 519 ::= { mplsInterfaceConfTable 1 } 521 MplsInterfaceConfEntry ::= SEQUENCE { 522 mplsInterfaceConfIndex InterfaceIndexOrZero, 523 mplsInterfaceLabelMinIn MplsLabel, 524 mplsInterfaceLabelMaxIn MplsLabel, 525 mplsInterfaceLabelMinOut MplsLabel, 526 mplsInterfaceLabelMaxOut MplsLabel, 527 mplsInterfaceAdminStatus INTEGER, 528 mplsInterfaceOperStatus INTEGER 529 } 531 mplsInterfaceConfIndex OBJECT-TYPE 532 SYNTAX InterfaceIndexOrZero 533 MAX-ACCESS read-only 534 STATUS current 535 DESCRIPTION 536 "Index for this row of the table. A value of 0 537 indicates the global label space and this entry is 538 created by the LSR if it supports a global label 539 space. A non-zero index is also the interface 540 index, ifIndex, for the corresponding interface 541 entry in ifTable." 542 REFERENCE 543 "RFC 2233 - The Interfaces Group MIB using SMIv2, 544 McCloghrie and Kastenholtz, Nov. 1997" 545 ::= { mplsInterfaceConfEntry 1 } 547 mplsInterfaceLabelMinIn OBJECT-TYPE 548 SYNTAX MplsLabel 549 MAX-ACCESS read-only 550 STATUS current 551 DESCRIPTION 552 "Minimum value of MPLS label that this LSR is willing 553 to receive on this interface." 554 ::= { mplsInterfaceConfEntry 2 } 556 mplsInterfaceLabelMaxIn OBJECT-TYPE 557 SYNTAX MplsLabel 558 MAX-ACCESS read-only 559 STATUS current 560 DESCRIPTION 561 "Maximum value of MPLS label that this LSR is willing 562 to receive on this interface." 563 ::= { mplsInterfaceConfEntry 3 } 565 mplsInterfaceLabelMinOut OBJECT-TYPE 566 SYNTAX MplsLabel 567 MAX-ACCESS read-only 568 STATUS current 569 DESCRIPTION 570 "Minimum value of MPLS label that this LSR is willing 571 to send on this interface." 572 ::= { mplsInterfaceConfEntry 4 } 574 mplsInterfaceLabelMaxOut OBJECT-TYPE 575 SYNTAX MplsLabel 576 MAX-ACCESS read-only 577 STATUS current 578 DESCRIPTION 579 "Maximum value of MPLS label that this LSR is willing 580 to send on this interface." 581 ::= { mplsInterfaceConfEntry 5 } 583 mplsInterfaceAdminStatus OBJECT-TYPE 584 SYNTAX INTEGER { 585 up(1), -- enable MPLS on this interface 586 down(2), -- disable MPLS on this interface 587 testing(3) -- in some test mode 588 } 589 MAX-ACCESS read-write 590 STATUS current 591 DESCRIPTION 592 "Indicates the administrator's intent as to whether 593 MPLS should be enabled or disabled on this 594 interface." 595 DEFVAL { down } 596 ::= { mplsInterfaceConfEntry 6 } 598 mplsInterfaceOperStatus OBJECT-TYPE 599 SYNTAX INTEGER { 600 up(1), -- ready to pass packets 601 down(2), 602 testing(3), -- in some test mode 603 unknown(4), -- status cannot be determined for some 604 -- reason 605 dormant(5), 606 notPresent(6), -- some component is missing 607 lowerLayerNotPresent(7) 608 -- down due to the state of 609 -- lower layer interfaces 610 } 611 MAX-ACCESS read-only 612 STATUS current 613 DESCRIPTION 614 "Indicates the actual status of MPLS on this 615 interface." 616 ::= { mplsInterfaceConfEntry 7 } 618 -- End of mplsInterfaceConfTable 619 -- MPLS Interface Performance Table. 621 mplsInterfacePerfTable OBJECT-TYPE 622 SYNTAX SEQUENCE OF MplsInterfacePerfEntry 623 MAX-ACCESS not-accessible 624 STATUS current 625 DESCRIPTION 626 "This table provides per-interface MPLS performance 627 information." 628 ::= { mplsLsrObjects 2 } 630 mplsInterfacePerfEntry OBJECT-TYPE 631 SYNTAX MplsInterfacePerfEntry 632 MAX-ACCESS not-accessible 633 STATUS current 634 DESCRIPTION 635 "An entry in this table is created by the LSR for 636 every interface capable of supporting MPLS. Its is 637 an extension to mplsInterfaceConfEntry." 638 AUGMENTS { mplsInterfaceConfEntry } 639 ::= { mplsInterfacePerfTable 1 } 641 MplsInterfacePerfEntry ::= SEQUENCE { 642 -- incoming direction 643 mplsInterfaceInLabelsUsed Gauge32, 644 mplsInterfaceInOctets Counter32, 645 mplsInterfaceInPackets Counter32, 646 mplsInterfaceInErrors Counter32, 647 mplsInterfaceInDiscards Counter32, 648 mplsInterfaceFailedLabelLookup Counter32, 650 -- outgoing direction 651 mplsInterfaceOutLabelsUsed Gauge32, 652 mplsInterfaceOutOctets Counter32, 653 mplsInterfaceOutPackets Counter32, 654 mplsInterfaceOutErrors Counter32, 655 mplsInterfaceOutDiscards Counter32, 657 -- high capacity counters 658 mplsInterfaceInHCOctets Counter64, 659 mplsInterfaceOutHCOctets Counter64 660 } 662 mplsInterfaceInLabelsUsed OBJECT-TYPE 663 SYNTAX Gauge32 664 MAX-ACCESS read-only 665 STATUS current 666 DESCRIPTION 667 "The number of labels that are in use at this point 668 on this interface in the incoming direction." 669 ::= { mplsInterfacePerfEntry 1 } 671 mplsInterfaceInOctets OBJECT-TYPE 672 SYNTAX Counter32 673 MAX-ACCESS read-only 674 STATUS current 675 DESCRIPTION 676 "The number of octets that have been received in 677 labeled packets on this interface." 678 ::= { mplsInterfacePerfEntry 2 } 680 mplsInterfaceInPackets OBJECT-TYPE 681 SYNTAX Counter32 682 MAX-ACCESS read-only 683 STATUS current 684 DESCRIPTION 685 "The number of labeled packets that have been 686 received on this interface." 687 ::= { mplsInterfacePerfEntry 3 } 689 mplsInterfaceInErrors OBJECT-TYPE 690 SYNTAX Counter32 691 MAX-ACCESS read-only 692 STATUS current 693 DESCRIPTION 694 "The number of labeled packets that have been 695 received on this interface that were errored." 696 ::= { mplsInterfacePerfEntry 4 } 698 mplsInterfaceInDiscards OBJECT-TYPE 699 SYNTAX Counter32 700 MAX-ACCESS read-only 701 STATUS current 702 DESCRIPTION 703 "The number of labeled packets that have been 704 received on this interface that were discarded." 705 ::= { mplsInterfacePerfEntry 5 } 707 mplsInterfaceFailedLabelLookup OBJECT-TYPE 708 SYNTAX Counter32 709 MAX-ACCESS read-only 710 STATUS current 711 DESCRIPTION 712 "The number of labeled packets that have been 713 received on this interface that were discarded 714 because no matching entries were found in 715 mplsInSegmentTable." 716 ::= { mplsInterfacePerfEntry 6 } 718 mplsInterfaceOutLabelsUsed OBJECT-TYPE 719 SYNTAX Gauge32 720 MAX-ACCESS read-only 721 STATUS current 722 DESCRIPTION 723 "The number of labels that are in use at this point 724 on this interface in the outgoing direction." 725 ::= { mplsInterfacePerfEntry 7 } 727 mplsInterfaceOutOctets OBJECT-TYPE 728 SYNTAX Counter32 729 MAX-ACCESS read-only 730 STATUS current 731 DESCRIPTION 732 "The number of octets that have been sent as labeled 733 packets on this interface." 734 ::= { mplsInterfacePerfEntry 8 } 736 mplsInterfaceOutPackets OBJECT-TYPE 737 SYNTAX Counter32 738 MAX-ACCESS read-only 739 STATUS current 740 DESCRIPTION 741 "The number of labeled packets that have been sent on 742 this interface." 743 ::= { mplsInterfacePerfEntry 9 } 745 mplsInterfaceOutErrors OBJECT-TYPE 746 SYNTAX Counter32 747 MAX-ACCESS read-only 748 STATUS current 749 DESCRIPTION 750 "The number of labeled packets that could not be sent 751 on this interface due to errors." 752 ::= { mplsInterfacePerfEntry 10 } 754 mplsInterfaceOutDiscards OBJECT-TYPE 755 SYNTAX Counter32 756 MAX-ACCESS read-only 757 STATUS current 758 DESCRIPTION 759 "The number of outgoing labeled packets on this 760 interface that had to be discarded due to errors or 761 other conditions such as buffer overflows." 762 ::= { mplsInterfacePerfEntry 11 } 764 mplsInterfaceInHCOctets OBJECT-TYPE 765 SYNTAX Counter64 766 MAX-ACCESS read-only 767 STATUS current 768 DESCRIPTION 769 "The number of octets that have been received in 770 labeled packets on this interface. This is the 64 771 bit version of mplsInterfaceInOctets." 772 ::= { mplsInterfacePerfEntry 15 } 774 mplsInterfaceOutHCOctets OBJECT-TYPE 775 SYNTAX Counter64 776 MAX-ACCESS read-only 777 STATUS current 778 DESCRIPTION 779 "The number of octets that have been sent in labeled 780 packets on this interface. This is the 64 bit 781 version of mplsInterfaceOutOctets." 782 ::= { mplsInterfacePerfEntry 16 } 784 -- End of mplsInterfacePerfTable 786 -- In-segment table. 788 mplsInSegmentTable OBJECT-TYPE 789 SYNTAX SEQUENCE OF MplsInSegmentEntry 790 MAX-ACCESS not-accessible 791 STATUS current 792 DESCRIPTION 793 "This table contains a description of the incoming 794 segments to a LSR." 795 ::= { mplsLsrObjects 3 } 797 mplsInSegmentEntry OBJECT-TYPE 798 SYNTAX MplsInSegmentEntry 799 MAX-ACCESS not-accessible 800 STATUS current 801 DESCRIPTION 802 "An entry in this table represents one incoming 803 segment. An entry can be created by a network 804 administrator or by an SNMP agent as instructed by 805 LDP or RSVP. It is indexed by the incoming 806 interface index and (top) label. Note that some of 807 the segments are associated with a tunnel, the 808 traffic parameters of these rows are supported as 809 read-only objects and their modification can be done 810 only via the tunnel table, mplsTunnelTable. This 811 issue will be addressed more naturally when 812 ownership related objects are introduced into these 813 tables." 814 REFERENCE 815 "MPLS Traffic Engineering Management Information Base 816 Using SMIv2, Srinivasan and Viswanathan, draft-ietf- 817 mpls-te-mib-01.txt, June 1999." 818 INDEX { mplsInSegmentIfIndex, mplsInSegmentLabel } 819 ::= { mplsInSegmentTable 1 } 821 MplsInSegmentEntry ::= SEQUENCE { 822 mplsInSegmentIfIndex InterfaceIndex, 823 mplsInSegmentLabel MplsLabel, 824 mplsInSegmentNPop Integer32, 825 mplsInSegmentAddrFamily MplsLsrIANAAddrFamily, 826 mplsInSegmentXCIndex Integer32, 827 mplsInSegmentTSpecIndex Unsigned32, 828 mplsInSegmentAdminStatus INTEGER, 829 mplsInSegmentOperStatus INTEGER, 830 mplsInSegmentRowStatus RowStatus 831 } 833 mplsInSegmentIfIndex OBJECT-TYPE 834 SYNTAX InterfaceIndexOrZero 835 MAX-ACCESS read-create 836 STATUS current 837 DESCRIPTION 838 "Incoming interface index. A value of zero 839 represents an incoming label from the per-platform 840 label space. In this case, the mplsInSegmentLabel 841 is interpreted to be an MPLS-type label." 842 ::= { mplsInSegmentEntry 1 } 844 mplsInSegmentLabel OBJECT-TYPE 845 SYNTAX MplsLabel 846 MAX-ACCESS not-accessible 847 STATUS current 848 DESCRIPTION 849 "The incoming label." 850 ::= { mplsInSegmentEntry 2 } 852 mplsInSegmentNPop OBJECT-TYPE 853 SYNTAX Integer32 854 MAX-ACCESS read-create 855 STATUS current 856 DESCRIPTION 857 "The number of labels to pop from the incoming 858 packet. Normally only the top label is popped 859 (based on which all switching decisions are taken)." 860 DEFVAL { 1 } 861 ::= { mplsInSegmentEntry 3 } 863 mplsInSegmentAddrFamily OBJECT-TYPE 864 SYNTAX MplsLsrIANAAddrFamily 865 MAX-ACCESS read-create 866 STATUS current 867 DESCRIPTION 868 "The IANA address family of the incoming packet. A 869 value of zero indicates that the family type is 870 either unknown or undefined (which could happen for 871 example when streams of different types are merged 872 in a multipoint-to-point connection)." 873 REFERENCE 874 "RFC 1700 - Assigned Numbers, Reynolds and Postel, 875 October 1994." 876 DEFVAL { 0 } 877 ::= { mplsInSegmentEntry 4 } 879 mplsInSegmentXCIndex OBJECT-TYPE 880 SYNTAX Integer32 881 MAX-ACCESS read-only 882 STATUS current 883 DESCRIPTION 884 "Index into mplsXCTable to identify which cross- 885 connect entry this segment is part of. A value of 886 zero indicates that it is not being referred to by 887 any cross-connect entry." 888 DEFVAL { 0 } 889 ::= { mplsInSegmentEntry 5 } 891 mplsInSegmentTSpecIndex OBJECT-TYPE 892 SYNTAX Unsigned32 893 MAX-ACCESS read-create 894 STATUS current 895 DESCRIPTION 896 "Pointer into mplsTSpecTable indicating the TSpec to 897 be assigned for this segment. A value of zero 898 indicates best-effort treatment. Two or more 899 segments can indicate resource sharing by pointing 900 to the same entry in mplsTSpecTable." 901 DEFVAL { 0 } 902 ::= { mplsInSegmentEntry 6 } 904 mplsInSegmentAdminStatus OBJECT-TYPE 905 SYNTAX INTEGER { 906 up(1), -- ready to pass packets 907 down(2), 908 testing(3) -- in some test mode 909 } 910 MAX-ACCESS read-create 911 STATUS current 912 DESCRIPTION 913 "Desired status of this segment." 914 ::= { mplsInSegmentEntry 7 } 916 mplsInSegmentOperStatus OBJECT-TYPE 917 SYNTAX INTEGER { 918 up(1), -- ready to pass packets 919 down(2), 920 testing(3), -- in some test mode 921 unknown(4), -- status cannot be determined for 922 -- some reason 923 dormant(5), 924 notPresent(6), -- some component is missing 925 lowerLayerNotPresent(7) 926 -- down due to the state of 927 -- lower layer interfaces 928 } 929 MAX-ACCESS read-only 930 STATUS current 931 DESCRIPTION 932 "The operational status of this segment." 933 ::= { mplsInSegmentEntry 8 } 935 mplsInSegmentRowStatus OBJECT-TYPE 936 SYNTAX RowStatus 937 MAX-ACCESS read-create 938 STATUS current 939 DESCRIPTION 940 "For creating, modifying, and deleting this row." 941 ::= { mplsInSegmentEntry 9 } 943 -- End of mplsInSegmentTable 945 -- In-segment performance table. 947 mplsInSegmentPerfTable OBJECT-TYPE 948 SYNTAX SEQUENCE OF MplsInSegmentPerfEntry 949 MAX-ACCESS not-accessible 950 STATUS current 951 DESCRIPTION 952 "This table contains statistical information about 953 incoming MPLS segments to an LSR." 954 ::= { mplsLsrObjects 4 } 956 mplsInSegmentPerfEntry OBJECT-TYPE 957 SYNTAX MplsInSegmentPerfEntry 958 MAX-ACCESS not-accessible 959 STATUS current 960 DESCRIPTION 961 "An entry in this table contains statistical 962 information about one incoming segment configured in 963 mplsInSegmentTable." 964 AUGMENTS { mplsInSegmentEntry } 965 ::= { mplsInSegmentPerfTable 1 } 967 MplsInSegmentPerfEntry ::= SEQUENCE { 968 mplsInSegmentOctets Counter32, 969 mplsInSegmentPackets Counter32, 970 mplsInSegmentErrors Counter32, 971 mplsInSegmentDiscards Counter32, 973 -- high capacity counter 974 mplsInSegmentHCOctets Counter64 975 } 977 mplsInSegmentOctets OBJECT-TYPE 978 SYNTAX Counter32 979 MAX-ACCESS read-only 980 STATUS current 981 DESCRIPTION 982 "Total number of octets received." 983 ::= { mplsInSegmentPerfEntry 1 } 985 mplsInSegmentPackets OBJECT-TYPE 986 SYNTAX Counter32 987 MAX-ACCESS read-only 988 STATUS current 989 DESCRIPTION 990 "Total number of packets received." 991 ::= { mplsInSegmentPerfEntry 2 } 993 mplsInSegmentErrors OBJECT-TYPE 994 SYNTAX Counter32 995 MAX-ACCESS read-only 996 STATUS current 997 DESCRIPTION 998 "Number of errored packets received." 999 ::= { mplsInSegmentPerfEntry 3 } 1001 mplsInSegmentDiscards OBJECT-TYPE 1002 SYNTAX Counter32 1003 MAX-ACCESS read-only 1004 STATUS current 1005 DESCRIPTION 1006 "Number of packets received that had to be dropped 1007 either because of errors or for other reasons such 1008 as buffer overflows." 1009 ::= { mplsInSegmentPerfEntry 4 } 1011 mplsInSegmentHCOctets OBJECT-TYPE 1012 SYNTAX Counter32 1013 MAX-ACCESS read-only 1014 STATUS current 1015 DESCRIPTION 1016 "Total number of octets received. This is the 64 bit 1017 version of mplsInSegmentOctets." 1018 ::= { mplsInSegmentPerfEntry 5 } 1020 -- End of mplsInSegmentPerfTable. 1022 -- Out-segment table. 1024 mplsOutSegmentTable OBJECT-TYPE 1025 SYNTAX SEQUENCE OF MplsOutSegmentEntry 1026 MAX-ACCESS not-accessible 1027 STATUS current 1028 DESCRIPTION 1029 "This table contains a description of the outgoing 1030 segments from an LSR." 1031 ::= { mplsLsrObjects 5 } 1033 mplsOutSegmentEntry OBJECT-TYPE 1034 SYNTAX MplsOutSegmentEntry 1035 MAX-ACCESS not-accessible 1036 STATUS current 1037 DESCRIPTION 1038 "An entry in this table represents one outgoing 1039 segment. An entry can be created by a network 1040 administrator or by an SNMP agent as instructed by 1041 LDP or RSVP. Note that some of the segments are 1042 associated with a tunnel, the traffic parameters of 1043 these rows are supported as read-only objects and 1044 their modification can be done only via the tunnel 1045 table, mplsTunnelTable. This issue will be addressed 1046 more naturally when ownership related objects are 1047 introduced into these tables." 1048 REFERENCE 1049 "MPLS Traffic Engineering Management Information Base 1050 Using SMIv2, Srinivasan and Viswanathan, draft-ietf- 1051 mpls-te-mib-01.txt, June 1999." 1052 INDEX { mplsOutSegmentIndex } 1053 ::= { mplsOutSegmentTable 1 } 1055 MplsOutSegmentEntry ::= SEQUENCE { 1056 mplsOutSegmentIndex Integer32, 1057 mplsOutSegmentIfIndex InterfaceIndex, 1058 mplsOutSegmentPushTopLabel TruthValue, 1059 mplsOutSegmentTopLabel MplsLabel, 1060 mplsOutSegmentNextHopIpAddrType INTEGER, 1061 mplsOutSegmentNextHopIpv4Addr IpAddress, 1062 mplsOutSegmentNextHopIpv6Addr Ipv6Address, 1063 mplsOutSegmentXCIndex Integer32, 1064 mplsOutSegmentTSpecIndex Unsigned32, 1065 mplsOutSegmentAdminStatus INTEGER, 1066 mplsOutSegmentOperStatus INTEGER, 1067 mplsOutSegmentRowStatus RowStatus 1068 } 1070 mplsOutSegmentIndex OBJECT-TYPE 1071 SYNTAX Integer32 1072 MAX-ACCESS not-accessible 1073 STATUS current 1074 DESCRIPTION 1075 "Unique index for this row. While a value of 0 is 1076 not valid as an index for this row it can be 1077 supplied as a valid value to index mplsXCTable to 1078 access entries for which no out-segment has been 1079 configured." 1080 ::= { mplsOutSegmentEntry 1 } 1082 mplsOutSegmentIfIndex OBJECT-TYPE 1083 SYNTAX InterfaceIndex 1084 MAX-ACCESS read-create 1085 STATUS current 1086 DESCRIPTION 1087 "Interface index of the outgoing interface." 1088 ::= { mplsOutSegmentEntry 2 } 1090 mplsOutSegmentPushTopLabel OBJECT-TYPE 1091 SYNTAX TruthValue 1092 MAX-ACCESS read-create 1093 STATUS current 1094 DESCRIPTION 1095 "Whether a top label should be pushed onto the 1096 outgoing packet's label stack. Its value has to be 1097 true if the outgoing interface is ATM (which does 1098 not support `pop-and-go') or if it is a tunnel 1099 origination. Note also that the case where 1100 mplsOutSegmentPushTopLabel is set to false but the 1101 cross-connect entry that refers to this out-segment 1102 has a non-zero mplsLabelStackIndex is an error which 1103 the LSR should ensure doesn't happen." 1104 ::= { mplsOutSegmentEntry 3 } 1106 mplsOutSegmentTopLabel OBJECT-TYPE 1107 SYNTAX MplsLabel 1108 MAX-ACCESS read-create 1109 STATUS current 1110 DESCRIPTION 1111 "If mplsOutSegmentPushTopLabel is true then this is 1112 the label that should be pushed onto the outgoing 1113 packet's label stack. Note that the contents of the 1114 label field can be interpreted in an outgoing 1115 interface specific fashion. For example, the label 1116 carried in the MPLS shim header is 20 bits wide and 1117 the top 12 bits must be zero. The Frame Relay label 1118 is 24 bits wide and the top 8 bits must be zero. 1119 For ATM interfaces the lowermost 16 bits are 1120 interpreted as the VCI, the next 8 bits as the VPI 1121 and the remaining bits must be zero." 1122 ::= { mplsOutSegmentEntry 4 } 1124 mplsOutSegmentNextHopIpAddrType OBJECT-TYPE 1125 SYNTAX INTEGER { none (1), ipV4 (2), ipV6 (3) } 1126 MAX-ACCESS read-create 1127 STATUS current 1128 DESCRIPTION 1129 "Whether the next hop address is IPv4 or IPv6. A 1130 value of none (1) is valid (only) when the outgoing 1131 interface is of type point-to-point." 1132 DEFVAL { none } 1133 ::= { mplsOutSegmentEntry 5 } 1135 mplsOutSegmentNextHopIpv4Addr OBJECT-TYPE 1136 SYNTAX IpAddress 1137 MAX-ACCESS read-create 1138 STATUS current 1139 DESCRIPTION 1140 "IPv4 Address of the next hop. Its value is 1141 significant only when 1142 mplsOutSegmentNextHopIpAddrType is ipV4 (2), 1143 otherwise it should return a value of 0." 1144 ::= { mplsOutSegmentEntry 6 } 1146 mplsOutSegmentNextHopIpv6Addr OBJECT-TYPE 1147 SYNTAX Ipv6Address 1148 MAX-ACCESS read-create 1149 STATUS current 1150 DESCRIPTION 1151 "IPv6 address of the next hop. Its value is 1152 significant only when 1153 mplsOutSegmentNextHopIpAddrType is ipV6 (3), 1154 otherwise it should return a value of 0." 1155 ::= { mplsOutSegmentEntry 7 } 1157 mplsOutSegmentXCIndex OBJECT-TYPE 1158 SYNTAX Integer32 1159 MAX-ACCESS read-create 1160 STATUS current 1161 DESCRIPTION 1162 "Index into mplsXCTable to identify which cross- 1163 connect entry this segment is part of. A value of 1164 zero indicates that it is not being referred to by 1165 any cross-connect entry." 1166 DEFVAL { 0 } 1167 ::= { mplsOutSegmentEntry 8 } 1169 mplsOutSegmentTSpecIndex OBJECT-TYPE 1170 SYNTAX Unsigned32 1171 MAX-ACCESS read-create 1172 STATUS current 1173 DESCRIPTION 1174 "Pointer into mplsTSpecTable indicating the TSpec to 1175 be assigned for this segment. A value of zero 1176 indicates best-effort treatment. Two or more 1177 segments can indicate resource sharing by pointing 1178 to the same entry in mplsTSpecTable." 1179 DEFVAL { 0 } 1180 ::= { mplsOutSegmentEntry 9 } 1182 mplsOutSegmentAdminStatus OBJECT-TYPE 1183 SYNTAX INTEGER { 1184 up(1), -- ready to pass packets 1185 down(2), 1186 testing(3) -- in some test mode 1187 } 1188 MAX-ACCESS read-create 1189 STATUS current 1190 DESCRIPTION 1191 "Desired status of this segment." 1192 ::= { mplsOutSegmentEntry 10 } 1194 mplsOutSegmentOperStatus OBJECT-TYPE 1195 SYNTAX INTEGER { 1196 up(1), -- ready to pass packets 1197 down(2), 1198 testing(3), -- in some test mode 1199 unknown(4), -- status cannot be determined for 1200 -- some reason 1201 dormant(5), 1202 notPresent(6), -- some component is missing 1203 lowerLayerNotPresent(7) 1204 -- down due to the state of 1205 -- lower layer interfaces 1206 } 1207 MAX-ACCESS read-only 1208 STATUS current 1209 DESCRIPTION 1210 "The operational status of this segment." 1211 ::= { mplsOutSegmentEntry 11 } 1213 mplsOutSegmentRowStatus OBJECT-TYPE 1214 SYNTAX RowStatus 1215 MAX-ACCESS read-create 1216 STATUS current 1217 DESCRIPTION 1218 "For creating, modifying, and deleting this row." 1219 ::= { mplsOutSegmentEntry 12 } 1221 -- End of mplsOutSegmentTable 1223 -- Out-segment performance table. 1225 mplsOutSegmentPerfTable OBJECT-TYPE 1226 SYNTAX SEQUENCE OF MplsOutSegmentPerfEntry 1227 MAX-ACCESS not-accessible 1228 STATUS current 1229 DESCRIPTION 1230 "This table contains statistical information about 1231 incoming segments to an LSR." 1232 ::= { mplsLsrObjects 6 } 1234 mplsOutSegmentPerfEntry OBJECT-TYPE 1235 SYNTAX MplsOutSegmentPerfEntry 1236 MAX-ACCESS not-accessible 1237 STATUS current 1238 DESCRIPTION 1239 "An entry in this table contains statistical 1240 information about one incoming segment configured in 1241 mplsOutSegmentTable." 1242 AUGMENTS { mplsOutSegmentEntry } 1243 ::= { mplsOutSegmentPerfTable 1 } 1245 MplsOutSegmentPerfEntry ::= SEQUENCE { 1246 mplsOutSegmentOctets Counter32, 1247 mplsOutSegmentPackets Counter32, 1248 mplsOutSegmentErrors Counter32, 1249 mplsOutSegmentDiscards Counter32, 1251 -- HC counter 1252 mplsOutSegmentHCOctets Counter64 1253 } 1255 mplsOutSegmentOctets OBJECT-TYPE 1256 SYNTAX Counter32 1257 MAX-ACCESS read-only 1258 STATUS current 1259 DESCRIPTION 1260 "Total number of octets sent." 1261 ::= { mplsOutSegmentPerfEntry 1 } 1263 mplsOutSegmentPackets OBJECT-TYPE 1264 SYNTAX Counter32 1265 MAX-ACCESS read-only 1266 STATUS current 1267 DESCRIPTION 1268 "Total number of packets sent." 1269 ::= { mplsOutSegmentPerfEntry 2 } 1271 mplsOutSegmentErrors OBJECT-TYPE 1272 SYNTAX Counter32 1273 MAX-ACCESS read-only 1274 STATUS current 1275 DESCRIPTION 1276 "Number of packets that could not be sent due to 1277 errors." 1278 ::= { mplsOutSegmentPerfEntry 3 } 1280 mplsOutSegmentDiscards OBJECT-TYPE 1281 SYNTAX Counter32 1282 MAX-ACCESS read-only 1283 STATUS current 1284 DESCRIPTION 1285 "Number of outgoing packets that had to be dropped 1286 either because of errors or for other reasons such 1287 as buffer overflows." 1288 ::= { mplsOutSegmentPerfEntry 4 } 1290 mplsOutSegmentHCOctets OBJECT-TYPE 1291 SYNTAX Counter64 1292 MAX-ACCESS read-only 1293 STATUS current 1294 DESCRIPTION 1295 "Total number of octets sent. This is the 64 bit 1296 version of mplsOutSegmentOctets." 1297 ::= { mplsOutSegmentPerfEntry 5 } 1299 -- End of mplsOutSegmentPerfTable. 1301 -- Cross-connect table. 1303 mplsXCTable OBJECT-TYPE 1304 SYNTAX SEQUENCE OF MplsXCEntry 1305 MAX-ACCESS not-accessible 1306 STATUS current 1307 DESCRIPTION 1308 "This table specifies information for switching 1309 between LSP segments. It supports point-to-point, 1310 point-to-multipoint and multipoint-to-point 1311 connections. mplsLabelStackTable specifies the 1312 label stack information for a cross-connect LSR and 1313 is referred to from mplsXCTable." 1314 ::= { mplsLsrObjects 7 } 1316 mplsXCEntry OBJECT-TYPE 1317 SYNTAX MplsXCEntry 1318 MAX-ACCESS not-accessible 1319 STATUS current 1320 DESCRIPTION 1321 "A row in this table represents one cross-connect 1322 entry. It is indexed by the following objects: 1324 - cross-connect index mplsXCIndex that uniquely 1325 identifies a group of cross-connect entries 1326 - interface index of the in-segment, 1327 mplsInSegmentIfIndex 1328 - incoming label(s), mplsInSegmentLabel 1329 - out-segment index, mplsOutSegmentIndex 1331 Originating LSPs: 1332 These are represented by using the special 1333 combination of values mplsInSegmentIfIndex=0 and 1334 mplsInSegmentLabel=0 as indexes. In this case the 1335 mplsOutSegmentIndex MUST be non-zero. 1337 Terminating LSPs: 1338 These are represented by using the special value 1339 mplsOutSegmentIndex=0 as index. 1341 Special labels: 1342 Entries indexed by reserved MPLS label values 0 1343 through 15 imply terminating LSPs and MUST have 1344 mplsOutSegmentIndex=0. 1346 An entry can be created by a network administrator 1347 or by an SNMP agent as instructed by LDP or RSVP." 1348 INDEX { mplsXCIndex, mplsInSegmentIfIndex, 1349 mplsInSegmentLabel, mplsOutSegmentIndex } 1350 ::= { mplsXCTable 1 } 1352 MplsXCEntry ::= SEQUENCE { 1353 mplsXCIndex INTEGER, 1354 mplsXCLabelStackIndex Integer32, 1355 mplsXCCOS Integer32, 1356 mplsXCIsPersistent TruthValue, 1357 mplsXCAdminStatus INTEGER, 1358 mplsXCOperStatus INTEGER, 1359 mplsXCRowStatus RowStatus 1360 } 1362 mplsXCIndex OBJECT-TYPE 1363 SYNTAX INTEGER (0..4294967295) 1364 MAX-ACCESS not-accessible 1365 STATUS current 1366 DESCRIPTION 1367 "Primary index for the row identifying a group of 1368 cross-connect segments." 1369 ::= { mplsXCEntry 1 } 1371 mplsXCLabelStackIndex OBJECT-TYPE 1372 SYNTAX Integer32 1373 MAX-ACCESS read-create 1374 STATUS current 1375 DESCRIPTION 1376 "Primary index into mplsLabelStackTable identifying a 1377 stack of labels to be pushed beneath the top label. 1378 Note that the top label is identified in the out- 1379 segment which ensures that all the components of a 1380 multipoint-to-point connection have the same 1381 outgoing label. A value of 0 indicates that no 1382 labels are to be stacked beneath the top label." 1383 ::= { mplsXCEntry 2 } 1385 mplsXCCOS OBJECT-TYPE 1386 SYNTAX Integer32 1387 MAX-ACCESS read-create 1388 STATUS current 1389 DESCRIPTION 1390 "Value to override the incoming COS field with for a 1391 cross-connect or the value to assign to outgoing 1392 packets for an outgoing segment of a tunnel." 1393 ::= { mplsXCEntry 3 } 1395 mplsXCIsPersistent OBJECT-TYPE 1396 SYNTAX TruthValue 1397 MAX-ACCESS read-create 1398 STATUS current 1399 DESCRIPTION 1400 "Whether this cross-connect entry and associated in- 1401 and out-segments should be restored automatically 1402 after failures." 1403 DEFVAL { false } 1404 ::= { mplsXCEntry 4 } 1406 mplsXCAdminStatus OBJECT-TYPE 1407 SYNTAX INTEGER { 1408 up(1), -- ready to pass packets 1409 down(2), 1410 testing(3) -- in some test mode 1411 } 1412 MAX-ACCESS read-create 1413 STATUS current 1414 DESCRIPTION 1415 "Desired status of this segment." 1416 ::= { mplsXCEntry 5 } 1418 mplsXCOperStatus OBJECT-TYPE 1419 SYNTAX INTEGER { 1420 up(1), -- ready to pass packets 1421 down(2), 1422 testing(3), -- in some test mode 1423 unknown(4), -- status cannot be determined for 1424 -- some reason 1425 dormant(5), 1426 notPresent(6), -- some component is missing 1427 lowerLayerNotPresent(7) 1428 -- down due to the state of 1429 -- lower layer interfaces 1430 } 1431 MAX-ACCESS read-only 1432 STATUS current 1433 DESCRIPTION 1434 "The operational status of this segment." 1435 ::= { mplsXCEntry 6 } 1437 mplsXCRowStatus OBJECT-TYPE 1438 SYNTAX RowStatus 1439 MAX-ACCESS read-create 1440 STATUS current 1441 DESCRIPTION 1442 "For creating, modifying, and deleting this row." 1443 ::= { mplsXCEntry 7 } 1445 -- End of mplsXCTable 1447 -- Label stack table. 1449 mplsLabelStackTable OBJECT-TYPE 1450 SYNTAX SEQUENCE OF MplsLabelStackEntry 1451 MAX-ACCESS not-accessible 1452 STATUS current 1453 DESCRIPTION 1454 "This table specifies the label stack to be pushed 1455 onto a packet, beneath the top label. Entries into 1456 this table are referred to from mplsXCTable." 1457 ::= { mplsLsrObjects 8 } 1459 mplsLabelStackEntry OBJECT-TYPE 1460 SYNTAX MplsLabelStackEntry 1461 MAX-ACCESS not-accessible 1462 STATUS current 1463 DESCRIPTION 1464 "An entry in this table represents one label to be 1465 pushed onto an outgoing packets beneath the top 1466 label. An entry can be created by a network 1467 administrator or by an SNMP agent as instructed by 1468 LDP or RSVP." 1469 INDEX { mplsLabelStackIndex } 1470 ::= { mplsLabelStackTable 1 } 1472 MplsLabelStackEntry ::= SEQUENCE { 1473 mplsLabelStackIndex Integer32, 1474 mplsLabelStackLabelIndex Integer32, 1475 mplsLabelStackLabel MplsLabel, 1476 mplsLabelStackRowStatus RowStatus 1477 } 1479 mplsLabelStackIndex OBJECT-TYPE 1480 SYNTAX Integer32 1481 MAX-ACCESS not-accessible 1482 STATUS current 1483 DESCRIPTION 1484 "Primary index for this row identifying a stack of 1485 labels to be pushed on an outgoing packet beneath 1486 the top label." 1487 ::= { mplsLabelStackEntry 1 } 1489 mplsLabelStackLabelIndex OBJECT-TYPE 1490 SYNTAX Integer32 1491 MAX-ACCESS not-accessible 1492 STATUS current 1493 DESCRIPTION 1494 "Secondary index for this row identifying one label 1495 of the stack." 1496 ::= { mplsLabelStackEntry 2 } 1498 mplsLabelStackLabel OBJECT-TYPE 1499 SYNTAX MplsLabel 1500 MAX-ACCESS read-create 1501 STATUS current 1502 DESCRIPTION 1503 "Label to pushed." 1504 ::= { mplsLabelStackEntry 3 } 1506 mplsLabelStackRowStatus OBJECT-TYPE 1507 SYNTAX RowStatus 1508 MAX-ACCESS read-create 1509 STATUS current 1510 DESCRIPTION 1511 "For creating, modifying, and deleting this row." 1513 ::= { mplsLabelStackEntry 4 } 1515 -- End of mplsLabelStackTable 1517 -- TSpec table. 1519 mplsTSpecTable OBJECT-TYPE 1520 SYNTAX SEQUENCE OF MplsTSpecEntry 1521 MAX-ACCESS not-accessible 1522 STATUS current 1523 DESCRIPTION 1524 "This table specifies TSpec objects for in and out- 1525 segments." 1526 ::= { mplsLsrObjects 9 } 1528 mplsTSpecEntry OBJECT-TYPE 1529 SYNTAX MplsTSpecEntry 1530 MAX-ACCESS not-accessible 1531 STATUS current 1532 DESCRIPTION 1533 "An entry in this table represents the TSpec objects 1534 for one or more in or out segments. A single entry 1535 can be pointed to by multiple segments indicating 1536 resource sharing." 1537 INDEX { mplsTSpecIndex } 1538 ::= { mplsTSpecTable 1 } 1540 MplsTSpecEntry ::= SEQUENCE { 1541 mplsTSpecIndex Unsigned32, 1542 mplsTSpecIfIndex InterfaceIndex, 1543 mplsTSpecDirection INTEGER, 1544 mplsTSpecMaxRate BitRate, 1545 mplsTSpecMeanRate BitRate, 1546 mplsTSpecMaxBurstSize BurstSize, 1547 mplsTSpecRowStatus RowStatus 1548 } 1550 mplsTSpecIndex OBJECT-TYPE 1551 SYNTAX Unsigned32 1552 MAX-ACCESS read-create 1553 STATUS current 1554 DESCRIPTION 1555 "Uniquely identifies this row of the table. Zero is 1556 not a valid index." 1557 ::= { mplsTSpecEntry 1 } 1559 mplsTSpecIfIndex OBJECT-TYPE 1560 SYNTAX InterfaceIndex 1561 MAX-ACCESS read-create 1562 STATUS current 1563 DESCRIPTION 1564 "Identifies the interface that this entry refers to." 1565 ::= { mplsTSpecEntry 2 } 1567 mplsTSpecDirection OBJECT-TYPE 1568 SYNTAX INTEGER { in(1), out(2) } 1569 MAX-ACCESS read-create 1570 STATUS current 1571 DESCRIPTION 1572 "Direction that these objects pertain to, incoming or 1573 outgoing." 1574 ::= { mplsTSpecEntry 3 } 1576 mplsTSpecMaxRate OBJECT-TYPE 1577 SYNTAX BitRate 1578 UNITS "bits per second" 1579 MAX-ACCESS read-create 1580 STATUS current 1581 DESCRIPTION 1582 "Maximum rate in bits/second." 1583 ::= { mplsTSpecEntry 4 } 1585 mplsTSpecMeanRate OBJECT-TYPE 1586 SYNTAX BitRate 1587 UNITS "bits per second" 1588 MAX-ACCESS read-create 1589 STATUS current 1590 DESCRIPTION 1591 "Mean rate in bits/second." 1592 ::= { mplsTSpecEntry 5 } 1594 mplsTSpecMaxBurstSize OBJECT-TYPE 1595 SYNTAX BurstSize 1596 UNITS "bytes" 1597 MAX-ACCESS read-create 1598 STATUS current 1599 DESCRIPTION 1600 "Maximum burst size in bytes." 1601 ::= { mplsTSpecEntry 6 } 1603 mplsTSpecRowStatus OBJECT-TYPE 1604 SYNTAX RowStatus 1605 MAX-ACCESS read-create 1606 STATUS current 1607 DESCRIPTION 1608 "For creating, modifying, and deleting this row." 1609 ::= { mplsTSpecEntry 7 } 1611 -- End of mplsTSpecTable 1612 -- Notifications. 1614 -- Interface configuration. 1616 mplsInterfaceUp NOTIFICATION-TYPE 1617 OBJECTS { mplsInterfaceConfIndex, 1618 mplsInterfaceAdminStatus, mplsInterfaceOperStatus } 1619 STATUS current 1620 DESCRIPTION 1621 "This notification is generated when a 1622 mplsInterfaceOperStatus object for one of the 1623 entries in mplsInterfaceConfTable is about to leave 1624 the down state and transition into some other state 1625 (but not into the notPresent state). This other 1626 state is indicated by the included value of 1627 mplsInterfaceOperStatus." 1628 ::= { mplsLsrNotifications 1 } 1630 mplsInterfaceDown NOTIFICATION-TYPE 1631 OBJECTS { mplsInterfaceConfIndex, 1632 mplsInterfaceAdminStatus, mplsInterfaceOperStatus } 1633 STATUS current 1634 DESCRIPTION 1635 "This notification is generated when a 1636 mplsInterfaceOperStatus object for one of the 1637 entries in mplsInterfaceConfTable is about to enter 1638 the down state from some other state (but not from 1639 the notPresent state). This other state is 1640 indicated by the included value of 1641 mplsInterfaceOperStatus." 1642 ::= { mplsLsrNotifications 2 } 1644 -- In-segment. 1646 mplsInSegmentUp NOTIFICATION-TYPE 1647 OBJECTS { mplsInSegmentIfIndex, mplsInSegmentLabel, 1648 mplsInSegmentAdminStatus, mplsInSegmentOperStatus } 1649 STATUS current 1650 DESCRIPTION 1651 "This notification is generated when a 1652 mplsInSegmentOperStatus object for one of the 1653 configured in-segments is about to leave the down 1654 state and transition into some other state (but not 1655 into the notPresent state). This other state is 1656 indicated by the included value of 1657 mplsInSegmentOperStatus." 1658 ::= { mplsLsrNotifications 3 } 1660 mplsInSegmentDown NOTIFICATION-TYPE 1661 OBJECTS { mplsInSegmentIfIndex, mplsInSegmentLabel, 1662 mplsInSegmentAdminStatus, mplsInSegmentOperStatus } 1663 STATUS current 1664 DESCRIPTION 1665 "This notification is generated when a 1666 mplsInSegmentOperStatus object for one of the 1667 configured in-segments is about to enter the down 1668 state from some other state (but not from the 1669 notPresent state). This other state is indicated by 1670 the included value of mplsInSegmentOperStatus." 1671 ::= { mplsLsrNotifications 4 } 1673 -- Out-segment. 1675 mplsOutSegmentUp NOTIFICATION-TYPE 1676 OBJECTS { mplsOutSegmentIndex, mplsInSegmentAdminStatus, 1677 mplsInSegmentOperStatus } 1678 STATUS current 1679 DESCRIPTION 1680 "This notification is generated when a 1681 mplsOutSegmentOperStatus object for one of the 1682 configured out-segments is about to leave the down 1683 state and transition into some other state (but not 1684 into the notPresent state). This other state is 1685 indicated by the included value of 1686 mplsOutSegmentOperStatus." 1687 ::= { mplsLsrNotifications 5 } 1689 mplsOutSegmentDown NOTIFICATION-TYPE 1690 OBJECTS { mplsOutSegmentIndex, mplsInSegmentAdminStatus, 1691 mplsInSegmentOperStatus } 1692 STATUS current 1693 DESCRIPTION 1694 "This notification is generated when a 1695 mplsOutSegmentOperStatus object for one of the 1696 configured out-segments is about to enter the down 1697 state from some other state (but not from the 1698 notPresent state). This other state is indicated by 1699 the included value of mplsOutSegmentOperStatus." 1700 ::= { mplsLsrNotifications 6 } 1702 -- Cross-connect. 1704 mplsXCUp NOTIFICATION-TYPE 1705 OBJECTS { mplsXCIndex, 1706 mplsInSegmentIfIndex, mplsInSegmentLabel, 1707 mplsOutSegmentIndex, 1708 mplsXCAdminStatus, mplsXCOperStatus } 1709 STATUS current 1710 DESCRIPTION 1711 "This notification is generated when a 1712 mplsXCOperStatus object for one of the configured 1713 cross-connect entries is about to leave the down 1714 state and transition into some other state (but not 1715 into the notPresent state). This other state is 1716 indicated by the included value of 1717 mplsXCOperStatus." 1718 ::= { mplsLsrNotifications 7 } 1720 mplsXCDown NOTIFICATION-TYPE 1721 OBJECTS { mplsXCIndex, 1722 mplsInSegmentIfIndex, mplsInSegmentLabel, 1723 mplsOutSegmentIndex, 1724 mplsXCAdminStatus, mplsXCOperStatus } 1725 STATUS current 1726 DESCRIPTION 1727 "This notification is generated when a 1728 mplsXCOperStatus object for one of the configured 1729 cross-connect entries is about to enter the down 1730 state from some other state (but not from the 1731 notPresent state). This other state is indicated by 1732 the included value of mplsXCOperStatus." 1733 ::= { mplsLsrNotifications 8 } 1735 -- End of notifications. 1737 -- Module compliance. 1739 mplsLsrGroups 1740 OBJECT IDENTIFIER ::= { mplsLsrConformance 1 } 1742 mplsLsrCompliances 1743 OBJECT IDENTIFIER ::= { mplsLsrConformance 2 } 1745 mplsLsrModuleCompliance MODULE-COMPLIANCE 1746 STATUS current 1747 DESCRIPTION 1748 "Compliance statement for agents that support the 1749 MPLS LSR MIB." 1750 MODULE -- this module 1752 -- The mandatory groups have to be implemented by all LSRs. 1753 -- However, they may all be supported as read-only objects 1754 -- in the case where manual configuration is not 1755 -- supported. 1757 MANDATORY-GROUPS { mplsInSegmentGroup, mplsOutSegmentGroup, 1758 mplsXCGroup, mplsInterfaceGroup, 1759 mplsPerfGroup } 1761 GROUP mplsHCInterfacePerfGroup 1762 DESCRIPTION 1763 "This group is mandatory for high-speed MPLS 1764 capable interfaces for which the objects 1765 mplsInterfaceInOctets and mplsInterfaceOutOctets 1766 wrap around too quickly." 1768 GROUP mplsHCInSegmentPerfGroup 1769 DESCRIPTION 1770 "This group is mandatory for those in-segment 1771 entries for which the object 1772 mplsInSegmentOutOctets wraps around too 1773 quickly." 1775 GROUP mplsHCOutSegmentPerfGroup 1776 DESCRIPTION 1777 "This group is mandatory for those out-segment 1778 entries for which the object 1779 mplsOutSegmentOctets wraps around too quickly." 1781 GROUP mplsTSpecGroup 1782 DESCRIPTION 1783 "This group is mandatory for those LSRs that 1784 support int-serv style resource reservation." 1786 -- Depending on whether the device implements persistent 1787 -- cross-connects or not one of the following two groups 1788 -- is mandatory. 1790 GROUP mplsXCIsPersistentGroup 1791 DESCRIPTION 1792 "This group is mandatory for devices which 1793 support persistent cross-connects. The 1794 following constraints apply: mplsXCIsPersistent 1795 must at least be read-only returning true(2)." 1797 GROUP mplsXCIsNotPersistentGroup 1798 DESCRIPTION 1799 "This group is mandatory for devices which 1800 support non-persistent cross-connects. The 1801 following constraints apply: mplsXCIsPersistent 1802 must at least be read-only returning false(1)." 1804 -- mplsInterfaceConfTable 1806 OBJECT mplsInterfaceAdminStatus 1807 SYNTAX INTEGER { up(1), down(2) } 1808 MIN-ACCESS read-only 1809 DESCRIPTION 1810 "A value of testing(3) need not be supported." 1812 OBJECT mplsInterfaceOperStatus 1813 SYNTAX INTEGER { up(1), down(2) } 1814 MIN-ACCESS read-only 1815 DESCRIPTION 1816 "Only up(1) and down(2) need to be supported." 1818 -- mplsInSegmentTable 1820 OBJECT mplsInSegmentIfIndex 1821 MIN-ACCESS read-only 1822 DESCRIPTION 1823 "Write access is not required." 1825 OBJECT mplsInSegmentLabel 1826 MIN-ACCESS read-only 1827 DESCRIPTION 1828 "Write access is not required." 1830 OBJECT mplsInSegmentXCIndex 1831 MIN-ACCESS read-only 1832 DESCRIPTION 1833 "Write access is not required." 1835 OBJECT mplsInSegmentTSpecIndex 1836 MIN-ACCESS read-only 1837 DESCRIPTION 1838 "Write access is not required." 1840 OBJECT mplsInSegmentNPop 1841 MIN-ACCESS read-only 1842 DESCRIPTION 1843 "Write access if not required. This object 1844 should be set to 1 if it is read-only." 1846 OBJECT mplsInSegmentAddrFamily 1847 SYNTAX INTEGER { other(0) } 1848 MIN-ACCESS read-only 1849 DESCRIPTION 1850 "Write access is not required. A value of 1851 other(0) should be supported." 1853 OBJECT mplsInSegmentAdminStatus 1854 SYNTAX INTEGER { up(1), down(2) } 1855 MIN-ACCESS read-only 1856 DESCRIPTION 1857 "A value of testing(3) need not be supported." 1859 OBJECT mplsInSegmentOperStatus 1860 SYNTAX INTEGER { up(1), down(2) } 1861 MIN-ACCESS read-only 1862 DESCRIPTION 1863 "Only up(1) and down(2) need to be supported." 1865 OBJECT mplsInSegmentRowStatus 1866 SYNTAX INTEGER { active(1), notInService(2), 1867 createAndGo(4), 1868 destroy(6) } 1869 MIN-ACCESS read-only 1870 DESCRIPTION 1871 "The notReady(3) and createAndWait(5) states need not 1872 be supported." 1874 -- mplsOutSegmentTable 1876 OBJECT mplsOutSegmentIndex 1877 MIN-ACCESS read-only 1878 DESCRIPTION 1879 "Write access is not required." 1881 OBJECT mplsOutSegmentIfIndex 1882 MIN-ACCESS read-only 1883 DESCRIPTION 1884 "Write access is not required." 1886 OBJECT mplsOutSegmentPushTopLabel 1887 MIN-ACCESS read-only 1888 DESCRIPTION 1889 "Write access is not required." 1891 OBJECT mplsOutSegmentTopLabel 1892 MIN-ACCESS read-only 1893 DESCRIPTION 1894 "Write access is not required." 1896 OBJECT mplsOutSegmentNextHopIpAddrType 1897 SYNTAX INTEGER { none(1), ipV4(2) } 1898 MIN-ACCESS read-only 1899 DESCRIPTION 1900 "ipV6(3) need not be supported." 1902 OBJECT mplsOutSegmentNextHopIpv4Addr 1903 MIN-ACCESS read-only 1904 DESCRIPTION 1905 "Write access is not required." 1907 OBJECT mplsOutSegmentNextHopIpv6Addr 1908 MIN-ACCESS read-only 1909 DESCRIPTION 1910 "Write access is not required." 1912 OBJECT mplsOutSegmentXCIndex 1913 MIN-ACCESS read-only 1914 DESCRIPTION 1915 "Write access is not required." 1917 OBJECT mplsOutSegmentTSpecIndex 1918 MIN-ACCESS read-only 1919 DESCRIPTION 1920 "Write access is not required." 1922 OBJECT mplsOutSegmentAdminStatus 1923 SYNTAX INTEGER { up(1), down(2) } 1924 MIN-ACCESS read-only 1925 DESCRIPTION 1926 "A value of testing(3) need not be supported." 1928 OBJECT mplsOutSegmentOperStatus 1929 SYNTAX INTEGER { up(1), down(2) } 1930 MIN-ACCESS read-only 1931 DESCRIPTION 1932 "Only up(1) and down(2) need to be supported." 1934 OBJECT mplsOutSegmentRowStatus 1935 SYNTAX INTEGER { active(1), notInService(2), 1936 createAndGo(4), 1937 destroy(6) } 1938 MIN-ACCESS read-only 1939 DESCRIPTION 1940 "The notReady(3) and createAndWait(5) states need 1941 not be supported." 1943 -- mplsXCTable 1945 OBJECT mplsXCIndex 1946 MIN-ACCESS read-only 1947 DESCRIPTION 1948 "Write access is not required." 1950 OBJECT mplsXCLabelStackIndex 1951 MIN-ACCESS read-only 1952 DESCRIPTION 1953 "Write access is not required." 1955 OBJECT mplsXCCOS 1956 MIN-ACCESS read-only 1957 DESCRIPTION 1958 "Write access is not required." 1960 OBJECT mplsXCIsPersistent 1961 MIN-ACCESS read-only 1962 DESCRIPTION 1963 "Write access is not required." 1965 OBJECT mplsXCAdminStatus 1966 SYNTAX INTEGER { up(1), down(2) } 1967 MIN-ACCESS read-only 1968 DESCRIPTION 1969 "A value of testing(3) need not be supported." 1971 OBJECT mplsXCOperStatus 1972 SYNTAX INTEGER { up(1), down(2) } 1973 MIN-ACCESS read-only 1974 DESCRIPTION 1975 "Only up(1) and down(2) need to be supported." 1977 OBJECT mplsXCRowStatus 1978 SYNTAX INTEGER { active(1), notInService(2), 1979 createAndGo(4), 1980 destroy(6) } 1981 MIN-ACCESS read-only 1982 DESCRIPTION 1983 "The notReady(3) and createAndWait(5) states need 1984 not be supported." 1986 ::= { mplsLsrCompliances 1 } 1988 -- Units of conformance. 1990 mplsInterfaceGroup OBJECT-GROUP 1991 OBJECTS { mplsInterfaceConfIndex, 1992 mplsInterfaceLabelMinIn, mplsInterfaceLabelMaxIn, 1993 mplsInterfaceLabelMinOut, mplsInterfaceLabelMaxOut, 1994 mplsInterfaceAdminStatus, mplsInterfaceOperStatus, 1995 mplsInterfaceInLabelsUsed, mplsInterfaceOutLabelsUsed } 1996 STATUS current 1997 DESCRIPTION 1998 "Collection of objects needed for MPLS interface 1999 configuration and performance information." 2000 ::= { mplsLsrGroups 1 } 2002 mplsInSegmentGroup OBJECT-GROUP 2003 OBJECTS { mplsInSegmentIfIndex, mplsInSegmentLabel, 2004 mplsInSegmentNPop, mplsInSegmentAddrFamily, 2005 mplsInSegmentXCIndex, mplsInSegmentTSpecIndex, 2006 mplsInSegmentAdminStatus, mplsInSegmentOperStatus, 2007 mplsInSegmentRowStatus, 2008 mplsInSegmentOctets, mplsInSegmentDiscards } 2009 STATUS current 2010 DESCRIPTION 2011 "Collection of objects needed to implement an in- 2012 segment." 2013 ::= { mplsLsrGroups 2 } 2015 mplsOutSegmentGroup OBJECT-GROUP 2016 OBJECTS { mplsOutSegmentIndex, mplsOutSegmentIfIndex, 2017 mplsOutSegmentPushTopLabel, mplsOutSegmentTopLabel, 2018 mplsOutSegmentNextHopIpAddrType, 2019 mplsOutSegmentNextHopIpv4Addr, 2020 mplsOutSegmentNextHopIpv6Addr, 2021 mplsOutSegmentXCIndex, mplsOutSegmentTSpecIndex, 2022 mplsOutSegmentAdminStatus, mplsOutSegmentOperStatus, 2023 mplsOutSegmentRowStatus, 2024 mplsOutSegmentOctets, mplsOutSegmentDiscards } 2025 STATUS current 2026 DESCRIPTION 2027 "Collection of objects needed to implement an out- 2028 segment." 2029 ::= { mplsLsrGroups 3 } 2031 mplsXCGroup OBJECT-GROUP 2032 OBJECTS { mplsXCIndex, mplsXCLabelStackIndex, 2033 mplsXCAdminStatus, mplsXCOperStatus, mplsXCRowStatus } 2034 STATUS current 2035 DESCRIPTION 2036 "Collection of objects needed to implement a cross- 2037 connect entry." 2038 ::= { mplsLsrGroups 4 } 2040 mplsPerfGroup OBJECT-GROUP 2041 OBJECTS { mplsInterfaceInOctets, mplsInterfaceInPackets, 2042 mplsInterfaceInDiscards, 2043 mplsInterfaceOutOctets, mplsInterfaceOutPackets, 2044 mplsInterfaceOutDiscards, 2045 mplsInSegmentOctets, mplsInSegmentPackets, 2046 mplsInSegmentDiscards, 2047 mplsOutSegmentOctets, mplsOutSegmentPackets, 2048 mplsOutSegmentDiscards } 2049 STATUS current 2050 DESCRIPTION 2051 "Collection of objects providing performance 2052 information about an LSR." 2053 ::= { mplsLsrGroups 5 } 2055 mplsHCInterfacePerfGroup OBJECT-GROUP 2056 OBJECTS { mplsInterfaceInHCOctets, mplsInterfaceOutHCOctets } 2057 STATUS current 2058 DESCRIPTION 2059 "Collection of objects providing performance 2060 information specific to high-speed interfaces for 2061 which the objects mplsInterfaceInOctets and 2062 mplsInterfaceOutOctets wrap-around too quickly." 2063 ::= { mplsLsrGroups 6 } 2065 mplsHCInSegmentPerfGroup OBJECT-GROUP 2066 OBJECTS { mplsInSegmentHCOctets } 2067 STATUS current 2068 DESCRIPTION 2069 "Object(s) providing performance information specific 2070 to out-segments for which the object 2071 mplsInterfaceInOctets wraps around too quickly." 2072 ::= { mplsLsrGroups 7 } 2074 mplsHCOutSegmentPerfGroup OBJECT-GROUP 2075 OBJECTS { mplsOutSegmentHCOctets } 2076 STATUS current 2077 DESCRIPTION 2078 "Object(s) providing performance information specific 2079 to out-segments for which the object 2080 mplsInterfaceOutOctets wraps around too quickly." 2081 ::= { mplsLsrGroups 8 } 2083 mplsTSpecGroup OBJECT-GROUP 2084 OBJECTS { mplsTSpecIndex, mplsTSpecIfIndex, mplsTSpecDirection, 2085 mplsTSpecMaxRate, mplsTSpecMeanRate, 2086 mplsTSpecMaxBurstSize, mplsTSpecRowStatus } 2087 STATUS current 2088 DESCRIPTION 2089 "Object(s) required for supporting int-serv style 2090 resource reservation." 2091 ::= { mplsLsrGroups 9 } 2093 mplsXCIsPersistentGroup OBJECT-GROUP 2094 OBJECTS { mplsXCIsPersistent } 2095 STATUS current 2096 DESCRIPTION 2097 "Objects needed to support persistent cross- 2098 connects." 2099 ::= { mplsLsrGroups 10 } 2101 mplsXCIsNotPersistentGroup OBJECT-GROUP 2102 OBJECTS { mplsXCIsPersistent } 2103 STATUS current 2104 DESCRIPTION 2105 "Objects needed to support non-persistent cross- 2106 connects." 2107 ::= { mplsLsrGroups 11 } 2109 mplsLsrNotificationGroup NOTIFICATION-GROUP 2110 NOTIFICATIONS { mplsInterfaceUp, mplsInterfaceDown, 2111 mplsInSegmentUp, mplsInSegmentDown, 2112 mplsOutSegmentUp, mplsOutSegmentDown, 2113 mplsXCUp, mplsXCDown } 2114 STATUS current 2115 DESCRIPTION 2116 "Set of notifications implemented in this module. 2117 None is mandatory." 2118 ::= { mplsLsrGroups 12 } 2120 -- End of MPLS-LSR-MIB 2121 END 2123 9. Security Considerations 2125 The MIB specified in this document does not raise any security 2126 issues other than those present in the MPLS architecture 2127 [MPLSArch] or those imposed by SNMP itself. 2129 10. Acknowledgments 2131 We wish to thank Ron Bonica, Eric Gray, and Dan Tappan for their 2132 comments on this draft. 2134 11. References 2136 [MPLSArch] Rosen, E., Viswanathan, A., and R. Callon, 2137 "Multiprotocol Label Switching Architecture", 2138 Internet Draft , 2139 February 1999. 2141 [MPLSFW] Callon, R., Doolan, P., Feldman, N., Fredette, A., 2142 Swallow, G., and A. Viswanathan, "A Framework for 2143 Multiprotocol Label Switching", Internet Draft 2144 , November 1997. 2146 [LDPMIB] Cucchiara, J., Sjostrand, H., and J. Luciani, " 2147 Definitions of Managed Objects for the 2148 Multiprotocol Label Switching, Label Distribution 2149 Protocol (LDP)", Internet Draft , August 1998. 2152 [LblStk] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D., 2153 Federokow, G., Li, T., and A. Conta, "MPLS Label 2154 Stack Encoding", Internet Draft , April 1999. 2157 [RSVPTun] Awaduche, D., Berger, L., Der-Haw, G., Li, T., 2158 Swallow, G., and V. Srinivasan, "Extensions to RSVP 2159 for LSP Tunnels", Internet Draft , March 1999. 2162 [CRLDP] B. Jamoussi (Editor), "Constraint-Based LSP Setup 2163 using LDP", Internet Draft , February 1999. 2166 [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", 2167 RFC 1700, October 1994. See also: 2168 http://www.isi.edu/in-notes/iana/assignments/smi- 2169 numbers 2171 [SNMPArch] Harrington, D., Presuhn, R., and B. Wijnen, "An 2172 Architecture for Describing SNMP Management 2173 Frameworks", RFC 2271, January 1998. 2175 [SMIv1] Rose, M., and K. McCloghrie, "Structure and 2176 Identification of Management Information for TCP/IP- 2177 based Internets", RFC 1155, May 1990. 2179 [SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB 2180 Definitions", RFC 1212, March 1991. 2182 [SNMPv1Traps] M. Rose, "A Convention for Defining Traps for use 2183 with the SNMP", RFC 1215, March 1991. 2185 [SMIv2] Case, J., McCloghrie, K., Rose, M., and S. 2186 Waldbusser, "Structure of Management Information 2187 for Version 2 of the Simple Network Management 2188 Protocol (SNMPv2)", RFC 1902, January 1996. 2190 [SNMPv2TC] Case, J., McCloghrie, K., Rose, M., and S. 2191 Waldbusser, "Textual Conventions for Version 2 of 2192 the Simple Network Management Protocol (SNMPv2)", 2193 RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., 2194 January 1996. 2196 [SNMPv2Conf] Case, J., McCloghrie, K., Rose, M., and S. 2197 Waldbusser, "Conformance Statements for Version 2 2198 of the Simple Network Management Protocol 2199 (SNMPv2)", RFC 1904, January 1996. 2201 [SNMPv1] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 2202 "Simple Network Management Protocol", RFC 1157, May 2203 1990. 2205 [SNMPv2c] Case, J., McCloghrie, K., Rose, M., and S. 2206 Waldbusser, "Introduction to Community-based 2207 SNMPv2", RFC 1901, January 1996. 2209 [SNMPv2TM] Case, J., McCloghrie, K., Rose, M., and S. 2210 Waldbusser, "Transport Mappings for Version 2 of 2211 the Simple Network Management Protocol (SNMPv2)", 2212 RFC 1906, January 1996. 2214 [SNMPv3MP] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2215 "Message Processing and Dispatching for the Simple 2216 Network Management Protocol (SNMP)", RFC 2272, 2217 January 1998. 2219 [SNMPv3USM] Blumenthal, U., and B. Wijnen, "User-based Security 2220 Model (USM) for version 3 of the Simple Network 2221 Management Protocol (SNMPv3)", RFC 2274, January 2222 1998. 2224 [SNMPv2PO] Case, J., McCloghrie, K., Rose, M., and S. 2225 Waldbusser, "Protocol Operations for Version 2 of 2226 the Simple Network Management Protocol (SNMPv2)", 2227 RFC 1905, January 1996. 2229 [SNMPv3App] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2230 Applications", RFC 2273, January 1998 2232 [SNMPv3VACM] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- 2233 based Access Control Model (VACM) for the Simple 2234 Network Management Protocol (SNMP)", RFC 2275, 2235 January 1998 2237 12. Authors's Addresses 2239 Cheenu Srinivasan 2240 Tachion Network Technologies 2241 2 Meridian Road 2242 Eatontown, NJ 07724 2244 Phone: +1-732-542-7750 x234 2245 Email: cheenu@tachion.com 2247 Arun Viswanathan 2248 Lucent Technologies 2249 4D537, 101 Crawfords Corner Road 2250 Holmdel, NJ 07733 2252 Phone: +1-732-332-5163 2253 Email: arunv@lucent.com