Ospf; Static Routes - Avaya P333R-LB User Manual

Chapter 1 Overview
Configuration of the RIP version, 1 or 2, is per IP interface (default is version 1).
Configuration should be homogenous on all routers on each subnet, i.e. there
should not be both RIPv1 and RIPv2 routers on the same subnet. However, different
IP interfaces of the P333R-LB can be configured with different RIP versions (as long
as all routers on the subnet are configured to the same version).
RIPv2 and RIPv1 are considered the same protocol with regard to redistribution to/
from OSPF and static route preferences.

OSPF

P333R-LB supports the OSPF routing protocol. P333R-LB can be configured as an
OSPF Autonomous System Boundary Router (ASBR) by configuration of route
redistribution. P333R-LB can be installed in the OSPF backbone area (area 0.0.0.0) or
in any OSPF area that is part of a multiple areas network. However, P333R-LB
cannot be configured to be an OSPF area border router itself.
The P333R-LB supports the equal-cost multipath (ECMP) feature which allows load
balancing by splitting traffic between several equivalent paths.
While OSPF can be activated with default values for each interface using a single
command, many of the OSPF parameters are configurable.
For a detailed description of OSPF, refer to the OSPF standards and published
literature.

Static Routes

Static routes can be configured to the P333R-LB. They are never timed-out, or lost
over reboot, and can only be removed by manual configuration. Deletion (by
configuration) of the IP interface deletes the static routes using this interface as well.
A static route becomes inactive if the interface over which it is defined is disabled.
When the interface is enabled, the static route becomes active again.
Static routes can only be configured for remote destinations, i.e. destinations that
are reachable via another router as a next hop. The next hop router must belong to
one of the directly attached networks for which P333R-LB has an IP interface.
"Local" static routes, such as those that have no next hop, are not allowed.
Two kinds of static routes can be configured, High Preference static routes which are
preferred to routes learned from any routing protocol and Low Preference static
routes which are used temporarily until the route is learned from a routing protocol.
By default, a static route has Low Preference.
Static routes can be advertised by routing protocols (i.e. RIP, OSPF) as described
under Route redistribution.
Static routes also support load-balancing similar to OSPF. A static route can be
configured with multiple next hops so that traffic is split between these next hops.
8 Avaya P333R-LB User's Guide