Re-optimization Time for Tunnel-TE in IOS XR 4.3.2
We have configured the Tunnel-TE with explicit path options 1 & 2. When we generate a failure scenario in primary path, the traffic switches over to secondary immediately but on the failure restoration, the primary tunnel does not preempt. On further investigation, we found that default reoptimization time for TE Tunnel is 60 mins which is vey high for us.
The tunnel configuration is as below.
ipv4 unnumbered Loopback10
path-option 1 explicit name PATH_Pri
path-option 2 explicit name PATH_Sec
explicit-path name PATH_Pri
index 10 next-address strict ipv4 unicast 10.220.37.82
explicit-path name PATH_Sec
index 10 next-address strict ipv4 unicast 10.220.37.6
index 20 next-address strict ipv4 unicast 10.220.37.86
index 30 next-address strict ipv4 unicast 10.220.37.9
While exploring through internet, I came across a forum which mentions 3 options for reoptimization but it is for IOS. The wording goes like...
Reoptimization causes a tunnel to be rerouted in the network onto the more optimal path.
Three triggers can cause reoptimization of the TE tunnel so that it can be rerouted to the better path.
Periodic reoptimization - By default, the reoptimization of a TE tunnel occurs with a frequency of one hour
mpls traffic-eng reoptimize timers frequencyinterval changes the periodic reoptimization of a tunnel.
Event-driven reoptimization -mpls traffic-eng reoptimize events link-upenables the reoptimization when a link becomes operational for MPLS TE
By default, Cisco IOS does not trigger reoptimization when a link in the network is available to TE again, either by configuration or because its state becomes operational.
Manual reoptimization - mpls traffic-eng reoptimize forces the immediate reoptimization of all the TE tunnels on the head end router.
I would like to know that
1. Is there any specific requirement behind keeping the default (periodic) reoptimization timer to 60 mins?
2. I could not find the options for configuring 'Event Driven reoptimization' in IOS XR. How to get it?
3. What are best practice reoptimization timer to be used in the network?
gfichera You are the man. Your reply works man. The only set back is that re-optimization is triggered by the RSVP (in your IGP) at the headend. Of which, this can take some time(seconds) depending on fast your IGP convergence to inform the headend that,"Oh man, that primary LSP that was down is now up, lets re-optimize and use it."
Listen: https://smarturl.it/CCRS8E39 Follow us: twitter.com/CiscoChampion5G and Wi-Fi 6, the next generation of mobile wireless technologies are here! But what does that mean? Where and how is 5G being deployed? What is Wi-Fi 6? Who’s on first? ...
loadbalancing is one of the more complex items in hardware forwarding. of course we have talked about it many years on cisco live (id 2904) with ever incrementing more detail. and there is the support forum article on loadbalancing.
IntroductionArchitecture Building BlocksIOS-XR RoutersConfigurationPerformance VerificationOptimizationStrict timerSome more verificationThe CollectorInfluxDBDatabase statistics and HealthClosing comments
This document was written in collaboration with:
IOS-XR MPLS TE Auto Tunnel Backup Bandwidth Protection Current Implementation of MPLS TE Auto Tunnel BackupPotential issue with current implementation of MPLS TE auto tunnel backupEnhancement to MPLS TE auto backup in IOS XR 7.5.1Supported HardwareConfig ...
we are trying to monitor the Cisco 9148s SFP status, and have get the Sensor's dBm value from the CISCO-ENTITY-SENSOR-MIB table, meanwile , it has an Index value like "30000xxxx",such as "30001773", entsensorValueTable but we can't sure how to l...