The customer had 3 ACX7024 running 24.2-EVO software; 1 site is a spoke and 2 are hubs. The two hub sites are running a VPLS instance with a mesh group. The spoke site has a l2circuit going to each hub site. One of the hub sites vpls connections show as up. The other hub site vpls connection shows as an MI state (MI -- Mesh-Group ID not available)

Both l2circuits show as up on the spoke. Traffic will not pass through. MI state indicates that MESH group is not reporting any circuit-id associated.

Starting in Junos OS Evolved 23.4R1, when rebooting a node on EVO, the Layer 2 applications l2ald, l2ald-agent, l2cpd, and l2cpd-agent are initialized and started only if any of the following configuration hierarchy levels contain any configuration statements:

• [edit interface interface-name unit number family ethernet-switching]
• [edit vlans]
• [edit routing-instance instance-name instance-type virtual-switch]
• [edit routing-instance instance-name instance-type mac-vrf]
• [edit protocols l2-learning]

Additionally, l2cpd, and l2cpd-agent are initialized and started if the [edit protocols lldp] hierarchy level contains any configuration statements.

As a result of this change, if your configuration already contains these configuration statements and you then delete all of the above configuration statements, these Layer 2 applications stop running.

We found that after configuring the vpls-meshgroups knob under packet-forwarding-options the device reported some l2ald-agent alarms and was unable to bring the IFL up. For that reason, the VPLS MESH-group was not coming up and was reporting the MI state.

Avoid configuring the system-profile vpls-meshgroups if no L2 configuration is added to the system.

set system packet-forwarding-options system-profile vpls-meshgroups

commit

commit complete

vpls-meshgroups >>> option introduced in Junos OS Evolved Release 24.1R1 for ACX7100-32C, ACX7100-48L, ACX7332, ACX7348, ACX7509, ACX7024, and ACX7024 Routers.

Follow Chassis Alarms could be seen if previous action is performed:

Major Application l2ald-agent fail on node Re0

Major Application l2ald fail on node Re0

Major Application l2cpd-agent fail on node Re0

Major Application l2cpd fail on node Re0

Minor chassis No Redundant Power

Recovery:

We should reboot the router with >request node reboot re0. After this step, we can recovery and bring up the IFL interface associated to the H-VPLS Mesh group.

After this we can see that the VPLS connection changed from MI to UP state.