[sfc-dev] Service Chain Last Hop

Reinaldo Penno rapenno at gmail.com
Tue Aug 25 02:04:50 UTC 2015

We have implemented option 2 when SFC is used standalone. Each last SFF is responsible for sending plain packet after removing NSH. Some people want packet to go back to central point due to overlay or addressing issues.

But you can ask Python SFF to send packet back to classifier (or anywhere really) by adding IP address to context header.

> On Aug 24, 2015, at 6:57 PM, Zhou, Danny <danny.zhou at intel.com> wrote:
> I think you have two options:
> 1)      Once the SFF detects the Service Index equal to zero, forward it to classifier which then remove the NSH header and forward it to real destination using inner headers.
> 2)      SFF directly remove the NSH header and forward it to real destination.
> I personally prefer option No.1 as single point in the SFC to encap/decap NSH headres.
> From: sfc-dev-bounces at lists.opendaylight.org [mailto:sfc-dev-bounces at lists.opendaylight.org] On Behalf Of Jo?o Silva
> Sent: Monday, August 24, 2015 11:24 PM
> To: sfc-dev at lists.opendaylight.org
> Subject: [sfc-dev] Service Chain Last Hop
> Hi guys!
> In the current implementation what happens when the SFF receives the vxlan+nsh packet from the last service function? I'm asking this because, it seems the SFF is dropping the packet instead of delivering it to the its destination.
> Kind regards,
> João
> _______________________________________________
> sfc-dev mailing list
> sfc-dev at lists.opendaylight.org
> https://lists.opendaylight.org/mailman/listinfo/sfc-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendaylight.org/pipermail/sfc-dev/attachments/20150824/8c5d0f3c/attachment-0001.html>

More information about the sfc-dev mailing list