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

Reminder

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

upgrade

CX11x, CX31x, CX710 (Earlier Than V6.03), and CX91x Series Switch Modules V100R001C10 Configuration Guide 13

The documents describe the configuration of various services supported by the CX11x&CX31x&CX91x series switch modules The description covers configuration examples and function configurations.
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).
Common Configuration Errors

Common Configuration Errors

This section describes common faults caused by incorrect local attack defense configurations and provides the troubleshooting procedure.

Attack Source Tracing Does Not Take Effect

Fault Description

Attack source tracing does not take effect after attack source tracing is configured.

Common Causes

Possible causes are as follows:
  • The attack defense policy is not applied
  • The checking threshold for attack source tracing is large.

Procedure

  1. Determine whether the attack defense policy configured with attack source tracing is applied.
    1. Run the display current-configuration command in the system view to check whether the cpu-defend-policy command is configured.
    2. If the policy is not configured, run the cpu-defend-policy command in the system view to configure the policy. If the policy is configured, go to the next step.
  2. Check whether the checking threshold for attack source tracing is large.

    Run the display this command in the attack defense policy view to check the checking threshold for attack source tracing. If the value is large, run the auto-defend threshold command in the attack defense policy view to reduce the value.

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:
  • Protocol packets are not sent to the CPU for the reasons such as a blacklist has been configured or a rule is configured to discard the specified protocol packets.
  • Invalid packets attack the CPU.

Procedure

  1. Check whether a rule is configured to discard protocol packets on the device.
    1. Run the display current-configuration 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 a 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.

  2. Check statistics about 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 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.

The Blacklist Does Not Take Effect

Fault Description

The Blacklist does not take effect after the Blacklist is configured.

Common Causes

Possible causes are as follows:
  • Rules in the blacklist does not match the packet.
  • ACL resources are insufficient.

Procedure

  1. Run the display cpu-defend policy policy-name command to check the attack defense policy.
  2. Check the ACL of the blacklist in the displayed attack defense policy information, and run the display acl acl-number command to check whether service packets match the ACL rule.
  3. If service packets do not match the ACL rule, run the rule command in the ACL view to modify the ACL rule. If service packets match the ACL rule, the blacklist may fail to be applied because ACL resources are insufficient.
Translation
Download
Updated: 2019-12-13

Document ID: EDOC1000041694

Views: 61013

Downloads: 3623

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