This article explains the abnormal behaviour of ACX device when active active EVPN setup is configured with ELP.

The routing table says to send traffic via the core link but the forwarding table still points out the interface that is down. 

Again the forwarding table still points to the local Access interface, which is down, even though the routing table is correctly sending the traffic via the EVPN Overlay to the other Leaf swtch. 

The issue is seen in 26.2R1 as I still see the ACX Leaf node pointing its forwarding entry out the local interface which is down. 
 
MAC forwarding entry points out local ae105.2003 interface
remote1@TIPT-Leaf2> show route forwarding-table vpn V302048R destination 00:00:4b:88:86:e6 
Routing table: V302048R.vpls
VPLS:
Destination        Type RtRef Next hop           Type Index    NhRef Netif
00:00:4b:88:86:e6/48 user     0                  ucst    11033     1 ae105.2003
 
This interface is DOWN though, therefore shouldn't be used
remote1@TIPT-Leaf2> show interfaces ae105.2003 
  Logical interface ae105.2003 (Index 3335) (SNMP ifIndex 554)
    Description: EVPN VLAN 2003
    Flags: SNMP-Traps CCC-Down VLAN-Tag[ 0x8100.2003 ]  Encapsulation: vlan-bridge
          , Source address: None, Destination address: None,
    Statistics        Packets        pps         Bytes          bps
    Bundle:
        Input :             0          0             0            0
        Output:         97095          0      81504984            0
    Protocol ethernet-switching, MTU: 9192
      Flags: None
 
The route table correctly points over the ae3.0 "Core link" 
remote1@TIPT-Leaf2> show route table V302048R.evpn.0 match-prefix 2:144.133.144.250:2001::2003::00:00:4b:88:86:e6
 
V302048R.evpn.0: 8358 destinations, 8358 routes (8358 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
 
2:144.133.144.250:2001::2003::00:00:4b:88:86:e6/304 MAC/IP        
                   *[BGP/170] 00:03:55, localpref 100, from 144.133.144.250
                      AS path: I, validation-state: unverified
>  to 172.16.1.0 via ae3.0, Push 26
                       to 172.16.2.1 via ae2.0, Push 26, Push 500250(top)
 

ELP is not supported for Active/Standy ESI, Checked with Engineering and got confirmation for the same as below:

We have RLI 38256 to support ELP for EVPN A/A. FS section 2.0.2 mentions it.

2.0.2 EVPN Active/Standby:

Due to tight schedule, we don’t support EVPN Active/Standby in this RLI. EVPN Active/Standby will be supported as needed in future RLIs.

We don’t have RLI to support ELP for A/S after RLI 38256 for EVPN A/A