Tuesday, November 10, 2020

IOS-XR Log message: %ROUTING-FIB-4-RETRYDB_NONEMPTY

 XR7/ LNT along with several other platforms are seeing the below errors: 

 

 

 

RP/0/RP0/CPU0:darwin1#show log | in RETRY
Fri Aug 28 02:35:15.217 UTC
RP/0/RP0/CPU0:Aug 24 07:06:43.951 UTC: fib_mgr[355]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : One or more FIB object(s) have been in IPv4 retry queue for at least 120 seconds
RP/0/RP0/CPU0:Aug 24 07:10:43.951 UTC: fib_mgr[355]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : One or more FIB object(s) have been in IPv4 retry queue for at least 240 seconds
RP/0/RP0/CPU0:Aug 24 07:18:43.951 UTC: fib_mgr[355]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : One or more FIB object(s) have been in IPv4 retry queue for at least 480 seconds
RP/0/RP0/CPU0:Aug 24 07:34:43.951 UTC: fib_mgr[355]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : One or more FIB object(s) have been in IPv4 retry queue for at least 960 seconds
RP/0/RP0/CPU0:Aug 24 08:06:43.951 UTC: fib_mgr[355]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : One or more FIB object(s) have been in IPv4 retry queue for at least 1920 seconds
RP/0/RP0/CPU0:Aug 24 09:10:43.951 UTC: fib_mgr[355]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : One or more FIB object(s) have been in IPv4 retry queue for at least 3840 seconds
RP/0/RP0/CPU0:Aug 24 11:18:43.951 UTC: fib_mgr[355]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : One or more FIB object(s) have been in IPv4 retry queue for at least 7680 seconds
RP/0/RP0/CPU0:Aug 24 15:34:43.952 UTC: fib_mgr[355]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : One or more FIB object(s) have been in IPv4 retry queue for at least 15360 seconds
RP/0/RP0/CPU0:Aug 25 00:06:43.952 UTC: fib_mgr[355]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : One or more FIB object(s) have been in IPv4 retry queue for at least 30720 seconds
RP/0/RP0/CPU0:Aug 25 17:10:43.952 UTC: fib_mgr[355]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : One or more FIB object(s) have been in IPv4 retry queue for at least 61440 seconds
RP/0/RP0/CPU0:Aug 26 17:10:43.952 UTC: fib_mgr[355]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : One or more FIB object(s) have been in IPv4 retry queue for at least 86400 seconds
RP/0/RP0/CPU0:Aug 27 17:10:43.952 UTC: fib_mgr[355]: %ROUTING-FIB-4-RETRYDB_NONEMPTY : One or more FIB object(s) have been in IPv4 retry queue for at least 86400 seconds
RP/0/RP0/CPU0:darwin1#

 

 

 

This is identical to: 

https://techzone.cisco.com/t5/IOS-XR-L3FIB-Eng-Discussion/NTT-7-0-2-ROUTING-FIB-4-RETRYDB-NONEMPTY-S...

 

From our lab node:

 

 

 

 

RP/0/RP0/CPU0:darwin1#show cef unresolved location 0/rp0/CPU0

Fri Aug 28 02:35:33.827 UTC



IPV4:

-----



Prefix              Next Hop            Interface

------------------- ------------------- ------------------

10.0.101.1/32       10.0.101.1/32 (?)   MgmtEth0/RP0/CPU0/0

10.0.101.3/32       10.0.101.3/32 (?)   MgmtEth0/RP0/CPU0/0

10.0.101.7/32       10.0.101.7/32 (?)   MgmtEth0/RP0/CPU0/0

10.0.101.8/32       10.0.101.8/32 (?)   MgmtEth0/RP0/CPU0/0

10.0.101.15/32      10.0.101.15/32 (?)  MgmtEth0/RP0/CPU0/0

10.0.101.22/32      10.0.101.22/32 (?)  MgmtEth0/RP0/CPU0/0

10.0.101.29/32      10.0.101.29/32 (?)  MgmtEth0/RP0/CPU0/0

10.0.101.102/32     10.0.101.102/32 (?) MgmtEth0/RP0/CPU0/0



<snip>

 

 

 

These are the ones that are not resolved at this time.

 

These entries were learned via arp. They are out of the subnet range configured on the MgMtETH0 interface

 

CEF as a check, requires we have a route for this entry in rib before installing this.

That is why we are seeing them in the retry db.

 

 

RP/0/RP0/CPU0:darwin1#show arp mgmtEth 0/RP0/CPU0/0

Fri Aug 28 02:35:45.052 UTC



-------------------------------------------------------------------------------

0/RP0/CPU0

-------------------------------------------------------------------------------

Address         Age        Hardware Addr   State      Type  Interface

10.0.101.1      00:10:12   00de.fb6e.7281  Dynamic    ARPA  MgmtEth0/RP0/CPU0/0

10.0.101.3      00:00:44   000c.299f.2ea0  Dynamic    ARPA  MgmtEth0/RP0/CPU0/0

10.0.101.7      03:21:44   0050.56b6.ea6e  Dynamic    ARPA  MgmtEth0/RP0/CPU0/0

10.0.101.8      00:00:49   000c.29dd.58eb  Dynamic    ARPA  MgmtEth0/RP0/CPU0/0

10.0.101.15     00:39:50   000c.291f.34b9  Dynamic    ARPA  MgmtEth0/RP0/CPU0/0

10.0.101.22     02:20:15   0050.56a2.36f9  Dynamic    ARPA  MgmtEth0/RP0/CPU0/0

10.0.101.29     02:59:25   0050.56a2.2503  Dynamic    ARPA  MgmtEth0/RP0/CPU0/0

10.0.101.102    00:08:56   00de.fbf0.bddd  Dynamic    ARPA  MgmtEth0/RP0/CPU0/0

10.0.101.151    00:06:40   0025.b500.000b  Dynamic    ARPA  MgmtEth0/RP0/CPU0/0



<snip>

 

 

 

To address this issue, please configure the below: 

 

 

 

RP/0/RP0/CPU0:darwin1#conf t

Fri Aug 28 02:35:51.928 UTC

RP/0/RP0/CPU0:darwin1(config)#int mgmtEth 0/RP0/CPU0/0

RP/0/RP0/CPU0:darwin1(config-if)#arp learning local

RP/0/RP0/CPU0:darwin1(config-if)#commit

Fri Aug 28 02:36:01.404 UTC

RP/0/RP0/CPU0:darwin1(config-if)#

RP/0/RP0/CPU0:darwin1(config-if)#

RP/0/RP0/CPU0:darwin1#

RP/0/RP0/CPU0:darwin1#

RP/0/RP0/CPU0:darwin1#

RP/0/RP0/CPU0:darwin1#show run int mgmtEth 0/RP0/CPU0/0

Fri Aug 28 02:43:03.993 UTC

interface MgmtEth0/RP0/CPU0/0

 ipv4 address 10.197.241.118 255.255.254.0

 arp learning local

!



RP/0/RP0/CPU0:darwin1#

No comments:

Post a Comment