Troubleshoot NPU Packet Trace
For supported software information, click here.
NPU packet trace helps to debug packet tracing in ingress pipelines on Broadcom-based platforms. You can inject a packet from a host CPU through an ingress Ethernet (enet) port and see the packet trace output in the /var/log/versa/versa-npu-pkttrace.log file.
Initiate NPU Packet Trace
To initiate the NPU packet trace, issue the following CLI command:
request debug session npu-packet-trace receive-interface <enet-name> input-file <packet-file>
For example:
You can obtain the hex contents of the file from the tcpdump capture and copy them to a file.
For example:
You can also store the hex contents as continuous bytes.
For example:
The example below shows the output of the NPU packet trace:
Diagnose NPU Packet Trace
You can diagnose NPU packet trace using the following CLI command:
show npu packet-trace <enet-name> <data> <file-name>
This is a Versa Services Management (VSM) command which takes input as either hex data or a file name. If you provide hex data, the file name can be passed as 0; if data is passed as 0, the file name can be provided with the proper path output. The output of this command is visible in the VSM diagnostics CLI and no output is directed to the versa-npu-pkttrace.log file.
The example below shows the VSM diagnostics CLI input as hex data:
The example below shows the VSM diagnostics CLI input as a file name:
Limitations
- The NPU packet trace request CLI command can be provided only for enet ports.
- Only file name input is allowed for the request CLI command.
- Broadcom-based platforms only support ingress pipeline lookup results, not egress pipeline results.
Supported Software Information
Releases 22.1.4 and later support all content described in this article.