Brocade Virtual ADX Switch and Router Guide (Supporting ADX v03.1.00) - Manual (Page 83)

Brocade Virtual ADX Switch and Router Guide 69
53-1003246-01
Configuring IP parameters
4
• The route’s administrative distance – The value that the Virtual ADX uses to compare this route
with routes from other route sources to the same destination before placing a route in the IP
route table. This parameter does not apply to routes that are already in the IP route table. The
default administrative distance for static IP routes is 1.
The default metric and administrative distance values ensure that the Virtual ADX always prefers
static IP routes over routes from other sources to the same destination.
Multiple static routes to the same destination provide load sharing and
redundancy
You can add multiple static routes for the same destination network to provide one or more of the
following benefits:
• IP load balancing – When you add multiple IP static routes for the same destination to different
next-hop gateways, and the routes each have the same metric and administrative distance, the
Virtual ADX can load balance traffic to the routes’ destination. For information about IP load
balancing, refer to
“Configuring IP load sharing” on page 77.
• Path redundancy – When you add multiple static IP routes for the same destination, but give
the routes different metrics or administrative distances, the Virtual ADX uses the route with the
lowest administrative distance by default, but uses another route to the same destination of
the first route becomes unavailable.
Refer to the following sections for examples and configuration information:
• “Configuring load balancing and redundancy using multiple static routes to the same
destination”
on page 72
• “Configuring standard static IP routes and interface or null static routes to the same
destination”
on page 73
Static route states follow port states
IP static routes remain in the IP route table only so long as the port or virtual interface used by the
route is available. If the port or virtual routing interface becomes unavailable, the software removes
the static route from the IP route table. If the port or virtual routing interface becomes available
again later, the software adds the route back to the route table.
This feature allows the Virtual ADX to adjust to changes in network topology. The Virtual ADX does
not continue trying to use routes on unavailable paths but instead uses routes only when their
paths are available.
Figure 15 shows an example of a network containing a static route. The static route is configured
on Router A, as shown in the CLI example following the figure.
FIGURE 15 Example of a static route
The following command configures a static route to 10.95.7.0, using 10.95.6.157 as the next-hop
gateway.
Virtual ADX(config)# ip route 10.95.7.0/24 10.95.6.157