Hello everyone.
Recently switched to the ASR 9006 runing on IOS XR Version 6.4.2 and faced with bgp process crashing.
Crashed pid:16695594 (pkg/bin/bgp) Time:Wed Mar 27 22:17:30 2019
Thread:21 received signal:11 - SIGSEGV. Segmentation fault. Sender:pkg/bin/bgp pid:16695594
Signal specific information: Signal code 0 - Unknown SIGSEGV code. Accessed BadAddr 0x0 at PC 0xffffffff.
Core dump file name:dumper_harddisk:/dumper/bgp_1060.by.bgp.20190327-221730.node0_RSP1_CPU0.x86.Z
Stack Trace
#0 0x429082c
#1 0xf2d6a19
#2 0xa19d2de
#3 0xa19d664
#4 0xf2d5d45
#5 0x429180d
#6 0x428bf30
#7 0xa1f2cbf
#8 0xa1f0ce8
#9 0xe7b355c
#10 0x4258d6e
Registers info
EDI ESI EBP(fp) EXX
R0 00000001 254e9ed8 03b8bcb0 fc5e6cd0
EBX EDX ECX EAX
R4 00000000 00000000 25451f48 00000064
EIP(pc) CS EFL ESP
R8 0429082c 000000f3 00011202 03b8bc60
SS
R12 000000fb
Also there are messages about disabled NSR for one of our neighbours in log. Only this peer is flapping periodicaly.
RP/0/RSP0/CPU0:2019 Apr 5 00:04:36.756 SAMST: tcp[451]: %IP-TCP_NSR-5-DISABLED : MF:179 <-> MF:56959:: NSR disabled for TCP connection because Retransmission threshold exceeded
RP/0/RSP0/CPU0:2019 Apr 5 00:04:36.756 SAMST: bgp[1060]: %ROUTING-BGP-3-NBR_NSR_DISABLED : NSR disabled on neighbor MF due to 'ip-tcp' detected the 'warning' condition 'NSR is down because the retransmission threshold exceeded (probably because downstream RP is not healthy)'
RP/0/RSP1/CPU0:2019 Apr 5 00:04:36.757 SAMST: bgp[1060]: %ROUTING-BGP-5-NBR_NSR_DISABLED_STANDBY : NSR disabled on neighbor MF on standby RP due to Peer closing down the session (VRF: default)
RP/0/RSP0/CPU0:2019 Apr 5 00:07:36.760 SAMST: bgp[1060]: %ROUTING-BGP-3-IO_INITSYNC_SESSION_FAILED : No error - for session, retry
RP/0/RSP1/CPU0:2019 Apr 5 00:07:36.760 SAMST: bgp[1060]: %ROUTING-BGP-5-IO_INITSYNC_FAILED : No such file or directory - set id 1
RP/0/RSP0/CPU0:2019 Apr 5 00:09:06.764 SAMST: bgp[1060]: %ROUTING-BGP-3-IO_INITSYNC_SESSION_FAILED : 'ip-tcp' detected the 'warning' condition 'NSR session was closed on standby' - for session, retry
RP/0/RSP1/CPU0:2019 Apr 5 00:09:06.764 SAMST: bgp[1060]: %ROUTING-BGP-5-IO_INITSYNC_FAILED : No such file or directory - set id 1
RP/0/RSP0/CPU0:2019 Apr 5 00:10:36.768 SAMST: bgp[1060]: %ROUTING-BGP-3-IO_INITSYNC_SESSION_FAILED : 'ip-tcp' detected the 'warning' condition 'NSR session was closed on standby' - for session, retry
RP/0/RSP1/CPU0:2019 Apr 5 00:10:36.768 SAMST: bgp[1060]: %ROUTING-BGP-5-IO_INITSYNC_FAILED : No such file or directory - set id 1
RP/0/RSP0/CPU0:2019 Apr 5 00:12:06.772 SAMST: bgp[1060]: %ROUTING-BGP-3-IO_INITSYNC_SESSION_FAILED : 'ip-tcp' detected the 'warning' condition 'NSR session was closed on standby' - for session, retry
RP/0/RSP1/CPU0:2019 Apr 5 00:12:06.773 SAMST: bgp[1060]: %ROUTING-BGP-5-IO_INITSYNC_FAILED : No such file or directory - set id 1
RP/0/RSP0/CPU0:2019 Apr 5 00:48:20.323 SAMST: bgp[1060]: %ROUTING-BGP-5-ADJCHANGE_DETAIL : neighbor MF Down - Peer closing down the session (VRF: default; AFI/SAFI: 1/1) (AS: 31133)
RP/0/RSP1/CPU0:2019 Apr 5 00:48:20.324 SAMST: bgp[1060]: %ROUTING-BGP-5-NBR_NSR_DISABLED_STANDBY : NSR disabled on neighbor MF on standby RP due to Peer closing down the session (VRF: default)
RP/0/RSP1/CPU0:2019 Apr 5 02:04:27.826 SAMST: dumper[61]: %OS-DUMPER-7-DUMP_REQUEST : Dump request for process pkg/bin/bgp
RP/0/RSP1/CPU0:2019 Apr 5 02:04:27.827 SAMST: dumper[61]: %OS-DUMPER-7-DUMP_ATTRIBUTE : Dump request with attribute 7 for process pkg/bin/bgp
RP/0/RSP1/CPU0:2019 Apr 5 02:04:27.827 SAMST: dumper[61]: %OS-DUMPER-4-SIGSEGV : Thread 22 received SIGSEGV - Segmentation Fault
RP/0/RSP1/CPU0:2019 Apr 5 02:04:27.827 SAMST: dumper[61]: %OS-DUMPER-4-SIGSEGV_INFO : Accessed BadAddr 0x0 at PC 0xffffffff. Signal code 0 - Unknown SIGSEGV code. 0
RP/0/RSP1/CPU0:2019 Apr 5 02:04:27.827 SAMST: dumper[61]: %OS-DUMPER-4-SIGNALCORE_INFO : Core for pid = 1003820 (pkg/bin/bgp) as signal 11 sent by pkg/bin/bgp@node0_RSP1_CPU0
RP/0/RSP1/CPU0:2019 Apr 5 02:04:27.829 SAMST: dumper[61]: %OS-DUMPER-7-PROC_PAGES : Process memory pages 1027
RP/0/RSP1/CPU0:2019 Apr 5 02:04:27.830 SAMST: dumper[61]: %OS-DUMPER-6-FALLBACK_CHOICE : Fall back choice: 0(harddisk:/dumper) in use
RP/0/RSP1/CPU0:2019 Apr 5 02:04:27.831 SAMST: dumper[61]: %OS-DUMPER-6-REGISTERS_INFO : EDI ESI EBP(fp) EXX
RP/0/RSP1/CPU0:2019 Apr 5 02:04:27.831 SAMST: dumper[61]: %OS-DUMPER-6-REGISTERS_INFO : R0 00000000 13027a14 03b6ae18 fc57a998
RP/0/RSP1/CPU0:2019 Apr 5 02:04:27.831 SAMST: dumper[61]: %OS-DUMPER-6-REGISTERS_INFO : EBX EDX ECX EAX
RP/0/RSP1/CPU0:2019 Apr 5 02:04:27.831 SAMST: dumper[61]: %OS-DUMPER-6-REGISTERS_INFO : R4 0005000d 0004fff1 0adabe3c 0004fff1
RP/0/RSP1/CPU0:2019 Apr 5 02:04:27.831 SAMST: dumper[61]: %OS-DUMPER-6-REGISTERS_INFO : EIP(pc) CS EFL ESP
RP/0/RSP1/CPU0:2019 Apr 5 02:04:27.831 SAMST: dumper[61]: %OS-DUMPER-6-REGISTERS_INFO : R8 0adabe40 000000f3 00011202 03b6ae04
RP/0/RSP1/CPU0:2019 Apr 5 02:04:27.831 SAMST: dumper[61]: %OS-DUMPER-6-REGISTERS_INFO : SS
RP/0/RSP1/CPU0:2019 Apr 5 02:04:27.831 SAMST: dumper[61]: %OS-DUMPER-6-REGISTERS_INFO : R12 000000fb
RP/0/RSP1/CPU0:2019 Apr 5 02:04:27.831 SAMST: dumper[61]: %OS-DUMPER-6-TRACE_BACK : #0 0xadabe40
RP/0/RSP1/CPU0:2019 Apr 5 02:04:27.840 SAMST: dumper[61]: %OS-DUMPER-6-TRACE_BACK : #1 0x10818625
RP/0/RSP1/CPU0:2019 Apr 5 02:04:27.840 SAMST: dumper[61]: %OS-DUMPER-6-TRACE_BACK : #2 0x10818955
RP/0/RSP1/CPU0:2019 Apr 5 02:04:27.840 SAMST: dumper[61]: %OS-DUMPER-6-TRACE_BACK : #3 0x108218df
RP/0/RSP1/CPU0:2019 Apr 5 02:04:27.840 SAMST: dumper[61]: %OS-DUMPER-6-TRACE_BACK : #4 0x10935c8f
RP/0/RSP1/CPU0:2019 Apr 5 02:04:27.840 SAMST: dumper[61]: %OS-DUMPER-6-TRACE_BACK : #5 0x10939713
RP/0/RSP1/CPU0:2019 Apr 5 02:04:27.840 SAMST: dumper[61]: %OS-DUMPER-6-TRACE_BACK : #6 0xad23cbf
RP/0/RSP1/CPU0:2019 Apr 5 02:04:27.840 SAMST: dumper[61]: %OS-DUMPER-6-TRACE_BACK : #7 0xad21ce8
RP/0/RSP1/CPU0:2019 Apr 5 02:04:27.840 SAMST: dumper[61]: %OS-DUMPER-6-TRACE_BACK : #8 0x105dd55c
RP/0/RSP1/CPU0:2019 Apr 5 02:04:27.840 SAMST: dumper[61]: %OS-DUMPER-6-TRACE_BACK : #9 0x1093a8b3
And the Recieved Prefixes counter is growing up VERY slowly. Like 750k prefixes are filling up about 3 hours when peer is in neighbor-group and like 45 minutes when the peer is just a neighbour (not in neighbor-group). All timeouts are in default state and no errors are visible on the link to the peer.
Eny ideas what can be wrong?
