Cisco Cisco IOS Software Release 12.0(22)S
MPLS Traffic Engineering (TE)—Scalability Enhancements
How to Configure MPLS Traffic Engineering (TE)—Scalability Enhancements
4
Cisco IOS Releases: Multiple Releases (see the Feature Information Table)
•
Increased scalability—Up to 600 MPLS traffic engineering tunnel headends are supported. Up to
10,000 traffic engineering tunnel midpoints are supported, with up to 5000 midpoints per interface.
10,000 traffic engineering tunnel midpoints are supported, with up to 5000 midpoints per interface.
•
Faster recovery after failure conditions—Message pacing provides a mechanism to throttle RSVP
control messages so that they are less likely to be dropped. This results in a faster recovery from
failure conditions when many MPLS traffic engineering tunnels are being set up.
control messages so that they are less likely to be dropped. This results in a faster recovery from
failure conditions when many MPLS traffic engineering tunnels are being set up.
•
Improved reroute time—When a traffic engineering tunnel is down, the headend router needs to be
notified so that it can signal for a new LSP for the tunnel along an alternate path. The headend router
does not have to wait for an IGP update to signal for a new LSP for the tunnel along an alternate path.
notified so that it can signal for a new LSP for the tunnel along an alternate path. The headend router
does not have to wait for an IGP update to signal for a new LSP for the tunnel along an alternate path.
•
Improved tunnel setup time—Fewer control messages and tunnel setup messages are dropped. This
reduces the average time required to set up tunnels.
reduces the average time required to set up tunnels.
How to Configure MPLS Traffic Engineering (TE)—Scalability
Enhancements
Enhancements
This section describes the following tasks:
•
•
Enabling RSVP Message Pacing
RSVP message pacing maintains, on an outgoing interface basis, a count of messages that were dropped
because the output queue for the interface used for message pacing was full.
because the output queue for the interface used for message pacing was full.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
ip rsvp msg-pacing [period ms [burst msgs [maxsize qsize]]]
4.
end
5.
show ip rsvp neighbor
DETAILED STEPS
Command or Action
Purpose
Step 1
enable
Example:
Router> enable
Enables privileged EXEC mode.
•
Enter your password if prompted.
Step 2
configure
terminal
Example:
Router# configure terminal
Enters global configuration mode.