Customer reported multicast routes are failing to install. They were observing below logs.
Jul 26 23:33:40 2024 LAB fpc0 brcm_ipmc_stat_get:3925pkt stat counter get failedwith error (-7:Entry not found)
Jul 26 23:33:40 2024 LAB fpc0 brcm_ipmc_get_multicast_stats:4086brcm_ipmc_stat_get failed for Grp IP:239.17.111.82, Src IP:192.168.15.117
Jul 26 23:33:40 2024 LAB fpc0 brcm_rt_stats:2967brcm_ipmc_stat_get failure
Jul 26 23:33:43 2024 LAB fpc0 BRCM_AGE:brcm_rt_nh_update_age(),64: Failure on traversing the L3 IPMC table -7 -> Entry not found
Jul 26 23:34:13 2024 LAB fpc0 BRCM_AGE:brcm_rt_nh_update_age(),64: Failure on traversing the L3 IPMC table -7 -> Entry not found
Jul 26 23:34:41 2024 LAB fpc0 brcm_ipmc_stat_get:3925pkt stat counter get failedwith error (-7:Entry not found)
Jul 26 23:34:41 2024 LAB fpc0 brcm_ipmc_get_multicast_stats:4086brcm_ipmc_stat_get failed for Grp IP:239.17.111.82, Src IP:192.168.15.117
Below logs are observed followed by parity errors.
Jul 26 20:01:05 2024 LAB fpc0 Parity error..
Jul 26 20:01:05 2024 LAB fpc0 Error in: SBUS transaction.
Jul 26 20:01:05 2024 LAB fpc0 Blk: 1, Pipe: 0, Address: 0x241003cb, base: 0x4, stage: 9, index: 971
Jul 26 20:01:05 2024 LAB fpc0 Unit 0: mem: 2095=L3_ENTRY_IPV4_UNICAST blkoffset:10
Jul 26 20:01:05 2024 LAB fpc0 Unit 0: CACHE_RESTORE: L3_ENTRY_IPV4_MULTICAST[2091] blk: ipipe0 index: 485 : [1][24100000]
Jul 26 20:01:05 2024 LAB fpc0 Unit 0: CACHE_RESTORE: L3_ENTRY_IPV6_UNICAST[2103] blk: ipipe0 index: 485 : [1][24100000]
Jul 26 20:01:05 2024 LAB fpc0 Unit: 0
Jul 26 20:01:05 2024 LAB fpc0 Multiple:
Jul 26 20:01:05 2024 LAB fpc0 Mem:
Jul 26 20:01:05 2024 LAB fpc0 Error in: SOP cell.
Jul 26 20:01:05 2024 LAB fpc0 Blk: 1, Pipe: 0, Address: 0x2410034b, base: 0x4, stage: 9, index: 843
Jul 26 20:01:05 2024 LAB fpc0 SER caused packet drop.
Jul 26 20:01:05 2024 LAB fpc0 Unit 0: CACHE_RESTORE: L3_ENTRY_IPV4_MULTICAST[2091] blk: ipipe0 index: 421 : [1][24100000]
Jul 26 20:01:05 2024 LAB fpc0 Unit 0: CACHE_RESTORE: L3_ENTRY_IPV6_UNICAST[2103] blk: ipipe0 index: 421 : [1][24100000]
Jul 26 20:01:33 2024 LAB fpc0 BRCM_AGE:brcm_rt_nh_update_age(),64: Failure on traversing the L3 IPMC table -7 -> Entry not found
Jul 26 20:01:40 2024 LAB fpc0 brcm_ipmc_stat_get:3925pkt stat counter get failedwith error (-7:Entry not found)
Jul 26 20:01:40 2024 LAB fpc0 brcm_ipmc_get_multicast_stats:4086brcm_ipmc_stat_get failed for Grp IP:239.17.111.82, Src IP:192.168.15.117
Jul 26 20:01:40 2024 LAB fpc0 brcm_rt_stats:2967brcm_ipmc_stat_get failure
Jul 26 20:02:03 2024 LAB fpc0 BRCM_AGE:brcm_rt_nh_update_age(),64: Failure on traversing the L3 IPMC table -7 -> Entry not found
Jul 26 20:02:33 2024 LAB fpc0 BRCM_AGE:brcm_rt_nh_update_age(),64: Failure on traversing the L3 IPMC table -7 -> Entry not found
Jul 26 20:02:40 2024 LAB fpc0 brcm_ipmc_stat_get:3925pkt stat counter get failedwith error (-7:Entry not found)
Jul 26 20:02:40 2024 LAB fpc0 brcm_ipmc_get_multicast_stats:4086brcm_ipmc_stat_get failed for Grp IP:239.17.111.82, Src IP:192.168.15.117
And in PFE we will not find this record.
On QFX5100 platform, some of the IPv4 multicast routes in the PFE might fail to install and update during normal operations, and as a result, multicast traffic from impacted groups traversing through the device might be silently discarded. Workaround Reboot the FPC facing these errors.
Resolved-In
junos:14.1X53-D130 junos:14.1X53-D47 junos:15.1R7 junos:15.1R8 junos:16.1R7 junos:16.1R8 junos:16.2R3 junos:17.1R3 junos:17.2R3 junos:17.3R3 junos:17.4R2 junos:18.1R2 junos:18.2R1 junos:18.2X75-D5
You can see below PR for more details. https://prsearch.juniper.net/problemreport/PR1320723