Re: [Isis-wg] Interface IP addresses from IS-IS

Hannes Gredler <hannes@juniper.net> Wed, 12 October 2005 15:03 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPi8o-0002Tj-C5; Wed, 12 Oct 2005 11:03:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPi8n-0002TS-0s for isis-wg@megatron.ietf.org; Wed, 12 Oct 2005 11:03:37 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26746 for <isis-wg@ietf.org>; Wed, 12 Oct 2005 11:03:33 -0400 (EDT)
Received: from borg.juniper.net ([207.17.137.119]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EPiJ6-00055I-O4 for isis-wg@ietf.org; Wed, 12 Oct 2005 11:14:18 -0400
Received: from unknown (HELO beta.jnpr.net) (172.24.18.109) by borg.juniper.net with ESMTP; 12 Oct 2005 08:03:26 -0700
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="3.97,207,1125903600"; d="scan'208"; a="504211949:sNHT98325278"
Received: from [172.26.200.92] ([172.26.200.92]) by beta.jnpr.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 12 Oct 2005 08:03:25 -0700
Message-ID: <434D25BC.3010406@juniper.net>
Date: Wed, 12 Oct 2005 17:03:24 +0200
From: Hannes Gredler <hannes@juniper.net>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: rup@sce.carleton.ca
Subject: Re: [Isis-wg] Interface IP addresses from IS-IS
References: <20051011182010.ajw7ta440cs4ggkc@webmail.sce.carleton.ca>
In-Reply-To: <20051011182010.ajw7ta440cs4ggkc@webmail.sce.carleton.ca>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Oct 2005 15:03:26.0021 (UTC) FILETIME=[18C1E750:01C5CF3E]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0fa76816851382eb71b0a882ccdc29ac
Content-Transfer-Encoding: 7bit
Cc: isis-wg@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/isis-wg>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
Sender: isis-wg-bounces@ietf.org
Errors-To: isis-wg-bounces@ietf.org


rup@sce.carleton.ca wrote:
> Hi guys,
> 
> Does any of the IS-IS packets contains the IP addresses of all the interfaces of
> router runnning IS-IS?

LSPs (if traffic-engineering is enabled on a link) may contain subTLV 6,8
      to the extended IS reach TLV 22.

i.e. see below a tcpdump output of an IS-IS LSP:

18:28:54.259841 IS-IS, length 333
         L2 LSP, hlen: 27, v: 1, pdu-v: 1, sys-id-len: 6 (0), max-area: 3 (0)
           lsp-id: 0102.5500.6110.00-00, seq: 0x00000005, lifetime:  1198s
           chksum: 0x59e3 (correct), PDU length: 333, Flags: [ L1L2 IS ]
             Area address(es) TLV #1, length: 14
               Area address (length: 13): 47.0005.80ff.f800.0000.0108.0001
             Protocols supported TLV #129, length: 2
               NLPID(s): IPv4 (0xcc), IPv6 (0x8e)
             Traffic Engineering Router ID TLV #134, length: 4
               Traffic Engineering Router ID: 10.255.6.110
             IPv4 Interface address(es) TLV #132, length: 4
               IPv4 interface address: 10.255.6.110
             Hostname TLV #137, length: 8
               Hostname: schnapps
             IS Reachability TLV #2, length: 12
               IsNotVirtual
               IS Neighbor: 0102.5507.0001.00, Default Metric: 10, Internal
             Extended IS Reachability TLV #22, length: 94
               IS Neighbor: 0102.5507.0001.00, Metric: 10, sub-TLVs present (83)
                 IPv4 interface address subTLV #6, length: 4, 10.40.2.1
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                 IPv4 neighbor address subTLV #8, length: 4, 10.40.2.2
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
                 Unreserved bandwidth subTLV #11, length: 32
                   TE-Class 0: 154.520 Mbps
                   TE-Class 1: 116.640 Mbps
                   TE-Class 2: 77.760 Mbps
                   TE-Class 3: 38.880 Mbps
                   TE-Class 4: 155.520 Mbps
                   TE-Class 5: 116.640 Mbps
                   TE-Class 6: 77.760 Mbps
                   TE-Class 7: 38.880 Mbps
                 Reservable link bandwidth subTLV #10, length: 4, 155.520 Mbps
                 Maximum link bandwidth subTLV #9, length: 4, 155.520 Mbps
                 Administrative groups subTLV #3, length: 4, 0x00000000
                 Bandwidth Constraints (old) subTLV #12, length: 17
                 Bandwidth Constraints Model ID: Russian dolls (0)
                   Bandwidth constraint CT0: 155.520 Mbps
                   Bandwidth constraint CT1: 116.640 Mbps
                   Bandwidth constraint CT2: 77.760 Mbps
                   Bandwidth constraint CT3: 38.880 Mbps
             IPv4 Internal Reachability TLV #128, length: 72
               IPv4 prefix:    10.255.6.110/32, Distribution: up, Metric: 0, Internal
               IPv4 prefix:       10.40.2.0/30, Distribution: up, Metric: 10, Internal
               IPv4 prefix:       10.40.1.0/30, Distribution: up, Metric: 20, Internal
               IPv4 prefix:       10.40.3.0/30, Distribution: up, Metric: 20, Internal
               IPv4 prefix:     10.255.70.1/32, Distribution: up, Metric: 10, Internal
               IPv4 prefix:   10.255.71.212/32, Distribution: up, Metric: 20, Internal
             Extended IPv4 Reachability TLV #135, length: 54
               IPv4 prefix:    10.255.6.110/32, Distribution: up, Metric: 0
               IPv4 prefix:       10.40.2.0/30, Distribution: up, Metric: 10
               IPv4 prefix:       10.40.1.0/30, Distribution: up, Metric: 20
               IPv4 prefix:       10.40.3.0/30, Distribution: up, Metric: 20
               IPv4 prefix:     10.255.70.1/32, Distribution: up, Metric: 10
               IPv4 prefix:   10.255.71.212/32, Distribution: up, Metric: 20
             IPv6 reachability TLV #236, length: 22
               IPv6 prefix: abcd::10:255:6:110/128, Distribution: up, Metric: 0, Internal

> I looked at TLV type 132, but it requires at least one interface IP address
> only, rest are optional. The TLV type 128 can give you the prefix and netmask
> but not the exact IP address.

TLV 132 is typically used in IIHs - some implementations add also the IP address of the
loopback IP adress packeged in TLV 132 in LSPs.

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg