LAB3-Part3(a)

After R7 router rip enable

Wireshark outputs
At int fa0/1

At int fa0/0

As observed from the wireshark outputs the respective connected interface sends a
RIP request and the interfaces in that networks send out arp to find out the mac of
the newly connected interface.Also observe the change in routing tables of R5 and
R8.

LAB3-Part(B)
Commands:
Setting timer command
http://www.freeccnaworkbook.com/workbooks/ccna/configuring-routing-informationprotocol-rip

http://blog.ine.com/2010/04/15/how-basic-are-rip-timers-test-your-knowledge-now/

Show ip protocols:

----------------------------------------------------------

Lab3- PART(c)
Routing table at R6 before r7 is shutdown.

After r7 fa0/1 is shutdown, then the tables converge(check how to view this(in my r3
output it just chaged from 16 hops to 12 hops)) and later all the packets to network
10.0.1.0 is sent through r1 despite the cost due to R7 link outage.

Ping output at R6: When R7 fa0/1 is shutdown, then naturally all the packets are
routed through r1 despite the high metric. Notice the metric at the bottom of the
image for 10.0.1.0 network

Debug R3:

Wireshark:

A rough note: probably to check the convergence time do continuous pings from R6
TO R5 and it will keep failing, until a certain point when the tables converge. Then
the R6 TO R5 ping will be successful. And also the time can be observed in the r3
router debug.
Lab 4-part3(b):

Wireshark output at r7 fa0/0 link

Sequence of events at R6:

TRACEROUTE AND PINGS R6 TO R5

DEBUG AT R3: Part(b) definitely takes longer to converge than Part(c)