Brocade BigIron RX Series Configuration Guide - Manual (Page 1305)

BigIron RX Series Configuration Guide 1227
53-1002484-04
Configuring BGP4+
46
• OSPFv3.
• RIPng.
You can redistribute routes in the following ways:
• By route types, for example, the switch redistributes all IPv6 static and RIPng routes.
• By using a route map to filter which routes to redistribute, for example, the switch redistributes
specified IPv6 static and RIPng routes only.
For example, to configure the redistribution of all RIPng routes into the BGP4+ unicast database,
enter the following commands at the BGP4+ address family configuration level:
BigIron RX(config-bgp-ipv6u)# redistribute rip
Syntax: redistribute <protocol> [level-1 | level-1-2 | level-2] [match external1 | external2 |
internal] [metric <metric-value>] [route-map <name>]
The <protocol> parameter can be connected, isis, ospf, rip, or static.
If you specify isis as the protocol, you can optionally specify the redistribution of level 1, level 1 and
2, or level 2 routes.
If you specify ospf as the protocol, you can optionally specify the redistribution of external 1,
external 2, or internal routes. (The default is internal.)
The metric <metric-value> parameter specifies the metric used for the redistributed route. If a
value is not specified for this option, and no value is specified using the default-metric command at
the BGP4+ unicast address family configuration level, the metric value for the IPv6 static, RIPng, or
IPv6 OSPF route is used. Use a value consistent with the destination protocol.
The <name> parameter specifies a route map name.
Aggregating routes advertised to BGP4 neighbors
By default, a switch advertises individual BGP4+ routes for all the networks. The aggregation
feature allows you to configure a switch to aggregate routes in a range of networks into a single
IPv6 prefix. For example, without aggregation, a switch will individually advertise routes for
networks ff00:f000:0001:0000::/64, ff00:f000:0002:0000::/64,ff00:f000:0003:0000::/64, and
so on. You can configure the switch to instead send a single, aggregate route for the networks. The
aggregate route would be advertised as ff00:f000::/24 to BGP4 neighbors.
To aggregate BGP4+ routes for ff00:f000:0001:0000::/64,
ff00:f000:0002:0000::/64,ff00:f000:0003:0000::/64, enter the following command.
BigIron RX(config-bgp)# aggregate-address ff00:f000::/24 summary-only
Syntax: aggregate-address <ipv6-prefix>/<prefix-length> [as-set] [summary-only] [suppress-map
<map-name>] [advertise-map <map-name>] [attribute-map <map-name>]
The <ipv6-prefix>/<prefix-length> parameter specifies the aggregate value for the networks. You
must specify the <ipv6-prefix> parameter in hexadecimal using 16-bit values between colons as
documented in RFC 2373. You must specify the <prefix-length> parameter as a decimal value. A
slash mark (/) must follow the <ipv6-prefix> parameter and precede the <prefix-length> parameter.
The as-set keyword causes the switch to aggregate AS-path information for all the routes in the
aggregate address into a single AS-path.
The summary-only keyword prevents the switch from advertising more specific routes contained
within the aggregate route.