MX ALS DATACENTER EDGE

Transcription

1 JUNIPER 5 DAAGSE MX ALS DATACENTER EDGE Rick Mur SENIOR SYSTEM ENGINEER JUNIPER NETWORKS JNCIE-SP #851, JNCIE-ENT #456, CCIE4 #21946

2 LEGAL DISCLAIMER This statement of direction sets forth Juniper Networks current intention and is subject to change at any time without notice. No purchases are contingent upon Juniper Networks delivering any feature or functionality depicted in this presentation.

3 EXPANDING THE UNIVERSAL EDGE One JUNOS One TRIO CHIPSET One UNIVERSAL EDGE 40Tbps 17Tbps 80Tbps 34Tbps N x 1Gbps 20Gbps 40Gbps 60Gbps 80Gbps 80 Gbps 1.6Tbps 4.8Tbps 2.8Tbps 1.4Tbps 8.8Tbps 5.3Tbps 2.6Tbps vmx MX 5-80 MX 104 MX 240 MX 480 MX 960 MX 2010 MX 2020 REVENUE GENERATION FOR THE NEXT DECADE

4 JUNIPER MX SERIES MID RANGE SOLUTION Family of high performance Mid-Range Routers MX5: 5G MR Router 20x1G MX10: 10G MR Router 20x1G & 1 Modular Slot MX40: 40G MR Router 2 Modular Slots & 2x10G MX80: 2 Modular Slots & 4x10G Support for WAN (TDM) Interfaces in Modular slots Option to upgrade from MX5 to MX10 to MX40 to 80 Service MIC support in rear slot MX5 MX10 MX40 MX80 4 Copyright 2013 Juniper Networks, Inc.

5 MX104: NG-PRE-AGGREGATION PLATFORM 4x 10GE SFP+ built in LAN/WAN uplink ports BITS (T1/E1), 10MHz, 1PPS & ToD I/O Alarm extension port 4 MIC slots, 20G BW per slot Dual redundant 1RU 600W AC/DC PSUs Dual redundant hot pluggable REs Compact, Redundant & Future proof Trio based PFE 80G ETSI compliant 17.5 inches (W) x 3.5RU (H) x 9.5 inches (D) Wide operating temp range -40C to +65C Forced cooling with side-to-side airflow; FRU able fan tray SyncE, SONET and 1588 (Brilliant IP integration) timing features 5 Copyright 2013 Juniper Networks, Inc.

6 MX104 ROUTE ENGINE 2 USB ports AUX port Console port Mgmt port 8GB NAND Flash Freescale P GHz CPU 4GB DDR3 RAM (mini DIMM) Dual redundant hot pluggable REs for enhanced availability

7 MX104 SCALE MAC scaling FIB capacity : IPv4 unicast FIB capacity : IPv6 unicast RIB capacity (IPv4) RIB capacity (IPv6) PARAMETERS SCALE 512k 1Mil 512K min 4Mil 3Mil Max L3vpn prefixes with remote PE using one VPNv4 label per CE (Juniper Way) 1.6Million Max L3vpn prefixes with remote PE using one VPNv4 label per prefix (Cisco way) 600K Max VRFs 2000 Max bridge / learning domains 8k Max PWs 16K Max L2VPN (Kompella L2VPN) instanses 2000

8 MX L2 REFERENCE STYLE CONFIGURATION Bridge-Domain L2 Flooding Domain Typically one BD per cloud tenant Assigned to tenant WAN instance BD level VLAN tag preserved over WAN IRB.0 Bridge Domain Automatic port level VLAN manipulation BD VLAN-ID used to identify tenant 4K VLAN / L2 learning domain per BD Extensive VLAN manipulations: swap, pop, push, pop-swap, swap-push, swapswap IFL 0: VLAN- ID 100 L3VPN.0 Bridge-Domain.0 VLAN-ID: 1001 IFL 1: VLAN 200 IFL 2: VLAN 300 VPLS.0 IFL 3: VLAN Copyright 2013 Juniper Networks, Inc. WAN Instances Stitched per tenant Multi-tenancy Interface tags locally significant IRB per tenant for L3 connectivity

9 VIRTUAL MX

10 VMX A SCALE-OUT VIRTUAL ROUTER Scale-up (Physical MX) Scale-out (Virtual MX) Optimize for density in a single instance of the platform. Innovate in ASIC, power and cooling technologies to drive density and most efficient power footprint. Virtualized platforms not optimized to compete with physical routers with regards to capacity per instance. Each instance is a router with its own dedicated control-plane and data-plane. Allows for a smaller footprint deployment with administrative separation per instance. Innovate in orchestration and management capabilities to easily deploy and manage a scale-out solution. 10 Copyright 2013 Juniper Networks, Inc.

11 VIRTUAL & PHYSICAL MX COMPARISON Forwarding Plane Control Plane = + Trio μcode + MX Trio ASIC VMX Trio μcode compiled = + as x86 instructions + x86 processor This model enables Virtual MX to be feature parity with Physical MX 11 Copyright 2013 Juniper Networks, Inc.

12 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) VFP VCP Virtual TRIO LC- Kernel RPD CHASSISD DCD SNMP SR-IOV Intel DPDK Guest OS (Linux) Hypervisor Guest OS (JUNOS) x86 Hardware 12 Copyright 2013 Juniper Networks, Inc. Physical NICs

13 VMX AS CLOUD SERVICE PROVIDER GATEWAY MARKET REQUIREMENT Virtual Private Cloud customers need a gateway router in the cloud to route between subnets, provide NAT and reachability from a public or private network Cloud Service Providers can offer a virtualized router to offer this functionality VMX VALUE PROPOSITION VMX can provide all the functionality enterprises utilize for an on-site MX gateway router. This functionality primarily includes NAT, IPSec and FW VMX can be managed similar to a cloud based application 13 Copyright 2013 Juniper Networks, Inc.

14 VMX AS A DC GATEWAY MARKET REQUIREMENT Service Providers need a gateway router to connect the virtual networks to the physical network Gateway should be capable of supporting different DC overlay, DC Interconnect and L2 technologies in the DC such as GRE, VXLAN, VPLS and EVPN VMX VALUE PROPOSITION VMX supports all the overlay, DCI and L2 technologies available on MX Scale-out control plane to scale up VRF instances and number of VPN routes 14 Copyright 2013 Juniper Networks, Inc.

15 UNIVERSAL SDN GATEWAY

16 SDN AND THE MX SERIES Delivering innovation inside and outside of the data center Flexible SDN enabled silicon to provide seamless workload mobility and connections between private and public cloud infrastructures USG (Universal SDN Gateway) The most advanced and flexible SDN bridging and routing gateway EVPN (Ethernet VPN) Next-generation technology for connecting multiple data centers and providing seamless workload mobility VMTO (VM Mobility Traffic Optimizer) Creating the most efficient network paths for mobile workloads

17 USG (UNIVERSAL SDN GATEWAY) Introducing four new options for SDN enablement USG (Universal SDN Gateway) Provide SDN-to-non-SDN translation, same IP subnet Layer2 USG SDN to IP (Layer 2) Provide SDN-to-non-SDN translation, different IP subnet Layer3 USG SDN to IP (Layer 3) Provide SDN-to-SDN translation, same or different IP subnet, same or different overlay SDN to SDN SDN USG Provide SDN-to-WAN translation, same or different IP subnet, same or different encapsulation WAN USG SDN to WAN Remote Data Center Branch Offices Internet

18 USGs INSIDE THE DATA CENTER USG (Universal SDN Gateway) DATA CENTER 1 Layer2 USG VxLAN VxLAN VxLAN VxLAN VxLAN Native IP L2 Native IP L2 Native IP L2 Native IP L2 Native IP L2 Native IP L2 Layer3 USG SDN USG NSX SDN Pod 1 VxLAN VxLAN VxLAN VxLAN VxLAN Using Layer 2 USGs to bridge between devices that reside within the same IP subnet: 1. Bare metal servers like high-performance databases, nonx86 compute, IP storage, non-sdn VMs Native IP L2 Native IP L2 Native IP L2 Native IP L2 Native IP L2 Native IP L2 Native IP L2 Native IP L2 Native Legacy Pods 2. Layer 4 7 services such as load balancers, firewalls, Application Device Controllers, and Intrusion Detection/Prevention gateways. L4 7 Services WAN USG

19 USGs INSIDE THE DATA CENTER USG (Universal SDN Gateway) DATA CENTER 1 Layer2 USG VxLAN VxLAN VxLAN VxLAN VxLAN Native IP L3 Native IP L3 Native IP L3 Native IP L3 Native IP L3 Native IP L3 Layer3 USG SDN USG NSX SDN Pod 1 VxLAN VxLAN VxLAN VxLAN VxLAN Using Layer 3 USGs to route between devices that reside within different IP subnets: 1. Bare metal servers like high-performance databases, nonx86 compute, IP storage, non-sdn VMs Native IP L3 Native IP L3 Native IP L3 Native IP L3 Native IP L3 Native IP L3 Native IP L3 Native IP L3 Native Legacy Pods 2. Layer 4 7 services such as load balancers, firewalls, Application Device Controllers, and Intrusion Detection/Prevention gateways. L4 7 Services WAN USG

20 USGs INSIDE THE DATA CENTER USG (Universal SDN Gateway) DATA CENTER 1 Layer2 USG VxLAN VxLAN VxLAN VxLAN VxLAN VxLAN VxLAN VxLAN VxLAN Layer3 USG SDN USG WAN USG NSX SDN Pod 1 VxLAN VxLAN VxLAN VxLAN VxLAN Using SDN USGs to communicate between islands of SDN: 1. NSX to NSX Risk, scale, change control, administration 2. NSX to Contrail Multi-vendor, migrations GRE MPLSoverGRE MPLSoverGRE MPLSoverGRE MP NSX SDN Pod 2 VxLAN VxLAN VxLAN VxLAN VxLAN VxLAN Contrail SDN Pod 1 LSoverGRE MPLSoverGRE MPLS

21 USGs FOR REMOTE CONNECTIVITY USG (Universal SDN Gateway) DATA CENTER 1 Internet Layer2 USG VxLAN VxLAN VxLAN VxLAN VxLAN Native IP L3 Native IP L3 Native IP L3 Native IP L3 Native IP L3 Native IP L3 Layer3 USG SDN USG WAN USG SDN Pod 1 Using SDN USGs to communicate to resources outside the local data center: 1. Data Center Interconnect SDN to [VPLS, EVPN, L3VPN] 2. Branch Offices SDN to [GRE, IPSec] 3. Internet SDN to IP (Layer 3) GRE GRE GRE GRE GRE GRE GRE GRE GRE GRE GRE GRE GRE EVPN EVPN EVPN EV PN EVPN EVPN EVPN EVPN BRANCH OFFICES NSX SDN Pod 2 EVPN EVPN VxLAN VxLAN VxLAN VxLAN VxLAN DATA CENTER 2

22 UNIVERSAL GATEWAY SOLUTIONS USG (Universal SDN Gateway) DATA CENTER 1 Layer2 USG VxLAN VxLAN VxLAN VxLAN VxLAN Native IP L2 Native IP L2 Native IP L2 Native IP L2 Native IP L2 Native IP L2 Native IP L3 Native IP L3 Native IP L3 Native IP L3 Native IP L3 Native IP L3 Layer3 USG SDN USG NSX SDN Pod 1 BRANCH OFFICES VxLAN VxLAN VxLAN VxLAN VxLAN NSX SDN Pod 2 GRE GRE GRE GRE GRE GRE GRE DATA CENTER 2 GRE GRE GRE VxLAN VxLAN VxLAN EVPN VxLAN Internet VxLAN VxLAN VxLAN VxLAN Native IP L3 Native IP VxLAN VxLAN VxLAN VxLAN VxLAN MPLSoverGRE MPLSoverGRE MPLSoverGRE Native IP L2 Native IP L2 Native IP L2 Native IP L2 Native IP L3 Native IP L3 Native IP L3 Native IP L3 NSX SDN Pod 2 LSoverGRE MPLSoverGRE MPLS Native Native IP L2 IP Native L3 Native IP L2 IP Native L3 Native IP IP Contrail SDN Pod 1 L2 Native IP L2 Native L3 Native IP L3 Native Legacy Pods L4 7 Services WAN USG

23 USG COMPARISONS USG (Universal SDN Gateway) Layer 2 Layer 3 SDN WAN USG USG USG USG Description Description Provide SDN-to-non-SDN translation, same IP subnet Provide SDN-to-non-SDN translation, different IP subnet Provide SDN-to-SDN translation, same or different IP subnet, same or different Overlay Provide SDN-to-WAN translation, same or different IP subnet QFX5100 MX Series/EX9200 X86 Appliance Competing ToRs Competing Chassis Use Cases NSX or Contrail talk Layer 2 to non-sdn VMs, bare metal and L4-7 services NSX or Contrail talk Layer 3 to non-sdn VMs, bare metal and L4-7 services and Internet NSX or Contrail talk to other PODs of NSX or Contrail NSX or Contrail talk to other remote locations branch, DCI

24 EVPN ETHERNET VPN

25 PRE-EVPN: LAYER 2 STRETCH BETWEEN DATA CENTERS Data Plane Without EVPN Only one path can be active at a given time Remaining links are put into standby mode EVPN (Ethernet VPN) Control Plane Layer 2 MAC tables are populated via the data plane (similar to a traditional L2 switch) Results in flooding of packets across WAN due to out of sync MAC tables MAC VLAN Interfaces MAC VLAN Interfaces DATA CENTER 1 AA 10 xe-1/0/0.10 Router 1 s MAC Table BB 10 xe-1/0/0.10 Router 2 s MAC Table DATA CENTER 2 Server 1 xe-1/0/0.10 ge-1/0/0.10 ge-1/0/0.10 xe-1/0/0.10 Server 2 MAC: AA xe-1/0/0.10 PRIVATE MPLS WAN without EVPN xe-1/0/0.10 MAC: BB VLAN 10 ge-1/0/0.10 ge-1/0/0.10 VLAN 10

26 POST-EVPN: LAYER 2 STRETCH BETWEEN DATA CENTERS Data Plane Control Plane With EVPN All paths are active Inter-data center traffic is load-balanced across all WAN links Layer 2 MAC tables are populated via the control plane (similar to QFabric) Eliminates flooding by maintaining MAC table synchronization between all EVPN nodes EVPN (Ethernet VPN) MAC VLAN Interfaces MAC VLAN Interfaces DATA CENTER 1 AA 10 xe-1/0/0.10 BB 10 ge-1/0/0.10 BB 10 xe-1/0/0.10 AA 10 ge-1/0/0.10 DATA CENTER 2 Router 1 s MAC Table Router 2 s MAC Table Server 1 xe-1/0/0.10 ge-1/0/0.10 ge-1/0/0.10 xe-1/0/0.10 Server 2 MAC: AA xe-1/0/0.10 PRIVATE MPLS WAN without EVPN xe-1/0/0.10 MAC: BB VLAN 10 ge-1/0/0.10 ge-1/0/0.10 VLAN 10

27 VMTO VM Mobility Traffic Optimizer

28 THE NEED FOR L2 LOCATION AWARENESS VMTO (VM Mobility Traffic Optimizer) Scenario without VMTO Scenario with VMTO enabled PRIVATE MPLS WAN PRIVATE MPLS WAN VLAN 10 VLAN 10 VLAN 10 VLAN 10

29 WITHOUT VMTO: EGRESS TROMBONE EFFECT /24 Server 1 VMTO (VM Mobility Traffic Optimizer) DC 1 VLAN 20 PRIVATE MPLS WAN DC 2 Standby VRRP DG: VLAN /24 Active VRRP DG: Task: Server 3 in Data Center 3 needs to send packets to Server 1 in Data Center 1. Problem: Server 3 s active Default Gateway for VLAN 10 is in Data Center 2. Effect: 1. Traffic must travel via Layer 2 from Data Center 3 to Data Center 2 to reach VLAN 10 s active Default Gateway. 2. The packet must reach the Default Gateway in order to be routed towards Data Center 1. This results in duplicate traffic on WAN links and suboptimal routing hence the Egress Trombone Effect. DC 3 Standby VRRP DG: VLAN 10 Server 2 Server /24 Standby VRRP DG:

30 WITH VMTO: NO EGRESS TROMBONE EFFECT /24 Server 1 VMTO (VM Mobility Traffic Optimizer) DC 1 VLAN 20 PRIVATE MPLS WAN DC 2 Active RVI DG: VLAN /24 Active RVI DG: Task: Server 3 in Datacenter 3 needs to send packets to Server 1 in Datacenter 1. Solution: Virtualize and distribute the Default Gateway so it is active on every router that participates in the VLAN. Effect: 1. Egress packets can be sent to any router on VLAN 10 allowing the routing to be done in the local datacenter. This eliminates the Egress Trombone Effect and DC 3 Active RVI DG: VLAN 10 Active RVI DG: creates the most optimal forwarding path for the Inter- Server 2 Server 3 DC traffic /24

31 WITHOUT VMTO: INGRESS TROMBONE EFFECT /24 Server 1 VMTO (VM Mobility Traffic Optimizer) Route Mask Cost Next Hop Datacenter 2 DC 1 VLAN Datacenter 3 DC 1 s Edge Router Table Without VMTO /24 Cost 5 PRIVATE MPLS WAN /24 Cost 10 DC 2 VLAN /24 Task: Server 1 in Datacenter 1 needs to send packets to Server 3 in Datacenter 3. Problem: Datacenter 1 s edge router prefers the path to Datacenter 2 for the /24 subnet. It has no knowledge of individual host IPs. Effect: 1. Traffic from Server 1 is first routed across the WAN to Datacenter 2 due to a lower cost route for the /24 subnet. 2. Then the edge router in Datacenter 2 will send the packet via Layer 2 to Datacenter 3. DC 3 VLAN 10 Server 2 Server /24

32 WITH VMTO: NO INGRESS TROMBONE EFFECT /24 Server 1 VMTO (VM Mobility Traffic Optimizer) Route Mask Cost Next Hop Datacenter 2 DC 1 VLAN Datacenter Datacenter Datacenter 3 DC 1 s Edge Router Table WITH VMTO /32 Cost /24 Cost 5 PRIVATE MPLS WAN /32 Cost /24 Cost 10 DC 2 VLAN /24 Task: Server 1 in Datacenter 1 needs to send packets to Server 3 in Datacenter 3. Solution: In addition to sending a summary route of /24 the datacenter edge routers also send host routes which represent the location of local Effect: servers. 1. Ingress traffic destined for Server 3 is sent directly across the WAN from Datacenter 1 to Datacenter 3. DC 3 VLAN 10 This eliminates the Ingress Trombone Effect and Server 2 Server 3 creates the most optimal forwarding path for the Inter- DC traffic /24

33 BILL OF MATERIALS SMALL DATACENTER DEPLOYMENTS MX104-MX5 20x 1GE MIC Services MIC slot available Included: JUNOS, ADV-R2, JFLOW-5G Optional: Redundant RE QFX S 10GE access/aggregation Start as small VCF Optional: EX4300 as 1GE access Junos Space Network Management Platform Network Director

34