I don’t know whether it is officially supported or not, but I was able to get
v6 working in a lab environment with MC-LAG, even with OSPF3 running and
working over it as well.
In v4 world you must configure VRRP to have the ARP sync work properly (this
bit us on a MC-LAG running OSPF where one would not expect to actually need
VRRP running), I suspect you may have to also configure VRRPv6 to have ND
entries sync properly.
below is snippet of IRB config of what worked in our lab — again, this was not
a production environment:
irb {
arp-l2-validate;
unit 1001 {
family inet {
mtu 1500;
address 192.168.1.3/24 {
arp 192.168.1.2 l2-interface ae0.0 mac 64:64:9b:4a:a5:00;
vrrp-group 1 {
virtual-address 192.168.1.1;
priority 100;
accept-data;
}
}
}
family inet6 {
mtu 1500;
address 2001:db8:0:1::3/64 {
ndp 2001:db8:0:1::2 l2-interface ae0.0 mac
64:64:9b:4a:a5:00;
vrrp-inet6-group 101 {
virtual-inet6-address 2001:db8:0:1::1;
priority 100;
accept-data;
}
}
address fe80::120e:7e03:e9b1:ab80/64 {
ndp fe80::6664:9b03:e94a:a500 l2-interface ae0.0 mac
64:64:9b:4a:a5:00;
}
}
}
Thanks,
Will
_______________________________________________
juniper-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/juniper-nsp
