The SFC-103 only includes the NSH aware SF, which means the SF recognizes the NSH as well as transports (e.g. VxLAN-GPE, Eth) in front of the original frame (say the TCP/HTTP packet in your case), so the SFF should keep the NSH instead of removing them.
The SFC-104 demo post Boron will be including VPP based NSH proxy which could remove the NSH when steering traffic to NSH unaware SFs. From: [email protected] [mailto:[email protected]] On Behalf Of Alioune Sent: Monday, September 5, 2016 5:40 AM To: sfc-dev opendaylight <[email protected]> Subject: [sfc-dev] SFC-103 SF NSH aware Hi all, I'm testing the SFC 103 demo, after launching the demo.sh all nodes and SFC services are corretlly configured. I run tcpdump on eth0 in SF1 and I expect to se e the HTTP traffic but it is encapsulated in UDP frames. Why does the SFF1 not remove the NSH headers ? Is there specific configuration for doing that ? Regards,
_______________________________________________ sfc-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/sfc-dev
