Skip to Content.
Sympa Menu

rare-users - Re: [RARE-users] Issues with RARE on WEDGE

Subject: RARE user and assistance email list

List archive

Re: [RARE-users] Issues with RARE on WEDGE


Chronological Thread 
  • From: Marc Bruyere <>
  • To:
  • Subject: Re: [RARE-users] Issues with RARE on WEDGE
  • Date: Wed, 6 Sep 2023 08:32:05 +0900

Hi

Sorry the bf-shell was from one of our UFI came from another platoform where we have the similar issues.
But here we try to at least make works the WEDGE reference platform first.

Changed the page with the correct output from the WEDGE
https://md.bruyere.family/ImBJBzbJSkaYoVmez9ZfFg?view

But better to have a look and do pause on the screen recording
https://cloud.bruyere.family/s/2oebQ9RgkJW5PeE

We do not have issue with the kernel PCI module and we did loaded withbf_kpkt_mod_load.
The issue is the packet are corrupted as seen in the pcap trace attached in the previous email.

Any idea, why ?

/mb




Le 2023/09/05 à 22:00, Alexander Gall a écrit :
Hi

On Tue, 5 Sep 2023 17:38:46 +0900, Marc Bruyere <>
said:

Hi All,
We are having issues to make it work RARE/FreeRtR on our WEDGE Tofino1.
I'm a bit confused: here you say your device is a WEDGE, i.e. EdgeCore
DCS800 (formerly known a Wedge100bf-32x), but at the link below you
say it's a "UFI s9180-32x". I assume it's the latter :) Since you
seem to build all software from scratch, you would need a "BSP"
(Baseboard Support Package) supplied by the vendor to get full support
of the hardware (I didn't know about this platform until now so we
also don't support it in our regular RARE builds). It should still
work without it but you won't be able to see the QSFP plugins from
within bfshell.

However, your first problem seems fairly simple. From your bfshell
log:

ASIC detected at PCI /sys/class/bf/bf0/device
ERROR getting ASIC pci device id fpr /sys/class/bf/bf0/device
Starting PD-API RPC server on port 9090
bf_switchd: drivers initialized
error opening /dev/bf0
ERROR: Device mmap failed for dev_id 0
Please load driver with bf_kdrv_mod_load script. Exiting..

This means that the kernel module hasn't been loaded yet. For RARE
you'll need the bf_kpkt module. So please use the bf_kpkt_mod_load
script from the SDE to load the module. This will create a new network
interface called "bf_pci0" (might get renamed to something else by
udev), which is needed for the the control-plane traffic between the
Tofino and freertr.

I hope this will bring you a step closer to success.

--
Alex

We have been able to run control plane and date plane, but we see like
corrupted packets reaching the FreeRouter process.
Please also find a short screen recording :
https://cloud.bruyere.family/s/2oebQ9RgkJW5PeE
We tried to ping from lab 2 to the freerouter interface but freerouter does
not even reply to ARP request has its not recognize the packets.
We tried to ping from freerouter to lab 2 same issue.
and a pcap trace of the traffic capture on the ubuntu PCIE ens1 interface
attached to this email.
More details on this page
https://md.bruyere.family/ImBJBzbJSkaYoVmez9ZfFg?view
and our testbed diagram :
+----+---------------------------+---+
| +---------------------------+ |
| | FreeRouter | |
| | | |
| | | |
| | | |
| | | |
| | 10.0.1.1 10.0.2.1 | |
| | sdn3 sdn4 | |
| +--+-------------------+----+ |
| | | |
| | | |
| FrontPanel 3 FrontPanel4 |
| Internal 144 Internal 152 |
+-------+-------------------+--------+
| |
| |
| |
| |
| |
| |
| |
| |
10.0.1.101 | | 10.0.2.202
+-------+----+ +----+--------+
| Lab1 server| | Lab2 Server |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
+------------+ +-------------+
Your help will be very appreciated !
Marc and Benoit
/mb




Archive powered by MHonArc 2.6.24.

Top of Page