cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
9102
Views
1
Helpful
7
Replies

BGP down with error -no supported AFI/SAFI

MilanVerma17
Level 1
Level 1

Hello All,

I have a 4331 router that has been configured with BGP. Presently BGP is flapping and giving error no support AFI/SAFI.

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

Thanks.

Log-

Oct 13 00:40:13: %BGP-5-ADJCHANGE: neighbor 192.168.251.242 passive Down AFI/SAFI not supported
Oct 13 00:41:51: %BGP-3-NOTIFICATION: received from neighbor 192.168.251.242 4/0 (hold time expired) 0 bytes
Oct 13 00:41:51: %BGP-5-NBR_RESET: Neighbor 192.168.251.242 reset (BGP Notification received)
Oct 13 00:41:51: %BGP-5-ADJCHANGE: neighbor 192.168.251.242 Down BGP Notification received
Oct 13 00:41:51: %BGP_SESSION-5-ADJCHANGE: neighbor 192.168.251.242 IPv4 Unicast topology base removed from session BGP Notification received
Oct 13 00:42:02: %BGP-5-ADJCHANGE: neighbor 192.168.251.242 Up

7 Replies 7

Hello,

 

how is your BGP confgured, are you using 'address family', and is the other side configured in the same way ? Would be helpful to see the configs from both BGP neighbors...

No, address family is not configured.

A-end
router bgp 65105
bgp log-neighbor-changes
neighbor 192.168.251.242 remote-as 65361
neighbor 192.168.251.242 next-hop-self
neighbor 192.168.251.242 send-community
neighbor 192.168.251.242 soft-reconfiguration inbound

B-end
router bgp 65361
bgp log-neighbor-change
neighbor 192.168.251.241 remote-as 65105
neighbor 192.168.251.241 next-hop-self
neighbor 192.168.251.241 send-community
neighbor 192.168.251.241 soft-reconfiguration inbound

Hello,

 

it looks like your neighbors are directly connected ? In that case, you don't need the next hop self, try and remove that from both routers.

Giuseppe Larosa
Hall of Fame
Hall of Fame

Hello @MilanVerma17 ,

the error says that the other peer is attempting to negoatiate an unsupported ( by local device) address family AFI sub address family SAFI.

 

>> Oct 13 00:40:13: %BGP-5-ADJCHANGE: neighbor 192.168.251.242 passive Down AFI/SAFI not supported
Oct 13 00:41:51: %BGP-3-NOTIFICATION: received from neighbor 192.168.251.242 4/0 (hold time expired) 0 bytes
Oct 13 00:41:51: %BGP-5-NBR_RESET: Neighbor 192.168.251.242 reset (BGP Notification received)
Oct 13 00:41:51: %BGP-5-ADJCHANGE: neighbor 192.168.251.242 Down BGP Notification received
Oct 13 00:41:51: %BGP_SESSION-5-ADJCHANGE: neighbor 192.168.251.242 IPv4 Unicast topology base removed from session BGP Notification received
Oct 13 00:42:02: %BGP-5-ADJCHANGE: neighbor 192.168.251.242 Up

 

The AFI/subAFI that was not supported is likely  the one I have highlighted IPv4 Unicast topology base.

 

the local device is an ISR 4331 running IOS XE . what is the peer 192.168.251.242 ?

 

Is now the session stable after the initial issues or it is still flapping ?

 

Hope to help

Giuseppe

 

Hello


@MilanVerma17 wrote:

Hello All,

I have a 4331 router that has been configured with BGP. Presently BGP is flapping and giving error no support AFI/SAFI.

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

Thanks.

Log-

Oct 13 00:40:13: %BGP-5-ADJCHANGE: neighbor 192.168.251.242 passive Down AFI/SAFI not supported
Oct 13 00:41:51: %BGP-3-NOTIFICATION: received from neighbor 192.168.251.242 4/0 (hold time expired) 0 bytes
Oct 13 00:41:51: %BGP-5-NBR_RESET: Neighbor 192.168.251.242 reset (BGP Notification received)
Oct 13 00:41:51: %BGP-5-ADJCHANGE: neighbor 192.168.251.242 Down BGP Notification received
Oct 13 00:41:51: %BGP_SESSION-5-ADJCHANGE: neighbor 192.168.251.242 IPv4 Unicast topology base removed from session BGP Notification received
Oct 13 00:42:02: %BGP-5-ADJCHANGE: neighbor 192.168.251.242 Up

 

A-end
router bgp 65105
bgp log-neighbor-changes
neighbor 192.168.251.242 remote-as 65361
neighbor 192.168.251.242 next-hop-self
neighbor 192.168.251.242 send-community
neighbor 192.168.251.242 soft-reconfiguration inbound

B-end
router bgp 65361
bgp log-neighbor-change
neighbor 192.168.251.241 remote-as 65105
neighbor 192.168.251.241 next-hop-self
neighbor 192.168.251.241 send-community
neighbor 192.168.251.241 soft-reconfiguration inbound


 

 

try the following:

router bgp xxx
no bgp default ipv4 multicast
no bgp default ipv4 unicast
address-family ipv4 unicast
neighbor x.x.x.x activate





Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

paul mebale
Level 1
Level 1

Hi all

I am presently facing an issue alike 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.
The only way to establish the bgp session is to delete the "family inet-vpn unicast"
command from the juniper side whereas it is used to set the vpnv4 AF.

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

From the cisco' side i have
NLRI for restart configured on peer: inet-unicast
NLRI advertised by peer: inet-unicast inet-vpn-unicast
NLRI for this session: inet-unicast
Peer supports Refresh capability (2)

Is there a way to solve this interoperability issue?

Regards

Hi @paul mebale ,

Can you please share more information about te issue itself, like logs, error messages, configuration snapshot and versions used on both sides.

It is generally preferable to open a new thread, rather than reopening an old one.

Regards,

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México
Review Cisco Networking for a $25 gift card