Ask is moving to Stack Overflow and! Please use the "opendaylight" tag on either of these sites. This site is now in Read-Only mode


SFCOFL2 Tutorial define classifiers

asked 2016-03-22 08:58:25 -0700

chrisborovas gravatar image

updated 2016-03-22 08:59:26 -0700

Hello everyone!

I 'm trying to deploy the SFCOFL2 Tutorial which is placed in the user-guide of berrylium.

I have made it in Lithium release (because in Beryllium a RuntimeException in processRenderedServicePath was raised) and I could take the correct flows using these commands on mininet VM:

sudo ovs-ofctl -O OpenFlow13 dump-flows s2 sudo ovs-ofctl -O OpenFlow13 dump-flows s3

The mininet topology is this: sudo mn --topo linear,4 --mac --controller remote,ip=<ip>,port=<port> --switch ovsk,protocols=OpenFlow13

I think that this tutorial is missing some extra things, because the bridges s1 and s4 have no flows. As the result of this the traffic from h1 is not trasported to anyone.

I 'm using the sfcofl2 module with mpls and vlans instead of NSH encapsulation, because the NSH is not integrated yet with OVS and hence its not stable. In addition, I don't know the state of sfc_proxy because the I think it's too hard to make the services NSH aware.

Am I wrong in my opinions?

Have anyone managed to make a sfc complte demo without nsh encapsoulation, testing it with traffic?

I have seen the demostration of ericsson, but they are adding manualy some flows:

sudo ovs-vsctl set bridge $NODE protocols=OpenFlow10,OpenFlow11,OpenFlow12,OpenFlow13 sudo ovs-ofctl -O Openflow13 add-flow $NODE "table=0,priority=10,inport=1,dltype=0x0800,nwproto=6,tpdst=80,actions=move:NXMOFETHDST[0..31]->NXMNXREG0[],move:NXMOFETHDST[32..47]->NXMNXREG1[0..15],move:NXMOFETHSRC[]->NXMOFETHDST[],move:NXMNXREG0[0..31]->NXMOFETHSRC[0..31],move:NXMNXREG1[0..15]->NXMOFETHSRC[32..47],inport" sudo ovs-ofctl -O Openflow13 add-flow $NODE "table=0,priority=10,inport=1,dltype=0x0800,nwproto=6,tpsrc=80,actions=move:NXMOFETHDST[0..31]->NXMNXREG0[],move:NXMOFETHDST[32..47]->NXMNXREG1[0..15],move:NXMOFETHSRC[]->NXMOFETHDST[],move:NXMNXREG0[0..31]->NXMOFETHSRC[0..31],move:NXMNXREG1[0..15]->NXMOFETHSRC[32..47],inport" sudo ovs-ofctl -O Openflow13 add-flow $NODE "table=0,priority=1,actions=drop"

The flows above are using NSH encapsulation, as I understand.

Is there any problem with the Services Functions which are not NSH aware?

I 'm litle bit confused.. :(

Any help would be appreciated! Regards

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2016-05-26 08:32:17 -0700

Looks like the user guide you mention needs to be updated. I will look into doing that for Boron.

To answer your questions:

Am I wrong in my opinions?

I dont think its correct to say that just because NSH hasnt been merged into OVS that its not stable. The OVS community is indeed taking a very long time to merge the NSH patches, but that's not due to stability.

Is there any problem with the Services Functions which are not NSH aware?

What we call "Non NSH-Aware" Service Functions is the only drawback to using NSH right now. Its a new technology which requires the industry to adapt.

I would invite you to try one of the following 2 NSH demos:

The Ericsson demo you mentioned above is currently broken due to some changes in Beryllium. This demo was prepared before we had any NSH demos available. I would prefer to migrate everyone over to the NSH demos.

edit flag offensive delete publish link more

answered 2016-05-27 01:33:03 -0700

chrisborovas gravatar image

Hello ebrjohn!

Thank you for your answer. I totally agree with your logic. I will deploy the new sfc-demo at the first chance.

Generally, the "Non NSH-Aware" service functions is a problem.. By the way, the SFC-proxy, for translating NSH packages for Non NSH-Aware SFs, is planned to be implemented?


edit flag offensive delete publish link more
Login/Signup to Answer

Question Tools

1 follower


Asked: 2016-03-22 08:58:25 -0700

Seen: 181 times

Last updated: May 27 '16