To trace IS-IS protocol traffic, you can specify options in the global traceoptions statement included at the [edit routing-options] hierarchy level, and you can specify IS-IS–specific options by including the traceoptions statement:
-
traceoptions {
- file filename <size size> <files number> <(world-readable
| no-world-readable)>;
- flag flag <flag-modifier> <disable>;
- }
For a list of hierarchy levels at which you can configure this statement, see the statement summary section for this statement.
You can specify the following IS-IS–specific trace options in the IS-IS flag statement:
You can optionally specify one or more of the following flag modifiers:
![]() |
Note: Use the trace flags detail and all with caution. These flags may cause the CPU to become very busy. |
For information about tracing and global tracing options, see Tracing Global Routing Protocol Operations.
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;
- }
- }
- }