Just to mention it. RIP version 2 is mostly the same
as RIP version 1. Both RIPv1 and RIPv2 are distance-vector protocols, which
means that each router running RIP sends its complete routing tables out all
active interfaces at periodic time intervals. Also, the timers and
loop-avoidance schemes are the same in both RIP versions-i.e., holddown timers
and split horizon rule. Both RIPv1 and RIPv2 are configured as classful
addressing, (but RIPv2 is considered classless because subnet information is
sent with each route update), and both have the same administrative distance
(120).
But there are some important differences that make
RIPv2 more scalable than RIPv1. And I’ve got to add a word of advice here
before we move on; I’m definitely not advocating using RIP of either version in
your network. But since RIP is an open standard, you can use RIP with any brand
of router. You can also use OSPF, since OSPF is an open standard as well. RIP
just requires too much bandwidth, making it pretty intensive to use in your
network. Why go there when you have other, more elegant options?
RIP v1 |
RIPv2
|
Distance vector
|
Distance vector
|
Maximum hop count of 15
|
Maximum hop count of 15
|
Classful
|
Classless
|
No support for VLSM
|
Supports VLSM networks
|
No support for discontiguous networks
|
Supports discontiguous networks
|
RIPv2, unlike RIPv1, is a classless routing protocol
(even though it is configured as classful, like RIPv1), which means that it
sends subnet mask information along with the route updates. By sending the
subnet mask information with the updates, RIPv2 can support Variable Length
Subnet Masks (VLSMs) as well as the summarization of network boundaries.
The configuration is preaty simple:
R1#conf t
Enter
configuration commands, one per line. End with CNTL/Z.
R1(config)#router
rip
R1(config-router)#network
10.0.0.0
R1(config-router)#version
2
No comments:
Post a Comment