Javier Antich jantich@juniper Iberia SP SE Manager

1. Next Next Next Generation Networks Jornadas Técnicas Rediris Alcalá de Henares – Noviembre 2008 Javier Antich jantich@juniper.net Iberia SP SE Manager

2. Goals Understand which are todays challenges and context that determine the requirements for the next generation networks Describe the new technologies that will help addressing the challenges introduced. Highlight the growing relevance of Energy efficiency and IP&Optical transport convergence as techniques to reduce OPEX Present how Juniper is sensible with these challenges and how we can help addressing them.

3. Today´s Generation Challenges

4. The general climate…

5. Network Trend #1: The Grand Exodus • Data/Apps are getting consolidated into a few Data centers • People are getting scattered all over the world Work Force Globalization Data Center Branches &Campuses Data Center Consolidation • RESULT AT DATA CENTER: • Demand for • Massive performance/scale • Carrier-class reliability • Green designs • Virtualization of everything • RESULT AT BRANCH/CAMPUS: • Demand for: • “All-in-one” integrated appliance • Remote deployment and management on a large scale

6. Network End Points Trend #2: The Blurring Work / Home • People are taking work home • People are bringing home-expectations to work Branches &Campuses Data Center • RESULT AT BRANCHES & CAMPUSES: • Demand for: • Securing corporate laptops even inside the “trusted” perimeter • Dual-mode WLAN or Enterprise Femto-cells • RESULT AT END POINTS: • Demand for: • A bewildering array of “unapproved” end-point devices • Un-tethered mobility • Data Leakage Prevention

7. Data Center Content Service Provider Network Trend #3: The Blurring of Company / Cloud • Companies are putting their applications in the cloud (“SaaS”) Branches &Campuses • RESULT AT CONTENT SP: • Demand for • DPI for XML/SOAP • Heightened QoS and acceleration

8. Reality iTunes creates > 200 connections Assumptions Single application = single connection Underlying Functionality Multiple connections are established to retried map segments Segments are then pieced together to form a whole map Infrastructure Requirements Must support multiple connections at once Network delays result in grey map areas until graphics are loaded Did you know this? Lack of NAT sessions

9. IPv4: The End of the Road Comes into View • Only 15% of IPv4 space remains available • Depletion projected late 2010 Source: www.tndh.net/~tony/ietf/ipv4-pool-combined-view.pdf Source: www.potaroo.net/tools/ipv4/

10. Three Trends in Networking • TDM is past its prime • Built primarily for voice, and adapted reasonably successfully for leased lines, fine-grained TDM (PDH/SDH) is increasingly irrelevant for Next Generation Networks • TDM is also very expensive on a cost/Gbps basis • Packet transport is on the rise • There is recognition that transport must focus on packets, not bits • There are multiple approaches, and a lot of confusion out there • Interest in the Packets+Photons Phenomenon is growing • There is also recognition that the worlds of packets and of optical transport must come together • Again, there are several approaches, and no clear way forward What Should Be Done?

11. Energy Savings • “The cost of power consumption by data centers doubled between 2000 and 2006, to $4.5 billion, and could double again by 2011” according to the U.S. government. BussinessWeek March2008

12. Breakdown of Network Downtime Maintenance Events System Errors Innovation Operations Human Error

13. IP Video/Voice IP Data IP Data Traffic CAGR of 40% IP Video/Voice CAGR of 85% 2004 2005 2006 2007 2008 2009 • Joost • Zattoo • And many more…

14. CONVERGENCE OPERATIONAL COSTS RELIABILITY SCALABILITY Challenges for the Next Generation Networks

15. OPERATIONAL COSTS RELIABILITY SCALABILITY Challenges for the Next Generation Networks CONVERGENCE

16. Scalability on the Data Plane (Multichassis)

17. Scalability and stability in large scale networks Absolut: Multi-chassis 25 Tbps System T1600 T1600 #1 #16 Switch Fabric Chassis 1600 Gbps 1600 Gbps #2 #15 25.6 Tbps Non-blocking #3 #14 #4 #9 #13

18. Control Plane Scale and Virtualization

19. Shared Control Plane SVC 1 SVC 2 SVC 3 SVC n Control Plane Forwarding Plane Router Stability Processing Requirements Scale SVC 1 SVC 2 SVC 3 SVC n Scalability and Stability in Large Networks Control plane can become a bottleneck • Popular notion that convergence has happened is false. It only happened at the forwarding plane – not the control plane • Each service has diverse requirements (TE, QOS, security, growth rates) • Requires multiple control planes • Since today’s equipment only supports one control plane, Service Providers are forced to roll out multiple subnets, or risk compromising scale, stability and/or security • As more new services are introduced this leads to escalating CapEx and OpEx

20. Control plane multiplicity changes that dynamic and fulfils the true promise of convergence Shared infrastructure Services are decoupled from network New services can be introduced without building a new subnet Each services can be managed and controlled individually Service introduction is swift and with reduced risk Each service now runs on its own “Virtual Service Network” Lower CapEx, lower OpEx, Lower risk Independent Control Plane SVC 1 SVC 2 SVC 3 SVC n CP1 CP2 CP3 CPn Juniper Control System Forwarding Plane Router Scale Stability Processing Requirements SVC 1 SVC 2 SVC 3 SVC n Scalability and Stability in Large Networks Control plane multiplicity

21. Virtualization Continuum Delivered Next Steps … Logical Routing Protected System Domain Shared hardware platform; Separate routing instances Shared hardware chassis; Dedicated routing resources PLogicalRouter PLogicalRouter PLogicalRouter VerticalConsolidation RE Pair Horizontal Consolidation RE Pair PSD1 PSD2 PELogicalRouter Safari • Dedicates and isolates forwarding and control plane resources • Run independent versions of JUNOS • Share uplinks across virtual nodes • No customer facing slots • Flexibility and scalability of investment • Isolates routing protocols & interfaces • Enables hardware reuse – shared uplinks, efficient inter-LR forwarding • Deployed for service separation, additional security, managed service, substitute for physical route

22. LR_1Service A LR_2Service B LR_3Tier 2/3 ISPs RI_1: ISP A RI_2: ISP B Scalability and Stability in Large Networks JCS 1200: A Radically New Architecture 2008 Juniper takes control plane architecture to the next level by physically decoupling the forwarding and control platforms T1600 TX Matrix 2007 100 Gbps/slot Core IP/MPLS forwarding density M40 2004 First multi-chassis routing system 1996 Juniper pioneers the separation of control and forwarding plane 2003 Multiple control instances running on one router Logical Routers

23. Example: Virtualized Routing System for Collapsed POP NETWORK CORE NETWORK CORE PRIVATE PEERING INTERNET PRIVATE PEERING INTERNET Core Routers Consolidated Router Internet Router Safari Peering Router 20-30% CapEx Reduction PSD 1: Core Aggregation Router PSD 2: Aggregation Aggregation Router PSD 3: Private Peering PSD 4: Route Reflection Edge Routers IP/MPLS CUSTOMERS IP/MPLS CUSTOMERS

24. 40/100 GEIEEE 802.3ba

27. 100 GE • Juniper is an active participant in the 100 GE standardization effort. • We are the only routing vendor to currently support 100 Gbps/slot of minimum packet sized Ethernet traffic and are working on support of 100 GE interfaces • Providing 100 GE in a timely fashion, commensurate with ratification of the technical details of the 100 GE standard, is a significant part of this effort within our product development team • Target delivery: 2010

28. OPERATIONAL COSTS RELIABILITY SCALABILITY Challenges for the Next Generation Networks CONVERGENCE

29. Breakdown of Network Downtime Maintenance Events System Errors Innovation Operations Human Error

30. Nonstop Operation

31. PrimaryRouting Engine Active StandbyRouting Engine Nonstop Operation Nonstop Routing • Self-contained solution • No requirement for peers to support • No disruption of protocol adjacencies • Switchover is transparent to neighbors • Stateful replication of adjacency information on standby RE • Routing updates, hello messages, adjacency state, etc. • Dual active protocol sessions • Standby RE is fully active and can immediately take over sessions • Switchover is not dependent on stable topology • Topology changes can occur during switchover Continuous Systems

32. In-Service Software Upgrade (ISSU) • What is our definition of ISSU? Daemon 2 Daemon 3 Daemon 1 Daemon n Routing Engine Kernel Packet Forwarding JUNOS 9.0 Physical Interfaces High-levelArchitecture View

33. Is this ISSU? JUNOS 9.2 • Upgrade of an individual module • NO: this is not true ISSU!! Daemon 2 Daemon 3 Daemon 1 Daemon n Routing Engine Kernel Packet Forwarding JUNOS 9.0 Physical Interfaces High-levelArchitecture View

34. Daemon 2 Daemon 3 Daemon 1 Daemon n Kernel Is this ISSU? • Upgrade of control plane software only • NO –this is not true ISSU! Daemon 2 Daemon 3 Daemon 1 Daemon n Routing Engine Kernel JUNOS 9.2 Packet Forwarding JUNOS 9.0 Physical Interfaces High-levelArchitecture View

35. Daemon 2 Daemon 3 Daemon 1 Daemon n Daemon 2 Daemon 3 Daemon 1 Daemon n Routing Engine Routing Engine Kernel Kernel Packet Forwarding Packet Forwarding JUNOS 9.0R2 Physical Interfaces Physical Interfaces Is this ISSU? • Upgrade within same major release • Example: 9.0R1 to 9.0R2 • Yes, this is possible with ISSU, but this is not always enough! JUNOS 9.0R1 High-levelArchitecture View

36. Daemon 2 Daemon 3 Daemon 1 Daemon n Routing Engine Kernel Packet Forwarding JUNOS 9.0 Physical Interfaces In-Service Software Upgrade (ISSU) • Our definition of ISSU: • Upgrade the entire code on the router… • Routing Engine • Packet Forwarding Engine • Physical Interfaces • …with minimal disruption to traffic • Can even go from one major release to another! Daemon 2 Daemon 3 Daemon 1 Daemon n Routing Engine Kernel Packet Forwarding JUNOS 9.2 Physical Interfaces High-levelArchitecture View Very comprehensive definition of ISSU!

37. Automated Operations Vision Advancing towards systems that proactively adapt to change and discover and mitigate problems • Error-resilient configuration, now with scripts to prevent procedural errors and to simplify common configurations • Confirmed adherence to business rules and policies • Auto-discovery and adaptation to network changes • Autonomic response to network conditions • Systematic implementation of diagnostics and repair to speed trouble response and resolution

38. JUNOScript Automation • Commit Script • Enforce Configuration Rules • Automatic Configuration Generation • Op Scripts • Build Custom Operational Commands • Build Powerful Troubleshooting Tools • Event Scripts • Automate Diagnostics • Automate Change Detection JUNOScript Automation

39. JUNOScript Automation Examples • Commit Script: • Operational Script: • Event Policy: [edit] admin@re0-ganimedes# commit [edit protocols ospf area 0.0.0.0 interface fe-0/2/3.0] 'interface fe-0/2/3.0;' warning: ATENCION: LDP no esta habilitado para este interface commit complete [edit] admin@re0-ganimedes> op vecinos - OSPF: Hay 2 vecinos OSPF activos - ISIS: No hay vecinos ISIS activos - BGP: Hay 3 vecinos BGP activos - LDP: Hay 2 vecinos LDP activos - RSVP: No hay vecinos RSVP activos admin@re0-ganimedes> [edit] admin@re1-leda# run file list detail /var/home/admin/: total 48 … -rw------- 1 admin field 209 Feb 23 12:22 re1-leda_Event-LINK-UP-Script.txt_20080223_122233 -rw------- 1 admin field 1391 Feb 23 12:22 re1-leda_Event-LINK-UP.txt_20080223_122231 [edit]

40. OPERATIONAL COSTS RELIABILITY SCALABILITY Challenges for the Next Generation Networks CONVERGENCE

41. JUNOS™ Software – A Single-source Operating System One OS Routers One Release 8.5 9.0 9.1 4Q07 1Q08 2Q08 One Architecture Switches Module X API

42. Energy-Efficient Networking

43. Why Care About Energy? • Electricity costs rose 88% in US since 2003 (US EIA data) Intl Energy Outlook ’07 predicts doubling energy generation by 2030, mostly via increasing the use of fossils Energy has become a non-trivial OPEX item 2. Worldwide legislation changes and public support for energy efficiency and climate control EMEA:reduce CO2 by 20% by 2020 UK:reduce CO2 by 20% by 2010 Japan:reduce CO2 to 6% under 1990 level by 2010 • Carriers and businesses are setting new targets reduced energy consumption reduced heat dissipation reduced space requirements (volume footprint)

44. What Does This Mean for Data Networking? • Telecom facilities require power and cooling • Direct contributors to CO2 emission • The cost of energy and space will rise • Data networking is still a growth industry • Global connectivity relies massively on routing and switching and this dependency increases • Significant increases in traffic are expected • This should NOT result in higher OPEX ► Vendors need to respond to the challenge

45. ECR InitiativeEnergy Consumption Ratingwww.ecrinitiative.org

46. Energy-Efficient Routing Platforms – Basics • Energy efficiency must be built into design • Once the platform is designed and built, it is too late to speak of energy improvements • Consumed energy dissipates as heat • Heat is the major limit for building faster routers Building energy-efficient routers goes well along building the fastest routers • Energy savings must be verifiable • Absolute energy consumption makes little sense • Energy should be normalized to capacity

47. Energy-efficient router – Definition Energy-efficient router is the one that needs the least amount of energy (in joules) to transfer network data (in bits) Energy Consumption of Router (ECR) ECR = Σ C(i) T C is the power rating of a router’s component i Є I, I is the set of configured components T is the router’s effective capacity (full-duplex) ECR is normalized to Watts/10 Gbps Also we can use Energy Efficiency (EER), EER = 1 / ECR EER is expressed in Gigabits/KW

48. What can be done to improve energy metrics? • Today • Custom-designed silicon dies: No wasted blocks or gates • Compare to commercial RISC CPU arrays (number of gates, clock) • Compare to off-the-shelf NPUs (effective speed per feature set) • Find fastest and simplest solution possible to do the job • Use DRAM instead of power-hungry TCAM • Shut elements when not in use (lookup cores, SerDes and memory) • Tomorrow • Better integration, faster silicon and lower voltage • Use of MCM (multi-chip modules) to unite several chips • Possible use of CLI to monitor the real-time energy consumption

49. Energy Efficiency: Positive Impact • Energy efficiency is synergetic with higher speed • Efficient designs need fewer gates, allowing dense packaging • Less energy means less heat dissipation, easier to scale up • Promotes newer silicon fabrication technologies • Promotes novel software and hardware structures • Accelerated technology introduction • Promotes intensive scaling over extensive scaling (larger systems) • Shortens effective silicon lifecycle in production networks • Newer and better technologies deployed more frequently

50. Reference Data: Silicon in Progress