opapacketcapture (1) - Linux Man Pages

NAME

opapacketcapture

Starts capturing packet data.

To stop capture and trigger dump, use SIGINT or SIGUSR1. Program dumps packets to file and exits.

NOTE: Using opapacketcapture with large amounts of traffic can cause performance issues on the given host. Intel recommends you use opapacketcapture on hosts with lower packet rates and bandwidth.

Syntax

opapacketcapture [-o outfile] [-d devfile] [-f filterfile] [-t triggerfile] [-l triggerlag][-a alarm] [-p packets] [-s maxblocks] [-v] [-h]

Options

-h/--help
Produces full help text.

-o outfile
Output file for captured packets. Default = packetDump.pcap

-d devfile
Device file for capturing packets. Default = /dev/hfi1_diagpkt0

-f filterfile
File used for filtering. If absent, no filtering is done.

-t triggerfile
File used for triggering a stop capture. If absent, normal triggering is performed.

-l triggerlag
Number of packets to collect after trigger condition is met, before dumping data and exiting. Default = 10.

-a alarm
Number of seconds for alarm trigger to dump capture and exit.

-p packets
Number of packets for alarm trigger to dump capture and exit.

-s maxblocks
Number of blocks to allocate for ring buffer. Value is in Millions. Default = 2 which corresponds to 128 MiB because 1 block = 64 Bytes.

-v
Produces verbose output.

Example

# opapacketcapture
opapacketcapture: Capturing packets using 128 MiB buffer
^C
opapacketcapture: Triggered
Number of packets stored is 100

In the example above, opapacketcapture operates until CTRL+C is entered.