...
BGP Process crashed with below logs RP/0/RP0/CPU0:Apr 26 17:38:40.027 AEST: dumper[69070]: %OS-SYSLOG-6-LOG_INFO : Dumping core /misc/scratch/core/bgp_7664.by.11.20230426-173839.xr-vm_node0_RP0_CPU0.3b0d6.core.gz RP/0/RP0/CPU0:Apr 26 17:38:48.963 AEST: tcp[404]: %OS-MMAP_PEER-6-RECV : Failed to recv mmap reply for process 5060 from 7664: Connection reset by peer RP/0/RP0/CPU0:Apr 26 17:38:48.963 AEST: bpm[1091]: %ROUTING-BGP-5-ASYNC_IPC_STATUS : bpm-default:(A)inst-id 0, Connection Closed RP/0/RP0/CPU0:Apr 26 17:38:48.968 AEST: processmgr[51]: bgp(1) (jid 1076) (pid 7664) (fail_count 1) abnormally terminated, restart scheduled RP/0/RP0/CPU0:Apr 26 17:38:48.998 AEST: tcp[404]: %OS-MMAP_PEER-7-CONNECT : Connect from process 5060 to 7664 skipped: Connection refused RP/0/RP0/CPU0:Apr 26 17:38:50.418 AEST: bpm[1091]: %ROUTING-BGP-5-ASYNC_IPC_STATUS : bpm-default:(A)inst-id 0, Connection Open RP/0/RP0/CPU0:Apr 26 17:38:50.728 AEST: bgp[1076]: %ROUTING-BGP-5-ASYNC_IPC_STATUS : default, process instance 1:(A)inst-id 0, Connection Establised RP/0/RP0/CPU0:Apr 26 17:38:51.418 AEST: bgp[1076]: %ROUTING-BGP-5-ASYNC_IPC_STATUS : default:(A)inst-id 0, ### Calvados Broadcom SDK Information Refpoint : thirdparty/broadcom-pp/fabric/release@tp-main/741 Built By : ramadura Build On : Mon Sep 7 00:37:10 PDT 2020 Build Host : sjc-ads-3569 Workspace : /auto/panini-projs2/brcm-sdk-6.5.19/tp-155 Workspace EFR : thirdparty EFR-00000409602 Lineup BRCM SDK Version : sdk-6.5.19 KBP SDK Version : KBP SDK 1.5.12.1 KBP SDK Tarball : KBP SRC Tarball : Signal information: Program terminated with signal 11, Segmentation fault. Faulting thread: 8102 Registers for Thread 8102 rax: 0x0 rbx: 0x7fae76efe028 rcx: 0x7faea890ae18 rdx: 0x7fae747ae52c rsi: 0x7fae747ae52c rdi: 0x7faea8964668 rbp: 0x7fae747ae310 rsp: 0x7fae747ae310
Configuration of flowspec AFI under BGP VRF (vrf under 'router bgp ') caused this issue. However, this issue is not limited to flowspec AFI and can occur for the following AFIs configured under BGP VRF. ipv4 unicast ipv4 multicast ipv4 mvpn ipv4 flowspec ipv6 unicast ipv6 multicast ipv6 mvpn ipv6 flowspec
None
It’s a Day-1 issue. It's a PI issue. So applicable to all platforms. So far it was reported only once. So the occurrence is rare.