MPLS-TE-STD-MIB DEFINITIONS ::= BEGINIMPORTS   MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,   Integer32, Unsigned32, Counter32, Counter64, TimeTicks,   zeroDotZero      FROM SNMPv2-SMI                                    -- [RFC2578]   MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP      FROM SNMPv2-CONF                                   -- [RFC2580]   TruthValue, RowStatus, RowPointer, StorageType,   TimeStamp      FROM SNMPv2-TC                                     -- [RFC2579]   InterfaceIndexOrZero, ifGeneralInformationGroup,   ifCounterDiscontinuityGroup      FROM IF-MIB                                        -- [RFC2863]   mplsStdMIB, MplsBitRate, MplsBurstSize, MplsLSPID,   MplsTunnelIndex, MplsTunnelInstanceIndex,   MplsTunnelAffinity, MplsExtendedTunnelId, MplsPathIndex,   MplsPathIndexOrZero, MplsOwner, TeHopAddressType,   TeHopAddress, TeHopAddressAS, TeHopAddressUnnum      FROM MPLS-TC-STD-MIB                               -- [RFC3811]   SnmpAdminString      FROM SNMP-FRAMEWORK-MIB                            -- [RFC3411]   IndexIntegerNextFree      FROM DIFFSERV-MIB                                  -- [RFC3289]   InetAddressPrefixLength      FROM INET-ADDRESS-MIB                              -- [RFC3291]   ;mplsTeStdMIB MODULE-IDENTITY   LAST-UPDATED      "200406030000Z" -- June 3, 2004   ORGANIZATION      "Multiprotocol Label Switching (MPLS) Working Group"   CONTACT-INFO        "        Cheenu Srinivasan                 Bloomberg L.P.         Email:  cheenu@bloomberg.net                 Arun Viswanathan                 Force10 Networks, Inc.         Email:  arunv@force10networks.com                 Thomas D. Nadeau                 Cisco Systems, Inc.         Email:  tnadeau@cisco.com                Comments about this document should be emailed                directly to the MPLS working group mailing list at                mpls@uu.net."   DESCRIPTION         "Copyright (C) The Internet Society (2004). The         initial version of this MIB module was published         in RFC 3812. For full legal notices see the RFC         itself or see: http://www.ietf.org/copyrights/ianamib.html         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), RFC 3212, January 2002         3. Requirements for Traffic Engineering Over MPLS,          Awduche, D., Malcolm, J., Agogbua, J., O'Dell, M.,          and J. McManus, [RFC2702], September 1999"   -- Revision history.   REVISION      "200406030000Z" -- June 3, 2004   DESCRIPTION        "Initial version issued as part of RFC 3812."   ::= { mplsStdMIB 3 }-- Top level components of this MIB module.-- trapsmplsTeNotifications OBJECT IDENTIFIER ::= { mplsTeStdMIB 0 }-- tables, scalarsmplsTeScalars       OBJECT IDENTIFIER ::= { mplsTeStdMIB 1 }mplsTeObjects       OBJECT IDENTIFIER ::= { mplsTeStdMIB 2 }-- conformancemplsTeConformance   OBJECT IDENTIFIER ::= { mplsTeStdMIB 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          mplsTunnelRowStatus is active(1)."   ::= { mplsTeScalars 1 }mplsTunnelActive OBJECT-TYPE   SYNTAX        Unsigned32   MAX-ACCESS    read-only   STATUS        current   DESCRIPTION        "The number of tunnels active on this device. A          tunnel is considered active if the          mplsTunnelOperStatus is up(1)."   ::= { mplsTeScalars 2 }mplsTunnelTEDistProto OBJECT-TYPE   SYNTAX        BITS {          other (0),          ospf (1),          isis (2)      }   MAX-ACCESS    read-only   STATUS        current   DESCRIPTION        "The traffic engineering distribution protocol(s)          used by this LSR. Note that an LSR may support more          than one distribution protocol simultaneously."   ::= { mplsTeScalars 3 }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 }mplsTunnelNotificationMaxRate OBJECT-TYPE   SYNTAX       Unsigned32   MAX-ACCESS   read-write   STATUS       current   DESCRIPTION        "This variable indicates the maximum number of          notifications issued per second. 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 throttling is applied and events may be          notified at the rate at which they occur."   DEFVAL       { 0 }   ::= { mplsTeScalars 5 }-- End of MPLS Tunnel scalars.-- MPLS tunnel table.mplsTunnelIndexNext OBJECT-TYPE   SYNTAX        IndexIntegerNextFree (0..65535)   MAX-ACCESS    read-only   STATUS        current   DESCRIPTION       "This object contains an unused value for        mplsTunnelIndex, or a zero to indicate        that none exist. Negative values are not allowed,        as they do not correspond to valid values of        mplsTunnelIndex.        Note that this object offers an unused value        for an mplsTunnelIndex value at the ingress        side of a tunnel. At other LSRs the value        of mplsTunnelIndex SHOULD be taken from the        value signaled by the MPLS signaling protocol.       "   ::= { mplsTeObjects 1 }mplsTunnelTable OBJECT-TYPE   SYNTAX        SEQUENCE OF MplsTunnelEntry   MAX-ACCESS    not-accessible   STATUS        current   DESCRIPTION        "The mplsTunnelTable allows new MPLS tunnels to be          created between an LSR and a remote endpoint, and          existing tunnels to be reconfigured or removed.          Note that only point-to-point tunnel segments are          supported, although multipoint-to-point and point-          to-multipoint connections are supported by an LSR          acting as a cross-connect.  Each MPLS tunnel can          thus have one out-segment originating at this LSR          and/or one in-segment terminating at this LSR."   ::= { 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          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).        A tunnel entry needs to be uniquely identified across          a MPLS network. Indices mplsTunnelIndex and          mplsTunnelInstance uniquely identify a tunnel on          the LSR originating the tunnel.  To uniquely          identify a tunnel across an MPLS network requires          index mplsTunnelIngressLSRId.  The last index          mplsTunnelEgressLSRId is useful in identifying all          instances of a tunnel that terminate on the same          egress LSR."   REFERENCE        "1. RFC 2863 - The Interfaces Group MIB, McCloghrie,          K., and F. Kastenholtz, June 2000 "   INDEX {  mplsTunnelIndex,            mplsTunnelInstance,            mplsTunnelIngressLSRId,            mplsTunnelEgressLSRId         }   ::= { mplsTunnelTable 1 }MplsTunnelEntry ::= SEQUENCE {      mplsTunnelIndex              MplsTunnelIndex,      mplsTunnelInstance           MplsTunnelInstanceIndex,      mplsTunnelIngressLSRId       MplsExtendedTunnelId,      mplsTunnelEgressLSRId        MplsExtendedTunnelId,      mplsTunnelName               SnmpAdminString,      mplsTunnelDescr              SnmpAdminString,      mplsTunnelIsIf               TruthValue,      mplsTunnelIfIndex            InterfaceIndexOrZero,      mplsTunnelOwner              MplsOwner,      mplsTunnelRole               INTEGER,      mplsTunnelXCPointer          RowPointer,      mplsTunnelSignallingProto    INTEGER,      mplsTunnelSetupPrio          Integer32,      mplsTunnelHoldingPrio        Integer32,      mplsTunnelSessionAttributes  BITS,      mplsTunnelLocalProtectInUse  TruthValue,      mplsTunnelResourcePointer    RowPointer,      mplsTunnelPrimaryInstance    MplsTunnelInstanceIndex,      mplsTunnelInstancePriority   Unsigned32,      mplsTunnelHopTableIndex      MplsPathIndexOrZero,      mplsTunnelPathInUse          MplsPathIndexOrZero,      mplsTunnelARHopTableIndex    MplsPathIndexOrZero,      mplsTunnelCHopTableIndex     MplsPathIndexOrZero,      mplsTunnelIncludeAnyAffinity MplsTunnelAffinity,      mplsTunnelIncludeAllAffinity MplsTunnelAffinity,      mplsTunnelExcludeAnyAffinity MplsTunnelAffinity,      mplsTunnelTotalUpTime        TimeTicks,      mplsTunnelInstanceUpTime     TimeTicks,      mplsTunnelPrimaryUpTime      TimeTicks,      mplsTunnelPathChanges        Counter32,      mplsTunnelLastPathChange     TimeTicks,      mplsTunnelCreationTime       TimeStamp,      mplsTunnelStateTransitions   Counter32,      mplsTunnelAdminStatus        INTEGER,      mplsTunnelOperStatus         INTEGER,      mplsTunnelRowStatus          RowStatus,      mplsTunnelStorageType        StorageType   }mplsTunnelIndex OBJECT-TYPE   SYNTAX        MplsTunnelIndex   MAX-ACCESS    not-accessible   STATUS        current   DESCRIPTION        "Uniquely identifies a set of tunnel instances          between a pair of ingress and egress LSRs.          Managers should obtain new values for row          creation in this table by reading          mplsTunnelIndexNext. When          the MPLS signalling protocol is rsvp(2) this value          SHOULD be equal to the value signaled in the          Tunnel Id of the Session object. When the MPLS          signalling protocol is crldp(3) this value          SHOULD be equal to the value signaled in the          LSP ID."   ::= { mplsTunnelEntry 1 }mplsTunnelInstance OBJECT-TYPE   SYNTAX        MplsTunnelInstanceIndex   MAX-ACCESS    not-accessible   STATUS        current   DESCRIPTION        "Uniquely identifies a particular instance of a          tunnel between a pair of ingress and egress LSRs.          It is useful to identify multiple instances of          tunnels for the purposes of backup and parallel          tunnels. When the MPLS signaling protocol is          rsvp(2) this value SHOULD be equal to the LSP Id          of the Sender Template object. When the signaling          protocol is crldp(3) there is no equivalent          signaling object."   ::= { mplsTunnelEntry 2 }mplsTunnelIngressLSRId OBJECT-TYPE   SYNTAX        MplsExtendedTunnelId   MAX-ACCESS    not-accessible   STATUS        current   DESCRIPTION        "Identity of the ingress LSR associated with this          tunnel instance. When the MPLS signalling protocol          is rsvp(2) this value SHOULD be equal to the Tunnel          Sender Address in the Sender Template object and MAY          be equal to the Extended Tunnel Id field in the          SESSION object. When the MPLS signalling protocol is          crldp(3) this value SHOULD be equal to 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), RFC 3212, January 2002"   ::= { mplsTunnelEntry 3 }mplsTunnelEgressLSRId OBJECT-TYPE   SYNTAX        MplsExtendedTunnelId   MAX-ACCESS    not-accessible   STATUS        current   DESCRIPTION        "Identity of the egress LSR associated with this          tunnel instance."   ::= { mplsTunnelEntry 4 }mplsTunnelName OBJECT-TYPE   SYNTAX        SnmpAdminString   MAX-ACCESS    read-create   STATUS        current   DESCRIPTION        "The canonical name assigned to the tunnel. This name          can be used to refer to the tunnel on the LSR's          console port.  If mplsTunnelIsIf is set to true          then the ifName of the interface corresponding to          this tunnel should have a value equal to          mplsTunnelName.  Also see the description of ifName          in RFC 2863."   REFERENCE        "RFC 2863 - The Interfaces Group MIB, McCloghrie, K.,          and F. Kastenholtz, June 2000"   DEFVAL {""}   ::= { mplsTunnelEntry 5 }mplsTunnelDescr OBJECT-TYPE   SYNTAX        SnmpAdminString   MAX-ACCESS    read-create   STATUS        current   DESCRIPTION        "A textual string containing information about the          tunnel.  If there is no description this object          contains a zero length string. This object is may          not be signaled by MPLS signaling protocols,          consequentally the value of this object at transit          and egress LSRs MAY be automatically generated or          absent."   DEFVAL {""}