Enterasys Networks X-PeditionTM manual RIPv1

IP Routing Protocols

•Static routes

•Route redistribution

•Default network

•CIDR (classless IP)

•Configurable Router ID

•Route Preference

When you run multiple routing protocols, the XSR assigns a weight to each of them. For more information, refer to “Route Preference” on page 5-17.

RIPv1 and v2

The Routing Information Protocol (RIP) is a distance-vector protocol based on the Bellman-Ford algorithm to learn the shortest path between two points in a network. RIP is used only on networks whose longest path is 15 hops or less and is marked by the following limits on the XSR:

•MD5 authentication is not supported

•Distribution lists require an ACL to be configured

RIP uses request and response messages. Requests ask for all or part of routing table entries and responses can be sent for one of these reasons:

•Response to a specific query

•Regular updates (unsolicited response)

•Triggered updates caused by a route change

RIP specifications are RFC-1058 for RIPv1 and RFC-2453 for RIPv2. It is supported on the XSR with the following features:

•Set globally with the router rip and per interface with the network commands: they

support RIP on both LAN and WAN interfaces with these default values: Receive RIPv1 and v2, Transmit RIPv1, no redistribution, no filtering and Split Horizon with no poison.

•Redistribute static routes into RIP with the redistribute command

•Redistribute RIP into OSPF and vice versa with the redistribute rip and redistribute ospf commands

•Split horizon with poisoned reverse enabled with ip split-horizon

•Triggered updates delivered by default or disabled by ip rip disable-triggered-updates

•Clear text authentication enabled by ip rip authentication mode

Note: RIP commands configured under Interface mode are independent of enabling/disabling the RIP protocol.

•RIP is configurable for:

–Send only mode set by issuing no received interface to prevent RIP from receiving update packets on a specified port

–Receive only mode set by issuing passive interface to prevent RIP from sending update packets on a specified port

XSR User’s Guide 5-11