No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FAQ-Why NE20 Refreshes FIB and Occurs Timeout Alarm

Publication Date:  2012-07-27 Views:  42 Downloads:  0
Issue Description
Q:
Why NE20 refreshes FIB and occurs timeout alarm? It is applied to VRP3.30 version.
Alarm Information
%Feb  8 09:30:51 2006 NE20_A FIB/5/log_fib:FIB timer 770 timeout!         
%Feb  8 09:30:51 2006 NE20_A FIB/5/log_fib:                               
FIB synchro state:  2006/02/08 09:30:51 Refresh time out                        
%Feb  8 09:30:51 2006 NE20_A FIB/5/log_fib:FIB is not refreshing routing! 
%Feb  8 09:30:51 2006 NE20_A FIB/5/log_fib:FIB create WalkForRefreshing ti
mer 492                                                                         
%Feb  8 09:30:51 2006 NE20_A FIB/5/log_fib:FIB create refreshing timer 601
%Feb  8 09:30:57 2006 NE20_A FIB/5/log_fib:FIB timer 492 timeout!         
%Feb  8 09:30:57 2006 NE20_A FIB/5/log_fib:                               
FIB synchro state:  2006/02/08 09:30:57 Begin to fresh walking                  
%Feb  8 09:30:57 2006 NE20_A FIB/5/log_fib:                               
FIB synchro state:  2006/02/08 09:30:57 in course of fresh walking              
%Feb  8 09:31:02 2006 NE20_A FIB/5/log_fib:FIB timer 487 timeout!         
%Feb  8 09:31:02 2006 NE20_A FIB/5/log_fib:                               
FIB synchro state:  2006/02/08 09:31:02 Begin to fresh walking                  
%Feb  8 09:31:02 2006 NE20_A FIB/5/log_fib:                               
FIB synchro state:  2006/02/08 09:31:02 Boards have been refreshed              
%Feb  8 09:31:02 2006 NE20_A FIB/5/log_fib:                               
FIB synchro state:  2006/02/08 09:31:02 End fresh walking
Handling Process
A:
Timeout alarm during FIB refresh process is caused by the difference between FIB refresh process of VRP and hardware of NE20.
Root Cause
From alarm information, it experiences the following process:
1. Timer expires. 
2. Refresh FIB timeout.
3. FIB is not refreshed.
4. Create refresh and start timer.
5. Timer expires again.
6. Refresh process starts.
7. It displays the timer expires.
8. Refresh finishes and end the process.
Reasons:
1. NE20 refresh is handled by CPU and NP. CPU floods NP refresh task and NP is responsible for refresh. And then synchronizes refresh result. 
2. According to the university of VRP software, VRP software starts new timer process when refresh. FIB refresh is not handled by CPU, so no system responds this process and timer timeout during the process. 
3. NP refreshes FIB and CPU synchronizes the data. FIB refresh ends.
Suggestions
The alarm does not influence the alarm. Whether FIB refresh succeeds or not, check there is "Boards have been refreshed" and "End fresh walking" field in the log. Refresh succeeds and it proves that the device can be operated normally.

END