Case Study Routing & Switching Cisco Networking Academy Routing and Switching: Scaling Network Case Study
Overview and Objectives This case study allows students to build and configure a complex network using skills gained throughout the course. This case study is not a trivial task. To complete it as outlined with all required documentation will be a significant accomplishment. The case study scenario describes the project in general terms, and will explain why the network is being built. Following the scenario, the project is broken into a number of phases, each of which has a detailed list of requirements. It is important to read and understand each requirement to make sure that the project is completed accurately. The following tasks are required to complete this case study: Set up the physical layout of the network using the diagram and accompanying narrative Correctly configure multi-area OSPF with MD5 authentication Correctly configure VLANs and 802.1q trunking Correctly configure STP Correctly configure VTP Correctly configure Etherchannel when required Correctly configure HSRP Correctly configure DHCP Correctly configure NAT Create and apply access control lists (ACL S) on the appropriate routers and interfaces Verify/test and document, all devices must operational and functioning according to the scenario guidelines Provide detailed documentation in a prescribed form as listed in the deliverables sections
Scenario Galway S0/0 OSPF 10 Area 1 ISP Server 209.1.1.2/30 G0/1 209.1.1.1/30 200 200 Hosts Hosts S0/0 DCE 10.0.0.2/30 10.0.0.1/30 ISP ISP 10.0.0.6/30 10.0.0.5/30 Nat Outside 200.10.10.64/26 Nat Inside 172.16.0.0/20 Cork 100 Hosts S0/1 OSPF 10 area 0 S0/1 DCE Belfast VLANs 900 hosts (total) Belfast2 G0/1 S2 G0/1 Etherchannel VLAN 3 Etherchannel S3 VLAN 4 Belfast1 HSRP S1 Etherchannel G0/1 G0/1 S0/0 Limerick 200 hosts A company needs a network to be designed and implemented; the company has locations in four cities. All of the locations will be connected using leased-line serial links. The company has previously used RIP version 2; however, all four locations will use OSPF routing process. Also, default static route must be used to access the internet. One location, Belfast, has a large and complex LAN. Due to the size and complexity, the company wants to create VLANs to control broadcasts, enhance security, and logically group users. The company also wants to use private addresses throughout the Autonomous System, DHCP over most of the LAN segments, and NAT implemented for Internet connectivity. The company also wishes to limit Internet access to Web traffic while allowing multiple protocols (not all) within its own WAN. Although private addresses (RFC 1918) will be used, the company appreciates efficiency and address conservation in design. To minimize wasted address space, they have requested VLSM to be used when appropriate. You will build and troubleshoot this design (Prototype), first in Packet Tracer, and then using lab equipment when presenting your design on the assigned date.
Phase 1: Addressing the WAN & LAN Use the following instructions to complete Phase 1: Use 172.16.0.0/20 for internal addressing with IP subnet zero enabled. Apply /30 subnets on all serial interfaces, using the last available subnet. Assign an appropriately sized subnet for the Belfast LAN, which has about 900 devices: 1. VLAN 99: 40 devices (Management VLAN) 2. VLAN 2: 120 hosts 3. VLAN 3: 250 hosts 4. VLAN 4: 500 hosts Assign the appropriately sized subnet to the Limerick LAN, which has 200 hosts. Assign an appropriately sized subnet for the Galway s 2 LANs, which have 400 devices. Assign the appropriately sized subnet to the Cork LAN, which has 100 hosts Document all of the addressing in tables. Phase 2: Configuring Default Routes, OSPF Routing and HSRP Use the following instructions to complete Phase 2: Configure each router with a hostname and required passwords. Configure each interface on all routers documented in Phase 1. Configure Multi-area OSPF on Routers (Galway, Cork, Limerick, and Belfast). Configure a summary (type 3) for area 1. Configure a Default on Belfast and redistribute the route into the OSPF process. Configure MD5 authentication between OSPF routers across all WAN links Adjust the Hello timer to 40 sec and Dead timers to 160 sec on the link between Cork and Galway Verify that the Limerick, Belfast, Galway, and Cork routers have connectivity through Layers 1-7. Provide the ability to dynamically recover from the failure of a device acting as a default gateway to ISP. Use first-hop redundancy protocol (HSRP) to provide the mechanism. Also allow for load balancing across the two Internet connections. Phase 3: Configuring VLANs Use the following instructions to complete Phase 3: 1. Apply the basic switch configuration Hostname, MOTD and passwords 2. Configure PVST+ on 3 switches, switch 1 and 2 must be able to do load balancing S1 is the root bridge for VLAN 4, S2 is the backup root bridge for mentioned VLAN. S2 is the root bridge for VLANs 2 and 3, S1 is the backup root bridge for mentioned VLANs 3. VTP must be used to propagate VLAN information to other client switches
VTP domain name: CCNA3, password: Ca$e$tudy3 Using VTP, create and name three Data VLANs and one Management VLAN on VTP server: o VLAN 99: Management (Native) o VLAN 2: HR o VLAN 3: R&D o VLAN 4: Production. 4. Configure switches S1, S2 and S3; assign: Gigabit ports 1-4 as trunks (802.1Q) Configure Etherchannel when appropriate. 5. Configure the Belfast s LAN (2 routers and 3 switches) as follows: 6. Configure access layer switch S3; assign: Port 6 to VLAN 99 Ports 7-10 to VLAN 2 Ports 11-14 to VLAN 3 Ports 14-20 to VLAN 4 Disable all unused ports Connect G0/1 of the Belfast s 2 routers to G0/1 of S1 and S2 o Configure the appropriate number of sub-interfaces o Associate each sub-interface with a VLAN o Assign sub-interfaces the appropriate IP addresses Configure other router interfaces as shown in the diagram Connect one workstation per VLAN Phase 4: Configuring ACLs Use the following instructions to complete Phase 4: 1. Configure an Extended ACL On the Belfast Routers. The ACL should: Allow IP traffic for TCP and ICMP sessions originating from the inside (established sessions) while denying IP traffic for sessions originating outside the network. 2. Use an ACL to control VTY access to routers ACL to permit Administrators from VLAN 99 VTY access to all routers. Phase 5: Configuring DHCP DHCP Services Configure DHCP services on the Cork router. DHCP should provide services to the following LANs hosts: Belfast s VLAN 2, VLAN 3 and VLAN 4 DHCP should pass the following parameters to the hosts:
IP address and Subnet Mask Default Gateway DNS address (10.0.0.4) The Cork router will perform the DHCP services. Configure Cork using the DHCP pools documented in Phase 1. Configure DHCP services on the Cork router as follows: Phase 6: NAT FG0/1 s sub-interfaces with the first useable address. Exclude the first 10 IP addresses from each pool (to be used for printers and servers) Configure Workstations to obtain its IP address automatically. Have one host connected to on Cork and one host per VLAN connected to VLANs 2-4 on the Belfast s access layer switch. Use the following instructions to complete Phase 6: 1. The Belfast s (2) routers will perform NAT. Configure the routers as follows: Define the NAT pool. The pool consists of public network address 200.10.10.64/26. Exclude first 10 addresses from this pool (to be use for servers, when required). Define an access control list, which will translate for all internal (172.16.0.0/20) addresses, and deny all other traffic. Establish dynamic source translation, specifying the NAT pool and the ACL defined in the previous steps. Specify the inside and the outside NAT interfaces. Change the default NAT timeout value to 120 seconds. Document NAT configuration in a chart; it will serve as the deliverable item for Phase 6. 2. Connect a Server to the ISP s port to simulate an ISP server. Configure this Server as follows: Configure the IP address and subnet mask as 209.1.1.2/8. Configure the default gateway to be 209.1.1.1. 3. Configure the server to act as a web server. enable a simple web page that will tell users that they have reached the ISP. Phase 7: Verification and Testing Use the following instructions to complete Phase 7: 1. Verify communication between various hosts in the network. Troubleshoot and fix any problems in the network until it works properly. Document the results of the tests in a table. 2. Capture and save the router configuration files for all four routers. Edit the text files, and include comments at the top of each file documenting the following: Your name
The date CCNA3 Case Study Final Router Configuration The router name that corresponds to each file.
Case Study Deliverables Once the case study problem has been solved, the network has been successfully designed and the prototype implemented and tested, a final report must be provided to your instructor. This report will include thorough and wellorganized documentation of the process. It is highly recommended that all tables be completed using a spreadsheet program such as Microsoft Excel. Cisco Network Designer, Visio or a paint program can be used for the network diagrams. Some of these tables and outputs should be used in your power point presentation The following items must be included in the final report and presentation: Outline Summary of the Company and Network Requirements Discussion on the implementation of IP address and VLSM Discussion on the implementation of Routing Discussion on the implementation of VLANs, STP, and switches Discussion on the physical layer design and equipment Discussion on testing and verification strategies Recommendations for future network upgrades Logical Diagram Physical Diagram IP Addressing Table Equipment Table including quantity, make and model (Routers & Switches ONLY) Show Commands outputs to verify connectivity: show ip route, show ip ospf neighbors, show spanning-tree, show vlan, ping, telnet, etc. Router Configurations Switch Configuration The documentation should be complete and should contain enough information to allow a third party to properly install, configure and troubleshoot the network without requesting additional information.