Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    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:

    • The packet filter traces both IPv4 and IPv6 traffic if only port is specified.
    • The packet filter traces IPv4, IPV6, and non-IP traffic if only interface is specified.

    Published: 2012-06-29