Packet Tracer Lab 7.6.1

The Packet Tracer Activity integrates all the knowledge and skills you acquired in previous chapters of the routing curriculum. Skills related to the discussion of RIPv2 are also included. In this activity, you build a network from the ground up. Starting with an addressing space and network requirements, you must implement a network design that satisfies the specifications, then implement an effective RIPv2 routing configuration with integrated default routing. Detailed instructions are provided within the activity. Design and document the addressing scheme according to the procedure, this includes configuring static routes and setting default routes, as well as verifying and troubleshooting all those configurations afterwards.

Packet Tracer Lab 7.5.3

In this packet tracer activity, you begin by loading configuration scripts on each of the routers. These scripts contain errors that will prevent end-to-end communication across the network. After loading the corrupted scripts, troubleshoot each router to determine the configuration errors, and then use the appropriate commands to correct the configurations. When you have corrected all of the configuration errors, all of the hosts on the network should be able to communicate with each other. Once all the connections are verified then you should configure the proper subnet mask as well as ip addresses for all the devices on the network. In addition clock rates must be adjusted as well as making sure that the port status for all device is on.

Packet Tracer Lab 7.5.2

This Packet Tracer Activity is a mirror image of the previous one, just with more complex configurations and a larger emphasis on CLI. In this lab activity, you are given a network address that must be subnetted using VLSM to complete the addressing of the network. A combination of RIP version 2 and static routing will be required so that hosts on networks that are not directly connected will be able to communicate with each other and the Internet. All in all this packet tracer activity requires you to use RIPv2 commands such as ip interface brief, in order to properly configure a network supported by VLSM. For obvious reasons you must use the information provided to you in the procedure although you must also create your own ip addresses and subnet masks in accordance to the rest of the network and the RIPv2 protocol.

Packet Tracer 7.5.1

In the following packet tracer activity we review the basic configurations and functions of RIPv2. Including discontigous networks and using VLSM to subnet it. Since we are configuring a classless routing protocol then commands such as show ip route, debug ip rip, as well as show ip interface brief. It is also encouraged to set the timers, all in all RIPv2 configurations are similar to RIPv1. Although it is classless, basically the strengths of the RIP protocol are enhanced but the flaws remain evident. That means that you will have to work around the 15 and 16 hop count to infinity. Verification as well as troubleshooting should be simple at this point, so pinging should come naturally. The rest of this lab is configuring the network ip's and subnet mask according to the procedure.

Packet Tracer Lab 7.4.3

Routing table corruption is a severe issue that can influence your network, this packet tracer activity will expose and troubleshoot such corruption. To avoid such problems it must be made sure that each router has a default route to the desired destination. It is also advised to take other authentication precautions such as routers accepting routing information only from other routers with the same passwords. This will prevent malicious attacks from outside sources. You must implement a load balance between routers to make sure that the following procedures work without flaw. The rest revolves around tidying up all of the standard security issues such as passwords and secrets. You also must be aware of the timers that are initiated on your routers, most significantly the update timer. Commands that will prove to be of worth include the show cdp neighbor as well as show running config.

Packet Tracer Lab 7.2.4

In this packet tracer activity we venture into the RIPv2 field. Requirements include disabling automatic configurations as well as verifying configurations. RIPv2 is a classless routing protocol this means that it supports VLSM along with CIDR. In networks that use a VLSM addressing scheme, a classless routing protocol is essential to propagate all of the networks along with their correct subnet masks. As a result we will be using such a format for the network at hand. The debug ip rip command will be of assistance in this lab, in order to reverse the previous configurations of RIPv1. Many of the same commands that were used for verifying and troubleshooting RIPv1 can be used for RIPv2 as well. Such commands include show ip route, show ip interface brief, as well as show running config, and then skynet takes over.

Packet Tracer Lab 7.1.5

This Packet Tracer Activity is relevant to verifying non convergence through commands. As you should already know, updates are not sent across classful network boundaries with RIPv1. This Packet Tracer utilizes the ip route, ping, and debug ip rip commands. Two extensions are implemented in order to verify and enable RIPv1, the first is the subnet mask, allowing a 32 bit mask in the rip route entry. As a result, the receiving router no longer depends upon the subnet mask of the inbound interface or the classful mask when determining the subnet mask for a route. The latter allows a router to make better decisions regarding the next hop address. With help from these two extensions your a able to successfully verify the non convergence of the network, of course you still need to access the convergence through the CLI. The commands should never be neglected and are vital to the completion of this assignment.