*Nov 18 12:38:28.527: %BGP-3-NOTIFICATION: received from neighbor 220.127.116.11 passive 2/7 (unsupported/disjoint capability) 6 bytes 41040000 FC00 *Nov 18 12:38:31.991: BGP: nbr_topo global 18.104.22.168 IPv4 Unicast:base (0x2726E074:0) Not scheduling for GR processing [Peer did not advertise GR cap] *Nov 18 12:38:31.991: BGP: ses global 22.214.171.124 (0x2726E074:0) act Reset (Peer closed the session).
Which tells that peer is not having capability for graceful-restart. You can disable this feature with global bgp command "no bgp graceful-restart"
But make sure you do not have any other peer need this feature.
You can give one hidden command "dont-capability-negotiate" per neighbor i.e neighbor 126.96.36.199 dont-capability-negotiate
This error message basically indicates that the two BGP neighbors didn't agree on some of the capabilities configured under the BGP configuration. This is as per RFC 2842 for Capabilities Advertisement with BGP-4. I am pasting the paragraph below, that explains this:
"If a BGP speaker that supports a certain capability determines that its peer doesn't support this capability, the speaker may send a NOTIFICATION message to the peer, and terminate peering. The Error Subcode in the message is set to Unsupported Capability. The message should contain the capability (capabilities) that causes the speaker to send the message. The decision to send the message and terminate peering is local to the speaker. Such peering should not be re- established automatically."
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...