I'm back and i'm more upgraded

Hello for those of you who are reading this post! Today is the third week of my CISCO Academy Progress, and I must admit CCNA1 hasn't been fully completed for me. My new goal for today is to keep improving or patch up any missing information I came to miss from last school year. I'm hoping for the better to be able to reach my goal for this year and to also start a new technology club called Tech Squad Rebooted. One of my former CISCO teacher's already applied for grants to help subsidize the club. I'm really hoping this club can get through because not only will it help improve my technology skills but it will also help other students. This is gonna be a good school year....

Packet Tracer# 7.1.5.2: Verify Non-Convergence Using Commands

In this Packet Tracer what i did was test out the network and identify the problems in the simulation mode. First i did show ip brief to show me everything that was configured for the the network according to R2. After managing that everything was good, i pinged to 172.30.1.1 & 172.30.100.1 and found that it was successful but there was still a problem. When R1 pinged to 172.30.100.1, it completely failed so i examined the route to R2 using show ip route and found that there is no route to network 172.30.100.0/24, so pings to that network will fail. The problem with network was that simple non convergence so i input the configuration to R2 and it was successfully functioning correctly.

Packet Tracer# 7.2.4 Configure RIPv2

For this lab all i did was change the RIPv1 version to RIPv2. RIPv1 is a classfull routing protocol that sends an update to every router with the same subnet mask every 30 seconds, but it doesn't send subnet mask information. RIPv2 does send out subnet mask information (Which was an improvement of RIPv1) to the network every 30 seconds and it's classless. RIPv2 also supports EIGRP , & OSPF, which RIPv1 didn't support for it's networking updating and it also supports VLSM (Variable Length Subnet Mask). I also had to turn off the automatic summarization of the network using the command: no auto summary. I use the command: version 2 to change the RIP version to RIPv2.

Packet Tracer# 7.4.3.2 Routing Table Corruption

In this packet tracer my job was to basically setup a default rip route, setup static routes for the ISP, turn every port status to up, and to setup a rip route. What my first priority was, is to turn on every port status so that there is a valid connection and so that i know if i can ping to the other routers. After doing all of that with the command no shutdown, i went straight with the rip routes. What RIP does is that it sends an update to the routers that you configured every 30 seconds for a network change. So after configuring every router with a RIP route with network (The network Address) i wanted to setup a default origin in the ISP. Since the ISP needed to know what is being changed in the network i had to make that the default information origin. I used the command Default-Information originate in the configuration terminal of ISP to setup the RIP default router. Finally, i made the static routes from ISP to every device that was in the network so i can ping and have communication to them. That's what Routing Table Corruption was basically all about, to fix anything and making sure the network was being updated.

My First Network Topology

Here are the screenshots of my network! I secured passwords for my routers, routed direct ip's from one end of the network to the other, setup a dhcp ip for the server, and learned the basic commands for configuring a router. Here is a screenshot of my router....

First i will demonstrate the first router as an example of simply configuring, i will also free post up commands and what they do.
First thing that i do is setup a password for the User, Privilege, Console, and Configuration modes; i don't want people editing my router so i put in a password. Here are my Statistic of my configurations.....

Ports...

Passwords....

Banner....

Now I will demonstrate my WannaB Router Statistics. This is pretty much the same thing....

Ports.....

Passwords......

Banners......

PT 4.4.1 Packet Tracer: Routing Loops

In this packet tracer we will identify what routing loop does to the network and what functions to take when a routing loop occurs. Routing Loops occur when there is an invalid static route or route in the network, when there is an error in the network the packet is then being constantly messaged through the network until it is eventually terminated. You can verify this using show run and ip route to check what the error is. The error in the route was Serial route 0.0.0.0 0.0.0.0 serial 0/1 had to be configured into the network; as a result of this direct conflict i used config t to enter in the ip route 0.0.0.0 0.0.0.0 0/1. After completing that, i could ping thorugh the network perfectly.

PT 3.4.4.2 Packet tracer: Viewing Routing Table Information -show ip route

Basically in this packet tracer, we are suppose to learn how we use show ip route and what the routing table actually represents in the network. show ip route gives you 2 addresses that show the source and the destination ip; but there is also something that is highlighted in brackets that is also important. For example, have you ever seen this next to the source ip [1/0]? You have! The 2 numbers are the AD (Administrative Distance) and the hop count (Which is the 0). To change the routes from static or directly connected just put in show ip route static/connected.