[NETVIRT-1142] Sfc classifier does not work for a reverse path when different egress/ingress port pairs Created: 08/Mar/18  Updated: 09/Mar/18  Resolved: 09/Mar/18

Status: Resolved
Project: netvirt
Component/s: General
Affects Version/s: Oxygen
Fix Version/s: Oxygen

Type: Bug Priority: Medium
Reporter: Jaime Caamaño Ruiz Assignee: Jaime Caamaño Ruiz
Resolution: Done Votes: 0
Labels: patch_merged
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

SFC classifier binds on the SF egress interface of the last RSP hop to be able to properly route the traffic to its original destination in case it is on the same compute as the original source of the traffic.

With the introduction of directional data plane locators for symmetric paths in SFC, the ingress and egress interfaces of a SF might be different and the classifier has to take care to bind to the correct one depending on the direction of the path, wether it is the reverse direction or the forward direction of the symmetric path.

Currently the classifier is binding randomly to one interfaces of the SFC, which makes it work sometimes but not always.



 Comments   
Comment by Jaime Caamaño Ruiz [ 08/Mar/18 ]

master: https://git.opendaylight.org/gerrit/#/c/69286/

oxygen: https://git.opendaylight.org/gerrit/#/c/69289/

Solved an additional issue where translator would set the ports of a port pair to the incorrect directional DPL:

master: https://git.opendaylight.org/gerrit/#/c/69295/

oxygen: https://git.opendaylight.org/gerrit/#/c/69296/

Comment by Sam Hague [ 09/Mar/18 ]

https://git.opendaylight.org/gerrit/69289

Generated at Wed Feb 07 20:23:20 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.