RFC 1765 (rfc1765) - Page 2 of 9


OSPF Database Overflow



Alternative Format: Original Text Document



RFC 1765                 OSPF Database Overflow               March 1995


1.  Overview

   OSPF requires that all OSPF routers within a single area maintain an
   identical copy of the OSPF link-state database.  However, when the
   size of the link-state database becomes very large, some routers may
   be unable to keep the entire database due to resource shortages; we
   term this "database overflow". For example, a regional network may
   have a very large OSPF database because it is importing a large
   number of external routes into OSPF. Unless database overflow is
   handled correctly, routers will end up with inconsistent views of the
   network, possibly leading to incorrect routing.

   One way of handling database overflow is to encase routers having
   limited resources within OSPF stub areas (see Section 3.6 of [1]) or
   NSSAs ([2]).  AS-external-LSAs are omitted from these areas' link-
   state databases, thereby controlling database size.

   However, unexpected database overflows cannot be handled in the above
   manner.  This memo describes a way of dynamically limiting database
   size under overflow conditions. The basic mechanism is as follows:

    (1) A parameter, ospfExtLsdbLimit, is configured in each router
        indicating the maximum number of AS-external-LSAs (excluding
        those describing the default route) that are allowed in the
        link-state database. This parameter must be the same in all
        routers in the routing domain (see Section 2.1); synchronization
        of the parameter is achieved via network management.

    (2) In any router's database, the number of AS-external-LSAs
        (excluding default) is never allowed to exceed ospfExtLsdbLimit.
        If a router receives a non-default AS-external-LSA that would
        cause the limit of ospfExtLsdbLimit to be exceeded, it drops the
        LSA and does NOT acknowledge it.

    (3) If the number of non-default AS-external-LSAs in a router's
        database hits ospfExtLsdbLimit, the router a) flushes all non-
        default AS-external-LSAs that it has itself originated (see
        Section 2.2) and b) goes into "OverflowState".

    (4) While in OverflowState, the router refuses to originate any
        non-default AS-external-LSAs (see Section 2.3.2).

    (5) Optionally, the router can attempt to leave OverflowState after
        the configurable parameter ospfExitOverflowInterval has elapsed
        since entering OverflowState (see Section 2.4). Only at this
        point can the router resume originating non-default AS-
        external-LSAs.




Moy