Module 9 Labs

pdf

School

University of Missouri, Columbia *

*We aren’t endorsed by this school

Course

221

Subject

Information Systems

Date

Oct 30, 2023

Type

pdf

Pages

Uploaded by joelpinto923

© 2013 - 2021 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 1 of 4 www.netacad.com Packet Tracer - Identify MAC and IP Addresses Objectives Part 1: Gather PDU Information for Local Network Communication Part 2: Gather PDU Information for Remote Network Communication Background This activity is optimized for viewing PDUs. The devices are already configured. You will gather PDU information in simulation mode and answer a series of questions about the data you collect. Instructions Part 1: Gather PDU Information for Local Network Communication Note : Review the Reflection Questions in Part 3 before proceeding with Part 1. It will give you an idea of the type of information you will need to gather PDU information as a packet travels from 172.16.31.5 to 172.16.31.2. a. Click 172.16.31.5 and open the Command Prompt . b. Enter the ping 172.16.31.2 command. c. Switch to simulation mode and repeat the ping 172.16.31.2 command. A PDU appears next to 172.16.31.5 . d. Click the PDU and note the following information from the OSI Model and Outbound PDU Layer tabs: o Destination MAC Address: 000C:85CC:1DA7 o Source MAC Address: 00D0:D311:C788 o Source IP Address: 172.16.31.5 o Destination IP Address: 172.16.31.2 o At Device: 172.16.31.5 e. Click Capture / Forward (the right arrow followed by a vertical bar) to move the PDU to the next device. Gather the same information from Step 1d. Repeat this process until the PDU reaches its destination. Record the PDU information you gathered into a spreadsheet using a format like the table shown below: Example Spreadsheet Format At Device Dest. MAC Src MAC Src IPv4 Dest IPv4 172.16.31.5 000C:85CC:1DA7 00D0:D311:C788 172.16.31.5 172.16.31.2 Switch1 000C:85CC:1DA7 00D0:D311:C788 N/A N/A Hub N/A N/A N/A N/A 172.16.31.2 00D0:D311:C788 000C:85CC:1DA7 172.16.31.2 172.16.31.5 Step 2: Gather additional PDU information from other pings. Repeat the process in Step 1 and gather the information for the following tests: • Ping 172.16.31.2 from 172.16.31.3.

Packet Tracer - Identify MAC and IP Addresses © 2013 - 2021 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 2 of 4 www.netacad.com • Ping 172.16.31.4 from 172.16.31.5. Return to Realtime mode. Part 2: Gather PDU Information for Remote Network Communication In order to communicate with remote networks, a gateway device is necessary. Study the process that takes place to communicate with devices on the remote network. Pay close attention to the MAC addresses used. Step 1: Gather PDU information as a packet travels from 172.16.31.5 to 10.10.10.2. a. Click 172.16.31.5 and open the Command Prompt . b. Enter the ping 10.10.10.2 command. c. Switch to simulation mode and repeat the ping 10.10.10.2 command. A PDU appears next to 172.16.31.5 . d. Click the PDU and note the following information from the Outbound PDU Layer tab: • Destination MAC Address: 00D0:BA8E:741A • Source MAC Address: 00D0:D311:C788 • Source IP Address: 172.16.31.5 • Destination IP Address: 10.10.10.2 • At Device: 172.16.31.5 Question: What device has the destination MAC that is shown? Type your answers here. e. Click Capture / Forward (the right arrow followed by a vertical bar) to move the PDU to the next device. Gather the same information from Step 1d. Repeat this process until the PDU reaches its destination. Record the PDU information you gathered from pinging 172.16.31.5 to 10.10.10.2 into a spreadsheet using a format like the sample table shown below: At Device Dest. MAC Src MAC Src IPv4 Dest IPv4 172.16.31.5 00D0:BA8E:741A 00D0:D311:C788 172.16.31.5 10.10.10.2 Switch1 00D0:BA8E:741A 00D0:D311:C788 N/A N/A Router 0060:2F84:4AB6 00D0:588C:2401 172.16.31.5 10.10.10.2 Switch0 0060:2F84:4AB6 00D0:588C:2401 N/A N/A Access Point N/A N/A N/A N/A 10.10.10.2 00D0:588C:2401 0060:2F84:4AB6 10.10.10.2 172.16.31.5 Reflection Questions Answer the following questions regarding the captured data: 1. Were there different types of cables/media used to connect devices? Type your answers here.

Packet Tracer - Identify MAC and IP Addresses © 2013 - 2021 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 3 of 4 www.netacad.com 2. Did the cables change the handling of the PDU in any way? Type your answers here. 3. Did the Hub lose any of the information that it received? Type your answers here. 4. What does the Hub do with MAC addresses and IP addresses? Type your answers here. 5. Did the wireless Access Point do anything with the information given to it? Type your answers here. 6. Was any MAC or IP address lost during the wireless transfer? Type your answers here. 7. What was the highest OSI layer that the Hub and Access Point used? Type your answers here. 8. Did the Hub or Access Point ever replicate a PDU that was rejected with a red “X”? Type your answers here. 9. When examining the PDU Details tab, which MAC address appeared first, the source or the destination? Type your answers here. 10. Why would the MAC addresses appear in this order? Type your answers here. 11. Was there a pattern to the MAC addressing in the simulation? Type your answers here. 12. Did the switches ever replicate a PDU that was rejected with a red “X”? Type your answers here.

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

Packet Tracer - Identify MAC and IP Addresses © 2013 - 2021 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 4 of 4 www.netacad.com 13. Every time that the PDU was sent between the 10 network and the 172 network, there was a point where the MAC addresses suddenly changed. Where did that occur? Type your answers here. 14. Which device uses MAC addresses that start with 00D0:BA? Type your answers here. 15. What devices did the other MAC addresses belong to? Type your answers here. 16. Did the sending and receiving IPv4 addresses change fields in any of the PDUs? Type your answers here. 17. When you follow the reply to a ping, sometimes called a pong , do you see the sending and receiving IPv4 addresses switch? Type your answers here. 18. What is the pattern to the IPv4 addressing used in this simulation? Type your answers here. 19. Why do different IP networks need to be assigned to different ports of a router? Type your answers here. 20. If this simulation was configured with IPv6 instead of IPv4, what would be different? Type your answers here. End of document

PT Lab 9.1.3 - Identify MAC and IP Addresses Submit screenshot of Overall Feedback tab

© 2013 - 2021 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 1 of 4 www.netacad.com Packet Tracer - Examine the ARP Table Addressing Table Device Interface MAC Address Switch Interface Router0 Gg0/0 0001.6458.2501 G0/1 Router0 S0/0/0 N/A N/A Router1 G0/0 00E0.F7B1.8901 G0/1 Router1 S0/0/0 N/A N/A 10.10.10.2 Wireless 0060.2F84.4AB6 F0/2 10.10.10.3 Wireless 0060.4706.572B F0/2 172.16.31.2 F0 000C.85CC.1DA7 F0/1 172.16.31.3 F0 0060.7036.2849 F0/2 172.16.31.4 G0 0002.1640.8D75 F0/3 Objectives Part 1: Examine an ARP Request Part 2: Examine a Switch MAC Address Table Part 3: Examine the ARP Process in Remote Communications Background This activity is optimized for viewing PDUs. The devices are already configured. You will gather PDU information in simulation mode and answer a series of questions about the data you collect. Instructions Part 1: Examine an ARP Request Step 1: Generate ARP requests by pinging 172.16.31.3 from 172.16.31.2. Open a command prompt a. Click 172.16.31.2 and open the Command Prompt . b. Enter the arp -d command to clear the ARP table. Close a command prompt c. Enter Simulation mode and enter the command ping 172.16.31.3 . Two PDUs will be generated. The ping command cannot complete the ICMP packet without knowing the MAC address of the destination. So the computer sends an ARP broadcast frame to find the MAC address of the destination. d. Click Capture/Forward once. The ARP PDU moves Switch1 while the ICMP PDU disappears, waiting for the ARP reply. Open the PDU and record the destination MAC address. Question: Is this address listed in the table above? Type your answers here.

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

Packet Tracer - Examine the ARP Table © 2013 - 2021 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 2 of 4 www.netacad.com e. Click Capture/Forward to move the PDU to the next device. Question: How many copies of the PDU did Switch1 make? Type your answers here. What is the IP address of the device that accepted the PDU? Type your answers here. f. Open the PDU and examine Layer 2. Question: What happened to the source and destination MAC addresses? Type your answers here. g. Click Capture/Forward until the PDU returns to 172.16.31.2 . Question: How many copies of the PDU did the switch make during the ARP reply? Type your answers here. Step 2: Examine the ARP table. a. Note that the ICMP packet reappears. Open the PDU and examine the MAC addresses. Question: Do the MAC addresses of the source and destination align with their IP addresses? Type your answers here. b. Switch back to Realtime and the ping completes. c. Click 172.16.31.2 and enter the arp – a command. Question: To what IP address does the MAC address entry correspond? Type your answers here. In general, when does an end device issue an ARP request? Type your answers here. Part 2: Examine a Switch MAC Address Table Step 1: Generate additional traffic to populate the switch MAC address table. Open a command prompt a. From 172.16.31.2 , enter the ping 172.16.31.4 command. b. Click 10.10.10. 2 and open the Command Prompt . c. Enter the ping 10.10.10.3 command. Question: How many replies were sent and received? Type your answers here.

Packet Tracer - Examine the ARP Table © 2013 - 2021 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 3 of 4 www.netacad.com Close a command prompt Step 2: Examine the MAC address table on the switches. a. Click Switch1 and then the CLI tab. Enter the show mac-address-table command. Question: Do the entries correspond to those in the table above? Type your answers here. b. Click Switch0 , then the CLI tab. Enter the show mac-address-table command. Questions: Do the entries correspond to those in the table above? Type your answers here. Why are two MAC addresses associated with one port? Type your answers here. Part 3: Examine the ARP Process in Remote Communications Step 1: Generate traffic to produce ARP traffic. Open a command prompt a. Click 172.16.31.2 and open the Command Prompt . b. Enter the ping 10.10.10.1 command. c. Type arp – a . Question: What is the IP address of the new ARP table entry? Type your answers here. d. Enter arp -d to clear the ARP table and switch to Simulation mode. e. Repeat the ping to 10.10.10.1. Question: How many PDUs appear? Type your answers here. Close a command prompt f. Click Capture/Forward . Click the PDU that is now at Switch1 . Question: What is the target destination IP destination address of the ARP request? Type your answers here. g. The destination IP address is not 10.10.10.1. Question: Why? Type your answers here.

Packet Tracer - Examine the ARP Table © 2013 - 2021 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 4 of 4 www.netacad.com Step 2: Examine the ARP table on Router1. a. Switch to Realtime mode. Click Router1 and then the CLI tab. b. Enter privileged EXEC mode and then the show mac-address-table command. Question: How many MAC addresses are in the table? Why? Type your answers here. c. Enter the show arp command. Questions: Is there an entry for 172.16.31.2 ? Type your answers here. What happens to the first ping in a situation where the router responds to the ARP request? Type your answers here. End of document

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

PT Lab 9.2.9 - Examine the ARP Table Submit screenshot of Overall Feedback tab

© 2019 - 2021 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 1 of 5 www.netacad.com Packet Tracer – IPv6 Neighbor Discovery Addressing Table Device Interface IPv6 Address / Prefix Default Gateway RTA G0/0/0 2001:db8:acad:1::1/64 N/A RTA G0/0/1 2001:db8:acad:1::1/64 N/A PCA1 NIC 2001:db8:acad:1::A/64 fe80::1 PCA2 NIC 2001:db8:acad:1::B/64 fe80::1 PCB1 NIC 2001:db8:acad:2::A/64 fe80::1 Objectives Part 1: IPv6 Neighbor Discovery Local Network Part 2: IPv6 Neighbor Discovery Remote Network Background In order for a device to communicate with another device, the MAC address of the destination must be known. With IPv6, a process called Neighbor Discovery using NDP or ND protocol is responsible for determining the destination MAC address. You will gather PDU information in simulation mode to better understand the process. There is no Packet Tracer scoring for this activity. Instructions Part 1: IPv6 Neighbor Discovery Local Network In Part 1 of this activity, you will obtain the MAC address of a destination device on the same network. Step 1: Check the router for any neighbors that it discovered. a. Click the RTA Router. Select the CLI tab and issue the command show ipv6 neighbors from the privileged exec mode. If there are any entries displayed, remove them using the command clear ipv6 neighbors . b. Click PCA1 , select the Desktop tab and click the Command Prompt icon. Step 2: Switch to Simulation Mode to capture events. c. Click the Simulation button in the lower right corner of the Packet Tracer Topology window. d. Click the Show All/None button in the lower left part of the Simulation Panel. Make certain Event List Filters – Visible Events displays None . e. From the command prompt on PCA1 , issue the command ping – n 1 2001:db8:acad:1::b . This will start the process of pinging PCA2 . f. Click the Play Capture Forward button, which is displayed as an arrow pointing to the right with a vertical bar within the Play Controls box. The status bar above the Play Controls should read Captured to 150. (The exact number may vary.)

Packet Tracer – IPv6 Neighbor Discovery © 2019 - 2021 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 2 of 5 www.netacad.com g. Click the Edit Filters button. Select the IPv6 tab at the top and check the boxes for ICMPv6 and NDP . Click the red X in the upper right of the Edit ACL Filters window. The captured events should now be listed. You should have approximately 12 entries in the window. Question: Why are ND PDUs present? Type your answers here. h. Click the square in the Type column for the first event, which should be ICMPv6 . Question: Because the message starts with this event there is only an Outbound PDU. Under the OSI Model tab, what is the Message Type listed for ICMPv6? Type your answers here. Notice there is no Layer 2 addressing. Click the Next Layer >> button to get an explanation about the ND (Neighbor Discovery) process. i. Click the square next to the next event in the Simulation Panel. It should be at device PCA1 and the type should be NDP. Questions: What changed in the Layer 3 addressing? Type your answers here. What Layer 2 addresses are shown? Type your answers here. When a host does not know the MAC address of the destination, a special multicast MAC address is used by IPv6 Neighbor Discovery as the Layer 2 destination address. j. Select the first NDP event at SwitchA. Question: Is there any difference between the In Layers and Out Layers for Layer 2? Type your answers here. k. Select the first NDP event at PCA2 . Click the Outbound PDU Details. Question: What addresses are displayed for the following? Note : The addresses in the fields may be wrapped, adjust the size of the PDU window to make address information easier to read. Ethernet II DEST ADDR: Type your answers here. Ethernet II SRC ADDR: Type your answers here. IPv6 SRC IP: Type your answers here. IPv6 DST IP:

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

Packet Tracer – IPv6 Neighbor Discovery © 2019 - 2021 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 3 of 5 www.netacad.com Type your answers here. Question: l. Select the first NDP event at RTA . Why are there no Out Layers? Type your answers here. m. Click through the Next Layer >> button until the end and read steps 4 through 7 for further explanation. n. Click the next ICMPv6 event at PCA1 . Question: Does PCA1 now have all of the necessary information to communicate with PCA2? Type your answers here. o. Click the last ICMPv6 event at PCA1 . Notice this is the last communication listed. Question: What is the ICMPv6 Echo Message Type? Type your answers here. p. Click the Reset Simulation button in the Simulation Panel. From the command prompt of PCA1 repeat the ping to PCA2. (Hint: you should be able to press the up arrow to bring the previous command back.) q. Click the Capture Forward button 5 times to complete the ping process. Question: Why weren’t there any NDP events? Type your answers here. Part 2: IPv6 Neighbor Discovery Remote Network In Part 2 of this activity, you will perform steps that are similar to those in Part 1, except in this case, the destination host is on another LAN. Observe how the Neighbor Discovery process differs from the process you observed in Part 1. Pay close attention to some of the additional addressing steps that take place when a device communicates with a device that is on a different network. Make sure to click the Reset Simulation button to clear out the previous events. Step 1: Capture events for remote communication. a. Display and clear any entries in the IPv6 neighbor device table as was done in Part I. b. Switch to simulation mode. Click the Show All/None button in the lower left part of the Simulation Panel. Make certain the Event List Filters – Visible Events displays None. c. From the command prompt on PCA1 issue the command ping – n 1 2001:db8:acad:2::a to ping host PCB1. d. Click the Play Capture Forward button which is displayed as an arrow pointing to the right with a vertical bar within the Play Controls box. The status bar above the Play Controls should read Captured to 150. (The exact number may vary.) e. Click the Edit Filters button. Select the IPv6 tab at the top and check the boxes for ICMPv6 and NDP . Click the red X in the upper right of the Edit ACL Filters window. All of the previous events should now be listed. You should notice there are considerably more entries listed this time. f. Click the square in the Type Column for the first event, which should be ICMPv6 . Because the message starts with this event, there is only an Outbound PDU. Notice that it is missing the Layer 2 information as it did in the previous scenario.

Packet Tracer – IPv6 Neighbor Discovery © 2019 - 2021 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 4 of 5 www.netacad.com g. Click the first NDP event At Device PCA1 . Question: What address is being used for the Src IP in the inbound PDU? Type your answers here. IPv6 Neighbor Discovery will determine the next destination to forward the ICMPv6 message. h. Click the second ICMPv6 event for PCA1 . PCA1 now has enough information to create an ICMPv6 echo request. Question: What MAC address is being used for the destination MAC? Type your answers here. i. Click the next ICMPv6 event at device RTA . Notice that the outbound PDU from RTA lacks the destination Layer 2 address, This means that RTA once again has to perform a Neighbor Discovery for the interface that has the 2001:db8:acad :2:: network because it doesn’t know the MAC addresses of the devices on the G0/0/1 LAN. j. Skip down to the first ICMPv6 event for device PCB1 . Question: What is missing in the outbound Layer 2 information? Type your answers here. k. The next few NDP events are associating the remaining IPv6 addresses to MAC addresses. The previous NDP events associated MAC addresses with Link Local addresses. l. Skip to the last set of ICMPv6 events and notice that all of the addresses have been learned. The required information is now known, so PCB1 can send echo reply messages to PCA1. m. Click the Reset Simulation button in the Simulation Panel. From the command prompt of PCA1 repeat the command to ping PCB1. n. Click the Capture Forward button nine times to complete the ping process. Question: Were there any NDP events? Type your answers here. o. Click the only PCB1 event in the new list. Questions: What does the destination MAC address correspond to? Type your answers here. Why is PCB1 using the router interface MAC address to make its ICMP PDUs? Type your answers here. Step 2: Examine router outputs. a. Return to Realtime mode.

Packet Tracer – IPv6 Neighbor Discovery © 2019 - 2021 Cisco and/or its affiliates. All rights reserved. Cisco Public Page 5 of 5 www.netacad.com b. Click RTA and select the CLI tab. At the router prompt enter the command show ipv6 neighbors . Questions: How many addresses are listed? Type your answers here. What devices are these addresses associated with? Type your answers here. Are there any entries for PCA2 listed (why or why not)? Type your answers here. Ping PCA2 from the router. c. Issue the show ipv6 neighbors command. Question: Are there entries for PCA2? Type your answers here. Reflection Questions 1. When does a device require the IPv6 Neighbor Discovery process? Type your answers here. 2. How does a router help to minimize the amount of IPv6 Neighbor Discovery traffic on a network? Type your answers here. How does IPv6 minimize the impact of the ND process on network hosts? Type your answers here. 3. How does the Neighbor Discovery process differ when a destination host is on the same LAN and when it is on a remote LAN? Type your answers here. End of document

Your preview ends here

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