jFlow v9 on MX960

Following configuration comes from MX960 using Junos 15.1F6. Sampling rate set to 1:300 packets and configuration is as follows, just IPs of Collector and router needs to be added.

You need to set the option to let the router know where to send data and which format.

set forwarding-options sampling input rate 300
set forwarding-options sampling family inet output flow-server a.b.c.d autonomous-system-type peer
set forwarding-options sampling family inet output flow-server a.b.c.d no-local-dump
set forwarding-options sampling family inet output flow-server a.b.c.d source-address b.c.d.e
set forwarding-options sampling family inet output flow-server a.b.c.d version9 template ipv4

Configure Flow monitoring templates and timeouts

set services flow-monitoring version9 template ipv4 flow-active-timeout 60
set services flow-monitoring version9 template ipv4 flow-inactive-timeout 60
set services flow-monitoring version9 template ipv4 template-refresh-rate seconds 300
set services flow-monitoring version9 template ipv4 option-refresh-rate seconds 300
set services flow-monitoring version9 template ipv4 ipv4-template
set services flow-monitoring version9 template ipv6 flow-active-timeout 60
set services flow-monitoring version9 template ipv6 flow-inactive-timeout 60
set services flow-monitoring version9 template ipv6 template-refresh-rate seconds 300
set services flow-monitoring version9 template ipv6 option-refresh-rate seconds 300
set services flow-monitoring version9 template ipv6 ipv6-template
set services flow-monitoring version9 template mpls flow-active-timeout 60
set services flow-monitoring version9 template mpls flow-inactive-timeout 60
set services flow-monitoring version9 template mpls template-refresh-rate seconds 300
set services flow-monitoring version9 template mpls option-refresh-rate seconds 300
set services flow-monitoring version9 template mpls mpls-ipv4-template label-position 1
set services flow-monitoring version9 template mpls mpls-ipv4-template label-position 2
set services flow-monitoring version9 template mpls mpls-ipv4-template label-position 3

To apply it to all interfaces you can configure it on firewall, ideally as a first rule to sample all the traffic

user1@router1.re0> show configuration firewall family inet filter peer1_inbound interface-specific;
term sample {
    then {
        sample;
        next term;
    }
}