SSMMX01D

ed u cat io n serv ices co ursew a re

MX Series Technical MX Series Technical MX Series Technical MX Series Technical

OverviewOverviewOverviewOverview

Student GuideStudent GuideStudent GuideStudent Guide

MX Series Technical Overview

Course SSMMX01D © Juniper Networks, Inc. 2

NOTE: Please note this Student Guide has been developed from an audio narration. Therefore it will have

conversational English. The purpose of this transcript is to help you follow the online presentation and may require

reference to it.

Slide 1

© 2013 Juniper Networks, Inc. All rights reserved. | www.juniper.net | Proprietary and Confidential

MX Series

Technical Overview

Welcome to Juniper Networks “MX Series Technical Overview” eLearning module.



Slide 2

© 2013 Juniper Networks, Inc. All rights reserved. www.juniper.net | 2CONFIDENTIAL SSMMX01D

Navigation

Throughout this module, you will find slides with valuable detailed information. You can stop any slide with the Pause button to study the details. You can also read the notes by using the Notes tab. You can click the Feedback link at anytime to submit suggestions or corrections directly to the Juniper Networks eLearning team.



Slide 3


Course Objectives

After successfully completing this course, you will be

able to:

•Discuss Juniper Networks approach to the high-end

enterprise routing market

•Discuss how Juniper Networks is changing the economics of

networking

•Describe Juniper Networks various advanced routing

features

•Identify components and cite capabilities of the MX Series

platforms

•Identify key enterprise applications for Juniper routers

After successfully completing this course, you will be able to:

•Discuss Juniper Networks approach to the high-end enterprise routing market;

•Discuss how Juniper Networks is changing the economics of networking;

•Describe Juniper Networks various advanced routing features;

•Identify components and cite capabilities of the MX Series platforms; and

•Identify key enterprise applications for Juniper routers.



Slide 4


Agenda: MX Series Technical Overview

� About Juniper Networks

� Challenges in the Enterprise

� Advanced Routing Hardware and Software

� Enterprise Product Portfolio

� Deployment Scenarios

This course consists of five sections. The five main sections are as follows:

•About Juniper;

•Challenges in the Enterprise;

•Advanced Routing Hardware and Software;

•Enterprise Product Portfolio; and

•Deployment Scenarios.



Slide 5


About Juniper Networks

MX Series

Technical Overview

Let’s start with a look at Juniper Networks presence in the high end enterprise routing market.



Slide 6


Section Objectives

After successfully completing this section, you will be

able to:

•Discuss Juniper’s approach to the high-end enterprise

routing market

•Describe Juniper’s mission and strategy

After successfully completing this section, you will be able to:

• Discuss Juniper’s approach to the high-end enterprise routing market; and

• Describe Juniper’s mission and strategy.



Slide 7


Juniper Networks: Strategic Differentiation

Juniper Networks: Strategic Differentiation We continue to offer a unique approach: No-compromise performance with best-in-class technologies, a comprehensive end-to-end portfolio, integrated solutions, superior partnerships, and award-winning services to enable enterprises to deliver fast, reliable, secure services that accelerate their business.



Slide 8


Clear Mission and Focused Strategy

Connect Everything; Empower Everyone

Through High-performance Networking And Industry Innovation

Clear Mission and Focused Strategy This slide refers to Juniper’s mission and strategy to deliver on something we set out to do several years ago. That is: “Connect everything, and empower everyone.” What that means is that you need to fundamentally design a system with certain things in mind. That means that we need to have very powerful silicon that can process millions of packets and also provide our customers with flexibility without compromising on performance. We need to build systems that are either distributed or centralized, depending on the applications that provide customers with that level of carrier class reliability, scalability and flexibility. Then we need to have the software that gives customers the full, rich set of features so that, as we start to build the network, and as we start to provide connectivity to multiple devices, we have a single pane of glass to look at from a provisioning standpoint. We have a single operating system that provides control plane functionality that is consistent across the product line.



Slide 9


MX Series: Continuing the Momentum

• Over $3B in shipments

• More than 5000 unique customers

• Over 40,000 chassis

• Densest Carrier Class Router in the industry

Trio Chipset

2010 Broadband

InfoVision Award

MX80 3D

Best of Show

Award 2010

MX80 3D

Best New

Product in

Telecom

MX3D 100-

Gigabit Ethernet

2011

MX Series: Continuing the Momentum The momentum of MX Series deployments continues. More than 5000 unique customers are using the MX Series in various critical locations in their networks. Shown on the slide are some of the awards the MX Series continues to receive.



Slide 10


Section Summary

In this section, we:

•Discussed Juniper’s approach to the high-end enterprise

routing market

•Described Juniper’s mission and strategy


• Discussed Juniper’s approach to the high-end enterprise routing market; and

• Described Juniper’s mission and strategy.



Slide 11


Learning Activity 1: Question 1

� Which of the following are the three elements of

Juniper’s strategy and mission to connect everything

and empower everyone? (Select three.)

A) Systems

B) Silicon

C) Security

D) Software




Slide 12


Challenges in the Enterprise

MX Series

Technical Overview

Now we’ll take a look at the challenges in the enterprise.



Slide 13


Section Objectives


able to:

•Discuss the explosive growth in traffic demand

•Review the evolution of enterprise networks

•Discuss the demand for improved user experience

•Contrast experience versus economics

•Discuss how Juniper is changing the economics of

networking


• Discuss the explosive growth in traffic demand;

• Review the evolution of enterprise networks;

• Discuss the demand for improved user experience;

• Contrast experience versus economics; and

• Discuss how Juniper is changing the economics of networking.



Slide 14


Explosive Growth in Traffic Demand

Explosive Growth in Traffic Demand The trend that is facilitating the refresh of the WAN is the overall traffic growth we are seeing across multiple enterprises. That trend is irrespective of whether you look at the total number of websites or the amount of video traffic or non-video traffic. You can see that there is exponential growth that kicked off right around 2008 and is trending up and to the right, going into 2020. So, overall traffic growth is phenomenal. Very closely associated with that is the total number of connections that we see across the Internet. What used to be just two devices talking to each other now has proliferated into multiple millions of devices that need to connect across the wide area.



Slide 15


Evolution of Enterprise NetworksCritical to Business and Competitive Advantage

Consolidation

Consolidate IT resources out of branch offices

and to place them in centralized data centers

Increased Complexity

Support any communication

application

ReliabilityBe available 100% of the time

Security and ComplianceSecure everyone from threats by anyone

Evolution of Enterprise Networks Critical to Business and Competitive Advantage Enterprise networks have become critical to business and provide the companies a competitive advantage in this highly competitive world market. Consolidation: During the past 10 years, as enterprises have grown, the data centers (DCs) have expanded into several locations to accommodate the increased demand for space. Customers ended up having 100s of data centers across the world, which became very difficult and expensive to manage. Now, enterprises are looking to consolidate and centralize. The trend is to consolidate IT resources—such as servers, applications, and storage—out of branch offices and to place them in centralized data centers Complexity: Networks have become very complex. They connect billions of users and devices, thousands of super data centers, and support many communication applications. You’ve got convergence of voice and video and data into single-application architectures, service-oriented architectures, and then finally, software is going to be delivered as a service. Reliability: Users and businesses are now global. The requirement is not only to be reliable, but 100% available because IT departments need to provide around-the-clock service. For example, people who work in the Americas need access to servers in APAC, and vice versa. Security and Compliance: Everybody has heard of denial of service (DoS) attacks and knows it is extremely important that your entire infrastructure is as secure as possible. Now, for the network that is critical to business, you need a high-performance network that is fast, reliable, and secure. And this is the opportunity for Juniper. This is where we are uniquely positioned to come in and deliver high-performance networks for high-performances businesses. Two other considerations are cloud computing and implementation of green networks.



Slide 16


Great Demand for Great Experiences

Great Demand for Great Experiences Optimized content delivery has become a critical requirement due to the increased levels of media-rich traffic on networks and across different spectrums of business and life—customers are demanding improved user experience. Companies are under pressure to improve user experience in order to stay competitive. For example, competitiveness in the global financial markets is measured in microseconds, and financial services, news services, and stock exchanges such as the NYSE have high-touch content that requires low latency, a high level of resiliency, and high security. In the case of the NYSE, they need to be able to broadcast stock information to a large number of end points/financial institutions and ensure that their customers (i.e., the financial institutions) receive that stock information simultaneously. They must also ensure that the financial institutions can send traffic back to the NYSE without any delay in the transmission, as that is the traffic that closes the deals.



Slide 17


Experience Versus Economics

The Eternal Challenge

Experience Versus Economics While there is a demand to improve experience, there are pressures to reduce costs and total cost of ownership (TCO).



Slide 18


Business Transformation

• Service richness

• Boost application

• performance

• Increase employee

• productivity

• Eliminate OS proliferation

• Converge separate application

• networks

• Integrate services

• Reduce power/space

• Competitive Advantage

• Customer attention, retention

• and satisfaction

• Faster time-to-market

Changing Economics of Networking

Business Transformation Juniper is changing the economics of networking by reducing TCO, increasing return on investment (ROI), and accelerating profitability. We will show you this in detail.



Slide 19


Section Summary


•Discussed the explosive growth in traffic demand

•Reviewed the evolution of enterprise networks

•Discussed the demand for improved user experience

•Contrasted experience versus economics

•Discussed how Juniper is changing the economics of

networking


• Discussed the explosive growth in traffic demand;

• Reviewed the evolution of enterprise networks;

• Discussed the demand for improved user experience;

• Contrasted experience versus economics; and

• Discussed how Juniper is changing the economics of networking.



Slide 20


� For an enterprise to be competitive today, its network

must be which three of the following? (Select three.)


A) Fast

B) Reliable

C) Complex

D) Secure




Slide 21


� Juniper is changing the economics of networking by

reducing what, increasing what, and accelerating

what?


A) ROI; TCO; NYSE

B) ROI; TCO; profitability

C) TCO; ROI; profitability

D) OpEx; CapEx; APAC




Slide 22


Advanced Routing

Hardware and Software

MX Series

Technical Overview

Next up, we’ll take a look at Juniper’s advanced routing hardware and software.



Slide 23


Section Objectives


able to:

•Describe the elements that provide the Juniper advantage in

high end routing

•Explain how the Junos OS reduces complexity

•Discuss the Junos Trio Chipset

•Cite examples of savings with Juniper

•Discuss the unmatched capacity of the MX 3D

•Discuss the need for advanced routing

•Describe Juniper’s various advanced routing features


• Describe the elements that provide the Juniper advantage in high end routing;

• Explain how the Junos operating system (Junos OS) reduces complexity;

• Discuss the Junos Trio Chipset;

• Cite examples of savings with Juniper;

• Discuss the unmatched capacity of the MX 3D;

• Discuss the need for advanced routing; and

• Describe Juniper’s various advanced routing features.



Slide 24


Juniper Advantage

Juniper Advantage The elements that provide the Juniper advantage in high-end routing include the following:

• An advanced silicon and hardware portfolio with the Junos OS, the single operating system across all hardware.

• Advanced routing features implemented on the routing platform needed to provide a competitive edge and address the challenges facing enterprises.

• And, finally, the two-tiered collapsed architecture that:

• Simplifies the architecture;

• Requires fewer devices;

• Reduces latency;

• Reduces space, power, and cooling requirements; and

• Simplifies management and support. We bring what we learned in the high-end routing hardware to the enterprise—consistency across all hardware. Solving massive scale problems 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. Juniper offers a high-performance network infrastructure that supports converged networks where data, voice, and video traffic are running in parallel, and one that keeps pace with the escalating demands of high-performance businesses. We offer a complete portfolio of products supporting the DC, campus, branch, and WAN edge. The Junos OS is one network operating system with a single release train that enables features and functionality to be consistently implemented across the network without compromise or complication. This drives significant operational efficiency and enables network administrators to spend more time innovating. The Junos OS is fundamentally different in not only its architectural design, but also in its development. We summarize the real differences of the Junos OS in Three key areas that we refer to as our 1-1-1 differentiation. One operating system with consistent core functionality that enables platforms from Mbps to Tbps speeds; one single software release extended through a highly disciplined and firmly scheduled development process; and one common modular software architecture that protects the base software and its applications. Cisco builds to every single platform different capabilities over time. It takes a long time for features to percolate to all platforms. We build features once and release to all platforms all at once. The result: The Junos OS has experienced



tremendous market success, capturing a significant portion of its available market in just 10 years and serving the most demanding customers in the world, including the top 40+ service providers and many high-performance enterprise and public sector accounts. Juniper Networks offers industry leading high performance routers with the most complete, advanced routing features in the industry, without compromising performance. These features include traffic segmentation and virtualization with MPLS, ultra low-latency multicast; and comprehensive QoS implementation. Juniper enables you to build a highly virtualized and secure data center network that:

• Eliminates the aggregation layer;




• Simplifies management and support with a single network OS.



Slide 25


Junos OS� Simplify Operations and Reduce Network Complexity

Junos OS The Junos OS ties together Juniper’s security, routing, and switching products with one operating system that can scale from the branch office to the core of the network. New releases are extensively tested and delivered in a steady cadence which provides a stable release of new features. The modular architecture provides predictable performance from the smallest to the largest platform in the product line. IT managers can use a consistent set of tools to manage, monitor, and update their network.



Slide 26


Junos Trio Chipset: Uncompromised 3D Scaling

Dense, Line rate 10GEs, 100GE Bandwidth ScaleBandwidth ScaleBandwidth ScaleBandwidth Scale

Quality of Experience in ServicesServices ScaleServices ScaleServices ScaleServices Scale

Large # of Users and AppsUser/Application ScaleUser/Application ScaleUser/Application ScaleUser/Application Scale

Junos Trio Chipset: Uncompromised 3D Scaling At the core of the success of Juniper’s routing and switching platforms is its industry leading ASIC technology. In 2009, we introduced the Junos TRIO chipset which provides uncompromised 3D scaling. The three dimensions are bandwidth, services and subscribers.

• Bandwidth: Support the ever increasing bandwidth demand.

• Services: Deliver services with the quality and performance that meets the customer’s expectations.

• Subscribers: Scale to support the growing subscriber base for the service providers.



Slide 27


Another Example of Savings with Juniper

Another Example of Savings with Juniper This slide offers is another example of savings with Juniper. Juniper is the provider of the world’s most powerful and efficient hardware. Whether you are measuring line card capacity, packet capability, addressing, or power efficiency—Juniper is the leader. With everyone talking about energy consumption, we have a powerful message. The Junos Trio chipset is designed to offer a very efficient power and thermal system. With 16-port 10-Gigabit Ethernet line cards, power draw is as low as 37 watts per 10-Gigabit Ethernet port, creating up to 1.7 times more power efficiency per 10-Gigabit Ethernet port compared to similar competitive line cards.



Slide 28


23.25W per line23.25W per line23.25W per line23.25W per line----rate port rate port rate port rate port

MX960 Versus ASR9000 (36x10GbE Card) Power Comparison

FRUFRUFRUFRU Power (W)Power (W)Power (W)Power (W)

24x10GbE w/o traffic 412 W

24x10GbE MPC4 only with

traffic 485.31W

Total power perTotal power perTotal power perTotal power per 10GbE port10GbE port10GbE port10GbE port

(including efficiency)(including efficiency)(including efficiency)(including efficiency)

558.1/24= 558.1/24= 558.1/24= 558.1/24=

23.2523.2523.2523.25 WWWW

FRUFRUFRUFRU Power (W)Power (W)Power (W)Power (W)

36x10GbE without traffic 686W

36x10GbE only with traffic 894.4W

Total power per 10GbE portTotal power per 10GbE portTotal power per 10GbE portTotal power per 10GbE port 24.84W24.84W24.84W24.84W

The MX960 utilizes

its power much more

efficiently, offering

Intelligent Edge

Capabilities and

higher port density ,

with a perperperper----port port port port

power consumption power consumption power consumption power consumption

of 23.25Wof 23.25Wof 23.25Wof 23.25W

The ASR9000 is hindered by its

high per-card power

consumption and low slot

capacity.

With their 36-port 10GbE line

card , ASR9000 consumes

nearly 25W per 1025W per 1025W per 1025W per 10----Gigabit port Gigabit port Gigabit port Gigabit port

24.84W per line24.84W per line24.84W per line24.84W per line----rate portrate portrate portrate port

GbE = Gigabit Ethernet

W = watts

MX960 Versus ASR9000 (36x10GbE Card) Power Comparison This slide shows a comparison between the Juniper MX960 and Cisco’s ASR9000 with its 36-port 10-Gigabit Ethernet line card. The MX960 utilizes its power much more efficiently, offering Intelligent Edge Capabilities and higher port density, with a per-port power consumption of 23.25 watts. The ASR9000 is hindered by its high per-card power consumption and low slot capacity.



Slide 29


Need for Advanced RoutingAdvanced Platform FeaturesAdvanced Platform FeaturesAdvanced Platform FeaturesAdvanced Platform FeaturesBusiness DriversBusiness DriversBusiness DriversBusiness Drivers

Need for Advanced Routing Routing has become a core function of any network, but routers have grown beyond the traditional role of connecting network segments. In order to provide a competitive edge and address the challenges facing enterprises, high-end routers must evolve from a device dedicated to connecting disparate networks, to an intelligent and integrated services device capable of multiple functions beyond routing. This diagram illustrates the fact that business imperatives drive technical strategies and how they can be achieved by advanced routing platforms. These are Juniper’s advanced routing capabilities addressing these business drivers.



Slide 30


Advanced Routing Features

Single Operating SystemSingle Operating SystemSingle Operating SystemSingle Operating System

Virtualization enabled by MPLSVirtualization enabled by MPLSVirtualization enabled by MPLSVirtualization enabled by MPLS

Low Latency Multicast Low Latency Multicast Low Latency Multicast Low Latency Multicast

Carrier Class Reliability for EnterpriseCarrier Class Reliability for EnterpriseCarrier Class Reliability for EnterpriseCarrier Class Reliability for Enterprise

Rich QoS FeaturesRich QoS FeaturesRich QoS FeaturesRich QoS Features

Collapsed Data Center DesignCollapsed Data Center DesignCollapsed Data Center DesignCollapsed Data Center Design

1111

2222

3333

4444

5555

6666

Advanced Routing Features We are now going to focus on the following six advanced routing features:

• A Single Operating System—the Junos OS;

• Collapsed Data Center Design;

• Network Virtualization enabled by MPLS;

• Carrier Class Reliability;

• Rich QoS Features; and

• Low Latency Multicast.



Slide 31


• One operating system across all platforms

• Extensively tested releases providing stable

delivery of new features

• Accelerate advance services and

application deployment

• Simplified network management

• Paralyzing complexity

• Consumes operational time

• Increases risk of downtime

• Unpredictable performance

• A hindrance to business innovation

and speed

Legacy OS Next Gen OSNext Gen OSNext Gen OSNext Gen OS

SimpleSimpleSimpleSimple

PredictablePredictablePredictablePredictable

ReliableReliableReliableReliable

1111Junos OS Reduces Network ComplexitySingle Operating System

Junos OS Reduces Network Complexity As the physical network has grown, legacy operating systems have also multiplied, resulting in IT organizations working under very difficult conditions. Some characteristic problems posed by legacy networks are:

• Paralyzing complexity: It becomes impossible to manage code branches and feature support across large networks;

• They consume operational time: The time and effort required to test different codes across multiple platforms for new feature support often requires a dedicated staff;

• There is an increased risk of downtime: Inconsistency across the network increases risk of downtime when new features are enabled, or new configurations applied;

• Unpredictable performance: Performance for new applications in individual environments is less predictable with all the possible variations of operating systems; and

• Legacy operating systems are a hindrance to business innovation and speed. Obviously, all these issues make it difficult to adapt to new opportunities as the business grows and changes. The Junos OS ties together Juniper’s security, routing, and switching products with one operating system that can scale from the branch office to the core of the network. New releases are extensively tested and delivered in a steady cadence which provides a stable release of new features. The modular architecture provides predictable performance from the smallest to the largest platform in the product line. With the Junos OS IT managers can use a consistent set of tools to manage, monitor, and update their network.



Slide 32


HighHighHighHighLatencyLatencyLatencyLatency

Overly Overly Overly Overly ComplexComplexComplexComplex

Legacy DC Architecture Layers of Switches

2222

Legacy DC Architecture Layers of Switches Typical DC architecture has access layer switches, an aggregation layer with FW, SSL VPN, and load balancers, and a core layer at the top. This DC structure is scalable because you can build multiples of these. It is reliable because you have redundancy at every layer. It is secure because you have the firewalls. But it is extremely complex. And a different operating system in each layer makes it operationally expensive and cumbersome. The issues are…

•Latency: If you want to talk from server A to server B, you are adding latency at every layer, which makes the latency very high and unpredictable. Therefore, we want to simplify and reduce the number of layers and the number of devices without compromising availability, reliability, and security.

• Oversubscription at every layer: You can have packets drop at any layer at the entry point and even on the backplane. Therefore, performance is not predictable.



Slide 33


Juniper’s Value: Simplification—Collapsing Core and Aggregation Layers

L2/L3Switch

L2/L3 Switch

L2/L3Switch

L2/L3 Switch

EX4200

SRX5800

MX Series

Enterprise Services Edge:

Application Segmentation—L3 VPN

VLAN extensions—VPLS

TDM replacements over IP WAN

Regulatory compliance

MX Series

Low LatencyLow LatencyLow LatencyLow Latency

2a2a2a2a

• MX in the core for simplified, collapsed architecture

• Scale of platforms reduces # of elements needed to support a growing network

• Low latency and scalable multicast

• MPLS, VPLS services: Network-wide mobility and segmentation

Juniper’s Value: Simplification—Collapsing Core and Aggregation Layers Juniper’s Value Proposition Juniper enables you to build a highly virtualized and secure data center network that:

• Eliminates the aggregation layer;

• Simplifies the architecture (requires fewer devices);


• Simplifies management and support with a single network OS. Our architecture deals with server over-subscription at the entry point, then we manage the bandwidth at all other layers to be at line-rate without latency. Therefore, you are not getting congested at the other layers and you’re allowing the traffic to flow. You start having more predictable performance from a QoS perspective.



Slide 34


Key Advanced Routing Features:MPLS Network Virtualization

� Support network segmentation and privacy

• Regional-, departmental-, and project-oriented groups have control over their network assets and configurations for MandA, and divestitures

� Enhances end-user application experience

• Traffic Engineering enables a fine-tuning of the network to deliver appropriate levels of services

� Improve network resiliency

• With features like Fast Re-Route – enabling sub-50 msec. reroute to maintain real-time traffic during a node or link failure

� Boost network scalability and performance

� Scales for future growthSeamless NetworkSeamless NetworkSeamless NetworkSeamless Network

ConnectivityConnectivityConnectivityConnectivity

3333

Key Advanced Routing Features: MPLS Network Virtualization One single technology gives you segmentation, privacy, scalability, reliability, and allows better user experience, by virtue of advanced traffic engineering. Traditional private IP networks do not optimally support real-time applications. Since IP networks lack granular traffic control, for sub-50 millisecond link and node failure detection and re-routing, the alternative is to deploy SONET/SDH. This requires an additional transport layer in the private WAN and data center, which comes at significant additional expense. MPLS, however, provides a cost-effective alternative for the highly resilient network supporting real-time communications. MPLS can be deployed without the additional cost and complexity of SONET/SDH (dark fiber installations and/or Provider Ethernet services). In addition, today's enterprises have several groups of users with specific needs. As the number of groups increases, keeping them separate and secure is a challenge for IT departments. In addition, regulatory environments and business operations sometimes require guarantees of business unit/subsidiary separation. Traditional practices require separate physical and redundant networks to be built. However, the cost of building redundant networks is extremely high. Each separate and redundant network requires its own equipment, WAN access, space and power, provisioning, and management—all making this an expensive proposition. MPLS, however, provides a cost-effective alternative to building and maintaining redundant networks. MPLS enables one physical network to be configured and operate as many separate virtual networks with Layer 2 or Layer 3 VPN services. MPLS:

• Enables consolidation of disparate networks onto a single network;

• Delivers control through traffic segmentation;

• Provides resiliency with fast reroute and traffic engineering; and

• Scales for future growth without compromising performance.



Slide 35


Extending VLAN Knowledge to MPLS

VLAN segmentation is

localized and limited in scale

VLAN Tags (4 bytes)16-bit PID, 3-bit Priority,

1-bit CFI, 12-bit VLAN ID

Layer 2 Segmentation

Spanning Tree Protocol

Active/Blocking

VLAN Trunking

VLAN ACLs

802.1p QoS Markings

Ethernet failures/repairs

VLAN ComponentsVLAN ComponentsVLAN ComponentsVLAN Components

Allows network-wide segmentation

with very large scale

MPLS label stack (4 bytes)20-bit Label, 3-bit QoS (EXP), 1-bit

bottom of stack flag, 8-bit TTL field

Layer 2 and Layer 3 Segmentation

OSPF/LDP

ECMP

LSP Switching

IP ACLs

DSCP/EXP QoS Markings

Fast reroute capabilities and BFD

MPLS ComponentsMPLS ComponentsMPLS ComponentsMPLS Components

Extending VLAN Knowledge to MPLS This slide lists some of the similarities between VLAN and MPLS architectural components. It’s not meant to be a one-to-one replacement of capabilities, but merely used to show the complexity myth (or bad rap) that MPLS receives in the Enterprise market. This is similar to the BGP introduction in the enterprise 10 years ago, and people’s concerns due to perceived complexity. Actually, most enterprise deployments don’t require all knobs and capabilities. There’s an equal or equivalent mapping between what people know in VLANs and what people would have to learn from an MPLS perspective. The objective of this slide is to show that VLANs and MPLS labels are basically the same concept—if you know VLANS, you know MPLS, and you don’t need to relearn a lot of the basic capabilities. The big difference is that, with VLANs, you can only have one VLAN or maybe you can do a MAC-in-MAC encapsulation. You can have only one level of encapsulation in Ethernet. With MPLS, you have the ability to stack labels and each stack of a label gives you a different service definition and that service definition does not require you to change your infrastructure in order to add a new service. Also it allows you to have a lot more than 4,000 services since you have twenty bits as opposed to sixteen bits. Translated to network architecture, this allows you to:

• Use MPLS switching, instead of VLAN switching, and allow for Layer 2, Layer 3, and both at the same time across the network.

• Do virtualization end-to-end and not be bound by just the localized Layer 2 of VLANs.

• Eliminate spanning tree scalability issues. With Ethernet and spanning tree, usually you have several seconds before you can actually detect a failure and recover from that failure. With MPLS in the data center, now you can actually utilize the fast reroute techniques and bidirectional forwarding detection to get you in the SONET range of 50 to 100 milliseconds in failure detection and recovery—which is something that, today, you don’t get.



Slide 36


MPLS Services Enablement

Service enablement is independent of core infrastructure

• MPLS provides same transport infrastructure for different services

• Offers same quality of service over different transport infrastructure through

uniform QOS

3b3b3b3b

MPLS Services Enablement MPLS enables service virtualization independent of core infrastructure. In essence, you can use a common infrastructure but use logical segmentation to run different services. For example, we can route only the services that require firewall filtering through the firewalls. So you may require firewall services for email but you may not require it for storage. So the infrastructure now allows you to send email services to the firewalls.



Slide 37


Juniper Data Center Network ArchitectureVirtualization with MPLS and Security

�Securely isolate

businesses and

applications

�End-to-end QoS from

server to server across

DCs

�Mapping of VLANs to

security zones

�Map VRF’s on core to

routing instances on

SRX

�Establish adjacency

between VRFs on core

�Traffic between

networks runs through

SRX by default, or

filtered on MX

Juniper Data Center Network Architecture Virtualization with MPLS and Security Here you see a Juniper Data Center Network Architecture that provides virtualization with MPLS and security. The key points are:

• It securely isolates businesses and applications;

• It enables end-to-end QoS from server to server across data centers;

• It maps VLANs to security zones;

• It maps VRFs on the core to routing instances on the SRX;

• It establishes adjacency between VRFs on the core; and

• Traffic between networks runs through the SRX by default, or is filtered on the MX.



Slide 38


Key Advanced Routing FeaturesCarrier-Class Reliability

High Availability and Resiliency

4444

Hardware Differentiators Hardware Differentiators Hardware Differentiators Hardware Differentiators

� Optimized ASIC development with I-Chip

� The separation of control plane, services plane, and forwarding plane

� Dedicated hardware assisted processing for CPU intensive services across all platforms

� Pre-calculated paths in hardware

� Failover decision made on line card (PFE)

� Redundancy (Routing Engines, Switching Fabric, and power

Software DifferentiatorsSoftware DifferentiatorsSoftware DifferentiatorsSoftware Differentiators

• Sub-msecond recovery with fast reroute (FRR)

• Nonstop active routing (NSR)

• Transparent software upgrade with unified in-service software upgrade (ISSU)

• Early detection of node and link failure with Bi-directional Forwarding Detection (BFD)

Key Advanced Routing Features Carrier-Class Reliability Let’s now consider the key advanced routing features. Hardware:

•I-chip powered processing delivers unparalleled performance. I-chip is the Layer 3 forwarding ASIC used on the DPCs (Dense Port Concentrators). It has been optimized for edge routing features, class of service (CoS) and scale, and provides the flexibility required to support a wide variety of features in hardware. It supports all IPv4, IPv6, and MPLS forwarding functionality, and also implements Layer 3 CoS, firewall filters, and port mirroring. I-chip also provides interfaces required to connect a PFE to the fabric.

•The modular design with the separation of control plane, services plane, and forwarding plane:

• Enhances resiliency with failure protection and independent restart;

• Scales performance; and

• Enables redundancy. Software:

• NSR is a prerequisite to true ISSU. In order to do ISSU you need to maintain the states of all the communication and protocols across all routing engines. If you don’t maintain the state (which Cisco does not, they do NSF) you are doing a standby re-start, which means you have to depend on the neighbors to give you the state, which takes time. Juniper’s Routing Engine switchover is transparent to network peers, does not require peer participation, does not drop adjacencies or sessions, has minimal impact on convergence, and allows the switchover to occur at any point—no matter how much routing is in flux.



Slide 39


MX Series: Reliable Hardware

� Hard fault tolerance

• Component redundancy

• Routing Engine

• Switch Control Board

• Power

• Cooling

• Environmental sensors

• Redundant boot devices

� Fast MTTR

• Hot swappable components

• Field replaceable components

MX Series: Reliable Hardware The MX Series platform can provide redundant components such as the Routing Engine, the switch control board, power and cooling, and obviously they have environmental sensors and redundant boot devices. That enables us to maintain a very high level of reliability, and it allows us to provide complete redundancy to all the components so that in case one fails we always have backup—from power, cooling, switching, and the Routing Engine. The fact that we can actually do hot-swappable components and field replaceable components allows us also to maintain a faster mean-time-to-repair environment. The less time it actually takes to replace those parts, the sooner the customer is able to reinitiate service.



Slide 40


Graceful RE Switchover (GRES)

Graceful RE Switchover (GRES) The main point we want to highlight here is the fact that the backup Routing Engine has all the state that the primary Routing Engine has, and we have a “keep-alive” mechanism between the Routing Engines so that we can detect failure as quickly as possible. The backup engine, then, takes over the entire system.



Slide 41


Nonstop Active Routing (NSR)4c4c4c4c

Nonstop Active Routing (NSR) In order to have unified in-service software upgrade (ISSU) capabilities, you need not only Graceful Routing Engine Switchover, but also to be able to maintain all the state across the Routing Engines. By maintaining all the routing information, from Layer 2 and Layer 3, and all the protocols across the Routing Engines, there is no latency when you’re going from one Routing Engine to another Routing Engine. While Cisco claims ISSU they do not have the ability to maintain state.



Slide 42


Unified In-Service Software Upgrade (ISSU)

Network globalization means no off-peak traffic periods

• Maintenance windows become difficult to schedule

Need to reduce time and risk of upgrade

• Unstable software with too many fixes and fixes of fixes

• Common industry practice is12-24 months between stable releases of generally deployable code

• Requires extensive manual planning and verification

11.x11.x11.x11.x 12.y12.y12.y12.y

Avoids drawbacks

in piecemeal system update

In-service migration of one Junosrelease to another

Minimizes upgrade time and risk

NSR and GRES are prerequisites

• Upgrade of entire system preserves full integrity of quality and regression testing

• Upgrade path available from any release to another

•Automates operations functions to plan and implement upgrade

•No disruption of control plane and minimal disruption of traffic

Unified In-service Software Upgrade (ISSU) GRES and NSR are prerequisites to unified in-service software upgrade (ISSU). Unified ISSU allows you to go from one Junos OS version to another without having to restart obtaining the state information from your neighbors. Let’s say for example, Junos 10.4 is in the primary Routing Engine: Install Junos 11.1 in the standby Routing Engine; when the secondary RE boots up, it collects all the state information and synchronizes with the primary Routing Engine. Then you can execute the switchover. The standby becomes the primary; the primary becomes the standby—in case there’s a need to fall back, from a routing perspective. Once you’re happy with the upgrade to the newest Junos release, you can upgrade the standby Routing Engine with the same release you just deployed, so you then have the ability to do nonstop active routing in case there’s a failure of the primary Routing Engine. Cisco doesn’t have the full support of NSR. They claim ISSU but, in reality, they do have to reestablish some state after they switch over the Routing Engine. That means you do have some hiccups and, in some cases, you do need the information from your neighbors. We’re the first to do this.



Slide 43


Key Advanced Routing Features: Quality of Service (QoS)

� Flexible and rich set of QoS features• Classification, Marking, Policing and Scheduling

� Flexible system-wide configuration

• Consistent modular QoS policy configuration across platforms

• Verify configurations before committing changes

• After verification, commit all changes at once without single line execution

• Roll back in case of configuration issues

� Line-rate throughput—No performancedegradation

• For QoS functionality such as Extended

ACLS, Etc.

� Standard 8 hardware queues per port

for all Juniper platforms• Option for products with 1000+ hardware

queues

� Consistency across IPv4, IPv6, MPLS and

multicast traffic• Option for products with 1000+ hardware

queues

Improved End User ExperienceImproved End User ExperienceImproved End User ExperienceImproved End User Experience

5555

Key Advanced Routing Features: Quality of Service (QoS) We have flexibility in our QoS implementation. We have consistency in configuration across all platforms. The slide depicts how low latency packets travel. Voice, which requires low latency, gets priority. All other traffic gets serviced with the scheduler. The Juniper MX Series offers a rich set of Diffserv features—classification, rewrite / marking, policing, and scheduling. The modular CLI offers a wide variety of methods to provision QoS—by customer, by protocol, by interface, etc. In addition, the QoS policies are consistent throughout the product portfolio, allowing for easier migration and easier provisioning. In addition, we have the ability to verify configurations before committing—a standard feature of the Junos operating system. All QoS features are implemented natively in the ASICs and in hardware. So, the router continues to forward traffic at line-rate without taking a performance hit. The products offer a standard eight hardware queues per port, with an option to go to thousands of queues if desired.



Slide 44


� MX have the most flexible and sophisticated policers in the

industry

� Apply policers to:• Logical interfaces

• Physical interfaces

• A specific class of traffic

• A specific “color of traffic”

• Any criteria matched within a firewall filter

� Single rate multi-color policers:• Mark one of four colors (using PLP) � Soft policers

• Drop � Hard policers

� Single rate three-color policers:• Mark one of two colors based on two bandwidth buckets and one rate

� Two rate three-color policer:• Mark one of two colors based on two bandwidth buckets and one rate

� Juniper has always supported LLQ

ACL and Policers

ACL and Policers After traffic flows are appropriately classified, the ingress router must condition these flows to ensure that traffic entering the network conforms to the pre-negotiated contract or service-level agreement (SLA). This form of traffic conditioning is accomplished by policing of flows. Policing limits the traffic volume to help enforce SLAs by ensuring the traffic meets a user-defined traffic profile. The MX family of routers supports both soft-policing and hard-policing options. Soft-policing simply signals whether a packet is in-profile or out-of-profile to a congestion control mechanism further down the packet path in the router. It is left to the congestion control mechanism to either drop the packet, or signal to downstream routers to provide a lower class of service to this packet. Hard-policing drops packets that are out of profile. Policers can be configured the following ways:

• They can be assigned to an interface to police all the traffic on that interface; and

• They can be the result of a firewall filter. Junos supports the configuration of the following types of policers on MX Series routers:

• Single rate policers that can drop or mark the loss priority of out of profile packets. The policer is capable of marking all 4 unique loss priorities supported by Junos.

• Single-rate three-color marker (srTCM) policers that color the packet, that is, they only have a soft-policing action.

• Two-rate three-color marker (trTCM) policers that can color the packet, that is, they only have a soft-policing action.



Slide 45


Scheduling

� Properties of a queue• Transmit-rate

• Weights on queues

• Buffer-size• Absorb burst

• Control latency

• Priority• Preferential treatment

during WRR

• Drop profile• Early congestion detection

• Control buffer utilization

5c5c5c5c

� Scheduling is done using a strict WRR priority order • As long as they are within their

SLAs or configured transmit rate

� Five priority levels• Strict-high (lowest latency), High,

Medium High, Medium Low, Low

� Strict-high queue is always serviced first if non-empty to

ensure lowest latency and jitter

Scheduling Scheduling involves port-based or hierarchical per-VLAN queuing. Queues are serviced using a priority Queue Deficit-WRR (Weighted Round-Robin) basis. There are a variety of configuration options to provide congestion control, latency and jitter control, and the ability to absorb bursts. Port-level queuing is supported by configuring up to 8 queues for every port. All VLANs configured on a port share those 8 queues. DPCs consist of 4 Packet Forwarding Engine (PFE) complexes. For port-level queuing, a packet is queued based on the forwarding class that was determined during classification. Multiple forwarding classes can use the same queue, and will share that queue’s scheduling properties. To provide differential treatment among multiple classes of traffic in a queue, the loss priority determined as a result of classification or policing can be used to influence WRED. Varying WRED profiles can be attached to different traffic profiles within a queue, based on the loss priority associated with the packet. The order in which queues are picked for transmission is referred to as the queue scheduling algorithm. Priority and transmission rate configuration of queues are the two components that drive the queue service discipline algorithm. The priority of a queue determines its ordering among other queues in the same port. Junos supports the configuration of the following priorities for queues on MX platforms:

• Strict-High (SH);

• High (H);

• Medium-High (MH);

• Medium-Low (ML); and

• Low (L) The transmit rate of a queue determines the bandwidth usage of a queue. It is the determining factor in how the priority of a queue is used. Queues operate in two priority regions. They operate in the guaranteed priority region when they are using bandwidth less than their configured transmit rate, and they operate in the excess (or bonus) priority region when they have exceeded their configured transmit rate.



Slide 46


Memory Allocation Dynamic (MAD)

� Two ways to configure delay buffer to queues:• As a percentage of the overall interface buffer

• As a value in time or temporal based on the queue’s transmit rate

� Example:• 1G port on a Type3 FPC

• Total Buffer available is 50ms or 6.25MBytes per interface

Memory Allocation Dynamic (MAD) For queues configured with a percentage of the port’s delay buffer, the memory available to buffer packets can grow dynamically based on the actual bandwidth utilized by the queue. This unique strength of the MX platform’s buffer management is called Memory Allocation Dynamic (MAD) MAD provides just the right amount of required buffer to queues based on the current bandwidth utilization of a queue with respect to its peers. Consider the example table above. If queue 0 is utilizing more than 10% of the bandwidth of the port, a static buffer allocation algorithm would still limit the buffer available to the queue to 10% of the port’s buffer. However, such a static scheme does not provide delay-bandwidth buffering. A queue that is using more than its share of configured bandwidth should be able to use more than its configured shared of buffers to provide effective delay-bandwidth buffering. Using MAD, Queue 0 can absorb bursts more effectively. The amount of additional dynamic buffer available to a queue is determined precisely based on the amount of additional bandwidth used by a queue. Such a situation arises when other queues on the same port use less than their share of allocated bandwidth. The amount of dynamic memory provided by MAD is continually updated as a weighted averaging function of the bandwidth used by the queue. For all memory calculations, this weighted average is used instead of the statically configured memory allocation.



Slide 47


Rewrites / Marking

� Ingress DSCP Rewrite

•Supported on IQE, IQ2E and IQ2 PICs

� Egress

•Rewrite IP Precedence, DSCP, EXP and IEEE 802.1p bits to

affect BA determination and CoS treatment at the next hop

router.

•Define your own or apply default rules.

•Rewrite MPLS EXP and IP header values simultaneously.

•Rewrite MPLS EXP and IEEE 802.1p bits.

•Rewrite MPLS EXP bits on multiple labels simultaneously.

Rewrites / Marking The classification, policing, and queuing stages of a packet’s CoS treatment pertain to the current-hop router. The motivation of packet rewrite is to efficiently convey a packet’s CoS profile to the next-hop router based on both the information sent by the previous-hop router, and the CoS profile of the packet in the current-hop. On MX routers, Junos uses the forwarding class and loss priority to determine the CoS value that is written in the packet’s header. The protocol of the outgoing packet, along with configuration, determines in which headers and where in the headers the rewrite takes place. Junos also provides default rewrite tables, that map pre-defined forwarding classes and loss priority values to a protocol’s CoS values, for various protocols. This can be used in lieu of defining custom rewrite tables. Junos supports the configuration of multiple custom rewrite tables per protocol that enable different topologies and protocols to flexibly apply various combinations of class and loss priority to header markings based on the demands and design of the network.



Slide 48


WRED

� Detect congestion early, and drop packets.

•Notify sender of congestion sooner, rather than later.

� Four levels of drop precedence/packet.

•based on input classification or policers, including trTCM.

� User configurable drop-profile map

•allows up to 64 fill-levels to drop-probability mapping.

� Forwarding class and packet drop priority determine

drop profile used.

•Allows precise differentiation and reaction to delay-sensitive

voice/video traffic, and bursty best-effort data traffic.

WRED Congestion control and avoidance is implemented by selectively dropping packets based on user configurable drop profiles, the forwarding class, and loss priority assigned to a packet by classifiers and policers. The primary mechanism for dropping packets is Weighted Random Early Drop (or WRED). WRED provides fine grained user-configurable options to control the level of buffer utilization for various profiles of traffic in the same queue. WRED is a probabilistic way to drop packets to both avoid and control congestion. A WRED profile contains several points of queue utilization to drop probability associations. Every association corresponds to the current level of buffer utilized by the queue, and the probability with which packets can be dropped at that level. Junos supports the following configuration mechanisms for WRED:

• Up to 64 queue buffer utilization to drop probability associations per WRED profile.

• Configurable WRED profiles to control buffer utilization for up to 4 traffic profiles in a queue.

• A strict buffer utilization threshold, using temporal configuration, to precisely control the maximum latency and jitter for up to 4 traffic profiles in a queue.

The WRED profile applied to a packet is determined by the queue that the packet is assigned to and the loss priority of the packet. Each queue can be configured with 4 WRED drop profiles. Each drop profile is unique in the aggressiveness with which packets are dropped. For instance, a packet that is within its configured traffic profile can be dropped only when the queue is full. A packet that is over its configured traffic profile can be dropped more aggressively in the presence of congestion.



Slide 49


Key Advanced Routing Features Low Latency Multicast

• Full support for native multicast

• Leader in P2MP MPLS for Optimal Network Replication

Improved Application PerformanceImproved Application PerformanceImproved Application PerformanceImproved Application Performance

• Highest PerformanceHighest PerformanceHighest PerformanceHighest Performance• Distributed hardware based multicast replication and scale

• Super-fast (sub-second) convergence on the control plane

• Scalable and event-driven protocol processing

• Full NSR support for all multicast protocols

6666

Key Advanced Routing Features Low Latency Multicast We have full native multicast capabilities. In addition to basic MC protocols and capabilities, we are a leader in P2MP MPLS, which optimizes the network utilization. Instead of having to do tunnels across your MPLS cloud, that replicate everything at the entry point (for example, MC to 1,000 destinations, instead of replicating it a thousand times), we replicate more efficiently by going down the tree at the point where the packets need to be replicated. Therefore, there is no head-of-line blocking, which reduces utilization and reduces impact on the entry point. On the slide you see PE1 is replicated to P1 and P2, and they replicate to other routers; instead of PE1 distributing to every router, it only replicates to adjacent routers. This is distributed network replication or P2MP. We do this distributed network replication in the hardware as part of the architecture and we support sub-second convergence on the control plane. Here are the details:

• Forwarding path is fully ASIC based;

• Very low latency for high priority packets—guaranteed during congestion;

• High priority packets have latency of 20 microseconds through the router;

• Fabric uses high speed interconnects;

• Memory-less fabric achieves negligible latency;

• Efficient line-rate multicast;

• Efficient 5 stage binary replication eliminates the need to have an over engineered fabric;

• No head-of-line blocking;

• Large fan-out has little/no impact on performance;

• Multicast packets use the same QoS policies as Unicast;

• High and Strict-High priorities;

• Control over latency of a queue in the event of a congestion; and

• Classifiers, Rewrites, and Schedulers to indicate QoS treatment.



Slide 50


� Group Membership Protocol – Enables hosts to dynamically join/leave multicast

groups. Membership info is communicated to nearest router

� Multicast Routing Protocol – Enables routers to build a delivery tree between the

sender(s) and receivers of a multicast group

Group MembershipProtocol (IGMP)

Multicast Routing Protocol(PIM, P2MP w/ MPLS)

IP Multicast Components

IP Multicast Components Here we show how IP multicast delivery tree works. We have a few receivers on the right hand interested in receiving MC stream. They send joins to the next hop router. The set of routers in between implement a multicast routing protocol in the IP world; it could be PIM (Protocol-Independent Multicast) or DVMRP (Distance Vector Multicast Routing Protocol) and in the MPLS world it could be point-to-multipoint with traffic engineering (TE) capabilities. The source essentially sends a multicast stream to the various receivers and the receivers—depending on their policy, depending on who they’re interested in receiving the traffic from—can choose to get traffic from a source or multiple of these sources. Fundamental to the delivery of multicast traffic, as we all know, is the delivery tree and there are multiple ways you can actually build this tree. The reason we emphasize the delivery tree is because it has an implication on latency with multicast.



Slide 51


Multicast Distribution Trees 6b6b6b6b

Multicast Distribution Trees There are multiple ways you can actually build a multicast distribution tree; the two common ways are referred to as the source tree and the shared tree. In the source tree the traffic is routed at the source, and you can see that in the diagram to the left. The distribution actually happens from the source to the various receivers (designated by the red line) and this is primarily useful for one-to-many distribution because everything is routed at the source and, as you can see, the delivery follows a highly optimal path, which in turn minimizes delay. On the right you have your shared tree, wherein you have multiple sources sending traffic to a single core or, in the case of PIM, it could be the RP, and traffic is essentially routed from that point to various receivers. If you follow the red line between source 1 and source 2, you can see that all traffic from source 1 and source 2 makes it to the core, or the RP, and you have a distribution tree from that point to the various receivers. As a consequence, you can see that the paths may always be optimal or, depending on the topology that you have—depending on the network policy that you have—the paths could really be sub-optimal, but you will be able to support multiple sources in a single distribution. In terms of processing that needs to happen along the way, in the source tree case it’s an order of magnitude higher; it really depends on the number of sources and the number of groups that you have, because everything is routed at the source. In the case of a shared tree, it’s just a function of the number of groups, because all the sources follow the same shared tree. Again, depending on the topology and depending on the paths from the source to the receivers, that’s where you could have a difference in latency. That covers the basics of multicast—especially in the context of low latency.



Slide 52


Dissecting End-to-End Network Latency

Dissecting End-to-End Network Latency Dissecting end-to-end latency between the source and the receivers, you can see that on the diagram above there are three main components that actually introduce delay.

• Forwarding delay in a router that is a direct function of the packet processing capabilities of the router; the ASIC architecture that is used, the kind of buffer management and queuing capabilities of the router and so forth. We’ll look at how the high engine of routers actually implements a really advanced ASIC architecture so that you can achieve low latency multicast.

• Transmission delay which is the time it takes to place a packet on to the wire and to send it out. This is a direct function of the port speed, so if you are really interested in micro second type latencies, then going for higher bandwidth ports is a direct necessity.

• The propagation delay is essentially that of physics. On an average you can roughly expect about 0.8 to 0.85 micro seconds per mile between the two end points. In order to reduce this latency you reduce the distance between the source and the receivers.

Putting it all together, you can see that the N2 and latency is a function of the forwarding delay—the transmission delay and the propagation—and each one of these components directly impacts the latency in your network.



Slide 53


ASIC Based Forwarding and ReplicationASIC Based Forwarding and ReplicationASIC Based Forwarding and ReplicationASIC Based Forwarding and Replication

Optimal Multicast Replication Distributed Forwarding

� Distributed, shared memory

architecture for highly

available non-stop unicast and

multicast forwarding

� Fabric speed-up for

line-rate, low latency multicast

replication

� Multicast packets use the

same class-of-service policies

as Unicast packets

� IPv4 and IPv6 Multicast and

MVPN support

Optimal Multicast Replication Distributed Forwarding To reduce forwarding delay, you need highly optimized hardware for multicast delivery. This is an example of an MX Series box, and it is equally applicable to other boxes as well. There are two routing engines at the top which implement the control plane; you have a pair of DPCs at the two sides of the box that have four PFEs (packet forwarding engines) inside it. Each PFE forwards traffic to an aggregate of about 10-Gigabit Ethernet. If you start with the arrow from the source, there is a 10-Gigabit Ethernet feed coming into a PFE. This gets replicated to two other PFEs over the crossbar fabric and each PFE that receives it, in turn replicates it to two other PFEs and this process continues until all the other receivers or the receivers of interest actually receive the traffic. There are multiple advantages to employing this kind of architecture.



Slide 54


Low Latency Multicast MX Series Optimized Hardware, Feature Rich Software

Optimized HardwareOptimized HardwareOptimized HardwareOptimized Hardware

� MX supports line rate replication and forwarding to every port

• MX960: 10Gbps � 176 10Gbps port



� Multicast source port is line rate bi-directionally

• 10G source port can receive 10Gbps of multicast traffic destined to other ports, and still process and transmit 10Gbps to the line.

Feature Rich Junos

IGMP v1,2,3• MX960: 10Gbps � 176 10Gbps port



Multicast Routing Protocols• PIM-SM, PIM-DM, DVMRP, PIM-SSM

P2MP with Traffic Engineering (TE)

MSDP

IPv6 Multicast• MLDv1,3 – Equivalent of IGMP• PIM-SM same as in IPv4r

Low Latency Multicast MX Series Optimized Hardware, Feature Rich Software The MX Series provides ASIC-based forwarding and replication in order to reduce latency. The MX Series can replicate multicast traffic at line rate on every port—that is, from any port, to any port, at line rate bi-directionally. A 10-Gigabit source port can receive 10Gbps of multicast traffic destined to other ports and still process and transmit 10Gbps to the line. For example, when the MX960 receives one stream of 10-Gigabit Ethernet it can replicate to all other 10-Gigabit Ethernet ports at line rate (this includes the 16-port 10-Gigabit Ethernet card). In addition, the Junos OS offers a rich set of multicast features including IGMP, P2MP with traffic engineering, and IPv6 Multicast.



Slide 55


P2MP LSP: Optimizing Multicast Over the WANPoint to Multipoint MPLS Point to Multipoint MPLS Point to Multipoint MPLS Point to Multipoint MPLS

P2MP LSP: Optimizing Multicast Over the WAN P2MP is a Point to Multipoint Label Switched Path (or LSP). It provides efficient traffic replication in the network and is application agnostic. You can utilize the MPLS infrastructure with P2MP LSPs across the core—which means you eliminate the need four multicast routing protocols in the WAN, which reduces configuration and maintenances complexity, as well increases network availability. Picture: A corporate WAN which is connected to 3 data centers. How can you have efficient delivery of multicast traffic over the WAN? By implementing MPLS at the core, you can logically segment the data centers, remote offices, corporate WAN. With the MPLS super core you can have multiple LSPs that provide data center-to-data center or corporate WAN to-data center connectivity. The advantage here is that you can use the fast re-route and also the failover characteristics of MPLS to precisely control the amount of latency. Let’s say we have the data center at the bottom left that needs to connect or multicast traffic to the data centre at the top right over the blue LSP, then you establish a primary LSP that connects these two data centers indirectly and you also establish a backup LSP, let’s say the red LSP, going from one data centre to another and then to the other data centre, so that in the event of failure you precisely know how much additional latency, there will be in the network. Having this type of predictability under failure conditions is critical and is really important, especially for the applications that are extremely latency-sensitive. Point-to-multipoint allows you to engineer traffic based on policy, based on QoS into specific point-to-multipoint tunnels and you can send this across the wide area to the multiple end points on the other side of your MPLS core.



Slide 56


What Is P2MP MPLS TE?

What Is P2MP MPLS TE? A traditional point-to-point LSP has one ingress point and one egress point, but a point-to-multipoint LSP has a single ingress node with multiple egress nodes. Router A1 is configured with a point-to-multipoint LSP to routers P1, P2, P3, and P4. When router A1 sends a packet on the point-to-multipoint LSP to routers P1 and P2, router P1 replicates the packet and forwards it to routers A2 and A4. Router P2 sends the packet to router A3 and A5. P2MP is the MPLS equivalent of IP multicast. In this example, at the top, A1 needs to send multicast traffic to all the other end points—A2, A3, A4 and A5—in an optimal way. If you just use MPLS without P2MP, then A1 has to replicate 4 times over each LSP to each of those end points. This is not efficiently utilizing bandwidth. If you use P2MP you can replicate at the point of interest. On the right side of the diagram, you send multicast traffic from A1 to A3 and A5 by sending one single stream from A1 to P2, and from that point you replicate to A3 and P3, and P3 then sends the traffic to A5. Instead of replicating twice at A1 and sending traffic across two LSPs to A3 and A5, you are sending a single stream to the P2 router and then using P2MP capabilities to replicate traffic to some of the other routers. Advantages include:

• Resiliency and resource reservation capabilities to native multicast

• Bandwidth efficiency compared to ingress replication—no multicast state in the core of the network

• TE (traffic engineering): the ability to control the path of traffic; CAC (Call Admission Control) and bandwidth guarantees



Slide 57


IP Multicast Versus P2MP MPLS TE

IP Multicast Versus P2MP MPLS TE This is an overview of what P2MP provides over IP multicast.

• The first and foremost advantage of using P2MP is resource reservation—because P2MP uses an underlying MPLS infrastructure and hence all the signaling associated with it, you now have capabilities to reserve resources. What that means is for your applications, let’s say for your HR applications, for some of your critical real-time applications and for some of your other applications, you can specifically reserve a 10 meg bandwidth or a 20 meg bandwidth and have multicast run over that; that is not possible using IP multicast today.

• Explicit Routing—The other capability is you can specifically choose the node that you want to take along your network path. An example in the diagram that we saw, you could actually choose your primary path and you could also choose your secondary path and that essentially takes two different nodes along the network path. IP multicast cannot allow you to do that.

• From computation, flexibility—IP multicast, uses receiver-initiated trees and so there is a little bit of complexity in doing some computation as opposed to P2MP that allows the head-end or the route to do all the signaling. Hence you can actually achieve a good level of flexibility and you can also do some really complex bandwidth management and so on and so forth with P2MP.

• Fast reroute; we looked at a specific example with the blue LSP and a standby red LSP. With MPLS and P2MP you can actually get SONET-like failover characteristics.

• State Maintenance—With IP multicast you have a lot of state to maintain—I, G, *, G-type state. With P2MP, because of RSVP refresh reduction that’s already built into the system, you have scalable state maintenance. The network node only needs to understand point-to-multipoint, rather than full multicast.



Slide 58


Resiliency with P2MP

Resiliency with P2MP There are a lot of advantages in using point-to-multipoint. From a resiliency standpoint, you can specifically designate a path. On this particular diagram on the slide, we show a primary path from A1 to A5 that takes the intermediate points P1 and P3, and there is also a backup path that takes A1 to P1 to P2 to P3 to A5. So, if the link between P1 and P3 goes down (represented on the diagram by the solid red arrow) then you automatically switch over to the backup path (represented by the blue dashed arrow on the diagram). With MPLS on an Ethernet link you will be able to achieve 50 millisecond payload characteristics if you use point-to-multipoint.



Slide 59


Section Summary


•Described the elements that provide the Juniper advantage

in high end routing

•Explained how Junos reduces complexity

•Discussed the Junos Trio Chipset

•Cited examples of savings with Juniper

•Discussed the unmatched capacity of the MX 3D

•Discussed the need for advanced routing

•Described Juniper’s various advanced routing features


• Described the elements that provide the Juniper advantage in high end routing;

• Explained how Junos reduces complexity;

• Discussed the Junos Trio Chipset;

• Cited examples of savings with Juniper;

• Discussed the unmatched capacity of the MX 3D;

• Discussed the need for advanced routing; and

• Described Juniper’s various advanced routing features.



Slide 60


� Juniper Networks enables you to build a highly

virtualized data center network that has which of the

following characteristics? (Select all that apply.)


A) Eliminates the aggregation layer

B) Simplifies the architecture to require fewer devices

C) Reduces space, power, and cooling requirements

D) Simplifies management and support




Slide 61


� In which two of the following ways does Juniper

Networks reduce network complexity? (Select two.)


A) Single operating system across all hardware

B) Collapsed architecture

C) Carrier-class reliability

D) Scalability




Slide 62



� Which of the following are key advanced routing

feature offered by Juniper? (Select all that apply.)

A) MPLS

B) Carrier-class reliability

C) QoS

D) Low-latency multicast




Slide 63



� True or false: To have unified ISSU capabilities, you

need not only GRES, but you must also maintain all

the state across the Routing Engines.

A) True

B) False




Slide 64


Enterprise Product Portfolio

MX Series

Technical Overview

Next, we’ll cover Juniper’s Enterprise Product Portfolio.



Slide 65


Section Objectives


able to:

•Describe Juniper’s MX Series product family

•Identify MX platform components and capabilities

• Discuss positioning of the MX Series

• Describe Junos Space


• Describe Juniper’s MX Series product family;

• Identify MX platform components and capabilities;

• Discuss positioning of the MX Series; and

• Describe Junos Space.



Slide 66


One Junos

One Trio Chipset

One Universal Edge

MX 10 MX 960MX 480MX 40 MX 80 MX 5 MX 240

80Gbps80Gbps80Gbps80Gbps60Gbps60Gbps60Gbps60Gbps40Gbps40Gbps40Gbps40Gbps20Gbps20Gbps20Gbps20Gbps

MX 2010MX 2010MX 2010MX 2010 MX 2020MX 2020MX 2020MX 2020

4.8 Tbps4.8 Tbps4.8 Tbps4.8 Tbps

8.8 Tbps8.8 Tbps8.8 Tbps8.8 Tbps

1.6Tbps1.6Tbps1.6Tbps1.6Tbps

Single Portfolio: 20 Gbps to 80 Tbps

40Tbps40Tbps40Tbps40Tbps

80808080TbpsTbpsTbpsTbps

Expanding the Universal Edge

NEWNEWNEWNEW

MX104 MX104 MX104 MX104

The Future of the Edge has Arrived

NEWNEWNEWNEW

NEWNEWNEWNEW

80Gbps80Gbps80Gbps80Gbps

Expanding the Universal Edge MX Series 3D Universal Edge Routers are Ethernet-centric services routers that are purpose-built for the most demanding carrier and enterprise applications. Powered by the Junos OS and the Junos Trio chipset, the MX Series delivers unprecedented scaling in bandwidth, subscribers, and services, that ensures investment protection in even the fastest growing markets. One Junos OS…One Trio Chipset…one family of powerful, open, service rich platforms covering a breadth of applications from 20Gbps all the way up to 80Tbps.



Slide 67


Midrange Routing Solutions

Family of 2RU High Performance MidFamily of 2RU High Performance MidFamily of 2RU High Performance MidFamily of 2RU High Performance Mid----Range RoutersRange RoutersRange RoutersRange Routers

� MX5MX5MX5MX5: 20Gbps router - 20x1G

� MX10MX10MX10MX10: 40Gbps router - 20x1G and 1 Modular Slot

� MX40MX40MX40MX40: 60Gbps router - 2x10G and 2 Modular Slots

� MX80:MX80:MX80:MX80: 80Gbps router - 4x10G and 2 Modular Slots

Option to upgrade from MX5Option to upgrade from MX5Option to upgrade from MX5Option to upgrade from MX5----> MX10> MX10> MX10> MX10---->MX40>MX40>MX40>MX40---->MX80>MX80>MX80>MX80

� Support for WAN (TDM) WAN (TDM) WAN (TDM) WAN (TDM) interfaces in modular slots

• Including MIC-3D-8DS3-E3

Pay-As-You-Grow

and Interface

Diversity

Upgradeability

20G -> 80G

10/100 -> 10G

OC3 -> OC48

Advanced Routing

Logical SystemsSmall Footprint

Service MIC support in Service MIC support in Service MIC support in Service MIC support in

rear slot (2T2013)rear slot (2T2013)rear slot (2T2013)rear slot (2T2013)

MX5

MX10

MX40

Midrange Routing Solutions Let’s take a look at the lower end of the MX Series edge solution portfolio. Back in 2008, Juniper started shipping the MX80 chassis with up to 80 Gbps bi-directional support offering two modular slots and four 10-Gigabit Ethernet ports. This solution has been very successful in the enterprise edge market and we acknowledged the desire for lower bandwidth needs for the enterprise as well as managed services. Therefore, Juniper developed the MX5, MX10, and MX40 chassis based on the same MX80 hardware architecture. There is an upgrade path from the MX5 all the way to the MX80 by means of licenses. Since the MX5 through MX40 chassis are based on the same MX80 hardware, a hardware upgrade is not required, just a software license. In addition, these lower end chassis have been designed from the beginning to support high performing services, and a service MIC slot is available in the back of the chassis which will support the service MIC, available in 2013. Another point to emphasize is that this lower range of the MX product portfolio also supports WAN (TDM) interfaces in modular slots. The MX5, MX10, MX40, and MX80 are compact platforms for enterprise applications, space and power constrained service provider facilities, and as a customer premises equipment (CPE) for managed services.



Slide 68


Midrange MX Series ComparisonMX5MX5MX5MX5 MX10MX10MX10MX10 MX40MX40MX40MX40 MX80MX80MX80MX80 MX104MX104MX104MX104

Capacity 20Gbps 40Gbps 60Gbps 80Gbps 80Gbps

Height (RU) 2 2 2 2 3.5

Slots 1 MIC 2 MIC 2 MIC 2 MIC 4 MIC

BW / Slot 20Gbps 40Gbps 60Gbps 80Gbps 80Gbps

10-Gigabit Ethernet Ports 2 4 6 8 12

Redundant RE No No No No Yes

Redundant Fabric No No No No No

Redundant PowerYes

AC/DC

Yes

AC/DC

Yes

AC/DC

Yes

AC/DC

Yes

AC/DC

ETSI -300mm depth No No No No Yes

Temperature Hardened No No No No Yes

# of Service MIC 1 1 1 1 2

Midrange MX Series Comparison The table on this slide provides a comparison of the midrange MX Series routers, from the MX5 to the MX104.



Slide 69


MX80 3D Ethernet Services RouterMost Powerful 3.5” Router

MX80 3D Ethernet Services Router—Most Powerful 3.5” Router This slide takes a closer look at the MX80 3D Ethernet services router, the world’s most powerful 3.5” router. In both fixed and modular versions, it has ample capacity. This would be suitable for the campus, data center, or any small sites needing WAN connectivity.



Slide 70


MX80 Models

2 MIC Slots

• 20x1SFP, 2x10 XFP, 40x1 RJ-45

• 100FX, 100BX

4x10GE XFP built in ports

1 Services Slot

2 UART ports (Clock input/output),

BITS input

Hierarchical QoS (per VLAN

queuing)

• License based queues

Synchronous Ethernet enabled

Modular ChassisModular ChassisModular ChassisModular Chassis Fixed ChassisFixed ChassisFixed ChassisFixed Chassis

48x1 RJ-45 ports

� 8 ports more than MIC

� 10/100/1000

4x10GE XFP built in ports

1 Services Slot

Per Port Queuing

MX80 Models The MX80 comes in two form factors: Modular and Fixed. The details of the two form factors are as follows: Modular Chassis

• 2 MIC Slots;

•Four built-in 10-Gigabit Ethernet XFP ports;

• 1 Services Slot;

• 2 UART ports;

• Hierarchical QoS (per VLAN queuing); and

• Synchronous Ethernet enabled. Fixed Chassis

• 48 10/100/1000 RJ-45 ports;

• 8 more ports than the modular chassis with MICS;

•Four built-in 10-Gigabit Ethernet XFP ports;

• 1 Services Slot; and

• Per Port Queuing.



Slide 71


MX104: Expanding the Aggregation Market

Space-constrained CO’s

Harsh environments

Outside plant and RTs

Trio ASIC based PFE

Resilient control plane

MIC slots for optimal configs

10GbE ports: full line-rate

Hardware based time stamping

NG-access ready, xPON, AE

An Aggregation Platform for Every

Access

MX Continuity, Resiliency, and

Modularity

Raising the Bar

MX104

80 80 80 80 GbpsGbpsGbpsGbps�4x 10GbE fixed ports

(SFP+)

�4 MIC slots

�Ethernet, TDM, and ATM MICs

3.5RU chassis

240mm Deep

GbE=Gigabit Ethernet

MX104: Expanding the Aggregation Market The MX104 is Juniper’s response to a shift in metro network architecture where the aggregation layer is assuming responsibility for the service provider edge. The MX104 simplifies metro architectures by eliminating unnecessary layers, dramatically reducing CapEx and OpEx. The MX104 router is optimized for aggregating mobile, enterprise WAN, business, and residential access services. The MX104 comes in a space-efficient 3.5 rack unit chassis and supports 80 Gbps of throughput, setting a new benchmark for port density in its product category.



Slide 72


MX Series Chassis Overview

MX240 MX480 MX960 MX2010 MX2020

Max system

witching Capacity

(1/2 duplex)

1.6Tbps 4.8Tbps 8.8Tbps 40Tbps 80Tbps

Height (RU) 6 8 16 34 45

Slots 2 6 11 10 20

Forwarding*

capacity/slot240Gbps 240Gbps 240Gbps 860Gbps 860Gbps

10GE Ports* 48 136 256 260 520

Redundant RE Yes Yes Yes Yes Yes

Redundant Fabric Yes Yes Yes Yes Yes

Redundant Power Yes - AC/DC Yes - AC/DC Yes - AC/DC Yes – AC/DC Yes – AC/DC

* Current capacity, system capacity is higher

MX Series Chassis Overview The MX240 delivers increased port density over traditional Ethernet platforms, as well as performance, scalability, and reliability in a space efficient package. The MX240 offers fully redundant hardware options that include redundant Switch Control Board (SCB) and Routing Engines to increase system availability. The MX480 provides a dense, highly redundant platform primarily targeted for medium to large enterprise campus and data centers, and dense dedicated access aggregation and provider edge services in medium and large points of presence (POPs). The MX480 offers common hardware redundancy options that include the SCBs, Routing Engines, fan trays, and power supplies. The MX960 is a high-density Layer 2 and Layer 3 Ethernet platform designed for deployment in a number of Ethernet scenarios. For service providers, the wide range of Universal Edge applications supported by the MX960 includes VPLS for multipoint connectivity, virtual leased line for point-to- point services, full support for MPLS VPNs throughout the Ethernet network, Ethernet aggregation at the campus/enterprise edge, and Ethernet aggregation at the multiservice edge. In the enterprise, the MX960 can be used for campus and data center core and aggregation as well as a WAN gateway. The MX2020 and MX2010 routers provide a common platform for the delivery of powerful routing, network services, and application enablement for a consolidated, financially optimized network model, scaling up to 80 Tbps and 40 Tbps respectively and allowing network operators to fully leverage assets. Both the MX2020 and the MX2010 share a common set of fans, power modules, Switch fabrics, and CB-REs. The MX2010 is half the number of slots, but with all the same powerful capabilities. MX Series 3D Universal Edge Routers scale in bandwidth, subscribers, and services, to meet the rapidly growing needs of enterprises and service provider networks of any size.



Slide 73


� 14 Slot Chassis

� Physical size• Height: 16RU (about 1/3 rack), Depth: <800mm deep

� System capacity

• 14 slots - 2 for Fabric Cards / REs with the option of 1 additional SCB for redundancy

• Up to 3.84 Tbps with the new 16 Port 10GbE line card

� Dependable hardware• Passive Mid-Plane

• Redundant Routing Engines

• Redundant Switching Fabric (2+1)

• Distributed Packet Forwarding Architecture

• Redundant Fan and Power

� Power and cooling• Front-to-back cooling with separate push-pull fan assemblies

• Holds up to 2 fan trays (1+1 redundancy)

• Holds up to 4 power supplies (2+2 DC, 3+1 AC)

• Rear-side power cabling

MX960MX960MX960MX960

MX960 Ethernet Services Router

MX960 Ethernet Services Router The MX960 is a 1/3 of a rack system. That’s important because every time you highlight the density to a customer, you can easily highlight the fact that the MX960, with the new line cards we’ve introduced, has 172 ports of 10 Gig—in 1/3 of a rack! So you can imagine that, for a lot of the large datacenter deployments out there, we have 172 times 3 in a single rack – and that’s how many ports you will actually be able to install into a single MX product. An important thing to highlight about this product as well is not just that fact it has a very high density number of ports for 10 Gig, but also that it’s a platform that’s preferred in a lot of data centers because of its front-to-back cooling. Instead of side-to-side cooling, the front-to-back cooling plays much better for many data center deployments. That’s one of the preferred mechanisms and the reason why many customers prefer this product. The nice thing about the MX product family, which includes the MX240, MX480, and MX960, is that all the line cards—the DPCs (Dense Port Concentrators) as well as the new Trio-based line cards, the MPCs (Modular Port Concentrators)—are interchangeable between all of these products. The routing engine is interchangeable, and the switch control card, which is the switch fabric, is also interchangeable between all of these cards.



Slide 74


MX960 Components

MX960 Components Here a few more of the MX960 components are highlighted. You need to ensure customers understand the terminology, as it differs from that used by other vendors. The DPC is for the current I-chip-based ASIC line cards. The MPC is for all the line cards that are based on our new Junos Trio ASICs. We have the routing engines and the switch control board. The routing engine is a daughter card to the switch control board, and you can see that, in the upper right hand corner, it’s a modular mechanism. The routing engine slides into the control port. You can see here how the previously mentioned front-to-back cooling has air intake at the bottom front, with the outtake at the back top of the system.



Slide 75


MX480 Ethernet Services Router

� 8 Slot Chassis (6+2)

� Physical size• Height: 8RU (about 1/6 rack), Depth: <800mm deep

� System capacity• 8 slots - 2 for Fabric Cards / REs

• Up to 1.92Tbps with with the new 16 Port 10GbE line card


• Redundant Routing Engines



• Redundant Fan and Power

� Power and cooling• Side to Side cooling

• Holds single fan tray

• Holds up to 4 power supplies (2+2 DC, 2+2 AC 240V, 3+1 AC 110V)



MX480 Ethernet Services Router The next product in the family is the MX480. It’s a smaller form factor, but the routing engine, the switch control boards, the line cards – regardless of whether they’re DPC or MPCs—they’re all part of the same product family, so they’re all interchangeable. This product offers half the capacity of the MX960; it has half the number of slots and, in this particular product, there are dedicated slots. There are two slots specifically for the routing engine switch control board and 6 slots specifically for the I/O cards, the DPCs and the MPCs. With the MX480, we have now introduced the capability to power the system with either high voltage (240 volts) or low voltage (110 volts). And the same 16-port 10 Gig card can go into this system.



Slide 76


MX240 Ethernet Services Router� 4 Slot Chassis (2+2 or 3+1)

� Physical size• Height: 5RU, Depth: <800mm deep

� System capacity

• 4slots – 2 available for Fabric Cards / REs

• Up to 960Gbps with the new 16 Port 10GbE line card

• System reuses existing SCBs, REs, and DPCs – common across all MX platforms


• Redundant Routing Engines (2+2 configuration)



• Redundant Power

� Power and cooling• Side to Side cooling Holds up to 2 fan trays (1+1 redundancy)

• Holds up to 4 power supplies (1+1 DC, 1+1 AC 200-240VAC, 2+2 AC 100-110VAC)



MX240 Ethernet Services Router The MX240 provides half of what the MX480 offers. As shown here, you have either 2 or 3 slots you can use for I/O cards. If you do require redundancy in the routing engine and the switch fabric, then you can only use 2 slots for I/O. If you do not require redundancy in the routing engine and the switch control board (the switch fabric), then you can use 3 of the slots in the system. So, basically, the second slot from the bottom is a dual purpose slot. And, just like the MX480, this product can be powered by either 240 or 110 volts.



Slide 77


MX 3D Aggregation Economics and Experience

Best 10GbE Capacity and Density

� 16 x 10GbE ports� 160 Gbps capacity

Applications

� Designed for high density, bandwidth

intensive needs

� Enterprise Core/Backbone� Enterprise Metro Network

Experience and Economics

� Capacity and density� Most power efficient

� L2, L3, and MPLS features of MX family

Unprecedented Port Density

and Performance

MX 3D Aggregation Economics and Experience The 16-port 10-Gigabit Ethernet fixed configuration MPCs for the MX Series 3D routers provide unprecedented port density and performance for the metro core and for large enterprises. The 16-port 10-Gigabit Ethernet MPC provides full wire-rate performance for the ports. This card is designed to be deployed in the Juniper Networks MX240, MX480, and MX960 3D Universal Edge Router, and it supports all of the Layer 2, Layer 3, and MPLS features currently available on the existing set of Dense Port Concentrator (DPC) line cards. The 16-port 10-Gigabit Ethernet MPCs provide port-based queuing with eight queues per port. The high throughput performance of the 16-port 10-Gigabit Ethernet is delivered with the industry leading Juniper Networks Junos Trio chipset. The Junos Trio chipset is also found on Juniper’s other MPCs and on the Juniper Networks MX80 3D Universal Edge Router.



Slide 78


MX 3D 100 Gigabit Ethernet Line Card Experience, Economics, and Ecosystem

Characteristics

� Line rate performance (up to 130Gbps)� Modular Design for future optics options

� 802.3ba compliant

MIC Form Factors

� 100GBASE-LR4 (CFP MIC)� 100GBASE-SR10 (CXP MIC)

� 2x40GbE QSFPP MIC with support for SR4and LR4 optics

� 10x10GbE (SFPP-MIC)

Experience, Economics, and

Ecosystem

� Full scale L3VPN and VPLS

� Service Rich Processing

WAN Edge Services

Applications 100 GbE Card

Full MPLS Features

All MX Functionality

100 GbE Modular Line Card

�

�

�

MX 3D 100 Gigabit Ethernet Line Card Experience, Economics, and Ecosystem The MX Series 3D Universal Edge Routers have been architected from day one to support 100-Gigabit Ethernet interfaces. The new Juniper Networks 100-Gigabit Ethernet MPC card delivers the industry’s first modular 100-Gigabit Ethernet interface on MX Series routers with line-rate forwarding. The 100-Gigabit Ethernet MPC card provides for aggregate bandwidth up to 130 Gbps, and it ensures compliance with the 802.3ba standard. It will have two Modular Interface Controller (MIC) slots, with each MIC slot capable of supporting 100-Gigabit Ethernet, 40-Gigabit Ethernet, and 10-Gigabit Ethernet interfaces.



Slide 79


MPC4E: Monolithic 10- and 100-Gigabit MPC

Line Card 1: 32x10GbE SFP+ ports

Applications

Full Scale Routing

260G MPC

VPLS, L3VPN, L2VPN

Service Rich

Line Card 2:

2x100GbE CFP & 8x10GbE SFP+ ports

Trio chipset

Now Shipping

240Gbps on MX960, MX480,

MX240; 260Gbps on MX2000

802.3ba compliant

�

�

�

MPC has 260G of bandwidth

capacity

32x10GbE SFPP ports

2x100GbE CFP + 8x10G SFPP ports

MPC4E: Monolithic 10- and 100-Gigabit MPC The Juniper Networks MPC4E-3D card family is optimized for two fixed port models—32 10-Gigabit Ethernet ports and two 100-Gigabit Ethernet ports plus eight 10-Gigabit Ethernet ports. Powered by the Junos Trio chipset and with a line rate of up to 260 Gbps, the MPC4E cards are compliant with the 802.3ba standard. The cards are supported on the Juniper Networks MX2020, MX2010, MX960, MX480 and MX240 3D Universal Edge Routers. The MPC4E line cards deliver economical, scalable, highly available, line-rate Ethernet and IP/MPLS edge services.



Slide 80


Modular Port Concentrator (MPC)

� Advanced MX line cards to support the Universal Edge

• Full JUNOS L3 routing and L2 switching technology and Application services

• Support for Provider Edge, ESE and BBE feature set

• In-line, distributed services

� Highly cost-optimized, advanced Ethernet

• Enhanced QoS, performance and scale

• High density GE and 10GE Ethernet

• Roadmap to 100G Ethernet

� Modular Design

• JUNOS Trio Chipset Advanced Silicon

• Up to two modular interface cards per slot

• Software license upgrades (X to R)

Modular Port Concentrator (MPC) Modular Port Concentrators (or MPCs) are advanced MX line cards that support full Junos Layer 3 routing, Layer 2 switching, and application services. The MPC has a modular design which allows up to 2 (Modular Interface Cards) or MICs to be used inside the MPC for flexibility of different types of connections.



Slide 81


Increased Flexibility with Modular Line Cards

� Modular Port Concentrator (MPC)Modular Port Concentrator (MPC)Modular Port Concentrator (MPC)Modular Port Concentrator (MPC)

• Consists of up to 2 MIC slots

• Integrated L2/L3 processing

• Hierarchical QoS, shaping, and rate limiting

• HW support for Synchronous Ethernet

� Modular Interface Card (MIC)Modular Interface Card (MIC)Modular Interface Card (MIC)Modular Interface Card (MIC)

• Up to two pluggable MICs per MPC

• Flexibly mix and match GbE and 10GbE interfaces

• 2x10GbE, 20x1GbE, and 4x10GbE modules (MIC)

Increased Flexibility with Modular Line Cards MPCs consist of up to 2 MICs per slot. A MIC is a Modular Interface Card that allows the ability to mix and match Gigabit Ethernet and 10Gigabit Ethernet interfaces. MICs come in a variety of different module types. MICs can also be placed into certain models of the MX80 for increased port density. 2-port 10-Gigabit Ethernet, 20-port 1-Gigabit Ethernet, and 4-port 10-Gigabit Ethernet are available today.



Slide 82


Three Dense Port Concentrator Types

Three Dense Port Concentrator Types Here you see the new suite of Dense Port Concentrator (DPC) cards for the MX Series enable cost- and performance-optimized Ethernet Services. The DPCs are interchangeable across the MX Series line (MX240, MX480, and MX960) to reduce sparing costs and increase flexibility. They’re available in 40x Gigabit Ethernet and 4x10 Gigabit Ethernet. Switching and routing (DPC-R) The DPC-R card is a mid-range solution that can operate as either a complete Layer 3 router or a purely Layer 2 switch. It delivers flexibility and reduces sparing costs. Scaled-down switching and routing (DPC-X) The DPC-X is a cost-optimized line card designed for Enterprise Ethernet switching and routing. Enhanced Queuing (DPC-Q) The DPC-Q is a high-performance card that supports per-VLAN queuing (up to 64,000 queues per card). It enables providers to deploy business Ethernet services with committed bandwidths and QoS characteristics, thereby increasing their revenue opportunities. It’s ideal for cost-effectively migrating legacy FR/ATM customers.



Slide 83


Non-Ethernet Interfaces on MX

Part No. OC3 OC12 OC48 DS3/E3

MIC-3D-4OC3OC12-1OC48 4 4 1 -

MIC-3D-8OC3OC12-4OC48 8 8 4 -

MIC-3D-8DS3-E3 - - - 8

MIC-3D-4CHOC3-2CHOC12 4 2 - -

MIC-3D-8CHOC3-4CHOC12 8 4 - -

MIC-3D-1CHOC48 - - 1 -

MIC-3D-8CHDS3-E3 - - - 8

All MICs are

interchangeable

across the MX

Series Routers:

Common Sparing

FPC

PICs

Two slots wide

Non-Ethernet Interfaces on MX The MX product family was primarily optimized for Ethernet type interfaces. Because of the way Ethernet is configured on our product lines, we can actually have a large number of 1 Gig or 10 Gig per slot. The MX was not built to carry non-Ethernet interfaces natively. But customers were asking, “Can we start using some of that capability of non-Ethernet interfaces on our box?” So, we introduced these carrier cards, called the MX-FPCs. These MX-FPC carrier cards allow customers to now take advantage of the same PICs—the same physical interface modules that are used on the M and the T Series—on the MX. The important thing to understand here is that each of these carrier cards is actually two slots wide for the MX. So, if you need to add non-Ethernet interfaces on the MX, you utilize two slots on the MX for the carrier card, and then you install two of the PICs (the modules you put into this product in order to have non-Ethernet interfaces). And you have two options: you can use Type 2 or Type 3 PICs. Each Type 2 PIC is 2 ½ Gbps; Type 3 PICs are 10 Gbps. So, for example, if you choose to use two PICs of Type 3 in the MX-FPC, then you are going to be carrying a total of 20 Gigs of total connectivity over one single card—even though, if you’ll recall, those 2 slots on the MX are now capable of 120 Gbps each. So, that’s the reason why they’re not necessarily optimized for non-Ethernet interfaces. But, with a high density box like the MX960, in the event you’re not using all the slots, this allows you to dedicate two of them to your WAN connectivity.



Slide 84


MX Series Multi-Service Interfaces

� Non-Ethernet interfaces• PDH: E1, T1, ChE1, ChT1, DS3, E3, and ChDS3

• SONET/SDH: OC3, OC12, OC48, OC192, ChOC3, ChOC12

• ATM: OC3 and OC12

• Circuit Emulation Services: ChE1, ChT1, ChOC3, and ChOC12

� See the latest documentation for MIC/platform

support

� Low and high port density options• OC3, OC12, OC48, ChOC3, and ChOC12 interfaces

MX Series Multi-Service Interfaces Juniper Networks Multiservice MICs deliver the most widely used multiservice interfaces, including DS3, OC-3, OC-12, OC48, and OC-192. The Multiservice MICs deliver these interfaces on all members of the MX Series family, see the latest documentation for platform support details. These interface options enable the MX Series to address various multiservices scenarios, permitting service delivery with a single versatile platform. The Multiservice MICs extend the latest advancements in traffic management technology, allowing service providers and enterprises to meet their most demanding WAN needs.



Slide 85


MX Architecture

� 2-3 Switch Control Boards (SCBs)

� Non-blocking any-to-any connectivity• ~2x speedup for performance

� SCBs fully redundant• Graceful degradation

� Packet Order maintained• Sequence ID used on ingress

• Reorder buffer re-sequences on egress

� QoS Maintained• Strict Priority queuing on

ingress PFE

• Parallel virtual paths for high and low priority packets

FPC2FPC2FPC2FPC2

4 active logical fabric planes

Every PFE connects to every logical fabric

plane – SF chip

Failover time: comparable to M320/T640: ~1s

MX Architecture An important thing to understand about the architecture of the MX is the fact that you have your DPCs, you have 4 of the ASICs attached to each of the line cards, and that’s what allows you to add a lot of the capacity in the system. One of the things we’ve done on the MX960, which is shown here, is to enable you to have two active SCBs and a third one for redundancy purposes. By introducing the 16-port 10 Gig card and providing 120 Gigs per slot, we’ve activated all 3 switch fabrics that you see in the drawing. Now all three are active at any one time, and that means you now have the ability to carry 120 Gigs of total throughput per line card with the new Trio ASICs. That’s an important point to understand because, while you now do not have a switch fabric for redundancy, your system will just go into an oversubscribed mode if you lose one of those switch fabrics. It will not stop forwarding; it will not drop ports; it will not drop line cards. It’ll just continue to forward on an oversubscribed manner.



Slide 86


MX-FPC Architecture� PICs are hot swappable and support OIR

� Same L3 PFE (ICHIP) and L2 ESE NPU as the DPCs

� FPCs support L2 and L3 forwarding functionality

� PICs handle channelization, L1/L2 framing, and physical layer

MX-FPC Architecture The modular card allows us to introduce the PICs—the non-Ethernet interfaces. We still have the same ASIC architecture—in this case we’re using the I-chip infrastructure for the non-Ethernet interfaces—so, we use the same architecture for Layer 3, Layer 2 ASICs that we have on the DPC—so, the I-chip and the Ethernet service engine—and then we have the connectors that come in for the non-Ethernet PICs (the physical interface connectors), and that’s where you plug in, and that’s what makes it modular to add whatever type of non-Ethernet interfaces you need. You can see in this diagram, two of those FPCs are being used with four particular PICs attached.



Slide 87


DPC Cards Deliver Maximum Performance and System Flexibility

Dense Port Concentrator (DPC) cards for the MX Series enable Dense Port Concentrator (DPC) cards for the MX Series enable Dense Port Concentrator (DPC) cards for the MX Series enable Dense Port Concentrator (DPC) cards for the MX Series enable costcostcostcost---- and performanceand performanceand performanceand performance----optimized Ethernet Services optimized Ethernet Services optimized Ethernet Services optimized Ethernet Services

• Interchangeable across the MX Series line (MX960, MX480, MX240) to reduce sparing costs and increase flexibility

• Available in 40x Gigabit Ethernet and 4x10 Gigabit Ethernet

Switching and routing (DPCSwitching and routing (DPCSwitching and routing (DPCSwitching and routing (DPC----R): R): R): R): • Mid-range solution that can operate as either a complete Layer 3 router or

purely Layer 2 switch • Delivers flexibility and reduces sparing costs

ScaledScaledScaledScaled----down switching and routing (DPCdown switching and routing (DPCdown switching and routing (DPCdown switching and routing (DPC----X): X): X): X): • Cost-optimized line cards designed for Enterprise Ethernet switching and

routing

Enhanced Queuing (DPCEnhanced Queuing (DPCEnhanced Queuing (DPCEnhanced Queuing (DPC----Q) Q) Q) Q) • High-performance card that supports per-VLAN queuing (up to 64,000

queues per card)• Enables providers to deploy business Ethernet services with committed

bandwidths and QoS characteristics, increasing revenue opportunities• Ideal for cost-effectively migrating legacy FR/ATM customers

DPC Cards Deliver Maximum Performance and System Flexibility Here we highlight the current set of cards we offer for the MX. With the current ASIC (the I-chip), we have three different types of cards. The important thing to understand here is that most enterprise customers will focus on either the dash X (–X) or the dash R (–R) cards. The dash Q (–Q) cards are mostly for high end Service Provider Metro Ethernet Carries—especially because they allow you to do a very large number of Q’s—64000 Q’s per card. Most enterprise customers utilize anywhere between 6 and 8 Qs. So, we definitely see the –R and the –X cards for that space. The –X card allows you to have full Layer 2 capabilities and limited scale Layer 3 capabilities. By limited scale, we’re talking about the fact that it can only handle about 32,000 IP addresses, for regular IP, and it does not have a lot of the capabilities of Layer 3 VPNs. But it does have full Ethernet switching and full VPLS capabilities. The –R card has full Layer 2, full Layer 3, full MPLS, and full VPLS capabilities and is a very scalable card.



Slide 88


MX SeriesMX SeriesMX SeriesMX Series M SeriesM SeriesM SeriesM Series

Product PositioningProduct PositioningProduct PositioningProduct Positioning Dense Multiservice Router Multiservice Router

Target DeploymentsTarget DeploymentsTarget DeploymentsTarget Deployments

WAN Gateway, Campus, Aggregation, Core, Data Center Aggregation and

Core

Campus backbone, WAN edge

WAN InterfacesWAN InterfacesWAN InterfacesWAN Interfaces Ethernet, SONET/SDHEthernet, ATM, Frame

Relay, SONET/SDH and TDM ATM

CapacityCapacityCapacityCapacity 20 Gbps to 3.84 Tbps 8.4 Gbps to 320 Gbps

SwitchingSwitchingSwitchingSwitching Yes No

M and MX Positioning

M and MX Positioning Where do we position the MX and the M Series? The positioning obviously becomes more interesting in this environment. If you require a large number of non-Ethernet type interfaces, then the M Series gives you the better capability. If you’re starting to go to only Ethernet type interfaces, the MX product gives you those options. Keep in mind that you also have the capability to put non-Ethernet type interfaces in the MX, but you give up a lot of the performance capabilities that you have per slot compared to the M Series. That’s the primary focus now. The big difference as well is that the MX works as a switch—a Layer 2 switch. The M Series offers mostly Layer 3 type functionality with some basic Layer 2 capabilities. It’s not full blown Layer 2 switching and bridging.



Slide 89


Junos Space Network Application Platform

Junos Space Network Management PlatformJunos Space Network Management PlatformJunos Space Network Management PlatformJunos Space Network Management PlatformDeep EMS with broad FCAPS, provisioning, and extensive automation1111

Junos Space Management ApplicationsJunos Space Management ApplicationsJunos Space Management ApplicationsJunos Space Management ApplicationsPlug-n-play applications to optimize management of specific domains2222

Junos Space SDK and APIsJunos Space SDK and APIsJunos Space SDK and APIsJunos Space SDK and APIsProgrammable interface to customize apps

Third party integration3333

Efficiently Manage the “New Network”Efficiently Manage the “New Network”Efficiently Manage the “New Network”Efficiently Manage the “New Network”

Junos Space Network Application Platform Junos Space is a comprehensive Network Management Solution that simplifies and automates management of Juniper’s switching, routing, and security devices. Junos Space consists of a network management platform for deep element management, plug-n-play management applications for reducing costs and provisioning new services quickly, and a programmable SDK for network customization. With each of these components working cohesively, Junos Space offers a unified network management and orchestration solution to help you more efficiently manage the New Network.



Slide 90


Junos Space Deployment

� Delivered to customers as a fabric

� Embodied in a number of common appliances

(physical and virtual)

� Apps enabled by simple licenses

� Purpose built to host Junos Space

Network Application Platform

� Easy to deploy

� Menu driven

� Hosted on VMware ESX servers

� Other Hypervisors planned

� Identical deployment options as

hardware appliance

JA1500

Content

Director

Service

Insight

Service

Now

Network

Director

Services

Activation

Director

Security

Director

Virtual

Control

Junos Space Deployment The Junos Space platform is available in two form-factors to offer a wide range of deployment options to suit the needs of your organization. The two form-factors are the JA1500 hardware appliance and a Virtual Appliance that can be hosted on VMware ESX servers. The JA1500 appliance is purpose-built to host the Junos Space Network Management Platform and is fine-tuned to ensure high availability and high performance of Junos Space applications. It does not require hardware and operating system configuration expertise to deploy the appliance and also makes initial configuration and deployment quite easy by providing a simple menu-driven console interface. Another advantage of deploying Junos Space hardware appliance is that it simplifies ordering, maintenance, and support of your network by making Juniper Networks the single destination for all your hardware and software requirements for Junos Space, as well as your other networking devices. A Junos Space Virtual Appliance includes the same software and all the functionality available in a Junos Space hardware appliance. However, you must deploy the virtual appliance on a VMware ESX server (version 3.5 or higher) or an ESXI server (version 4.0 or higher). The main driver for choosing Junos Space Virtual Appliances would be that it allows you to utilize any existing investment already made in VMware virtualization infrastructure instead of purchasing new hardware. You can also scale up a Junos Space Virtual Appliance by increasing the resources assigned to it in terms of CPU, memory, and disk space. Extending the breadth of the Junos Space Network Management Platform are multiple Junos Space Management Applications that optimize network management for various domains. These applications, with their easy-to-use interface, enable you to provision new services across thousands of devices and optimize workflow tasks for specific domains, such as core, edge, data center, campus, security, mobile, and more. The applications available for Junos Space today include Virtual Control, Content Director, Service Insight, Service Now, Network Director, Services Activation Director, and Security Director.



Slide 91


Section Summary


•Described Juniper’s MX Series product family

•Identified MX platform components and capabilities

•Discussed positioning of the MX Series

•Described Junos Space


• Described Juniper’s MX Series product family;

• Identified MX platform components and capabilities;

• Discussed positioning of the MX Series; and

• Described Junos Space.



Slide 92



� What is the name of Juniper’s comprehensive

Network Management Solution that simplifies and

automates management of Juniper’s switching,

routing, and security devices?

A) Junos Space

B) Junos Pulse

C) Trio 3D

D) Intelligent Services Edge




Slide 93



� True or false: An MX5, MX10, or MX40 can be

upgraded to an MX80 with a software license.

A) True

B) False




Slide 94


Deployment Scenarios

M and MX Series

Technical Overview

In this last section, we will take a look at some deployment scenarios.



Slide 95


Section Objectives


able to:

•Identify key enterprise applications for Juniper routers

•Discuss any of six sample deployment scenarios

•Describe the Juniper advantage


• Identify key enterprise applications for Juniper routers;

• Discuss any of six sample deployment scenarios; and

• Describe the Juniper advantage.



Slide 96


Key Enterprise Applications for Juniper Routers

Key Enterprise Applications for Juniper Routers We play in all areas of network including regional enterprise backbone, high speed super core interconnecting data centers, large branches and remote campuses.



Slide 97


Sample Deployment Scenarios

DC Transport Super CoreDC Transport Super CoreDC Transport Super CoreDC Transport Super Core

Server Live Mirroring and MigrationServer Live Mirroring and MigrationServer Live Mirroring and MigrationServer Live Mirroring and Migration

NetworkNetworkNetworkNetwork----Wide Virtualization with MPLSWide Virtualization with MPLSWide Virtualization with MPLSWide Virtualization with MPLS

Low Latency MulticastLow Latency MulticastLow Latency MulticastLow Latency Multicast

High Availability High Availability High Availability High Availability

1111

2222

3333

4444

5555

6666

Regulatory ComplianceRegulatory ComplianceRegulatory ComplianceRegulatory Compliance

Sample Deployment Scenarios The sample deployment scenarios we’ll cover are:

• DC Transport Super Core;

• Server Live Mirroring and Migration;

• Network-Wide Virtualization with MPLS;

• Regulatory Compliance;

• Low Latency Multicast; and

• High Availability.



Slide 98


Inter-Data Center Transport Network• Highly Available and Resilient DC Super Core

• Guaranteed Bandwidth allocation for critical application

• More predictable latency characteristics

• Faster failure Detection and re-route recovery (sub 50 msec)

Inter-Data Center Transport Network Deployment Scenario 1: Logical connectivity for a large bank that purchased another large bank. The different colored lines show that each application is allowed to operate as though it has a private network over a cost effective shared infrastructure while maintaining QoS and latency requirements for the applications. In case of a primary path failure (either of the black or orange lines) , the critical application is protected with a secondary/standby LSP (red line) with the same QoS guarantees and latency, going through the 3

rd data center. The challenge is how to cost effectively

connect the data centers of the two banks. Use of SONET is very expensive for connecting DCs across country. The merged organization needs to support many more access nodes and hence scalability and flexibility of the existing infrastructure is of paramount importance. To adhere to regulations, the merged bank needs to maintain traffic segmentation across specific departments while maximizing existing equipment the most effective way. In the proposed new design the expensive SONET links were replaced with a private cloud of Ethernet links that run MPLS. The resulting cloud is called the “Super Core” that is a transport core only and is a strict demark from the existing WAN—there’s no routing interaction. All links are point-to-point Layer 2 VPNs. The traffic engineering component of MPLS guarantees bandwidth and thus offers QoS for the delay sensitive applications. MPLS VPNs provide logical separation of different traffic between the data centers and thereby ensure security and privacy. The highly available and resilient DC Super Core provides:

• Guaranteed bandwidth allocation for critical applications;

• More predictable latency characteristics; and

• Resiliency and availability with faster failure detection and re-route recovery (sub 50 milliseconds).



Slide 99


• Easy management of L2 extended domains across Data Centers

• Can extend VLAN segments across multiple locations

• Data Mirroring, archiving and application standby for DRP

• Server virtualization and virtual machine management across DCs

Server Live Migration Across DCs 2222

Server Live Migration Across DCs A large health care provider in the US requires reliability and rapid access to data and its services must be available around the clock. One way they achieve this availability is through collocation of DCs. Further, the hospital needs to comply with several regulations and requires securing and isolating patient information. For Layer 2 connectivity, the hospital has forty 40 10-Gigabit Ethernet inter-DC links for 40 applications with the utilization of less than 1% on each link. We recommended that the customer move the bandwidth to the MPLS core, and inter-connect with VPLS through the core. With QoS and TE, you can allocate the necessary bandwidth specific to each application. Therefore, the customer was able to have optimal bandwidth utilization and thereby reducing CapEx and OpEx.



Slide 100


Enterprise-Wide Virtualization• Enables logical separation of network services:

• One physical network – As many virtual networks as needed

• Allows for privacy and control across lines of business and/or applications

• Ensures a more optimal utilization of network resources

Enterprise-Wide Virtualization MPLS VPN deployment at the WAN Edge and Core/Aggregation layer provides unique traffic separation capabilities. It enables logical separation of network services: One physical network – as many virtual networks as needed. For example, different organizational units or departments on a single physical companywide network can be segmented to have independent logical networks. It allows for privacy and control across lines of business and/or applications and ensures a more optimal utilization of network resources. In this scenario a very large US governmental agency needed to provide authenticated access to customers, employees, many databases and application servers that host hundreds of applications and web servers that host many web pages for its portals. It was faced with the challenge of how to enforce strict security policies on the use of specific applications to different departments in various locations as well as allowing controlled access to external users. The firewalls had proliferated in order to “separate” applications and enforce policy and the Access Control Lists (ACLs) on the edge routers had become unmanageable – there were hundreds to thousands of ACLs on each router to allow for logical separation by Layer 2 VLANs at the edge. Therefore, enforcement of security policy no longer scaled well and was very costly to implement. Deployment Considerations:

• Scaled and secured support for a large number of applications being used by different locations and departments (security zones);

• Easily enforce security policies for each application and location; and

• Simplify management and reduce TCO. The proposed new design implemented MPLS at the core, where the MPLS WAN “Super Core” separated security zones. Therefore, individual security zones became MPLS Layer 3 VPNs (VRF); MPLS implicitly denies access between security zones and, therefore, there is no need for extensive router ACLs; endpoints are mapped into security zones by Unified Access Control, where policy is enforced by firewall and/or IDP at zone boundaries. Figure 3 depicts how multiple security zones are maintained between different physical locations. For example, only the campus and data center are on the Red Security zone, while the branch office and extended enterprise are prevented from accessing the data/application on the Red Security zone.



In Summary, Network-Wide Virtualization with MPLS:

• Allows separate Layer 3 VPN connectivity across data centers with the supercore network;

• Provides Multipoint Layer 2 VLAN networks across an MPLS Core to different facilities/locations;

• Allows Separation of Layer 3 traffic across the core network for business service/application requirements or for compliance by mapping of VLANs to VRFs to maintain consistent segmentation end-to-end; and

• Provides Circuit Cross Connects (pseudo-wires) by sending Layer 2 services, such as Ethernet, Frame Relay, and ATM, across an MPLS network.



Slide 101


• Transmission Distribution, Power Generation Stations, Consumers all sharing the same infrastructure but are separate virtual networks.

• Results in a Network that meets or exceeds regulatory requirements

Regulatory Compliance

Regulatory Compliance Companies are faced with meeting regulatory compliance mandates for security and data integrity. We already have comprehensive compliance mechanisms through STRM and firewalls that protect the servers. Now we can allow you to extend that segmentation to the network. Customers can allow their branches and partners to communicate with each another easily and yet still comply with security and privacy regulations by using MPLS. With MPLS, you can guarantee reliability, segmentation and privacy and assign specific bandwidth from one site to another across the same physical network infrastructure.



Slide 102


Low Latency Scenario Financial Market Data Distribution

• Multicast Everywhere

• Forwarding Path is fully ASIC based

5555

FinancialsFinancialsFinancialsFinancials----1111DCDCDCDC FinancialsFinancialsFinancialsFinancials----2222

DCDCDCDC

Financials-1 Corp Financials-2 Corp

Exchange-1

PrimaryExchange-1

Redundant

Exchange-2

PrimaryExchange-2

Redundant

Financial

Institution

Dir

ect

Dir

ect

PIMPIMPIMPIM----SMSMSMSM

IGMPv3IGMPv3IGMPv3IGMPv3

P2MP w/ TEP2MP w/ TEP2MP w/ TEP2MP w/ TE

PIM SMPIM SMPIM SMPIM SM

PIMPIMPIMPIM----SSM or PIMSSM or PIMSSM or PIMSSM or PIM----

SMSMSMSM

IGMPv3IGMPv3IGMPv3IGMPv3

P2MP w/ TEP2MP w/ TEP2MP w/ TEP2MP w/ TE

Dir

ect

Dir

ect

Multicast Traffic from

Exchanges to Financial

Institutions

Unicast Traffic from Financial

Institutions back to

Exchanges

• Upper Bounds on Latency “A Must” at Every Stage• Use high performance hardware for near-zero latency• High speed interfaces to reduce transmission latency• Use P2MP to place upper-bounds on latency by pre-

establishing paths

Low Latency Scenario Financial Market Data Distribution Optimized content delivery has become a critical requirement due to the increased level of media-rich traffic on networks. Financial services, news services and stock exchanges have high-touch content that requires low latency, a high level of resiliency and high security. Although native IP multicast can achieve these broadcast requirements, it lacks the security offered by combining MVPN services and a P2MP LSP delivery mechanism. In this scenario, a very large stock exchange needs to broadcast rapid market quotes (with multicast) every few microseconds to financial institutions which in turn use Unicast to communicate back to the exchange. The performance of the trading network is absolutely critical for the success of the Exchange. More than any other business “time is money” in this industry and competitiveness of the market is no longer measured in milliseconds (ms), but in microseconds (µs). Therefore, reducing every microsecond is a competitive advantage for the Exchange. The large network of the organization and large volumes of data create a challenge for scaling traditional multicast technologies. Traditionally for multicast traffic, an ingress router must replicate the traffic on a pseudo-wire to every remote location in the network. As the number of remote locations increases, the traffic in the core for replication also proportionately increases. Therefore, this approach increases bandwidth consumption in the core network, reducing the efficiency. In addition, traditional data center design consists of three layers, i.e., access, aggregation and core. This architecture requires a large number of devices that must be deployed and managed, requiring a larger capital investment, increased and unpredictable latency, more rack space and increased power requirements. Deployment Considerations:

• Provide consistent and ultra-low latency multicast to a large number of end points/financial institutions;

• Any delay or queuing inserted into the trading path must be eliminated; and

• Ensure that high volumes of multicast do not impact the Unicast traffic, as that is the communication that closes the deals.

The proposed new design includes running Point-to-Multipoint (P2MP) Multicast. The Juniper MPLS infrastructure design involved the use of P2MP label switched paths (LSPs), referred to as P2MP-TE multicast. P2MP-TE’s traffic engineering capabilities allow complete path control with resource reservation that guarantees QoS for the LSP from



end to end. P2MP-TE also supports fast reroute, which can deliver high availability with failover times of approximately 50msec for deterministic routing. The slide shows how the Exchange can send out multicast traffic (red lines) to a large number of financial institutions, while the financial institutions can send Unicast traffic back to the exchange (dotted green lines) for closing or making a transaction. P2MP with TE in the core is used to reduce the latency to near zero. The proposed new network design includes:

• High performance, ASIC based MX Series hardware for near-zero latency;

• High speed interfaces to reduce transmission latency;

• Use of P2MP to place upper-bounds on latency by pre-establishing paths; and

• Applying the same QoS policies to Multicast and Unicast packets. In summary, competitiveness in the global financial markets is measured in microseconds. The Exchange’s new trading platform is one of the world's premiere high-performance networks, supporting billions of transactions each day. Juniper's high performance routers with advance routing services will lead to the creation of a robust infrastructure that will deliver a collapsed DC architecture along with P2MP-TE for ultra low-latency multicast traffic with great scale, performance and simplicity.



Slide 103


High Availability

High Availability Our customers are increasingly operating in a 24by7 world, so high availability is critical. Juniper provides this in a number of ways. The software provides such things as graceful switchover, nonstop active routing, in-service software upgrades. There is automatic protection switching (or APS) in our SONET switching circuits. The network itself has system failure protection, and fault transparency to minimize service interruption. Our hardware is hot-swappable, and key components are provided in redundant configurations. And Juniper’s release process is fully tested, and our MTBF times are tracked for continual improvement.



Slide 104


Juniper Advantage

Juniper Advantage The elements that provide the Juniper advantage in high end routing include:

• An advanced silicon and hardware portfolio with Junos the single operating system across all hardware;

• Advanced routing features implemented on the routing platform needed to provide a competitive edge and address the challenges facing enterprises; and

• The two-tiered collapsed architecture that:



• Reduces latency;


• Simplifies management and support.



Slide 105


Section Summary


•Identified key enterprise applications for Juniper routers

•Discussed six sample deployment scenarios

•Described the Juniper advantage


• Identified key enterprise applications for Juniper routers;

• Discussed six sample deployment scenarios; and

• Described the Juniper advantage.



Slide 106



� True or false: MPLS implicitly denies access between

security zones and, therefore, there is no need for

extensive router ACLs.

A) True

B) False




Slide 107


� Juniper Networks provides high availability in which

three of the following ways? (Select three.)


A) Graceful switchover

B) Nonstop active routing

C) In-service software upgrades

D) Manual protection switching




Slide 108


Course Summary

In this course, we:

•Discussed Juniper Networks approach to the high-end

enterprise routing market

•Discussed how Juniper Networks is changing the economics

of networking

•Described Juniper Networks various advanced routing

features

•Identified components and capabilities of the MX Series

platforms

•Identified key enterprise applications for Juniper routers

In this course, we:

•Discussed Juniper Networks approach to the high-end enterprise routing market;

•Discussed how Juniper Networks is changing the economics of networking;

•Described Juniper Networks various advanced routing features;

•Identified components and capabilities of the MX Series platforms; and

•Identified key enterprise applications for Juniper routers.



Slide 109


Additional Resources

� Education Services training classes

•http://www.juniper.net/training/technical_education/

� Juniper Networks Certification Program Web site

•www.juniper.net/certification

� Juniper Networks documentation and white papers

•www.juniper.net/techpubs

� To submit errata or for general questions

•[email protected]

For additional resources or to contact the Juniper Networks eLearning team, click the links on the screen.



Slide 110


Evaluation and Survey

� You have reached the end of this Juniper Networks

eLearning module

� You should now return to your Juniper Learning

Center to take the assessment and the student

survey

•After successfully completing the assessment, you will earn

credits that will be recognized through certificates and non-

monetary rewards

•The survey will allow you to give feedback on

the quality and usefulness of the course

You have reached the end of this Juniper Networks eLearning module. You should now return to your Juniper Learning Center to take the assessment and the student survey. After successfully completing the assessment, you will earn credits that will be recognized through certificates and non-monetary rewards. The survey will allow you to give feedback on the quality and usefulness of the course.



Slide 111


© 2013 Juniper Networks, Inc.

Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and

ScreenOS are registered trademarks of Juniper Networks, Inc. in

the United States and other countries. The Juniper Networks

Logo, the Junos logo, and JunosE are trademarks of Juniper

Networks, Inc. All other trademarks, service marks, registered

trademarks, or registered service marks are the property of their

respective owners. Juniper Networks reserves the right to change,

modify, transfer, or otherwise revise this publication without notice.

Juniper Networks, Inc. All rights reserved. Juniper Networks, the Juniper Networks logo, Junos, NetScreen and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United States and other countries. JunosE is a trademark of Juniper Networks, Inc. All other trademarks, service marks, registered trademarks or registered service marks are the property of their respective owners. Juniper Networks reserves the right to change, modify, transfer or otherwise revise this publication without notice.



Slide 112

CONFIDENTIAL

Corporat e and Sales Headquart ers

Juniper Net works, Inc.

119 4 Nort h Mat hilda Avenue

Sunnyvale, CA 9 40 8 9 USA

Phone: 8 8 8 .JUNIPER

( 8 8 8 .58 6.4737)

or 40 8 .745.20 0 0

Fax: 40 8 .745.210 0

w ww.juniper.net

APAC Headquart ers

Juniper Net works ( Hong Kong)

26/ F, Cit yplaza One

1111 King’s Road

Taikoo Shing, Hong Kong

Phone: 8 52.2332.3636

Fax: 8 52.2574.78 0 3

EMEA Headquart ers

Juniper Net works Ireland

Airside Business Park

Swords, Count y Dubl in, Ireland

Phone: 35.31.8 9 0 3.6 0 0

EMEA Sales: 0 0 8 0 0 .458 6.4737

Fax: 35.31.8 9 0 3.6 0 1

Copyright 20 10 Juniper Net works, Inc.

Al l right s reserved. Juniper Net works,

t he Juniper Net works logo, Junos,

Net Screen, and ScreenOS are regist ered

t radem arks of Juniper Net works, Inc. in

t he Unit ed St at es and ot her count ries.

Al l ot her t radem arks, service m arks,

regist ered m arks, or regist ered service

m arks are t he propert y of t heir

respect ive ow ners. Juniper Net works

assum es no responsib il it y for any

inaccuracies in t his docum ent . Juniper

Net works reserves t he right t o change,

m odif y, t ransfer, or ot herw ise revise t his

publ icat ion w it hout not ice.

ed u cat io n serv ices co ursew are

Documents

SSMMX01D