Setting the next hop – Brocade Multi-Service IronWare Routing Configuration Guide (Supporting R05.6.00) User Manual

Page 790

Advertising
background image

762

Multi-Service IronWare Routing Configuration Guide

53-1003033-02

Configuring an IPv6 PBR policy

Syntax: [no] route-map map-name permit | deny num

The map-name variable is a string of characters that names the map. Map names can be up to 80
characters in length. You can define an unlimited number of route maps on the Brocade device, as
long as system memory is available.

The permit | deny parameter specifies the action the Brocade device will take if a route matches a
match statement:

If you specify a deny route map instance, it is ignored and not programmed in Layer 4 CAM.

If you specify permit, the Brocade device applies the match and set statements associated
with this route map instance.

The num parameter specifies the instance of the route map you are defining. Routes are compared
to the instances in ascending numerical order. For example, a route is compared to instance 1,
then instance 2, and so on.

IPv6 PBR uses up to 64 route map instances for comparison and ignores the rest.

Syntax: [no] match ipv6 address [ipv6_access_list_name]

The ipv6_access_list_name parameter specifies a IPv6 ACL name. Up to five ACL names can be
configured in one match statement.

To add IPv6 ACLs to the existing match command, enter the entire command line, including the old
IPv6 ACL names. For example, if you want to add v6_acl2, to the previous example, you need to
enter the complete command line, as follows:

Brocade(config-routemap v6pbr)# match ipv6 address v6_acl1 v6_acl2

Setting the next hop

Traffic that matches a match statement in the route map is forwarded as defined by set
commands. Multiple set commands can be configured and when a match condition is met, the
device works sequentially through the list of set commands until it finds the first next hop that is
operational and uses it. If that next hop goes down, the next hop as defined in a set command is
chosen and if all next hop interfaces in the list are down, the packet is routed as determined in the
IP Route Table. If a next hop interface that was down comes back up, the next hop selection
process begins again and restarts its selection process from the top of the list.

Options for setting the next hop are described in the following sections:

“Setting the next hop to an IPv6 address”

on page 762

“Setting the next hop to a Null0 interface”

on page 763

“Setting next hop VLAN flooding”

on page 763

Setting the next hop to an IPv6 address
You can set the next hop to an IPv6 address as shown in the following example.

Brocade(config)#route-map v6pbr permit 10

Brocade(config-routemap v6pbr)#match ipv6 address v6acl

Brocade(config-routemap v6pbr)#set ipv6 next-hop 2001:db8::1

Syntax: [no] set ipv6 next-hop ipv6-address

The ipv6-address variable specifies the IPv6 address to which the packets will be sent.

Advertising