If NH doesn't have policy, do not create flows even if the source is an
ECMP
For providing stickiness in the case of ECMP, vRouter explicitly used to
create flows even if the corresponding NextHop didn't have the policy bit
set. This now is a wrong behavior when we are supporting ECMP without
flows. Hence, do not create such flows, if the nexthop doesn't have
policy enabled.
Reviewed: https:/ /review. opencontrail. org/22142 github. org/Juniper/ contrail- vrouter/ commit/ 75f51c86ac76341 69696f44231b842 b26a476191
Committed: http://
Submitter: Zuul
Branch: R3.1
commit 75f51c86ac76341 69696f44231b842 b26a476191
Author: Anand H. Krishnan <email address hidden>
Date: Fri Jul 15 10:09:55 2016 +0530
If NH doesn't have policy, do not create flows even if the source is an
ECMP
For providing stickiness in the case of ECMP, vRouter explicitly used to
create flows even if the corresponding NextHop didn't have the policy bit
set. This now is a wrong behavior when we are supporting ECMP without
flows. Hence, do not create such flows, if the nexthop doesn't have
policy enabled.
Change-Id: I48c28150b75e7c 78d4d093de327ca f98a19ff420
Partial-BUG: #1566650