[SFC-198] ACL classifier flow entry is not programmed correctly when ACL Classifier and SF are connected to same SFF Created: 07/Jul/17 Updated: 19/Oct/17 |
|
| Status: | Open |
| Project: | sfc |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Periyasamy Palanisamy | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
|
| External issue ID: | 8816 |
| Description |
|
When hosts which undergoes into ACL classification and SF is connected to same SFF, then table 0 flow entry for ACL classifier is programmed with action pointing to SFF's vxlan-gpe port instead of forwarding packet into table 1 so that packet can be steered into SF. |
| Comments |
| Comment by Periyasamy Palanisamy [ 07/Jul/17 ] |
|
Attachment logs.txt has been added with description: flows, ports, sf and sff dumps |
| Comment by Brady Johnson [ 07/Jul/17 ] |
|
Please provide more information:
|
| Comment by Jaime CaamaƱo Ruiz [ 07/Jul/17 ] |
|
I had the chance to talk with Perisayami so let me add some more info. This is using the sfc-scf classifier on a standard deployment (like 103 demo, but just 1 node). The classifier does not account for the fact that it could be located on the same node as the first SFF and in such a case attempts to output through the vxlan-gpe port instead of the redirecting the packet to the SFF pipeline. Anyway Perisayami, please attach the information mentioned by Brady. |
| Comment by Periyasamy Palanisamy [ 11/Jul/17 ] |
|
Attachment sfc-demo-single-computenode.postman_collection has been added with description: sfc json input |
| Comment by Periyasamy Palanisamy [ 11/Jul/17 ] |
|
(In reply to Periyasamy Palanisamy from comment #3)
If you are okay, then I would take up this bug and start investigating it. |