02.10.2013 Views

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

FTOS Configuration Guide for the C-Series - Force10 Networks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 24 Routing In<strong>for</strong>mation Protocol<br />

Routing In<strong>for</strong>mation Protocol is supported only on plat<strong>for</strong>ms: c e<br />

Routing In<strong>for</strong>mation Protocol (RIP) is a distance-vector routing protocol, which tracks distances or hop<br />

counts to nearby routers.<br />

• Protocol Overview on page 443<br />

• Implementation In<strong>for</strong>mation on page 444<br />

• <strong>Configuration</strong> In<strong>for</strong>mation on page 444<br />

• RIP <strong>Configuration</strong> Example on page 452<br />

Protocol Overview<br />

RIP is <strong>the</strong> oldest interior gateway protocol. There are two versions of RIP: RIP version 1 (RIPv1) and RIP<br />

version 2 (RIPv2). These versions are documented in RFCs 1058 and 2453.<br />

RIPv1<br />

RIPv1 uses hop counts as its metric to construct a table of routing in<strong>for</strong>mation of <strong>the</strong> network and that<br />

routing table is sent as ei<strong>the</strong>r a request or response message. In RIPv1, <strong>the</strong> protocol’s packets are ei<strong>the</strong>r<br />

one-time requests <strong>for</strong> all routing in<strong>for</strong>mation or periodic responses (every 30 seconds) from o<strong>the</strong>r routers<br />

<strong>for</strong> routing in<strong>for</strong>mation. RIP transports its responses or requests by means of UDP, port 520.<br />

RIP must receive regular routing updates to maintain a correct routing table. Response messages<br />

containing a router’s full routing table are transmitted every 30 seconds. If a router does not send an update<br />

within a certain amount of time, <strong>the</strong> hop count to that route is changed to unreachable (a route hop metric<br />

of 16 hops). Ano<strong>the</strong>r timer sets <strong>the</strong> amount of time be<strong>for</strong>e <strong>the</strong> unreachable routes are removed from <strong>the</strong><br />

routing table.<br />

This first RIP version does not support VLSM or CIDR and is not widely used.<br />

RIPv2<br />

RIPv2 adds support <strong>for</strong> subnet fields in <strong>the</strong> RIP routing updates, thus qualifying it as a classless routing<br />

protocol. The RIPv2 message <strong>for</strong>mat includes entries <strong>for</strong> route tags, subnet masks, and next hop addresses.<br />

Ano<strong>the</strong>r enhancement included in RIPv2 is multicasting <strong>for</strong> route updates on IP multicast address<br />

224.0.0.9.<br />

<strong>FTOS</strong> <strong>Configuration</strong> <strong>Guide</strong>, version 7.7.1.0 443

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!