Information Technology Reference
In-Depth Information
R1#
show ip protocols
Routing Protocol is “rip”
Sending updates every 30 seconds, next due in 10 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
Serial0/0/0 1 2 1
Automatic network summarization is in effect
Maximum path: 4
Routing for Networks:
172.30.0.0
Passive Interface(s):
FastEthernet0/0
Routing Information Sources:
Gateway Distance Last Update
172.30.2.2 120 00:00:13
Distance: (default is 120)
View the RIP messages being sent and received.
Step 3.
To view the RIP messages being sent and received, use the
debug ip rip
command. Notice
that RIP updates are not sent out of the Fa0/0 interface because of the
passive-interface
fastethernet 0/0
command:
R1#
debug ip rip
RIP: sending v1 update to 255.255.255.255 via Serial0/0/0 (172.30.2.1)
RIP: build update entries
network 172.30.1.0 metric 1
RIP: received v1 update from 172.30.2.2 on Serial0/0/0
172.30.3.0 in 1 hops
Discontinue the debug output with the
undebug all
command.
Step 4.
R1#
undebug all
All possible debugging has been turned off
Packet Tracer Companion: Basic RIP Configuration (5.6.1b)
Packet Tracer
Companion
You can now open the file LSG02-Lab561b.pka on the CD-ROM that accompanies this topic to repeat
this portion of the hands-on lab using Packet Tracer. Remember, however, that Packet Tracer is not a
substitute for a hands-on lab experience with real equipment. A summary of the instructions is provid-
ed within the activity.
