Customer might notice unexpected behavior of L2circuits and VPLS went down post changes made in EVPN instances without deactivating it.

Changes including VLAN modification/addition/deletion under EVPN Instance.

set routing-instances <Instance name> vlan-id none

All VPLS and L2 circuit went down post committing these changes.

Jan 22 00:11:35.326 2025 ROUTER-RE0 rpd[13165]: %DAEMON-5-RPD_LAYER2_VC_DOWN: State of Layer 2 VC (VPN : XXXX_10MB_L2VPN_ORSD-PGMB, local-site : 1, remote-site : 2) changed from UP to DELETED

Jan 22 00:11:35.524 2025 ROUTER-RE0 rpd[13165]: %DAEMON-5-RPD_LAYER2_VC_DOWN: State of Layer 2 VC (VPN : XXXX_EPLAN_VPLS, local-site : 1, remote-site : 5) changed from UP to DELETED

Jan 22 00:11:35.529 2025 ROUTER-RE0 rpd[13165]: %DAEMON-5-RPD_LAYER2_VC_DOWN: State of Layer 2 VC (VPN : ERC_NTP_L2VPN_XXXX_OSS, local-site : 1, remote-site : 2) changed from UP to DELETED

Some configuration changes can be what we call catastrophic if you perform them in an operating network, which means you might see small to significant disruption in network operation. Network disruption can include loss of connectivity among the network devices and traffic loss while the devices reconverge on changes to network information.

Changing the vlan-id on the fly, without first deactivating the associated EVPN routing instance would be catastrophic.

As a result, when you want to change an option in a routing instance where that option has the potential to impact traffic flow, make sure you use the following procedure to avoid traffic loss:

1. Deactivate the routing instance configuration.
2. Change the traffic impacting option.
3. Reactivate the updated routing instance configuration.