idnits 2.17.1 draft-dubuc-mpls-bundle-mib-02.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 2 instances of too long lines in the document, the longest one being 1 character 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 has text resembling 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.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'SNMPv1MIBDef' is mentioned on line 128, but not defined == Unused Reference: 'LMP' is defined on line 2050, but no explicit reference was found in the text == Unused Reference: 'GMPLS' is defined on line 2057, but no explicit reference was found in the text == Unused Reference: 'OSPF' is defined on line 2078, but no explicit reference was found in the text == Unused Reference: 'LSP-HIER' is defined on line 2088, but no explicit reference was found in the text == Unused Reference: 'ZININ' is defined on line 2092, but no explicit reference was found in the text == Unused Reference: 'Assigned' is defined on line 2096, but no explicit reference was found in the text == Unused Reference: 'IANAFamily' is defined on line 2101, but no explicit reference was found in the text == Unused Reference: 'RFC2572' is defined on line 2121, but no explicit reference was found in the text == Unused Reference: 'RFC2574' is defined on line 2126, but no explicit reference was found in the text == Unused Reference: 'RFC1905' is defined on line 2131, but no explicit reference was found in the text == Unused Reference: 'RFC2573' is defined on line 2136, but no explicit reference was found in the text == Unused Reference: 'RFC2575' is defined on line 2139, but no explicit reference was found in the text == Unused Reference: 'RFC2570' is defined on line 2144, 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 (ref. 'SNMPArch') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. 'SNMPv1Traps') ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. 'SNMPv1') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. 'SNMPv2c') ** Obsolete normative reference: RFC 1906 (ref. 'SNMPv2TM') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2272 (ref. 'SNMPv3MP') (Obsoleted by RFC 2572) -- Duplicate reference: RFC2574, mentioned in 'SNMPv3USM', was also mentioned in 'RFC2574'. ** Obsolete normative reference: RFC 2574 (ref. 'SNMPv3USM') (Obsoleted by RFC 3414) -- Duplicate reference: RFC1905, mentioned in 'SNMPv2PO', was also mentioned in 'RFC1905'. ** Obsolete normative reference: RFC 1905 (ref. 'SNMPv2PO') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2273 (ref. 'SNMPv3App') (Obsoleted by RFC 2573) -- Duplicate reference: RFC2575, mentioned in 'SNMPv3VACM', was also mentioned in 'RFC2575'. ** Obsolete normative reference: RFC 2575 (ref. 'SNMPv3VACM') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2401 (ref. 'IPSEC') (Obsoleted by RFC 4301) Summary: 26 errors (**), 0 flaws (~~), 17 warnings (==), 14 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Martin Dubuc 3 Internet Draft edgeflow, Inc. 4 Expires: November 2001 5 Sudheer Dharanikota 6 Nayna Networks, Inc. 8 Thomas D. Nadeau 9 Cisco Systems, Inc. 11 Jonathan P. Lang 12 Calient Networks, Inc. 14 Link Bundling Management Information Base Using SMIv2 16 draft-dubuc-mpls-bundle-mib-02.txt 18 Status of this Memo 20 This document is an Internet-Draft and is in full conformance with 21 all provisions of Section 10 of RFC 2026. 23 Internet-Drafts are working documents of the Internet Engineering 24 Task Force (IETF), its areas, and its working groups. Note that other 25 groups may also distribute working documents as Internet- Drafts. 27 Internet-Drafts are draft documents valid for a maximum of six months 28 and may be updated, replaced, or obsoleted by other documents at any 29 time. It is inappropriate to use Internet- Drafts as reference 30 material or to cite them other than as "work in progress." 32 The list of current Internet-Drafts can be accessed at 33 http://www.ietf.org/ietf/1id-abstracts.txt. 35 The list of Internet-Draft Shadow Directories can be accessed at 36 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 4.1. Object Definitions ........................................... 4 45 5. Feature Checklist ............................................ 4 46 6. Outline ...................................................... 5 47 6.1. Summary of Link Bundling MIB ................................. 5 48 7. Brief Description of MIB Objects ............................. 6 49 7.1. teLinkTable .................................................. 6 50 7.2. teLinkDescriptorTable ........................................ 6 51 7.3. teLinkOspfTeTable ............................................ 6 52 7.4. teLinkSrlgTable .............................................. 7 53 7.5. teLinkBandwidthTable ......................................... 7 54 7.6. dataBearingChannelTable ...................................... 7 55 7.7. dataBearingChannelDescriptorTable ............................ 7 56 7.8. dataBearingChannelBandwidthTable ............................. 7 57 8. Example of Bundled Link Setup ................................ 7 58 9. Application of the Interface Group to TE Links ............... 11 59 9.1 Support of the TE Link Layer by ifTable ...................... 12 60 9.2 Using ifStackTable ........................................... 13 61 10. Link Bundling MIB Definitions ............................... 15 62 11. Security Considerations ...................................... 43 63 12. Acknowledgments .............................................. 44 64 13. References ................................................... 44 65 14. Authors' Addresses ........................................... 48 66 15. Full Copyright Statement ..................................... 48 68 1. Abstract 70 This memo defines an experimental portion of the Management Informa- 71 tion Base (MIB) for use with network management protocols in the 72 Internet community. In particular, it describes managed objects for 73 modeling link bundling as described in [BUNDLING]. 75 2. Introduction 77 This memo defines an experimental portion of the Management Informa- 78 tion Base (MIB) for use with network management protocols in the 79 Internet community. In particular, it describes managed objects for 80 modeling link bundling as described in [BUNDLING]. 82 Comments should be made directly to the MPLS mailing list at 83 mpls@uu.net. 85 This memo does not, in its draft form, specify a standard for the 86 Internet community. 88 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 89 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 90 document are to be interpreted as described in RFC 2119, reference 92 [BCP14]. 94 3. Terminology 96 This document uses terminology from the documents describing link 97 bundling [BUNDLING] and G-MPLS [GMPLS-ARCH]. 99 The link bundling feature is designed to aggregate one or more simi- 100 lar entities between a node pair into a bundled link [BUNDLING]. In 101 the document, those entities are referred to as TE links. A TE link 102 is a subinterface capable of carrying MPLS traffic engineered 103 traffic. A TE Link may be comprised of only one underlying data- 104 bearing channels. In cases where more than one data-bearing channel 105 is to be combined, multiple data-bearing links should be created with 106 differing priorities to indicate hot-standby or parallel utilization. 108 A bundled link is just another kind of Traffic Engineering (TE) link 109 (see [GMPLS-OSPF]). A link bundle is a subinterface which bonds the 110 traffic of a group of one or more TE links. There should be more than 111 one TE Link in a link bundle, but this is not a requirement. Furth- 112 ermore, if there are more than one TE link in a link bundle at some 113 time, and at some point later, all but one of the links are deleted, 114 the agent may choose to either delete the link bundle, or it may 115 choose to leave it intact. Traffic counters on a link bundle are 116 cumulative for all subinterfaces which it binds together. 118 4. The SNMP Management Framework 120 The SNMP Management Framework presently consists of five major com- 121 ponents: 123 - An overall architecture, described in RFC 2571 [SNMPArch]. 125 - Mechanisms for describing and naming objects and events for the 126 purpose of management. The first version of this Structure of 127 Management Information (SMI) is called SMIv1 and described in 128 RFC 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215 129 [SNMPv1Traps]. The second version, called SMIv2, is described 130 in RFC 2578 [SMIv2], RFC 2579 [SNMPv2TC] and RFC 2580 131 [SNMPv2Conf]. 133 - Message protocols for transferring management information. The 134 first version of the SNMP message protocol is called SNMPv1 135 and described in RFC 1157 [SNMPv1]. A second version of the 136 SNMP message protocol, which is not an Internet standards 137 track protocol, is called SNMPv2c and described in RFC 1901 138 [SNMPv2c] and RFC 1906 [SNMPv2TM]. The third version of the 139 message protocol is called SNMPv3 and described in RFC 1906 140 [SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC 2574 [SNMPv3USM]. 142 - Protocol operations for accessing management information. The 143 first set of protocol operations and associated PDU formats is 144 described in RFC 1157 [SNMPv1]. A second set of protocol 145 operations and associated PDU formats is described in RFC 1905 146 [SNMPv2PO]. 148 - A set of fundamental applications described in RFC 2273 149 [SNMPv3App] and the view-based access control mechanism 150 described in RFC 2575 [SNMPv3VACM]. 152 Managed objects are accessed via a virtual information store, termed 153 the Management Information Base or MIB. Objects in the MIB are 154 defined using the mechanisms defined in the SMI. This memo specifies 155 a MIB module that is compliant to the SMIv2. A MIB conforming to the 156 SMIv1 can be produced through the appropriate translations. The 157 resulting translated MIB must be semantically equivalent, except 158 where objects or events are omitted because no translation is possi- 159 ble (use of Counter64). Some machine-readable information in SMIv2 160 will be converted into textual descriptions in SMIv1 during the 161 translation process. However, this loss of machine-readable informa- 162 tion is not considered to change the semantics of the MIB. 164 4.1. Object Definitions 166 Managed objects are accessed via a virtual information store, termed 167 the Management Information Base or MIB. Objects in the MIB are 168 defined using the subset of Abstract Syntax Notation One (ASN.1) 169 defined in the SMI. In particular, each object type is named by an 170 OBJECT IDENTIFIER, an administratively assigned name. The object 171 type together with an object instance serves to uniquely identify a 172 specific instantiation of the object. For human convenience, we often 173 use a textual string, termed the descriptor, to also refer to the 174 object type. 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 9 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(1), 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(1), 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(1), 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) 353 } 355 The OSPF traffic engineering parameters are configured for the 356 TE links. 358 In teLinkOspfTeTable: 359 { 360 ifIndex = 20, 361 teLinkOspfLinkId = 'c0010101'H, -- 192.1.1.1 362 teLinkRowStatus = createAndGo(4) 363 } 365 In teLinkOspfTeTable: 366 { 367 ifIndex = 21, 368 teLinkOspfLinkId = 'c0010101'H, -- 192.1.1.1 369 teLinkRowStatus = createAndGo(4) 370 } 372 We assign SRLGs to the TE links. 374 In the teLinkSrlgTable: 375 { 376 ifIndex = 20, 377 srlg = 10, 378 srlgRowStatus = createAndGo(4) 379 } 381 In the teLinkSrlgTable: 382 { 383 ifIndex = 21, 384 srlg = 50, 385 srlgRowStatus = createAndGo(4) 386 } 388 The bundled link inherits the OSPF and SRLG properties from the 389 associated TE links. 391 Next, for each TE link, two data-bearing channels are created. 392 An ifEntry with the same ifIndex needs to be created beforehand. 394 In dataBearingChannelTable: 395 { 396 ifIndex = 40, 397 dataBearingChannelPreferredProtection = primary(1), 398 dataBearingChannelRowStatus = createAndGo(4) 399 } 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 } 450 In this example, once a data-bearing channel is added to the 451 dataBearingChannelTable, the associated link descriptors are 452 implicitly added to the dataBearingChannelDescriptorTable. 454 TE link link descriptors are derived from their data-bearing channel 455 link descriptors. 457 Note that the bandwidth attributes in teLinkDescriptorTable, 458 dataBearingChannelDescriptorTable, teLinkBandwidthTable 459 and dataBearingChannelBandwidthTable are maintained by the 460 device according to LSP creation/deletion at different priorities. 461 The values in the teLinkBandwidthTable are an aggregation 462 of the values for the data-bearing channels of the TE links and 463 the TE links of the bundled link. 465 9. Application of the Interface Group to TE Links 467 The Interfaces Group of MIB II defines generic managed objects for 468 managing interfaces. This memo contains the media-specific 469 extensions to the Interfaces Group for managing TE LInk 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(TBD) + 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 TBD. 505 This number will be assigned by the IANA. 507 ifSpeed The total bandwidth in bits per second for use by 508 the TE Link layer. 510 ifPhysAddress Unused. 512 ifAdminStatus This variable indicates the administrator's intent 513 as to whether TE Link should be enabled, disabled, or 514 running in some diagnostic testing mode on this 515 interface. Also see [IFMIB]. 517 ifOperStatus This value reflects the actual or operational 518 status of TE Link on this interface. 520 ifLastChange See [IFMIB]. 522 ifInOctets The number of received octets over the interface, 523 i.e., the number of received octets in all data-bearing 524 channels associated with the interface. 526 ifOutOctets The number of transmitted octets over the 527 interface, i.e., the number of octets transmitted 528 over all data-bearing channels associated with the 529 interface. 531 ifInErrors The number of packets dropped due to 532 uncorrectable errors. 534 ifInUnknownProtos 535 The number of received packets discarded during 536 packet header validation. 538 ifOutErrors See [IFMIB]. 540 ifName Textual name (unique on this system) of the 541 interface or an octet string of zero length. 543 ifLinkUpDownTrapEnable 544 Default is disabled (2). 546 ifConnectorPresent 547 Set to false (2). 549 ifHighSpeed See [IFMIB]. 551 ifHCInOctets The 64-bit version of ifInOctets; supported if 552 required by the compliance statements in [IFMIB]. 554 ifHCOutOctets The 64-bit version of ifOutOctets; supported if 555 required by the compliance statements in [IFMIB]. 557 ifAlias The non-volatile 'alias' name for the interface as 558 specified by a network manager. 560 ifCounterDiscontinuityTime 561 See [IFMIB]. 563 Support for ifInOctets, ifOutOctets, ifInErrors, ifInUnknownProtos, 564 ifOutErrors, ifHCInOctets and ifHCOutOctets objects is not required 565 if encoding type is clear. For other encoding types, traffic 566 counters on a TE link are cumulative for all subinterfaces which it 567 binds together. 569 9.2. Using ifStackTable 571 This section describes by example how to use ifStackTable to 572 represent the relationship of TE links with underlying TE-enabled 573 interfaces. Implementors of the stack table for TE link interfaces 574 should look at the appropriate RFC for the service being stacked 575 on TE links. Examples given below are for illustration purposes 576 only. 578 Example: MPLS is being carried on 2 bundled TE links. 579 Each bundled TE link runs over a 1:1 optical 580 transport interface. 582 +---------------------------------+ 583 | mpls | 584 +---------------------------------+ 585 | 586 +---------------------------------+ 587 | teLink (Link Bundle) | 588 +---------------------------------+ 589 | | 590 +---------------+ +---------------+ 591 | teLink | | teLink | 592 +---------------+ +---------------+ 593 | | | | 594 +------+ +------+ +------+ +------+ 595 |oTrans| |oTrans| |oTrans| |oTrans| 596 +------+ +------+ +------+ +------+ 598 The assignment of the index values could for example be: 600 ifIndex Description 601 1 mpls (type 166) 602 2 teLink (type TBD) 603 3 teLink (type TBD) 604 4 teLink (type TBD) 605 5 opticalTransport (type 196) 606 6 opticalTransport (type 196) 607 7 opticalTransport (type 196) 608 8 opticalTransport (type 196) 610 The ifStackTable is then used to show the relationships between the 611 various interfaces. 613 ifStackTable Entries 615 HigherLayer LowerLayer 616 0 1 617 1 2 618 2 3 619 2 4 620 3 5 621 3 6 622 4 7 623 4 8 624 5 0 625 6 0 626 7 0 627 8 0 629 In the case where MPLS is using a single TE link, then 630 the upper TE link layer (link bundle) is not required. 632 +---------------+ 633 | mpls | 634 +---------------+ 635 | 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 "200105221200Z" -- 22 May 2001 12:00:00 EST 692 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 693 CONTACT-INFO 694 " Martin Dubuc 695 Postal: edgeflow, Inc. 696 329 March Rd. 697 Kanata, ON, CANADA K2K 2E1 698 Tel: +1-613-270-9279 x253 699 Email: martin.dubuc@edgeflow.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 February 2001." 729 -- Revision history. 730 REVISION 731 "200105221200Z" -- 22 May 2001 12:00:00 EST 732 DESCRIPTION 733 "Replaced InetAddressIPv4 and InetAddressIPv6 with InetAddress 734 and InetAddrType. Changed description of entries which extend 735 ifEntry. Made various minor corrections." 736 REVISION 737 "200105141200Z" -- 14 May 2001 12:00:00 EST 738 DESCRIPTION 739 "Replaced componentLinkTable by dataBearingChannelTable. 740 Replaced linkBundlingTable by teLinkTable. Converted TE links 741 into interfaces." 742 REVISION 743 "200102231200Z" -- 23 February 2001 12:00:00 EST 744 DESCRIPTION 745 "Initial draft version." 746 ::= { experimental 114 } 748 -- Textual Conventions 750 -- Top level components of this MIB 752 -- Traps 753 linkBundlingNotifications OBJECT IDENTIFIER ::= { linkBundlingMIB 0 } 754 -- Tables, Scalars 755 linkBundlingObjects OBJECT IDENTIFIER ::= { linkBundlingMIB 1 } 756 -- Conformance 757 linkBundlingConformance OBJECT IDENTIFIER ::= { linkBundlingMIB 2 } 759 -- TE Link Table 761 teLinkTable OBJECT-TYPE 762 SYNTAX SEQUENCE OF TeLinkEntry 763 MAX-ACCESS not-accessible 764 STATUS current 765 DESCRIPTION 766 "This table specifies the grouping of data-bearing channels into 767 TE links and grouping of TE links into bundled links." 768 ::= { linkBundlingObjects 1 } 770 teLinkEntry OBJECT-TYPE 771 SYNTAX TeLinkEntry 772 MAX-ACCESS not-accessible 773 STATUS current 774 DESCRIPTION 775 "An entry in this table exists for each ifEntry with an 776 ifType of teLink(TBD), i.e. for every TE link. An ifEntry 777 in the ifTable must exist before a teLinkEntry is created with 778 the corresponding ifIndex. If a TE link entry in the ifTable is 779 destroyed, then so is the corresponding entry in the 780 teLinkTable. The administrative and operational status values 781 are controlled from the ifEntry." 782 INDEX { ifIndex } 783 ::= { teLinkTable 1 } 785 TeLinkEntry ::= SEQUENCE { 786 teLinkNumberingType Unsigned32, 787 teLinkIpAddrType InetAddressType, 788 teLinkIpAddr InetAddress, 789 teLinkRemoteId InterfaceIndexOrZero, 790 teLinkRemoteIpAddr InetAddress, 791 teLinkMetric Unsigned32, 792 teLinkMuxCapability Unsigned32, 793 teLinkProtectionType Unsigned32, 794 teLinkWorkingPriority Unsigned32, 795 teLinkResourceClass Unsigned32, 796 teLinkIncomingIfId InterfaceIndexOrZero, 797 teLinkOutgoingIfId InterfaceIndexOrZero, 798 teLinkFlooding InterfaceIndexOrZero, 799 teLinkRowStatus RowStatus, 800 teLinkStorageType StorageType 801 } 803 teLinkNumberingType OBJECT-TYPE 804 SYNTAX INTEGER { 805 numbered(0), 806 unnumbered(1) 807 } 808 MAX-ACCESS read-create 809 STATUS current 810 DESCRIPTION 811 "The TE link identifier type (numbered or unnumbered)." 812 ::= { teLinkEntry 1 } 814 teLinkIpAddrType OBJECT-TYPE 815 SYNTAX InetAddressType 816 MAX-ACCESS read-create 817 STATUS current 818 DESCRIPTION 819 "Indicates whether the TE link address is IPv4 or 820 IPv6 (numbered link)." 822 ::= { teLinkEntry 2 } 824 teLinkIpAddr OBJECT-TYPE 825 SYNTAX InetAddress 826 MAX-ACCESS read-create 827 STATUS current 828 DESCRIPTION 829 "The IP address associated with the TE link (numbered links)." 830 ::= { teLinkEntry 3 } 832 teLinkRemoteId OBJECT-TYPE 833 SYNTAX InterfaceIndexOrZero 834 MAX-ACCESS read-create 835 STATUS current 836 DESCRIPTION 837 "This is the remote interface identifier for the TE link." 838 REFERENCE 839 "RFC 2863 - The Interfaces Group MIB, 840 McCloghrie, K., and F. Kastenholtz, June 2000" 841 ::= { teLinkEntry 4 } 843 teLinkRemoteIpAddr OBJECT-TYPE 844 SYNTAX InetAddress 845 MAX-ACCESS read-create 846 STATUS current 847 DESCRIPTION 848 "The remote IP address associated with the TE link (numbered 849 links)." 850 ::= { teLinkEntry 5 } 852 teLinkMetric OBJECT-TYPE 853 SYNTAX Unsigned32 854 MAX-ACCESS read-create 855 STATUS current 856 DESCRIPTION 857 "The traffic engineering metric for the TE link is 858 derived from its data-bearing channels. All data-bearing 859 channels within the TE link must have the same traffic 860 engineering metric." 861 REFERENCE 862 "draft-kompella-mpls-bundle-05.txt - Link Bundling in MPLS 863 Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, 864 February 2001." 865 ::= { teLinkEntry 6 } 867 teLinkMuxCapability OBJECT-TYPE 868 SYNTAX INTEGER { 869 packetSwitch1(1), 870 packetSwitch2(2), 871 packetSwitch3(3), 872 packetSwitch4(4), 873 layer2Switch(51), 874 tdm(100), 875 lambdaSwitch(150), 876 fiberSwitch(200) 877 } 878 MAX-ACCESS read-only 879 STATUS current 880 DESCRIPTION 881 "This attribute specifies link multiplex capability of the 882 TE link, which is derived from its data-bearing channels. All 883 data-bearing channels within the same TE link must have the 884 same link multiplex capability." 885 REFERENCE 886 "draft-ietf-mpls-lsp-hierarchy-01.txt - LSP Hierarchy with 887 MPLS TE, K. Kompella, Y. Rekhter, September 2000." 888 ::= { teLinkEntry 7 } 890 teLinkProtectionType OBJECT-TYPE 891 SYNTAX INTEGER { 892 unprotected(0), 893 shared(1), 894 dedicated1For1(2), 895 dedicated1Plus1(3), 896 enhanced(4) 897 } 898 MAX-ACCESS read-create 899 STATUS current 900 DESCRIPTION 901 "This attribute specifies link protection type of the 902 TE link." 903 REFERENCE 904 "draft-kompella-ospf-gmpls-extensions-01.txt - OSPF Extensions 905 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 906 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 907 D. Saha, V. Sharma, February 2001." 908 ::= { teLinkEntry 8 } 910 teLinkWorkingPriority OBJECT-TYPE 911 SYNTAX Unsigned32 (0..7) 912 MAX-ACCESS read-create 913 STATUS current 914 DESCRIPTION 915 "This object represents a priority value such that a new 916 connection with a higher priority, i.e. numerically lower than 917 this value, is guaranteed to be setup on a primary channel and 918 not on a secondary channel." 919 REFERENCE 920 "draft-kompella-ospf-gmpls-extensions-01.txt - OSPF Extensions 921 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 922 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 923 D. Saha, V. Sharma, February 2001." 924 ::= { teLinkEntry 9 } 926 teLinkResourceClass OBJECT-TYPE 927 SYNTAX Unsigned32 928 MAX-ACCESS read-create 929 STATUS current 930 DESCRIPTION 931 "This attribute specifies the TE link resource class. 932 The resource class is a 32 bit bitfield. The resource class for 933 a link bundle is derived from the resource class of its 934 TE links. All TE links within a link bundle must have the 935 same resource class." 936 ::= { teLinkEntry 10 } 938 teLinkIncomingIfId OBJECT-TYPE 939 SYNTAX InterfaceIndexOrZero 940 MAX-ACCESS read-only 941 STATUS current 942 DESCRIPTION 943 "The incoming interface is set to the outgoing interface 944 identifier chosen by the neighboring LSR for the reverse 945 link corresponding to this TE link." 946 REFERENCE 947 "draft-kompella-mpls-bundle-05.txt - Link Bundling in MPLS 948 Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, 949 February 2001." 950 ::= { teLinkEntry 11 } 952 teLinkOutgoingIfId OBJECT-TYPE 953 SYNTAX InterfaceIndexOrZero 954 MAX-ACCESS read-only 955 STATUS current 956 DESCRIPTION 957 "If the link is unnumbered, the outgoing interface identifier is 958 set to the outgoing interface identifier chosen for the TE link 959 by the advertising LSR." 960 REFERENCE 961 "draft-kompella-mpls-bundle-05.txt - Link Bundling in MPLS 962 Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, 963 February 2001." 964 ::= { teLinkEntry 12 } 966 teLinkFlooding OBJECT-TYPE 967 SYNTAX InterfaceIndexOrZero 968 MAX-ACCESS read-create 969 STATUS current 970 DESCRIPTION 971 "This object only has significance for link bundles which 972 encoding type is not clear. For these link bundles, this object 973 identifies the TE link on which to restrict flooding. If the 974 value is zero, then flooding must be done on all TE links 975 within the link bundle." 976 REFERENCE 977 "draft-ietf-ospf-isis-flood-opt-00.txt - Flooding optimization 978 in link-state routing protocols, A. Zinin, M. Shand, 979 October 2000." 980 DEFVAL { 0 } 981 ::= { teLinkEntry 13 } 983 teLinkRowStatus OBJECT-TYPE 984 SYNTAX RowStatus 985 MAX-ACCESS read-create 986 STATUS current 987 DESCRIPTION 988 "This variable is used to create, modify, and/or 989 delete a row in this table." 990 ::= { teLinkEntry 14 } 992 teLinkStorageType OBJECT-TYPE 993 SYNTAX StorageType 994 MAX-ACCESS read-create 995 STATUS current 996 DESCRIPTION 997 "This variable indicates the storage type for this 998 object." 999 ::= { teLinkEntry 15 } 1001 -- End of teLinkTable 1003 -- TE Link Descriptor Table 1005 teLinkDescriptorTable OBJECT-TYPE 1006 SYNTAX SEQUENCE OF TeLinkDescriptorEntry 1007 MAX-ACCESS not-accessible 1008 STATUS current 1009 DESCRIPTION 1010 "This table specifies the link descriptors associated with the 1011 TE links." 1012 ::= { linkBundlingObjects 2 } 1014 teLinkDescriptorEntry OBJECT-TYPE 1015 SYNTAX TeLinkDescriptorEntry 1016 MAX-ACCESS not-accessible 1017 STATUS current 1018 DESCRIPTION 1019 "An entry in this table is created for every TE link descriptor. 1020 An ifEntry in the ifTable must exist before a 1021 teLinkDescriptorEntry using the same ifIndex is created. 1022 If a TE link entry in the ifTable is destroyed, then so are all 1023 entries in the teLinkDescriptorTable that use the ifIndex of 1024 this TE link." 1025 INDEX { ifIndex, teLinkDescriptorId } 1026 ::= { teLinkDescriptorTable 1 } 1028 TeLinkDescriptorEntry ::= SEQUENCE { 1029 teLinkDescriptorId Unsigned32, 1030 teLinkEncodingType Unsigned32, 1031 teLinkDescrPriority Unsigned32, 1032 teLinkMinReservableBandwidth Unsigned32, 1033 teLinkMaxReservableBandwidth Unsigned32, 1034 teLinkDescrRowStatus RowStatus, 1035 teLinkDescrStorageType StorageType 1036 } 1038 teLinkDescriptorId OBJECT-TYPE 1039 SYNTAX Unsigned32 1040 MAX-ACCESS not-accessible 1041 STATUS current 1042 DESCRIPTION 1043 "This object specifies the link descriptor identifier." 1044 ::= { teLinkDescriptorEntry 1 } 1046 teLinkEncodingType OBJECT-TYPE 1047 SYNTAX INTEGER { 1048 standardSonet(1), 1049 arbitrarySonet(2), 1050 standardSdh(3), 1051 arbitrarySdh(4), 1052 clear(5), 1053 gigE(6), 1054 tenGigE(7) 1055 } 1056 MAX-ACCESS read-only 1057 STATUS current 1058 DESCRIPTION 1059 "This attribute specifies the TE link encoding type." 1060 REFERENCE 1061 "draft-kompella-ospf-gmpls-extensions-01.txt - OSPF Extensions 1062 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1063 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1064 D. Saha, V. Sharma, February 2001." 1065 ::= { teLinkDescriptorEntry 2 } 1067 teLinkDescrPriority OBJECT-TYPE 1068 SYNTAX Unsigned32 (0..7) 1069 MAX-ACCESS read-only 1070 STATUS current 1071 DESCRIPTION 1072 "This object specifies the lowest priority at which that link 1073 encoding type is available." 1074 REFERENCE 1075 "draft-kompella-ospf-gmpls-extensions-01.txt - OSPF Extensions 1076 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1077 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1078 D. Saha, V. Sharma, February 2001." 1079 ::= { teLinkDescriptorEntry 3 } 1081 teLinkMinReservableBandwidth OBJECT-TYPE 1082 SYNTAX Unsigned32 1083 MAX-ACCESS read-only 1084 STATUS current 1085 DESCRIPTION 1086 "This attribute specifies the minimum reservable bandwidth on 1087 the TE link. This is derived from the union of the 1088 minimum reservable bandwidth of all the data-bearing 1089 channels associated with the TE link that can be used to carry 1090 live traffic." 1091 REFERENCE 1092 "draft-kompella-ospf-gmpls-extensions-01.txt - OSPF Extensions 1093 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1094 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1095 D. Saha, V. Sharma, February 2001." 1096 ::= { teLinkDescriptorEntry 4 } 1098 teLinkMaxReservableBandwidth OBJECT-TYPE 1099 SYNTAX Unsigned32 1100 MAX-ACCESS read-only 1101 STATUS current 1102 DESCRIPTION 1103 "This attribute specifies the maximum reservable bandwidth on 1104 the TE link. This is the union of the maximum reservable 1105 bandwidth of all the data-bearing channels within the 1106 TE link that can be used to carry live traffic." 1107 REFERENCE 1108 "draft-kompella-ospf-gmpls-extensions-01.txt - OSPF Extensions 1109 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1110 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1111 D. Saha, V. Sharma, February 2001." 1112 ::= { teLinkDescriptorEntry 5 } 1114 teLinkDescrRowStatus OBJECT-TYPE 1115 SYNTAX RowStatus 1116 MAX-ACCESS read-create 1117 STATUS current 1118 DESCRIPTION 1119 "This variable is used to create, modify, and/or 1120 delete a row in this table." 1121 ::= { teLinkDescriptorEntry 6 } 1123 teLinkDescrStorageType OBJECT-TYPE 1124 SYNTAX StorageType 1125 MAX-ACCESS read-create 1126 STATUS current 1127 DESCRIPTION 1128 "This variable indicates the storage type for this 1129 object." 1130 ::= { teLinkDescriptorEntry 7 } 1132 -- End of Link Descriptor Table 1134 -- OSPF Traffic Engineering Parameters for TE Links 1136 teLinkOspfTeTable OBJECT-TYPE 1137 SYNTAX SEQUENCE OF TeLinkOspfTeEntry 1138 MAX-ACCESS not-accessible 1139 STATUS current 1140 DESCRIPTION 1141 "This table specifies the OSPF traffic engineering information 1142 associated with TE links." 1143 ::= { linkBundlingObjects 3 } 1145 teLinkOspfTeEntry OBJECT-TYPE 1146 SYNTAX TeLinkOspfTeEntry 1147 MAX-ACCESS not-accessible 1148 STATUS current 1149 DESCRIPTION 1150 "If OSPF is enabled, an entry in this table is created for 1151 every TE link." 1152 AUGMENTS { teLinkEntry } 1153 ::= { teLinkOspfTeTable 1 } 1155 TeLinkOspfTeEntry ::= SEQUENCE { 1156 teLinkOspfLinkType Unsigned32, 1157 teLinkOspfLinkId RouterID 1158 } 1160 teLinkOspfLinkType OBJECT-TYPE 1161 SYNTAX INTEGER { 1162 pointToPoint(1), 1163 multiAccess(2) 1164 } 1165 MAX-ACCESS read-only 1166 STATUS current 1167 DESCRIPTION 1168 "This attribute specifies the OSPF link type for the TE link. 1169 All TE links within the same bundle must have the same 1170 link type." 1171 ::= { teLinkOspfTeEntry 1 } 1173 teLinkOspfLinkId OBJECT-TYPE 1174 SYNTAX RouterID 1175 MAX-ACCESS read-only 1176 STATUS current 1177 DESCRIPTION 1178 "On point-to-point link, the link identifier is the Router ID 1179 of the neighbor. For bundled link, is derived from the link 1180 identifier associated with its TE links." 1181 REFERENCE 1182 "draft-kompella-mpls-bundle-05.txt - Link Bundling in MPLS 1183 Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, 1184 February 2001." 1185 ::= { teLinkOspfTeEntry 2 } 1187 -- End of teLinkOspfTeTable 1189 -- TE Link Shared Risk Link Group Table 1191 teLinkSrlgTable OBJECT-TYPE 1192 SYNTAX SEQUENCE OF TeLinkSrlgEntry 1193 MAX-ACCESS not-accessible 1194 STATUS current 1195 DESCRIPTION 1196 "This table specifies the SRLGs associated with TE links." 1197 ::= { linkBundlingObjects 4 } 1199 teLinkSrlgEntry OBJECT-TYPE 1200 SYNTAX TeLinkSrlgEntry 1201 MAX-ACCESS not-accessible 1202 STATUS current 1203 DESCRIPTION 1204 "An entry in this table contains information about a 1205 SRLG associated with a TE link. 1206 An ifEntry in the ifTable must exist before a 1207 teLinkSrlgEntry using the same ifIndex is created. 1208 If a TE link entry in the ifTable is destroyed, then so are all 1209 entries in the teLinkSrlgTable that use the ifIndex of 1210 this TE link." 1211 INDEX { ifIndex, srlg } 1212 ::= { teLinkSrlgTable 1 } 1214 TeLinkSrlgEntry ::= SEQUENCE { 1215 srlg Unsigned32, 1216 srlgRowStatus RowStatus, 1217 srlgStorageType StorageType 1218 } 1220 srlg OBJECT-TYPE 1221 SYNTAX Unsigned32 1222 MAX-ACCESS not-accessible 1223 STATUS current 1224 DESCRIPTION 1225 "This identifies a SRLG supported by the TE link." 1226 REFERENCE 1227 "draft-kompella-ospf-gmpls-extensions-01.txt - OSPF Extensions 1228 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1229 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1230 D. Saha, V. Sharma, February 2001." 1231 ::= { teLinkSrlgEntry 1 } 1233 srlgRowStatus OBJECT-TYPE 1234 SYNTAX RowStatus 1235 MAX-ACCESS read-create 1236 STATUS current 1237 DESCRIPTION 1238 "This variable is used to create, modify, and/or 1239 delete a row in this table." 1240 ::= { teLinkSrlgEntry 2 } 1242 srlgStorageType OBJECT-TYPE 1243 SYNTAX StorageType 1244 MAX-ACCESS read-create 1245 STATUS current 1246 DESCRIPTION 1247 "This variable indicates the storage type for this 1248 object." 1249 ::= { teLinkSrlgEntry 3 } 1251 -- End of teLinkSrlgTable 1252 -- TE Link Bandwidth Table 1254 teLinkBandwidthTable OBJECT-TYPE 1255 SYNTAX SEQUENCE OF TeLinkBandwidthEntry 1256 MAX-ACCESS not-accessible 1257 STATUS current 1258 DESCRIPTION 1259 "This table specifies the priority-based bandwidth table 1260 for TE links." 1261 ::= { linkBundlingObjects 5 } 1263 teLinkBandwidthEntry OBJECT-TYPE 1264 SYNTAX TeLinkBandwidthEntry 1265 MAX-ACCESS not-accessible 1266 STATUS current 1267 DESCRIPTION 1268 "An entry in this table contains information about 1269 the priority-based bandwidth of TE links. An ifEntry in the 1270 ifTable must exist before a teLinkBandwidthEntry using the 1271 same ifIndex is created. If a TE link entry in the ifTable 1272 is destroyed, then so are all entries in the teLinkBandwidthTable 1273 that use the ifIndex of this TE link." 1274 INDEX { ifIndex, teLinkPriority } 1275 ::= { teLinkBandwidthTable 1 } 1277 TeLinkBandwidthEntry ::= SEQUENCE { 1278 teLinkPriority Unsigned32, 1279 teLinkUnreservedBandwidth Unsigned32, 1280 teLinkMaximumLspBandwidth Unsigned32, 1281 teLinkBandwidthRowStatus RowStatus, 1282 teLinkBandwidthStorageType StorageType 1283 } 1285 teLinkPriority OBJECT-TYPE 1286 SYNTAX Unsigned32 (1..8) 1287 MAX-ACCESS not-accessible 1288 STATUS current 1289 DESCRIPTION 1290 "This attribute specifies the priority. It should be mapped 1291 to a number between 0 and 7" 1292 REFERENCE 1293 "draft-kompella-ospf-gmpls-extensions-01.txt - OSPF Extensions 1294 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1295 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1296 D. Saha, V. Sharma, February 2001." 1297 ::= { teLinkBandwidthEntry 1 } 1299 teLinkUnreservedBandwidth OBJECT-TYPE 1300 SYNTAX Unsigned32 1301 MAX-ACCESS read-only 1302 STATUS current 1303 DESCRIPTION 1304 "This attribute specifies the TE link unreserved 1305 bandwidth at priority p. It is the sum of the unreserved 1306 bandwidths at priority p of all data-bearing channel associated 1307 with the TE link (excludes all channels that are strictly 1308 used as protecting channels)." 1309 REFERENCE 1310 "draft-kompella-mpls-bundle-05.txt - Link Bundling in MPLS 1311 Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, 1312 February 2001." 1313 ::= { teLinkBandwidthEntry 2 } 1315 teLinkMaximumLspBandwidth OBJECT-TYPE 1316 SYNTAX Unsigned32 1317 MAX-ACCESS read-only 1318 STATUS current 1319 DESCRIPTION 1320 "This attribute specifies the TE link maximum 1321 LSP bandwidth at priority p. It is the maximum of all 1322 maximum LSP bandwidth at priority p of the data-bearing channels 1323 associated with the TE link (excludes all channels that are 1324 strictly used as protecting channels)." 1325 REFERENCE 1326 "draft-kompella-mpls-bundle-05.txt - Link Bundling in MPLS 1327 Traffic Engineering, K. Kompella, Y. Rekhter, L. Berger, 1328 February 2001." 1329 ::= { teLinkBandwidthEntry 3 } 1331 teLinkBandwidthRowStatus OBJECT-TYPE 1332 SYNTAX RowStatus 1333 MAX-ACCESS read-create 1334 STATUS current 1335 DESCRIPTION 1336 "This variable is used to create, modify, and/or 1337 delete a row in this table." 1338 ::= { teLinkBandwidthEntry 4 } 1340 teLinkBandwidthStorageType OBJECT-TYPE 1341 SYNTAX StorageType 1342 MAX-ACCESS read-create 1343 STATUS current 1344 DESCRIPTION 1345 "This variable indicates the storage type for this 1346 object." 1347 ::= { teLinkBandwidthEntry 5 } 1349 -- End of teLinkBandwidthTable 1351 -- Data-bearing Channel Table 1353 dataBearingChannelTable OBJECT-TYPE 1354 SYNTAX SEQUENCE OF DataBearingChannelEntry 1355 MAX-ACCESS not-accessible 1356 STATUS current 1357 DESCRIPTION 1358 "This table specifies the data-bearing channel 1359 parameters." 1360 ::= { linkBundlingObjects 6 } 1362 dataBearingChannelEntry OBJECT-TYPE 1363 SYNTAX DataBearingChannelEntry 1364 MAX-ACCESS not-accessible 1365 STATUS current 1366 DESCRIPTION 1367 "An entry in this table exists for each ifEntry that represents 1368 a data-bearing channel. An ifEntry must exist in the ifTable 1369 before a dataBearingChannelEntry is created with the 1370 corresponding ifIndex. If an entry representing a data-bearing 1371 channel is destroyed in the ifTable, then so is the 1372 corresponding entry in the dataBearingChannelTable. The 1373 administrative and operational status values are controlled 1374 from the ifEntry." 1375 INDEX { ifIndex } 1376 ::= { dataBearingChannelTable 1 } 1378 DataBearingChannelEntry ::= SEQUENCE { 1379 dataBearingChannelLinkMuxCapability Unsigned32, 1380 dataBearingChannelPreferredProtection Unsigned32, 1381 dataBearingChannelCurrentProtection Unsigned32, 1382 dataBearingChannelRowStatus RowStatus, 1383 dataBearingChannelStorageType StorageType 1384 } 1386 dataBearingChannelLinkMuxCapability OBJECT-TYPE 1387 SYNTAX INTEGER { 1388 packetSwitch1(1), 1389 packetSwitch2(2), 1390 packetSwitch3(3), 1391 packetSwitch4(4), 1392 layer2Switch(51), 1393 tdm(100), 1394 lambdaSwitch(150), 1395 fiberSwitch(200) 1397 } 1398 MAX-ACCESS read-create 1399 STATUS current 1400 DESCRIPTION 1401 "This attribute specifies link multiplexing capabilities of the 1402 data-bearing channel." 1403 REFERENCE 1404 "draft-ietf-mpls-lsp-hierarchy-01.txt - LSP Hierarchy with 1405 MPLS TE, K. Kompella, Y. Rekhter, September 2000." 1406 ::= { dataBearingChannelEntry 1 } 1408 dataBearingChannelPreferredProtection OBJECT-TYPE 1409 SYNTAX INTEGER { 1410 primary(1), 1411 secondary(2) 1412 } 1413 MAX-ACCESS read-create 1414 STATUS current 1415 DESCRIPTION 1416 "This attribute specifies whether this data-bearing channel is 1417 a primary or secondary entity." 1418 ::= { dataBearingChannelEntry 2 } 1420 dataBearingChannelCurrentProtection OBJECT-TYPE 1421 SYNTAX INTEGER { 1422 primary(1), 1423 secondary(2) 1424 } 1425 MAX-ACCESS read-only 1426 STATUS current 1427 DESCRIPTION 1428 "This attribute specifies whether this data-bearing channel is 1429 currently used as primary or secondary channel." 1430 ::= { dataBearingChannelEntry 3 } 1432 dataBearingChannelRowStatus OBJECT-TYPE 1433 SYNTAX RowStatus 1434 MAX-ACCESS read-create 1435 STATUS current 1436 DESCRIPTION 1437 "This variable is used to create, modify, and/or 1438 delete a row in this table." 1439 ::= { dataBearingChannelEntry 4 } 1441 dataBearingChannelStorageType OBJECT-TYPE 1442 SYNTAX StorageType 1443 MAX-ACCESS read-create 1444 STATUS current 1445 DESCRIPTION 1446 "This variable indicates the storage type for this 1447 object." 1448 ::= { dataBearingChannelEntry 5 } 1450 -- End of dataBearingChannelTable 1452 -- Data-bearing Channel Link Descriptor Table 1454 dataBearingChannelDescriptorTable OBJECT-TYPE 1455 SYNTAX SEQUENCE OF DataBearingChannelDescrEntry 1456 MAX-ACCESS not-accessible 1457 STATUS current 1458 DESCRIPTION 1459 "This table specifies the link descriptors associated with the 1460 data-bearing channels." 1461 ::= { linkBundlingObjects 7 } 1463 dataBearingChannelDescrEntry OBJECT-TYPE 1464 SYNTAX DataBearingChannelDescrEntry 1465 MAX-ACCESS not-accessible 1466 STATUS current 1467 DESCRIPTION 1468 "An entry in this table is created for every data-bearing channel 1469 descriptor. An ifEntry in the ifTable must exist before a 1470 dataBearingChannelDescrEntry using the same ifIndex is created. 1471 If a data-bearing channel entry in the ifTable is destroyed, 1472 then so are all entries in the 1473 dataBearingChannelDescriptorTable that use the ifIndex of 1474 this data-bearing channel." 1475 INDEX { ifIndex, dataBearingChannelDescrId } 1476 ::= { dataBearingChannelDescriptorTable 1 } 1478 DataBearingChannelDescrEntry ::= SEQUENCE { 1479 dataBearingChannelDescrId Unsigned32, 1480 dataBearingChannelEncodingType Unsigned32, 1481 dataBearingChannelDescrPriority Unsigned32, 1482 dataBearingChannelMinReservableBandwidth Unsigned32, 1483 dataBearingChannelMaxReservableBandwidth Unsigned32, 1484 dataBearingChannelDescrRowStatus RowStatus, 1485 dataBearingChannelDescrStorageType StorageType 1486 } 1488 dataBearingChannelDescrId OBJECT-TYPE 1489 SYNTAX Unsigned32 1490 MAX-ACCESS not-accessible 1491 STATUS current 1492 DESCRIPTION 1493 "This object specifies the link descriptor identifier." 1494 ::= { dataBearingChannelDescrEntry 1 } 1496 dataBearingChannelEncodingType OBJECT-TYPE 1497 SYNTAX INTEGER { 1498 standardSonet(1), 1499 arbitrarySonet(2), 1500 standardSdh(3), 1501 arbitrarySdh(4), 1502 clear(5), 1503 gigE(6), 1504 tenGigE(7) 1505 } 1506 MAX-ACCESS read-create 1507 STATUS current 1508 DESCRIPTION 1509 "This attribute specifies the data-bearing channel encoding type." 1510 REFERENCE 1511 "draft-kompella-ospf-gmpls-extensions-01.txt - OSPF Extensions 1512 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1513 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1514 D. Saha, V. Sharma, February 2001." 1515 ::= { dataBearingChannelDescrEntry 2 } 1517 dataBearingChannelDescrPriority OBJECT-TYPE 1518 SYNTAX Unsigned32 (0..7) 1519 MAX-ACCESS read-create 1520 STATUS current 1521 DESCRIPTION 1522 "This object specifies the lowest priority at which that link 1523 encoding type is available for the data-bearing channel." 1524 REFERENCE 1525 "draft-kompella-ospf-gmpls-extensions-01.txt - OSPF Extensions 1526 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1527 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1528 D. Saha, V. Sharma, February 2001." 1529 ::= { dataBearingChannelDescrEntry 3 } 1531 dataBearingChannelMinReservableBandwidth OBJECT-TYPE 1532 SYNTAX Unsigned32 1533 MAX-ACCESS read-create 1534 STATUS current 1535 DESCRIPTION 1536 "This attribute specifies the minimum reservable bandwidth on 1537 the data-bearing channel." 1538 REFERENCE 1539 "draft-kompella-ospf-gmpls-extensions-01.txt - OSPF Extensions 1540 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1541 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1542 D. Saha, V. Sharma, February 2001." 1543 ::= { dataBearingChannelDescrEntry 4 } 1545 dataBearingChannelMaxReservableBandwidth OBJECT-TYPE 1546 SYNTAX Unsigned32 1547 MAX-ACCESS read-only 1548 STATUS current 1549 DESCRIPTION 1550 "This attribute specifies the maximum reservable bandwidth on 1551 the data-bearing channel." 1552 REFERENCE 1553 "draft-kompella-ospf-gmpls-extensions-01.txt - OSPF Extensions 1554 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1555 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1556 D. Saha, V. Sharma, February 2001." 1557 ::= { dataBearingChannelDescrEntry 5 } 1559 dataBearingChannelDescrRowStatus OBJECT-TYPE 1560 SYNTAX RowStatus 1561 MAX-ACCESS read-create 1562 STATUS current 1563 DESCRIPTION 1564 "This variable is used to create, modify, and/or 1565 delete a row in this table." 1566 ::= { dataBearingChannelDescrEntry 6 } 1568 dataBearingChannelDescrStorageType OBJECT-TYPE 1569 SYNTAX StorageType 1570 MAX-ACCESS read-create 1571 STATUS current 1572 DESCRIPTION 1573 "This variable indicates the storage type for this 1574 object." 1575 ::= { dataBearingChannelDescrEntry 7 } 1577 -- End of Link Descriptor Table 1579 -- Data-bearing Channel Bandwidth Table 1581 dataBearingChannelBandwidthTable OBJECT-TYPE 1582 SYNTAX SEQUENCE OF DataBearingChannelBandwidthEntry 1583 MAX-ACCESS not-accessible 1584 STATUS current 1585 DESCRIPTION 1586 "This table specifies the priority-based bandwidth 1587 for data-bearing channels." 1588 ::= { linkBundlingObjects 8 } 1590 dataBearingChannelBandwidthEntry OBJECT-TYPE 1591 SYNTAX DataBearingChannelBandwidthEntry 1592 MAX-ACCESS not-accessible 1593 STATUS current 1594 DESCRIPTION 1595 "An entry in this table contains information about 1596 the priority-based bandwidth on data-bearing channels. 1597 An ifEntry in the ifTable must exist before a 1598 dataBearingChannelBandwidthEntry using the same ifIndex is 1599 created. If a data-bearing channel entry in the ifTable is 1600 destroyed, then so are all entries in the 1601 dataBearingChannelBandwidthTable that use the ifIndex of 1602 this data-bearing channel." 1603 INDEX { ifIndex, dataBearingChannelPriority } 1604 ::= { dataBearingChannelBandwidthTable 1 } 1606 DataBearingChannelBandwidthEntry ::= SEQUENCE { 1607 dataBearingChannelPriority Unsigned32, 1608 dataBearingChannelUnreservedBandwidth Unsigned32, 1609 dataBearingChannelMaximumLspBandwidth Unsigned32, 1610 dataBearingChannelBwRowStatus RowStatus, 1611 dataBearingChannelBwStorageType StorageType 1612 } 1614 dataBearingChannelPriority OBJECT-TYPE 1615 SYNTAX Unsigned32 (1..8) 1616 MAX-ACCESS not-accessible 1617 STATUS current 1618 DESCRIPTION 1619 "This attribute specifies the priority. It should be mapped 1620 to a number between 0 and 7." 1621 REFERENCE 1622 "draft-kompella-ospf-gmpls-extensions-01.txt - OSPF Extensions 1623 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1624 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1625 D. Saha, V. Sharma, February 2001." 1626 ::= { dataBearingChannelBandwidthEntry 1 } 1628 dataBearingChannelUnreservedBandwidth OBJECT-TYPE 1629 SYNTAX Unsigned32 1630 MAX-ACCESS read-only 1631 STATUS current 1632 DESCRIPTION 1633 "This attribute specifies the data-bearing channel unreserved 1634 bandwidth at priority p." 1636 REFERENCE 1637 "draft-kompella-ospf-gmpls-extensions-01.txt - OSPF Extensions 1638 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1639 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1640 D. Saha, V. Sharma, February 2001." 1641 ::= { dataBearingChannelBandwidthEntry 2 } 1643 dataBearingChannelMaximumLspBandwidth OBJECT-TYPE 1644 SYNTAX Unsigned32 1645 MAX-ACCESS read-only 1646 STATUS current 1647 DESCRIPTION 1648 "This attribute specifies the data-bearing channel maximum 1649 LSP bandwidth at priority p." 1650 REFERENCE 1651 "draft-kompella-ospf-gmpls-extensions-01.txt - OSPF Extensions 1652 in Support of Generalized MPLS, K. Kompella, Y. Rekhter, 1653 A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, 1654 D. Saha, V. Sharma, February 2001." 1655 ::= { dataBearingChannelBandwidthEntry 3 } 1657 dataBearingChannelBwRowStatus OBJECT-TYPE 1658 SYNTAX RowStatus 1659 MAX-ACCESS read-create 1660 STATUS current 1661 DESCRIPTION 1662 "This variable is used to create, modify, and/or 1663 delete a row in this table." 1664 ::= { dataBearingChannelBandwidthEntry 4 } 1666 dataBearingChannelBwStorageType OBJECT-TYPE 1667 SYNTAX StorageType 1668 MAX-ACCESS read-create 1669 STATUS current 1670 DESCRIPTION 1671 "This variable indicates the storage type for this 1672 object." 1673 ::= { dataBearingChannelBandwidthEntry 5 } 1675 -- End of dataBearingChannelBandwidthTable 1677 -- Notification Configuration 1679 linkBundlingTrapEnable OBJECT-TYPE 1680 SYNTAX TruthValue 1681 MAX-ACCESS read-write 1682 STATUS current 1683 DESCRIPTION 1684 "If this object is true, then it enables the 1685 generation of the link bundling traps, 1686 otherwise these traps are not emitted." 1687 DEFVAL { false } 1688 ::= { linkBundlingObjects 9 } 1690 -- Notifications 1692 -- Bundled Link Traps 1694 linkBundleMismatch NOTIFICATION-TYPE 1695 OBJECTS { ifIndex } 1696 STATUS current 1697 DESCRIPTION 1698 "This notification is generated when a mismatch is found on a 1699 bundled link. Such mismatch can be detected for instance if one 1700 of the traffic engineering parameters is not consistent across 1701 all TE links within a bundled link (resource class, 1702 OSPF link type, etc.)." 1703 ::= { linkBundlingNotifications 1 } 1705 -- End of notifications 1707 -- Module compliance 1709 linkBundlingGroups 1710 OBJECT IDENTIFIER ::= { linkBundlingConformance 1 } 1712 linkBundlingCompliances 1713 OBJECT IDENTIFIER ::= { linkBundlingConformance 2 } 1715 linkBundlingModuleCompliance MODULE-COMPLIANCE 1716 STATUS current 1717 DESCRIPTION 1718 "Compliance statement for agents that support the 1719 link bundling MIB." 1720 MODULE -- this module 1722 -- The mandatory groups have to be implemented 1723 -- by all devices supporting link bundling. However, they may all 1724 -- be supported as read-only objects in the case where manual 1725 -- configuration is unsupported. 1727 MANDATORY-GROUPS { linkBundlingGroup, 1728 teLinkBandwidthGroup } 1730 GROUP teLinkOspfTeGroup 1731 DESCRIPTION 1732 "This group is mandatory for OSPF enabled devices." 1734 GROUP teLinkSrlgGroup 1735 DESCRIPTION 1736 "This group is mandatory for G-MPLS enabled devices." 1738 -- teLinkTable 1740 OBJECT teLinkProtectionType 1741 MIN-ACCESS read-only 1742 DESCRIPTION 1743 "Write access is not required." 1745 OBJECT teLinkWorkingPriority 1746 MIN-ACCESS read-only 1747 DESCRIPTION 1748 "Write access is not required." 1750 OBJECT teLinkFlooding 1751 MIN-ACCESS read-only 1752 DESCRIPTION 1753 "Write access is not required." 1755 OBJECT teLinkRowStatus 1756 SYNTAX INTEGER { active(1), notInService(2), 1757 createAndGo(4), destroy(6) } 1758 MIN-ACCESS read-only 1759 DESCRIPTION 1760 "The notReady(3) state need not be supported." 1762 OBJECT teLinkStorageType 1763 SYNTAX INTEGER { other(1) } 1764 MIN-ACCESS read-only 1765 DESCRIPTION 1766 "Only other(1) needs to be supported." 1768 -- teLinkDescriptorTable 1770 OBJECT teLinkDescrRowStatus 1771 SYNTAX INTEGER { active(1), notInService(2), 1772 createAndGo(4), destroy(6) } 1773 MIN-ACCESS read-only 1774 DESCRIPTION 1775 "The notReady(3) state need not be supported." 1777 OBJECT teLinkDescrStorageType 1778 SYNTAX INTEGER { other(1) } 1779 MIN-ACCESS read-only 1780 DESCRIPTION 1781 "Only other(1) needs to be supported." 1783 -- teLinkOspfTeTable 1785 OBJECT teLinkOspfLinkId 1786 SYNTAX INTEGER { pointToPoint(1) } 1787 MIN-ACCESS read-only 1788 DESCRIPTION 1789 "A value of multiAccess(2) need not be supported." 1791 -- teLinkSrlgTable 1793 OBJECT srlgRowStatus 1794 SYNTAX INTEGER { active(1), notInService(2), 1795 createAndGo(4), destroy(6) } 1796 MIN-ACCESS read-only 1797 DESCRIPTION 1798 "The notReady(3) and createAndWait(5) states need 1799 not be supported." 1801 OBJECT srlgStorageType 1802 SYNTAX INTEGER { other(1) } 1803 MIN-ACCESS read-only 1804 DESCRIPTION 1805 "Only other(1) needs to be supported." 1807 -- teLinkBandwidthTable 1809 OBJECT teLinkBandwidthRowStatus 1810 SYNTAX INTEGER { active(1), notInService(2), 1811 createAndGo(4), destroy(6) } 1812 MIN-ACCESS read-only 1813 DESCRIPTION 1814 "The notReady(3) and createAndWait(5) states need 1815 not be supported." 1817 OBJECT teLinkBandwidthStorageType 1818 SYNTAX INTEGER { other(1) } 1819 MIN-ACCESS read-only 1820 DESCRIPTION 1821 "Only other(1) needs to be supported." 1823 -- dataBearingChannelTable 1824 OBJECT dataBearingChannelPreferredProtection 1825 MIN-ACCESS read-only 1826 DESCRIPTION 1827 "Write access is not required." 1829 OBJECT dataBearingChannelRowStatus 1830 SYNTAX INTEGER { active(1), notInService(2), 1831 createAndGo(4), destroy(6) } 1832 MIN-ACCESS read-only 1833 DESCRIPTION 1834 "The notReady(3) and createAndWait(5) states need 1835 not be supported." 1837 OBJECT dataBearingChannelStorageType 1838 SYNTAX INTEGER { other(1) } 1839 MIN-ACCESS read-only 1840 DESCRIPTION 1841 "Only other(1) needs to be supported." 1843 -- dataBearingChannelDescriptorTable 1845 OBJECT dataBearingChannelEncodingType 1846 MIN-ACCESS read-only 1847 DESCRIPTION 1848 "Write access is not required." 1850 OBJECT dataBearingChannelDescrPriority 1851 MIN-ACCESS read-only 1852 DESCRIPTION 1853 "Write access is not required." 1855 OBJECT dataBearingChannelMinReservableBandwidth 1856 MIN-ACCESS read-only 1857 DESCRIPTION 1858 "Write access is not required." 1860 OBJECT dataBearingChannelDescrRowStatus 1861 SYNTAX INTEGER { active(1), notInService(2), 1862 createAndGo(4), destroy(6) } 1863 MIN-ACCESS read-only 1864 DESCRIPTION 1865 "The notReady(3) state need not be supported." 1867 OBJECT dataBearingChannelDescrStorageType 1868 SYNTAX INTEGER { other(1) } 1869 MIN-ACCESS read-only 1870 DESCRIPTION 1871 "Only other(1) needs to be supported." 1873 -- dataBearingChannelBandwidthTable 1875 OBJECT dataBearingChannelBwRowStatus 1876 SYNTAX INTEGER { active(1), notInService(2), 1877 createAndGo(4), destroy(6) } 1878 MIN-ACCESS read-only 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-only 1886 DESCRIPTION 1887 "Only other(1) needs to be supported." 1889 ::= { linkBundlingCompliances 1 } 1891 -- Units of conformance 1893 linkBundlingGroup OBJECT-GROUP 1894 OBJECTS { teLinkNumberingType, 1895 teLinkIpAddrType, 1896 teLinkIpAddr, 1897 teLinkRemoteIpAddr, 1898 teLinkMetric, 1899 teLinkMuxCapability, 1900 teLinkProtectionType, 1901 teLinkWorkingPriority, 1902 teLinkResourceClass, 1903 teLinkIncomingIfId, 1904 teLinkOutgoingIfId, 1905 teLinkFlooding, 1906 teLinkRowStatus, 1907 teLinkStorageType, 1908 teLinkEncodingType, 1909 teLinkDescrPriority, 1910 teLinkMinReservableBandwidth, 1911 teLinkMaxReservableBandwidth, 1912 teLinkDescrRowStatus, 1913 teLinkDescrStorageType, 1914 dataBearingChannelLinkMuxCapability, 1915 dataBearingChannelPreferredProtection, 1916 dataBearingChannelCurrentProtection, 1917 dataBearingChannelRowStatus, 1918 dataBearingChannelStorageType, 1919 linkBundlingTrapEnable 1920 } 1922 STATUS current 1923 DESCRIPTION 1924 "Collection of objects needed for the monitoring of 1925 resources associated with TE links." 1926 ::= { linkBundlingGroups 1 } 1928 teLinkOspfTeGroup OBJECT-GROUP 1929 OBJECTS { teLinkOspfLinkType, 1930 teLinkOspfLinkId 1931 } 1933 STATUS current 1934 DESCRIPTION 1935 "Collection of objects needed for the OSPF traffic 1936 engineering parameters of TE links." 1937 ::= { linkBundlingGroups 2 } 1939 teLinkSrlgGroup OBJECT-GROUP 1940 OBJECTS { srlgRowStatus, 1941 srlgStorageType 1942 } 1944 STATUS current 1945 DESCRIPTION 1946 "Collection of objects needed for the monitoring of 1947 SRLG resources associated with TE links." 1948 ::= { linkBundlingGroups 3 } 1950 teLinkBandwidthGroup OBJECT-GROUP 1951 OBJECTS { teLinkUnreservedBandwidth, 1952 teLinkMaximumLspBandwidth, 1953 teLinkBandwidthRowStatus, 1954 teLinkBandwidthStorageType 1955 } 1957 STATUS current 1958 DESCRIPTION 1959 "Collection of objects needed for the monitoring of 1960 the priority-based bandwidth resources associated with 1961 TE links and data-bearing channels." 1962 ::= { linkBundlingGroups 4 } 1964 dataBearingChannelBandwidthGroup OBJECT-GROUP 1965 OBJECTS { dataBearingChannelEncodingType, 1966 dataBearingChannelDescrPriority, 1967 dataBearingChannelMinReservableBandwidth, 1968 dataBearingChannelMaxReservableBandwidth, 1969 dataBearingChannelDescrRowStatus, 1970 dataBearingChannelDescrStorageType, 1971 dataBearingChannelUnreservedBandwidth, 1972 dataBearingChannelMaximumLspBandwidth, 1973 dataBearingChannelBwRowStatus, 1974 dataBearingChannelBwStorageType 1975 } 1977 STATUS current 1978 DESCRIPTION 1979 "Collection of objects needed for the monitoring of 1980 bandwidth parameters associated with data-bearing channels." 1981 ::= { linkBundlingGroups 5 } 1983 linkBundlingNotificationGroup NOTIFICATION-GROUP 1984 NOTIFICATIONS { linkBundleMismatch } 1985 STATUS current 1986 DESCRIPTION 1987 "Set of notifications implemented in this module. 1988 None is mandatory." 1989 ::= { linkBundlingGroups 6 } 1991 -- End of LINK-BUNDLING-MIB 1992 END 1994 11. Security Considerations 1996 It is clear that this MIB is potentially useful for monitoring of 1997 link bundling enabled devices. This MIB can also be used for confi- 1998 guration of certain objects, and anything that can be configured can 1999 be incorrectly configured, with potentially disastrous results. 2001 At this writing, no security holes have been identified beyond those 2002 that SNMP Security [SNMPArch] is itself intended to address. These 2003 relate to primarily controlled access to sensitive information and 2004 the ability to configure a device - or which might result from opera- 2005 tor error, which is beyond the scope of any security architecture. 2007 There are a number of management objects defined in this MIB which 2008 have a MAX-ACCESS clause of read-write and/or read-create. Such 2009 objects may be considered sensitive or vulnerable in some network 2010 environments. The support for SET operations in a non-secure environ- 2011 ment without proper protection can have a negative effect on network 2012 operations. The use of SNMP Version 3 is recommended over prior ver- 2013 sions, for configuration control, as its security model is improved. 2015 SNMPv1 or SNMPv2 are by themselves not a secure environment. Even if 2016 the network itself is secure (for example by using IPSec [IPSEC]), 2017 there is no control as to who on the secure network is allowed to 2018 access and GET/SET (read/change/create/delete) the objects in this 2019 MIB. It is recommended that the implementers consider the security 2020 features as provided by the SNMPv3 framework. Specifically, the use 2021 of the User-based Security Model [SNMPv3USM] and the View-based 2022 Access Control [SNMPv3VACM] is recommended. It is then a 2023 customer/user responsibility to ensure that the SNMP entity giving 2024 access to an instance of this MIB is properly configured to give 2025 access to the objects only to those principals (users) that have leg- 2026 itimate rights to indeed GET or SET (change/create/delete) them. 2028 There are a number of managed objects in this MIB that may contain 2029 information that may be sensitive from a business perspective, in 2030 that they represent a customer's interface to the OSPF/MPLS network. 2031 Allowing uncontrolled access to these objects could result in mali- 2032 cious and unwanted disruptions of network traffic or incorrect confi- 2033 gurations for these customers. There are no objects that are particu- 2034 larly sensitive in their own right, such as passwords or monetary 2035 amounts. 2037 12. Acknowledgments 2039 The general structure of this draft has been modeled around draft- 2040 ietf-mpls-lsr-mib-06.txt. The authors would like to acknowlegde the 2041 contribution of Dmitry Ryumkin. 2043 13. References 2045 [BUNDLING] Kompella, K., Rekhter, Y., and Berger, L., 2046 "Link Bundling in MPLS Traffic Engineering", 2047 Internet Draft , 2048 February 2001. 2050 [LMP] Lang, J., Mitra, K., Drake, J., Kompella, K., 2051 Rekhter, Y., Berger, L., Rajagopalan, B., 2052 Basak, D., Sandick, H., Zinin, A., and 2053 Banarjee, A., "Link Management Protocol", 2054 Internet Draft , 2055 March 2001. 2057 [GMPLS] Ashwood-Smith, P., Banarjee, A., Berger, L., 2058 Bernstein, G., Drake, J., Fan, Y., Kompella, K., 2059 Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y., 2060 Saha, D., Sharma, V., Swallow, G., and Tang, Z., 2061 "Generalized MPLS Signaling Functional Description", 2062 Internet Draft 2063 , 2064 May 2001. 2066 [GMPLS-ARCH] Ashwood-Smith, P., Awduche, D., Banarjee, A., 2067 Basak, D., Berger, L., Bernstein, G., Drake, J., 2068 Fan, Y., Fedyk, D., Grammel, G., Kompella, K., 2069 Kullberg, A., Lang, J., Liaw, F., Papadimitriou, D., 2070 Pendarakis, D., Rajagopalan, B., Rekhter, Y., 2071 Saha, D., Sharma, V., Swallow, G., Tang, Z., 2072 Yu, J., Zinin, A., Mannie, E., 2073 "Generalized Multi-Protocol Label Switching (GMPLS) 2074 Architecture", Internet Draft 2075 , 2076 February 2001. 2078 [OSPF] Katz, D., Yeung, D. "Traffic Engineering Extensions to 2079 OSPF", Internet Draft 2080 , March 2001. 2082 [GMPLS-OSPF] Kompella, K., Rekhter, Y., Banerjee, A. et al, "OSPF 2083 Extensions in Support of Generalized MPLS", Internet 2084 Draft 2085 , 2086 February 2001. 2088 [LSP-HIER] Kompella, K., Rekhter, Y., LSP Hierarchy with MPLS TE, 2089 Internet Draft , 2090 September 2000. 2092 [ZININ] Zinin, A., SHand, M., "Flooding optimizations in link- 2093 state routing protocols", Internet Draft, 2094 , October 2000. 2096 [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", 2097 RFC 1700, October 1994. See also: 2098 http://www.isi.edu/in-notes/iana/assignments/smi- 2099 numbers 2101 [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS 2102 FAMILY NUMBERS, (http://www.isi.edu/in- 2103 notes/iana/assignements/address-family-numbers), 2104 for MIB see: 2105 ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib 2107 [SNMPArch] Harrington, D., Presuhn, R., and B. Wijnen, "An 2108 Architecture for Describing SNMP Management 2109 Frameworks", RFC 2571, April 1999. 2111 [SMIv1] Rose, M., and K. McCloghrie, "Structure and 2112 Identification of Management Information for TCP/IP- 2113 based Internets", RFC 1155, May 1990. 2115 [SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB 2116 Definitions", RFC 1212, March 1991. 2118 [SNMPv1Traps] M. Rose, "A Convention for Defining Traps for use 2119 with the SNMP", RFC 1215, March 1991. 2121 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2122 "Message Processing and Dispatching for the Simple 2123 Network Management Protocol (SNMP)", RFC 2572, 2124 April 1999. 2126 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 2127 Model (USM) for version 3 of the Simple Network 2128 Management Protocol (SNMPv3)", RFC 2574, April 2129 1999. 2131 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. 2132 Waldbusser, "Protocol Operations for Version 2 of 2133 the Simple Network Management Protocol (SNMPv2)", 2134 RFC 1905, January 1996. 2136 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2137 Applications", RFC 2573, April 1999. 2139 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- 2140 based Access Control Model (VACM) for the Simple 2141 Network Management Protocol (SNMP)", RFC 2575, 2142 April 1999. 2144 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 2145 "Introduction to Version 3 of the Internet-standard 2146 Network Management Framework", RFC 2570, April 2147 1999. 2149 [SMIv2] McCloghrie, K., Perkins, D., Schoenwaelder, J., 2150 Case, J., Rose, M., and S. Waldbusser, 2151 "Structure of Management Information 2152 Version 2 (SMIv2)", RFC 2578, April 1999. 2154 [SNMPv2TC] McCloghrie, K., Perkins, D., Schoenwaelder, J., 2155 Case, J., Rose, M., and S. Waldbusser, 2156 "Textual Conventions for SMIv2", 2157 RFC 2579, April 1999. 2159 [SNMPv2Conf] McCloghrie, K., Perkins, D., Schoenwaelder, J., 2160 Case, J., Rose, M., and S. Waldbusser, 2161 "Conformance Statements for SMIv2", 2162 RFC 2580, April 1999. 2164 [SNMPv1] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 2165 "Simple Network Management Protocol", RFC 1157, May 2166 1990. 2168 [SNMPv2c] Case, J., McCloghrie, K., Rose, M., and S. 2169 Waldbusser, "Introduction to Community-based 2170 SNMPv2", RFC 1901, January 1996. 2172 [SNMPv2TM] Case, J., McCloghrie, K., Rose, M., and S. 2173 Waldbusser, "Transport Mappings for Version 2 of 2174 the Simple Network Management Protocol (SNMPv2)", 2175 RFC 1906, January 1996. 2177 [SNMPv3MP] Case, J., Harrington D., Presuhn R., and B. Wijnen, 2178 "Message Processing and Dispatching for the Simple 2179 Network Management Protocol (SNMP)", RFC 2272, 2180 January 1998. 2182 [SNMPv3USM] Blumenthal, U., and B. Wijnen, "User-based Security 2183 Model (USM) for version 3 of the Simple Network 2184 Management Protocol (SNMPv3)", RFC 2574, April 2185 1999. 2187 [SNMPv2PO] Case, J., McCloghrie, K., Rose, M., and S. 2188 Waldbusser, "Protocol Operations for Version 2 of 2189 the Simple Network Management Protocol (SNMPv2)", 2190 RFC 1905, January 1996. 2192 [SNMPv3App] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 2193 Applications", RFC 2273, January 1998. 2195 [SNMPv3VACM] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- 2196 based Access Control Model (VACM) for the Simple 2197 Network Management Protocol (SNMP)", RFC 2575, 2198 April 1999. 2200 [IPSEC] Kent, S., and Atkinson, R., "Security Architecture 2201 for the Internet Protocol", RFC 2401, November 2202 1998. 2204 [IFMIB] McCloghrie, K., and Kastenholtz, F., "The Interfaces 2205 Group MIB", RFC 2863, June 2000. 2207 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 2208 Requirement Levels", BCP 14, RFC 2119, March 1997. 2210 14. Authors' Addresses 2212 Martin Dubuc Thomas D. Nadeau 2213 edgeflow, Inc. Cisco Systems, Inc. 2214 329 March Rd. 300 Apollo Drive 2215 Kanata, ON, CANADA K2K 2E1 Chelmsford, MA 01824 2216 Phone: +1-613-270-9279 x253 Phone: +1-978-244-3051 2217 Email: martin.dubuc@edgeflow.com Email: tnadeau@cisco.com 2219 Sudheer Dharanikota Jonathan P. Lang 2220 Nayna Networks, Inc. Calient Networks, Inc. 2221 157 Topaz Street 25 Castilian Drive 2222 Milipitas, CA 95035 Goleta, CA 93117 2223 Phone: +1-408-956-8000 x357 Email: jplang@calient.net 2224 Email: sudheer@nayna.com 2226 15. Full Copyright Statement 2228 Copyright (C) The Internet Society (2000). All Rights Reserved. 2230 This document and translations of it may be copied and furnished to 2231 others, and derivative works that comment on or otherwise explain it 2232 or assist in its implementation may be prepared, copied, published 2233 and distributed, in whole or in part, without restriction of any 2234 kind, provided that the above copyright notice and this paragraph are 2235 included on all such copies and derivative works. However, this docu- 2236 ment itself may not be modified in any way, such as by removing the 2237 copyright notice or references to the Internet Society or other 2238 Internet organizations, except as needed for the purpose of develop- 2239 ing Internet standards in which case the procedures for copyrights 2240 defined in the Internet Standards process must be followed, or as 2241 required to translate it into languages other than English. 2243 The limited permissions granted above are perpetual and will not be 2244 revoked by the Internet Society or its successors or assigns. This 2245 document and the information contained herein is provided on an "AS 2246 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 2247 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 2248 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL 2249 NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY 2250 OR FITNESS FOR A PARTICULAR PURPOSE.