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

After a BGP Peer Relationship is Established, the State of the BGP Neighbor Immediately Changes from Establish to Idle

Publication Date:  2012-07-27 Views:  53 Downloads:  0
Issue Description
The NE80E establishes an EBGP peer relationship with the router of an ISP. After the BGP peer relationship is established, the status of the peer immediately changes from Establish to Idle. Enable debugging BGP. The following information is displayed:
Mar 19 2008 17:02:02 CA2_NE80E_B %%01BGP/3/STATE_CHG_UPDOWN(l): Peer 84.16.10.18
5 state was changed from OPENCONFIRM to ESTABLISHED. (BGP address family=public)
Mar 19 2008 17:02:02 CA2_NE80E_B %%01BGP/3/NOTIFY_MSG_ERR(l): NOTIFICATION message from peer 84.16.10.185 was identified error. (error code=6, sub error code=1,BGP address family=public)
Mar 19 2008 17:02:03 CA2_NE80E_B %%01BGP/3/STATE_CHG_UPDOWN(l): Peer 84.16.10.18
5 state was changed from ESTABLISHED to IDLE. (BGP address family=public)
-----------------------------------
Mar 19 2008 17:08:58 CA2_NE80E_B %%01BGP/3/STATE_CHG_UPDOWN(l): Peer 193.251.252
.73 state was changed from OPENCONFIRM to ESTABLISHED. (BGP address family=public)
Mar 19 2008 17:08:59 CA2_NE80E_B %%01BGP/3/STATE_CHG_UPDOWN(l): Peer 193.251.252
.73 state was changed from ESTABLISHED to IDLE. (BGP address family=public)
From the above information, we can see that the BGP neighbor state changes from establish to idle after the NE80E receives a NOTIFICATION message from the peer device. 

 
Alarm Information
 Null
Handling Process
Reduce the number of routing entries to be advertised to the peer ISP device by modifying the routing policy on the NE80E. After that, the EBGP peer relationship between the NE80E and the peer ISP device is normal. Ask the peer ISP to increase the capacity of the router interconnected to the NE80E.  
Root Cause
 View the debugging information and focus on the codes of the NOTIFICATION message. The NOTIFICATION message contains such information (error code=6, sub error code=1, BGP address family=public). In RFC 4486, sub error code=1 indicates the maximum number of prefixes is reached. When the number of routes on the peer device reaches the maximum value, the peer device will interrupt the EBGP neighbor connection. 
Suggestions
Null 

END