Cisco Cisco IOS Software Release 12.0(16)S
1
Cisco IOS Release 12.0(16)S
MPLS Traffic Engineering (TE) MIB
This document describes the Simple Network Management Protocol (SNMP) agent support in Cisco IOS
for Multiprotocol Label Switching (MPLS) traffic engineering management, as implemented in the
MPLS Traffic Engineering MIB (MPLS TE MIB).
for Multiprotocol Label Switching (MPLS) traffic engineering management, as implemented in the
MPLS Traffic Engineering MIB (MPLS TE MIB).
Multiprotocol Label Switching (MPLS) traffic engineering capabilities in Cisco IOS enable an MPLS
backbone to replicate and expand upon the traffic engineering capabilities of Layer 2 ATM and Frame
Relay networks.
backbone to replicate and expand upon the traffic engineering capabilities of Layer 2 ATM and Frame
Relay networks.
Traffic engineering capabilities are essential to effective management of service provider and Internet
service provider (ISP) backbones. Such backbones must support high transmission capacities, and the
networks incorporating backbones must be extremely resilient to link or node failures.
service provider (ISP) backbones. Such backbones must support high transmission capacities, and the
networks incorporating backbones must be extremely resilient to link or node failures.
The MPLS traffic engineering facilities built into Cisco IOS provide a feature-rich, integrated approach
to managing the large volumes of traffic that typically flow through wide area networks (WANs). The
MPLS traffic engineering facilities are integrated into Layer 3 network services, thereby optimizing the
routing of IP traffic in the face of constraints imposed by existing backbone transmission capacities and
network topologies.
to managing the large volumes of traffic that typically flow through wide area networks (WANs). The
MPLS traffic engineering facilities are integrated into Layer 3 network services, thereby optimizing the
routing of IP traffic in the face of constraints imposed by existing backbone transmission capacities and
network topologies.
Feature Overview
SNMP agent code operating in conjunction with the MPLS TE MIB enables a standardized,
SNMP-based approach to be used in managing the MPLS traffic engineering features in Cisco IOS.
SNMP-based approach to be used in managing the MPLS traffic engineering features in Cisco IOS.
The MPLS TE MIB is based on the IETF draft MIB entitled draft-ietf-mpls-te-mib-05.txt, which includes
objects describing features that support MPLS traffic engineering. This IETF draft MIB, which
undergoes revisions from time to time, is being evolved toward becoming a standard. Accordingly,
Cisco’s implementation of the MPLS TE MIB is expected to track the evolution of the IETF draft MIB.
objects describing features that support MPLS traffic engineering. This IETF draft MIB, which
undergoes revisions from time to time, is being evolved toward becoming a standard. Accordingly,
Cisco’s implementation of the MPLS TE MIB is expected to track the evolution of the IETF draft MIB.
Slight differences between the IETF draft MIB and the implementation of the traffic engineering
capabilities within Cisco IOS require some minor translations between the MPLS TE MIB and the
internal data structures of Cisco IOS. These translations are accomplished by means of the SNMP agent
code that is installed and operating on various hosts within the network. This SNMP agent code, running
in the background as a low priority process, provides a management interface to Cisco IOS.
capabilities within Cisco IOS require some minor translations between the MPLS TE MIB and the
internal data structures of Cisco IOS. These translations are accomplished by means of the SNMP agent
code that is installed and operating on various hosts within the network. This SNMP agent code, running
in the background as a low priority process, provides a management interface to Cisco IOS.
The SNMP objects defined in the MPLS TE MIB can be viewed by any standard SNMP utility. All MPLS
TE MIB objects are based on the IETF draft MIB; thus, no specific Cisco SNMP application is required
to support the functions and operations pertaining to the MPLS TE MIB.
TE MIB objects are based on the IETF draft MIB; thus, no specific Cisco SNMP application is required
to support the functions and operations pertaining to the MPLS TE MIB.