Seems it is a Cisco bug, ..following error message: %BGP-3-NOTIFICATION: sent to neighbor 1::1 passive 2/3 (BGP identifier wrong) 4 bytes 01000003 Conditions...Workaround: Enter the clear ip bgp command. *CSCsy29534... 06 Oct 2009 - www.cisco.com/en/US/docs/ios/12_2sr/release/notes/122SRcavs1.html
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Andy Davidson Sent: Friday, November 20, 2009 8:22 PM To: [email protected] Subject: [c-nsp] (BGP identifier wrong) error on majority of ebgp peers Hi, I have a Cisco 6509 with SUP720-3BXL. It has over a hundred bgp peers configured, two full tables, 4 ibgp, several peerings at an IXP. Seemingly without a config change, there are some sessions which refuse to establish, because of a bgp notification : %BGP-3-NOTIFICATION: received from neighbor XXX 2/3 (BGP identifier wrong) 4 bytes XXX The router-id has not been changed - it was using the address from Loopback 0. The router-id *is* unique, and the remote side of the peering is using a different address. We tried modifying the local router-id to match an address used on a point-to-point link and clearing all sessions - same error. This router was loaded with SXF3, moved to SXF16, moved to SXI3 - same error seen with all three. We removed the router bgp xx config and pasted it back in - when the sessions established the same error was noticed. There appears to be no commonality (eg. linecard) between the sessions which establish, and those which don't - for example, some over the shared ixp link establish fine, and some do not due to this router-id clash notification. It is always the same sessions which either come up, or refuse to come up each time. The ibgp sessions always establish (fortunately). Has anyone seen this before ? Thanks andy _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ The information contained in this transmission may contain privileged and confidential information. It is intended only for the use of the person(s) named above. If you are not the intended recipient, you are hereby notified that any review, dissemination, distribution or duplication of this communication is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
