Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Analyzing IS-IS Link-State PDUs in Detail

    To analyze IS-IS link-state PDUs in detail, follow these steps:

    1. Configure IS-IS open messages.
      [edit protocols isis traceoptions]user@host# set flag lsp detail
    2. Verify the configuration.
      user@host# show

      For example:

      [edit protocols isis traceoptions]
      user@host# show 
      file isislog size 5m world-readable;
      flag error;
      flag lsp detail;
    3. Commit the configuration.
      user@host# commit
    4. View the contents of the file containing the detailed messages.
      user@host# run show log filename

      For example:

      user@host# run show log isislog
      Nov 28 20:17:24 Received L2 LSP abc-core-01.00-00, interface so-1/1/0.0
      Nov 28 20:17:24     from abc-core-01
      Nov 28 20:17:24     sequence 0x1c4f9, checksum 0x9fea, lifetime 1199
      Nov 28 20:17:24     max area 0, length 426
      Nov 28 20:17:24     no partition repair, no database overload
      Nov 28 20:17:24     IS type 3, metric type 0
      Nov 28 20:17:24     area address 99.0908 (1)
      Nov 28 20:17:24     speaks CLNP
      Nov 28 20:17:24     speaks IP
      Nov 28 20:17:24     dyn hostname abc-core-01
      Nov 28 20:17:24     IP address 10.10.134.11
      Nov 28 20:17:24    IP prefix: 10.10.10.0/30 metric 1 up
      Nov 28 20:17:24    IP prefix: 10.10.10.4/30 metric 5 up
      Nov 28 20:17:24    IP prefix: 10.10.10.56/30 metric 5 up
      Nov 28 20:17:24    IP prefix: 10.10.10.52/30 metric 1 up
      Nov 28 20:17:24    IP prefix: 10.10.10.64/30 metric 5 up
      Nov 28 20:17:24    IP prefix: 10.10.10.20/30 metric 5 up
      Nov 28 20:17:24    IP prefix: 10.10.10.28/30 metric 5 up
      Nov 28 20:17:24    IP prefix: 10.10.10.44/30 metric 5 up
      Nov 28 20:17:24     IP prefix 10.10.10.0 255.255.255.252
      Nov 28 20:17:24     internal, metrics: default 1
      Nov 28 20:17:24     IP prefix 10.10.10.4 255.255.255.252
      Nov 28 20:17:24     internal, metrics: default 5
      Nov 28 20:17:24     IP prefix 10.10.10.56 255.255.255.252
      Nov 28 20:17:24     internal, metrics: default 5
      Nov 28 20:17:24     IP prefix 10.10.10.52 255.255.255.252
      Nov 28 20:17:24     internal, metrics: default 1
      Nov 28 20:17:24     IP prefix 10.10.10.64 255.255.255.252
      Nov 28 20:17:24     internal, metrics: default 5
      Nov 28 20:17:24     IP prefix 10.10.10.20 255.255.255.252
      Nov 28 20:17:24     internal, metrics: default 5
      Nov 28 20:17:24     IP prefix 10.10.10.28 255.255.255.252
      Nov 28 20:17:24     internal, metrics: default 5
      Nov 28 20:17:24     IP prefix 10.10.10.44 255.255.255.252
      Nov 28 20:17:24     internal, metrics: default 5
      Nov 28 20:17:24     IS neighbors:
      Nov 28 20:17:24     IS neighbor abc-core-02.00
      Nov 28 20:17:24     internal, metrics: default 1
      [...Output truncated...]
      Nov 28 20:17:24     internal, metrics: default 5
      Nov 28 20:17:24     IS neighbor abc-brdr-01.00
      Nov 28 20:17:24     internal, metrics: default 5
      Nov 28 20:17:24     IS neighbor abc-core-02.00, metric: 1
      Nov 28 20:17:24     IS neighbor abc-esr-02.00, metric: 5
      Nov 28 20:17:24     IS neighbor abc-edge-03.00, metric: 5
      Nov 28 20:17:24     IS neighbor abc-edge-01.00, metric: 5
      Nov 28 20:17:24     IS neighbor abc-edge-02.00, metric: 5
      Nov 28 20:17:24     IS neighbor abc-brdr-01.00, metric: 5
      Nov 28 20:17:24    IP prefix: 10.10.134.11/32 metric 0 up
      Nov 28 20:17:24    IP prefix: 10.11.0.0/16 metric 5 up
      Nov 28 20:17:24    IP prefix: 10.211.0.0/16 metric 0 up
      Nov 28 20:17:24     IP prefix 10.10.134.11 255.255.255.255
      Nov 28 20:17:24     internal, metrics: default 0
      Nov 28 20:17:24     IP prefix 10.11.0.0 255.255.0.0
      Nov 28 20:17:24     internal, metrics: default 5
      Nov 28 20:17:24     IP prefix 10.211.0.0 255.255.0.0
      Nov 28 20:17:24     internal, metrics: default 0
      Nov 28 20:17:24     Updating LSP
      Nov 28 20:17:24 Updating L2 LSP abc-core-01.00-00 in TED
      Nov 28 20:17:24 Analyzing subtlv's for abc-core-02.00
      Nov 28 20:17:24 Analysis complete
      Nov 28 20:17:24 Analyzing subtlv's for abc-esr-02.00
      Nov 28 20:17:24 Analysis complete
      Nov 28 20:17:24 Analyzing subtlv's for abc-edge-03.00
      Nov 28 20:17:24 Analysis complete
      Nov 28 20:17:24 Analyzing subtlv's for abc-edge-01.00
      Nov 28 20:17:24 Analysis complete
      Nov 28 20:17:24 Analyzing subtlv's for abc-edge-02.00
      Nov 28 20:17:24 Analysis complete
      Nov 28 20:17:24 Analyzing subtlv's for abc-brdr-01.00
      Nov 28 20:17:24 Analysis complete
      Nov 28 20:17:24     Scheduling L2 LSP abc-core-01.00-00 sequence 0x1c4f9 on interface so-1/1/1.0

    Published: 2013-07-25