Concept Guide
Destination Gateway Dist/Metric Last Change
----------- ------- ----------- -----------
C 10.11.10.0/24 Direct, Te 2/11/1 0/0 00:02:26
C 10.11.20.0/24 Direct, Te 2/3/1 0/0 00:02:02
R 10.11.30.0/24 via 10.11.20.1, Te 1/1/1/1 120/1 00:01:20
C 10.200.10.0/24 Direct, Te 2/4/1 0/0 00:03:03
C 10.300.10.0/24 Direct, Te 2/5/1 0/0 00:02:42
R 192.168.1.0/24 via 10.11.20.1, Te 1/1/1/1 120/1 00:01:20
R 192.168.2.0/24 via 10.11.20.1, Te 1/1/1/1 120/1 00:01:20
Core2# 
R 192.168.1.0/24 via 10.11.20.1, Te 1/1/1/1 120/1 00:05:22
R 192.168.2.0/24 via 10.11.20.1, Te 1/1/1/1 120/1 00:05:22
Core2#
The following example shows the show ip protocols command to show the RIP conguration activity on Core 2.
Core2#show ip protocols
Routing Protocol is "RIP"
 Sending updates every 30 seconds, next due in 17
 Invalid after 180 seconds, hold down 180, flushed after 240
 Output delay 8 milliseconds between packets
 Automatic network summarization is in effect
 Outgoing filter for all interfaces is
 Incoming filter for all interfaces is
 Default redistribution metric is 1
 Default version control: receive version 2, send version 2
 Interface Recv Send
 TenGigabitEthernet 1/1/1/1 2 2
 TenGigabitEthernet 1/1/1/2 2 2
 TenGigabitEthernet 1/1/1/3 2 2
 TenGigabitEthernet 1/1/1/4 2 2
Routing for Networks:
 10.300.10.0
 10.200.10.0
 10.11.20.0
 10.11.10.0
Routing Information Sources:
Gateway Distance Last Update
10.11.20.1 120 00:00:12
Distance: (default is 120)
Core2#
RIP Conguration on Core3
The following example shows how to congure RIPv2 on a host named Core3.
Example of Conguring RIPv2 on Core3
Core3(conf)#router rip
Core3(conf-router_rip)#version 2
Core3(conf-router_rip)#network 192.168.1.0
Core3(conf-router_rip)#network 192.168.2.0
Core3(conf-router_rip)#network 10.11.30.0
Core3(conf-router_rip)#network 10.11.20.0
Core3(conf-router_rip)#show config
!
router rip
 network 10.0.0.0
 network 192.168.1.0
 network 192.168.2.0
 version 2
Core3(conf-router_rip)#
Routing Information Protocol (RIP)
809










