Packet Capture Configuration Settings

Use the Packet Capture Settings to configure your Packet Capture Module environment.

There are three groups of settings:

  1. Capture Profiles

  2. Storage Profiles

  3. Global Settings

Capture Profiles

A capture profileClosed A configuration template that defines packet capture parameters. defines the parameters used when starting a capture jobClosed Writes network packets to local disk for continuous or on-demand captures.. It includes:

When you start a capture job, you select a capture profile. The job uses that profile's settings to determine what packets are captured and how the capture behaves.

You can edit and delete created profiles by clicking [...].

Click Create New Capture Profile to open the Create Capture Profile pop-up. This pop-up has a few sections of configurable settings:

Create Capture Profile dialog with Name, Snap length, Capture Filter, Capture Limits, and Capture Options

Name

Set a name for this profile.

Snap length

Note: Packet slicing requires module version 26.10.1 or later on the device that runs the capture. You can save a snap length before every device is upgraded. You cannot create a capture that uses packet slicing on an older module. If a maximum packet size is set, you also cannot create a capture on an older module, because that module stores full packets and would exceed the maximum.

Snap length sets how many bytes of each packet are stored. Storing fewer bytes than the full packet is packet slicing. Enter 0 to store full packets. To slice packets, enter a value from 34 to 65536 bytes.

The snap length must be less than or equal to Maximum packet size (snap length) in Global Settings, unless your role can configure Global Settings. A role that can configure Global Settings can save a snap length above that maximum. For the roles that can configure Global Settings, see Built-in Roles.

When a maximum packet size is set, a new profile defaults to that maximum. When the maximum is No limit, a new profile defaults to 0.

Capture Filter (Optional)

Set a BPFClosed Berkeley Packet Filter. A syntax for selecting which network packets are captured or harvested based on protocol, address, port, and other packet attributes. expression to filter captured packets.

Capture Limits

  1. Set the maximum size of the continuous capture rolling buffer, in Megabytes.

  2. Set the maximum time for the capture, in seconds.

  3. (Conditional) If you are not creating a continuous capture profile, set the maximum packets. See Understanding Continuous Capture vs. On-Demand for more information about continuous versus on demand captures.

Capture Options

  1. Enable or disable automatically creating a capture job with this profile on new devices. This setting doesn't impact existing devices.

  2. Enable or disable continuous capture. Enabling this setting disables the Max Packets field and puts the capture job in continuous capture mode.

How Profile Changes Are Propagated to Modules

When you edit a capture profile, changes to certain settings are automatically propagated to all capture jobs that use that profile. The system identifies all active captures using the modified profile and updates them with the new settings.

Note: Only active capture jobs are impacted. If a job is in a stopped state, the changes only apply when the job is restarted.

The following profile changes trigger automatic updates to affected capture jobs:

Changes to the profile name or the auto-start setting do not trigger updates to existing capture jobs. These settings only affect how the profile appears in the UI and whether new devices automatically start captures with this profile.

When a profile change is detected, the system:

  1. Identifies all capture jobs currently using the modified profile

  2. Validates that all affected devices support the new profile settings

  3. Creates update commands for each affected capture job

  4. Sends notifications to the Packet Capture Modules on the affected devices

  5. Sets the capture job status to Pending while the update is processed

The modules receive the notification and apply the updated profile settings to their capture jobs. If a module is temporarily unavailable, the update command remains in a pending state and will be processed when the module next reports its status.

Lowering Maximum packet size (snap length) can also update capture profiles. That update is described in Maximum packet size. It is separate from editing a profile.

Storage profile changes do not propagate to modules. Storage profiles are only used when you issue a harvest command, and the profile settings are read at that time.

Storage Profiles

A storage profileClosed A configuration that defines where the stores PCAP files, specifying the storage type and connection details for customer-managed repositories. defines where harvested PCAPClosed Packet Capture. A file format that contains captured network packet data, typically used for network analysis and troubleshooting. files are uploaded. It includes:

  • Storage type

  • Connection details (URLs, credentials, etc.)

When you issue a harvestClosed The process of retrieving PCAP files from devices and transferring them to a customer-provided repository for analysis. command, you select a storage profile. The Packet Capture Module uploads the PCAP file directly from the endpoint device to the configured repository. The Web UI stores metadata and links to the files but does not store the files themselves.

PCAP files are stored in customer managed repositories.

Click Create New Storage Profile to open the Storage Profile pop-up. This pop-up has five configurable settings:

  1. Create a Profile Name.

  2. Set the Storage Type. See Storage Profile Types for information about supported storage types and configuration settings.

You can edit and delete created profiles by clicking [...].

Global Settings

Global Settings with the free disk space threshold and Maximum packet size set to a custom limit

Global Settings apply to every device. Only a role that can configure Global Settings can change these values. See Built-in Roles.

Free disk space

Set the minimum percent of free disk space that should be maintained on the device at all times.

The module monitors disk space and if the percentage of free space falls below the setting, the Packet Capture Module will stop all captures. New capture attempts will fail until you free up disk space.

HarvestClosed The process of retrieving PCAP files from devices and transferring them to a customer-provided repository for analysis. commands will evaluate available disk space against this percentage and will fail the harvest request if there is not enough disk space to hold the estimated size of the PCAP to be harvested.

Maximum packet size

Maximum packet size (snap length) sets the upper limit for snap length on capture profiles and harvests. Choose No limit to allow any valid snap length. No limit is the default. Choose Custom limit and enter a value from 34 to 65535 bytes.

Users who cannot configure Global Settings must keep capture profile and harvest snap lengths at or below this maximum. Users who can configure Global Settings can save a higher snap length.

When you lower the maximum and one or more capture profiles would exceed it, the Confirm maximum packet size change dialog lists the affected profiles and running captures. Click Update settings and profiles to apply the change. Click Cancel to leave the current maximum in place.

  • Profiles used only on modules version 26.10.1 or later are updated automatically. The new snap length is applied the next time each device reports status. Running captures are not stopped.

  • Profiles that are also used on older modules are not changed automatically. Upgrade those modules to 26.10.1 or later, or remove the captures on those devices, and then set the snap length on each profile. For how a saved profile change reaches a running capture, see How Profile Changes Are Propagated to Modules.