CCNA Discovery Working at a Small-to-Medium Business or ISP

Lab 1.2.3 Mapping ISP Connectivity Using Traceroute

Objectives

Run the Windows tracert utility from a local host computer to a website on a different continent. Interpret the traceroute output to determine which ISPs the packets passed through on their way from the local host to the destination website. Draw a diagram of the traceroute path, showing the routers and ISP clouds passed through from the local host to the destination website, including IP addresses for each device.

Background / Preparation
In this activity, you will use the Windows tracert utility to map Internet connectivity between your local ISP and the other ISPs that it uses to provide global Internet access. You will also map connectivity to the following major Regional Internet Registries (RIRs). However, your instructor may choose different destination websites.

AfriNIC (African Network Information Centre) Africa Region APNIC (Asia Pacific Network Information Centre) Asia/Pacific Region ARIN (American Registry for Internet Numbers) North America Region LACNIC (Regional Latin-American and Caribbean IP Address Registry) Latin America and some Caribbean Islands RIPE NCC (Rseaux IP Europens) Europe, the Middle East, and Central Asia

This activity can be done individually, in pairs, or in teams. It can be done as an in-class activity or as a homework assignment, depending on whether the classroom computers have access to the Internet. The following resources are required: Host computer with the Windows operating system Access to the command prompt Internet connection Routes Traced worksheet for each destination URL. The worksheet is attached to this lab. Each student completes their own worksheets and gives them to the instructor. Global Connectivity Map, which is attached at the end of this lab Access to the PC command prompt
Page 1 of 17

All contents are Copyright 19922008 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Step 1: Run the tracert utility from a host computer

a. Verify that the host computer has a connection to the Internet. b. Open a Command Prompt window by clicking Start > Run and typing cmd. alternatively, you may click Start > All programs > Accessories >
Command Prompt.

c.

At the prompt, type tracert and your first destination website. The output should look similar to the following:

Save the tracert output in a text file as follows:

1) Right-click the title bar of the Command Prompt window and choose Edit > Select All. 2) Right-click the title bar of the Command Prompt window again and choose Edit > Copy. 3) Open the Windows Notepad program: Start > All Programs > Accessories > Notepad. 4) To paste the output into Notepad, choose Edit > Paste. 5) Choose File > Save As and save the Notepad file to your desktop as tracert1.txt. d. Run tracert for each destination website and save the output in sequentially numbered files.

All contents are Copyright 19922008 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 2 of 17

e. Run tracert from a different computer network, for example, from the public library or from a friends computer that accesses the Internet using a
different ISP (for instance, cable instead of DSL). Save a copy of that output in Notepad and print it out for later reference

Step 2: Interpret tracert outputs to determine ISP connectivity Routes traced may go through many hops and a number of different ISPs depending on the size of your ISP and the location of the source and destination hosts. In the example output shown below, the tracert packets travel from the source PC to the local router default gateway to the ISPs Point of Presence (POP) router and then to an Internet Exchange Point (IXP). From there they pass through two Tier 2 ISP routers and then though several Tier 1 ISP routers as they move across the Internet backbone. When they leave the Tier 1 ISPs backbone, they move through another Tier 2 ISP on the way to the destination server at www.ripe.net.

a. Open the first traceroute output file and answer the following questions. 1) What is the IP address of your local POP router? 66.153.196.240 2) How many hops did the traceroute packet take on its journey from the host computer to the destination? 17 3) How many different ISPs did the traceroute packet pass through on its journey from the host computer to the destination? 8 4) List the IP addresses and URLs of all the devices in the traceroute output in the order that they appear on the Routes Traced worksheet. 5) In the Network Owner column of the worksheet, identify which ISP owns each router. If the router belongs to your LAN, write LAN. The last two parts of the URL indicates the ISP name. For example, a router that has sprint.net in its URL belongs to the network of an ISP called Sprint. 6) Did the traceroute pass through an unidentified router between two ISPs? This might be an IXP. Run the whois command utility or whois function of a visual traceroute program to identify ownership of that router. Alternatively, go to http://www.arin.net/whois to determine to whom the IP is assigned. b. Complete the worksheet using the traceroute output file for each of the other destination URLs. c. Compare your results from the different traceroute output files. Did your ISP connect to different ISPs to reach different destinations? __________________________________________________________________________

All contents are Copyright 19922008 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 3 of 17

d. If you ran a traceroute from a different computer network, check the output for that traceroute file as well. Was the number of hops different to reach the same destination from different local ISPs? Which ISP was able to reach the destination in fewer hops? __________________________________________________________________________

Step 3: Map the connectivity of your ISP

e. For each traceroute output, draw a diagram on a separate sheet of paper showing how your local ISP interconnects with other ISPs to reach the destination URL, as follows: 1) Show all of the devices in sequence from the LAN router to the destination website server. Label all of the devices with their IP addresses. 2) Draw a box around the local POP router that you identified, and label the box POP. 3) Draw an ISP cloud around all the routers that belong to each ISP, and label the cloud with the ISP name. 4) Draw a box around any IXP routers that you identified, and label the box IXP. f. Use the Global Connectivity Map to create a combined drawing showing only ISP clouds and IXP boxes.

Worksheet for Routes Traced

Destination URL: http://www.afrinic.net/ Router IP Address 66.153.207.66 66.153.207.98 Router URL (if any) 66.207-core01-et.8.2-mi.sccoast.net 98.207-core02-gi.16.1.sccoast.net LAN LAN
Page 4 of 17

Total Number of Hops: _18__________________ Network Owner (LAN, Name of ISP or IXP)

All contents are Copyright 19922008 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Router IP Address 4.71.124.85 4.69.132.162 4.69.148.106 4.69.143.214 4.69.148.49 4.69.137.65 4.69.153.142 195.50.124.34 4.69.139.105 168.209.201.82 196.26.0.101 196.37.155.180 196.216.3.132

Router URL (if any) te-4-4.car1.Charlotte1.Level3.net ae-4-4.ebr1.Atlanta2.Level3.net ae-66.ebr1.Washington12.Level3.net ae-1100.ebr2.Washington12.Level3.net IXP (LVLT-ORG-4-8) ae-41-41.ebr2.London1.Level3.net ae-59-224.csw2.London1.Level3.net IXP ae-2-52.edge3.London1.Level3.net (AFRINIC-168-209-0-0)core2b-pkltenge-0-7-0-0-126.ip.isnet.net csw4-pkl-gi1-1.ip.isnet.net fa1-0-1.ar02.jnb.afrinic.net Atlanta

Network Owner (LAN, Name of ISP or IXP) Charlotte Washington Washington Level 3 Communications, Inc. (CO) London London RIPE-CBLK3 (Amsterdan) London AFRINIC NET196- AFRINIC.net NET196- AFRINIC.net afrinic.net

Global Connectivity Map

1) 66.153.196.240 POP (SC) 2) 66.153.207.66 - SC 3) 66.153.207.98 - SC 4) 4.71.124.85 - NC 5) 4.69.132.162 - ATL 6) 4.69.148.106 - DC 7) 4.69.143.214 DC 8) 4.69.148.49 CO (IXP)
All contents are Copyright 19922008 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 5 of 17

9) 4.69.137.65 - London 10) 4.69.153.142 - London 11) 195.50.124.34 Amsterdam (IXP) 12) 4.69.139.105 - London 13) 168.209.201.82 MU 14) 196.26.0.101 MU 15) 196.37.155.180 IXP 16) 196.216.3.132 - Destination

All contents are Copyright 19922008 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 6 of 17

Step 3: Map the connectivity of your ISP

a. For each traceroute output, draw a diagram on a separate sheet of paper showing how your local ISP interconnects with other ISPs to reach the destination URL, as follows: 1) Show all of the devices in sequence from the LAN router to the destination website server. Label all of the devices with their IP addresses. 2) Draw a box around the local POP router that you identified, and label the box POP. 3) Draw an ISP cloud around all the routers that belong to each ISP, and label the cloud with the ISP name. 4) Draw a box around any IXP routers that you identified, and label the box IXP. b. Use the Global Connectivity Map to create a combined drawing showing only ISP clouds and IXP boxes.

All contents are Copyright 19922008 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 7 of 17

Worksheet for Routes Traced

Destination URL: http://www.apnic.net_ Router IP Address 66.153.207.66 66.153.207.98 4.71.124.85 4.69.132.162 4.69.148.241 4.69.134.21 4.69.132.77 4.69.148.202 4.69.148.142 4.69.153.26 4.69.152.139 4.59.0.230 66.192.244.74 203.29.135.33 202.7.162.246 203.194.59.159 203.194.59.159 202.12.29.211 Router URL (if any) 66.207-core01-et.8.2-mi.sccoast.net 98.207-core02-gi.16.1.sccoast.net te-4-4.car1.Charlotte1.Level3.net ae-4-4.ebr1.Atlanta2.Level3.net ae-63-63.ebr3.Atlanta2.Level3.net ae-7-7.ebr3.Dallas1.Level3.net ae-3-3.ebr2.LosAngeles1.Level3.net ae-6-6.ebr2.SanJose5.Level3.net ae-2-2.ebr2.SanJose1.Level3.net ae-82-82.csw3.SanJose1.Level3.net ae-41-80.car1.SanJose2.Level3.net TIMEWARNER.car1.SanJose2.Level3.net pdx1-ar4-xe-0-1-0-0.us.twtelecom.net syd-sot-ken-crt1-ge-3-1-0.tpgi.com.au 202-7-162-246.tpgi.com.au-NET-202-00-0-1 159.59.194.203.static.comindico.com.au 159.59.194.203.static.comindico.com.au matrix-proxy1.apnic.net LAN LAN Charlotte Atlanta Atlanta Dallas Los Angeles San Jose San Jose San Jose San Jose San Jose Tw telecom - CO APNIC-203 - Brisbane-AU APNIC-203- Brisbane-AU comindico- Brisbane-AU comindico- Brisbane-AU APNIC-- Brisbane-AU Total Number of Hops: 18_____________________________ Network Owner (LAN, Name of ISP or IXP)

All contents are Copyright 19922008 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 8 of 17

Global Connectivity Map

1) 66.153.196.240 POP (SC) 2) 66.153.207.66 -SC 3) 66.153.207.98 -SC 4) 4.71.124.85 NC 5) 4.69.132.162 -ATL 6) 4.69.148.241 - ATL 7) 4.69.134.21 - DALLAS 8) 4.69.132.77 Los Angeles 9) 4.69.148.202 San Jose 10) 4.69.148.142 San Jose 11) 4.69.153.26 San Jose 12) 4.69.152.139 San Jose 13) 4.59.0.230 San Jose 14) 66.192.244.74 -CO 15) 203.29.135.33 Brisbane-AU 16) 202.7.162.246 - Brisbane-AU 17) 203.194.59.159 - Brisbane-AU 18) 203.194.59.159 - Brisbane-AU 19) 202.12.29.211 - Brisbane-AU

All contents are Copyright 19922008 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 9 of 17

Step 3: Map the connectivity of your ISP

c. For each traceroute output, draw a diagram on a separate sheet of paper showing how your local ISP interconnects with other ISPs to reach the destination URL, as follows: 1) Show all of the devices in sequence from the LAN router to the destination website server. Label all of the devices with their IP addresses.

2) Draw a box around the local POP router that you identified, and label the box POP. 3) Draw an ISP cloud around all the routers that belong to each ISP, and label the cloud with the ISP name. 4) Draw a box around any IXP routers that you identified, and label the box IXP. d. Use the Global Connectivity Map to create a combined drawing showing only ISP clouds and IXP boxes.

All contents are Copyright 19922008 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 10 of 17

Worksheet for Routes Traced

Destination URL: https://www.arin.net Router IP Address 66.153.207.66 66.153.207.98 4.71.124.85 4.69.132.162 4.69.148.241 4.69.132.86 4.69.134.130 4.69.149.16 4.53.114.94 68.1.1.5 98.172.152.14 192.149.252.131
COX-COMMUNI.edge2.Washington4.Level3.net

Total Number of Hops: 13_______________________________________ Router URL (if any) Network Owner (LAN, Name of ISP or IXP) 66.207-core01-et.8.2-mi.sccoast.net 98.207-core02-gi.16.1.sccoast.net te-4-4.car1.Charlotte1.Level3.net ae-4-4.ebr1.Atlanta2.Level3.net ae-63-63.ebr3.Atlanta2.Level3.net ae-2-2.ebr1.Washington1.Level3.net ae-61-61.csw1.Washington1.Level3.net ae-1-60.edge2.Washington4.Level3.net COX-COMMUNI.edge2.Washington4.Level3.net mrfddsrj01-ae0.0.rd.dc.cox.net wsip-98-172-152-14.dc.dc.cox.net host-252-131.arin.net

All contents are Copyright 19922008 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 11 of 17

Global Connectivity Map

Worksheet for Routes Traced

Destination URL: www.lacnic.net Total Number of Hops: 22____________________________

All contents are Copyright 19922008 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 12 of 17

Router IP Address 66.153.207.66 66.153.207.98 4.71.124.85 4.69.132.162 4.69.148.106 4.69.143.214 4.69.148.49 4.69.137.69 4.69.153.138 4.69.139.106 212.187.160.226 94.142.126.61 94.142.122.210 94.142.123.90 94.142.118.86 201.48.46.34 201.48.44.93 201.48.44.93 200.160.0.166 200.160.0.249 200.160.0.249 200.160.0.212 200.3.14.10

Router URL (if any)

Network Owner (LAN, Name of ISP or IXP) 66.207-core01-et.8.2-mi.sccoast.net 98.207-core02-gi.16.1.sccoast.net te-4-4.car1.Charlotte1.Level3.net ae-4-4.ebr1.Atlanta2.Level3.net ae-6-6.ebr1.Washington12.Level3.net ae-1-100.ebr2.Washington12.Level3.net IXP ae-42-42.ebr2.London1.Level3.net ae-58-223.csw2.London1.Level3.net ae-2-52.edge4.London1.Level3.net

TELEFONICA.edge4.London1.Level3.net

TELEFONICA.edge4.London1.Level3.net Xe-2-0-1-0-grtnycpt2.red.telefonica-wholesale.net Xe2-0-0-0-grtmiabr3.red.telefonica-wholesale.net Xe2-1-0-0-grtsaosi3.red.telefonica-wholesale.net Xe3-0-2-0-grtsaosi2.red.telefonica-wholesale.net xe-1-2-0-0.core-b.spo511.ctbc.com.br xe-0-1-0-0.edge-c.spo511.ctbc.com.br xe-0-1-0-0.edge-c.spo511.ctbc.com.br xe-5-0-1-0.core1.nu.registro.br

ae0-0.ar3.nu.registro.br ae0-0.ar3.nu.registro.br gw01.lacnic.registro.br

ae0-0.ar3.nu.registro.br ae0-0.ar3.nu.registro.br gw01.lacnic.registro.br www.lacnic.net

All contents are Copyright 19922008 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 13 of 17

Global Connectivity Map

Worksheet for Routes Traced

Destination URL: http://www.ripe.net Total Number of Hops: 12_________________

All contents are Copyright 19922008 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 14 of 17

Router IP Address 66.153.207.66 66.153.207.98 4.71.124.85 4.69.132.162 4.69.148.106 4.69.143.214 4.69.148.49 4.69.137.65 4.69.143.77 4.69.153.214 ae-29- 4.69.139.178 195.69.144.68 reports: Destination net unreachable.

Router URL (if any)

Network Owner (LAN, Name of ISP or IXP) 66.207-core01-et.8.2-mi.sccoast.net 98.207-core02-gi.16.1.sccoast.net te-4-4.car1.Charlotte1.Level3.net ae-4-4.ebr1.Atlanta2.Level3.net ae-6-6.ebr1.Washington12.Level3.net ae-1-100.ebr2.Washington12.Level3.net IXP ae-41-41.ebr2.London1.Level3.net ae-47-47.ebr2.Amsterdam1.Level3.net ae-59-224.csw2.Amsterdam1.Level3.net 52.sar1.Amsterdam1.Level3.net gw.amsix.nikrtr.ripe.net

All contents are Copyright 19922008 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 15 of 17

Global Connectivity Map

Global Connectivity Map

All contents are Copyright 19922008 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 16 of 17

All contents are Copyright 19922008 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information.

Page 17 of 17