Hi Neale,
The ping still failed .Here is the specific information:
DBGvpp# show trace
CLIB unknown format `%#' x label 0 eos 1024
17:23:38:439098: lookup-mpls-dst
fib-index:0 hdr:[1023:85:0:eos] load-balance:29
17:23:38:439159: ip4-mpls-label-disposition
disp:0
17:23:38:439198:
I am asking this because the session lookup functions in tcp_input.c does
not seem to be taking a fib index or a table id to look up the session -
just the usual 4-tuple.
If it is done in a different way, please help me see it.
Thanks,
-nagp
___
I am guessing the fix will work long term, but if not, perhaps an
alternative is to add --oldpackage to the rpm install options.
Burt
On Fri, May 19, 2017 at 8:34 AM, Thomas F Herbert
wrote:
>
>
> On 05/18/2017 04:37 PM, Florin Coras wrote:
>
> Well, uri.am is a known
That specific trace formatting error was fixed on master earlier today. Could
you give it a try?
Chris.
From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On
Behalf Of ???
Sent: Wednesday, May 24, 2017 22:03
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] Some error in L3VPN
Hi Matt,
Glad to hear it. And thank you for the patch.
Regards,
neale
-Original Message-
From: Matthew Smith
Date: Wednesday, 24 May 2017 at 22:24
To: "Neale Ranns (nranns)"
Cc: "vpp-dev@lists.fd.io"
Subject: Re: [vpp-dev]
Hi Neale,
I set that flag and have been testing with it and it seems to have solved the
problem.
Thanks!
-Matt
> On May 20, 2017, at 2:18 AM, Neale Ranns (nranns) wrote:
>
> Hi Matt,
>
> No ARP lookup is needed for interfaces that are point-2-point. The FIB will
> link
Dear all,
I use the vagrant installation.
I can start the VM, build the packages and start vpp process.
I am stuck at the step (Step 1: Configure and enable an interface) of the
guide available at
https://wiki.fd.io/view/VPP/Build,_install,_and_test_images.
At the first boot I have:
On Wed, May 24, 2017 at 6:21 PM, Jon Loeliger wrote:
> On Wed, May 24, 2017 at 2:00 AM, wrote:
> > Hi Jon,
>
> Hi Ole,
>
> > Thanks for the poetry! ;-)
>
> Most welcome.
>
> > This is me in 01384fe
> > Apologies for that. Next time I see you let me bring
well sure enough…i doubled the cpu reservation and it all passed clean…
things are pretty quiet right now so ill throw it up again when things are busy
but right now I’m just happy to see a full test-all-debug pass.
thanks,
Ed
> On May 24, 2017, at 8:42 AM, Klement Sekera -X (ksekera -
It may be extreme, but perhaps detect if any namespace is configured (whether
we’re running in a namespace or in the default) and then fall back to the
safest behavior (with a note in the startup output saying so).
Is it reasonable? Could add a flag that always binds every device found for
Hi,
Seems that your last patch fixed the issue. I was now able to bind both unbound
interfaces and also interfaces that were bound to kernel but were down. Thanks
_____ _ ___
__/ __/ _ \ (_)__| | / / _ \/ _ \
_/ _// // / / / _ \ | |/ / ___/ ___/
/_/
On Wed, May 24, 2017 at 2:00 AM, wrote:
> Hi Jon,
Hi Ole,
> Thanks for the poetry! ;-)
Most welcome.
> This is me in 01384fe
> Apologies for that. Next time I see you let me bring both band aid and
> whiskey.
Apology accepted!
> To my excuse, there has been this list
Hi Sergio,
Right, without the change to dpdk.am, it builds correctly with the
crypto libraries, but the plugin fails to load.
After the change, i'm able to load the plugin, but the enqueue_crypto
call does not return, no crypto error ops counters are incremented
either
Building it using the
I know that the functional BFD tests passed so unless there is a bug in
the tests, the failures are pretty much timing issues. From my
experience the load is the culprit as the BFD tests test interactive
sessions, which need to be kept alive. The timings currently are set at
300ms and for most
I think i fixed the issue. New version is in gerrit. If you still see the crash
please try to capture backtrace.
Thanks,
Damajn
> On 24 May 2017, at 16:29, Damjan Marion (damarion) wrote:
>
>
> Any chance you can capture backtrace?
>
> just "gdb —args vpp unix
Any chance you can capture backtrace?
just "gdb —args vpp unix interactive”
Thanks,
Damjan
> On 24 May 2017, at 13:10, Michal Cmarada -X (mcmarada - PANTHEON TECHNOLOGIES
> at Cisco) wrote:
>
> Hi,
>
> I tried your patch, I built rpms from it and then reinstalled vpp
right now its a VERY intentional mix…but depending on loading I could easily
see this coming up if those timings are strict.
To not dodge your question max loading on my slowest node would be 3 concurrent
builds on an Xeon™ E3-1240 v3 (4 cores @ 3.4Ghz)
yeah yeah stop laughing…..Do you have
Hi,
I tried your patch, I built rpms from it and then reinstalled vpp with those
rpms. I ensured that the interface was not bound to kernel or dpdk. But I got
Segmentation fault. See output:
[root@overcloud-novacompute-1 ~]# dpdk-devbind --status
Network devices using DPDK-compatible driver
Yeah, I’m aware of this issue but I don’t have any good idea how to address it.
We can disable unbind if we detect that we are running inside namespace, but
that will not fix problem in opposite direction, when specific interface is
mapped to namespace and vpp running in global.
any ideas?
>
Hi Ed,
how fast are your boxes? And how many cores? The BFD tests struggle to meet
the aggresive timings on slower boxes...
Thanks,
Klement
Quoting Ed Kern (ejk) (2017-05-23 20:43:55)
>No problem.
>If anyone is curious in rubbernecking the accident that is the current
>test-all (at
20 matches
Mail list logo