Modifying metric type for routes redistributed, Into ospf version 3, Configuring external route summarization – Brocade Multi-Service IronWare Routing Configuration Guide (Supporting R05.6.00) User Manual

Page 676

Advertising
background image

648

Multi-Service IronWare Routing Configuration Guide

53-1003033-02

Configuring OSPFv3

To restore the default metric to the default value, use the no form of this command.

Modifying metric type for routes redistributed into OSPF Version 3

The device uses the metric-type parameter by default for all routes redistributed into OSPFv3
unless you specify a different metric type for individual routes using the redistribute command. (For
more information about using the redistribute command, refer to

“Redistributing routes into

OSPFv3”

on page 645.)

A type 1 route specifies a small metric (two bytes), while a type 2 route specifies a big metric (three
bytes). The default value is type 2.

To modify the default value of type 2 to type 1, enter the following command.

Brocade(config-ospf6-router)# metric-type type1

Syntax: [no] metric-type type1 | type2

To restore the metric type to the default value, use the no form of this command.

Configuring external route summarization

When the device is an OSPF Autonomous System Boundary Router (ASBR), you can configure it to
advertise one external route as an aggregate for all redistributed routes that are covered by a
specified IPv6 address range.

When you configure an address range, the range takes effect immediately. All the imported routes
are summarized according to the configured address range. Imported routes that have already
been advertised and that fall within the range are flushed out of the AS and a single route
corresponding to the range is advertised.

If a route that falls within a configured address range is imported by the device, no action is taken if
the device has already advertised the aggregate route; otherwise, the device advertises the
aggregate route. If an imported route that falls within a configured address range is removed by the
device, no action is taken if there are other imported routes that fall with in the same address
range; otherwise the aggregate route is flushed.

You can configure up to 32 address ranges. The device sets the forwarding address of the
aggregate route to zero and sets the tag to zero.

If you delete an address range, the advertised aggregate route is flushed and all imported routes
that fall within the range are advertised individually.

If an external link state database overflow (LSDB) condition occurs, all aggregate routes are flushed
out of the AS, along with other external routes. When the device exits the external LSDB overflow
condition, all the imported routes are summarized according to the configured address ranges.

NOTE

If you use redistribution filters in addition to address ranges, the device applies the redistribution
filters to routes first, then applies them to the address ranges.

NOTE

If you disable redistribution, all the aggregate routes are flushed, along with other imported routes.

Advertising