Symptom
FIB objects stuck in retry queue for long
The following logs are seen:
%ROUTING-FIB-4-RETRYDB_NONEMPTY : One or more FIB object(s) have been in IPv4 retry queue for at least 3840 seconds
%ROUTING-FIB-4-RETRYDB_NONEMPTY : One or more FIB object(s) have been in IPv6 retry queue for at least 3840 seconds
Conditions
- The reason for the issue should be IDB extension creation failure for loopbacks
- This could happen on standby-RP
Workaround
The trace will become infrequent with passage of time, only showing up once a day.
The trace is harmless, and so is the object in the retry db.
The syslog could disappear if any routes path via the loopback.
Further Problem Description
show cef retry-db location
Has entries such as these (type Route_upd)
show trace shows that there is a local cef entry that is in retry
