Related Documentation
- SRX Series
- Debugging the Data Path (CLI Procedure)
- Additional Information
- Junos OS Feature Support Reference for SRX Series and J Series Devices

Understanding Data Path Debugging for SRX Series Devices
Data path debugging provides tracing and debugging at multiple processing units along the packet-processing path. The packet filter can be executed with minimal impact to the production system.
In data path debugging, a packet goes through multiple Services Processing Units (SPUs). At the same time, several Flexible PIC Concentrator (FPC) I/O cards (IOCs) provide EZchip ingress and egress traffic management. Junos OS supports IOC for filter-based, per-packet counting and logging to record the processing path of a packet. Only the matched packets are traced by the IOC EZchip ingress, EZchip egress, load-balancing thread (LBT), and packet-ordering thread (POT).
The following events are defined in the packet-processing path:
- ezchip ingress
- ezchip egress
- spu.lbt
- spu.pot
![]() | The packet-filtering behavior for the port and interface options is as follows:
|
Related Documentation
- SRX Series
- Debugging the Data Path (CLI Procedure)
- Additional Information
- Junos OS Feature Support Reference for SRX Series and J Series Devices



