Specifications

snmp-server enable traps mpls traffic-eng
MP-805
Cisco IOS Multiprotocol Label Switching Command Reference
January 2010
When the reroute keyword is used, mplsTunnelRerouted notifications are sent to the NMS under the
following conditions:
• The signaling path of an existing MPLS traffic engineering tunnel fails and a new path option is
signaled and placed into effect (that is, the tunnel is rerouted).
• The signaling path of an existing MPLS traffic engineering tunnel is fully operational, but a better
path option can be signaled and placed into effect (that is, the tunnel can be reoptimized). This
reoptimization can be triggered by:
– A timer
– The issuance of an mpls traffic-eng reoptimize command
– A configuration change that requires the resignaling of a tunnel
The mplsTunnelReoptimized notification is not generated when an MPLS traffic engineering tunnel is
re
optimized. However, an mplsTunnelReroute notification is generated. Thus, at the NMS, you cannot
distinguish between a tunnel reoptimization and a tunnel reroute event.
The s
nmp-server enable traps mpls traffic-eng command is used with the snmp-server host
command. Use the snmp-server host command to specify which hosts receive SNMP notifications. To
send SNMP notifications, you must configure at least one snmp-server host command.
Examples The following example shows how to enable the router to send MPLS notifications to the host at the
ad
dress myhost.cisco.com using the community string defined as public:
Router(config)# snmp-server enable traps mpls traffic-eng
Router(config)# snmp-server host myhost.cisco.com informs version 2c public
Related Commands Command Description
snmp-server host Specifies the recipient of an SNMP notification operation.
snmp-server trap-source Specifies the interface that an SNMP trap should originate from.