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>Search


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


Can't bind L3VPN to some tunnel with using tunnel-policy (MPLS-TE) due to no mpls te reserved-for-binding command

Publication Date:  2013-07-15 Views:  77 Downloads:  1
Issue Description
Can't bind L3VPN. When use command
tunnel binding destiantion te Tunnel 0/1/3
Routing information not distributed. Traffic not flow.
Tunnel not present in vpn-instance routing table 
Handling Process
First, it was checking configuration of tunnel interface it could be found:
interface Tunnel0/1/3
 description to_XXX_NE-1_unstable
 ip address unnumbered interface LoopBack0
 tunnel-protocol mpls te
 mpls te tunnel-id 1003
 mpls te record-route label
 mpls te path explicit-path path_nera_ge_lnk
 mpls te commit
statistic enable
there is no mpls te reserved-for-binding command in the tunnel interface
Root Cause
When you configure the tunnel binding command, note the following:
    Before configuring the MPLS TE tunnel to be bound to VPN, configure the mpls te reserved-for-binding command in the tunnel interface view first.
    If the priority sequence and the load-balance number of tunnels are configured by using the tunnel select-seq command, you cannot configure the tunnel binding command for the tunnel policy, vice versa.

mpls te reserved-for-binding command in the tunnel interface view was configured, after that the issue was solved.

Команда tunnel select-seq взаимоисключает применение для политики команды tunnel binding и наоборот. Я указал это в выдержке из мануала.