Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation

Example: Disabling Strict LSA Checking for OSPF Graceful Restart

This example shows how to disable strict link-state advertisement (LSA) checking for OSPF graceful restart.

Requirements

Before you begin:

Overview

You can disable strict LSA checking to prevent the termination of graceful restart by a helping router. You might configure this option for interoperability with other vendor devices. The OSPF graceful restart helper capability must be enabled if you disable strict LSA checking. By default, LSA checking is enabled.

In this example, interfaces fe-1/1/1 and fe-1/1/2 are in OSPF area 0.0.0.0, and you configure those interfaces for graceful restart. You then disable strict LSA checking by including the no-strict-lsa-checking statement.

Note: The helper-disable statement and the no-strict-lsa-checking statement cannot be configured at the same time. If you attempt to configure both statements at the same time, the routing device displays a warning message when you enter the show protocols ospf command.

Configuration

CLI Quick Configuration

To quickly enable graceful restart for OSPF with strict LSA checking disabled, copy the following commands and paste them into the CLI.

[edit] set interfaces fe-1/1/1 unit 0 family inet address 10.0.0.4set interfaces fe-1/1/2 unit 0 family inet address 10.0.0.5set protocols ospf area 0.0.0.0 interface fe-1/1/1set protocols ospf area 0.0.0.0 interface fe-1/1/2set protocols ospf graceful-restart no-strict-lsa-checking

Step-by-Step Procedure

To enable graceful restart for OSPF with strict LSA checking disabled:

  1. Configure the interfaces.

    Note: For OSPFv3, use IPv6 addresses.

    [edit]user@host# set interfaces fe-1/1/1 unit 0 family inet address 10.0.0.4user@host# set interfaces fe-1/1/1 unit 0 family inet address 10.0.0.5
  2. Configure OSPF on the interfaces

    Note: To specify OSPFv3, include the ospf3 statement at the [edit protocols] hierarchy level.

    [edit]user@host# set protocols ospf area 0.0.0.0 interface fe-1/1/1user@host# set protocols ospf area 0.0.0.0 interface fe-1/1/2
  3. Disable strict LSA checking.
    If you disable the strict LSA checking, OSPF graceful restart helper capability must be enabled (which is the default behavior).
    [edit]user@host# set protocols ospf graceful-restart no-strict-lsa-checking
  4. If you are done configuring the device, commit the configuration.
    [edit ]user@host# commit

Results

Confirm your configuration by entering the show interfaces and the show protocols ospf commands. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

user@host# show interfaces
fe-1/1/1 {unit 0 {family inet {address 10.0.0.4/32;}}}
fe-1/1/2 {unit 0 {family inet {address 10.0.0.5/32;}}}
user@host# show protocols ospf
graceful-restart {no-strict-lsa-checking;}
area 0.0.0.0 {interface fe-1/1/1.0;interface fe-1/1/2.0;}

To confirm your OSPFv3 configuration, enter the show interfaces and the show protocols ospf3 commands.

Verification

Confirm that the configuration is working properly.

Verifying the OSPF Graceful Restart Configuration

Purpose

Verify information about your OSPF graceful restart configuration. The Restart field displays the status of graceful restart as either enabled or disabled.

Action

From operational mode, enter the show ospf overview command for OSPFv2, and enter the show ospf3 overview command for OSPFv3.

Verifying Graceful Restart Status

Purpose

Verify the status of graceful restart. The Restart State field displays Pending if the restart has not completed, or Complete if the restart has finished. The Path selection timeout field indicates the amount of time remaining until graceful restart is declared complete. There is a more detailed Restart State field that displays a list of protocols that have completed graceful restart or have not yet completed graceful restart for the specified routing table.

Action

From operational mode, enter the show route instance detail command.

Published: 2013-08-15