Hi Srikanth， Yes，NSH_SFC has implemented NSH-proxy. You could use that. Please refer to NSH_SFC wiki/design for details.
-Hongjun Send from iPhone > 在 2017年7月6日，16:54，Srikanth Lingala <srikanth.ling...@nxp.com> 写道： > > Thanks Hongjun, for your reply. I will ask in the community. > > But, before that I have a doubt. > Actually, I want to use VPP NSH SFC plugin in the NSH unaware VM to replace > vxlan_tool.py. Because, vxlan_tool.py is only used when VM has normal NICs. > In the case of DPDK VM, which does have only DPDK interfaces, vxlan_tool.py > can’t be used, as it requires normal Ethernet interface to work with NSH > packets and send back to SFF. > Is there any alternative to vxlan_tool.py in NSH unaware VM (DPDK based) to > make NSH aware VM? > I heard that ODL also supports SFC proxy to make NSH aware. > Can you please provide me some information on that? > > Thanks & Regards, > Srikanth. > > From: Ni, Hongjun [mailto:hongjun...@intel.com] > Sent: Thursday, July 06, 2017 2:08 PM > To: Srikanth Lingala <srikanth.ling...@nxp.com> > Subject: RE: Compiling NSH_SFC 17.01 plugin for VPP > > Hi Srikanth, > > I have not run into this issue before. > > I suggest you ask for help from VPP community. > > Thanks, > Hongjun > > From: Srikanth Lingala [mailto:srikanth.ling...@nxp.com] > Sent: Thursday, July 6, 2017 2:14 PM > To: Ni, Hongjun <hongjun...@intel.com> > Subject: RE: Compiling NSH_SFC 17.01 plugin for VPP > > Hi Hngjun, > As per your suggestion, I am trying to compile VPP 17.04. > But, during compilation, I got an error. Following is the error, which is > part of compilation logs: > > make[5]: Leaving directory > '/root/srikanth/17.04/vpp-ls1/build-root/build-dpaa-aarch64/vpp/vpp-api/python' > make[4]: Leaving directory > '/root/srikanth/17.04/vpp-ls1/build-root/build-dpaa-aarch64/vpp/vpp-api/python' > Making install in vpp-api/java > make[4]: Entering directory > '/root/srikanth/17.04/vpp-ls1/build-root/build-dpaa-aarch64/vpp/vpp-api/java' > make install-am > make[5]: Entering directory > '/root/srikanth/17.04/vpp-ls1/build-root/build-dpaa-aarch64/vpp/vpp-api/java' > make[6]: Entering directory > '/root/srikanth/17.04/vpp-ls1/build-root/build-dpaa-aarch64/vpp/vpp-api/java' > /bin/mkdir -p > '/root/srikanth/17.04/vpp-ls1/build-root/install-dpaa-aarch64/vpp/lib' > /bin/bash ../../libtool --quiet --mode=install /usr/bin/install -c > libjvpp_common.la > '/root/srikanth/17.04/vpp-ls1/build-root/install-dpaa-aarch64/vpp/lib' > /bin/mkdir -p > '/root/srikanth/17.04/vpp-ls1/build-root/install-dpaa-aarch64/vpp/include' > /bin/mkdir -p > '/root/srikanth/17.04/vpp-ls1/build-root/install-dpaa-aarch64/vpp/share/java' > /usr/bin/install -c -m 644 jvpp-registry-17.04.2.jar jvpp-core-17.04.2.jar > jvpp-acl-17.04.2.jar jvpp-snat-17.04.2.jar jvpp-ioamtrace-17.04.2.jar > jvpp-ioampot-17.04.2.jar jvpp-ioamexport-17.04.2.jar > '/root/srikanth/17.04/vpp-ls1/build-root/install-dpaa-aarch64/vpp/share/java' > /bin/mkdir -p > '/root/srikanth/17.04/vpp-ls1/build-root/install-dpaa-aarch64/vpp/include/jvpp-common' > /usr/bin/install -c -m 644 > /root/srikanth/17.04/vpp-ls1/build-data/../src/vpp-api/java/jvpp-common/jvpp_common.h > > '/root/srikanth/17.04/vpp-ls1/build-root/install-dpaa-aarch64/vpp/include/jvpp-common' > libtool: warning: remember to run 'libtool --finish /none' > make[6]: Leaving directory > '/root/srikanth/17.04/vpp-ls1/build-root/build-dpaa-aarch64/vpp/vpp-api/java' > make[5]: Leaving directory > '/root/srikanth/17.04/vpp-ls1/build-root/build-dpaa-aarch64/vpp/vpp-api/java' > make[4]: Leaving directory > '/root/srikanth/17.04/vpp-ls1/build-root/build-dpaa-aarch64/vpp/vpp-api/java' > make[3]: Leaving directory > '/root/srikanth/17.04/vpp-ls1/build-root/build-dpaa-aarch64/vpp' > make[2]: Leaving directory > '/root/srikanth/17.04/vpp-ls1/build-root/build-dpaa-aarch64/vpp' > @@@@ Arch for platform 'dpaa' is aarch64 @@@@ > @@@@ Finding source for vlib @@@@ > @@@@ Package vlib not found with path /root/srikanth/17.04/vpp-ls1 @@@@ > Makefile:780: recipe for target 'vlib-find-source' failed > make[1]: *** [vlib-find-source] Error 1 > make[1]: Leaving directory '/root/srikanth/17.04/vpp-ls1/build-root' > /root/srikanth/17.04/vpp-ls1/build-data/platforms.mk:99: recipe for target > 'install-rpm' failed > make: *** [install-rpm] Error 1 > > Do you have any clue to debug further? > > Regards, > Srikanth. > > From: Ni, Hongjun [mailto:hongjun...@intel.com] > Sent: Wednesday, July 05, 2017 9:33 AM > To: Srikanth Lingala <srikanth.ling...@nxp.com>; nsh_sfc-...@lists.fd.io; > vpp-dev@lists.fd.io > Subject: RE: Compiling NSH_SFC 17.01 plugin for VPP > > Hi Srikanth, > > Please use VPP 17.04 release and NSH 17.04 release, which contains majority > NSH features and new building system. > > For building NSH_SFC 17.04, using below commands: > cd $Path/nsh_sfc/nsh-plugin/ > rm -fr build > ./build.sh > > I just compiled them and it worked well. > > Regards, > Hongjun > > From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On > Behalf Of Srikanth Lingala > Sent: Tuesday, July 4, 2017 7:35 PM > To: nsh_sfc-...@lists.fd.io; vpp-dev@lists.fd.io > Subject: [vpp-dev] Compiling NSH_SFC 17.01 plugin for VPP > > Hi, > I am trying to compile NSH SFC plugin 17.01 for VPP. > I downloaded the source using the following command: > > #> git clone https://gerrit.fd.io/r/nsh_sfc -b stable/1701 > > I execute the below commands, for compilation: > > #> autoreconf -i -f > #> ./configure > #> make > make all-recursive > make[1]: Entering directory '/root/vpp-ls1-working-code/plugins/nsh-plugin' > Making all in java > make[2]: Entering directory > '/root/vpp-ls1-working-code/plugins/nsh-plugin/java' > dir=`pwd`; \ > mkdir -p jvpp/src/main/java/io/fd/nsh_sfc/jvpp; \ > cd jvpp/src/main/java/io/fd/nsh_sfc/jvpp; \ > mkdir -p dto future callfacade callback notification test; \ > jvpp_gen.py -i ${dir}/nsh.api.json --plugin_name nsh; \ > cd -; \ > mv -f jvpp/src/main/java/io/fd/nsh_sfc/jvpp/jvpp_nsh_gen.h > jvpp/jvpp_nsh_gen.h; \ > cp ./pom.xml jvpp/; \ > cp ./jvpp/test/*.java jvpp/src/main/java/io/fd/nsh_sfc/jvpp/test/; > \ > cd jvpp; \ > mvn ${MAVEN_SETTINGS_OPTIONS} -v; \ > mvn ${MAVEN_SETTINGS_OPTIONS} clean process-classes; > Generating Java API for > ['/root/vpp-ls1-working-code/plugins/nsh-plugin/java/nsh.api.json'] > inputfiles ['/root/vpp-ls1-working-code/plugins/nsh-plugin/java/nsh.api.json'] > plugin_name nsh > Skipping custom types generation > (['/root/vpp-ls1-working-code/plugins/nsh-plugin/java/nsh.api.json'] does not > define custom types). > Generating DTOs > Generating JVpp > Generating Callback interfaces > Generating Notification interfaces and implementation > Generating jvpp C > Generating JVpp future facade > Generating JVpp callback facade > Java API for > ['/root/vpp-ls1-working-code/plugins/nsh-plugin/java/nsh.api.json'] generated > successfully > /root/vpp-ls1-working-code/plugins/nsh-plugin/java > Apache Maven 3.3.9 > Maven home: /usr/share/maven > Java version: 1.8.0_131, vendor: Oracle Corporation > Java home: /usr/lib/jvm/java-8-openjdk-arm64/jre > Default locale: en_US, platform encoding: ANSI_X3.4-1968 > OS name: "linux", version: "4.1.35-rt41_1703", arch: "aarch64", family: "unix" > [INFO] Scanning for projects... > [INFO] > [INFO] > ------------------------------------------------------------------------ > [INFO] Building nsh-sfc 17.01-SNAPSHOT > [INFO] > ------------------------------------------------------------------------ > Downloading: > https://repo.maven.apache.org/maven2/io/fd/vpp/jvpp-registry/17.01/jvpp-registry-17.01.pom > [WARNING] The POM for io.fd.vpp:jvpp-registry:jar:17.01 is missing, no > dependency information available > Downloading: > https://repo.maven.apache.org/maven2/io/fd/vpp/jvpp-registry/17.01/jvpp-registry-17.01.jar > [INFO] > ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] > ------------------------------------------------------------------------ > [INFO] Total time: 20.420 s > [INFO] Finished at: 2017-07-04T16:29:34+05:30 > [INFO] Final Memory: 11M/178M > [INFO] > ------------------------------------------------------------------------ > [ERROR] Failed to execute goal on project nsh-sfc: Could not resolve > dependencies for project io.fd.nsh_sfc:nsh-sfc:jar:17.01-SNAPSHOT: Could not > find artifact io.fd.vpp:jvpp-registry:jar:17.01 in central > (https://repo.maven.apache.org/maven2) -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e > switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please > read the following articles: > [ERROR] [Help 1] > http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException > Makefile:990: recipe for target 'jvpp/io_fd_vpp_jvpp_nsh_JVppNshImpl.h' failed > make[2]: *** [jvpp/io_fd_vpp_jvpp_nsh_JVppNshImpl.h] Error 1 > make[2]: Leaving directory > '/root/vpp-ls1-working-code/plugins/nsh-plugin/java' > Makefile:612: recipe for target 'all-recursive' failed > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory '/root/vpp-ls1-working-code/plugins/nsh-plugin' > Makefile:433: recipe for target 'all' failed > make: *** [all] Error 2 > > When I want download the file ‘jvpp-registry-17.01.pom’ manually from the > below location: > https://repo.maven.apache.org/maven2/io/fd/vpp/jvpp-registry/17.01/, the link > is NOT FOUND. > Can anyone please help me to compile NSH SFC plugin? > > > Regards, > Srikanth. > _______________________________________________ > vpp-dev mailing list > vpp-dev@lists.fd.io > https://lists.fd.io/mailman/listinfo/vpp-dev
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
