22
Case Study 2 – TeraBit Inc. DMico Johnson Hans Schmidt

Case Study 2 – TeraBit Inc. DMico Johnson Hans Schmidt

Embed Size (px)

Citation preview

Case Study 2 – TeraBit Inc.DMico JohnsonHans Schmidt

Outline• Introduction• Problem Statement• Goals and objectives• Existing Network Analysis• Recommended Changes• VOIP System• IP Address Design• MPLS Design• Security Design• Performance Design• Availability Design• Timetable• Budget• Evaluation• Conclusion• Appendix• Peer Evaluation

Introduction• Epical Systems Solutions is an Industry Leader in providing

businesses of any size network solutions that will:• Increase network usability • Reduce network costs• Increase profitability

• We offer a wide rang of services that can fit the needs of any organization large or small.

Problem Statement• Tera Research and Bit Computer Companies have merged as

one company, TeraBit Inc.• The Merge brings together network users that need to be

unified in the three major office locations of:• Chicago, Illinois• Mendota Heights, Minnesota• Chippewa Falls, Wisconsin

• The network services need to be consolidated and located to provide superior support and high availability to employees.

• The Merge has created the need for a Unified communications system, a green data center, a new IP addressing scheme, and a new protocols to connect the locations.

Goals and Objectives• Install a new VOIP system that will reduce costs by at least

60% in 5 years• The new VOIP system should be able to provide redundancy and

failover if the central location goes down• All existing fax machines need to be supported• Ensure acceptable call quality

• Migrate the Company to MPLS to connect the three locations• Introduce a Green Datacenter at the Chicago location• The new datacenter will reduce TCO and increase the ROI over a

5 year span.• Consolidate servers and increase utilization of servers• Consolidate the Datacenter with minimal downtime • The new data center will have 99% uptime

Goals and Objectives Cont.• Introduce a new IP address Scheme• Support IP summarization• Easily scalable

Existing Network Analysis• 3 network locations• Chicago – 4000 Users• Mendota – 1500 Users• Chippewa Falls – 1200 Users• 6700 Total users

• Outdated and expensive phone system• Non-green Datacenter• Over 500 servers• 80 servers with low utilization

Recommended Changes• Introduce a VOIP phone system to reduce costs and increase

availability• Implement QOS• Consolidate servers and Virtualize to increase overall server

efficiency• Put servers in a central location• Provide network and server redundancy• Utilize high efficiency cooling and equipment in the new

datacenter to reduce energy costs.• Introduce a new IP address scheme to support the converged

network• Use MPLS to connect the remote locations

VOIP System

IP Address Design

Internet\ MPLS Design• All of the locations would have outgoing internet lines. • Dedicated VPN tunnels to each location would allow for data

transfer between sites. • MPLS would provide WAN connection. • Since each site will have an outgoing internet pipe, if one site

loses internet connection MPLS will route that traffic to a different location who’s pipe is up utilizing IPSLA monitoring.

MPLS Design Visio

Security Design

Performance Design

Availability Design• Servers will be converted from physical to virtual at their current

locations. • Utilizing VMware's vCenter client, 3 VM clusters would be

configured representing each location. • Virtual servers would be copied from there current locations to

other locations using Vmware’s Syste Recovery Manager (SRM). • SRM would also provide automated failover when the current

site goes down and failback when the site was back up. • Each site would have outgoing internet line with vpn failover for

the redundancy if there was total MPLS service interruption• MPLS service would also provide failover if a site loss internet

connectivity.

Availability Design Visio

Timetable• The total network transformation will take place within a 2

year span:• Migrate all end user devices to new IP scheme in 2 months • Migrate employees to VOIP system within 6 months, with

approximately 2000 people in Chicago and 500 people in the other 2 locations respectively.

• Connect the three locations with MPLS within 3 months• Convert all physical servers to virtual servers (utilizing VMware's

conversion tool) ; should take 6-9 months• Build and move all servers to new datacenter location within 2

years

Budget Summary• IP Scheme Design and conversion Labor: $5,000• MPLS Conversion labor: $10,000• VOIP System Conversion Hardware: $35,000• VOIP System Conversion Labor: $10,000• Server Virtualization and consolidation Labor: $25,000• New Datacenter: $450,000• Move servers to new Datacenter Labor: $15,000

• Total cost: $550,000

Evaluation• VOIP system Migration: Low risk as new system can be built along

side current system resulting in immediate cutover with minimal down time. VOIP system will also be able to be tested before implementation

• Server virtualization and centralization: Low risk as servers can be virtualized while running resulting in minimal downtime as the cutover takes place.

• MPLS Conversion: • IP Scheme Conversion: This will have the potential for High impact

as it cannot be tested before hand. Implementation will take 2 days for each location to take in account for any static IP changes needed.

• Green Datacenter server move: Medium Impact. Servers will be down for physical moving, priority services and servers will have back ups in other locations.

Conclusion• We believe the new network design will be able to

accommodate you for the present as well as into the foreseeable future.

• The new network design will allow for near 24*7*365, uptime and will have a green IT Datacenter.

• The new network is both scalable and easy to manage.• The new network design will reduce the Total Cost of

ownership and Increase the return on your investment.• The Unified communication system and MPLS connections will

allow for all locations to be united and work seamlessly as if they were all one location.

Appendix

Peer Evaluation• Hans:• DMico: