Data Center Interconnect Solution for EVPN Overlay networks
70 likes | 230 Vues
Data Center Interconnect Solution for EVPN Overlay networks. draft-rabadan-l2vpn -dci-evpn-overlay-01 Jorge Rabadan Senthil Sathappan Wim Henderickx Florin Balus Senad Palislamovic. IETF 89, March 2014 London, UK. The issue we want to address…. DATA CENTER INTERCONNECT
Data Center Interconnect Solution for EVPN Overlay networks
E N D
Presentation Transcript
Data Center Interconnect Solution for EVPN Overlay networks draft-rabadan-l2vpn-dci-evpn-overlay-01 Jorge Rabadan SenthilSathappan WimHenderickx Florin Balus SenadPalislamovic • IETF 89, March 2014 • London, UK
The issue we want to address… DATA CENTER INTERCONNECT FOR LAYER-2 EXTENSION DGW-1 EVI EVI WAN PEs DGW-2 HYPERVISOR HYPERVISOR HYPERVISOR EXISTING OR NEW WAN TECHNOLOGIES DIFFERENT OR SAME ADMIN DOMAINS (DC AND WAN) WAN VPLS PBB-VPLS DECOUPLED MODEL EVPN-OVERLAYS EVPN PBB-EVPN INTEGRATED MODEL
IP IP MAC MAC MPLS VXLAN IP IP MAC DECOUPLED MODEL INTEGRATED MODEL Interconnect requirements (Dec-M) PW or VLAN hand-off (PBB-)VPLS (PBB-)EVPN BGP EVPN for Overlay tunnels WAN Edge DGW-1 EVI EVI EVI EVI EVI HYPERVISOR HYPERVISOR HYPERVISOR DGW-2 • Optimizations on the DC GW: • Unknown-flooding reduction • Control of the MAC advertisements to the DC • ARP-flooding control MAC IP WAN • Clear and simple demarcation (QoS/ACL enforcement, OAM) • Minimum or no control plane interaction between DGWs and WAN PEs • Multi-homing required VID MAC
IP MAC VXLAN IP IP MAC INTEGRATED MODEL DECOUPLED MODEL Interconnect requirements (Int-M) BGP EVPN for Overlay tunnels (PBB-)VPLS DGW-1 EVI EVI EVI EVI VSI (PBB-)EVPN EVI HYPERVISOR HYPERVISOR HYPERVISOR DGW-2 MAC • Independent inclusive multicast trees in WAN and DC • If EVPN in the WAN the following end-to-end features: • MAC mobility, protection • Proxy-ARP WAN IP/MPLS • Data Plane AND Control plane gateway function on DGWs • Multi-homing required: • Per-service load balancing • Per-flow load balancing - only (PBB-)EVPN WAN IP/MPLS
DGW Control Plane EVPN extensions proposed to address the e2e EVPN model • evpn RT=2 • evpn RT=2 • evpn RT=2 • evpn RT=2 RD-DGW1 RD-DGW4 RD-DGW3 RD-NVE1 1 1 2 3 2 2 EVI EVI EVI EVI EVI EVI EVI EVI FW-1 VXLAN VXLAN MPLS VXLAN DGW-3 (non-DF) DGW-1 (DF) NVE3 NVE1 ESI=DC1 ESI=DC2 ESI=DC2 ESI=TS1 ESI=DC1 P2MP LSPs • ESI=DC1 AA:AA AA:AA AA:AA AA:AA AA:AA • ESI=TS1 TS2 ESI=DC2 TS1 • ESI=TS2 VNI1 VNI1 Label-x VNI1 Label-y AA:AA BB:BB • evpn RT=2 Ingress replication RD-DGW2 NVE4 NVE2 DGW-4 (DF) DGW-2 (non-DF) Definition of a ‘DCI-ESI’ used to advertise MACs learnt from EVPN to EVPN and allow e2e per-flow load-balancingand aliasing (and backup-path) FW-2 MPLS MAC mobility only propagated for mac-moves between DCs Independent inclusive mcast trees in each domain
DGW Data Plane EVPN extensions for B/U/M traffic in e2e all-active EVPN: no need for ESI label EVPN-MPLS EVPN for Overlay tunnels EVPN for Overlay tunnels FW-1 FW-1 DGW-3 (non-DF) DGW-1 (DF) 1 2 4 3 NVE3 NVE1 EVI EVI EVI EVI EVI EVI EVI EVI • ESI=TS1 TS2 TS1 • ESI=TS2 • ESI=DC1 • ESI=DC2 AA:AA BB:BB NVE4 NVE2 DGW-4 (DF) DGW-2 (non-DF) FW-2 FW-2 (1) (4) No change in the EVPN procedures for split-horizon at the NVEs (3) Non-DF will ONLY forward to local ACs DF will never forward to WAN SHG or non-DF (2) Non-DF will ONLY forward to local ACs DF will never forward to DC SHG or non-DF
NEXT STEPS • More feedback from WG