PRVT-MPLS-TE-MIB: View SNMP OID List / Download MIB

This MIB module contains managed object definitions for MPLS Traffic Engineering (TE) as defined in: Extensions to RSVP for LSP Tunnels, Awduche et al, Internet Draft , August 2000; Constraint-Based LSP Setup using LDP, B. Jamoussi, Internet Draft , July 2000; Requirements for Traffic Engineering Over MPLS, Awduche, D., J. Malcolm, J., Agogbua, J., O'Dell, M., J. McManus, , September 1999.

This table contains the next available values of mplsTunnelIndex for all entities.

An entry in this table represents the next available mplsTunnelIndex for a specific TE-MIB entity. This MIB table is indexed by the PRVT-TE-MIB entity Index.

This object contains the next appropriate value to be used for mplsTunnelIndex when creating entries in the mplsTunnelTable. If the number of unassigned entries is exhausted, this object will take on the value of 0. To obtain the mplsTunnelIndex value 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.

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 multi-point-to-point and point- to-multi-point 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. To configure tunnels where the ingress and egress routers are identified by IPv6 addresses, the following approach is used. - The mplsTunnelIngressLSRId and mplsTunnelEgressLSRId fields are set to 32-bit identifiers for the ingress and egress routers. - mplsTunnelHopTableIndex must be set to a non-zero value. - The first hop in the hop table for the tunnel path must be set to a global scope IPv6 address of the local router. - The last entry in the hop table must be set to a global scope IPv6 address of the egress router.

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 corresponding entry is created in ifTable as well (see RFC 2233). The ifType of this entry is mplsTunnel(150).

Uniquely identifies this row.

Uniquely identifies an instance of a tunnel. It is useful to identify multiple instances of tunnels for the purposes of backup and parallel tunnels.

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.

Identity of the egress LSR associated with this tunnel instance.

The canonical name assigned to the tunnel. This name can be used to refer to the tunnel on the LSRs 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.

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.

Denotes whether or not this tunnel corresponds to an interface represented in the interfaces group table. Note that if this variable 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 2233.

If mplsTunnelIsIf is set to true, then this value contains the LSR-assigned ifIndex which corresponds to an entry in the interfaces table. Otherwise this variable should contain the value of zero indicating that a valid ifIndex was not assigned to this tunnel interface.

Denotes the entity that created and is responsible for managing this tunnel. This column is automatically filled by the agent on creation of a row.

This value signifies the role that this tunnel entry/instance represents. This value MUST be set to head(1) at the originating point of the tunnel. This value MUST be set to transit(2) at transit points along the tunnel, if transit points are supported. This value MUST be set to tail(3) at the terminating point of the tunnel if tunnel tails are supported. The value headTail(4) is provided for tunnels that begin and end on the same LSR. Enumeration: 'head': 1, 'headTail': 4, 'tail': 3, 'transit': 2.

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. The array of longs specified here is configured as the OID array for the lmgr entity cross connect row. This consists of the length, family, lmgr entity index and row index values. Only the AMB_MPLS_XC_INDEX_IDX index is referenced by the TE-MIB.

The signalling protocol, if any, used to setup this tunnel. Enumeration: 'none': 1, 'other': 4, 'crldp': 3, 'rsvp': 2.

Indicates the setup priority of this tunnel.

Indicates the holding priority for this tunnel.

This bitmask indicates optional session values for this tunnel. The following describes these bit fields: fastReroute This flag indicates that 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 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. 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. recordRoute This flag indicates if the signaling protocol should remember the tunnel path after it has been signaled. -- recordLabels This flag indicates if the -- signaling protocol should record labels as well as -- the tunnel path. bandwidthProtect This flag indicates whether fast reroute bandwidth protection is desired. nodeProtect This flag indicates whether fast reroute node protection is desired. Bits: 'bandwidthProtect': 6, 'isPersistent': 2, 'isPinned': 3, 'nodeProtect': 7, 'fastReroute': 0, 'recordRoute': 4, 'mergingPermitted': 1, 'reserved5': 5.

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).

This variable represents a pointer to the traffic 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 LSP instance. 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 LSPs can indicate resource sharing. In this implementation of the mplsTunnelTable, the row must either be set to zeroDotZero, or must point at an entry in the mplsTunnelResourceTable. If a value other than zeroDotZero is used, then mplsTunnelExtraParamsPtr must be set to zeroDotZero.

Specifies the instance index of the primary instance of this tunnel.

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 LSPs with the same mplsTunnelIndex in this table, but with a different mplsTunnelInstance. Tunnel instance 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.

Index into the mplsTunnelHopTable entry that specifies the explicit route hops for this tunnel. This object is meaningful only at the head-end of the tunnel. For UNI tunnels, this field should be set to 0. For tunnels with no configured explicit route hops, this field should be set to 0. In this case, the tunnel is routed using mplsTunnelEgressLSRId.

This value denotes the configured path that was chosen for this tunnel. This value reflects the secondary index into mplsTunnelHopTable. This path may not exactly match the one in mplsTunnelARHopTable due to the fact that some CSPF modification may have taken place. See mplsTunnelARHopTable for the actual path being taken by the tunnel. A value of zero denotes that no path is currently in use or available. For UNI tunnels, this field should be set to 0. For tunnels with no configued explicit route hops, this field should be set to 0.

Index into the mplsTunnelARHopTable entry that specifies the actual hops traversed by the tunnel. This is automatically updated by the agent when the actual hops becomes available.

Index into the mplsTunnelCHopTable entry that specifies the computed hops traversed by the tunnel. This is automatically updated by the agent when computed hops become available or when computed hops get modified.

A link satisfies the include-any constraint if and only if the constraint is zero, or the link and the constraint have a resource class in common. The field is a bitmask. Every request does not overwrite the previous one. 0 value resets the field.

A link satisfies the include-all constraint if and only if the link contains all of the administrative groups specified in the constraint. The field is a bitmask. Every request does not overwrite the previous one. 0 value resets the field.

A link satisfies the exclude-any constraint if and only if the link contains none of the administrative groups specified in the constraint. The field is a bitmask. Every request does not overwrite the previous one. 0 value resets the field.

This value represents the aggregate up time for all instances of this tunnel, if available. If this value is unavailable, it MUST return a value of 0.

This value identifies the total time that this tunnel instance's operStatus has been Up(1).

Specifies the total time the primary instance of this tunnel has been active. The primary instance of this tunnel is defined in mplsTunnelPrimaryInstance.

Specifies the number of times the actual path for this tunnel instance has changed.

Specifies the time since the last change to the actual path for this tunnel instance.

Specifies the value of SysUpTime when the first instance of this tunnel came into existence. That is, when the value of mplsTunnelOperStatus was first set to up(1).

Specifies the number of times the state (mplsTunnelOperStatus) of this tunnel instance has changed.

Indicates the desired operational status of this tunnel. Enumeration: 'down': 2, 'testing': 3, 'up': 1.

Indicates the actual operational status of this tunnel, which is typically but not limited to, a function of the state of individual segments of this tunnel. Enumeration: 'dormant': 5, 'lowerLayerDown': 7, 'unknown': 4, 'testing': 3, 'up': 1, 'down': 2, 'notPresent': 6.

This variable is used to create, modify, and/or delete a row in this table. When a row in this table is in active(1) state, no objects in that row can be modified by the agent except mplsTunnelAdminStatus, mplsTunnelRowStatus and mplsTunnelStorageType.

The storage type for this tunnel entry. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.

Denotes whether or not this tunnel corresponds to an unnumbered interface represented in the interfaces group table. This object is only used if mplsTunnelIsIf is set to 'true'. If both this object and the mplsTunnelIsIf object are set to 'true', the originating LSR adds an LSP_TUNNEL_INTERFACE_ID object to the outgoing Path message. This object contains information that is only used by the terminating LSR.

This bitmask indicates optional parameters for this tunnel. These bits should be taken in addition to those defined in mplsTunnelSessionAttributes in order to determine the full set of options to be signaled (for example SESSION_ATTRIBUTES flags in RSVP-TE). The following describes these bitfields: labelRecordingDesired This flag indicates that label information should be included when doing a route record. This bit is not valid unless the recordRoute bit is set in the mplsTunnelSessionAttributes object. Bits: 'reserved4': 4, 'labelRecordingDesired': 5, 'reserved1': 1, 'reserved0': 0, 'reserved3': 3, 'reserved2': 2.

This object indicates the encoding of the LSP being requested. It is only required when a generalized label request will be used for this LSP. A value of 0 in this object indicates that a generalized label request will not be used to set up this LSP. If this object indicates Sonet / SDH LSP encoding, then the choice of QOS to use is controlled by the mplsTunnelResourcePointer object. If mplsTunnelResourcePointer is 0.0, then a Sonet/SDH QOS format is used, else an Intserv QOS is used. Enumeration: 'tunnelLspFiber': 9, 'tunnelLspDigitalWrapper': 7, 'tunnelLspAnsiEtsiPdh': 3, 'tunnelLspFiberChannel': 11, 'tunnelLspSdhSonet': 5, 'tunnelLspEthernet': 2, 'tunnelLspPacket': 1, 'tunnelLspLambda': 8, 'notInUse': 0.

Indicates the type of switching that should be performed on a particular link. This field is needed for links that advertise more than one type of switching capability. Values of this field are as in the Switching Capability field defined in rfc3471. It is only used when mplsTunnelLSPEncoding is non-zero.

This bitmask indicates the level of link protection required. A value of zero (no bits set) indicates that any protection may be used. The following describes these bitfields: extraTraffic Indicates that the LSP should use links that are protecting other (primary) traffic. Such LSPs may be preempted when the links carrying the (primary) traffic being protected fail. unprotected Indicates that the LSP should not use any link layer protection. shared Indicates that a shared link layer protection scheme, such as 1:N protection, should be used to support the LSP. dedicatedOneToOne Indicates that a dedicated link layer protection scheme, i.e., 1:1 protection, should be used to support the LSP. dedicatedOnePlusOne Indicates that a dedicated link layer protection scheme, i.e., 1+1 protection, should be used to support the LSP. enhanced Indicates that a protection scheme that is more reliable than Dedicated 1+1 should be used, e.g., 4 fiber BLSR/MS-SPRING. This object is only meaningful if mplsTunnelLSPEncoding is not set to 'tunnelLspNotGmpls'. Bits: 'dedicatedOneToOne': 3, 'unprotected': 1, 'enhanced': 5, 'shared': 2, 'dedicatedOnePlusOne': 4, 'extraTraffic': 0.

This object indicates the payload carried by the LSP.It is only required when GMPLS will be used for this LSP. Only valid if Generalized Label Request is in use as specified by mplsTunnelLSPEncodingType. This object is only meaningful if mplsTunnelLSPEncoding is not set to 0 Enumeration: 'posScrambling32CRC': 31, 'vcByteSyncDS2': 19, 'ether8023': 46, 'hdlc': 44, 'bitSyncE3': 8, 'vt': 26, 'vcAsyncE1': 20, 'byteSyncDS2': 12, 'byteSyncDS1': 18, 'byteSyncE3': 9, 'byteSyncE1': 14, 'unknown': 0, 'laps': 40, 'byteSync31DS0': 15, 'asyncDS1': 16, 'asyncDS3': 6, 'asyncDS2': 10, 'pos32CRC': 29, 'bitSyncDS2': 11, 'posScrambling16CRC': 30, 'ds1SFAsync': 22, 'bitSyncDS1': 17, 'dqdb': 42, 'ds3M23': 3, 'ds1SF': 1, 'ds1ESFAsync': 23, 'fiberch3': 43, 'digitalWrapper': 36, 'vcByteSyncE1': 21, 'ds3CbitAsync': 25, 'etsiPdh': 38, 'ds3M23Async': 24, 'pos16CRC': 28, 'sdh': 34, 'fddi': 41, 'asyncE4': 5, 'ansiPdh': 39, 'asyncE1': 13, 'asyncE3': 7, 'ds1ESF': 2, 'sonet': 35, 'etherV2di': 45, 'ds3Cbit': 4, 'sts': 27, 'atmMapping': 32, 'ethernet': 33, 'etherGfpSonet': 56, 'lambda': 37.

Indicates that the requested LSP is a secondary LSP. This is a GMPLS feature, and should only be used when GMPLS will be be used for this LSP. This object is only meaningful if mplsTunnelLSPEncoding is not set to 0.

Whether this tunnel is unidirectional-incoming, unidirectional-outgoing, bidirectional in hardware, the terminator end of a signalled bidirectional tunnel, the initiator end of a signalled bidirectional tunnel, unidirectional at transit, signalled bidirectional at transit, or bidirectional in hardware at transit. Values of this object other than 'out' are meaningful only if mplsTunnelLSPEncoding is not set to 0. Enumeration: 'transbih': 7, 'transbi': 6, 'hwbidir': 3, 'outbidir': 1, 'inbidir': 4, 'transuni': 5, 'in': 2, 'out': 0.

This value instructs the source node on how to perform path computation on the explicit route specified by the associated entries in the mplsTunnelHopTable. dynamicFull The user specifies at least the source and destination of the path and expects that the CSPF will calculate the remainder of the path. explicit The user specifies the entire path for the tunnel to take. This path may contain strict or loose hops. Evaluation of the explicit route will be performed hop by hop through the network. dynamicPartial The user specifies at least the source and destination of the path and expects that the CSPF will calculate the remainder of the path. The path computed by CSPF is allowed to be only partially computed allowing the remainder of the path to be filled in across the network. This object deprecates mplsTunnelHopEntryPathComp. Enumeration: 'explicit': 2, 'dynamicFull': 1, 'dynamicPartial': 3.

Indicates the address of the upstream recipient for Notify messages relating to this tunnel. This object is only valid when signaling a tunnel using RSVP. It is also not valid at the tail end of the tunnel. If set to 0, no Notify Request object will be included in outgoing Path messages.

Indicates the address of the downstream recipient for Notify messages relating to this tunnel. This object is only valid when signaling a tunnel using RSVP. It is also not valid at the head end of the tunnel. If set to 0, no Notify Request object will be included in outgoing Resv messages.

Determines the setting of the Admin Status flags in the Admin Status object or TLV, as described in RFC 3471. Setting this field to a non-zero value will result in the inclusion of the admin status object on signaling messages. If the prvtMplsTeMibAllowGracefulDeletion product MIB field is set, then the delInProgress flag is not writable. Instead, Use the deletion_mode setting to indicate whether Graceful deletion should be used for the tunnel. This value of this object can be modified when the corresponding mplsTunnelRowStatus and mplsTunnelAdminStatus is active(1). By doing so, a new signaling message will be triggered including the requested Admin Status object or TLV. Bits: 'testing': 2, 'reserved9': 9, 'reserved8': 8, 'reserved5': 5, 'reserved4': 4, 'reserved7': 7, 'reserved6': 6, 'reserved3': 3, 'delInProgress': 0, 'reserved30': 30, 'reserved15': 15, 'reserved14': 14, 'reserved17': 17, 'reserved16': 16, 'reserved11': 11, 'reserved10': 10, 'reserved13': 13, 'reserved12': 12, 'reserved19': 19, 'reserved18': 18, 'reflect': 31, 'adminDown': 1, 'reserved28': 28, 'reserved29': 29, 'reserved20': 20, 'reserved21': 21, 'reserved22': 22, 'reserved23': 23, 'reserved24': 24, 'reserved25': 25, 'reserved26': 26, 'reserved27': 27.

Some Tunnels will run over transports that can usefully support technology-specific additional parameters (for example, SONET resource usage). Such parameters can be supplied in an external table and referenced from here. In this implementation of the mplsTunnelTable, the row must either be set to zeroDotZero, or must point at an entry in the mplsTunnelSonetResTable. If a value other than zeroDotZero is used, then mplsTunnelResourcePointer must be set to zeroDotZero.

Whether or not to use an explicit route Label subobject as configured in mplsTunnelEgressLabel.

The egress control Label in the explicit route, and its length. At ingress, this value must be inserted as the last hop of the explicit route. At egress this is the value of the received Label subobject. Since 0 is a valid value, the validity of this field is indicated by mplsTunnelUseEgressLabel. When this label is used in signaling protocol messages, it is copied byte for byte as is. Therefore, if the label octet string is intended to represent multibyte values, it should encode those values in network (big-endian) byte order. This interpretation applies in particular to the non-generalized MPLS labels (32 bits) used in ATM, FR and generic MPLS networks.

The C-Type of the egress control Label configured in mplsTunnelEgressLabel.

Indicates whether the explicit route object should be omitted from the Path message when the tunnel consists of just one loose hop. Note that if mplsTunnelHopTableIndex is set to 0, the tunnel is routed to the address configured in mplsTunnelEgressLSRId. This avoids the need to configure a single loose hop containing the tunnel's destination address and setting this field to true.

This object contains the customer defined private data for the forward signaling direction. At ingress it is filled in with the private data present on the MIB SET message. Note that this field can be updated even when the Tunnel is OperUp. At egress it is filled in with the decoded forward private data. Note that there is a separate MIB field for the reverse signaling direction private data, mplsTunnelReversePrivateData.

Type of the source TNA address of this tunnel. This field is used for UNI. For standard MPLS and GMPLS, this field must be set to none. Enumeration: 'nsap': 3, 'ipv6': 2, 'none': 0, 'ipv4': 1.

Source TNA address of this tunnel. This field is only valid if mplsTunnelSrcTNAAddressType is not none.

Type of the destination TNA address of this tunnel. This field is used for UNI. For standard MPLS and GMPLS, this field must be set to none. Enumeration: 'nsap': 3, 'ipv6': 2, 'none': 0, 'ipv4': 1.

Destination TNA address of this tunnel. This field is only valid if mplsTunnelDestTNAAddressType is not none.

Indicates that Crankback End to End rerouting should be enabled on this LSP. Setting this flag will cause Rerouting information to be returned to the ingress node on PathErrs and Notifications. No Rerouting information will be included if the Path Message does not contain an ERO. Rerouting information will be limited to 'Node' errors unless a switch managed label space is used.

This flag indicates whether the tunnel is to conform to UNI 1.0.

Indicates the UNI service level. It is only valid when _is_uni_ is set to true.

The label to be used at the destination UNI in the forward direction. This field is only valid if one of mplsTunnelIsUni or mplsTunnelIsSpc is set, and must be filled in if mplsTunnelIsSpc is set.

The C-Type of the forward label to be used at the destination UNI. This field is only valid if one of mplsTunnelIsUni or mplsTunnelIsSpc is set, and must be filled in if mplsTunnelIsSpc is set.

The logical port identifier used to uniquely identify and select a (forward) data link at the destination UNI. This port identifier is relative to the destination UNI-C for UNI-initiated connections, but is relative to the destination UNI-N for connections that are initiated by management at the source UNI-N. This field is only valid if one of mplsTunnelIsUni or mplsTunnelIsSpc is set, and must be filled in if mplsTunnelIsSpc is set.

The label to be used at the destination UNI in the reverse direction. This field is only valid if one of mplsTunnelIsUni or mplsTunnelIsSpc is set, and must be filled in if mplsTunnelIsSpc is set and the tunnel is bi-directional.

The C-Type of the reverse label to be used at the destination UNI. This field is only valid if one of mplsTunnelIsUni or mplsTunnelIsSpc is set, and must be filled in if mplsTunnelIsSpc is set and the tunnel is bi-directional.

The logical port identifier used to uniquely identify and select a (reverse) data link at the destination UNI. This port identifier is relative to the destination UNI-C for UNI-initiated connections, but is relative to the destination UNI-N for connections that are initiated by management at the source UNI-N. This field is only valid if one of mplsTunnelIsUni or mplsTunnelIsSpc is set, and must be filled in if mplsTunnelIsSpc is set and the tunnel is bi-directional.

Whether to use forced or graceful deletion to delete this LSP. This field is ignored if graceful deletion is not allowed in the TE-MIB entity MIB. Enumeration: 'forced': 1, 'graceful': 2.

UNI specific. This field references a prvtMplsTunnelUNIDivListIndex in the mplsTunnelUNIDiversityTable, and defines this list of tunnels to be diverse from. A value of zero indicates that no diversity is configured. Note that if the diversity requirements specified in the referenced diversity list cannot be satisfied by signaling, this tunnel will fail to move to oper_status up. See the Description in the mplsTunnelUNIDiversityTable for more information.

Index into the mplsDiffServTable entry that specifies the L-LSP or E-LSP parameters to signal when setting up the tunnel. If this field is not filled in or is assigned the value zero then no DiffServ parameters are signalled.

This object contains the customer defined private data for the reverse signaling direction. At egress it is initially set by the RRR_EGRESS_TRANSLATE_PRIV_DATA user exit and subsequently may be altered via MIB operations. At ingress it is filled in with the decoded reverse private data. Note that there is a separate MIB field for the forward signaling direction private data, mplsTunnelPrivateData.

Indicates whether or not this tunnel should be protected by a fast reroute mechanism, and if so which method should be used. noFastReroute - no fast reroute protection. detourFastReroute - fast reroute protection using the one-to-one detour backup method. facilityFastReroute - fast reroute protection using the facility backup method. Fast reroute is only available for uni-directional LSPs. Enumeration: 'detourFastReroute': 1, 'noFastReroute': 0, 'facilityFastReroute': 2.

Setup priority for backup tunnels set up to protect this tunnel. This field is only valid if the mplsTunnelFastRerouteMode above is not noFastReroute.

Holding priority for backup tunnels set up to protect this tunnel. This field is only valid if the mplsTunnelFastRerouteMode above is not noFastReroute.

Include-any resource affinity for backup tunnels set up to protect this tunnel. A link satisfies the include-any constraint if and only if the constraint is zero, or the link and the constraint have a resource class in common. This field is only valid if the mplsTunnelFastRerouteMode above is not noFastReroute.

Include-all resource affinity for backup tunnels set up to protect this tunnel. A link satisfies the include-all constraint if and only if the link contains all of the adminstrative groups specified in the constraint. This field is only valid if the mplsTunnelFastRerouteMode above is not noFastReroute.

Exclude-any resource affinity for backup tunnels set up to protect this tunnel. A link satisfies the exclude-any constraint if and only if the constraint is zero, or the link and the constraint have a resource class in common. This field is only valid if the mplsTunnelFastRerouteMode above is not noFastReroute.

The estimated bandwidth required for backup tunnels, in units of 1000 bits/second. A value of zero indicates best-effort. This field is only valid if the mplsTunnelFastRerouteMode above is not noFastReroute.

The maximum number of extra hops the backup path is allowed to take, from a Point of Local Repair (PLR) to a Merge Point (MP), with PLR and MP excluded in counting. A hop-limit of 0 means only direct links between PLR and MP can be used. This field is only valid if the mplsTunnelFastRerouteMode above is not noFastReroute.

This flag indicates whether the tunnel is an OIF soft permanent connection (SPC).

The label to be used for the in-segment at the source UNI-N in the forward direction. This field is only valid if the mplsTunnelIsSpc field is true.

The C-Type of the forward label to be used for the in-segment at the source UNI-N. This field is only valid if the mplsTunnelIsSpc field is true.

The logical port identifier used to uniquely identify and select a (forward) data link for the in-segment at the source UNI-N. This field is only valid if the mplsTunnelIsSpc field is true.

The label to be used at the source UNI-N for the out-segment in the reverse direction. This field is only valid if the mplsTunnelIsSpc field is true.

The C-Type of the reverse label to be used for the out-segment at the source UNI-N. This field is only valid if the mplsTunnelIsSpc field is true.

The logical port identifier used to uniquely identify and select a data link for the reverse out-segment at the source UNI-N. This field is only valid if the mplsTunnelIsSpc field is true.

DiffServ Class-Type of the LSP as defined in draft-ietf-tewg-diff-te-proto-03.

Indicates that the requested LSP should use the extended PROTECTION object as defined in draft-lang-ccamp-gmpls-recovery-e2e-signaling. This is a GMPLS feature, and should only be used when GMPLS will be used for this LSP.

Indicates that the requested LSP is a protecting LSP and not a working LSP. This field is only valid if mplsTunnelExtendedProtection is true.

Indicates that the control plane message exchange is only used for notification during protection switching. This field is only valid if mplsTunnelExtendedProtection is true.

This field indicates the level of end-to-end protection for this LSP. This field is only valid if mplsTunnelExtendedProtection is true. A value of zero indicates that no protection is provided for the tunnel. This field is not a bitmask; only one LSP protection may be selected. See draft-lang-ccamp-gmpls-recovery-e2e-signaling for a description of the possible values.

The mplsTunnelInstance of an associated tunnel between the same ingress and egress and with the same mplsTunnelIndex. If this field is zero, the associated LSP ID is not known, or there are multiple. This field is only valid if mplsTunnelExtendedProtection is true.

The C-Type of the following CALL ID. This field is insignificant if the mplsTunnelCallId has zero length. This field can only be changed when the Admin Status is down. Enumeration: 'operatorSpecific': 1, 'globallyUnique': 2.

The CALL ID to be used on this tunnel, including the address type, International and National segment (if applicable), source transport network element address, and Local Identifier as defined in G.7713.2 (version 0.8). This field can only be changed when the Admin Status is down.

Flag indicating whether this tunnel uses IPv6 addresses. If this flag is set, the tunnel may only be activated if - TE-MIB is configured to allow IPv6 tunnels - the hop path index is non-zero - all hops in the hop path have IPv6 addresses - the first and last hops in the hop path have global scope addresses.

Type of upstream notify recipient address for this tunnel.

Type of downstream notify recipient address for this tunnel.

Maximal transfer unit of the tunnel

Defines a period in minutes (0..1440), after which the tunnel will be unconditionally rebuild. The maximal valid value is 1440 minutes (24 hours)

Flags to extend the information of the tunnel state For the behaviour - bits meaning: tunnelResignalling (1) - This status shows that currently the tunnel has been resignalled. The resignalling state of a tunnel should be considered together with the mplsTunnelOperStatus attribute value of the same tunnel. tunnelSuppressed (2) - This status shows that the tunnel has been established, but higher priority tunnel is active and in use. This tunnel can be activated, once the higher protocol tunnel fails by any reason, and in this case the tunnelSuppressed status will be cleared. Bits: 'tunnelSuppressed': 2, 'empty': 0, 'tunnelResignalling': 1.

The guarded destination object specifies which IP destination address the current tunnel protects used with the fast reroute feature. The tunnel must not be fast reroute enabled.

Specifies the timer configuration (in minutes) for Make-before-break (MBB). The default value of this object is 10 minutes.

This table contains the next available values of mplsTunnelHopIndex for all entities.

An entry in this table represents the next available mplsTunnelHopIndex for a specific TE-MIB entity. This MIB table is indexed by the PRVT-TE-MIB entity Index.

This object contains an appropriate value to be used for mplsTunnelHopListIndex when creating entries in the mplsTunnelHopTable. 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 mplsTunnelHopTable is implemented as read-only. To obtain the value of mplsTunnelHopListIndex for a new entry in the mplsTunnelHopTable, the manager issues a management protocol retrieval operation to obtain the current value of mplsTunnelHopIndex. After each retrieval operation, the agent should modify the value to reflect the next unassigned index. After a manager retrieves a value the agent will determine through its local policy when this index value will be made available for reuse.

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 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.

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 protocol.

Primary index into this table identifying a particular explicit route object.

Secondary index into this table identifying a particular group of hops representing a particular configured path. This is otherwise known as a path option.

Secondary index into this table identifying a particular hop.

The Hop Address Type of this tunnel hop. The value of this object cannot be changed if the value of the corresponding mplsTunnelHopRowStatus object is 'active'. Note that lspid(5) is a valid option only for tunnels signaled via CRLDP.

The Tunnel Hop Address for this tunnel hop. The type of this address is determined by the value of the corresponding mplsTunnelHopAddrType. The value of this object cannot be changed if the value of the corresponding mplsTunnelHopRowStatus object is 'active'.

If mplsTunnelHopAddrType is set to ipv4(1) or ipv6(2), then this value will contain an appropriate prefix length for the IP address in object mplsTunnelHopIpAddr. Otherwise this value is irrelevant and should be ignored.

If mplsTunnelHopAddrType is set to asnumber(3), then this value will contain the AS number of this hop. Otherwise the agent should set this object to zero- length string and the manager should ignore this.

If mplsTunnelHopAddrType is set to unnum(4) or unnumv6(6), then this value will contain the interface identifier of the unnumbered interface for this hop. This object should be used in conjunction with mplsTunnelHopIpAddress which would contain the LSR Router ID in this case. Otherwise the agent should set this object to zero-length string and the manager should ignore this.

If mplsTunnelHopAddrType is set to lspid(5), 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.

Denotes whether this tunnel hop is routed in a strict or loose fashion. The value of this object has no meaning if the mplsTunnelHopInclude object is set to 'false'. Enumeration: 'strict': 1, 'loose': 2.

If this value is set to true, then this indicates that this hop must be included in the tunnel's path. If this value is set to 'false', then this hop must be avoided when calculating the path for this tunnel. The default value of this object is 'true', so that by default all indicated hops are included in the CSPF path computation. If this object is set to 'false' the value of mplsTunnelHopType should be ignored.

The description of this series of hops as they relate to the specified path option. The value of this object SHOULD be the same for each hop in the series that comprises a path option.

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. Enumeration: 'dynamic': 1, 'explicit': 2.

This variable is used to create, modify, and/or delete a row in this table. When a row in this table is in active(1) state, no objects in that row can be modified by the agent except mplsTunnelHopRowStatus and mplsTunnelHopStorageType.

The storage type for this Hop entry. Conceptual rows having the value 'permanent' need not allow write-access to any columnar objects in the row.

This bitmask indicates the presence of labels indicated by the mplsTunnelHopExpLabel and mplsTunnelHopExpRvrsLabel objects. For the Present bits, a set bit indicates that a label is present for this hop in the route. This allows zero to be a valid label value. Bits: 'forwardPresent': 0, 'reversePresent': 1.

Denotes the type of the label configured in mplsTunnelHopExpLabel.

If mplsTunnelHopLabelStatuses object indicates that a forward label is present then the label to use on this hop is found in this object.

Denotes the type of the label configured in mplsTunnelHopExpRvrsLabel.

If the mplsTunnelHopLabelStatuses object indicates that a reverse label is present then the label to use on this hop is found in this object.

This table contains the next available values of mplsTunnelResourceIndex for all entities.

An entry in this table represents the next available mplsTunnelResourceIndex for a specific TE-MIB entity. This MIB table is indexed by the PRVT-TE-MIB entity Index.

This object contains the next appropriate value to be used for mplsTunnelResourceIndex when creating entries in the mplsTunnelResourceTable. 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 mplsTunnelResourceIndex value 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.

The mplsTunnelResourceTable allows a manager to specify which resources are desired for an MPLS tunnel. This table also allows several tunnels to point to a single entry in this table, implying that these tunnels should share resources.

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.

Uniquely identifies this row.

The maximum rate in units of 1000 bits/second. Note that setting 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. If the ingress node sets a maximum rate of positive infinity, the egress node will return a value of positive infinity on the MIB GET response. This special value may not be used when setting the maximum rate with this MIB.

The mean rate in units of 1000 bits/second. 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.

The maximum burst size in bytes. This object is copied to mplsInSegmentMaxBurstSize of the corresponding in-segment. 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.

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.

The Excess burst size in bytes. The implementations which do not implement this variable must return noSuchObject(0) exception for this object and must not allow a user to set this value.

The granularity of the availability of committed rate. The implementations which do not implement this variable must return unspecified(1) for this value and must not allow a user to set this value. Enumeration: 'unspecified': 1, 'frequent': 2, 'veryFrequent': 3.

The relative weight for using excess bandwidth above its committed rate. The value of 0 means that weight is not applicable for the CR-LSP.

This variable is used to create, modify, and/or delete a row in this table.

This variable indicates the storage type for this object.

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 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 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.

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 protocol.

Primary index into this table identifying a particular recorded hop list.

Secondary index into this table identifying the particular hop.

The Hop Address Type of this tunnel hop. If the type value is set to ipv4(1) or ipv6(2). The tunnel path can be determin using mplsTunnelARHopIpAddr object. mplsTunnelARHopAddrUnnum and mplsTunnelARHopLspId should not be used. If the type value is set to unnum(4) or unnumv6(6). The tunnel path can be determin using mplsTunnelARHopAddrUnnum object. mplsTunnelARHopIpAddr and mplsTunnelARHopLspId should not be used. Note that lspid(5) is a valid option only for tunnels signaled via CRLDP. The tunnel path can be determin using mplsTunnelARHopLspId object. mplsTunnelARHopIpAddr and mplsTunnelARHopAddrUnnum should not be used. Currently only ipv4(1) type is supported

The Tunnel Hop Address for this tunnel hop. The type of this address is determined by the value of the corresponding mplsTunnelARHopAddrType. If mplsTunnelARHopAddrType is set to ipv4(1) or ipv6(2), then this value contains the LSR Router ID of the unnumbered interface. Otherwise the agent SHOULD set this object to the zero-length string and the manager should ignore this object.

If mplsTunnelARHopAddrType is set to unnum(4) or unnumv6(6), then this value will contain the interface identifier of the unnumbered interface for this hop. This object should be used in conjunction with mplsTunnelARHopIpAddr which would contain the LSR Router ID in this case. Otherwise the agent should set this object to zero-length string and the manager should ignore this.

If mplsTunnelARHopAddrType is set to lspid(5), 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.

This bitmask indicates the presence and status of labels indicated by the mplsTunnelARHopExpLabel and mplsTunnelARHopExpRvrsLabel objects. For the Present bits, a set bit indicates that a label is present for this hop in the route. For the Global bits, a set bit indicates that the label comes from the Global Label Space. A clear bit indicates that this is a Per- Interface label. A Global bit only has meaning if the corresponding Present bit is set. Bits: 'forwardPresent': 0, 'reversePresent': 1, 'reverseGlobal': 3, 'forwardGlobal': 2.

The C-Type of the following hop label. This field is insignificant unless mplsTunnelARHopLabelStatuses has the forwardPresent(0) or forwardGlobal(2) bits set.

If mplsTunnelARHopLabelStatus has the present(0) bit set, then this value indicates the label value used for this hop. This object is otherwise insignificant and should contain a value of 0. When this label is read from a signaling protocol message, it is copied byte for byte as is. Therefore, if the label octet string is understood to represent multibyte values, it encodes those values in network (big-endian) byte order. This interpretation applies in particular to the non-generalized MPLS labels (32 bits) used in ATM, FR and generic MPLS networks.

The C-Type of the following hop label. This field is insignificant unless mplsTunnelARHopLabelStatuses has the reversePresent(1) or reverseGlobal(3) bits set.

If the mplsTunnelARHopLabelStatuses object indicates that a reverse label is present then the label in use on this hop is found in this object.

Availability and usage of protection on the reported link. localAvailable Indicates that the link downstream of this node is protected via a local repair mechanism. localInUse Indicates that a 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). Bits: 'localAvailable': 0, 'localInUse': 1.

The mplsTunnelCHopTable is used to indicate the hops, strict or loose, for an MPLS tunnel defined in mplsTunnelTable, as computed by a constraint- based routing protocol, based on the mplsTunnelHopTable for the outgoing direction of the tunnel. Each row in this table is indexed by mplsTunnelCHopListIndex. Each row also has a secondary index mplsTunnelCHopIndex, 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 mplsTunnelCHopTable. Please note that since the information necessary to build entries within this table may not be supported by some LSRs, implementation of this table is optional. Furthermore, since the information in this table is actually provided by routing protocol after the path has been computed, the entries in this table are provided only for observation, and hence, all variables in this table are accessible exclusively as read-only.

An entry in this table represents a tunnel hop. An entry in this table is created by a constraint- based routing protocol based on the hops specified in the corresponding mplsTunnelHopTable.

Primary index into this table identifying a particular computed hop list.

Secondary index into this table identifying the particular hop.

The Hop Address Type of this tunnel hop. Note that lspid(5) is a valid option only for tunnels signaled via CRLDP.

The Tunnel Hop Address for this tunnel hop. The type of this address is determined by the value of the corresponding mplsTunnelCHopAddrType. If mplsTunnelCHopAddrType is set to unnum(4) or unnumv6(6), then this value will contain the LSR Router ID of the unnumbered interface. Otherwise the agent should set this object to the zero-length string and the manager SHOULD ignore this object.

If mplsTunnelCHopAddrType is set to ipv4(1) or ipv6(2), then this value will contain an appropriate prefix length for the IP address in object mplsTunnelCHopIpAddr. Otherwise this value is irrelevant and should be ignored.

If mplsTunnelCHopAddrType is set to asnumber(3), then this value will contain the AS number of this hop. Otherwise the agent should set this object to zero-length string and the manager should ignore this.

If mplsTunnelCHopAddrType is set to unnum(4) or unnumv6(6), then this value will contain the unnumbered interface identifier of this hop. This object should be used in conjunction with mplsTunnelCHopIpAddr which would contain the LSR Router ID in this case. Otherwise the agent should set this object to zero- length string and the manager should ignore this.

If mplsTunnelCHopAddrType is set to lspid(5), 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.

Denotes whether this is tunnel hop is routed in a strict or loose fashion. Enumeration: 'strict': 1, 'loose': 2.

This bitmask indicates the presence of labels indicated by the mplsTunnelCHopExpLabel and mplsTunnelCHopExpRvrsLabel objects. A set bit indicates that a label is present for this hop in the route thus allowing zero to be a valid label value. Bits: 'forwardPresent': 0, 'reversePresent': 1.

The C-Type of the following hop label. This field is insignificant unless mplsTunnelCHopLabelStatuses has the forwardPresent(0) bit set.

The explicit out-segment label to use on the forward path. When this label is used in signaling protocol messages, it is copied byte for byte as is. Therefore, if the label octet string is intended to represent multibyte values, it should encode those values in network (big-endian) byte order. This interpretation applies in particular to the non-generalized MPLS labels (32 bits) used in ATM, FR and generic MPLS networks.

The C-Type of the following hop label. This field is insignificant unless mplsTunnelCHopLabelStatuses has the reversePresent(0) bit set.

The explicit in-segment label to use on the reverse path. When this label is used in signaling protocol messages, it is copied byte for byte as is. Therefore, if the label octet string is intended to represent multibyte values, it should encode those values in network (big-endian) byte order. This interpretation applies in particular to the non-generalized MPLS labels (32 bits) used in ATM, FR and generic MPLS networks.

This table provides per-tunnel MPLS performance information.

An entry in this table is created by the LSR for every tunnel. Its is an extension to mplsTunnelEntry.

Number of packets forwarded by the tunnel.

High capacity counter for number of packets forwarded by the tunnel.

Number of errored packets.

Number of bytes forwarded by the tunnel.

High capacity counter for number of bytes forwarded by the tunnel.

The mplsTunnelCRLDPResTable allows a manager to specify which CR-LDP-specific resources are desired for an MPLS tunnel if that tunnel is signaled using CR-LDP. Note that these attributes are in addition to those specified in mplsTunnelResourceTable. This table also allows several tunnels to point to a single entry in this table, implying that these tunnels should share resources.

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.

The mean burst size in bytes.

The Excess burst size in bytes.

The granularity of the availability of committed rate. Enumeration: 'unspecified': 1, 'frequent': 2, 'veryFrequent': 3.

The relative weight for using excess bandwidth above its committed rate. The value of 0 means that weight is not applicable for the CR-LSP.

The value of the 1 byte Flags conveyed as part of the traffic parameters during the establishment of the CRLSP. The bits in this object are to be interpreted as follows. +==+==+==+==+==+==+==+==+ | Res |F6|F5|F4|F3|F2|F1| +==+==+==+==+==+==+==+==+ Res - These bits are reserved. Zero on transmission. Ignored on receipt. F1 - Corresponds to the PDR. F2 - Corresponds to the PBS. F3 - Corresponds to the CDR. 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.

This variable is used to create, modify, and/or delete a row in this table.

This variable indicates the storage type for this object.

This table contains the next available values of mplsDiffServIndex for all entities.

An entry in this table represents the next available mplsDiffServIndex for a specific TE-MIB entity. This MIB table is indexed by the PRVT-TE-MIB entity Index.

This object contains the next appropriate value to be used for mplsDiffServIndex when creating entries in the mplsDiffServTable. If the number of unassigned entries is exhausted, this object will take on the value of 0. To obtain the mplsDiffServIndex value 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.

The mplsDiffServTable allows DiffServ parameters to be configured for DiffServ enabled LSPs signalled by the mplsTunnelTable. If a tunnel is an E-LSP, then fields in this table must be set to indicate 0 - 8 EXP->PHB maps, and the number of such maps, to be used by LSRs in the E-LSP to determine the PHB to apply to incoming packets. If a tunnel is an L-LSP, then fields in this table must be set to indicate the PHB Scheduling Class (PSC) to use for incoming packets.

An entry in this table represents either a set of 0 - 8 EXP->PHB maps, and the number of such maps, for an E-LSP or a PSC value for an L-LSP.

Uniquely identifies this row.

This field must be set to indicate whether this row contains parameters for an E-LSP or an L-LSP. Enumeration: 'elsp': 0, 'llsp': 1.

Valid only when mplsDiffServType takes the value l-lsp (1), this field contains the16-bit encoding of the PHB Scheduling Class (PSC) to be used for packets on this LSP (RFC 3140).

Valid only when mplsDiffServType takes the value e-lsp (0), this value indicates the number of EXP->PHB maps defined in this row.

Valid only when mplsDiffServType takes the value e-lsp (0), this field contains the 16-bit encoding of the PHB (RFC 3140) which is assigned to packets on this LSP with the value 0 in the EXP field of their MPLS shim header.

Valid only when mplsDiffServType takes the value e-lsp (0), this field contains the 16-bit encoding of the PHB (RFC 3140) which is assigned to packets on this LSP with the value 1 in the EXP field of their MPLS shim header.

Valid only when mplsDiffServType takes the value e-lsp (0), this field contains the 16-bit encoding of the PHB (RFC 3140) which is assigned to packets on this LSP with the value 2 in the EXP field of their MPLS shim header.

Valid only when mplsDiffServType takes the value e-lsp (0), this field contains the 16-bit encoding of the PHB (RFC 3140) which is assigned to packets on this LSP with the value 3 in the EXP field of their MPLS shim header.

Valid only when mplsDiffServType takes the value e-lsp (0), this field contains the 16-bit encoding of the PHB (RFC 3140) which is assigned to packets on this LSP with the value 4 in the EXP field of their MPLS shim header.

Valid only when mplsDiffServType takes the value e-lsp (0), this field contains the 16-bit encoding of the PHB (RFC 3140) which is assigned to packets on this LSP with the value 5 in the EXP field of their MPLS shim header.

Valid only when mplsDiffServType takes the value e-lsp (0), this field contains the 16-bit encoding of the PHB (RFC 3140) which is assigned to packets on this LSP with the value 6 in the EXP field of their MPLS shim header.

Valid only when mplsDiffServType takes the value e-lsp (0), this field contains the 16-bit encoding of the PHB (RFC 3140) which is assigned to packets on this LSP with the value 7 in the EXP field of their MPLS shim header.

This variable is used to create, modify, and/or delete a row in this table.

This table contains the next available values of prvtMplsTunnelUNIDivListIdx for all entities.

An entry in this table represents the next available prvtMplsTunnelUNIDivListIdx for a specific TE-MIB entity. This MIB table is indexed by the PRVT-TE-MIB entity Index.

This is the next available List Index in the prvtMplsTunnelUNIDiversityTable.

The prvtMplsTunnelUNIDiversityTable is used to indicate which existing tunnels a new UNI Connection is to be diverse from. This table is UNI specific. Each prvtMplsTunnelUNIDiversityTable is indexed using prvtMplsTeMibEntityIndex, prvtMplsTunnelUNIDivListIdx, prvtMplsTunnelUNIDivTnnlIdx. To create a UNI tunnel to use Diversity, set up a row entry in the prvtMplsTunnelUNIDiversityTable for each existing tunnel that the new tunnel should be diverse from. Then when creating the new UNI tunnel, set prvtMplsTunnelUNIDiversityTableIndex in the mplsTunnelTable to the list_index corresponding to the Diversity Table to be used. A diversity list is read-only if it is referenced by an active row in the mplsTunnelTable that is admin_status up. Under these circumstances, no individual rows/diversity requirements making up the list can be added, modified or deleted. A list of diversity requirements can only be satisfied by signaling if all of the referenced rows in the mplsTunnelTable are oper_status up when signaling is initiated. If the requirements cannot be satisfied, any tunnel attempting to use the list will remain oper_status down.

An entry in this table corresponds to an entry in the mplsTunnelTable. A subsequent Tunnel that references this entry will be created Diverse from the tunnel row entry specified here.

Primary index into this table identifying a particular list of Diversity requirements.

Secondary index into this table identifying a Diversity requirement within the list.

This field represents a pointer to the entry in the mplsTunnelTable to which the Diversity requirement applies. The array of longs specified here is configured as the OID of the corresponding tunnel.

The Oper Status of the mplsTunnelTable row referred to by prvtMplsTunnelUNIDivPointer. If this tunnel is removed from the mplsTunnelTable then this is set to AMB_OPER_STATUS_DOWN. This field is used to determine whether a diversity requirement can currently be satisfied by signaling.

This variable is used to create or delete this row.

This field indicates the Diversity Requirement for the corresponding tunnel. Once an row entry has been created and is oper status 'up' for this tunnel this value cannot be altered. Enumeration: 'sharedPath': 4, 'nodeDiverse': 1, 'srlg': 3, 'linkDiverse': 2.

This field indicates the access (read-only or writable) that the user has over this row entry. The circumstances under which a row is read-only are described above.

The prvtMplsTunnelTrapEnable Table allows a manager to enable or disable TRAPs.

An entry in this table is used to configure trap support for this instance of TE-MIB

If this object is true, then it enables the generation of mplsTunnelUp and mplsTunnelDown traps, otherwise these traps are not emitted.

The mplsTeMibEntityScalarTable contains all MPLS Tunnel scalars.

The mplsTeMibEntityScalarTable contains all MPLS Tunnel scalars.

The number of tunnels configured on this device. A tunnel is considered configured if the mplsTunnelRowStatus is active(1).

The number of tunnels active on this device. A tunnel is considered active if the mplsTunnelOperStatus is up(1).

The traffic engineering distribution protocol(s) used by this LSR. Note that an LSR may support more than one distribution protocol simultaneously. Bits: 'isis': 2, 'other': 0, 'ospf': 1.

The maximum number of hops that can be specified for a tunnel on this device.

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.

The mplsTunnelSonetResTable allows a manager to specify which Sonet-specific resources are desired for an MPLS tunnel. Note that these attributes are in addition to those specified in mplsTunnelResourceTable. This table also allows several tunnels to point to a single entry in this table, implying that these tunnels should share resources.

An entry in this table represents a set of Sonet 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.

Requested Contiguous Concatenation. Indicates the types of contiguous concatenation requested for this LSP. This field is only valid if is SDH or SONET, and the is 0.0.

Requested Number of Contiguous Components. Indicates the number of identical SDH/SONET SPEs/VCs that are requested to be concatenated, as indicated in the field. This field is only valid if is SDH or SONET, and the is 0.0.

This field indicates the number of signals that are requested to be virtually concatenated. These signals are all of the same type. This field is valid only if is SDH or SONET, and the is 0.0.

This field is a bit field indicating the number of identical signals that are requested for the LSP. This field is valid only if is SDH or SONET, and the is 0.0.

This field is a bit field indicating the type of Transparency being requested. Several flags can be combined to provide different types of transparency. Not all combinations are necessarily valid. This field is valid only if is SDH or SONET, and the is 0.0.

This variable is used to create, modify, and/or delete a row in this table.

Indicates the overhead termination type and is interpreted in relation to the LSP Encoding Type.

This table 'augments' the mplsTunnelTable. This table provides per-tunnel information about errors. Errors may be detected locally or reported through the signaling protocol. Error reporting is not exclusive to GMPLS and this table may be applied in MPLS systems.

An entry in this table is created by the LSR for every tunnel where error information is visible to the LSR. Note that systems which read the objects in this table one at a time may experience a discontinuity as the result of a new error occurring in between object reads. Systems that are vulnerable to this should read mplsTunnelErrorLastTime before and after reading the other objects.

The nature of the last error. Provides interpretation context for mplsTunnelErrorProtocolCode and mplsTunnelErrorProtocolSubcode. A value of noError (0) shows that there is no error associated with this tunnel and means that the other objects in this table entry have no meaning. A value of unknown (1) shows that there is an error but that no additional information about the cause is known. The error may have been received in a signaled message or generated locally. A value of protocol (2) or pathComputation (3) indicates that the cause of an error and identifies an error that has been received through signaling or will itself be signaled. A value of localConfiguration (4), localResources (5) or localOther (6) identifies an error which has been detected by the local node, but which will not be reported through signaling. Enumeration: 'localConfiguration': 4, 'protocol': 2, 'unknown': 1, 'localResources': 5, 'noError': 0, 'pathComputation': 3, 'localOther': 6.

The time at which the last error occurred. This is presented as the value of SysUpTime when the error occurred or was reported to this node. If mplsTunnelErrorLastErrorType has the value noError (0), then this object is ignored.

The address type of the error reported. This object is used to aid in interpretation of mplsTunnelErrorReporter.

The address of the node reporting the last error, or the address of the resource (such as an interface) associated with the error. If mplsTunnelErrorLastErrorType has the value noError (0), then this object is ignored. If mplsTunnelErrorLastErrorType has the value unknown (1), localConfiguration (4), localResources (5), or localOther (6) this object MAY contain a zero value. This object should be interpreted in the context of the value of the object mplsTunnelErrorReporterType.

The primary error code associated with the last error. The interpretation of this error code depends on the value of mplsTunnelErrorLastErrorType. If the value of mplsTunnelErrorLastErrorType is noError (0) the value of this object should be 0 and should be ignored. If the value of mplsTunnelErrorLastErrorType is protocol (2) the error should be interpreted in the context of the signling protocol identified by the mplsTunnelSignallingProto object. Values in excess 32767 of are not used by signaling protocols and may safely be used as implementation-specific error codes.

The secondary error code associated with the last error and the protocol used to signal this tunnel. This value is interpreted in the context of the value of mplsTunnelErrorCode. If the value of mplsTunnelErrorLastErrorType is noError (0) the value of this object should be 0 and should be ignored.

The sequence of interface identifier TLVs reported with the error by the protocol code. The interpretation of the TLVs and the encoding within the protocol are described in the references. A value of zero in the first octet indicates that no TLVs are present.

A textual string containing information about the last error, recovery actions and support advice. If there is no help string this object contains a zero length string. If the value of mplsTunnelErrorLastErrorType is noError (0) this object should contain a zero length string, but may contain a help string indicating that there is no error.

Defines a period in seconds needed to wait before rebuilding backup or primary tunnels if a frr condition occurs Currently no more than 10 seconds are allowed

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. This structure is the same as the generic AMB_MPLS_TUNNEL_TRAP_COMMON.

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. This structure is the same as the generic AMB_MPLS_TUNNEL_TRAP_COMMON.

This notification is generated when a tunnel is rerouted. If the actual path is used, then this object MAY contain the new path for this tunnel some time after this trap is issued by the agent. This structure is the same as the generic AMB_MPLS_TUNNEL_TRAP_COMMON.

This notification is generated when a tunnel is reoptimized. If the mplsTunnelARHopTable is used, then this tunnel instance's entry in the mplsTunnelARHopTable MAY contain the new path for this tunnel some time after this trap is issued by the agent. This structure is the same as the generic AMB_MPLS_TUNNEL_TRAP_COMMON.

Necessary, but not sufficient, set of objects to implement tunnels. In addition, depending on the type of the tunnels supported (for example, manually configured or signaled, persistent or non- persistent, etc.), the following other groups defined below are mandatory: mplsTunnelManualGroup and/or mplsTunnelSignaledGroup, mplsTunnelIsNotIntfcGroup and/or mplsTunnelIsIntfcGroup.

Object(s) needed to implement manually configured tunnels.

Objects needed to implement signaled tunnels.

Scalar object needed to implement MPLS tunnels.

Objects needed to implement tunnels that are interfaces.

Objects needed to implement tunnels that are not interfaces.

Set of objects implemented for resources applicable for tunnels signaled using CR-LDP.

Set of objects needed to implement Sonet. None of these objects are mandatory.

Set of objects needed to implement UNI. None of these objects are mandatory.

Set of objects needed for backup tunnels. None of these objects are mandatory.

Set of objects relating to ARHop. None of these objects are mandatory.

Set of objects relating to CHop. None of these objects are mandatory.

Set of objects relating to DiffServ. None of these objects are mandatory.

Set of notifications implemented in this module. None is mandatory.

Compliance statement for agents that provide full support the MPLS-TE-STD-MIB module.

Compliance requirement for implementations that only provide read-only support for MPLS-TE-STD-MIB. Such devices can then be monitored but cannot be configured using this MIB modules.