Data Center Interconnect Solution for EVPN Overlay networks

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…
DGW-1
DATA CENTER INTERCONNECT
FOR LAYER-2 EXTENSION
HYPERVISOR EVI
WAN
EVI
WAN
PEs
HYPERVISOR HYPERVISOR DGW-2
EVPN-OVERLAYS
DIFFERENT OR SAME
ADMIN DOMAINS
(DC AND WAN)
DECOUPLED
MODEL
INTEGRATED
MODEL
draft-rabadan-l2vpn-dci-evpn-overlay-01
EXISTING OR NEW
WAN
TECHNOLOGIES
VPLS
PBB-VPLS
EVPN
PBB-EVPN
IETF89 – March 2014
DECOUPLED
MODEL
Interconnect requirements (Dec-M)
PW or VLAN
hand-off
BGP EVPN for
Overlay
tunnels
INTEGRATED
MODEL
(PBB-)VPLS
(PBB-)EVPN
WAN
Edge
DGW-1
EVI
HYPERVISOR EVI
EVI
WAN
IP
HYPERVISOR MAC
EVI
EVI
HYPERVISOR IP
MAC
VXLAN
DGW-2
•  Optimizations on the DC GW:
IP
MAC
IP
MAC
MPLS
•  Clear and simple demarcation
(QoS/ACL enforcement, OAM)
•  Minimum or no control plane
interaction between DGWs and
WAN PEs
•  Multi-homing required
draft-rabadan-l2vpn-dci-evpn-overlay-01
IP
VID
MAC
Ø  Unknown-flooding
reduction
Ø  Control of the MAC
advertisements to the DC
Ø  ARP-flooding control
IETF89 – March 2014
DECOUPLED
MODEL
Interconnect requirements (Int-M)
BGP EVPN for
Overlay
tunnels
INTEGRATED
MODEL
(PBB-)VPLS
DGW-1
EVI
IP
HYPERVISOR MAC
(PBB-)EVPN
EVI
HYPERVISOR IP
EVI
WAN
IP/MPLS
MAC
VXLAN
VSI
WAN
IP/MPLS
EVI
HYPERVISOR EVI
DGW-2
IP
MAC
•  Data Plane AND Control plane gateway
function on DGWs
•  Multi-homing required:
Ø  Per-service load balancing
Ø  Per-flow load balancing - only
(PBB-)EVPN
draft-rabadan-l2vpn-dci-evpn-overlay-01
•  Independent inclusive multicast
trees in WAN and DC
•  If EVPN in the WAN the following
end-to-end features:
Ø  MAC mobility, protection
Ø  Proxy-ARP
IETF89 – March 2014
DGW Control Plane EVPN extensions proposed to address the
e2e EVPN model
EVI1
MAC
ESI
NH
evpn RT=2
AA:AA
TS1
NVE1,2
RD-NVE1
BB:BB
DC2
DGW3,4
ESI=TS1
VNI1
DGW-1
(DF)
NVE1
1
EVI
ESI=TS1
1
NVE2
NH
AA:AA
DC1
DGW1,2
BB:BB
TS2
NVE3,4
AA:AA
DGW-3
(non-DF)
Label-x
MPLS
EVI
EVI
ESI
ESI=DC1
FW-1
VXLAN
AA:AA
evpn RT=2
MAC
RD-DGW1
AA:AA
TS1
EVI1
2
Ingress
replication
ESI=DC1
EVI
EVI
ESI=DC2
evpn RT=2
ESI=DC1
AA:AA
Label-y
Definition of a ‘DCI-ESI’ used to advertise
FW-2
MPLS
MACs learnt from EVPN to EVPN and
allow e2e per-flow load-balancing and
aliasing (and backup-path)
Independent inclusive mcast trees in
each domain 2
draft-rabadan-l2vpn-dci-evpn-overlay-01
NVE3
AA:AA
EVI
VNI1
EVI
VXLAN
TS2
ESI=TS2
evpn RT=2
BB:BB
EVI
RD-DGW4
RD-DGW2
DGW-2
(non-DF)
RD-DGW3
ESI=DC2
2
P2MP LSPs
evpn RT=2
DGW-4
(DF)
ESI=DC2
NVE4
AA:AA
VNI1
VXLAN
MAC mobility only propagated for
mac-moves between DCs
3
IETF89 – March 2014
DGW Data Plane EVPN extensions for B/U/M traffic in e2e allactive EVPN: no need for ESI label
EVPN for
Overlay tunnels
EVPNMPLS
FW-1
FW-1
EVI
ESI=TS1
DGW-3
(non-DF)
DGW-1
(DF)
NVE1
TS1
EVPN for
Overlay tunnels
EVI
2
EVI
EVI
3
ESI=DC1
NVE3
4
ESI=DC2
ESI=TS2
AA:AA
TS2
BB:BB
EVI
EVI
EVI
EVI
1
NVE2
FW-2
(1) (4)
No change in the EVPN procedures
for split-horizon at the NVEs
NVE4
DGW-4
(DF)
DGW-2
(non-DF)
FW-2
(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
draft-rabadan-l2vpn-dci-evpn-overlay-01
IETF89 – March 2014
NEXT STEPS
•  More feedback from WG
draft-rabadan-l2vpn-dci-evpn-overlay-01
IETF89 – March 2014

Download Report