After rebooting the windows VM will get duplicate IP conflict issue in EVPN-VXLAN environments under some random Vlans when you configure the PIP interface for the EVPN traffics.
The system detected an address conflict for IP address 0.0.0.0 with the system having network hardware address C8-E7-F0-B8-B6-E0. Network operations on this system may be disrupted as a result.
Triggers of this issue:
We can try the below command under the specific vlans when we are not in MW.
We have below options for the Workaround:
evo:20.4R3-S7-EVO evo:21.4R3-EVO evo:22.1R3-EVO evo:22.2R2-EVO evo:22.3R1-EVO evo:22.4R1-EVO junos:20.4R3-S7 junos:21.4R3 junos:22.1R3 junos:22.2R2 junos:22.3R1 junos:22.4R1
Public PR: PR1427109 :: https://prsearch.juniper.net/problemreport/PR1427109