Submitted by: Submitted by mrspiderman
Views: 151
Words: 823
Pages: 4
Category: Other Topics
Date Submitted: 06/07/2014 08:11 AM
Support for High-Definition IP Cameras
DeVry University
NETW206: Introduction to Switching
Submitted to:
Professor:
Date:
Support for high definition IP-Cameras
To support Devry’s new high-definition IP-Cameras and to continue supporting Devry’s existing infrastructure I have put together a new network topology and design that should would sufficiently for our new system.
Topology
This topology quickly summarizes our new network structure. We are implementing a hierarchical design model with our network. Devices are shown for reference on the bottom row. The next row up is our Access layer, we can see that we are hoping to utilize eight switches for this network, all with at least one route that has logical bandwidth aggregation for backup and redundancy. In the second layer of switches we have our distribution layer, made up of 5 switches, also with physical and logical redundancies. In the very top layer we have our core layer, made up of three switches.
(Network Topology of Visio Document Attached to lab also.)
Network Segmentation
Our network segmentation will be handled via VLAN (Virtual Local Area networks) that we will manage in future design requirements. This should handle our properly segmenting our cameras from our different departments/workgroups. (Printers, Servers, Users, etc.).
Network Size and Scope
Devry is looking to setup a network that can handle 150 cameras and provide connectivity for 120 existing users, printers, and servers, with 20% expansion. With that, we took into assumption that that would mean 150 cameras would be connected immediately, with the ability to handle another 30 in the future, totaling 180 cameras. Then we would need to handle 120 existing devices with enough to handle an additional 24 for future expansion. Our Total network will need to handle 324 devices.
Our Infrastructure Support
Access Layer:
When looking at our 324 devices, we could see that we may be...