The updates include an Ethernet segment identifier label that is used in loop prevention.

The updates advertise the Ethernet segment availability in a given EVPN service.

The updates include an MPLS label that is set to a non-zero value.

The updates include an Ethernet tag ID that is set to zero.

VPLS 10 must be configured with two BGP instances on PE3 and PE4.

On PE3 and PE4, VPLS 10 must be configured with two different route-distinguisher values: one for VXLAN and another for MPLS.

On PE3 and PE4, VPLS 10 must be configured with two different route-target values: one for VXLAN and another for MPLS.

A BGP export policy is required on PE3 and PE4 to ensure that IMET routes originated with VXLAN encapsulation are not advertised to the peer across the core network.

In the single-active mode, the CE requires a LAG to be configured between the CE and all attached PEs.

In the single-active mode, the CE forwards traffic to all attached PES and receives traffic from a single PE.

In the all-active mode, all PES attached to a CE can forward traffic to and from the CE.

The Nokia 7750 SR supports a CE being multi-homed to a maximum of two PEs.

CEI generates an update message to PEI withdrawing its MAC.

PEI generates an update message to remote PES identifying the new location of CEI.

PE2 advertises a MAC/IP route for MACI with a sequence number higher than that received from PEI.

PE3 waits to receive a data packet from CEI to update its FDB entry for MACI.

The service distinguisher (label or VNI) is advertised with the MAC/IP EVPN update.

Route targets are used to uniquely identify routes between EVIS in the case of MAC address overlaps.

A PE uses a single MP-BGP session with a remote peer to exchange the routes for all EVIs.

A PE advertises locally-learned MAC addresses to remote PES using EVPN type-2 routes.

PEI consults the FDB of RVPLS 1 and forwards the traffic to the local interface of VPRN 11.

PEI encapsulates the packet with two labels: an outer transport label and an inner service label.

PE2 inspects the service label and determines that it is associated with RVPLS 2.

PE2 consults the FDB of RVPLS 2 and forwards the traffic to Host 2.

PEI does not flood the packet because PEI is acting as non-designated forwarder (non-DF) for VPLS 10.

PEI sends the packet to PE2 but not to PE3 because PE3 is connected to the originating ES.

PEI sends the packet to PE2 and to PE3. An ESI label is included only in the packet sent to PE2.

PEI sends the packet to PE2 and to PE3. An ESI label is included only in the packet sent to PE3.

PEI advertises an auto-discovery per EVPN instance (A-D per EVI) route to PE3 as soon as the SAP becomes operationally

PE3 advertises an IMET route to PEI as soon as VPWS 4 is administratively enabled.

PEI and PE3 exchange their service labels using A-D per EVI routes.

PE3 and PE4 exchange their service labels over an established targeted LDP session.

1

2

3

4

EVPN routes are advertised with a service label associated with the SBD VPLS.

IP-Prefix routes exchanged between PES include a non-zero gateway IP address as an overlay index.

EVPN MAC/IP routes are used to advertise the MAC and IP addresses of local hosts.

EVPN MAC/IP routes are used to advertise the MAC and IP addresses of SBD IRB interfaces.