[an error occurred while processing this directive][an error occurred while processing this directive]

Configuring OSPF Database Protection

By configuring OSPF database protection, you can help prevent your OSPF link-state database from being overrun with excessive LSAs that are not generated by the local router. You specify the maximum number of LSAs whose advertising router ID is not the same as the local router ID in an OSPF instance. This feature is particularly useful if your provider edge and customer edge routers are configured with VPN routing and forwarding using OSPF.

OSPF database protection is supported on the following:

  • Logical systems
  • All routing instances supported by OSPFv2 and OSPFv3
  • OSPFv2 and OSPFv3 topologies
  • OSPFv3 realms

To configure OSPF database protection:

  1. Include the database-protection statement at one of the following hierarchy levels:
    • [edit protocols ospf | ospf3]
    • [edit logical-systems logical-system-name routing-instances routing-instance-name protocols (ospf |ospf3)]
    • [edit routing-instances routing-instance-name protocols (ospf |ospf3)]
    • [edit routing-instances routing-instance-name protocols ospf3 realm (ipv4–unicast | ipv4–multicast | ipv6–unicast | ipv6–multicast)]
  2. Include the maximum-lsa number statement.

    Note: The maximum-lsa statement is mandatory, and there is no default value for it. If you omit this statement, you cannot configure OSPF database protection.

  3. (Optional) Include the following statements:
    • ignore-count number—Specify the number of times the database can enter the ignore state before it goes into the isolate state.
    • ignore-time seconds—Specify the time limit the database must remain in the ignore state before it resumes regular operations.
    • reset-time seconds—Specify the time during which the database must operate without being in either the ignore or isolate state before it is reset to a normal operating state.
    • warning-threshold percent—Specify the percent of the maximum LSA number that must be exceeded before a warning message is issued.

    Note: If you configure the warning-only statement, values for the optional statements above will not be used when the maximum LSA number is exceeded.

  4. (Optional) Include the warning-only statement to prevent the database from entering the ignore state or isolate state when the maximum LSA count is exceeded.

Published: 2010-04-14

[an error occurred while processing this directive]