As I understand it, this is because ARP learning is handled by EVPN (including aging) and not the normal ARP handling mechanism.
Marking it as permanent in the ARP table prevents race conditions between EVPN and normal ARP processing. EVPN will delete the permanent entry when the mac-ip entry ages out of the EVPN table (whether it was learned locally or from a remote device). -- Eldon On Sun, Dec 13, 2020, 20:43 Chen Jiang <iloveb...@gmail.com> wrote: > Hi! Experts > > Sorry for disturbing, I am curious why local learned ARP in EVPN also has > "permanent remote" flags? if it is learned from remote VTEP then makes > sense, cause it is learned from BGP. but why local learned ARP also has > these flags. > > lab@qfx5110> show arp no-resolve > MAC Address Address Interface Flags > fe:00:00:00:00:80 128.0.0.16 bme0.0 permanent > 84:b5:9c:ce:b9:71 192.168.0.0 xe-0/0/46.0 none > b8:c2:53:ad:e1:03 192.168.1.1 em2.32768 none > 7e:13:0b:56:e5:c0 192.168.1.16 em2.32768 none > 5c:5e:ab:6b:d5:81 192.168.5.1 em0.0 none > 64:87:88:b8:55:43 192.168.100.10 irb.100 [ae1.0] permanent remote > > Thanks for your help. > > -- > BR! > > > > James Chen > _______________________________________________ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp