Packet Capture Module Operations
Some operations are dependent on your RBAC assignments, the state of the module, and the state of capture jobs. The UI
User Interface. The visual components and controls that users interact with to access features and manage the system. will enforce restrictions by either dimming buttons when the operation is not available or via pop-up messages that require your approval.
New Capture Job
Use the new capture job
Writes network packets to local disk for continuous or on-demand captures. button to start a capture on a selected device. When you start a capture job, you provide a name for the capture job and select a capture profile
A configuration template that defines packet capture parameters.. The capture profile determines which packets are captured and how the capture behaves, including whether it runs as a continuous capture or an on-demand capture. The capture job writes network packets to local disk on the device.
The Packet Capture Module supports up to three concurrent active captures per device. Each capture job must use a different capture profile with unique filters and size, time, or packet limits. Capture jobs can be stopped and then started again using the same capture buffer.
The UI blocks creating a capture on a module older than 26.10.1 when the profile uses packet slicing, or when a maximum packet size is set. It also blocks creating or starting a capture when the profile snap length is above the maximum packet size and your role cannot configure Global Settings. Upgrade the module, or choose a profile the device can run. See Packet Capture Configuration Settings.
Start Capture
Click this button to resume a previously stopped capture job on the selected device.
Rename Capture
You can rename either an active or inactive capture job.
Stop Capture
For any active capture, you have the option of stopping the capture job. The packets remain in this capture job on the end point device until you either harvest
The process of retrieving PCAP files from devices and transferring them to a customer-provided repository for analysis. from this capture job, or you delete the capture job.
Delete Capture
You can delete an active or stopped capture to free up disk space. The UI will prompt you with a confirmation message.
Harvest Packets
The Harvest operation supports the following harvest modes:
-
Harvest the last
nnminutes of time, working backward from the current time, or a configured time range. -
Harvest the entire contents of the continuous capture rolling buffer.
You can also configure the following optional fields:
-
Note: Packet slicing on harvest requires module version 26.10.1 or later. On an older module, if no maximum packet size is set, the harvest uses full packets and Snap length is not available. If a maximum packet size is set, the harvest is blocked until the module is upgraded.
Snap length (optional): Set a tighter limit on how many bytes of each packet are written to the harvested PCAP
Packet Capture. A file format that contains captured network packet data, typically used for network analysis and troubleshooting.. This re-slices packets during export. Enter 0 to apply no extra limit. The harvest cannot recover bytes that the capture did not store. Any other value must be from 34 to 65536 bytes, cannot be higher than the capture profile snap length, and cannot be higher than the maximum packet size unless your role can configure Global Settings. The field starts at the maximum packet size, or at the capture profile snap length when that value is lower. See Packet Capture Configuration Settings. -
Harvest BPF Filter: Apply a Berkeley Packet Filter (BPF
Berkeley Packet Filter. A syntax for selecting which network packets are captured or harvested based on protocol, address, port, and other packet attributes.) at harvest (query) time, not just at capture time. The harvest-time BPF
Berkeley Packet Filter. A syntax for selecting which network packets are captured or harvested based on protocol, address, port, and other packet attributes. is additive. It narrows what is extracted from the already-stored packet capture buffer. It does not replace the capture-time BPF
Berkeley Packet Filter. A syntax for selecting which network packets are captured or harvested based on protocol, address, port, and other packet attributes.. This option allows you to retrieve a targeted subset of already-stored packets without recapturing. -
Note (optional field): Add a note to the harvest to provide additional context. The contents of this field are displayed in the harvest list. Hover over the harvest name in harvest history to view the note.
Viewing History of Harvest Commands
Just below the list of capture jobs for each device, you will see a historical reference of harvest operations that have been executed for this device. Each harvest entry includes a hyperlink to your customer-provided repository, or a chain icon for CIFS and Local harvests. For details on harvest notes, BPF
Berkeley Packet Filter. A syntax for selecting which network packets are captured or harvested based on protocol, address, port, and other packet attributes., and accessing harvested files, see Lists of Harvests.