Tracing IS-IS Protocol Traffic

You can trace various types of IS-IS protocol traffic to help debug IS-IS protocol issues. To trace IS-IS protocol traffic include the traceoptions statement at the [edit protocols isis] hierarchy level:

traceoptions {file filename <files number> <size size> <world-readable | no-world-readable>;flag flag <flag-modifier> <disable>;}

You can specify the following IS-IS protocol-specific trace options using the flag statement:

You can optionally specify one or more of the following flag modifiers:

Global tracing options are inherited from the configuration set by the traceoptions statement at the [edit routing-options] hierarchy level. You can override the following global trace options for the IS-IS protocol using the traceoptions flag statement included at the [edit protocols isis] hierarchy level:

Note: Use the trace flag all with caution as this may cause the CPU to become very busy.

Examples: Tracing IS-IS Protocol Traffic

A common configuration traces SPF calculations, LSP calculations, normal protocol operations, and errors in protocol operation:

[edit]protocols {isis {traceoptions {file isis-log size 1m files 10;flag spf;flag lsp;flag error;flag normal;}}}

Trace only unusual or abnormal operations to the file routing-log, and trace detailed information about all IS-IS packets to the file isis-log:

[edit]routing-options {traceoptions {file routing-log;}}protocols {isis {traceoptions {file isis-log size 10k files 5;flag csn detail;flag hello detail;flag lsp detail;flag psn detail;}}}

Perform detailed tracing of mesh-group flooding:

[edit]protocols {isis {traceoptions {file isis-log;flag lsp detail;}}}

IS-IS LSP packets that contain errors are discarded by default. To log these errors, specify the error tracing operation:

[edit]protocols {isis {traceoptions {file isis-log;flag error;}}}

Related Topics