Owner's Manual

548
Area
If you select the Area option, the remainder of the screen has these fields (rather than those in
Export Policies or Interface):
Figure 13-102. Routing Instances -> VRF Instances - OSPF and OSPF3 (Area)
- Area ID —Specify the area identifier for this router to use when participating in OSPF routing.
All routers in an area must use the same area identifier to establish adjacencies.
Specify multiple area statements to configure the router as an area border router. An area
border router does not automatically summarize routes between areas; use the area-range
statement to configure route summarization. By definition, an area border router must be
connected to the backbone area through either a physical or virtual link.
To specify that the router is directly connected to the OSPF and OSPFv3 backbone, include
the area 0.0.0.0 statement.
-
Area Type —Select NSSA or Stub as the area type.
An
NSSA area allows external routes to be flooded within the area. These routes are then
leaked into other areas.
Select
Stub to indicate that this area should not be flooded with AS external link-state
advertisements. You must include the stub statement when configuring all routers that are in
the stub area. The backbone cannot be configured as a stub area.
NOTE:
You cannot configure an area as being both a stub area and an NSSA.
- Metric Type —External metric type for the default LSA. Select 1 or 2 . Enabled for Area Type
NSSA only.
-
Default Metric —On area border routers only, for a stub area, inject a default route with a
specified metric value into the area. The default route matches any destination not explicitly
reachable from within the area.