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-15Views: 77Downloads: 1
Can't bind L3VPN. When use command tunnel binding destiantion 22.214.171.124 te Tunnel 0/1/3 Routing information not distributed. Traffic not flow. Tunnel not present in vpn-instance routing table
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 destination 126.96.36.199 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 nomplste reserved-for-binding command in the tunnel interface
When you configure the tunnel binding command, note the following: · Before configuring the MPLS TE tunnel to be bound to VPN, configure the mplste 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.
mplste reserved-for-binding command in the tunnel interface view was configured, after that the issue was solved.
Команда tunnel select-seq взаимоисключает применение для политики команды tunnel binding и наоборот. Я указал это в выдержке из мануала.