Andy Davidson wrote: > 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.
Seems this could be a bug affecting the routers of our peers - when we rebuilt the session config our side, the same behaviour was observed, but when the remote party deletes and recreates the config facing us, the session is allowed to establish. Andy _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
