6-3 and Example 6-4. RIP is enabled on all interfaces and on all routers in this example.
The RIP update sent out Albuquerque's Ethernet0 interface advertises five routes but does
not advertise the route to 10.1.1.0 because that is the subnet of that attached Ethernet.
Albuquerque's update sent on its Serial1 interface advertises only three routes due to split
horizon rules. Finally, notice the update received on Albuquerque, entering Serial0 (from
Yosemite) after Yosemite's Ethernet0 interface has failed. Yosemite has described subnet
10.1.2.0 with a metric 16 route, which is considered infinite by RIP.
migrate to IGRP. The logic of the network commands works just like with RIP. The output of
the show and debug commands provides some insights into the differences between RIP and
IGRP.
subnet 10.1.6.0, metric 1
subnet 10.1.5.0, metric 2
subnet 10.1.4.0, metric 1
RIP: received v1 update from 10.1.6.253 on Serial1
10.1.3.0 in 1 hops
10.1.2.0 in 16 hops (inaccessible)
10.1.5.0 in 1 hops
ip addr 10.1.2.252 255.255.255.0
interface serial 0
ip addr 10.1.4.252 255.255.255.0
interface serial 1
ip addr 10.1.5.252 255.255.255.0
network 10.0.0.0
no router rip
router igrp 5
network 10.0.0.0
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default
U - per-user static route, o - ODR