Reference no: EM133744188
Data Communications and Networks
Naming and Numbering Instructions:
You are required to use Packet Tracer to design the network above using the appropriate cabling. Devices names as shown below are related to your name.
Required Resources
1 Router (Cisco 4221 with Cisco IOS XE Release 16.9.4 universal image or comparable)
1 Switch (Cisco 2960 with Cisco IOS Release 15.2(2) lanbasek9 image or comparable)
2 PCs (Windows with a terminal emulation program, such as Tera Term)
Console cables to configure the Cisco IOS devices via the console ports
Ethernet cables as shown in the topology
Note: The Gigabit Ethernet interfaces on Cisco 4221 routers are autosensing and an Ethernet straight-through cable may be used between the router and PC-B. If using another model Cisco router, it may be necessary to use an Ethernet crossover cable.
Objectives
Set Up the Topology and Initialize Devices
Configure Devices and Verify Connectivity
Background / Scenario
This is a comprehensive lab to review previously covered IOS commands. In this lab, you will cable the equipment as shown in the topology diagram. You will then configure the devices to match the addressing table. After the configurations have been saved, you will verify your configurations by testing for network connectivity.
After the devices have been configured and network connectivity has been verified, you will use IOS commands to retrieve information from the devices to answer questions about your network equipment.
This lab provides minimal assistance with the actual commands necessary to configure the router. Test your knowledge by trying to configure the devices without referring to the content or previous activities.
Note: The routers used with CCNA hands-on labs are Cisco 4221 with Cisco IOS XE Release 16.9.4 (universalk9 image). The switches used in the labs are Cisco Catalyst 2960s with Cisco IOS Release 15.2(2) (lanbasek9 image). Other routers, switches, and Cisco IOS versions can be used. Depending on the model and Cisco IOS version, the commands available and the output produced might vary from what is shown in the labs. Refer to the Router Interface Summary Table at the end of the lab for the correct interface identifiers.
Task 0: Create Network Topology
Cable your network as shown in the above network topology.
Use the below Youtube tutorial to help you with all steps:
Task 1: Set Up Topology and Initialize Devices
Step 1.1: Cable the network as shown in the topology.
Attach the devices shown in the topology diagram, and cable, as necessary.
Power on all the devices in the topology.
Step 1.2: Initialize and reload the router and switch.
If configuration files were previously saved on the router and switch, initialize and reload these devices back to their default configurations.
Task 2: Configure Devices and Verify Connectivity
In Task 2, you will set up the network topology and configure basic settings, such as the interface IP addresses, device access, and passwords. Refer to the addressing table and topology at the beginning of this lab for device names and address information.
Step 2.1: Assign static IPv4 information to the PC interfaces.
Configure the IP address, subnet mask, and default gateway settings on PC-A.
Configure the IP address, subnet mask, and default gateway settings on PC-B.
Ping PC-B from a command prompt window on PC-A.
Question:
Why were the pings not successful?
Step 2.2: Configure the router.
Console into the router and enable privileged EXEC mode.
Open configuration window
Enter configuration mode.
Assign a device name to the router.
Router(config)# hostname R1_<Your StudentID>
R1_xxxxxxx(config)# exit
DO not use xxxxxxx, use your student ID.
Disable DNS lookup to prevent the router from attempting to translate incorrectly entered commands as though they were host names.
Assign class as the privileged EXEC encrypted password.
Assign cisco as the console password and enable login.
Assign cisco as the VTY password and enable login.
Encrypt the plaintext passwords.
Create a banner that warns anyone accessing the device that unauthorized access is prohibited.
Configure and activate both interfaces on the router.
Configure an interface description for each interface indicating which device is connected to it.
To enable IPv4 routing, enter the command ip routing.
R1(config)# ip routing
Save the running configuration to the startup configuration file.
Issue show run and paste the running configuration below.
Insert running configuration below:
o. Set the clock on the router.
Note: Use the question mark (?) to help with the correct sequence of parameters needed to execute this command.
Close configuration window
p. Ping PC-B from a command prompt window on PC-A.
Note: If pings are not successful, the Windows Firewall may need to be turned off.
Question:
Were the pings successful? Explain.
Step 2.3: Configure the switch.
In this step, you will configure the hostname, the VLAN 1 interface and its default gateway.
Open configuration window
Console into the switch and enable privileged EXEC mode.
Enter configuration mode.
Assign the device name S1_<Your StudentID> to the switch.
Disable DNS lookup to prevent the router from attempting to translate incorrectly entered commands as though they were host names.
Configure and activate the VLAN interface on the switch S1.
Configure the default gateway for the switch S1.
Save the running configuration to the startup configuration file.
Issue show run and paste the running configuration below.
Insert running configuration below:
Step 2.4: Verify connectivity end-to-end connectivity.
From PC-A, ping PC-B.
From S1, ping PC-B.
All the pings should be successful.
Task 3: Display Device Information
Close configuration window
In Task 3, you will use show commands to retrieve interface and routing information from the router and switch.
Step 3.1: Display the routing table on the router.
Use the show ip route command on the router R1 to answer the following questions.
Open configuration window
Questions:
What code is used in the routing table to indicate a directly connected network?
How many route entries are coded with a C code in the routing table?
What interface types are associated to the C coded routes?
Use the show ip route command on router R1 to display the IPv4 routes.
Insert Screenshots for steps a-b below:
Step 3.2: Display interface information on the router R1.
Use the show ip interface g0/0/1 to answer the following questions.
Questions:
What is the operational status of the G0/0/1 interface?
What is the Media Access Control (MAC) address of the G0/1 interface?
How is the Internet address displayed in this command?
Step 3.3: Display a summary list of the interfaces on the router and switch.
There are several commands that can be used to verify an interface configuration. One of the most useful of these is the show ip interface brief command. The command output displays a summary list of the interfaces on the device and provides immediate feedback to the status of each interface.
Enter the show ip interface brief command on the router R1.
R1# show ip interface brief
Close configuration window
Enter the show ip interface brief command on the switch S1.
Open configuration window
S1# show ip interface brief
Insert Screenshots for steps a-c below:
Reflection Questions
If the G0/0/1 interface showed that it was administratively down, what interface configuration command would you use to turn the interface up?
What would happen if you had incorrectly configured interface G0/0/1 on the router with an IP address of 192.168.1.2?
The default bias template used by the Switch Database Manager (SDM) does not provide IPv6 address capabilities. Verify that SDM is using either the dual-ipv4-and-ipv6 template or the lanbase-routing template. The new template will be used after reboot even if the configuration is not saved.
S1# show sdm prefer
Use the following commands to assign the dual-ipv4-and-ipv6 template as the default SDM template.
S1# configure terminal
S1(config)# sdm prefer dual-ipv4-and-ipv6 default
S1(config)# end
S1# reload
Task 0: Create Network Topology
Use the below Youtube tutorial to help you with all steps:
Task 4: Configure IPv6 Addresses Manually
Step 4.1: Assign the IPv6 addresses to Ethernet interfaces on R1.
Assign the IPv6 global unicast addresses, listed in the Addressing Table, to both Ethernet interfaces on R1.
Open configuration window
Verify that the correct IPv6 unicast address is assigned to each interface.
Note: The link-local address (fe80::) displayed is based on EUI-64 addressing, which automatically uses the interface Media Access Control (MAC) address to create a 128-bit IPv6 link-local address.
To get the link-local address to match the global unicast address on the interface, manually enter the link-local addresses on each of the Ethernet interfaces on R1.
Note: Each router interface belongs to a separate network. Packets with a link-local address never leave the local network; therefore, you can use the same link-local address on both interfaces.
Use a command of your choice to verify that the link-local address has been changed to fe80::1.
Step 4.2: Enable IPv6 routing on R1.
On a PC-B command prompt, enter the ipconfig command to examine IPv6 address information assigned to the PC interface.
Question:
Has an IPv6 unicast address been assigned to the network interface card (NIC) on PC-B?
b. Enable IPv6 routing on R1 using the IPv6 unicast-routing command.
Open configuration window
c. Use a command to verify the new multicast group are assigned to interface G0/0/0. Notice that the all-router multicast group (FF02::2) now appears for interface G0/0/0.
Note: This will allow the PCs to obtain their IP address and default gateway information automatically using Stateless Address Autoconfiguration (SLAAC).
d. Now that R1 is part of the all-router multicast group ff02::2, re-issue the ipconfig command on PC-B and examine the IPv6 address information.
Step 4.3: Assign IPv6 addresses to the management interface (SVI) on S1.
Assign the IPv6 address for S1. Also assign a link-local address for this interface.
Use a command of your choice to verify that the IPv6 addresses are properly assigned to the management interface.
Step 4.4: Assign static IPv6 addresses to the PCs.
Open the Ethernet Properties window on for each PC and assign IPv6 addressing.
Verify both PCs have the correct IPv6 address information. Each PC should have two Global IPv6 addresses: one static and one SLACC
Step 4.5: Verify End-to-End Connectivity
From PC-A, ping fe80::1. This is the link-local address assigned to G0/0/1 on R1.
Ping the S1 management interface from PC-A.
Use the tracert command on PC-A to verify that you have end-to-end connectivity to PC-B.
From PC-B, ping PC-A.
From PC-B, ping the link-local address for G0/0/0 on R1.
Note: If end-to-end connectivity is not established, troubleshoot your IPv6 address assignments to verify that you entered the addresses correctly on all devices.
Reflection Questions
Why can the same link-local address, fe80::1, be assigned to both Ethernet interfaces on R1?
What is the Subnet ID of the IPv6 unicast address 2001:db8:acad::aaaa:1234/64?
In this part 3, you will configure RIP routing protocol and generate the routing tables.
Cable your network as shown in the below network topology.
Task 5: Configure Dynamic RIP Routing on Routers
Step 5.1: Configure RIP
Follow the step-by-step video and configure RIP on all three router. Note that you MUST use your addresses that depend on your students ID.
Under each router use the command "show run" and paste the running configuration of each router below.
Insert running configurations for R1-R3 for steps a-b below:
Task 6: Generate Routing Tables
Step 6.1: Generate the routing tables of all routers.
Under each router use the command "show ip route" and generate the routing table of the router and paste the routing table of each router below.
Consider the routing Table of R1 and answer the below questions:
Which networks are directly connected (those labeled by "C") and on which ports?
Which network destinations have been learned dynamically by R1 using RIP (those labeled by "R") and on which ports?
Task 7: Link Failure Impact on Routing Tables
Step 6.1: Fail a Link.
Delete the link between R1 and R2 to simulate a broken link.
Regenerate the routing tables of R1 using the "show ip route" and answer the below question.
What is the main differences between R1 routing tables before and after the failure from a routing perspective?
Attachment:- Data Communications and Networks.rar