Hi Brady Thanks for pointing out this link. I am trying to bring up the right OS environment as per the note in the link ( reference [1] ) . My Ubuntu is 16.04 with kernel version 4.8.0-54-generic on x86_64 box. I can create VM for this purpose.
Query - 1: Can I get Ubuntu 15.10image ? Query - 2: Is this possible in Ubuntu 14.04 / Ubuntu 16.04 Thanks in Advance [1] . The version should built is 2.5.90. This version is not compatible with kernel versions newer than 4.3.x. It works on Ubuntu 15.10 for example. More information available on in this With Best Regards Dhevendran Kulandaivel Tata Consultancy Services Limited Cell:- +919845439011 Mailto: [email protected] Website: http://www.tcs.com ____________________________________________ Experience certainty. IT Services Business Solutions Consulting ____________________________________________ From: Brady Allen Johnson <[email protected]> To: Dhevendran K <[email protected]> Cc: Sunil Desai <[email protected]>, Sujith Kumar K <[email protected]>, Suresh Nagaraj <[email protected]>, Divya T V <[email protected]>, Eshappa K <[email protected]>, Mani Mahalingam <[email protected]>, "[email protected]" <[email protected]> Date: 06/12/2017 06:33 PM Subject: Re: [sfc-dev] ODL Log Message while configuring the SFC Dhevendran, Looks like you're not using a version of OVS with NSH installed. As you mentioned there are no flows with VXLAN-GPE (notice its gpe (generic protocol encapsulation), not gre) but more importantly, no flows with NSH. You can use this link to install OVS with NSH: https://wiki.opendaylight.org/view/Service_Function_Chaining:Main#Building_Open_vSwitch_with_VxLAN-GPE_and_NSH_support Regards, Brady -----Original Message----- From: Dhevendran K <[email protected]> To: Brady Allen Johnson <[email protected]> Cc: Eshappa K <[email protected]>, Mani Mahalingam < [email protected]>, [email protected] < [email protected]>, Sujith Kumar K <[email protected]>, Sunil Desai <[email protected]>, Suresh Nagaraj <[email protected] >, Divya T V <[email protected]> Subject: Re: [sfc-dev] ODL Log Message while configuring the SFC Date: Mon, 12 Jun 2017 16:16:42 +0530 Hi Brady Thanks for your immediate response (along with the patch update). With your patch, we are able to see the configuration of SFFs on OVS. But, our dump-flows results as follows (not matching with your result). By looking at this, it is clear that the VXLAN-GRE tunnel flows are missing. Query-1 : It would be great if you guide us to create the missing (or correct) topology for this SFC environment. =========================== Out put of "sudo ovs-ofctl dump-flows br-int" ================================================= ubuntu@ubuntu-HP-Compaq-8200-Elite-SFF-PC:~/VCPE/SCF_app/sfc/vnfmgr/vnfmgr_odl$ sudo ovs-ofctl dump-flows br-int [sudo] password for ubuntu: NXST_FLOW reply (xid=0x4): cookie=0x2b00000000000005, duration=475.147s, table=0, n_packets=0, n_bytes=0, idle_age=475, priority=100,dl_type=0x88cc actions=CONTROLLER:65535 cookie=0x2b00000000000005, duration=475.147s, table=0, n_packets=0, n_bytes=0, idle_age=475, priority=0 actions=drop cookie=0x14, duration=473.558s, table=0, n_packets=0, n_bytes=0, idle_age=473, priority=5 actions=resubmit(,1) cookie=0x2b00000000000005, duration=473.147s, table=0, n_packets=0, n_bytes=0, idle_age=473, priority=2,in_port=1 actions=CONTROLLER:65535 cookie=0x14, duration=473.459s, table=1, n_packets=0, n_bytes=0, idle_age=473, priority=5 actions=drop cookie=0x14, duration=473.459s, table=2, n_packets=0, n_bytes=0, idle_age=473, priority=5 actions=resubmit(,3) cookie=0x14, duration=473.458s, table=3, n_packets=0, n_bytes=0, idle_age=473, priority=5 actions=resubmit(,4) cookie=0x14, duration=473.458s, table=4, n_packets=0, n_bytes=0, idle_age=473, priority=5 actions=resubmit(,10) cookie=0x14, duration=473.458s, table=10, n_packets=0, n_bytes=0, idle_age=473, priority=5 actions=drop ubuntu@ubuntu-HP-Compaq-8200-Elite-SFF-PC:~/VCPE/SCF_app/sfc/vnfmgr/vnfmgr_odl$ =========================== Out put of "sudo ovs-ofctl dump-flows br-int" ================================================= Thanks in Advance With Best Regards Dhevendran Kulandaivel Tata Consultancy Services Limited Cell:- +919845439011 Mailto: [email protected] Website: http://www.tcs.com ____________________________________________ Experience certainty. IT Services Business Solutions Consulting ____________________________________________ From: Brady Allen Johnson <[email protected]> To: Dhevendran K <[email protected]> Cc: "[email protected]" <[email protected]>, "Eshappa K" <[email protected]>, Mani Mahalingam <[email protected]>, "Sujith Kumar K" <[email protected]>, Suresh Nagaraj <[email protected]>, Divya T V <[email protected]>, Sunil Desai <[email protected]> Date: 06/12/2017 02:46 PM Subject: Re: [sfc-dev] ODL Log Message while configuring the SFC Here is the OPNFV SFC gerrit patch with the config changes: https://gerrit.opnfv.org/gerrit/36001 Here is the output I get from OVS: $ sudo ovs-vsctl show e5cf1e83-a101-45d8-8cb7-7f096434b549 Manager "tcp:159.107.45.19:6640" is_connected: true Bridge br-int Controller "tcp:159.107.45.19:6653" is_connected: true Port "sff2-dp1" Interface "sff2-dp1" type: vxlan options: {dst_port="6633", exts=gpe, key=flow, remote_ip=flow} Port br-int Interface br-int type: internal ovs_version: "2.5.90" $ sudo ovs-ofctl -O OpenFlow13 dump-flows br-int OFPST_FLOW reply (OF1.3) (xid=0x2): cookie=0x14, duration=8.013s, table=0, n_packets=0, n_bytes=0, priority=5 actions=goto_table:1 cookie=0x14, duration=8.013s, table=1, n_packets=0, n_bytes=0, priority=250,nsp=4 actions=goto_table:4 cookie=0x14, duration=8.013s, table=1, n_packets=0, n_bytes=0, priority=250,nsp=8388612 actions=goto_table:4 cookie=0x14, duration=8.013s, table=1, n_packets=0, n_bytes=0, priority=5 actions=drop cookie=0x14, duration=8.013s, table=2, n_packets=0, n_bytes=0, priority=5 actions=goto_table:3 cookie=0x14, duration=8.013s, table=3, n_packets=0, n_bytes=0, priority=5 actions=goto_table:4 cookie=0x14, duration=8.013s, table=4, n_packets=0, n_bytes=0, priority=550,nsi=255,nsp=4 actions=load:0xc0a8010b->NXM_NX_TUN_IPV4_DST[],goto_table:10 cookie=0x14, duration=8.013s, table=4, n_packets=0, n_bytes=0, priority=550,nsi=254,nsp=4 actions=load:0xc0a8010c->NXM_NX_TUN_IPV4_DST[],goto_table:10 cookie=0x14, duration=8.013s, table=4, n_packets=0, n_bytes=0, priority=550,nsi=254,nsp=8388612 actions=load:0xc0a8010b->NXM_NX_TUN_IPV4_DST[],goto_table:10 cookie=0x14, duration=8.013s, table=4, n_packets=0, n_bytes=0, priority=550,nsi=255,nsp=8388612 actions=load:0xc0a8010c->NXM_NX_TUN_IPV4_DST[],goto_table:10 cookie=0x14, duration=8.013s, table=4, n_packets=0, n_bytes=0, priority=5 actions=goto_table:10 cookie=0xba5eba1100000102, duration=8.013s, table=10, n_packets=0, n_bytes=0, priority=660,nsi=253,nsp=4,nshc1=0 actions=load:0x4->NXM_NX_TUN_GPE_NP[],IN_PORT cookie=0xba5eba1100000102, duration=8.013s, table=10, n_packets=0, n_bytes=0, priority=660,nsi=253,nsp=8388612,nshc1=0 actions=load:0x4->NXM_NX_TUN_GPE_NP[],IN_PORT cookie=0xba5eba1100000101, duration=8.013s, table=10, n_packets=0, n_bytes=0, priority=655,nsi=254,nsp=4,in_port=1 actions=move:NXM_NX_NSH_MDTYPE[]->NXM_NX_NSH_MDTYPE[],move:NXM_NX_NSH_NP[]->NXM_NX_NSH_NP[],move:NXM_NX_NSH_C1[]->NXM_NX_NSH_C1[],move:NXM_NX_NSH_C2[]->NXM_NX_NSH_C2[],move:NXM_NX_NSH_C3[]->NXM_NX_NSH_C3[],move:NXM_NX_NSH_C4[]->NXM_NX_NSH_C4[],move:NXM_NX_TUN_ID[0..31]->NXM_NX_TUN_ID[0..31],load:0x4->NXM_NX_TUN_GPE_NP[],IN_PORT cookie=0xba5eba1100000103, duration=8.013s, table=10, n_packets=0, n_bytes=0, priority=655,nsi=253,nsp=4,in_port=1 actions=move:NXM_NX_NSH_MDTYPE[]->NXM_NX_NSH_MDTYPE[],move:NXM_NX_NSH_NP[]->NXM_NX_NSH_NP[],move:NXM_NX_NSI[]->NXM_NX_NSI[],move:NXM_NX_NSP[0..23]->NXM_NX_NSP[0..23],move:NXM_NX_NSH_C1[]->NXM_NX_TUN_IPV4_DST[],move:NXM_NX_NSH_C2[]->NXM_NX_TUN_ID[0..31],load:0x4->NXM_NX_TUN_GPE_NP[],IN_PORT cookie=0xba5eba1100000101, duration=8.013s, table=10, n_packets=0, n_bytes=0, priority=655,nsi=255,nsp=4,in_port=1 actions=move:NXM_NX_NSH_MDTYPE[]->NXM_NX_NSH_MDTYPE[],move:NXM_NX_NSH_NP[]->NXM_NX_NSH_NP[],move:NXM_NX_NSH_C1[]->NXM_NX_NSH_C1[],move:NXM_NX_NSH_C2[]->NXM_NX_NSH_C2[],move:NXM_NX_NSH_C3[]->NXM_NX_NSH_C3[],move:NXM_NX_NSH_C4[]->NXM_NX_NSH_C4[],move:NXM_NX_TUN_ID[0..31]->NXM_NX_TUN_ID[0..31],load:0x4->NXM_NX_TUN_GPE_NP[],IN_PORT cookie=0xba5eba1100000101, duration=8.013s, table=10, n_packets=0, n_bytes=0, priority=655,nsi=255,nsp=8388612,in_port=1 actions=move:NXM_NX_NSH_MDTYPE[]->NXM_NX_NSH_MDTYPE[],move:NXM_NX_NSH_NP[]->NXM_NX_NSH_NP[],move:NXM_NX_NSH_C1[]->NXM_NX_NSH_C1[],move:NXM_NX_NSH_C2[]->NXM_NX_NSH_C2[],move:NXM_NX_NSH_C3[]->NXM_NX_NSH_C3[],move:NXM_NX_NSH_C4[]->NXM_NX_NSH_C4[],move:NXM_NX_TUN_ID[0..31]->NXM_NX_TUN_ID[0..31],load:0x4->NXM_NX_TUN_GPE_NP[],IN_PORT cookie=0xba5eba1100000101, duration=8.013s, table=10, n_packets=0, n_bytes=0, priority=655,nsi=254,nsp=8388612,in_port=1 actions=move:NXM_NX_NSH_MDTYPE[]->NXM_NX_NSH_MDTYPE[],move:NXM_NX_NSH_NP[]->NXM_NX_NSH_NP[],move:NXM_NX_NSH_C1[]->NXM_NX_NSH_C1[],move:NXM_NX_NSH_C2[]->NXM_NX_NSH_C2[],move:NXM_NX_NSH_C3[]->NXM_NX_NSH_C3[],move:NXM_NX_NSH_C4[]->NXM_NX_NSH_C4[],move:NXM_NX_TUN_ID[0..31]->NXM_NX_TUN_ID[0..31],load:0x4->NXM_NX_TUN_GPE_NP[],IN_PORT cookie=0xba5eba1100000103, duration=8.013s, table=10, n_packets=0, n_bytes=0, priority=655,nsi=253,nsp=8388612,in_port=1 actions=move:NXM_NX_NSH_MDTYPE[]->NXM_NX_NSH_MDTYPE[],move:NXM_NX_NSH_NP[]->NXM_NX_NSH_NP[],move:NXM_NX_NSI[]->NXM_NX_NSI[],move:NXM_NX_NSP[0..23]->NXM_NX_NSP[0..23],move:NXM_NX_NSH_C1[]->NXM_NX_TUN_IPV4_DST[],move:NXM_NX_NSH_C2[]->NXM_NX_TUN_ID[0..31],load:0x4->NXM_NX_TUN_GPE_NP[],IN_PORT cookie=0xba5eba1100000101, duration=8.013s, table=10, n_packets=0, n_bytes=0, priority=650,nsi=254,nsp=4 actions=move:NXM_NX_NSH_MDTYPE[]->NXM_NX_NSH_MDTYPE[],move:NXM_NX_NSH_NP[]->NXM_NX_NSH_NP[],move:NXM_NX_NSH_C1[]->NXM_NX_NSH_C1[],move:NXM_NX_NSH_C2[]->NXM_NX_NSH_C2[],move:NXM_NX_NSH_C3[]->NXM_NX_NSH_C3[],move:NXM_NX_NSH_C4[]->NXM_NX_NSH_C4[],move:NXM_NX_TUN_ID[0..31]->NXM_NX_TUN_ID[0..31],load:0x4->NXM_NX_TUN_GPE_NP[],output:1 cookie=0xba5eba1100000103, duration=8.013s, table=10, n_packets=0, n_bytes=0, priority=650,nsi=253,nsp=4 actions=move:NXM_NX_NSH_MDTYPE[]->NXM_NX_NSH_MDTYPE[],move:NXM_NX_NSH_NP[]->NXM_NX_NSH_NP[],move:NXM_NX_NSI[]->NXM_NX_NSI[],move:NXM_NX_NSP[0..23]->NXM_NX_NSP[0..23],move:NXM_NX_NSH_C1[]->NXM_NX_TUN_IPV4_DST[],move:NXM_NX_NSH_C2[]->NXM_NX_TUN_ID[0..31],load:0x4->NXM_NX_TUN_GPE_NP[],output:1 cookie=0xba5eba1100000101, duration=8.013s, table=10, n_packets=0, n_bytes=0, priority=650,nsi=255,nsp=4 actions=move:NXM_NX_NSH_MDTYPE[]->NXM_NX_NSH_MDTYPE[],move:NXM_NX_NSH_NP[]->NXM_NX_NSH_NP[],move:NXM_NX_NSH_C1[]->NXM_NX_NSH_C1[],move:NXM_NX_NSH_C2[]->NXM_NX_NSH_C2[],move:NXM_NX_NSH_C3[]->NXM_NX_NSH_C3[],move:NXM_NX_NSH_C4[]->NXM_NX_NSH_C4[],move:NXM_NX_TUN_ID[0..31]->NXM_NX_TUN_ID[0..31],load:0x4->NXM_NX_TUN_GPE_NP[],output:1 cookie=0xba5eba1100000101, duration=8.013s, table=10, n_packets=0, n_bytes=0, priority=650,nsi=255,nsp=8388612 actions=move:NXM_NX_NSH_MDTYPE[]->NXM_NX_NSH_MDTYPE[],move:NXM_NX_NSH_NP[]->NXM_NX_NSH_NP[],move:NXM_NX_NSH_C1[]->NXM_NX_NSH_C1[],move:NXM_NX_NSH_C2[]->NXM_NX_NSH_C2[],move:NXM_NX_NSH_C3[]->NXM_NX_NSH_C3[],move:NXM_NX_NSH_C4[]->NXM_NX_NSH_C4[],move:NXM_NX_TUN_ID[0..31]->NXM_NX_TUN_ID[0..31],load:0x4->NXM_NX_TUN_GPE_NP[],output:1 cookie=0xba5eba1100000101, duration=8.013s, table=10, n_packets=0, n_bytes=0, priority=650,nsi=254,nsp=8388612 actions=move:NXM_NX_NSH_MDTYPE[]->NXM_NX_NSH_MDTYPE[],move:NXM_NX_NSH_NP[]->NXM_NX_NSH_NP[],move:NXM_NX_NSH_C1[]->NXM_NX_NSH_C1[],move:NXM_NX_NSH_C2[]->NXM_NX_NSH_C2[],move:NXM_NX_NSH_C3[]->NXM_NX_NSH_C3[],move:NXM_NX_NSH_C4[]->NXM_NX_NSH_C4[],move:NXM_NX_TUN_ID[0..31]->NXM_NX_TUN_ID[0..31],load:0x4->NXM_NX_TUN_GPE_NP[],output:1 cookie=0xba5eba1100000103, duration=8.013s, table=10, n_packets=0, n_bytes=0, priority=650,nsi=253,nsp=8388612 actions=move:NXM_NX_NSH_MDTYPE[]->NXM_NX_NSH_MDTYPE[],move:NXM_NX_NSH_NP[]->NXM_NX_NSH_NP[],move:NXM_NX_NSI[]->NXM_NX_NSI[],move:NXM_NX_NSP[0..23]->NXM_NX_NSP[0..23],move:NXM_NX_NSH_C1[]->NXM_NX_TUN_IPV4_DST[],move:NXM_NX_NSH_C2[]->NXM_NX_TUN_ID[0..31],load:0x4->NXM_NX_TUN_GPE_NP[],output:1 cookie=0x14, duration=8.013s, table=10, n_packets=0, n_bytes=0, priority=5 actions=drop Regards, Brady From: Dhevendran K <[email protected]> Sent: Monday, June 12, 2017 10:23 AM To: Brady Allen Johnson Cc: [email protected]; Eshappa K; Mani Mahalingam; [email protected]; Sujith Kumar K; Suresh Nagaraj; Divya T V; Sunil Desai Subject: Re: [sfc-dev] ODL Log Message while configuring the SFC Hi Brady Thanks for your answer. Let me try out these examples and get back to you With Best Regards Dhevendran Kulandaivel Tata Consultancy Services Limited Cell:- +919845439011 Mailto: [email protected] Website: http://www.tcs.com ____________________________________________ Experience certainty. IT Services Business Solutions Consulting ____________________________________________ Tata Consultancy Services | Technology, Digital Solutions, Consulting www.tcs.com Global Leader in IT Services, Consulting, Technology and Digital Solutions with a Large Network of Innovation & Delivery Centers. From: Brady Allen Johnson <[email protected]> To: Dhevendran K <[email protected]>, "[email protected]" <[email protected]> Date: 06/12/2017 12:38 PM Subject: Re: [sfc-dev] ODL Log Message while configuring the SFC Dhevendran, I have several answers from your internal discussions with Manuel. First of all, while using option 7 of the vnfmgr python script, you can ignore the messages related to "[RestConf-SFselect-HttpPut.json] does not exist". SFC uses SF selection algorithms when multiple SFs of the same type exist when creating a chain, and this REST json file selects which algorithm to use. But, if you dont manually specify it via REST, internally the random algorithm will be chosen by default. Regarding your question about the SF "rest-uri", that's an optional configuration that can be removed. There is a legacy SFC script called sfc-agent that received ODL southbound REST SFC configuration. The sfc-agent is no longer used. I see from your SF JSON that there are some deprecated fields in the configuration with respect to the latest version of ODL, such as the "nsh-aware" which has been moved to the SF-type model. I'll submit a patch now to the OPNFV SFC repo to update the config to the latest version of ODL, namely Carbon. Also, if you clone the ODL SFC repo, there are postman SFC examples that are updated to the latest in <sfc-repo>/resources/configuration-examples. I hope I covered all of your issues for now, but please let me know if you need any more help. Regards, Brady From: [email protected] <[email protected]> on behalf of Dhevendran K <[email protected]> Sent: Friday, June 9, 2017 11:54 AM To: [email protected] Subject: [sfc-dev] ODL Log Message while configuring the SFC Hi All I am getting the the following error message while configuring ODL SFC feature by referring [1] As per the instructions provided , the following are completed 1. OpenDayLight (i.e. distribution-karaf-0.5.3-Boron-SR3.tar.gz ) is installed and required features are installed 2. As per the instructions [1], the topology for SFC configuration is simulated using mininet command "sudo mn --topo linear,4 --mac --controller=remote,ip=10.132.206.138,port=6633 --switch ovsk,protocals=OpenFlow13" 3. SFs are created as per the instructions in [1] 4. When I am trying to create the SFFs, the following ODL Log Message are observed ============================= ODL Log Message ====================== 2017-06-09 14:50:46,815 | INFO | on-dispatcher-44 | SfcSffToOvsMappingAPI | 358 - org.opendaylight.sfc.ovs - 0.3.3.Boron-SR3 | Cannot build OvsdbBridgeAugmentation. Missing OVS Bridge augmentation on SFF SffName [_value=sff1] 2017-06-09 14:50:46,817 | INFO | on-dispatcher-44 | SfcSffToOvsMappingAPI | 358 - org.opendaylight.sfc.ovs - 0.3.3.Boron-SR3 | Cannot build OvsdbBridgeAugmentation. Missing OVS Bridge augmentation on SFF SffName [_value=sff2] ============================= ODL Log Message ====================== Quary-1 : Is there anything missed here ? [1] : http://docs.opendaylight.org/en/stable-boron/user-guide/service-function-chaining.html Service Function Chaining ? OpenDaylight Documentation ... docs.opendaylight.org OpenDaylight Service Function Chaining (SFC) Overview¶ OpenDaylight Service Function Chaining (SFC) provides the ability to define an ordered list of a network ... Service Function Chaining ? OpenDaylight Documentation ... docs.opendaylight.org OpenDaylight Service Function Chaining (SFC) Overview¶ OpenDaylight Service Function Chaining (SFC) provides the ability to define an ordered list of a network ... Thanks in Advance With Best Regards Dhevendran Kulandaivel Tata Consultancy Services Limited Cell:- +919845439011 Mailto: [email protected] Website: http://www.tcs.com ____________________________________________ Experience certainty. IT Services Business Solutions Consulting ____________________________________________ Tata Consultancy Services | Technology, Digital Solutions, Consulting www.tcs.com Global Leader in IT Services, Consulting, Technology and Digital Solutions with a Large Network of Innovation & Delivery Centers. =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you
_______________________________________________ sfc-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/sfc-dev
