Ignoring Lsp Errors - Juniper IGP - CONFIGURATION GUIDE V11.1.X Configuration Manual

JUNOSe 11.0.x IP, IPv6, and IGP Configuration Guide

Ignoring LSP Errors

You can configure the router to ignore rather than purge LSPs received with errors.
ignore-lsp-errors
372
Configuring Global IS-IS Parameters
To prevent real traffic from flowing through a router to an IS-IS network,
such as might be the case for a test router connected to a production network.
Use the on-startup keyword to set the overload bit when the router reboots and
to specify a period in seconds that IS-IS waits after the reboot before it clears
the overload bit.
Use the on-startup wait-for-bgp keywords to instruct IS-IS to set the overload
bit when the router reboots and then wait until BGP has completed convergence
after the reload before IS-IS clears the overload bit. You can specify a maximum
interval that IS-IS waits for BGP notification. When that interval passes, IS-IS
clears the overload bit. If you do not specify an interval, IS-IS waits a default 600
seconds and then clears the overload bit.
If you issue the on-startup keyword but do not issue the wait-for-bgp keyword,
then you must specify the number of seconds that IS-IS waits after a reload
before clearing the overload bit.
If you issue both the on-startup keyword and the wait-for-bgp keyword, you
cannot specify a time interval for on-startup but can optionally do so for
wait-for-bgp.
By default, the overload bit is not set.
Example 1
host1(config-router)#set-overload-bit
Example 2
host1(config-router)#set-overload-bit on-startup 900
Example 3
host1(config-router)#set-overload-bit on-startup wait-for-bgp 450
Use the no version to disable the setting.
See set-overload-bit
Use to enable your router to ignore rather than purge IS-IS LSPs that are received
with internal checksum errors.
Under normal conditions, the IS-IS protocol definition requires that received LSPs
with incorrect data link checksums are to be purged by the receiver. This causes
the LSP initiator to regenerate LSPs. If a network link causes data corruption
while still delivering LSPs with correct data link checksums, a continuous cycle
of regenerating and purging LSPs may result. This can render the network
nonfunctional. Enabling this command prevents this continuous cycle from
occurring because LSPs are ignored rather than purged.