The Evolution of the Central Office

Transcription

1 The Gateway to Learning an All IP Network The Evolution of the Central Office -Where did all the DS-1s go? Presented by: Steven Senne, P.E. APRIL 27-30, 2014 ACE/RUS SCHOOL AND SYMPOSIUM 1

2 The New Central Office The Core of the Network is Now Transport/Pipe vs Class 5 Switch Voice is now just an application running on a Call Server. The TDM switch has been replaced by IP Routers, Switches and Application Servers. APRIL 27-30, 2014 ACE/RUS SCHOOL AND SYMPOSIUM 2

3 The New Central Office Data Centric using IP based Transport, Routing and Switching TDM based Core Technologies are being phased out as part of new service deployments or as existing equipment is replaced. SONET, DS1/3, OC-3/12/48, 4Wire TO, Digital Cross Connects. IP based Services are no longer a hobby but are ever increasingly becoming a bigger part of the revenue stream with SLA and QOS Requirements. APRIL 27-30, 2014 ACE/RUS SCHOOL AND SYMPOSIUM 3

4 The New Central Office Going Forward Class 5 switch replaced by Application Servers and Gateways. Gateways start to disappear in an all IP world with no transition to TDM required. Core and Edge Routers Redundancy and High Availability similar to the old TDM Switches. Size Reduction Power and Heat APRIL 27-30, 2014 ACE/RUS SCHOOL AND SYMPOSIUM 4

5 Software Defined Networks (SDN) Opportunity for Service Providers to evolve from being just a dumb pipe provider of bandwidth. Bandwidth on Demand/Services on Demand. End User provisioning of what they need when they need it from End to End. APRIL 27-30, 2014 ACE/RUS SCHOOL AND SYMPOSIUM 5

6 Software Defined Networking (SDN) Separation of the Control and Data planes in the network device The Data plane provide the hardware layer that is responsible for the actual routing of the IP packet. It may be generalized or specialized routing hardware The Control Plane is implemented as software Communicates with the Data plane standardized API or well defined APIs May control multiple SDN elements to allow end to end provisioning APRIL 27-30, 2014 ACE/RUS SCHOOL AND SYMPOSIUM 6

7 SDN Architecture APRIL 27-30, 2014 ACE/RUS SCHOOL AND SYMPOSIUM 7

8 SDN APRIL 27-30, 2014 ACE/RUS SCHOOL AND SYMPOSIUM 8

9 Why SDN SDN addresses the fact that the static architecture of conventional networks is ill-suited to the dynamic computing and storage needs of today s data centers, campuses, and carrier environments. The key computing trends driving the need for a new network paradigm include: Applications that commonly access geographically distributed databases and servers through public and private clouds require extremely flexible traffic management and access to bandwidth on demand. The Bring Your Own Device (BYOD) trend requires networks that are both flexible and secure. APRIL 27-30, 2014 ACE/RUS SCHOOL AND SYMPOSIUM 9

10 Why SDN Users expect on-demand access to applications, infrastructure, and other IT resources. Big data means more bandwidth: Handling today s mega datasets requires massive parallel processing that is fueling a constant demand for additional capacity and any-to-any connectivity. In trying to meet the networking requirements posed by evolving computing trends, network designers find themselves constrained by the limitations of current networks: APRIL 27-30, 2014 ACE/RUS SCHOOL AND SYMPOSIUM 10

11 Why SDN Complexity that leads to stasis: Adding or moving devices and implementing network-wide policies are complex, timeconsuming, and primarily manual endeavors that risk service disruption, discouraging network changes. Inability to scale: The time-honored approach of link oversubscription to provision scalability is not effective with the dynamic traffic patterns in virtualized networks a problem that is even more pronounced in service provider networks with large-scale parallel processing algorithms and associated datasets across an entire computing pool. Vendor dependence: Lengthy vendor equipment product cycles and a lack of standard, open interfaces limit the ability of network operators to tailor the network to their individual environments. APRIL 27-30, 2014 ACE/RUS SCHOOL AND SYMPOSIUM 11

12 SDN Implementation Challenges Immature standards, industry hype and vendor promises hindering SDN deployments. Slow transition to open API by vendors. What is needed is common language Element Adapters that act as a mediator to program multi-vendor networks. APRIL 27-30, 2014 ACE/RUS SCHOOL AND SYMPOSIUM 12

13 SDN Implementation Challenges Multi-Vendor Integrations between data plane and control plane elements. Well Defined APIs allow the creation of plugin software modules to interface vendor specific devices. Multi-Service Provider Integrations. Interoperability between multiple Service Providers with different SDN Control Plane platforms. Each providing a portion of the overall Ethernet circuit Embedded base of older non-complaint network equipment with large upgrade or replacement costs APRIL 27-30, 2014 ACE/RUS SCHOOL AND SYMPOSIUM 13

14 Initial SDN Implementations Access Network Metro Business Services Business WAN Interconnects Private Line Ethernet Services Wireless Cell Site Backhaul Tier III Service Providers network are not yet ready or are waiting on upstream providers to implement APRIL 27-30, 2014 ACE/RUS SCHOOL AND SYMPOSIUM 14

15 SDN More Reading Open Networking Foundation OpenFlow This specification covers the components and the basic functions of the switch, and the OpenFlow protocol to manage an OpenFlow switch from a remote controller. APRIL 27-30, 2014 ACE/RUS SCHOOL AND SYMPOSIUM 15

16 Network Function Virtualization Dedicated Hardware Devices are eliminated. Firewall, IPS/IDS, Session Boarder Controllers, Core and Edge routers, Content Delivery Networks. Replaced by generic hardware platform using standard off-the-shelf servers, storage and Ethernet Switching. Functions previously provided by dedicated hardware devices are now implement as virtualized software appliances. Resources can be allocated on the fly and as needed APRIL 27-30, 2014 ACE/RUS SCHOOL AND SYMPOSIUM 16

17 Questions? Contact Information: Steven Senne, P.E. CTO Finley Engineering Company, Inc. APRIL 27-30, 2014 ACE/RUS SCHOOL AND SYMPOSIUM 17