>From looking at the message I would think that the router's just reporting an error based on the standard error codes that are available in your standard BGP notification messages.
I'd imagine that the way the errors are reported could be different from vendor to vendor, but here's some decent info on the error codes in BGP notification messages: http://www.tcpipguide.com/free/t_BGPErrorReportingNotificationMessages-3.htm HTH, -JJ On Sat, Sep 27, 2008 at 10:45 AM, Paul Stewart <[EMAIL PROTECTED]> wrote: > Thanks - we discovered that the multihop session (the destination IP > address) wasn't reachable at all across the Internet ... still trying to > figure out why but that might explain the weird debug... > > Take care, > > Paul > > > -----Original Message----- > From: Oliver Boehmer (oboehmer) [mailto:[EMAIL PROTECTED] > Sent: September 27, 2008 12:34 PM > To: Paul Stewart; cisco-nsp > Subject: RE: [c-nsp] Weird BGP Error > > Paul Stewart <> wrote on Friday, September 26, 2008 7:40 PM: > >> Anyone ever seen this before? >> >> Sep 26 13:38:07: BGP_Router: unhandled major event code 128, minor 0 >> Sep 26 13:38:12: BGP_Router: unhandled major event code 128, minor 0 >> >> Trying to turn up a multihop eBGP session and not coming up ... did a >> debug on the nei IP address and got this.... > > As far as I've been able to find out, this message is completely > harmless (and should be removed from the debug).. So something else must > be going on. > > oli > > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
