The Sunnyslope Lan Design Project

1
The Sunnyslope Lan Design Project

• Presented by
• Dr. Kenneth Holmes

2
Pre-amble

• Each semester must do a Threaded Case Study. This
  is an example of a case study done for semester
  1. It involves a School District that needs to
  have a network developed for it. This is only a
  model of how the process is done.

3
Sunnyslope Table of Contents
1.General requirements 2..Physic
al Design wiring 3..Logical
Wiring 4. Addressing Format 5..W
iring implementation/Cables 6.
Access-List (ACL)
4
Sunnyslope general LAN Implementation
Requirements

• Threaded Case Study for Sunnyslope Technical
  Specifications on Sunnyslope High School
  requirements.
• The Sunnyslope High School LAN designs will have
  two Local Area Networks. One will be assigned for
  administration usage and the other will be
  designated for student/curriculum usage.

5
Specifications continues

• 1.Extended Star topology- for direct connection
  between MDF and IDF
• connected to the MDF
• 2.Transport speeds 100baseFX (Fiber), 10BaseT,
  and 100BaseT
• 3.Horizontal Cable CAT5 UTP
• 4.Backbone Cabling Fiber Optic Multi-mode and
  will be compliance with EIA/TIA standards.
• 5. Each Central location will be assigned a Main
  Distribution Facility (MDF)- for LAN termination
  and POP (Point of presence) for WAN connection.
  Routers, switches, Hubs and other network media
  will reside on this location. IDF (Intermediate
  Distribution Facility) will also be used and will
  be directly connected
•    

6
Lan specifications (cont)

• Protocols Required layer 3 and 4 of the OSI
  model are TCP/IP and Novells IPX
• Network Media Routers, Switches, Hubs,
• Fast Ethernet 100 Mbps (802.3 IEEE Standards)
• Full Duplex- Able to simultaneously transmission
  between sending and receiving stations.

7
Lan Specifications

• Each room or classroom will have a minimal of 24
  workstations and be supplied with four (4) CAT 5
  UTP runs the data. One cable will be assigned to
  the instructor.
• CAT 5 UTP will be tested for end to end for 100
  MBPS bandwidth capacity.
• The minimal for initial implementation design
  will be 1.0 MBPS to any server host in the
  network

8
Logical wiring
9
Protocols TCP/IP
TCP/IP is the de facto standard for internetwork
communications and serves as the transport
protocol for the Internet, enabling millions of
computers to communicate globally. The function
of the TCP/IP protocol stack, or suite, is the
transfer of information from one network device
to another. In doing so, it closely maps the OSI
reference model in the lower layers, and supports
all standard physical and data link protocols.
The layers most closely affected by TCP/IP are
Layer 7 (application), Layer 4 (transport), and
Layer 3 (network).


10
Protocols TCP/IP

• IPX is the NetWare Layer 3 protocol used to route
  packets through interconnected networks. IPX is
  connectionless (similar to IP packets in TCP/IP
  networks) and operates within the same network
  implementation as TCP/IP, provided that you have
  a multi protocol router. Some of the
  characteristics of IPX are
• It is used in a client/server environment
• It uses the network.node IPX addressing structure
  
• Its logical address contains an interface MAC
  address
• IPX interface configuration supports multiple
  data-link encapsulations
• Novell RIP uses the distance-vector metrics of
  ticks and hops
• Service advertisement protocol (SAP) and Get
  Nearest Server (GNS) broadcasts connect clients
  and servers
• IPX uses distance-vector routing (such as RIP) or
  link-state routing (such as NetWare Link Services
  Protocol NLSP). IPX RIP sends routing updates
  every 60 seconds. RIP uses ticks (network delay)
  and hop count as its routing metrics and is
  limited to a maximum of 16 hops.

11
Protocol Novell-IPX

•  Novell IPX is a proprietary suite of protocols
  and includes the following 
• A connectionless layer 3 protocol that does not
  require an acknowledgment for each packet.  
• A Layer 3 protocol that defines the network and
  internode addresses. 
• Novell NetWare uses RIP to facilitate the
  exchange of routing information and SAP to
  advertise network services. NetWare uses NCP to
  provide client-to-server connections and
  applications, and SPX for Layer 4
  connection-oriented services. 
• IPX is the NetWare Layer 3 protocol and specifies
  a connectionless datagram, similarly to an IP
  packet in TCP/IP networks. 
• The default encapsulation types on Cisco router
  interfaces and their keywords are Ethernet
  (novell-ether), Token Ring (sap), and FDDI
  (snap). 
• Novell RIP is a distance-vector routing protocol
  and uses two metrics to make routing decisions
  ticks and hop count. NetWare's SAP allows
  network resources to advertise their network
  addresses and the services they provide. 
• GNS enables a client to locate the nearest server
  for login. 
• The router configuration for IPX routing involves
  both global and interface tasks

12
Sunnyslope Physical Design
13
LAN Logical Design
14
Wiring Implementation/Cable
Switch Ports Required
51 Classrooms x 24 Students 1224 switched
ports for students   51 Classrooms x 1 Teacher
51 switched ports for teachers   Total switched
ports needed 1275
Media Used   HCC to Comm Outlet 100BaseT 100
Mbs   VCC to VCC 100 BaseFX 100Mbs 2 Fibers
15
Access ListSunnyslope SchoolACCESS CONTROL LIST
(S) IMPLIMENTATION
Router exit Routergt exit  
16
Purpose of ACLsThe purpose of the ACLs is to
limit student access to the administration LAN
and to allow access for students to the Internet,
E-mail and DNS. The ACLs will also allow the
teachers and administration full access to all of
the resources of the WAN and the local LANs.
Finally the ACLs will act as a firewall to
protect the schoolsnetworks from intrusion from
unauthorized access from the WAN or the Internet
17
Addressing Schemes

• Sunnyslope School
• List of Subnets for the Curriculum LAN
• Class B Network 3 Bits borrowed
• For the 175.25.0.0 network with the subnet mask
  255.255.224.0
• Network Hosts per Subnet Broadcast Address
•  
• 175.25.0.0 175.25.0.1 to 175.25.31.254 175.25.31.2
  55
• 175.25.32.0 175.25.32.1 to 175.25.63.254 175.25.63
  .255
• 175.25.64.0 175.25.64.1 to 175.25.95.254 175.25.95
  .255
• 175.25.96.0 175.25.96.1 to 175.25.127.254 175.25.1
  27.255
• 175.25.128.0 175.25.128.1 to 175.25.159.254 175.25
  .159.255
• 175.25.160.0 175.25.160.1 to 175.25.191.254 175.25
  .191.255
• 175.25.192.0 175.25.192.1 to 175.25.223.254 175.25
  .223.255
• 175.25.224.0 175.25.224.1 to 175.25.255.254 175.25
  .255.255

•  

18

• Router Command Sequence
•  
• Expected Prompt Command
• Routergt enable
• Password
• Router config t
• Router(config) access-list 100 permit tcp
  175.30.0.0 0.0.255.255 175.25.0.0 0.0.255.255 eq
  http
• Router(config) access-list 101 permit udp
  175.30.0.0 0.0.255.255 175.25.0.0 0.0.255.255 eq
  smtp
• Router(config) access-list 102 permit udp
  175.30.0.0 0.0.255.255 175.25.0.0 0.0.255.255 eq
  dns
• Router(config) access-list 1 permit 175.25.0.0
  any
• Router(config) access-list 2 permit175.100.0.0
  any
• Router(config) int e1
• Router(config-if) ip access-group 100 in
• Router(config-if) ip access-group 101 in
• Router(config-if) ip access-group 102 in
• Router(config) exit
• Router(config) int e1
• Router(config-if) ip access-group 1 out
• Router(config) exit

19
The end