Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?




Hierarchy Level


PTX10004, PTX10008, and PTX10016 devices running Junos OS Evolved Release 22.1R1 can provide an SDN-based backbone (data center interconnect) for target networks. It works by using a firewall filter to redirect matching packets, via a P4Runtime agent running in Junos OS Evolved on the Routing Engine, to a P4 controller that is also running on the PTX router. (The P4Runtime agent registers with the Juniper Extension Toolkit (JET) services daemon (JSD) to open the gRPC connections and listen for P4 requests from clients.)

You can match:

  • IPv4, IPv6, UDP, and TCP protocol packets according to the destination IP address

  • Google Discovery protocol packets (matched by specifying VLAN ID: 4000, EtherType: 0x6007)

  • traceroute redirect packets (matched by specifying TTL=0 for IPv4 and TTL=1 for IPv6)

The P4Runtime agent supports packet I/O from network devices to the SDN controller, as well as OpenConfig for switch configuration, and gRIBI for route programming.

To configure inline-monitoring services for packet redirects to the P4 controller, you need to configure inline-monitoring, create an instance, and set the instance type to controller P4, as shown here:

And configure a firewall filter action to redirect matching packets to your instance, as shown here:

Optionally, you may also want to modify the DDoS protocol parameters:

or disable DDoS, as the case may be:

Controller type:



Select this option to have the P4Runtime agent send packets to the P4 controller (instead of the default Routing Engine).


Select this option to send packets to the default Routing Engine.

Required Privilege Level

system—To view this statement in the configuration.

system-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Evolved Release 22.1R1.