7/26/2019 Juniper Vmx i.lysogor
1/38
Juniper SP ProductsUpdate
Ivan Lysogor
4thSeptember 2015
7/26/2019 Juniper Vmx i.lysogor
2/38
Opera
Comp
Margin
pressure
Long Lead
Times
MARKET & CHALLENGES
Successful business requires
Velocity - Agility - Continuity
7/26/2019 Juniper Vmx i.lysogor
3/38
FULL PORTFOLIO COVERAGECPE
ACCESS
PRE-AGGREGA
AGGREGATION
CORE NETWO
EPC
Solution re
Solution c
- Port
- Main
- Upg
Reliability
New serv
HOMEHOME
PTX
ACX
MX
ACX
PTX
ACX
MX
ACX
PTX
ACX
MX
ACX
PTX
ACX
MX
ACX
PTX
ACX
MX
ACX
BackbonePTX
PTXPTX
MX
MX
MX
MX
MX
MX
BRANCH
MOBILE
HOME
Metro
Metro
Metro
Metro
Metro
PTX
HQ
MOBILE
BRANCH
MOBILE
HOME
HQ
MOBILE
HQ
MOBILE
NorthStarController
ContrailController
7/26/2019 Juniper Vmx i.lysogor
4/38
ROUTING PORTFOLIOFortify the portfolio, help SP customers address transforming their business
Ubiquitous Access
Mature SW for access: L2,OAM
ACX500 on time for SCBH ACX5K addresses Wireline
& Converged access,
Full features for A&Amarket
Small Backhaul, MobileBackhaul,Wireline/Convergedbackhaul
SAD2.0 + CPP for
operation + Migration
Universal Edge
Continuous leadership:new HW, SW, Userexperience to maintainscale, capacity and featuredifferentiation
Full L2/L3 flavors
Advance services (SCG)and pathway to NFV
Relevance to Cloud: USG
New use casedevelopment
Seamless virtual
experience
Massive Core
Build from position ofstrength to address LeanCore with LSR as well asfull IP Core with Qos &Services
Leapfrog in term ofcapacity
Pragmatic approach toIntegrated Packet Optical
RejL
Embe
Mod64 bmod
VirtvBN
Platfo
Nor
NFVNFV
SAD
ACX MX PTX S
7/26/2019 Juniper Vmx i.lysogor
5/38
MX Product Update
7/26/2019 Juniper Vmx i.lysogor
6/38
MX Portfolio Overview
One TRIO ArchitectureOne UNIVERSAL EDGE
MX 240
520 Gbps
MX 480
1560 Gbps
MX 960
2860 Gbps
MX 2010
4800 Gbps
MX 104
80 Gbps
* Current full duplex capacity is shown
N x 10Gbps
VMX
7/26/2019 Juniper Vmx i.lysogor
7/38
MPC5E
MPC5E 24 x 10GE or 6 x 40GE
Applications and Scale
Description
240 Gbps line card with flexible 10GE/40GE interface
configuration options, increased scale and OTN support
Interface combinations:
24 x 10GE (MIC0 and MIC1)
6 x 40GE (MIC2 and MIC3)
12 x 10GE and 3 x 40GE (MIC0 and MIC3)
12 x 10GE and 3 x 40GE (MIC1 and MIC2)
Port queues with optional 32K queues upgrade license
1M queues option
Interface Features
Up to 10M IP Routes (in hardware)
Full scale L3VPN and VPLS
Increased Inline IPFIX Scale
MIC0/1
MIC2
MIC3QSFPQSFP
QSFP
QSFP
QSFP
QSFP
7/26/2019 Juniper Vmx i.lysogor
8/38
MPC5E
MPC5E 2 x 100 GE and 4 x 10GE
Applications and Scale
Description
240 Gbps line card with providing 100GE and 10GE
connectivity, increased scale and OTN support
Interfaces:
4 x 10GE SFP+
2 x 100GE CFP2
Port queues with optional 32K queues upgrade license
1M queues option
Interface Features
Up to 10M IP Routes (in hardware)
Full scale L3VPN and VPLS
Increased Inline IPFIX Scale
MIC0
MIC2
MIC1
MIC3
CFP2
CFP2
7/26/2019 Juniper Vmx i.lysogor
9/38
MPC6E Overview
Applications and Scale
Description
480 (520) Gbps modular line card for MX2K platform,
increased scale and performance
Interface cards supported:
2x100G CFP2 w/ OTN (OTU4)
4x100G CXP
24x10G SFP+
24x10GSFP+ w/ OTN (OTU2)
Port based queueing
Limited scale per-vlan queueing
Interface Features
Up to 10M IP Routes
Full scale L3VPN and VPLS
Increased Inline IPFIX Scale
MPC6E
MIC0
MIC1
X
X
X
X
7/26/2019 Juniper Vmx i.lysogor
10/38
Routing system upgrade scenario
Highlights
Protects investments into ha Reduces software qualificat
No JUNOS upgrade require
installation is in service
8 x SFB
800 Gbps per slot
Future Router
MPC6 installed,
480Gbps per slot
With Continuity
Support
New higher density
MPCs added
Driver package
installed
May upgrade to
new fabric or may
use the same
Happy network enginee
something else (probab
7/26/2019 Juniper Vmx i.lysogor
11/38
Software
7/26/2019 Juniper Vmx i.lysogor
12/38
MX Data Center Gateway
DC Gateway
Internet
EVPN
13.2R1 First Implementation (MPLS encaps)
14.1R2 VM Mobility Support
14.1R4 Active / Active Support
14.1R4 VXLAN encapsulation
VXLAN
14.1R4 VMWare NSX Inte
7/26/2019 Juniper Vmx i.lysogor
13/38
EVPN Advantages
DC Fabric DC Gateway DDC Gateway
Link Efficiency
All Active forwarding with
built-in L2 LoopPrevention
Convergence
Leading high availability,
convergence, fast reroutecapabilities
L3 and L2
L2 & L3 Layers Tie-In
Built-in the protocol
Opt
Ingress a
Mobility
MPLS / IP
Virtual Machine Mobility
7/26/2019 Juniper Vmx i.lysogor
14/38
Virtualization strategy and goals
7/26/2019 Juniper Vmx i.lysogor
15/38
The high-level objectives of NFVare:
Rapid service innovationthrough software-based deployment and operationalization of network functions
services.
Greater flexibility in assigning VNFs to hardware.
Improved capital efficiencies compared with dedicated hardware implementations
Substantial saving may be possible by moving routing functionality from purpose-built routers to equivalen
implemented in COTS hardware environments providing cloud computing capabilities such as the NFVI.
These Enterprise network functions include:
1)AR - Enterprise Access Router / Enterprise CPE
2)PE - Provider Edge Router
3) FW
Provider Edge (PE) routers run out of control plane resources before they run out of data plane resources
control plane functions improves scalability.
It is estimated that a large number of Virtualised devices need to be supported at the edge, requiring enorm
resources from the NFVI. The vPE should be able to independently scale on the data plane and control plane
forwarding tables and a very large number of flows
ETSI G
CE &PE are being considered for virtualization, just as DPI
Control plane scale is a concern, and it needs to scale indep
Service agility
Flexibility to assign VNF/services to
hardware, improve capital efficiency
What is on the mind of SPs
7/26/2019 Juniper Vmx i.lysogor
16/38
Physical vs. Virtual
Physical Virtual
High throughput, high density Flexibility to reach higher scale in coservice plane
Guarantee of SLA Agile, quick to start
Low powerconsumption per throughput Low power consumption per contro
Scale up Scale out
Higher entry cost in $ and longer time to deploy Lower entry cost in $ and shorter tim
Distributed or centralized model Optimal in centralized cloud-centric
Well development network mgmt system, OSS/BSS Same platform mgmt as Physical, plu
mgmt as a SW on server in the cloud
Variety of network interfaces for flexibility Cloud centric, Ethernet-only
Excellent price per throughput ratio Ability to apply pay as you grow m
Each option has its own strengt
created with different fo
7/26/2019 Juniper Vmx i.lysogor
17/38
Type of deployments with virtual platform
Traditionalfunction, 1:1
formreplacement
New applicationswhere physical is
not feasible or ideal
A whole newapproach toa traditional
concept
Cloud CPE
Cloud based VPN
ServiceChaining GW
Virtual Private Cloud GWMulti-function, multi-layer integrat
w/ routing as a plug-in
SDN
Route Reflector
Servic
Lab & POC
Branch Router
DC GW
CPE
PE
Wire
Mo
7/26/2019 Juniper Vmx i.lysogor
18/38
vMX introduction
7/26/2019 Juniper Vmx i.lysogor
19/38
What is vMX
vMX is the virtualized Juniper MX platform with complete contr
forwarding and management plane
Leverage development effort and JunOS feature velocity on the and is presented in the virtualized software format
Aiming for complete feature parity with physical MX, and align wsoftware release development timeline
In line with general trend of virtualization and enable cloud basedeployment
7/26/2019 Juniper Vmx i.lysogor
20/38
VMX overview
Efficient separation of control and data-plane
Data packets are switched within vTRIO Multi-threaded SMP implementation allows core elasticity
Only control packets forwarded to JUNOS
Feature parity with JUNOS (CLI, interface model, service configuration)
NIC interfaces (eth0) are mapped to JUNOS interfaces (ge-0/0/0)
Guest OS (Linux) Guest OS (JUNOS)
Hypervisor
x86 Hardware
CHASS
ISD
RPDLC-
Kern
el
DCD
SNM
PvTRIO
VFP VCP
TCP
7/26/2019 Juniper Vmx i.lysogor
21/38
Key Benefit of vMX
Exact same controlplane features ofJUNOS & forwardingfeature set of Trio, andmanaged same way asphysical router
Same release timelineas the JunOS releases
ConsistencyQuick serviceenablement byleveragingvirtualizationtechnology
Service separationwith different routers
Agility
Ef
Pcs
Scalability
7/26/2019 Juniper Vmx i.lysogor
22/38
vMX Use Cases
7/26/2019 Juniper Vmx i.lysogor
23/38
General consideration of vMX deploymen
vMX behaves the same way as the physical MX, so it is capable of being t
or virtual PE, virtual BNG, (*note-1)
Great option as labequipment for general qualification or function valida
In cloud or NFV deployment, when virtualization is the preferred technol
Fast service enablement without overhead of installing new HW
Solution for scaling services when control plane scale is the bottleneck
When network functions are centralized in DC or cloud When service separation is preferred by deploying different routing platf
Note-1: Please see product feature & Perf detail in later slides, also see other comments for where vMX is mo
7/26/2019 Juniper Vmx i.lysogor
24/38
Service agility with virtualized technology
New service introduction takes time
Qualifying on the existing infra Validate new JunOS release
New service may destabilizing current service and delay the introduction
vMX can be a quick way to validate new a service:
No need to disturb current services, simple enable service on the vMX in current infra
Validate a specific JunOS only for the new service
Lower CAPEX to start a new service trial
vMX behaves the same way as the MX, easy for service planning, migration & integration
If the service fails, no significant impact to network operation and CAPEX investment
If service is successful
Either scale out the service with vMX if the traffic profile permits,
Or integrate this new service to the existing MX or new MX physical chassis
7/26/2019 Juniper Vmx i.lysogor
25/38
Agility example: Bring up a new service in
SP Network for VPN
service
PE
L3 CPE
PE
POP
1. Install a new vMX to
start offering a new
service without
impact to existing
platformvMX
2. Scale out the service with vMX traffic profile fits the requireme
vMX 3. Add service directly to theGW or add more physical successful and there is mosignificant traffic growth
MX
4. Integrated the new service into existing PEwhen the service is mature
7/26/2019 Juniper Vmx i.lysogor
26/38
Proof of concept lab validation or SW cert
CAPEX or OPEX reduction for lab validation or network POC
7/26/2019 Juniper Vmx i.lysogor
27/38
vCPE solution with vMX as the SDN Gate
SP Network for VPN
service
L3 CPE
VPN-starbucks-LA
L3 CPE
L3 CPE
vMX as SDN GW router
providing support for BGP
and overlay tunnelingprotocols
vMX also address the VRF
scaling issue for L3 service
chaining
PE
PEPE
L3 CPE
vCPE service
Virtualized services foaccess to internet or aFirewall, DPI, caching
DC GW
PE
VPN-starbucks-LA
VPN-
starbucks-core
VPN-
starbucks-core
VPN-
starbucks-NY
VPN-
starbucks-
Hawaii
VPN-starbucks-NY
Service-chain-X1 Service-chain-Y1
VPN-starbucks-LA
VPN-starbucks-core
LA
LasVegas
Honolulu
Chicago
DCDC
DC
SDN GWSDN GW
7/26/2019 Juniper Vmx i.lysogor
28/38
Virtual Route Reflector
vMX can be used as Route Reflector and deployed the same way as the physical RR in
vMX can act as both vRR or any typical router function with forwarding capability
Client 1
Client 2
Client 3
Client n
Virtual RR on VMs
On standard serversVirtual RR
7/26/2019 Juniper Vmx i.lysogor
29/38
Virtual BNG cluster in a data center
BNG cluster
10K~100K subscribers
Data Center or CO
vMX as vBNG
vMX vMX vMX vMX vMX
Potentially BNG function can be virtualized, and vMX can help form a BNG cluster at the DC or CO (Roadmap item
Suitable to perform heavy load BNG control-plane work while there is little BW needed;
Pay-as-you-grow model;
Rapid Deployment of new BNG router when needed;
Scale-out works well due to S-MPLS architecture, leverages Inter-Domain L2VPN, L3VPN, VPLS;
7/26/2019 Juniper Vmx i.lysogor
30/38
vMX Product Details
7/26/2019 Juniper Vmx i.lysogor
31/38
vMX Components
Virtual JUNOS to be hosted on a VM Follows standard JUNOS release cycles
Additional software licenses for different control p
applications such Virtual Route Reflector
VM that runs the packet forwading engine that ismodeled after Trio ASIC
Can be hosted on a VM (offer at FRS) OR run as a
Linux container (bare-metal) in the future
VCP
(Virtualized Control Plane)
VFP(Virtualized Forwarding Plane)
7/26/2019 Juniper Vmx i.lysogor
32/38
VMX system architecture
Optimized data path from physical NIC to
vNIC via SR-IOV (Single Root IOVirtualization).
vSwitch for VFP to VCP communication(internal host path)
OpenStack (Icehouse) for VM management(Nova) and provisioning of infrastructurenetwork connections (Neutron)
VCPVFP
Physical NICs
Virtual NICs
Guest VM (Linux + DPDK) Guest VM
Hypervisor
Cores Memo
vSwitchSR-IOV
Physical layer
7/26/2019 Juniper Vmx i.lysogor
33/38
Packet Flow
Physical NICs
Virtual NICs
vSwitch
eth0
fxp0
VCP
VFP
DCDRPD
Kernel
Microkernel
vTrio
Intel DPDKOp
fro
SR-IO V
OpenS
manag
provisnetwo
vSwitch forcommunication
(internal host path)
7/26/2019 Juniper Vmx i.lysogor
34/38
Product Offering at FRS
7/26/2019 Juniper Vmx i.lysogor
35/38
FRS Product Offering
FRS at Q2 2015 with JUNOS release 14.1R4
Function: Provide feature parity with MX except function related to HA and QOS
Performance: SR-IOV w/ PCI pass-through, along with DPDK integration
Hypervisor support: KVM
VM Implementation: VFP to VCP 1:1 mapping
OpenStack integration (to be finalized)
VFP VCP
Hypervisor/Linux
NIC drivers, DPDK
Server, CPU, NIC
Juniper deliverable
Customer defined
7/26/2019 Juniper Vmx i.lysogor
36/38
Reference server configuration
CPU Intel Xeon 3.1GHz
Cores Minimum 10 cores
RAM 20GB
OS Ubuntu 14.04 LTS (w/ libvirt 1.2.2, for better performance, upg
1.2.6)
Kernel: Linux 3.13.0-32-generic
Libvert: 1.2.6
NICs Intel 82599EB (for 10G)
QEMU-KVM Version 2.0
Note: Initially requires minimum 10 Cores: 1 for RE VM, 7 for PFE VM which include 4 packetprocessing cores, 2 I/O cores, 1 for host0if processing), and 2 cores for RE and PFE emulations(QEMU/KVM) ; Later a version with smaller footprint, less # of cores or RAM required
7/26/2019 Juniper Vmx i.lysogor
37/38
Performance
VMX
Tester
Test setup
8
.9G
8.9
G
8.9
G
8
.9G
8.9
G
8
.9G
8
.9G
8
.9G
8.9
G
Setup:
Single instance of VMX with 6 ports of 10G
sending bidirectional traffic
16 core total (among those, 6 for I/O, 6 for
packet processing)
20G RAM total, 16G memory for vFP
process
Basic routing is enabled, no filter
configured
Performance
60G bi-directional traffic per VMX instance
@ 1500 bytes
No packet loss
Complete RFC2544 results to follow
7/26/2019 Juniper Vmx i.lysogor
38/38