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.

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 protocols simultaneously. Bits: 'isis': 2, 'other': 0, 'ospf': 1.

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

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

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.

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 Extended Tunnel Id field in the Session object. When the MPLS signalling protoocol is crldp(3) this value should mimic the Ingress LSR Router ID field in the LSPID TLV object.

Specifies the egress LSR Id.

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

A textual string containing information about the tunnel. If there is no description this object contains a zero length string.

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.

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 signaling protocol, if any, which was 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 bitfields: 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 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. isComputed This flag indicates whether the tunnel path is computed using a constraint-based routing algorithm based on the mplsTunnelHopTable entries. recordRoute This flag indicates whether or not the signaling protocol should remember the tunnel path after it has been signaled. Bits: 'isPersistent': 2, 'isPinned': 3, 'fastReroute': 0, 'recordRoute': 5, 'mergingPermitted': 1, 'isComputed': 4.

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. Enumeration: 'admin': 1, 'other': 5, 'crldp': 3, 'policyAgent': 4, 'rsvp': 2.

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

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

Index into the mplsTunnelARHopTable entry that specifies the actual hops traversed by the tunnel.

Index into the mplsTunnelCHopTable entry that specifies the computed hops traversed by the tunnel.

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

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 paths has changed for this tunnel.

Specifies the time since the last path change for this tunnel.

Specifies the value of SysUpTime when the first instance of this tunnel came into existence.

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

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.

A link satisfies the include-all constraint if and only if the link contains all of the adminstrative groups specified in the constraint.

A link satisfies the exclude-all constraint if and only if the link contains none of the adminstrative groups specifie in the constraint.

This value denotes the configured path that was chosen for this tunnel. This value reflects the secondary index into the TunnelHopTable. This path may not exactly match the one in the ARHopTable due to the fact that some CSPF modification may have taken place. See the ARHopTable for the actual path being taken by the tunnel. A value of zero denotes that no path is currently in use or available.

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. Enumeration: 'head': 1, 'tail': 3, 'transit': 2.

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

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.

This variable indicates the storage type for this object.

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.

Denotes the address type of this tunnel hop. Enumeration: 'lspid': 4, 'asNumber': 3, 'ipV4': 1, 'ipV6': 2.

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

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

If mplsTunnelHopAddrType is set to lspid(4), 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. Enumeration: 'strict': 1, 'loose': 2.

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

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.

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.

Denotes the address type of this tunnel hop. Enumeration: 'asNumber': 3, 'ipV4': 1, 'ipV6': 2.

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

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

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

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.

Denotes the address type of this tunnel hop. Enumeration: 'asNumber': 3, 'ipV4': 1, 'ipV6': 2.

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

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

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

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.

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

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 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 notification is generated when a tunnel is rerouted or re-optimized. 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.

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.

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

The objects in this group are optional.

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

Compliance statement for agents that support the MPLS TE MIB.