MX Series Technical Overview

education services courseware

MX Series Technical Overview

Student Guide


Course SSMMX01C 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 2

2011 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 3

2011 Juniper Networks, Inc. All rights reserved. www.juniper.net | 3CONFIDENTIAL SSMMX01C

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 4


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, and

Identify key enterprise applications for Juniper routers

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, and Identify key enterprise applications for Juniper routers



Slide 5


Agenda: MX Series Technical Overview

About Juniper Networks

Challenges in the Enterprise

Advanced Routing Hardware and Software

Enterprise Product Portfolio

Deployment Scenarios

Agenda: MX Series Technical Overview This course consists of 5 sections. The 5 main sections are provided in sequential order and are titled as follows: About Juniper Challenges in the Enterprise Advanced Routing Hardware and Software Enterprise Product Portfolio, and Deployment Scenarios



Slide 6


About Juniper Networks

MX Series

Technical Overview

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



Slide 7


Section Objectives

After successfully completing this section, you will be

able to:

Discuss Junipers approach to the high-end enterprise

routing market

State the rate at which Juniper is increasing its market

share

Section Objectives After successfully completing this section, you will be able to: Discuss Junipers approach to the high-end enterprise routing market, and State the rate at which Juniper is increasing its market share



Slide 8


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 9


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 Junipers mission and strategy to deliver on something we set out to do two or three 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 10


High End Enterprise Routing Data

Juniper is #2 with 48% market share in enterprise high end routing

Juniper has been gaining market share rapidly Gained 19.1% YoY, 6.3% QoQ

Cisco losing market share Lost 20.3% YoY, 8.3% QoQ

High End Enterprise Routing Data by Synergy High End Enterprise Routing is a growing market, and Juniper is leading the way. Synergy Research Group found that Cisco has been losing market share to Juniper. This slide shows the past few years, where Juniper moved from one-third to nearly one-half of the market for this important market segment. As you can see, Juniper has gained 19.1 percent, year over year, while Cisco has been losing share by 20% year over year. Juniper has a very strong story, and many of our premier customers have participated in our Advanced Routing Seminars, describing how they have deployed our solutions in their environments.



Slide 11


MX: A Resounding Success

Over $1.5 B in shipmentsOver $1.5 B in shipmentsOver $1.5 B in shipmentsOver $1.5 B in shipments

Over 1000 customersOver 1000 customersOver 1000 customersOver 1000 customers

Over 12,500 chassis and 40,000 line cards deployedOver 12,500 chassis and 40,000 line cards deployedOver 12,500 chassis and 40,000 line cards deployedOver 12,500 chassis and 40,000 line cards deployed

Densest Carrier Class Router in the industry (3.84T)Densest Carrier Class Router in the industry (3.84T)Densest Carrier Class Router in the industry (3.84T)Densest Carrier Class Router in the industry (3.84T)

Q2 2007 Q4 2007 Q2 2008Q4 2008Q2 2009Q4 2009 Q2 2010

MX: A Resounding Success One of the reasons for Junipers gains in the router market is the MX platform. As this slide illustrates, since its introduction it has been a resounding success with customers with over 12,500 chassis and 40,000 line cards deployed.



Slide 12


Section Summary

After successfully completing this section, we:

Discussed Junipers approach to the high-end enterprise

routing market

Stated the rate at which Juniper is increasing its market

share

Section Summary After successfully completing this section, we: Discussed Junipers approach to the high-end enterprise routing market, and Stated the rate at which Juniper is increasing its market share



Slide 13


True or false: In the past few years, Juniper Networks has moved from having one-third to nearly one-half of the high-end enterprise routing market.

Learning Activity 1: Question 1

A) True

B) False

Learning Activity 1: Question 1 True or false: In the past few years, Juniper Networks has moved from having one-third to nearly one-half of the high-end enterprise routing market.



Slide 14


Challenges in the Enterprise

MX Series

Technical Overview

Now well take a look at the Challenges in the Enterprise



Slide 15


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

Section Objectives After successfully completing this section, you will be 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, and Discuss how Juniper is changing the economics of networking



Slide 16


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 17


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 as they have to connect billions of users and devices, and thousands of super data centers, and support any communication application. Youve 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: The users and businesses are now global. Requirement is not only to be reliable but 100% available because IT departments need to provide around the sun service. For example people who work in Americas need access to servers in APAC and vice versa. Security and Compliance: Everybody has heard of denial of service 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 18


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 19


Experience versus Economics

The eternal challenge

Experience versus Economics While there is a demand to improve experience, there are pressures to reduce costs and TCO.



Slide 20


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

Business Transformation Juniper is changing the economics of networking by reducing TCO, Increasing ROI and accelerating profitability. We will show you this in detail.



Slide 21


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

Section Summary After successfully completing this section, we: 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 22


For an enterprise to be competitive today, its network must be which three of the following?


A) Fast

B) Reliable

C) Complex

D) Secure

Learning Activity 2: Question 1 For an enterprise to be competitive today, its network must be which three of the following?



Slide 23



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

Learning Activity 2: Question 2 Juniper is changing the economics of networking by reducing what, increasing what, and accelerating what?



Slide 24


Advanced Routing

Hardware and Software

MX Series

Technical Overview

Next up, well take a look at Junipers Advanced Routing Hardware and Software



Slide 25


Section Objectives


able to:

Describe the elements that provide the Juniper advantage in

high end routing

Explain how Junos reduces complexity and provides the

Power of One

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 Junipers various advanced routing features

Section Objectives After successfully completing this section, you will be able to: Describe the elements that provide the Juniper advantage in high end routing Explain how Junos reduces complexity and provides the Power of One 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 Junipers various advanced routing features



Slide 26


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, 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.



Junos 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. Junos software is fundamentally different in not only its architectural design, but also in its development. We summarize the real differences of Junos in 3 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 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: Junos has experienced tremendous market success, capturing a significant portion of its available market in just 10 years, serving the most demanding customers in the world, including: Top 40+ service providers 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 the architecture Requires fewer devices Reduces space, power, and cooling requirements, and Simplifies management and support with a single network OS



Slide 27


Junos Software: The Power of One Simplify Operations and Reduce Network Complexity

Junos Software: The Power of One Junos ties together Junipers 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 28


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 Apps

User/Application SCALEUser/Application SCALEUser/Application SCALEUser/Application SCALE

Junos Trio Chipset Uncompromised 3D Scaling At the core of the success of Junipers routing and switching platforms are 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 customers expectations. Subscribers: Scale to support the growing subscriber base for the service providers.



Slide 29


Another Example of Savings with Juniper

Another Example of Savings with Juniper Here is another example of savings with Juniper. Juniper is the provider of the worlds 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 is designed to offer a very efficient power and thermal system. With 16x10GbE line cards, power draw is as low as 37Watts per 10GbE, creating up to 1.7x more power efficiency per 10GbE compared to similar competitive line cards.



Slide 30


Savings with MX960 versus Cisco ASR 9010

* $.30/Kilowatts/hr

** Assumes 24x7 usage

Savings with MX960 versus Cisco ASR 9010 This chart shows a comparison between the Juniper MX960 and Ciscos ASR 9010. On every dimension you see the superiority of the MX capacity, ports, ports per chassis all provide greater value to the customer. Note that the Cisco literature claims 6.4 Tbps, but we are only seeing 1.28 Tbps in the units being shipped. This chart also shows that this capacity is delivered with a smaller energy footprint. Assuming 24 by 7 usage, the Juniper energy costs are dramatically less.



Slide 31


Need for Advanced Routing per Jim Metzler

Metzler ArticleMetzler ArticleMetzler ArticleMetzler Article

Advanced Platform FeaturesAdvanced Platform FeaturesAdvanced Platform FeaturesAdvanced Platform FeaturesBusiness DriversBusiness DriversBusiness DriversBusiness Drivers

Need for Advanced Routing per Jim Metzler 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 Junipers advanced routing capabilities addressing these business drivers. Business drivers we hear from our customers are: Carrier class reliability which means fully redundant hardware and a comprehensive set of software features, such as Fast Re-Route (FRR), Non Stop Routing (NSR), In-service Software Upgrade (ISSU), Bi-Directional Forwarding (BFD). The hardware/software combination must be able to detect failures in sub-second time.



Slide 32


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 Were now going to focus on these six advanced routing features: A Single Operating System Junos Collapsed Data Center Design Network Virtualization enabled by MPLS Carrier Class Reliability Rich QoS Features and Low Latency Multicast



Slide 33


Junos Reduces Network ComplexitySingle Operating System

One operating system across all platforms One release train providing stable delivery of new

features Accelerate advance services and Application

deployment Centralized NSM to manage the entire life-cycle of

ALL network devices

1111

SimpleSimpleSimpleSimple

PredictablePredictablePredictablePredictable

ReliableReliableReliableReliable

Paralyzing complexity

Consumes operational time

Increases risk of downtime

Unpredictable performance

A pacing factor to business innovation and speed

Junos Reduces Network Complexity Single Operating System 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 often requires a dedicated staff Theres 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 the possible variations of operating systems Theyre a pacing factor to business innovation and speed. Obviously, all these issues make it difficult to adapt to new opportunities as the business grows and changes.

This is where Junos comes in! Running a single operating system across devices makes the day-to-day operation of the network less complex. The IT staff can focus on rolling out new deployments and maintaining the network, making better use of their time and effort. With a steady release of new features and a modular architecture they have predictable performance and the ability to streamline their tasks through automation. This provides a consistent user experience for the IT staff and lower costs for the customer.



Slide 34


HighHighHighHighLatencyLatencyLatencyLatency

Overly Overly Overly Overly ComplexComplexComplexComplex

Legacy DC Architecture Layers of Switches2222

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 35


Junipers Value: Simplification Collapsing Core and Aggregation Layers

L2/L3L2/L3L2/L3L2/L3SwitchSwitchSwitchSwitch

L2/L3 L2/L3 L2/L3 L2/L3 SwitchSwitchSwitchSwitch

L2/L3L2/L3L2/L3L2/L3SwitchSwitchSwitchSwitch

L2/L3 L2/L3 L2/L3 L2/L3 SwitchSwitchSwitchSwitch

EX4200EX4200EX4200EX4200

SRX5800SRX5800SRX5800SRX5800

MX SeriesMX SeriesMX SeriesMX Series Enterprise Services Edge:Enterprise Services Edge:Enterprise Services Edge:Enterprise Services Edge:

Application Segmentation Application Segmentation Application Segmentation Application Segmentation ---- L3 VPNL3 VPNL3 VPNL3 VPN

VLAN extensions VLAN extensions VLAN extensions VLAN extensions VPLSVPLSVPLSVPLS

TDM replacements over IP WANTDM replacements over IP WANTDM replacements over IP WANTDM replacements over IP WAN

Regulatory complianceRegulatory complianceRegulatory complianceRegulatory compliance

MX SeriesMX SeriesMX SeriesMX 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

Junipers Value: Simplification Collapsing Core and Aggregation Layers Junipers 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) Reduces space, power, and cooling requirements, and 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 youre allowing the traffic to flow. You start having more predictable performance from a QoS perspective.



Slide 36


Key Advanced Routing FeaturesMPLS 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 growth

Seamless NetworkSeamless NetworkSeamless NetworkSeamless NetworkConnectivityConnectivityConnectivityConnectivity

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 37


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

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 Re-route capabilities and BFD

VLAN ComponentsVLAN ComponentsVLAN ComponentsVLAN Components MPLS ComponentsMPLS ComponentsMPLS ComponentsMPLS Components

Extending VLAN Knowledge to MPLS These are just some of the similarities between architectural components. Its 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 peoples concerns due to perceived complexity. Actually, most Enterprise deployments dont require all knobs and capabilities. Theres 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 dont 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 dont get.



Slide 38


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 39


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 VRFs 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 40


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 Re-route (FRR)

Non-Stop 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 Lets now consider the key advanced routing features. Hardware: Hardware: Hardware: 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:Software:Software: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 dont 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. Junipers 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 41


MX: 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: Reliable Hardware The MX 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 42


Graceful RE Switchover (GRES)

Graceful RE Switchover (GRES) Graceful Routing Engine 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 43


Nonstop Active Routing (NSR)4c4c4c4c

Nonstop Active Routing (NSR) Nonstop Active Routing, NSR In order to have 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, all the protocols across the routing engines there is no latency when youre going from one routing engine to another routing engine. While Cisco claims ISSU they do not have the ability to maintain state.



Slide 44


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

In-service migration of one Junos release to another

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

Upgrade path available from any release to another

Minimizes upgrade time and risk

Automates operations functions to plan and implement upgrade

No disruption of control plane and minimal disruption of traffic

NSR and GRES are prerequisites

10.x10.x10.x10.x 11.y11.y11.y11.y

Avoids drawbacks

in piecemeal system update

Unified In-service Software Upgrade (ISSU) GRES and NSR are prerequisite to In-Service Software Upgrade (ISSU). ISSU allows you to go from one Junos version to another without having to restart obtaining the state information from your neighbors. Lets 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 theres a need to fall back, from a routing perspective. Once youre 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 theres a failure of the primary routing engine. Cisco doesnt 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. Were the first to do this.



Slide 45


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 ExtendedACLS, 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. We have a standard eight Hardware queues with an option for 1000+ hardware queues with consistency across all traffic types. 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 46


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 4 colors (using PLP) Soft policers

Drop Hard policers

Single Rate Three-Color Policers: Mark one of 2 colors based on 2 bandwidth buckets and one rate

Two Rate Three-Color Policer: Mark one of 2 colors based on 2 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 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 47


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

5 Priority levels

Strict High-Lowest Latency, Medium

High, 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 queues 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) 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 48


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 queues 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 ports 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 platforms buffer management is called Memory Allocation Dynamic or 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 ports 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 49


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 packets CoS treatment pertain to the current-hop router. The motivation of packet rewrite is to efficiently convey a packets 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 packets 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 protocols 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 50


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 51


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 a 1000 destination, 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: Here are the details: Here are the details: 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 52


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 theyre 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 53


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 its 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, its 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, thats where you could have a difference in latency. That covers the basics of multicast especially in the context of low latency.



Slide 54


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. Well 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 55


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 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 GbE. If you start with the arrow from the source, there is a 10 GbE feed coming in to 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 56


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 JunosIGMP v1,2,3

MX960: 10Gbps 176 10Gbps port MX480: 10Gbps 96 10Gbps port MX240: 10Gbps 48 10Gbps port

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

P2MP with Traffic Engineering (TE)MSDPIPv6 Multicast

MLDv1,3 Equivalent of IGMP PIM-SM same as in IPv4r

Low Latency Multicast MX Series Optimized Hardware, Feature Rich Software The MX provides ASIC-based forwarding and replication in order to reduce latency. Were replicating multicast traffic at line rate on every port. Thats from any port to any port and this is line rate bi-directionally, i.e. a 10G 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 GbE it can replicate to all other 132 other 10 GbE ports at line rate (this includes the 16 port 10GE Card). In addition Junos offers a rich set of multicast features including: IGMP, P2MP with traffic engineering and IPv6 Multicast



Slide 57


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 centre 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. Lets say we have the data centre 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, lets 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 58


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, P4, and P5. 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 59


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, lets 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 M2PM 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 thats already built into the system, you have scalable state maintenance. The node along the network really you need not understand the full multicast, but only you need to understand point-to-multipoint.



Slide 60


Resiliency with P2MP

Resiliency with P2MP There are a lot of advantages in using point-to-multipoint; well look at specific examples as well. Also, from a resiliency standpoint, you can specifically designate so, on this particular diagram, you can actually have a primary path from PE1 to PE5, take the intermediate points P1 and P3, and you can also have a backup path that takes PE1, P1, P2, P3 and PE5, so that if the link between P1 and P3 goes down the red arrow then you automatically switch over to the green arrow. With MPLS on an Ethernet link you will be able to achieve 50 millisecond payload characteristics if you use point-to-multipoint.



Slide 61


Section Summary


Described the elements that provide the Juniper advantage

in high end routing

Explained how Junos reduces complexity and provides the

Power of One

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 Junipers various advanced routing features

Section Summary After successfully completing this section, you should now be able to:

Described the elements that provide the Juniper advantage in high end routing Explained how Junos reduces complexity and provides the Power of One 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 Junipers various advanced routing features



Slide 62



Which three of the following describe the Junos 1-1-1 differentiation?

A) One Tbps rate

B) One operating system

C) One software release

D) One modular architecture

Learning Activity 3: Question 1 Which three of the following describe the Junos 1-1-1 differentiation?



Slide 63



Juniper Networks enables you to build a highly virtualized data center network that which of the following? (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

Learning Activity 3: Question 2 Juniper Networks enables you to build a highly virtualized data center network that which of the following? (Select all that apply.)



Slide 64



In which two of the following ways does Juniper Networks reduce network complexity?

A) Single operating system across all hardware

B) Collapsed architecture

C) Carrier-class reliability

D) Scalability

Learning Activity 3: Question 3 In which two of the following ways does Juniper Networks reduce network complexity?



Slide 65



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

Learning Activity 3: Question 4 Which of the following are key advanced routing feature offered by Juniper? (Select all that apply.)



Slide 66



True or false: To have ISSU capabilities, you need not only GRES, but you must also maintain all the state across the routing engines.

A) True

B) False

Learning Activity 3: Question 5 True or false: To have ISSU capabilities, you need not only GRES, but you must also maintain all the stat

Documents

MX Series Technical Overview