Step 3: Analyze IS-IS-Link State Packets in Detail
Action
To analyze IS-IS link-state packets (LSPs) in detail, follow these steps:
- In configuration mode, go to the following hierarchy level:
[edit]user@host#edit protocols isis traceoptions- Configure IS-IS open messages:
[edit protocols isis traceoptions]user@host#set flag lsp detail- Verify the configuration:
user@host#show[edit protocols isis traceoptions]user@host#showfile isislog size 5m world-readable;flag error;flag lsp detail;
- Commit the configuration:
user@host#commit- View the contents of the file containing the detailed messages:
user@host#run show logfilenameuser@host#run show log isislogNov 28 20:17:24 Received L2 LSP abc-core-01.00-00, interface so-1/1/0.0Nov 28 20:17:24 from abc-core-01Nov 28 20:17:24 sequence 0x1c4f9, checksum 0x9fea, lifetime 1199Nov 28 20:17:24 max area 0, length 426Nov 28 20:17:24 no partition repair, no database overloadNov 28 20:17:24 IS type 3, metric type 0Nov 28 20:17:24 area address 99.0908 (1)Nov 28 20:17:24 speaks CLNPNov 28 20:17:24 speaks IPNov 28 20:17:24 dyn hostname abc-core-01Nov 28 20:17:24 IP address10.10.134.11Nov 28 20:17:24 IP prefix: 10.10.10.0/30 metric 1 upNov 28 20:17:24 IP prefix: 10.10.10.4/30 metric 5 upNov 28 20:17:24 IP prefix: 10.10.10.56/30 metric 5 upNov 28 20:17:24 IP prefix: 10.10.10.52/30 metric 1 upNov 28 20:17:24 IP prefix: 10.10.10.64/30 metric 5 upNov 28 20:17:24 IP prefix: 10.10.10.20/30 metric 5 upNov 28 20:17:24 IP prefix: 10.10.10.28/30 metric 5 upNov 28 20:17:24 IP prefix: 10.10.10.44/30 metric 5 upNov 28 20:17:24 IP prefix 10.10.10.0 255.255.255.252Nov 28 20:17:24 internal, metrics: default 1Nov 28 20:17:24 IP prefix 10.10.10.4 255.255.255.252Nov 28 20:17:24 internal, metrics: default 5Nov 28 20:17:24 IP prefix 10.10.10.56 255.255.255.252Nov 28 20:17:24 internal, metrics: default 5Nov 28 20:17:24 IP prefix 10.10.10.52 255.255.255.252Nov 28 20:17:24 internal, metrics: default 1Nov 28 20:17:24 IP prefix 10.10.10.64 255.255.255.252Nov 28 20:17:24 internal, metrics: default 5Nov 28 20:17:24 IP prefix 10.10.10.20 255.255.255.252Nov 28 20:17:24 internal, metrics: default 5Nov 28 20:17:24 IP prefix 10.10.10.28 255.255.255.252Nov 28 20:17:24 internal, metrics: default 5Nov 28 20:17:24 IP prefix 10.10.10.44 255.255.255.252Nov 28 20:17:24 internal, metrics: default 5Nov 28 20:17:24 IS neighbors:Nov 28 20:17:24 IS neighbor abc-core-02.00Nov 28 20:17:24 internal, metrics: default 1[...Output truncated...]Nov 28 20:17:24 internal, metrics: default 5Nov 28 20:17:24 IS neighbor abc-brdr-01.00Nov 28 20:17:24 internal, metrics: default 5Nov 28 20:17:24 IS neighbor abc-core-02.00, metric: 1Nov 28 20:17:24 IS neighbor abc-esr-02.00, metric: 5Nov 28 20:17:24 IS neighbor abc-edge-03.00, metric: 5Nov 28 20:17:24 IS neighbor abc-edge-01.00, metric: 5Nov 28 20:17:24 IS neighbor abc-edge-02.00, metric: 5Nov 28 20:17:24 IS neighbor abc-brdr-01.00, metric: 5Nov 28 20:17:24 IP prefix:10.10.134.11/32 metric 0 upNov 28 20:17:24 IP prefix: 10.11.0.0/16 metric 5 upNov 28 20:17:24 IP prefix: 10.211.0.0/16 metric 0 upNov 28 20:17:24 IP prefix10.10.134.11 255.255.255.255Nov 28 20:17:24 internal, metrics: default 0Nov 28 20:17:24 IP prefix 10.11.0.0 255.255.0.0Nov 28 20:17:24 internal, metrics: default 5Nov 28 20:17:24 IP prefix 10.211.0.0 255.255.0.0Nov 28 20:17:24 internal, metrics: default 0Nov 28 20:17:24 Updating LSPNov 28 20:17:24 Updating L2 LSP abc-core-01.00-00 in TEDNov 28 20:17:24 Analyzing subtlv's for abc-core-02.00Nov 28 20:17:24 Analysis completeNov 28 20:17:24 Analyzing subtlv's for abc-esr-02.00Nov 28 20:17:24 Analysis completeNov 28 20:17:24 Analyzing subtlv's for abc-edge-03.00Nov 28 20:17:24 Analysis completeNov 28 20:17:24 Analyzing subtlv's for abc-edge-01.00Nov 28 20:17:24 Analysis completeNov 28 20:17:24 Analyzing subtlv's for abc-edge-02.00Nov 28 20:17:24 Analysis completeNov 28 20:17:24 Analyzing subtlv's for abc-brdr-01.00Nov 28 20:17:24 Analysis completeNov 28 20:17:24 Scheduling L2 LSP abc-core-01.00-00 sequence 0x1c4f9 on interface so-1/1/1.0