idnits 2.17.1 draft-ietf-mpls-telink-mib-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) Miscellaneous warnings: ---------------------------------------------------------------------------- -- 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 (May 2003) is 7650 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: 'RFC3291' is defined on line 2060, but no explicit reference was found in the text ** Obsolete normative reference: RFC 3291 (Obsoleted by RFC 4001) -- Possible downref: Non-RFC (?) normative reference: ref. 'BUNDLING' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLS-OSPF' -- Possible downref: Non-RFC (?) normative reference: ref. 'IANAifType' -- Possible downref: Non-RFC (?) normative reference: ref. 'LMP' -- Possible downref: Non-RFC (?) normative reference: ref. 'OSPF' -- Possible downref: Non-RFC (?) normative reference: ref. 'ROUTING' Summary: 3 errors (**), 0 flaws (~~), 1 warning (==), 8 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Martin Dubuc 3 Internet Draft 4 Category: Standards Track Sudheer Dharanikota 5 Expires: November 2003 Avici Systems 7 Thomas D. Nadeau 8 Cisco Systems 10 Jonathan P. Lang 11 Rincon Networks 13 May 2003 15 Traffic Engineering Link Management Information Base 17 draft-ietf-mpls-telink-mib-02.txt 19 Status of this Memo 21 This document is an Internet-Draft and is in full conformance with 22 all provisions of Section 10 of RFC 2026. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF), its areas, and its working groups. Note that other 26 groups may also distribute working documents as Internet-Drafts. 28 Internet-Drafts are draft documents valid for a maximum of six months 29 and may be updated, replaced, or obsoleted by other documents at any 30 time. It is inappropriate to use Internet-Drafts as reference 31 material or to cite them other than as "work in progress." 33 The list of current Internet-Drafts can be accessed at 34 http://www.ietf.org/ietf/1id-abstracts.txt. 36 The list of Internet-Draft Shadow Directories can be accessed at 37 http://www.ietf.org/shadow.html. 39 Abstract 41 This memo defines a portion of the Management Information Base (MIB) 42 for use with network management protocols in the Internet community. 43 In particular, it describes managed objects for modeling TE links as 44 described in the Link Bundling in MPLS Traffic Engineering document. 46 Table of Contents 47 1. The Internet-Standard Management Framework . . . . . . . . . . . 2 48 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 2 49 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 50 4. Feature Checklist . . . . . . . . . . . . . . . . . . . . . . . . 3 51 5. Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 52 6. Brief Description of MIB Objects . . . . . . . . . . . . . . . . 4 53 6.1. teLinkTable . . . . . . . . . . . . . . . . . . . . . . . . . . 4 54 6.2. teLinkDescriptorTable . . . . . . . . . . . . . . . . . . . . . 4 55 6.3. teLinkSrlgTable . . . . . . . . . . . . . . . . . . . . . . . . 4 56 6.4. teLinkBandwidthTable . . . . . . . . . . . . . . . . . . . . . 4 57 6.5. componentLinkTable . . . . . . . . . . . . . . . . . . . . . . 4 58 6.6. componentLinkDescriptorTable . . . . . . . . . . . . . . . . . 5 59 6.7. componentLinkBandwidthTable . . . . . . . . . . . . . . . . . . 5 60 7. Example of Bundled Link Setup . . . . . . . . . . . . . . . . . . 5 61 8. Application of the Interfaces Group to TE Links . . . . . . . . . 9 62 8.1 Support of the TE Link Layer by ifTable . . . . . . . . . . . . 9 63 8.2 Using ifStackTable . . . . . . . . . . . . . . . . . . . . . . . 11 64 9. TE Link MIB Module Definitions . . . . . . . . . . . . . . . . . 13 65 10. Intellectual Property Considerations . . . . . . . . . . . . . . 42 66 11. Security Considerations . . . . . . . . . . . . . . . . . . . . 42 67 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 43 68 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 69 13.1 Normative References . . . . . . . . . . . . . . . . . . . . . 43 70 13.2 Informative References . . . . . . . . . . . . . . . . . . . . 44 71 14. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 45 72 15. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 45 74 1. The Internet-Standard Management Framework 76 For a detailed overview of the documents that describe the current 77 Internet-Standard Management Framework, please refer to section 7 of 78 RFC 3410 [RFC3410]. 80 Managed objects are accessed via a virtual information store, termed 81 the Management Information Base or MIB. MIB objects are generally 82 accessed through the Simple Network Management Protocol (SNMP). 83 Objects in the MIB are defined using the mechanisms defined in the 84 Structure of Management Information (SMI). This memo specifies a MIB 85 module that is compliant to the SMIv2, which is described in STD 58, 86 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 87 [RFC2580]. 89 2. Introduction 91 OSPF [OSPF], Generalized MPLS (GMPLS) [RFC3471] and the Link Manage- 92 ment Protocol (LMP) [LMP] use the concept of traffic engineering (TE) 93 links to abstract link properties. The effect of this approach is the 94 reduction of the amount of routing information exchanged in the 95 network, which improves routing scalability. In addition, the use of 96 TE link allows the implementation of new capabilities such as link 97 protection. 99 We present in this document a MIB module that can be used to manage 100 TE links and their extension, the bundled link. This MIB module 101 enables both the configuration and the performance monitoring of TE 102 links and bundled link. 104 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 105 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 106 document are to be interpreted as described in RFC 2119, reference 107 [RFC2119]. 109 3. Terminology 111 This document uses terminology from the documents describing link 112 bundling [BUNDLING] and G-MPLS [GMPLS-ARCH]. 114 The link bundling feature is designed to aggregate one or more simi- 115 lar entities between a node pair into a bundled link [BUNDLING]. In 116 the document, those entities are referred to as TE links. A TE link 117 is a subinterface capable of carrying MPLS traffic engineered traf- 118 fic. A TE Link may be comprised of only one underlying component 119 link. In cases where more than one component links are to be com- 120 bined, multiple component links should be created with differing pri- 121 orities to indicate hot-standby or parallel utilization. 123 A bundled link is just another kind of Traffic Engineering (TE) link 124 (see [GMPLS-OSPF]). A link bundle is a subinterface which bounds the 125 traffic of a group of one or more TE links. There should be more than 126 one TE Link in a link bundle, but this is not a requirement. Fur- 127 thermore, if there are more than one TE link in a link bundle at some 128 time, and at some point later, all but one of the links are deleted, 129 the agent may choose to either delete the link bundle, or it may 130 choose to leave it intact. Traffic counters on a link bundle are 131 cumulative for all subinterfaces which it binds together. 133 4. Feature Checklist 135 The TE Link MIB module (TE-LINK-MIB) is designed to satisfy the fol- 136 lowing requirements and constraints: 138 - The MIB module supports the management of TE links, including 139 bundled links. 141 - Support is provided for configuration of traffic engineering 142 parameters associated with TE links. 144 - The MIB module is used to monitor the priority-based component 145 link and TE link bandwidth values. 147 5. Outline 149 Configuring bundled links involves the following steps: 151 - Creating a bundled link. 153 - Creating TE links. 155 - Optionally specifying the shared risk link groups associated with 156 the TE links. 158 - Configuring the component links including the bandwidth 159 parameters and associating the component links with the 160 appropriate TE link. 162 - Associating the TE links with the appropriate bundled link. 164 6. Brief Description of MIB Objects 166 Sections 6.1-6.4 describe objects pertaining to TE links. The MIB 167 objects were derived from the link bundling document [BUNDLING]. 169 6.1. teLinkTable 171 This table represents the TE links, including bundled links, and 172 their generic traffic engineering parameters. 174 6.2. teLinkDescriptorTable 176 This table represents the TE link descriptors. 178 6.3. teLinkSrlgTable 180 This table represents the shared risk link groups (SRLGs) associated 181 with TE links. 183 6.4. teLinkBandwidthTable 185 This table specifies the priority-based bandwidth traffic engineering 186 parameters associated with TE links. 188 6.5. componentLinkTable 190 This table enumerates the component links and their generic traffic 191 engineering parameters. with TE link. 193 6.6. componentLinkDescriptorTable 195 This table enumerates the link descriptors that each component link 196 supports. 198 6.7. componentLinkBandwidthTable 200 The component link bandwidth table specifies the priority-based band- 201 width values associated with the component links. 203 Component links that belong to the same TE link must be compatible. 204 They must support the same switching capability and the same set of 205 link descriptors. Consequently, the link descriptors of the teLinkDe- 206 scriptorTable can be derived from the link descriptors of the compo- 207 nentLinkDescrTable. If these two tables are managed independently, 208 mechanisms should be put in place to ensure consistency between the 209 two tables. 211 TE links that form a bundled link must have compatible traffic engi- 212 neering parameters (switching capability, link descriptors, resource 213 class, link metric and protection type). 215 Some of the bandwidth parameters of the teLinkBandwidthTable are 216 derived from the bandwidth parameters of the componentLinkBand- 217 widthTable (maximum/minimum reservable bandwidth and unreserved band- 218 width). 220 7. Example of Bundled Link Setup 222 In this section we provide a brief example of using the MIB 223 objects described in section 10 to set up a bundled link. 224 While this example is not meant to illustrate every nuance of the 225 MIB module, it is intended as an aid to understanding some 226 of the key concepts. It is meant to be read after going through the 227 MIB module itself. More details on the use of the ifStackTable 228 to establish relationship between bundled links, TE links and 229 component links are given in Section 8.2. 231 Suppose that one would like to manually create a bundled link 232 out of two 1:1 TE links as depicted on the figure in Section 8.2. 233 Assume that the bundled link is associated with SRLGs 10 and 50. 234 Finally, let the component links be port entity interfaces 235 (lambdas). The following example illustrates which rows and 236 corresponding objects might be created to accomplish this. 238 First, a bundled link entry is created. An ifEntry with the same 239 ifIndex and with ifType teLink needs to be created beforehand. 241 In teLinkTable: 242 { 243 ifIndex = 2, 244 teLinkAddressType = unknown(0), 245 teLinkLocalIpAddr = ''H, 246 teLinkRemoteIpAddr = ''H, 247 teLinkMetric = 5, 248 teLinkMuxCapability = lambdaSwitch(150), 249 teLinkProtectionType = dedicated1For1(4), 250 teLinkWorkingPriority = 7, 251 teLinkResourceClass = 3, 252 teLinkIncomingIfId = 0, 253 teLinkOutgoingIfId = 2, 254 teLinkRowStatus = createAndGo(4), 255 teLinkStorageType = nonVolatile(3) 256 } 258 In ifStackTable: 259 { 260 ifStackHigherLayer = 0, 261 ifStackLowerLayer = 2, 262 ifStackStatus = createAndGo(4) 263 } 265 Next, the two TE links are created. 267 In teLinkTable: 268 { 269 ifIndex = 3, 270 teLinkAddressType = unknown(0), 271 teLinkLocalIpAddr = ''H, 272 teLinkRemoteIpAddr = ''H, 273 teLinkMetric = 5, 274 teLinkMuxCapability = lambdaSwitch(150), 275 teLinkProtectionType = unprotected(2), 276 teLinkWorkingPriority = 7, 277 teLinkResourceClass = 3, 278 teLinkIncomingIfId = 0, 279 teLinkOutgoingIfId = 3, 280 teLinkRowStatus = createAndGo(4), 281 teLinkStorageType = nonVolatile(3) 282 } 284 In ifStackTable: 285 { 286 ifStackHigherLayer = 2, 287 ifStackLowerLayer = 3, 288 ifStackStatus = createAndGo(4) 290 } 292 In teLinkTable: 293 { 294 ifIndex = 4, 295 teLinkAddressType = unknown(0), 296 teLinkLocalIpAddr = ''H, 297 teLinkRemoteIpAddr = ''H, 298 teLinkMetric = 5, 299 teLinkMuxCapability = lambdaSwitch(150), 300 teLinkProtectionType = unprotected(2), 301 teLinkWorkingPriority = 7, 302 teLinkResourceClass = 3, 303 teLinkIncomingIfId = 0, 304 teLinkOutgoingIfId = 4, 305 teLinkRowStatus = createAndGo(4), 306 teLinkStorageType = nonVolatile(3) 307 } 309 In ifStackTable: 310 { 311 ifStackHigherLayer = 2, 312 ifStackLowerLayer = 4, 313 ifStackStatus = createAndGo(4) 314 } 316 We assign SRLGs to the TE links. 318 In the teLinkSrlgTable: 319 { 320 ifIndex = 3, 321 teSrlg = 10, 322 teSrlgRowStatus = createAndGo(4), 323 teSrlgStorageType = nonVolatile(3) 324 } 326 In the teLinkSrlgTable: 327 { 328 ifIndex = 4, 329 teSrlg = 50, 330 teSrlgRowStatus = createAndGo(4), 331 teSrlgStorageType = nonVolatile(3) 332 } 334 The bundled link inherits the SRLG properties from the 335 associated TE links. 337 Next, for each unbundled TE link, a component link is created. 339 An ifEntry with the same ifIndex needs to be created beforehand. 341 In componentLinkTable: 342 { 343 ifIndex = 5, 344 componentLinkMuxCapability = lambdaSwitch(150), 345 componentLinkPreferredProtection = primary(1), 346 componentLinkRowStatus = createAndGo(4), 347 componentLinkStorageType = nonVolatile(3) 348 } 350 In ifStackTable: 351 { 352 ifStackHigherLayer = 3, 353 ifStackLowerLayer = 5, 354 ifStackStatus = createAndGo(4) 355 } 357 In componentLinkTable: 358 { 359 ifIndex = 6, 360 componentLinkMuxCapability = lambdaSwitch(150), 361 componentLinkPreferredProtection = secondary(2), 362 componentLinkRowStatus = createAndGo(4) 363 componentLinkStorageType = nonVolatile(3) 364 } 366 In ifStackTable: 367 { 368 ifStackHigherLayer = 4, 369 ifStackLowerLayer = 6, 370 ifStackStatus = createAndGo(4) 371 } 373 In this example, once a component link is added to the 374 componentLinkTable, the associated link descriptors are 375 implicitly added to the componentLinkDescriptorTable. 377 TE link link descriptors are derived from their component link 378 descriptors. 380 Note that the bandwidth attributes in teLinkDescriptorTable, 381 componentLinkDescriptorTable, teLinkBandwidthTable 382 and componentLinkBandwidthTable are maintained by the 383 device according to LSP creation/deletion at different priorities. 384 The values in the teLinkBandwidthTable are an aggregation 385 of the values for the component links of the TE links and 386 the TE links of the bundled link. 388 8. Application of the Interfaces Group to TE Links 390 The Interfaces Group [RFC2863] defines generic managed objects for 391 managing interfaces. This memo contains the media-specific 392 extensions to the Interfaces Group for managing TE Link interfaces 393 as logical interfaces. 395 This memo assumes the interpretation of the Interfaces Group to be 396 in accordance with [RFC2863] which states that the interfaces table 397 (ifTable) contains information on the managed resource's 398 interfaces and that each sub-layer below the internetwork layer of 399 a network interface is considered an interface. Thus, the TE Link 400 interface is represented as an entry in the ifTable. The inter- 401 relation of entries in the ifTable is defined by Interfaces Stack 402 Group defined in [RFC2863]. 404 When using TE Link interfaces, the interface stack table might appear 405 as follows: 407 +----------------------------------------+ 408 | TE link-interface ifType = teLink(200) + 409 +----------------------------------------+ 410 | Underlying Layer... + 411 +----------------------------------------+ 413 In the above diagram, "Underlying Layer..." refers to the ifIndex 414 of any interface type, which has been defined for TE Link 415 interworking. Examples include ATM, Frame Relay, Ethernet, etc. 417 8.1. Support of the TE Link Layer by ifTable 419 Some specific interpretations of ifTable for the TE Link layer 420 follow. 422 Object Use for the TE Link layer 424 ifIndex Each TE Link interface is represented by an ifEntry. 426 ifDescr Description of the TE Link interface. 428 ifType The value that is allocated for TE Link is 200 429 [IANAifType]. 431 ifSpeed The total bandwidth in bits per second for use by 432 the TE Link layer. 434 ifPhysAddress Unused. 436 ifAdminStatus This variable indicates the administrator's intent 437 as to whether TE Link should be enabled, disabled, or 438 running in some diagnostic testing mode on this 439 interface. Also see [RFC2863]. 441 ifOperStatus This value reflects the actual or operational 442 status of TE Link on this interface. 444 ifLastChange See [RFC2863]. 446 ifInOctets The number of received octets over the interface, 447 i.e., the number of received octets in all component 448 links associated with the interface. 450 ifOutOctets The number of transmitted octets over the 451 interface, i.e., the number of octets transmitted 452 over all component links associated with the 453 interface. 455 ifInErrors The number of packets dropped due to 456 uncorrectable errors. 458 ifInUnknownProtos 459 The number of received packets discarded during 460 packet header validation. 462 ifOutErrors See [RFC2863]. 464 ifName Textual name (unique on this system) of the 465 interface or an octet string of zero length. 467 ifLinkUpDownTrapEnable 468 Default is disabled (2). 470 ifConnectorPresent 471 Set to false (2). 473 ifHighSpeed See [RFC2863]. 475 ifHCInOctets The 64-bit version of ifInOctets; supported if 476 required by the compliance statements in [RFC2863]. 478 ifHCOutOctets The 64-bit version of ifOutOctets; supported if 479 required by the compliance statements in [RFC2863]. 481 ifAlias The non-volatile 'alias' name for the interface as 482 specified by a network manager. 484 ifCounterDiscontinuityTime 485 See [RFC2863]. 487 Support for ifInOctets, ifOutOctets, ifInErrors, ifInUnknownProtos, 488 ifOutErrors, ifHCInOctets and ifHCOutOctets objects is not required 489 if encoding type is clear. For other encoding types, traffic 490 counters on a TE link are cumulative for all subinterfaces which it 491 binds together. 493 8.2. Using ifStackTable 495 This section describes by example how to use ifStackTable to 496 represent the relationship of TE links with underlying TE-enabled 497 interfaces. Implementors of the stack table for TE link interfaces 498 should look at the appropriate RFC for the service being stacked 499 on TE links. Examples given below are for illustration purposes 500 only. 502 Example: MPLS is being carried on a bundled TE links. 503 The bundled TE link represents a 1:1 optical 504 transport interface. 506 In this example, the component link is a TE link. The two component 507 links/TE links are grouped in a bundled link. 509 +-------------------------------------------------------------------+ 510 | MPLS interface ifType = mpls(166) | 511 | ifIndex = 1 | 512 +-------------------------------------------------------------------+ 513 | TE link (bundled link) ifType = teLink(200) | 514 | ifIndex = 2 | 515 +--------------------------------+-+--------------------------------+ 516 | TE link ifType = teLink(200) | | TE link ifType = teLink(200) | 517 | ifIndex = 3 | | ifIndex = 4 | 518 +--------------------------------+ +--------------------------------+ 519 | Component link | | Component link | 520 | ifType = opticalTransport(196) | | ifType = opticalTransport(196) | 521 | ifIndex = 5 | | ifIndex = 6 | 522 +--------------------------------+ +--------------------------------+ 524 The assignment of the index values could for example be: 526 ifIndex Description 527 1 mpls (type 166) 528 2 teLink (type 200) 529 3 teLink (type 200) 530 4 teLink (type 200) 531 5 opticalTransport (type 196) 532 6 opticalTransport (type 196) 534 The ifStackTable is then used to show the relationships between the 535 various interfaces. 537 ifStackTable Entries 539 HigherLayer LowerLayer 540 0 1 541 1 2 542 2 3 543 2 4 544 3 5 545 4 6 546 5 0 547 6 0 549 In the case where MPLS is using a single TE link, then 550 the upper TE link layer (link bundle) is not required. 552 +-----------------------------------+ 553 | MPLS interface ifType = mpls(166) | 554 +-----------------------------------+ 555 | TE link ifType = teLink(200) | 556 +-----------------------------------+ 557 | Component link | 558 | ifType = opticalTransport(196) | 559 +-----------------------------------+ 561 The assignment of the index values could for example be: 563 ifIndex Description 564 1 mpls (type 166) 565 2 teLink (type 200) 566 3 opticalTransport (type 196) 568 The ifStackTable is then used to show the relationships between the 569 various interfaces. 571 ifStackTable Entries 573 HigherLayer LowerLayer 574 0 1 575 1 2 576 2 3 577 3 0 579 9. TE Link MIB Module Definitions 581 TE-LINK-STD-MIB DEFINITIONS ::= BEGIN 583 IMPORTS 584 MODULE-IDENTITY, OBJECT-TYPE, transmission, Unsigned32 585 FROM SNMPv2-SMI 587 MODULE-COMPLIANCE, OBJECT-GROUP 588 FROM SNMPv2-CONF 590 TEXTUAL-CONVENTION, RowStatus, StorageType 591 FROM SNMPv2-TC 593 InterfaceIndexOrZero, ifIndex 594 FROM IF-MIB 596 InetAddressType, InetAddress 597 FROM INET-ADDRESS-MIB; 599 teLinkStdMIB MODULE-IDENTITY 600 LAST-UPDATED "200305211200Z" -- 21 May 2003 12:00:00 EST 601 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 602 CONTACT-INFO 603 " Martin Dubuc 604 Email: dubuc.consulting@rogers.com 606 Sudheer Dharanikota 607 Email: sudheer@avici.com 609 Thomas D. Nadeau 610 Email: tnadeau@cisco.com 612 Jonathan P. Lang 613 Email: jplang@ieee.org 615 Comments about this document should be emailed directly to 616 the MPLS working group mailing list at mpls@uu.net." 618 DESCRIPTION 619 "Copyright (C) 2003 The Internet Society. This version of 620 this MIB module is part of RFC XXXX; see the RFC 621 itself for full legal notices. 623 This MIB module contains managed object definitions for 624 MPLS traffic engineering links as defined in 625 'Link Bundling in MPLS Traffic Engineering'." 627 -- Revision history. 628 REVISION 629 "200305211200Z" -- 21 May 2003 12:00:00 EST 630 DESCRIPTION 631 "Initial version published as RFC xxxx (to be assigned by RFC 632 Editor)" 633 ::= { transmission xxx } -- To be assigned by IANA (experimental 114 634 -- can be used in the interim) 636 -- Textual Conventions 638 TeLinkPriority ::= TEXTUAL-CONVENTION 639 DISPLAY-HINT "d" 640 STATUS current 641 DESCRIPTION 642 "This type is used to represent a priority. Each connection is 643 assigned a priority. This priority is used when accounting for 644 bandwidth on TE links or component links, for resource 645 allocation and for rerouting purposes. Value 0 is the highest 646 priority. Value 7 is the lowest priority." 647 SYNTAX Unsigned32 (0..7) 649 TeLinkProtection ::= TEXTUAL-CONVENTION 650 STATUS current 651 DESCRIPTION 652 "Link protection." 653 SYNTAX INTEGER { 654 primary(1), 655 secondary(2) 656 } 658 TeLinkSwitchingCapability ::= TEXTUAL-CONVENTION 659 STATUS current 660 DESCRIPTION 661 "Switching capability as specified in the 'OSPF Extensions in 662 Support of Generalized MPLS' document. The values specified in 663 this document are not contiguous." 664 SYNTAX INTEGER { 665 packetSwitch1(1), 666 packetSwitch2(2), 667 packetSwitch3(3), 668 packetSwitch4(4), 669 layer2Switch(51), 670 tdm(100), 671 lambdaSwitch(150), 672 fiberSwitch(200) 673 } 675 TeLinkEncodingType ::= TEXTUAL-CONVENTION 676 STATUS current 677 DESCRIPTION 678 "Link encoding type as specified in 'GMPLS Signaling Functional 679 Description' document. The values specified in this document are 680 not contiguous." 681 SYNTAX INTEGER { 682 packet(1), 683 ethernet(2), 684 ansiEtsiPdh(3), 685 sdhItuSonetAnsi(5), 686 digitalWrapper(7), 687 lambda(8), 688 fiber(9), 689 fiberChannel(11) 690 } 692 -- Top level components of this MIB module 694 -- Notifications 695 teLinkNotifications OBJECT IDENTIFIER ::= { teLinkStdMIB 0 } 696 -- Tables, Scalars 697 teLinkObjects OBJECT IDENTIFIER ::= { teLinkStdMIB 1 } 698 -- Conformance 699 teLinkConformance OBJECT IDENTIFIER ::= { teLinkStdMIB 2 } 701 -- TE Link Table 703 teLinkTable OBJECT-TYPE 704 SYNTAX SEQUENCE OF TeLinkEntry 705 MAX-ACCESS not-accessible 706 STATUS current 707 DESCRIPTION 708 "This table specifies the grouping of component links into 709 TE links and grouping of TE links into bundled links." 710 ::= { teLinkObjects 1 } 712 teLinkEntry OBJECT-TYPE 713 SYNTAX TeLinkEntry 714 MAX-ACCESS not-accessible 715 STATUS current 716 DESCRIPTION 717 "An entry in this table exists for each ifEntry with an 718 ifType of teLink(200), i.e. for every TE link. An ifEntry 719 in the ifTable must exist before a teLinkEntry is created with 720 the corresponding ifIndex. If a TE link entry in the ifTable is 721 destroyed, then so is the corresponding entry in the 722 teLinkTable. The administrative and operational status values 723 are controlled from the ifEntry." 724 INDEX { ifIndex } 725 ::= { teLinkTable 1 } 727 TeLinkEntry ::= SEQUENCE { 728 teLinkAddressType InetAddressType, 729 teLinkLocalIpAddr InetAddress, 730 teLinkRemoteIpAddr InetAddress, 731 teLinkMetric Unsigned32, 732 teLinkMuxCapability TeLinkSwitchingCapability, 733 teLinkProtectionType INTEGER, 734 teLinkWorkingPriority TeLinkPriority, 735 teLinkResourceClass Unsigned32, 736 teLinkIncomingIfId InterfaceIndexOrZero, 737 teLinkOutgoingIfId InterfaceIndexOrZero, 738 teLinkRowStatus RowStatus, 739 teLinkStorageType StorageType 740 } 742 teLinkAddressType OBJECT-TYPE 743 SYNTAX InetAddressType 744 MAX-ACCESS read-create 745 STATUS current 746 DESCRIPTION 747 "The type of Internet address for the TE link. Only IPv4, 748 IPv6 and unknown (for unnumbered links) need to be supported." 749 ::= { teLinkEntry 1 } 751 teLinkLocalIpAddr OBJECT-TYPE 752 SYNTAX InetAddress 753 MAX-ACCESS read-create 754 STATUS current 755 DESCRIPTION 756 "The local Internet address for numbered links. The type of this 757 address is determined by the value of the teLinkAddressType 758 object. 760 For IPv4 and IPv6 numbered links, this object represents the 761 local IP address associated with the TE link. For an 762 unnumbered link, the local address is of type unknown and this 763 object is set to the zero length string and the 764 teLinkOutgoingIfId object then identifies the unnumbered 765 address." 766 ::= { teLinkEntry 2 } 768 teLinkRemoteIpAddr OBJECT-TYPE 769 SYNTAX InetAddress 770 MAX-ACCESS read-create 771 STATUS current 772 DESCRIPTION 773 "The remote Internet address for numbered links. The type of 774 this address is determined by the value of the 775 teLinkAddressType object. 777 The remote IP address associated with the TE link (IPv4 and 778 IPv6 numbered links). For an unnumbered link, the remote 779 address is of type unknown and this object is set to the 780 zero length string and the teLinkIncomingIfId object then 781 identifies the unnumbered address." 782 ::= { teLinkEntry 3 } 784 teLinkMetric OBJECT-TYPE 785 SYNTAX Unsigned32 786 MAX-ACCESS read-create 787 STATUS current 788 DESCRIPTION 789 "The traffic engineering metric for the TE link is 790 derived from its component links. All component links 791 within the TE link must have the same traffic 792 engineering metric." 793 REFERENCE 794 "Link Bundling in MPLS Traffic Engineering, RFC xxxx" 795 -- RFC Editor to fill in RFC number that will be assigned to 796 -- [BUNDLING] 797 ::= { teLinkEntry 4 } 799 teLinkMuxCapability OBJECT-TYPE 800 SYNTAX TeLinkSwitchingCapability 801 MAX-ACCESS read-create 802 STATUS current 803 DESCRIPTION 804 "This attribute specifies link multiplex capability of the 805 TE link, which is derived from its component links. All 806 component links within the same TE link must have the 807 same link multiplex capability." 808 REFERENCE 809 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 810 -- RFC Editor to fill in RFC number that will be assigned to 811 -- [GMPLS-OSPF] 812 ::= { teLinkEntry 5 } 814 teLinkProtectionType OBJECT-TYPE 815 SYNTAX INTEGER { 816 extraTraffic(1), 817 unprotected(2), 818 shared(3), 819 dedicated1For1(4), 820 dedicated1Plus1(5), 821 enhanced(6) 822 } 823 MAX-ACCESS read-create 824 STATUS current 825 DESCRIPTION 826 "This attribute specifies link protection type of the 827 TE link. Description of the different protection types can be 828 found in the 'Routing Extensions in Support of Generalized 829 MPLS' document." 830 REFERENCE 831 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx and 832 Routing Extensions in Support of Generalized MPLS, RFC xxxx" 833 -- RFC Editor to fill in RFC number that will be assigned to 834 -- [GMPLS-OSPF] and [ROUTING] 835 ::= { teLinkEntry 6 } 837 teLinkWorkingPriority OBJECT-TYPE 838 SYNTAX TeLinkPriority 839 MAX-ACCESS read-create 840 STATUS current 841 DESCRIPTION 842 "This object represents a priority value such that a new 843 connection with a higher priority, i.e. numerically lower than 844 this value, is guaranteed to be setup on a primary link and 845 not on a secondary link." 846 REFERENCE 847 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 848 -- RFC Editor to fill in RFC number that will be assigned to 849 -- [GMPLS-OSPF] 850 ::= { teLinkEntry 7 } 852 teLinkResourceClass OBJECT-TYPE 853 SYNTAX Unsigned32 854 MAX-ACCESS read-create 855 STATUS current 856 DESCRIPTION 857 "This attribute specifies the TE link resource class. 858 The resource class is a 32 bit bitfield. The resource class for 859 a link bundle is derived from the resource class of its 860 TE links. All TE links within a link bundle must have the 861 same resource class. Encoding of the resource class is described 862 in the 'Traffic Engineering Extensions to OSPF Version 2' 863 document." 864 REFERENCE 865 "Link Bundling in MPLS Traffic Engineering, RFC xxxx and 866 Traffic Engineering Extensions to OSPF Version 2, RFC xxxx" 868 -- RFC Editor to fill in RFC number that will be assigned to 869 -- [BUNDLING] and [OSPF] 870 ::= { teLinkEntry 8 } 872 teLinkIncomingIfId OBJECT-TYPE 873 SYNTAX InterfaceIndexOrZero 874 MAX-ACCESS read-create 875 STATUS current 876 DESCRIPTION 877 "For unnumbered links, the incoming interface is set to the 878 outgoing interface identifier chosen by the neighboring LSR 879 for the reverse link corresponding to this TE link. For 880 numbered links, the address is stored in the teLinkRemoteIpAddr 881 instead." 882 REFERENCE 883 "Link Bundling in MPLS Traffic Engineering, RFC xxxx" 884 -- RFC Editor to fill in RFC number that will be assigned to 885 -- [BUNDLING] 886 ::= { teLinkEntry 9 } 888 teLinkOutgoingIfId OBJECT-TYPE 889 SYNTAX InterfaceIndexOrZero 890 MAX-ACCESS read-create 891 STATUS current 892 DESCRIPTION 893 "If the link is unnumbered, the outgoing interface identifier is 894 set to the outgoing interface identifier chosen for the TE link 895 by the advertising LSR. For numbered links, the address is 896 stored in the teLinkLocalIpAddr instead." 897 REFERENCE 898 "Link Bundling in MPLS Traffic Engineering, RFC xxxx" 899 -- RFC Editor to fill in RFC number that will be assigned to 900 -- [BUNDLING] 901 ::= { teLinkEntry 10 } 903 teLinkRowStatus OBJECT-TYPE 904 SYNTAX RowStatus 905 MAX-ACCESS read-create 906 STATUS current 907 DESCRIPTION 908 "This variable is used to create, modify, and/or 909 delete a row in this table. All read-create objects 910 can only be changed when teLinkRowStatus is notInService(2) 911 or notReady(3)." 912 ::= { teLinkEntry 11 } 914 teLinkStorageType OBJECT-TYPE 915 SYNTAX StorageType 916 MAX-ACCESS read-create 917 STATUS current 918 DESCRIPTION 919 "The storage type for this conceptual row in the 920 teLinkTable. Conceptual rows having the value 921 'permanent' need not allow write-access to any 922 columnar object in the row." 923 ::= { teLinkEntry 12 } 925 -- End of teLinkTable 927 -- TE Link Descriptor Table 929 teLinkDescriptorTable OBJECT-TYPE 930 SYNTAX SEQUENCE OF TeLinkDescriptorEntry 931 MAX-ACCESS not-accessible 932 STATUS current 933 DESCRIPTION 934 "This table specifies the link descriptors associated with the 935 TE links." 936 ::= { teLinkObjects 2 } 938 teLinkDescriptorEntry OBJECT-TYPE 939 SYNTAX TeLinkDescriptorEntry 940 MAX-ACCESS not-accessible 941 STATUS current 942 DESCRIPTION 943 "An entry in this table is created for every TE link descriptor. 944 An ifEntry in the ifTable must exist before a 945 teLinkDescriptorEntry using the same ifIndex is created. 946 ifType of ifEntry must be teLink(200). 947 If a TE link entry in the ifTable is destroyed, then so are all 948 entries in the teLinkDescriptorTable that use the ifIndex of 949 this TE link." 950 INDEX { ifIndex, teLinkDescriptorId } 951 ::= { teLinkDescriptorTable 1 } 953 TeLinkDescriptorEntry ::= SEQUENCE { 954 teLinkDescriptorId Unsigned32, 955 teLinkDescrEncodingType TeLinkEncodingType, 956 teLinkDescrPriority TeLinkPriority, 957 teLinkDescrMinResBandwidth Unsigned32, 958 teLinkDescrMaxResBandwidth Unsigned32, 959 teLinkDescrRowStatus RowStatus, 960 teLinkDescrStorageType StorageType 961 } 962 teLinkDescriptorId OBJECT-TYPE 963 SYNTAX Unsigned32 (1..4294967295) 964 MAX-ACCESS not-accessible 965 STATUS current 966 DESCRIPTION 967 "This object specifies the link descriptor identifier." 968 ::= { teLinkDescriptorEntry 1 } 970 teLinkDescrEncodingType OBJECT-TYPE 971 SYNTAX TeLinkEncodingType 972 MAX-ACCESS read-create 973 STATUS current 974 DESCRIPTION 975 "This attribute specifies the TE link encoding type." 976 REFERENCE 977 "Generalized MPLS Signaling Functional Description, RFC 3471" 978 ::= { teLinkDescriptorEntry 2 } 980 teLinkDescrPriority OBJECT-TYPE 981 SYNTAX TeLinkPriority 982 MAX-ACCESS read-create 983 STATUS current 984 DESCRIPTION 985 "This object specifies the lowest priority at which that link 986 encoding type is available." 987 REFERENCE 988 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 989 -- RFC Editor to fill in RFC number that will be assigned to 990 -- [GMPLS-OSPF] 991 ::= { teLinkDescriptorEntry 3 } 993 teLinkDescrMinResBandwidth OBJECT-TYPE 994 SYNTAX Unsigned32 995 UNITS "thousand bps" 996 MAX-ACCESS read-create 997 STATUS current 998 DESCRIPTION 999 "This attribute specifies the minimum reservable bandwidth on 1000 the TE link. This is derived from the union of the 1001 minimum reservable bandwidth of all the component links 1002 associated with the TE link that can be used to carry 1003 live traffic. This value is an estimate in units of 1,000 bits 1004 per second." 1005 REFERENCE 1006 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1007 -- RFC Editor to fill in RFC number that will be assigned to 1008 -- [GMPLS-OSPF] 1009 ::= { teLinkDescriptorEntry 4 } 1011 teLinkDescrMaxResBandwidth OBJECT-TYPE 1012 SYNTAX Unsigned32 1013 UNITS "thousand bps" 1014 MAX-ACCESS read-create 1015 STATUS current 1016 DESCRIPTION 1017 "This attribute specifies the maximum reservable bandwidth on 1018 the TE link. This is the union of the maximum reservable 1019 bandwidth of all the component links within the 1020 TE link that can be used to carry live traffic. This value 1021 is an estimate in units of 1,000 bits per second." 1022 REFERENCE 1023 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1024 -- RFC Editor to fill in RFC number that will be assigned to 1025 -- [GMPLS-OSPF] 1026 ::= { teLinkDescriptorEntry 5 } 1028 teLinkDescrRowStatus OBJECT-TYPE 1029 SYNTAX RowStatus 1030 MAX-ACCESS read-create 1031 STATUS current 1032 DESCRIPTION 1033 "This variable is used to create, modify, and/or 1034 delete a row in this table. No read-create object 1035 can changed if teLinkDescrRowStatus is in active(1) state." 1036 ::= { teLinkDescriptorEntry 6 } 1038 teLinkDescrStorageType OBJECT-TYPE 1039 SYNTAX StorageType 1040 MAX-ACCESS read-create 1041 STATUS current 1042 DESCRIPTION 1043 "The storage type for this conceptual row in the 1044 teLinkDescriptorTable. Conceptual rows having the value 1045 'permanent' need not allow write-access to any 1046 columnar object in the row." 1047 ::= { teLinkDescriptorEntry 7 } 1049 -- End of teLinkDescriptorTable 1051 -- TE Link Shared Risk Link Group Table 1053 teLinkSrlgTable OBJECT-TYPE 1054 SYNTAX SEQUENCE OF TeLinkSrlgEntry 1055 MAX-ACCESS not-accessible 1056 STATUS current 1057 DESCRIPTION 1058 "This table specifies the SRLGs associated with TE links." 1059 ::= { teLinkObjects 3 } 1061 teLinkSrlgEntry OBJECT-TYPE 1062 SYNTAX TeLinkSrlgEntry 1063 MAX-ACCESS not-accessible 1064 STATUS current 1065 DESCRIPTION 1066 "An entry in this table contains information about a 1067 SRLG associated with a TE link. 1068 An ifEntry in the ifTable must exist before a 1069 teLinkSrlgEntry using the same ifIndex is created. 1070 ifType of ifEntry must be teLink(200). 1071 If a TE link entry in the ifTable is destroyed, then so are all 1072 entries in the teLinkSrlgTable that use the ifIndex of 1073 this TE link." 1074 INDEX { ifIndex, teSrlg } 1075 ::= { teLinkSrlgTable 1 } 1077 TeLinkSrlgEntry ::= SEQUENCE { 1078 teSrlg Unsigned32, 1079 teSrlgRowStatus RowStatus, 1080 teSrlgStorageType StorageType 1081 } 1083 teSrlg OBJECT-TYPE 1084 SYNTAX Unsigned32 (0..4294967295) 1085 MAX-ACCESS not-accessible 1086 STATUS current 1087 DESCRIPTION 1088 "This identifies a SRLG supported by the TE link. An SRLG is 1089 identified with a 32 bit number that is unique within an IGP 1090 domain. Zero is a valid SRLG number." 1091 REFERENCE 1092 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1093 -- RFC Editor to fill in RFC number that will be assigned to 1094 -- [GMPLS-OSPF] 1095 ::= { teLinkSrlgEntry 1 } 1097 teSrlgRowStatus OBJECT-TYPE 1098 SYNTAX RowStatus 1099 MAX-ACCESS read-create 1100 STATUS current 1101 DESCRIPTION 1102 "This variable is used to create, modify, and/or 1103 delete a row in this table. No read-create object can 1104 be modified if teSrlgRowStatus is active(1)." 1105 ::= { teLinkSrlgEntry 2 } 1107 teSrlgStorageType OBJECT-TYPE 1108 SYNTAX StorageType 1109 MAX-ACCESS read-create 1110 STATUS current 1111 DESCRIPTION 1112 "The storage type for this conceptual row in the 1113 teLinkSrlgTable. Conceptual rows having the value 1114 'permanent' need not allow write-access to any 1115 columnar object in the row." 1116 ::= { teLinkSrlgEntry 3 } 1118 -- End of teLinkSrlgTable 1120 -- TE Link Bandwidth Table 1122 teLinkBandwidthTable OBJECT-TYPE 1123 SYNTAX SEQUENCE OF TeLinkBandwidthEntry 1124 MAX-ACCESS not-accessible 1125 STATUS current 1126 DESCRIPTION 1127 "This table specifies the priority-based bandwidth table 1128 for TE links." 1129 ::= { teLinkObjects 4 } 1131 teLinkBandwidthEntry OBJECT-TYPE 1132 SYNTAX TeLinkBandwidthEntry 1133 MAX-ACCESS not-accessible 1134 STATUS current 1135 DESCRIPTION 1136 "An entry in this table contains information about 1137 the priority-based bandwidth of TE links. An ifEntry in the 1138 ifTable must exist before a teLinkBandwidthEntry using the 1139 same ifIndex is created. ifType of ifEntry must be teLink(200). 1140 If a TE link entry in the ifTable is destroyed, then so are 1141 all entries in the teLinkBandwidthTable that use the ifIndex of 1142 this TE link." 1143 INDEX { ifIndex, teLinkBandwidthPriority } 1144 ::= { teLinkBandwidthTable 1 } 1146 TeLinkBandwidthEntry ::= SEQUENCE { 1147 teLinkBandwidthPriority TeLinkPriority, 1148 teLinkUnreservedBandwidth Unsigned32, 1149 teLinkMaximumLspBandwidth Unsigned32, 1150 teLinkBandwidthRowStatus RowStatus, 1151 teLinkBandwidthStorageType StorageType 1152 } 1153 teLinkBandwidthPriority OBJECT-TYPE 1154 SYNTAX TeLinkPriority 1155 MAX-ACCESS not-accessible 1156 STATUS current 1157 DESCRIPTION 1158 "This attribute specifies the priority. A value of 0 is valid 1159 as specified in the 'Traffic Engineering Extensions to OSPF 1160 Version 2' document." 1161 REFERENCE 1162 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx and 1163 Traffic Engineering Extensions to OSPF Version 2, RFC xxxx" 1164 -- RFC Editor to fill in RFC number that will be assigned to 1165 -- [GMPLS-OSPF] and [OSPF] 1166 ::= { teLinkBandwidthEntry 1 } 1168 teLinkUnreservedBandwidth OBJECT-TYPE 1169 SYNTAX Unsigned32 1170 UNITS "thousand bps" 1171 MAX-ACCESS read-only 1172 STATUS current 1173 DESCRIPTION 1174 "This attribute specifies the TE link unreserved 1175 bandwidth at priority p. It is the sum of the unreserved 1176 bandwidths at priority p of all component links associated 1177 with the TE link (excludes all links that are strictly 1178 used as protecting links). This value is an estimate in units 1179 of 1,000 bits per second." 1180 REFERENCE 1181 "Link Bundling in MPLS Traffic Engineering, RFC xxxx" 1182 -- RFC Editor to fill in RFC number that will be assigned to 1183 -- [BUNDLING] 1184 ::= { teLinkBandwidthEntry 2 } 1186 teLinkMaximumLspBandwidth OBJECT-TYPE 1187 SYNTAX Unsigned32 1188 UNITS "thousand bps" 1189 MAX-ACCESS read-create 1190 STATUS current 1191 DESCRIPTION 1192 "This attribute specifies the TE link maximum 1193 LSP bandwidth at priority p. It is the maximum of all 1194 maximum LSP bandwidth at priority p of the component links 1195 associated with the TE link (excludes all links that are 1196 strictly used as protecting links). This value is an estimate 1197 in units of 1,000 bits per second." 1198 REFERENCE 1199 "Link Bundling in MPLS Traffic Engineering, RFC xxxx" 1200 -- RFC Editor to fill in RFC number that will be assigned to 1201 -- [BUNDLING] 1202 ::= { teLinkBandwidthEntry 3 } 1204 teLinkBandwidthRowStatus OBJECT-TYPE 1205 SYNTAX RowStatus 1206 MAX-ACCESS read-create 1207 STATUS current 1208 DESCRIPTION 1209 "This variable is used to create, modify, and/or 1210 delete a row in this table. No read-create object 1211 can be modified when teLinkBandwidthRowStatus is active(1)." 1212 ::= { teLinkBandwidthEntry 4 } 1214 teLinkBandwidthStorageType OBJECT-TYPE 1215 SYNTAX StorageType 1216 MAX-ACCESS read-create 1217 STATUS current 1218 DESCRIPTION 1219 "The storage type for this conceptual row in the 1220 teLinkBandwidthTable. Conceptual rows having the value 1221 'permanent' need not allow write-access to any 1222 columnar object in the row." 1223 ::= { teLinkBandwidthEntry 5 } 1225 -- End of teLinkBandwidthTable 1227 -- Component Link Table 1229 componentLinkTable OBJECT-TYPE 1230 SYNTAX SEQUENCE OF ComponentLinkEntry 1231 MAX-ACCESS not-accessible 1232 STATUS current 1233 DESCRIPTION 1234 "This table specifies the component link parameters." 1235 ::= { teLinkObjects 5 } 1237 componentLinkEntry OBJECT-TYPE 1238 SYNTAX ComponentLinkEntry 1239 MAX-ACCESS not-accessible 1240 STATUS current 1241 DESCRIPTION 1242 "An entry in this table exists for each ifEntry that represents 1243 a component link. An ifEntry must exist in the ifTable 1244 before a componentLinkEntry is created with the 1245 corresponding ifIndex. ifEntry's ifType can be 1246 of any interface type which has been defined for TE Link 1247 interworking. Examples include ATM, Frame Relay, Ethernet, etc. 1249 If an entry representing a component link is destroyed in the 1250 ifTable, then so is the corresponding entry in the 1251 componentLinkTable. The administrative and operational status 1252 values are controlled from the ifEntry." 1253 INDEX { ifIndex } 1254 ::= { componentLinkTable 1 } 1256 ComponentLinkEntry ::= SEQUENCE { 1257 componentLinkMuxCapability TeLinkSwitchingCapability, 1258 componentLinkPreferredProtection TeLinkProtection, 1259 componentLinkCurrentProtection TeLinkProtection, 1260 componentLinkRowStatus RowStatus, 1261 componentLinkStorageType StorageType 1262 } 1264 componentLinkMuxCapability OBJECT-TYPE 1265 SYNTAX TeLinkSwitchingCapability 1266 MAX-ACCESS read-create 1267 STATUS current 1268 DESCRIPTION 1269 "This attribute specifies link multiplexing capabilities of the 1270 component link." 1271 REFERENCE 1272 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1273 -- RFC Editor to fill in RFC number that will be assigned to 1274 -- [GMPLS-OSPF] 1275 ::= { componentLinkEntry 1 } 1277 componentLinkPreferredProtection OBJECT-TYPE 1278 SYNTAX TeLinkProtection 1279 MAX-ACCESS read-create 1280 STATUS current 1281 DESCRIPTION 1282 "This attribute specifies whether this component link is 1283 a primary or secondary entity." 1284 ::= { componentLinkEntry 2 } 1286 componentLinkCurrentProtection OBJECT-TYPE 1287 SYNTAX TeLinkProtection 1288 MAX-ACCESS read-only 1289 STATUS current 1290 DESCRIPTION 1291 "This attribute specifies whether this component link is 1292 currently used as primary or secondary link." 1293 ::= { componentLinkEntry 3 } 1295 componentLinkRowStatus OBJECT-TYPE 1296 SYNTAX RowStatus 1297 MAX-ACCESS read-create 1298 STATUS current 1299 DESCRIPTION 1300 "This variable is used to create, modify, and/or 1301 delete a row in this table. No read-create object 1302 can be modified when componentLinkRowStatus is active(1)." 1303 ::= { componentLinkEntry 4 } 1305 componentLinkStorageType OBJECT-TYPE 1306 SYNTAX StorageType 1307 MAX-ACCESS read-create 1308 STATUS current 1309 DESCRIPTION 1310 "The storage type for this conceptual row in the 1311 componentLinkTable. Conceptual rows having the value 1312 'permanent' need not allow write-access to any 1313 columnar object in the row." 1314 ::= { componentLinkEntry 5 } 1316 -- End of componentLinkTable 1318 -- Component Link Descriptor Table 1320 componentLinkDescriptorTable OBJECT-TYPE 1321 SYNTAX SEQUENCE OF ComponentLinkDescriptorEntry 1322 MAX-ACCESS not-accessible 1323 STATUS current 1324 DESCRIPTION 1325 "This table specifies the link descriptors associated with the 1326 component links." 1327 ::= { teLinkObjects 6 } 1329 componentLinkDescriptorEntry OBJECT-TYPE 1330 SYNTAX ComponentLinkDescriptorEntry 1331 MAX-ACCESS not-accessible 1332 STATUS current 1333 DESCRIPTION 1334 "An entry in this table is created for every component link 1335 descriptor. An ifEntry in the ifTable must exist before a 1336 componentLinkDescriptorEntry using the same ifIndex is created. 1337 ifEntry's ifType can be of any interface type which has been 1338 defined for TE Link interworking. Examples include ATM, Frame 1339 Relay, Ethernet, etc. If a component link entry in the ifTable 1340 is destroyed, then so are all entries in the 1341 componentLinkDescriptorTable that use the ifIndex of this 1342 component link." 1343 INDEX { ifIndex, componentLinkDescrId } 1344 ::= { componentLinkDescriptorTable 1 } 1346 ComponentLinkDescriptorEntry ::= SEQUENCE { 1347 componentLinkDescrId Unsigned32, 1348 componentLinkDescrEncodingType TeLinkEncodingType, 1349 componentLinkDescrPriority TeLinkPriority, 1350 componentLinkDescrMinBandwidth Unsigned32, 1351 componentLinkDescrMaxBandwidth Unsigned32, 1352 componentLinkDescrRowStatus RowStatus, 1353 componentLinkDescrStorageType StorageType 1354 } 1356 componentLinkDescrId OBJECT-TYPE 1357 SYNTAX Unsigned32 (1..4294967295) 1358 MAX-ACCESS not-accessible 1359 STATUS current 1360 DESCRIPTION 1361 "This object specifies the link descriptor identifier." 1362 ::= { componentLinkDescriptorEntry 1 } 1364 componentLinkDescrEncodingType OBJECT-TYPE 1365 SYNTAX TeLinkEncodingType 1366 MAX-ACCESS read-create 1367 STATUS current 1368 DESCRIPTION 1369 "This attribute specifies the component link encoding type." 1370 REFERENCE 1371 "Generalized MPLS Signaling Functional Description, RFC 3471" 1372 ::= { componentLinkDescriptorEntry 2 } 1374 componentLinkDescrPriority OBJECT-TYPE 1375 SYNTAX TeLinkPriority 1376 MAX-ACCESS read-create 1377 STATUS current 1378 DESCRIPTION 1379 "This object specifies the lowest priority at which that link 1380 encoding type is available for the component link." 1381 REFERENCE 1382 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1383 -- RFC Editor to fill in RFC number that will be assigned to 1384 -- [GMPLS-OSPF] 1385 ::= { componentLinkDescriptorEntry 3 } 1387 componentLinkDescrMinBandwidth OBJECT-TYPE 1388 SYNTAX Unsigned32 1389 UNITS "thousand bps" 1390 MAX-ACCESS read-create 1391 STATUS current 1392 DESCRIPTION 1393 "This attribute specifies the minimum reservable bandwidth on 1394 the component link. This value is an estimate 1395 in units of 1,000 bits per second." 1396 REFERENCE 1397 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1398 -- RFC Editor to fill in RFC number that will be assigned to 1399 -- [GMPLS-OSPF] 1400 ::= { componentLinkDescriptorEntry 4 } 1402 componentLinkDescrMaxBandwidth OBJECT-TYPE 1403 SYNTAX Unsigned32 1404 UNITS "thousand bps" 1405 MAX-ACCESS read-create 1406 STATUS current 1407 DESCRIPTION 1408 "This attribute specifies the maximum reservable bandwidth on 1409 the component link. This value is an estimate 1410 in units of 1,000 bits per second." 1411 REFERENCE 1412 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1413 -- RFC Editor to fill in RFC number that will be assigned to 1414 -- [GMPLS-OSPF] 1415 ::= { componentLinkDescriptorEntry 5 } 1417 componentLinkDescrRowStatus OBJECT-TYPE 1418 SYNTAX RowStatus 1419 MAX-ACCESS read-create 1420 STATUS current 1421 DESCRIPTION 1422 "This variable is used to create, modify, and/or 1423 delete a row in this table. No read-create object 1424 can be modified when componentLinkDescrRowStatus 1425 is active(1)." 1426 ::= { componentLinkDescriptorEntry 6 } 1428 componentLinkDescrStorageType OBJECT-TYPE 1429 SYNTAX StorageType 1430 MAX-ACCESS read-create 1431 STATUS current 1432 DESCRIPTION 1433 "The storage type for this conceptual row in the 1434 componentLinkDescriptorTable. Conceptual rows 1435 having the value 'permanent' need not allow write-access 1436 to any columnar object in the row." 1437 ::= { componentLinkDescriptorEntry 7 } 1439 -- End of componentLinkDescriptorTable 1440 -- Component Link Bandwidth Table 1442 componentLinkBandwidthTable OBJECT-TYPE 1443 SYNTAX SEQUENCE OF ComponentLinkBandwidthEntry 1444 MAX-ACCESS not-accessible 1445 STATUS current 1446 DESCRIPTION 1447 "This table specifies the priority-based bandwidth 1448 for component links." 1449 ::= { teLinkObjects 7 } 1451 componentLinkBandwidthEntry OBJECT-TYPE 1452 SYNTAX ComponentLinkBandwidthEntry 1453 MAX-ACCESS not-accessible 1454 STATUS current 1455 DESCRIPTION 1456 "An entry in this table contains information about 1457 the priority-based bandwidth on component links. 1458 An ifEntry in the ifTable must exist before a 1459 componentLinkBandwidthEntry using the same ifIndex is 1460 created. ifEntry's ifType can be of any interface type which 1461 has been defined for TE Link interworking. Examples include 1462 ATM, Frame Relay, Ethernet, etc. If a component link entry in 1463 the ifTable is destroyed, then so are all entries in the 1464 componentLinkBandwidthTable that use the ifIndex of 1465 this component link." 1466 INDEX { ifIndex, componentLinkPriority } 1467 ::= { componentLinkBandwidthTable 1 } 1469 ComponentLinkBandwidthEntry ::= SEQUENCE { 1470 componentLinkPriority TeLinkPriority, 1471 componentLinkUnreservedBandwidth Unsigned32, 1472 componentLinkMaximumLspBandwidth Unsigned32, 1473 componentLinkBandwidthRowStatus RowStatus, 1474 componentLinkBwStorageType StorageType 1475 } 1477 componentLinkPriority OBJECT-TYPE 1478 SYNTAX TeLinkPriority 1479 MAX-ACCESS not-accessible 1480 STATUS current 1481 DESCRIPTION 1482 "This attribute specifies the priority. A value of 0 is valid 1483 as specified in the 'Traffic Engineering Extensions to OSPF 1484 Version 2' document." 1485 REFERENCE 1486 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx and 1487 Traffic Engineering Extensions to OSPF Version 2, RFC xxxx" 1489 -- RFC Editor to fill in RFC number that will be assigned to 1490 -- [GMPLS-OSPF] and [OSPF] 1491 ::= { componentLinkBandwidthEntry 1 } 1493 componentLinkUnreservedBandwidth OBJECT-TYPE 1494 SYNTAX Unsigned32 1495 UNITS "thousand bps" 1496 MAX-ACCESS read-only 1497 STATUS current 1498 DESCRIPTION 1499 "This attribute specifies the component link unreserved 1500 bandwidth at priority p. This value is an estimate 1501 in units of 1,000 bits per second." 1502 REFERENCE 1503 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1504 -- RFC Editor to fill in RFC number that will be assigned to 1505 -- [GMPLS-OSPF] 1506 ::= { componentLinkBandwidthEntry 2 } 1508 componentLinkMaximumLspBandwidth OBJECT-TYPE 1509 SYNTAX Unsigned32 1510 UNITS "thousand bps" 1511 MAX-ACCESS read-create 1512 STATUS current 1513 DESCRIPTION 1514 "This attribute specifies the component link maximum 1515 LSP bandwidth at priority p. This value is an estimate 1516 in units of 1,000 bits per second." 1517 REFERENCE 1518 "OSPF Extensions in Support of Generalized MPLS, RFC xxxx" 1519 -- RFC Editor to fill in RFC number that will be assigned to 1520 -- [GMPLS-OSPF] 1521 ::= { componentLinkBandwidthEntry 3 } 1523 componentLinkBandwidthRowStatus OBJECT-TYPE 1524 SYNTAX RowStatus 1525 MAX-ACCESS read-create 1526 STATUS current 1527 DESCRIPTION 1528 "This variable is used to create, modify, and/or 1529 delete a row in this table. No read-create object can 1530 be modified when componentLinkBandwidthRowStatus is 1531 active(1)." 1532 ::= { componentLinkBandwidthEntry 4 } 1534 componentLinkBwStorageType OBJECT-TYPE 1535 SYNTAX StorageType 1536 MAX-ACCESS read-create 1537 STATUS current 1538 DESCRIPTION 1539 "The storage type for this conceptual row in the 1540 componentLinkBandwidthTable. Conceptual rows 1541 having the value 'permanent' need not allow write-access 1542 to any columnar object in the row." 1543 ::= { componentLinkBandwidthEntry 5 } 1545 -- End of componentLinkBandwidthTable 1547 -- Module compliance 1549 teLinkGroups 1550 OBJECT IDENTIFIER ::= { teLinkConformance 1 } 1552 teLinkCompliances 1553 OBJECT IDENTIFIER ::= { teLinkConformance 2 } 1555 teLinkModuleFullCompliance MODULE-COMPLIANCE 1556 STATUS current 1557 DESCRIPTION 1558 "Compliance statement for agents that support the 1559 configuration and monitoring of TE Link MIB module." 1560 MODULE -- this module 1562 MANDATORY-GROUPS { teLinkGroup, 1563 teLinkBandwidthGroup, 1564 componentLinkBandwidthGroup } 1566 GROUP teLinkSrlgGroup 1567 DESCRIPTION 1568 "This group is mandatory for G-MPLS enabled devices." 1570 -- teLinkTable 1572 OBJECT teLinkAddressType 1573 SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } 1574 DESCRIPTION 1575 "Only ipv4(1) and ipv6(2) address types need to be 1576 supported for numbered links. For unnumbered links, the 1577 unknown(0) address type needs to be supported." 1579 OBJECT teLinkLocalIpAddr 1580 SYNTAX InetAddress (SIZE(0|4|16)) 1581 DESCRIPTION 1582 "Size of TE link IP address depends on type of TE link. 1583 TE link IP address size is zero if link is unnumbered, 1584 four if link IP address is IPv4 and sixteen if link IP 1585 address is IPv6." 1587 OBJECT teLinkRemoteIpAddr 1588 SYNTAX InetAddress (SIZE(0|4|16)) 1589 DESCRIPTION 1590 "Size of TE link IP address depends on type of TE link. 1591 TE link IP address size is zero if link is unnumbered, 1592 four if link IP address is IPv4 and sixteen if link IP 1593 address is IPv6." 1595 OBJECT teLinkRowStatus 1596 SYNTAX INTEGER { active(1), notInService(2), 1597 createAndGo(4), destroy(6) } 1598 DESCRIPTION 1599 "The notReady(3) and createAndWait(5) states need 1600 not be supported." 1602 -- teLinkDescriptorTable 1604 OBJECT teLinkDescrRowStatus 1605 SYNTAX INTEGER { active(1), notInService(2), 1606 createAndGo(4), destroy(6) } 1607 DESCRIPTION 1608 "The notReady(3) and createAndWait(5) states need 1609 not be supported." 1611 OBJECT teLinkDescrStorageType 1612 MIN-ACCESS read-only 1613 DESCRIPTION 1614 "Write access is not required." 1616 -- teLinkSrlgTable 1618 OBJECT teSrlgRowStatus 1619 SYNTAX INTEGER { active(1), notInService(2), 1620 createAndGo(4), destroy(6) } 1621 DESCRIPTION 1622 "The notReady(3) and createAndWait(5) states need 1623 not be supported." 1625 -- teLinkBandwidthTable 1627 OBJECT teLinkBandwidthRowStatus 1628 SYNTAX INTEGER { active(1), notInService(2), 1629 createAndGo(4), destroy(6) } 1630 DESCRIPTION 1631 "The notReady(3) and createAndWait(5) states need 1632 not be supported." 1634 -- componentLinkTable 1636 OBJECT componentLinkRowStatus 1637 SYNTAX INTEGER { active(1), notInService(2), 1638 createAndGo(4), destroy(6) } 1639 DESCRIPTION 1640 "The notReady(3) and createAndWait(5) states need 1641 not be supported." 1643 -- componentLinkDescriptorTable 1645 OBJECT componentLinkDescrRowStatus 1646 SYNTAX INTEGER { active(1), notInService(2), 1647 createAndGo(4), destroy(6) } 1648 DESCRIPTION 1649 "The notReady(3) and createAndWait(5) states need 1650 not be supported." 1652 -- componentLinkBandwidthTable 1654 OBJECT componentLinkBandwidthRowStatus 1655 SYNTAX INTEGER { active(1), notInService(2), 1656 createAndGo(4), destroy(6) } 1657 DESCRIPTION 1658 "The notReady(3) and createAndWait(5) states need 1659 not be supported." 1661 ::= { teLinkCompliances 1 } 1663 teLinkModuleReadOnlyCompliance MODULE-COMPLIANCE 1664 STATUS current 1665 DESCRIPTION 1666 "Compliance statement for agents that support the 1667 monitoring of TE link MIB module." 1668 MODULE -- this module 1670 -- The mandatory groups have to be implemented 1671 -- by all devices supporting TE links. However, they may all 1672 -- be supported as read-only objects in the case where manual 1673 -- configuration is unsupported. 1675 MANDATORY-GROUPS { teLinkGroup, 1676 teLinkBandwidthGroup, 1677 componentLinkBandwidthGroup } 1679 GROUP teLinkSrlgGroup 1680 DESCRIPTION 1681 "This group is mandatory for G-MPLS enabled devices." 1683 -- teLinkTable 1685 OBJECT teLinkAddressType 1686 SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } 1687 MIN-ACCESS read-only 1688 DESCRIPTION 1689 "Only ipv4(1) and ipv6(2) address types need to be 1690 supported for numbered links. For unnumbered links, the 1691 unknown(0) address type needs to be supported." 1693 OBJECT teLinkLocalIpAddr 1694 SYNTAX InetAddress (SIZE(0|4|16)) 1695 MIN-ACCESS read-only 1696 DESCRIPTION 1697 "Size of TE link IP address depends on type of TE link. 1698 TE link IP address size is zero if link is unnumbered, 1699 four if link IP address is IPv4 and sixteen if link IP 1700 address is IPv6." 1702 OBJECT teLinkRemoteIpAddr 1703 SYNTAX InetAddress (SIZE(0|4|16)) 1704 MIN-ACCESS read-only 1705 DESCRIPTION 1706 "Size of TE link IP address depends on type of TE link. 1707 TE link IP address size is zero if link is unnumbered, 1708 four if link IP address is IPv4 and sixteen if link IP 1709 address is IPv6." 1711 OBJECT teLinkMuxCapability 1712 MIN-ACCESS read-only 1713 DESCRIPTION 1714 "Write access is not required." 1716 OBJECT teLinkProtectionType 1717 MIN-ACCESS read-only 1718 DESCRIPTION 1719 "Write access is not required." 1721 OBJECT teLinkWorkingPriority 1722 MIN-ACCESS read-only 1723 DESCRIPTION 1724 "Write access is not required." 1726 OBJECT teLinkRowStatus 1727 SYNTAX INTEGER { active(1) } 1728 MIN-ACCESS read-only 1729 DESCRIPTION 1730 "Write access is not required and active(1) is the 1731 only status that needs to be supported." 1733 OBJECT teLinkStorageType 1734 MIN-ACCESS read-only 1735 DESCRIPTION 1736 "Write access is not required." 1738 -- teLinkDescriptorTable 1740 OBJECT teLinkDescrEncodingType 1741 MIN-ACCESS read-only 1742 DESCRIPTION 1743 "Write access is not required." 1745 OBJECT teLinkDescrPriority 1746 MIN-ACCESS read-only 1747 DESCRIPTION 1748 "Write access is not required." 1750 OBJECT teLinkDescrMinResBandwidth 1751 MIN-ACCESS read-only 1752 DESCRIPTION 1753 "Write access is not required." 1755 OBJECT teLinkDescrMaxResBandwidth 1756 MIN-ACCESS read-only 1757 DESCRIPTION 1758 "Write access is not required." 1760 OBJECT teLinkDescrRowStatus 1761 SYNTAX INTEGER { active(1) } 1762 MIN-ACCESS read-only 1763 DESCRIPTION 1764 "Write access is not required and active(1) is the 1765 only status that needs to be supported." 1767 OBJECT teLinkDescrStorageType 1768 MIN-ACCESS read-only 1769 DESCRIPTION 1770 "Write access is not required." 1772 -- teLinkSrlgTable 1774 OBJECT teSrlgRowStatus 1775 SYNTAX INTEGER { active(1) } 1776 MIN-ACCESS read-only 1777 DESCRIPTION 1778 "Write access is not required and active(1) is the 1779 only status that needs to be supported." 1781 OBJECT teSrlgStorageType 1782 MIN-ACCESS read-only 1783 DESCRIPTION 1784 "Write access is not required." 1786 -- teLinkBandwidthTable 1788 OBJECT teLinkMaximumLspBandwidth 1789 MIN-ACCESS read-only 1790 DESCRIPTION 1791 "Write access is not required." 1793 OBJECT teLinkBandwidthRowStatus 1794 SYNTAX INTEGER { active(1) } 1795 MIN-ACCESS read-only 1796 DESCRIPTION 1797 "Write access is not required and active(1) is the 1798 only status that needs to be supported." 1800 OBJECT teLinkBandwidthStorageType 1801 MIN-ACCESS read-only 1802 DESCRIPTION 1803 "Write access is not required." 1805 -- componentLinkTable 1807 OBJECT componentLinkMuxCapability 1808 MIN-ACCESS read-only 1809 DESCRIPTION 1810 "Write access is not required." 1812 OBJECT componentLinkPreferredProtection 1813 MIN-ACCESS read-only 1814 DESCRIPTION 1815 "Write access is not required." 1817 OBJECT componentLinkRowStatus 1818 SYNTAX INTEGER { active(1) } 1819 MIN-ACCESS read-only 1820 DESCRIPTION 1821 "Write access is not required and active(1) is the 1822 only status that needs to be supported." 1824 OBJECT componentLinkStorageType 1825 MIN-ACCESS read-only 1826 DESCRIPTION 1827 "Write access is not required." 1829 -- componentLinkDescriptorTable 1831 OBJECT componentLinkDescrEncodingType 1832 MIN-ACCESS read-only 1833 DESCRIPTION 1834 "Write access is not required." 1836 OBJECT componentLinkDescrPriority 1837 MIN-ACCESS read-only 1838 DESCRIPTION 1839 "Write access is not required." 1841 OBJECT componentLinkDescrMinBandwidth 1842 MIN-ACCESS read-only 1843 DESCRIPTION 1844 "Write access is not required." 1846 OBJECT componentLinkDescrMaxBandwidth 1847 MIN-ACCESS read-only 1848 DESCRIPTION 1849 "Write access is not required." 1851 OBJECT componentLinkDescrRowStatus 1852 SYNTAX INTEGER { active(1) } 1853 MIN-ACCESS read-only 1854 DESCRIPTION 1855 "Write access is not required and active(1) is the 1856 only status that needs to be supported." 1858 OBJECT componentLinkDescrStorageType 1859 MIN-ACCESS read-only 1860 DESCRIPTION 1861 "Write access is not required." 1863 -- componentLinkBandwidthTable 1865 OBJECT componentLinkMaximumLspBandwidth 1866 MIN-ACCESS read-only 1867 DESCRIPTION 1868 "Write access is not required." 1870 OBJECT componentLinkBandwidthRowStatus 1871 SYNTAX INTEGER { active(1) } 1872 MIN-ACCESS read-only 1873 DESCRIPTION 1874 "Write access is not required and active(1) is the 1875 only status that needs to be supported." 1877 OBJECT componentLinkBwStorageType 1878 MIN-ACCESS read-only 1879 DESCRIPTION 1880 "Write access is not required." 1882 ::= { teLinkCompliances 2 } 1884 -- Units of conformance 1886 teLinkGroup OBJECT-GROUP 1887 OBJECTS { teLinkAddressType, 1888 teLinkLocalIpAddr, 1889 teLinkRemoteIpAddr, 1890 teLinkMetric, 1891 teLinkMuxCapability, 1892 teLinkProtectionType, 1893 teLinkWorkingPriority, 1894 teLinkResourceClass, 1895 teLinkIncomingIfId, 1896 teLinkOutgoingIfId, 1897 teLinkRowStatus, 1898 teLinkStorageType, 1899 teLinkDescrEncodingType, 1900 teLinkDescrPriority, 1901 teLinkDescrMinResBandwidth, 1902 teLinkDescrMaxResBandwidth, 1903 teLinkDescrRowStatus, 1904 teLinkDescrStorageType, 1905 componentLinkMuxCapability, 1906 componentLinkPreferredProtection, 1907 componentLinkCurrentProtection, 1908 componentLinkRowStatus, 1909 componentLinkStorageType 1910 } 1912 STATUS current 1913 DESCRIPTION 1914 "Collection of objects needed for the monitoring of 1915 resources associated with TE links." 1916 ::= { teLinkGroups 1 } 1918 teLinkSrlgGroup OBJECT-GROUP 1919 OBJECTS { teSrlgRowStatus, 1920 teSrlgStorageType 1921 } 1923 STATUS current 1924 DESCRIPTION 1925 "Collection of objects needed for the monitoring of 1926 SRLG resources associated with TE links." 1927 ::= { teLinkGroups 2 } 1929 teLinkBandwidthGroup OBJECT-GROUP 1930 OBJECTS { teLinkUnreservedBandwidth, 1931 teLinkMaximumLspBandwidth, 1932 teLinkBandwidthRowStatus, 1933 teLinkBandwidthStorageType 1934 } 1936 STATUS current 1937 DESCRIPTION 1938 "Collection of objects needed for the monitoring of 1939 the priority-based bandwidth resources associated with 1940 TE links and component links." 1941 ::= { teLinkGroups 3 } 1943 componentLinkBandwidthGroup OBJECT-GROUP 1944 OBJECTS { componentLinkDescrEncodingType, 1945 componentLinkDescrPriority, 1946 componentLinkDescrMinBandwidth, 1947 componentLinkDescrMaxBandwidth, 1948 componentLinkDescrRowStatus, 1949 componentLinkDescrStorageType, 1950 componentLinkUnreservedBandwidth, 1951 componentLinkMaximumLspBandwidth, 1952 componentLinkBandwidthRowStatus, 1953 componentLinkBwStorageType 1954 } 1956 STATUS current 1957 DESCRIPTION 1958 "Collection of objects needed for the monitoring of 1959 bandwidth parameters associated with component links." 1960 ::= { teLinkGroups 4 } 1962 -- End of TE-LINK-MIB 1963 END 1964 10. Intellectual Property Considerations 1966 The IETF takes no position regarding the validity or scope of any 1967 intellectual property or other rights that might be claimed to per- 1968 tain to the implementation or use of the technology described in this 1969 document or the extent to which any license under such rights might 1970 or might not be available; neither does it represent that it has made 1971 any effort to identify any such rights. Information on the IETF's 1972 procedures with respect to rights in standards-track and standards- 1973 related documentation can be found in BCP-11. Copies of claims of 1974 rights made available for publication and any assurances of licenses 1975 to be made available, or the result of an attempt made to obtain a 1976 general license or permission for the use of such proprietary rights 1977 by implementers or users of this specification can be obtained from 1978 the IETF Secretariat. 1980 The IETF invites any interested party to bring to its attention any 1981 copyrights, patents or patent applications, or other proprietary 1982 rights which may cover technology that may be required to practice 1983 this standard. Please address the information to the IETF Executive 1984 Director. 1986 11. Security Considerations 1988 There are a number of management objects defined in this MIB module 1989 with a MAX-ACCESS clause of read-write and/or read-create. Such 1990 objects may be considered sensitive or vulnerable in some network 1991 environments. The support for SET operations in a non-secure environ- 1992 ment without proper protection can have a negative effect on network 1993 operations. These are the tables and objects and their sensitiv- 1994 ity/vulnerability: 1996 - All the tables in this MIB module have routing information in 1997 them and so they all have the same security attributes. 1998 Unauthorized changes to attributes of these tables can disrupt 1999 resource allocation in the network. 2001 Some of the readable objects in this MIB module (i.e., objects with a 2002 MAX-ACCESS other than not-accessible) may be considered sensitive or 2003 vulnerable in some network environments. It is thus important to con- 2004 trol even GET and/or NOTIFY access to these objects and possibly to 2005 even encrypt the values of these objects when sending them over the 2006 network via SNMP. These are the tables and objects and their sensi- 2007 tivity/vulnerability: 2009 - IP address entries in the teLinkTable (teLinkLocalIpAddr and 2010 teLinkRemoteIpAddr) may reveal the internals of a network provider 2011 IP address space. 2013 SNMP versions prior to SNMPv3 did not include adequate security. 2014 Even if the network itself is secure (for example by using IPSec), 2015 even then, there is no control as to who on the secure network is 2016 allowed to access and GET/SET (read/change/create/delete) the objects 2017 in this MIB module. 2019 It is RECOMMENDED that implementers consider the security features as 2020 provided by the SNMPv3 framework (see [RFC3410], section 8), includ- 2021 ing full support for the SNMPv3 cryptographic mechanisms (for authen- 2022 tication and privacy). 2024 Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOM- 2025 MENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable 2026 cryptographic security. It is then a customer/operator responsibility 2027 to ensure that the SNMP entity giving access to an instance of this 2028 MIB module is properly configured to give access to the objects only 2029 to those principals (users) that have legitimate rights to indeed GET 2030 or SET (change/create/delete) them. 2032 12. Acknowledgments 2034 The authors would like to acknowledge the contribution of Dmitry 2035 Ryumkin. 2037 13. References 2039 13.1. Normative References 2041 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2042 Requirement Levels", BCP 14, RFC 2119, March 1997. 2044 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2045 J., Rose, M., and S. Waldbusser, "Structure of 2046 Management Information Version 2 (SMIv2)", STD 58, 2047 RFC 2578, April 1999. 2049 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2050 J., Rose, M., and S. Waldbusser, "Textual Conventions 2051 for SMIv2", STD 58, RFC 2579, April 1999. 2053 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2054 J., Rose, M., and Waldbusser, S., "Conformance 2055 Statements for SMIv2", STD 58, RFC 2580, April 1999. 2057 [RFC2863] McCloghrie, K., and Kastenholtz, F., "The Interfaces 2058 Group MIB", RFC 2863, June 2000. 2060 [RFC3291] Daniele, M., Haberman, B., Routhier, S., and 2061 Shoenwaelder, J., "Textual Conventions for Internet 2062 Network Addresses", RFC 3291, May 2002. 2064 [RFC3471] Ashwood-Smith, P., Banarjee, A., Berger, L., 2065 Bernstein, G., Drake, J., Fan, Y., Kompella, K., 2066 Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y., 2067 Saha, D., Sharma, V., Swallow, G., and Tang, Z., 2068 "Generalized MPLS Signaling Functional Description", 2069 RFC 3471, January 2003. 2071 [BUNDLING] Kompella, K., Rekhter, Y., and Berger, L., 2072 "Link Bundling in MPLS Traffic Engineering", 2073 Internet Draft , 2074 July 2002. 2076 [GMPLS-OSPF] Kompella, K., Rekhter, Y., Banerjee, A. et al, "OSPF 2077 Extensions in Support of Generalized MPLS", Internet 2078 Draft , 2079 December 2002. 2081 [IANAifType] "IANAifType MIB Module", 2082 http://www.iana.org/assignments/ianaiftype-mib. 2084 [LMP] Lang, J., Mitra, K., Drake, J., Kompella, K., 2085 Rekhter, Y., Berger, L., Rajagopalan, B., 2086 Basak, D., Sandick, H., Zinin, A., 2087 Rajagopalan, B., and Ramamoorthi, S., 2088 "Link Management Protocol", 2089 Internet Draft , 2090 March 2003. 2092 [OSPF] Katz, D., Yeung, D., and Kompella, K., "Traffic 2093 Engineering Extensions to OSPF", Internet Draft 2094 , October 2002. 2096 [ROUTING] Kompella, K., Rekhter, Y., "Routing Extensions in 2097 Support of Generalized MPLS", Internet Draft 2098 , August 2002. 2100 13.2. Informative References 2102 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 2103 "Introduction and Applicability Statements for 2104 Internet-Standard Management Framework", RFC 3410, 2105 December 2002. 2107 [GMPLS-ARCH] Mannie, E., Ashwood-Smith, P., Awduche, D., 2108 Banarjee, A., Basak, D., Berger, L., Bernstein, G., 2109 Dharanikota, S., Drake, J., Fan, Y., Fedyk, D., 2110 Grammel, G., Guo, D., Kompella, K., Kullberg, A., 2111 Lang, J., Liaw, F., Nadeau, T., Ong, L., 2112 Papadimitriou, D., Pendarakis, D., Rajagopalan, B., 2113 Rekhter, Y., Saha, D., Sandick, H., Sharma, V., 2114 Swallow, G., Tang, Z., Yates, J., Young, G., Yu, J., 2115 Zinin, A., "Generalized Multi-Protocol Label Switching 2116 (GMPLS) Architecture", Internet Draft 2117 , 2118 March 2003. 2120 14. Authors' Addresses 2122 Martin Dubuc Thomas D. Nadeau 2123 Email: dubuc.consulting@rogers.com Cisco Systems, Inc. 2124 300 Apollo Drive 2125 Chelmsford, MA 01824 2126 Phone: +1-978-244-3051 2127 Email: tnadeau@cisco.com 2129 Sudheer Dharanikota Jonathan P. Lang 2130 Avici Systems, Inc. Rincon Networks, Inc. 2131 101 Billerica Avenue 110 El Paseo 2132 N Billerica, MA 08162 Santa Barbara, CA 93101 2133 Email: sudheer@avici.com Email: jplang@ieee.org 2135 15. Full Copyright Statement 2137 Copyright (C) The Internet Society (2003). All Rights Reserved. 2139 This document and translations of it may be copied and furnished to 2140 others, and derivative works that comment on or otherwise explain it 2141 or assist in its implementation may be prepared, copied, published 2142 and distributed, in whole or in part, without restriction of any 2143 kind, provided that the above copyright notice and this paragraph are 2144 included on all such copies and derivative works. However, this docu- 2145 ment itself may not be modified in any way, such as by removing the 2146 copyright notice or references to the Internet Society or other 2147 Internet organizations, except as needed for the purpose of develop- 2148 ing Internet standards in which case the procedures for copyrights 2149 defined in the Internet Standards process must be followed, or as 2150 required to translate it into languages other than English. 2152 The limited permissions granted above are perpetual and will not be 2153 revoked by the Internet Society or its successors or assigns. This 2154 document and the information contained herein is provided on an "AS 2155 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 2156 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 2157 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL 2158 NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY 2159 OR FITNESS FOR A PARTICULAR PURPOSE.