241_Lab4_Instructions_Netlab_2205

docx

School

Rochester Institute of Technology *

*We aren’t endorsed by this school

Course

241

Subject

Computer Science

Date

Apr 3, 2024

Type

docx

Pages

Uploaded by JusticeEagleMaster178

NSSA 241 Lab 4 – Introduction to Routing with Static Routes - Netlab Before starting each activity, review the report questions to ensure that all observations and data necessary to complete your report are recorded. Note no more than two students may work on one bench which has three PCs. Two benches comprise a pod of six PCs which are numbered 1-6. Overview In this lab you will setup and configure routed networks using static routes. You will construct a two- router topology on your bench. In Part I you will examine a successful ping and in Part II you will examine and diagnose an unsuccessful ping. Both cases will present you with an opportunity to gain a deep understanding of the data communication flow and data encapsulation across a routed network. Objectives for this lab are to:  Examine and understand host routing tables  Configure and examine router settings  Compare and contrast messages from the network on one side of a router to the network on the other side of router.  Plan, configure and understand static routes on routers  Test a fully routed network Part I – Examining a Successful Ping - Pinging from PC 2/5 -> PC 3/6 Activity 1 – Setting up the network topology In this activity you will configure your bench network according to the following topology diagram. Note the differing network id in the third octet of the IP addresses for each bench. HINT : For visual clarity, consider using the yellow straight through Ethernet cables for the PC to switch connections and console connections and the green straight through cables for the switch to router connections. 1. Set up the static IPs, masks and gateways on the PCs as you have done in previous weeks 2. Power up the bench rack so that you can configure the Cisco Routers A (2651) and B (2621) 2205- SPM/SPH Page 1

NSSA 241 Lab 4 – Introduction to Routing with Static Routes - Netlab 3. Establish a console session to both Routers A and B via the rack patch panel. Follow the same process as you did with the switches in previous weeks. See Appendix 2 for a refresher on details if needed. HINT : Remember that this is a separate physical connection; different from the Ethernet connections used for data transmission. 4. Write Erase and reload the routers before configuring them. See Appendix 2. As always, it is a good practice to write erase each router and switch used in a topology prior to running experiments. 5. Do not use the autoconfiguration for the routers. As with the switches in previous weeks, answer NO when asked to enter setup configuration. Instead you will configure the device manually. 6. Set the IP addresses for the router interfaces. a. At the router> prompt, enter the command ‘enable’ to move to the next configuration level. b. At the router # prompt, enter the ‘config t’command to move to the global configuration level. c. At the router (config) # prompt, move to a specific interface to configure its IP address and mask. Once you have configured one interface exit to go up a level and enter the second interface to be configured. d. Use the command ‘IP ?’ at the interface level to find the specific command needed to configure the IP address. Hint: use the table below and the appendix at the end of this lab for help with commands. 7. After configuration, the interfaces may be in a shutdown state by default. Check this by using the show interfaces command (just as you did with the switches). 8. To bring the interfaces ‘up,’ issue the ‘no shutdown’ command as you did in previous weeks. Remember you need to be in the interface configuration level for this to take effect. 9. Verify your interface settings by examining the running-configuration for the router. Router# show running-config 10. Verify the routing tables for both routers by issuing the command : Router# show ip route You should see a directly connected route for each interface. This table with examples will help you in configuring the router interfaces. These are EXAMPLES ONLY ! You will need to configure your specific topology settings. Step 1 ip address ip-address mask Example: Router(config-int)# ip address 192.168.12.2 255.255.255.0 Router(config-int)# Sets the IP address and subnet mask for the specified Fast Ethernet interface. Step 2 no shutdown Example: Enables the Ethernet interface, changing its state from administratively down to administratively up. 2205- SPM/SPH Page 2

NSSA 241 Lab 4 – Introduction to Routing with Static Routes - Netlab Router(config-int)# no shutdown Router(config-int)# Step 3 exit Example: Router(config-int)# exit Router(config)# Exits configuration mode for the Fast Ethernet interface and returns to global configuration mode. Activity 2 – Gather network interface data In this activity you will gather the IP and MAC address data of the interfaces in your topology. This is important in analyzing the network traffic that you will see throughout the rest of the experiments. Utilize the ‘show interfaces’ or ‘show running-config’ command as you did earlier to gather the data from the router and ipconfig /all to gather the information from the PCs. Activity 2 Questions 1. Record the MAC and IP addresses below. Interface IP Address MAC address ID to Use for Report Questions Router A 0/0 Rtr_A int 0 Router A 0/1 Rtr_A int 1 Router B 0/0 Rtr_B int 0 Router B 0/1 Rtr_B int 1 PC1/4 PC1/4 PC2/5 PC2/5 PC3/6 PC3/6 2205- SPM/SPH Page 3

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help

NSSA 241 Lab 4 – Introduction to Routing with Static Routes - Netlab Activity 3 – Examine Network Traffic on the Left Side of Router B In this activity you will test connectivity across Router B by pinging from PC2/5->PC3/6. You will examine the arp and ICMP traffic to look at the encapsulation for messages going to the router and then also on the other side of the router. To start with a clean slate, you will begin by clearing all the arp tables on the PCs as well as Router B. 1. Start Wireshark on PCs 2/5 and 3/6. 2. Clear the arp tables of any dynamic entries on both PCs 2/5 and 3/6. a. At the DOS Admin shell, use the arp – d command with the appropriate parameters. NOTE: you will not be able to delete arp entries from the DOS shell you have been using in previous weeks. Instead you will need to have an admin level DOS shell. Right click on the Windows icon and select ‘Windows Powershell Admin.’ 3. Clear the arp table on Router B of any dynamic entries for PCs 2/5 and 3/6. router# clear arp-cache int f 0/1 (specific port will vary based on your device) Detailed Cisco Syntax Description clear arp-cache { traffic type interface-path-id | location node-id } traffic (Optional) Deletes traffic statistics on the specified interface. type Interface type. For more information, use the question mark (?) online help function. interface- path-id Either a physical interface instance or a virtual interface instance as follows: Physical interface instance. Naming notation is rack/slot/module/port and a slash between values is required as part of the notation. rack: Chassis number of the rack. slot: Physical slot number of the modular services card or line card. module: Module number. A physical layer interface module (PLIM) is always 0. port: Physical port number of the interface. Not e In references to a Management Ethernet interface located on a route processor card, the physical slot number is alphanumeric (RP0 or RP1) and the module is CPU0. Example: interface MgmtEth0/RP1/CPU0/0. Virtual interface instance. Number range varies depending on interface type. For more information about the syntax for the router, use the question mark (?) online help function. Location node-id Clears the ARP entries for a specified location. The node-id argument is entered in the rack/slot/module notation. 2205- SPM/SPH Page 4

NSSA 241 Lab 4 – Introduction to Routing with Static Routes - Netlab Note: In order to clear the router’s ARP table, both interfaces must be physically disconnected prior to issuing the command. Reconnect the interfaces when the table is empty. This same procedure may be necessary to clear the PC ARP tables as well. Also consider if ALL interfaces can be cleared from the arp table and if something may need to remain. 4. Ping from PC 2/5 -> PC 3/6. This ping will be successful. 5. Examine the Wireshark captures and arp tables on the PCs and the routers to answer the following questions. As the arp tables may time out, it is good idea to look at those first. Activity 3 Questions 2. When PC 2/5 pings PC 3/6, the first message you should see is an arp request. What IP (device) is PC2/5 arping for? 3. Why is PC2/5 arping for this IP (device) address? Examine your Wireshark captures from PC2/5 to fill in the following diagrams of the ICMP echoes encapsulated in the IP packets that are encapsulated in the Ethernet frames. It is important that you are examining the messages on the left side of Router B as they will be different from the messages on the right side of Router B. The order of the messages is also important in considering the flow of traffic in a fully functional network. Save your packet captures to help you in answering these questions. Hint: There are many questions below that seem repetitive in nature. This is intentional in order for you to gain a deep understanding of the message encapsulation on one side of the router compared to the other side of the router. Pay close attention to all of the source and destination fields as you work through these questions. The concepts you are learning here lay a foundation for all networking communication. REQUIRED: When identifying the node or interface in the tables for the lab report, use the ID assigned in the table in Activity 2. Ex. Rtr_A int 0 4. Ethernet frame encapsulating arp request from PC2/5 Preamble Start of frame delimiter Dest MAC Src MAC Type/Length Data (Encapsulated ARP Message) CRC N/A N/A N/A 5. Explain the destination MAC address in the Ethernet frame above. What is it and why? 6. Explain the source MAC address in the Ethernet frame above. What is it and why? 7. ARP request from PC2/5 (encapsulated in frame above) Hardware type Protocol type Op Code Hardwar e addr. Len Protocol addr. Len Sender hardware address Sender protocol address Target hardware address Target protocol address 2205- SPM/SPH Page 5

NSSA 241 Lab 4 – Introduction to Routing with Static Routes - Netlab 8. Explain the sender hardware address in the arp request above. What is it and why? 9. Explain the sender protocol address in the arp request above. What is it and why? 10. Explain the target hardware address in the arp request above. What is it and why? 11. Explain the target protocol address in the arp request above. What is it and why? 12. Ethernet frame encapsulating arp reply Preamble Start of frame delimiter Dest MAC Src MAC Length/Type Data (Encapsulated ARP message) CRC N/A N/A N/A 13. Explain the destination MAC in the Ethernet frame above. What is it and why? 14. Explain the Source MAC in the Ethernet frame above. What is it and why? 15. ARP reply (encapsulated in frame above) Hardware type Protocol type Op Code Hardwar e addr. Len Protocol addr. len Sender hardware address Sender protocol address Target hardware address Target protocol address 16. Explain the sender hardware address in the arp reply above. What is it and why? 17. Explain the sender protocol address in the arp reply above. What is it and why? 18. Explain the target hardware address in the arp reply above. What is it and why? 19. Explain the target protocol address in the arp reply above. What is it and why? 20. Ethernet frame encapsulating ICMP ECHO request from PC2/5 Preamble Start of frame delimiter Dest MAC Src MAC Length/Type Data (Encapsulated ICMP Msg) CRC N/A N/A N/A 21. Explain the destination MAC address in the Ethernet frame above. What is it and why? 22. Explain the source MAC address in the Ethernet frame above. What is it and why? 2205- SPM/SPH Page 6

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help

NSSA 241 Lab 4 – Introduction to Routing with Static Routes - Netlab 23. IP Packet with encapsulated ICMP ECHO request from PC2/5. Note that this is an abbreviated packet format that focuses on the source and destination IP addresses for the ICMPs. IP Header info Source IP Destination IP DATA (ICMP ECHO REQUEST) Nothing to record here nothing to record here 24. Explain the source IP address in the IP packet above. What is it and why? 25. Explain the destination IP address in the IP packet above. What is it and why? Activity 4 – Examine Network Traffic on the Right Side of Router B You have already pinged across the router from PC2/5 -> PC 3/6. 1. Examine the arp tables on PC 3/6. If the table entries have been flushed, redo the ping to repopulate the arp table on PC3/6 so you can answer the following questions. Save the packet captures to help you in answering these questions. Activity 4 Questions 26. When PC 2/5 pings PC 3/6, you will also see an arp request on the right side of Router B. Who is arping for whom? 27. Why is this arp occurring? Examine your Wireshark captures from PC3/6 to fill in the following diagrams of the ICMP echoes encapsulated in the IP packets that are encapsulated in the Ethernet frames and answer the questions. It is important that you are now examining the messages on the right side of Router B as they will be different from the messages on the left side of Router B. 28. Ethernet frame encapsulating arp request Preamble Start of frame delimiter Dest MAC Src MAC Length/Type Data CRC N/A N/A N/A 29. Explain the destination MAC address in the Ethernet frame above. What is it and why? 30. Explain the source MAC address in the Ethernet frame above. What is it and why? 31. ARP request (encapsulated in frame above) Hardware type Protocol type Op Code Hardwar e addr. Len Protocol addr. len Sender hardware address Sender protocol address Target hardware address Target protocol address 2205- SPM/SPH Page 7

NSSA 241 Lab 4 – Introduction to Routing with Static Routes - Netlab 32. Explain the sender hardware address in the arp request above. What is it and why? 33. Explain the sender protocol address in the arp request above. What is it and why? 34. Explain the target hardware address in the arp request above. What is it and why? 35. Explain the target protocol address in the arp request above. What is it and why? 36. Ethernet frame encapsulating arp reply Preamble Start of frame delimiter Dest MAC Src MAC Length/Type Data CRC N/A N/A N/A 37. Explain the destination MAC in the Ethernet frame above. What is it and why? 38. Explain the Source MAC in the Ethernet frame above. What is it and why? 39. ARP reply (encapsulated in frame above) Hardware type Protocol type Op Code Hardwar e addr. Len Protocol addr. len Sender hardware address Sender protocol address Target hardware address Target protocol address 40. Explain the sender hardware address in the arp reply above. What is it and why? 41. Explain the sender protocol address in the arp reply above. What is it and why? 42. Explain the target hardware address in the arp reply above. What is it and why? 43. Explain the target protocol address in the arp reply above. What is it and why? 44. Ethernet frame encapsulating ICMP ECHO request Preamble Start of frame delimiter Dest MAC Src MAC Length/Type Data CRC N/A N/A N/A 45. Explain the destination MAC address in the Ethernet frame above. What is it and why? 46. Explain the source MAC address in the Ethernet frame above. What is it and why? 47. IP Packet with encapsulated ICMP ECHO request from PC2/5. Note that this is an abbreviated packet format that focuses on the source and destination IP addresses for the ICMPs. IP Header info Source IP Destination IP DATA (ICMP ECHO REQUEST) 2205- SPM/SPH Page 8

NSSA 241 Lab 4 – Introduction to Routing with Static Routes - Netlab Nothing to record here nothing to record here 48. Explain the source IP address in the IP packet above. What is it and why? 49. Explain the destination IP address in the IP packet above. What is it and why? 50. Ethernet frame encapsulating ICMP ECHO reply Preamble Start of frame delimiter Dest MAC Src MAC Length/Type Data CRC N/A N/A N/A 51. Explain the source MAC address in the Ethernet frame above. What is it and why? 52. IP Packet with encapsulated ICMP ECHO reply. Note that this is an abbreviated packet format that focuses on the source and destination IP addresses for the ICMPs. IP Header info Source IP Destination IP DATA (ICMP ECHO REQUEST) Nothing to record here nothing to record here 53. Explain the Source IP in the IP packet above. What is it and why? 54. Explain the destination IP in the IP packet above. What is it and why? Activity 5 – Examine the Routing Tables - Router B and the Host PCs You have already pinged across the router from PC2/5 -> PC 3/6. Now you will examine the routing tables on both the router and the PCs to determine how each device was processing and forwarding the messages. 1. Examine the routing table on Router B using the command ‘show ip route.’ 2. Examine the routing tables on the PCs using the command ‘route print.’ 3. Save screen captures of these outputs to help you in answering the questions for this activity. Activity 5 Questions 55. Identify which line in the host routing table was used to determine where to send the ICMP echo request. Explain how the host used that specific line in its routing table to determine where to send the ICMP echo request message. Where did it send it? 56. Identify which line in the router’s routing table was used to determine where to send the ICMP echo request. Explain how the router used that specific line in its routing table to forward the ICMP echo request message from one network to the network on the other side of Router B. Part II – Examining and Diagnosing a Ping Failure - Pinging from PC1/4 -> PC 2/5 Activity 6 – Pinging Across Router A 2205- SPM/SPH Page 9

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help

NSSA 241 Lab 4 – Introduction to Routing with Static Routes - Netlab In this activity you will ping from PC1/4 -> PC 2/5, across router A. The ping will fail. You need to determine where the failure is occurring and be able to explain why it fails. Examine the arp tables and routing tables of all the devices in the topology as well as the Wireshark captures to answer the questions for this activity. 1. Refer back to the network topology diagram and trace the path the ping will take from the source to the destination. 2. Ping from PC1/4 -> PC 2/5. Activity 6 Questions 57. At what point in the communication path does the ping fail? Consider the successful communication from your previous experiment where you pinged across router B. This will help you to determine where the failure occurs in this ping from PC1/4->PC2/5. 58. Why does the communication fail here? Consider both static routes and default gateways on both the hosts and the routers in your answer. Activity 7 – Correcting the Communication Failure from Activity 6 Obviously, it is not acceptable that the hosts are unable to reach all the networks. You will need to correct the routing so that all devices can communicate with one another. To do this, you will set up static routes on both routers A and B so that each router will know how to reach the remote networks. For example, Router A needs to know the path to get to the 192.168.103/106.0 network and Router B needs to know how to reach the 192.168.101/104.0 network. 1. Develop a plan for configuring static routes on each router. For example, what network route(s) must be configured on Router A? What network route(s) must be configured on Router B? 2. Once you have that plan, use the following command to configure the static route(s). Remember to always use the ? as a help for deciphering the Cisco commands, formats and required parameters. 3. Command Purpose Step 1 ip route prefix mask { ip- address | interface-type inter face-number [ ip-address ]} Example: Router(config)# ip route 192.168.1.0 255.255.0.0 10.10.10.2 Router(config)# Specifies the static route for the IP packets. For details about this command and additional parameters that can be set, see the Cisco IOS IP Command Reference, Volume 2 of 4: Routing Protocols . 2205- SPM/SPH Page 10

NSSA 241 Lab 4 – Introduction to Routing with Static Routes - Netlab Step 2 end Example: Router(config)# end Router# Exits router configuration mode, and enters privileged EXEC mode. 4. To verify that you have properly configured static routing, enter the ‘show ip route’ command and look for static routes signified by the "S." Router# show ip route 5. Verify that all PCs are able to ping one another. If there is a failure, you will need to determine where and why. Consider all the tools that you have used so far – Wireshark captures, ping tests, tracert, arp table examination. Use these tools to determine where the failure is occurring and correct it. Activity 7 Questions 59. What static route(s) did you add to Router A for successful communication across the entire topology? 60. Describe how each static route added to Router A enables successful communication between the networks. 61. What static route(s) did you add to Router B for successful communication across the entire topology? 62. Describe how each static route added to Router B facilitates successful communications between networks. 63. Map the path of a ping echo request from PC1/4 -> PC2/5. Explain where the packet goes first, then second, then next. Consider the default gateways and the static routes in your response. 64. Map the path of a ping echo reply from PC1/4 -> PC2/5. Explain where the packet goes first, then second, then next. Consider the default gateways and the static routes in your response. You can use a flow chart format for this to visualize the path. NOTE: The return path for the ping (echo reply) is not direct. Be sure to look for and explain why. 2205- SPM/SPH Page 11

NSSA 241 Lab 4 – Introduction to Routing with Static Routes - Netlab Appendix 1 – Brief List of Cisco IOS Commands 2621/2651 enable configure terminal shutdown / no shutdown bridge 1 protocol ieee bridge-group 1 no ip routing show interface ip route spanning-tree bridge run ctrl z ctrl c exit ? tab interface f0/0 / f0/1 ip route <network> <mask> <next-hop-address> ip route 0.0.0.0 0.0.0.0 < interface of default route > ip address < ip address > < subnet mask > 3750 enable configure terminal shutdown / no shutdown show interfaces (to display information on all interfaces) show interfaces <interface number> (to display a specific interface) show spanning-tree show mac address-table show run show monitor debug spanning-tree events switchport access ctrl z ctrl c exit ? tab interface <interface number> for example: int Gi1/0/3 2205- SPM/SPH Page 12

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help

NSSA 241 Lab 4 – Introduction to Routing with Static Routes - Netlab Appendix 2 – Cisco Console Connection and Write Erase Procedure The write erase procedure is something you should become very familiar with. Execute it at the beginning and completion of any labs involving the use of a router or switch. Obviously, in the real world this will be the exception. As the semester progresses the switches will be configured for VLANs, in which case the VLAN configuration settings must be deleted. The Write Erase procedure does not delete the VLAN file, step 7 provides the command to delete this file. 1. Power up the rack to provide power to all the devices on the rack. 2. In order to communicate with the switch or router, a connection must be made between one of the green PC Console ports on the bench rack (there is one per PC) and the green console port for the Cisco 3550 or 2651/2621 router selected via the rack patch panel. Each green PC Console port on the bench rack patch panel is connected to the PC serial (COM) port indicated by the label number. To successfully connect to the console port of the router or switch attach an Ethernet patch cable between one of the PC Console ports ( For example PC1) and the green port having the same letter as the device. 3. There are several terminal emulators that can be used to console into the routers and switches. Click on the Windows icon and type Putty in the search box. 4. Select the Putty icon and configure your terminal session as follows: 5. Select the Serial option for Connection type, the serial line should be COM1 . Configure the terminal session by selecting ‘serial’ on the bottom left hand side of the window and setting the parameters as follows:  9600 Baud  8 bits of data  No parity  1 stop bit  No flow control Then Click Open. 6. Once Putty is running, the boot up process of the switch or router should be visible in the terminal window. If it is already powered up just hit the enter key and you should get a prompt for the switch (switch>) or router (router>) 7. If device presents the Switch> or Router> prompt without entering the system configuration dialog shown on the next page skip to step 8, write erase the device, and start again. Write erase resets the switch to factory defaults. Since many students use these devices it is good practice to write erase these devices prior to using them. Therefore, it is important that you 2205- SPM/SPH Page 13

NSSA 241 Lab 4 – Introduction to Routing with Static Routes - Netlab know how to do it. Below is the initial configuration dialog. If you see this you do not need to write erase the device. === SYSTEM CONFIGURATION DIALOG === Would you like to enter the initial configuration dialog? [yes]: <no> Press RETURN (ENTER) to get started! Once you answer no a couple of minutes will pass and you will see a few more messages. The device will start in auto configuration mode. There are couple of different ways the question to begin automatic setup is asked. Read the question carefully and answer in such a way that does not take you through automatic setup. You will not be using the automatic setup in this course . If you accidentally start automatic setup you can break out of the setup typing <ctrl> c. You will also never set a password (Do not enable secret) on these devices. Hit Enter and a few messages about the interfaces will scroll by. Hit Enter again to get the switch> prompt. 8. To Write Erase the Cisco devices ~ Use as necessary~ Purpose: To ensure that the device is running a standard configuration. Procedure: a. Power up the device. b. Wait for the device to present a Switch> or Router> prompt c. Go to Privileged Exec mode by issuing the enable command. The device will present a Switch# or Router# prompt d. Erase non-volatile memory by issuing the write erase command at the prompt e. When completed, to delete any VLAN configuration settings on the switches, enter delete flash:vlan.dat . f. If you are prompted to confirm these choices, type “y” and enter. g. Issue the reload command at the prompt h. If prompted to save the configuration, select “ no ”. i. When asked to confirm the reload, select “ yes ”. j. After the reload, the system prompts with “enter the initial configuration dialog”, select “ no ”. k. When asked to “terminate the autoinstall”, select “yes”. l. When the message, “Press RETURN to get started!” displays hit return. At this point the switch should be set to its default configuration settings and return user EXEC mode indicated by the switch> prompt 2205- SPM/SPH Page 14

241_Lab4_Instructions_Netlab_2205

Related Documents