idnits 2.17.1 draft-nadeau-ccamp-gmpls-lsr-mib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? == 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.) Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 2040 has weird spacing: '...ase the gmpls...' == Line 2305 has weird spacing: '... may be encod...' == Line 2325 has weird spacing: '...or this table...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (January 2002) is 8134 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'RFC2026' is mentioned on line 27, but not defined == Missing Reference: 'GMPLSTCMIB' is mentioned on line 174, but not defined == Missing Reference: 'GMPLSLABELMIB' is mentioned on line 778, but not defined == Missing Reference: 'RFC2401' is mentioned on line 2990, but not defined ** Obsolete undefined reference: RFC 2401 (Obsoleted by RFC 4301) == Unused Reference: 'RFC3036' is defined on line 3032, but no explicit reference was found in the text == Unused Reference: 'RSVPTE' is defined on line 3036, but no explicit reference was found in the text == Unused Reference: 'CRLDP' is defined on line 3042, but no explicit reference was found in the text == Unused Reference: 'GMPLSSig' is defined on line 3066, but no explicit reference was found in the text == Unused Reference: 'GMPLSCRLDP' is defined on line 3077, but no explicit reference was found in the text == Unused Reference: 'GMPLSRSVPTE' is defined on line 3088, but no explicit reference was found in the text == Unused Reference: 'GMPLSSonetSDH' is defined on line 3099, but no explicit reference was found in the text == Unused Reference: 'LABELMIB' is defined on line 3127, but no explicit reference was found in the text == Unused Reference: 'RFC2514' is defined on line 3167, but no explicit reference was found in the text == Unused Reference: 'RFC3034' is defined on line 3218, but no explicit reference was found in the text == Unused Reference: 'RFC3035' is defined on line 3222, but no explicit reference was found in the text ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Obsolete normative reference: RFC 3036 (Obsoleted by RFC 5036) == Outdated reference: A later version (-09) exists of draft-ietf-mpls-rsvp-lsp-tunnel-08 == Outdated reference: A later version (-06) exists of draft-ietf-mpls-cr-ldp-05 -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLSArch' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLSSig' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLSCRLDP' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLSRSVPTE' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLSSonetSDH' -- Possible downref: Non-RFC (?) normative reference: ref. 'TCMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'LSRMIB' -- Possible downref: Normative reference to a draft: ref. 'LABELMIB' -- Possible downref: Normative reference to a draft: ref. 'GMPLSTEMIB' -- Obsolete informational reference (is this intentional?): RFC 1905 (Obsoleted by RFC 3416) -- Obsolete informational reference (is this intentional?): RFC 1906 (Obsoleted by RFC 3417) -- Obsolete informational reference (is this intentional?): RFC 2570 (Obsoleted by RFC 3410) -- Obsolete informational reference (is this intentional?): RFC 2571 (Obsoleted by RFC 3411) -- Obsolete informational reference (is this intentional?): RFC 2572 (Obsoleted by RFC 3412) -- Obsolete informational reference (is this intentional?): RFC 2573 (Obsoleted by RFC 3413) -- Obsolete informational reference (is this intentional?): RFC 2574 (Obsoleted by RFC 3414) -- Obsolete informational reference (is this intentional?): RFC 2575 (Obsoleted by RFC 3415) Summary: 6 errors (**), 0 flaws (~~), 21 warnings (==), 19 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Thomas D. Nadeau 3 Internet Draft Cisco Systems, Inc. 4 Expires: July 2002 5 Cheenu Srinivasan 6 Parama Networks, Inc. 8 Adrian Farrel 9 Movaz Networks, Inc. 11 Tim Hall 12 Edward Harrison 13 Data Connection Ltd. 15 January 2002 17 Generalized Multiprotocol Label Switching (GMPLS) 18 Label Switching Router Management Information Base 20 draft-nadeau-ccamp-gmpls-lsr-mib-01.txt 22 Status of this Memo 24 This document is an Internet-Draft and is in full 25 conformance with all provisions of Section 10 of RFC 2026 26 [RFC2026]. 28 Internet-Drafts are working documents of the Internet 29 Engineering Task Force (IETF), its areas, and its working 30 groups. Note that other groups may also distribute 31 working documents as Internet-Drafts. 33 Internet-Drafts are draft documents valid for a maximum 34 of six months and may be updated, replaced, or obsoleted 35 by other documents at any time. It is inappropriate to 36 use Internet- Drafts as reference material or to cite 37 them other than as "work in progress." 39 The list of current Internet-Drafts can be accessed at 40 http://www.ietf.org/ietf/1id-abstracts.txt. 42 The list of Internet-Draft Shadow Directories can be 43 accessed at http://www.ietf.org/shadow.html. 45 Abstract 47 This memo defines a portion of the Management Information 48 Base (MIB) for use with network management protocols in 49 the Internet community. In particular, it describes 50 managed objects for Multiprotocol Label Switching (MPLS) 51 and Generalized Multiprotocol Label Switching (GMPLS) 52 Label Switched Routers (LSRs). 54 Table of Contents 56 1. Changes and Pending Work .................................. 2 57 1.1. Changes Since the Last Version ......................... 2 58 1.2. Pending Work ........................................... 3 59 2. Introduction .............................................. 3 60 2.1. Migration Strategy ..................................... 4 61 3. The SNMP Management Framework ............................. 4 62 4. Terminology ............................................... 6 63 5. Feature List .............................................. 6 64 6. Outline ................................................... 7 65 6.1. Summary of LSR MIB ..................................... 7 66 7. Brief Description of MIB Objects .......................... 8 67 7.1. gmplsInterfaceConfTable ................................ 8 68 7.2. gmplsInterfacePerfTable ................................ 9 69 7.3. gmplsInSegmentTable .................................... 9 70 7.4. gmplsInSegmentPerfTable ................................ 9 71 7.5. gmplsOutSegmentTable ................................... 9 72 7.6. gmplsOutSegmentPerfTable ............................... 10 73 7.7. gmplsXCTable ........................................... 10 74 7.8. gmplsLabelStackTable ................................... 10 75 7.9. gmplsTrafficParamTable ................................. 10 76 8. Bidirectional LSPs ........................................ 10 77 9. Example of LSP Setup ...................................... 11 78 10. Application of the Interface Group to MPLS ............... 14 79 10.1. Support of the MPLS Layer by ifTable .................. 15 80 11. The Use of RowPointer and Other Cross-References ......... 16 81 11.1. RowPointer ............................................ 16 82 11.2. Cross-referencing to the gmplsLabelTable .............. 17 83 12. GMPLS Label Switching Router MIB Definitions ............. 17 84 13. Security Considerations .................................. 60 85 14. References ............................................... 62 86 14.1. Normative References .................................. 64 87 14.2. Informational References .............................. 66 88 15. Authors' Addresses ....................................... 66 89 16. Full Copyright Statement ................................. 67 91 1. Changes and Pending Work 93 This section must be removed before the draft progresses 94 to RFC. 96 1.1. Changes Since the Last Version 97 - Clarify which objects can be modified when row-status 98 and admin-status are set to active. 100 - Apply bug fixes in line with updates to [LSRMIB]. 102 - Update examples and provide more detail. 104 1.2. Pending Work 106 The following work items have been identified for this 107 draft. They will be addressed in a future version. 109 - Expand conformance statements to give one for 110 monitoring only, and one for monitoring and control. 112 - Bring references up to date, include all drafts 113 referenced from this document, and exclude those that 114 are not referenced. 116 - Provide objects or tables to support getNextIndex for 117 all arbitrary indexes. 119 - Provide support for monitoring tunnel resources in 120 GMPLS systems. For example, SONET/SDH or G.709. This 121 might be done through an arbitrary RowPointer to an 122 external MIB. 124 - Enhance gmplsTrafficParamsTable to support GMPLS 125 traffic parameters for signaled and static LSPs. 127 - Enhance performance tables for technology-specific 128 GMPLS LSPs. 130 2. Introduction 132 This memo defines a portion of the Management Information 133 Base (MIB) for use with network management protocols in 134 the Internet community. In particular, it describes 135 managed objects for Multiprotocol Label Switching (MPLS) 136 [RFC3031] and Generalized Multiprotocol Label Switching 137 (GMPLS) [GMPLSArch] Label Switching Routers (LSRs). 139 Comments should be made directly to the CCAMP mailing 140 list at ccamp@ops.ietf.org. 142 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", 143 "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", 144 "MAY", and "OPTIONAL" in this document are to be 145 interpreted as described in RFC 2119, reference 146 [RFC2119]. 148 2.1. Migration Strategy 150 This MIB is built upon the Label Switching Router MIB 151 defined for use with MPLS [LSRMIB]. The only changes made 152 are additions for support of GMPLS or changes that are 153 necessary to support the increased complexity of a GMPLS 154 system. 156 In all cases, these changes have been made such that 157 migration from [LSRMIB] to this MIB will be as simple as 158 possible. 160 Note that this MIB may be used in systems that support 161 MPLS, GMPLS or both. 163 This MIB may be seen as a replacement for the MPLS LSR 164 MIB [LSRMIB] in systems which support GMPLS, but it is 165 not a requirement that it replace the MPLS LSR MIB in 166 systems that only support MPLS. 168 The companion document modeling and managing GMPLS based 169 traffic engineering [GMPLSTEMIB] is based on the MPLS TE 170 MIB [TEMIB] with the same intentions. It is not expected 171 that a system would mix MPLS and GMPLS MIBs. 173 Textual conventions and OBJECT-IDENTIFIERS are defined in 174 [GMPLSTCMIB] which extends the set of textual conventions 175 originally defined in [TCMIB]. 177 See section 11.1 for a description of how the 178 gmplsLabelTable may be omitted in systems that support 179 MPLS only. 181 3. The SNMP Management Framework 183 The SNMP Management Framework presently consists of five 184 major components: 186 - An overall architecture, described in RFC 2571 187 [RFC2571]. 189 - Mechanisms for describing and naming objects and 190 events for the purpose of management. The first 191 version of this Structure of Management Information 192 (SMI) is called SMIv1 and described in STD 16, RFC 193 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and STD 16, 194 RFC 1215 [RFC1215]. The second version, called SMIv2, 195 is described in STD 58, RFC 2578 [RFC2578], STD 58, 196 RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 198 - Message protocols for transferring management 199 information. The first version of the SNMP message 200 protocol is called SNMPv1 and described in STD 15, RFC 201 1157 [RFC1157]. A second version of the SNMP message 202 protocol, which is not an Internet standards track 203 protocol, is called SNMPv2c and described in RFC 1901 204 [RFC1901] and RFC 1906 [RFC1906]. The third version 205 of the message protocol is called SNMPv3 and described 206 in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 207 [RFC2574]. 209 - Protocol operations for accessing management 210 information. The first set of protocol operations and 211 associated PDU formats is described in STD 15, RFC 212 1157 [RFC1157]. A second set of protocol operations 213 and associated PDU formats is described in RFC 1905 214 [RFC1905]. 216 - A set of fundamental applications described in RFC 217 2573 [RFC2573] and the view-based access control 218 mechanism described in RFC 2575 [RFC2575]. 220 A more detailed introduction to the current SNMP 221 Management Framework can be found in RFC 2570 [RFC2570]. 223 Managed objects are accessed via a virtual information 224 store, termed the Management Information Base or MIB. 225 Objects in the MIB are defined using the mechanisms 226 defined in the SMI. 228 This memo specifies a MIB module that is compliant to the 229 SMIv2. A MIB conforming to the SMIv1 can be produced 230 through the appropriate translations. The resulting 231 translated MIB must be semantically equivalent, except 232 where objects or events are omitted because no 233 translation is possible (use of Counter64). Some machine 234 readable information in SMIv2 will be converted into 235 textual descriptions in SMIv1 during the translation 236 process. However, this loss of machine readable 237 information is not considered to change the semantics of 238 the MIB. 240 4. Terminology 242 This document uses terminology from the document 243 describing the MPLS architecture [RFC3031]. 245 A label switched path (LSP) is modeled as a connection 246 consisting of one or more incoming segments (in-segments) 247 and/or one or more outgoing segments (out-segments) at a 248 Label Switching Router (LSR). The association or 249 interconnection of the in-segments and out-segments is 250 accomplished by using a cross-connect. We use the 251 terminology "connection" and "LSP" interchangeably where 252 the meaning is clear from the context. 254 5. Feature List 256 The GMPLS Label Switching Router MIB is designed to 257 satisfy the following requirements and constraints: 259 - The MIB supports both manually configured LSPs as well 260 as those configured via any MPLS or GMPLS signaling 261 protocol. 263 - The MIB supports the enabling and disabling of MPLS 264 capability on MPLS capable interfaces of an LSR. 266 - The MIB allows resource sharing between two or more 267 LSPs. 269 - Both per-platform and per-interface label spaces are 270 supported. 272 - Forwarding can be performed solely based on an 273 incoming top label [RFC3031, RFC3032]. 275 - Support is provided for next-hop resolution when the 276 outgoing interface is a shared media interface. In 277 the point-to-multipoint case, each outgoing segment 278 can reside on a different shared media interface. 280 - The MIB supports point-to-point, point-to-multipoint 281 and multipoint-to-point connections at an LSR. 283 - For multipoint-to-point connections all outgoing 284 packets can have the same top label. 286 - For multipoint-to-point connections, the outgoing 287 resources of the merged connections can be shared. 289 - For multipoint-to-point connections, packets from 290 different incoming connections can have distinct 291 outgoing label stacks beneath the (identical) top 292 label. 294 - In the point-to-multipoint case each outgoing 295 connection can have a distinct label stack including 296 the top label. 298 - All the members of a point-to-multipoint connection 299 can share the resources allocated for the ingress 300 segments. 302 - The MIB provides cross-connect capability to "pop" an 303 incoming label and forward the packet with the 304 remainder of the label stack unchanged and without 305 pushing any labels ("pop-and-go") [RFC3032]. 307 - The MIB supports persistent as well as non-persistent 308 LSPs. 310 - Performance counters are provided for in-segments and 311 out-segments as well as for measuring performance on a 312 per-interface basis. 314 6. Outline 316 Configuring LSPs through an LSR involves the following 317 steps: 319 - Enabling MPLS on MPLS capable interfaces. 321 - Configuring in-segments and out-segments. 323 - Setting up the cross-connect table to associate 324 segments and/or to indicate connection origination and 325 termination. 327 - Optionally specifying label stack actions. 329 - Optionally specifying segment traffic parameters. 331 6.1. Summary of LSR MIB 333 The MIB objects for performing these actions consist of 334 the following tables: 336 - The interface configuration table 337 (gmplsInterfaceConfTable), which is used for enabling 338 the MPLS protocol on MPLS-capable interfaces. 340 - The in-segment (gmplsInSegmentTable) and out-segment 341 (gmplsOutSegmentTable) tables, which are used for 342 configuring LSP segments at an LSR. 344 - The cross-connect table (gmplsXCTable), which is used 345 to associate in and out segments together, in order to 346 form a cross-connect. 348 - The label stack table (gmplsLabelStackTable), which is 349 used for specifying label stack operations. 351 - The Traffic Parameter table (gmplsTrafficParamTable), 352 which is used for specifying LSP-related traffic 353 parameters. 355 Further, the in-segment and out-segment performance 356 tables, gmplsInSegmentPerfTable and 357 gmplsOutSegmentPerfTable, contain the objects necessary 358 to measure the performance of LSPs, and 359 gmplsInterfacePerfTable has objects to measure 360 performance on a per-interface basis. 362 These tables are described in the subsequent sections. 364 7. Brief Description of MIB Objects 366 Sections 7.1-7.2 describe objects pertaining to MPLS- 367 capable interfaces of an LSR. The objects described in 368 Sections 7.3-7.8, were derived from the Incoming Label 369 Map (ILM) and Next Hop Label Forwarding Entry (NHLFE) as 370 specified in the MPLS architecture document [RFC3031]. 371 Section 7.9 describes objects for specifying traffic 372 parameters for in and out segments. It is appropriate to 373 note that the in-segment, out-segment, and cross-connect 374 tables were modeled after similar tables found in 375 [RFC2515]. 377 7.1. gmplsInterfaceConfTable 379 This table represents the interfaces that are MPLS or 380 GMPLS capable. An LSR creates an entry in this table for 381 every such interface on that LSR. 383 7.2. gmplsInterfacePerfTable 385 This table contains objects to measure the performance of 386 MPLS and GMPLS capable interfaces and is an AUGMENT to 387 gmplsInterfaceConfTable. High capacity counters are 388 provided for objects that are likely to wrap around 389 quickly on high-speed interfaces. 391 7.3. gmplsInSegmentTable 393 This table contains a description of the incoming 394 segments to an LSR and their associated parameters. 396 The administrative and operational status objects for 397 this table are used to control packet transmission on 398 this segment. If either the administrative or 399 operational status objects for this table is set to 400 'down', this implies that packets will not be forwarded. 401 Likewise, if the values are set to 'up' this implies that 402 packets are forwarded. These values are particularly 403 useful in cases where multi-point connections utilize a 404 single cross-connect and the administrator wishes to 405 disable some, but not all of the streams. In these 406 cases, the administrator may set the administrative 407 status object to 'down' on some of the in-segments. 409 7.4. gmplsInSegmentPerfTable 411 The In-Segment Performance Table has objects to measure 412 the performance of an incoming segment configured on an 413 LSR. It is an AUGMENT to gmplsInSegmentTable. High 414 capacity counters are provided for objects that are 415 likely to wrap around quickly on high-speed interfaces. 417 7.5. gmplsOutSegmentTable 419 The Out-Segment Table contains a description of the 420 outgoing segments at an LSR and their associated 421 parameters. The administrative and operational status 422 objects for this table are used to control packet 423 transmission on this segment. If either the 424 administrative or operational status objects is set to 425 'down', this implies that packets will not be forwarded. 426 Likewise, if the values are set to 'up' this implies that 427 packets are forwarded. These values are particularly 428 useful in cases where multicast connections utilize a 429 single cross-connect and the administrator wishes to 430 disable some, but not all of the streams. In these 431 cases, the administrator may set the administrative 432 status object to 'down' on some of the out-segments. 434 7.6. gmplsOutSegmentPerfTable 436 The Out-Segment Table contains objects to measure the 437 performance of an outgoing segment configured on an LSR. 438 It is an AUGMENT to gmplsOutSegmentTable. High capacity 439 counters are provided for objects that are likely to wrap 440 around quickly on high-speed interfaces. 442 7.7. gmplsXCTable 444 The gmplsXCTable specifies information for associating 445 segments together in order to instruct the LSR to switch 446 between the specified segments. It supports point-to- 447 point, point-to-multi-point and multi-point-to-point 448 connections. 450 The administrative and operational status objects for 451 this table imply control of packet forwarding to and from 452 a XCEntry. When the administrative and operational 453 status objects are set to 'down' for example, this 454 implies that the specified XCEntry will not forward 455 packets. Likewise, when either is set to 'up' this 456 implies that packets will be forwarded. 458 7.8. gmplsLabelStackTable 460 The gmplsLabelStackTable specifies the label stack to be 461 pushed onto a packet, beneath the top label. Entries to 462 this table are referred to from gmplsXCTable. 464 7.9. gmplsTrafficParamTable 466 The gmplsTrafficParamTable contains objects for 467 specifying the traffic parameters of in-segments and out- 468 segments. Entries in this table are referred to from 469 gmplsInSegmentTable and gmplsOutSegmentTable. 471 8. Bidirectional LSPs 472 This MIB supports bidirectional LSPs as required for 473 GMPLS. 475 A single entry in the gmplsXCIndex is shared by all of 476 the segments for the entire bidirectional LSP. This 477 facilitates a simple reference from [GMPLSTEMIB] and 478 makes fate-sharing more obvious. 480 It is, however, important that the direction of segments 481 is understood to avoid connecting all in-segments to all 482 out-segments. This is achieved by an object in each 483 segment that indicates the direction of the segment with 484 respect to data flow. 486 A segment that is marked as 'forward' carries data from 487 the 'head' of the LSP to the 'tail'. A segment marked as 488 'reverse' carries data in the reverse direction. 490 Where an LSP is signaled using a conventional signaling 491 protocol, the 'head' of the LSP is the source of the 492 signaling (also known as the ingress) and the 'tail' is 493 the destination (also known as the egress). For manually 494 configured LSPs an arbitrary decision must be made about 495 which segments are 'forward' and which 'reverse'. For 496 consistency this decision should be made across all LSRs 497 that participate in the LSP by assigning 'head' and 498 'tail' ends to the LSP. 500 9. Example of LSP Setup 502 In this section we provide a brief example of using the 503 MIB objects described in section 12. to set up an LSP. 504 While this example is not meant to illustrate every 505 nuance of the MIB, it is intended as an aid to 506 understanding some of the key concepts. It is meant to 507 be read after going through the MIB itself. 509 Suppose that one would like to manually create a best- 510 effort, bi-directional LSP. Assume that, in the forward 511 direction, the LSP enters the LSR via MPLS interface A 512 with ifIndex 12 and exits the LSR via MPLS interface B 513 with ifIndex 13. For the reverse direction, we assume 514 the LSP enters via interface B and leaves via interface A 515 (i.e. the forward and reverse directions use the same bi- 516 directional interfaces). Let us also assume that we do 517 not wish to have a label stack beneath the top label on 518 the outgoing labeled packets. The following example 519 illustrates which rows and corresponding objects might be 520 created to accomplish this. 522 First, the traffic parameter entries must be set-up for 523 both segments. 525 In gmplsTrafficParamTable for the incoming direction: 526 { 527 gmplsTrafficParamIndex = 5 528 gmplsTrafficParamMaxRate = 100000, 529 gmplsTrafficParamMeanRate = 100000, 530 gmplsTrafficParamMaxBurstSize = 2000, 531 gmplsTrafficParamRowStatus = createAndGo(4) 532 } 534 In gmplsTrafficParamTable for the outgoing direction: 535 { 536 gmplsTrafficParamIndex = 6 537 gmplsTrafficParamMaxRate = 100000, 538 gmplsTrafficParamMeanRate = 100000, 539 gmplsTrafficParamMaxBurstSize = 2000, 540 gmplsTrafficParamRowStatus = createAndGo(4) 541 } 543 Note that for a bi-directional LSP, the segments in the 544 reverse direction can share the traffic parameter entries 545 (and hence resources) with the segments in the forward 546 direction. 548 We must next create the appropriate in-segment and out- 549 segment entries with suitable traffic parameters by 550 pointing to the appropriate traffic parameter entries 551 that we have just created. 553 First for the forward direction: 555 In gmplsInSegmentTable 556 { 557 gmplsInSegmentIndex = 1, 558 -- incoming interface 559 gmplsInSegmentIfIndex = 12, 560 -- incoming label 561 gmplsInSegmentLabel = 21, 562 gmplsInSegmentNPop = 1, 563 gmplsInSegmentOwner = snmp (2), 564 gmplsInSegmentTrafficParamPtr = 565 gmplsTrafficParamIndex.5, 566 gmplsInSegmentDirection = forward (1), 567 gmplsInSegmentRowStatus = createAndGo(4) 568 } 570 In gmplsOutSegmentTable 571 { 572 gmplsOutSegmentIndex = 1, 573 -- outgoing interface 574 gmplsOutSegmentIfIndex = 13, 575 gmplsOutSegmentPushTopLabel = true(1), 576 -- outgoing label 577 gmplsOutSegmentTopLabel = 22, 578 gmplsOutSegmentOwner = snmp (2), 579 gmplsOutSegmentTrafficParamPtr = 580 gmplsTrafficParamIndex.6, 581 gmplsOutSegmentDirection = forward (1), 582 gmplsOutSegmentRowStatus = createAndGo(4) 583 } 585 Next for the reverse direction: 587 In gmplsInSegmentTable 588 { 589 gmplsInSegmentIndex = 2, 590 -- incoming interface 591 gmplsInSegmentIfIndex = 13, 592 -- incoming label 593 gmplsInSegmentLabel = 31, 594 gmplsInSegmentNPop = 1, 595 gmplsInSegmentOwner = snmp (2), 596 gmplsInSegmentTrafficParamPtr = 597 gmplsTrafficParamIndex.6, 598 gmplsInSegmentDirection = reverse (2), 599 gmplsInSegmentRowStatus = createAndGo(4) 600 } 602 In gmplsOutSegmentTable 603 { 604 gmplsOutSegmentIndex = 2, 605 -- outgoing interface 606 gmplsOutSegmentIfIndex = 12, 607 gmplsOutSegmentPushTopLabel = true(1), 608 -- outgoing label 609 gmplsOutSegmentTopLabel = 32, 611 gmplsOutSegmentOwner = snmp (2), 612 gmplsOutSegmentTrafficParamPtr = 613 gmplsTrafficParamIndex.5, 614 gmplsOutSegmentDirection = reverse (2), 615 gmplsOutSegmentRowStatus = createAndGo(4) 616 } 618 Next, two cross-connect entries are created thereby 619 associating the newly created segments together. 621 In gmplsXCTable: 622 { 623 gmplsXCIndex = 2, 624 gmplsInSegmentIndex = 1, 625 gmplsOutSegmentIndex = 1, 626 -- 192.33.4.21.2 627 gmplsXCLspId = 'c021041502'H, 628 gmplsXCIsPersistent = false (1), 629 gmplsXCOwner = snmp (2), 630 -- only a single outgoing label 631 gmplsLabelStackIndex = 0, 632 gmplsXCRowStatus = createAndGo(4) 633 } 635 In gmplsXCTable: 636 { 637 gmplsXCIndex = 3, 638 gmplsInSegmentIndex = 2, 639 gmplsOutSegmentIndex = 2, 640 -- 192.33.4.21.2 641 gmplsXCLspId = 'c021041502'H, 642 gmplsXCIsPersistent = false (1), 643 gmplsXCOwner = snmp (2), 644 -- only a single outgoing label 645 gmplsLabelStackIndex = 0, 646 gmplsXCRowStatus = createAndGo(4) 647 } 649 Note that the gmplsInSegmentXCIndex and 650 gmplsOutSegmentXCIndex objects will automatically be 651 populated with the values 2 and 3 (for the forward and 652 reverse segments respectively) when these segments are 653 referred to from the corresponding cross-connect entry. 655 10. Application of the Interface Group to MPLS 657 This memo contains media-specific extensions to the 658 Interfaces Group for managing MPLS interfaces and assumes 659 the interpretation of the Interfaces Group to be in 660 accordance with [RFC2863] which states that the 661 interfaces table (ifTable) contains information on the 662 managed resource's interfaces and that each sub-layer 663 below the internetwork layer of a network interface is 664 considered an interface. Thus, the MPLS interface is 665 represented as an entry in the ifTable. The inter- 666 relation of entries in the ifTable is defined by 667 Interfaces Stack Group defined in [RFC2863]. 669 When using MPLS interfaces, the interface stack table 670 might appear as follows: 672 +----------------------------------------+ 673 | MPLS-interface ifType = mpls(166) + 674 +----------------------------------------+ 675 | Underlying Layer... + 676 +----------------------------------------+ 678 In the above diagram, "Underlying Layer..." refers to the 679 ifIndex of any interface type, which has been defined for 680 MPLS interworking. Examples include ATM, Frame Relay, 681 Ethernet, etc. 683 10.1. Support of the MPLS Layer by ifTable 685 Some specific interpretations of ifTable for the MPLS 686 layer follow. 688 Object Use for the MPLS layerObject 690 ifIndex Each MPLS interface is represented by an 691 ifEntry. 693 ifDescr Description of the MPLS interface. 695 ifType The value that is allocated for MPLS is 696 166. 698 ifSpeed The total bandwidth in bits per second for 699 use by the MPLS layer. 701 ifPhysAddress Unused. 703 ifAdminStatus This variable indicates the administrator's 704 intent as to whether MPLS should be 705 enabled, disabled, or running in some 706 diagnostic testing mode on this interface. 707 Also see [RFC2863]. 709 ifOperStatus This value reflects the actual or 710 operational status of MPLS on this 711 interface. 713 ifLastChange See [RFC2863]. 715 ifInOctets The number of received octets over the 716 interface, i.e., the number of received, 717 octets received as labeled packets. 719 ifOutOctets The number of transmitted octets over the 720 interface, i.e., the number of octets 721 transmitted as labeled packets. 723 ifInErrors The number of labeled packets dropped due 724 to uncorrectable errors. 726 ifInUnknownProtosThe number of received packets 727 discarded during packet header validation, 728 including packets with unrecognized label 729 values. 731 ifOutErrors See [RFC2863]. 733 ifName Textual name (unique on this system) of the 734 interface or an octet string of zero 735 length. 737 ifLinkUpDownTrapEnable 738 Default is disabled (2). 740 ifConnectorPresent 741 Set to false (2). 743 ifHighSpeed See [RFC2863]. 745 ifHCInOctets The 64-bit version of ifInOctets; supported 746 if required by the compliance statements in 747 [RFC2863]. 749 ifHCOutOctets The 64-bit version of ifOutOctets; 750 supported if required by the compliance 751 statements in [RFC2863]. 753 ifAlias The non-volatile 'alias' name for the 754 interface as specified by a network 755 manager. 757 ifCounterDiscontinuityTime 758 See [RFC2863]. 760 11. The Use of RowPointer and Other Cross-References 762 11.1. RowPointer 764 RowPointer is a textual convention used to identify a 765 conceptual row in an SNMP Table by pointing to one of its 766 objects. In this MIB, it is used in gmplsInSegmentTable 767 and gmplsOutSegmentTable for the following purposes. 768 First, it indicates a particular traffic parameter table. 769 An example of such a table is gmplsTrafficParamTable. 770 Second, it is used to indicate a specific instance of a 771 traffic parameter entry that is associated with a given 772 in-segment or out-segment entry. In the in-segment and 773 out-segment tables, the trafficParamPtr SHOULD point to 774 the first column of the appropriate conceptual row. 776 11.2. Cross-referencing to the gmplsLabelTable 778 The gmplsLabelTable [GMPLSLABELMIB] provides a way to 779 model labels in a GMPLS system where labels might not be 780 simple 32 bit integers. 782 Several tables in this document (gmplsInterfaceConfTable, 783 gmplsInSegmentTable, gmplsOutSegmentTable, 784 gmplsLabelStackTable) use arbitrary indexes to point to 785 entries in the gmplsLabelTable to indicate specific label 786 values. 788 Since the primary index into gmplsLabelTabel is a simple 789 32 bit integer (gmplsLabelIndex), in systems where the 790 nature of a label is well-known, and where the label can 791 safely be encoded as a 32 bit integer (for example a 792 conventional MPLS system), the gmplsLabelTable does not 793 need to be supported and the pointers to the 794 gmplsLabelTable (gmplsInterfaceLabelMinIn, 795 gmplsInterfaceLabelMaxIn, gmplsInterfaceLabelMinOut, 796 gmplsInterfaceLabelMaxOut, gmplsInSegmentLabel, 797 gmplsOutSegmentTopLabel, gmplsLabelStackLabel) may be 798 replaced with the direct label values. 800 This provides both a good way to support legacy systems 801 that implement the previous version of this MIB [LSRMIB], 802 and a significant simplification in GMPLS systems that 803 are limited to a single, simple label type. 805 Note that gmplsLabelTable supports concatenated labels 806 through the use of a sub-label index 807 (gmplsSublabelIndex). 809 12. GMPLS Label Switching Router MIB Definitions 811 GMPLS-LSR-MIB DEFINITIONS ::= BEGIN 813 IMPORTS 814 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 815 Integer32, Counter32, Unsigned32, Counter64, 816 Gauge32 817 FROM SNMPv2-SMI 818 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 819 FROM SNMPv2-CONF 820 TruthValue, RowStatus, StorageType, 821 RowPointer, TimeStamp 822 FROM SNMPv2-TC 823 InterfaceIndexOrZero 824 FROM IF-MIB 825 AddressFamilyNumbers 826 FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB 827 InetAddressIPv4, InetAddressIPv6, InetAddressType 828 FROM INET-ADDRESS-MIB 829 MplsLSPID, MplsBitRate, MplsBurstSize, 830 MplsInitialCreationSource 831 FROM MPLS-TC-MIB 832 gmplsMIB, GmplsSegmentDirection, GmplsTrapEnable 833 FROM GMPLS-TC-MIB 834 InetAddressIPv4, InetAddressIPv6 835 FROM INET-ADDRESS-MIB 836 ; 838 gmplsLsrMIB MODULE-IDENTITY 839 LAST-UPDATED 840 "200201251200Z" -- 25 Jan 2002 12:00:00 GMT 841 ORGANIZATION 842 "Common Control And Management Protocols 843 (CCAMP) Working Group" 844 CONTACT-INFO 845 " Thomas D. Nadeau 846 Postal: Cisco Systems, Inc. 847 250 Apollo Drive 848 Chelmsford, MA 01824 849 Tel: +1-978-244-3051 850 Email: tnadeau@cisco.com 852 Cheenu Srinivasan 853 Postal: Parama Networks, Inc. 854 1030 Broad Street 855 Shrewsbury, NJ 07702 856 Tel: +1-732-544-9120 x731 857 Email: cheenu@paramanet.com 859 Adrian Farrel 860 Postal: Movaz Networks, Inc. 861 7926 Jones Branch Drive 862 McLean, VA 22102 863 Tel: +1-703-847-1986 865 Email: afarrel@movaz.com 867 Edward Harrison 868 Postal: Data Connection Ltd. 869 100 Church Street 870 Enfield, Middlesex 871 EN2 6BQ, United Kingdom 872 Tel: +44-20-8366-1177 873 Email: eph@dataconnection.com 875 Tim Hall 876 Postal: Data Connection Ltd. 877 100 Church Street 878 Enfield, Middlesex 879 EN2 6BQ, United Kingdom 880 Tel: +44-20-8366-1177 881 Email: timhall@dataconnection.com 883 Email comments to the CCAMP WG Mailing List 884 at ccamp@ops.ietf.org." 885 DESCRIPTION 886 "This MIB contains managed object 887 definitions for the Generalized 888 Multiprotocol Label Switching (GMPLS) 889 Router." 890 -- Revision history. 891 REVISION 892 "200111111100Z" -- 11 Nov 2001 11:00:00 GMT 893 DESCRIPTION 894 "Initial draft version." 895 REVISION 896 "200201251200Z" -- 25 Jan 2002 12:00:00 GMT 897 DESCRIPTION 898 "Revision for compilation and work in 899 progress." 900 ::= { gmplsMIB 2 } 902 -- Tables, Scalars 903 gmplsLsrObjects 904 OBJECT IDENTIFIER ::= { gmplsLsrMIB 1 } 906 -- Notifications 907 gmplsLsrNotifications 908 OBJECT IDENTIFIER ::= { gmplsLsrMIB 2 } 910 gmplsLsrNotifyPrefix 911 OBJECT IDENTIFIER ::= { gmplsLsrNotifications 0 } 913 -- Conformance 914 gmplsLsrConformance 915 OBJECT IDENTIFIER ::= { gmplsLsrMIB 3 } 917 -- GMPLS Interface Configuration Table. 919 gmplsInterfaceConfTable OBJECT-TYPE 920 SYNTAX SEQUENCE OF GmplsInterfaceConfEntry 921 MAX-ACCESS not-accessible 922 STATUS current 923 DESCRIPTION 924 "This table specifies per-interface MPLS 925 capability and associated information." 926 ::= { gmplsLsrObjects 1 } 928 gmplsInterfaceConfEntry OBJECT-TYPE 929 SYNTAX GmplsInterfaceConfEntry 930 MAX-ACCESS not-accessible 931 STATUS current 932 DESCRIPTION 933 "An entry in this table is created by an LSR 934 for every interface capable of supporting 935 MPLS. Each entry in this table will exist 936 only if a corresponding entry in ifTable 937 exists. If the associated entry in ifTable 938 is deleted, the corresponding entry in this 939 table must also be deleted shortly 940 thereafter. The entry with index 0 941 represents the per-platform label space and 942 contains parameters that apply to all 943 interfaces that participate in the per- 944 platform label space. Other entries defined 945 in this table represent additional MPLS 946 interfaces that may participate in either 947 the per-platform or per-interface label 948 spaces, or both. Additional information 949 about label space participation of an 950 interface is provided in the description 951 clause of 952 mplsInterfaceLabelParticipationType." 953 INDEX { gmplsInterfaceConfIndex } 954 ::= { gmplsInterfaceConfTable 1 } 956 GmplsInterfaceConfEntry ::= SEQUENCE { 957 gmplsInterfaceConfIndex InterfaceIndexOrZero, 958 gmplsInterfaceLabelMinIn Unsigned32, 959 gmplsInterfaceLabelMaxIn Unsigned32, 960 gmplsInterfaceLabelMinOut Unsigned32, 961 gmplsInterfaceLabelMaxOut Unsigned32, 962 gmplsInterfaceTotalBandwidth MplsBitRate, 963 gmplsInterfaceAvailableBandwidth MplsBitRate, 964 gmplsInterfaceLabelParticipationType BITS, 965 gmplsInterfaceConfSignalingCaps BITS 966 } 968 gmplsInterfaceConfIndex OBJECT-TYPE 969 SYNTAX InterfaceIndexOrZero 970 MAX-ACCESS not-accessible 971 STATUS current 972 DESCRIPTION 973 "This is a unique index for an entry in the 974 gmplsInterfaceConfTable. A non-zero index 975 for an entry indicates the ifIndex for the 976 corresponding interface entry in of the 977 MPLS-layer in the ifTable. Note that the 978 per-platform label space may apply to 979 several interfaces, and therefore the 980 configuration of the per-platform label 981 space interface parameters will apply to 982 all of the interfaces that are 983 participating in the per-platform label 984 space." 985 REFERENCE 986 "RFC 2863 - The Interfaces Group MIB, 987 McCloghrie, K., and F. Kastenholtz, June 988 2000" 989 ::= { gmplsInterfaceConfEntry 1 } 991 gmplsInterfaceLabelMinIn OBJECT-TYPE 992 SYNTAX Unsigned32 993 MAX-ACCESS read-only 994 STATUS current 995 DESCRIPTION 996 "This is the minimum value of an MPLS label 997 that this LSR is willing to receive on this 998 interface. This object contains the index 999 into the gmplsLabelTable of the entry that 1000 contains the label value to apply. Note 1001 that in implementations where the label may 1002 be encoded within a 32 bit integer and 1003 where gmplsLabelTable is not implemented, 1004 this object may directly contain the label 1005 value to use." 1006 ::= { gmplsInterfaceConfEntry 2 } 1008 gmplsInterfaceLabelMaxIn OBJECT-TYPE 1009 SYNTAX Unsigned32 1010 MAX-ACCESS read-only 1011 STATUS current 1012 DESCRIPTION 1013 "This is the maximum value of an MPLS label 1014 that this LSR is willing to receive on this 1015 interface. This object contains the index 1016 into the gmplsLabelTable of the entry that 1017 contains the label value to apply. Note 1018 that in implementations where the label may 1019 be encoded within a 32 bit integer and 1020 where gmplsLabelTable is not implemented, 1021 this object may directly contain the label 1022 value to use." 1023 ::= { gmplsInterfaceConfEntry 3 } 1025 gmplsInterfaceLabelMinOut OBJECT-TYPE 1026 SYNTAX Unsigned32 1027 MAX-ACCESS read-only 1028 STATUS current 1029 DESCRIPTION 1030 "This is the minimum value of an MPLS label 1031 that this LSR is willing to send on this 1032 interface. This object contains the index 1033 into the gmplsLabelTable of the entry that 1034 contains the label value to apply. Note 1035 that in implementations where the label may 1036 be encoded within a 32 bit integer and 1037 where gmplsLabelTable is not implemented, 1038 this object may directly contain the label 1039 value to use." 1040 ::= { gmplsInterfaceConfEntry 4 } 1042 gmplsInterfaceLabelMaxOut OBJECT-TYPE 1043 SYNTAX Unsigned32 1044 MAX-ACCESS read-only 1045 STATUS current 1046 DESCRIPTION 1047 "This is the maximum value of an MPLS label 1048 that this LSR is willing to send on this 1049 interface. This object contains the index 1050 into the gmplsLabelTable of the entry that 1051 contains the label value to apply. Note 1052 that in implementations where the label may 1053 be encoded within a 32 bit integer and 1054 where gmplsLabelTable is not implemented, 1055 this object may directly contain the label 1056 value to use." 1057 ::= { gmplsInterfaceConfEntry 5 } 1059 gmplsInterfaceTotalBandwidth OBJECT-TYPE 1060 SYNTAX MplsBitRate 1061 MAX-ACCESS read-only 1062 STATUS current 1063 DESCRIPTION 1064 "This value indicates the total amount of 1065 usable bandwidth on this interface and is 1066 specified in kilobits per second (Kbps). 1067 This variable is not applicable when 1068 applied to the interface with index 0. 1069 When this value cannot be measured, this 1070 value should contain the nominal 1071 bandwidth." 1072 ::= { gmplsInterfaceConfEntry 6 } 1074 gmplsInterfaceAvailableBandwidth OBJECT-TYPE 1075 SYNTAX MplsBitRate 1076 MAX-ACCESS read-only 1077 STATUS current 1078 DESCRIPTION 1079 "This value indicates the total amount of 1080 available bandwidth available on this 1081 interface and is specified in kilobits per 1082 second (Kbps). This value is calculated as 1083 the difference between the amount of 1084 bandwidth currently in use and that 1085 specified in gmplsInterfaceTotalBandwidth. 1086 This variable is not applicable when 1087 applied to the interface with index 0. 1088 When this value cannot be measured, this 1089 value should contain the nominal 1090 bandwidth." 1091 ::= { gmplsInterfaceConfEntry 7 } 1093 gmplsInterfaceLabelParticipationType OBJECT-TYPE 1094 SYNTAX BITS { 1095 perPlatform (0), 1096 perInterface (1) 1097 } 1098 MAX-ACCESS read-only 1099 STATUS current 1100 DESCRIPTION 1101 "Either the perPlatform(0) or 1102 perInterface(1) bit MUST be set. If the 1103 value of the gmplsInterfaceConfIndex for 1104 this entry is zero, then only the 1105 perPlatform(0) bit MUST be set and the 1106 perInterface(1) bit is meaningless. If the 1107 perInterface(1) bit is set then the value 1108 of gmplsInterfaceLabelMinIn, 1109 gmplsInterfaceLabelMaxIn, 1110 gmplsInterfaceLabelMinOut, and 1111 gmplsInterfaceLabelMaxOut for this entry 1112 reflect the label ranges for this 1113 interface. If only the perPlatform(0) bit 1114 is set, then the value of 1115 gmplsInterfaceLabelMinIn, 1116 gmplsInterfaceLabelMaxIn, 1117 gmplsInterfaceLabelMinOut, and 1118 gmplsInterfaceLabelMaxOut for this entry 1119 must be identical to the instance of these 1120 objects with index 0." 1121 REFERENCE 1122 "Multiprotocol Label Switching, Rosen et al, 1123 RFC 3031, January 2001." 1124 ::= { gmplsInterfaceConfEntry 8 } 1126 gmplsInterfaceConfSignalingCaps OBJECT-TYPE 1127 SYNTAX BITS { 1128 rsvpMpls (0), 1129 crldpMpls (1), 1130 ldpMpls (2), 1131 otherMpls (3), 1132 rsvpGmpls (4), 1133 crldpGmpls (5), 1134 otherGmpls (6) 1135 } 1136 MAX-ACCESS read-create 1137 STATUS current 1138 DESCRIPTION 1139 "Defines the signaling capabilities on this 1140 interface. Multiple bits may legitimately 1141 be set at once. Setting no bits implies 1142 that signaling cannot be performed on this 1143 interface and all LSPs must be manually 1144 provisioned." 1145 ::= { gmplsInterfaceConfEntry 9 } 1147 -- End of gmplsInterfaceConfTable 1149 -- MPLS Interface Performance Table. 1150 gmplsInterfacePerfTable OBJECT-TYPE 1151 SYNTAX SEQUENCE OF GmplsInterfacePerfEntry 1152 MAX-ACCESS not-accessible 1153 STATUS current 1154 DESCRIPTION 1155 "This table provides MPLS performance 1156 information on a per-interface basis." 1157 ::= { gmplsLsrObjects 2 } 1159 gmplsInterfacePerfEntry OBJECT-TYPE 1160 SYNTAX GmplsInterfacePerfEntry 1161 MAX-ACCESS not-accessible 1162 STATUS current 1163 DESCRIPTION 1164 "An entry in this table is created by the 1165 LSR for every interface capable of 1166 supporting MPLS. Its is an extension to 1167 the gmplsInterfaceConfEntry table." 1168 AUGMENTS { gmplsInterfaceConfEntry } 1169 ::= { gmplsInterfacePerfTable 1 } 1171 GmplsInterfacePerfEntry ::= SEQUENCE { 1172 -- incoming direction 1173 gmplsInterfaceInLabelsUsed Gauge32, 1174 gmplsInterfaceFailedLabelLookup Counter32, 1175 -- outgoing direction 1176 gmplsInterfaceOutLabelsUsed Gauge32, 1177 gmplsInterfaceOutFragments Counter32 1178 } 1180 gmplsInterfaceInLabelsUsed OBJECT-TYPE 1181 SYNTAX Gauge32 1182 MAX-ACCESS read-only 1183 STATUS current 1184 DESCRIPTION 1185 "This object counts the number of labels 1186 that are in use at this point in time on 1187 this interface in the incoming direction. 1188 If the interface participates in the per- 1189 platform label space only, then this 1190 instance of this object MUST be identical 1191 with the instance with index 0. If the 1192 interface participates in the per-interface 1193 label space, then this this instance of 1194 this object MUST represent the number of 1195 per-interface labels that are in use at 1196 this point in time on this interface." 1197 ::= { gmplsInterfacePerfEntry 1 } 1199 gmplsInterfaceFailedLabelLookup OBJECT-TYPE 1200 SYNTAX Counter32 1201 MAX-ACCESS read-only 1202 STATUS current 1203 DESCRIPTION 1204 "This object counts the number of labeled 1205 packets that have been received on this 1206 interface and were discarded because there 1207 was no matching cross-connect entry. This 1208 object MUST count on a per-interface basis 1209 regardless of which label space the 1210 interface participates in." 1211 ::= { gmplsInterfacePerfEntry 2 } 1213 gmplsInterfaceOutLabelsUsed OBJECT-TYPE 1214 SYNTAX Gauge32 1215 MAX-ACCESS read-only 1216 STATUS current 1217 DESCRIPTION 1218 "This object counts the number of top-most 1219 labels in the outgoing label stacks that 1220 are in use at this point in time on this 1221 interface. This object MUST count on a per- 1222 interface basis regardless of which label 1223 space the interface participates in." 1224 ::= { gmplsInterfacePerfEntry 3 } 1226 gmplsInterfaceOutFragments OBJECT-TYPE 1227 SYNTAX Counter32 1228 MAX-ACCESS read-only 1229 STATUS current 1230 DESCRIPTION 1231 "This object counts the number of outgoing 1232 MPLS packets that required fragmentation 1233 before transmission on this interface. This 1234 object transmission on this interface. This 1235 object MUST count on a per-interface basis 1236 regardless of which label space the 1237 interface participates in." 1238 ::= { gmplsInterfacePerfEntry 4 } 1240 -- In-segment table. 1242 gmplsInSegmentIndexNext OBJECT-TYPE 1243 SYNTAX Unsigned32 (0..4294967295) 1244 MAX-ACCESS read-only 1245 STATUS current 1246 DESCRIPTION 1247 "This object contains the next appropriate 1248 value to be used for gmplsInSegmentIndex 1249 when creating entries in the 1250 gmplsInSegmentTable. If the number of 1251 unassigned entries is exhausted, this 1252 object will take on the value of 0. To 1253 obtain the gmplsInSegmentIndex value for a 1254 new entry, the manager must first issue a 1255 management protocol retrieval operation to 1256 obtain the current value of this object. 1257 The agent should modify the value to 1258 reflect the next unassigned index after 1259 each retrieval operation. After a manager 1260 retrieves a value the agent will determine 1261 through its local policy when this index 1262 value will be made available for reuse." 1263 ::= { gmplsLsrObjects 3 } 1265 gmplsInSegmentTable OBJECT-TYPE 1266 SYNTAX SEQUENCE OF GmplsInSegmentEntry 1267 MAX-ACCESS not-accessible 1268 STATUS current 1269 DESCRIPTION 1270 "This table contains a collection of 1271 incoming segments to an LSR." 1272 ::= { gmplsLsrObjects 4 } 1274 gmplsInSegmentEntry OBJECT-TYPE 1275 SYNTAX GmplsInSegmentEntry 1276 MAX-ACCESS not-accessible 1277 STATUS current 1278 DESCRIPTION 1279 "An entry in this table represents one 1280 incoming segment. An entry can be created 1281 by a network administrator or an SNMP 1282 agent, or an MPLS signaling protocol. The 1283 creator of the entry is denoted by 1284 gmplsInSegmentOwner. The value of 1285 gmplsInSegmentRowStatus cannot be 1286 active(1)unless the ifTable entry 1287 corresponding to gmplsInSegmentIfIndex 1288 exists." 1289 INDEX { gmplsInSegmentIndex } 1290 ::= { gmplsInSegmentTable 1 } 1292 GmplsInSegmentEntry ::= SEQUENCE { 1293 gmplsInSegmentIndex Unsigned32, 1294 gmplsInSegmentIfIndex InterfaceIndexOrZero, 1295 gmplsInSegmentLabel Unsigned32, 1296 gmplsInSegmentNPop Integer32, 1297 gmplsInSegmentAddrFamily AddressFamilyNumbers, 1298 gmplsInSegmentXCIndex Unsigned32, 1299 gmplsInSegmentOwner MplsInitialCreationSource, 1300 gmplsInSegmentTrafficParamPtr RowPointer, 1301 gmplsInSegmentRowStatus RowStatus, 1302 gmplsInSegmentStorageType StorageType, 1303 gmplsInSegmentDirection GmplsSegmentDirection 1304 } 1306 gmplsInSegmentIndex OBJECT-TYPE 1307 SYNTAX Unsigned32 (0..4294967295) 1308 MAX-ACCESS not-accessible 1309 STATUS current 1310 DESCRIPTION 1311 "This value contains a unique index for this 1312 row. While a value of 0 is not valid as an 1313 index for this row it can be supplied as a 1314 valid value to index gmplsXCTable to access 1315 entries for which no in-segment has been 1316 configured." 1317 ::= { gmplsInSegmentEntry 1 } 1319 gmplsInSegmentIfIndex OBJECT-TYPE 1320 SYNTAX InterfaceIndexOrZero 1321 MAX-ACCESS read-create 1322 STATUS current 1323 DESCRIPTION 1324 "This is a unique index for an entry in the 1325 gmplsInSegmentTable. This value represents 1326 the interface index for the incoming MPLS 1327 interface. A value of zero represents an 1328 incoming label from the per-platform label 1329 space." 1330 ::= { gmplsInSegmentEntry 2 } 1332 gmplsInSegmentLabel OBJECT-TYPE 1333 SYNTAX Unsigned32 1334 MAX-ACCESS read-create 1335 STATUS current 1336 DESCRIPTION 1337 "The incoming label for this segment. This 1338 object contains the index into the 1339 gmplsLabelTable of the entry that contains 1340 the label value to apply. Note that in 1341 implementations where the label may be 1342 encoded within a 32 bit integer and where 1343 gmplsLabelTable is not implemented, this 1344 object may directly contain the label value 1345 to use." 1346 ::= { gmplsInSegmentEntry 3 } 1348 gmplsInSegmentNPop OBJECT-TYPE 1349 SYNTAX Integer32 (1..2147483647) 1350 MAX-ACCESS read-create 1351 STATUS current 1352 DESCRIPTION 1353 "The number of labels to pop from the 1354 incoming data. Note that technologies 1355 which do not support examining label stacks 1356 and multi-label popping should set this 1357 value to its default value of 1. Note 1358 further that in some GMPLS technologies 1359 labels are not pushed and popped at each 1360 LSR, but where LSRs handle LSP hierarchies 1361 this function is used. This object cannot 1362 be modified if gmplsInSegmentRowStatus is 1363 active(1)." 1364 DEFVAL { 1 } 1365 ::= { gmplsInSegmentEntry 4 } 1367 gmplsInSegmentAddrFamily OBJECT-TYPE 1368 SYNTAX AddressFamilyNumbers 1369 MAX-ACCESS read-create 1370 STATUS current 1371 DESCRIPTION 1372 "The IANA address family [IANAFamily] of the 1373 incoming packet. A value of other(0) 1374 indicates that the family type is either 1375 unknown or undefined. This object cannot 1376 be modified if gmplsInSegmentRowStatus is 1377 active(1)." 1378 DEFVAL { other } 1379 ::= { gmplsInSegmentEntry 5 } 1381 gmplsInSegmentXCIndex OBJECT-TYPE 1382 SYNTAX Unsigned32 (0..4294967295) 1383 MAX-ACCESS read-only 1384 STATUS current 1385 DESCRIPTION 1386 "Index into gmplsXCTable which identifies 1387 which cross-connect entry this segment is 1388 part of. A value of zero indicates that 1389 this entry is not referred to by any cross- 1390 connect entry. When a cross-connect entry 1391 is created which this in-segment is a part 1392 of, this object is automatically updated to 1393 reflect the value of gmplsXCIndex of that 1394 cross-connect entry." 1395 DEFVAL { 0 } 1396 ::= { gmplsInSegmentEntry 6 } 1398 gmplsInSegmentOwner OBJECT-TYPE 1399 SYNTAX MplsInitialCreationSource 1400 MAX-ACCESS read-create 1401 STATUS current 1402 DESCRIPTION 1403 "Denotes the entity that created and is 1404 responsible for managing this segment. 1405 This object cannot be modified if 1406 gmplsInSegmentRowStatus is active(1)." 1407 DEFVAL { unknown } 1408 ::= { gmplsInSegmentEntry 7 } 1410 gmplsInSegmentTrafficParamPtr OBJECT-TYPE 1411 SYNTAX RowPointer 1412 MAX-ACCESS read-create 1413 STATUS current 1414 DESCRIPTION 1415 "This variable represents a pointer to the 1416 traffic parameter specification for this in- 1417 segment. This value may point at an entry 1418 in the gmplsTrafficParamTable to indicate 1419 which gmplsTrafficParamEntry is to be 1420 assigned to this segment. This value may 1421 optionally point at an externally defined 1422 traffic parameter specification table. A 1423 value of zero-dot-zero indicates best- 1424 effort treatment. By having the same value 1425 of this object, two or more segments can 1426 indicate resource sharing. This object 1427 cannot be modified if 1428 gmplsInSegmentRowStatus is active(1)." 1429 ::= { gmplsInSegmentEntry 8 } 1431 gmplsInSegmentRowStatus OBJECT-TYPE 1432 SYNTAX RowStatus 1433 MAX-ACCESS read-create 1434 STATUS current 1435 DESCRIPTION 1436 "This variable is used to create, modify, 1437 and/or delete a row in this table. This 1438 object cannot be modified if 1439 gmplsInSegmentRowStatus is active(1). If 1440 this variable is set to readOnly(5), and 1441 the corresponding TFIB entry is removed, 1442 then the agent must remove this row shortly 1443 thereafter." 1444 ::= { gmplsInSegmentEntry 9 } 1446 gmplsInSegmentStorageType OBJECT-TYPE 1447 SYNTAX StorageType 1448 MAX-ACCESS read-create 1449 STATUS current 1450 DESCRIPTION 1451 "This variable indicates the storage type 1452 for this table entry. When set to 1453 'permanent', the entire row is to be 1454 stored." 1455 ::= { gmplsInSegmentEntry 10 } 1457 gmplsInSegmentDirection OBJECT-TYPE 1458 SYNTAX GmplsSegmentDirection 1459 MAX-ACCESS read-create 1460 STATUS current 1461 DESCRIPTION 1462 "This variable indicates the direction of 1463 data flow on this segment." 1464 DEFVAL { forward } 1465 ::= { gmplsInSegmentEntry 11 } 1467 -- End of gmplsInSegmentTable 1469 -- In-segment performance table. 1471 gmplsInSegmentPerfTable OBJECT-TYPE 1472 SYNTAX SEQUENCE OF GmplsInSegmentPerfEntry 1473 MAX-ACCESS not-accessible 1474 STATUS current 1475 DESCRIPTION 1476 "This table contains statistical information 1477 for incoming MPLS segments to an LSR." 1478 ::= { gmplsLsrObjects 5 } 1480 gmplsInSegmentPerfEntry OBJECT-TYPE 1481 SYNTAX GmplsInSegmentPerfEntry 1482 MAX-ACCESS not-accessible 1483 STATUS current 1484 DESCRIPTION 1485 "An entry in this table contains statistical 1486 information about one incoming segment 1487 which was configured in the 1488 gmplsInSegmentTable. The counters in this 1489 entry should behave in a manner similar to 1490 that of the interface." 1491 AUGMENTS { gmplsInSegmentEntry } 1492 ::= { gmplsInSegmentPerfTable 1 } 1494 GmplsInSegmentPerfEntry ::= SEQUENCE { 1495 gmplsInSegmentOctets Counter32, 1496 gmplsInSegmentPackets Counter32, 1497 gmplsInSegmentErrors Counter32, 1498 gmplsInSegmentDiscards Counter32, 1500 -- high capacity counter 1501 gmplsInSegmentHCOctets Counter64, 1503 gmplsInSegmentPerfDiscontinuityTime TimeStamp 1504 } 1506 gmplsInSegmentOctets OBJECT-TYPE 1507 SYNTAX Counter32 1508 MAX-ACCESS read-only 1509 STATUS current 1510 DESCRIPTION 1511 "This value represents the total number of 1512 octets received by this segment." 1513 ::= { gmplsInSegmentPerfEntry 1 } 1515 gmplsInSegmentPackets OBJECT-TYPE 1516 SYNTAX Counter32 1517 MAX-ACCESS read-only 1518 STATUS current 1519 DESCRIPTION 1520 "Total number of packets received by this 1521 segment." 1522 ::= { gmplsInSegmentPerfEntry 2 } 1524 gmplsInSegmentErrors OBJECT-TYPE 1525 SYNTAX Counter32 1526 MAX-ACCESS read-only 1527 STATUS current 1528 DESCRIPTION 1529 "The number of errored packets received on 1530 this segment." 1531 ::= { gmplsInSegmentPerfEntry 3 } 1533 gmplsInSegmentDiscards OBJECT-TYPE 1534 SYNTAX Counter32 1535 MAX-ACCESS read-only 1536 STATUS current 1537 DESCRIPTION 1538 "The number of labeled packets received on 1539 this in-segment, which were chosen to be 1540 discarded even though no errors had been 1541 detected to prevent their being 1542 transmitted. One possible reason for 1543 discarding such a labeled packet could be 1544 to free up buffer space." 1545 ::= { gmplsInSegmentPerfEntry 4 } 1547 gmplsInSegmentHCOctets OBJECT-TYPE 1548 SYNTAX Counter64 1549 MAX-ACCESS read-only 1550 STATUS current 1551 DESCRIPTION 1552 "The total number of octets received. This 1553 is the 64 bit version of 1554 gmplsInSegmentOctets." 1555 ::= { gmplsInSegmentPerfEntry 5 } 1557 gmplsInSegmentPerfDiscontinuityTime OBJECT-TYPE 1558 SYNTAX TimeStamp 1559 MAX-ACCESS read-only 1560 STATUS current 1561 DESCRIPTION 1562 "The value of sysUpTime on the most recent 1563 occasion at which any one or more of this 1564 segment's Counter32 or Counter64 suffered a 1565 discontinuity. If no such discontinuities 1566 have occurred since the last re- 1567 initialization of the local management 1568 subsystem, then this object contains a zero 1569 value." 1570 ::= { gmplsInSegmentPerfEntry 6 } 1572 -- End of gmplsInSegmentPerfTable. 1574 -- Out-segment table. 1576 gmplsOutSegmentIndexNext OBJECT-TYPE 1577 SYNTAX Unsigned32 (0..4294967295) 1578 MAX-ACCESS read-only 1579 STATUS current 1580 DESCRIPTION 1581 "This object contains the next appropriate 1582 value to be used for gmplsOutSegmentIndex 1583 when creating entries in the 1584 gmplsOutSegmentTable. If the number of 1585 unassigned entries is exhausted, this 1586 object will take on the value of 0. To 1587 obtain the gmplsOutSegmentIndex value for a 1588 new entry, the manager must first issue a 1589 management protocol retrieval operation to 1590 obtain the current value of this object. 1591 The agent should modify the value to 1592 reflect the next unassigned index after 1593 each retrieval operation. After a manager 1594 retrieves a value the agent will determine 1595 through its local policy when this index 1596 value will be made available for reuse." 1597 ::= { gmplsLsrObjects 6 } 1599 gmplsOutSegmentTable OBJECT-TYPE 1600 SYNTAX SEQUENCE OF GmplsOutSegmentEntry 1601 MAX-ACCESS not-accessible 1602 STATUS current 1603 DESCRIPTION 1604 "This table contains a representation of the 1605 outgoing segments from an LSR." 1606 ::= { gmplsLsrObjects 7 } 1608 gmplsOutSegmentEntry OBJECT-TYPE 1609 SYNTAX GmplsOutSegmentEntry 1610 MAX-ACCESS not-accessible 1611 STATUS current 1612 DESCRIPTION 1613 "An entry in this table represents one 1614 outgoing segment. An entry can be created 1615 by a network administrator or an SNMP 1616 agent, or an MPLS signaling protocol. The 1617 object gmplsOutSegmentOwner indicates the 1618 creator of this entry. The value of 1619 gmplsOutSegmentRowStatus cannot be 1620 active(1) unless the ifTable entry 1621 corresponding to gmplsOutSegmentIfIndex 1622 exists." 1623 INDEX { gmplsOutSegmentIndex } 1624 ::= { gmplsOutSegmentTable 1 } 1626 GmplsOutSegmentEntry ::= SEQUENCE { 1627 gmplsOutSegmentIndex Unsigned32, 1628 gmplsOutSegmentIfIndex 1629 InterfaceIndexOrZero, 1630 gmplsOutSegmentPushTopLabel TruthValue, 1631 gmplsOutSegmentTopLabel Unsigned32, 1632 gmplsOutSegmentNextHopIpAddrType InetAddressType, 1633 gmplsOutSegmentNextHopIpv4Addr InetAddressIPv4, 1634 gmplsOutSegmentNextHopIpv6Addr InetAddressIPv6, 1635 gmplsOutSegmentXCIndex Unsigned32, 1636 gmplsOutSegmentOwner MplsInitialCreationSource, 1637 gmplsOutSegmentTrafficParamPtr RowPointer, 1638 gmplsOutSegmentRowStatus RowStatus, 1639 gmplsOutSegmentStorageType StorageType, 1640 gmplsOutSegmentDirection GmplsSegmentDirection, 1641 gmplsOutSegmentTTLDecrement Unsigned32 1642 } 1644 gmplsOutSegmentIndex OBJECT-TYPE 1645 SYNTAX Unsigned32 (0..4294967295) 1646 MAX-ACCESS not-accessible 1647 STATUS current 1648 DESCRIPTION 1649 "This value contains a unique index for this 1650 row. While a value of 0 is not valid as an 1651 index for this row it can be supplied as a 1652 valid value to index gmplsXCTable to access 1653 entries for which no out-segment has been 1654 configured." 1655 ::= { gmplsOutSegmentEntry 1 } 1657 gmplsOutSegmentIfIndex OBJECT-TYPE 1658 SYNTAX InterfaceIndexOrZero 1659 MAX-ACCESS read-create 1660 STATUS current 1661 DESCRIPTION 1662 "This value must contain the interface index 1663 of the outgoing interface. This object may 1664 only take the value of 0 during the create- 1665 and-wait row creation operation if the 1666 management station has not yet set the 1667 value of this object. This object cannot be 1668 modified if gmplsOutSegmentRowStatus is 1669 active(1). The gmplsOutSegmentRowStatus 1670 cannot be set to active(1) until this 1671 object is set to a value corresponding to a 1672 valid ifEntry." 1673 DEFVAL { 0 } 1674 ::= { gmplsOutSegmentEntry 2 } 1676 gmplsOutSegmentPushTopLabel OBJECT-TYPE 1677 SYNTAX TruthValue 1678 MAX-ACCESS read-create 1679 STATUS current 1680 DESCRIPTION 1681 "This value indicates whether or not a top 1682 label should be pushed onto the outgoing 1683 label stack. The value of this variable 1684 MUST be set to true if the outgoing 1685 interface does not support pop-and-go (for 1686 example an ATM interface) or if it is a 1687 tunnel origination. Note that it is 1688 considered an error in the case that 1689 gmplsOutSegmentPushTopLabel is set to 1690 false, but the cross-connect entry which 1691 refers to this out-segment has a non-zero 1692 gmplsLabelStackIndex. The LSR MUST ensure 1693 that this situation does not happen. Note 1694 that in many GMPLS technologies labels are 1695 not popped and pushed at each LSR, but are 1696 passed through. This pass-through approach 1697 is equivalent to pop and push. 1698 This object cannot be modified if 1699 gmplsOutSegmentRowStatus is active(1)." 1700 ::= { gmplsOutSegmentEntry 3 } 1702 gmplsOutSegmentTopLabel OBJECT-TYPE 1703 SYNTAX Unsigned32 1704 MAX-ACCESS read-create 1705 STATUS current 1706 DESCRIPTION 1707 "If gmplsOutSegmentPushTopLabel is true then 1708 this represents the label that should be 1709 pushed onto the top of the outgoing 1710 packet's label stack. This object contains 1711 the index into the gmplsLabelTable of the 1712 entry that contains the label value to 1713 apply. Note that in implementations where 1714 the label may be encoded within a 32 bit 1715 integer and where gmplsLabelTable is not 1716 implemented, this object may directly 1717 contain the label value to use. If no 1718 label is to be pushed this value SHOULD be 1719 set to 0 by the management station and MUST 1720 be ignored by the agent. This object cannot 1721 be modified if gmplsOutSegmentRowStatus is 1722 active(1)." 1723 DEFVAL { 0 } 1724 ::= { gmplsOutSegmentEntry 4 } 1726 gmplsOutSegmentNextHopIpAddrType OBJECT-TYPE 1727 SYNTAX InetAddressType 1728 MAX-ACCESS read-create 1729 STATUS current 1730 DESCRIPTION 1731 "Indicates whether the next hop address is 1732 IPv4 or IPv6. Note that a value of unknown 1733 (0) is valid only when the outgoing 1734 interface is of type point-to-point. This 1735 object cannot be modified if 1736 gmplsOutSegmentRowStatus is active(1)." 1737 DEFVAL { unknown } 1738 ::= { gmplsOutSegmentEntry 5 } 1740 gmplsOutSegmentNextHopIpv4Addr OBJECT-TYPE 1741 SYNTAX InetAddressIPv4 1742 MAX-ACCESS read-create 1743 STATUS current 1744 DESCRIPTION 1745 "IPv4 Address of the next hop. Its value is 1746 significant only when 1747 gmplsOutSegmentNextHopIpAddrType is ipV4 1748 (1), otherwise it SHOULD return a value of 1749 0. This object cannot be modified if 1750 gmplsOutSegmentRowStatus is active(1)." 1751 ::= { gmplsOutSegmentEntry 6 } 1753 gmplsOutSegmentNextHopIpv6Addr OBJECT-TYPE 1754 SYNTAX InetAddressIPv6 1755 MAX-ACCESS read-create 1756 STATUS current 1757 DESCRIPTION 1758 "IPv6 address of the next hop. Its value is 1759 significant only when 1760 gmplsOutSegmentNextHopIpAddrType is ipV6 1761 (2), otherwise it SHOULD return a value of 1762 0. This object cannot be modified if 1763 gmplsOutSegmentRowStatus is active(1)." 1764 ::= { gmplsOutSegmentEntry 7 } 1766 gmplsOutSegmentXCIndex OBJECT-TYPE 1767 SYNTAX Unsigned32 (0..4294967295) 1768 MAX-ACCESS read-only 1769 STATUS current 1770 DESCRIPTION 1771 "Index into gmplsXCTable which identifies 1772 which cross-connect entry this segment is 1773 part of. A value of zero indicates that 1774 this entry is not referred to by any cross- 1775 connect entry. When a cross-connect entry 1776 is created which this out-segment is a part 1777 of, this object is automatically updated to 1778 reflect the value of gmplsXCIndex of that 1779 cross-connect entry." 1780 DEFVAL { 0 } 1781 ::= { gmplsOutSegmentEntry 8 } 1783 gmplsOutSegmentOwner OBJECT-TYPE 1784 SYNTAX MplsInitialCreationSource 1785 MAX-ACCESS read-create 1786 STATUS current 1787 DESCRIPTION 1788 "Denotes the entity which created and is 1789 responsible for managing this segment. 1790 This object cannot be modified if 1791 gmplsOutSegmentRowStatus is active(1)." 1792 DEFVAL { unknown } 1793 ::= { gmplsOutSegmentEntry 9 } 1795 gmplsOutSegmentTrafficParamPtr OBJECT-TYPE 1796 SYNTAX RowPointer 1797 MAX-ACCESS read-create 1798 STATUS current 1799 DESCRIPTION 1800 "This variable represents a pointer to the 1801 traffic parameter specification for this 1802 out-segment. This value may point at an 1803 entry in the gmplsTrafficParamTable to 1804 indicate which gmplsTrafficParamEntry is to 1805 be assigned to this segment. This value 1806 may optionally point at an externally 1807 defined traffic parameter specification 1808 table. A value of zero-dot-zero indicates 1809 best-effort treatment. By having the same 1810 value of this object, two or more segments 1811 can indicate resource sharing. This object 1812 cannot be modified if 1813 gmplsOutSegmentRowStatus is active(1)." 1814 ::= { gmplsOutSegmentEntry 10 } 1816 gmplsOutSegmentRowStatus OBJECT-TYPE 1817 SYNTAX RowStatus 1818 MAX-ACCESS read-create 1819 STATUS current 1820 DESCRIPTION 1821 "For creating, modifying, and deleting this 1822 row." 1823 ::= { gmplsOutSegmentEntry 11 } 1825 gmplsOutSegmentStorageType OBJECT-TYPE 1826 SYNTAX StorageType 1827 MAX-ACCESS read-create 1828 STATUS current 1829 DESCRIPTION 1830 "This variable indicates the storage type 1831 for this table entry. When set to 1832 'permanent', the entire row is to be 1833 stored. This object cannot be modified if 1834 gmplsOutSegmentRowStatus is active(1). If 1835 this variable is set to readOnly(5), and 1836 the corresponding TFIB entry is removed, 1837 then the agent must remove this row shortly 1838 thereafter." 1839 ::= { gmplsOutSegmentEntry 12 } 1841 gmplsOutSegmentDirection OBJECT-TYPE 1842 SYNTAX GmplsSegmentDirection 1843 MAX-ACCESS read-create 1844 STATUS current 1845 DESCRIPTION 1846 "This variable indicates the direction of 1847 data flow on this segment. This object 1848 cannot be modified if 1849 gmplsOutSegmentRowStatus is active(1)." 1850 DEFVAL { forward } 1851 ::= { gmplsOutSegmentEntry 13 } 1853 gmplsOutSegmentTTLDecrement OBJECT-TYPE 1854 SYNTAX Unsigned32 (0..255) 1855 MAX-ACCESS read-create 1856 STATUS current 1857 DESCRIPTION 1858 "This variable indicates the amount by which 1859 to decrement the TTL of any payload packets 1860 forwarded on this segment if per-hop 1861 decrementing is being done. 1862 A value of zero indicates that no decrement 1863 should be made or that per-hop decrementing 1864 is not in force. 1865 See the gmplsTunnelTTLDecrement object in 1866 the gmplsTunnelTable of [GMPLSTEMIB] for a 1867 value by which to decrement the TTL for the 1868 whole of a tunnel. 1869 This object cannot be modified if 1870 gmplsOutSegmentRowStatus is active(1)." 1871 DEFVAL { 0 } 1872 ::= { gmplsOutSegmentEntry 14 } 1874 -- End of gmplsOutSegmentTable 1876 -- Out-segment performance table. 1878 gmplsOutSegmentPerfTable OBJECT-TYPE 1879 SYNTAX SEQUENCE OF GmplsOutSegmentPerfEntry 1880 MAX-ACCESS not-accessible 1881 STATUS current 1882 DESCRIPTION 1883 "This table contains statistical information 1884 about outgoing segments from an LSR. The 1885 counters in this entry should behave in a 1886 manner similar to that of the interface." 1887 ::= { gmplsLsrObjects 8 } 1889 gmplsOutSegmentPerfEntry OBJECT-TYPE 1890 SYNTAX GmplsOutSegmentPerfEntry 1891 MAX-ACCESS not-accessible 1892 STATUS current 1893 DESCRIPTION 1894 "An entry in this table contains statistical 1895 information about one outgoing segment 1896 configured in gmplsOutSegmentTable." 1897 AUGMENTS { gmplsOutSegmentEntry } 1898 ::= { gmplsOutSegmentPerfTable 1 } 1900 GmplsOutSegmentPerfEntry ::= SEQUENCE { 1901 gmplsOutSegmentOctets Counter32, 1902 gmplsOutSegmentPackets Counter32, 1903 gmplsOutSegmentErrors Counter32, 1904 gmplsOutSegmentDiscards Counter32, 1906 -- HC counter 1907 gmplsOutSegmentHCOctets Counter64, 1909 gmplsOutSegmentPerfDiscontinuityTime TimeStamp 1910 } 1912 gmplsOutSegmentOctets OBJECT-TYPE 1913 SYNTAX Counter32 1914 MAX-ACCESS read-only 1915 STATUS current 1916 DESCRIPTION 1917 "This value contains the total number of 1918 octets sent on this segment." 1919 ::= { gmplsOutSegmentPerfEntry 1 } 1921 gmplsOutSegmentPackets OBJECT-TYPE 1922 SYNTAX Counter32 1923 MAX-ACCESS read-only 1924 STATUS current 1925 DESCRIPTION 1926 "This value contains the total number of 1927 packets sent on this segment." 1928 ::= { gmplsOutSegmentPerfEntry 2 } 1930 gmplsOutSegmentErrors OBJECT-TYPE 1931 SYNTAX Counter32 1932 MAX-ACCESS read-only 1933 STATUS current 1934 DESCRIPTION 1935 "Number of packets that could not be sent 1936 due to errors on this segment." 1937 ::= { gmplsOutSegmentPerfEntry 3 } 1939 gmplsOutSegmentDiscards OBJECT-TYPE 1940 SYNTAX Counter32 1941 MAX-ACCESS read-only 1942 STATUS current 1943 DESCRIPTION 1944 "The number of labeled packets received on 1945 this out-segment, which were chosen to be 1946 discarded even though no errors had been 1947 detected to prevent their being 1948 transmitted. One possible reason for 1949 discarding such a labeled packet could be 1950 to free up buffer space." 1951 ::= { gmplsOutSegmentPerfEntry 4 } 1953 gmplsOutSegmentHCOctets OBJECT-TYPE 1954 SYNTAX Counter64 1955 MAX-ACCESS read-only 1956 STATUS current 1957 DESCRIPTION 1958 "Total number of octets sent. This is the 1959 64 bit version of gmplsOutSegmentOctets." 1960 ::= { gmplsOutSegmentPerfEntry 5 } 1962 gmplsOutSegmentPerfDiscontinuityTime OBJECT-TYPE 1963 SYNTAX TimeStamp 1964 MAX-ACCESS read-only 1965 STATUS current 1966 DESCRIPTION 1967 "The value of sysUpTime on the most recent 1968 occasion at which any one or more of this 1969 segment's Counter32 or Counter64 suffered a 1970 discontinuity. If no such discontinuities 1971 have occurred since the last re- 1972 initialization of the local management 1973 subsystem, then this object contains a zero 1974 value." 1975 ::= { gmplsOutSegmentPerfEntry 6 } 1977 -- End of gmplsOutSegmentPerfTable. 1979 -- Cross-connect table. 1981 gmplsXCIndexNext OBJECT-TYPE 1982 SYNTAX Unsigned32 (0..4294967295) 1983 MAX-ACCESS read-only 1984 STATUS current 1985 DESCRIPTION 1986 "This object contains an appropriate value 1987 to be used for gmplsXCIndex when creating 1988 entries in the gmplsXCTable. The value 0 1989 indicates that no unassigned entries are 1990 available. To obtain the value of 1991 gmplsXCIndex for a new entry in the 1992 gmplsXCTable, the manager issues a 1993 management protocol retrieval operation to 1994 obtain the current value of gmplsXCIndex. 1995 After each retrieval operation, the agent 1996 should modify the value to reflect the next 1997 unassigned index. After a manager 1998 retrieves a value the agent will determine 1999 through its local policy when this index 2000 value will be made available for reuse." 2001 ::= { gmplsLsrObjects 9 } 2003 gmplsXCTable OBJECT-TYPE 2004 SYNTAX SEQUENCE OF GmplsXCEntry 2005 MAX-ACCESS not-accessible 2006 STATUS current 2007 DESCRIPTION 2008 "This table specifies information for 2009 switching between LSP segments. It 2010 supports point-to-point, point-to- 2011 multipoint and multipoint-to-point 2012 connections. gmplsLabelStackTable 2013 specifies the label stack information for a 2014 cross-connect LSR and is referred to from 2015 gmplsXCTable." 2016 ::= { gmplsLsrObjects 10 } 2018 gmplsXCEntry OBJECT-TYPE 2019 SYNTAX GmplsXCEntry 2020 MAX-ACCESS not-accessible 2021 STATUS current 2022 DESCRIPTION 2023 "A row in this table represents one cross- 2024 connect entry. The following objects index 2025 it: 2027 - cross-connect index gmplsXCIndex that uniquelyidentifies 2028 a group of cross-connect entries 2029 - - in-segment index, gmplsInSegmentIndex 2030 - - out-segment index, gmplsOutSegmentIndex 2032 Originating LSPs: 2033 These are represented by using the special 2034 value gmplsInSegmentIndex=0In this case the 2035 gmplsOutSegmentIndex MUST be non-zero. 2037 Terminating LSPs: 2038 These are represented by using the special 2039 value gmplsOutSegmentIndex=0 as index. In 2040 this case the gmplsInSegmentIndex MUST be 2041 non-zero. 2043 Bidirectional LSPs: 2044 These are represented in the normal way. 2045 Objects within the component links indicate 2046 the direction of data flow on those links. 2048 Special labels: 2049 Entries indexed by reserved MPLS label 2050 values 0 through 15 imply terminating LSPs 2051 and MUST have gmplsOutSegmentIfIndex = 0. 2052 Note that situations where LSPs are 2053 terminated with incoming label equal to 0, 2054 should have gmplsInSegmentIfIndex = 0 as 2055 well, but can be distinguished from 2056 originating LSPs because the 2057 gmplsOutSegmentIfIndex = 0. The 2058 gmplsOutSegmentIfIndex MUST only be set to 2059 0 in cases of terminating LSPs. 2061 An entry can be created by a network 2062 administrator by an SNMP agent as 2063 instructed by an MPLS signaling protocol." 2064 INDEX { gmplsXCIndex, 2065 gmplsInSegmentIndex, 2066 gmplsOutSegmentIndex } 2067 ::= { gmplsXCTable 1 } 2069 GmplsXCEntry ::= SEQUENCE { 2070 gmplsXCIndex Unsigned32, 2071 gmplsXCLspId MplsLSPID, 2072 gmplsXCLabelStackIndex Unsigned32, 2073 gmplsXCIsPersistent TruthValue, 2074 gmplsXCOwner MplsInitialCreationSource, 2075 gmplsXCRowStatus RowStatus, 2076 gmplsXCStorageType StorageType, 2077 gmplsXCAdminStatus INTEGER, 2078 gmplsXCOperStatus INTEGER 2079 } 2081 gmplsXCIndex OBJECT-TYPE 2082 SYNTAX Unsigned32 (0..4294967295) 2083 MAX-ACCESS not-accessible 2084 STATUS current 2085 DESCRIPTION 2086 "Primary index for the conceptual row 2087 identifying a group of cross-connect 2088 segments." 2089 ::= { gmplsXCEntry 1 } 2091 gmplsXCLspId OBJECT-TYPE 2092 SYNTAX MplsLSPID 2093 MAX-ACCESS read-create 2094 STATUS current 2095 DESCRIPTION 2096 "This value identifies the label switched 2097 path that this cross-connect entry belongs 2098 to. This object cannot be modified if 2099 mplsXCRowStatus is active(1)." 2100 ::= { gmplsXCEntry 2 } 2102 gmplsXCLabelStackIndex OBJECT-TYPE 2103 SYNTAX Unsigned32 (0..4294967295) 2104 MAX-ACCESS read-create 2105 STATUS current 2106 DESCRIPTION 2107 "Primary index into gmplsLabelStackTable 2108 identifying a stack of labels to be pushed 2109 beneath the top label. Note that the top 2110 label identified by the out-segment ensures 2111 that all the components of a multipoint-to- 2112 point connection have the same outgoing 2113 label. A value of 0 indicates that no 2114 labels are to be stacked beneath the top 2115 label. This object cannot be modified if 2116 mplsXCRowStatus is active(1)." 2117 ::= { gmplsXCEntry 3 } 2119 gmplsXCIsPersistent OBJECT-TYPE 2120 SYNTAX TruthValue 2121 MAX-ACCESS read-create 2122 STATUS current 2123 DESCRIPTION 2124 "Denotes whether or not this cross-connect 2125 entry and associated in- and out-segments 2126 should be restored automatically after 2127 failures. This value MUST be set to false 2128 in cases where this cross-connect entry was 2129 created by a signaling protocol. This 2130 object cannot be modified if 2131 mplsXCRowStatus is active(1)." 2132 DEFVAL { false } 2133 ::= { gmplsXCEntry 4 } 2135 gmplsXCOwner OBJECT-TYPE 2136 SYNTAX MplsInitialCreationSource 2137 MAX-ACCESS read-create 2138 STATUS current 2139 DESCRIPTION 2140 "Denotes the entity that created and is 2141 responsible for managing this cross- 2142 connect. This object cannot be modified 2143 if mplsXCRowStatus is active(1)." 2144 ::= { gmplsXCEntry 5 } 2146 gmplsXCRowStatus OBJECT-TYPE 2147 SYNTAX RowStatus 2148 MAX-ACCESS read-create 2149 STATUS current 2150 DESCRIPTION 2151 "For creating, modifying, and deleting this 2152 row." 2153 ::= { gmplsXCEntry 6 } 2155 gmplsXCStorageType OBJECT-TYPE 2156 SYNTAX StorageType 2157 MAX-ACCESS read-create 2158 STATUS current 2159 DESCRIPTION 2160 "Defines the storage type for this table 2161 entry. When set to 'permanent', the entire 2162 row is to be stored. This object cannot be 2163 modified if mplsXCRowStatus is active(1). 2164 If this variable is set to readOnly(5), and 2165 the corresponding TFIB entry is removed, 2166 then the agent must remove this row shortly 2167 thereafter." 2168 ::= { gmplsXCEntry 7 } 2170 gmplsXCAdminStatus OBJECT-TYPE 2171 SYNTAX INTEGER { 2172 up(1), -- ready to pass packets 2173 down(2), 2174 testing(3) -- in some test mode 2175 } 2176 MAX-ACCESS read-create 2177 STATUS current 2178 DESCRIPTION 2179 "The desired operational status of this 2180 segment." 2181 ::= { gmplsXCEntry 8 } 2183 gmplsXCOperStatus OBJECT-TYPE 2184 SYNTAX INTEGER { 2185 up(1), -- ready to pass packets 2186 down(2), 2187 testing(3), -- in some test mode 2188 unknown(4), -- status cannot be determined 2189 -- for some reason. 2190 dormant(5), 2191 notPresent(6), -- some component is missing 2192 lowerLayerDown(7) -- down due to the state of 2193 -- lower layer interfaces 2194 } 2195 MAX-ACCESS read-only 2196 STATUS current 2197 DESCRIPTION 2198 "The actual operational status of this cross- 2199 connect." 2200 ::= { gmplsXCEntry 9 } 2202 -- End of gmplsXCTable 2204 -- Label stack table. 2206 gmplsMaxLabelStackDepth OBJECT-TYPE 2207 SYNTAX Integer32 (1..2147483647) 2208 MAX-ACCESS read-only 2209 STATUS current 2210 DESCRIPTION 2211 "The maximum stack depth supported by this 2212 LSR." 2213 ::= { gmplsLsrObjects 11 } 2215 gmplsLabelStackIndexNext OBJECT-TYPE 2216 SYNTAX Unsigned32 (0..4294967295) 2217 MAX-ACCESS read-only 2218 STATUS current 2219 DESCRIPTION 2220 "This object contains an appropriate value 2221 to be used for gmplsLabelStackIndex when 2222 creating entries in the 2223 gmplsLabelStackTable. The value 0 2224 indicates that no unassigned entries are 2225 available. To obtain an 2226 gmplsLabelStackIndex value for a new entry, 2227 the manager issues a management protocol 2228 retrieval operation to obtain the current 2229 value of this object. After each retrieval 2230 operation, the agent should modify the 2231 value to reflect the next unassigned index. 2232 After a manager retrieves a value the agent 2233 will determine through its local policy 2234 when this index value will be made 2235 available for reuse." 2236 ::= { gmplsLsrObjects 12 } 2238 gmplsLabelStackTable OBJECT-TYPE 2239 SYNTAX SEQUENCE OF GmplsLabelStackEntry 2240 MAX-ACCESS not-accessible 2241 STATUS current 2242 DESCRIPTION 2243 "This table specifies the label stack to be 2244 pushed onto a packet, beneath the top 2245 label. Entries into this table are 2246 referred to from gmplsXCTable." 2247 ::= { gmplsLsrObjects 13 } 2249 gmplsLabelStackEntry OBJECT-TYPE 2250 SYNTAX GmplsLabelStackEntry 2251 MAX-ACCESS not-accessible 2252 STATUS current 2253 DESCRIPTION 2254 "An entry in this table represents one label 2255 which is top label. An entry can be 2256 created by a network administrator or by an 2257 SNMP agent as instructed by an MPLS 2258 signaling protocol." 2259 INDEX { gmplsLabelStackIndex, 2260 gmplsLabelStackLabelIndex } 2261 ::= { gmplsLabelStackTable 1 } 2263 GmplsLabelStackEntry ::= SEQUENCE { 2264 gmplsLabelStackIndex Unsigned32, 2265 gmplsLabelStackLabelIndex Unsigned32, 2266 gmplsLabelStackLabel Unsigned32, 2267 gmplsLabelStackRowStatus RowStatus, 2268 gmplsLabelStackStorageType StorageType 2269 } 2271 gmplsLabelStackIndex OBJECT-TYPE 2272 SYNTAX Unsigned32 (0..4294967295) 2273 MAX-ACCESS not-accessible 2274 STATUS current 2275 DESCRIPTION 2276 "Primary index for this row identifying a 2277 stack of labels to be pushed on an outgoing 2278 packet, beneath the top label." 2279 ::= { gmplsLabelStackEntry 1 } 2281 gmplsLabelStackLabelIndex OBJECT-TYPE 2282 SYNTAX Unsigned32 (0..4294967295) 2283 MAX-ACCESS not-accessible 2284 STATUS current 2285 DESCRIPTION 2286 "Secondary index for this row identifying 2287 one label of the stack. Note that an entry 2288 with a smaller gmplsLabelStackLabelIndex 2289 would refer to a label higher up the label 2290 stack and would be popped at a downstream 2291 LSR before a label represented by a higher 2292 gmplsLabelStackLabelIndex at a downstream 2293 LSR." 2294 ::= { gmplsLabelStackEntry 2 } 2296 gmplsLabelStackLabel OBJECT-TYPE 2297 SYNTAX Unsigned32 2298 MAX-ACCESS read-create 2299 STATUS current 2300 DESCRIPTION 2301 "The label to be pushed. This object 2302 contains the index into the gmplsLabelTable 2303 of the entry that contains the label value 2304 to apply. Note that in implementations 2305 where the label may be encoded within a 32 2306 bit integer and where gmplsLabelTable is 2307 not implemented, this object may directly 2308 contain the label value to use." 2309 ::= { gmplsLabelStackEntry 3 } 2311 gmplsLabelStackRowStatus OBJECT-TYPE 2312 SYNTAX RowStatus 2313 MAX-ACCESS read-create 2314 STATUS current 2315 DESCRIPTION 2316 "For creating, modifying, and deleting this 2317 row." 2318 ::= { gmplsLabelStackEntry 4 } 2320 gmplsLabelStackStorageType OBJECT-TYPE 2321 SYNTAX StorageType 2322 MAX-ACCESS read-create 2323 STATUS current 2324 DESCRIPTION 2325 "Defines the storage type for this table 2326 entry. When set to 'permanent', the entire 2327 row is to be stored. If this variable is 2328 set to readOnly(5), and the corresponding 2329 TFIB entry is removed, then the agent must 2330 remove this row shortly thereafter." 2331 ::= { gmplsLabelStackEntry 5 } 2333 -- End of gmplsLabelStackTable 2335 -- Traffic Parameter table. 2337 gmplsTrafficParamIndexNext OBJECT-TYPE 2338 SYNTAX Unsigned32 (0..4294967295) 2339 MAX-ACCESS read-only 2340 STATUS current 2341 DESCRIPTION 2342 "This object contains an appropriate value 2343 which will be used for 2344 gmplsTrafficParamIndex when creating 2345 entries in the gmplsTrafficParamTable. The 2346 value 0 indicates that no unassigned 2347 entries are available. To obtain the 2348 gmplsTrafficParamIndex value for a new 2349 entry, the manager issues a management 2350 protocol retrieval operation to obtain the 2351 current value of this object. After each 2352 retrieval operation, the agent should 2353 modify the value to reflect the next 2354 unassigned index. After a manager 2355 retrieves a value the agent will determine 2356 through its local policy when this index 2357 value will be made available for reuse." 2358 ::= { gmplsLsrObjects 14 } 2360 gmplsTrafficParamTable OBJECT-TYPE 2361 SYNTAX SEQUENCE OF GmplsTrafficParamEntry 2362 MAX-ACCESS not-accessible 2363 STATUS current 2364 DESCRIPTION 2365 "This table specifies the Traffic Parameter 2366 objects for in and out-segments." 2367 ::= { gmplsLsrObjects 15 } 2369 gmplsTrafficParamEntry OBJECT-TYPE 2370 SYNTAX GmplsTrafficParamEntry 2371 MAX-ACCESS not-accessible 2372 STATUS current 2373 DESCRIPTION 2374 "An entry in this table represents the 2375 TrafficParam objects for one or more in or 2376 out segments. A single entry can be 2377 pointed to by multiple segments indicating 2378 resource sharing." 2379 INDEX { gmplsTrafficParamIndex } 2380 ::= { gmplsTrafficParamTable 1 } 2382 GmplsTrafficParamEntry ::= SEQUENCE { 2383 gmplsTrafficParamIndex Unsigned32, 2384 gmplsTrafficParamMaxRate MplsBitRate, 2385 gmplsTrafficParamMeanRate MplsBitRate, 2386 gmplsTrafficParamMaxBurstSize MplsBurstSize, 2387 gmplsTrafficParamRowStatus RowStatus, 2388 gmplsTrafficParamStorageType StorageType 2389 } 2391 gmplsTrafficParamIndex OBJECT-TYPE 2392 SYNTAX Unsigned32 (0..4294967295) 2393 MAX-ACCESS not-accessible 2394 STATUS current 2395 DESCRIPTION 2396 "Uniquely identifies this row of the table. 2397 Note that zero represents an invalid 2398 index." 2399 ::= { gmplsTrafficParamEntry 1 } 2401 gmplsTrafficParamMaxRate OBJECT-TYPE 2402 SYNTAX MplsBitRate 2403 UNITS "kilobits per second" 2404 MAX-ACCESS read-create 2405 STATUS current 2406 DESCRIPTION 2407 "Maximum rate in kilobits/second." 2408 ::= { gmplsTrafficParamEntry 2 } 2410 gmplsTrafficParamMeanRate OBJECT-TYPE 2411 SYNTAX MplsBitRate 2412 UNITS "kilobits per second" 2413 MAX-ACCESS read-create 2414 STATUS current 2415 DESCRIPTION 2416 "Mean rate in kilobits/second." 2417 ::= { gmplsTrafficParamEntry 3 } 2419 gmplsTrafficParamMaxBurstSize OBJECT-TYPE 2420 SYNTAX MplsBurstSize 2421 UNITS "bytes" 2422 MAX-ACCESS read-create 2423 STATUS current 2424 DESCRIPTION 2425 "Maximum burst size in bytes." 2426 ::= { gmplsTrafficParamEntry 4 } 2428 gmplsTrafficParamRowStatus OBJECT-TYPE 2429 SYNTAX RowStatus 2430 MAX-ACCESS read-create 2431 STATUS current 2432 DESCRIPTION 2433 "For creating, modifying, and deleting this 2434 row." 2435 ::= { gmplsTrafficParamEntry 5 } 2437 gmplsTrafficParamStorageType OBJECT-TYPE 2438 SYNTAX StorageType 2439 MAX-ACCESS read-create 2440 STATUS current 2441 DESCRIPTION 2442 "The storage type for this table entry. When 2443 set to 'permanent', the entire row is to be 2444 stored. If this variable is set to 2445 readOnly(5), and the corresponding TFIB 2446 entry is removed, then the agent must 2447 remove this row shortly thereafter." 2448 ::= { gmplsTrafficParamEntry 6 } 2450 -- End of gmplsTrafficParamTable 2452 -- Notification Configuration 2454 gmplsXCTrapEnable OBJECT-TYPE 2455 SYNTAX GmplsTrapEnable 2456 MAX-ACCESS read-write 2457 STATUS current 2458 DESCRIPTION 2459 "This object controls the generation of 2460 gmplsXCUp and gmplsXCDown notifications. 2461 If set to diabled (0), these notifications 2462 are not emitted. If set to oneAtATime (1), 2463 each notification may only carry 2464 information about a single XC that has 2465 changed state. If set to rangeAllowed (2), 2466 each notification MAY carry information 2467 about a contiguous range of XCs that have 2468 changed state, but note that 2469 implementations may send multiple 2470 individual notifications even when 2471 rangeAllowed is selected." 2472 DEFVAL { disabled } 2473 ::= { gmplsLsrObjects 16 } 2475 -- Cross-connect. 2477 gmplsXCUp NOTIFICATION-TYPE 2478 OBJECTS { 2479 gmplsXCOperStatus, -- start of range 2480 gmplsXCOperStatus -- end of range 2481 } 2482 STATUS current 2483 DESCRIPTION 2484 "This notification is generated when the 2485 gmplsXCOperStatus object for one or more 2486 contiguous entries in gmplsXCTable are 2487 about to enter the up(1) state from some 2488 other. The included values of 2489 gmplsXCOperStatus MUST both be set equal to 2490 this other state. The two instances of 2491 gmplsXCOperStatus in this notification 2492 indicate the range of indexes that are 2493 affected. Note that all the indexes of the 2494 two ends of the range can be derived from 2495 the instance identifiers of these two 2496 objects. For cases where a contiguous 2497 range of cross-connects have transitioned 2498 into the up(1) state at roughly the same 2499 time, the device SHOULD issue a single 2500 notification for each range of contiguous 2501 indexes in an effort to minimize the 2502 emission of a large number of 2503 notifications. If a notification has to be 2504 issued for just a single cross-connect 2505 entry, then the instance identifier (and 2506 values) of the two gmplsXCOperStatus 2507 objects MUST be the identical." 2508 ::= { gmplsLsrNotifyPrefix 1 } 2510 gmplsXCDown NOTIFICATION-TYPE 2511 OBJECTS { 2512 gmplsXCOperStatus, -- start of range 2513 gmplsXCOperStatus -- end of range 2514 } 2515 STATUS current 2516 DESCRIPTION 2517 "This notification is generated when the 2518 gmplsXCOperStatus object for one or more 2519 contiguous entries in gmplsXCTable are 2520 about to enter the down(2) state from some 2521 other. The included values of 2522 gmplsXCOperStatus MUST both be set equal to 2523 this other state. The two instances of 2524 gmplsXCOperStatus in this notification 2525 indicate the range of indexes that are 2526 affected. Note that all the indexes of the 2527 two ends of the range can be derived from 2528 the instance identifiers of these two 2529 objects. For cases where a contiguous 2530 range of cross-connects have transitioned 2531 into the down(2) state at roughly the same 2532 time, the device SHOULD issue a single 2533 notification for each range of contiguous 2534 indexes in an effort to minimize the 2535 emission of a large number of 2536 notifications. If a notification has to be 2537 issued for just a single cross-connect 2538 entry, then the instance identifier (and 2539 values) of the two gmplsXCOperStatus 2540 objects MUST be the identical." 2541 ::= { gmplsLsrNotifyPrefix 2 } 2543 -- End of notifications. 2545 -- Module compliance. 2547 gmplsLsrGroups 2548 OBJECT IDENTIFIER ::= { gmplsLsrConformance 1 } 2550 gmplsLsrCompliances 2551 OBJECT IDENTIFIER ::= { gmplsLsrConformance 2 } 2553 gmplsLsrModuleCompliance MODULE-COMPLIANCE 2554 STATUS current 2555 DESCRIPTION 2556 "Compliance statement for agents that 2557 support the MPLS LSR MIB." 2558 MODULE -- this module 2560 -- The mandatory groups have to be implemented 2561 -- by all LSRs. However, they may all be supported 2562 -- as read-only objects in the case where manual 2563 -- configuration is unsupported. 2565 MANDATORY-GROUPS { 2566 gmplsInSegmentGroup, 2567 gmplsOutSegmentGroup, 2568 gmplsXCGroup, 2569 gmplsInterfaceGroup, 2570 gmplsPerfGroup, 2571 gmplsSegmentDiscontinuityGroup 2572 } 2574 GROUP gmplsHCInSegmentPerfGroup 2575 DESCRIPTION 2576 "This group is mandatory for those in- 2577 segment entries for which the object 2578 gmplsInSegmentOutOctets wraps around too 2579 quickly." 2581 GROUP gmplsHCOutSegmentPerfGroup 2582 DESCRIPTION 2583 "This group is mandatory for those out- 2584 segment entries for which the object 2585 gmplsOutSegmentOctets wraps around too 2586 quickly." 2588 GROUP gmplsTrafficParamGroup 2589 DESCRIPTION 2590 "This group is mandatory for those LSRs that 2591 support QoS resource reservation." 2593 -- Depending on whether the device implements 2594 -- persistent cross-connects or not one of the 2595 -- following two groups is mandatory. 2597 GROUP gmplsXCIsPersistentGroup 2598 DESCRIPTION 2599 "This group is mandatory for devices which 2600 support persistent cross-connects. The 2601 following constraints apply: 2602 gmplsXCIsPersistent must at least be read- 2603 only returning true(2)." 2605 GROUP gmplsXCIsNotPersistentGroup 2606 DESCRIPTION 2607 "This group is mandatory for devices which 2608 support non-persistent cross-connects. The 2609 following constraints apply: 2610 gmplsXCIsPersistent must at least be read- 2611 only returning false(1)." 2613 -- gmplsInSegmentTable 2615 OBJECT gmplsInSegmentXCIndex 2616 DESCRIPTION 2617 "Write access is not required." 2619 OBJECT gmplsInSegmentNPop 2620 MIN-ACCESS read-only 2621 DESCRIPTION 2622 "Write access is not required. This object 2623 should be set to 1 if it is read-only." 2625 OBJECT gmplsInSegmentAddrFamily 2626 DESCRIPTION 2627 "Write access is not required. A value of 2628 other(0) should be supported because there 2629 may be cases where the agent may not know 2630 about or support any address types." 2632 OBJECT gmplsInSegmentStorageType 2633 SYNTAX INTEGER { other(1) } 2634 MIN-ACCESS read-only 2635 DESCRIPTION 2636 "Only other(1) needs to be supported." 2638 OBJECT gmplsInSegmentDirection 2639 SYNTAX GmplsSegmentDirection 2640 MIN-ACCESS read-only 2641 DESCRIPTION 2642 "Only forward(1) needs to be supported." 2644 -- gmplsOutSegmentTable 2646 OBJECT gmplsOutSegmentIfIndex 2647 MIN-ACCESS read-only 2648 DESCRIPTION 2649 "Write access is not required." 2651 OBJECT gmplsOutSegmentPushTopLabel 2652 MIN-ACCESS read-only 2653 DESCRIPTION 2654 "Write access is not required." 2656 OBJECT gmplsOutSegmentTopLabel 2657 MIN-ACCESS read-only 2658 DESCRIPTION 2659 "Write access is not required." 2661 OBJECT gmplsOutSegmentNextHopIpAddrType 2662 MIN-ACCESS read-only 2663 DESCRIPTION 2664 "ipV6(3) need not be supported." 2666 OBJECT gmplsOutSegmentNextHopIpv4Addr 2667 MIN-ACCESS read-only 2668 DESCRIPTION 2669 "Write access is not required." 2671 OBJECT gmplsOutSegmentNextHopIpv6Addr 2672 MIN-ACCESS read-only 2673 DESCRIPTION 2674 "Write access is not required." 2676 OBJECT gmplsOutSegmentRowStatus 2677 SYNTAX INTEGER { 2678 active(1), 2679 notInService(2),createAndGo(4), 2680 destroy(6) 2681 } 2682 MIN-ACCESS read-only 2683 DESCRIPTION 2684 "The notReady(3) and createAndWait(5) states 2685 need not be supported." 2687 OBJECT gmplsOutSegmentStorageType 2688 SYNTAX INTEGER { other(1) } 2689 MIN-ACCESS read-only 2690 DESCRIPTION 2691 "Only other(1) needs to be supported." 2693 OBJECT gmplsOutSegmentDirection 2694 SYNTAX GmplsSegmentDirection 2695 MIN-ACCESS read-only 2696 DESCRIPTION 2697 "Only forward(1) needs to be supported." 2699 OBJECT gmplsOutSegmentTTLDecrement 2700 SYNTAX Unsigned32 (0..255) 2701 MIN-ACCESS read-only 2702 DESCRIPTION 2703 "Write access is not required." 2705 -- gmplsXCTable 2707 OBJECT gmplsXCLabelStackIndex 2708 MIN-ACCESS read-only 2709 DESCRIPTION 2710 "Write access is not required." 2712 OBJECT gmplsXCIsPersistent 2713 MIN-ACCESS read-only 2714 DESCRIPTION 2715 "Write access is not required." 2717 OBJECT gmplsXCAdminStatus 2718 SYNTAX INTEGER { up(1), down(2) } 2719 MIN-ACCESS read-only 2720 DESCRIPTION 2721 "A value of testing(3) need not be 2722 supported." 2724 OBJECT gmplsXCOperStatus 2725 SYNTAX INTEGER { up(1), down(2) } 2726 DESCRIPTION 2727 "Only up(1) and down(2) need to be 2728 supported." 2730 OBJECT gmplsXCRowStatus 2731 SYNTAX INTEGER { 2732 active(1), 2733 notInService(2), 2734 createAndGo(4), 2735 destroy(6) 2736 } 2737 MIN-ACCESS read-only 2738 DESCRIPTION 2739 "The notReady(3) and createAndWait(5) states 2740 need not be supported." 2742 OBJECT gmplsXCStorageType 2743 SYNTAX INTEGER { other(1) } 2744 MIN-ACCESS read-only 2745 DESCRIPTION 2746 "Only other(1) needs to be supported." 2748 ::= { gmplsLsrCompliances 1 } 2750 -- Units of conformance. 2752 gmplsInterfaceGroup OBJECT-GROUP 2753 OBJECTS { 2754 gmplsInterfaceLabelMinIn, 2755 gmplsInterfaceLabelMaxIn, 2756 gmplsInterfaceLabelMinOut, 2757 gmplsInterfaceLabelMaxOut, 2758 gmplsInterfaceTotalBandwidth, 2759 gmplsInterfaceAvailableBandwidth, 2760 gmplsInterfaceLabelParticipationType, 2761 gmplsInterfaceConfSignalingCaps 2762 } 2763 STATUS current 2764 DESCRIPTION 2765 "Collection of objects needed for MPLS 2766 interface configuration and performance 2767 information." 2768 ::= { gmplsLsrGroups 1 } 2770 gmplsInSegmentGroup OBJECT-GROUP 2771 OBJECTS { 2772 gmplsInSegmentIndexNext, 2773 gmplsInSegmentIfIndex, 2774 gmplsInSegmentLabel, 2775 gmplsInSegmentNPop, 2776 gmplsInSegmentAddrFamily, 2777 gmplsInSegmentXCIndex, 2778 gmplsInSegmentOwner, 2779 gmplsInSegmentTrafficParamPtr, 2780 gmplsInSegmentRowStatus, 2781 gmplsInSegmentStorageType, 2782 gmplsInSegmentDirection 2783 } 2784 STATUS current 2785 DESCRIPTION 2786 "Collection of objects needed to implement 2787 an in-segment." 2788 ::= { gmplsLsrGroups 2 } 2790 gmplsOutSegmentGroup OBJECT-GROUP 2791 OBJECTS { 2792 gmplsOutSegmentIndexNext, 2793 gmplsOutSegmentIfIndex, 2794 gmplsOutSegmentPushTopLabel, 2795 gmplsOutSegmentTopLabel, 2796 gmplsOutSegmentNextHopIpAddrType, 2797 gmplsOutSegmentNextHopIpv4Addr, 2798 gmplsOutSegmentNextHopIpv6Addr, 2799 gmplsOutSegmentXCIndex, 2800 gmplsOutSegmentOwner, 2801 gmplsOutSegmentTrafficParamPtr, 2802 gmplsOutSegmentRowStatus, 2803 gmplsOutSegmentStorageType, 2804 gmplsOutSegmentDirection, 2805 gmplsOutSegmentTTLDecrement 2806 } 2807 STATUS current 2808 DESCRIPTION 2809 "Collection of objects needed to implement 2810 an out-segment." 2811 ::= { gmplsLsrGroups 3 } 2813 gmplsXCGroup OBJECT-GROUP 2814 OBJECTS { 2815 gmplsXCIndexNext, 2816 gmplsXCLabelStackIndex, 2817 gmplsXCIsPersistent, 2818 gmplsXCOwner, 2819 gmplsXCRowStatus, 2820 gmplsXCAdminStatus, 2821 gmplsXCStorageType, 2822 gmplsXCOperStatus, 2823 gmplsXCTrapEnable 2824 } 2825 STATUS current 2826 DESCRIPTION 2827 "Collection of objects needed to implement a 2828 cross-connect entry." 2829 ::= { gmplsLsrGroups 4 } 2831 gmplsXCOptionalGroup OBJECT-GROUP 2832 OBJECTS { gmplsXCLspId } 2833 STATUS current 2834 DESCRIPTION 2835 "Collection of optional objects for 2836 implementing a cross-connect entry." 2837 ::= { gmplsLsrGroups 5 } 2839 gmplsPerfGroup OBJECT-GROUP 2840 OBJECTS { 2841 gmplsInSegmentOctets, 2842 gmplsInSegmentPackets, 2843 gmplsInSegmentErrors, 2844 gmplsInSegmentDiscards, 2845 gmplsOutSegmentOctets, 2846 gmplsOutSegmentPackets, 2847 gmplsOutSegmentErrors, 2848 gmplsOutSegmentDiscards, 2849 gmplsInterfaceInLabelsUsed, 2850 gmplsInterfaceFailedLabelLookup, 2851 gmplsInterfaceOutFragments, 2852 gmplsInterfaceOutLabelsUsed 2853 } 2854 STATUS current 2855 DESCRIPTION 2856 "Collection of objects providing performance 2857 information about an LSR." 2858 ::= { gmplsLsrGroups 6 } 2860 gmplsHCInSegmentPerfGroup OBJECT-GROUP 2861 OBJECTS { gmplsInSegmentHCOctets } 2862 STATUS current 2863 DESCRIPTION 2864 "Object(s) providing performance information 2865 specific to out-segments for which the 2866 object gmplsInterfaceInOctets wraps around 2867 too quickly." 2868 ::= { gmplsLsrGroups 7 } 2870 gmplsHCOutSegmentPerfGroup OBJECT-GROUP 2871 OBJECTS { gmplsOutSegmentHCOctets } 2872 STATUS current 2873 DESCRIPTION 2874 "Object(s) providing performance information 2875 specific to out-segments for which the 2876 object gmplsInterfaceOutOctets wraps around 2877 too quickly." 2878 ::= { gmplsLsrGroups 8 } 2880 gmplsXCIsPersistentGroup OBJECT-GROUP 2881 OBJECTS { gmplsXCIsPersistent } 2882 STATUS current 2883 DESCRIPTION 2884 "Objects needed to support persistent cross- 2885 connects." 2886 ::= { gmplsLsrGroups 9 } 2888 gmplsXCIsNotPersistentGroup OBJECT-GROUP 2889 OBJECTS { gmplsXCIsPersistent } 2890 STATUS current 2891 DESCRIPTION 2892 "Objects needed to support non-persistent 2893 cross-connects." 2894 ::= { gmplsLsrGroups 10 } 2896 gmplsLabelStackGroup OBJECT-GROUP 2897 OBJECTS { 2898 gmplsLabelStackIndexNext, 2899 gmplsLabelStackLabel, 2900 gmplsLabelStackRowStatus, 2901 gmplsLabelStackStorageType, 2902 gmplsMaxLabelStackDepth 2903 } 2904 STATUS current 2905 DESCRIPTION 2906 "Objects needed to support label stacking." 2907 ::= { gmplsLsrGroups 11 } 2909 gmplsTrafficParamGroup OBJECT-GROUP 2910 OBJECTS { 2911 gmplsTrafficParamIndexNext, 2912 gmplsTrafficParamMaxRate, 2913 gmplsTrafficParamMeanRate, 2914 gmplsTrafficParamMaxBurstSize, 2915 gmplsTrafficParamRowStatus, 2916 gmplsTrafficParamStorageType 2917 } 2918 STATUS current 2919 DESCRIPTION 2920 "Object(s) required for supporting QoS 2921 resource reservation." 2922 ::= { gmplsLsrGroups 12 } 2924 gmplsSegmentDiscontinuityGroup OBJECT-GROUP 2925 OBJECTS { 2926 gmplsInSegmentPerfDiscontinuityTime, 2927 gmplsOutSegmentPerfDiscontinuityTime 2928 } 2929 STATUS current 2930 DESCRIPTION 2931 "A collection of objects providing 2932 information specific to segment 2933 discontinuities.." 2934 ::= { gmplsLsrGroups 13 } 2936 gmplsLsrNotificationGroup NOTIFICATION-GROUP 2937 NOTIFICATIONS { 2938 gmplsXCUp, 2939 gmplsXCDown 2940 } 2941 STATUS current 2942 DESCRIPTION 2943 "Set of notifications implemented in this 2944 module. None is mandatory." 2945 ::= { gmplsLsrGroups 14 } 2947 END 2949 13. Security Considerations 2950 It is clear that this MIB is potentially useful for 2951 monitoring of MPLS and GMPLS LSRs. This MIB can also be 2952 used for configuration of certain objects, and anything 2953 that can be configured can be incorrectly configured, 2954 with potentially disastrous results. 2956 There are a number of management objects defined in this 2957 MIB that have a MAX-ACCESS clause of read-write and/or 2958 read-create. Such objects may be considered sensitive or 2959 vulnerable in some network environments. The support for 2960 SET operations in a non-secure environment without proper 2961 protection can have a negative effect on network 2962 operations. 2964 There are a number of managed objects in this MIB that 2965 may contain information that may be sensitive from a 2966 business perspective, in that they represent a customer's 2967 interface to the MPLS network. Allowing uncontrolled 2968 access to these objects could result in malicious and 2969 unwanted disruptions of network traffic or incorrect 2970 configurations for these customers. There are no objects 2971 that are particularly sensitive in their own right, such 2972 as passwords or monetary amounts. 2974 It is thus important to control even GET access to these 2975 objects and possibly to even encrypt the values of these 2976 object when sending them over the network via SNMP. Not 2977 all versions of SNMP provide features for such a secure 2978 environment. 2980 At this writing, no security holes have been identified 2981 beyond those that SNMP Security [RFC2571] is itself 2982 intended to address. These relate to primarily 2983 controlled access to sensitive information and the 2984 ability to configure a device - or which might result 2985 from operator error, which is beyond the scope of any 2986 security architecture. 2988 SNMPv1 or SNMPv2 are by themselves not a secure 2989 environment. Even if the network itself is secure (for 2990 example by using IPSec [RFC2401]), there is no control as 2991 to who on the secure network is allowed to access and 2992 GET/SET (read, change, create and/or delete) the objects 2993 in this MIB. It is recommended that the implementers 2994 consider the security features as provided by the SNMPv3 2995 framework. Specifically, the use of the User-based 2996 Security Model [RFC2574] and the View-based Access 2997 Control [RFC2575] is recommended. It is then a 2998 customer/user responsibility to ensure that the SNMP 2999 entity giving access to an instance of this MIB is 3000 properly configured to give access to the objects only to 3001 those principals (users) that have legitimate rights to 3002 indeed GET or SET (change/create/delete) them. 3004 14. References 3006 14.1. Normative References 3008 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and 3009 J. Davin, "Simple Network Management 3010 Protocol", RFC 1157, May 1990. 3012 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB 3013 Definitions", RFC 1212, March 1991. 3015 [RFC2119] Bradner, S., "Key words for use in RFCs to 3016 Indicate Requirement Levels", BCP 14, RFC 3017 2119, March 1997. 3019 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, 3020 J., Case, J., Rose, M., and S. Waldbusser, 3021 "Textual Conventions for SMIv2", STD 58, 3022 RFC 2579, April 1999. 3024 [RFC2863] McCloghrie, K. and F. Kastenholtz, "The 3025 Interfaces Group MIB", RFC 2863, June 2000. 3027 [RFC3032] Rosen, E., Rekhter, Y., Tappan, D., 3028 Farinacci, D., Federokow, G., Li, T., and 3029 A. Conta, "MPLS Label Stack Encoding", RFC 3030 3032, January 2001. 3032 [RFC3036] Anderson, L., Doolan, P., Feldman, N., 3033 Fredette, A., and B. Thomas, "LDP 3034 Specification", RFC 3036, January 2001. 3036 [RSVPTE] Awduche, D., Berger, L., Gan, D., Li, T., 3037 Srinivasan, V., and G. Swallow, "RSVP-TE: 3038 Extensions to RSVP for LSP Tunnels", draft- 3039 ietf-mpls-rsvp-lsp-tunnel-08.txt, February 3040 2001, work in progress. 3042 [CRLDP] Jamoussi, B., Aboul-Magd, O., Andersson, 3043 L., Ashwood-Smith, P., Hellstrand, F., 3044 Sundell, K., Callon, R., Dantu, R., Wu, L., 3045 Doolan, P., Worster, T., Feldman, N., 3046 Fredette, A., Girish, M., Gray, E., 3047 Halpern, J., Heinanen, J., Kilty, T., 3048 Malis, A., and P. Vaananen, "Constraint- 3049 Based LSP Setup using LDP", draft-ietf-mpls- 3050 cr-ldp-05.txt, February 2001, work in 3051 progress." 3053 [GMPLSArch] Ashwood-Smith, P., Awduche, D., Banerjee, 3054 A., Basak, D, Berger, L., Bernstein, G., 3055 Drake, J., Fan, Y., Fedyk, D., Grammel, D., 3056 Kompella, K., Kullberg, A., Lang, J., Liaw, 3057 F., Papadimitriou, D., Pendarakis, D., 3058 Rajagopalan, B., Rekhter, Y., Saha, D., 3059 Sandick, H., Sharma, V., Swallow, G., Tang, 3060 Z., Yu, J., Zinin, A., Nadeau, T., Mannie, 3061 E., Generalized Multiprotocol Label 3062 Switching (GMPLS) Architecture, Internet 3063 Draft , March 2001, work in progress. 3066 [GMPLSSig] Ashwood-Smith, P., Awduche, D., Banerjee, 3067 A., Basak, D, Berger, L., Bernstein, G., 3068 Drake, J., Fan, Y., Fedyk, D., Grammel, D., 3069 Kompella, K., Kullberg, A., Lang, 3070 Rajagopalan, B., Rekhter, Y., Saha, D., 3071 Sharma, V., Swallow, G., Bo Tang, Z., 3072 Generalized MPLS - Signaling Functional 3073 Description, , May 2001, work in 3075 progress. 3077 [GMPLSCRLDP] Ashwood-Smith, P., Awduche, D., Banerjee, 3078 A., Basak, D, Berger, L., Bernstein, G., 3079 Drake, J., Fan, Y., Fedyk, D., Grammel, D., 3080 Kompella, K., Kullberg, A., Lang, 3081 Rajagopalan, B., Rekhter, Y., Saha, D., 3082 Sharma, V., Swallow, G., Bo Tang, Z., 3083 Generalized MPLS Signaling - CR-LDP 3084 Extensions, Internet Draft , May 2001, work 3086 in progress. 3088 [GMPLSRSVPTE] Ashwood-Smith, P., Awduche, D., Banerjee, 3089 A., Basak, D, Berger, L., Bernstein, G., 3090 Drake, J., Fan, Y., Fedyk, D., Grammel, D., 3091 Kompella, K., Kullberg, A., Lang, 3092 Rajagopalan, B., Rekhter, Y., Saha, D., 3093 Sharma, V., Swallow, G., Bo Tang, Z., 3094 Generalized MPLS Signaling - RSVP-TE 3095 Extensions, Internet Draft , May 2001, work 3097 in progress. 3099 [GMPLSSonetSDH] Mannie, E., Ansorge, S., Ashwood-Smith, 3100 P., Banerjee, A., Berger, L., Bernstein, 3101 G., Chiu, A., Drake, J., Fan, Y., Fontana, 3102 M., Grammel, G., Heiles, J., Katukam, S., 3103 Kompella, K., Lang, J. P., Liaw, F., Lin, 3104 Z., Mack-Crane, B., Papadimitriou, D., 3105 Pendarakis, D., Raftelis, M., Rajagopalan, 3106 B., Rekhter, Y., Saha, D., Sharma, V., 3107 Swallow, G., Bo Tang, Z., Varma, E., 3108 Vissers, M., Xu, Y., GMPLS Extensions for 3109 SONET and SDH Control, Internet Draft 3110 , 3111 May 2001, work in progress. 3113 [TCMIB] Nadeau, T., Cucchiara, J., Srinivasan, C, 3114 Viswanathan, A. and H. Sjostrand, 3115 "Definition of Textual Conventions and 3116 OBJECT-IDENTITIES for Multiprotocol Label 3117 Switching (MPLS) Management", Internet 3118 Draft , 3119 January 2002, work in progress. 3121 [LSRMIB] Srinivasan, C., Viswanathan, A. and T. 3122 Nadeau, "MPLS Label Switching Router 3123 Management Information Base Using SMIv2", 3124 Internet Draft , January 2002, work in progress. 3127 [LABELMIB] Nadeau, T., Srinivasan, C., A., Farrel, A., 3128 Hall, T., and Harrison, E., "Generalized 3129 Multiprotocol Label Switching (GMPLS) Label 3130 Management Information Base", draft-nadeau- 3131 ccamp-gmpls-label-mib-01.txt, January 2002, 3132 work in progress. 3134 [GMPLSTEMIB] Nadeau, T., Srinivasan, C., Farrel, A., 3135 Hall, T., and Harrison, E., "Generalized 3136 Multiprotocol Label Switching (GMPLS) 3137 Traffic 3138 Engineering Management Information Base", 3139 draft-nadeau-ccamp-gmpls-te-mib-01.txt, 3140 January 2002, work in progress. 3142 14.2. Informational References 3144 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 3145 Identification of Management Information 3146 for TCP/IP-based Internets", RFC 1155, May 3147 1990. 3149 [RFC1215] M. Rose, "A Convention for Defining Traps 3150 for use with the SNMP", RFC 1215, March 3151 1991. 3153 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. 3154 Waldbusser, "Introduction to Community- 3155 based SNMPv2", RFC 1901, January 1996. 3157 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. 3158 Waldbusser, "Protocol Operations for 3159 Version 2 of the Simple Network Management 3160 Protocol (SNMPv2)", RFC 1905, January 1996. 3162 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. 3163 Waldbusser, "Transport Mappings for Version 3164 2 of the Simple Network Management Protocol 3165 (SNMPv2)", RFC 1906, January 1996. 3167 [RFC2514] Noto, et. al., "Definitions of Textual 3168 Conventions and OBJECT-IDENTITIES for ATM 3169 Management", RFC 2514, Feb. 1999 3171 [RFC2515] K. Tesink, "Definitions of Managed Objects 3172 for ATM Management", RFC 2515, Feb. 1999 3174 [RFC2570] Case, J., Mundy, R., Partain, D., and B. 3175 Stewart, "Introduction to Version 3 of the 3176 Internet-standard Network Management 3177 Framework", RFC 2570, April 1999. 3179 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, 3180 "An Architecture for Describing SNMP 3181 Management Frameworks", RFC 2571, April 3182 1999. 3184 [RFC2572] Case, J., Harrington D., Presuhn R., and B. 3185 Wijnen, "Message Processing and Dispatching 3186 for the Simple Network Management Protocol 3187 (SNMP)", RFC 2572, April 1999. 3189 [RFC2573] Levi, D., Meyer, P., and B. Stewart, 3190 "SNMPv3 Applications", RFC 2573, April 3191 1999. 3193 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based 3194 Security Model (USM) for version 3 of the 3195 Simple Network Management Protocol 3196 (SNMPv3)", RFC 2574, April 1999. 3198 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, 3199 "View-based Access Control Model (VACM) for 3200 the Simple Network Management Protocol 3201 (SNMP)", RFC 2575, April 1999. 3203 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, 3204 J., Case, J., Rose, M., and S. Waldbusser, 3205 "Structure of Management Information 3206 Version 2 (SMIv2)", STD 58, RFC 2578, April 3207 1999. 3209 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, 3210 J., Case, J., Rose, M., and S. Waldbusser, 3211 "Conformance Statements for SMIv2", STD 58, 3212 RFC 2580, April 1999. 3214 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 3215 "Multiprotocol Label Switching 3216 Architecture", RFC 3031, January 2001. 3218 [RFC3034] Conta, A., Doolan, P., Malis, A., "Use of 3219 Label Switching on Frame Relay Networks 3220 Specification", RFC 3034, January 2001. 3222 [RFC3035] Davie, B., Lawrence, J., McCloghrie, K., 3223 Rosen, E., Swallow, G., Rekhter, Y., and P. 3224 Doolan, "MPLS using LDP and ATM VC 3225 switching", RFC 3035, January 2001. 3227 [IANAFamily] Internet Assigned Numbers Authority (IANA), 3228 ADDRESS FAMILY NUMBERS. 3230 [TEMIB] Nadeau, T., Srinivasan, C, Viswanathan, A., 3231 "Multiprotocol Label Switching (MPLS) 3232 Traffic Engineering Management Information 3233 Base", Internet Draft , January 2002, work in 3235 progress. 3237 15. Authors' Addresses 3239 Thomas D. Nadeau 3240 Cisco Systems, Inc. 3241 300 Apollo Drive 3242 Chelmsford, MA 01824 3244 Phone: +1-978-244-3051 3245 Email: tnadeau@cisco.com 3246 Cheenu Srinivasan 3247 Parama Networks, Inc. 3248 1030 Broad Street 3249 Shrewsbury, NJ 07702 3250 Phone: +1-732-544-9120 x731 3251 Email: cheenu@paramanet.com 3253 Adrian Farrel 3254 Movaz Networks, Inc. 3255 7926 Jones Branch Drive, Suite 615 3256 McLean VA, 22102 USA 3257 Phone: +1-703-847-9847 3258 Email: afarrel@movaz.com 3260 Tim Hall 3261 Data Connection Ltd. 3262 100 Church Street 3263 Enfield, Middlesex 3264 EN2 6BQ, UK 3265 Phone: +44 20 8366 1177 3266 Email: timhall@dataconnection.com 3268 Edward Harrison 3269 Data Connection Ltd. 3270 100 Church Street 3271 Enfield, Middlesex 3272 EN2 6BQ, UK 3273 Phone: +44 20 8366 1177 3274 Email: eph@dataconnection.com 3276 16. Full Copyright Statement 3278 Copyright (C) The Internet Society (2002). All Rights 3279 Reserved. 3281 This document and translations of it may be copied and 3282 furnished to others, and derivative works that comment on 3283 or otherwise explain it or assist in its implementation 3284 may be prepared, copied, published and distributed, in 3285 whole or in part, without restriction of any kind, 3286 provided that the above copyright notice and this 3287 paragraph are included on all such copies and derivative 3288 works. However, this document itself may not be modified 3289 in any way, such as by removing the copyright notice or 3290 references to the Internet Society or other Internet 3291 organizations, except as needed for the purpose of 3292 developing Internet standards in which case the 3293 procedures for copyrights defined in the Internet 3294 Standards process must be followed, or as required to 3295 translate it into languages other than English. 3297 The limited permissions granted above are perpetual and 3298 will not be revoked by the Internet Society or its 3299 successors or assigns. This document and the information 3300 contained herein is provided on an "AS IS" basis and THE 3301 INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE 3302 DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 3303 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 3304 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY 3305 IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 3306 PARTICULAR PURPOSE.