No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FAQ-How to Change tunnel paths configuration over MPLS TE without Service interruption in Live Network

Publication Date:  2012-07-27 Views:  159 Downloads:  1
Issue Description
Q:
How we can modify MPLS TE tunnels paths Primary and secondary explicit paths without live traffice interruption?
Customer need to modify the mpls te tunnel paths to put the optimum path for primary and the other path for secondary while the network is live without any interruption.


Alarm Information
N/A


Handling Process

A :

1.    Firstly, you need to create a new primary and secondary explicits paths other than the already used ones ,

explicit-path primary2
  next hop 10.244.47.150 include loose
#
 explicit-path backup2
  next hop 10.244.47.150 exclude
 

2.    Enter the current configured tunnel mode and undo the explicits paths primary and secondary without excute “MPLS TE Commit “command, in this way the old tunnel will be still used,

interface Tunnel0/2/201
 undo mpls te path explicit-path primary1
 undo mpls te path explicit-path backup secondary1
 

3.   Configure the tunnel with new primary and secondary explicits paths

interface Tunnel0/2/201
 mpls te path explicit-path primary2
 mpls te path explicit-path backup2 secondary
 
4.  Configure MPLS TE Reoptimaization and backup hot standby & ordinary best effort  (Optional)mpls te reoptimization
      mpls te backup hot-standby
      mpls te backup ordinary best-effort
 

5.  Configure MPLS TE commit, now the traffic will transfer through the new paths without interruption on the live network through same tunnel

interface Tunnel0/2/201
mpls te commit

6.    After that you can remove the old explicits paths safely .

Undo explicit-path primary1
Undo explicit-path backup1
 

7.   We should test the primary path hubs that what we need by using command :
     > tracert lsp te tunnel 0/2/201

Here is the final full configuration :
explicit-path primary
  next hop 10.244.47.150 include loose
#
 explicit-path backup
  next hop 10.244.47.150 exclude
#
interface Tunnel0/2/201
 description ***to_BKK3200-AG-01 ***
 ip address unnumbered interface LoopBack0
 tunnel-protocol mpls te
 destination 10.240.160.21
 mpls te tunnel-id 201
 mpls te record-route label
 mpls te path explicit-path primary
 mpls te path explicit-path backup secondary
 mpls te backup hot-standby
 mpls te backup ordinary best-effort
 mpls te reoptimization
 mpls te commit
#
#
bfd main bind mpls-te interface Tunnel0/2/201 te-lsp
 discriminator local 1
 discriminator remote 5262
 process-pst
 commit
#
bfd backup bind mpls-te interface Tunnel0/2/201 te-lsp backup
 discriminator local 2
 discriminator remote 6262
 process-pst
 commit
#
 
 


Root Cause
Suggestions
N/A


END