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.


The C Device and the Router Are Connected Through the BGP that Adopts the MD5 Authentication. After the C Device Is Replaced, the Authentication Fails

Publication Date:  2012-07-27 Views:  59 Downloads:  0
Issue Description
The External Border Gateway Protocol (EBGP) peer relationship between the C device and the NE80 is set up through the loopback interface. The EBGP peer relationship adopts MD5 authentication. During the project alteration, the C device needs to be replaced by the NE80E. During the replacement, the command lines of the BGP MD5 authentication method are replicated. As a result, the EBGP peer relationship cannot be set up between the NE80E and the NE80 after the replacement.
Alarm Information
#Sep 13 01:58:57 2007 GX-GL-ZNJ-A-1.163 SOCKET/5/TRAP:                                                                              
          MD5 authentication failure                                            
          TCP connection-Source Source port:49571        
          Foreign port:179                        
          Protocol:BGP,VRF Name:
Handling Process
Modify the MD5 authentication password of the NE80E to be consistent with that of the peer NE80.
Root Cause
The password authentication algorithm of the C device is not the same as that of the router, which causes that original MD5 authentication password of the C device cannot be analyzed correctly by the NE80E and that the negotiation fails.
For different vendors, the authentication algorithms are different, which needs to be noted during the replacement. Therefore, re-configurations on both ends are needed for consistence.