Rip; Ospf; Static Routes - Avaya P334T-ML User Manual

RIP

P334T-ML supports the widely used RIP routing protocol (both RIPv1 and RIPv2).
The RIPv1 protocol imposes some limitations on the network design with regard to
subnetting. When operating RIPv1, you must not configure variable length subnet
masks (VLMS). Each IP network must have a single mask, implying that all subnets
in a given IP network are of the same size. Also, when operating RIPv1, you must
not configure supernets, which are networks with a mask smaller than the natural
net mask of the address class, such as 192.1.0.0 with mask 255.255.0.0 (smaller than
the natural class C mask which is 255.255.255.0). For detailed descriptions of RIP
refer to the standards and published literature.
RIPv2 is a new version of the RIP routing protocol, not yet widely used but with
some advantages over RIPv1. RIPv2 solves some of the problems associated with
RIPv1. The most important change in RIPv2 is the addition of a subnet mask field
which allows RIPv2 to support variable length subnets. RIPv2 also includes an
authentication mechanism similar to the one used in OSPF.
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 P334T-ML 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

P334T-ML supports the OSPF routing protocol. P334T-ML can be configured as an
OSPF Autonomous System Boundary Router (ASBR) by configuration of route
redistribution. P334T-ML 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, P334T-ML
cannot be configured to be an OSPF area border router itself.
The P334T-ML 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 P334T-ML. 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.
P334T-ML User's Guide
Chapter 1 Overview
11