BUG 6387: Traffic drop in 17 in serviceChain
Analysis:
In a non servicechain scenario, packets get to LFIB and are sent over
the corresponding port.
In ServiceChain scenario, there are new Flows in LFIB, with higher priority,
that sends the packet to 17 which, in turn, is redirecting it to SCF Pipeline.
However, no SC matches and packets are submitted back to 17. Since packets
have not changed, they get in a loop between 17 and 70.
Solution:
Table-miss in 70-75 tables must change the SI to L3VPN, so that when
the packet gets back to 17, they are redirected to FIB table.
Also, entries in 17 that handle packets that match no SC must be
programmed in all CSS where the VPN has footprint, not just in the
CSS where the last vSF in the chain is located.
Change-Id: I1cfc2973049746019a310ef3b106a5e416f24f04
Signed-off-by: Suraj Ranjan <suraj.ranjan@ericsson.com>