No relevant resource is found in the selected language.
Your browser version is too early. Some functions of the website may be unavailable. To obtain better user experience, upgrade the browser to the latest version.
CloudEngine 12800 and 12800E V200R005C10 Configuration Guide - Security
This document describes the configurations of Security, including AAA, 802.1x Authentication, ACL, TCAM ACL Customization, local attack defense, Microsegmentation, MFF, attack defense, traffic suppression and storm control, ARP security, Port security, MACsec, DHCP snooping, IPSG, URPF, SSL, Keychain and FIPS.
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).
Protocol Packets Are Not Sent to the CPU
Protocol Packets Are Not Sent to the CPU
Fault Description
Protocol packets are not sent to the CPU after CPU attack defense is configured.
Common Causes
Possible causes are as follows:
A blacklist has been configured or a rule is configured to discard the specified protocol packets.
The CPU is attacked by invalid packets.
Procedure
Check whether a rule has been configured to discard protocol packets on the device.
Run the display
current-configuration command in the system view to check the configured attack defense policy.
Run the display cpu-defend policy [ policy-name ] command to check whether a blacklist, or
rule is configured in an attack defense policy to discard protocol packets.
If a blacklist is configured, run the display acl or display acl ipv6 command to check whether protocol packets match the rules in the blacklist. If protocol packets match the rules, adjust the rules as required. Otherwise, go to
the next step.
If the action taken on the protocol packets sent to the CPU is deny, run the car command in the attack defense policy view to set the rate limit.
If no blacklist is configured, and the action taken on the protocol packets sent to the CPU is not deny, go to step 2.
Check statistics for packets sent to the CPU.
Run the display cpu-defend statistics [ packet-typepacket-type ] { all | slotslot-id } command to check statistics on packets sent to the CPU. If a large number of protocol packets are being discarded, check whether these packets are invalid attack
packets using the attack source tracing function. If they are invalid attack packets, use the configured blacklist or traffic policy to prevent these packets from being sent to the CPU.