Configuration Guide Vol. 3


30.2.3 RIPng advertised route filtering

<Structure of this section>

(1) Advertisement of specific protocol routes

Configure the advertisement of static routes and OSPFv3 domain 1 routes by RIPng.

Points to note

The example below shows how to use the redistribute command to advertise routes that would not be advertised by default. In the redistribute command, specify the protocols that you want advertised.

When configuring advertisement of OSPFv3 routes, you must also specify a metric. OSPFv3 and BGP4+ routes cannot be advertised without a metric.

Command examples

  1. (config)# ipv6 router rip

    (config-rtr-rip)# redistribute static

    Advertises static routes into RIPng.

  2. (config-rtr-rip)# redistribute ospf 1 metric 2

    Advertises OSPFv3 domain 1 routes, assigning them a metric of 2.

(2) Advertising Specific Destination Network Routes for Specific Protocols

Configure RIPng to advertise static routes, and only those OSPFv3 routes that have a destination network in the 3ffe:501:811:ff01::/64 range.

Points to note

To filter advertised routes based on their learning source protocol, specify route-map in the redistribute command. Use an ipv6 prefix-list filter to supply the destination network conditions for route-map.

First, configure an ipv6 prefix-list filter to permit only routes in the 3ffe:501:811:ff01::/64 range. Next, configure route-map to use this filter as filter conditions. Finally, use redistribute commands to specify static routes and OSPFv3 routes. In the redistribute command for the OSPFv3 routes, specify the route-map that you configured.

Command examples

  1. (config)# ipv6 prefix-list ONLY0811ff01 seq 10 permit 3ffe:501:811:ff01::/64

    Configures prefix-list to permit only routes in the 3ffe:501:811:ff01::/64 range. Because ONLY0811ff01 has no other conditions, the filter denies routes with any other destination address or mask length.

  2. (config)# route-map ONLY0811ff01 permit 10

    (config-route-map)# match ipv6 address prefix-list ONLY0811ff01

    (config-route-map)# exit

    Configures route-map to permit routes whose destination network is in the 3ffe:501:811:ff01::/64 range.

  3. (config)# ipv6 router rip

    (config-rtr-rip)# redistribute static

    Configures RIPng to advertise static routes.

  4. (config-rtr-rip)# redistribute ospf 1 metric 2 route-map ONLY0811ff01

    Configures RIPng to filter OSPFv3 domain 1 routes by ONLY0811ff01 and advertise permitted routes, assigning them a metric of 2.

(3) Suppressing advertisement of specific destination network routes

You can prevent RIPng from advertising routes destined for the 3ffe:501:811:ff01::/64 address range.

Points to note

The example below shows how to use the distribute-list out command to filter advertised routes regardless of their learning source protocol.

First, configure an ipv6 prefix-list filter to deny routes to the 3ffe:501:811:ff01::/64 address range. By referencing this filter from the distribute-list out command, you can configure RIPng to filter learned routes according to their destination network.

Command examples

  1. (config)# ipv6 prefix-list OMIT0811ff01 seq 10 deny 3ffe:501:811:ff01::/64

    Configures prefix-list to deny routes in the 3ffe:501:811:ff01::/64 range.

  2. (config)# ipv6 prefix-list OMIT0811ff01 seq 100 permit ::/0 ge 0 le 128

    Configures ipv6 prefix-list to permit routes with any destination address and mask length. Because OMIT0811ff01 has no other conditions, the filter denies routes to 3ffe:501:811:ff01::/64 only.

  3. (config)# ipv6 router rip

    (config-rtr-rip)# distribute-list prefix-list OMIT0811ff01 out

    Configures RIPng to apply the OMIT0811ff01 filter to every route it advertises.

(4) Filtering advertised routes for each advertised interface

Configure the switch to use RIPng interface VLAN 10 to advertise routes to 3ffe:501:811:ff01::/64, and RIPng interface VLAN 20 to advertise all other routes. In this scenario, no interface-level filtering is applied to the other RIPng interfaces.

Points to note

To apply route filtering at the level of individual RIPng interfaces, specify the <Interface> in the parameters of the distribute-list out command.

First, configure an ipv6 prefix-list filter to permit routes in the 3ffe:501:811:ff01::/64 range and another to permit any route not in the 3ffe:501:811:ff01::/64 range. Next, specify the distribute-list out <Interface> command for RIPng interfaces VLAN 10 and VLAN 20. In the distribute-list out <Interface> command, specify the prefix-list filter appropriate to that RIPng interface.

Command examples

  1. (config)# ipv6 prefix-list ONLY0811ff01 seq 10 permit 3ffe:501:811:ff01::/64

    Configures prefix-list to permit only routes in the 3ffe:501:811:ff01::/64 range. Because ONLY0811ff01 has no other conditions, the filter denies routes with any other destination address or mask length.

  2. (config)# ipv6 prefix-list OMIT0811ff01 seq 10 deny 3ffe:501:811:ff01::/64

    Configures prefix-list to deny routes in the 3ffe:501:811:ff01::/64 range.

  3. (config)# ipv6 prefix-list OMIT0811ff01 seq 100 permit ::/0 ge 0 le 128

    Configures prefix-list to permit routes with any destination address and mask length. Because OMIT0811ff01 has no other conditions, the filter denies routes to 3ffe:501:811:ff01::/64 only.

  4. (config)# ipv6 router rip

    (config-rtr-rip)# distribute-list prefix-list ONLY0811ff01 out vlan 10

    Configures RIPng to apply criterion ONLY0811ff01 to routes advertised from VLAN 10.

  5. (config-rtr-rip)# distribute-list prefix-list OMIT0811ff01 out vlan 20

    Configures RIPng to apply criterion OMIT0811ff01 to routes advertised from VLAN 20.

(5) Controlling advertised routes by tag value

Configure the switch to assign a tag value of 210 to any directly connected routes it advertises and advertise static routes only if they have a tag value of 211. You then configure the switch to not advertise routes that have a tag value of 210 or 211 by RIPng. This process prevents RIPng-advertised routes from looping through the Switch.

Points to note

The example below shows how to use route-map to filter a route by an attribute other than its destination network, or you wish to change a route attribute other than the metric. You can reference this route-map from redistribute and distribute-list out among other commands.

The commands below configure route-map to set the tag value of directly connected routes to 210, route-map to permit static routes with a tag value of 211, and route-map to deny RIPng routes with tag values of 210 or 211.

Command examples

  1. (config)# route-map ConnectedToRIPng permit 10

    (config-route-map)# set tag 210

    (config-route-map)# exit

    Configures route-map to assign a tag value of 210.

  2. (config)# route-map StaticToRIPng permit 10

    (config-route-map)# match tag 211

    (config-route-map)# exit

    Configures route-map to permit routes with a tag value of 211.

  3. (config)# route-map RIPngToRIPng deny 10

    (config-route-map)# match tag 210 211

    (config-route-map)# exit

    (config)# route-map RIPngToRIPng permit 20

    (config-route-map)# exit

    Configures route-map to deny routes with a tag value of 210 or 211 while permitting all others.

  4. (config)# ipv6 router rip

    (config-rtr-rip)# redistribute connected route-map ConnectedToRIPng

    Advertises direct routes into RIPng. Specify ConnectedToRIPng as the advertising conditions.

  5. (config-rtr-rip)# redistribute static route-map StaticToRIPng

    Advertises static routes into RIPng. Specify StaticToRIPng as the advertising conditions.

  6. (config-rtr-rip)# redistribute rip route-map RIPngToRIPng

    Advertises RIPng routes to RIPng. Specify RIPngToRIPng as the advertising conditions.