[f-nsp] IPv6 on MLX stopped working

[Daniel Schmidt]

One of my BR-MLX-100Gx2-X ceased working in suspicious proximity to the fb
upgrade.

On Tue, Jun 16, 2015 at 9:50 AM, "Rolf Hanßen" <nsp at rhanssen.de> wrote:

> Hello Niels,
>
> you were right:
> ICMPv6-ND: DAD: duplicate address XXXX:XXXX:200:5::1 on port v1359
>
> The date matches a power outage in a DC, I moved the interface to the new
> router and the old kicked in after coming back.
>
> I am just wondering that the route keeps in place without an (active) IP
> in that network.
>
> Looks like I should use "ipv6 nd dad attempts 0" from now on. ;)
>
> kind regards
> Rolf
>
> > * nsp at rhanssen.de ("Rolf Hanßen") [Mon 15 Jun 2015, 16:56 CEST]:
> >>IPv6 stopped working for a ve interface, re-entering the IP solved it.
> >>As far as I see this affected only that interface/IP.
> >
> > There may have been a loop in the VLAN corresponding to that ve
> > interface, and DAD kicked in.  Removing and re-entering the IP address
> > generally makes the router do another round of DAD, and if the
> > duplicate address (i.e. the loop) is gone, then it will stick.
> >
> > So check your syslog, and whether the output of 'show ipv6 interface'
> > at the time of the breakage included anything about DAD.
> >
> >
> >       -- Niels.
> >
> > --
> > _______________________________________________
> > foundry-nsp mailing list
> > foundry-nsp at puck.nether.net
> > http://puck.nether.net/mailman/listinfo/foundry-nsp
> >
>
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/foundry-nsp
>

-- 

E-Mail to and from me, in connection with the transaction 
of public business, is subject to the Wyoming Public Records 
Act and may be disclosed to third parties.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/foundry-nsp/attachments/20150616/5bfe17dd/attachment.html>