Possible causes for an IPv6 address conflict on an interface

31

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.

Other related questions:
Possible causes for a failure to ping an IPv6 address
In V100R002 and later versions, the IPv6 address of a device fails to be pinged due to the following possible causes: l. The physical state or protocol state of the interface is Down. You can run the display ipv6 interface interface-type interface-number command in any view to check the physical state and protocol state of an interface. 2. The switch fails to learn ND entries of the peer device. You can run the display ipv6 neighbors command in any view to check information about ND entries. 3. The link transmission delay is too long. The source device does not receive any Response packet from the destination device within the waiting time, and the ping operation fails. You can run the ping ipv6 -t timeout destination-ipv6-address command in any view to set “-t&rdquo to increase the timeout interval for waiting for Response packets.

How to clear MAC address flapping alarms on an AC
The possible causes for MAC address flapping alarms are as follows: - The interfaces where a loop occurs are added to the same VLAN. - Cables are connected incorrectly. - A loop occurs on the network. Troubleshooting procedure: 1. Connect cables on the interfaces correctly and check whether the alarm persists. If so, go to step 2. If not, go to step 6. 2. Check whether the two interfaces that learn the same MAC address can be added to different VLANs based on the network topology. If yes, go to step 3. If not, go to step 4. 3. Add the two interfaces to different VLANs, and check whether the alarm persists. If so, go to step 4. If not, go to step 6. 4. Disable loop detection and enable STP. Check whether the alarm persists. If so, go to step 5. If not, go to step 6. 5. Contact Huawei technical personnel. 6. End.

When prompted to configure NAT Server,AR router report ARP conflict or interface conflict ?
When configure NAT Server, if use the network interface IP address, there may be the following configuration error. [AR2200-GigabitEthernet0/0/1] IP 22.1.1.1 address 24 [AR2200-GigabitEthernet0/0/1] NAT protocol 80 global inside 22.1.1.1 10.1.1.1 server Error: The conflicts with or ARP interface address IP. At this time, need to configure NAT server command when the network port IP address to current-interface, as follows: [AR2200-GigabitEthernet0/0/1] NAT protocol 80 global inside current-interface 10.1.1.1 server

Possible causes of an OSNR decrease
The possible causes are as follows: Possible cause 1: Any fiber pigtail in a multiplexing part or the optical cable degrades or is physically damaged. As a result, the attenuation of the fiber increases, and the receive optical power decline causes an OSNR decrease. Possible cause 2: The OA board gain at the local or peer site is decreased.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top