Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

%BGP-3-NOTIFICATION Erro

Hello Friends:

Seeing the following error in the log messages and seems to be mostly cosmetic as the BGP neighbor is up and working.

Sep xx 07:12:48 EDT: %BGP-3-NOTIFICATION: sent to neighbor 172.16.1.1 passive 2/8 (no supported AFI/SAFI) 3 bytes 000000

The version of IOS is:

System image file is "disk0:c7600s72033-advipservices-mz.122-33.SRB3.bin"

CISCO7609 (R7000) processor (revision 1.2) with 983008K/65536K bytes of memory.

My thoughts on it was to perform a BGP shutdown for this neighbor, wait a few minutes and then re-enable it back up. If it persists, I was going to open a TAC case. Please feel free to put into your comments/suggestions in the event if somebody has experienced this in the past.

Many Thanks,

Brian

1 ACCEPTED SOLUTION

Accepted Solutions
Hall of Fame Super Silver

Re: %BGP-3-NOTIFICATION Erro

Hello Brian,

the eBGP peer 172.16.1.1  is configured for multiprotocol BGP and AFI=2 means IPv4 multicast

see

http://www.faqs.org/rfcs/rfc2858.html

the message simply states that your side is not configured for speaking on address family IPv4 multicast at least not with this specific BGP peer.

Hope to help

Giuseppe

2 REPLIES
Hall of Fame Super Silver

Re: %BGP-3-NOTIFICATION Erro

Hello Brian,

the eBGP peer 172.16.1.1  is configured for multiprotocol BGP and AFI=2 means IPv4 multicast

see

http://www.faqs.org/rfcs/rfc2858.html

the message simply states that your side is not configured for speaking on address family IPv4 multicast at least not with this specific BGP peer.

Hope to help

Giuseppe

Community Member

Re: %BGP-3-NOTIFICATION Erro

The issue has been resolved and here was the fix. The customer has two BGP peers with us, an existing 10m Metro-E and a new upcoming frame T1; the frame T1 was currently down and it looks like the customer's CPE was trying to bring that second peer up over the Metro-E circuit causing that notification.

However, this is what TAC had to say about that:

*****************************************************************************************************

CSCsj03911
Remove MSGDUMP message at no supported AFI/SAFI notification
Symptom:
Unsupported AFI/SAFI BGP Notification message appear on the console.
Conditions:
This happens when  connection collision occur during  multisession negotiation in BGP
Workaround:
None
*****************************************************************************************************
CSCsq18756
"Multi-session Capability" is enabled as default
Symptoms:
MTR (with multi-session capability) is enabled by default and  cannot be disabled. Old CE routers do not understand the multi-session capability therefore they disconnect the BGP session with notification.
Conditions:
The symptoms are observed when the MTR feature is enabled as default and when multi-session capability is sent in the default BGP peer.
Workaround:
There is no workaround.

******************************************************************************************************

You can go to the following link to review them both:

http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs

Thanks and regards,

UGOT2NOME

21574
Views
0
Helpful
2
Replies
CreatePlease to create content