No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Alarm Handling

AR100, AR120, AR160, AR1200, AR2200, AR3200, and AR3600 V300R003

This document provides the trap description, attributes, parameters, impact on the system, possible causes, procedures, and references. This document provides a complete set of traps, through which intended readers are kept of the running status of the device so as to locate faults.

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
SECE_1. hwARPSGatewayConflict

SECE_1. hwARPSGatewayConflict


SECE/4/GATEWAY_CONFLICT:OID=[oid] Gateway conflict.(SourceInterface=[OCTET], SourceIP=[OCTET], SourceMAC=[OCTET], PVLAN=[INTEGER], CVLAN=[INTEGER])

The system detects attack packets whose source IP addresses are the same as the gateway IP address.


Alarm ID Alarm Severity Alarm Type Warning equipmentAlarm(5)


Name Meaning

Indicates the MIB object ID of the alarm.

SourceInterface Indicates the source interface of packets.
SourceIP Indicates the source IP address of packets.
SourceMAC Indicates the source MAC address of packets.
PVLAN Indicates the outer VLAN ID of packets.
CVLAN Indicates the inner VLAN ID of packets.

Impact on the System

If this alarm is generated, the user gateway information may be modified by an attacker. As a result, the user is attacked and user services are interrupted.

Possible Causes

The device is attacked by packets whose source IP address is the same as the gateway IP address.


  1. Find the interface where the gateway conflict occurs according to the value of SourceInterface.
  2. Lock the user who sends gateway conflict packets according to the values of SourceMAC and PVLAN.
  3. Check whether the allocated address of the user conflicts with the gateway address. If the address conflicts, allocate an address to the user again. If the address does not conflict, the user may be the attacker. In this case, you can take such measures as disconnecting the user.

Related Information


Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 106919

Downloads: 68

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next