Re: Which use case / situation need this config in MC-LAG setup?
[ Edited ]
So it means if i'm using MX with version 18.x then that knob dont need right? Also i check with KB info that u mention. It's look like if i configure VRRP then that knob dont need anymore right? Please correct me if i wrong.
Greetings gentleman, your understanding is correct, from 15.1R3/16.1R1, mc-lag does not need static entry (ARP/NDP) for remote IRB, this will overcome the ICL arp reply limitation.
If you already configured the static entry(ARP/NDP) and then try to remove it on any version higher than 15.1, remote IRB arp resolution will not happen automatically due to the static programming that was in place before, in order to solve this problem you will have to reconfigure the IRB & restart l2-learning process on both the MC-LAG peers.
root#delete interface irb.123 root#commit root#rollback 1 commit root# run restart l2-learning Layer 2 address flooding and learning process started, pid 12435
If this solves your problem, please mark this post as "Accepted Solution" so we can help others too \:)/
Lil Dexx JNCIE-ENT#863, 3X JNCIP-[SP-ENT-DC], 4X JNCIA [cloud-DevOps-Junos-Design], Champions Ingenius, SSYB