Use the AREA statement to set the parameters for an OSPF area. If no areas are defined, OMPROUTE assumes that all directly attached networks belong to the backbone area (area ID 0.0.0.0).
.-Area_Number=0.0.0.0---------------. >>-Area--+-----------------------------------+------------------> '-Area_Number--=--ospf_area_address-' .-Authentication_Type=None----------------. >--+-----------------------------------------+------------------> '-Authentication_Type--=--security_scheme-' .-Stub_Area=NO--------. .-Stub_Default_Cost=1--------. >--+---------------------+--+----------------------------+------> '-Stub_Area--=--value-' '-Stub_Default_Cost--=--cost-' .-Import_Summaries=YES-------. >--+----------------------------+------------------------------>< '-Import_Summaries--=--value-'
If you specify Stub_area = YES, the area does not receive any AS external link advertisements, reducing the size of your database and decreasing memory usage for routers in the stub area. You cannot configure virtual links through a stub area. You cannot configure a router within the stub area as an AS boundary router.
You cannot configure the backbone as a stub area. External routing in stub areas is based on a default route. Each border area router attaching to a stub area originates a default route for this purpose. The cost of this default route is also configurable with the AREA statement.