--- 1/draft-ietf-mpls-te-mib-08.txt 2006-02-05 00:43:38.000000000 +0100 +++ 2/draft-ietf-mpls-te-mib-09.txt 2006-02-05 00:43:38.000000000 +0100 @@ -1,25 +1,25 @@ Network Working Group Cheenu Srinivasan Internet Draft Parama Networks, Inc. -Expires: July 2002 +Expires: May 2003 Arun Viswanathan Force10 Networks, Inc. Thomas D. Nadeau Cisco Systems, Inc. - January 2002 + November 2002 Multiprotocol Label Switching (MPLS) Traffic Engineering Management Information Base - draft-ietf-mpls-te-mib-08.txt + draft-ietf-mpls-te-mib-09.txt Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC 2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. @@ -39,72 +39,75 @@ Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for Multiprotocol Label Switching (MPLS) based traffic engineering. Table of Contents - 1. Introduction .............................................. 2 - 2. Terminology ............................................... 2 - 3. The SNMP Management Framework ............................. 3 - 4. Feature List .............................................. 4 - 5. Outline ................................................... 4 - 5.1. Summary of Traffic Engineering MIB ..................... 4 - 6. Brief Description of MIB Objects .......................... 5 - 6.1. mplsTunnelTable ........................................ 5 - 6.2. mplsTunnelResourceTable ................................ 6 - 6.3. mplsTunnelHopTable ..................................... 6 - 6.4. mplsTunnelARHopTable ................................... 6 - 6.5. mplsTunnelCHoptable .................................... 6 - 6.6. mplsTunnelPerfTable .................................... 6 - 6.7. mplsTunnelCRLDPResTable ................................ 6 - 7. Application of the Interface Group to MPLS Tunnels ........ 7 - 7.1. Support of the MPLS Tunnel Interface by ifTable ........ 7 - 8. Example of Tunnel Setup ................................... 9 - 9. The Use of RowPointer ..................................... 10 - 10. MPLS Traffic Engineering MIB Definitions ................. 11 - 11. Security Considerations .................................. 60 - 12. Acknowledgments .......................................... 60 - 13. References ............................................... 60 - 14. Authors' Addresses ....................................... 63 - 15. Full Copyright Statement ................................. 63 +1. Introduction ........................................... 2 + +2. Terminology ............................................ 2 +3. The SNMP Management Framework .......................... 3 +4. Feature List ........................................... 4 +5. Outline ................................................ 4 +5.1. Summary of Traffic Engineering MIB ................... 5 +6. Brief Description of MIB Objects ....................... 5 +6.1. mplsTunnelTable ...................................... 5 +6.2. mplsTunnelResourceTable .............................. 6 +6.3. mplsTunnelHopTable ................................... 6 +6.4. mplsTunnelARHopTable ................................. 6 +6.5. mplsTunnelCHoptable .................................. 7 +6.6. mplsTunnelPerfTable .................................. 7 +6.7. mplsTunnelCRLDPResTable .............................. 7 +7. Use of 32-bit and 64-bit Counters ...................... 7 +8. Application of the Interface Group to MPLS Tunnels ..... 7 +8.1. Support of the MPLS Tunnel Interface by ifTable ...... 8 +9. Example of Tunnel Setup ............................... 10 +10. The Use of RowPointer ................................ 12 +11. MPLS Traffic Engineering MIB Definitions ............. 12 +12. Security Considerations .............................. 63 +13. Acknowledgments ...................................... 64 +14. References ........................................... 64 +15. Authors' Addresses ................................... 67 +16. Full Copyright Statement ............................. 67 1. Introduction This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects for modeling a Multi-Protocol Label Switching (MPLS) [RFC3031] based traffic engineering. This MIB should be used in conjunction with the companion document [LSRMIB] for MPLS based traffic engineering configuration and management. 2. Terminology This document uses terminology from the MPLS architecture - document [RFC3031] and MPLS Label Switch Router MIB + document [RFC3031] and MPLS Label Switching Router MIB [LSRMIB]. Some frequently used terms are described next. An explicitly routed LSP (ERLSP) is referred to as an MPLS tunnel. It consists of one in-segment and/or one out- segment at the ingress/egress LSRs, each segment being associated with one MPLS interface. These are also referred to as tunnel segments. Additionally, at an intermediate LSR, we model a connection as consisting of one or more in-segments and/or one or more out-segments. The binding or interconnection between in-segments and out- segments in performed using a cross-connect. These objects - are defined in the MPLS Label Switch Router MIB [LSRMIB]. + are defined in the MPLS Label Switching Router MIB + [LSRMIB]. 3. The SNMP Management Framework The SNMP Management Framework presently consists of five major components: - An overall architecture, described in RFC 2571 [RFC2571]. - Mechanisms for describing and naming objects and events @@ -161,22 +164,28 @@ The MPLS traffic engineering MIB is designed to satisfy the following requirements and constraints. - The MIB supports configuration of point-to-point unidirectional tunnels. - MPLS tunnels need not be interfaces, but it is possible to configure a tunnel as an interface. - - The MIB supports manually configured MPLS tunnels as - well as those set up via an MPLS signaling protocol. + - The MIB supports tunnel establishment via an MPLS + signalling protocol wherein the tunnel parameters are + specified using this MIB at the head end of the LSP and + end-to-end tunnel LSP establishment is accomplished via + signalling. The MIB also supports manually configured + tunnels, i.e. those for which label associations at + each hop of the tunnel LSP are provisioned by the + administrator via the LSR MIB [LSRMIB]. - The MIB supports persistent as well as non-persistent tunnels. 5. Outline Traffic engineering support for MPLS tunnels requires the following configuration. - Setting up MPLS tunnels along with appropriate @@ -243,35 +253,35 @@ mplsTunnelResourceTable is used to indicate the resources required for a tunnel. Multiple tunnels may share the same resources by pointing to the same entry in this table. Tunnels that do not share resources must point to separate entries in this table. 6.3. mplsTunnelHopTable mplsTunnelHopTable is used to indicate the hops, strict or loose, for an MPLS tunnel defined in mplsTunnelTable, when - it is established via signaling. Multiple tunnels may + it is established via signalling. Multiple tunnels may share the same hops by pointing to the same entry in this table. Each row also has a secondary index, mplsTunnelHopIndex, corresponding to the next hop of this tunnel. The scalar mplsTunnelMaxHops indicates the maximum number of hops that can be specified on each tunnel supported by this LSR. 6.4. mplsTunnelARHopTable mplsTunnelARHopTable is used to indicate the actual hops - traversed by a tunnel as reported by the MPLS signaling + traversed by a tunnel as reported by the MPLS signalling protocol after the tunnel is setup. The support of this - table is optional since not all MPLS signaling protocol may - support this feature. + table is optional since not all MPLS signalling protocol + may support this feature. 6.5. mplsTunnelCHoptable mplsTunnelCHopTable lists the actual hops computed by a constraint-based routing algorithm based on the mplsTunnelHopTable. The support of this table is optional since not all implementations may support computation of hop list using a constraint-based routing protocol. 6.6. mplsTunnelPerfTable @@ -284,22 +294,39 @@ mplsTunnelCRLDPResTable contains resource information for those tunnels that are signaled using CRLDP [CRLDP]. This is a sparse extension to mplsTunnelResourceTable and is also indexed by mplsTunnelResourceIndex. As with mplsTunnelResourceTable, multiple tunnels may share the same resources by pointing to the same entry in this table. Tunnels that do not share resources must point to separate entries in this table. -7. Application of the Interface Group to MPLS Tunnels +7. Use of 32-bit and 64-bit Counters + 64-bit counters are provided in this MIB for high-speed + interfaces where the use of 32-bit counters might be + impractical. The requirements on the use of 32-bit and 64- + bit counters (copied verbatim from [RFC2863]) are as + follows. + + For interfaces that operate at 20,000,000 (20 million) bits + per second or less, 32-bit byte and packet counters MUST be + supported. For interfaces that operate faster than + 20,000,000 bits/second, and slower than 650,000,000 + bits/second, 32-bit packet counters MUST be supported and + 64-bit octet counters MUST be supported. For interfaces + that operate at 650,000,000 bits/second or faster, 64-bit + packet counters AND 64-bit octet counters MUST be + supported. + +8. Application of the Interface Group to MPLS Tunnels The Interfaces Group of MIB II defines generic managed objects for managing interfaces. This memo contains the media-specific extensions to the Interfaces Group for managing MPLS Tunnels as logical interfaces. This memo assumes the interpretation of the Interfaces Group to be in accordance with [RFC2863] which states that the interfaces table (ifTable) contains information on the managed resource's interfaces and that each sub-layer below the internetwork layer of a network interface is considered @@ -313,25 +340,25 @@ +------------------------------------------------+ | MPLS tunnel interface ifType = mplsTunnel(150) | +------------------------------------------------+ | MPLS interface ifType = mpls(166) | +------------------------------------------------+ | Underlying layer | +------------------------------------------------+ In the above diagram, "Underlying Layer" refers to the - ifIndex of any interface type, which has been defined for - MPLS interworking. Examples include ATM, Frame Relay, and - Ethernet. + ifIndex of any interface type for which MPLS + internetworking has been defined. Examples include ATM, + Frame Relay, and Ethernet. -7.1. Support of the MPLS Tunnel Interface by ifTable +8.1. Support of the MPLS Tunnel Interface by ifTable Some specific interpretations of ifTable for those MPLS tunnels represented as interfaces follow: Object Use for the MPLS tunnel. ifIndex Each MPLS tunnel is represented by an ifEntry. ifDescr Description of the MPLS tunnel. @@ -339,21 +366,23 @@ ifType The value that is allocated for MPLS tunnel is 150. ifSpeed The total bandwidth in bits per second for use by the MPLS tunnel. ifPhysAddress Unused. ifAdminStatus See [RFC2863]. - ifOperStatus Assumes the value down(2) if the MPLS + ifOperStatus This value reflects the actual + operational status of MPLS tunnel. + Assumes the value down(2) if the MPLS tunnel is down. ifLastChange See [RFC2863]. ifInOctets The number of octets received over the MPLS tunnel. ifOutOctets The number of octets transmitted over the MPLS tunnel. @@ -383,144 +412,166 @@ statements in [RFC2863]. ifHCOutOctets The 64-bit version of ifOutOctets; supported if required by the compliance statements in [RFC2863]. ifAlias The non-volatile 'alias' name for the MPLS tunnel as specified by a network manager. -8. Example of Tunnel Setup +9. Example of Tunnel Setup This section contains an example of which MIB objects should be modified if one would like to create a best effort, loosely routed, unidirectional traffic engineered tunnel, which spans two hops of a simple network. Note that these objects should be created on the "head-end" - LSR. + LSR. Those objects relevant to illustrating the + relationships amongst different tables are shown here. + Other objects may be needed before conceptual row + activation can happen. + + The RowStatus values shown in this section are those to be + used in the set request, typically createAndGo(4) which is + used to create the conceptual row and have its status + immediately set to active. A subsequent retrieval + operation on the conceptual row will return a different + value, such as active(1). Please see [RFC2579] for a + detailed discussion on the use of RowStatus. In mplsTunnelTable: { - mplsTunnelIndex = 1, + mplsTunnelIndexIndex = 1, mplsTunnelInstance = 1, mplsTunnelIngressLSRId = 123.123.125.1, mplsTunnelEgressLSRId = 123.123.126.1, mplsTunnelName = "My first tunnel", mplsTunnelDescr = "Here to there", mplsTunnelIsIf = true (1), + -- RowPointer MUST point to the first accessible column mplsTunnelXCPointer = mplsXCIndex.2.0.0.15, mplsTunnelSignallingProto = none (1), mplsTunnelSetupPrio = 0, mplsTunnelHoldingPrio = 0, mplsTunnelSessionAttributes = 0, mplsTunnelOwner = snmp (1), mplsTunnelLocalProtectInUse = false (0), + -- RowPointer MUST point to the first accessible column mplsTunnelResourcePointer = mplsTunnelResourceIndex.5, mplsTunnelInstancePriority = 1, mplsTunnelHopTableIndex = 1, mplsTunnelPrimaryInstance = 0, mplsTunnelIncludeAnyAffinity = 0, mplsTunnelIncludeAllAffinity = 0, mplsTunnelExcludeAllAffinity = 0, mplsTunnelPathInUse = 1, mplsTunnelRole = head (1), + -- Mandatory parameters needed to activate the row go here mplsTunnelRowStatus = createAndGo (4) } In mplsTunnelResourceTable: { mplsTunnelResourceIndex = 5, mplsTunnelResourceMaxRate = 0, mplsTunnelResourceMeanRate = 0, mplsTunnelResourceMaxBurstSize = 0, + -- Mandatory parameters needed to activate the row go here mplsTunnelResourceRowStatus = createAndGo (4) } The next two instances of mplsTunnelHopEntry are used to denote the hops this tunnel will take across the network. The following denotes the beginning of the network, or the first hop. We have used the fictitious LSR identified by "123.123.125.1" as our example head-end router. In mplsTunnelHopTable: { mplsTunnelHopListIndex = 1, mplsTunnelPathOptionIndex = 1, mplsTunnelHopIndex = 1, mplsTunnelHopAddrType = 1, - mplsTunnelHopIpv4Addr = 123.123.125.1, - mplsTunnelHopIpv4PrefixLen = 9, + mplsTunnelHopIpAddrType = ipV4 (1) + mplsTunnelHopIpAddr = 123.123.125.1, + mplsTunnelHopIpPrefixLen = 9, mplsTunnelHopType = loose (2), + -- Mandatory parameters needed to activate the row go here mplsTunnelHopRowStatus = createAndGo (4) } The following denotes the end of the network, or the last hop in our example. We have used the fictitious LSR identified by "123.123.126.1" as our end router. In mplsTunnelHopTable: { mplsTunnelHopListIndex = 1, mplsTunnelPathOptionIndex = 1, mplsTunnelHopIndex = 2, mplsTunnelHopAddrType = 1, - mplsTunnelHopIpv4Addr = 123.123.126.1, - mplsTunnelHopIpv4PrefixLen = 9, + mplsTunnelHopIpAddrType = ipV4 (1), + mplsTunnelHopIpAddr = 123.123.126.1, + mplsTunnelHopIpPrefixLen = 9, mplsTunnelHopType = loose (2), + -- Mandatory parameters needed to activate the row go here mplsTunnelHopRowStatus = createAndGo (4) } -9. The Use of RowPointer +10. The Use of RowPointer RowPointer is a textual convention used to identify a conceptual row in an SNMP Table by pointing to one of its objects. In this MIB, in mplsTunnelTable, the objects mplsTunnelXCPointer and mplsTunnelResourcePointer are of type RowPointer. The object mplsTunnelXCPointer points to a specific entry in the mplsXCTable [LSRMIB]. This entry in the mplsXCTable is the associated LSP for the given MPLS tunnel entry. The object mplsTunnelResourcePointer points to a specific entry in a traffic parameter table. An example of such a traffic parameter table is mplsTunnelResourceTable. It indicates a specific instance of a traffic parameter entry that is associated with a - given MPLS tunnel entry. + given MPLS tunnel entry. Row pointers mplsTunnelXCPointer + and mplsTunnelResourcePointer MUST point to the first + column of the appropriate conceptual row. -10. MPLS Traffic Engineering MIB Definitions +11. MPLS Traffic Engineering MIB Definitions MPLS-TE-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, - Integer32, Unsigned32, Counter32, Counter64, TimeTicks + Integer32, Unsigned32, Counter32, Counter64, TimeTicks, + zeroDotZero FROM SNMPv2-SMI MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF TruthValue, RowStatus, RowPointer, StorageType, DisplayString, TimeStamp FROM SNMPv2-TC InterfaceIndexOrZero FROM IF-MIB mplsMIB, MplsBitRate, MplsBurstSize, MplsLSPID, MplsTunnelIndex, MplsTunnelInstanceIndex, MplsTunnelAffinity, MplsLsrIdentifier, MplsPathIndex, - MplsPathIndexOrZero + MplsPathIndexOrZero, MplsOwner FROM MPLS-TC-MIB - InetAddressIPv4, InetAddressIPv6 + InetAddress, InetAddressType, InetAddressPrefixLength FROM INET-ADDRESS-MIB ; mplsTeMIB MODULE-IDENTITY LAST-UPDATED - "200201041200Z" -- 4 January 2002 12:00:00 GMT + "200211041200Z" -- 4 November 2002 12:00:00 GMT ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" CONTACT-INFO " Cheenu Srinivasan Postal: Parama Networks, Inc. 1030 Broad Street Shrewsbury, NJ 07702 Tel: +1-732-544-9120 x731 Email: cheenu@paramanet.com @@ -533,54 +583,55 @@ Tel: +1-408-571-3516 Email: arun@force10networks.com Thomas D. Nadeau Postal: Cisco Systems, Inc. 250 Apollo Drive Chelmsford, MA 01824 Tel: +1-978-244-3051 Email: tnadeau@cisco.com + Comments about this document should be + emailed + directly to the MPLS working group mailing + list at + mpls@uu.net. " DESCRIPTION "This MIB module contains managed object definitions for MPLS Traffic Engineering (TE) as defined in: 1. Extensions to RSVP for LSP Tunnels, Awduche et al, RFC 3209, December 2001 2. Constraint-Based LSP Setup using LDP, Jamoussi - (Editor), Internet Draft , November 2001 + (Editor), RFC 3212, January 2002 3. Requirements for Traffic Engineering Over MPLS, Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M., and J. McManus, RFC 2702, September 1999" -- Revision history. REVISION - "200201041200Z" -- 4 January 2002 12:00:00 GMT + "200211041200Z" -- 4 November 2002 12:00:00 GMT DESCRIPTION "Initial draft version issues as part of RFC XXXX." ::= { mplsMIB 3 } -- Top level components of this MIB. +-- traps +mplsTeNotifications OBJECT IDENTIFIER ::= { mplsTeMIB 0 } -- tables, scalars mplsTeScalars OBJECT IDENTIFIER ::= { mplsTeMIB 1 } mplsTeObjects OBJECT IDENTIFIER ::= { mplsTeMIB 2 } - --- traps -mplsTeNotifications OBJECT IDENTIFIER ::= { mplsTeMIB 3 } -mplsTeNotifyPrefix OBJECT IDENTIFIER ::= { mplsTeNotifications 0 } - -- conformance -mplsTeConformance OBJECT IDENTIFIER ::= { mplsTeMIB 4 } +mplsTeConformance OBJECT IDENTIFIER ::= { mplsTeMIB 3 } -- MPLS Tunnel scalars. mplsTunnelConfigured OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The number of tunnels configured on this device. A tunnel is considered configured if the @@ -613,38 +664,53 @@ mplsTunnelMaxHops OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The maximum number of hops that can be specified for a tunnel on this device." ::= { mplsTeScalars 4 } +mplsTunnelNotifMaxRate OBJECT-TYPE + SYNTAX Unsigned32 + MAX-ACCESS read-write + STATUS current + DESCRIPTION + "This variable indicates the number of milliseconds + that must elapse between notification emissions. If + events occur more rapidly, the implementation may + simply fail to emit these notifications during that + period, or may queue them until an appropriate + time. A value of 0 means no minimum elapsed period + is specified." + DEFVAL { 0 } + ::= { mplsTeScalars 5 } + -- End of MPLS Tunnel scalars. -- MPLS tunnel table. mplsTunnelIndexNext OBJECT-TYPE SYNTAX Integer32 (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "This object contains the next appropriate value to - be used for mplsTunnelIndex when creating entries - in mplsTunnelTable. If the number of unassigned - entries is exhausted, a retrival operation will - return a value of 0. This object may also return a - value of 0 when the LSR is unable to accept - conceptual row creation, for example, if the - mplsTunnelTable is implemented as read-only. To - obtain the value of mplsTunnelIndex for a new + be used for mplsTunnelIndexIndex when creating + entries in mplsTunnelTable. If the number of + unassigned entries is exhausted, a retrival + operation will return a value of 0. This object + may also return a value of 0 when the LSR is unable + to accept conceptual row creation, for example, if + the mplsTunnelTable is implemented as read-only. To + obtain the value of mplsTunnelIndexIndex for a new entry, the manager must first issue a management protocol retrieval operation to obtain the current value of this object. The agent should modify the value to reflect the next unassigned index after each retrieval operation. After a manager retrieves a value the agent will determine through its local policy when this index value will be made available for reuse." ::= { mplsTeObjects 1 } @@ -665,53 +731,53 @@ ::= { mplsTeObjects 2 } mplsTunnelEntry OBJECT-TYPE SYNTAX MplsTunnelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents an MPLS tunnel. An entry can be created by a network administrator or by an SNMP agent as instructed by an MPLS - signaling protocol. Whenever a new entry is created - with mplsTunnelIsIf set to true(1), then a + signalling protocol. Whenever a new entry is + created with mplsTunnelIsIf set to true(1), then a corresponding entry is created in ifTable as well (see RFC 2863). The ifType of this entry is mplsTunnel(150)." REFERENCE "1. RFC 2863 - The Interfaces Group MIB, McCloghrie, K., and F. Kastenholtz, June 2000 2. RFC 1700 - Assigned Numbers, Reynolds, J. and J. Postel, Oct. 1994" INDEX { - mplsTunnelIndex, + mplsTunnelIndexIndex, mplsTunnelInstance, mplsTunnelIngressLSRId, mplsTunnelEgressLSRId } ::= { mplsTunnelTable 1 } MplsTunnelEntry ::= SEQUENCE { - mplsTunnelIndex MplsTunnelIndex, + mplsTunnelIndexIndex MplsTunnelIndex, mplsTunnelInstance MplsTunnelInstanceIndex, mplsTunnelIngressLSRId MplsLsrIdentifier, mplsTunnelEgressLSRId MplsLsrIdentifier, mplsTunnelName DisplayString, mplsTunnelDescr DisplayString, mplsTunnelIsIf TruthValue, mplsTunnelIfIndex InterfaceIndexOrZero, mplsTunnelXCPointer RowPointer, mplsTunnelSignallingProto INTEGER, - mplsTunnelSetupPrio INTEGER, - mplsTunnelHoldingPrio INTEGER, + mplsTunnelSetupPrio Integer32, + mplsTunnelHoldingPrio Integer32, mplsTunnelSessionAttributes BITS, - mplsTunnelOwner INTEGER, + mplsTunnelOwner MplsOwner, mplsTunnelLocalProtectInUse TruthValue, mplsTunnelResourcePointer RowPointer, mplsTunnelInstancePriority Unsigned32, mplsTunnelHopTableIndex MplsPathIndexOrZero, mplsTunnelARHopTableIndex MplsPathIndexOrZero, mplsTunnelCHopTableIndex MplsPathIndexOrZero, mplsTunnelPrimaryInstance MplsTunnelInstanceIndex, mplsTunnelPrimaryTimeUp TimeTicks, mplsTunnelPathChanges Counter32, mplsTunnelLastPathChange TimeTicks, @@ -723,21 +789,21 @@ mplsTunnelPathInUse MplsPathIndexOrZero, mplsTunnelRole INTEGER, mplsTunnelTotalUpTime TimeTicks, mplsTunnelInstanceUpTime TimeTicks, mplsTunnelAdminStatus INTEGER, mplsTunnelOperStatus INTEGER, mplsTunnelRowStatus RowStatus, mplsTunnelStorageType StorageType } -mplsTunnelIndex OBJECT-TYPE +mplsTunnelIndexIndex OBJECT-TYPE SYNTAX MplsTunnelIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "Uniquely identifies this row." ::= { mplsTunnelEntry 1 } mplsTunnelInstance OBJECT-TYPE SYNTAX MplsTunnelInstanceIndex MAX-ACCESS not-accessible @@ -748,31 +814,30 @@ for the purposes of backup and parallel tunnels." ::= { mplsTunnelEntry 2 } mplsTunnelIngressLSRId OBJECT-TYPE SYNTAX MplsLsrIdentifier MAX-ACCESS not-accessible STATUS current DESCRIPTION "The purpose of this object is to uniquely identity a tunnel within a network. When the MPLS signalling - protoocol is rsvp(2) this value SHOULD mimic the + protocol is rsvp(2) this value SHOULD mimic the Extended Tunnel Id field in the SESSION object. - When the MPLS signalling protoocol is crldp(3) this + When the MPLS signalling protocol is crldp(3) this value SHOULD mimic the Ingress LSR Router ID field in the LSPID TLV object." REFERENCE "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, Awduche et al, RFC 3209, December 2001 2. Constraint-Based LSP Setup using LDP, Jamoussi - (Editor), Internet Draft , November 2001" + (Editor), RFC 3212, January 2002" ::= { mplsTunnelEntry 3 } mplsTunnelEgressLSRId OBJECT-TYPE SYNTAX MplsLsrIdentifier MAX-ACCESS not-accessible STATUS current DESCRIPTION "Specifies the egress LSR ID." ::= { mplsTunnelEntry 4 } @@ -843,36 +908,37 @@ STATUS current DESCRIPTION "This variable points to a row in the mplsXCTable. This table identifies the segments that compose this tunnel, their characteristics, and relationships to each other. A value of zeroDotZero indicates that no LSP has been associated with this tunnel yet." REFERENCE "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS - Label Switch Router Management Information Base, - Internet Draft , - December 2001." + Label Switching Router Management Information Base, + Internet Draft , + October 2002." + DEFVAL { zeroDotZero } ::= { mplsTunnelEntry 9 } mplsTunnelSignallingProto OBJECT-TYPE SYNTAX INTEGER { none(1), rsvp(2), crldp(3), other(4) } MAX-ACCESS read-create STATUS current DESCRIPTION - "The signaling protocol, if any, which was used to + "The signalling protocol, if any, which was used to setup this tunnel." DEFVAL { none } ::= { mplsTunnelEntry 10 } mplsTunnelSetupPrio OBJECT-TYPE SYNTAX Integer32 (0..7) MAX-ACCESS read-create STATUS current DESCRIPTION "Indicates the setup priority of this tunnel." @@ -887,85 +953,77 @@ mplsTunnelHoldingPrio OBJECT-TYPE SYNTAX Integer32 (0..7) MAX-ACCESS read-create STATUS current DESCRIPTION "Indicates the holding priority for this tunnel." REFERENCE "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, Awduche et al, RFC3209, December 2001 2. Constraint-Based LSP Setup using LDP, Jamoussi - (Editor), Internet Draft , November 2001" + (Editor), RFC 3212, January 2002" ::= { mplsTunnelEntry 12 } mplsTunnelSessionAttributes OBJECT-TYPE SYNTAX BITS { fastReroute (0), mergingPermitted (1), isPersistent (2), isPinned (3), recordRoute(4) } MAX-ACCESS read-create STATUS current DESCRIPTION "This bitmask indicates optional session values for - this tunnel. The following describes these - bitfields: + this tunnel. The following describes these bit + fields: fastRerouteThis flag indicates that the any tunnel hop may choose to reroute this tunnel without tearing it down. This flag permits transit routers to use a local repair mechanism which may result in violation of the explicit routing of this tunnel. + When a fault is detected on an adjacent downstream - link or node, a transit router can reroute traffic + link or node, a transit router can re-route traffic for fast service restoration. mergingPermitted This flag permits transit routers to merge this session with other RSVP sessions for the purpose of reducing resource overhead on downstream transit routers, thereby providing - better network scalability. + better network scaling. isPersistent Indicates whether this tunnel should be restored automatically after a failure occurs. isPinned This flag indicates whether the loose- routed hops of this tunnel are to be pinned. recordRouteThis flag indicates whether or not the - signaling protocol should remember the tunnel path + signalling protocol should remember the tunnel path after it has been signaled." REFERENCE "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, Awduche et al, RFC 3209, December 2001." - DEFVAL { 0 } ::= { mplsTunnelEntry 13 } mplsTunnelOwner OBJECT-TYPE - SYNTAX INTEGER { - admin(1), -- represents all management entities - rsvp(2), - crldp(3), - policyAgent(4), - other(5) - } - MAX-ACCESS read-create + SYNTAX MplsOwner + MAX-ACCESS read-only STATUS current DESCRIPTION - "Indicates which protocol created and is responsible - for managing this tunnel. Values rsvp(2) and - crldp(3) should not be used at the head-end of a - MPLS tunnel." + "Denotes the entity that created and is responsible + for managing this tunnel. This object cannot be + modified if mplsTunnelRowStatus is active(1). " ::= { mplsTunnelEntry 14 } mplsTunnelLocalProtectInUse OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Indicates that the local repair mechanism is in use to maintain this tunnel (usually in the face of an outage of the link it was previously routed over)." @@ -980,35 +1038,36 @@ parameter specification for this tunnel. This value may point at an entry in the mplsTunnelResourceEntry to indicate which mplsTunnelResourceEntry is to be assigned to this segment. This value may optionally point at an externally defined traffic parameter specification table. A value of zeroDotZero indicates best- effort treatment. By having the same value of this object, two or more segments can indicate resource sharing." + DEFVAL { zeroDotZero } ::= { mplsTunnelEntry 16 } mplsTunnelInstancePriority OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-create STATUS current DESCRIPTION "This value indicates which priority, in descending order, with 0 indicating the lowest priority, within a group of tunnel instances. A group of tunnel instances is defined as a set of tunnels - with the same mplsTunnelIndex in this table, but - with a different mplsTunnelInstance. Tunnel group - priorities are used to denote the priority at which - a particular tunnel instance will supercede + with the same mplsTunnelIndexIndex in this table, + but with a different mplsTunnelInstance. Tunnel + group priorities are used to denote the priority at + which a particular tunnel instance will supercede another. Instances of tunnels containing the same mplsTunnelInstancePriority will be used for load sharing." DEFVAL { 0 } ::= { mplsTunnelEntry 17 } mplsTunnelHopTableIndex OBJECT-TYPE SYNTAX MplsPathIndexOrZero MAX-ACCESS read-create STATUS current @@ -1104,35 +1163,35 @@ "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, Awduche et al, RFC 3209, December 2001." ::= { mplsTunnelEntry 27 } mplsTunnelIncludeAllAffinity OBJECT-TYPE SYNTAX MplsTunnelAffinity MAX-ACCESS read-create STATUS current DESCRIPTION "A link satisfies the include-all constraint if and - only if the link contains all of the adminstrative + only if the link contains all of the administrative groups specified in the constraint." REFERENCE "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, Awduche et al, RFC 3209, December 2001." ::= { mplsTunnelEntry 28 } mplsTunnelExcludeAllAffinity OBJECT-TYPE SYNTAX MplsTunnelAffinity MAX-ACCESS read-create STATUS current DESCRIPTION "A link satisfies the exclude-all constraint if and - only if the link contains none of the adminstrative - groups specifie in the constraint." + only if the link contains none of the + administrative groups specified in the constraint." REFERENCE "1. RSVP-TE: Extensions to RSVP for LSP Tunnels, Awduche et al, RFC 3209, December 2001." ::= { mplsTunnelEntry 29 } mplsTunnelPathInUse OBJECT-TYPE SYNTAX MplsPathIndexOrZero MAX-ACCESS read-create STATUS current DESCRIPTION @@ -1229,21 +1288,25 @@ "This variable is used to create, modify, and/or delete a row in this table." ::= { mplsTunnelEntry 36 } mplsTunnelStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "This variable indicates the storage type for this - object." + object. This object cannot be modified if + mplsTunnelRowStatus is active(1). If this variable + is set to readOnly(5), and the corresponding entry + is removed, then the agent must remove this row + shortly thereafter [RFC2579]." ::= { mplsTunnelEntry 37 } -- End of mplsTunnelTable mplsTunnelHopListIndexNext OBJECT-TYPE SYNTAX Unsigned32 (0..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "This object contains an appropriate value to be used @@ -1266,59 +1329,58 @@ ::= { mplsTeObjects 3 } mplsTunnelHopTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsTunnelHopEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The mplsTunnelHopTable is used to indicate the hops, strict or loose, for an MPLS tunnel defined in mplsTunnelTable, when it is established via - signaling, for the outgoing direction of the + signalling, for the outgoing direction of the tunnel. Each row in this table is indexed by mplsTunnelHopListIndex. Each row also has a secondary index mplsTunnelHopIndex corresponding to the next hop that this row corresponds to. The first row in the table is the first hop after the origination point of the tunnel. In case we want to specify a particular interface on the originating LSR of an outgoing tunnel by which we want packets to exit the LSR, we specify this as the first hop for this tunnel in mplsTunnelHopTable." ::= { mplsTeObjects 4 } mplsTunnelHopEntry OBJECT-TYPE SYNTAX MplsTunnelHopEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents a tunnel hop. An entry is created by a network administrator for - signaled ERLSP set up by an MPLS signaling + signaled ERLSP set up by an MPLS signalling protocol." INDEX { mplsTunnelHopListIndex, mplsTunnelHopPathOptionIndex, mplsTunnelHopIndex } ::= { mplsTunnelHopTable 1 } MplsTunnelHopEntry ::= SEQUENCE { mplsTunnelHopListIndex MplsPathIndex, mplsTunnelHopPathOptionIndex MplsPathIndex, mplsTunnelHopIndex MplsPathIndex, mplsTunnelHopAddrType INTEGER, - mplsTunnelHopIpv4Addr InetAddressIPv4, - mplsTunnelHopIpv4PrefixLen Unsigned32, - mplsTunnelHopIpv6Addr InetAddressIPv6, - mplsTunnelHopIpv6PrefixLen Unsigned32, + mplsTunnelHopIpAddrType InetAddressType, + mplsTunnelHopIpAddr InetAddress, + mplsTunnelHopIpPrefixLen InetAddressPrefixLength, mplsTunnelHopAsNumber Unsigned32, mplsTunnelHopLspId MplsLSPID, mplsTunnelHopType INTEGER, mplsTunnelHopIncludeExclude INTEGER, mplsTunnelHopPathOptionName DisplayString, mplsTunnelHopEntryPathComp INTEGER, mplsTunnelHopRowStatus RowStatus, mplsTunnelHopStorageType StorageType } @@ -1346,179 +1408,189 @@ SYNTAX MplsPathIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "Secondary index into this table identifying a particular hop." ::= { mplsTunnelHopEntry 3 } mplsTunnelHopAddrType OBJECT-TYPE SYNTAX INTEGER { - ipV4(1), - ipV6(2), - asNumber(3), - lspid(4) + ipAddr(1), + asNumber(2), + lspId(3) } MAX-ACCESS read-create STATUS current DESCRIPTION - "Denotes the address type of this tunnel hop. Note - that lspId(4) is a valid option only for tunnels - signaled via CRLDP." - DEFVAL { ipV4 } + "Denotes the address type of this tunnel hop. If set + to ipAddr(1), this value denotes an IP address type + and also indicates that the + mplsTunnelHopIpAddrType, mplsTunnelHopIpAddr, and + mplsTunnelHopIpPrefixLen should be used to refer to + the IP address of this hop. The values contained in + mplsTunnelHopAsNumber, and mplsTunnelHopLspId + should be ignored. If this object is set to + asNumber(2), the IP address related objects should + be ignored, and the mplsTunnelHopAsNumber should be + refered to. If the object is set to lspId(3), then + all but the mplsTunnelHopLspId should be referred + to. Note that lspId(3) is a valid option only for + tunnels signaled via CRLDP." + DEFVAL { ipAddr } ::= { mplsTunnelHopEntry 4 } -mplsTunnelHopIpv4Addr OBJECT-TYPE - SYNTAX InetAddressIPv4 +mplsTunnelHopIpAddrType OBJECT-TYPE + SYNTAX InetAddressType MAX-ACCESS read-create STATUS current DESCRIPTION - "If mplsTunnelHopAddrType is set to ipV4(1), then - this value will contain the IPv4 address of this - hop. If mplsTunnelHopAddrType is set to lspid(4), - then this value will contain the Ingress LSR Router - ID of the Tunnel. This object is otherwise - insignificant and should contain a value of 0." + "If mplsTunnelHopAddrType is set to ipAddr(1) then + this value will contain the IP address type of this + hop. If mplsTunnelHopAddrType is set to lspId(3) + then this value will contain the IP address type of + the Ingress LSR Router ID contained in object + mplsTunnelHopIpAddr. Otherwise a management entity + SHOULD ignore this object." ::= { mplsTunnelHopEntry 5 } -mplsTunnelHopIpv4PrefixLen OBJECT-TYPE - SYNTAX Unsigned32 (0..32) +mplsTunnelHopIpAddr OBJECT-TYPE + SYNTAX InetAddress MAX-ACCESS read-create STATUS current DESCRIPTION - "If mplsTunnelHopAddrType is ipV4(1), then the prefix - length for this hop's IPv4 address is contained - herein. This object is otherwise insignificant and - should contain a value of 0." + "If mplsTunnelHopIpAddrType is set to ipV4(1) or + ipV6(2), then this value will contain respectively + the IPv4 address or the IPv6 address of this hop. + If mplsTunnelHopAddrType is set to lspId(3), then + this value will contain the Ingress LSR Router ID + of the Tunnel. Otherwise a management entity SHOULD + set this to 0 and an agent MUST ignore it. Likewise + an agent MUST return a value of 0 for a retrieval + operation." ::= { mplsTunnelHopEntry 6 } -mplsTunnelHopIpv6Addr OBJECT-TYPE - SYNTAX InetAddressIPv6 +mplsTunnelHopIpPrefixLen OBJECT-TYPE + SYNTAX InetAddressPrefixLength MAX-ACCESS read-create STATUS current DESCRIPTION - "If the mplsTunnelHopAddrType is set to ipV6(2), then - this variable contains the IPv6 address of this - hop. This object is otherwise insignificant and - should contain a value of 0." + "If mplsTunnelHopIpAddrType is set to ipV4(1) or + ipV6(2), then this value will contain an + appropriate prefix length for this hop. Otherwise a + management entity SHOULD set this object to 0 and + an agent MUST ignore it." ::= { mplsTunnelHopEntry 7 } -mplsTunnelHopIpv6PrefixLen OBJECT-TYPE - SYNTAX Unsigned32 (0..128) - MAX-ACCESS read-create - STATUS current - DESCRIPTION - "If mplsTunnelHopAddrType is set to ipV6(2), this - value will contain the prefix length for this hop's - IPv6 address. This object is otherwise - insignificant and should contain a value of 0." - ::= { mplsTunnelHopEntry 8 } - mplsTunnelHopAsNumber OBJECT-TYPE SYNTAX Unsigned32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION - "If mplsTunnelHopAddrType is set to asNumber(3), then + "If mplsTunnelHopAddrType is set to asNumber(2), then this value will contain the AS number of this hop. This object is otherwise insignificant and should contain a value of 0 to indicate this fact." - ::= { mplsTunnelHopEntry 9 } + ::= { mplsTunnelHopEntry 8 } mplsTunnelHopLspId OBJECT-TYPE SYNTAX MplsLSPID MAX-ACCESS read-create STATUS current DESCRIPTION - "If mplsTunnelHopAddrType is set to lspid(4), then + "If mplsTunnelHopAddrType is set to lspId(3), then this value will contain the LSPID of a tunnel of this hop. The present tunnel being configured is tunneled through this hop (using label stacking). This object is otherwise insignificant and should contain a value of 0 to indicate this fact." - ::= { mplsTunnelHopEntry 10 } + ::= { mplsTunnelHopEntry 9 } mplsTunnelHopType OBJECT-TYPE SYNTAX INTEGER { strict(1), loose(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "Denotes whether this tunnel hop is routed in a strict or loose fashion." - ::= { mplsTunnelHopEntry 11 } + ::= { mplsTunnelHopEntry 10 } mplsTunnelHopIncludeExclude OBJECT-TYPE SYNTAX INTEGER { include(1), exclude(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "If this value is set to include(1), then this indicates that this hop must be included in the tunnel's path. If this value is set to exclude(2), then this hop must be avoided when calculating the path for this tunnel. The default value of this object is include(1), so that by default all indicated hops are included in the CSPF path computation." DEFVAL { include } - ::= { mplsTunnelHopEntry 12 } + ::= { mplsTunnelHopEntry 11 } mplsTunnelHopPathOptionName OBJECT-TYPE SYNTAX DisplayString MAX-ACCESS read-create STATUS current DESCRIPTION "The description of this series of hops as they relate to the specified path option." - ::= { mplsTunnelHopEntry 13 } + ::= { mplsTunnelHopEntry 12 } mplsTunnelHopEntryPathComp OBJECT-TYPE SYNTAX INTEGER { dynamic(1), -- CSPF computed explicit(2) -- strict hop } MAX-ACCESS read-create STATUS current DESCRIPTION "If this value is set to dynamic, then the user should only specify the source and destination of the path and expect that the CSPF will calculate the remainder of the path. If this value is set to explicit, the user should specify the entire path for the tunnel to take. This path may contain strict or loose hops. Each hop along a specific path should have this object set to the same value" - ::= { mplsTunnelHopEntry 14 } + ::= { mplsTunnelHopEntry 13 } mplsTunnelHopRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This variable is used to create, modify, and/or delete a row in this table." - ::= { mplsTunnelHopEntry 15 } + ::= { mplsTunnelHopEntry 14 } mplsTunnelHopStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "This variable indicates the storage type for this - object." - ::= { mplsTunnelHopEntry 16 } + object. This object cannot be modified if + mplsTunnelHopRowStatus is active(1). If this + variable is set to readOnly(5), and the + corresponding entry is removed, then the agent must + remove this row shortly thereafter [RFC2579]." + ::= { mplsTunnelHopEntry 15 } -- End of mplsTunnelHopTable -- Begin of mplsTunnelResourceTable mplsTunnelResourceIndexNext OBJECT-TYPE SYNTAX Unsigned32 (0.. 2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION @@ -1554,31 +1626,31 @@ ::= { mplsTeObjects 6 } mplsTunnelResourceEntry OBJECT-TYPE SYNTAX MplsTunnelResourceEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents a set of resources for an MPLS tunnel. An entry can be created by a network administrator or by an SNMP agent as - instructed by any MPLS signaling protocol." + instructed by any MPLS signalling protocol." INDEX { mplsTunnelResourceIndex } ::= { mplsTunnelResourceTable 1 } MplsTunnelResourceEntry ::= SEQUENCE { mplsTunnelResourceIndex Unsigned32, mplsTunnelResourceMaxRate MplsBitRate, mplsTunnelResourceMeanRate MplsBitRate, mplsTunnelResourceMaxBurstSize MplsBurstSize, mplsTunnelResourceMeanBurstSize MplsBurstSize, - mplsTunnelResourceExcessBurstSize MplsBurstSize, + mplsTunnelResourceExBurstSize MplsBurstSize, mplsTunnelResourceFrequency INTEGER, mplsTunnelResourceWeight Unsigned32, mplsTunnelResourceRowStatus RowStatus, mplsTunnelResourceStorageType StorageType } mplsTunnelResourceIndex OBJECT-TYPE SYNTAX Unsigned32 (1..2147483647) MAX-ACCESS not-accessible STATUS current @@ -1596,23 +1668,23 @@ mplsTunnelResourceMaxRate, mplsTunnelResourceMeanRate, and mplsTunnelResourceMaxBurstSize to 0 indicates best- effort treatment. This object is copied to an instance of mplsTrafficParamMaxRate in mplsTrafficParamTable the OID of which is copied into the corresponding mplsInSegmentTrafficParamPtr." REFERENCE "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS - Label Switch Router Management Information Base, - Internet Draft , - December 2001." + Label Switching Router Management Information Base, + Internet Draft , + October 2002." ::= { mplsTunnelResourceEntry 2 } mplsTunnelResourceMeanRate OBJECT-TYPE SYNTAX MplsBitRate UNITS "bits per second" MAX-ACCESS read-create STATUS current DESCRIPTION "This object is copied into an instance of mplsTrafficParamMeanRate in the @@ -1617,29 +1689,28 @@ "This object is copied into an instance of mplsTrafficParamMeanRate in the mplsTrafficParamTable. The OID of this table entry is then copied into the corresponding mplsInSegmentTrafficParamPtr. When resource allocation is performed as requested by this TSpec object, it is copied into an entry in mplsTrafficParamTable [LSRMIB]: mplsTunnelInMeanRate to mplsTrafficParamMeanRate. - The OID of this entry is copied to mplsInSegmentTrafficParamPtr of the corresponding in-segment entry." REFERENCE "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS - Label Switch Router Management Information Base, - Internet Draft , - December 2001." + Label Switching Router Management Information Base, + Internet Draft , + October 2002." ::= { mplsTunnelResourceEntry 3 } mplsTunnelResourceMaxBurstSize OBJECT-TYPE SYNTAX MplsBurstSize UNITS "bytes" MAX-ACCESS read-create STATUS current DESCRIPTION "The maximum burst size in bytes. This object is copied to mplsInSegmentMaxBurstSize of the @@ -1647,38 +1718,38 @@ When resource allocation is performed as requested by this TSpec object, it is copied into an entry in mplsTrafficParamTable [LSRMIB]: mplsTunnelInMaxBurstSize to mplsTrafficParamMaxBurstSize. The OID of this entry is copied to mplsInSegmentTrafficParamPtr of the corresponding in-segment entry." REFERENCE "Srinivasan, C., Viswanathan, A., and T. Nadeau, MPLS - Label Switch Router Management Information Base, - Internet Draft , - December 2001." + Label Switching Router Management Information Base, + Internet Draft , + October 2002." ::= { mplsTunnelResourceEntry 4 } mplsTunnelResourceMeanBurstSize OBJECT-TYPE SYNTAX MplsBurstSize UNITS "bytes" MAX-ACCESS read-create STATUS current DESCRIPTION "The mean burst size in bytes. The implementations which do not implement this variable must return 0 for this value and must not allow a user to set this value." ::= { mplsTunnelResourceEntry 5 } -mplsTunnelResourceExcessBurstSize OBJECT-TYPE +mplsTunnelResourceExBurstSize OBJECT-TYPE SYNTAX MplsBurstSize UNITS "bytes" MAX-ACCESS read-create STATUS current DESCRIPTION "The Excess burst size in bytes. The implementations which do not implement this variable must return 0 for this value and must not allow a user to set this value." REFERENCE @@ -1722,79 +1793,83 @@ "This variable is used to create, modify, and/or delete a row in this table." ::= { mplsTunnelResourceEntry 9 } mplsTunnelResourceStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "This variable indicates the storage type for this - object." + object. This object cannot be modified if + mplsTunnelResourceRowStatus is active(1). If this + variable is set to readOnly(5), and the + corresponding entry is removed, then the agent must + remove this row shortly thereafter [RFC2579]." ::= { mplsTunnelResourceEntry 10 } -- End mplsTunnelResourceTable -- Tunnel Actual Route Hop table. mplsTunnelARHopTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsTunnelARHopEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The mplsTunnelARHopTable is used to indicate the hops, strict or loose, for an MPLS tunnel defined in mplsTunnelTable, as reported by the MPLS - signaling protocol, for the outgoing direction of + signalling protocol, for the outgoing direction of the tunnel. Each row in this table is indexed by mplsTunnelARHopListIndex. Each row also has a secondary index mplsTunnelARHopIndex, corresponding to the next hop that this row corresponds to. The first row in the table is the first hop after the origination point of the tunnel. In case we want to specify a particular interface on the originating LSR of an outgoing tunnel by which we want packets to exit the LSR, we specify this as the first hop for this tunnel in mplsTunnelARHopTable. Please note that since the information necessary to build entries within this table are not provided by - some MPLS signaling protocols, implementation of + some MPLS signalling protocols, implementation of this table is optional. Furthermore, since the information in this table is actually provided by - the MPLS signaling protocol after the path has been - set-up, the entries in this table are provided only - for observation, and hence, all variables in this - table are accessible exclusively as read-only." + the MPLS signalling protocol after the path has + been set-up, the entries in this table are provided + only for observation, and hence, all variables in + this table are accessible exclusively as read- + only." ::= { mplsTeObjects 7 } mplsTunnelARHopEntry OBJECT-TYPE SYNTAX MplsTunnelARHopEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents a tunnel hop. An entry is created by a network administrator for - signaled ERLSP set up by an MPLS signaling + signaled ERLSP set up by an MPLS signalling protocol." INDEX { mplsTunnelARHopListIndex, mplsTunnelARHopIndex } ::= { mplsTunnelARHopTable 1 } MplsTunnelARHopEntry ::= SEQUENCE { mplsTunnelARHopListIndex MplsPathIndex, mplsTunnelARHopIndex MplsPathIndex, mplsTunnelARHopAddrType INTEGER, - mplsTunnelARHopIpv4Addr InetAddressIPv4, - mplsTunnelARHopIpv4PrefixLen Unsigned32, - mplsTunnelARHopIpv6Addr InetAddressIPv6, - mplsTunnelARHopIpv6PrefixLen Unsigned32, + mplsTunnelARHopIpAddrType InetAddressType, + mplsTunnelARHopIpAddr InetAddress, + mplsTunnelARHopIpPrefixLen InetAddressPrefixLength, mplsTunnelARHopAsNumber Unsigned32, mplsTunnelARHopLspId MplsLSPID } mplsTunnelARHopListIndex OBJECT-TYPE SYNTAX MplsPathIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "Primary index into this table identifying a @@ -1805,97 +1880,89 @@ SYNTAX MplsPathIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "Secondary index into this table identifying the particular hop." ::= { mplsTunnelARHopEntry 2 } mplsTunnelARHopAddrType OBJECT-TYPE SYNTAX INTEGER { - ipV4(1), - ipV6(2), - asNumber(3), - lspId(4) + ipAddr(1), + asNumber(2), + lspId(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "Denotes the address type of this tunnel hop." - DEFVAL { ipV4 } + DEFVAL { ipAddr } ::= { mplsTunnelARHopEntry 3 } -mplsTunnelARHopIpv4Addr OBJECT-TYPE - SYNTAX InetAddressIPv4 - MAX-ACCESS read-only +mplsTunnelARHopIpAddrType OBJECT-TYPE + SYNTAX InetAddressType + MAX-ACCESS read-create STATUS current DESCRIPTION - "If mplsTunnelARHopAddrType is set to ipV4(1), then - this value will contain the IPv4 address of this - hop. This object is otherwise insignificant and - should contain a value of 0." + "If mplsTunnelARHopAddrType is set to ipAddr(1) then + this value will contain the IP address type of this + hop. If mplsTunnelARHopAddrType is set to + asNumber(2) or lspId(3) then a management entity + SHOULD ignore this object." ::= { mplsTunnelARHopEntry 4 } -mplsTunnelARHopIpv4PrefixLen OBJECT-TYPE - SYNTAX Unsigned32 (0..32) +mplsTunnelARHopIpAddr OBJECT-TYPE + SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION - "If mplsTunnelARHopAddrType is ipV4(1), then the - prefix length for this hop's IPv4 address is - contained herein. This object is otherwise - insignificant and should contain a value of 0." + "If mplsTunnelARHopIpAddrType is set to ipV4(1) or + ipV6(2), then this value will contain respectively + the IPv4 address or the IPv6 address of this hop. + Otherwise a management entity SHOULD set this to 0 + and an agent MUST ignore it. Likewise an agent MUST + return a value of 0 for a retrieval operation." ::= { mplsTunnelARHopEntry 5 } -mplsTunnelARHopIpv6Addr OBJECT-TYPE - SYNTAX InetAddressIPv6 +mplsTunnelARHopIpPrefixLen OBJECT-TYPE + SYNTAX InetAddressPrefixLength MAX-ACCESS read-only STATUS current DESCRIPTION - "If the mplsTunnelARHopAddrType is set to ipV6(2), - then this variable contains the IPv6 address of - this hop. This object is otherwise insignificant - and should contain a value of 0." + "If mplsTunnelARHopIpAddrType is set to ipV4(1) or + ipV6(2), then this value will contain an + appropriate prefix length for this hop. Otherwise a + management entity SHOULD set this object to 0 and + an agent MUST ignore it." ::= { mplsTunnelARHopEntry 6 } -mplsTunnelARHopIpv6PrefixLen OBJECT-TYPE - SYNTAX Unsigned32 (0..128) - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "If mplsTunnelARHopAddrType is set to ipV6(2), this - value will contain the prefix length for this hop's - IPv6 address. This object is otherwise - insignificant and should contain a value of 0." - ::= { mplsTunnelARHopEntry 7 } - mplsTunnelARHopAsNumber OBJECT-TYPE SYNTAX Unsigned32 (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION - "If mplsTunnelARHopAddrType is set to asNumber(3), + "If mplsTunnelARHopAddrType is set to asNumber(2), then this value will contain the AS number of this hop. This object is otherwise insignificant and should contain a value of 0 to indicate this fact." - ::= { mplsTunnelARHopEntry 8 } + ::= { mplsTunnelARHopEntry 7 } mplsTunnelARHopLspId OBJECT-TYPE SYNTAX MplsLSPID MAX-ACCESS read-only STATUS current DESCRIPTION - "If mplsTunnelARHopAddrType is set to lspid(4), then + "If mplsTunnelARHopAddrType is set to lspId(3), then this value will contain the LSP ID of this hop. This object is otherwise insignificant and should contain a value of 0 to indicate this fact." - ::= { mplsTunnelARHopEntry 9 } + ::= { mplsTunnelARHopEntry 8 } -- End of mplsTunnelARHopTable -- Tunnel Computed Hop table. mplsTunnelCHopTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsTunnelCHopEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION @@ -1936,24 +2003,23 @@ entry in this table is created by a constraint- based routing protocol based on the hops specified in the corresponding mplsTunnelHopTable." INDEX { mplsTunnelCHopListIndex, mplsTunnelCHopIndex } ::= { mplsTunnelCHopTable 1 } MplsTunnelCHopEntry ::= SEQUENCE { mplsTunnelCHopListIndex MplsPathIndex, mplsTunnelCHopIndex MplsPathIndex, mplsTunnelCHopAddrType INTEGER, - mplsTunnelCHopIpv4Addr InetAddressIPv4, - mplsTunnelCHopIpv4PrefixLen Unsigned32, - mplsTunnelCHopIpv6Addr InetAddressIPv6, - mplsTunnelCHopIpv6PrefixLen Unsigned32, + mplsTunnelCHopIpAddrType InetAddressType, + mplsTunnelCHopIpAddr InetAddress, + mplsTunnelCHopIpPrefixLen InetAddressPrefixLength, mplsTunnelCHopAsNumber Unsigned32, mplsTunnelCHopLspId MplsLSPID, mplsTunnelCHopType INTEGER } mplsTunnelCHopListIndex OBJECT-TYPE SYNTAX MplsPathIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION @@ -1965,111 +2031,103 @@ SYNTAX MplsPathIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "Secondary index into this table identifying the particular hop." ::= { mplsTunnelCHopEntry 2 } mplsTunnelCHopAddrType OBJECT-TYPE SYNTAX INTEGER { - ipV4(1), - ipV6(2), - asNumber(3), - lspId(4) + ipAddr(1), + asNumber(2), + lspId(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "Denotes the address type of this tunnel hop. Note - that lspId(4) is a valid option only for tunnels + that lspId(3) is a valid option only for tunnels signaled via CRLDP." - DEFVAL { ipV4 } + DEFVAL { ipAddr } ::= { mplsTunnelCHopEntry 3 } -mplsTunnelCHopIpv4Addr OBJECT-TYPE - SYNTAX InetAddressIPv4 - MAX-ACCESS read-only +mplsTunnelCHopIpAddrType OBJECT-TYPE + SYNTAX InetAddressType + MAX-ACCESS read-create STATUS current DESCRIPTION - "If mplsTunnelCHopAddrType is set to ipV4(1), then - this value will contain the IPv4 address of this - hop. This object is otherwise insignificant and - should contain a value of 0." + "If mplsTunnelCHopAddrType is set to ipAddr(1) then + this value will contain the IP address type of this + hop. If mplsTunnelCHopAddrType is set to + asNumber(2) or lspId(3) then a management entity + SHOULD ignore this object." ::= { mplsTunnelCHopEntry 4 } -mplsTunnelCHopIpv4PrefixLen OBJECT-TYPE - SYNTAX Unsigned32 (0..32) +mplsTunnelCHopIpAddr OBJECT-TYPE + SYNTAX InetAddress MAX-ACCESS read-only STATUS current DESCRIPTION - "If mplsTunnelCHopAddrType is ipV4(1), then the - prefix length for this hop's IPv4 address is - contained herein. This object is otherwise - insignificant and should contain a value of 0." + "If mplsTunnelCHopIpAddrType is set to ipV4(1) or + ipV6(2), then this value will contain respectively + the IPv4 address or the IPv6 address of this hop. + Otherwise a management entity SHOULD set this to 0 + and an agent MUST ignore it. Likewise an agent MUST + return a value of 0 for a retrieval operation." ::= { mplsTunnelCHopEntry 5 } -mplsTunnelCHopIpv6Addr OBJECT-TYPE - SYNTAX InetAddressIPv6 +mplsTunnelCHopIpPrefixLen OBJECT-TYPE + SYNTAX InetAddressPrefixLength MAX-ACCESS read-only STATUS current DESCRIPTION - "If the mplsTunnelCHopAddrType is set to ipV6(2), - then this variable contains the IPv6 address of - this hop. This object is otherwise insignificant - and should contain a value of 0." + "If mplsTunnelCHopIpAddrType is set to ipV4(1) or + ipV6(2), then this value will contain an + appropriate prefix length for this hop. Otherwise a + management entity SHOULD set this object to 0 and + an agent MUST ignore it. " ::= { mplsTunnelCHopEntry 6 } -mplsTunnelCHopIpv6PrefixLen OBJECT-TYPE - SYNTAX Unsigned32 (0..128) - MAX-ACCESS read-only - STATUS current - DESCRIPTION - "If mplsTunnelCHopAddrType is set to ipV6(2), this - value will contain the prefix length for this hop's - IPv6 address. This object is otherwise - insignificant and should contain a value of 0." - ::= { mplsTunnelCHopEntry 7 } - mplsTunnelCHopAsNumber OBJECT-TYPE SYNTAX Unsigned32 (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION - "If mplsTunnelCHopAddrType is set to asNumber(3), + "If mplsTunnelCHopAddrType is set to asNumber(2), then this value will contain the AS number of this hop. This object is otherwise insignificant and should contain a value of 0 to indicate this fact." - ::= { mplsTunnelCHopEntry 8 } + ::= { mplsTunnelCHopEntry 7 } mplsTunnelCHopLspId OBJECT-TYPE SYNTAX MplsLSPID MAX-ACCESS read-only STATUS current DESCRIPTION - "If mplsTunnelCHopAddrType is set to lspid(4), then + "If mplsTunnelCHopAddrType is set to lspId(3), then this value will contain the LSP ID of this hop. This object is otherwise insignificant and should contain a value of 0 to indicate this fact." - ::= { mplsTunnelCHopEntry 9 } + ::= { mplsTunnelCHopEntry 8 } mplsTunnelCHopType OBJECT-TYPE SYNTAX INTEGER { strict(1), loose(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "Denotes whether this is tunnel hop is routed in a strict or loose fashion." - ::= { mplsTunnelCHopEntry 10 } + ::= { mplsTunnelCHopEntry 9 } -- End of mplsTunnelCHopTable -- MPLS Tunnel Performance Table. mplsTunnelPerfTable OBJECT-TYPE SYNTAX SEQUENCE OF MplsTunnelPerfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION @@ -2111,21 +2169,21 @@ DESCRIPTION "High capacity counter for number of packets forwarded by the tunnel." ::= { mplsTunnelPerfEntry 2 } mplsTunnelPerfErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION - "Number of errored packets." + "Number of packets with errors." ::= { mplsTunnelPerfEntry 3 } mplsTunnelPerfBytes OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of bytes forwarded by the tunnel." ::= { mplsTunnelPerfEntry 4 } @@ -2160,44 +2218,44 @@ mplsTunnelCRLDPResEntry OBJECT-TYPE SYNTAX MplsTunnelCRLDPResEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in this table represents a set of resources for an MPLS tunnel established using CRLDP (mplsTunnelSignallingProto equal to crldp (3)). An entry can be created by a network administrator or by an SNMP agent as instructed by any MPLS - signaling protocol." + signalling protocol." INDEX { mplsTunnelResourceIndex } ::= { mplsTunnelCRLDPResTable 1 } MplsTunnelCRLDPResEntry ::= SEQUENCE { mplsTunnelCRLDPResMeanBurstSize MplsBurstSize, - mplsTunnelCRLDPResExcessBurstSize MplsBurstSize, - mplsTunnelCRLDPResFrequency Integer32, + mplsTunnelCRLDPResExBurstSize MplsBurstSize, + mplsTunnelCRLDPResFrequency INTEGER, mplsTunnelCRLDPResWeight Unsigned32, mplsTunnelCRLDPResFlags Unsigned32, mplsTunnelCRLDPResRowStatus RowStatus, mplsTunnelCRLDPResStorageType StorageType } mplsTunnelCRLDPResMeanBurstSize OBJECT-TYPE SYNTAX MplsBurstSize UNITS "bytes" MAX-ACCESS read-create STATUS current DESCRIPTION "The mean burst size in bytes." ::= { mplsTunnelCRLDPResEntry 2 } -mplsTunnelCRLDPResExcessBurstSize OBJECT-TYPE +mplsTunnelCRLDPResExBurstSize OBJECT-TYPE SYNTAX MplsBurstSize UNITS "bytes" MAX-ACCESS read-create STATUS current DESCRIPTION "The Excess burst size in bytes." REFERENCE "CR-LDP Specification, Section 4.3." ::= { mplsTunnelCRLDPResEntry 3 } @@ -2251,46 +2309,49 @@ F4 - Corresponds to the CBS. F5 - Corresponds to the EBS. F6 - Corresponds to the Weight. Each flag if is a Negotiable Flag corresponding to a Traffic Parameter. The Negotiable Flag value zero denotes Not Negotiable and value one denotes Negotiable." REFERENCE "1. Section 4.3, Constraint-Based LSP Setup using - LDP, Jamoussi (Editor), Internet Draft , November 2001" + LDP, Jamoussi (Editor), RFC 3212, January 2002" DEFVAL { 0 } ::= { mplsTunnelCRLDPResEntry 6 } mplsTunnelCRLDPResRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This variable is used to create, modify, and/or delete a row in this table." ::= { mplsTunnelCRLDPResEntry 7 } mplsTunnelCRLDPResStorageType OBJECT-TYPE SYNTAX StorageType MAX-ACCESS read-create STATUS current DESCRIPTION "This variable indicates the storage type for this - object." + object. This object cannot be modified if + mplsTunnelCRLDPResResourceRowStatus is active(1). + If this variable is set to readOnly(5), and the + corresponding entry is removed, then the agent must + remove this row shortly thereafter [RFC2579]." ::= { mplsTunnelCRLDPResEntry 8 } -- Notifications. -mplsTunnelTrapEnable OBJECT-TYPE +mplsTunnelNotificationEnable OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-write STATUS current DESCRIPTION "If this object is true, then it enables the generation of mplsTunnelUp and mplsTunnelDown traps, otherwise these traps are not emitted." DEFVAL { false } ::= { mplsTeObjects 11 } @@ -2301,80 +2362,80 @@ } STATUS current DESCRIPTION "This notification is generated when a mplsTunnelOperStatus object for one of the configured tunnels is about to leave the down state and transition into some other state (but not into the notPresent state). This other state is indicated by the included value of mplsTunnelOperStatus." - ::= { mplsTeNotifyPrefix 1 } + ::= { mplsTeNotifications 1 } mplsTunnelDown NOTIFICATION-TYPE OBJECTS { mplsTunnelAdminStatus, mplsTunnelOperStatus } STATUS current DESCRIPTION "This notification is generated when a mplsTunnelOperStatus object for one of the configured tunnels is about to enter the down state from some other state (but not from the notPresent state). This other state is indicated by the included value of mplsTunnelOperStatus." - ::= { mplsTeNotifyPrefix 2 } + ::= { mplsTeNotifications 2 } mplsTunnelRerouted NOTIFICATION-TYPE OBJECTS { mplsTunnelAdminStatus, mplsTunnelOperStatus } STATUS current DESCRIPTION "This notification is generated when a tunnel is rerouted. If the actual path is used, then this tunnel's entry MAY contain the new path for this tunnel some time after this trap is issued by the agent." - ::= { mplsTeNotifyPrefix 3 } + ::= { mplsTeNotifications 3 } mplsTunnelReoptimized NOTIFICATION-TYPE OBJECTS { mplsTunnelAdminStatus, mplsTunnelOperStatus } STATUS current DESCRIPTION "This notification is generated when a tunnel is reoptimized. If the actual path is used, then this tunnel's entry MAY contain the new path for this tunnel some time after this trap is issued by the agent." - ::= { mplsTeNotifyPrefix 4 } + ::= { mplsTeNotifications 4 } -- End of notifications. -- Module compliance. mplsTeGroups OBJECT IDENTIFIER ::= { mplsTeConformance 1 } mplsTeCompliances OBJECT IDENTIFIER ::= { mplsTeConformance 2 } mplsTeModuleCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents that support the - MPLS TE MIB." + MPLS-TE-MIB." MODULE -- this module -- The mandatory group has to be implemented by all -- LSRs that originate/terminate ESLSPs/tunnels. -- In addition, depending on the type of tunnels -- supported, other groups become mandatory as -- explained below. MANDATORY-GROUPS { mplsTunnelGroup, @@ -2406,25 +2468,37 @@ returning false(1)." GROUP mplsTunnelIsIntfcGroup DESCRIPTION "This group is mandatory for devices which support tunnels that are interfaces, in addition to mplsTunnelGroup. The following constraints apply: mplsTunnelIsIf must at least be read-only returning true(2)." + GROUP mplsTeNotificationGroup + DESCRIPTION + "Objects in this group are optional unless + notifications are supported." + + GROUP mplsTunnelCRLDPResOptionalGroup + DESCRIPTION + "Objects in this group are oiptional except for + implementations supporting the CR-LDP protocol for + signalling of TE tunnels." + GROUP mplsTunnelOptionalGroup DESCRIPTION "Objects in this group are optional." -- mplsTunnelTable + OBJECT mplsTunnelName MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsTunnelDescr MIN-ACCESS read-only DESCRIPTION "Write access is not required." @@ -2543,21 +2618,20 @@ createAndGo(4), destroy(6) } MIN-ACCESS read-only DESCRIPTION "The notReady(3) and createAndWait(5) states need not be supported. Write access is not required." OBJECT mplsTunnelStorageType SYNTAX INTEGER { other(1) } - MIN-ACCESS read-only DESCRIPTION "Only other (1) needs to be supported." OBJECT mplsTunnelPathInUse MIN-ACCESS read-only DESCRIPTION "Read-only support is required." OBJECT mplsTunnelRole SYNTAX INTEGER { head(1) } @@ -2573,37 +2648,31 @@ MIN-ACCESS read-only DESCRIPTION "Read-only support is required." -- mplsTunnelHopTable OBJECT mplsTunnelHopAddrType MIN-ACCESS read-only DESCRIPTION "Write access is not required." - - OBJECT mplsTunnelHopIpv4Addr - MIN-ACCESS read-only - DESCRIPTION - "Write access is not required." - - OBJECT mplsTunnelHopIpv4PrefixLen + OBJECT mplsTunnelHopIpAddrType MIN-ACCESS read-only DESCRIPTION "Write access is not required." - OBJECT mplsTunnelHopIpv6Addr + OBJECT mplsTunnelHopIpAddr MIN-ACCESS read-only DESCRIPTION "Write access is not required." - OBJECT mplsTunnelHopIpv6PrefixLen + OBJECT mplsTunnelHopIpPrefixLen MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsTunnelHopAsNumber MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsTunnelHopLspId @@ -2640,21 +2708,20 @@ createAndGo(4), destroy(6) } MIN-ACCESS read-only DESCRIPTION "The notReady(3) and createAndWait(5) states need not be supported. Write access is not required." OBJECT mplsTunnelHopStorageType SYNTAX INTEGER { other(1) } - MIN-ACCESS read-only DESCRIPTION "Only other (1) needs to be supported." -- mplsTunnelResourceTable OBJECT mplsTunnelResourceMaxRate MIN-ACCESS read-only DESCRIPTION "Write access is not required." @@ -2666,30 +2733,29 @@ OBJECT mplsTunnelResourceMaxBurstSize MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsTunnelResourceMeanBurstSize MIN-ACCESS read-only DESCRIPTION "Write access is not required." - OBJECT mplsTunnelResourceExcessBurstSize + OBJECT mplsTunnelResourceExBurstSize MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsTunnelResourceFrequency MIN-ACCESS read-only DESCRIPTION "Write access is not required." - OBJECT mplsTunnelResourceWeight MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT mplsTunnelResourceRowStatus SYNTAX INTEGER { active(1), notInService(2), createAndGo(4), @@ -2695,21 +2761,20 @@ createAndGo(4), destroy(6) } MIN-ACCESS read-only DESCRIPTION "The notReady(3) and createAndWait(5) states need not be supported. Write access is not required." OBJECT mplsTunnelResourceStorageType SYNTAX INTEGER { other(1) } - MIN-ACCESS read-only DESCRIPTION "Only other (1) needs to be supported." -- mplsTunnelPerfTable OBJECT mplsTunnelPerfPackets MIN-ACCESS read-only DESCRIPTION "Write access is not required." @@ -2744,21 +2809,21 @@ mplsTunnelDescr, mplsTunnelOwner, mplsTunnelXCPointer, mplsTunnelIfIndex, mplsTunnelHopTableIndex, mplsTunnelARHopTableIndex, mplsTunnelCHopTableIndex, mplsTunnelAdminStatus, mplsTunnelOperStatus, mplsTunnelRowStatus, - mplsTunnelTrapEnable, + mplsTunnelNotificationEnable, mplsTunnelStorageType, mplsTunnelConfigured, mplsTunnelActive, mplsTunnelPrimaryInstance, mplsTunnelPrimaryTimeUp, mplsTunnelPathChanges, mplsTunnelLastPathChange, mplsTunnelCreationTime, mplsTunnelStateTransitions, mplsTunnelIncludeAnyAffinity, @@ -2799,44 +2864,44 @@ mplsTunnelSignaledGroup OBJECT-GROUP OBJECTS { mplsTunnelSetupPrio, mplsTunnelHoldingPrio, mplsTunnelSignallingProto, mplsTunnelLocalProtectInUse, mplsTunnelSessionAttributes, mplsTunnelHopListIndexNext, mplsTunnelHopAddrType, - mplsTunnelHopIpv4Addr, - mplsTunnelHopIpv4PrefixLen, - mplsTunnelHopIpv6Addr, - mplsTunnelHopIpv6PrefixLen, + mplsTunnelHopIpAddrType, + mplsTunnelHopIpAddr, + mplsTunnelHopIpPrefixLen, mplsTunnelHopAsNumber, mplsTunnelHopLspId, mplsTunnelHopType, mplsTunnelHopIncludeExclude, mplsTunnelHopPathOptionName, mplsTunnelHopEntryPathComp, mplsTunnelHopRowStatus, mplsTunnelHopStorageType } STATUS current DESCRIPTION "Object needed to implement signaled tunnels." ::= { mplsTeGroups 3 } mplsTunnelScalarGroup OBJECT-GROUP OBJECTS { mplsTunnelConfigured, mplsTunnelActive, mplsTunnelTEDistProto, - mplsTunnelMaxHops + mplsTunnelMaxHops, + mplsTunnelNotifMaxRate } STATUS current DESCRIPTION "Scalar object needed to implement MPLS tunnels." ::= { mplsTeGroups 4 } mplsTunnelIsIntfcGroup OBJECT-GROUP OBJECTS { mplsTunnelIsIf } STATUS current DESCRIPTION @@ -2852,50 +2917,48 @@ interfaces." ::= { mplsTeGroups 6 } mplsTunnelOptionalGroup OBJECT-GROUP OBJECTS { mplsTunnelResourceIndexNext, mplsTunnelResourceMaxRate, mplsTunnelResourceMeanRate, mplsTunnelResourceMaxBurstSize, mplsTunnelResourceMeanBurstSize, - mplsTunnelResourceExcessBurstSize, + mplsTunnelResourceExBurstSize, mplsTunnelResourceFrequency, mplsTunnelResourceWeight, mplsTunnelResourceRowStatus, mplsTunnelResourceStorageType, mplsTunnelARHopAddrType, - mplsTunnelARHopIpv4Addr, - mplsTunnelARHopIpv4PrefixLen, - mplsTunnelARHopIpv6Addr, - mplsTunnelARHopIpv6PrefixLen, + mplsTunnelARHopIpAddrType, + mplsTunnelARHopIpAddr, + mplsTunnelARHopIpPrefixLen, mplsTunnelARHopAsNumber, mplsTunnelARHopLspId, mplsTunnelCHopAddrType, - mplsTunnelCHopIpv4Addr, - mplsTunnelCHopIpv4PrefixLen, - mplsTunnelCHopIpv6Addr, - mplsTunnelCHopIpv6PrefixLen, + mplsTunnelCHopIpAddrType, + mplsTunnelCHopIpAddr, + mplsTunnelCHopIpPrefixLen, mplsTunnelCHopAsNumber, mplsTunnelCHopLspId, mplsTunnelCHopType } STATUS current DESCRIPTION "The objects in this group are optional." ::= { mplsTeGroups 7 } mplsTunnelCRLDPResOptionalGroup OBJECT-GROUP OBJECTS { mplsTunnelCRLDPResMeanBurstSize, - mplsTunnelCRLDPResExcessBurstSize, + mplsTunnelCRLDPResExBurstSize, mplsTunnelCRLDPResFrequency, mplsTunnelCRLDPResWeight, mplsTunnelCRLDPResFlags, mplsTunnelCRLDPResRowStatus, mplsTunnelCRLDPResStorageType } STATUS current DESCRIPTION "Set of objects implemented for resources applicable for tunnels signaled using CR-LDP." @@ -2909,21 +2972,21 @@ mplsTunnelReoptimized } STATUS current DESCRIPTION "Set of notifications implemented in this module. None is mandatory." ::= { mplsTeGroups 9 } END -11. Security Considerations +12. Security Considerations There are a number of management objects defined in this MIB that have a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. It is thus important to control even GET access to these @@ -2941,48 +3004,49 @@ features as provided by the SNMPv3 framework. Specifically, the use of the User-based Security Model [RFC2574] and the View- based Access Control [RFC2575] is recommended. It is then a customer/user responsibility to ensure that the SNMP entity giving access to an instance of this MIB, is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. -12. Acknowledgments +13. Acknowledgments We wish to thank Adrian Farrel, Eric Gray, Joan Cucchiara, Patrick Kerharo, Paul Langille and Mike Piecuch for their comments on this draft. -13. References +14. References [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", RFC 1700, October 1994. See also: http://www.isi.edu/in- notes/iana/assignments/smi-numbers + [TCMIB] Nadeau, T., Cucchiara, J., Srinivasan, C, Viswanathan, A. and H. Sjostrand, "Definition of Textual Conventions and OBJECT-IDENTITIES for Multi-Protocol Label Switching (MPLS) Management", Internet Draft - , January + , October 2002. [LSRMIB] Srinivasan, C., Viswanathan, A. and T. - Nadeau, "MPLS Label Switch Router Management + Nadeau, "MPLS Multiprotocol Label Switching + (MPLS) Label Switching Router Management Information Base ", Internet Draft , January 2002. + ietf-mpls-lsr-mib-09.txt>, October 2002. [CRLDP] B. Jamoussi (Editor), "Constraint-Based LSP - Setup using LDP", Internet Draft , November 2001. + Setup using LDP", RFC 3212, January 2002. [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification of Management Information for TCP/IP-based Internets", RFC 1155, May 1990. [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network Management Protocol", RFC 1157, May 1990. [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB @@ -3066,21 +3130,21 @@ [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol Label Switching Architecture", RFC 3031, January 2001. [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP Tunnels", RFC 3209, December 2001. -14. Authors' Addresses +15. Authors' Addresses Cheenu Srinivasan Parama Networks, Inc. 1030 Broad Street Shrewsbury, NJ 07702 Phone: +1-732-544-9120 x731 Email: cheenu@paramanet.com Arun Viswanathan Force10 Networks, Inc. @@ -3089,21 +3153,21 @@ Phone: +1-408-571-3516 Email: arun@force10networks.com Thomas D. Nadeau Cisco Systems, Inc. 300 Apollo Drive Chelmsford, MA 01824 Phone: +1-978-244-3051 Email: tnadeau@cisco.com -15. Full Copyright Statement +16. Full Copyright Statement Copyright (C) The Internet Society (2001). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on