Static routes can be configured with a tag value, which can be used to color routes and filter routes
during a redistribution process. When tagged static routes are redistributed to OSPF or to a protocol
that can carry tag information, they are redistributed with their tag values.

To add a tag value to a static route, enter commands such as the following.

Brocade(config)# ip route 10.122.12.1 255.255.255.0 10.122.1.1 tag 20

Syntax: [no] ip route dest-ip-addr dest-mask | dest-ip-addr/dest-mask next-hop-ip-address tag

value

The dest-ip-addr is the route’s destination. The dest-mask is the network mask for the route’s
destination IP address. Alternatively, you can specify the network mask information by entering a
forward slash followed by the number of bits in the network mask. For example, you can enter
10.0.0.0 255.255.255.0 as 10.0.0.0/.24. You can enter multiple static routes for the same
destination for load balancing or redundancy.

The next-hop-ip-address is the IP address of the next-hop router (gateway) for the route. In addition,
the next-hop-ip-address can also be a virtual routing interface (for example. ve 100), or a physical
port (for example, ethernet 1/1) that is connected to the next-hop router.

Enter 0 – 4294967295 for tag value. The default is 0, meaning no tag.

Static route next hop resolution

This feature of the Multi-Service IronWare software enables the Brocade device to use routes from
a specified protocol to resolve a configured static route. By default this is disabled.

To configure static route next hop resolution with OSPF routes, use the following command.

Brocade(config)# ip route next-hop ospf

Syntax: [no] ip route next-hop [bgp | isis | ospf | rip ]

NOTE

This command can be independently applied on a per-VRF basis.

This command causes the resolution of static route next hop using routes learned from one of the
following protocols:

•

bgp – both iBGP and eBGP routes are used to resolve static routes.

•

isis

Advertising