Possible causes for an IPv6 address conflict on an interface

In V100R002 and later versions, an IPv6 address conflict on an interface may be caused by the following
- The peer interface directly connected to this interface has been configured with the same IPv6 address as that of the interface.
- After the internal loopback detection function is enabled on an Ethernet interface, the IPv6 link-local address status of the interface is DUPLICATE, and the IPv6 global unicast address status of the interface is TENTATIVE (the address is a tentative address and have not passed the duplicate address detection). You can run the undo loopback command in the Ethernet interface view to disable the loopback detection mode on the interface.
- There is a loop on the network.
Note:
By default, a switch performs duplicate address detection after an IPv6 address is configured for an interface on the switch. You can run the display ipv6 interface interface-type interface-number command in any view to check whether the IPv6 address of an interface conflicts with another IPv6 address.

Scroll to top