Use the IPv6_AREA statement to set the parameters for an IPv6 OSPF area. If no areas are defined, OMPROUTE assumes that all the router's directly attached networks belong to the backbone area (area ID 0.0.0.0).
Syntax
>>-IPv6_Area--Area_Number--=--ospf_area_address-----------------> .-Stub_Area=NO--------. .-Stub_Default_Cost=1--------. >--+---------------------+--+----------------------------+------> '-Stub_Area--=--value-' '-Stub_Default_Cost--=--cost-' .-Import_Prefixes=YES-------. >--+---------------------------+------------------------------->< '-Import_Prefixes--=--value-'
Parameters
- Area_Number
- The 32–bit OSPF area number in dotted decimal.
- Stub_Area
- Specifies
whether this area is a stub area or not. Valid values are YES or NO.
Restrictions: 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. The following restrictions apply:
- 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 area border router attaching to a stub area originates a default route for this purpose. The cost of this default route is also configurable with the IPv6_AREA statement.
- Stub_Default_Cost
- The cost that an OMPROUTE area border router associates with the default route that it generates into the stub area. Valid values are in the range 1 - 16 777 215.
- Import_Prefixes
- If this area is a stub area, indicates whether prefixes from
neighboring areas are imported. Valid values are YES or NO.
Tip: A stub area with Import_Prefixes set to NO is commonly referred to in RFCs and other standards documentation as a Totally Stubby Area.