Cisco Networking Academy Student Packet Tracer Manual

  • 5,394 views
Uploaded on

CCNA Discovery 3: …

CCNA Discovery 3:
Designing and Supporting Computer Networks v4.0
Student Packet Tracer Manual

StadiumCompany Story
The Discovery “Designing and Supporting Computer Networks” course uses the fictional StadiumCompany network upgrade story in the main text and media presentation and in Packet Tracer activities. StadiumCompany is a stadium management company that manages a large sports facility.

When the sports facility was built, the network that supported its business offices and security services provided state-of-the-art communications capabilities. Over the years, the company added new equipment and increased the number of connections without considering the overall business goals and long-term infrastructure design. Some projects went ahead without an understanding of the bandwidth, traffic prioritization, and other requirements needed to support this advanced and business-critical network. Now the StadiumCompany management wants to improve the customer experience by adding high-tech features and support for concerts, but the underlying network cannot support these additions.

The StadiumCompany management understands that they do not have sufficient network expertise to support the network upgrade. The StadiumCompany decides to hire network consultants to provide design, project management, and implementation support. The project will be implemented in three phases. The first phase is to plan the project and prepare the high-level network design. The second phase is to develop the detailed network design. The third phase is to implement the design.

After a few meetings, StadiumCompany hires the NetworkingCompany, a local network design and consulting firm to support the phase 1, high-level design. NetworkingCompany is a Cisco Premier Partner employing 20 network engineers who have various CCNA, CCDA, CCNP, CCDP, and CCIE certifications and significant industry experience.

To create the high-level design, the NetworkingCompany first interviewed the staff at the stadium and developed a profile of the organization and the facility.

More in: Technology , Education
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
5,394
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
670
Comments
0
Likes
2

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. This document is exclusive property of Cisco Systems, Inc. Permission is granted toprint and copy this document for non-commercial distribution and exclusive use byinstructors in the CCNA Discovery Designing and Supporting Computer Networkscourse as part of an official Cisco Networking Academy.
  • 2. CCNA DiscoveryDesigning and Supporting Computer NetworksStadiumCompany StoryThe Discovery “Designing and Supporting Computer Networks” course uses the fictional StadiumCompanynetwork upgrade story in the main text and media presentation and in Packet Tracer activities. StadiumCompanyis a stadium management company that manages a large sports facility.When the sports facility was built, the network that supported its business offices and security services providedstate-of-the-art communications capabilities. Over the years, the company added new equipment and increasedthe number of connections without considering the overall business goals and long-term infrastructure design.Some projects went ahead without an understanding of the bandwidth, traffic prioritization, and otherrequirements needed to support this advanced and business-critical network. Now the StadiumCompanymanagement wants to improve the customer experience by adding high-tech features and support for concerts,but the underlying network cannot support these additions.The StadiumCompany management understands that they do not have sufficient network expertise to support thenetwork upgrade. The StadiumCompany decides to hire network consultants to provide design, projectmanagement, and implementation support. The project will be implemented in three phases. The first phase is toplan the project and prepare the high-level network design. The second phase is to develop the detailed networkdesign. The third phase is to implement the design.After a few meetings, StadiumCompany hires the NetworkingCompany, a local network design and consultingfirm to support the phase 1, high-level design. NetworkingCompany is a Cisco Premier Partner employing 20network engineers who have various CCNA, CCDA, CCNP, CCDP, and CCIE certifications and significantindustry experience.To create the high-level design, the NetworkingCompany first interviewed the staff at the stadium and developeda profile of the organization and the facility.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 6
  • 3. CCNA DiscoveryDesigning and Supporting Computer NetworksStadiumCompany OrganizationThe StadiumCompany provides the network infrastructure and facilities at the stadium. The StadiumCompany has170 full-time people:• 35 managers and executives• 135 salaried personnelApproximately 80 additional hourly workers are hired as needed to support events in the facility and securitydepartments.StadiumManagementOfficesStadiumCompany Phones and PCsAll the managers and executives at the StadiumCompany use PCs and phones connected to a digital voice PBX.With the exception of the full-time grounds people and the janitors, all the salaried personnel also use PCs andphones.Fifty shared phones for the security staff are distributed throughout the stadium. There are also 12 analogphones, some that support faxes and others that provide direct access to the police and fire stations. The securitygroup also has 30 security cameras implemented on a separate network.Existing Facilities and SupportThe StadiumCompany provides facilities and network support for two sports teams (Team A and Team B), avisiting team, a restaurant, and a concessions vendor.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 6
  • 4. CCNA DiscoveryDesigning and Supporting Computer NetworksThe stadium is approximately 725 feet wide by 900 feet long (approximately 220 meters wide by 375 meterslong). There are two levels. Because of the size of the facility, multiple wiring closets connected with fiber-opticcabling are distributed throughout the stadium.The Team A and Team B locker rooms and player lounges are on the first level of the south side of the stadium.The team offices are on the second level and measure 50 feet x 200 feet (approximately 15 meters wide by 60meters long)The office and locker room of the visiting team are also located on the first level.StadiumCompany offices are in the north side of the stadium on both levels. The office space on the first levelmeasures 200 feet x 60 feet (approximately 60 meters wide by 18 meters long), and measures 200 feet x 50 feet(approximately 60 meters wide by 15 meters long) on the second level.Team A and Team B are in different sports leagues with different seasons. They both contract with theStadiumCompany for offices and services at the stadium.Team A OrganizationTeam A has 90 people in the organization:• 4 executives• 12 coaches• 14 support staff (including doctors, masseuse, secretary, assistants, finance and accounting)• 60 playersTeam A has 15 offices in the stadium to support their non-player staff. Five of these offices are shared. There are24 PCs and 28 phones installed in the offices.Team A also has a player locker room and a large player lounge and workout room. The non-player staff uses thefacility year round. Players have access to the locker room and workout equipment both during the season andAll contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 3 of 6
  • 5. CCNA DiscoveryDesigning and Supporting Computer Networksthe off-season. There are 5 phones in the locker room, and 15 phones in the player lounge. There are rumors thatTeam A recently installed a wireless hub in the player lounge.Team B OrganizationTeam B has 64 people in the organization:• 4 executives• 8 coaches• 12 support staff (including doctors, masseuse, secretary, assistants, finance and accounting)• 40 playersTeam B has 12 offices in the stadium to support their non-player staff. Three of the offices are shared. There are19 PCs and 22 phones installed in the offices. They also have a player locker room and a large player lounge.The non-player staff uses the facility year round. Players have access to the locker room and workout equipmentboth during the season and the off season. There are 5 phones in the locker room, and 15 phones in the playerlounge.Visiting Team SupportThe visiting team locker room and lounge has 10 phones. Each visiting team requires temporary support on thegame day and for a few days before the game. The visiting teams also contract with the StadiumCompany foroffice support and services at the stadium.Concession VendorA concession vendor manages the concessions provided at games and events. There are five full-timeemployees. They use two private and two shared offices with five PCs and seven phones. These offices arelocated on the south side of the stadium between the Team A and Team B office space. Two part-time employeestake orders from the luxury boxes during events. The concession vendor uses seasonal hourly workers to support32 permanent concession stands and other services distributed throughout the stadium. At this time, there are nophones or PCs in the concession areas.Luxury Restaurant OrganizationThere is one luxury restaurant at the stadium that is open year round. In addition to the customer and kitchenareas, the restaurant contracts for office space from the StadiumCompany. The four managers have privateoffices. The two salaried financial and accounting staff share an office. Six PCs and phones are supported. Twoadditional phones are used for reservations in the customer area.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 4 of 6
  • 6. CCNA DiscoveryDesigning and Supporting Computer NetworksLuxury Skybox SupportThere are 20 luxury skyboxes. The StadiumCompany provides a phone in each skybox that supports local callsand calls to the luxury restaurant and the concession vendor.Press Area SupportThe StadiumCompany provides a press box with three shared areas:• The press print area typically houses 40 to 50 reporters during a game. There are 10 analog phones availablein this shared area, and two shared data ports. It is known that one newspaper intern brings in a smallwireless Access Point for games that she covers.• The press radio area supports 15 to 20 radio announcers and has 10 analog phone lines.• The press TV area typically supports 10 people. There are five phones available here.Remote Site SupportThe StadiumCompany currently has two remote locations: a ticketing office located in the downtown area, and asouvenir shop in a local shopping mall. The remote locations are connected using DSL service to a local Internetservice provider (ISP).All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 5 of 6
  • 7. CCNA DiscoveryDesigning and Supporting Computer NetworksThe stadium is connected to the local ISP using ISP1, a managed services router owned by the ISP. The tworemote sites have a connection to the same ISP supported by the ISP2 and ISP3 routers provisioned andmanaged by the ISP. This connection provides the remote sites access to the databases located on servers in theStadiumCompany management offices. The StadiumCompany also has a perimeter router named Edge Routerthat connects to the ISP1 router at the stadium.StadiumCompany PlansThe StadiumCompany wants to add new services, such as video, to their network. They are also thinking aboutreplacing the existing digital voice PBX. They would like better access to their existing security camera network.Two new remote sites are planned in the near future:• A film production company that has been hired to provide video during and after the sporting events andconcerts needs to connect to the stadium network to exchange files.• Team A is expanding to a remote office location. They are requesting access to the same network resourcesthat they use on the stadium LAN.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 6 of 6
  • 8. 1.2.1 3 What Happens at the Core Layer? Activity - Packet Tracer - pka1.2.3 2 Network Convergence Activity - Packet Tracer - pka1.3.1 3 What Happens at the Distribution Layer? Activity - Packet Tracer - pka1.3.2 2 Limiting the Scope of Network Failure Activity - Packet Tracer - pka1.3.4 3 Traffic Filtering at the Distribution Layer Activity - Packet Tracer - pka1.4.1 4 What Happens at the Access Layer? Activity - Packet Tracer - pka1.4.2 2 Network Topologies at the Access Layer Activity - Packet Tracer - pka1.5.1 2 What is a Server Farm? Activity - Packet Tracer - pka1.5.3 2 High Availability Activity - Packet Tracer - pka3.1.1 5 Creating a Network Diagram Activity - Packet Tracer - pka3.1.3 2 Developing a Modular Diagram Activity - Packet Tracer - pka3.1.4 3 Strengths and Weaknesses of the Existing Network Activity - Packet Tracer - pka3.2.4 4 Download and Install Cisco IOS Software Activity - Packet Tracer - pka3.3.3 2 Installing a New Hardware Option Activity - Packet Tracer - pka3.4.3 3 Wireless Site Survey and Planning Activity - Packet Tracer - pka5.2.2 3 Designing Distribution Layer Topology Activity - Packet Tracer - pka5.3.2 2 Defining Traffic Patterns and Application Support Activity - Packet Tracer - pka5.3.4 2 Creating the Logical Network Design for the WAN Activity - Packet Tracer - pka5.5.3 2 Updating the Logical Network Design Documentation Activity - Packet Tracer - pka6.1.1 4 Using Hierarchical Routing and Addressing Schemes Activity - Packet Tracer - pka6.1.2 2 Classful Subnets and Summarization Activity - Packet Tracer - pka6.1.3 2 Using VLSM when Designing IP Addressing Activity - Packet Tracer - pka6.2.3 4 Designating the Routing Strategy Activity - Packet Tracer - pka6.2.5 3 Designing the Addressing Scheme Activity - Packet Tracer - pka7.1.4 3 Validating LAN Technologies and Devices Activity - Packet Tracer - pka7.2.2 3 Creating the Test Plan Activity - Packet Tracer - pka7.2.3 2 Validating the Choice of Devices and Topologies Activity - Packet Tracer - pka7.2.4 2 Validating the Choice of Routing Protocol Activity - Packet Tracer - pka7.2.5 2 Validating the IP Addressing Scheme Activity - Packet Tracer - pka7.3.2 3 Creating the Test Plan Activity - Packet Tracer - pka7.3.4 3 Validating the Security Plan Activity - Packet Tracer - pka8.1.2 3 Testing WAN Connectivity with Simulation Software Activity - Packet Tracer - pka8.2.5 4 Troubleshooting Frame Relay Operation Activity - Packet Tracer - pka
  • 9. CCNA DiscoveryDesigning and Supporting Computer Networks1.2.1 Comparing Mesh TopologiesObjectives• Compare the routing tables of a partial mesh topology with a full mesh topology• Observe the convergence of the network when an interface is shut down and brought back up• Examine the EIGRP packets in the Simulation Mode as the network convergesBackground / PreparationYou have been provided with a partial mesh and a full mesh topology to examine in this exercise. The interfaceshave been addressed and EIGRP has been configured as the routing protocol. All necessary configurationcommands have been entered into the routers and the networks are fully functional.Required file: Comparing Mesh Topologies.pkaStep 1: Compare the routing tables of the partial mesh and full mesh topologya. Use the Inspect tool to examine the routing table on HQP and HQF.b. Notice the difference in the number of routes in each table.c. Record the routes to 192.168.0.204 network on HQP and the routes to the 172.16.3.196 network on HQF.Routes to 192.168.0.204______________________________________________________________________________________________________________________________________________________________________________Routes to 172.16.3.196_______________________________________________________________________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 2
  • 10. CCNA DiscoveryDesigning and Supporting Computer Networks_______________________________________________________________________________________Step 2: Examine the routing table and observe the convergence of a partial mesh topologya. Shut down the interface S0/0/1 on BR2P and observe the routing table on HQP.b. Note that two routes to the 192.168.0.204 network were removed.c. Bring the interface S0/0/1 back up and observe the routing table on HQP.d. Observe the convergence of the network (it may take a minute for both routes to be re-installed).e. Examine the routing table on HQP again. Which interface is used to reach network 192.168.0.160?______________________________________________________________________________________f. On router BR2P, shut down the interface S0/0/0. How will HQP get to the 192.168.0.160 network now?______________________________________________________________________________________g. Bring interface S0/0/0 on BR2P back up and observe the convergence of the network (it may take aminute).h. What happens to the routes to the 192.168.0.160 network that were in the routing table?______________________________________________________________________________________i. Repeat Step 2 process in the Simulation Mode with only the EIGRP filter active. Use the Capture /Forward button to examine the EIGRP packets and routing table as the network converges.Step 3: Examine the routing table and observe the convergence of a full mesh topologya. Shut down the interface S0/0/1 on BR2F and observe the routing table on HQF.b. Note that two routes to the 172.16.3.196 network were removed.c. Bring the interface S0/0/1 back up and observe the routing table on HQF.d. Observe the convergence of the network (it may take a minute for both routes to be re-installed).e. Examine the routing table on HQF again. Which interface is used to reach network 172.16.3.128?_____________________________________________________________________________________f. On router BR2F, shut down the interface S0/0/0. How will HQF get to the 172.16.3.128 network now?_____________________________________________________________________________________g. Bring interface S0/0/0 on BR2F back up and observe the convergence of the network (it may take aminute).h. What happens to the routes to the 172.16.3.128 network that were in the routing table?_____________________________________________________________________________________i. Repeat Step 3 process in the Simulation Mode with only the EIGRP filter active. Use the Capture /Forward button to examine the EIGRP packets and routing table as the network converges.Reflection1. On router BR2P, when you shut down the interface S0/0/0, why was the one original route to the192.168.0.160 network replaced with two routes?____________________________________________________________________________________________________________________________________________________________________________2. What are the advantages and disadvantages of a full mesh topology?__________________________________________________________________________________________________________________________________________________________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 2
  • 11. CCNA DiscoveryDesigning and Supporting Computer Networks1.2.3 Observing Network ConvergenceObjectives• Connect and configure WAN connections• Configure EIGRP to advertise specific networks• Observe the convergence of the network through the CLI window when an interface is shut down andbrought back up• Examine the EIGRP packets in the Simulation Mode as the network convergesBackground / PreparationYou have been provided a topology in which HQ, Branch1, Branch2, and Branch3 are pre-configured. A newrouter has been added to the topology (New_Branch) that is partially configured. You will need to connectNew_Branch to HQ and Branch1, complete the configuration of the new router, and then examine theconvergence of the network.Required file: Observing Network Convergence.pkaStep 1: Connect and configure WAN connection on New_Branch routera. Connect interface S0/0/0 on New_Branch to S0/1/1 on HQ (DCE)b. Connect interface S0/0/1 on New_Branch to S0/1/1 on Branch1 (DCE)c. Configure interface S0/0/0 with the IP address 172.16.3.218/30d. Configure interface S0/0/1 with the IP address 172.16.3.221/30Step 2: Configure EIGRP to advertise specific network on New_Branch routerAll contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 2
  • 12. CCNA DiscoveryDesigning and Supporting Computer Networksa. Configure New_Branch with EIGRP and the autonomous system number 3b. Advertise specifically the directly connected networksStep 3: Observe the network convergence in the Realtime modea. While in the CLI window of New_Branch, you can observe the convergence in the Realtime mode. As thenetwork converges you will see that EIGRP develops adjacencies.b. After the network has converged, shut down interface S0/0/0 on New_Branch.c. Observe the changes in the networkd. Bring interface S0/0/0 back upStep 4: Observe the network convergence in the Simulation modea. Click on Simulation Modeb. Set the Event List Filters to show only EIGRP packetsc. Go to CLI interface window of New_Branchd. Shutdown the interface S0/0/1e. Click on the Auto Capture / Play button to start the simulationf. Re-open the CLI window and observe the affectsg. Allows the simulation to run for a brief period, then click the Auto Capture / Play button to pause thesimulationh. Examine some to the packets in the Event ListStep 5: Observe the affects of an interface being brought upa. Re-start the simulation by clicking the Auto Capture / Play button again.b. Bring interface S0/0/1 back up and observe the convergence through the CLI window, Event List, andtopologyc. Stop the simulationReflection1. What output was shown in the CLI window once EIGRP had converged?____________________________________________________________________________________________________________________________________________________________________________2. When the WAN link between HQ and New_Branch went down, what happened to the EIGRP packets onthe New LAN?__________________________________________________________________________________________________________________________________________________________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 2
  • 13. CCNA DiscoveryDesigning and Supporting Computer Networks1.3.1 Demonstrating Distribution Layer FunctionsObjective• Demonstrate the functions performed by the Distribution Layer devices.Background / PreparationVLANs can be added to a network for security purposes and traffic control. Devices on separate VLANs areunable to communicate unless a router has been configured to help with this communication. Observe howpacket filtering and route summarization traverse the network using simulation mode.Required file: Demonstrating Distribution Layer FunctionsStep 1: Setup Simulation filters to capture routing protocolsa. Enter simulation mode in Packet Tracer.b. Click on the edit filters button.c. Select EIGRPd. Click on the Reset Simulation button.e. Click Auto Capture/Playf. Observe the EIGRP updatesStep 2: Test connectivity between the network devices using Realtime mode.a. From PC0 ping PC1, PC2, PC3, and PC4.b. From PC1 ping PC0, PC2, PC4, PC3Step 3: Test connectivity between the network devices using Simulation modea. Switch from Realtime mode to Simulation mode.b. Create a simple PDU from PC0 to PC1. Click Capture/Forward until the PDU has made the complete tripto PC1 and back.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 2
  • 14. CCNA DiscoveryDesigning and Supporting Computer Networksc. In the event list view the PDU events.d. Create another PDU from PC0 to PC2.Reflectiona. Why can’t PC0 communicate with PC1 but PC1 can communicate with PC0’s default gateway?b. What effect on connectivity would removing the subinterfaces have?c. Why must a router be in the topology to have communication between the VLANs?All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 2
  • 15. CCNA DiscoveryDesigning and Supporting Computer Networks1.3.2 Investigating Failure DomainsObjectivea. Observe the flow of network traffic in different topologiesb. Observe the change of flow in network traffic when a point of failure is introduced into the networkBackground / PreparationThis activity has three different topologies: a partial mesh, a star, and a full mesh. When this activity is started,you will need to allow time for each network topology to converge. This may take several minutes. Oncethe networks have converged, you will note the following:a. The partial mesh topology will have one link light on the PM4 switch that remains amber.b. The star topology will have all the link lights green.c. The full mesh topology will have three link lights amber; one on the FM1 switch and two on the FM3switch.Required file: Investigating Failure Domains.pkaIn the partial mesh and full mesh topology the network has redundant links. However, in order to avoid switchingloops some of the links have been shutdown as noted by the amber link light. Note that the star topology does notAll contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 3
  • 16. CCNA DiscoveryDesigning and Supporting Computer Networkshave redundant links between switches. Why are all of the link lights green in this topology?___________________________________________________________________________Good Distribution Layer design can limit the parts of the network that are affected by a network failure. The failureof a single device should not cause the network to go down. In this activity you will observe the flow of thenetwork traffic in each topology. Then you will introduce a point of failure in each network topology by deleting atrunk link between two switches. Once the link is removed, you will need to allow time for the network to re-converge. After the network has re-converged, you will again observe the flow of traffic and note how the networkfailure affected the flow of traffic.Step 1: Observe the flow of traffic on the partial mesh topologya. Once the network has converged, enter simulation mode by clicking on the Simulation tab.b. By default, Scenario 0 should be displayed in the Scenario window. Click on the Auto Capture/Playbutton and observe the flow of traffic from PM3B to PM4Bc. When the Buffer Full window appears, click Clear Event List.d. Click the Reset Simulation buttonStep 2: Introduce a point of failure on the partial mesh topologya. Delete the trunk link between PM2 and PM4b. Change to simulation mode by clicking on the Simulation tab.c. Play Scenario 0 again by clicking on the Auto Capture/ Play button and observe the flow of traffic fromPMB to PM4Bd. When the Buffer Full window appears, click Clear Event List.e. Click the Reset Simulation buttonStep 3: Observe the flow of traffic on the star topologya. Click on the dropdown arrow to the Scenario window and select Scenario 1.b. Play Scenario 1 by clicking on the Auto Capture/ Play button and observe the flow of traffic from S2A toS4Bc. Click Clear event List when the Buffer Full window appears and click the Reset Simulation buttonStep 4: Introduce a point of failure on the star topologya. Delete the trunk link between Star1 and Star2b. Since the star topology has no redundant links, the network will not need to re-convergec. Play Scenario 1 again and observe the flow of traffic from S2A to S4Bd. Click Clear event List when the Buffer Full window appears and click the Reset Simulation buttonStep 5: Observe the flow of traffic on the full mesh topologya. Click on the dropdown arrow to the Scenario window and select Scenario 2b. Play Scenario 2 by clicking the Auto Capture / Play button and observe the flow of traffic from FM1A toFM3Bc. Click Clear event List when the Buffer Full window appears and click the Reset Simulation buttonStep 6: Introduce a point of failure on the full mesh topologya. Delete the trunk link between FM2 and FM3b. Switch to the Realtime modec. Allow time for the network to converge. (This may take several minutes.)d. Play Scenario 2 again and observe the flow of traffic from FM1A to FM3Be. Click Clear event List when the Buffer Full window appears and click the Reset Simulation buttonReflection1. How was the effect of the network failure in the star topology different from the partial mesh and full meshtopologies?All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 3
  • 17. CCNA DiscoveryDesigning and Supporting Computer Networks_____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________2. What effect did the removal of the link in the star topology have on the hosts that were attached to theStar2 switch?_____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 3 of 3
  • 18. CCNA DiscoveryDesigning and Supporting Computer Networks1.3.4 Placing ACLsObjectives• Verify network connectivity• Examine the Access Control Lists (ACLs) that are configured on the routers• Determine the appropriate interface to apply the ACLs• Examine the affects of the ACLAll contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 2
  • 19. CCNA DiscoveryDesigning and Supporting Computer NetworksBackground / PreparationThis activity demonstrates how the flow of network traffic is affected by applying an ACL to permit or deny traffic inthe network. The network administrator has decided that all external web traffic goes only to the Web server.Also, in order to protect the data o their employees, the HR server is only accessible to HR employees.Therefore, ACLs will need to be implemented on the network. Another network technician has already configuredthe necessary ACLs on both the Gateway and Distribution2 routers. However, the ACLs have not been applied toan interface. You have been asked to apply the ACLs and verify that the appropriate traffic is permitted or denied.Required file: Placing ACLsStep 1: Verify network connectivitya. Verify that all of the PCs can communicate with each other and with the servers.b. Verify that the Internet Host can access the Web server (192.168.0.3), Sales server (192.168.10.2) andHR server (192.168.40.2) using the browser.Step 2: Examine the Access Control Lists that are configured on the routersa. Access the Distribution1 router. Use the following commands to view the ACL that has been configuredon the Distribution1 router:• show running-config• show access-lists 1b. Access the Gateway router. Use the following commands to view the ACL that has been configured onthe Gateway router:• show running-config• show access-lists 100Step 3: Determine the appropriate interface to apply the ACLsa. After examining the ACLs determine on which interface the ACLs should be appliedb. The ACL must be applied to an interface or subinterface before it will affect the network trafficc. The extended ACL should be placed closest to the source and the standard ACL should be closest to thedestination.d. Remember that only one ACL per port, per protocol, per direction is allowed.e. Apply the ACL to the appropriate interface or subinterface.Step 4: Examine the affects of the ACLa. Internet Host should be able to ping any device in the network, except HR1 or HR server.b. Internet Host should be able to access Web server (192.168.0.3) using the browser.c. Internet Host should not be able to access either the HR server (192.168.40.1) or Sales server(192.168.10.2) using the browser.d. HR2 should be able to access HR server (192.168.40.1) using ping or the browser.e. RandD2 should not be able to access HR server (192.168.40.1) using ping or the browser.Reflection1. How can ACLs be used to control the flow of network traffic?_______________________________________________________________________________________2. By default, what is always the last statement in an ACL?_______________________________________________________________________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 2
  • 20. CCNA DiscoveryDesigning and Supporting Computer Networks1.4.1 Exploring Access Layer FunctionsObjective• Describe the function of the Network Access Layer including equipment usually installed in the wiring closets.Background / PreparationEquipment installed at the Network Access Layer usually consists of Layer 2 switches. These switchesconnect to workgroup servers, workstations, and other end user equipment. The Network Access Layerswitches then connect to Layer 3 devices, such as routers and multi-layer switches, at the NetworkDistribution Layer.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 2
  • 21. CCNA DiscoveryDesigning and Supporting Computer NetworksA new office space is being created for users in the Sales and Marketing departments of an organization, thePCs have been set up and configured in the office area and a Layer 2 switch has been installed in the wiringcloset. You will connect the switch to the end user devices and to the router in the Network Distribution Layer.You will then configure the switch and verify connectivity to key devices in the network.Required file: Exploring Access Layer Functions.pkaStep 1: Connect the Access Layer switch.a. Using the proper cable, connect FastEthernet0/1 on switch Access1B to FastEthernet0/1 on routerDistribution1.b. Using the proper cable, connect PC Sales2 to the next interface on switch Access1B.c. Using the proper cable, connect PC Marketing2 to the next interface on switch Access1B.Step 2: Configure the Access Layer switch.a. Using the CLI on switch Access1B, configure the interface that connects to router Distribution1 tocarry traffic for all VLANs.b. Using the CLI on switch Access1B, configure the interface that connects to PC Sales2 to carry trafficfor all only VLAN 11.c. Using the CLI on switch Access1B, configure the interface that connects to PC Marketing2 to carrytraffic for all only VLAN 21.d. Check your configuration using the Check Results button. Correct any errors in the configuration.Step 3: Verify connectivity.a. From PC Sales2, ping server Sales at 192.168.10.2. Ping server HR at 192.168.40.2. Ping serverWeb at 192.168.0.3. All pings should be successful, if not verify the configuration.b. From PC Marketing2, ping server Sales at 192.168.10.2. Ping server HR at 192.168.40.2. Pingserver Web at 192.168.0.3. All pings should be successful, if not verify the configuration.c. From the Web Browser on PC Sales2, request a web page from URL http://www.Discovery.com (inPacket Tracer the URL is case sensitive). The page should be displayed.d. Switch to Simulation mode. From the Web Browser on PC Sales2 click the Go button to requestthe page again. Click the Auto Capture / Play button to observe the flow of traffic from the Accesslayer through the hierarchical network to the server farm.Step 4: Reflectiona. Why are the Sales and HR servers connected to the network at the Access Layer?b. If you wanted to restrict access to the HR server which hierarchical network layer would you place thenecessary configuration?All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 2
  • 22. CCNA DiscoveryDesigning and Supporting Computer Networks1.4.2 Creating TopologiesObjective• Create a network with a star topology.Background / PreparationYou have been given the task of designing a network using a star topology. The star topology is one with acentral point of connectivity. The central device should be a switch.Required file: Creating Topologies.pkaStep 1: Create a network using a star topology.a. Add a 2960 switch to the network topology between the Distriburtion2 router and the PCs.b. Connect the switch to the Distribution2 router’s fa0/0 interface.c. Connect the switch to each of the PC.d. Enable the fa0/0 interface on the Distribution2 router.Step 2: Reflectiona. What outcome would there be if a hub had been used instead of a switch?All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 2
  • 23. CCNA DiscoveryDesigning and Supporting Computer Networks________________________________________________________________________________________________________________________b. What is the advantage to a using a star topology?__________________________________________________________________________________________________________________________________________________________________________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 2
  • 24. CCNA DiscoveryDesigning and Supporting Computer Networks1.5.1 Observing and Recording Server TrafficObjective• Observe and record the way in which traffic moves to and from the servers on the network.Background / PreparationAn enterprise has installed servers containing sales and human resources information at the Access Layer oftheir network and an intranet web server and a DNS server in a server farm off of the Core Layer of thenetwork. This activity will observe the flow of traffic between a typical PC at the Access Layer and three ofthe servers in the network.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 2
  • 25. CCNA DiscoveryDesigning and Supporting Computer NetworksStep 1: Verify connectivity to the servers in the network.a. From the desktop of PC HR2, ping the HR server at IP address 192.168.40.2.b. From the desktop of PC HR2, ping the Sales server at IP address 192.168.10.2.c. From the desktop of PC HR2, ping the Web server at IP address 192.168.0.3.Step 2: Observe and record the way traffic moves in the network.a. Switch to Simulation mode. Click the Auto Capture / Play button to send a packet between PCHR2 and the HR server and back. Count the number of intermediate devices the packet passesthrough.b. Switch to scenario To Sales. Click the Auto Capture / Play button to send a packet between PCHR2 and the Sales server and back. Count the number of intermediate devices the packet passesthrough.c. Switch to scenario To Web. Click the Auto Capture / Play button to send a packet between PC HR2and the Web server and back. Count the number of intermediate devices the packet passes through.Step 3: Reflectiona. Based on your observations, what be would two advantages of putting all of the servers in the serverfarm?____________________________________________________________________________________________________________________________________________________________________________________________________________________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 2
  • 26. CCNA DiscoveryDesigning and Supporting Computer Networks1.5.3 Using Redundant Links on Server Farm DevicesObjective• Determine how redundancy affects server availability.Background / PreparationThe physical topology of the first network (Topology 1) has been designed without redundancy. To test the faulttolerance of the network, links should be removed to test the effect on the network and to determine if the networkcan recover from the removed link.The physical topology of the second network (Topology 2) has been designed and redundancy has beenincorporated into the design. To test the fault tolerance of the network, links should be removed to test the effecton the network and to determine if the network can recover from the downed link.Required file: Using Redundant Links on Server Farm Devices.pkaStep 1: Examine the network and the status of the links in Topology 1a. Examine Topology 1b. View the network and the active links within the network.c. Note which links are active and which links are blocked.d. Open PC1-A. At the command prompt, enter a command to send 100 ICMP requests to Server Web-A.The command format is ping –n 100 192.168.2.3.Step 2: Test single point of failure in network without redundancya. Since switches do not have power buttons, delete the link between Router-A and switch Server-A.1. Click on the red X located in the right panel of the Packet Tracer screen.2. Click on the cable between Router-A and switch Server-A.b. View the network and note the active links within the topology.c. There is no network redundancy and therefore a single point of failure within the network. There is nolonger a route to the servers.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 2
  • 27. CCNA DiscoveryDesigning and Supporting Computer NetworksStep 3: Examine the network and the status of the links in Topology 2a. Examine Topology 2.b. View the network and note the active links within the topology.c. Open PC1-B. At the command prompt, enter a command to send 100 ICMP requests to Server Web-A.The command format is ping –n 100 192.168.4.3d. Open PC2-B. At the command prompt, enter a command to send 100 ICMP requests to ServerMarketing-B. The command format is ping –n 100 192.168.4.6.Step 4: Test network redundancya. Delete the link between switch Server1-B and switch Server2-B.1. Click on the red X located in the right panel of the Packet Tracer screen.2. Click on the cross-over cable between switch Server1 and switch Server2.b. View the network and note the active links within the topology.c. Spanning Tree should recalculate and automatically begin using the alternate links.d. Delete the link between switch Server3-B and switch Server5-B.1. Click on the red X located in the right panel of the Packet Tracer screen.2. Click on the cross-over cable between switch Server3-B and switch Server5-B.e. View the network and note the active links within the topology.f. The topology should reconfigure and automatically begin using the alternative links.Reflectiona. Using the network without redundant equipment, what advantage would be gained by adding 1 additionalswitch to the design?________________________________________________________________________________________________________________________________________________________________________________________________b. When a network is designed to have redundancy and Spanning Tree is disabled on the Layer 2 switches,what effect would it have on the network?__________________________________________________________________________________________________________________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 2
  • 28. CCNA DiscoveryDesigning and Supporting Computer Networks3.1.1 Investigating Existing Network DevicesObjective• Use router and switch commands to obtain information about an existing network.Background / PreparationYou have been given the task of documenting a large campus network. When you arrive at the site youdiscover that the network administrator is not available and he has the only keys to the wiring closets and thecabinets containing the existing network documentation. Since information on the network is needed as soonas possible, you decide to discover as much information as possible using router and switch commands.You are given access to the administrator’s PC and are told that the Telnet access password for all devices iscisco and the password to enter privileged exec mode is class.Step 1: Discover and document the first device.a. Access the Admin PC and issue the ipconfig command from the command prompt to discover thedefault gateway.b. Telnet to the IP address of the gateway device and enter privileged exec mode using the passwordsgiven above.c. Issue IOS commands such as show running-config, show ip route, show interfaces, show ipinterface brief, show version and other commands to learn about the device.d. Issue IOS commands such as show cdp neighbors and show cdp neighbors detail to discoverinformation about connected devices. It may take a few minutes for the network to converge. If you donot see any neighboring devices initially, repeat the command until you do.e. Document the information you gather in the appropriate table below.f. Close the Telnet session by issuing the exit command.Step 2: Discover the remaining devices.a. Packet Tracer works best when you successfully ping a device before attempting to Telnet to it.Issue the ping command to the IP address of one of the devices you discovered in Step 1. Repeatthe ping command until it succeeds.b. Telnet to the IP address of the device and repeat the process in Step 1 to document the device.c. To not overuse the resources of Packet Tracer, do not Telnet from device to device. Always exit tothe command prompt before accessing the next device.d. Repeat the process until all devices in the network are discovered and documented.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 10
  • 29. CCNA DiscoveryDesigning and Supporting Computer Networkse. As you work, sketch out a diagram of the network devices and their interconnections.Device Tables:RouterHostname _________________________Model _________________________ IOS version ______________________________Interface IP Address Subnet Mask Connects to Device Connects to InterfaceRouterHostname _________________________Model _________________________ IOS version ______________________________Interface IP Address Subnet Mask Connects to Device Connects to InterfaceRouterHostname _________________________Model _________________________ IOS version ______________________________Interface IP Address Subnet Mask Connects to Device Connects to InterfaceRouterHostname _________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 10
  • 30. CCNA DiscoveryDesigning and Supporting Computer NetworksModel _________________________ IOS version ______________________________Interface IP Address Subnet Mask Connects to Device Connects to InterfaceSwitchHostname _________________________Model _________________________ IOS version ______________________________IP Address _______________________ Subnet Mask __________________________Default Gateway ________________________Trunk Ports Connects to Device Connects to InterfaceActive Access Ports VLAN Number VLAN NameAll contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 3 of 10
  • 31. CCNA DiscoveryDesigning and Supporting Computer NetworksSwitchHostname _________________________Model _________________________ IOS version ______________________________IP Address _______________________ Subnet Mask __________________________Default Gateway ________________________Trunk Ports Connects to Device Connects to InterfaceActive Access Ports VLAN Number VLAN NameSwitchHostname _________________________Model _________________________ IOS version ______________________________IP Address _______________________ Subnet Mask __________________________Default Gateway ________________________Trunk Ports Connects to Device Connects to InterfaceActive Access Ports VLAN Number VLAN NameAll contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 4 of 10
  • 32. CCNA DiscoveryDesigning and Supporting Computer NetworksSwitchHostname _________________________Model _________________________ IOS version ______________________________IP Address _______________________ Subnet Mask __________________________Default Gateway ________________________Trunk Ports Connects to Device Connects to InterfaceActive Access Ports VLAN Number VLAN NameSwitchHostname _________________________Model _________________________ IOS version ______________________________IP Address _______________________ Subnet Mask __________________________Default Gateway ________________________Trunk Ports Connects to Device Connects to InterfaceActive Access Ports VLAN Number VLAN NameAll contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 5 of 10
  • 33. CCNA DiscoveryDesigning and Supporting Computer NetworksSwitchHostname _________________________Model _________________________ IOS version ______________________________IP Address _______________________ Subnet Mask __________________________Default Gateway ________________________Trunk Ports Connects to Device Connects to InterfaceActive Access Ports VLAN Number VLAN NameSwitchHostname _________________________Model _________________________ IOS version ______________________________IP Address _______________________ Subnet Mask __________________________Default Gateway ________________________Trunk Ports Connects to Device Connects to InterfaceActive Access Ports VLAN Number VLAN NameAll contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 6 of 10
  • 34. CCNA DiscoveryDesigning and Supporting Computer NetworksSwitchHostname _________________________Model _________________________ IOS version ______________________________IP Address _______________________ Subnet Mask __________________________Default Gateway ________________________Trunk Ports Connects to Device Connects to InterfaceActive Access Ports VLAN Number VLAN NameSwitchHostname _________________________Model _________________________ IOS version ______________________________IP Address _______________________ Subnet Mask __________________________Default Gateway ________________________Trunk Ports Connects to Device Connects to InterfaceActive Access Ports VLAN Number VLAN NameAll contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 7 of 10
  • 35. CCNA DiscoveryDesigning and Supporting Computer NetworksSwitchHostname _________________________Model _________________________ IOS version ______________________________IP Address _______________________ Subnet Mask __________________________Default Gateway ________________________Trunk Ports Connects to Device Connects to InterfaceActive Access Ports VLAN Number VLAN NameSwitchHostname _________________________Model _________________________ IOS version ______________________________IP Address _______________________ Subnet Mask __________________________Default Gateway ________________________Trunk Ports Connects to Device Connects to InterfaceActive Access Ports VLAN Number VLAN NameAll contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 8 of 10
  • 36. CCNA DiscoveryDesigning and Supporting Computer NetworksNetwork Diagram:All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 9 of 10
  • 37. CCNA DiscoveryDesigning and Supporting Computer NetworksStep 3: Reflectiona. We used this technique to discover and document a campus LAN. Would the same technique workfor an enterprise network that included WAN links?____________________________________________________________________________________________________________________________________________________________________________________________________________________________________b. Could we use this technique in a network that included routers and switches from a manufacturerother than Cisco? Why or why not?____________________________________________________________________________________________________________________________________________________________________________________________________________________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 10 of 10
  • 38. CCNA DiscoveryDesigning and Supporting Computer Networks3.1.3 Creating Modular Block DiagramsObjective• Use a logical network diagram of the existing network to create a modularized view of the network.Background / PreparationStart with the logical diagram showing the critical network devices and representative user devices. Groupthe devices by their role within the network design hierarchy.The final step is to create the modular block diagram of the network.Required file: Creating Modular Block Diagrams.pkaAll contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 4
  • 39. CCNA DiscoveryDesigning and Supporting Computer NetworksStep 1: Group the devices by their role within the network design hierarchy.a. Using the Palette tool (second button from the right on the Main Tool Bar), drag an ellipse tohighlight the client devices in pink.b. Using the Palette tool, drag an ellipse to highlight the access layer devices in light blue.c. Using the Palette tool, drag an ellipse to highlight the distribution layer devices in light green.d. Using the Palette tool, drag an ellipse to highlight the core layer devices in yellow.Step 2: Create the modular block diagram of the network.a. Use the table on the next page to create the modular block diagram of the network by drawing andlisting the devices in the appropriate column.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 4
  • 40. CCNA DiscoveryDesigning and Supporting Computer NetworksModular Block Diagram:Client Devices Access Distribution Core Services andManagementAll contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 3 of 4
  • 41. CCNA DiscoveryDesigning and Supporting Computer NetworksStep 3: Reflectiona. Why is it important to group devices by their role within the network design hierarchy to analyze anexisting network?____________________________________________________________________________________________________________________________________________________________________________________________________________________________________b. What is an advantage of describing a network using a modular block diagram instead of in a narrativefashion?____________________________________________________________________________________________________________________________________________________________________________________________________________________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 4 of 4
  • 42. CCNA DiscoveryDesigning and Supporting Computer Networks3.1.4 Determining Network Strengths and WeaknessesObjective• Identify and document the strengths and weaknesses of the existing network.Background / PreparationIn the previous activity you created a modular block diagram of the Film Company network. The next step isto examine the physical layout of the devices in the network, the cabling plant and the device configurations toidentify and document the strengths and weaknesses of the existing network.Packet Tracer provides a limited physical view of the network where devices are placed in wiring closets invarious buildings in various cities. The physical view in this activity represents the building containing the FilmCompany and the building containing their ISP located in the same city. The Film Company building containsAll contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 4
  • 43. CCNA DiscoveryDesigning and Supporting Computer Networksa wiring closet containing the MDF and POP that serves the general office functions and a wiring closet forthe production area. Since all devices must be placed in wiring closets, wiring closets containing typicalclients devices used by the general office staff and the production staff have been placed in the approximatecenter of their respective areas. There is a conference room that is also used by visitors with wireless laptopcomputers that is represented by a wiring closet in its center. Assume all cabling in the Film Companybuilding is category 5 UTP.Step 1: Examine the physical location of devices.a. Switch from the Logical Workplace to the Physical Workplace, enter the Home City and note theextent of the wireless coverage around the Film Company building.b. Enter the Film Company building and note the extent of the wireless coverage within the building andthe location of the wiring closets and work areas.c. Enter each of the wiring closets and note where the various client devices and network devices arelocated.Step 2: Examine the device configurations.a. Switch from the Physical Workplace to the Logical Workplace.b. Access each of the network devices in the Film Company network. Examine each device usingcommands such as show running-config, show version, show interfaces and other commands.c. Look for information on the speed of various links, passwords, traffic filtering and any otherinformation you can gather.Step 3: Evaluate the network.a. Based on your observations from Steps 1 and 2, rate the network in the areas listed in the table onthe next page on a scale of 1 (lowest) to 5 (highest).All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 4
  • 44. CCNA DiscoveryDesigning and Supporting Computer NetworksNetwork Ratings:Lowest Highest1 2 3 4 5Hierarchical network designFirewall locationServer locationBandwidthQuality of wiringNetwork equipment suitabilityWireless securitySuitability for advanced services like IP phones or videoRedundancy and availabilityFailure domain sizePhysical securityAll contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 3 of 4
  • 45. CCNA DiscoveryDesigning and Supporting Computer NetworksStep 4: Reflectiona. List the strengths of the existing network.____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________b. List the weaknesses of the existing network.____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 4 of 4
  • 46. CCNA DiscoveryDesigning and Supporting Computer Networks3.2.4 Installing Cisco IOS SoftwareObjectives• Verify the IOS image currently installed on the router• Transfer a new IOS image to the Cisco router• Verify that the new image is installed• Specify an image boot order on the router• Verify that the proper image is loaded when the router boots upBackground / PreparationYou have been asked to upgrade a Cisco 1841 router with the latest IOS image to support encryption. Thenetwork administrator has informed you that the necessary IOS image has already been downloaded to theNetwork_Server. It is your task to verify the current IOS image and install the new image through the TFTP serverthat is installed on the network server. You will also need to configure the router to use the new IOS image.Required file: Installing Cisco IOS SoftwareStep 1: Verify the IOS image currently installed on the routera. Access the router through the CLI modeb. Enter the privileged EXEC modec. Use the following command to verify current installed IOS:Router#show flashWhat is the file name of the IOS image? ___________________________________________________________How many bytes of memory are available? ________________________________________________________Step 2: Transfer the new IOS image to the Cisco routera. It is always good to ping the tftp server before attempting to copy an IOS image from a server.b. Enter the following command to test the connectivity between the router and the tftp server:Router#ping 192.168.1.10Note that the first ping may fail, if so repeat the ping. If the problem still persist, it will be necessary totroubleshoot the problem.c. On an actual network before beginning this upgrade you would copy the existing IOS file to the TFTPserver as a backup copy in case of problems.d. Enter the following command begin the process of transferring the new IOS image to the router:Router#copy tftp flashe. You will be prompted to enter the address or name of the remote host. Enter the IP address of theNetwork_Server (192.168.1.10) and press Enter.f. You will now be prompted to enter the name of the file you wish to transfer. Enter the following IOS filename:c1841-ipbasek9-mz.124-12.binAll contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 2
  • 47. CCNA DiscoveryDesigning and Supporting Computer Networksg. You will be prompted for the destination filename. The default filename will appear in brackets as shown:[c1841-ipbasek9-mz.124-12.bin]h. Press Enter to accept the default name.i. The image should now begin transferring from the server and you should see output that resembles thefollowing:Accessing tftp://192.168.1.10/c1841-ipbasek9-mz.124-12.bin....Loading c1841-ipbasek9-mz.124-12.bin from 192.168.1.10:!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!![OK - 16599160 bytes]16599160 bytes copied in 16.126 secs (230327 bytes/sec)Router#Step 3: Verify that the new IOS image is installeda. Use the following command to verify current IOS images that are installed:Router#show flasha. You should now see two IOS images in the outputStep 4: Specify an image boot order on the routera. Enter the global configuration modeb. To specify the boot order of the IOS images enter the following commands:Router(config)#boot system flash c1841-ipbasek9-mz.124-12.binRouter(config)#boot system flash c1841-ipbase-mz.123-14.T7.binc. These commands specify that the router will attempt to boot the new IOS image first. If for some reasonthe image is not located in flash, the router will then load the original IOS image.d. Exit to the privileged EXEC prompte. Enter the following command to verify the boot system commands:Router#show running-configStep 5: Verify that the proper image is loaded when the router boots upa. Save the current router configuration to NVRAMb. Restart the router by entering the following command:Router#reloadc. Allow the router to reboot completely, then enter the privileged EXEC moded. Use the following command to verify that the proper IOS image was loaded when the router booted up:Router#show versione. Check your answer by clicking the Check Results button.Reflectiona. Why would you want to have access to multiple IOS images on a router?____________________________________________________________________________________________________________________________________________________________________________b. What are two other locations that a router will look to obtain an IOS if it cannot locate one in flash?__________________________________________________________________________________________________________________________________________________________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 2
  • 48. CCNA DiscoveryDesigning and Supporting Computer Networks3.3.3 Installing Option Modules on a RouterObjective• Familiarize yourself with the 1841 router and the various interface modules available for installation.• Observe the changes in the number and designation of the various interfaces depending on where theyare installed in the router.Background / PreparationCisco Integrated Service Routers (ISR) are designed to fulfill different networking requirements. Each of thesemodular interfaces allows the installation of different modules. A network technician needs to become familiar withthe Cisco 1841 router and the difference modules that can be added to the device.Required file: Installing Option Modules on a Router.pkaStep 1: Examine the 1841 router and the default hardwarea. Place an 1841 router on the Logical Workspace.b. Execute the show run command and view default hardware settings.c. Note there are 2 FastEthernet interfaces and 1 VLAN interface. What are the interface designations?Step 2: Add additional modulesa. Power off the router.b. Add the HWIC-4ESW module to Slot 1.c. Power on the router.d. Execute the show run command and view the hardware settings. What are the interface designations?Step 3: Remove and add additional modulesa. Power off the router.b. Move the HWIC-4ESW module to Slot 0.c. Power on the router.d. Execute the show run command and view the hardware settings. What are the interface designations?Step 4: Examine the 2811 router and the default hardwarea. Execute the show run command and view the hardware settings. What are the interface designations?b. Note the interfaces and their designations.Step 5: Add additional modulesa. Power off the router.b. Add the HWIC-4ESW module to Slot 2.c. Power on the router.d. Execute the show run command and view the hardware settings. What are the interface designations?Step 6: Add additional modulesa. Power off the router.b. Add the HWIC-4ESW module to Slot 3.c. Power on the router.d. Execute the show run command and view the hardware settings. What are the interface designations?Reflectiona. The ability to add different modules allows for flexibility with networking devices. What type ofconnectivity will adding a WIC-2T module allow?_________________________________________________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 2
  • 49. CCNA DiscoveryDesigning and Supporting Computer Networks__________________________________________________________________________________________________________________________________b. What would happen to your existing configuration if you move a module from Slot 1 to Slot 2?___________________________________________________________________________________________________________________________________________________________________________________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 2
  • 50. CCNA DiscoveryDesigning and Supporting Computer Networks3.4.3 Placing Wireless Access PointsObjective• Use available tools to perform a wireless site survey.Background / PreparationA wireless network consists of one or more wireless access points to provide coverage for wireless clients inan office environment. The goal of the site survey is to find the optimal number and placement of accesspoints to provide coverage where it is needed and, for security reasons, to minimize coverage where it is notneeded. We will use the tools available in Packet Tracer to simulate a site survey of a one story officebuilding with two access points installed in the ceiling.The Linksys WRT300N wireless access routers are used to simulate access points installed in the ceiling, aPC with a Linksys WMP300N interface installed is used to simulate a laptop computer with wireless capability.Required file: Placing Wireless Access Points.pkaStep 1: Conduct the wireless site survey.a. In the logical view of the network observe which access point the Wireless PC is associated with.b. Access the Wireless PC and choose the PC Wireless button on the Desktop tab. Click the Connecttab in the Linksys window and observe the signal strength from both access points. Minimize theWireless PC window.c. Click the Physical Workplace tab in the upper left hand corner of the interface. Click on the HomeCity to enter it. The crosshatch ovals represent areas of wireless coverage. Note the areas outsideof the Corporate Office that have coverage.d. Click on the Corporate Office to enter it. Observe the areas of coverage inside the building and theplacement of the access points and the Wireless PC. In a real environment the wireless coverageareas would be invisible. Mark the location of the access points on the Building Diagram below. Markthe location if the Wireless PC and note the signal strength for each access point.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 3
  • 51. CCNA DiscoveryDesigning and Supporting Computer Networkse. Move the Wireless PC to different locations around the office. For each location, access the WirelessPC window and click the Refresh button. Note on the Building Diagram, at each location, the accesspoints (if any) and their signal strength. Minimize the Wireless PC window.f. Continue until the entire building is surveyed.Step 2: Relocate the access points to their optimal location.a. Move the access points to assure that all areas inside the building have wireless coverage and thatcoverage outside of the building is minimized.b. Verify your placement by spot checking key locations within the building using the techniques fromStep 1 and adjust the placement as needed.Building Diagram:Step 3: Reflectiona. If the coverage shown in the Physical view represents the maximum power output of the accesspoint, could the building be covered by a single access point?____________________________________________________________________________________________________________________________________________________________________________________________________________________________________b. On real equipment, what else could be done to minimize coverage outside of the building?____________________________________________________________________________________________________________________________________________________________________________________________________________________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 3
  • 52. CCNA DiscoveryDesigning and Supporting Computer Networksc. What types of problems would you encounter when you have overlapping coverage of access pointsusing the same channel?____________________________________________________________________________________________________________________________________________________________________________________________________________________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 3 of 3
  • 53. CCNA DiscoveryDesigning and Supporting Computer Networks5.2.2 Connecting Access and Distribution Layer SwitchesObjective• Design and diagram the Distribution Layer topology to support given network business and technicalrequirements.640-802 CCNA Exam ObjectivesThis activity contains skills that relate to the following CCNA exam objectives:• Select the components required to meet a network specification• Select the appropriate media, cables, ports, and connectors to connect switches to other networkdevices and hosts• Describe enhanced switching technologies (including: VTP, RSTP, VLAN, PVSTP, 802.1q)All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 3
  • 54. CCNA DiscoveryDesigning and Supporting Computer NetworksExpected Results and Success Criteriaa. Before beginning this activity, read through the tasks you are expected to perform. What do youexpect the result of performing these tasks will be?____________________________________________________________________________________________________________________________________________________________________________________________________________________________________b. Why do you think that network administrators use redundant links in their network?____________________________________________________________________________________________________________________________________________________________________________________________________________________________________c. Why is Spanning Tree Protocol necessary where there are redundant links?____________________________________________________________________________________________________________________________________________________________________________________________________________________________________Background / PreparationEquipment installed at the Network Distribution Layer usually consists of multi-layer, modular switches thatconnect to Layer 2 Access Layer switches through redundant links. These Distribution Layer switches thenconnect to Core Layer devices, also through redundant links. Spanning Tree Protocol allows these redundantconnections without the problems associated with switching loops.Packet Tracer only supports devices typically found in the CCNA academy lab bundle, not the type ofswitches typically used at the Network Distribution Layer. We will use regular Layer 2 switches to representthese switches as we connect the redundant links between the Access and Distribution Layer switches andobserve the operation of Spanning Tree Protocol.Required file: Connecting Access and Distribution Layer Switches.pkaStep 1: Connect the Access Layer switches to the Distribution Layer switches.a. Using the proper cables, connect the first interface on switch Access1 to the first interface on switchDistribution1 and the second interface on switch Access1 to the first interface on switchDistribution2.b. Using the proper cables, connect the first interface on switch Access2 to the second interface onswitch Distribution1 and the second interface on switch Access2 to the second interface on switchDistribution2.c. Using the proper cables, connect the first interface on switch Access3 to the third interface on switchDistribution1 and the second interface on switch Access3 to the third interface on switchDistribution2.d. Using the proper cables, connect the first interface on switch Access4 to the fourth interface onswitch Distribution1 and the second interface on switch Access4 to the fourth interface on switchDistribution2.e. Check your configuration using the Check Results button. Correct any errors in the configuration.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 3
  • 55. CCNA DiscoveryDesigning and Supporting Computer NetworksStep 2: Observe the operation of Spanning Tree Protocol.a. Wait a few minutes for Spanning Tree Protocol to open up forwarding ports that are indicated by thegreen link lights. The ports whose link lights remain orange are blocked by Spanning Tree Protocol.b. Observe which ports are blocked. Enter Simulation mode to verify that packets from any switch canbe sent to every other switch in the network. Be sure that all events are visible in the Event ListFilters, then click Auto Capture / Play.Step 3: Reflectiona. Why do you think Spanning Tree Protocol blocked the links that it did?____________________________________________________________________________________________________________________________________________________________________________________________________________________________________b. Would Spanning Tree Protocol be necessary if we used routers at the Network Distribution Layer?Why or why not?____________________________________________________________________________________________________________________________________________________________________________________________________________________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 3 of 3
  • 56. CCNA DiscoveryDesigning and Supporting Computer Networks5.3.2 Examining WAN ConnectionsObjectiveThe show commands are very powerful commands for troubleshooting and monitoring networks. They give astatic image of the network at a given time. The use of a variety of show commands will give a clear picture ofhow the networking is communicating and transferring data.Background / PreparationThe physical topology of the network has been designed using Frame Relay. To test the network connectivity,use a variety of show commands.Required file: Examining WAN Connections.pkaStep 1: Examine the configuration of Branch1 and Branch2.a. Click on Branch1 and use various show commands to view the connectivity to the network.b. Use the show running-configuration command to view the router configuration.c. Use the show ip interface brief command to view the status of the interfaces.d. Use the various show frame-relay map, show frame-relay pvc, and show frame-relay lmi commandsto see the status of the Frame-relay circuit.e. Click on Branch 2 and use various show commands to view the connectivity to the network.f. Use the show running-configuration command to view the router configuration.g. Use the show ip interface brief command to view the status of the interfaces.h. Use the various show frame-relay map, show frame-relay pvc, and show frame-relay lmi commandsto see the status of the Frame-relay circuit.Step 2: Examine the configuration of Main.a. Click on Main and use a variety of show commands to view the connectivity to the network.b. Use the show running-configuration command to view the router configuration.c. Use the show ip interface brief command to view the status of the interfaces.d. To view the status of the frame-relay configurations use the show frame-relay lmi, show frame-relaymap, and show frame-relay pvc commands.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 2
  • 57. CCNA DiscoveryDesigning and Supporting Computer NetworksReflectiona. In what situations would it be beneficial to use the various show commands?________________________________________________________________________________________________________________________________________________________________b. What beneficial information can be obtained from the various show commands?________________________________________________________________________________________________________________________________________________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 2
  • 58. CCNA DiscoveryDesigning and Supporting Computer Networks5.3.4 Observing Static and Dynamic RoutingObjectiveObserve the network behavior using static and default routing only and compare it to the behavior of dynamicrouting.Background / PreparationIn this exercise, you will observe what the adaptability of dynamic routing compared to static and default routing.The Ticket Sales Office network is currently configured using static and default routing.Required file: Observing Static and Dynamic Routing.pkaStep 1: Test Connectivity Using Static and Default Routing.a. Open a Command Prompt on PC0.b. Trace (tracert) a connection to the Edge1 FastEthernet 0/0 address. This should be successful.Step 2: Bring down Frame Relay Network and Observe Routing.a. On the BR2 router, shutdown the link to the Frame Relay network.b. Perform a trace from PC0 again to the Edge1 FastEthernet 0/0 address. What happens this time?__________________________________________________________________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 2
  • 59. CCNA DiscoveryDesigning and Supporting Computer NetworksStep 3: Configure Dynamic Routing and Observe Routinga. Configure EIGRP (AS 10) on the BR2 and ISP2 routers. Be sure to include all directly connectednetworks and turn off auto-summary.b. Do a third trace from PC0 to the Edge1 FastEthernet 0/0 interface. (It should be successful again.)c. Did the path change? If so, how? ___________________________________________________Reflection1. What are the advantages of using dynamic routing? Static and default routing?________________________________________________________________________________________________________________________________________________________________2. The static routes in this lab were set with an administrative distance of 130. What would havehappened if they were set at 30? At 230?________________________________________________________________________________.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 2
  • 60. CCNA DiscoveryDesigning and Supporting Computer Networks5.5.3 Implementing Access Control ListsObjective• Test basic connectivity• Create and apply an Access Control List (ACL)• Verify the application of the ACLBackground / PreparationAs part of an IT staff, you have been asked to work with the network designer to define the firewall rule set tobe implemented in the new network design. The firewall rule set dictates the exact types of network activitypermitted. As the designer of a network, you are responsible for the first line of security on the network. Thesecurity policies will dictate which users and groups are permitted access to what resources, and what type ofaccess is denied. When designing firewall rule sets and access control lists, the general policy is to deny alltraffic that is either not specifically authorized or is not in response to a permitted inquiry. Each firewall rule setmay require more than one ACL statement and may require both inbound and outbound placement. In thisscenario, you will be creating a sampling of ACLs that might be applied in a firewall rule set.Required file: Implementing Access Control Lists.pkaStep 1: Discover and document the first device.a. Access the Admin PC and issue the ipconfig command from the command prompt to discover thedefault gateway.b. Telnet to the IP address of the gateway device and enter privileged exec mode using the passwordsgiven above.c. Issue IOS commands such as show running-config, show ip route, show interfaces, show ipinterface brief, show version and other commands to learn about the device.d. Issue IOS commands such as show cdp neighbors and show cdp neighbors detail to discoverinformation about connected devices. It may take a few minutes for the network to converge. If you donot see any neighboring devices initially, repeat the command until you do.e. Document the information you gather in the appropriate table below.f. Close the Telnet session by issuing the exit command.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 2
  • 61. CCNA DiscoveryDesigning and Supporting Computer NetworksStep 2: Discover the remaining devices.a. Packet Tracer works best when you successfully ping a device before attempting to Telnet to it.Issue the ping command to the IP address of one of the devices you discovered in Step 1. Repeatthe ping command until it succeeds.b. Telnet to the IP address of the device and repeat the process in Step 1 to document the device.c. To not overuse the resources of Packet Tracer, do not Telnet from device to device. Always exit tothe command prompt before accessing the next device.d. Repeat the process until all devices in the network are discovered and documented.e. As you work, sketch out a diagram of the network devices and their interconnections.Step 3: Examine the Access Control Lists that are configured on the routersa. Click on the CLI tab on Edge1 to examine the ACLs that have been configuredb. Use the following commands to view the ACLs that have been configured on the routers:• show running-config• show access-lists 100Step 4: Determine the appropriate interface to apply the ACLsa. After examining the ACLs determine where the ACLs should be appliedb. The ACL must be applied to an interface before it will affect the network trafficc. Remember that only one ACL per port, per protocol, per direction is allowed.d. Using the CLI mode, apply the ACL to the appropriate interface on the Edge1 routerStep 5: Examine the affects of the ACLa. Verify that the appropriate traffic is permitted or deniedb. The Inside PC should be permitted to:• Ping all devices (use the command prompt)• Make HTTP request from the Web Server at 192.168.2.10 (use the Web browser on the InsidePC)• Telnet to the Internet router at 172.16.1.1 (use the command prompt) – password = cisco. Usethe command exit to return to PC prompt.• Use FTP to reach other devices (use Simulation mode and a Complex PDU to simulate the FTPtraffic – for the Complex PDU set the Select Application: FTP, Destination IP Address:192.168.1.10, Source Port: 50000, One Shot Time: 1)c. The Outside PC should be denied the following:• Ping to Edge1, Core, Inside PC, and Data Center (use the command prompt)• Make HTTP request from the Data Center 10.0.10.20 (use the Web browser on the Inside PC).However, it should still be able to reach the Web Server at 192.168.2.10.• Use FTP to reach other devices (use Simulation mode and a Complex PDU to simulate the FTPtraffic – for the Complex PDU set the Select Application: FTP, Destination IP Address:10.0.10.10, Source Port: 50000, One Shot Time: 1)d. All other network traffic should be denied from reaching the 10.0.10.0 networkReflection1. With the current ACL applied, would you be able to Telnet from the Outside PC to the Edge1 router at172.16.1.2? Why?______________________________________________________________________________________________________________________________________________________________________________2. Why is it always necessary to have at least one Permit statement in an ACL?______________________________________________________________________________________________________________________________________________________________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 2
  • 62. CCNA DiscoveryDesigning and Supporting Computer Networks6.1.1 Designing and Addressing a TopologyAddressing TableDevice Interface IP Address Subnet Mask Default GatewayS0/0/0 N/AS0/0/1 N/AR1S0/1/0 N/AFa0/0 N/AR2S0/0/0 N/AFa0/0 N/AR3S0/0/0 N/AFa0/0 N/AR4S0/0/0 N/AR2 Host-ANICR2 Host-BNICR2Printer-ANICR2 Host-CNICR2 Host-DNICR3 Host-ANICR3 Host-BNICR3Printer-BNICR3 Host-CNICR3 Host-DNICR4 Host-ANICR4 Host-BNICR4Printer-CNICR4 Host-CNICR4 Host-DNICAll contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 5
  • 63. CCNA DiscoveryDesigning and Supporting Computer NetworksLearning Objectives• Determine the number of subnets needed.• Determine the number of hosts needed for each LAN.• Design a hierarchical addressing scheme.• Assign addresses and subnet masks to device interfaces and hosts.• Examine the use of the available network address space.IntroductionIn this lab, you have been given the IP addresses included in 192.168.8.0/22. Use this range of IP addresses tosubnet and provide the IP addressing for the network. The network has the following addressing requirements:• The R2 LAN will require 120 host IP addresses.• The R3 LAN will require 120 host IP addresses.• The R4 LAN will require 120 host IP addresses.• The WAN links between each of the routers will require an IP address for each end of the link.Required file: Designing and Addressing a Topology.pkaTask 1: Examine the network requirements.Examine the network requirements and answer the questions below. Keep in mind that IP addresses will beneeded for each LAN interface on each router.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 LANs?4. How many IP addresses are needed for all of the connections between routers?5. What is the total number of IP addresses that are needed?At the end of this task your completion rate should be 0%.Task 2: Design a hierarchical IP addressing scheme.Step 1. Subnet 192.168.8.0/22.Calculate the subnetworks based on the maximum number of IP addresses needed in the largest subnet. Keepthe number of hosts per subnet as close as possible to the maximum number of hosts required.1. What is the subnet mask for each subnetwork?2. How many usable IP addresses are there for each subnetwork?All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 5
  • 64. CCNA DiscoveryDesigning and Supporting Computer NetworksFill in the following chart with the subnet information.Subnet Number Subnet IP First Usable Last Usable Broadcast Address012345Step 2. Assign the subnets to the network.When assigning the subnets, keep in mind that routing will need to occur to allow information to be sentthroughout the network.The subnets will be assigned to the networks to allow for route summarization on each of the routers.1. Assign subnet 0 to the R1 to R2 WAN.2. Assign subnet 1 to the R2 LAN.3. Assign subnet 2 to the R1 to R3 WAN.4. Assign subnet 3 to the R3 LAN.5. Assign subnet 4 to the R1 to R4 WAN.6. Assign subnet 5 to the R4 LAN.At the end of this task your completion rate should be 0%.Task 3: Assign and configure IP Addresses on the network devices.Assign the appropriate addresses to the device interfaces. Document the addresses to be used in the AddressingTable provided. Configure network devices with the assigned IP address, subnet mask and gateway address,when applicable.Step 1. Assign and configure addresses on the R1 Router.1. Assign and configure the first valid host address in the R1 to R2 WAN subnet on the s0/0/0 interface.2. Assign and configure the first valid host address in the R1 to R3 WAN subnet on the s0/0/1 interface.3. Assign and configure the first valid host address in the R1 to R4 WAN subnet on the s0/1/0 interface.Step 2. Assign and configure addresses on the R2 Router.1. Assign and configure the second valid host address in the R1 to R2 WAN subnet on the s0/0/0 interface.2. Assign and configure the first valid host address in the R2 LAN subnet on the LAN interface.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 3 of 5
  • 65. CCNA DiscoveryDesigning and Supporting Computer NetworksStep 3. Assign and configure addresses on the R3 Router.1. Assign and configure the second valid host address in the R1 to R3 WAN subnet on the s0/0/0 interface.2. Assign and configure the first valid host address in the R3 LAN subnet on the LAN interface.Step 4. Assign and configure addresses on the R4 Router.1. Assign and configure the second valid host address in the R1 to R4 WAN subnet on the s0/0/0 interface.2. Assign and configure the first valid host address in the R4 LAN subnet on the LAN interface.Step 5. Assign and configure addresses on the host devices (PCs and Printers) of R2.1. Assign and configure the second valid host address in the R2 LAN subnet on R2 Host-A.2. Assign and configure the third valid host address in the R2 LAN subnet onR2 Host-B.3. Assign and configure the fourth valid host address in the R2 LAN subnet on Printer-A.4. Assign and configure the fifth valid host address in the R2 LAN subnet on R2 Host-C.5. Assign and configure the sixth valid host address in the R2 LAN subnet on R2 Host-D.Step 6. Assign and configure addresses on the host devices (PCs and Printers) of R3.1. Assign and configure the second valid host address in the R3 LAN subnet on R3 Host-A.2. Assign and configure the third valid host address in the R3 LAN subnet on R3 Host-B.3. Assign and configure the fourth valid host address in the R3 LAN subnet on Printer-B.4. Assign and configure the fifth valid host address in the R3 LAN subnet on R3 Host-C.5. Assign and configure the sixth valid host address in the R3 LAN subnet on R3 Host-D.Step 7. Assign and configure addresses on the host devices (PCs and Printers) of R4.1. Assign and configure the second valid host address in the R4 LAN subnet on R4 Host-A.2. Assign and configure the third valid host address in the R4 LAN subnet on R4 Host-B.3. Assign and configure the fourth valid host address in the R4 LAN subnet on Printer-C.4. Assign and configure the fifth valid host address in the R4 LAN subnet on R4 Host-C.5. Assign and configure the sixth valid host address in the R4 LAN subnet on R4 Host-D.At the end of this task your completion rate should be 91%.Task 4: Verify connectivity.Check to see that all devices on directly connected networks can ping each other.Task 5: Configure EIGRP routing protocol on each router.Step 1. Configure EIGRP on router R1.1. Configure EIGRP using autonomous system number 10.2. Configure EIGRP to route for all three directly connected networks.Step 2. Configure EIGRP on router R2.1. Configure EIGRP using autonomous system number 10.2. Configure EIGRP to route for both directly connected networks.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 4 of 5
  • 66. CCNA DiscoveryDesigning and Supporting Computer NetworksStep 3. Configure EIGRP on router R3.1. Configure EIGRP using autonomous system number 10.2. Configure EIGRP to route for both directly connected networks.Step 4. Configure EIGRP on router R4.1. Configure EIGRP using autonomous system number 10.2. Configure EIGRP to route for both directly connected networks.Task 6: Verify EIGRP routing.Step 1. Verify EIGRP routing on router R1.1. Check the routing table of router R1.2. How many routes are in the routing table?3. Are any of the routes summarized? If so, which ones are summarized?Step 2. Verify EIGRP routing on R2, R3, and R4.1. Check the routing tables of R2, R3, and R4.2. How many routes are in each routing table?3. Are any of the routes summarized? If so, which ones are summarized?Task 7: Reflection1. How many IP addresses in 192.168.8.0/22 are wasted in this design?2. What change(s) could be made to this IP addressing scheme to be more efficient?3. Would route summarization have occurred in a non-hierarchical design?At the end of this task your completion rate should be 100%.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 5 of 5
  • 67. CCNA DiscoveryDesigning and Supporting Computer Networks6.1.2 Resolving Discontiguous Network ProblemsAddressing TableDevice Interface IP Address Subnet Mask Default GatewayS0/0/0 209.165.202.245 255.255.255.252 N/AS0/0/1 209.165.202.249 255.255.255.252 N/AR1S0/1/0 2092.168.202.253 255.255.255.252 N/AFa0/0 192.168.40.33 255.255.255.224 N/AR2S0/0/0 209.165.202.249 255.255.255.252 N/AFa0/0 192.168.40.65 255.255.255.224 N/AR3S0/0/0 209.165.202.250 255.255.255.252 N/AFa0/0 192.168.40.97 255.255.255.224 N/AR4S0/0/0 209.165.202.254 255.255.255.252 N/AR2Host-ANIC 192.168.40.34 255.255.255.224 192.168.40.33R2Host-BNIC 192.168.40.35 255.255.255.224 192.168.40.33Printer0 NIC 192.168.40.36 255.255.255.224 192.168.40.33R2Host-CNIC 192.168.40.37 255.255.255.224 192.168.40.33R2Host-DNIC 192.168.40.38 255.255.255.224 192.168.40.33R3Host-ANIC 192.168.40.66 255.255.255.224 192.168.40.65R3Host-BNIC 192.168.40.67 255.255.255.224 192.168.40.65Printer1 NIC 192.168.40.68 255.255.255.224 192.168.40.65R3Host-CNIC 192.168.40.69 255.255.255.224 192.168.40.65R3Host-DNIC 192.168.40.70 255.255.255.224 192.168.40.65R4Host-ANIC 192.168.40.98 255.255.255.224 192.168.40.97R4Host-BNIC 192.168.40.99 255.255.255.224 192.168.40.97Printer2 NIC 192.168.40.100 255.255.255.224 192.168.40.97R4Host-CNIC 192.168.40.101 255.255.255.224 192.168.40.97R4Host-DNIC 192.168.40.102 255.255.255.224 192.168.40.97Objectives• Verify RIPv2 is auto-summarizing the discontiguous networks.• Describe the behavior of traffic directed to and from the discontiguous networks.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 3
  • 68. CCNA DiscoveryDesigning and Supporting Computer Networks• Disable auto-summarization in RIPv2.• Test and verify full connectivityBackground / PreparationIn this lab activity, you will be given a preconfigured topology with discontiguous subnetworks. The routers areconfigured with RIPv2 and auto-summarization is running by default. The discontiguous networks are each ofthe three LANs separated by the WAN links. The default auto-summarization in RIPv2 is preventing trafficfrom routing properly throughout this topology.This activity has multiple windows of instructions. Select the ">" button to view the next portion of instructions.Required file: Resolving Discontiguous Network Problems.pkaTask 1: Examine the network requirements.The addressing for the network has the following requirements:• The link between R1 and R2 is currently configured with the 209.165.202.244/30 network.• The link between R1 and R3 is currently configured with the 209.165.202.248/30 network.• The link between R1 and R4 is currently configured with the 209.165.202.252/30 network.• The R2 LAN and its devices are already configured with the 192.168.40.32/27 network.• The R3 LAN and its devices are already configured with the 192.168.40.64/27 network.• The R4 LAN and its devices are already configured with the 192.168.40.96/27 network.Task 2: Verify connectivity to next-hop device.You should not have connectivity between end devices on different subnets yet. However, you can testconnectivity between two routers and between an end device and its default gateway.Step 1. Verify WAN connectivity.1. Verify that R2 can ping across the WAN link to R1.2. Verify that R3 can ping across the WAN link to R1.3. Verify that R4 can ping across the WAN link to R1.Step 2. Verify that Host-A, Host-B, Host-C, Host-D, and Printer can ping their respective defaultgateways. If the pings are unsuccessful, check device configurations.Step 3. Verify end device connectivity.1. Can router R1 ping the Fa0/0 interface on R2? Yes or No?2. Can router R1 ping the Fa0/0 interface on R3? Yes or No?3. Can router R1 ping the Fa0/0 interface on R4? Yes or No?4. Can router R1 ping R3 Host-A? Yes or No?5. Can router R1 ping R4 Host-A? Yes or No?6. Some of the pings should be successful. What is the pattern of successful pings (!) and failed pings (.)?7. Why is this so?At the end of this task your completion rate should be 0%.Task 3: Verify RIP routesStep 1. View the routing table of router R1.1. List the routes that are included in the R1 routing table.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 3
  • 69. CCNA DiscoveryDesigning and Supporting Computer Networks2. Assume R1 is sending a packet to 192.168.40.34. What out-going interfaces on R1 are identified as apath to any IP address in the range of 192.168.40.0/24?3. Which of these out-going interfaces can be used to successfully send a packet to 192.168.40.34?Step 2. View the routing table of router R2.1. List the routes that are included in the R2 routing table.2. Assume R2 is sending a packet to 192.168.40.98. What out-going interface on R2 would be used to senda packet to 192.168.40.98?3. Will router R2 be able to successfully route traffic destined for 192.168.40.98?Step 3. View the routing table of router R3.1. List the routes that are included in the R3 routing table.2. Assume R3 is sending a packet to 192.168.40.98. What out-going interface on R3 would be used to senda packet to 192.168.40.98?3. Will router R3 be able to successfully route traffic destined for 192.168.40.98?Step 4. View the routing table of router R4.1. List the routes that are included in the R4 routing table.2. Assume R4 is sending a packet to 192.168.40.34. What out-going interface on R4 would be used to senda packet to 192.168.40.34?3. Will router R4 be able to successfully route traffic destined for 192.168.40.34?At the end of this task your completion rate should be 0%.Task 4: Resolve discontiguous network problem.Step 1. On each router, disable automatic summarization in RIPv2.Step 2. View the routing table of each router.1. What routes have been added to the R1 routing table?2. What routes have been added to the R2 routing table?3. What routes have been added to the R3 routing table?4. What routes have been added to the R4 routing table?Task 5: Verify connectivityAnswer the following questions to verify that the network is operating as expected:1. From router R1, is it possible to ping R2 Host-A?2. From router R1, is it possible to ping R3 Host-A?3. From router R1, is it possible to ping R4 Host-A?The answers to the above questions should be yes. If any of the above pings failed on the initial try, repeat inorder to help build the routing table.At the end of this task your completion rate should be 100%.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 3 of 3
  • 70. CCNA DiscoveryDesigning and Supporting Computer Networks6.1.3 Applying VLSM AddressingAddressing TableDevice Interface IP Address Subnet Mask Default GatewayFa0/0 n/aFa0/1 n/aS0/0/0 n/aR1S0/0/1 n/aFa0/0 n/aFa0/1 n/aS0/0/0 n/aR2S0/0/1 n/aFa0/0 n/aFa0/1 n/aS0/0/0 n/aR3S0/0/1 n/aObjectives• Determine the number of subnets needed.• Determine the number of hosts needed for each subnet.• Design an appropriate addressing scheme using VLSM.• Assign addresses and subnet mask pairs to device interfaces.• Examine the use of the available network address space.Background / PreparationIn this activity, you have been given the network address 192.168.1.0/24 to subnet and provide the IP addressingfor the network shown in the Topology Diagram. VLSM will be used so that the addressing requirements can bemet using the 192.168.1.0/24 network. The network has the following addressing requirements:• The R1 LAN1 will require 50 host IP addresses.• The R1 LAN2 will require 50 host IP addresses.• The R2 LAN1 will require 20 host IP addresses.• The R2 LAN2 will require 20 host IP addresses• The R3 LAN1 will require 12 host IP addresses.• The R3 LAN2 will require 12 host IP addresses.• The link from R1 to R2 will require an IP address for each end of the link.• The link from R1 to R3 will require an IP address for each end of the link.• The link from R2 to R3 will require an IP address for each end of the link.This activity has multiple windows of instructions. Select the ">" button to view the next portion of instructions.Required file: Applying VLSM Addressing.pkaAll contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 4
  • 71. CCNA DiscoveryDesigning and Supporting Computer NetworksTask 1: Examine the network requirements.Examine the network requirements and answer the questions below. Keep in mind that IP addresses will beneeded for each LAN interface on each router.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 R1 LANs?4. How many IP addresses are needed for each of the R2 LANs?5. How many IP addresses are needed for each of the R3 LANs?6. How many IP addresses are needed for each of the WAN links between routers?7. What is the total number of IP addresses that are needed?8. What is the total number of IP addresses that are available in the 192.168.1.0/24 network?9. Can the network addressing requirements be met using the 192.168.1.0/24 network?At the end of this task your completion rate should be 0%.Task 2: Design an IP Addressing SchemeStep 1. Determine the subnet information for the largest network segment or segments.In this case, the two R1 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 R1 LANs.Start at the beginning of the 192.168.1.0/24 network.1. Assign the first available subnet to R1 LAN1.2. Fill in the chart below with the appropriate information. R1 LAN1 Subnet.NetworkAddressDecimalSubnet MaskSubnet MaskBitsFirst Usable IPAddressLast Usable IPAddressBroadcastAddress3. Assign the next available subnet to R1 LAN2.4. Fill in the chart below with the appropriate information. R1 LAN2 Subnet.NetworkAddressDecimalSubnet MaskSubnet MaskBitsFirst Usable IPAddressLast Usable IPAddressBroadcastAddressStep 3. Determine the subnet information for the next largest network segment or segments.In this case, the two R2 LANs are the next 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 4. Assign subnet to R2 LANs. Start with the IP address following the R1 LAN subnets.1. Assign the next available subnet to R2 LAN1.2. Fill in the chart below with the appropriate information. R2 LAN1 Subnet.NetworkAddressDecimalSubnet MaskSubnet MaskBitsFirst Usable IPAddressLast Usable IPAddressBroadcastAddress3. Assign the next available subnet to R2 LAN2.4. Fill in the chart below with the appropriate information. R2 LAN2 Subnet.NetworkAddressDecimalSubnet MaskSubnet MaskBitsFirst Usable IPAddressLast Usable IPAddressBroadcastAddressAll contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 4
  • 72. CCNA DiscoveryDesigning and Supporting Computer NetworksStep 5. Determine the subnet information for the next largest network segment or segments.In this case, the two R3 LANs are the next 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 6. Assign subnets to R3 LANs.Start with the IP address following the R2 LAN subnets.1. Assign the next available subnet to the R3 LAN1.2. Fill in the chart below with the appropriate information. R3 LAN1 Subnet.NetworkAddressDecimalSubnet MaskSubnet MaskBitsFirst Usable IPAddressLast Usable IPAddressBroadcastAddress3. Assign the next available subnet to R3 LAN2.4. Fill in the chart below with the appropriate information. R3 LAN2 Subnet.NetworkAddressDecimalSubnet MaskSubnet MaskBitsFirst Usable IPAddressLast Usable IPAddressBroadcastAddressStep 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 R3 LAN subnets.1. Assign the next available subnet to the link between the R1 and R2 routers.2. Fill in the chart below with the appropriate information. Link between R1 and R2 Subnet.NetworkAddressDecimalSubnet MaskSubnet MaskBitsFirst Usable IPAddressLast Usable IPAddressBroadcastAddress3. Assign the next available subnet to the link between the R1 and R3 routers.4. Fill in the chart below with the appropriate information. Link between R1 and R3 Subnet.NetworkAddressDecimalSubnet MaskSubnet MaskBitsFirst Usable IPAddressLast Usable IPAddressBroadcastAddress5. Assign the next available subnet to the link between the R2 and R3 routers.6. Fill in the chart below with the appropriate information. Link between R2 and R3 Subnet.NetworkAddressDecimalSubnet MaskSubnet MaskBitsFirst Usable IPAddressLast Usable IPAddressBroadcastAddressAt the end of this task your completion rate should be 0%.Task 3: Assign IP Addresses to the Network Devices Assign the appropriate addressesto the device interfaces.Step 1. Assign addresses to the R1 router.1. Assign the first valid host address in the R1 LAN 1 subnet to the Fa0/0 LAN interface.2. Assign the first valid host address in the R1 LAN 2 subnet to the Fa0/1 LAN interface.3. Assign the first valid host address in the link between R1 and R2 subnet to the S0/0/0 interface.4. Assign the first valid host address in the link between R1 and R3 subnet to the S0/0/1 interface.Step 2. Assign addresses to the R2 router.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 3 of 4
  • 73. CCNA DiscoveryDesigning and Supporting Computer Networks1. Assign the first valid host address in the R2 LAN1 subnet to the Fa0/0 LAN interface.2. Assign the first valid host address in the R2 LAN2 subnet to the Fa0/1 LAN interface.3. Assign the last valid host address on the link between R2 and R1 subnet to the S0/0/0 interface.4. Assign the first valid host address on the link between R2 and R3 subnet to the S0/0/1 interface.Step 3. Assign addresses to the R3 router.1. Assign the first valid host address in the R3 LAN1 subnet to the Fa0/0 LAN interface.2. Assign the first valid host address in the R3 LAN 2 subnet to the Fa0/1 LAN interface.3. Assign the last valid host address on the link between R1 and R3 subnet to the S0/0/1 interface.4. Assign the last valid host address on the link between R2 and R3 subnet to the S0/0/0 interface.At the end of this task your completion rate should be 100%.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 4 of 4
  • 74. CCNA DiscoveryDesigning and Supporting Computer Networks6.2.3 Configuring a Multirouter EIGRP NetworkAddressing TableDevice Interface IP Address Subnet Mask Default GatewayFa0/0 N/AFa0/1 N/AS0/0/0 209.165.202.1 255.255.255.252 N/AR1S0/0/1 209.165.202.5 255.255.255.252 N/AFa0/0 N/AFa0/1 N/AS0/0/0 209.165.202.9 255.255.255.252 N/AR2S0/0/1 209.165.202.2 255.255.255.252 N/AFa0/0 N/AFa0/1 N/AS0/0/0 209.165.202.6 255.255.255.252 N/AR3S0/0/1 209.165.202.10 255.255.255.252 N/ALearning Objectives• Determine the number of subnets needed.• Determine the number of hosts needed for each subnet.• Design an appropriate addressing scheme using VLSM.• Assign addresses and subnet mask pairs to device interfaces.• Configure EIGRP on the network.IntroductionIn this activity, you have been given the network address 172.16.0.0/16 to subnet and providethe IP addressing for the network shown in the Topology Diagram. VLSM will be used so thatthe addressing requirements can be met using the 172.16.0.0/16 network. The network has thefollowing addressing requirements:• The R1 LAN 1 will require 8,000 host IP addresses.• The R1 LAN 2 will require 4,000 host IP addresses.• The R2 LAN 1 will require 2,000 host IP addresses.• The R2 LAN 2 will require 1,000 host IP addresses.• The R3 LAN 1 will require 500 host IP addresses.• The R3 LAN 2 will require 200 host IP addresses.• The serial link from R1 to R2 has been preconfigured with the 209.165.202.0/30network.• The serial link from R1 to R3 has been preconfigured with the 209.165.202.4/30network.• The serial link from R2 to R3 has been preconfigured with the 209.165.202.8/30network.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 6
  • 75. CCNA DiscoveryDesigning and Supporting Computer NetworksRequired file: Configuring a Multirouter EIGRP Network.pkaTask 1: Examine the Network Requirements.Examine the network requirements and answer the questions below. Keep in mind that IPaddresses will be needed for each LAN interface on each router.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 the R1 LAN 1?4. How many IP addresses are needed for the R1 LAN 2?5. How many IP addresses are needed for the R2 LAN 1?6. How many IP addresses are needed for the R2 LAN 2?7. How many IP addresses are needed for the R3 LAN 1?8. How many IP addresses are needed for the R3 LAN 2?9. What is the total number of IP addresses that are needed?10. What is the total number of IP addresses that are available in the 172.16.0.0/16network?11. Can the network addressing requirements be met using the 172.16.0.0/16 network?At the end of this task your completion rate should be 0%.Task 2: Design an IP Addressing SchemeStep 1. Determine the subnet information for the largest network segment or segments.In this case, the R1 LAN 1 is the largest subnet.1. How many IP addresses are needed for the R1 LAN 1?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 the subnet to the R1 LAN 1.Start at the beginning of the 172.16.0.0/16 network.1. Assign the first available subnet to the R1 LAN 1.2. Fill in the chart below with the appropriate information.R1 LAN 1 SubnetNetworkAddressDecimalSubnet MaskSubnetMask BitsFirst UsableAddressLast UsableAddressBroadcastAddress192.168.Step 3. Determine the subnet information for the next largest network segment orsegments.In this case, the R1 LAN 2 is the next largest subnet.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 6
  • 76. CCNA DiscoveryDesigning and Supporting Computer Networks1. How many IP addresses are needed for the R1 LAN 2?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 4. Assign the subnet to R1 LAN 2.Start with the IP address following the R1 LAN 1 subnet.1. Assign the next subnet to R1 LAN 2.2. Fill in the chart below with the appropriate information.R1 LAN 2 SubnetNetworkAddressDecimalSubnet MaskSubnetMask BitsFirst UsableAddressLast UsableAddressBroadcastAddressStep 5. Determine the subnet information for the next largest network segment orsegments.In this case, the R2 LAN 1 is the next largest subnet.1. How many IP addresses are needed for the R2 LAN 1?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 6. Assign the subnet to R2 LAN 1.Start with the IP address following the R1 LAN 2 subnet.1. Assign the next subnet to R2 LAN 1.2. Fill in the chart below with the appropriate information.R2 LAN 1 SubnetNetworkAddressDecimalSubnet MaskSubnetMask BitsFirst UsableAddressLast UsableAddressBroadcastAddressAll contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 3 of 6
  • 77. CCNA DiscoveryDesigning and Supporting Computer NetworksStep 7. Determine the subnet information for the next largest network segment orsegments.In this case, the R2 LAN 2 is the next largest subnet.1. How many IP addresses are needed for the R2 LAN 2?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 the subnet to R2 LAN 2.Start with the IP address following the R2 LAN 1 subnet.1. Assign the next subnet to R2 LAN 2.2. Fill in the chart below with the appropriate information.R2 LAN 2 SubnetNetworkAddressDecimalSubnet MaskSubnetMask BitsFirst UsableAddressLast UsableAddressBroadcastAddressStep 9. Determine the subnet information for the next largest network segment orsegments.In this case, the R3 LAN 1 is the next largest subnet.1. How many IP addresses are needed for the R3 LAN 1?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 10. Assign the subnet to R3 LAN 1.Start with the IP address following the R2 LAN 2 subnet.1. Assign the next subnet to R3 LAN 1.2. Fill in the chart below with the appropriate information.R3 LAN 1 SubnetNetworkAddressDecimalSubnet MaskSubnetMask BitsFirst UsableAddressLast UsableAddressBroadcastAddressAll contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 4 of 6
  • 78. CCNA DiscoveryDesigning and Supporting Computer NetworksStep 11. Determine the subnet information for the next largest network segment orsegments.In this case, the R3 LAN 2 is the next largest subnet.1. How many IP addresses are needed for the R3 LAN 2?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 12. Assign the subnet to R3 LAN 2.Start with the IP address following the R3 LAN 1 subnet.1. Assign the next subnet to R3 LAN 2.2. Fill in the chart below with the appropriate information.3.R3 LAN 2 SubnetNetworkAddressDecimalSubnet MaskSubnetMask BitsFirst UsableAddressLast UsableAddressBroadcastAddressAt the end of this task your completion rate should be 0%.Task 3: Assign IP Addresses to the Network DevicesAssign the appropriate addresses to the device interfaces.Step 1: Assign addresses to the R1 router.1. Assign the first valid host address in the R1 LAN 1 subnet to the Fa0/0 LANinterface.2. Assign the first valid host address in the R1 LAN 2 subnet to the Fa0/1 LANinterface.Step 2. Assign addresses to the R2 router.1. Assign the first valid host address in the R2 LAN 1 subnet to the Fa0/0 LANinterface.2. Assign the first valid host address in the R2 LAN 2 subnet to the Fa0/1 LANinterface.Step 3. Assign addresses to the R3 router.1. Assign the first valid host address in the R3 LAN 1 subnet to the Fa0/0 LANinterface.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 5 of 6
  • 79. CCNA DiscoveryDesigning and Supporting Computer Networks2. Assign the first valid host address in the R3 LAN 2 subnet to the Fa0/1 LANinterface.At the end of this task your completion rate should be 60%.Task 4: Configure Routing ProtocolIn order to provide connectivity among the LANs, a routing protocol must be configured on eachrouter. The routing protocol must meet these requirements:• Classless routing operation that supports VLSM• Small and infrequent routing table updates to reduce traffic• Fast convergence in the event of a failureWhat routing protocol meets these requirements?Step 1. Configuring the Routing Protocol on R1.1. What networks need to be advertised from the R1 Router?2. What commands would be used if these networks were advertised as subnets inAS number 1?Step 2. Configuring the Routing Protocol on R2.1. What networks need to be advertised from the R2 Router?2. What commands would be used if these networks were advertised as subnets inAS number 1?Step 3. Configuring the Routing Protocol on R3.1. What networks need to be advertised from the R3 Router?2. What commands would be used if these networks were advertised as subnets inAS number 1?Task 5: Test the Network Design.Apply your addressing scheme to the Packet Tracer file that has been supplied with this lab.What command would be used in order to check if all the networks have been advertised?Step 1. List the results of the show IP route command for R1.Step 2. List the results of the show IP route command for R2.Step 3. List the results of the show IP route command for R3.Step 4. Are all routes shown in their routing tables?At the end of this task your completion rate should be 100%.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 6 of 6
  • 80. CCNA DiscoveryDesigning and Supporting Computer Networks6.2.5 Assigning IP AddressesAddressing TableDevice Interface IP Address Subnet Mask Default GatewayS0/0/0 N/AS0/0/1 N/AR1S0/1/0 N/AFa0/0 N/AR2S0/0/0 N/AFa0/0 N/AR3S0/0/0 N/AFa0/0 N/AR4S0/0/0 N/AR2 Host-A NICR2 Host-B NICR2 Printer-A NICR2 Host-C NICR2 Host-D NICR3 Host-A NICR3 Host-B NICR3 Printer-B NICR3 Host-C NICR3 Host-D NICR4 Host-A NICR4 Host-B NICR4 Printer-C NICR4 Host-C NICR4 Host-D NICAll contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 6
  • 81. CCNA DiscoveryDesigning and Supporting Computer NetworksLearning Objectives• Determine the number of subnets needed.• Determine the number of hosts needed for each subnet.• Design an appropriate addressing scheme using VLSM.• Assign addresses and subnet mask pairs to device interfaces.IntroductionIn this activity, you have been given the network address 172.16.0.0/16 to subnet and providethe IP addressing for the network shown in the Topology Diagram. VLSM will be used so thatthe addressing requirements can be met using the 172.16.0.0/16 network. Subnet 0 will also beused. The network has the following addressing requirements:• The R2 LAN will require 8,000 host IP addresses.• The R3 LAN will require 1,000 host IP addresses.• The R4 LAN will require 250 host IP addresses.• The link from R1 to R2 will require an IP address for each end of the link.• The link from R1 to R3 will require an IP address for each end of the link.• The link from R1 to R4 will require an IP address for each end of the link.Required file: Assigning IP Addresses.pkaTask 1: Examine the Network Requirements.Examine the network requirements and answer the questions below. Keep in mind that IPaddresses will be needed for each LAN interface on each router.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 the R2 LAN?4. How many IP addresses are needed for the R3 LAN?5. How many IP addresses are needed for the R4 LAN?6. How many IP addresses are needed for each of the WAN links?7. What is the total number of IP addresses that are needed?8. What is the total number of IP addresses that are available in the 172.16.0.0/16network?9. Can the network addressing requirements be met using the 172.16.0.0/16 network?At the end of this task your completion rate should be 0%.Task 2: Design an IP Addressing SchemeStep 1. Determine the subnet information for the largest network segment or segments.In this case, the R2 LAN is the largest subnets.1. How many IP addresses are needed for the R2 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?All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 6
  • 82. CCNA DiscoveryDesigning and Supporting Computer NetworksStep 2. Assign the subnet to the R2 LAN.Start at the beginning of the 172.16.0.0/16 network.1. Assign the first available subnet to the R2 LAN.2. Fill in the chart below with the appropriate information.R2 LAN SubnetSubnet Mask BitsNetworkAddressDecimalSubnet MaskSubnetMask BitsFirst UsableAddressLast UsableAddressBroadcastAddressStep 3. Determine the subnet information for the next largest network segment orsegments.In this case, the R3 LAN is the next largest subnet.1. How many IP addresses are needed for the R3 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 4. Assign the subnet to R3 LAN. Start with the IP address following the R2 LANsubnet.1. Assign the next subnet to R3 LAN.2. Fill in the chart below with the appropriate information.R3 LAN SubnetNetworkAddressDecimalSubnet MaskSubnetMask BitsFirst UsableAddressLast UsableAddressBroadcastAddressStep 5. Determine the subnet information for the next largest network segment orsegments.In this case, the R4 LAN is the next largest subnet.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 3 of 6
  • 83. CCNA DiscoveryDesigning and Supporting Computer Networks1. How many IP addresses are needed for the R4 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 6. Assign the subnet to R4 LAN.Start with the IP address following the R3 LAN subnets.1. Assign the next subnet to the R4 LAN.2. Fill in the chart below with the appropriate information.R4 LAN Subnet NetworkNetworkAddressDecimalSubnet MaskSubnetMask BitsFirst UsableAddressLast UsableAddressBroadcastAddressStep 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 R4 LAN subnets.1. Assign the next available subnet to the link between the R1 and R2 routers.2. Fill in the chart below with the appropriate information.NetworkAddressDecimalSubnet MaskSubnetMask BitsFirst UsableAddressLast UsableAddressBroadcastAddress3. Assign the next available subnet to the link between the R1 and R3 routers.4. Fill in the chart below with the appropriate information.NetworkAddressDecimalSubnet MaskSubnetMask BitsFirst UsableAddressLast UsableAddressBroadcastAddress5. Assign the next available subnet to the link between the R1 and R4 routers.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 4 of 6
  • 84. CCNA DiscoveryDesigning and Supporting Computer Networks6. Fill in the chart below with the appropriate information.Atthe end of this task your completion rate should be 0%.NetworkAddressDecimalSubnet MaskSubnetMask BitsFirst UsableAddressLast UsableAddressBroadcastAddressTask 3: Assign IP Addresses to the Network DevicesAssign the appropriate addresses to the device interfaces. Document the addresses to be usedin the Addressing Table provided under the Topology Diagram.Step 1: Assign addresses to the R1 router.1. Assign the first valid host address in the link between R1 and R2 subnet to the s0/0/0interface.2. Assign the first valid host address in the link between R1 and R3 subnet to theS0/0/1 interface.3. Assign the first valid host address in the link between R1 and R4 subnet to theS0/1/0 interface.Step 2: Assign addresses to the R2 router.1. Assign the first valid host address in the R2 LAN subnet to the Fa0/0 LAN interface.2. Assign the last valid host address on the link between R1 and R2 subnet to theS0/0/0 interfaceStep 3: Assign addresses to the R3 router.1. Assign the first valid host address in the R3 LAN subnet to the Fa0/0 LAN interface.2. Assign the last valid host address on the link between R1 and R3 subnet to theS0/0/0 interface.Step 4: Assign addresses to the R4 router.1. Assign the first valid host address in the R4 LAN subnet to the Fa0/0 LAN interface.2. Assign the last valid host address on the link between R1 and R4 subnet to theS0/0/0 interface.Step 5: Assign addresses to the host devices (PCs and Printer) of R2.1. Assign the second valid host address in the R2 LAN subnet to R2 Host-A.2. Assign the third valid host address in the R2 LAN subnet to R2 Host-B.3. Assign the fourth valid host address in the R2 LAN subnet to R2 Printer-A.4. Assign the fifth valid host address in the R2 LAN subnet to R2 Host-C.5. Assign the sixth valid host address in the R2 LAN subnet to R2 Host-D.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 5 of 6
  • 85. CCNA DiscoveryDesigning and Supporting Computer NetworksStep 6: Assign addresses to the host devices (PCs and Printer) of R3.1. Assign the second valid host address in the R3 LAN subnet to R3 Host-A.2. Assign the third valid host address in the R3 LAN subnet to R3 Host-B.3. Assign the fourth valid host address in the R3 LAN subnet to R3 Printer -B.4. Assign the fifth valid host address in the R3 LAN subnet to R3 Host-C.5. Assign the sixth valid host address in the R3 LAN subnet to R3 Host-D.Step 7: Assign addresses to the host devices (PCs and Printer) of R4.1. Assign the second valid host address in the R4 LAN subnet to R4 Host-A.2. Assign the third valid host address in the R4 LAN subnet to R4 Host-B.3. Assign the fourth valid host address in the R4 LAN subnet to R4 Printer-C.4. Assign the fifth valid host address in the R4 LAN subnet to R4 Host-C.5. Assign the sixth valid host address in the R4 LAN subnet to R4 Host-D.At the end of this task your completion rate should be 100%.Task 4: Verify connectivity.Verify that all hosts and printers can ping their respective default gateways and that theSerial interfaces can ping each other as well. There is no routing protocol running and nostatic routing. Devices will only be able to ping their directly connected neighbors.At the end of this task your completion rate should be 100%.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 6 of 6
  • 86. CCNA DiscoveryDesigning and Supporting Computer Networks7.1.4 Using Commands to Test Network FunctionalityObjective• Describe various tools and methods used to validate that the design is working as anticipated.640-802 CCNA Exam ObjectivesThis activity contains skills that relate to the following CCNA exam objectives:• Verify network status and switch operation using basic utilities (including: ping, traceroute, telnet,SSH, arp, ipconfig), show & debug commandsAll contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 6
  • 87. CCNA DiscoveryDesigning and Supporting Computer Networks• Verify device configuration and network connectivity using ping, traceroute, telnet, SSH or otherutilities• Verify network connectivity (including: using ping, traceroute, and telnet or SSH)Expected Results and Success Criteriaa. Before beginning this activity, read through the tasks you are expected to perform. What do youexpect the result of performing these tasks will be?____________________________________________________________________________________________________________________________________________________________________________________________________________________________________b. Why do you think that it is important to verify the basic operation of the network even if it is just aprototype of the proposed network?____________________________________________________________________________________________________________________________________________________________________________________________________________________________________c. How can these techniques be used to document a prototype network that was designed by somebodyelse?____________________________________________________________________________________________________________________________________________________________________________________________________________________________________Background / PreparationThe router and switch IOS provides a number of commands in the CLI that provide detailed and summaryinformation about the configuration and operation of the device. These are known as show commands.This activity will use Packet Tracer to practice using various show commands to explore the configuration ofrouters and switches in a configured prototype network.Required file: Using Commands to Test Network Functionality.pkaStep 1: Console to a switch and explore the configuration.a. From PC1 establish a console connection to switch S1. Enter privileged exec mode, using the enablesecret password of class.b. Issue the command show running-config and list five pieces of information the command displays.____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________c. Issue the command show ip interface brief and list five pieces of information the command displays.________________________________________________________________________________________________________________________________________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 6
  • 88. CCNA DiscoveryDesigning and Supporting Computer Networks____________________________________________________________________________________________________________________________________________________________________________________________________________________________________d. Issue the command show version and list five pieces of information the command displays.____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________e. Issue the command show cdp neighbors and list five pieces of information the command displays.____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________f. Issue the command show cdp neighbors detail and list three additional pieces of information thecommand displays.____________________________________________________________________________________________________________________________________________________________________________________________________________________________________g. Write down an IP address you can use to reach router R1.____________________________________________________________________________Step 2: Telnet to a router and explore the configuration.a. From PC1 ping the IP address of router R1, telnet to router R1, the telnet password is cisco, andenter privileged exec mode, the enable secret is class.b. Issue the command show running-config and list five pieces of information the command displays.____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________c. Issue the command show ip interface brief and list five pieces of information the command displays.____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 3 of 6
  • 89. CCNA DiscoveryDesigning and Supporting Computer Networksd. Issue the command show interface and list five pieces of information the command displays.____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________e. Issue the command show version and list five pieces of information the command displays.____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________f. Issue the command show ip route and list five pieces of information the command displays.____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________g. Issue the command show ip protocols and list five pieces of information the command displays.____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________h. Issue the command show ip eigrp neighbors and list five pieces of information the commanddisplays.____________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________i. Issue the command show ip eigrp topology and list five pieces of information the commanddisplays.________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 4 of 6
  • 90. CCNA DiscoveryDesigning and Supporting Computer Networks____________________________________________________________________________j. Issue the command show cdp neighbors detail and write down IP addresses you can use to reachneighboring devices.____________________________________________________________________________________________________________________________________________________________________________________________________________________________________Step 3: Explore the remaining network devices.a. Repeat the above steps for the remaining routers and switch. Record the ip addresses assigned toeach device on the diagram below.b. Verify the flow of traffic through the network by issuing the tracert command from PC1 to the variousdevices in the network.Step 4: Reflectiona. What are some other commands you can think of to discover more information about the network?____________________________________________________________________________________________________________________________________________________________________________________________________________________________________b. If the results of your testing are not as expected, what commands could be used to observe real-timetraffic flowing through a device?All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 5 of 6
  • 91. CCNA DiscoveryDesigning and Supporting Computer Networks____________________________________________________________________________________________________________________________________________________________________________________________________________________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 6 of 6
  • 92. 7.2.2 Basic Connectivity Test PlanStart Date End DateNetwork Build (Setup)Testing Date
  • 93. Table of ContentsATTENDEES 3INTRODUCTION 4EQUIPMENT 4DESIGN AND TOPOLOGY DIAGRAM 5TEST 1. DESCRIPTION: BASELINE CONNECTIVITY TEST 6TEST 1. PROCEDURES: 6TEST 1. EXPECTED RESULTS AND SUCCESS CRITERIA: 6TEST 1. CONCLUSIONS 7APPENDIX 8
  • 94. AttendeesName Company Position
  • 95. IntroductionAn introduction to the testing explaining briefly what the purpose of the test is, and what shouldbe observed. Include a brief description of testing goals. List all tests you intend to run.For example:The purpose of this test plan is to demonstrate that the basic connectivity and routing protocol areconfigured correctly. This prototype network is used to test various aspects of the proposed design.• Test 1: Baseline Connectivity Test• Verify physical and IP connectivity between devices on the prototype network.• Collect operational baselines.• Demonstrate IP connectivity between devices on the same VLANs.• Demonstrate the routing protocol operates correctly and that the web server is accessiblethrough the network.EquipmentList all of the equipment needed to perform the tests. Be sure to include cables, optionalconnectors or components, and software.Qty. Req Model Any additionaloptions orsoftware requiredSubstitute IOS Software Rev.2 2960 Layer 2switchnone Any 2950 or 2960 modelswitch12.2 or above2 1841 ISRrouters with 2FastEthernetports and 2Serial portsnone Any multilayer switch orrouter with minimum 2FastEthernet ports andone serial port.12.2 or above2 PersonalComputer end-devicesFastEthernetNICAt least one PC and anyother IP end-device(camera, printer, etc.)Windows, MAC or Linuxoperating system.1 PersonalComputerServerFastEthernetNICAny PC with web serversoftware loadedWindows, MAC, orLinux operating system6 Cat 5 or abovestraight-through patchcables.none none n/a2 Cat 5 or abovecross-overpatch cablesnone none n/a2 V.35 DTESerial CablesNone None n/a2 V.35 DCESerial CablesNone None n/a
  • 96. Design and Topology DiagramPlace a copy of the prototype network topology in this section. This is the network as it should bebuilt to be able to perform the required tests. If this topology duplicates a section of the actualnetwork, include a reference topology showing the location within the existing or plannednetwork. Initial configurations for each device must be included in the Appendix.Figure 1: Topology - Prototype test topology.Add a description about this design here that is essential to provide a better understanding of thetesting or to emphasize any aspect of the test network to the reader.
  • 97. For each test to be performed state the goals of the test, the data to record during the test, and theestimated time to perform the test.Test 1. Description: Baseline Connectivity TestGoals of Test:The goal of the baseline is to verify that the topology is up and running withthe proper protocols and features.Data to Record:ConfigurationsRouting TablesCPU & MemoryPing Test OutputEstimated Time:120 minutesTest 1. Procedures:Itemize the procedures to follow to perform the test.1. Connect and configure the prototype network according to the Installation Checklist.2. Console into one of the devices in the topology and ping all of the other devices in the topology.Record any anomalies.3. Examine the “show running-config” and “show ip route” output. Copy and paste theresults into a document for later use.4. Telnet to all of the other devices and get the same information.5. Use the “traceroute” commands to verify that the traffic is taking the correct routes through thenetwork.6. Test IP connectivity between host devices on the same VLAN.7. Verify EIGRP configuration using “show ip route” and “show ip protocols”, and“show ip eigrp topology” or ““show ip eigrp interfaces”.Test 1. Expected Results and Success Criteria:List all of the expected results. Specific criteria that must be met for the test to be considered asuccess should be listed. An example of specific criteria is: “A requirement that ping responsetimes cannot exceed 100 ms.”1. All networking devices are connected and accessible through Telnet.2. Hosts on a VLAN can ping successfully to other hosts on the same VLAN.
  • 98. 3. EIGRP routes are advertised correctly and are installed into the routing tables on all of therouters.4. Web pages stored on the Discovery Server are available to both PCs.Test 1. Results and ConclusionsRecord the results of the tests and the conclusions that can be drawn from the results.
  • 99. AppendixRecord the starting configurations, any modifications, log file or command output, and any otherrelevant documentation.
  • 100. AppendixRecord the starting configurations, any modifications, log file or command output, and any otherrelevant documentation.
  • 101. CCNA DiscoveryDesigning and Supporting Computer Networks7.2.2 Building the Prototype NetworkObjective• Build and test a prototype network for use in the Stadium Prototype Test Plan.Background / PreparationIn this exercise, you will use the installation checklist provided by the network designer to build the prototypenetwork. Once the network is built and configured, you can perform the Basic Connectivity Test specified inthe designer’s test plan. Download the Stadium Prototype Test Plan document. Complete the StadiumPrototype Test Plan document after the prototype network has been built.Required files: Building the Prototype Network.pka, Stadium Prototype Test Plan.Step 1: Connect all devices as shown in the topology diagram.Step 2: Configure the hostnames and interface IP addresses on all of the devices.Step 3: Configure basic security on the devices: Privileged mode password and requirelogin on VTY ports.Step 4: Configure EIGRP routing on all routers and advertise all connected networks.Disable EIGRP default route summarization on all routers.Step 5: Perform Basic Connectivity Test according to the Stadium Prototype Test Plan.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 1
  • 102. 7.2.3 Testing Redundancy in the Network Design Test PlanStart Date End DateNetwork Build (Setup)Testing Date
  • 103. Table of ContentsATTENDEES 3INTRODUCTION 4EQUIPMENT 4DESIGN AND TOPOLOGY DIAGRAM 5TEST 1. NETWORK REDUNDANCY TEST 7TEST 1. PROCEDURES: 7TEST 1. EXPECTED RESULTS AND SUCCESS CRITERIA: 7TEST 1. CONCLUSIONS 9APPENDIX 10
  • 104. AttendeesName Company Position
  • 105. IntroductionAn introduction to the testing explaining briefly what the purpose of the test is, and what shouldbe observed. Include a brief description of testing goals. List all tests you intend to run.The purpose of this test plan is to demonstrate that the network can recover from failed links due to itsredundant design. This prototype network is used to test various aspects of the proposed design.• Test 1: Network Redundancy Test• Verify that redundant links allow successful recovery from failed links.• Compare the operation of static routes with the operation of a dynamic routing protocol when alink fails.EquipmentList all of the equipment needed to perform the tests. Be sure to include cables, optionalconnectors or components, and software.Qty. Req Model Any additionaloptions orsoftware requiredSubstitute IOS Software Rev.4 2960 Layer 2switchnone Any 2950 or 2960 modelswitch12.2 or above4 1841 ISRrouters with 2FastEthernetports and 2Serial portsnone Any multilayer switch orrouter with minimum 2FastEthernet ports andone serial port.12.2 or above2 PersonalComputer end-devicesFastEthernetNICAt least one PC and anyother IP end-device(camera, printer, etc.)Windows, MAC or Linuxoperating system.1 PersonalComputerServerFastEthernetNICAny PC with web serversoftware loadedWindows, MAC, orLinux operating system6 Cat 5 or abovestraight-through patchcables.none none n/a5 Cat 5 or abovecross-overpatch cablesnone none n/a1 V.35 DTESerial CablesNone None n/a1 V.35 DCESerial CablesNone None n/a
  • 106. Design and Topology DiagramPlace a copy of the prototype network topology in this section. This is the network as it should bebuilt to be able to perform the required tests. If this topology duplicates a section of the actualnetwork, include a reference topology showing the location within the existing or plannednetwork. Initial configurations for each device must be included in the Appendix.
  • 107. DeviceDesignation Interface IP Address Subnet maskR1 Fa0/0 172.18.4.1 255.255.255.0R1 Fa0/1 172.18.0.5 255.255.255.252R2 Fa0/0 172.18.4.2 255.255.255.0R2 Fa0/1 172.18.0.13 255.255.255.252R3 Fa0/0 172.18.0.14 255.255.255.252R3 Fa0/1 172.18.0.6 255.255.255.252R3 S0/1/0 * 172.18.0.17 255.255.255.252R4 Fa0/0 172.18.8.1 255.255.255.0R4 S0/1/0 * 172.18.0.18 255.255.255.252S1 VLAN1 172.18.4.3 255.255.255. 0S2 VLAN1 172.18.4.4 255.255.255. 0S3 VLAN1 172.18.4.5 255.255.255. 0S4 VLAN1 172.18.8.2 255.255.255.0PC1 172.18.4.10 255.255.255.0PC2 172.18.8.10 255.255.255.0DiscoveryServer 172.18.4.25 255.255.255.0Figure 1: Topology - Prototype test topology.Add a description about this design here that is essential to provide a better understanding of thetesting or to emphasize any aspect of the test network to the reader.
  • 108. For each test to be performed state the goals of the test, the data to record during the test, and theestimated time to perform the test.Test 1. Description: Network Redundancy TestGoals of Test:The goal of the test is to verify network recovery after a failed link in both aswitched and a routed environment and to compare the speed of recovery.Data to Record:ConfigurationsRouting TablesSpanning Tree OutputCPU & MemoryPing Test OutputTrace Route OutputEstimated Time:120 minutesTest 1. Procedures:Itemize the procedures to follow to perform the test.Step 1: Verify the configuration and operation of EIGRP.1. Console into one of the devices in the topology and ping all of the other devices in the topology.Record any anomalies.2. Telnet to router R1 and examine the show running-config, and show ip route output.Copy and paste the results into a document for later use.3. Telnet to all of the other routers and get the same information.4. Use the tracert between PC1 and PC2 to verify the path that the traffic is taking through thenetwork.5. Verify EIGRP configuration using show ip protocols, show ip eigrp topology, andshow ip eigrp interfaces.6. Record the results of this step in the Test1: Results and Conclusions section of this test plan.Step 2: Verify the configuration and operation of Spanning Tree Protocol.1. Telnet to switch S1 and examine show running-config output. Copy and paste the resultsinto a document for later use.2. Telnet to switches S2 and S3 and get the same information.3. Wait a few seconds for the Spanning Tree topology to converge.
  • 109. 4. Verify Spanning Tree operation using show spanning-tree vlan 1.5. Record the results of this step in the Test1: Results and Conclusions section of this test plan.Step 3: Simulate a failure in the switched portion of the network and verify and observe recovery.1. From PC1 issue the command ping -n 1000 172.18.4.25 to ping the Discovery serverthrough the switched network.2. To simulate a link failure, remove the link between S1 and S3.3. Observe the output of the extended ping and when it begins to succeed again, press Ctrl-C tointerrupt it.4. Telnet to all three switches and issue the command show spanning-tree vlan 1.5. Record the results of this step in the Test1: Results and Conclusions section of this test plan.Step 4: Simulate a failure in the routed portion of the network and verify and observe recovery.1. From PC1 issue the command ping -n 1000 172.18.8.10 to ping PC2 through the routednetwork.2. To simulate a link failure, remove the link between R2 and R3.3. Observe the output of the extended ping and after several more iterations, press Ctrl-C tointerrupt it.4. Use the tracert command from PC1 to PC2 to verify the path that the traffic is taking throughthe network.5. Telnet to all of the routers and issue the command show ip route.6. Record the results of this step in the Test1: Results and Conclusions section of this test plan.
  • 110. Test 1. Expected Results and Success Criteria:List all of the expected results. Specific criteria that must be met for the test to be considered asuccess should be listed. An example of specific criteria is: “A requirement that ping responsetimes cannot exceed 100 ms.”1. Both the switched and routed portion of the network should automatically recover from the loss ofa redundant link.2. The routed portion of the network should provide faster recovery after the failure of a redundantlink.Test 1. Results and ConclusionsRecord the results of the tests and the conclusions that can be drawn from the results.
  • 111. AppendixRecord the starting configurations, any modifications, log file or command output, and any otherrelevant documentation.
  • 112. AppendixRecord the starting configurations, any modifications, log file or command output, and any otherrelevant documentation.
  • 113. CCNA DiscoveryDesigning and Supporting Computer Networks7.2.3 Testing Redundancy in the Network DesignObjectiveDevelop methodologies for comparing devices and topologies.Background / PreparationThe purpose of this test plan is to demonstrate that the network can recover from failed links due to itsredundant design. This prototype network is used to test various aspects of the proposed design. Downloadand complete the Stadium Redundancy Test Plan document.Required files: Testing Redundancy in the Network Design.pka and Stadium Redundancy Test Plan (TestingRedundancy in the Network Design Test Plan) and Installation Checklist (Network Redundancy InstallationChecklist).Step 1: Verify the configuration and operation of EIGRP.Step 2: Verify the configuration and operation of Spanning Tree Protocol.Step 3: Simulate a failure in the switched portion of the network and verify and observerecovery.Step 4: Simulate a failure in the routed portion of the network and verify and observe recovery.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 1
  • 114. 7.2.4 Routing Protocol Test PlanStart Date End DateNetwork Build (Setup)Testing Date
  • 115. Table of ContentsATTENDEES 3INTRODUCTION 4EQUIPMENT 4DESIGN AND TOPOLOGY DIAGRAM 5TEST 1. ROUTING PROTOCOL TEST 7TEST 1. PROCEDURES: 7TEST 1. EXPECTED RESULTS AND SUCCESS CRITERIA: 7TEST 1. CONCLUSIONS 9APPENDIX 10
  • 116. AttendeesName Company Position
  • 117. IntroductionAn introduction to the testing explaining briefly what the purpose of the test is, and what shouldbe observed. Include a brief description of testing goals. List all tests you intend to run.The purpose of this test plan is to demonstrate that the basic connectivity and routing protocol areconfigured correctly. This prototype network is used to test various aspects of the proposed design.• Test 1: Routing Protocol Test• Verify that EIGRP recovers successfully from failed links.• Compare the operation of static routes with the operation of a dynamic routing protocol when alink fails.EquipmentList all of the equipment needed to perform the tests. Be sure to include cables, optionalconnectors or components, and software.Qty. Req Model Any additionaloptions orsoftware requiredSubstitute IOS Software Rev.4 2960 Layer 2switchnone Any 2950 or 2960 modelswitch12.2 or above4 1841 ISRrouters with 2FastEthernetports and 2Serial portsnone Any multilayer switch orrouter with minimum 2FastEthernet ports andone serial port.12.2 or above2 PersonalComputer end-devicesFastEthernetNICAt least one PC and anyother IP end-device(camera, printer, etc.)Windows, MAC or Linuxoperating system.1 PersonalComputerServerFastEthernetNICAny PC with web serversoftware loadedWindows, MAC, orLinux operating system6 Cat 5 or abovestraight-through patchcables.none none n/a5 Cat 5 or abovecross-overpatch cablesnone none n/a1 V.35 DTESerial CablesNone None n/a1 V.35 DCESerial CablesNone None n/a
  • 118. Design and Topology DiagramPlace a copy of the prototype network topology in this section. This is the network as it should bebuilt to be able to perform the required tests. If this topology duplicates a section of the actualnetwork, include a reference topology showing the location within the existing or plannednetwork. Initial configurations for each device must be included in the Appendix.
  • 119. DeviceDesignation Interface IP Address Subnet maskR1 Fa0/0 172.18.4.1 255.255.255.0R1 Fa0/1 172.18.0.5 255.255.255.252R2 Fa0/0 172.18.4.2 255.255.255.0R2 Fa0/1 172.18.0.13 255.255.255.252R3 Fa0/0 172.18.0.14 255.255.255.252R3 Fa0/1 172.18.0.6 255.255.255.252R3 S0/1/0 * 172.18.0.17 255.255.255.252R4 Fa0/0 172.18.8.1 255.255.255.0R4 S0/1/0 * 172.18.0.18 255.255.255.252S1 VLAN1 172.18.4.3 255.255.255. 0S2 VLAN1 172.18.4.4 255.255.255. 0S3 VLAN1 172.18.4.5 255.255.255. 0S4 VLAN1 172.18.8.2 255.255.255.0PC1 172.18.4.10 255.255.255.0PC2 172.18.8.10 255.255.255.0DiscoveryServer 172.18.4.25 255.255.255.0Figure 1: Topology - Prototype test topology.Add a description about this design here that is essential to provide a better understanding of thetesting or to emphasize any aspect of the test network to the reader.
  • 120. For each test to be performed state the goals of the test, the data to record during the test, and theestimated time to perform the test.Test 1. Description: Routing Protocol TestGoals of Test:The goal of the test is to verify the expected operation of the EIGRP routingprotocol compared to static routes.Data to Record:ConfigurationsRouting TablesCPU & MemoryPing Test OutputTrace Route OutputEstimated Time:120 minutesTest 1. Procedures:Itemize the procedures to follow to perform the test.Step 1: Verify the configuration and operation of EIGRP.1. Console into one of the devices in the topology and ping all of the other devices in the topology.Record any anomalies.2. Telnet to router R1 and examine the show running-config, and show ip route output.Copy and paste the results into a document for later use.3. Telnet to all of the other routers and get the same information.4. Use the tracert between PC1 and PC2 to verify the path that the traffic is taking through thenetwork.5. Verify EIGRP configuration using show ip route, show ip protocols, show ip eigrptopology, and show ip eigrp interfaces.6. Record the results of this step in the Test1: Results and Conclusions section of this test plan.Step 2: Verify that EIGRP can recover from a routed link failure.1. Telnet to Router R2.2. Disable the link between R2 and R3 by shutting down interface fa0/1 on R2.3. Wait a few seconds for the EIGRP topology to converge.4. Examine the show ip route output. Copy and paste the results into a document for later use.
  • 121. 5. Compare the command output with the previously recorded show ip route output for R2.6. Use the tracert command on PC1 and PC2 to verify the path that the traffic is taking throughthe network.7. Record the results of this step in the Test1: Results and Conclusions section of this test plan.Step 3: Remove EIGRP from R2 and configure static routes.1. Telnet to router R2,2. Enable the link between R2 and R3 by activating interface fa0/1 on R2.3. Remove EIGRP from router R2 by using the no router EIGRP 1 command.4. Add a static default route to Router R2 that uses Router R3 as the default gateway.ip route 0.0.0.0 0.0.0.0 172.18.0.45. Telnet to router R3,6. Add a static route to router R3 using the ip route 172.18.4.0 255.255.255.0172.18.0.13 to enable R3 to use R2 to reach the 172.18.4.0/24 network.7. Use the show ip route command on routers R2 and R3 to verify that the static routes areentered correctly.8. Use the tracert and ping commands to verify connectivity between PC1 and PC2.9. Record the results of this step in the Test1: Results and Conclusions section of this test plan.Step 4: Verify that static routes can recover from a link failure.1. Telnet to router R2.2. Disable the link between R2 and R3 by shutting down interface fa0/1 on R2.3. Examine the show ip route output. Copy and paste the results into a document for later use.4. Compare the output with the previously recorded output from steps 1 and 2.5. Use the tracert command on PC1 and PC2 to verify the path that the traffic is taking throughthe network.6. Record the results of this step in the Test1: Results and Conclusions section of this test plan.
  • 122. Test 1. Expected Results and Success Criteria:List all of the expected results. Specific criteria that must be met for the test to be considered asuccess should be listed. An example of specific criteria is: “A requirement that ping responsetimes cannot exceed 100 ms.”1. EIGRP recovers dynamically from the link failure and restores connectivity between PC1 andPC2. This can be verified by the output of the show ip route command and a successfultrace route between PC1 and PC2.2. Static routes in Router R2 and R3 do not recover from the link failure and connectivity betweenPC1 and PC2 is not restored.Test 1. Results and ConclusionsRecord the results of the tests and the conclusions that can be drawn from the results.
  • 123. AppendixRecord the starting configurations, any modifications, log file or command output, and any otherrelevant documentation.
  • 124. AppendixRecord the starting configurations, any modifications, log file or command output, and any otherrelevant documentation.
  • 125. CCNA DiscoveryDesigning and Supporting Computer Networks7.2.4 Testing a Multi-Router Network with Redundant LinksObjectiveDevelop methodologies for selecting and testing the appropriate routing protocol based on networkrequirements.Background / PreparationThe purpose of this test plan is to demonstrate that the basic connectivity and routing protocol are configuredcorrectly. This prototype network is used to test various aspects of the proposed design. Download andcomplete the Stadium Routing Protocol Test Plan document.Required files: Testing a Multi-Router Network with Redundant Links.pka and Stadium Routing Protocol TestPlan.Step 1: Verify the configuration and operation of EIGRP.Step 2: Verify that EIGRP can recover from a routed link failure.Step 3: Remove EIGRP from R2 and configure static routes.Step 4: Verify that static routes can recover from a link failure..All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 1
  • 126. 7.2.5 Validating the IP Addressing Scheme Test PlanStart Date End DateNetwork Build (Setup)Testing Date
  • 127. Table of ContentsATTENDEES 3INTRODUCTION 4EQUIPMENT 4DESIGN AND TOPOLOGY DIAGRAM 5TEST 1. VALIDATING THE IP ADDRESSING SCHEME TEST 7TEST 1. PROCEDURES: 7TEST 1. EXPECTED RESULTS AND SUCCESS CRITERIA: 7TEST 1. CONCLUSIONS 9APPENDIX 10
  • 128. AttendeesName Company Position
  • 129. IntroductionAn introduction to the testing explaining briefly what the purpose of the test is, and what shouldbe observed. Include a brief description of testing goals. List all tests you intend to run.The purpose of this test plan is to validate the IP addressing scheme and to examine the content of thecore routing tables and test schemes to reduce the number of entries. This prototype network is used totest various aspects of the proposed design.• Test 1: Validating the IP Addressing Scheme Test• Verify the IP address scheme and that all devices are fully reachable.• Examine ways to reduce the size of the core routing tables by using route summarization.EquipmentList all of the equipment needed to perform the tests. Be sure to include cables, optionalconnectors or components, and software.Qty. Req Model Any additionaloptions orsoftware requiredSubstitute IOS Software Rev.4 2960 Layer 2switchnone Any 2950 or 2960 modelswitch12.2 or above4 1841 ISRrouters with 2FastEthernetports and 2Serial portsnone Any multilayer switch orrouter with minimum 2FastEthernet ports andone serial port.12.2 or above2 PersonalComputer end-devicesFastEthernetNICAt least one PC and anyother IP end-device(camera, printer, etc.)Windows, MAC or Linuxoperating system.1 PersonalComputerServerFastEthernetNICAny PC with web serversoftware loadedWindows, MAC, orLinux operating system6 Cat 5 or abovestraight-through patchcables.none none n/a1 Cat 5 or abovecross-overpatch cablesnone none n/a3 V.35 DTESerial CablesNone None n/a3 V.35 DCESerial CablesNone None n/a
  • 130. Design and Topology DiagramPlace a copy of the prototype network topology in this section. This is the network as it should bebuilt to be able to perform the required tests. If this topology duplicates a section of the actualnetwork, include a reference topology showing the location within the existing or plannednetwork. Initial configurations for each device must be included in the Appendix.
  • 131. DeviceDesignation Interface IP Address Subnet maskR1 Fa0/0 172.16.4.1 255.255.255.0R1 Fa0/1 172.15.5.1 255.255.255.0R1 S0/1/0 192.168.1.1 255.255.255.0R2 Fa0/0 172.17.6.1 255.255.255.0R2 Fa0/1 172.17.7.1 255.255.255.0R2 S0/1/0 192.168.2.1 255.255.255.0R3 S0/0/0 192.168.1.2 255.255.255.0R3 S0/0/1 192.168.2.2 255.255.255.0R3 S0/1/0 192.168.0.1 255.255.255.0R4 Fa0/0 172.18.0.1 255.255.0.0R4 S0/1/0 192.168.0.2 255.255.255.0S1 VLAN1 172.16.4.3 255.255.255. 0S2 VLAN1 172.16.5.2 255.255.255. 0S3 VLAN1 172.17.6.2 255.255.255. 0S4 VLAN1 172.17.7.2 255.255.255.0PC1 172.18.4.10 255.255.255.0PC2 172.18.0.10 255.255.0.0DiscoveryServer 172.18.4.25 255.255.255.0Figure 1: Topology - Prototype test topology.Add a description about this design here that is essential to provide a better understanding of thetesting or to emphasize any aspect of the test network to the reader.
  • 132. For each test to be performed state the goals of the test, the data to record during the test, and theestimated time to perform the test.Test 1. Description: Validating the IP Addressing SchemeTestGoals of Test:The goal of the test is to verify the IP addressing scheme and summarizeroutes to reduce the size of the core routing tables.Data to Record:ConfigurationsRouting TablesCPU & MemoryPing Test OutputTrace Route OutputEstimated Time:120 minutesTest 1. Procedures:Itemize the procedures to follow to perform the test.Step 1: Verify the configuration and operation of EIGRP.1. Console into one of the devices in the topology and ping all of the other devices in the topology.Record any anomalies.2. Telnet to router R1 and examine the show running-config, and show ip route output.Copy and paste the results into a document for later use.3. Telnet to all of the other routers and get the same information.4. Use the tracert between PC1 and PC2 to verify the path that the traffic is taking through thenetwork.5. Verify EIGRP configuration using show ip protocols, show ip eigrp topology, andshow ip eigrp interfaces.6. Record the results of this step in the Test1: Results and Conclusions section of this test plan.Step 2: Configure the routers to allow automatic summarization.1. Telnet to every router.2. On each router, enter router configuration mode by issuing the command router eigrp 1.3. Enter the command auto-summary to allow automatic summarization.
  • 133. 4. Exit configuration mode and save the running configuration.5. Click the Power Cycle Devices button on the lower task bar to force the network to reconverge.Step 3: Verify the configuration and operation of EIGRP for the summarized network.1. Start a log file and record the show running-config, and show ip route output.2. Telnet to router R1 and examine the show running-config, and show ip route output.Copy and paste the results into a document for later use.3. Use the tracert between PC1 and PC2 to verify the path that the traffic is taking through thenetwork.4. On the routers, verify EIGRP configuration using show ip protocols, show ip eigrptopology, and show ip eigrp interfaces.5. Record the results of this step in the Test1: Results and Conclusions section of this test plan.
  • 134. Test 1. Expected Results and Success Criteria:List all of the expected results. Specific criteria that must be met for the test to be considered asuccess should be listed. An example of specific criteria is: “A requirement that ping responsetimes cannot exceed 100 ms.”1. All devices in the network should be reachable in both configurations.2. With automatic summarization enabled, the size of the routing tables on the core router should bereduced.Test 1. Results and ConclusionsRecord the results of the tests and the conclusions that can be drawn from the results.
  • 135. AppendixRecord the starting configurations, any modifications, log file or command output, and any otherrelevant documentation.
  • 136. 7.3.4 Testing ACLsStart Date End DateNetwork Build (Setup)Testing Date
  • 137. Table of ContentsATTENDEES 3INTRODUCTION 4EQUIPMENT 4DESIGN AND TOPOLOGY DIAGRAM 5TEST 1. DESCRIPTION: ACCESS CONTROL LISTS TEST 7TEST 1. PROCEDURES: 8TEST 1. EXPECTED RESULTS AND SUCCESS CRITERIA: 8TEST 1. CONCLUSIONS 9APPENDIX 10
  • 138. AttendeesName Company Position
  • 139. IntroductionAn introduction to the testing explaining briefly what the purpose of the test is, and what shouldbe observed. Include a brief description of testing goals. List all tests you intend to run.For example:The purpose of this test plan is to add access control lists to the prototype network to secure unauthorizedaccess to the server farm and to demonstrate that the access control lists are configured correctly. Thisrevised prototype network is used to test various aspects of the proposed design.• Test 1: Access Control Lists Test• Verify full connectivity from all PCs to all servers.• Plan access control lists to prevent unauthorized access to the server farm.• Configure access control lists on Distribution Layer devices and apply them to the properinterfaces in the proper direction.• Verify proper operation of the access control lists by verifying that permitted traffic gets throughto the servers and unauthorized traffic is blocked.EquipmentList all of the equipment needed to perform the tests. Be sure to include cables, optionalconnectors or components, and software.Qty. Req Model Any additionaloptions orsoftware requiredSubstitute IOS Software Rev.5 2960 Layer 2switchnone Any 2950 or 2960 modelswitch12.2 or above5 1841 ISRrouters with 2FastEthernetports and 2Serial portsnone Any multilayer switch orrouter with minimum 2FastEthernet ports andtwo serial port.12.2 or above3 PersonalComputer end-devicesFastEthernetNICAt least one PC and anyother IP end-device(camera, printer, etc.)Windows, MAC or Linuxoperating system.6 PersonalComputerServerFastEthernetNICAny PC with web serverand DNS software loadedWindows, MAC, orLinux operating system12 Cat 5 or abovestraight-through patchcables.none none n/a6 Cat 5 or abovecross-overpatch cablesnone none n/a5 V.35 DTESerial CablesNone None n/a5 V.35 DCESerial CablesNone None n/a
  • 140. Design and Topology DiagramPlace a copy of the prototype network topology in this section. This is the network as it should bebuilt to be able to perform the required tests. If this topology duplicates a section of the actualnetwork, include a reference topology showing the location within the existing or plannednetwork. Initial configurations for each device must be included in the Appendix.
  • 141. DeviceDesignation Interface IP Address Subnet mask GatewayR1 Fa0/0.1 172.18.2.1 255.255.255.0 N/AR1 Fa0/0.21 172.18.21.1 255.255.255.0 N/AR1 Fa0/0.22 172.18.22.1 255.255.255.0 N/AR1 Fa0/0.23 172.18.23.1 255.255.255.0 N/AR1 Fa0/1 172.18.0.17 255.255.255.252 N/AR1 S0/1/0 * DTE 172.18.0.13 255.255.255.252 N/AR1 S0/1/1 * DCE 172.18.0.25 255.255.255.252 N/AR2 Fa0/0.1 172.18.2.2 255.255.255.0 N/AR2 Fa0/0.21 172.18.21.2 255.255.255.0 N/AR2 Fa0/0.22 172.18.22.2 255.255.255.0 N/AR2 Fa0/0.23 172.18.23.2 255.255.255.0 N/AR2 Fa0/1 172.18.0.21 255.255.255.252 N/AR2 S0/1/0 * DTE 172.18.0.10 255.255.255.252 N/AR2 S0/1/1 * DTE 172.18.0.26 255.255.255.252 N/AR3 Fa0/0 172.18.0.18 255.255.255.252 N/AR3 S0/1/0 * DTE 172.18.0.1 255.255.255.252 N/AR3 S0/1/1 * DCE 172.18.0.9 255.255.255.252 N/AR4 Fa0/0 172.18.0.22 255.255.255.252 N/AR4 S0/1/0 * DTE 172.18.0.5 255.255.255.252 N/AR4 S0/1/1 * DCE 172.18.0.14 255.255.255.252 N/AR5 Fa0/0 172.18.1.1 255.255.255.0 N/AR5 S0/1/0 * DCE 172.18.0.2 255.255.255.252 N/AR5 S0/1/1 * DCE 172.18.0.6 255.255.255.252 N/AS1 VLAN1 172.18.2.3 255.255.255.0 172.18.2.1S2 VLAN1 172.18.2.4 255.255.255.0 172.18.2.1S3 VLAN1 172.18.2.5 255.255.255.0 172.18.2.1S4 VLAN1 172.18.2.6 255.255.255.0 172.18.2.1S5 VLAN1 172.18.1.2 255.255.255.0 172.18.1.1PC1 172.18.23.10 255.255.255.0 172.18.23.1PC2 172.18.1.10 255.255.255.0 172.18.1.1PC3 172.18.1.11 255.255.255.0 172.18.1.1Web 1A 172.18.21.3 255.255.255.0 172.18.21.1Web 1B 172.18.21.4 255.255.255.0 172.18.21.2DNS A 172.18.22.3 255.255.255.0 172.18.22.1DNS B 172.18.22.4 255.255.255.0 172.18.22.2Web 2A 172.18.23.3 255.255.255.0 172.18.23.1Web 2B 172.18.23.4 255.255.255.0 172.18.23.2
  • 142. Figure 1: Topology - Prototype test topology.Add a description about this design here that is essential to provide a better understanding of thetesting or to emphasize any aspect of the test network to the reader.For each test to be performed state the goals of the test, the data to record during the test, and theestimated time to perform the test.Test 1. Description: Access Control Lists TestGoals of Test:The goal of the test is to verify that access control lists are properlyconfigured and applied to permit authorized traffic and to block unauthorizedtraffic.Data to Record:ConfigurationsRouter configurationsACL informationPing Test OutputWeb page access informationEstimated Time:120 minutes
  • 143. Test 1. Procedures:Itemize the procedures to follow to perform the test.Step 1: Verify full connectivity from all PCs to all servers.1. From PC1 and PC2 ping all of the servers in the topology. Record the results.2. From PC1 and PC2 access the following web pages: www.web1a.com, www.web1b.com,www.web2a.com, and www.web2b.com. Record the results.3. From PC2, ping the Fa0/1 interface of routers R1 and R2 to verify connectivity and then telnet torouters R1 and R2 and get the “show running-config” output. Copy and paste the results intoa document for later use.Step 2: Plan access control lists to prevent unauthorized access to the server farm.1. Design an access control list numbered 101 to allow only web access from hosts on the internalnetwork, 172.18.0.0/16, to any device and deny all other traffic. Design an access control listnumbered 102 to allow only DNS access from hosts on the internal network, 172.18.0.0/16, to anydevice and deny all other traffic.Step 3: Configure and apply access control lists.1. Telnet to routers R1 and R2 and add both access control lists and apply them on to the properinterfaces in the proper direction to protect the servers connected to that interface.Step 4: Verify proper operation of the access control lists.1. From PC1 and PC2 ping all of the servers in the topology. Record the results.2. From PC1 and PC2 access the following web pages: www.web1a.com, www.web1b.com,www.web2a.com, and www.web2b.com. Record the results.3. Telnet to routers R1 and R2 and document the final cofiguration using “show running-config”, and “show access-lists”.Test 1. Expected Results and Success Criteria:List all of the expected results. Specific criteria that must be met for the test to be considered asuccess should be listed. An example of specific criteria is: “A requirement that ping responsetimes cannot exceed 100 ms.”1. Prior to configuring access control lists both PCs can ping all servers and access all web pages.2. After configuring access control lists, PC2, representing a legitimate inside user, can not ping anyserver but can access all web pages.3. After configuring access control lists, PC1, representing a PC set up to maintain switchconfigurations, can ping servers in its own VLAN, can not ping other servers, and can not accessany web pages.
  • 144. 4. Test 1. Results and ConclusionsRecord the results of the tests and the conclusions that can be drawn from the results.
  • 145. AppendixRecord the starting configurations, any modifications, log file or command output, and any otherrelevant documentation.
  • 146. 7.3.4 Testing ACLsStart Date End DateNetwork Build (Setup)Testing Date
  • 147. Table of ContentsATTENDEES 3INTRODUCTION 4EQUIPMENT 4DESIGN AND TOPOLOGY DIAGRAM 5TEST 1. DESCRIPTION: ACCESS CONTROL LISTS TEST 7TEST 1. PROCEDURES: 8TEST 1. EXPECTED RESULTS AND SUCCESS CRITERIA: 8TEST 1. CONCLUSIONS 9APPENDIX 10
  • 148. AttendeesName Company Position
  • 149. IntroductionAn introduction to the testing explaining briefly what the purpose of the test is, and what shouldbe observed. Include a brief description of testing goals. List all tests you intend to run.For example:The purpose of this test plan is to add access control lists to the prototype network to secure unauthorizedaccess to the server farm and to demonstrate that the access control lists are configured correctly. Thisrevised prototype network is used to test various aspects of the proposed design.• Test 1: Access Control Lists Test• Verify full connectivity from all PCs to all servers.• Plan access control lists to prevent unauthorized access to the server farm.• Configure access control lists on Distribution Layer devices and apply them to the properinterfaces in the proper direction.• Verify proper operation of the access control lists by verifying that permitted traffic gets throughto the servers and unauthorized traffic is blocked.EquipmentList all of the equipment needed to perform the tests. Be sure to include cables, optionalconnectors or components, and software.Qty. Req Model Any additionaloptions orsoftware requiredSubstitute IOS Software Rev.5 2960 Layer 2switchnone Any 2950 or 2960 modelswitch12.2 or above5 1841 ISRrouters with 2FastEthernetports and 2Serial portsnone Any multilayer switch orrouter with minimum 2FastEthernet ports andtwo serial port.12.2 or above3 PersonalComputer end-devicesFastEthernetNICAt least one PC and anyother IP end-device(camera, printer, etc.)Windows, MAC or Linuxoperating system.6 PersonalComputerServerFastEthernetNICAny PC with web serverand DNS software loadedWindows, MAC, orLinux operating system12 Cat 5 or abovestraight-through patchcables.none none n/a6 Cat 5 or abovecross-overpatch cablesnone none n/a5 V.35 DTESerial CablesNone None n/a5 V.35 DCESerial CablesNone None n/a
  • 150. Design and Topology DiagramPlace a copy of the prototype network topology in this section. This is the network as it should bebuilt to be able to perform the required tests. If this topology duplicates a section of the actualnetwork, include a reference topology showing the location within the existing or plannednetwork. Initial configurations for each device must be included in the Appendix.
  • 151. DeviceDesignation Interface IP Address Subnet mask GatewayR1 Fa0/0.1 172.18.2.1 255.255.255.0 N/AR1 Fa0/0.21 172.18.21.1 255.255.255.0 N/AR1 Fa0/0.22 172.18.22.1 255.255.255.0 N/AR1 Fa0/0.23 172.18.23.1 255.255.255.0 N/AR1 Fa0/1 172.18.0.17 255.255.255.252 N/AR1 S0/1/0 * DTE 172.18.0.13 255.255.255.252 N/AR1 S0/1/1 * DCE 172.18.0.25 255.255.255.252 N/AR2 Fa0/0.1 172.18.2.2 255.255.255.0 N/AR2 Fa0/0.21 172.18.21.2 255.255.255.0 N/AR2 Fa0/0.22 172.18.22.2 255.255.255.0 N/AR2 Fa0/0.23 172.18.23.2 255.255.255.0 N/AR2 Fa0/1 172.18.0.21 255.255.255.252 N/AR2 S0/1/0 * DTE 172.18.0.10 255.255.255.252 N/AR2 S0/1/1 * DTE 172.18.0.26 255.255.255.252 N/AR3 Fa0/0 172.18.0.18 255.255.255.252 N/AR3 S0/1/0 * DTE 172.18.0.1 255.255.255.252 N/AR3 S0/1/1 * DCE 172.18.0.9 255.255.255.252 N/AR4 Fa0/0 172.18.0.22 255.255.255.252 N/AR4 S0/1/0 * DTE 172.18.0.5 255.255.255.252 N/AR4 S0/1/1 * DCE 172.18.0.14 255.255.255.252 N/AR5 Fa0/0 172.18.1.1 255.255.255.0 N/AR5 S0/1/0 * DCE 172.18.0.2 255.255.255.252 N/AR5 S0/1/1 * DCE 172.18.0.6 255.255.255.252 N/AS1 VLAN1 172.18.2.3 255.255.255.0 172.18.2.1S2 VLAN1 172.18.2.4 255.255.255.0 172.18.2.1S3 VLAN1 172.18.2.5 255.255.255.0 172.18.2.1S4 VLAN1 172.18.2.6 255.255.255.0 172.18.2.1S5 VLAN1 172.18.1.2 255.255.255.0 172.18.1.1PC1 172.18.23.10 255.255.255.0 172.18.23.1PC2 172.18.1.10 255.255.255.0 172.18.1.1PC3 172.18.1.11 255.255.255.0 172.18.1.1Web 1A 172.18.21.3 255.255.255.0 172.18.21.1Web 1B 172.18.21.4 255.255.255.0 172.18.21.2DNS A 172.18.22.3 255.255.255.0 172.18.22.1DNS B 172.18.22.4 255.255.255.0 172.18.22.2Web 2A 172.18.23.3 255.255.255.0 172.18.23.1Web 2B 172.18.23.4 255.255.255.0 172.18.23.2
  • 152. Figure 1: Topology - Prototype test topology.Add a description about this design here that is essential to provide a better understanding of thetesting or to emphasize any aspect of the test network to the reader.For each test to be performed state the goals of the test, the data to record during the test, and theestimated time to perform the test.Test 1. Description: Access Control Lists TestGoals of Test:The goal of the test is to verify that access control lists are properlyconfigured and applied to permit authorized traffic and to block unauthorizedtraffic.Data to Record:ConfigurationsRouter configurationsACL informationPing Test OutputWeb page access informationEstimated Time:120 minutes
  • 153. Test 1. Procedures:Itemize the procedures to follow to perform the test.Step 1: Verify full connectivity from all PCs to all servers.1. From PC1 and PC2 ping all of the servers in the topology. Record the results.2. From PC1 and PC2 access the following web pages: www.web1a.com, www.web1b.com,www.web2a.com, and www.web2b.com. Record the results.3. From PC2, ping the Fa0/1 interface of routers R1 and R2 to verify connectivity and then telnet torouters R1 and R2 and get the “show running-config” output. Copy and paste the results intoa document for later use.Step 2: Plan access control lists to prevent unauthorized access to the server farm.1. Design an access control list numbered 101 to allow only web access from hosts on the internalnetwork, 172.18.0.0/16, to any device and deny all other traffic. Design an access control listnumbered 102 to allow only DNS access from hosts on the internal network, 172.18.0.0/16, to anydevice and deny all other traffic.Step 3: Configure and apply access control lists.1. Telnet to routers R1 and R2 and add both access control lists and apply them on to the properinterfaces in the proper direction to protect the servers connected to that interface.Step 4: Verify proper operation of the access control lists.1. From PC1 and PC2 ping all of the servers in the topology. Record the results.2. From PC1 and PC2 access the following web pages: www.web1a.com, www.web1b.com,www.web2a.com, and www.web2b.com. Record the results.3. Telnet to routers R1 and R2 and document the final cofiguration using “show running-config”, and “show access-lists”.Test 1. Expected Results and Success Criteria:List all of the expected results. Specific criteria that must be met for the test to be considered asuccess should be listed. An example of specific criteria is: “A requirement that ping responsetimes cannot exceed 100 ms.”1. Prior to configuring access control lists both PCs can ping all servers and access all web pages.2. After configuring access control lists, PC2, representing a legitimate inside user, can not ping anyserver but can access all web pages.3. After configuring access control lists, PC1, representing a PC set up to maintain switchconfigurations, can ping servers in its own VLAN, can not ping other servers, and can not accessany web pages.
  • 154. 4. Test 1. Results and ConclusionsRecord the results of the tests and the conclusions that can be drawn from the results.
  • 155. AppendixRecord the starting configurations, any modifications, log file or command output, and any otherrelevant documentation.
  • 156. AppendixRecord the starting configurations, any modifications, log file or command output, and any otherrelevant documentation.
  • 157. CCNA DiscoveryDesigning and Supporting Computer Networks7.3.4 Testing ACLsObjectiveDevelop methodologies for comparing devices and topologies.Background / PreparationThe purpose of this test plan is to add ACLs to the prototype network to secure unauthorized access to theserver farm and to demonstrate that the ACLs are configured correctly. Download and complete the StadiumACL Test Plan (Testing ACLs) document.Required files: Testing ACLs.pka and Stadium ACL Test Plan (Testing ACLs).Step 1: Verify full connectivity from all PCs to all servers.Step 2: Plan ACLs to prevent unauthorized access to the server farm.Step 3: Configure and apply ACLs.Step 4: Verify proper operation of the ACLs.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 1
  • 158. CCNA DiscoveryDesigning and Supporting Computer Networks: Prototyping the WAN8.1.2 Configuring a WAN Connection Using PPPObjectives• Simulate WAN connections• Demonstrate the benefits of using simulation software• Explore the effects of implementing new devices in a network topology• Use simulation software to test new configurationsBackground / PreparationThe XYZ Corporation is planning to expand soon. They are planning to open a new branch office that will connectto the main company network through the ISP. This will require router R0 in the existing network to be upgradedand new equipment be purchased and configured. They would also like to add some wireless connectivity to theexisting network. And finally, they wish to set up some basic security through using access control lists (ACLs).The network administrator has provided you with a simulated model of the current network and a diagram of thenew expanded network. You have been asked to modify the existing simulation to verify that the new devices andconfigurations will work as planned prior to purchasing new equipment and making changes to the live network.Required file: Configuring a WAN Connection Using PPP.pkaTask 1Step 1: Upgrade the WAN interfaces on router R0a. Remove the NM-4A/S WAN moduleb. Add a WIC-2T module in Slot0c. Add a WIC-2T module in Slot1All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 4
  • 159. CCNA DiscoveryDesigning and Supporting Computer NetworksStep 2: Reconnect WAN links on router R0a. Connect R0 S0/0/0 to R2 S0/0/1 (DCE)b. Connect R0 S0/0/1 (DCE) to R3 S0/0/1Step 3: Reconfigure WAN links on router R0a. Configure interface S0/0/0 with the following:• IP address 172.16.3.6/30• Encapsulation PPPb. Configure interface S0/0/1 with the following:• IP address 172.16.3.9/30• Encapsulation PPP• Clock rate 64000c. Configure a default static route using S0/1/0 as the exit interfaceStep 4: Test network connectivitya. Use the command prompt on PC0 to ping the Web Server and all other PCsb. Troubleshoot if neededTask 2Step 1: Set up additional devices for new branch networka. Add a new 2811 router between the ISP and Switch5b. Add a WIC-2T module in Slot0c. Connect S0/0/0 on the new router to ISP S0/0/1 (DCE)d. Connect Fa0/0 on the new router to Switch5 Fa0/24Step 2: Connect the existing network to the ISPa. Connect router R0 S0/1/0 to ISP S0/0/0 (DCE)b. Configure interface S0/1/0 on R0 with the following:• IP address 10.1.1.2/30Step 3: Configure the new routera. Use the Config tab for the new router to change the display name to R5b. Configure the hostname as R5d. Configure interface S0/0/0 with the following:• IP address 10.1.1.6/30e. Configure interface Fa0/0 with the following:• IP address 192.168.6.1/24f. Configure a default static route using S0/0/0 as the exit interfaceStep 4: Test network connectivitya. Use a Simple PDU to send icmp packets from ISP to R5b. Use a Simple PDU to send icmp packets from ISP to PC5c. Use a Simple PDU to send icmp packets from ISP to R0d. Use a Simple PDU to send icmp packets from PC5 to R0e. Use a Simple PDU to send icmp packets from PC5 to PC0 (repeat if fails)f. Use a Simple PDU to send icmp packets from PC5 to PC1 (repeat if fails)g. Use a Simple PDU to send icmp packets from PC5 to PC2 (repeat if fails)h. Use a Simple PDU to send icmp packets from PC5 to PC3 (repeat if fails)i. Troubleshoot if neededTask 3Step 1: Set up additional devices for new wireless networka. Add a Linksys-WRT300N wireless router below router R3b. Connect the Internet port on the Linksys device to R3 F0/1 (be careful about which type of cable you use)All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 4
  • 160. CCNA DiscoveryDesigning and Supporting Computer NetworksStep 2: Configure the new wireless networka. On router R3 configure interface Fa0/1 with the following:• IP address 192.168.7.1/24b. On the wireless router configure the following:• Change the display name to Wireless_Router4• Configure the Internet interface with the a Default Gateway of 192.168.7.1 and an IP address of192.168.7.2/24• Configure the LAN interface with the IP address of 192.168.5.1/24Step 3: Test network connectivitya. Use a Simple PDU to send icmp packets from PC4 to the wireless router (repeat if fails)b. Use a Simple PDU to send icmp packets from PC4 to R3 (repeat if fails)c. Use a Simple PDU to send icmp packets from PC4 to PC0 (repeat if fails)d. Use a Simple PDU to send icmp packets from PC4 to PC1 (repeat if fails)e. Use a Simple PDU to send icmp packets from PC4 to PC2 (repeat if fails)f. Use a Simple PDU to send icmp packets from PC4 to PC3 (repeat if fails)g. Use a Simple PDU to send icmp packets from PC4 to PC5 (repeat if fails)Task 4Company XYZ wishes to set up some basic security through using access control lists (ACLs). The ACL shouldpermit all www traffic to the Web Server. Permit any return traffic that originated in the 192.168.3.0 network. Allowthe ICMP protocol to receive echo replies and unreachable messages. The ACL should deny all other traffic.Step 1: Set up basic security using access control lists (ACLs)a. Add the following ACL to router R2• access-list 100 permit tcp any 192.168.3.250 eq 80• access-list 100 permit tcp any any established• access-list 100 permit icmp any any echo-reply• access-list 100 permit icmp any any unreachable• access-list 100 deny ip any anyb. Apply the ACL to interface Fa0/0 on router R2Step 2: Test network connectivitya. Verify that traffic originating from outside the 192.168.3.0 network is denied• Use a Simple PDU to send icmp packets to PC2 from PC0 (should fail)• Use a Simple PDU to send icmp packets to PC2 from PC1 (should fail)• Use a Simple PDU to send icmp packets to PC2 from PC3 (should fail)• Use a Simple PDU to send icmp packets to PC2 from PC4 (should fail)• Use a Simple PDU to send icmp packets to PC2 from PC5 (should fail)b. Verify that traffic originating from inside the 192.168.3.0 network is permitted• Use a Simple PDU to send icmp packets from PC2 to PC0 (should be successful)• Use a Simple PDU to send icmp packets from PC2 to PC1 (should be successful)• Use a Simple PDU to send icmp packets from PC2 to PC3 (should be successful)• Use a Simple PDU to send icmp packets from PC2 to PC4 (should be successful)• Use a Simple PDU to send icmp packets from PC2 to PC5 (should be successful)c. Verify that all www traffic is permitted to the Web Server• On PC0, open the Web Browser and type 192.168.3.250 in as the URL (should display the serverweb page)• On PC1, open the Web Browser and type 192.168.3.250 in as the URL (should display the serverweb page)• On PC2, open the Web Browser and type 192.168.3.250 in as the URL (should display the serverweb page)• On PC3, open the Web Browser and type 192.168.3.250 in as the URL (should display the serverweb page)All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 3 of 4
  • 161. CCNA DiscoveryDesigning and Supporting Computer Networks• On PC4, open the Web Browser and type 192.168.3.250 in as the URL (should display the serverweb page)• On PC5, open the Web Browser and type 192.168.3.250 in as the URL (should display the serverweb page)d. Troubleshoot if neededStep 3: Verify completion of all tasksa. Click on Check Results to verify that all tasks have been completedReflection1. How could using simulation software such as Packet Tracer be beneficial to network personnel?____________________________________________________________________________________________________________________________________________________________________________________________2. What are some limitations to using simulation software such as Packet Tracer?______________________________________________________________________________________________All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 4 of 4
  • 162. 8.2.5.4 Stadium Redundancy Test PlanStart Date End DateNetwork Build (Setup)Testing Date
  • 163. Table of ContentsATTENDEES ...................................................................................................................3INTRODUCTION .............................................................................................................4EQUIPMENT....................................................................................................................5DESIGN AND TOPOLOGY DIAGRAM ...........................................................................6TEST 1. DESCRIPTION: FRAME RELAY CONNECTIVITY TEST.................................8TEST 1. RESULTS AND CONCLUSIONS......................................................................9TEST 2. DESCRIPTION: FLOATING STATIC ROUTES CONFIGURATION TEST.....10TEST 2. RESULTS AND CONCLUSIONS....................................................................11TEST 3. DESCRIPTION: LINK FAILURE TEST ..........................................................12TEST 3. RESULTS AND CONCLUSIONS....................................................................13APPENDIX.....................................................................................................................14
  • 164. AttendeesName Company PositionNetworkingCompany Account ManagerNetworkingCompany Network DesignerNetworkingCompany System EngineerInstructor note: Students can enter their own names in the roles they choose, or make up names for theattendees.
  • 165. IntroductionAn introduction to the testing explaining briefly what the purpose of the test is, and what shouldbe observed. Include a brief description of testing goals. List all tests you intend to run.Purpose of this test:Tests to run:• Test 1: Frame Relay Connectivity Test• Verify physical and IP connectivity between Edge2 and BR3 on the prototype network.• Document operation.• Test 2: Floating Static Route Configuration Test• Demonstrate backup route interface configuration.• Verify connectivity through backup route.• Demonstrate backup static route configuration.• Verify routing priority• Test 3: Link Failure Test• Demonstrate routing of traffic between separate Edge2 and BR3 with Frame network active.• Demonstrate routing of traffic after Frame network is inactive.• Demonstrate routing of traffic after Frame network is reactivated.• Document operation.
  • 166. EquipmentList all of the equipment needed to perform the tests. Be sure to include cables, optionalconnectors or components, and software.Qty. Req Model Any additionaloptions orsoftware requiredSubstitute IOS SoftwareRev.1 PersonalComputer end-devicesFastEthernetNICAt least onePC and anyother IP end-device(camera,printer, etc.)Windows,MAC or Linuxoperatingsystem.
  • 167. Design and Topology DiagramPlace a copy of the prototype network topology in this section. This is the network as it should bebuilt to be able to perform the required tests, including IP Addressing and DLCI information. Ifthis topology duplicates a section of the actual network, include a reference topology showing thelocation within the existing or planned network. Initial configurations for each device must beincluded in the Appendix.Figure 1: Topology - Prototype test topology.IP Address Plan:Device Name Interface IP Address Subnet Mask DLCIEdge2 Serial 0/1/1 172.18.0.9 255.255.255.252 110Edge2 Fa 0/1 172.18.0.249 255.255.255.252BR3 Serial 0/1/0 172.18.0.10 255.255.255.252 100BR3 Fa 0/0 172.18.225.249 255.255.255.252BR3 Fa0/1 172.18.225.1 255.255.255.128ISPX Fa0/0 172.18.225.250 255.255.255.252ISPX Fa0/1 172.18.0.250 255.255.255.252
  • 168. Additional Notes and Instructions:Instructor note: Student records any other information that they think might be useful to the techniciansperforming the tests. These might be things like: This test must show the routes automatically changingfor link states.Add a description about this design here that is essential to provide a better understanding of thetesting or to emphasize any aspect of the test network to the reader.__________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
  • 169. For each test to be performed state the goals of the test, the data to record during the test, and theestimated time to perform the test. Test 1 is given as an example.Test 1. Description: Frame Relay Connectivity TestGoals of Test:The goal of the baseline is to verify that the Frame Relay network is up and running with theproper protocols and features.Data to Record:ConfigurationsInterface statusRouting TablesCPU & MemoryPing Test OutputEstimated Time:45 minutes total30 minutes build15 minutes testTest 1. Procedures:Itemize the procedures to follow to perform the test.1. Build the topology according to the diagram shown in Figure 1 without Ethernet backup link.Assign IP addresses according to the IP address plan. To configure the serial connectionsthrough the Frame Relay network, you will need to change the encapsulation type to frame relay.Then use the frame-relay map ip command to identify what circuit needs to be used to reachthe distant IP address. Lastly, turn on the interface. For example, on the Edge2 router, you needto enter:Edge2(config)#interface Serial 0/1/1Edge2(config)#encapsulation frame-relayEdge2(config-if)#frame-relay map ip 172.18.0.10 100 broadcastEdge2(config-if)#no shutdownNotice that you are using the BR3 Serial 0/1/0 address and connecting it to the local 100 DLCI.The ‘broadcast’ will allow EIGRP multicast updates to use the link as well. The BR3 router Serial0/1/0 will need to be configured in a like manner.2. Create a basic configuration on each device. Include applicable passwords, device names,default routes, default gateways, and activate interfaces.3. Console into one of the devices in the topology and ping all of the other devices in the topology.Record any anomalies.4. Telnet to each device in the configuration and verify that each is reachable.
  • 170. 5. Start a log file and get the “show running-config”, “show ip route”, “show processescpu sorted”, “show interfaces” and the first few lines of “show memory” . Save the log filefor later analysis. Repeat for all devices in the topology.Test 1. Expected Results and Success Criteria:List all of the expected results. Specific criteria that must be met for the test to be considered asuccess should be listed.1. All networking devices, except ISPX, are connected and accessible through Telnet.2. Hosts can ping successfully to other hosts, except ISPX on the network.Test 1. Results and ConclusionsRecord the results of the tests and the conclusions that can be drawn from the results.
  • 171. Test 2. Description: Floating Static Routes Configuration TestInstructor note: Students must fill in the goal of the test. Sample goal: Verify routing tables includefloating static route.Goals of Test:Data to Record:Routing tablesCPU & MemoryPing Test OutputEstimated Time:30 minutes total15 minutes configure15 minutes testTest 2. Procedures:Itemize the procedures to follow to perform the test.______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
  • 172. Test 2. Expected Results and Success Criteria:List all of the expected results. Specific criteria that must be met for the test to be considered asuccess should be listed.1. _________________________________________________________________________2. _________________________________________________________________________3. __________________________________________________________________________.Test 2. Results and ConclusionsRecord the results of the tests and the conclusions that can be drawn from the results.
  • 173. Test 3. Description: Link Failure TestGoals of Test:Data to Record:Router ConfigurationIP Routing Table InformationCPU & MemoryPing Test OutputEstimated Time:20 minutes total10 minutes configure10 minutes testTest 3. Procedures:Itemize the procedures to follow to perform the test.______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________
  • 174. Test 3. Expected Results and Success Criteria:List all of the expected results. Specific criteria that must be met for the test to be considered asuccess should be listed.1. _________________________________________________________________________2. _________________________________________________________________________3. __________________________________________________________________________Test 3. Results and ConclusionsRecord the results of the tests and the conclusions that can be drawn from the results.
  • 175. AppendixRecord the starting configurations, any modifications, log file or command output, and any otherrelevant documentation.
  • 176. CCNA DiscoveryDesigning and Supporting Computer Networks: Prototyping the WAN8.2.5 Testing Design RedundancyObjectives• Using the test plan, configure the backup links and verify the failover works as expected.Background / PreparationIn this exercise, you will configure a Frame Relay network and a backup link. Once the network is built andconfigured, you can perform a Frame Relay Connectivity Test, Floating Static Routes Configuration Test and aLink Failure Test specified in the designer’s test plan. Download and complete the Redundancy Test Plandocument in addition to the PT activity.Required files: Testing Design Redundancy.pka and Redundancy Test PlanTest 1 Frame Relay Connectivity Test• Configure Edge2 and BR3 hostnames and LAN connection to Switch0. Use the address table in theRedundancy Test Plan. To configure the serial connections through the Frame Relay network, you will needto change the encapsulation type to frame relay. Then use the frame-relay map ip command to identify whatcircuit needs to be used to reach the distant IP address. Lastly, turn on the interface. For example, on theEdge2 router, you need to enter:Edge2(config)#interface Serial 0/1/1Edge2(config)#encapsulation frame-relayEdge2(config-if)#frame-relay map ip 172.18.0.10 100 broadcastEdge2(config-if)#no shutdownNotice that you are using the BR3 Serial 0/1/0 address and connecting it to the local 100 DLCI. The‘broadcast’ will allow EIGRP multicast updates to use the link as well. The BR3 router Serial 0/1/0 will need tobe configured in a like manner.• Configure EIGRP (AS 1) on Edge2 and BR3. Advertise only the networks connected to the FrameCloud andSwitch0. On BR3, do not send advertisements out fa0/1.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 1 of 2
  • 177. CCNA DiscoveryDesigning and Supporting Computer NetworksTest 2 Floating Static Routes Configuration Test• On Edge2, configure fa0/1 using the addressing given in the Test Plan.• On Edge2, configure floating static routes (AD=130) to 172.18.225.0/25 and 172.18.225.248/30 throughthe back-up network using the local interface argument.• On BR3, configure fa0/0 using the addressing given in the Test Plan.• On BR3, configure a floating default route (AD=130) through fa0/0.Test 3 Link Failure Test• On Edge2, shutdown interface s0/1/1 and wait a few seconds.• From Edge2, ping 172.18.225.1. Troubleshoot until it is successful.• On Edge2, turn interface s0/1/1 back on and wait a few seconds.• From Edge2, ping 172.18.225.1. Ensure the path is back through the Frame network.All contents are Copyright © 1992–2007 Cisco Systems, Inc. All rights reserved. This document is Cisco Public Information. Page 2 of 2