We've tried pretty much every relevant isis and clns debug and haven't found one that works. It's pretty strange. I wonder if this is just a quirk of the code we're running.
On Mon, Jul 1, 2013 at 10:31 AM, Aaron <[email protected]> wrote: > debug isis > possibly add lsp at the end > > > On Mon, Jul 1, 2013 at 11:41 AM, John Neiberger <[email protected]>wrote: > >> This one has me and TAC stumped. Let's say you have a 7600 with multiple >> devices connected to it running ISIS. One of them has the wrong >> authentication key, so you see a bunch of this in the logs: >> >> %CLNS-4-AUTH_FAIL: ISIS: LSP authentication failed >> >> How do you find out what neighbor is causing that? We have not found any >> show command or debug command, either ISIS or CLNS, that would show us the >> source of the problem. This is very easy in OSPF, but it's starting to >> look >> pretty dang hard to do with ISIS. >> >> Does anyone know what ninja commands or procedure I need to find the >> source >> of ISIS authentication failures from the router CLI? >> >> Thanks, >> John >> _______________________________________________ >> 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/
