ND_1.3.6.1.4.1.2011.5.25.332.2.7 hwNDDuplicateIPv6

Trap Buffer Description

Received a [PktType] packet with a duplicate IP address [TgtIpv6Address] from the interface [TgtInterfaceName]. (ReceiveIfName=[LocInterfaceName], SourceMacAddress=[SrcMacAddress], DestinationMACAddress=[DstMacAddress], SourceAddress=[SrcIpv6Address], DestinationAddress=[DstIpv6Address], PE-VLAN=[PeVLAN], CE-VLAN=[CeVLAN], SelfMacRecv=[SelfLoop], Attempted=[DadAttempts])

This alarm occurred in the system if the IPv6 address on the interface of the local device was same with that of the peer direct device (devices on a same link).

Trap Attributes

Trap Attribute	Description
Alarm or Event	Alarm
Trap Severity	Critical
Mnemonic Code	ND_DUPLICATE_IPV6ADDR
Trap OID	1.3.6.1.4.1.2011.5.25.332.2.7
MIB	HUAWEI-ND-MIB
Alarm ID	0x00F10304
Alarm Name	ND_DUPLICATE_IPV6ADDR
Alarm Type	communicationsAlarm
Raise or Clear	Raise
Match trap	ND_1.3.6.1.4.1.2011.5.25.332.2.8 hwNDDuplicateIPv6Resume

Trap Buffer Parameters

Parameter	Description
PktType	Indicate the packet type in the received ND message.
TgtIpv6Address	Indicates the IPv6 address generating the alarm.
TgtInterfaceName	Indicates the name of the interface receiving the alarm.
LocInterfaceName	Indicates the name of the local interface receiving the alarm.
SrcMacAddress	Indicates the source MAC address in the received ND message.
DstMacAddress	Indicate the destination MAC address in the received ND message.
SrcIpv6Address	Indicate the source IPv6 address in the received ND message.
DstIpv6Address	Indicates the destination IPv6 address in the received ND message.
PeVLAN	Indicates the outer VLAN ID carried in the received ND message.
CeVLAN	InIndicates the inner VLAN ID carried in the received ND message.
SelfLoop	Indicate the self-loop flag in the received ND message.
DadAttempts	Indicate the attempted times in the received message.

VB Parameters

VB OID	VB Name	VB Index
1.3.6.1.4.1.2011.5.25.332.1.4.1.1	hwNDDulicatePktType	hwNDDulicatePktType hwNDDulicateTgtIPv6Addr hwNDDulicateTgtIf
1.3.6.1.4.1.2011.5.25.332.1.4.1.2	hwNDDulicateTgtIPv6Addr	hwNDDulicatePktType hwNDDulicateTgtIPv6Addr hwNDDulicateTgtIf
1.3.6.1.4.1.2011.5.25.332.1.4.1.3	hwNDDulicateTgtIf	hwNDDulicatePktType hwNDDulicateTgtIPv6Addr hwNDDulicateTgtIf
1.3.6.1.4.1.2011.5.25.332.1.4.1.4	hwNDDulicateLocalIf	hwNDDulicatePktType hwNDDulicateTgtIPv6Addr hwNDDulicateTgtIf
1.3.6.1.4.1.2011.5.25.332.1.4.1.5	hwNDDulicateSrcMAC	hwNDDulicatePktType hwNDDulicateTgtIPv6Addr hwNDDulicateTgtIf
1.3.6.1.4.1.2011.5.25.332.1.4.1.6	hwNDDulicateDstMAC	hwNDDulicatePktType hwNDDulicateTgtIPv6Addr hwNDDulicateTgtIf
1.3.6.1.4.1.2011.5.25.332.1.4.1.7	hwNDDulicateSrcIPv6Addr	hwNDDulicatePktType hwNDDulicateTgtIPv6Addr hwNDDulicateTgtIf
1.3.6.1.4.1.2011.5.25.332.1.4.1.8	hwNDDulicateDstIPv6Addr	hwNDDulicatePktType hwNDDulicateTgtIPv6Addr hwNDDulicateTgtIf
1.3.6.1.4.1.2011.5.25.332.1.4.1.9	hwNDDulicatePeVLAN	hwNDDulicatePktType hwNDDulicateTgtIPv6Addr hwNDDulicateTgtIf
1.3.6.1.4.1.2011.5.25.332.1.4.1.10	hwNDDulicateCeVLAN	hwNDDulicatePktType hwNDDulicateTgtIPv6Addr hwNDDulicateTgtIf
1.3.6.1.4.1.2011.5.25.332.1.4.1.11	hwNDDulicateSelfLoop	hwNDDulicatePktType hwNDDulicateTgtIPv6Addr hwNDDulicateTgtIf
1.3.6.1.4.1.2011.5.25.332.1.4.1.12	hwNDDulicateDadAttempts	hwNDDulicatePktType hwNDDulicateTgtIPv6Addr hwNDDulicateTgtIf

Impact on the System

If the alarm is generated, it indicates that there exists a conflicting IPv6 address between the local device and peer direct device (devices on a same link). If the conflict is not cleared in time, service or traffic interruptions may occur.

Possible Causes

The IPv6 address of the local interface is the same as an existing IPv6 address on the network.

Procedure

1.According to network planning and service deployment, query the peer directly-connected device based on the MAC address in the alarm. Then, run the display this ipv6 interface command to query the IPv6 address of the interface.

If the IPv6 address of the peer interface is the same as that of the local interface, go to 2.
If the IPv6 address of the peer interface is different from that of the local interface, go to 3.
If information about the peer device is not obtained, go to 4.

2.According to network planning and service deployment, modify the IPv6 address of the local interface and check whether the alarm is cleared.

Yes: The alarm handling is complete, and no further action is required.
No: Go to 5.

3.According to network planning and service deployment, check whether the IPv6 address of the local interface can be modified.

Yes: Go to 2.
No: Go to 4.

4.If the conflicting IPv6 address of the local interface is still required, run the undo shutdown command to change the administrative status of the local interface from Down to Up. Alternatively, run the undo ipv6 address command to delete the IPv6 address and then the ipv6 address command to add this address again. Trigger DAD and check whether an IPv6 address conflict exists.

Yes: Go to 5.
No: The alarm handling is complete, and no further action is required.

5.Collect alarm information and configuration information, and then contact technical support personnel.