Thank you Aaron. In my humble opinion, syslog is a bit inapplicable. The way I know it, it will have an error message like "ISIS session to <neighboring router hostname> changed to down" (maybe it do has interface name, I don't recall the exact message right now).
Anyhow, not the neighboring router hostname nor interface name, have the exact circuit (that went down) information. In our case, it encoded into interface description. To your knowledge, the tools you mentioned, are able to append that information to the original syslog message? בתאריך 16 בספט' 2017 4:57 AM, "Aaron Gould" <aar...@gvtc.com> כתב: > Kiwi syslogd or maybe splunk > > -Aaron > > _______________________________________________ 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/
