MPLS-TE path-proction

 

Hi My Everone please me some issue about MPLS-TE Path protection.

 I've done on end to end configure, when main path go to down backup path working as well, but whe main coming up again the protection path still up, traffic not go to main path how we can do that, please help.

 

 

XR_A

Tunnel-TE40001
main path = XR_A to XR_B
protection path = XR_A -to- XR_C -to- XR_D -to- XR_E -to- XR_B.


XR_B
Tunnel-TE40001
main path = XR_B to XR_A
protection path = XR_B -to- XR_E -to- XR_D -to- XR_C -to- XR_A.


XR_A.


interface TenGigE0/2/0/0.10
 
 ipv4 address interface loopback0_XR_A
 load-interval 30
 dot1q vlan 10
!

explicit-path name TH-SG-main-path
 index 10 next-address strict ipv4 unicast IP_XR_B
!
explicit-path name TH-SG-protection-path
 index 10 next-address strict ipv4 unicast IP_XR_C
 index 20 next-address strict ipv4 unicast IP_XR_D
 index 30 next-address strict ipv4 unicast IP_XR_E

!

XR_A#sh run mpls traffic-eng
Thu Dec 26 14:49:46.065 THAI
mpls traffic-eng
 
 interface TenGigE0/2/0/0
 !
 interface TenGigE0/2/0/0.10
 !
!


XR_A#sh run mpls traffic-eng
Thu Dec 26 14:49:46.065 THAI
mpls traffic-eng

 interface TenGigE0/2/0/0
 !
 interface TenGigE0/2/0/0.10
 !
!

XR_A#sh run int tunnel-te40001
Thu Dec 26 14:51:34.654 THAI
interface tunnel-te40001
 ipv4 unnumbered Loopback1
 priority 1 1
 destination interface loopback0_XR_A
 fast-reroute
 path-option 10 explicit name TH-SG-main-path
 path-option 100 explicit name TH-SG-protection-path
!


--------------------------------------------------------------------


XR_B.

XR_B#sh run int tenGigE 0/3/0/0.10
Thu Dec 26 14:55:24.739 THAI
interface TenGigE0/3/0/0.10
 
 ipv4 address interface loopback0_XR_A
 load-interval 30
 dot1q vlan 10
!

explicit-path name TH-SG-main-path
 index 10 next-address strict ipv4 unicast IP_XR_A
!
explicit-path name TH-SG-protection-path
 index 10 next-address strict ipv4 unicast IP_XR_E
 index 20 next-address strict ipv4 unicast IP_XR_D
 index 30 next-address strict ipv4 unicast IP_XR_C

!

XR_B#sh run rsvp
Thu Dec 26 14:57:31.494 THAI
rsvp

 interface tunnel-te40001
  signalling hello graceful-restart interface-based
  signalling refresh interval 10
 !
 signalling graceful-restart
 signalling hello graceful-restart refresh interval 10000
!


XR_B#sh run rsvp
Thu Dec 26 14:57:31.494 THAI
rsvp

 interface tunnel-te40001
  signalling hello graceful-restart interface-based
  signalling refresh interval 10
 !
 signalling graceful-restart
 signalling hello graceful-restart refresh interval 10000
!

 

XR_B#sh run interface tunnel-te40001
Thu Dec 26 15:01:56.681 THAI
interface tunnel-te40001
 ipv4 unnumbered Loopback1
 priority 1 1
 destination interface loopback0_XR_A
 fast-reroute
 path-option 10 explicit name SG-TH-main-path
 path-option 100 explicit name SG-TH-protection-path
!

Comments

  • By default Cisco IOS reoptimizes the TE tunnel every hour - you can change this behaviour with the command 'mpls traffic-eng reoptimize timers frequency interval'.

     

    Alternatively, you can manually reoptimize the TE tunnels by issuing the command 'mpls traffic-eng reoptimize' at the router prompt.

     

    Hope that helps.

  • peetypeety ✭✭✭

    Are you saying the traffic is flowing over the backup tunnel after the main tunnel has had time to converge onto a new path after the initial path failure, or are you saying that the traffic is flowing over the main tunnel but the main tunnel hasn't reconverged onto the direct/preferred path?

    As mnhussain mentioned, are you waiting long enough for the optimization timers to trigger path reoptimization?  If not, you're jumping the gun; you should expect a "slow and graceful" return to the direct path, which I actually prefer since a flapping link won't get used right away, minimizing secondary convergence impact.

  • Hi Friends,

    So many thanks for your kind, You're right the main tunnal came up after around 30 minute. good job have a new year 2014.

     

Sign In or Register to comment.