IT assignment
|
|
COURSE: IT Infrastructure |
MARK: /10 |
||
|
|
DEADLINE: 20th March 2016 |
COURSE CODE: IT 202 |
|
|
|
|
ASSESSMENT: Assignment |
BIL: 1 |
|
|
Designing a LAN Network with proper Configurations
Learning Outcomes: At the end of the assignment, student should be able:
· To have an understanding of the issues of procuring corporate networking
· To have practical experience in designing corporate networks including the specification of a network design
· To understand the IT infrastructure of any Enterprise including components of IT infrastructure
Company Name: (HealthCare Strategies Inc.)
Background
HealthCare Strategies Inc. was founded in 1998 to deliver a wide variety of healthcare and information technology services to home health agencies, hospices, hospitals, and other health-care providers in a cost-effective manner. The company focuses on the home health and hospice industry, offering services such as systems development; training and support; billing, collecting, and other financial processes and consulting. HealthCare Strategies also recently began offering agency management software products to clients.
In order for the company to provide services to clients located around the country, it must be able to deliver reliable and secure access to its server-based databases. Its clients rely on access to HealthCare Strategies systems to enter and view data from remote locations such as hospitals and clinics. They need to access a variety of applications to support essential business processes such as billing.
A big task is ahead for the IT Department at HealthCare Strategies: to develop a LAN network that provides connectivity to all users inside the company (approximately 500 users). Existing and new technologies will need to be considered and deployed not only to provide interconnectivity but also to support the existing and new applications that are and will be used within the company.
You have to complete this project by coming up with a strategy, putting into a plan, setting up LAN Design and its implementation strategies and eventually documenting the project close-out to ensure project reappraisal had been done to deem the project being successfully completed.
General Assumptions/Plans
· Building must use a structured cabling design.
· All analog leased lines will move to digital leased lines.
· Applications required across the company to minimize duplication and maintenance issues.
· Application servers can be located in any part of the company to best suit the application needs and technical skill logistics.
· Use of Wireless Mobile Computing is permitted.
Individual Deliverables (Research & Documentation by individual members)
Topology
Bus/Star/Ring/Mesh etc with High Speed Ethernet
Network topology is the arrangement of the nodes in a network (typically the computers). In bus topology, the nodes connect to a common backbone or trunk, called the bus. Data sent between the nodes travel along the bus and are received by all nodes at once. Star topology links all nodes of the network to a central node. Data transmitted between nodes are first sent to the central node, which then retransmits the data to the other nodes in the network. In ring topology, each node connects to another in a closed loop. Data travel from one node to the next, usually flowing through the network in a single direction.
We will chose Bus ,because Bus topology is fairly old news and you probably won't be seeing much of these around in any modern office or home.
With the Bus topology, all workstations are connect directly to the main backbone that carries the data. Traffic generated by any computer will travel across the backbone and be received by all workstations. This works well in a small network of 2-5 computers, but as the number of computers increases so will the network traffic and this can greatly decrease the performance and available bandwidth of your network.
As you can see in the above example, all computers are attached to a continuous cable which connects them in a straight line. The arrows clearly indicate that the packet generated by Node 1 is transmitted to all computers on the network, regardless the destination of this packet.In most hospitals, several networks will “overlay” this topology, each with its own cross connect, to keep medical and nonmedical networks separate. Different networks can also be physically separated by dividing equipment rooms into different areas. Hospital and network administrators may wish to apply a higher level of physical security to the medical network. This would prevent outside service providers, such as telephone or cable TV, from having access to the other network equipment and cabling.
Transmission Media
Cables & Media Selection etc.
Transmission medium is the means through which we send our data from one place to another. The first layer (physical layer) of Communication Networks OSI Seven layer model is dedicated to the transmission media, we will study the OSI Model later.
We chose cabal , because It is the most common type of telecommunication when compared with Shielded Twisted Pair Cable which consists of two conductors usually copper, each with its own color plastic insulator. Identification is the reason behind colored plastic insulation.
IT Infrastructure IT 202
Page 2 of 13
Advantages :
· Installation is easy
· Flexible
· Cheap
· It has high speed capacity,
· 100 meter limit
· Higher grades of UTP are used in LAN technologies like Ethernet.
It consists of two insulating copper wires (1mm thick). The wires are twisted together in a helical form to reduce electrical interference from similar pair.
Disadvantages :
· Bandwidth is low when compared with Coaxial Cable
· Provides less protection from interference.
The healthcare desktop has not undergone significant changes for a number of years. We continue to upgrade the operating systems, the applications, add new features, but the delivery not kept up with threats. We have moved the desktop or application and its data inside the datacenter where it is secure, but that only goes so far. We are seeing increased mergers and acquisitions in healthcare which often brings together disparate systems. In many locations, doctors are becoming contractors, or employees of larger health care systems. We are even seeing a surge in software development at some of the larger healthcare systems, some customer facing.
Bringing the data into the datacenter, some of the liability was removed. With no data on the device, the provider was able to move from system to system, with a similar, and more secure experience.
Unfortunately, this uncovers another flaw. With the traditional model of datacenter security, we secure the perimeter, as on the left, but once inside security is often far more relaxed. To resolve this, a micro segmentation such as on the right side can be deployed. For most environments though, doing this in hardware is to costly to deploy and maintain. Firewalls everywhere requires managing in many places, and updating policies in many places.
Security built in not bolted on
In order to give a healthcare provider, the security they need, and to do so at the scale required, we need to look at a combination of the two models. We need to bring the data in the datacenter, protect the physicians and give them an experience they are going to be excited to use, make it better not just more secure. We also need to secure the traffic once it is brought inside the datacenter. Not a new concept, just applying datacenter micro segmentation to the virtual desktop.
In reviewing the design, nothing is being removed from a traditional VDI design, physical networking components are still present. The change comes is the green network icons represent software routers and firewalls which enable us to simplify the design. Notice multiple layer 3 domains, not just VLAN’s, but full L3 domains enabling us to completely isolate traffic. The firewalls encapsulate each virtual machine, not simply an operating system firewall, wrapping the virtual machine in a container and allow inspection and security at the actual VM level
Finally we will present all work as Medium HealthCare Strategies Architecture
The medium clinic architecture provides for flexibility to support a wide range of clinic operations under a common and cost-effective networking model. This model stresses the adaptability of the architecture to multiple functions and data types, all brought under a common control structure so the healthcare security requirements can be controlled either at the clinic or centrally across the larger organization. The medium clinic architecture is optimized for efficient business operation without sacrificing centralized controls and layered security control to best resist breach.
Notes:
· All sections above should include proper evaluation of alternatives
· An effort to ensure there is standardization must be indicated in all designs.
· Use appropriate diagrams wherever possible to illustrate your proposals.
e.g. The network ‘design’ and ‘topology’ and other aspects should definitely have diagram/s to indicate how LAN has been designed and implemented.
Important:
This is a team effort. All members must be fully informed about and involved in all aspects of the project plans. Individual members will be responsible for researching and documenting certain discrete portions of the project. All findings must be shared and discussed and work on the project should be done on a collaborative basis.
Final documentation and discussion of each section is what is expected individually.
Deliverables
Based on the above deliverables, you are required to: -
a) Provide a hardcopy and a softcopy of the document indicating each member’s area of responsibility.
This includes specifications for high speed technologies, cabling, topology and architecture, protocols and proposed LAN design. An overall diagram must be provided, showing the high speed technologies, devices and topology used.
Justification must be provided for each technology proposal made with rough estimates of cost to be provided. The purpose of the report is to convince management that you know what you are doing, and can successfully implement the solution to keep the company operational in any situation.
You can make assumptions in support of your report, but these assumptions MUST BE STATED.
Your hardcopy report must be typed using Microsoft Word and bound in A4 sheets. Expected length is 3,000 - 5,000 words, with as many illustrations as possible and with all references clearly indicated and provided. You can use a diagramming application, e.g. Visio, for diagrams and copy them to the WinWord Document.
Your softcopy should also be in Microsoft Word or pdf compatible format
Note: THIS ASSIGNMENT IS TO BE CARRIED OUT IN GROUPS OF 4 MEMBERS.
· Your areas of responsibility must be managed and organized per the deliverables with each member of a group being responsible for one of the deliverables stated above.
· These areas of responsibilities must be provided in a summarized workload matrix and marking matrix, indicating the individual members in the team. This should be inserted at the bottom centre of the cover page of the document. Please Note: Failure to include this matrix on the documentation cover will result in a mark deduction of 10% of the group marks.
· The separate individual sections of the deliverables should be clearly separated by a section dividing sheet that clearly indicates the author of that section.
· Each individual section must use proper citing techniques and have a separate research references list/bibliography etc. at the end of that section
· Your report(s) must combine all the deliverables in one coherent document.
References
1. McNurlin, Barbara; et al. (2009). "Information Systems Management in Practice (8th ed.)". Prentice Hall.
2. O’Brien, J (1999). Management Information Systems – Managing Information Technology in the Internetworked Enterprise. Boston: Irwin McGraw-Hill. ISBN 0-07-112373-3 .
3. Bird, M. (2010). Modern Management Guide to Information Technology. Create Space.
4. Talbot, Chris, “HP Adds to Converged Infrastructure Lineup,” ChannelInsider, June 7, 2011.
7. Harris, Derrick, "Can Open Converged Infrastructure Compete?" GigaOM, October 10, 2010.
8. Oestreich, Ken, "Converged Infrastructure," CTO Forum, November 15, 2010.
9. Golden, Bernard, "Cloud Computing: Two Kinds of Agility," CIO, July 16, 2010.
10. Veen, Annelies van der; Jan van Bon (2007). Foundations of ITIL V3. Van Haren Publishing. ISBN 978-90-8753-057-0 .