[31918] in North American Network Operators' Group
IS-IS protocol implementation problem
daemon@ATHENA.MIT.EDU (Sean Donelan)
Sun Oct 29 17:58:29 2000
Date: 29 Oct 2000 14:56:21 -0800
Message-ID: <20001029225621.13695.cpmta@c004.sfo.cp.net>
Content-Type: text/plain
Content-Disposition: inline
Mime-Version: 1.0
To: nanog@merit.edu
From: Sean Donelan <sean@donelan.com>
Errors-To: owner-nanog-outgoing@merit.edu
Network operators using IS-IS on Cisco should be aware of a problem
which can result in their routers reloading unexpectedly when a corrupt
IS-IS packet is received. Cisco has fixed the problem in various 12.0
software trains. The problem can cascade through a single provider's
network. Because IS-IS is an IGP protocol, it does not propagate between
providers.
This has already affected a provider. I haven't found out what is
originating the bad IS-IS packet, i.e. is this an inter-vender operability
issue?
