This document describes log message -L2ALD_MAC_MOVE_NOTIF_ACTION and steps to resolve the issue.

Customer facing interface for vpls service was blocked.
We could see below logs for mac-move due to which vpls service went down.

Oct 12 02:03:40 2023 lab_re0 l2ald[26326]: L2ALD_MAC_MOVE_NOTIF_ACTION: MAC move action offending MAC: 00:00:00:17:00:0a, blocking ifl ae17.1217 for bd __Customer1.ELAN__ . 
Oct 12 02:03:40 2023 lab_re0 [26370]: SNMP_TRAP_LINK_DOWN: ifIndex 1534, ifAdminStatus up(1), ifOperStatus down(2), ifName ae17.1217

A MAC move occurs when a MAC address frequently appears on a different physical interface than the one it was learned on. Frequent MAC moves indicate the presence of loops. To avoid loops across interfaces in virtual private LAN services (VPLS), you can configure MAC pinning.
configure mac pinning on vpls interface.

When you enable MAC pinning on an interface in a bridge domain or VPLS domain, MAC addresses learned over that interface cannot be relearned on any other interface in the same bridge domain or VPLS domain until the MAC address either ages out on the first interface or is cleared from the MAC table. If a packet with the same MAC address arrives at any other interface in the same bridge domain, it is discarded. This, effectively, controls MAC address moves and prevents the creation of loops in Layer 2 bridges and VPLS domains.

Configuration on vpls interface under routing-instance:

set routing-instances <instance_name> protocols vpls interface <name> mac-pinning

For more information on mac-pinning please refer below document
https://www.juniper.net/documentation/us/en/software/junos/vpn-l2/topics/concept/mac-pinning-understanding.html

2023-10-12 : Initial draft
 

2023-1012-787006