Frames can be filtered based on error information.
NTPL examples
The following error filters are
supported.
// Frames with code violation errors. Assign[StreamId = 0] = CvError==TRUE //Frames with FCS errors. Assign[StreamId = 1] = CrcError==TRUEError filters can be combined as follows.
Assign[StreamId=1] = CvError==TRUE OR CrcError==TRUEFrames with a length larger than 10,000 bytes are hard-sliced into 10,000 bytes and forwarded with a hard-sliced indication. Truncated frames can be filtered as shown in the following example.
Assign[StreamId=2] = Truncated==True
Layer 3 and 4 checksum errors
The following SmartNICs support layer 3 and 4 checksum errors.
- NT200A02 SmartNICs running on a test and measurement image
- NT100A01 SmartNICs running on a test and measurement image
- NT50B01 SmartNICs running on a test and measurement image
Assign[StreamId = 3] = Layer3CheckSumError==TRUE Assign[StreamId = 4] = Layer4CheckSumError==TRUE
Frames with layer 3 and 4 checksum errors on the inner layer can be
filtered as
follows.
Assign[StreamId = 5] = Layer3TunnelCheckSumError==TRUE Assign[StreamId = 6] = Layer4TunnelCheckSumError==TRUE
For error checks of tunneled traffic, it is possible to validate
checksum errors on both inner and outer layers by configuring the
CsrxPrioritizeInnerProtocol parameter in the
/opt/napatech3/config/ntservice.ini file as
follows.
CsrxPrioritizeInnerProtocol = orIf it is set to or, both inner and outer layer 3 and 4 checksum errors will be detected on frames containing an inner layer. See Checksum error indications in DN-1128.