Re: [Isis-wg] Question about Purge LSP in RFC 1142

Dave Katz <dkatz@juniper.net> Fri, 19 October 2007 14:33 UTC

Return-path: <isis-wg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iisv8-00017n-20; Fri, 19 Oct 2007 10:33:50 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Iisv7-00017c-Ex for isis-wg@ietf.org; Fri, 19 Oct 2007 10:33:49 -0400
Received: from exprod7og107.obsmtp.com ([64.18.2.167]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Iisuz-0001VR-Jv for isis-wg@ietf.org; Fri, 19 Oct 2007 10:33:49 -0400
Received: from source ([66.129.224.36]) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP; Fri, 19 Oct 2007 07:33:04 PDT
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Fri, 19 Oct 2007 07:32:17 -0700
Received: from [172.16.12.139] (nimbus-sf.juniper.net [172.16.12.139]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id l9JEWGn32632; Fri, 19 Oct 2007 07:32:16 -0700 (PDT) (envelope-from dkatz@juniper.net)
In-Reply-To: <47189633.7040303@cisco.com>
References: <9b0da1460710140414s1a3d89byb9cc873fc964eddf@mail.gmail.com> <47189633.7040303@cisco.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <5CDD3344-4FBD-45F7-857E-553FFD0015B5@juniper.net>
Content-Transfer-Encoding: 7bit
From: Dave Katz <dkatz@juniper.net>
Subject: Re: [Isis-wg] Question about Purge LSP in RFC 1142
Date: Fri, 19 Oct 2007 08:32:15 -0600
To: mike shand <mshand@cisco.com>
X-Mailer: Apple Mail (2.752.3)
X-OriginalArrivalTime: 19 Oct 2007 14:32:17.0146 (UTC) FILETIME=[D943F5A0:01C8125C]
X-Spam-Score: -4.0 (----)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: "Theodore.Wang" <theodore.wang@gmail.com>, 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>
Errors-To: isis-wg-bounces@ietf.org

On Oct 19, 2007, at 5:34 AM, mike shand wrote:

>
>>
>> But in fact, in a huge network, it is hard to locate the router  
>> that generate the Purge LSP, and which is the situation I'm  
>> facing. A Corrupted LSP Storm is happening in the network and it  
>> lacks a efficient way to troubleshooting because we can only use  
>> "ignore checksum error" on every router to find the one that  
>> flooded the Purge LSP.
> It is for this reason (the purge storm) that the specification was  
> changed!

Yep.  There was a busted UUnet link in Texas, I believe, back in  
around '96, that was corrupting packets but delivering them with  
valid datalink checksums.  This caused every LSP crossing the link  
(which is, by definition, eventually *every* LSP) to be purged and  
reflooded.  And purged and reflooded.  It was quite spectacular, if  
rather unpleasant.  I don't quite remember how we found the bad  
link;  probably saw some other error indications at the ends.  A knob  
was added rather quickly.

--Dave

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