This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject
Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Warn:IPRT> Route IPFDB Handle

Warn:IPRT> Route IPFDB Handle

Jimmy2
New Contributor

‎04-28-2014 04:09 AM

What are the source of these issues in the logs? I am seeing this on 7i's very intermittently. I have tried search extreme site but unable to get any results/.

04/17/2014 12:24:16.00 Route IPFDB Handle 0x1886c != Passed Curr Handle 0x2c46c04/17/2014 12:24:16.00 Route IPFDB Handle 0x1886c != Passed Curr Handle 0x2746c
04/17/2014 12:24:16.00 Route IPFDB Handle 0x2686c != Passed Curr Handle 0x2046c
04/17/2014 12:24:16.00 Route IPFDB Handle 0x2686c != Passed Curr Handle 0x1e86c
04/17/2014 12:24:16.00 Route IPFDB Handle 0x2686c != Passed Curr Handle 0x4c6c
04/17/2014 12:24:16.00 Port 13 link down
04/17/2014 12:21:03.31 Route IPFDB Handle 0x1445c != Passed Curr Handle 0x1585c
04/17/2014 12:21:02.93 Route IPFDB Handle 0x1745c != Passed Curr Handle 0x1445c
04/17/2014 12:21:02.11 Route IPFDB Handle 0x1785c != Passed Curr Handle 0x1705c
0 Kudos
5 REPLIES 5

Sumit_Tokle
Contributor

‎04-28-2014 01:50 PM



04/17/2014 12:21:02.11 Route IPFDB Handle 0x1785c != Passed Curr Handle 0x1705c

Description of the above warning message:

The IPFDB was looking for an entry to flush. When IPFBDFlush went to find the entry, it had already aged out and this is why we see the error:
"IPRT: Route IPFDB Handle 0x1785c != Passed Curr Handle 0x1705c

This message means that the IPFDB entry 0x1705c will be deleted from the system, but the associated IPRoute table entry is pointing to FDB entry 0x1785c. The system ignores this inconsistency and keeps the IPRoute table as it is.

This message appears when the FDB is full. Full can be either the specified limit as specified in the Release Notes or the outcome of the FDB hashing (four entries in the FDB + four entries in the Alternate Bucket).

Below are the possible Solution:
===================================
1)To avoid this warning message, reduce the FDB entries by limiting the FDB aging timer and/or the IPFDB aging timer.

2)Reboot the switch
The reason to reboot the switch is that some time the entries in HW and SW tables did not sync up due to any reason, so when the switch reboot it will sync up both SW and HW entries.
0 Kudos
GTM-P2G8KFN