![]() It is important to recognize such situations and avoid incrementing the sequence number (in the MAC Mobility attribute) to infinity. As a result, the traffic originating from the hosts triggers continuous MAC moves among the PEs attached to the hosts. In a scenario where two or more hosts are misconfigured using the same (duplicate) MAC address, the duplicate MAC address is learned by the PEs in the VPLS. The 7210 SAS supports an enhanced version of this procedure, which is described in this section. In the latter case, PE1 considers it safe to forward the frame to the CE, even if it is unknown unicast.ĮVPN defines a mechanism to protect the EVPN service from control plane churn as a result of loops or accidental duplicated MAC addresses. If PE1 and PE2 are configured using ingress-replication-bum-label, PE3 sends unknown unicast packets with a BUM label and known unicast with a unicast label. To resolve this issue, unknown unicast traffic that arrives with a unicast label should not be blocked on the NDF. If PE3 hashing picks up PE1 as the destination of the aliased MAC1, the packets are blackholed. However, MAC1 is not yet known in PE1, which is the NDF for the ES. In an all-active multi-homing scenario, MAC1 is known in PE3 and aliasing is applied to MAC1. In Figure 51, the scenario on the right shows an example of transient black hole caused by delay in PE1 to learn MAC1. PE1 and PE2 know that the received packet is an unknown unicast packet consequently, the NDF (PE1) does not send the packets to the CE, which prevents transient and duplication. In an all-active multi-homing scenario, if a specified MAC address (for example, MAC1), is not yet learned in a remote PE (for example, PE3), but it is known in the two PEs of the ES (for example, PE1 and PE2), the latter PEs might send duplicated packets to the CE.Ĭonfiguring ingress-replication-bum-label in PE1 and PE2 resolves the issue. In the preceding figure, the scenario on the left shows an example of transient packet duplication caused by delay in PE3 to learn MAC1. Transient issues caused by “slow” MAC learning ![]() The EVPN-MPLS functionality is standardized in RFC 7432. EVPN-MPLS is generally used as an evolution for VPLS services. The Nokia implementation supports EVPN for MPLS tunnels (EVPN-MPLS), where PEs are connected by any type of MPLS tunnel. The main objective of EVPN is to build E-LAN services similar to IP-VPNs defined in RFC 4364, while supporting MAC learning in the control plane (distributed using multi-protocol BGP (MP-BGP)), efficient multi-destination traffic delivery, and single-active/active-active multi-homing.ĮVPN can be used as the control plane for different data plane encapsulations. EVPN, as described in RFC 7432, BGP MPLS-Based Ethernet VPN, is an IETF technology that uses a new BGP address family and allows Virtual Private LAN Services (VPLS) to operate in a similar manner to IP-VPNs, in which the MAC addresses and information to set up flooding trees are distributed by BGP.ĮVPN is designed to fill the gaps of traditional L2VPN technologies, such as VPLS. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |