Skip to Content.

rare-dev - Re: [rare-dev] issues with tofino2

Subject: Rare project developers

List archive


Re: [rare-dev] issues with tofino2


Chronological Thread 
  • From: Frédéric LOUI <>
  • To:
  • Subject: Re: [rare-dev] issues with tofino2
  • Date: Wed, 2 Nov 2022 15:53:35 +0100
  • Dkim-filter: OpenDKIM Filter v2.10.3 zmtaauth03.partage.renater.fr 2A584800BE

Hi,

In order to test RARE/freeRtr with TOFINO 2, I tried to use the SDE used in
RARE/freeRtr ONIE image and that is installed on AS9516-32D.
The only TOFINO 2 sample is provided with the courtesy of CALTECH.

IIRC it uses right now 9.7.2.

However, bf_forwarder.py still some adjustment and is not ready for TOFINO 2.
https://bitbucket.software.geant.org/projects/RARE/repos/rare/browse/bfrt_python/rare/bf_forwarder/opt_parser.py#91

It shows that accton_as9516_32d is missing and might need adjustment for the
future.
I presume that TOFINO 2 development will effectively, practically start when
we will have one in GP4L.

I did not have tested 9.11.0 yet, SDE NixPkgs is including SDEs -> 9.10.0

I presume that « self.stub.GetForwardingPipelineConfig » has changed in
client.py API 9.11.0 as we get a "Unexpected error in RPC handling » error.

So maybe a couple of idea to move forward:
-1 Get a hand at SDE 9.11.0 grpc BfRuntime API document and look at new API
name for « self.stub.GetForwardingPipelineConfig"
-2 In SDE 9.11.0 try to grep proto file and identify the new RPC message

IIRC this arrived already in the past and some protobuf message had to be
adjusted in the code.

Frederic

> Le 2 nov. 2022 à 11:33, mc36 <> a écrit :
>
> hi,
> i tried to reproduce the tofino2 issue with the latest sde911 but i get the
> below error...
> the forwarder errors out pointing to the sde itself... it works if i start
> for tofino1...
> any idea on how to proceed?
> thanks,
> cs
>
>
>
> bf_forwarder.py running on: ACCTON_WEDGE100BF_32X
> Connected to control plane 10.10.10.227:9080
> GRPC_ADDRESS: 127.0.0.1:50052
> P4_NAME: bf_router
> CLIENT_ID: 0
> Subscribe attempt #1
> Subscribe response received 0
> Connected to grcp server
> Traceback (most recent call last):
> File
> "/home/mc36/bf-sde-9.11.0/install/lib/python3.9/site-packages/tofino/bfrt_grpc/client.py",
> line 494, in bfrt_info_get
> msg = self.stub.GetForwardingPipelineConfig(req)
> File "/usr/lib/python3/dist-packages/grpc/_channel.py", line 826, in
> __call__
> return _end_unary_response_blocking(state, call, False, None)
> File "/usr/lib/python3/dist-packages/grpc/_channel.py", line 729, in
> _end_unary_response_blocking
> raise _InactiveRpcError(state)
> grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated
> with:
> status = StatusCode.UNKNOWN
> details = "Unexpected error in RPC handling"
> debug_error_string =
> "{"created","description":"Error received from peer
> ipv4:127.0.0.1:50052","file":"src/core/lib/surface/call.cc","file_line":1055,"grpc_message":"Unexpected
> error in RPC handling","grpc_status":2}"
> >
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
> File "/home/mc36/rare/bfrt_python/bf_forwarder.py", line 100, in <module>
> bf_client, bf_client_id = newClient(bind = True)
> File "/home/mc36/rare/bfrt_python/bf_forwarder.py", line 85, in newClient
> client = BfRuntimeGrpcClient(
> File "/home/mc36/rare/bfrt_python/rare/bf_grpc_client/__init__.py", line
> 40, in __init__
> self.bfrt_info = self.interface.bfrt_info_get()
> File
> "/home/mc36/bf-sde-9.11.0/install/lib/python3.9/site-packages/tofino/bfrt_grpc/client.py",
> line 496, in bfrt_info_get
> raise BfruntimeForwardingRpcException(e)
> File
> "/home/mc36/bf-sde-9.11.0/install/lib/python3.9/site-packages/tofino/bfrt_grpc/client.py",
> line 266, in __init__
> assert(grpc_error.code() != grpc.StatusCode.UNKNOWN)
> AssertionError
>




Archive powered by MHonArc 2.6.19.

Top of Page