BGP Down with AFI/SAFI not supported

[agus.siswanto]

Hi Everyone.
I have Cisco Router 3945 that has been configure with 2 neighbor BGP. and sometimes BGP is flapping only few second and its say error no supported AFI/SAFI.

Could you let me what could be a reason for it?

Apr 2 19:14:55.147 GMT: %BGP-3-NOTIFICATION: sent to neighbor 172.16.254.29 4/0 (hold time expired) 0 bytes
Apr 2 19:14:55.147 GMT: %BGP-5-NBR_RESET: Neighbor 172.16.254.29 reset (BGP Notification sent)
Apr 2 19:14:55.147 GMT: %BGP-5-ADJCHANGE: neighbor 172.16.254.29 Down BGP Notification sent
Apr 2 19:14:55.147 GMT: %BGP_SESSION-5-ADJCHANGE: neighbor 172.16.254.29 IPv4 Unicast topology base removed from session BGP Notification sent
Apr 2 19:15:08.717 GMT: %BGP-5-NBR_RESET: Neighbor 172.16.254.29 passive reset (Peer closed the session)
Apr 2 19:15:08.717 GMT: %BGP-5-ADJCHANGE: neighbor 172.16.254.29 passive Down AFI/SAFI not supported
Apr 2 19:15:08.749 GMT: %BGP-5-ADJCHANGE: neighbor 172.16.254.29 Up

Apr 12 14:57:14.419 GMT: %BGP-3-NOTIFICATION: sent to neighbor 172.16.254.33 4/0 (hold time expired) 0 bytes
Apr 12 14:57:14.419 GMT: %BGP-5-NBR_RESET: Neighbor 172.16.254.33 reset (BGP Notification sent)
Apr 12 14:57:14.419 GMT: %BGP-5-ADJCHANGE: neighbor 172.16.254.33 Down BGP Notification sent
Apr 12 14:57:14.419 GMT: %BGP_SESSION-5-ADJCHANGE: neighbor 172.16.254.33 IPv4 Unicast topology base removed from session BGP Notification sent
Apr 12 14:57:41.956 GMT: %BGP-5-NBR_RESET: Neighbor 172.16.254.33 passive reset (Peer closed the session)
Apr 12 14:57:41.958 GMT: %BGP-5-ADJCHANGE: neighbor 172.16.254.33 passive Down AFI/SAFI not supported
Apr 12 14:57:42.158 GMT: %BGP-5-ADJCHANGE: neighbor 172.16.254.33 Up


Both .29 and .33 are IBGP neighbor
thanks

[Flavio Miranda]

Does this neighbors has IPV6 enable?

Can you run "debug bgp all" ?

[agus.siswanto]

im using ipv4 bgp

here's the config

[Flavio Miranda]

Yeah, but what about the other side? 

[agus.siswanto]

other side router is actually third party router, i do not have access on there, i just wanna make sure on my side router first

[Flavio Miranda]

This messages indicates that the router (yours or others) is trying to negociate aditional capabilities and one side does not understand.  This can be multiple protocol like IPv6 and/or muticast protocol.

[paul driver]

Hello
Looks like possible mismatch capabilities, try the following:
router bgp xxx
neighbor 172.16.254.29 dont−capability−negotiate
neighbor 172.16.254.33 dont−capability−negotiate

[agus.siswanto]

Hi Paul
is there any alternate command ? unfortunate in cisco 3945 there is no such that command available

[paul driver]

Hello

It is a hidden command, append it manually and it should be accepted.

[paul mebale]

Hello 

I am presently facing this issue while processing iBGP between cisco and juniper device. 

The "dont−capability−negotiate" doesn't solve the issue. VPNV4 prefixes are not exchanged with the juniper peer.

From the cisco' side i have 

Route refresh: advertised and received(new)
Four-octets ASN Capability: advertised and received
Address family IPv4 Unicast: advertised and received
Address family VPNv4 Unicast: advertised 

Is there a way to solve this interoperability issue?

Regards

[Harold Ritter]

Hi @paul mebale ,

You have already posted this question in another conversation. I will try to help in this other conversation.

Regards,