Brocade FastIron Ethernet Switch Layer 3 Routing Configuration Guide - Manual (Page 237)

Changing the metric of routes learned and advertised on an interface
A device interface increases the metric of an incoming RIPng route it learns by an offset (the default is
one). The device then places the route in the route table. When the device sends an update, it
advertises the route with the metric plus the default offset of zero in an outgoing update message.
You can change the metric offset an individual interface adds to a route learned by the interface or
advertised by the interface. For example, to change the metric offset for incoming routes learned by
Ethernet interface 3/1 to one and the metric offset for outgoing routes advertised by the interface to
three, enter the following commands.
device(config)# interface ethernet 3/1
device(config-if-e100-3/1)# ipv6 rip metric-offset 2
device(config-if-e100-3/1)# ipv6 rip metric-offset out 3
In this example, if Ethernet interface 3/1 learns about an incoming route, it will increase the incoming
metric by two. if the interface 3/1 advertises an outgoing route, it will increase the metric offset by 3 as
specified in the example. Configuring the default metric (1 for incoming, 0 for outgoing) will be allowed
but will not be visible in the show run output for the interface.
Syntax: [no] ipv6 rip metric-offset 1-16
Syntax: [no] ipv6 rip metric-offset out 0-15
To return the metric offset to its default value, use the no form of this command.
Redistributing routes into RIPng
You can configure the Brocade device to redistribute routes from the following sources into RIPng:
• IPv6 static routes
• Directly connected IPv6 networks
• BGP4+
• OSPFv3
When you redistribute a route from BGP4+ or OSPFv3 into RIPng, the device can use RIPng to
advertise the route to its RIPng neighbors.
When configuring the Brocade device to redistribute routes, such as BGP4+ routes, you can optionally
specify a metric for the redistributed routes. If you do not explicitly configure a metric, the default metric
value of one is used.
For example, to redistribute OSPFv3 routes into RIPng, enter the following command.
device(config)# ipv6 router rip
device(config-ripng-router)# redistribute ospf
Syntax: [no] redistribute{ bgp | connected | ospf | static [ metric number ] }
For the metric, specify a numerical value that is consistent with RIPng.
Controlling distribution of routes through RIPng
You can create a prefix list and then apply it to RIPng routing updates that are received or sent on a
device interface. Performing this task allows you to control the distribution of routes through RIPng.
For example, to permit the inclusion of routes with the prefix 2001:db8::/32 in RIPng routing updates
sent from Ethernet interface 3/1, enter the following commands.
device(config)# ipv6 prefix-list routesfor2001 permit 2001:db8::/32
Changing the metric of routes learned and advertised on an interface
FastIron Ethernet Switch Layer 3 Routing Configuration Guide 237
53-1003087-04