idnits 2.17.1 draft-ietf-mpls-te-mib-06.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document is more than 15 pages and seems to lack a Table of Contents. == There are 2 instances of lines with non-ascii characters in the document. == 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. ** The abstract seems to contain references ([MPLSArch]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 4 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 595: '...e identifier for an MPLS LSR. This MAY...' RFC 2119 keyword, line 1202: '...nce represents. This value MUST be set...' RFC 2119 keyword, line 1204: '... This value MUST be set to transi...' RFC 2119 keyword, line 1206: '...rted. This value MUST be set to tail(3...' RFC 2119 keyword, line 1218: '... unavailable, it MUST return a value o...' (2 more instances...) Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 338 has weird spacing: '... tunnel is do...' == Line 682 has weird spacing: '... in mplsT...' -- 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 (March 2, 2001) is 8454 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'SNMPv1MIBDef' is mentioned on line 93, but not defined == Unused Reference: 'LblStk' is defined on line 3019, but no explicit reference was found in the text == Unused Reference: 'Assigned' is defined on line 3035, but no explicit reference was found in the text == Unused Reference: 'INETADDRMIB' is defined on line 3117, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'MPLSArch' -- Possible downref: Non-RFC (?) normative reference: ref. 'LSRMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'LblStk' -- Possible downref: Non-RFC (?) normative reference: ref. 'RSVPTun' -- Possible downref: Non-RFC (?) normative reference: ref. 'CR-LDP' ** Obsolete normative reference: RFC 1700 (ref. 'Assigned') (Obsoleted by RFC 3232) ** Obsolete normative reference: RFC 2271 (ref. 'SNMPArch') (Obsoleted by RFC 2571) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. 'SNMPv1Traps') ** Obsolete normative reference: RFC 1902 (ref. 'SMIv2') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. 'SNMPv2TC') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. 'SNMPv2Conf') (Obsoleted by RFC 2580) ** 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) ** Obsolete normative reference: RFC 2574 (ref. 'SNMPv3USM') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. 'SNMPv2PO') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2273 (ref. 'SNMPv3App') (Obsoleted by RFC 2573) ** Obsolete normative reference: RFC 2575 (ref. 'SNMPv3VACM') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2401 (ref. 'IPSEC') (Obsoleted by RFC 4301) ** Obsolete normative reference: RFC 2233 (ref. 'IFMIB') (Obsoleted by RFC 2863) ** Obsolete normative reference: RFC 2851 (ref. 'INETADDRMIB') (Obsoleted by RFC 3291) Summary: 23 errors (**), 0 flaws (~~), 9 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Cheenu Srinivasan 2 Internet Draft Tachion Networks, Inc. 3 Expires: September 2001 4 Arun Viswanathan 5 Force10 Networks, Inc. 7 Thomas D. Nadeau 8 Cisco Systems, Inc. 10 March 2, 2001 12 MPLS Traffic Engineering Management Information Base Using 13 SMIv2 15 draft-ietf-mpls-te-mib-06.txt 17 Status of this Memo 19 This document is an Internet-Draft and is in full 20 conformance with all provisions of Section 10 of RFC2026. 22 Internet-Drafts are working documents of the Internet 23 Engineering Task Force (IETF), its areas, and its working 24 groups. Note that other groups may also distribute working 25 documents as Internet-Drafts. 27 Internet-Drafts are draft documents valid for a maximum of 28 six months and may be updated, replaced, or obsoleted by 29 other documents at any time. It is inappropriate to use 30 Internet-Drafts as reference material or to cite them other 31 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 37 accessed at http://www.ietf.org/shadow.html. 39 Abstract 41 This memo defines an experimental portion of the Management 42 Information Base (MIB) for use with network management 43 protocols in the Internet community. In particular, it 44 describes managed objects for Multi-Protocol Label 45 Switching (MPLS) [MPLSArch] based traffic engineering. 47 1. Introduction 49 This memo defines an experimental portion of the Management 50 Information Base (MIB) for use with network management 51 protocols in the Internet community. In particular, it 52 describes managed objects for modeling a Multi-Protocol 53 Label Switching (MPLS) [MPLSArch] based traffic 54 engineering. This MIB should be used in conjunction with 55 the companion document [LSRMIB] for MPLS based traffic 56 engineering configuration and management. 58 Comments should be made directly to the MPLS mailing list 59 at mpls@uu.net. 61 This memo does not, in its draft form, specify a standard 62 for the Internet community. 64 2. Terminology 66 This document uses terminology from the MPLS architecture 67 document [MPLSArch] and MPLS Label Switch Router MIB 68 [LSRMIB]. Some frequently used terms are described next. 70 An explicitly routed LSP (ERLSP) is referred to as an MPLS 71 tunnel. It consists of one in-segment and/or one out- 72 segment at the ingress/egress LSRs, each segment being 73 associated with one MPLS interface. These are also 74 referred to as tunnel segments. Additionally, at an 75 intermediate LSR, we model a connection as consisting of 76 one or more in-segments and/or one or more out-segments. 77 The binding or interconnection between in-segments and out- 78 segments in performed using a cross-connect. These objects 79 are defined in the MPLS Label Switch Router MIB [LSRMIB]. 81 3. The SNMP Management Framework 83 The SNMP Management Framework presently consists of five 84 major components: 86 - An overall architecture, described in RFC 2271 87 [SNMPArch]. 89 - Mechanisms for describing and naming objects and events 90 for the purpose of management. The first version of 91 this Structure of Management Information (SMI) is 92 called SMIv1 and described in RFC 1155 [SMIv1], RFC 93 1212 [SNMPv1MIBDef] and RFC 1215 [SNMPv1Traps]. The 94 second version, called SMIv2, is described in RFC 1902 95 [SMIv2], RFC 1903 [SNMPv2TC] and RFC 1904 [SNMPv2Conf]. 97 - Message protocols for transferring management 98 information. The first version of the SNMP message 99 protocol is called SNMPv1 and described in RFC 1157 100 [SNMPv1]. A second version of the SNMP message 101 protocol, which is not an Internet standards track 102 protocol, is called SNMPv2c and described in RFC 1901 103 [SNMPv2c] and RFC 1906 [SNMPv2TM]. The third version 104 of the message protocol is called SNMPv3 and described 105 in RFC 1906 [SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC 106 2574 [SNMPv3USM]. 108 - Protocol operations for accessing management 109 information. The first set of protocol operations and 110 associated PDU formats is described in RFC 1157 111 [SNMPv1]. A second set of protocol operations and 112 associated PDU formats is described in RFC 1905 113 [SNMPv2PO]. 115 - A set of fundamental applications described in RFC 2273 116 [SNMPv3App] and the view-based access control mechanism 117 described in RFC 2575 [SNMPv3VACM]. 119 Managed objects are accessed via a virtual information 120 store, termed the Management Information Base or MIB. 121 Objects in the MIB are defined using the mechanisms defined 122 in the SMI. This memo specifies a MIB module that is 123 compliant to the SMIv2. A MIB conforming to the SMIv1 can 124 be produced through the appropriate translations. The 125 resulting translated MIB must be semantically equivalent, 126 except where objects or events are omitted because no 127 translation is possible (use of Counter64). Some machine- 128 readable information in SMIv2 will be converted into 129 textual descriptions in SMIv1 during the translation 130 process. However, this loss of machine-readable 131 information is not considered to change the semantics of 132 the MIB. 134 3.1. Object Definitions 136 Managed objects are accessed via a virtual information 137 store, termed the Management Information Base or MIB. 138 Objects in the MIB are defined using the subset of Abstract 139 Syntax Notation One (ASN.1) defined in the SMI. In 140 particular, each object type is named by an OBJECT 141 IDENTIFIER, an administratively assigned name. The object 142 type together with an object instance serves to uniquely 143 identify a specific instantiation of the object. For human 144 convenience, we often use a textual string, termed the 145 descriptor, to also refer to the object type. 147 4. Feature List 149 The MPLS traffic engineering MIB is designed to satisfy the 150 following requirements and constraints. 152 - The MIB supports configuration of point-to-point 153 unidirectional tunnels. 155 - MPLS tunnels need not be interfaces, but it is possible 156 to configure a tunnel as an interface. 158 - The MIB supports manually configured MPLS tunnels as 159 well as those set up via any MPLS signaling protocol. 161 - The MIB supports persistent as well as non-persistent 162 tunnels. 164 5. Outline 166 Traffic engineering support for MPLS tunnels requires the 167 following configuration. 169 - Setting up MPLS tunnels along with appropriate 170 configuration parameters. 172 - Configuring tunnel loose and strict source routed hops. 174 These actions may need to be accompanied with corresponding 175 actions using [LSRMIB] to establish and configure tunnel 176 segments, if this is done manually. Also, the in-segment 177 and out-segment performance tables, mplsInSegmentPerfTable 178 and mplsOutSegmentPerfTable [LSRMIB], should be used to 179 determine performance of the tunnels and tunnel segments. 181 5.1. Summary of Traffic Engineering MIB 183 The MIB objects for performing these actions consist of the 184 following tables. 186 - Tunnel table (mplsTunnelTable) for setting up MPLS 187 tunnels. 189 - Resource table (mplsTunnelResourceTable) for setting up 190 the tunnel resources. 192 - CRLDP resource table (mplsTunnelCRLDPResTable) for 193 specifying resource objects applicable to tunnels 194 signaled using CRLDP. 196 - Tunnel hop table (mplsTunnelHopTable) for configuring 197 strict and loose source routed MPLS tunnels hops. 199 When a tunnel is signaled via a MPLS signaling protocol, 200 the mplsTunnelARHopTable gives the actual list of hops 201 traversed by the tunnel as reported by the signaling 202 protocol. These tables are described in the subsequent 203 sections. 205 6. Brief Description of MIB Objects 207 The objects described in this section support the 208 functionality described in documents [RSVPTun][CR-LDP]. 209 The tables support both manually configured and signaled 210 tunnels. 212 6.1. mplsTunnelTable 214 The mplsTunnelTable allows new MPLS tunnels to be created 215 between an MPLS LSR and a remote endpoint, and existing 216 tunnels to be reconfigured or removed. Note that we only 217 support point-to-point tunnel segments, although multi- 218 point-to-point and point-to-multi-point connections are 219 supported by an LSR acting as a cross-connect. Each MPLS 220 tunnel can thus have one out-segment originating at an LSR 221 and/or one in-segment terminating at that LSR. 223 mplsTunnelTable does not define the in and out segments 224 forming the tunnel. Instead, these are defined by creating 225 rows in the in-segment and out-segment tables, defining 226 relationships in the cross-connect table and referring to 227 these rows in the mplsTunnelTable using a cross-connect 228 index, mplsTunnelXCIndex. These segment and cross-connect 229 related objects are defined in [LSRMIB]. 231 6.2. mplsTunnelResourceTable 233 mplsTunnelResourceTable is used to indicate the resources 234 required for a tunnel. Multiple tunnels may share the same 235 resources by pointing to the same entry in this table. 236 Tunnels that do not share resources must point to separate 237 entries in this table. 239 6.3. mplsTunnelHopTable 240 mplsTunnelHopTable is used to indicate the hops, strict or 241 loose, for an MPLS tunnel defined in mplsTunnelTable, when 242 it is established via signaling. Multiple tunnels may 243 share the same hops by pointing to the same entry in this 244 table. Each row also has a secondary index, 245 mplsTunnelHopIndex, corresponding to the next hop of this 246 tunnel. The scalar mplsTunnelMaxHops indicates the maximum 247 number of hops that can be specified on each tunnel 248 supported by this LSR. 250 6.4. mplsTunnelARHopTable 252 mplsTunnelARHopTable is used to indicate the actual hops 253 traversed by a tunnel as reported by the MPLS signaling 254 protocol after the tunnel is setup. The support of this 255 table is optional since not all MPLS signaling protocol may 256 support this feature. 258 6.5. mplsTunnelCHoptable 260 mplsTunnelCHopTable lists the actual hops computed by a 261 constraint-based routing algorithm based on the 262 mplsTunnelHopTable. The support of this table is optional 263 since not all implementations may support computation of 264 hop list using a constraint-based routing protocol. 266 6.6. mplsTunnelPerfTable 268 mplsTunnelPerfTable provides several counters to measure 269 the performance of the MPLS tunnels. This table auguments 270 mplsTunnelTable. 272 6.7. mplsTunnelCRLDPResTable 274 mplsTunnelCRLDPResTable contains resource information for 275 those tunnels that are signaled using CRLDP. This is a 276 sparse extension to mplsTunnelResourceTable and is also 277 indexed by mplsTunnelResourceIndex. As with 278 mplsTunnelResourceTable, multiple tunnels may share the 279 same resources by pointing to the same entry in this table. 280 Tunnels that do not share resources must point to separate 281 entries in this table. 283 7. Application of the Interface Group to MPLS Tunnels 284 The Interfaces Group of MIB II defines generic managed 285 objects for managing interfaces. This memo contains the 286 media-specific extensions to the Interfaces Group for 287 managing MPLS Tunnels as logical interfaces. 289 This memo assumes the interpretation of the Interfaces 290 Group to be in accordance with [IFMIB] which states that 291 the interfaces table (ifTable) contains information on the 292 managed resource's interfaces and that each sub-layer below 293 the internetwork layer of a network interface is considered 294 an interface. Thus, the MPLS interface is represented as 295 an entry in the ifTable. The interrelation of entries in 296 the ifTable is defined by Interfaces Stack Group defined in 297 [IFMIB]. 299 When using MPLS Tunnels as interfaces, the interface stack 300 table might appear as follows: 302 +------------------------------------------------+ 303 | MPLS-Tunnel-interface ifType = mplsTunnel(150) | 304 +------------------------------------------------+ 305 | MPLS-interface ifType = mpls(166) | 306 +------------------------------------------------+ 307 | Underlying Layer | 308 +------------------------------------------------+ 310 In the above diagram, "Underlying Layer" refers to the 311 ifIndex of any interface type, which has been defined for 312 MPLS interworking. Examples include ATM, Frame Relay, 313 Ethernet, etc. 315 7.1. Support of the MPLS Tunnel Interface by ifTable 317 Some specific interpretations of ifTable for those MPLS 318 tunnels represented as interfaces follow: 320 Object Use for the MPLS tunnel. 322 ifIndex Each MPLS tunnel is represented by an 323 ifEntry. 325 ifDescr Description of the MPLS tunnel. 327 ifType The value that is allocated for MPLS 328 tunnel is 150. 330 ifSpeed The total bandwidth in bits per second 331 for use by the MPLS tunnel. 333 ifPhysAddress Unused. 335 ifAdminStatus See [IFMIB]. 337 ifOperStatus Assumes the value down(2) if the MPLS 338 tunnel is down. 340 ifLastChange See [IFMIB]. 342 ifInOctets The number of octets received over the 343 MPLS tunnel. 345 ifOutOctets The number of octets transmitted over 346 the MPLS tunnel. 348 ifInErrors The number of labeled packets dropped 349 due to uncorrectable errors. 351 ifInUnknownProtos The number of received packets 352 discarded during packet header 353 validation, including packets with 354 unrecognized label values. 356 ifOutErrors See [IFMIB]. 358 ifName Textual name (unique on this system) of 359 the MPLS tunnel or an octet string of 360 zero length. 362 ifLinkUpDownTrapEnable 363 Default is disabled (2). 365 ifConnectorPresent Set to false (2). 367 ifHighSpeed See [IFMIB]. 369 ifHCInOctets The 64-bit version of ifInOctets; 370 supported if required by the compliance 371 statements in [IFMIB]. 373 ifHCOutOctets The 64-bit version of ifOutOctets; 374 supported if required by the compliance 375 statements in [IFMIB]. 377 ifAlias The non-volatile 'alias' name for the 378 MPLS tunnel as specified by a network 379 manager. 381 8. Example of Tunnel Setup 383 This section contains an example of which MIB objects 384 should be modified if one would like to create a best 385 effort, loosely routed, unidirectional traffic engineered 386 tunnel, which spans two hops of a simple network. Note 387 that these objects should be created on the "head-end" 388 LSR. 390 In mplsTunnelTable: 391 { 392 mplsTunnelIndex = 1, 393 mplsTunnelInstance = 1, 394 mplsTunnelIngressLSRId = 123.123.125.1, 395 mplsTunnelEgressLSRId = 123.123.126.1, 396 mplsTunnelName = "My first tunnel", 397 mplsTunnelDescr = "Here to there", 398 mplsTunnelIsIf = true (1), 399 mplsTunnelXCPointer = mplsXCIndex.2.0.0.15, 400 mplsTunnelSignallingProto = none (1), 401 mplsTunnelSetupPrio = 0, 402 mplsTunnelHoldingPrio = 0, 403 mplsTunnelSessionAttributes = 0, 404 mplsTunnelOwner = snmp (1), 405 mplsTunnelLocalProtectInUse = false (0), 406 mplsTunnelResourcePointer = mplsTunnelResourceIndex.5, 407 mplsTunnelInstancePriority = 1, 408 mplsTunnelHopTableIndex = 1, 409 mplsTunnelPrimaryInstance = 0, 410 mplsTunnelIncludeAnyAffinity = 0, 411 mplsTunnelIncludeAllAffinity = 0, 412 mplsTunnelExcludeAllAffinity = 0, 413 mplsTunnelPathInUse = 1, 414 mplsTunnelRole = head(1), 415 mplsTunnelRowStatus = createAndGo (4) 416 } 418 In mplsTunnelResourceTable: 419 { 420 mplsTunnelResourceIndex = 5, 421 mplsTunnelResourceMaxRate = 0, 422 mplsTunnelResourceMeanRate = 0, 423 mplsTunnelResourceMaxBurstSize = 0, 424 mplsTunnelResourceRowStatus = createAndGo (4) 425 } 427 The next two instances of mplsTunnelHopEntry are used to 428 denote the hops this tunnel will take across the network. 430 The following denotes the beginning of the network, or the 431 first hop. We have used the fictitious LSR identified by 432 "123.123.125.1" as our example head-end router. 434 In mplsTunnelHopTable: 435 { 436 mplsTunnelHopListIndex = 1, 437 mplsTunnelPathOptionIndex = 1, 438 mplsTunnelHopIndex = 1, 439 mplsTunnelHopAddrType = 1, 440 mplsTunnelHopIpv4Addr = 123.123.125.1, 441 mplsTunnelHopIpv4PrefixLen = 9, 442 mplsTunnelHopType = loose (2), 443 mplsTunnelHopRowStatus = createAndGo (4) 444 } 446 The following denotes the end of the network, or the last 447 hop in our example. We have used the fictitious LSR 448 identified by "123.123.126.1" as our end router. 450 In mplsTunnelHopTable: 451 { 452 mplsTunnelHopListIndex = 1, 453 mplsTunnelPathOptionIndex = 1, 454 mplsTunnelHopIndex = 2, 455 mplsTunnelHopAddrType = 1, 456 mplsTunnelHopIpv4Addr = 123.123.126.1, 457 mplsTunnelHopIpv4PrefixLen = 9, 458 mplsTunnelHopType = loose (2), 459 mplsTunnelHopRowStatus = createAndGo (4) 460 } 462 9. The Use of RowPointer 464 RowPointer is a textual convention used to identify a 465 conceptual row in an SNMP Table by pointing to one of its 466 objects. In this MIB, in mplsTunnelTable, the objects 467 mplsTunnelXCPointer and mplsTunnelResourcePointer are of 468 type RowPointer. The object mplsTunnelXCPointer points to a 469 specific entry in the mplsXCTable [LSRMIB]. This entry in 470 the mplsXCTable is the associated LSP for the given MPLS 471 tunnel entry. The object mplsTunnelResourcePointer points 472 to a specific entry in a traffic parameter table. An 473 example of such a traffic parameter table is 474 mplsTunnelResourceTable. It indicates a specific instance 475 of a traffic parameter entry that is associated with a 476 given MPLS tunnel entry. 478 10. MPLS Traffic Engineering MIB Definitions 479 MPLS-TE-MIB DEFINITIONS ::= BEGIN 481 IMPORTS 482 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 483 experimental, Integer32, Unsigned32, Counter32, 484 Counter64, TimeTicks, TimeStamp 485 FROM SNMPv2-SMI 487 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 488 FROM SNMPv2-CONF 490 TEXTUAL-CONVENTION, TruthValue, RowStatus, RowPointer, 491 StorageType, DisplayString 492 FROM SNMPv2-TC 494 InterfaceIndexOrZero 495 FROM IF-MIB 497 MplsBitRate, MplsBurstSize, MplsLSPID 498 FROM MPLS-LSR-MIB 500 InetAddressIPv4, InetAddressIPv6 501 FROM INET-ADDRESS-MIB; 503 mplsTeMIB MODULE-IDENTITY 504 LAST-UPDATED 505 "200103021200Z" -- March 2, 2001 12:00:00 EST 506 ORGANIZATION 507 "Multiprotocol Label Switching (MPLS) Working Group" 508 CONTACT-INFO 509 " Cheenu Srinivasan 510 Postal: Tachion Networks, Inc. 511 Monmouth Park Corporate Center I 512 Building C, 185 Monmouth Park Highway 513 West Long Branch, NJ 07764 514 Tel: +1-732-542-7750 x1234 515 Email: cheenu@tachion.com 517 Arun Viswanathan 518 Postal: Force10 Networks, Inc. 519 1440 McCarthy Blvd 520 Milpitas, CA 95035 521 Tel: +1-408-571-3516 522 Email: arun@force10networks.com 524 Thomas D. Nadeau 525 Postal: Cisco Systems, Inc. 526 250 Apollo Drive 527 Chelmsford, MA 01824 528 Tel: +1-978-244-3051 529 Email: tnadeau@cisco.com" 530 DESCRIPTION 531 "This MIB module contains managed object definitions 532 for MPLS Traffic Engineering (TE) as defined in: 533 Extensions to RSVP for LSP Tunnels, Awduche et al, 534 Internet Draft , August 2000; Constraint-Based LSP Setup 536 using LDP, B. Jamoussi, Internet Draft , July 2000; Requirements for 538 Traffic Engineering Over MPLS, Awduche, D., J. 539 Malcolm, J., Agogbua, J., O'Dell, M., J. McManus, 540 , September 1999." 542 -- Revision history. 544 REVISION 545 "200103021200Z" -- 2 March 2001 12:00:00 EST 546 DESCRIPTION 547 "Updates based on MPLS WG last call feedback." 548 REVISION 549 "200011211200Z" -- 21 November 2000 12:00:00 EST 550 DESCRIPTION 551 "Updates based on MPLS WG feedback." 552 REVISION 553 "200007141200Z" -- 14 July 2000 12:00:00 EST 554 DESCRIPTION 555 "Updates based on MPLS WG feedback." 556 REVISION 557 "200005261200Z" -- 26 May 2000 12:00:00 EST 558 DESCRIPTION 559 "Updates based on MPLS WG feedback." 560 REVISION 561 "200003031200Z" -- 3 March 2000 12:00:00 EST 562 DESCRIPTION 563 "Updates based on MPLS WG feedback." 564 REVISION 565 "199907161200Z" -- 16 July 1999 12:00:00 EST 566 DESCRIPTION 567 "Initial draft version." 569 ::= { experimental 95 } 571 -- Textual Conventions. 573 MplsTunnelIndex ::= TEXTUAL-CONVENTION 574 STATUS current 575 DESCRIPTION 576 "Index into mplsTunnelTable." 577 SYNTAX Integer32 (1..65535) 579 MplsTunnelInstanceIndex ::= TEXTUAL-CONVENTION 580 STATUS current 581 DESCRIPTION 582 "Instance index into mplsTunnelTable." 583 SYNTAX Unsigned32 (0..65535) 585 MplsTunnelAffinity ::= TEXTUAL-CONVENTION 586 STATUS current 587 DESCRIPTION 588 "Include-any, include-all, or exclude-all constraint 589 for link selection." 590 SYNTAX Unsigned32 592 MplsLsrId ::= TEXTUAL-CONVENTION 593 STATUS current 594 DESCRIPTION 595 "A unique identifier for an MPLS LSR. This MAY 596 represent an IpV4 address." 597 SYNTAX Unsigned32 599 MplsPathIndex ::= TEXTUAL-CONVENTION 600 STATUS current 601 DESCRIPTION 602 "A unique identifier used to identify a specific path 603 used by a tunnel." 604 SYNTAX Unsigned32 606 MplsPathIndexOrZero ::= TEXTUAL-CONVENTION 607 STATUS current 608 DESCRIPTION 609 "A unique identifier used to identify a specific path 610 used by a tunnel. If this value is set to 0, it 611 indicates that no path is in use." 612 SYNTAX Unsigned32 614 -- Top level components of this MIB. 616 -- tables, scalars 617 mplsTeScalars OBJECT IDENTIFIER ::= { mplsTeMIB 1 } 618 mplsTeObjects OBJECT IDENTIFIER ::= { mplsTeMIB 2 } 620 -- traps 621 mplsTeNotifications OBJECT IDENTIFIER ::= { mplsTeMIB 3 } 622 mplsTeNotifyPrefix OBJECT IDENTIFIER ::= { mplsTeNotifications 0 } 623 -- conformance 624 mplsTeConformance OBJECT IDENTIFIER ::= { mplsTeMIB 4 } 626 -- MPLS Tunnel scalars. 628 mplsTunnelConfigured OBJECT-TYPE 629 SYNTAX Unsigned32 630 MAX-ACCESS read-only 631 STATUS current 632 DESCRIPTION 633 "The number of tunnels configured on this device. A 634 tunnel is considered configured if the 635 mplsTunnelRowStatus is active(1)." 636 ::= { mplsTeScalars 1 } 638 mplsTunnelActive OBJECT-TYPE 639 SYNTAX Unsigned32 640 MAX-ACCESS read-only 641 STATUS current 642 DESCRIPTION 643 "The number of tunnels active on this device. A 644 tunnel is considered active if the 645 mplsTunnelOperStatus is up(1)." 646 ::= { mplsTeScalars 2 } 648 mplsTunnelTEDistProto OBJECT-TYPE 649 SYNTAX BITS { 650 other (0), 651 ospf (1), 652 isis (2) 653 } 654 MAX-ACCESS read-only 655 STATUS current 656 DESCRIPTION 657 "The traffic engineering distribution protocol(s) 658 used by this LSR. Note that an LSR may support more 659 than one distribution protocol simultaneously." 660 ::= { mplsTeScalars 3 } 662 mplsTunnelMaxHops OBJECT-TYPE 663 SYNTAX Unsigned32 664 MAX-ACCESS read-only 665 STATUS current 666 DESCRIPTION 667 "The maximum number of hops that can be specified for 668 a tunnel on this device." 669 ::= { mplsTeScalars 4 } 671 -- End of MPLS Tunnel scalars. 673 -- MPLS tunnel table. 675 mplsTunnelIndexNext OBJECT-TYPE 676 SYNTAX Integer32 (0..65535) 677 MAX-ACCESS read-only 678 STATUS current 679 DESCRIPTION 680 "This object contains the next appropriate value to 681 be used for mplsTunnelIndex when creating entries 682 in mplsTunnelTable. If the number of unassigned 683 entries is exhausted, a retrival operation will 684 return a value of 0. This object may also return a 685 value of 0 when the LSR is unable to accept 686 conceptual row creation, for example, if the 687 mplsTunnelTable is implemented as read-only. To 688 obtain the value of mplsTunnelIndex for a new 689 entry, the manager must first issue a management 690 protocol retrieval operation to obtain the current 691 value of this object. The agent should modify the 692 value to reflect the next unassigned index after 693 each retrieval operation. After a manager retrieves 694 a value the agent will determine through its local 695 policy when this index value will be made available 696 for reuse." 697 ::= { mplsTeObjects 1 } 699 mplsTunnelTable OBJECT-TYPE 700 SYNTAX SEQUENCE OF MplsTunnelEntry 701 MAX-ACCESS not-accessible 702 STATUS current 703 DESCRIPTION 704 "The mplsTunnelTable allows new MPLS tunnels to be 705 created between an LSR and a remote endpoint, and 706 existing tunnels to be reconfigured or removed. 707 Note that only point-to-point tunnel segments are 708 supported, although multi-point-to-point and point- 709 to-multi-point connections are supported by an LSR 710 acting as a cross-connect. Each MPLS tunnel can 711 thus have one out-segment originating at this LSR 712 and/or one in-segment terminating at this LSR." 713 ::= { mplsTeObjects 2 } 715 mplsTunnelEntry OBJECT-TYPE 716 SYNTAX MplsTunnelEntry 717 MAX-ACCESS not-accessible 718 STATUS current 719 DESCRIPTION 720 "An entry in this table represents an MPLS tunnel. 721 An entry can be created by a network administrator 722 or by an SNMP agent as instructed by an MPLS 723 signaling protocol. Whenever a new entry is created 724 with mplsTunnelIsIf set to true(1), then a 725 corresponding entry is created in ifTable as well 726 (see RFC 2233). The ifType of this entry is 727 mplsTunnel(150)." 728 REFERENCE 729 "1. RFC 2233 - The Interfaces Group MIB using SMIv2, 730 McCloghrie, K., and F. Kastenholtz, Nov. 1997 731 2. RFC 1700 - Assigned Numbers, Reynolds, J. and J. 732 Postel, Oct. 1994" 733 INDEX { mplsTunnelIndex, mplsTunnelInstance, 734 mplsTunnelIngressLSRId, mplsTunnelEgressLSRId 735 } 736 ::= { mplsTunnelTable 1 } 738 MplsTunnelEntry ::= SEQUENCE { 739 mplsTunnelIndex MplsTunnelIndex, 740 mplsTunnelInstance MplsTunnelInstanceIndex, 741 mplsTunnelIngressLSRId MplsLsrId, 742 mplsTunnelEgressLSRId MplsLsrId, 743 mplsTunnelName DisplayString, 744 mplsTunnelDescr DisplayString, 745 mplsTunnelIsIf TruthValue, 746 mplsTunnelIfIndex InterfaceIndexOrZero, 747 mplsTunnelXCPointer RowPointer, 748 mplsTunnelSignallingProto INTEGER, 749 mplsTunnelSetupPrio INTEGER, 750 mplsTunnelHoldingPrio INTEGER, 751 mplsTunnelSessionAttributes BITS, 752 mplsTunnelOwner INTEGER, 753 mplsTunnelLocalProtectInUse TruthValue, 754 mplsTunnelResourcePointer RowPointer, 755 mplsTunnelInstancePriority Unsigned32, 756 mplsTunnelHopTableIndex MplsPathIndexOrZero, 757 mplsTunnelARHopTableIndex MplsPathIndexOrZero, 758 mplsTunnelCHopTableIndex MplsPathIndexOrZero, 759 mplsTunnelPrimaryInstance MplsTunnelInstanceIndex, 760 mplsTunnelPrimaryTimeUp TimeTicks, 761 mplsTunnelPathChanges Counter32, 762 mplsTunnelLastPathChange TimeTicks, 763 mplsTunnelCreationTime TimeStamp, 764 mplsTunnelStateTransitions Counter32, 765 mplsTunnelIncludeAnyAffinity MplsTunnelAffinity, 766 mplsTunnelIncludeAllAffinity MplsTunnelAffinity, 767 mplsTunnelExcludeAllAffinity MplsTunnelAffinity, 768 mplsTunnelPathInUse MplsPathIndexOrZero, 769 mplsTunnelRole INTEGER, 770 mplsTunnelTotalUpTime TimeTicks, 771 mplsTunnelInstanceUpTime TimeTicks, 772 mplsTunnelAdminStatus INTEGER, 773 mplsTunnelOperStatus INTEGER, 774 mplsTunnelRowStatus RowStatus, 775 mplsTunnelStorageType StorageType 776 } 778 mplsTunnelIndex OBJECT-TYPE 779 SYNTAX MplsTunnelIndex 780 MAX-ACCESS accessible-for-notify 781 STATUS current 782 DESCRIPTION 783 "Uniquely identifies this row." 784 ::= { mplsTunnelEntry 1 } 786 mplsTunnelInstance OBJECT-TYPE 787 SYNTAX MplsTunnelInstanceIndex 788 MAX-ACCESS accessible-for-notify 789 STATUS current 790 DESCRIPTION 791 "Uniquely identifies an instance of a tunnel. It is 792 useful to identify multiple instances of tunnels 793 for the purposes of backup and parallel tunnels." 794 ::= { mplsTunnelEntry 2 } 796 mplsTunnelIngressLSRId OBJECT-TYPE 797 SYNTAX MplsLsrId 798 MAX-ACCESS accessible-for-notify 799 STATUS current 800 DESCRIPTION 801 "The purpose of this object is to uniquely identity a 802 tunnel within a network. When the MPLS signalling 803 protoocol is rsvp(2) this value should mimic the 804 Extended Tunnel Id field in the Session object. 805 When the MPLS signalling protoocol is crldp(3) this 806 value should mimic the Ingress LSR Router ID field 807 in the LSPID TLV object." 808 REFERENCE 809 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 810 Awduche et al, Internet Draft , August 2000., 812 2. Constraint-Based LSP Setup using LDP, Jamoussi, 813 Internet Draft , 814 July 2000." 815 ::= { mplsTunnelEntry 3 } 817 mplsTunnelEgressLSRId OBJECT-TYPE 818 SYNTAX MplsLsrId 819 MAX-ACCESS accessible-for-notify 820 STATUS current 821 DESCRIPTION 822 "Specifies the egress LSR Id." 823 ::= { mplsTunnelEntry 4 } 825 mplsTunnelName OBJECT-TYPE 826 SYNTAX DisplayString 827 MAX-ACCESS read-create 828 STATUS current 829 DESCRIPTION 830 "The canonical name assigned to the tunnel. This name 831 can be used to refer to the tunnel on the LSR�s 832 console port. If mplsTunnelIsIf is set to true 833 then the ifName of the interface corresponding to 834 this tunnel should have a value equal to 835 mplsTunnelName. Also see the description of ifName 836 in RFC 2233." 837 REFERENCE 838 "RFC 2233 - The Interfaces Group MIB using SMIv2, 839 McCloghrie, K., and F. Kastenholtz, Nov. 1997" 840 ::= { mplsTunnelEntry 5 } 842 mplsTunnelDescr OBJECT-TYPE 843 SYNTAX DisplayString 844 MAX-ACCESS read-create 845 STATUS current 846 DESCRIPTION 847 "A textual string containing information about the 848 tunnel. If there is no description this object 849 contains a zero length string." 850 ::= { mplsTunnelEntry 6 } 852 mplsTunnelIsIf OBJECT-TYPE 853 SYNTAX TruthValue 854 MAX-ACCESS read-create 855 STATUS current 856 DESCRIPTION 857 "Denotes whether or not this tunnel corresponds to an 858 interface represented in the interfaces group 859 table. Note that if this variable is set to true 860 then the ifName of the interface corresponding to 861 this tunnel should have a value equal to 862 mplsTunnelName. Also see the description of ifName 863 in RFC 2233." 864 REFERENCE 865 "RFC 2233 - The Interfaces Group MIB using SMIv2, 866 McCloghrie, K., and F. Kastenholtz, Nov. 1997" 867 DEFVAL { false } 868 ::= { mplsTunnelEntry 7 } 870 mplsTunnelIfIndex OBJECT-TYPE 871 SYNTAX InterfaceIndexOrZero 872 MAX-ACCESS read-only 873 STATUS current 874 DESCRIPTION 875 "If mplsTunnelIsIf is set to true, then this value 876 contains the LSR-assigned ifIndex which corresponds 877 to an entry in the interfaces table. Otherwise 878 this variable should contain the value of zero 879 indicating that a valid ifIndex was not assigned to 880 this tunnel interface." 881 REFERENCE 882 "RFC 2233 - The Interfaces Group MIB using SMIv2, 883 McCloghrie, K., and F. Kastenholtz, Nov. 1997" 884 ::= { mplsTunnelEntry 8 } 886 mplsTunnelXCPointer OBJECT-TYPE 887 SYNTAX RowPointer 888 MAX-ACCESS read-create 889 STATUS current 890 DESCRIPTION 891 "This variable points to a row in the mplsXCTable. 892 This table identifies the segments that compose 893 this tunnel, their characteristics, and 894 relationships to each other. A value of zeroDotZero 895 indicates that no LSP has been associated with this 896 tunnel yet." 897 REFERENCE 898 "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS 899 Label Switch Router Management Information Base 900 Using SMIv2, Internet Draft , July 2000." 902 ::= { mplsTunnelEntry 9 } 904 mplsTunnelSignallingProto OBJECT-TYPE 905 SYNTAX INTEGER { 906 none(1), 907 rsvp(2), 908 crldp(3), 909 other(4) 910 } 911 MAX-ACCESS read-create 912 STATUS current 913 DESCRIPTION 914 "The signaling protocol, if any, which was used to 915 setup this tunnel." 916 DEFVAL { none } 917 ::= { mplsTunnelEntry 10 } 919 mplsTunnelSetupPrio OBJECT-TYPE 920 SYNTAX INTEGER (0..7) 921 MAX-ACCESS read-create 922 STATUS current 923 DESCRIPTION 924 "Indicates the setup priority of this tunnel." 925 REFERENCE 926 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 927 Awduche et al, Internet Draft , August 2000., 929 2. Constraint-Based LSP Setup using LDP, Jamoussi, 930 Internet Draft , 931 July 2000." 932 ::= { mplsTunnelEntry 11 } 934 mplsTunnelHoldingPrio OBJECT-TYPE 935 SYNTAX INTEGER (0..7) 936 MAX-ACCESS read-create 937 STATUS current 938 DESCRIPTION 939 "Indicates the holding priority for this tunnel." 940 REFERENCE 941 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 942 Awduche et al, Internet Draft , August 2000., 944 2. Constraint-Based LSP Setup using LDP, Jamoussi, 945 Internet Draft , 946 July 2000." 947 ::= { mplsTunnelEntry 12 } 949 mplsTunnelSessionAttributes OBJECT-TYPE 950 SYNTAX BITS { 951 fastReroute (0), 952 mergingPermitted (1), 953 isPersistent (2), 954 isPinned (3), 955 recordRoute(4) 956 } 957 MAX-ACCESS read-create 958 STATUS current 959 DESCRIPTION 960 "This bitmask indicates optional session values for 961 this tunnel. The following describes these 962 bitfields: 964 fastRerouteThis flag indicates that the any tunnel 965 hop may choose to reroute this tunnel without 966 tearing it down. This flag permits transit routers 967 to use a local repair mechanism which may result in 968 violation of the explicit routing of this tunnel. 969 When a fault is detected on an adjacent downstream 970 link or node, a transit router can reroute traffic 971 for fast service restoration. 973 mergingPermitted This flag permits transit routers 974 to merge this session with other RSVP sessions for 975 the purpose of reducing resource overhead on 976 downstream transit routers, thereby providing 977 better network scalability. 979 isPersistent Indicates whether this tunnel should 980 be restored automatically after a failure occurs. 982 isPinned This flag indicates whether the loose- 983 routed hops of this tunnel are to be pinned. 985 recordRouteThis flag indicates whether or not the 986 signaling protocol should remember the tunnel path 987 after it has been signaled." 989 REFERENCE 990 "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, 991 Awduche et al, Internet Draft , August 2000." 993 DEFVAL { 0 } 994 ::= { mplsTunnelEntry 13 } 996 mplsTunnelOwner OBJECT-TYPE 997 SYNTAX INTEGER { 998 admin(1), -- represents all management entities 999 rsvp(2), 1000 crldp(3), 1001 policyAgent(4), 1002 other(5) 1003 } 1004 MAX-ACCESS read-create 1005 STATUS current 1006 DESCRIPTION 1007 "Indicates which protocol created and is responsible 1008 for managing this tunnel. Values rsvp(2) and 1009 crldp(3) should not be used at the head-end of a 1010 MPLS tunnel." 1011 ::= { mplsTunnelEntry 14 } 1013 mplsTunnelLocalProtectInUse OBJECT-TYPE 1014 SYNTAX TruthValue 1015 MAX-ACCESS read-create 1016 STATUS current 1017 DESCRIPTION 1018 "Indicates that the local repair mechanism is in use 1019 to maintain this tunnel (usually in the face of an 1020 outage of the link it was previously routed over)." 1021 ::= { mplsTunnelEntry 15 } 1023 mplsTunnelResourcePointer OBJECT-TYPE 1024 SYNTAX RowPointer 1025 MAX-ACCESS read-create 1026 STATUS current 1027 DESCRIPTION 1028 "This variable represents a pointer to the traffic 1029 parameter specification for this tunnel. This 1030 value may point at an entry in the 1031 mplsTunnelResourceEntry to indicate which 1032 mplsTunnelResourceEntry is to be assigned to this 1033 segment. This value may optionally point at an 1034 externally defined traffic parameter specification 1035 table. A value of zeroDotZero indicates best- 1036 effort treatment. By having the same value of this 1037 object, two or more segments can indicate resource 1038 sharing." 1039 ::= { mplsTunnelEntry 16 } 1041 mplsTunnelInstancePriority OBJECT-TYPE 1042 SYNTAX Unsigned32 1043 MAX-ACCESS read-create 1044 STATUS current 1045 DESCRIPTION 1046 "This value indicates which priority, in descending 1047 order, with 0 indicating the lowest priority, 1048 within a group of tunnel instances. A group of 1049 tunnel instances is defined as a set of tunnels 1050 with the same mplsTunnelIndex in this table, but 1051 with a different mplsTunnelInstance. Tunnel group 1052 priorities are used to denote the priority at which 1053 a particular tunnel instance will supercede 1054 another. Instances of tunnels containing the same 1055 mplsTunnelInstancePriority will be used for load 1056 sharing." 1057 DEFVAL { 0 } 1058 ::= { mplsTunnelEntry 17 } 1060 mplsTunnelHopTableIndex OBJECT-TYPE 1061 SYNTAX MplsPathIndexOrZero 1062 MAX-ACCESS read-create 1063 STATUS current 1064 DESCRIPTION 1065 "Index into the mplsTunnelHopTable entry that 1066 specifies the explicit route hops for this tunnel." 1067 ::= { mplsTunnelEntry 18 } 1069 mplsTunnelARHopTableIndex OBJECT-TYPE 1070 SYNTAX MplsPathIndexOrZero 1071 MAX-ACCESS read-only 1072 STATUS current 1073 DESCRIPTION 1074 "Index into the mplsTunnelARHopTable entry that 1075 specifies the actual hops traversed by the tunnel." 1076 ::= { mplsTunnelEntry 19 } 1078 mplsTunnelCHopTableIndex OBJECT-TYPE 1079 SYNTAX MplsPathIndexOrZero 1080 MAX-ACCESS read-only 1081 STATUS current 1082 DESCRIPTION 1083 "Index into the mplsTunnelCHopTable entry that 1084 specifies the computed hops traversed by the 1085 tunnel." 1086 ::= { mplsTunnelEntry 20 } 1088 mplsTunnelPrimaryInstance OBJECT-TYPE 1089 SYNTAX MplsTunnelInstanceIndex 1090 MAX-ACCESS read-only 1091 STATUS current 1092 DESCRIPTION 1093 "Specifies the instance index of the primary instance 1094 of this tunnel." 1095 ::= { mplsTunnelEntry 21 } 1097 mplsTunnelPrimaryTimeUp OBJECT-TYPE 1098 SYNTAX TimeTicks 1099 MAX-ACCESS read-only 1100 STATUS current 1101 DESCRIPTION 1102 "Specifies the total time the primary instance of 1103 this tunnel has been active. The primary instance 1104 of this tunnel is defined in 1105 mplsTunnelPrimaryInstance." 1106 ::= { mplsTunnelEntry 22 } 1108 mplsTunnelPathChanges OBJECT-TYPE 1109 SYNTAX Counter32 1110 MAX-ACCESS read-only 1111 STATUS current 1112 DESCRIPTION 1113 "Specifies the number of times the paths has changed 1114 for this tunnel." 1115 ::= { mplsTunnelEntry 23 } 1117 mplsTunnelLastPathChange OBJECT-TYPE 1118 SYNTAX TimeTicks 1119 MAX-ACCESS read-only 1120 STATUS current 1121 DESCRIPTION 1122 "Specifies the time since the last path change for 1123 this tunnel." 1124 ::= { mplsTunnelEntry 24 } 1126 mplsTunnelCreationTime OBJECT-TYPE 1127 SYNTAX TimeStamp 1128 MAX-ACCESS read-only 1129 STATUS current 1130 DESCRIPTION 1131 "Specifies the value of SysUpTime when the first 1132 instance of this tunnel came into existence." 1133 ::= { mplsTunnelEntry 25 } 1135 mplsTunnelStateTransitions OBJECT-TYPE 1136 SYNTAX Counter32 1137 MAX-ACCESS read-only 1138 STATUS current 1139 DESCRIPTION 1140 "Specifies the number of times the state of this 1141 tunnel instance has changed." 1142 ::= { mplsTunnelEntry 26 } 1144 mplsTunnelIncludeAnyAffinity OBJECT-TYPE 1145 SYNTAX MplsTunnelAffinity 1146 MAX-ACCESS read-create 1147 STATUS current 1148 DESCRIPTION 1149 "A link satisfies the include-any constraint if and 1150 only if the constraint is zero, or the link and the 1151 constraint have a resource class in common." 1152 REFERENCE "RSVP-TE: Extensions to RSVP for LSP 1153 Tunnels, 1154 draft-ietf-mpls-rsvp-lsp-tunnel-07.txt" 1155 ::= { mplsTunnelEntry 27 } 1157 mplsTunnelIncludeAllAffinity OBJECT-TYPE 1158 SYNTAX MplsTunnelAffinity 1159 MAX-ACCESS read-create 1160 STATUS current 1161 DESCRIPTION 1162 "A link satisfies the include-all constraint if and 1163 only if the link contains all of the adminstrative 1164 groups specified in the constraint." 1165 REFERENCE "RSVP-TE: Extensions to RSVP for LSP 1166 Tunnels, draft-ietf-mpls-rsvp-lsp-tunnel-07.txt" 1167 ::= { mplsTunnelEntry 28 } 1169 mplsTunnelExcludeAllAffinity OBJECT-TYPE 1170 SYNTAX MplsTunnelAffinity 1171 MAX-ACCESS read-create 1172 STATUS current 1173 DESCRIPTION 1174 "A link satisfies the exclude-all constraint if and 1175 only if the link contains none of the adminstrative 1176 groups specifie in the constraint." 1177 REFERENCE "RSVP-TE: Extensions to RSVP for LSP 1178 Tunnels, draft-ietf-mpls-rsvp-lsp-tunnel-07.txt" 1179 ::= { mplsTunnelEntry 29 } 1181 mplsTunnelPathInUse OBJECT-TYPE 1182 SYNTAX MplsPathIndexOrZero 1183 MAX-ACCESS read-create 1184 STATUS current 1185 DESCRIPTION 1186 "This value denotes the configured path that was 1187 chosen for this tunnel. This value reflects the 1188 secondary index into the TunnelHopTable. This path 1189 may not exactly match the one in the ARHopTable due 1190 to the fact that some CSPF modification may have 1191 taken place. See the ARHopTable for the actual path 1192 being taken by the tunnel. A value of zero denotes 1193 that no path is currently in use or available." 1194 ::= { mplsTunnelEntry 30 } 1196 mplsTunnelRole OBJECT-TYPE 1197 SYNTAX INTEGER { head(1), transit(2), tail(3) } 1198 MAX-ACCESS read-create 1199 STATUS current 1200 DESCRIPTION 1201 "This value signifies the role that this tunnel 1202 entry/instance represents. This value MUST be set 1203 to head(1) at the originating point of the tunnel. 1204 This value MUST be set to transit(2) at transit 1205 points along the tunnel, if transit points are 1206 supported. This value MUST be set to tail(3) at the 1207 terminating point of the tunnel if tunnel tails are 1208 supported." 1209 ::= { mplsTunnelEntry 31 } 1211 mplsTunnelTotalUpTime OBJECT-TYPE 1212 SYNTAX TimeTicks 1213 MAX-ACCESS read-create 1214 STATUS current 1215 DESCRIPTION 1216 "This value represents the aggregate up time for all 1217 instances of this tunnel, if available. If this 1218 value is unavailable, it MUST return a value of 0." 1220 ::= { mplsTunnelEntry 32 } 1222 mplsTunnelInstanceUpTime OBJECT-TYPE 1223 SYNTAX TimeTicks 1224 MAX-ACCESS read-create 1225 STATUS current 1226 DESCRIPTION 1227 "This value identifies the total time that this 1228 tunnel instance's operStatus has been Up(1)." 1229 ::= { mplsTunnelEntry 33 } 1231 mplsTunnelAdminStatus OBJECT-TYPE 1232 SYNTAX INTEGER { 1233 -- ready to pass packets 1234 up(1), 1235 down(2), 1236 -- in some test mode 1237 testing(3) 1238 } 1239 MAX-ACCESS read-create 1240 STATUS current 1241 DESCRIPTION 1242 "Indicates the desired operational status of this 1243 tunnel." 1244 ::= { mplsTunnelEntry 34 } 1246 mplsTunnelOperStatus OBJECT-TYPE 1247 SYNTAX INTEGER { 1248 -- ready to pass packets 1249 up(1), 1250 down(2), 1251 -- in some test mode 1252 testing(3), 1253 -- status cannot be determined 1254 unknown(4), 1255 dormant(5), 1256 -- some component is missing 1257 notPresent(6), 1258 -- down due to the state of 1259 -- lower layer interfaces 1260 lowerLayerDown(7) 1261 } 1262 MAX-ACCESS read-only 1263 STATUS current 1264 DESCRIPTION 1265 "Indicates the actual operational status of this 1266 tunnel, which is typically but not limited to, a 1267 function of the state of individual segments of 1268 this tunnel." 1269 ::= { mplsTunnelEntry 35 } 1271 mplsTunnelRowStatus OBJECT-TYPE 1272 SYNTAX RowStatus 1273 MAX-ACCESS read-create 1274 STATUS current 1275 DESCRIPTION 1276 "This variable is used to create, modify, and/or 1277 delete a row in this table." 1278 ::= { mplsTunnelEntry 36 } 1280 mplsTunnelStorageType OBJECT-TYPE 1281 SYNTAX StorageType 1282 MAX-ACCESS read-create 1283 STATUS current 1284 DESCRIPTION 1285 "This variable indicates the storage type for this 1286 object." 1287 ::= { mplsTunnelEntry 37 } 1289 -- End of mplsTunnelTable 1291 mplsTunnelHopListIndexNext OBJECT-TYPE 1292 SYNTAX Unsigned32 (0..2147483647) 1293 MAX-ACCESS read-only 1294 STATUS current 1295 DESCRIPTION 1296 "This object contains an appropriate value to be used 1297 for mplsTunnelHopListIndex when creating entries in 1298 the mplsTunnelHopTable. If the number of 1299 unassigned entries is exhausted, a retrival 1300 operation will return a value of 0. This object 1301 may also return a value of 0 when the LSR is unable 1302 to accept conceptual row creation, for example, if 1303 the mplsTunnelHopTable is implemented as read-only. 1304 To obtain the value of mplsTunnelHopListIndex for a 1305 new entry in the mplsTunnelHopTable, the manager 1306 issues a management protocol retrieval operation to 1307 obtain the current value of mplsTunnelHopIndex. 1308 After each retrieval operation, the agent should 1309 modify the value to reflect the next unassigned 1310 index. After a manager retrieves a value the agent 1311 will determine through its local policy when this 1312 index value will be made available for reuse." 1313 ::= { mplsTeObjects 3 } 1315 mplsTunnelHopTable OBJECT-TYPE 1316 SYNTAX SEQUENCE OF MplsTunnelHopEntry 1317 MAX-ACCESS not-accessible 1318 STATUS current 1319 DESCRIPTION 1320 "The mplsTunnelHopTable is used to indicate the hops, 1321 strict or loose, for an MPLS tunnel defined in 1322 mplsTunnelTable, when it is established via 1323 signaling, for the outgoing direction of the 1324 tunnel. Each row in this table is indexed by 1325 mplsTunnelHopListIndex. Each row also has a 1326 secondary index mplsTunnelHopIndex corresponding to 1327 the next hop that this row corresponds to. The 1328 first row in the table is the first hop after the 1329 origination point of the tunnel. In case we want 1330 to specify a particular interface on the 1331 originating LSR of an outgoing tunnel by which we 1332 want packets to exit the LSR, we specify this as 1333 the first hop for this tunnel in 1334 mplsTunnelHopTable." 1335 ::= { mplsTeObjects 4 } 1337 mplsTunnelHopEntry OBJECT-TYPE 1338 SYNTAX MplsTunnelHopEntry 1339 MAX-ACCESS not-accessible 1340 STATUS current 1341 DESCRIPTION 1342 "An entry in this table represents a tunnel hop. An 1343 entry is created by a network administrator for 1344 signaled ERLSP set up by an MPLS signaling 1345 protocol." 1346 INDEX { mplsTunnelHopListIndex, 1347 mplsTunnelHopPathOptionIndex, mplsTunnelHopIndex } 1348 ::= { mplsTunnelHopTable 1 } 1350 MplsTunnelHopEntry ::= SEQUENCE { 1351 mplsTunnelHopListIndex MplsPathIndex, 1352 mplsTunnelHopPathOptionIndex MplsPathIndex, 1353 mplsTunnelHopIndex MplsPathIndex, 1354 mplsTunnelHopAddrType INTEGER, 1355 mplsTunnelHopIpv4Addr InetAddressIPv4, 1356 mplsTunnelHopIpv4PrefixLen Unsigned32, 1357 mplsTunnelHopIpv6Addr InetAddressIPv6, 1358 mplsTunnelHopIpv6PrefixLen Unsigned32, 1359 mplsTunnelHopAsNumber Unsigned32, 1360 mplsTunnelHopLspId MplsLSPID, 1361 mplsTunnelHopType INTEGER, 1362 mplsTunnelHopIncludeExclude INTEGER, 1363 mplsTunnelHopPathOptionName DisplayString, 1364 mplsTunnelHopEntryPathComp INTEGER, 1365 mplsTunnelHopRowStatus RowStatus, 1366 mplsTunnelHopStorageType StorageType 1367 } 1369 mplsTunnelHopListIndex OBJECT-TYPE 1370 SYNTAX MplsPathIndex 1371 MAX-ACCESS not-accessible 1372 STATUS current 1373 DESCRIPTION 1374 "Primary index into this table identifying a 1375 particular explicit route object." 1376 ::= { mplsTunnelHopEntry 1 } 1378 mplsTunnelHopPathOptionIndex OBJECT-TYPE 1379 SYNTAX MplsPathIndex 1380 MAX-ACCESS not-accessible 1381 STATUS current 1382 DESCRIPTION 1383 "Secondary index into this table identifying a 1384 particular group of hops representing a particular 1385 configured path. This is otherwise known as a path 1386 option." 1387 ::= { mplsTunnelHopEntry 2 } 1389 mplsTunnelHopIndex OBJECT-TYPE 1390 SYNTAX MplsPathIndex 1391 MAX-ACCESS not-accessible 1392 STATUS current 1393 DESCRIPTION 1394 "Secondary index into this table identifying a 1395 particular hop." 1396 ::= { mplsTunnelHopEntry 3 } 1398 mplsTunnelHopAddrType OBJECT-TYPE 1399 SYNTAX INTEGER { 1400 ipV4(1), 1401 ipV6(2), 1402 asNumber(3), 1403 lspid(4) 1404 } 1405 MAX-ACCESS read-create 1406 STATUS current 1407 DESCRIPTION 1408 "Denotes the address type of this tunnel hop." 1409 DEFVAL { ipV4 } 1410 ::= { mplsTunnelHopEntry 4 } 1412 mplsTunnelHopIpv4Addr OBJECT-TYPE 1413 SYNTAX InetAddressIPv4 1414 MAX-ACCESS read-create 1415 STATUS current 1416 DESCRIPTION 1417 "If mplsTunnelHopAddrType is set to ipV4(1), then 1418 this value will contain the IPv4 address of this 1419 hop. If mplsTunnelHopAddrType is set to lspid(4), 1420 then this value will contain the Ingress LSR Router 1421 ID of the Tunnel. This object is otherwise 1422 insignificant and should contain a value of 0." 1423 ::= { mplsTunnelHopEntry 5 } 1425 mplsTunnelHopIpv4PrefixLen OBJECT-TYPE 1426 SYNTAX Unsigned32 (0..32) 1427 MAX-ACCESS read-create 1428 STATUS current 1429 DESCRIPTION 1430 "If mplsTunnelHopAddrType is ipV4(1), then the prefix 1431 length for this hop's IPv4 address is contained 1432 herein. This object is otherwise insignificant and 1433 should contain a value of 0." 1434 ::= { mplsTunnelHopEntry 6 } 1436 mplsTunnelHopIpv6Addr OBJECT-TYPE 1437 SYNTAX InetAddressIPv6 1438 MAX-ACCESS read-create 1439 STATUS current 1440 DESCRIPTION 1441 "If the mplsTunnelHopAddrType is set to ipV6(2), then 1442 this variable contains the IPv6 address of this 1443 hop. This object is otherwise insignificant and 1444 should contain a value of 0." 1445 ::= { mplsTunnelHopEntry 7 } 1447 mplsTunnelHopIpv6PrefixLen OBJECT-TYPE 1448 SYNTAX Unsigned32 (0..128) 1449 MAX-ACCESS read-create 1450 STATUS current 1451 DESCRIPTION 1452 "If mplsTunnelHopAddrType is set to ipV6(2), this 1453 value will contain the prefix length for this hop's 1454 IPv6 address. This object is otherwise 1455 insignificant and should contain a value of 0." 1456 ::= { mplsTunnelHopEntry 8 } 1458 mplsTunnelHopAsNumber OBJECT-TYPE 1459 SYNTAX Unsigned32 (0..65535) 1460 MAX-ACCESS read-create 1461 STATUS current 1462 DESCRIPTION 1463 "If mplsTunnelHopAddrType is set to asNumber(3), then 1464 this value will contain the AS number of this hop. 1465 This object is otherwise insignificant and should 1466 contain a value of 0 to indicate this fact." 1467 ::= { mplsTunnelHopEntry 9 } 1469 mplsTunnelHopLspId OBJECT-TYPE 1470 SYNTAX MplsLSPID 1471 MAX-ACCESS read-create 1472 STATUS current 1473 DESCRIPTION 1474 "If mplsTunnelHopAddrType is set to lspid(4), then 1475 this value will contain the LSPID of a tunnel of 1476 this hop. The present tunnel being configured is 1477 �tunneled� through this hop (using label stacking). 1478 This object is otherwise insignificant and should 1479 contain a value of 0 to indicate this fact." 1480 ::= { mplsTunnelHopEntry 10 } 1482 mplsTunnelHopType OBJECT-TYPE 1483 SYNTAX INTEGER { 1484 strict(1), 1485 loose(2) 1486 } 1487 MAX-ACCESS read-create 1488 STATUS current 1489 DESCRIPTION 1490 "Denotes whether this tunnel hop is routed in a 1491 strict or loose fashion." 1492 ::= { mplsTunnelHopEntry 11 } 1494 mplsTunnelHopIncludeExclude OBJECT-TYPE 1495 SYNTAX INTEGER { 1496 include(1), 1497 exclude(2) 1498 } 1499 MAX-ACCESS read-create 1500 STATUS current 1501 DESCRIPTION 1502 "If this value is set to include(1), then this 1503 indicates that this hop must be included in the 1504 tunnel's path. If this value is set to exclude(2), 1505 then this hop must be avoided when calculating the 1506 path for this tunnel. The default value of this 1507 object is include(1), so that by default all 1508 indicated hops are included in the CSPF path 1509 computation." 1510 DEFVAL { include } 1511 ::= { mplsTunnelHopEntry 12 } 1513 mplsTunnelHopPathOptionName OBJECT-TYPE 1514 SYNTAX DisplayString 1515 MAX-ACCESS read-create 1516 STATUS current 1517 DESCRIPTION 1518 "The description of this series of hops as they 1519 relate to the 1520 specified path option." 1521 ::= { mplsTunnelHopEntry 13 } 1523 mplsTunnelHopEntryPathComp OBJECT-TYPE 1524 SYNTAX INTEGER { 1525 dynamic(1), -- CSPF computed 1526 explicit(2) -- strict hop 1527 } 1528 MAX-ACCESS read-create 1529 STATUS current 1530 DESCRIPTION 1531 "If this value is set to dynamic, then the user 1532 should only specify the source and destination of 1533 the path and expect that the CSPF will calculate 1534 the remainder of the path. If this value is set to 1535 explicit, the user should specify the entire path 1536 for the tunnel to take. This path may contain 1537 strict or loose hops. Each hop along a specific 1538 path should have this object set to the same value" 1539 ::= { mplsTunnelHopEntry 14 } 1541 mplsTunnelHopRowStatus OBJECT-TYPE 1542 SYNTAX RowStatus 1543 MAX-ACCESS read-create 1544 STATUS current 1545 DESCRIPTION 1546 "This variable is used to create, modify, and/or 1547 delete a row in this table." 1548 ::= { mplsTunnelHopEntry 15 } 1550 mplsTunnelHopStorageType OBJECT-TYPE 1551 SYNTAX StorageType 1552 MAX-ACCESS read-create 1553 STATUS current 1554 DESCRIPTION 1555 "This variable indicates the storage type for this 1556 object." 1557 ::= { mplsTunnelHopEntry 16 } 1559 -- End of mplsTunnelHopTable 1561 -- Begin of mplsTunnelResourceTable 1563 mplsTunnelResourceIndexNext OBJECT-TYPE 1564 SYNTAX Unsigned32 (0.. 2147483647) 1565 MAX-ACCESS read-only 1566 STATUS current 1567 DESCRIPTION 1568 "This object contains the next appropriate value to 1569 be used for mplsTunnelResourceIndex when creating 1570 entries in the mplsTunnelResourceTable. If the 1571 number of unassigned entries is exhausted, a 1572 retrival operation will return a value of 0. This 1573 object may also return a value of 0 when the LSR is 1574 unable to accept conceptual row creation, for 1575 example, if the mplsTunnelTable is implemented as 1576 read-only. To obtain the mplsTunnelResourceIndex 1577 value for a new entry, the manager must first issue 1578 a management protocol retrieval operation to obtain 1579 the current value of this object. The agent should 1580 modify the value to reflect the next unassigned 1581 index after each retrieval operation. After a 1582 manager retrieves a value the agent will determine 1583 through its local policy when this index value will 1584 be made available for reuse." 1585 ::= { mplsTeObjects 5 } 1587 mplsTunnelResourceTable OBJECT-TYPE 1588 SYNTAX SEQUENCE OF MplsTunnelResourceEntry 1589 MAX-ACCESS not-accessible 1590 STATUS current 1591 DESCRIPTION 1592 "The mplsTunnelResourceTable allows a manager to 1593 specify which resources are desired for an MPLS 1594 tunnel. This table also allows several tunnels to 1595 point to a single entry in this table, implying 1596 that these tunnels should share resources." 1597 ::= { mplsTeObjects 6 } 1599 mplsTunnelResourceEntry OBJECT-TYPE 1600 SYNTAX MplsTunnelResourceEntry 1601 MAX-ACCESS not-accessible 1602 STATUS current 1603 DESCRIPTION 1604 "An entry in this table represents a set of resources 1605 for an MPLS tunnel. An entry can be created by a 1606 network administrator or by an SNMP agent as 1607 instructed by any MPLS signaling protocol." 1608 INDEX { mplsTunnelResourceIndex } 1609 ::= { mplsTunnelResourceTable 1 } 1611 MplsTunnelResourceEntry ::= SEQUENCE { 1612 mplsTunnelResourceIndex Unsigned32, 1613 mplsTunnelResourceMaxRate MplsBitRate, 1614 mplsTunnelResourceMeanRate MplsBitRate, 1615 mplsTunnelResourceMaxBurstSize MplsBurstSize, 1616 mplsTunnelResourceMeanBurstSize MplsBurstSize, 1617 mplsTunnelResourceExcessBurstSize MplsBurstSize, 1618 mplsTunnelResourceFrequency INTEGER, 1619 mplsTunnelResourceWeight Unsigned32, 1620 mplsTunnelResourceRowStatus RowStatus, 1621 mplsTunnelResourceStorageType StorageType 1622 } 1624 mplsTunnelResourceIndex OBJECT-TYPE 1625 SYNTAX Unsigned32 (1..2147483647) 1626 MAX-ACCESS not-accessible 1627 STATUS current 1628 DESCRIPTION 1629 "Uniquely identifies this row." 1630 ::= { mplsTunnelResourceEntry 1 } 1632 mplsTunnelResourceMaxRate OBJECT-TYPE 1633 SYNTAX MplsBitRate 1634 UNITS "bits per second" 1635 MAX-ACCESS read-create 1636 STATUS current 1637 DESCRIPTION 1638 "The maximum rate in bits/second. Note that setting 1639 mplsTunnelResourceMaxRate, 1640 mplsTunnelResourceMeanRate, and 1641 mplsTunnelResourceMaxBurstSize to 0 indicates best- 1642 effort treatment. 1643 This object is copied to an instance of 1644 mplsTrafficParamMaxRate in mplsTrafficParamTable 1645 the OID of which is copied into the corresponding 1646 mplsInSegmentTrafficParamPtr." 1647 REFERENCE 1648 "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS 1649 Label Switch Router Management Information Base 1650 Using SMIv2, Internet Draft , July 2000." 1652 ::= { mplsTunnelResourceEntry 2 } 1654 mplsTunnelResourceMeanRate OBJECT-TYPE 1655 SYNTAX MplsBitRate 1656 UNITS "bits per second" 1657 MAX-ACCESS read-create 1658 STATUS current 1659 DESCRIPTION 1660 "This object is copied into an instance of 1661 mplsTrafficParamMeanRate in the 1662 mplsTrafficParamTable. The OID of this table entry 1663 is then copied into the corresponding 1664 mplsInSegmentTrafficParamPtr. 1666 When resource allocation is performed as requested 1667 by this TSpec object, it is copied into an entry in 1668 mplsTrafficParamTable [LSRMIB]: 1670 mplsTunnelInMeanRate to mplsTrafficParamMeanRate. 1671 The OID of this entry is copied to 1672 mplsInSegmentTrafficParamPtr of the corresponding 1673 in-segment entry." 1675 REFERENCE 1676 "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS 1677 Label Switch Router Management Information Base 1678 Using SMIv2, Internet Draft , July 2000." 1680 ::= { mplsTunnelResourceEntry 3 } 1682 mplsTunnelResourceMaxBurstSize OBJECT-TYPE 1683 SYNTAX MplsBurstSize 1684 UNITS "bytes" 1685 MAX-ACCESS read-create 1686 STATUS current 1687 DESCRIPTION 1688 "The maximum burst size in bytes. This object is 1689 copied to mplsInSegmentMaxBurstSize of the 1690 corresponding in-segment. 1692 When resource allocation is performed as requested 1693 by this TSpec object, it is copied into an entry in 1694 mplsTrafficParamTable [LSRMIB]: 1695 mplsTunnelInMaxBurstSize to 1696 mplsTrafficParamMaxBurstSize. The OID of this entry 1697 is copied to mplsInSegmentTrafficParamPtr of the 1698 corresponding in-segment entry." 1699 REFERENCE 1700 "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS 1701 Label Switch Router Management Information Base 1702 Using SMIv2, Internet Draft , July 2000." 1704 ::= { mplsTunnelResourceEntry 4 } 1706 mplsTunnelResourceMeanBurstSize OBJECT-TYPE 1707 SYNTAX MplsBurstSize 1708 UNITS "bytes" 1709 MAX-ACCESS read-create 1710 STATUS current 1711 DESCRIPTION 1712 "The mean burst size in bytes. The implementations 1713 which do not implement this variable must return 0 1714 for this value and must not allow a user to set 1715 this value." 1716 ::= { mplsTunnelResourceEntry 5 } 1718 mplsTunnelResourceExcessBurstSize OBJECT-TYPE 1719 SYNTAX MplsBurstSize 1720 UNITS "bytes" 1721 MAX-ACCESS read-create 1722 STATUS current 1723 DESCRIPTION 1724 "The Excess burst size in bytes. The implementations 1725 which do not implement this variable must return 0 1726 for this value and must not allow a user to set 1727 this value." 1728 REFERENCE 1729 "CR-LDP Specification, Section 4.3." 1730 ::= { mplsTunnelResourceEntry 6 } 1732 mplsTunnelResourceFrequency OBJECT-TYPE 1733 SYNTAX INTEGER { 1734 unspecified(1), 1735 frequent(2), 1736 veryFrequent(3) 1737 } 1738 MAX-ACCESS read-create 1739 STATUS current 1740 DESCRIPTION 1741 "The granularity of the availability of committed 1742 rate. The implementations which do not implement 1743 this variable must return unspecified(1) for this 1744 value and must not allow a user to set this value." 1745 REFERENCE 1746 "CR-LDP Specification, Section 4.3." 1747 ::= { mplsTunnelResourceEntry 7 } 1749 mplsTunnelResourceWeight OBJECT-TYPE 1750 SYNTAX Unsigned32(0..255) 1751 MAX-ACCESS read-create 1752 STATUS current 1753 DESCRIPTION 1754 "The relative weight for using excess bandwidth above 1755 its committed rate. The value of 0 means that 1756 weight is not applicable for the CR-LSP." 1757 REFERENCE 1758 "CR-LDP Specification, Section 4.3." 1759 ::= { mplsTunnelResourceEntry 8 } 1761 mplsTunnelResourceRowStatus OBJECT-TYPE 1762 SYNTAX RowStatus 1763 MAX-ACCESS read-create 1764 STATUS current 1765 DESCRIPTION 1766 "This variable is used to create, modify, and/or 1767 delete a row in this table." 1768 ::= { mplsTunnelResourceEntry 9 } 1770 mplsTunnelResourceStorageType OBJECT-TYPE 1771 SYNTAX StorageType 1772 MAX-ACCESS read-create 1773 STATUS current 1774 DESCRIPTION 1775 "This variable indicates the storage type for this 1776 object." 1777 ::= { mplsTunnelResourceEntry 10 } 1779 -- End mplsTunnelResourceTable 1781 -- Tunnel Actual Route Hop table. 1783 mplsTunnelARHopTable OBJECT-TYPE 1784 SYNTAX SEQUENCE OF MplsTunnelARHopEntry 1785 MAX-ACCESS not-accessible 1786 STATUS current 1787 DESCRIPTION 1788 "The mplsTunnelARHopTable is used to indicate the 1789 hops, strict or loose, for an MPLS tunnel defined 1790 in mplsTunnelTable, as reported by the MPLS 1791 signaling protocol, for the outgoing direction of 1792 the tunnel. Each row in this table is indexed by 1793 mplsTunnelARHopListIndex. Each row also has a 1794 secondary index mplsTunnelARHopIndex, corresponding 1795 to the next hop that this row corresponds to. The 1796 first row in the table is the first hop after the 1797 origination point of the tunnel. In case we want 1798 to specify a particular interface on the 1799 originating LSR of an outgoing tunnel by which we 1800 want packets to exit the LSR, we specify this as 1801 the first hop for this tunnel in 1802 mplsTunnelARHopTable. 1804 Please note that since the information necessary to 1805 build entries within this table are not provided by 1806 some MPLS signaling protocols, implementation of 1807 this table is optional. Furthermore, since the 1808 information in this table is actually provided by 1809 the MPLS signaling protocol after the path has been 1810 set-up, the entries in this table are provided only 1811 for observation, and hence, all variables in this 1812 table are accessible exclusively as read-only." 1813 ::= { mplsTeObjects 7 } 1815 mplsTunnelARHopEntry OBJECT-TYPE 1816 SYNTAX MplsTunnelARHopEntry 1817 MAX-ACCESS not-accessible 1818 STATUS current 1819 DESCRIPTION 1820 "An entry in this table represents a tunnel hop. An 1821 entry is created by a network administrator for 1822 signaled ERLSP set up by an MPLS signaling 1823 protocol." 1824 INDEX { mplsTunnelARHopListIndex, mplsTunnelARHopIndex } 1825 ::= { mplsTunnelARHopTable 1 } 1827 MplsTunnelARHopEntry ::= SEQUENCE { 1828 mplsTunnelARHopListIndex MplsPathIndex, 1829 mplsTunnelARHopIndex MplsPathIndex, 1830 mplsTunnelARHopAddrType INTEGER, 1831 mplsTunnelARHopIpv4Addr InetAddressIPv4, 1832 mplsTunnelARHopIpv4PrefixLen Unsigned32, 1833 mplsTunnelARHopIpv6Addr InetAddressIPv6, 1834 mplsTunnelARHopIpv6PrefixLen Unsigned32, 1835 mplsTunnelARHopAsNumber Unsigned32, 1836 mplsTunnelARHopLspId MplsLSPID 1837 } 1839 mplsTunnelARHopListIndex OBJECT-TYPE 1840 SYNTAX MplsPathIndex 1841 MAX-ACCESS not-accessible 1842 STATUS current 1843 DESCRIPTION 1844 "Primary index into this table identifying a 1845 particular recorded hop list." 1846 ::= { mplsTunnelARHopEntry 1 } 1848 mplsTunnelARHopIndex OBJECT-TYPE 1849 SYNTAX MplsPathIndex 1850 MAX-ACCESS not-accessible 1851 STATUS current 1852 DESCRIPTION 1853 "Secondary index into this table identifying the 1854 particular hop." 1855 ::= { mplsTunnelARHopEntry 2 } 1857 mplsTunnelARHopAddrType OBJECT-TYPE 1858 SYNTAX INTEGER { 1859 ipV4(1), 1860 ipV6(2), 1861 asNumber(3) 1862 } 1863 MAX-ACCESS read-only 1864 STATUS current 1865 DESCRIPTION 1866 "Denotes the address type of this tunnel hop." 1867 DEFVAL { ipV4 } 1868 ::= { mplsTunnelARHopEntry 3 } 1870 mplsTunnelARHopIpv4Addr OBJECT-TYPE 1871 SYNTAX InetAddressIPv4 1872 MAX-ACCESS read-only 1873 STATUS current 1874 DESCRIPTION 1875 "If mplsTunnelARHopAddrType is set to ipV4(1), then 1876 this value will contain the IPv4 address of this 1877 hop. This object is otherwise insignificant and 1878 should contain a value of 0." 1879 ::= { mplsTunnelARHopEntry 4 } 1881 mplsTunnelARHopIpv4PrefixLen OBJECT-TYPE 1882 SYNTAX Unsigned32 (0..32) 1883 MAX-ACCESS read-only 1884 STATUS current 1885 DESCRIPTION 1886 "If mplsTunnelARHopAddrType is ipV4(1), then the 1887 prefix length for this hop's IPv4 address is 1888 contained herein. This object is otherwise 1889 insignificant and should contain a value of 0." 1890 ::= { mplsTunnelARHopEntry 5 } 1892 mplsTunnelARHopIpv6Addr OBJECT-TYPE 1893 SYNTAX InetAddressIPv6 1894 MAX-ACCESS read-only 1895 STATUS current 1896 DESCRIPTION 1897 "If the mplsTunnelARHopAddrType is set to ipV6(2), 1898 then this variable contains the IPv6 address of 1899 this hop. This object is otherwise insignificant 1900 and should contain a value of 0." 1901 ::= { mplsTunnelARHopEntry 6 } 1903 mplsTunnelARHopIpv6PrefixLen OBJECT-TYPE 1904 SYNTAX Unsigned32 (0..128) 1905 MAX-ACCESS read-only 1906 STATUS current 1907 DESCRIPTION 1908 "If mplsTunnelARHopAddrType is set to ipV6(2), this 1909 value will contain the prefix length for this hop's 1910 IPv6 address. This object is otherwise 1911 insignificant and should contain a value of 0." 1912 ::= { mplsTunnelARHopEntry 7 } 1914 mplsTunnelARHopAsNumber OBJECT-TYPE 1915 SYNTAX Unsigned32 (0..65535) 1916 MAX-ACCESS read-only 1917 STATUS current 1918 DESCRIPTION 1919 "If mplsTunnelARHopAddrType is set to asNumber(3), 1920 then this value will contain the AS number of this 1921 hop. This object is otherwise insignificant and 1922 should contain a value of 0 to indicate this fact." 1923 ::= { mplsTunnelARHopEntry 8 } 1925 mplsTunnelARHopLspId OBJECT-TYPE 1926 SYNTAX MplsLSPID 1927 MAX-ACCESS read-only 1928 STATUS current 1929 DESCRIPTION 1930 "If mplsTunnelARHopAddrType is set to lspid(4), then 1931 this value will contain the LSP ID of this hop. 1932 This object is otherwise insignificant and should 1933 contain a value of 0 to indicate this fact." 1934 ::= { mplsTunnelARHopEntry 9 } 1936 -- End of mplsTunnelARHopTable 1938 -- Tunnel Computed Hop table. 1940 mplsTunnelCHopTable OBJECT-TYPE 1941 SYNTAX SEQUENCE OF MplsTunnelCHopEntry 1942 MAX-ACCESS not-accessible 1943 STATUS current 1944 DESCRIPTION 1945 "The mplsTunnelCHopTable is used to indicate the 1946 hops, strict or loose, for an MPLS tunnel defined 1947 in mplsTunnelTable, as computed by a constraint- 1948 based routing protocol, based on the 1949 mplsTunnelHopTable for the outgoing direction of 1950 the tunnel. Each row in this table is indexed by 1951 mplsTunnelCHopListIndex. Each row also has a 1952 secondary index mplsTunnelCHopIndex, corresponding 1953 to the next hop that this row corresponds to. The 1954 first row in the table is the first hop after the 1955 origination point of the tunnel. In case we want 1956 to specify a particular interface on the 1957 originating LSR of an outgoing tunnel by which we 1958 want packets to exit the LSR, we specify this as 1959 the first hop for this tunnel in 1960 mplsTunnelCHopTable. 1962 Please note that since the information necessary to 1963 build entries within this table may not be 1964 supported by some LSRs, implementation of this 1965 table is optional. Furthermore, since the 1966 information in this table is actually provided by 1967 routing protocol after the path has been computed, 1968 the entries in this table are provided only for 1969 observation, and hence, all variables in this table 1970 are accessible exclusively as read-only." 1971 ::= { mplsTeObjects 8 } 1973 mplsTunnelCHopEntry OBJECT-TYPE 1974 SYNTAX MplsTunnelCHopEntry 1975 MAX-ACCESS not-accessible 1976 STATUS current 1977 DESCRIPTION 1978 "An entry in this table represents a tunnel hop. An 1979 entry in this table is created by a constraint- 1980 based routing protocol based on the hops specified 1981 in the corresponding mplsTunnelHopTable." 1982 INDEX { mplsTunnelCHopListIndex, mplsTunnelCHopIndex } 1983 ::= { mplsTunnelCHopTable 1 } 1985 MplsTunnelCHopEntry ::= SEQUENCE { 1986 mplsTunnelCHopListIndex MplsPathIndex, 1987 mplsTunnelCHopIndex MplsPathIndex, 1988 mplsTunnelCHopAddrType INTEGER, 1989 mplsTunnelCHopIpv4Addr InetAddressIPv4, 1990 mplsTunnelCHopIpv4PrefixLen Unsigned32, 1991 mplsTunnelCHopIpv6Addr InetAddressIPv6, 1992 mplsTunnelCHopIpv6PrefixLen Unsigned32, 1993 mplsTunnelCHopAsNumber Unsigned32, 1994 mplsTunnelCHopType INTEGER 1995 } 1997 mplsTunnelCHopListIndex OBJECT-TYPE 1998 SYNTAX MplsPathIndex 1999 MAX-ACCESS not-accessible 2000 STATUS current 2001 DESCRIPTION 2002 "Primary index into this table identifying a 2003 particular computed hop list." 2004 ::= { mplsTunnelCHopEntry 1 } 2006 mplsTunnelCHopIndex OBJECT-TYPE 2007 SYNTAX MplsPathIndex 2008 MAX-ACCESS not-accessible 2009 STATUS current 2010 DESCRIPTION 2011 "Secondary index into this table identifying the 2012 particular hop." 2013 ::= { mplsTunnelCHopEntry 2 } 2015 mplsTunnelCHopAddrType OBJECT-TYPE 2016 SYNTAX INTEGER { 2017 ipV4(1), 2018 ipV6(2), 2019 asNumber(3) 2020 } 2021 MAX-ACCESS read-only 2022 STATUS current 2023 DESCRIPTION 2024 "Denotes the address type of this tunnel hop." 2025 DEFVAL { ipV4 } 2026 ::= { mplsTunnelCHopEntry 3 } 2028 mplsTunnelCHopIpv4Addr OBJECT-TYPE 2029 SYNTAX InetAddressIPv4 2030 MAX-ACCESS read-only 2031 STATUS current 2032 DESCRIPTION 2033 "If mplsTunnelCHopAddrType is set to ipV4(1), then 2034 this value will contain the IPv4 address of this 2035 hop. This object is otherwise insignificant and 2036 should contain a value of 0." 2037 ::= { mplsTunnelCHopEntry 4 } 2039 mplsTunnelCHopIpv4PrefixLen OBJECT-TYPE 2040 SYNTAX Unsigned32 (0..32) 2041 MAX-ACCESS read-only 2042 STATUS current 2043 DESCRIPTION 2044 "If mplsTunnelCHopAddrType is ipV4(1), then the 2045 prefix length for this hop's IPv4 address is 2046 contained herein. This object is otherwise 2047 insignificant and should contain a value of 0." 2048 ::= { mplsTunnelCHopEntry 5 } 2050 mplsTunnelCHopIpv6Addr OBJECT-TYPE 2051 SYNTAX InetAddressIPv6 2052 MAX-ACCESS read-only 2053 STATUS current 2054 DESCRIPTION 2055 "If the mplsTunnelCHopAddrType is set to ipV6(2), 2056 then this variable contains the IPv6 address of 2057 this hop. This object is otherwise insignificant 2058 and should contain a value of 0." 2059 ::= { mplsTunnelCHopEntry 6 } 2061 mplsTunnelCHopIpv6PrefixLen OBJECT-TYPE 2062 SYNTAX Unsigned32 (0..128) 2063 MAX-ACCESS read-only 2064 STATUS current 2065 DESCRIPTION 2066 "If mplsTunnelCHopAddrType is set to ipV6(2), this 2067 value will contain the prefix length for this hop's 2068 IPv6 address. This object is otherwise 2069 insignificant and should contain a value of 0." 2070 ::= { mplsTunnelCHopEntry 7 } 2072 mplsTunnelCHopAsNumber OBJECT-TYPE 2073 SYNTAX Unsigned32 (0..65535) 2074 MAX-ACCESS read-only 2075 STATUS current 2076 DESCRIPTION 2077 "If mplsTunnelCHopAddrType is set to asNumber(3), 2078 then this value will contain the AS number of this 2079 hop. This object is otherwise insignificant and 2080 should contain a value of 0 to indicate this fact." 2081 ::= { mplsTunnelCHopEntry 8 } 2083 mplsTunnelCHopType OBJECT-TYPE 2084 SYNTAX INTEGER { 2085 strict(1), 2086 loose(2) 2087 } 2088 MAX-ACCESS read-only 2089 STATUS current 2090 DESCRIPTION 2091 "Denotes whether this is tunnel hop is routed in a 2092 strict or loose fashion." 2093 ::= { mplsTunnelCHopEntry 9 } 2095 -- End of mplsTunnelCHopTable 2097 -- MPLS Tunnel Performance Table. 2099 mplsTunnelPerfTable OBJECT-TYPE 2100 SYNTAX SEQUENCE OF MplsTunnelPerfEntry 2101 MAX-ACCESS not-accessible 2102 STATUS current 2103 DESCRIPTION 2104 "This table provides per-tunnel MPLS performance 2105 information." 2106 ::= { mplsTeObjects 9 } 2108 mplsTunnelPerfEntry OBJECT-TYPE 2109 SYNTAX MplsTunnelPerfEntry 2110 MAX-ACCESS not-accessible 2111 STATUS current 2112 DESCRIPTION 2113 "An entry in this table is created by the LSR for 2114 every tunnel. Its is an extension to 2115 mplsTunnelEntry." 2116 AUGMENTS { mplsTunnelEntry } 2117 ::= { mplsTunnelPerfTable 1 } 2119 MplsTunnelPerfEntry ::= SEQUENCE { 2120 mplsTunnelPerfPackets Counter32, 2121 mplsTunnelPerfHCPackets Counter64, 2122 mplsTunnelPerfErrors Counter32, 2123 mplsTunnelPerfBytes Counter32, 2124 mplsTunnelPerfHCBytes Counter64 2125 } 2127 mplsTunnelPerfPackets OBJECT-TYPE 2128 SYNTAX Counter32 2129 MAX-ACCESS read-only 2130 STATUS current 2131 DESCRIPTION 2132 "Number of packets forwarded by the tunnel." 2133 ::= { mplsTunnelPerfEntry 1 } 2135 mplsTunnelPerfHCPackets OBJECT-TYPE 2136 SYNTAX Counter64 2137 MAX-ACCESS read-only 2138 STATUS current 2139 DESCRIPTION 2140 "High capacity counter for number of packets 2141 forwarded by the tunnel." 2142 ::= { mplsTunnelPerfEntry 2 } 2144 mplsTunnelPerfErrors OBJECT-TYPE 2145 SYNTAX Counter32 2146 MAX-ACCESS read-only 2147 STATUS current 2148 DESCRIPTION 2149 "Number of errored packets." 2150 ::= { mplsTunnelPerfEntry 3 } 2152 mplsTunnelPerfBytes OBJECT-TYPE 2153 SYNTAX Counter32 2154 MAX-ACCESS read-only 2155 STATUS current 2156 DESCRIPTION 2157 "Number of bytes forwarded by the tunnel." 2158 ::= { mplsTunnelPerfEntry 4 } 2160 mplsTunnelPerfHCBytes OBJECT-TYPE 2161 SYNTAX Counter64 2162 MAX-ACCESS read-only 2163 STATUS current 2164 DESCRIPTION 2165 "High capacity counter for number of bytes forwarded 2166 by the tunnel." 2167 ::= { mplsTunnelPerfEntry 5 } 2169 -- End of mplsTunnelPerfTable 2171 -- CR-LDP Tunnel Resource Table 2173 mplsTunnelCRLDPResTable OBJECT-TYPE 2174 SYNTAX SEQUENCE OF MplsTunnelCRLDPResEntry 2175 MAX-ACCESS not-accessible 2176 STATUS current 2177 DESCRIPTION 2178 "The mplsTunnelCRLDPResTable allows a manager to 2179 specify which CR-LDP-specific resources are desired 2180 for an MPLS tunnel if that tunnel is signaled using 2181 CR-LDP. Note that these attributes are in addition 2182 to those specified in mplsTunnelResourceTable. This 2183 table also allows several tunnels to point to a 2184 single entry in this table, implying that these 2185 tunnels should share resources." 2186 ::= { mplsTeObjects 10 } 2188 mplsTunnelCRLDPResEntry OBJECT-TYPE 2189 SYNTAX MplsTunnelCRLDPResEntry 2190 MAX-ACCESS not-accessible 2191 STATUS current 2192 DESCRIPTION 2193 "An entry in this table represents a set of resources 2194 for an MPLS tunnel established using CRLDP 2195 (mplsTunnelSignallingProto equal to crldp (3)). An 2196 entry can be created by a network administrator or 2197 by an SNMP agent as instructed by any MPLS 2198 signaling protocol." 2199 INDEX { mplsTunnelResourceIndex } 2200 ::= { mplsTunnelCRLDPResTable 1 } 2202 MplsTunnelCRLDPResEntry ::= SEQUENCE { 2203 mplsTunnelCRLDPResMeanBurstSize MplsBurstSize, 2204 mplsTunnelCRLDPResExcessBurstSize MplsBurstSize, 2205 mplsTunnelCRLDPResFrequency Integer32, 2206 mplsTunnelCRLDPResWeight Unsigned32, 2207 mplsTunnelCRLDPResFlags Unsigned32, 2208 mplsTunnelCRLDPResRowStatus RowStatus, 2209 mplsTunnelCRLDPResStorageType StorageType 2210 } 2212 mplsTunnelCRLDPResMeanBurstSize OBJECT-TYPE 2213 SYNTAX MplsBurstSize 2214 UNITS "bytes" 2215 MAX-ACCESS read-create 2216 STATUS current 2217 DESCRIPTION 2218 "The mean burst size in bytes." 2219 DEFVAL { 0 } 2220 ::= { mplsTunnelCRLDPResEntry 2 } 2222 mplsTunnelCRLDPResExcessBurstSize OBJECT-TYPE 2223 SYNTAX MplsBurstSize 2224 UNITS "bytes" 2225 MAX-ACCESS read-create 2226 STATUS current 2227 DESCRIPTION 2228 "The Excess burst size in bytes." 2229 REFERENCE 2230 "CR-LDP Specification, Section 4.3." 2231 DEFVAL { 0 } 2232 ::= { mplsTunnelCRLDPResEntry 3 } 2234 mplsTunnelCRLDPResFrequency OBJECT-TYPE 2235 SYNTAX INTEGER { 2236 unspecified(1), 2237 frequent(2), 2238 veryFrequent(3) 2239 } 2240 MAX-ACCESS read-create 2241 STATUS current 2242 DESCRIPTION 2243 "The granularity of the availability of committed 2244 rate." 2245 REFERENCE 2246 "CR-LDP Specification, Section 4.3." 2247 ::= { mplsTunnelCRLDPResEntry 4 } 2249 mplsTunnelCRLDPResWeight OBJECT-TYPE 2250 SYNTAX Unsigned32(0..255) 2251 MAX-ACCESS read-create 2252 STATUS current 2253 DESCRIPTION 2254 "The relative weight for using excess bandwidth above 2255 its committed rate. The value of 0 means that 2256 weight is not applicable for the CR-LSP." 2257 REFERENCE 2258 "CR-LDP Specification, Section 4.3." 2259 DEFVAL { 0 } 2260 ::= { mplsTunnelCRLDPResEntry 5 } 2262 mplsTunnelCRLDPResFlags OBJECT-TYPE 2263 SYNTAX Unsigned32 (0..63) 2264 MAX-ACCESS read-create 2265 STATUS current 2266 DESCRIPTION 2267 "The value of the 1 byte Flags conveyed as part of 2268 the traffic parameters during the establishment of 2269 the CRLSP. The bits in this object are to be 2270 interpreted as follows. 2272 +--+--+--+--+--+--+--+--+ 2273 | Res |F6|F5|F4|F3|F2|F1| 2274 +--+--+--+--+--+--+--+--+ 2276 Res - These bits are reserved. Zero on transmission. 2277 Ignored on receipt. 2278 F1 - Corresponds to the PDR. 2279 F2 - Corresponds to the PBS. 2280 F3 - Corresponds to the CDR. 2281 F4 - Corresponds to the CBS. 2282 F5 - Corresponds to the EBS. 2283 F6 - Corresponds to the Weight. 2285 Each flag if is a Negotiable Flag corresponding to a 2286 Traffic Parameter. The Negotiable Flag value zero 2287 denotes Not Negotiable and value one denotes 2288 Negotiable." 2289 REFERENCE 2290 "Section 4.3, Constraint-Based LSP Setup using LDP, 2291 Jamoussi, et. al,, 2292 July 2000." 2293 DEFVAL { 0 } 2294 ::= { mplsTunnelCRLDPResEntry 6 } 2296 mplsTunnelCRLDPResRowStatus OBJECT-TYPE 2297 SYNTAX RowStatus 2298 MAX-ACCESS read-create 2299 STATUS current 2300 DESCRIPTION 2301 "This variable is used to create, modify, and/or 2302 delete a row in this table." 2303 ::= { mplsTunnelCRLDPResEntry 7 } 2305 mplsTunnelCRLDPResStorageType OBJECT-TYPE 2306 SYNTAX StorageType 2307 MAX-ACCESS read-create 2308 STATUS current 2309 DESCRIPTION 2310 "This variable indicates the storage type for this 2311 object." 2312 ::= { mplsTunnelCRLDPResEntry 8 } 2314 -- Notifications. 2316 mplsTunnelTrapEnable OBJECT-TYPE 2317 SYNTAX TruthValue 2318 MAX-ACCESS read-write 2319 STATUS current 2320 DESCRIPTION 2321 "If this object is true, then it enables the 2322 generation of mplsTunnelUp and mplsTunnelDown 2323 traps, otherwise these traps are not emitted." 2324 DEFVAL { false } 2325 ::= { mplsTeObjects 11 } 2327 mplsTunnelUp NOTIFICATION-TYPE 2328 OBJECTS { 2329 mplsTunnelIndex, 2330 mplsTunnelInstance, 2331 mplsTunnelIngressLSRId, 2332 mplsTunnelEgressLSRId, 2333 mplsTunnelAdminStatus, 2334 mplsTunnelOperStatus 2335 } 2336 STATUS current 2337 DESCRIPTION 2338 "This notification is generated when a 2339 mplsTunnelOperStatus object for one of the 2340 configured tunnels is about to leave the down state 2341 and transition into some other state (but not into 2342 the notPresent state). This other state is 2343 indicated by the included value of 2344 mplsTunnelOperStatus." 2345 ::= { mplsTeNotifyPrefix 1 } 2347 mplsTunnelDown NOTIFICATION-TYPE 2348 OBJECTS { 2349 mplsTunnelIndex, 2350 mplsTunnelInstance, 2351 mplsTunnelIngressLSRId, 2352 mplsTunnelEgressLSRId, 2353 mplsTunnelAdminStatus, 2354 mplsTunnelOperStatus 2355 } 2356 STATUS current 2357 DESCRIPTION 2358 "This notification is generated when a 2359 mplsTunnelOperStatus object for one of the 2360 configured tunnels is about to enter the down state 2361 from some other state (but not from the notPresent 2362 state). This other state is indicated by the 2363 included value of mplsTunnelOperStatus." 2364 ::= { mplsTeNotifyPrefix 2 } 2366 mplsTunnelRerouted NOTIFICATION-TYPE 2367 OBJECTS { 2368 mplsTunnelIndex, 2369 mplsTunnelInstance, 2370 mplsTunnelIngressLSRId, 2371 mplsTunnelEgressLSRId, 2372 mplsTunnelAdminStatus, 2373 mplsTunnelOperStatus 2374 } 2375 STATUS current 2376 DESCRIPTION 2377 "This notification is generated when a tunnel is 2378 rerouted. If the actual path is used, then this 2379 object MAY contain the new path for this tunnel 2380 some time after this trap is issued by the agent." 2381 ::= { mplsTeNotifyPrefix 3 } 2383 mplsTunnelReoptimized NOTIFICATION-TYPE 2384 OBJECTS { 2385 mplsTunnelIndex, 2386 mplsTunnelInstance, 2387 mplsTunnelIngressLSRId, 2388 mplsTunnelEgressLSRId, 2389 mplsTunnelAdminStatus, 2390 mplsTunnelOperStatus 2391 } 2392 STATUS current 2393 DESCRIPTION 2394 "This notification is generated when a tunnel is 2395 reoptimized. If the actual path is used, then this 2396 object MAY contain the new path for this tunnel 2397 some time after this trap is issued by the agent." 2398 ::= { mplsTeNotifyPrefix 4 } 2400 -- End of notifications. 2402 -- Module compliance. 2404 mplsTeGroups 2405 OBJECT IDENTIFIER ::= { mplsTeConformance 1 } 2407 mplsTeCompliances 2408 OBJECT IDENTIFIER ::= { mplsTeConformance 2 } 2410 mplsTeModuleCompliance MODULE-COMPLIANCE 2411 STATUS current 2412 DESCRIPTION 2413 "Compliance statement for agents that support the 2414 MPLS TE MIB." 2415 MODULE -- this module 2417 -- The mandatory group has to be implemented by all 2418 -- LSRs that originate/terminate ESLSPs/tunnels. 2419 -- In addition, depending on the type of tunnels 2420 -- supported, other groups become mandatory as 2421 -- explained below. 2423 MANDATORY-GROUPS { 2424 mplsTunnelGroup, 2425 mplsTunnelScalarGroup 2426 } 2428 GROUP mplsTunnelManualGroup 2429 DESCRIPTION 2430 "This group is mandatory for devices which support 2431 manual configuration of tunnels, in addition to 2432 mplsTunnelGroup. The following constraints apply: 2433 mplsTunnelSignallingProto should be at least read- 2434 only with a value of none(1)." 2436 GROUP mplsTunnelSignaledGroup 2437 DESCRIPTION 2438 "This group is mandatory for devices which support 2439 signaled tunnel set up, in addition to 2440 mplsTunnelGroup. The following constraints apply: 2441 mplsTunnelSignallingProto should be at least read- 2442 only returning a value of ldp(2), or rsvp(3)." 2444 GROUP mplsTunnelIsNotIntfcGroup 2445 DESCRIPTION 2446 "This group is mandatory for devices which support 2447 tunnels that are not interfaces, in addition to 2448 mplsTunnelGroup. The following constraints apply: 2449 mplsTunnelIsIf must at least be read-only 2450 returning false(1)." 2452 GROUP mplsTunnelIsIntfcGroup 2453 DESCRIPTION 2454 "This group is mandatory for devices which support 2455 tunnels that are interfaces, in addition to 2456 mplsTunnelGroup. The following constraints apply: 2457 mplsTunnelIsIf must at least be read-only 2458 returning true(2)." 2460 GROUP mplsTunnelOptionalGroup 2461 DESCRIPTION 2462 "Objects in this group are optional." 2464 -- mplsTunnelTable 2466 OBJECT mplsTunnelName 2467 MIN-ACCESS read-only 2468 DESCRIPTION 2469 "Write access is not required." 2471 OBJECT mplsTunnelDescr 2472 MIN-ACCESS read-only 2473 DESCRIPTION 2474 "Write access is not required." 2476 OBJECT mplsTunnelIsIf 2477 MIN-ACCESS read-only 2478 DESCRIPTION 2479 "Write access is not required." 2481 OBJECT mplsTunnelIfIndex 2482 DESCRIPTION 2483 "Write access is not required." 2485 OBJECT mplsTunnelXCPointer 2486 MIN-ACCESS read-only 2487 DESCRIPTION 2488 "Write access is not required." 2490 OBJECT mplsTunnelSignallingProto 2491 MIN-ACCESS read-only 2492 DESCRIPTION 2493 "Write access is not required." 2495 OBJECT mplsTunnelSetupPrio 2496 MIN-ACCESS read-only 2497 DESCRIPTION 2498 "Write access is not required." 2500 OBJECT mplsTunnelHoldingPrio 2501 MIN-ACCESS read-only 2502 DESCRIPTION 2503 "Write access is not required." 2505 OBJECT mplsTunnelSessionAttributes 2506 MIN-ACCESS read-only 2507 DESCRIPTION 2508 "Write access is not required." 2510 OBJECT mplsTunnelOwner 2511 MIN-ACCESS read-only 2512 DESCRIPTION 2513 "Write access is not required." 2515 OBJECT mplsTunnelLocalProtectInUse 2516 MIN-ACCESS read-only 2517 DESCRIPTION 2518 "Write access is not required." 2520 OBJECT mplsTunnelResourcePointer 2521 MIN-ACCESS read-only 2522 DESCRIPTION 2523 "Write access is not required." 2525 OBJECT mplsTunnelInstancePriority 2526 MIN-ACCESS read-only 2527 DESCRIPTION 2528 "Write access is not required." 2530 OBJECT mplsTunnelHopTableIndex 2531 MIN-ACCESS read-only 2532 DESCRIPTION 2533 "Write access is not required." 2535 OBJECT mplsTunnelPrimaryInstance 2536 MIN-ACCESS read-only 2537 DESCRIPTION 2538 "Write access is not required." 2540 OBJECT mplsTunnelPrimaryTimeUp 2541 MIN-ACCESS read-only 2542 DESCRIPTION 2543 "Write access is not required." 2545 OBJECT mplsTunnelPathChanges 2546 MIN-ACCESS read-only 2547 DESCRIPTION 2548 "Write access is not required." 2550 OBJECT mplsTunnelLastPathChange 2551 MIN-ACCESS read-only 2552 DESCRIPTION 2553 "Write access is not required." 2555 OBJECT mplsTunnelCreationTime 2556 MIN-ACCESS read-only 2557 DESCRIPTION 2558 "Write access is not required." 2560 OBJECT mplsTunnelStateTransitions 2561 MIN-ACCESS read-only 2562 DESCRIPTION 2563 "Write access is not required." 2565 OBJECT mplsTunnelARHopTableIndex 2566 DESCRIPTION 2567 "Write access is not required." 2569 OBJECT mplsTunnelCHopTableIndex 2570 DESCRIPTION 2571 "Write access is not required." 2573 OBJECT mplsTunnelAdminStatus 2574 SYNTAX INTEGER { up (1), down (2) } 2575 MIN-ACCESS read-only 2576 DESCRIPTION 2577 "Only up and down states must be supported. Write 2578 access is not required." 2580 OBJECT mplsTunnelOperStatus 2581 SYNTAX INTEGER { up (1), down (2) } 2582 DESCRIPTION 2583 "Only up and down states must be supported. Write 2584 access is not required." 2586 OBJECT mplsTunnelRowStatus 2587 SYNTAX INTEGER { 2588 active(1), 2589 notInService(2), 2590 createAndGo(4), 2591 destroy(6) 2592 } 2593 MIN-ACCESS read-only 2594 DESCRIPTION 2595 "The notReady(3) and createAndWait(5) states need 2596 not be supported. Write access is not required." 2598 OBJECT mplsTunnelStorageType 2599 SYNTAX INTEGER { other(1) } 2600 MIN-ACCESS read-only 2601 DESCRIPTION 2602 "Only other (1) needs to be supported." 2604 OBJECT mplsTunnelPathInUse 2605 MIN-ACCESS read-only 2606 DESCRIPTION 2607 "Read-only support is required." 2609 OBJECT mplsTunnelRole 2610 SYNTAX INTEGER { head(1) } 2611 MIN-ACCESS read-only 2612 DESCRIPTION 2613 "Only support for head is required." 2615 OBJECT mplsTunnelTotalUpTime 2616 MIN-ACCESS read-only 2617 DESCRIPTION 2618 "Read-only support is required." 2620 OBJECT mplsTunnelInstanceUpTime 2621 MIN-ACCESS read-only 2622 DESCRIPTION 2623 "Read-only support is required." 2625 -- mplsTunnelHopTable 2627 OBJECT mplsTunnelHopAddrType 2628 MIN-ACCESS read-only 2629 DESCRIPTION 2630 "Write access is not required." 2632 OBJECT mplsTunnelHopIpv4Addr 2633 MIN-ACCESS read-only 2634 DESCRIPTION 2635 "Write access is not required." 2637 OBJECT mplsTunnelHopIpv4PrefixLen 2638 MIN-ACCESS read-only 2639 DESCRIPTION 2640 "Write access is not required." 2642 OBJECT mplsTunnelHopIpv6Addr 2643 MIN-ACCESS read-only 2644 DESCRIPTION 2645 "Write access is not required." 2647 OBJECT mplsTunnelHopIpv6PrefixLen 2648 MIN-ACCESS read-only 2649 DESCRIPTION 2650 "Write access is not required." 2652 OBJECT mplsTunnelHopAsNumber 2653 MIN-ACCESS read-only 2654 DESCRIPTION 2655 "Write access is not required." 2657 OBJECT mplsTunnelHopLspId 2658 MIN-ACCESS read-only 2659 DESCRIPTION 2660 "Write access is not required." 2662 OBJECT mplsTunnelHopType 2663 SYNTAX INTEGER { strict(1) } 2664 MIN-ACCESS read-only 2665 DESCRIPTION 2666 "loose(2) need not be supported. Write access is 2667 not required." 2669 OBJECT mplsTunnelHopIncludeExclude 2670 MIN-ACCESS read-only 2671 DESCRIPTION 2672 "Write access is not required." 2674 OBJECT mplsTunnelHopPathOptionName 2675 MIN-ACCESS read-only 2676 DESCRIPTION 2677 "Write access is not required." 2679 OBJECT mplsTunnelHopEntryPathComp 2680 MIN-ACCESS read-only 2681 DESCRIPTION 2682 "Write access is not required." 2684 OBJECT mplsTunnelHopRowStatus 2685 SYNTAX INTEGER { 2686 active(1), 2687 notInService(2), 2688 createAndGo(4), 2689 destroy(6) 2690 } 2691 MIN-ACCESS read-only 2692 DESCRIPTION 2693 "The notReady(3) and createAndWait(5) states need 2694 not be supported. Write access is not required." 2696 OBJECT mplsTunnelHopStorageType 2697 SYNTAX INTEGER { other(1) } 2698 MIN-ACCESS read-only 2699 DESCRIPTION 2700 "Only other (1) needs to be supported." 2702 -- mplsTunnelResourceTable 2704 OBJECT mplsTunnelResourceMaxRate 2705 MIN-ACCESS read-only 2706 DESCRIPTION 2707 "Write access is not required." 2709 OBJECT mplsTunnelResourceMeanRate 2710 MIN-ACCESS read-only 2711 DESCRIPTION 2712 "Write access is not required." 2714 OBJECT mplsTunnelResourceMaxBurstSize 2715 MIN-ACCESS read-only 2716 DESCRIPTION 2717 "Write access is not required." 2719 OBJECT mplsTunnelResourceMeanBurstSize 2720 MIN-ACCESS read-only 2721 DESCRIPTION 2722 "Write access is not required." 2724 OBJECT mplsTunnelResourceExcessBurstSize 2725 MIN-ACCESS read-only 2726 DESCRIPTION 2727 "Write access is not required." 2729 OBJECT mplsTunnelResourceFrequency 2730 MIN-ACCESS read-only 2731 DESCRIPTION 2732 "Write access is not required." 2734 OBJECT mplsTunnelResourceWeight 2735 MIN-ACCESS read-only 2736 DESCRIPTION 2737 "Write access is not required." 2739 OBJECT mplsTunnelResourceRowStatus 2740 SYNTAX INTEGER { 2741 active(1), 2742 notInService(2), 2743 createAndGo(4), 2744 destroy(6) 2745 } 2746 MIN-ACCESS read-only 2747 DESCRIPTION 2748 "The notReady(3) and createAndWait(5) states need 2749 not be supported. Write access is not required." 2751 OBJECT mplsTunnelResourceStorageType 2752 SYNTAX INTEGER { other(1) } 2753 MIN-ACCESS read-only 2754 DESCRIPTION 2755 "Only other (1) needs to be supported." 2757 -- mplsTunnelPerfTable 2759 OBJECT mplsTunnelPerfPackets 2760 MIN-ACCESS read-only 2761 DESCRIPTION 2762 "Write access is not required." 2764 OBJECT mplsTunnelPerfHCPackets 2765 MIN-ACCESS read-only 2766 DESCRIPTION 2767 "Write access is not required." 2769 OBJECT mplsTunnelPerfErrors 2770 MIN-ACCESS read-only 2771 DESCRIPTION 2772 "Write access is not required." 2774 OBJECT mplsTunnelPerfBytes 2775 MIN-ACCESS read-only 2776 DESCRIPTION 2777 "Write access is not required." 2779 OBJECT mplsTunnelPerfHCBytes 2780 MIN-ACCESS read-only 2781 DESCRIPTION 2782 "Write access is not required." 2784 ::= { mplsTeCompliances 1 } 2786 -- Units of conformance. 2788 mplsTunnelGroup OBJECT-GROUP 2789 OBJECTS { 2790 mplsTunnelIndexNext, 2791 mplsTunnelName, 2792 mplsTunnelDescr, 2793 mplsTunnelOwner, 2794 mplsTunnelXCPointer, 2795 mplsTunnelIfIndex, 2796 mplsTunnelHopTableIndex, 2797 mplsTunnelARHopTableIndex, 2798 mplsTunnelCHopTableIndex, 2799 mplsTunnelAdminStatus, 2800 mplsTunnelOperStatus, 2801 mplsTunnelRowStatus, 2802 mplsTunnelTrapEnable, 2803 mplsTunnelStorageType, 2804 mplsTunnelConfigured, 2805 mplsTunnelActive, 2806 mplsTunnelPrimaryInstance, 2807 mplsTunnelPrimaryTimeUp, 2808 mplsTunnelPathChanges, 2809 mplsTunnelLastPathChange, 2810 mplsTunnelCreationTime, 2811 mplsTunnelStateTransitions, 2812 mplsTunnelEgressLSRId, 2813 mplsTunnelIncludeAnyAffinity, 2814 mplsTunnelIncludeAllAffinity, 2815 mplsTunnelExcludeAllAffinity, 2816 mplsTunnelPerfPackets, 2817 mplsTunnelPerfHCPackets, 2818 mplsTunnelPerfErrors, 2819 mplsTunnelPerfBytes, 2820 mplsTunnelPerfHCBytes, 2821 mplsTunnelResourcePointer, 2822 mplsTunnelInstancePriority, 2823 mplsTunnelPathInUse, 2824 mplsTunnelRole, 2825 mplsTunnelTotalUpTime, 2826 mplsTunnelInstanceUpTime 2827 } 2828 STATUS current 2829 DESCRIPTION 2830 "Necessary, but not sufficient, set of objects to 2831 implement tunnels. In addition, depending on the 2832 type of the tunnels supported (for example, 2833 manually configured or signaled, persistent or non- 2834 persistent, etc.), the following other groups 2835 defined below are mandatory: mplsTunnelManualGroup 2836 and/or mplsTunnelSignaledGroup, 2837 mplsTunnelIsNotIntfcGroup and/or 2838 mplsTunnelIsIntfcGroup." 2839 ::= { mplsTeGroups 1 } 2841 mplsTunnelManualGroup OBJECT-GROUP 2842 OBJECTS { mplsTunnelSignallingProto } 2843 STATUS current 2844 DESCRIPTION 2845 "Object(s) needed to implement manually configured 2846 tunnels." 2847 ::= { mplsTeGroups 2 } 2849 mplsTunnelSignaledGroup OBJECT-GROUP 2850 OBJECTS { 2851 mplsTunnelSetupPrio, 2852 mplsTunnelHoldingPrio, 2853 mplsTunnelSignallingProto, 2854 mplsTunnelLocalProtectInUse, 2855 mplsTunnelSessionAttributes, 2856 mplsTunnelHopListIndexNext, 2857 mplsTunnelHopAddrType, 2858 mplsTunnelHopIpv4Addr, 2859 mplsTunnelHopIpv4PrefixLen, 2860 mplsTunnelHopIpv6Addr, 2861 mplsTunnelHopIpv6PrefixLen, 2862 mplsTunnelHopAsNumber, 2863 mplsTunnelHopLspId, 2864 mplsTunnelHopType, 2865 mplsTunnelHopIncludeExclude, 2866 mplsTunnelHopPathOptionName, 2867 mplsTunnelHopEntryPathComp, 2868 mplsTunnelHopRowStatus, 2869 mplsTunnelHopStorageType 2870 } 2871 STATUS current 2872 DESCRIPTION 2873 "Object needed to implement signaled tunnels." 2874 ::= { mplsTeGroups 3 } 2876 mplsTunnelScalarGroup OBJECT-GROUP 2877 OBJECTS { 2878 mplsTunnelConfigured, 2879 mplsTunnelActive, 2880 mplsTunnelTEDistProto, 2881 mplsTunnelMaxHops 2882 } 2883 STATUS current 2884 DESCRIPTION 2885 "Scalar object needed to implement MPLS tunnels." 2886 ::= { mplsTeGroups 4 } 2888 mplsTunnelIsIntfcGroup OBJECT-GROUP 2889 OBJECTS { mplsTunnelIsIf } 2890 STATUS current 2891 DESCRIPTION 2892 "Objects needed to implement tunnels that are 2893 interfaces." 2894 ::= { mplsTeGroups 5 } 2896 mplsTunnelIsNotIntfcGroup OBJECT-GROUP 2897 OBJECTS { mplsTunnelIsIf } 2898 STATUS current 2899 DESCRIPTION 2900 "Objects needed to implement tunnels that are not 2901 interfaces." 2902 ::= { mplsTeGroups 6 } 2904 mplsTunnelOptionalGroup OBJECT-GROUP 2905 OBJECTS { 2906 mplsTunnelResourceIndexNext, 2907 mplsTunnelResourceMaxRate, 2908 mplsTunnelResourceMeanRate, 2909 mplsTunnelResourceMaxBurstSize, 2910 mplsTunnelResourceMeanBurstSize, 2911 mplsTunnelResourceExcessBurstSize, 2912 mplsTunnelResourceFrequency, 2913 mplsTunnelResourceWeight, 2914 mplsTunnelResourceRowStatus, 2915 mplsTunnelResourceStorageType, 2916 mplsTunnelARHopAddrType, 2917 mplsTunnelARHopIpv4Addr, 2918 mplsTunnelARHopIpv4PrefixLen, 2919 mplsTunnelARHopIpv6Addr, 2920 mplsTunnelARHopIpv6PrefixLen, 2921 mplsTunnelARHopAsNumber, 2922 mplsTunnelCHopAddrType, 2923 mplsTunnelCHopIpv4Addr, 2924 mplsTunnelCHopIpv4PrefixLen, 2925 mplsTunnelCHopIpv6Addr, 2926 mplsTunnelCHopIpv6PrefixLen, 2927 mplsTunnelCHopAsNumber, 2928 mplsTunnelCHopType 2929 } 2930 STATUS current 2931 DESCRIPTION 2932 "The objects in this group are optional." 2933 ::= { mplsTeGroups 7 } 2935 mplsTunnelCRLDPResOptionalGroup OBJECT-GROUP 2936 OBJECTS { 2937 mplsTunnelCRLDPResMeanBurstSize, 2938 mplsTunnelCRLDPResExcessBurstSize, 2939 mplsTunnelCRLDPResFrequency, 2940 mplsTunnelCRLDPResWeight, 2941 mplsTunnelCRLDPResFlags, 2942 mplsTunnelCRLDPResRowStatus, 2943 mplsTunnelCRLDPResStorageType 2944 } 2945 STATUS current 2946 DESCRIPTION 2947 "Set of objects implemented for resources applicable 2948 for tunnels signaled using CR-LDP." 2949 ::= { mplsTeGroups 8 } 2951 mplsTeNotificationGroup NOTIFICATION-GROUP 2952 NOTIFICATIONS { 2953 mplsTunnelUp, 2954 mplsTunnelDown, 2955 mplsTunnelRerouted, 2956 mplsTunnelReoptimized 2957 } 2958 STATUS current 2959 DESCRIPTION 2960 "Set of notifications implemented in this module. 2962 None is mandatory." 2963 ::= { mplsTeGroups 9 } 2965 -- End of MPLS-TE-MIB 2966 END 2968 11. Security Considerations 2970 There are a number of management objects defined in this 2971 MIB that have a MAX-ACCESS clause of read-write and/or 2972 read-create. Such objects may be considered sensitive or 2973 vulnerable in some network environments. The support for 2974 SET operations in a non-secure environment without proper 2975 protection can have a negative effect on network 2976 operations. 2978 It is thus important to control even GET access to these 2979 objects and possibly to even encrypt the values of these 2980 object when sending them over the network via SNMP. Not 2981 all versions of SNMP provide features for such a secure 2982 environment. 2984 SNMPv1 by itself is not a secure environment. Even if the 2985 network itself is secure (for example by using IPSec 2986 [IPSEC]), there is no control as to who on the secure 2987 network is allowed to access and GET/SET 2988 (read/change/create/delete) the objects in this MIB. It is 2989 recommended that the implementers consider the security 2990 features as provided by the SNMPv3 framework. 2991 Specifically, the use of the User-based Security Model 2992 [SNMPv3USM] and the View- based Access Control 2993 [SNMPv3VACM] is recommended. It is then a customer/user 2994 responsibility to ensure that the SNMP entity giving 2995 access to an instance of this MIB, is properly configured 2996 to give access to the objects only to those principals 2997 (users) that have legitimate rights to indeed GET or SET 2998 (change/create/delete) them. 3000 12. Acknowledgments 3002 We wish to thank Adrian Farrel, Eric Gray, Joan Cucchiara, 3003 Patrick Kerharo, Paul Langille and Mike Piecuch for their 3004 comments on this draft. 3006 13. References 3008 [MPLSArch] Rosen, E., Viswanathan, A., and R. Callon, 3009 "Multiprotocol Label Switching 3010 Architecture", Internet Draft , July 2000. 3013 [LSRMIB] Srinivasan, C., Viswanathan, A. and T. 3014 Nadeau, "MPLS Label Switch Router Management 3015 Information Base Using SMIv2", Internet 3016 Draft , July 3017 2000. 3019 [LblStk] Rosen, E., Rekhter, Y., Tappan, D., 3020 Farinacci, D., Federokow, G., Li, T., and A. 3021 Conta, "MPLS Label Stack Encoding", Internet 3022 Draft , 3023 July 2000. 3025 [RSVPTun] Awaduche, D., Berger, L., Der-Haw, G., Li, 3026 T., Swallow, G., and V. Srinivasan, 3027 "Extensions to RSVP for LSP Tunnels", 3028 Internet Draft , August 2000. 3031 [CR-LDP] B. Jamoussi (Editor), "Constraint-Based LSP 3032 Setup using LDP", Internet Draft , July 2000. 3035 [Assigned] Reynolds, J., and J. Postel, "Assigned 3036 Numbers", RFC 1700, October 1994. See also: 3037 http://www.isi.edu/in- 3038 notes/iana/assignments/smi-numbers 3040 [SNMPArch] Harrington, D., Presuhn, R., and B. Wijnen, 3041 "An Architecture for Describing SNMP 3042 Management Frameworks", RFC 2271, January 3043 1998. 3045 [SMIv1] Rose, M., and K. McCloghrie, "Structure and 3046 Identification of Management Information for 3047 TCP/IP-based Internets", RFC 1155, May 1990. 3049 [SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB 3050 Definitions", RFC 1212, March 1991. 3052 [SNMPv1Traps] M. Rose, "A Convention for Defining Traps 3053 for use with the SNMP", RFC 1215, March 3054 1991. 3056 [SMIv2] Case, J., McCloghrie, K., Rose, M., and S. 3057 Waldbusser, "Structure of Management 3058 Information for Version 2 of the Simple 3059 Network Management Protocol (SNMPv2)", RFC 3060 1902, January 1996. 3062 [SNMPv2TC] Case, J., McCloghrie, K., Rose, M., and S. 3063 Waldbusser, "Textual Conventions for Version 3064 2 of the Simple Network Management Protocol 3065 (SNMPv2)", RFC 1903, SNMP Research, Inc., 3066 Cisco Systems, Inc., January 1996. 3068 [SNMPv2Conf] Case, J., McCloghrie, K., Rose, M., and S. 3069 Waldbusser, "Conformance Statements for 3070 Version 2 of the Simple Network Management 3071 Protocol (SNMPv2)", RFC 1904, January 1996. 3073 [SNMPv1] Case, J., Fedor, M., Schoffstall, M., and J. 3074 Davin, "Simple Network Management Protocol", 3075 RFC 1157, May 1990. 3077 [SNMPv2c] Case, J., McCloghrie, K., Rose, M., and S. 3078 Waldbusser, "Introduction to Community-based 3079 SNMPv2", RFC 1901, January 1996. 3081 [SNMPv2TM] Case, J., McCloghrie, K., Rose, M., and S. 3082 Waldbusser, "Transport Mappings for Version 3083 2 of the Simple Network Management Protocol 3084 (SNMPv2)", RFC 1906, January 1996. 3086 [SNMPv3MP] Case, J., Harrington D., Presuhn R., and B. 3087 Wijnen, "Message Processing and Dispatching 3088 for the Simple Network Management Protocol 3089 (SNMP)", RFC 2272, January 1998. 3091 [SNMPv3USM] Blumenthal, U., and B. Wijnen, "User-based 3092 Security Model (USM) for version 3 of the 3093 Simple Network Management Protocol 3094 (SNMPv3)", RFC 2574, April 1999. 3096 [SNMPv2PO] Case, J., McCloghrie, K., Rose, M., and S. 3097 Waldbusser, "Protocol Operations for Version 3098 2 of the Simple Network Management Protocol 3099 (SNMPv2)", RFC 1905, January 1996. 3101 [SNMPv3App] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 3102 Applications", RFC 2273, January 1998. 3104 [SNMPv3VACM] Wijnen, B., Presuhn, R., and K. McCloghrie, 3105 "View-based Access Control Model (VACM) for 3106 the Simple Network Management Protocol 3107 (SNMP)", RFC 2575, April 1999. 3109 [IPSEC] Kent, S., and Atkinson, R., "Security 3110 Architecture for the Internet Protocol", RFC 3111 2401, November 1998. 3113 [IFMIB] McCloghrie, K., and F. Kastenholtz, "The 3114 Interfaces Group MIB using SMIv2", RFC 2233, 3115 Nov. 1997. 3117 [INETADDRMIB] Daniele, M., Haberman, B., Routhier, S. and 3118 J. Schoenwaelder, "Textual Conventions for 3119 Internet Network Addresses", RFC 2851, June 3120 2000. 3122 14. Authors' Addresses 3124 Cheenu Srinivasan 3125 Tachion Networks, Inc. 3126 Monmouth Park Corporate Center I 3127 Building C, 185 Monmouth Park Highway 3128 West Long Branch, NJ 07764 3129 Phone: +1-732-542-7750 x1234 3130 Email: cheenu@tachion.com 3132 Arun Viswanathan 3133 Force10 Networks, Inc. 3134 1440 McCarthy Blvd 3135 Milpitas, CA 95035 3136 Phone: +1-408-571-3516 3137 Email: arun@force10networks.com 3139 Thomas D. Nadeau 3140 Cisco Systems, Inc. 3141 300 Apollo Drive 3142 Chelmsford, MA 01824 3143 Phone: +1-978-244-3051 3144 Email: tnadeau@cisco.com 3146 15. Full Copyright Statement 3148 Copyright (C) The Internet Society (2000). All Rights 3149 Reserved. 3151 This document and translations of it may be copied and 3152 furnished to others, and derivative works that comment on 3153 or otherwise explain it or assist in its implementation may 3154 be prepared, copied, published and distributed, in whole or 3155 in part, without restriction of any kind, provided that the 3156 above copyright notice and this paragraph are included on 3157 all such copies and derivative works. However, this 3158 document itself may not be modified in any way, such as by 3159 removing the copyright notice or references to the Internet 3160 Society or other Internet organizations, except as needed 3161 for the purpose of developing Internet standards in which 3162 case the procedures for copyrights defined in the Internet 3163 Standards process must be followed, or as required to 3164 translate it into languages other than English. 3166 The limited permissions granted above are perpetual and 3167 will not be revoked by the Internet Society or its 3168 successors or assigns. This document and the information 3169 contained herein is provided on an "AS IS" basis and THE 3170 INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE 3171 DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 3172 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 3173 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 3174 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 3175 PURPOSE.