Dear All %BGP-3-NOTIFICATION: sent to neighbor x.x.x.x 2/7 (unsupported/disjointcapability) 0 bytes Thankx for you all for your participations and your solutions And a reply on Vicuna last e-mail about this problem is that am getting this msg repeated from over than 30 routers All routers are logging this msg to the syslog I'll check with your solutions and am going to post you the result Thankx again Regards -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Vicuna, Mark Sent: Monday, January 06, 2003 10:57 AM To: [EMAIL PROTECTED] Subject: RE: BGP problem [7:60338] >From the original post, sounds like he was getting repeated messages of that kind. rfc3392 is the current release. 2842 is obseleted by 3392. It does say in the last para of section 3, " 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. If terminated, such peering SHOULD NOT be re-established automatically. " Can the original poster confirm if the notications in the logs were once from each peer or repeated messages from numerous peers. -----Original Message----- From: John Murphy [mailto:[EMAIL PROTECTED]] Sent: Sunday, January 05, 2003 7:24 PM To: [EMAIL PROTECTED] Subject: Re: BGP problem [7:60338] The message format is FACILITY-SEVERITY-MNEMONIC. So this is a message from the BGP Facility, the severity indicates functionality may be affected, and the message identifier is 'Notification.' In this case the Error Code is 2 (Open) and the SubCode is 7 (Unsupported Capability - see RFC2842). The only time I've seen this is when there is an address-family mismatch, i.e., one peer is ipv4 only, one peer is vpnv4 with ipv4-unicast disabled, specifically when configuring MPLS VPNs using MBGP, but I'd expect you'd see the same message if you had any sort of address family (or other optional capability) mismatch. Of course, I don't have a PhD, nor my CCIE # yet, so I may not actually be worthy of the response I've typed. Best Regards, John ----- Original Message ----- From: "Charles" To: Sent: Sunday, January 05, 2003 3:43 PM Subject: Re: BGP problem [7:60338] > hey, > > %BGP-3-NOTIFICATION: sent to neighbor x.x.x.x 2/7 > > BGP-3 means it's a BGP UPDATE message error > 2/7 are the error subcodes (I believe!) > 2- unrecognized well known attribute > 7- AS Routing loop > > take a closer look at your configs, etc... is it possible you've got a loop > on your hands? > > hope this helps, > Charles > > > > ""Amr Essam"" wrote in message > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > Dear all > > > > I have been receiving this msg in all my routers during the past month > > and I have searched on how I can remove it but I didn't have any luck to > > find anything can tell on how to remove this entry to appear in my log > > The entry is: > > > > %BGP-3-NOTIFICATION: sent to neighbor x.x.x.x 2/7 (unsupported/disjoint > > capability) 0 bytes > > > > I hope I can find some advice on how to remove this entry to appear in > > my router logs > > > > Regards > > Amr
Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=60416&t=60338 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]