Access over 20 million homework & study documents

search

NTC 360 Updated_NetworkArch_Outline

Type

Homework

Rating

Showing Page:
1/5
Network Architecture
I. Overview of current network Architecture
A. Current State of Network Architecture and connections – Portals, Web
servers, etc
B. What needs to be changed and why?
II. Proposed Architecture and Topology for the network
A. User Computers
B. Satellite servers
C. Main server cluster
D. Internet and Infrastructure
E. Back up/ contingency plans
III. Equipment that will be used in the new network
A. Routers
B. Domain
C. DNS
D. Firewalls
E. Internet
F. Back up equipment
IV. Costs and rough implementation Estimates
A. Costs of Equipment Purchase
B. Costs of Service Contracts
C. Implementation Estimates.

Sign up to view the full document!

lock_open Sign Up
Write up
Current State of Network Architecture and connections
The current network architecture of Huffman Trucking’s network is very outdated.
Currently there are four geographical locations and two individual networks at each
location, one office network and one plant network. These networks are all configured
differently, with different equipment and very little consistency in architecture between
each network. All the office networks connect to the Internet, but since California holds
the web server, there is no firewall. Both Missouri and Ohio plants have connections
through a fractional T1, but California has a standard AOL model connection (dial up).
The wiring infrastructure is consistent across the networks, but is rated at Cat3. There is
also no clear voice network. California runs off a standard PBX, whereas Missouri and
Ohio both have Avaya digital switches. The computers in the company range from
Windows 3.1 boxes to Windows XP.
What needs to be changed and why?
One of the most important characteristics of a good IT infrastructure is
consistency. Most of the computers need to be the same, the servers need to be the same
throughout the network, and the voice equipment needs to be consistent. The first thing
that needs to change is all computers need to be running Windows XP (with the exception
of the Macs). The technology of Windows 3.1 and Windows 98 is to antiquated for
today’s technology. Having all Windows boxes with XP will help ensure easy

Sign up to view the full document!

lock_open Sign Up
manageability, data surety, and when problems do arise, XP can be supported and
repaired. The next change arises from the physical infrastructure of the networks. Cat 3
is old and slow, the equipment made for it isn’t manufactured anymore, therefore, finding
support for any of this equipment will be hard to find and expensive. Connections
between locations and to the internet need to be consistent. Using AOL and modems at
one location, while having a T1 at others doesn’t give a very efficient operations flow.
The networks all seem to operate independently, so if one site goes down, nothing is lost
(unless you are at that site), but what about communications and load balancing between
the sites during normal working hours?
Proposed Architecture and Topology for the network
Team D is proposing a total reorganization of Huffman Trucking’s Network
Architecture based on the reasons stated above. This new network will have scalability,
integrity, and easier manageability. It will also have to the ability to load balance
between sites if one or multiple sites go down. The topology itself will be a star
topology. This will help with troubleshooting the locations of problems while at the same
time not crashing the network. The network itself will be a Windows Domain network.
Servers
At each geographical location there will be a cluster of 3 servers, with 6 servers at the
main headquarters**. The Satellite clusters will have 3 main functions. One server will
act as a secondary Domain Name Server(DNS), the second server will be a local file
storage and printing server. The third server will act as a fall over/backup for the other
two. The main server cluster located at Headquarters will have one Server as the primary

Sign up to view the full document!

lock_open Sign Up

Unformatted Attachment Preview

Network ArchitectureI. Overview of current network ArchitectureA. Current State of Network Architecture and connections - Portals, Web servers, etcB. What needs to be changed and why?II. Proposed Architecture and Topology for the networkA. User ComputersB. Satellite serversC. Main server clusterD. Internet and InfrastructureE. Back up/ contingency plansIII. Equipment that will be used in the new networkA. RoutersB. DomainC. DNSD. FirewallsE. InternetF. Back up equipmentIV. Costs and rough implementation EstimatesA. Costs of Equipment PurchaseB. Costs of Service ContractsC. Implementation Estimates.Write upCurrent State of Network Architecture and connectionsThe current network architecture of Huffman Trucking's network is very outdated. Currently there are four geographical locations and two individual networks at each location, one office network and one plant network. These networks are all configured differently, with different equipment and very little consistency in architecture between each network. All the office networks connect to the Internet, but since California holds the web server, there is no firewall. Both Missouri and Ohio plants have connections through a fractional T1, but California has a standard AOL model connection (dial up). The wiring infrastructure is consistent across the networks, but is rated at Cat3. There is also no clear voice network. California runs off a standard PBX, whereas Missouri and Ohio both have Ava ...
Purchase document to see full attachment
User generated content is uploaded by users for the purposes of learning and should be used following Studypool's honor code & terms of service.

Anonymous
I was stuck on this subject and a friend recommended Studypool. I'm so glad I checked it out!

Studypool
4.7
Trustpilot
4.5
Sitejabber
4.4