CCNA   Discovery:    Designing   and   Supporting   Computer   Networks
Chapter   7   Case   Study
Prototyping   the   Campus   Network
Note:   This   case   study   utilizes   Packet   Tracer.
Please   see   the   Chapter   7   Packet   Tracer   file   located   in
Supplemental   Materials.
Introduction   and   Scenario
It   is   recommended   to   test   a   new   network   design   before   approval   or   deployment   which   provides   a   proof ‐ of ‐ concept   for   the   design.
Two   methods   of   accomplishing   this   are   prototyping   and/or   installing   a   pilot   on   the   existing   network   to   identify   risks   and   weaknesses.
Before   performing   either   one,   a   detailed   test   plan   should   be   created.
This   test   plan   document   includes   an   equipment   list,   logical   and   physical   topologies,   testing   descriptions   and   procedures   as   well   as   results   and   conclusions.
You   have   been   contracted   by   the   ABC   Company   to   prototype   their   enterprise   network   following   specific   guidelines   as   outlined   in   their   requirements   document   below.
The   company   has   provided   you   with   the   network   topology   and   their   IP   addressing   scheme   they   propose   to   use   when   deployed.
You   notice   that   this   design   includes   redundancy   at   all   layers   in   this   hierarchical   model.
Out   of   several   choices,   you
decide   to   use   Packet   Tracer   as   the   tool   of   choice   for   prototyping   the   network.
Topology
© 2009 Cisco Learning Institute

CCNA   Discovery:    Designing   and   Supporting   Computer   Networks
Chapter   7   Case   Study
IP   Addressing   Table
Device   Name
R1   (PT   Router   6)
R1
R1
R1
R1
R2
R2
R2
R2
R1
R1
R2   (PT   Router   7
R2
R2
R3   (PT   Router   8)
R3
R3
R4   (PT   Router   9)
R4
R4
R5
R5
R5
S1   (PT   Switch   0)
S2   (PT   Switch   1)
S3   (PT   Switch   2)
S4   (PT   Switch   3)
ISP
ISP
ISP   Web   Server
PC1   (PT   PC0)
Mail   A   (PT   Server   4)
Interface
Fa0/0.1
Fa0/0.21
Fa0/0.22
Fa0/0.23
Fa0/1
IP   Address
172.18.2.1
172.18.21.1
172.18.22.1
172.18.23.1
172.18.0.17
S0/0/0   *    DTE   172.18.0.13
S0/0/1   *    DCE   172.18.0.25
Fa0/0.1
Fa0/0.21
172.18.2.2
172.18.21.2
Fa0/0.22
Fa0/0.23
172.18.22.2
172.18.23.2
Fa0/1   172.18.0.21
S0/0/0   *    DTE   172.18.0.10
Subnet   mask
255.255.255.0
Default   Gateway
N/A
255.255.255.0
255.255.255.0
N/A
N/A
255.255.255.0
N/A
255.255.255.252
N/A
255.255.255.252
N/A
255.255.255.252
N/A
255.255.255.0
255.255.255.0
N/A
N/A
255.255.255.0
255.255.255.0
N/A
N/A
255.255.255.252
N/A
255.255.255.252
N/A
S0/0/1   *    DTE   172.18.0.26
Fa0/0   172.18.0.18
S0/0/0   *    DTE   172.18.0.1
S0/0/1   *    DCE   172.18.0.9
255.255.255.252
N/A
255.255.255.252
N/A
255.255.255.252
N/A
255.255.255.252
N/A
Fa0/0   172.18.0.22
S0/0/0   *    DTE   172.18.0.5
255.255.255.252
N/A
255.255.255.252
N/A
S0/0/1   *    DCE   172.18.0.14
255.255.255.252
N/A
S0/2/0   *    DTE   205.100.80.1
255.255.255.252
N/A
S0/0/0   *    DCE   172.18.0.2
S0/0/1   *    DCE   172.18.0.6
VLAN1
VLAN1
172.18.2.3
172.18.2.4
255.255.255.252
N/A
255.255.255.252
N/A
255.255.255.0
255.255.255.0
172.18.2.1
172.18.2.1
VLAN1
VLAN1
172.18.2.5
172.18.2.6
255.255.255.0
255.255.255.0
172.18.2.1
172.18.2.1
S0/0/0   *    DCE   205.100.80.2
255.255.255.252
N/A
Fa0/0     68.0.0.5
255.0.0.0
68.0.0.6
255.0.0.0
172.18.23.10
255.255.255.0
172.18.21.3
255.255.255.0
68.0.0.5
172.18.23.1
172.18.21.1
© 2009 Cisco Learning Institute

CCNA   Discovery:    Designing   and   Supporting   Computer   Networks
Chapter   7   Case   Study
Mail   B   (PT   Server   6)
FTP   A   (PT   Server   2)
FTP   B   (PT   Server   3)
Web   A   (PT   Server   0)
Web   B   (PT   Server   1)
Tasks
172.18.21.4
172.18.22.3
172.18.22.4
172.18.23.3
172.18.23.4
255.255.255.0
255.255.255.0
255.255.255.0
255.255.255.0
255.255.255.0
172.18.21.2
172.18.22.1
172.18.22.2
172.18.23.1
172.18.23.2
Using   the   IP   addressing   table   above,   connect   all   devices   as   shown   in   the   topology   diagram   except   for   the   Gateway   Edge   Router   R5   and   ISP   devices.
Step   1:    Configure   the   hostnames,   interface   IP   addresses,   and   default   gateways   on   switches   S1,   S2,   S3,   and   S4,   PC1   and   all   of   the   servers.
Step   2:   Configure   basic   security   on   switches   S1,   S2,   S3,   and   S4.
Configure   privileged   mode   secret   password   and   require   login   on   VTY   ports   0   and   1   only.
Step   3:   Create   VLAN21,   VLAN22   and   VLAN23   on   switches   S1,   S2,   S3,   and   S4.
Assign   proper   switchport   roles   to   all   connected   interfaces   and   the   proper   VLAN   numbers   to   ports   that   connect   to   end   user   devices.
Step   4:   Set   the   STP   priority   on   switch   S3   to   4096   for   all   VLANs   to   make   it   the   primary   root   bridge.
Set   the
STP   priority   on   switch   S4   to   8192   for   all   VLANs   to   make   it   the   secondary   root   bridge.
Step   5:   Configure   Fa0/0   sub ‐ interfaces   and   inter ‐ vlan   routing   parameters   on   routers   R1   and   R2   with   the
IP   addresses   shown   in   the   table.
Step   6:   Configure   the   hostnames,   interface   IP   addresses   on   routers   R1,   R2,   R3,   and   R4.
Configure   basic   security   on   switches   S1,   S2,   S3,   and   S4.
Configure   privileged   mode   secret   password   and   require   login   on
VTY   ports   0  ‐  4.
Step   7:   Configure   EIGRP   routing   for   AS   100   on   R1,   R2,   R3,   and   R4   and   advertise   all   connected   networks.
Disable   EIGRP   automatic   route   summarization   on   all   routers.
Step   8:   Verify   full   connectivity   from   PC1   to   all   servers.
Make   sure   PC1   can   reach   the   ISP   Web   server.
Perform   basic   connectivity   tests   using   ping,   trace   route,   telnet,   relative   show   and   debug   commands.
Step   9 :   Simulate   a   failure   in   the   switched   portion   of   the   network   and   verify   and   observe   recovery.
Step   10:   Simulate   a   failure   in   the   routed   portion   of   the   network   and   verify   and   observe   recovery.
© 2009 Cisco Learning Institute