Description

ACX7100 JFLOW not working

Symptoms

ACX7100 JFLOW/IPFIX not showing flows for input IPV4 flows. This issue is induced by having a mix of SFLOW and JFLOW.


Configuraiton: SFLOW

set protocols sflow agent-id x.x.x.x

set protocols sflow polling-interval 60

set protocols sflow inline-sampling

set protocols sflow sample-rate ingress 2000

set protocols sflow source-ip x.x.x.x

set protocols sflow collector x.x.x.x udp-port 20013

set protocols sflow interfaces et-0/0/0.0


JFLOW:

set forwarding-options sampling instance ipfix input rate 2000

set forwarding-options sampling instance ipfix family inet output flow-server x.x.x.x port 20013

set forwarding-options sampling instance ipfix family inet output flow-server x.x.x.x autonomous-system-type origin

set forwarding-options sampling instance ipfix family inet output flow-server x.x.x.x version-ipfix template ipv4

set forwarding-options sampling instance ipfix family inet output inline-jflow source-address x.x.x.x

set forwarding-options sampling instance ipfix family inet6 output flow-server x.x.x.x port 20013

set forwarding-options sampling instance ipfix family inet6 output flow-server x.x.x.x autonomous-system-type origin

set forwarding-options sampling instance ipfix family inet6 output flow-server x.x.x.x version-ipfix template ipv6

set forwarding-options sampling instance ipfix family inet6 output inline-jflow source-address x.x.x.x


set firewall family inet filter jflow interface-specific

set firewall family inet filter jflow term 1 then sample

set firewall family inet filter jflow term 1 then accept


set interfaces et-0/0/0 description INFRA::CRM1017605::pe-r-00.psg.uk

set interfaces et-0/0/0 speed 10g

set interfaces et-0/0/0 mtu 9192

set interfaces et-0/0/0 hold-time up 1000

set interfaces et-0/0/0 hold-time down 1000

set interfaces et-0/0/0 unit 0 family inet mtu 8192

set interfaces et-0/0/0 unit 0 family inet policer arp arp-policer-core

set interfaces et-0/0/0 unit 0 family inet address 185.75.28.248/31

set interfaces et-0/0/0 unit 0 family inet6 mtu 8192

set interfaces et-0/0/0 unit 0 family inet6 address 2001:a08:5000::155/126

set interfaces et-0/0/0 unit 0 family mpls

set interfaces et-0/0/1 mtu 9192

set interfaces et-0/0/1 hold-time up 1000

set interfaces et-0/0/1 hold-time down 1000

set interfaces et-0/0/1 unit 0 family inet mtu 8192

set interfaces et-0/0/1 unit 0 family inet filter input jflow

set interfaces et-0/0/1 unit 0 family inet address 185.75.28.80/31

set interfaces et-0/0/1 unit 0 family inet6 mtu 8192

set interfaces et-0/0/1 unit 0 family inet6 address 2001:a08:5000::159/126

set interfaces et-0/0/1 unit 0 family mpls




Example:

Interface et-0/0/0.0 => SFLOW ingress

Interface et-0/0/1.0 > added to Jflow with FWF for sample ingress.  


As sflow/jflow is sampling on ingress traffic it is see that JFLOW will not pick up flows. Deleting all of SFLOW does not change the behavior. A system reboot is needed to have JFLOW work correctly.


Example:

SFLOW:

labroot@h20-41# run show sflow collector 

Collector                 Udp-port  Dscp   Forwarding-Class        No. of samples

 address

x.x.x.x               20013    0    best-effort           941      


[edit]

labroot@h20-41# run show sflow collector   

Collector                 Udp-port  Dscp   Forwarding-Class        No. of samples

 address

x.x.x.x               20013    0    best-effort           944      


[edit]

labroot@h20-41# 



For JFLOW...no ingress flows are seen:


labroot@h20-41# run set cli timestamp 

Jan 13 13:13:31

CLI timestamp set to: %b %d %T


[edit]

labroot@h20-41# run show services accounting flow inline-jflow fpc-slot 0 | match "ipv4 Flows"   

Jan 13 13:13:33

  IPv4 Flows:

  IPv4 Flows Exported: 917

  IPv4 Flows Inactive Timed Out: 917, IPv4 Flows Active Timed Out: 0


labroot@h20-41# run show interfaces et-0/0/1.0 extensive 

Jan 13 13:13:58

 Logical interface et-0/0/1.0 (Index 1003) (SNMP ifIndex 606) (Generation 605590389824)

  Flags: Up SNMP-Traps Encapsulation: ENET2 DF

 Traffic statistics:

  Input bytes :      6039851838

  Output bytes :      6186644988

  Input packets:       3908317

  Output packets:       7812128

  Local statistics:

  Input bytes :        67392

  Output bytes :        103290

  Input packets:         754

  Output packets:         838

  Transit statistics:

  Input bytes :      6039784446       23744032 bps

  Output bytes :      6186541698       24109136 bps

  Input packets:       3907563         1921 pps

  Output packets:       7811290         3805 pps



labroot@h20-41# run show services accounting flow inline-jflow fpc-slot 0 | match "ipv4 Flows"   

Jan 13 13:14:27

  IPv4 Flows:

  IPv4 Flows Exported: 917

  IPv4 Flows Inactive Timed Out: 917, IPv4 Flows Active Timed Out: 0


[edit]

labroot@h20-41# 



Remove SFLOW completely and problem remains.


abroot@h20-41# delete protocols sflow 

Jan 13 13:14:53


[edit]

labroot@h20-41# commit 

Jan 13 13:14:54

commit complete


[edit]

labroot@h20-41# run show sflow collector                              

Jan 13 13:15:05


[edit]

labroot@h20-41# run show services accounting flow inline-jflow fpc-slot 0 | match "ipv4 Flows"   

Jan 13 13:15:09

  IPv4 Flows:

  IPv4 Flows Exported: 917

  IPv4 Flows Inactive Timed Out: 917, IPv4 Flows Active Timed Out: 0


[edit]

labroot@h20-41# run show services accounting flow inline-jflow fpc-slot 0 | match "ipv4 Flows"   

Jan 13 13:15:12

  IPv4 Flows:

  IPv4 Flows Exported: 917

  IPv4 Flows Inactive Timed Out: 917, IPv4 Flows Active Timed Out: 0



So far a reboot of the ACX clears this condition.  


labroot@h20-41> show services accounting flow inline-jflow fpc-slot 0 | match "ipv4 Flows" 

Jan 13 13:21:41

  IPv4 Flows:

  IPv4 Flows Exported: 188

  IPv4 Flows Inactive Timed Out: 188, IPv4 Flows Active Timed Out: 0


labroot@h20-41> show services accounting flow inline-jflow fpc-slot 0 | match "ipv4 Flows"   

Jan 13 13:21:44

  IPv4 Flows:

  IPv4 Flows Exported: 194

  IPv4 Flows Inactive Timed Out: 194, IPv4 Flows Active Timed Out: 0





Solution

Temporary work around:

1) remove SFLOW configuation (this alone will not resolve JFLOW issue)

2) reboot ACX -request system reboot.

Modification History

2025-01-13 : Article Created