Issue Description
A load-sharing problem over NE40E its software version (V300R003C02B608) as follow :
Routes for a vpn-instance are installed with next-hop IP 172.21.1.120, which is reachable within global routing table through two interfaces (G8/0/0.103 & G4/0/1.203) as shown in the beolw output :
<NE40E>display ip routing-table 172.21.1.120
Route Flags: R - relay, D - download to fib
------------------------------------------------------------------------------
Routing Table : Public
Summary Count : 2
Destination/Mask Proto Pre Cost Flags NextHop Interface
172.21.1.120/32 ISIS 8 30 D 172.21.26.9 GigabitEthernet8/0/0.103
ISIS 8 30 D 172.21.26.13 GigabitEthernet4/0/1.203
However the next hop interface for all vpn-instance routes are installed with only single next-hop interface, while ignoring the other interface as shown in the beolw output :
<NE40E>display ip routing-table vpn-instance ADSL 0.0.0.0
Route Flags: R - relay, D - download to fib
------------------------------------------------------------------------------
Routing Table : ADSL
Summary Count : 1
Destination/Mask Proto Pre Cost Flags NextHop Interface
0.0.0.0/0 BGP 255 0 RD 172.21.1.120 GigabitEthernet8/0/0.103
Handling Process
the problem is solved after adding the below configuration :
[NE40E]tunnel-policy adsl
[NE40E-tunnel-policy-adsl]tunnel select-seq cr-lsp lsp load-balance-number 2
[NE40E]ip vpn-instance ADSL
[NE40E-vpn-instance-ADSL]tnl-policy adsl
Root Cause
There is no configuration on this router to support load-sharing mode, usually this is a configuration problem
Due to the default of vpn traffic is to only select one path to transfer the packets, so we should define a "tunnel-policy" to make the load-sharing .
