Via-Interface Static Route - Avaya G250 Administration

Using the no ip route command deletes the route including all of its next-hops, whether
entered individually or with a single command. 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,
Or
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.
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.
Note:
Metrics are used to choose between routes of the same protocol. Preferences
Note:
are used to choose between routes of different protocols.
The Avaya G250/G350 Media Gateway supports the following Static Route configurations:

Via-interface static route

●
Permanent static route
●
Discard route
●
Via-interface static route
PPP and frame relay allow for a Layer 3 interface to be established without knowing in advance
the next-hop on the other side of a serial link. In this case you can specify a Serial Layer 2
interface or a GRE tunnel 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.
Note:
The interface used in the via route must have an IP address attached to it.
Note:
For example, the command ip route 193.168.10.0 24 serial 2/1:1 creates a static
route to the network 193.168.10.0 24 via the Serial 2/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.
Configuring the routing table
Issue 1.1 June 2005 319