Error : RETRYDB_NONEMPTY; Message Text: One or more FIB object(s) have been in IPv4 retry queue for at least 86400 seconds

[Muradazz]

Hi,

recently i saw this MSG. on the log file  but i cant understand what is the cause route of it 

LC/0/0/CPU0:Feb 26 21:46:30.694 UTC: fib_mgr[184]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : One or more FIB object(s) have been in IPv4 retry queue for at least 86400 seconds
RP/0/RSP1/CPU0:Feb 27 21:19:27.740 UTC: fib_mgr[230]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : One or more FIB object(s) have been in IPv4 retry queue for at least 86400 seconds
LC/0/1/CPU0:Feb 27 21:45:50.251 UTC: fib_mgr[184]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : One or more FIB object(s) have been in IPv4 retry queue for at least 86400 seconds
LC/0/0/CPU0:Feb 27 21:46:31.038 UTC: fib_mgr[184]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : One or more FIB object(s) have been in IPv4 retry queue for at least 86400 seconds

I did search on google   and someone says that this alert appears after reload the LC cards  but  all the cards stable and did not has any reload on it since we install and run the box 

[marce1000]

 - Which router-hardware platform is this ? You will find a number of related bug reports below :

         https://bst.cloudapps.cisco.com/bugsearch/search?kw=ROUTING-FIB-4-RETRYDB_NONEMPTY&pf=prdNm&sb=anfr

 It is always advisable to use an advisory software release for the router , if feasible and applicable.

 M.

[Muradazz]

thank you for your support 

this platform is ASR9006 

Cisco IOS XR Software, Version 6.7.1[Default]
Copyright (c) 2020 by Cisco Systems, Inc.

ROM: System Bootstrap, Version 0.76(c) 1994-2012 by Cisco Systems, Inc.

HB-AHL00-CSASR9-PE01 uptime is 14 weeks, 5 days, 23 hours, 18 minutes
System image file is "disk0:asr9k-os-mbi-6.7.1/0x100305/mbiasr9k-rsp3.vm"

cisco ASR9K Series (Intel 686 F6M14S4) processor with 12582912K bytes of memory.
Intel 686 F6M14S4 processor at 2136MHz, Revision 2.174
ASR 9006 4 Line Card Slot Chassis with V2 DC PEM

1 FastEthernet
4 Management Ethernet
20 GigabitEthernet
2 TenGigE
2 DWDM controller(s)
2 WANPHY controller(s)
503k bytes of non-volatile configuration memory.
6220M bytes of hard disk.
12510192k bytes of disk0: (Sector size 512 bytes).
12510192k bytes of disk1: (Sector size 512 bytes).

[marce1000 · Accepted solution]

 - Tryout this release : https://software.cisco.com/download/home/282423206/type/280805694/release/7.1.3

                    and check if the problem remains in place or not.

 M.

[Georg Pauwen · Accepted solution]

Hello,

if this is just an informational message, use the logging discriminator below to make that log entry not show up anymore:

logging discriminator FIB_RETRY severity drops 4 facility drops ROUTING mnemonics drops RETRYDB_NONEMPTY
logging buffered discriminator FIB_RETRY 100000
logging console discriminator FIB_RETRY
logging monitor discriminator FIB_RETRY
logging host x.x.x.x discriminator FIB_RETRY

[swikel1006]

I have this same problem however it is surrounding ipv6 on the NCS55A1 platform.

[EnriqueRiojaLlanos7753]

In my case is similar, the messages repeated several times around the day:

LC/0/0/CPU0:May 14 16:23:27.749 -04: fib_mgr[157]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : 1 FIB object(s) have been in IPv6 retry queue for at least 120 seconds
RP/0/RP0/CPU0:May 14 16:23:27.750 -04: fib_mgr[454]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : 1 FIB object(s) have been in IPv6 retry queue for at least 120 seconds
LC/0/0/CPU0:May 14 16:27:27.749 -04: fib_mgr[157]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : 1 FIB object(s) have been in IPv6 retry queue for at least 240 seconds
RP/0/RP0/CPU0:May 14 16:27:27.750 -04: fib_mgr[454]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : 1 FIB object(s) have been in IPv6 retry queue for at least 240 seconds
LC/0/0/CPU0:May 14 16:28:53.651 -04: fib_mgr[157]: %ROUTING-FIB-6-RETRYDB_OK : All objects in FIB IPv6 retry queue are resolved now.
RP/0/RP0/CPU0:May 14 16:28:53.657 -04: fib_mgr[454]: %ROUTING-FIB-6-RETRYDB_OK : All objects in FIB IPv6 retry queue are resolved now.
LC/0/0/CPU0:May 14 16:34:09.674 -04: fib_mgr[157]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : 1 FIB object(s) have been in IPv6 retry queue for at least 120 seconds
RP/0/RP0/CPU0:May 14 16:34:09.674 -04: fib_mgr[454]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : 1 FIB object(s) have been in IPv6 retry queue for at least 120 seconds
LC/0/0/CPU0:May 14 16:38:09.674 -04: fib_mgr[157]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : 1 FIB object(s) have been in IPv6 retry queue for at least 240 seconds
RP/0/RP0/CPU0:May 14 16:38:09.674 -04: fib_mgr[454]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : 1 FIB object(s) have been in IPv6 retry queue for at least 240 seconds
LC/0/0/CPU0:May 14 16:39:57.398 -04: fib_mgr[157]: %ROUTING-FIB-6-RETRYDB_OK : All objects in FIB IPv6 retry queue are resolved now.
RP/0/RP0/CPU0:May 14 16:39:57.404 -04: fib_mgr[454]: %ROUTING-FIB-6-RETRYDB_OK : All objects in FIB IPv6 retry queue are resolved now.
LC/0/0/CPU0:May 14 16:46:32.255 -04: fib_mgr[157]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : 1 FIB object(s) have been in IPv6 retry queue for at least 120 seconds
RP/0/RP0/CPU0:May 14 16:46:32.255 -04: fib_mgr[454]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : 1 FIB object(s) have been in IPv6 retry queue for at least 120 seconds
LC/0/0/CPU0:May 14 16:50:32.255 -04: fib_mgr[157]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : 1 FIB object(s) have been in IPv6 retry queue for at least 240 seconds
RP/0/RP0/CPU0:May 14 16:50:32.255 -04: fib_mgr[454]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : 1 FIB object(s) have been in IPv6 retry queue for at least 240 seconds
LC/0/0/CPU0:May 14 16:52:00.496 -04: fib_mgr[157]: %ROUTING-FIB-6-RETRYDB_OK : All objects in FIB IPv6 retry queue are resolved now.
RP/0/RP0/CPU0:May 14 16:52:00.502 -04: fib_mgr[454]: %ROUTING-FIB-6-RETRYDB_OK : All objects in FIB IPv6 retry queue are resolved now.
RP/0/RP0/CPU0:May 14 16:58:18.717 -04: fib_mgr[454]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : 1 FIB object(s) have been in IPv6 retry queue for at least 120 seconds
LC/0/0/CPU0:May 14 16:58:18.717 -04: fib_mgr[157]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : 1 FIB object(s) have been in IPv6 retry queue for at least 120 second
RP/0/RP0/CPU0:May 14 17:02:18.717 -04: fib_mgr[454]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : 1 FIB object(s) have been in IPv6 retry queue for at least 240 seconds
LC/0/0/CPU0:May 14 17:02:18.718 -04: fib_mgr[157]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : 1 FIB object(s) have been in IPv6 retry queue for at least 240 seconds
LC/0/0/CPU0:May 14 17:04:01.497 -04: fib_mgr[157]: %ROUTING-FIB-6-RETRYDB_OK : All objects in FIB IPv6 retry queue are resolved now.
RP/0/RP0/CPU0:May 14 17:04:01.504 -04: fib_mgr[454]: %ROUTING-FIB-6-RETRYDB_OK : All objects in FIB IPv6 retry queue are resolved now.
LC/0/0/CPU0:May 14 17:22:31.696 -04: fib_mgr[157]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : 1 FIB object(s) have been in IPv6 retry queue for at least 120 seconds
RP/0/RP0/CPU0:May 14 17:22:31.696 -04: fib_mgr[454]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : 1 FIB object(s) have been in IPv6 retry queue for at least 120 seconds

[perevillar]

Hello,

For what it's worth, In my case I had a similar message this morning ...

LC/0/0/CPU0:Aug 29 07:02:24.971 CEST: fib_mgr[177]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : 2 FIB object(s) have been in IPv4 retry queue for at least 15360 seconds
RP/0/RP0/CPU0:Aug 29 15:34:24.968 CEST: fib_mgr[137]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : 1 FIB object(s) have been in IPv4 retry queue for at least 30720 seconds
LC/0/0/CPU0:Aug 29 15:34:24.973 CEST: fib_mgr[177]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : 1 FIB object(s) have been in IPv4 retry queue for at least 30720 seconds

... and it turns out that I had changed the loopback address of a router but not the corresponding connected-prefix-sid-map:

segment-routing mpls
global-block 16000 23999
!
connected-prefix-sid-map
address-family ipv4
198.18.255.7/32 absolute 16007 range 1
exit-address-family
!
segment-routing mpls

as soon as I fixed it the problem disappeared:

RP/0/RP0/CPU0:Aug 29 22:29:57.832 CEST: fib_mgr[137]: %ROUTING-FIB-6-RETRYDB_OK : All objects in FIB IPv4 retry queue are resolved now.
LC/0/0/CPU0:Aug 29 22:29:57.842 CEST: fib_mgr[177]: %ROUTING-FIB-6-RETRYDB_OK : All objects in FIB IPv4 retry queue are resolved now.

---

---