#Sap pes mac
Otherwise, for example, PE3 continues sending traffic with MAC DA = CE1 to PE1, and PE1īoth ES peers (PE1 and PE2) should be configured with the same ve-id for the ES SAP. PE4 the need to flush MAC addresses learned from PE1 (flush-all-from-me message). Ve-id are updated so that the remote BGP-VPLS PEs can perform a mac-flush operation onĪs an example, in case of a failure on the Ethernet-segment sap on PE1, PE1 must indicate PE3 and Upon a Designatedįorwarder (DF) switchover, the F and D bits of the generated L2VPN routes for the SAP Indicate the state of the multi-homed SAPs to the remote BGP-VPLS PEs.
The sap> bgp-vpls-mh-veid number command should be configured on the SAPs that are part of anĮVPN single-active Ethernet Segment, and allows the advertisement of L2VPN routes that In addition to the BGP-VPLS routes sent for the service ve-id, the multi-homing PEs in this case need to generate additional BGP-VPLS routes per Ethernet Segment (per VPLS service) for the purpose of MAC flush on the remote BGP-VPLS PEs in case of failure. PE can signal the non-DF state to CE1 (in the form of LACP out-of-synch or
Lag> monitor-oper-group 1 so that the non-DF The LAG is associated with theĮthernet-segment 1 on PE1 and PE2, which is configured as single-active and with The EVPN PEs through a single LAG (lag-1). BGP-VPLS to EVPN Integration and Single-Active MHĪlthough other single-active examples are supported, in Figure 1, CE1 is connected to
0 kommentar(er)
