The following error message is seen after upgrading qfx5120-48y-8c to 20.4R3-S6.3 flex:
fpc0 Failed to get ifl for ifl index = 584
The following error message is seen after upgrading qfx5120-48y-8c to 20.4R3-S6.3 flex.
Same logs are observed from the PFE:
[Fri Jan 27 20:19:18.613 LOG: Err] Failed to get ifl for ifl index = 584
[Fri Jan 27 20:19:18.822 LOG: Debug] brcm_pkt_is_mac2me:1157 Failed to get ifl for ifl index = 584
[Fri Jan 27 20:19:18.822 LOG: Err] Failed to get ifl for ifl index = 584
[Fri Jan 27 20:19:25.633 LOG: Debug] PFESVCS: Input IFL not found, iif 7 proto 2
[Fri Jan 27 20:19:26.759 LOG: Debug] PFESVCS: Input IFL not found, iif 9 proto 2
[Fri Jan 27 20:19:28.684 LOG: Debug] brcm_pkt_is_mac2me:1157 Failed to get ifl for ifl index = 584
[Fri Jan 27 20:19:28.684 LOG: Err] Failed to get ifl for ifl index = 584
You may see the following error message in a VXLAN environment. This can happen when the device receives a DHCP packet via a remote vtep and an L3 interface (IRB) is not assiged on the egress interface.
Even though there is no DHCP configuration, the packet injection happens and it fails to get an IFL index as there is no IRB interface on the egress interface.
Oct 7 16:31:51.137 2022 d16-25 : %PFE-3: fpc0 Failed to get ifl for ifl index = 640
RESOLVED IN
Junos 20.4R3-S8, 21.2R3-S6, 21.4R3-S4, 22.2R3-S1, 22.3R3, 22.4R3, 23.1R2, 23.2R1, 23.2R2, 23.3R1
WORKAROUND
You can ignore the error message or you may assign an L3 interface (IRB) to the vlan. The DHCP packet is forwarded to the egress interfaces as expected.
TRIGGERS
This issue might be seen if the following conditions are met:
* On QFX 5K series platform and EX4600 series.
* In VXLAN environment
* Receiving DHCP packet via remote vtep
* No IRB interface on the egress interface.
PR1721318: https://prsearch.juniper.net/problemreport/PR1721318
Jun 12, 2023: Version 1