we get nvipc.pcap file according to Aerial SDK 24-2.1 release guide, but we cannot decode it as FAPI message with wireshark.
do we have some tools to decode nvipc.pcap as FAPI message?
eg, loading some .lua file to decode nvipc.pcap file.
capture pcap log: Running cuBB End-to-End - NVIDIA Docs
get this lua file now. but some error occurred. may need to update lua file.
scffapi_nv.lua.zip (27.1 KB)
Hi @zhenming.a.cheng ,
Welcome to the Aerial forum.
Can you check preferences> protocols > NVIDIA_FAPI tab? The “Size of length field in CONFIG.request TLV” should be set to uint32_t. If there is a parsing error, it is most likely caused by wrong setting(s) in one of these parameters on NVIDIA_FAPI tab.
Thank you.
hi @bkecicioglu ,
thank you for your quick response. In fact several message have similar Lua Error as below:
I update NVIDIA_FAPI tab as you mentioned. but this Error still exist. maybe I miss something?
Error:
CONFIG.request
Lua Error: C:\Program Files\Wireshark\plugins\scffapi_nv.lua:1151: attempt to index a nil value (field ‘?’)
UL_TTI.request
Lua Error: C:\Program Files\Wireshark\plugins\scffapi_nv.lua:1975: Range is out of bounds
TX_DATA.request
Lua Error: C:\Program Files\Wireshark\plugins\scffapi_nv.lua:2970: attempt to perform arithmetic on a nil value (global ‘length’)
UCI_indication
Lua Error: C:\Program Files\Wireshark\plugins\scffapi_nv.lua:3122: attempt to call a nil value (field ‘pow’)
the command I used (AERIAL SDK 24-2.1):
cmake -Bbuild -GNinja -DCMAKE_TOOLCHAIN_FILE=cuPHY/cmake/toolchains/native -DSCF_FAPI_10_04=ON -DENABLE_CONFORMANCE_TM_PDSCH_PDCCH=ON
nvipc.pcap:
nvipc.zip (45.7 MB)
I am not seeing the lua errors with the following settings.
I also attached the lua file I use.
I hope this resolves the issue.
Thank you.
scffapi_nv.lua.zip (29.2 KB)
Thanks! @bkecicioglu .
when i use the .lua you offered. CONFIG.request can be decoded successfully.
However, UL_TTI.request and TX_DATA.request still cannot be decoded.
do you have the same issue with your .lua and my .pcap ?
my wireshark version is “Version 4.4.2 (v4.4.2-0-g9947b17309f4)”. is it relevant to wireshark version?
@zhenming.a.cheng are you using testMAC or an actual L2+ stack for this test?
@bkecicioglu , Yes, I am using testMAC for this test. release Aerial SDK 24-2.1
# terminal testmac
cd /opt/nvidia/cuBB/build/cuPHY-CP/testMAC/testMAC
sudo numactl -N 1 -m 1 ./test_mac F08 1C 61
# cuphy terminal
cd /opt/nvidia/cuBB/build/cuPHY-CP/cuphycontroller/examples
export CUDA_DEVICE_MAX_CONNECTIONS=8
export CUDA_MPS_PIPE_DIRECTORY=/var
export CUDA_MPS_LOG_DIRECTORY=/var
sudo -E echo quit | sudo -E nvidia-cuda-mps-control
sudo -E nvidia-cuda-mps-control -d
sudo -E echo start_server -uid 0 | sudo -E nvidia-cuda-mps-control
sudo -E numactl -N 1 -m 1 ./cuphycontroller_scf F08_R750
If you disable “Parse MAC PDU in TX data request”, TX data request message should be parsed correctly.
The parsing error for UL_TTI request also seems to limited to RX Beamforming PDU part of the PUSCH PDU. You can still see the L1 configuration properly.
Please see attached for the examples from the pcap capture you shared earlier.
We did observe some issues with the Wireshark version in the past. The version I am using is Version 4.4.1 (v4.4.1-0-g575b2bf4746e).
Thank you.
HI, @bkecicioglu , Thank you very much! we can get UL_TTI.request info.
it seems that CRC.indication and UCI.indication cannot be parsed correctly?
Could we manage to parse below info also? :) .
Thanks very much for your support!!
CRC.indication
@bkecicioglu
UCI.indication
I do not see any parsing errors with UCI or CRC indication. Please see attached.
Thanks.
Hi, @bkecicioglu,
It is strange that I have Lua Errors for UCI.indication and CRC.indication although I use the scffapi_nv.lua and FAPI Protocol configuration you offered.
Could you please share the wireshark install file?
named as Wireshark-4.4.1-x64.exe. I want to try the same wireshark as you. But I cannot download the wireshark version you used.
Could you please also help to check my FAPI Protocol configuration as below?
Hi @zhenming.a.cheng ,
The FAPI protocol settings are matching with what I use.
You can find the installer you are looking for here.
Please note that we are not including the lua file with the release. Therefore, it is for internal use and not maintained regularly.
I attached the lua file I am currently using (it is possible that I updated it recently and it could be different than what I shared above).
Thanks.
scffapi_nv.lua.zip (29.3 KB)
Hi @bkecicioglu ，
Got it, thanks for your reminding, we will internal use it for debug issue only.
The lua file you offered today is the same as the one offered on Jan 3. right？. And it is the one I used now.
However, below lua error still exist. may be it is because we use different wireshark version? :(
Hi @zhenming.a.cheng
while compiling cuBB, did you have FAPI 10.04 flag?
Hello, @jixu
Yes, I build with below flag which is recommended when testing F08.
aha, I am curious why I cannot decode UCI.indication/CRC.indication while bkecicioglu can decode it although we use the same configuraiton and lua script to decode same pcap file !!! it seems that only difference is wireshark verson.
$ cmake -Bbuild -GNinja -DCMAKE_TOOLCHAIN_FILE=cuPHY/cmake/toolchains/native -DSCF_FAPI_10_04=ON -DENABLE_CONFORMANCE_TM_PDSCH_PDCCH=ON
$ cmake --build build
Hello, @jixu @bkecicioglu ,
Could I ask whether you have lua script for cumac pcap?
I collect cumac pcap file (testMAC+cuMAC-CP) and want to decode it as related message.
Could you please share it if you have?
Thanks!!!
cumac pcap file (run in CPU for known solution do not match issue):
cumac.zip (162.9 KB)
cuMAC message:
CUMAC_PARAM_REQUEST = 0x00,
CUMAC_PARAM_RESPONSE = 0x01,
CUMAC_CONFIG_REQUEST = 0x02,
CUMAC_CONFIG_RESPONSE = 0x03,
CUMAC_START_REQUEST = 0x04,
CUMAC_STOP_REQUEST = 0x05,
CUMAC_STOP_RESPONSE = 0x06,
CUMAC_ERROR_INDICATION = 0x07,
CUMAC_START_RESPONSE = 0x08,
CUMAC_DL_TTI_REQUEST = 0x80,
CUMAC_UL_TTI_REQUEST = 0x81,
CUMAC_SCH_TTI_REQUEST = 0x82,
CUMAC_SCH_TTI_RESPONSE = 0x83,
CUMAC_TTI_END = 0x8F,
CUMAC_TTI_ERROR_INDICATION = 0x90,
@zhenming.a.cheng
I don’t see the lua error with the same lua file either. I would like to check the pcap you captured that gives lua error. would you please share one?
Hi @jixu
The pcap and Lua I used as below:
pcap_lua.zip (45.7 MB)
The wireshark version I used: Version 4.4.2 (v4.4.2-0-g9947b17309f4).
The error I have is as below:
