Configuring MPLS Traffic Engineering and Fast Reroute
Configuring a Protected Link to Use a Backup Tunnel
Beginning in privileged EXEC mode, follow these steps to configure a protected link to use the backup
tunnel:
Command
Step 1
configure terminal
Step 2
interface interface-id
Step 3
mpls traffic-eng backup-path tunnel
tunnel-id
Step 4
end
Step 5
show mpls traffic-eng fast-reroute
database
Step 6
copy running-config startup-config
To remove the backup tunnel configuration, enter the no mpls traffic-eng backup-path tunnel interface
configuration command.
Configuring Fast Reroute Failure Detection (Optional)
This configuration is needed only when loss of signal cannot be detected.
Beginning in privileged EXEC mode, follow these steps to configure fast reroute failure detection:
Command
Step 1
configure terminal
Step 2
ip rsvp signalling hello
Step 3
interface interface-id
Step 4
ip rsvp signalling hello fast-reroute refresh
misses number
Step 5
ip rsvp signalling hello fast-reroute refresh
interval interval-value
Step 6
ip rsvp signalling hello
Step 7
end
Cisco ME 3800X and 3600X Switch Software Configuration Guide
34-24
Chapter 34
Configuring MPLS, MPLS VPN, MPLS OAM, and EoMPLS
Purpose
Enter global configuration mode.
Specify the interface ID of the protected link and enter interface
configuration mode.
Configure the interface to use a backup tunnel in the event of a
detected failure on that interface. You can enter this command
multiple times to associate the protected interface with multiple
backup tunnels.
Return to privileged EXEC mode.
Verify the that backup protection is configured. A ready status means
that the tunnel is ready to switch to backup; an active status means
that tunnel traffic is on backup.
(Optional) Save your entries in the configuration file.
Purpose
Enter global configuration mode.
Globally enable Hello signalling on the switch.
Specify an interface ID, and enter interface configuration mode.
Configure the number of consecutive RSVP TE hello
acknowledgments a node can miss before the node communication
with its neighbor status is down. Valid values are from 4 to 10. The
default is 4.
Configure the frequency, in milliseconds, at which a node sends
hello messages to a neighbor. Valid values are from 10 to 30000 (.01
to 30 seconds). The default frequency is 1000 milliseconds (10
seconds).
Note
To prevent false detection of a down neighbor and
unnecessarily triggering fast reroute, we recommend
configuring a minimum frequency of 200 ms.
Enable Hello signalling on the interface.
Return to privileged EXEC mode.
OL-23400-01