Description

Customer reporting flow creating failures in MX304. Sampling is not exporting.

mx304 Junos: 23.2R1-S2.5


> show services accounting errors inline-jflow fpc-slot 0 

IPv4:

IPv4 Flow Creation Failures: 134399857

IPv4 Route Record Lookup Failures: 2, IPv4 AS Lookup Failures: 2

IPv4 Export Packet Failures: 0


IPv6:

IPv6 Flow Creation Failures: 9339571

IPv6 Route Record Lookup Failures: 0, IPv6 AS Lookup Failures: 0

IPv6 Export Packet Failures: 0


> show services accounting errors inline-jflow fpc-slot 0 

IPv4:

IPv4 Flow Creation Failures: 134428923

IPv4 Route Record Lookup Failures: 2, IPv4 AS Lookup Failures: 2

IPv4 Export Packet Failures: 0


IPv6:

IPv6 Flow Creation Failures: 9342451

IPv6 Route Record Lookup Failures: 0, IPv6 AS Lookup Failures: 0

IPv6 Export Packet Failures: 0



If we restart FPC0 , Then flows are working for 4 hours and again flow-creation failures are increasing and flows are reduced to 3 active flow.


> show services accounting flow inline-jflow fpc-slot 0 

Flow information FPC Slot: 0 Flow Packets: 311118, Flow Bytes: 183288063 

Active Flows: 42873, Total Flows: 242007 Flows Exported: 330288, 

Flow Packets Exported: 86466 Flows Inactive Timed Out: 91869, 

Flows Active Timed Out: 107046 Total Flow Insert Count: 134961


IPv4 Flows:

IPv4 Flow Packets: 297077, IPv4 Flow Bytes: 172392994

IPv4 Active Flows: 38862, IPv4 Total Flows: 232497

IPv4 Flows Exported: 324120, IPv4 Flow Packets exported: 82014

IPv4 Flows Inactive Timed Out: 89148, IPv4 Flows Active Timed Out: 104270

IPv4 Flow Insert Count: 128227


IPv6 Flows:

IPv6 Flow Packets: 14041, IPv6 Flow Bytes: 10895069

IPv6 Active Flows: 4011, IPv6 Total Flows: 9510

IPv6 Flows Exported: 6168, IPv6 Flow Packets Exported: 4452

IPv6 Flows Inactive Timed Out: 2721, IPv6 Flows Active Timed Out: 2776

IPv6 Flow Insert Count: 6734


Symptoms

core5> show services accounting flow inline-jflow fpc-slot 0

Flow information FPC Slot: 0 Flow Packets: 26448654, Flow Bytes: 21452905631

Active Flows: 3, Total Flows: 21770623 Flows Exported: 30806378,

Flow Packets Exported: 8534199 Flows Inactive Timed Out: 10461297,

Flows Active Timed Out: 11288953 Total Flow Insert Count: 10481670


IPv4 Flows: IPv4 Flow Packets: 17044627, IPv4 Flow Bytes: 12648289213

IPv4 Active Flows: 3, IPv4 Total Flows: 14621280

IPv4 Flows Exported: 23354358, IPv4 Flow Packets exported: 5958843

IPv4 Flows Inactive Timed Out: 6972250, IPv4 Flows Active Timed Out: 7633500 IPv4 Flow Insert Count: 6987780


IPv6 Flows: IPv6 Flow Packets: 9404027, IPv6 Flow Bytes: 8804616418

IPv6 Active Flows: 0, IPv6 Total Flows: 7149343

IPv6 Flows Exported: 7452020, IPv6 Flow Packets Exported: 2575356

IPv6 Flows Inactive Timed Out: 3489047, IPv6 Flows Active Timed Out: 3655453 IPv6 Flow Insert Count: 3493890


 

Solution

On MX304 and MX platform with MPC11 line cards and inline jflow sampling configured, the Inline Jflow stops learning new flows as flows created on odd slices are not cleared when they time out, hence the values become large enough and no new flows will be learned.

https://prsearch.juniper.net/problemreport/PR1742752

Resolved In

Evo Junos

23.2R2-EVO 23.2R2

23.3R1-EVO 23.3R1

23.3R2-EVO 23.3R2

Modification History

2025-09-29 : Article Created