After configuring a new vlan in evpn/vxlan setup, the servers in same vlan (newly added) are unable to communicate. The servers are able to reach the gateway.

The reachability between two servers in same vlan is not working after configuring a new vlan.

• It is ERB evpn/vxlan setup.
• After configuring a new vlan in evpn/vxlan setup, the servers in same vlan (newly added) are unable to communicate.
• The servers are able to ping the gateway configured on leaf switches.
• We could see the MAC and ARP entry for servers on LEAF switches.
• We could see the below logs on LEAF switches, after configuring the new vlan :

Apr 7 13:00:45 leaf-switch fpc0 BRCM-VIRTUAL,brcm_virtual_add_vlan_egress_rw(),1252:VLANRW EGRESS vlan-xlat port-classid alloc failed for ifl(xx) vlan(yy) ifd_name (zz) egr-xlat-vid(0)  

Apr 7 13:00:45 leaf-switch fpc0 BRCM-VIRTUAL,brcm_virtual_add_vlan_egress_rw(),1252:VLANRW EGRESS vlan-xlat port-classid alloc failed for ifl(xx) vlan(yy) ifd_name (zz) egr-xlat-vid(0)  

If we are observing the above logs, we are hitting the known PR : PR1691417.

Link : https://prsearch.juniper.net/problemreport/PR1691417

On QFX5K platforms with Virtual Extensible VLAN (VXLAN) configuration, when a new Virtual Local Area Network (VLAN) is added to the trunk, it is not getting added and traffic loss will be seen on the newly VLAN added port.
The issue state recovers after rebooting the device, however if the VLAN is removed and reconfigured on the interfaces then again the issue is observed.

The PR is resolved in below versions

21.2R3-S4, 21.2R3-S5, 21.3R3-S3, 21.3R3-S4

2026-09-30 : Externalized

PR LINK : https://prsearch.juniper.net/problemreport/PR1691417

Related Case : 2023-0410-673506