[stratum-dev] Is there a limit on the # of ECMP groups stratum_bmv2 can handle?
max at opennetworking.org
Wed May 12 03:38:02 UTC 2021
After some investigation I found the root cause to this issue:
I expect this to get merged soon.
On Mon, May 10, 2021 at 5:36 PM Maximilian Pudelko via stratum-dev <
stratum-dev at lists.stratumproject.org> wrote:
> Hi Syd,
> I have not observed this error before. Stratum-bmv2 is backed by PI (
> All P4RT messages are passed to it nearly unmodified, so the issue must
> lie there.
> On Mon, May 10, 2021 at 1:47 PM A Sydney via stratum-dev <
> stratum-dev at lists.stratumproject.org> wrote:
>> Hi Stratum folks,
>> # Context:
>> I have created a pipeline that enables IPv4-ECMP (P4 snippet shown in
>> attached file action_selector*) and I am able to build and push p4info.txt
>> and bmv2.json to the switches.
>> # Issue:
>> When I attempt to add groups, the first one moves to the "ADDED" state.
>> When I attempt to add a second, the first group and the second both move to
>> the "PENDING_ADD_RETRY" state.
>> # ONOS logs:
>> At the same time, P4RuntimeClientImpl throws the error "Error while
>> performing READ on device:spine2...Unexpected error in RPC handling". Then
>> ONOS spirals into this cycle of attempting to reinstall all flows on the
>> switch (See debug.log for details.).
>> # Logs on one of the bmv2 switches:
>> I then see the following error on the switch:
>> [libprotobuf FATAL
>> CHECK failed: (index) < (current_size_):
>> # Question:
>> Have you ever come across this one? Are there any obvious mistakes that
>> I'm running into (Perhaps my P4 ECMP definition attached is incorrect?)?
>> Any suggestions on how to debug further?
>> stratum-dev mailing list
>> stratum-dev at lists.stratumproject.org
> stratum-dev mailing list
> stratum-dev at lists.stratumproject.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the stratum-dev