Juniper Networks Intelligent Services Edge Launch Message Testing

1,067 views
1,004 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,067
On SlideShare
0
From Embeds
0
Number of Embeds
5
Actions
Shares
0
Downloads
39
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • This was not such a big issue even two years ago
  • When Juniper was founded, it was done by a realization that the Internet was growing exponentially and that the boundaries of Metcalfe’s law were being stretched. This presented a fundamental problem that needed to be addressed: How do we connect everything to everything at worldwide scale? Coincident was a fundamental understanding that TCP/IP would be an integral element to seeking the answer and that the Router would be an essential element of the solution. Solving this massive scale problem called for radical change in the way Routers were designed. Our approach was to move packets through hardware on a set of silicon chips without the intervention of software. Success required designing a new router while mastering the 5 core tenets of high-performance networking: 1. Routing protocols to enable networking at scale 2. Real-time embedded software systems to provide carrier-class reliability 3. Silicon design to separate packet processing from management overhead 4. System design to reduce rooms full of machines to a single half-rack 5. Power, cooling and space capabilities that deliver high availability 6. Security, integration across network infrastructure
  • Juniper Networks Intelligent Services Edge Launch Message Testing

    1. 1. Javier Antich jantich@juniper.net Iberia SP SE Manager Next Next Next Generation Networks Jornadas Técnicas Rediris Alcalá de Henares – Noviembre 2008
    2. 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. 3. Today´s Generation Challenges
    4. 4. The general climate…
    5. 5. Trend #1: The Grand Exodus <ul><li>RESULT AT DATA CENTER: </li></ul><ul><li>Demand for </li></ul><ul><li>Massive performance/scale </li></ul><ul><li>Carrier-class reliability </li></ul><ul><li>Green designs </li></ul><ul><li>Virtualization of everything </li></ul><ul><li>Data/Apps are getting consolidated into a few Data centers </li></ul><ul><li>People are getting scattered all over the world </li></ul><ul><li>RESULT AT BRANCH/CAMPUS: </li></ul><ul><li>Demand for: </li></ul><ul><li>“ All-in-one” integrated appliance </li></ul><ul><li>Remote deployment and management on a large scale </li></ul>Branches & Campuses Data Center Work Force Globalization Data Center Consolidation Network
    6. 6. Trend #2: The Blurring Work / Home <ul><li>People are taking work home </li></ul><ul><li>People are bringing home-expectations to work </li></ul>Branches & Campuses Data Center <ul><li>RESULT AT END POINTS: </li></ul><ul><li>Demand for: </li></ul><ul><li>A bewildering array of “unapproved” end-point devices </li></ul><ul><li>Un-tethered mobility </li></ul><ul><li>Data Leakage Prevention </li></ul><ul><li>RESULT AT BRANCHES & CAMPUSES: </li></ul><ul><li>Demand for: </li></ul><ul><li>Securing corporate laptops even inside the “trusted” perimeter </li></ul><ul><li>Dual-mode WLAN or Enterprise Femto-cells </li></ul>End Points Network
    7. 7. Trend #3: The Blurring of Company / Cloud <ul><li>Companies are putting their applications in the cloud (“SaaS”) </li></ul>Branches & Campuses <ul><li>RESULT AT CONTENT SP: </li></ul><ul><li>Demand for </li></ul><ul><li>DPI for XML/SOAP </li></ul><ul><li>Heightened QoS and acceleration </li></ul>Data Center Content Service Provider Network
    8. 8. Did you know this? <ul><li>Reality </li></ul><ul><ul><li>iTunes creates > 200 connections </li></ul></ul><ul><li>Assumptions </li></ul><ul><ul><li>Single application = single connection </li></ul></ul><ul><li>Underlying Functionality </li></ul><ul><ul><li>Multiple connections are established to retried map segments </li></ul></ul><ul><ul><li>Segments are then pieced together to form a whole map </li></ul></ul><ul><li>Infrastructure Requirements </li></ul><ul><ul><li>Must support multiple connections at once </li></ul></ul><ul><ul><li>Network delays result in grey map areas until graphics are loaded </li></ul></ul>Lack of NAT sessions WebPages # of Sessions No Operation 5 ~ 10 Yahoo Top page/Google Map 10~20 iTune 200~250 iGoogle 80~100 Youtube 50~80 Amazon ~80
    9. 9. IPv4: The End of the Road Comes into View <ul><li>Only 15% of IPv4 space remains available </li></ul><ul><li>Depletion projected late 2010 </li></ul>Source: www.potaroo.net/tools/ipv4/ Source: www.tndh.net/~tony/ietf/ipv4-pool-combined-view.pdf
    10. 10. <ul><li>TDM is past its prime </li></ul><ul><ul><li>Built primarily for voice, and adapted reasonably successfully for leased lines, fine-grained TDM (PDH/SDH) is increasingly irrelevant for Next Generation Networks </li></ul></ul><ul><ul><li>TDM is also very expensive on a cost/Gbps basis </li></ul></ul><ul><li>Packet transport is on the rise </li></ul><ul><ul><li>There is recognition that transport must focus on packets, not bits </li></ul></ul><ul><ul><li>There are multiple approaches, and a lot of confusion out there </li></ul></ul><ul><li>Interest in the Packets+Photons Phenomenon is growing </li></ul><ul><ul><li>There is also recognition that the worlds of packets and of optical transport must come together </li></ul></ul><ul><ul><li>Again, there are several approaches, and no clear way forward </li></ul></ul>Three Trends in Networking What Should Be Done?
    11. 11. Energy Savings <ul><li>“ 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 </li></ul>
    12. 12. Breakdown of Network Downtime Innovation Operations Maintenance Events System Errors Human Error
    13. 13. <ul><li>Joost </li></ul><ul><li>Zattoo </li></ul><ul><li>And many more… </li></ul>2004 2005 2006 2007 2008 2009 IP Data Traffic CAGR of 40% IP Video/Voice CAGR of 85% IP Data IP Video/Voice
    14. 14. Challenges for the Next Generation Networks SCALABILITY RELIABILITY OPERATIONAL COSTS CONVERGENCE
    15. 15. Challenges for the Next Generation Networks CONVERGENCE SCALABILITY RELIABILITY OPERATIONAL COSTS
    16. 16. Scalability on the Data Plane (Multichassis)
    17. 17. Scalability and stability in large scale networks Absolut: Multi-chassis 25 Tbps System Switch Fabric Chassis 25.6 Tbps Non-blocking #1 #4 #2 #3 #16 #13 #15 #14 #9 1600 Gbps 1600 Gbps T1600 T1600
    18. 18. Control Plane Scale and Virtualization
    19. 19. Scalability and Stability in Large Networks Control plane can become a bottleneck <ul><li>Popular notion that convergence has happened is false. It only happened at the forwarding plane – not the control plane </li></ul><ul><li>Each service has diverse requirements (TE, QOS, security, growth rates) </li></ul><ul><li>Requires multiple control planes </li></ul><ul><li>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 </li></ul><ul><li>As more new services are introduced this leads to escalating CapEx and OpEx </li></ul>Shared Control Plane SVC 1 SVC 2 SVC 3 SVC n Control Plane Forwarding Plane Router SVC 1 SVC 2 SVC 3 SVC n Processing Requirements Stability Scale
    20. 20. <ul><li>Control plane multiplicity changes that dynamic and fulfils the true promise of convergence </li></ul><ul><ul><li>Shared infrastructure </li></ul></ul><ul><ul><li>Services are decoupled from network </li></ul></ul><ul><ul><li>New services can be introduced without building a new subnet </li></ul></ul><ul><ul><li>Each services can be managed and controlled individually </li></ul></ul><ul><ul><li>Service introduction is swift and with reduced risk </li></ul></ul><ul><li>Each service now runs on its own “Virtual Service Network” </li></ul><ul><li>Lower CapEx, lower OpEx, Lower risk </li></ul>Scalability and Stability in Large Networks Control plane multiplicity Independent Control Plane SVC 1 SVC 2 SVC 3 SVC n CP1 Forwarding Plane Router SVC 1 SVC 2 SVC 3 SVC n CP2 CP3 CPn Juniper Control System Processing Requirements Stability Scale
    21. 21. Virtualization Continuum Delivered Next Steps … Logical Routing Protected System Domain Shared hardware platform; Separate routing instances <ul><li>Isolates routing protocols & interfaces </li></ul><ul><li>Enables hardware reuse – shared uplinks, efficient inter-LR forwarding </li></ul><ul><li>Deployed for service separation, additional security, managed service, substitute for physical route </li></ul>Shared hardware chassis; Dedicated routing resources <ul><li>Dedicates and isolates forwarding and control plane resources </li></ul><ul><li>Run independent versions of JUNOS </li></ul><ul><li>Share uplinks across virtual nodes </li></ul><ul><li>No customer facing slots </li></ul><ul><li>Flexibility and scalability of investment </li></ul>PE Logical Router Horizontal Consolidation Vertical Consolidation P Logical Router P Logical Router P Logical Router RE Pair RE Pair PSD1 PSD2 Safari
    22. 22. 1996 2003 2004 2007 First multi-chassis routing system Juniper pioneers the separation of control and forwarding plane M40 TX Matrix T1600 100 Gbps/slot Core IP/MPLS forwarding density Multiple control instances running on one router Juniper takes control plane architecture to the next level by physically decoupling the forwarding and control platforms Logical Routers 2008 Scalability and Stability in Large Networks JCS 1200: A Radically New Architecture LR_1 Service A LR_2 Service B LR_3 Tier 2/3 ISPs RI_1: ISP A RI_2: ISP B
    23. 23. Example: Virtualized Routing System for Collapsed POP Aggregation Router NETWORK CORE INTERNET PRIVATE PEERING Peering Router Internet Router Core Routers Aggregation Router IP/MPLS CUSTOMERS Edge Routers 20-30% CapEx Reduction NETWORK CORE INTERNET PRIVATE PEERING IP/MPLS CUSTOMERS PSD 1: Core PSD 2: Aggregation PSD 3: Private Peering PSD 4: Route Reflection Consolidated Router Safari
    24. 24. 40/100 GE IEEE 802.3ba
    25. 27. <ul><li>Juniper is an active participant in the 100 GE standardization effort. </li></ul><ul><li>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 </li></ul><ul><li>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 </li></ul><ul><li>Target delivery: 2010 </li></ul>100 GE
    26. 28. Challenges for the Next Generation Networks CONVERGENCE SCALABILITY RELIABILITY OPERATIONAL COSTS
    27. 29. Breakdown of Network Downtime Innovation Operations Maintenance Events System Errors Human Error
    28. 30. Nonstop Operation
    29. 31. Nonstop Operation <ul><li>Self-contained solution </li></ul><ul><ul><li>No requirement for peers to support </li></ul></ul><ul><li>No disruption of protocol adjacencies </li></ul><ul><ul><li>Switchover is transparent to neighbors </li></ul></ul><ul><li>Stateful replication of adjacency information on standby RE </li></ul><ul><ul><li>Routing updates, hello messages, adjacency state, etc. </li></ul></ul><ul><li>Dual active protocol sessions </li></ul><ul><ul><li>Standby RE is fully active and can immediately take over sessions </li></ul></ul><ul><li>Switchover is not dependent on stable topology </li></ul><ul><ul><li>Topology changes can occur during switchover </li></ul></ul>Continuous Systems Nonstop Routing Primary Routing Engine Active Standby Routing Engine
    30. 32. In-Service Software Upgrade (ISSU) <ul><li>What is our definition of ISSU? </li></ul>High-level Architecture View Daemon 2 Daemon n Packet Forwarding Daemon 3 Daemon 1 Kernel Physical Interfaces Routing Engine JUNOS 9.0
    31. 33. Is this ISSU? <ul><li>Upgrade of an individual module </li></ul><ul><li>NO: this is not true ISSU!! </li></ul>Daemon 3 Daemon n Packet Forwarding High-level Architecture View Daemon 1 Kernel Physical Interfaces Routing Engine Daemon 2 JUNOS 9.2 JUNOS 9.0
    32. 34. Is this ISSU? <ul><li>Upgrade of control plane software only </li></ul><ul><li>NO –this is not true ISSU! </li></ul>High-level Architecture View Daemon 2 Daemon n Packet Forwarding Daemon 3 Daemon 1 Kernel Physical Interfaces Routing Engine JUNOS 9.0 JUNOS 9.2 Daemon 2 Daemon n Daemon 3 Daemon 1 Kernel
    33. 35. Is this ISSU? <ul><li>Upgrade within same major release </li></ul><ul><li>Example: 9.0R1 to 9.0R2 </li></ul><ul><li>Yes, this is possible with ISSU, but this is not always enough! </li></ul>High-level Architecture View JUNOS 9.0R1 Daemon 2 Daemon n Packet Forwarding Daemon 3 Daemon 1 Kernel Physical Interfaces Routing Engine Daemon 2 Daemon n Packet Forwarding Daemon 3 Daemon 1 Kernel Physical Interfaces Routing Engine JUNOS 9.0R2
    34. 36. In-Service Software Upgrade (ISSU) <ul><li>Our definition of ISSU: </li></ul><ul><li>Upgrade the entire code on the router… </li></ul><ul><ul><li>Routing Engine </li></ul></ul><ul><ul><li>Packet Forwarding Engine </li></ul></ul><ul><ul><li>Physical Interfaces </li></ul></ul><ul><li>… with minimal disruption to traffic </li></ul><ul><li>Can even go from one major release to another! </li></ul>High-level Architecture View Daemon 2 Daemon n Packet Forwarding Daemon 3 Daemon 1 Kernel Physical Interfaces Routing Engine JUNOS 9.2 Very comprehensive definition of ISSU! Daemon 2 Daemon n Packet Forwarding Daemon 3 Daemon 1 Kernel Physical Interfaces Routing Engine JUNOS 9.0
    35. 37. Automated Operations Vision <ul><li>Advancing towards systems that proactively adapt to change and discover and mitigate problems </li></ul><ul><ul><li>Error-resilient configuration , now with scripts to prevent procedural errors and to simplify common configurations </li></ul></ul><ul><ul><li>Confirmed adherence to business rules and policies </li></ul></ul><ul><ul><li>Auto-discovery and adaptation to network changes </li></ul></ul><ul><ul><li>Autonomic response to network conditions </li></ul></ul><ul><ul><li>Systematic implementation of diagnostics and repair to speed trouble response and resolution </li></ul></ul>
    36. 38. JUNOScript Automation JUNOScript Automation <ul><li>Commit Script </li></ul><ul><ul><li>Enforce Configuration Rules </li></ul></ul><ul><ul><li>Automatic Configuration Generation </li></ul></ul><ul><li>Op Scripts </li></ul><ul><ul><li>Build Custom Operational Commands </li></ul></ul><ul><ul><li>Build Powerful Troubleshooting Tools </li></ul></ul><ul><li>Event Scripts </li></ul><ul><ul><li>Automate Diagnostics </li></ul></ul><ul><ul><li>Automate Change Detection </li></ul></ul>
    37. 39. JUNOScript Automation Examples <ul><li>Commit Script: </li></ul><ul><li>Operational Script: </li></ul><ul><li>Event Policy: </li></ul>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] [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]
    38. 40. Challenges for the Next Generation Networks CONVERGENCE SCALABILITY RELIABILITY OPERATIONAL COSTS
    39. 41. JUNOS™ Software – A Single-source Operating System One OS One Release One Architecture Switches Routers 9.1 Module X API 2Q08 1Q08 9.0 4Q07 8.5
    40. 42. Energy-Efficient Networking
    41. 43. <ul><li>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 </li></ul><ul><li>Energy has become a non-trivial OPEX item </li></ul><ul><li>2. Worldwide legislation changes and public support for energy efficiency and climate control </li></ul><ul><li>EMEA: reduce CO 2 by 20% by 2020 </li></ul><ul><li>UK: reduce CO 2 by 20% by 2010 </li></ul><ul><li>Japan: reduce CO 2 to 6% under 1990 level by 2010 </li></ul><ul><li>Carriers and businesses are setting new targets </li></ul><ul><li>reduced energy consumption </li></ul><ul><li>reduced heat dissipation </li></ul><ul><li>reduced space requirements (volume footprint) </li></ul>Why Care About Energy?
    42. 44. What Does This Mean for Data Networking? <ul><li>Telecom facilities require power and cooling </li></ul><ul><ul><li>Direct contributors to CO 2 emission </li></ul></ul><ul><ul><li>The cost of energy and space will rise </li></ul></ul><ul><li>Data networking is still a growth industry </li></ul><ul><ul><li>Global connectivity relies massively on routing and switching and this dependency increases </li></ul></ul><ul><ul><li>Significant increases in traffic are expected </li></ul></ul><ul><ul><li>This should NOT result in higher OPEX </li></ul></ul>► Vendors need to respond to the challenge
    43. 45. ECR Initiative Energy Consumption Rating www.ecrinitiative.org
    44. 46. Energy-Efficient Routing Platforms – Basics <ul><li>Energy efficiency must be built into design </li></ul><ul><ul><li>Once the platform is designed and built, it is too late to speak of energy improvements </li></ul></ul><ul><li>Consumed energy dissipates as heat </li></ul><ul><ul><li>Heat is the major limit for building faster routers Building energy-efficient routers goes well along building the fastest routers </li></ul></ul><ul><li>Energy savings must be verifiable </li></ul><ul><ul><li>Absolute energy consumption makes little sense </li></ul></ul><ul><ul><li>Energy should be normalized to capacity </li></ul></ul>
    45. 47. Energy-efficient router – Definition <ul><li>Energy-efficient router is the one that needs the least amount of energy (in joules) to transfer network data (in bits) </li></ul><ul><li> Energy Consumption of Router (ECR) </li></ul><ul><li>ECR = Σ C(i) </li></ul><ul><li> T </li></ul><ul><li>C is the power rating of a router’s component </li></ul><ul><li>i Є I , I is the set of configured components </li></ul><ul><li>T is the router’s effective capacity (full-duplex) </li></ul><ul><li>ECR is normalized to Watts/10 Gbps </li></ul><ul><li>Also we can use Energy Efficiency ( EER ), EER = 1 / ECR </li></ul><ul><li>EER is expressed in Gigabits/KW </li></ul>
    46. 48. What can be done to improve energy metrics? <ul><li>Today </li></ul><ul><ul><li>Custom-designed silicon dies: No wasted blocks or gates </li></ul></ul><ul><ul><ul><li>Compare to commercial RISC CPU arrays (number of gates, clock) </li></ul></ul></ul><ul><ul><ul><li>Compare to off-the-shelf NPUs (effective speed per feature set) </li></ul></ul></ul><ul><ul><li>Find fastest and simplest solution possible to do the job </li></ul></ul><ul><ul><li>Use DRAM instead of power-hungry TCAM </li></ul></ul><ul><ul><li>Shut elements when not in use (lookup cores, SerDes and memory) </li></ul></ul><ul><li>Tomorrow </li></ul><ul><ul><li>Better integration, faster silicon and lower voltage </li></ul></ul><ul><ul><li>Use of MCM (multi-chip modules) to unite several chips </li></ul></ul><ul><ul><li>Possible use of CLI to monitor the real-time energy consumption </li></ul></ul>
    47. 49. Energy Efficiency: Positive Impact <ul><li>Energy efficiency is synergetic with higher speed </li></ul><ul><ul><li>Efficient designs need fewer gates, allowing dense packaging </li></ul></ul><ul><ul><li>Less energy means less heat dissipation, easier to scale up </li></ul></ul><ul><ul><li>Promotes newer silicon fabrication technologies </li></ul></ul><ul><ul><li>Promotes novel software and hardware structures </li></ul></ul><ul><li>Accelerated technology introduction </li></ul><ul><ul><li>Promotes intensive scaling over extensive scaling (larger systems) </li></ul></ul><ul><ul><li>Shortens effective silicon lifecycle in production networks </li></ul></ul><ul><ul><li>Newer and better technologies deployed more frequently </li></ul></ul>
    48. 50. Reference Data: Silicon in Progress   Juniper M40 M160 T640 T1600 Next-gen Slot Capacity, Gpbs 3.0 10 40 100 System Capacity 40Gbps 160G 640G 1600G Technology 180nm 180nm 130nm 90nm 65nm and < Consumption, KW 1.5 3.15 6.34 8.21 EER (Gbps/KW) 13 Gbps/KW 25 Gbps/KW 50.5 Gbps/KW 97.5 Gbps/KW > 100 Gbps/KW FRS 1998 2000 2002 2007 2010+
    49. 51. Juniper Experience: Technology Into Energy <ul><li>Small power overhead for packet operations </li></ul><ul><li>Fully custom in-house packet processors </li></ul><ul><li>Unique ASIC expertise, very high gate utilization </li></ul><ul><li>Highest Integration Levels – fabrication and packaging </li></ul><ul><li>Full 10 Gbps datapath on a single IP3 chip (includes lookup engine, memory controller and fabric interface) </li></ul><ul><li>Up to four forwarding engines on one blade (MX960) </li></ul><ul><li>Industry’s only 100G/slot core router in commercial use (T1600) </li></ul><ul><li>Patented and Energy-Optimized Design </li></ul><ul><li>Stateless packet services without TCAM </li></ul><ul><li>Best-of-breed power converters </li></ul>
    50. 52. Synergy Between Vendors and Customers <ul><li>Data networking is very mature now </li></ul><ul><li>Many protocols and technologies were developed </li></ul><ul><ul><li>some are obsolete </li></ul></ul><ul><li>But every time a network buildout is considered, it comes with a hefty list of features on RFP </li></ul><ul><li>Someone has to pay for all those features </li></ul><ul><ul><li>Carved in silicon, unused gates and wasted power </li></ul></ul><ul><li>Time to stop and think – </li></ul><ul><ul><li>Which features are really needed and where? </li></ul></ul><ul><li>Precise match of form and function is the best </li></ul>Efficient network design is extremely important
    51. 53. Conclusions <ul><li>Environmental impact and energy efficiency are verifiable </li></ul><ul><ul><li>Choose right platforms to satisfy energy requirements </li></ul></ul><ul><ul><li>Use normalized ECR/EER metrics for comparison </li></ul></ul><ul><ul><li>Design networks to minimize the energy and rack space usage </li></ul></ul><ul><li>We need to define and pursue aggressive energy goals </li></ul><ul><ul><li>Reduced energy consumption </li></ul></ul><ul><ul><li>Reduced heat dissipation </li></ul></ul><ul><ul><li>Reduced space requirements (compact footprint) </li></ul></ul><ul><ul><li>This should be a joint effort between vendors, carriers and enterprises </li></ul></ul><ul><li>Energy efficiency stimulates the industry </li></ul><ul><ul><li>New designs will increase EER and decrease environmental footprint </li></ul></ul><ul><ul><li>Fast networking and energy efficiency are not conflicting goals </li></ul></ul>
    52. 54. Challenges for the Next Generation Networks CONVERGENCE SCALABILITY RELIABILITY OPERATIONAL COSTS
    53. 55. Convergence from many different perspectives <ul><li>Services Convergence. </li></ul><ul><li>Technology convergence. </li></ul><ul><ul><li>Optical and IP </li></ul></ul><ul><li>Topology / planes convergence. </li></ul><ul><ul><li>POP consolidation. </li></ul></ul><ul><ul><li>Reduction of network layers. </li></ul></ul><ul><li>Networks convergence </li></ul><ul><ul><li>Fixed and mobile. </li></ul></ul>
    54. 56. IP & Optical Convergence
    55. 57. Transport Intelligence <ul><li>Easy operations (OAM&P) </li></ul><ul><ul><li>G.709 overheads mimic SONET/SDH functions </li></ul></ul><ul><ul><li>GMPLS allows optical layer visibility into hard to detect failures </li></ul></ul><ul><ul><li>Integrated optics  low-cost optical monitoring and provisioning </li></ul></ul><ul><li>Fast protection </li></ul><ul><ul><li>Integrated DWDM interfaces of a router enable fast triggers </li></ul></ul><ul><ul><li>Router-based fast reroute (FRR) may be more economical and as fast and reliable as SONET/SDH ring-based protection </li></ul></ul><ul><li>Sub-wavelength grooming </li></ul><ul><ul><li>Not needed—router trunks can fill 10G/40G wavelengths </li></ul></ul><ul><ul><li>Manage bandwidth at the wavelength level using ROADMs </li></ul></ul>Substituting key SONET/SDH functions with G.709 and GMPLS Replacing SONET/SDH functions by MPLS + G.709 + DWDM allows for a simpler, more scalable architecture
    56. 58. Transport Intelligence Optical integration Fixed and Tunable Optics GMPLS interoperability 40 Gbps IPoDWDM 10GE Tunable Optics WAN PHY <ul><li>Elegant, multilayer failover scenarios </li></ul><ul><li>End-to-end performance monitoring </li></ul><ul><li>Coordinates end-to-end restoration across optic and routing layers </li></ul><ul><li>Reduces bandwidth and interface requirements for redundancy </li></ul>GMPLS Ethernet OAM 1:1 or 1:n protection OSS G.709 GMPLS OTN Interfaces Single Transport-Service Control Plane Container Interfaces <ul><li>Simplifies core topologies </li></ul><ul><li>Offers flexibility in provisioning and response to topology changes </li></ul><ul><li>Enables on-demand services </li></ul><ul><li>Connecting Metro E over SONET </li></ul>Available today Next steps
    57. 59. Transport intelligence <ul><li>Lower CapEx </li></ul><ul><li>66% optics reduction </li></ul><ul><li>Lower OpEx </li></ul><ul><li>Fewer shelves (space, cooling, power, management), </li></ul><ul><li>Fewer interconnects </li></ul><ul><li>Enhanced resiliency </li></ul><ul><li>Fewer devices </li></ul><ul><li>Fewer active components </li></ul><ul><li>Fewer interconnects </li></ul>CapEx and OpEx performance Router Transponder Mux/ROADM Before After Benefits Router Mux/ROADM
    58. 60. Transport Intelligence CLI NETCONF JUNOScript E.g., SNMP Transmission Management Router Management Control Plane Data Plane Mgmt. Plane WDM GMPLS OTN Juniper GMPLS Control End to end service view provided by transmission MGMT or other common OSS Integrated Control Plane based provisioning OSS Management Options <ul><li>Single intelligent IP control plane for delivering service flexibility and lower OpEx </li></ul><ul><li>Segmented or integrated management model for faster provisioning, reduced OpEx </li></ul><ul><li>Integrated transponders lower CapEx/OpEx, increase reliability </li></ul><ul><li>ROADMs eliminate OEO and minimize truck rolls for reliability, service flexibility, and lower OpEx </li></ul>
    59. 61. Topology / planes convergence
    60. 62. Example: Virtualized Routing System for Collapsed POP Aggregation Router NETWORK CORE INTERNET PRIVATE PEERING Peering Router Internet Router Core Routers Aggregation Router IP/MPLS CUSTOMERS Edge Routers 20-30% CapEx Reduction NETWORK CORE INTERNET PRIVATE PEERING IP/MPLS CUSTOMERS PSD 1: Core PSD 2: Aggregation PSD 3: Private Peering PSD 4: Route Reflection Consolidated Router Safari
    61. 63. Services convergence
    62. 64. New services, new ideas <ul><li>The network must be open to the integration of new services, new capabilities. </li></ul><ul><li>Equipment vendors should no longer be the only source for the innovation. </li></ul><ul><li>Example: </li></ul><ul><ul><li>Juniper PSPD. </li></ul></ul>
    63. 65. <ul><li>For Customers </li></ul><ul><ul><li>An ecosystem of choice </li></ul></ul><ul><ul><li>Build competitive differentiators internally </li></ul></ul><ul><ul><li>Bring new technologies to customers </li></ul></ul><ul><li>For Partners </li></ul><ul><ul><li>Reducing barriers to partnership </li></ul></ul><ul><ul><li>Integrate new technologies more quickly </li></ul></ul>New Supply Models Existing Supply Models Customer Idea Juniper Developer User Independent Vendor Customer Customer Juniper Customer Customer Juniper Customer Customer Independent Vendor Customer Customer Independent Vendor Customer ? ? Juniper Vision: An Ecosystem of Choice
    64. 66. Summary
    65. 67. DNA of the Next Generation Networks 100GbE NSR, ISSU IPv6 Multichasis systems Flexible control plane virtualization Operational Automation Energy Efficiency IP & Optical convergence - GMPLS Open Networks for innovation.
    66. 68. Javier Antich Romaguera Systems Engineer Manager Iberia SP [email_address]

    ×