Description

Hi Team,


MX304 upgraded to Junos 24.4R1-S2.9, since then we noticed there is a lot of route record lookup failures / AS lookup failures for the inline-jflow.

Here is the Route Record Lookup Failures in MX304:


======


show services accounting status inline-jflow fpc-slot 0

 Flow information

  FPC Slot: 0

  Flow Packets: 11281035431, Flow Bytes: 9597268145284

  Active Flows: 52981, Total Flows: 3729256899

  Flows Exported: 7424499595, Flow Packets Exported: 1860432548

  Flows Inactive Timed Out: 3610148461, Flows Active Timed Out: 118872741

  Total Flow Insert Count: 3610384158


  IPv4 Flows:

  IPv4 Flow Packets: 11280938800, IPv4 Flow Bytes: 9597249820956

  IPv4 Active Flows: 52981, IPv4 Total Flows: 3729161553

  IPv4 Flows Exported: 7424308907, IPv4 Flow Packets exported: 1860241964

  IPv4 Flows Inactive Timed Out: 3610053117, IPv4 Flows Active Timed Out: 118872741

  IPv4 Flow Insert Count: 3610288812


  IPv6 Flows:

  IPv6 Flow Packets: 96631, IPv6 Flow Bytes: 18324328

  IPv6 Active Flows: 0, IPv6 Total Flows: 95346

  IPv6 Flows Exported: 190688, IPv6 Flow Packets Exported: 190584

  IPv6 Flows Inactive Timed Out: 95344, IPv6 Flows Active Timed Out: 0

  IPv6 Flow Insert Count: 95346


=====

> status inline-jflow fpc-slot 0      

 Status information

  FPC Slot: 0

  IPV4 export format: Version9, IPV6 export format: Version-IPFIX

  BRIDGE export format: Not set, MPLS export format: Not set

  IPv4 Route Record Count: 2053178, IPv6 Route Record Count: 428153, MPLS Route Record Count: 0

  Route Record Count: 2481331, AS Record Count: 393523

  Route-Records Set: Yes, Config Set: Yes

  Service Status: PFE-0: Steady PFE-1: Steady PFE-2: Steady PFE-3: Steady PFE-4: Steady PFE-5: Steady

  Using Extended Flow Memory?: PFE-0: No PFE-1: No PFE-2: No PFE-3: No PFE-4: No PFE-5: No

  Flex Flow Sizing ENABLED?: PFE-0: Yes PFE-1: Yes PFE-2: Yes PFE-3: Yes PFE-4: Yes PFE-5: Yes

  IPv4 MAX FLOW Count: 29360132, IPv6 MAX FLOW Count: 29360132

  BRIDGE MAX FLOW Count: 29360132, MPLS MAX FLOW Count: 29360132

  MAX supported Flow Table size: 80



Symptoms

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

Error information

FPC Slot: 0

Flow Creation Failures: 0

Route Record Lookup Failures: 1755473303, AS Lookup Failures: 1755473318

Export Packet Failures: 186774

Memory Overload: No, Memory Alloc Fail Count: 0


IPv4:

IPv4 Flow Creation Failures: 0

IPv4 Route Record Lookup Failures: 1755466585, IPv4 AS Lookup Failures: 1755466582

IPv4 Export Packet Failures: 186772


IPv6:

IPv6 Flow Creation Failures: 0

IPv6 Route Record Lookup Failures: 6718, IPv6 AS Lookup Failures: 6736

IPv6 Export Packet Failures: 2

Solution

It is a Day-1 issue for Inline Jflow feature on AFT based Line cards.

 

Trigger : Insert an Explicit Default Route(either BGP Injected or create static route manually or in any other form) where the traffic should get forwarded with this route.

Impact: The inline Jflow feature will not report right AS information in the exported IPFIX Records.

Fixed under PR1901369

 

Resolved-In

evo:25.2R2-EVO

evo:25.4R1-EVO

evo:26.1R1-EVO

junos:24.4R2-S2

junos:25.2R2

junos:25.4R1

Modification History

2025-10-15 : Article Created