1 / 45

Dimension Network: Impact of Cloud Computing

Dimension Network: Impact of Cloud Computing. SEIS 645 Joel Bonstrom , Paul De Rocher , Phil Erickson, Faizan Khan, Gemma Misolas. Overview. Introduction Company Attributes Current State Summary Future State Summary. OSI Layers Impact Physical Layer Data Link Layer Network Layer

bambi
Download Presentation

Dimension Network: Impact of Cloud Computing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Dimension Network:Impact of Cloud Computing SEIS 645 Joel Bonstrom, Paul De Rocher, Phil Erickson, Faizan Khan, GemmaMisolas

  2. Overview • Introduction • Company Attributes • Current State Summary • Future State Summary • OSI Layers Impact • Physical Layer • Data Link Layer • Network Layer • Transport Layer • Application Layer • Conclusion

  3. Introduction • Project analysis on the impact of network structure of company Dimension. • Moving company applications from internal datacenters to an external cloud computing environment. • Applications considered for moving to cloud: • Unified Communications (Voice, Video) • Desktop applications (E-mail, IM, Sharepoint, Office) • Internet DMZs

  4. Company Attributes • 100,000 employees • 40 countries • 2000 branch offices • Plant locations in all 4 regions • Headquarters in Minneapolis, MN • Data Center in Dallas, TX • 97,000 users @ 1900 locations use PBX telephones • 3,000 users use IP telephony. • VPN access for external employees

  5. Current Data Network

  6. Current Telecommunications System

  7. Current Assumptions • 4 Regions • North America – Dallas, TX, USA • Latin America – Rio de Janeiro, Brazil • Europe/Middle East/Africa – Paris, France • Asia/Pacific – Hong Kong, China

  8. Current Assumptions (con’t) • 17% concurrently use voice • 15% concurrently use e-mail. • 1-2% concurrently use video. • 50% of employees are actively working at a time due to different time-zones. • Every employee has access to desktop applications • Private IP addressing scheme used with ample additional room for future. • Fiber-optic (SONET) network for connections into MPLS WAN. • Ethernet Layer 2 protocol used across LAN and WAN.

  9. Current Assumptions (con’t) • Uses a private IP addressing scheme (10.0.0.0) • Standard Ethernet LANs (10 Mbps) already in place. • Servers upgraded to latest hardware and OS, and max size 65k transport layer buffers. • All datacenters have UPS back up power. • 1 DMZ in each reason for extranet and internet browsing. • Fully established Desktop apps and Communications are transferrable from internal datacenters to cloud without major impact. • Live HQ video streaming to multiple targets is not provided. • Platinum level SLA with MPLS WAN provider meeting required RTO and RPO.

  10. Current Assumptions (con’t) • VPN Split tunneling not allowed. • using Autonomous system inter-domain path vector routing (BGP); will use this to provide routing once moved to cloud. • Bluetooth usage only for keyboards, mouse or voice connection to local devices. • Some wireless LAN access at most company locations. • UDP and TCP transport protocols are in place. SCTP is not being used. • RTO & RPO exist so company can provide required level of business continuity. • 3000 users (3% of total employees) in 100 locations (5% of total branches) which have adopted the IP telephony • Desktop apps include MS Office Suite; data artifacts saved in network storage devices. • Majority of business applications are hosted in the primary datacenter in Dallas, TX

  11. Future Data Network

  12. Cloud Network Picture

  13. Future Assumptions • Regional data centers in Asia Pacific, Latin America, and Europe-Mideast-Africa will be eliminated. The primary data center in Dallas will remain • All 3 categories of services will be moved into the cloud • Unified communications (IP Telephony, video conferencing, etc.) • Desktop applications • Internet DMZ – NA Cloud, Asia- Pacific Cloud & Dallas Datacenter • Business applications will continue to be hosted at the Dallas data center

  14. Future Assumptions (con’t) • Two cloud instances will replace regional data centers to provide closer physical proximity and performance. Cloud will host all systems previously housed at regional data centers including voice, video, desktop applications, & DMZ • Sites continuing to rely on PSTN service will be upgraded to IP telephony. • Approximately 50,000 employees at all 2000 sites • This upgrade will allow us to leverage our MPLS WAN connections between all company sites and employees and greatly reduce our reliance on the PSTN

  15. Future Assumptions (con’t) • Cloud instances will be connected by MPLS into the Dimension MPLS WAN private network • Since fiber optic cable has unidirectional propagation, we will need 2 fiber optic connections per site to WAN connection, as in the past when we’ve upgraded sites to fiber optic service. • All Dimension phones will be move to IP Telephony and all PBX systems eliminated • Level of voice, video, desktop usage etc. remains the same from the current state

  16. Future Assumptions (con’t) • Level of wireless access will remain the same • Level of VPN access by remote employees will remain the same • Cloud servers will be IaaS/PaaS servers with full administrative control over cloud environment • Platinum level SLA will be established with the Tier 1 Service provider providing cloud services including full UPS power backup, 99.999% availability, etc. and meeting the required Recovery Time Objectives (RTO) & Recovery Point Objectives (RPO)

  17. OSI Layer: Physical Joel Bonstrom, Paul De Rocher

  18. Physical: Current Situation • Desktop and business applications hosted in primary data center, adequately served by SONET STS-1 fiber optic cable along with Cat5 and fiber optic cable. • Hybrid voice and video solution, served in most cases by DS-1 and DS-3 service and in a few cases by SONET STS-1 fiber optic cable • Four regional data centers each hosting DMZs

  19. Physical: Future Situation • Continue to host business and desktop applications from single primary data center • Aggressively pursue IP Telephony for voice and video • Move DMZs to two cloud instances and eliminate three regional data centers

  20. Physical Layer: Effects • Upgrade bandwidth in increase traffic areas due to transfer to cloud. STS-1 service to STS-3 service throughout the network • Upgrade switches to level 3 • Install new IPT telephones.

  21. OSI Layer: Data Link GemmaMisolas

  22. Data Link: Current Assumptions • Protocol • Dimension networks utilize the Standard Ethernet protocol over its STS-1 lines for wired connectivity • The implementation uses digital signaling or baseband at 10Mbps using the Manchester encoding • LANs • Wired Full-duplex switched Ethernet Increases capacity from 10 Mbps to 20 Mbps Star topology • Wireless Basic service set (BSS) Extended service set (ESS) Uses CSMA/CA access method Uses point coordination function (PCF) for time-sensitive transmissions • Virtual LANs VLANs for data traffic only.

  23. Data Link Current Assumptions (cont.) • WAN • Dimension’s wide area network run in SONET/SDH technology • Ethernet over SONET/SDH the protocol running in WAN network using mesh topology configuration • Others • Both telephone and email systems use gateways to route internal and external voice or email traffics • Dimension does not subscribe to any satellite service

  24. Data Link Layer Impacts • New VLANs configured to provide VLAN separation of voice and data • Eliminate layer 2 switches

  25. Data Link: Future State There are no changes on the current state of Dimension’s Data Link layer except for the following: • Upgrade to 100 Mbps Fast Ethernet Layer 2 protocol using the 4B5B with NRZI encoding schemes over the STS-3 lines • Faster data rates to accommodate increased traffic due to IPT • Segregation of voice traffic in the LAN • All non voice traffic will go through existing VLANs while voice traffics go through separate VLANs. • Data frames are left untagged, the voice frames are tagged. • For the purpose identifying which packets will need Quality of service (QoS) and monitor the traffic separately • To minimize distortions on voice traffic if there are broadcast data traffic • To safeguard voice data packets from viruses

  26. Data Link Future State (cont.) • Layer 2 switches will be replaced by layer 3 switches • To support QoSprioritization of voice and video traffic on the core switch for the entire LAN • To support the creation of VLANs with multiple ports to allow traffic to be routed between VLANs

  27. OSI Layer: Network Faizan Khan

  28. Network Layer: Current State • Only IPv4 addresses used. • 10.0.0.0 IP addressing scheme used. • All incoming and outgoing packets pass through NAT Router. • 3000 users use IPT. • Traditional routers, Layer 2, and Layer 3 switches are used for directing traffic in Dimensions LAN. • Company Intranet is run on Layer 2 switches.

  29. Network Layer: Future State No significant changes on the current state of Dimension’s Network Layer except for the following: • New private IP addresses will be required for VoIP. • Existing IP addresses will not be re-numbered. • Since ISP is not changed, NAT global address for external packet routing will not be changed.

  30. Network Layer: Future State con’t • Communications over IP is less reliable  lower QoS. • Just IP is not well-suited for IPT voice transmission; will require support from Transport and Application layers to provide required QoS. • Higher bandwidth will be required to increase QoS by lowering latency. • New IP addresses will be IPv4 scheme, not IPv6.

  31. Network Layer: Future State con’t • All protocol will remain the same: IP, IGMP, ICMP, ARP, and RARP. • A smarter switch is required. • Layer 2 switches  Layer 3 switches; can be placed anywhere on the network: handling high LAN traffic. • High-performance packet switching, high-speed scalability, quality of service, lower latency, and security

  32. OSI Layer: Transport Phil Erickson

  33. OSI Layer: Transport • Transport Layer Assumptions • Existing UDP & TCP protocols continue • Existing port numbers continue • TCP window sizes already configured to 65K byte (16 bits) RWND windows

  34. OSI Layer: Transport • Transport Layer Impacts • Real-time Transport Protocol (RTP) on top of UDP • unreliable connectionless protocol is acceptable and required • SCTP protocol for VoIP and other streaming traffic could be considered in the future

  35. Congestion & Quality of Service (QoS) • Congestion & QoS • Introduced Additional bandwidth introduced • Voice traffic itself is not “bursty” • End-to-end QOS across both LAN and WAN • Both WAN and LAN must be Layer 3/4 aware to provide this end-to-end QoS • Weighted Fair Queuing QOS scheme • Interactive Video, Audio for IPT as top priority • H.323 including Control protocol over TCP

  36. OSI Layer: Application • Application Layer Assumptions • MPLS private network connection to cloud supports applications with minimal impact • Existing IPT application currently in place for a small number of users will be expanded to include the entire company.

  37. OSI Layer: Application • Application Layer Impacts • Application protocols • H.323 Application Protocol for IP Telephony • IP Telephones supporting H.323 • SIP trunking could be considered in the future

  38. On Net IPT Call

  39. Off Net IPT Call

  40. Security & Business Continuity • Security • IaaS and PaaS Cloud servers allow administrative control • MPLS for connection to the cloud • Don’t need VPN for cloud connection • Mitigates eavesdropping concerns • Firewall added between cloud and private network as “defense in depth” • DMZ’s in Cloud and Dallas datacenter • Existing SSL/TLS unchanged • Business Continuity • Platinum level Cloud Provider SLA service • Meet existing RTO & RPO

  41. Summary & Conclusion • Transfer of the 3 categories to Cloud had minimal to no impact Dimension's network structure. • Primary impact on moving from traditional PBX to IP Telephony (IPT) system.

  42. Summary & Conclusion (con’t) • Physical Layer Impacts of IP Telephony in the Cloud • New IP Telephones • No new Ethernet jacks or cables • Plug phones into existing jacks and plug PCs into phones • STS-3 optical cables to carry increased traffic • Data Link Layer Impacts of IP Telephony in the Cloud • Upgrade to Fast Ethernet network protocol • New VLANs configured to provide VLAN separation of voice and data • Eliminate layer 2 switches

  43. Summary & Conclusion (con’t) • Network Layer Impacts of IP Telephony in the Cloud • Add level 3 switches • Configure QoS to provide proper priority for voice traffic • Require additional IP addresses allocated from our private network address scheme for up to 100,000 new IP phones • Transport Layer Impacts of IP Telephony in the Cloud • Transport protocols • RTP on top of UDP • Quality of Service • Need end-to-end QOS across both LAN and WAN with level 3 awareness • Weighted Fair Queuing QOS scheme

  44. Summary & Conclusion (con’t) • Application Layer Impacts of IP Telephony in the Cloud • Applications in the Cloud • Move Unified communications, Desktop applications and DMZ categories into the cloud • Application protocols • H.323 used for IPT • Security • IaaS/PaaS administrative level control • MPLS secure private network • Defense in depth through firewalled connection to the cloud • Business Continuity • Platinum level SLA service with Tier 1 Cloud provider will meet existing Recovery Time Objective (RTO) and Recovery Point Objective (RPO)

  45. Questions

More Related