date:20170704

Re: [vpp-dev] A query regarding fib_path_ext_init

2017-07-04 Thread Neale Ranns (nranns)

Hi nagp,

My intention there was to ‘pass ownership’ of the label stack to the extension. 
The caller, the owner of the rpath, should not then free the label stack. This 
saves the allocation of a new vector and memcpy.

Regards,
neale

From:  on behalf of Nagaprabhanjan Bellari 

Date: Monday, 3 July 2017 at 14:38
To: vpp-dev 
Subject: [vpp-dev] A query regarding fib_path_ext_init

Hi,
I have  small query regarding fib_path_ext_init which takes an rpath - of type 
fib_route_path_t, potentially containing a vector of frp_label_stack.
When we add routes, the API handler stacks rpath->frp_label_stack with one or 
more labels, and in fib_path_ext_init, we have:

path_ext->fpe_path = *rpath;
One side effect, IMHO, of copying rpath structure as is will be copying the 
frp_label_stack pointer as well. So, when the caller is done and frees up the 
rpath (including frp_label_stack), then wouldn't 
path_ext->fpe_path.frp_label_stack point to garbage?
Please correct me if I am wrong.
Thanks,
-nagp
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] A query regarding fib_path_ext_init

2017-07-04 Thread Nagaprabhanjan Bellari

I see thanks! the api add_del_route_t_handler too, I realize, does not free
the label_stack.

Thanks,
-nagp

On Tue, Jul 4, 2017 at 1:54 PM, Neale Ranns (nranns) 
wrote:

> Hi nagp,
>
>
>
> My intention there was to ‘pass ownership’ of the label stack to the
> extension. The caller, the owner of the rpath, should not then free the
> label stack. This saves the allocation of a new vector and memcpy.
>
>
>
> Regards,
>
> neale
>
>
>
> *From: * on behalf of Nagaprabhanjan Bellari
> 
> *Date: *Monday, 3 July 2017 at 14:38
> *To: *vpp-dev 
> *Subject: *[vpp-dev] A query regarding fib_path_ext_init
>
>
>
> Hi,
>
> I have  small query regarding fib_path_ext_init which takes an rpath - of
> type fib_route_path_t, potentially containing a vector of frp_label_stack.
>
> When we add routes, the API handler stacks rpath->frp_label_stack with one
> or more labels, and in fib_path_ext_init, we have:
>
> path_ext->fpe_path = *rpath;
>
> One side effect, IMHO, of copying rpath structure as is will be copying
> the frp_label_stack pointer as well. So, when the caller is done and frees
> up the rpath (including frp_label_stack), then wouldn't
> path_ext->fpe_path.frp_label_stack point to garbage?
>
> Please correct me if I am wrong.
>
> Thanks,
>
> -nagp
>
>
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] how can i include dpdk.h header file in vnet?

2017-07-04 Thread Samuel S

Hi
I want to include header file dpdk.h from src/plugin/dpdk/device to
src/vnet/interface_api.c, but when i compile vpp with build.sh, An error
occurs in the compilation process.

/root/vpp/build-data/../src/vnet/interface_api.c:76:35: fatal error:
dpdk/dpdk.h: No such file or directory
#include 
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

[vpp-dev] Compiling NSH_SFC 17.01 plugin for VPP

2017-07-04 Thread Srikanth Lingala

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

Re: [vpp-dev] how can i include dpdk.h header file in vnet?

2017-07-04 Thread Dave Barach (dbarach)

Please do not introduce dpdk plugin dependencies into interface_api.c. We’ve 
moved all dpdk dependencies to the dpdk plugin, on purpose.

What are you trying to do?

Thanks… Dave

From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On 
Behalf Of Samuel S
Sent: Tuesday, July 4, 2017 7:15 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] how can i include dpdk.h header file in vnet?

Hi
I want to include header file dpdk.h from src/plugin/dpdk/device to 
src/vnet/interface_api.c, but when i compile vpp with build.sh, An error occurs 
in the compilation process.

/root/vpp/build-data/../src/vnet/interface_api.c:76:35: fatal error: 
dpdk/dpdk.h: No such file or directory
#include 
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] A few questions regarding mcast fib

2017-07-04 Thread Nagaprabhanjan Bellari

Hi Neale,

I have added a mpls local-label 501 with eos 1 to lookup in multicast table
of table_id 3.

Basically, I am setting FIB_ENTRY_FLAG_MULTICAST while adding the mpls
route. It is displayed as follows in "show mpls fib":
--
501:eos/21 fib:0 index:60 locks:2
  src:API  refs:1 flags:multicast,
index:77 locks:12 flags:shared, uPRF-list:61 len:0 itfs:[]
  index:121 pl-index:77 ipv4 weight=1 deag:  oper-flags:resolved,
   [@0]: dst-address,unicast lookup in ipv4-VRF:1

 forwarding:   mpls-eos-chain
  [@0]: dpo-replicate: [index:16 buckets:1 to:[0:0]]
[0] [@1]: mpls-disposition:[0]:[ip4]
[@1]: dst-address,unicast lookup in ipv4-VRF:1
--

The flags show multicast, but the destination address has lookup in unicast
table. Why is that so? Am I missing something?

Thanks,
-nagp

On Fri, Jun 30, 2017 at 7:55 AM, Nagaprabhanjan Bellari <
nagp.li...@gmail.com> wrote:

> Got it, thanks!
>
> On Thu, Jun 29, 2017 at 10:56 PM, Neale Ranns (nranns) 
> wrote:
>
>> Hi,
>>
>>
>>
>> No. If we did allow that then every receiver on that interface would
>> receive packets encapsulated with that label, which is equivalent to the
>> label being upstream assigned and probably not what you want. An MPLS
>> tunnel can itself be P2MP so the same argument applies.
>>
>> If you have one or more unicast MPLS tunnels in the multicast replication
>> list, then you can create each MPLS tunnel with multiple output labels.
>>
>>
>>
>> Hth,
>>
>> neale
>>
>>
>>
>> *From: *Nagaprabhanjan Bellari 
>> *Date: *Thursday, 29 June 2017 at 13:01
>>
>> *To: *"Neale Ranns (nranns)" 
>> *Cc: *vpp-dev 
>> *Subject: *Re: [vpp-dev] A few questions regarding mcast fib
>>
>>
>>
>> Hi Neale,
>>
>> For the IP-to-MPLS case, can we specify another label in
>> rpath.frp_label_stack (the vc label) in addition to specifying the
>> sw_if_index of an MPLS tunnel (which will carry the tunnel label)?
>>
>> Thanks,
>>
>> -nagp
>>
>>
>>
>> On Tue, Jun 13, 2017 at 5:28 PM, Neale Ranns (nranns) 
>> wrote:
>>
>>
>>
>> Quite a few of the multicast related options are not available via the
>> CLI. I don’t use the debug CLI much for testing, it’s all done in the
>> python UT through the API. If you can see your way to adding CLI options,
>> I’d be grateful.
>>
>>
>>
>> Thanks,
>>
>> neale
>>
>>
>>
>> *From: *Nagaprabhanjan Bellari 
>> *Date: *Tuesday, 13 June 2017 at 12:37
>> *To: *"Neale Ranns (nranns)" 
>> *Cc: *vpp-dev 
>> *Subject: *Re: [vpp-dev] A few questions regarding mcast fib
>>
>>
>>
>> One question: I dont see a "multicast" option with the "mpls local-label"
>> command with latest VPP - am I missing something?
>>
>> Thanks,
>>
>> -nagp
>>
>>
>>
>> On Tue, Jun 13, 2017 at 4:40 PM, Nagaprabhanjan Bellari <
>> nagp.li...@gmail.com> wrote:
>>
>> Thank you! As always, a great answer!
>>
>> This itself is good enough a documentation to get going. :-)
>>
>> -nagp
>>
>>
>>
>> On Tue, Jun 13, 2017 at 4:34 PM, Neale Ranns (nranns) 
>> wrote:
>>
>> Hi nagp,
>>
>>
>>
>> VPP does support those scenarios. I’ve not written any documentation
>> sadly, so I’ll write some instructions here… When I wrote the mfib/mpls
>> code I did little testing via the debug CLI, so some of the options below
>> are not be available via the CLI, I’ve put those options is []. I’ll be
>> cheeky and leave the implementation as an exercise to the reader…. but see
>> test_mpls.py and the test_mcast* functions therein for the various head,
>> midpoint and tail programming via the API. There are also examples of how
>> to setup the fib_route_path_t for each scenario in [m]fib_test.c.
>>
>>
>>
>> IP-to-IP:
>>
>>
>>
>> Adding routes to the mfib, and adding replications for those routes, is
>> similar to adding ECMP paths to routes in the unicast-fib (they even share
>> the sme fib_path[_list] code).
>>
>> The prefix in the mFIB can be:
>>
>> 1)(*,G/m)
>>
>> ip mroute add 232.1.0.0/16 via Eth0 Forward
>>
>> 2)   (*,G)
>>
>> ip mroute add 232.1.1.1 via Eth0 Forward
>>
>> 3)   (S,G)
>>
>>ip mroute add 1.1.1.1 239.1.1.1 via Eth0 Forward
>>
>>
>>
>> adding more replications is achieved by adding more paths:
>>
>> ip mroute add 1.1.1.1 239.1.1.1 via Eth1 Forward
>>
>> ip mroute add 1.1.1.1 239.1.1.1 via Eth2 Forward
>>
>> ip mroute add 1.1.1.1 239.1.1.1 via Eth3 Forward
>>
>>
>>
>> You’ll note the path is “attached”, i.e. only the interface is given and
>> not the next-hop. For mcast routes this is the expected case. The path will
>> resolve via the special multicast adjacency on the interface, which will
>> perform the MAC address fixup at switch time. If you want to specify a
>> next-hop in the path, and so have a unicast MAC address applied, then
>> you’ll need: https://gerrit.fd.io/r/#/c/6974/
>>
>>
>>
>> The flag ‘Forward’ is required to specify this is as a replication, i.e.
>> a path used for forwarding. This distinction is required because for
>> multicast one must also specify the RPF constraints. RPF can be specified
>> in several ways:
>>
>> 1)

Re: [vpp-dev] A few questions regarding mcast fib

2017-07-04 Thread Neale Ranns (nranns)

Hi,

The lookup DPO the route’s path links to needs to be created with:
  lookup_dpo_add_or_lock_w_fib_index(fib_index,
   DPO_PROTO_IP4,
   LOOKUP_MULTICAST,   
Etc…);

This is done in fib_path_resolve if the path is flagged as RPF_ID, which yours 
is not…

/neale

From: Nagaprabhanjan Bellari 
Date: Tuesday, 4 July 2017 at 14:18
To: "Neale Ranns (nranns)" 
Cc: vpp-dev 
Subject: Re: [vpp-dev] A few questions regarding mcast fib

Hi Neale,
I have added a mpls local-label 501 with eos 1 to lookup in multicast table of 
table_id 3.
Basically, I am setting FIB_ENTRY_FLAG_MULTICAST while adding the mpls route. 
It is displayed as follows in "show mpls fib":
--
501:eos/21 fib:0 index:60 locks:2
  src:API  refs:1 flags:multicast,
index:77 locks:12 flags:shared, uPRF-list:61 len:0 itfs:[]
  index:121 pl-index:77 ipv4 weight=1 deag:  oper-flags:resolved,
   [@0]: dst-address,unicast lookup in ipv4-VRF:1

 forwarding:   mpls-eos-chain
  [@0]: dpo-replicate: [index:16 buckets:1 to:[0:0]]
[0] [@1]: mpls-disposition:[0]:[ip4]
[@1]: dst-address,unicast lookup in ipv4-VRF:1
--
The flags show multicast, but the destination address has lookup in unicast 
table. Why is that so? Am I missing something?
Thanks,
-nagp

On Fri, Jun 30, 2017 at 7:55 AM, Nagaprabhanjan Bellari 
mailto:nagp.li...@gmail.com>> wrote:
Got it, thanks!

On Thu, Jun 29, 2017 at 10:56 PM, Neale Ranns (nranns) 
mailto:nra...@cisco.com>> wrote:
Hi,

No. If we did allow that then every receiver on that interface would receive 
packets encapsulated with that label, which is equivalent to the label being 
upstream assigned and probably not what you want. An MPLS tunnel can itself be 
P2MP so the same argument applies.
If you have one or more unicast MPLS tunnels in the multicast replication list, 
then you can create each MPLS tunnel with multiple output labels.

Hth,
neale

From: Nagaprabhanjan Bellari mailto:nagp.li...@gmail.com>>
Date: Thursday, 29 June 2017 at 13:01

To: "Neale Ranns (nranns)" mailto:nra...@cisco.com>>
Cc: vpp-dev mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] A few questions regarding mcast fib

Hi Neale,
For the IP-to-MPLS case, can we specify another label in rpath.frp_label_stack 
(the vc label) in addition to specifying the sw_if_index of an MPLS tunnel 
(which will carry the tunnel label)?
Thanks,
-nagp

On Tue, Jun 13, 2017 at 5:28 PM, Neale Ranns (nranns) 
mailto:nra...@cisco.com>> wrote:

Quite a few of the multicast related options are not available via the CLI. I 
don’t use the debug CLI much for testing, it’s all done in the python UT 
through the API. If you can see your way to adding CLI options, I’d be grateful.

Thanks,
neale

From: Nagaprabhanjan Bellari mailto:nagp.li...@gmail.com>>
Date: Tuesday, 13 June 2017 at 12:37
To: "Neale Ranns (nranns)" mailto:nra...@cisco.com>>
Cc: vpp-dev mailto:vpp-dev@lists.fd.io>>
Subject: Re: [vpp-dev] A few questions regarding mcast fib

One question: I dont see a "multicast" option with the "mpls local-label" 
command with latest VPP - am I missing something?
Thanks,
-nagp

On Tue, Jun 13, 2017 at 4:40 PM, Nagaprabhanjan Bellari 
mailto:nagp.li...@gmail.com>> wrote:
Thank you! As always, a great answer!
This itself is good enough a documentation to get going. :-)
-nagp

On Tue, Jun 13, 2017 at 4:34 PM, Neale Ranns (nranns) 
mailto:nra...@cisco.com>> wrote:
Hi nagp,

VPP does support those scenarios. I’ve not written any documentation sadly, so 
I’ll write some instructions here… When I wrote the mfib/mpls code I did little 
testing via the debug CLI, so some of the options below are not be available 
via the CLI, I’ve put those options is []. I’ll be cheeky and leave the 
implementation as an exercise to the reader…. but see test_mpls.py and the 
test_mcast* functions therein for the various head, midpoint and tail 
programming via the API. There are also examples of how to setup the 
fib_route_path_t for each scenario in [m]fib_test.c.

IP-to-IP:

Adding routes to the mfib, and adding replications for those routes, is similar 
to adding ECMP paths to routes in the unicast-fib (they even share the sme 
fib_path[_list] code).
The prefix in the mFIB can be:

1)(*,G/m)
ip mroute add 232.1.0.0/16 via Eth0 Forward

2)   (*,G)

ip mroute add 232.1.1.1 via Eth0 Forward

3)   (S,G)

   ip mroute add 1.1.1.1 239.1.1.1 via Eth0 Forward

adding more replications is achieved by adding more paths:

ip mroute add 1.1.1.1 239.1.1.1 via Eth1 Forward

ip mroute add 1.1.1.1 239.1.1.1 via Eth2 Forward

ip mroute add 1.1.1.1 239.1.1.1 via Eth3 Forward

You’ll note the path is “attached”, i.e. only the interface is given and not 
the next-hop. For mcast routes this is the expected case. The path will resolve 
via the special multicast adjacency on the interface, which will perform the 
MAC address fixup at switch

[vpp-dev] Compilation error: NSH SFC VPP plugin

2017-07-04 Thread Srikanth Lingala

Hi Hongjun,
I am trying to compile NSH SFC plugin (17.01) for VPP. While compiling, I am 
getting the following error for 'nsh_plugin' compilation. But, I can see that a 
JIRA (https://jira.fd.io/browse/NSHSFC-18?gerritIssueType=IssueOnly ) ticket is 
generated on the same issue. It's resolved by you. Can you please let me know, 
what could be the issue. BTW, I tried both 17.01 and 17.04, I am getting the 
same error.

[INFO] Scanning for projects...
[INFO]
[INFO] 
[INFO] Building nsh-sfc 17.04
[INFO] 
Downloading: 
http://nexus.fd.io/content/repositories/fd.io.release/io/fd/vpp/jvpp-registry/17.04/jvpp-registry-17.04.pom
Downloaded: 
http://nexus.fd.io/content/repositories/fd.io.release/io/fd/vpp/jvpp-registry/17.04/jvpp-registry-17.04.pom
 (395 B at 0.1 KB/sec)
Downloading: 
http://nexus.fd.io/content/repositories/fd.io.release/io/fd/vpp/jvpp-registry/17.04/jvpp-registry-17.04.jar
Downloaded: 
http://nexus.fd.io/content/repositories/fd.io.release/io/fd/vpp/jvpp-registry/17.04/jvpp-registry-17.04.jar
 (60 KB at 32.2 KB/sec)
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ nsh-sfc ---
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ nsh-sfc 
---
[WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered 
resources, i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory 
/root/vpp-ls1-working-code/plugins/nsh-plugin/build/java/jvpp/src/main/resources
[INFO]
[INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ nsh-sfc ---
[INFO] Changes detected - recompiling the module!
[WARNING] File encoding has not been set, using platform encoding 
ANSI_X3.4-1968, i.e. build is platform dependent!
[INFO] Compiling 2 source files to 
/root/vpp-ls1-working-code/plugins/nsh-plugin/build/java/jvpp/target/classes
[INFO] Some messages have been simplified; recompile with -Xdiags:verbose to 
get full output
[INFO] -
[ERROR] COMPILATION ERROR :
[INFO] -
[ERROR] 
/root/vpp-ls1-working-code/plugins/nsh-plugin/build/java/jvpp/src/main/java/io/fd/vpp/jvpp/nsh/test/NshFutureApiTest.java:[28,1]
 package io.fd.vpp.jvpp.nsh.dto does not exist
[ERROR] 
/root/vpp-ls1-working-code/plugins/nsh-plugin/build/java/jvpp/src/main/java/io/fd/vpp/jvpp/nsh/test/NshFutureApiTest.java:[29,1]
 package io.fd.vpp.jvpp.nsh.callback does not exist
[ERROR] 
/root/vpp-ls1-working-code/plugins/nsh-plugin/build/java/jvpp/src/main/java/io/fd/vpp/jvpp/nsh/test/NshFutureApiTest.java:[31,33]
 package io.fd.vpp.jvpp.nsh.future does not exist
[ERROR] 
/root/vpp-ls1-working-code/plugins/nsh-plugin/build/java/jvpp/src/main/java/io/fd/vpp/jvpp/nsh/test/NshFutureApiTest.java:[59,50]
 cannot find symbol
  symbol:   class FutureJVppNshFacade
  location: class io.fd.vpp.jvpp.nsh.test.NshFutureApiTest
[ERROR] 
/root/vpp-ls1-working-code/plugins/nsh-plugin/build/java/jvpp/src/main/java/io/fd/vpp/jvpp/nsh/test/NshFutureApiTest.java:[78,48]
 cannot find symbol
  symbol:   class FutureJVppNshFacade
  location: class io.fd.vpp.jvpp.nsh.test.NshFutureApiTest
[ERROR] 
/root/vpp-ls1-working-code/plugins/nsh-plugin/build/java/jvpp/src/main/java/io/fd/vpp/jvpp/nsh/test/JVppNshTest.java:[25,1]
 package io.fd.vpp.jvpp.nsh.dto does not exist
[ERROR] 
/root/vpp-ls1-working-code/plugins/nsh-plugin/build/java/jvpp/src/main/java/io/fd/vpp/jvpp/nsh/test/JVppNshTest.java:[26,1]
 package io.fd.vpp.jvpp.nsh.callback does not exist
[ERROR] 
/root/vpp-ls1-working-code/plugins/nsh-plugin/build/java/jvpp/src/main/java/io/fd/vpp/jvpp/nsh/test/JVppNshTest.java:[36,42]
 cannot find symbol
  symbol:   class NshAddDelEntryCallback
  location: class io.fd.vpp.jvpp.nsh.test.JVppNshTest
[ERROR] 
/root/vpp-ls1-working-code/plugins/nsh-plugin/build/java/jvpp/src/main/java/io/fd/vpp/jvpp/nsh/test/JVppNshTest.java:[36,66]
 cannot find symbol
  symbol:   class NshEntryCallback
  location: class io.fd.vpp.jvpp.nsh.test.JVppNshTest
[ERROR] 
/root/vpp-ls1-working-code/plugins/nsh-plugin/build/java/jvpp/src/main/java/io/fd/vpp/jvpp/nsh/test/JVppNshTest.java:[39,49]
 cannot find symbol
  symbol:   class NshAddDelEntryReply
  location: class io.fd.vpp.jvpp.nsh.test.JVppNshTest.TestCallback
[ERROR] 
/root/vpp-ls1-working-code/plugins/nsh-plugin/build/java/jvpp/src/main/java/io/fd/vpp/jvpp/nsh/test/JVppNshTest.java:[43,45]
 cannot find symbol
  symbol:   class NshEntryDetails
  location: class io.fd.vpp.jvpp.nsh.test.JVppNshTest.TestCallback
[ERROR] 
/root/vpp-ls1-working-code/plugins/nsh-plugin/build/java/jvpp/src/main/java/io/fd/vpp/jvpp/nsh/test/NshFutureApiTest.java:[47,25]
 cannot find symbol
  symbol:   class JVppNshImpl
  location: class io.fd.vpp.jvpp.nsh.test.NshFutureApiTest
[ERROR] 
/root/vpp-ls1-working-code/plugins/nsh-plugin/build/java/jvpp/src/mai

[vpp-dev] 50GE interface support on VPP

2017-07-04 Thread Bernier, Daniel

Hi,

I have ConnectX-4 50GE interfaces running on VPP and for some reason, they 
appear as “Unknown” even when running as 40GE.

localadmin@sm981:~$ lspci | grep Mellanox
81:00.0 Ethernet controller: Mellanox Technologies MT27700 Family [ConnectX-4]
81:00.1 Ethernet controller: Mellanox Technologies MT27700 Family [ConnectX-4]

localadmin@sm981:~$ ethtool ens1f0
Settings for ens1f0:
Supported ports: [ FIBRE Backplane ]
Supported link modes:   1000baseKX/Full
1baseKR/Full
4baseKR4/Full
4baseCR4/Full
4baseSR4/Full
4baseLR4/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Advertised link modes:  1000baseKX/Full
1baseKR/Full
4baseKR4/Full
4baseCR4/Full
4baseSR4/Full
4baseLR4/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 4Mb/s
Duplex: Full
Port: Direct Attach Copper
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Cannot get wake-on-lan settings: Operation not permitted
Current message level: 0x0004 (4)
   link
Link detected: yes

localadmin@sm981:~$ sudo vppctl show interface
  Name   Idx   State  Counter  Count
UnknownEthernet81/0/0 1 up   rx packets
723257
 rx bytes
68599505
 tx packets 
39495
 tx bytes 
2093235
 drops 
723257
 ip4
48504
UnknownEthernet81/0/1 2 up   rx packets
723194
 rx bytes
68592678
 tx packets 
39495
 tx bytes 
2093235
 drops 
723194
 ip4
48504
local00down


Any ideas where this could be fixed?

Thanks,

Daniel Bernier | Bell Canada

___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev

Re: [vpp-dev] 50GE interface support on VPP

2017-07-04 Thread Damjan Marion (damarion)

Hi Daniel,

Can you try with this patch?

https://gerrit.fd.io/r/#/c/7418/

Regards,

Damjan

On 4 Jul 2017, at 22:14, Bernier, Daniel 
mailto:daniel.bern...@bell.ca>> wrote:

Hi,

I have ConnectX-4 50GE interfaces running on VPP and for some reason, they 
appear as “Unknown” even when running as 40GE.

localadmin@sm981:~$ lspci | grep Mellanox
81:00.0 Ethernet controller: Mellanox Technologies MT27700 Family [ConnectX-4]
81:00.1 Ethernet controller: Mellanox Technologies MT27700 Family [ConnectX-4]

localadmin@sm981:~$ ethtool ens1f0
Settings for ens1f0:
Supported ports: [ FIBRE Backplane ]
Supported link modes:   1000baseKX/Full
1baseKR/Full
4baseKR4/Full
4baseCR4/Full
4baseSR4/Full
4baseLR4/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Advertised link modes:  1000baseKX/Full
1baseKR/Full
4baseKR4/Full
4baseCR4/Full
4baseSR4/Full
4baseLR4/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Speed: 4Mb/s
Duplex: Full
Port: Direct Attach Copper
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Cannot get wake-on-lan settings: Operation not permitted
Current message level: 0x0004 (4)
   link
Link detected: yes

localadmin@sm981:~$ sudo vppctl show interface
  Name   Idx   State  Counter  Count
UnknownEthernet81/0/0 1 up   rx packets
723257
 rx bytes
68599505
 tx packets 
39495
 tx bytes 
2093235
 drops 
723257
 ip4
48504
UnknownEthernet81/0/1 2 up   rx packets
723194
 rx bytes
68592678
 tx packets 
39495
 tx bytes 
2093235
 drops 
723194
 ip4
48504
local00down


Any ideas where this could be fixed?

Thanks,

Daniel Bernier | Bell Canada

___
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

Re: [vpp-dev] Compiling NSH_SFC 17.01 plugin for VPP

2017-07-04 Thread Ni, Hongjun

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 FO

Re: [vpp-dev] A query regarding fib_path_ext_init

Re: [vpp-dev] A query regarding fib_path_ext_init

[vpp-dev] how can i include dpdk.h header file in vnet?

[vpp-dev] Compiling NSH_SFC 17.01 plugin for VPP

Re: [vpp-dev] how can i include dpdk.h header file in vnet?

Re: [vpp-dev] A few questions regarding mcast fib

Re: [vpp-dev] A few questions regarding mcast fib

[vpp-dev] Compilation error: NSH SFC VPP plugin

[vpp-dev] 50GE interface support on VPP

Re: [vpp-dev] 50GE interface support on VPP

Re: [vpp-dev] Compiling NSH_SFC 17.01 plugin for VPP

11 matches

Site Navigation

Mail list logo

Footer information