To have a better experience, please upgrade your IE browser.upgrade
Questo sito utilizza cookie di profilazione (propri e di terze parti) per ottimizzare la tua esperienza online e per inviarti pubblicità in linea con le tue preferenze. Continuando a utilizzare questo sito senza modificare le tue preferenze acconsenti all’uso dei cookie. Se vuoi saperne di più o negare il consenso a tutti o ad alcuni cookie clicca qui>
The website that you are visiting also provides Arabian language. Do you wish to switch language version?
يوفر موقع الويب الذي تزوره المحتوى باللغة العربية أيضًا. هل ترغب في تبديل إصدار اللغة؟
The website that you are visiting also provides Russia language Do you wish to switch language version?
Данный сайт есть в английской версии. Желаете ли Вы перейти на английскую версию?
Cisco device is connected by (POS1/0/0 & POS1/0/2) to the Aggregation layer "NE40-X8" and prefers an interface at the expense of the other on the inbound direction.
Sub Board: CR53P8CF
Customer had tried the below action without success:
1. Active Load balance per-packet on All slot. not success
2. Active Load balance per-flow on all slot with (ip-enhance, hash-enhance, deep-hash) not success
As the interfaces are connected to different NE routers and they are using MPLS LDP.
So we need to confirm the traffic model, if the traffic goes into the remote device under different tunnel.
in this case, We need to set the tunnel as load balance with tunnel policy.
ip address 10.100.215.25 255.255.255.252
isis enable 1
isis circuit-level level-2
isis cost 1000
flag c2 207
flag j0 peer
flag j1 peer
if no policy is used , NE40E may only use one LSP for forwarding.
tunnel-policy (system view)
By default, LDP LSPs or static LSPs are adopted for a VPN and no load balancing is carried out.
By using the tunnel policy, you can:
· Bind a tunnel to a destination IP address (also called VPN tunnel binding).
· Define the priority sequence or number of tunnels taking part in load balancing.
In the tunnel select-seq command:
The nearer a tunnel type is to the keyword select-seq, the higher the tunnel priority is. Only the tunnel types listed in the command can be used.
When load balancing is performed among different types of tunnels, traffic prefers the tunnel with higher priority.
In tunnel policy, the multiple class type (multi-CT) CR-LSP supports only the VPN tunnel binding mode rather than the select-sequence mode.
# Configure a tunnel policy that only LDP LSPs or static LSPs can be used. Set the number of tunnels taking part in load balancing to 2.
[HUAWEI] tunnel-policy l2
[HUAWEI-tunnel-policy-l2] tunnel select-seq lsp load-balance-number 2
need tunnel policy because the tunnel is not making load balance between the 2 POS interfaces by default.
using tunnel policy and Tunnel select-seq
[PE1] tunnel-policy policy1
[PE1-tunnel-policy-policy1] tunnel select-seq lsp load-balance-number 2
[PE1] mpls l2vpn
[PE1-l2vpn] mpls l2vpn default martini
[PE1] interface pos2/0/0
[PE1-Pos2/0/0] mpls l2vc 220.127.116.11 100 tunnel-policy policyl2
[PE1-Pos2/0/0] undo shutdown