Re: [vpp-dev] VPP crash after days of heavy traffic, next_index is not associated to an interface #vpp_stability

Perfect! Thanks for confirming! Florin > On Oct 21, 2018, at 12:16 PM, JB wrote: > > Hello Florin, > > Brilliant, that does seem to address it. > > We'll patch it tomorrow. > > Much appreciated. > > Thanks, > John -=-=-=-=-=-=-=-=-=-=-=- > Links: You receive all messages sent to this group.

Re: [vpp-dev] VPP crash after days of heavy traffic, next_index is not associated to an interface #vpp_stability

Hello Florin, Brilliant, that does seem to address it. We'll patch it tomorrow. Much appreciated. Thanks, John -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#10898): https://lists.fd.io/g/vpp-dev/message/10898 Mute This Topic: https://lists.fd.i

Re: [vpp-dev] VPP crash after days of heavy traffic, next_index is not associated to an interface #vpp_stability

The issue should be fixed by this [1]. Thanks, Florin [1] https://gerrit.fd.io/r/#/c/15430/ > On Oct 21, 2018, at 7:23 AM, Dave Barach via Lists.Fd.Io > wrote: > > Thanks for the report… This is the sort of thing we need to clean up. We do > very little negative testing of the form: send the

Re: [vpp-dev] How are graph nodes scheduled?

See …/src/vlib/main.c, and https://fdio-vpp.readthedocs.io/en/latest/gettingstarted/developers/vlib.html?highlight=dispatch#graph-node-dispatcher At this level, we need to make a distinction between a vlib_pending_frame_t – a vector of buffer indices to be processed by a certain node – and the

[vpp-dev] How are graph nodes scheduled?

Hello, I'd like to know a few more details how the packet scheduling in the node graph works. From what I understand, in every scheduling "event", the input node is executed. But what about the other nodes? Are they executed in parallel or sequentially? Is a packet vector processed completely afte

Re: [vpp-dev] VPP crash after days of heavy traffic, next_index is not associated to an interface #vpp_stability

Thanks for the report… This is the sort of thing we need to clean up. We do very little negative testing of the form: send the kitchen sink with nothing configured. From: on behalf of JB Date: Sunday, October 21, 2018 at 9:59 AM To: "vpp-dev@lists.fd.io" Subject: Re: [vpp-dev] VPP crash after

Re: [vpp-dev] VPP crash after days of heavy traffic, next_index is not associated to an interface #vpp_stability

Hi Dave,   We have not configured LISP-GPE   Could it be that VPP received an encapsulated packet it wasn't expecting causing it to crash? That'd be dangerous   I'll have a look at the page for bug reports! Thanks, John -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this gr

Re: [vpp-dev] VPP crash after days of heavy traffic, next_index is not associated to an interface #vpp_stability

Please see https://wiki.fd.io/view/VPP/BugReports. Just to confirm: you’re using LISP-GPE, right? Please send vpp version and configuration info. Anyhow, the clib_warning “vnet[18358]: next_index_to_iface:101: next_index not associated to an interface!” suggests that an immediate NULL pointer

[vpp-dev] VPP crash after days of heavy traffic, next_index is not associated to an interface #vpp_stability

Hello, I've encountered a crash I've not seen posted anywhere. We have a test setup running NAT and on average around 5 Gbps/500 kpps of traffic. After 24-48 hours, VPP crashes with the following error: vnet[18358]: next_index_to_iface:101: next_index not associated to an interface! vnet[18358]