[NETVIRT-690] New netvirt classifier expects but not set tunnel IP destination on egress pipeline Created: 23/May/17 Updated: 19/Oct/17 Resolved: 12/Aug/17 |
|
| Status: | Resolved |
| Project: | netvirt |
| Component/s: | General |
| Affects Version/s: | Carbon |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Jaime Caamaño Ruiz | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 8537 |
| Description |
|
Genius, on its egress handling of flow based tunnel interfaces, sets the remote IP address as the very last action before output. The original design of the new netvirt classifier egress pipeline expected this IP address to be set beforehand so that it could move it to NSH C1 and replace it with the SFF IP. As a result, C1 is empty and on chain egress the original packet cannot be handled properly. |
| Comments |
| Comment by Jaime Caamaño Ruiz [ 23/May/17 ] |
|
Solution proposed on master [1] and carbon [2] patches: Set the IP address on REG0 on the egress service binding actions (for which there is a genius bug reported [3] to get working properly). This will be the remote IP of the bound interface in case of tunnel ot the local IP otherwise. To avoid overuse of registries, a REG is no longer use to set the SFF IP address on table 101. This IP will be set directly on the path specific flows of table 223 if needed. Previously this REG was being use to know if the SFF was remote by comparing with the local IP in these flows but that is not need as it can be known at configuration time. [1] https://git.opendaylight.org/gerrit/#/c/57716 |