[SFC-192] Non-NSH packets going to SF are dropped Created: 27/Apr/17  Updated: 30/May/18  Resolved: 30/May/18

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

Type: Bug
Reporter: Manuel Buil Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


External issue ID: 8316

 Description   

SFC service is the one with the biggest priority in the ingress interface of a SF. That means the packet going to that SF will first be evaluated by the SFC pipeline. If it should not go into that pipeline, the packet will return to the service dispatcher table and be processed by the following service by priority. However, packets are being dropped in the SFC pipeline instead of being returned to the dispatcher table if they are not related to SFC (non-NSH packets). This should change because for example, as soon as a RSP is created, we cannot ping or SSH the SF anymore.



 Comments   
Comment by Manuel Buil [ 27/Apr/17 ]

https://git.opendaylight.org/gerrit/#/c/56091/
https://git.opendaylight.org/gerrit/#/c/56091/6

Comment by Manuel Buil [ 27/Apr/17 ]

https://git.opendaylight.org/gerrit/#/c/56091/ <--- stable/carbon
https://git.opendaylight.org/gerrit/#/c/56172/1 <--- master

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