In addition, do
1. show hardware
The bond, eth1/0, and eth2/0 should have the same mac address.
2. show lacp details
Check these statistics for the interface that is not forming the bond
Good LACP PDUs received: 13
Bad LACP PDUs received: 0
LACP PDUs sent: 14
last LACP PDU receive
> As suggested we tried putting the rdma interfaces in promiscuous mode, but
> still facing the same issue:-
> vpp# set interface promiscuous on eth1/0 vpp# set interface promiscuous on
> eth2/1
> What could be the possible reason for this issue?
Can you share a packet trace?
vpp# cle tr
vpp# tr a
Hi,
As suggested we tried putting the rdma interfaces in promiscuous mode, but
still facing the same issue:-
vpp# set interface promiscuous on eth1/0 vpp# set interface promiscuous on
eth2/1
What could be the possible reason for this issue?
Thanks and Regards,
Chinmaya Agarwal.
-=-=-=-=-=-=-
Hello,
> In our intentions:
> Our process --> Memif --> VPP (TCP to eth) --> ??? custom plug-in -->
> Our radio stack (including driver)
> I walked through the VPP docs, but it is not clear to me if there is
> already something that can let us interface with the bottom of the stack.
From what I u
Hello,
Hard to tell without info about the various nodes etc.
The best should be to look at the "show run" output:
https://s3-docs.fd.io/vpp/23.02/gettingstarted/troubleshooting/cpuusage.html#vpp-cpu-load
When traffic run through, do "clear run" and then "show run" in the VPP cli to
see where cy
