Mailing List Archive: Dcd complains about duplicate IPv6 link-local address

Hello,

I've notice our M10 (running 5.4R3.2) generating the following log
entries (line wrapped):

dcd[535]: Warning: identical local address is found on route instance,
intf: at-0/0/0.200, family type: inet6

When I look at the interface addresses I see the following:

at-0/0/0.96 up up inet6 2001:708:310:722::2/64
fe80::2a0:a5ff:fe12:6601/64
at-0/0/0.200 up up inet6 2001:708:310:723::2/64
fe80::2a0:a5ff:fe12:6601/64
lo0.0 up up inet6 2001:708:310:100::2 --> ::/0
fe80::2a0:a5ff:fe12:6601--> ::/0

As it can be seen all the interfaces have identical link-local
addresses.

The relevant configuration of the ATM interface looks like this:

unit 96 {
encapsulation atm-snap;
vci 0.96;
inverse-arp;
family iso;
family inet6 {
address 2001:708:310:722::2/64;
}
}

unit 200 {
encapsulation atm-snap;
vci 0.200;
inverse-arp;
family iso;
family inet6 {
address 2001:708:310:723::2/64;
}
}

Is the log message only informational? Could there be some problems
waiting to turn up later and the cause would be this one? I couldn't
find anything special with Google so I decided to ask here, too.

--
- Matti -

Matti,
this is just a warning and will not cause you
any troubles. In version 5.5 and higher we don't send
such warnings in this case as the link-local address
will be the same for all logical links for one atm-interface.

thanks
Josef

At 08:48 AM 1/13/2003, Matti Saarinen wrote:

>Hello,
>
>I've notice our M10 (running 5.4R3.2) generating the following log
>entries (line wrapped):
>
>dcd[535]: Warning: identical local address is found on route instance,
>intf: at-0/0/0.200, family type: inet6
>
>
>When I look at the interface addresses I see the following:
>
>at-0/0/0.96 up up inet6 2001:708:310:722::2/64
> fe80::2a0:a5ff:fe12:6601/64
>at-0/0/0.200 up up inet6 2001:708:310:723::2/64
> fe80::2a0:a5ff:fe12:6601/64
>lo0.0 up up inet6 2001:708:310:100::2 --> ::/0
> fe80::2a0:a5ff:fe12:6601--> ::/0
>
>
>As it can be seen all the interfaces have identical link-local
>addresses.
>
>The relevant configuration of the ATM interface looks like this:
>
>
>unit 96 {
> encapsulation atm-snap;
> vci 0.96;
> inverse-arp;
> family iso;
> family inet6 {
> address 2001:708:310:722::2/64;
> }
>}
>
>unit 200 {
> encapsulation atm-snap;
> vci 0.200;
> inverse-arp;
> family iso;
> family inet6 {
> address 2001:708:310:723::2/64;
> }
>}
>
>
>
>Is the log message only informational? Could there be some problems
>waiting to turn up later and the cause would be this one? I couldn't
>find anything special with Google so I decided to ask here, too.
>
>
>--
>- Matti -
>_______________________________________________
>juniper-nsp mailing list juniper-nsp@puck.nether.net
>http://puck.nether.net/mailman/listinfo/juniper-nsp