laborotory workbook 2016/17€¦ · web viewby the end of this course, students will be able to...

CCE 1030Computer Networking

Laboratory Workbook

Autumn/Winter term – Sept start (24 week module)

2019/20

Student Name:…………………………….

Student ID:………………………..

Usama ArusiFaculty of Science and Technology

of 210

Disclaimer

This laboratory workbook is designed to provide practical exercises for CCE1030 Computer Networks. Every effort has been made to make this laboratory workbook as complete and as true and accurate as possible, but no warranty or fitness is implied.

The author has based its content on material provided by Cisco Cert Guide, and shall have neither liability nor responsibility to any person or entity with respect to any loss or damages arising from the information contained in this laboratory workbook.

The opinions expressed in this book belong to the author and are not necessarily those of Cisco Systems, Inc.

of 210

ContentsDisclaimer..................................................................................................................................2Introduction..............................................................................................................................14Lab 1: My First Packet Tracer Lab..........................................................................................16

Introduction..........................................................................................................................16Lab Objectives.....................................................................................................................16Important Terminology........................................................................................................16Task 1: Viewing Help and Tutorials....................................................................................17Task 2: Creating a First Network.........................................................................................18Task 3: Sending Simple Test Messages in Realtime Mode.................................................19Task 4: Establishing a Web Server Connection Using the PC’s Web Browser...................20Task 5: Capturing Events and Viewing Animations in Simulation Mode...........................21Task 6: Looking Inside Packets in Simulation Mode..........................................................22Task 7: Viewing Device Tables and Resetting the Network...............................................23Task 8: Reviewing Your New Skills....................................................................................24

Lab 2: Investigating the TCP/IP and OSI Models in Action (Packet Tracer)..........................25Objectives.............................................................................................................................25Background..........................................................................................................................25Task 1: Examine HTTP Web Traffic...............................................................................25

Step 1: Switch from Realtime to Simulation mode......................................................25Step 2: Generate web (HTTP) traffic...........................................................................26Step 3: Explore the contents of the HTTP packet........................................................26

Task 2: Display Elements of the TCP/IP Protocol Suite......................................................28Step 1: View Additional Events.......................................................................................28Challenge..........................................................................................................................29

Lab 3: Examining Packets (Packet Tracer)..............................................................................30Learning Objectives.............................................................................................................30Background..........................................................................................................................31Task 1: Complete the Topology...........................................................................................31Task 2: Add Simple PDUs in Realtime Mode.....................................................................31Task 3: Analyse PDUs in Simulation Mode (Packet Tracing)............................................31Task 4: Experiment with the Model of the Standard Lab Setup..........................................32Reflection.............................................................................................................................32

Lab 4: Analysing the Application and Transport Layers (Packet Tracer)...............................34Learning Objectives.............................................................................................................34Background..........................................................................................................................35Task 1: Repair and Test the Topology.................................................................................35Task 2: Explore How DNS, UDP, HTTP, and TCP Work Together...................................36Reflection.............................................................................................................................36

Lab 5: Connecting to a Cisco Device via Console (Hardware)...............................................38Lab Prerequisites..................................................................................................................38Learning Objectives.............................................................................................................38Background..........................................................................................................................38Lab Instruction.....................................................................................................................39

Lab 6: Topology Orientation and Building a Small Network (Packet Tracer)........................41Learning Objectives.............................................................................................................41Background..........................................................................................................................41Scenario................................................................................................................................42Section 1...............................................................................................................................42

of 210

Task 1: Create a Peer-to-Peer Network................................................................................42Task 2: Identify the Cables used in a Network....................................................................42Task 3: Cable the Peer-to-peer Network..............................................................................42

Step 1: Connect two workstations....................................................................................42Step 2: Apply a Layer 3 address to the workstations.......................................................42Step 3: Verify connectivity..............................................................................................43

Section 2...............................................................................................................................45Task 4: Connect Your Workstations to the Switch..............................................................45

Step 1: Connect workstation to a switch..........................................................................45Step 2: Repeat this process for each workstation on your network.................................45Step 3: Verify connectivity..............................................................................................45

Task 5: Reflection................................................................................................................46Lab 7: Topology Orientation and Building a Small Network (Hardware Equipment)............47

Learning Objectives.............................................................................................................47Background..........................................................................................................................47Scenario................................................................................................................................48Task 1: Create a Peer-to-Peer Network................................................................................48

Step 1: Obtain equipment and resources for the lab........................................................48Task 2: Identify the Cables used in a Network....................................................................48Task 3: Cable the Peer-to-peer Network..............................................................................48

Step 1: Connect two workstations....................................................................................48Step 2: Apply a Layer 3 address to the workstations.......................................................48Step 3: Verify connectivity..............................................................................................50

Task 4: Connect Your Workstations to the Classroom Lab Switch.....................................51Step 1: Connect workstation to switch.............................................................................51Step 2: Repeat this process for each workstation on your network.................................52Step 3: Verify connectivity..............................................................................................52Step 4: Share a document between PCs...........................................................................52

Task 5: Reflection................................................................................................................52Lab 8: Configure Initial Router Settings (Packet Tracer)........................................................54

Objectives.............................................................................................................................54Background..........................................................................................................................54Task 1: Verify the Default Router Configuration................................................................54

Step 1: Establish a console connection to R1...................................................................54Step 2: Enter privileged mode and examine the current configuration............................54

Task 2: Configure and Verify the Initial Router Configuration...........................................55Step 1: Configure the initial settings on R1.....................................................................55Step 2: Verify the initial settings on R1...........................................................................56

Task 3: Save the Running Configuration File......................................................................57Step 1: Save the configuration file to NVRAM...............................................................57

Lab 9: Configure Initial Router Settings (Hardware Equipment)............................................58Objectives.............................................................................................................................58Background..........................................................................................................................58Equipment............................................................................................................................58Task 1: Connect to the Router & Verify the Default Router Configuration........................58

Step 1: Establish a console connection to router..............................................................58Step 2: Enter privileged mode and examine the current configuration............................58

Task 2: Configure and Verify the Initial Router Configuration...........................................59Step 1: Configure the initial settings on R1.....................................................................59Step 2: Verify the initial settings on R1...........................................................................60

of 210

Lab 10: Cabling a Network and Basic Router Configuration (Packet Tracer)........................61Topology Diagram..............................................................................................................61Addressing Table................................................................................................................61Learning Objectives.............................................................................................................61Scenario................................................................................................................................61Task 1: Cable the Ethernet Links of the Network................................................................62

Step 1: Connect the R1 Router to the S1 Switch.............................................................62Step 2: Connect PC1 to the S1 Switch.............................................................................62Step 3: Connect PC2 to the R2 Router.............................................................................62

Task 2: Cable the Serial Link between R1 and R2 Routers.................................................63Task 3: Establish a connection to the R1 Router.................................................................63Task 4: Understand Command Line Basics.........................................................................63

Step 1: Enter privileged EXEC mode..............................................................................63Step 2: Enter an incorrect command and observe the router response............................63Step 3: Correct the previous command............................................................................64Step 4: Return to privileged EXEC mode with the exit command..................................64Step 5: Examine the commands that are available for privileged EXEC mode...............64Step 6: View output..........................................................................................................65Step 7: Exit privileged EXEC mode with the exit command...........................................65Step 8: Press the Enter key to enter user EXEC mode.....................................................65Step 9: Type an abbreviated IOS command.....................................................................65Step 10: Press the Tab key after an abbreviated command to use auto-complete...........66Step 11: Enter IOS commands in the correct mode.........................................................66

Task 5: Perform Basic Configuration of Router R1.............................................................66Step 1: Establish a HyperTerminal session to router R1..................................................66Step 2: Enter privileged EXEC mode..............................................................................66Step 3: Enter global configuration mode.........................................................................66Step 4: Configure the router name as R1.........................................................................67Step 5: Disable DNS lookup with the no ip domain-lookup command...........................67Step 6: Configure an EXEC mode password...................................................................67Step 7: Remove the enable password...............................................................................67Step 8: Configure a message-of-the-day banner using the banner motd command.........68Step 9: Configure the console password on the router.....................................................68Step 10: Configure the password for the virtual terminal lines.......................................68Step 11: Configure the FastEthernet 0/0 interface with the IP address 192.168.1.1/24.. 68Step 12: Use the description command to provide a description for this interface..........69Step 13: Configure the Serial0/0/0 interface with the IP address 192.168.2.1/24...........69Step 14: Use the description command to provide a description for this interface..........69Step 15: Use the end command to return to privileged EXEC mode...............................69

Task 6: Perform Basic Configuration of Router R2.............................................................70Step 1: For R2, repeat Steps 1 through 10 from Task 5...................................................70Step 2: Configure the Serial 0/0/0 interface with the IP address 192.168.2.2/24............70Step 3: Use the description command to provide a description for this interface............70Step 4: Configure the FastEthernet 0/0 interface with the IP address 192.168.3.1/24.. . .70Step 5: Use the description command to provide a description for this interface............70Step 6: Use the end command to return to privileged EXEC mode.................................70

Task 7: Configure IP Addressing on the Host PCs..............................................................71Step 1: Configure the host PC1........................................................................................71Step 2: Configure the host PC2........................................................................................71

Task 8: Examine Router show Commands..........................................................................71

of 210

Step 1: Examine the show running-config command......................................................71Step 2: Examine the show startup-config command........................................................72Step 3: Examine the show interfaces command...............................................................74Step 4: Examine the show version command..................................................................74Step 5: Examine the show ip interface brief command....................................................75

Task 9: Using ping...............................................................................................................76Step 1: Use the ping command to test connectivity between the R1 router and PC1......76Step 2: Repeat the ping from R1 to PC1..........................................................................76Step 3: Send an extended ping from R1 to PC1...............................................................76Step 4: Send a ping from PC1 to R1................................................................................77Step 5: Send an extended ping from PC1 to R1...............................................................77

Task 10: Using Traceroute...................................................................................................77Step 1: Use the traceroute command at the R1 privileged EXEC prompt to discover the path that a packet will take from the R1 router to PC1....................................................78Step 2: Use the tracert command at the Windows command prompt to discover the path that a packet will take from the R1 router to PC1............................................................78

Lab 11: Cabling a Network and Basic Router Configuration (Hardware Equipment)............79Topology Diagram..............................................................................................................79Addressing Table................................................................................................................79Learning Objectives.............................................................................................................79Scenario................................................................................................................................79Task 1: Cable the Ethernet Links of the Network................................................................80

Step 1: Connect the R1 Router to the S1 Switch.............................................................80Step 2: Connect PC1 to the S1 Switch.............................................................................80Step 3: Connect PC2 to the R2 Router.............................................................................80

Task 2: Cable the Serial Link between R1 and R2 Routers.................................................80Step 1: Create a null serial cable to connect the R1 router to the R2 router....................81Step 2: Connect the DCE end of the null serial cable to the Serial 0/0/0 interface of the R1 router, and the DTE end of the null serial cable to the Serial 0/0/0 interface of the R2 router................................................................................................................................81

Task 3: Establish a Console connection to R1 Router.........................................................81Step 1: Examine the router and locate the RJ-45 connector labeled Console..................82Step 2: Examine PC1 and locate a 9-pin male connector serial port...............................82Step 3: Locate the console cable......................................................................................82Step 4: Connect the console cable to the router and PC..................................................82Step 5: Test router connection..........................................................................................82

Task 4: Erase and Reload the Routers..................................................................................82Step 1: Using the HyperTerminal session established in Task 3, enter privileged EXEC mode on R1......................................................................................................................82Step 2: Erase the configuration........................................................................................82Step 3: Reload the configuration......................................................................................83Step 4: Establish a HyperTerminal Session to R2...........................................................83

Task 5: Perform Basic Configuration of Router R1.............................................................83Step 1: Establish a HyperTerminal session to router R1..................................................83Step 2: Enter privileged EXEC mode..............................................................................83Step 3: Enter global configuration mode.........................................................................83Step 4: Configure the router name as R1.........................................................................83Step 5: Disable DNS lookup with the no ip domain-lookup command...........................84Step 6: Configure an EXEC mode password...................................................................84Step 7: Remove the enable password...............................................................................84

of 210

Step 8: Configure a message-of-the-day banner using the banner motd command.........84Step 9: Configure the console password on the router.....................................................85Step 10: Configure the password for the virtual terminal lines.......................................85Step 11: Configure the FastEthernet 0/0 interface with the IP address 192.168.1.1/24.. 85Step 12: Use the description command to provide a description for this interface..........85Step 13: Configure the Serial0/0/0 interface with the IP address 192.168.2.1/24...........85Step 14: Use the description command to provide a description for this interface..........86Step 15: Use the end command to return to privileged EXEC mode...............................86

Task 6: Perform Basic Configuration of Router R2.............................................................86Step 1: For R2, repeat Steps 1 through 10 from Task 6...................................................86Step 2: Configure the Serial 0/0/0 interface with the IP address 192.168.2.2/24............86Step 3: Use the description command to provide a description for this interface............87Step 4: Configure the FastEthernet 0/0 interface with the IP address 192.168.3.1/24.. . .87Step 5: Use the description command to provide a description for this interface............87Step 6: Use the end command to return to privileged EXEC mode.................................87

Task 7: Configure IP Addressing on the Host PCs..............................................................87Step 1: Configure the host PC1........................................................................................87Step 2: Configure the host PC2........................................................................................87

Task 8: Examine Router Show Commands.........................................................................87Step 1: Examine the show running-config command......................................................88Step 2: Examine the show startup-config command........................................................88Step 3: Examine the show interfaces command...............................................................88Step 4: Examine the show version command..................................................................89Step 5: Examine the show ip interface brief command....................................................89

Task 9: Using ping...............................................................................................................89Step 1: Use the ping command to test connectivity between the R1 router and PC1......89Step 2: Repeat the ping from R1 to PC1..........................................................................90Step 3: Send an extended ping from R1 to PC1...............................................................90Step 4: Send a ping from PC1 to R1................................................................................90Step 5: Send an extended ping from PC1 to R1...............................................................90

Task 10: Using Traceroute...................................................................................................91Step 1: Use the traceroute command at the R1 privileged EXEC prompt to discover the path that a packet will take from the R1 router to PC1....................................................91Step 2: Use the tracert command at the Windows command prompt to discover the path that a packet will take from the R1 router to PC1............................................................91

Task 11: Create a start.txt File.............................................................................................91Step 1: View the running configuration of the router using the show running-config command..........................................................................................................................92Step 2: Copy the command output...................................................................................92Step 3: Paste output in Notepad.......................................................................................92Step 4: Edit commands.....................................................................................................92Step 5: Save the open file in Notepad to start.txt.............................................................93

Task 12: Load the start.txt File onto R1 Router...................................................................93Step 1: Erase the current startup configuration of R1......................................................93Step 2: When the prompt returns, issue the reload command..........................................93Step 3: Enter global configuration mode.........................................................................94Step 4: Copy the commands.............................................................................................94Step 5: From the HyperTerminal Edit menu, choose Paste to Host.................................94Step 6: Verify the running configuration.........................................................................94

Lab 12: IPv4 Address Subnetting (part 1)................................................................................95

of 210

Learning Objectives.............................................................................................................95Background..........................................................................................................................95Scenario................................................................................................................................95Task 1: For a given IP address, Determine Network Information.......................................95

Step 1: Translate Host IP address and network mask into binary notation......................95Step 2: Determine the network address............................................................................95Step 3: Determine the broadcast address for the network address...................................96

Task 2: Challenge.................................................................................................................97Lab 13: IPv4 Address Subnetting (part 2)................................................................................99

Learning Objectives.............................................................................................................99Background..........................................................................................................................99Scenario..............................................................................................................................100Task 1: For a Given IP Address and Subnet Mask, Determine Subnet Information.........100

Step 1: Translate host IP address and subnet mask into binary notation.......................100Step 2: Determine the network (or subnet) where this host address belongs.................100Step 3: Determine which bits in the address contain network information and which contain host information................................................................................................101Step 4: Determine the bit ranges for subnets and hosts.................................................101Step 5: Determine the range of host addresses available on this subnet and the broadcast address on this subnet.....................................................................................................102Step 6: Determine the number of subnets......................................................................103Step 7: Determine the number usable hosts per subnet..................................................103Step 8: Final Answers....................................................................................................104

Task 2: Challenge...............................................................................................................104Lab 14: Troubleshooting a Small Network (Packet Tracer)..................................................107

Learning Objectives...........................................................................................................107Scenario..............................................................................................................................107Task 1: Examine the Logical LAN Topology....................................................................107Task 2: Cable the Routers..................................................................................................109Task 3: Configure the Host Computers..............................................................................109

Step 1: Configure host computers..................................................................................109Task 4: Load the Router with the Supplied Scripts............................................................109Task 5: Identify Connectivity Problems............................................................................110

Step 1: Use the ping command to test network connectivity.........................................110Task 6: Troubleshoot Network Connections......................................................................110

Step 1: Begin troubleshooting at the host connected to the BRANCH router...............110Step 2: Examine the router to find possible configuration errors..................................110Step 3: Use the necessary commands to correct the router configuration.....................111Step 4: View a summary of the status information........................................................111Step 5: Verify the logical configuration.........................................................................111

Lab 15: Configuring and Testing the Lab Network (Packet Tracer).....................................112Topology Diagram................................................................................................................112

Learning Objectives...........................................................................................................112 Build, test, and configure the entire lab network...........................................................112 Integrate skills from throughout the course...................................................................112 Analyse the events involved in requesting a web page (DNS, ARP, HTTP, TCP, IP, Ethernet, HDLC)....................................................................................................................112 Analyse the events involved in tracing the route to the web server (DNS, UDP, ARP, ICMP, IP, Ethernet, HDLC)...................................................................................................112

Background........................................................................................................................113

of 210

Task 1: Plan........................................................................................................................113Task 2: Build and Configure the Network.........................................................................114Task 3: Test and Analyse...................................................................................................115Task 4: Reflection - Putting it All Together.......................................................................116

Lab 16: Subnetting (Packet Tracer).......................................................................................117Learning Objectives...........................................................................................................117Scenario..............................................................................................................................118Task 1: Examine the Network Requirements.....................................................................118Task 2: Design an IP Addressing Scheme.........................................................................118

Step 1: Subnet the 192.168.9.0 network into the appropriate number of subnets..........118Step 2: Assign the subnets to the network shown in the Topology Diagram................119

Task 3: Assign IP Addresses to the Network Devices.......................................................120Step 1: Assign addresses to the HQ router.....................................................................120Step 2: Assign addresses to the BRANCH1 router........................................................120Step 3: Assign addresses to the BRANCH2 router........................................................120Step 4: Assign addresses to the host PCs.......................................................................120

Task 4: Test the Network Design.......................................................................................121Task 5: Reflection..............................................................................................................121

Lab 17: VLSM Variable-Length Subnet Mask......................................................................122What is VLSM...................................................................................................................123The Box Method................................................................................................................123VLSM Addressing Part 1...................................................................................................126

Problem 1 (Example).....................................................................................................126Problem 2 (Example).........................................................................................................127Problem 3...........................................................................................................................128Problem 4...........................................................................................................................129Problem 5...........................................................................................................................130Problem 6...........................................................................................................................131Problem 7...........................................................................................................................132Problem 8...........................................................................................................................133

VLSM Addressing Part 2.......................................................................................................135Problem 9 (Example).........................................................................................................135Problem 10 (Example).......................................................................................................136Problem 11.........................................................................................................................136Problem 12.........................................................................................................................137Problem 13.........................................................................................................................137Problem 14.........................................................................................................................138Problem 15.........................................................................................................................139Problem 16.........................................................................................................................139

Lab 18: Basic VLSM Calculation and Addressing Design....................................................143Learning Objectives...........................................................................................................143Scenario..............................................................................................................................144Task 1: Examine the Network Requirements.....................................................................144Task 2: Design an IP Addressing Scheme.........................................................................145

Step 1: Determine the subnet information for the largest network segment or segments.........................................................................................................................................145Step 2: Assign subnets to HQ LANs..............................................................................145Step 3: Determine the subnet information for the next largest network segment or segments.........................................................................................................................145Step 4: Assign subnet to BRANCH1 LANs..................................................................146

of 210

Step 5: Determine the subnet information for the next largest network segment or segments.........................................................................................................................146Step 6: Assign subnets to BRANCH2 LANs.................................................................146Step 7: Determine the subnet information for the links between the routers.................147Step 8: Assign subnets to links.......................................................................................147

Task 3: Assign IP Addresses to the Network Devices.......................................................148Step 1: Assign addresses to the HQ router.....................................................................148Step 2: Assign addresses to the Branch1 router.............................................................148Step 3: Assign addresses to the Branch2 router.............................................................149

Lab 19: Basic Static Route Configuration (Hardware Equipment).......................................150Learning Objectives...........................................................................................................150Scenario..............................................................................................................................151Task 1: Cable, Erase, and Reload the Routers...................................................................151

Step 1: Cable a network that is similar to the one in the Topology Diagram................151Step 2: Clear the configuration on each router...............................................................151

Task 2: Perform Basic Router Configuration.....................................................................151Step 1: Use global configuration commands.................................................................152Step 2: Configure the console and virtual terminal line passwords on each of the routers.........................................................................................................................................152Step 3: Add the logging command to the console and virtual terminal lines................152Step 4: Add the exec-timeout command to the console and virtual terminal lines........153

Task 3: Interpreting Debug Output....................................................................................154Step 1: On R1 from privileged EXEC mode, enter the debug ip routing command......154Step 2: Enter interface configuration mode for R1’s LAN interface.............................154Step 3: Enter the command necessary to install the route in the routing table..............155Step 4: Enter the command to verify that the new route is now in the routing table.....156Step 5: Enter interface configuration mode for R1’s WAN interface connected to R2.156Step 6: Enter the clock rate command on R1.................................................................156Step 7: Enter the command necessary to ensure that the interface is fully configured..157Step 8:.............................................................................................................................157Step 9: Enter the command necessary to ensure that the interface is fully configured..158Step 10: Enter the command to verify that the new route is now in the routing table for R1 and R2.......................................................................................................................159Step 11: Turn off debugging on both routers using either no debug ip routing or simply, undebug all.....................................................................................................................159

Task 4: Finish Configuring Router Interfaces....................................................................160Step 1: Configure Remaining R2 Interfaces..................................................................160Step 2: Configure R3 Interfaces.....................................................................................160

Task 5: Configure IP Addressing on the Host PCs............................................................160Step 1: Configure the host PC1......................................................................................160Step 2: Configure the host PC2......................................................................................160Step 3: Configure the host PC3......................................................................................160

Task 6: Test and Verify the Configurations.......................................................................161Step 1: Test connectivity................................................................................................161Step 2: Use the ping command to test connectivity between directly connected routers.........................................................................................................................................161Step 3: Use ping to check connectivity between devices that are not directly connected.........................................................................................................................................162

Task 7: Gather Information................................................................................................162Step 1: Check status of interfaces..................................................................................162

of 210

Step 2: View the routing table information for all three routers....................................163Task 8: Configure a Static Route Using a Next-Hop Address...........................................164

Step 1: To configure static routes with a next-hop specified, use the following syntax:........................................................................................................................................164Step 2: View the routing table to verify the new static route entry................................165Step 3: Use ping to check connectivity between the host PC3 and the host PC2..........165Step 4: On the R2 router, configure a static route to reach the 192.168.2.0 network....166Step 5: View the routing table to verify the new static route entry................................166Step 6: Use ping to check connectivity between the host PC3 and the host PC2..........166

Task 9: Configure a Static Route Using an Exit Interface.................................................166Step 1: On the R3 router, configure a static route..........................................................167Step 2: View the routing table to verify the new static route entry................................167Step 3: On the R2 router, configure a static route..........................................................168Step 4: View the routing table to verify the new static route entry................................168Step 5: Use ping to check connectivity between the host PC2 and PC1........................169

Task 10: Configure a Default Static Route........................................................................169Step 1: Configure the R1 router with a default route.....................................................169Step 2: View the routing table to verify the new static route entry................................170Step 3: Use ping to check connectivity between the host PC2 and PC1........................170

Task 11: Configure a Summary Static Route.....................................................................170Step 1: Configure the summary static route on the R3 router........................................171Step 2: Verify that the summary route is installed in the routing table..........................171Step 3: Remove static routes on R3...............................................................................172Step 4: Verify that the routes are no longer in the routing table....................................172Step 5: Use ping to check connectivity between the host PC3 and PC1........................172

Task 12: Summary, Reflection, and Documentation.........................................................173Task 13: Clean Up..............................................................................................................174

Lab 20: Basic RIP Configuration (Packet Tracer).................................................................175Learning Objectives...........................................................................................................175Scenarios............................................................................................................................175Scenario A: Running RIPv1 on Classful Networks...........................................................176Task 1: Prepare the Network..............................................................................................176

Step 1: Cable a network that is similar to the one in the Topology Diagram................176Step 2: Clear any existing configurations on the routers...............................................176

Task 2: Perform Basic Router Configurations...................................................................177Task 3: Configure and Activate Serial and Ethernet Addresses........................................177

Step 1: Configure interfaces on R1, R2, and R3............................................................177Step 2: Verify IP addressing and interfaces...................................................................177Step 3: Configure Ethernet interfaces of PC1, PC2, and PC3.......................................177Step 4: Test the PC configuration by pinging the default gateway from the PC...........177

Task 4: Configure RIP.......................................................................................................178Step 1: Enable dynamic routing.....................................................................................178Step 2: Enter classful network addresses.......................................................................178Step 3: Configure RIP on the R2 router using the router rip and network commands.. 179Step 4: Configure RIP on the R3 router using the router rip and network commands.. 179

Task 5: Verify RIP Routing...............................................................................................179Step 1: Use the show ip route command to verify that each router has all of the networks in the topology entered in the routing table...................................................................179Step 2: Use the show ip protocols command to view information about the routing processes........................................................................................................................181

of 210

Step 3: Use the debug ip rip command to view the RIP messages being sent and received..........................................................................................................................182Step 4: Discontinue the debug output with the undebug all command..........................182

Scenario B: Running RIPv1 with Subnets and Between Classful Networks.....................183Task 1: Make Changes between Scenario A and Scenario B............................................183

Step 1: Change the IP addressing on the interfaces as shown in the Topology Diagram and the Addressing Table...............................................................................................183Step 2: Verify that routers are active..............................................................................184Step 3: Remove the RIP configurations from each router.............................................184

Task 2: Configure RIP.......................................................................................................185Step 1: Configure RIP routing on R1 as shown below..................................................185Step 2: Configure R1 to stop sending updates out the FastEthernet0/0 interface..........185Step 3: Configure RIP routing on R2 as shown below..................................................185Step 4: Configure RIP routing on R3 as shown below..................................................186

Task 3: Verify RIP Routing...............................................................................................186Step 1: Use the show ip route command to verify that each router has all of the networks in the topology in the routing table................................................................................186Step 2: Verify that all necessary interfaces are active....................................................187Step 3: View the RIP messages being sent and received...............................................188Step 4: Discontinue the debug output with the undebug all command..........................188

Scenario C: Running RIPv1 on a Stub Network................................................................190Background........................................................................................................................190Task 1: Make Changes between Scenario B and Scenario C.............................................191

Step 1: Remove network 192.168.4.0 from the RIP configuration for R2....................191Step 2: Completely remove RIP routing from R3..........................................................191

Task 2: Configure the Static Route on R3 for the 172.30.0.0/16 network.........................191Task 3: Configure a Default Static Route on R2................................................................192

Step 1: Configure R2 to send default traffic to R3.........................................................192Step 2: Configure R2 to send default static route information to R1.............................192

Task 4: Verify RIP Routing...............................................................................................192Step 1: Use the show ip route command to view the routing table on R2 and R1.........192Step 2: View the RIP updates that are sent and received on R1 with the debug ip rip command........................................................................................................................193Step 3: Discontinue the debug output with the undebug all command..........................193Step 4: Use the show ip route command to view the routing table on R3.....................193

Task 5: Document the Router Configurations...................................................................193Lab 21 - Configuring VLANs and Trunking (Hardware Equipment)...................................195

Task 1: Build the Network and Configure Basic Device Settings.....................................196Step 1: Cable the network as shown in the topology.....................................................196Step 2: Initialize and reload the switches as necessary..................................................196Step 3: Configure basic settings for each switch...........................................................196Step 4: Configure PC hosts............................................................................................197Step 5: Test connectivity................................................................................................197

Task 2: Create VLANs and Assign Switch Ports...............................................................197Step 1: Create VLANs on the switches..........................................................................197Step 2: Assign VLANs to the correct switch interfaces.................................................199

Task 3: Maintain VLAN Port Assignments and the VLAN Database...............................201Step 1: Assign a VLAN to multiple interfaces...............................................................201Step 2: Remove a VLAN assignment from an interface................................................201

Step 3: Remove a VLAN ID from the VLAN database.....................................................201

of 210

Task 4: Configure an 802.1Q Trunk Between the Switches..............................................203Step 1: Use DTP to initiate trunking on F0/1.................................................................203Step 2: Manually configure trunk interface F0/1...........................................................205

Task 5: Delete the VLAN Database...................................................................................206Step 1: Determine if the VLAN database exists............................................................206Step 2: Delete the VLAN database................................................................................206Task 6: Reflection..........................................................................................................207

of 210

Introduction

The main aim of this laboratory workbook is to keep a record of your laboratory experiments associated with CCE1030 Computer Networking. These experiments are designed to consolidate concepts covered in lectures, to give practical insight into computer networking and to prepare you in experimental techniques, analysis and design of networks.

This workbook contains a number of experiments covering topics taken in lectures and you are expected to complete all tasks. You are expected to record within this workbook all experiments performed in the laboratory. The laboratory tutor is to sign off each experiment completed by you which will serve as evidence of your laboratory work and attendance. Admittance to lab tests will be subject to lab session attendance.

Within these laboratory experiments, you will be introduced to networking tools like Packet Tracer and real equipment like routers and switches which by the end of the course you are expected to become proficient in their use to enable you to progress to the following year of your study programme.

As part of your learning process, you will practice using Packet Tracer simulation tool, it is a networking learning tool that supports a wide range of physical and logical simulations. It also provides visualization tools to help you understand the internal workings of a network.

The pre-made Packet Tracer activities consist of network simulations, activities, and challenges that provide a broad range of learning experiences. These tools will help you develop an understanding of how data flows in a network.

The completion of the various tasks within the experiments in this laboratory workbook carry weight according to their relative standing within the module material. These will be marked using the Student Observable Behaviour (SOB) framework. SOBs are classified into 3 categories; Threshold, Typical and Excellent. It is imperative that you manage to complete all Threshold tasks within the workbook (numbering 40), in order to pass the SOBs. However, you are advised to complete successfully all Threshold and Typical SOBs as well as aim to finish the Excellent.

In this course, you will learn both the practical and conceptual skills that build the foundation for understanding basic networking. You will be expected to experiment using not just simulation tools like Packet Tracer but also to replicate those experiments on real equipment which will be available for you in the laboratory. You will at the end of each experiment make a reflective comparison between your results in both Packet Tracer and real equipment. You will do the following:

•Be introduced to the two major models used to plan and implement networks: OSI and TCP/IP

•Gain an understanding of the "layered" approach to networks

of 210

•Examine the OSI and TCP/IP layers in detail to understand their functions and services

•Become familiar with the various network devices and network addressing schemes

•Discover the types of media used to carry data across the network

•Configure and troubleshoot basic operations of a small switched network

•Configure and verify static routing and default routing

•Configure and troubleshoot basic operations of routers in a small routed network

•Configure and troubleshoot basic operations of routing protocols in a small routed network

By the end of this course, students will be able to build simple LANs, perform basic configurations for routers and switches, and implement IP addressing schemes. They will also be able to configure and troubleshoot routers and switches and resolve common issues with RIPv1.

of 210

Lab 1: My First Packet Tracer Lab

Introduction

Welcome to Packet Tracer. Research has shown that users who master a few basic tasks when first starting to use Packet Tracer get much more out of the software. This lab is designed to familiarize a user with Packet Tracer's features. This activity should take approximately 30 minutes to complete. Use these directions to go through the lab yourself, or view the animated tutorial version of the lab.

Lab Objectives

Viewing Help and Tutorials Creating Your First Network Sending Simple Test Messages in Realtime Mode Establishing a Web Server Connection Using the PC’s Web Browser Capturing Events and Viewing Animation in Simulation Mode Looking Inside Packets in Simulation Mode Viewing Device Tables and Resetting the Network Reviewing Your New Skills

Important Terminology

1. ICMP ping: command consisting of an echo request message from one device to another, and the returning echo reply.

2. IP address: 32-bit address assigned to devices as identification in the network.3. Ethernet: one of the most common LAN standards for hardware, communication and

cabling.4. Fast Ethernet Interface: 100 Mbps Ethernet port. In Packet Tracer, a GUI may be used

to configure such interfaces.5. OSI model: 7-layer framework for looking at network protocols and devices,

consisting of the application, presentation, session, transport, network, data link, and physical layers.

6. PDU: protocol data unit, a grouping of data appropriate to a given layer in the OSI model.

7. Packets: OSI Layer 3 protocol data units. Represented by envelopes in Packet Tracer Simulation Mode.

8. Device Tables: includes ARP, switching, and routing tables. They contain information regarding the devices and protocols in the network.

9. ARP Table: Address Resolution Protocol (ARP) table, stores pairings of IP Addresses and Ethernet MAC addresses.

of 210

10. Scenario: one topology with a set of PDUs placed in the network to be sent at specific times. Using different scenarios, experiment with different combinations of packets using the same base topology.

Task 1: Viewing Help and Tutorials

1. Launch Packet Tracer.2. Open the help content by clicking Help > Contents on the Menu bar. You can also

click the question mark on the Main toolbar. Another option is the F1 shortcut key.3. The menu will always be visible on the left side of the window while browsing

through the help files. Skim through the help sections to get an idea of the functionality of Cisco Packet Tracer.

4. The What's New section under Introduction provides an overview of features that have been added to Packet Tracer.

5. Pay close attention to the Interface Overview section under Getting Started to familiarize yourself quickly to the Packet Tracer interface.

6. Browse the Tutorials section as well.7. Open the Interface Overview tutorial to learn the basics of the Packet Tracer graphical

user interface. Note: Some browsers may prevent the tutorial from playing. Configure your browser to allow active content to enable the viewing of the tutorial.

8. When the first caption appears, as shown below, click the Pause button in the playback controls.

9. Click the Forward button to skip to the next caption. Then click Pause again. Click the Back button to view the previous caption.

10. Continue viewing the tutorial by pressing the Play button. Parts of the tutorial can also be skipped by dragging the slider to the right. If needed, click the Rewind button to restart the tutorial.

11. Click Exit to close the tutorial window. Close the help content as well.

Congratulations on learning more about resources that will help you get the most out of Packet Tracer.

of 210

Task 2: Creating a First Network

1. Start creating a network by first selecting the End Devices. Add a Generic PC and a Generic Server to the workspace.

2. Under Connections, select the Copper Straight-through cable (solid black line) and connect the devices with it. The red lights on the link indicate that the connection is not working. Now, use the Delete tool to remove the Copper Straight-through cable, and use a Copper Cross-over cable (dashed line) instead. The lights should turn green at this point. If the mouse pointer is held over either device, the link status will be shown as “Up.” The network should look similar to this:

3. Click on the PC. While paying attention to the link lights, turn the power on, off, and on again. Follow the same steps for the server. The link lights turn red when the device is off. This means that the link is down or is not working. The link lights turn green when the device is turned back on.

4. Try all three ways to learn about the devices. First, mouse over the devices to see basic configuration information about them. Second, click on each device with the Select tool to show the device configuration window, which provides several ways to configure the device. Third, use the Inspect tool to view the tables the network device will build as it learns about the network around it. In this example, open the ARP table. Since the devices have not been configured yet, the ARP tables are empty. Always remember to close the windows after viewing them or they will clutter the workspace.

5. Open the PC configuration window and change the settings using the Config tab. Change the display name to Client and set the DNS server to 192.168.0.105. Under Interface, click FastEthernet and set the IP address as 192.168.0.110. Packet Tracer automatically calculates other parameters. Make sure that the Port Status box is checked. For future reference, note that other Ethernet interface settings, such as bandwidth, duplex, MAC address, and subnet mask can be modified using this window.

6. Go to the Desktop Tab and click on IP Configuration. Notice that the IP address, subnet mask and DNS server can be changed here as well.

7. Open the Server configuration window and go to the Config tab. Change the display name to Web Server. Click FastEthernet and set the IP address as 192.168.0.105.

of 210

Make sure that the Port Status is also on. Click DNS and set the domain name as www.firstlab.com. Set the IP address as 192.168.0.105 and click Add. Finally, check to make sure that the service for DNS is on.

8. Reposition the network devices by dragging them to a new location. Add a network description by using the “i” button on the upper right corner. Then add some text labels within the Logical Workspace by using the Place Note tool.

9. Load a background grid using the Set Tiled Background button.10. Save your work using the File > Save As option and create a meaningful filename.

Task 3: Sending Simple Test Messages in Realtime Mode

1. Start by opening the file saved in the last section.2. Notice that the file opens in Realtime Mode. Use the Add Simple PDU tool to send a

simple one-time ping message, called an echo request, to the server. The server responds with an echo reply because all devices have properly configured IP address settings.

3. Scroll up and down the User Created Packet Window to see the different capabilities of this ping message, including an indication that the ping was successful.

4. Toggle the PDU List Window to see a larger display of this message. One or more of these messages can be saved as a scenario. Scenario 0 is displayed when starting. Label this first scenario with an “i” note. Different scenarios allow the use of the same topology for experiments with different groupings of user created packets.

5. Click New to create a new scenario. New scenarios will initially be blank.6. Add two packets using the Simple PDU tool, a PDU from the PC to the Server and a

different PDU from the Server to the PC. Then add an “i” note describing the scenario, to complete Scenario 1. An example is shown below:

of 210

Threshold SOB 01

7. Several scenarios can be saved with a single network. Alternate between Scenario 0 and 1.

8. Now, remove Scenario 0 using the Delete button.9. Scenario 1 is now visible. Go to the last column in the User Created Packet Window

and double-click (delete) to remove a PDU.10. Delete the whole scenario. Notice that the scenario list went back to the default

Scenario 0.

Task 4: Establishing a Web Server Connection Using the PC’s Web Browser

1. Open the file saved from the previous section.2. Click on the PC to view the configuration window.3. Select the Desktop tab, and then click Web Browser. Type in www.firstlab.com as the

URL and click the Go button. The Packet Tracer welcome page, shown below, appears, indicating that the web connection has been successfully established.

4. Clear the URL, type www and click Go. Since the address entered is not complete, a “Host Name Unresolved” message appears.

5. Type 192.168.0.105 as the URL entry and click on Go. Notice that the Packet Tracer welcome page appears again. This is because the Server IP address can also be used to establish a web connection.

6. Close the window and try the same steps in Simulation Mode. In this mode, the user controls time, so the network can be viewed running at a slower pace, allowing observation of the paths packets take and inspection of packets in detail (packet tracing!).

7. Select the PC again and go to the Web Browser in the Desktop tab. Type www.firstlab.com as the URL again and click Go. The welcome page should not appear right away.

8. Switch to the main interface of Packet Tracer without closing the PC configuration window. Notice that a DNS packet is added to the event list.

9. Click Auto Capture/Play or repeatedly click the Capture/Forward button until the HTTP packet appears on the PC. Go back to the PC configuration window. The Packet Tracer welcome page is now shown.

10. Close the PC configuration window.

of 210

Threshold SOB 02

Task 5: Capturing Events and Viewing Animations in Simulation Mode

1. Open the previously saved file.2. In Realtime Mode, send a simple PDU from the PC to the Server.3. Delete the PDU by using the method learned in the previous section.4. Switch to Simulation Mode.5. Click Edit Filters and click All/None to uncheck all fields. Then click ICMP to only

view ICMP packets in the animation.6. Add a simple PDU from the PC to the Server. Notice that the newly created PDU is

added to the User Created PDU List. This packet has been captured as the first event in the event list and a new packet icon (envelope) appears in the workspace. The eye icon to the left of the event list indicates that this packet is currently displayed.

7. Click the Capture/Forward button once. This simulates a network sniffing program, capturing the next event that occurs on the network. Note that after clicking Capture/Forward, the packet in the workspace moves from one device to another (this is the ICMP echo request message from the PC to the Server). Another event is added in the event list – this reflects the change in the workspace. The first time through an animation, the meaning of the Capture/Forward is capture; after resetting the simulation, the meaning is forward.

8. Adjust the speed of the animation by dragging the Play Speed slider to the right making it go faster. Dragging the speed slider in the opposite direction (to the left) will slow down the animation.

9. Click the Capture/Forward button a second time. This captures the next network event (this is the echo reply from the Server to the PC, shown as successful with a green check mark on the envelope).

10. Click Capture/Forward button again. The Server has already sent an echo reply to the PC therefore, there are no more ICMP events left to capture.

of 210

Threshold SOB 03

Task 6: Looking Inside Packets in Simulation Mode

1. Continuing from the last activity, click Reset Simulation. This clears the entries in the event list except for the original packet.

2. Select the packet envelope on the workspace to show the PDU Information window like the one shown in the screenshot below. This window contains the OSI Model tab, which shows how the packet is processed at each layer of the OSI model by the current device. Close this window, noting that this packet is indicated in the event list by the eye icon. The whole row in the event list is also highlighted. Clicking on the colour square in the Info column is equivalent to clicking directly on the packet envelope (try it!).

3. Use the Next Layer and Previous Layer buttons to see details of the packet processing at the relevant OSI layers. Note that only the Out Layers can be viewed in the case of this original echo request message.

4. Click on the Outbound PDU Details tab. This tab shows exactly what makes up the PDU headers. It is organized into header type and the individual fields in each header.

5. Close the PDU Information window. Click on Capture/Forward button once.6. Click on the packet in the workspace again to open the PDU Information window.

Notice that this time, information regarding both the In Layers and Out Layers can be viewed.

7. Click on the Inbound PDU Details tab. This shows the details of the inbound echo request packet from the PC to the Server. The Outbound PDU Details tab, shows similar information, but for the echo reply packet from the Server to the PC.

8. Click on Reset Simulation again. Now click on Auto Capture/Play. The echo request and echo reply are automatically captured. Click on the Back Button to rewind the

of 210

Threshold SOB 04

animation one step at a time. Now click on the Capture/Forward button to forward the packet through the animation. Note the change in the event list and the workspace. Remember that at any time, a PDU Information Window can be opened by clicking directly on the envelope on the workspace, or by clicking the Info column in the Event List.

9. Click on the Back Button twice to rewind the animation. Now click Auto Capture/Play and the packet animation will automatically occur.

Task 7: Viewing Device Tables and Resetting the Network

1. Open the file saved from the previous section.2. Open the ARP Tables for both devices by clicking them with the Inspect tool. The

ARP tables always appear on the same spot. Reposition them to make them both visible. You can also resize the tables for better viewing.

3. In Realtime Mode, send a simple PDU from the PC to the Server. Notice that the ARP tables are filled in automatically, as shown here:

4. Delete the PDU using the method covered in the previous sections. Notice that the entries in the ARP tables are NOT cleared. ARP entries for both devices have already been learned. Deleting the user created PDUs does not reset events what has already occurred in the network.

5. Click Power Cycle Devices. ARP tables are cleared because the Power Cycle Devices button turns the devices off and back on again therefore, losing temporary information like the ARP table entries.

6. Go to Simulation Mode. In the event list filters, make sure that ICMP and ARP are checked so that you can view ICMP and ARP packets in the animation.

7. Create a new simple PDU from the Server to the PC.8. Notice that since the devices were power cycled earlier, the ARP tables are empty.

ARP request packets need to be issued before the ICMP ping packets, so that the devices in the network can learn about each other. Click on Auto Capture/Play to watch the animation.

of 210

9. Click Reset Simulation. Notice that even though the event list is cleared (except for the user created PDU), the ARP tables remain full. Click Auto Capture/Play. This time, since the ARP tables are full, there are no new ARP packets issued.

10. Click Power Cycle Devices. Doing so will empty the tables. Notice that new ARP request packets appear automatically in the event list.

Task 8: Reviewing Your New Skills

Single-clicking on the Delete button removes the entire scenario including all the PDUs associated with it.

Double-clicking on (delete) in the far right column in the PDU List window deletes individual PDUs.

The Reset Simulation button clears all entries in the Event List, except for User Created PDUs, and allows the animation to restart. This, however, does not reset the device tables.

The Power Cycle Devices button turns all of the devices in the network off and on so the tables that the devices built are lost along with configurations and other information not saved.

Saving work periodically prevents lost configurations and state changes in the network.

Congratulations on being ready to build and analyse many different networks in Packet Tracer! Be aware that there are many other features that were not covered in this lab. To learn more, please view the other available tutorials and review the help files. Have Fun!

of 210

Typical SOB 05

Lab 2: Investigating the TCP/IP and OSI Models in Action (Packet Tracer)

Objectives

Part 1: Examine HTTP Web TrafficPart 2: Display Elements of the TCP/IP Protocol Suite

Background

This simulation activity is intended to provide a foundation for understanding the TCP/IP protocol suite and the relationship to the OSI model. Simulation mode allows you to view the data contents being sent across the network at each layer.

As data moves through the network, it is broken down into smaller pieces and identified so that the pieces can be put back together when they arrive at the destination. Each piece is assigned a specific name (protocol data unit [PDU]) and associated with a specific layer of the TCP/IP and OSI models. Packet Tracer simulation mode enables you to view each of the layers and the associated PDU. The following steps lead the user through the process of requesting a web page from a web server by using the web browser application available on a client PC.

Even though much of the information displayed will be discussed in more detail later, this is an opportunity to explore the functionality of Packet Tracer and be able to visualize the encapsulation process.

Task 1: Examine HTTP Web Traffic

In Part 1 of this activity, you will use Packet Tracer (PT) Simulation mode to generate web traffic and examine HTTP.

Step 1: Switch from Realtime to Simulation mode.

In the lower right corner of the Packet Tracer interface are tabs to toggle between Realtime and Simulation mode. PT always starts in Realtime mode, in which

of 210

networking protocols operate with realistic timings. However, a powerful feature of Packet Tracer allows the user to “stop time” by switching to Simulation mode. In Simulation mode, packets are displayed as animated envelopes, time is event driven, and the user can step through networking events.

a. Click the Simulation mode icon to switch from Realtime mode to Simulation mode.

b. Select HTTP from the Event List Filters.

1) HTTP may already be the only visible event. Click Edit Filters to display the available visible events. Toggle the Show All/None check box and notice how the check boxes switch from unchecked to checked or checked to unchecked, depending on the current state.

2) Click the Show All/None check box until all boxes are cleared and then select HTTP. Click anywhere outside of the Edit Filters box to hide it. The Visible Events should now only display HTTP

Step 2: Generate web (HTTP) traffic.

Currently the Simulation Panel is empty. There are six columns listed across the top of the Event List within the Simulation Panel. As traffic is generated and stepped through, events appear in the list. The Info column is used to inspect the contents of a particular event.

Note: The Web Server and Web Client are displayed in the left pane. The panels can be adjusted in size by hovering next to the scroll bar and dragging left or right when the double-headed arrow appears.

a. Click Web Client in the far left pane.b. Click the Desktop tab and click the Web Browser icon to open it.c. In the URL field, enter www.osi.local and click Go.

Because time in Simulation mode is event-driven, you must use the Capture/Forward button to display network events.

d. Click Capture/Forward four times. There should be four events in the Event List.

Look at the Web Client web browser page. Did anything change? __________________________________________________________________________________________________________________________________________

Step 3: Explore the contents of the HTTP packet.

a. Click the first coloured square box under the Event List > Info column. It may be necessary to expand the Simulation Panel or use the scrollbar directly below the Event List.

The PDU Information at Device: Web Client window displays. In this window, there are only two tabs (OSI Model and Outbound PDU Details) because this is the start of the transmission. As more events are examined, there will be three tabs displayed, adding a tab for Inbound PDU Details. When an event is the last event in the stream of traffic, only the OSI Model and Inbound PDU Details tabs are displayed.

of 210

b. Ensure that the OSI Model tab is selected. Under the Out Layers column, ensure that the Layer 7 box is highlighted.

What is the text displayed next to the Layer 7 label? _____________________

What information is listed in the numbered steps directly below the In Layers and Out Layers boxes?__________________________________________________________________________________________________________________________________________

c. Click Next Layer. Layer 4 should be highlighted. What is the Dest Port value? ___________________

d. Click Next Layer. Layer 3 should be highlighted. What is the Dest. IP value? ____________________

e. Click Next Layer. What information is displayed at this layer? __________________________________________________________________________________________________________________________________________

f. Click the Outbound PDU Details tab.

Information listed under the PDU Details is reflective of the layers within the TCP/IP model.

Note: The information listed under the Ethernet II section provides even more detailed information than is listed under Layer 2 on the OSI Model tab. The Outbound PDU Details provides more descriptive and detailed information. The values under DEST MAC and SRC MAC within the Ethernet II section of the PDU Details appear on the OSI Model tab under Layer 2, but are not identified as such.

What is the common information listed under the IP section of PDU Details as compared to the information listed under the OSI Model tab? With which layer is it associated?_______________________________________________________________________________________________________________________________________________________________________________________________________________

What is the common information listed under the TCP section of PDU Details, as compared to the information listed under the OSI Model tab, and with which layer is it associated?_______________________________________________________________________________________________________________________________________________________________________________________________________________

What is the Host listed under the HTTP section of the PDU Details? ___________________________

What layer would this information be associated with under the OSI Model tab? __________________

g. Click the next coloured square box under the Event List > Info column. Only Layer 1 is active (not greyed out). The device is moving the frame from the buffer and placing it on to the network.

h. Advance to the next HTTP Info box within the Event List and click the coloured square box. This window contains both In Layers and Out Layers. Notice the direction of the arrow directly under the In Layers column; it is pointing upward,

of 210

indicating the direction the information is travelling. Scroll through these layers making note of the items previously viewed. At the top of the column the arrow points to the right. This denotes that the server is now sending the information back to the client.

Comparing the information displayed in the In Layers column with that of the Out Layers column, what are the major differences?____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

i. Click the Outbound PDU Details tab. Scroll down to the HTTP section.

What is the first line in the HTTP message that displays?_____________________________________________________________________

j. Click the last coloured square box under the Info column. How many tabs are displayed with this event and why?_____________________________________________________________________

Task 2: Display Elements of the TCP/IP Protocol Suite

In Part 2 of this activity, you will use the Packet Tracer Simulation mode to view and examine some of the other protocols comprising of the TCP/IP suite.

Step 1: View Additional Events

a. Close any open PDU information windows.

b. In the Event List Filters > Visible Events section, click Show All.

What additional Event Types are displayed? __________________________________________________________________________________________________________________________________________

These extra entries play various roles within the TCP/IP suite. If the Address Resolution Protocol (ARP) is listed, it searches MAC addresses. DNS is responsible for converting a name (for example, www.osi.local) to an IP address. The additional TCP events are responsible for connecting, agreeing on communication parameters, and disconnecting the communications sessions between the devices. Currently there are over 35 possible protocols (event types) available for capture within Packet Tracer.

c. Click the first DNS event in the Info column. Explore the OSI Model and PDU Detail tabs and note the encapsulation process. As you look at the OSI Model tab with Layer 7 highlighted, a description of what is occurring is listed directly below the In Layers and Out Layers (“1. The DNS client sends a DNS query to the DNS

of 210

Threshold SOB 06

server.”). This is very useful information to help understand what is occurring during the communication process.

d. Click the Outbound PDU Details tab. What information is listed in the NAME: in the DNS QUERY section?

__________________________________________________________________________________________________________________________________________

e. Click the last DNS Info coloured square box in the event list. Which device is displayed? ___________

What is the value listed next to ADDRESS: in the DNS ANSWER section of the Inbound PDU Details? _____________________________________________________________________

f. Find the first HTTP event in the list and click the coloured square box of the TCP event immediately following this event. Highlight Layer 4 in the OSI Model tab. In the numbered list directly below the In Layers and Out Layers, what is the information displayed under items 4 and 5? _______________________________________________________________________________________________________________________________________________________________________________________________________________

TCP manages the connecting and disconnecting of the communications channel along with other responsibilities. This particular event shows that the communication channel has been ESTABLISHED.

g. Click the last TCP event. Highlight Layer 4 in the OSI Model tab. Examine the steps listed directly below In Layers and Out Layers. What is the purpose of this event, based on the information provided in the last item in the list (should be item 4)?

__________________________________________________________________________________________________________________________________________

Challenge

This simulation provided an example of a web session between a client and a server on a local area network (LAN). The client makes requests to specific services running on the server. The server must be set up to listen on specific ports for a client request. (Hint: Look at Layer 4 in the OSI Model tab for port information.)

Based on the information that was inspected during the Packet Tracer capture, what port number is the Web Server listening on for the web request? __________________

What port is the Web Server listening on for a DNS request? ______________________

of 210

Threshold SOB 07

Lab 3: Examining Packets (Packet Tracer)

Topology Diagram

Addressing Table

Device Interface IP Address Subnet Mask Default Gateway

R1-ISPFa0/0 192.168.254.253 255.255.255.0 N/AS0/0/0 10.10.10.6 255.255.255.252 N/A

R2-Central

Fa0/0 172.16.255.254 255.255.0.0 N/AS0/0/0 10.10.10.5 255.255.255.252 N/A

S1-Central

VLAN 1 172.16.254.1 255.255.0.0 172.16.255.254

PC 1A NIC 172.16.1.1 255.255.0.0 172.16.255.254PC 1B NIC 172.16.1.2 255.255.0.0 172.16.255.254Eagle Server NIC 192.168.254.254 255.255.255.0 192.168.254.253

of 210

Excellent SOB 08

Learning Objectives

Complete the Topology Add Simple PDUs in Realtime Mode Analyse PDUs in Simulation Mode Experiment with the model of the standard lab setup

Background

In this activity you will continue learning how to build and analyse this standard lab topology. If you have not done so already, you are encouraged to examine the Help files available from the Help Pull-down menu at the top of the Packet Tracer GUI. This activity will provide an opportunity to explore the standard lab setup using Packet Tracer simulator. Packet Tracer has two file formats it can create: .pkt files (network simulation model files) and .pka files (activity files for practice). When you create your own networks in Packet Tracer, or modify existing files from your instructor or your peers, you will often use the .pkt file format. When you launched this activity from the curriculum, these instructions appeared. They are the result of the .pka, Packet Tracer activity file format. At the bottom of these instructions are two buttons: Check Results (which gives you feedback on how much of the activity you have completed) and Reset Activity (which starts the activity over, if you want to clear your work or gain more practice).

Task 1: Complete the Topology.

Add a PC to the workspace. Configure it the following parameters: IP Address 172.16.1.2, Subnet Mask 255.255.0.0, Default Gateway 172.16.255.254, DNS Server 192.168.254.254, Display Name "1B" (do not include the quotation marks). Connect PC 1B to the Fa0/2 port of the S1-Central Switch and check your work with the Check Results button to see that the topology is complete.

Task 2: Add Simple PDUs in Realtime Mode.

Using the Add Simple PDU, send a test message: one between PC 1B and Eagle Server. Note that this packet will appear in the event list as something that was "detected" or "sniffed" on the network, and in the lower right as a user created PDU that can be manipulated for testing purposes.

of 210

Threshold SOB 09

Task 3: Analyse PDUs in Simulation Mode (Packet Tracing).

Switch to simulation mode. Use the Capture / Forward button to move the packet through the network by clicking 8 times. Click on the packet envelope, or on the coloured square in the Info column of the Event List, to examine the packet at each step in its journey.

What is the packet type that was sent? ___________

How many steps does it take to send and receive the packet? _____________

Task 4: Experiment with the Model of the Standard Lab Setup.

The standard lab setup will consist of two routers, one switch, one server, and two PCs. Each of these devices are pre-configured. Try creating different combinations of test packets and analysing their journey through the network.

Reflection

Using the exercise above reflect on the communication process in a network where a simple PDU travels through the network from source to destination. What are the various steps (in detail) to completing this process successfully? (Keeping in mind that there are layers on the In and Out sides in each device).

_________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

of 210

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

of 210

of 210

Typical SOB 10

Lab 4: Analysing the Application and Transport Layers (Packet Tracer)

Topology Diagram

Addressing Table


R1-ISPFa0/0 192.168.254.253 255.255.255.0 N/A

S0/0/0 10.10.10.6 255.255.255.252 N/A

R2-CentralFa0/0 172.16.255.254 255.255.0.0 N/A

S0/0/0 10.10.10.5 255.255.255.252 N/A

S1-Central VLAN 1 172.16.254.1 255.255.0.0 172.16.255.254

PC 1A NIC 172.16.1.1 255.255.0.0 172.16.255.254PC 1B NIC 172.16.1.2 255.255.0.0 172.16.255.254Eagle Server NIC 192.168.254.254 255.255.255.0 192.168.254.253

Learning Objectives

Configure Hosts and Services Connect and configure hosts and services on the model of the lab network Explore How DNS, UDP, HTTP, and UDP Work Together

of 210

Use simulation mode to visualize the operation of DNS, UDP, HTTP, and TCP on the model of the lab network.

Background

Throughout the course you will be using a standard lab setup created from actual PCs, servers, routers, and switches to learn networking concepts. At the end of each chapter, you will build increasingly larger parts of this topology in Packet Tracer, and analyze increasingly more complex protocol interactions.

Task 1: Repair and Test the Topology.

The server has been replaced. It must be powered on and connect it to R1-ISP router via Fa0/0 interface using cross-over cable. Then configure it with the following settings: IP Address 192.168.254.254, Subnet Mask 255.255.255.0, Default Gateway 192.168.254.253, DNS enabled, with the association of Eagle-Server.example.com with the server's IP address, HTTP enabled.

PC 1A has lost its IP address information. Configure it with the following settings: IP Address 172.16.1.1, Subnet Mask 255.255.0.0, Default Gateway 172.16.255.254, and DNS Server 192.168.254.254. Connect PC 1A to the Fa0/1 port of the S1-Central switch using a straight-through cable.

Verify your work using feedback from the Check Results button and the Assessment Items tab. Test connectivity, in realtime, by using ADD SIMPLE PDU to test connectivity between PC 1A and the Eagle Server.

Note that when you add a simple PDU, it appears in the PDU List Window as part of "Scenario 0". The first time you issue this one-shot ping message, it will show as Failed--this is because of the ARP process which will be explained later. Double clicking the "Fire" button in the PDU List Window, send this single test ping a second time. This time it will be successful. In Packet Tracer, the term "scenario" means a specific configuration of one or more test packets. You can create different test packet scenarios by using the New button--for example Scenario 0 might have one test packet from PC 1A to Eagle Server; Scenario 1 might have test packets between PC 1B and the routers; and so on. You can remove all test packets in a particular scenario by using the Delete button. For example, if you use the Delete button for Scenario 0 the test packet you just created between PC 1A and Eagle Server will be removed--please do this prior to the next task.

of 210

Threshold SOB 11

Task 2: Explore How DNS, UDP, HTTP, and TCP Work Together

Switch from Realtime to Simulation Mode. Make sure Event Filter is set to display DNS, UDP, HTTP, TCP, and ICMP. Open a web browser from the desktop of 1A. Type in the URL eagle-server.example.com, press Enter, and then use the Capture / Forward button in the Event List to capture the interaction of DNS, UDP, HTTP and TCP.You can examine the packet in two ways: by clicking on the packet envelope as it is displayed in the animation, or by clicking on the Info column for that packet instance as it is listed in the Event List. Play this animation and examine the Packet contents (PDU Information Window, Inbound PDU Details, Outbound PDU Details) for each event in the event list, especially when the packets are at PC 1A or at the Eagle Server. If you receive a "Buffer Full" message, click the View Previous Events button. While the processing of the packets at the switch and the routers may not make sense to you yet, you should be able to see how DNS, UDP, HTTP, and TCP work together by studying tracing the packets and using the PDU Information window to look "inside" them.

Reflection

Make a diagram of the sequence of protocol events involved in requesting a web page using a URL? Where might things go wrong? Compare and contrast DNS and HTTP, and UDP and TCP.

________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

of 210

______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

of 210

Typical SOB 12

Lab 5: Connecting to a Cisco Device via Console (Hardware)

Lab Prerequisites

In order to complete this lab you will need a real Cisco Router or Switch.

Prior to attempting this lab you must have a terminal emulator application installed such as HyperTerminal or Putty.

Learning Objectives

To complete this lab you will perform the following objectives:

Connect your PC to your Cisco Router using the blue Cisco Console Cable. Execute putty and connect to your Cisco Router or Switch using Serial COM1 or your

respective COM port at the speed of 9600bps. Power on your Cisco device and verify your console session by watching the device

boot up on the terminal emulator.

Background

So you take a brand new Cisco Router or switch out of the box and the very first thing you must do prior to installing it is to put a basic configuration on it. In order to configure the basics on a Cisco device you must first Console into the device.

If you ever take a brand new Cisco device out of the box you’ll see that it comes with a blue flat cable that has a DB9 serial connector on one end and a network RJ45 connector on the other. Don’t be fooled, this is not a “next generation” Ethernet cable or some token ring cable but rather a Cisco Console Cable.

You use this cable to connect to He Cisco device via Serial Port so you can configure the device using command line.

Because Cisco devices do not have graphics cards or the ability to use a mouse and keyboard, you must connect to the device using another computer that provides that functionality so you can configure the device via Console CLI.

In order to connect to a Cisco device via Console you’ll need to use a Terminal Emulator application.

Applications that you commonly use to perform this task can be Windows HyperTerminal which is included with Windows XP however Windows Vista and newer requires you to manually download/install this application. An extremely popular terminal emulator is Putty which is completely free to download.

of 210

Lab Instruction

While most terminal emulation software differs in available features and/or protocols, all terminal emulators achieve the same goal. In this walk through, Putty will be used, which is freely available (See Lab Summary) to connect to a Cisco device and establish a console session to the Cisco Command Line Interface.

Step 1: Connect your Cisco console cable or terminal adapter to a Serial port on your computer.

Step 2: Connect the RJ45 end of the console cable to the “Console” port on your Cisco router.

Step 3: When first running the Putty executable you will be presented with the Putty Configuration Window as shown below;

Step 4: After the Putty configuration window appears, move the bullet from SSH to Serial;

Note: COM1 is the default communications port for Putty Serial communications; you may need to change your COM port to match the port which your console cable is connected to.

of 210

Step 5: Once you’ve verified the COM port and Speed click “Open” and a new window will appear. This window will be the terminal window. Once the COM# – Putty terminal window has appeared, power on your Cisco Device. After the device has booted; assuming that the NVRAM is clear, you will be prompted with a Setup Configuration Dialog:

After you are presented with the Setup Configuration Dialog type “n” for no and press enter. You will then be prompted to press Return to Get Started!, after pressing Enter you will be at the routers user mode command line interface which looks like the following;

After you have reached this point you have completed the objectives of this lab.

of 210

Threshold SOB 13

Lab 6: Topology Orientation and Building a Small Network (Packet Tracer)

Topology DiagramPeer to Peer Network

Switched Network

Learning Objectives

Upon completion of this lab, you will be able to:• Correctly identify cables for use in the network.• Physically cable a peer-to-peer and switched network.• Verify basic connectivity on each network.

Background

Many network problems can be fixed at the Physical layer of a network. For this reason, it is important to have a clear understanding of which cables to use for your network connections.

At the Physical layer (Layer 1) of the OSI model, end devices must be connected by media (cables). The type of media required depends on the type of device being connected. In the basic portion of this lab, straight–through or patch—cables will be used to connect workstations and switches.

In addition, two or more devices communicate through an address. The Network layer (Layer 3) requires a unique address (also known as a logical address or IP Addresses), which allows the data to reach the appropriate destination device.

of 210

Addressing for this lab will be applied to the workstations and will be used to enable communication between the devices.

Scenario

This lab exercise is divided into two sections, the first section starts with the simplest form of networking (peer-to-peer network) where two workstations are directly connected.

The second section will require the addition of a switch to the network in section 1.

Section 1

Task 1: Create a Peer-to-Peer Network.

As in the first diagram, use packet tracer simulator to create the following networks. For the first network use two workstations for a peer-to-peer network.

Task 2: Identify the Cables used in a Network.

Before the devices can be cabled, you will need to identify the types of media you will be using. The cables used in this lab are crossover and straight-through.

Use a crossover cable to connect two workstations to each other through their NIC’s Ethernet port. This is an Ethernet cable. When you look at the plug you will notice that the orange and green wires are in opposite positions on each end of the cable.

Use a straight-through cable to connect the router’s Ethernet port to a switch port or a workstation to a switch port. This is also an Ethernet cable. When you look at the plug you will notice that both ends of the cable are exactly the same in each pin position.

Task 3: Cable the Peer-to-peer Network.

Step 1: Connect two workstations.Using the correct Ethernet cable, connect two workstations together. Connect one end of the cable to the FastEthernet port on PC0 and the other end of the cable to the FastEthernet port on PC1.

Which cable did you use? ______________________________________________________

Step 2: Apply a Layer 3 address to the workstations.To complete this task, you will need to follow the step-by-step instructions below.

of 210

1. Click on PC0, choose the Desktop tab at the top, and then the IP Configuration option at the top left of the window. The IP Configuration window should appear as can be seen below.

2. In the IP address box, enter the IP address 192.168.1.2 for PC0. (Enter the IP address 192.168.1.3 for PC1.)

3. Press the tab key and the Subnet mask is automatically entered. The subnet address should be 255.255.255.0. If this address is not automatically entered, enter this address manually.

4. Close the window.

Step 3: Verify connectivity.

1. Click on PC0, click on Desktop tab, then click Command Prompt.

of 210

The DOS command (cmd.exe) window will appear. You can enter DOS commands using this window. For the purposes of this lab, basic network commands will be entered to allow you to test your computer connections.

The ping command is a computer network tool used to test whether a host (workstation, router, server, etc.) is reachable across an IP network.

2. Use the ping command to verify that PC0 can reach PC1 and PC1 can reach PC0. From the PC0 DOS command prompt, type ping 192.168.1.3. From the PC1 DOS command prompt, type ping 192.168.1.2.

What is the output of the ping command?_________________________________________________________________________________________________________________________________________________________________________________________________________________________________

If the ping command displays an error message or doesn’t receive a reply from the other workstation, troubleshoot as necessary. Possible areas to troubleshoot include:

Verifying the correct IP addresses on both workstations Ensuring that the correct type of cable is used between the workstations

What is the output of the ping command if you unplug the network cable and ping the other workstation?_________________________________________________________________________________________________________________________________________________________________________________________________________________________________

of 210

Threshold SOB 14

Section 2

Task 4: Connect Your Workstations to the Switch.

Step 1: Connect workstation to a switch.

Add a 2960 switch to your Logical Workplace and then using the correct cable, connect one end of the cable to the FastEthernat port (make sure you delete the cable connection between the two PCs first) on PC0 and the other end to FastEthernet 0/1 port on the switch.

Step 2: Repeat this process for each workstation on your network.



Verify network connectivity by using the ping command to reach the other workstations attached to the switch.What is the output of the ping command?____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

What is the output of the ping command if you ping an address that is not connected to this network?_________________________________________________________________________________________________________________________________________________________________________________________________________________________________

of 210

Typical SOB 15

Task 5: Reflection

What could prevent a ping from being sent between the workstations when they are directly connected?_______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

What could prevent the ping from being sent to the workstations when they are connected through the switch?_______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

of 210

Excellent SOB 16

Lab 7: Topology Orientation and Building a Small Network (Hardware Equipment)

Topology DiagramPeer to Peer Network

Switched Network

Learning Objectives

Upon completion of this lab, you will be able to:• Correctly identify cables for use in the network.• Physically cable a peer-to-peer and switched network.• Verify basic connectivity on each network.

Background

Many network problems can be fixed at the Physical layer of a network. For this reason, it is important to have a clear understanding of which cables to use for your network connections.

At the Physical layer (Layer 1) of the OSI model, end devices must be connected by media (cables). The type of media required depends on the type of device being connected. In the basic portion of this lab, straight–through or patch—cables will be used to connect workstations and switches.

In addition, two or more devices communicate through an address. The Network layer (Layer 3) requires a unique address (also known as a logical address or IP Addresses), which allows the data to reach the appropriate destination device.

Addressing for this lab will be applied to the workstations and will be used to enable communication between the devices.

of 210

Scenario

For the duration of this lab you will work in pairs. You will be using real hardware equipment.

This lab starts with the simplest form of networking (peer-to-peer) and ends with the lab connecting through a switch.

Task 1: Create a Peer-to-Peer Network.

Step 1: Obtain equipment and resources for the lab.

Equipment needed:2 workstations2 straight through (patch) cables1 crossover cable1 switch

Task 2: Identify the Cables used in a Network.

Before the devices can be cabled, you will need to identify the types of media you will be using. The cables used in this lab are crossover and straight-through.

Use a crossover cable to connect two workstations to each other through their NIC’s Ethernet port. This is an Ethernet cable. When you look at the plug you will notice that the orange and green wires are in opposite positions on each end of the cable.

Use a straight-through cable to connect the router’s Ethernet port to a switch port or a workstation to a switch port. This is also an Ethernet cable. When you look at the plug you will notice that both ends of the cable are exactly the same in each pin position.

Task 3: Cable the Peer-to-peer Network.

Step 1: Connect two workstations.

Using the correct Ethernet cable, connect two workstations together. Connect one end of the cable to the NIC port on PC1 and the other end of the cable to PC2.


Step 2: Apply a Layer 3 address to the workstations.

To complete this task, you will need to follow the step-by-step instructions below.

of 210

Note: These steps must be completed on each workstation. The instructions are for Windows XP—steps may differ slightly if you are using a different operating system.

1. On your computer, click Start, right-click My Network Places, and then click Properties. The Network Connections window should appear, with icons showing the different network connections.

2. Right-click the Local Area Connection and click Properties.3. Select the Internet Protocol (TCP/IP) item and then click the Properties button.

4. On the General tab of the Internet Protocol (TCP/IP) Properties window, select the Use the following IP address option.

5. In the IP address box, enter the IP address 192.168.1.2 for PC1. (Enter the IP address 192.168.1.3 for PC2.)

6. Press the tab key and the Subnet mask is automatically entered. The subnet address should be 255.255.255.0. If this address is not automatically entered, enter this address manually.

7. Click OK.

of 210

8. Close the Local Area Connection Properties window.


1. On your computer, click Start, and then click Run.

2. Type cmd in the Open box and then click OK.

The DOS command (cmd.exe) window will appear. You can enter DOS commands using this window. For the purposes of this lab, basic network commands will be entered to allow you to test your computer connections.

The ping command is a computer network tool used to test whether a host (workstation, router, server, etc.) is reachable across an IP network.

of 210

3. Use the ping command to verify that PC1 can reach PC2 and PC2 can reach PC1. From the PC1 DOS command prompt, type ping 192.168.1.3. From the PC2 DOS command prompt, type ping 192.168.1.2.

What is the output of the ping command?____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

If the ping command displays an error message or doesn’t receive a reply from the other workstation, troubleshoot as necessary. Possible areas to troubleshoot include:

Verifying the correct IP addresses on both workstations Ensuring that the correct type of cable is used between the workstations

What is the output of the ping command if you unplug the network cable and ping the other workstation?____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Task 4: Connect Your Workstations to the Classroom Lab Switch.

Step 1: Connect workstation to switch.

Using the correct cable, connect one end of the cable to the NIC port on the workstation and the other end to a port on the switch.

of 210

Threshold SOB 17

Step 2: Repeat this process for each workstation on your network.



Verify network connectivity by using the ping command to reach the other workstations attached to the switch.What is the output of the ping command?_________________________________________________________________________________________________________________________________________________________________________________________________________________________________

What is the output of the ping command if you ping an address that is not connected to this network?_________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Step 4: Share a document between PCs.

1. On your desktop, create a new folder and name it test.2. Right-click the folder and click File sharing. Note: A hand will be placed under the

icon.3. Place a file in the folder.4. On the desktop, double-click My Network Places and then Computers Near Me.5. Double-click the workstation icon. The test folder should appear. You will be able to

access this folder across the network. Once you are able to see it and work with the file, you have access through all 7 layers of the OSI model.

Task 5: Reflection

What could prevent a ping from being sent between the workstations when they are directly connected?_______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

of 210

Typical SOB 18

What could prevent the ping from being sent to the workstations when they are connected through the switch?_______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

of 210

Excellent SOB 19

Lab 8: Configure Initial Router Settings (Packet Tracer)

Objectives

Part 1: Verify the Default Router Configuration

Part 2: Configure and Verify the Initial Router Configuration

Part 3: Save the Running Configuration File

Background

For this lab, you will need to download the .pka file in the labs folder in week 10 from Moodle.

In this activity, you will perform basic router configurations. You will secure access to the CLI and console port using encrypted and plain text passwords. You will also configure messages for users logging into the router. These banners also warn unauthorized users that access is prohibited. Finally, you will verify and save your running configuration.

Task 1: Verify the Default Router Configuration

Step 1: Establish a console connection to R1.

a. Choose a Console cable from the available connections.b. Click PCA and select RS 232.c. Click R1 and select Console.d. Click PCA > Desktop tab > Terminal.e. Click OK and press ENTER. You are now able to configureR1.

Step 2: Enter privileged mode and examine the current configuration.

You can access all the router commands from privileged EXEC mode. However, because many of the privileged commands configure operating parameters, privileged access should be password-protected to prevent unauthorized use.

a. Enter privileged EXEC mode by entering the enable command.Router> enableRouter#Notice that the prompt changed in the configuration to reflect privileged EXEC mode.

b. Enter the show running-config command:Router# show running-config

c. Answer the following questions:What is the router’s hostname? _________________________

of 210

How many Fast Ethernet interfaces does the Router have? ______________How many Gigabit Ethernet interfaces does the Router have? ______________How many Serial interfaces does the router have? ______________What is the range of values shown for the vty lines? ______________

d. Display the current contents of NVRAM.Router# show startup-configstartup-config is not presentWhy does the router respond with the startup-config is not present message?____________________________________________________________________________________________________________________________________

Task 2: Configure and Verify the Initial Router Configuration

To configure parameters on a router, you may be required to move between various configuration modes. Notice how the prompt changes as you navigate through the router.

Step 1: Configure the initial settings on R1.

a. R1 as the hostname.Enter privileged EXEC modeRouter>enableRouter#Enter global configuration modeRouter#configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)#Configure the router name as R1Router(config)#hostname R1 R1(config)#

b. Use the following passwords:a. Console: letmein

R1(config)#line console 0 R1(config-line)#password letmein R1(config-line)#login R1(config-line)#exit R1(config)#

b. Privileged EXEC, unencrypted: ciscoR1(config)#enable password ciscoR1(config)#

c. Privileged EXEC, encrypted: itsasecret

of 210

Threshold SOB 20

R1(config)#enable secret itsasecretR1(config)#

c. Encrypt all plain text passwords.R1(config)# service password-encryptionR1(config)#

d. Message of the day text: Unauthorized access is strictly prohibited.R1(config)#banner motd &Enter TEXT message. End with the character '&'.AUTHORIZED ACCESS IS STRICKTLY PROHIBITED&R1(config)#

Step 2: Verify the initial settings on R1.

Note: If you cannot remember the commands, look up previous labs.

a. Verify the initial settings by viewing the configuration for R1. What command do you use? ___________________________________________________________

b. Exit the current console session until you see the following message:R1 con0 is now availablePress RETURN to get started.

c. Press ENTER; you should see the following message:AUTHORIZED ACCESS IS STRICKTLY PROHIBITED.User Access VerificationPassword:

Why should every router have a message-of-the-day (MOTD) banner?_____________________________________________________________________

If you are not prompted for a password, what console line command did you forget to configure? ___________________________________

d. Enter the passwords necessary to return to privileged EXEC mode.Why would the enable secret password allow access to the privileged EXEC mode and the enable password no longer be valid?__________________________________________________________________________________________________________________________________________

If you configure any more passwords on the router, are they displayed in the configuration file as plain text or in encrypted form? Explain.

_______________________________________________________________________________________________________________________________________________________________________________________________________________

of 210

Task 3: Save the Running Configuration File

Step 1: Save the configuration file to NVRAM.

a. You have configured the initial settings for R1. Now back up the running configuration file to NVRAM to ensure that the changes made are not lost if the system is rebooted or loses power.What command did you enter to save the configuration to NVRAM?_____________________________________________________________________What is the shortest, unambiguous version of this command?_____________________________________________________________________Which command displays the contents of the NVRAM?_____________________________________________________________________

of 210

Threshold SOB 21

Threshold SOB 22

Lab 9: Configure Initial Router Settings (Hardware Equipment)

Objectives

Part 1: Verify the Default Router Configuration

Part 2: Configure and Verify the Initial Router Configuration

Part 3: Save the Running Configuration File

Background

For this lab, you will need to work in pairs.

In this activity, you will perform basic router configurations. You will secure access to the CLI and console port using encrypted and plain text passwords. You will also configure messages for users logging into the router. These banners also warn unauthorized users that access is prohibited. Finally, you will verify and save your running configuration.

Equipment

1 router 2 PCs Console cable Straight cable

Task 1: Connect to the Router & Verify the Default Router Configuration

Step 1: Establish a console connection to router.

a. Connect a PC to the router via a Console cable.b. From your PC open a hyper terminal connection (see lab 5).

Step 2: Enter privileged mode and examine the current configuration.

You can access all the router commands from privileged EXEC mode. However, because many of the privileged commands configure operating parameters, privileged access should be password-protected to prevent unauthorized use.

a. Enter privileged EXEC mode by entering the enable command.Router> enableRouter#Notice that the prompt changed in the configuration to reflect privileged EXEC mode.

of 210

b. Enter the show running-config command:Router# show running-config

c. Answer the following questions:What is the router’s hostname? _______________How many Fast Ethernet interfaces does the Router have? ______________How many Gigabit Ethernet interfaces does the Router have? ______________How many Serial interfaces does the router have? ______________What is the range of values shown for the vty lines? ______________

Task 2: Configure and Verify the Initial Router Configuration

To configure parameters on a router, you may be required to move between various configuration modes. Notice how the prompt changes as you navigate through the router.

Step 1: Configure the initial settings on R1.

a. R1 as the hostname.Enter privileged EXEC modeRouter>enableRouter#Enter global configuration modeRouter#configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)#Configure the router name as R1Router(config)#hostname R1 R1(config)#

b. Use the following passwords:a. Console: letmein

R1(config)#line console 0 R1(config-line)#password letmein R1(config-line)#login R1(config-line)#exit R1(config)#

b. Privileged EXEC, unencrypted: ciscoR1(config)#enable password ciscoR1(config)#

c. Privileged EXEC, encrypted: itsasecretR1(config)#enable secret itsasecretR1(config)#

of 210

Typical SOB 23

c. Encrypt all plain text passwords.R1(config)# service password-encryptionR1(config)#

d. Message of the day text: Unauthorized access is strictly prohibited.R1(config)#banner motd &Enter TEXT message. End with the character '&'.AUTHORIZED ACCESS IS STRICKTLY PROHIBITED&R1(config)#

Step 2: Verify the initial settings on R1.

a. Verify the initial settings by viewing the configuration for R1. What command do you use? ___________________________________________________________

b. Exit the current console session until you see the following message:R1 con0 is now availablePress RETURN to get started.

c. Press ENTER; you should see the following message:Unauthorized access is strictly prohibited.User Access VerificationPassword:

Why should every router have a message-of-the-day (MOTD) banner?_____________________________________________________________________

If you are not prompted for a password, what console line command did you forget to configure? ___________________________________

d. Enter the passwords necessary to return to privileged EXEC mode.Why would the enable secret password allow access to the privileged EXEC mode and the enable password no longer be valid?__________________________________________________________________________________________________________________________________________

If you configure any more passwords on the router, are they displayed in the configuration file as plain text or in encrypted form? Explain.

____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

of 210

Typical SOB 24

Lab 10: Cabling a Network and Basic Router Configuration (Packet Tracer)

Topology Diagram

Addressing Table


R1Fa0/0 192.168.1.1 255.255.255.0 N/A

S0/0/0 192.168.2.1 255.255.255.0 N/A

R2Fa0/0 192.168.3.1 255.255.255.0 N/A

S0/0/0 192.168.2.2 255.255.255.0 N/A

PC1 N/A 192.168.1.10 255.255.255.0 192.168.1.1

PC2 N/A 192.168.3.10 255.255.255.0 192.168.3.1

Learning Objectives

Upon completion of this lab, you will be able to: Cable devices and establish console connections. Erase and reload the routers. Perform basic IOS command line interface operations. Perform basic router configuration. Verify and test configurations using show commands, ping and traceroute. Create a startup configuration file. Reload a startup configuration file.

Scenario

In this lab activity, you will review previously learned skills including cabling devices, establishing a console connection, and basic IOS command line interface operation and configuration commands. You will also learn to save configuration files and capture your configurations to a text file. The skills presented in this lab are essential to completing the rest of the labs in this course. You will be using Packet Tracer tool.

Show your work by answering questions where allocated.

of 210

Task 1: Cable the Ethernet Links of the Network.

Cable the Ethernet links for a network that is similar to the one in the Topology Diagram. The output used in this lab is from Cisco 1841 routers. But you can use any current router in your lab as long as it has the required interfaces as shown in the topology. A simple way to identify the available interfaces on a router is by entering the show ip interface brief command.

Which of the devices in the Topology Diagram require an Ethernet cable between them? ___________________________________________________________________________

Step 1: Connect the R1 Router to the S1 Switch.

Use a straight-through Ethernet cable to connect the FastEthernet 0/0 interface of the R1 router to the FastEthernet 0/1 interface on the S1 switch.

What colour is the link status light next to the FastEthernet 0/0 interface on R1? __________

What colour is the link status light next to the FastEthernet 0/1 interface on S1? ___________

Step 2: Connect PC1 to the S1 Switch.

Use a straight-through Ethernet cable to connect the network interface card (NIC) of PC1 to the FastEthernet 0/2 Interface of the S1 switch.

What colour is the link status light next to the NIC interface on PC1? ___________________

What colour is the link status light next to the FastEthernet 0/2 interface on S1? ___________

If the link status lights are not green, wait a few moments for the link between the two devices to become established. If the lights do not turn green after a few moments, check that you are using a straight-through Ethernet cable and that the power is on for the S1 switch and PC1.

Step 3: Connect PC2 to the R2 Router.

Use a crossover Ethernet cable to connect the FastEthernet 0/0 interface of the R2 router to the NIC of PC2. Because there is no switch between PC2 and the R2 router, a crossover cable is required for a direct link between the PC and the router.

What color is the link status light next to the NIC interface on PC2? __________________

What color is the link status light next to the FastEthernet 0/0 interface on R2? _________

of 210

Threshold SOB 25

Task 2: Cable the Serial Link between R1 and R2 Routers.

In a real-world WAN connection, the customer premises equipment (CPE), which is often a router, is the data terminal equipment (DTE). This equipment is connected to the service provider through a data circuit-terminating equipment (DCE) device, which is commonly a modem or channel service unit (CSU)/ data service unit (DSU). This device is used to convert the data from the DTE into a form acceptable to the WAN service provider.

Before you are able to connect the serial cables to the routers you would have to first provide the routers with the correct ports. Click on a router and in the physical tab power off the device, then choose the High-Speed WAN Interface Card from the left options. Drag the port plate to the allocated slot and power the device back on. Locate a DCE serial cable (with clock symbol) in your connections panel and connect R1 serial 0/0/0 port to R2 serial 0/0/0 port.

Task 3: Establish a connection to the R1 Router.

The console port is a management port used to provide out-of-band access to a router. It is used to set up the initial configuration of a router and to monitor it.

1. Click on the router and then click the CLI tab. Once the terminal window is open choose NO for the configuration dialog option and press RETURN.

2. Then press the Enter key again to start.

Task 4: Understand Command Line Basics.

Step 1: Enter privileged EXEC mode.

Router>enableRouter#

Step 2: Enter an incorrect command and observe the router response.

Router#comfigure terminal ^% Invalid input detected at '^' marker.

Router#

Command line errors occur primarily from typing mistakes. If a command keyword is incorrectly typed, the user interface uses the caret symbol (^) to identify and isolate the error.

of 210

Threshold SOB 26

The ^ appears at or near the point in the command string where an incorrect command, keyword, or argument was entered.

Step 3: Correct the previous command.

If a command is entered incorrectly, and the Enter key is pressed, the Up Arrow key on the keyboard can be pressed to repeat the last command. Use the Right Arrow and Left Arrow keys to move the cursor to the location where the mistake was made. Then make the correction. If something needs to be deleted, use the Backspace key. Use the directional keys and the Backspace key to correct the command to configure terminal, and then press Enter.

Router#configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)#

Step 4: Return to privileged EXEC mode with the exit command.

Router(config)#exit%SYS-5-CONFIG_I: Configured from console by consoleRouter#

Step 5: Examine the commands that are available for privileged EXEC mode.

A question mark, ?, can be entered at the prompt to display a list of available commands.

Router#?Exec commands: <1-99> Session number to resume clear Reset functions clock Manage the system clock configure Enter configuration mode connect Open a terminal connection copy Copy from one file to another debug Debugging functions (see also 'undebug') delete Delete a file dir List files on a filesystem disable Turn off privileged commands disconnect Disconnect an existing network connection enable Turn on privileged commands erase Erase a filesystem exit Exit from the EXEC logout Exit from the EXEC no Disable debugging informations ping Send echo messages reload Halt and perform a cold restart resume Resume an active network connection

of 210

setup Run the SETUP command facility show Show running system information --More--

Notice the --More-- at the bottom of the command output. The --More-- prompt indicates that there are multiple screens of output. When a --More-- prompt appears, press the Spacebar to view the next available screen. To display only the next line, press the Enter key. Press any other key to return to the prompt.

Step 6: View output.

View the rest of the command output by pressing the Spacebar. The remainder of the output will appear where the --More-- prompt appeared previously.

telnet Open a telnet connection traceroute Trace route to destination undebug Disable debugging functions (see also 'debug') vlan Configure VLAN parameters write Write running configuration to memory, network, or terminal

Step 7: Exit privileged EXEC mode with the exit command.

Router#exit

The following output should be displayed:

Router con0 is now available

Press RETURN to get started.

Step 8: Press the Enter key to enter user EXEC mode.

The Router> prompt should be visible.

Step 9: Type an abbreviated IOS command.

IOS commands can be abbreviated, as long as enough characters are typed for the IOS to recognize the unique command.

Enter only the character e at the command prompt and observe the results.

Router>e% Ambiguous command: "e"Router>

Enter en at the command prompt and observe the results.

Router>enRouter#

of 210

The abbreviated command en contains enough characters for the IOS to distinguish the enable command from the exit command.

Step 10: Press the Tab key after an abbreviated command to use auto-complete.

Typing an abbreviated command, such as conf, followed by the Tab key completes a partial command name. This functionality of the IOS is called auto-complete. Type the abbreviated command conf, press the Tab key, and observe the results.

Router#confRouter#configure

This auto-complete feature can be used as long as enough characters are typed for the IOS to recognize the unique command.

Step 11: Enter IOS commands in the correct mode.

IOS commands must be entered in the correct mode. For example, configuration changes cannot be made while in privileged EXEC mode. Attempt to enter the command hostname R1 at the privileged EXEC prompt and observe the results.

Router#hostname R1 ^% Invalid input detected at '^' marker.

Router#

Task 5: Perform Basic Configuration of Router R1.

Step 1: Establish a HyperTerminal session to router R1.


Router>enableRouter#

Step 3: Enter global configuration mode.

Router#configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)#

of 210

Typical SOB 27

Step 4: Configure the router name as R1.

Enter the command hostname R1 at the prompt.

Router(config)#hostname R1 R1(config)#

Step 5: Disable DNS lookup with the no ip domain-lookup command.

R1(config)#no ip domain-lookupR1(config)#

Why would you want to disable DNS lookup in a lab environment?______________________________________________________________________________________________________________________________________________________

What would happen if you disabled DNS lookup in a production environment?______________________________________________________________________________________________________________________________________________________

Step 6: Configure an EXEC mode password.

Configure an EXEC mode password using the enable secret password command. Use class for the password.

R1(config)#enable secret classR1(config)#

The enable secret command is used to provide an additional layer of security over the enable password command. The enable secret command provides better security by storing the enable secret password using a non-reversible cryptographic function. The added layer of security encryption provides is useful in environments where the password crosses the network or is stored on a TFTP server. When both the enable password and enable secret passwords are configured, the router expects the password as defined in the enable secret command. In this case, the router ignores the password defined in the enable password command.

What is the difference between enable secret and enable password commands?_________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Step 7: Remove the enable password.

Because the enable secret is configured, the enable password is no longer necessary. IOS commands can be removed from the configuration using the no form of the command.

R1(config)#no enable password

of 210

R1(config)#

Step 8: Configure a message-of-the-day banner using the banner motd command.

R1(config)#banner motd &Enter TEXT message. End with the character '&'.******************************** !!!AUTHORIZED ACCESS ONLY!!!********************************&R1(config)#

When does this banner display? ______________________________________________________________________________________________________________________________________________________

Why should every router have a message-of-the-day banner? ______________________________________________________________________________________________________________________________________________________

Step 9: Configure the console password on the router.

Use cisco as the password. When you are finished, exit from line configuration mode.R1(config)#line console 0 R1(config-line)#password cisco R1(config-line)#login R1(config-line)#exit R1(config)#

Step 10: Configure the password for the virtual terminal lines.

Use cisco as the password. When you are finished, exit from line configuration mode.R1(config)#line vty 0 4 R1(config-line)#password cisco R1(config-line)#login R1(config-line)#exit R1(config)#

Step 11: Configure the FastEthernet 0/0 interface with the IP address 192.168.1.1/24.

R1(config)#interface fastethernet 0/0R1(config-if)#ip address 192.168.1.1 255.255.255.0R1(config-if)#no shutdown

%LINK-5-CHANGED: Interface FastEthernet0/0, changed state to up

of 210

%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to upR1(config-if)#

Step 12: Use the description command to provide a description for this interface.

R1(config-if)#description R1 LAN R1(config-if)#

Step 13: Configure the Serial0/0/0 interface with the IP address 192.168.2.1/24.

Set the clock rate to 64000.

Note: Because the routers in the labs will not be connected to a live leased line, one of the routers will need to provide the clocking for the circuit. This is normally provided to each of the routers by the service provider. To provide this clocking signal in the lab, one of the routers will need to act as the DCE on the connection. This function is achieved by applying the clock rate 64000 command on the serial 0/0/0 interface, where the DCE end of the null modem cable has been connected. The purpose of the clock rate command is discussed further in Chapter 2, “Static Routes.”

R1(config-if)#interface serial 0/0/0R1(config-if)#ip address 192.168.2.1 255.255.255.0R1(config-if)#clock rate 64000R1(config-if)#no shutdownR1(config-if)#

When will the interface be active?___________________________________________________________________________


R1(config-if)#description Link to R2R1(config-if)#

Step 15: Use the end command to return to privileged EXEC mode.

R1(config-if)#endR1#

of 210

Threshold SOB 28


Step 1: For R2, repeat Steps 1 through 10 from Task 5.

Step 2: Configure the Serial 0/0/0 interface with the IP address 192.168.2.2/24.

R2(config)#interface serial 0/0/0R2(config-if)#ip address 192.168.2.2 255.255.255.0R2(config-if)#no shutdown

%LINK-5-CHANGED: Interface Serial0/0/0, changed state to up%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0, changed state to upR2(config-if)#




R2(config-if)#interface fastethernet 0/0R2(config-if)#ip address 192.168.3.1 255.255.255.0R2(config-if)#no shutdown

%LINK-5-CHANGED: Interface FastEthernet0/0, changed state to up%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to upR2(config-if)#


R1(config-if)#description R2 LANR1(config-if)#



of 210

Typical SOB 29

Task 7: Configure IP Addressing on the Host PCs.

Step 1: Configure the host PC1.

Configure the host PC1 that is attached to R1 with an IP address of 192.168.1.10/24 and a default gateway of 192.168.1.1.



Task 8: Examine Router show Commands.

There are many show commands that can be used to examine the operation of the router. In both privileged EXEC and user EXEC modes, the command show ? provides a list of available show commands. The list is considerably longer in privileged EXEC mode than it is in user EXEC mode.

Step 1: Examine the show running-config command.

The show running-config command is used to display the contents of the currently running configuration file. From privileged EXEC mode on the R1 router, examine the output of the show running-config command. If the –-More-- prompt appears, press the Spacebar to view the remainder of the command output.

R1#show running-config!version 12.3!hostname R1!!enable secret 5 $1$AFDd$0HCi0iYHkEWR4cegQdTQu/!no ip domain-lookup!interface FastEthernet0/0 description R1 LAN mac-address 0007.eca7.1511 ip address 192.168.1.1 255.255.255.0

of 210

Threshold SOB 30

duplex auto speed auto!interface FastEthernet0/1 mac-address 0001.42dd.a220 no ip address duplex auto speed auto shutdown!interface Serial0/0/0 description Link to R2 ip address 192.168.2.1 255.255.255.0 clock rate 64000!interface Serial0/0/1 no ip address shutdown!interface Vlan1 no ip address shutdown!ip classless!!!!line con 0 password ciscoline vty 0 4 password cisco login!end

Step 2: Examine the show startup-config command.

The show startup-config command displays the startup configuration file contained in NVRAM. From privileged EXEC mode on the R1 router, examine the output of the show startup-config command. If the –-More-- prompt appears, press the Spacebar to view the remainder of the command output.

R1#show startup-config Using 583 bytes

of 210

!version 12.3!hostname R1!!no ip domain-lookup!interface FastEthernet0/0 description R1 LAN mac-address 0007.eca7.1511 ip address 192.168.1.1 255.255.255.0 duplex auto speed auto!interface FastEthernet0/1 mac-address 0001.42dd.a220 no ip address duplex auto speed auto shutdown!interface Serial0/0/0 description Link to R2 ip address 192.168.2.1 255.255.255.0 clock rate 64000!interface Serial0/0/1 no ip address shutdown!interface Vlan1 no ip address shutdown!ip classless!!!!line con 0 password ciscoline vty 0 4 password cisco

of 210

login!end

Step 3: Examine the show interfaces command.

The show interfaces command displays statistics for all interfaces configured on the router. A specific interface can be added to the end of this command to display the statistics for only that interface. From privileged EXEC mode on the R1 router, examine the output of the show interfaces fastEthernet0/0 command. If the –-More-- prompt appears, press the Spacebar to view the remainder of the command output.

R1# show interfaces fastEthernet 0/0FastEthernet0/0 is up, line protocol is up (connected) Hardware is Lance, address is 0007.eca7.1511 (bia 0002.1625.1bea) Description: R1 LAN Internet address is 192.168.1.1/24 MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, rely 255/255, load 1/255 Encapsulation ARPA, loopback not set ARP type: ARPA, ARP Timeout 04:00:00, Last input 00:00:08, output 00:00:05, output hang never Last clearing of "show interface" counters never Queueing strategy: fifo Output queue :0/40 (size/max) 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 0 packets input, 0 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort 0 input packets with dribble condition detected 0 packets output, 0 bytes, 0 underruns 0 output errors, 0 collisions, 1 interface resets 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier 0 output buffer failures, 0 output buffers swapped outR1#

Step 4: Examine the show version command.

The show version command displays information about the currently loaded software version along with hardware and device information. From privileged EXEC mode on the R1 router, examine the output of the show version command. If the –-More-- prompt appears, press the Spacebar to view the remainder of the command output.

R1#show version

of 210

Cisco IOS Software, 1841 Software (C1841-IPBASE-M), Version 12.3(14)T7, RELEASE SOFTWARE (fc2)Technical Support: http://www.cisco.com/techsupportCopyright (c) 1986-2006 by Cisco Systems, Inc.Compiled Mon 15-May-06 14:54 by pt_team

ROM: System Bootstrap, Version 12.3(8r)T8, RELEASE SOFTWARE (fc1)

System returned to ROM by power-onSystem image file is "flash:c1841-ipbase-mz.123-14.T7.bin"

This product contains cryptographic features and is subject to UnitedStates and local country laws governing import, export, transfer anduse. Delivery of Cisco cryptographic products does not implythird-party authority to import, export, distribute or use encryption.Importers, exporters, distributors and users are responsible forcompliance with U.S. and local country laws. By using this product youagree to comply with applicable laws and regulations. If you are unableto comply with U.S. and local laws, return this product immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email [email protected].

Cisco 1841 (revision 5.0) with 114688K/16384K bytes of memory.Processor board ID FTX0947Z18EM860 processor: part number 0, mask 492 FastEthernet/IEEE 802.3 interface(s)2 Low-speed serial(sync/async) network interface(s)191K bytes of NVRAM.31360K bytes of ATA CompactFlash (Read/Write)

Configuration register is 0x2102

R1#

Step 5: Examine the show ip interface brief command.

The show ip interface brief command displays a summary of the usability status information for each interface. From privileged EXEC mode on the R1 router, examine the output of the show ip interface brief command. If the –-More-- prompt appears, press the Spacebar to view the remainder of the command output.

of 210

R1#show ip interface briefInterface IP-Address OK? Method Status Protocol FastEthernet0/0 192.168.1.1 YES manual up up FastEthernet0/1 unassigned YES manual administratively down down Serial0/0/0 192.168.2.1 YES manual up up Serial0/0/1 unassigned YES manual administratively down down Vlan1 unassigned YES manual administratively down downR1#

Task 9: Using ping.

The ping command is a useful tool for troubleshooting Layers 1 though 3 of the OSI model and diagnosing basic network connectivity. This operation can be performed at either the user or privileged EXEC modes. Using ping sends an Internet Control Message Protocol (ICMP) packet to the specified device and then waits for a reply. Pings can be sent from a router or a host PC.

Step 1: Use the ping command to test connectivity between the R1 router and PC1.

What is the command used? _________________________________________________Where all attempts successful? _______________________________________________If not which were not and why? ______________________________________________ ________________________________________________________________________________________________________________________________________________

Step 2: Repeat the ping from R1 to PC1.

Were all attempts successful? ________________________________________________If yes why? ______________________________________________________________

Step 3: Send an extended ping from R1 to PC1.

To accomplish this, type ping at the privileged EXEC prompt and press Enter. Fill out the rest of the prompts as shown:

R1#ping

of 210

Threshold SOB 31

Protocol [ip]: Target IP address: 192.168.1.10Repeat count [5]: 10Datagram size [100]: Timeout in seconds [2]: Extended commands [n]: Sweep range of sizes [n]: Type escape sequence to abort.Sending 10, 100-byte ICMP Echos to 192.168.1.10, timeout is 2 seconds:!!!!!!!!!!Success rate is 100 percent (10/10), round-trip min/avg/max = 53/77/94 ms

R1#

Step 4: Send a ping from PC1 to R1.

From Windows go to Start > Programs > Accessories > Command Prompt. In the Command Prompt window that opens, ping R1 by issuing the following command:

Was ping response successful? __________________________________________________

Step 5: Send an extended ping from PC1 to R1.

To accomplish this, enter the following command at the Windows command prompt:

C:\>ping 192.168.1.1 –n 10

There should be 10 successful responses from the command.

Task 10: Using Traceroute.

The traceroute command is an excellent utility for troubleshooting the path that a packet takes through an internetwork of routers. It can help to isolate problem links and routers along the way. The traceroute command uses ICMP packets and the error message generated by routers when the packet exceeds its Time-To-Live (TTL). This operation can be performed at either the user or privileged EXEC modes. The Windows version of this command is tracert.

of 210

Threshold SOB 32

Step 1: Use the traceroute command at the R1 privileged EXEC prompt to discover the path that a packet will take from the R1 router to PC1.

R1#traceroute 192.168.1.10Type escape sequence to abort.Tracing the route to 192.168.1.10

1 192.168.1.10 103 msec 81 msec 70 msec R1#

Step 2: Use the tracert command at the Windows command prompt to discover the path that a packet will take from the R1 router to PC1.

C:\>tracert 192.168.1.1

Tracing route to 192.168.1.1 over a maximum of 30 hops:

1 71 ms 70 ms 73 ms 192.168.1.1

Trace complete.C:\>

of 210

Threshold SOB 33

Lab 11: Cabling a Network and Basic Router Configuration (Hardware Equipment)

Topology Diagram

Addressing Table


R1Fa0/0 192.168.1.1 255.255.255.0 N/A

S0/0/0 192.168.2.1 255.255.255.0 N/A

R2Fa0/0 192.168.3.1 255.255.255.0 N/A

S0/0/0 192.168.2.2 255.255.255.0 N/A

PC1 N/A 192.168.1.10 255.255.255.0 192.168.1.1

PC2 N/A 192.168.3.10 255.255.255.0 192.168.3.1

Learning Objectives

Upon completion of this lab, you will be able to: Cable devices and establish console connections. Erase and reload the routers. Perform basic IOS command line interface operations. Perform basic router configuration. Verify and test configurations using show commands, ping and traceroute. Create a startup configuration file. Reload a startup configuration file. Install a terminal emulation program.

Scenario

In this lab activity, you will review previously learned skills including cabling devices, establishing a console connection, and basic IOS command line interface operation and configuration commands. You will also learn to save configuration files and capture your configurations to a text file. The skills presented in this lab are essential to completing the rest of the labs in this course.

For this lab exercise you will have to work in pairs. You will be using real hardware equipment. Show your work by answering questions where allocated.

of 210

Task 1: Cable the Ethernet Links of the Network.

Cable the Ethernet links for a network that is similar to the one in the Topology Diagram. The output used in this lab is from Cisco 1841 routers. But you can use any current router in your lab as long as it has the required interfaces as shown in the topology. A simple way to identify the available interfaces on a router is by entering the show ip interface brief command.

Which of the devices in the Topology Diagram require an Ethernet cable between them?

___________________________________________________________________________

Step 1: Connect the R1 Router to the S1 Switch.

Use a straight-through Ethernet cable to connect the FastEthernet 0/0 interface of the R1 router to the FastEthernet 0/1 interface on the S1 switch.

Step 2: Connect PC1 to the S1 Switch.

Use a straight-through Ethernet cable to connect the network interface card (NIC) of PC1 to the FastEthernet 0/2 Interface of the S1 switch.

Step 3: Connect PC2 to the R2 Router.

Use a crossover Ethernet cable to connect the FastEthernet 0/0 interface of the R2 router to the NIC of PC2. Because there is no switch between PC2 and the R2 router, a crossover cable is required for a direct link between the PC and the router.

Task 2: Cable the Serial Link between R1 and R2 Routers.

In a real-world WAN connection, the customer premises equipment (CPE), which is often a router, is the data terminal equipment (DTE). This equipment is connected to the service provider through a data circuit-terminating equipment (DCE) device, which is commonly a modem or channel service unit (CSU)/ data service unit (DSU). This device is used to convert the data from the DTE into a form acceptable to the WAN service provider.

Unlike the cables in the academy lab setup, the serial cables in the real world are not connected back to back. In a real-world situation, one router might be in New York, while another router might be in Sydney, Australia. An administrator located in Sydney would have to connect to the router in New York through the WAN cloud in order to troubleshoot the New York router.

of 210

Threshold SOB 34

In the academy labs, devices that make up the WAN cloud are simulated by the connection between the back-to-back DTE-DCE cables. The connection from one router serial interface to another router serial interface simulates the whole circuit cloud.

Step 1: Create a null serial cable to connect the R1 router to the R2 router.

In the academy labs, the WAN connection between routers uses one DCE cable and one DTE cable. The DCE-DTE connection between routers is referred to as a null serial cable. The labs will use one V.35 DCE cable and one V.35 DTE cable to simulate the WAN connection. The V.35 DCE connector is usually a female V.35 (34-pin) connector. The DTE cable has a male V.35 connector. The cables are also labeled as DCE or DTE on the router end of the cable.

The DTE and DCE V.35 cables must be joined together. Holding one of the V.35 ends in each hand, examine the pins and sockets as well as the threaded connectors. Note that there is only one proper way for the cables to fit together. Align the pins on the male cable with the sockets on the female cable and gently couple them. Very little effort should be required to accomplish this. When they are joined, turn the thumbscrews clockwise and secure the connectors.

Step 2: Connect the DCE end of the null serial cable to the Serial 0/0/0 interface of the R1 router, and the DTE end of the null serial cable to the Serial 0/0/0 interface of the R2 router.

Review the information provided below before making these connections.Before making the connection to one of the routers, examine the connector on the router and the cable. Note that the connectors are tapered to help prevent improper connection. Holding the connector in one hand, orient the cable and router connecters so that the tapers match. Now push the cable connector partially into the router connector. It probably will not go in all the way because the threaded connectors need to be tightened in order for the cable to be inserted completely. While holding the cable in one hand and gently pushing the cable toward the router, turn one of the thumb screws clockwise, 3 or 4 rounds, to start the screws. Now turn the other thumbscrew clockwise, 3 or 4 rounds, to get it started. At this point the cable should be attached sufficiently to free both hands to advance each thumbscrew at the same rate until the cable is fully inserted. Do not over-tighten these connectors.

Task 3: Establish a Console connection to R1 Router.

The console port is a management port used to provide out-of-band access to a router. It is used to set up the initial configuration of a router and to monitor it.

of 210

Threshold SOB 35

A rollover cable and an RJ-45 to DB-9 adapter are used to connect a PC to the console port. As you know from your previous studies, terminal emulation software is used to configure the router over the console connection. The Cisco Networking Academy Program recommends using Tera Term. However, you can also use HyperTerminal, which is part of the Windows operating system, or you can use Putty.

Step 1: Examine the router and locate the RJ-45 connector labeled Console.

Step 2: Examine PC1 and locate a 9-pin male connector serial port.

It may—or may not—be labeled as COM1 or COM2.

Step 3: Locate the console cable.

Some console cables have an RJ-45 to DB-9 adapter built into one end. Others do not. Locate either a console cable with a built-in adapter or a console cable with a separate RJ-45 to DB-9 adapter attached to one end.

Step 4: Connect the console cable to the router and PC.

First, connect the console cable to the router console port, an RJ-45 connector. Next, connect the DB-9 end of the console cable to the serial port of PC1.

Step 5: Test router connection.

1. Open your terminal emulation software (HyperTerminal, Tera Term, or other software specified by your instructor).

2. Once the terminal window is open, press the Enter key. There should be a response from the router. If there is, then the connection has been successfully completed. If there is no connection, troubleshoot as necessary. For example, verify that the router has power. Check the connection to the serial port on the PC and the console port on the router.

Was connection successful? _________________

Task 4: Erase and Reload the Routers.

Step 1: Using the HyperTerminal session established in Task 3, enter privileged EXEC mode on R1.

Write down the command to enter Privileged EXEC mode.________________________________________________________________________

of 210

Threshold SOB 36

Step 2: Erase the configuration.

To clear the configuration, issue the erase startup-config command. Confirm the objective when prompted, and answer no if asked to save changes. The result should look something like this:

Router#erase startup-configErasing the nvram filesystem will remove all files! Continue? [confirm][OK]Erase of nvram: completeRouter#

Step 3: Reload the configuration.

When the prompt returns, issue the reload command. Confirm the objective when prompted. After the router finishes the boot process, choose not to use the AutoInstall facility, as shown:

Would you like to enter the initial configuration dialog? [yes/no]: noWould you like to terminate autoinstall? [yes]: Press Enter to accept default.Press RETURN to get started!

Step 4: Establish a HyperTerminal Session to R2.

Repeat Steps 1 through 3 to remove any startup configuration file that may be present.


Step 1: Establish a HyperTerminal session to router R1.


Write down the command to enter Privileged EXEC mode.________________________________________________________________________


Write down the command to enter global configuration mode.________________________________________________________________________

of 210

Threshold SOB 37

Step 4: Configure the router name as R1.

Enter the command hostname R1 at the prompt.

Router(config)#hostname R1 R1(config)#

Step 5: Disable DNS lookup with the no ip domain-lookup command.

R1(config)#no ip domain-lookupR1(config)#

Why would you want to disable DNS lookup in a lab environment?

______________________________________________________________________________________________________________________________________________________

What would happen if you disabled DNS lookup in a production environment?

______________________________________________________________________________________________________________________________________________________

Step 6: Configure an EXEC mode password.

Configure an EXEC mode password using the enable secret password command. Use class for the password.

R1(config)#enable secret classR1(config)#

The enable secret command is used to provide an additional layer of security over the enable password command. The enable secret command provides better security by storing the enable secret password using a non-reversible cryptographic function. The added layer of security encryption provided is useful in environments where the password crosses the network or is stored on a TFTP server. When both the enable password and enable secret passwords are configured, the router expects the password as defined in the enable secret command. In this case, the router ignores the password defined in the enable password command.

Step 7: Remove the enable password.

Because the enable secret is configured, the enable password is no longer necessary. IOS commands can be removed from the configuration using the no form of the command.

R1(config)#no enable passwordR1(config)#

of 210

Step 8: Configure a message-of-the-day banner using the banner motd command.

R1(config)#banner motd &Enter TEXT message. End with the character '&'.******************************** !!!AUTHORIZED ACCESS ONLY!!!********************************&R1(config)#

When does this banner display? ______________________________________________________________________________________________________________________________________________________

Why should every router have a message-of-the-day banner? ______________________________________________________________________________________________________________________________________________________

Step 9: Configure the console password on the router.

Use cisco as the password. When you are finished, exit from line configuration mode.R1(config)#line console 0 R1(config-line)#password cisco R1(config-line)#login R1(config-line)#exit R1(config)#

Step 10: Configure the password for the virtual terminal lines.

Use cisco as the password. When you are finished, exit from line configuration mode.R1(config)#line vty 0 4 R1(config-line)#password cisco R1(config-line)#login R1(config-line)#exit R1(config)#


Which mode is the command entered from? ____________________________________

Write the full sequence of commands to configure the interface above.____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

of 210


R1(config-if)#description R1 LAN R1(config-if)#

Step 13: Configure the Serial0/0/0 interface with the IP address 192.168.2.1/24.

Set the clock rate to 64000.

Note: Because the routers in the labs will not be connected to a live leased line, one of the routers will need to provide the clocking for the circuit. This is normally provided to each of the routers by the service provider. To provide this clocking signal in the lab, one of the routers will need to act as the DCE on the connection. This function is achieved by applying the clock rate 64000 command on the serial 0/0/0 interface, where the DCE end of the null modem cable has been connected. The purpose of the clock rate command is discussed further in Chapter 2, “Static Routes.”

R1(config-if)#interface serial 0/0/0R1(config-if)#ip address 192.168.2.1 255.255.255.0R1(config-if)#clock rate 64000R1(config-if)#no shutdownR1(config-if)#

Note: The interface will not be activated until the serial interface on R2 is configured and activated.





of 210

Typical SOB 38


Step 1: For R2, repeat Steps 1 through 10 from Task 6.

Step 2: Configure the Serial 0/0/0 interface with the IP address 192.168.2.2/24.

Write commands used.________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________




Write commands used.________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________


R1(config-if)#description R2 LANR1(config-if)#






of 210

Typical SOB 39



Task 8: Examine Router Show Commands.

There are many show commands that can be used to examine the operation of the router. In both privileged EXEC and user EXEC modes, the command show ? provides a list of available show commands. The list is considerably longer in privileged EXEC mode than it is in user EXEC mode.

Step 1: Examine the show running-config command.

The show running-config command is used to display the contents of the currently running configuration file. From privileged EXEC mode on the R1 router, examine the output of the show running-config command. If the –-More-- prompt appears, press the Spacebar to view the remainder of the command output.

What information is displayed when you enter show running-config command?_______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Step 2: Examine the show startup-config command.

The show startup-config command displays the startup configuration file contained in NVRAM. From privileged EXEC mode on the R1 router, examine the output of the show startup-config command. If the –-More-- prompt appears, press the Spacebar to view the remainder of the command output.

What are the differences between the outputs of show startup-config and show running config? Why?

_______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Step 3: Examine the show interfaces command.

The show interfaces command displays statistics for all interfaces configured on the router. A specific interface can be added to the end of this command to display the statistics for only that interface. From privileged EXEC mode on the R1 router, examine the output of the show

of 210

interfaces fastEthernet0/0 command. If the –-More-- prompt appears, press the Spacebar to view the remainder of the command output.

How many interfaces show as up? _________________

List all up interfaces and enter their IP addresses

____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Step 4: Examine the show version command.

The show version command displays information about the currently loaded software version along with hardware and device information. From privileged EXEC mode on the R1 router, examine the output of the show version command. If the –-More-- prompt appears, press the Spacebar to view the remainder of the command output.

What version is used on the router? ______________________________________

Step 5: Examine the show ip interface brief command.

The show ip interface brief command displays a summary of the usability status information for each interface. From privileged EXEC mode on the R1 router, examine the output of the show ip interface brief command. If the –-More-- prompt appears, press the Spacebar to view the remainder of the command output.

R1#show ip interface briefInterface IP-Address OK? Method Status Protocol FastEthernet0/0 192.168.1.1 YES manual up up FastEthernet0/1 unassigned YES manual administratively down down Serial0/0/0 192.168.2.1 YES manual up up Serial0/0/1 unassigned YES manual administratively down down Vlan1 unassigned YES manual administratively down downR1#

of 210

Typical SOB 40

Task 9: Using ping.

The ping command is a useful tool for troubleshooting Layers 1 through 3 of the OSI model and diagnosing basic network connectivity. This operation can be performed at either the user or privileged EXEC modes. Using ping sends an Internet Control Message Protocol (ICMP) packet to the specified device and then waits for a reply. Pings can be sent from a router or a host PC.

Step 1: Use the ping command to test connectivity between the R1 router and PC1.

R1#ping 192.168.1.10

What was the response?

_______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Step 2: Repeat the ping from R1 to PC1.

R1#ping 192.168.1.10

Were all pings successful? _____________________________________________________

Step 3: Send an extended ping from R1 to PC1.

To accomplish this, type ping at the privileged EXEC prompt and press Enter. Fill out the rest of the prompts as shown:

R1#pingProtocol [ip]: Target IP address: 192.168.1.10Repeat count [5]: 10Datagram size [100]: Timeout in seconds [2]: Extended commands [n]: Sweep range of sizes [n]: Type escape sequence to abort.Sending 10, 100-byte ICMP Echos to 192.168.1.10, timeout is 2 seconds:!!!!!!!!!!Success rate is 100 percent (10/10), round-trip min/avg/max = 53/77/94 ms

R1#

of 210

Step 4: Send a ping from PC1 to R1.

From Windows go to Start > Programs > Accessories > Command Prompt. In the Command Prompt window that opens, ping R1 by issuing the following command:

C:\> ping 192.168.1.1

The ping should respond with successful results.

Step 5: Send an extended ping from PC1 to R1.

To accomplish this, enter the following command at the Windows command prompt:

C:\>ping 192.168.1.1 –n 10

There should be 10 successful responses from the command

Task 10: Using Traceroute.

The traceroute command is an excellent utility for troubleshooting the path that a packet takes through an internetwork of routers. It can help to isolate problem links and routers along the way. The traceroute command uses ICMP packets and the error message generated by routers when the packet exceeds its Time-To-Live (TTL). This operation can be performed at either the user or privileged EXEC modes. The Windows version of this command is tracert.

Step 1: Use the traceroute command at the R1 privileged EXEC prompt to discover the path that a packet will take from the R1 router to PC1.

R1#traceroute 192.168.1.10Type escape sequence to abort.Tracing the route to 192.168.1.10

1 192.168.1.10 103 msec 81 msec 70 msec R1#

Step 2: Use the tracert command at the Windows command prompt to discover the path that a packet will take from the R1 router to PC1.

C:\>tracert 192.168.1.1

Tracing route to 192.168.1.1 over a maximum of 30 hops:

1 71 ms 70 ms 73 ms 192.168.1.1

of 210

Trace complete.

C:\>

Task 11: Create a start.txt File.

Router configurations can be captured to a text (.txt) file and saved for later use. The configuration can be copied back to the router so that the commands do not have to be entered one at a time.

Step 1: View the running configuration of the router using the show running-config command.

R1#show running-config

Step 2: Copy the command output.

Select the command output. From the HyperTerminal Edit menu, choose the copy command.

Step 3: Paste output in Notepad.

Open Notepad. Notepad is typically found on the Start menu under Programs > Accessories. From the Notepad Edit menu, click Paste.

Step 4: Edit commands.

Some commands will have to be edited or added before the startup script can be applied to a router. Some of these changes are:

Adding a no shutdown command to FastEthernet and serial interfaces that are being used.

Replacing the encrypted text in the enable secret command with the appropriate password.

Removing the mac-address command from the interfaces.Removing the ip classless command.Removing unused interfaces.

Edit the text in the Notepad file as shown below:

hostname R1!

of 210

Typical SOB 41

!enable secret class!no ip domain-lookup!interface FastEthernet0/0 description R1 LAN ip address 192.168.1.1 255.255.255.0 no shutdown duplex auto speed auto!interface Serial0/0/0 description Link to R2 ip address 192.168.2.1 255.255.255.0 clock rate 64000 no shutdown!!!!line con 0 password ciscoline vty 0 4 password cisco login!End

Step 5: Save the open file in Notepad to start.txt.

Task 12: Load the start.txt File onto R1 Router.

Step 1: Erase the current startup configuration of R1.

Confirm the objective when prompted, and answer no if asked to save changes. The result should look something like this:

R1#erase startup-configErasing the nvram filesystem will remove all files! Continue? [confirm]

of 210

Threshold SOB 42

[OK]Erase of nvram: completeRouter#

Step 2: When the prompt returns, issue the reload command.

Confirm the objective when prompted. After the router finishes the boot process, choose not to use the AutoInstall facility, as shown:

Would you like to enter the initial configuration dialog? [yes/no]: noWould you like to terminate autoinstall? [yes]: Press Enter to accept default.Press RETURN to get started!


Router#configure terminal Enter configuration commands, one per line. End with CNTL/Z.Router(config)#

Step 4: Copy the commands.

In the start.txt file that was created in Notepad, select all the lines, and then choose Edit > Copy.

Step 5: From the HyperTerminal Edit menu, choose Paste to Host.

Step 6: Verify the running configuration.

After all of the pasted commands have been applied, use the show running-config command to verify that the running configuration appears as expected.

of 210

Threshold SOB 43

Lab 12: IPv4 Address Subnetting (part 1)

Learning Objectives

Upon completion of this activity, you will be able to determine network information for a given IP address and network mask.

Background

This activity is designed to teach how to compute network IP address information from a given IP address.

Scenario

When given an IP address and network mask, you will be able to determine other information about the IP address such as:

Network address Network broadcast address Total number of host bits Number of hosts

Task 1: For a given IP address, Determine Network Information.

Given:Host IP Address 172.200.114.250Network Mask 255.255.0.0 (/16)

Find:Network AddressNetwork Broadcast AddressTotal Number of Host BitsNumber of Hosts

Step 1: Translate Host IP address and network mask into binary notation.

Convert the host IP address and network mask to binary:

172 200 114 250IP Address 10101100 11001000 01110010 11111010Network Mask 11111111 11111111 00000000 00000000

255 255 0 0

of 210

Step 2: Determine the network address.

1. Draw a line under the mask.2. Perform a bit-wise AND operation on the IP address and the subnet mask.

Note: 1 AND 1 results in a 1; 0 AND anything results in a 0.

3. Express the result in dotted decimal notation.4. The result is the network address for this host IP address, which is 172.200.0.0.

172 200 114 250IP Address 10101100 11001000 01110010 11111010Subnet Mask 11111111 11111111 00000000 00000000Network Add 10101100 11001000 00000000 00000000

172 200 0 0

Step 3: Determine the broadcast address for the network address

The network mask separates the network portion of the address from the host portion. The network address has all 0s in the host portion of the address and the broadcast address has all 1s in the host portion of the address.

172 200 0 0Network Add. 10101100 11001000 00000000 00000000Mask 11111111 11111111 00000000 00000000Broadcast. 10101100 11001000 11111111 11111111

172 200 255 255

By counting the number of host bits, we can determine the total number of usable hosts for this network.

Host bits: 16

Total number of hosts:

216 = 65,536

65,536 – 2 = 65,534 (addresses that cannot use the all 0s address, network address, or the all 1s address, broadcast address.)

Add this information to the table:

Host IP Address 172.200.114.250Network Mask 255.255.0.0 (/16)Network AddressNetwork Broadcast

of 210

AddressTotal Number of Host BitsNumber of Hosts

Task 2: Challenge

For all problems:

Create a Subnetting Worksheet to show and record all work for each problem.

Problem 1Host IP Address 172.30.1.33Network Mask 255.255.0.0Network AddressNetwork Broadcast AddressTotal Number of Host BitsNumber of Hosts




of 210



of 210

Threshold SOB 44

Lab 13: IPv4 Address Subnetting (part 2)

Learning Objectives

Upon completion of this activity, you will be able to determine subnet information for a given IP address and subnetwork mask.

Background

Borrowing Bits

How many bits must be borrowed to create a certain number of subnets or a certain number of hosts per subnet?

Using this chart, it is easy to determine the number of bits that must be borrowed.

Things to remember:

Subtract 2 for the usable number of hosts per subnet, one for the subnet address and one for the broadcast address of the subnet.

210 29 28 27 26 25 24 23 22 21 20

1,024 512 256 128 64 32 16 8 4 2 1Number of bits borrowed:

10 9 8 7 6 5 4 3 2 1 11,024 512 256 128 64 32 16 8 4 2 1

Hosts or Subnets

Possible Subnet Mask Values

Because subnet masks must be contiguous 1’s followed by contiguous 0’s, the converted dotted decimal notation can contain one of a certain number of values:

Dec. Binary255 11111111254 11111110252 11111100248 11111000240 11110000224 11100000192 11000000128 100000000 00000000

of 210

Scenario

When given an IP address, network mask, and subnetwork mask, you will be able to determine other information about the IP address such as:

The subnet address of this subnet The broadcast address of this subnet The range of host addresses for this subnet The maximum number of subnets for this subnet mask The number of hosts for each subnet The number of subnet bits The number of this subnet

Task 1: For a Given IP Address and Subnet Mask, Determine Subnet Information.

Given:

Host IP Address 172.200.114.250Network Mask 255.255.0.0 (/16)Subnet Mask 255.255.255.192 (/26)

Find:

Number of Subnet BitsNumber of SubnetsNumber of Host Bits per SubnetNumber of Usable Hosts per SubnetSubnet Address for this IP AddressIP Address of First Host on this SubnetIP Address of Last Host on this SubnetBroadcast Address for this Subnet

Step 1: Translate host IP address and subnet mask into binary notation.

172 200 114 250IP Address 10101100 11001000 01110010 11111010

11111111 11111111 11111111 11000000Subnet Mask 255 255 255 192

Step 2: Determine the network (or subnet) where this host address belongs.

1. Draw a line under the mask.2. Perform a bit-wise AND operation on the IP Address and the Subnet Mask.

of 210

Note: 1 AND 1 results in a 1’ 0 AND anything results in a 0.

3. Express the result in dotted decimal notation.4. The result is the Subnet Address of this Subnet, which is 172.25.114.192

172 200 114 250IP Address 10101100 11001000 01110010 11111010Subnet Mask 11111111 11111111 11111111 11000000Subnet Add. 10101100 11001000 01110010 11000000

172 200 114 192

Add this information to the table:

Subnet Address for this IP Address 172.200.114.192

Step 3: Determine which bits in the address contain network information and which contain host information.

1. Draw the Major Divide (M.D.) as a wavy line where the 1s in the major network mask end (also the mask if there was no subnetting). In our example, the major network mask is 255.255.0.0, or the first 16 left-most bits.

2. Draw the Subnet Divide (S.D.) as a straight line where the 1s in the given subnet mask end. The network information ends where the 1s in the mask end.

M.D S.DIP Address 10101100 11001000 01110010 11111010Subnet Mask 11111111 11111111 11111111 11000000Subnet Add. 10101100 11001000 01110010 11000000 ← 10 bits →

3. The result is the Number of Subnet Bits, which can be determined by simply counting the number of bits between the M.D. and S.D., which in this case is 10 bits.

Step 4: Determine the bit ranges for subnets and hosts.

1. Label the subnet counting range between the M.D. and the S.D. This range contains the bits that are being incremented to create the subnet numbers or addresses.

2. Label the host counting range between the S.D. and the last bits at the end on the right. This range contains the bits that are being incremented to create the host numbers or addresses.

of 210

M.D S.DIP Address 10101100 11001000 01110010 11111010Subnet Mask 11111111 11111111 11111111 11000000Subnet Add. 10101100 11001000 01110010 11000000 ← Subnet → ← Host → counting counting range range

Step 5: Determine the range of host addresses available on this subnet and the broadcast address on this subnet.

1. Copy down all of the network/subnet bits of the network address (that is, all bits before the S.D.).

2. In the host portion (to the right of the S.D.), make the host bits all 0s except for the right-most bit (or least significant bit), which you make a 1. This gives us the first host IP address on this subnet, which is the first part of the result for Range of Host Addresses for This Subnet, which in the example is 172.200.114.193.

3. Next, in the host portion (to the right of the S.D.), make the host bits all 1s except for the rightmost bit (or least significant bit), which you make a 0. This gives us the last host IP address on this subnet, which is the last part of the result for Range of Host Addresses for This Subnet, which in the example is 172.200.114.254.

4. In the host portion (to the right of the S.D.), make the host bits all 1s. This gives us the broadcast IP address on this subnet. This is the result for Broadcast Address of This Subnet, which in the example is 172.25.114.255.

M.D S.DIP Address 10101100 11001000 01110010 11111010Subnet Mask 11111111 11111111 11111111 11000000

Subnet Add. 10101100 11001000 01110010 11000000

← Subnet → ← Host → counting counting range rangeFirst Host 10101100 11001000 01110010 11000001

172 200 114 193Last Host 10101100 11001000 01110010 11111110

172 200 114 254Broadcast 10101100 11001000 01110010 11111111

172 200 114 255

Let’s add some of this information to our table:

of 210

Host IP Address 172.200.114.250Major Network Mask 255.255.0.0 (/16)Major (Base) Network Address 172.200.0.0Major Network Broadcast Address 172.25.255.255

Total Number of Host Bits 16 bits or 216 or 65,536 total hosts

Number of Hosts 65,536 – 2 = 65,534 usable hostsSubnet Mask 255.255.255.192 (/26)Number of Subnet BitsNumber of SubnetsNumber of Host Bits per SubnetNumber of Usable Hosts per SubnetSubnet Address for this IP AddressIP Address of First Host on this SubnetIP Address of Last Host on this SubnetBroadcast Address for this Subnet

Step 6: Determine the number of subnets.

The number of subnets is determined by how many bits are in the subnet counting range (in this example, 10 bits).

Use the formula 2n, where n is the number of bits in the subnet counting range.

210 = 1024

Number of Subnet Bits 10 bitsNumber of Subnets(all 0s used, all 1s not used) 210 = 1024 subnets

Step 7: Determine the number usable hosts per subnet.

The number of hosts per subnet is determined by the number of host bits (in this example, 6 bits) minus 2 (1 for the subnet address and 1 for the broadcast address of the subnet).

26 – 2 = 64 – 2 = 62 hosts per subnetNumber of Host Bits per Subnet 6 bitsNumber of Usable Hosts per Subnet

26 – 2 = 64 – 2 = 62 hosts per subnet

of 210

Step 8: Final Answers

Host IP Address 172.200.114.250Subnet Mask 255.255.255.192 (/26)Number of Subnet Bits 26 bitsNumber of Subnets 210 = 1024 subnetsNumber of Host Bits per Subnet 6 bitsNumber of Usable Hosts per Subnet 26 – 2 = 64 – 2 = 62 hosts per subnetSubnet Address for this IP Address 172.200.114.192IP Address of First Host on this Subnet 172.200.114.193

IP Address of Last Host on this Subnet 172.200.114.254

Broadcast Address for this Subnet 172.200.114.255

Task 2: Challenge.

For all problems:Create a Subnetting Worksheet to show and record all work for each problem.

Problem 1

Host IP Address 172.30.1.33Subnet Mask 255.255.255.0Number of Subnet BitsNumber of SubnetsNumber of Host Bits per SubnetNumber of Usable Hosts per SubnetSubnet Address for this IP AddressIP Address of First Host on this SubnetIP Address of Last Host on this SubnetBroadcast Address for this Subnet

Problem 2


of 210

Problem 3


Problem 4


Problem 5


of 210

Problem 6


of 210

Threshold SOB 45

Lab 14: Troubleshooting a Small Network (Packet Tracer)

Topology Diagram

Learning Objectives

Upon completion of this lab, you will be able to: • Verify that a paper design meets stated network requirements • Cable a network according to the topology diagram • Erase the startup configuration and reload a router to the default state • Load the routers with supplied scripts • Discover where communication is not possible • Gather information about the misconfigured portion of the network along with any other errors • Analyze information to determine why communication is not possible • Propose solutions to network errors • Implement solutions to network errors

Scenario

In this lab, you are given a completed configuration for a small routed network. The configuration contains design and configuration errors that conflict with stated requirements and prevent end-to-end communication. You will examine the given design and identify and correct any design errors. You will then cable the network, configure the hosts, and load configurations onto the router. Finally, you will troubleshoot the connectivity problems to determine where the errors are occurring and correct them using the appropriate commands. When all errors have been corrected, each host should be able to communicate with all other configured network elements and with the other host.

Task 1: Examine the Logical LAN Topology

The IP address block of 172.16.30.0 /23 is subnetted to meet the following requirements:

Subnet Number of Hosts Subnet A 174

of 210

Subnet B 60 Additional requirements and specifications:

The 0 subnet is used. The smallest possible number of subnets that satisfy the requirements for hosts should

be used, keeping the largest possible block in reserve for future use. Assign the first usable subnet to Subnet A. Host computers use the first IP address in the subnet. The network router uses the last

network host address.

Based on these requirements, the following topology has been provided to you:

Subnet A

Specification Value

IP mask (decimal) 255.255.255.0

IP address 172.16.30.0

First IP host address 172.16.30.1

Last IP host address 172.16.30.254

Subnet BSpecification Value IP mask (decimal) 255.255.255.128 IP address 172.16.31.0 First IP host address 172.16.31.1 Last IP host address 172.16.31.126

Examine each of the values in the tables above and verify that this topology meets all requirements and specifications. Are any of the given values incorrect? __________________________________

If yes, correct the values in the table above and write the corrected values below: ______________________________________________________________________________________________________________________________________________________

Create a configuration table similar to the one below using your corrected values:

Device IP address Mask Gateway Host1 172.16.30.1 255.255.255.0 172.16.30.254 Router1–Fa0/0 172.16.30.254 255.255.255.0 N/A Host2 172.16.31.1 255.255.255.128 172.16.31.126 Router1–Fa0/1 172.16.31.126 255.255.255.128 N/A

of 210

Task 2: Cable the Routers

Cable a network that is similar to the one in the topology diagram.

Task 3: Configure the Host Computers

Step 1: Configure host computers.

Configure the static IP address, subnet mask, and gateway for each host computer based on the configuration table created in Task 1. After configuring each host computer, display and verify the host network settings with the ipconfig /all command.

Task 4: Load the Router with the Supplied Scripts

enable ! config term ! hostname Router1 ! enable secret class ! no ip domain-lookup ! interface FastEthernet0/0 description connection to host1 ip address 172.16.30.1 255.255.255.0 duplex auto speed auto ! interface FastEthernet0/1 description connection to switch1 ip address 192.16.31.1 255.255.255.192 duplex auto speed auto ! ! line con 0 password cisco

of 210

Threshold SOB 46

login line vty 0 login line vty 1 4 password cisco login ! End

Task 5: Identify Connectivity Problems

Step 1: Use the ping command to test network connectivity.

Use the following table to test the connectivity of each network device.

From To IP Address Ping Results Host1 NIC IP address 172.16.30.1 Host1 Router1, Fa0/0 172.16.30.254 Host1 Router1, Fa0/1 172.16.31.126 Host1 Host2 172.16.31.1 Host2 NIC IP address 172.16.30.1 Host2 Router1, Fa0/1 172.16.31.126 Host2 Router1, Fa0/0 172.16.30.254 Host2 Host1 172.16.30.1

Task 6: Troubleshoot Network Connections

Step 1: Begin troubleshooting at the host connected to the BRANCH router.

From host PC1, is it possible to ping PC2? _________ From host PC1, is it possible to ping the router fa0/1 interface? _________ From host PC1, is it possible to ping the default gateway? _________ From host PC1, is it possible to ping itself? _________ Where is the most logical place to begin troubleshooting the PC1 connection problems? ______________________________________________________________________________________________________________________________________________________

Step 2: Examine the router to find possible configuration errors.

Begin by viewing the summary of status information for each interface on the router.

of 210

Typical SOB 47

Are there any problems with the status of the interfaces? ______________________________________________________________________________________________________________________________________________________

If there are problems with the status of the interfaces, record any commands that are necessary to correct the configuration errors. ______________________________________________________________________________________________________________________________________________________

Step 3: Use the necessary commands to correct the router configuration.

Step 4: View a summary of the status information.

If any changes were made to the configuration in the previous step, view the summary of the status information for the router interfaces.

Does the information in the interface status summary indicate any configuration errors on Router1? _________

If the answer is yes, troubleshoot the interface status of the interfaces.

Has connectivity been restored? ________

Step 5: Verify the logical configuration.

Examine the full status of Fa 0/0 and 0/1. Is the IP addresses and subnet mask information in the interface status consistent with the configuration table? ________

If there are differences between the configuration table and the router interface configuration, record any commands that are necessary to correct the router configuration. ______________________________________________________________________________________________________________________________________________________

Has connectivity been restored? ________

Why is it useful for a host to ping its own address? ______________________________________________________________________________________________________________________________________________________

of 210

Threshold SOB 48

of 210

Lab 15: Configuring and Testing the Lab Network (Packet Tracer)

Topology Diagram

Addressing Table


R1-ISPFa0/0 N/A

S0/0/0 N/A

R2-CentralFa0/0 N/A

S0/0/0 N/APC 1A NICPC 1B NICEagle Server NIC

Learning Objectives

Build, test, and configure the entire lab network Integrate skills from throughout the course Analyse the events involved in requesting a web page (DNS, ARP, HTTP, TCP, IP,

Ethernet, HDLC)

of 210

Analyse the events involved in tracing the route to the web server (DNS, UDP, ARP, ICMP, IP, Ethernet, HDLC)

Background

For this lab use packet tracer.Throughout the course, you have been developing network planning, building, configuring, and testing skills. You have also developed conceptual understandings of networking protocols and device algorithms. Here is an opportunity to test yourself: see if you can complete the entire challenge (approximately 100 configurable components, though some are quite easy) in under 30 minutes.

Task 1: Plan.

Use the standard Exploration lab topology as you plan your IP addressing scheme:

Two 1841 routers with WIC-2T interface cards, installed in the right hand slot (one named R1-ISP, which has the serial DCE WAN connection to R2-Central, and the Fa0/0 LAN connection to Eagle_Server) and one named R2-Central (which has the serial DCE WAN connection to R1-ISP and the Fa0/0 LAN connection to S1-Central)

One 2960TT Switch (S1-Central) Two PCs named 1A and 1B A server named Eagle_Server.

Note that both the Display names AND host names for all devices must be configured exactly, and in general all strings (names, passwords, banners) should be typed exactly as specified in these instructions, for the grading to work properly.

You have been given an IP address block of 192.168.3.0 /24. You must provide for existing networks as well as future growth.

Subnet assignments are:

1st subnet, existing student LAN, up to 28 hosts (Fa0/0 on R2-Central, connected to Fa0/24 on S1-Central)

2nd subnet, future student LAN, up to 28 hosts (not yet implemented) 3rd subnet, existing ISP LAN, up to 14 hosts (Fa0/0 on R1-ISP) 4th subnet, future ISP LAN, up to 7 hosts (not yet implemented) 5th subnet, existing WAN, point-to-point link (S0/0/0 on R1-ISP and S0/0/0 on R2-

Central)

IP address assignments are:

For the server, configure the second highest usable IP address on the ISP LAN subnet.

of 210

For R1-ISP's Fa0/0 interface, configure the highest usable IP address on the ISP LAN subnet.

For R1-ISP's S0/0/0 interface, configure the highest usable address on the existing WAN subnet.

For R2-Central's S0/0/0 interface, use the lowest usable address on the existing WAN subnet.

For R2-Central's Fa0/0 interface, use the highest usable address on the existing student LAN subnet and connect it to the Fa0/24 interface on S1-Central.

For hosts 1A and 1B, use the first 2 IP addresses (two lowest usable addresses) on the existing student LAN subnet and connect them to the Fa0/1 and Fa0/2 interfaces on S1-Central.

For the switch management interface, use the second highest usable address on the student subnet.

Task 2: Build and Configure the Network.

Build the network, taking care to make connections as specified. Configure both routers, the switch, the server, and the two PCs.

Configure the routers using the CLI to practice your skills. The router configuration must include "housekeeping" (display name, hostname, passwords, banner), interfaces (Fast Ethernet and Serial), and routing (static route on R1-ISP, default route on R2-Central). The following login passwords should all be set to "cisco" (no quotes): enable password (not secret), console, and Telnet. The banners should say **This is lab router R1-ISP. Authorized access only.** and **This is lab router R2-Central. Authorized access only.**

What are the commands used for router “housekeeping”_______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Write the command used for static route on R1-ISP___________________________________________________________________________

Write the command used for the default route on R2-Central

of 210

Threshold SOB 49

___________________________________________________________________________

What are the commands needed to configure the login passwords?

Enable password:___________________________________________________________Console:__________________________________________________________________Telnet:___________________________________________________________________

The interfaces should be configured as specified in the IP addressing section above; use a clock rate of 64000 on the R1-ISP S0/0/0 interface. The static route on R1-ISP should point to the existing Student LAN subnet via R2-Central's serial interface IP address; the static route on R2-Central should be a default static route which points via R1-ISP's serial interface IP address.

Enter the command used for the clock rate on R1-ISP S0/0/0 interface___________________________________________________________________________

On the switch, configure the display name, hostname, banner (**This is lab switch S1-Central. Authorized access only.**), login passwords for access (enable, console, and Telnet passwords all set to "cisco"), and management interface (int vlan1).

For Hosts 1A and 1B, in addition to IP configuration, configure them to use DNS services. For the server, enable DNS services, use the domain name eagle-server.example.com, and enable HTTP services.

Task 3: Test and Analyse.

It is a good practice to test connectivity through ping and Telnet, and to examine routing tables. In simulation mode, request a web page while making the following protocols visible in the event list: DNS, HTTP, Telnet, TCP, UDP, ICMP, ARP. Examine the packets as they are processed by the devices to study protocol behaviour, especially how IP is involved in everything. Also note the algorithms used by hosts, switches, and routers.

Explain the entire process__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

of 210

Threshold SOB 50

_________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Issue a traceroute to the server from one of the PCs. Examine how trace is built up of ICMP echo requests. Again explain the entire process______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Task 4: Reflection - Putting it All Together.

Relate the processes observed in Task 3 to the TCP/IP Protocol. _________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

of 210

Threshold SOB 51

Lab 16: Subnetting (Packet Tracer)

Topology Diagram

Addressing Table


HQ

Fa0/1 N/A

S0/0/0 N/A

S0/0/1 N/A

BRANCH1

Fa0/0 N/A

Fa0/1 N/A

S0/0/0 N/A

BRANCH2

Fa0/0 N/A

Fa0/1 N/A

S0/0/1 N/A

PC1 NIC

PC2 NIC

PC3 NIC

PC4 NIC

PC5 NIC

of 210

Typical SOB 52

Learning Objectives

Upon completion of this lab, you will be able to: Determine the number of subnets needed. Determine the number of hosts needed. Design an appropriate addressing scheme. Assign addresses and subnet mask pairs to device interfaces and hosts. Examine the use of the available network address space. Determine how static routing could be applied to the network.

Scenario

In this lab, you have been given the network address 192.168.9.0/24 to subnet and provide the IP addressing for the network shown in the Topology Diagram. The network has the following addressing requirements:

The BRANCH1 LAN 1 will require 10 host IP addresses. The BRANCH1 LAN 2 will require 10 host IP addresses. The BRANCH2 LAN 1 will require 10 host IP addresses. The BRANCH2 LAN 2 will require 10 host IP addresses. The HQ LAN will require 20 host IP addresses. The link from HQ to BRANCH1 will require an IP address for each end of the link. The link from HQ to BRANCH2 will require an IP address for each end of the link.

(Note: Remember that the interfaces of network devices are also host IP addresses and are included in the above addressing requirements.)

Task 1: Examine the Network Requirements.

Examine the network requirements and answer the questions below. Keep in mind that IP addresses will be needed for each of the LAN interfaces.

How many subnets are needed? __________

What is the maximum number of IP addresses that are needed for a single subnet? __________

How many IP addresses are needed for each of the branch LANs? __________

What is the total number of IP addresses that are needed? __________

of 210

Typical SOB 53

Task 2: Design an IP Addressing Scheme.

Step 1: Subnet the 192.168.9.0 network into the appropriate number of subnets.

What will the subnet mask be for the subnetworks? __________________________

How many usable host IP addresses are there per subnet? __________

Fill in the following chart with the subnet information.

Subnet Number

Subnet AddressFirst UsableHost Address

Last UsableHost Address

Broadcast Address

01234567

Step 2: Assign the subnets to the network shown in the Topology Diagram.

When assigning the subnets, keep in mind that routing will need to occur to allow information to be sent throughout the network. The subnets will be assigned to the networks to allow for route summarization on each of the routers.

1. Assign first subnet (lowest subnet) to the LAN connected to the Fa0/1 interface of BRANCH2. What is the subnet address? ____________________

2. Assign second subnet to LAN connected to the Fa0/0 interface of BRANCH2. What is the subnet address? ____________________

3. Assign third subnet to LAN connected to the Fa0/0 interface of BRANCH1. What is the subnet address? ____________________

4. Assign fourth subnet to LAN connected to the Fa0/1 interface of BRANCH1. What is the subnet address? ____________________

5. Assign fifth subnet to the WAN link from HQ to BRANCH1. What is the subnet address? ____________________

6. Assign sixth subnet to the WAN link from HQ to BRANCH2. ____________________

of 210

7. Assign seventh subnet to LAN connected to the Fa0/1 interface of HQ. What is the subnet address? ____________________

Note: The highest subnet will not be required in this topology.

Task 3: Assign IP Addresses to the Network Devices

Assign the appropriate addresses to the device interfaces. Document the addresses to be used in the Addressing Table provided under the Topology Diagram.

Step 1: Assign addresses to the HQ router.

1. Assign the first valid host address in the HQ LAN subnet to the LAN interface.2. Assign the first valid host address in link from HQ to BRANCH1 subnet to the S0/0/0

interface.3. Assign the first valid host address in link from HQ to BRANCH2 subnet to the S0/0/1

interface.

Step 2: Assign addresses to the BRANCH1 router.

1. Assign the first valid host address in the BRANCH1 LAN 1 subnet to the Fa0/0 LAN interface.


3. Assign the last valid host address in link from HQ to BRANCH1 subnet to the WAN interface.

Step 3: Assign addresses to the BRANCH2 router.



3. Assign the last valid host address in link from HQ to BRANCH2 subnet to the WAN interface.

Step 4: Assign addresses to the host PCs.

1. Assign the last valid host address in the HQ LAN subnet to PC1.2. Assign the last valid host address in the BRANCH1 LAN 1 subnet to PC2.3. Assign the last valid host address in the BRANCH1 LAN 2 subnet to PC3.4. Assign the last valid host address in the BRANCH2 LAN 1 subnet to PC4.

of 210

Typical SOB 54

5. Assign the last valid host address in the BRANCH2 LAN 2 subnet to PC5.

Task 4: Test the Network Design.

Apply your addressing scheme. Check to see that all devices on directly connected networks can ping each other.

Task 5: Reflection

How many IP address in the 192.168.9.0 network are unused or unusable in this design? __________

What would the command be to add a default static route on the WAN interface of the BRANCH1 router? __________________________________________________________________________

Can both of the BRANCH1 LANs be summarized into one route on the HQ router? _________What would be the command used to add this summary route to the routing table?__________________________________________________________________________

Can both of the BRANCH2 LANs be summarized into one route on the HQ router? __________

What would be the command used to add this summary route to the routing table?

__________________________________________________________________________

Can the HQ LAN and both of the BRANCH1 LANs be summarized into one route on the BRANCH2 router? This summarized route should also include the link between the HQ and BRANCH1 routers.__________

What would be the command used to add this summary route to the routing table?

__________________________________________________________________________

of 210

Typical SOB 55

of 210

Excellent SOB 56

Lab 17: VLSM Variable-Length Subnet Mask

IP Address Classes

Class A 1 – 127 (Network 127 is reserved for loopback and internal testing) Leading bit pattern 0 00000000.00000000.00000000.00000000

Network . Host . Host . Host

Class B 128 – 191 Leading bit pattern 10 10000000.00000000.00000000.00000000Network . Network . Host . Host

Class C 192 – 223 Leading bit pattern 110 11000000.00000000.00000000.00000000Network . Network . Network . Host

Class D 224 – 239 (Reserved for multicast)

Class E 240 – 255 (Reserved for experimental, used for research)

Private Address Space

Class A 10.0.0.0 to 10.255.255.255

Class B 172.16.0.0 to 172.31.255.255

Class C 192.168.0.0 to 192.168.255.255

Default Subnet Masks

Class A 255.0.0.0

Class B 255.255.0.0

Class C 255.255.255.0

of 210

What is VLSM

Variable Length Subnet Masks allow you a much tighter control over your addressing scheme. If you use a class C address with a default subnet mask you end up with one subnet containing 256 addresses. By using VLSM you can adjust the number of subnets and number of addresses depending on the specific needs of your network. The same rules apply to a class A orB addresses.

VLSM is supported by Cisco, OSPF, Dual IS-IS, BGP-4, and EIGRP. You need to configure your router for Variable Length Subnet Masking by setting up one of these protocols. Then configure the subnet masks of the various interfaces in the IP address interface sub-command. To use supernet you must also configure IP classless routes.

The Box Method

The box method is the simplest way to visualize the breakdown of a range of addresses into smaller different sized subnets.

Start with a square. The whole square is a single 0

subnet comprised of 256 addresses

/24

255.255.255.0

256 Hosts

1 Subnet 255

of 210

Split the box in half and you get two 0 128Subnets with 128 addresses

/25 255.255.255.128 128 Hosts 2 Subnets 127 255

Divide the box into quarters and you get 0 128four subnets with 64 addresses

63 191 64 192

/26 255.255.255.192 62 Hosts 4 Subnets 127 255

Split each individual square and you get 0 32 128 160eight subnets with 32 addresses

31 63 159 191

64 96 192 224

of 210

/27 255.255.255.224 32 Hosts 8 Subnets 95 127 223 255

Split the boxes in half again and you get 0 32 128 160sixteen subnets with sixteen addresses

15 47 143 175 16 48 144 176

31 63 159 191 64 96 192 224

/28 79 111 207 239 255.255.255.240 80 112 208 240 16 Hosts

16 Subnets 95 127 223 255

The next split gives you thirty two subnets 0 8 32 40 128 136 160 168

with eight addresses 7 15 39 47 135 143 167 175 16 24 48 56 144 152 176 184

23 31 55 63 151 159 183 191

64 72 96 104 192 200 224 232

71 79 103 111 199 207 231 239 /29 80 88 112 120 208 216 240 248 255.255.255.248 8 Hosts 32 Subnets 87 95 119 127 215 223 247 255

of 210

The last split gives sixty four subnets with 0 8 32 40 128 136 160 168

four addresses each, you can use these 3 11 35 43 131 139 163 171

squares in any combination to fit your 4 12 36 44 132 140 164 172

addressing needs 7 15 39 47 135 143 167 175 16 24 48 56 144 152 176 184

19 27 51 59 147 155 179 187 20 28 52 60 148 156 180 188

23 31 55 63 151 159 183 191 64 72 96 104 192 200 224 232

67 75 99 107 195 203 227 235

/30 68 76 100 108 196 204 228 236

255.255.255.252 71 79 103 111 199 207 231 239

4 Hosts 80 88 112 120 208 216 240 248

64 Subnets 83 91 115 123 211 219 243 251 84 92 116 124 212 220 244 252

87 95 119 127 215 223 247 255

VLSM Addressing Part 1

Problem 1 (Example)

Using the network diagram and information given create an addressing scheme which utilizes variable-length subnet masks. Show the subnet address and subnet mask in the boxes below, colour or shade the sub-subnets used in the box. This business will be using the class C address 220.10.10.0.Remember to start with your largest groups first.

of 210

Colour in the squares used with different shades to highlight each subnet.

0

63

128

255

64

95

96

127

Problem 2 (Example)

Using the network diagram and information given create an addressing scheme which utilizes variable-length subnet masks. Show the subnet address and subnet mask in the boxes below, colour or shade the sub-subnets used in the box. This company will be using the class C address 192.168.16.0.Remember to start with your largest groups first.

Colour in the squares used with different shades to highlight each sub-subnet.

of 210

0

127

128

191192

223

224

227

232

239

228

321240

255

Problem 3



of 210

0

63

128

255

64

95

96

9

104

111

100

10112

127

Problem 4



of 210

0 8 32 40 128 136 160 168

3 11 35 43 131 139 163 171 4 12 36 44 132 140 164 172

7 15 39 47 135 143 167 175

16 24 48 56 144 152 176 184

19 27 51 59 147 155 179 187 20 28 52 60 148 156 180 188

23 31 55 63 151 159 183 191 64 72 96 104 192 200 224 232

67 75 99 107 195 203 227 235 68 76 100 108 196 204 228 236

71 79 103 111 199 207 231 239

80 88 112 120 208 216 240 248

83 91 115 123 211 219 243 251

84 92 116 124 212 220 244 252

87 95 119 127 215 223 247 255

Problem 5

Using the network diagram and information given create an addressing scheme which utilizes variable-length subnet masks. Show the subnet address and subnet mask in the boxes below, colour or shade the sub-subnets used in the box. This company will be using the class C address192.168.10.0. Remember to start with your largest groups first.

of 210


0 8 32 40 128 136 160 168

3 11 35 43 131 139 163 171 4 12 36 44 132 140 164 172

7 15 39 47 135 143 167 175

16 24 48 56 144 152 176 184

19 27 51 59 147 155 179 187 20 28 52 60 148 156 180 188

23 31 55 63 151 159 183 191 64 72 96 104 192 200 224 232

67 75 99 107 195 203 227 235 68 76 100 108 196 204 228 236

71 79 103 111 199 207 231 239

80 88 112 120 208 216 240 248

83 91 115 123 211 219 243 251

84 92 116 124 212 220 244 252

87 95 119 127 215 223 247 255

Problem 6

Using the network diagram and information given create an addressing scheme which utilizes variable-length subnet masks. Show the subnet address and subnet mask in the boxes below, colour or shade the sub-subnets used in the box. This company will be using the class C address 222.10.150.0. Remember to start with your largest groups first.

of 210

Draw the necessary lines and colour in the used squares with different shades to highlight each sub-subnet.

0 32 128 160

31 63 159 191 64 96 192 224

95 127 223 255

Problem 7


of 210


0 128

63 191 64 192

127 255

Problem 8


of 210


0

255

of 210

VLSM Addressing Part 2

Problem 9 (Example)

You are developing a school network with the class C address 192.168.2.0/24. There will be three computer labs with 30 computers each that need to be on different sub-subnets. Forty eight classrooms with one computer each that will comprise a single sub-subnet. The administrative office and guidance office contain a total of seven computers which will need to be grouped together. Plan for four more mini labs with six computers to each sub-subnetwork. Divide the network using variable length subnet masks. Complete the information required below. Remember to work from largest to smallest.

Subnet

Subnet Address Subnet Mask (/X)

First Usable Host Last Usable Host Broadcast Address

1 192.168.2.0 /26 192.168.2.1 192.168.2.62 192.168.2.632 192.168.2.64 /27 192.168.2.65 192.168.2.94 192.168.2.953 192.168.2.96 /27 192.168.2.97 192.168.2.126 192.168.2.1274 192.168.2.128 /27 192.168.2.129 192.168.2.158 192.168.2.1595 192.168.2.160 /28 192.168.2.161 192.168.2.174 192.168.2.1756 192.168.2.176 /29 192.168.2.177 192.168.2.182 192.168.2.1837 192.168.2.184 /29 192.168.2.185 192.168.2.190 192.168.2.1918 192.168.2.192 /29 192.168.2.193 192.168.2.198 192.168.2.1999 192.168.2.200 /29 192.168.2.201 192.168.2.206 192.168.2.20710

of 210

Problem 10 (Example)

You are setting up a small business network with the class C address 220.55.80.0/24. The marketing division will need 12 computers. Research and development needs 27 computers. The reception area will need two computers. Management requires 19 computers. Divide the network using variable length subnet masks. Complete the information required below. Remember to work from largest to smallest.

Subnet



1 220.55.80.0 /27 220.55.80.1 220.55.80.30 220.55.80.312 220.55.80.32 /27 220.55.80.33 220.55.80.62 220.55.80.633 220.55.80.64 /28 220.55.80.65 220.55.80.78 220.55.80.794 220.55.80.80 /30 220.55.80.81 220.55.80.82 220.55.80.835

Problem 11

You are setting up a medium sized network with the class C address 222.37.34.0/24. Marketing needs 29 computers. Research and development needs 110 computers. Bookkeeping will use 12 computers. The reception area will need three computers. Management requires 60 computers. Divide the network using variable length subnet masks. Complete the information required below. Remember to work from largest to smallest.

Subnet



1234

of 210

5678

Problem 12

A shipping company needs to set up its network across several locations. The Denver office needs six computers. The Waco office needs 22 computers. The Fargo office will need five computers. The WAN links between all three locations need to be included in the solution. Using the IP address 192.168.10.0/24 divide the network using VLSM. Complete the information required below. Remember to work from largest to smallest.

Subnet



12345678

Problem 13

A new school is being built in the local school district. It will have three computer labs with 28 computers each. There will be 58 classrooms with 2 computers each that need to be on one sub-subnet. The office staff and administrators will need 7 computers. The guidance and

of 210

attendance office will have 5 computers. Setup the remaining addressing into one sub-subnet for future expansion. The school has been given the address 223.145.75.0/24. Complete the information required below. Remember to work from largest to smallest.

Subnet



12345678

Problem 14

A local college is setting up a campus wide network. The technology wing will be on its own network address of 192.168.250.0/24. The office wing will include 15 computers. There are 2 labs of 20 computers each, 2 labs of 30 computers each and one lab of 35 computers. Complete the information required below. Remember to work from largest to smallest.

Subnet



12

of 210

Threshold SOB 57

345678

Problem 15

You are setting up a network for a company in four locations. Location A has 8 computers. Location B has 122 computers. Location C has 4 computers. Location D has 55 computers. There is a WAN connection between all four locations. Complete the information required below using the class C address 192.168.10.0.Remember to work from largest to smallest.

Subnet



12345678

of 210

Problem 16

A college dormitory is being remoulded. A new network is being installed. There are 50 dorm rooms with two drops each that will be on one sub-subnet. The offices will have 5 drops. The reception desk will have three drops. A small study hall will include 30 drops. Using the IP address 192.168.12.0/24 complete the information required below using VLSM. Work from largest to smallest.

Subnet



12345678

of 210

Typical SOB 58

Class A Addressing Guide# of Bits

BorrowedSubnetMask

Total # ofSubnets

Usable # ofSubnets

Total # ofHosts

Usable # ofHosts

2 255.192.0.0 4 2 4,194,304 4,194,3023 255.224.0.0 8 6 2,097,152 2,097,1504 255.240.0.0 16 14 1,048,576 1,048,5745 255.248.0.0 32 30 524,288 524,2866 255.252.0.0 64 62 262,144 262,1427 255.254.0.0 128 126 131,072 131,0708 255.255.0.0 256 254 65,536 65,5349 255.255.128.0 512 510 32,768 32,76610 255.255.192.0 1,024 1,022 16,384 16,38211 255.255.224.0 2,048 2,046 8,192 8,19012 255.255.240.0 4,096 4,094 4,096 4,09413 255.255.248.0 8,192 8,190 2,048 2,04614 255.255.252.0 16,384 16,382 1,024 1,02215 255.255.254.0 32,768 32,766 512 51016 255.255.255.0 65,536 65,534 256 25417 255.255.255.128 131,072 131,070 128 12618 255.255.255.192 262,144 262,142 64 6219 255.255.255.224 524,288 524,286 32 3020 255.255.255.240 1,048,576 1,048,574 16 1421 255.255.255.248 2,097,152 2,097,150 8 622 255.255.255.252 4,194,304 4,194,302 4 2

Class B Addressing Guide# of Bits

BorrowedSubnetMask

Total # ofSubnets

Usable # ofSubnets

Total # ofHosts

Usable # ofHosts

2 255.255.192.0 4 2 16,384 16,3823 255.255.224.0 8 6 8,192 8,1904 255.255.240.0 16 14 4,096 4,0945 255.255.248.0 32 30 2,048 2,0466 255.255.252.0 64 62 1,024 1,0227 255.255.254.0 128 126 512 5108 255.255.255.0 256 254 256 2549 255.255.255.128 512 510 128 12610 255.255.255.192 1,024 1,022 64 6211 255.255.255.224 2,048 2,046 32 3012 255.255.255.240 4,096 4,094 16 1413 255.255.255.248 8,192 8,190 8 614 255.255.255.252 16,384 16,382 4 2

Class C Addressing Guide# of Bits

BorrowedSubnetMask

Total # ofSubnets

Usable # ofSubnets

Total # ofHosts

Usable # ofHosts

2 255.255.255.192 4 2 64 623 255.255.255.224 8 6 32 304 255.255.255.240 16 14 16 145 255.255.255.248 32 30 8 66 255.255.255.252 64 62 4 2

VLSM Chart 24-30 Bits144

/24255.255.255.0

256 Hosts

/25255.255.255.128

128 Hosts

/26

255.255.255.19

/27255.255.255.224

32 Hosts

/28255.255.255.240

16 Hosts

/29255.255.255.248

8 Hosts

/30255.255.255.252

4 Hosts

0-127

0-127

0-63

0-31

0-150-7

0-34-7

8-158-11

12-15

16-3116-23

16-1920-23

24-3124-2728-31

32-63

32-4732-39

32-3536-39

40-4740-4344-47

48-6348-55 48-51

52-55

56-6356-5960-63

64-127

64-95

64-7964-71 64-67

68-71

72-79 72-7576-79

80-9580-87

80-8384-87

88-95 88-9192-95

96-127

96-11196-103

96-99100-103

104-111104-107108-111

112-127112-119 112-115

116-119

120-127 120-123124-127

128-255

128-191

128-159

128-143128-135

128-131132-135

136-143 136-139140-143

144-159144-151

144-147148-151

152-159152-155156-159

160-191

160-17516-167

160-163164-167

168-175168-171172-175

176-191176-183

176-179180-183

184-191184-187188-191

192-255

192-223

192-207192-199

192-195196-199

200-207 200-203204-207

208-223208-215

208-211212-215

216-223 216-219220-223

224-255

224-239224-231

224-227228-231

232-239232-235236-239

240-255240-247

240-243244-247248-251

145

248-255252-255

Lab 18: Basic VLSM Calculation and Addressing Design

Topology Diagram

Addressing Table


HQ Fa0/0 N/AFa0/1 N/AS0/0/0 N/AS0/0/1 N/A

Branch 1

Fa0/0 N/AFa0/1 N/AS0/0/0 N/AS0/0/1 N/A

Branch 2

Fa0/0 N/AFa0/1 N/AS0/0/0 N/AS0/0/1 N/A

Learning Objectives

Upon completion of this activity, you will be able to:

Determine the number of subnets needed. Determine the number of hosts needed for each subnet. Design an appropriate addressing scheme using VLSM.

146

Assign addresses and subnet mask pairs to device interfaces. Examine the use of the available network address space.

Scenario

In this activity, you have been given the network address 192.168.1.0/24 to subnet and provide the IP addressing for the network shown in the Topology Diagram. VLSM will be used so that the addressing requirements can be met using the 192.168.1.0/24 network. The network has the following addressing requirements:

The HQ LAN1 will require 50 host IP addresses. The HQ LAN2 will require 50 host IP addresses. The Branch1 LAN1 will require 20 host IP addresses. The Branch1 LAN2 will require 20 host IP addresses The Branch2 LAN1 will require 12 host IP addresses. The Branch2 LAN2 will require 12 host IP addresses. The link from HQ to Branch1 will require an IP address for each end of the link. The link from HQ to Branch2 will require an IP address for each end of the link. The link Branch1 to Branch2 will require an IP address for each end of the link.

(Note: Remember that the interfaces of network devices are also host IP addresses and are included in the above addressing requirements.)

Task 1: Examine the Network Requirements.

Examine the network requirements and answer the questions below. Keep in mind that IP addresses will be needed for each of the LAN interfaces.

1. How many subnets are needed? _______2. What is the maximum number of IP addresses that are needed for a single subnet?

_______3. How many IP addresses are needed for each of the BranchBranch1 LANs? _______4. How many IP addresses are needed for each of the BranchBranch2 LANs? _______5. How many IP addresses are needed for each of the WAN links between routers?

_______6. What is the total number of IP addresses that are needed? _______7. What is the total number of IP addresses that are available in the 192.168.1.0/24

network? _________8. Can the network addressing requirements be met using the 192.168.1.0/24 network?

_______

147

Typical SOB 59

Task 2: Design an IP Addressing Scheme

Step 1: Determine the subnet information for the largest network segment or segments.

In this case, the two HQ LANs are the largest subnets.

1. How many IP addresses are needed for each LAN? _______2. What is the smallest size subnet that can be used to meet this requirement? _______3. What is the maximum number of IP addresses that can be assigned in this size subnet?

________

Step 2: Assign subnets to HQ LANs.

Start at the beginning of the 192.168.1.0/24 network.

1. Assign the first available subnet to HQ LAN1.2. Fill in the chart below with the appropriate information.

HQ LAN1 Subnet

Network Address

Decimal Subnet Mask

CIDR Subnet Mask

First Usable IP Address

Last Usable IP Address

Broadcast Address

3. Assign the next available subnet to HQ LAN2.4. Fill in the chart below with the appropriate information.

HQ LAN2 Subnet

Network Address

Decimal Subnet Mask

CIDR Subnet Mask



Broadcast Address

Step 3: Determine the subnet information for the next largest network segment or segments.

In this case, the two Branch1 LANs are the next largest subnets.

148

Threshold SOB 60


_______

Step 4: Assign subnet to BRANCH1 LANs.

Start with the IP address following the HQ LAN subnets.

1. Assign the next subnet to Branch1 LAN1.2. Fill in the chart below with the appropriate information.

Branch1 LAN1 Subnet

Network Address

Decimal Subnet Mask

CIDR Subnet Mask



Broadcast Address

3. Assign the next available subnet to Branch1 LAN2.4. Fill in the chart below with the appropriate information.

Branch1 LAN2 Subnet

Network Address

Decimal Subnet Mask

CIDR Subnet Mask



Broadcast Address

Step 5: Determine the subnet information for the next largest network segment or segments.

In this case, the two Branch 2 LANs are the next largest subnets.


________

Step 6: Assign subnets to BRANCH2 LANs.

Start with the IP address following the Branch1 LAN subnets.149

Threshold SOB 61

1. Assign the next subnet to the Branch2 LAN1. Fill in the chart below with the appropriate information.

Branch2 LAN1 Subnet

Network Address

Decimal Subnet Mask

CIDR Subnet Mask



Broadcast Address

2. Assign the next available subnet to Branch2 LAN2.3. Fill in the chart below with the appropriate information.

Branch2 LAN2 Subnet

Network Address

Decimal Subnet Mask

CIDR Subnet Mask



Broadcast Address

Step 7: Determine the subnet information for the links between the routers.

1. How many IP addresses are needed for each link? _______2. What is the smallest size subnet that can be used to meet this requirement? _______3. What is the maximum number of IP addresses that can be assigned in this size subnet?

_________

Step 8: Assign subnets to links.

Start with the IP address following the Branch2 LAN subnets.

1. Assign the next available subnet to the link between the HQ and Branch1 routers.2. Fill in the chart below with the appropriate information.

Link between HQ and Branch1 Subnet

Network Address

Decimal Subnet Mask

CIDR Subnet Mask



Broadcast Address

150

Threshold SOB 62

3. Assign the next available subnet to the link between the HQ and Branch2 routers.4. Fill in the chart below with the appropriate information.

Link between HQ and Branch2 Subnet

Network Address

Decimal Subnet Mask

CIDR Subnet Mask



Broadcast Address

5. Assign the next available subnet to the link between the Branch1 and Branch2 routers.6. Fill in the chart below with the appropriate information.

Link between Branch1 and Branch2 Subnet

Network Address

Decimal Subnet Mask

CIDR Subnet Mask



Broadcast Address

Task 3: Assign IP Addresses to the Network Devices

Assign the appropriate addresses to the device interfaces. Document the addresses to be used in the Addressing Table provided under the Topology Diagram.

Step 1: Assign addresses to the HQ router.

1. Assign the first valid host address in the HQ LAN 1 subnet to the Fa0/0 LAN interface.

2. Assign the first valid host address in the HQ LAN 2 subnet to the Fao/1 LAN interface.

3. Assign the first valid host address in the link between HQ and Branch1 subnet to the S0/0/0 interface.

4. Assign the first valid host address in the link between HQ and Branch2 subnet to the S0/0/1 interface.

151

Threshold SOB 63

Step 2: Assign addresses to the Branch1 router.

1. Assign the first valid host address in the Branch1 LAN1 subnet to the Fa0/0 LAN interface.


3. Assign the last valid host address on the link between Branch1 and HQ subnet to the S0/0/0 interface

4. Assign the first valid host address on the link between Branch1 and Branch2 subnet to the S0/0/1 interface.

Step 3: Assign addresses to the Branch2 router.


2. Assign the first valid host address in the Branch 2 LAN 2 subnet to the Fa0/1 LAN interface.

3. Assign the last valid host address on the link between HQ and Branch2 subnet to the S0/0/1 interface

4. Assign the last valid host address on the link between Branch1 and Branch2 subnet to the S0/0/0 interface.

152

Typical SOB 64

Lab 19: Basic Static Route Configuration (Hardware Equipment)

Topology Diagram

Addressing Table


R1Fa0/0 172.16.3.1 255.255.255.0 N/AS0/0/0 172.16.2.1 255.255.255.0 N/A

R2Fa0/0 172.16.1.1 255.255.255.0 N/AS0/0/0 172.16.2.2 255.255.255.0 N/AS0/0/1 192.168.1.2 255.255.255.0 N/A

R3FA0/0 192.168.2.1 255.255.255.0 N/AS0/0/1 192.168.1.1 255.255.255.0 N/A

PC1 NIC 172.16.3.10 255.255.255.0 172.16.3.1PC2 NIC 172.16.1.10 255.255.255.0 172.16.1.1PC3 NIC 192.168.2.10 255.255.255.0 192.168.2.1

Learning Objectives

Upon completion of this lab, you will be able to: Cable a network according to the Topology Diagram. Erase the startup configuration and reload a router to the default state. Perform basic configuration tasks on a router. Interpret debug ip routing output.

153

Configure and activate Serial and Ethernet interfaces. Test connectivity. Gather information to discover causes for lack of connectivity between devices. Configure a static route using an intermediate address. Configure a static route using an exit interface. Compare a static route with intermediate address to a static route with exit interface. Configure a default static route. Configure a summary static route. Document the network implementation.

Scenario

For this lab exercise you will have to work in threes. You will be using real hardware equipment. Show your work by answering questions where allocated.

In this lab activity, you will create a network that is similar to the one shown in the Topology Diagram. Begin by cabling the network as shown in the Topology Diagram. You will then perform the initial router configurations required for connectivity. Use the IP addresses that are provided in the Addressing Table to apply an addressing scheme to the network devices. After completing the basic configuration, test connectivity between the devices on the network. First test the connections between directly connected devices, and then test connectivity between devices that are not directly connected. Static routes must be configured on the routers for end-to-end communication to take place between the network hosts. You will configure the static routes that are needed to allow communication between the hosts. View the routing table after each static route is added to observe how the routing table has changed.

Task 1: Cable, Erase, and Reload the Routers.

Step 1: Cable a network that is similar to the one in the Topology Diagram.

Step 2: Clear the configuration on each router.

Clear the configuration on each of the routers using the erase startup-config command and then reload the routers. Answer no if asked to save changes.

154

Typical SOB 65

Task 2: Perform Basic Router Configuration.

Note: If you have difficulty with any of the commands in this task, see Lab 10: Cabling a Network and Basic Router Configuration.

Step 1: Use global configuration commands.

On the routers, enter global configuration mode and configure the basic global configuration commands including:

hostname no ip domain-lookup enable secret (use “cisco” for password)

Step 2: Configure the console and virtual terminal line passwords on each of the routers.

Password (class) login

Step 3: Add the logging command to the console and virtual terminal lines.

This command is very helpful in both lab and production environments and uses the following syntax:

Router(config-line)#logging synchronous

To synchronize unsolicited messages and debug output with solicited Cisco IOS software output and prompts for a specific console port line, auxiliary port line, or virtual terminal line, we can use the logging synchronous line configuration command. In other words, the logging synchronous command prevents IOS messages delivered to the console or Telnet lines from interrupting your keyboard input. For example, you may have already experienced something similar to the following example:

Note: Do not configure R1 interfaces yet.

R1(config)#interface fastethernet 0/0R1(config-if)#ip address 172.16.3.1 255.255.255.0R1(config-if)#no shutdownR1(config-if)#descri*Mar 1 01:16:08.212: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state

to up*Mar 1 01:16:09.214: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to upptionR1(config-if)#

155

The IOS sends unsolicited messages to the console when you activate an interface with the no shutdown command. However, the next command you enter (in this case, description) is interrupted by these messages. The logging synchronous command solves this problem by copying the command entered up to that point down to the next router prompt.

R1(config)#interface fastethernet 0/0R1(config-if)#ip address 172.16.3.1 255.255.255.0R1(config-if)#no shutdownR1(config-if)#description*Mar 1 01:28:04.242: %LINK-3-UPDOWN: Interface FastEthernet0/0, changed state

to up*Mar 1 01:28:05.243: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to upR1(config-if)#description <-- Keyboard input copied after message

R1 is shown here as an example. Add logging synchronous to the console and virtual terminal lines on all routers.

R1(config)#line console 0R1(config-line)#logging synchronousR1(config-line)#line vty 0 4R1(config-line)#logging synchronous

Step 4: Add the exec-timeout command to the console and virtual terminal lines.

To set the interval that the EXEC command interpreter waits until user input is detected, we can use the exec-timeout line configuration command. If no input is detected during the interval, the EXEC facility resumes the current connection. If no connections exist, the EXEC facility returns the terminal to the idle state and disconnects the incoming session. This command allows you to control the amount of time a console or virtual terminal line can be idle before the session is terminated. The syntax follows:

Router(config-line)#exec-timeout minutes [seconds]Syntax description:

minutes—Integer that specifies the number of minutes. seconds—(Optional) Additional time intervals in seconds.

In a lab environment, you can specify “no timeout” by entering the exec-timeout 0 0 command. This command is very helpful because the default timeout for lines is 10 minutes. However, for security purposes, you would not normally set lines to “no timeout” in a production environment.

156

R1 is shown here as an example.

Add exec-timeout 0 0 to console and virtual terminal lines on all routers.

R1(config)#line console 0R1(config-line)#exec-timeout 0 0R1(config-line)#line vty 0 4R1(config-line)#exec-timeout 0 0

Task 3: Interpreting Debug Output.

Note: If you already configured IP addressing on R1, please remove all interface commands now before proceeding. R1, R2 and R3 should be configured through the end of Task 2 without any interface configurations.

Step 1: On R1 from privileged EXEC mode, enter the debug ip routing command.

R1#debug ip routingIP routing debugging is on

The debug ip routing command shows when routes are added, modified, and deleted from the routing table. For example, every time you successfully configure and activate an interface, Cisco IOS adds a route to the routing table. We can verify this by observing output from the debug ip routing command.

Step 2: Enter interface configuration mode for R1’s LAN interface.

R1#configure terminalEnter configuration commands, one per line. End with CNTL/Z.R1(config)#interface fastethernet 0/0

Configure the IP address as specified in the Topology Diagram.

R1(config-if)#ip address 172.16.3.1 255.255.255.0is_up: 0 state: 6 sub state: 1 line: 1 has_route: False

As soon as you press the Enter key, Cisco IOS debug output informs you that there is now a route, but its state is False. In other words, the route has not yet been added to the routing

157

Typical SOB 66

table. Why did this occur and what steps should be taken to ensure that the route is entered into the routing table?______________________________________________________________________________________________________________________________________________________

Step 3: Enter the command necessary to install the route in the routing table.

After you enter the correct command, you should see debug output. Your output may be slightly different from the example below.

is_up: 1 state: 4 sub state: 1 line: 1 has_route: FalseRT: add 172.16.3.0/24 via 0.0.0.0, connected metric [0/0]RT: NET-RED 172.16.3.0/24RT: NET-RED queued, Queue size 1RT: interface FastEthernet0/0 added to routing table%LINK-3-UPDOWN: Interface FastEthernet0/0, changed state to upis_up: 1 state: 4 sub state: 1 line: 1 has_route: True%LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/0, changed state to upis_up: 1 state: 4 sub state: 1 line: 1 has_route: Trueis_up: 1 state: 4 sub state: 1 line: 1 has_route: True

The new network you configured on the LAN interface is now added to the routing table, as shown in the highlighted output.

If you do not see the route added to the routing table, the interface did not come up. Use the following systematic process to troubleshoot your connection:

1. Check your physical connections to the LAN interface. Is the correct interface attached? ________ Your router may have more than one LAN interface. Did you connect the correct LAN interface? ________An interface will not come up unless it detects a carrier detect signal at the Physical layer from another device. Is the interface connected to another device such as a hub, switch, or PC? ________

2. Check link lights. Are all link lights blinking? ________3. Check the cabling. Are the correct cables connected to the devices? ________4. Has the interface been activated or enabled? ________

If you can answer yes to all the proceeding questions, the interface should come up.

158

Step 4: Enter the command to verify that the new route is now in the routing table.

Your output should look similar to the following output. There should now be one route in the table for R1. What command did you use?

R1#______________________________________Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area * - candidate default, U - per-user static route, o - ODR P - periodic downloaded static route

Gateway of last resort is not set

172.16.0.0/24 is subnetted, 1 subnets

C 172.16.3.0 is directly connected, FastEthernet0/0

Step 5: Enter interface configuration mode for R1’s WAN interface connected to R2.

R1#configure terminalEnter configuration commands, one per line. End with CNTL/Z.R1(config)#interface Serial 0/0/0


R1(config-if)#ip address 172.16.2.1 255.255.255.0is_up: 0 state: 0 sub state: 1 line: 0 has_route: False

As soon as you press the Enter key, Cisco IOS debug output informs you that there is now a route, but its state is False. Because R1 is the DCE side of our lab environment, we must specify how fast the bits will be clocked between R1 and R2.

159

Excellent SOB 67

Step 6: Enter the clock rate command on R1.

You can specify any valid clocking speed. Use the ? to find the valid rates. Here, we used 64000 bps.

R1(config-if)#clock rate 64000is_up: 0 state: 0 sub state: 1 line: 0 has_route: False

Some IOS versions display the output shown above every 30 seconds. Why is the state of the route still False? What step must you now take to make sure that the interface is fully configured?___________________________________________________________________________

Step 7: Enter the command necessary to ensure that the interface is fully configured.

R1(config-if)#_____________________________

After you enter the correct command, you should see debug output similar to the following example:

is_up: 0 state: 0 sub state: 1 line: 0 has_route: False%LINK-3-UPDOWN: Interface Serial0/0/0, changed state to down

Unlike configuring the LAN interface, fully configuring the WAN interface does not always guarantee that the route will be entered in the routing table, even if your cable connections are correct. The other side of the WAN link must also be configured.

Step 8:

If possible, establish a separate terminal session by consoling into R2 from another workstation. Doing this allows you to observe the debug output on R1 when you make changes on R2. You can also turn on debug ip routing on R2.

R2#debug ip routingIP routing debugging is on

Enter interface configuration mode for R2’s WAN interface connected to R1.

160

Typical SOB 68

R2#configure terminal

Enter configuration commands, one per line. End with CNTL/Z.

R2(config)#interface serial 0/0/0


R2(config-if)#ip address 172.16.2.2 255.255.255.0is_up: 0 state: 6 sub state: 1 line: 0

Step 9: Enter the command necessary to ensure that the interface is fully configured.

R2(config-if)#_____________________________

After you enter the correct command, you should see debug output similar to the following example:

is_up: 0 state: 4 sub state: 1 line: 0%LINK-3-UPDOWN: Interface Serial0/0/0, changed state to upis_up: 1 state: 4 sub state: 1 line: 0RT: add 172.16.2.0/24 via 0.0.0.0, connected metric [0/0]RT: interface Serial0/0/0 added to routing tableis_up: 1 state: 4 sub state: 1 line: 0%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0, changed state to

upis_up: 1 state: 4 sub state: 1 line: 0

The new network that you configured on the WAN interface is now added to the routing table, as shown in the highlighted output.

If you do not see the route added to the routing table, the interface did not come up. Use the following systematic process to troubleshoot your connection:

1. Check your physical connections between the two WAN interfaces for R1 and R2. Is the correct interface attached? ________ Your router has more than one WAN interface. Did you connect the correct WAN interface? ________An interface will not come up unless it detects a link beat at the Physical layer from another device. Is the interface connected to the other router’s interface? ________

2. Check link lights. Are all link lights blinking? ________

161

3. Check the cabling. R1 must have the DCE side of the cable attached and R2 must have the DTE side of the cable attached. Are the correct cables connected to the routers? ________

4. Has the interface been activated or enabled? ________

If you can answer yes to all the proceeding questions, the interface should come up.

Step 10: Enter the command to verify that the new route is now in the routing table for R1 and R2.

Your output should look similar to the following output. There should now be two routes in the routing table for R1 and one route in the table for R2. What command did you use?

R1#_________________________________Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP

D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2 i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2

ia - IS-IS inter area, * - candidate default, U - per-user static route o - ODR, P - periodic downloaded static route


172.16.0.0/24 is subnetted, 2 subnetsC 172.16.2.0 is directly connected, Serial0/0/0C 172.16.3.0 is directly connected, FastEthernet0/0R2#_________________________________Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area * - candidate default, U - per-user static route, o - ODR P - periodic downloaded static route


172.16.0.0/24 is subnetted, 1 subnetsC 172.16.2.0 is directly connected, Serial0/0/0

162

Step 11: Turn off debugging on both routers using either no debug ip routing or simply, undebug all.

R1(config-if)#endR1#no debug ip routingIP routing debugging is off

Task 4: Finish Configuring Router Interfaces

Step 1: Configure Remaining R2 Interfaces

Finish configuring the remaining interfaces on R2 according to the Topology Diagram and Addressing Table.

Step 2: Configure R3 Interfaces

Console into R3 and configure the necessary interfaces according to the Topology Diagram and Addressing Table.



Configure the host PC1 with an IP address of 172.16.3.10/24 and a default gateway of 172.16.3.1.





163

Typical SOB 69

Task 6: Test and Verify the Configurations.

Step 1: Test connectivity.

Test connectivity by pinging from each host to the default gateway that has been configured for that host.

From the host PC1, is it possible to ping the default gateway? ________From the host PC2, is it possible to ping the default gateway? ________From the host PC3, is it possible to ping the default gateway? ________

If the answer is no for any of these questions, troubleshoot the configurations to find the error using the following systematic process:

1. Check the cabling. Are the PCs physically connected to the correct router? ________(Connection could be through a switch or directly)Are link lights blinking on all relevant ports? ________

2. Check the PC configurations. Do they match the Topology Diagram? ________3. Check the router interfaces using the show ip interface brief command.

Are all relevant interfaces up and up? ________

If your answer to all three steps is yes, you should be able to successfully ping the default gateway.

Step 2: Use the ping command to test connectivity between directly connected routers.

From the router R2, is it possible to ping R1 at 172.16.2.1? ________From the router R2, is it possible to ping R3 at 192.168.1.1? ________

If the answer is no for any of these questions, troubleshoot the configurations to find the error using the following systematic process:

1. Check the cabling. Are the routers physically connected? ________Are link lights blinking on all relevant ports? ________

164

Typical SOB 70

2. Check the router configurations. Do they match the Topology Diagram? ________Did you configure the clock rate command on the DCE side of the link? ________

3. Has the interface been activated or enabled? ________4. Check the router interfaces using the show ip interface brief command.

Are the interfaces up and up? ________

If your answer to all three steps is yes, you should be able to successfully ping from R2 to R1 and from R2 to R3.

Step 3: Use ping to check connectivity between devices that are not directly connected.

From the host PC3, is it possible to ping the host PC1? ________From the host PC3, is it possible to ping the host PC2? ________From the host PC2, is it possible to ping the host PC1? ________From the router R1, is it possible to ping router R3? ________These pings should all fail. Why?____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Task 7: Gather Information.

Step 1: Check status of interfaces.

Check the status of the interfaces on each router with the command show ip interface brief. The following output is for R2.

R2#show ip interface briefInterface IP-Address OK? Method Status ProtocolFastEthernet0/0 172.16.1.1 YES manual up upFastEthernet0/1 unassigned YE Sunset administratively downdownSerial0/0/0 172.16.2.2 YES manual up upSerial0/0/1 192.168.1.2 YES manual up upVlan1 unassigned YES manual administratively down down

165

Typical SOB 71

Are all of the relevant interfaces on each router activated (that is, in the up and up state)? _________How many interfaces are activated on R1 and R3? __________Why are there three activated interfaces on R2? _______________________________________________________________________________________________________________

Step 2: View the routing table information for all three routers.

R1#________________________________Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area * - candidate default, U - per-user static route, o - ODR P - periodic downloaded static route


172.16.0.0/24 is subnetted, 2 subnetsC 172.16.2.0 is directly connected, Serial0/0/0C 172.16.3.0 is directly connected, FastEthernet0/0

What networks are present in the Topology Diagram but not in the routing table for R1? ___________________________________________________________________________

R2#_________________________________Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default U - per-user static route, o - ODR


172.16.0.0/24 is subnetted, 2 subnetsC 172.16.1.0 is directly connected, FastEthernet0/0C 172.16.2.0 is directly connected, Serial0/0/0C 192.168.1.0/24 is directly connected, Serial0/0/1


166



C 192.168.1.0/24 is directly connected, Serial0/0/1C 192.168.2.0/24 is directly connected, FastEthernet0/0


Why are all the networks not in the routing tables for each of the routers?______________________________________________________________________________________________________________________________________________________

What can be added to the network so that devices that are not directly connected can ping each other? ___________________________________________________________________________

Task 8: Configure a Static Route Using a Next-Hop Address.

Step 1: To configure static routes with a next-hop specified, use the following syntax:

Router(config)# ip route network-address subnet-mask ip-address network-address:—Destination network address of the remote network to be

added to the routing table. subnet-mask—Subnet mask of the remote network to be added to the routing

table. The subnet mask can be modified to summarize a group of networks. ip-address—Commonly referred to as the next-hop router’s IP address.

On the R3 router, configure a static route to the 172.16.1.0 network using the Serial 0/0/1 interface of R2 as the next-hop address.

167

Excellent SOB 72

R3(config)#ip route 172.16.1.0 255.255.255.0 192.168.1.2R3(config)#

Step 2: View the routing table to verify the new static route entry.

Notice that the route is coded with an S, which means that the route is a static route.

R3#_________________________________

Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default U - per-user static route, o - ODR


172.16.0.0/24 is subnetted, 1 subnetsS 172.16.1.0 [1/0] via 192.168.1.2C 192.168.1.0/24 is directly connected, Serial0/0/1C 192.168.2.0/24 is directly connected, FastEthernet0/0R3#

With this route entered in the routing table, any packet that matches the first 24 left-most bits of 172.16.1.0/24 will be forwarded to the next-hop router at 192.168.1.2. What interface will R3 use to forward packets to the 172.16.1.0/24 network? ____________

Assume that the following packets have arrived at R3 with the indicated destination addresses. Will R3 discard the packet or forward the packet? If R3 forwards the packet, with what interface will R3 send the packet?

Packet Destination IP Discard or Forward? Interface1 172.16.2.1 _________ _________2 172.16.1.10 _________ _________3 192.168.1.2 _________ _________4 172.16.3.10 _________ _________5 192.16.2.10 _________ _________

Although R3 will forward packets to destinations for which there is a route, this does not mean that a packet will arrive safely at the final destination.

168

Step 3: Use ping to check connectivity between the host PC3 and the host PC2.

From the host PC3, is it possible to ping the host PC2? ________These pings should fail. The pings will arrive at PC2 if you have configured and verified all devices through Task 7, “Gather Information.” PC2 will send a ping reply back to PC3. However, the ping reply will be discarded at R2 because the R2 does not have a return route to the 192.168.2.0 network in the routing table.

Step 4: On the R2 router, configure a static route to reach the 192.168.2.0 network.

What is the next-hop address to which R2 would send a packet destined for the 192.168.2.0/24 network?

R2(config)#ip route 192.168.2.0 255.255.255.0 ________________R2(config)#


Notice that the route is coded with an S, which means the route is a static route.

R2#_________________________________

Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default U - per-user static route, o - ODR


172.16.0.0/24 is subnetted, 2 subnetsC 172.16.1.0 is directly connected, FastEthernet0/0C 172.16.2.0 is directly connected, Serial0/0/0C 192.168.1.0/24 is directly connected, Serial0/0/1S 192.168.2.0/24 [1/0] via 192.168.1.1R2#

Step 6: Use ping to check connectivity between the host PC3 and the host PC2.

From the host PC3, is it possible to ping the host PC2? ________This ping should be successful.

169

Task 9: Configure a Static Route Using an Exit Interface.

To configure static routes with an exit interface specified, use the following syntax:

Router(config)# ip route network-address subnet-mask exit-interface

network-address—Destination network address of the remote network to be added to the routing table.

subnet-mask—Subnet mask of the remote network to be added to the routing table. The subnet mask can be modified to summarize a group of networks.

exit-interface—Outgoing interface that would be used in forwarding packets to the destination network.

Step 1: On the R3 router, configure a static route.

On the R3 router, configure a static route to the 172.16.2.0 network using the Serial 0/0/1 interface of the R3 router as the exit interface.

R3(config)# ip route 172.16.2.0 255.255.255.0 Serial0/0/1R3(config)#


R3#________________________________Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default U - per-user static route, o - ODR


172.16.0.0/24 is subnetted, 2 subnetsS 172.16.1.0 [1/0] via 192.168.1.2S 172.16.2.0 is directly connected, Serial0/0/1C 192.168.1.0/24 is directly connected, Serial0/0/1C 192.168.2.0/24 is directly connected, FastEthernet0/0R3#

Use the show running-config command to verify the static routes that are currently configured on R3.

R3#show running-config

170

Building configuration...

<output omitted>!hostname R3!interface FastEthernet0/0ip address 192.168.2.1 255.255.255.0!interface Serial0/0/0 no ip address shutdown!interface Serial0/0/1 ip address 192.168.1.1 255.255.255.0!ip route 172.16.1.0 255.255.255.0 192.168.1.2ip route 172.16.2.0 255.255.255.0 Serial0/0/1!end

How would you remove either of these routes from the configuration?___________________________________________________________________________

Step 3: On the R2 router, configure a static route.

On the R2 router, configure a static route to the 172.16.3.0 network using the Serial 0/0/0 interface of the R2 router as the exit interface.

R2(config)# ip route 172.16.3.0 255.255.255.0 Serial0/0/0R2(config)#



Gateway of last resort is not set171

172.16.0.0/24 is subnetted, 3 subnetsC 172.16.1.0 is directly connected, FastEthernet0/0C 172.16.2.0 is directly connected, Serial0/0/0S 172.16.3.0 is directly connected, Serial0/0/0C 192.168.1.0/24 is directly connected, Serial0/0/1S 192.168.2.0/24 [1/0] via 192.168.1.1R2#

At this point, R2 has a complete routing table with valid routes to all five networks shown in the Topology Diagram. Does this mean that R2 can receive ping replies from all destinations shown in the Topology Diagram? ________Why or why not?______________________________________________________________________________________________________________________________________________________

Step 5: Use ping to check connectivity between the host PC2 and PC1.

This ping should fail because the R1 router does not have a return route to the 172.16.1.0 network in the routing table.

Task 10: Configure a Default Static Route.

In the previous steps, you configured the router for specific destination routes. But could you do this for every route on the Internet? No. The router and you would be overwhelmed. To minimize the size of the routing tables, add a default static route. A router uses the default static route when there is not a better, more specific route to a destination.

Instead of filling the routing table of R1 with static routes, we could assume that R1 is a stub router. This means that R2 is the default gateway for R1. If R1 has packets to route that do not belong to any of R1 directly connected networks, R1 should send the packet to R2. However, we must explicitly configure R1 with a default route before it will send packets with unknown destinations to R2. Otherwise, R1 discards packets with unknown destinations.

To configure a default static route, use the following syntax:

Router(config)#ip route 0.0.0.0 0.0.0.0 { ip-address | interface }

Step 1: Configure the R1 router with a default route.

Configure the R1 router with a default route using the interface option on Serial 0/0/0 of R1 as the next-hop interface.

172

R1(config)#ip route 0.0.0.0 0.0.0.0 172.16.2.2R1(config)#


R1#________________________________Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default U - per-user static route, o - ODR

Gateway of last resort is 172.16.2.2 to network 0.0.0.0

172.16.0.0/24 is subnetted, 2 subnets

C 172.16.2.0 is directly connected, Serial0/0/0C 172.16.3.0 is directly connected, FastEthernet0/0S* 0.0.0.0/0 [1/0] via 172.16.2.2R1#

Note that the R1 router now has a default route, the gateway of last resort, and will send all unknown traffic out Serial 0/0/0, which is connected to R2.


From the host PC2, is it possible to ping PC1? ________This ping should be successful this time because the R1 router can return the packet using the default route.From the host PC3, is it possible to ping the host PC1? ________Is there a route to the 172.16.3.0 network in the routing table on the R3 router? ________

Task 11: Configure a Summary Static Route.

We could configure another static route on R3 for the 172.16.3.0 network. However, we already have two static routes to 172.16.2.0/24 and 172.16.1.0/24. Because these networks are so close together, we can summarize them into one route. Again, doing this helps reduce the size of routing tables, which makes the route lookup process more efficient.

173

Threshold SOB 73

Looking at the three networks at the binary level, we can a common boundary at the 22 nd bit from the left.172.16.1.0 10101100.00010000.00000001.00000000172.16.2.0 10101100.00010000.00000010.00000000172.16.3.0 10101100.00010000.00000011.00000000

The prefix portion will include 172.16.0.0, because this would be the prefix if we turned off all the bits to the right of the 22nd bit.

Prefix 172.16.0.0

To mask the first 22 left-most bits, we use a mask with 22 bits turned on from left to right:

Bit Mask 11111111.11111111.11111100.00000000

This mask, in dotted-decimal format, is...

Mask 255.255.252.0

Step 1: Configure the summary static route on the R3 router.

The network to be used in the summary route is 172.16.0.0/22. R3(config)#ip route 172.16.0.0 255.255.252.0 192.168.1.2

Step 2: Verify that the summary route is installed in the routing table.

R3#________________________________Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area * - candidate default, U - per-user static route, o - ODR P - periodic downloaded static route


172.16.0.0/16 is variably subnetted, 3 subnets, 2 masksS 172.16.0.0/22 [1/0] via 192.168.1.2S 172.16.1.0/24 [1/0] via 192.168.1.2S 172.16.2.0/24 is directly connected, Serial0/0/1C 192.168.1.0/24 is directly connected, Serial0/0/1C 192.168.2.0/24 is directly connected, FastEthernet0/0

174

Configuring a summary route on R3 did not remove the static routes configured earlier because these routes are more specific routes. They both use /24 mask, whereas the new summary will be using a /22 mask. To reduce the size of the routing table, we can now remove the more specific /24 routes.

Step 3: Remove static routes on R3.

Remove the two static routes that are currently configured on R3 by using the no form of the command.

R3(config)#no ip route 172.16.1.0 255.255.255.0 192.168.1.2 R3(config)#no ip route 172.16.2.0 255.255.255.0 Serial0/0/1

Step 4: Verify that the routes are no longer in the routing table.

R3#_________________________________Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area * - candidate default, U - per-user static route, o - ODR P - periodic downloaded static route


172.16.0.0/22 is subnetted, 1 subnetsS 172.16.0.0 [1/0] via 192.168.1.2C 192.168.1.0/24 is directly connected, Serial0/0/1C 192.168.2.0/24 is directly connected, FastEthernet0/0

R3 now only has one route to any host belonging to networks 172.16.0.0/24, 172.16.1.0/24, 172.16.2.0/24, and 172.16.3.0/24. Traffic destined for these networks will be sent to R2 at 192.168.1.2.


From the host PC3, is it possible to ping the host PC1? ________This ping should be successful this time because there is a route to the 172.16.3.0 network on the R3 router, and the R1 router can return the packet using the default route.

175

Task 12: Summary, Reflection, and Documentation

With the completion of this lab, you have: Configured your first network with a combination of static and default routing to

provide full connectivity to all networks Observed how a route is installed in the routing table when you correctly configure

and activate the interface Learned how to statically configure routes to destinations that are not directly

connected Learned how to configure a default route that is used to forward packets to unknown

destinations Learned how to summarize a group of networks into one static route to reduce the size

of a routing tableAlong the way, you have also probably encountered some problems either in your physical lab setup or in your configurations. Hopefully, you have learned to systematically troubleshoot such problems. At this point, record any comments or notes that may help you in future labs.____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Finally, you should document your network implementation. On each router, capture the following command output to a text (.txt) file and save for future reference.

show running-config show ip route show ip interface brief

176

Threshold SOB 74

Task 13: Clean Up

Erase the configurations and reload the routers. Disconnect and store the cabling. For PC hosts that are normally connected to other networks (such as the school LAN or to the Internet), reconnect the appropriate cabling and restore the TCP/IP settings.

177

Excellent SOB 75

Lab 20: Basic RIP Configuration (Packet Tracer)

Topology Diagram

Learning Objectives

Upon completion of this lab, you will be able to:

Cable a network according to the Topology Diagram. Erase the startup configuration and reload a router to the default state. Perform basic configuration tasks on a router. Configure and activate interfaces. Configure RIP routing on all routers. Verify RIP routing using show and debug commands. Reconfigure the network to make it contiguous. Observe automatic summarization at boundary router. Gather information about RIP processing using the debug ip rip command. Configure a static default route. Propagate default routes to RIP neighbours. Document the RIP configuration.

Scenarios

Scenario A: Running RIPv1 on Classful Networks Scenario B: Running RIPv1 with Subnets and Between Classful Networks Scenario C: Running RIPv1 on a Stub Network.

178

Scenario A: Running RIPv1 on Classful Networks

Topology Diagram

Addressing Table


R1 Fa0/0 192.168.1.1 255.255.255.0 N/AS0/0/0 192.168.2.1 255.255.255.0 N/A

R2Fa0/0 192.168.3.1 255.255.255.0 N/AS0/0/0 192.168.2.2 255.255.255.0 N/AS0/0/1 192.168.4.2 255.255.255.0 N/A

R3 Fa0/0 192.168.5.1 255.255.255.0 N/AS0/0/1 192.168.4.1 255.255.255.0 N/A


179

Task 1: Prepare the Network.

Step 1: Cable a network that is similar to the one in the Topology Diagram.

Step 2: Clear any existing configurations on the routers.

Task 2: Perform Basic Router Configurations.

Perform basic configuration of the R1, R2, and R3 routers according to the following guidelines:

1. Configure the router hostname.2. Disable DNS lookup.3. Configure an EXEC mode password.4. Configure a message-of-the-day banner.5. Configure a password for console connections.6. Configure a password for VTY connections.

Task 3: Configure and Activate Serial and Ethernet Addresses.

Step 1: Configure interfaces on R1, R2, and R3.

Configure the interfaces on the R1, R2, and R3 routers with the IP addresses from the table under the Topology Diagram.

Step 2: Verify IP addressing and interfaces.

Use the show ip interface brief command to verify that the IP addressing is correct and that the interfaces are active.

Are all router interfaces active? _________

Are you able to get a successful reply between all routers interfaces? _________

180

Typical SOB 76

Typical SOB 77

If not troubleshoot the problem before you proceed.

Step 3: Configure Ethernet interfaces of PC1, PC2, and PC3.

Configure the Ethernet interfaces of PC1, PC2, and PC3 with the IP addresses and default gateways from the table under the Topology Diagram.

Step 4: Test the PC configuration by pinging the default gateway from the PC.

Is network connection successful? __________

Task 4: Configure RIP.

Step 1: Enable dynamic routing.

To enable a dynamic routing protocol, enter global configuration mode and use the router command.

Enter router ? at the global configuration prompt to a see a list of available routing protocols on your router.

To enable RIP, enter the command router rip in global configuration mode.

R1(config)#router ripR1(config-router)#

Step 2: Enter classful network addresses.

Once you are in routing configuration mode, enter the classful network address for each directly connected network, using the network command.

R1(config-router)#network 192.168.1.0R1(config-router)#network 192.168.2.0R1(config-router)#

The network command:

Enables RIP on all interfaces that belong to this network. These interfaces will now both send and receive RIP updates.

Advertises this network in RIP routing updates sent to other routers every 30 seconds.

181

Typical SOB 78

When you are finished with the RIP configuration, return to privileged EXEC mode.

R1(config-router)#end%SYS-5-CONFIG_I: Configured from console by consoleR1#

Step 3: Configure RIP on the R2 router using the router rip and network commands.

R2(config)#router ripR2(config-router)#network 192.168.2.0R2(config-router)#network 192.168.3.0R2(config-router)#network 192.168.4.0R2(config-router)#end%SYS-5-CONFIG_I: Configured from console by consoleR2#


Step 4: Configure RIP on the R3 router using the router rip and network commands.

R3(config)#router ripR3(config-router)#network 192.168.4.0R3(config-router)#network 192.168.5.0R3(config-router)#end%SYS-5-CONFIG_I: Configured from console by consoleR3#


Task 5: Verify RIP Routing.

Step 1: Use the show ip route command to verify that each router has all of the networks in the topology entered in the routing table.

Routes learned through RIP are coded with an R in the routing table. If the tables are not converged as shown here, troubleshoot your configuration.

182

Excellent SOB 79

Did you verify that the configured interfaces are active? ___________

Did you configure RIP correctly? ___________

Return to Task 3 and Task 4 to review the steps necessary to achieve convergence.

R1#show ip routeCodes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area * - candidate default, U - per-user static route, o - ODR P - periodic downloaded static route


C 192.168.1.0/24 is directly connected, FastEthernet0/0C 192.168.2.0/24 is directly connected, Serial0/0/0R 192.168.3.0/24 [120/1] via 192.168.2.2, 00:00:04, Serial0/0/0R 192.168.4.0/24 [120/1] via 192.168.2.2, 00:00:04, Serial0/0/0R 192.168.5.0/24 [120/2] via 192.168.2.2, 00:00:04, Serial0/0/0R1#

R2#show ip route

<Output omitted>

R 192.168.1.0/24 [120/1] via 192.168.2.1, 00:00:22, Serial0/0/0C 192.168.2.0/24 is directly connected, Serial0/0/0C 192.168.3.0/24 is directly connected, FastEthernet0/0C 192.168.4.0/24 is directly connected, Serial0/0/1R 192.168.5.0/24 [120/1] via 192.168.4.1, 00:00:23, Serial0/0/1R2#

R3#show ip route

<Output omitted>

R 192.168.1.0/24 [120/2] via 192.168.4.2, 00:00:18, Serial0/0/1R 192.168.2.0/24 [120/1] via 192.168.4.2, 00:00:18, Serial0/0/1R 192.168.3.0/24 [120/1] via 192.168.4.2, 00:00:18, Serial0/0/1

183

C 192.168.4.0/24 is directly connected, Serial0/0/1C 192.168.5.0/24 is directly connected, FastEthernet0/0R3#

Step 2: Use the show ip protocols command to view information about the routing processes.

The show ip protocols command can be used to view information about the routing processes that are occurring on the router. This output can be used to verify most RIP parameters to confirm that:

RIP routing is configured The correct interfaces send and receive RIP updates The router advertises the correct networks RIP neighbors are sending updates

R1#show ip protocols Routing Protocol is "rip"Sending updates every 30 seconds, next due in 16 secondsInvalid after 180 seconds, hold down 180, flushed after 240Outgoing update filter list for all interfaces is not setIncoming update filter list for all interfaces is not setRedistributing: ripDefault version control: send version 1, receive any version

Interface Send Recv Triggered RIP Key-chainFastEthernet0/0 1 2 1 Serial0/0/0 1 2 1

Automatic network summarization is in effectMaximum path: 4Routing for Networks:

192.168.1.0192.168.2.0

Passive Interface(s):Routing Information Sources:

Gateway Distance Last Update192.168.2.2 120

Distance: (default is 120)R1#

184

R1 is indeed configured with RIP. R1 is sending and receiving RIP updates on FastEthernet0/0 and Serial0/0/0. R1 is advertising networks 192.168.1.0 and 192.168.2.0. R1 has one routing information source. R2 is sending R1 updates.

Step 3: Use the debug ip rip command to view the RIP messages being sent and received.

Rip updates are sent every 30 seconds so you may have to wait for debug information to be displayed.

R1#debug ip ripR1#RIP: received v1 update from 192.168.2.2 on Serial0/0/0 192.168.3.0 in 1 hops 192.168.4.0 in 1 hops 192.168.5.0 in 2 hopsRIP: sending v1 update to 255.255.255.255 via FastEthernet0/0 (192.168.1.1)RIP: build update entries network 192.168.2.0 metric 1 network 192.168.3.0 metric 2 network 192.168.4.0 metric 2 network 192.168.5.0 metric 3RIP: sending v1 update to 255.255.255.255 via Serial0/0/0 (192.168.2.1)RIP: build update entries network 192.168.1.0 metric 1

The debug output shows that R1 receives an update from R2. Notice how this update includes all the networks that R1 does not already have in its routing table. Because the FastEthernet0/0 interface belongs to the 192.168.1.0 network configured under RIP, R1 builds an update to send out that interface. The update includes all networks known to R1 except the network of the interface. Finally, R1 builds an update to send to R2. Because of split horizon, R1 only includes the 192.168.1.0 network in the update.

Step 4: Discontinue the debug output with the undebug all command.

R1#undebug allAll possible debugging has been turned off

185

Excellent SOB 80

Scenario B: Running RIPv1 with Subnets and Between Classful Networks

Topology Diagram

Addressing Table


R1Fa0/0 172.30.1.1 255.255.255.0 N/AS0/0/0 172.30.2.1 255.255.255.0 N/A

R2Fa0/0 172.30.3.1 255.255.255.0 N/AS0/0/0 172.30.2.2 255.255.255.0 N/AS0/0/1 192.168.4.9 255.255.255.252 N/A

R3Fa0/0 192.168.5.1 255.255.255.0 N/AS0/0/1 192.168.4.10 255.255.255.252 N/A


Task 1: Make Changes between Scenario A and Scenario B

Step 1: Change the IP addressing on the interfaces as shown in the Topology Diagram and the Addressing Table.

Sometimes when changing the IP address on a serial interface, you may need to reset that interface by using the shutdown command, waiting for the LINK-5-CHANGED message,

186

and then using the no shutdown command. This process will force the IOS to starting using the new IP address.

R1(config)#int s0/0/0

R1(config-if)#ip add 172.30.2.1 255.255.255.0R1(config-if)#shutdown

%LINK-5-CHANGED: Interface Serial0/0/0, changed state to administratively down%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0, changed state to downR1(config-if)#no shutdown

%LINK-5-CHANGED: Interface Serial0/0/0, changed state to upR1(config-if)#%LINEPROTO-5-UPDOWN: Line protocol on Interface Serial0/0/0, changed state to up

Step 2: Verify that routers are active.

After reconfiguring all the interfaces on all three routers, verify that all necessary interfaces are active with the show ip interface brief command.

Did you verify that the configured interfaces are active? ___________

Step 3: Remove the RIP configurations from each router.

Although you can remove the old network commands with the no version of the command, it is more efficient to simply remove RIP and start over. Remove the RIP configurations from each router with the no router rip global configuration command. This will remove all the RIP configuration commands including the network commands.

R1(config)#no router rip



Why is it necessary to remove rip configuration at this stage?

_________________________________________________________________________________________________________________________________________________________________________________________________________________________________

187

Task 2: Configure RIP

Step 1: Configure RIP routing on R1 as shown below.

R1(config)#router ripR1(config-router)#network 172.30.0.0

Notice that only a single network statement is needed for R1. This statement includes both interfaces on different subnets of the 172.30.0.0 major network.

Step 2: Configure R1 to stop sending updates out the FastEthernet0/0 interface.

The passive-interface fastethernet 0/0 command is used to disable sending RIPv1 updates out that interface. When you are finished with the RIP configuration, return to privileged EXEC mode.

R1(config-router)#passive-interface fastethernet 0/0R1(config-router)#end%SYS-5-CONFIG_I: Configured from console by consoleR1#

Why is it necessary to stop R1 from sending updates out of Fa0/0?_______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________


R2(config)#router rip R2(config-router)#network 172.30.0.0

188

Typical SOB 81

Excellent SOB 82

R2(config-router)#network 192.168.4.0R2(config-router)#passive-interface fastethernet 0/0R2(config-router)#end%SYS-5-CONFIG_I: Configured from console by consoleR2#

Again notice that only a single network statement is needed for the two subnets of 172.30.0.0. This statement includes both interfaces, on different subnets, of the 172.30.0.0 major network. The network for the WAN link between R2 and R3 is also configured.



R3(config)#router rip R3(config-router)#network 192.168.4.0R3(config-router)#network 192.168.5.0R3(config-router)#passive-interface fastethernet 0/0R3(config-router)#end%SYS-5-CONFIG_I: Configured from console by consoleR3#


Task 3: Verify RIP Routing

Step 1: Use the show ip route command to verify that each router has all of the networks in the topology in the routing table.

R1#show ip route

<Output omitted>

172.30.0.0/24 is subnetted, 3 subnetsC 172.30.1.0 is directly connected, FastEthernet0/0C 172.30.2.0 is directly connected, Serial0/0/0R 172.30.3.0 [120/1] via 172.30.2.2, 00:00:22, Serial0/0/0R 192.168.4.0/24 [120/1] via 172.30.2.2, 00:00:22, Serial0/0/0

189

Typical SOB 83

R 192.168.5.0/24 [120/2] via 172.30.2.2, 00:00:22, Serial0/0/0R1#Note: RIPv1 is a classful routing protocol. Classful routing protocols do not send the subnet mask with network in routing updates. For example, 172.30.1.0 is sent by R2 to R1 without any subnet mask information.

R2#show ip route

<Output omitted>

172.30.0.0/24 is subnetted, 3 subnetsR 172.30.1.0 [120/1] via 172.30.2.1, 00:00:04, Serial0/0/0C 172.30.2.0 is directly connected, Serial0/0/0C 172.30.3.0 is directly connected, FastEthernet0/0 192.168.4.0/30 is subnetted, 1 subnetsC 192.168.4.8 is directly connected, Serial0/0/1R 192.168.5.0/24 [120/1] via 192.168.4.10, 00:00:19, Serial0/0/1R2#

R3#show ip route

<Output omitted>

R 172.30.0.0/16 [120/1] via 192.168.4.9, 00:00:22, Serial0/0/1 192.168.4.0/30 is subnetted, 1 subnetsC 192.168.4.8 is directly connected, Serial0/0/1C 192.168.5.0/24 is directly connected, FastEthernet0/0

Step 2: Verify that all necessary interfaces are active.

If one or more routing tables does not have a converged routing table, first make sure that all necessary interfaces are active with show ip interface brief.

Then use show ip protocols to verify the RIP configuration. Notice in the output from this command that the FastEthernet0/0 interface is no longer listed under Interface but is now listed under a new section of the output: Passive Interface(s).

R1#show ip protocolsRouting Protocol is "rip" Sending updates every 30 seconds, next due in 20 seconds Invalid after 180 seconds, hold down 180, flushed after 240 Outgoing update filter list for all interfaces is not set

190

Incoming update filter list for all interfaces is not set Redistributing: rip Default version control: send version 2, receive version 2

Interface Send Recv Triggered RIP Key-chainSerial0/1/0 2 2

Automatic network summarization is in effect Maximum path: 4 Routing for Networks: 172.30.0.0 209.165.200.0Passive Interface(s):

FastEthernet0/0 Routing Information Sources: Gateway Distance Last Update 209.165.200.229 120 00:00:15 Distance: (default is 120)

Step 3: View the RIP messages being sent and received.

To view the RIP messages being sent and received use the debug ip rip command. Why are there no messages being sent from Fa0/0?

______________________________________________________________________________________________________________________________________________________

R1#debug ip ripR1#RIP: sending v1 update to 255.255.255.255 via Serial0/0/0 (172.30.2.1)RIP: build update entries network 172.30.1.0 metric 1RIP: received v1 update from 172.30.2.2 on Serial0/0/0 172.30.3.0 in 1 hops


R1#undebug allAll possible debugging has been turned off

191

Typical SOB 84

192

Excellent SOB 85

Scenario C: Running RIPv1 on a Stub Network

Topology Diagram

Background

In this scenario we will modify Scenario B to only run RIP between R1 and R2. Scenario C is a typical configuration for most companies connecting a stub network to a central headquarters router or an ISP. Typically, a company runs a dynamic routing protocol (RIPv1 in our case) within the local network but finds it unnecessary to run a dynamic routing protocol between the company’s gateway router and the ISP. For example, colleges with multiple campuses often run a dynamic routing protocol between campuses but use default routing to the ISP for access to the Internet. In some cases, remote campuses may even use default routing to the main campus, choosing to use dynamic routing only locally.

To keep our example simple, for Scenario C, we left the addressing intact from Scenario B. Let’s assume that R3 is the ISP for our Company XYZ, which consists of the R1 and R2 routers using the 172.30.0.0/16 major network, subnetted with a /24 mask. Company XYZ is a stub network, meaning that there is only one way in and one way out of the 172.30.0.0/16 network—in via R2 (the gateway router) and out via R3 (the ISP). It doesn’t make sense for R2 to send R3 RIP updates for the 172.30.0.0 network every 30 seconds, because R3 has no other way to get to 172.30.0.0 except through R2. It makes more sense for R3 to have a static route configured for the 172.30.0.0/16 network pointing to R2.

How about traffic from Company XYZ toward the Internet? It makes no sense for R3 to send over 120,000 summarized Internet routes to R2. All R2 needs to know is that if a packet is not destined for a host on the 172.30.0.0 network, then it should send the packet to the ISP, R3. This is the same for all other Company XYZ routers (only R1 in our case). They should

193

send all traffic not destined for the 172.30.0.0 network to R2. R2 would then forward the traffic to R3.

Task 1: Make Changes between Scenario B and Scenario C.

Step 1: Remove network 192.168.4.0 from the RIP configuration for R2.

Why should you remove network 192.168.4.0 from the RIP configuration for R2?____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

R2(config)#router ripR2(config-router)#no network 192.168.4.0

Step 2: Completely remove RIP routing from R3.


Task 2: Configure the Static Route on R3 for the 172.30.0.0/16 network.

Why do you need to configure Static Route on R3?_________________________________________________________________________________________________________________________________________________________________________________________________________________________________

R3(config)#ip route 172.30.0.0 255.255.252.0 serial0/0/1

194

Typical SOB 86

Excellent SOB 87

Task 3: Configure a Default Static Route on R2.

Step 1: Configure R2 to send default traffic to R3.

Configure a default static route on R2 that will send all default traffic—packets with destination IP addresses that do not match a specific route in the routing table—to R3.

R2(config)# ip route 0.0.0.0 0.0.0.0 serial 0/0/1

Step 2: Configure R2 to send default static route information to R1.

The default-information originate command is used to configure R2 to include the default static route with its RIP updates. Configure this command on R2 so that the default static route information is sent to R1.

R2(config)#router rip R2(config-router)#default-information originate R2(config-router)#

Note: Sometimes it is necessary to clear the RIP routing process before the default-information originate command will work. First, try the command clear ip route * on both R1 and R2. This command will cause the routers to immediately flush routes in the routing table and request updates from each other. Sometimes this does not work with RIP. If the default route information is still not sent to R1, save the configuration on R1 and R2 and then reload both routers. Doing this will reset the hardware and both routers will restart the RIP routing process.

Task 4: Verify RIP Routing.

Step 1: Use the show ip route command to view the routing table on R2 and R1.

R2#show ip route

Notice that R2 now has a static route tagged as a candidate default.

R1#show ip route

195

Typical SOB 88

Notice that R1 now has a RIP route tagged as a candidate default route. The route is the “quad-zero” default route sent by R2. R1 will now send default traffic to the Gateway of last resort at 172.30.2.2, which is the IP address of R2.

Step 2: View the RIP updates that are sent and received on R1 with the debug ip rip command.

R1#debug ip ripRIP protocol debugging is onR1#RIP: sending v1 update to 255.255.255.255 via Serial0/0/0 (172.30.2.1)RIP: build update entries network 172.30.1.0 metric 1RIP: received v1 update from 172.30.2.2 on Serial0/0/0 0.0.0.0 in 1 hops 172.30.3.0 in 1 hops

Notice that R1 is receiving the default route from R2.


R1#undebug all

Step 4: Use the show ip route command to view the routing table on R3.

R3#show ip route

Notice that RIP is not being used on R3. The only route that is not directly connected is the static route.

Task 5: Document the Router Configurations

On each router, capture the following command output to a text file and save for future reference:

Running configuration Routing table Interface summarization Output from show ip protocols

196

Typical SOB 89

197

Excellent SOB 90

Lab 21 - Configuring VLANs and Trunking (Hardware Equipment)

Topology

Addressing Table


S1 VLAN 1 192.168.1.11 255.255.255.0 N/AS2 VLAN 1 192.168.1.12 255.255.255.0 N/APC-A NIC 192.168.10.3 255.255.255.0 192.168.10.1PC-B NIC 192.168.10.4 255.255.255.0 192.168.10.1PC-C NIC 192.168.20.3 255.255.255.0 192.168.20.1

Objectives

Part 1: Build the Network and Configure Basic Device Settings

Part 2: Create VLANs and Assign Switch Ports

Part 3: Maintain VLAN Port Assignments and the VLAN Database

198

Part 4: Configure an 802.1Q Trunk between the Switches

Part 5: Delete the VLAN Database

Background / Scenario

Modern switches use virtual local-area networks (VLANs) to improve network performance by separating large Layer 2 broadcast domains into smaller ones. VLANs can also be used as a security measure by controlling which hosts can communicate. In general, VLANs make it easier to design a network to support the goals of an organization.

VLAN trunks are used to span VLANs across multiple devices. Trunks allow the traffic from multiple VLANS to travel over a single link, while keeping the VLAN identification and segmentation intact.

In this lab, you will create VLANs on both switches in the topology, assign VLANs to switch access ports, verify that VLANs are working as expected, and then create a VLAN trunk between the two switches to allow hosts in the same VLAN to communicate through the trunk, regardless of which switch the host is actually attached to.

Note: The switches used are Cisco Catalyst 2960s with Cisco IOS Release 15.0(2) (lanbasek9 image). Other switches and Cisco IOS versions can be used. Depending on the model and Cisco IOS version, the commands available and output produced might vary from what is shown in the labs.

Note: Ensure that the switches have been erased and have no startup configurations. If you are unsure contact your instructor.

Required Resources

2 Switches (Cisco 2960 with Cisco IOS Release 15.0(2) lanbasek9 image or comparable)

3 PCs (Windows 7, Vista, or XP with 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

Task 1: Build the Network and Configure Basic Device Settings

Step 1: Cable the network as shown in the topology.

Attach the devices as shown in the topology diagram, and cable as necessary.

199

Step 2: Initialize and reload the switches as necessary.

Step 3: Configure basic settings for each switch.

a. Disable DNS lookup.b. Configure device name as shown in the topology.c. Assign class as the privileged EXEC password.d. Assign cisco as the console and vty passwords and enable login for console and vty

lines.e. Configure logging synchronous for the console line.f. Configure a MOTD banner to warn users that unauthorized access is prohibited.g. Configure the IP address listed in the Addressing Table for VLAN 1 on both switches.h. Administratively deactivate all unused ports on the switch.i. Copy the running configuration to the startup configuration.

Step 4: Configure PC hosts.

Refer to the Addressing Table for PC host address information.

Step 5: Test connectivity.

Verify that the PC hosts can ping one another.

Note: It may be necessary to disable the PCs firewall to ping between PCs. Can PC-A ping

PC-B?

Can PC-A ping PC-C? Can PC-A ping S1? Can PC-B ping

PC-C? Can PC-B ping S2? Can PC-C ping

S2? Can S1 ping S2?

If you answered no to any of the above questions, why were the pings unsuccessful?

______________________________________________________________________________________________________________________________________________________

200

Typical SOB 91

Task 2: Create VLANs and Assign Switch Ports

In Task 2, you will create student, faculty, and management VLANs on both switches. You will then assign the VLANs to the appropriate interface. The show vlan command is used to verify your configuration settings.

Step 1: Create VLANs on the switches.

a. Create the VLANs on S1.S1(config)# vlan 10S1(config-vlan)# name Student S1(config-vlan)# vlan 20 S1(config-vlan)# name Faculty S1(config-vlan)# vlan 99 S1(config-vlan)# name Management S1(config-vlan)# end

b. Create the same VLANs on S2.c. Issue the show vlan command to view the list of VLANs on S1.

S1# show vlan

VLAN Name Status Ports---- -------------------------------- --------- -------------------------------

default active Fa0/1, Fa0/2, Fa0/3, Fa0/4 Fa0/5, Fa0/6, Fa0/7, Fa0/8 Fa0/9, Fa0/10, Fa0/11, Fa0/12 Fa0/13, Fa0/14, Fa0/15, Fa0/16 Fa0/17, Fa0/18, Fa0/19, Fa0/20 Fa0/21, Fa0/22, Fa0/23, Fa0/24 Gi0/1, Gi0/2

10 Student active20 Faculty active99 Management active

1002 fddi-default act/unsup1003 token-ring-default act/unsup1004 fddinet-default act/unsup1005 trnet-default act/unsup

VLAN

Type SAID MTU Parent RingNo BridgeNo Stp BrdgModeTrans1 Trans2

---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------1 enet 100001 1500 - - - - - 0 010 enet 100010 1500 - - - - - 0 020 enet 100020 1500 - - - - - 0 099 enet 100099 1500 - - - - - 0 0

VLAN

Type SAID MTU Parent RingNo BridgeNo Stp BrdgModeTrans1 Trans2

---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ ------201

1002 fddi 101002 1500 - - - - - 0 01003 tr 101003 1500 - - - - - 0 01004 fdnet 101004 1500 - - - ieee - 0 01005 trnet 101005 1500 - - - ibm - 0 0

Remote SPAN VLANs------------------------------------------------------------------------------

Primary Secondary Type Ports------- --------- ----------------- ------------------------------------------

What is the default VLAN?

What ports are assigned to the default VLAN?_______________________________

Step 2: Assign VLANs to the correct switch interfaces.

a. Assign VLANs to the interfaces on S1.1) Assign PC-A to the Student VLAN.

S1(config)# interface f0/6S1(config-if)# switchport mode accessS1(config-if)# switchport access vlan 10

2) Move the switch IP address VLAN 99.S1(config)# interface vlan 1 S1(config-if)# no ip address S1(config-if)# interface vlan 99S1(config-if)# ip address 192.168.1.11 255.255.255.0S1(config-if)# end

b. Issue the show vlan brief command and verify that the VLANs are assigned to the correct interfaces.S1# show vlan brief

VLAN Name Status Ports

---- -------------------------------- --------- -------------------------------

default active Fa0/1, Fa0/2, Fa0/3, Fa0/4 Fa0/5, Fa0/7, Fa0/8, Fa0/9 Fa0/10, Fa0/11, Fa0/12, Fa0/13 Fa0/14, Fa0/15, Fa0/16, Fa0/17 Fa0/18, Fa0/19, Fa0/20, Fa0/21 Fa0/22, Fa0/23, Fa0/24, Gi0/1 Gi0/2

202

Excellent SOB 92

10 Student active Fa0/6

20 Faculty active

99 Management active

1002 fddi-default act/unsup

1003 token-ring-default act/unsup

1004 fddinet-default act/unsup

1005 trnet-default act/unsup

c. Issue the show ip interfaces brief command.

What is the status of VLAN 99? Why?__________________________________________________________________________________________________________________________________________

d. Use the Topology to assign VLANs to the appropriate ports on S2.e. Remove the IP address for VLAN 1 on S2.f. Configure an IP address for VLAN 99 on S2 according to the Addressing Table.g. Use the show vlan brief command to verify that the VLANs are assigned to the

correct interfaces.

S2# show vlan brief

VLAN Name Status Ports---- -------------------------------- --------- -------------------------------1 default active Fa0/1, Fa0/2, Fa0/3, Fa0/4Fa0/5, Fa0/6, Fa0/7, Fa0/8 Fa0/9, Fa0/10, Fa0/12, Fa0/13 Fa0/14, Fa0/15, Fa0/16, Fa0/17 Fa0/19, Fa0/20, Fa0/21, Fa0/22

Fa0/23, Fa0/24, Gi0/1, Gi0/210 Student active Fa0/1120 Faculty active Fa0/18

99 Management active

1002 fddi-default act/unsup

1003 token-ring-default act/unsup

1004 fddinet-default act/unsup

203

Typical SOB 93

1005 trnet-default act/unsup

Is PC-A able to ping PC-B? Why?______________________________________________________________________________________________________________________________________________________

Is S1 able to ping S2? Why?

______________________________________________________________________________________________________________________________________________________

Task 3: Maintain VLAN Port Assignments and the VLAN Database

In Task 3, you will change VLAN assignments to ports and remove VLANs from the VLAN database.

Step 1: Assign a VLAN to multiple interfaces.

a. On S1, assign interfaces F0/11 – 24 to VLAN 10.S1(config)# interface range f0/11-24 S1(config-if-range)# switchport mode access S1(config-if-range)# switchport access vlan 10 S1(config-if-range)# end

b. Issue the show vlan brief command to verify VLAN assignments.c. Reassign F0/11 and F0/21 to VLAN 20.d. Verify that VLAN assignments are correct

Step 2: Remove a VLAN assignment from an interface.

a. Use the no switchport access vlan command to remove the VLAN 10 assignment to F0/24.S1(config)# interface f0/24S1(config-if)# no switchport access vlanS1(config-if)# end

b. Verify that the VLAN change was made. Which VLAN is F0/24 is now associated with?_____________________________________________________________________

204

Typical SOB 94

Step 3: Remove a VLAN ID from the VLAN database.

a. Add VLAN 30 to interface F0/24 without issuing the VLAN command.S1(config)# interface f0/24S1(config-if)# switchport access vlan 30% Access VLAN does not exist. Creating vlan 30

Note: Current switch technology no longer requires that the vlan command be issued to add a VLAN to the database. By assigning an unknown VLAN to a port, the VLAN adds to the VLAN database.

b. Verify that the new VLAN is displayed in the VLAN table.S1# show vlan brief

VLAN Name Status Ports---- -------------------------------- --------- -------------------------------default active Fa0/1, Fa0/2, Fa0/3, Fa0/4 Fa0/5, Fa0/6, Fa0/7, Fa0/8 Fa0/9, Fa0/10, Gi0/1, Gi0/2active Fa0/12, Fa0/13, Fa0/14, Fa0/15 Fa0/16, Fa0/17, Fa0/18, Fa0/19 Fa0/20, Fa0/22, Fa0/23

20 Faculty active Fa0/11, Fa0/2130 VLAN0030 active Fa0/2499 Management active1002 fddi-default act/unsup1003 token-ring-default act/unsup1004 fddinet-default act/unsup1005 trnet-default act/unsup

What is the default name of VLAN 30?__________________________________________________________________________________________________________________________________________

c. Use the no vlan 30 command to remove VLAN 30 from the VLAN database.S1(config)# no vlan 30S1(config)# end

d. Issue the show vlan brief command. F0/24 was assigned to VLAN 30.After deleting VLAN 30, what VLAN is port F0/24 assigned to? What happens to the

205

Typical SOB 95

traffic destined to the host attached to F0/24?__________________________________________________________________________________________________________________________________________

S1# show vlan brief

e. Issue the no switchport access vlan command on interface F0/24.f. Issue the show vlan brief command to determine the VLAN assignment for F0/24.

To which VLAN is F0/24 assigned?_____________________________________________________________________

Note: Before removing a VLAN from the database, it is recommended that you reassign all the ports assigned to that VLAN.

Why should you reassign a port to another VLAN before removing the VLAN from the VLAN database?_______________________________________________________________________________________________________________________________________________________________________________________________________________

Task 4: Configure an 802.1Q Trunk Between the Switches

In Task 4, you will configure interface F0/1 to use the Dynamic Trunking Protocol (DTP) to allow it to negotiate the trunk mode. After this has been accomplished and verified, you will disable DTP on interface F0/1 and manually configure it as a trunk.

Step 1: Use DTP to initiate trunking on F0/1.

The default DTP mode of a 2960 switch port is dynamic auto. This allows the interface to convert the link to a trunk if the neighbouring interface is set to trunk or dynamic desirable mode.

a. Set F0/1 on S1 to negotiate trunk mode.S1(config)# interface f0/1S1(config-if)# switchport mode dynamic desirable

b. Issue the show vlan brief command on S1 and S2.Interface F0/1 is no longer assigned to VLAN 1. Trunked interfaces are not listed in the VLAN table.S1# show vlan brief

206

Excellent SOB 96

VLAN Name Status Ports---- -------------------------------- --------- -------------------------------default active Fa0/2, Fa0/3, Fa0/4, Fa0/5 Fa0/7, Fa0/8, Fa0/9, Fa0/10 Fa0/24, Gi0/1, Gi0/2Student active Fa0/6, Fa0/12, Fa0/13, Fa0/14 Fa0/15, Fa0/16, Fa0/17, Fa0/18 Fa0/19, Fa0/20, Fa0/22, Fa0/23

20 Faculty active Fa0/11, Fa0/2199 Management active1002 fddi-default act/unsup1003 token-ring-default act/unsup1004 fddinet-default act/unsup1005 trnet-default act/unsup

c. Issue the show interfaces trunk command to view trunked interfaces. Notice that the mode on S1 is set to desirable, and the mode on S2 is set to auto.

S1# show interfaces trunk

Port Fa0/1

Mode desirable Encapsulation 802.1q

Status trunking

Native vlan 1

Port Fa0/1

Vlans allowed 1-4094

on trunk

Port Vlans allowed and active in management domain Fa0/1 1,10,20,99

Port Vlans in spanning tree forwarding state and not pruned Fa0/11,10,20,99


Port Mode Encapsulation Status Native vlanFa0/1

Port

auto

Vlans

802.1q

allowed on trunk

trunking 1

Fa0/1 1-4094


207

Port Vlans in spanning tree forwarding state and not pruned Fa0/1 1,10,20,99

Note: By default, all VLANs are allowed on a trunk. The switchport trunk command allows you to control what VLANs have access to the trunk. For this lab, keep the default settings which allows all VLANs to traverse F0/1.

d. Verify that VLAN traffic is traveling over trunk interface F0/1.

Can S1 ping S2?___________ Can PC-A ping PC-B?___________ Can PC-A ping PC-C?___________ Can PC-B ping PC-C?___________ Can PC-A ping S1?____________ Can PC-B ping S2?___________ Can PC-C ping S2?___________

If you answered no to any of the above questions, explain below.__________________________________________________________________________________________________________________________________________

Step 2: Manually configure trunk interface F0/1.

The switchport mode trunk command is used to manually configure a port as a trunk. This command should be issued on both ends of the link.

a. Change the switchport mode on interface F0/1 to force trunking. Make sure to do this on both switches.

S1(config)# interface f0/1

S1(config-if)# switchport mode trunk

b. Issue the show interfaces trunk command to view the trunk mode. Notice that the mode changed from desirable to on.


Port Mode Encapsulation Status Native vlan Fa0/1 on 802.1q trunking 99

Port Vlans allowed on trunk

Fa0/1 1-4094


Port Vlans in spanning tree forwarding state and not pruned Fa0/1 1,10,20,99Why might you want to manually configure an interface to trunk mode instead of using DTP?

208

Excellent SOB 97

_________________________________________________________________________________________________________________________________________________________________________________________________________________________________

Task 5: Delete the VLAN Database

In Task 5, you will delete the VLAN Database from the switch. It is necessary to do this when initializing a switch back to its default settings.

Step 1: Determine if the VLAN database exists.

Issue the show flash command to determine if a vlan.dat file exists in flash.S1# show flash

Directory of flash:/

2 -rwx 1285 Mar 1 199300:01:24 +00:00 config.text3 -rwx 43032 Mar 1 199300:01:24 +00:00 multiple-fs4 -rwx 5 Mar 1 199300:01:24 +00:00 private-config.text5 -rwx 11607161 Mar 1 199302:37:06 +00:00 c2960-lanbasek9-mz.150-2.SE.bin6 -rwx 736 Mar 1 199300:19:41 +00:00 vlan.dat

32514048 bytes total (20858880 bytes free)

Note: If there is a vlan.dat file located in flash, then the VLAN database does not contain its default settings.

Step 2: Delete the VLAN database.

a. Issue the delete vlan.dat command to delete the vlan.dat file from flash and reset the VLAN database back to its default settings. You will be prompted twice to confirm that you want to delete the vlan.dat file. Press Enter both times.

S1# delete vlan.dat

Delete filename [vlan.dat]? Delete flash:/vlan.dat? [confirm] S1#

b. Issue the show flash command to verify that the vlan.dat file has been deleted.

S1# show flash209

Excellent SOB 98

Directory of flash:/

2 -rwx 1285 Mar 1 199300:01:24 +00:00 config.text3 -rwx 43032 Mar 1 199300:01:24 +00:00 multiple-fs4 -rwx 5 Mar 1 199300:01:24 +00:00 private-config.text5 -rwx 11607161 Mar 1 199302:37:06 +00:00 c2960-lanbasek9-mz.150-2.SE.bin

32514048 bytes total (20859904 bytes free)

To initialize a switch back to its default settings, what other commands are needed?______________________________________________________________________________________________________________________________________________________

Task 6: Reflection

1. What is needed to allow hosts on VLAN 10 to communicate to hosts on VLAN 20?_________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

2. What are some primary benefits that an organization can receive through effective use of VLANs?_________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________

210

Excellent SOB 99

Excellent SOB 100

laborotory workbook 2016/17€¦ · web viewby the end of this course, students will be able to...

Documents