Hello Manu, answering your questions. > - it first goes to SFC service. No action is taken here.
Only if SFC service is bound to the interface, which is only if thats the interface of SF participating on a RSP. If it does, SFC wont act on it because it's not a nsh packet. > - After processing by SFC service, it is again sent to egress > dispatcher. (Not sure whether the packet again passes through egress > acl and egress sfc classifier?) It does. For now we disable port security of the SF so the egress ACL wont act. > I couldn't find any value in NSH C1 being matched at egress > classifier at table 223(Egress Classifier TransportEgress table). It's on the egress classifier filter table (221), matching C1 to 0xFFFFFFFF. BR Jaime. -----Original Message----- From: Manu B <[email protected]> To: Vinayak Joshi <[email protected]>, sfc- [email protected] <[email protected]>, jcaamano@s use.de Subject: RE: [sfc-dev] Question on OF pipeline Date: Sun, 6 May 2018 10:39:31 +0000 Some more questions on top of this. "No, it does send it to the ingress sfc service directly in that case." Question: In the case of classifier and first SFF on same DPN, please let me know whether the below pipeline is correct. - it first goes to SFC service. No action is taken here. - Then it is resubmitted to Ingress Dispactcher which takes the packet to Ingress SFC classifier. - NSH is pushed here and then it is sent to Ingress dispatcher table. - This takes packet to remaining netvirt pipeline and then to egress SFC classifier. - Decision to sent to local or egress port is taken here. For local, it is sent again to SFC service. - After processing by SFC service, it is again sent to egress dispatcher. (Not sure whether the packet again passes through egress acl and egress sfc classifier?) Is the above pipeline correct? " We also set a magic value in NSH C1 on ingress classifier, and egress classifier only acts when this magic value is present." Question : I couldn't find any value in NSH C1 being matched at egress classifier at table 223(Egress Classifier TransportEgress table). In the function createEgressClassifierTransportEgressLocalFlow(OpenFlow13Provider.java) , the only match is nsp. Thanks, Manu -----Original Message----- From: [email protected] [mailto:sfc-dev-bounces@li sts.opendaylight.org] On Behalf Of Jaime Caamaño Ruiz Sent: 04 May 2018 14:11 To: Vinayak Joshi <[email protected]>; [email protected] ght.org Subject: Re: [sfc-dev] Question on OF pipeline No, it does send it to the ingress sfc service directly in that case. -----Original Message----- From: Vinayak Joshi <[email protected]> To: [email protected] <[email protected]>, jc [email protected] Subject: RE: [sfc-dev] Question on OF pipeline Date: Fri, 4 May 2018 04:29:59 +0000 Hi Jaime, What Egress SFC classifier does if the pkt has NSH and if SFF is local? (The slide says it gives is to Ingress SFC Service, it should be “gives it to Ingress Dispatcher” is that correct?) Regards, Vinayak -----Original Message----- From: Jaime Caamaño Ruiz [mailto:[email protected]] Sent: Thursday, May 03, 2018 8:07 PM To: Vinayak Joshi <[email protected]>; [email protected] ght.org Subject: Re: [sfc-dev] Question on OF pipeline Hello Vinayak The slide is probably a bit updated. > Doesn’t this cause a packet loop? Classifier service index is higher than SFC service index, so this can't happen. We also set a magic value in NSH C1 on ingress classifier, and egress classifier only acts when this magic value is present. > Isn’t this incorrect, packet with NSH should always be forwarded by > SFC services? The packet is intercepted and forwarded by the egress SFC classifier service, to the first SFF. Nevertheless, the egress SFC classifier needs to know which is the final destination (lport) of the packet, and thats determined by the remaining ingress services so thats the reason why the packet is resubmitted to the dispatcher by the ingress SFC classifier service. BR Jaime. -----Original Message----- From: Vinayak Joshi <[email protected]> To: [email protected] <[email protected]>, jc [email protected] Subject: [sfc-dev] Question on OF pipeline Date: Thu, 3 May 2018 10:28:00 +0000 Hi, I have a few questions on the OF pipeline described in Slide 1 at https ://docs.google.com/presentation/d/1gN8GnpVGwku4mp1on7EBZiE41RI7lZ- FFmFS2QlUTKk/edit#slide=id.g210ac90bb8_0_78. Sorry for the long mail. Please point out if the scenarios/my packet flows are incorrect. Say a regular packet arrives at br-int1 on port P1 from VM1 (i.e. VM1 is not an SF). Say the SFC Classifier (ingress) matches ACL ant it stamps NSH into the packet and resubmits to the ingress-dispatcher. Now there are two possible scenarios: Port P1 also has SFC service enabled on it. i. Packet gets into Ingress SFC service which sends the packet to egress dispatcher table. ii. Egress SFC Classifier acts on it. Since the packet has NSH and if the fist SFF is on the same br-int the packet is given packet to Ingress SFC. This is as per- iii. Question: Doesn’t this cause a packet loop? Port P1 does not have SFC service enabled on it. i. In this case a packet with NSH would be given to some other service (say L3) which for forward packet to final destination with NSH. ii. Question: Isn’t this incorrect, packet with NSH should always be forwarded by SFC services? Thanks in advance, Vinayak _______________________________________________ sfc-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/sfc-dev _______________________________________________ sfc-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/sfc-dev _______________________________________________ sfc-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/sfc-dev
