Tecnologies de Xarxes D’Ordinadors

(CCNA)

CCNA 2: ROUTING AND SWITCHING ESSENTIALS

CASE STUDY
CCNA 2: Routing and Switching Essentials v5.0 Case Study

Overview and Objectives

This case study allows students to complete a network design, implementation, and
troubleshooting project using the skills gained in CCNA 2. Students will use the skills that have
already been developed to use, make and connect the proper cabling to the appropriate devices.

It is crucial to read and understand the tasks to make sure that all requirements are fulfilled.
Each task guides the student through the proper steps to ensure that the project is completed
properly.

This case study requires the student to accomplish the following tasks:

 Set up the physical layout of the network using the diagram and accompanying
narrative.
 Correctly configure the routers with a basic router configuration.
 Correctly configure the routing features that the design requirements describe.
 Correctly configure the switch with a basic switch configuration.
 Correctly configure the switching features that the design requirements describe.
 Correctly configure the Network Address Translation (NAT) needed to communicate
inside users to external Servers and external users to internal Servers.
 Correctly configure DHCP features to provide dynamic addressing.
 Correctly configure Access Control Lists (ACL) to filter some traffic.
 Troubleshoot and test the connectivity between all devices.
 Provide detailed documentation in a prescribed form, as listed in the deliverables
section.

2
CCNA 2: Routing and Switching Essentials v5.0 Case Study

Scenario and Phase 1: Project Description

200.200.200.0/24
Fa0/1
Public ISP .1
Domain Fa0/0 .2 External Server
HTTP/ FTP
1.1.1.0/24 200.200.200.100/24

Fa0/0 .1
Admin1 Admin2
Private Lo0 Lo1

Domain R2
OSPF Se0/1 DCE
PID 10 Se0/0
RIPv2
DCE
Se0/0 Se0/1
194.0.0.0/30 DCE
Se0/1
Se0/0
.1
R1 .2 R3
Fa0/0 Fa0/0

Fa0/1 Fa0/1
Fa0/2
SW1 Fa0/2 SW2 SW3
Fa0/3 Fa0/3 Fa0/7 Fa0/3

Internal Server (VLAN 20)

HTTP/ FTP
External IP: 1.1.1.100/24

Sales Sales Marketing

PC1 (VLAN 10) PC2 (VLAN 10) PC3

Figure 1: Case Study Scenario

LaSalle Telecom is a company that has several people responsible for designing and
implementing a new network for ABC Company. Many technicians are involved in the upgrading
process.

A technician is given the task to complete this design and implementation knowing that the final
network has the topology of the Figure 1.

After deploying the solution, it is important that any documentation explaining the purpose,
design, implementation or troubleshooting is recorded for further upgrade.

3
CCNA 2: Routing and Switching Essentials v5.0 Case Study

Phase 2: IP Addressing
The team leader assigns the technician to develop a prototype for the new internetwork.
Use the network address assigned along with the subnetting requirements, to subnet the
network. From the IP addressing scheme, assign IP addresses to the appropriate interfaces
on all devices in the internetwork.

Obtain approval of this phase of development from the team leader (Instructor) before
proceeding to Phase 3.

IP Addressing Requirements:

 IP address assigned: 172.16.0.0/16

 The waste of IP addresses have to be the minimum per network assigned
 Sales LAN (VLAN 10) will require 100 host IP addresses
 Servers LAN (VLAN 20) will require 30 host IP addresses
 Admin1 LAN will require 60 host IP addresses
 Admin2 LAN will require 60 host IP addresses
 Marketing LAN will require 100 host IP addresses
 Management VLAN for switches (VLAN 99) will require 10 hosts
 The link between R1 and R2 will require an IP address for each end of the link
 The link between R2 and R3 will require an IP address for each end of the link
 The IP addressing allocated has to allow summarize each routing domain separately

Fill in the chart below to document the final addressing scheme:

 Assign the last IP address available to end devices

 Assign the first IP address available to routers
 Figure 1 shows the IP addressing assigned to the Public Domain
o ISP
o External Server
o R2 External side
 The link between R1 and R3 has a 194.0.0.0/30 assigned

4
CCNA 2: Routing and Switching Essentials v5.0 Case Study

Addressing Table

Device Interface IP Address Subnet Mask Default Gateway

Fa0/0 N/A
Fa0/0.10 N/A
Fa0/0.20 N/A
R1
Fa0/0.99 N/A
Se0/0 N/A
Se0/1 194.0.0.1 255.255.255.252 N/A
Fa0/0 1.1.1.1 255.255.255.0 1.1.1.2
Se0/0 N/A
R2 Se0/1 N/A
Lo0 N/A
Lo1 N/A
Fa0/0 N/A
R3 Se0/0 194.0.0.2 255.255.255.252 N/A
Se0/1 N/A
VLAN 10
SW1 VLAN 20
VLAN 99
VLAN 10
SW2 VLAN 20
VLAN 99
Fa0/0 1.1.1.2 255.255.255.0 N/A
ISP
Fa0/1 200.200.200.1 255.255.255.0 N/A
PC1 NIC
PC2 NIC
Internal
NIC
Server
PC3 NIC
External
NIC 200.200.200.100 255.255.255.0 200.200.200.1
Server
Table 1: Addressing Table

Other information that the technician needs is presented below:

Port Assignments

Switch Ports Assignment Network

F0/1 - F0/2 802.1q Trunks (Native VLAN 99)
SW1 F0/3 - F0/6 VLAN 10 – Sales
Fa0/7 – Fa0/10 VLAN 20 – Servers
F0/1 - F0/2 802.1q Trunks (Native VLAN 99)
SW2 F0/3 - F0/6 VLAN 10 – Sales
Fa0/7 – Fa0/10 VLAN 20 – Servers
Table 2: Port Assignments Table

5
CCNA 2: Routing and Switching Essentials v5.0 Case Study

VLANs Information
VLAN VLAN Name
VLAN 99 (Native) Management
VLAN 10 Sales
VLAN 20 Servers
Table 3: VLANs Information Table

Phase 3: Basic Configuration Requirements

The technician is assigned to create a configuration that meets the following requirements:

1. Basic configuration for R1, R2 and R3.

a. Router name.
b. Passwords must have a minimum length of 10 characters and must be
encrypted
c. Local authentication on Console 0.
 The database contains a user named Admin01 with a password
admin01pass.
d. Only SSH access is permitted to VTY lines with a crypto key of 1024 bits.
 Username: adminSSHuser
 Password: adminSSHpass
 Domain name: CCNA2CS.com
e. Enable secret password: ciscoenpa55
f. Banner MOTD:
***************************
This is the <router_name> CLI.
***************************
g. Interfaces configuration.
 IP addressing and subnet masking according to Table 1
NOTE: Remember that R1’s Fa0/0 requires special attention (InterVLAN
Routing)
h. Descriptions in point-to-point interfaces:
Link <router1_name> - <router2_name>
i. Descriptions in LAN interfaces/subinterfaces:
LAN <LAN_name>
2. Basic configuration for ISP.
a. Passwords must have a minimum length of 10 characters.
b. Console 0 password: ciscoconpa55
c. Line VTY password: ciscovtypa55
d. Only Telnet access is permitted to VTY lines.
e. Enable secret password: ciscoenpa55

6
CCNA 2: Routing and Switching Essentials v5.0 Case Study

f. Banner MOTD:
***************************
This is the <router_name> CLI.
***************************
g. Interfaces configuration.
 IP addressing and subnet masking according to Table 1
h. Descriptions in LAN interfaces/subinterfaces:
LAN <LAN_name>
3. Basic configuration for SW1 and SW2.
a. Passwords must be encrypted.
b. Console 0 password: ciscoconpa55
c. Line VTY password: ciscovtypa55
d. Enable secret password: ciscoenpa55
e. Banner MOTD:
***************************
This is the <switch_name> CLI.
***************************
f. Configure SVIs (Switched Virtual Interfaces) according Table 1.
g. Configure the trunk port between SW1 and SW2 to allow access to VLAN 10, 20
and 99.
h. Configure switch ports assigned to VLANs according Table 2.
i. The Management VLAN has to be accessible from remote devices.
j. Packets can traverse between VLANs, inter-VLAN Routing.
k. Configure security on ports Fa0/3 of SW1 and SW2 and port Fa0/7 of SW2:

 Port Fa0/3 of SW1 and SW2 can learn 2 different MAC addresses
 Port Fa0/3 of SW1 learns the MAC of PC1 statically and the rest
dynamically. If the switch reboots for any reason, the end devices that
can be connected have to be the same.
 Port Fa0/3 of SW2 learns the MAC of PC2 statically and the rest
dynamically. If the switch reboots for any reason, the end devices that
can be connected have to be the same.
 Port Fa0/3 of SW1 and SW2 drops packets with unknown source
addresses until the number of secure MAC addresses drops below the
maximum value.
 Port Fa0/7 of SW2 can learn 3 different MAC addresses.
 Port Fa0/7 of SW2 learns the MAC of Internal Server statically and the
rest dynamically. If the switch reboots for any reason, the end devices
that can be connected have to be the same.

7
CCNA 2: Routing and Switching Essentials v5.0 Case Study

 Port F0/7 of SW2 drops packets with unknown source addresses until
the number of secure MAC addresses drops below the maximum value
and causes the Security Violation counter to increment.
4. Device interface configuration.
a. Configure IP addressing for PC1, PC2, Internal Server, External Server and PC3
Interfaces according Table 1.
5. Perform a basic checking.
a. Connectivity between PC1 and R1.
b. Connectivity between PC2 and R1.
c. Connectivity between Internal Server and R1.
d. Connectivity between SW1 and R1 (all SVIs).
e. Connectivity between SW2 and R1 (all SVIs).
f. Connectivity between PC1 and PC2.
g. Connectivity between PC1 and SW1 (all SVIs).
h. Connectivity between PC2 and SW1 (all SVIs).
i. Connectivity between PC1 and SW2 (all SVIs).
j. Connectivity between PC2 and SW2 (all SVIs).
k. Connectivity between SW1 and Internal Server.
l. Connectivity between SW2 and Internal Server.
m. Connectivity between PC3 and R3.
n. Connectivity between R1 and R2.
o. Connectivity between R1 and R3.
p. Connectivity between R2 and R3.
q. Connectivity between ISP and R2.
r. Connectivity between External Server and ISP.
s. Access to all routers with passwords assigned (Enable, Console and VTY lines).
t. Check port security on switches SW1 and SW2.

Phase 4: Routing Configuration Requirements

The technician is assigned to create a configuration that meets the following requirements:

1. Routing Configuration.
a. OSPF with the Process ID 10 for R1 and R2.
b. R1 propagates OSPF routing information about all its directly connected
networks.
c. R2 propagates OSPF routing information about its directly connected networks
on Se0/1 and Lo0.
d. R1 only sends and receives OSPF routing updates through Se0/0.
e. R2 only sends and receives OSPF routing updates through Se0/1.
f. RIPv2 for R2 and R3.
g. R3 propagates RIPv2 routing information about all its directly connected
networks.
h. R2 propagates RIPv2 routing information about its directly connected networks
on Se0/0 and Lo1.

8
CCNA 2: Routing and Switching Essentials v5.0 Case Study

i.R3 only sends RIPv2 routing updates through Se0/1.

j.R2 only sends RIPv2 routing updates through Se0/0.
k.R2 and R3 does not summarize to major networks.
l.Connection between domains:
 The connection between R1 and the networks inside RIPv2 domain
requires only one command. You have to reach R3 LAN, the serial
link R2–R3 and the R2’s Loopback1 from any host in R1 LANs. The
packets will pass through R1-R3 Link. A default static route is not valid.
 The connection between R3 and the networks inside OSPF domain
requires only one command. You have to reach R1 LANs, the serial link
R1–R2 and the R2’s Loopback0 from any host in R3 LAN. The packets
will pass through R1-R3 Link. A default static route is not valid.
m. R2 has a default gateway toward ISP.
n. R1 and R3 forwards packets to R2 when they do not find a match between
the destination IP address in the packet header and their routing tables (NOTE:
You can only modify the R2’s configuration to achieve this requirement).
o. ISP only knows information about its directly connected networks.
2. Perform a basic checking.
a. Connectivity between all devices inside OSPF process.
b. Connectivity between all devices inside RIPv2 process.
c. Connectivity between routing domains.
d. Connectivity between External Server and private domain devices. Is it
successful or not? Why?

Phase 5: NAT Configuration Requirements

The technician is assigned to create a configuration that meets the following requirements:

1. Users within Sales and Marketing networks gain access to Public Domain through a
translation of internal IP addresses to the Fa0/0 interface of R2 and different ports.
2. Users in the Public Domain gain access to Internal Server sending the requests to
1.1.1.100/24.
3. Perform a basic checking.
a. Connectivity from users inside Private Domain to External Server.
b. Connectivity from users inside Public Domain to Internal Server.

Phase 6: DHCP Configuration Requirements

The technician is assigned to create a configuration that meets the following requirements:

1. R2 is the DHCP Server.

2. R2 serves IP addressing information to users in Sales and Marketing networks.
3. Exclude IP addresses that are yet assigned of being assigned in new DHCP requests.
4. Change the configuration of PC1, PC2 and PC3 to request IP addressing parameters to
DHCP Server.
5. Perform a basic checking.

9
CCNA 2: Routing and Switching Essentials v5.0 Case Study

a. Note the IP address of PC1: _______________________

b. Note the IP address of PC2: _______________________
c. Note the IP address of PC3: _______________________
d. Do they belong to the pools created?
e. Check connectivity between PC1 and other devices in Private and Public
Domains.
f. Check connectivity between PC2 and other devices in Private and Public
Domains.
g. Check connectivity between PC3 and other devices in Private and Public
Domains.

Phase 7: ACL Configuration Requirements

The technician is assigned to create a configuration that meets the following requirements:

1. Only users within Sales network have access to R1 VTY lines. Use standard named ACLs.
2. Only users within Sales network have FTP access to the External Server.
3. Only users within Marketing network have HTTP access to the External Server.
4. Ping from PC1 to PC3 is successful but ping from PC3 to PC1 is unsuccessful.
5. Apply ACLs carefully.
6. Configurations in ISP are not permitted.
7. Perform a basic checking.
a. Be sure that all requirements are fulfilled and there is still connectivity in the
topology.

Phase 8: Troubleshooting
The technician is assigned to check the connectivity and performance of the network
implemented.

1. Repeat the checking done before to be sure that the performance is correct and provide
documentation that specifies how the checking was tested.
2. Explain and justify the results.

10
CCNA 2: Routing and Switching Essentials v5.0 Case Study

Phase 9: Documenting the Network

In order to support the network properly, documentation is required. Create documentation
that is logically organized to make troubleshooting simpler:

Routers

 show cdp neighbors

 show ip interface brief
 show ip route
 show ip protocols
 show interfaces <type_slot_port>
 show startup-config
 show ip ospf neighbor
 show ip nat statistics
 show ip nat translations
 show ip dhcp binding
 show ip dhcp pool
 show ip access-lists

Switches

 show cdp neighbors

 show ip interface brief
 show interfaces trunk
 show interface vlan <vlan>
 show vlan brief
 show startup-config

Case Study Deliverables

The key lesson of this case study is the importance of thorough and clear documentation. There
should be two types of documentation completed.

General Documentation:

 A complete narrative of the project should be typed using word processing software.
 Since the scenarios break up the entire task into pieces, take care to address each
scenario task so that any person could understand that particular task.
 Microsoft Excel or another spreadsheet program could be used to simply list the
equipment and serial numbers.
 Microsoft Visio or any paint program could be used to draw the network.
 Provide documentation that specifies how the connectivity was tested.

11
CCNA 2: Routing and Switching Essentials v5.0 Case Study

Technical Documentation:

The technical documentation should include details of the network topology. Microsoft Visio or
any paint program could be used to draw the network (physical or logical topology).

The technical documentation has to include a table or tables with the following details:

 IP addressing of all interfaces

 DCE/DTE information
 Router passwords
 Banner MOTD
 Interface descriptions
 IP addressing and gateway assignments for all end devices
 Router output from the following commands should be captured and placed into this
documentation (for each router):
o show cdp neighbors
o show ip interface brief
o show ip route
o show ip protocols
o show interfaces <type_slot_port>
o show startup-config
o show ip ospf neighbor
o show ip nat statistics
o show ip nat translations
o show ip dhcp binding
o show ip dhcp pool
o show ip access-lists
 Switch output from the following commands should be captured and placed into this
documentation:
o show cdp neighbors
o show ip interface brief
o show interfaces trunk
o show interface vlan <vlan>
o show vlan brief
o show startup-config

12