idnits 2.17.1 draft-ietf-mpls-bundle-mib-01.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.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 3 instances of too long lines in the document, the longest one being 3 characters in excess of 72. ** The abstract seems to contain references ([BUNDLING]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == 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 (February 2002) is 8105 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: 'LMP' is defined on line 2231, but no explicit reference was found in the text == Unused Reference: 'GMPLS' is defined on line 2238, but no explicit reference was found in the text == Unused Reference: 'OSPF' is defined on line 2260, but no explicit reference was found in the text == Unused Reference: 'LSP-HIER' is defined on line 2270, but no explicit reference was found in the text == Unused Reference: 'ZININ' is defined on line 2274, but no explicit reference was found in the text == Unused Reference: 'Assigned' is defined on line 2278, but no explicit reference was found in the text == Unused Reference: 'IANAFamily' is defined on line 2283, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'BUNDLING' -- Possible downref: Non-RFC (?) normative reference: ref. 'LMP' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLS' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLS-ARCH' -- Possible downref: Non-RFC (?) normative reference: ref. 'OSPF' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLS-OSPF' -- Possible downref: Non-RFC (?) normative reference: ref. 'LSP-HIER' -- Possible downref: Non-RFC (?) normative reference: ref. 'ZININ' ** Obsolete normative reference: RFC 1700 (ref. 'Assigned') (Obsoleted by RFC 3232) -- Possible downref: Non-RFC (?) normative reference: ref. 'IANAFamily' ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2401 (ref. 'IPSEC') (Obsoleted by RFC 4301) Summary: 21 errors (**), 0 flaws (~~), 10 warnings (==), 11 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Martin Dubuc 3 Internet Draft Meriton Networks 4 Expires: August 2002 5 Sudheer Dharanikota 6 Nayna Networks 8 Thomas D. Nadeau 9 Cisco Systems 11 Jonathan P. Lang 12 Calient Networks 14 February 2002 16 Link Bundling Management Information Base 18 draft-ietf-mpls-bundle-mib-01.txt 20 Status of this Memo 22 This document is an Internet-Draft and is in full conformance with 23 all provisions of Section 10 of RFC 2026. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF), its areas, and its working groups. Note that other 27 groups may also distribute working documents as Internet- Drafts. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet- Drafts as reference 32 material or to cite them other than as "work in progress." 34 The list of current Internet-Drafts can be accessed at 35 http://www.ietf.org/ietf/1id-abstracts.txt. 37 The list of Internet-Draft Shadow Directories can be accessed at 38 http://www.ietf.org/shadow.html. 40 Table of Contents 42 1. Abstract ..................................................... 2 43 2. Introduction ................................................. 2 44 3. Terminology .................................................. 3 45 4. The SNMP Management Framework ................................ 3 46 5. Feature Checklist ............................................ 4 47 6. Outline ...................................................... 5 48 6.1. Summary of Link Bundling MIB ................................. 5 49 7. Brief Description of MIB Objects ............................. 6 50 7.1. teLinkTable .................................................. 6 51 7.2. teLinkDescriptorTable ........................................ 6 52 7.3. teLinkOspfTeTable ............................................ 6 53 7.4. teLinkSrlgTable .............................................. 6 54 7.5. teLinkBandwidthTable ......................................... 7 55 7.6. dataBearingChannelTable ...................................... 7 56 7.7. dataBearingChannelDescriptorTable ............................ 7 57 7.8. dataBearingChannelBandwidthTable ............................. 7 58 8. Example of Bundled Link Setup ................................ 7 59 9. Application of the Interfaces Group to TE Links .............. 11 60 9.1 Support of the TE Link Layer by ifTable ...................... 12 61 9.2 Using ifStackTable ........................................... 13 62 10. Link Bundling MIB Definitions ................................ 15 63 11. Security Considerations ...................................... 47 64 12. Acknowledgments .............................................. 48 65 13. References ................................................... 48 66 14. Authors' Addresses ........................................... 51 67 15. Full Copyright Statement ..................................... 51 69 1. Abstract 71 This memo defines an experimental portion of the Management Informa- 72 tion Base (MIB) for use with network management protocols in the 73 Internet community. In particular, it describes managed objects for 74 modeling link bundling as described in [BUNDLING]. 76 2. Introduction 78 OSPF, G-MPLS and LMP use the concept of traffic engineering (TE) 79 links to abstract link properties. The effect of this approach is the 80 reduction of the amount of routing information exchanged in the net- 81 work, which improves routing scalability. In addition, the use of TE 82 link allows the implementation of new capabilities such as link pro- 83 tection. 85 We present in this document a MIB that can be used to manage TE links 86 and their extension, the bundled link. This MIB enable both the con- 87 figuration and the performance monitoring of TE links and bundled 88 link. 90 Comments should be made directly to the MPLS mailing list at 91 mpls@uu.net. 93 This memo does not, in its draft form, specify a standard for the 94 Internet community. 96 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 97 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 98 document are to be interpreted as described in RFC 2119, reference 99 [BCP14]. 101 3. Terminology 103 This document uses terminology from the documents describing link 104 bundling [BUNDLING] and G-MPLS [GMPLS-ARCH]. 106 The link bundling feature is designed to aggregate one or more simi- 107 lar entities between a node pair into a bundled link [BUNDLING]. In 108 the document, those entities are referred to as TE links. A TE link 109 is a subinterface capable of carrying MPLS traffic engineered 110 traffic. A TE Link may be comprised of only one underlying data- 111 bearing channels. In cases where more than one data-bearing channel 112 is to be combined, multiple data-bearing links should be created with 113 differing priorities to indicate hot-standby or parallel utilization. 115 A bundled link is just another kind of Traffic Engineering (TE) link 116 (see [GMPLS-OSPF]). A link bundle is a subinterface which bonds the 117 traffic of a group of one or more TE links. There should be more than 118 one TE Link in a link bundle, but this is not a requirement. Furth- 119 ermore, if there are more than one TE link in a link bundle at some 120 time, and at some point later, all but one of the links are deleted, 121 the agent may choose to either delete the link bundle, or it may 122 choose to leave it intact. Traffic counters on a link bundle are 123 cumulative for all subinterfaces which it binds together. 125 4. The SNMP Management Framework 127 The SNMP Management Framework presently consists of five major com- 128 ponents: 130 - An overall architecture, described in RFC 2571 [RFC2571]. 132 Mechanisms for describing and naming objects and events for the 133 purpose of management. The first version of this Structure of 134 Management Information (SMI) is called SMIv1 and described in 135 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 136 1215 [RFC1215]. The second version, called SMIv2, is described 137 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 138 STD 58, RFC 2580 [RFC2580]. 140 - Message protocols for transferring management information. The 141 first version of the SNMP message protocol is called SNMPv1 and 142 described in STD 15, RFC 1157 [RFC1157]. A second version of 143 the SNMP message protocol, which is not an Internet standards 144 track protocol, is called SNMPv2c and described in RFC 1901 145 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 146 message protocol is called SNMPv3 and described in RFC 1906 147 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 149 - Protocol operations for accessing management information. The 150 first set of protocol operations and associated PDU formats is 151 described in STD 15, RFC 1157 [RFC1157]. A second set of 152 protocol operations and associated PDU formats is described in 153 RFC 1905 [RFC1905]. 155 - A set of fundamental applications described in RFC 2573 156 [RFC2573] and the view-based access control mechanism described 157 in RFC 2575 [RFC2575]. 159 A more detailed introduction to the current SNMP Management Framework 160 can be found in RFC 2570 [RFC2570]. 162 Managed objects are accessed via a virtual information store, termed 163 the Management Information Base or MIB. Objects in the MIB are 164 defined using the mechanisms defined in the SMI. 166 This memo specifies a MIB module that is compliant to the SMIv2. A 167 MIB conforming to the SMIv1 can be produced through the appropriate 168 translations. The resulting translated MIB must be semantically 169 equivalent, except where objects or events are omitted because no 170 translation is possible (use of Counter64). Some machine readable 171 information in SMIv2 will be converted into textual descriptions in 172 SMIv1 during the translation process. However, this loss of machine 173 readable information is not considered to change the semantics of the 174 MIB. 176 5. Feature Checklist 178 The link bundling MIB (LINK-BUNDLING-MIB) is designed to satisfy the 179 following requirements and constraints: 181 - The MIB supports the management of TE links, including bundled 182 links. 184 - Support is provided for configuration of traffic engineering 185 parameters associated with TE links. 187 - The MIB is used to monitor the priority-based data-bearing channel 188 and TE link bandwidth values. 190 6. Outline 192 Configuring bundled links involves the following steps: 194 - Creating a bundled link. 196 - Creating TE links. 198 - Optionally specifying the shared risk link groups associated with 199 the TE links. 201 - Configuring the data-bearing channels including the bandwidth 202 parameters and associating the data-bearing channels with the 203 appropriate TE link. 205 - Associating the TE links with the appropriate bundled link. 207 6.1. Summary of Link Bundling MIB 209 The MIB objects for performing these actions consist of the following 210 tables: 212 - The TE link table (teLinkTable), which is used to 213 specify TE links, including bundled links, and their generic 214 traffic engineering parameters. 216 - The TE link descriptor table (teLinkDescriptorTable), which is 217 used to enumerate the TE link descriptors. 219 - The TE link OSPF traffic engineering table 220 (teLinkOspfTeTable), which is used for configuring OSPF 221 traffic engineering parameters associated with TE links. 223 - The shared risk link group (SRLG) table (teLinkSrlgTable), 224 which is used to specify the SRLGs associated with TE links. 226 - The TE link bandwidth table (teLinkBandwidthTable), 227 which is used for reporting priority-based bandwidth values 228 associated with TE links. 230 - The data-bearing channel table (dataBearingChannelTable), which is 231 used to identify the data-bearing channels that are associated 232 with the TE links and specify the data-bearing channel generic 233 traffic engineering parameters. 235 - The data-bearing channel link descriptor table 236 (dataBearingChannelDescriptorTable), which is used to enumerate 237 the data-bearing channel link descriptors. 239 - The data-bearing channel bandwidth table 240 (dataBearingChannelBandwidthTable), which is used to report 241 priority-based bandwidth values associated with data-bearing 242 channels. 244 These tables are described in the subsequent sections. 246 7. Brief Description of MIB Objects 248 Sections 7.1-7.5 describe objects pertaining to TE links. The MIB 249 objects were derived from the link bundling document [BUNDLING]. 251 7.1. teLinkTable 253 This table represents the TE links, including bundled links. 255 7.2. teLinkDescriptorTable 257 This table represents the TE link descriptors. 259 7.3. teLinkOspfTeTable 261 This table represents the OSPF traffic engineering parameters that 262 are associated with the TE links. 264 7.4. teLinkSrlgTable 266 This table represents the shared risk link groups (SRLGs) associated 267 with TE links. 269 7.5. teLinkBandwidthTable 271 This table specifies the priority-based bandwidth traffic engineering 272 parameters associated with TE links. 274 7.6. dataBearingChannelTable 276 This table enumerates the data-bearing channels and their association 277 with TE link. 279 7.7. dataBearingChannelDescriptorTable 281 This table enumerates the link descriptors that each data-bearing 282 channel supports. 284 7.8. dataBearingChannelBandwidthTable 286 The data-bearing channel bandwidth table specifies the priority-based 287 bandwidth values associated with the data-bearing channels. 289 8. Example of Bundled Link Setup 291 In this section we provide a brief example of using the MIB 292 objects described in section 10 to set up a bundled link. 293 While this example is not meant to illustrate every 294 nuance of the MIB, it is intended as an aid to understanding some 295 of the key concepts. It is meant to be read after going through the 296 MIB itself. 298 Suppose that one would like to manually create a bundled link 299 out of two 1:1 TE links. Assume that the bundled link is associated 300 with SRLGs 10 and 50. Finally, let the data-bearing channels be port 301 entity interfaces (lambdas). The following example illustrates which 302 rows and corresponding objects might be created to accomplish this. 304 First, a bundled link entry is created. An ifEntry with the same 305 ifIndex and with ifType teLink needs to be created beforehand. 307 In teLinkTable: 308 { 309 ifIndex = 25, 310 teLinkNumberingType = unnumbered(2), 311 teLinkRowStatus = createAndGo(4) 312 } 314 In ifStackTable: 315 { 316 ifStackHigherLayer = 0, 317 ifStackLowerLayer = 25, 318 ifStackStatus = createAndGo(4) 319 } 321 Next, the two TE links are created. 323 In teLinkTable: 324 { 325 ifIndex = 20, 326 teLinkNumberingType = unnumbered(2), 327 teLinkMetric = 5, 328 teLinkResourceClass = 3, 329 teLinkRowStatus = createAndWait(5) 330 } 332 In ifStackTable: 333 { 334 ifStackHigherLayer = 25, 335 ifStackLowerLayer = 20, 336 ifStackStatus = createAndGo(4) 337 } 339 In teLinkTable: 340 { 341 ifIndex = 21, 342 teLinkNumberingType = unnumbered(2), 343 teLinkMetric = 5, 344 teLinkResourceClass = 3, 345 teLinkRowStatus = createAndWait(5) 346 } 348 In ifStackTable: 349 { 350 ifStackHigherLayer = 25, 351 ifStackLowerLayer = 21, 352 ifStackStatus = createAndGo(4) 354 } 356 The OSPF traffic engineering parameters are configured for the 357 TE links. 359 In teLinkOspfTeTable: 360 { 361 ifIndex = 20, 362 teLinkOspfLinkId = 'c0010101'H, -- 192.1.1.1 363 teLinkRowStatus = createAndGo(4) 364 } 366 In teLinkOspfTeTable: 367 { 368 ifIndex = 21, 369 teLinkOspfLinkId = 'c0010101'H, -- 192.1.1.1 370 teLinkRowStatus = createAndGo(4) 371 } 373 We assign SRLGs to the TE links. 375 In the teLinkSrlgTable: 376 { 377 ifIndex = 20, 378 srlg = 10, 379 srlgRowStatus = createAndGo(4) 380 } 382 In the teLinkSrlgTable: 383 { 384 ifIndex = 21, 385 srlg = 50, 386 srlgRowStatus = createAndGo(4) 387 } 389 The bundled link inherits the OSPF and SRLG properties from the 390 associated TE links. 392 Next, for each TE link, two data-bearing channels are created. 393 An ifEntry with the same ifIndex needs to be created beforehand. 395 In dataBearingChannelTable: 396 { 397 ifIndex = 40, 398 dataBearingChannelPreferredProtection = primary(1), 399 dataBearingChannelRowStatus = createAndGo(4) 400 } 401 In ifStackTable: 402 { 403 ifStackHigherLayer = 20, 404 ifStackLowerLayer = 40, 405 ifStackStatus = createAndGo(4) 406 } 408 In dataBearingChannelTable: 409 { 410 ifIndex = 43, 411 dataBearingChannelPreferredProtection = secondary(2), 412 dataBearingChannelRowStatus = createAndGo(4) 413 } 415 In ifStackTable: 416 { 417 ifStackHigherLayer = 20, 418 ifStackLowerLayer = 43, 419 ifStackStatus = createAndGo(4) 420 } 422 In dataBearingChannelTable: 423 { 424 ifIndex = 44, 425 dataBearingChannelPreferredProtection = primary(1), 426 dataBearingChannelRowStatus = createAndGo(4) 427 } 429 In ifStackTable: 430 { 431 ifStackHigherLayer = 21, 432 ifStackLowerLayer = 44, 433 ifStackStatus = createAndGo(4) 434 } 436 In dataBearingChannelTable: 437 { 438 ifIndex = 48, 439 dataBearingChannelPreferredProtection = secondary(2), 440 dataBearingChannelRowStatus = createAndGo(4) 441 } 443 In ifStackTable: 444 { 445 ifStackHigherLayer = 21, 446 ifStackLowerLayer = 48, 447 ifStackStatus = createAndGo(4) 448 } 449 In this example, once a data-bearing channel is added to the 450 dataBearingChannelTable, the associated link descriptors are 451 implicitly added to the dataBearingChannelDescriptorTable. 453 TE link link descriptors are derived from their data-bearing channel 454 link descriptors. 456 Note that the bandwidth attributes in teLinkDescriptorTable, 457 dataBearingChannelDescriptorTable, teLinkBandwidthTable 458 and dataBearingChannelBandwidthTable are maintained by the 459 device according to LSP creation/deletion at different priorities. 460 The values in the teLinkBandwidthTable are an aggregation 461 of the values for the data-bearing channels of the TE links and 462 the TE links of the bundled link. 464 9. Application of the Interfaces Group to TE Links 466 The Interfaces Group [IFMIB] defines generic managed objects for 467 managing interfaces. This memo contains the media-specific 468 extensions to the Interfaces Group for managing TE Link interfaces 469 as logical interfaces. 471 This memo assumes the interpretation of the Interfaces Group to be 472 in accordance with [IFMIB] which states that the interfaces table 473 (ifTable) contains information on the managed resource's 474 interfaces and that each sub-layer below the internetwork layer of 475 a network interface is considered an interface. Thus, the TE Link 476 interface is represented as an entry in the ifTable. The inter- 477 relation of entries in the ifTable is defined by Interfaces Stack 478 Group defined in [IFMIB]. 480 When using TE Link interfaces, the interface stack table might appear 481 as follows: 483 +----------------------------------------+ 484 | TE link-interface ifType = teLink(200) + 485 +----------------------------------------+ 486 | Underlying Layer... + 487 +----------------------------------------+ 489 In the above diagram, "Underlying Layer..." refers to the ifIndex 490 of any interface type, which has been defined for TE Link 491 interworking. Examples include ATM, Frame Relay, Ethernet, etc. 493 9.1. Support of the TE Link Layer by ifTable 495 Some specific interpretations of ifTable for the TE Link layer 496 follow. 498 Object Use for the TE Link layer 500 ifIndex Each TE Link interface is represented by an ifEntry. 502 ifDescr Description of the TE Link interface. 504 ifType The value that is allocated for TE Link is 200. 506 ifSpeed The total bandwidth in bits per second for use by 507 the TE Link layer. 509 ifPhysAddress Unused. 511 ifAdminStatus This variable indicates the administrator's intent 512 as to whether TE Link should be enabled, disabled, or 513 running in some diagnostic testing mode on this 514 interface. Also see [IFMIB]. 516 ifOperStatus This value reflects the actual or operational 517 status of TE Link on this interface. 519 ifLastChange See [IFMIB]. 521 ifInOctets The number of received octets over the interface, 522 i.e., the number of received octets in all data-bearing 523 channels associated with the interface. 525 ifOutOctets The number of transmitted octets over the 526 interface, i.e., the number of octets transmitted 527 over all data-bearing channels associated with the 528 interface. 530 ifInErrors The number of packets dropped due to 531 uncorrectable errors. 533 ifInUnknownProtos 534 The number of received packets discarded during 535 packet header validation. 537 ifOutErrors See [IFMIB]. 539 ifName Textual name (unique on this system) of the 540 interface or an octet string of zero length. 542 ifLinkUpDownTrapEnable 543 Default is disabled (2). 545 ifConnectorPresent 546 Set to false (2). 548 ifHighSpeed See [IFMIB]. 550 ifHCInOctets The 64-bit version of ifInOctets; supported if 551 required by the compliance statements in [IFMIB]. 553 ifHCOutOctets The 64-bit version of ifOutOctets; supported if 554 required by the compliance statements in [IFMIB]. 556 ifAlias The non-volatile 'alias' name for the interface as 557 specified by a network manager. 559 ifCounterDiscontinuityTime 560 See [IFMIB]. 562 Support for ifInOctets, ifOutOctets, ifInErrors, ifInUnknownProtos, 563 ifOutErrors, ifHCInOctets and ifHCOutOctets objects is not required 564 if encoding type is clear. For other encoding types, traffic 565 counters on a TE link are cumulative for all subinterfaces which it 566 binds together. 568 9.2. Using ifStackTable 570 This section describes by example how to use ifStackTable to 571 represent the relationship of TE links with underlying TE-enabled 572 interfaces. Implementors of the stack table for TE link interfaces 573 should look at the appropriate RFC for the service being stacked 574 on TE links. Examples given below are for illustration purposes 575 only. 577 Example: MPLS is being carried on 2 bundled TE links. 578 Each bundled TE link runs over a 1:1 optical 579 transport interface. 581 +---------------------------------+ 582 | mpls | 583 +---------------------------------+ 584 | 585 +---------------------------------+ 586 | teLink (Link Bundle) | 587 +---------------------------------+ 588 | | 589 +---------------+ +---------------+ 590 | teLink | | teLink | 591 +---------------+ +---------------+ 592 | | | | 593 +------+ +------+ +------+ +------+ 594 |oTrans| |oTrans| |oTrans| |oTrans| 595 +------+ +------+ +------+ +------+ 597 The assignment of the index values could for example be: 599 ifIndex Description 600 1 mpls (type 166) 601 2 teLink (type TBD) 602 3 teLink (type TBD) 603 4 teLink (type TBD) 604 5 opticalTransport (type 196) 605 6 opticalTransport (type 196) 606 7 opticalTransport (type 196) 607 8 opticalTransport (type 196) 609 The ifStackTable is then used to show the relationships between the 610 various interfaces. 612 ifStackTable Entries 614 HigherLayer LowerLayer 615 0 1 616 1 2 617 2 3 618 2 4 619 3 5 620 3 6 621 4 7 622 4 8 623 5 0 624 6 0 625 7 0 626 8 0 628 In the case where MPLS is using a single TE link, then 629 the upper TE link layer (link bundle) is not required. 631 +---------------+ 632 | mpls | 633 +---------------+ 634 | 636 +---------------+ 637 | teLink | 638 +---------------+ 639 | | 640 +------+ +------+ 641 |oTrans| |oTrans| 642 +------+ +------+ 644 The assignment of the index values could for example be: 646 ifIndex Description 647 1 mpls (type 166) 648 2 teLink (type TBD) 649 3 opticalTransport (type 196) 650 4 opticalTransport (type 196) 652 The ifStackTable is then used to show the relationships between the 653 various interfaces. 655 ifStackTable Entries 657 HigherLayer LowerLayer 658 0 1 659 1 2 660 2 3 661 2 4 662 3 0 663 4 0 665 10. Link Bundling MIB Definitions 667 LINK-BUNDLING-MIB DEFINITIONS ::= BEGIN 669 IMPORTS 670 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 671 experimental, Integer32, Unsigned32 672 FROM SNMPv2-SMI 674 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 675 FROM SNMPv2-CONF 677 TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType, 678 RowPointer, TimeStamp 679 FROM SNMPv2-TC 681 InterfaceIndex, InterfaceIndexOrZero, ifIndex 682 FROM IF-MIB 684 RouterID 685 FROM OSPF-MIB 687 InetAddressType, InetAddress 688 FROM INET-ADDRESS-MIB; 690 linkBundlingMIB MODULE-IDENTITY 691 LAST-UPDATED "200202261200Z" -- 26 February 2002 12:00:00 EST 692 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 693 CONTACT-INFO 694 " Martin Dubuc 695 Postal: Meriton Networks 696 3026 Solandt Road 697 Kanata, ON, CANADA K2K 2A5 698 Tel: +1-613-270-9279 x253 699 Email: martin.dubuc@meriton.com 701 Sudheer Dharanikota 702 Postal: Nayna Networks, Inc. 703 157 Topaz Street 704 Milipitas, CA 95035 705 Tel: +1-408-956-8000 x357 706 Email: sudheer@nayna.com 708 Thomas D. Nadeau 709 Postal: Cisco Systems, Inc. 710 300 Apollo Drive 711 Chelmsford, MA 01824 712 Tel: +1-978-244-3051 713 Email: tnadeau@cisco.com 715 Jonathan P. Lang 716 Postal: Calient Networks, Inc. 717 25 Castilian Drive 718 Goleta, CA 93117 719 Email: jplang@calient.net" 721 DESCRIPTION 722 "This MIB contains managed object definitions for 723 MPLS traffic engineering link bundling as 724 defined in: Kompella, K., Rekhter, Y., Berger, L., 725 Link Bundling in MPLS Traffic Engineering 726 Internet Draft , 727 November 2001." 729 -- Revision history. 730 REVISION 731 "200202261200Z" -- 26 February 2002 12:00:00 EST 732 DESCRIPTION 733 "- Updated MIB boiler plate and references. 734 - Added linkBundlingFullModuleCompliance conformance statement. 735 - Removed teLinkIpAddrType. Replaced numbered value with 736 ipV4 and ipV6 values in teLinkNumberingType. 737 - Updated description of all row status and storage type objects. 738 - Changed some of the enumerated value to start from 1 instead of 0. 739 - Updated references." 740 REVISION 741 "200109101200Z" -- 10 September 2001 12:00:00 EST 742 DESCRIPTION 743 "Removed teLinkRemoteId. Updated teLinkEncodingType and 744 dataBearingChannelEncodingType values." 745 REVISION 746 "200105223200Z" -- 22 May 2001 12:00:00 EST 747 DESCRIPTION 748 "Replaced InetAddressIPv4 and InetAddressIPv6 with InetAddress 749 and InetAddrType. Changed description of entries which extend 750 ifEntry. Made various minor corrections." 751 REVISION 752 "200105141200Z" -- 14 May 2001 12:00:00 EST 753 DESCRIPTION 754 "Replaced componentLinkTable by dataBearingChannelTable. 755 Replaced linkBundlingTable by teLinkTable. Converted TE links 756 into interfaces." 757 REVISION 758 "200102231200Z" -- 23 February 2001 12:00:00 EST 759 DESCRIPTION 760 "Initial draft version." 761 ::= { experimental 114 } 763 -- Textual Conventions 765 -- Top level components of this MIB 767 -- Notifications 768 linkBundlingNotifications OBJECT IDENTIFIER ::= { linkBundlingMIB 0 } 769 -- Tables, Scalars 770 linkBundlingObjects OBJECT IDENTIFIER ::= { linkBundlingMIB 1 } 771 -- Conformance 772 linkBundlingConformance OBJECT IDENTIFIER ::= { linkBundlingMIB 2 } 774 -- TE Link Table 775 teLinkTable OBJECT-TYPE 776 SYNTAX SEQUENCE OF TeLinkEntry 777 MAX-ACCESS not-accessible 778 STATUS current 779 DESCRIPTION 780 "This table specifies the grouping of data-bearing channels into 781 TE links and grouping of TE links into bundled links." 782 ::= { linkBundlingObjects 1 } 784 teLinkEntry OBJECT-TYPE 785 SYNTAX TeLinkEntry 786 MAX-ACCESS not-accessible 787 STATUS current 788 DESCRIPTION 789 "An entry in this table exists for each ifEntry with an 790 ifType of teLink(TBD), i.e. for every TE link. An ifEntry 791 in the ifTable must exist before a teLinkEntry is created with 792 the corresponding ifIndex. If a TE link entry in the ifTable is 793 destroyed, then so is the corresponding entry in the 794 teLinkTable. The administrative and operational status values 795 are controlled from the ifEntry. If the link is unnumbered, 796 ifIndex is also used as the outgoing interface identifier." 797 INDEX { ifIndex } 798 ::= { teLinkTable 1 } 800 TeLinkEntry ::= SEQUENCE { 801 teLinkNumberingType INTEGER, 802 teLinkIpAddr InetAddress, 803 teLinkRemoteIpAddr InetAddress, 804 teLinkMetric Unsigned32, 805 teLinkMuxCapability INTEGER, 806 teLinkProtectionType INTEGER, 807 teLinkWorkingPriority Unsigned32, 808 teLinkResourceClass Unsigned32, 809 teLinkIncomingIfId InterfaceIndexOrZero, 810 teLinkOutgoingIfId InterfaceIndexOrZero, 811 teLinkFlooding InterfaceIndexOrZero, 812 teLinkRowStatus RowStatus, 813 teLinkStorageType StorageType 814 } 816 teLinkNumberingType OBJECT-TYPE 817 SYNTAX INTEGER { 818 unnumbered(1), 819 ipV4(2), 820 ipV6(3) 821 } 822 MAX-ACCESS read-create 823 STATUS current 824 DESCRIPTION 825 "The TE link identifier address numbering type." 826 ::= { teLinkEntry 1 } 828 teLinkIpAddr OBJECT-TYPE 829 SYNTAX InetAddress 830 MAX-ACCESS read-create 831 STATUS current 832 DESCRIPTION 833 "For IPv4 and IPv6 numbered links, this object represents the 834 IP address associated with the TE link." 835 ::= { teLinkEntry 2 } 837 teLinkRemoteIpAddr OBJECT-TYPE 838 SYNTAX InetAddress 839 MAX-ACCESS read-create 840 STATUS current 841 DESCRIPTION 842 "The remote IP address associated with the TE link (IPv4 and 843 IPv6 numbered links)." 844 ::= { teLinkEntry 3 } 846 teLinkMetric OBJECT-TYPE 847 SYNTAX Unsigned32 848 MAX-ACCESS read-create 849 STATUS current 850 DESCRIPTION 851 "The traffic engineering metric for the TE link is 852 derived from its data-bearing channels. All data-bearing 853 channels within the TE link must have the same traffic 854 engineering metric." 855 REFERENCE 856 "draft-kompella-mpls-bundle-05.txt - Link Bundling in MPLS 857 Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, 858 February 2001." 859 ::= { teLinkEntry 4 } 861 teLinkMuxCapability OBJECT-TYPE 862 SYNTAX INTEGER { 863 packetSwitch1(1), 864 packetSwitch2(2), 865 packetSwitch3(3), 866 packetSwitch4(4), 867 layer2Switch(51), 868 tdm(100), 869 lambdaSwitch(150), 870 fiberSwitch(200) 872 } 873 MAX-ACCESS read-only 874 STATUS current 875 DESCRIPTION 876 "This attribute specifies link multiplex capability of the 877 TE link, which is derived from its data-bearing channels. All 878 data-bearing channels within the same TE link must have the 879 same link multiplex capability." 880 REFERENCE 881 "draft-ietf-mpls-lsp-hierarchy-03.txt - LSP Hierarchy with 882 MPLS TE, K. Kompella, Y. Rekhter, May 2001." 883 ::= { teLinkEntry 5 } 885 teLinkProtectionType OBJECT-TYPE 886 SYNTAX INTEGER { 887 unprotected(1), 888 shared(2), 889 dedicated1For1(3), 890 dedicated1Plus1(4), 891 enhanced(5) 892 } 893 MAX-ACCESS read-create 894 STATUS current 895 DESCRIPTION 896 "This attribute specifies link protection type of the 897 TE link." 898 REFERENCE 899 "draft-ietf-ccamp-ospf-gmpls-extensions-04.txt - OSPF Extensions 900 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 901 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 902 D. Saha, V. Sharma, February 2002." 903 ::= { teLinkEntry 6 } 905 teLinkWorkingPriority OBJECT-TYPE 906 SYNTAX Unsigned32 (0..7) 907 MAX-ACCESS read-create 908 STATUS current 909 DESCRIPTION 910 "This object represents a priority value such that a new 911 connection with a higher priority, i.e. numerically lower than 912 this value, is guaranteed to be setup on a primary channel and 913 not on a secondary channel." 914 REFERENCE 915 "draft-ietf-ccamp-ospf-gmpls-extensions-04.txt - OSPF Extensions 916 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 917 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 918 D. Saha, V. Sharma, Februrary 2002." 919 ::= { teLinkEntry 7 } 921 teLinkResourceClass OBJECT-TYPE 922 SYNTAX Unsigned32 923 MAX-ACCESS read-create 924 STATUS current 925 DESCRIPTION 926 "This attribute specifies the TE link resource class. 927 The resource class is a 32 bit bitfield. The resource class for 928 a link bundle is derived from the resource class of its 929 TE links. All TE links within a link bundle must have the 930 same resource class." 931 ::= { teLinkEntry 8 } 933 teLinkIncomingIfId OBJECT-TYPE 934 SYNTAX InterfaceIndexOrZero 935 MAX-ACCESS read-create 936 STATUS current 937 DESCRIPTION 938 "For unnumbered links, the incoming interface is set to the 939 outgoing interface identifier chosen by the neighboring LSR 940 for the reverse link corresponding to this TE link." 941 REFERENCE 942 "draft-ietf-mpls-bundle-01.txt - Link Bundling in MPLS 943 Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, 944 November 2001." 945 ::= { teLinkEntry 9 } 947 teLinkOutgoingIfId OBJECT-TYPE 948 SYNTAX InterfaceIndexOrZero 949 MAX-ACCESS read-create 950 STATUS current 951 DESCRIPTION 952 "If the link is unnumbered, the outgoing interface identifier is 953 set to the outgoing interface identifier chosen for the TE link 954 by the advertising LSR." 955 REFERENCE 956 "draft-ietf-mpls-bundle-01.txt - Link Bundling in MPLS 957 Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, 958 November 2001." 959 ::= { teLinkEntry 10 } 961 teLinkFlooding OBJECT-TYPE 962 SYNTAX InterfaceIndexOrZero 963 MAX-ACCESS read-create 964 STATUS current 965 DESCRIPTION 966 "This object only has significance for link bundles which 967 encoding type is not clear. For these link bundles, this object 968 identifies the TE link on which to restrict flooding. If the 969 value is zero, then flooding must be done on all TE links 970 within the link bundle." 971 REFERENCE 972 "draft-ietf-ospf-isis-flood-opt-01.txt - Flooding optimization 973 in link-state routing protocols, A. Zinin, M. Shand, 974 March 2001." 975 DEFVAL { 0 } 976 ::= { teLinkEntry 12 } 978 teLinkRowStatus OBJECT-TYPE 979 SYNTAX RowStatus 980 MAX-ACCESS read-create 981 STATUS current 982 DESCRIPTION 983 "This variable is used to create, modify, and/or 984 delete a row in this table. All read-create objects 985 can be changed when teLinkRowStatus is active." 986 ::= { teLinkEntry 13 } 988 teLinkStorageType OBJECT-TYPE 989 SYNTAX StorageType 990 MAX-ACCESS read-create 991 STATUS current 992 DESCRIPTION 993 "The storage type for this conceptual row in the 994 teLinkTable. Conceptual rows having the value 995 'permanent' need not allow write-access to any 996 columnar object in the row." 997 ::= { teLinkEntry 14 } 999 -- End of teLinkTable 1001 -- TE Link Descriptor Table 1003 teLinkDescriptorTable OBJECT-TYPE 1004 SYNTAX SEQUENCE OF TeLinkDescriptorEntry 1005 MAX-ACCESS not-accessible 1006 STATUS current 1007 DESCRIPTION 1008 "This table specifies the link descriptors associated with the 1009 TE links." 1010 ::= { linkBundlingObjects 2 } 1012 teLinkDescriptorEntry OBJECT-TYPE 1013 SYNTAX TeLinkDescriptorEntry 1014 MAX-ACCESS not-accessible 1015 STATUS current 1016 DESCRIPTION 1017 "An entry in this table is created for every TE link descriptor. 1018 An ifEntry in the ifTable must exist before a 1019 teLinkDescriptorEntry using the same ifIndex is created. 1020 If a TE link entry in the ifTable is destroyed, then so are all 1021 entries in the teLinkDescriptorTable that use the ifIndex of 1022 this TE link." 1023 INDEX { ifIndex, teLinkDescriptorId } 1024 ::= { teLinkDescriptorTable 1 } 1026 TeLinkDescriptorEntry ::= SEQUENCE { 1027 teLinkDescriptorId Unsigned32, 1028 teLinkEncodingType INTEGER, 1029 teLinkDescrPriority Unsigned32, 1030 teLinkMinReservableBandwidth Unsigned32, 1031 teLinkMaxReservableBandwidth Unsigned32, 1032 teLinkDescrRowStatus RowStatus, 1033 teLinkDescrStorageType StorageType 1034 } 1036 teLinkDescriptorId OBJECT-TYPE 1037 SYNTAX Unsigned32 1038 MAX-ACCESS not-accessible 1039 STATUS current 1040 DESCRIPTION 1041 "This object specifies the link descriptor identifier." 1042 ::= { teLinkDescriptorEntry 1 } 1044 teLinkEncodingType OBJECT-TYPE 1045 SYNTAX INTEGER { 1046 packet(1), 1047 ethernetV2Dix(2), 1048 ansiPdh(3), 1049 etsiPdh(4), 1050 sdhItuG707(5), 1051 sonetAnsiT1105(6), 1052 digitalWrapper(7), 1053 lambda(8), 1054 fiber(9), 1055 ethernet8023(10), 1056 fiberChannel(11) 1057 } 1058 MAX-ACCESS read-only 1059 STATUS current 1060 DESCRIPTION 1061 "This attribute specifies the TE link encoding type." 1062 REFERENCE 1063 "draft-ietf-mpls-generalized-signaling-07.txt - Generalized 1064 MPLS Signaling Functional Description, P. Ashwood-Smith, 1065 A. Banarjee, L. Berger, G. Bernstein, J. Drake, Y. Fan, 1066 E. Mannie, J. Lang, B. Rajagopalan, Y. Rekhter, D. Saha, 1067 V. Sharma, G. Swallow, Z. Tang, November 2001." 1068 ::= { teLinkDescriptorEntry 2 } 1070 teLinkDescrPriority OBJECT-TYPE 1071 SYNTAX Unsigned32 (0..7) 1072 MAX-ACCESS read-only 1073 STATUS current 1074 DESCRIPTION 1075 "This object specifies the lowest priority at which that link 1076 encoding type is available." 1077 REFERENCE 1078 "draft-ietf-ccamp-ospf-gmpls-extensions-04.txt - OSPF Extensions 1079 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1080 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1081 D. Saha, V. Sharma, February 2002." 1082 ::= { teLinkDescriptorEntry 3 } 1084 teLinkMinReservableBandwidth OBJECT-TYPE 1085 SYNTAX Unsigned32 1086 MAX-ACCESS read-only 1087 STATUS current 1088 DESCRIPTION 1089 "This attribute specifies the minimum reservable bandwidth on 1090 the TE link. This is derived from the union of the 1091 minimum reservable bandwidth of all the data-bearing 1092 channels associated with the TE link that can be used to carry 1093 live traffic. This value is an estimate in units of 1,000 bits 1094 per second." 1095 REFERENCE 1096 "draft-ietf-ccamp-ospf-gmpls-extensions-04.txt - OSPF Extensions 1097 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1098 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1099 D. Saha, V. Sharma, February 2002." 1100 ::= { teLinkDescriptorEntry 4 } 1102 teLinkMaxReservableBandwidth OBJECT-TYPE 1103 SYNTAX Unsigned32 1104 MAX-ACCESS read-only 1105 STATUS current 1106 DESCRIPTION 1107 "This attribute specifies the maximum reservable bandwidth on 1108 the TE link. This is the union of the maximum reservable 1109 bandwidth of all the data-bearing channels within the 1110 TE link that can be used to carry live traffic. This value 1111 is an estimate in units of 1,000 bits per second." 1113 REFERENCE 1114 "draft-ietf-ccamp-ospf-gmpls-extensions-04.txt - OSPF Extensions 1115 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1116 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1117 D. Saha, V. Sharma, February 2002." 1118 ::= { teLinkDescriptorEntry 5 } 1120 teLinkDescrRowStatus OBJECT-TYPE 1121 SYNTAX RowStatus 1122 MAX-ACCESS read-create 1123 STATUS current 1124 DESCRIPTION 1125 "This variable is used to create, modify, and/or 1126 delete a row in this table. All read-create objects 1127 can be changed when teLinkDescrRowStatus is active." 1128 ::= { teLinkDescriptorEntry 6 } 1130 teLinkDescrStorageType OBJECT-TYPE 1131 SYNTAX StorageType 1132 MAX-ACCESS read-create 1133 STATUS current 1134 DESCRIPTION 1135 "The storage type for this conceptual row in the 1136 teLinkDescriptorTable. Conceptual rows having the value 1137 'permanent' need not allow write-access to any 1138 columnar object in the row." 1139 ::= { teLinkDescriptorEntry 7 } 1141 -- End of teLinkDescriptorTable 1143 -- OSPF Traffic Engineering Parameters for TE Links 1145 teLinkOspfTeTable OBJECT-TYPE 1146 SYNTAX SEQUENCE OF TeLinkOspfTeEntry 1147 MAX-ACCESS not-accessible 1148 STATUS current 1149 DESCRIPTION 1150 "This table specifies the OSPF traffic engineering information 1151 associated with TE links." 1152 ::= { linkBundlingObjects 3 } 1154 teLinkOspfTeEntry OBJECT-TYPE 1155 SYNTAX TeLinkOspfTeEntry 1156 MAX-ACCESS not-accessible 1157 STATUS current 1158 DESCRIPTION 1159 "If OSPF is enabled, an entry in this table is created for 1160 every TE link." 1161 AUGMENTS { teLinkEntry } 1162 ::= { teLinkOspfTeTable 1 } 1164 TeLinkOspfTeEntry ::= SEQUENCE { 1165 teLinkOspfLinkType INTEGER, 1166 teLinkOspfLinkId RouterID 1167 } 1169 teLinkOspfLinkType OBJECT-TYPE 1170 SYNTAX INTEGER { 1171 pointToPoint(1), 1172 multiAccess(2) 1173 } 1174 MAX-ACCESS read-only 1175 STATUS current 1176 DESCRIPTION 1177 "This attribute specifies the OSPF link type for the TE link. 1178 All TE links within the same bundle must have the same 1179 link type." 1180 ::= { teLinkOspfTeEntry 1 } 1182 teLinkOspfLinkId OBJECT-TYPE 1183 SYNTAX RouterID 1184 MAX-ACCESS read-only 1185 STATUS current 1186 DESCRIPTION 1187 "On point-to-point link, the link identifier is the Router ID 1188 of the neighbor. For bundled link, is derived from the link 1189 identifier associated with its TE links." 1190 REFERENCE 1191 "draft-ietf-mpls-bundle-01.txt - Link Bundling in MPLS 1192 Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, 1193 November 2001." 1194 ::= { teLinkOspfTeEntry 2 } 1196 -- End of teLinkOspfTeTable 1198 -- TE Link Shared Risk Link Group Table 1200 teLinkSrlgTable OBJECT-TYPE 1201 SYNTAX SEQUENCE OF TeLinkSrlgEntry 1202 MAX-ACCESS not-accessible 1203 STATUS current 1204 DESCRIPTION 1205 "This table specifies the SRLGs associated with TE links." 1206 ::= { linkBundlingObjects 4 } 1208 teLinkSrlgEntry OBJECT-TYPE 1209 SYNTAX TeLinkSrlgEntry 1210 MAX-ACCESS not-accessible 1211 STATUS current 1212 DESCRIPTION 1213 "An entry in this table contains information about a 1214 SRLG associated with a TE link. 1215 An ifEntry in the ifTable must exist before a 1216 teLinkSrlgEntry using the same ifIndex is created. 1217 If a TE link entry in the ifTable is destroyed, then so are all 1218 entries in the teLinkSrlgTable that use the ifIndex of 1219 this TE link." 1220 INDEX { ifIndex, srlg } 1221 ::= { teLinkSrlgTable 1 } 1223 TeLinkSrlgEntry ::= SEQUENCE { 1224 srlg Unsigned32, 1225 srlgRowStatus RowStatus, 1226 srlgStorageType StorageType 1227 } 1229 srlg OBJECT-TYPE 1230 SYNTAX Unsigned32 1231 MAX-ACCESS not-accessible 1232 STATUS current 1233 DESCRIPTION 1234 "This identifies a SRLG supported by the TE link." 1235 REFERENCE 1236 "draft-ietf-ccamp-ospf-gmpls-extensions-04.txt - OSPF Extensions 1237 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1238 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1239 D. Saha, V. Sharma, February 2002." 1240 ::= { teLinkSrlgEntry 1 } 1242 srlgRowStatus OBJECT-TYPE 1243 SYNTAX RowStatus 1244 MAX-ACCESS read-create 1245 STATUS current 1246 DESCRIPTION 1247 "This variable is used to create, modify, and/or 1248 delete a row in this table. All read-create objects 1249 can be changed when srlgRowStatus is active." 1250 ::= { teLinkSrlgEntry 2 } 1252 srlgStorageType OBJECT-TYPE 1253 SYNTAX StorageType 1254 MAX-ACCESS read-create 1255 STATUS current 1256 DESCRIPTION 1257 "The storage type for this conceptual row in the 1258 teLinkSrlgTable. Conceptual rows having the value 1259 'permanent' need not allow write-access to any 1260 columnar object in the row." 1261 ::= { teLinkSrlgEntry 3 } 1263 -- End of teLinkSrlgTable 1265 -- TE Link Bandwidth Table 1267 teLinkBandwidthTable OBJECT-TYPE 1268 SYNTAX SEQUENCE OF TeLinkBandwidthEntry 1269 MAX-ACCESS not-accessible 1270 STATUS current 1271 DESCRIPTION 1272 "This table specifies the priority-based bandwidth table 1273 for TE links." 1274 ::= { linkBundlingObjects 5 } 1276 teLinkBandwidthEntry OBJECT-TYPE 1277 SYNTAX TeLinkBandwidthEntry 1278 MAX-ACCESS not-accessible 1279 STATUS current 1280 DESCRIPTION 1281 "An entry in this table contains information about 1282 the priority-based bandwidth of TE links. An ifEntry in the 1283 ifTable must exist before a teLinkBandwidthEntry using the 1284 same ifIndex is created. If a TE link entry in the ifTable 1285 is destroyed, then so are all entries in the teLinkBandwidthTable 1286 that use the ifIndex of this TE link." 1287 INDEX { ifIndex, teLinkPriority } 1288 ::= { teLinkBandwidthTable 1 } 1290 TeLinkBandwidthEntry ::= SEQUENCE { 1291 teLinkPriority Unsigned32, 1292 teLinkUnreservedBandwidth Unsigned32, 1293 teLinkMaximumLspBandwidth Unsigned32, 1294 teLinkBandwidthRowStatus RowStatus, 1295 teLinkBandwidthStorageType StorageType 1296 } 1298 teLinkPriority OBJECT-TYPE 1299 SYNTAX Unsigned32 (1..8) 1300 MAX-ACCESS not-accessible 1301 STATUS current 1302 DESCRIPTION 1303 "This attribute specifies the priority. It should be mapped 1304 to a number between 0 and 7" 1305 REFERENCE 1306 "draft-ietf-ccamp-ospf-gmpls-extensions-04.txt - OSPF Extensions 1307 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1308 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1309 D. Saha, V. Sharma, February 2002." 1310 ::= { teLinkBandwidthEntry 1 } 1312 teLinkUnreservedBandwidth OBJECT-TYPE 1313 SYNTAX Unsigned32 1314 MAX-ACCESS read-only 1315 STATUS current 1316 DESCRIPTION 1317 "This attribute specifies the TE link unreserved 1318 bandwidth at priority p. It is the sum of the unreserved 1319 bandwidths at priority p of all data-bearing channel associated 1320 with the TE link (excludes all channels that are strictly 1321 used as protecting channels). This value is an estimate in units 1322 of 1,000 bits per second." 1323 REFERENCE 1324 "draft-ietf-mpls-bundle-05.txt - Link Bundling in MPLS 1325 Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, 1326 November 2001." 1327 ::= { teLinkBandwidthEntry 2 } 1329 teLinkMaximumLspBandwidth OBJECT-TYPE 1330 SYNTAX Unsigned32 1331 MAX-ACCESS read-only 1332 STATUS current 1333 DESCRIPTION 1334 "This attribute specifies the TE link maximum 1335 LSP bandwidth at priority p. It is the maximum of all 1336 maximum LSP bandwidth at priority p of the data-bearing channels 1337 associated with the TE link (excludes all channels that are 1338 strictly used as protecting channels). This value is an estimate 1339 in units of 1,000 bits per second." 1340 REFERENCE 1341 "draft-ietf-mpls-bundle-05.txt - Link Bundling in MPLS 1342 Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, 1343 November 2001." 1344 ::= { teLinkBandwidthEntry 3 } 1346 teLinkBandwidthRowStatus OBJECT-TYPE 1347 SYNTAX RowStatus 1348 MAX-ACCESS read-create 1349 STATUS current 1350 DESCRIPTION 1351 "This variable is used to create, modify, and/or 1352 delete a row in this table. All read-create objects 1353 can be changed when teLinkBandwidthRowStatus is active." 1354 ::= { teLinkBandwidthEntry 4 } 1356 teLinkBandwidthStorageType OBJECT-TYPE 1357 SYNTAX StorageType 1358 MAX-ACCESS read-create 1359 STATUS current 1360 DESCRIPTION 1361 "The storage type for this conceptual row in the 1362 teLinkBandwidthTable. Conceptual rows having the value 1363 'permanent' need not allow write-access to any 1364 columnar object in the row." 1365 ::= { teLinkBandwidthEntry 5 } 1367 -- End of teLinkBandwidthTable 1369 -- Data-bearing Channel Table 1371 dataBearingChannelTable OBJECT-TYPE 1372 SYNTAX SEQUENCE OF DataBearingChannelEntry 1373 MAX-ACCESS not-accessible 1374 STATUS current 1375 DESCRIPTION 1376 "This table specifies the data-bearing channel 1377 parameters." 1378 ::= { linkBundlingObjects 6 } 1380 dataBearingChannelEntry OBJECT-TYPE 1381 SYNTAX DataBearingChannelEntry 1382 MAX-ACCESS not-accessible 1383 STATUS current 1384 DESCRIPTION 1385 "An entry in this table exists for each ifEntry that represents 1386 a data-bearing channel. An ifEntry must exist in the ifTable 1387 before a dataBearingChannelEntry is created with the 1388 corresponding ifIndex. If an entry representing a data-bearing 1389 channel is destroyed in the ifTable, then so is the 1390 corresponding entry in the dataBearingChannelTable. The 1391 administrative and operational status values are controlled 1392 from the ifEntry." 1393 INDEX { ifIndex } 1394 ::= { dataBearingChannelTable 1 } 1396 DataBearingChannelEntry ::= SEQUENCE { 1397 dataBearingChannelLinkMuxCapability INTEGER, 1398 dataBearingChannelPreferredProtection INTEGER, 1399 dataBearingChannelCurrentProtection INTEGER, 1400 dataBearingChannelRowStatus RowStatus, 1401 dataBearingChannelStorageType StorageType 1402 } 1404 dataBearingChannelLinkMuxCapability OBJECT-TYPE 1405 SYNTAX INTEGER { 1406 packetSwitch1(1), 1407 packetSwitch2(2), 1408 packetSwitch3(3), 1409 packetSwitch4(4), 1410 layer2Switch(51), 1411 tdm(100), 1412 lambdaSwitch(150), 1413 fiberSwitch(200) 1414 } 1415 MAX-ACCESS read-create 1416 STATUS current 1417 DESCRIPTION 1418 "This attribute specifies link multiplexing capabilities of the 1419 data-bearing channel." 1420 REFERENCE 1421 "draft-ietf-mpls-lsp-hierarchy-02.txt - LSP Hierarchy with 1422 MPLS TE, K. Kompella, Y. Rekhter, February 2001." 1423 ::= { dataBearingChannelEntry 1 } 1425 dataBearingChannelPreferredProtection OBJECT-TYPE 1426 SYNTAX INTEGER { 1427 primary(1), 1428 secondary(2) 1429 } 1430 MAX-ACCESS read-create 1431 STATUS current 1432 DESCRIPTION 1433 "This attribute specifies whether this data-bearing channel is 1434 a primary or secondary entity." 1435 ::= { dataBearingChannelEntry 2 } 1437 dataBearingChannelCurrentProtection OBJECT-TYPE 1438 SYNTAX INTEGER { 1439 primary(1), 1440 secondary(2) 1441 } 1442 MAX-ACCESS read-only 1443 STATUS current 1444 DESCRIPTION 1445 "This attribute specifies whether this data-bearing channel is 1446 currently used as primary or secondary channel." 1447 ::= { dataBearingChannelEntry 3 } 1449 dataBearingChannelRowStatus OBJECT-TYPE 1450 SYNTAX RowStatus 1451 MAX-ACCESS read-create 1452 STATUS current 1453 DESCRIPTION 1454 "This variable is used to create, modify, and/or 1455 delete a row in this table. All read-create objects 1456 can be changed when dataBearingChannelRowStatus is active." 1457 ::= { dataBearingChannelEntry 4 } 1459 dataBearingChannelStorageType OBJECT-TYPE 1460 SYNTAX StorageType 1461 MAX-ACCESS read-create 1462 STATUS current 1463 DESCRIPTION 1464 "The storage type for this conceptual row in the 1465 dataBearingChannelTable. Conceptual rows having the value 1466 'permanent' need not allow write-access to any 1467 columnar object in the row." 1468 ::= { dataBearingChannelEntry 5 } 1470 -- End of dataBearingChannelTable 1472 -- Data-bearing Channel Link Descriptor Table 1474 dataBearingChannelDescriptorTable OBJECT-TYPE 1475 SYNTAX SEQUENCE OF DataBearingChannelDescrEntry 1476 MAX-ACCESS not-accessible 1477 STATUS current 1478 DESCRIPTION 1479 "This table specifies the link descriptors associated with the 1480 data-bearing channels." 1481 ::= { linkBundlingObjects 7 } 1483 dataBearingChannelDescrEntry OBJECT-TYPE 1484 SYNTAX DataBearingChannelDescrEntry 1485 MAX-ACCESS not-accessible 1486 STATUS current 1487 DESCRIPTION 1488 "An entry in this table is created for every data-bearing channel 1489 descriptor. An ifEntry in the ifTable must exist before a 1490 dataBearingChannelDescrEntry using the same ifIndex is created. 1491 If a data-bearing channel entry in the ifTable is destroyed, 1492 then so are all entries in the 1493 dataBearingChannelDescriptorTable that use the ifIndex of 1494 this data-bearing channel." 1495 INDEX { ifIndex, dataBearingChannelDescrId } 1496 ::= { dataBearingChannelDescriptorTable 1 } 1498 DataBearingChannelDescrEntry ::= SEQUENCE { 1499 dataBearingChannelDescrId Unsigned32, 1500 dataBearingChannelEncodingType INTEGER, 1501 dataBearingChannelDescrPriority Unsigned32, 1502 dataBearingChannelMinReservableBandwidth Unsigned32, 1503 dataBearingChannelMaxReservableBandwidth Unsigned32, 1504 dataBearingChannelDescrRowStatus RowStatus, 1505 dataBearingChannelDescrStorageType StorageType 1506 } 1508 dataBearingChannelDescrId OBJECT-TYPE 1509 SYNTAX Unsigned32 1510 MAX-ACCESS not-accessible 1511 STATUS current 1512 DESCRIPTION 1513 "This object specifies the link descriptor identifier." 1514 ::= { dataBearingChannelDescrEntry 1 } 1516 dataBearingChannelEncodingType OBJECT-TYPE 1517 SYNTAX INTEGER { 1518 packet(1), 1519 ethernetV2(2), 1520 ansiPdh(3), 1521 etsiPdh(4), 1522 sdhItu1996(5), 1523 sonetAnsi1995(6), 1524 digitalWrapper(7), 1525 lambda(8), 1526 fiber(9), 1527 ethernet8023(10), 1528 sdhItu2000(11), 1529 sonetAnsi2000(12) 1530 } 1531 MAX-ACCESS read-create 1532 STATUS current 1533 DESCRIPTION 1534 "This attribute specifies the data-bearing channel encoding type." 1535 REFERENCE 1536 "draft-ietf-ccamp-ospf-gmpls-extensions-04.txt - OSPF Extensions 1537 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1538 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1539 D. Saha, V. Sharma, February 2002." 1540 ::= { dataBearingChannelDescrEntry 2 } 1542 dataBearingChannelDescrPriority OBJECT-TYPE 1543 SYNTAX Unsigned32 (0..7) 1544 MAX-ACCESS read-create 1545 STATUS current 1546 DESCRIPTION 1547 "This object specifies the lowest priority at which that link 1548 encoding type is available for the data-bearing channel." 1549 REFERENCE 1550 "draft-ietf-ccamp-ospf-gmpls-extensions-04.txt - OSPF Extensions 1551 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1552 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1553 D. Saha, V. Sharma, February 2002." 1554 ::= { dataBearingChannelDescrEntry 3 } 1556 dataBearingChannelMinReservableBandwidth OBJECT-TYPE 1557 SYNTAX Unsigned32 1558 MAX-ACCESS read-create 1559 STATUS current 1560 DESCRIPTION 1561 "This attribute specifies the minimum reservable bandwidth on 1562 the data-bearing channel. This value is an estimate 1563 in units of 1,000 bits per second." 1564 REFERENCE 1565 "draft-ietf-ccamp-ospf-gmpls-extensions-04.txt - OSPF Extensions 1566 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1567 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1568 D. Saha, V. Sharma, February 2002." 1569 ::= { dataBearingChannelDescrEntry 4 } 1571 dataBearingChannelMaxReservableBandwidth OBJECT-TYPE 1572 SYNTAX Unsigned32 1573 MAX-ACCESS read-only 1574 STATUS current 1575 DESCRIPTION 1576 "This attribute specifies the maximum reservable bandwidth on 1577 the data-bearing channel. This value is an estimate 1578 in units of 1,000 bits per second." 1579 REFERENCE 1580 "draft-ietf-ccamp-ospf-gmpls-extensions-04.txt - OSPF Extensions 1581 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1582 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1583 D. Saha, V. Sharma, February 2002." 1584 ::= { dataBearingChannelDescrEntry 5 } 1586 dataBearingChannelDescrRowStatus OBJECT-TYPE 1587 SYNTAX RowStatus 1588 MAX-ACCESS read-create 1589 STATUS current 1590 DESCRIPTION 1591 "This variable is used to create, modify, and/or 1592 delete a row in this table. All read-create objects 1593 can be changed when dataBearingChannelDescrRowStatus is active." 1594 ::= { dataBearingChannelDescrEntry 6 } 1596 dataBearingChannelDescrStorageType OBJECT-TYPE 1597 SYNTAX StorageType 1598 MAX-ACCESS read-create 1599 STATUS current 1600 DESCRIPTION 1601 "The storage type for this conceptual row in the 1602 dataBearingChannelDescriptorTable. Conceptual rows 1603 having the value 'permanent' need not allow write-access 1604 to any columnar object in the row." 1605 ::= { dataBearingChannelDescrEntry 7 } 1607 -- End of dataBearingChannelDescriptorTable 1609 -- Data-bearing Channel Bandwidth Table 1611 dataBearingChannelBandwidthTable OBJECT-TYPE 1612 SYNTAX SEQUENCE OF DataBearingChannelBandwidthEntry 1613 MAX-ACCESS not-accessible 1614 STATUS current 1615 DESCRIPTION 1616 "This table specifies the priority-based bandwidth 1617 for data-bearing channels." 1618 ::= { linkBundlingObjects 8 } 1620 dataBearingChannelBandwidthEntry OBJECT-TYPE 1621 SYNTAX DataBearingChannelBandwidthEntry 1622 MAX-ACCESS not-accessible 1623 STATUS current 1624 DESCRIPTION 1625 "An entry in this table contains information about 1626 the priority-based bandwidth on data-bearing channels. 1627 An ifEntry in the ifTable must exist before a 1628 dataBearingChannelBandwidthEntry using the same ifIndex is 1629 created. If a data-bearing channel entry in the ifTable is 1630 destroyed, then so are all entries in the 1631 dataBearingChannelBandwidthTable that use the ifIndex of 1632 this data-bearing channel." 1633 INDEX { ifIndex, dataBearingChannelPriority } 1634 ::= { dataBearingChannelBandwidthTable 1 } 1636 DataBearingChannelBandwidthEntry ::= SEQUENCE { 1637 dataBearingChannelPriority Unsigned32, 1638 dataBearingChannelUnreservedBandwidth Unsigned32, 1639 dataBearingChannelMaximumLspBandwidth Unsigned32, 1640 dataBearingChannelBwRowStatus RowStatus, 1641 dataBearingChannelBwStorageType StorageType 1642 } 1644 dataBearingChannelPriority OBJECT-TYPE 1645 SYNTAX Unsigned32 (1..8) 1646 MAX-ACCESS not-accessible 1647 STATUS current 1648 DESCRIPTION 1649 "This attribute specifies the priority. It should be mapped 1650 to a number between 0 and 7." 1651 REFERENCE 1652 "draft-ietf-ccamp-ospf-gmpls-extensions-04.txt - OSPF Extensions 1653 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1654 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1655 D. Saha, V. Sharma, February 2002." 1656 ::= { dataBearingChannelBandwidthEntry 1 } 1658 dataBearingChannelUnreservedBandwidth OBJECT-TYPE 1659 SYNTAX Unsigned32 1660 MAX-ACCESS read-only 1661 STATUS current 1662 DESCRIPTION 1663 "This attribute specifies the data-bearing channel unreserved 1664 bandwidth at priority p. This value is an estimate 1665 in units of 1,000 bits per second." 1666 REFERENCE 1667 "draft-ietf-ccamp-ospf-gmpls-extensions-04.txt - OSPF Extensions 1668 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1669 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1670 D. Saha, V. Sharma, February 2002." 1671 ::= { dataBearingChannelBandwidthEntry 2 } 1673 dataBearingChannelMaximumLspBandwidth OBJECT-TYPE 1674 SYNTAX Unsigned32 1675 MAX-ACCESS read-only 1676 STATUS current 1677 DESCRIPTION 1678 "This attribute specifies the data-bearing channel maximum 1679 LSP bandwidth at priority p. This value is an estimate 1680 in units of 1,000 bits per second." 1681 REFERENCE 1682 "draft-ietf-ccamp-ospf-gmpls-extensions-04.txt - OSPF Extensions 1683 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1684 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1685 D. Saha, V. Sharma, February 2002." 1686 ::= { dataBearingChannelBandwidthEntry 3 } 1688 dataBearingChannelBwRowStatus OBJECT-TYPE 1689 SYNTAX RowStatus 1690 MAX-ACCESS read-create 1691 STATUS current 1692 DESCRIPTION 1693 "This variable is used to create, modify, and/or 1694 delete a row in this table. All read-create objects 1695 can be changed when dataBearingChannelBwRowStatus is active." 1696 ::= { dataBearingChannelBandwidthEntry 4 } 1698 dataBearingChannelBwStorageType OBJECT-TYPE 1699 SYNTAX StorageType 1700 MAX-ACCESS read-create 1701 STATUS current 1702 DESCRIPTION 1703 "The storage type for this conceptual row in the 1704 dataBearingChannelBandwidthTable. Conceptual rows 1705 having the value 'permanent' need not allow write-access 1706 to any columnar object in the row." 1707 ::= { dataBearingChannelBandwidthEntry 5 } 1709 -- End of dataBearingChannelBandwidthTable 1711 -- Notification Configuration 1713 linkBundlingNotifEnable OBJECT-TYPE 1714 SYNTAX TruthValue 1715 MAX-ACCESS read-write 1716 STATUS current 1717 DESCRIPTION 1718 "If this object is true, then it enables the 1719 generation of the link bundling notifications, 1720 otherwise these notifications are not emitted." 1721 DEFVAL { false } 1722 ::= { linkBundlingObjects 9 } 1724 -- Notifications 1726 -- Bundled Link Notifications 1728 linkBundleMismatch NOTIFICATION-TYPE 1729 OBJECTS { ifIndex } 1730 STATUS current 1731 DESCRIPTION 1732 "This notification is generated when a mismatch is found on a 1733 bundled link. Such mismatch can be detected for instance if one 1734 of the traffic engineering parameters is not consistent across 1735 all TE links within a bundled link (resource class, 1736 OSPF link type, etc.)." 1737 ::= { linkBundlingNotifications 1 } 1739 -- End of notifications 1741 -- Module compliance 1743 linkBundlingGroups 1744 OBJECT IDENTIFIER ::= { linkBundlingConformance 1 } 1746 linkBundlingCompliances 1747 OBJECT IDENTIFIER ::= { linkBundlingConformance 2 } 1749 linkBundlingFullModuleCompliance MODULE-COMPLIANCE 1750 STATUS current 1751 DESCRIPTION 1752 "Compliance statement for agents that support the 1753 configuration and monitoring of link bundling MIB." 1754 MODULE -- this module 1756 -- The mandatory groups have to be implemented 1757 -- by all devices supporting link bundling. However, they may all 1758 -- be supported as read-only objects in the case where manual 1759 -- configuration is unsupported. 1761 MANDATORY-GROUPS { linkBundlingGroup, 1762 teLinkBandwidthGroup } 1764 GROUP teLinkOspfTeGroup 1765 DESCRIPTION 1766 "This group is mandatory for OSPF enabled devices." 1768 GROUP teLinkSrlgGroup 1769 DESCRIPTION 1770 "This group is mandatory for G-MPLS enabled devices." 1772 -- teLinkTable 1774 OBJECT teLinkRowStatus 1775 SYNTAX INTEGER { active(1), notInService(2), 1776 createAndGo(4), destroy(6) } 1778 MIN-ACCESS read-create 1779 DESCRIPTION 1780 "The notReady(3) state need not be supported." 1782 OBJECT teLinkStorageType 1783 SYNTAX INTEGER { other(1) } 1784 MIN-ACCESS read-create 1785 DESCRIPTION 1786 "Only other(1) needs to be supported." 1788 -- teLinkDescriptorTable 1790 OBJECT teLinkDescrRowStatus 1791 SYNTAX INTEGER { active(1), notInService(2), 1792 createAndGo(4), destroy(6) } 1793 MIN-ACCESS read-create 1794 DESCRIPTION 1795 "The notReady(3) state need not be supported." 1797 OBJECT teLinkDescrStorageType 1798 SYNTAX INTEGER { other(1) } 1799 MIN-ACCESS read-create 1800 DESCRIPTION 1801 "Only other(1) needs to be supported." 1803 -- teLinkOspfTeTable 1805 OBJECT teLinkOspfLinkId 1806 SYNTAX INTEGER { pointToPoint(1) } 1807 MIN-ACCESS read-create 1808 DESCRIPTION 1809 "A value of multiAccess(2) need not be supported." 1811 -- teLinkSrlgTable 1813 OBJECT srlgRowStatus 1814 SYNTAX INTEGER { active(1), notInService(2), 1815 createAndGo(4), destroy(6) } 1816 MIN-ACCESS read-create 1817 DESCRIPTION 1818 "The notReady(3) and createAndWait(5) states need 1819 not be supported." 1821 OBJECT srlgStorageType 1822 SYNTAX INTEGER { other(1) } 1823 MIN-ACCESS read-create 1824 DESCRIPTION 1825 "Only other(1) needs to be supported." 1827 -- teLinkBandwidthTable 1829 OBJECT teLinkBandwidthRowStatus 1830 SYNTAX INTEGER { active(1), notInService(2), 1831 createAndGo(4), destroy(6) } 1832 MIN-ACCESS read-create 1833 DESCRIPTION 1834 "The notReady(3) and createAndWait(5) states need 1835 not be supported." 1837 OBJECT teLinkBandwidthStorageType 1838 SYNTAX INTEGER { other(1) } 1839 MIN-ACCESS read-create 1840 DESCRIPTION 1841 "Only other(1) needs to be supported." 1843 -- dataBearingChannelTable 1845 OBJECT dataBearingChannelRowStatus 1846 SYNTAX INTEGER { active(1), notInService(2), 1847 createAndGo(4), destroy(6) } 1848 MIN-ACCESS read-create 1849 DESCRIPTION 1850 "The notReady(3) and createAndWait(5) states need 1851 not be supported." 1853 OBJECT dataBearingChannelStorageType 1854 SYNTAX INTEGER { other(1) } 1855 MIN-ACCESS read-create 1856 DESCRIPTION 1857 "Only other(1) needs to be supported." 1859 -- dataBearingChannelDescriptorTable 1861 OBJECT dataBearingChannelDescrRowStatus 1862 SYNTAX INTEGER { active(1), notInService(2), 1863 createAndGo(4), destroy(6) } 1864 MIN-ACCESS read-create 1865 DESCRIPTION 1866 "The notReady(3) state need not be supported." 1868 OBJECT dataBearingChannelDescrStorageType 1869 SYNTAX INTEGER { other(1) } 1870 MIN-ACCESS read-create 1871 DESCRIPTION 1872 "Only other(1) needs to be supported." 1874 -- dataBearingChannelBandwidthTable 1875 OBJECT dataBearingChannelBwRowStatus 1876 SYNTAX INTEGER { active(1), notInService(2), 1877 createAndGo(4), destroy(6) } 1878 MIN-ACCESS read-create 1879 DESCRIPTION 1880 "The notReady(3) and createAndWait(5) states need 1881 not be supported." 1883 OBJECT dataBearingChannelBwStorageType 1884 SYNTAX INTEGER { other(1) } 1885 MIN-ACCESS read-create 1886 DESCRIPTION 1887 "Only other(1) needs to be supported." 1889 ::= { linkBundlingCompliances 1 } 1891 linkBundlingMonitoringModuleCompliance MODULE-COMPLIANCE 1892 STATUS current 1893 DESCRIPTION 1894 "Compliance statement for agents that support the 1895 monitoring of link bundling MIB." 1896 MODULE -- this module 1898 -- The mandatory groups have to be implemented 1899 -- by all devices supporting link bundling. However, they may all 1900 -- be supported as read-only objects in the case where manual 1901 -- configuration is unsupported. 1903 MANDATORY-GROUPS { linkBundlingGroup, 1904 teLinkBandwidthGroup } 1906 GROUP teLinkOspfTeGroup 1907 DESCRIPTION 1908 "This group is mandatory for OSPF enabled devices." 1910 GROUP teLinkSrlgGroup 1911 DESCRIPTION 1912 "This group is mandatory for G-MPLS enabled devices." 1914 -- teLinkTable 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 teLinkDescrRowStatus 1947 SYNTAX INTEGER { active(1), notInService(2), 1948 createAndGo(4), destroy(6) } 1949 MIN-ACCESS read-only 1950 DESCRIPTION 1951 "The notReady(3) state need not be supported." 1953 OBJECT teLinkDescrStorageType 1954 SYNTAX INTEGER { other(1) } 1955 MIN-ACCESS read-only 1956 DESCRIPTION 1957 "Only other(1) needs to be supported." 1959 -- teLinkOspfTeTable 1961 OBJECT teLinkOspfLinkId 1962 SYNTAX INTEGER { pointToPoint(1) } 1963 MIN-ACCESS read-only 1964 DESCRIPTION 1965 "A value of multiAccess(2) need not be supported." 1967 -- teLinkSrlgTable 1969 OBJECT srlgRowStatus 1970 SYNTAX INTEGER { active(1), notInService(2), 1971 createAndGo(4), destroy(6) } 1972 MIN-ACCESS read-only 1973 DESCRIPTION 1974 "The notReady(3) and createAndWait(5) states need 1975 not be supported." 1977 OBJECT srlgStorageType 1978 SYNTAX INTEGER { other(1) } 1979 MIN-ACCESS read-only 1980 DESCRIPTION 1981 "Only other(1) needs to be supported." 1983 -- teLinkBandwidthTable 1985 OBJECT teLinkBandwidthRowStatus 1986 SYNTAX INTEGER { active(1), notInService(2), 1987 createAndGo(4), destroy(6) } 1988 MIN-ACCESS read-only 1989 DESCRIPTION 1990 "The notReady(3) and createAndWait(5) states need 1991 not be supported." 1993 OBJECT teLinkBandwidthStorageType 1994 SYNTAX INTEGER { other(1) } 1995 MIN-ACCESS read-only 1996 DESCRIPTION 1997 "Only other(1) needs to be supported." 1999 -- dataBearingChannelTable 2001 OBJECT dataBearingChannelPreferredProtection 2002 MIN-ACCESS read-only 2003 DESCRIPTION 2004 "Write access is not required." 2006 OBJECT dataBearingChannelRowStatus 2007 SYNTAX INTEGER { active(1), notInService(2), 2008 createAndGo(4), destroy(6) } 2009 MIN-ACCESS read-only 2010 DESCRIPTION 2011 "The notReady(3) and createAndWait(5) states need 2012 not be supported." 2014 OBJECT dataBearingChannelStorageType 2015 SYNTAX INTEGER { other(1) } 2016 MIN-ACCESS read-only 2017 DESCRIPTION 2018 "Only other(1) needs to be supported." 2020 -- dataBearingChannelDescriptorTable 2022 OBJECT dataBearingChannelEncodingType 2023 MIN-ACCESS read-only 2024 DESCRIPTION 2025 "Write access is not required." 2027 OBJECT dataBearingChannelDescrPriority 2028 MIN-ACCESS read-only 2029 DESCRIPTION 2030 "Write access is not required." 2032 OBJECT dataBearingChannelMinReservableBandwidth 2033 MIN-ACCESS read-only 2034 DESCRIPTION 2035 "Write access is not required." 2037 OBJECT dataBearingChannelDescrRowStatus 2038 SYNTAX INTEGER { active(1), notInService(2), 2039 createAndGo(4), destroy(6) } 2040 MIN-ACCESS read-only 2041 DESCRIPTION 2042 "The notReady(3) state need not be supported." 2044 OBJECT dataBearingChannelDescrStorageType 2045 SYNTAX INTEGER { other(1) } 2046 MIN-ACCESS read-only 2047 DESCRIPTION 2048 "Only other(1) needs to be supported." 2050 -- dataBearingChannelBandwidthTable 2052 OBJECT dataBearingChannelBwRowStatus 2053 SYNTAX INTEGER { active(1), notInService(2), 2054 createAndGo(4), destroy(6) } 2055 MIN-ACCESS read-only 2056 DESCRIPTION 2057 "The notReady(3) and createAndWait(5) states need 2058 not be supported." 2060 OBJECT dataBearingChannelBwStorageType 2061 SYNTAX INTEGER { other(1) } 2062 MIN-ACCESS read-only 2063 DESCRIPTION 2064 "Only other(1) needs to be supported." 2066 ::= { linkBundlingCompliances 2 } 2068 -- Units of conformance 2070 linkBundlingGroup OBJECT-GROUP 2071 OBJECTS { teLinkNumberingType, 2072 teLinkIpAddr, 2073 teLinkRemoteIpAddr, 2074 teLinkMetric, 2075 teLinkMuxCapability, 2076 teLinkProtectionType, 2077 teLinkWorkingPriority, 2078 teLinkResourceClass, 2079 teLinkIncomingIfId, 2080 teLinkOutgoingIfId, 2081 teLinkFlooding, 2082 teLinkRowStatus, 2083 teLinkStorageType, 2084 teLinkEncodingType, 2085 teLinkDescrPriority, 2086 teLinkMinReservableBandwidth, 2087 teLinkMaxReservableBandwidth, 2088 teLinkDescrRowStatus, 2089 teLinkDescrStorageType, 2090 dataBearingChannelLinkMuxCapability, 2091 dataBearingChannelPreferredProtection, 2092 dataBearingChannelCurrentProtection, 2093 dataBearingChannelRowStatus, 2094 dataBearingChannelStorageType, 2095 linkBundlingNotifEnable 2096 } 2098 STATUS current 2099 DESCRIPTION 2100 "Collection of objects needed for the monitoring of 2101 resources associated with TE links." 2102 ::= { linkBundlingGroups 1 } 2104 teLinkOspfTeGroup OBJECT-GROUP 2105 OBJECTS { teLinkOspfLinkType, 2106 teLinkOspfLinkId 2107 } 2109 STATUS current 2110 DESCRIPTION 2111 "Collection of objects needed for the OSPF traffic 2112 engineering parameters of TE links." 2113 ::= { linkBundlingGroups 2 } 2115 teLinkSrlgGroup OBJECT-GROUP 2116 OBJECTS { srlgRowStatus, 2117 srlgStorageType 2118 } 2120 STATUS current 2121 DESCRIPTION 2122 "Collection of objects needed for the monitoring of 2123 SRLG resources associated with TE links." 2124 ::= { linkBundlingGroups 3 } 2126 teLinkBandwidthGroup OBJECT-GROUP 2127 OBJECTS { teLinkUnreservedBandwidth, 2128 teLinkMaximumLspBandwidth, 2129 teLinkBandwidthRowStatus, 2130 teLinkBandwidthStorageType 2131 } 2133 STATUS current 2134 DESCRIPTION 2135 "Collection of objects needed for the monitoring of 2136 the priority-based bandwidth resources associated with 2137 TE links and data-bearing channels." 2138 ::= { linkBundlingGroups 4 } 2140 dataBearingChannelBandwidthGroup OBJECT-GROUP 2141 OBJECTS { dataBearingChannelEncodingType, 2142 dataBearingChannelDescrPriority, 2143 dataBearingChannelMinReservableBandwidth, 2144 dataBearingChannelMaxReservableBandwidth, 2145 dataBearingChannelDescrRowStatus, 2146 dataBearingChannelDescrStorageType, 2147 dataBearingChannelUnreservedBandwidth, 2148 dataBearingChannelMaximumLspBandwidth, 2149 dataBearingChannelBwRowStatus, 2150 dataBearingChannelBwStorageType 2151 } 2153 STATUS current 2154 DESCRIPTION 2155 "Collection of objects needed for the monitoring of 2156 bandwidth parameters associated with data-bearing channels." 2157 ::= { linkBundlingGroups 5 } 2159 linkBundlingNotificationGroup NOTIFICATION-GROUP 2160 NOTIFICATIONS { linkBundleMismatch } 2161 STATUS current 2162 DESCRIPTION 2163 "Set of notifications implemented in this module. 2165 None is mandatory." 2166 ::= { linkBundlingGroups 6 } 2168 -- End of LINK-BUNDLING-MIB 2169 END 2171 11. Security Considerations 2173 It is clear that this MIB is potentially useful for monitoring of 2174 link bundling enabled devices. This MIB can also be used for confi- 2175 guration of certain objects, and anything that can be configured can 2176 be incorrectly configured, with potentially disastrous results. 2178 At this writing, no security holes have been identified beyond those 2179 that SNMP Security [RFC2571] is itself intended to address. These 2180 relate to primarily controlled access to sensitive information and 2181 the ability to configure a device - or which might result from opera- 2182 tor error, which is beyond the scope of any security architecture. 2184 There are a number of management objects defined in this MIB which 2185 have a MAX-ACCESS clause of read-write and/or read-create. Such 2186 objects may be considered sensitive or vulnerable in some network 2187 environments. The support for SET operations in a non-secure environ- 2188 ment without proper protection can have a negative effect on network 2189 operations. The use of SNMP Version 3 is recommended over prior ver- 2190 sions, for configuration control, as its security model is improved. 2192 SNMPv1 or SNMPv2 are by themselves not a secure environment. Even if 2193 the network itself is secure (for example by using IPSec [IPSEC]), 2194 there is no control as to who on the secure network is allowed to 2195 access and GET/SET (read/change/create/delete) the objects in this 2196 MIB. It is recommended that the implementers consider the security 2197 features as provided by the SNMPv3 framework. Specifically, the use 2198 of the User-based Security Model [RFC2574] and the View-based Access 2199 Control [RFC2575] is recommended. It is then a customer/user respon- 2200 sibility to ensure that the SNMP entity giving access to an instance 2201 of this MIB is properly configured to give access to the objects only 2202 to those principals (users) that have legitimate rights to indeed GET 2203 or SET (change/create/delete) them. 2205 There are a number of managed objects in this MIB that may contain 2206 information that may be sensitive from a business perspective, in 2207 that they can be used to derive the network topology, e.g. list of 2208 nodes and their IP address (teLinkTable), list of data-bearing chan- 2209 nels (dataBearingChannelTable) in addition to usage of network 2210 resources (teLinkBandwidthTable and 2211 dataBearingChannelBandwidthTable). Allowing uncontrolled access to 2212 these objects could result in malicious and unwanted disruptions of 2213 network traffic, incorrect network configuration or theft of competi- 2214 tive business information. There are no objects that are particu- 2215 larly sensitive in their own right, such as passwords or monetary 2216 amounts. 2218 12. Acknowledgments 2220 The general structure of this draft has been modeled around draft- 2221 ietf-mpls-lsr-mib-06.txt. The authors would like to acknowlegde the 2222 contribution of Dmitry Ryumkin. 2224 13. References 2226 [BUNDLING] Kompella, K., Rekhter, Y., and Berger, L., 2227 "Link Bundling in MPLS Traffic Engineering", 2228 Internet Draft , 2229 November 2001. 2231 [LMP] Lang, J., Mitra, K., Drake, J., Kompella, K., 2232 Rekhter, Y., Berger, L., Rajagopalan, B., 2233 Basak, D., Sandick, H., Zinin, A., and 2234 Banarjee, A., "Link Management Protocol", 2235 Internet Draft , 2236 November 2001. 2238 [GMPLS] Ashwood-Smith, P., Banarjee, A., Berger, L., 2239 Bernstein, G., Drake, J., Fan, Y., Kompella, K., 2240 Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y., 2241 Saha, D., Sharma, V., Swallow, G., and Tang, Z., 2242 "Generalized MPLS Signaling Functional Description", 2243 Internet Draft 2244 , 2245 November 2001. 2247 [GMPLS-ARCH] Mannie, E., Ashwood-Smith, P., Awduche, D., 2248 Banarjee, A., Basak, D., Berger, L., Bernstein, G., 2249 Dharanikota, S., Drake, J., Fan, Y., Fedyk, D., 2250 Grammel, G., Guo, D., Kompella, K., Kullberg, A., 2251 Lang, J., Liaw, F., Nadeau, T., Ong, L., 2252 Papadimitriou, D., Pendarakis, D., Rajagopalan, B., 2253 Rekhter, Y., Saha, D., Sandick, H., Sharma, V., 2254 Swallow, G., Tang, Z., Yates, J., Young, G., Yu, J., 2255 Zinin, A., "Generalized Multi-Protocol Label Switching 2256 (GMPLS) Architecture", Internet Draft 2257 , 2258 November 2001. 2260 [OSPF] Katz, D., Yeung, D. "Traffic Engineering Extensions to 2261 OSPF", Internet Draft 2262 , October 2001. 2264 [GMPLS-OSPF] Kompella, K., Rekhter, Y., Banerjee, A. et al, "OSPF 2265 Extensions in Support of Generalized MPLS", Internet 2266 Draft 2267 , 2268 February 2002. 2270 [LSP-HIER] Kompella, K., Rekhter, Y., LSP Hierarchy with MPLS TE, 2271 Internet Draft , 2272 May 2001. 2274 [ZININ] Zinin, A., SHand, M., "Flooding optimizations in link- 2275 state routing protocols", Internet Draft, 2276 , March 2001. 2278 [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", 2279 RFC 1700, October 1994. See also: 2280 http://www.isi.edu/in-notes/iana/assignments/smi- 2281 numbers 2283 [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS 2284 FAMILY NUMBERS, (http://www.isi.edu/in- 2285 notes/iana/assignements/address-family-numbers), 2286 for MIB see: 2287 ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib 2289 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 2290 Architecture for Describing SNMP Management 2291 Frameworks", RFC 2571, April 1999. 2293 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 2294 Identification of Management Information for TCP/IP- 2295 based Internets", STD 16, RFC 1155, May 1990. 2297 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 2298 STD 16, RFC 1212, March 1991. 2300 [RFC1215] M. Rose, "A Convention for Defining Traps for use with 2301 the SNMP", RFC 1215, March 1991. 2303 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2304 J., Rose, M., and S. Waldbusser, "Structure of 2305 Management Information Version 2 (SMIv2)", STD 58, 2306 RFC 2578, April 1999. 2308 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2309 J., Rose, M., and S. Waldbusser, "Textual Conventions 2310 for SMIv2", STD 58, RFC 2579, April 1999. 2312 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2313 J., Rose, M., and S. Waldbusser, "Conformance 2314 Statements for SMIv2", STD 58, RFC 2580, April 1999. 2316 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 2317 "Simple Network Management Protocol", STD 15, RFC 1157, 2318 May 1990. 2320 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2321 "Introduction to Community-based SNMPv2", RFC 1901, 2322 January 1996. 2324 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2325 "Transport Mappings for Version 2 of the Simple Network 2326 Management Protocol (SNMPv2)", RFC 1906, January 1996. 2328 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2329 "Message Processing and Dispatching for the Simple 2330 Network Management Protocol (SNMP)", RFC 2572, April 2331 1999. 2333 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 2334 Model (USM) for version 3 of the Simple Network 2335 Management Protocol (SNMPv3)", RFC 2574, April 1999. 2337 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2338 "Protocol Operations for Version 2 of the Simple 2339 Network Management Protocol (SNMPv2)", RFC 1905, 2340 January 1996. 2342 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2343 Applications", RFC 2573, April 1999. 2345 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 2346 Access Control Model (VACM) for the Simple Network 2347 Management Protocol (SNMP)", RFC 2575, April 1999. 2349 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 2350 "Introduction to Version 3 of the Internet-standard 2351 Network Management Framework", RFC 2570, April 1999. 2353 [IPSEC] Kent, S., and Atkinson, R., "Security Architecture 2354 for the Internet Protocol", RFC 2401, November 2355 1998. 2357 [IFMIB] McCloghrie, K., and Kastenholtz, F., "The Interfaces 2358 Group MIB", RFC 2863, June 2000. 2360 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 2361 Requirement Levels", BCP 14, RFC 2119, March 1997. 2363 14. Authors' Addresses 2365 Martin Dubuc Thomas D. Nadeau 2366 Meriton Networks Cisco Systems, Inc. 2367 3026 Solandt Road 300 Apollo Drive 2368 Kanata, ON, CANADA K2K 2A5 Chelmsford, MA 01824 2369 Phone: +1-613-270-9279 x253 Phone: +1-978-244-3051 2370 Email: martin.dubuc@meriton.com Email: tnadeau@cisco.com 2372 Sudheer Dharanikota Jonathan P. Lang 2373 Nayna Networks, Inc. Calient Networks, Inc. 2374 157 Topaz Street 25 Castilian Drive 2375 Milipitas, CA 95035 Goleta, CA 93117 2376 Phone: +1-408-956-8000 x357 Email: jplang@calient.net 2377 Email: sudheer@nayna.com 2379 15. Full Copyright Statement 2381 Copyright (C) The Internet Society (2001). All Rights Reserved. 2383 This document and translations of it may be copied and furnished to 2384 others, and derivative works that comment on or otherwise explain it 2385 or assist in its implementation may be prepared, copied, published 2386 and distributed, in whole or in part, without restriction of any 2387 kind, provided that the above copyright notice and this paragraph are 2388 included on all such copies and derivative works. However, this docu- 2389 ment itself may not be modified in any way, such as by removing the 2390 copyright notice or references to the Internet Society or other 2391 Internet organizations, except as needed for the purpose of develop- 2392 ing Internet standards in which case the procedures for copyrights 2393 defined in the Internet Standards process must be followed, or as 2394 required to translate it into languages other than English. 2396 The limited permissions granted above are perpetual and will not be 2397 revoked by the Internet Society or its successors or assigns. This 2398 document and the information contained herein is provided on an "AS 2399 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 2400 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 2401 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL 2402 NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY 2403 OR FITNESS FOR A PARTICULAR PURPOSE.