Packet Tracer Exploration: Verify Non-Convergence Using Commands 7.1.5.2

In this packet tracer consists of the same network topology setup as the previous network. I did not have to do any configuring, however, we needed to perform several tasks in order to ensure the reliability of the network. First I verified and tested the connectivity. I verified the link status by issuing the command show ip interface brief. Afterwards, I used ping commands from router 2. I used the command "Ping 172.30.1.1, and it was partially successful. Then I pinged 172.30.100.1, and it was also partially successful. Once I was finished with that, I went over to router 1 and accessed the CLI tab. I then pinged devices from there also. I issued the "Ping 10.1.0.1" and "Ping 172.30.100.1" however, Ping 172.30.100.1 was a failed ping, which meant that the connection to that device was not good. I also issued ping commands from router 3 also. I then examined the routing table on each router by accessing their CLI tab and using the "Show IP route" It turns out that there is no connection to the network 172.30.100.0/24. I was able to examine the updates sent and received on router 2 by issuing the "debug ip rip" command. By doing this, I was able to simulate and trace the pings. I entered simulation mode so I can monitor and trace the destination of packets in order to find out where the problem was. By examining the inbound and outbound PDU details in order for me to understand the content of the RIP updates.