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. hwARPSEntryCheck

SECE_1. hwARPSEntryCheck


SECE/4/ARP_ENTRY_CHECK:OID=[oid] Arp entry attack.(SourceInterface=[OCTET], SourceIP=[OCTET], SourceMAC=[OCTET], PVLAN=[INTEGER], CVLAN=[INTEGER])

The system detects attack packets used to modify ARP entries.


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, ARP entries on the devices may be changed to ARP entries of attackers. As a result, user traffic is intercepted by attackers and user services are interrupted.

Possible Causes

The devices are attacked by packets used to modify ARP entries.


  1. Find the interface where attacks occur according to SourceInterface.
  2. Check whether users who are not in the DHCP snooping binding table range are connected to the interface.
  3. If new users are connected, run related DHCP snooping commands to generate the DHCP snooping binding table. Then find the interface where the gateway conflict occurs according to the value of SourceInterface.

Related Information


Updated: 2019-03-06

Document ID: EDOC1100041475

Views: 101289

Downloads: 61

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next