EDM01-36v10 DAG_9.2X2_Card_User_Guide - Using your DAG card
48 ©2010 - 2012 Endace Technology Ltd. Confidential - Version 10 - May 2012
Trace files
You can use dagflood to transmit ERF format trace files, providing the files contain only ERF records of
the type matching the current link configuration.
For detailed information on using
dagflood, refer the
EDM04-03 dagflood User Manual
.
When you use DAG cards with multiple ports, ensure all ports referred to by the trace file are active.
This ensures the
dagflood traffic is not blocked when trying to delivering data to an inactive port.
Check the interface status output for the DAG card and ensure the link status for all required destination
ports is active. See Viewing the DAG card statistics. (page 34
)
For further information on using dagflood please refer to the
EDM04-03 dagflood User Manual
available
from Endace Customer Support at https://support.endace.com/.
In addition the length of the ERF records to be transmitted must be a multiple of 64-bits. You can
configure this when capturing packets for later transmission by setting 64-bit alignment using the
dagconfig align64 command.
If packets have been captured without using the
align64 option you can convert the trace files so that
they can be transmitted by using dagconvert (page 43
) as shown below:
dagconvert -v -i tracefile.erf -o tracefile.erf -A8
Alternatively if you are unsure if a trace file is 64-bit aligned you can test the file using dagbits (page 40
)
as shown below:
dagbits -v align64 -f tracefile.erf
If you do not have any ERF trace files available, you can use
daggen to generate trace files containing
simple traffic patterns. This allows the DAG 9.2X2 card to be used as a test traffic generator.
For further information on using daggen please refer to the
EDM04-06 Daggen User Guide
available from
Endace Customer Support at https://support.endace.com/.
TR TERF
For a description, see Timed Release TERF (TR-TERF) (page 7).
Selectable CRC length
TR-TERF can be optionally configured to strip the CRC of an incoming ERF stream, to allow the
retransmitted stream to calculate and add a CRC. There are some situations where this option may be
useful.
The ERF stream was generated without a CRC.
In this case, you should configure TR-TERF not to strip the last 32 bits of the packet as there is no CRC
in place, and configure the MAC to add a hardware-calculated CRC. This has the effect of reducing the
burden of calculating a CRC in the software.
dagconfig noterf_strip tx_crc
To Next Page
Loading...