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

S9300, S9300E, and S9300X V200R010C00

This document provides the explanations, causes, and recommended actions of alarms on the product.
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. hwARPSPacketCheck

SECE_1. hwARPSPacketCheck


SECE/4/ARP_PACKET_CHECK:OID [oid] Invalid packet.(SourceInterface=[OCTET], SourceIP=[OCTET], SourceMAC=[OCTET], OuterVlan=[INTEGER], InnerVlan=[INTEGER])

The system detected invalid ARP packets.


Alarm ID Alarm Severity Alarm Type Warning equipmentAlarm(5)


Name Meaning
OID Indicates the ID of the MIB object.
SourceInterface Indicates the source interface of packets.
SourceIP Indicates the source IP address of packets.
SourceMAC Indicates the source MAC address of packets.


Indicates the outer VLAN ID of packets.


Indicates the inner VLAN ID of packets.

Impact on the System

If this alarm is generated, the device may be attacked. If the attack traffic volume is heavy, the device is busy processing attack packets. As a result, services of authorized users are interrupted.

Possible Causes

The device received invalid ARP packets.


  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-08-21

Document ID: EDOC1000142054

Views: 192410

Downloads: 44

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Previous Next