CCNA31

CCNA3:
Switching Basics and Intermediate

Routing Case Study
Adam Acker
Perry Skipton
February 25th, 2008
NETW3000 – Internetworking III
NETW3000 – Internetworking III – CCNA3 – Switching Basics and Intermediate Routing Case Study
Table of Contents
Introduction.................................................................................................................................................1
Scenario...................................................................................................................................................1
Requirements..........................................................................................................................................2
General Requirements.........................................................................................................................2
Network Layout...........................................................................................................................................4
Physical Layout........................................................................................................................................4
Logical Layout..........................................................................................................................................5
Routing Protocol Requirements...........................................................................................................6
OSPF Configuration..............................................................................................................................7
VLSM Layout........................................................................................................................................8
VLAN Layout........................................................................................................................................9
Equipment Configuration...................................................................................................................10
Finalization................................................................................................................................................14
Testing...................................................................................................................................................14
Initial Testing.....................................................................................................................................14
Implementation Testing.....................................................................................................................15
Conclusion.................................................................................................................................................16
Appendix.......................................................................................................................................................i
Router Configuration Files........................................................................................................................i
Gateway................................................................................................................................................i
Main.....................................................................................................................................................ii
Admin..................................................................................................................................................iv
Remote_Sales......................................................................................................................................v
Switch Configuration................................................................................................................................v
Admin_Switch......................................................................................................................................v
Remote Sales Switch...........................................................................................................................vi
Main_1st_Floor..................................................................................................................................vii
Main_2nd_Floor...................................................................................................................................x
Main_3rd_Floor.................................................................................................................................xiii
ii | P a g e
Introduction
Scenario
The purpose of this case study is to show our
knowledge of network design and documentation in
regards to CCNA3. Throughout this case study we will
demonstrate our abilities as they relate to the CCNA3
course.
The scenario case study is fairly straight forward. The

company XYZ Research Company has hired a network
consultant group to design their network. The XYZ
Research Company is a small company which develops high-speed wireless products. Their office is
contained within two separate buildings, one for the administrative group, and the other is for sales and
marketing group, and the larger research and development group. The larger building which contains
the sales and marketing group, and the research and development group is three floors (with various
employees on each floor).
1|Page
Requirements
General Requirements
Like any project of this nature, there are requirements. These requirements must be met in order for
the documentation to be of use to XYZ Research Company.
Since they are a relatively small company, they will require a bit of equipment including five switches
and four routers.
The requirements as stated by the XYZ Research Company are:
 18 employees in the Research and Development group.
 9 employees in the Sales and Marketing group.
 8 employees in the Administration group.
 5 employees in the remote sales office.
 Lifetime Max of 5 servers on separate subnet, regardless of company growth.
 Use subnet 200.200.100.0 /30 for connection to the Internet router.
 Use VLSM for IP addressing.
 Expect 100% growth of current IP requirements when determining size of subnets.
 All networking devices must have IP addresses.
The company also requires a table of the VLSM design, showing all subnets which are to meet the XYZ
Research Company’s design. They also require more documentation which will be provided throughout
this documentation.
XYZ Research Company also has requirements regarding the VLANs that are created. The requirements
that were given are:
 There are 18 Research and Development employees.
 There are 9 Sales and Marketing employees.
 8 Research personnel and 2 Sales personnel are on Floor 3.
2|Page
 Floor 1 also has the Server LAN. Five server machines are planned but at this time only one is
available.
 There are separate rooms on each floor for the workgroups.
 There is sufficient space in each room to accommodate growth.
 The 100% growth will occur uniformly per floor.
 Switches in the Main building are connected in a loop so that if one switch fails an alternative
path is used.
 There will be one switch per floor shared among the different subnets.
 Spanning tree root is to be placed in an optimal position.
3|Page
Network Layout
Physical Layout
Before doing any detailed specifications for the network, it makes the most sense to determine the
physical layout before doing anything else. Notice that there are three different locations for the
network: The administrative building, branch office, and the main building (which is three floors, with
one switch per floor).
Below is a physical diagram of the basic network layout for the XYZ Research Company. The diagram
only shows the physical connections that devices have to each other. Notice that each building is
enclosed in a box so that it is easy to distinguish between different locations.
Administrative Building
Gateway Admin
Admin_Switch
DTE Serial0/0 FastEthernet 0/0
ISP FastEthernet 0/0 FastEthernet 0/1
DCE Serial0/1
Admin LAN
Branch Office
Main Building
DCE Serial 0/0

Remote_Sales_Switch Remote_Sales
Main_1st_Floor
DCE Serial0/1 FastEthernet 0/0
FastEthernet 0/0 DTE Serial0/1
Main
Trunked
Branch LAN
Main_2nd_Floor
Trunked
Trunked
Main_3rd _Floor
Some parts of the network are more complicated than others. For example, the branch office, and
Administrative building are fairly simple because they each have hosts on a single network. The main
building on the other hand, has three different networks that hosts are on (which span across three
different switches). The major difference is that these networks are taking advantage of VLANs.
All three switches are connected to each other (for redundancy and throughput purposes). The
interfaces that connect the switches together are trunked too, since each switch has to handle the three
different networks.
4|Page
Logical Layout
After the physical layout comes the logical layout. The diagram below is the same physical diagram as
before, but with specifics about each interface. After the network is set up physically, the configuration
can begin.
Loopback 0 Loopback0
Gateway 223.0.0.193 Admin 223.0.0.189
Admin_Switch
DTE Serial0/1 FastEthernet 0/0 223.0.0.66
200.200.100.1 /30 223.0.0.177 /30
223.0.0.178 223.0.0.65
DCE Serial0/0
223.0.0.181 /30
Admin LAN
Branch Office
Main Building
DTE Serial 0/0

223.0.0.182 Main _1st_Floor
Remote_Sales _Switch Remote_Sales 223 .0.0.162
223.0.0.98
DCE Serial0/1
223.0.0.185 Logical Interfaces
FastEthernet 0/0.1
223.0.0.97 223.0.0.186
223.0.0.161
Loopback 0 Main FastEthernet 0/0.2

223.0.0.1 Trunked
Branch LAN 223.0.0.197
Loopback 0 FastEthernet 0/0.3
223.0.0.201 223.0.0.229 Main_2nd_Floor
223 .0.0.163
Trunked
Trunked
VLAN Specifications
Main_3rd _Floor
VLAN1 - Server VLAN 223 .0.0.164
VLAN2 - Workgroup 1 (Research & Development VLAN)

VLAN3 - Workgroup 2 (Sales and Marketing VLAN)
There are a few things you may notice from the diagram. For example, each router has its’ own loopback
interface. These loopback interfaces are useful for troubleshooting connection problems inside of the
network.
Also notice that there are three lines going from the Main router to the Main_1st_Floor switch. These
are actually connected by one physical cat5e cable, but are three different logical interfaces (one
interface per VLAN).
5|Page
Routing Protocol Requirements

One thing that should be determined before implementation is the desired routing protocol. There are
several routing protocols to choose from, including RIPv1, RIPv2, EIGRP, IGRP, and OSPF.
The table below shows a comparison of the different routing protocols. Notice that each routing
protocol has its advantages and disadvantages. Also note that acronyms DV=Distance Vector,
BH=Balanced Hybrid, and LS=Link State.
Protocol Classful/ Convergence Bandwidth CPU/Memory Proprietary Stability Total

Classless Time Usage Usage
RIPv1 (DV) Classful High (-1) High (-1) Low (+1) No (+1) Poor (-1) -1(No VLSM)
RIPv2 (DV) Classless High (-1) High (-1) Low (+1) No (+1) Poor (-1) -1
EIGRP Classless Low (+1) Moderate (0) Moderate (0) Yes (-1) Good (+1) +1
(BH)
IGRP (LS) Classful Low (+1) Low (+1) High (-1) Yes (-1) Good (+1) +1 (No VLSM)
OSPF (LS) Classless Low (+1) Low (+1) High (-1) No (+1) Good (+1) +3
After comparing the different routing protocols, we determined that OSPF is the best routing protocol
for this situation. The only major disadvantage of OSPF is that it is more difficult to set up and
administrate since it is more complex. Also, notice that the classful routing protocols cannot be used
because they do not support Variable Length Subnet Masks.
6|Page
OSPF Configuration
As mentioned before, OSPF is one of the more difficult routing protocols to configure. It requires that an
administrator knows how OSPF works before configuring it.
One decision that must be made when implementing OSPF is deciding which router is going to be the
designated router (DR) and which is going to be the backup-designated router (DBR).
In our case, we discovered that OSPF uses multicast which is an Ethernet protocol and therefore will not
work through a serial connection. There are only two routers (of the four) that are connected through a
Fast Ethernet connection, therefore assigning a designated router and backup-designated router is not
necessary since there are only two routers to worry about. The diagram below helps illustrate this fact.
Gateway Admin
FastEthernet 0/0
ISP FastEthernet 0/0
DCE Serial0/0
DTE Serial 0/0

Remote_Sales
DTE Serial0/1
Main
7|Page
VLSM Layout
With the use of variable length subnetting, we can very efficiently take advantage of all addresses in the
network. With basic subnetting, all subnets are the same size, and therefore, some addresses are
reserved for a subnet when they are not needed. Therefore with basic subnetting, there would be many
unused addresses. It does not make sense to have a large subnet if there are only two used IP addresses
in it if the subnet has over 16 addresses.
As you can see by the cart below, the subnets are various sizes. There is even some of the network
addresses that are not subnetted in light-blue (which can subnetted at a later time).
In this implementation there are five major networks that have to be created, along with seven more
networks which will be used for router-connections. The five major networks are research and
development, administration, remote sales, sales and marketing, and servers / http.
The network takes advantage of VLSM by having each network with various subnet masks. We
determined the size that the subnet must be and then determined the subnet mask which determines
the size of the network. On the next page is a diagram with more specific details in relation to the VLSM
configuration.
8|Page
Subnet Name Needed Allocated Address Mask Dec Mask Assignable Range
Size Size
Research and Development 36 62 223.0.0.0 /26 255.255.255.192 223.0.0.1 - 223.0.0.62

Administration 30 30 223.0.0.64 /27 255.255.255.224 223.0.0.65 - 223.0.0.94
Remote Sales Office 20 30 223.0.0.96 /27 255.255.255.224 223.0.0.97 - 223.0.0.126
Sales and Marketing 18 30 223.0.0.128 /27 255.255.255.224 223.0.0.129 - 223.0.0.158
Servers and HTTP 14 14 223.0.0.160 /28 255.255.255.240 223.0.0.161 – 223.0.0.174
Router Link Gateway Admin 2 2 223.0.0.176 /30 255.255.255.252 223.0.0.177 – 223.0.0.178
Router Link Gateway Main 2 2 223.0.0.180 /30 255.255.255.252 223.0.0.181 – 223.0.0.182
Router Link Gateway 2 2 223.0.0.184 /30 255.255.255.252 223.0.0.185 – 223.0.0.186
Remote-Sales
Router Loopback Admin 1 2 223.0.0.188 /30 255.255.255.252 223.0.0.189 – 223.0.0.190
Router Loopback Gateway 1 2 223.0.0.192 /30 255.255.255.252 223.0.0.193 – 223.0.0.194
Router Loopback Main 1 2 223.0.0.196 /30 255.255.255.252 223.0.0.197 - 223.0.0.198
Router Loopback Remote- 1 2 223.0.0.200 /30 255.255.255.252 223.0.0.201 - 223.0.0.202
Sales
VLAN Layout
One interesting part of this network is the implementation of VLANs. Inside of the main building there
are three separate networks which span across three switches on three floors. Depending on what is
connected to a port determines what VLAN the device attached to it will be on. These VLANs are set
statically to each port. They could be assigned dynamically if the hardware was available, but it is not
required for this implementation.
The diagram below focuses on how everything in the main building is connected:
To Gateway
(Router)
Main Building
DTE Serial 0/0
223.0.0.182
Main_1st_Floor
DCE Serial0/1
223.0.0.162
223.0.0.185
To Remote_Sales Logical Interfaces
(Router)
FastEthernet 0/0.1
223.0.0.161
Loopback0 Main FastEthernet 0/0.2
223.0.0.1 Trunked
223.0.0.197
FastEthernet 0/0.3
223.0.0.229 Main_2nd_Floor
223 .0.0.163
Trunked
Trunked
VL A N Sp ecificatio n s
Main_3rd_Floor
VL A N 1 - Server VLAN [223 .0 .0.161 – 223.0.0.174] 223.0.0.164
VL A N 2 - Research & Development VLAN [223 .0.0.1 - 223 .0 .0.62]
VL A N 3 - Sales and Marketing VLAN [223.0.0.129 - 223 .0.0 .158 ]
Take note that there are three VLANs configured across the three switches. Each VLAN is assigned a
specific subnet which is listed above.
9|Page
Equipment Configuration
Switches
There are a total of five switches that will be used in the implementation of
this network. One switch will be located in the administration building, one
switch will be in the branch office, and there will be three switches in the main
building. The two lone-switches will not have much in the way of
configuration, since they will be using a lot less features. The lone-switches will
each be controlling one network.
As stated before, the three switches that are located in the main building are a bit more complex. They
will be using IEEE 802.1Q as a trunking protocol so that they can share VLANs between each other.
The chart below shows the basic configuration of each switch in the network:
Switch Name Model # of ports Location IP Address Gateway Management VTP VTP Domain STP Root
VLAN Mode
Admin_Switch 2950 24 Administratio 223.0.0.66 223.0.0.65 1 N/A N/A N/A

n Building
Remote_Sales_Switch 2950 24 Branch Office 223.0.0.98 223.0.0.97 1 N/A N/A N/A
Main_1st_Floor_Switch 2950 24 Main Building 223.0.0.162 223.0.0.161 1 Server Main Yes
Main_2nd_Floor_Switch 2950 24 Main Building 223.0.0.163 223.0.0.161 1 Client Main No
Main_3rd_Floor_Switch 2950 24 Main Building 223.0.0.164 223.0.0.161 1 Client Main No
[More tables for the switch interfaces can be found in the Appendix.]
The main 1st floor Switch was selected as the STP (Spanning Tree Protocol) root because it was centered
logically between the 2 other switches in the physical loop. Both of the other 2 switches are reachable
with a link cost of 19. Any inter-VLAN traffic or other traffic that must be routed will only have to go
through maximum of two switches in one trip. This would provide for the lowest latency possible. To
ensure that the Main 1st Floor switch is elected as the STP, should have a lower priority.
Once this switch is elected, the link between the Main 2nd floor switch and the Main 3rd Floor switch
will be blocked due to a higher root path cost. This will result in the desired configuration of STP.
10 | P a g e
Routers
There are four routers in the network we have designed, each with a different configuration (although in
some cases they are similar). The routers are shown below:
Gateway Admin
DTE Serial0/1
FastEthernet 0/0 FastEthernet 0/1
ISP FastEthernet 0/0 To Admin_Switch
DCE Serial0/0
DTE Serial 0/0

Remote_Sales
FastEthernet 0/0
To Main_1st_Floor
To Remote_Sales_Switch DTE Serial0/1
Main
All passwords on the routers are configured the same. If changes are made to these passwords, they
should be documented. The passwords can be found in the table below:
Authentication Password
VTY (User Mode) cisco
Console (User Mode) cisco
Privilleged Exec Mode class
Below are four tables which show each of the four routers and their interfaces. For more information,
the router configuration files can be found in the Appendix. Note that as stated earlier, routers will be
using OSPF as a routing protocol.
Gateway
Hostname: Gateway
Location: Administrative Building
Interface Description and DTE/DCE Clock Network Name Interface IP Interface IP Subnet Mask Wildcard
Purpose Rate Address Mask
Serial 0/1 To ISP DTE Router Link Gateway 200.200.100.0 200.200.100.1 255.255.255.252 0.0.0.3
to ISP
Serial 0/0 To Main DCE 64000 Router Link Gateway 223.0.0.180 223.0.0.181 225.255.255.252 0.0.0.3
– Main
FE 0/0 To Admin N/A 100MB Router Link Gateway 223.0.0.176 223.0.0.177 255.255.255.252 0.0.0.3
– Admin
Loopback OSPF Config N/A N/A Router Loopback 223.0.0.192 223.0.0.193 255.255.255.252 0.0.0.3
0 Gateway
11 | P a g e
Main
Hostname: Main
Location: Main Building
Interface Description DTE/DCE Clock Network Name Network Number Interface IP Subnet Mask Wildcard
and Purpose Rate Mask
Serial To Gateway DTE --- Router Link Gateway - Main 223.0.0.180 223.0.0.182 255.255.255.252 0.0.0.3
0/0
Serial To DCE 64000 Router Link Main –Remote_Sales 223.0.0.184 223.0.0.185 255.255.255.252 0.0.0.3
0/1 Remote_Sales
FE 0.1 VLAN 1 N/A 100MB Enterprise Servers & HTTP 223.0.0.160 223.0.0.161 255.255.255.240 0.0.0.15
Servers
FE 0.2 VLAN 2 R&D N/A 100MB Research and Development 223.0.0.0 223.0.0.1 255.255.255.192 0.0.0.63
FE 0.3 VLAN 3 Sales N/A 100MB Sales and Marketing 223.0.0.228 223.0.0.229 255.255.255.224 0.0.0.31
Loopbac OSPF Config N/A N/A Router Loopback Main 223.0.0.196 223.0.0.197 255.255.255.252 0.0.0.3
k0
Admin
Hostname: Admin
Interface Description and DTE/DCE Clock Network Name Network Interface IP Subnet Mask Wildcard
Purpose Rate Number Mask
FE 0/0 To Gateway N/A 100MB Router Link 223.0.0.176 223.0.0.178 255.255.255.252 0.0.0.3
Gateway - Admin
FE 0/1 To MainTo Admin N/A 100MB From Admin to 223.0.0.64 223.0.0.65 225.255.255.224 0.0.0.31
Lan Adminlan
Loopback OSPF Config N/A N/A Router Loopback 223.0.0.188 223.0.0.189 255.255.255.252 0.0.0.3
0 Admin
Remote_Sales
Hostname: Gateway
Location: Branch Office
Interface Description DTE/DCE Clock Network Name Network Number Interface IP Subnet Mask Wildcard Mask
and Purpose Rate
Serial 0/1 To Main DTE -- Router Link Main 223.0.0.184 223.0.0.186 255.255.255.252 0.0.0.3
– Remote_Sales
FE 0/0 To N/A 100MB From 223.0.0.96 223.0.0.97 225.255.255.224 0.0.0.31
Remote_Sales Remote_Sales -
LAN LAN
Loopback 0 OSPF Config N/A N/A Router Loopback 223.0.0.200 223.0.0.201 255.255.255.252 0.0.0.3
Remote_Sales
12 | P a g e
Hosts
Each host, server or network device has to have its’ own network settings in order to connect to the
network. For each device, the IP settings have to be in a range which is acceptable for the network that
it is in. For example, Host 1 is in the Research & Development LAN, and therefore has an IP address of
223.0.0.2 which is in the Research & Development subnet (which has a range of 223.0.0.1 to 223.0.0.62).
Since all hosts will be set statically, it is required that all host addresses be documented to ensure that
there are no conflicts, and hosts are on the proper networks. The table below shows all of the hosts,
servers and devices along with their settings in regards to the network that must be configured:
LAN Name PC or Server IP Address Subnet Mask Gateway Services

Provided
Reseach & Host 1 223.0.0.2 255.255.255.192 223.0.0.1 N/A

Development
Host 2 223.0.0.3 255.255.255.192 223.0.0.1 N/A
Host 3 223.0.0.4 255.255.255.192 223.0.0.1 N/A
Host 4 223.0.0.5 255.255.255.192 223.0.0.1 N/A
Host 5 223.0.0.6 255.255.255.192 223.0.0.1 N/A
Host 6 223.0.0.7 255.255.255.192 223.0.0.1 N/A
Host 7 223.0.0.8 255.255.255.192 223.0.0.1 N/A
Host 8 223.0.0.9 255.255.255.192 223.0.0.1 N/A
Host 9 223.0.0.10 255.255.255.192 223.0.0.1 N/A
Host 10 223.0.0.11 255.255.255.192 223.0.0.1 N/A
Host 11 223.0.0.12 255.255.255.192 223.0.0.1 N/A
Host 12 223.0.0.13 255.255.255.192 223.0.0.1 N/A
Host 13 223.0.0.14 255.255.255.192 223.0.0.1 N/A
Host 14 223.0.0.15 255.255.255.192 223.0.0.1 N/A
Host 15 223.0.0.16 255.255.255.192 223.0.0.1 N/A
Host 16 223.0.0.17 255.255.255.192 223.0.0.1 N/A
Host 17 223.0.0.18 255.255.255.192 223.0.0.1 N/A
Host 18 223.0.0.19 255.255.255.192 223.0.0.1 N/A
Sales & Marketing Host 1 223.0.0.130 255.255.255.224 223.0.0.129 N/A
Host 2 223.0.0.131 255.255.255.224 223.0.0.129 N/A
Host 3 223.0.0.132 255.255.255.224 223.0.0.129 N/A
Host 4 223.0.0.133 255.255.255.224 223.0.0.129 N/A
Host 5 223.0.0.134 255.255.255.224 223.0.0.129 N/A
Host 6 223.0.0.135 255.255.255.224 223.0.0.129 N/A
Host 7 223.0.0.136 255.255.255.224 223.0.0.129 N/A
Host 8 223.0.0.137 255.255.255.224 223.0.0.129 N/A
Host 9 223.0.0.138 255.255.255.224 223.0.0.129 N/A
Servers Main 1st fl switch 223.0.0.162 255.255.255.240 223.0.0.161 N/A
Main 2nd fl switch 223.0.0.163 255.255.255.240 223.0.0.161 N/A
Main 3rd fl switch 223.0.0.164 255.255.255.240 223.0.0.161 N/A
Server 1 223.0.0.165 255.255.255.240 223.0.0.161 N/A
Server 2 223.0.0.166 255.255.255.240 223.0.0.161 N/A
Server 3 223.0.0.167 255.255.255.240 223.0.0.161 N/A
Server 4 223.0.0.168 255.255.255.240 223.0.0.161 N/A
Server 5 223.0.0.169 255.255.255.240 223.0.0.161 N/A
HTTP Server HTTP Server 223.0.0.170 255.255.255.240 223.0.0.161 DHCP, HTTP
Admin Admin Switch 223.0.0.66 255.255.255.224 223.0.0.65 N/A
Host 1 223.0.0.67 255.255.255.224 223.0.0.65 N/A
Host 2 223.0.0.68 255.255.255.224 223.0.0.65 N/A
Host 3 223.0.0.69 255.255.255.224 223.0.0.65 N/A
Host 4 223.0.0.70 255.255.255.224 223.0.0.65 N/A
Host 5 223.0.0.71 255.255.255.224 223.0.0.65 N/A
Host 6 223.0.0.72 255.255.255.224 223.0.0.65 N/A
Host 7 223.0.0.73 255.255.255.224 223.0.0.65 N/A
Branch Office Remote Sales Switch 223.0.0.98 255.255.255.224 223.0.0.97 N/A
Host 1 223.0.0.99 255.255.255.224 223.0.0.97 N/A
Host 2 223.0.0.100 255.255.255.224 223.0.0.97 N/A
Host 3 223.0.0.101 255.255.255.224 223.0.0.97 N/A
13 | P a g e
Host 4 223.0.0.102 255.255.255.224 223.0.0.97 N/A

Host 5 223.0.0.103 255.255.255.224 223.0.0.97 N/A
Finalization
Testing
Initial Testing
For the initial testing, the network was simulated with the program Packet Tracer 4.11. Here the
configuration files were put into the devices, and tested. As you can see below, the network created
looks very similar to the physical diagram that was created.
Packet Tracer 4.11 allows us to

simulate a lot of things with the
network. We were able to test the
connections between all devices to
ensure that they could communicate
with each other.
We sent packets between all devices

in the network and everything
appeared to work properly. As you
can see on the left, all ICMP traffic
was successful. Therefore in theory,
the network should work the same if
it were to be implemented on the
actual hardware.
14 | P a g e
Implementation Testing
After actually implementing the network, it is important to ensure that everything is working as desired.
All bugs should be troubleshot and fixed before traffic is passed through the network (for security and
reliability reasons). The checklist below should be used after everything is configured:
Condition Passed? (Yes/No)

Ping ISP from all hosts
Ping HTTP server (223.0.0.170) from all hosts
Ping VLAN1 host from VLAN1 (on same floor)
Ping VLAN1 host from VLAN1 (on different floor)
Ping Remote Sales LAN host (223.0.0.98-223.0.0.103) from VLAN1 host
Ping Admin LAN host (223.0.0.66-223.0.0.73) from VLAN1 host
15 | P a g e
Conclusion
As a final point, the network that we have documented should be sufficient to the needs of XYZ
Research Company. The documented network meets all
Gateway Admin
Admin_Switch
of the requirements that were specified.

DTE Serial0/1 FastEthernet 0/0
DCE Serial0/0
Admin LAN
Branch Office
Main Building
The next thing that may be worth implementing is the
Remote_Sales_Switch Remote_Sales
DCE Serial0/1
DTE Serial 0/0
FastEthernet 0/0
Trunked
Main_1st_Floor use of ACLs (access-control-lists). With the use of ACLs
the network could be more secure, only allowing traffic
Main
Trunked
Branch LAN
Main_2nd_Floor
in and out of each of the routers that is designated. ACLs

Trunked
Trunked
are useful but they also add another layer of complexity

Main_3rd_Floor
to the network which may not be desired.
The network should be sufficient to last the next five to ten years. The subnets that have been created
should allow for uniform growth (over 100%). And there is also room to create new subnets since about
30% of the network addresses are not used.
16 | P a g e
Appendix
Router Configuration Files
The following are copies of the router configuration files. If you want a briefer overview of the routers,
look in the Routers section under Equipment Details.
Gateway
! ip address 223.0.0.193 255.255.255.255
version 12.2 !
no service password-encryption router ospf 50
! log-adjacency-changes
hostname Gateway network 223.0.0.176 0.0.0.3 area 0
! network 223.0.0.180 0.0.0.3 area 0
! !
enable secret 5 $1$mERr ip classless

$9cTjUIEqNGurQiFU.ZeCi1
ip route 0.0.0.0 0.0.0.0 200.200.100.1
enable password cisco
!
!
!
!
!
!
!
interface FastEthernet0/0
line con 0
ip address 223.0.0.177 255.255.255.252
line vty 0 4
duplex auto
login
speed auto
!
!
!
interface Serial0/0
end
description Gateway To Main
ip address 223.0.0.181 255.255.255.252
clock rate 64000
interface Serial0/1
description Gateway To ISP
ip address 200.200.100.2 255.255.255.252
interface Loopback0
i|Page
interface Serial0/0
Main
! description Main To Gateway
version 12.2 ip address 223.0.0.182 255.255.255.252
no service password-encryption !
! interface Serial0/1
hostname Main description Main To Remote Sales
! ip address 223.0.0.185 255.255.255.252
! clock rate 64000
enable secret 5 $1$mERr !

interface Loopback0
ip address 223.0.0.196 255.255.255.255
!
!
!
router ospf 50
!
log-adjacency-changes
network 223.0.0.128 0.0.0.63 area 0
no ip address
network 223.0.0.0 0.0.0.31 area 0
duplex auto
network 223.0.0.128 0.0.0.15 area 0
speed auto
network 223.0.0.180 0.0.0.3 area 0
!
network 223.0.0.184 0.0.0.3 area 0
interface FastEthernet0/0.1
network 223.0.0.160 0.0.0.15 area 0
description VLAN 1 Enterprise Servers
network 223.0.0.0 0.0.0.63 area 0
encapsulation dot1Q 1 native
network 223.0.0.128 0.0.0.31 area 0
ip address 223.0.0.161 255.255.255.240
!
!
ip classless
!
description VLAN 2 Research & Development
!
encapsulation dot1Q 2
!
ip address 223.0.0.1 255.255.255.192
!
!
line con 0
line vty 0 4
description VLAN 3 Sales & Marketing
login
encapsulation dot1Q 3
!
ip address 223.0.0.129 255.255.255.224
!
ii | P a g e
end
iii | P a g e
network 223.0.0.176 0.0.0.3 area 0
!
Admin
! ip classless
version 12.2 !
! !
hostname Admin !
! line con 0
! password cisco
enable secret 5 $1$mERr login

line vty 0 4
password cisco
!
login
!
!
!
!
end
ip address 223.0.0.178 255.255.255.252
ip ospf priority 60
duplex auto
speed auto
ip address 223.0.0.65 255.255.255.224
duplex auto
speed auto
interface Loopback0
ip address 223.0.0.189 255.255.255.255
router ospf 50
network 223.0.0.64 0.0.0.31 area 0
iv | P a g e
router ospf 50
Remote_Sales
! network 223.0.0.96 0.0.0.15 area 0
version 12.2 network 223.0.0.184 0.0.0.3 area 0
! ip classless
hostname Remote_Sales !
! !
! !
enable secret 5 $1$mERr !

line con 0
password cisco
!
login
!
line vty 0 4
!
password cisco
login
ip address 223.0.0.97 255.255.255.240
!
ip ospf priority 30
!
duplex auto
end
speed auto
interface Serial0/0
no ip address
shutdown
interface Serial0/1
description To Main
ip address 223.0.0.186 255.255.255.252
interface Loopback0
ip address 223.0.0.201 255.255.255.255
v|Page
Switch Configuration
Admin_Switch
Switch Name: Admin_Switch
IP Address: 233.0.0.66 /27
Default Gateway: 223.0.0.65
Interface or / Description and Speed Duplex Network Network Subnet Mask VLAN Switch port Encapsulation
Subinterface Purpose Name Number type
type/number
FA 0/1 Host 1 100 MB Full Administration 223.0.0.64 255.255.255.224 1 100 MB N/A

FA 0/8 Rsvd for Admin 100 MB
FA 0/15 100 MB
FA 0/16 100 MB
FA 0/17 100 MB
FA 0/18 100 MB
FA 0/19 100 MB
FA 0/20 100 MB
FA 0/21 100 MB
FA 0/22 100 MB
FA 0/23 100 MB
FA 0/24 To Admin Router 100 MB Full Administration 223.0.0.64 255.255.255.224 1 100 MB N/A
Remote Sales Switch
Switch Name: Remote_Sales_Switch
Location: Branch Office
IP Address: 233.0.0.98 /28
Interface or / Description and Speed Duplex Network Network Subnet Mask VLAN Switch port Encapsulation (if
Subinterface Purpose Name Number type needed)
type/number
FA 0/1 Host 1 100 MB Full Remote Sales 223.0.0.96 255.255.255.224 1 100 MB N/A
Office
Office
Office
Office
Office
FA 0/6 Remote Sales 100 MB
Rsvd
Rsvd
Rsvd
Rsvd
Rsvd
FA 0/11 100 MB
FA 0/12 100 MB
FA 0/13 100 MB
FA 0/14 100 MB
FA 0/15 100 MB
FA 0/16 100 MB
FA 0/17 100 MB
FA 0/18 100 MB
FA 0/19 100 MB
FA 0/20 100 MB
FA 0/21 100 MB
FA 0/22 100 MB
FA 0/23 100 MB
FA 0/24 Remote Sales 100 MB Full Remote Sales 223.0.0.96 255.255.255.224 1 100 MB N/A
Router Office
Main_1st_Floor
Switch Name: Main_1st_Floor_Switch
Location: Main Building, 1st floor
IP Address: 233.0.0.162 /28
type/number
FA 0/1 Main Router 100 MB Full Trunking 223.0.0.160 255.255.255.240 1 100 MB 802.1Q
223.0.0.0 255.255.255.192 2 100 MB 802.1Q
223.0.0.128 255.255.255.224 3 100 MB 802.1Q
FA 0/2 Server 1 100 MB Full Enterprise 223.0.0.160 255.255.255.240 1 100 MB 802.1Q
Servers &
HTTP
FA 0/3 Server Rsvd 100 MB Full Enterprise 223.0.0.160 255.255.255.240 1 100 MB 802.1Q
Servers &
HTTP
Servers &
HTTP
Servers &
HTTP
Servers &
HTTP
FA 0/7 R&D Host 1 100 MB Full Reseach & 223.0.0.0 255.255.255.192 2 100 MB 802.1Q
Development
Development
Development
Development
FA 0/11 R & D Rsvd 100 MB Full Reseach & 223.0.0.0 255.255.255.192 2 100 MB 802.1Q
Development
Development
Development
Development
FA 0/15 Sales Host 1 100 MB Full Sales & 223.0.0.128 255.255.255.224 3 100 MB 802.1Q
Marketing
Marketing
FA 0/17 HTTP Server 100 MB Full Enterprise 223.0.0.160 255.255.255.240 1 100 MB 802.1Q
Servers &
HTTP
Marketing
FA 0/19 Sales Rsvd 100 MB Full Sales & 223.0.0.128 255.255.255.224 3 100 MB 802.1Q
Marketing
Marketing
Marketing
FA 0/23 Trunk 100 MB Full Trunking 223.0.0.160 255.255.255.240 1 100 MB 802.1Q
223.0.0.0 255.255.255.192 2 100 MB 802.1Q
223.0.0.128 255.255.255.224 3 100 MB 802.1Q
FA 0/24 Switch 2nd floor 100 MB Full Trunking 223.0.0.160 255.255.255.240 1 100 MB 802.1Q
223.0.0.0 255.255.255.192 2 100 MB 802.1Q
223.0.0.128 255.255.255.224 3 100 MB 802.1Q
Configuration File
switchport access vlan 2
!
switchport mode access

version 12.1
!
no service password-encryption
!

hostname Main_1st_Floor

!
!
enable secret 5 $1$mERr
!
!
!
spanning-tree vlan 1 priority 4096
!
!
switchport mode trunk
!
!
!
!
!
!
!
!
!
!
!
!
!
! !
interface FastEthernet0/19 end
interface Vlan1
ip address 223.0.0.162 255.255.255.240
shutdown
ip default-gateway 223.0.0.161
line con 0
password cisco
login
line vty 0 4
password cisco
login
line vty 5 15
password cisco
login
!
Main_2nd_Floor
Switch Name: Main_2nd_Floor_Switch
Location: Main Building, 2nd floor
IP Address: 233.0.0.163 /28
type/number
Development
Development
Development
Development
Development
Development
Development
Development
Development
Development
Development
Development
Marketing
Marketing
Marketing
Marketing
Marketing
Marketing
Marketing
Marketing
FA 0/21 100 MB
FA 0/22 100 MB
FA 0/23 Main 1st Floor 100 MB Full Trunking 223.0.0.160 255.255.255.240 1 100 MB 802.1Q
Switch
223.0.0.0 255.255.255.192 2 100 MB 802.1Q
223.0.0.128 255.255.255.224 3 100 MB 802.1Q
FA 0/24 Main 3rd Floor 100 MB Full Trunking 223.0.0.160 255.255.255.240 1 100 MB 802.1Q
Switch
223.0.0.0 255.255.255.192 2 100 MB 802.1Q
223.0.0.128 255.255.255.224 3 100 MB 802.1Q
!
Configuration File
!

version 12.1

!
!
hostname Main_2nd_Floor
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
! password cisco
interface FastEthernet0/17 login
! !
interface FastEthernet0/18 !
! end
interface Vlan1
ip address 223.0.0.163 255.255.255.240
line con 0
password cisco
login
line vty 0 4
password cisco
login
line vty 5 15
Main_3rd_Floor
Switch Name: Main_3rd_Floor_Switch
Location: Main Building, 3rd floor
IP Address: 233.0.0.164 /28
type/number
Development
Development
Development
Development
Development
Development
Development
Development
Development
Development
Development
Development
Development
Development
Development
Development
Marketing
FA 0/18 Sales Host 9 100 MB Full Sales & 223.0.0128 255.255.255.224 3 100 MB 802.1Q
Marketing
Marketing
Marketing
FA 0/21 100 MB 802.1Q
FA 0/22 100 MB 802.1Q
FA 0/23 Switch 2nd floor 100 MB Full Trunking 223.0.0.160 255.255.255.240 1 100 MB 802.1Q
223.0.0.0 255.255.255.192 2 100 MB 802.1Q
223.0.0.128 255.255.255.224 3 100 MB 802.1Q
FA 0/24 Trunk 100 MB Full Trunking 223.0.0.160 255.255.255.240 1 100 MB 802.1Q
223.0.0.0 255.255.255.192 2 100 MB 802.1Q

223.0.0.128 255.255.255.224 3 100 MB 802.1Q
!
Configuration File
!

version 12.1

!
!
hostname Main_3rd_Floor

!

!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
!
! line vty 0 4
interface FastEthernet0/18 password cisco
switchport access vlan 3 login
switchport mode access line vty 5 15
! password cisco
interface FastEthernet0/19 login
switchport access vlan 3 !
switchport mode access !
! end
interface Vlan1
ip address 223.0.0.164 255.255.255.240
line con 0
password cisco
login

CCNA31

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

CCNA31

Enviado por

Direitos autorais:

Formatos disponíveis

CCNA3:

Switching Basics and Intermediate

The scenario case study is fairly straight forward. The

The requirements as stated by the XYZ Research Company are:

 18 employees in the Research and Development group.

 9 employees in the Sales and Marketing group.

 8 employees in the Administration group.

 5 employees in the remote sales office.

 Lifetime Max of 5 servers on separate subnet, regardless of company growth.

 Use subnet 200.200.100.0 /30 for connection to the Internet router.

 Use VLSM for IP addressing.

 Expect 100% growth of current IP requirements when determining size of subnets.

 All networking devices must have IP addresses.

 There are 18 Research and Development employees.

 There are 9 Sales and Marketing employees.

 8 Research personnel and 2 Sales personnel are on Floor 3.

 6 Research personnel and 4 Sales personnel are on Floor 2.

 4 Research personnel and 3 Sales personnel are on Floor 1.

 There are separate rooms on each floor for the workgroups.

 There is sufficient space in each room to accommodate growth.

 The 100% growth will occur uniformly per floor.

 Spanning tree root is to be placed in an optimal position.

DCE Serial 0/0

FastEthernet 0/0 DTE Serial0/1

DTE Serial 0/0

Loopback 0 Main FastEthernet 0/0.2

VLAN2 - Workgroup 1 (Research & Development VLAN)

Routing Protocol Requirements

Protocol Classful/ Convergence Bandwidth CPU/Memory Proprietary Stability Total

ISP FastEthernet 0/0

DTE Serial 0/0

Research and Development 36 62 223.0.0.0 /26 255.255.255.192 223.0.0.1 - 223.0.0.62

VL A N 2 - Research & Development VLAN [223 .0.0.1 - 223 .0 .0.62]

VL A N 3 - Sales and Marketing VLAN [223.0.0.129 - 223 .0.0 .158 ]

Admin_Switch 2950 24 Administratio 223.0.0.66 223.0.0.65 1 N/A N/A N/A

Main_1st_Floor_Switch 2950 24 Main Building 223.0.0.162 223.0.0.161 1 Server Main Yes

Main_2nd_Floor_Switch 2950 24 Main Building 223.0.0.163 223.0.0.161 1 Client Main No

Main_3rd_Floor_Switch 2950 24 Main Building 223.0.0.164 223.0.0.161 1 Client Main No

DTE Serial 0/0

LAN Name PC or Server IP Address Subnet Mask Gateway Services

Reseach & Host 1 223.0.0.2 255.255.255.192 223.0.0.1 N/A

Host 4 223.0.0.102 255.255.255.224 223.0.0.97 N/A

Packet Tracer 4.11 allows us to

We sent packets between all devices

Condition Passed? (Yes/No)

of the requirements that were specified.

in and out of each of the routers that is designated. ACLs

are useful but they also add another layer of complexity

to the network which may not be desired.

no service password-encryption router ospf 50

hostname Gateway network 223.0.0.176 0.0.0.3 area 0

! network 223.0.0.180 0.0.0.3 area 0

enable secret 5 $1$mERr ip classless

ip address 223.0.0.181 255.255.255.252

clock rate 64000

description Gateway To ISP

ip address 200.200.100.2 255.255.255.252

version 12.2 ip address 223.0.0.182 255.255.255.252

hostname Main description Main To Remote Sales

! ip address 223.0.0.185 255.255.255.252

! clock rate 64000

enable secret 5 $1$mERr !

network 223.0.0.176 0.0.0.3 area 0

enable secret 5 $1$mERr login