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>Search


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


BGP Peer Relationship Flaps After BFD Is Configured on the NE5000E

Publication Date:  2013-09-03 Views:  72 Downloads:  0
Issue Description
BFD for BGP is configured between the NE5000E and ME60. After the link between them is expanded, the BGP status is unstable, affecting the BGP peer relationship.
Handling Process
1. Check the link quality.
2. Check the configuration of BFD for BGP.
3. Check the BFD specifications.
Root Cause
1. The link quality is low.
2. The configuration of BFD for BGP is incorrect.
3. The NE5000E does not support BFD specifications.
1. Check whether CRC error packets exist on connected interfaces. No error packet exists, indicating the normal link.
2. Check the configuration. The configuration is correct.
     bgp 100
           peer as-number 100
           peer bfd enable

3. Currently, BFD links cannot be bound on different boards. If BFD links are bound on different boards, BFD sessions become Up and Down at a probability. Delete the bfd enable configuration for BGP. To use inter-board BFD, add an SPUC and use the centralized BFD.

<NE5000E>display bfd session all
9786  8924  Up        D_IP_PEER         -  
<NE5000E>disp ip routing-table  ISIS   115  3000         D   GigabitEthernet1/7/0/3
                                           ISIS   115  3000         D   GigabitEthernet1/4/1/2
                                             ISIS   115  3000         D  GigabitEthernet1/4/1/3

The command output shows that the BGP neighbor route is learned from slots 4 and 7. This scenario is not supported by the NE40E&NE80E&NE5000E.
On the NE40E&NE80E&NE5000E, BFD for BGP is not supported on the inter-board link.