Hello Dhineshkumar,
from the log file we see
*Sep 12 09:50:03.710: %BGP_SESSION-5-ADJCHANGE: neighbor 192.168.13.2 IPv4 Unicast topology base removed from session Peer closed the session
--More--
*Sep 12 09:50:05.838: %BGP-3-NOTIFICATION: received from neighbor 192.168.13.2 passive 2/7 (unsupported/disjoint capability) 6 bytes 41040000 FDED
--More--
*Sep 12 09:50:05.838: %BGP_SESSION-5-ADJCHANGE: neighbor 192.168.13.2 IPv4 Unicast topology base removed from session BGP Notification received
--More--
*Sep 12 09:50:10.854: %BGP-3-NOTIFICATION: received from neighbor 192.168.13.2 passive 2/7 (unsu
the error code associated to the BGP notification is 2/7
from
http://www.tcpipguide.com/free/t_BGPErrorReportingNotificationMessages-3.htm
we see that error code 2 refers to the BGP Open message sent by C1900 to the iBGP neighbor 192.168.13.2
2 | Open Message Error | A problem was found in the body of an Open message. The Error Subtype field describes the problem in more detail. Note that authentication failures or inability to agree on a parameter such as hold time are included here. |
error subcode 7 means unsupported capability
http://itlearninz.com/bgp-notification-error-codes/
the neighbor 192.168.13.2 is an iBGP neighbor can you check its configuration and IOS version?
It would be nice to see the log messages from the iBGP neighbor too and to see the contents of the offending BGP Open Message packet.
the C1900 has the following image:
System image file is "flash0:c1900-universalk9-mz.SPA.151-3.T.bin"
the iBGP peer 192.168.13.2 complains of an unsupported feature that is proposed by the local node C1900 and closes the iBGP session. The issue happens during BGP session setup and happens everytime the session is started every few seconds.
note:
Are you a friend of the original poster of the following thread?
https://supportforums.cisco.com/thread/2170829?tstart=0
the log file is the same!!!
Hope to help
Giuseppe
