idnits 2.17.1 draft-ietf-mpls-bundle-mib-04.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents -- however, there's a paragraph with a matching beginning. Boilerplate error? ** 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.) ** There are 3 instances of too long lines in the document, the longest one being 5 characters in excess of 72. == There are 2 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- 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 (November 2002) is 7832 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) == Unused Reference: 'Assigned' is defined on line 2316, but no explicit reference was found in the text == Unused Reference: 'FLOOD' is defined on line 2325, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2401 (Obsoleted by RFC 4301) ** Obsolete normative reference: RFC 1700 (ref. 'Assigned') (Obsoleted by RFC 3232) -- Possible downref: Non-RFC (?) normative reference: ref. 'BUNDLING' -- Possible downref: Non-RFC (?) normative reference: ref. 'FLOOD' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLS' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLS-OSPF' -- Possible downref: Non-RFC (?) normative reference: ref. 'IANAFamily' -- Possible downref: Non-RFC (?) normative reference: ref. 'LMP' -- Possible downref: Non-RFC (?) normative reference: ref. 'OSPF' -- 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: 8 errors (**), 0 flaws (~~), 5 warnings (==), 17 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Martin Dubuc 3 Internet Draft Editor 4 Expires: May 2003 5 Sudheer Dharanikota 7 Thomas D. Nadeau 8 Cisco Systems 10 Jonathan P. Lang 11 Calient Networks 13 November 2002 15 Link Bundling Management Information Base 17 draft-ietf-mpls-bundle-mib-04.txt 19 Status of this Memo 21 This document is an Internet-Draft and is in full conformance with 22 all provisions of Section 10 of RFC 2026. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF), its areas, and its working groups. Note that other 26 groups may also distribute working documents as Internet- Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet- Drafts as reference 31 material or to cite them other than as "work in progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/ietf/1id-abstracts.txt. 36 The list of Internet-Draft Shadow Directories can be accessed at 37 http://www.ietf.org/shadow.html. 38 Table of Contents 40 1. Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 41 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 42 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 43 4. The SNMP Management Framework . . . . . . . . . . . . . . . . . 3 44 5. Feature Checklist . . . . . . . . . . . . . . . . . . . . . . . 4 45 6. Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 46 6.1. Summary of Link Bundling MIB . . . . . . . . . . . . . . . . . 5 47 7. Brief Description of MIB Objects . . . . . . . . . . . . . . . 6 48 7.1. teLinkTable . . . . . . . . . . . . . . . . . . . . . . . . . . 6 49 7.2. teLinkDescriptorTable . . . . . . . . . . . . . . . . . . . . . 6 50 7.3. teLinkOspfTeTable . . . . . . . . . . . . . . . . . . . . . . . 6 51 7.4. teLinkSrlgTable . . . . . . . . . . . . . . . . . . . . . . . . 6 52 7.5. teLinkBandwidthTable . . . . . . . . . . . . . . . . . . . . . 6 53 7.6. componentLinkTable . . . . . . . . . . . . . . . . . . . . . . 6 54 7.7. componentLinkDescriptorTable . . . . . . . . . . . . . . . . . 6 55 7.8. componentLinkBandwidthTable . . . . . . . . . . . . . . . . . . 6 56 8. Example of Bundled Link Setup . . . . . . . . . . . . . . . . . 6 57 9. Application of the Interfaces Group to TE Links . . . . . . . . 10 58 9.1 Support of the TE Link Layer by ifTable . . . . . . . . . . . . 11 59 9.2 Using ifStackTable . . . . . . . . . . . . . . . . . . . . . . 12 60 10. Link Bundling MIB Definitions . . . . . . . . . . . . . . . . . 14 61 11. Intellectual Property Considerations . . . . . . . . . . . . . 47 62 12. Security Considerations . . . . . . . . . . . . . . . . . . . . 47 63 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 48 64 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 49 65 14.1 Normative References . . . . . . . . . . . . . . . . . . . . . 49 66 14.2 Informative References . . . . . . . . . . . . . . . . . . . . 50 67 15. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 52 68 16. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 52 70 1. Abstract 72 This memo defines a portion of the Management Information Base (MIB) 73 for use with network management protocols in the Internet community. 74 In particular, it describes managed objects for modeling link 75 bundling as described in the Link Bundling in MPLS Traffic Engineer- 76 ing Internet Draft. 78 2. Introduction 80 OSPF [OSPF], Generalized MPLS (GMPLS) [GMPLS] and the Link Management 81 Protocol (LMP) [LMP] use the concept of traffic engineering (TE) 82 links to abstract link properties. The effect of this approach is the 83 reduction of the amount of routing information exchanged in the net- 84 work, which improves routing scalability. In addition, the use of TE 85 link allows the implementation of new capabilities such as link pro- 86 tection. 88 We present in this document a MIB that can be used to manage TE links 89 and their extension, the bundled link. This MIB enable both the con- 90 figuration and the performance monitoring of TE links and bundled 91 link. 93 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 94 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 95 document are to be interpreted as described in RFC 2119, reference 96 [RFC2119]. 98 3. Terminology 100 This document uses terminology from the documents describing link 101 bundling [BUNDLING] and G-MPLS [GMPLS-ARCH]. 103 The link bundling feature is designed to aggregate one or more simi- 104 lar entities between a node pair into a bundled link [BUNDLING]. In 105 the document, those entities are referred to as TE links. A TE link 106 is a subinterface capable of carrying MPLS traffic engineered traf- 107 fic. A TE Link may be comprised of only one underlying component 108 links. In cases where more than one component link is to be com- 109 bined, multiple component links should be created with differing pri- 110 orities to indicate hot-standby or parallel utilization. 112 A bundled link is just another kind of Traffic Engineering (TE) link 113 (see [GMPLS-OSPF]). A link bundle is a subinterface which bonds the 114 traffic of a group of one or more TE links. There should be more than 115 one TE Link in a link bundle, but this is not a requirement. Fur- 116 thermore, if there are more than one TE link in a link bundle at some 117 time, and at some point later, all but one of the links are deleted, 118 the agent may choose to either delete the link bundle, or it may 119 choose to leave it intact. Traffic counters on a link bundle are 120 cumulative for all subinterfaces which it binds together. 122 4. The SNMP Management Framework 124 The SNMP Management Framework presently consists of five major compo- 125 nents: 127 - An overall architecture, described in RFC 2571 [RFC2571]. 129 Mechanisms for describing and naming objects and events for the 130 purpose of management. The first version of this Structure of 131 Management Information (SMI) is called SMIv1 and described in 132 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 133 1215 [RFC1215]. The second version, called SMIv2, is described 134 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 135 STD 58, RFC 2580 [RFC2580]. 137 - Message protocols for transferring management information. The 138 first version of the SNMP message protocol is called SNMPv1 and 139 described in STD 15, RFC 1157 [RFC1157]. A second version of 140 the SNMP message protocol, which is not an Internet standards 141 track protocol, is called SNMPv2c and described in RFC 1901 142 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 143 message protocol is called SNMPv3 and described in RFC 1906 144 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 146 - Protocol operations for accessing management information. The 147 first set of protocol operations and associated PDU formats is 148 described in STD 15, RFC 1157 [RFC1157]. A second set of 149 protocol operations and associated PDU formats is described in 150 RFC 1905 [RFC1905]. 152 - A set of fundamental applications described in RFC 2573 153 [RFC2573] and the view-based access control mechanism described 154 in RFC 2575 [RFC2575]. 156 A more detailed introduction to the current SNMP Management Framework 157 can be found in RFC 2570 [RFC2570]. 159 Managed objects are accessed via a virtual information store, termed 160 the Management Information Base or MIB. Objects in the MIB are 161 defined using the mechanisms defined in the SMI. 163 This memo specifies a MIB module that is compliant to the SMIv2. A 164 MIB conforming to the SMIv1 can be produced through the appropriate 165 translations. The resulting translated MIB must be semantically 166 equivalent, except where objects or events are omitted because no 167 translation is possible (use of Counter64). Some machine readable 168 information in SMIv2 will be converted into textual descriptions in 169 SMIv1 during the translation process. However, this loss of machine 170 readable information is not considered to change the semantics of the 171 MIB. 173 5. Feature Checklist 175 The link bundling MIB (LINK-BUNDLING-MIB) is designed to satisfy the 176 following requirements and constraints: 178 - The MIB supports the management of TE links, including bundled 179 links. 181 - Support is provided for configuration of traffic engineering 182 parameters associated with TE links. 184 - The MIB is used to monitor the priority-based component link 185 and TE link bandwidth values. 187 6. Outline 189 Configuring bundled links involves the following steps: 191 - Creating a bundled link. 193 - Creating TE links. 195 - Optionally specifying the shared risk link groups associated with 196 the TE links. 198 - Configuring the component links including the bandwidth 199 parameters and associating the component links with the 200 appropriate TE link. 202 - Associating the TE links with the appropriate bundled link. 204 6.1. Summary of Link Bundling MIB 206 The MIB objects for performing these actions consist of the following 207 tables: 209 - The TE link table (teLinkTable), which is used to 210 specify TE links, including bundled links, and their generic 211 traffic engineering parameters. 213 - The TE link descriptor table (teLinkDescriptorTable), which is 214 used to enumerate the TE link descriptors. 216 - The TE link OSPF traffic engineering table 217 (teLinkOspfTeTable), which is used for configuring OSPF 218 traffic engineering parameters associated with TE links. 220 - The shared risk link group (SRLG) table (teLinkSrlgTable), 221 which is used to specify the SRLGs associated with TE links. 223 - The TE link bandwidth table (teLinkBandwidthTable), 224 which is used for reporting priority-based bandwidth values 225 associated with TE links. 227 - The component link table (componentLinkTable), which is 228 used to identify the component links that are associated 229 with the TE links and specify the component link generic 230 traffic engineering parameters. 232 - The component link descriptor table 233 (componentLinkDescriptorTable), which is used to enumerate 234 the component link descriptors. 236 - The component link bandwidth table 237 (componentLinkBandwidthTable), which is used to report 238 priority-based bandwidth values associated with component links. 240 These tables are described in the subsequent sections. 242 7. Brief Description of MIB Objects 244 Sections 7.1-7.5 describe objects pertaining to TE links. The MIB 245 objects were derived from the link bundling document [BUNDLING]. 247 7.1. teLinkTable 249 This table represents the TE links, including bundled links. 251 7.2. teLinkDescriptorTable 253 This table represents the TE link descriptors. 255 7.3. teLinkOspfTeTable 257 This table represents the OSPF traffic engineering parameters that 258 are associated with the TE links. 260 7.4. teLinkSrlgTable 262 This table represents the shared risk link groups (SRLGs) associated 263 with TE links. 265 7.5. teLinkBandwidthTable 267 This table specifies the priority-based bandwidth traffic engineering 268 parameters associated with TE links. 270 7.6. componentLinkTable 272 This table enumerates the component links and their association with 273 TE link. 275 7.7. componentLinkDescriptorTable 277 This table enumerates the link descriptors that each component link 278 supports. 280 7.8. componentLinkBandwidthTable 282 The component link bandwidth table specifies the priority-based band- 283 width values associated with the component links. 285 8. Example of Bundled Link Setup 287 In this section we provide a brief example of using the MIB 288 objects described in section 10 to set up a bundled link. 289 While this example is not meant to illustrate every 290 nuance of the MIB, it is intended as an aid to understanding some 291 of the key concepts. It is meant to be read after going through the 292 MIB itself. 294 Suppose that one would like to manually create a bundled link 295 out of two 1:1 TE links. Assume that the bundled link is associated 296 with SRLGs 10 and 50. Finally, let the component links be port 297 entity interfaces (lambdas). The following example illustrates which 298 rows and corresponding objects might be created to accomplish this. 300 First, a bundled link entry is created. An ifEntry with the same 301 ifIndex and with ifType teLink needs to be created beforehand. 303 In teLinkTable: 304 { 305 ifIndex = 25, 306 teLinkIpAddrType = unknown(0), 307 teLinkRowStatus = createAndGo(4) 308 } 310 In ifStackTable: 311 { 312 ifStackHigherLayer = 0, 313 ifStackLowerLayer = 25, 314 ifStackStatus = createAndGo(4) 315 } 317 Next, the two TE links are created. 319 In teLinkTable: 320 { 321 ifIndex = 20, 322 teLinkIpAddrType = unknown(0), 323 teLinkMetric = 5, 324 teLinkResourceClass = 3, 325 teLinkRowStatus = createAndWait(5) 326 } 328 In ifStackTable: 329 { 330 ifStackHigherLayer = 25, 331 ifStackLowerLayer = 20, 332 ifStackStatus = createAndGo(4) 334 } 336 In teLinkTable: 337 { 338 ifIndex = 21, 339 teLinkIpAddrType = unknown(0), 340 teLinkMetric = 5, 341 teLinkResourceClass = 3, 342 teLinkRowStatus = createAndWait(5) 343 } 345 In ifStackTable: 346 { 347 ifStackHigherLayer = 25, 348 ifStackLowerLayer = 21, 349 ifStackStatus = createAndGo(4) 350 } 352 The OSPF traffic engineering parameters are configured for the 353 TE links. 355 In teLinkOspfTeTable: 356 { 357 ifIndex = 20, 358 teLinkOspfLinkId = 'c0010101'H, -- 192.1.1.1 359 teLinkRowStatus = createAndGo(4) 360 } 362 In teLinkOspfTeTable: 363 { 364 ifIndex = 21, 365 teLinkOspfLinkId = 'c0010101'H, -- 192.1.1.1 366 teLinkRowStatus = createAndGo(4) 367 } 369 We assign SRLGs to the TE links. 371 In the teLinkSrlgTable: 372 { 373 ifIndex = 20, 374 srlg = 10, 375 srlgRowStatus = createAndGo(4) 376 } 378 In the teLinkSrlgTable: 379 { 380 ifIndex = 21, 381 srlg = 50, 382 srlgRowStatus = createAndGo(4) 383 } 385 The bundled link inherits the OSPF and SRLG properties from the 386 associated TE links. 388 Next, for each TE link, two component links are created. 389 An ifEntry with the same ifIndex needs to be created beforehand. 391 In componentLinkTable: 392 { 393 ifIndex = 40, 394 componentLinkPreferredProtection = primary(1), 395 componentLinkRowStatus = createAndGo(4) 396 } 398 In ifStackTable: 399 { 400 ifStackHigherLayer = 20, 401 ifStackLowerLayer = 40, 402 ifStackStatus = createAndGo(4) 403 } 405 In componentLinkTable: 406 { 407 ifIndex = 43, 408 componentLinkPreferredProtection = secondary(2), 409 componentLinkRowStatus = createAndGo(4) 410 } 412 In ifStackTable: 413 { 414 ifStackHigherLayer = 20, 415 ifStackLowerLayer = 43, 416 ifStackStatus = createAndGo(4) 417 } 419 In componentLinkTable: 420 { 421 ifIndex = 44, 422 componentLinkPreferredProtection = primary(1), 423 componentLinkRowStatus = createAndGo(4) 424 } 426 In ifStackTable: 427 { 428 ifStackHigherLayer = 21, 429 ifStackLowerLayer = 44, 430 ifStackStatus = createAndGo(4) 431 } 433 In componentLinkTable: 434 { 435 ifIndex = 48, 436 componentLinkPreferredProtection = secondary(2), 437 componentLinkRowStatus = createAndGo(4) 438 } 440 In ifStackTable: 441 { 442 ifStackHigherLayer = 21, 443 ifStackLowerLayer = 48, 444 ifStackStatus = createAndGo(4) 445 } 447 In this example, once a component link is added to the 448 componentLinkTable, the associated link descriptors are 449 implicitly added to the componentLinkDescriptorTable. 451 TE link link descriptors are derived from their component link 452 descriptors. 454 Note that the bandwidth attributes in teLinkDescriptorTable, 455 componentLinkDescriptorTable, teLinkBandwidthTable 456 and componentLinkBandwidthTable are maintained by the 457 device according to LSP creation/deletion at different priorities. 458 The values in the teLinkBandwidthTable are an aggregation 459 of the values for the component links of the TE links and 460 the TE links of the bundled link. 462 9. Application of the Interfaces Group to TE Links 464 The Interfaces Group [RFC2863] defines generic managed objects for 465 managing interfaces. This memo contains the media-specific 466 extensions to the Interfaces Group for managing TE Link interfaces 467 as logical interfaces. 469 This memo assumes the interpretation of the Interfaces Group to be 470 in accordance with [RFC2863] which states that the interfaces table 471 (ifTable) contains information on the managed resource's 472 interfaces and that each sub-layer below the internetwork layer of 473 a network interface is considered an interface. Thus, the TE Link 474 interface is represented as an entry in the ifTable. The inter- 475 relation of entries in the ifTable is defined by Interfaces Stack 476 Group defined in [RFC2863]. 478 When using TE Link interfaces, the interface stack table might appear 479 as follows: 481 +----------------------------------------+ 482 | TE link-interface ifType = teLink(200) + 483 +----------------------------------------+ 484 | Underlying Layer... + 485 +----------------------------------------+ 487 In the above diagram, "Underlying Layer..." refers to the ifIndex 488 of any interface type, which has been defined for TE Link 489 interworking. Examples include ATM, Frame Relay, Ethernet, etc. 491 9.1. Support of the TE Link Layer by ifTable 493 Some specific interpretations of ifTable for the TE Link layer 494 follow. 496 Object Use for the TE Link layer 498 ifIndex Each TE Link interface is represented by an ifEntry. 500 ifDescr Description of the TE Link interface. 502 ifType The value that is allocated for TE Link is 200 503 [IANAFamily]. 505 ifSpeed The total bandwidth in bits per second for use by 506 the TE Link layer. 508 ifPhysAddress Unused. 510 ifAdminStatus This variable indicates the administrator's intent 511 as to whether TE Link should be enabled, disabled, or 512 running in some diagnostic testing mode on this 513 interface. Also see [RFC2863]. 515 ifOperStatus This value reflects the actual or operational 516 status of TE Link on this interface. 518 ifLastChange See [RFC2863]. 520 ifInOctets The number of received octets over the interface, 521 i.e., the number of received octets in all component 522 links associated with the interface. 524 ifOutOctets The number of transmitted octets over the 525 interface, i.e., the number of octets transmitted 526 over all component links associated with the 527 interface. 529 ifInErrors The number of packets dropped due to 530 uncorrectable errors. 532 ifInUnknownProtos 533 The number of received packets discarded during 534 packet header validation. 536 ifOutErrors See [RFC2863]. 538 ifName Textual name (unique on this system) of the 539 interface or an octet string of zero length. 541 ifLinkUpDownTrapEnable 542 Default is disabled (2). 544 ifConnectorPresent 545 Set to false (2). 547 ifHighSpeed See [RFC2863]. 549 ifHCInOctets The 64-bit version of ifInOctets; supported if 550 required by the compliance statements in [RFC2863]. 552 ifHCOutOctets The 64-bit version of ifOutOctets; supported if 553 required by the compliance statements in [RFC2863]. 555 ifAlias The non-volatile 'alias' name for the interface as 556 specified by a network manager. 558 ifCounterDiscontinuityTime 559 See [RFC2863]. 561 Support for ifInOctets, ifOutOctets, ifInErrors, ifInUnknownProtos, 562 ifOutErrors, ifHCInOctets and ifHCOutOctets objects is not required 563 if encoding type is clear. For other encoding types, traffic 564 counters on a TE link are cumulative for all subinterfaces which it 565 binds together. 567 9.2. Using ifStackTable 569 This section describes by example how to use ifStackTable to 570 represent the relationship of TE links with underlying TE-enabled 571 interfaces. Implementors of the stack table for TE link interfaces 572 should look at the appropriate RFC for the service being stacked 573 on TE links. Examples given below are for illustration purposes 574 only. 576 Example: MPLS is being carried on 2 bundled TE links. 577 Each bundled TE link runs over a 1:1 optical 578 transport interface. 580 +---------------------------------+ 581 | mpls | 582 +---------------------------------+ 583 | 584 +---------------------------------+ 585 | teLink (Link Bundle) | 586 +---------------------------------+ 587 | | 588 +---------------+ +---------------+ 589 | teLink | | teLink | 590 +---------------+ +---------------+ 591 | | | | 592 +------+ +------+ +------+ +------+ 593 |oTrans| |oTrans| |oTrans| |oTrans| 594 +------+ +------+ +------+ +------+ 596 The assignment of the index values could for example be: 598 ifIndex Description 599 1 mpls (type 166) 600 2 teLink (type 200) 601 3 teLink (type 200) 602 4 teLink (type 200) 603 5 opticalTransport (type 196) 604 6 opticalTransport (type 196) 605 7 opticalTransport (type 196) 606 8 opticalTransport (type 196) 608 The ifStackTable is then used to show the relationships between the 609 various interfaces. 611 ifStackTable Entries 613 HigherLayer LowerLayer 614 0 1 615 1 2 616 2 3 617 2 4 618 3 5 619 3 6 620 4 7 621 4 8 622 5 0 623 6 0 624 7 0 625 8 0 627 In the case where MPLS is using a single TE link, then 628 the upper TE link layer (link bundle) is not required. 630 +---------------+ 631 | mpls | 632 +---------------+ 633 | 634 +---------------+ 635 | teLink | 636 +---------------+ 637 | | 638 +------+ +------+ 639 |oTrans| |oTrans| 640 +------+ +------+ 642 The assignment of the index values could for example be: 644 ifIndex Description 645 1 mpls (type 166) 646 2 teLink (type 200) 647 3 opticalTransport (type 196) 648 4 opticalTransport (type 196) 650 The ifStackTable is then used to show the relationships between the 651 various interfaces. 653 ifStackTable Entries 655 HigherLayer LowerLayer 656 0 1 657 1 2 658 2 3 659 2 4 660 3 0 661 4 0 663 10. Link Bundling MIB Definitions 665 LINK-BUNDLING-MIB DEFINITIONS ::= BEGIN 667 IMPORTS 668 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 669 mib-2, Unsigned32 670 FROM SNMPv2-SMI 672 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 673 FROM SNMPv2-CONF 675 TruthValue, RowStatus, StorageType 676 FROM SNMPv2-TC 678 InterfaceIndexOrZero, ifIndex 679 FROM IF-MIB 681 RouterID 682 FROM OSPF-MIB 684 InetAddressType, InetAddress 685 FROM INET-ADDRESS-MIB; 687 linkBundlingMIB MODULE-IDENTITY 688 LAST-UPDATED "200211011200Z" -- 1 November 2002 12:00:00 EST 689 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 690 CONTACT-INFO 691 " Martin Dubuc 692 Email: dubuc.consulting@rogers.com 694 Sudheer Dharanikota 695 Email: sudheer@ieee.org 697 Thomas D. Nadeau 698 Postal: Cisco Systems, Inc. 699 300 Apollo Drive 700 Chelmsford, MA 01824 701 Tel: +1-978-244-3051 702 Email: tnadeau@cisco.com 704 Jonathan P. Lang 705 Postal: Calient Networks, Inc. 706 25 Castilian Drive 707 Goleta, CA 93117 708 Email: jplang@calient.net" 710 DESCRIPTION 711 "This MIB contains managed object definitions for 712 MPLS traffic engineering link bundling as 713 defined in: Kompella, K., Rekhter, Y., Berger, L., 714 Link Bundling in MPLS Traffic Engineering 715 Internet Draft , 716 July 2002." 718 -- Revision history. 719 REVISION 720 "200211011200Z" -- 1 November 2002 12:00:00 EST 721 DESCRIPTION 722 "Initial version published as RFC xxxx (to be assigned by RFC Editor)" 723 ::= { mib-2 xxx } -- To be assigned by IANA (experimental 114 can be used 724 -- in the interim) 726 -- Textual Conventions 728 -- Top level components of this MIB 730 -- Notifications 731 linkBundlingNotifications OBJECT IDENTIFIER ::= { linkBundlingMIB 0 } 732 -- Tables, Scalars 733 linkBundlingObjects OBJECT IDENTIFIER ::= { linkBundlingMIB 1 } 734 -- Conformance 735 linkBundlingConformance OBJECT IDENTIFIER ::= { linkBundlingMIB 2 } 737 -- TE Link Table 739 teLinkTable OBJECT-TYPE 740 SYNTAX SEQUENCE OF TeLinkEntry 741 MAX-ACCESS not-accessible 742 STATUS current 743 DESCRIPTION 744 "This table specifies the grouping of component links into 745 TE links and grouping of TE links into bundled links." 746 ::= { linkBundlingObjects 1 } 748 teLinkEntry OBJECT-TYPE 749 SYNTAX TeLinkEntry 750 MAX-ACCESS not-accessible 751 STATUS current 752 DESCRIPTION 753 "An entry in this table exists for each ifEntry with an 754 ifType of teLink(TBD), i.e. for every TE link. An ifEntry 755 in the ifTable must exist before a teLinkEntry is created with 756 the corresponding ifIndex. If a TE link entry in the ifTable is 757 destroyed, then so is the corresponding entry in the 758 teLinkTable. The administrative and operational status values 759 are controlled from the ifEntry. If the link is unnumbered, 760 ifIndex is also used as the outgoing interface identifier." 761 INDEX { ifIndex } 762 ::= { teLinkTable 1 } 764 TeLinkEntry ::= SEQUENCE { 765 teLinkIpAddrType InetAddressType, 766 teLinkIpAddr InetAddress, 767 teLinkRemoteIpAddr InetAddress, 768 teLinkMetric Unsigned32, 769 teLinkMuxCapability INTEGER, 770 teLinkProtectionType INTEGER, 771 teLinkWorkingPriority Unsigned32, 772 teLinkResourceClass Unsigned32, 773 teLinkIncomingIfId InterfaceIndexOrZero, 774 teLinkOutgoingIfId InterfaceIndexOrZero, 775 teLinkFlooding InterfaceIndexOrZero, 776 teLinkRowStatus RowStatus, 777 teLinkStorageType StorageType 778 } 780 teLinkIpAddrType OBJECT-TYPE 781 SYNTAX InetAddressType 782 MAX-ACCESS read-create 783 STATUS current 784 DESCRIPTION 785 "For IPv4 and IPv6 numbered links, this object represents the 786 IP address type associated with the TE link. For 787 unnumbered links, a value of unknown(0) must be used." 788 ::= { teLinkEntry 1 } 790 teLinkIpAddr OBJECT-TYPE 791 SYNTAX InetAddress 792 MAX-ACCESS read-create 793 STATUS current 794 DESCRIPTION 795 "For IPv4 and IPv6 numbered links, this object represents the 796 IP address associated with the TE link." 797 ::= { teLinkEntry 2 } 799 teLinkRemoteIpAddr OBJECT-TYPE 800 SYNTAX InetAddress 801 MAX-ACCESS read-create 802 STATUS current 803 DESCRIPTION 804 "The remote IP address associated with the TE link (IPv4 and 805 IPv6 numbered links)." 806 ::= { teLinkEntry 3 } 808 teLinkMetric OBJECT-TYPE 809 SYNTAX Unsigned32 810 MAX-ACCESS read-create 811 STATUS current 812 DESCRIPTION 813 "The traffic engineering metric for the TE link is 814 derived from its component links. All component links 815 within the TE link must have the same traffic 816 engineering metric." 817 REFERENCE 818 "[BUNDLING]" 819 ::= { teLinkEntry 4 } 821 teLinkMuxCapability OBJECT-TYPE 822 SYNTAX INTEGER { 823 packetSwitch1(1), 824 packetSwitch2(2), 825 packetSwitch3(3), 826 packetSwitch4(4), 827 layer2Switch(51), 828 tdm(100), 829 lambdaSwitch(150), 830 fiberSwitch(200) 831 } 832 MAX-ACCESS read-create 833 STATUS current 834 DESCRIPTION 835 "This attribute specifies link multiplex capability of the 836 TE link, which is derived from its component links. All 837 component links within the same TE link must have the 838 same link multiplex capability." 839 REFERENCE 840 "[GMPLS-OSPF]" 841 ::= { teLinkEntry 5 } 843 teLinkProtectionType OBJECT-TYPE 844 SYNTAX INTEGER { 845 extraTraffic(1), 846 unprotected(2), 847 shared(3), 848 dedicated1For1(4), 849 dedicated1Plus1(5), 850 enhanced(6) 851 } 852 MAX-ACCESS read-create 853 STATUS current 854 DESCRIPTION 855 "This attribute specifies link protection type of the 856 TE link." 857 REFERENCE 858 "[GMPLS-OSPF]" 859 ::= { teLinkEntry 6 } 861 teLinkWorkingPriority OBJECT-TYPE 862 SYNTAX Unsigned32 (0..7) 863 MAX-ACCESS read-create 864 STATUS current 865 DESCRIPTION 866 "This object represents a priority value such that a new 867 connection with a higher priority, i.e. numerically lower than 868 this value, is guaranteed to be setup on a primary link and 869 not on a secondary link." 870 REFERENCE 871 "[GMPLS-OSPF]" 872 ::= { teLinkEntry 7 } 874 teLinkResourceClass OBJECT-TYPE 875 SYNTAX Unsigned32 876 MAX-ACCESS read-create 877 STATUS current 878 DESCRIPTION 879 "This attribute specifies the TE link resource class. 880 The resource class is a 32 bit bitfield. The resource class for 881 a link bundle is derived from the resource class of its 882 TE links. All TE links within a link bundle must have the 883 same resource class." 884 ::= { teLinkEntry 8 } 886 teLinkIncomingIfId OBJECT-TYPE 887 SYNTAX InterfaceIndexOrZero 888 MAX-ACCESS read-create 889 STATUS current 890 DESCRIPTION 891 "For unnumbered links, the incoming interface is set to the 892 outgoing interface identifier chosen by the neighboring LSR 893 for the reverse link corresponding to this TE link." 894 REFERENCE 895 "[BUNDLING]" 896 ::= { teLinkEntry 9 } 898 teLinkOutgoingIfId OBJECT-TYPE 899 SYNTAX InterfaceIndexOrZero 900 MAX-ACCESS read-create 901 STATUS current 902 DESCRIPTION 903 "If the link is unnumbered, the outgoing interface identifier is 904 set to the outgoing interface identifier chosen for the TE link 905 by the advertising LSR." 907 REFERENCE 908 "[BUNDLING]" 909 ::= { teLinkEntry 10 } 911 teLinkFlooding OBJECT-TYPE 912 SYNTAX InterfaceIndexOrZero 913 MAX-ACCESS read-create 914 STATUS current 915 DESCRIPTION 916 "This object only has significance for link bundles which 917 encoding type is not clear. For these link bundles, this object 918 identifies the TE link on which to restrict flooding. If the 919 value is zero, then flooding must be done on all TE links 920 within the link bundle." 921 REFERENCE 922 "[FLOOD]" 923 DEFVAL { 0 } 924 ::= { teLinkEntry 11 } 926 teLinkRowStatus OBJECT-TYPE 927 SYNTAX RowStatus 928 MAX-ACCESS read-create 929 STATUS current 930 DESCRIPTION 931 "This variable is used to create, modify, and/or 932 delete a row in this table. All read-create objects 933 can only be changed when teLinkRowStatus is active." 934 ::= { teLinkEntry 12 } 936 teLinkStorageType OBJECT-TYPE 937 SYNTAX StorageType 938 MAX-ACCESS read-create 939 STATUS current 940 DESCRIPTION 941 "The storage type for this conceptual row in the 942 teLinkTable. Conceptual rows having the value 943 'permanent' need not allow write-access to any 944 columnar object in the row." 945 ::= { teLinkEntry 13 } 947 -- End of teLinkTable 949 -- TE Link Descriptor Table 951 teLinkDescriptorTable OBJECT-TYPE 952 SYNTAX SEQUENCE OF TeLinkDescriptorEntry 953 MAX-ACCESS not-accessible 954 STATUS current 955 DESCRIPTION 956 "This table specifies the link descriptors associated with the 957 TE links." 958 ::= { linkBundlingObjects 2 } 960 teLinkDescriptorEntry OBJECT-TYPE 961 SYNTAX TeLinkDescriptorEntry 962 MAX-ACCESS not-accessible 963 STATUS current 964 DESCRIPTION 965 "An entry in this table is created for every TE link descriptor. 966 An ifEntry in the ifTable must exist before a 967 teLinkDescriptorEntry using the same ifIndex is created. 968 If a TE link entry in the ifTable is destroyed, then so are all 969 entries in the teLinkDescriptorTable that use the ifIndex of 970 this TE link." 971 INDEX { ifIndex, teLinkDescriptorId } 972 ::= { teLinkDescriptorTable 1 } 974 TeLinkDescriptorEntry ::= SEQUENCE { 975 teLinkDescriptorId Unsigned32, 976 teLinkEncodingType INTEGER, 977 teLinkDescrPriority Unsigned32, 978 teLinkMinReservableBandwidth Unsigned32, 979 teLinkMaxReservableBandwidth Unsigned32, 980 teLinkDescrRowStatus RowStatus, 981 teLinkDescrStorageType StorageType 982 } 984 teLinkDescriptorId OBJECT-TYPE 985 SYNTAX Unsigned32 986 MAX-ACCESS not-accessible 987 STATUS current 988 DESCRIPTION 989 "This object specifies the link descriptor identifier." 990 ::= { teLinkDescriptorEntry 1 } 992 teLinkEncodingType OBJECT-TYPE 993 SYNTAX INTEGER { 994 packet(1), 995 ethernet(2), 996 ansiEtsiPdh(3), 997 sdhItuSonetAnsi(5), 998 digitalWrapper(7), 999 lambda(8), 1000 fiber(9), 1001 fiberChannel(11) 1003 } 1004 MAX-ACCESS read-create 1005 STATUS current 1006 DESCRIPTION 1007 "This attribute specifies the TE link encoding type." 1008 REFERENCE 1009 "[GMPLS]" 1010 ::= { teLinkDescriptorEntry 2 } 1012 teLinkDescrPriority OBJECT-TYPE 1013 SYNTAX Unsigned32 (0..7) 1014 MAX-ACCESS read-create 1015 STATUS current 1016 DESCRIPTION 1017 "This object specifies the lowest priority at which that link 1018 encoding type is available." 1019 REFERENCE 1020 "[GMPLS-OSPF]" 1021 ::= { teLinkDescriptorEntry 3 } 1023 teLinkMinReservableBandwidth OBJECT-TYPE 1024 SYNTAX Unsigned32 1025 MAX-ACCESS read-create 1026 STATUS current 1027 DESCRIPTION 1028 "This attribute specifies the minimum reservable bandwidth on 1029 the TE link. This is derived from the union of the 1030 minimum reservable bandwidth of all the component links 1031 associated with the TE link that can be used to carry 1032 live traffic. This value is an estimate in units of 1,000 bits 1033 per second." 1034 REFERENCE 1035 "[GMPLS-OSPF]" 1036 ::= { teLinkDescriptorEntry 4 } 1038 teLinkMaxReservableBandwidth OBJECT-TYPE 1039 SYNTAX Unsigned32 1040 MAX-ACCESS read-create 1041 STATUS current 1042 DESCRIPTION 1043 "This attribute specifies the maximum reservable bandwidth on 1044 the TE link. This is the union of the maximum reservable 1045 bandwidth of all the component links within the 1046 TE link that can be used to carry live traffic. This value 1047 is an estimate in units of 1,000 bits per second." 1048 REFERENCE 1049 "[GMPLS-OSPF]" 1050 ::= { teLinkDescriptorEntry 5 } 1052 teLinkDescrRowStatus OBJECT-TYPE 1053 SYNTAX RowStatus 1054 MAX-ACCESS read-create 1055 STATUS current 1056 DESCRIPTION 1057 "This variable is used to create, modify, and/or 1058 delete a row in this table. All read-create objects 1059 can only be changed when teLinkDescrRowStatus is active." 1060 ::= { teLinkDescriptorEntry 6 } 1062 teLinkDescrStorageType OBJECT-TYPE 1063 SYNTAX StorageType 1064 MAX-ACCESS read-create 1065 STATUS current 1066 DESCRIPTION 1067 "The storage type for this conceptual row in the 1068 teLinkDescriptorTable. Conceptual rows having the value 1069 'permanent' need not allow write-access to any 1070 columnar object in the row." 1071 ::= { teLinkDescriptorEntry 7 } 1073 -- End of teLinkDescriptorTable 1075 -- OSPF Traffic Engineering Parameters for TE Links 1077 teLinkOspfTeTable OBJECT-TYPE 1078 SYNTAX SEQUENCE OF TeLinkOspfTeEntry 1079 MAX-ACCESS not-accessible 1080 STATUS current 1081 DESCRIPTION 1082 "This table specifies the OSPF traffic engineering information 1083 associated with TE links." 1084 ::= { linkBundlingObjects 3 } 1086 teLinkOspfTeEntry OBJECT-TYPE 1087 SYNTAX TeLinkOspfTeEntry 1088 MAX-ACCESS not-accessible 1089 STATUS current 1090 DESCRIPTION 1091 "If OSPF is enabled, an entry in this table is created for 1092 every TE link." 1093 AUGMENTS { teLinkEntry } 1094 ::= { teLinkOspfTeTable 1 } 1096 TeLinkOspfTeEntry ::= SEQUENCE { 1097 teLinkOspfLinkType INTEGER, 1098 teLinkOspfLinkId RouterID 1100 } 1102 teLinkOspfLinkType OBJECT-TYPE 1103 SYNTAX INTEGER { 1104 pointToPoint(1), 1105 multiAccess(2) 1106 } 1107 MAX-ACCESS read-create 1108 STATUS current 1109 DESCRIPTION 1110 "This attribute specifies the OSPF link type for the TE link. 1111 All TE links within the same bundle must have the same 1112 link type." 1113 ::= { teLinkOspfTeEntry 1 } 1115 teLinkOspfLinkId OBJECT-TYPE 1116 SYNTAX RouterID 1117 MAX-ACCESS read-create 1118 STATUS current 1119 DESCRIPTION 1120 "On point-to-point link, the link identifier is the Router ID 1121 of the neighbor. For bundled link, is derived from the link 1122 identifier associated with its TE links." 1123 REFERENCE 1124 "[BUNDLING]" 1125 ::= { teLinkOspfTeEntry 2 } 1127 -- End of teLinkOspfTeTable 1129 -- TE Link Shared Risk Link Group Table 1131 teLinkSrlgTable OBJECT-TYPE 1132 SYNTAX SEQUENCE OF TeLinkSrlgEntry 1133 MAX-ACCESS not-accessible 1134 STATUS current 1135 DESCRIPTION 1136 "This table specifies the SRLGs associated with TE links." 1137 ::= { linkBundlingObjects 4 } 1139 teLinkSrlgEntry OBJECT-TYPE 1140 SYNTAX TeLinkSrlgEntry 1141 MAX-ACCESS not-accessible 1142 STATUS current 1143 DESCRIPTION 1144 "An entry in this table contains information about a 1145 SRLG associated with a TE link. 1146 An ifEntry in the ifTable must exist before a 1147 teLinkSrlgEntry using the same ifIndex is created. 1148 If a TE link entry in the ifTable is destroyed, then so are all 1149 entries in the teLinkSrlgTable that use the ifIndex of 1150 this TE link." 1151 INDEX { ifIndex, srlg } 1152 ::= { teLinkSrlgTable 1 } 1154 TeLinkSrlgEntry ::= SEQUENCE { 1155 srlg Unsigned32, 1156 srlgRowStatus RowStatus, 1157 srlgStorageType StorageType 1158 } 1160 srlg OBJECT-TYPE 1161 SYNTAX Unsigned32 1162 MAX-ACCESS not-accessible 1163 STATUS current 1164 DESCRIPTION 1165 "This identifies a SRLG supported by the TE link." 1166 REFERENCE 1167 "[GMPLS-OSPF]" 1168 ::= { teLinkSrlgEntry 1 } 1170 srlgRowStatus OBJECT-TYPE 1171 SYNTAX RowStatus 1172 MAX-ACCESS read-create 1173 STATUS current 1174 DESCRIPTION 1175 "This variable is used to create, modify, and/or 1176 delete a row in this table. All read-create objects 1177 can only be changed when srlgRowStatus is active." 1178 ::= { teLinkSrlgEntry 2 } 1180 srlgStorageType OBJECT-TYPE 1181 SYNTAX StorageType 1182 MAX-ACCESS read-create 1183 STATUS current 1184 DESCRIPTION 1185 "The storage type for this conceptual row in the 1186 teLinkSrlgTable. Conceptual rows having the value 1187 'permanent' need not allow write-access to any 1188 columnar object in the row." 1189 ::= { teLinkSrlgEntry 3 } 1191 -- End of teLinkSrlgTable 1193 -- TE Link Bandwidth Table 1194 teLinkBandwidthTable OBJECT-TYPE 1195 SYNTAX SEQUENCE OF TeLinkBandwidthEntry 1196 MAX-ACCESS not-accessible 1197 STATUS current 1198 DESCRIPTION 1199 "This table specifies the priority-based bandwidth table 1200 for TE links." 1201 ::= { linkBundlingObjects 5 } 1203 teLinkBandwidthEntry OBJECT-TYPE 1204 SYNTAX TeLinkBandwidthEntry 1205 MAX-ACCESS not-accessible 1206 STATUS current 1207 DESCRIPTION 1208 "An entry in this table contains information about 1209 the priority-based bandwidth of TE links. An ifEntry in the 1210 ifTable must exist before a teLinkBandwidthEntry using the 1211 same ifIndex is created. If a TE link entry in the ifTable 1212 is destroyed, then so are all entries in the teLinkBandwidthTable 1213 that use the ifIndex of this TE link." 1214 INDEX { ifIndex, teLinkPriority } 1215 ::= { teLinkBandwidthTable 1 } 1217 TeLinkBandwidthEntry ::= SEQUENCE { 1218 teLinkPriority Unsigned32, 1219 teLinkUnreservedBandwidth Unsigned32, 1220 teLinkMaximumLspBandwidth Unsigned32, 1221 teLinkBandwidthRowStatus RowStatus, 1222 teLinkBandwidthStorageType StorageType 1223 } 1225 teLinkPriority OBJECT-TYPE 1226 SYNTAX Unsigned32 (1..8) 1227 MAX-ACCESS not-accessible 1228 STATUS current 1229 DESCRIPTION 1230 "This attribute specifies the priority. It should be mapped 1231 to a number between 0 and 7" 1232 REFERENCE 1233 "[GMPLS-OSPF]" 1234 ::= { teLinkBandwidthEntry 1 } 1236 teLinkUnreservedBandwidth OBJECT-TYPE 1237 SYNTAX Unsigned32 1238 MAX-ACCESS read-only 1239 STATUS current 1240 DESCRIPTION 1241 "This attribute specifies the TE link unreserved 1242 bandwidth at priority p. It is the sum of the unreserved 1243 bandwidths at priority p of all component links associated 1244 with the TE link (excludes all links that are strictly 1245 used as protecting links). This value is an estimate in units 1246 of 1,000 bits per second." 1247 REFERENCE 1248 "[BUNDLING]" 1249 ::= { teLinkBandwidthEntry 2 } 1251 teLinkMaximumLspBandwidth OBJECT-TYPE 1252 SYNTAX Unsigned32 1253 MAX-ACCESS read-create 1254 STATUS current 1255 DESCRIPTION 1256 "This attribute specifies the TE link maximum 1257 LSP bandwidth at priority p. It is the maximum of all 1258 maximum LSP bandwidth at priority p of the component links 1259 associated with the TE link (excludes all links that are 1260 strictly used as protecting links). This value is an estimate 1261 in units of 1,000 bits per second." 1262 REFERENCE 1263 "[BUNDLING]" 1264 ::= { teLinkBandwidthEntry 3 } 1266 teLinkBandwidthRowStatus OBJECT-TYPE 1267 SYNTAX RowStatus 1268 MAX-ACCESS read-create 1269 STATUS current 1270 DESCRIPTION 1271 "This variable is used to create, modify, and/or 1272 delete a row in this table. All read-create objects 1273 can only be changed when teLinkBandwidthRowStatus is active." 1274 ::= { teLinkBandwidthEntry 4 } 1276 teLinkBandwidthStorageType OBJECT-TYPE 1277 SYNTAX StorageType 1278 MAX-ACCESS read-create 1279 STATUS current 1280 DESCRIPTION 1281 "The storage type for this conceptual row in the 1282 teLinkBandwidthTable. Conceptual rows having the value 1283 'permanent' need not allow write-access to any 1284 columnar object in the row." 1285 ::= { teLinkBandwidthEntry 5 } 1287 -- End of teLinkBandwidthTable 1288 -- Component Link Table 1290 componentLinkTable OBJECT-TYPE 1291 SYNTAX SEQUENCE OF ComponentLinkEntry 1292 MAX-ACCESS not-accessible 1293 STATUS current 1294 DESCRIPTION 1295 "This table specifies the component link parameters." 1296 ::= { linkBundlingObjects 6 } 1298 componentLinkEntry OBJECT-TYPE 1299 SYNTAX ComponentLinkEntry 1300 MAX-ACCESS not-accessible 1301 STATUS current 1302 DESCRIPTION 1303 "An entry in this table exists for each ifEntry that represents 1304 a component link. An ifEntry must exist in the ifTable 1305 before a componentLinkEntry is created with the 1306 corresponding ifIndex. If an entry representing a component 1307 link is destroyed in the ifTable, then so is the 1308 corresponding entry in the componentLinkTable. The 1309 administrative and operational status values are controlled 1310 from the ifEntry." 1311 INDEX { ifIndex } 1312 ::= { componentLinkTable 1 } 1314 ComponentLinkEntry ::= SEQUENCE { 1315 componentLinkMuxCapability INTEGER, 1316 componentLinkPreferredProtection INTEGER, 1317 componentLinkCurrentProtection INTEGER, 1318 componentLinkRowStatus RowStatus, 1319 componentLinkStorageType StorageType 1320 } 1322 componentLinkMuxCapability OBJECT-TYPE 1323 SYNTAX INTEGER { 1324 packetSwitch1(1), 1325 packetSwitch2(2), 1326 packetSwitch3(3), 1327 packetSwitch4(4), 1328 layer2Switch(51), 1329 tdm(100), 1330 lambdaSwitch(150), 1331 fiberSwitch(200) 1332 } 1333 MAX-ACCESS read-create 1334 STATUS current 1335 DESCRIPTION 1336 "This attribute specifies link multiplexing capabilities of the 1337 component link." 1338 REFERENCE 1339 "[GMPLS-OSPF]" 1340 ::= { componentLinkEntry 1 } 1342 componentLinkPreferredProtection OBJECT-TYPE 1343 SYNTAX INTEGER { 1344 primary(1), 1345 secondary(2) 1346 } 1347 MAX-ACCESS read-create 1348 STATUS current 1349 DESCRIPTION 1350 "This attribute specifies whether this component link is 1351 a primary or secondary entity." 1352 ::= { componentLinkEntry 2 } 1354 componentLinkCurrentProtection OBJECT-TYPE 1355 SYNTAX INTEGER { 1356 primary(1), 1357 secondary(2) 1358 } 1359 MAX-ACCESS read-only 1360 STATUS current 1361 DESCRIPTION 1362 "This attribute specifies whether this component link is 1363 currently used as primary or secondary link." 1364 ::= { componentLinkEntry 3 } 1366 componentLinkRowStatus OBJECT-TYPE 1367 SYNTAX RowStatus 1368 MAX-ACCESS read-create 1369 STATUS current 1370 DESCRIPTION 1371 "This variable is used to create, modify, and/or 1372 delete a row in this table. All read-create objects 1373 can only be changed when componentLinkRowStatus is active." 1374 ::= { componentLinkEntry 4 } 1376 componentLinkStorageType OBJECT-TYPE 1377 SYNTAX StorageType 1378 MAX-ACCESS read-create 1379 STATUS current 1380 DESCRIPTION 1381 "The storage type for this conceptual row in the 1382 componentLinkTable. Conceptual rows having the value 1383 'permanent' need not allow write-access to any 1384 columnar object in the row." 1385 ::= { componentLinkEntry 5 } 1387 -- End of componentLinkTable 1389 -- Component Link Descriptor Table 1391 componentLinkDescriptorTable OBJECT-TYPE 1392 SYNTAX SEQUENCE OF ComponentLinkDescriptorEntry 1393 MAX-ACCESS not-accessible 1394 STATUS current 1395 DESCRIPTION 1396 "This table specifies the link descriptors associated with the 1397 component links." 1398 ::= { linkBundlingObjects 7 } 1400 componentLinkDescriptorEntry OBJECT-TYPE 1401 SYNTAX ComponentLinkDescriptorEntry 1402 MAX-ACCESS not-accessible 1403 STATUS current 1404 DESCRIPTION 1405 "An entry in this table is created for every component link 1406 descriptor. An ifEntry in the ifTable must exist before a 1407 componentLinkDescriptorEntry using the same ifIndex is created. 1408 If a component link entry in the ifTable is destroyed, 1409 then so are all entries in the componentLinkDescriptorTable 1410 that use the ifIndex of this component link." 1411 INDEX { ifIndex, componentLinkDescrId } 1412 ::= { componentLinkDescriptorTable 1 } 1414 ComponentLinkDescriptorEntry ::= SEQUENCE { 1415 componentLinkDescrId Unsigned32, 1416 componentLinkEncodingType INTEGER, 1417 componentLinkDescrPriority Unsigned32, 1418 componentLinkMinReservBandwidth Unsigned32, 1419 componentLinkMaxReservBandwidth Unsigned32, 1420 componentLinkDescrRowStatus RowStatus, 1421 componentLinkDescrStorageType StorageType 1422 } 1424 componentLinkDescrId OBJECT-TYPE 1425 SYNTAX Unsigned32 1426 MAX-ACCESS not-accessible 1427 STATUS current 1428 DESCRIPTION 1429 "This object specifies the link descriptor identifier." 1430 ::= { componentLinkDescriptorEntry 1 } 1432 componentLinkEncodingType OBJECT-TYPE 1433 SYNTAX INTEGER { 1434 packet(1), 1435 ethernet(2), 1436 ansiEtsiPdh(3), 1437 sdhItuSonetAnsi(5), 1438 digitalWrapper(7), 1439 lambda(8), 1440 fiber(9), 1441 fiberChannel(11) 1442 } 1443 MAX-ACCESS read-create 1444 STATUS current 1445 DESCRIPTION 1446 "This attribute specifies the component link encoding type." 1447 REFERENCE 1448 "[GMPLS]" 1449 ::= { componentLinkDescriptorEntry 2 } 1451 componentLinkDescrPriority OBJECT-TYPE 1452 SYNTAX Unsigned32 (0..7) 1453 MAX-ACCESS read-create 1454 STATUS current 1455 DESCRIPTION 1456 "This object specifies the lowest priority at which that link 1457 encoding type is available for the component link." 1458 REFERENCE 1459 "[GMPLS-OSPF]" 1460 ::= { componentLinkDescriptorEntry 3 } 1462 componentLinkMinReservBandwidth OBJECT-TYPE 1463 SYNTAX Unsigned32 1464 MAX-ACCESS read-create 1465 STATUS current 1466 DESCRIPTION 1467 "This attribute specifies the minimum reservable bandwidth on 1468 the component link. This value is an estimate 1469 in units of 1,000 bits per second." 1470 REFERENCE 1471 "[GMPLS-OSPF]" 1472 ::= { componentLinkDescriptorEntry 4 } 1474 componentLinkMaxReservBandwidth OBJECT-TYPE 1475 SYNTAX Unsigned32 1476 MAX-ACCESS read-create 1477 STATUS current 1478 DESCRIPTION 1479 "This attribute specifies the maximum reservable bandwidth on 1480 the component link. This value is an estimate 1481 in units of 1,000 bits per second." 1482 REFERENCE 1483 "[GMPLS-OSPF]" 1484 ::= { componentLinkDescriptorEntry 5 } 1486 componentLinkDescrRowStatus OBJECT-TYPE 1487 SYNTAX RowStatus 1488 MAX-ACCESS read-create 1489 STATUS current 1490 DESCRIPTION 1491 "This variable is used to create, modify, and/or 1492 delete a row in this table. All read-create objects 1493 can only be changed when componentLinkDescrRowStatus 1494 is active." 1495 ::= { componentLinkDescriptorEntry 6 } 1497 componentLinkDescrStorageType OBJECT-TYPE 1498 SYNTAX StorageType 1499 MAX-ACCESS read-create 1500 STATUS current 1501 DESCRIPTION 1502 "The storage type for this conceptual row in the 1503 componentLinkDescriptorTable. Conceptual rows 1504 having the value 'permanent' need not allow write-access 1505 to any columnar object in the row." 1506 ::= { componentLinkDescriptorEntry 7 } 1508 -- End of componentLinkDescriptorTable 1510 -- Component Link Bandwidth Table 1512 componentLinkBandwidthTable OBJECT-TYPE 1513 SYNTAX SEQUENCE OF ComponentLinkBandwidthEntry 1514 MAX-ACCESS not-accessible 1515 STATUS current 1516 DESCRIPTION 1517 "This table specifies the priority-based bandwidth 1518 for component links." 1519 ::= { linkBundlingObjects 8 } 1521 componentLinkBandwidthEntry OBJECT-TYPE 1522 SYNTAX ComponentLinkBandwidthEntry 1523 MAX-ACCESS not-accessible 1524 STATUS current 1525 DESCRIPTION 1526 "An entry in this table contains information about 1527 the priority-based bandwidth on component links. 1528 An ifEntry in the ifTable must exist before a 1529 componentLinkBandwidthEntry using the same ifIndex is 1530 created. If a component link entry in the ifTable is 1531 destroyed, then so are all entries in the 1532 componentLinkBandwidthTable that use the ifIndex of 1533 this component link." 1534 INDEX { ifIndex, componentLinkPriority } 1535 ::= { componentLinkBandwidthTable 1 } 1537 ComponentLinkBandwidthEntry ::= SEQUENCE { 1538 componentLinkPriority Unsigned32, 1539 componentLinkUnreservedBandwidth Unsigned32, 1540 componentLinkMaximumLspBandwidth Unsigned32, 1541 componentLinkBandwidthRowStatus RowStatus, 1542 componentLinkBwStorageType StorageType 1543 } 1545 componentLinkPriority OBJECT-TYPE 1546 SYNTAX Unsigned32 (1..8) 1547 MAX-ACCESS not-accessible 1548 STATUS current 1549 DESCRIPTION 1550 "This attribute specifies the priority. It should be mapped 1551 to a number between 0 and 7." 1552 REFERENCE 1553 "[GMPLS-OSPF]" 1554 ::= { componentLinkBandwidthEntry 1 } 1556 componentLinkUnreservedBandwidth OBJECT-TYPE 1557 SYNTAX Unsigned32 1558 MAX-ACCESS read-only 1559 STATUS current 1560 DESCRIPTION 1561 "This attribute specifies the component link unreserved 1562 bandwidth at priority p. This value is an estimate 1563 in units of 1,000 bits per second." 1564 REFERENCE 1565 "[GMPLS-OPSF]" 1566 ::= { componentLinkBandwidthEntry 2 } 1568 componentLinkMaximumLspBandwidth OBJECT-TYPE 1569 SYNTAX Unsigned32 1570 MAX-ACCESS read-create 1571 STATUS current 1572 DESCRIPTION 1573 "This attribute specifies the component link maximum 1574 LSP bandwidth at priority p. This value is an estimate 1575 in units of 1,000 bits per second." 1576 REFERENCE 1577 "[GMPLS-OSPF]" 1578 ::= { componentLinkBandwidthEntry 3 } 1580 componentLinkBandwidthRowStatus OBJECT-TYPE 1581 SYNTAX RowStatus 1582 MAX-ACCESS read-create 1583 STATUS current 1584 DESCRIPTION 1585 "This variable is used to create, modify, and/or 1586 delete a row in this table. All read-create objects can only 1587 be changed when componentLinkBandwidthRowStatus is active." 1588 ::= { componentLinkBandwidthEntry 4 } 1590 componentLinkBwStorageType OBJECT-TYPE 1591 SYNTAX StorageType 1592 MAX-ACCESS read-create 1593 STATUS current 1594 DESCRIPTION 1595 "The storage type for this conceptual row in the 1596 componentLinkBandwidthTable. Conceptual rows 1597 having the value 'permanent' need not allow write-access 1598 to any columnar object in the row." 1599 ::= { componentLinkBandwidthEntry 5 } 1601 -- End of componentLinkBandwidthTable 1603 -- Notification Configuration 1605 linkBundlingNotifEnable OBJECT-TYPE 1606 SYNTAX TruthValue 1607 MAX-ACCESS read-write 1608 STATUS current 1609 DESCRIPTION 1610 "If this object is true, then it enables the 1611 generation of the link bundling notifications, 1612 otherwise these notifications are not emitted." 1613 DEFVAL { false } 1614 ::= { linkBundlingObjects 9 } 1616 -- Notifications 1618 -- Bundled Link Notifications 1619 linkBundleMismatch NOTIFICATION-TYPE 1620 OBJECTS { teLinkIpAddrType, teLinkIpAddr, teLinkRemoteIpAddr } 1621 STATUS current 1622 DESCRIPTION 1623 "This notification is generated when a mismatch is found on a 1624 bundled link. Such mismatch can be detected for instance if one 1625 of the traffic engineering parameters is not consistent across 1626 all TE links within a bundled link (resource class, 1627 OSPF link type, etc.)." 1628 ::= { linkBundlingNotifications 1 } 1630 -- End of notifications 1632 -- Module compliance 1634 linkBundlingGroups 1635 OBJECT IDENTIFIER ::= { linkBundlingConformance 1 } 1637 linkBundlingCompliances 1638 OBJECT IDENTIFIER ::= { linkBundlingConformance 2 } 1640 linkBundlingFullModuleCompliance MODULE-COMPLIANCE 1641 STATUS current 1642 DESCRIPTION 1643 "Compliance statement for agents that support the 1644 configuration and monitoring of link bundling MIB." 1645 MODULE -- this module 1647 -- The mandatory groups have to be implemented 1648 -- by all devices supporting link bundling. However, they may all 1649 -- be supported as read-only objects in the case where automatic 1650 -- configuration is supported. 1652 MANDATORY-GROUPS { linkBundlingGroup, 1653 teLinkBandwidthGroup, 1654 componentLinkBandwidthGroup } 1656 GROUP teLinkOspfTeGroup 1657 DESCRIPTION 1658 "This group is mandatory for OSPF enabled devices." 1660 GROUP teLinkSrlgGroup 1661 DESCRIPTION 1662 "This group is mandatory for G-MPLS enabled devices." 1664 GROUP linkBundlingNotificationGroup 1665 DESCRIPTION 1666 "This group is mandatory for equipment that support 1667 link bundling notifications." 1669 -- teLinkTable 1671 OBJECT teLinkIpAddrType 1672 SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } 1673 MIN-ACCESS read-only 1674 DESCRIPTION 1675 "The dns(16) address type need not be supported. 1676 The ipv4(1) and ipv6(2) address types need not be 1677 supported if numbered links are not supported. The 1678 unknown(0) address type need not be supported if 1679 unnumbered links are not supported." 1681 OBJECT teLinkIpAddr 1682 SYNTAX InetAddress (SIZE(0|4|16)) 1683 DESCRIPTION 1684 "Size of TE link IP address depends on type of TE link. 1685 TE link IP address size is zero if link is unnumbered, 1686 four if link IP address is IPv4 and sixteen if link IP 1687 address is IPv6." 1689 OBJECT teLinkRemoteIpAddr 1690 SYNTAX InetAddress (SIZE(0|4|16)) 1691 DESCRIPTION 1692 "Size of TE link IP address depends on type of TE link. 1693 TE link IP address size is zero if link is unnumbered, 1694 four if link IP address is IPv4 and sixteen if link IP 1695 address is IPv6." 1697 OBJECT teLinkMuxCapability 1698 MIN-ACCESS read-only 1699 DESCRIPTION 1700 "Write access is not required." 1702 OBJECT teLinkProtectionType 1703 MIN-ACCESS read-only 1704 DESCRIPTION 1705 "Write access is not required." 1707 OBJECT teLinkRowStatus 1708 SYNTAX INTEGER { active(1), notInService(2), 1709 createAndGo(4), destroy(6) } 1710 DESCRIPTION 1711 "The notReady(3) state need not be supported." 1713 OBJECT teLinkStorageType 1714 SYNTAX INTEGER { other(1) } 1715 DESCRIPTION 1716 "Only other(1) needs to be supported." 1718 -- teLinkDescriptorTable 1720 OBJECT teLinkEncodingType 1721 MIN-ACCESS read-only 1722 DESCRIPTION 1723 "Write access is not required." 1725 OBJECT teLinkDescrPriority 1726 MIN-ACCESS read-only 1727 DESCRIPTION 1728 "Write access is not required." 1730 OBJECT teLinkMinReservableBandwidth 1731 MIN-ACCESS read-only 1732 DESCRIPTION 1733 "Write access is not required." 1735 OBJECT teLinkMaxReservableBandwidth 1736 MIN-ACCESS read-only 1737 DESCRIPTION 1738 "Write access is not required." 1740 OBJECT teLinkDescrRowStatus 1741 SYNTAX INTEGER { active(1), notInService(2), 1742 createAndGo(4), destroy(6) } 1743 DESCRIPTION 1744 "The notReady(3) state need not be supported." 1746 OBJECT teLinkDescrStorageType 1747 SYNTAX INTEGER { other(1) } 1748 DESCRIPTION 1749 "Only other(1) needs to be supported." 1751 -- teLinkOspfTeTable 1753 OBJECT teLinkOspfLinkType 1754 SYNTAX INTEGER { pointToPoint(1) } 1755 MIN-ACCESS read-only 1756 DESCRIPTION 1757 "A value of multiAccess(2) need not be supported." 1759 OBJECT teLinkOspfLinkId 1760 MIN-ACCESS read-only 1761 DESCRIPTION 1762 "Write access is not required." 1764 -- teLinkSrlgTable 1766 OBJECT srlgRowStatus 1767 SYNTAX INTEGER { active(1), notInService(2), 1768 createAndGo(4), destroy(6) } 1769 DESCRIPTION 1770 "The notReady(3) and createAndWait(5) states need 1771 not be supported." 1773 OBJECT srlgStorageType 1774 SYNTAX INTEGER { other(1) } 1775 DESCRIPTION 1776 "Only other(1) needs to be supported." 1778 -- teLinkBandwidthTable 1780 OBJECT teLinkMaximumLspBandwidth 1781 MIN-ACCESS read-only 1782 DESCRIPTION 1783 "Write access is not required." 1785 OBJECT teLinkBandwidthRowStatus 1786 SYNTAX INTEGER { active(1), notInService(2), 1787 createAndGo(4), destroy(6) } 1788 DESCRIPTION 1789 "The notReady(3) and createAndWait(5) states need 1790 not be supported." 1792 OBJECT teLinkBandwidthStorageType 1793 SYNTAX INTEGER { other(1) } 1794 DESCRIPTION 1795 "Only other(1) needs to be supported." 1797 -- componentLinkTable 1799 OBJECT componentLinkMuxCapability 1800 MIN-ACCESS read-only 1801 DESCRIPTION 1802 "Write access is not required." 1804 OBJECT componentLinkMaxReservBandwidth 1805 MIN-ACCESS read-only 1806 DESCRIPTION 1807 "Write access is not required." 1809 OBJECT componentLinkRowStatus 1810 SYNTAX INTEGER { active(1), notInService(2), 1811 createAndGo(4), destroy(6) } 1812 DESCRIPTION 1813 "The notReady(3) and createAndWait(5) states need 1814 not be supported." 1816 OBJECT componentLinkStorageType 1817 SYNTAX INTEGER { other(1) } 1818 DESCRIPTION 1819 "Only other(1) needs to be supported." 1821 -- componentLinkDescriptorTable 1823 OBJECT componentLinkDescrRowStatus 1824 SYNTAX INTEGER { active(1), notInService(2), 1825 createAndGo(4), destroy(6) } 1826 DESCRIPTION 1827 "The notReady(3) state need not be supported." 1829 OBJECT componentLinkDescrStorageType 1830 SYNTAX INTEGER { other(1) } 1831 DESCRIPTION 1832 "Only other(1) needs to be supported." 1834 -- componentLinkBandwidthTable 1836 OBJECT componentLinkMaximumLspBandwidth 1837 MIN-ACCESS read-only 1838 DESCRIPTION 1839 "Write access is not required." 1841 OBJECT componentLinkBandwidthRowStatus 1842 SYNTAX INTEGER { active(1), notInService(2), 1843 createAndGo(4), destroy(6) } 1844 DESCRIPTION 1845 "The notReady(3) and createAndWait(5) states need 1846 not be supported." 1848 OBJECT componentLinkBwStorageType 1849 SYNTAX INTEGER { other(1) } 1850 DESCRIPTION 1851 "Only other(1) needs to be supported." 1853 ::= { linkBundlingCompliances 1 } 1855 linkBundlingMonModuleCompliance MODULE-COMPLIANCE 1856 STATUS current 1857 DESCRIPTION 1858 "Compliance statement for agents that support the 1859 monitoring of link bundling MIB." 1860 MODULE -- this module 1862 -- The mandatory groups have to be implemented 1863 -- by all devices supporting link bundling. However, they may all 1864 -- be supported as read-only objects in the case where manual 1865 -- configuration is unsupported. 1867 MANDATORY-GROUPS { linkBundlingGroup, 1868 teLinkBandwidthGroup, 1869 componentLinkBandwidthGroup } 1871 GROUP teLinkOspfTeGroup 1872 DESCRIPTION 1873 "This group is mandatory for OSPF enabled devices." 1875 GROUP teLinkSrlgGroup 1876 DESCRIPTION 1877 "This group is mandatory for G-MPLS enabled devices." 1879 GROUP linkBundlingNotificationGroup 1880 DESCRIPTION 1881 "This group is optional." 1883 -- teLinkTable 1885 OBJECT teLinkIpAddrType 1886 SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } 1887 MIN-ACCESS read-only 1888 DESCRIPTION 1889 "The dns(16) address type need not be supported. 1890 The ipv4(1) and ipv6(2) address types need not be 1891 supported if numbered links are not supported. The 1892 unknown(0) address type need not be supported if 1893 unnumbered links are not supported." 1895 OBJECT teLinkIpAddr 1896 SYNTAX InetAddress (SIZE(0|4|16)) 1897 DESCRIPTION 1898 "Size of TE link IP address depends on type of TE link. 1899 TE link IP address size is zero if link is unnumbered, 1900 four if link IP address is IPv4 and sixteen if link IP 1901 address is IPv6." 1903 OBJECT teLinkRemoteIpAddr 1904 SYNTAX InetAddress (SIZE(0|4|16)) 1905 DESCRIPTION 1906 "Size of TE link IP address depends on type of TE link. 1907 TE link IP address size is zero if link is unnumbered, 1908 four if link IP address is IPv4 and sixteen if link IP 1909 address is IPv6." 1911 OBJECT teLinkMuxCapability 1912 MIN-ACCESS read-only 1913 DESCRIPTION 1914 "Write access is not required." 1916 OBJECT teLinkProtectionType 1917 MIN-ACCESS read-only 1918 DESCRIPTION 1919 "Write access is not required." 1921 OBJECT teLinkWorkingPriority 1922 MIN-ACCESS read-only 1923 DESCRIPTION 1924 "Write access is not required." 1926 OBJECT teLinkFlooding 1927 MIN-ACCESS read-only 1928 DESCRIPTION 1929 "Write access is not required." 1931 OBJECT teLinkRowStatus 1932 SYNTAX INTEGER { active(1), notInService(2), 1933 createAndGo(4), destroy(6) } 1934 MIN-ACCESS read-only 1935 DESCRIPTION 1936 "The notReady(3) state need not be supported." 1938 OBJECT teLinkStorageType 1939 SYNTAX INTEGER { other(1) } 1940 MIN-ACCESS read-only 1941 DESCRIPTION 1942 "Only other(1) needs to be supported." 1944 -- teLinkDescriptorTable 1946 OBJECT teLinkEncodingType 1947 MIN-ACCESS read-only 1948 DESCRIPTION 1949 "Write access is not required." 1951 OBJECT teLinkDescrPriority 1952 MIN-ACCESS read-only 1953 DESCRIPTION 1954 "Write access is not required." 1956 OBJECT teLinkMinReservableBandwidth 1957 MIN-ACCESS read-only 1958 DESCRIPTION 1959 "Write access is not required." 1961 OBJECT teLinkMaxReservableBandwidth 1962 MIN-ACCESS read-only 1963 DESCRIPTION 1964 "Write access is not required." 1966 OBJECT teLinkDescrRowStatus 1967 SYNTAX INTEGER { active(1), notInService(2), 1968 createAndGo(4), destroy(6) } 1969 MIN-ACCESS read-only 1970 DESCRIPTION 1971 "The notReady(3) state need not be supported." 1973 OBJECT teLinkDescrStorageType 1974 SYNTAX INTEGER { other(1) } 1975 MIN-ACCESS read-only 1976 DESCRIPTION 1977 "Only other(1) needs to be supported." 1979 -- teLinkOspfTeTable 1981 OBJECT teLinkOspfLinkType 1982 SYNTAX INTEGER { pointToPoint(1) } 1983 DESCRIPTION 1984 "A value of multiAccess(2) need not be supported." 1986 OBJECT teLinkOspfLinkId 1987 MIN-ACCESS read-only 1988 DESCRIPTION 1989 "Write access is not required." 1991 -- teLinkSrlgTable 1993 OBJECT srlgRowStatus 1994 SYNTAX INTEGER { active(1), notInService(2), 1995 createAndGo(4), destroy(6) } 1996 MIN-ACCESS read-only 1997 DESCRIPTION 1998 "The notReady(3) and createAndWait(5) states need 1999 not be supported." 2001 OBJECT srlgStorageType 2002 SYNTAX INTEGER { other(1) } 2003 MIN-ACCESS read-only 2004 DESCRIPTION 2005 "Only other(1) needs to be supported." 2007 -- teLinkBandwidthTable 2009 OBJECT teLinkMaximumLspBandwidth 2010 MIN-ACCESS read-only 2011 DESCRIPTION 2012 "Write access is not required." 2014 OBJECT teLinkBandwidthRowStatus 2015 SYNTAX INTEGER { active(1), notInService(2), 2016 createAndGo(4), destroy(6) } 2017 MIN-ACCESS read-only 2018 DESCRIPTION 2019 "The notReady(3) and createAndWait(5) states need 2020 not be supported." 2022 OBJECT teLinkBandwidthStorageType 2023 SYNTAX INTEGER { other(1) } 2024 MIN-ACCESS read-only 2025 DESCRIPTION 2026 "Only other(1) needs to be supported." 2028 -- componentLinkTable 2030 OBJECT componentLinkMuxCapability 2031 MIN-ACCESS read-only 2032 DESCRIPTION 2033 "Write access is not required." 2035 OBJECT componentLinkPreferredProtection 2036 MIN-ACCESS read-only 2037 DESCRIPTION 2038 "Write access is not required." 2040 OBJECT componentLinkMaxReservBandwidth 2041 MIN-ACCESS read-only 2042 DESCRIPTION 2043 "Write access is not required." 2045 OBJECT componentLinkRowStatus 2046 SYNTAX INTEGER { active(1), notInService(2), 2047 createAndGo(4), destroy(6) } 2048 MIN-ACCESS read-only 2049 DESCRIPTION 2050 "The notReady(3) and createAndWait(5) states need 2051 not be supported." 2053 OBJECT componentLinkStorageType 2054 SYNTAX INTEGER { other(1) } 2055 MIN-ACCESS read-only 2056 DESCRIPTION 2057 "Only other(1) needs to be supported." 2059 -- componentLinkDescriptorTable 2061 OBJECT componentLinkEncodingType 2062 MIN-ACCESS read-only 2063 DESCRIPTION 2064 "Write access is not required." 2066 OBJECT componentLinkDescrPriority 2067 MIN-ACCESS read-only 2068 DESCRIPTION 2069 "Write access is not required." 2071 OBJECT componentLinkMinReservBandwidth 2072 MIN-ACCESS read-only 2073 DESCRIPTION 2074 "Write access is not required." 2076 OBJECT componentLinkDescrRowStatus 2077 SYNTAX INTEGER { active(1), notInService(2), 2078 createAndGo(4), destroy(6) } 2079 MIN-ACCESS read-only 2080 DESCRIPTION 2081 "The notReady(3) state need not be supported." 2083 OBJECT componentLinkDescrStorageType 2084 SYNTAX INTEGER { other(1) } 2085 MIN-ACCESS read-only 2086 DESCRIPTION 2087 "Only other(1) needs to be supported." 2089 -- componentLinkBandwidthTable 2091 OBJECT componentLinkMaximumLspBandwidth 2092 MIN-ACCESS read-only 2093 DESCRIPTION 2094 "Write access is not required." 2096 OBJECT componentLinkBandwidthRowStatus 2097 SYNTAX INTEGER { active(1), notInService(2), 2098 createAndGo(4), destroy(6) } 2099 MIN-ACCESS read-only 2100 DESCRIPTION 2101 "The notReady(3) and createAndWait(5) states need 2102 not be supported." 2104 OBJECT componentLinkBwStorageType 2105 SYNTAX INTEGER { other(1) } 2106 MIN-ACCESS read-only 2107 DESCRIPTION 2108 "Only other(1) needs to be supported." 2110 ::= { linkBundlingCompliances 2 } 2112 -- Units of conformance 2114 linkBundlingGroup OBJECT-GROUP 2115 OBJECTS { teLinkIpAddrType, 2116 teLinkIpAddr, 2117 teLinkRemoteIpAddr, 2118 teLinkMetric, 2119 teLinkMuxCapability, 2120 teLinkProtectionType, 2121 teLinkWorkingPriority, 2122 teLinkResourceClass, 2123 teLinkIncomingIfId, 2124 teLinkOutgoingIfId, 2125 teLinkFlooding, 2126 teLinkRowStatus, 2127 teLinkStorageType, 2128 teLinkEncodingType, 2129 teLinkDescrPriority, 2130 teLinkMinReservableBandwidth, 2131 teLinkMaxReservableBandwidth, 2132 teLinkDescrRowStatus, 2133 teLinkDescrStorageType, 2134 componentLinkMuxCapability, 2135 componentLinkPreferredProtection, 2136 componentLinkCurrentProtection, 2137 componentLinkRowStatus, 2138 componentLinkStorageType, 2139 linkBundlingNotifEnable 2140 } 2142 STATUS current 2143 DESCRIPTION 2144 "Collection of objects needed for the monitoring of 2145 resources associated with TE links." 2147 ::= { linkBundlingGroups 1 } 2149 teLinkOspfTeGroup OBJECT-GROUP 2150 OBJECTS { teLinkOspfLinkType, 2151 teLinkOspfLinkId 2152 } 2154 STATUS current 2155 DESCRIPTION 2156 "Collection of objects needed for the OSPF traffic 2157 engineering parameters of TE links." 2158 ::= { linkBundlingGroups 2 } 2160 teLinkSrlgGroup OBJECT-GROUP 2161 OBJECTS { srlgRowStatus, 2162 srlgStorageType 2163 } 2165 STATUS current 2166 DESCRIPTION 2167 "Collection of objects needed for the monitoring of 2168 SRLG resources associated with TE links." 2169 ::= { linkBundlingGroups 3 } 2171 teLinkBandwidthGroup OBJECT-GROUP 2172 OBJECTS { teLinkUnreservedBandwidth, 2173 teLinkMaximumLspBandwidth, 2174 teLinkBandwidthRowStatus, 2175 teLinkBandwidthStorageType 2176 } 2178 STATUS current 2179 DESCRIPTION 2180 "Collection of objects needed for the monitoring of 2181 the priority-based bandwidth resources associated with 2182 TE links and component links." 2183 ::= { linkBundlingGroups 4 } 2185 componentLinkBandwidthGroup OBJECT-GROUP 2186 OBJECTS { componentLinkEncodingType, 2187 componentLinkDescrPriority, 2188 componentLinkMinReservBandwidth, 2189 componentLinkMaxReservBandwidth, 2190 componentLinkDescrRowStatus, 2191 componentLinkDescrStorageType, 2192 componentLinkUnreservedBandwidth, 2193 componentLinkMaximumLspBandwidth, 2194 componentLinkBandwidthRowStatus, 2195 componentLinkBwStorageType 2196 } 2198 STATUS current 2199 DESCRIPTION 2200 "Collection of objects needed for the monitoring of 2201 bandwidth parameters associated with component links." 2202 ::= { linkBundlingGroups 5 } 2204 linkBundlingNotificationGroup NOTIFICATION-GROUP 2205 NOTIFICATIONS { linkBundleMismatch } 2206 STATUS current 2207 DESCRIPTION 2208 "Set of notifications implemented in this module. 2209 None is mandatory." 2210 ::= { linkBundlingGroups 6 } 2212 -- End of LINK-BUNDLING-MIB 2213 END 2215 11. Intellectual Property Considerations 2217 The IETF takes no position regarding the validity or scope of any 2218 intellectual property or other rights that might be claimed to per- 2219 tain to the implementation or use of the technology described in this 2220 document or the extent to which any license under such rights might 2221 or might not be available; neither does it represent that it has made 2222 any effort to identify any such rights. Information on the IETF's 2223 procedures with respect to rights in standards-track and standards- 2224 related documentation can be found in BCP-11. Copies of claims of 2225 rights made available for publication and any assurances of licenses 2226 to be made available, or the result of an attempt made to obtain a 2227 general license or permission for the use of such proprietary rights 2228 by implementers or users of this specification can be obtained from 2229 the IETF Secretariat. 2231 The IETF invites any interested party to bring to its attention any 2232 copyrights, patents or patent applications, or other proprietary 2233 rights which may cover technology that may be required to practice 2234 this standard. Please address the information to the IETF Executive 2235 Director. 2237 12. Security Considerations 2239 It is clear that this MIB is potentially useful for monitoring of 2240 link bundling enabled devices. This MIB can also be used for configu- 2241 ration of certain objects, and anything that can be configured can be 2242 incorrectly configured, with potentially disastrous results. 2244 At this writing, no security holes have been identified beyond those 2245 that SNMP Security [RFC2571] is itself intended to address. These 2246 relate to primarily controlled access to sensitive information and 2247 the ability to configure a device - or which might result from opera- 2248 tor error, which is beyond the scope of any security architecture. 2250 There are a number of management objects defined in this MIB which 2251 have a MAX-ACCESS clause of read-write and/or read-create. Such 2252 objects may be considered sensitive or vulnerable in some network 2253 environments. The support for SET operations in a non-secure environ- 2254 ment without proper protection can have a negative effect on network 2255 operations. The use of SNMP Version 3 is recommended over prior ver- 2256 sions, for configuration control, as its security model is improved. 2258 SNMPv1 or SNMPv2 are by themselves not a secure environment. Even if 2259 the network itself is secure (for example by using IPSec [RFC2401]), 2260 there is no control as to who on the secure network is allowed to 2261 access and GET/SET (read/change/create/delete) the objects in this 2262 MIB. It is recommended that the implementers consider the security 2263 features as provided by the SNMPv3 framework. Specifically, the use 2264 of the User-based Security Model [RFC2574] and the View-based Access 2265 Control [RFC2575] is recommended. It is then a customer/user respon- 2266 sibility to ensure that the SNMP entity giving access to an instance 2267 of this MIB is properly configured to give access to the objects only 2268 to those principals (users) that have legitimate rights to indeed GET 2269 or SET (change/create/delete) them. 2271 There are a number of managed objects in this MIB that may contain 2272 information that may be sensitive from a business perspective, in 2273 that they can be used to derive the network topology, e.g. list of 2274 nodes and their IP address (teLinkTable), list of component links 2275 (componentLinkTable) in addition to usage of network resources 2276 (teLinkBandwidthTable and componentLinkBandwidthTable). Allowing 2277 uncontrolled access to these objects could result in malicious and 2278 unwanted disruptions of network traffic, incorrect network configura- 2279 tion or theft of competitive business information. There are no 2280 objects that are particularly sensitive in their own right, such as 2281 passwords or monetary amounts. 2283 13. Acknowledgments 2285 The general structure of this draft has been modeled around draft- 2286 ietf-mpls-lsr-mib-06.txt. The authors would like to acknowlegde the 2287 contribution of Dmitry Ryumkin. 2289 14. References 2291 14.1. Normative References 2293 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2294 Requirement Levels", BCP 14, RFC 2119, March 1997. 2296 [RFC2401] Kent, S., and Atkinson, R., "Security Architecture 2297 for the Internet Protocol", RFC 2401, November 2298 1998. 2300 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2301 J., Rose, M., and S. Waldbusser, "Structure of 2302 Management Information Version 2 (SMIv2)", STD 58, 2303 RFC 2578, April 1999. 2305 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2306 J., Rose, M., and S. Waldbusser, "Textual Conventions 2307 for SMIv2", STD 58, RFC 2579, April 1999. 2309 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2310 J., Rose, M., and S. Waldbusser, "Conformance 2311 Statements for SMIv2", STD 58, RFC 2580, April 1999. 2313 [RFC2863] McCloghrie, K., and Kastenholtz, F., "The Interfaces 2314 Group MIB", RFC 2863, June 2000. 2316 [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", 2317 RFC 1700, October 1994. See also: 2318 http://www.iana.org/assignments/smi-numbers 2320 [BUNDLING] Kompella, K., Rekhter, Y., and Berger, L., 2321 "Link Bundling in MPLS Traffic Engineering", 2322 Internet Draft , 2323 July 2002. 2325 [FLOOD] Zinin, A., and Shand, M., "Flooding optimization 2326 in link-state routing protocols, Internet Draft 2327 , 2328 March 2001." 2330 [GMPLS] Ashwood-Smith, P., Banarjee, A., Berger, L., 2331 Bernstein, G., Drake, J., Fan, Y., Kompella, K., 2332 Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y., 2333 Saha, D., Sharma, V., Swallow, G., and Tang, Z., 2334 "Generalized MPLS Signaling Functional Description", 2335 Internet Draft 2336 , 2337 August 2002. 2339 [GMPLS-OSPF] Kompella, K., Rekhter, Y., Banerjee, A. et al, "OSPF 2340 Extensions in Support of Generalized MPLS", Internet 2341 Draft , 2342 August 2002. 2344 [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS 2345 FAMILY NUMBERS, (http://www.isi.edu/in- 2346 notes/iana/assignements/address-family-numbers), 2347 for MIB see: 2348 ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib 2350 [LMP] Lang, J., Mitra, K., Drake, J., Kompella, K., 2351 Rekhter, Y., Berger, L., Rajagopalan, B., 2352 Basak, D., Sandick, H., Zinin, A., 2353 Rajagopalan, B., and Ramamoorthi, S., 2354 "Link Management Protocol", 2355 Internet Draft , 2356 September 2002. 2358 [OSPF] Katz, D., Yeung, D., and Kompella, K., "Traffic 2359 Engineering Extensions to OSPF", Internet Draft 2360 , October 2002. 2362 14.2. Informative References 2364 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 2365 Identification of Management Information for TCP/IP- 2366 based Internets", STD 16, RFC 1155, May 1990. 2368 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 2369 "Simple Network Management Protocol", STD 15, RFC 1157, 2370 May 1990. 2372 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 2373 STD 16, RFC 1212, March 1991. 2375 [RFC1215] M. Rose, "A Convention for Defining Traps for use with 2376 the SNMP", RFC 1215, March 1991. 2378 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2379 "Introduction to Community-based SNMPv2", RFC 1901, 2380 January 1996. 2382 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2383 "Protocol Operations for Version 2 of the Simple 2384 Network Management Protocol (SNMPv2)", RFC 1905, 2385 January 1996. 2387 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2388 "Transport Mappings for Version 2 of the Simple Network 2389 Management Protocol (SNMPv2)", RFC 1906, January 1996. 2391 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 2392 "Introduction to Version 3 of the Internet-standard 2393 Network Management Framework", RFC 2570, April 1999. 2395 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 2396 Architecture for Describing SNMP Management 2397 Frameworks", RFC 2571, April 1999. 2399 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2400 "Message Processing and Dispatching for the Simple 2401 Network Management Protocol (SNMP)", RFC 2572, April 2402 1999. 2404 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2405 Applications", RFC 2573, April 1999. 2407 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 2408 Model (USM) for version 3 of the Simple Network 2409 Management Protocol (SNMPv3)", RFC 2574, April 1999. 2411 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 2412 Access Control Model (VACM) for the Simple Network 2413 Management Protocol (SNMP)", RFC 2575, April 1999. 2415 [GMPLS-ARCH] Mannie, E., Ashwood-Smith, P., Awduche, D., 2416 Banarjee, A., Basak, D., Berger, L., Bernstein, G., 2417 Dharanikota, S., Drake, J., Fan, Y., Fedyk, D., 2418 Grammel, G., Guo, D., Kompella, K., Kullberg, A., 2419 Lang, J., Liaw, F., Nadeau, T., Ong, L., 2420 Papadimitriou, D., Pendarakis, D., Rajagopalan, B., 2421 Rekhter, Y., Saha, D., Sandick, H., Sharma, V., 2422 Swallow, G., Tang, Z., Yates, J., Young, G., Yu, J., 2423 Zinin, A., "Generalized Multi-Protocol Label Switching 2424 (GMPLS) Architecture", Internet Draft 2425 , 2426 August 2002. 2428 15. Authors' Addresses 2430 Martin Dubuc Thomas D. Nadeau 2431 Email: dubuc.consulting@rogers.com Cisco Systems, Inc. 2433 300 Apollo Drive 2434 Chelmsford, MA 01824 2435 Phone: +1-978-244-3051 2436 Email: tnadeau@cisco.com 2438 Sudheer Dharanikota Jonathan P. Lang 2439 Email: sudheer@ieee.org Calient Networks, Inc. 2440 25 Castilian Drive 2441 Goleta, CA 93117 2442 Email: jplang@calient.net 2444 16. Full Copyright Statement 2446 Copyright (C) The Internet Society (2001). All Rights Reserved. 2448 This document and translations of it may be copied and furnished to 2449 others, and derivative works that comment on or otherwise explain it 2450 or assist in its implementation may be prepared, copied, published 2451 and distributed, in whole or in part, without restriction of any 2452 kind, provided that the above copyright notice and this paragraph are 2453 included on all such copies and derivative works. However, this docu- 2454 ment itself may not be modified in any way, such as by removing the 2455 copyright notice or references to the Internet Society or other 2456 Internet organizations, except as needed for the purpose of develop- 2457 ing Internet standards in which case the procedures for copyrights 2458 defined in the Internet Standards process must be followed, or as 2459 required to translate it into languages other than English. 2461 The limited permissions granted above are perpetual and will not be 2462 revoked by the Internet Society or its successors or assigns. This 2463 document and the information contained herein is provided on an "AS 2464 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 2465 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 2466 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL 2467 NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY 2468 OR FITNESS FOR A PARTICULAR PURPOSE.