Release Note for Napatech Link™ Software Driver Version 3.25.3
Release date
2021-09-21
Description
This release note applies to driver package nt_driver_3gd-linux-3.25.3
Release history from version 3.21.2 to 3.25.3
New Features
| ID | Customer tracking number | Summary | Implemented in |
|---|---|---|---|
| 44416 | Support for new FPGA images: 9541-47-07, 9543-47-07, 9545-47-07, 9555-47-07, 9546-47-07, 9554-47-07, 9560-47-07 added | 3.25.3 | |
| 44353 | 44296 (Support) | File permissions set to 644 when generating ntservice.ini and ntservice.ini.txt | 3.25.3 |
| 44342 | 44316 (Support) | Support for new FPGAs: 9521-43-12, 9526-43-12, 9532-43-12, 9533-43-12, 9549-43-12 and 9555-47-06 | 3.25.3 |
| 44267 | 44188 (Support) |
The options "DynOffset" and "Offset" have been deprecated in favor of "ProtOffset".
It is still possible to use "DynOffset", but it is recommended to use "ProtOffset" instead. Macros in FilterMacros.txt have been updated accordingly. Finally, for those who still use "DynOffset", a bug has been fixed such that "DynOffLayer2Data" now works for MPLS packets. |
3.25.1 |
| 44243 | It is now possible to configure the size of the packet buffer vs. the size of the flow-table in a number of discrete steps. | 3.25.3 | |
| 44218 | 44199 (Support) | Flow manager SPAN port example has been added | 3.25.1 |
| 44154 | 43773 / 43855 (Supp) | Support for FPGA images 9537-44-11 and 9538-44-11 added | 3.24.1 |
| 44143 | 44141 / 43655 (FR) | Support for up to Linux kernel version 5.11 has been added | 3.24.1 |
| 44105 | 44055 (FR) | When calling the NT_NetFileOpen_v2 function with the 'noConvert' parameter equal to False (i.e, request automatic conversion of PCAP packets) to read a file containing PCAP packets with PCAP-NANO timestamps, the Napatech library silently discards the nanosecond precision and converts the timestamps to 10-nanosecond precision. | 3.24.1 |
| 44072 | 43637 (FR) | Added option in ntservice.ini to configure inclusion of Ethernet FCS when capturing with PCAP descriptor on 4GArch cards supporting that capability. | 3.23.7 |
| 44064 | Support for new FPGA: 200-9554 4*10/25G, Test & Measurement & 200-9560 4*1/10G, Test & Measurement for NT100A01 | 3.24.0 | |
| 44043 | 43895, 43981 (Sup) |
Driver support added for FPGA-image v35-25 of these image IDs:
NT200A02: 9532, 9533, 9534, 9545, 9549, 9555 NT50B01: 9541 NT100A01: 9553, 9559 NT200A01: 9531 |
3.23.6 |
| 43925 | 43895 (Support) | Driver support added for FPGA-image 9541-35-23 | 3.23.4 |
| 43896 | Support for new FPGA: 200-9553-35-20 (NT100A01-4x10/25Gb, capture flow management) | 3.23.3 | |
| 43848 | New feature, PORT SPEED LOCKING, added for NT50B01 | 3.23.3 | |
| 43847 | New feature, PORT SPEED LOCKING, added for NT100A01 | 3.23.3 | |
| 43811 | 43801 (Support) | Code example of how to poll for hostbuffers attached using NTAPI has been added | 3.23.3 |
| 43809 | 43774 (FPGA) | Added support for FPGA image 200-9555-32-11 (NT200A02-2x1/10G, Capture) | 3.22.3 |
| 43804 | Support for new FPGA: 200-9559 for NT100A01 4x1/10G, Capture Flow Management (FM1) | 3.23.2 | |
| 43785 | Support for new FPGA: 200-9541-25-xx-xx (NT50B01-2x25/10Gb, capture) | 3.23.1 | |
| 43753 | 43750 (Support) | New feature, %s placeholder for PtpStatusLogFile, added | 3.23.6 |
| 43718 | 43592 (FeatureReq) | Tx path latency values available via NTAPI for 2x10/25G (FPGA image 9545), 2x40G(FPGA Image 9546) & 2x100G (FPGA image 9543) with Capture Test & Measurement feature set | 3.22.0 |
| 43619 | Support for FPGA ID 9555 (2x1/10G Capture/Replay feature set) | 3.22.0 | |
| 43598 | 43577 (Support) | Error messages and NTPL FilterInfo printout has been updated to better describe the resources used by the FPGA TCAM. | 3.21.4 |
Resolved Issues
| ID | Customer tracking number | Summary | Found in version | Resolved in version |
|---|---|---|---|---|
| 44238 | 44202 (Support) | When using PCAP descriptor the segment timestamps retrieved via NT_NET_GET_SEGMENT_TIMESTAMP() are section-swapped, if segments are empty. | 3.16.1 | 3.25.1 |
| 44215 | 44208 (Support) | Reading host buffer info with NT_NETRX_READ_CMD_GET_HB_INFO command will occasionally return values far out of range for host buffer "pending" and "available" values. | 3.9.1 | 3.25.0 |
| 43829 | 42574 (Support) | Tx TBH delineation errors may occur when applying certain filter instructions during packet transmission in forwarding (inline) scenarios | 3.10.2 | 3.23.3 |
| 43818 | 43798 (Support) | Binaries were dynamically linked to libncurses | 3.9.0 | 3.23.3 |
| 43756 | 43570 (FR) | Various code changes and bugfixes to get a clean MF Fortify static code scan | 1.0.0 | 3.23.0 |
| 43755 | 43730 (Support) | Ntservice now fails when using unsupported/depreciated adapter settings in ntservice.ini | 1.0.0 | 3.23.0 |
| 43599 | 43596 (Support) | For host-loopback to work, it requires a "link up" state when enabled on adapters with multiple lanes for each physical port. | 3.20.4 | 3.21.4 |
Known issues
| ID | Customer tracking number | Summary | Found in version |
|---|---|---|---|
| 44314 | SFP+ dual-speed 1000BASE-T/10GBASE-T modules support 10G only | 3.23.3 | |
| 44312 |
Periodic problem for adapter installed in a x8-lane PCIe gen.3 supported slot and configured with 25G DAC
Workaround: Reboot server |
3.25.1 | |
| 44286 | The diode on both cards light up when using CU and TRI speed electrical plugables, regardless of link status. | 3.25.1 | |
| 43621 | TX is not properly disabled on all ports when enabling host-loopback while using DAC cables, resulting in packets being transmitted from the adapter. | 3.21.3 | |
| 42948 | Frequent CRC errors when using DAC cables shorter than 1 meter. | 3.13.3 | |
| 42936 | The link diode extinguishes when the port is disabled as it should, but lights up again when the module is unplugged and reinserted with the port still disabled. No link is up. But the diode lights up as if there is. Status is read correct from software. | 3.13.3 | |
| 42888 | 42887 (Support) |
When using a TX host buffer that is at least two gigabytes, the driver may, for some FPGA image versions, log:
"Tx TBH delineation error on Tx feed <number>: some packets may not have been transmitted", in which case the adapter transmits at a slower rate and discards packets. Workaround: There are three workarounds: 1. Upgrade to a newer FPGA-image version (please check FPGA release notes). 2. Use a TX host buffer smaller than two gigabytes. 3. Edit the driver configuration file /opt/napatech3/config/ntservice.ini and insert the following in the [system] section: [System] NtapiNetTxSegmentRawAlignMode = 1 Then restart the driver: /opt/napatech3/bin/ntstop.sh /opt/napatech3/bin/ntstart.sh |
3.8.1 |
| 42653 | 42616 (fix) |
When using host loopback on NT200A01 without any NIMs plugged in, it is not possible to get link on a QSFP28-LR4 NIM inserted afterwards unless FEC has been disabled (for SR modules) in the ini file
Workaround: If QSFP28-LR module is to be used then either plug it in before start-up of the system or set DisableFEC=TRUE in ntsevice.ini |
3.11.1 |
| 42652 | 42616 (fix) |
FEC cannot be changed dynamically on NT200A01, if traffic has been applied. Hence, it is not possible to dynamically swap between SR and LR QSFP28 if unless FEC has been disabled for SR modules in the ini file
Workaround: If QSFP28-LR module is to be used then either plug it in before start-up of the system or set DisableFEC=TRUE in ntsevice.ini |
3.11.1 |
| 42257 |
Dynamic hostbuffers are not supported by Intel PAC A10 accelerators.
Therefore NTAPI Inline features are not supported by Intel PAC A10 accelerators. Workaround: Applications using DPDK will support Inline for Intel PAC A10 accelerators. |
3.9.1 | |
| 41150 | The Automatic over-temperature shutdown will only stop NT service, it cannot shutdown the Intel Programmable Acceleration Card Blue bitstream. | 3.9.0 | |
| 38699 |
Using NT_NetRxGet* or NT_NetRxGetMult* first time on newly created or reconfigured streams can lead to initial package drops when the system is configured with large hostbuffers or many client applications.
This will only be triggered on newly created and reconfigured streams. Workaround: If packet loss is observed, to get clean statistics no traffic should be received on connected ports while streams are being started. |
3.7.5 | |
| 32765 | When using the GlobalSync feature, link down/up events causes the port to enter 'unknown' state | 2.9.4 | |
| 14086 |
If NUMA node zero is offline and /opt/napatech3/config/ntservice.ini does not exist, the driver cannot start because it fails to allocate memory for the default host buffer set-up.
Workaround: Use an existing ntservice.ini or specify the host buffer set-up on an online NUMA node: '/opt/napatech3/bin/start.sh -o adapter0.BusId=0000:04:00.0 -o adapter0.AdapterType=NT40E3_4_PTP -o adapter0.HostBuffersRx=[4,32,1] -o adapter0.HostBuffersTx=[2,16,1]'. BusId and AdapterType are only required if there are multiple adapters in the server; the BusId can be obtained with 'lspci | grep Napa'. |
2.8.5 | |
| 10740 | When using a Cisco DAC pluggable, link is detected even if the other end of the cable is unplugged. | 2.7.0 | |
| 9189 | 9137 (Support) |
The Linux kernel v3.8->v3.12 has a bug in the NUMA balancing code which was introduced in v3.8. See https://bugzilla.kernel.org/show_bug.cgi?id=60734
The issue causes high execution delays on cores running on other than NUMA 0 if the feature is enabled. To work around the problem, disable the NUMA balancing by adding "numa_balancing=disable" to the kernel command line. The Linux kernel 3.13 received significant NUMA updates which fixes this issue. The 3.10 kernel in RHEL 7, CentOS 7 and Oracle Linux 7 (not the 3.8.13 uek kernel) contains a fix for this, thus the work around is not needed. |
0.1.1 |
| 8719 | Setting TimeSyncTimeJumpThreshold for OS timesync to values > 0, will enable the time jump feature and results in a jump threshold of 1 second. | 2.4.1 | |
| 4324 | 3GD requires at least gcc 4.0 to build and at least glibc 2.5 to run. | 1.1.0 |
Operating systems
The following operating systems are supported:
- Linux 3.0 -> 3.19 (64-bit)
- Linux 4.0 -> 4.18 (64-bit)
- Linux 5.0 -> 5.11 (64-bit)
The software has been qualified on: CentOS 7 and Ubuntu 20.04
Hardware and FPGA image compatibility
| Hardware | 4GA FPGA images |
|---|---|
| NT20E3-2-PTP | 200-9501-02-16, 200-9501-04-04, 200-9501-06-06, 200-9501-08-06, 200-9501-09-08, 200-9501-10-07, 200-9501-15-02, 200-9501-17-02, 200-9501-18-07, 200-9501-22-05, 200-9501-27-03, 200-9501-28-07 |
| NT40E3-4-PTP | 200-9502-02-16, 200-9502-04-04, 200-9502-06-06, 200-9502-06-07, 200-9502-08-06, 200-9502-08-07, 200-9502-08-08, 200-9502-09-08, 200-9502-10-07, 200-9537-22-06, 200-9537-28-07, 200-9537-44-11, 200-9538-34-09, 200-9538-44-11, 200-8011-22-02 |
| NT80E3-2-PTP | 200-9503-02-16, 200-9503-04-04, 200-9503-06-05, 200-9503-08-06, 200-9503-08-07, 200-9503-08-08, 200-9503-09-08, 200-9503-10-07, 200-9503-10-09, 200-9503-15-02, 200-9503-17-02, 200-9503-18-07, 200-9503.20.04, 200-9503-22-05, 200-9503-22-08, 200-9503-28-07, 200-9519-10-05, 200-9519-10-07, 200-9519-15-02, 200-9519-17-02, 200-9519-18-07, 200-9519-22-05, 200-9519-22-07, 200-9519-28-07, 200-8005-10-01, 200-8005-15-02, 200-8005-17-02, 200-8005-22-00 |
| NT200A01 | 200-9508-05-08, 200-9508-05-17, 200-9508-06-06, 200-9508-07-06, 200-9508-07-07, 200-9515-10-07, 200-9515-15-02, 200-9515-18-09, 200-9515-20-04, 200-9515-20-06, 200-9515-20-10, 200-9516-10-07, 200-9516-15-05, 200-9516-18-09, 200-9516-20-04, 200-9516-20-06, 200-9516-20-10, 200-9531-20-12, 200-9531-28-08, 200-9531-35-25, 200-8002-09-01, 200-8002-09-02, 200-8002-09-04, 200-8002-10-02, 200-8002-15-02, 200-8002-20-01, 200-9512-07-02, 200-9512-08-08, 200-9512-08-09, 200-9512-09-08, 200-9512-10-07, 200-9512-15-02, 200-9512-18-07, 200-9512-20-04, 200-9512-22-05, 200-9512-22-07, 200-9512-28-07, 200-9522-15-03, 200-9522-18-07, 200-9522-20-04, 200-9522-22-05, 200-9522-22-07, 200-9522-28-07, 200-8001-08-00, 200-8001-08-01, 200-8003-09-01, 200-8003-09-03, 200-8003-10-02, 200-8003-15-02, 200-8003-22-00, 200-8004-10-03, 200-8004-15-02, 200-8004-22-00, 200-8006-15-03, 200-8006-22-00, 200-8010-20-02 |
| NT40A01-4x1 | 200-9500-06-07, 200-9500-06-07, 200-9500-08-06, 200-9500-09-08, 200-9500-10-07, 200-9500-15-02, 200-9500-18-07, 200-9500-22-05, 200-9500-27-02, 200-9500-28-07 |
| NT100E3-1-PTP | 200-9504-01-12, 200-9505-02-16, 200-9505-04-04, 200-9505-06-05, 200-9505-08-06, 200-9505-08-07, 200-9505-09-08, 200-9505-10-08, 200-9505-10-09, 200-9505-15-02, 200-9505-18-07, 200-9505-20-05, 200-9505-20-07, 200-9505-28-07 |
| NT40A01 | 200-9517-09-08 |
| INTEL-A10 | 200-7000-12-00, 200-7000-12-02, 200-7000-12-06, 200-7000-22-05, 200-7000-27-02, 200-7000-28-07, 200-7001-12-00, 200-7001-12-03, 200-7001-12-06, 200-7001-22-05, 200-7001-27-02, 200-7001-28-07 |
| NT200A02 | 200-9521-18-11, 200-9521-20-04, 200-9521-22-05, 200-9521-27-03, 200-9521-28-07, 200-9521-41-04, 200-9521-43-11, 200-9521-43-13, 200-9526-18-10, 200-9526-20-04, 200-9526-22-05, 200-9526-27-03, 200-9526-28-07, 200-9526-41-04, 200-9526-43-11, 200-9526-43-13, 200-9532-27-00, 200-9532-27-02, 200-9532-27-03, 200-9532-28-08, 200-9532-35-25, 200-9532-43-11, 200-9532-43-13, 200-9533.20.04, 200-9533-22-05, 200-9533-27-03, 200-9533-28-07, 200-9533-35-25, 200-9533-43-11, 200-9533-43-13, 200-9534-21-28, 200-9534-28-07, 200-9534-35-25, 200-9534-46-06, 200-9535-21-28, 200-9535-28-07, 200-9535-46-06, 200-9536-37-00, 200-9536-46-10, 200-9539-23-00, 200-9539-23-01, 200-9540-23-00, 200-9540-23-01, 200-9543-28-07, 200-9543-44-10, 200-9543-47-07, 200-9545-28-08, 200-9545-35-25, 200-9545-44-10, 200-9545-47-07, 200-9546-28-07, 200-9546-44-10, 200-9546-47-07, 200-9549-31-03, 200-9549-35-25, 200-9549-43-11, 200-9549-43-13, 200-9555-32-10, 200-9555-35-20, 200-9555-35-25, 200-9555-43-11, 200-9555-47-05, 200-9555-47-07, 200-8007-22-00, 200-8008-22-00, 200-8009-22-00 |
| NT50B01 | 200-9541-35-20, 200-9541-35-23, 200-9541-35-24, 200-9541-35-25, 200-9541-47-04, 200-9541-47-07, 200-9561-47-05 |
| NT100A01 | 200-9553-35-20, 200-9553-35-25, 200-9553-46-06, 200-9554-44-10, 200-9554-47-04, 200-9554-47-07, 200-9559-35-20, 200-9559-35-25, 200-9559-46-06, 200-9560-44-10, 200-9560-47-04, 200-9560-47-07 |
| Hardware | 3GA FPGA images |
|---|---|
| NT4E | 200-9015-42-08, 200-9015-42-13, 200-9015-42-14 |
| NT4E-STD | 200-9017-42-09, 200-9017-42-10 |
| NT4E-INL | 200-9115-42-13 |
| NT4E2-4-PTP | 200-9226-46-12, 200-9226-46-13, 200-9226-48-05, 200-9226-50-03, 200-9226-50-04, 200-9226-51-03, 200-9226-51-04 |
| NT20E2 | 200-9220-44-10, 200-9220-44-12, 200-9220-45-06, 200-9220-46-09, 200-9220-47-03, 200-9220-50-03, 200-9220-50-04, 200-9220-50-05 |
| NT20E2-PTP | 200-9227-50-03, 200-9227-51-03, 200-9227-51-04 |
| NT20E3-2-PTP | 200-9233-52-13, 200-9233-53-01 |
| NT40E3-4-PTP | 200-9232-50-04, 200-9232-51-04, 200-9232-51-07, 200-9232-52-13, 200-9232-53-01 |
| NT40E2-1 | 200-9222-52-05 |
| NT40E2-4 | 200-9221-44-13, 200-9221-50-04 |
Microcontroller compatibility
Test status
Complete test plan
Documentation
See the Documentation Portal, WebHelp or DN-0449 for reference documentation on Napatech Software Suite.
Release note generated at
2021-09-21