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.


load balance per-packet is not working

Publication Date:  2014-06-27 Views:  109 Downloads:  0
Issue Description

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.

Board: DEVLPUF-1

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

Handling Process

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.

interface Pos1/0/0                                 

 link-protocol hdlc

description LAT:JBL_POPR_Cisco_01

undo shutdown

ip address

isis enable 1

isis circuit-level level-2

isis cost 1000


mpls ldp

undo scramble

crc 16

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)

Usage Guidelines

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.

tunnel select-seq

Usage Guidelines

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> system-view
[HUAWEI] tunnel-policy l2
[HUAWEI-tunnel-policy-l2] tunnel select-seq lsp load-balance-number 2

Root Cause

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-tunnel-policy-policy1] quit


[PE1] mpls l2vpn

[PE1-l2vpn] mpls l2vpn default martini  

[PE1-l2vpn] quit

[PE1] interface pos2/0/0

[PE1-Pos2/0/0] mpls l2vc 100 tunnel-policy policyl2

[PE1-Pos2/0/0] undo shutdown