ARP/2/hwARPHostConflict_active

Message

ARP/2/hwARPHostConflict_active: The host access interface frequently changed. (LocalIPAddress=[LocalIP], LocalBDID=[LocalBDId], LocalMAC=[LocalMAC], RemoteIPAddress=[ConflictIP], RemoteBDID=[RemoteBDId], RemoteMAC=[RemoteMAC], LocalInterface=[LocalInterface], RemoteInterface=[RemoteInterface], TunnelPeer=[TunnelPeer])

Description

The host access interface frequently changed.

Parameters

Parameter Name	Parameter Meaning
LocalIP	Local IP address
LocalBDId	Local BD ID
LocalMAC	Local MAC address
ConflictIP	Remote IP address
RemoteBDId	Remote BD ID
RemoteMAC	Remote MAC address
LocalInterface	Local interface
RemoteInterface	Remote interface
TunnelPeer	Peer IP address of the tunnel

Possible Causes

In a BD gateway scenario, a user frequently migrates between local and remote devices or between different local EVC sub-interfaces. (The alarm reporting condition is controlled by the arp host ip-conflict-check command. By default, an alarm is reported when the number of migrations within 180s reaches 5.)

Procedure

1. Based on the alarm information, determine the IP address, BD, and access interface of the alarm user.

If the alarm user's information can be determined, go to Step 2.
If the alarm user's information cannot be determined, go to Step 5.

2. Based on the network plan, service deployment, and alarm user information, check the user access information on the BD gateway and the user configuration on the device connected to the user access interface.

If multiple devices connected to the BD gateway are configured with the same alarm user IP address, go to Step 3.
Run the debugging arp packet command in the user view to obtain ARP packets of the alarm user, and run the display arp history command in the diagnostic view to check the user change information. If the user frequently goes online between distributed gateways or between different EVC sub-interfaces on the same device, go to Step 4.
If the same alarm user IP address is not configured on the devices connected to the distributed gateway and packets of the alarm user for frequent access cannot be obtained, go to Step 5.

3. Change the conflicting IP address and check whether the alarm persists.

If yes, go to Step 2.
If no, go to Step 6.

4. Based on the user operation logs, check whether the frequent migrations of the alarm user are proper.

If the frequent migrations of the alarm user can be determined to be proper, go to Step 6.
If the frequent migrations of the alarm user cannot be determined to be proper, go to Step 5.

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

6. End.