Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Ensure flow-stickiness with bridged forward flow and routed reverse flow
Support for following scenario, - An ECMP source sends a bridged packet to destination - On the destination compute node, l2-flow is created - Destination VM responds to flow with l3-flow - In VRouter packet processing, - Packet hits flow without any ECMP-Index - Packet go thru route processing (since dest mac is VRRP-MAC) - L3-Processing results in ECMP-NH - Packet trapped for ECMP resolution since ECMP-Index is not known In this scenario, we need to pick ECMP-Index such that packet reaches the reaches original source of packet from (1) after routing. Agent changes in ECMP Resolve processing: - Original source is found from the tunnel-info field of original forward flow - ECMP index computation logic is changed to choose the NH with tunnel-source got above Closes-Bug: #1645978 (cherry picked from commit 1433319) Conflicts: src/vnsw/agent/pkt/pkt_flow_info.h Change-Id: I1f7ac4bc46de49bc68f93a9248d40db325eb51bb
- Loading branch information
Showing
8 changed files
with
326 additions
and
44 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.