ON THIS PAGE
Example: Configuring LACP for EVPN Active-Active Multihoming
This example shows how to configure the Link Aggregation Control Protocol (LACP) on multihomed customer edge (CE) and provider edge (PE) devices in an Ethernet VPN (EVPN) active-active multihomed network.
Requirements
This example uses the following hardware and software components:
Four MX Series 5G Universal Routing Platforms with MPC interfaces only, of which:
Two routers are configured as PE devices connected to a common multihomed customer site.
One router is configured as a remote PE device connected to a single-homed customer site.
One router is configured as the core provider device.
Two CE devices, of which:
One CE device is multihomed to the two PE devices.
One CE device is single-homed to the remote PE device.
Junos OS Release 17.1 or later running on all the PE devices.
Before you begin:
Configure the device interfaces and enable MPLS on all the interfaces of the PE devices.
Configure OSPF or any other IGP between the core provider device and the PE devices.
Configure MPLS and a label-switched path (LSP) from the ingress PE device to the remote egress PE device.
Configure an internal BGP session between the PE devices.
Note:We recommend that you configure Bidirectional Forwarding Detection (BFD) on the BGP session for faster detection of core isolation and better convergence.
Overview
Starting with Junos OS Release 17.1, an extra level of redundancy can be achieved in an EVPN active-active multihoming environment by configuring LACP on both the endpoints of the multihomed CE-PE link. The multihomed devices are configured with aggregated trunk links, where the link aggregation group (LAG) interfaces of the CE-PE link can either be in the active or in the standby state. When the LAG interface is in the active state, data traffic is transmitted over the CE-PE link. When the LAG interface is in the standby state, data traffic is blocked and only control traffic for communicating LAG interface state is transmitted over the link.
The LAG interface state is monitored and operated by LACP to ensure fast convergence on isolation of a multihomed PE device from the core. When there is a core failure, a null route can occur at the isolated PE device. However, with the support for LACP on the CE-PE link, at the time of core isolation, the CE-facing interface of the multihomed PE device is set to the standby state, thereby blocking data traffic transmission from and toward the multihomed CE device. After the core recovers from the failure, the interface state is switched back from standby to active.
The support for LACP for EVPN active-active multihoming is applicable to both EVPN with MPLS and EVPN with VXLAN.
When LACP is configured on the CE-PE link, isolation of the multihomed PE device from the core is handled as follows:
-
When the EVPN BGP peers are null for a multihomed PE device, the PE device is isolated from the core. The CE devices connected to the isolated PE device are notified about the core failure by the isolated PE device.
-
On learning about the core failure, data traffic is not forwarded from the CE device to the isolated multihomed PE device. Instead, the traffic is diverted to the other multihomed PE devices that belong to the same LAG. This helps in preventing traffic black holes at the isolated PE device.
-
If the multihomed CE device uses the LAG for load balancing traffic to multiple active multihomed PE devices, then the LACP configuration along with the same system ID configured on all the multihomed PE devices for that given LAG, triggers an LACP out-of-sync to all the attached multihomed CE links.
When configuring LACP on the multihomed devices, be aware of the following considerations:
-
The LAG link can operate either in the active or in the standby state regardless of the UP/DOWN operational state.
-
On system reboot, the LACP link on the multihomed PE device is in the active state.
-
When the control plane goes down or when the BGP-EVPN session is down, LACP is notified to run multiplexer state machine for the aggregation port and move the link from active to standby.
-
An interface is not treated as up unless it operates in the active state and its operational state is also up.
-
The following features are not supported with LACP on EVPN active-active multihoming:
-
Ethernet segment identifier (ESI) value auto-derivation from LACP system ID.
-
Redundancy coverage for non-LAG interfaces.
-
Redundancy coverage for core isolation with static LAGs.
-
Node isolation.
-
Access failures for LACP with EVPN active-active multihoming.
-
Topology
Figure 1 illustrates an EVPN active-active multihoming network with LACP configured on the multihomed CE and PE devices. Device CE1 is single-homed and is connected to a remote PE device, PE1. Device PE2 and Device PE3 connect to a common multihomed CE—CE2. Device P is the core device to which all the PE devices (PE1, PE2, and PE3) are connected.
The endpoints of the multihomed devices—Device CE2, Device PE2, and Device PE3—are configured with LACP on the CE-PE link.
Core isolation of Device PE3 is handled as follows:
-
After LACP is configured on the multihomed CE-PE links, the LACP configuration and operational data is synchronized between the LACP peers to operate as a LAG.
The synchronization between the LACP peers happens with the exchange of control PDUs, and is required for the following reasons:
-
To determine the state of the links in the Ethernet bundle—all-active or standby.
-
To detect and handle CE device misconfiguration when LACP Port Key is configured on the PE device.
-
To detect and handle miswiring between CE and PE devices when LACP Port Key is configured on the PE device.
-
To detect and react to actor or partner churn when the LACP speakers are not able to converge.
-
-
After Device PE2 and Device PE3 establish BGP session with at least one peer, the state of the CE-PE link is set to unblocking mode by LACP.
-
When there is a core failure, and the BGP EVPN peers of Device PE2 becomes null, Device PE2 is isolated from the core. This can cause a null route at Device PE2. To prevent this situation, the LAG interface of Device PE2 that is facing Device CE2 is changed from the active state to the standby state by LACP.
-
An out-of-sync notification is sent from LACP on the attached multihomed CE2 link to block traffic transmission between Device CE2 and Device PE2.
-
When the control plane recovers, that is when Device PE2 establishes BGP session with other EVPN PEs, the LAG interface of Device PE2 is switched back from standby to active by LACP.
Configuration
CLI Quick Configuration
To quickly configure this example, copy the following commands, paste them into a
text file, remove any line breaks, change any details necessary to match your
network configuration, copy and paste the commands into the CLI at the
[edit] hierarchy level, and then enter
commit from configuration mode.
Device CE1
set interfaces ge-0/0/0 vlan-tagging set interfaces ge-0/0/0 mac 00:00:00:00:00:01 set interfaces ge-0/0/0 unit 0 vlan-id 100 set interfaces ge-0/0/0 unit 0 family inet address 192.0.2.1/26 set interfaces lo0 unit 0 family inet address 10.255.255.8/32
Device CE2
set chassis aggregated-devices ethernet device-count 1 set interfaces ge-0/0/0 gigether-options 802.3ad ae0 set interfaces ge-0/0/1 gigether-options 802.3ad ae0 set interfaces ae0 flexible-vlan-tagging set interfaces ae0 encapsulation flexible-ethernet-services set interfaces ae0 mac 00:00:00:00:00:03 set interfaces ae0 aggregated-ether-options lacp active set interfaces ae0 unit 0 vlan-id 100 set interfaces ae0 unit 0 family inet address 192.0.2.2/26 set interfaces lo0 unit 0 family inet address 10.255.255.9/32
Device PE1
set interfaces ge-0/0/0 vlan-tagging set interfaces ge-0/0/0 encapsulation flexible-ethernet-services set interfaces ge-0/0/0 unit 0 encapsulation vlan-bridge set interfaces ge-0/0/0 unit 0 vlan-id 100 set interfaces ge-0/0/1 unit 0 family inet address 192.0.2.65/26 set interfaces ge-0/0/1 unit 0 family iso set interfaces ge-0/0/1 unit 0 family mpls set interfaces lo0 unit 0 family inet address 10.255.255.1/32 set routing-options router-id 10.255.255.1 set routing-options autonomous-system 65100 set routing-options forwarding-table chained-composite-next-hop ingress evpn set protocols mpls interface all set protocols mpls interface fxp0.0 disable set protocols mpls interface ge-0/0/1.0 set protocols bgp local-address 10.255.255.1 set protocols bgp family inet unicast set protocols bgp group ibgp type internal set protocols bgp group ibgp local-address 10.255.255.1 set protocols bgp group ibgp family evpn signaling set protocols bgp group ibgp neighbor 10.255.255.2 set protocols bgp group ibgp neighbor 10.255.255.3 set protocols ospf area 0.0.0.0 interface all set protocols ospf area 0.0.0.0 interface fxp0.0 disable set protocols ospf area 0.0.0.0 interface lo0.0 passive set protocols ospf area 0.0.0.0 interface ge-0/0/1.0 set protocols ldp interface ge-0/0/1.0 set protocols ldp interface all set protocols ldp interface fxp0.0 disable set protocols ldp interface lo0.0 set routing-instances ALPHA instance-type evpn set routing-instances ALPHA vlan-id 100 set routing-instances ALPHA interface ge-0/0/0.0 set routing-instances ALPHA route-distinguisher 10.255.255.1:100 set routing-instances ALPHA vrf-target target:65100:100 set routing-instances ALPHA protocols evpn label-allocation per-instance set policy-options policy-statement load_balance then load-balance per-packet set routing-options forwarding-table export load_balance
Device PE2
set chassis aggregated-devices ethernet device-count 1 set interfaces ge-0/0/0 unit 0 family inet address 172.16.0.2/24 set interfaces ge-0/0/0 unit 0 family iso set interfaces ge-0/0/0 unit 0 family mpls set interfaces ge-0/0/1 gigether-options 802.3ad ae0 set interfaces ge-0/0/2 unit 0 family inet address 203.0.113.2/24 set interfaces ge-0/0/2 unit 0 family iso set interfaces ge-0/0/2 unit 0 family mpls set interfaces ae0 vlan-tagging set interfaces ae0 encapsulation flexible-ethernet-services set interfaces ae0 esi 00:11:22:33:44:55:66:77:88:99 set interfaces ae0 esi all-active set interfaces ae0 aggregated-ether-options lacp active set interfaces ae0 aggregated-ether-options lacp system-id 00:01:02:03:04:05 set interfaces ae0 unit 0 encapsulation vlan-bridge set interfaces ae0 unit 0 vlan-id 100 set interfaces lo0 unit 0 family inet address 10.255.255.2/32 set routing-options router-id 10.255.255.2 set routing-options autonomous-system 65100 set routing-options forwarding-table chained-composite-next-hop ingress evpn set protocols mpls interface all set protocols mpls interface fxp0.0 disable set protocols bgp local-address 10.255.255.2 set protocols bgp family inet unicast set protocols bgp family l2vpn signaling set protocols bgp group ibgp type internal set protocols bgp group ibgp local-address 10.255.255.2 set protocols bgp group ibgp family evpn signaling set protocols bgp group ibgp neighbor 10.255.255.3 set protocols bgp group ibgp neighbor 10.255.255.1 set protocols ospf area 0.0.0.0 interface all set protocols ospf area 0.0.0.0 interface fxp0.0 disable set protocols ospf area 0.0.0.0 interface lo0.0 passive set protocols ldp interface all set protocols ldp interface fxp0.0 disable set protocols ldp interface lo0.0 set routing-instances ALPHA instance-type evpn set routing-instances ALPHA vlan-id 100 set routing-instances ALPHA interface ae0.0 set routing-instances ALPHA route-distinguisher 10.255.255.2:100 set routing-instances ALPHA vrf-target target:65100:100 set policy-options policy-statement load_balance then load-balance per-packet set routing-options forwarding-table export load_balance
Device PE3
set chassis aggregated-devices ethernet device-count 1 set interfaces ge-0/0/0 gigether-options 802.3ad ae0 set interfaces ge-0/0/1 unit 0 family inet address 198.51.100.2/24 set interfaces ge-0/0/1 unit 0 family iso set interfaces ge-0/0/1 unit 0 family mpls set interfaces ge-0/0/2 unit 0 family inet address 203.0.113.1/24 set interfaces ge-0/0/2 unit 0 family iso set interfaces ge-0/0/2 unit 0 family mpls set interfaces ae0 vlan-tagging set interfaces ae0 encapsulation flexible-ethernet-services set interfaces ae0 esi 00:11:22:33:44:55:66:77:88:99 set interfaces ae0 esi all-active set interfaces ae0 aggregated-ether-options lacp active set interfaces ae0 aggregated-ether-options lacp system-id 00:01:02:03:04:05 set interfaces ae0 unit 0 encapsulation vlan-bridge set interfaces ae0 unit 0 vlan-id 100 set interfaces lo0 unit 0 family inet address 10.255.255.3/32 set routing-options router-id 10.255.255.3 set routing-options autonomous-system 65100 set routing-options forwarding-table chained-composite-next-hop ingress evpn set protocols mpls interface all set protocols mpls interface fxp0.0 disable set protocols bgp local-address 10.255.255.3 set protocols bgp family inet unicast set protocols bgp group ibgp type internal set protocols bgp group ibgp local-address 10.255.255.3 set protocols bgp group ibgp family evpn signaling set protocols bgp group ibgp neighbor 10.255.255.2 set protocols bgp group ibgp neighbor 10.255.255.1 set protocols bgp group l2vpn type internal set protocols bgp group l2vpn family l2vpn signaling set protocols bgp group l2vpn neighbor 10.255.255.4 set protocols ospf area 0.0.0.0 interface all set protocols ospf area 0.0.0.0 interface fxp0.0 disable set protocols ospf area 0.0.0.0 interface lo0.0 passive set protocols ldp interface all set protocols ldp interface fxp0.0 disable set protocols ldp interface lo0.0 set routing-instances ALPHA instance-type evpn set routing-instances ALPHA vlan-id 100 set routing-instances ALPHA interface ae0.0 set routing-instances ALPHA route-distinguisher 10.255.255.3:100 set routing-instances ALPHA vrf-target target:65100:100 set policy-options policy-statement load_balance then load-balance per-packet set routing-options forwarding-table export load_balance
Device P
set interfaces ge-0/0/0 unit 0 family inet address 192.0.2.66/26 set interfaces ge-0/0/0 unit 0 family iso set interfaces ge-0/0/0 unit 0 family mpls set interfaces ge-0/0/1 unit 0 family inet address 172.16.0.1/24 set interfaces ge-0/0/1 unit 0 family iso set interfaces ge-0/0/1 unit 0 family mpls set interfaces ge-0/0/2 unit 0 family inet address 198.51.100.1/24 set interfaces ge-0/0/2 unit 0 family iso set interfaces ge-0/0/2 unit 0 family mpls set interfaces lo0 unit 0 family inet address 10.255.255.4/32 set routing-options router-id 10.255.255.4 set routing-options autonomous-system 100 set protocols rsvp interface all aggregate set protocols mpls interface ge-0/0/0.0 set protocols mpls interface ge-0/0/1.0 set protocols mpls interface ge-0/0/2.0 set protocols bgp group l2vpn type internal set protocols bgp group l2vpn local-address 10.255.255.4 set protocols bgp group l2vpn family l2vpn signaling set protocols bgp group l2vpn neighbor 10.255.255.3 set protocols ospf area 0.0.0.0 interface lo0.0 passive set protocols ospf area 0.0.0.0 interface ge-0/0/0.0 set protocols ospf area 0.0.0.0 interface ge-0/0/1.0 set protocols ospf area 0.0.0.0 interface ge-0/0/2.0 set protocols ldp interface all set routing-instances vpls1 instance-type vpls set routing-instances vpls1 route-distinguisher 10.255.255.4:100 set routing-instances vpls1 vrf-target target:200:200 set routing-instances vpls1 protocols vpls no-tunnel-services set routing-instances vpls1 protocols vpls site vpls-pe site-identifier 3 set routing-instances vpls1 protocols vpls site vpls-pe best-site set policy-options policy-statement load_balance then load-balance per-packet set routing-options forwarding-table export load_balance
Procedure
Step-by-Step Procedure
The following example requires that you navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the CLI User Guide.
To configure Device PE2:
Repeat this procedure for other multihomed PE devices after modifying the appropriate interface names, addresses, and other parameters.
-
Specify the number of aggregated Ethernet interfaces to be created on Device PE2.
[edit chassis] user@PE2# set aggregated-devices ethernet device-count 1
-
Configure Device PE2 interfaces that connect to Device P and Device PE3, respectively.
[edit interfaces] user@PE2# set ge-0/0/0 unit 0 family inet address 172.16.0.2/24 user@PE2# set ge-0/0/0 unit 0 family iso user@PE2# set ge-0/0/0 unit 0 family mpls user@PE2# set ge-0/0/2 unit 0 family inet address 203.0.113.2/24 user@PE2# set ge-0/0/2 unit 0 family iso user@PE2# set ge-0/0/2 unit 0 family mpls
-
Configure Device PE2 interfaces within the ae0 aggregated bundle toward the multihomed Device CE2.
[edit interfaces] user@PE2# set ge-0/0/1 gigether-options 802.3ad ae0 user@PE2# set ae0 vlan-tagging user@PE2# set ae0 encapsulation flexible-ethernet-services user@PE2# set ae0 unit 0 encapsulation vlan-bridge user@PE2# set ae0 unit 0 vlan-id 100
-
Configure active-active multihoming on the aggregated Ethernet interface.
[edit interfaces] user@PE2# set ae0 esi 00:11:22:33:44:55:66:77:88:99 user@PE2# set ae0 esi all-active
-
Configure LACP on the CE-PE link of Device PE2.
[edit interfaces] user@PE2# set ae0 aggregated-ether-options lacp active user@PE2# set ae0 aggregated-ether-options lacp system-id 00:01:02:03:04:05
-
Configure the loopback interface of Device PE2.
[edit interfaces] user@PE2# set lo0 unit 0 family inet address 10.255.255.2/32
-
Configure the router ID and autonomous system number for Device PE2.
[edit routing-options] user@PE2# set router-id 10.255.255.2 user@PE2# set autonomous-system 65100
-
Enable chained composite next hop for EVPN on Device PE2.
[edit routing-options] user@PE2# set forwarding-table chained-composite-next-hop ingress evpn
-
Configure MPLS on all the interfaces of Device PE2, excluding the management interface.
[edit protocols] user@PE2# set mpls interface all user@PE2# set mpls interface fxp0.0 disable
-
Configure an internal BGP group for Device PE1 to peer with the other EVPN PE devices.
[edit protocols] user@PE2# set bgp local-address 10.255.255.2 user@PE2# set bgp family inet unicast user@PE2# set bgp family l2vpn signaling user@PE2# set bgp group ibgp type internal user@PE2# set bgp group ibgp local-address 10.255.255.2 user@PE2# set bgp group ibgp family evpn signaling user@PE2# set bgp group ibgp neighbor 10.255.255.3 user@PE2# set bgp group ibgp neighbor 10.255.255.1
-
Configure OSPF and LDP on all the interfaces of Device PE2, excluding the management interface.
[edit protocols] user@PE2# set ospf area 0.0.0.0 interface all user@PE2# set ospf area 0.0.0.0 interface fxp0.0 disable user@PE2# set ospf area 0.0.0.0 interface lo0.0 passive user@PE2# set ldp interface all user@PE2# set ldp interface fxp0.0 disable user@PE2# set ldp interface lo0.0
-
Configure an EVPN routing instance on Device PE2 and assign the routing instance parameters.
[edit routing-instances] user@PE2# set ALPHA instance-type evpn user@PE2# set ALPHA vlan-id 100 user@PE2# set ALPHA interface ae0.0 user@PE2# set ALPHA route-distinguisher 10.255.255.2:100 user@PE2# set ALPHA vrf-target target:65100:100
-
Create and apply an ECMP load balancing policy.
[edit] user@PE2# set policy-options policy-statement load_balance then load-balance per-packet user@PE2# set routing-options forwarding-table export load_balance
Results
From configuration mode, confirm your configuration by entering the
show chassis, show interfaces,
show routing-options, show protocols,
and show routing-instances commands. If the output does not
display the intended configuration, repeat the instructions in this example
to correct the configuration.
user@PE2# show chassis
aggregated-devices {
ethernet {
device-count 1;
}
}
user@PE2# show interfaces
ge-0/0/0 {
unit 0 {
family inet {
address 172.16.0.2/24;
}
family iso;
family mpls;
}
}
ge-0/0/1 {
gigether-options {
802.3ad ae0;
}
}
ge-0/0/2 {
unit 0 {
family inet {
address 203.0.113.2/24;
}
family iso;
family mpls;
}
}
ae0 {
vlan-tagging;
encapsulation flexible-ethernet-services;
esi {
00:11:22:33:44:55:66:77:88:99;
all-active;
}
aggregated-ether-options {
lacp {
active;
system-id 00:01:02:03:04:05;
}
}
unit 0 {
encapsulation vlan-bridge;
vlan-id 100;
}
}
lo0 {
unit 0 {
family inet {
address 10.255.255.2/32;
}
}
}
user@PE2# show routing-options
router-id 10.255.255.2;
autonomous-system 65100;
forwarding-table {
export load_balance;
chained-composite-next-hop {
ingress {
evpn;
}
}
}
user@PE2# show protocols
mpls {
interface all;
interface fxp0.0 {
disable;
}
}
bgp {
local-address 10.255.255.2;
family inet {
unicast;
}
family l2vpn {
signaling;
}
group ibgp {
type internal;
local-address 10.255.255.2;
family evpn {
signaling;
}
neighbor 10.255.255.3;
neighbor 10.255.255.1;
}
}
ospf {
area 0.0.0.0 {
interface all;
interface fxp0.0 {
disable;
}
interface lo0.0 {
passive;
}
}
}
ldp {
interface all;
interface fxp0.0 {
disable;
}
interface lo0.0;
}
user@PE2# show routing-instances
ALPHA {
instance-type evpn;
vlan-id 100;
interface ae0.0;
route-distinguisher 10.255.255.2:100;
vrf-target target:65100:100;
protocols {
evpn {
traceoptions {
file evpn-alpha.txt size 4294967295;
flag all;
}
}
}
}
user@PE2# show policy-options
then {
load-balance per-packet;
}
}
If you are done configuring the device, enter commit from
configuration mode.
Procedure
Step-by-Step Procedure
The following example requires that you navigate various levels in the configuration hierarchy. For information about navigating the CLI, see Using the CLI Editor in Configuration Mode in the CLI User Guide.
To configure Device CE2:
Repeat this procedure for other multihomed CE devices after modifying the appropriate interface names, addresses, and other parameters.
-
Specify the number of aggregated Ethernet interfaces to be created on Device CE2.
[edit chassis] user@CE2# set aggregated-devices ethernet device-count 1
-
Configure Device CE2 interfaces within the ae0 aggregated bundle toward Device PE2 and Device PE3.
[edit interfaces] user@CE2# set ge-0/0/0 gigether-options 802.3ad ae0 user@CE2# set ge-0/0/1 gigether-options 802.3ad ae0 user@CE2# set ae0 flexible-vlan-tagging user@CE2# set ae0 encapsulation flexible-ethernet-services user@E2# set ae0 mac 00:00:00:00:00:03 user@E2# set ae0 unit 0 vlan-id 100 user@CE2# set ae0 unit 0 family inet address 192.0.2.2/26
-
Configure LACP on the CE-PE links on Device CE2.
[edit interfaces] user@CE2# set ae0 aggregated-ether-options lacp active
-
Configure the loopback interface of Device CE2.
[edit interfaces] user@CE2# set interfaces lo0 unit 0 family inet address 10.255.255.9/32
Results
From configuration mode, confirm your configuration by entering the
show chassis, show interfaces,
show routing-options, show protocols,
and show routing-instances commands. If the output does not
display the intended configuration, repeat the instructions in this example
to correct the configuration.
user@CE2# show chassis
aggregated-devices {
ethernet {
device-count 1;
}
}
user@CE2# show interfaces
ge-0/0/0 {
gigether-options {
802.3ad ae0;
}
}
ge-0/0/1 {
gigether-options {
802.3ad ae0;
}
}
ae0 {
flexible-vlan-tagging;
encapsulation flexible-ethernet-services;
mac 00:00:00:00:00:03;
aggregated-ether-options {
lacp {
active;
}
}
unit 0 {
vlan-id 100;
family inet {
address 192.0.2.2/26;
}
}
}
lo0 {
unit 0 {
family inet {
address 10.255.255.9/32;
}
}
}
If you are done configuring the device, enter commit from
configuration mode.
Verification
Confirm that the configuration is working properly.
- Verifying BGP Session Status
- Verifying LACP Interface Status of Multihomed PE Device
- Verifying LACP Interface State of Isolated PE Device
- Verifying EVPN Routing Instance
Verifying BGP Session Status
Purpose
Verify that Device PE2 has established BGP peering with other EVPN PE devices.
Action
From operational mode, run the show bgp summary command.
user@PE2> show bgp summary
Groups: 1 Peers: 2 Down peers: 0
Table Tot Paths Act Paths Suppressed History Damp State Pending
inet.0
0 0 0 0 0 0
bgp.l2vpn.0
0 0 0 0 0 0
bgp.evpn.0
5 5 0 0 0 0
Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
10.255.255.1 65100 6316 6333 0 0 1d 23:33:03 Establ
bgp.evpn.0: 1/1/1/0
ALPHA.evpn.0: 1/1/1/0
__default_evpn__.evpn.0: 0/0/0/0
10.255.255.3 65100 6318 6332 0 0 1d 23:32:56 Establ
bgp.evpn.0: 4/4/4/0
ALPHA.evpn.0: 3/3/3/0
__default_evpn__.evpn.0: 1/1/1/0Meaning
Device PE2 has established BGP peering with the other EVPN PE devices—Device PE1 and Device PE3.
Verifying LACP Interface Status of Multihomed PE Device
Purpose
Verify the LACP interface state on Device PE2.
Action
From operational mode, run the show lacp interfaces and show interfaces ae* terse commands.
user@PE2> show lacp interfaces
Aggregated interface: ae0
LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity
ge-0/0/1 Actor No No Yes Yes Yes Yes Fast Active
ge-0/0/1 Partner No No Yes Yes Yes Yes Fast Active
LACP protocol: Receive State Transmit State Mux State
ge-0/0/1 Current Fast periodic Collecting distributinguser@PE2> show interfaces ae* terse Interface Admin Link Proto Local Remote ae0 up up ae0.0 up up bridge ae0.32767 up up multiservice
Meaning
The LACP LAG interface state is active when there is BGP peering with other EVPN PE devices. The physical interface state of the aggregated Ethernet interfaces are up and operational.
Verifying LACP Interface State of Isolated PE Device
Purpose
Verify the LACP interface state of Device PE2 when no BGP EVPN peers have been established.
Action
From operational mode, run the show lacp interfaces and show interfaces ae* terse commands.
user@PE2> show lacp interfaces
Aggregated interface: ae0
LACP state: Role Exp Def Dist Col Syn Aggr Timeout Activity
ge-0/0/1 Actor No No No No No Yes Fast Active
ge-0/0/1 Partner No No No No Yes Yes Fast Active
LACP protocol: Receive State Transmit State Mux State
ge-0/0/1 Current Fast periodic Waitinguser@PE2> show interfaces ae* terse Interface Admin Link Proto Local Remote ae0 up down ae0.0 up down bridge ae0.32767 up down multiservice
Meaning
Because of core isolation, the LAG interface state is in standby, blocking traffic to-and-from Device CE2. As a result, the physical interface state of the aggregated Ethernet interface is also down until the LACP link state switches back to active on core failure recovery.
Verifying EVPN Routing Instance
Purpose
Verify the EVPN routing instance parameters on Device PE2.
Action
From operational mode, run the show evpn instance extensive command.
user@PE2> show evpn instance extensive
Instance: ALPHA
Route Distinguisher: 10.255.255.2:100
VLAN ID: 100
Per-instance MAC route label: 299776
MAC database status Local Remote
MAC advertisements: 0 0
MAC+IP advertisements: 0 0
Default gateway MAC advertisements: 0 0
Number of local interfaces: 1 (1 up)
Interface name ESI Mode Status
ae0.0 00:11:22:33:44:55:66:77:88:99 all-active Up
Number of IRB interfaces: 0 (0 up)
Number of bridge domains: 1
VLAN Domain ID Intfs / up IRB intf Mode MAC sync IM route label
100 1 1 Extended Enabled 300048
Number of neighbors: 2
Address MAC MAC+IP AD IM ES
10.255.255.1 0 0 0 1 0
10.255.255.3 0 0 2 1 0
Number of ethernet segments: 1
ESI: 00:11:22:33:44:55:66:77:88:99
Status: Resolved by IFL ae0.0
Local interface: ae0.0, Status: Up/Forwarding
Number of remote PEs connected: 1
Remote PE MAC label Aliasing label Mode
10.255.255.3 0 299856 all-active
Designated forwarder: 10.255.255.2
Backup forwarder: 10.255.255.3
Last designated forwarder update: Nov 21 01:27:52
Advertised MAC label: 299856
Advertised aliasing label: 299856
Advertised split horizon label: 299968
Instance: __default_evpn__
Route Distinguisher: 10.255.255.2:0
Number of bridge domains: 0
Number of neighbors: 1
Address MAC MAC+IP AD IM ES
10.255.255.3 0 0 0 0 1Meaning
The output provides the following information:
EVPN routing instance
Mode of operation of each interface
Neighbors of the routing instance
Number of different routes received from each neighbor
ESI attached to the routing instance
Number of Ethernet segments on the routing instance
Designated forwarder (DF) election roles for each ESI in an EVPN instance (EVI)
VLAN ID and MAC labels for the routing instance