Secure packet capture to cloud

This feature enables you to capture packets from a device and securely stream them to an external telemetry data collector (for example, a cloud-based collector) for monitoring and analysis. Network professionals use real-time packet capture data to troubleshoot complex issues, including network and performance degradation, and poor end-user experience.

For secure packet capture, the maximum packet size is 512 bytes, including both the packet header and payload. To enable secure packet capture, include the /junos/system/linecard/packet-capture resource path in a Junos RPC call.

For ingress packet capture, include the packet-capture option in the firewall filter configuration:

edit firewall family family-name filter filter-name term match-term then packet-capture

This configuration sends packet capture sensor data to the collector. Remove the packet-capture configuration after the required data is collected. After capture is complete, ingress packets that match the filter conditions are trapped to the CPU and forwarded to the collector over a secure channel using the JTI-defined key-value format over a gRPC connection.

For egress packet capture on physical interfaces (ge-*, xe-*, mge-*, and et-*), include "packet-capture-telemetry," "egress," and "interface " at the [edit forwarding-options] hierarchy level. For example:

set forwarding-options packet-capture-telemetry egress interface ge-0/0/0

set forwarding-options packet-capture-telemetry egress interface ge-0/0/10

You can configure multiple interfaces for egress packet capture. When enabled, host-bound egress packets are captured and sent to the collector. Remove the configuration when packet capture is no longer required.