Ccna4 Accessing The WAN Guided Case Study
Ccna4 Accessing The WAN Guided Case Study
Ccna4 Accessing The WAN Guided Case Study
(Case Study)
CCNA4
Student:
483986223.doc Page 1 / 15
CCNA4:
(Case Study)
This final 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 the case study:
Design the network using the diagram and accompanying
narrative.
Simulate and test the network using the network simulator tool
Packet Tracer.
Correctly configure single-area OSPF
Correctly configure VLANs and 802.1q trunking
Correctly configure DHCP
Correctly configure NAT and PAT
Create and apply access control lists on the appropriate routers
and interfaces
Verify that all configurations are operational and functioning according to
the scenario guidelines
Provide documentation and configuration files as detailed in the
following sections.
483986223.doc Page 2 / 15
CCNA4:
(Case Study)
Scenario
DNS Server HQ 200.1.1.1/24
198.198.1.2/24 (Exeter) 200.1.1.2/24
Interne
t ISP
Web Site
example.com
S1 210.1.1.2/24
DCE
PPP
DSW0
ASW1
ASW0
Sales
Call Centre Engineering (Bournemouth)
(Plymouth) (Poole)
IT Support
Accounts Personnel Accounts Personnel
Server Server
General
Server
OSPF Area 0
Engineering
Server
The regional electrical utility company, South West Electrical, needs a network to be designed and
implemented. The company supplies electricity over a wide area. Its headquarters is in Exeter with a call-
centre in Plymouth connected via leased line. The Engineering division operates out of Poole whilst the
Sales team have a Sales Office in Bournemouth. The Bournemouth and Poole branches are connected
to the company’s headquarters in Exeter using Ethernet because of cost considerations. The company’s
networks communicate using the open standard routing protocol OSPF.
The company wants to use private addresses throughout for security reasons and DHCP for the LANs.
Access to the Internet is provided from Exeter using network address translation. The company also
wishes to limit Internet access to Web traffic while allowing multiple protocols within its own WAN. A set
of servers are provided at the company’s headquarters in Exeter although the Engineering division has it
own server connected to its own network. Due to the size and complexity, the company wants to create
VLANs to control broadcasts, enhance security, and logically group users.
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.
483986223.doc Page 3 / 15
CCNA4:
(Case Study)
Requirements
The company has 6 departments / divisions – Personnel, Accounts, Engineering, Sales,
Customer Services and IT Support. The offsite sales team are provided with wireless laptops for
access to the sales network via the Bournemouth branch. Your design must provide for
4 employees in the Personnel department.
5 employees in the Accounts department.
30 employees in the Engineering division at Poole
50 wired workstations for Customer Services at Plymouth.
50 laptops for external mobile Sales staff for access via Bournemouth office.
5 employees (maximum) in IT Support with direct access at Exeter.
Lifetime max of two servers for Accounts and Personnel and two General Servers for all
departments and divisions.
Expect 100% growth of current IP requirements when determining size of subnets.
All networking devices must have IP addresses.
Use the private class B 172.XX.0.0 network for internal addressing throughout the
company’s WAN and LAN networks.
XX = 16 for Carlo Capule
XX = 17 for Claire Lois Debatian
XX = 18 for Lance Tecson
XX = 19 for Patrice Alaba
XX = 20 for Juan Philip Bermudo
XX = 21 for Juan Lanz Romero
XX = 20 for Group 7
XX = 21 for Group 8
483986223.doc Page 4 / 15
CCNA4:
(Case Study)
Apply /30 subnets on all serial interfaces, using the last available subnets.
Define router and switch names
Design a redundant switched network with spanning-tree to elect the root bridge.
Define VLANs, names and their network addresses.
Design for the propagation of VLANs with VTP.
All network addresses.
Number of hosts per network.
Link Speeds.
Design to secure the ports on the switches using port security.
The next few sections have example grids for documenting this information.
2. The company expects the use of VLSM Design to maximize the use of IP addresses. A table is to be
produced showing the subnets that meet the Companies requirements using a VLSM design.
A sample table layout for recording the VLSM design is below. Include all VLANs and WANs.
Network Name VLAN Number of host Network Address Subnet Mask Max Number Gateway Address
addresses of Hosts
required Possible
483986223.doc Page 5 / 15
CCNA4:
(Case Study)
483986223.doc Page 6 / 15
CCNA4:
(Case Study)
3. For each device, a set of tables is required. These will assist with design and development activities
and used when configuring switches and routers. A separate table should be created for each router
and switch.
Below is a sample layout for routers. Reproduce this for each of the four routers and one for the ISP router.
483986223.doc Page 7 / 15
CCNA4:
(Case Study)
Router Name: ISP
Network Description and Interface/Sub Network Interface IP Subnet Mask
Name Purpose Interface Address Address
Type/Number
Router Name: HQ
Network Description and Interface/Sub VLAN Network Interface IP Subnet
Name Purpose Interface Address Address Mask
Type/Number
Port 0 (Wired)
Port 1
(Wireless)
483986223.doc Page 8 / 15
CCNA4:
(Case Study)
There are three switches with the distribution switch connected to the router. All switches are interconnected
via two trunk links for robustness. Below is the sample layout for the tables for the switches.
Distribution Switch Name:
Switch IP address: VLAN:
483986223.doc Page 9 / 15
CCNA4:
(Case Study)
4. Complete the IP design, assign and tabulate PC/workstation and server addresses for each LAN in each
location.
Configure DHCP on the routers to allocate address dynamically with reserved address groups for the servers
and switches.
For demonstration purposes, the company agrees that it is enough to implement a single representative
example of a server for each VLAN and a PC/workstation for each department/division. Stackable
switches may be needed to accommodate the requirements for the full implementation.
The tables and supporting text will be part of the documentation delivered to the company.
Before you commence with the implementation the logical diagram and tables need to be approved by the
company.
For this Case Study, implement your design in phases with Packet Tracer and check out any particular
aspects not supported by Packet Tracer with the equipment.
483986223.doc Page 10 / 15
CCNA4:
(Case Study)
Using Packet Tracer, create and connect two access switches, one distribution switch, and the HQ router.
When these are communicating, connect the servers and PCs together to form a redundant switched
network connected to the HQ router.
Steps
1. Configure Switches
1.1 Name the switches
1.2 On all switches, configure a login password as cisco, an encrypted privileged password as
class, and provide secure telnet login capability. All passwords should be encrypted.
1.3 Assign single ports as access ports with port security for each VLAN on both access switches.
1.4 Create trunk ports assigning the management VLAN as the native VLAN.
1.5 Configure VTP on all switches with version 2, domain to SWElectrical and password cisco with
the distribution switch in server mode and the access switches in client mode.
1.6 Create the VLANs as in your design for Personnel, Accounts and another for the General Server
on the distribution switch and propagate with VTP.
1.7 Create a Management VLAN for the switches.
1.8 Connect the IT Management PC and assign a static IP address.
Tests
3. Can the ITManagement PC ping all the switches, PCs and servers? [Y/N]
483986223.doc Page 11 / 15
CCNA4:
(Case Study)
Steps
1 Configure the WAN link between the HQ router and the Plymouth router.
1.1 Connect the routers using dedicated serial WAN link at 64Kbps.
1.2 Assign IP addresses to the serial ports on the link.
1.3 Configure ppp encapsulation between HQ router and Plymouth
1.4 Configure chap authentication with password cisco.
2 Configure Ethernet between the HQ router and the routers at Poole and Bournemouth.
3 Configure the Poole and Bournemouth LANs.
4 Configure a wireless access point with SSID SWElectrical and WEP key 0123456789 on the
Bournemouth LAN and a wireless PC.
5 Add OSPF area 0 routing protocol to the HQ, Plymouth, Poole and Bournemouth routers.
6 Provide a website over the Internet link for browsing from any PC.
6.1 Provide a default route from the HQ to the ISP and static route from the ISP to the company HQ.
1.1 Create a DNS server at 198.198.1.2 connected to the HQ router on an Ethernet port.
6.2 Setup the appropriate services for browsing to the website example.com at the ISP.
6.3 Propagate the default route within OSPF.
Tests
1. Can the HQ router ping the Poole and Bournemouth routers? [Y/N]
2. Check the HQ routing table. Can the HQ router see the LANs of Plymouth, Poole and
Bournemouth? [Y/N]
3. Can the PCs on the LANs of Poole and Bournemouth reach the servers on the HQ LAN network?
[Y/N]
4. Can the IT Support PC reach the PC’s at Plymouth, Poole and Bournemouth? [Y/N]
Record the wireless access point configuration with the security settings.
Record the configurations of routers for (1) HQ, (2) Plymouth, (3) Poole, (4) Bournemouth.
483986223.doc Page 12 / 15
CCNA4:
(Case Study)
Steps
1 Configure NAT with overload to translate all communication from the company to the single IP address
199.199.199.1 with overload..
2 Configure Access Control Lists
2.1 Permit only http access for all networks to the Internet. Test all PCs can browse to the test
website, example.com, on the ISP server.
2.2 Create a firewall to only allow established communication i.e. replies for web pages into the
company’s network from example.com
2.3 Deny all other protocols to the Internet.
2.4 Permit all access from IT support throughout the company’s network.
2.5 Permit FTP and HTTP from workstations on subnetworks to their own servers. Additionally,
allow Finance workstations access to Personnel’s servers.
Tests
1. Can the Sales, Engineering, Call-Centre PCs browse to the ISP website? [Y/N]
2. Can Finance and Personnel and IT Support browse to the ISP website? [Y/N]
3. Can Finance reach Personnel’s server but not vice versa? [Y/N]
5. Can the PCs on the LANs all reach their own servers via with FTP? [Y/N]
Record the ACL configurations of routers for (1) HQ, (2) Plymouth, (3) Poole and (4) Bournemouth.
Record the routing tables of these routers.
Record the Network Address Translations.
Log all ACL activity.
483986223.doc Page 13 / 15
CCNA4:
(Case Study)
Record and log all ACL output and ping, browser and ping tests for future reference.
483986223.doc Page 14 / 15
CCNA4:
(Case Study)
Phase 6: Presentation
The final task in this case study is to deliver a 15-minute presentation using powerpoint or flash for
the visual presentation of the main features of the design decisions and recommendations. A formal
written report should also be provided that contains all of the design documents as well as all the
supporting worksheets (see case study deliverables). The document should be complete enough to
allow a third party to install and configure the network without any additional documents.
Phase 7: 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 well-organized 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.
The following items must be included in the final report:
Title Page
Outline
Summary of the Company and Network Requirements
Phase 1: Network Design
- Complete Logical Diagram
- VLSM Table
- Router Interface Table
- Switch Interface Table
- PC/Server Addressing Table
Phase 2: Configure Switched Network with VLANs linked to HQ Router
- VTP status for Distribution and Access Switches
- VLAN database for Access SW1 and SW2
- DHCP binding from HQ router
Phase 3: Configuring the WAN links and OSPF
- Routing table for all the routers
- Configuration files of HQ, Berlin, Monaco, Vienna, and Paris
- Show interface output for HQ, Berlin, Monaco, Vienna, and Paris
- PVC status in Berlin, Monaco, Vienna, Paris
Phase 4: Configuring NAT and PAT, and ACLs
- Translation table
- Access-list table
Phase 5: Verification and Testing
- test result
Recommendations for future network upgrades
Appendix
- Running configuration files for all the routers and switches
- Equipment specification
Softcopy of Packet Tracer simulation and document(pdf) for the case study –bring the file on
the deadline save it in CELERIO..
483986223.doc Page 15 / 15