Dell PowerConnect B-RX Configuration Manual page 274

7
Configuring forwarding parameters
To add a tag value to a static route, enter commands such as the following:
BigIron RX(config)#ip route 192.122.12.1 255.255.255.0 192.122.1.1 tag 20
Syntax: ip route <dest-ip-addr> <dest-mask> | <dest-ip-addr>/<dest-mask>
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
192.0.0.0 255.255.255.0 as 192.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.
Configuring load balancing and redundancy using multiple static
routes to the same destination
You can configure multiple static IP routes to the same destination, for the following benefits:
•
•
NOTE
You also can bias the device to select one of the routes by configuring them with different
administrative distances. However, make sure you do not give a static route a higher administrative
distance than other types of routes, unless you want those other types to be preferred over the static
route. For a list of the default administrative distances, refer to
on page 757.
The steps for configuring the static routes are the same as described in the previous section. The
following sections provide examples.
To configure multiple static IP routes, enter commands such as the following.
BigIron RX(config)# ip route 192.128.2.69 255.255.255.0 209.157.22.1
BigIron RX(config)# ip route 192.128.2.69 255.255.255.0 192.111.10.1
The commands in the example above configure two static IP routes. The routes go to different
next-hop gateways but have the same metrics. These commands use the default metric value (1),
so the metric is not specified. These static routes are used for load sharing among the next-hop
gateways.
202
<next-hop-ip-address> tag <value>
IP load sharing – If you configure more than one static route to the same destination, and the
routes have different next-hop gateways but have the same metrics, the device load balances
among the routes using basic round-robin. For example, if you configure two static routes with
the same metrics but to different gateways, the device alternates between the two routes. For
information about IP load balancing, refer to
Backup Routes – If you configure multiple static IP routes to the same destination, but give the
routes different next-hop gateways and different metrics, the device will always use the route
with the lowest metric. If this route becomes unavailable, the device will fail over to the static
route with the next-lowest metric, and so on.
"Configuring IP load sharing"
"Changing administrative distances"
BigIron RX Series Configuration Guide
on page 207.
53-1001986-01