
Customizing OSPF Services
308627-14.20 Rev 00
6-9
Figure 6-1. OSPF ASE Routes
By default, an OSPF boundary router generates a type 2 metric for BGP, EGP, and
RIP routes. For local networks not configured with a routing protocol and for
static routes, the boundary router generates a type 1 metric with a value equal to
the route’s cost in the routing table.
By default, ASE metric support is disabled. This means that the lower 17 bits of
the route weight are used for non-BGP originated routes and a value of 1 is used
for BGP originated routes. If ASE metric support is enabled, the metric value
advertised for a non-OSPF originated route being imported into the OSPF domain
consists of the lower 24 bits of the route weight from that route. For more
information about route weights, see “Route Weights” on page 1-22.
Note:
All routers advertising a particular route metric value must use the same
metric type — type 1 or type 2. If not, the router that receives the
advertisements may choose the wrong route.
BGP route to
destination X
BGP route to
destination X
OSPF AS
ASE routes
Boundary
router B
Internal
router
Boundary
router A
IP0019A
Commentaires sur ces manuels