Information Technology Reference
In-Depth Information
R1#
show ip protocols
Routing Protocol is “rip”
Sending updates every 30 seconds, next due in 16 seconds
Invalid after 180 seconds, hold down 180, flushed after 240
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Redistributing: rip
Default version control: send version 1, receive any version
Interface Send Recv Triggered RIP Key-chain
FastEthernet0/0 1 2 1
Serial0/0/0 1 2 1
Automatic network summarization is in effect
Maximum path: 4
Routing for Networks:
192.168.1.0
192.168.2.0
Passive Interface(s):
Routing Information Sources:
Gateway Distance Last Update
192.168.2.2 120
Distance: (default is 120)
R1 is indeed configured with RIP. R1 is sending and receiving RIP updates on
FastEthernet 0/0 and Serial 0/0/0. R1 is advertising networks 192.168.1.0 and 192.168.2.0.
R1 has one routing information source. R2 is sending R1 updates.
Use the
debug ip rip
command to view the RIP messages being sent and received.
Step 3.
Note:
RIP updates are sent every 30 seconds, so you might have to wait for debug information to be displayed.
R1#
debug ip rip
RIP: received v1 update from 192.168.2.2 on Serial0/0/0
192.168.3.0 in 1 hops
192.168.4.0 in 1 hops
192.168.5.0 in 2 hops
RIP: sending v1 update to 255.255.255.255 via FastEthernet0/0
(192.168.1.1)
RIP: build update entries
network 192.168.2.0 metric 1
network 192.168.3.0 metric 2
network 192.168.4.0 metric 2
network 192.168.5.0 metric 3
RIP: sending v1 update to 255.255.255.255 via Serial0/0/0 (192.168.2.1)
RIP: build update entries
network 192.168.1.0 metric 1
The debug output shows that R1 receives an update from R2. Notice how this update
includes all the networks that R1 does not already have in its routing table. Because the
FastEthernet 0/0 interface belongs to the 192.168.1.0 network configured under RIP, R1
