Ethereal-dev: [Ethereal-dev] bad ISIS system ID display format

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: "Feiyun Wang" <ffcs@xxxxxxxxxxx>
Date: Thu, 4 Dec 2003 11:30:55 +0800
Hi all,

I am reporting IS-IS protocol related bugs in Ethereal 0.9.16.

The display format for IS-IS system ID related stuff (System ID, Pseudonode ID, LSP ID) is not good.
The conventional display format should be:
System ID: 920B.920B.920B
Pseudonode ID: 920B.920B.920B.01
LSP ID: 920B.920B.920B.00-00

Affected IS-IS protocol PDU fields:
1. ISIS HELLO PDU
        System-ID {Sender of PDU} : 16407000.9175
        System-ID {Designated IS} : 16407000.917502
  should be displayed as:
        System-ID {Sender of PDU} : 1640.7000.9175
        System-ID {Designated IS} : 1640.7000.9175.02
2. ISIS LSP PDU
        LSP-ID: 11001111.ffee0000
            IS Neighbor:  16407000.917501
  should be displayed as:
        LSP-ID: 1100.1111.ffee.00-00
            IS Neighbor:  1640.7000.9175.01
3. ISIS CSNP PDU
        Source-ID:    16407000.917500
        Start LSP-ID: 00000000.00000000
        End LSP-ID: ffffffff.ffffffff
        LSP entries (160)
            LSP-ID: 16407000.91750000, Sequence: 0x00000005, Lifetime:  1035s, Checksum: 0x5253
  should be displayed as:
        Source-ID:    1640.7000.9175.00
        Start LSP-ID: 0000.0000.0000.00-00
        End LSP-ID: ffff.ffff.ffff.ff-ff
        LSP entries (160)
            LSP-ID: 1640.7000.9175.00-00, Sequence: 0x00000005, Lifetime:  1035s, Checksum: 0x5253
4. ISIS PSNP PDU
        Source-ID: 16407000.917500
        LSP entries (16)
            LSP-ID: 11001111.ffee0000, Sequence: 0x00000002, Lifetime:     0s, Checksum: 0x69de
                LSP-ID:             : 11001111.ffee0000
  should be displayed as:
        Source-ID: 1640.7000.9175.00
        LSP entries (16)
            LSP-ID: 1100.1111.ffee.00-00, Sequence: 0x00000002, Lifetime:     0s, Checksum: 0x69de
                LSP-ID:             : 1100.1111.ffee.00-00
5. All Info Column in packet summary panel for the above PDUs
        Info
        L1 HELLO, System-ID: 16407000.9175
        L2 HELLO, System-ID: 16407000.9175
        L1 CSNP, Source-ID: 16407000.917500, Start LSP-ID: 00000000.00000000, End LSP-ID: ffffffff.ffffffff
        L2 CSNP, Source-ID: 16407000.917500, Start LSP-ID: 00000000.00000000, End LSP-ID: ffffffff.ffffffff
        L1 LSP, LSP-ID: 11001111.ffee0000, Sequence: 0x00000002, Lifetime:     0s
        L1 PSNP, Source-ID: 16407000.917500
        L2 LSP, LSP-ID: 11001111.ffee0000, Sequence: 0x00000002, Lifetime:     0s
        L2 PSNP, Source-ID: 16407000.917500
  should be displayed as:
        L1 HELLO, System-ID: 1640.7000.9175
        L2 HELLO, System-ID: 1640.7000.9175
        L1 CSNP, Source-ID: 1640.7000.9175.00, Start LSP-ID: 0000.0000.0000.00-00, End LSP-ID: ffff.ffff.ffff.ff-ff
        L2 CSNP, Source-ID: 1640.7000.9175.00, Start LSP-ID: 0000.0000.0000.00-00, End LSP-ID: ffff.ffff.ffff.ff-ff
        L1 LSP, LSP-ID: 1100.1111.ffee.00-00, Sequence: 0x00000002, Lifetime:     0s
        L1 PSNP, Source-ID: 1640.7000.9175.00
        L2 LSP, LSP-ID: 1100.1111.ffee.00-00, Sequence: 0x00000002, Lifetime:     0s
        L2 PSNP, Source-ID: 1640.7000.9175.00
The display format in Ethereal 0.9.16 for these fields is very annoying.
I am not sure if I have all related PDU fields checked, and I suggest the bug resolver to go through other IS-IS PDU TLVs.

BTW, here is an example of Cisco router's output for reference:
cisco7206>show clns neighbor

System Id      Interface   SNPA                State  Holdtime  Type Protocol
920B.920B.920B Fa3/0       00e0.0030.c3a6      Up     9999      L1L2 IS-IS
920B.920B.920B PO1/0       *HDLC*              Up     26        L1L2 IS-IS
cisco7206>show clns is-neighbors

System Id      Interface   State  Type Priority  Circuit Id         Format
920B.920B.920B Fa3/0       Init   L1L2 64/128    cisco7206.01       Phase V
920B.920B.920B PO1/0       Up     L1L2 0 /0      85                 Phase V
cisco7206>show isis database

IS-IS Level-1 Link State Database:
LSPID                 LSP Seq Num  LSP Checksum  LSP Holdtime      ATT/P/OL
cisco7206.00-00     * 0x0000010C   0x4C9A        1192              0/0/0
cisco7206.01-00     * 0x000000C3   0x5C63        0 (1197)          0/0/0
920B.920B.920B.00-00  0x00000111   0xBB1D        1198              0/0/0
920B.920B.920B.83-00  0x00000169   0x3593        1197              0/0/0
IS-IS Level-2 Link State Database:
LSPID                 LSP Seq Num  LSP Checksum  LSP Holdtime      ATT/P/OL
cisco7206.00-00     * 0x00000107   0xF7F3        1192              0/0/0
cisco7206.01-00     * 0x000000C0   0x6260        0 (1198)          0/0/0
920B.920B.920B.00-00  0x0000011F   0xD77A        1198              0/0/0
920B.920B.920B.83-00  0x0000012E   0xDA96        0 (1199)          0/0/0
cisco7206>show isis topology

IS-IS IP paths to level-1 routers
System Id            Metric     Next-Hop             Interface   SNPA
cisco7206            --
920B.920B.920B       10         920B.920B.920B       Fa3/0       00e0.0030.c3a6
                                920B.920B.920B       PO1/0       *HDLC*

IS-IS IP paths to level-2 routers
System Id            Metric     Next-Hop             Interface   SNPA
cisco7206            --
920B.920B.920B       10         920B.920B.920B       Fa3/0       00e0.0030.c3a6
                                920B.920B.920B       PO1/0       *HDLC*
cisco7206>
(Forget things like "cisco7206.01" and "cisco7206.00-00" as they are using hostname shortcut)

The attachment is the file which contains some captured IS-IS packets, which is used when I found this error.

Best regards,
Feiyun Wang (feiyunw at yahoo dot com)

Attachment: isis.pkt
Description: Binary data