Via interface” static route, Permanent static route, Via interface” static route permanent static route – Avaya X330WAN User Manual
Page 58: Ge 36
Chapter 4
Operational Concepts and Configuration Examples
36
Avaya X330WAN User’s Guide
For example:
To specify next-hops 149.49.54.1 and 149.49.75.1 as a static route to the
network 10.1.1.0, perform one of the following:
•
Use the single
ip route 10.1.1.0 24 149.49.54.1 149.49.75.1
command
specifying all next-hops together.
•
Use the individual
ip route 10.1.1.0 24 149.49.54.1
and
ip route
10.1.1.0 24 149.49.75.1
commands.
Note:
Next-hops can only be added to an existing static route if they have the same
preference and metric as the currently defined next-hops.
X330WAN supports the following Static Route configurations:
•
•
•
These configurations are described below.
“via interface” Static Route
PPP and Frame Relay allow for a Layer 3 interface to be established without
knowing in advance what the next-hop on the other side of a Serial link is. In this
case you can specify a Serial Layer 2 interface as a next-hop instead of providing a
specific next-hop IP address. This is equivalent to specifying the node on the other
side of the Serial link as the next-hop when its IP address is unknown. The “via
interface” option is configured by specifying the type and the number of the Serial
interface using the
ip route
command.
For example:
The command
ip route 193.168.10.0 24 serial 1:1
creates a
static route to the network 193.168.10.0 24 via the Serial 1:1 interface.
A static route can have both “via interface” and IP addressed next-hops, with a
maximum of three next-hops. If such a combination is required, separate
ip route
commands should be used for the “via interface” static route and the IP addressed
next-hop routes. Also, if more than one “via interface” next-hops are required, each
must be configured by separate
ip route
commands.
Permanent Static Route
X330WAN enables you to configure a static route as a permanent route.
Configuring this option prevents the static route from becoming inactive whenever
the underlying Layer 2 interface is down. This prevents routing table updates from
being sent each time an interface goes up or down when there is a fluctuating Layer
2 interface on the static route.
Configure the ‘permanent’ option using the
ip route
command.