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.


Configuration Guide - Security

S1720, S2700, S5700, and S6720 V200R011C10

This document describes the configurations of Security, including ACL, local attack defense, MFF, attack defense, traffic suppression and storm control, ARP security, Port security, DHCP snooping, ND snooping, PPPoE+, IPSG, SAVI, URPF, keychain, MPAC, separating the management plane from the service plane, security risks, PKI.
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).
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.


  1. Check whether a rule has been configured to discard protocol packets on the device.
    1. Run the display this command in the system view to check the configured attack defense policy.
    2. 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 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.

  2. Check statistics for packets sent to the CPU.

    Run the display cpu-defend statistics [ packet-type packet-type ] [ all | slot slot-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.

Updated: 2019-03-28

Document ID: EDOC1000178177

Views: 219840

Downloads: 712

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