drafthaoevpnmhn00 July 2013 1 MHN in EVPN Weiguo Hao Huawei Yizhou Li Huawei Pei Xu Huawei haoweiguohuaweicom liyizhouhuaweicom xupeihuaweicom July 2013 Berlin Germany ID: 229554
Download Presentation The PPT/PDF document "Multi-homed network in EVPN" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
Multi-homed network in EVPN draft-hao-evpn-mhn-00
July 2013
1
MHN in EVPN
Weiguo Hao(Huawei)Yizhou Li(Huawei)Pei Xu(Huawei)
haoweiguo@huawei.comliyizhou@huawei.comxupei@huawei.com
July, 2013 Berlin GermanySlide2
EVPN Network
Multi-homed network (MHN) in EVPN scenarios
July 2013
2
MHN in EVPN
PE1PE2B1B2B3
Bridged Network
There are two categories of mechanisms to avoid the layer 2 traffic loop.
1, PEs doesn’t participate in the control protocol of the bridged network , that is designated forwarder (DF) election mechanism.
2, PEs participate in the control protocol of the bridged network, active/active MAC-based load balancing can be achieved through the solution.
ES1
ES2
ES3Slide3
DF MechanismJuly 2013
3
MHN in EVPN
VLAN-based load balancing
among PEs can be achieved. Only one of the links between theswitched bridged network and the PEs is active for a given VLAN.All end systems of one VLAN can access the EVPN network through only one PE.
EVPN NetworkPE1PE2B1(STP Root)B2B3
BLOCKED
MSTP Network
ES1
ES2
ES3
EVPN For DF
Non-DF
ES1,ES2 and ES3 access to EVPN network through PE1 Slide4
Active/Active MAC-based load balancing mechanism
July 2013
4
MHN in EVPN
EVPN Network
PE1PE2B1B2B3
BLOCKED
MSTP Network
ES1
ES2
ES3
ES1 and ES2 access to EVPN network through PE1
BLOCKED
ES3 accesses to EVPN network through PE2
The mechanism requires PEs participate in the control plane protocol of the bridged network.
per-
vlan
MAC-based load balancing can be achieved through the mechanism , so it can achieve better load balancing than DF election.
Two solutions:
1, emulated MSTP root bridge solution.
2, bridge control plane protocol tunneling solution.Slide5
Emulated MSTP root bridge solution
July 2013
5
MHN in EVPN
EVPN Network
PE1PE2B1(STP Root)B2B3
BLOCKED
MSTP Network
ES1
ES2
ES3
BLOCKED
PE1 and PE2 emulate MSTP root bridge
PE1 & PE2 use the same bridge ID to emit spanning tree BPDUs as the highest priority
root Bx.
When PE2 receives TC BPDU from the bridge network , PE2 tunnel the TC BPDU to PE1.
This solution is only applicable for STP/MSTP network.
PE3Slide6
Bridge control plane protocol tunneling solution
EVPN Network
PE1(STP Root)
PE2
B1
B2B3
BLOCKED
MSTP Network
ES1
ES2
ES3
BLOCKED
PE3
BPDU tunnel
EVPN Network
PE1
PE2
B1
B2
B3
BLOCKED
G.8032 Network
ES1
ES2
ES3
BLOCKED
PE3
G.8032 message tunnel
RPL owner node
MHN in EVPN
July 2013
RPL owner node
The cost should be set to 0 to avoid blockingSlide7
Bridge control plane protocol tunneling solutionJuly 2013
MHN in EVPN
7
The solution can be used for both MSTP and G.8032 domain.
Scenario 1: Local bridged network is MSTPPE1 and PE2 act as normal MSTP bridge nodes. BPDU message can be sent through tunnel over EVPN network between PE1 and PE2. Scenario 2: Local bridged network is G.8032PE1 and PE2 act as normal G.8032 ring nodes. They support standard FDB MAC learning, forwarding, flush behavior and port blocking/unblocking mechanisms. G.8032 message can be sent through tunnel over EVPN network between PE1 and PE2.Slide8
EVPN protocol extensionJuly 2013
8
MHN in EVPN
"M" bit is introduced to indicate multi-homing mode of MAC-based all active without DF Election.
DF selection procedures should be skipped if "M" bit is set to be 1.When remote PE receives Ethernet A-D route withdraw message, it simply invalidates the MAC entries for the segment that corresponding to the Ethernet A-D route.0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+| Type=0x06 | Sub-Type=0x01 |DF|R|M| Reserved=0 |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+| Reserved = 0| ESI Label |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ESI Label Extended CommunitySlide9
Next StepsJuly 2013
9
MHN in EVPN
Does WG think this can be put into EVPN base protocol?
Any other comments and suggestions?