Questions

Answer for:

Suggestions for a network case study?

Message 6 of 7

View entire thread
+
0 Votes
CIOandManager

Consider each aspect individually:
1. Network is to be secured: Externally that means a firewall, internally indicates either separate physical or logical networks to meet the requirements of the case study.

Based on the available information, the following assumptions are made:
Staff must be able to access email, file and printer services both cabled and wirelessly.
The computer lab will have different requirements from regular users and needs to be on a separate network
Given that there are only 16 staff users, the building is assumed to be quite small (probably only one to four PCs per floor.
It is assumed that there is a central vertical wiring duct

Given that, the physical cabling for all locations may be within 300 ft of the admin office in which you will have your server room/wiring closet, all cabling should be home run to that location (AND EACH CLEARLY NUMBERED at patch panel and at the wall outlet - as well as having a building diagram of where each is located).

Assuming one wireless access point can handle two floors, you are likely to need three of them (don't forget to mention configuring the channels at least three apart)

In all likelihood, the most elegant solution technically would be to have two 48 port managed switches, VLANs for admin, computer lab, student and surveillance, either a single high speed connection to the internet with throttling on the VLANs to ensure consisten access throughput for all users. Wireless access points need to be dual band with staff having access through one SSID, students the other.

And from a management and security access, a domain controller for the administrative functions (fully integrated with email, file and print services, database and security if you choose something like Microsoft Small Business Server 2011). The student acces to the printer can be managed through configuring as a workgroup.

The key aspect of this, however, is that it can be quite technically challenging to implement (and maintain and make changes to) the networking aspects discussed - which are quite sophisticated for a small environment such as this, therefore often a simpler setup with individual networks and separtae servers can be chosen. In addition if we start running VMWare ESX and multiple NIcs on the server it offers other signifiucant networing opportiunities - and challenges...