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 Information on the LPU Is Inconsistent With that on the MPU

Publication Date:  2012-07-27 Views:  41 Downloads:  0
Issue Description
 Q:
Why is information on the LPU inconsistent with that on the MPU? 

 
Alarm Information
 Null 

 
Handling Process
 A:
BFD sessions are processed on the LPU. Information of different types is synchronized to the MPU at different intervals.
For example:
Session status: synchronized at the interval of 100 ms
Session information: synchronized at the interval of 5 minutes
Session statistics: synchronized at the interval of 5 to 10 minutes according to the type of the device….
Therefore, session status displayed on the MPU is almost synchronous with that on the LPU; other information is displayed on the MPU with delay. For example,
Actual Tx Interval (ms) and Actual Rx Interval (ms) indicate the actual intervals for sending and receiving packets respectively in a session. If you view information about the MPU and LPU as soon as a session goes Up, these two fields are usually of different values. This is because the intervals for sending and receiving packets on the MPU remain those in the negotiation stage, whereas the intervals for sending and receiving packets on the LPU have been updated.
You can do as follows to view the statistics on the LPU:
Specify slot-number in the display bfd discriminator XX verbose command (the slot number specifies the LPU where the session is processed), run the command, and then view the value of the field FSM Board Id. 

 
Root Cause
 Null 

 
Suggestions
 Null 

 

END